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
Between release 1.37.10 and 1.44.2 there appears to have been a change in behavior of the Storage.get() method when used on empty objects whose name ends in "/". The new behavior is that Storage.get() returns zero when used on a BlobId representing such an empty "directory" (i.e. an object with a trailing slash in their name) objects. Interestingly, the current version still returns a non-zero response from Storage.get() when used on empty objects whose name does not end in a slash. Older versions like 1.37.10 as well as the "real" GCS return a non-zero response for empty objects regardless of their name (i.e. wether it ends in a trailing slash or not).
Expected behavior: fake-gcs-server behaves the same for empty objects, regardless of whether their name ends in a trailing slash or not.
The text was updated successfully, but these errors were encountered:
Between release 1.37.10 and 1.44.2 there appears to have been a change in behavior of the Storage.get() method when used on empty objects whose name ends in "/". The new behavior is that Storage.get() returns
zero
when used on a BlobId representing such an empty "directory" (i.e. an object with a trailing slash in their name) objects. Interestingly, the current version still returns a non-zero response from Storage.get() when used on empty objects whose name does not end in a slash. Older versions like 1.37.10 as well as the "real" GCS return a non-zero response for empty objects regardless of their name (i.e. wether it ends in a trailing slash or not).Expected behavior: fake-gcs-server behaves the same for empty objects, regardless of whether their name ends in a trailing slash or not.
The text was updated successfully, but these errors were encountered: