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

Update Windstream Parser for new emails #291

Merged
merged 4 commits into from
Sep 9, 2024

Conversation

aliex-13
Copy link
Contributor

@aliex-13 aliex-13 commented Aug 7, 2024

It seems Windstream have updated their emails with an additional table to include GPS location - Lat and Long.

This has messed with the existing parser so i've had to add some additional checks to the parser.

Just re-checks for maint_id, start and end time.

No other changes included.

Copy link
Contributor

@glennmatthews glennmatthews left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide an (anonymized) example of the updated email format to use as a test case?

circuit_maintenance_parser/parsers/windstream.py Outdated Show resolved Hide resolved
circuit_maintenance_parser/parsers/windstream.py Outdated Show resolved Hide resolved
@aliex-13
Copy link
Contributor Author

Hey @glennmatthews, test email has been added and unit tests updated.
Other threads have been resolved.

@chadell
Copy link
Collaborator

chadell commented Aug 14, 2024

@aliex-13 could you fix the CI tests?

@aliex-13
Copy link
Contributor Author

Hey @chadell - I've pushed updates to fix the pylint issues but other issues unrelated to my code are occurring. Any chance you could take a look at the pipeline and let me know. I noticed these when running my own tests internally but didn't want to mess around with other code which was already in this state.

@chadell
Copy link
Collaborator

chadell commented Aug 19, 2024

Hey @chadell - I've pushed updates to fix the pylint issues but other issues unrelated to my code are occurring. Any chance you could take a look at the pipeline and let me know. I noticed these when running my own tests internally but didn't want to mess around with other code which was already in this state.

Yes @aliex-13 , going to fix the doctest

@@ -83,7 +83,6 @@ class CircuitImpact(BaseModel, extra="forbid"):
pydantic_core._pydantic_core.ValidationError: 1 validation error for CircuitImpact
impact
Input should be 'NO-IMPACT', 'REDUCED-REDUNDANCY', 'DEGRADED' or 'OUTAGE' [type=enum, input_value='wrong impact', input_type=str]
...
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aliex-13 could you readd this to fix the doctest?

Copy link
Collaborator

@chadell chadell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@chadell chadell merged commit c51bd86 into networktocode:develop Sep 9, 2024
15 checks passed
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

Successfully merging this pull request may close these issues.

3 participants