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

carry forward flags in a seperate task #65

Merged
merged 3 commits into from
Aug 31, 2023
Merged

Conversation

dana-yaish
Copy link
Contributor

move carry forwarding to a new seperate task that will get called when creating a new db report instance

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. In 2022 this entity acquired Codecov and as result Sentry is going to need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

@codecov
Copy link

codecov bot commented Aug 16, 2023

Codecov Report

Merging #65 (4941ed0) into main (36b9432) will decrease coverage by 0.05%.
The diff coverage is 89.78%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main      #65      +/-   ##
==========================================
- Coverage   98.51%   98.47%   -0.05%     
==========================================
  Files         359      361       +2     
  Lines       26339    26476     +137     
==========================================
+ Hits        25949    26072     +123     
- Misses        390      404      +14     
Flag Coverage Δ
integration 98.44% <89.70%> (-0.05%) ⬇️
latest-uploader-overall 98.44% <89.70%> (-0.05%) ⬇️
onlysomelabels 98.47% <89.78%> (-0.05%) ⬇️
unit 98.44% <89.70%> (-0.05%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
NonTestCode 97.13% <80.28%> (-0.12%) ⬇️
OutsideTasks 98.23% <ø> (ø)
Files Changed Coverage Δ
tasks/preprocess_upload.py 80.00% <80.00%> (ø)
tasks/__init__.py 100.00% <100.00%> (ø)
tasks/tests/unit/test_preprocess_upload.py 100.00% <100.00%> (ø)

This change has been scanned for critical changes. Learn more

@dana-yaish dana-yaish marked this pull request as ready for review August 29, 2023 18:18
@dana-yaish
Copy link
Contributor Author

we probably should push this to staging first

Copy link
Contributor

@giovanni-guidini giovanni-guidini left a comment

Choose a reason for hiding this comment

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

LGTM
I think we can take care of "let's push this to staging first" on the task trigger side and not in the worker exactly

@dana-yaish dana-yaish merged commit 8012c86 into main Aug 31, 2023
9 of 12 checks passed
@dana-yaish dana-yaish deleted the dana/pre-process-upload branch August 31, 2023 08:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Pre-processing upload task that carries forward previous labels and flags
2 participants