This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
Bug: Order spend panic [ETH] #2012
Labels
bug
ethereum
Ethereum integration-related issues.
🔍 readyForReview
Issue or PR ready for code review prior to closing.
Projects
Comments
It's clear after reviewing the data that the purchase order used an item and shipping option that charged a few cents for every unit (and there are 10000000000 units), which returned an expected price of ~$1 billion dollars lol. The UPDATE: Using the correct purchase order payload, the test passed.
|
drwasho
added
the
🔍 readyForReview
Issue or PR ready for code review prior to closing.
label
Mar 4, 2020
Ran into this panic again after attempting to fetch an order 2 seconds after releasing the funds from escrow:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
ethereum
Ethereum integration-related issues.
🔍 readyForReview
Issue or PR ready for code review prior to closing.
Context
AWAITING_PAYMENT
due to a problem in thePOST /ob/orderspend
call200 OK
but an empty response... so the problem wasn't handled properly, on top of whatever the problem isThe Problem
To reproduce the problem locally, you'll need to:
Complete moderated online (eth, +options, +shipping, +taxes, +coupons, q=10000000000)
:This is the order flow of the test:
This is the listing:
This is the purchase order payload:
This is the purchase order response:
This is the order spend (
POST /ob/orderspend
) payload:The response was:
At the same time, this appeared in stdout:
The text was updated successfully, but these errors were encountered: