Closed neverett closed 4 days ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 60.98%. Comparing base (
bd2f9a8
) to head (0cb167e
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@davidmirror-ops looks like docs tests are failing because the MMCloud plugin example page has a 404ing link. Here's a PR to remove and redirect the MMCloud plugin pages -- once it's merged, I can update the branch in this PR and the tests should pass.
@cosmicBboy I'm able to generate mermaid diagrams locally with the changes in this PR, but docs tests are failing with command '/home/docs/.asdf/shims/mmdc' cannot be run (needed for mermaid output), check the mermaid_cmd setting
.
That is the location mmdc
ends up installed in on the build server (see the readthedocs build logs), so I'm not sure what else to try -- any ideas?
As far I as I can tell the mmdc
path will be different in readthedocs build env from the githin actions monodocs env.
I think the monodocs build GH workflow needs to be updated: https://github.com/flyteorg/flyte/blob/c10346d5bc07e37783c277f6d3bede301ae3ad99/flytectl/.github/workflows/monodocs_build.yml#L2
And then in conf.py
the path needs to be set as an environment variable.
However, weird thing is that even in the readthedocs preview the mermaid diagrams aren't showing up: https://flyte--5467.org.readthedocs.build/en/5467/deployment/configuration/auth_appendix.html
trying out this smaller configuration change: https://github.com/flyteorg/flyte/pull/5498
Closing since this was fixed in https://github.com/flyteorg/flyte/pull/5498
Why are the changes needed?
Closes https://github.com/flyteorg/flyte/issues/4864
What changes were proposed in this pull request?
npm install -g @mermaid-js/mermaid-cli
during build processCheck all the applicable boxes
Related PRs
https://github.com/flyteorg/flyte/pull/5373
Docs link
TK