Errors after the registry server is restarted
First of all, this is amazing project, thank you guys!
My steps:
1. Started the rivet-engine via docker-compose
2. Started registry server (as in express example, nothing more)
3. Send post request via curl (as in example)
4. Send again the same request
The first problem: it returns {count: 1} twice, but I expect it will increment each time I make request. Starting from the third request it works fine: 2,3,4...
The second problem: I shut down the registry server and start it again. As a result - "Active actors count: 0" in console and when I try send request it just waiting and then error 500
env is RIVET_ENGINE=http://localhost:6420
the third problem with rivet.studio. After I insert the token and tried to connect it failed with error:
What am I doing wrong?
And also, are there any examples which show how to run actors on several machines? With rivet-engine, several nodes and so on.
Thanks!
My steps:
1. Started the rivet-engine via docker-compose
2. Started registry server (as in express example, nothing more)
3. Send post request via curl (as in example)
4. Send again the same request
The first problem: it returns {count: 1} twice, but I expect it will increment each time I make request. Starting from the third request it works fine: 2,3,4...
The second problem: I shut down the registry server and start it again. As a result - "Active actors count: 0" in console and when I try send request it just waiting and then error 500
env is RIVET_ENGINE=http://localhost:6420
the third problem with rivet.studio. After I insert the token and tried to connect it failed with error:
level=WARN msg="internal error" error="this.raw.headers.get is not a function" stack="TypeError: this.raw.headers.get is not a function\n at HonoRequest.headerWhat am I doing wrong?
And also, are there any examples which show how to run actors on several machines? With rivet-engine, several nodes and so on.
Thanks!
Build and scale stateful backends. Rivet Actors is a library for long-lived processes with durable state, realtime, and scalability. Easily self-hostable and works with your infrastructure.
1,419Members
Resources
Was this page helpful?
