fix: set correct workerId in runtime: 'child_process'

[alisd23]

First attempt at using the correct threadId/workerId for the worker when in child_process mode.

• Set worker data as required in init options as it seems to be always defined.
• Pass internal (correct) tinypool workerId down to fork with process.env
• Set correct fork state process.__tinypool_state__.workerId from the env variable

[alisd23]

I couldn't think of a better way to test the correct threadId so I decide to just check that the ID equals 1 exactly, which is more precise. I can't imagine that internal ID strategy would change anytime soon so I think it's probably fine?

[AriPerkkio]

Looks good to me, thanks! Impressive how fast you were able to set up a PR. 🚀

@Aslemammad this PR can be considered as semver patch. The process.__tinypool_state__.workerId was always supposed to be Tinypool's workerId and not the process.id as it was set.

[Aslemammad]

@AriPerkkio @alisd23 Thank you so much for the effort folks!

[alisd23]

Thanks both for the help and getting this through so quick! 👍

[alisd23]

Final thing, @Aslemammad when can we expect a release? Looks like releases are done manually is that right?

[Aslemammad]

Final thing, @Aslemammad when can we expect a release? Looks like releases are done manually is that right?

Yea sure, I'm just going to give an access to @AriPerkkio so he can releases.

[AriPerkkio]

Thanks! 🙌

I'll do release tomorrow and do some testing with Vitest.