It could also be https://github.com/facebook/react/commit/7dc903cd29dac55efb4... ("This also fixes a critical security vulnerability.")

It does the same thing here, too: https://github.com/facebook/react/commit/7dc903cd29dac55efb4...

What are you missing from the TUI? The latest version has improved it a bit, it's more responsive now and you can navigate around the UI with the keyboard more easily (tab, up/down arrows, and pgup/pgdown). If you don't like it though, you can also use `--format text` for a UI-less experience that just prints things to stdout.

As for converting failures into forge tests, there's multiple tools offering a solution to that problem; check out (in no particular order):

  * the Recon VSCode extension (https://github.com/Recon-Fuzz/recon-extension)
  * fuzz-utils (https://github.com/crytic/fuzz-utils)
  * runes (https://github.com/Enigma-Dark/runes)
  * fuzz_parser (https://github.com/Enigma-Dark/fuzz-trace-parser)

Some of them use the Echidna trace output, while others (like runes and fuzz-utils) take advantage of the fact that Echidna saves these sequences as part of the corpus during runtime (particularly, in the `reproducers` and `reproducers-unshrunk` corpus subdirectories)

Wow these would have saved my team and I a ton of time. Thanks for the links.

For what's missing from the TUI. The fact that the outputs in the main window are not selectable makes it difficult to keep the fuzzer running but copy the call sequence. I have to ctrl+c to get it into my terminal output and copy from there. I think these tools might help here though.