-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reload started twice can generate panic #2656
Conversation
…art function of the Instance
Thank you for your contribution. I've just checked the OWNERS files to find a suitable reviewer. This search was successful and I've asked varyoo (via If you have questions or suggestions for this bot, please file an issue against the miekg/dreck repository. The bot understands the commands that are listed here. |
I could reproduce locally the bug mentionned.
console output:
|
With the fix, i can observe the behavior os back to normal.
It will need an Integration Test to be permanently validated on PRs. |
Codecov Report
@@ Coverage Diff @@
## master #2656 +/- ##
==========================================
+ Coverage 55.93% 55.95% +0.02%
==========================================
Files 194 194
Lines 9962 9961 -1
==========================================
+ Hits 5572 5574 +2
+ Misses 3979 3977 -2
+ Partials 411 410 -1
Continue to review full report at Codecov.
|
Please add a test
…On Wed, 6 Mar 2019, 00:52 Francois Tur, ***@***.***> wrote:
…art function of the Instance
1. Why is this pull request needed and what does it do?
Fix problem of reload kicked-off twice.
Since last release of Caddy, the event InstanceStartupEvent is triggered
directly by Caddy when starting the Instance. CoreDNS MUST not trigger that
event again.
2. Which issues (if any) are related?
#2654 <#2654>
3. Which documentation changes (if any) need to be made?
None. It is fixing an bug.
4. Does this introduce a backward incompatible change or deprecation?
No.
------------------------------
You can view, comment on, or merge this pull request online at:
#2656
Commit Summary
- - remove caddy event, It is now triggered directly by Caddy in the
Start function of the Instance
File Changes
- *M* coremain/run.go
<https://github.com/coredns/coredns/pull/2656/files#diff-0> (3)
Patch Links:
- https://github.com/coredns/coredns/pull/2656.patch
- https://github.com/coredns/coredns/pull/2656.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2656>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAVkW23qDmSKzClVSllpjU0T3ORyvnMUks5vTxFQgaJpZM4bf0J2>
.
|
…art function of the Instance (coredns#2656)
…art function of the Instance (coredns#2656)
1. Why is this pull request needed and what does it do?
Fix problem of reload kicked-off twice.
Since last release of Caddy, the event
InstanceStartupEvent
is triggered directly by Caddy when starting the Instance. CoreDNS MUST not trigger that event again.2. Which issues (if any) are related?
#2654
3. Which documentation changes (if any) need to be made?
None. It is fixing an bug.
4. Does this introduce a backward incompatible change or deprecation?
No.