-
Notifications
You must be signed in to change notification settings - Fork 127
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
Add JDC/S initializers in integration tests #1226
base: main
Are you sure you want to change the base?
Add JDC/S initializers in integration tests #1226
Conversation
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Bencher Report
Click to view all benchmark results
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1226 +/- ##
=======================================
Coverage 19.36% 19.36%
=======================================
Files 164 164
Lines 10811 10811
=======================================
Hits 2094 2094
Misses 8717 8717
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Why have you had to create all those new config structs? How was it working before?
pub async fn start_jdc( | ||
pool_address: SocketAddr, | ||
tp_address: SocketAddr, | ||
jds_address: SocketAddr, | ||
) -> SocketAddr { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please see #1234
jdc_address | ||
} | ||
|
||
pub async fn start_jds(tp_address: SocketAddr) -> SocketAddr { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please see #1234
I pulled this branch and tried to do some quick experimentation, where my goal was to put a sniffer between JDC and JDS to look into the messages they are exchanging. Here's my test: #[tokio::test]
async fn sniff_jdc_jds() {
let sniffer_addr = common::get_available_address();
let tp_addr = common::get_available_address();
let _jdc_addr = common::get_available_address();
let jds_addr = common::get_available_address();
let pool_addr = common::get_available_address();
let _tp = common::start_template_provider(tp_addr.port()).await;
let _pool = common::start_pool(Some(pool_addr), Some(tp_addr)).await;
let _jds = common::start_jds(tp_addr).await;
let sniffer = common::start_sniffer(sniffer_addr, jds_addr).await;
let _jdc = common::start_jdc(pool_addr, tp_addr, sniffer_addr).await;
let d = sniffer.next_downstream_message();
let u = sniffer.next_upstream_message();
println!("d: {:?}", d);
println!("u: {:?}", u);
} but when I tried to run it, I got a nasty panic... did I make some mistake on the test above, or is there something wrong with the APIs? The log line that really stand out is:
which is coming from anyways, here's the full panic logs:
|
resolves #1223