-
Notifications
You must be signed in to change notification settings - Fork 228
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
agoric start output is super noisy #571
Comments
PR #730 introduces @DavidBruant please reopen if this issue is closed but not satisfactory. |
It's much better indeed, thanks! I'm reopening The current output is: agoric: start: rm -rf _agstate/agoric-servers/dev
agoric: start: /home/david/projects/agoric-sdk/packages/cosmic-swingset/bin/ag-solo init dev --egresses=fake
agoric: start: /home/david/projects/agoric-sdk/packages/cosmic-swingset/bin/ag-solo set-fake-chain --role=two_chain --delay=0 myFakeGCI
agoric: start: /home/david/projects/agoric-sdk/packages/cosmic-swingset/bin/ag-solo start --role=two_client
web: Listening on 127.0.0.1:8000
launch-chain: Launching SwingSet kernel
start: swingset running
outbound: invoking deliverator; 1 new messages for myFakeGCI
outbound: invoking deliverator; 4 new messages for myFakeGCI
outbound: invoking deliverator; 2 new messages for myFakeGCI
outbound: invoking deliverator; 5 new messages for myFakeGCI
outbound: invoking deliverator; 3 new messages for myFakeGCI
outbound: invoking deliverator; 2 new messages for myFakeGCI
outbound: invoking deliverator; 0 new messages for myFakeGCI Out of all of this, my guess is that the only lines that may be of interest to someone working with agoric-cli but not on it are: agoric: start: rm -rf _agstate/agoric-servers/dev # because it reflects --reset
web: Listening on 127.0.0.1:8000 # because it's some form of indication that some http server is ready to receive requests Depending on priority, maybe i'll do the rest |
I'd recommend to keep the
Those are important to indicate round trips (i.e. activity that might be useful to optimise). Also the logs should still show the HTTP/WebSocket connections, which is another indication of activity. Maybe just a single-line indicator of |
@DavidBruant can you check again on the status of this issue? |
I wonder whether this is crucial or nice-to-have information But for non-blockchain and fake-blockchain cases, i feel like this should be hidden by default and shown with an opt-in (like |
I think this is good enough for now |
Console output for working "agoric start"
Instant reaction:

I understand all of this is probably useful for debugging purposes, but could it be hidden behind an opt-in (like a
--debug
flag)?I would have expected something like (intention, not real content):
$ agoric start ✓ Local Agoric Node started ✓ Local Wallet server started, ready to receive requests at http://localhost:5555/ ✓ Local Dapp server started, ready to receive requests at http://localhost:8888/ Everything is ok and ready! Keep this terminal open somewhere In order to deploy a contract, you need to open a new terminal
The text was updated successfully, but these errors were encountered: