I'm not a Cloudflare employee, but a community member simply passing along the information as I rece

I'm not a Cloudflare employee, but a community member simply passing along the information as I receive it. I understand this is frustrating, and only apologise for that. For us to escalate issues, we have to see it impacting multiple users, and until very recently, we did not have many reports of this. Once we did, it was escalated, and we got confirmation within minutes which was then relayed to you.

JamesOP•7/28/23, 1:41 PM

I'm sure we'll get an update on the status page soon. Thanks for your patience.

JamesOP•7/28/23, 1:42 PM

https://www.cloudflarestatus.com/incidents/03vm5mx76pc6 has now been updated to include a note about this:

Cloudflare API in Pages Functions may also have been affected returning intermittent 500 errors.

A fix has been implemented and we are monitoring the results.

JJames I'm not a Cloudflare employee, but a community member simply passing along the i...

JSON•7/28/23, 1:44 PM

I think I misunderstood because you gave me the answer like an employee I'm sorry.
But why do you say sorry when you're not an employee? The front and the back are a bit weird?

JJSON I think I misunderstood because you gave me the answer like an employee I'm sorr...

JamesOP•7/28/23, 1:48 PM

I still feel bad when people have issues, having experienced things like this myself

Just trying to empathise with your situation - sorry for any confusion.

JamesOP•7/28/23, 1:49 PM

It sounds like a fix is rolling out though, so hopefully you won't be seeing issues for much longer!

Erisa•7/28/23, 1:49 PM

A note was added to https://www.cloudflarestatus.com/incidents/03vm5mx76pc6

Cloudflare API in Pages Functions may also have been affected returning intermittent 500 errors.

A fix has been implemented and we are monitoring the results.

EErisa A note was added to <https://www.cloudflarestatus.com/incidents/03vm5mx76pc6> > ...

JSON•7/28/23, 1:52 PM

What did you fix? The error is not solved at all.

JJSON What did you fix? The error is not solved at all.

JamesOP•7/28/23, 1:55 PM

That's a very different error. It sounds like you're getting a key and requesting it to parse as JSON, but haven't stored valid JSON in the value

JamesOP•7/28/23, 1:56 PM

Try getting it as

text

text

and not jsonjson and logging the result.

JamesOP•7/28/23, 1:56 PM

env.NAMESPACE.get(key, { type: "text" });env.NAMESPACE.get(key, { type: "text" }); instead of env.NAMESPACE.get(key, { type: "json" });env.NAMESPACE.get(key, { type: "json" }); for example.

JJames That's a very different error. It sounds like you're getting a key and requestin...

JSON•7/28/23, 1:56 PM

What are you saying.
JSON parsing has an error because the value above says "error:code 500".

JJSON What are you saying. JSON parsing has an error because the value above says "er...

JamesOP•7/28/23, 1:57 PM

Apologies, I missed that. You're likely just waiting for the fix to roll out then. It's still in the process of rolling out.

JSON•7/28/23, 1:57 PM

If the response gives you a normal KV value, you don't see it down there, it's just an extra log I printed out to check

JamesOP•7/28/23, 1:58 PM

Yeah - give it a bit for the fix to rollout everywhere - Cloudflare's network is very large so it can take a little bit for fixes to land everywhere.

JamesOP•7/28/23, 1:58 PM

We're seeing it intermittently resolved depending on which location etc. you hit, so just give it a little while to fully propagate

JSON•7/28/23, 1:59 PM

The KV propagation is up to 60 seconds.
How come there's no change after 17 minutes?

JamesOP•7/28/23, 1:59 PM

The fix is rolling out. Please be patient.

JSON•7/28/23, 2:02 PM

Will cloudflare compensate you financially for this?

JJSON Will cloudflare compensate you financially for this?

JamesOP•7/28/23, 2:04 PM

If you're an ENT customer, I'd recommend you reach out to your account team for any SLA information and compensation.

JamesOP•7/28/23, 2:04 PM

As a pay-go user, you're welcome to submit a ticket, but as far as I know there's no official SLA for things like this, sorry.

