v-data-table causing vue warn infinite update loop in component render function

[austi10]

Version

1.0.0-beta.30

Reproduction link

https://github.com/Austino18/Vue-Test-Utils-v1.0.0-beta30--using-Vuetify-Data-Table

Steps to reproduce

Clone/Download the github link provided and kindly follow the readme

What is expected?

The test should run without any vue warnings

What is actually happening?

v1.0.0-beta30 leads to the following:
[Vue warn]: You may have an infinite update loop in a component render function.

Found in

---->VDataTable

---

The warning is encountered when using vue test utils v1.0.0-beta 30.
The same test case passes upon using the previous version, v1.0.0-beta29 without any warnings

[leoclipet]

Any news on this one ? I have actually a similar problem but I tried version beta 29, 30 and 31.

[austi10]

Any news on this one ? I have actually a similar problem but I tried version beta 29, 30 and 31.

I haven't heard anything from the team yet. Hopefully they provide a fix for it soon

[lmiller1990]

I notice the loop occurring if I remove the stubbed requestAnimationFrame. I guess you just stubbed that to avoid the infinite loops?

I wonder what changed in beta-30 that would be causing this. I'll think about this a bit today. The main priority at the moment is updating the codebase to work with Vue 3, and rewriting big chunks, so I can't promise I'll find a fix for this.

On the other hand, we are using libraries like Vuetify as part of the base test suite for the Vue 3 update, so bug like this should be much less common. One of the main pain points of the beta is poor support for third party component libs, which is one the main things we are looking to address.

If you would like to help out debugging this, I'd like at the release notes for v30 and see what might have caused this to happen. The process I usually follow from there is going into node_modules and commenting out the VDataTable code until the error stops - this is how I find the root problem.

[Ins1eme]

the same problem .31 @lmiller1990

[andriymurovanyi]

Also i have the same problem.

[bob-lee]

Downgrading to 1.0.0-beta.29 was a temporary fix for this issue for me. Also it runs a lot quicker than 1.0.0-beta.30

[lmiller1990]

Thanks for the feedback all - I can take a look at the diff between beta-29 and beta-30 sometime this week, if anyone else wants to help https://github.com/vuejs/vue-test-utils/releases/tag/v1.0.0-beta.30

Something to do with sync mode getting removed I guess? Hm.

[mkalam-alami]

I also reproduce the problem with 1.0.0-beta.31, downgrading to 29 works.
If it helps, I have tried toggling the sync option on 29 but I can't trigger the error at all.

[d2phap]

I got the same problem

[lmiller1990]

I haven't had a chance to look at this - focusing on Vue 3 integration (which includes better support for Vuetify and none of this sync legacy stuff that messes everything up).

For now, it seems the best work around is downgrading to 29 (not great, but I don't have anything better at the moment, sorry all).

Happy to help guide someone who wants to dive into this issue, can ping me here or Vueland.

[pgoshulak]

I dug into this a while back and it seems like the issue is in VDataIterator (which is extended by VDataTable)