Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

null values are interpreted incorrectly #40

Open
karenetheridge opened this issue Jan 20, 2020 · 1 comment
Open

null values are interpreted incorrectly #40

karenetheridge opened this issue Jan 20, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@karenetheridge
Copy link
Contributor

e.g. in kosh builds ls, a null timestamp (in the 'completed' column) is inflated to the value '0001-01-01 00:00:00 +0000 UTC', or '0001-01-01T00:00:00Z' in the json view -- this would cause client scripts to mistakenly believe the build is completed, as this time is in the past.

Null uuids are displayed as 00000000-0000-0000-0000-000000000000 which is also incorrect.
@karenetheridge karenetheridge added the bug Something isn't working label Jan 20, 2020
@karenetheridge
Copy link
Contributor Author

kosh build us-east-1-ceres has similar issues.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@karenetheridge