-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
delve support #15713
base: develop
Are you sure you want to change the base?
delve support #15713
Conversation
Is this a potential security risk? 🤔 exposing a debugger port by default seems like it could be unsafe. Afaik we do ship this image to NOPs |
AER Report: CI Coreaer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , Scheduled Run Frequency , Flakeguard Root Project / Get Tests To Run , lint , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Flakeguard Deployment Project , Core Tests (go_core_ccip_deployment_tests) , Core Tests (go_core_race_tests) , Core Tests (go_core_fuzz) , Flakeguard Root Project / Run Tests , Flakeguard Root Project / Report , Flakey Test Detection , SonarQube Scan 1. Error stopping job service:[go_core_ccip_deployment_tests]Source of Error:
Why: The error occurred because the job service attempted to stop a subservice that had already been stopped. This resulted in a panic due to the redundant stop operation. Suggested fix: Ensure that the service stop logic checks if the service is already stopped before attempting to stop it again. This can be done by adding a state check before the stop operation. 2. Error reading from connection:[go_core_ccip_deployment_tests]Source of Error:
Why: The error occurred because the connection was closed while there were still attempts to read from it, resulting in an EOF (End of File) error. Suggested fix: Ensure that all read operations are properly synchronized with the connection closure. Implement checks to confirm that the connection is open before attempting to read from it. 3. Error reading from connection:[go_core_ccip_deployment_tests]Source of Error:
Why: Similar to the previous error, this occurred because the connection was closed while read operations were still being attempted, leading to an EOF error. Suggested fix: Implement proper synchronization to ensure that read operations are only performed on open connections. Add checks to verify the connection status before reading. 4. Error reading from connection:[go_core_ccip_deployment_tests]Source of Error:
Why: This error is also due to attempts to read from a connection that has already been closed, resulting in an EOF error. Suggested fix: Similar to the previous fixes, ensure that read operations are synchronized with connection status checks to avoid reading from closed connections. |
Add
delve
support for plugins image