Closed philrz closed 3 years ago
The root cause of this was fixed on the Zed side via brimdata/zed#2745. However, while studying this symptom, @nwt spotted some unexpected redundant requests coming from Brim. These were shown to @jameskerr and he agreed to take a closer look at them. #1666 has been opened to track that. Closing this one.
Repro is with Brim commit 207cb69 which uses Zed commit
1d16c1b
. The issue actually did not appear at a Brim-side code change but rather when the Zed dependency inpackage.json
was updated to that Zed commit. It's not clear to me if the problem is because some Zed bug unexpectedly broke Brim or if we just missed updating Brim to adapt to a new Zed behavior, so I've flipped a coin and opened this on the Brim side to start.As shown in the attached video, if I import a larger pcap such as https://storage.googleapis.com/brimsec-releases/wrccdc.pcap, the histogram never draws and there's an error dump visible in DevTools. With smaller pcaps I've seen the histogram draw ok.
https://user-images.githubusercontent.com/5934157/118733121-89fc9d00-b7f0-11eb-986a-18c1b71aaada.mp4
Here's a text dump of the error shown in the video:
As mentioned above, I've confirmed this problem first showed up when the Zed commit in Brim's
package.json
was advanced to Zed commit1d16c1b6ae24c20210683c533905598239d37d80
, which is associated with brimdata/zed#2731 (cc: @mccanne). If I update that dependency inpackage.json
to the prior Zed commitd5b407d05f6c9aa82c7cb87accf2aa083600b980
, the histogram draws ok and the error dump does not appear in DevTools.