I’m Building the .Net-Wrapper for libuplink and it works basically. But I have huge Problems while uploading. If my file exceeds a certain amount, the upload Always Fails with an error like this:
“segment error: ecclient error: successful puts (0) less than or equal to repair threshold (35)
I’m not sure what happens and how I can debug this. It might be a Problem with my Proxy, with the call to the Underlying CGO-libuplink, something sepcific to .Net or even an issue on the satellite. I’m uploading to “europe-west-1.tardigrade.io” and I’m using the latest GitHub-commit ( d3ef574) for libuplink to build my wrapper.
What I find strange: if I watch the Network utilisation, it gets slower and slower the more data I “upload_write” to the Uploader. Basically I do the following:
loop while there are Bytes left
I’m sending Bytes in Batches of 1024 Bytes. So every “upload_write”-call gets the next 1024 Bytes. the strange Thing is: the function immediately Returns even if I put around 100MB into it. Shouldn’t it send what I’ve put unto first and come back to me then? If I have a 100MB-file and cut it into 1024bytes-pieces, the uploader might struggle handling all those Little pieces?
I really Need help on this one as it makes my wrapper not reliable and I Need to know if the Problem is on my side and where. I would love to get Feedback on
- do I do the upload Right?
- what is the best amount pushed to a call to upload_write?
- is there any way to debug what is really being sent?
- shouldn’t the call to upload_write block until the data is really sent?