209843 - An event only listed on 10/26 is also being placed on the 27th.

Status: RESOLVED WORKSFORME

(Calendar :: General, defect)

Description

[u59231]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612

I have an event listed on 10/26/1980.  It is supposed to only be listed that day
but is also being displayed on the 27th.  The ICS file lists the correct date
information.  However, when you bring up the event specifics it shows an ending
date of 10/27/1980.  I will be attaching my ICS file and an image of what I'm
seeing.

Reproducible: Didn't try

Steps to Reproduce:
1.
2.
3.



Expected Results:  
It should show the event only on the dates specified.

I think this may be related to another error I'm seeing.  The DST-Ends event in
the ICS file is showing a 10/27 start and a 10/28 end.  However, the calendar
parses it as starting on the 10/26 and ending on 10/27...

Comment 1

[u59231]

Attachment: The ICS file that I'm using to produce this error...

Comment 2

[u59231]

Attachment: This is what I'm seeing...

Comment 3

[Kathleen Jones]

I have the same thing happen, if I add an event on October 26th and have it
repeat every 1 year. If I do the same thing on another date, it displays as
expected. The event date ending on the 27th makes sense seeing as the event is
marked to last all day. All day being from midnight on the 26th to midnight on
the 27th (24 hours). Also, Daylight Savings time is shown both the 26th and
27th, instead of just on the 27th. I don't know if it's a different bug or if
it's related to the problem here.

Comment 4

[u59231]

Since a new RC came out today, I decided to reinstall the browser and see if the
error still exists.  It does, I suspect that this is related to an error in the
"Daylight Saving Times - Ends" event which is also shown on 2 days but it is the
wrong two days.  Both can be seen in the files that I have submitted along with
this bug.

Version of Moz & Calendar:

Mozilla Calendar 2003061213-cal
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4; MultiZilla v1.4.0.4A)
Gecko/20030624

Comment 5

[Mike Potter]

New contact from [e-mail] to [e-mail]
Filter on string OttawaMBA to get rid of these messages. 
Sorry for the spam.

Comment 6

[Calum Mackay]

It looks to me as though bug 209843 and bug 212531 are describing the same issue.

Submitters: would you please check and confirm? I can then close one as a dup.

Comment 7

[Luis Sousa]

*** Bug 224006 has been marked as a duplicate of this bug. ***

Comment 8

[Calum Mackay]

*** Bug 212531 has been marked as a duplicate of this bug. ***

Comment 9

[Calum Mackay]

I'm seeing this, on a current Linux/x86 build.

The simplest part of the problem seems to be that an all-day event runs from
0000 day x to 0000 day (x+1). Perhaps it should run to 2359 day x?

Comment 10

[Luis Sousa]

Hi folks!
I've added bug Bug 224006, which turned out to be a duplicate of this one.
I would like to add that this bug only reveals itself if recursion is added to
the event, no matter what type of recursion you set (weekly, monthly or annually).

(answering to comment #6 From Calum Mackay)
For that reason, and because of the behavior of bug 212531 which is opposite to
this one, I'm lead to think that these two bugs (209843 and 212531) are not the
same. This only happens if recursion is set and spawns one day shorter. 212531
spans even if recursion is not set.
I don't think bug 212531 is influenced by the year the event is set. Bug 209843 is.

So, I confirm bug 209843 to happen on 26/10 of years 1980,1986,1997,2003 (No
other year in between, I've tested them all) and on the 26/10 for year 1976 (no
other years tested.

This behavior was tested on Netscape 7.1:

Mozilla Calendar 2003092817-cal
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Netscape/7.1 (ax)

Netscape 7.1
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Netscape/7.1 (ax)

Comment 11

[Luis Sousa]

Sorry, last comment should have been:

...
So, I confirm bug 209843 to happen on 26/10 of years 1980,1986,1997,2003 (No
other year in between, I've tested them all) and on the 31/10 for year 1976 (no
other years tested.
...

Comment 12

[Luis Sousa]

Well ... mean while I've found out this:

If I set the event for day 31/10 on years 1971, 1976, 1982, 1993, 1999, 2010,
2021, 2032, it reveals the bug. past this date I didn't find any year that would
also reveal the bug. There is a pattern in the years.
the gap is 5, 6, 11, 6, 11, 11, 11 years between the years the bug appears.

for day 26/10 it happens on 1975, 1980, 1986, 1997, 2003, 2014, 2025, 2036.
Again the gap is 5, 6, 11, 6, 11, 11, 11 years. ODD ?!?!?

More notes: is stops at this dates because past year 2038 all events stop
recurring. Is this something like year 2038 bug for Unix on calendar? Is
Calendar also using a 32 bit length seconds timer for this?
I'm filling a bug for this since I didn't find this on any bug report.

After year 2000 the pattern is always 11 year between the years the bug reveals.

Hope this helps.

Comment 13

[Tom Blake]

Using the latest version for Mac OS X, creating a multi-day "all-day" event, the
event appears to not include the last day, but then this (kind-of) makes sense,
as the dialog box shows the event extending until 12:00am of the "last day"
(which is midnight of the day before, and, so, in a sense, does not include any
of the last day!)

So, perhaps an "all day" event should be defined as extending through 11:59pm of
the last day.  (Could it be that simple!?)

Comment 14

[rosi_1]

i've got a similar problem. If you create a whole day date on the 30th of
october 2005 then it is dublicated to the 31st of october 2005 but it is still
one instance. if you delete the clone on the 31st then the original on the 30th
disappears as well.

this is reproduceable for the year 2005 for the german time-zone but not for the
year 2006. the day-light saving end 2006 on the 29th of october but if you
create a all-day date ether on the 29th or the 30th nothing is dublicated.

my original report is shown as 292626

Comment 15

[Joey Minta]

*** Bug 292626 has been marked as a duplicate of this bug. ***

Comment 16

[Robin Edrenius]

WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050807
Mozilla Sunbird/0.2+

Comment 17

[Joey Minta]

(In reply to comment #16)
> WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050807
> Mozilla Sunbird/0.2+

WFM me also, but this bug scares me a bit.  Anyone using a nightly build of
Sunbird should definitely feel encouraged to re-open if this still exists.

Comment 18

[Ian Cairns]

Using the current Sunbird 0.2 - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.8a5) Gecko/20050203 Mozilla Sunbird/0.2 - I get a similar problem for Oct
30 2005 provided that it repeats annually. An echo entry appears for Oct 31 for
2005, 2006 (haven't checked further). Deleting the entry takes out all entries.
If it does not repeat annually, then it only appears for Oct 30. I have several
other repeating annual anniversaries that are fine.

Comment 19

[Paul]

Can confirm that Sunbird 0.2 repeats "birthday" entries for the 30-10-2005 on the 31st. No other day in Oct is affected.

The 26-10 problem has gone from 0.2

Comment 20

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!