Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Published worksheets do not get update automatically in flask notebook #11644

Closed
wypong mannequin opened this issue Aug 3, 2011 · 4 comments
Closed

Published worksheets do not get update automatically in flask notebook #11644

wypong mannequin opened this issue Aug 3, 2011 · 4 comments
Assignees
@jasongrout @williamstein @qed777
Labels
c: user interface r: invalid t: bug

Comments

@wypong
Copy link
Mannequin

wypong mannequin commented Aug 3, 2011

The "Automatically re-publish when changes are made" feature does not work in flask notebook.

Upstream: Reported upstream. Developers acknowledge bug.

CC: @fchapoton

Component: notebook

Issue created by migration from https://trac.sagemath.org/ticket/11644
@wypong wypong mannequin added this to the sage-5.11 milestone Aug 3, 2011
@wypong wypong mannequin added c: user interface labels Aug 3, 2011
@wypong wypong mannequin assigned jasongrout, qed777 and williamstein Aug 3, 2011
@jdemeyer jdemeyer modified the milestones: sage-5.11, sage-5.12 Aug 13, 2013
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@kcrisman
Copy link
Member

comment:5

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

Automatically re-publish when changes are made (after saving)

Pong, if you see this, let me know if you think this is an acceptable compromise.

@kcrisman
Copy link
Member

comment:6

Upstream at sagemath/sagenb#246

@kcrisman
Copy link
Member

Upstream: Reported upstream. Developers acknowledge bug.

@mkoeppe
Copy link
Member

mkoeppe commented Aug 18, 2020

comment:7

Proposing to close all sagenb tickets as outdated, so that all remaining open tickets in the notebook component are about the Jupyter notebook.

@mkoeppe mkoeppe removed this from the sage-6.4 milestone Aug 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jasongrout jasongrout

@williamstein williamstein

@qed777 qed777

Labels
c: user interface r: invalid t: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@jasongrout @williamstein @kcrisman @jdemeyer @fchapoton @mkoeppe