You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[DEBUG: 2025-01-10 14:49:47 : segment_gatherer] No key 'uri' in message.
[DEBUG: 2025-01-10 14:49:47 : segment_gatherer] No parser matching message, skipping.
Why do I have all_files_are_local: True when collecting dataset messages where the scheme has already been filtered? Because I have a segment gatherer that collects 1) a dataset message with 40 FDHSI files (scheme already removed with a previous segment gatherer), together with 2) a file message with a single CLM file (scheme still present).
The scheme removal functionality appears to assume the uri is present top-level in the message:
As a solution, the scheme removal functionality could have an internal try/except and not remove a scheme if it doesn't find an URI, or it could go into a dataset and remove the URI from all components.
The text was updated successfully, but these errors were encountered:
When
all_files_are_local: True
is set, the segment gatherer skips all dataset messages.With
"all_files_are_local": False
, this gives:With
"all_files_are_local": True
, this gives:Why do I have
all_files_are_local: True
when collecting dataset messages where the scheme has already been filtered? Because I have a segment gatherer that collects 1) a dataset message with 40 FDHSI files (scheme already removed with a previous segment gatherer), together with 2) a file message with a single CLM file (scheme still present).The scheme removal functionality appears to assume the uri is present top-level in the message:
pytroll-collectors/pytroll_collectors/segments.py
Line 200 in 292e745
this triggers a
KeyError
handled by:pytroll-collectors/pytroll_collectors/segments.py
Lines 819 to 820 in 292e745
As a solution, the scheme removal functionality could have an internal try/except and not remove a scheme if it doesn't find an URI, or it could go into a dataset and remove the URI from all components.
The text was updated successfully, but these errors were encountered: