I think the rule must be that a Task initializer in a MainActor method runs on the main thread. And all methods of a view controller are MainActor methods by default; plus, I observe that if I declare test2 to be nonisolated, its Task operation runs on a background thread instead of the main thread. … Read more
You want the Microsoft.Bcl.Async package. That’s a properly released, non-CTP package that is stable. This also requires VS2012 since an updated compiler is needed to understand async and await. In theory one could use older tools from VS2010 along with the older CTP library, I’d strongly recommend that you don’t – it has bugs and … Read more
Any time that you need to do an action on a remote server, your program generates the request, sends it, then waits for a response. I will use SaveChanges() and SaveChangesAsync() as an example but the same applies to Find() and FindAsync(). Say you have a list myList of 100+ items that you need to … Read more
The newest version of .Net (v4.6) is adding just that, a built-in Task.CompletedTask: Task completedTask = Task.CompletedTask; That property is implemented as a no-lock singleton so you would almost always be using the same completed task.
I was able to reproduce the issue you are observing. It is clearly a flaw in the Channels library IMHO. Here is my repro: using System; using System.Diagnostics; using System.Threading; using System.Threading.Channels; using System.Threading.Tasks; using System.Threading.Tasks.Dataflow; public static class Program { public static async Task Main() { var channel = Channel.CreateUnbounded<int>(); var bufferBlock = new … Read more
By using code from this article, you can implement the following: public static Task<Task<T>>[] Interleaved<T>(IEnumerable<Task<T>> tasks) { var inputTasks = tasks.ToList(); var buckets = new TaskCompletionSource<Task<T>>[inputTasks.Count]; var results = new Task<Task<T>>[buckets.Length]; for (int i = 0; i < buckets.Length; i++) { buckets[i] = new TaskCompletionSource<Task<T>>(); results[i] = buckets[i].Task; } int nextTaskIndex = -1; Action<Task<T>> continuation … Read more
Wait for any task and return the task if the condition is met. Otherwise wait again for the other tasks until there is no more task to wait for. public static async Task<Task> WhenAny( IEnumerable<Task> tasks, Predicate<Task> condition ) { var tasklist = tasks.ToList(); while ( tasklist.Count > 0 ) { var task = await … Read more
I think document would only be available within page.evaluate (according to puppeteer documentation ) Try: async function gallery(page) { await page.waitFor(3000); await page.evaluate(() => { document.querySelector(‘div.image’).click(); }) }
While you can reuse WithCancellation for both cancellations and timeouts I think it’s an overkill for what you need. A simpler and clearer solution for an async operation timeout would be to await both the actual operation and a timeout task using Task.WhenAny. If the timeout task completes first, you got yourself a timeout. Otherwise, … Read more
You have to set HttpContext.Current.User as well. See this answer and this blog post for more info. Update: Also ensure you are running on .NET 4.5 and have UserTaskFriendlySynchronizationContext set to true.