108 Replies
Project ID:
06e4ecc3-6fcc-4222-9ab4-57bd805ed75f06e4ecc3-6fcc-4222-9ab4-57bd805ed75f
No support?
this is community support, please be patient
where do you see these logs, in the build or deployment logs
Build.
full buil logs please https://bookmarklets.up.railway.app/log-downloader/
what
Ah
second
I am mobile rn give me a while to get you the file but, this is all it shows
the bookmarklet only works on desktop browsers
ye ig
Give me a while to get on my pc then ill share the full log file
no worries
yea thats all what it gives
In the build logs
are you uploading code with railway up?
Nope
https://bookmarklets.up.railway.app/service-redeploy/
use that to redeploy
If that just redeploys the service i tried
from the button
this is different, it redoploys it from the source
Okiee
still same
what kind of app are you trying to deploy
and could you share the repo?
Its a private repo
Btw this started happening just now
before that it was working fine
^
nextjs
A monorepo but I have the root set as the nextjs dir.
Thread has been flagged to Railway team by @Brody.
Any update yet?
the team will come to this thread when they have the time to tackle this
The project ID you gave doesn't exist
This looks like an issue with your app but please link the project
Ohk a second
2d9d995c-09bb-4a71-a40f-f079b6d925ac
Uhh, can you try and deploy again?
I've literally never seen this in my life
I tried multiple times
linking unlinking the repo too
Its failing to extract the zip ig?
How are you deploying
Looks like via GH
Yea
What did you change between the successful and failed deploy?
Just added new components ig nothing much?
I dont see anything unusual
No unusual activity in ram either + the other project from same repo fails as well with same error
I'll have to log it for triage for tomorrow
👍
Please ping me if I can help w something
PRO-1368 - Fail to extract code archive
Use has issues deploying from GitHub with above error
Status
Triage
Product
Any updates?
its now the weekend, and the team doesnt work on the weekends
Any updates 😄
it's Monday morning, please wait until the team can get through the queue
but I don't know why I didn't think of it sooner, can you try to deploy your code in a new service in a new project?
Does it have no content?
Rather, does the root URL have content in it/is accurate?
It does.
I already tried it's the same
Is there any update?
I'm with cooper when he said that this looks like an issue with your app, no one has reported anything remotely similar, so it's likely something about your code
can you share your repo? provide a minimal reproducible example? something to help either me or the team
I get that it can be w my app
or something
but how will I be able to reproduce when its happening on railway only?
How do you guys clone the repo or whatever?
Maybe we can start from there
With git clone. You’ll need to create a repo publically with config we can reproduce
Do you want me to add you the do the repo?
please create a public repo that when built on railway will produce the same error
😭😭😭I wish i know what caused that error
Did you update or add any npm package ?
I mean I ddi but does that has to do w anything?
are you using "yarn.lock" or "package-lock.json" ?
Maybe the problem is when you compile a npm package
pnpm uses package-lcok iirc
But that should be in the build stage right
I will check your build logs, a moment..
i think the problem rn its not that
But sure
you can check those and lmk whatever uou find sus
Could you provide the full build log ?
I can give you access to the github repo, if you can give me your email
its provided above lemme
is this the full build log ?
yep.
thats all it has
Nothing more
Really ? oh gosh
a moment...
Yea if it was anything extra I could have digged in some more infonor knew how to debug
What do you see here ? Could you sent me the print ?
a moment... sorry
lemme see I am on phone.
What do you see here ?
I want to know what builder railway is using..
This right?
yes
its been like this since the beginning i suppose
I mean added scripts but nothing else
could you check if "pnpm-lock.yaml" was changed between commits ?
i can second
yea it was
but nothing more than addition of lodash
maybe this is the problem 🙂
let me check
Lodash? :0
What node version are you using in your pc ?
"node -v"
The packages was changed between commits. This is a good hint.
should be 20+
one second ill confirm
20.8.0
to be exact
we found a POSSIBLE solution... 🙂
Node | Nixpacks
App source + Nix packages + Docker = Image
18 is the default
a moment..
yea I am aware about that
I will try removing lodash and try deploying again
"engines" : {
"node" : ">=20.0.0"
}
Builds are slow for a subset of users - Incident details - Railway ...
Builds are slow for a subset of users - Incident details - Railway Status
I will try rmeoving lodash
But what if it doesnt work :0
you don't need to remove
just undo package-json and pnpm-lock.yaml
i mean node version too.
will try both.
change node version first
oh you mean commit
are you using it ?
.
Nope
or something similar ?
its default, should be 18 on railway
do you understand that if railway compile your code in node v18 and your computer compiles in node v20, you will get different results ?
so...
you should first check the node version
yea i am aware about that :p
it is not necessary touch in package* or anywhere
Will try
I think we found the issue
we need investigate futher
But why do I feel like this has something to do with permissions over github
there is a very easy way to check that......
railway cli
a moment...
If you want to check if the issue is github-related, use railway up
I’ll trust
try*
@Felinto btw
The same issue persist on the other folder too which hasn't had any changes
since I am on a monorepo
just trying changing the nodde version
Ohk that worked
amazingly
And the other folder too?
wowie
Is it worked?
Everything OK, now?
yea it did
Yep
Thankss
👍🥰