For ingress?

K

Kimitri•6/28/24, 8:47 PM

no, I'm trying to run wrangler locally and it's getting an error, I just did exactly like the documentation says to start a project "npm create hono@latest" but when I run "npm run dev" I get this error

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
from this
my-app\node_modules\wrangler\wrangler-dist\cli.js:29747
throw a;
^
and searching on google and in this community I found may be the wrangler needs certification to run locally

C

ccostes•6/28/24, 8:54 PM

Also unable to run pages (remix framework created with

create-cloudflare

create-cloudflare

) with wrangler locally (not sure why it thinks the address in use - it's not)

 ⛅️ wrangler 3.62.0
-------------------

✨ Compiled Worker successfully
✘ [ERROR] Address already in use (127.0.0.1:8788). Please check that you are not already running a server on this address or specify a different port with --port.

[wrangler:inf] Ready on http://localhost:53635
⎔ Starting local server...
/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/wrangler/wrangler-dist/cli.js:29747
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:9161:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v21.5.0

 ⛅️ wrangler 3.62.0
-------------------

✨ Compiled Worker successfully
✘ [ERROR] Address already in use (127.0.0.1:8788). Please check that you are not already running a server on this address or specify a different port with --port.

[wrangler:inf] Ready on http://localhost:53635
⎔ Starting local server...
/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/wrangler/wrangler-dist/cli.js:29747
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:9161:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v21.5.0

 ⛅️ wrangler 3.62.0
-------------------

✨ Compiled Worker successfully
✘ [ERROR] Address already in use (127.0.0.1:8788). Please check that you are not already running a server on this address or specify a different port with --port.

[wrangler:inf] Ready on http://localhost:53635
⎔ Starting local server...
/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/wrangler/wrangler-dist/cli.js:29747
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:9161:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v21.5.0

 ⛅️ wrangler 3.62.0
-------------------

✨ Compiled Worker successfully
✘ [ERROR] Address already in use (127.0.0.1:8788). Please check that you are not already running a server on this address or specify a different port with --port.

[wrangler:inf] Ready on http://localhost:53635
⎔ Starting local server...
/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/wrangler/wrangler-dist/cli.js:29747
            throw a;
            ^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
    at #assembleAndUpdateConfig (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:9161:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Mutex.runWith (/Users/ccostes/dev/onecall-cloudflare/frontend/node_modules/miniflare/dist/src/index.js:3521:16) {
  code: 'ERR_RUNTIME_FAILURE',
  cause: undefined
}

Node.js v21.5.0

KKimitri no, I'm trying to run wrangler locally and it's getting an error, I just did exa...

H

Hello, I’m Allie!OP•6/28/24, 9:47 PM

That sounds like something else…

H

Hello, I’m Allie!OP•6/28/24, 9:48 PM

Did you try again?

HHello, I’m Allie!Did you try again?

K

Kimitri•6/29/24, 3:14 AM

yes, I retry all process since run npm create hono@latest again, and still getting the error, I don't know if this happens because I choose the option to don't send metrics to cloudflare, is it forced required?

K

Kimitri•6/29/24, 3:33 AM

and I'm o Windows

HHello, I’m Allie!Did you try again?

K

Kimitri•6/29/24, 3:38 AM

one question, to run Hono I need to install bun? Because I just installed Node, not even Bun

K

Kimitri•6/29/24, 5:27 AM

I'm really frustrated about honor, I don't know what I'm doing wrong, I literally just did everything that documentation from this page says
https://hono.dev/docs/getting-started/cloudflare-workers

and still not working locally, just work when I deploy it, I tried even dockerize it using the dockerfile exemplo provided by documentation and not worked. I don't know if it is because I'm using windows, or something wrong

Cloudflare Workers - Hono

Ultrafast web framework for Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Node.js, and others. Fast, but not only fast.

KKimitri one question, to run Hono I need to install bun? Because I just installed Node, ...

H

Hello, I’m Allie!OP•6/29/24, 8:10 AM

No, you don’t need bun.

K

Kimitri•6/29/24, 12:25 PM

I finally fixed the issue, the problem is with version 3.62.0 from wrangler, I downgrade it to 3.61.0 and the problem was fixed.

PPorush Manjhi How can I edit wrangler's ```https://github.com/cloudflare/workers-sdk/blob/main...

H

Hello, I’m Allie!OP•6/30/24, 1:26 PM

It gets bundled. You would need to clone the repo, make your change, then rebuild

N

Nima•6/30/24, 2:39 PM

