Closed egguy closed 1 year ago
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@egguy Sorry for the delay in this, it's been a pretty hectic time. Nice idea, see comment on the review, i'd love to implement this
I've updated the pull with your recommendations.
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed after being inactive for 30 days. If you require further assistance please reopen the issue with more details or talk to us on discord
Hello @VibroAxe, I hope it's not tool late, could I request a review, or there are some remaining changes to do ?
Hey, certainly. Apologies but code review has taken a bit of a back seat. I'll take a look
No worries, It was my bad too, I was too late to react to prevent closure from the bot.
Thx for taking time and maintaining this project
PS: Is it possible to also take a look ad #147 to allow the test to work again ?
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed after being inactive for 30 days. If you require further assistance please reopen the issue with more details or talk to us on discord
@VibroAxe is there a reason why Pull Requests keep getting auto-closed by the bot? I see how there could be a valid reason for issues, but IMO PRs can just stay open until a developer/maintainer decides it doesn't make sense to pursue them further. Autoclosing them because "hurr durr it's inactive" even though what's missing can't even be delivered by the author of the PR is a bit irritating.
Fair comment. I'll see if I can stop the bot idling out on PRs
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
bump
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Any progress on not idling out on PRs? :p
This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed after being inactive for 30 days. If you require further assistance please reopen the issue with more details or talk to us on discord
Can this be reopened?
Allow to detect it there's problem with the nginx process and restart it. Use the
/lancache-heartbeat
URL to check.Based on: https://scoutapm.com/blog/how-to-use-docker-healthcheck