Bug: spamming `]` at bottom of diff causes Error

[jonator]

It's not easily reproducible, but this was after returning to a pane and scrolling to bottom, then spamming ].

Not sure if it was because I had another session running that AI posted comments, then returned to this one.

Error: Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.
    at getRootForUpdatedFiber (/$bunfs/root/hunk:3318:131)
    at dispatchSetStateInternal (/$bunfs/root/hunk:4544:45)
    at dispatchSetState (/$bunfs/root/hunk:4515:31)
    at updateViewport (/$bunfs/root/hunk:90341:24)
    at handleViewportChange (/$bunfs/root/hunk:90344:21)
    at emit (node:events:95:22)
    at onChange (/$bunfs/root/hunk:67287:18)
    at value (/$bunfs/root/hunk:66965:23)
    at updateSliderFromScrollState (/$bunfs/root/hunk:67372:16)
    at scrollPosition (/$bunfs/root/hunk:67243:39)

[grocky]

I just ran into this as well. When AI notes are loaded in a session. I tried running hunk diff with --watch applied and not applied.

For me, when navigating with {/} causes it to reach the react error.

For context: I'm running hunk in tmux in Ghostty on OSX