Bugzilla

(In reply to Geoff Lankow (:darktrojan) from comment #15)
> I'll approve this on the conditions that you include the test from the other patch, and that the fix is verified on 102 before it ships. Thomas can do that

(In reply to Sean Burke [:leftmostcat] from comment #3)
> I haven't been able to reproduce this issue, but potentially have a fix for it.

Me neither.

- I've converted one of the problem events from comment 2 into a testcase (which required some manual tweaking of newlines; I believe I got that right) - see attachment.
- Steps to reproduce are not clear to me, and probably not reduced. Since this is about the timezone problem, I don't think NextCloud is required for reproducing this.
- I've successfully imported the test event to a Google Calendar via their web interface, but it won't sync with Thunderbird's respective Google Calendar at all (both on 102.3.3 w/o this patch and on 102.4.0 candidate with this patch, Win10) - but then, we also have this issue about Google Calendar sync quota?
- I'm also getting errors even when trying to just import the testcase into a local calendar (both on 102.3.3 w/o this patch and on 102.4.0 candidate with this patch, Win10), but they don't look related to the timezone problem. Another TB-generated ics imported alright.

(In reply to Geoff Lankow (:darktrojan) from comment #15)
> I'll approve this on the conditions that you include the test from the other patch, and that the fix is verified on 102 before it ships. Thomas can do that

(In reply to Sean Burke [:leftmostcat] from comment #3)
> I haven't been able to reproduce this issue, but potentially have a fix for it.

Me neither.

- I've converted one of the problem events from comment 2 into a testcase (which required some manual tweaking of newlines; I believe I got that right) - see attachment.
- Steps to reproduce are not clear to me, and probably not reduced. Since this is about the timezone problem, I don't think NextCloud is required for reproducing this.
- I've successfully imported the test event to a Google Calendar via their web interface, but it won't sync with Thunderbird's respective Google Calendar at all (both on 102.3.3 w/o this patch and on 102.4.0 candidate with this patch, Win10) - but then, we also have this issue about Google Calendar sync quota?
- I'm also getting errors even when trying to just import the testcase into a local calendar (both on 102.3.3 w/o this patch and on 102.4.0 candidate with this patch, Win10), but they don't look related to the timezone problem. Another TB-generated ics imported alright.
  - Calendar: id is null when parsing
  - mail.import: Error: noItemsFound

(In reply to Geoff Lankow (:darktrojan) from comment #15)
> I'll approve this on the conditions that you include the test from the other patch, and that the fix is verified on 102 before it ships. Thomas can do that

(In reply to Sean Burke [:leftmostcat] from comment #3)
> I haven't been able to reproduce this issue, but potentially have a fix for it.

Me neither.

- I've converted one of the problem events from comment 2 into a testcase (which required some manual tweaking of newlines; I believe I got that right) - see attachment.
- Steps to reproduce are not clear to me, and probably not reduced. Since this is about the timezone problem, I don't think NextCloud is required for reproducing this.
- I've successfully imported the test event to a Google Calendar via their web interface, but it won't sync with Thunderbird's respective Google Calendar at all (both on 102.3.3 w/o this patch and on 102.4.0 candidate with this patch, Win10) - but then, we also have this issue about Google Calendar sync quota?
- I'm also getting errors even when trying to just import the testcase into a local calendar (both on 102.3.3 w/o this patch and on 102.4.0 candidate with this patch, Win10), but they don't look related to the timezone problem (see error log in comment 21, attachment 9299128 [details]). Another TB-generated ics imported alright.
  - Calendar: id is null when parsing
  - mail.import: Error: noItemsFound