JP Posma

Btw this is also causing trouble for people using rust-analyzer; see https://github.com/rust-analyzer/rust-analyzer/issues/6835#issuecomment-756648136 — so would be great to merge this :)

I ran into this too. It's a race condition, because the returning `postMessage` calls are not guaranteed to fire in order.

Here is an example I came across: https://flows.nodered.org/flow/3827f07ed08826b01bd71b2c874f7fdc 

Seeing the same problem, also when using built files (in this case using [watchify](https://github.com/substack/watchify)).

We just need to have the mouth curl up a bit into a smile. According to @hassonics this looks like a hippo in pain, we need a happy hippo! 😁

Haha so awesome! > On 23 Sep 2016, at 04:59, Henric Trotzig [email protected] wrote: > > I tried out the svg locally, and it has some issues: > > The...

If you're just reading the entire bag, you can determine how many messages there are in each topic by using `bag.chunkInfos`. Each `ChunkInfo` has a list of "connections" and how...

Should we detect this using the bag index and show a warning or error?

Hm, interesting, I can't reproduce. Do you get the same error if you use `docker run -p 8080:8080 cruise/webviz` instead of `npm run serve-static-webviz`? I think I've seen this error...

Ok I updated `master` with our latest code changes (https://github.com/cruise-automation/webviz/pull/443), can you pull and try again and see what happens?