Duet AI feature doesn't work in PyCharm 2023.2.2

[hclockzz]

I have tested with Duet AI features on VS Code, and it's working as expected. While in PyCharm, code generation is not working. Can follow this link, https://cloud.google.com/code/docs/intellij/write-code-duet-ai#prompt-duet-ai-in-code-file, to test with it. No error logs and notifications when hit the icon for code generation (a pen with a star), but just no reaction.

Expected Behavior

how it works in VSCode

Actual Behavior

No response and reaction

Additional Information

• IDE type & version (e.g. IntelliJ, Pycharm): PyCharm 2023.2.2 (Community Edition, Build #PC-232.9921.89, built on October 1, 2023)
• Cloud Code version (Settings > Plugins > Cloud Code): 23.10.1
• Cloud SDK (Settings > Cloud Code > Cloud SDK)
  • Are you allowing the plugin to manage the Cloud SDK: No
  • Version of the Cloud SDK: 416.0.0
• Skaffold version (If you are using Kubernetes features; Settings > Cloud Code > Kubernetes): v2.7.1
• Operating System: OSX 13.6 (22G120)

Feel free to deviate from this template as needed, especially if you are submitting a feature request.

[etanshaul]

@hclockzz thanks for the report. We have several fixing coming around feedback / error handling.

In the meantime, to figure out this specific issue, could you please share the logs? The best way to do this:

1) Click the magic wand to trigger something from Duet 2) Use the Duet status bar to submit a feedback report (which will automatically attach the logs):

Some other things to check:

• ensure that you have your GCP project entered in the Duet AI settings. To get there, use the same status bar above > Settings. And ensure the Cloud Project field is populated with the correct GCP project where Duet AI is enabled.

[hclockzz]

I did side-by-side comparison with vscode and pycharm setting and find out the issue. It turns out may relate to two things:

• The most straightforward one is the project field needs to be project id, not just the project name. But I have tried with project id before, so the issue may also relate to the second thing.
• I switch Cloud SDK from "use a custom local installation" to "Allow the plugin to manage and install the Cloud SDK", and then the IDE installed a newer version.

I am not in favor of making dependencies managed by a plugin in real development. But at least this issue is resolved by this way.

[etanshaul]

I switch Cloud SDK from "use a custom local installation" to "Allow the plugin to manage and install the Cloud SDK", and then the IDE installed a newer version.

This is interesting. There is no reliance by any Duet features on the cloud sdk at all - you don't even need it installed. We'll double check though

Update: I just tested this quickly and can confirm that Duet works without having the plugin manage any dependencies. Now that you have Duet working, would you mind trying to unset managed dependencies and seeing if it continues to work? thanks.

[etanshaul]

The most straightforward one is the project field needs to be project id, not just the project name. But I have tried with project id before, so the issue may also relate to the second thing.

When you use the project selection widget, does it do the right thing?

(we'll double check on the name vs id requirement for freeform text entry; update - you are right, this field needs ID, not name. Mainly because ID is unique but name is not. We'll update the wording on this text field to make it clearer. Great callout.).

[ivanporty]

Closing as we didn't have more comments, and significantly improved onboarding process with our 23.10.2 release.