[GitHub] couchdb-couch-replicator issue #48: Port HTTP 429 Commits

2016-10-03 Thread tonysun83
Github user tonysun83 commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/48 @kxepal: made every macro configurable --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have

[GitHub] couchdb-couch-replicator issue #48: Port HTTP 429 Commits

2016-10-04 Thread nickva
Github user nickva commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/48 +1 (after rebase + lower case the config constants). I tested with a rate limited account. Changes replicated and made progress. I lowered the max backoff value to see how er

[GitHub] couchdb-couch-replicator issue #48: Port HTTP 429 Commits

2016-10-04 Thread tonysun83
Github user tonysun83 commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/48 @nickva : thx for the review. rebased and lowered cased the names. do the builds fail sometimes for CI? Log shows ``` in function couch_changes_tests:'-should_select_with_c

[GitHub] couchdb-couch-replicator issue #48: Port HTTP 429 Commits

2016-10-05 Thread nickva
Github user nickva commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/48 @tonysun83 I think that is a flaky test, will try it locally see what it does --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub a

[GitHub] couchdb-couch-replicator issue #48: Port HTTP 429 Commits

2016-10-05 Thread nickva
Github user nickva commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/48 @tonysun83 looks like it is flaky and it is in the couch repo anyway, not even in replicator, so go ahead and merge if you want --- If your project is set up for it, you can reply to