Skip to content

Conversation

b8raoult
Copy link
Collaborator

@b8raoult b8raoult commented May 7, 2025

Description

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Issue Number

Code Compatibility

  • I have performed a self-review of my code

Code Performance and Testing

  • I have added tests that prove my fix is effective or that my feature works
  • I ran the complete Pytest test suite locally, and they pass

Dependencies

  • I have ensured that the code is still pip-installable after the changes and runs
  • I have tested that new dependencies themselves are pip-installable.

Documentation

  • My code follows the style guidelines of this project
  • I have updated the documentation and docstrings to reflect the changes
  • I have added comments to my code, particularly in hard-to-understand areas

Additional Notes

@github-actions github-actions bot added the enhancement New feature or request label May 7, 2025
Copy link
Contributor

@flyIchtus flyIchtus left a comment

Choose a reason for hiding this comment

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

All good ! Only one small comment.

assert not kwargs
raise NotImplementedError("requests not implemented")

if kwargs:
Copy link
Contributor

Choose a reason for hiding this comment

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

Could we briefly explain why requests and kwargs are incompatible ?

Copy link
Contributor

@aaron-hopkinson aaron-hopkinson left a comment

Choose a reason for hiding this comment

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

Do we have tests to check the new behaviour?

indexdb=use_grib_index,
flavour=None,
requests=requests,
request_already_using_valid_datetime=True,
Copy link
Contributor

Choose a reason for hiding this comment

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

request_already_using_valid_datetime isn't actually changing the behaviour of the code, as far as I can tell


if requests is not None:
assert not kwargs
raise NotImplementedError("requests not implemented")
Copy link
Contributor

Choose a reason for hiding this comment

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

If we're not using it, why add it?

raise NotImplementedError("requests not implemented")

if kwargs:
assert not requests
Copy link
Contributor

Choose a reason for hiding this comment

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

Because request_already_using_valid_datetime=True in the accumulation source, this will fail if requests is truthy – is it better to capture that error at that level rather than here? (I don't mind - just curious)

----------
dates : List[Any]
List of dates to retrieve data for.
request_already_using_valid_datetime : bool, optional
Copy link
Contributor

Choose a reason for hiding this comment

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

request_already_using_valid_datetime is set to True in the accumulation code, has a default of False here - but there's no switch that changes the behaviour of the code. This feels incorrect to me

@github-project-automation github-project-automation bot moved this from Now In Progress to Under Review in Anemoi-dev Aug 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Under Review

Development

Successfully merging this pull request may close these issues.

4 participants