exercism / exercism/website

InvalidStateError: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.

Open
#9,466 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
548
Forks
168
Avg merge
1d 3h
Merged PRs (30d)
28

Description

## Error

```
Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.
```

## Stack trace

```
/asset/asset.js:2 in e.WebsocketManager.send
/asset/asset.js:2 in e.EntityManager.flush
../node_modules/@sentry/browser/src/helpers.ts:117 in sentryWrapped
```

## Tracking Details
- **Project**: exercism-js
- **Sentry**: [InvalidStateError: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state.](https://thalamus-ai.sentry.io/issues/144962841/)
- **Culprit**: e.WebsocketManager.send(asset/asset)
- **First seen:** Sep 4, 2026

Contributor guide

Open the contributing guide

Research direction

Start with the reported calls in asset/asset.js, especially WebsocketManager.send and EntityManager.flush, and inspect how the WebSocket connection state is handled before sending. Reproduce the Sentry error if possible and trace the relevant source around the bundled asset. Done means the CONNECTING-state exception no longer occurs during the reported exercism-js flow.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.