forked from basho/riak_kv
-
Notifications
You must be signed in to change notification settings - Fork 1
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
WIP Tiot/openriak 3.4/tictacaae and nextgenrepl cli commands #55
Open
hmmr
wants to merge
18
commits into
OpenRiak:openriak-3.4
Choose a base branch
from
TI-Tokyo:tiot/openriak-3.4/tictacaae-and-nextgenrepl-cli-commands
base: openriak-3.4
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
fa26da7
set/print tictacaae_* settings via riak admin
hmmr 2647b26
aae_schedule_nextrebuild
hmmr 19553b5
getters of various vnode state fields needed for `riak admin aae-prog…
hmmr 1b3b260
riak admin treestatus (aka aae-progress-report)
hmmr be49b51
correct kv_index_tictactree tag
hmmr 96231e4
use getopt facilities for parsing tictacaae_cmd options
hmmr abdf158
final kv_index_tictactree tag
hmmr 773440f
update meck version (#22)
hmmr a27da00
Proposal 10: TicTac AAE and NextGenRepl CLI commands, part 1/n
hmmr 400247a
delete stray debugging aids
671950c
set/show af1, af4, be worker pool sizes
f838376
validate args; accept "0xfafa"-style binaries
d0f7fe5
access object_splitfun field in aae_controller state directly
9921ba9
temp switch deps to tiot branches
a0c616a
tweaks to strings
7533730
more tweaks to strings
86b0a35
wip, much perplexion and stupefication
b68a6bd
open and close outfile in the spawned process
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Cloning your own version of meck seems to me the wrong way to go
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.
This is consistent with our approach everywhere, which is to clone all repos we depend on - only we didn't do it previously for test.
If we just get
meck
latest, as was - we're subject to time-expensive surprises when all our deps can no longer update. If we tag to a version, then we still need to check upstream for critical updates.There's no perfect solution, so I'm happy that in this case we should resolve with the same solution used for non-test dependencies.