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

feat: schema 5.3.0 gene bumps #1286

Merged
merged 9 commits into from
Mar 10, 2025
Merged

feat: schema 5.3.0 gene bumps #1286

merged 9 commits into from
Mar 10, 2025

Conversation

ejmolinelli
Copy link
Contributor

Reason for Change

Update (a) gene info files and (b) COG version to comply with cxg schema 5.3.0.

Changes

  • update COG version in requirements
  • update to gene info.

Testing

  • Reminder For CLI changes: upon merge, contact Lattice for final sign-off. Do not release a new cellxgene-schema
    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
pip install git+https://github.com/chanzuckerberg/single-cell-curation/@main#subdirectory=cellxgene_schema_cli

Notes for Reviewer

Copy link

codecov bot commented Mar 6, 2025

Codecov Report

Attention: Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.

Project coverage is 89.29%. Comparing base (cde8485) to head (aa788de).
Report is 1 commits behind head on main.

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     
Components Coverage Δ
cellxgene_schema_cli 89.93% <ø> (-0.06%) ⬇️
migration_assistant 91.26% <ø> (ø)
schema_bump_dry_run_genes 79.74% <0.00%> (ø)
schema_bump_dry_run_ontologies 99.53% <ø> (ø)
🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ejmolinelli ejmolinelli force-pushed the ejmolinelli/5.3.0 branch 2 times, most recently from 603ba15 to 0612226 Compare March 7, 2025 13:49
run_reporter.public_errored_datasets += 1
logger.error(
f"Error processing public dataset {dataset['dataset_id']}, in collection {dataset['collection_id']}: "
f"{e}"
Copy link
Contributor

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")
Copy link
Contributor

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

Copy link
Contributor Author

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.

Copy link
Contributor

@joyceyan joyceyan left a 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

@ejmolinelli ejmolinelli merged commit 44947f4 into main Mar 10, 2025
12 of 16 checks passed
@ejmolinelli ejmolinelli deleted the ejmolinelli/5.3.0 branch March 10, 2025 18:19
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.

2 participants