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
If the HTTP_PORT is blocked the server should not start. Currently, it appears the server attempts to start even if the port is in use which can lead to issues.
This issue proposes that the server should perform a check before starting to ensure the HTTP_PORT is available. If the port is blocked, the server should fail to start and log an error message.
This enhancement will improve the reliability of the application and prevent unexpected behavior.
The text was updated successfully, but these errors were encountered:
To address this issue, I will refactor the code to ensure that all required servers (gRPC, Pub/Sub, HTTP) are able to start successfully. If any of these servers fail to start, for example, due to a blocked port, we should shut down the entire application to maintain consistency and avoid partial availability.
If the HTTP_PORT is blocked the server should not start. Currently, it appears the server attempts to start even if the port is in use which can lead to issues.
This issue proposes that the server should perform a check before starting to ensure the HTTP_PORT is available. If the port is blocked, the server should fail to start and log an error message.
This enhancement will improve the reliability of the application and prevent unexpected behavior.
The text was updated successfully, but these errors were encountered: