Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible regression: Error after closing the pane #229

Closed
tscolari opened this issue Aug 18, 2024 · 2 comments · Fixed by #231
Closed

Possible regression: Error after closing the pane #229

tscolari opened this issue Aug 18, 2024 · 2 comments · Fixed by #231

Comments

@tscolari
Copy link
Contributor

Hello there, I think there is a regression at some recentish change 🤔
I use vimux as the strategy for nvim-neotest, and up until recently the behaviour it presented was, for example:

- run some tests
- it would open a pane, and run the tests there
- I could close the pane
- run again some other tests
- it would open another pane

Now, what is happening is that when I close the pane, if I try to run the command again I'll get this error from vimux for example:

Error detected while processing function test#run[27]..test#execute[23]..test#shell[19]..test#strategy#vimux[2]..VimuxClearTerminalScreen[2]..VimuxSendKeys[2]..VimuxTmux[8]..function test#ru
n[27]..test#execute[23]..test#shell[19]..test#strategy#vimux[2]..VimuxClearTerminalScreen[2]..VimuxSendKeys[2]..VimuxTmux:                                                                    
line    8:                                                                                                                                                                                    
E605: Exception not caught: Tmux command failed with message:can't find pane: %71^@

Is this intended?
I've been trying to find out what could be causing this, any help will be appreciated.

@tscolari
Copy link
Contributor Author

I managed to trace the code that caused the issue here: fa35410#r145509866
Going to create a PR with a fix

@tscolari
Copy link
Contributor Author

Fix: #231

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant