"Docs markdown link couldn't be resolved" infinite loop on build or start

[Southclaws]

🐛 Bug Report

I upgraded to 66 recently for our docs site and since we're doing translations that are in-progress, there are a lot of broken links (because translators copy the english, change the text and keep the markdown - so links and images, etc) which is fine, I don't want translators to remove links then re-add them later it'll just get confusing. I have set onBrokenLink to ignore but the warning messages still appear.

The issue is whenever I do a build or run the dev server the console just gets inundated with:

Docs markdown link couldn't be resolved: ...

I thought there were just a lot of links so I left it running for 10 minutes and it's still printing! It seems to be stuck in an infinite loop as it prints the same thing over and over. It opens the browser but the page never loads.

I'm thinking it's related to the type of TTY though because on Vercel it builds fine (ignoring the other error) https://vercel.com/openmultiplayer/wiki/4wphzsm3e could it be related to that progress bar graphic that appears in the terminal?

It seems to be TTY related, if I pipe the output to a file then the server starts up fine:

wiki on  master [$✘] via ⬢ v12.18.3 took 2m48s
❯ npm start > logs
Docs markdown link couldn't be resolved: (NPC:StartRecordingPlayback.md) in E:\Work\open.mp\wiki\docs\scripting\callbacks\OnRecordingPlaybackEnd.md for version current
Docs markdown link couldn't be resolved: (NPC:StopRecordingPlayback.md) in E:\Work\open.mp\wiki\docs\scripting\callbacks\OnRecordingPlaybackEnd.md for version current
[BABEL] Note: The code generator has deoptimised the styling of E:\Work\open.mp\wiki\docs\scripting\resources\animations.md as it exceeds the max of 500KB.
Docs markdown link couldn't be resolved: (../resources/weaponskills#skill-levels.md) in E:\Work\open.mp\wiki\docs\scripting\functions\SetPlayerSkillLevel.md for version current
Docs markdown link couldn't be resolved: (../scripting/functions/GetPlayerDrunkLevel.md) in E:\Work\open.mp\wiki\docs\scripting\functions\SetPlayerDrunkLevel.md for version current
Docs markdown link couldn't be resolved: (GetVehicleRotation.md) in E:\Work\open.mp\wiki\docs\scripting\functions\GetVehicleZAngle.md for version current
Docs markdown link couldn't be resolved: (GetVehicleRotation.md) in E:\Work\open.mp\wiki\docs\scripting\functions\GetVehiclePos.md for version current
Docs markdown link couldn't be resolved: (../tutorials/colorfix.md) in E:\Work\open.mp\wiki\docs\scripting\functions\GetPlayerColor.md for version current
Docs markdown link couldn't be resolved: (UpdatePlayer3DTextLabel.md) in E:\Work\open.mp\wiki\docs\scripting\functions\Attach3DTextLabelToVehicle.md for version current
Docs markdown link couldn't be resolved: (UpdatePlayer3DTextLabel.md) in E:\Work\open.mp\wiki\docs\scripting\functions\Attach3DTextLabelToPlayer.md for version current

And it stops printing there, the browser opens as expected and I can browse/edit the site and it reloads live.

Have you read the Contributing Guidelines on issues?

Yes

To Reproduce

I think just having a ton of 404s triggers it, clone this and build it: https://github.com/openmultiplayer/wiki/

Your Environment

Does not occur on Vercel but occurs locally on Windows.

[slorber]

Hi,

I'm not sure what's the error that you are reporting here?
Is it just the infinite loop, or is it also the error message?
Because I see your Vercel deployment also has this error message.

As far as I understand it is a cosmetic terminal issue, and is not blocking you from building your site right?

Note: I'm working on proper i18n support right now, will soon look for early adopters to onboard

[Southclaws]

It seems to be stuck in an infinite loop as it prints the same thing over and over. It opens the browser but the page never loads.

The page on localhost never loads, but if I pipe output to a file, it works fine. I think it's detecting if it's writing to a TTY and if it is, redrawing the entire terminal because normally there's a progress bar for the client and server build.

Here's a video: https://i.imgur.com/NhLGNZs.mp4

Notice how the scroll bar starts to grow just for this progress, each render adds more lines to the terminal:

As soon as the 404 errors start to print, the buffer starts to fill up. If I leave it running, it just does this constantly.

It might not actually be an "infinite loop" though, it might just be the constant writes to stdout slowing down the process so it just takes an insanely long time to actually build and serve content.

---

On the topic of translations, we'll be very interested in trialing that new feature, we've been anticipating its release! We have about 700 pages in each language and our number of languages is growing constantly so it's a big test-base!

[slorber]

Seems to work for me on macos with yarn install && yarn start

Not working for me, running wiki locally makes loop for 3 hours straight.
The problem keep repeating itself, idk why.

[slorber]

Can you both share your env?
Both on Windows?

I'm on windows.
Using cmd.

your env?

What do you mean?

[slorber]

your env?
What do you mean?

Anything useful to share. But knowing you are both on windows is a good first step 👍

Unfortunately, I don't have windows, but if someone can help figure this problem out that would be nice