-
Notifications
You must be signed in to change notification settings - Fork 14
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
fix(core): CONFIG_OVERRIDE mutex poison #3946
Conversation
Co-authored-by: DaughterOfMars <[email protected]>
crates/iota-e2e-tests/tests/snapshots/snapshot_tests__body_fn.snap
Outdated
Show resolved
Hide resolved
This pull request has been deployed to Vercel. Latest commit: 7069a96 ✅ Preview: https://iota-rebased-explorer-092603f1de8088243ccb8b861b23e-i0su9g1sx.vercel.app |
This pull request has been deployed to Vercel. Latest commit: 7069a96 ✅ Preview: https://apps-backend-29a719c9ccbdb9b80c97b599a599d8953354da-9ybjmhki8.vercel.app |
This pull request has been deployed to Vercel. Latest commit: 7069a96 ✅ Preview: https://wallet-dashboard-a225fcfa1e2f852205a61a7cd1d5d93e92-50oohptaw.vercel.app |
Description of change
This PR fixes a problem that was introduced in a previous PR (when attempting to fix a broken test).
Since we didn't test the consensus package, we didn't realize we introduced another problem.
Problem Description
The CONFIG_OVERRIDES need to be thread local as the lock can otherwise end up in a poisoned state.