You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
When submitting a WASM-based transaction with "classic" payment, if the payment-amount exceeds the highest gas lane limit, the transaction fails with a generic error message:
{"code":-32016,"message":"Invalid transaction","data":"the transaction was invalid: The transaction sent to the network was invalid for an unspecified reason"}
The current error message lacks clarity and does not explain that the failure occurs because the payment amount cannot be assigned to an existing gas lane.
{"code":-32016,"message":"Invalid transaction","data":"the transaction was invalid: The transaction sent to the network was invalid for an unspecified reason"}
Expected Behaviour:
The error message should clearly explain that the transaction failed because the payment-amount exceeded the largest available gas lane.
Actual Behaviour:
A vague error message is returned, making debugging difficult
Related PR/Changes:
Recent change (merged on Dec 15) that modifies behavior around gas lane determination for classic payment.
Additional Context:
Reported by Jiuhong during testing. Confirmed by Jakub that the issue arises when the payment exceeds the largest gas lane limit (100000000000).
Acceptance Criteria:
The error message clearly specifies that the payment amount exceeds the allowable gas lane limit.
The change is reflected in casper-node and/or casper-sidecar logs and responses.
A test case is added to verify this scenario.
The text was updated successfully, but these errors were encountered:
Description:
When submitting a WASM-based transaction with "classic" payment, if the payment-amount exceeds the highest gas lane limit, the transaction fails with a generic error message:
The current error message lacks clarity and does not explain that the failure occurs because the payment amount cannot be assigned to an existing gas lane.
Steps to Reproduce:
casper-client put-transaction package \ --chain-name casper-test-jh \ -n http://172.31.27.77:7777 \ --package-address package-10314994ca14feddc562fe63c7407f750c6f81a0ced65e0e33c0ad63fcbe0281 \ --session-entry-point apple \ --payment-amount 500000000000 \ --pricing-mode classic \ --gas-price-tolerance 2 \ --standard-payment true \ --secret-key /home/ubuntu/keys/test0/secret_key.pem
Expected Behaviour:
The error message should clearly explain that the transaction failed because the payment-amount exceeded the largest available gas lane.
Actual Behaviour:
A vague error message is returned, making debugging difficult
Environment Details:
casper-node:
61b78eabc52e1de3489c5652810dc030a1a5743f
casper-sidecar:
359792250d1f4d998a347546b8205cac15c86bd6
casper-client:
2e4bfcdda1d699a60183631cb619371d5c2f5d51
Related PR/Changes:
Recent change (merged on Dec 15) that modifies behavior around gas lane determination for classic payment.
Additional Context:
Reported by Jiuhong during testing. Confirmed by Jakub that the issue arises when the payment exceeds the largest gas lane limit (100000000000).
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: