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

IntelliJ Idea hangs intermittently when Amazon Q is enabled #5043

Open
spatanjali opened this issue Nov 4, 2024 · 0 comments
Open

IntelliJ Idea hangs intermittently when Amazon Q is enabled #5043

spatanjali opened this issue Nov 4, 2024 · 0 comments
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@spatanjali
Copy link

Describe the bug
Q is running multiple security scans that results in HTTP 429.

To reproduce
No specific steps are required. Just the normal usage of the IDE or keeping it opened results in the IDE getting hung with the below exception.

Failed to run security scan and display results. Caused by: CreateCodeScanException: Too many requests, please wait before trying again. (Service: CodeWhispererRuntime, Status Code: 429, Request ID: 6a897505-732d-449f-baa8-a71a5d526fee), status code: null, exception: CodeWhispererCodeScanServerException, request ID: nullJetbrains IDE: IntelliJ IDEA 2024.2.4, IDE version: IU-242.23726.103, 

software.aws.toolkits.jetbrains.services.codewhisperer.codescan.CodeWhispererCodeScanServerException: CreateCodeScanException: Too many requests, please wait before trying again. (Service: CodeWhispererRuntime, Status Code: 429, Request ID: 6a897505-732d-449f-baa8-a71a5d526fee)
	at software.aws.toolkits.jetbrains.services.codewhisperer.codescan.CodeWhispererCodeScanExceptionKt.codeScanServerException(CodeWhispererCodeScanException.kt:31)
	at software.aws.toolkits.jetbrains.services.codewhisperer.codescan.CodeWhispererCodeScanSession.createCodeScan(CodeWhispererCodeScanSession.kt:343)
	at software.aws.toolkits.jetbrains.services.codewhisperer.codescan.CodeWhispererCodeScanSession.run(CodeWhispererCodeScanSession.kt:137)
	at software.aws.toolkits.jetbrains.services.codewhisperer.codescan.CodeWhispererCodeScanManager$launchCodeScanCoroutine$1$3.invokeSuspend(CodeWhispererCodeScanManager.kt:254)
	at software.aws.toolkits.jetbrains.services.codewhisperer.codescan.CodeWhispererCodeScanManager$launchCodeScanCoroutine$1$3.invoke(CodeWhispererCodeScanManager.kt)
	at software.aws.toolkits.jetbrains.services.codewhisperer.codescan.CodeWhispererCodeScanManager$launchCodeScanCoroutine$1$3.invoke(CodeWhispererCodeScanManager.kt)
	at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturnIgnoreTimeout(Undispatched.kt:74)
	at kotlinx.coroutines.TimeoutKt.setupTimeout(Timeout.kt:148)
	at kotlinx.coroutines.TimeoutKt.withTimeout(Timeout.kt:43)
	at kotlinx.coroutines.time.TimeKt.withTimeout(Time.kt:42)
	at software.aws.toolkits.jetbrains.services.codewhisperer.codescan.CodeWhispererCodeScanManager$launchCodeScanCoroutine$1.invokeSuspend(CodeWhispererCodeScanManager.kt:250)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:735)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:732)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:400)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:732)
	at java.base/java.lang.Thread.run(Thread.java:1583)

Your Environment

  • OS: Windows 11
  • JetBrains product: IntelliJ Idea 2024.2.4
  • JetBrains product version: IU-242.23726.103
  • AWS Toolkit version: 3.37-242
  • SAM CLI version: N/A
  • JVM/Python version: JDK 21 (Adoptium)
@spatanjali spatanjali added the bug We can reproduce the issue and confirmed it is a bug. label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

1 participant