Difficulties fails / use websocket to be informed about a new block

It fails due to new block and the node answer a 504 error.

Using Duniterpy may solve this issue as there is a jsonschema check.

For now, an exception could be triggered to avoid breaking the loop.

• add blockchain/difficulties jsonschema in DuniterPy.

assigned to @moul

changed milestone to %0.7.0

changed the description

marked the checklist item add blockchain/difficulties jsonschema in DuniterPy. as completed

A better way would be to use ws/block to get new blocks rather than requesting every time.

unassigned @moul

mentioned in commit 092ce727

mentioned in commit 5f982f04

assigned to @moul

added ~330 enhancement labels

changed title from Difficulties fails to Difficulties fails / use websocket to be informed about a new block

mentioned in commit cef6b3cf

closed

The good thing about the WS solution, is that there is much less traffic made in order to know if a new block arrived.

And, the bad thing about it, is that, in case of network disconnection, the websocket is broken and no error occurs. And the view is not updated.

mentioned in issue #190 (closed)

mentioned in issue #216 (closed)