[Bug]: cannot access a scoped thread local variable without calling set first

[Joozty]

System Info

System:
OS: Linux 6.5 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
CPU: (2) x64 AMD EPYC 7763 64-Core Processor
Memory: 6.72 GB / 7.74 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.13.1 - /opt/hostedtoolcache/node/20.13.1/x64/bin/node
Yarn: 1.22.22 - /usr/local/bin/yarn
npm: 10.5.2 - /opt/hostedtoolcache/node/20.13.1/x64/bin/npm
pnpm: 9.7.0 - ~/setup-pnpm/node_modules/.bin/pnpm
Browsers:
Chrome: 128.0.6613.84
Chromium: 128.0.6613.0

Details

Builds are failing with the error message:
cannot access a scoped thread local variable without calling 'set' first.

This issue began occurring in version @rspack/core 1.0.0-beta.5 and is still present in version 1.0.0. The build completes successfully on my local machine (macOS), but it fails when running in CI using GitHub Actions with the latest Ubuntu image.

Reproduce link

No response

Reproduce Steps

This is a bit complicated, and I am not sure if I will be able to provide a minimal reproducible example.

[Joozty]

It should be anywhere between 218bda0 (1.0.0-beta.5) and f9b6ca2 (1.0.0-beta.4).

I think it is caused by rspack.HtmlRspackPlugin, when I disable it build does not fail.

[Joozty]

Maybe this commit 250304a

[h-a-n-a]

I will take a look into this one soon. You can temporarily switch to html-webpack-plugin if disabling HtmlRspackPlugin fixes this.

[Joozty]

Any luck guys? Thanks a lot for looking into it.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[hardfist]

@Joozty do you still met this problem?

[Joozty]

bump

[Joozty]

yes still a problem