yeah, you just gave me the confirmation I was needing, I think it would be impossible to transfer th

JJorge yeah, you just gave me the confirmation I was needing, I think it would be impos...

H

Not quite on that part. While it can be difficult, and may not have a prebuilt solution, it definitely isn't impossible to move stuff between accounts

H

Hello, I’m Allie!•3/30/24, 10:05 PM

Though I would generally start on the account I want to stay on, if at all possible

P

Phisn•3/30/24, 11:03 PM

I currently am looking in implementing authentication / authorization in my application. Im considering either using oauth with google and co or having my own accounts. Do there exist solutions that already fit with cloudflare workers?

C

Caleb•3/31/24, 1:16 AM

Hi i was wondering if someone could help me

C

Caleb•3/31/24, 1:16 AM

im trying to run my worker using wrangler dev --remote

C

Caleb•3/31/24, 1:18 AM

and i get the error Error on remote worker: APIError: A request to the Cloudflare API (/accounts/<account_id>/workers/scripts/test/edge-preview) failed

C

Caleb•3/31/24, 1:18 AM

i have binded an r2 bucket in my wrangler.toml file

C

Caleb•3/31/24, 1:19 AM

[[r2_buckets]]
binding = 'MY_BUCKET' # <~ valid JavaScript variable name
bucket_name = '<test_bucket>'
preview_bucket_name = '<test_bucket>'

[[r2_buckets]]
binding = 'MY_BUCKET' # <~ valid JavaScript variable name
bucket_name = '<test_bucket>'
preview_bucket_name = '<test_bucket>'

[[r2_buckets]]
binding = 'MY_BUCKET' # <~ valid JavaScript variable name
bucket_name = '<test_bucket>'
preview_bucket_name = '<test_bucket>'

[[r2_buckets]]
binding = 'MY_BUCKET' # <~ valid JavaScript variable name
bucket_name = '<test_bucket>'
preview_bucket_name = '<test_bucket>'

C

Caleb•3/31/24, 1:19 AM

when i remove this code or run wrangler dev without remote flag, it works

C

Caleb•3/31/24, 1:19 AM

i also get the error when running wrangler deploy

C

Caleb•3/31/24, 1:20 AM

└────────────────────────────────────┴──────────────────────────────────┘
🔓 Token Permissions: If scopes are missing, you may need to logout and re-login.
Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- d1 (write)
- pages (write)
- zone (read)
- ssl_certs (write)
- constellation (write)
- ai (read)
- offline_access

└────────────────────────────────────┴──────────────────────────────────┘
🔓 Token Permissions: If scopes are missing, you may need to logout and re-login.
Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- d1 (write)
- pages (write)
- zone (read)
- ssl_certs (write)
- constellation (write)
- ai (read)
- offline_access

└────────────────────────────────────┴──────────────────────────────────┘
🔓 Token Permissions: If scopes are missing, you may need to logout and re-login.
Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- d1 (write)
- pages (write)
- zone (read)
- ssl_certs (write)
- constellation (write)
- ai (read)
- offline_access

└────────────────────────────────────┴──────────────────────────────────┘
🔓 Token Permissions: If scopes are missing, you may need to logout and re-login.
Scope (Access)
- account (read)
- user (read)
- workers (write)
- workers_kv (write)
- workers_routes (write)
- workers_scripts (write)
- workers_tail (read)
- d1 (write)
- pages (write)
- zone (read)
- ssl_certs (write)
- constellation (write)
- ai (read)
- offline_access

C

Caleb•3/31/24, 1:20 AM

when i run wrangler whoami i get the above output

C

Caleb•3/31/24, 1:20 AM

i don't see r2 on there, could this be the issue? and if it is how would i fix it?

C

Caleb•3/31/24, 1:21 AM

i already tried logout and re-login btw

C

Caleb•3/31/24, 1:25 AM

sorry i should have put this in wrangler channel my bad

C

Caleb•3/31/24, 1:35 AM

wait i think i figured it out

C

Caleb•3/31/24, 1:35 AM

i might be stupid

C

Caleb•3/31/24, 1:35 AM

i didnt remove <> from name lol

PPhisn I currently am looking in implementing authentication / authorization in my appl...

B

bun•3/31/24, 9:44 AM

Oslo auth

O

outsideurimagination•3/31/24, 11:52 AM

Anyone know if I can check what's been stored in caches.default somewhere?

Ooutsideurimagination Anyone know if I can check what's been stored in caches.default somewhere?

H

Hello, I’m Allie!•3/31/24, 11:56 AM

