- Shipped
- September 28, 2026 at 8:32 PM UTC
- Author
- Kamo
- Commit
- 7986439
SP98-F-5. **************** returned the CalendarEvent entity, whose attendees point back at their event, so writing it recursed until the stack overflowed; it now answers with the same summary as /send and /{eventId}, and with no body when the invitation made no event. It also handed the parser the member id as the user id (another table's number), so it found no event and no calendar; it now passes the session's user id and refuses a session without one. The parser takes the member's default calendar only when it is the member's own: a preference holds whatever id it was sent, so a colleague's calendar or the organisation's (which needs the publishing right) was a way to write into it.