Repository navigation
Tags
Tags
chore: simplify ruff (#922) ## Checklist Please check if the PR fulfills these requirements: - [x] PR Title follows conventional commit messages - [ ] Tests for the changes have been added (for bug fixes / features) - [ ] Docs have been added / updated (for bug fixes / features) - [x] All commits in this PR are DCO signed-off (see CONTRIBUTING.md) ## Does this PR already have an issue describing the problem? Fixes # ## What is the new behavior and why? ruff is now officially called ruff-check remove duplicate call ## Does this PR introduce a breaking change? - [ ] Yes, because - [x] No Signed-off-by: Sascha Petznick <229719644+spetznick-elia@users.noreply.github.com>
build(deps): bump tornado to 6.6 (#890) ## Checklist Please check if the PR fulfills these requirements: - [x] PR Title follows conventional commit messages - [ ] Tests for the changes have been added (for bug fixes / features) — n/a, dependency update only - [ ] Docs have been added / updated (for bug fixes / features) — n/a, dependency update only - [x] All commits in this PR are DCO signed-off (see CONTRIBUTING.md) ## Does this PR already have an issue describing the problem? No linked issue. Dependabot raised 21 security alerts for tornado (three advisories, each in all seven lockfiles) and opened one fix PR per lockfile. This PR bundles them so CI runs once. Supersedes #881, #882, #883, #884, #885, #886, #887. Partly supersedes #878 (see below). #869 is already on `main` via #871 and can be closed. ## What is the new behavior and why? tornado 6.6 is now locked in the root and every package environment, which closes these advisories: - GHSA-pcg2-g6cj-q92c (medium): quadratic CPU use when parsing HTTP headers with line folding - GHSA-r4j5-9xpp-3985 (medium): event-loop blocking and excess memory use from chunked bodies with many small chunks - GHSA-pw9p-v7r6-gx4p (low): open redirect in `RedirectHandler` via protocol-relative URLs The Docker image now builds with uv 0.13.7 (from #878). Deliberately left out: - **python:3.15.0 base image** (#878): the packages declare `requires-python = ">=3.11,<3.15"` and CI tests 3.11–3.14, so the image stays on 3.14.7 until 3.15 support is added. - **pandas 3** (#504): pandapower still requires `pandas<3`. ## Does this PR introduce a breaking change? - [ ] Yes, because - [x] No --------- Signed-off-by: Sascha Petznick <229719644+spetznick-elia@users.noreply.github.com>
feat: configurable monitoring of 3W trafo legs (#876) feat: configurable monitoring of 3W trafo legs --- ## Checklist Please check if the PR fulfills these requirements: - [x] PR Title follows conventional commit messages - [x] Tests for the changes have been added (for bug fixes / features) - [x] Docs have been added / updated (for bug fixes / features) - [x] All commits in this PR are DCO signed-off (see CONTRIBUTING.md) ## Does this PR already have an issue describing the problem? No linked issue. The problem showed up with input N-1 definitions that list three-winding transformers as monitored elements. ## What is the new behavior and why? The importer replaces every three-winding transformer with three two-winding legs. Until now, a monitored three-winding transformer passed its `optimized`, `non_worsening` and `displayed` flags to all three legs. One transformer then showed up three times in the UI and was optimized three times, although usually only one leg carries a limit. The new importer parameter `trafo3w_leg_monitoring` selects how the legs inherit the flags. It applies to the input N-1 definition and to the definition derived from the network masks. The lead leg is the first leg with an operational limit (Leg1, Leg2, Leg3 in that order), or Leg1 with a warning if no leg has a limit. | Mode | Lead leg | Other legs | |---|---|---| | `trafo3w_all_legs_monitoring` (default) | all flags | all flags | | `trafo3w_single_leg_monitoring` | all flags | not optimized, not displayed; non-worsening only if the transformer is optimized and not non-worsening | | `trafo3w_remove_non_lead_legs` | all flags | removed from the monitored elements | Contingencies and SPPS rules are not affected by the mode; outaging a three-winding transformer still outages all three legs. A leg that the definition lists by its own id keeps its own flags. ## Does this PR introduce a breaking change? - [ ] Yes, because - [x] No --------- Signed-off-by: Sascha Petznick <229719644+spetznick-elia@users.noreply.github.com>
Merge remote-tracking branch 'origin/main' into feat/add-qu-controlle… …rs-result-data Signed-off-by: siarhei <Siarhei.Matsiushonak_ext@50hertz.com>
build(deps): bump certifi, filelock, nbconvert, pillow and virtualenv (… …#861) ## Checklist Please check if the PR fulfills these requirements: - [x] PR Title follows conventional commit messages - [ ] Tests for the changes have been added (for bug fixes / features) — n/a, lockfile-only dependency update - [ ] Docs have been added / updated (for bug fixes / features) — n/a, lockfile-only dependency update - [x] All commits in this PR are DCO signed-off (see CONTRIBUTING.md) ## Does this PR already have an issue describing the problem? No linked issue. Dependabot opened 16 PRs that each bump one transitive dependency in one lockfile. This PR replaces them so CI runs once and all lockfiles stay on the same versions. Supersedes #844, #845, #846, #847, #848, #849, #850, #851, #852, #853, #854, #855, #856, #857, #858, #859. ## What is the new behavior? No functional change. The root lockfile and all six package lockfiles now resolve to: - certifi 2026.10.23 (#851, #853, #856 proposed 2026.10.19) - filelock 4.2.4 (#849, #855, #858 proposed 4.2.1) - nbconvert 7.17.2 (#850, #854, #857) - pillow 13.0.0 (#844–#847): major version, pulled in through matplotlib, not imported by ToOp itself - virtualenv 21.14.13 (#848, #852, #859): dependabot cites advisory GHSA-cx6f-vjhg-g3cc Dependabot only updated the lockfiles it opened PRs for. Here every lockfile that contains these packages is updated, so the root and package environments don't drift apart. Still open and not part of this PR: pandas 3 (#504). pandapower still requires `pandas<3`. ## Does this PR introduce a breaking change? - [ ] Yes - [x] No Signed-off-by: Sascha Petznick <229719644+spetznick-elia@users.noreply.github.com>
Merge branch 'main' into feat/artificial_dc_limits Signed-off-by: Benjamin Petrick <170433522+BenjPetr@users.noreply.github.com>
fix: fix bug in default permanent limit for some edge cases on tie lines Signed-off-by: Benjamin Petrick <170433522+BenjPetr@users.noreply.github.com>
fix: displayed_branch_ids=nminus1_definition.displayed_branch_ids Signed-off-by: Benjamin Petrick <170433522+BenjPetr@users.noreply.github.com>
feat: add a tolerance for the non worsening logic to avoid overloaded… … lines due to nummerical noise Signed-off-by: Benjamin Petrick <170433522+BenjPetr@users.noreply.github.com>
switch test to run the importer and check against the artificial dc l… …imits Signed-off-by: Benjamin Petrick <170433522+BenjPetr@users.noreply.github.com>
PreviousNext