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

Missing extension command in VSCode #680

Open
MintakaB opened this issue Feb 20, 2024 · 19 comments
Open

Missing extension command in VSCode #680

MintakaB opened this issue Feb 20, 2024 · 19 comments

Comments

@MintakaB
Copy link

Hi,
It was just to note that I can not see the command "Quarkus: Add extensions to current project:" in the drop down list.

OS: MacOS

VSCode:
Version: 1.86.2 (Universal)
Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda
Date: 2024-02-13T19:42:13.651Z
Electron: 27.2.3
ElectronBuildId: 26908389
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin x64 23.2.0

Quarkus Extension version: 1.17.0

Screenshot 2024-02-20 at 18 38 39

@fbricon
Copy link
Collaborator

fbricon commented Feb 20, 2024

Do you have a Quarkus project opened?

@MintakaB
Copy link
Author

hi, Yes, this is happening in all my three workspaces. It happens the same thing. No command to add new extensions to the project. It's a bit weird because it worked in the past!. Thank you for looking at the issue.

Screenshot 2024-02-21 at 11 40 15

@mproep
Copy link

mproep commented Mar 18, 2024

Hi, I think the http client from "axios", which is used in requestUtil.ts has some problem with https over http proxy. The problem is mentionend here: axios/axios#4531

For me it also the reason why the vscode-quarkus extension is failing in the last step of "Generate a Quarkus project" with the same message mentioned here: #292

It was working for me eigth month ago.

@Chealer
Copy link

Chealer commented Aug 6, 2024

Does this persist in VS Code 1.92+? If so, please provide a screenshot of a search for "quarkus:" in the keyboard shortcuts tab. For reference, with 1.17.0: image

@mproep
Copy link

mproep commented Aug 9, 2024

For me the problem still persists.

@angelozerr
Copy link
Contributor

@datho7561 have you an idea why we have this issue?

@Chealer
Copy link

Chealer commented Aug 9, 2024

For me nothing, the problem still persists

I cannot make sense of what you wrote... thanks anyway, but a screenshot would be clearer.

@mproep
Copy link

mproep commented Aug 9, 2024

For me nothing, the problem still persists

I cannot make sense of what you wrote... thanks anyway, but a screenshot would be clearer.

Sorry for the confusion. I've corrected my comment.
Here is a screenshot:
image

Creating a Quarkus project is also still failing in last step, where the extensions would be selected.
For Info I'm using http for HTTPS_PROXY in a company network

@Chealer
Copy link

Chealer commented Aug 9, 2024

Thank you @mproep

@mproep , @MintakaB: does this happen in a multi-root workspace? And if so, can you reproduce this in a single-root workspace (regular folder)?

@mproep
Copy link

mproep commented Aug 9, 2024

For me, it happens in single and multi root workspaces.

@Chealer
Copy link

Chealer commented Aug 9, 2024

Thanks @mproep
Just to be clear, does this happen in a single-root workspace which is a Quarkus project?

@mproep
Copy link

mproep commented Aug 9, 2024

Yes, the screenshot from above is from a single-root workspace.

@datho7561
Copy link
Contributor

I'll see if I can reproduce

@datho7561
Copy link
Contributor

What I'm seeing currently is that the Java extension is stuck activating. Until it finishes activating, we cannot properly detect that the current project is a Quarkus project. We'll need to figure out what's causing this. It could be either vscode-quarkus or vscode-java itself.

Creating a Quarkus project is also still failing in last step, where the extensions would be selected.
For Info I'm using http for HTTPS_PROXY in a company network

This is probably a separate issue given I can reproduce the first issue without using a proxy. Hopefully #711 (using the NodeJS built-in fetch instead of axios) can fix it. I'll clean up that PR.

@datho7561
Copy link
Contributor

I retried it after closing and reopening VS Code, and now I get "no quarkus projects were found in the current folder".

@datho7561
Copy link
Contributor

It suddenly started working again for me.

@datho7561
Copy link
Contributor

Sorry for the confusion. I've corrected my comment. Here is a screenshot:

@mproep from this screenshot it seems that vscode-quarkus cannot detect that the project is a Quarkus project since vscode-java never finishes starting. Is vscode-java running? There should be something that says "☕ Java: Ready" in the bottom bar if it has started properly.

Unfortunately, I haven't been able to reproduce this failure reliably. Maybe try closing and reopening VS Code? Sometimes if vscode-java gets stuck importing the project the first time around, it works the second time.

@Chealer
Copy link

Chealer commented Aug 13, 2024

Thank you @mproep
Could you please retitle this to something like:

Missing commands for existing Quarkus projects (Add extensions to current project, Debug current Quarkus project)

@angelozerr
Copy link
Contributor

angelozerr commented Aug 21, 2024

@mproep have you support

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

6 participants