nextcloud / nextcloud/profiler
JS error when explaning a query
Open
Nobody has claimed this yet.
- Dominant language
- Vue
- Stars
- 11
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 17
Description
After clicking "Explain" on a query that has no explanation like SET SESSION AUTOCOMMIT=1
there is an JS error in the console and you can not toggle other queries anymore
Uncaught (in promise) TypeError: can't access property "emitsOptions", component is null
shouldUpdateComponent runtime-core.esm-bundler.js:6766
updateComponent runtime-core.esm-bundler.js:5316
processComponent runtime-core.esm-bundler.js:5262
patch runtime-core.esm-bundler.js:4767
patchBlockChildren runtime-core.esm-bundler.js:5123
patchElement runtime-core.esm-bundler.js:5041
processElement runtime-core.esm-bundler.js:4900
patch runtime-core.esm-bundler.js:4755
patchBlockChildren runtime-core.esm-bundler.js:5123
patchElement runtime-core.esm-bundler.js:5041
processElement runtime-core.esm-bundler.js:4900
patch runtime-core.esm-bundler.js:4755
patchKeyedChildren runtime-core.esm-bundler.js:5668
patchChildren runtime-core.esm-bundler.js:5545
processFragment runtime-core.esm-bundler.js:5225
patch runtime-core.esm-bundler.js:4741
patchBlockChildren runtime-core.esm-bundler.js:5123
patchElement runtime-core.esm-bundler.js:5041
processElement runtime-core.esm-bundler.js:4900
patch runtime-core.esm-bundler.js:4755
componentUpdateFn runtime-core.esm-bundler.js:5477
run reactivity.esm-bundler.js:237
runIfDirty reactivity.esm-bundler.js:275
callWithErrorHandling runtime-core.esm-bundler.js:199
flushJobs runtime-core.esm-bundler.js:408
Contributor guide
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
Reproduce the issue in the profiler UI by clicking “Explain” for a query without an explanation, such as SET SESSION AUTOCOMMIT=1, and inspect the affected Vue component and update path. Done means no console TypeError occurs and other queries can still be toggled afterward.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100