Log: Locally bound server address

[ReinierMaas]

Logging the actually bound port is good for debug-ability:

$ target/debug/opsqueue --port 0
Starting Opsqueue v0.32.0
Hello, hello!
2025-12-23T14:33:12.068100Z  INFO ThreadId(01) opsqueue: 24: Finished setting up tracing subscriber
2025-12-23T14:33:12.069220Z  INFO ThreadId(01) opsqueue::db: 385: Starting up using existing sqlite DB opsqueue.db
2025-12-23T14:33:12.073634Z  INFO ThreadId(01) opsqueue::db: 390: Migrating backing DB
2025-12-23T14:33:12.073792Z  INFO ThreadId(01) opsqueue::db: 397: Finished migrating backing DB
2025-12-23T14:33:12.073817Z  INFO ThreadId(01) opsqueue: 66: Startup of Opsqueue (v0.32.0) complete.
2025-12-23T14:33:12.074275Z  INFO ThreadId(01) opsqueue::server: 48: Server listening on 0.0.0.0:45953
...

[Copilot]

Pull request overview

This PR improves debuggability by logging the actual bound server address instead of the requested address. This is particularly useful when using port 0 (ephemeral port assignment), where the OS assigns an available port at runtime.

Key Changes:

• Moved server address logging from application startup to after TCP listener binding
• Log now displays the actual bound address (e.g., "0.0.0.0:45953") rather than the requested address
• Added error handling for cases where the locally bound address cannot be retrieved

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
opsqueue/src/server.rs	Added logging of actual bound address using listener.local_addr() with error handling; also modified retry policy (unrelated change)
opsqueue/app/main.rs	Removed old logging statement that showed requested address instead of actual bound address
default.nix	Added "rust-src" extension to Rust toolchain (unrelated change)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.