search

rubin-dp0 / Support

Submit Github Issues related to DP0
MIT License
1 stars 3 forks source link

[BUG] JupyterLab fails to save changes to notebooks, text files #38

Closed duncanwood closed 1 year ago

duncanwood commented 1 year ago

Describe the bug Files fail to save while editing. Both notebooks and text (.py) files, apparently at the same time. Persists until refreshing page, which loses any changes since last successful save.

To Reproduce ???

Expected behavior Expected files to either autosave or successfully manually save.

Screenshots Screen Shot 2022-11-07 at 12 44 15

URL If applicable, cut and paste the URL from your browser at which the issue occurred

Desktop (please complete the following information):

Additional context Has happened at least a couple times, first time lost 4 hours of changes.

MelissaGraham commented 1 year ago

Hi @duncanwood, thanks for submitting this bug report. A few initial follow-up questions to help the team figure this out.

Which directory path are you attempting to save in? I ask because your "notebooks/tutorial-notebooks" directory might be read-only, if it was created on or after Thu Sep 29. Extra info on this:

When you say "persists until refreshing page", are you able to save files again immediately after refreshing the browser page through which you're using the RSP?

Last question is when / how long your Notebook Aspect session was open when you noticed the issue. I ask this because I'm wondering if your session overlapped with a Patch Thursday window.

duncanwood commented 1 year ago

Hi Melissa.

Here are two URLs that failed to save: https://usdf-rsp.slac.stanford.edu/nb/user/duncanw/lab/tree/notebooks/bias-shifts/shifts_2022_11_01-multiprocessing.ipynb https://usdf-rsp.slac.stanford.edu/nb/user/duncanw/lab/tree/repos/lsstcam-bias-shifts/bias_shifts.py The failure to save is intermittent, and relatively infrequent, so I don't think it's related to the above permission error. I'm confused why it would present as a permission error.

In my encounters with the bug, I am able to make edits and save the files immediately after refreshing the page.

I'm not sure about the previous episodes, but the bug happened today, just before posting this report, on a session that I opened this morning. That is assuming "session" means launching the portal with a browser - I haven't spawned a new server in probably a couple weeks. If I should be shutting down the server when I'm done working for the day, for example, then that could be a red flag here.

MelissaGraham commented 1 year ago

Thanks Duncan, I think those details are going to help a lot.

By "session" I did mean a log in, or spawning a new server, with a browser. It is recommended to shut down the server at the end of every day or work session, so that could be part of the issue.

duncanwood commented 1 year ago

Thanks for the info! I thought these were meant to be more persistent so hopefully this is user error...

frossie commented 1 year ago

Hello I notice that you are asking a question about the RSP deployed at the USDF. As a project user you have access to support for that deployment on the #ops-usdf slack channel and the project JIRA system - these Github issues are primarily for users of the science RSP at data.lsst.cloud.

frossie commented 1 year ago

See https://lsstc.slack.com/archives/C027902HL8H/p1667861271885699 on the project slack for a discussion of your issue and any followup