You can't. If you have a specific URL, you can check whether something is cached for that value, but you can't ask for arbitrary cached items

O

outsideurimagination•3/31/24, 12:36 PM

I can't figure out why my cache isn't working. Anyone have an idea? This is a remix app on CF Pages with a custom domain.

import { json } from "@remix-run/react";

export const loader: LoaderFunction = async ({ request, context, params }) => {
  const url = new URL(request.url);

  const cacheKey = new Request(url.toString(), request);
  const cache = context.cloudflare.caches.default;
  const cacheEntry = await cache.match(cacheKey);
  let users = (await cacheEntry?.json())?.users;

  if (!users) {
    const query = url.searchParams.get("query");
    const db = await context.db;
    users = await db.query(query);
    context.cloudflare.ctx.waitUntil(
      cache.put(
        cacheKey,
        json(users, {
          headers: {
            Expires: new Date(
              new Date().setFullYear(new Date().getFullYear() + 1),
            ).toUTCString(),
          },
        }),
      ),
    );
  }
  ...
}

import { json } from "@remix-run/react";

export const loader: LoaderFunction = async ({ request, context, params }) => {
  const url = new URL(request.url);

  const cacheKey = new Request(url.toString(), request);
  const cache = context.cloudflare.caches.default;
  const cacheEntry = await cache.match(cacheKey);
  let users = (await cacheEntry?.json())?.users;

  if (!users) {
    const query = url.searchParams.get("query");
    const db = await context.db;
    users = await db.query(query);
    context.cloudflare.ctx.waitUntil(
      cache.put(
        cacheKey,
        json(users, {
          headers: {
            Expires: new Date(
              new Date().setFullYear(new Date().getFullYear() + 1),
            ).toUTCString(),
          },
        }),
      ),
    );
  }
  ...
}

import { json } from "@remix-run/react";

export const loader: LoaderFunction = async ({ request, context, params }) => {
  const url = new URL(request.url);

  const cacheKey = new Request(url.toString(), request);
  const cache = context.cloudflare.caches.default;
  const cacheEntry = await cache.match(cacheKey);
  let users = (await cacheEntry?.json())?.users;

  if (!users) {
    const query = url.searchParams.get("query");
    const db = await context.db;
    users = await db.query(query);
    context.cloudflare.ctx.waitUntil(
      cache.put(
        cacheKey,
        json(users, {
          headers: {
            Expires: new Date(
              new Date().setFullYear(new Date().getFullYear() + 1),
            ).toUTCString(),
          },
        }),
      ),
    );
  }
  ...
}

import { json } from "@remix-run/react";

export const loader: LoaderFunction = async ({ request, context, params }) => {
  const url = new URL(request.url);

  const cacheKey = new Request(url.toString(), request);
  const cache = context.cloudflare.caches.default;
  const cacheEntry = await cache.match(cacheKey);
  let users = (await cacheEntry?.json())?.users;

  if (!users) {
    const query = url.searchParams.get("query");
    const db = await context.db;
    users = await db.query(query);
    context.cloudflare.ctx.waitUntil(
      cache.put(
        cacheKey,
        json(users, {
          headers: {
            Expires: new Date(
              new Date().setFullYear(new Date().getFullYear() + 1),
            ).toUTCString(),
          },
        }),
      ),
    );
  }
  ...
}

json is a helper from remix that does

// So you can write this:
return json({ any: "thing" });

// Instead of this:
return new Response(JSON.stringify({ any: "thing" }), {
  headers: {
    "Content-Type": "application/json; charset=utf-8",
  },
});

// So you can write this:
return json({ any: "thing" });

// Instead of this:
return new Response(JSON.stringify({ any: "thing" }), {
  headers: {
    "Content-Type": "application/json; charset=utf-8",
  },
});

// So you can write this:
return json({ any: "thing" });

// Instead of this:
return new Response(JSON.stringify({ any: "thing" }), {
  headers: {
    "Content-Type": "application/json; charset=utf-8",
  },
});

// So you can write this:
return json({ any: "thing" });

// Instead of this:
return new Response(JSON.stringify({ any: "thing" }), {
  headers: {
    "Content-Type": "application/json; charset=utf-8",
  },
});

C

Cretezy•3/31/24, 1:58 PM

Anyone seen

Error: Trace resource limit exceeded; subsequent exceptions not recorded.

Error: Trace resource limit exceeded; subsequent exceptions not recorded.

before?

