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

LCD deposits for proposals returns null #4276

Closed
4 tasks
sabau opened this issue May 6, 2019 · 6 comments
Closed
4 tasks

LCD deposits for proposals returns null #4276

sabau opened this issue May 6, 2019 · 6 comments

Comments

@sabau
Copy link
Contributor

sabau commented May 6, 2019

Summary of Bug

I was going to add a ticket but can be an extension of this:

https://stargate.cosmos.network/gov/proposals/4/deposits
Returns null -> probably because it's rejected, still I would expect an empty array
So probably this is related to:
#4114

https://stargate.cosmos.network/gov/proposals/5/deposits
returns null -> this Passed so we should have the deposits list

Probably adding the tests will fix it
#3094

Version

0.34.1

Steps to Reproduce

When I access a Passed proposal https://stargate.cosmos.network/gov/proposals/5/deposits
Then I should receive the list of deposits

When I access a rejected proposal https://stargate.cosmos.network/gov/proposals/4/deposits
Then I should receive an empty array (is this true? #4114)


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@fedekunze
Copy link
Collaborator

this is not a bug, it is part of the chain's pruning strategy and is expected. See #2880 for more details

@fedekunze fedekunze removed the T:Bug label May 6, 2019
@fedekunze
Copy link
Collaborator

oh you mean the REST response, then yes. I guess we need to return the empty array

@sabau
Copy link
Contributor Author

sabau commented May 6, 2019

For proposal 4 it's just null instead of []
But for proposal 5 it seems we are missing the deposits. I've seen that this is the behaviour for the getter, but for the REST endpoint I would expect the outcome to be the same, so in the background it should query the transactions, giving this extra effort to the cilents will move this extra complexity on their side

@alexanderbez
Copy link
Contributor

It seems the governance module's client package is itself turning into a meta-client 🙁

It's the only module I know of that does these meta tx query aggregations for you...I don't know if we're heading down the right path here, but I guess it does help upstream clients a lot. Also doing proofs on this will be tough.

@sabau
Copy link
Contributor Author

sabau commented May 20, 2019

Agree! doing proofs would be tough!
I've seen a PR today that will mitigate this, seems not burning them at all unless vetoed or ignored:
#4374
It follows the porposal:
https://hubble.figment.network/cosmos/chains/cosmoshub-2/governance/proposals/6

@fedekunze
Copy link
Collaborator

moved to #4741

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

No branches or pull requests

3 participants