Revert timezone workaround for submitted vs completed timestamps#195
Merged
batzionb merged 1 commit intoRHEcosystemAppEng:mainfrom Mar 30, 2026
Merged
Conversation
…amp" This reverts commit 0f59a42.
batzionb
requested review from
IlonaShishov,
rhartuv,
vbelouso and
zvigrinberg
as code owners
Collaborator
Author
|
Agent fix here |
zvigrinberg
approved these changes
Mar 30, 2026
Collaborator
zvigrinberg
left a comment
zvigrinberg
left a comment
There was a problem hiding this comment.
@batzionb Good catch
This is better.
LGTM Approved.
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
3 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.
Reverts #181 / commit 0f59a42 (timezone mismatch workaround).
Why revert
The web UI relies on ISO-8601 timestamps with an explicit UTC marker (
Z) so JavaScriptDateparsing andIntl/locale formatting behave correctly. The reverted change compensated for agent payloads that omit timezone information. This produced UI with none browser localized dates.Root cause
The vulnerability-analysis agent sets
started_atandcompleted_atwith naivedatetime.now().isoformat()strings (noZor offset). The durable fix is for the agent to produce explicit UTC dates, not to adjust behavior in Morpheus backend or UI for naive timestamps.Made with Cursor
Resolves https://redhat.atlassian.net/browse/APPENG-4833