-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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.
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
BUG-Date control time jumps forward with DST #563
Comments
…ault-methods Refactor#470 - Rename configure_default_..() methods to set_default_..()
A client reported this issue again. It seems tricky to handle. |
This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines. |
Hi @jrobinAV I would like to tackle this bug for |
Let me assign this to you @IvanLauLinTiong. If you need help, you can ask @FabienLelaquais. Thank you for your contribution |
New Quest!A new Quest has been launched in @Avaiga’s repo. Some loot has been stashed in this issue to reward the solver! 🗡 Comment ⚔️ When you submit a PR, comment Questions? Check out the docs. |
@arcanaxion @FlorianJacta could please assign the above issue to me, if @IvanLauLinTiong is not working on it. |
This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines. |
Hey @arcanaxion, @FabienLelaquais, Is this issue happening only for this "Australia/Melbourne" location alone? Because when I tried from my end, the issue doesn't seem to happen for different timezones. I'd appreciate if you provide any inputs! |
This issue has been labelled as "🥶Waiting for contributor" because it has been inactive for more than 14 days. If you would like to continue working on this issue, please add another comment or create a PR that links to this issue. If a PR has already been created which refers to this issue, then you should explicitly mention this issue in the relevant PR. Otherwise, you will be unassigned in 14 days. For more information please refer to the contributing guidelines. |
This issue has been unassigned automatically because it has been marked as "🥶Waiting for contributor" for more than 14 days with no activity. |
Description
The time portion of the date control behaves strangely when attempting to select a time after clocks shift with DST.
Specifically, when selecting a time after the clock moves forward (an hour) with DST, the control automatically modifies my selection by +1 hour.
How to reproduce
Then,
a. The taipy app time_zone is set to Melbourne, which turns their clock forward at 2023-10-01T02:00:00 to 2023-10-01T03:00:00
a. E.g. clicking the hour 04 would instead select 05
Also
Expected behavior
No automatic incrementing should happen and possibly also 0200 <= time < 0300 (which doesn't exist on 2023-10-01 in Melbourne) should not be selectable.
Screenshots
Runtime environment
The text was updated successfully, but these errors were encountered: