Skip to content
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

Bug report: mkdocs serve fails due to issue with pygments version #3389

Closed
martinlingstuyl opened this issue Jun 8, 2022 · 0 comments
Closed

Comments

@martinlingstuyl
Copy link
Contributor

Description

When running mkdocs serve after cloning the cli repo, the serve task fails with an error. This is due to the pip packages that are installed. Pygments version 2.12 is automatically installed as a dependency. This version does not work well with mkdocs currently.

The documentation release does work correctly, because the deploy_docs job installs Pygments 2.11: pip install mkdocs-material==7.1.7 pymdown-extensions==9.0 pygments==2.11

The current workaround would be to add pygments 2.11 to the pip requirements in the docker file.

Steps to reproduce

  1. Clone the cli repo in a docker container
  2. run cd docs and mkdocs serve in the terminal
  3. it will throw an error

Expected results

The docs site starts serving

Actual results

the serve task returns an error

Diagnostics

not important here, but let me list the pip packages that are installed instead:
PS /workspaces/cli-microsoft365> pip list
Package Version


click 8.1.3
ghp-import 2.1.0
importlib-metadata 4.11.4
Jinja2 3.1.2
Markdown 3.3.7
MarkupSafe 2.1.1
mergedeep 1.3.4
mkdocs 1.3.0
mkdocs-material 7.1.7
mkdocs-material-extensions 1.0.3
packaging 21.3
pip 20.0.2
Pygments 2.12.0
pymdown-extensions 9.0
pyparsing 3.0.9
python-dateutil 2.8.2
PyYAML 6.0
pyyaml-env-tag 0.1
setuptools 45.2.0
six 1.16.0
watchdog 2.1.8
wheel 0.34.2
zipp 3.8.0

CLI for Microsoft 365 version

5.3

nodejs version

16.15.0

Operating system (environment)

Linux

Shell

zsh

cli doctor

No response

Additional Info

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants