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.

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

"Request Re-execution" button #497

Open
u8sand opened this issue Jan 19, 2021 · 0 comments
Open

"Request Re-execution" button #497

u8sand opened this issue Jan 19, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@u8sand
Copy link
Collaborator

u8sand commented Jan 19, 2021

Because output is cached and because we live in an imperfect world -- it's possible that some external API was unavailable coincidentally during an execution, in this case it may be necessary to re-execute the appyter. Currently I can manually mark an appyter to be re-executed by removing metadata.nbexecute part of the instance's notebook, but it may make sense to allow users to request a re-execution to mitigate permanently broken appyter instances.

Because some appyters can simply be flawed -- we can't just assume errors mean we should re-execute; in any case, the current recommended way to deal with these situations is to submit an issue and let us investigate manually.

@u8sand u8sand added the enhancement New feature or request label Jan 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant