When saving an object with siblings Ripple saved the object with Content-Type
set to multipart/mixed
.
This has been fixed in v1.0.0beta2
by requiring Ripple documents to specify an
on_conflict
handler.
cd bad_content_type
bundle install
bundle exec ruby foo.rb
Accessing objects incorrectly created by Ripple results in an exception being raised related to an unimplemented serializer.
cd handling_bad_content_type
bundle install
bundle exec ruby scenario1.rb
Accessing objects incorrectly created by Ripple results in an exception being raised related to parsing a multipart message with a nil boundary.
cd handling_bad_content_type
bundle install
bundle exec ruby scenario2.rb
Hey @dreverri, thanks for putting this together!
Two questions/comments about this:
on_conflict
hook (it was extracted from our code base, actually) and I was curious to see the change you refer to here. I looked through the recent commit history of ripple and couldn't find anything like this. For reference, we've never used the 0.9.5 release of ripple in production; in fact we've been locked to my last ripple commit or newer for the last nine months (I updated our code base to that commit the day I added it to ripple, IIRC).on_conflict
handler for all documents that haveallow_mult = true
, so I don't see how this explains what happened. Silo's been properly resolving conflicted documents for 12+ months.