did you resolve it? 🤔 i have the same problem 😄

K

kian•12/29/23, 2:24 AM

If you mean that your Service Binding subrequests are showing

canceled

canceled

canceled

canceled, make sure you read the response body (even if you don't need it).

Kkian If you mean that your Service Binding subrequests are showing `canceled`, make s...

S

schkovichOP•12/29/23, 2:35 AM

thank you! it makes sense, but it would not cross my mind anytime soon.

Sschkovich did you resolve it? 🤔 i have the same problem 😄

K

kingmesal•12/29/23, 1:52 PM

Still get the cancelled message... But we'll try that new suggestion...

Kkingmesal Still get the cancelled message... But we'll try that new suggestion...

S

schkovichOP•12/29/23, 2:22 PM

I couldn't find such a restriction in fetch API. Most likely, this behaviour is cloudflare

undocumented implementation detail. Like providing dummy properly formatted URI in fetch request to desired Service Binding. Nevertheless, @kian suggestion worked.

T

Tudders•12/30/23, 1:52 AM

Hey all - wondering if anyone has gotten the openAI includes to work in functions ala -> https://developers.cloudflare.com/workers/tutorials/openai-function-calls-workers/ ?

My build is erroring out looking for the packages -> utils/chatGPT.js:6:24: ERROR: No matching export in "../node_modules/openai/index.mjs" for import "OpenAIApi" ...

SOLVED blobyes

OpenAI GPT function calling with JavaScript and Cloudflare Workers ...

All of the tutorials assume you have already completed the Get started guide, which gets you set up with a Cloudflare Workers account, C3 , and …

E

Esteban 🇨🇺•1/2/24, 6:11 PM

Anyone want to chime in why this Pages Function works with GET but with POST it returns CORS errors.

function generateUUID() {
  return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) {
    var r = (Math.random() * 16) | 0,
      v = c == 'x' ? r : (r & 0x3) | 0x8;
    return v.toString(16);
  });
}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });
  
  response.headers.set('Access-Control-Allow-Origin', '*');
  
  return response;

}

function generateUUID() {
  return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) {
    var r = (Math.random() * 16) | 0,
      v = c == 'x' ? r : (r & 0x3) | 0x8;
    return v.toString(16);
  });
}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });
  
  response.headers.set('Access-Control-Allow-Origin', '*');
  
  return response;

}

function generateUUID() {
  return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) {
    var r = (Math.random() * 16) | 0,
      v = c == 'x' ? r : (r & 0x3) | 0x8;
    return v.toString(16);
  });
}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });
  
  response.headers.set('Access-Control-Allow-Origin', '*');
  
  return response;

}

function generateUUID() {
  return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) {
    var r = (Math.random() * 16) | 0,
      v = c == 'x' ? r : (r & 0x3) | 0x8;
    return v.toString(16);
  });
}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });
  
  response.headers.set('Access-Control-Allow-Origin', '*');
  
  return response;

}

E

Esteban 🇨🇺•1/2/24, 6:30 PM

~~I'm somewhat certain this is not a traditional Browser CORS issue. Instead it's an issue of Cloudflare arbitrarily re-imagining how CORS is configured on their platform.~~

I eagerly await support, as no Googling or ChatGPT is helpful here.

J

James•1/2/24, 6:32 PM

Can you provide the error you receive in your browser when attempting to hit it? A screenshot of your browser console might be helpful

E

Esteban 🇨🇺•1/2/24, 6:33 PM

Network Tab.

Screen_Shot_2024-01-02_at_1.32.38_PM.png

E

Esteban 🇨🇺•1/2/24, 6:33 PM

Console. At this point, I don't care about showing my domain.

Screen_Shot_2024-01-02_at_1.33.08_PM.png

K

kian•1/2/24, 6:34 PM

This is nothing to do with Cloudflare, you just haven't setup preflight handling.

K

kian•1/2/24, 6:35 PM

https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request

K

kian•1/2/24, 6:35 PM

Primarily https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Headers

J

James•1/2/24, 6:35 PM

I'd recommend you lock it down more tightly than this, but a baseline to get things working during testing should be:

    'Access-Control-Allow-Origin': '*',
    'Access-Control-Allow-Headers': '*',
    'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS',

    'Access-Control-Allow-Origin': '*',
    'Access-Control-Allow-Headers': '*',
    'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS',

    'Access-Control-Allow-Origin': '*',
    'Access-Control-Allow-Headers': '*',
    'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS',

    'Access-Control-Allow-Origin': '*',
    'Access-Control-Allow-Headers': '*',
    'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS',

E

Esteban 🇨🇺•1/2/24, 6:36 PM

