timers: fix priority queue removeAt fn#23870
timers: fix priority queue removeAt fn#23870apapirovski wants to merge 1 commit intonodejs:masterfrom
Conversation
3e8f600 to
bdb44a5
Compare
|
I suppose you want to fast-track? I can promote the release today or tomorrow, if someone else prepares it. |
|
Please 👍 this if you approve fast tracking. |
mcollina
left a comment
There was a problem hiding this comment.
LGTM and +1 to fast track. Can you add a test with timers as well?
|
Commit pushed since last CI. CI again: https://ci.nodejs.org/job/node-test-pull-request/18147/ |
|
@Trott technically I updated the CI after the commit :) |
jasnell
left a comment
There was a problem hiding this comment.
A fast-track is good. There are a few more commits landed in master that should be in an 11.0.1 release. Let's make sure we pull in the other semver-patch commits.
|
+1 to fast-track |
PR-URL: nodejs#23870 Fixes: nodejs#23860 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: James M Snell <[email protected]>
|
Landed in 958d5b7. The request from @mcollina for an additional test can be added as a separate PR if highly desirable. I assumed it was an optional nit based on their approval. Hope that was OK. |
|
That was the intent, yes
Il giorno gio 25 ott 2018 alle 19:47 Rich Trott <[email protected]>
ha scritto:
… Closed #23870 <#23870>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23870 (comment)>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AADL4x9UKSHiycSP4JMv852tsB4fW7Suks5uofk-gaJpZM4X6EEr>
.
|
PR-URL: #23870 Fixes: #23860 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: James M Snell <[email protected]>
PR-URL: #23870 Fixes: #23860 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Gus Caplan <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: James M Snell <[email protected]>
|
Thank you for the fix. |
|
I'm assuming this fix is based on top of a Semver-Major change and thus shouldn't land within LTS. Can you please change the labels to |
|
Took me a whole week of my API randomly crashing to figure out this was the issue! Was on Node 11.0.0. Thank you so much for the fix! Went back to LTS though ;). |
🤷♂️ I'm an idiot... and we probably should get a release out (11.0.1)... @nodejs/tsc
Fixes: #23860
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes