6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
3/2/26
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#14153] Weekly invitation adds one hour to the start time
*
Your Email Address
*
Spam protection
Enter the letters below:
. . ..___.. . |_/ | _/ | | | \\__|./__.|___\__|
Comment
> I've narrowed it down to either a broken VTimezone definition or an > issue in the way we sort the components in > Horde_Icalendar::_parseTZID(). There is some strange interaction > going on with the transition 'end' values vs the 'time' values in > this zone when they are being sorted such that the incorrect zone is > detected as the correct one. > > If C is the current component then: > > The date we are checking (D) is larger than the C's ['time'] value > and less than (C+1)'s ['time'] value - but because of (C+1)'s > ['end'] value, (C+2) and above's ['time] value is less than D until > at some point we get the correct component (C+x) where the ['time'] > value is still less than the date we are checking, but (C+x+1)'s > ['time'] value is larger that the date we are checking - and both are > still less than the (C+2) ['time'] value. > > tldr; the sorted components are not correctly sorted by 'time'. It > could very well be the timezone definition is broken, but I'm not > 100% sure how to tell yet.
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers