Conversation
SteveMicroNova
force-pushed
the
PinPyroute
branch
from
96e47e4 to
8c58172
Compare
SteveMicroNova
force-pushed
the
PinPyroute
branch
from
8c58172 to
36f6e9c
Compare
|
It looks like this check is failing because of this thing that is enabled: https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-automatic-dependency-submission-for-your-repository |
linknum23
force-pushed
the
PinPyroute
branch
from
2a65c2e to
66ea462
Compare
| @@ -0,0 +1 @@ | |||
| 3.9 | |||
There was a problem hiding this comment.
to my knowledge the specific python version that the support tunnel runs in is 3.8.20, at least according to the python version I had when I entered the venv
There was a problem hiding this comment.
Yeah I was just testing out if this fixed the failures we are seeing. When I reran this check yesterday it was complaining about a missing .python-version. I'm guessing one fix here might be to upgrade this project to use pyproject.toml and follow a different package build flow.
There was a problem hiding this comment.
There is some incompatibility with how we currently build this project and this security check.
linknum23
left a comment
linknum23
left a comment
There was a problem hiding this comment.
Lets merge this in and then we can fix the failing dependency issue.
2 participants
Our support tunnel has been spotty lately and the culprit was discovered by a user, stamateviorel.
pyroute2 version 0.7.12 is the last version of pyroute supported by wireguard, which demands it be under version 8.0. pyroute is up to version 0.9.2 or so, so our unpinned versioning was bricking the support tunnels in the field (which will be solved after any update once this is merged)