diagnostics | Topic Model Diagnostics | Topic Modeling library

Downgrading Xcode from 13.3 to 13.2.1 solved my problems.

As Lasse V. Karslen already commented, your code will trigger a compiler error CS0182. Next problem is the required format for AssemblyVersion - major[.minor[.build[.revision]]], there are other assembly metadata fields that can be used for strings - e.g. InformationalVersion.

There is more than one way to add assembly meta data while building... there are probably more then these five:

• assembly attribute
• dotnet-cli parameter
• msbuild parameter
• csproj config entry
• Build Events / Scripting is also a way to reach your goal, but is more fiddeling.

The problem with the assembly attribute is that it need to be constant expression. That is not straight forward to achieve, but Gitinfo managed to serve a solution. An other disadvantage is the need to disable the compiler to generate the AssemblyInfo.cs that will break writing some values configured in csproj to the final assembly.

Install gitinfo

This package requires go v1.16, please upgrade your go version or use the appropriate docker builder.

You can add a dummy property that is used during serialization that handles this.

• Add a new property with the same signature, but flag it with JsonPropertyNameAttribute to ensure it is being serialized with the correct name, and also with the JsonIgnoreAttribute so that it will not be serialized when it returns null.
• The original property you mark with JsonIgnore, unconditionally, so that it will never be serialized itself
• This dummy property would return null (and thus be ignored) when the actual property contains an empty list, otherwise it would return that (non-empty) list
• Writes to the dummy property just writes to the actual property

Something like this:

Add try/catch similar to the above around IHostBulder.Build() in any .NET/EF Core 6.0 RC2 project, and attempt to add a migration can reproduce the issue.

We can fix the issue with the following :

Looks like you have resolved the embedding part of your question and are left with just the deletion of the extracted DLLs.

Because the DLL is inuse but your own process, unless you are able to uload the DLL successfully, I dont think you will be able to delete the DLL.

1st Potential Option

One thing you could try and do is schedule the deletion of the file after reboot. This SO post explains how to do that using P/Invoke and MoveFileEx.

The example they give is as follows:

After contacting Apple Developer Technical Support (DTS) regarding this issue, they provided me with the following guidance.

Regarding "insufficient usage data available" for energy logs accessible via the Xcode organizer:

DTS indicated that they do not publish the thresholds for active users and usage logs would be expected to be present if you have more that a few thousand active users consistently on each version of your app. If your app meets this criteria and still does not show energy logs, DTS recommended opening a bug report with them.

Regarding how to collect energy log data for your app:

DTS recommended using MetricKit to get daily metric payloads. Payloads are delivered to your app every 24 hours and it is then possible to consume them and send them off device.

The instantiation of this is vey basic and can be as simple as:

For a built-in compound assignment operator $= the expression A $= B behaves identical to an expression A = A $ B, except that A is evaluated only once. All promotions and other usual arithmetic conversions and converting back to the original type still happen.

Therefore it shouldn't be expected that the warnings differ between short avg1 = sum / count; and tmp /= count;.

A conversion from int to short happens in each case. So a conversion warning would be appropriate in either case.

However, the documentation of GCC warning flags says specifically that conversions back from arithmetic on small types which are promoted is excluded from the -Wconversion flag. GCC offers the -Warith-conversion flag to include such cases nonetheless. With it all arithmetic in your examples generates a warning.

Also note that this exception to -Wconversion has been introduced only with GCC 10. For some more context on it, the bug report from which it was introduced is here.

It seems that Clang has always been more lenient on these cases than GCC. See for example this issue and this issue.

For / in GCC -fsanitize=undefined seems to break the exception that -Wconversion is supposed to have. It seems to me that this is related to the undefined behavior sanitizer adding a null-value check specifically for division. Maybe, after this transformation, the warning flag logic doesn't recognize it as direct arithmetic on the smaller type anymore.

If my understanding of the intended behavior of the warning flags is correct, I would say that this looks unintended and thus is a bug.

Even though nobody posted an answer, from the comment section I could conclude that:

• Nobody found any undefined behavior in the bug repro code.
• At least some of you were able to reproduce the undesired behavior.

So I filed a bug report against Visual Studio 2019.

The Microsoft team confirmed the problem.

However, unfortunately it seems like Visual Studio 2019 will not receive a bug fix because Visual Studio 2022 seemingly does not have the bug. Apparently, the most recent version not having that particular bug is good enough for Microsoft's quality standards.

I find this disappointing because I think that the correctness of a compiler is essential and Visual Studio 2022 has just been released with new features and therefore probably contains new bugs. So there is no real "stable version" (one is cutting edge, the other one doesn't get bug fixes). But I guess we have to live with that or choose a different, more stable compiler.