Phil Rzewski

See also https://github.com/zeek/zeek/issues/2141 and https://github.com/brimdata/geoip-conn/issues/39.

@milti: Thanks for your interest in the projects. A couple of us on the Brim team have read this issue and admit to some limits in our PyPi knowledge. Personally...

Hrm. Indeed, I saw Avast on the list of engines that flagged it and I happen to run Avast on my Windows system, so I reproduced the problem successfully. ...

I just went ahead and submitted it at https://www.avast.com/false-positive-file-form.php to see if the Avast people might come back with anything more specific to say.

I did get the following reply from Avast: --- > Greetings, > > Thank you for contacting Avast with your concerns. > > Our virus specialists have been working on...

Alas, when I replied and asked Avast to point to Brim's specific violations from their checklist, they did not provide. Their message: --- > Hello Phil, > > Thank you...

Note to self: If/when we make improvements here, I should be able to revise the wiki article updated via https://github.com/brimsec/brim/pull/1380.

This was recently reviewed with the UX team. We suspect the "open" would return a non-zero when the app fails to launch, and so we could catch this. @jameskerr: Also...

@Ibranum: A couple questions to help narrow it down. 1. Which Brim version are you running? The current version is shown when you select **Brim > About Brim** from the...

@Ibranum: Glad to hear you were able to figure out what was going on. Indeed, my next line of inquiry would have been to start to piece together the `brimcap`...