Skip to content
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

chore: improve regulation-worker status capture #2837

Merged
merged 2 commits into from
Feb 27, 2023

Conversation

saurav-malani
Copy link
Contributor

@saurav-malani saurav-malani commented Dec 29, 2022

Description

Currently, when regulation-worker responds to regulation-manager, it doesn't return the reason in case of failure or aborted. And, as it could be helpful in debugging and in various other cases. This PR modifies response body to return the reason too.

Notion Ticket

https://www.notion.so/rudderstacks/improve-regulation-worker-status-capture-f1e82e5fe8e64ec1b88fc7df29e9325e

@saurav-malani saurav-malani changed the base branch from master to feat.MTSupportRegWorker December 29, 2022 11:56
@codecov
Copy link

codecov bot commented Dec 29, 2022

Codecov Report

Base: 52.97% // Head: 52.99% // Increases project coverage by +0.01% 🎉

Coverage data is based on head (61cba86) compared to base (ed83eaa).
Patch coverage: 51.21% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2837      +/-   ##
==========================================
+ Coverage   52.97%   52.99%   +0.01%     
==========================================
  Files         334      334              
  Lines       51863    51858       -5     
==========================================
+ Hits        27475    27482       +7     
+ Misses      22785    22776       -9     
+ Partials     1603     1600       -3     
Impacted Files Coverage Δ
regulation-worker/internal/delete/api/mock_api.go 0.00% <0.00%> (ø)
regulation-worker/internal/delete/batch/batch.go 50.56% <10.00%> (ø)
regulation-worker/internal/delete/api/api.go 65.30% <36.36%> (-1.58%) ⬇️
...gulation-worker/internal/delete/kvstore/kvstore.go 85.18% <50.00%> (ø)
regulation-worker/internal/service/service.go 74.07% <81.81%> (ø)
regulation-worker/internal/client/client.go 71.53% <100.00%> (+0.44%) ⬆️
regulation-worker/internal/delete/delete.go 100.00% <100.00%> (ø)
processor/worker.go 82.81% <0.00%> (-2.35%) ⬇️
processor/processor.go 87.35% <0.00%> (+0.15%) ⬆️
router/router.go 77.86% <0.00%> (+0.19%) ⬆️
... and 2 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

Base automatically changed from feat.MTSupportRegWorker to master January 6, 2023 10:10
@github-actions github-actions bot added the Stale label Jan 27, 2023
@github-actions github-actions bot closed this Feb 3, 2023
@saurav-malani saurav-malani reopened this Feb 21, 2023
@rudderlabs rudderlabs deleted a comment from github-actions bot Feb 23, 2023
Copy link
Contributor

@atzoum atzoum left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

expectedDeleteStatus: model.JobStatusComplete,
expectedPayload: `[{"jobId":"1","destType":"ga","config":{"rudderDeleteAccountId":"xyz"},"userAttributes":[{"email":"dorowane8n285680461479465450293437@gmail.com","phone":"6463633841","randomKey":"randomValue","userId":"Jermaine1473336609491897794707338"},{"email":"dshirilad853601942465969121327991@gmail.com","userId":"Mercie8221821544021583104106123"},{"phone":"8782905113","userId":"Claiborn443446989226249191822329"}]}]`,
},
// {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why those tests are commented out?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, that is mistake. I was debugging something and forgot to uncomment them back. Thanks for pointing it out. Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants