You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking through the AsyncWrap code, and it appears that 64-bit signed int values are being cast to 32-bit signed int values here, here and here.
A few questions:
Am I reading this correctly?
Is there an alternative here? I don't immediately see how to seed a V8::Number with a 64-bit int.
Is 32 bits enough "space" to maintain a monotonically increasing set of unique IDs? A process running continuously for 30 days, and consuming 1657 async events per second would exhaust this space & subsequent casts would overlap with previously issued IDs.
Activity
async_wrap: add uid to TickObject instances
trevnorris commentedon Apr 14, 2016
No it's not correct, and I know it's a problem. I have a fix in the pipeline.
trevnorris commentedon Jun 1, 2016
Fixed here nodejs/node#7096