Skip to content

VIM E2E Test Broken by VIM Ubuntu Package 8.2.3995-1ubuntu2.19 #2182

Open

Activity

JustinGrote

JustinGrote commented on Oct 2, 2024

@JustinGrote
CollaboratorAuthor

Test works fine in upterm, weird. What context is different in the run env I wonder?
image

JustinGrote

JustinGrote commented on Oct 2, 2024

@JustinGrote
CollaboratorAuthor

@andyleejordan I think whatever VIM you're downloading, something in the latest version broke the tests. If I remove the ENV to the executable, the test completes, see this PR:
#2183

JustinGrote

JustinGrote commented on Oct 2, 2024

@JustinGrote
CollaboratorAuthor

Looks like package updated to vim-gtk3 8.2.3995-1ubuntu2.19, it was ubuntu2.18 before, something in that update appears to have broken it.
https://launchpad.net/ubuntu/+source/vim/2:8.2.3995-1ubuntu2.19

changed the title [-]VIM E2E Test Broken Assignees: @andyleejordan @JustinGrote Labels: bug Milestone: Projects: [/-] [+]VIM E2E Test Broken by VIM Ubuntu Package 8.2.3995-1ubuntu2.19[/+] on Oct 2, 2024
JustinGrote

JustinGrote commented on Oct 2, 2024

@JustinGrote
CollaboratorAuthor

@andyleejordan nightly works fine, so I adjusted the github action to use nightly, see this PR:
#2183

We will need to actually verify if the extension is actually broken due to this security update package, since it is the current stable ubuntu package and will have widespread usage, and determine if it's something with us or with vim or their lsp client (it's not clear from the test)

andyleejordan

andyleejordan commented on Oct 7, 2024

@andyleejordan
Member

Yay for fun new bugs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @andyleejordan@JustinGrote

      Issue actions

        VIM E2E Test Broken by VIM Ubuntu Package 8.2.3995-1ubuntu2.19 · Issue #2182 · PowerShell/PowerShellEditorServices