claude
37feee1eb3
Four real defects, two of them silent. FactSpan built both instants as midnight.Add(hours). A day is 23 or 25 hours wide on the two DST changeovers, so every span on those days was an hour off and the busy gate read a 14:00 meeting as 13:00 or 15:00. Both readings are time.Date now, and the midnight crossing is AddDate rather than adding 24 hours. parseVEVENT split the block on newlines and trimmed each one, which destroys the leading space that marks a folded continuation. Servers fold at 75 octets and a Russian summary is two bytes a letter, so the tail of an ordinary weekly standup was read as an unknown property and dropped. The event was filed under a truncated name, and through safeKey a truncated fact key. Unfolding runs before the split now. RenderICal escaped TEXT and the parse never unescaped it, so a server-written summary reached the day plan with its backslashes. The MIME walk recursed with no depth cap and the nesting comes off the wire. A boundary line is a few bytes, so one message inside MaxMessageBytes can declare tens of thousands of levels. MaxMIMEDepth is 12 and the headers still come through. Two whole-body copies went with it. Read-only IMAP confirmed rather than assumed: EXAMINE not SELECT, BODY.PEEK not BODY, and no STORE, APPEND, EXPUNGE, COPY or MOVE anywhere in the package or the daemon. No credential is logged, and the dial seam is unexported so no caller can point the reader at a plaintext transport. internal/event needed nothing. (V-581)