[GH-ISSUE #1632] 1.49.1 gives me "Invalid Date" error in ruby google cloud storage implementation #206

New issue

Closed

opened 2026-03-03 12:09:09 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 12:09:09 +03:00

Owner

Originally created by @AlvesJorge on GitHub (Jun 9, 2024).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/1632

Sorry don't have the time to provide a working reproducible example.

I tested 1.48, and 1.49.0 and I can confirm this only happens in 1.49.1

My implementation is a simple set client -> set bucket > bucket.upload(bytes, path), and somehow I get an error saying "Invalid Date", where clearly I'm not setting anything date related in my upload arguments.

Originally created by @AlvesJorge on GitHub (Jun 9, 2024). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/1632 Sorry don't have the time to provide a working reproducible example. I tested 1.48, and 1.49.0 and I can confirm this only happens in 1.49.1 My implementation is a simple set client -> set bucket > `bucket.upload(bytes, path)`, and somehow I get an error saying "Invalid Date", where clearly I'm not setting anything date related in my upload arguments.

kerem

2026-03-03 12:09:09 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-03 12:09:10 +03:00

Author

Owner

@AlvesJorge commented on GitHub (Jun 9, 2024):

Of course, just so anyone else is getting this error, just specify 1.49.0 as your desired version

@AlvesJorge commented on GitHub (Jun 9, 2024): Of course, just so anyone else is getting this error, just specify 1.49.0 as your desired version

kerem commented

2026-03-03 12:09:10 +03:00

Author

Owner

@AlvesJorge commented on GitHub (Jun 9, 2024):

Might be this change

@AlvesJorge commented on GitHub (Jun 9, 2024): [Might be this change ](https://github.com/fsouza/fake-gcs-server/pull/1619/files#r1632356947)

kerem commented

2026-03-03 12:09:11 +03:00

Author

Owner

@fsouza commented on GitHub (Jun 10, 2024):

Thanks for reporting and sorry for the breakage. I just published 1.49.2. Can you confirm that this issue is fixed in that release?

@fsouza commented on GitHub (Jun 10, 2024): Thanks for reporting and sorry for the breakage. I just published 1.49.2. Can you confirm that this issue is fixed in that release?

kerem commented

2026-03-03 12:09:11 +03:00

Author

Owner

@AlvesJorge commented on GitHub (Jun 10, 2024):

Yes, it is indeed working normally!
No worries with the bug, this project is very useful and I'm very grateful for it, keep up the great work! 😄

@AlvesJorge commented on GitHub (Jun 10, 2024): Yes, it is indeed working normally! No worries with the bug, this project is very useful and I'm very grateful for it, keep up the great work! 😄

kerem referenced this issue

2026-03-15 17:57:00 +03:00

[GH-ISSUE #206] "prefixes" key is always in the response of Object:list even if it's empty. #2185