- Notifications
You must be signed in to change notification settings - Fork16
impl: prefer agent name over agent id in URI handler#585
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Agent name is easier to resolve in jetbrains gateway module
Error reporting should also prefer agent name over the agent id.
Test cases related to agent matching have to be updatednow that agent name is preferred over agent id.
github-actionsbot commentedOct 1, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
Qodana Community for JVM34 new problems were found
💡 Qodana analysis was run in the pull request mode: only the changed files were checked View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get -name:'Qodana Scan'uses:JetBrains/qodana-action@v2023.3.2with:upload-result:true Contact Qodana teamContact us atqodana-support@jetbrains.com
|
Rewrote the entire test to be easier to read and debug.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
wonderful 🎉
9bff367
intomainUh oh!
There was an error while loading.Please reload this page.
Agent name is easier to resolve in jetbrains gateway module and provides more safety.
Reported by customer on Zendesk ticket 4391