and comment it out
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.
next step
everything compiles
well there will be with index names
lol
but don’t think it’s quite there yet.
you can make a storage folder the trigger… so just putting the postdata there would trigger it to run.
can run C# code and it scales on its own based on triggers.
but it looks like you have to just run some c# code from a text box vs triggering a exe or being able to use full assemblies.
guess you can add nuget packages and external references
but you have to put the core logic in a .csx script file.
hmm
won’t be live until 8pm tonight
:)