mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #2432] dns-test: Stop using TTY in docker exec #989
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#989
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @divergentdave on GitHub (Sep 5, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2432
Is your feature request related to a problem? Please describe.
I kept stress-testing one conformance test after fixing #2421, and I found that sometimes the output from
ldns-signzonewould get truncated, either losing the second line, or losing two columns from one of the lines. (less frequently than the seconds underflow issue, but still repeatable, given enough time) There was no message on stderr indicating why, and the status code was still successful. I confirmed the container was still running by exec-ingidafterldns-signzone, and saw that still worked when the signed zone output got truncated.Describe the solution you'd like
I tried removing the
-tflag fromdocker execin the relevant place, and I haven't seen any more truncation issues from this command. I've seen a few complaints of other weird output truncation issues withdocker exec -twhile searching around the internet, but didn't find a complete explanation. At any rate, not using a TTY where we don't need it should simplify things.One additional benefit of not using
-tis thatdocker execno longer combines the process's stdout and stderr into its own stdout, so we could remove some hacks intshark.rsthat redirect one stream to a file, andcatit later. The downside is that we have to remove those hacks, and in the case oftshark, read from both stdout and stderr simultaneously on two threads, so processes doesn't get blocked on full buffers.Describe alternatives you've considered
Keep the status quo