User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36

Steps to reproduce:

Thunderbird / Lightning 68.1.2 (32bit) / ProviderForGoogleCalendar
Windows10 64bit 1903

Issue with TODAY-PANE (calendar side-bar).
The following 2 problems correlate to each other.

Problem 1:
When the PC sleeps and is woken up AFTER 00:00 so when it is woken up on the next day, then the today-pane will NOT automatically move to the next day. This can become an issue and work should be done on this, at least allowing the user to set this behaviour e.g. "check for today-date every x minutes".

Problem 2:
Future-day-appointments (e.g. for the next 7 days) will disappear completely, IF the today-pane is set to a past date or to a future date, e.g. if the today-pane is set to yesterday instead of today.

So this does relate to Problem 1: if the PC wakes up after midnight, then all future appointments will disappear and no longer show in the today-pane. Clicking the today-circle will bring them back.

Actual results:

see above. In the today-pane, future appointments will disappear if the PC wakes up after midnight, and the today-date will not be automatically updated.

Expected results:

The today-date should automatically update to "real today" e.g. if the PC wakes up after midnight.
The future appointments should ALWAYS show up correctly, no matter if the today-circle is clicked, or if +/- one or two days in past/future are clicked. Currently, future appointments only show if today-date is set to real today.

as shown, the future-appointments in the today-pane are only displayed, of the today-date of the today-pane matches the real (system) date.
If the today-pane is clickt one day left or one day right (yesterday / tomorrow) then the future appointments will no longer be shown.
Therefore also, if the PC wakes out of standby /sleep mode after midnight, the future appointments will not show, as the today-pane does not automatically update its today-date.

Calendar bugs go into the Calendar product and appropriate component.

Better chance of calendar developers seeing it there.

(Lightning 7.0 was renamed to Lightning 68 shortly before release. Unfortunately it is not yet possible to select this version in the drop-down menu, causing lots of confusion)

As far as I know the behavior described by you as problem 2 is the intended behavior and therefore works as specified. The agenda view has two operation modes: A) when set to today it will show events for today, tomorrow and the next X days. or B) when set to a different date it will show the events for the selected date. This allows to quickly view events for any past and future date without the need to switch to calendar tab.

User is using version 68.4.2
There are reports that the 'Today Pane' is not auto updating the date when it goes past midnight, so it is not showing the 'Today' date.
Thunderbird is left running 24/7
https://support.mozilla.org/en-US/questions/1278106
https://support.mozilla.org/en-US/questions/1278229

The point being if you select to see only 'Today' then today should be the correct date. When it gets to midnight, the date should update in the same way the computer date updates. This is the usual behaviour and works on my computer. At midnight the date updates, but it does not seem to be the case for others, forced to restart Thunderbird just to see the correct date automatically. There are no other addons conflicting.

Bug 1598858, which I reported, seems like it's a dupe of this one.

The reports on this reported problem keep appearing in Support forum.
https://support.mozilla.org/en-US/questions/1279219

I've been trying many things and the only one that's managed to reproduce this so far is to change Lightning's timezone to be different from the system timezone. Is that the case for anybody reporting this?

(Also, if that is the problem, I don't know why it worked before and doesn't now.)

I've asked the various users to check out the 'timezone' as to whether computer and Lightning are using different or same timezones. I'll report back when they repond.

