Page MenuHomePhabricator

[services] Tunnelbroker - Changes in Amqp messages testing to send and listen in different threads
ClosedPublic

Authored by max on Aug 4 2022, 12:36 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 20, 12:42 AM
Unknown Object (File)
Sun, Dec 15, 10:18 PM
Unknown Object (File)
Sun, Dec 15, 10:18 PM
Unknown Object (File)
Thu, Nov 28, 7:26 PM
Unknown Object (File)
Tue, Nov 26, 4:08 PM
Unknown Object (File)
Tue, Nov 26, 3:47 PM
Unknown Object (File)
Tue, Nov 26, 3:38 PM
Unknown Object (File)
Tue, Nov 26, 2:42 PM

Details

Summary

In real-world usage sending and receiving messages in the AMQP client (AMQP Manager) would be in different threads.
This diff changes sending messages from another than the main thread. Listening (message pop) is in blocking mode in the main thread without changes.

Related Linear task: ENG-1491

Test Plan

Successfully built using yarn run-tunnelbroker-service-in-sandbox command.
Passing all AMQP unit tests in the last diff D4749 in a stack.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

max held this revision as a draft.
max published this revision for review.Aug 4 2022, 4:55 PM
max edited the test plan for this revision. (Show Details)
tomek added inline comments.
services/tunnelbroker/test/AmqpManagerTest.cpp
41 ↗(On Diff #15409)

Is there a reason to not capture by reference?

This revision is now accepted and ready to land.Aug 9 2022, 9:35 AM

Rebase and merge on a master changes.

Minor fix with removing the ini file from the commit.

max added inline comments.
services/tunnelbroker/test/AmqpManagerTest.cpp
41 ↗(On Diff #15409)

Is there a reason to not capture by reference?

Yes, we can! I've made these changes. Thanks!