Caelan

I would argue that neither a configuration option nor detecting the package size will be helpful. Even a relatively small package (eg. 20-50mb) can take upwards of 30s to install...

I agree @kenjenkins, providing an option to ignore the port in route matching would be a simple solution to the problem and would work perfectly. @wasaga The problem for me...

I don't know about any challenges that are angular specific, but identifying what url param goes to what component shouldn't be a big pain. As far as I know we...

@niemyjski For the reason you mentioned (billing) I think groups and teams might be a better idea than doing exceptionless/Exceptionless.UI#141. Because an organization is the billing entity there really shouldn't...

@niemyjski I can't speak for the author of this issue, I think permissions is an unrelated issue to this one. exceptionless/Exceptionless.UI#230 may or may not solve the grouping aspect of...

bulk changes are a non-issue really as long as we use an anchor, I could be on page 5, and all the events from pages 2-4 could get deleted and...

I'm not entirely sure what the confusion is - maybe I'm missing something? I'd imagine an endpoint that takes an `anchorId` (an id of an event or stack) as a...

ElasticSearch supports this natively, so we just need to expose this instead of a page number: https://www.elastic.co/guide/en/elasticsearch/reference/master/search-request-search-after.html

fwiw, a scrolling API is not what you'd wan't either.`search_after` is very different and is exactly what you want. You want to retrieve all results that come _after_ a specific...

It will need to be SUBPROCESS_NULL on windows, I suspect a better fix will be to check if cwd is null, and if so, skip the call to `posix_spawn_file_actions_addchdir_np`. I'll...