clockworklabs / clockworklabs/SpacetimeDB

CI flake: segfault in TS `delete_connection_id` test

Open
#5,402 1 comment 0 reactions 0 assignees View on GitHub

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 merge-queue run succeeded in a later merge-queue run without a new PR head commit.

Tests:

  • typescript::delete_connection_id

Error:
thread 'typescript::delete_connection_id' (193365) panicked at crates/testing/src/sdk.rs:115:9:
(running): Error running "node --experimental-websocket -e '(async () => { const m = require("/home/runner/actions-runner/_work/SpacetimeDB/SpacetimeDB/sdks/rust/tests/test-client/target/sdk-test-web-bindgen/test-...

Failed job runs:

Context:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the failing typescript::delete_connection_id test and the panic location in crates/testing/src/sdk.rs:115. Review the failed and later successful merge-queue runs to determine why the test intermittently segfaults. Done means identifying and fixing the flake, then confirming the test passes reliably in CI.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, rust, typescript
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.