-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
lib: resolve the issue of not adhering to the specified buffersize #55896
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
@Ethan-Arrowood, please take a look at the PR when you have a chance. It should be ready for merge unless some any issues is found! |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #55896 +/- ##
==========================================
+ Coverage 88.00% 88.53% +0.53%
==========================================
Files 656 657 +1
Lines 188999 190413 +1414
Branches 35989 36554 +565
==========================================
+ Hits 166331 168589 +2258
+ Misses 15848 15007 -841
+ Partials 6820 6817 -3
🚀 New features to boost your workflow:
|
Looking good. Have you tested it locally by running the relevant fs readdir and opendir recursive test files? I'm not really sure if this needs a unique test as you are more just improving an existing solution. I requested a CI run now and we'll see how this does. Thanks for the contribution! |
Yes, I've tested it. It should be good unless I missed something.
Agreed. I don't think we need a new test since, as you mentioned, nothing fundamentally new was added. |
Looks good to me, and CI is passing! Thank you, lets gets this merged. |
Commit Queue failed- Loading data for nodejs/node/pull/55896 ✔ Done loading data for nodejs/node/pull/55896 ----------------------------------- PR info ------------------------------------ Title lib: resolve the issue of not adhering to the specified buffersize (#55896) ⚠ Could not retrieve the email or name of the PR author's from user's GitHub profile! Branch cu8code:55723 -> nodejs:main Labels fs, needs-ci Commits 1 - lib: resolve the issue of not adhering to the specified buffer size Committers 1 - cu8code <git8ankanroy@gmail.com> PR-URL: https://github.com/nodejs/node/pull/55896 Refs: https://github.com/nodejs/node/issues/55764 Reviewed-By: Ethan Arrowood <ethan@arrowood.dev> ------------------------------ Generated metadata ------------------------------ PR-URL: https://github.com/nodejs/node/pull/55896 Refs: https://github.com/nodejs/node/issues/55764 Reviewed-By: Ethan Arrowood <ethan@arrowood.dev> -------------------------------------------------------------------------------- ℹ This PR was created on Sun, 17 Nov 2024 17:27:03 GMT ✔ Approvals: 1 ✔ - Ethan Arrowood (@Ethan-Arrowood): https://github.com/nodejs/node/pull/55896#pullrequestreview-2470703507 ✘ Last GitHub CI failed ℹ Last Full PR CI on 2024-11-30T01:14:02Z: https://ci.nodejs.org/job/node-test-pull-request/63800/ - Querying data for job/node-test-pull-request/63800/ ✔ Last Jenkins CI successful -------------------------------------------------------------------------------- ✔ Aborted `git node land` session in /home/runner/work/node/node/.ncuhttps://github.com/nodejs/node/actions/runs/12093348479 |
Hm i thought the CI run succeeded. I'll see if a retry helps. |
We create a `queueHandler`, and in every iteration we execute the handlers in the `queueHandler` until we get a non-null result.
Keep an eye on that CI run. Lets make sure nothing is failing because of these changes. I haven't ran the CI recently so I'm unaware of current known flakey tests, but they are usually pretty obvious. |
@0hmX, are U planing to move with this fix?? i would like to help |
@edilson258 I do not plan to / know how to fix the failing tests. If you can help, I would appreciate it! |
Is there a way of accessing the CI logs or any other way of seeing the failure reason?? @Ethan-Arrowood ? |
Once the CI runs (again fresh) it will comment the result here. That link will be show any failures and details as to why |
@Ethan-Arrowood I think this is ready to be merged! |
Landed in a8a86b3 |
Great work @0hmX ! Thank you for your contribution - apologies it took so long to land! Next one should be faster 🏎️ |
fixes #55764
We create a
queueHandler
, and in every iteration we execute the handlers in thequeueHandler
until we get a non-null result.