Small fixes

A selection of 80 fixes from 174 pull requests.

Effect · 2–4 September 2026 · Kit Langton

77.A colliding SQL alias

A joined reply_id overwrote an acknowledgement’s own reply ID. Use the distinct reply_reply_id alias expected by the shared decoder.

1. BigInt precision2. The wrong database3. Lost leftovers4. Binary data, decoded twice5. Literal configuration values6. Partial writes7. Cleanup after a throw8. Deleting a prefix9. Pipeline input10. A counter shared across registries11. Request zero12. A zero cache lifetime13. An exhausted comparison14. Iterables are not arrays15. An error wrapped as an error16. Day 5 became day 1517. Negative flag values18. A suppressed React update19. Writing to the wrapper20. A stale tool schema21. A bodyless response22. A raw streaming body23. A missing URL prefix24. Unparsed form data25. A missing content length26. Overwriting Vary27. The string “null”28. An uncaught SQL error29. The wrong column names30. An index is not a primary key31. Characters are not bytes32. Mixed line endings33. A missing first character34. A percent sign in a reference35. Too many arguments36. The excluded endpoint37. Cancelling the existing task38. An evaluator returning itself39. Writing zero bytes40. Attribute order41. Child tables in separate entries42. Folded YAML paragraphs43. Optional alternative flags44. Range on a HEAD request45. Errors during finalization46. An unsupported form reader47. A discarded domain option48. Binding byte arrays49. A replaced reason phrase50. An ignored SSL override51. Text from a binary response52. A stale Vue snapshot53. Negative counter deltas54. A field that would not delete55. An array hole instead of removal56. An array-valued element57. Waiting past a line ending58. Three rows became four59. An off-by-one allocation60. Half a Unicode character61. Media-type parameters62. A default that never applied63. One slash too many64. Stale response metadata65. Two encoders, two statuses66. Missing response hooks in tests67. An uncatchable storage error68. Cleaning up the same key twice69. Encoding the wrong result branch70. A missing semicolon71. Overlapping metric intervals72. Normalizing a value twice73. An undefined write flag74. The wrong address kind75. A reply without its envelope76. A URI matched as a path77. A colliding SQL alias78. A zero durability threshold79. A cause that looked absent80. A port that never started