-
Notifications
You must be signed in to change notification settings - Fork 910
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR production parser down #3999
Comments
From logs:
|
The interesting thing isn't so much the warning (it should continue working just fine in spite of it), but that it is always the exact same amount. A look at the timestamp URL confirms what I feared: data hasn't been updated since 03/24/2022 04:43:29 PM. Given that #3613 mentions the website where we're getting the data is being phased out, I'm not very hopeful it'll start being updated again. Edit: clearer wording in last sentence |
Yeah good point, if nothing else it would confirm if that's the reason why it's happening :) |
The new website didn't have the information we need, IIRC. |
I checked again, and it looks like the new website has generation data now: https://lumapr.com/system-overview/?lang=en Please note that they're using geoblocking, so if you're not in the United States you'll need to use a VPN or similar to view it. |
verify the new website https://genera-pr.com/data-generacion |
Greetings, you have been able to analyze the data provided. |
Thanks for the heads-up, I checked the website linked in your previous comment. Interestingly, they have a generation by fuel type breakdown for thernal generation now, which is what #5232 and #5334 got stuck on. Pinging @VIKTORVAV99 and @MuffinCompiler as they were previously involved with the Puerto Rico parser fixing attempts. |
please see if this link which is the new one from the old link works |
Description
This is an automatic error report generated for Puerto Rico (PR).
Issues:
production
parserSuggestions
poetry run test_parser PR production
You can see an overview of all parser issues here.
The text was updated successfully, but these errors were encountered: