there were a few things
the elastic guys have been unresponsive
guess I’m going to have to progress without them
I caught the flu or we could have done this on Tuesday
sounds good
I hope you feel better
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
not DI and general helper lib.
cloud app abstractions and impls.
cause you should be
talking to greg from elastic now
we WILL have to go to elastic 2.x before elastic 5
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."
learned a few things today
basically it’s pretty much impossible to do nicely
wonder if we should think about hosting our jobs that way.