Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 09:22
    ismaelhamed commented #3863
  • Oct 19 23:39
    valdisz synchronize #3889
  • Oct 19 23:08
    edvinasz commented #2947
  • Oct 19 13:36
    Aaronontheweb commented #3973
  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3995
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump BenchmarkDotNet from 0.10.… (compare)

  • Oct 19 13:34
    dependabot-preview[bot] edited #3995
  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3993
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump Google.Protobuf from 3.9.1… (compare)

  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3991
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump Microsoft.Extensions.Depen… (compare)

  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3989
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump ApiApprover from 3.0.1 to … (compare)

  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3992
  • Oct 19 13:34
    dependabot-preview[bot] edited #3993
  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3985
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump System.Reflection.Emit fro… (compare)

  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3986
  • Oct 19 13:34

    dependabot-preview[bot] on nuget

    Bump FsCheck.Xunit from 2.9.0 t… (compare)

  • Oct 19 13:34
    dependabot-preview[bot] synchronize #3983
Bartosz Sypytkowski
@Horusiath
@andreyleskov in general querying over all persistence ids is not a good idea - this is something not provided by default, as persistence queries are designed to tolerate partitions (so you can have events for persistence ids from 1 to 100 on one machine and from 101 to 200 on other)
if I'm correct event store also doesn't offer an ability to query over "all" streams
Andrey Leskov
@andreyleskov
@Horusiath sure, querying all persistence id is not a good idea, I'm talking about be notified when a new message is saved by journal, regardless its persistence Id.
btw, SqlJournal current implementation queries for all persistence ids on startup ) Had a few problems with on on production. : https://github.com/akkadotnet/akka.net/blob/ecd0ede93c7fe7b888703fb54c03e2bcec39ef6f/src/contrib/persistence/Akka.Persistence.Sql.Common/Journal/QueryExecutor.cs#L159
Bartosz Sypytkowski
@Horusiath
I suspected, this could be a problem in the future
just for curiosity, how many persistence ids do you have on production?
Sergey Prytkov
@Rattenkrieg
Hello guys, congrats with 1.1.2. But what is the status of pull #2277 and related issues? Is it fixed on Wire side?
Bartosz Sypytkowski
@Horusiath
strange, from what I know Wire should be able to serialize types marked as internal. @rogeralsing ?
Aaron Stannard
@Aaronontheweb
@ronnieoverby good question
mind logging an issue for that?
Andrey Leskov
@andreyleskov
@Horusiath ~ 350 000 unique ids and ~ 2 500 000 events in total
Problem was related to Azure sql db performance, we are far from theoretical limit )
Sergey Prytkov
@Rattenkrieg
Wire now is 0.8.1, but I haven't found any release notes
this issue reported while Wire was at 0.8.0
Andrey Leskov
@andreyleskov
@Horusiath @Silv3rcircl3 will such functionality be valuable for project? If yes I will create a PR.
Bartosz Sypytkowski
@Horusiath
@andreyleskov I think, you can add it as an issue on github - this will be at least point to start a discussion
(also if I'm right, there might be already something similar available)
Roger Johansson
@rogeralsing
There are tests in the Wire test suite that creates internal types, any specific details here
?
Alex Valuyskiy
@alexvaluyskiy
@rogeralsing look at this PR akkadotnet/akka.net#2277
Roger Johansson
@rogeralsing
Oooh, the array serializer fails on internal types... Didnt know that. Ill provide a fix asap
Ronnie Overby
@ronnieoverby
@Aaronontheweb logged. Man. I'm on a role.
Aaron Stannard
@Aaronontheweb
@ronnieoverby there's lots of stuff to test :p
stevemesser
@stevemesser
See
Arsene T. Gandote
@Tochemey
Hello gurus. is Akka on Net.Core
Arsene T. Gandote
@Tochemey
Tx
Arsene T. Gandote
@Tochemey
@Silv3rcircl3 I believe I can use it on Net.Core even though there are some works to be done.
Marc Piechura
@marcpiechura
@Tochemey sure, but keep in mind that it is not even a official beta. @alexvaluyskiy can tell you more about the current status
Arsene T. Gandote
@Tochemey
Thank you
Robert Stiff
@uatec
aloha
Jason Bock
@JasonBock
Hey, got a question about hosting an actor system in Azure. I tried following this: http://getakka.net/docs/deployment-scenarios/Azure%20PaaS%20Worker%20Role.
But when I get to my ActorSystem.Create() call, I get this error: Could not load type 'Akka.Util.RuntimeDetector' from assembly 'Akka, Version=1.1.1.27, Culture=neutral, PublicKeyToken=null'.
Any ideas?
Jason Bock
@JasonBock
Well, I realized some of my NuGet packages were not updated, so I made sure all my projects had the most recent versions and that removed the error. Now I'm having an issue where the client can't talk to the system because Akka thinks the address is incorrect. Not sure what I need to do in the worker role to get all the configuration right so a client can talk to the system.
Chris Martin
@trbngr
How in the hell do you guys provision a cluster in Azure? I thinking multiple instances in a cloud service. We have to know the ports ahead of time to create the endpoint. But how do you assign a port to an instance? Maddening....
Jason Bock
@JasonBock
I'm using RoleEnvironment.CurrentRoleInstance.InstanceEndpoints["UserActorEndpoint"] to get the Address and Port but even putting that into my HOCON configuration dynamically doesn't seem to work. The client still gets an error
akka.tcp://KeyWatcherListener@localhost:4545 ---> Akka.Remote.Transport.InvalidAssociationException: Association failure ---> Akka.Remote.Transport.AkkaProtocolException: The remote system explicitly disassociated (reason unknown).
That's the error I'm getting. Changing that to "127.0.0.1" doesn't matter (I'm doing this locally first)
Chris Martin
@trbngr
what's your helios.tcp config look like?
Jason Bock
@JasonBock
        var endpoint = RoleEnvironment.CurrentRoleInstance.InstanceEndpoints["UserActorEndpoint"];
        var config = ConfigurationFactory.ParseString($@"
akka {{
actor {{
provider = ""Akka.Remote.RemoteActorRefProvider, Akka.Remote""
}}
remote {{
helios.tcp {{
port = {endpoint.IPEndpoint.Port}
hostname = {endpoint.IPEndpoint.Address}
}}
}}
}}
");
Chris Martin
@trbngr
I'm assuming single instance.
Jason Bock
@JasonBock
sorry for the formatting
Chris Martin
@trbngr
cool
Jason Bock
@JasonBock
this.system = ActorSystem.Create("KeyWatcherListener", config);
That's what I do in my worker role, and that works (at least it doesn't fail)
but the client app gets the exception when it tries to talk to the system.
Chris Martin
@trbngr
so you get a unique port per instance?
Chris Martin
@trbngr
I see now. I was setting up NAT with public-hostname which may just need to be the IPAddress
and not the public IP of the cloud service
Chris Martin
@trbngr
BTW: my config
Jason Bock
@JasonBock
This is just using the local Azure compute emulator