Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@tbkr
Copy link
Contributor

@tbkr tbkr commented Oct 20, 2025

Description

Fixing the open todos in the new codebase.

Contributor Declaration

By opening this pull request, I affirm the following:

  • All authors agree to the Contributor License Agreement.
  • The code follows the project's coding standards.
  • I have performed self-review and added comments where needed.
  • I have added or updated tests to verify that my changes are effective and functional.
  • I have run all existing tests and confirmed they pass.

🌈🌦️📖🚧 Documentation Z3FDB 🚧📖🌦️🌈
https://sites.ecmwf.int/docs/dev-section/z3fdb/pull-requests/PR-186

🌈🌦️📖🚧 Documentation FDB 🚧📖🌦️🌈
https://sites.ecmwf.int/docs/dev-section/fdb/pull-requests/PR-186

@codecov-commenter
Copy link

codecov-commenter commented Oct 20, 2025

Codecov Report

❌ Patch coverage is 73.58491% with 42 lines in your changes missing coverage. Please review.
✅ Project coverage is 74.57%. Comparing base (525720c) to head (1ce14bf).
⚠️ Report is 21 commits behind head on feature/zarr-fdb-interface.

Files with missing lines Patch % Lines
tests/chunked_data_view/test_builder.cc 72.50% 33 Missing ⚠️
src/chunked_data_view/ChunkedDataViewImpl.cc 75.00% 2 Missing ⚠️
src/chunked_data_view/GribExtractor.cc 0.00% 2 Missing ⚠️
src/chunked_data_view/ViewPart.cc 80.00% 2 Missing ⚠️
src/chunked_data_view/ChunkedDataViewBuilder.cc 93.75% 1 Missing ⚠️
src/chunked_data_view/Extractor.cc 0.00% 1 Missing ⚠️
src/chunked_data_view/Fdb.cc 0.00% 1 Missing ⚠️
Additional details and impacted files
@@                      Coverage Diff                       @@
##           feature/zarr-fdb-interface     #186      +/-   ##
==============================================================
+ Coverage                       74.53%   74.57%   +0.04%     
==============================================================
  Files                             358      359       +1     
  Lines                           20968    21070     +102     
  Branches                         2139     2150      +11     
==============================================================
+ Hits                            15628    15714      +86     
- Misses                           5340     5356      +16     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@tbkr tbkr force-pushed the feature/zarr-fdb-interface-todos branch from 4819cd0 to 303b6d2 Compare October 21, 2025 07:35
tbkr and others added 11 commits October 22, 2025 14:34
The extension axis is now only needed for a build with multiple parts.
For an single part it's simply ignored.
In case the keyword is already mapped by another axis or isn't mapped by
any axis, throw a eckit user error instead of std::runtime_error.
Noted the class where the exception occurred.
With the introduction of the writeInto method with he list_iterator
interface the former one is now obsolete.
This is really just an interface for the Mock or the FDB wrapper and
thus should be called accordingly.
@tbkr tbkr force-pushed the feature/zarr-fdb-interface-todos branch from 04d3d91 to 60ca37b Compare October 22, 2025 13:52
@tbkr tbkr force-pushed the feature/zarr-fdb-interface-todos branch from 60ca37b to 6145207 Compare October 22, 2025 13:54
@tbkr tbkr requested a review from Ozaq October 27, 2025 07:06
tbkr and others added 3 commits October 27, 2025 12:26
Added test cases for chunked and non-chunked permutations of axis, in the
MARS requests, as well as in the AxisDefinitons.

Added further comments to the test cases.
Comment on lines 47 to 49
if (viewParts.empty()) {
throw eckit::UserError("ChunkedDataViewBuilder: No view parts are given.");
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Pull up check into build

Comment on lines 106 to 107
// @info This is not checking whether the parameters are matching, in theory we could
// stitch mismatching parameters.
Copy link
Contributor

Choose a reason for hiding this comment

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

This comment is misleading, we do not care for the parameters, the only thing that needs to match is the field size / field data type. If we have Surface fields on one side and Pressure layer on the other we already stitch different parameters and that's intentional.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is exactly what the comment is aiming for the possibility of merging different 'cubes' . How is this misleading?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Rewrote the info.

@Ozaq Ozaq merged commit 7771ecd into feature/zarr-fdb-interface Oct 30, 2025
81 of 82 checks passed
@Ozaq Ozaq deleted the feature/zarr-fdb-interface-todos branch October 30, 2025 13:00
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.

4 participants