Tcl Library Source Code

View Ticket
Login
2026-11-16
00:06 • Ticket [187a6fa7ae] DNS client not handling partial TCP responses correctly status still Open with 3 other changes artifact: f7e75785c2 user: serhiy.storchaka
00:06 • Ticket [022bca0ff5] Fix for dns: can't read "state(size)": no such element in array status still Open with 3 other changes artifact: ee1295c5a1 user: serhiy.storchaka
2026-11-15
23:36
Fix [187a6fa7ae], [022bca0ff5]: the dns client did not handle TCP replies that arrive in several reads. Buffer until the 2-byte length has arrived, read the length unsigned, and take the id from the reply. leaf check-in: 79c8191d74 user: serhiy.storchaka tags: dns-tcp-partial-reads
2024-04-22
15:10 • Add attachment dns.patch to ticket [022bca0ff5] artifact: bfcdff3264 user: DasBrain
15:09 • New ticket [022bca0ff5] Fix for dns: can't read "state(size)": no such element in array. artifact: 14b0190a7b user: DasBrain

Ticket UUID: 022bca0ff5aa69095e2b83727236a50e152a4ae1
Title: Fix for dns: can't read "state(size)": no such element in array
Type: Patch Version: DNS 1.4.1
Submitter: DasBrain Created on: 2024-04-22 15:09:03
Subsystem: dns Assigned To: nobody
Priority: 5 Medium Severity: Important
Status: Open Last Modified: 2026-11-16 00:06:14
Resolution: None Closed By: nobody
    Closed on:
Description:
I noticed that the dns lookup would sometimes error with can't read "state(size)": no such element in array

The only way I can think of why this happens is when it reads exactly 1 byte from the tcp socket.

So, I made the stuff a bit more robust.
User Comments: serhiy.storchaka added on 2026-11-16 00:06:14:

Duplicate of [187a6fa7ae]; proposed fix in branch dns-tcp-partial-reads. The attachment isn't in my clone, so I could not compare it with that fix.


Attachments: