Currently keploy would wait till delay (5s) as provided using delay flag for user application to start , but it is required only for native env and for docker related application we have to have till the application starts or buildDelay time is completed. This pr fix this bug by adding a channel to signal the start of application or cancel the service if buildDelay is reached. Also the PR fixes the panic in keploy during an error by adding an err channel on the required goroutine which became unreachable due to the error.
Type of change
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
Please let us know if any test cases are added
Please describe the tests(if any). Provide instructions how its affecting the coverage.
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Checklist:
[ ] My code follows the style guidelines of this project.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
Related Issue
Closes: #1810 Closes: #1795
Describe the changes you've made
Currently keploy would wait till delay (5s) as provided using delay flag for user application to start , but it is required only for native env and for docker related application we have to have till the application starts or buildDelay time is completed. This pr fix this bug by adding a channel to signal the start of application or cancel the service if buildDelay is reached. Also the PR fixes the panic in keploy during an error by adding an err channel on the required goroutine which became unreachable due to the error.
Type of change
Please let us know if any test cases are added
Please describe the tests(if any). Provide instructions how its affecting the coverage.
Describe if there is any unusual behaviour of your code(Write
NAif there isn't)A clear and concise description of it.
Checklist:
Screenshots (if any)