Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Changing the scheduled hour also changes the date #1062

Open
gregorydlogan opened this issue Jan 14, 2025 · 1 comment
Open

Changing the scheduled hour also changes the date #1062

gregorydlogan opened this issue Jan 14, 2025 · 1 comment
Labels
type:bug Something isn't working

Comments

@gregorydlogan
Copy link
Member

gregorydlogan commented Jan 14, 2025 •
edited
Loading

Oh boy. I'm going to do this in video form since it's probably easier to get:

2025-01-14.12-05.Display.OC.Studio.webm

This occurs regardless of what start time I set. Notably this does not happen for @lkiesow who is in a not-negative-UTC timezone.

I suspect that this comment might be relevant but haven't stepped through the code.

Further weirdness: Despite what I said earlier (when it wasn't doing this), the end time is also displaying weird behaviour later in the day

2025-01-14.16-28.Display.OC.Studio.webm
@gregorydlogan gregorydlogan added the type:bug Something isn't working label Jan 14, 2025
@gregorydlogan
Copy link
Member Author

Trying to schedule things is also very broken, obviously. This line has a value of "2025-01-14T00:00:00.000Z" when I try and schedule a recording for that time in UTC-6, so we've at the very least lost the fact that we're in UTC-6 (the browser renders it as 1800 on 25-01-13), and then the next few things muck with the hours so...

This reminds me a lot of the pain we went through with the original admin UI. The USask team exposed a lot of timezone related things back then :D

Arnei added a commit to Arnei/opencast-admin-interface that referenced this issue Jan 15, 2025
@Arnei
Fix scheduling for negative timezones
1b4c565 
And hopefully all other timezones. The date for a
scheduled event should now always be correct,
no matter what hour/minute is selected.

Aims at fixing opencast#1062.
@Arnei Arnei mentioned this issue Jan 15, 2025
Merged
Arnei added a commit to Arnei/opencast-admin-interface that referenced this issue Jan 15, 2025
@Arnei
Fix scheduling for negative timezones
72159e1 
And hopefully all other timezones. The date for a
scheduled event should now always be correct,
no matter what hour/minute is selected.

Aims at fixing opencast#1062.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gregorydlogan