View Ticket
Not logged in
2024-08-20
20:25
Merge [5fb3c75e4a4b063d]: Expand zipfs tests. Fix [9a80630571], [6ed3447a7e], [01d8f30342] and manpa... check-in: f6176984d2 user: pooryorick tags: unchained, INCOMPATIBLE_LICENSE
2023-09-15
15:46 Closed ticket [01d8f30342]: zipfs canonical two argument form produces garbage in result plus 5 other changes artifact: d97337c458 user: apnadkarni
15:46 Ticket [01d8f30342]: 3 changes artifact: 25b76da22c user: apnadkarni
08:38
Merge 8.7 - Expand zipfs tests. Fix [9a80630571], [6ed3447a7e], [01d8f30342] and manpages. check-in: 5fb3c75e4a user: apnadkarni tags: trunk, main
08:00
Expand zipfs tests. Fix [9a80630571], [6ed3447a7e], [01d8f30342] and manpages. check-in: 2fd1277ae3 user: apnadkarni tags: core-8-branch
2023-09-14
14:52
More tests and fix one more case triggering bug [01d8f30342] check-in: 7b81ff8bc4 user: apnadkarni tags: apn-zipfs-tests
2023-09-13
16:48 Ticket [01d8f30342] zipfs canonical two argument form produces garbage in result status still Open with 3 other changes artifact: bce0d997f1 user: apnadkarni
16:45
Bug [01d8f30342]. zipfs canonical produces garbage. check-in: 626ffd4fea user: apnadkarni tags: apn-zipfs-tests
12:02 New ticket [01d8f30342] zipfs canonical two argument form produces garbage in result. artifact: 4c6235b3b2 user: apnadkarni

Ticket UUID: 01d8f30342295486658798851bacf2dd26a3422b
Title: zipfs canonical two argument form produces garbage in result
Type: Bug Version: 8.7
Submitter: apnadkarni Created on: 2023-09-13 12:02:45
Subsystem: - New Builtin Commands Assigned To: nobody
Priority: 5 Medium Severity: Important
Status: Closed Last Modified: 2023-09-15 15:46:44
Resolution: Fixed Closed By: apnadkarni
    Closed on: 2023-09-15 15:46:44
Description:
Leaving aside the question of `zipfs canonical` being implemented and documented in the manpages without being TIP'ed, it produces garbage in its two argument form.

```
% zipfs canonical mtpt
//zipfs:/mtpt
% zipfs canonical mtpt file
//zipfs:/ú½¼ûfile
% codepoints [zipfs canonical mtpt file]
U+00002F U+00002F U+00007A U+000069 U+000070 U+000066 U+000073 U+00003A U+00002F U+0000FA U+0000BD U+0000BC U+0000FB U+000066 U+000069 U+00006C U+000065
```
User Comments: apnadkarni added on 2023-09-15 15:46:33:
Fixed in [2fd1277ae3].

apnadkarni added on 2023-09-13 16:48:26:
Fixed this particular issue of pointer miscalculation. Still lots of issues with undefined semantics of the command. Are multiple / to be collapsed? Are drive letters intentionally dropped? Is it intentional that only \\ is considered UNC but not // ?

Leaving open as a reminder to revisit semantics.