Why am I not able to deploy my last git commit

I had pushed my requirements.txt file as requirements. Made the necessary changes and commits. But I am still seeing the older commit that is being deployed. How do I deploy the latest commit?

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

Solved

11 Replies

a year ago

you can use ctrl+k (or cmd+k on mac) to open the command pallet while on a service, you should then see an option to deploy the latest commit


Oh nice, I tried removing the deployment first and then got the option for the latest commit. Thanks!


dev

you can use ctrl+k (or cmd+k on mac) to open the command pallet while on a service, you should then see an option to deploy the latest commit

Can you help with this too? I am using Python Django btw:
context: 70b21e39584d526ff698766d118f7b0d

Dec 30 16:11:47

Nixpacks build failed

Dec 30 16:11:47

Dec 30 16:11:47

Error: Error reading runtime.txt

Dec 30 16:11:47

Dec 30 16:11:47

Caused by:

Dec 30 16:11:47

stream did not contain valid UTF-8


a year ago

Does your runtime.txt contain valid UTF-8?


(venv) PS C:\Users\ms\Codes and docs\Iteration_5\Server> $path = "runtime.txt"

(venv) PS C:\Users\ms\Codes and docs\Iteration_5\Server> $encoding = (Get-Content $path -Encoding Byte | Set-Content temp.txt -Encoding utf8)

(venv) PS C:\Users\ms\Codes and docs\Iteration_5\Server> Write-Host "File is encoded as UTF-8"

File is encoded as UTF-8

It does show; I previously used heroku. A lot of things in Railway seem new to me.


dev

Does your runtime.txt contain valid UTF-8?

Should I try using the Railway CLI? What would be better?


a year ago

Nah using CLI wouldn't make a difference, the issue is that the file just isn't encoded as UTF-8.. I'd personally just copy and paste the contents over to Notepad or some other text editor and make sure it saves the content as UTF-8 and then I'd use that new file


a year ago

Did you manage to get it working?


a year ago

Yes they did.


dev

Did you manage to get it working?

Yep, idk didn't work any how, so deleted the deployment and redeployed. And I haven't been getting the commit error since.


a year ago

Oh awesome, marking as solved then


Status changed to Solved dev about 1 year ago


Loading...