I'll give it a shot

E

Esteban 🇨🇺•1/2/24, 6:36 PM

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });

  response.headers.set("Access-Control-Allow-Origin", "*")
  response.headers.set("Access-Control-Allow-Headers", "*")
  response.headers.set("Access-Control-Allow-Methods", "GET,HEAD,POST,OPTIONS")

  return response;

}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });

  response.headers.set("Access-Control-Allow-Origin", "*")
  response.headers.set("Access-Control-Allow-Headers", "*")
  response.headers.set("Access-Control-Allow-Methods", "GET,HEAD,POST,OPTIONS")

  return response;

}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });

  response.headers.set("Access-Control-Allow-Origin", "*")
  response.headers.set("Access-Control-Allow-Headers", "*")
  response.headers.set("Access-Control-Allow-Methods", "GET,HEAD,POST,OPTIONS")

  return response;

}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });

  response.headers.set("Access-Control-Allow-Origin", "*")
  response.headers.set("Access-Control-Allow-Headers", "*")
  response.headers.set("Access-Control-Allow-Methods", "GET,HEAD,POST,OPTIONS")

  return response;

}

Updated onRequest

E

Esteban 🇨🇺•1/2/24, 6:38 PM

It worked. I take back what i said.

J

James•1/2/24, 6:40 PM

Glad you got it working

W

Will•1/3/24, 10:57 AM

So I have an SSR site made with astro.
let's on the server side rendering I need to access worker KV.

now I have two options :

use pages function(I am still not sure how is this going to work tbh, but it looks like astro made a js file under function folder)
make a worker then bind that to the astro pages.

what is the pros and cons of both option?

Q

quambo•1/3/24, 12:21 PM

Quick question around

pages dev

pages dev

pages dev

pages dev functions and restarting on code changes.

I've got a function that re-exports

onRequest

onRequest

onRequest

onRequest from a different folder, and I use the wrangler dev bundling. The details are here: wrangler pages dev when functions are not in root?

For some reason during dev, codechanges are not applied without having to restart. Is this a bug?

N

NoOneInParticulate•1/9/24, 8:27 PM

I have a page with a simple function using

export async function onRequestPost(context) {

export async function onRequestPost(context) {

export async function onRequestPost(context) {

export async function onRequestPost(context) { I am trying to POST some JSON to it. While logging

context

context

context

context or

context.request

context.request

context.request

context.request, or

context.request.body

context.request.body

context.request.body

context.request.body I don't see the data I am passing in from a POST via curl or Postman.

I'm not seeing enough information in the docs to help me understand what I'm doing incorrectly.

Thanks!

NNoOneInParticulate I have a page with a simple function using `export async function onRequestPost(...

K

kian•1/9/24, 8:31 PM

context.request

context.request

context.request

context.request is the Request Web API, where the

body

body

body

body property is a ReadableStream

K

kian•1/9/24, 8:32 PM

If you want to access the body, there are helper methods on

Request

Request

Request

Request like

text()

text()

text()

text() &

json()

json()

json()

json(). So, if your request body is JSON, then you'd do...

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

N

NoOneInParticulate•1/9/24, 8:32 PM

Thank you!

K

kian•1/9/24, 8:32 PM

json()

json()

json()

json() is basically

JSON.parse(await request.text())

JSON.parse(await request.text())

JSON.parse(await request.text())

JSON.parse(await request.text()), you'll get an object back

T

TigersWay•1/10/24, 9:22 AM

Trying to rewrite some old workers to pages functions I have a "strange" error message:

Your worker created multiple branches of a single stream...

Your worker created multiple branches of a single stream...

Your worker created multiple branches of a single stream...

Your worker created multiple branches of a single stream...
The

GET

GET

GET

GET are working fine, but nothing else even with "empty" APIs.

export const onRequest: PagesFunction = async (context) => {
  console.log('TRACKING');
  return new Response();
};

export const onRequest: PagesFunction = async (context) => {
  console.log('TRACKING');
  return new Response();
};

export const onRequest: PagesFunction = async (context) => {
  console.log('TRACKING');
  return new Response();
};

export const onRequest: PagesFunction = async (context) => {
  console.log('TRACKING');
  return new Response();
};

G

gabrielstuff•1/10/24, 9:15 PM

Hello, I'm trying to use page functions to run

ytdl-code

ytdl-code

ytdl-code

ytdl-code but got errors everywhere :

✘ [ERROR] 14 error(s) and 0 warning(s) when compiling Worker.
✘ [ERROR] Could not resolve "buffer"

✘ [ERROR] 14 error(s) and 0 warning(s) when compiling Worker.
✘ [ERROR] Could not resolve "buffer"

✘ [ERROR] 14 error(s) and 0 warning(s) when compiling Worker.
✘ [ERROR] Could not resolve "buffer"

✘ [ERROR] 14 error(s) and 0 warning(s) when compiling Worker.
✘ [ERROR] Could not resolve "buffer"

I' trying to understand if page function support external packages at all

K

kian•1/10/24, 9:17 PM

Yes, but Workers and Functions aren't Node so they don't have Node built-ins.

G

gabrielstuff•1/10/24, 9:21 PM

ok thanks, so are we able to use npm package in them ?

G

gabrielstuff•1/10/24, 9:21 PM

or maybe esm.sh import ?

G

gabrielstuff•1/10/24, 9:22 PM

Reading the doc, I thought i could simply adjust the netlify functions path, rewrite and run. But it looks like it is not the case exactly.

Ggabrielstuff ok thanks, so are we able to use npm package in them ?

I

Isaac McFadyen•1/10/24, 9:22 PM

You can use NPM packages, but you cannot use a Node built-in module, which ytdl-code does (

buffer

buffer

buffer

buffer)

I

Isaac McFadyen•1/10/24, 9:22 PM

If there's an alternative package that doesn't use

buffer

buffer

buffer

buffer then you might be able to use that

I

Isaac McFadyen•1/10/24, 9:23 PM

You could also patch

ytdl-code

ytdl-code

ytdl-code

ytdl-code to import from

node:buffer

node:buffer

node:buffer

node:buffer instead and then use Workers NodeJS compat: https://developers.cloudflare.com/workers/runtime-apis/nodejs/

G

gabrielstuff•1/10/24, 9:24 PM

ok, I see. No I do not think so. What is the alternative when people rely on package with node built-in module ? Any cloudflare product

G

gabrielstuff•1/10/24, 9:24 PM

(going to read the code of ytdl-core

but the patch path seems a bit long to me)

Ggabrielstuff ok, I see. No I do not think so. What is the alternative when people rely on pac...

I

Isaac McFadyen•1/10/24, 9:25 PM

There is no Cloudflare product that allows build-in modules unfortunately - it's either patching it to use

node:buffer

node:buffer

node:buffer

node:buffer or finding an alternative package.

I

Isaac McFadyen•1/10/24, 9:25 PM

Actually, you might be able to.

I

Isaac McFadyen•1/10/24, 9:25 PM

Try adding
node_compat = true
node_compat = true
node_compat = true
node_compat = true to your
wrangler.toml
wrangler.toml
: https://developers.cloudflare.com/workers/wrangler/configuration/#node-compatibility

I

Isaac McFadyen•1/10/24, 9:25 PM

It's the older form of Node compat so it won't work as well for some things but it might work.

I

Isaac McFadyen•1/10/24, 9:27 PM

Oh this is Pages. Hmmm.

I

Isaac McFadyen•1/10/24, 9:27 PM

Not sure if you can use node_compat in Pages

G

gabrielstuff•1/10/24, 9:27 PM

Reading the code, as https://github.com/fent/node-ytdl-core/blob/master/package.json#L39 depends on m3u8stream,miniget and sax I guess I should also patch this packages ?

I

Isaac McFadyen•1/10/24, 9:28 PM

Yeah, probably. Assuming they use node built-ins

IIsaac McFadyen Not sure if you can use node_compat in Pages

G

gabrielstuff•1/10/24, 9:28 PM

https://developers.cloudflare.com/workers/runtime-apis/nodejs/#enable-nodejs-with-pages-functions apparently yes it's possible

G

gabrielstuff•1/10/24, 9:28 PM

I did that but no effect

I

Isaac McFadyen•1/10/24, 9:28 PM

That would be the newer nodejs_compat (similar names, it's a bit confusing) which requires you to change your imports to

node:buffer

node:buffer

node:buffer

node:buffer unfortunately.

G

gabrielstuff•1/10/24, 9:28 PM

I locally tested with

npx wrangler pages dev --compatibility-flags="nodejs_compat" -- npm run dev

npx wrangler pages dev --compatibility-flags="nodejs_compat" -- npm run dev

npx wrangler pages dev --compatibility-flags="nodejs_compat" -- npm run dev

npx wrangler pages dev --compatibility-flags="nodejs_compat" -- npm run dev

I

Isaac McFadyen•1/10/24, 9:28 PM

I don't think the

node_compat

node_compat

node_compat

node_compat (the original one) works with Pages.

did you resolve it? 🤔 i have the same problem 😄

Similar Threads

Similar Threads

Similar Threads