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

404 error for nested folder #7267

Open
vijaysebastian opened this issue Feb 10, 2021 · 3 comments
Open

404 error for nested folder #7267

vijaysebastian opened this issue Feb 10, 2021 · 3 comments
Labels
type: question Request for information or clarification. Not an issue.

Comments

@vijaysebastian
Copy link

I have a bucket called turbocomply-new, and inside that i have 9b8d64bf-4108-48db-86ad-d7481cc08564 folder inside that i have 0f11f37c-4ca4-11eb-8c9c-88e9fe822525.png file.
my folder structure is
turbocomply-new -> 9b8d64bf-4108-48db-86ad-d7481cc08564 -> 0f11f37c-4ca4-11eb-8c9c-88e9fe822525.png

this is what I am using to the object
{:ok, body} = GoogleApi.Storage.V1.Api.Objects.storage_objects_get(gconn, "turbocomply-new", "9b8d64bf-4108-48db-86ad-d7481cc08564/0f11f37c-4ca4-11eb-8c9c-88e9fe822525.png",[{:alt, "media"}], decode: false)

but I'm getting
status: 404, url: "https://storage.googleapis.com/storage/v1/b/turbocomply-new/o/9b8d64bf-4108-48db-86ad-d7481cc08564/0f11f37c-4ca4-11eb-8c9c-88e9fe822525.png"

is there any way to get the object? I checked the object inside turbocomply-new bucket and it's working

@davidye
Copy link

davidye commented Feb 10, 2021

I'm also seeing this issue in 0.28.0 - but this works fine in 0.23.0 so seems like a bug.

@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Feb 11, 2021
@dazuma dazuma added type: question Request for information or clarification. Not an issue. and removed 🚨 This issue needs some love. triage me I really want to be triaged. labels Feb 19, 2021
@dazuma
Copy link
Member

dazuma commented Feb 19, 2021

It's possible this is related to #6352.

@antedeguemon
Copy link

Updating to 0.29 fixed the issue for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

5 participants