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

function trapped tx result when footprint is insufficient #1111

Open
leighmcculloch opened this issue Oct 13, 2023 · 5 comments
Open

function trapped tx result when footprint is insufficient #1111

leighmcculloch opened this issue Oct 13, 2023 · 5 comments
Labels
bug Something isn't working

Comments

@leighmcculloch
Copy link
Member

What version are you using?

v20.0.0-rc.2.1

What did you do?

Invoked a transaction with insufficient footprint.

What did you expect to see?

An error indicating that the resources were exceeded.

What did you see instead?

"function trapped" error.

Discussion

Bundling footprints in with "function trapped" is pretty ambiguous. We return specific resource related errors when other resources are exceeded.

@leighmcculloch leighmcculloch added the bug Something isn't working label Oct 13, 2023
@dmkozh dmkozh closed this as completed Oct 13, 2023
@anupsdf
Copy link
Contributor

anupsdf commented Oct 13, 2023

Fixed in #1112

@leighmcculloch
Copy link
Member Author

Does #1112 fix this for all insufficient footprints? or just nonce footprint? This issue is intended to be more general than the nonce case.

@dmkozh
Copy link
Contributor

dmkozh commented Oct 16, 2023

Does #1112 fix this for all insufficient footprints? or just nonce footprint? This issue is intended to be more general than the nonce case.

It fixes only the nonce case because other cases have been decorated before that. Nonce case was just missed during the initial round of fixes.

@leighmcculloch
Copy link
Member Author

Reopening the issue then because this issue is not about the nonce case not generating a diagnostic event. Rather, it's about how in general insufficient footprint errors are communicated to the user as a "function trapped" rather than a "exceeds resources" or "exceeds footprint".

@dmkozh
Copy link
Contributor

dmkozh commented Oct 16, 2023

The footprint errors do have the corresponding diagnostic events. I'm not sure we have time/need to change the error code to resource limit exceeded - it doesn't seem like it would significantly more information and it won't be distinguishable from CPU/mem exceeded errors without diagnostics (at which point you don't care what's the top-level error code is).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants
@leighmcculloch @dmkozh @anupsdf and others