Mermaid diagrams not rendering for multiple documentation pages

[McPatate]

All graphs on this doc page are showing a Mermaid error, as follows:

[utkarsh-singh1]

Hi @McPatate, can you share the link of the doc where the error is showing?

[McPatate]

This is the page, though I see it working on my mobile now:
https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/

I'll check on my laptop tomorrow to see if this is still an issue.

[sftim]

I can't replicate this on my computer. It'd be good to know some reliable steps-to-replicate including what OS, what CPU architecture, and what software.

[sftim]

/area web-development

For now:
/priority awaiting-more-evidence

[McPatate]

Well, I have graphs again, even on the computer it wasn't working on before. No idea what went wrong here, sorry !

I'll let you close the issue.

[utkarsh-singh1]

Hi @McPatate, thanks for your update, I have also checked on my device it seems to be working. It seems it was an error from 3rd party tool mermaid, I am running on intel x86_64 and fedora OS and this error seems to be frequent.

[McPatate]

Firefox, intel x86_64, popOS on my end :)

[sftim]

I can replicate this issue 😞

/triage accepted
/remove-priority awaiting-more-evidence

[sftim]

/retitle Mermaid diagrams not rendering for “Pod Topology Spread Constraints” concept

[chrismetz09]

Cannot replicate using Chrome and FF. Indicates a parser error or sometimes Mermaid can't pick up the configuration if mermaid.js is loaded from cache.

Investigating further.

[hujun-open]

have this issue with FF on windows 10;
chrome works fine though

[utkarsh-singh1]

Mostly, I have faced this issue on both Firefox and chrome when network connection is relatively slow.

[SergiyKolesnikov]

After reloading the page, the diagrams are displayed correctly. Firefox 107.0.1 (64-bit), Debian 11.

[sftim]

/retitle Mermaid diagrams not rendering for multiple documentation pages

[shurup]

I can confirm this issue on my Firefox/Linux, too. It appears when I open this page for the first time. After I do a refresh (F5), this issue disappears and I can see the actual charts.

While investigating this issue, I found squidfunk/mkdocs-material#3232 and — funny enough — there I found a reference to #31960 with the same investigation. Shouldn't we close all duplicated issues regarding broken Mermaid diagrams?

[sftim]

/triage duplicate

[sftim]

/remove-triage accepted

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sftim]

This is a duplicate report

/close not-planned

[k8s-ci-robot]

@sftim: Closing this issue, marking it as "Not Planned".

In response to this:

This is a duplicate report

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.