-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: unable to kill fuels dev
with pnpm
#3508
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This PR is published in NPM with version 0.0.0-pr-3508-20241230183927 |
CodSpeed Performance ReportMerging #3508 will degrade performances by 47.96%Comparing Summary
Benchmarks breakdown
|
…/fuels-ts into ps/fix/unable-to-kill-fuels-dev
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.
We need tests for both issues the PR is closing (#2889, #3479).
You can find a test for #2889 in #3038. The same infrastructure in that test can be used for this PR. An approach could be to use a modified version of runInit
where one would add a "fuels:dev": "fuels dev"
script into the package.json
file and then run a detached spawn('pnpm fuels:dev')
command. This should simulate the same behavior that we do manually when testing with releases of PRs.
@nedsalk I found that the test within #3038 only working with Linux due to the I found that when I re-added the following "fix" line to the source code (e2998d8), the tests can still pass. I experienced a lot of timeouts with this test in CI, have you experienced similar? For me, we could investigate this further but I don't think the time required outweighs the value that this test would provide. Processes and process events are inherently difficult to test and I believe manual testing is adequate for now. Happy to create an issue to revisit this and add automated tests for this scenario, but IMO it's not top priority. |
@petertonysmith94 sounds good. I have created #3547 and we can continue the discussion there. With regards to the test I wrote in #3038, it was failing at that time's |
Coverage Report:
Changed Files:
|
fuels:dev
process when usingpnpm
#3479fuels dev
withCTRL+C
(SIGINT
) doesn't killfuel-core
node #2889Summary
fuels dev
not exiting on a single Ctrl + C forpnpm
.npm
,pnpm
andbun
. (0.0.0-pr-3508-20241230183927
)Checklist