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
basho-patches #994
Comments
Currently riak develop-3.0 does not support basho-patches in the code path. Bodge this so we can still add and save a patch (maybe - or perhaps just adding the path this way won't have the intercept survive the reboot?). basho/riak#994
@martinsumner it's a side effect of moving away from the runner in node_package. It's on my todo. |
Sorry, what's the official stance on this? I find code in 3.0.1 referring to |
Some riak_test tests (e.g. ensemble_remove_node - https://github.com/basho/riak_test/blob/develop-2.9/tests/ensemble_basic2.erl) require a patch that survives restart using
rt_intercept:add_and_save/2
.This add and save uses the basho_patches folder, which is required to be in the code path of the node. However this is no longer in the code path in
develop-3.0
.The mkdir command in
rebar.config
riak/rebar.config
Line 76 in 8a257ee
make devrel
, it will not add the path to the code_path (i.e. if you start a node and then call code_get_path() fromriak remote_console
it is not included).Is this a relx issue?
@martincox might you be able to take a look?
The text was updated successfully, but these errors were encountered: