ChallengeWhy is this code broken?
The following code looks straightforward, but it has a really subtle issue.
Can you spot what is going on?
You can ignore the error handling here, by the way, the issue isn’t related to handling unexpected errors.
More posts in "Challenge" series:
- (04 Jan 2023) what does this code print?
- (14 Dec 2022) What does this code print?
- (01 Jul 2022) Find the stack smash bug… – answer
- (30 Jun 2022) Find the stack smash bug…
- (03 Jun 2022) Spot the data corruption
- (06 May 2022) Spot the optimization–solution
- (05 May 2022) Spot the optimization
- (06 Apr 2022) Why is this code broken?
- (16 Dec 2021) Find the slow down–answer
- (15 Dec 2021) Find the slow down
- (03 Nov 2021) The code review bug that gives me nightmares–The fix
- (02 Nov 2021) The code review bug that gives me nightmares–the issue
- (01 Nov 2021) The code review bug that gives me nightmares
- (16 Jun 2021) Detecting livelihood in a distributed cluster
- (21 Apr 2020) Generate matching shard id–answer
- (20 Apr 2020) Generate matching shard id
- (02 Jan 2020) Spot the bug in the stream
- (28 Sep 2018) The loop that leaks–Answer
- (27 Sep 2018) The loop that leaks
- (03 Apr 2018) The invisible concurrency bug–Answer
- (02 Apr 2018) The invisible concurrency bug
- (31 Jan 2018) Find the bug in the fix–answer
- (30 Jan 2018) Find the bug in the fix
- (19 Jan 2017) What does this code do?
- (26 Jul 2016) The race condition in the TCP stack, answer
- (25 Jul 2016) The race condition in the TCP stack
- (28 Apr 2015) What is the meaning of this change?
- (26 Sep 2013) Spot the bug
- (27 May 2013) The problem of locking down tasks…
- (17 Oct 2011) Minimum number of round trips
- (23 Aug 2011) Recent Comments with Future Posts
- (02 Aug 2011) Modifying execution approaches
- (29 Apr 2011) Stop the leaks
- (23 Dec 2010) This code should never hit production
- (17 Dec 2010) Your own ThreadLocal
- (03 Dec 2010) Querying relative information with RavenDB
- (29 Jun 2010) Find the bug
- (23 Jun 2010) Dynamically dynamic
- (28 Apr 2010) What killed the application?
- (19 Mar 2010) What does this code do?
- (04 Mar 2010) Robust enumeration over external code
- (16 Feb 2010) Premature optimization, and all of that…
- (12 Feb 2010) Efficient querying
- (10 Feb 2010) Find the resource leak
- (21 Oct 2009) Can you spot the bug?
- (18 Oct 2009) Why is this wrong?
- (17 Oct 2009) Write the check in comment
- (15 Sep 2009) NH Prof Exporting Reports
- (02 Sep 2009) The lazy loaded inheritance many to one association OR/M conundrum
- (01 Sep 2009) Why isn’t select broken?
- (06 Aug 2009) Find the bug fixes
- (26 May 2009) Find the bug
- (14 May 2009) multi threaded test failure
- (11 May 2009) The regex that doesn’t match
- (24 Mar 2009) probability based selection
- (13 Mar 2009) C# Rewriting
- (18 Feb 2009) write a self extracting program
- (04 Sep 2008) Don't stop with the first DSL abstraction
- (02 Aug 2008) What is the problem?
- (28 Jul 2008) What does this code do?
- (26 Jul 2008) Find the bug fix
- (05 Jul 2008) Find the deadlock
- (03 Jul 2008) Find the bug
- (02 Jul 2008) What is wrong with this code
- (05 Jun 2008) why did the tests fail?
- (27 May 2008) Striving for better syntax
- (13 Apr 2008) calling generics without the generic type
- (12 Apr 2008) The directory tree
- (24 Mar 2008) Find the version
- (21 Jan 2008) Strongly typing weakly typed code
- (28 Jun 2007) Windsor Null Object Dependency Facility
Maybe using the same
HttpClientin parallels request can overuse the socket? The
HttpClientis not disposed? Maybe related with bad handling tasks? OpenRead stream is not seeked and is reading the file from the end, causing sending empty file?
I don't thing that will be related with the issue, but why declaring
var file = finstead of doing directly in the foreach
foreach (var file in files)?
flle = fthere is here to avoid variable capture issue, see: https://stackoverflow.com/questions/271440/captured-variable-in-a-loop-in-c-sharp
@Oren Eini - on the
file = f- you haven't had to do that in a
foreachsince c# 5, where they made a breaking change in order to have the captured loop variable work "as expected".
Your code's primary issue is using
Task.Factory.StartNewwith an async delegate. In this case you're waiting on a list of
Task<Task>s, so you're waiting on the wrong thing. I suppose you could unwrap them - but I wouldn't recommend using
StartNewat all. Especially since you're now at its mercy for a task scheduler.
You are correct, and I'm shocked. I wasn't aware of this change.
It doesn't check the status of the response. PostAsync won't throw an exception on a non-successful HTTP status code. A call to EnsureSuccessStatusCode() or similar mechanism should be added. Also why does it use Task.Factory.StartNew? Wouldn't just calling an async method be better?
Task.Factory.StartNewdoesn't have an overload that takes a
Func<Task>, so the
async () => ...lambda is actually an
async voidmethod. It won't actually wait until the transfer is complete.
Those are issues, but actually relatively minor ones. Thomas got it.
My initial impression was that the code is broken by the use of async/await. Happy to see that it was the case :)
Ok, as Thomas got the error, how is the correct solution?
Carsten, Instead of
Ok, thank you. As I never use Task.Factory.StartNew but always Task.Run (just checked all my code), I did not see this difference :-)