You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support for new status and forceclose server commands (#229)
* add errormonitor also to subtask
* add Dates dep
* add run start and finish timestamps to `File`
* add a "workers" message type that returns worker metadata
* reformat docstring
* remove forced error again
* add tests
* format
* switch to string with full server status via "status" message
* print server timeout and time left
* fix test
* format
* add info about when server started
* formatting
* add changelog
* read QNR_VERSION at compile time
* break after error to not continue with `nothing` as json
* formatting
* throw errors when run/close are called on a notebook that's running
* add tests for notebook run collisions
* remove obsolete concurrency test
* add env to printout
* add changelog about failure behavior
* add `forceclose` server command and tests
* format
* `empty!(channel)` is not available on previous julia versions
* `Base.errormonitor` is also not available on earlier julias
* fix issue when `evaluate!` throws
* fix message
* add forceclose mention to changelog
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## Unreleased
9
9
10
+
### Added
11
+
12
+
- New socket server command `status` that returns a string describing the current server status, including information for each active worker, as well as `forceclose` which is the forced version of `close` that can shut down a worker even if it's currently running [#229](https://github.com/PumasAI/QuartoNotebookRunner.jl/pull/229).
13
+
14
+
### Changed
15
+
16
+
- Socket server commands `run`, `close` and `stop` will error if a file lock is currently held (a file worker is running) instead of waiting potentially a long time for that lock to open. Those locks were always intended only as mutation protection and not a queueing mechanism, they only behaved that way by accident and in case some worker hangs, it's impractical that further `quarto render` commands just add on top of the pile without a message [#229](https://github.com/PumasAI/QuartoNotebookRunner.jl/pull/229).
0 commit comments