-
Notifications
You must be signed in to change notification settings - Fork 26
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
feat: schema 5.3.0 gene bumps #1286
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1286 +/- ##
==========================================
- Coverage 89.33% 89.29% -0.05%
==========================================
Files 21 21
Lines 2373 2373
==========================================
- Hits 2120 2119 -1
- Misses 253 254 +1
🚀 New features to boost your workflow:
|
603ba15
to
0612226
Compare
d7ec712
to
aa788de
Compare
run_reporter.public_errored_datasets += 1 | ||
logger.error( | ||
f"Error processing public dataset {dataset['dataset_id']}, in collection {dataset['collection_id']}: " | ||
f"{e}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is there any reason why we would not want to log the actual exception that occurred?
run_reporter.private_errored_datasets += 1 | ||
logger.error(f"Error processing private dataset: {e}") | ||
logger.error("Error processing private dataset") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i understand that we don't want to log stuff about private datasets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For expedience only. We have another issue to handle meaningful logs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good, i think we may want to add back some additional logging info for dataset failures (ex: just the dataset id seems fine?) but i'm ok with removing it for now to err on the side of being more private / secure
Reason for Change
Update (a) gene info files and (b) COG version to comply with cxg schema 5.3.0.
Changes
Testing
version to PyPI without explicit QA + sign-off from Lattice on all functional CLI changes. They may install the package
version at HEAD of main with
Notes for Reviewer