Phil Rzewski

The next round of debug was to add `console.log()` messages at various points in dependencies. Ultimately it was this change in `node_modules/playwright-core/lib/server/electron/electron.js` that showed us what we needed to see:...

Verified on Zui commit 5fa9071. I started this loop of the e2e test at this commit to check for failure rates. ``` $ SUCCESSES=0; FAILURES=0; while true; do yarn e2e...

The changes in linked PR #3087 provide the "squiggly lines under an error in the editor" envisioned above by @jameskerr. If The red squiggly lines appear below whatever caused the...

Note to self: When this change is complete, I should be able to leverage it to simplify some things in https://github.com/brimdata/grafana-zed-datasource.

A summary of what's been spawned from this issue: * While `zq` can read the JSON without complaint, there's some curious challenges getting the same JSON to successfully `zed load`....

As shown in the attached video, the main symptom of this issue has been addressed by the changes in #3026. The `mun.json` file can now be loaded into Zui without...

Note to self: When this change is complete, I should be able to leverage it to simplify some things in https://github.com/brimdata/grafana-zed-datasource.

@Dessix: Indeed, a PR merge triggered the early closure of this issue, so I'm reopening. As you noted, #5119 just rationalizes the tool's current behavior so it's no longer contradicting...

@Dessix: Yes, it certainly was the `Closes #5110`. It would be nice if they had an easier way to link up PRs and Issues in advance without the auto-close trigger...

As part of the evolution to SuperDB we did make multiple changes that affect what's described in this issue. The tl;dr is that [these docs](https://zed.brimdata.io/docs/next/commands/super#usage) accurately describe how the `super`...