How do i fix this error, isolated it to a new project and the problem persists (nothing to do with the code, e.g npx create-cloudflare@latest):

npm run dev

dev
wrangler dev

wrangler 3.62.0
-------------------

⎔ Starting local server...
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ [b] open a browser, [d] open Devtools, [l] turn off local mode, [c] clear console, [x] to exit │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
C:...\test-wrangler\jolly-pine-7ab4\node_modules\wrangler\wrangler-dist\cli.js:29747
throw a;
^

MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
at #assembleAndUpdateConfig (C:...\test-wrangler\jolly-pine-7ab4\node_modules\miniflare\dist\src\index.js:9161:13)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Mutex.runWith (C:...\test-wrangler\jolly-pine-7ab4\node_modules\miniflare\dist\src\index.js:3521:16) {
code: 'ERR_RUNTIME_FAILURE',
cause: undefined
}

Node.js v22.3.0

https://github.com/cloudflare/workers-sdk/issues/6170#issuecomment-2198662368

GitHub

🐛 BUG: Received structured exception #0xc0000005: access violation;...

Which Cloudflare product(s) does this pertain to? Miniflare What version(s) of the tool(s) are you using? 3.20240620.0 [Miniflare] What version of Node are you using? 22.3.0 What operating system a...

KKimitri I finally fixed the issue, the problem is with version 3.62.0 from wrangler, I d...

M

Mayuresh Choudhary•7/1/24, 5:18 AM

Yeah I did the same last night and it worked the issue is with the latest version of Wrangler (i.e 3.62.0)

NNima How do i fix this error, isolated it to a new project and the problem persists (...

M

Mayuresh Choudhary•7/1/24, 5:20 AM

downgrade the version of Wrangler to 3.61.0 or less
and directly use "wrangler dev" command

MMayuresh Choudhary downgrade the version of Wrangler to 3.61.0 or less and directly use "wrangler ...

N

Nima•7/1/24, 8:14 AM

Ty

V

Vero•7/1/24, 3:15 PM

Hellooo devs. See you July 1, 2024 for our @Wrangler office hours
https://discord.gg/cloudflaredev?event=1255538131910787134

A

AteMyCats•7/1/24, 3:18 PM

bro why ping

A

AteMyCats•7/1/24, 3:18 PM

u eoke me up

A

AteMyCats•7/1/24, 3:18 PM

meanie

Z

ZachHandley•7/1/24, 3:32 PM

lol take away the wrangler role yeah

T

Tin Cap•7/1/24, 4:02 PM

Why did I get invited into that with a notification?

T

Tin Cap•7/1/24, 4:55 PM

Been in this discord for a few years. Never got a notification that opened a live chat before.

R

Ruxorly•7/1/24, 5:32 PM

probably update

A

Aditya Mathur•7/1/24, 6:43 PM

Hello! I am using

WorkerKV

WorkerKV

for some experiment and this is my code

await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
  expiration: Math.floor(payload.resetTime.getTime() / 1000),
});

await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
  expiration: Math.floor(payload.resetTime.getTime() / 1000),
});

await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
  expiration: Math.floor(payload.resetTime.getTime() / 1000),
});

await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
  expiration: Math.floor(payload.resetTime.getTime() / 1000),
});

So here are the problems I am facing -

The key is not getting deleted, I am still getting the old value when I fetch it
If I want to update the value for a key but still want to have the same expiration time, what will be implmentation for that? Should I just pass the
```
expiration
```
```
expiration
```
props again?

AAditya Mathur Hello! I am using `WorkerKV` for some experiment and this is my code ```ts awai...

H

Hello, I’m Allie!OP•7/1/24, 6:47 PM

Does it expire after a minute or so?
And yes, on your second one

HHello, I’m Allie!Does it expire after a minute or so? And yes, on your second one

A

Aditya Mathur•7/1/24, 6:52 PM

A

Aditya Mathur•7/1/24, 6:53 PM

Here is the code -

async increment(key: string): Promise<ClientRateLimitInfo> {
    const keyWithPrefix = this.prefixKey(key);
    // @ts-ignore
    let payload: Required<ClientRateLimitInfo> = await this.namespace.get<Required<ClientRateLimitInfo>>(
      keyWithPrefix,
      "json",
    );

    const wasCreated = payload != null

    if (wasCreated) payload = {
      totalHits: payload.totalHits + 1,
      resetTime: new Date(payload.resetTime),
    };
    else
      payload = {
        totalHits: 1,
        resetTime: new Date(Date.now() + this.windowMs),
      };

    console.log("Payload - ", payload, " Expire - ", payload.resetTime.toLocaleString(), " Current - ", new Date().toLocaleString())

    await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
      expiration: !wasCreated ? Math.floor(payload.resetTime.getTime() / 1000) : undefined,
      // expirationTtl: this.windowMs
    });

    return payload;
  }

async increment(key: string): Promise<ClientRateLimitInfo> {
    const keyWithPrefix = this.prefixKey(key);
    // @ts-ignore
    let payload: Required<ClientRateLimitInfo> = await this.namespace.get<Required<ClientRateLimitInfo>>(
      keyWithPrefix,
      "json",
    );

    const wasCreated = payload != null

    if (wasCreated) payload = {
      totalHits: payload.totalHits + 1,
      resetTime: new Date(payload.resetTime),
    };
    else
      payload = {
        totalHits: 1,
        resetTime: new Date(Date.now() + this.windowMs),
      };

    console.log("Payload - ", payload, " Expire - ", payload.resetTime.toLocaleString(), " Current - ", new Date().toLocaleString())

    await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
      expiration: !wasCreated ? Math.floor(payload.resetTime.getTime() / 1000) : undefined,
      // expirationTtl: this.windowMs
    });

    return payload;
  }

async increment(key: string): Promise<ClientRateLimitInfo> {
    const keyWithPrefix = this.prefixKey(key);
    // @ts-ignore
    let payload: Required<ClientRateLimitInfo> = await this.namespace.get<Required<ClientRateLimitInfo>>(
      keyWithPrefix,
      "json",
    );

    const wasCreated = payload != null

    if (wasCreated) payload = {
      totalHits: payload.totalHits + 1,
      resetTime: new Date(payload.resetTime),
    };
    else
      payload = {
        totalHits: 1,
        resetTime: new Date(Date.now() + this.windowMs),
      };

    console.log("Payload - ", payload, " Expire - ", payload.resetTime.toLocaleString(), " Current - ", new Date().toLocaleString())

    await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
      expiration: !wasCreated ? Math.floor(payload.resetTime.getTime() / 1000) : undefined,
      // expirationTtl: this.windowMs
    });

    return payload;
  }

async increment(key: string): Promise<ClientRateLimitInfo> {
    const keyWithPrefix = this.prefixKey(key);
    // @ts-ignore
    let payload: Required<ClientRateLimitInfo> = await this.namespace.get<Required<ClientRateLimitInfo>>(
      keyWithPrefix,
      "json",
    );

    const wasCreated = payload != null

    if (wasCreated) payload = {
      totalHits: payload.totalHits + 1,
      resetTime: new Date(payload.resetTime),
    };
    else
      payload = {
        totalHits: 1,
        resetTime: new Date(Date.now() + this.windowMs),
      };

    console.log("Payload - ", payload, " Expire - ", payload.resetTime.toLocaleString(), " Current - ", new Date().toLocaleString())

    await this.namespace.put(keyWithPrefix, JSON.stringify(payload), {
      expiration: !wasCreated ? Math.floor(payload.resetTime.getTime() / 1000) : undefined,
      // expirationTtl: this.windowMs
    });

    return payload;
  }

A

Aditya Mathur•7/1/24, 6:54 PM

this.windowMs = 60_000 // 1 minute

this.windowMs = 60_000 // 1 minute

AAditya Mathur Here is the code - ```ts async increment(key: string): Promise<ClientRateLimitIn...

A

Aditya Mathur•7/2/24, 3:26 AM

Hey @Hello, I’m Allie!, do you know what am I doing wrong?

AAditya Mathur Hey @Hello, I’m Allie!, do you know what am I doing wrong?

I

Ian•7/2/24, 3:33 AM

was it the if statement?

IIan was it the if statement?

A

Aditya Mathur•7/2/24, 3:37 AM

?

I

Ian•7/2/24, 3:37 AM

by the way, you'd be better served using a ternary instead of an if statement since a ternary always assigns something.

const payload = wasCreated
  ? {
      totalHits: payload.totalHits + 1,
      resetTime: new Date(payload.resetTime)
    }
  : {
       totalHits: 1,
       resetTime: new Date(Date.now() + this.windowMs),
    }

const payload = wasCreated
  ? {
      totalHits: payload.totalHits + 1,
      resetTime: new Date(payload.resetTime)
    }
  : {
       totalHits: 1,
       resetTime: new Date(Date.now() + this.windowMs),
    }

