clockworklabs / clockworklabs/SpacetimeDB
CI flake: Test Suite / typescript::insert_call_uuid_v4, typescript::insert_call_uuid_v7,...
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::insert_call_uuid_v4typescript::insert_call_uuid_v7typescript::insert_caller_connection_idtypescript::insert_caller_identitytypescript::insert_connection_id
Error:
thread 'typescript::insert_call_uuid_v4' (153616) 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/32949572715/job/98118575600 (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 with the five named TypeScript tests and crates/testing/src/sdk.rs:175, where the PoisonError unwrap occurs. Reproduce the failed GitHub Actions Test Suite run or run the listed tests locally, then trace the shared failure state around that line. Done means the tests no longer flake and the Test Suite passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, typescript
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100