You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During automated testing with the Go race detector enabled, we've identified various race conditions resulting from concurrent access by multiple goroutines in the plugin system.
Related functions can be executed concurrently by multiple goroutines without causing race conditions. This could involve implementing locks or other synchronization techniques around shared resource accesses
Verify that executing pre-hooks and post-hooks in parallel scenarios does not lead to race conditions.
All unit and integration tests related to the plugin system must pass consistently without triggering race condition warnings under the -race flag.
Benchmark tests should confirm that the fixes for race conditions do not adversely affect the performance of the plugin system
Expected Outcomes:
The CLI must correctly handle concurrent plugin operations, such as simultaneous plugin loading, execution, and unloading, without leading to race conditions or inconsistent states.
Notes:
A contributor with more experience in Go concurrency should refine this issue.
The text was updated successfully, but these errors were encountered:
Context:
During automated testing with the Go race detector enabled, we've identified various race conditions resulting from concurrent access by multiple goroutines in the plugin system.
Follows #4060
Acceptance Criteria:
-race
flag.Expected Outcomes:
The CLI must correctly handle concurrent plugin operations, such as simultaneous plugin loading, execution, and unloading, without leading to race conditions or inconsistent states.
Notes:
A contributor with more experience in Go concurrency should refine this issue.
The text was updated successfully, but these errors were encountered: