clockworklabs / clockworklabs/SpacetimeDB
CI flake: Test Suite / typescript::indexed_simple_enum, typescript::insert_call_uuid_v4,...
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 25.2k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 46
Description
Detected by CI Gremlin after a failed GitHub Actions attempt succeeded on rerun.
Tests:
typescript::indexed_simple_enumtypescript::insert_call_uuid_v4typescript::insert_call_uuid_v7typescript::insert_caller_connection_idtypescript::insert_caller_identity
Error:
thread 'typescript::indexed_simple_enum' (111399) panicked at crates/testing/src/sdk.rs:175:5:
called Result::unwrap() on an Err value: PoisonError { .. }
Failed job runs:
- https://github.com/clockworklabs/SpacetimeDB/actions/runs/33025679340/job/98367633650 (Test Suite, attempt 1 -> 2)
Timeout detection:
- none
Context:
- none
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at crates/testing/src/sdk.rs:175 and inspect how the listed TypeScript tests share test setup when a GitHub Actions run is retried. Reproduce the affected Test Suite tests and trace the PoisonError reported for typescript::indexed_simple_enum. Done means the listed tests pass reliably without the CI-only flake or unwrap panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust, typescript
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100