[19.0][MIG] resource_booking#1
Open
dnplkndll wants to merge 6 commits into
Open
Conversation
dnplkndll
changed the title
dnplkndll
force-pushed
the
19.0-mig-resource_booking
branch
from
946e5f5 to
c6ef9ab
Compare
dnplkndll
force-pushed
the
19.0-mig-resource_booking
branch
3 times, most recently
from
53d4b5d to
21d0bd2
Compare
…ctly When using a booking type with a resource calendar that has a different time zone than the resource itself, the slots are returned with mixed time zones. This commit normalizes the behavior and ensures that slots are always returned in the time zone of the booking type. Steps to reproduce: Create a resource with the time zone America/Guayaquil, and a calendar that starts from 06:00 to 15:00. Create a resource booking type with a new calendar that starts from 09:00 to 16:00, and set the time zone to Europe/Madrid. Before this commit, the slot displayed in the portal was 06:00, but it should have been 12:00. After this commit, the slot is displayed in the correct time zone (Madrid) at 12:00. Note: The 06:00 in America/Guayaquil corresponds to 12:00 in Madrid standard time, not during daylight saving time. The tests use a freeze date in February.
When a user had no resource_booking permissions and opened a calendar event linked to a resource booking, he got an unnecessary access error.
dnplkndll
force-pushed
the
19.0-mig-resource_booking
branch
from
21d0bd2 to
aa94567
Compare
Odoo 19.0+ HttpCase tour tests leave renderer/websocket chrome subprocesses that don't exit when the parent is killed; Odoo's own test framework reports them via WARNING "Killing chrome descendants- or-self of N: M remaining". These are benign cleanup notifications emitted AFTER the test result line, not test failures. Without this ignore pattern, any 19.0 PR that includes tour tests in resource_booking (test_portal_no_bookings, test_portal_list_with_ bookings, etc.) deterministically fails CI even when 0 tests fail. This is an OCA-CI configuration fix, not a module change. Will be split into its own PR once verified on the OCA#217 retrigger.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.