I'm seeing frequent (nightly) failures of the trigger-pipeline pipe when it tries to trigger a pipeline:
Status: Downloaded newer image for bitbucketpipelines/trigger-pipeline:5.5.1
92
Traceback (most recent call last):
93
File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 537, in _make_request
94
response = conn.getresponse()
95
File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 466, in getresponse
96
httplib_response = super().getresponse()
97
File "/usr/local/lib/python3.10/http/client.py", line 1375, in getresponse
98
response.begin()
99
File "/usr/local/lib/python3.10/http/client.py", line 318, in begin
100
version, status, reason = self._read_status()
101
File "/usr/local/lib/python3.10/http/client.py", line 279, in _read_status
102
line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
103
File "/usr/local/lib/python3.10/socket.py", line 705, in readinto
104
return self._sock.recv_into(b)
105
File "/usr/local/lib/python3.10/ssl.py", line 1307, in recv_into
106
return self.read(nbytes, buffer)
107
File "/usr/local/lib/python3.10/ssl.py", line 1163, in read
108
return self._sslobj.read(len, buffer)
109
TimeoutError: The read operation timed out
This is happened quite often lately. I'm on the latest version of the pipe. This is forcing multiple manual reruns of scheduled pipelines across different Bitbucket repositories.
