Skip to content

Conversation

@christopher-hakkaart
Copy link
Member

  • Update headers and sections
  • Make into multiple pages
  • Start migration error messages

@netlify
Copy link

netlify bot commented Jan 12, 2026

Deploy Preview for seqera-docs ready!

Name Link
🔨 Latest commit 2263543
🔍 Latest deploy log https://app.netlify.com/projects/seqera-docs/deploys/6967620323000c0008756467
😎 Deploy Preview https://deploy-preview-1007--seqera-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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.
Copy link
Contributor

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
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants