hi guys, silly question from a newbie here, I am getting starting with wrangler and I learned how to

MMarcosZapa hi guys, silly question from a newbie here, I am getting starting with wrangler ...

J

James•11/21/24, 2:13 PM

Try the

—from-dash

—from-dash

—from-dash

—from-dash option in

wrangler init

wrangler init

wrangler init

wrangler init: https://developers.cloudflare.com/workers/wrangler/commands/#init

Cloudflare Docs

Commands | Cloudflare Workers docs

Create, develop, and deploy your Cloudflare Workers with Wrangler commands.

JJames Try the `—from-dash` option in `wrangler init`: https://developers.cloudflare.co...

M

MarcosZapaOP•11/21/24, 2:49 PM

ah yes! the --from-dash command! thanks again!!

Original message was deleted

A

Adam•11/21/24, 3:38 PM

in that case I wonder if there's a way to configure an S3 client to point to the local R2 storage somehow? My problem is basically that I have a service which writes files to an R2 bucket using a standard S3 client because it runs outside of cloudflare, but then I have a cloudflare worker that wants to read those files out of R2. I can't get this setup to run locally because the cloudflare worker can only read from its own local version of r2, and the local service can only write to an s3-compatible API

B

BumblebeeSquare•11/21/24, 3:57 PM

hi all, how do i make Cloudflare build my pages sveltekit with wrangler@latest ? it keeps building it with 3.76 not 3.88 , i have compatibility date set up to latest one which is 11 on cf dashboard

S

surgery18•11/21/24, 10:09 PM

Hey guys, I just upgraded wrangler to 3.89 and now whatever I do, I cannot get my SERVICE to connect to my other wrangler instances. And yes, my other wrangler instance is persisting the data to the same .wrangler/state as the first one so all data can flow locally correctly. It was working before but now.

Services:
- POST: add-post [not connected]

I only get [not connected] now. What can I do to make that service connect again?

Thanks!

S

surgery18•11/22/24, 3:02 AM

3.88 does not work either
3.87 works.

So something from 3.88 broke the connection to Services.

V

Vladimir_dev•11/22/24, 5:52 AM

Hello. How to solve this error on windows 11?
wrangler 3.89.0

npx wrangler dev
✘ [ERROR] service core:user:hello-world: Uncaught LinkError: WebAssembly.Instance(): Import #9 "./index_bg.js" "__wbg_error_53abcd6a461f73d8": function import requires a callable

    at null.<anonymous> (shim.js:15:9)


                                                                                                                               
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.

npx wrangler dev
✘ [ERROR] service core:user:hello-world: Uncaught LinkError: WebAssembly.Instance(): Import #9 "./index_bg.js" "__wbg_error_53abcd6a461f73d8": function import requires a callable

    at null.<anonymous> (shim.js:15:9)


                                                                                                                               
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.

npx wrangler dev
✘ [ERROR] service core:user:hello-world: Uncaught LinkError: WebAssembly.Instance(): Import #9 "./index_bg.js" "__wbg_error_53abcd6a461f73d8": function import requires a callable

    at null.<anonymous> (shim.js:15:9)


                                                                                                                               
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.

npx wrangler dev
✘ [ERROR] service core:user:hello-world: Uncaught LinkError: WebAssembly.Instance(): Import #9 "./index_bg.js" "__wbg_error_53abcd6a461f73d8": function import requires a callable

    at null.<anonymous> (shim.js:15:9)


                                                                                                                               
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.

Original message was deleted

V

Vladimir_dev•11/22/24, 2:53 PM

https://github.com/cloudflare/workers-rs/issues/668#issuecomment-2486930295

[patch.crates-io]
wasm-bindgen = { git = "https://github.com/rustwasm/wasm-bindgen" }

[patch.crates-io]
wasm-bindgen = { git = "https://github.com/rustwasm/wasm-bindgen" }

[patch.crates-io]
wasm-bindgen = { git = "https://github.com/rustwasm/wasm-bindgen" }

[patch.crates-io]
wasm-bindgen = { git = "https://github.com/rustwasm/wasm-bindgen" }

Original message was deleted

C

Cyb3r-Jak3•11/23/24, 4:22 PM

Typically means that you have the wrong output directory configured

Original message was deleted

C

Cyb3r-Jak3•11/23/24, 4:56 PM

What does the

Assets Uploaded

Assets Uploaded

Assets Uploaded

Assets Uploaded tab show on the deployment logs in Cloudflare?

Original message was deleted

C

Cyb3r-Jak3•11/23/24, 5:28 PM

Weird that all looks right to me. Maybe someone else will have an idea as to why it is not working

J

James•11/23/24, 6:17 PM

Can you share the URL and ideally a screenshot of the assets uploaded so we can check if there's any nesting?

N

NH 🇮🇹•11/23/24, 9:00 PM

Hey guys,
I’m new to Cloudflare and Wrangler, so I apologize in advance if I have misunderstood anything. I’m trying to deploy my Next.js website using Cloudflare Pages, so to build/deploy I'm using the

@cloudflare/next-on-pages@1

@cloudflare/next-on-pages@1

@cloudflare/next-on-pages@1

@cloudflare/next-on-pages@1 package. This requires me to add a

wrangler.toml

wrangler.toml

wrangler.toml

wrangler.toml file to my project root as it complained about a missing

nodejs_compat

nodejs_compat

nodejs_compat

nodejs_compat flag I needed to set, which I have done in the wrangler config.

name = "<PROJECT_NAME>"
compatibility_date = "2024-11-22"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

name = "<PROJECT_NAME>"
compatibility_date = "2024-11-22"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

name = "<PROJECT_NAME>"
compatibility_date = "2024-11-22"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

name = "<PROJECT_NAME>"
compatibility_date = "2024-11-22"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

However, every time I try to deploy my site, I encounter the following issue:

