a month ago
I'm seeing this timeout when trying to build... so it seems that it can't fetch. Is this a Railway issue or some issue in my setup. I don't see any issues on the status page.
poetry install --no-interaction --no-ansi --only main --no-root
17s
Creating virtualenv auther in /app/.venv
Installing dependencies from lock file
Package operations: 44 installs, 0 updates, 0 removals
- Installing idna (3.10)
- Installing six (1.16.0)
- Installing sniffio (1.3.1)
- Installing typing-extensions (4.12.2)
- Installing anyio (4.4.0)
- Installing certifi (2024.8.30)
- Installing annotated-types (0.7.0)
- Installing h11 (0.14.0)
- Installing jmespath (1.0.1)
- Installing packaging (24.1)
- Installing pycparser (2.22)
- Installing pydantic-core (2.33.2)
- Installing python-dateutil (2.9.0.post0)
- Installing typing-inspection (0.4.2)
- Installing urllib3 (2.2.3)
- Installing starlette (0.32.0.post1)
- Installing marshmallow (3.22.0)
- Installing cffi (2.0.0)
- Installing httpcore (1.0.8)
- Installing pydantic (2.11.10)
- Installing markupsafe (2.1.5)
- Installing botocore (1.35.19)
- Installing python-dotenv (1.0.1)
TimeoutError
The read operation timed out
at /mise/installs/python/3.13.13/lib/python3.13/ssl.py:1150 in read
1146│ if self._sslobj is None:
1147│ raise ValueError("Read on closed or unwrapped SSL socket.")
1148│ try:
1149│ if buffer is not None:
→ 1150│ return self._sslobj.read(len, buffer)
1151│ else:
1152│ return self._sslobj.read(len)
1153│ except SSLError as x:
1154│ if x.args[0] == SSL_ERROR_EOF and self.suppress_ragged_eofs:
The following error occurred when trying to handle this error:
ReadTimeoutError
HTTPSConnectionPool(host='files.pythonhosted.org', port=443): Read timed out.
3 Replies
a month ago
Builds do have full outbound internet access, so this is a transient timeout between our build infrastructure and PyPI (files.pythonhosted.org), not a configuration issue on your end. Retriggering the build should resolve it.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Ok, that seems to have worked... but this lack of connectivity was not reported on your status pages anywhere and it also caused my service to fail while it was operating. This was a critical auth component which cannot fail. Any ideas to make this more robust if Railway can fail to connect from time to time?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The build timeout was between our build servers and a third-party host (files.pythonhosted.org), not a Railway service outage, which is why it didn't appear on our status page. A failed build does not take down your running deployment, so your existing service should have remained active during the build failure. For resilience against deploy-time issues, configuring a healthcheck endpoint ensures traffic only switches to a new deployment after it passes the health check, and horizontal scaling with replicas provides redundancy across multiple instances.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago