Interactive snapshot update doesn't work

[noinkling]

🐛 Bug Report

Running Jest in watch mode, I get some failing snapshot tests (the diffs are visible, etc). I press i to try and interactively update these snapshots. It shows Determining test suites to run... (plus the line showing which suite is running) for a short time. Sometimes I can notice quick flashes of something at this point, but they only appear for an instant (some of them look like failing tests, maybe the diffs as well, very difficult to make anything out at that speed). After that it just prints out:

Interactive Snapshot Result
 › 5 snapshots reviewed, 5 snapshots updated

Watch Usage
 › Press Enter to return to watch mode.

Watch Usage: Press w to show more.

I don't get presented with any other prompts during this process.

Worth noting that pressing w at this point doesn't do anything.

Looking at the snapshot files, they weren't actually updated (thankfully). If I press Enter it goes back to watch mode like expected, and the snapshot errors haven't changed.

Expected behavior

I expected to be presented with interactive prompts for updating (or not updating) failing snapshots as described here: http://jestjs.io/docs/en/snapshot-testing#interactive-snapshot-mode

Run npx envinfo --preset jest

  System:
    OS: Linux 4.4 Ubuntu 16.04.4 LTS (Xenial Xerus)
    CPU: x64 Intel(R) Core(TM)2 Quad CPU    Q9400  @ 2.66GHz
  Binaries:
    Node: 10.5.0 - /usr/bin/node
    Yarn: 1.7.0 - /usr/bin/yarn
    npm: 6.1.0 - /usr/bin/npm
  npmPackages:
    jest: ^23.2.0 => 23.2.0

It's probably important to note that I'm running in WSL. This occurs in both the WSL-provided (conhost-based) terminal, as well as in Mintty.

[wyze]

Duplicate of #6485.

[SimenB]

Fix should be out in 23.3.0

[noinkling]

Duplicate of #6485.

Apologies, I did a search and somehow missed that one.

[noinkling]

@wyze @SimenB 23.3.0 kinda fixes it, but there's a follow-on bug which I've made a new issue for (#6625).

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.