diff --git a/_quarto.yml b/_quarto.yml index a242f78..907fa1b 100644 --- a/_quarto.yml +++ b/_quarto.yml @@ -22,7 +22,7 @@ book: - visualizations/visualizations.md - projA1/projA1.md - projA2/projA2.md - - sql/sql.md + # - sql/sql.md sidebar: logo: "data100_logo.png" diff --git a/docs/Data-100-Debugging-Guide.pdf b/docs/Data-100-Debugging-Guide.pdf index 4121a49..aeb6f53 100644 Binary files a/docs/Data-100-Debugging-Guide.pdf and b/docs/Data-100-Debugging-Guide.pdf differ diff --git a/docs/jupyter_datahub/jupyter_datahub.html b/docs/jupyter_datahub/jupyter_datahub.html index dd5f82f..4daef14 100644 --- a/docs/jupyter_datahub/jupyter_datahub.html +++ b/docs/jupyter_datahub/jupyter_datahub.html @@ -212,7 +212,7 @@

M
  • Restart your kernel
  • Rerun your cells
    • -

    Note that you may loose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend saving your work as often as possible.

    +

    Note that you may lose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend saving your work as often as possible.

    If this does not fix the issue, it could be a problem with your code, usually the last cell that executed before your kernel crashed. Double check your logic, and feel free to make a private post on Ed if you’re stuck!

    diff --git a/docs/search.json b/docs/search.json index 97b7dbb..e641303 100644 --- a/docs/search.json +++ b/docs/search.json @@ -46,7 +46,7 @@ "href": "jupyter_datahub/jupyter_datahub.html#my-kernel-died-restarted-or-is-very-slow", "title": "Jupyter / Datahub", "section": "My kernel died, restarted, or is very slow", - "text": "My kernel died, restarted, or is very slow\nJupyterhub connects you to an external container to run your code. That connection could be slow/severed because:\n\nyou haven’t made any changes to the notebook for a while\na cell took too much time to run\na cell took up too many resources to compute\n\nWhen you see a message like this:\n\n\n\n\nEither press the “Ok” button or reload the page\nRestart your kernel\nRerun your cells\n\nNote that you may loose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend saving your work as often as possible.\nIf this does not fix the issue, it could be a problem with your code, usually the last cell that executed before your kernel crashed. Double check your logic, and feel free to make a private post on Ed if you’re stuck!" + "text": "My kernel died, restarted, or is very slow\nJupyterhub connects you to an external container to run your code. That connection could be slow/severed because:\n\nyou haven’t made any changes to the notebook for a while\na cell took too much time to run\na cell took up too many resources to compute\n\nWhen you see a message like this:\n\n\n\n\nEither press the “Ok” button or reload the page\nRestart your kernel\nRerun your cells\n\nNote that you may lose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend saving your work as often as possible.\nIf this does not fix the issue, it could be a problem with your code, usually the last cell that executed before your kernel crashed. Double check your logic, and feel free to make a private post on Ed if you’re stuck!" }, { "objectID": "jupyter_datahub/jupyter_datahub.html#i-cant-edit-a-cell", diff --git a/jupyter_datahub/jupyter_datahub.md b/jupyter_datahub/jupyter_datahub.md index 35ddc05..926328c 100644 --- a/jupyter_datahub/jupyter_datahub.md +++ b/jupyter_datahub/jupyter_datahub.md @@ -38,7 +38,7 @@ When you see a message like this: 2. [Restart your kernel](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#restarting-kernel) 3. [Rerun your cells](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#running-cells) -Note that you may loose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend [saving your work](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#saving-your-notebook) as often as possible. +Note that you may lose some recent work if your kernel restarted when you were in the middle of editing a cell. As such, we recommend [saving your work](https://ds100.org/debugging-guide/jupyter101/jupyter101.html#saving-your-notebook) as often as possible. If this does not fix the issue, it could be a problem with your code, usually the last cell that executed before your kernel crashed. Double check your logic, and feel free to make a private post on Ed if you're stuck!