-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Conversation
Hey @RafLit , Thanks for submitting the PR
CI supported jobs: [windows-gpu, website, unix-cpu, windows-cpu, centos-cpu, centos-gpu, miscellaneous, unix-gpu, sanity, clang, edge] Note: |
@mxnet-bot run ci [centos-gpu] |
Jenkins CI successfully triggered : [centos-gpu] |
@mxnet-bot run ci [centos-gpu] |
Jenkins CI successfully triggered : [centos-gpu] |
I ran into this issue in my own PR #20876. If you decide you don't want to upgrade Jinja2, I found that adding this requirement:
also solves the issue. |
Can you also remove broken reference to https://ts.gluon.ai/ in docs/python_docs/python/tutorials/getting-started/crash-course/7-use-gpus.md ? |
I see that this upgrade of Jinja2 from 2.11.3 to 3.0.3 indeed solves the import error. But, since the upgrade is in theory a breaking change, is there a way to confirm that Jinja2 continues to work as needed for MXNet? |
You're right - this might need further verification. Adding the MarkupSafe dependency isn't a clean solution either as we don't depend directly on it - Jinja does. So I would see it as a temporary solution to fix the CI problems while we switch to a supported version of Jinja. |
@mxnet-bot run ci [unix-cpu] |
Jenkins CI successfully triggered : [unix-cpu] |
@mxnet-bot run ci [unix-cpu] |
Jenkins CI successfully triggered : [unix-cpu] |
please restart linkcheck |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This upgrade of Jinja2 from 2.11.3 to 3.0.3 is the simplest fix of the import error affecting the website
job. If we learn that the docs are adversely affected, we can try a different fix, like leaving Jinja2 at 2.11.3 and adding a pinned MarkupSafe to 2.0.1. So in summary, LGTM.
Description
The CI is failing due to Jinja version being unsupported:
https://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Fwebsite/detail/PR-20899/1/pipeline/
Pinned the new version of the package to fix the issue.
Related issue:
pallets/jinja#1585