Conversation
Review Summary by QodoFix false failure flag when signature is fetched from server
WalkthroughsDescription• Fix signature fetch logic to prevent false failures - Only update signature if server received one - Reset error failure flag when signature is fetched • Add test fixtures for OAuth catalog configuration • Add end-to-end test for catalog server scanning Diagramflowchart LR
A["Server signature missing locally"] -->|"Check if remote has signature"| B["Remote signature exists?"]
B -->|"Yes"| C["Update local signature"]
C --> D["Reset error is_failure flag"]
D --> E["Success"]
B -->|"No"| F["Skip update"]
File Changes1. src/agent_scan/verify_api.py
|
Code Review by QodoSorry, something went wrongWe weren't able to complete the code review on our side. Please try againⓘ The new review experience is currently in Beta. Learn more |
CI Feedback 🧐A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
| if server_given.signature is None and server_received.signature is not None: | ||
| server_given.signature = server_received.signature | ||
| if server_given.error is not None: | ||
| server_given.error.is_failure = False |
There was a problem hiding this comment.
Should we attach some metadata with the error here or the server so that we know that we failed to start the server but it matched something in the catalog? It can get confusing in the platform otherwise all fields look like the server failed to start but is_failure is set to False.
9a622a9 to
47d1c14
Compare
No description provided.