You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently classify notebooks in notebooks.toml into notebooks_that_submit_jobs and notebooks_no_mock. If the notebook is left off, it defaults to our third category of notebooks that do not submit jobs at all.
It's easy to not realize when you should be changing notebooks.toml. After talking to some of the content team, we think it'd be better to explicitly categorize every notebook in notebooks.toml.
Tasks:
Create a new category like notebooks_no_jobs
Error if a notebook is not categorized with a helpful message saying what file to modify and explaining the three available categories
Feedback from Kevin: We should try to clarify what we mean by the notebook being "too big".
The text was updated successfully, but these errors were encountered:
This script now has some non-trivial logic to do with skipping, mocking,
writing, etc. This refactor combines the `Config` and args objects so we
have a single point of decision making. You may find it easier to review
each commit separately.
This is prework for #1319.
---------
Co-authored-by: Eric Arellano <14852634+Eric-Arellano@users.noreply.github.com>
Closes#1319.
* The script no longer uses `all-notebooks` as a glob pattern to search,
instead it just iterates through the list of filepaths
* Added a check to detect unclassified notebooks
---------
Co-authored-by: Eric Arellano <14852634+Eric-Arellano@users.noreply.github.com>
We currently classify notebooks in
notebooks.toml
intonotebooks_that_submit_jobs
andnotebooks_no_mock
. If the notebook is left off, it defaults to our third category of notebooks that do not submit jobs at all.It's easy to not realize when you should be changing
notebooks.toml
. After talking to some of the content team, we think it'd be better to explicitly categorize every notebook innotebooks.toml
.Tasks:
notebooks_no_jobs
Feedback from Kevin: We should try to clarify what we mean by the notebook being "too big".
The text was updated successfully, but these errors were encountered: