7 months ago
I know that this issue is supposed to be solved, but i do see these errors in my github action.
I have tried both: Installing the latest CLI via NPM and installing the latest CLI via the github action:
`
container: ghcr.io/railwayapp/cli:latest`
Can you please check if the latest CLI is working as desired?
12 Replies
7 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Failed to stream build logs: Failed to retrieve build log
- 🧵 Been regularly receiving "Failed to stream build logs" errors when running railway up in Githhub Actions
- 🧵 railway logs cli
If you find the answer from one of these, please let us know by solving the thread!
7 months ago
Hey there, which errors are you running into?
I don't see any attached to your message.
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
Every now and then (in around 25% of cases) we are running into these errors
```
Uploading...
CI mode enabled
Failed to stream build logs: Failed to retrieve build log
Error: Process completed with exit code 1.
```
Status changed to Awaiting Railway Response Railway • 7 months ago
7 months ago
Which version of the CLI are you currently on?
You can find that out with railway --version
Status changed to Awaiting User Response Railway • 7 months ago
7 months ago
we are using the container: ghcr.io/railwayapp/cli:latest in our workflow file
It is: 4.11.0 when I print `railway --version`
Status changed to Awaiting Railway Response Railway • 7 months ago
7 months ago
we are using the container: ghcr.io/railwayapp/cli:latest in our workflow file
It is: 4.11.0 when I print railway --version
7 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
7 months ago
It happening now in more than 75% of cases. So I can hardly make a deployment. Is there a specific CLI version that works?
nikolandgraf
It happening now in more than 75% of cases. So I can hardly make a deployment. Is there a specific CLI version that works?
6 months ago
Wanted to comment here as I'm getting this as well with some frequency. I'm using a project token. I'm doing a fresh install of the railway CLI everytime. This is what my deploy-backend looks like in github actions. I have also confirmed the version is the latest (4.11.0 as of today).
---
name: Deploy Backend
on:
workflow_call:
jobs:
deploy-backend:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Download backend build artifacts
uses: actions/download-artifact@v4
with:
name: backend-dist
path: dist/apps/backend
- name: Install Railway CLI
run: npm install -g @railway/cli
- name: Check Railway version
run: railway --version
- name: Deploy to Railway
run: railway up --service=${{ secrets.RAILWAY_SERVICE_ID }} --no-gitignore
env:
RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
noahd
Which version of the CLI are you currently on? You can find that out with `railway --version`
6 months ago
Is there an update on this issue? This is actually a big deal/problem for us. As a workaround we are using --detach . But this causes another problem: We have a pipeline with 3 sequential github steps. I expect that these steps are executed sequentially. But with --detach all three steps are executed in parallel, which causes problem.
Would be happy if this issue is being prioritized.
4 months ago
Hey there!
We're looking into this more now. Could you try upgrading to the latest version, v4.25.1, and letting me know if you still run into this? We want to nail down any CLI issues!
4 months ago
❌ The ticket CLI stability improvements has been marked as canceled.