-
Notifications
You must be signed in to change notification settings - Fork 8
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
First version of progress reporting #100
base: main
Are you sure you want to change the base?
Conversation
After properly testing it locally I will need to figur out with other teams how should we report the progress - because playbook worker does it in some mysterious way through ansible and several events - AFAIK only remediations app uses it. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #100 +/- ##
==========================================
+ Coverage 64.20% 66.89% +2.69%
==========================================
Files 5 5
Lines 338 293 -45
==========================================
- Hits 217 196 -21
+ Misses 101 75 -26
- Partials 20 22 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
3b8a9f5
to
c331766
Compare
Signed-off-by: Andrea Waltlova <[email protected]>
Signed-off-by: Andrea Waltlova <[email protected]>
Signed-off-by: Andrea Waltlova <[email protected]>
Signed-off-by: Andrea Waltlova <[email protected]>
Signed-off-by: Andrea Waltlova <[email protected]>
Signed-off-by: Andrea Waltlova <[email protected]>
…n for that buffer for stdout flush python script stdout after every print to force 'progress' reporting Signed-off-by: Andrea Waltlova <[email protected]>
Signed-off-by: Andrea Waltlova <[email protected]>
Signed-off-by: Andrea Waltlova <[email protected]>
Signed-off-by: Andrea Waltlova <[email protected]>
b28987e
to
864af76
Compare
HMS-3622