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

JetBrains: Guardrail is not available in Enterprise account. #1483

Closed
jay-fibi opened this issue May 10, 2024 · 3 comments
Closed

JetBrains: Guardrail is not available in Enterprise account. #1483

jay-fibi opened this issue May 10, 2024 · 3 comments
Assignees
Labels
bug Something isn't working fibilabs-qa

Comments

@jay-fibi
Copy link
Collaborator

jay-fibi commented May 10, 2024

Cody Version

v5.5.10-nightly

IDE Information

PyCharm 2023.3.3 (Community Edition)
Build #PC-233.13763.11, built on January 26, 2024
Runtime version: 17.0.9+7-b1087.11 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.3
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Metal Rendering is ON
Non-Bundled Plugins:
com.sourcegraph.jetbrains (5.5.10-nightly)

Describe the bug

Platform: macOS

Steps to reproduce:

  1. Have Cody plugin installed in your JB PyCharm editor
  2. Login to Cody with Enterprise user
  3. Open any source code file and select "Generate Test" command
  4. Verify the code snippet generated in Cody response

Observed behavior:

Guardrail is not available in the code snippet generated in response.

Expected behavior

Guardrail should be available for Enterprise account.

Additional context

Screenshot:

Screenshot 2024-05-11 at 12 56 16 AM

@jay-fibi jay-fibi added bug Something isn't working fibilabs-qa fibilabs-qa-p0 labels May 10, 2024
@dominiccooney
Copy link
Contributor

@kalanchan , can you look into what's going on with sg04? It answers the following GraphQL with "" which disables Guardrails and this is blocking testing. (It can't answer site { productVersion } either...)

query CodyConfigFeaturesResponse {
    site {
        codyConfigFeatures {
            chat
            autoComplete
            commands
            attribution
        }
    }
}

@dominiccooney
Copy link
Contributor

Taking the P0 label off this since I just tested guardrails on s2 and the feature is working there. (Well... it is not triggering any detections for me 🤷 but the label is present in the view, all the code to hit the backend and display a response from it is running.)

Copy link
Contributor

I'm closing this as there has been no activity. Every indication I have is that the feature is working.

@dominiccooney dominiccooney closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fibilabs-qa
Projects
None yet
Development

No branches or pull requests

3 participants