hot-fix/dnp3-python-change-classname #8
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
From User:
"""
can you look at this https://github.com/eclipse-volttron/volttron-dnp3-outstation/actions/runs/4961666407/jobs/8878743363
what steps are missing to make the run test work properly
"""
Investigation:
Note "E ModuleNotFoundError: No module named 'dnp3_python.dnp3station.outstation_new'" from https://github.com/eclipse-volttron/volttron-dnp3-outstation/actions/runs/4961666407/jobs/8878743363#step:17:56
Which is caused by dnp3-python package change classname since 0.3.0, referencing issue: Backward compatibility within major viersion (after changing the classname from MyOutStationNew to MyOutStation)
Solution
Currently, pin to dnp3-python>=0.2.3 < 0.3.0