Richard Astbury
Richard Astbury
I'd be happy for it just to block until the result is complete.
...another option is the client registers a webhook, which you call upon completion. I prefer a simple blocking HTTP call, it's not like you're keeping the client waiting that long...
I'll clarify my position. From the perspective of the consumer (I think) it's easier to have a single http get to retrieve the results, which are returned on the response...
I found that `uploader.removeAllEventListeners()` seems to do the job of at least disabling the uploader.
This looks like a great idea. It would be awesome to overlay call counts, exceptions, latency etc..
something like the map you get in Application Insights 
There is now a dotnet 6.0 runner, which might fix the failing CI
well it builds @ElanHasson
something like '10 reminders due in the next hour'
Yes, it's webpack (CreateReactApp). I'll need to add a CORS rule in for local dev.