Conversation
|
This PR was marked stale due to lack of activity. |
|
why was this marked as stale? Plus there are not reviewers ... |
|
This PR was marked stale due to lack of activity. |
|
any update on this? It keeps getting labeled as stale |
|
This PR was marked stale due to lack of activity. |
|
why is this stale if it is marked as ready for testing |
|
This PR was marked stale due to lack of activity. |
|
@zhihonl is this going to be merged? it keeps getting marked as stale and I cannot see any activity/interest in this PR |
|
This PR was marked stale due to lack of activity. |
|
This PR was marked stale due to lack of activity. |
|
This PR was marked stale due to lack of activity. |
|
This PR was marked stale due to lack of activity. |
|
@mitali-salvi any update on this? There seems to be unrelated errors in your pipelines: Anything you need me to update? |
|
@pete911 respect for your perseverance! :-) |
Description of the issue
Describe the problem or feature in addition to a link to the issues.
Description of changes
server.Close only closes connections and does not wait for server shutdown. We can see this behaviour in the logs:
http: Server closederror is coming fromListenAndServeTLS(s.shuttingDown()check, this means that the server is not shut down. After multiple tries, we get error fromnet.Listen. By usingShutdown(...)instead ofClose(), the code is going to wait for server shutdown, not just for connections to be closed.License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Existing tests were re-run and are working. This change does not introduce any new behaviour.
Requirements
Before commiting your code, please do the following steps.
make fmtandmake fmt-shmake lintIntegration Tests
To run integration tests against this PR, add the
ready for testinglabel.