-
Notifications
You must be signed in to change notification settings - Fork 631
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
Jupyter-book build errors #2611
Comments
@da5nsy, love the We can add a room at an upcoming Collaboration Cafe to talk more about it, maybe at the one on the 20th if you're interested & available. I'm beginning to wonder if there should be an ongoing infrastructure room at Collab Cafes, or a separate recurring call. -- Also flagging that I spoke to @aldenc today about how we can build better issue templates around reporting bugs & infrastructure issues. She's opening a room at Collab Cafe to do some user testing tomorrow, so if you're free to attend tomorrow, maybe you could speak with her about it? 😊 |
Thanks @aleesteele! I'm not certain that I'll try to swing by tomorrow! |
I would strongly suggest that once all these issues are fixed, change the CI so the jobs would fail with any errors (or even better, any warnings) raised during the build. |
@bsipocz - How would we go about doing this? |
There is a nitpicky mode for sphinx, but I'll have to check how that can be applied to this setup (as opposed to library API docs building where it works out of the box) I'll try to find some time later this week for a small pr. |
Updated output (formatting edited for clarity):
Lots of bugs fixed 🎉 |
From the original list we're now down to:
(and of course some others have been introduced in the meantime 😭) |
Oh, this is a great improvement! The remaining question then to whether they should be orphans, removed, or linked somewhere? |
😅 |
Big thank you to @JimMadge who handled some of the gnarlier warnings on this list. |
Well done, congrats folks! |
Getting some fun* errors currently in building the jupyter book locally.
* where "fun" = not serious but we should work through them.
I'll put the raw output here and then we can spin out individual issues/PRs for each one as we see fit.
Here's the raw output:
Individual Issues:
journal
field to supress jupyter-book warning #2621communication/peer-review/peer-review-overview
#2673The text was updated successfully, but these errors were encountered: