Skip to content
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

Bug: Can't use query size script to fix file sizes when using S3 (B2) #350

Closed
NebulaBC opened this issue Mar 28, 2023 · 6 comments · Fixed by #386
Closed

Bug: Can't use query size script to fix file sizes when using S3 (B2) #350

NebulaBC opened this issue Mar 28, 2023 · 6 comments · Fixed by #386
Labels
bug Something isn't working

Comments

@NebulaBC
Copy link

What happened?

When running docker compose exec zipline yarn scripts:query-size I get:

/zipline/node_modules/minio/dist/main/transformers.js:149
      var e = new errors.S3Error(message); // S3 Error code.
              ^
S3Error: Not Found
    at getError (/zipline/node_modules/minio/dist/main/transformers.js:149:15)
    at /zipline/node_modules/minio/dist/main/transformers.js:161:14
    at DestroyableTransform._flush (/zipline/node_modules/minio/dist/main/transformers.js:91:10)
    at DestroyableTransform.prefinish (/zipline/node_modules/readable-stream/lib/_stream_transform.js:129:10)
    at DestroyableTransform.emit (node:events:513:28)
    at prefinish (/zipline/node_modules/readable-stream/lib/_stream_writable.js:611:14)
    at finishMaybe (/zipline/node_modules/readable-stream/lib/_stream_writable.js:620:5)
    at endWritable (/zipline/node_modules/readable-stream/lib/_stream_writable.js:643:3)
    at Writable.end (/zipline/node_modules/readable-stream/lib/_stream_writable.js:571:22)
    at IncomingMessage.onend (node:internal/streams/readable:705:10) {
  code: 'NotFound',
  amzRequestid: null,
  amzId2: null,
  amzBucketRegion: null
}

Node.js v18.15.0
error Command failed with exit code 1.

Version

upstream (ghcr.io/diced/zipline:trunk)

What browser(s) are you seeing the problem on?

No response

Zipline Logs

No response

Browser Logs

No response

Additional Info

I'm using Backblaze's implementation of S3.

@NebulaBC NebulaBC added the bug Something isn't working label Mar 28, 2023
@github-actions github-actions bot added this to the 3.7.1 milestone Mar 28, 2023
@diced
Copy link
Owner

diced commented Apr 6, 2023

#363 Does this PR (latest commit as of now), fix any of the issues here?

@TacticalTechJay
Copy link
Collaborator

Hey there @NebulaBC, just checking in to see if your issue was resolved. Has there been any issue since #363?

@NebulaBC
Copy link
Author

Nope, after pulling and restarting my container I’m still getting the same error when I try to run this script.

TacticalTechJay added a commit to TacticalTechJay/zipline that referenced this issue Apr 25, 2023

Verified

This commit was signed with the committer’s verified signature. The key has expired.
diced pushed a commit that referenced this issue Apr 29, 2023

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
* @diced forgor

* check if proper id

* fix(?): await datasource's get

* fix (#350): Return size 0 for not found
@diced diced reopened this Apr 29, 2023
@diced
Copy link
Owner

diced commented Apr 29, 2023

Reopened, until we see a response from @NebulaBC - hope the fix works!

@TacticalTechJay
Copy link
Collaborator

@NebulaBC, has the following commit (3ff2153) fixed your issue?

@NebulaBC
Copy link
Author

This problem is solved, thanks. Sorry for the delay, Github is not my primary git platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants