Skip to content
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

feat: reintroduce anylogger as the console endowment #1285

Merged
merged 2 commits into from
Jul 11, 2020

Conversation

michaelfig
Copy link
Member

The agoric start console output regressed and is currently very noisy. This PR makes things nice and tidy again.

Looks like the anylogger-scoped console baby got thrown out with the SES1 bathwater. 😉

BTW, If you ever want to crank up the debug level (to see the console.debug messages), use:

# for running ag-solo directly:
DEBUG=agoric ag-solo start ...
# for running under CLI:
agoric -vvv start

This doesn't change any semantics unless anylogger is configured
by the entry point.

Making SwingSet quieter when it's running as ag-solo is the goal.
@michaelfig michaelfig added the SwingSet package: SwingSet label Jul 10, 2020
@michaelfig michaelfig requested review from warner and FUDCo July 10, 2020 22:39
@michaelfig michaelfig self-assigned this Jul 10, 2020
Copy link
Contributor

@FUDCo FUDCo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

At some point I'm going want to go over the anylogger stuff with you to understand how to use the anylogger initialization controls to control kdebug instead of using an ad hoc mechanism for the latter. I filed this as ticket #1286 so I don't forget.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SwingSet package: SwingSet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants