I have tried with VPNs and seems like fixed

Y

yigitOP•5/20/23, 10:23 PM

yeap guys, this issue only affects my IP, totally weird.

Yyigit ta-daa

Y

yigitOP•5/20/23, 10:24 PM

the weirdest part is that, it only happens in Portugal - when I use VPN and go another location, it works. but all Portugal IPs in ProtonVPN, it returns same error

Yyigit I have tried with VPNs and seems like fixed

H

Hello, I’m Allie!•5/20/23, 10:24 PM

Depending on what your Worker is doing, it might be an edge case to do with your colo(or something else), that causes an infinite loop. If you are able to give us some insight into what your code is doing(or a repo if you got one), then we might be able to help you.

HHello, I’m Allie!Depending on what your Worker is doing, it might be an edge case to do with your...

Y

yigitOP•5/20/23, 10:24 PM

actually nothing, ordinary use of Zaraz + Cloudflare Pages - and not having any custom Workers, just using CF services with Workers

Yyigit actually nothing, ordinary use of Zaraz + Cloudflare Pages - and not having any ...

H

Hello, I’m Allie!•5/20/23, 10:27 PM

Just a full static site with Zaraz, is that what you mean?

Y

yigitOP•5/20/23, 10:27 PM

yes, it is

H

Hello, I’m Allie!•5/20/23, 10:27 PM

Hm…

H

Hello, I’m Allie!•5/20/23, 10:28 PM

I’ll try to see if there is something I can do…

Y

yigitOP•5/20/23, 10:28 PM

To me, it appears that the problem is fixed. However, if the continuous ban persists in Portugal, then the issue may recur. In such a case, the problem will likely be resolved automatically in due time.

HHello, I’m Allie!I’ll try to see if there is something I can do…

Y

yigitOP•5/20/23, 10:28 PM

thanks a lot for your close interest

don't forget to check from Portugal based IP

Yyigit thanks a lot for your close interest 🙏🏽 don't forget to check from Portugal ba...

H

Hello, I’m Allie!•5/20/23, 10:29 PM

Yup, I see it borks in Lisboa

M

matt•5/21/23, 1:56 AM

has anyone managed to get itty-router v4 types working with cloudflare's worker types? the main issue appears to be that both libraries have bespoke typings for

Request

Request

and

Response

Response

I

Ian•5/21/23, 11:46 AM

Hi guys, what is the best for simply "counting requests per user", I am have a hard time on the economics because each time a user does something a write request has to be made even just for logging, the cheapest write request is on durable objects but it still costs 1$/1M sweatguy

Z

zegevlier•5/21/23, 11:48 AM

Could #analytics-engine-beta work for your usecase?

Z

zegevlier•5/21/23, 11:49 AM

Otherwise, Durable Objects are the only thing that CF had that is really meant for strongly consistent counting

Zzegevlier Could #analytics-engine-beta work for your usecase?

I

Ian•5/21/23, 11:51 AM

It indeed does help, I am just worried because it is on beta and no pricing is available

I

Ian•5/21/23, 11:51 AM

Thanks tho

Z

zegevlier•5/21/23, 12:02 PM

That's very understandable. There was some discussion in that channel about how pricing might work but AFAIK nothing is firm on that yet

Zzegevlier That's very understandable. There was some discussion in that channel about how ...

I

Ian•5/21/23, 12:15 PM

i am not sure if I should bet on it tbh, if such a product exists for the purpose of usage-based-billing (this is what says in the docs for one of the usages apparently), it should have a much lower price if we compare it to existing storage options thonk

I

Ian•5/21/23, 12:15 PM

But then people may abuse it

S

sakuta•5/21/23, 3:30 PM

are there already type declarations for the TCP socket api?

K

kian•5/21/23, 3:51 PM

there should be

K

kian•5/21/23, 3:51 PM

not sure why there hasn't been a release

K

kian•5/21/23, 3:51 PM

K

kian•5/21/23, 3:51 PM

it's under the alpha tag for whatever reason

K

kian•5/21/23, 3:51 PM

declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}

declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}

declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}

declare module "cloudflare:sockets" {
  function _connect(
    address: string | SocketAddress,
    options?: SocketOptions
  ): Socket;
  export { _connect as connect };
}

M

Murder Chicken•5/21/23, 5:23 PM

Any reason why when upgrading to Wrangler 3 and using the latest

compatibility_date

compatibility_date

why creating new Request objects would result in an empty object? Using module syntax, trying to create any new requests from within a module results in

{}

{}

when outputting it to console even with

console.log(JSON.stringify(req))

console.log(JSON.stringify(req))

... bit stumped as this was working just fine before I tried migrating things to Wrangler v3 and updated my

compatibility_date

compatibility_date

... any ideas?

This is being done to create new Requests with custom cookies attached to pull information from an external website.

M

Murder Chicken•5/21/23, 5:26 PM

Any easy way to inspect the Request object created? Suddenly, this block of code (where

requests

requests

is an array of Request objects)...

const responseData = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))

const responseData = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))

... no longer works resulting in this error...

Cannot read properties of undefined (reading 'map')
TypeError: Cannot read properties of undefined (reading 'forEach')

Cannot read properties of undefined (reading 'map')
TypeError: Cannot read properties of undefined (reading 'forEach')

Which has me baffled... trying to figure out where it's failing.

M

Murder Chicken•5/21/23, 5:28 PM

Yeah, just realized it's incomplete, one sec.

M

Murder Chicken•5/21/23, 5:34 PM

export async function example() {
  const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
  let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
  let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
  let data = responses.map(response => processResponse(response['records']))
  let records = data.flat(3)
  records.forEach(a => {
    // Failure is this forEach
  })
}

export async function example() {
  const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
  let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
  let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
  let data = responses.map(response => processResponse(response['records']))
  let records = data.flat(3)
  records.forEach(a => {
    // Failure is this forEach
  })
}

export async function example() {
  const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
  let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
  let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
  let data = responses.map(response => processResponse(response['records']))
  let records = data.flat(3)
  records.forEach(a => {
    // Failure is this forEach
  })
}

export async function example() {
  const endpoints = generateEndpoints() // returns a simple array of string URLs to fetch
  let requests = endpoints.map(endpoint => new Request(endpoint, { headers: { cookie } }))
  let responses = await Promise.all(requests.map(request => fetch(request).then(r => r.json())))
  let data = responses.map(response => processResponse(response['records']))
  let records = data.flat(3)
  records.forEach(a => {
    // Failure is this forEach
  })
}

M

Murder Chicken•5/21/23, 5:36 PM

I think I got it.

M

Murder Chicken•5/21/23, 5:37 PM

Looks like the response changed and I failed to check for a data structure update in the response.

M

Murder Chicken•5/21/23, 5:38 PM

I'm good! Thanks for responding so quickly @skye_31 (as always)

M

Murder Chicken•5/21/23, 5:40 PM

hahaha, all good. I have to comment on how much I appreciate that you're always immediately responding to questions. Learning the platform can be difficult at times but you're constantly out there answering questions and assisting. It's really helpful.

M

Murder Chicken•5/21/23, 6:28 PM

Is it possible to trigger a worker

scheduledEvent

scheduledEvent

from a development environment similar to the

--test-scheduled

--test-scheduled

flag and hitting the

__scheduled

__scheduled

route locally?

J

James•5/21/23, 6:36 PM

In dev, miniflare used to support hitting

/cdn-cgi/mf/scheduled

/cdn-cgi/mf/scheduled

/cdn-cgi/mf/scheduled

/cdn-cgi/mf/scheduled but I don't believe that's a thing anymore with v3 unfortunately.

D

DaniFoldi•5/21/23, 6:38 PM

it'll be reimplemented in v3 soon

M

Murder Chicken•5/21/23, 7:02 PM

locally in v3, it works fine, just add the

--test-scheduled

--test-scheduled

flag and hit the

__scheduled

__scheduled

route at the root of the domain. but once it's pushed to a development environment in CF, you have to wait for the event to trigger so I was hoping we could somehow trigger it manually.

L

lily•5/21/23, 8:06 PM

