-
-
Notifications
You must be signed in to change notification settings - Fork 528
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
Docbuild workflow broken because furo is too new #34092
Comments
New commits:
|
Commit: |
This comment has been minimized.
This comment has been minimized.
Author: Matthias Koeppe |
comment:3
Also fails with Furo: 2022.04.07 - https://256ca4be1c5defc9de1f43a18a475258c5b19a00--sagemath-tobias.netlify.app/ |
comment:4
Or perhaps something else changed on our side since #33601? |
Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:7
Okay. I have no idea either. It works locally well. |
Reviewer: Kwankyu Lee |
comment:8
Thanks! |
comment:9
This seems to only affect the index page, eg https://8f7574169b6743890bc32b58d9d2afcb4a5d6375--sagemath-tobias.netlify.app/reference/ is working. How is the starting page generated? |
comment:10
Replying to @tobiasdiez:
Indeed. It is generated by |
Changed branch from u/mkoeppe/docbuild_workflow_broken_because_furo_is_too_new to |
As seen for example in
https://8f7574169b6743890bc32b58d9d2afcb4a5d6375--sagemath-tobias.netlify.app/
As a workaround, we back out the use of furo on the docbuild CI.
CC: @tobiasdiez @kwankyu
Component: documentation
Author: Matthias Koeppe
Branch/Commit:
889fcc1
Reviewer: Kwankyu Lee
Issue created by migration from https://trac.sagemath.org/ticket/34092
The text was updated successfully, but these errors were encountered: