Opened 10 years ago
Closed 10 months ago
#11644 closed defect (invalid)
Published worksheets do not get update automatically in flask notebook
Reported by: | pong | Owned by: | jason, mpatel, was |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | notebook | Keywords: | |
Cc: | chapoton | Merged in: | |
Authors: | Reviewers: | ||
Report Upstream: | Reported upstream. Developers acknowledge bug. | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
The "Automatically re-publish when changes are made" feature does not work in flask notebook.
Change History (8)
comment:1 Changed 8 years ago by
- Milestone changed from sage-5.11 to sage-5.12
comment:2 Changed 7 years ago by
- Milestone changed from sage-6.1 to sage-6.2
comment:3 Changed 7 years ago by
- Milestone changed from sage-6.2 to sage-6.3
comment:4 Changed 7 years ago by
- Milestone changed from sage-6.3 to sage-6.4
comment:5 Changed 7 years ago by
comment:6 Changed 7 years ago by
- Report Upstream changed from N/A to Reported upstream. Developers acknowledge bug.
Upstream at https://github.com/sagemath/sagenb/issues/246
comment:7 Changed 10 months ago by
- Cc chapoton added
- Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
- Status changed from new to needs_review
Proposing to close all sagenb tickets as outdated, so that all remaining open tickets in the notebook component are about the Jupyter notebook.
comment:8 Changed 10 months ago by
- Resolution set to invalid
- Status changed from needs_review to closed
Note: See
TracTickets for help on using
tickets.
This is not quite correct. They do show up, but one has to save the worksheet first (not necessarily quit). Maybe we could just add some verbiage making this clear in the instructions
Pong, if you see this, let me know if you think this is an acceptable compromise.