CCretezy Anyone seen `Error: Trace resource limit exceeded; subsequent exceptions not rec...

D

DaniFoldi•3/31/24, 2:09 PM

I believe you get that error when you hit this limit: https://developers.cloudflare.com/workers/platform/limits/#log-size

C

Cretezy•3/31/24, 2:10 PM

I don't have a single console.log in that handler. It seems to be when I'm doing an external request, but I'm not sure why

D

DaniFoldi•3/31/24, 2:10 PM

do you have logpush enabled?

C

Cretezy•3/31/24, 2:10 PM

No

D

DaniFoldi•3/31/24, 2:11 PM

hmm, interesting, this could be a new limit I haven't seen yet

C

Cretezy•3/31/24, 2:17 PM

Seems like it was doing a

throw

throw

and that was too big (176kb lol).

graphql-request

graphql-request

errors are very big somehow

J

johtso•3/31/24, 4:02 PM

for some reason

wrangler dev

wrangler dev

has stopped working for me.. it just returns with no output. is there some way to debug?

J

johtso•3/31/24, 4:03 PM

wrangler dev --log-level debug

wrangler dev --log-level debug

also gives no output

J

johtso•3/31/24, 4:08 PM

updated wrangler, still no dice

J

James•3/31/24, 4:26 PM

Can you reproduce with a fresh worker created via

npm create cloudflare@latest

npm create cloudflare@latest

?

J

James•3/31/24, 4:26 PM

Is there something specific in your worker or wrangler.toml that's causing it? I'd start by trying to reproduce with a simple worker and then going from there.

B

bernardo.abreu•3/31/24, 5:30 PM

Hey folks, does anyone know what this error means? Specially the "make sure you've set the upstream option" part

Bbernardo.abreu Hey folks, does anyone know what this error means? Specially the "make sure you'...

H

Hello, I’m Allie!•3/31/24, 5:44 PM

This sounds like the Worker is calling itself in an infinite loop.

HHello, I’m Allie!This sounds like the Worker is calling itself in an infinite loop.

B

bernardo.abreu•3/31/24, 5:45 PM

What does upstream option mean ?

Bbernardo.abreu What does upstream option mean ?

H

Hello, I’m Allie!•3/31/24, 5:48 PM

The

host

host

option in your

wrangler

wrangler

config: https://developers.cloudflare.com/workers/wrangler/configuration/#local-development-settings

Cloudflare Docs

Configuration - Wrangler · Cloudflare Workers docs

Use a

wrangler.toml

wrangler.toml

configuration file to customize the development and deployment setup for your Worker project and other Developer Platform …

JJames Can you reproduce with a fresh worker created via `npm create cloudflare@latest`...

J

johtso•3/31/24, 5:51 PM

in the end reopening iterm sorted it out. still seems strange for it to silently fail with no output. I guess maybe an issue with a wrangler process still running? or maybe something to do with deleting the

.wrangler

.wrangler

directory in the project and the environment still thinking it should be there?

J

johtso•3/31/24, 5:51 PM

"have you tried turning it off and on again?"

J

johtso•3/31/24, 6:15 PM

@James I spoke too soon, it's doing the same thing again..

J

johtso•3/31/24, 6:16 PM

same issue happens in a fresh worker created with create-cloudflare

J

johtso•3/31/24, 6:16 PM

so seems to be wrangler getting into some kind of bad state

J

johtso•3/31/24, 6:19 PM

seems to be kind of non deterministic.. sometimes it works if I quit iterm and run

wrangler dev

wrangler dev

again.. sometimes it just continues to return after a small delay with no output

J

johtso•3/31/24, 6:29 PM

J

johtso•3/31/24, 6:29 PM

dev server runs successfully. I press x to close it. I try to run it again.. no output

J

johtso•3/31/24, 6:41 PM

upgrading from node 18 to 21 and reinstalling wrangler seems to have sorted it for now..

D

dog1283•3/31/24, 8:12 PM

Hello all. Just posted this in workers help in case anyone has a view: workers-and-pages-helpCustom Routes - Best Practice for Workers as Microservices

N

NazCodeland•3/31/24, 9:01 PM

I don't think I remember

wrangler tail

wrangler tail

working for remote urls, but it does now and its amazing. Out of curiousity, is it able to tail deployed Workers because those Workers are deployed on Cloudflare networks and therefore, Cloudflare knows when their code is executing?

NNazCodeland I don't think I remember `wrangler tail` working for remote urls, but it does no...

H

Hello, I’m Allie!•3/31/24, 9:07 PM

Do you mean

wrangler tail

wrangler tail

?

yeah, you just gave me the confirmation I was needing, I think it would be impossible to transfer th

Similar Threads