BufferStock REMARK notebook hangs on first code cell

[sbenthall]

The first executable code cell in the BufferStock REMARK notebook (linked here from the git repo submodule):
https://github.com/llorracc/BufferStockTheory/blob/5ccb22b72cb9fd46245b8954459ce5f44ab3c7ea/Code/Python/BufferStockTheory.ipynb

hangs upon execution of the first code cell.

Command line output from Jupyter lab indicates a 404 connection to the local JupyterLab endpoint.

[I 11:13:19.120 LabApp] Saving file at /BufferStockTheory.ipynb
[W 11:13:19.120 LabApp] Saving untrusted notebook BufferStockTheory.ipynb
[W 11:13:22.667 LabApp] 404 GET /metrics?1572275602658 (127.0.0.1) 3.85ms referer=http://localhost:8888/lab
[W 11:13:27.679 LabApp] 404 GET /metrics?1572275607671 (127.0.0.1) 3.81ms referer=http://localhost:8888/lab
[W 11:13:32.689 LabApp] 404 GET /metrics?1572275612681 (127.0.0.1) 3.58ms referer=http://localhost:8888/lab
[W 11:13:37.700 LabApp] 404 GET /metrics?1572275617692 (127.0.0.1) 3.82ms referer=http://localhost:8888/lab
[W 11:13:42.711 LabApp] 404 GET /metrics?1572275622702 (127.0.0.1) 3.84ms referer=http://localhost:8888/lab

[llorracc]

Strange. I think I've only looked at this using a regular jupyter notebook, not jupyter lab. Does it work for you with jupyter?

…

On Mon, Oct 28, 2019 at 11:19 AM Sebastian Benthall < ***@***.***> wrote: The first executable code cell in the BufferStock REMARK notebook (linked here from the git repo submodule): https://github.com/llorracc/BufferStockTheory/blob/5ccb22b72cb9fd46245b8954459ce5f44ab3c7ea/Code/Python/BufferStockTheory.ipynb hangs upon execution of the first code cell. Command line output from Jupyter lab indicates a 404 connection to the local JupyterLab endpoint. [I 11:13:19.120 LabApp] Saving file at /BufferStockTheory.ipynb [W 11:13:19.120 LabApp] Saving untrusted notebook BufferStockTheory.ipynb [W 11:13:22.667 LabApp] 404 GET /metrics?1572275602658 (127.0.0.1) 3.85ms referer=http://localhost:8888/lab [W 11:13:27.679 LabApp] 404 GET /metrics?1572275607671 (127.0.0.1) 3.81ms referer=http://localhost:8888/lab [W 11:13:32.689 LabApp] 404 GET /metrics?1572275612681 (127.0.0.1) 3.58ms referer=http://localhost:8888/lab [W 11:13:37.700 LabApp] 404 GET /metrics?1572275617692 (127.0.0.1) 3.82ms referer=http://localhost:8888/lab [W 11:13:42.711 LabApp] 404 GET /metrics?1572275622702 (127.0.0.1) 3.84ms referer=http://localhost:8888/lab — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AAKCK72HNWDYZVB77PE3CO3QQ37HPA5CNFSM4JF3WAJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HUZOGTA>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKCK73A4EUHHMGDRTXGMLLQQ37HPANCNFSM4JF3WAJA> .

-- - Chris Carroll

[MridulS]

Seems like a jupyterlab error jupyterlab/jupyterlab#6884 <jupyterlab/jupyterlab#6884>

…

On 28-Oct-2019, at 8:50 PM, Christopher Llorracc Carroll ***@***.***> wrote: Strange. I think I've only looked at this using a regular jupyter notebook, not jupyter lab. Does it work for you with jupyter? On Mon, Oct 28, 2019 at 11:19 AM Sebastian Benthall < ***@***.***> wrote: > The first executable code cell in the BufferStock REMARK notebook (linked > here from the git repo submodule): > > https://github.com/llorracc/BufferStockTheory/blob/5ccb22b72cb9fd46245b8954459ce5f44ab3c7ea/Code/Python/BufferStockTheory.ipynb > > hangs upon execution of the first code cell. > > Command line output from Jupyter lab indicates a 404 connection to the > local JupyterLab endpoint. > > [I 11:13:19.120 LabApp] Saving file at /BufferStockTheory.ipynb > [W 11:13:19.120 LabApp] Saving untrusted notebook BufferStockTheory.ipynb > [W 11:13:22.667 LabApp] 404 GET /metrics?1572275602658 (127.0.0.1) 3.85ms referer=http://localhost:8888/lab > [W 11:13:27.679 LabApp] 404 GET /metrics?1572275607671 (127.0.0.1) 3.81ms referer=http://localhost:8888/lab > [W 11:13:32.689 LabApp] 404 GET /metrics?1572275612681 (127.0.0.1) 3.58ms referer=http://localhost:8888/lab > [W 11:13:37.700 LabApp] 404 GET /metrics?1572275617692 (127.0.0.1) 3.82ms referer=http://localhost:8888/lab > [W 11:13:42.711 LabApp] 404 GET /metrics?1572275622702 (127.0.0.1) 3.84ms referer=http://localhost:8888/lab > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#18?email_source=notifications&email_token=AAKCK72HNWDYZVB77PE3CO3QQ37HPA5CNFSM4JF3WAJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HUZOGTA>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAKCK73A4EUHHMGDRTXGMLLQQ37HPANCNFSM4JF3WAJA> > . > -- - Chris Carroll — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=ABI5RFHOFLZQLDVKO4RFSJ3QQ37NFA5CNFSM4JF3WAJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECNIKIY#issuecomment-546997539>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABI5RFCDURB6DYLRCR2DWHLQQ37NFANCNFSM4JF3WAJA>.

