[6.0.0alpha] Actions infinite loop regression

[PVince81]

See nextcloud/server#33387 (comment)

@Pytal can you investigate ?

[PVince81]

I suggest to first revert all changes in AppSidebar to see if the problem persists, in case it's only a side effect.

[Pytal]

Findings as follows

The infinite loop is not triggered in AppSidebar but rather in Actions

The recent changes which touch related code are these fixes #2878 and #2532

With the isValidSingleAction fix the markup https://github.com/nextcloud/nextcloud-vue/blob/79f3c499f14c8d188c93da2258bb690977bfa8f3/src/components/Actions/Actions.vue#L135-L159 which depends on firstAction renders as expected but because children change at some point during the render lifecycle the watcher https://github.com/nextcloud/nextcloud-vue/blob/79f3c499f14c8d188c93da2258bb690977bfa8f3/src/components/Actions/Actions.vue#L477-L488 mutates firstAction while rendering leading to the "infinite update loop in a component render function" error, commenting out the assignment removes the error

Wrapping it in $nextTick doesn't seem to work so any suggestions here are welcome @PVince81

[PVince81]

@vinicius73 @raimund-schluessler @marcoambrosini please help solve the infinite loop in the Actions component. I picked you as you are connected to the matching PRs.

[raimund-schluessler]

Findings as follows

The infinite loop is not triggered in AppSidebar but rather in Actions

The recent changes which touch related code are these fixes #2878 and #2532

With the isValidSingleAction fix the markup https://github.com/nextcloud/nextcloud-vue/blob/79f3c499f14c8d188c93da2258bb690977bfa8f3/src/components/Actions/Actions.vue#L135-L159 which depends on firstAction renders as expected but because children change at some point during the render lifecycle the watcher https://github.com/nextcloud/nextcloud-vue/blob/79f3c499f14c8d188c93da2258bb690977bfa8f3/src/components/Actions/Actions.vue#L477-L488 mutates firstAction while rendering leading to the "infinite update loop in a component render function" error, commenting out the assignment removes the error

Wrapping it in $nextTick doesn't seem to work so any suggestions here are welcome @PVince81

Does reverting #2878 fix the issue? Could also be related to the migration to floating-vue, although given the investigation above, I find it rather not likely. I can only have a look on Tuesday, sorry.

[raimund-schluessler]

Honestly, I find the Actions component a bit messy and wanted to rewrite it / clean it up. But I planned to add some tests for it in #2881 first, just haven't had the time to do it yet, though.

[marcoambrosini]

Does reverting #2878 fix the issue?

I've done some testing with and it doesn't seem so :/

I've also tried to link nextcloud/vue to server but it fails to build due to a problem with material design icons

ERROR in ./node_modules/@nextcloud/vue/node_modules/vue-material-design-icons/ToggleSwitchOff.vue 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
> <template>
|   <span v-bind="$attrs"
|         :aria-hidden="!title"
 @ ./node_modules/@nextcloud/vue/dist/Components/CheckboxRadioSwitch.js 2:79915-79967
 @ ./node_modules/babel-loader/lib/index.js!./node_modules/vue-loader/lib/index.js??vue-loader-options!./apps/settings/src/components/AdminTwoFactor.vue?vue&type=script&lang=js& 69:0-85 79:25-44
 @ ./apps/settings/src/components/AdminTwoFactor.vue?vue&type=script&lang=js& 1:0-186 1:202-205 1:207-390 1:207-390
 @ ./apps/settings/src/components/AdminTwoFactor.vue 2:0-66 3:0-61 3:0-61 10:2-8
 @ ./apps/settings/src/main-admin-security.js 26:0-61 36:22-36

[raimund-schluessler]

Does reverting #2878 fix the issue?

I've done some testing with and it doesn't seem so :/

I've also tried to link nextcloud/vue to server but it fails to build due to a problem with material design icons

ERROR in ./node_modules/@nextcloud/vue/node_modules/vue-material-design-icons/ToggleSwitchOff.vue 1:0

Module parse failed: Unexpected token (1:0)

You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

> <template>

|   <span v-bind="$attrs"

|         :aria-hidden="!title"

 @ ./node_modules/@nextcloud/vue/dist/Components/CheckboxRadioSwitch.js 2:79915-79967

 @ ./node_modules/babel-loader/lib/index.js!./node_modules/vue-loader/lib/index.js??vue-loader-options!./apps/settings/src/components/AdminTwoFactor.vue?vue&type=script&lang=js& 69:0-85 79:25-44

 @ ./apps/settings/src/components/AdminTwoFactor.vue?vue&type=script&lang=js& 1:0-186 1:202-205 1:207-390 1:207-390

 @ ./apps/settings/src/components/AdminTwoFactor.vue 2:0-66 3:0-61 3:0-61 10:2-8

 @ ./apps/settings/src/main-admin-security.js 26:0-61 36:22-36

The problem also occurs in the Tasks app dashboard widget: nextcloud/tasks#2056 Maybe that's easier to debug.

[Pytal]

I've also tried to link nextcloud/vue to server but it fails to build due to a problem with material design icons

Removing these lines https://github.com/nextcloud/server/blob/952acd4d276b3190d23e0597c5e01b1dfc4d72bc/webpack.common.js#L82-L85 fixes the build error @marcoambrosini @raimund-schluessler

After some more tinkering it's seems that floating-vue #2600 may be the actual source of the issue

[PVince81]

I tried removing the v-tooltip row in Actions and now instead of seeing Chromium hanging, I see this:

if it was related only to floating-vue the infinite loop should stop