-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Sudden interruption of @nx/next:build target on 18.0.5 #21895
Comments
Well, seems listen events on process and interrupt
|
Well. Code above doesn't solve the problem, we still experiencing sudden interruption of nextjs build through plugin (no signals sent) config of target is
I hope nx/nx nextjs plugin already fixed that in next releases. Going to wait for fix: #23496 |
Seems that bug is related to this issue #23013 |
Closing the issue. We have a huge code base and it worked on nextjs + react-router. We decided to migrate to nextjs pages router. Starting from some point nextjs start to silently fail on build and return zero code. We decreased load on nextjs by removing option transpilePackages which were required for transpile out external design-system package and seems now build is stable and 25% faster. Going to split application on couple smaller. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
I'm using nx with custom task runner. Which is supposed only to upload cache artifacts from
.nx/cache
to GCP.We use buildkite for CI purposes. Months ago I noticed that some builds are invalid (in my case that was when I downloaded artifacts on some of next similar builds and they are not full (doesn't contain desired site dist, much smaller by size).
After couple months I figure out that was because of cancel-running-intermediate-builds feature.
I'm using nextjs for site build. According to logs seems build of nextjs interrupted (I'm using plugin), but
GCSRemoteCache.store
function still called (when artifacts are incorrect).Also according to logs seems even if parent task is failed, Nx still launch dependent task (which seems very wrong)
Probably I'm incorrectly implementing task runner. Could you point me how to properly handle termination?
Content of nx.json
Content of apps/dashboard/project.json
Content of libs/nx-task-runner/lib/index.js
Content of libs/nx-task-runner/lib/cache.js
Expected Behavior
GCSRemoteCache.store is not called when plugin build cancelled.
The target is not launched when the dependent task failed.
GitHub Repo
No response
Steps to Reproduce
It seems need to launch
nx affected -t build -c production
in buildkite CI and then interrupt build in the stage when plugin @nx/next:build working. Plus need to implement custom task runner.Nx Report
Failure Logs
No response
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: