-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Setting runOnDemandStartTimeout or runOnDemandCloseAfter for a path causes segfault/panic in v1.2.0 #2529
Comments
Thanks for reporting the issue, this is fixed by #2529 |
added in v1.2.1 |
@aler9 Is there a replacement for the deprecated settings? I'm still getting some panics related to onDemand:
|
@mrlt8 open another issue and provide details on how to replicate the new, unrelated crash. |
This issue is being locked automatically because it has been closed for more than 6 months. |
Which version are you using?
v1.2.0
Which operating system are you using?
Describe the issue
Setting runOnDemandStartTimeout and/or runOnDemandCloseAfter for a specific path causes a segfault/panic. This issue started with v1.2.0 and was not an issue with v1.1.1.
Describe how to replicate the issue
Did you attach the server logs?
yes
Did you attach a network dump?
no
The text was updated successfully, but these errors were encountered: