-
Notifications
You must be signed in to change notification settings - Fork 2.6k
feat(core): transition daemon from queue to transaction based messaging #28983
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
Conversation
|
Your CI Pipeline Execution ↗ for commit 87a0bac ⏳ is in progress.
Last updated at 2024-12-12 18:47:18UTC Sent with 💌 from NxCloud. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
686e04a to
0b4924b
Compare
0b4924b to
7cc7547
Compare
7cc7547 to
155844f
Compare
9fcc0a3 to
a22d5d5
Compare
097b8d9 to
87a0bac
Compare
87a0bac to
7eecf06
Compare
|
Your CI Pipeline Execution ↗ for commit 7eecf06 has failed ❌
☁️ Nx Cloud last updated this comment at |
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
The daemon uses a serial queue to communicate with individual Nx processes. This can slow things down if things inside of a
promise.allor similar method call the daemon multiple times, as all calls must wait for the prior call to finish before starting.Expected Behavior
The daemon utilizes a transaction based message system, such that it can respond to a message which arrived later if its able to complete quicker
Related Issue(s)
Fixes #