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

Mexico parser working locally but not filling data in prod #7556

Open
tuxity opened this issue Dec 16, 2024 · 6 comments
Open

Mexico parser working locally but not filling data in prod #7556

tuxity opened this issue Dec 16, 2024 · 6 comments
Assignees

Comments

@tuxity
Copy link
Contributor

tuxity commented Dec 16, 2024

Description

Mexico CENACE parser is working correctly in local but not on prod it seems. I have talked about that with @VIKTORVAV99 but since Slack got close I wanted to open a ticket as a reminder.

Thanks!

@VIKTORVAV99
Copy link
Member

Description

Mexico CENACE parser is working correctly in local but not on prod it seems. I have talked about that with @VIKTORVAV99 but since Slack got close I wanted to open a ticket as a reminder.

Thanks!

Thanks!

This is actually on my todo list for after new years! We'll go into a production freeze at the end of the week over the holidays not much I can do before then unfortunately.

I think I've tracked down the issue though, just need to test and verify that's the actual cause.

@VIKTORVAV99 VIKTORVAV99 self-assigned this Dec 16, 2024
@consideRatio
Copy link
Contributor

I saw that 3rd Nov 2024 included an hour entry of 25, which breaks things for me locally when trying the production parser.

This led to pd.to_datetime erroring. I figure its hard to say why there was 25 hours entries, but maybe the fix of this is to drop the 25 hour time if it shows up?

45    02/11/2024 22
46    02/11/2024 23
47    03/11/2024 00
48    03/11/2024 01
49    03/11/2024 02
50    03/11/2024 03
51    03/11/2024 04
52    03/11/2024 05
53    03/11/2024 06
54    03/11/2024 07
55    03/11/2024 08
56    03/11/2024 09
57    03/11/2024 10
58    03/11/2024 11
59    03/11/2024 12
60    03/11/2024 13
61    03/11/2024 14
62    03/11/2024 15
63    03/11/2024 16
64    03/11/2024 17
65    03/11/2024 18
66    03/11/2024 19
67    03/11/2024 20
68    03/11/2024 21
69    03/11/2024 22
70    03/11/2024 23
71    04/11/2024 00
72    03/11/2024 25
73    04/11/2024 01
74    04/11/2024 02
75    04/11/2024 03

@VIKTORVAV99
Copy link
Member

BTW I have tracked down the issue here to an edge case which I'll personally solve as it requires both back-end and changes in here.

I am a bit busy this week but when my current project is done I'll pick up this one.

@tuxity
Copy link
Contributor Author

tuxity commented Jan 6, 2025

Thanks for noticing this @consideRatio! That is weird indeed. Idk what they did in their CSV file 😅
Thanks @VIKTORVAV99 as well!

Let me know if you need anything 🙌

@tuxity
Copy link
Contributor Author

tuxity commented Jan 17, 2025

Hello @VIKTORVAV99 did you had time to check the issue?
Can't wait to see for Mexico and start talking about ElectrictyMaps there 🙌

@VIKTORVAV99
Copy link
Member

Hello @VIKTORVAV99 did you had time to check the issue?
Can't wait to see for Mexico and start talking about ElectrictyMaps there 🙌

Yep!

The fix is included as a part of a bigger PR to merge the subzones (until we can find production data for them) which should be ready early next week.

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

3 participants