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

Exception in Jetbrains 2023.2 EAP IDEs #553

Open
yohannlog opened this issue Jun 30, 2023 · 9 comments
Open

Exception in Jetbrains 2023.2 EAP IDEs #553

yohannlog opened this issue Jun 30, 2023 · 9 comments
Assignees

Comments

@yohannlog
Copy link

yohannlog commented Jun 30, 2023

Hi!

I've got an exception when using tabnine in EAP version (When autocompleting with tab key).
This causes an exception causing the inability to copy paste and this causes several bugs on undo action.

This is the error:
java.lang.Throwable: Assertion failed: Undoable actions allowed inside commands only (see com.intellij.openapi.command.CommandProcessor.executeCommand())

I had opened a bug report on Jetbrains youtrack but after investigation, it seems that the problem came from here. Here is the link: https://youtrack.jetbrains.com/issue/IDEA-323867/Undo-problem-Undoable-actions-allowed-inside-commands-only

Thanks !

gz#24636

(related to Zendesk ticket #24636)

@yohannlog yohannlog changed the title Exception in 2023.2 EAP Exception in Jetbrains 2023.2 EAP IDEs Jun 30, 2023
@TzufTabnine
Copy link

Hi @yohannlog
Try using Tabnine on a non-EAP version.

@jingxinli33
Copy link

jingxinli33 commented Jul 11, 2023

Hi @yohannlog Try using Tabnine on a non-EAP version.

Hi @TzufTabnine I am also an IntelliJ IDEA plugin developer and I have encountered a similar issue as yours. The problem seems to be triggered by the auto-import command after accepting the completion suggestions. When the user attempts to undo the action using ctrl+z, this exception is thrown. Additionally, it appears that this issue only occurs in the 2023.2 EAP of the IDEA. Could you please kindly share how you managed to resolve this issue? Thanks

@yonip23
Copy link
Contributor

yonip23 commented Jul 11, 2023

Hi @jingxinli33
Thanks for reporting the EAP issue, we will add this to our backlog and prioritize.

Could you please kindly share how you managed to resolve this issue?

Are you asking how did we manage to resolve the issue on the stable versions, or the EAP version?

@Metachemix1
Copy link

@TzufTabnine this issue still occurs on Build #WS-232.8660.143, built on July 21, 2023 NON-EAP build of Webstorm, as a workaround i've temporary disabled the plugin. As it influences my workflow too much by disabling the undo /copy-paste within webstorm IDE.

Please consider re-opening this ticket.

@gvko
Copy link

gvko commented Jul 26, 2023

Yesterday I upgraded to the latest WebStorm version WS-232.8660.143, built on July 21, 2023 and I'm having the same issue. After disabling the plugin, I have no more issues with copy-paste functionality.
This is not resolved and the ticket should be re-opened.

@yairco1990
Copy link
Contributor

We have identified an issue with the auto-import module in our plugin, which appears to conflict with the latest version of Jetbrains. We're working diligently to address this.
In the meantime, we recommend a temporary workaround: disabling the auto-import functionality. You can do this through the TabNine settings panel in your IDE. We'll keep you updated as we work towards a resolution.

@mkalus
Copy link

mkalus commented Jul 31, 2023

We have identified an issue with the auto-import module in our plugin, which appears to conflict with the latest version of Jetbrains. We're working diligently to address this. In the meantime, we recommend a temporary workaround: disabling the auto-import functionality. You can do this through the TabNine settings panel in your IDE. We'll keep you updated as we work towards a resolution.

This did not solve the error for me (Ubuntu 22.04, Jetbrain IDEs installed via Toolbox). Affects all IDEs!

@TzufTabnine
Copy link

Make sure you have the latest version of Tabnine (1.0.37). It should solve the issue.

@mkalus
Copy link

mkalus commented Jul 31, 2023

Nope, it did not - I did test with the latest issue and it still throws the same error.

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

No branches or pull requests

9 participants