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
Can this bug be reproduced with the latest release?
Option Yes
What did you do?
As shown in the image, we have two HTTP servers: one for web interfaces and another for monitoring services. However, if both are started using the Server.Run method, a race condition occurs. Shouldn't preBindItems be an attribute of the Server rather than a global variable?
What did you see happen?
Here is our code:
Step 1: Use go func to register the monitoring HTTP service routes and start the service.
Step 2: Register the web routes and start the web service.
Result: Both HTTP services concurrently write to and read from the global preBindItems variable, leading to a race condition.
What did you expect to see?
Shouldn't preBindItems be an attribute of the Server rather than a global variable?
The text was updated successfully, but these errors were encountered:
Go version
go 1.19
GoFrame version
v2.5.7
Can this bug be reproduced with the latest release?
Option Yes
What did you do?
As shown in the image, we have two HTTP servers: one for web interfaces and another for monitoring services. However, if both are started using the Server.Run method, a race condition occurs. Shouldn't preBindItems be an attribute of the Server rather than a global variable?
What did you see happen?
Here is our code:
Step 1: Use go func to register the monitoring HTTP service routes and start the service.
Step 2: Register the web routes and start the web service.
Result: Both HTTP services concurrently write to and read from the global preBindItems variable, leading to a race condition.
What did you expect to see?
Shouldn't preBindItems be an attribute of the Server rather than a global variable?
The text was updated successfully, but these errors were encountered: