Details
Run the tunnelbroker integration suite. First start docker, then:
nix develop comm-dev services start (cd services/tunnelbroker && RUST_LOG=debug cargo run) (cd services/commtest && cargo test --test tunnelbroker_integration_test)
Diff Detail
- Repository
- rCOMM Comm
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
services/tunnelbroker/src/websockets/session.rs | ||
---|---|---|
88–89 ↗ | (On Diff #27673) | I'd like to understand this better.
|
services/tunnelbroker/src/websockets/session.rs | ||
---|---|---|
88–89 ↗ | (On Diff #27673) |
It is possible. The action is idempotent, I can restart tunnelbroker, and redo the logic and it's successful the second time. The options relate to these options, since we are publishing with immediate = true, a lot of these options don't matter as they will just be deleted and kicked back to us if they fail to deliver.
I would assume that we would get an error when awaiting the confirmation. But I haven't tested this scenario.
Rabbitmq allows some flexibility. In our case we have a simple one-to-one correlation of messages routing-key to queue names. However, amqp allows some flexibility, this post should help: https://www.cloudamqp.com/blog/part4-rabbitmq-for-beginners-exchanges-routing-keys-bindings.html |
39 ↗ | (On Diff #27629) | This was refactored out from the previous work. Previously, the function handled all message requests, but now is scoped down to just the first message. |
services/tunnelbroker/src/websockets/session.rs | ||
---|---|---|
88–89 ↗ | (On Diff #27673) | Thanks for the detailed explanation @jon! |