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
{{ message }}
This repository was archived by the owner on Mar 3, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 3, 2026. It is now read-only.
test: finish updating conformance test upload cases #2193
In #2190 I tried to add two new upload cases including 408 errors. One of them was fine, but the case "instructions": ["return-503-after-8192K", "return-408"] failed with the following error on various upload methods:
RangeError: The offset is lower than the number of bytes written. The server has 0 bytes and while 8388608 bytes has been uploaded - thus 8388608 bytes are missing. Stopping as this could result in data loss. Initiate a new upload to continue.
This looks like a bug in resetting the offset for the upload after a failure. It may be a bug in the testbench for some particular case; however, I tested manually and verified that the testbench correctly implements the method to query upload status at least for a simple case of uploading in chunks. Some debugging has to be done in the Node library to understand what is failing here.
RangeError: The offset is lower than the number of bytes written. The server has 183762944 bytes and while 184465013 bytes has been uploaded - thus 702069 bytes are missing. Stopping as this could result in data loss. Initiate a new upload to continue.
at Upload.startUploading (/home/simon/Dev/hokify/hokify/node_modules/.pnpm/@[email protected]/node_modules/@google-cloud/storage/build/cjs/src/resumable-upload.js:463:32)
at Upload.continueUploading (/home/simon/Dev/hokify/hokify/node_modules/.pnpm/@[email protected]/node_modules/@google-cloud/storage/build/cjs/src/resumable-upload.js:450:21)
at processTicksAndRejections (node:internal/process/task_queues:95:5) RangeError
hard to reproduce, but it happens quite a lot lately... any idea what I could try to fix this?
Activity
simllll commentedon Apr 18, 2024
I think I ran into something simliar:
hard to reproduce, but it happens quite a lot lately... any idea what I could try to fix this?
iamstarkov commentedon Aug 19, 2024
we experienced it during the production workflow run