I’m on the current node release version and some cli test uploads of 1.5Gb files are often triggering ‘PaymentQuoteOutOfRange’ errors, which in turn causes chunk not stored. Its taken 2-3 upload attempts to get all chunks committed. Is anyone else seeing this problem? Not under any illusion that stability is quite here yet.
3 Likes
Yes, I have heard others mention this behaviour. @Mightyfool might be able to explain further since he has done some uploading recently
3 Likes
There are 3 errors I’m seeing at the moment when uploading with Merkle:
- Merkle batch upload: Payment error: Wallet error: MerklePayment(“Payment failed: Transaction failed to send: server returned an error response: error code -32000: oversized data”)
- Merkle batch upload: Payment error: Not enough valid candidate responses: got 15, needed 16
- Merkle batch upload: Payment error: Wallet error: MerklePayment(“Payment failed: Transaction reverted with data”)
Is it any of these 3 you’re seeing? I’m not familiar with the error code name you mentioned.
Merkle uploads are definitely still struggeling a bit and (hopefully) will be fixed in this weeks release according to the team. You can use regular payments in the meanwhile which is a bit more expensive but works like a charm.
3 Likes
I get this one a lot too.
2 Likes
Still? Because it is supposed to be fixed in the latest release once the older nodes are filtered out by the network I haven’t tested in a few days now but I guess it should be a lot less common already.
1 Like
I’m seeing the over sized data error when trying to upload with merkel
Yeah that’s my main issue as well at the moment. This is what the team mentioned could hopefully be addressed in this week update.
1 Like
I probably tried a big upload about 3 days ago. I will keep an eye on impact going forward.
2 Likes
I’ll check Merkle tonight, the other errors were non Merkle