Constantly verify that the Shiny app is working
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 123
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Checking only at the beginning is not enough. Errors can happen after the initialization.
It would be good to have an app_abort() if the app has shut down. This check should happen for every call made to the shiny app / shiny server.
cc @cpsievert
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the code that makes calls to the Shiny app or Shiny server and the existing initialization check. Trace how a shutdown is currently detected, then determine how the check can cover every call and how an app_abort() failure should be observed. Done means calls after shutdown consistently abort, with tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100