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

Improperly formatted proto file causes ORDER_BY_DESC enum to be parsed incorrectly #15437

Closed
colin-axner opened this issue Mar 17, 2023 · 3 comments
Labels

Comments

@colin-axner
Copy link
Contributor

Summary of Bug

There's an extra semi-colon in the proto file on the release/v0.46.x line (fixed on main/v0.47)

Version

release/v0.46.x

Steps to Reproduce

Using stake.tax you can use any chain on the v0.46.x release line, use the cli to generate csv and you'll run into the error: strconv.ParseInt: parsing "ORDER_BY_DESC": invalid syntax'. This can be fixed on stake.tax by using 2 instead of ORDER_BY_DESC. I believe removing the extra semi-colon will allow the enum to be properly parsed again

Please add a test for this workflow since dependencies use this functionality

@julienrbrt
Copy link
Member

What kind of test are you thinking about?

@colin-axner
Copy link
Contributor Author

What kind of test are you thinking about?

A test that uses the order_by argument in the URL request? Would that be possible?

@julienrbrt
Copy link
Member

@julienrbrt julienrbrt closed this as not planned Won't fix, can't repro, duplicate, stale Oct 1, 2024
@github-project-automation github-project-automation bot moved this from 📋 Backlog to 🥳 Done in Cosmos-SDK Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🥳 Done
Development

No branches or pull requests

3 participants