Ilona Tomkowicz
Ilona Tomkowicz
Head on 0ef117e33e711950b0e6ac41c8fdb87503167e75, all of above are passing.
Might be random race as @pavelsavara says it was passing on CI re-run.
I am adding some new cases affected by this error. 1) Installer Build and Test coreclr Linux_arm64 Release, [Pipelines - Run 20220314.2](https://dev.azure.com/dnceng/public/_build/results?buildId=1661723&view=logs&j=36f5df04-f069-50e9-49af-755a9549bd25&t=1b35d20c-729d-5c6d-6d86-1d8eb0d873b7). error: ``` docker run -v /mnt/vss/_work/1/s:/root/runtime -w=/root/runtime -e...
> Is there a minimal repro someone can provide for this? I am hitting it every time on main, HEAD: cc9d46546b8e72b34a5f387a5ec9615197d79f1f, running: WasmBuildTests InvariantGlobalizationTests for Browser, wasm. If we add...
Current behavior - no internal members:  while in the reply we are including them: ``` {[Result: IsOk: True, IsErr: False, Value: { "result": [ { "get": { "type": "function",...
Mininal repro: ``` public class MyObject { public int publicVar => 0; internal int internalVar => 1; protected int protectedVar => 2; private int privateVar => 3; } private void...
The reason: while grouping the members by protection level we were populating `internalProperties` part of response with internal/protected members. In fact, `internalProperties` does not correspond with C#'s protection level `internal`...
/backport to release/7.0-rc2
/backport to release/7.0-rc2
> @ilonatommy just curious, is VS using the `privateProperties` part? It is using it in the meaning: they are displayed. However, the difference between them and `result` is not stressed...