Calendaring : Seeking clarity regarding the Room and Resource scheduling implementation

Hi all,

I was curious if someone could clarify how resource scheduling is intended to work within the dav application w/regards to CalDAV events?

In specific, this line within the scheduling plugin seems to be faulty.

The conditional’s log statement suggests that, given a CUTYPE of either ROOM, or RESOURCE, the condition should evaluate as True.

That doesn’t seem to be what the conditional is asserting, however. This seems to suggest that VEVENT processing given a CUTYPE=Room may not be happening as intended, and is only “working” due to other bugs.

Having done some naive testing to force a VEVENT of CUTYPE=Room to evaluate True for this branch, it seems that this conditional branch may be the root cause of other resource issues, e.g., “Infinite Checking Availability”, as a True evaluation here will also result in the “Infinite Checking Availability” issue for the described Room.

I’d be keen to clarify the above as needed; interested in understanding if this a problem with my assumptions, or with the code itself

Cheers

2 Likes

The logging looks like it was added well after the logic in that area of code. I think the log may be incorrect and should say something like:

Calendar user type is *neither* room nor resource, not processing further

I can’t speak to the larger context offhand as I’m not familiar with this area of code.