-
-
Notifications
You must be signed in to change notification settings - Fork 355
No objects after restart of fakes3 #22
Comments
I needed to patch fake-s3 to handle a case that led to same exact behavior: May or may not be your problem though.
On Jan 5, 2013, at 1:25 PM, Markus Korn notifications@github.com wrote:
|
I'm seeing the exact same problem using the AWS-S3 ruby gem. Everything works great, but after server restart I get "AWS::S3::NoSuchKey ". Checking the fakes3 folder, the files are there. The proposed patch is not working. Any ideas on what could cause this?
|
I worked around this locally with the following changes in lib/fakes3/file_store.rb:
|
I just had the same problem - objects are no longer listed after restarting the server, although I can still GET them. I applied the fix from dterhorst and it worked. This would be a good pull request. |
I had to use a combination of fixes here to get it working in my fork: |
I'm using HEAD of fakes3, and whenever I restart the fakes3 server lookinng up keys is not working anymore, I always get an empty list of objects for each bucket.
The text was updated successfully, but these errors were encountered: