NATS cluster: tons of Error reading from client: invalid character '"' after top-level value

Hello, I'm trying to start introducing NATS as a microservice communication protocol on mesos. I'm using mesos master nodes as seed nodes for NATS and each mesos slave runs gnatsd pointing to those seed nodes. I observed a peculiar flood of messages once I start/restart a bunch of mesos slaves (and gnatsd as it runs on those slaves).
This is small extract from gnats log:

[7723] 2016/05/11 16:42:37.015681 [ERR] <IP_ADDRESS>:7222 - rid:96441 - Route Error {"server_id":"OWN6ITRHRzycwYnuZVpESI","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[7723] 2016/05/11 16:42:37.016299 [ERR] <IP_ADDRESS>:48898 - rid:96291 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.017219 [ERR] <IP_ADDRESS>:7222 - rid:96502 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.018002 [ERR] <IP_ADDRESS>:7222 - rid:91454 - Route Error 'Parser Error'
[7723] 2016/05/11 16:42:37.018738 [ERR] <IP_ADDRESS>:35941 - rid:96520 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.021777 [ERR] <IP_ADDRESS>:23365 - rid:96456 - Route Error 'Parser Error'
[7723] 2016/05/11 16:42:37.022236 [ERR] <IP_ADDRESS>:28619 - rid:96325 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.025008 [ERR] <IP_ADDRESS>:7222 - rid:96523 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.026082 [ERR] <IP_ADDRESS>:7222 - rid:96535 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.027167 [ERR] <IP_ADDRESS>:3391 - rid:96527 - Route Error 'Parser Error'
[7723] 2016/05/11 16:42:37.028311 [ERR] <IP_ADDRESS>:56649 - rid:96437 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.028988 [ERR] <IP_ADDRESS>:57138 - rid:96524 - Route Error 'Parser Error'
[7723] 2016/05/11 16:42:37.029456 [ERR] <IP_ADDRESS>:7222 - rid:96522 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.035386 [ERR] <IP_ADDRESS>:7222 - rid:96442 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.055451 [ERR] <IP_ADDRESS>:3716 - rid:96492 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.057689 [ERR] <IP_ADDRESS>:7222 - rid:96543 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.075498 [ERR] <IP_ADDRESS>:7222 - rid:96436 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.407565 [ERR] <IP_ADDRESS>:7222 - rid:96540 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.411138 [ERR] <IP_ADDRESS>:29337 - rid:96486 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.413138 [ERR] <IP_ADDRESS>:65103 - rid:96241 - Route Error 'Parser Error'
[7723] 2016/05/11 16:42:37.413265 [ERR] <IP_ADDRESS>:28632 - rid:96539 - Route Error 'Parser Error'
[7723] 2016/05/11 16:42:37.424351 [ERR] <IP_ADDRESS>:50446 - rid:96334 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.431253 [ERR] <IP_ADDRESS>:35303 - rid:96376 - Route Error 'Parser Error'
[7723] 2016/05/11 16:42:37.458023 [ERR] <IP_ADDRESS>:38285 - rid:96521 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.470157 [ERR] <IP_ADDRESS>:3758 - rid:96564 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.471790 [ERR] <IP_ADDRESS>:13872 - rid:96479 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.496984 [ERR] <IP_ADDRESS>:7222 - rid:96624 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.497997 [ERR] <IP_ADDRESS>:15451 - rid:96669 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.500422 [ERR] <IP_ADDRESS>:7863 - rid:96530 - Route Error {"server_id":"OWN6ITRHRzycwYnuZVpESI","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[7723] 2016/05/11 16:42:37.527624 [ERR] <IP_ADDRESS>:57330 - rid:96500 - Error reading from client: invalid character '"' after top-level value
[7723] 2016/05/11 16:42:37.572838 [ERR] <IP_ADDRESS>:14535 - rid:96519 - Route Error 'Parser Error'

I tried using -DV flag for more info but I could not find anything related so I decided not to include it here as it's super verbose.
As a side effect noticed that sometimes (rarely) some of the gnatsd on mesos slaves keep running but are not connected to the rest of the cluster. Another case is when I restart gnatsd on one of the slave and it produces a cascading flood of logs like above. While observing /routez monitoring endpoint I can see "num_rutes" going up and down as if propagating routes cycles other live gnatsd instances.
Configuration files for seed nodes (routes changes depending on server):
port: 4222
http_port: 8222

cluster {
  host: '<IP_ADDRESS>'
  port: 7222

  routes = [
    nats-route://mesos-master-2:7222
    nats-route://mesos-master-3:7222
  ]
}

Configuration for slave nodes:
port: 4222

cluster {
  host: '<IP_ADDRESS>' # Managed by startup script
  port: 7222

  routes = [
    nats-route://mesos-master-1:7222
    nats-route://mesos-master-2:7222
    nats-route://mesos-master-3:7222
  ]
}

I'm not certain if there is something wrong with the configuration files or my idea to run gnatsd on each mesos slave (for mesh cluster) is not the best use case for NATS.
If you need more details - let me know. I can alter configuration and deploy test code if needed.

Quick question: are all your servers of the same version?

@kozlovic Yes, they're all on the same gnatsd 0.8.0 version.

Although verbose, we may be able to use the -DV log information could be helpful to the NATS team. I believe something other than a route connection is connection to the route port.

I find this suspicious:

@derekcollison No problem. Do you know a good place to place logs so that I would not pollute this thread?

@kozlovic I have them:
Start <IP_ADDRESS>:
[825] 2016/05/11 16:42:07.266892 [INF] Starting nats-server version 0.8.0
[825] 2016/05/11 16:42:07.266980 [INF] Listening for route connections on <IP_ADDRESS>:7222
[825] 2016/05/11 16:42:07.267068 [INF] Listening for client connections on <IP_ADDRESS>:4222
[825] 2016/05/11 16:42:07.267107 [INF] Server is ready
[825] 2016/05/11 16:42:07.273272 [ERR] <IP_ADDRESS>:18598 - rid:6 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.274221 [ERR] <IP_ADDRESS>:54777 - rid:7 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.276166 [ERR] <IP_ADDRESS>:59077 - rid:5 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.278241 [ERR] <IP_ADDRESS>:40404 - rid:15 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.278591 [ERR] <IP_ADDRESS>:63776 - rid:25 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.280708 [ERR] <IP_ADDRESS>:7222 - rid:21 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.281130 [ERR] <IP_ADDRESS>:37587 - rid:17 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.575228 [ERR] <IP_ADDRESS>:7222 - rid:163 - Error reading from client: invalid     character '"' after top-level value
[825] 2016/05/11 16:42:07.582954 [ERR] <IP_ADDRESS>:7222 - rid:1 - Error reading from client: invalid        character '"' after top-level value
[825] 2016/05/11 16:42:07.586072 [ERR] <IP_ADDRESS>:7222 - rid:23 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.586184 [ERR] <IP_ADDRESS>:7222 - rid:164 - Route Error {"server_id":              "c1WavpAMoGOCUEVmLngLIi","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false, "ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://10. 21.0.19:7222/"}Parser Error'
[825] 2016/05/11 16:42:07.589882 [ERR] <IP_ADDRESS>:61213 - rid:12 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.590191 [ERR] <IP_ADDRESS>:2264 - rid:9 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.591689 [ERR] <IP_ADDRESS>:59078 - rid:47 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.593101 [ERR] <IP_ADDRESS>:7222 - rid:190 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.602562 [ERR] <IP_ADDRESS>:56800 - rid:195 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.604988 [ERR] <IP_ADDRESS>:7222 - rid:215 - Error reading from client: invalid     character '"' after top-level value
[825] 2016/05/11 16:42:07.610009 [ERR] <IP_ADDRESS>:7222 - rid:220 - Error reading from client: invalid     character '"' after top-level value
[825] 2016/05/11 16:42:07.610132 [ERR] <IP_ADDRESS>:7222 - rid:200 - Error reading from client: invalid     character '"' after top-level value
[825] 2016/05/11 16:42:07.610699 [ERR] <IP_ADDRESS>:7222 - rid:194 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.611747 [ERR] <IP_ADDRESS>:7222 - rid:2 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.613129 [ERR] <IP_ADDRESS>:7222 - rid:198 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.613394 [ERR] <IP_ADDRESS>:37595 - rid:72 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.613860 [ERR] <IP_ADDRESS>:37992 - rid:28 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.614004 [ERR] <IP_ADDRESS>:7222 - rid:3 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.614672 [ERR] <IP_ADDRESS>:53147 - rid:13 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.614710 [ERR] <IP_ADDRESS>:7222 - rid:205 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.615725 [ERR] <IP_ADDRESS>:7222 - rid:201 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.616128 [ERR] <IP_ADDRESS>:43072 - rid:242 - Route Error 'Parser Error'
[825] 2016/05/11 16:42:07.619119 [ERR] <IP_ADDRESS>:7222 - rid:230 - Error reading from client: invalid     character '"' after top-level value

Start of <IP_ADDRESS>:
[827] 2016/05/11 16:38:58.583587 [INF] Starting nats-server version 0.8.0
[827] 2016/05/11 16:38:58.583860 [INF] Listening for route connections on <IP_ADDRESS>:7222
[827] 2016/05/11 16:38:58.583986 [INF] Listening for client connections on <IP_ADDRESS>:4222
[827] 2016/05/11 16:38:58.584031 [INF] Server is ready
[827] 2016/05/11 16:40:36.577628 [ERR] <IP_ADDRESS>:7222 - rid:11 - Error reading from client: invalid      character '"' after top-level value
[827] 2016/05/11 16:42:06.708679 [ERR] <IP_ADDRESS>:48910 - rid:4 - Error reading from client: invalid       character '"' after top-level value
[827] 2016/05/11 16:42:06.710426 [ERR] <IP_ADDRESS>:33255 - rid:3 - Route Error {"server_id":                "g3nC2596EJUmiX1bVdc6ht","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false, "ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://10. 21.0.37:7222/"}Parser Error'
[827] 2016/05/11 16:42:06.710972 [ERR] <IP_ADDRESS>:37140 - rid:7 - Route Error {"server_id":                "g3nC2596EJUmiX1bVdc6ht","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false, "ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://10. 21.0.37:7222/"}Parser Error'
[827] 2016/05/11 16:42:06.711062 [ERR] <IP_ADDRESS>:7222 - rid:1 - Route Error {"server_id":                 "g3nC2596EJUmiX1bVdc6ht","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false, "ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://10. 21.0.37:7222/"}Parser Error'
[827] 2016/05/11 16:42:07.803115 [ERR] <IP_ADDRESS>:7222 - rid:90 - Error reading from client: invalid      character '"' after top-level value
[827] 2016/05/11 16:42:07.804890 [ERR] <IP_ADDRESS>:7222 - rid:44 - Error reading from client: invalid      character '"' after top-level value
[827] 2016/05/11 16:42:07.823386 [ERR] <IP_ADDRESS>:11095 - rid:150 - Error reading from client: invalid    character '"' after top-level value
[827] 2016/05/11 16:42:07.825418 [ERR] <IP_ADDRESS>:7222 - rid:35 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.825743 [ERR] <IP_ADDRESS>:7222 - rid:22 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.826140 [ERR] <IP_ADDRESS>:7222 - rid:75 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.826573 [ERR] <IP_ADDRESS>:7222 - rid:79 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.828017 [ERR] <IP_ADDRESS>:7222 - rid:151 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.829675 [ERR] <IP_ADDRESS>:7222 - rid:124 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.829686 [ERR] <IP_ADDRESS>:37218 - rid:63 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.832440 [ERR] <IP_ADDRESS>:7222 - rid:52 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.837844 [ERR] <IP_ADDRESS>:33399 - rid:166 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.838225 [ERR] <IP_ADDRESS>:7222 - rid:66 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.838384 [ERR] <IP_ADDRESS>:7222 - rid:77 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.839216 [ERR] <IP_ADDRESS>:37323 - rid:180 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.840155 [ERR] <IP_ADDRESS>:7222 - rid:38 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.840434 [ERR] <IP_ADDRESS>:7222 - rid:168 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.841818 [ERR] <IP_ADDRESS>:63860 - rid:17 - Route Error 'Parser Error'
[827] 2016/05/11 16:42:07.841942 [ERR] <IP_ADDRESS>:7222 - rid:196 - Error reading from client: invalid      character '"' after top-level value

I think you could just attach the logs by dragging into the comment box.

Any chance that one of the server is trying to connect to the client port 4222? Could you check all configs?
I am seeing a server reporting the "invalid character" error when one of the server connects to another server to the client port, instead of the route port. In debug, I see that the routes are recreated constantly from the server with wrong config with a "Detected duplicate remote route" error message.

@derekcollison Attached log <IP_ADDRESS>.verbose.zip
@kozlovic The config file (second one) in my first post is what all 30 slaves are using (it's a template and the only part that's dynamic is # Managed by startup script one).
Just a random thought but looking at the verbose log could it be that because all 30 (+3 seed) instances are restarting/dropping connection for some reason and that causes data to be just partially available on the wire?

Thanks for the log, would you please provide the log for <IP_ADDRESS>?
Are you able to have a successful deploy or is it always end-up like this? If you try to bring one server at a time, do you still get this issue? Thanks!

@awdrius I think I was able to reproduce the issue with "invalid character" with lots of servers (with correctly connecting to the route port). I will keep you posted. Thanks again for the report!

@kozlovic That's good news (not that it's good it happens (-. ). Let me know if you need any help.

Will do. In the meantime, if you want to experiment and see if works better deploying one server at a time...

@awdrius I have made some progress, so don't waste your time experimenting. I should get an update on the next step by the end of the day.

So I tried getting a similar behavior while bringing slaves online one by one and got the same thing.
I started gnatsd on all three mesos masters to act as a seed nodes. Checking /routez confirmed that they all are fine. Then I got one of slaves gnatsd process online with no issues and nor errors in any of the logs. Once I started the second gnatsd process on a second slave all three initial nodes started complaining:
master 1 (<IP_ADDRESS>):
[24765] 2016/05/11 21:29:33.755202 [INF] Starting nats-server version 0.8.0
[24765] 2016/05/11 21:29:33.755737 [INF] Starting http monitor on <IP_ADDRESS>:8222
[24765] 2016/05/11 21:29:33.755861 [INF] Listening for route connections on <IP_ADDRESS>:7222
[24765] 2016/05/11 21:29:33.756193 [INF] Listening for client connections on <IP_ADDRESS>:4222
[24765] 2016/05/11 21:29:33.756220 [INF] Server is ready
[24765] 2016/05/11 21:36:28.481178 [ERR] <IP_ADDRESS>:39347 - rid:1 - Error reading from client: invalid character '"' after top-level value
[24765] 2016/05/11 21:36:28.481353 [ERR] <IP_ADDRESS>:46756 - rid:3 - Error reading from client: invalid character '"' after top-level value

master 2 (<IP_ADDRESS>):
[24602] 2016/05/11 21:29:44.071109 [INF] Starting nats-server version 0.8.0
[24602] 2016/05/11 21:29:44.071746 [INF] Starting http monitor on <IP_ADDRESS>:8222
[24602] 2016/05/11 21:29:44.072095 [INF] Listening for route connections on <IP_ADDRESS>:7222
[24602] 2016/05/11 21:29:44.072290 [INF] Listening for client connections on <IP_ADDRESS>:4222
[24602] 2016/05/11 21:29:44.072445 [INF] Server is ready
[24602] 2016/05/11 21:36:28.481620 [ERR] <IP_ADDRESS>:50655 - rid:3 - Error reading from client: invalid character '"' after top-level value
[24602] 2016/05/11 21:36:28.482195 [ERR] <IP_ADDRESS>:7222 - rid:1 - Route Error {"server_id":"fVnT72z3FJHk3AwTKrrBda","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'

master 3 (<IP_ADDRESS>):
[24694] 2016/05/11 21:29:52.892725 [INF] Starting nats-server version 0.8.0
[24694] 2016/05/11 21:29:52.893268 [INF] Starting http monitor on <IP_ADDRESS>:8222
[24694] 2016/05/11 21:29:52.893499 [INF] Listening for route connections on <IP_ADDRESS>:7222
[24694] 2016/05/11 21:29:52.893670 [INF] Listening for client connections on <IP_ADDRESS>:4222
[24694] 2016/05/11 21:29:52.893821 [INF] Server is ready
[24694] 2016/05/11 21:36:28.481586 [ERR] <IP_ADDRESS>:7222 - rid:1 - Error reading from client: invalid character '"' after top-level value
[24694] 2016/05/11 21:36:28.482670 [ERR] <IP_ADDRESS>:7222 - rid:2 - Route Error {"server_id":"fVnT72z3FJHk3AwTKrrBda","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'

Slave 1 (in order of start) (<IP_ADDRESS>):
[11497] 2016/05/11 21:36:00.793712 [INF] Starting nats-server version 0.8.0
[11497] 2016/05/11 21:36:00.793786 [INF] Listening for route connections on <IP_ADDRESS>:7222
[11497] 2016/05/11 21:36:00.793849 [INF] Listening for client connections on <IP_ADDRESS>:4222
[11497] 2016/05/11 21:36:00.793880 [INF] Server is ready

Slave 2 (<IP_ADDRESS>):
[12341] 2016/05/11 21:36:28.478798 [INF] Starting nats-server version 0.8.0
[12341] 2016/05/11 21:36:28.478926 [INF] Listening for route connections on <IP_ADDRESS>:7222
[12341] 2016/05/11 21:36:28.478996 [INF] Listening for client connections on <IP_ADDRESS>:4222
[12341] 2016/05/11 21:36:28.479030 [INF] Server is ready

Summary: it looks like after starting second slave all seed gnatsd instances started complaining about first slave.
Out of curiosity I started gnatsd on a third slave and got the following:
master 1 (<IP_ADDRESS>):
[24765] 2016/05/11 21:29:33.755202 [INF] Starting nats-server version 0.8.0
[24765] 2016/05/11 21:29:33.755737 [INF] Starting http monitor on <IP_ADDRESS>:8222
[24765] 2016/05/11 21:29:33.755861 [INF] Listening for route connections on <IP_ADDRESS>:7222
[24765] 2016/05/11 21:29:33.756193 [INF] Listening for client connections on <IP_ADDRESS>:4222
[24765] 2016/05/11 21:29:33.756220 [INF] Server is ready
[24765] 2016/05/11 21:36:28.481178 [ERR] <IP_ADDRESS>:39347 - rid:1 - Error reading from client: invalid character '"' after top-level value
[24765] 2016/05/11 21:36:28.481353 [ERR] <IP_ADDRESS>:46756 - rid:3 - Error reading from client: invalid character '"' after top-level value
[24765] 2016/05/11 21:47:38.718733 [ERR] <IP_ADDRESS>:16890 - rid:6 - Error reading from client: invalid character '"' after top-level value
[24765] 2016/05/11 21:47:38.719716 [ERR] <IP_ADDRESS>:39484 - rid:7 - Error reading from client: invalid character '"' after top-level value
[24765] 2016/05/11 21:47:38.720231 [ERR] <IP_ADDRESS>:58279 - rid:5 - Error reading from client: invalid character '"' after top-level value
[24765] 2016/05/11 21:47:38.720289 [ERR] <IP_ADDRESS>:46880 - rid:8 - Error reading from client: invalid character '"' after top-level value

master 2 (<IP_ADDRESS>):
[24602] 2016/05/11 21:29:44.071109 [INF] Starting nats-server version 0.8.0
[24602] 2016/05/11 21:29:44.071746 [INF] Starting http monitor on <IP_ADDRESS>:8222
[24602] 2016/05/11 21:29:44.072095 [INF] Listening for route connections on <IP_ADDRESS>:7222
[24602] 2016/05/11 21:29:44.072290 [INF] Listening for client connections on <IP_ADDRESS>:4222
[24602] 2016/05/11 21:29:44.072445 [INF] Server is ready
[24602] 2016/05/11 21:36:28.481620 [ERR] <IP_ADDRESS>:50655 - rid:3 - Error reading from client: invalid character '"' after top-level value
[24602] 2016/05/11 21:36:28.482195 [ERR] <IP_ADDRESS>:7222 - rid:1 - Route Error {"server_id":"fVnT72z3FJHk3AwTKrrBda","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24602] 2016/05/11 21:47:38.718027 [ERR] <IP_ADDRESS>:22859 - rid:7 - Error reading from client: invalid character '"' after top-level value
[24602] 2016/05/11 21:47:38.719066 [ERR] <IP_ADDRESS>:14872 - rid:14 - Error reading from client: invalid character '"' after top-level value
[24602] 2016/05/11 21:47:38.720212 [ERR] <IP_ADDRESS>:7222 - rid:9 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24602] 2016/05/11 21:47:38.720505 [ERR] <IP_ADDRESS>:21311 - rid:5 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24602] 2016/05/11 21:47:38.720606 [ERR] <IP_ADDRESS>:7222 - rid:8 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24602] 2016/05/11 21:47:39.722032 [ERR] <IP_ADDRESS>:7222 - rid:15 - Error reading from client: invalid character '"' after top-level value
[24602] 2016/05/11 21:47:39.725843 [ERR] <IP_ADDRESS>:7222 - rid:19 - Error reading from client: invalid character '"' after top-level value

master 3 (<IP_ADDRESS>):
[24694] 2016/05/11 21:29:52.892725 [INF] Starting nats-server version 0.8.0
[24694] 2016/05/11 21:29:52.893268 [INF] Starting http monitor on <IP_ADDRESS>:8222
[24694] 2016/05/11 21:29:52.893499 [INF] Listening for route connections on <IP_ADDRESS>:7222
[24694] 2016/05/11 21:29:52.893670 [INF] Listening for client connections on <IP_ADDRESS>:4222
[24694] 2016/05/11 21:29:52.893821 [INF] Server is ready
[24694] 2016/05/11 21:36:28.481586 [ERR] <IP_ADDRESS>:7222 - rid:1 - Error reading from client: invalid character '"' after top-level value
[24694] 2016/05/11 21:36:28.482670 [ERR] <IP_ADDRESS>:7222 - rid:2 - Route Error {"server_id":"fVnT72z3FJHk3AwTKrrBda","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24694] 2016/05/11 21:47:38.718988 [ERR] <IP_ADDRESS>:5827 - rid:6 - Error reading from client: invalid character '"' after top-level value
[24694] 2016/05/11 21:47:38.719930 [ERR] <IP_ADDRESS>:50747 - rid:7 - Error reading from client: invalid character '"' after top-level value
[24694] 2016/05/11 21:47:38.720570 [ERR] <IP_ADDRESS>:28509 - rid:5 - Error reading from client: invalid character '"' after top-level value
[24694] 2016/05/11 21:47:38.720817 [ERR] <IP_ADDRESS>:7222 - rid:8 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'

Slave 1 (in order of start) (<IP_ADDRESS>):
[11497] 2016/05/11 21:36:00.793712 [INF] Starting nats-server version 0.8.0
[11497] 2016/05/11 21:36:00.793786 [INF] Listening for route connections on <IP_ADDRESS>:7222
[11497] 2016/05/11 21:36:00.793849 [INF] Listening for client connections on <IP_ADDRESS>:4222
[11497] 2016/05/11 21:36:00.793880 [INF] Server is ready
[11497] 2016/05/11 21:47:38.719426 [ERR] <IP_ADDRESS>:7222 - rid:5 - Error reading from client: invalid character '"' after top-level value
[11497] 2016/05/11 21:47:38.719929 [ERR] <IP_ADDRESS>:7222 - rid:3 - Error reading from client: invalid character '"' after top-level value
[11497] 2016/05/11 21:47:38.720598 [ERR] <IP_ADDRESS>:7222 - rid:1 - Error reading from client: invalid character '"' after top-level value
[11497] 2016/05/11 21:47:38.720739 [ERR] <IP_ADDRESS>:7222 - rid:2 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[11497] 2016/05/11 21:47:39.723485 [ERR] <IP_ADDRESS>:32509 - rid:10 - Route Error 'Parser Error'
[11497] 2016/05/11 21:47:39.727319 [ERR] <IP_ADDRESS>:49989 - rid:11 - Route Error 'Parser Error'

Slave 2 (<IP_ADDRESS>):
[12341] 2016/05/11 21:36:28.478798 [INF] Starting nats-server version 0.8.0
[12341] 2016/05/11 21:36:28.478926 [INF] Listening for route connections on <IP_ADDRESS>:7222
[12341] 2016/05/11 21:36:28.478996 [INF] Listening for client connections on <IP_ADDRESS>:4222
[12341] 2016/05/11 21:36:28.479030 [INF] Server is ready
[12341] 2016/05/11 21:47:38.718309 [ERR] <IP_ADDRESS>:7222 - rid:1 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[12341] 2016/05/11 21:47:38.719268 [ERR] <IP_ADDRESS>:7222 - rid:2 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[12341] 2016/05/11 21:47:38.719331 [ERR] <IP_ADDRESS>:7222 - rid:3 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[12341] 2016/05/11 21:47:38.719726 [ERR] <IP_ADDRESS>:31937 - rid:4 - Route Error {"server_id":"xn4pmtvOp6Wqr1fJyCKUVf","version":"0.8.0","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[12341] 2016/05/11 21:47:39.722514 [ERR] <IP_ADDRESS>:7222 - rid:8 - Route Error 'Parser Error'
[12341] 2016/05/11 21:47:39.722536 [ERR] <IP_ADDRESS>:60497 - rid:11 - Route Error 'Parser Error'
[12341] 2016/05/11 21:47:39.723487 [ERR] <IP_ADDRESS>:7222 - rid:13 - Error reading from client: invalid character '"' after top-level value

Slave 3 (<IP_ADDRESS>):
[18121] 2016/05/11 21:47:38.711869 [INF] Starting nats-server version 0.8.0
[18121] 2016/05/11 21:47:38.711968 [INF] Listening for route connections on <IP_ADDRESS>:7222
[18121] 2016/05/11 21:47:38.712065 [INF] Listening for client connections on <IP_ADDRESS>:4222
[18121] 2016/05/11 21:47:38.712107 [INF] Server is ready
[18121] 2016/05/11 21:47:38.717567 [ERR] <IP_ADDRESS>:7222 - rid:1 - Route Error 'Parser Error'
[18121] 2016/05/11 21:47:39.720371 [ERR] <IP_ADDRESS>:44548 - rid:11 - Error reading from client: invalid character '"' after top-level value

@kozlovic Good to know. I didn't get notified about your message so posted that nice wall of text (-.

@awdrius That's fine, sorry for the trouble. I think I have identified the issue and submitted PR #271 that should address this.

Awesome. I'm happy to be helpful.

@awdrius Feel free to pull from master, 0.8.1 and let us know if the issue is corrected. Thanks again for the feedback.

@derekcollison Cloned repo and build. Binary report version 0.8.0beta2 but I can confirm that fix is in place by checking changed source file. Then deployed it to 3 seed nodes and 30 slave nodes. I can confirm that I do not see a bunch of cascading errors anymore and /routez reports 32 routes and that number is no longer jumping. I do still see errors in log files.
master-1 (<IP_ADDRESS>):
[25159] 2016/05/11 23:41:27.370025 [INF] Starting nats-server version 0.8.0.beta2
[25159] 2016/05/11 23:41:27.370431 [INF] Starting http monitor on <IP_ADDRESS>:8222
[25159] 2016/05/11 23:41:27.370534 [INF] Listening for route connections on <IP_ADDRESS>:7222
[25159] 2016/05/11 23:41:27.370577 [INF] Listening for client connections on <IP_ADDRESS>:4222
[25159] 2016/05/11 23:41:27.370599 [INF] Server is ready
[25159] 2016/05/11 23:49:40.747766 [ERR] <IP_ADDRESS>:49219 - rid:3 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:49:40.749337 [ERR] <IP_ADDRESS>:41825 - rid:1 - Route Error {"server_id":"EB2RwClf6LY74kezPOkhqy","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[25159] 2016/05/11 23:51:43.149713 [ERR] <IP_ADDRESS>:24511 - rid:9 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:43.150688 [ERR] <IP_ADDRESS>:42011 - rid:10 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:43.151365 [ERR] <IP_ADDRESS>:20564 - rid:16 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:43.152081 [ERR] <IP_ADDRESS>:7222 - rid:5 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:43.152907 [ERR] <IP_ADDRESS>:41455 - rid:15 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:43.153529 [ERR] <IP_ADDRESS>:7222 - rid:29 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:43.160929 [ERR] <IP_ADDRESS>:7222 - rid:8 - Route Error {"server_id":"oqqYaosRcPn6D3nDfTdkQn","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[25159] 2016/05/11 23:51:43.162364 [ERR] <IP_ADDRESS>:5080 - rid:28 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:43.162937 [ERR] <IP_ADDRESS>:20651 - rid:33 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.545920 [ERR] <IP_ADDRESS>:27129 - rid:17 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.545978 [ERR] <IP_ADDRESS>:7222 - rid:18 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.546243 [ERR] <IP_ADDRESS>:60706 - rid:21 - Route Error 'Parser Error'
[25159] 2016/05/11 23:51:45.547856 [ERR] <IP_ADDRESS>:64994 - rid:70 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.547972 [ERR] <IP_ADDRESS>:46548 - rid:71 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.549205 [ERR] <IP_ADDRESS>:7222 - rid:72 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.549877 [ERR] <IP_ADDRESS>:10177 - rid:34 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.552317 [ERR] <IP_ADDRESS>:7222 - rid:52 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.555678 [ERR] <IP_ADDRESS>:7222 - rid:83 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.557004 [ERR] <IP_ADDRESS>:7222 - rid:82 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.558162 [ERR] <IP_ADDRESS>:7222 - rid:57 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:45.562747 [ERR] <IP_ADDRESS>:7222 - rid:51 - Route Error 'Parser Error'
[25159] 2016/05/11 23:51:45.568465 [ERR] <IP_ADDRESS>:42086 - rid:41 - Route Error 'Parser Error'
[25159] 2016/05/11 23:51:46.287553 [ERR] <IP_ADDRESS>:21773 - rid:124 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:46.482407 [ERR] <IP_ADDRESS>:7222 - rid:147 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:46.691726 [ERR] <IP_ADDRESS>:14642 - rid:178 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:46.692509 [ERR] <IP_ADDRESS>:7222 - rid:23 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:46.697094 [ERR] <IP_ADDRESS>:7222 - rid:181 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:46.701206 [ERR] <IP_ADDRESS>:32642 - rid:199 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:46.701949 [ERR] <IP_ADDRESS>:7222 - rid:115 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:47.352503 [ERR] <IP_ADDRESS>:21602 - rid:25 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:47.356545 [ERR] <IP_ADDRESS>:7222 - rid:249 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:47.734404 [ERR] <IP_ADDRESS>:26443 - rid:258 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:49.828601 [ERR] <IP_ADDRESS>:6371 - rid:295 - Error reading from client: invalid character '"' after top-level value
[25159] 2016/05/11 23:51:52.615339 [ERR] <IP_ADDRESS>:18989 - rid:350 - Error reading from client: invalid character '"' after top-level value

master-2 (<IP_ADDRESS>):
[24895] 2016/05/11 23:41:38.380592 [INF] Starting nats-server version 0.8.0.beta2
[24895] 2016/05/11 23:41:38.380804 [INF] Starting http monitor on <IP_ADDRESS>:8222
[24895] 2016/05/11 23:41:38.380889 [INF] Listening for route connections on <IP_ADDRESS>:7222
[24895] 2016/05/11 23:41:38.380937 [INF] Listening for client connections on <IP_ADDRESS>:4222
[24895] 2016/05/11 23:41:38.380960 [INF] Server is ready
[24895] 2016/05/11 23:49:40.746847 [ERR] <IP_ADDRESS>:53120 - rid:3 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:49:40.748312 [ERR] <IP_ADDRESS>:7222 - rid:1 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:49:43.877191 [ERR] <IP_ADDRESS>:17211 - rid:20 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.147379 [ERR] <IP_ADDRESS>:7222 - rid:35 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.148758 [ERR] <IP_ADDRESS>:15531 - rid:6 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.149640 [ERR] <IP_ADDRESS>:61879 - rid:14 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.149779 [ERR] <IP_ADDRESS>:6880 - rid:17 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.150079 [ERR] <IP_ADDRESS>:20212 - rid:5 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.150414 [ERR] <IP_ADDRESS>:7222 - rid:7 - Route Error {"server_id":"oqqYaosRcPn6D3nDfTdkQn","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24895] 2016/05/11 23:51:43.151381 [ERR] <IP_ADDRESS>:7222 - rid:8 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.154301 [ERR] <IP_ADDRESS>:7222 - rid:38 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.155649 [ERR] <IP_ADDRESS>:7222 - rid:37 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:43.156819 [ERR] <IP_ADDRESS>:7222 - rid:40 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.542432 [ERR] <IP_ADDRESS>:7222 - rid:18 - Route Error {"server_id":"2MblphGmkg60y03IrzRLO8","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24895] 2016/05/11 23:51:45.542647 [ERR] <IP_ADDRESS>:7222 - rid:21 - Route Error {"server_id":"2MblphGmkg60y03IrzRLO8","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24895] 2016/05/11 23:51:45.544648 [ERR] <IP_ADDRESS>:60791 - rid:28 - Route Error 'Parser Error'
[24895] 2016/05/11 23:51:45.547197 [ERR] <IP_ADDRESS>:6259 - rid:71 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.548376 [ERR] <IP_ADDRESS>:7222 - rid:73 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.551352 [ERR] <IP_ADDRESS>:7222 - rid:74 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.558266 [ERR] <IP_ADDRESS>:7222 - rid:72 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.560278 [ERR] <IP_ADDRESS>:7222 - rid:77 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.561255 [ERR] <IP_ADDRESS>:7222 - rid:85 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.563059 [ERR] <IP_ADDRESS>:7222 - rid:60 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.563674 [ERR] <IP_ADDRESS>:7222 - rid:49 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.567555 [ERR] <IP_ADDRESS>:47667 - rid:36 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:45.813436 [ERR] <IP_ADDRESS>:6864 - rid:110 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:46.481487 [ERR] <IP_ADDRESS>:24713 - rid:116 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:46.682473 [ERR] <IP_ADDRESS>:7222 - rid:148 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:46.684418 [ERR] <IP_ADDRESS>:45734 - rid:29 - Route Error {"server_id":"5q71bPewlOKmhddReWNwrg","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[24895] 2016/05/11 23:51:47.351716 [ERR] <IP_ADDRESS>:7222 - rid:30 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:47.505676 [ERR] <IP_ADDRESS>:7222 - rid:185 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:47.733469 [ERR] <IP_ADDRESS>:57464 - rid:201 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:47.863500 [ERR] <IP_ADDRESS>:30688 - rid:222 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:48.593505 [ERR] <IP_ADDRESS>:10013 - rid:251 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.641439 [ERR] <IP_ADDRESS>:43359 - rid:281 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.709225 [ERR] <IP_ADDRESS>:7222 - rid:288 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.711744 [ERR] <IP_ADDRESS>:7222 - rid:287 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.724111 [ERR] <IP_ADDRESS>:7222 - rid:151 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.725633 [ERR] <IP_ADDRESS>:7222 - rid:289 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.727096 [ERR] <IP_ADDRESS>:7222 - rid:204 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.761358 [ERR] <IP_ADDRESS>:7222 - rid:293 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.767856 [ERR] <IP_ADDRESS>:57589 - rid:309 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.826205 [ERR] <IP_ADDRESS>:7222 - rid:304 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.843653 [ERR] <IP_ADDRESS>:38602 - rid:320 - Error reading from client: invalid character '"' after top-level value
[24895] 2016/05/11 23:51:49.867997 [ERR] <IP_ADDRESS>:57596 - rid:313 - Route Error 'Parser Error'
[24895] 2016/05/11 23:51:49.917486 [ERR] <IP_ADDRESS>:7222 - rid:114 - Error reading from client: invalid character '"' after top-level value

master-3 (<IP_ADDRESS>):
[25209] 2016/05/11 23:41:47.251309 [INF] Starting nats-server version 0.8.0.beta2
[25209] 2016/05/11 23:41:47.251526 [INF] Starting http monitor on <IP_ADDRESS>:8222
[25209] 2016/05/11 23:41:47.251759 [INF] Listening for route connections on <IP_ADDRESS>:7222
[25209] 2016/05/11 23:41:47.251937 [INF] Listening for client connections on <IP_ADDRESS>:4222
[25209] 2016/05/11 23:41:47.252088 [INF] Server is ready
[25209] 2016/05/11 23:49:40.746981 [ERR] <IP_ADDRESS>:7222 - rid:2 - Route Error {"server_id":"EB2RwClf6LY74kezPOkhqy","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[25209] 2016/05/11 23:49:40.748221 [ERR] <IP_ADDRESS>:7222 - rid:1 - Route Error {"server_id":"EB2RwClf6LY74kezPOkhqy","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[25209] 2016/05/11 23:49:43.877373 [ERR] <IP_ADDRESS>:7222 - rid:31 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.148773 [ERR] <IP_ADDRESS>:18639 - rid:10 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.149785 [ERR] <IP_ADDRESS>:7222 - rid:7 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.149836 [ERR] <IP_ADDRESS>:25373 - rid:18 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.149908 [ERR] <IP_ADDRESS>:53276 - rid:11 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.150059 [ERR] <IP_ADDRESS>:7222 - rid:22 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.150773 [ERR] <IP_ADDRESS>:43257 - rid:9 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.151043 [ERR] <IP_ADDRESS>:7222 - rid:51 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.152966 [ERR] <IP_ADDRESS>:7222 - rid:49 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.155257 [ERR] <IP_ADDRESS>:7222 - rid:52 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.159458 [ERR] <IP_ADDRESS>:7222 - rid:57 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:43.160200 [ERR] <IP_ADDRESS>:7222 - rid:55 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.544526 [ERR] <IP_ADDRESS>:7222 - rid:34 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.545731 [ERR] <IP_ADDRESS>:7222 - rid:29 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.546220 [ERR] <IP_ADDRESS>:7222 - rid:40 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.549350 [ERR] <IP_ADDRESS>:2493 - rid:102 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.550846 [ERR] <IP_ADDRESS>:62512 - rid:91 - Route Error 'Parser Error'
[25209] 2016/05/11 23:51:45.552569 [ERR] <IP_ADDRESS>:7222 - rid:111 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.555389 [ERR] <IP_ADDRESS>:43310 - rid:81 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.560807 [ERR] <IP_ADDRESS>:7222 - rid:106 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.562448 [ERR] <IP_ADDRESS>:35731 - rid:107 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:45.563777 [ERR] <IP_ADDRESS>:53357 - rid:79 - Route Error 'Parser Error'
[25209] 2016/05/11 23:51:45.566159 [ERR] <IP_ADDRESS>:33124 - rid:78 - Route Error 'Parser Error'
[25209] 2016/05/11 23:51:45.567173 [ERR] <IP_ADDRESS>:2526 - rid:121 - Route Error 'Parser Error'
[25209] 2016/05/11 23:51:46.291334 [ERR] <IP_ADDRESS>:51656 - rid:150 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:46.481574 [ERR] <IP_ADDRESS>:35587 - rid:162 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:46.686796 [ERR] <IP_ADDRESS>:61647 - rid:193 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:46.688625 [ERR] <IP_ADDRESS>:7222 - rid:43 - Route Error {"server_id":"5q71bPewlOKmhddReWNwrg","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[25209] 2016/05/11 23:51:46.690606 [ERR] <IP_ADDRESS>:7222 - rid:190 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:46.694291 [ERR] <IP_ADDRESS>:7222 - rid:214 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:47.351584 [ERR] <IP_ADDRESS>:37990 - rid:47 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:47.866106 [ERR] <IP_ADDRESS>:41792 - rid:266 - Error reading from client: invalid character '"' after top-level value
[25209] 2016/05/11 23:51:49.711900 [ERR] <IP_ADDRESS>:42544 - rid:315 - Error reading from client: invalid character '"' after top-level value

Random slave (<IP_ADDRESS>):
[827] 2016/05/11 23:49:40.369469 [INF] Starting nats-server version 0.8.0.beta2
[827] 2016/05/11 23:49:40.370738 [INF] Listening for route connections on <IP_ADDRESS>:7222
[827] 2016/05/11 23:49:40.370890 [INF] Listening for client connections on <IP_ADDRESS>:4222
[827] 2016/05/11 23:49:40.370948 [INF] Server is ready
[827] 2016/05/11 23:49:42.643024 [ERR] <IP_ADDRESS>:7222 - rid:16 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:49:43.509642 [ERR] <IP_ADDRESS>:7222 - rid:36 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.148718 [ERR] <IP_ADDRESS>:7222 - rid:11 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.149620 [ERR] <IP_ADDRESS>:7222 - rid:1 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.149680 [ERR] <IP_ADDRESS>:7222 - rid:13 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.149713 [ERR] <IP_ADDRESS>:7222 - rid:29 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.149816 [ERR] <IP_ADDRESS>:51702 - rid:6 - Route Error {"server_id":"oqqYaosRcPn6D3nDfTdkQn","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[827] 2016/05/11 23:51:43.150431 [ERR] <IP_ADDRESS>:54504 - rid:3 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.158658 [ERR] <IP_ADDRESS>:51764 - rid:78 - Route Error 'Parser Error'
[827] 2016/05/11 23:51:43.163504 [ERR] <IP_ADDRESS>:7222 - rid:73 - Route Error 'Parser Error'
[827] 2016/05/11 23:51:45.544556 [ERR] <IP_ADDRESS>:7222 - rid:37 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:45.544613 [ERR] <IP_ADDRESS>:7222 - rid:31 - Route Error {"server_id":"2MblphGmkg60y03IrzRLO8","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[827] 2016/05/11 23:51:45.545729 [ERR] <IP_ADDRESS>:7222 - rid:45 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:45.549022 [ERR] <IP_ADDRESS>:7222 - rid:84 - Route Error 'Parser Error'
[827] 2016/05/11 23:51:45.551933 [ERR] <IP_ADDRESS>:7222 - rid:111 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:46.481424 [ERR] <IP_ADDRESS>:7222 - rid:138 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:46.690483 [ERR] <IP_ADDRESS>:7222 - rid:48 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:46.690699 [ERR] <IP_ADDRESS>:7222 - rid:164 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:47.351299 [ERR] <IP_ADDRESS>:7222 - rid:50 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:52.701579 [ERR] <IP_ADDRESS>:7222 - rid:400 - Error reading from client: invalid character '"' after top-level value
e ():
[827] 2016/05/11 23:49:40.369469 [INF] Starting nats-server version 0.8.0.beta2
[827] 2016/05/11 23:49:40.370738 [INF] Listening for route connections on <IP_ADDRESS>:7222
[827] 2016/05/11 23:49:40.370890 [INF] Listening for client connections on <IP_ADDRESS>:4222
[827] 2016/05/11 23:49:40.370948 [INF] Server is ready
[827] 2016/05/11 23:49:42.643024 [ERR] <IP_ADDRESS>:7222 - rid:16 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:49:43.509642 [ERR] <IP_ADDRESS>:7222 - rid:36 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.148718 [ERR] <IP_ADDRESS>:7222 - rid:11 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.149620 [ERR] <IP_ADDRESS>:7222 - rid:1 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.149680 [ERR] <IP_ADDRESS>:7222 - rid:13 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.149713 [ERR] <IP_ADDRESS>:7222 - rid:29 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.149816 [ERR] <IP_ADDRESS>:51702 - rid:6 - Route Error {"server_id":"oqqYaosRcPn6D3nDfTdkQn","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[827] 2016/05/11 23:51:43.150431 [ERR] <IP_ADDRESS>:54504 - rid:3 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:43.158658 [ERR] <IP_ADDRESS>:51764 - rid:78 - Route Error 'Parser Error'
[827] 2016/05/11 23:51:43.163504 [ERR] <IP_ADDRESS>:7222 - rid:73 - Route Error 'Parser Error'
[827] 2016/05/11 23:51:45.544556 [ERR] <IP_ADDRESS>:7222 - rid:37 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:45.544613 [ERR] <IP_ADDRESS>:7222 - rid:31 - Route Error {"server_id":"2MblphGmkg60y03IrzRLO8","version":"0.8.0.beta2","go":"","host":"<IP_ADDRESS>","port":7222,"auth_required":false,"ssl_required":false,"tls_required":false,"tls_verify":false,"max_payload":1048576,"ip":"nats-route://<IP_ADDRESS>:7222/"}Parser Error'
[827] 2016/05/11 23:51:45.545729 [ERR] <IP_ADDRESS>:7222 - rid:45 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:45.549022 [ERR] <IP_ADDRESS>:7222 - rid:84 - Route Error 'Parser Error'
[827] 2016/05/11 23:51:45.551933 [ERR] <IP_ADDRESS>:7222 - rid:111 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:46.481424 [ERR] <IP_ADDRESS>:7222 - rid:138 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:46.690483 [ERR] <IP_ADDRESS>:7222 - rid:48 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:46.690699 [ERR] <IP_ADDRESS>:7222 - rid:164 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:47.351299 [ERR] <IP_ADDRESS>:7222 - rid:50 - Error reading from client: invalid character '"' after top-level value
[827] 2016/05/11 23:51:52.701579 [ERR] <IP_ADDRESS>:7222 - rid:400 - Error reading from client: invalid character '"' after top-level value

I have a single service that subscribes to 2 subjects and a test requester and can confirm that request-reply (on Queue subscribers) work fine.

Master builds should report 0.8.1 version, can you double check?

Yes, either those are older logs (I am not sure you would be able to get the full mesh with the prior bug) and the version should definitively report something else. Maybe some caching issue?

I build gnats fallowing Building of the docs (go build). I now have a version built using Dockerfile in git repo root and will deploy it shortly.
As for 0.8.0beta2 I restarted one gnatsd instance on one of the slaves and I got that cascading thing again (with /routez reporting num_routes jumping up and down) but it stabilized after couple of seconds.
I'll follow up with the results of the 0.8.1 version.

@derekcollison @kozlovic I can confirm that it works flawlessly with gnatsd 0.8.1. No more errors in logs, no more route number going up and down upon a single gnatsd instance restart.
Apologies for the false alarm previously and thanks for the quick turnaround.

Glad to know it works now! And again, thank you for the report.


[Firefox]: Filter mode causing scrolling of fixed elements

Examples: StackOverflow header, Facebook header and chat.

Looks like it is a Firefox bug and there is nothing I can do


ERROR: Could not find a version that satisfies the requirement pickle (from versions: none) ERROR: No matching distribution found for pickle

Can you tell us a what you did to get this error message?


Initial commit for the elasticsearch bundle to Nifi

Matt, first pass at trying to incorporate ES.

Looks great, thanks!


Exception while loading sample 3MF file (duplicated metadata entries)

When trying to load one of the 3MF files from the 3mf-samples repository, lib3mf gives me an exception.  Specifically, this issue can be seen when trying to load the file found at:  https://github.com/3MFConsortium/3mf-samples/blob/master/examples/material/dodeca_chain_loop_color.3mf
The problem, for this file, is that there are two "Description" metadata entries.
Inside CModelReaderNode_Model::ReadMetaDataNode(), there is an if-clause that detects the duplicated metadata, and produces a MODELREADERWARNING_DUPLICATEMETADATA warning.  However, the code proceeds to throw an exception a few lines later during the call to m_pModel->addMetaData().  This exception (NMR_ERROR_DUPLICATEMETADATA) prevents the file from loading.
As I see it, there are two reasonable solutions:

After generating the MODELREADERWARNING_DUPLICATEMETADATA, the ReadMetaDataNode() method could just return.  This means that the "first copy" of the duplicated metadata would be preserved.  The warning would be generated, but no exception would occur, allowing the file-load to complete.
After generating the MODELREADERWARNING_DUPLICATEMETADATA, the ReadMetaDataNode() method could remove the existing/conflicting metadata entry.  That means that the "second copy" (or "Nth copy") of the duplicated metadata would replace the original data.  The warning would be generated, but no exception would occur, allowing the file-load to complete.

Either way, it seems like more or less a one line fix, but it does require a "policy decision" to be made.  (Does lib3mf want to keep the first copy of the duplicated data, or the final copy?)

Hi @jbherdman ,
thank you for your contribution.
According to the core specification, meta data names must be unique:

https://github.com/3MFConsortium/spec_core/blob/1.2.3/3MF Core Specification.md#341-metadata
thus, the intent is that lib3mf handles this accordingly.

Thus option 1 of you suggestions would be the right approach.
Can you change you PR accordingly?
In the mean time, I will take the first part of you PR https://github.com/3MFConsortium/lib3mf/pull/210/files# which fixes https://github.com/3MFConsortium/lib3mf/issues/197 and https://github.com/3MFConsortium/lib3mf/issues/201 and copy it into develop.
Thanks!

Luckily for us, that is already the approach taken in my existing PR.
Technically, my PR moves everything after the warning's if into an else block, rather than forcing a return; onto line 160.  It is functionally equivalent, but seemed more "in the style of" the surrounding code.  Alternately, feel free to just add a "return;" directly after the addWarning() on line 159, instead of picking up the remainder of my PR.

Hi @jbherdman ,
you are right. I was not able to change your PR easily, so I moved your fix onto https://github.com/3MFConsortium/lib3mf/pull/216.
Will be part of v2.1.0.
Thanks again!


Link to Paper

Hi!
The README mentions "our paper"

Add features:
Ground point segmentation:
In our paper we do ground point segmentation by using a accumulated terrain grid

Is this paper yet publicly available? If so, I would love to learn more.
Thanks!

Hello,
Thank you for your interest in our work. Sorry, we didn't expect that this repository gets attention so fast. Luckily, the link to our paper about the continuous clustering was published ( today :) ) on ArXiv: https://arxiv.org/abs/2311.13976
The link to the terrain estimation paper of colleague is here: https://ieeexplore.ieee.org/abstract/document/9827214
As already mentioned in the code of this repository we do not use the terrain estimation yet but rather use a simpler ground point segmentation. That's because the ground point segmentation algorithm from my colleague is not open source yet.


Add LinkedIn to K8s.io and K8s.dev

Now that the community has control of the LinkedIn page, it should be added to the web sites.
/sig contribex

We should either track a similar issue for k/website, or put a checklist on this one.

hi, JFI: The following similar issue is opened in k8s/website,
https://github.com/kubernetes/website/issues/46405

https://github.com/kubernetes/website/issues/46405 is broadly similar, but is about 𝕏 not LinkedIn.

yeah, you are right. I'm just wondering can we consider both icon 𝕏 and LinkedIn, while opening the the new issue or making a checklist on this issue?
@sftim your thoughts on this?

/remove-lifecycle stale
/lifecycle frozen


Provide a flip transition animation for View component.

This gives the <View /> component a flip animation. It doesn't actually modify the view, but utilizes the iOS built in transition animation for UIView.
Example code: https://github.com/adamkrell/FlipCardRN

I believe this can be accomplished with perspective, like in the UI Explorer example here https://github.com/facebook/react-native/blob/master/Examples/UIExplorer/TransformExample.js

@browniefed That's interesting. I haven't experimented with the Animated library yet. The nice thing about using UIView animations is that they are smooth and performant. Do you think this is unnecessary?

@adamkrell they are pretty smooth but in JS now, they'll be hopefully moving to the native world eventually. However I don't think this should be in core, it'd be great if this were a custom view you just released.

@browniefed The View component is quite complex. I'm not exactly sure how to implement that without duplicating a lot of the react native code. Is there an easier way to implement it as a separate component?

@adamkrell you can just extend RCTView and add your own side prop, lots of examples of custom components on the web.

I like the feature, but this isn't the right way to implement it. If we want to support native transitions, we should come up with a proper API for specifying them, possibly an extension of the LayoutAnimation system, or the Animated API?

@browniefed Thanks. I'll give that a try.

@nicklockwood Supporting an API for the native transitions and animations makes sense. I was trying to think of a simple way to add a basic flip animation to a view using a declarative approach (e.g., side = front or back). But there is so much that can be done with animations and transitions that it does seem too specific to make it a property.


Add 'formatter' prop to PlotBandLineLabel

It was missing for some reason...

Codecov Report

Merging #301 into master will decrease coverage by 5.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #301      +/-   ##
==========================================
- Coverage   88.20%   82.69%   -5.51%
==========================================
  Files          82        4      -78
  Lines        1051       52     -999
  Branches      206       15     -191
==========================================
- Hits          927       43     -884
+ Misses        108        9      -99
+ Partials       16        0      -16

Impacted Files
Coverage Δ

...jsx-highcharts/src/components/Subtitle/Subtitle.js

...act-jsx-highcharts/src/utils/propTypeValidators.js

...ackages/react-jsx-highcharts/src/utils/warnings.js

...highcharts/src/components/UsePlotBandLine/index.js

...act-jsx-highcharts/src/components/Legend/Legend.js

...rts/src/components/UseManualEventHandlers/index.js

...jsx-highcharts/src/components/UsePrevious/index.js

...rc/components/RangeSelector/RangeSelectorButton.js

...sx-highcharts/src/components/Legend/LegendTitle.js

...hstock/src/components/Navigator/NavigatorSeries.js

... and 67 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 48928ef...453a960. Read the comment docs.

Thanks!

Published.

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>


[ESP32AT-296] Communication interrupt when +IPD occur in AT+CIPSEND process

Firmware version:
AT version:<IP_ADDRESS>(e44648c - Nov  4 2019 02:18:57)
SDK version:v3.3
compile time(7cac7ad):Nov  4 2019 06:11:40
Bin version:2.0.0(WROOM-32)
Test condiction:
ESP32 connecting to a TCP server which will send message "test x" around every 200ms. ESP32 will echo immediately when got message.
Issue occur condition:
Sometime the +IPD will occur between AT+CIPSEND command and "Recv x bytes", then ESP32 won't get the fellow messages from the server. After 2~3 min, the server will show the connection is closed but the ESP32 still show the connection is alive but will respone SEND FAIL to AT+CIPSEND
[2020-01-14 12:05:09,091][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:11.605]:Send:b'AT+CIPSEND=0,8'
[2020-01-14 12:05:09,099][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:11.613]:Recv:b'AT+CIPSEND=0,8\r\n\r\nOK\r\n\r\n>'
[2020-01-14 12:05:09,100][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:11.613]:Send:b'test,26,'
[2020-01-14 12:05:09,109][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:11.623]:Recv:b'\r\nRecv 8 bytes\r\n\r\nSEND OK\r\n'
[2020-01-14 12:05:09,510][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:12.024]:Recv:b'\r\n+IPD,0,8:test,28,\r\n'
[2020-01-14 12:05:09,510][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:12.024]:got 1 msg, COM40"<IP_ADDRESS>":ipd=14, msg=14, retry=None,send=13
[2020-01-14 12:05:09,510][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:12.024]:Send:b'AT+CIPSEND=0,8'
[2020-01-14 12:05:09,517][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:12.031]:Recv:b'AT+CIPSEND=0,8\r\n\r\nOK\r\n\r\n>'
[2020-01-14 12:05:09,518][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:12.032]:Send:b'test,28,'
[2020-01-14 12:05:09,526][DEBUG]:<COM40"<IP_ADDRESS>">[0:00:12.039]:Recv:b'\r\n+IPD,0,8:test,30,\r\n\r\nRecv 8 bytes\r\n\r\nSEND OK\r\n

This bug also affect me, I write a simple server program to test this bug, you can follow the instruction in README.md to reproduce this bug
server program at https://github.com/iabdurrahman/echo_server


Remove AllowOrigin from route since it is deprecated in istio API

This PR removes the AllowOrigin and relies completely on AllowOrigins from route since it is deprecated in istio API.

@Nino-K: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Nino-K: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test unit-tests_istio

release-test_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test unit-tests_istio

release-test_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test release-test_istio

integ-conformance-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-conformance-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test unit-tests_istio

release-test_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test release-test_istio

integ-conformance-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test unit-tests_istio

release-test_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test release-test_istio

integ-conformance-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-security-k8s-tests_istio

gencheck_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test unit-tests_istio

release-test_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test release-test_istio

integ-conformance-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-security-k8s-tests_istio

gencheck_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test gencheck_istio

integ-distroless-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test unit-tests_istio

release-test_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test release-test_istio

integ-conformance-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-security-k8s-tests_istio

gencheck_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test gencheck_istio

integ-distroless-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-distroless-k8s-tests_istio

integ-local-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-local-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Nino-K: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-mixer-k8s-tests_istio

integ-galley-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-galley-k8s-tests_istio

integ-telemetry-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-telemetry-k8s-tests_istio

lint_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test lint_istio

integ-pilot-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-pilot-k8s-tests_istio

unit-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test unit-tests_istio

release-test_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test release-test_istio

integ-conformance-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-conformance-k8s-tests_istio

integ-security-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-security-k8s-tests_istio

gencheck_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test gencheck_istio

integ-distroless-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-distroless-k8s-tests_istio

integ-local-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-local-tests_istio

integ-multicluster-k8s-tests_istio
5905434873c6855df6774f60dfc62c1c21774a23
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Chrome extension broken again.

MGGA is not showing up at all anymore, on any pages.

I'm currently unable to test the userscript version; if anyone knows its status please chime in.
Link to page where error occurs

It's working again.


Corrupted data for Haryana coming

Please find attached screen shot for the same..

Refer to https://github.com/covid19india/covid19india-react/issues/1846#issuecomment-626884611


Popup for creating new playlist

A continuation of https://github.com/aome510/spotify-player/pull/234.

Thanks @m-torhan for taking on this. I'll review this PR once I get back from vacation.

Thanks @m-torhan for taking on this. I'll review this PR once I get back from vacation.

Very nice guys!!
Nice @m-torhan ✨

PR looks good to me. I added a few changes to improve the code and the UI. However, for some reasons, I couldn't push my commits to this PR. Replace by https://github.com/aome510/spotify-player/pull/379


Add Plex

Add Plex for media transcoding/streaming
Docker container: https://hub.docker.com/r/linuxserver/plex/
Homepage: http://plex.tv

was just going to ask this lol


Faster augmentation

Hi.
I've made very fast augmentation algorithms for keras version of project
https://github.com/anatolix/keras_Realtime_Multi-Person_Pose_Estimation
It augments 140 images per second in python (C++ augmentation augments 30)
Trick is in made all augmentation(crop/scale/resize/shift) with one warpAffine and vectorized generation of heatmaps and pafs. Please take a look, if you like it i could adapt it and make pull request.

Thank you very much. It's a wonderful work!


Add check for code style

Add code style checking into travis.

Will use WordPress Coding Standards with GIOS Coding Standards Blend for consistency across our repos.
Also need to fix all the coding standard mishaps.

Ugh, there is a bug somewhere in the coding standards where an if statement in a closure is always improperly indented.


Remove duplicate enum entries

Docs Build status updates of commit 9ed60df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/docs-ref-autogen/excel-async/toc.yml
:white_check_mark:Succeeded

docs/docs-ref-autogen/excel/toc.yml
:white_check_mark:Succeeded

generate-docs/scripts/postprocessor.ts
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Implement ES6 RegExp.prototype[@@match]

@abchatra Could you take a look?

Closed in favor of #376. This PR didn't show the correct set of commits for some reason.


carthage support

Thanks for the cool project. Is there any plan to support Carthage?
Thanks
Tianzhu

You are welcome to leave a pull request if you like. I am not familiar with the specifics of supporting Carthage.


java.lang.IllegalArgumentException: kundera.client property is missing for persistence

this issue was fixed in 2.3 by @kkmishra  and returned in 3.0
https://github.com/impetus-opensource/Kundera/issues/133

Fixed in trunk, issue was in loadEntityMetadata method of MetamodelConfiguration.java class, when there is no <property name="kundera.client.lookup.class" value="com.impetus.client.xxxx" /> property in persistence unit. Thanks Kuldeep

sorry, not an issue. typo in configuration


Crash while using turbine

Crash report:
---- Minecraft Crash Report ----
// Why did you do that?
Time: 24.06.15 21:01
Description: Unexpected error
java.lang.IllegalStateException: Already tesselating!
at net.minecraft.client.renderer.Tessellator.func_78371_b(Tessellator.java:374)
at net.minecraft.client.renderer.Tessellator.func_78382_b(Tessellator.java:364)
at net.minecraft.client.particle.EffectRenderer.func_78874_a(EffectRenderer.java:147)
at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1617)
at net.minecraft.client.renderer.EntityRenderer.func_78480_b(EntityRenderer.java:1305)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:1001)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:898)
at net.minecraft.client.main.Main.main(SourceFile:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)
A detailed walkthrough of the error, its code path and all known details is as follows:
-- Head --
Stacktrace:
at net.minecraft.client.renderer.Tessellator.func_78371_b(Tessellator.java:374)
at net.minecraft.client.renderer.Tessellator.func_78382_b(Tessellator.java:364)
at net.minecraft.client.particle.EffectRenderer.func_78874_a(EffectRenderer.java:147)
at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1617)
-- Affected level --
Details:
Level name: MpServer
All players: 1 total; [GCEntityClientPlayerMP['ColdPhoenix'/14, l='MpServer', x=1755,79, y=63,89, z=453,71]]
Chunk stats: MultiplayerChunkCache: 289, 298
Level seed: 0
Level generator: ID 01 - flat, ver 0. Features enabled: false
Level generator options:
Level spawn location: World: (1739,4,463), Chunk: (at 11,0,15 in 108,28; contains blocks 1728,0,448 to 1743,255,463), Region: (3,0; contains chunks 96,0 to 127,31, blocks 1536,0,0 to 2047,255,511)
Level time: 17924 game time, 17924 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: creative (ID 1). Hardcore: false.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Anisotropic filtering is supported and maximum anisotropy is 16.
Shaders are available because OpenGL 2.1 is supported.
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Packs: []
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Anisotropic Filtering: Off (1)

This is likely caused by optifine, either use default or smooth chunk loading or disable connected textures if it happens again, if all else fails let me know. Also, next time use something like http://paste.ubuntu.com/ for crashlogs etc.


How to handle other users camera and mic

Hello Everyone
can you guys suggest that how to handle others attendees camera and mic ?
I want to On/Off camera and Mic of other users.
please tell me how to handle this features.

Hey @AbhishekSri979  you can make use of Data Channels to send on/off events that will get listened to by all users in the Video call room. Send correct payload to identify whom mic/camera you want to switch.

Ok Thanks @saurabhghadi0401
Now, i am able to handle camera/mic.


[sync] feat: enable Trusty's Bias Feature Flag

Description

cherry-pick ODH
https://github.com/opendatahub-io/opendatahub-operator/pull/1220
https://github.com/opendatahub-io/opendatahub-operator/pull/1232

https://issues.redhat.com/browse/RHOAIENG-11891
How Has This Been Tested?

Screenshot or short clip

Merge criteria

[ ] You have read the contributors guide.
[ ] Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
[ ] Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

close in favor of https://github.com/red-hat-data-services/rhods-operator/pull/355


Adds IExceptionInterpreter.Order property

Description

The Order property can be used to give priority on exception interpreters calls.
Related Issue

#1630
Motivation and Context

If two or more interpreters can be used by a particular exception, priorities need to be defined.
Requires Documentation Change

No.
How Has This Been Tested?

Unit tests.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/ect)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description or feature-<issue#>-<description>

Building failing due to QuantConnect.Tests.Engine.DataFeeds.BaseDataExchangeTests.EndsQueueConsumption -- this is not due to changes in this PR but due to travis.

I increased the timeout in the BaseDataExchangeTests, rebasing the PR should fix the Travis issue.


OCPBUGS-13034: Fixed revoking some permissions to CAPI Manager Clusterrole

What this PR does / why we need it:
I the previous PR on this topic, I've added non necessary permissions, this PR fixes that.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #OCPBUGS-13034
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.

/approve
/lgtm

/retest-required

/retest-required

/retest-required

/retest-required

/test e2e-aws

/test e2e-aws

/jira refresh

/jira refresh


Picking up wrong standardised name

Hi,
Tried FlashText. Unfortunately, it picks up the wrong standardised name.
For example, if I have two different values (standardised name ) for unclean name i.e "able" and "unable".
It interchanges the values during the search. Can we have the options for both exact string matching like REGEX and also the speed of Flashtext? Can we have the configurable Levenshtein distance while searching. Then it could be interesting.
Regards
Prabhat

Hi @prabhatM ,
Sorry I didn't understand your first point clearly.
Regarding second point, unfortunately myself and the repository owners are busy. So if you would like you can go ahead and build the feature and push a merge request.
Kind regards,
Nandan Thakur

Hi,
Thanks for your reply.
For the time being, I have moved on. When I come back to the issue again, I
will keep you updated.
Regards.
Prabhat
On Sat, 7 Nov, 2020, 1:39 pm Nandan Thakur<EMAIL_ADDRESS>wrote:

Hi @prabhatM https://github.com/prabhatM ,
Sorry I didn't understand your first point clearly.
Regarding second point, unfortunately myself and the repository owners are
busy. So if you would like you can go ahead and build the feature and push
a merge request.
Kind regards,
Nandan Thakur
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vi3k6i5/flashtext/issues/116#issuecomment-723416359,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABXKGXHI3WJYZZ7NYTCCE3DSOT6BZANCNFSM4RNIDNXQ
.


[E2E refactor - 7] refactor authorization e2e test

I decided to break out the kind E2E test refactor PR https://github.com/GoogleCloudPlatform/prometheus-engine/pull/738 into smaller, digestible PRs for reviewing.
Note: because of the nature of the change, presubmits (i.e. Github Actions) may fail until the final PR is merged.
This is the seventh one, where we refactor and simplify authorization e2e tests.

Yea - here you just run TEST_RUN=TestBasicAuthClusterPodMonitoring make e2e to get the desired affect.
I did it this way, against some convention for two reasons:

Readability and reusability - each Test has clear steps with comments, and each flavor of test is separated out for clear distinction. Obviously, the main drawback here is DRY - but I lean towards repeating oneself if it makes the code easier to follow - particularly in Go, where this is more conventional. Additionally, the subtests run sequentially and are not marked with t.Parallel().
Parallelism in GH Actions. The conventional way would essentially recommend bundling everything in one TestXXX function, in-line your set and teardown, and sandwich in your subtests do the various flavors. This works in some cases, and doesn't work in others. For example, in our case, where we need to patch the example-app with specific flags for each subtest. Doing this in one Test function increases build times and can cause timeout issues against the K8s API server.

If we really wanted to force convention for our use case, we could look into changing the way we build our TEST_RUN matrix to list all subtests as well. However, I'm not sure how to do this.

Thanks for the feedback - that SGTM!


rayffi.bqn shouldn't use Struct to combine strings prematurely

the current way rayffi is set up with the structs is that the Struct function is applied to a sequence of types and they're joined right away. instead, what should be done is the _R modifier should join the types itself, since this allows more possibilities for checking types of structs outside the ffi file.
Also after this is done, i'll be soon adding automatic null-terminating for strings in structs aswell, like how i've done with the non-struct arguments.

i was actually done with I'll be soon adding automatic null-terminating for strings in structs aswell, like how i've done with the non-struct arguments. first suprisingly. So only the top is left

I have hit a road block with implementing this, and that is how to detect if input list of structs is a list of arguments to _R or if it's a single struct with lists. I have not found a solution yet.

I have now a autogenerated rayffi.bqn working, and an idea for how to fully close this issue.
First, making all arguments for _R (which are types) be lists, which is already done.
and second just apply S recursively at each perameter input.
Fixing this issue will actually open a lot of ways of improving the autogeneration and make me able to autoparse structs and such easier. very exciting

Done!
This will make so many improvements possible! i am very excited :)


BlackDuck API - get_asset issue

Hi I am facing the below issue when trying to connect to my BlackDuck repository.
I did create the API Tool conection, with the API Key, but the error is showed when configuring a new API Scan configuration.
Deployment method (select with an X)

[ x] Docker Compose
[ ] Kubernetes
[ ] GoDojo

Environment information

Operating System: [e.g. Ubuntu 18.04]
DefectDojo version v. 2.19.2 ( release mode )

Fixed in #7665, released in 2.19.3.


More powerful $cookies service

I want to set a cookie on the root path / so it's available everywhere on the domain.
But the $cookies service only accepts name and value, and always sets the cookie path to the current page via self.baseHref().
Could the $cookies service be extended to provide access to additional cookie properties like path, expires, domain and secure?
I quite like the API of the jquery.cookie plugin: https://github.com/carhartl/jquery-cookie#usage. It keeps the common name=value use case simple and allows to set additional cookie properties via a third options object parameter.
I'm not very proficient in Javascript but I might try to implement something over the weekend.

+1

I'd love to take this one if it is available.  however it looks like it has already been taken care of by this commit: d4567891b8616596d125b4dd5560dc9471d2ed63
Can any one verify this?

+1

I've updated my module fix - ng-biscuit, but of course ngKookies looks more mature


Lookup Fields in SharePoint Online not Working Correctly

This is to reopen this issue. First time posting so please forgive any error - I am still having the same problem.
Category

[ ] Question
[ ] Typo
[X] Bug
[ ] Additional article idea

Expected or Desired Behavior
When a file is uploaded to Sharepoint,, you should be able to use the details pane to select any value from a lookup table and save the correct value.
Observed Behavior
Sharepoint 365 fields are defaulting to the first value in the list, no matter what is selected. When you try to correct it within the details pane, it opens an "edit" dialog and any change is made to the lookup table itself.  If you select "Edit all" to get the full pane then you can make the proper change but it is not possible from the details pane.
Steps to Reproduce

Add a list with a few test items, titles only is fine.
2, Create a column in a document library with type "Lookup".  Under "Get Information from", select the list from step 1.
Upload a document to the library.
Attempt to set lookup column to anything EXCEPT first item.
Sharepoint uses the first value, no matter what you selected, and autosaves.
Go back to try to change - drop down will not show up but an Edit dialog box will show up tied to the lookup table itself.

Work around - Select Edit all.

Thank you for your submission. This GitHub issue list is targeted only for developer issues. As your issue is related on out-of-the-box capabilities or features, we cannot unfortunately process is through this channel. Please submit your finding using the Tenant administrator support channels in your tenant or using Premier support, if that’s available for you. Sorry for the inconvenience.