JSON•7/28/23, 2:05 PM

I used to use a pro rating.
Nevertheless, when I ask for a ticket, I get an answer after a few days by email
Ask me again lol

When I inquired again, I only got the same macro answer.
So I didn't want to spend 20 dollars on that crap.

The service is a mess.

Where the hell am I supposed to ask?
They don't even see discord
They don't even look at the community
Tickets are even Macro-answers

JJSON I used to use a pro rating. Nevertheless, when I ask for a ticket, I get an answ...

Isaac McFadyen•7/28/23, 2:09 PM

They don't even see discord

The issue has been acknowledged. It's not a matter of "not seeing it", it's actively being worked on by the relevant teams. If you don't want to spend money on Pro, that's fine - but debating this won't get the issue resolved faster

JSON•7/28/23, 2:14 PM

when I asked about 'enterprise grade', I couldn't get a reply even after a year
I don't even know why contract tickets exist

JSON•7/28/23, 2:18 PM

If you configure redundancy like that, don't you think it should all be redundant, including domain services, pages, and serverless functions?

Gytis•7/30/23, 5:55 PM

Hi all, I as wondering has anyone did any benchmarks for js vs wasm in case its a very simple gateway (like storing request in KV)
I dont expect for latency to change much but I am wondering if there is any difference in cpu time used

kian•7/30/23, 5:57 PM

The WASM will always be slower, but it's unlikely to be noticeable unless your Worker bundle goes above 1 MiB - since that's when cold starts are bad.

Gytis•7/30/23, 7:10 PM

I mean I wonder if there is any difference in cpu usage once function is running

Gytis•7/30/23, 7:10 PM

like startup aside

GGytis I mean I wonder if there is any difference in cpu usage once function is running

Matt Silverlock•7/31/23, 1:33 PM

JS is likely to be faster for HTTP request processing. The benefit of Wasm is usually in heavy, off-request compute or where you want to use non-JS libraries/code

MMatt Silverlock JS is likely to be faster for HTTP request processing. The benefit of Wasm is us...

Gytis•7/31/23, 1:48 PM

yeah, thats what im thinking as well, I just dont have numbers to prove it. I might end up doing some benchmarks myself

kian•7/31/23, 2:03 PM

The WASM performance hits are usually when you’re doing any large copying of data between the WASM <-> JS boundary. Since the stringref proposal isn’t stabilised yet, strings are always copied rather than a reference being passed.

kian•7/31/23, 2:04 PM

Unless it’s a large workload, I doubt there’ll be differences other than a few milliseconds (if that)

Gytis•7/31/23, 10:38 PM

yep, thats what I am thinking. I think the only place where one may see any difference is cost. I am not sure if I should expect it to be higher or lower for such case
Anyways, I will write up a benchmark someday to play around with it. Im just curious

Tin Cap•8/3/23, 8:58 PM

I just switched a short algorithm from JS to WASM. My worker was taking about 3.5ms before and after.

Tin Cap•8/3/23, 8:59 PM

I was worried that invoking the WASM runtime would have a big performance impact but I didn't see it.

leostera•8/4/23, 2:09 PM

hey folks! has someone implemented simple locks with kv? for implementing a synchronized monotonic counter

kian•8/4/23, 2:15 PM

KV is eventually consistent so I'm not too sure it fits your use-case

kian•8/4/23, 2:15 PM

Writes take some time to propagate, reads are cached, etc

leostera•8/4/23, 2:31 PM

hmm. good point.

Lleostera hey folks! has someone implemented simple locks with kv? for implementing a sync...

DaniFoldi•8/4/23, 2:32 PM

#durable-objects are much more suited for that - with KV the best you could do (not recommended) is to write a key on each request, and then list them 1000 at a time to count (again, not recommended, not scalable, just a way to abuse KV into what you want)

leostera•8/4/23, 2:32 PM

cool! will look into this

leostera•8/4/23, 2:33 PM

thanks @Dani Foldi @kian !