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.

Sign up for GitHub

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

Jump to bottom

COST_ANSWER query for getInfo on invalid account id returns 0 #42

Closed
tinker-michaelj opened this issue May 12, 2020 · 0 comments
Closed

COST_ANSWER query for getInfo on invalid account id returns 0 #42

tinker-michaelj opened this issue May 12, 2020 · 0 comments
Assignees
@anighanta
Labels
Bug An error that causes the feature to behave differently than what was expected based on design. P1 High priority issue, which must be completed in the milestone otherwise the release is at risk. Release Note Issues which need a release note created.

Comments

@tinker-michaelj
Copy link
Collaborator

Summary of the defect
When the target account does not exist, a CryptoGetInfo query with response type COST_ANSWER has status OK (and cost 0) instead of INVALID_ACCOUNT_ID.

Suggested resolution
Make CryptoGetInfo response statuses consistent with the contract, file, and topic Get*Info queries.
@tinker-michaelj tinker-michaelj added Bug An error that causes the feature to behave differently than what was expected based on design. P1 High priority issue, which must be completed in the milestone otherwise the release is at risk. Release Note Issues which need a release note created. labels May 12, 2020
lukelee-sl pushed a commit that referenced this issue Mar 31, 2023
@tinker-michaelj @lukelee-sl
Use mirror address of selfdestruct-ed creation in record (#42)
7b858a6 
* Remove assumption that new contract address link persists

Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>

* Add comment

Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>

---------

Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>
@tinker-michaelj tinker-michaelj mentioned this issue Jan 4, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@anighanta anighanta

Labels
Bug An error that causes the feature to behave differently than what was expected based on design. P1 High priority issue, which must be completed in the milestone otherwise the release is at risk. Release Note Issues which need a release note created.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tinker-michaelj @anighanta