-
As observed in "Build test / distcheck (pull_request)" of #2963.
I may have to backport some changes from https://github.com/util-linux/util-linux/pull/2952 semantically.
@karelzak Please assign t…
-
## What's the test to develop? Please describe
Implement manual test case [pull backup created by another Longhorn system](https://longhorn.github.io/longhorn-tests/manual/pre-release/backup-and-re…
-
**Pros**
- Runners already exist locally/in CI
- Improving test coverage over time
- Higher confidence in code quality
- Less need for backports/Z-Stream releases
**Cons**
- Slows development …
-
## Description
In order to fix the compile errors with multiplying/solving `CWiseUnaryViews` (which originally necessitated the `val_op` and `adj_op` member introductions), I've submitted patches t…
-
PRs for stable branches should be reviewed by the bot to determine if the diff is an exact match for the original PR in devel. If there is a match, apply a label, perhaps something like `exact_backpor…
-
On any backport, check:
1) it was cherry picked
2) the thing has a test target
3) the code changed has coverage
4) it's not a new module/plugin/feature/etc
If either fails, it's an "invalid" …
-
The [new instructions](https://ros-planning.github.io/moveit_tutorials/doc/ikfast/ikfast_tutorial.html) for OpenRAVE are a lot more convenient, so they should be backported to the Melodic tutorials. W…
-
This issue tracks the back porting of Ntupliser features from 2017 and 2018 to master_2016_94X branch.
-
An addendum of https://github.com/elastic/security-docs/pull/5186. We need to backport the same changes to `7.17-8.9`. We previously merged these changes to `main` and versions `8.14-8.10`.
**NOTE…
-
**Is your feature request related to a problem? Please describe.**
previous working issue: #1114
- [ ] commit id: 3875b3e353b0e429e3114de4b8301f205d813b50
- [ ] related id: 93d555780360dc29…