Matt Galbraith
Matt Galbraith
> Thanks for reporting! > > Yes flushing on every item causes TransmissionSender (default capacity of 3 transmissions at a time) to run out quickly, and SDK will be forced...
> > > Thanks for reporting! > > > Yes flushing on every item causes TransmissionSender (default capacity of 3 transmissions at a time) to run out quickly, and SDK...
OK, I give up, I will let it be closed with no fix.
> @javiercn `node --version` on Musl gives the following immediately after installing node 16.x: > > > /__w/_temp/f5c5264c-3db8-4ff5-8493-cab567b71d45.sh: line 1: /__t/node/16.19.0/x64/bin/node: No such file or directory > > Even though...
@wtgodbe some notes: - Both "good" and "bad" ASP.NET core runs are using sha 83f779a1faf182ba7ceec453fd02869bfba13abb37f17e354ac4fd91338bb4a6 of the `mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.14-WithNode` image, so this doesn't seem likely to be your root cause. -...
sure I'll create a fresh IcM asking for investigation
> It is interesting to me that the only hits we see come from the aspnetcore repo The reason this is specific to AspNet is likely that most .NET Core...
Replied to requests in the IcM; I left step-by-step instructions how to get precise timestamps of what failed and such, hopefully they actually believe us now.
Pinged the IcM, no replies since updating it. Tossing this issue into tracking.
Still reproing, IcM ticket is just claiming they don't have telemetry for the problem still. Added repro from last night to the IcM and pinged the ticket.