Open tcllib tickets: Not a bug

Triage of all 509 open and Pending tickets of tcllib (bugs, patches and feature requests) on 2026-11-15. Each ticket was checked against tcllib trunk on Linux with Tcl 9.1, 9.0, 8.6 and 8.5, using local servers for the network modules and a Windows 11 VM for Windows-only tickets. Outdated, superseded, duplicate and misfiled tickets are listed separately. Rows marked patch link to a prototype fix with a regression test (147 in all, in tcllib-triage/prototypes). Updated 2026-11-16.

Not a bug 23

⬜dce2cb7dc42026Design a blueprint for all the Internet security, 1, cloud storage offline 2, security data cookies 3 device learning mechanism for user biometricNOT-A-BUG (spam / unrelated request)

Open ticket dce2cb7dc4 · RFE · Build System & Testing · filed 2026-06-11

Full verdict

NOT-A-BUG (spam / unrelated request)

  • Module none
  • Tested n/a
  • Cause n/a
  • Prototype none
  • Suggested action close as Rejected (or delete as spam)
  • Suggested ticket comment Not a Tcllib issue.
⬜6c615f0a812022ldap module doesn't handle $code "error" from server...NOT-A-BUG (local socket error, not a server code. Only the diagnostic is confusing)

Open ticket 6c615f0a81 · Bug · ldap · filed 2022-10-21

Full verdict

NOT-A-BUG (local socket error, not a server code. Only the diagnostic is confusing)

  • Module ldap 1.10.2
  • Tested decoded the hex in the report with binary format h* (the code dumps it nibble-swapped). It reads error reading "sockeb61d42490": software caused connection abort.
  • Cause ldap::ReceiveBytes returns the code error when read throws, here because the connection was aborted (ECONNABORTED). MessageReceiver sends that to the default branch, which labels it "Protocol error ... Error reading SEQUENCE" and hex-dumps the error text. The caller does get an error, which is correct. The wording is misleading and the socket is not closed.
  • Prototype none (cosmetic. A test would need a forced socket read error)
  • Suggested action close as Works as designed. Optionally add an explicit error branch that reports the read error text in plain words and closes the socket.
  • Suggested ticket comment Decoded, the dump says error reading "sock...": software caused connection abort: the TCP connection was aborted (server or network), and ldap reported it. The message could be clearer, but no server reply is mishandled.
⬜2aa0cebb882021json::json2dict treats null as a stringNOT-A-BUG (documented design). json.man now states that null becomes the string "null" and links this ticket (2b2bcd7ecf, 2026-01-27).

Open ticket 2aa0cebb88 · Bug · json · filed 2021-04-27

Full verdict

NOT-A-BUG (documented design). json.man now states that null becomes the string "null" and links this ticket (2b2bcd7ecf, 2026-01-27).

  • Module json 1.3.6
  • Tested 9.1: {"a":null,"b":"null"} gives a null b null
  • Cause parseValue returns the bare token
  • Prototype none (changing it to "" would break existing users and is equally lossy)
  • Suggested action close as Works as designed (now documented)
  • Suggested ticket comment This is documented behaviour now. null and "null" cannot be distinguished in the untyped dict result. Use huddle::json or typed-json if you need that.
⬜79c916b9042020couldn't open socket: address already in useNOT-A-BUG (the ::httpd::server constructor already calls my start. The wiki snippet then calls HTTPD start a second time, which binds the sam…

Open ticket 79c916b904 · Bug · httpd · filed 2020-06-04

Full verdict

