-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PUML not working on CI deployment (Teammates) due to lack of graphviz #1903
Comments
Putting some details of the investigation that I have done here for reference:
|
Thanks for the investigation so far @tlylt |
Yes @damithc, I just tested it and it seems like as long as we do install java and Graphviz on CI (which is doable), then the images will be generated accordingly. I will drop a message in teammates' repo to ask if they wish to have this done (modifying the CI script) or hosting the images (the current changes by @kaixin-hc) I think on our end we do need to put in a note in our deploy section, to inform users that if they are using puml diagrams, especially if they do continuous integration, they will have to ensure that their CI environment satisfy the required dependencies (Java and Graphviz). |
Great. Thanks for the quick action @tlylt |
If I may add, the fact that this does not fail the CI build is itself a red flag. |
Related to #1863. In short, we've been (again presumably - I don't have context) prioritising usability of @tlylt referring to #1245 (comment) as well, we can also aim to keep the current behaviour for
Iirc this was discussed and acknowledged verbally (or maybe in some PR 👀) among us 2 years back. The rationale (not too big of an issue) is as we aim to test only the file paths we supply to the puml process. Having the puml images error out would still generate error images, which is plenty sufficient for verifying said file paths. (we assume puml would do its things correctly, and leave testing that to the puml team) In the case of graphviz errors, we assume the author has knowledge that it is required, which we've also documented quite clearly since the original PR by @alyip98. https://markbind.org/userGuide/components/imagesAndDiagrams.html#diagrams |
Based on the work done on this issue + the two original issues that flagged now being fixed, I think this issue can be closed now. If anyone else has any thoughts on this, let me know : ) |
Should be ok to close. The problem of not throwing an error when plantuml diagrams generation fails can be discussed in #1863 |
Please confirm that you have searched existing issues in the repo
Yes, I have searched the existing issues
Any related issues?
See Teammates issue and reposense issue
Tell us about your environment
Live Deployed version
MarkBind version
3.1.1
What did you do? Describe the bug
After deployment, puml diagrams seem to be missing and have thrown an error.
Steps to reproduce
Unable to reproduce manually on local serve or on manual deployment on a forked branch
Expected behavior
.puml diagrams should display
Actual behavior
No response
Anything else?
Hypothesis: This is related to CI, and building .puml files during CI is the problem. CI may not have graphviz.
Observation: For MarkBind docs puml diagrams, we actually never use the tags within the website. Instead, we have saved the .puml as equivalent .pngs, and displayed the .png instead (see
diagrams.md
) Found this PR #917 explaining the reason is to avoid installing graphviz.Graphviz related .puml errors: #1459, and the reposense: #1406 Replace images as PUML diagrams PR leading to #916 which was marked as fixed. Also consider reposense 1427 on the PUML diagrams not rendering
Suggestions? What should we do about this issue?
The text was updated successfully, but these errors were encountered: