Skip to content
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

feat(gatsby-worker): Show original stack trace #37206

Conversation

LekoArts
Copy link
Contributor

@LekoArts LekoArts commented Dec 7, 2022

Description

When our workers fail a task, they'll often error with a single line message with no context. One of our top error messages across all versions is "Building static HTML failed".

Or it says Error: Worker exited before finishing task. With this PR the original error thrown in the error should be surfaced at leat.

There is polishing to be done in follow-up work, but this is a good start to begin with.

Related Issues

Fixes #36947
[ch58027]

@LekoArts LekoArts added the topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine) label Dec 7, 2022
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Dec 7, 2022
@LekoArts LekoArts removed the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Dec 7, 2022
@LekoArts LekoArts merged commit 3b75594 into master Dec 8, 2022
@LekoArts LekoArts deleted the fix/gatsby-worker/ensure-sudden-worker-exit-doesnt-loose-messages branch December 8, 2022 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: core Relates to Gatsby's core (e.g. page loading, reporter, state machine)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Gatsby doesn't add detailed logs for Parallel Queries Errors on macOS
3 participants