- 02 Mar, 2021 2 commits
-
-
acruikshank authored
-
acruikshank authored
-
- 28 Apr, 2020 3 commits
-
-
Steven Allen authored
-
Steven Allen authored
Co-Authored-By:Will <will.scott@protocol.ai>
-
Steven Allen authored
1. Don't log an error when shutting down while reproviding. 2. Reprovide on a fixed interval instead of treating the interval as a delay. 3. Remove trigger muting logic and use the simpler way. 4. Add some tests for triggering. 5. Make sure Reprovider.Close actually, you know, does something. And waits for the reprovider to stop.
-
- 06 Dec, 2019 1 commit
-
-
Michael Muré authored
-
- 17 Oct, 2019 1 commit
-
-
Michael Muré authored
-
- 02 Oct, 2019 1 commit
-
-
Michael Muré authored
If an error bubble up here, the Reprovider is effectively disabled. Error level is justified IMHO.
-
- 25 Jul, 2019 1 commit
-
-
Michael Muré authored
-
- 12 Jul, 2019 1 commit
-
-
Steven Allen authored
And improve the tests.
-
- 11 Jul, 2019 1 commit
-
-
Steven Allen authored
-
- 10 Jun, 2019 1 commit
-
-
Michael Avila authored
-
- 06 Jun, 2019 1 commit
-
-
Michael Avila authored
-
- 01 Jun, 2019 1 commit
-
-
Raúl Kripalani authored
closes #6391 License: MIT Signed-off-by:Raúl Kripalani <raul@protocol.ai>
-
- 29 May, 2019 1 commit
-
-
Michael Avila authored
License: MIT Signed-off-by:Michael Avila <davidmichaelavila@gmail.com>
-
