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
The number of build errors resulting from empty data files coming from Wildlife Computers API has increased in the last few weeks. It was previously 1-2x (hours) per day but in recent days/week it has increased to 6-10x (hours) per day.
This coincides with a separate note from @StacieKozHardy that she's seen similar issues in downloads of PEP telemetry data.
I suspect this issue resides within the wcUtils package and how it interacts with the Wildlife Computers API. It may also be that there are some limitations or other issues with the Wildlife Computers API causing the return of empty data.
The text was updated successfully, but these errors were encountered:
The number of build errors resulting from empty data files coming from Wildlife Computers API has increased in the last few weeks. It was previously 1-2x (hours) per day but in recent days/week it has increased to 6-10x (hours) per day.
This coincides with a separate note from @StacieKozHardy that she's seen similar issues in downloads of PEP telemetry data.
I suspect this issue resides within the
wcUtils
package and how it interacts with the Wildlife Computers API. It may also be that there are some limitations or other issues with the Wildlife Computers API causing the return of empty data.The text was updated successfully, but these errors were encountered: