Bump github.com/miekg/dns from 1.1.55 to 1.1.57

[dependabot[bot]]

trafficstars

Bumps github.com/miekg/dns from 1.1.55 to 1.1.57.

Commits

• 836bea2 Release 1.1.57
• 257e89e feat: add support for ReuseAddr (#1510)
• 3d593a6 Swap closing order in inAxfr and inIxfr (#1511)
• 5d3f81b Remove slurpRemainder TODO from (*ZoneParser).Next (#1508)
• a16092f Use strings.Builder in endingToString (#1506)
• 3996b17 Avoid using a goto loop in unpackDataOpt (#1505)
• 1c418a3 Use cloneSlice in unpackDataA and unpackDataAAAA (#1504)
• 6836ba8 Eliminate tmp buffer from packOctetString (#1503)
• 9657fe6 Cleanup IsRRSet (#1502)
• 02e9e72 Avoid using strings.Split (#1501)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[pr-commenter[bot]]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: ef3578d0-a4d8-4533-a705-481d07a0f651
Baseline: a3b8e6d0b8e8b24a3750050ca9f6be9d72a95bd8
Comparison: 492f8981f833ebba0d60afd6bf1a29fae10d0206
Total datadog-agent CPUs: 7

Explanation

A regression test is an integrated performance test for datadog-agent in a repeatable rig, with varying configuration for datadog-agent. What follows is a statistical summary of a brief datadog-agent run for each configuration across SHAs given above. The goal of these tests are to determine quickly if datadog-agent performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%.

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
file_tree	egress throughput	+0.32	[-1.58, +2.21]	21.77%
otel_to_otel_logs	ingress throughput	+0.12	[-1.45, +1.69]	10.07%
tcp_syslog_to_blackhole	ingress throughput	+0.12	[-0.01, +0.25]	87.74%
uds_dogstatsd_to_api	ingress throughput	+0.05	[-0.14, +0.23]	33.16%
file_to_blackhole	egress throughput	+0.05	[-0.97, +1.06]	6.16%
dogstatsd_string_interner_8MiB_10k	ingress throughput	+0.01	[-0.03, +0.05]	30.12%
dogstatsd_string_interner_8MiB_100	ingress throughput	+0.00	[-0.12, +0.13]	2.91%
tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.13, +0.14]	2.09%
dogstatsd_string_interner_8MiB_50k	ingress throughput	+0.00	[-0.04, +0.04]	5.43%
dogstatsd_string_interner_128MiB_1k	ingress throughput	+0.00	[-0.13, +0.14]	1.00%
trace_agent_json	ingress throughput	+0.00	[-0.13, +0.13]	0.59%
dogstatsd_string_interner_128MiB_100	ingress throughput	+0.00	[-0.14, +0.14]	0.20%
dogstatsd_string_interner_64MiB_1k	ingress throughput	-0.00	[-0.13, +0.13]	0.46%
dogstatsd_string_interner_64MiB_100	ingress throughput	-0.00	[-0.14, +0.14]	0.65%
trace_agent_msgpack	ingress throughput	-0.00	[-0.12, +0.12]	2.41%
dogstatsd_string_interner_8MiB_1k	ingress throughput	-0.01	[-0.11, +0.10]	7.04%
dogstatsd_string_interner_8MiB_100k	ingress throughput	-0.02	[-0.07, +0.03]	40.71%
idle	egress throughput	-0.21	[-2.68, +2.25]	11.38%

[paulcacheux]

@dependabot recreate

[dependabot[bot]]

Looks like github.com/miekg/dns is up-to-date now, so this is no longer needed.