-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Mark maxWorkers
as optional
#8848
Conversation
Everything in |
TS did not appreciate |
Seems nothing was relying on the mutation - yay! |
@jeysal The mac build passed all the tests, but failed w/ exit code 1 &:
Do you think this could be what's happening in my other PR, & CircleCI just isn't reporting the signal that the command failed w/? Eitherway, I don't have a Mac, so not too sure how to fix this 😕 |
Idk, in the other one all jobs are failing so I don't think it's related. I also don't see the SIGSEGV anywhere, maybe I'm missing something |
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.
Seems sensible to me. Mind updating the changelog as well?
@SimenB No problem - 🎉 No segfault! 🎉 I'm also rebasing my snapshot branch, which'll hopefully not have problems with. If you don't mind me taking advantage of your attention, have you had a chance to look over my comment about doing releases on |
Codecov Report
@@ Coverage Diff @@
## master #8848 +/- ##
==========================================
- Coverage 64.72% 64.71% -0.02%
==========================================
Files 277 277
Lines 11706 11706
Branches 2874 2875 +1
==========================================
- Hits 7577 7575 -2
- Misses 3512 3514 +2
Partials 617 617
Continue to review full report at Codecov.
|
thanks for the patience! |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Currently
maxWorkers
inInitialConfig
is marked as required, which meansnormalize
is being used in an "unsafe" manner in some places.Meanwhile
getMaxWorkers
ensures this value is set innormalise
.I don't think this needs a changelog entry as it's an internal change - externally
maxWorkers
is technically already optional.