Closed jaredpar closed 10 months ago
@rainersigwald this is almost certainly why complog was failing to run on the customer machine. Their scenario is for a new version of VS, same I used locally, and it's seemingly triggering a new path in the forward compat code here.
can you try using 2.2.169? I made a fix recently to always call Strings.Initialize(). Hopefully it will fix your case? Need to update to latest for other reasons anyway.
This is the fix I made: https://github.com/KirillOsenkov/MSBuildStructuredLog/commit/83a97d05a5e02af24ad0e418d83b27840cdd8c14
does your version have it?
No don't have that in the repro case. Case where it doesn't repro does have it.
Just assuming that is the fix then. Thanks!
fyi @JanKrivanek. Thanks @KirillOsenkov!
fyi @JanKrivanek. Thanks @KirillOsenkov!
Thx for heads-up. Yeah this is what we've been batling with in arcade binlogs redaction step end of last year: https://github.com/KirillOsenkov/MSBuildStructuredLog/issues/736
Using the 2.2.155 version of the NuPkg I'm starting to see
ArgumentNullExceptions
when reading newer log files. The stack of the error is:Digging into the crash it looks like
Strings.PropertyReAssignment
isnull
here. Hard to see all the values in the debugger but seems like everystatic
member inStrings
isnull
here. Looking through the code seems there is an expectation thatStrings.Initalize
is called before this code path is hit.Think I can likely fix this on my end by just calling this but never had to do this before. Have I just been getting lucky all this time?
Note: this is not easy to reproduce when running from source. It repros 100% of the time when I use my published global tool. Not sure if running from an apphost is changing anything here. Wanted to add that here in case it helps explain what is going on.