#Build failed but not sure why

63 messages · Page 1 of 1 (latest)

waxen spoke
#

Hi! I'm trying to understand why my build failed, and I can't discern any errors in the logs. Here's the deployment id: 9a66c609-3d1d-4062-a5ad-61b812df8e62, context: 009fc5728ee64eb7a597ef6570e251a0 (if that's helpful).

muted otterBOT
#

Project ID: 9a66c609-3d1d-4062-a5ad-61b812df8e62

jade pythonBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

sharp osprey
waxen spoke
#

ah cool thanks

sharp osprey
#

can you share your repo too?

waxen spoke
#

it's private though

sharp osprey
#

public it?

waxen spoke
#

can I just add your email temporarily?

#

your github

sharp osprey
#

for sure

#

brody192

waxen spoke
#

cool just added ya

sharp osprey
#

did i help you the other day, or did you just grab a railway.json from a thread that i helped someone else with?

waxen spoke
#

you did help me yeah!

sharp osprey
#

okay good, thought you where just using a random railway.json you found laying around for a sec

waxen spoke
#

I had to add some dependency to my nixpkgs array

#

lol

sharp osprey
#

okay let me get acquainted with this project

#

ive never seen python and node intermixed like this, is this some kind of framework?

waxen spoke
#

Yeah it's a little funky. Django backend/api with a react frontend

#

bundled with webpack

sharp osprey
#

ive seen that, just haven't seen them mixed like this

#

so it just looks like your build logs hang at the webpack build step

waxen spoke
#

oh rly? what's weird about the way we're doing it out of curiosity

#

^ yep

#

are there ever random transient failures? I could just retry

sharp osprey
#

usually you dont have python files sprinkled into the node project, but what do i know lol

#

how long does your build run for before it fails?

waxen spoke
#

I actually didn't see this one fail, my friend merged his commit earlier today and I just recently saw that we had a failed build

#

I'll try again

sharp osprey
#

i think build time limit is like 20 minutes

#

so something was merged that caused this to start hanging, maybe put webpack into verbose mode or something?

waxen spoke
#

Hm interesting

#

So I just forced another build and this time I got an error

sharp osprey
#

send it over

waxen spoke
#

oh looks like there's a ts error

#

in AlbumCard.tsx

sharp osprey
#

i dont even know how you saw that from within all this mess

waxen spoke
#

lol yea i stare at stacktraces too much i guess

sharp osprey
#

uh also, it spat out your api keys for everything

waxen spoke
#

oh shit

sharp osprey
#

i wont tell anyone

waxen spoke
#

did you hide them? thanks

#

haha

#

okay, built and deployed successfully

#

thanks!

sharp osprey
#

feel free to remove me from the repo!

waxen spoke
#

weird that the first failure didn't show the ts error

sharp osprey
#

yeah and the second log showed a stack trace from their internal build system, but you didnt see that 😉

waxen spoke
#

ha, from Railways?

sharp osprey
#

yep 😬

waxen spoke
#

Wait you don't work for them

sharp osprey
#

nope

waxen spoke
#

?

#

Wow

sharp osprey
#

?

waxen spoke
#

well thanks for the help!

sharp osprey
#

no problem!

waxen spoke
#

you should be getting paid!

sharp osprey
#

i get paid for template bounties