[sbenthall]

Confirmed: it works with the regular jupyter notebook

[MridulS]

not a REMARK issue

[llorracc]

Could one of you add a test in the first code line of the source document that determines whether it's being run as a Jupyter notebook or in JupyterLab?

Pseudocode:

if [running environment is JupyterLab]:
      print a fatal error message like 'As of 20191031, this notebook does not work with JupyterLab because of a JupyterLab problem, jupyterlab/jupyterlab#6884'
      halt execution

[MridulS]

I’m able to run this in jupyterlab, it probably has something to do with the local env of Seb

…

On 01-Nov-2019, at 1:06 AM, Christopher Llorracc Carroll ***@***.***> wrote: Could one of you add a test in the first code line of the source document that determines whether it's being run as a Jupyter notebook or in JupyterLab? Pseudocode: if [running environment is JupyterLab]: print a fatal error message like 'As of 20191031, this notebook does not work with JupyterLab because of a JupyterLab problem, jupyterlab/jupyterlab#6884 <jupyterlab/jupyterlab#6884>' halt execution exit (or whatever halts execution of the notebook (BufferStockTheory-Problems-And-Solutions.ipynb) in the private master repo from which the public one is constructed? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=ABI5RFFWGIXZHTVHU2WIGLTQRMXS3A5CNFSM4JF3WAJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECY72EQ#issuecomment-548535570>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABI5RFFVK3SH4ATWSQDSL33QRMXS3ANCNFSM4JF3WAJA>.

[llorracc]

Oh, OK, then cancel the request. On Thu, Oct 31, 2019 at 3:37 PM Mridul Seth <notifications@github.com> wrote:

…

I’m able to run this in jupyterlab, it probably has something to do with the local env of Seb > On 01-Nov-2019, at 1:06 AM, Christopher Llorracc Carroll < ***@***.***> wrote: > > Could one of you add a test in the first code line of the source document that determines whether it's being run as a Jupyter notebook or in JupyterLab? > > Pseudocode: > if [running environment is JupyterLab]: > print a fatal error message like 'As of 20191031, this notebook does not work with JupyterLab because of a JupyterLab problem, jupyterlab/jupyterlab#6884 < jupyterlab/jupyterlab#6884>' > halt execution > > exit (or whatever halts execution of the notebook > (BufferStockTheory-Problems-And-Solutions.ipynb) in the private master repo from which the public one is constructed? > > — > You are receiving this because you modified the open/close state. > Reply to this email directly, view it on GitHub < #18?email_source=notifications&email_token=ABI5RFFWGIXZHTVHU2WIGLTQRMXS3A5CNFSM4JF3WAJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECY72EQ#issuecomment-548535570>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABI5RFFVK3SH4ATWSQDSL33QRMXS3ANCNFSM4JF3WAJA >. > — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AAKCK76CMSDX6HV2OBP53ELQRMXZNA5CNFSM4JF3WAJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECY76WY#issuecomment-548536155>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKCK75YAAI5UYSHUQNTYC3QRMXZNANCNFSM4JF3WAJA> .

-- - Chris Carroll

[sbenthall]

Confirmed I was able to fix this on my end.
Sorry for the confusion

[llorracc]

Confusion is good - because other people have been there too. Let’s find a way to help other people who make the same mistake. Add a line testing for ipython, per my prior msg.

On Thu, Oct 31, 2019 at 15:47 Sebastian Benthall ***@***.***> wrote: Confirmed I was able to fix this on my end. Sorry for the confusion — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AAKCK7ZFOENQLIZP4FFAEO3QRMY65A5CNFSM4JF3WAJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECZA6HA#issuecomment-548540188>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKCK7ZKBCAWOAFRUBVMHGLQRMY65ANCNFSM4JF3WAJA> .

-- Sent from Gmail Mobile

[sbenthall]

Add a line testing for ipython, per my prior msg.

Forgive me, but are you referring to issue #19 here?

This issue #18 is about JupyterLab, but it was an issue with my JupyterLab environment.

[llorracc]

Yes, this was about #19