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 configuration for locations loads twice at startup, it's visible in the logs with suffixed locations being loaded at startup i.e. westus, and then westus_1. It happens for all configured location files.
client
WebAPI (Default)
Relevant log output
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
I saw same issue, and I created a patch (but I've not sent it as a PR): YaSuenag@84662a4
Maybe it happens when both EmissionsDataSource and ForecastDataSource are defined.
LocationSource would be loaded when each data source are prepared, so same location JSON would be loaded by preparation phase of both EmissionsDatasource and ForecastDataSource.
My patch adds HashSet to remember loaded location JSONs, so it prevents to load in twice.
Contact Details
No response
What happened?
The configuration for locations loads twice at startup, it's visible in the logs with suffixed locations being loaded at startup i.e. westus, and then westus_1. It happens for all configured location files.
client
WebAPI (Default)
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: