Error deploying pages project to preview environment

Using wrangler 3.15.0, I cannot deploy my pages project to a preview environment. Using the following pages deployment command:

> wrangler pages deploy static --project-name=<REDACTED>
▲ [WARNING] Warning: Your working directory is a git repo and has uncommitted changes

  To silence this warning, pass in --commit-dirty=true


✨ Compiled Worker successfully
🌍  Uploading... (93/93)

✨ Success! Uploaded 0 files (93 already uploaded) (0.46 sec)

✨ Uploading Functions bundle
✨ Deployment complete! Take a peek over at <REDACTED>

> wrangler pages deploy static --project-name=<REDACTED>
▲ [WARNING] Warning: Your working directory is a git repo and has uncommitted changes

  To silence this warning, pass in --commit-dirty=true


✨ Compiled Worker successfully
🌍  Uploading... (93/93)

✨ Success! Uploaded 0 files (93 already uploaded) (0.46 sec)

✨ Uploading Functions bundle
✨ Deployment complete! Take a peek over at <REDACTED>

> wrangler pages deploy static --project-name=<REDACTED>
▲ [WARNING] Warning: Your working directory is a git repo and has uncommitted changes

  To silence this warning, pass in --commit-dirty=true


✨ Compiled Worker successfully
🌍  Uploading... (93/93)

✨ Success! Uploaded 0 files (93 already uploaded) (0.46 sec)

✨ Uploading Functions bundle
✨ Deployment complete! Take a peek over at <REDACTED>

> wrangler pages deploy static --project-name=<REDACTED>
▲ [WARNING] Warning: Your working directory is a git repo and has uncommitted changes

  To silence this warning, pass in --commit-dirty=true


✨ Compiled Worker successfully
🌍  Uploading... (93/93)

✨ Success! Uploaded 0 files (93 already uploaded) (0.46 sec)

✨ Uploading Functions bundle
✨ Deployment complete! Take a peek over at <REDACTED>

James•11/5/23, 7:27 PM

It sounds like you're running into https://github.com/cloudflare/workers-sdk/issues/3966, where your Functions are erroring after being uploaded

landonOP•11/5/23, 7:28 PM

so maybe a compilation error in the fuctions could be causing this?

James•11/5/23, 7:28 PM

not a compilation error, something at runtime specifically

landonOP•11/5/23, 7:28 PM

is there a log i could look at myself?

James•11/5/23, 7:29 PM

unfortunately there is not. If you post a deployment ID, I can ping someone tomorrow to take a look for you

landonOP•11/5/23, 7:30 PM

from the url looks like this could be the deployment id: 9604495b-8d76-4a37-890a-4131f5a6103e9604495b-8d76-4a37-890a-4131f5a6103e

landonOP•11/5/23, 7:31 PM

looking forward to understanding more tomorrow

James•11/5/23, 7:33 PM

thanks, I'll ping someone to pull logs for you, sorry for the trouble

James•11/5/23, 7:34 PM

Out of interest, does it work locally with pages devpages dev? That might be a way you can shortcut figuring this out if it errors there too

landonOP•11/5/23, 7:35 PM

yeah sure does

James•11/5/23, 7:39 PM

that's no fun, sorry. Hopefully the logs will yield more info

landonOP•11/5/23, 7:41 PM

well, getting an issue with 3.15.0 that im not getting with 3.4.0

Error: D1_ERROR: no such table: dashboard_notifications

Error: D1_ERROR: no such table: dashboard_notifications

landonOP•11/5/23, 7:41 PM

there any issues w/ d1 bindings that could be causing this? (ive tried to deploy with 3.4.0 as well)

James•11/5/23, 7:42 PM

not to my knowledge

you might try asking in #d1-beta

James•11/5/23, 10:04 PM

some logs were pulled for you @landon :

James•11/5/23, 10:04 PM

could not resolve binding "BUILD_SCHEDULER"could not resolve binding "BUILD_SCHEDULER"

James•11/5/23, 10:04 PM

something about your service binding config is incorrect

James•11/5/23, 10:04 PM

double check your environments and everything there is setup correctly

landonOP•11/5/23, 10:04 PM

Will do thank you!

landonOP•11/5/23, 10:15 PM

i checked to make sure its bound through the UI. i selected "production" but its linking to a staging version (our worker is confusingly named build-scheduler-stagingbuild-scheduler-staging)

https://dash.cloudflare.com/e7526284f9ee484875c61723e78af4ae/workers/services/view/build-scheduler-staging/staging

i get a 404 from that link, but f i replace that last path parameter of "staging" with "production" it resolves

James•11/5/23, 10:17 PM

hmmm, is build-scheduler-stagingbuild-scheduler-staging a very old worker that uses service environments or something like that? What's your account ID?

James•11/5/23, 10:19 PM

dumb question, it's in your url above e7526284f9ee484875c61723e78af4aee7526284f9ee484875c61723e78af4ae

James•11/5/23, 10:21 PM

what happens if you try and edit the binding and point it to the productionproduction env? (service environments were an old thing that's since legacy, so every worker has a productionproduction env that's just default nowadays)

landonOP•11/5/23, 10:24 PM

I tried that it had no effect

landonOP•11/5/23, 10:25 PM

The link still pointed to staging

James•11/5/23, 10:28 PM

Can you check the payload being sent from the dash when you make that change, in your browser's network reqs?

landonOP•11/5/23, 10:30 PM

Sorry I had to step away I can check in about 10 min

landonOP•11/5/23, 10:49 PM

little disparity here between what im sending, and what im receiving check it

{"deployment_configs":{"preview":{"services":{"BUILD_SCHEDULER":{"service":"build-scheduler-staging","environment":"production"}}}}}

{"deployment_configs":{"preview":{"services":{"BUILD_SCHEDULER":{"service":"build-scheduler-staging","environment":"production"}}}}}

and then in the response i see:

...
        "services": {
          "BUILD_SCHEDULER": {
            "service": "build-scheduler-staging",
            "environment": "staging"
          }
        },
...

...
        "services": {
          "BUILD_SCHEDULER": {
            "service": "build-scheduler-staging",
            "environment": "staging"
          }
        },
...

James•11/5/23, 10:52 PM

oookay I think we're getting somewhere. Can you try entirely removing it, save, and then re-add, and save again? I think there's a bug there that's pending a fix but it hasn't landed yet

landonOP•11/5/23, 10:54 PM

yeah i tried to do that, but i did it in one shot, hold on let me try again ins eparate steps

landonOP•11/5/23, 10:55 PM

ok response looks better, let me try to redeploy

landonOP•11/5/23, 10:56 PM

success!

landonOP•11/5/23, 10:56 PM

thank you

James•11/5/23, 10:56 PM

awesome!

kingmesal•11/6/23, 3:16 PM

There is an inconsistency in the API implementation and docs.

When doing wrangler deploy --env stagingwrangler deploy --env staging on my function name test it creates the worker as test-staging, but based on this, it seems like the worker should be deployed as name=testname=test with env="staging"env="staging"

What is the process to get these 2 sides synced up?

Kkingmesal There is an inconsistency in the API implementation and docs. When doing `wrang...

Chaika•11/6/23, 3:19 PM

Sounds like you're confusing Pages and Workers? This is the Pages help forum. Pages have full blown environments, prod & preview for the same pages project. Workers don't, they used to have something like it, but now it just works like you've reported -- by creating separate workers
Please make your own #workers-help thread if you need help, don't hijack others

CChaika Sounds like you're confusing Pages and Workers? This is the Pages help forum. Pa...

kingmesal•11/6/23, 3:20 PM

Thanks for that, but I'm not. A pages project can depend on a worker through a service binding. That binding naming / env is the problem.

kingmesal•11/6/23, 3:29 PM

There are numerous problems between the names / env as well as the API for creating bindings.

It starts with deploying a worker (aka service) -- let's call it test
wrangler deploy --env stagingwrangler deploy --env staging
This results in a worker being deployed named
test-stagingtest-staging

If you then try to add a 'service' binding to your pages project via the API
https://developers.cloudflare.com/api/operations/pages-project-create-project
The docs incorrectly say:

      "service_bindings": {
        "SERVICE_BINDING": {
          "environment": "production",
          "service": "example-worker"
        }
      }

      "service_bindings": {
        "SERVICE_BINDING": {
          "environment": "production",
          "service": "example-worker"
        }
      }

Now check the wrangler docs:
https://developers.cloudflare.com/workers/wrangler/configuration/#service-bindings
It has a correct layout which is:

      "services": {
        "SERVICE_BINDING": {
          "environment": "production",
          "service": "example-worker"
        }
      }

      "services": {
        "SERVICE_BINDING": {
          "environment": "production",
          "service": "example-worker"
        }
      }

EXCEPT, that doc says environment is optional, but via the API it is not optional. It is required.

Now if you deployed the

test

test

worker into stagingstaging you might think that service

test

test

with environment stagingstaging is correct, but that worker wont' exist because it was deployed as test-stagingtest-staging. If you specify service as test-stagingtest-staging and environment as stagingstaging that also will not work because when that worker was deployed the actual behind the scenes environment was set to productionproduction.

kingmesal•11/6/23, 3:34 PM

I would consider this to be a pretty big inconsistency that should get resolved ASAP.

I raised a support issue on the API doc inconsistency, but had not yet experience the pages -> service binding environment issue.
https://support.cloudflare.com/hc/en-us/requests/2938937

But this problem is worse than just an inconsistency in the docs, because this is an implementation inconsistency in wrangler and pages services references.

Kkingmesal There are numerous problems between the names / env as well as the API for creat...

Chaika•11/6/23, 3:36 PM

Again, that's just how workers work. They have no environments, those are a relic of the past, always production these days. You can specify different service bindings for each pages environment, ex example-worker for prod, example-worker-staging for preview

Chaika•11/6/23, 3:37 PM

James has a pretty good summary on that all with Workers, let me see if I can't dig it up

Chaika•11/6/23, 3:37 PM

https://community.cloudflare.com/t/environments-vs-deployments/451036/2?u=chaika
it is a bit confusing to be fair

Chaika•11/6/23, 3:38 PM

There is ongoing work to make that simpler with convergence of pages & workers: https://blog.cloudflare.com/pages-and-workers-are-converging-into-one-experience/, but still a while out afaik

CChaika Again, that's just how workers work. They have no environments, those are a reli...

kingmesal•11/6/23, 3:39 PM

I understand what you are saying...

then the docs need to get corrected and environment on the pages service bindings should be removed because it can ONLY be productionproduction

Chaika•11/6/23, 3:40 PM

The thing is really really old workers can still have environments, you just can't set them anymore on new workers, so it's a bit more complex then that, I just simplified it a bit

kingmesal•11/6/23, 3:40 PM

okay... then why do the docs not reflect that information

Chaika•11/6/23, 3:40 PM

hmm, where?

Chaika•11/6/23, 3:41 PM

I can't view support tickets, if the details are in there

Chaika•11/6/23, 3:41 PM

The docs are also open source, might just be redirected/could just create an issue there

kingmesal•11/6/23, 3:41 PM

the links I just shared to wrangler and the API docs

Error deploying pages project to preview environment

Similar Threads

Similar Threads

Similar Threads