which is half true
scalameta maintains a fastparse 1 fork, as far as i understood
I assumed (the migration to fastparse2 and 2.13) was in the same branch
But Yes is better to have two commits. I will make a PR to support Scala 2.13 today based in your branch @mfirry
@andreaTP Will you created a new main branch in addition to master where the support to Scala native is drooped? or should we make the PR to master?
I assumed (the migration to fastparse2 and 2.13) was in the same branch
it is. i mean same branch but i wanted fastparse2 to work BEFORE i start changing scala version
let me do something
I'll merge the branch on my master
and start the WIP PR
and support for Scala 2.13 is ready (cc. @FabioPinheiro )but blocked by: wvlet/airframe#868
hey @andreaTP ! I'm getting this when not having the snapshot resolver added with the latest 1.2.6.1 [error] not found: .ivy2/local/org.akka-js/shocon_sjs0.6_2.12/0.5.1-SNAPSHOT/ivys/ivy.xml
[error] not found: https://repo1.maven.org/maven2/org/akka-js/shocon_sjs0.6_2.12/0.5.1-SNAPSHOT/shocon_sjs0.6_2.12-0.5.1-SNAPSHOT.pom
[error] not found: https://repo1.maven.org/maven2/org/akka-js/shocon_sjs0.6_2.12/0.5.1-SNAPSHOT/shocon_sjs0.6_2.12-0.5.1-SNAPSHOT.pom
right
I published without updating shocon :-(
try to add:
"org.akka-js" %%% "shocon" % "0.5.0"
cc. @an-tex
2.2.6.1 published on sonatype
I guess it's on your list but just as I stumbled over it https://github.com/akka-js/akka.js/releases is missing the latest release
Second, I'm going to be running this app on a Kubernetes (AWS Fargate) cluster, which may scale up and down depending on resource utilization. How would the Actor system be affected by this activity? Are there any guideline for setting up an actor system on Kubernetes?
Kubernetes is outside the scope of this project, this is a toolkit to develop applications, and since that akka-cluster is not available how the application handle restarts is all in the logic that you are going to write
There is no real need to hack things around if you stay on the JVM
Also if you wanna write business logic in JS (I'm assuming that's the real reason for those questions) GraalVM provides a polyglot JVM that might help
Do you wanna elaborate on the use case @volkanunsal ?
I have a Node.js codebase that uses worker threads for concurrency, which don't scale well, and I want to use a more lightweight concurrency model. The actors would be used to create a Cometd subscription to a long-polling server for every object inside an S3 bucket. Each actor will be responsible for holding a single subscription, and when a new replica is launched, I want to make sure that the actor system knows which objects are "taken" by an actor, and avoid subscribing that object again.
So my hack is to use
this.path() of the actor, and store that in a Redis backend with the object id as a central database of where each object subscription is located. And I plan to use that in a very limited way, i.e. only as a blacklist, for now.
In one of your talks, you mentioned that we can configure the actor system to use as many worker threads as we like. Is there an example of how to do that?
looks like a pretty heavy production system, I suggest you to switch to something more robust and well maintained like Akka for the JVM, but, well if you continue with Akka.Js, well keep pinging me and I’ll try to do my best to support :-)
Quck question. Is there any support for supervisor strategy?
(from JS I mean) if you use Scala is all there
it should be just a matter of exposing the API through akka.js bindings @volkanunsal
Testkit is pretty limited ATM, basically it’s taking control over the thread of the JS VM, so, you can’t really do nothing with the “real world” since the external calls are not handled.
My suggestion would be to separate the tests:
My suggestion would be to separate the tests:
- use testkit exclusively to test actor’s business logic without interactions with the external world
- use other tests to test exclusively the interactions