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
RP2ValueError("Total in-transaction value < total taxable entries") from None #24
Comments
The error is saying that total crypto in < total crypto out. If you sum the 3 crypto in entries you get 1.3031783, which is less than the amount disposed of in the out transaction (1.30317832). Could you check on the Coinbase-generated CSV files and verify the following:
|
Here's the 4 raw transactions.
So, it looks like there's a few more digits in the raw transactions vs. what the ODS outputted, so it seems like a rounding issue? |
This is from the Coinbase CSV, correct? The next step is to look for these 4 transactions in the DaLI debug log: this will show us what numbers Coinbase is putting out via the REST API. Definitely looks like a rounding issue, but looking at the REST output from the debug log will tell us who's rounding incorrectly (DaLI or Coinbase). |
Yes, the above post was the Coinbase CSV. Here's the DEBUG logs:
Looks like the 3 IN total to 1.3031783 So it's off by −0.00000002 |
Now that I see that's the crypto values, I may have to just manually edit a few around to make sure that the rounding errors are corrected in the ODS. |
Yes, looks like Coinbase is feeding us bad data via REST (though the error is really small)... :-( However it's interesting that they are generating their CSV file correctly: perhaps they have another version of the REST API they use only internally. |
Yeah. I was able to generate the RP2 files after manually adjusting. Since I think this is a limitation on the REST API data, I don't think it's specifically an RP2 issue. I guess close this out? |
Yes, it's a problem with Coinbase REST data. Let's close the issue. Thanks for reporting! |
BTW, the RP2 error message was a bit cryptic: I improved it and now it should be easier to understand. |
Is there a work around for this issue? |
Unfortunately not... This is a Coinbase REST API bug, so there isn't a lot we can do about it. The only workaround would be to write a script to patch the ODS file before feeding it to RP2. |
Here's something hacky I put together a while ago for testing purposes. With a few modifications you should be able to use it to patch your file before feeding it to RP2:
|
I didn't have very complicated amount of transactions. (Multiple INs, and 1 OUT), so I ended up just SUM-ing the values to make it equal in the ODS file. |
RP2
Version: RP2 0.9.26 (https://pypi.org/project/rp2/)
Command:
rp2_us -m fifo -o output/ -p rp2_ output/crypto_data.config output/crypto_data.ods
Ran DaLI with Coinbase REST API for output ODS file and config file. Logs show:
Looking at LRC table:
From what I see, it's $1.50 in and $1.50 out. I'm not sure if there's something else I should be looking at.
The text was updated successfully, but these errors were encountered: