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
During the time interval 23:00--02:00 (UTC) the function query_physical_crossborder_allborders consistently errors with ValueError: No objects to concatenate.
there are only NoMatchingData errors and thus imports is never appended to.
I would suggest to raise an error message that is meaningful for the user, for instance "NoMatchingData error for all neighboring crossborder flow queries" instead of letting the Pandas ValueError bubble all the way up to the user.
If you are ok with that proposal, I am going to prepare a PR.
The text was updated successfully, but these errors were encountered:
fleimgruber
changed the title
ValueError: No objects to concatenate for query_physical_crossborder_allborders
ValueError: No objects to concatenate in query_physical_crossborder_allbordersFeb 18, 2025
During the time interval 23:00--02:00 (UTC) the function
query_physical_crossborder_allborders
consistently errors with ValueError: No objects to concatenate.The result of my analysis is that in
entsoe-py/entsoe/entsoe.py
Line 2274 in c03c604
imports
is the empty list[]
because inentsoe-py/entsoe/entsoe.py
Lines 2270 to 2273 in c03c604
NoMatchingData
errors and thusimports
is never appended to.I would suggest to raise an error message that is meaningful for the user, for instance "NoMatchingData error for all neighboring crossborder flow queries" instead of letting the Pandas ValueError bubble all the way up to the user.
If you are ok with that proposal, I am going to prepare a PR.
The text was updated successfully, but these errors were encountered: