Golem GitHub Digest #11: Easy log collection

This article was first published on null
-----

What’s in store for this Digest?

Golem GitHub Digest #11: Easy log collection

In the previous Golem GitHub Digest (#10) we covered the Alpha 3 release and announcement of the hackathon and Golem Test Harness (Goth).

We’ve been thrilled by the community getting involved in the Golem Hackathon and have had so much amazing feedback and overall positivity, both from requestors/buidl`ers participating in the Golem Online Hackathon and providers joining the Provider Bounties.

So, what’s in the Golem GitHub?

The team added a feature for logging collection to an output file, utilizing Flexi_Logger. You’ll be able to save the logging information in a desired directory by running the command

yagna service run -d YOUR_DIRECTORY or golemsp run -d YOUR_DIRECTORY
For example: yagna service run -d ~/tmp/ya-req

Prior to this, users that wanted to collect logs of stdout/stderr had to do so manually using commands such as yagna service run 2>&1 | tee -a logfile.log. Just as a note, you can still collect more detailed logs using this command:

RUST_LOG=debug,tokio_core=info,tokio_reactor=info,hyper=info golemsp run 2>&1 | tee -a logfile.log

Although be warned that the output file will get large quite quickly so it’s not for the average user!

There was a significant collaboration between developers on the Event API in the Yagna client across a few months that was ready to be merged into the master branch. If you're interested to go into a lower level overview of some of the Yagna Client API specs, you can do so here!

Other than that, improvement mentioned in the previous GitHub update containing some important bug fixes for long computations while using YaJSapi, handling HTTP 408 errors and decreasing API timeouts and sleep duration to fix ECONNRESET error, has been merged. There are many more minor improvements that have been made across almost all repositories.

...

-----
To keep reading, please go to the original article at:
null

Comments (No)

Leave a Reply