Subscribe on changes!

Getting "Unhandled error during execution of scheduler flush. This is likely a Vue internals bug."

avatar
Mar 23rd 2021

Version

3.0.7

Reproduction link

https://jsfiddle.net/pez641n5/2/

Steps to reproduce

Click on any of the list items. The error message "Unhandled error during execution of scheduler flush. This is likely a Vue internals bug.Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/vue-next" is shown, and the selected text is not shown in the input.

What is expected?

When clicking on an item, it is shown in the input.

What is actually happening?

Getting the mentiuoned error message, and the text is not shown in the input.

avatar
Mar 23rd 2021

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.


Please do not open issues with fake reproductions like that one using Vue 1

avatar
Mar 23rd 2021

Well, this is a bug that occurs when using Vue 3.0.7. If it helps, here is teh stack trace that I get in my version of the code (I am not sure how to get that in jsfiddle):

runtime-core.esm-bundler.js:38 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/vue-next 
  at <SelectDialog list= (3) ["One", "Two", "Three"] > 
  at <App>
warn @ runtime-core.esm-bundler.js:38
logError @ runtime-core.esm-bundler.js:211
handleError @ runtime-core.esm-bundler.js:203
callWithErrorHandling @ runtime-core.esm-bundler.js:157
flushJobs @ runtime-core.esm-bundler.js:384
Promise.then (async)
queueFlush @ runtime-core.esm-bundler.js:286
queueJob @ runtime-core.esm-bundler.js:280
run @ reactivity.esm-bundler.js:183
trigger @ reactivity.esm-bundler.js:189
set @ reactivity.esm-bundler.js:292
set @ runtime-core.esm-bundler.js:6219
onClick @ SelectDialog.vue:12
callWithErrorHandling @ runtime-core.esm-bundler.js:154
callWithAsyncErrorHandling @ runtime-core.esm-bundler.js:163
invoker @ runtime-dom.esm-bundler.js:308
runtime-dom.esm-bundler.js:175 Uncaught (in promise) DOMException: Failed to execute 'setAttribute' on 'Element': '0' is not a valid attribute name.
    at patchAttr (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:6789:10)
    at patchProp (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:6931:9)
    at patchProps (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:4319:11)
    at patchElement (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:4257:9)
    at processElement (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:4156:7)
    at patch (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:4088:11)
    at patchBlockChildren (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:4308:7)
    at patchElement (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:4289:7)
    at processElement (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:4156:7)
    at patch (http://localhost:3000/node_modules/.vite/vue.js?v=2c2f4f03:4088:11)
avatar
Mar 23rd 2021

ok, my bad: I was using v-bind instead of v-model.