Phil Rzewski

This one is in the "On Deck" pile on the assumption we'd attack the first item in the list soon, and once we've done that we can open issues for...

Note that even before we start presenting the crash/log info nicely in the app, I've noticed that currently even if the user knows where to find the `zlake.log` for the...

Note that https://github.com/brimdata/zed/issues/4080 was another incident where an unexpected `zed serve` failure made for a bad debug UX due to lack of detail in the logs.

@jameskerr has pointed out that our new design has something like this. Let's make sure to show it to the original requesting user and get their feedback.

Here's another request for this from the community Slack: https://brimdata.slack.com/archives/C010DR0HHMF/p1657017681180799 Also, the original Slack thread that that spawned the initial issue, which had 4 community members speaking up in favor...

Note that a community user in a [public Slack message](https://brimsec.slack.com/archives/CTT24051C/p1650984944949229) recently expressed what they believed was a valid reason to want to continue using an older release. If they happen...

Today we received another piece of test data from a zync user that performs even worse due to this problem. It's sensitive data so I'm not attaching it to this...

I've found the GitHub test data downloaded in #2283 is also good for repro'ing this issue, once you preprocess it with `over this`.

I just happened to bump into this again in Brim commit 55d1fdc. In this case I only single-clicked it. 

Since #2471 recently fixed an issue with a similar message, I checked to see if this one is still with us. As shown in the attached video, there is indeed...