Stop watching and building Rmd if server is stopped #488
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will fix when the of behavior observed in #481
I believe we should stop watching for modification and auto building Rmd is server has been stopped by the user, using
server_stop()opts$get("served_dirs")seems the right option to check. However, that require setting the first value earlier the first time, that is not inon.exit. Is it safe to modify this ? Seems like the change does the same as before while usingokay = FALSE, thenokay = TRUEIf not, we could also use
opts$get("pids")which is set to NULL instop_serveror another option if necessary.Feel free to change if that is not okay