After an on-prem upgrade to 1.7.4, is there a comm...
# general
m
After an on-prem upgrade to 1.7.4, is there a command to clear or build up the cache of calendar availability? I'm finding that the availability is showing many more times than I should have, especially repeating events
z
Can you elaborate? I think I'm not following
m
I might be mistaken about the feature, so please forgive me if I've mixed this up. I thought that 1.7.x added the ability to cache an external calendar's availability, so that you didn't have to click on each day to find available times. What I'm seeing is that classic "more times shown than actually available" when you browse.
Troubleshooter seems to be broken so it's hard to confirm. https://github.com/calcom/cal.com/issues/3169
For 6/30 at Americas/Chicago, there should be blocks at 10a, 11a, 11:30a, 3p-4p, and 5p.
All repeating appointments from a while back.
z
This a know issue. Can you try using latest main?
m
z
We added a cache layer to fetch external calendars to speed up subsequent queries in the next 30 seconds. But also we query the time slots for the whole month so you don't have to load each individual day. It's a tradeoff really.
Does this looks good to you?
m
Ok, struggled a bit but am now at main branch again. Here's what troubleshooter is showing me and what the actual view show me for 6/29 (changed to allow bookings within 0 minutes):
z
@alannnc I don't think we're running the same function for troubleshooter. cc @Emrysal
👍 1
e
That's right, I think we still duplicate that
m
In this instance, troubleshooter is accurate but the public booking page is not, shows wide open.
Ok, looks like the problem is with a timeout when checking on specific day's availability. From Chrome: "The operation was aborted."stack: "TRPCClientError: The operation was aborted.\n at Function.value (https://book.gravislaw.com/_next/static/chunks/pages/_app-6410f8f9e4562f0e.js:1:7039"
Should I open an issue instead of messages like this?
e
The timeout we've diagnosed and will be fixed shortly :)
👍 1
m
Thank you @Emrysal - should I roll back to an older version for the time being?
e
Hi @Mark Z. - sorry was at a dinner; It's hard to revert due to an migration but the PR to fix is now in review @ https://github.com/calcom/cal.com/pull/3201/files
m
@Emrysal don't ever apologize for taking a dinner - I really appreciate your prompt help on this! I see the PR was committed, I'll give it a try. Thank you!!
@Emrysal I ended up doing a clean pull of main and deployed it to our production - the page is loading quite quickly, but I'm getting react errors in the console and still don't have proper availability loaded. https://book.gravislaw.com/mzocher/30min
I bumped to 1.7.5 just in case, but still seeing the errors in console
z
Does availability loads tho? The console errors I think is because locale mismatch but it should not affect the functionality
m
No, availability does not load. Currently it's saying I'm available all day on 7/4 (US Independence day, has a blocker on my Exchange calendar). https://book.gravislaw.com/mzocher/30min?month=2022-07&date=2022-07-04
If I select a time and go through to the end, it keeps me from actually blocking a time saying I'm unavailable
z
Looks blocked on my end tho
m
Ok, that's good to see! I've refreshed and see the 4th blocked out, but I'm still seeing wide availability for me on July 18-20 when I've got blockers from 10a-7p each day in Outlook.
z
Also if I select it via query it doesn't load any time slots
m
Now I'm starting to think I'm crazy @zomars 🙂 Here's what I'm seeing for July 18th, a day I'm booked from 10a-7p Central
And when I switched to another browser and loaded the page, it went back to saying i was available July 4th.
e
You weren't crazy @Mark Z. - turned out there was an issue with a cache key which resulted in busy times sometimes clearing out (the same cache key was used for Available times and for the month availability) - which randomly meant that the cache key only had one day worth of busy times. Took most of my weekend to nail down but it's fixed in upcoming release v1.7.6
🙏 1
m
Sounds like a painful way to spend a weekend @Emrysal, but I really appreciate your hard work finding and fixing that! I'll watch for 1.7.6 and apply that ASAP. Thanks again!
🙏 1