fix: merged timeline orderby localtime #22371
Merged
Conversation
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
Contributor
|
I think this also covers #20150 (different description of the same issue) |
jrasm91
approved these changes
Sep 25, 2025
Member
Author
|
Drafted the PR to change the implementation. Will reopen it once the new fix is tested |
shenlong-tanwen
force-pushed
the
fix/merged-timeline-order
branch
from
b563eaa to
58f217d
Compare
shenlong-tanwen
force-pushed
the
fix/merged-timeline-order
branch
from
58f217d to
08ad22e
Compare
13 tasks
bwees
pushed a commit
that referenced
this pull request
Oct 6, 2025
* chore: refactor dateFmt to truncateDate * fix: merged timeline orderby localtime --------- Co-authored-by: shenlong-tanwen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Fixes #21612
Fixes #20150
created_atfromlocal_asset_entityis in local time while the one fromremote_asset_entityis currently stored in UTC resulting in the asset jumping on the timeline when it is updated. This fixes it by migrating thelocal_asset_entityto store the datetime values in the same format as stored in theremote_asset_entityHow has this been tested