the docs also say to do something like ```ts interface Env { MY_SERVICE: Service<MyService>; }```

J

johtsoOP•4/6/24, 9:32 PM

ah right, you don't have the code together

J

johtsoOP•4/6/24, 9:32 PM

makes sense

Jjohtso the docs also say to do something like ```ts interface Env { MY_SERVICE: Servi...

T

Tilon•4/6/24, 9:33 PM

I basically did what's written in the blog post under "What about type safety"
https://blog.cloudflare.com/javascript-native-rpc

Hmm, I just read it again and it sounds like import should work as well:

You might do this by defining the interface in a separate shared TypeScript file, or by extracting a .d.ts type declaration file from your server code...

The Cloudflare Blog

We've added JavaScript-native RPC to Cloudflare Workers

Cloudflare Workers now features a built-in RPC (Remote Procedure Call) system for use in Worker-to-Worker and Worker-to-Durable Object communication, with absolutely minimal boilerplate. We've designed an RPC system so expressive that calling a remote service can feel like using a library.

J

johtsoOP•4/6/24, 9:58 PM

Yeah, even ignoring typescript, I keep getting "TypeError: Illegal invocation" when trying to use the service

J

johtsoOP•4/6/24, 9:58 PM

my wrangler has something like this

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

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

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

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

J

johtsoOP•4/6/24, 9:58 PM

which I thought was all you needed to do

J

James•4/6/24, 9:59 PM

hmm. What's your compat date/flags?

J

johtsoOP•4/6/24, 9:59 PM

compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]

compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]

compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]

compatibility_date = "2024-04-06"
compatibility_flags = [ "nodejs_compat" ]

J

James•4/6/24, 9:59 PM

okay yeah that should be totally fine

J

johtsoOP•4/6/24, 10:00 PM

pdfparser is the name of my other worker. it exports the

WorkerEntrypoint

WorkerEntrypoint

WorkerEntrypoint

WorkerEntrypoint that I want to use as its default export

JJames Hey, you've asked that same question about 5 times, and already been told that m...

S

safah222•4/6/24, 10:01 PM

they told me that request.cf.verifiedBotCategory; is avaulable for all plans , so I am trying to know how I can use it within the worker

J

James•4/6/24, 10:02 PM

Did you try giving the entrypoint a name with

entrypoint

entrypoint

entrypoint

entrypoint?

Ssafah222 they told me that request.cf.verifiedBotCategory; is avaulable for all plans , ...

J

James•4/6/24, 10:02 PM

I'm not sure it is. But if it is, your code should be fine. Have you tried it? Did you experience any issue?

J

johtsoOP•4/6/24, 10:03 PM

um.. so I deleted all my
.wrangler
.wrangler
directories and restarted my workers and now it's working?

S

safah222•4/6/24, 10:03 PM

the worker didnt gave any error , how ever its not detecting any type of bots

S

safah222•4/6/24, 10:03 PM

all of the bots still not triggered by my code , maybe because I am writing the code in inccorect way

S

safah222•4/6/24, 10:03 PM

how should I mention the catagories

T

Titan•4/6/24, 10:04 PM

Is there a performance penalty to enabling node_compat? Just wondering the reason for it not being enabled by default

TTitan Is there a performance penalty to enabling node_compat? Just wondering the reaso...

J

James•4/6/24, 10:04 PM

node_compat

node_compat

node_compat

node_compat as a top-level option is legacy and should be avoided whenever possible.

J

James•4/6/24, 10:04 PM

nodejs_compat

nodejs_compat

nodejs_compat

nodejs_compat as a compat flag is good and won't incur any kind of performance issues

A

Arnø•4/6/24, 10:04 PM

Hi, what would you recommend for importing a 1GB txt file from a cron to populate my D1 database? So that it doesn't exceed the resource limits.

J

johtsoOP•4/6/24, 10:04 PM

oh wait no ignore that.. the ports just got swapped so I was hitting the other worker.. still not working

JJames Did you try giving the entrypoint a name with `entrypoint`?

J

johtsoOP•4/6/24, 10:07 PM

I did try exporting it with a name, I'll give that another try though

J

johtsoOP•4/6/24, 10:11 PM

@James I get this message when running the dev server

▲ [WARNING] This worker is bound to live services: PDFPARSER_SERVICE (pdfparser#PdfParserService)

▲ [WARNING] This worker is bound to live services: PDFPARSER_SERVICE (pdfparser#PdfParserService)

▲ [WARNING] This worker is bound to live services: PDFPARSER_SERVICE (pdfparser#PdfParserService)

▲ [WARNING] This worker is bound to live services: PDFPARSER_SERVICE (pdfparser#PdfParserService)

J

johtsoOP•4/6/24, 10:11 PM

which seems promising

J

johtsoOP•4/6/24, 10:11 PM

but then the Illegal invocation error

J

James•4/6/24, 10:11 PM

How are you calling it? Can you share a snippet?

JJames How are you calling it? Can you share a snippet?

J

johtsoOP•4/6/24, 10:12 PM

async function membershipRequestHandler (request: Request, env: Env) {
    const body = await request.arrayBuffer();

    console.log(`Parsing PDF size ${body.byteLength / 1024 / 1024} MBs`)

    const result = await env.PDFPARSER_SERVICE.parsePdf(body);

async function membershipRequestHandler (request: Request, env: Env) {
    const body = await request.arrayBuffer();

    console.log(`Parsing PDF size ${body.byteLength / 1024 / 1024} MBs`)

    const result = await env.PDFPARSER_SERVICE.parsePdf(body);

async function membershipRequestHandler (request: Request, env: Env) {
    const body = await request.arrayBuffer();

    console.log(`Parsing PDF size ${body.byteLength / 1024 / 1024} MBs`)

    const result = await env.PDFPARSER_SERVICE.parsePdf(body);

async function membershipRequestHandler (request: Request, env: Env) {
    const body = await request.arrayBuffer();

    console.log(`Parsing PDF size ${body.byteLength / 1024 / 1024} MBs`)

    const result = await env.PDFPARSER_SERVICE.parsePdf(body);

J

johtsoOP•4/6/24, 10:13 PM

export class PdfParserService extends WorkerEntrypoint<Env> {
  async fetch() { return new Response("Hello from Worker B"); }
  
  async parsePdf(data: ArrayBuffer) {
        return await pdf2array(Buffer.from(data));
    }
}

export class PdfParserService extends WorkerEntrypoint<Env> {
  async fetch() { return new Response("Hello from Worker B"); }
  
  async parsePdf(data: ArrayBuffer) {
        return await pdf2array(Buffer.from(data));
    }
}

export class PdfParserService extends WorkerEntrypoint<Env> {
  async fetch() { return new Response("Hello from Worker B"); }
  
  async parsePdf(data: ArrayBuffer) {
        return await pdf2array(Buffer.from(data));
    }
}

export class PdfParserService extends WorkerEntrypoint<Env> {
  async fetch() { return new Response("Hello from Worker B"); }
  
  async parsePdf(data: ArrayBuffer) {
        return await pdf2array(Buffer.from(data));
    }
}

J

James•4/6/24, 10:13 PM

And your toml is this?

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

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

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

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

J

johtsoOP•4/6/24, 10:14 PM

exactly

J

James•4/6/24, 10:14 PM

Hmm, looks fine on the surface to me

J

johtsoOP•4/6/24, 10:14 PM

I do have lots of linting errors in my TOML file.. I can't for a life of me remember what's responsible for that linting though

J

johtsoOP•4/6/24, 10:15 PM

whatever it is doesn't know about

upload_source_maps

upload_source_maps

upload_source_maps

upload_source_maps or

services -> entrypoint

services -> entrypoint

services -> entrypoint

services -> entrypoint

J

johtsoOP•4/6/24, 10:20 PM

@James from a bit of google I think it might actually have something to do with what I'm doing with the request body

J

johtsoOP•4/6/24, 10:21 PM

I'll try just doing a hello world method on the service worker

J

johtsoOP•4/6/24, 10:23 PM

nope, no luck with that either

K

kian•4/6/24, 11:18 PM

What's your full TOML?

Kkian What's your full TOML?

J

johtsoOP•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

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

OH

J

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

I have an idea..

J

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

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

J

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

makes total sense that that would break things

J

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

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

J

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

so I now get "Error: Cannot access

hello

hello

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

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

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

J

johtsoOP•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

the docs also say to do something like ```ts interface Env { MY_SERVICE: Service<MyService>; }```

Similar Threads

Similar Threads

Similar Threads