Skip to content

[CRE][Settings] Fix time parsing#1863

Merged
bolekk merged 1 commit intomainfrom
fix_time_parsing
Feb 27, 2026
Merged

[CRE][Settings] Fix time parsing#1863
bolekk merged 1 commit intomainfrom
fix_time_parsing

Conversation

@bolekk
Copy link
Contributor

@bolekk bolekk commented Feb 27, 2026

Accept two formats

@bolekk bolekk requested a review from a team as a code owner February 27, 2026 19:44
@github-actions
Copy link

👋 bolekk, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@github-actions
Copy link

github-actions bot commented Feb 27, 2026

📊 API Diff Results

No changes detected for module github.com/smartcontractkit/chainlink-common

View full report

@bolekk bolekk changed the title [CRE][Setting] Fix time parsing [CRE][Settings] Fix time parsing Feb 27, 2026
if t, err := time.Parse(time.RFC3339, s); err == nil {
return t, nil
}
return time.Parse("2006-01-02 15:04:05 -0700 MST", s) // Go default format
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The package docs show 2006-01-02 15:04:05.999999999 -0700 MST. Is the extra precision omitted intentionally? Is that ok?

jmank88
jmank88 previously approved these changes Feb 27, 2026
@bolekk bolekk enabled auto-merge February 27, 2026 20:02
@bolekk bolekk added this pull request to the merge queue Feb 27, 2026
Merged via the queue into main with commit 0f1cea0 Feb 27, 2026
37 checks passed
@bolekk bolekk deleted the fix_time_parsing branch February 27, 2026 20:27
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.

3 participants