Repository navigation
release: 0.3.1 - #3
Merged
Merged
Conversation
- **`instrument verify` says how a run ended when the program raised, too.** The harness said its own ending only for a program that returned, so a program that ended on an exception before a line of it was seen — a script that does not compile, a module whose bytecode another Python wrote — left no ending behind, and the command answered `4` and « the verification did not run to a conclusion »: « the control plane could not be asked », about a plane that had answered. It now answers `7`, « the verifier never saw the program's own code start », naming the exception the program ended on; the program's own traceback is still printed. For the same reason, a program that caught the abort of an unreadable chain and then raised an exception of its own now gets the chain's ending (`4`, the transport's own problem code and sentence) rather than the generic one. - The contract and the boundary move to 0.3.1, released with this client. - A `python` the shell cannot find is refused as before (64), and the refusal now names the `python3` on the same PATH. - Every program the README and the quickstart run is spelled `python3 …`; the quickstart starts the daemon again before section 7, shows a closed epoch verified, and says how long a rejection stands. Signed-off-by: fredaime <frederic.aime@gmail.com>
This file contains hidden or 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.
instrument verifysays how a run ended when the program raised, too. The harness saidits own ending only for a program that returned, so a program that ended on an exception before
a line of it was seen — a script that does not compile, a module whose bytecode another Python
wrote — left no ending behind, and the command answered
4and « the verification did not runto a conclusion »: « the control plane could not be asked », about a plane that had answered.
It now answers
7, « the verifier never saw the program's own code start », naming theexception the program ended on; the program's own traceback is still printed. For the same
reason, a program that caught the abort of an unreadable chain and then raised an exception of
its own now gets the chain's ending (
4, the transport's own problem code and sentence) ratherthan the generic one.
pythonthe shell cannot find is refused as before (64), and the refusal now namesthe
python3on the same PATH.python3 …; thequickstart starts the daemon again before section 7, shows a closed epoch verified,
and says how long a rejection stands.