with the new TCP connections thing, i'm wondering if it would make sense to keep a postgres connection alive in a durable object as to not have to spin a new one for every worker run?

L

lily•5/21/23, 8:07 PM

i havent worked with DOs before but this kinda seems like something it would be good for

J

James•5/21/23, 8:07 PM

Yep that would make a lot of sense to me

.

. Arbitration and Class Action W•5/22/23, 3:51 AM

i made my website anti ddos
i added a lot of rules
is there a way i can copy the cloudflare rules
onto another website of mine?

S

Supa Safe•5/22/23, 3:55 AM

Hi folks, I bought a domain name from cloudflare this month, and use pages to host my web site, it's awseome!

I'm now learning how to use WASM as serverless solution, and found that cloudflare supports Wasm now: https://developers.cloudflare.com/workers/platform/web-assembly/

Just out of curiosity, does any one what's the different of the Wasm solution between fastly and CF? I mean, it would be better to describe the difference in high level, I wanna to to convince my boss to use one of it:
https://www.fastly.com/blog/unlocking-real-time-at-the-edge

WebAssembly (Wasm) · Cloudflare Workers docs

WebAssembly (abbreviated Wasm) allows you to compile languages like Rust, Go, or C to a binary format that can run in a wide variety of environments, …

Unlocking Real-Time at the Edge

We are excited to announce that we have made big strides integrating Fanout into Fastly. We recently announced that Fastly has acquired Fanout in order to unlock real-time web features on our scalable, WASM-based Compute@Edge, our serverless compute offering. Our first step was to add WebSockets support to our Compute@Edge platform.

M

matt•5/22/23, 5:01 AM

Is bunnynet a good tool to use if I want to test global latency into my cloudflare workers?

WWalshy Not possible, I need to see how we go about making that available

A

Alaanor•5/22/23, 9:01 AM

Is it now possible to have logpush enable for page's worker ?

.. Arbitration and Class Action W i made my website anti ddos i added a lot of rules is there a way i can copy the...

I

Isaac McFadyen•5/22/23, 11:55 AM

Please don't cross-post across channels.

E

Elie Zedeck R.•5/22/23, 12:26 PM

Hi guys, I'm developing 2 workers for the same project/account, in a Service Binding fashion. When deployed, the workers A is successfully able to call B. But locally, the Service Binding is actually

undefined

undefined

. Anyone can help? I have no idea why it can't see each other when running locally.

This is my env during dev, for Workers A (caller):

[env.dev]
vars = { ENVIRONMENT = "dev", ENV = "dev" }
services = [
  { binding = "SERVICES", service = "workers-services", environment = "dev" }
]

[env.dev]
vars = { ENVIRONMENT = "dev", ENV = "dev" }
services = [
  { binding = "SERVICES", service = "workers-services", environment = "dev" }
]

[env.dev]
vars = { ENVIRONMENT = "dev", ENV = "dev" }
services = [
  { binding = "SERVICES", service = "workers-services", environment = "dev" }
]

[env.dev]
vars = { ENVIRONMENT = "dev", ENV = "dev" }
services = [
  { binding = "SERVICES", service = "workers-services", environment = "dev" }
]

And this is for Workers B (being called):

[env.dev]
name = "workers-services"
vars = { ENVIRONMENT = "dev", ENV = "dev" }

[env.dev]
name = "workers-services"
vars = { ENVIRONMENT = "dev", ENV = "dev" }

[env.dev]
name = "workers-services"
vars = { ENVIRONMENT = "dev", ENV = "dev" }

[env.dev]
name = "workers-services"
vars = { ENVIRONMENT = "dev", ENV = "dev" }

When I run with

--remote

--remote

--remote

--remote (using Wrangler v3.0.0), I get this error: text: 'workers.api.error.service_binding_env_error: could not resolve binding "SERVICES":
environment "dev" not found for service "workers-services" [code: 10144]'

These are however separate project, one is Bundled (A) and one is Unbound (B). One is nodejs compat (B), one is not (A).

I have tried with VPNs and seems like fixed

Similar Threads

Similar Threads

Similar Threads