exercism / exercism/website

OperationError: The operation failed for an operation-specific reason

Open
#9,443 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

```
The operation failed for an operation-specific reason
```

## Stack trace

```
../app/javascript/components/editor/header/Settings.tsx:98 in Settings
../app/javascript/components/Editor.tsx:88 in Editor_default
../node_modules/@sentry/react/src/errorboundary.tsx:101 in new ErrorBoundary
../node_modules/@tanstack/react-query/src/QueryClientProvider.tsx:29 in QueryClientProvider
```

## Tracking Details
- **Project**: exercism-js
- **Sentry**: [OperationError: The operation failed for an operation-specific reason](https://thalamus-ai.sentry.io/issues/143420479/)
- **Culprit**: id(app/javascript/components/dropdowns/useDropdown)
- **First seen:** Aug 28, 2026

Contributor guide

Open the contributing guide

Research direction

Start by reading app/javascript/components/editor/header/Settings.tsx at line 98 and trace the call through app/javascript/components/Editor.tsx. Then inspect the app/javascript/components/dropdowns/useDropdown entry named as the Sentry culprit and use the linked Sentry event for context. Done means the reported OperationError no longer occurs in the affected editor flow.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.