@staticshock reports that a file with a single latin-1 character is degrading pretty badly in Diffusion (showing a blank file instead of describing the error or recovering from it).
Broadly, if we hit a file which has an encoding which we don't expect (i.e., not the repository's configured encoding, as per T452), we should try to recover more gracefully. Anything (explicit error, attempted conversion with note) would be better than what we do now.
See also T2999, T452.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | btrahan | T6350 Diffusion spamming the feed/commits going weird | ||
| Resolved | None | T1191 Comments are truncated at first non-base-plane character | ||
| Resolved | epriestley | T5644 Add controls to prevent `pygmentize` from saturating system resources | ||
| Resolved | epriestley | T5179 Unearth Differential rendering technical debt | ||
| Open | None | T5229 Fixing up invalid encoding confuses archanists utf8-check | ||
| Resolved | • clark.woo.12 | T7116 differential final diff shows "This file uses an unknown character encoding" | ||
| Resolved | epriestley | T4045 Store diffs as binary, not UTF-8 | ||
| Resolved | epriestley | T3788 Improve encoding management in Diffusion |