STATS messages are being sent twice for some reason #29

Closed
opened 2017-02-27 20:06:33 +01:00 by mikegioia · 2 comments
mikegioia commented 2017-02-27 20:06:33 +01:00 (Migrated from github.com)

It looks like STATS messages are being streamed to the client 2x instead of once. The error does not seem to be in the JSON Parsing but instead it could be related to the stream receiving two SIGUSR2s or the message being duplicated to the server process. This is a very complicated one.

It looks like STATS messages are being streamed to the client 2x instead of once. The error does not seem to be in the JSON Parsing but instead it could be related to the stream receiving two SIGUSR2s or the message being duplicated to the server process. This is a very complicated one.
mikegioia commented 2018-07-23 03:35:35 +02:00 (Migrated from github.com)

This could be the message sending "null" for active before it starts the next folder:

image

If that's the case, active=null might not necessarily need to be send while scanning the folders.

This could be the message sending "null" for active before it starts the next folder: ![image](https://user-images.githubusercontent.com/387937/43052830-f121513c-8ddd-11e8-8a17-5813f7741e45.png) If that's the case, active=null might not necessarily need to be send while scanning the folders.
mikegioia commented 2018-07-23 20:29:56 +02:00 (Migrated from github.com)

This is resolved now in commit 4cacada

This is resolved now in commit 4cacada
Sign in to join this conversation.
No description provided.