21:46:32.059  Found wrangler.toml file. Reading build configuration...
21:46:32.064  pages_build_output_dir: .vercel/output/static
21:46:32.065  Build environment variables: (none found)
21:46:32.162  Successfully read wrangler.toml file.
21:46:32.300  Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
21:46:32.300  Installing project dependencies: npm clean-install --progress=false
21:46:33.815  npm WARN EBADENGINE Unsupported engine {
21:46:33.815  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.815  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.816  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:46:33.816  npm WARN EBADENGINE }
...
21:47:03.417  npm WARN EBADENGINE Unsupported engine {
21:46:33.417  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.417  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.418  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:47:04.782  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
21:47:04.798  Error: Command "npm run build" exited with 1

21:46:32.059  Found wrangler.toml file. Reading build configuration...
21:46:32.064  pages_build_output_dir: .vercel/output/static
21:46:32.065  Build environment variables: (none found)
21:46:32.162  Successfully read wrangler.toml file.
21:46:32.300  Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
21:46:32.300  Installing project dependencies: npm clean-install --progress=false
21:46:33.815  npm WARN EBADENGINE Unsupported engine {
21:46:33.815  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.815  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.816  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:46:33.816  npm WARN EBADENGINE }
...
21:47:03.417  npm WARN EBADENGINE Unsupported engine {
21:46:33.417  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.417  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.418  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:47:04.782  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
21:47:04.798  Error: Command "npm run build" exited with 1

21:46:32.059  Found wrangler.toml file. Reading build configuration...
21:46:32.064  pages_build_output_dir: .vercel/output/static
21:46:32.065  Build environment variables: (none found)
21:46:32.162  Successfully read wrangler.toml file.
21:46:32.300  Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
21:46:32.300  Installing project dependencies: npm clean-install --progress=false
21:46:33.815  npm WARN EBADENGINE Unsupported engine {
21:46:33.815  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.815  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.816  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:46:33.816  npm WARN EBADENGINE }
...
21:47:03.417  npm WARN EBADENGINE Unsupported engine {
21:46:33.417  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.417  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.418  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:47:04.782  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
21:47:04.798  Error: Command "npm run build" exited with 1

21:46:32.059  Found wrangler.toml file. Reading build configuration...
21:46:32.064  pages_build_output_dir: .vercel/output/static
21:46:32.065  Build environment variables: (none found)
21:46:32.162  Successfully read wrangler.toml file.
21:46:32.300  Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
21:46:32.300  Installing project dependencies: npm clean-install --progress=false
21:46:33.815  npm WARN EBADENGINE Unsupported engine {
21:46:33.815  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.815  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.816  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:46:33.816  npm WARN EBADENGINE }
...
21:47:03.417  npm WARN EBADENGINE Unsupported engine {
21:46:33.417  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.417  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.418  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:47:04.782  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
21:47:04.798  Error: Command "npm run build" exited with 1

N

NH 🇮🇹•11/23/24, 9:00 PM

The issue appears to be related to the Node.js version. Even though I have set the Node.js version in my environment configuration of the worker:

env NODE_VERSION        20.11.1

env NODE_VERSION        20.11.1

env NODE_VERSION        20.11.1

env NODE_VERSION        20.11.1

  

The build process is still using Node.js version 18.17.1, which is causing compatibility issues with Next.js, as it requires Node.js ^18.18.0 or higher.

Could someone advise on why the environment variable is not being recognized, or what I might be missing in the configuration? Additionally, does the nodejs_compat flag set a specific Node.js version that could be overriding the one specified in my environment variable?

Any help would be greatly appreciated!

K

Kimitri•11/24/24, 12:07 PM

Hey guys, if I use the cloudflare/wrangler-action@v3 ci/cd and put a preCommands, if the command setted in this variable fails the deploy will fail?

U

unfleshedone•11/24/24, 7:48 PM

How do I force wrangler to offer account selection on login again (after I chose the wrong one)? Logout/login doesn't seem to work...

U

unfleshedone•11/24/24, 7:49 PM

nvm, works now after several logouts

K

Kimitri•11/25/24, 11:44 AM

I would like to share something that I did yesterday.
I'm start to working in a open source side project to my portfolio to improve my chances to get a job or be founded by a recruiter, and I decided to host this project on Cloudflare. The problem was even the Cloudflare team telling wrangler file can be public because resources ids isn't sensitive information, I didn't want to share it in my public repository.
I use Vitest for test, and the Cloudflare docs says that I need to put the wrangler path in Vitest config file to this work properly to my end to end tests. So after a lot of tests I found this way to Vitest Pool Workers without wrangler file:

import {
    defineWorkersConfig,
    readD1Migrations
} from '@cloudflare/vitest-pool-workers/config'

export default defineWorkersConfig(async () => {
    const migrations = await readD1Migrations('./src/migrations')
    return {
        test: {
            globals: true,
            poolOptions: {
                workers: {
                    isolatedStorage: true,
                    miniflare: {
                        d1Databases: {
                            DB: 'db-tests'
                        },
                        bindings: {
                            TEST_MIGRATIONS: migrations
                        },
                        compatibilityDate: '2024-11-20',
                        compatibilityFlags: ['nodejs_compat']
                    }
                }
            }
        }
    }
})

import {
    defineWorkersConfig,
    readD1Migrations
} from '@cloudflare/vitest-pool-workers/config'

export default defineWorkersConfig(async () => {
    const migrations = await readD1Migrations('./src/migrations')
    return {
        test: {
            globals: true,
            poolOptions: {
                workers: {
                    isolatedStorage: true,
                    miniflare: {
                        d1Databases: {
                            DB: 'db-tests'
                        },
                        bindings: {
                            TEST_MIGRATIONS: migrations
                        },
                        compatibilityDate: '2024-11-20',
                        compatibilityFlags: ['nodejs_compat']
                    }
                }
            }
        }
    }
})

import {
    defineWorkersConfig,
    readD1Migrations
} from '@cloudflare/vitest-pool-workers/config'

export default defineWorkersConfig(async () => {
    const migrations = await readD1Migrations('./src/migrations')
    return {
        test: {
            globals: true,
            poolOptions: {
                workers: {
                    isolatedStorage: true,
                    miniflare: {
                        d1Databases: {
                            DB: 'db-tests'
                        },
                        bindings: {
                            TEST_MIGRATIONS: migrations
                        },
                        compatibilityDate: '2024-11-20',
                        compatibilityFlags: ['nodejs_compat']
                    }
                }
            }
        }
    }
})

import {
    defineWorkersConfig,
    readD1Migrations
} from '@cloudflare/vitest-pool-workers/config'

export default defineWorkersConfig(async () => {
    const migrations = await readD1Migrations('./src/migrations')
    return {
        test: {
            globals: true,
            poolOptions: {
                workers: {
                    isolatedStorage: true,
                    miniflare: {
                        d1Databases: {
                            DB: 'db-tests'
                        },
                        bindings: {
                            TEST_MIGRATIONS: migrations
                        },
                        compatibilityDate: '2024-11-20',
                        compatibilityFlags: ['nodejs_compat']
                    }
                }
            }
        }
    }
})

K

Kimitri•11/25/24, 11:44 AM

With this settings I can run Vitest pool workers both locally and with official cloudflare/wrangler-action@v3 using the precommands.
But I still had a problem, the deploy needs the wrangler.toml file to be executed, and to do that I decided generate this file dynamically in a step from deploy job, and injecting the resources ids with gitactions secrets, and this is the final workflow:

name: Deploy Cloudflare Workers

on:
  push:
    branches:
      - main
jobs:
  deploy:
    name: Deploy to Cloudflare Workers
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install pnpm
        uses: pnpm/action-setup@v4
        with:
          version: 9

      - name: Create wrangler.toml dynamically
        run: |
          cat <<EOF > wrangler.toml
          name = "${{ secrets.PROJECT_NAME }}"
          main = "src/index.ts"
          compatibility_date = "2024-11-20"
          compatibility_flags = ["nodejs_compat"]

          [[d1_databases]]
          binding = "DB"
          database_name = "${{ secrets.D1_DATABASE_NAME }}"
          database_id = "${{ secrets.D1_DATABASE_ID }}"
          migrations_dir = "./src/migrations"
          EOF

      - name: Run Tests, Migrations and Deploy using Cloudflare CLI environment
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          preCommands: |
            pnpm test 
            pnpm migration:prod

name: Deploy Cloudflare Workers

on:
  push:
    branches:
      - main
jobs:
  deploy:
    name: Deploy to Cloudflare Workers
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install pnpm
        uses: pnpm/action-setup@v4
        with:
          version: 9

      - name: Create wrangler.toml dynamically
        run: |
          cat <<EOF > wrangler.toml
          name = "${{ secrets.PROJECT_NAME }}"
          main = "src/index.ts"
          compatibility_date = "2024-11-20"
          compatibility_flags = ["nodejs_compat"]

          [[d1_databases]]
          binding = "DB"
          database_name = "${{ secrets.D1_DATABASE_NAME }}"
          database_id = "${{ secrets.D1_DATABASE_ID }}"
          migrations_dir = "./src/migrations"
          EOF

      - name: Run Tests, Migrations and Deploy using Cloudflare CLI environment
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          preCommands: |
            pnpm test 
            pnpm migration:prod

name: Deploy Cloudflare Workers

on:
  push:
    branches:
      - main
jobs:
  deploy:
    name: Deploy to Cloudflare Workers
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install pnpm
        uses: pnpm/action-setup@v4
        with:
          version: 9

      - name: Create wrangler.toml dynamically
        run: |
          cat <<EOF > wrangler.toml
          name = "${{ secrets.PROJECT_NAME }}"
          main = "src/index.ts"
          compatibility_date = "2024-11-20"
          compatibility_flags = ["nodejs_compat"]

          [[d1_databases]]
          binding = "DB"
          database_name = "${{ secrets.D1_DATABASE_NAME }}"
          database_id = "${{ secrets.D1_DATABASE_ID }}"
          migrations_dir = "./src/migrations"
          EOF

      - name: Run Tests, Migrations and Deploy using Cloudflare CLI environment
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          preCommands: |
            pnpm test 
            pnpm migration:prod

name: Deploy Cloudflare Workers

on:
  push:
    branches:
      - main
jobs:
  deploy:
    name: Deploy to Cloudflare Workers
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install pnpm
        uses: pnpm/action-setup@v4
        with:
          version: 9

      - name: Create wrangler.toml dynamically
        run: |
          cat <<EOF > wrangler.toml
          name = "${{ secrets.PROJECT_NAME }}"
          main = "src/index.ts"
          compatibility_date = "2024-11-20"
          compatibility_flags = ["nodejs_compat"]

          [[d1_databases]]
          binding = "DB"
          database_name = "${{ secrets.D1_DATABASE_NAME }}"
          database_id = "${{ secrets.D1_DATABASE_ID }}"
          migrations_dir = "./src/migrations"
          EOF

      - name: Run Tests, Migrations and Deploy using Cloudflare CLI environment
        uses: cloudflare/wrangler-action@v3
        with:
          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          preCommands: |
            pnpm test 
            pnpm migration:prod

if someone don't want expose the wrangler.toml file in the repository, this is the my way to do it. If you have some advice, please let me know.

-

-yko-•11/25/24, 4:30 PM

hi all, I hope this is the right channel for the question.
Q: I deploy code with wrangler. How do I correlate cloudflare deploy tag e.g.

1a9dcf7c

1a9dcf7c

1a9dcf7c

1a9dcf7c to a commit in my repo? Is there a standard way to do so?

Eelijah.01 Hi everyone! has somebody worked with nuxt ssr + nuxthub/core? The thing is, if ...

D

DaniFoldi•11/26/24, 1:42 PM

The fetch api in Workers does not support credentials, this is something that the nuxt/nuxthub people will have to fix on their end

D

dev•11/27/24, 12:20 AM

due to legal reasons, I have o deploy the same pages project to US and CANADA servers. The docs say that "--config string (not supported by Pages)". If I can't use different .toml files, how can I deploy the same code to different servers?

Ddev due to legal reasons, I have o deploy the same pages project to US and CANADA se...

I

Isaac McFadyen•11/27/24, 12:40 AM

Pages projects are automatically deployed globally - you don't get to choose where they are.

I

Isaac McFadyen•11/27/24, 12:41 AM

If your restrictions mandate you can only deploy to US/Canada then Pages isn't the right platform for you, unfortunately.

IIsaac McFadyen Pages projects are automatically deployed globally - you don't get to choose whe...

D

dev•11/27/24, 2:25 AM

I’ll have to check if we can get away with a region specific DB but still use pages..

N

naourass•11/27/24, 1:14 PM

Any specific version of Node.js you guys recommend when developing locally using Wrangler's

getPlatformProxy

getPlatformProxy

getPlatformProxy

getPlatformProxy and miniflare/workerd ?

Nnaourass Any specific version of Node.js you guys recommend when developing locally using...

J

James•11/27/24, 2:15 PM

>=18 should be good. I personally recommend latest LTS, which is currently 22.x

N

naourass•11/27/24, 4:51 PM

Looks like there's a timeout issue for the proxy process of D1 simulation in the latest versions of wrangler's

getPlatformProxy

getPlatformProxy

getPlatformProxy

getPlatformProxy:

const cfPlatformProxy = await getPlatformProxy();
const db = drizzle(cfPlatformProxy.env.DB);

// Do some a few seconds long computation here...

const res = await db.select().from(myTable);

const cfPlatformProxy = await getPlatformProxy();
const db = drizzle(cfPlatformProxy.env.DB);

// Do some a few seconds long computation here...

const res = await db.select().from(myTable);

const cfPlatformProxy = await getPlatformProxy();
const db = drizzle(cfPlatformProxy.env.DB);

// Do some a few seconds long computation here...

const res = await db.select().from(myTable);

const cfPlatformProxy = await getPlatformProxy();
const db = drizzle(cfPlatformProxy.env.DB);

// Do some a few seconds long computation here...

const res = await db.select().from(myTable);

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at D1PreparedQuery.get (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:223:16) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:529:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1400:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 57506,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1091,
      bytesRead: 1783105
    }
  }
}

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at D1PreparedQuery.get (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:223:16) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:529:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1400:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 57506,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1091,
      bytesRead: 1783105
    }
  }
}

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at D1PreparedQuery.get (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:223:16) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:529:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1400:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 57506,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1091,
      bytesRead: 1783105
    }
  }
}

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at D1PreparedQuery.get (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:223:16) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:529:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1400:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 57506,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1091,
      bytesRead: 1783105
    }
  }
}

Is there some way to make the proxy process persist till I call cfPlatformProxy.dispose(), or should I just recreate the proxy process each time using getPlatformProxy() after a long computation as a workaround for now?

N

naourass•11/27/24, 5:43 PM

BTW this error wasn't happening in the previous versions of wrangler before the 2 or 3 latest updates.

N

naourass•11/28/24, 11:49 AM

Not sure why but looks like this workaround helped bypass that error (recalling

drizzle(db)

drizzle(db)

drizzle(db)

drizzle(db) and waiting for ~1sec):

const cfPlatformProxy = await getPlatformProxy();
let db = drizzle(cfPlatformProxy.env.DB);

// Do some a few seconds long computation here...

db = drizzle(cfPlatformProxy.env.DB);
await new Promise(resolve => setTimeout(resolve, 1500));

const res = await db.select().from(myTable);

const cfPlatformProxy = await getPlatformProxy();
let db = drizzle(cfPlatformProxy.env.DB);

// Do some a few seconds long computation here...

db = drizzle(cfPlatformProxy.env.DB);
await new Promise(resolve => setTimeout(resolve, 1500));

const res = await db.select().from(myTable);

const cfPlatformProxy = await getPlatformProxy();
let db = drizzle(cfPlatformProxy.env.DB);

// Do some a few seconds long computation here...

db = drizzle(cfPlatformProxy.env.DB);
await new Promise(resolve => setTimeout(resolve, 1500));

const res = await db.select().from(myTable);

const cfPlatformProxy = await getPlatformProxy();
let db = drizzle(cfPlatformProxy.env.DB);

// Do some a few seconds long computation here...

db = drizzle(cfPlatformProxy.env.DB);
await new Promise(resolve => setTimeout(resolve, 1500));

const res = await db.select().from(myTable);

W

Walshy•11/28/24, 11:50 PM

can you expand? logs?

W

Walshy•11/29/24, 12:16 AM

Your custom build command is an npm script which runs wrangler build... which then triggers the custom build command and there's the loop

W

Walshy•11/29/24, 12:17 AM

Custom build command is for like your own handling of esbuild. I'd recommend just running your dry run as part of some npm script

J

James•11/29/24, 12:23 AM

Has anyone seen a case where bindings to D1 or DO don't work when running wrangler with --test-scheduled flag? I get silent failures when trying to access D1 or D0 in either case, only locally with cron tasks on a worker. But the same worker codebase runs fine with the bindings when I run it as a regular worker for both fetch or queue incoming requests.

I've tested this at its most raw level. When I run the cron task locally, it starts fine, runs fine until I use either binding. Even for a basic statement such as:
await env.BINDING.exec("select * from users");

Fails silently with or without debugging on. I tested, and the --persist-to is set correctly, where I have a shared folder for D1/DO storage.

Again, this worker access all bindings fine running under the queue/fetch context, just not when running --test-scheduled

JJames Has anyone seen a case where bindings to D1 or DO don't work when running wrangl...

J

James•11/29/24, 3:08 PM

Tried reinstalling and upgrading wrangler, no dice. My Hacky workaround is to call the same code from a queue message instead of the cron simulator.

Sounds like a wrangler bug.

V

Vero•11/29/24, 4:04 PM

Hey all! Just a heads-up: we’re changing the format of the @Wrangler office hours. Going forward, instead of a call, the Wrangler team will answer your questions directly in this channel during the event.
https://discord.gg/cloudflaredev?event=1303336766237048853

M

mani123•11/29/24, 4:10 PM

hi all, im can use WasmJs from Kotlin in Wrangler?

Mmani123 hi all, im can use WasmJs from Kotlin in Wrangler?

M

mani123•11/29/24, 5:50 PM

https://github.com/bashor/kotlin-worker-hello-world/tree/master

GitHub

GitHub - bashor/kotlin-worker-hello-world

Contribute to bashor/kotlin-worker-hello-world development by creating an account on GitHub.

N

neoney•11/29/24, 10:03 PM

im running

wrangler dev

wrangler dev

wrangler dev

wrangler dev on a worker and I can't access the bindings made from anotehr worker

N

neoney•11/29/24, 10:03 PM

http://localhost:6284/workers

N

neoney•11/29/24, 10:03 PM

is unable to connect

N

neoney•11/29/24, 10:05 PM

N

neoney•11/29/24, 10:14 PM

now i get this

N

neoney•11/29/24, 10:15 PM

its supposed to be a http binding

N

neoney•11/29/24, 10:16 PM

ok i fixed it, turns out if you log the binding it errors but it works fine

C

Constantin•11/30/24, 12:05 PM

any ideea how build variables like

CF_PAGES_COMMIT_SHA

CF_PAGES_COMMIT_SHA

CF_PAGES_COMMIT_SHA

CF_PAGES_COMMIT_SHA and

CF_PAGES_BRANCH

CF_PAGES_BRANCH

CF_PAGES_BRANCH

CF_PAGES_BRANCH can be extracted in the qwik framework?

having them like:

export const useServerTimeLoader = routeLoader$(async ({ env }) => {
  return {
    date: new Date().toISOString(),
    commit: env.get("CF_PAGES_COMMIT_SHA"),
    branch: env.get("CF_PAGES_BRANCH"),
  };
});

export const useServerTimeLoader = routeLoader$(async ({ env }) => {
  return {
    date: new Date().toISOString(),
    commit: env.get("CF_PAGES_COMMIT_SHA"),
    branch: env.get("CF_PAGES_BRANCH"),
  };
});

export const useServerTimeLoader = routeLoader$(async ({ env }) => {
  return {
    date: new Date().toISOString(),
    commit: env.get("CF_PAGES_COMMIT_SHA"),
    branch: env.get("CF_PAGES_BRANCH"),
  };
});

export const useServerTimeLoader = routeLoader$(async ({ env }) => {
  return {
    date: new Date().toISOString(),
    commit: env.get("CF_PAGES_COMMIT_SHA"),
    branch: env.get("CF_PAGES_BRANCH"),
  };
});

is not working

C

Constantin•11/30/24, 1:46 PM

does CF_PAGES_COMMIT_SHA and CF_PAGES_BRANCH are missing from workers ? (i'm using the new git integration)

W

Walshy•11/30/24, 4:27 PM

no, the id is not private

hi guys, silly question from a newbie here, I am getting starting with wrangler and I learned how to

Similar Threads