(In reply to Anje from comment #10)

I've asked the various users to check out the 'timezone' as to whether computer and Lightning are using different or same timezones. I'll report back when they repond.

I'm on 71.0b and my timezone is ok. I feel like this was ok in 70.0b and started happening in 71.0b.

I have the same timezone in TB and system and I am affected by this bug. Both on Linux and Windows, with release version of TB and Lightning (68.4). This has been happening for several months.

Today pane is set to show the following 5 days.

Feedback: Timezone is not the issue.
New report of occurance after updating to 68.6.0:
https://support.mozilla.org/en-US/questions/1283579

Hi, 1. Make sure the calendar events are shown in main window (by default on the right side of main menu) 2. Put the computer to sleep mode. 3. Wake up from sleep. Calendar in main window shows no events. 4. Navigate to full calendar window to notice the events are still there. 5. Restart Thunderbird to make it show incoming events in main window again. This started to happening after latest update 68.6.0. Windows 10 x64 Pro build 1909

It does not seem to happen at midnight if we have scheduled any incoming meeting in next 5 days. The meeting appear on the right side of main window and others do not disappear. I have just checked it twice as I have events on Sunday and Monday.

I also have this problem with Thunderbird 68.4.1 (64-Bit) on Linux Mint 19.3. PC runs 24/7 but goes to sleep mode after 10 minutes. "Today" is never updated when I come back the next day.

Same problem here. 68.7.0 (32-Bit) / Lightning / ProviderForGoogleCalendar

PC is on 24 hours. Today not updated at midnight. Tomorrow etc. lost. Restart handles it.

As a first test, I disabled all other addons. Error still happens.

I went back to 52.9.1 (32-Bit) - works fine there.

I will now upgrade step by step and report every day.

60.9.1 (32-Bit) works
68.0 (32-Bit) does not work

So the error was introduced between these two.

Dupe of bug 402842?

No. 402842 was 13 years ago was had been fixed.

(In reply to stephan from comment #24)

No. 402842 was 13 years ago was had been fixed.

Apologies, looks like the Status is "New".

Somebody forget to mark it resolved?

fix?

I don't know how much help this is but today when I woke my PC from sleep I went to the error console and saw:

uncaught exception: 2147746065 autosync.jsm: 244:30
Lightning: [calGoogleCalendar] 2020-05-28T14:30:00-05:00 does not match timezone offset for America/Chicago gdataUtils.jsm:251
Lightning: [calGoogleCalendar] 2020-05-28T15:30:00-05:00 does not match timezone offset for America/Chicago gdataUtils.jsm:251

Assert failed: TypeError: realDay is null calUtils.jsm:141
ASSERT resource://calendar/modules/calUtils.jsm:141
refreshUIBits chrome://lightning/content/messenger-overlay-sidebar.js:436
notify chrome://calendar/content/calendar-views-utils.js:336

My time zone is set correctly for Chicago in Win 10 @ UTC -6:00 Central Time (US & Canada).

Noted in release notes: fixed Calendar: Today Pane updated prior to loading all data

Can I presume this particular fix has nothing to do with the this bug?

Just as heads up fixed bug 1560547 has not fixed this particular bug. Not that it was expected, but I thought I'd post info based on Support forum report that 68.9.0 still has this bug.

You can presume that nothing has fixed this particular bug until this bug is marked fixed.

I normally use Mini-Month in the Today Pane with the Mail tab.

Set View > Today Pane > Show Mini-Day in the Mail tab using Thunderbird 68.9.0 on Windows and let it hibernate since Friday 06/19 until today.
Left Thunderbird up and maximized.
Resumed the computer, logged in and the Today Pane showed 06/22.
No data was lost.

Did the same steps overnight with Thunderbird 68.8.0 from Ubuntu, 78.0b2 and Daily 79.0a1 on Ubuntu Linux 18.04.4.
After resuming from sleep and logging in the Today Pane still showed 06/21 and updated to 06/22 after a few seconds in Thunderbird 68.8.0.
Both 78.0b2 and 79.0a1 were updated to 06/22. Not sure if there was a delay there.
No data was lost.

(In reply to WaltS48 [:walts48] from comment #31)

I normally use Mini-Month in the Today Pane with the Mail tab.

Set View > Today Pane > Show Mini-Day in the Mail tab using Thunderbird 68.9.0 on Windows and let it hibernate since Friday 06/19 until today.
Left Thunderbird up and maximized.
Resumed the computer, logged in and the Today Pane showed 06/22.
No data was lost.

Did the same steps overnight with Thunderbird 68.8.0 from Ubuntu, 78.0b2 and Daily 79.0a1 on Ubuntu Linux 18.04.4.
After resuming from sleep and logging in the Today Pane still showed 06/21 and updated to 06/22 after a few seconds in Thunderbird 68.8.0.
Both 78.0b2 and 79.0a1 were updated to 06/22. Not sure if there was a delay there.
No data was lost.

I too am on mini-month view yet when I wake from sleep the next day, it's still stuck on the previous day and will only advance date when I shut down TB and restart it. Don't think I am doing anything different than you.

(In reply to Arthur K. from comment #32)

(In reply to WaltS48 [:walts48] from comment #31)

I normally use Mini-Month in the Today Pane with the Mail tab.

Set View > Today Pane > Show Mini-Day in the Mail tab using Thunderbird 68.9.0 on Windows and let it hibernate since Friday 06/19 until today.
Left Thunderbird up and maximized.
Resumed the computer, logged in and the Today Pane showed 06/22.
No data was lost.

Did the same steps overnight with Thunderbird 68.8.0 from Ubuntu, 78.0b2 and Daily 79.0a1 on Ubuntu Linux 18.04.4.
After resuming from sleep and logging in the Today Pane still showed 06/21 and updated to 06/22 after a few seconds in Thunderbird 68.8.0.
Both 78.0b2 and 79.0a1 were updated to 06/22. Not sure if there was a delay there.
No data was lost.

I too am on mini-month view yet when I wake from sleep the next day, it's still stuck on the previous day and will only advance date when I shut down TB and restart it. Don't think I am doing anything different than you.

I thought I specifically stated that I followed the steps to reproduce and changed the View to show Mini-Day as in the screenshots and report.

I'll test one more time with Mini-Month set as the view, but I don't think it is relevant to this bug report.

Tested with Mini-Month enabled and when I woke the computer this morning the Mini-Month date and Today Pane still did show yesterday's date and information.

Updated to today after a few seconds.

A lot of testing has been done on this. All documented.

Nobody is working on fixing the issue, so we can post here day and night, nothing will happen ;-)

(In reply to stephan from comment #35)

A lot of testing has been done on this. All documented.

Nobody is working on fixing the issue, so we can post here day and night, nothing will happen ;-)

I don't see an issue and this appears to be a support issue to me.

Let the PC run overnight and you will see that it does not update.

(In reply to stephan from comment #37)

Let the PC run overnight and you will see that it does not update.

I'm sorry. I thought the issue was with waking from sleep mode. That is what I tested and it works for me.

today-pane not updating if PC wakes from sleep-mode AFTER midnight; future appointments disappear if today-date is in the past or future

Don't know about past or future dates. Seems to me if you selected a date manually, that is the one you want to see when you wake from sleep.

Letting the PC run overnight would be a different bug IMHO.

The Today Pane functions correctly until you allow the PC to go into sleep mode whilst Thunderbird is left running. At midnight the PC date changes and upon waking PC and thus Thunderbird is still running, the PC date is correct, but the date in the Today Pane is still on the previous day, not the current day. Thunderbird Today Pane should show the current date. This is precisely the same bug as reported by the original postee - not a different bug.

I quote :
Problem 1:
When the PC sleeps and is woken up AFTER 00:00 so when it is woken up on the next day, then the today-pane will NOT automatically move to the next day. This can become an issue and work should be done on this, at least allowing the user to set this behaviour e.g. "check for today-date every x minutes".

It has been occuring since version 68 was introduced and mentioned a lot in the Support Forum.

My systems run 24 hours and do NOT go to sleep. Same problem.

I hope I don't add more confusion, but I had this issue too (see Comment 17 above) and it seeems to be gone now.

It looks like the update on May 27th to Version 68.8.0 (Linux Mint 19.3) fixed it for me.

Before I had the same problem but never had to restart Thunderbird, though: After waking up the PC in the morning I would just click the "O" button (the one between "<" and ">" in the Today Pane titled "go to today" or similar) and everything was fine again.

I'm going to leave my error console running all night tonight to see what happens in the morning when I wake from sleep. I've switched from GData Provider to CalDAV (thanks again Walt!) on both my home and work PCs and also to 78 beta so maybe there will be some better info in the error console tomorrow morning.

(In reply to WaltS48 [:walts48] from comment #34)

Tested with Mini-Month enabled and when I woke the computer this morning the Mini-Month date and Today Pane still did show yesterday's date and information.

Updated to today after a few seconds.

Sadly, I didn't see that behavior on 78.0b3. Waited a few minutes but it just sat there.

(In reply to stephan from comment #35)

A lot of testing has been done on this. All documented.

Nobody is working on fixing the issue, so we can post here day and night, nothing will happen ;-)

I originally thought "Assert failed: TypeError: realDay is null calUtils.jsm:141" stating it's null pointed to a possible spot int he code where the issue is happening. Isearched for calUtils.jsm and looked at line 141, it's a } and realDay seems to have been removed.

(In reply to Anje from comment #39)

The Today Pane functions correctly until you allow the PC to go into sleep mode whilst Thunderbird is left running. At midnight the PC date changes and upon waking PC and thus Thunderbird is still running, the PC date is correct, but the date in the Today Pane is still on the previous day, not the current day. Thunderbird Today Pane should show the current date. This is precisely the same bug as reported by the original postee - not a different bug.

I quote :
Problem 1:
When the PC sleeps and is woken up AFTER 00:00 so when it is woken up on the next day, then the today-pane will NOT automatically move to the next day. This can become an issue and work should be done on this, at least allowing the user to set this behaviour e.g. "check for today-date every x minutes".

It has been occuring since version 68 was introduced and mentioned a lot in the Support Forum.

Anje, thanks for your help in the support forums.

How do I allow my Ubuntu 18.04.4 Linux to go to into sleep mode without actually going to the Power button, selecting it, holding down the Power icon in the drop-down until it changes to a Pause icon then clicking the Pause icon until the monitor goes dark and the fans turn off? I leave Thunderbird open and maximized.

As for Problem 1.

When I wake the machine in the morning around 08:00 that is way AFTER 00:00, the View > Today Pane > Show Mini-Day as per the screenshots does show the previous day for about 3 to 5 seconds and then updates. That is okay with me.

Am I supposed to expect it to change at Midnight with the power off in Sleep mode?

What exactly in the Today Pane is the reporter talking about?

How did you test the problem?

The Mini-Day updates after a few seconds upon waking from sleep for me.
The Mini-Month updates after a few seconds upon waking from sleep for me.
The information in the Today Pane Events updates after a few seconds upon waking from sleep for me.

(In reply to stephan from comment #37)

Let the PC run overnight and you will see that it does not update.

Please read Comment 0 again.

Letting the PC run overnight is a different problem.

This is what Error Console showed in the AM when PC woke from sleep. Sorry about the formatting, it was a copy and paste:

07:09:52.002
NS_ERROR_ILLEGAL_VALUE: 2 CalRecurrenceInfo.jsm:736
modifyException resource:///modules/CalRecurrenceInfo.jsm:736
_assureRecurringItemCaches resource:///modules/CalStorageCalendar.jsm:1772
AsyncFunctionNext self-hosted:693
07:09:52.003 Lightning: recurrenceInfo::addException: item with null recurrenceId! CalRecurrenceInfo.jsm:735
07:09:52.003 Lightning:
Exception
​
columnNumber: 0
​
data: null
​
filename: "resource:///modules/CalRecurrenceInfo.jsm"
​
lineNumber: 736
​
location: XPCWrappedNative_NoHelper { QueryInterface: QueryInterface(), filename: Getter, name: Getter, … }
​
message: ""
​
name: "NS_ERROR_ILLEGAL_VALUE"
​
result: 2147942487
​
stack: "modifyException@resource:///modules/CalRecurrenceInfo.jsm:736:24\n_assureRecurringItemCaches/<@resource:///modules/CalStorageCalendar.jsm:1772:11\n"
​
<prototype>: ExceptionPrototype { toString: toString(), name: Getter, message: Getter, … }
CalStorageCalendar.jsm:297
07:09:52.003
NS_ERROR_ILLEGAL_VALUE: CalRecurrenceInfo.jsm:736
modifyException resource:///modules/CalRecurrenceInfo.jsm:736
_assureRecurringItemCaches resource:///modules/CalStorageCalendar.jsm:1772
AsyncFunctionNext self-hosted:693
07:09:52.062
XHRPOSThttps://accounts.google.com/o/oauth2/token[HTTP/2 200 OK 119ms]
07:09:53.140
REPORThttps://apidata.googleusercontent.com/caldav/v2/<removed>/events/[HTTP/2 207 Multi-Status 161ms]
07:09:53.141
XHRPOSThttps://accounts.google.com/o/oauth2/token[HTTP/2 200 OK 70ms]
07:09:53.143
TypeError: impl is null8 network-response-listener.js:104:7
_forwardNotification resource://devtools/server/actors/network-monitor/network-response-listener.js:104
onStatus resource://devtools/server/actors/network-monitor/network-response-listener.js:395

I have to withdraw my comment 41 above: The problem is back. When I woke up my PC this morning the Today Pane still showed yesterday's date. I waited for quite some time and it did not update.

The last messages from the error console are:

Lightning: [calCachedCalendar] replayChangesOn finished. calCachedCalendar.js:356
Lightning: [calCachedCalendar] sync queue empty. calCachedCalendar.js:328
Lightning: [calSleepMonitor] Sleep cycle detected, notifying observers. calSleepMonitor.js:25
Assert failed: TypeError: realDay is null
 calUtils.jsm:139
    ASSERT resource://calendar/modules/calUtils.jsm:139
    refreshUIBits chrome://lightning/content/messenger-overlay-sidebar.js:455
    notify chrome://calendar/content/calendar-views-utils.js:335

Thunderbird 68.8.0 on Linux Mint 19.3

Now that is interesting. There must be a failure here which would cause this bug. But I'm not sure how we get there yet.

Okay, found it. If the month view is selected but the calendar tab has not been shown since Thunderbird opened, this bug occurs. Can anybody confirm that?

(In reply to Geoff Lankow (:darktrojan) from comment #50)

Okay, found it. If the month view is selected but the calendar tab has not been shown since Thunderbird opened, this bug occurs. Can anybody confirm that?

That would explain why I'm sometimes seeing this bug, and sometimes not.

(In reply to Geoff Lankow (:darktrojan) from comment #50)

Okay, found it. If the month view is selected but the calendar tab has not been shown since Thunderbird opened, this bug occurs. Can anybody confirm that?

I rebooted yesterday and probably did not open the calendar tab since - but can't say for sure. Can you think of an easy way to verify this without having to wait for another day each time?

(In reply to Geoff Lankow (:darktrojan) from comment #50)

Okay, found it. If the month view is selected but the calendar tab has not been shown since Thunderbird opened, this bug occurs. Can anybody confirm that?

So, if I get it correctly, exact STR are:

1. Open thunderbird, go to calendar, select month view
2. restart thunderbird, do not open calendar
3. put your computer to sleep before midnight
4. wake it up after midnight

Right? Or is this also connected to the issue with going over midnight with TB running? I can give it a test today.

Just did the following test. TB was still in error condition (i.e. yesteday's date was still selected in the side bar).

• Called refreshUIBits(); in console. Result: I got the above exception
• Selected the calendar tab
• Called refreshUIBits(); again. Result: No exception
• Selected the Inbox tab again: Still yesteday was selected in the side bar
• Called refreshUIBits(); result: No exception, Today is now selected

(In reply to Martin Pecka from comment #53)

So, if I get it correctly, exact STR are:

Pretty much, although I've since got my VM to cooperate and have done this myself.

We already made this change in bug 1610832 (for other reasons) but it was not uplifted to ESR. That's why this bug has not been seen since 74. I don't think the line being removed actually did what it was supposed to anyway – the selected day in the month view is not changed at midnight.

This is what happens on my computers at midnight when I leave them on:

Assert failed: TypeError: realDay is null calUtils.jsm:139
ASSERT resource://calendar/modules/calUtils.jsm:139
refreshUIBits chrome://lightning/content/messenger-overlay-sidebar.js:455
notify chrome://calendar/content/calendar-views-utils.js:335

EVERY night.

And I do not use the monthly view.

Did this get pulled into the 78.0b4 that is on the FTP? If so, it didn't seem to fix the issue.

Is there any way to test this with 68.9?

(In reply to Arthur K. from comment #60)

Did this get pulled into the 78.0b4 that is on the FTP? If so, it didn't seem to fix the issue.
(In reply to stephan from comment #61)
Is there any way to test this with 68.9?

The answer to both is no.

Depending on how quickly things proceed it may get into 78.0b4. and maybe 68.10.0.

(In reply to Wayne Mery (:wsmwk) from comment #62)

(In reply to Arthur K. from comment #60)

Did this get pulled into the 78.0b4 that is on the FTP? If so, it didn't seem to fix the issue.
(In reply to stephan from comment #61)
Is there any way to test this with 68.9?

The answer to both is no.

Depending on how quickly things proceed it may get into 78.0b4. and maybe 68.10.0.

Like I said in comment 56, this change already landed in Thunderbird 74. If you are still seeing a problem, then there is another cause we have to find.

Ah, I need this kind of help.

Thunderbird 68.10.0:
https://hg.mozilla.org/releases/comm-esr68/rev/b9ce60200cb6

I'm calling this fixed to keep our systems happy. If you continue to see problems in Lightning 68.10.0, please file a new bug and reference this one.

I stand corrected. Today on both my home PC and office PC, it moved me to July 1st on mini-month without any intervention or needing to restart TB.

(In reply to Arthur K. from comment #67)

I stand corrected. Today on both my home PC and office PC, it moved me to July 1st on mini-month without any intervention or needing to restart TB.

Same here using 78.0b4.

Sorry, forgot to test with the 68.10 release candidate.

I tested intensively on multiple computers with 68.10 and I can confirm the problem when keeping TB running overnight (no sleep mode) is also fully gone. All fine! Thank you very much!

So. It seems not to be fully gone or something else is amiss. I'm testing on the 78.0RC. I left my error console running Tuesday night and didn't come back to my work PC until this morning and it was still stuck at Tuesday's date on the mini-month.

Error console showed this on Tuesday before I left for the day:

15:47:53.395 TypeError: this._idleService is undefinedimCore.jsm:152:20
_checkIdle resource:///modules/imCore.jsm:152
observe resource:///modules/imCore.jsm:122

When it woke just now, I saw these messages:

07:54:02.701 Lightning: recurrenceInfo::addException: item with null recurrenceId! CalRecurrenceInfo.jsm:735
07:54:02.703 NS_ERROR_ILLEGAL_VALUE: CalRecurrenceInfo.jsm:736
modifyException resource:///modules/CalRecurrenceInfo.jsm:736
_assureRecurringItemCaches resource:///modules/CalStorageCalendar.jsm:1772
AsyncFunctionNext self-hosted:693

As well as many repeated instances of this (in its unexploded view):

07:54:02.704 Lightning:
Exception
​columnNumber: 0
​data: null
​filename: "resource:///modules/CalRecurrenceInfo.jsm"
​lineNumber: 736
​location: XPCWrappedNative_NoHelper { QueryInterface: QueryInterface(), filename: Getter, name: Getter, … }
​message: ""
​name: "NS_ERROR_ILLEGAL_VALUE"
​result: 2147942487
​stack: "modifyException@resource:///modules/CalRecurrenceInfo.jsm:736:24\n_assureRecurringItemCaches/<@resource:///modules/CalStorageCalendar.jsm:1772:11\n"
​<prototype>: ExceptionPrototype { toString: toString(), name: Getter, message: Getter, … }

@Arthur K.

I think that might be bug 1648718 but I did not see any error messages in my Error Console this morning.

(In reply to WaltS48 [:walts48] from comment #71)

@Arthur K.

I think that might be bug 1648718 but I did not see any error messages in my Error Console this morning.

Yes, probably is related to bug 1648718.

What I'll try to do tonight on my home machine is leave my PC running all night and disable sleep so it doesn't power down whilst leaving error console running. Whatever happens at or shortly after midnight should show up in error console.

The error info I reported above was a fraction of the unexploded view. Is there a clean way to output it so it captures all the line things that appear after clicking a right arrows (►)? There may be more useful info if I drill down.

By "all the line things", I meant the furcation.

(In reply to Arthur K. from comment #73)

By "all the line things", I meant the furcation.

Not cleanly that I can see.

Expanded some I had in the Error Console and used either "Select All", then copied and pasted it into a text file, or use "Export Visible Messages To" and selected "File".

So between 11:30PM and 12:00AM, the only things in Error Console were below. Judging by that, it would seem mini-month has some other issue as in bug 1648718.

23:30:11.970 TypeError: impl is null network-response-listener.js:104:7
_forwardNotification resource://devtools/server/actors/network-monitor/network-response-listener.js:104
onProgress resource://devtools/server/actors/network-monitor/network-response-listener.js:391

00:00:11.680
XHRPOSThttps://accounts.google.com/o/oauth2/token [HTTP/2 200 OK 131ms]

00:00:11.842
XHRPOSThttps://accounts.google.com/o/oauth2/token [HTTP/2 200 OK 85ms]

00:00:11.842
REPORThttps://apidata.googleusercontent.com/caldav/v2/<removed>/events/ [HTTP/2 207 Multi-Status 232ms]

00:00:11.857
TypeError: impl is null5 network-response-listener.js:104:7
_forwardNotification resource://devtools/server/actors/network-monitor/network-response-listener.js:104
onStatus resource://devtools/server/actors/network-monitor/network-response-listener.js:395

So, is the original problem here actually fixed? I can't tell from the comments.

(In reply to Worcester12345 from comment #76)

So, is the original problem here actually fixed? I can't tell from the comments.

Not that I can see. I'm testing with 82.0b2 and as of right now (6:04AM CST), my mini-month is on Tue the 6th.

(In reply to Arthur K. from comment #77)

(In reply to Worcester12345 from comment #76)

So, is the original problem here actually fixed? I can't tell from the comments.

Not that I can see. I'm testing with 82.0b2 and as of right now (6:04AM CST), my mini-month is on Tue the 6th.

Please, have a look at bug 1648718, which is crossreferenced here a couple of times.

For the past couple of days, 98.0b3 has been acting ok for me. Haven't had to restart TB in order for minimonth to move the date.

(In reply to Geoff Lankow (:darktrojan) (away, back 7 Nov) from comment #66)

I'm calling this fixed to keep our systems happy. If you continue to see problems in Lightning 68.10.0, please file a new bug and reference this one.

It seems that the bug is back now in 102.4.0. I've opened a new issue here: bug 1797294

Maybe someone can also confirm?