Skip to content

Conversation

@russelldb
Copy link

js_driver:eval_js/2 uses a macro SCRIPT_TIMEOUT for the amount of
time to wait for a js script to execute before timing out. In some
instances (testing JS map reduce on limited hardware) it would be
handy to set this timeout higher.

Use the 'erlang_js' app_env var 'script_timeout' and any int value.
Timeout is in milliseconds.

js_driver:eval_js/2 uses a macro SCRIPT_TIMEOUT for the amount of
time to wait for a js script to execute before timing out. In some
instances (testing JS map reduce on limited hardware) it would be
handy to set this timeout higher.

Use the 'erlang_js' app_env var 'script_timeout' and any int value.
Timeout is in milliseconds.
@joedevivo
Copy link

+1 this worked great in riak 1.2.1 with riak_test, but I did have to rebase before rebar would allow the dependency to work.

@strange
Copy link

strange commented Jan 28, 2013

Our use application:get_env/2? A little messier, but nice to get rid of the dep.

@cmeiklejohn
Copy link
Contributor

app_helper is only going to work when bundled with riak/riak_core. Should this be modified to use application:get_env as recommended above?

@cmeiklejohn
Copy link
Contributor

Closing in favor of #41.

@seancribbs seancribbs deleted the rdb-js-timeout branch April 1, 2015 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants