-
-
Notifications
You must be signed in to change notification settings - Fork 515
Issues: asynkron/protoactor-go
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Bad performance test ping/pong messages
investigate
up for grabs
#838
opened Apr 12, 2023 by
kharitonov1995
remote.Watch can't support one local actor monitor many actor in the same remote endpoint
#172
opened Sep 7, 2017 by
alex023
How can I make ‘Spawn’ return the error that occurred when 'Started' is received?
#1105
opened Apr 19, 2024 by
DustOak
Error while trying to read a message in Go client sent by C# server
#724
opened Sep 20, 2022 by
gustavokorp
How to rolling update protoactor cluster without losing states?
question
t:cluster
#404
opened Oct 14, 2020 by
cupen
[Feature] Allow to run StopFuture and PoisonFuture with a custom timeout
#351
opened Aug 14, 2019 by
melaurent
It might be better to remove
actor.stopping
from the application layer
bug
#214
opened Jan 5, 2018 by
alex023
The framework needs to determine the nil structure implementation of actor.Actor
#168
opened Aug 28, 2017 by
alex023
Error when sending large message to remote actors
up for grabs
#1114
opened May 20, 2024 by
iori2333
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.