Skip to content

Conversation

@d-chambers
Copy link
Contributor

@d-chambers d-chambers commented Feb 28, 2025

Description

This PR fixes an issue in the Febus data format which causes dascore to identify empty hdf5 files as febus format.

Checklist

I have (if applicable):

  • referenced the GitHub issue this PR closes.
  • documented the new feature with docstrings or appropriate doc page.
  • included a test. See testing guidelines.
  • your name has been added to the contributors page (docs/contributors.md).
  • added the "ready_for_review" tag once the PR is ready to be reviewed.

Summary by CodeRabbit

  • Bug Fixes
    • Refined version display logic to ensure version information is only presented when complete instrument details are available.
  • Tests
    • Expanded test coverage by adding scenarios that verify proper error handling when processing empty input files.

@d-chambers d-chambers added bug Something isn't working IO Work for reading/writing different formats labels Feb 28, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 28, 2025

Walkthrough

This pull request updates the Febus version string retrieval logic and expands the test suite. In the Febus utility, the conditional check now requires both a valid Febus flag and non-empty instrument keys before returning a version string. Meanwhile, new tests were introduced that create an empty HDF5 file fixture and verify that calling the format retrieval function on such a file raises an appropriate error.

Changes

File Summary
dascore/.../utils.py Modified _get_febus_version_str to require non-empty inst_keys along with is_febus before returning the version string.
tests/.../test_io_core.py Added a new pytest fixture empty_h5_path to create an empty HDF5 file and a test test_empty_hdf5_no_format to assert error raising on it.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant VersionFunc as _get_febus_version_str
    Caller->>VersionFunc: Call with (inst_keys, is_febus)
    alt inst_keys is non-empty and is_febus is true
        VersionFunc-->>Caller: Return version string
    else Condition not met
        VersionFunc-->>Caller: No version string returned
    end
Loading
sequenceDiagram
    participant Test
    participant FileFixture as empty_h5_path
    participant DC as dc.get_format
    Test->>FileFixture: Create an empty HDF5 file
    Test->>DC: Call get_format(empty HDF5 file)
    DC-->>Test: Raise UnknownFiberFormatError
Loading

Poem

Hi, I'm a happy rabbit on the run,
Hopping through fixes just for fun.
Now our Febus check needs more than a glance,
And empty files get met with a testy chance.
Code carrots abound—let’s celebrate each one!
🥕🐇


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1dbb10e and 6648cc5.

📒 Files selected for processing (2)
  • dascore/io/febus/utils.py (1 hunks)
  • tests/test_io/test_io_core.py (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (15)
  • GitHub Check: test_code (windows-latest, 3.12)
  • GitHub Check: test_code (ubuntu-latest, 3.10)
  • GitHub Check: test_code (ubuntu-latest, 3.12)
  • GitHub Check: test_code (macos-latest, 3.12)
  • GitHub Check: test_code (windows-latest, 3.11)
  • GitHub Check: test_code (ubuntu-latest, 3.11)
  • GitHub Check: test_code (macos-latest, 3.11)
  • GitHub Check: test_code (windows-latest, 3.10)
  • GitHub Check: test_code (macos-latest, 3.10)
  • GitHub Check: test_code_min_deps (macos-latest, 3.13)
  • GitHub Check: test_code_min_deps (ubuntu-latest, 3.12)
  • GitHub Check: test_code_min_deps (windows-latest, 3.13)
  • GitHub Check: test_code_min_deps (macos-latest, 3.12)
  • GitHub Check: test_code_min_deps (windows-latest, 3.12)
  • GitHub Check: test_code_min_deps (ubuntu-latest, 3.13)
🔇 Additional comments (4)
dascore/io/febus/utils.py (1)

78-78: Good fix for the empty file detection.

This change ensures that empty HDF5 files aren't incorrectly identified as Febus format files by checking that inst_keys is not empty before determining a file is in Febus format. This addresses the PR's main objective.

tests/test_io/test_io_core.py (3)

10-10: Added necessary import for the new test fixture.

The h5py import is required for creating the empty HDF5 test file.


264-271: Well-designed test fixture for creating empty HDF5 files.

This fixture creates an empty HDF5 file that will be used to verify the fix for the Febus format detection issue. The class scope is appropriate as the file can be reused across tests.


291-295: Effective test case that verifies the fix.

This test ensures that the empty HDF5 file correctly raises an UnknownFiberFormatError instead of being incorrectly identified as a Febus format file, which directly addresses the issue described in the PR objective.

✨ Finishing Touches
  • 📝 Generate Docstrings

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov
Copy link

codecov bot commented Feb 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.85%. Comparing base (1dbb10e) to head (6648cc5).
Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #492   +/-   ##
=======================================
  Coverage   99.85%   99.85%           
=======================================
  Files         118      118           
  Lines        9696     9696           
=======================================
  Hits         9682     9682           
  Misses         14       14           
Flag Coverage Δ
unittests 99.85% <100.00%> (ø)

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@d-chambers d-chambers merged commit 045cbbb into master Feb 28, 2025
19 checks passed
@d-chambers d-chambers deleted the fix_febus_format_empty_file branch February 28, 2025 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working IO Work for reading/writing different formats

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants