Open pzehner opened 4 years ago
Anyone ever figure out anything about this?
Ouch I have the exact same issue :\ Update - I checked the code and it seems it all started since version 1.3. That method just raises NotImplementedError without even explaining what exactly is not implemented. Please fix this guys, it's been 3 years already with that pretty weird (bad?) code sitting in there
Are there exact steps available for us to reproduce this issue?
Is it still happening with the latest releases of fabric 2.6 and invoke 1.7?
Ehhh... Still not fixed? Omg
Are there exact steps available for us to reproduce this issue?
Is it still happening with the latest releases of fabric 2.6 and invoke 1.7?
Fabric 2.7.1 and invoke 1.7.3 works fine for me inside this Bitbucket ci/cd pipeline:
image: python:3.9-bullseye
pipelines:
default:
- step:
script:
- python --version
branches:
master:
- step:
script:
- apt-get update && apt-get install -y unzip rsync build-essential libssl-dev libffi-dev cargo
- curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs >> rustup.sh
- sh rustup.sh -y
- rustc --version
- pip install --upgrade pip
- pip install fabric2==2.7.1
- pip install patchwork
- fab2 deploy
Also my pip list
output:
bcrypt 4.0.1
cffi 1.15.1
cryptography 40.0.2
fabric2 2.7.1
invoke 1.7.3
paramiko 3.1.0
patchwork 1.0.1
pathlib2 2.3.7.post1
pip 23.1.2
pycparser 2.21
PyNaCl 1.5.0
setuptools 58.1.0
six 1.16.0
wheel 0.40.0
For people landing here with the same error: patchwork forcing an invoke 1.7.3 on a fabric2 3.x.x version was the issue for me :)
I use Invoke v1.3.0 through Fabric v2.4.0 to execute actions on a remote server from a Docker container run by Gitlab-CI. When trying to run a simple remote command (i.e.
uname -a
), I get the following exception:Here are the last lines of the logs:
I was unable to reproduce the bug: neither on dev environment, nor on the same Docker container, nor on the same Docker container on the same host as Gitlab-CI. I have absolutely no clue on what is going wrong and why
close_proc_stdin
is called. I have no problem when using Invoke v1.2.0, ashandle_stdin
behaves differently (see for v1.2.0 and for v1.3.0)