-
Notifications
You must be signed in to change notification settings - Fork 177
Mv bucket expiry2 #235
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
Mv bucket expiry2 #235
Conversation
Looks good! 👍✅ MERGE
|
…id from ERL_NIF_TERM
… io:format() calls, create catch-all
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
Looks good! 👍✅ MERGE
|
…of onload() parameters.
Looks good! 👍✅ MERGE
|
…lbacks (there is another one on the horizon
There seems to be an issue with build step **merge** ! ☁️⛔ MERGE
|
…ead of direct member variables.
There seems to be an issue with build step **merge** ! ☁️⛔ MERGE
|
…ache get written to cache correctly.
There seems to be an issue with build step **merge** ! ☁️⛔ MERGE
|
|
(I thought @tburghart was reviewing this one, but the riak team said this morning that I should look at it too, so I'm adding a few notes here, despite not being sure whether this is ready for review, etc)
|
There seems to be an issue with build step **merge** ! ☁️⛔ MERGE
|
|
Good questions Erik.
|
|
Ideally I think we'd allow eleveldb to report two categories of errors: permanent and transient. Future enhancement to the info service, perhaps. |
|
Added locking around ServiceCallback accessors per code review. |
…f blanket ok, per John D.
There seems to be an issue with build step **merge** ! ☁️⛔ MERGE
|
There seems to be an issue with build step **merge** ! ☁️⛔ MERGE
|
erikleitch
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops - I think the spec for eleveldb:property_cache/2 is now wrong (eleveldb::property_cache changed to return ok, or {error, any()}, but spec still reads: -spec property_cache(string(), string()) -> ok.)
|
Wrong, maybe. In flux, absolutely. Waiting on API lock down. |
There seems to be an issue with build step **merge** ! ☁️⛔ MERGE
|
|
This was a horrible merge. Done by hand directly to develop. |
No description provided.