NOT-A-BUG (the ::httpd::server constructor already calls my start. The wiki snippet then calls HTTPD start a second time, which binds the same port again. With port auto the second start just allocates another port, which is why that "works")

  • Module httpd 4.3.6
  • Tested httpd::server create HTTPD port 18000; HTTPD start gives "couldn't open socket: address already in use" on 9.1. Without the extra start the server runs (the man page's minimal example has no start call).
  • Cause httpd.tcl server constructor ends with my start. httpd.man documents start as "Open the socket listener" but does not say that the constructor already calls it.
  • Prototype none (docs or a wiki fix. Optionally start could close existing listeners first)
  • Suggested action close as Works as Designed. Optionally add one sentence to httpd.man saying the constructor starts listening.
  • Suggested ticket comment The server constructor already opens the listener, so the extra HTTPD start from the wiki snippet tries to bind the same port a second time. Drop that line, as in the man page's minimal example.
⬜7d12acd1052017uri::split does not parse file schemes correctly on WindowsNOT-A-BUG. Same issue as 6362dbd12b; it could also be closed as a DUPLICATE of 6362dbd12b. join and split are complementary: `uri::join scheme file…

Open ticket 7d12acd105 · Bug · uri · filed 2017-08-29

Full verdict

NOT-A-BUG. Same issue as 6362dbd12b; it could also be closed as a DUPLICATE of 6362dbd12b. join and split are complementary: uri::join scheme file path /C:/src gives file:///C:/src, which splits back to path /C:/src. The leading / belongs to the URI path.

  • Module uri 1.2.8
  • Tested 9.1, the round trip.
  • Cause n/a
  • Prototype none
  • Suggested action close as Works as designed (or Duplicate of 6362dbd12b)
  • Suggested ticket comment The leading "/" is part of the URI path (RFC 3986/8089), and join/split round-trip correctly. Converting to a native Windows filename is documented in uri.man.
⬜9f1eda18872016snit -option -default won't recognize global or namespaced variablespatchNOT-A-BUG (by design; DOCS)

Open ticket 9f1eda1887 · Bug · snit · filed 2016-09-02

Full verdict

NOT-A-BUG (by design; DOCS)

  • Module snit 2.3.4
  • Tested option -a -default $::a gives can't read "::a" on 9.1/8.6. snit::type C [list option -a -default $::a] works.
  • Cause type definitions are evaluated in Snit's separate compiler interpreter, so the caller's variables don't exist there. snit.man only mentions this interpreter for macros.
  • Prototype prototypes/9f1eda1887.patch (60 lines, docs + tests option-default-1.1/1.2). It documents the limitation and the workarounds (substitute with list/string map, or set the option in the constructor) next to snit::type. The tests pin the error and the workaround.
  • Suggested action apply doc patch, close as Won't Fix / Documented
  • Suggested ticket comment By design: the definition is evaluated in Snit's compiler interpreter, not the caller's. Build the body with list/string map or set the option in the constructor. A doc note is proposed.
⬜6362dbd12b2016uri::split does not support Windows drivesNOT-A-BUG. file:///T:/dir1/file1.txt splits to path /T:/dir1/file1.txt, which is the RFC 3986/8089 path-absolute form. Since uri 1.2.7, uri.man…

Open ticket 6362dbd12b · Bug · uri · filed 2016-08-19

Full verdict

NOT-A-BUG. file:///T:/dir1/file1.txt splits to path /T:/dir1/file1.txt, which is the RFC 3986/8089 path-absolute form. Since uri 1.2.7, uri.man documents that on Windows the path of a file URI is not a valid local filename, and its EXAMPLES section shows how to convert. T:/dir1/file1.txt is not a URI, so unknown scheme 'T' is correct.

  • Module uri 1.2.8
  • Tested 9.1, uri::split file:///T:/dir1/file1.txt and uri::split T:/dir1/file1.txt file.
  • Cause n/a (by design)
  • Prototype none
  • Suggested action close as Works as designed. Branch pbrooks-ticket-664392 additionally makes uri::geturl accept such paths on Windows.
  • Suggested ticket comment Per RFC 3986, the path of file:///T:/x is "/T:/x". uri.man (since 1.2.7) documents this and how to convert to a native name. "T:/..." is not a URI, hence the unknown-scheme error.
⬜29aa4821212015JSON module fails to parse dataNOT-A-BUG (the input is not a JSON object: no {}. Only the first entity is returned, which is documented.) A related real weakness was found: the…

Open ticket 29aa482121 · Bug · json · filed 2015-05-13

Full verdict

NOT-A-BUG (the input is not a JSON object: no {}. Only the first entity is returned, which is documented.) A related real weakness was found: the Tcl parser silently skips characters that are not tokens, e.g. {"a": @@ 1} gives a 1, and trailing garbage is ignored.

  • Module json 1.3.6
  • Tested 9.1, 8.6: the example returns message, {"a":1} garbage gives a 1, {"a": @@ 1} gives a 1
  • Cause json_tcl.tcl:json2dict_tcl tokenizes with regexp -all -inline $tokenRE, which drops unmatched text
  • Prototype none (strict validation would change behaviour for existing lenient users; needs a decision, e.g. a -strict option)
  • Suggested action close as Not a bug. Optionally open a new RFE for strict mode/validation.
  • Suggested ticket comment The input lacks the enclosing braces, so it is not a JSON object. json2dict returns the first entity ("success" at key position), as documented. Wrap it in {...}.
⬜52b764e4dd2015json2dict incorrectly adds braces to strings starting with $NOT-A-BUG ({$::x} is just the list string representation. lindex returns $::x exactly. The fact that an array gives a list is now documented.)

Open ticket 52b764e4dd · Bug · json · filed 2015-01-22

Full verdict

NOT-A-BUG ({$::x} is just the list string representation. lindex returns $::x exactly. The fact that an array gives a list is now documented.)

  • Module json 1.3.6
  • Tested 9.1, 8.6: json2dict {["length","$::x"]} gives length {$::x}
  • Cause Tcl list quoting
  • Prototype none
  • Suggested action close as Not a bug
  • Suggested ticket comment The braces are Tcl list quoting. The element value is $::x, as lindex shows. Use list commands, or join, rather than the string form.
⬜4565d1598d2015Type change from "request" in 1.3.1 to "connect" in 1.4NOT-A-BUG (intentional change from 2015; connect is the documented event and request was never documented). Re-adding request after 11 years …

Open ticket 4565d1598d · Bug · websocket · filed 2015-01-15

Full verdict

NOT-A-BUG (intentional change from 2015; connect is the documented event and request was never documented). Re-adding request after 11 years would surprise current users more than it helps.

  • Module websocket 1.6
  • Tested read websocket.tcl takeover and websocket.man.
  • Cause n/a
  • Prototype none
  • Suggested action close as Won't fix
  • Suggested ticket comment The event was renamed to "connect" in 1.4 (2015), and only "connect" is documented. Bringing back "request" now would mostly cause duplicate callbacks, so closing.
⬜cffddbb4262013Is this package being supported?NOT-A-BUG (support question, answered by aku in 2013)

Open ticket cffddbb426 · Bug · yaml · filed 2013-11-26

Full verdict

NOT-A-BUG (support question, answered by aku in 2013)

  • Module yaml 0.4.2 / huddle 0.5
  • Tested n/a
  • Cause n/a
  • Prototype none
  • Suggested action close (question answered)
  • Suggested ticket comment Question answered; yaml/huddle remain in Tcllib with fixes taken as patches with tests. Specific bugs are tracked in their own tickets.
⬜01afa9345d2013textutil::expander expand - cget within an expandNOT-A-BUG (expand pushes a new empty context, so cset values from the outer context are not visible. Resolution is already Invalid. A note was adde…

Open ticket 01afa9345d · Bug · textutil :: expander · filed 2013-10-18

Full verdict

NOT-A-BUG (expand pushes a new empty context, so cset values from the outer context are not visible. Resolution is already Invalid. A note was added to the documentation in e53cad73ec 2013-12-06 and is present in expander.man.)

  • Module textutil::expander 1.3.2
  • Tested checked expander.man for the note (line ~208) and expander.tcl:Op_expand (Op_cpush $name expand)
  • Cause intended behaviour
  • Prototype none
  • Suggested action close (Invalid). Only the status was left Open.
  • Suggested ticket comment As explained below, this is intended, and the documentation notes it. Closing.
⬜2861189fff2009decode and encode: inconsistent handling of line breaksNOT-A-BUG (by spec). application/x-www-form-urlencoded requires line breaks to be sent as CR LF (%0D%0A), browsers send textarea content that way…

Open ticket 2861189fff · Bug · ncgi · filed 2009-09-18

Full verdict

NOT-A-BUG (by spec). application/x-www-form-urlencoded requires line breaks to be sent as CR LF (%0D%0A), browsers send textarea content that way, and Tcl's own http::formatQuery does the same. decode faithfully returns what was sent. Mapping CRLF to LF in decode would silently alter data.

  • Module ncgi 1.4.6
  • Tested ncgi::decode [ncgi::encode "a\nb"] gives "a\r\nb" on 9.1 and 8.6
  • Cause by design (map(\n) = %0D%0A)
  • Prototype none
  • Suggested action close as Works as designed (optionally mention it in the man page)
  • Suggested ticket comment The form encoding mandates CR LF for line breaks, so encode sends %0D%0A like browsers and http::formatQuery do. The receiver should normalize with string map {\r\n \n} if it wants LF.
⬜2220156fff2008Several questions about Snit objectsNOT-A-BUG (support questions, not an RFE)

Open ticket 2220156fff · RFE · snit · filed 2008-11-04

Full verdict

NOT-A-BUG (support questions, not an RFE)

  • Module snit 2.3.4
  • Tested on 9.1, install called from a method after construction replaces the component, and delegated methods follow the new component.
  • Cause n/a. (1) There is no built-in clone; you write it with introspection or serialize methods. (2) install (or plain assignment to the component variable) works at any time, not only in the constructor. (3) delegate is a definition-time statement only.
  • Prototype none (questions)
  • Suggested action close as Works For Me / Answered
  • Suggested ticket comment Answers: no built-in cloning; components can be re-installed at any time (e.g. from a method) and delegation follows the new component; delegate is only available in the type definition. Closing.
⬜1798420fff2007Documenting C functionsNOT-A-BUG (the [fun] and [type] markup exists and the reporter got good results with it, see the 2007-09-23 comment. Creating man-page aliases/…

Open ticket 1798420fff · Bug · doctools · filed 2007-09-19

Full verdict

NOT-A-BUG (the [fun] and [type] markup exists and the reporter got good results with it, see the 2007-09-23 comment. Creating man-page aliases/symlinks for installation is outside doctools' scope, as AK said.)

  • Module doctools 1.6.1
  • Tested code reading (checker.tcl fun, type)
  • Cause n/a
  • Prototype none
  • Suggested action close as Works For Me
  • Suggested ticket comment C functions can be documented with [fun], [type] and [arg], as the reporter found. Creating per-function man page aliases is a job for the build system, not doctools.
⬜1733442fff2007elements of htmlparse param list cannot be accessedNOT-A-BUG (param is the raw attribute string, not a Tcl list)

Open ticket 1733442fff · Bug · htmlparse · filed 2007-06-08

Full verdict

NOT-A-BUG (param is the raw attribute string, not a Tcl list)

  • Module htmlparse 1.2.3
  • Tested by code reading. parse passes the text between the tag name and > unchanged. A string with quoted values containing quotes or spaces is not a valid list.
  • Cause htmlparse.man line 197 calls it the "un-interpreted list of parameters", which misleads. The intro and the 2tree section say the attributes are passed unparsed.
  • Prototype none
  • Suggested action close as Works as designed (maybe fix the "list" wording in the docs). Attribute parsing is RFE 3000165.
  • Suggested ticket comment The param argument is the raw attribute text, not a Tcl list, so list commands cannot be used on it. Attribute parsing is requested in RFE 3000165.
⬜1584235fff2006Nlist against win. IIS behaves bizarNOT-A-BUG (NList passes server output through unchanged; the reporter agreed in 2006 that it is IIS behaviour)

Open ticket 1584235fff · Bug · ftp · filed 2006-10-25

Full verdict

NOT-A-BUG (NList passes server output through unchanged; the reporter agreed in 2006 that it is IIS behaviour)

  • Module ftp 2.4.14
  • Tested none (needs IIS); code read
  • Cause server-specific NLST name format
  • Prototype none (the docs note is part of prototypes/1307714fff.patch)
  • Suggested action close as Works as designed
  • Suggested ticket comment NList returns names as the server sends them. The IIS backslashes and missing prefixes come from the server; the manual now mentions that prefixes are server-dependent.
⬜1554121fff2006Camel case optionsNOT-A-BUG (documented restriction)

Open ticket 1554121fff · Bug · snit · filed 2006-09-07

Full verdict

NOT-A-BUG (documented restriction)

  • Module snit 2.3.4
  • Tested option -thisOrThat is rejected ("badly named option"). -thisÄtsch is accepted, because the check is [A-Z ] only.
  • Cause main2.tcl: Comp.OptionNameIsValid. By design: resource/class names are derived from the option name, and the explicit form option {-name resourceName ClassName} gives camel-case resource names.
  • Prototype none
  • Suggested action close as Works as designed (optionally mention the non-ASCII loophole)
  • Suggested ticket comment Lower-case option names are a documented rule. Use option {-thisorthat thisOrThat ThisOrThat} for a camel-case resource name. Closing.
⬜1473699fff2006-? and -help brokenNOT-A-BUG (by design and documented)

Open ticket 1473699fff · Bug · cmdline · filed 2006-04-20

Full verdict

NOT-A-BUG (by design and documented)

  • Module cmdline 1.5.3
  • Tested -?/-help throw the usage message with errorcode CMDLINE USAGE on 9.1 and 8.6. ?/help without a dash are plain arguments.
  • Cause documented since 1.3.2 (Bug 3041989): -? and -help "abort option processing by throwing an error". Since 1.5 the man page has a try ... trap {CMDLINE USAGE} example to print it and exit.
  • Prototype none
  • Suggested action close as Works as Designed
  • Suggested ticket comment The error is how -?/-help deliver the usage text. Trap {CMDLINE USAGE} as in the man page example. See also 472259ffff.
⬜1308006fff2005ftp::List problem on WindowsNOT-A-BUG (IIS answers LIST of a non-matching name with 550; Solaris ftpd answers 226 with an empty list. The package logs the 550 as an error and …

Open ticket 1308006fff · Bug · ftp · filed 2005-09-29

Full verdict

NOT-A-BUG (IIS answers LIST of a non-matching name with 550; Solaris ftpd answers 226 with an empty list. The package logs the 550 as an error and returns {} in both cases)

  • Module ftp 2.4.14
  • Tested code read (List returns {} on failure). ftpd behaves like Solaris.
  • Cause server reply code. Same mechanism as 898067.
  • Prototype none
  • Suggested action close as Works as designed
  • Suggested ticket comment IIS reports a 550 failure for a pattern with no matches. ftp::List still returns an empty list; the logged error just reflects the server's reply.
⬜1273537fff2005uuencode pad character confusion/messNOT-A-BUG (the testsuite confusion was fixed in 2005, ChangeLog 2005-08-26). Pure Tcl and critcl pad with backtick, like GNU/perl. Only the optiona…

Open ticket 1273537fff · Bug · base64 · filed 2005-08-25

Full verdict

NOT-A-BUG (the testsuite confusion was fixed in 2005, ChangeLog 2005-08-26). Pure Tcl and critcl pad with backtick, like GNU/perl. Only the optional Trf accelerator uses ~, and Trf is not available for current Tcl here. uudecode accepts ` `, ~, =` and space padding equally, because the length byte decides.

  • Module uuencode 1.1.6
  • Tested uudecode with each padding character on 9.1; Trf not installable on 9.1/8.6
  • Cause n/a
  • Prototype none
  • Suggested action close as Works for me / Wont fix
  • Suggested ticket comment The encoders pad with backtick (same as GNU uuencode), and the decoder accepts any padding character, because the length byte governs. The test confusion was fixed in 2005. Closing.
⬜1008797fff2004bad multiple calls to logging command in log::logNOT-A-BUG (deliberate since 2003-11-25, "better handling of multiple lines". log::logsubst does the same)

Open ticket 1008797fff · Bug · log · filed 2004-08-13

Full verdict

NOT-A-BUG (deliberate since 2003-11-25, "better handling of multiple lines". log::logsubst does the same)

  • Module log 1.5
  • Tested code review of log.tcl ::log::log and ::log::logsubst. Both call the command once per line.
  • Cause foreach line [split $text \n] {...} in log::log. Changing it now would alter the output of every existing user.
  • Prototype none
  • Suggested action close as Won't fix. Optionally add a sentence to log.man saying the command runs once per line. Users who want one call per event can call the level command themselves or use logger.
  • Suggested ticket comment The one-call-per-line behaviour is deliberate and has been in place for 20 years. Changing it would break existing log formats. Closing; logger, or a custom command fed by the caller, gives one call per event.
⬜898067ffff2004ftp::NList error when directory emptyNOT-A-BUG (the server answers NLST on an empty directory with 450/550 "No files found", as wu-ftpd/ProFTPD do. The package then logs an error and s…

Open ticket 898067ffff · Bug · ftp · filed 2004-02-16

Full verdict

NOT-A-BUG (the server answers NLST on an empty directory with 450/550 "No files found", as wu-ftpd/ProFTPD do. The package then logs an error and still returns {}, the same value as for an empty listing)

  • Module ftp 2.4.14
  • Tested ftpd: NList/List on an empty directory → {} and no error. Code: NList/List return {} on failure. The only difference is the logged error message.
  • Cause server reply code, not the client
  • Prototype none
  • Suggested action close as Works as designed
  • Suggested ticket comment Some servers answer NLST on an empty directory with a 450/550 error. NList still returns an empty list; the logged message only reflects the server's failure code.