Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Currently, BulwarkProcessor can fail silently if it tries to bind to a port already in use #274

Closed
sporkmonger opened this issue Apr 9, 2024 · 0 comments · Fixed by #355
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/testing Categorizes issue or PR as related to testing. kind/usability Categorizes issue or PR as related to improving some aspect of usability.
Milestone

Comments

@sporkmonger
Copy link
Contributor

Notably this can happen in the integration tests, since they currently use the default port. The port used by tests should probably be changed to avoid this collision with dev servers, but also tests should fail much earlier if this happens.

@sporkmonger sporkmonger added kind/bug Categorizes issue or PR as related to a bug. kind/usability Categorizes issue or PR as related to improving some aspect of usability. kind/testing Categorizes issue or PR as related to testing. labels Apr 9, 2024
@sporkmonger sporkmonger added this to the Release 0.6.0 milestone Apr 9, 2024
@sporkmonger sporkmonger self-assigned this Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/testing Categorizes issue or PR as related to testing. kind/usability Categorizes issue or PR as related to improving some aspect of usability.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant