Feature: Reload configuration upon receiving SIGHUP
asn-d6 opened this issue · 12 comments
Identical to DonnchaC/onionbalance#24
Patches welcome.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 200.0 DAI (200.0 USD @ $1.0/DAI) attached to it.
- If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
- Want to chip in? Add your own contribution here.
- Questions? Checkout Gitcoin Help or the Gitcoin Slack
- $126,487.08 more funded OSS Work available on the Gitcoin Issue Explorer
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work has been started.
These users each claimed they can complete the work by 1 week from now.
Please review their action plans below:
1) touhonoob has started work.
reload configuration on SIGHUP
Learn more on the Gitcoin Issue Details page.
Does v2 need to be supported as well?
Does v2 need to be supported as well?
Nope.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work for 200.0 DAI (200.0 USD @ $1.0/DAI) has been submitted by:
@ceresstation please take a look at the submitted work:
- PR by @touhonoob
- Learn more on the Gitcoin Issue Details page
- Want to chip in? Add your own contribution here.
- Questions? Checkout Gitcoin Help or the Gitcoin Chat
- $178,131.88 more funded OSS Work available on the Gitcoin Issue Explorer
Hello, this looks really good! Great work!
I left a comment that should be easy to fix.
Also, can you think of any unittests that would help with coverage here? Either checking that the config exceptions are thrown correctly, or that the SIGHUP handler works as expected?
Thanks! :)
Hello. Thanks for your work. As a final thing before we wrap this up, is it possible for you to disable the functional unittests in CI/tox so that they stop breaking Travis? Since they are unstable I guess we should disable them for now until we fix them. As a matter of fact, I thought they were disabled, but I see this PR failing on the functional tests so I'm not sure if I had actually disabled them.
@asn-d6 Yes, functional tests were disabled on Travis-CI as the $TEST environment variable was never set. The CI/testing stuff indeed deserves its own pull request I think.
ACK. But then why did PR#31 fail initially if the TEST envvar was not set? Also, I see that your last commit (3005dab) enabled the TEST envvar, so perhaps we should disable it again?
@asn-d6 functional tests disabled via the latest commit https://travis-ci.org/github/asn-d6/onionbalance/builds/703140184
Merged! Thanks a lot!! :)
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
The funding of 200.0 DAI (200.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @touhonoob.
- Learn more on the Gitcoin Issue Details page
- Questions? Checkout Gitcoin Help or the Gitcoin Chat
- $252,741.37 more funded OSS Work available on the Gitcoin Issue Explorer