SHOWSTOPPER BUG: wiki does not load (Insufficient resources)#547

My team has been trying out YNAW however we’ve run into a showstopper. 2 members of my team (including myself, who is the owner of the wiki) - cannot load the wiki.

The page loads, and the content just spins. I’m a developer, so I when Ctrl+Shift+J in Chrome I get about 2000+ 403 forbidden, and about a minute or two later, I start getting thousands and thousands of:

Failed to load resource: net::ERR_INSUFFICIENT_RESOURCES - which is crazy since this PC has 32 GB of RAM on it. And our wiki isn’t THAT big. Maybe 50 documents.

…actually, just an idea came to me, since I’m the owner, I wonder if I might have a circular reference of a subfolder that’s referencing another folder up the tree somewhere? Could that cause this error?

It seems like this is possible in Google Drive: https://stackoverflow.com/questions/43793895/is-it-possible-for-google-drives-folder-structure-to-contain-a-loop - does YNAW detect this?

Unfortunately I don’t have a way to test this if this is the culprit. But it does seem to make sense. Although, the errors eventually did stop. Like, Chrome, just gave up.

Thanks Mark, I can reproduce this.
I’ll have an update soon.

@Mark Mikulec same here, and your looping link above seems to be the culprit for me. Working on hunting down the loops on my end to see if that fixes it before Grant does!

[Edit: it did!]

Ok, moved some things around and I’m back to just loading – I can’t find if I’ve somehow added another loop with shortcuts to set it off, but we’re not able to access anything via YNAW.

A fix has gone out for this.

If a shortcut references a folder that is above it’s hierarchy in the wiki, it will not render the shortcut or it’s children to avoid the runaway recursive problem.

I’ve also set a limit for wiki folder depth of 1000 in case there is something I’m missing.

I’m monitoring this limit with error tracking. I can remove it over time or make it higher if needed.

@Cameron Dunn @Mark Mikulec if you get a chance could you confirm this is fixed on your end.