NodeBreakerVoltageLevel connect may change the topology as unwanted side effect #285
Labels
bug
Something isn't working
Comments
|
There's no alert from github apparently, but powsybl/powsybl-core#1644 has been fixed by powsybl/powsybl-core#1720 |
sebalaig
added a commit
that referenced
this issue
May 28, 2021
…nwanted topology change (#285) Signed-off-by: Sébastien LAIGRE <[email protected]>
5 tasks
5 tasks
sebalaig
added a commit
that referenced
this issue
May 31, 2021
…nwanted topology change (#285) Signed-off-by: Sébastien LAIGRE <[email protected]>
mathbagu
pushed a commit
that referenced
this issue
May 31, 2021
…nwanted topology change (#285) (#324) Signed-off-by: Sébastien LAIGRE <[email protected]>
mathbagu
pushed a commit
that referenced
this issue
Nov 30, 2021
…nwanted topology change (#285) (#324) Signed-off-by: Sébastien LAIGRE <[email protected]>
mathbagu
pushed a commit
that referenced
this issue
Jan 10, 2022
…nwanted topology change (#285) (#324) Signed-off-by: Sébastien LAIGRE <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
NodeBreakerVoltageLevel connect may change the topology as unwanted side effect powsybl-core#1644
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
NodeBreakerVoltageLevel connect may change the topology as unwanted side effect powsybl-core#1644
What is the expected behavior?
NodeBreakerVoltageLevel connect may change the topology as unwanted side effect powsybl-core#1644
What is the motivation / use case for changing the behavior?
NodeBreakerVoltageLevel connect may change the topology as unwanted side effect powsybl-core#1644
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, spectrum, etc)
(if a question doesn't apply, you can delete it)
The text was updated successfully, but these errors were encountered: