Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 00:55
    Aaronontheweb opened #4273
  • 00:42
    Arkatufus synchronize #4253
  • 00:40
    Arkatufus commented #4253
  • 00:37
    Arkatufus synchronize #4253
  • 00:32
    Aaronontheweb synchronize #4270
  • 00:24
    Aaronontheweb milestoned #3735
  • 00:24
    Aaronontheweb demilestoned #3735
  • 00:24

    Aaronontheweb on dev

    unregister AppDomain.ProcessExi… (compare)

  • 00:24
    Aaronontheweb closed #3846
  • 00:24
    Aaronontheweb closed #3735
  • Feb 27 23:27
    Aaronontheweb edited #4272
  • Feb 27 23:27
    Aaronontheweb edited #4272
  • Feb 27 23:26
    Aaronontheweb opened #4272
  • Feb 27 23:14
    Aaronontheweb closed #2229
  • Feb 27 23:14
    Aaronontheweb commented #2229
  • Feb 27 23:14
    Aaronontheweb commented #3791
  • Feb 27 23:13
    Aaronontheweb closed #3791
  • Feb 27 23:13
    Aaronontheweb commented #3791
  • Feb 27 23:13
    Aaronontheweb demilestoned #4120
  • Feb 27 23:12
    Aaronontheweb labeled #4120
Aaron Stannard
@Aaronontheweb
@creepone but if this is causing some unintended side effects, please file an issue!
I think @stefansedich recommended for Ninject that you bind things .InScope()
@bruinbrown > I've got the child process debugging power tools but it doesn't seem to attach the debugger on child processes. Any tips on running them as well?
there's a little trick to this that isn't very straightforward
blob
Aaron Stannard
@Aaronontheweb
so you want to open that menu, Debug --> Other Debug Targets --> Child Process Debugging Settings
and then configure it like this
blob
make sure Enable child process debugging is checked
and add NodeTestRunner.exe as an entry, also checked, with action Attach debugger
then press Save
Suhas Chatekar
@schatekar
@Aaronontheweb could you stick that to a gist or an issue? so that it is easy to refer to in future?
on a second thought, I could do that as well ;)
Aaron Stannard
@Aaronontheweb
that way we could include it in the official documentation
@GraemeBradbury I'm probably going to end up incorporating #1261 into a larger PR that matches the multi-node test runner itself
going to take some work, but basically I need to get throttling to work
Graeme Bradbury
@GraemeBradbury
@Aaronontheweb cool, if there is anything i can help with that just holler.
Aaron Stannard
@Aaronontheweb
will do! I think I'm close to tracking the issue down
turns out there's a meta-spec for exactly this
Suhas Chatekar
@schatekar
@Aaronontheweb raised #111 for documentation issue
that is on this repo - akkadotnet/getakka.net#111
@Aaronontheweb could you assign that to me?
Anthony Brown
@bruinbrown
@Aaronontheweb that's exactly what I've got, I'm going to try removing the extension and reinstalling it
Aaron Stannard
@Aaronontheweb
@schatekar done
the biggest thing we could do to improve usability with the multi-node test runner is this: akkadotnet/akka.net#1196
Aaron Stannard
@Aaronontheweb
for #1196, we already emit a .JSON file to disk that's just a serialized version of this object https://github.com/akkadotnet/akka.net/blob/dev/src/core/Akka.MultiNodeTestRunner.Shared/Reporting/TestRunTree.cs
I'm running a multi-node test locally right now so I can add one of the output files to the issue :p
but what we'd want to do is change it such that instead of outputting just the JSON file
actually output a static webpage that renders that data into concurrent timelines for each test / node
so we can sort out what's happening, individually, across each node
that'd make it a lot easier to figure out what's going on, right?
Graeme Bradbury
@GraemeBradbury
I had a quick look at that. Found http://visjs.org/examples/timeline/groups/groups.html so would just be a case of creating the data as visjs data structure and then spitting out into a html file.
Aaron Stannard
@Aaronontheweb
@GraemeBradbury looks like a great fit!
can we make an adapter for TestRunTree that will render it into a VisJS structure?
btw... love that I can use the scrollwheel for that :p
Graeme Bradbury
@GraemeBradbury
don't see why not. It's just a different json data strcuture
Aaron Stannard
@Aaronontheweb
cool, would you mind adding that suggestion about VisJS to the issue comments?
and would one of you brave souls like to claim that issue? :p
Suhas Chatekar
@schatekar
would d3.js be better in this situation?
Graeme Bradbury
@GraemeBradbury
I'm on holiday next week so i'll have a look after that if no one else does it before then :-)
@schatekar I've not used either before so don't know which is best. visjs has an example that's almost exactly what we want.
ok, i'm off home to download Shadowrun:HK so I may be on during the hols but otherwise have fun everyone.
Aaron Stannard
@Aaronontheweb
take care @GraemeBradbury!
Tomas Vana
@creepone
@Aaronontheweb As I understand it, the problem is that the activation block forces everything to use InScope(), overriding all the original settings. That makes it impossible to reuse global services or any shared infrastructure between actors -> every dependency becomes implicitly owned by the actor (see e.g. this article).
Roger Johansson
@rogeralsing
@GraemeBradbury I use VisJs for my cluster visualzer. love that lib!
Aaron Stannard
@Aaronontheweb
@creepone we might have made a mistake then - could you create a Github issue for it?
we did have a lot of discussion about this on #942 and the PR for those changes was open for a couple of weeks while we worked out the details
but the standard is set now for how resources are expected to behave - we still need docs on the website explaining what those are and what the right configuration options are for each container
I'm personally of the opinion that Autofac is the only container that appears to have correct-by-default behavior - the rest of the containers are susceptible to resource leaks by default