Merged
Conversation
make the lease maintenance crawler run often and renew aggressively that way it might actually see some use on the staging grid as a result, if it has problems, they are more likely to surface there
Collaborator
Author
|
I did a self-review on this, fixed the |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #8
I successfully manually tested this against GridSync 9ea708351591aad74ecc705fc919d9a3e3cdea8d and ZKAPAuthorizer 41446070c99adf0092d619e6ba09ca76d0454ce1 (which is the first revision that cares to load any of this configuration). I tested as far as being able to connect to the staging grid. I could not upload any files because the ZKAPAuthorizer on the staging grid disagrees with 9ea708351591aad74ecc705fc919d9a3e3cdea8d about pricing of mutables in a way that prevents directories from being created. However, I could verify that the new ZKAPAuthorizer configuration values were loaded by the plugin.