Skip to content
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

Automation for production parser issues broken - fails to open new issues? #7747

Open
consideRatio opened this issue Jan 15, 2025 · 1 comment
Assignees

Comments

@consideRatio
Copy link
Contributor

consideRatio commented Jan 15, 2025

The production parser is down for BD (at least until #7746), but there was no github issue for it opened saying the production parser is down as I expected.

Doing poetry run test-parser BD production leads to the following error, and BD data seems to have been estimated since 15th November. Why didn't we have an issue opened about it? I guess it can be because its failing to open new issues, but perhaps succeeding to comment on the PR as I've seen it active commenting previously.

parsers.lib.exceptions.ParserException: ERP_PGCB.py Parser: Table headers mismatch with expected ones.Expected: ['Date', 'Time', 'Generation(MW)', 'Demand(MW)', 'Loadshed', 'Gas', 'Liquid Fuel', 'Coal', 'Hydro', 'Solar', 'Wind', 'Bheramara HVDC', 'Tripura', 'Adani', 'Remarks']Parsed: ['Date', 'Time', 'Generation(MW)', 'Demand(MW)', 'Loadshed', 'Gas', 'Liquid Fuel', 'Coal', 'Hydro', 'Solar', 'Wind', 'India', 'Nepal', 'Remarks', 'Bheramara HVDC', 'Tripura', 'Adani']
@VIKTORVAV99
Copy link
Member

BTW I think I might have figured out the issue here, it seems to think that estimated data also comes from the parsers, basically it's checking the output of our data instead of the inputs.

I'll see if I can fix that.

@VIKTORVAV99 VIKTORVAV99 self-assigned this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants