-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore(deps): Bump Rust version to 1.80 #20949
Conversation
20476bb
to
7bc9dd7
Compare
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.
Nice, thank you!
@@ -25,7 +25,7 @@ pub fn data_dir() -> &'static Path { | |||
pub fn default_target() -> String { | |||
if cfg!(windows) { |
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.
Nit: could this be target_os = "windows"
for consistency?
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.
Maybe, but we use just windows
everywhere else. There are two special OS-type configs, unix
and windows
. In the case of unix
, it includes both Linux and macOS (and of course BSDs etc), but I'm not sure if windows
similarly includes some other sub-targets.
Datadog ReportBranch report: ❌ 1 Failed (0 Known Flaky), 2396 Passed, 0 Skipped, 4m 4.39s Total Time ❌ Failed Tests (1)
|
@@ -2,7 +2,6 @@ | |||
feature = "sources-apache_metrics", | |||
feature = "sources-aws_ecs_metrics", | |||
feature = "sources-aws_kinesis_firehose", | |||
feature = "sources-http-client", |
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.
Does this line get removed or just corrected to feature = "sources-http_client",
with an underscore?
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.
That's a good question. I had initially just corrected it, but since the feature before correction was always false, it obviously wasn't necessary so I just removed it.
This has introduced a problem with the |
Could you do the same thing for config generation that you did for tests?
|
That's a possibility, but |
Ah, for some reason I was thinking this source was only included on *nix, but I see it exists on Windows too. Maybe it could conditionally open |
The latest attempt still doesn't work, giving the error: |
Oddly I don't get that error running the tests locally 🤔 |
Update: I can reproduce on Linux. |
Removing this explicit close seems to fix it:
I'm not sure what else might be closing the fd before that line though 🤔 |
Actually it does. Spooky action at a distance. |
Thanks for taking this across the finish line! |
@@ -163,7 +163,7 @@ impl TransformContext { | |||
} | |||
} | |||
|
|||
#[cfg(any(test, feature = "test"))] | |||
#[cfg(test)] |
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.
This might break other users who use the test
feature.
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.
I believe that ended up complaining about an unreachable pub
item, meaning it can't actually be used outside of vector as it stands.
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.
AFAICT that is only ever called from src/transforms/remap.rs
in its test code, so it being unreachable unused code when built with just the test
feature tracks.
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.
Interesting, TransformContext
is exposed though. The new_test
function only has one usage and all fields are pub
already, maybe it can be deleted/refactored.
src/config/watcher.rs
Outdated
@@ -14,7 +14,8 @@ use crate::Error; | |||
/// But, config and topology reload logic can handle: | |||
/// - Invalid config, caused either by user or by data race. | |||
/// - Frequent changes, caused by user/editor modifying/saving file in small chunks. | |||
/// so we can use smaller, more responsive delay. | |||
/// so we can use smaller, more responsive delay. | |||
#[cfg(unix)] |
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.
Could this break macOS builds?
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.
Hmm, I could have sworn I needed to add that to fix a clippy
issue, but it's not there now and it's obviously bogus since the constant is used unconditionally below.
Let's address this #20949 (comment) before merging. |
Oops, fixed it in c1fd64d and forgot to push. |
Regression Detector ResultsRun ID: 230ddd7e-d8b4-41ad-b49d-3e1674e848da Metrics dashboard Baseline: a1edf90 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
❌ | file_to_blackhole | egress throughput | -18.50 | [-24.72, -12.29] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +4.05 | [+3.93, +4.18] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +3.13 | [+3.02, +3.25] | |
➖ | http_elasticsearch | ingress throughput | +2.77 | [+2.58, +2.96] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +2.59 | [+2.47, +2.71] | |
➖ | http_to_http_acks | ingress throughput | +2.53 | [+1.28, +3.77] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +2.44 | [+2.22, +2.65] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | +2.34 | [+2.18, +2.50] | |
➖ | syslog_loki | ingress throughput | +1.62 | [+1.53, +1.70] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.02 | [-0.07, +0.11] | |
➖ | http_to_http_json | ingress throughput | +0.02 | [-0.01, +0.05] | |
➖ | http_to_http_noack | ingress throughput | -0.00 | [-0.02, +0.02] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.11, +0.10] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.03 | [-0.12, +0.06] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -0.04 | [-0.15, +0.07] | |
➖ | otlp_http_to_blackhole | ingress throughput | -0.13 | [-0.28, +0.02] | |
➖ | fluent_elasticsearch | ingress throughput | -0.25 | [-0.74, +0.24] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -0.25 | [-0.37, -0.14] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -0.30 | [-0.38, -0.23] | |
➖ | syslog_humio_logs | ingress throughput | -0.31 | [-0.41, -0.21] | |
➖ | http_text_to_http_json | ingress throughput | -0.35 | [-0.49, -0.21] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | -0.40 | [-0.52, -0.28] | |
➖ | http_to_s3 | ingress throughput | -0.51 | [-0.78, -0.24] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -0.58 | [-0.73, -0.43] | |
➖ | splunk_hec_route_s3 | ingress throughput | -2.45 | [-2.76, -2.14] | |
➖ | socket_to_socket_blackhole | ingress throughput | -2.64 | [-2.72, -2.57] | |
❌ | file_to_blackhole | egress throughput | -18.50 | [-24.72, -12.29] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
Regression Detector ResultsRun ID: 5bb76055-ea83-496f-8277-03b9b9ede069 Metrics dashboard Baseline: 22c23c3 Performance changes are noted in the perf column of each table:
Significant changes in experiment optimization goalsConfidence level: 90.00%
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | file_to_blackhole | egress throughput | -5.46 | [-12.33, +1.42] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | syslog_log2metric_humio_metrics | ingress throughput | +6.66 | [+6.54, +6.79] | |
➖ | otlp_http_to_blackhole | ingress throughput | +3.79 | [+3.66, +3.93] | |
➖ | socket_to_socket_blackhole | ingress throughput | +3.04 | [+2.95, +3.13] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +2.52 | [+2.33, +2.71] | |
➖ | http_text_to_http_json | ingress throughput | +1.88 | [+1.75, +2.01] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | +1.78 | [+1.56, +2.01] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | +1.04 | [+0.93, +1.16] | |
➖ | http_to_s3 | ingress throughput | +0.78 | [+0.50, +1.05] | |
➖ | http_to_http_noack | ingress throughput | +0.13 | [+0.06, +0.21] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +0.06 | [-0.05, +0.17] | |
➖ | http_to_http_json | ingress throughput | +0.03 | [-0.02, +0.07] | |
➖ | http_to_http_acks | ingress throughput | +0.02 | [-1.18, +1.23] | |
➖ | splunk_hec_route_s3 | ingress throughput | +0.00 | [-0.30, +0.30] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.11, +0.11] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.01 | [-0.09, +0.08] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.01 | [-0.11, +0.09] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -0.02 | [-0.18, +0.15] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | -0.38 | [-0.45, -0.30] | |
➖ | syslog_humio_logs | ingress throughput | -0.41 | [-0.51, -0.31] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | -0.51 | [-0.61, -0.40] | |
➖ | syslog_loki | ingress throughput | -0.56 | [-0.66, -0.47] | |
➖ | fluent_elasticsearch | ingress throughput | -0.59 | [-1.08, -0.09] | |
➖ | http_elasticsearch | ingress throughput | -0.80 | [-0.96, -0.64] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -0.86 | [-0.97, -0.75] | |
➖ | syslog_splunk_hec_logs | ingress throughput | -1.00 | [-1.10, -0.90] | |
➖ | file_to_blackhole | egress throughput | -5.46 | [-12.33, +1.42] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
Closes: #21127