Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 18 19:12
    IgorFedchenko commented #3998
  • Oct 18 18:29
    Aaronontheweb commented #3998
  • Oct 18 18:24
    Aaronontheweb opened #3998
  • Oct 18 18:19

    Aaronontheweb on fix-readme-logo

    (compare)

  • Oct 18 17:30
    Aaronontheweb milestoned #3973
  • Oct 18 16:38
    jaydeboer opened #3997
  • Oct 18 15:53
    Aaronontheweb synchronize #3973
  • Oct 18 15:52

    dependabot-preview[bot] on dev

    Bump Microsoft.NET.Test.Sdk fro… (compare)

  • Oct 18 15:52

    dependabot-preview[bot] on nuget

    (compare)

  • Oct 18 15:52
    dependabot-preview[bot] closed #3996
  • Oct 18 15:52
    Aaronontheweb commented #3996
  • Oct 18 14:53
    Aaronontheweb commented #3973
  • Oct 18 12:20
    IgorFedchenko commented #3973
  • Oct 18 12:17
    IgorFedchenko commented #3973
  • Oct 18 11:58
    IgorFedchenko synchronize #3973
  • Oct 18 11:33
    IgorFedchenko commented #3973
  • Oct 18 11:25
    IgorFedchenko synchronize #3973
  • Oct 18 07:04
    dependabot-preview[bot] labeled #3996
  • Oct 18 07:04
    dependabot-preview[bot] opened #3996
  • Oct 18 07:04

    dependabot-preview[bot] on nuget

    Bump Microsoft.NET.Test.Sdk fro… (compare)

Aaron Stannard
@Aaronontheweb
it's something we've discussed with @rkuhn as something to consider for both Akkas in the future
definitely not a "hack this up over a weekend" sort of feature, as it has the potential to break location transparency
since it requires DI containers on both ends of the wire to have the same dependencies
errr, the appropriate configuration
so yeah, let's discuss it
could you create a discussion issue for it?
Bartosz Sypytkowski
@Horusiath
yes
Aaron Stannard
@Aaronontheweb
thanks bud :+1:
I think it'd be a kick ass feature - since as you've discovered right now, the status quo breaks location transparency quite easily too :p
Bartosz Sypytkowski
@Horusiath
yes, but you could say that requirement to have the libraries to share actor definitions across the nodes also breaks location transparency
Aaron Stannard
@Aaronontheweb
yeah, that's true I suppose
same of message types
although I guess the idea is that if you're going to have location transparency, you'd assume that you'd have 100% of the messages and actors you want to use defined locally too
Bartosz Sypytkowski
@Horusiath
personaly I don't feel need for DI in akka, but tomorrow I'll try to evangelize my team to use it, and probably it will be on the wishlist :P
Aaron Stannard
@Aaronontheweb
and in order to make that work over the network, you'd expect that code to be deployed and ready there
@Horusiath I know that feel bro
during a bunch of our consulting calls we're pitching customers on ditching SQL Server and ACID for certain workloads
and even while SQL Server is literally the single point of failure that is causing massive scaling problems for some of these guys
Aaron Stannard
@Aaronontheweb
they're still really skeptical of the alternatives :p
point being: I'm with you, I'd probably not use DI with actors
but it's hard asking people to throw away ALL of the tools they're used to using at once, so I understand why there's resistance lol :p
Aaron Stannard
@Aaronontheweb
@GraemeBradbury yep, think I've figured it out - found some issues with Throttling and Blackhole still. Looks like we basically didn't implement that at the time we wrote the multi-node testkit, because none of those transport adapters were implemented yet
looks like I'll have my own PR in for this - have some multinode testkit meta-tests I need to port :p
Suhas Chatekar
@schatekar
Folks, does the following command work for you
build multinodetests spec-assembly=remote
Aaron Stannard
@Aaronontheweb
not yet - I have to pull in #1265 for that
Suhas Chatekar
@schatekar
I get following output when I run the above command
Checking for updates from https://www.nuget.org/api/v2/.
Currently running NuGet.exe 2.8.6.
NuGet.exe is up to date.
Package "FAKE" is already installed.
Package "xunit.runner.console" is already installed.
Package "nunit.runners" is already installed.
Assembly version: 1.0.5
Nuget version; 1.0.5

Building project with version: LocalBuild
Shortened DependencyGraph for Target MultiNodeTests:
<== MultiNodeTests

The resulting target order is:
 - MultiNodeTests
Starting Target: MultiNodeTests
Using MultiNodeTestRunner: e:\Source\akka.net\src\core\Akka.MultiNodeTestRunner\bin\Debug\Akka.MultiNodeTestRunner.exe
Finished Target: MultiNodeTests

---------------------------------------------------------------------
Build Time Report
---------------------------------------------------------------------
Target           Duration
------           --------
MultiNodeTests   00:00:00.4902232
Total:           00:00:00.5702187
Status:          Ok
---------------------------------------------------------------------
Aaron Stannard
@Aaronontheweb
hmmm... that's odd
let me double check the FAKE file
James Andrew-Smith
@james-andrewsmith
@Aaronontheweb Thank you for the example, that makes a lot of sense. I'm new to Akka.net but it seems like the tools are there to build this pattern with an actor per API account with a scheduler attached. Thank you for taking the time to answer!
Aaron Stannard
@Aaronontheweb
@james-andrewsmith you're welcome! please feel free to ask questions here any time
we try to make sure that all of them get answered, and if that doesn't work lots of people actively answer akka.net-tagged questions on StackOverflow too
to answer your question @schatekar
this is suspicious :p
Shortened DependencyGraph for Target MultiNodeTests:
<== MultiNodeTests
ah wait
I stand corrected
that's technically correct with what's in the FAKE file today
but a big goof on my part - reason why it's probably not running for you right now is that the MultiNodeTests step does technically depend on BuildRelease
otherwise it won't find any of the test assemblies inside a bin/Release folder
so could you send a PR that modifies the FAKE script to do the following:
// build dependencies
"Clean" ==> "AssemblyInfo" ==> "RestorePackages" ==> "Build" ==> "CopyOutput" ==> "BuildRelease"

// tests dependencies
"CleanTests" ==> "RunTests"
"BuildRelease" ==> "CleanTests" ==> "MultiNodeTests"
the last line is the one we need to add
the others are already inside the FAKE file
Aaron Stannard
@Aaronontheweb
could you add that and see if this resolves your issue?
and if so, send that in as a PR to fix the FAKE script :shipit:
Suhas Chatekar
@schatekar
sure
are dependencies going from right to left?
never used FAKE before
Aaron Stannard
@Aaronontheweb
"MultiNodeTests" depends on the things to its left
yeah, it was trippy for me too at first :p