-
Notifications
You must be signed in to change notification settings - Fork 5
[Fusion] Troubleshooting error codes #1007
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
christopher-hakkaart
commented
Jan 12, 2026
- Update headers and sections
- Make into multiple pages
- Start migration error messages
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| - **Ambiguity of exit codes**: As the container entrypoint, the container's final exit code can originate from either Fusion itself (e.g., exit code `174`) or from the task's actual command. When a container exits with a failure code, there's no immediate way to determine the source of the failure without examining logs. | ||
|
|
||
| - **Mixed log outputs**: Fusion also emits errors to stdout, where they typically mix with the task output. They are indistinguishable from a task's own errors when you review the task's logs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alberto-miranda is this still the case with our improved error logging?
|
|
||
| This page describes Fusion's error reporting system, including exit codes, FUSE status codes (errno values), cloud provider error categories, and internal error types. | ||
|
|
||
| ## Architectural limitations |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm actually not sure we need to have this whole section at the moment. This just looks like us listing our product flaws and I'm not sure how much value it provides to the end user (other than us saying 'Fusion has limitations' - surely their response will be 'well then fix it?' As internal documentation it makes sense