Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Improve error message for bad timestamps #70

Merged
merged 2 commits into from
Jun 6, 2023

Conversation

ValarDragon
Copy link
Contributor

Its very painful to figure out how to correctly encode timestamps right now. This at least saves one step, so you know what to google

@ValarDragon ValarDragon requested a review from a team as a code owner June 5, 2023 18:57
@ValarDragon ValarDragon changed the title Improve error message for bad timestamps feat: Improve error message for bad timestamps Jun 5, 2023
@ValarDragon
Copy link
Contributor Author

The continuous integration error is certainly unrelated to this pr, its about go.sum which this can't be affecting.

@ValarDragon
Copy link
Contributor Author

Looks like it broke in the last merged PR: #69

@julienrbrt
Copy link
Member

julienrbrt commented Jun 6, 2023

Looks like it broke in the last merged PR: #69

No, we just kept the CI from the original repo, which was not optimal.
Basically, you need to update those deps to make CI happy; otherwise it updates in CI and crash (as it does a go get)
Fixed #71 so it do not happen again.

@julienrbrt julienrbrt enabled auto-merge (squash) June 6, 2023 20:54
@julienrbrt julienrbrt merged commit 7118606 into cosmos:main Jun 6, 2023
3 of 4 checks passed
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.

None yet

3 participants