fix(reaper): forkExec error no such file or directory & prometheus exit error
- fix https://github.com/aptible/supercronic/issues/177
- run reaper test in docker container
- use bats-action to install bats-core and bats-assert ...
- fix https://github.com/aptible/supercronic/issues/173
@UserNotFound Is there anything I can do? There's no progress.
Can you add a test for this case?
Also, i'm not sure if it would be related, but there's another issue listed related to this feature, if you could patch that here in this PR is would streamline review and release. https://github.com/aptible/supercronic/issues/173
@UserNotFound
I added the test and ran the reaper test in Docker The bats-core action needs to be trusted bats-core/[email protected] is not allowed to be used in aptible/supercronic.
The Prometheus error may not be related; the old version has the same error. https://github.com/aptible/supercronic/releases/download/v0.2.30/supercronic-linux-amd64
@UserNotFound i fixed prometheus http server closed error
@UserNotFound Is there anything I can do? There's no progress.
@UserNotFound Is there anything I can do? There's no progress.
@UserNotFound Is there anything I can do? There's no progress.
This review is being prioritized within our team, but I don't have any information at the moment as to when that will occur.
I have the same issue, is there a plan to merge it?
Use the full path of Supercronic (e.g., /usr/bin/supercronic) for now, until the fix PR is merged
@eabruzzese @almathew ping
@qianlongzt i forked this repo and created my own release with your PR and bumped dependencies from this recently merged PR #192
if you want to check it out here it is:
https://github.com/CoreProc/supercronic/releases/tag/0.2.35
@eloisejones @eabruzzese sorry to pester, but this PR has been waiting for review for 11 months and could really use your approval + release. (I spent 20+ minutes today chasing down the Failed to fork exec error that this fixes.) Thank you in advance!
Fixed in v0.2.36