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

Refine waitForServer() logging #89

Merged
merged 2 commits into from
Jul 3, 2015

Conversation

dexX7
Copy link
Member

@dexX7 dexX7 commented Jul 3, 2015

As described in #74 (comment):

  • status messages are logged only once, if new or updated
  • status messages are logged as INFO
  • begin and end of waiting is logged as DEBUG

dexX7 added 2 commits July 3, 2015 18:40
- status messages are logged only once, if new or updated
- status messages are logged as `INFO`
- begin and end of waiting is logged as `DEBUG`
msgilligan added a commit that referenced this pull request Jul 3, 2015
Refine waitForServer() logging
@msgilligan msgilligan merged commit c84266c into OmniLayer:master Jul 3, 2015
@@ -83,7 +84,7 @@ public Boolean waitForServer(int timeout) throws JsonRPCException {
status = e.getMessage();
} catch (JsonRPCStatusException e) {
// If server is in "warmup" mode, e.g. validating/parsing the blockchain...
if ( e.jsonRPCCode == -28) {
if (e.jsonRPCCode == -28) {
Copy link
Member

Choose a reason for hiding this comment

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

We should probably start defining error codes symbolically, but this is fine for now.

(I realize that I put in the -28 and you just removed a space)

@dexX7
Copy link
Member Author

dexX7 commented Jul 3, 2015

Thanks for the merge! Now the output looks like this:

https://ci.omni.foundation/job/omni-mainnet-consensus/44/console

Even though there are quite a few messages (it's printed every 30 seconds), it's very convenient to watch the progress, or spot, whether the parsing stalled.

@msgilligan
Copy link
Member

I'm going to move that Setup comparison height1 = message into a logger, so we can get rid of the STANDARD_OUT and STANDARD_ERROR switching...

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

Successfully merging this pull request may close these issues.

2 participants