Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Eric J. Smith
@ejsmith
where is it at.
Blake Niemyjski
@niemyjski
in a branch
want me to update it
the branch
Eric J. Smith
@ejsmith
yes, I know that… but I want to know what is blocking it from moving forward.
Blake Niemyjski
@niemyjski
looking
there were a few things
the elastic guys have been unresponsive
guess I’m going to have to progress without them
Eric J. Smith
@ejsmith
niemyjskify those sons of bitches.
Lord-Hasek
@Lord-Hasek
Good day everyone, @niemyjski when you have some free time would you be able to help take a look at our recalcitrant setup of Exceptionless?
Blake Niemyjski
@niemyjski
Yeah, when are you free today?
Lord-Hasek
@Lord-Hasek
lets say around 1:00 PM central time, have a meeting that is supposed to go through lunch
I caught the flu or we could have done this on Tuesday
Blake Niemyjski
@niemyjski
ok
sounds good
I hope you feel better
Lord-Hasek
@Lord-Hasek
Ok cool, then 1:00 it is :)
Blake Niemyjski
@niemyjski
@ejsmith did you get rid of some typehelper stuff in foundatio?
    private ICollection<IMigration> GetAllMigrations() {
        var migrationTypes = TypeHelper.GetDerivedTypes<IMigration>(new[] { typeof(IMigration).Assembly });
        return migrationTypes
            .Select(migrationType => (IMigration)_container.GetService(migrationType))
            .OrderBy(m => m.Version)
            .ToList();
    }
GetDerivedTypes no longer works
you removed it
guess we should get that from di
or what
Eric J. Smith
@ejsmith
yeah, tying to stay focused on what Foundatio is supposed to be.
not DI and general helper lib.
cloud app abstractions and impls.
Blake Niemyjski
@niemyjski
I’m goign to mark that as a todo
and comment it out
Blake Niemyjski
@niemyjski
@ejsmith are you updated to use foundatio.repositories
cause you should be
Eric J. Smith
@ejsmith
nope, but I am going to do that as part of updating our stuff to work on 2.0
Blake Niemyjski
@niemyjski
ok
talking to greg from elastic now
Blake Niemyjski
@niemyjski
@ejsmith
we WILL have to go to elastic 2.x before elastic 5
Eric J. Smith
@ejsmith
they are killing us
Lord-Hasek
@Lord-Hasek
@niemyjski I messaged you a link to a join.me so we can continue troubleshooting
Blake Niemyjski
@niemyjski
sounds good
Blake Niemyjski
@niemyjski
he gets all the clicks
Sander Rijken
@srijken
Been fighting with calling async/await code from an Rx Subscribe(Observer). Problem was that IObserver only contains void OnNext(T item). Because there’s nothing that returns task, you can’t do .Subscribe(async item => { await ProcessAsync(item) }).
it’s fixed now by doing: .Subscribe(item => { ProcessAsync(item).GetAwaiter().Result(); })
in the process I learned the difference between Task.Wait() and Task.Result vs Task.GetAwaiter().Result()
it’s explained best over here: aspnet/Security#59
"One last remark: you should avoid using Task.Result and Task.Wait as much as possible as they always encapsulate the inner exception in an AggregateException and replace the message by a generic one (One or more errors occurred), which makes debugging harder. Even if the synchronous version shouldn't be used that often, you should strongly consider using Task.GetAwaiter().GetResult() instead."
Blake Niemyjski
@niemyjski
+1
learned a few things today
Eric J. Smith
@ejsmith
?
Sander Rijken
@srijken
I learned that I’ve got a lot to learn about mixing Rx and async/await