The eval runner now handles SIGTERM as well as interrupt, and reports which ended the run.
What's wrong with this entry?
The eval CLI now handles SIGTERM as well as SIGINT, printing its own message and latching whichever signal arrived first so the run can report how it ended.
- Eval temporary directories are resolved through realpath before use.
- The HTML report relabels the judge evidence block to explain that an image appears there as a description of what was sent.
Terminated — finishing up…
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
plugin evalnow tells you when a nearby plugin is not being loadedBoth mention eval
-
v2.1.235
--eval-diron the eval command, with warnings that name the fixBoth mention eval
-
v2.1.235
Eval setup refuses directories it cannot vouch for
Both mention eval