ondravondra

Is there estimation when this will be merged and available on nuget?

I would use it too. Currently I link to a submodule pointing to dev branch which is definitely not the best solution.

We also ran into the issue of massive spike in memory and cpu usage when building. A way to limit parallelism is a must have for us.

The primary key could be identified by anonymous type or lambda expression, EF uses `Expression identifierExpression`. It could be upsert, but many DBs do not support it and it really...

I wrote an extension for our company project. It merges the data comparing set of columns for each row. It reuses existing fluent migrator code. Sample usage: ``` csharp Merge.IntoTable("role").Row(new...

is this library even supported anymore ? this caused critical error on our production!!! how is this not fixed for almost 2 years?

This behaviour can be fixed by reordering the case labels, e.g.: ```private T GetResult(object reply) { switch (reply) { case T wtv: return wtv; case null: return default; case Status.Failure...

> reproduction spec we'd be happy to merge it. We can write something ourselves too - but totally up to you. I am afraid I won't be able to write...

It seems that the framework relies on this behavior. For example, test `Inbox_Receive_will_timeout_gracefully_if_timeout_is_already_expired` uses `Akka.Actor.Inbox.Receive` that calls `Ask` and expects the result to be `Status.Failure`. A bit of a pickle...

It now points to 1.3.1, still wrong, caused error in our production system because unpkg fetches this version instead of the real last version.