-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test(ses-ava): option to use t.log #2101
test(ses-ava): option to use t.log #2101
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice; this is definitely an improvement!
a0ce2a3
to
2458798
Compare
87982e5
to
7a7ff1a
Compare
caf11d6
to
f1b5d40
Compare
This is now actually ready for review. Enough has changed since you approved that I request new approvals. (I have no idea how to clear the old ones, or even if that's possible.) Note that this PR now depends on, and is staged on, #2107, so that would need to get reviewed and merged before this one could. Please review that one too. It should be straightforward. |
7f8b02c
to
92e34c9
Compare
92e34c9
to
4edbbbd
Compare
Converting to Draft. See #2107 (comment) |
8e3c1c6
to
37f2093
Compare
37f2093
to
650e719
Compare
Closing in favor of #2109 |
#2109 is sufficiently different that it needs a from-scratch review. |
Staged on #2107
closes: #XXXX
refs: Agoric/agoric-sdk#8965 (comment) #611 #647 #891 #1467 #2107 Agoric/agoric-sdk#8662 #1798
Description
Alter ses-ava so that it ultimately uses
t.log
to log errors or rejections from thet => {...}
function.Security Considerations
As of this PR, ses-ava will import from
console-tools.js
, as exported byses
in #2107 . We must ensure that this arrangement does not accidentally make these powers available to non-privileged code executing in constructed (non-start) compartments. See "Security Considerations" at #2107Scaling Considerations
none
Documentation Considerations
none
Testing Considerations
The whole point. Since this PR changes only the logging of errors or rejections from the
t => {...}
function, it will not by itself clean up console output in general. But at least it will cause these error reports to appear at the "right" place in the overall console output.Compatibility Considerations
Mostly none.
If there are programs post-processing our voluminous console output, they might need to change. However,
Upgrade Considerations
Nothing breaking. Nothing newsworthy as of this PR by itself.
*BREAKING*:
in the commit message with migration instructions for any breaking change.NEWS.md
for user-facing changes.