What's your full TOML?

J

johtso•4/6/24, 11:26 PM

name = "newdo"
main = "src/index.ts"
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]
logpush = true
upload_source_maps = true

[vars]
SERVICE_NAME = "datawrangler"

[[services]]
binding = "PDFPARSER_SERVICE"
service = "pdfparser"
entrypoint = "PdfParserService"

[[d1_databases]]
binding = "DB" # i.e. available in your Worker on env.DB
database_name = "memberships"
database_id = "xxxxxxxxxxx"
migrations_dir = "../database/src/migrations"

[[durable_objects.bindings]]
name = "MY_DURABLE_OBJECT"
class_name = "MyDurableObject"

[[migrations]]
tag = "v1"
new_classes = ["MyDurableObject"]

name = "newdo"
main = "src/index.ts"
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]
logpush = true
upload_source_maps = true

[vars]
SERVICE_NAME = "datawrangler"

[[services]]
binding = "PDFPARSER_SERVICE"
service = "pdfparser"
entrypoint = "PdfParserService"

[[d1_databases]]
binding = "DB" # i.e. available in your Worker on env.DB
database_name = "memberships"
database_id = "xxxxxxxxxxx"
migrations_dir = "../database/src/migrations"

[[durable_objects.bindings]]
name = "MY_DURABLE_OBJECT"
class_name = "MyDurableObject"

[[migrations]]
tag = "v1"
new_classes = ["MyDurableObject"]

name = "newdo"
main = "src/index.ts"
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]
logpush = true
upload_source_maps = true

[vars]
SERVICE_NAME = "datawrangler"

[[services]]
binding = "PDFPARSER_SERVICE"
service = "pdfparser"
entrypoint = "PdfParserService"

[[d1_databases]]
binding = "DB" # i.e. available in your Worker on env.DB
database_name = "memberships"
database_id = "xxxxxxxxxxx"
migrations_dir = "../database/src/migrations"

[[durable_objects.bindings]]
name = "MY_DURABLE_OBJECT"
class_name = "MyDurableObject"

[[migrations]]
tag = "v1"
new_classes = ["MyDurableObject"]

name = "newdo"
main = "src/index.ts"
compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]
logpush = true
upload_source_maps = true

[vars]
SERVICE_NAME = "datawrangler"

[[services]]
binding = "PDFPARSER_SERVICE"
service = "pdfparser"
entrypoint = "PdfParserService"

[[d1_databases]]
binding = "DB" # i.e. available in your Worker on env.DB
database_name = "memberships"
database_id = "xxxxxxxxxxx"
migrations_dir = "../database/src/migrations"

[[durable_objects.bindings]]
name = "MY_DURABLE_OBJECT"
class_name = "MyDurableObject"

[[migrations]]
tag = "v1"
new_classes = ["MyDurableObject"]

J

johtso•4/6/24, 11:27 PM

OH

J

johtso•4/6/24, 11:27 PM

I have an idea..

J

johtso•4/6/24, 11:30 PM

@kian aha! it was because I was instrumenting my worker with otel-cf-workers

J

johtso•4/6/24, 11:30 PM

makes total sense that that would break things

J

johtso•4/6/24, 11:31 PM

and now that I look at the stacktrace again I see it..

J

johtso•4/6/24, 11:32 PM

so I now get "Error: Cannot access

hello

hello

as we couldn't find a

wrangler dev

wrangler dev

session for service "pdfparser" to proxy to"

S

Silent•4/6/24, 11:35 PM

How do i trigger a workers cron schedule code manually once?

W

Walshy•4/6/24, 11:47 PM

What I do is just have a fetch handler with some auth check and I just manually hit it

W

Walshy•4/6/24, 11:47 PM

In local dev I think you can hit like /__trigger_cron or something but prod doesn't have that

J

johtso•4/6/24, 11:47 PM

RPC is now working deployed! just not working locally with the dev server

J

johtso•4/6/24, 11:48 PM

not sure how wrangler tries to find the other dev session with the service.. but something ain't working

J

johtso•4/6/24, 11:48 PM

on a different note, is there a way to proxy the incoming request data to the service instead of serializing the data?

J

johtso•4/6/24, 11:49 PM

I'm handling files that exceed the 1MB limit

J

johtso•4/6/24, 11:49 PM

so just passing the request body ArrayBuffer as an argument to the service worker method doesn't work

J

johtso•4/6/24, 11:51 PM

the blog post says "You can send a byte stream over RPC, and the system will automatically stream the bytes with proper flow control."

J

johtso•4/6/24, 11:52 PM

I guess I just give it the whole

Response

Response

Response

Response instead? the post doesn't seem to say

J

johtso•4/7/24, 12:04 AM

that works

J

johtso•4/7/24, 12:25 AM

also not sure what changed.. but it's working locally now too

J

johtso•4/7/24, 12:25 AM

the only thing that isn't working now is the types

B

boywonder350•4/7/24, 12:29 AM

Does anyone know if you need to read the

body

body

of a

fetch

fetch

response for it to be garbage collected properly? Sometimes I make requests but don't care about the body and want to make sure this is ok

U

user•4/7/24, 4:11 AM

I am suffering getting my CF pages site to be able to access my CF worker

U

