-
Notifications
You must be signed in to change notification settings - Fork 208
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
fix(SwingSet): silence vat console output during replay #8943
Conversation
Do you mean #8572? |
Adding |
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.
I can confirm that the new logs don't include any output from replaying vats during kernel start:
Sun, 18 Feb 2024 05:14:18 GMT
#21 3.455 2024-02-18T05:14:18.469Z launch-chain: Launching SwingSet kernel
Sun, 18 Feb 2024 05:14:51 GMT
#21 36.36 2024-02-18T05:14:51.377Z block-manager: block 967 begin
Sun, 18 Feb 2024 05:14:51 GMT
#21 36.42 2024-02-18T05:14:51.435Z SwingSet: vat: v1: evaluateBundleCap { manifestBundleRef: { bundleID: 'b1-773d4b972ad4fe803de4947c7f907a85a52fc08e1f6789ba1b853db4e691d10c43847612de281b4567710c92a678cf5ee9fa441d71f81a1f2bc538d6f255c75b' }, manifestGetterName: 'getManifestForUpgradeWallet', vatAdminSvc: Promise [Promise] {} }
I am however wondering if we should add a log entry after cosmic-swingset has finished launching the kernel as right now if things get stuck, it'd be hard to determine if we got stuck in kernel or cosmos land.
fix(SwingSet): silence vat console output during replay
fix(SwingSet): silence vat console output during replay
refs: #8572
Description
Fix a longstanding issue that confuses anybody who restarts a SwingSet kernel. This is not the most elegant, bandwidth-conserving solution as proposed in #8572, but it scratches the annoying itch of stale console output.
Security Considerations
Scaling Considerations
Documentation Considerations
Testing Considerations
Upgrade Considerations