Skip to content

Fix unix epoch showing for job started#367

Closed
oblakeerickson wants to merge 1 commit intooxidecomputer:mainfrom
oblakeerickson:job-started-epoch
Closed

Fix unix epoch showing for job started#367
oblakeerickson wants to merge 1 commit intooxidecomputer:mainfrom
oblakeerickson:job-started-epoch

Conversation

@oblakeerickson
Copy link
Copy Markdown
Contributor

Adding .nullable() allows null values to pass through as null rather than being coerced to a Date.

Fixes #353

Adding `.nullable()` allows null values to pass through as null rather than
being coerced to a Date.

Fixes oxidecomputer#353
@augustuswm
Copy link
Copy Markdown
Contributor

Appreciate it! I will give this a test and get it merged.

@augustuswm
Copy link
Copy Markdown
Contributor

Hey, for transparency I likely won't get to testing this until January as there are a lot of other competing priorities currently. I will get back to it though, and my apologies for the delay.

@oblakeerickson
Copy link
Copy Markdown
Contributor Author

@augustuswm Thank you for letting me know, appreciate it. That's not a problem at all. No rush on my end.

If I get the spare time over xmas break to work on some other PRs please know that anything I submit can be looked at whenever you get a chance and in 2026.

@augustuswm
Copy link
Copy Markdown
Contributor

Superseding this with #370 . This particular issue is a symptom of the larger problem that we were still using and old version of the ts client generator.

@augustuswm augustuswm closed this Dec 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Job started time is unix epoch

2 participants