const payload = wasCreated
  ? {
      totalHits: payload.totalHits + 1,
      resetTime: new Date(payload.resetTime)
    }
  : {
       totalHits: 1,
       resetTime: new Date(Date.now() + this.windowMs),
    }

const payload = wasCreated
  ? {
      totalHits: payload.totalHits + 1,
      resetTime: new Date(payload.resetTime)
    }
  : {
       totalHits: 1,
       resetTime: new Date(Date.now() + this.windowMs),
    }

Now payload is always assigned a value

AAditya Mathur ?

I

Ian•7/2/24, 3:37 AM

Oh I see, you were asking for help. I thought you were saying you figured it out and wanted to let @Hello, I’m Allie! know how you fixed it.

I

Ian•7/2/24, 3:38 AM

I think your problem is your if statement. It has a semicolon before the

else

else

clause. Try the following

I

Ian•7/2/24, 3:39 AM

if (wasCreated) {
  payload = {
    totalHits: payload.totalHits + 1,
    resetTime: new Date(payload.resetTime),
  }; // <-- semicolon here
} else {  // <-- not here
  payload = {
    totalHits: 1,
    resetTime: new Date(Date.now() + this.windowMs),
  };
}

if (wasCreated) {
  payload = {
    totalHits: payload.totalHits + 1,
    resetTime: new Date(payload.resetTime),
  }; // <-- semicolon here
} else {  // <-- not here
  payload = {
    totalHits: 1,
    resetTime: new Date(Date.now() + this.windowMs),
  };
}

if (wasCreated) {
  payload = {
    totalHits: payload.totalHits + 1,
    resetTime: new Date(payload.resetTime),
  }; // <-- semicolon here
} else {  // <-- not here
  payload = {
    totalHits: 1,
    resetTime: new Date(Date.now() + this.windowMs),
  };
}

if (wasCreated) {
  payload = {
    totalHits: payload.totalHits + 1,
    resetTime: new Date(payload.resetTime),
  }; // <-- semicolon here
} else {  // <-- not here
  payload = {
    totalHits: 1,
    resetTime: new Date(Date.now() + this.windowMs),
  };
}

IIan I think your problem is your if statement. It has a semicolon before the `else` ...

A

Aditya Mathur•7/2/24, 3:40 AM

I don't think so, but just give me a sec let me try

I

Ian•7/2/24, 3:40 AM

even if it's somehow valid syntax, it's a very odd way of doing an if/else

IIan even if it's somehow valid syntax, it's a very odd way of doing an if/else

A

Aditya Mathur•7/2/24, 3:43 AM

Yeah, I was just prototyping, so was not really looking into making it look good. But you are right about that, it does look odd

IIan even if it's somehow valid syntax, it's a very odd way of doing an if/else

A

Aditya Mathur•7/2/24, 3:46 AM

Nope, this was not it.

AAditya Mathur Hello! I am using `WorkerKV` for some experiment and this is my code ```ts awai...

A

Aditya Mathur•7/2/24, 3:52 AM

Hey @Community Champion guys, sorry for pinning you like this but I am stuck on this for a week. Does anyone knows what is wrong in this?

A

andrew_nyr•7/2/24, 4:00 AM

?pings

F

Flare•7/2/24, 4:00 AM

Please do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.

A

Aditya Mathur•7/2/24, 4:20 AM

okay

I

Ian•7/2/24, 5:07 AM

@Aditya Mathur are you sure you meant to use

expiration

expiration

(seconds since the epoch) or

expirationTtl

expirationTtl

(seconds from now) ? Because I saw your

this.windowMs = 60_000 // 1 minute

this.windowMs = 60_000 // 1 minute

comment, but you also have

expirationTtl: this.windowMs

expirationTtl: this.windowMs

and that would be wrong; it would be 60000 seconds.

IIan @Aditya Mathur are you sure you meant to use `expiration` (seconds since the epo...

A

Aditya Mathur•7/2/24, 5:13 AM

Yeah, you are right about that but it is commented, so it is not getting executed. This is a rate limiter, so the problem is every time a user requests the server I have to update the

totalHits

totalHits

but the expiration time remains that same, thats why it is stored in

resetTime

resetTime

. So when I am updating it, I am passing the

expiration

expiration

again.

I

Ian•7/2/24, 5:14 AM

In the docs

As of January 2022, expiration targets that are less than 60 seconds into the future are not supported. This is true for both expiration methods.

I

Ian•7/2/24, 5:16 AM

@Aditya Mathur when you read the KV, doesn't it also contain the

expiration

expiration

attribute?

Similar Threads

Similar Threads

Similar Threads