[ERROR] ENOENT: no such file or directory, open '/pages/build_tool/js/.wrangler/tmp/pages-XcFqUA...'
I'm having a problem building an update of my app in cloudflare pages as after all the building of the client, during the build phase of the functions it drops me this error
✘ [ERROR] ENOENT: no such file or directory, open '/pages/build_tool/js/.wrangler/tmp/pages-XcFqUA/functionsWorker-0.889026161898957.js'
i've never seen this before
27 Replies
Anyone? I'm not able to build anything with functions inside pages
Have you got a deployment ID?
?pages-deployment-id
The Pages deployment ID is a unique build identifier.
It's the UUID in the browser bar (for example, a URL would be
dash.cloudflare.com/ACCOUNT_ID/pages/view/PROJECT/DEPLOYMENT_ID where the deployment ID looks something like a398d794-7322-4c97-96d9-40b5140a8d9b).
This ID can help troubleshoot some issues with Pages builds so if you have a failing build make sure you grab that ID for the Pages team to use.Hey, @naive17 the release has been rolled back. Can you do a new build and confirm it works now?
Hey thanks for the reply!
I'm split between the forum and there so sorry for the late response, i'm retrying a build.
also on the forum they requested a wrangler.toml file but i never needed one
I can confirm the build is now working!
@Walshy | Deploying (OOO)
Perfect!
Just to confirm did you not have a wrangler.toml in the project then?
yup, never had one
Was it something i did wrong?
Nope, you're good
That was the suspected cause of issues, so we just needed to try and validate that suspicion
Okok, thanks a lot! Appreciate the care ❤️
Could you give a deployment ID for one of the ones that failed so we can dig deeper? @naive17
Here a failed one, i tried few times to remake the deployment and then made a mock commit to forcibly retry, that's why there should be a pair of failed deployments with the same commit btw
be5b21cf-000f-4e42-8d29-ea809da4ba7c
Thank you for sharing!
Hey @Walshy | Deploying sorry to bother again, but the same problem is happening again, it worked flawlessly for few days but now the build is failing.
I'll give you the deployment id
c3b5e78e-efa1-4381-9d6a-b9e98f8714aa
👀
Very very very weird
So we rolled back, that fixed it, I guess we rolled a new release and it broke again. Will ping the team and have them investigate
Okay i'll wait for news
Do you possibly have a repro by chance we can test with?
Seems it breaks with functions, so maybe just testing with a repo with functions folders(?)
The annoying part is, it definitely isn't all Functions or we'd have been in an incident right away 😦
It's something weirdly specific with you, I'm just not sure what. Anyway, I just made an internal escalation and will let you know what happens
Okay the only thing maybe that can help is that the project is a monorepo and the functions folder is a symlink to a subfolder
/functions redirect to /client/functions
as it was very complicated to move everything away we made it this way and it always worked.
probably that's the only weird thing
oh interesting, let me note that down. It shouldn't cause issues but symlinks are a bit unpredictable at times
Yeah! that's the only weird thing i could think of
Hey @Walshy | Deploying tiny update on the situation.
I literally moved the code outside the /client/functions and removed the symlink so now functions are just inside /functions at the root of the folder and everything built successfully.
Very weird behaviour, probably something changed by your side and it's not able anymore to handle symlinks.
Not a big problem, very quirky!
Looks solved to me nonetheless after my actions
Interesting, thanks for the update! The team have the internal escalation so they can figure out what happened and hopefully fix it for others 🙂
Good to hear! The symlink things was just to separate it from the other folders, as functions would not mean anything at the root, but understandably that's a bit out of scope from pages haha.
thanks for the support in the end ❤️
@Walshy I seem to have the same issue - symlinking the functions dir gives me the same error that OP reported:
✘ [ERROR] ENOENT: no such file or directory, open '/Users/nickfisher/Documents/polyvox/.wrangler/tmp/pages-hyR6eo/functionsWorker-0.9542707583863828.js'
if I delete the symlink and move the functions dir to the top-level dir (so it's sitting alongside wrangler.toml), everything works
(as an aside, it's a bit counterintuitive that you cannot put the functions dir in the same directory as pages_build_output_dir)@Walshy | Deploying for nuxt i have the same issue since today... All builds which worked before, now have this error:
[error] ENOENT: no such file or directory, open '/opt/buildhome/repo/@css-inline/css-inline-wasm/index_bg.wasm'