reactjs / reactjs/react.dev

Uncaught Error: Should have a queue. This is likely a bug in React. Please file an issue.

Open
#3,178 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
11.8k
Forks
7.9k
Avg merge
1d 11h
Merged PRs (30d)
11

Description

This is the console message:
Uncaught Error: Should have a queue. This is likely a bug in React. Please file an issue.
at updateReducer (react-dom.development.js:16456)
at Object.useReducer (react-dom.development.js:17326)
at useReducer (react.development.js:1623)
at UseReducer (vendorsmain.node_modules%40.chunk.js:1937)
at useSelectorWithStoreAndSubscription (useSelector.js:34)
at useSelector (useSelector.js:125)
at UseSelector (vendorsmain.node_modules%40.chunk.js:1937)
at useSelector (index.js:7)
at usePagePreference (use-pagePreference.js:15)
at WorkflowReport.jsx:11
at renderWithHooks (react-dom.development.js:16240)
at updateFunctionComponent (react-dom.development.js:18327)
at beginWork$1 (react-dom.development.js:20150)
at HTMLUnknownElement.callCallback (react-dom.development.js:337)
at Object.invokeGuardedCallbackDev (react-dom.development.js:386)
at invokeGuardedCallback (react-dom.development.js:441)
at beginWork$$1 (react-dom.development.js:25737)
at performUnitOfWork (react-dom.development.js:24661)
at workLoopSync (react-dom.development.js:24637)
at performSyncWorkOnRoot (react-dom.development.js:24236)
at react-dom.development.js:12181
at unstable_runWithPriority (scheduler.development.js:818)
at runWithPriority$2 (react-dom.development.js:12131)
at flushSyncCallbackQueueImpl (react-dom.development.js:12176)
at flushSyncCallbackQueue (react-dom.development.js:12164)
at Object.batchedUpdates$1 [as unstable_batchedUpdates] (react-dom.development.js:24358)
at react-hot-loader.development.js:3045
at react-hot-loader.development.js:3004

Contributor guide

Open the contributing guide

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 reported stack trace at updateReducer and useReducer, then follow useSelector.js:34, useSelector.js:125, use-pagePreference.js:15, and WorkflowReport.jsx:11. Reproduce the error from the console trace and identify a concrete change and verification case; the issue does not provide enough information to define completion.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.