Skip to content

fix reload server method#1957

Merged
sky333999 merged 15 commits intoaws:mainfrom
pete911:address-already-in-use
Apr 15, 2026
Merged

fix reload server method#1957
sky333999 merged 15 commits intoaws:mainfrom
pete911:address-already-in-use

Conversation

@pete911
Copy link
Copy Markdown
Contributor

@pete911 pete911 commented Dec 11, 2025

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:

failed to serve and listen","error":"listen tcp :4311: bind: address already in use
failed to serve and listen","error":"http: Server closed"
failed to serve and listen","error":"http: Server closed"
failed to serve and listen","error":"http: Server closed"

http: Server closed error is coming from ListenAndServeTLS (s.shuttingDown() check, this means that the server is not shut down. After multiple tries, we get error from net.Listen. By using Shutdown(...) instead of Close(), 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.

  1. Run make fmt and make fmt-sh
  2. Run make lint

Integration Tests

To run integration tests against this PR, add the ready for testing label.

@pete911 pete911 requested a review from a team as a code owner December 11, 2025 17:08
@github-actions
Copy link
Copy Markdown
Contributor

This PR was marked stale due to lack of activity.

@github-actions github-actions Bot added the Stale label Dec 19, 2025
@pete911
Copy link
Copy Markdown
Contributor Author

pete911 commented Dec 19, 2025

why was this marked as stale? Plus there are not reviewers ...

@github-actions github-actions Bot removed the Stale label Dec 20, 2025
@github-actions
Copy link
Copy Markdown
Contributor

This PR was marked stale due to lack of activity.

@github-actions github-actions Bot added the Stale label Dec 30, 2025
@pete911
Copy link
Copy Markdown
Contributor Author

pete911 commented Dec 30, 2025

any update on this? It keeps getting labeled as stale

@github-actions github-actions Bot removed the Stale label Dec 31, 2025
@zhihonl zhihonl added the ready for testing Indicates this PR is ready for integration tests to run label Dec 31, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 8, 2026

This PR was marked stale due to lack of activity.

@github-actions github-actions Bot added the Stale label Jan 8, 2026
@pete911
Copy link
Copy Markdown
Contributor Author

pete911 commented Jan 9, 2026

why is this stale if it is marked as ready for testing

@github-actions github-actions Bot removed the Stale label Jan 10, 2026
@github-actions
Copy link
Copy Markdown
Contributor

This PR was marked stale due to lack of activity.

@github-actions github-actions Bot added the Stale label Jan 20, 2026
@pete911
Copy link
Copy Markdown
Contributor Author

pete911 commented Jan 20, 2026

@zhihonl is this going to be merged? it keeps getting marked as stale and I cannot see any activity/interest in this PR

@github-actions github-actions Bot removed the Stale label Jan 21, 2026
@github-actions
Copy link
Copy Markdown
Contributor

This PR was marked stale due to lack of activity.

@github-actions github-actions Bot added the Stale label Jan 28, 2026
@github-actions github-actions Bot removed the Stale label Jan 31, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Feb 7, 2026

This PR was marked stale due to lack of activity.

@github-actions github-actions Bot added the Stale label Feb 7, 2026
@github-actions github-actions Bot removed the Stale label Feb 8, 2026
@github-actions
Copy link
Copy Markdown
Contributor

This PR was marked stale due to lack of activity.

@github-actions github-actions Bot added the Stale label Feb 27, 2026
@github-actions github-actions Bot removed the Stale label Feb 28, 2026
@github-actions
Copy link
Copy Markdown
Contributor

This PR was marked stale due to lack of activity.

@github-actions github-actions Bot added the Stale label Mar 22, 2026
@github-actions github-actions Bot removed the Stale label Mar 28, 2026
Comment thread extension/server/extension.go Outdated
Comment thread extension/server/extension.go Outdated
@pete911 pete911 requested a review from mitali-salvi April 10, 2026 18:51
@mitali-salvi mitali-salvi requested a review from movence April 13, 2026 20:41
@pete911
Copy link
Copy Markdown
Contributor Author

pete911 commented Apr 14, 2026

@mitali-salvi any update on this? There seems to be unrelated errors in your pipelines:

Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers

Anything you need me to update?

@sky333999 sky333999 merged commit f347e7f into aws:main Apr 15, 2026
25 of 30 checks passed
@jreisinger
Copy link
Copy Markdown

@pete911 respect for your perseverance! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready for testing Indicates this PR is ready for integration tests to run

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants