actor-model
Here are 517 public repositories matching this topic...
-
Updated
Feb 13, 2022 - C#
Your issue may already be reported!
Please search on the Actix issue tracker before creating one.
Expected Behavior
WeakRecipient
has Clone, similar to Addr
, WeakAddr
, and Recipient
.
Curre
-
Updated
Aug 10, 2021 - Rust
We've currently turned them off as they are randomly failing in CI but not locally.
We need to get them fixed in CI and turned back on.
-
Updated
Feb 13, 2022 - C#
-
Updated
Feb 14, 2022 - Go
-
Updated
Sep 26, 2021 - Objective-C
-
Updated
Feb 13, 2022 - C++
-
Updated
Jun 15, 2021 - Kotlin
-
Updated
Feb 12, 2022 - Go
-
Updated
Feb 12, 2022 - Rust
-
Updated
Feb 7, 2022 - Python
-
Updated
Jan 28, 2022 - TypeScript
-
Updated
Feb 4, 2022 - C#
-
Updated
Nov 24, 2021 - Rust
Currently, WebSocket is working for client/server side. However, the browsers do not allow to create tcp connections direclty (which is the current implementation based). Instead, the web-sys
must be used.
- Use a different WebSocket implementation if the target is
wasm
. - wasm example of a client.
-
Updated
Oct 13, 2021 - C#
-
Updated
Oct 14, 2021 - Go
-
Updated
Dec 3, 2021 - Java
-
Updated
Feb 5, 2022 - C
-
Updated
Feb 9, 2022 - Java
-
Updated
Jan 28, 2022 - Erlang
With CAF 0.18, actor names must be constant strings. The active and passive partition carry their human-readable name in the variable self->state.name
already.
In active_partition.cpp
and passive_partition.cpp
we currently have a lot of log messages using the actor name rather than the human-readable partition name. We need to change them like this:
VAST_DEBUG("{} persists p
-
Updated
Feb 14, 2022 - C
-
Updated
Aug 13, 2020 - Python
-
Updated
Jan 13, 2022 - C++
-
Updated
Jan 27, 2021 - Python
-
Updated
Feb 3, 2022 - Rust
-
Updated
Dec 25, 2018 - Go
Improve this page
Add a description, image, and links to the actor-model topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the actor-model topic, visit your repo's landing page and select "manage topics."
current
return queueOfferResult == QueueOfferResult.enqueued();