-
**(1)**
`CConfig.py` defines a `varNamePattern`.
Inside a `for` loop this pattern is used:
`if not re.match(varNamePattern, k):`
My understanding of regular expressions is that they need t…
-
**(1)**
Input:
```
"teststring-1" : "teststring-1 value",
${params.global.teststring-1} : "${params.global.teststring-1} extended"
```
Result:
```
ERROR - Found invalid parameter name…
-
Hello,
We are trying to use this package for both `2F-140` and `2F-85` URDF files, but we notice that the naming convention is very different for the link names between the two.
Why is this the …
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Feature Description
Some files in the project have inconsistent naming conventions. For example, files like `p…
-
/area testing
We have started following test naming convention for new test cases in CAPA, we can also do this for existing test cases to bring consistency.
We use [this]( https://medium.com/@s…
-
Since PR's are squash merged, their commit into main will be named after the PR itself. It is redundant to enforce commit names since they will not show up in the protected branch anyways.
-
Currently, our naming is:
- repo: `pyglvis`
- pypi: we have two registered packages, [glvis](https://pypi.org/project/glvis/) and [pyglvis](https://pypi.org/project/pyglvis/), although `glvis` i…
-
**Describe the bug**
There is a wrong link in /docs/checks.md file:
https://github.com/ossf/scorecard/blob/6d9b2e4f78f7389961cb2e80851b4e901cf635bc/docs/checks.md (the latest commit as of the day o…
-
**Describe your environment** I am currently using the Python SDK for a sample app that creates metrics instruments like Counter, UpDownCounter, and etc. When my metrics were exported to Cloudwatch, …
-
## Proposal
When adding a test to `libocpp` that partially (or fully) validates `libocpp`'s conformance to a functional requirement in an OCPP standard, prefix the name of the test with said function…
drmrd updated
3 weeks ago