user•4/7/24, 4:12 AM

cors my behated

A

addison•4/7/24, 6:50 AM

is anyone having issues with mailchannels on workers? getting

"Get \"http://customer-accounts-service.outbound.svc.cluster.local.:9292/v1/accounts/cloudflare\": read tcp 100.112.254.53:39318->100.70.108.250:9292: read: connection reset by peer"

"Get \"http://customer-accounts-service.outbound.svc.cluster.local.:9292/v1/accounts/cloudflare\": read tcp 100.112.254.53:39318->100.70.108.250:9292: read: connection reset by peer"

"Get \"http://customer-accounts-service.outbound.svc.cluster.local.:9292/v1/accounts/cloudflare\": read tcp 100.112.254.53:39318->100.70.108.250:9292: read: connection reset by peer"

"Get \"http://customer-accounts-service.outbound.svc.cluster.local.:9292/v1/accounts/cloudflare\": read tcp 100.112.254.53:39318->100.70.108.250:9292: read: connection reset by peer"

Jjlworkshop for example, your CF page served at example.com, and you would like to trigger y...

U

user•4/7/24, 7:17 AM

._.

U

user•4/7/24, 7:17 AM

hadn’t thought of that.

J

johtso•4/7/24, 9:57 AM

Does anyone know what's up with this style of import? https://github.com/cloudflare/js-rpc-and-entrypoints-demo/blob/main/public-admin-api-interfaces%2Fpublic-service%2Fsrc%2Findex.ts#L1

GitHub

js-rpc-and-entrypoints-demo/public-admin-api-interfaces/public-serv...

Contribute to cloudflare/js-rpc-and-entrypoints-demo development by creating an account on GitHub.

J

johtso•4/7/24, 9:58 AM

Seems strange to be importing a type from .js in a typescript project.. but I can't get RPC types working and this is the only difference I can see..

J

johtso•4/7/24, 11:13 AM

aha, apparently it's to do with using module: preserve and moduleResolution: Bundler

J

johtso•4/7/24, 11:14 AM

Is it intended behavior that RPC calls to services appear as "Unknown Event - Ok @ 07/04/2024, 12:11:08" in logs?

J

johtso•4/7/24, 1:16 PM

Okay, so switching to

@cloudflare/workers-types/experimental

@cloudflare/workers-types/experimental

@cloudflare/workers-types/experimental

@cloudflare/workers-types/experimental fixes my type issues with Workers RPC

J

johtso•4/7/24, 1:17 PM

is this a bug? should

@cloudflare/workers-types/2023-07-01

@cloudflare/workers-types/2023-07-01

@cloudflare/workers-types/2023-07-01

@cloudflare/workers-types/2023-07-01 support the new RPC functionality?

J

James•4/7/24, 1:17 PM

Not yet afaik: https://cfdata.lol/workerd/

workerd - Cloudflare Datamining

Automated datamining from workerd, the Cloudflare Workers runtime. Including compatibility flags.

J

James•4/7/24, 1:18 PM

RPC is only enabled by default since 2024-04-03. I imagine there will be a new types compat date cut soon

JJames Not yet afaik: https://cfdata.lol/workerd/

J

johtso•4/7/24, 1:40 PM

oh that's a handy page!

J

johtso•4/7/24, 1:41 PM

opened a docs issue https://github.com/cloudflare/cloudflare-docs/issues/13899

J

johtso•4/7/24, 1:42 PM

@James but actually, I'm double confused now. The demo repo uses 2023-07-01.. and after cloning it there don't seem to be any type errors https://github.com/cloudflare/js-rpc-and-entrypoints-demo/blob/d1180c6d17983ca10e775009fc05d4aa9c01dc01/tsconfig.json#L16

J

johtso•4/7/24, 1:43 PM

don't know if there's an easy way to see what types have changed between two compatibility versions

J

James•4/7/24, 1:46 PM

Hmm that's odd. I guess it's not a breaking types change so it's probably in all of them

J

James•4/7/24, 1:47 PM

I have https://npmdiff.dev/@cloudflare%2fworkers-types/4.20230419.0/4.20230511.0/ for diffing between npm versions, but not that useful for quickly diffing two files in each folder. You could probably just throw those 2 files from the most recent version into a diff checker

Aaddison is anyone having issues with mailchannels on workers? getting `"Get \"http://cus...

J

James•4/7/24, 1:48 PM

This is sadly not a direct solution to your issue, but I would recommend avoiding MailChannels and using some other service like Amazon SES, Sendgrid, Postmark, etc.

There are a lot of security implications and their responses to the situation have been very undesirable. Further reading:

To this day, that have still not truly acknowledged the problems, and brushed it aside or "patched" it with paywalls.

JJames I have https://npmdiff.dev/@cloudflare%2fworkers-types/4.20230419.0/4.20230511.0...

J

johtso•4/7/24, 1:54 PM

hmm, but this doesn't seem to be a difference in behaviour between release versions, just a difference in behaviour between compatiblity dates

J

johtso•4/7/24, 1:54 PM

type error with 2023-07-01, no type error with experimental

J

johtso•4/7/24, 2:28 PM

does anyone know of any kind of instrumentation that works with RPC?

Similar Threads

Similar Threads

Similar Threads