Adam Mizerski

you can find this also in #925

`asyncio.get_event_loop()` gives you always the same global event loop. The `close` method (see [documentation](https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.AbstractEventLoop.close)) > is idempotent and irreversible. No other methods should be called after this one. Probably what...

https://en.wikipedia.org/wiki/Lossless_JPEG ;)

There is a unit test, that mocks `Client` and adds `concent_variant` to it. Maybe using `Mock(spec=Client)` would help.

Hypothesis: Before starting hyperg, golem tries to connect to potentially existing one. This might be undefined behaviored by twisted, if called from thread.

I'm digging it out of the grave of oblivion. @golemfactory/ya-sdk Maybe it's possible for ya*api to ask yagna for current gas price and estimate required gas before starting computation?

In case of Task API tasks, `TaskComputerAdapter._handle_computation_results` calls `send_results` or `send_task_failed` on `self._task_server`. Then calls `self._finished_cb()`, which is `Node._try_shutdown`. The problem is that methods on `TaskServer` are sending messages (and...

In case of old tasks, the problem is the same. Messages are queued in `self.results_to_send` and `Node._try_shutdown` kicks in.

It seems to be triggered by errors in simple-transfer, for example: ``` ERROR [actix_http::response] Internal Server Error: IO(Os { code: 113, kind: Other, message: "Host is unreachable" }) ``` ```...

This happens also for other calls, get_gntb_balance in this case. ``` 2019-12-10 11:01:05 ERROR golem Service Error: Traceback (most recent call last): File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner self.run() File...