Dogfooding TaskRun names do not fit inside Result name lengths

Expected Behavior
We should be able to repurpose TaskRun names / IDs as Result name parts.
Actual Behavior
Certain names do not match the name regex because they are too large.
Example: tektonci/results/taskrun-check-pr-labels-rzjhs-check-kind-label-g6qxc-check-name-m-vxrhd
Full log:

{"level":"error","ts":"2021-01-13T10:44:08.825-0500","logger":"watcher.TaskRunResultsWatcher","caller":"taskrun/taskrun.go:62","msg":"error updating Record: rpc error: code = InvalidArgument desc = GetResult(tektonci/results/taskrun-check-pr-labels-rzjhs-check-kind-label-g6qxc-check-name-m-vxrhd): rpc error: code = InvalidArgument desc = rpc error: code = InvalidArgument desc = name must match (^[a-z0-9_-]{1,63})/results/([a-z0-9_-]{1,63}$)","knative.dev/traceid":"987d645f-0b1c-4dc3-9f1d-3c932334b4c2","knative.dev/key":"tektonci/check-pr-labels-rzjhs-check-kind-label-g6qxc-check-name-m-vxrhd","stacktrace":"github.com/tektoncd/results/pkg/watcher/reconciler/taskrun.(*Reconciler).Reconcile\n\t/usr/local/google/home/wlynch/src/github.com/tektoncd/results/pkg/watcher/reconciler/taskrun/taskrun.go:62\nknative.dev/pkg/controller.(*Impl).processNextWorkItem\n\t/usr/local/google/home/wlynch/pkg/mod/knative.dev/pkg@v0.0.0-20200831162708-14fb2347fb77/controller/controller.go:511\nknative.dev/pkg/controller.(*Impl).RunContext.func3\n\t/usr/local/google/home/wlynch/pkg/mod/knative.dev/pkg@v0.0.0-20200831162708-14fb2347fb77/controller/controller.go:449"}

The issue here is that both the Results API and k8s object names approximately follow RFC 1123, which has a max length of of 63 chars. If we want to support <type>-<name> syntax, we'll need to either bump the max allowed length to 127 (63+1+63) or use a different strategy for selecting default names.

The issue here is that both the Results API and k8s object names approximately follow RFC 1123, which has a max length of of 63 chars. If we want to support <type>-<name> syntax, we'll need to either bump the max allowed length to 127 (63+1+63) or use a different strategy for selecting default names.

Few options I'm considering at the moment:

Use object UIDs. This has the benefit of dealing with delete + apply iterations gracefully, but loses out on human recognizable names.
Drop the type prefix, and only use the name. Since k8s resource names will be <= 63 chars, this will make it compatible with the current results constraints, but this means that we can't distinguish taskruns from pipelineruns, so if a pair of objects share the same name they will be automatically grouped in the same result by default (which might be unintended in some cases).
Expand the constraints to allow for type + name. While this would allow us to keep the same semantics as we have right now, this means that names could potentially be up to 63+len('/results/')+127+len('/records/')+127 = 335, which seems excessive.

Few options I'm considering at the moment:

Use object UIDs. This has the benefit of dealing with delete + apply iterations gracefully, but loses out on human recognizable names.
Drop the type prefix, and only use the name. Since k8s resource names will be <= 63 chars, this will make it compatible with the current results constraints, but this means that we can't distinguish taskruns from pipelineruns, so if a pair of objects share the same name they will be automatically grouped in the same result by default (which might be unintended in some cases).
Expand the constraints to allow for type + name. While this would allow us to keep the same semantics as we have right now, this means that names could potentially be up to 63+len('/results/')+127+len('/records/')+127 = 335, which seems excessive.


Fix IPv4, IPv6, and Subdomain Issues with Dynu DNS usage.

Hello,
With the commits in this PR, I believe it will be possible to close most of the issues!
A quick explanation of the fixes:
Subdomains: #9 In the Dynu DNS API, subdomains are almost full domains. The full domain object (of the subdomain) must be retrieved, modified, and returned, rather than modifying the records of the root domain.
IPv6: #12 The container doesn't have access to IPv6, and hence can't see it's interfaces or make calls to external IPv6 servers to determine it's IP Address. The solution, inspired by this commit: https://github.com/home-assistant/addons/pull/2490/commits/db3f53f5f557f587c4742073d1b957325a7d3abb
Error Handling, Printing, and Checking Inputs: #8 Should not use a blank IPv4 address
Improved API usage: #3 The previous call updated certain fields of the Domain settings, however this left most at blank or default, so it "overwrote" whenever it updated.

Thanks for this.
How can I create a subdomain in dynudns for the sake of testing?

Yeah, I know up to there ;)
But how to create a subdomain?
Literately adding sub domains like below?

Yeah, I know up to there ;) But how to create a _sub_domain? Literately adding sub domains like below?

Hmm, I see. The terminology is a bit confusing I think.
To clarify, Either of the these methods creates a new Domain object in the DynU database. It has its own set of DNS records, and it's own Dynamic IPv4 and IPv6 address.
I just tested, it seems that when you are using Option 1, you are already a subdomain, and with Option 1, sub-subdomain seems to not be allowed.
With Option 2, I can make nested subdomains.

Ok. So are you saying what the "subdomain issue" is only when delegating domains you own to dynudns?
That I cannot test, so I'll just do a quick regression test for option 1.
Thanks

Ok. So are you saying what the "subdomain issue" is only when delegating domains you own to dynudns? That I cannot test, so I'll just do a quick regression test for option 1.
Thanks

Yes.


#195:Updated the language links to English

The edits, unfortunately, do not correspond to the meaning of task https://github.com/good-first-issues/good-first-issues.github.io/issues/195. I wrote in more detail in comment https://github.com/good-first-issues/good-first-issues.github.io/issues/195#issuecomment-2351548661.
I propose to close this PR.


Unhandled exception in XAML viewer when the project is in a path with private characters

This issue has been moved from a ticket on Developer Community.

Apologies for putting the problem here. My "Report a problem.." doesnt work from my visual studio
To reproduce.
You will need to create a private character.  So run eudcedit.exe from windows run dialog. Ive attached an example picture of the character I created.

next thing. Create a directory with the private character in windows. Once again.. Ive attached a picture

Now create a WPF project  in visual studio in the directory below the one that you created above.
Then try and open the designer to the main dialog.
You should see the error below..

Now this error not only applies to WPF .. but  projects created with .Net48 doesnt compile when placed under such a directory. In fact many things dont work when placed under such a directory.

Original Comments
Feedback Bot on 6/7/2022, 07:54 PM:
(private comment, text removed)
Ann Yang (Beyondsoft Corporation) [MSFT] on 6/8/2022, 01:19 AM:
(private comment, text removed)
Maurice Marinus on 6/15/2022, 06:44 AM:
(private comment, text removed)
Ann Yang (Beyondsoft Corporation) [MSFT] on 6/8/2022, 01:31 AM:
(private comment, text removed)
Feedback Bot on 6/15/2022, 01:09 AM:
(private comment, text removed)
Maurice Marinus on 6/15/2022, 06:54 AM:
(private comment, text removed)
Feedback Bot on 6/15/2022, 07:16 PM:
(private comment, text removed)

Original Solutions
(no solutions)

The images are broken, both here and in the VS Feedback link, but the user did follow up with additional comments in the VS Feedback issue. I'm transferring to msbuild.


Cannot read property 'forEach' of undefined

(node:21128) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'forEach' of undefined
    at Object.sendAll (/home/dzik/Projects/games/change_management/koa_app/node_modules/boardgame.io/dist/server.js:2524:25)
    at Master.onUpdate (/home/dzik/Projects/games/change_management/koa_app/node_modules/boardgame.io/dist/server.js:2397:25)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
(node:21128) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:21128) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Sometime i got this error and to be honest i have no chance to reproduce it, it seems to be completly random and as you can see its reported very poor. What could be reason ?
When i restar my koa server then everything back to normality i can perform move which previously thrown this error and continue, and then after some time i got this error one more time and so on. Really strange.

Haven't seen this error myself, and given that there isn't a sure way to reproduce it, I'll close this for now.  Feel free to re-open if you see this after upgrading to v0.33.


#autoplay-policy is not working properly

Backgrounds

OS: Windows 11
Thorium Version: Thorium_SSE3_122.0.6261.132.zip

Problems
Descriptions of the flag:

Disable/Enable AutoPlay
Allows setting the AutoPlay policy. Use No User Gesture Required to enable AutoPlay, and use Document User Activation Required to disable AutoPlay and force all sites to require a click to initiate media playback. User Gesture Required is the default, and blocks most AutoPlay annoyances, while allowing some (i.e. WebAudio) to continue. – Mac, Windows, Linux, ChromeOS, Fuchsia, Lacros
#autoplay-policy

Settings of it:

Default
No User Gesture Required
User Gesture Required
Document User Activation Required

Test Case
Try to open up any multimedia sites with its AutoPlay such as YouTube video.
For example this ads free one: https://www.youtube.com/watch?v=NeBlDtBSbI8

Default
The description says that "User Gesture Required is the default" but if I try to use it, then it won't block any AutoPlay.
No User Gesture Required
It's working as it should.
User Gesture Required
This one successfully blocks the AutoPlay if reloaded from already fully-loaded pages.
Document User Activation Required
This one supposedly more strict than User Gesture Required, but if I try to use it, then it won't block any AutoPlay.

Summary
User Gesture Required is working partially.
Default and Document User Activation Required is not working.

@Unknown78 Hmm, let me check this out next release.

@Alex313031 I've just tested Thorium_SSE3_123.0.6312.133.zip and it still not working properly.

@Alex313031 Still no changes with Thorium_SSE3_124.0.6367.218.zip


[idea] CSSketch reverse mode

Hi, John
Thanks for the awesome plugin.
Is it possible to to use Sketch api and webkit engine to work in "reverse mode"? I mean we give layers id/class-like names just like before and plugin generates CSS code based on styles that we apply to layers.
Something like capturing "Copy CSS Attributes" and outputting it in attached css file.
What do you think?
Thanks.

That's actually a pretty cool idea! Unfortunately it's not relevant to my workflow right now, as I barely ever to any web development, so it doesn't interest me to develop it.

Would you mind if I use your code to build upon it?

Please do! I've licensed it under the MIT license, so you're free to build upon it, make whatever you want with it, use it commercially and closed source if you want. 😁

Thanks, John. Good luck)


Not updating to latest version

I'm following the vuetify project and the latest release there is 0.13.1 but on the releaser site it is still on 0.12.5

There was a bug in the cron-job that made everything fail, it has been fixed, and it seems Vuetify has the correct latest release, so I'm closing the issue, please reopen if there is still a issue!


api docs responsiveness

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.NoelKova seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


How to project envmap to ball?

I notice that you have compiled py code to convert ball in square image to env map, but can you supply the code of the inversion process, thank you a lot.

It's depend on what you are looking for.
For compare the score
If you are looking to get the score to compare without paper. You need to set up a blender scene that renders an environment map of Chromeball. Please see the DiffusionLight-evaluation  repository for more information.
For other proposed.
If you want to the python code that just inversed of ball2envmap.py. Here is the envmap2ball.py that converts from the environment map back to chromeball.  Please note that our work assumes orthographic projection, which may make the result differ from blender rendering.
Usage:
python envmap2ball.py --envmap_dir <directory_that_contain_environmentmap> --ball_dir <directory_to_saved_the_output_chromeball>

I find your code envmap2ball.py is so good, but I also have some confusions about the result, here is my example.
I use this image(inage 1) as input and then I run the code envmap2ball.py. The final result is image 2, as image 2 displays, I cannot see the back of this image. So does the code envmap2ball.py projects the image 1 only into the front of the ball and does not project anything into the back? And I also wonder can I use image 2 as supervision to relight my portrait image? Looking forward to you reply.

Thanks for your awesome and detalied reply , I have learned a lot from it. Because of my poor knowledge of CG, I have another question: The solution of the environment map I supply(Image 1 in the previous question which is a diffuse irradiance map from a HDR image) is 256 * 128, while the solution of the environment map from training data of IC-Light is 32 * 32, I notice that relighting works(such as Relightful Harmonization)usually condition the model with a HDR environment map of high resolution(maybe 2048 or 4096+), So I have confused about whether I can extract the envirmont lighting through diffuse irradiance map and then resize it to low resolution, and then call the result as environment map. In other words, whether environment map does not be confined with resolution, thanks for your previous reply again.

Environment map does not be confined with resolution
Yes, environment map have nothing to do with resolution. we always can do bilinear interpolation to obtain light in any given direction (theta,phi).   image size of 32 x 32 using IC-Light also counts as an Environment map even if it low resolution.
can I extract the environment lighting through a diffuse irradiance map and then resize it to low resolution, and then call the result an environment map.
By definition, it's two different things. diffuse irradiance map combines multiple light rays from an environment map.
but in my opinion, it is close enough. you can just call it an environment map and think about it as a low-resolution environment map that looks very smooth because of bilinear interpolation.
This image taken from LearnOpenGL.com. You can see the environment map (left) and the diffuse irradiance map (right)  is very similar. if you downsize the environment map and upsize it with anti-aliasing. you basically get the same image.

Thanks for your reply again, you have help me solve many questions which have confused me for a long time , specially your great   code.I notice that this hub also has some great codes consisting of some demos of blender python api, and your hub, Diffusionlight-evaluation has some demos of blender api too.All of those really help me a lot. Considering that I am a green hand in CG and I am not familar with C++(So I cannot handle OpenGL well now), I will continully learn basic knowledge of CG and blender python api, and follow your great work in the future.Finally, sincerely thanks for your help again.

Thanks for your reply again, you have help me solve many questions which have confused me for a long time , especially your great   codes and diagrams you provide above.I notice that this hub also has some great codes consisting of some demos of blender python api, and your hub, Diffusionlight-evaluation has some demos of blender api too.All of those really help me a lot. Considering that I am a green hand in CG and I am not familar with C++(So I cannot handle OpenGL well now), I will continully learn basic knowledge of CG and blender python api, and follow your great work in the future.Finally, sincerely thanks for your help again.


Improve readability of IonReaderContinuableCoreBinary.nextValue() and transcodeNextTo()

These are lengthy methods with looping constructs and early returns. Figuring out a better factoring would improve readability and maintainability.

Also apply this to IonReaderTextSystemX.transcodeNextTo().
Additionally, IonReaderContinuableCoreBinary.transcodeValueLiteral() and IonReaderTextSystemX.transcodeValueLiteral() are similar enough that we could consider making MacroAwareIonReader abstract and putting a generalized implementation in there.


Error: The "UseDependentUponConvention" parameter is not supported by the "CreateCSharpManifestResourceName" task

Issue Description
OmniSharp.MSBuild.ProjectLoader fails when trying to load a solution that contains a project with reference to another project.
Due to this problem, the IntelliSense does not work!

Looks like this change is not available in the "omnisharp-vscode" built-in MSBuild.
I removed the UseDependentUponConvention="$(EmbeddedResourceUseDependentUponConvention)" lines from the following files:

~/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/15.0/Bin/Microsoft.CSharp.CurrentVersion.targets
~/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Microsoft.CSharp.CurrentVersion.targets

So, the VS Code loaded the solution with no errors and everything worked!

Steps to Reproduce

Create a solution with 2 projects (with the main project referencing the subproject: <ProjectReference Include="(...).csproj" />);
Open the Visual Studio Code in Ubuntu (>= 18.04);
Check the warning message: Some projects have trouble loading. Please review the output for more details.
Try to use the Go to definion feature.

Expected Behavior
The Visual Studio Code loads the projects with no error and the IntelliSense works.
Actual Behavior
The Visual Studio Code loads the project (with troubles) and the IntelliSense does not work.
Logs
OmniSharp log

(...)
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        FAILURE: Could not locate '/(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Microsoft.Build.Tasks.Core.resources.dll'.

[fail]: OmniSharp.MSBuild.ProjectLoader
        The "UseDependentUponConvention" parameter is not supported by the "CreateCSharpManifestResourceName" task. Verify the parameter exists on the task, and it is a settable public instance property.

[fail]: OmniSharp.MSBuild.ProjectLoader
        The "CreateCSharpManifestResourceName" task could not be initialized with its input parameters.

[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file '/(...)/workspace/(...)/mySubProject.csproj'.
/(...)/workspace/(...)/mySubProject.csproj
/(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Microsoft.CSharp.CurrentVersion.targets(110,15): Error: The "UseDependentUponConvention" parameter is not supported by the "CreateCSharpManifestResourceName" task. Verify the parameter exists on the task, and it is a settable public instance property.
/(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Microsoft.CSharp.CurrentVersion.targets(107,9): Error: The "CreateCSharpManifestResourceName" task could not be initialized with its input parameters.

[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /(...)/workspace/(...)/myMainProject.csproj

[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/(...)/workspace/(...)/myMainProject.csproj'.

[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/(...)/workspace/(...)/myMainProject.csproj'

[fail]: OmniSharp.MSBuild.ProjectManager
        Attempted to update project that is not loaded: /(...)/workspace/(...)/mySubProject.csproj

[info]: OmniSharp.MSBuild.ProjectManager
        Update project: myMainProject

[warn]: OmniSharp.MSBuild.ProjectManager
        Ignoring previously failed to load project '/(...)/workspace/(...)/mySubProject.csproj' referenced by 'myMainProject'.

[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/(...)/mySubproject.csproj to be already loaded for project myMainProject
(...)

C# log
N/A
Environment information
VSCode version: 1.40.1
C# Extension: 1.21.7
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100
 Commit:    04339c3a26
Runtime Environment:
OS Name:     ubuntu
OS Version:  19.10
OS Platform: Linux
RID:         ubuntu.19.10-x64
Base Path:   /usr/share/dotnet/sdk/3.0.100/
Host (useful for support):
Version: 3.0.0
Commit:  95a0a61858
.NET Core SDKs installed:
3.0.100 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

cpptools
ms-vscode
0.26.2-insiders

csharp
ms-vscode
1.21.7

gitlens
eamodio
10.2.0

todo-tree
Gruntfuggly
0.0.162

Looks like this change is not available in the "omnisharp-vscode" built-in MSBuild.
I removed the UseDependentUponConvention="$(EmbeddedResourceUseDependentUponConvention)" lines from the following files:

~/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/15.0/Bin/Microsoft.CSharp.CurrentVersion.targets
~/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/15.0/Bin/Microsoft.CSharp.CurrentVersion.targets
~/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Microsoft.CSharp.CurrentVersion.targets
~/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Microsoft.CSharp.CurrentVersion.targets

can you post the full log (including OmniSharp startup info etc)?

Sorry, but I've needed to remove some tokens due to confidentiality.
Starting OmniSharp server at 11/20/2019, 9:49:48 AM
    Target: /(...)/workspace/myProject/myProject.sln

OmniSharp server started.
    Path: /(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/run
    PID: 17476

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on ubuntu 19.10 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 1 MSBuild instance(s)
            1: StandAlone 16.3 - "/(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        MSBUILD_EXE_PATH environment variable set to '/(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/MSBuild.dll'
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: StandAlone 16.3 - "/(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin"
            CscToolExe = csc.exe
            MSBuildToolsPath = /(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin
            CscToolPath = /(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Roslyn
            BypassFrameworkInstallChecks = true
            MSBuildExtensionsPath = /(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/(...)/workspace/myProject'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.MSBuild.ProjectSystem
        Detecting projects in '/(...)/workspace/myProject/myProject.sln'.
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/(...)/workspace/myProject/(...)/mySubproject.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/(...)/workspace/myProject/(...)/myProject.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/(...)/workspace/myProject'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /(...)/workspace/myProject/(...)/mySubproject.csproj
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.EditorConfigWorkspaceOptionsProvider, Order: 200
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/(...)/workspace/myProject' on host 17378.
[fail]: OmniSharp.MSBuild.ProjectLoader
        The "UseDependentUponConvention" parameter is not supported by the "CreateCSharpManifestResourceName" task. Verify the parameter exists on the task, and it is a settable public instance property.
[fail]: OmniSharp.MSBuild.ProjectLoader
        The "CreateCSharpManifestResourceName" task could not be initialized with its input parameters.
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file '/(...)/workspace/myProject/(...)/mySubproject.csproj'.
/(...)/workspace/myProject/(...)/mySubproject.csproj
/(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Microsoft.CSharp.CurrentVersion.targets(110,15): Error: The "UseDependentUponConvention" parameter is not supported by the "CreateCSharpManifestResourceName" task. Verify the parameter exists on the task, and it is a settable public instance property.
/(...)/.vscode/extensions/ms-vscode.csharp-1.21.7/.omnisharp/1.34.7/omnisharp/.msbuild/Current/Bin/Microsoft.CSharp.CurrentVersion.targets(107,9): Error: The "CreateCSharpManifestResourceName" task could not be initialized with its input parameters.

[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /(...)/workspace/myProject/(...)/myProject.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file '/(...)/workspace/myProject/(...)/myProject.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project '/(...)/workspace/myProject/(...)/myProject.csproj'
[fail]: OmniSharp.MSBuild.ProjectManager
        Attempted to update project that is not loaded: /(...)/workspace/myProject/(...)/mySubproject.csproj
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Ignoring previously failed to load project '/(...)/workspace/myProject/(...)/mySubproject.csproj' referenced by 'myProject'.
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Unable to resolve assembly '/(...)/workspace/myProject/(...)/bin/Debug/netstandard2.0/myProject.dll'
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject
[warn]: OmniSharp.MSBuild.ProjectManager
        Expected project reference /(...)/workspace/myProject/(...)/mySubproject.csproj to be already loaded for project myProject

thanks I suspect the problem is related to embedded resources (do you have any?) - not project-to-project references (there are plenty of integration tests for that, and if that didn't work, then really nothing would work).
on macOS we use msbuild from Mono 6.4.0, it could be that it was built before the commit that added the property.
you could try to install mono 6.6.0 preview (https://www.mono-project.com/download/preview/) and see if it helps/

Yeah, I have one <EmbeddedResource/>.
So, I installed the mono-devel 6.6.0, and the things now work fine.

The problem is not reproduced anymore after version 1.21.11.


"@namespace" rules are not supported

What version of Remix are you using?
1.16.1
Are all your remix dependencies & dev-dependencies using the same version?

[x] Yes

Steps to Reproduce
Import a CSS file that contains @namespace svg "http://www.w3.org/2000/svg";.
Don't use any of the new CSS integrations, just a plain old CSS import.
Expected Behavior
No warning.
Actual Behavior
The warning:
"@namespace" rules are not supported [unsupported-@namespace]

is shown in the console.

This warning is coming from esbuild, not something we have control over.
Warnings aside, is the built CSS correct? In my local testing against esbuild directly, despite warning me that @namespace rules aren't supported, the following input generates the following output:
Input CSS:
@namespace svg url('http://www.w3.org/2000/svg');

a {
  color: orangered;
}

svg|a {
  fill: blueviolet;
}

Output:
@namespace svg url(http://www.w3.org/2000/svg);a{color:#ff4500}svg|a{fill:#8a2be2}

If this is causing you issues, I'd raise an issue upstream against esbuild.

Yes, the warning aside, the build is correct!


Consider updating CI to be more like rust-bitcoin

Are any of the recent improvements to CI in rust-bitcoin worth adopting here?

Run fuzzer daily: https://github.com/rust-bitcoin/rust-bitcoin/pull/2634 ?
Re-write tesh.sh to do as we do in run_task.sh?

Probably yeah. Though we should wait for the rust-bitcoin CI to settle out a little bit first.

OMG we are not using the recent/minimal lock files in CI. Shall I re-write CI now?

That would be awesome if you have the time.

I have exactly 24 hours in each day!

OMG we are not using the recent/minimal lock files in CI. Shall I re-write CI now?

For what it's worth, I use these files locally, so they are exercised.
But yes, if you have the time and inclination, please rewrite CI here!
To the extent possible, can you try to factor things out of rust-bitcoin into https://github.com/rust-bitcoin/rust-bitcoin-maintainer-tools/ rather than copy/pasting the scripts around? I think that would get us to a more sustainable situation regarding CI script maintenance.

I might as well do that at the same time as doing bitcoincore-rpc, I'll give it a shot today.

I can help reviewing, please ping me?

Legend, can do.

Hey @storopoli, and anyone else, if you want to look there are a bunch of drafts open that I did today that re-write CI to use a shared script that lives in rust-bitcoin-maintainer-tools

https://github.com/rust-bitcoin/rust-bitcoin-maintainer-tools/pull/4
https://github.com/rust-bitcoin/rust-bitcoincore-rpc/pull/348
https://github.com/rust-bitcoin/rust-bitcoin/pull/2736
https://github.com/rust-bitcoin/rust-miniscript/pull/682


feat(abi): internal abi handling

Description
This PR introduces a first in our handling of Actor's Binary Interface in our testing framework. In this PR we:

Create an abi module in the common crate containing an ABI and Method structures that we will use to parse the content of ABI files in. Also introduced a utility function to convert method names to their method numbers based on the FRC 0042 standard.
Fix kythera-lib crate as we could not run any actor based on the current implementation. The bug was caused by a wrong CID being used to instantiate the Machine.
Implemented a way for us to scale actors test over our testing framework, with their wasm binaries being compiled at test time, preventing an overload of static files on the repo.

Links to any relevant issues or pull requests
This PR starts to tackle #23 , however we still have some work to produce.
Open Questions
As previously stated, we started to tackle this interface matter in this PR. Because the changes are already quite heavy we decided to first open this PR to focus the rest of our TODO in a separate one. The related TODO can be found here.
Change checklist

[X] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[X] I have added tests that prove my fix is effective or that my feature works

Note: We should merge develop in initial-testing-feature before proceeding to review.

Secondary note, it seems that the current testing of our lib takes already 8minutes because of builtins and wasm projects compilation. We should find a way to solve that. Adding a new issue #28


Polkit variable

Bbappend for polkit sets a variable POLKITAUTH.
The explanation is that "default meta-oe value is consolekit" but I can't seem to find this variable in meta-oe. I would appreciate help in defining the need for this variable and how it is used.
NOTE: this recipe was renamed from polkit_0.111 to polkit_0.113, could be related to old version...

@erikboto should know that but I suspect it's still in there from the time when poky didn't do systemd per default.


flutter all pictures turn purple

Problem description
Occasionally, it will appear after entering the foreground from the background, and all the pictures will turn purple. After restarting the APP, the pictures will load normally
Expected results:
The picture is displayed normally.
Actual results:

Development environment
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.0, on macOS 12.3.1 21E258 darwin-x64, locale
zh-Hans-CN)
Checking Android licenses is taking an unexpectedly long time...[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2020.3)
[✓] VS Code (version 1.69.2)
[✓] Connected device (3 available)
! Error: 孙武东 is not connected. Xcode will continue when 孙武东 is connected.
(code -13)
[✓] HTTP Host Availability
• No issues found!
code desc
I am sorry that I cannot provide the code because I do not know which part of the code is faulty

Hello @WuKong94. Thank you for filing this issue. Can you provide the below information:

Can you try to reproduce this issue in a new project? Basically, what we're looking for is a minimal, reproducible example so that we can verify and investigate the issue.
Does this occur on a Simulator, or physical device? Is it reproducible on any other platforms like Android or desktop?

It is currently only available on real iOS devices.
In addition, it is difficult for me to provide a new project, because it is not easy to reproduce, and it takes several days to reproduce in the background.

@WuKong94 Could you give a sample of the code that exists that's causing this? For example: Are you using Image.network() or a 3rd party library?
Also, if you have gotten any crash logs from your users via something like Firebase Crashlytics if you have set that up, could you share those as well?

@WuKong94 Could you give a sample of the code that exists that's causing this? For example: Are you using Image.network() or a 3rd party library?
Also, if you have gotten any crash logs from your users via something like Firebase Crashlytics if you have set that up, could you share those as well?

I used Image.asset and cached_network_image, So I don't think it's cached_network_image,  I accessed Bugly, similar to Firebase Crashlytics, but did not find any error messages

Are the images rendered purple from Image.asset() or from cached_network_image?

all

Are you using any specific image format? Or are they all pngs and/or jpegs?

png

Since I cannot reproduce this issue, I am labelling this for further insights from the team.

Without a reproducible test case, we unable to make progress on this.


feat(lang): Add Rust config

thanks!

@amaanq Thanks for this! Quick question: when you goto definition to the standard library, do you also get this problem? https://github.com/simrat39/rust-tools.nvim/issues/394
It seems like the issue here is that a new instance of the LSP is boot up and that there are duplicate definitions.

@amaanq Thanks for this! Quick question: when you goto definition to the standard library, do you also get this problem? https://github.com/simrat39/rust-tools.nvim/issues/394
It seems like the issue here is that a new instance of the LSP is boot up and that there are duplicate definitions.

I do not, just tried going to definition on Result and I couldn't replicate that


Update HttpConnection.java

I find a problem in src/main/java/org/jsoup/helper/HttpConnection.java line-769
when contentType="application/javascript"

Hi, thanks for the PR. This is the point of the ignore mime type setting - if you want to handle non HTML / XML content, set that to true.


DBeaver 5.1.0 launch on OpenSUSE Leap 15.0 fails at missing, old "libffi.so.4"

Exec/launch of DBeaver 5.1.0 on OpenSUSE Leap 15.0, fails with
	/tmp/jna-3506402/jna6054383978633988988.tmp: libffi.so.4: cannot open shared object file: No such file or directory
	/tmp/jna-3506402/jna6054383978633988988.tmp: libffi.so.4: cannot open shared object file: No such file or directory

on this distro, the official release of libffi*
	https://build.opensuse.org/package/show/openSUSE%3ALeap%3A15.0/libffi

is v3.2.1 rgit259
	rpm -q --whatprovides ./libffi.so
		libffi-devel-3.2.1.git259-lp150.18.2.x86_64

which installs
	cd /usr/lib64
	ls -al *libffi*
		lrwxrwxrwx 1 root root  15 May 31 21:39 libffi.so -> libffi.so.7.1.0*
		lrwxrwxrwx 1 root root  15 May 31 21:38 libffi.so.7 -> libffi.so.7.1.0*
		-rwxr-xr-x 1 root root 39K Apr  9 11:30 libffi.so.7.1.0*

forcing a symlink
	cd /usr/lib64
	ln -sf libffi.so.7.1.0 libffi.so.4

and relaunching DBeaver does appear to work -- currently

Not sure what component has this dependency.
As far as I know Eclipse (SWT) doesn't have direct dependencies on libffi. Maybe this is side effect of some local build.

Eclipse (SWT) doesn't have direct dependencies on libffi

Starting wih that realization, after some digging, and the obvious whine^ about
/tmp/jna-3506402/jna6054383978633988988.tmp

I force un-/re-installed 'jna' packages, and ... that solved the issue.
After rm'ing the faux libffi.so.4 link, DBeaver's error-free on launch again.
Thx!


refactor: avoid polluting the user's rxjs setup

Currently, the internal uses of RxJS operators are done via patch imports, which add methods directly to the global Observable object. This can be an issue since the user may not know where these methods are coming from and may depend on them. Afterwards, if Material removes a method import, the user's app will break since the methods won't be defined anymore. This PR:

Replaces all of the patch imports with imports of individual operators and fixes any issues that showed up afterwards.
Adds a FunctionChain class to help with chaining the individually-imported operators.

Fixes #2622.

This is still something we need to do, but it's going to get stuck rebasing all the time if we're not ready for it. @crisbeto let's give this another try after beta.3 and ng-conf
We should also introduce a lint check at the same time so that we don't keep adding more in the future.

Is this still scheduled for beta 4, or do you expect it will be bumped?

We may push it out a bit- we're waiting to see if rxjs will add a more convenient syntax

Closing in favor of #5314.


PolygonMeshBuilder Tutorial

Added a simple tutorial for PolygonMeshBuilder including images inpublic/html/img/tutorials/polymeshbuild folder

thanks!!


Area Damage On Swords

Info

Server version: 1.12
OldCombatMechanics version:1.6.6
Server log file:
OldCombatMechanics config file:

Problem Description

The area damage added in 1.9 is still not removed pls remove it

no errors in logs and I didn't change the config file. sweep attack damages other enemies 1 heart  not main enemy main enemy damages by 7 heart if im holding diamond sword but other enemies can take damage

Do the other move at all, or flash red?

no knock back at other mobs

Do they flash red, like the mob being hit does?

no they dont https://dev.bukkit.org/projects/damage-indicator

Could this be because OCM has the listener set on HIGHEST priority and thus only cancels the event after the damage indicator plugin has gotten the info?

Yes, that sounds right. Checking the source, that damage indicator plugin listens on priority NORMAL, although it should really listen on MONITOR. Not sure if we should adjust OCM, but listening on LOWEST sounds nicer than HIGHEST to me - I don't think a plugin would un-cancel the event.
In summary we can either change this to LOWEST or nag the plugin author to use MONITOR. The latter is a bit unlikely to help:

Or find a similar plugin with the same features or even modify the plugin for him?

Why did you initially put the OCM listener to highest and not lowest? Lowest sounds like it would better fit what it does, as no other plugin will notice those unless it really wants to.

Almost all of OCM's listeners are on HIGHEST to avoid messing up other plugin's functionality.
In this case, since all the module really does is cancel an event, it may be fine to set it to LOWEST.

It would be my preferred solution here, unless it causes some other conflicts. Not sure which ones that would be here. Some plugin would need to un-cancel damage events to reinstate the sweep damage. I don't know who would do that, but somebody might.
It really is the fault of the DamageIndicator plugin, but we could maybe be a bit more friendly to it unless you know a plugin that does un-cancel damage events.

Alright, I have made this change. @AhmetDS please try this test build and see if the DamageIndicator plugin still tells you other entities are being damaged.

okey

 [OldCombatMechanics] Config file config.yml generated [13:46:08 ERROR]: Error occurred while enabling OldCombatMechanics v1.7.0 (Is it up to date?) java.lang.IllegalArgumentException: No enum constant org.bukkit.potion.PotionType.F¦RE_RES¦STANCE         at java.lang.Enum.valueOf(Unknown Source) ~[?:1.8.0_141]         at org.bukkit.potion.PotionType.valueOf(PotionType.java:1) ~[spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at gvlfm78.plugin.OldCombatMechanics.utilities.ConfigUtils.loadPotionDurationsList(ConfigUtils.java:73) ~[?:?]         at gvlfm78.plugin.OldCombatMechanics.module.ModuleOldPotionEffects.reload(ModuleOldPotionEffects.java:44) ~[?:?]         at gvlfm78.plugin.OldCombatMechanics.module.ModuleOldPotionEffects.<init>(ModuleOldPotionEffects.java:39) ~[?:?]         at gvlfm78.plugin.OldCombatMechanics.OCMMain.registerModules(OCMMain.java:117) ~[?:?]         at gvlfm78.plugin.OldCombatMechanics.OCMMain.onEnable(OCMMain.java:47) ~[?:?]         at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:337) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:403) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at org.bukkit.craftbukkit.v1_12_R1.CraftServer.enablePlugin(CraftServer.java:381) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at org.bukkit.craftbukkit.v1_12_R1.CraftServer.enablePlugins(CraftServer.java:330) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at net.minecraft.server.v1_12_R1.MinecraftServer.t(MinecraftServer.java:422) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at net.minecraft.server.v1_12_R1.MinecraftServer.l(MinecraftServer.java:383) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at net.minecraft.server.v1_12_R1.MinecraftServer.a(MinecraftServer.java:338) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at net.minecraft.server.v1_12_R1.DedicatedServer.init(DedicatedServer.java:272) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]         at net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:545) [spigot-1.12.2.jar:git-Spigot-2cf50f0-2b93d83]

Can you post your config.yml please?

myconfigbutitstxtforupload.txt

Where are you from? Can you tell the language your server uses? I am in germany, so mine is de_DE, what is yours? I suspect a locale problem when upper casing the potion type as he gvlfm doesn't seem to have taken that into account.
If you do not want to tell me that, can you tell me what your upper case i/I looks like?

im from turkish :/

jshell> "hey you there i am nice".toUpperCase($1);
$2 ==> "HEY YOU THERE İ AM NİCE"

Yea, that seems to be the problem. Languages are mean.
Can you try this this please?

Makes sense as the author did not set ignoreCancelled to true and doesn't check himself. That plugin is really broken.
You are likely better off finding another plugin, but if you insist you can try this patch  I made.

can you use this damage indicator damage indicator doesnt supports 1.12.2 but this support
Yeni WinRAR arşivi.zip

That plugin looks like it will have the exact same problem. Can somebody tell me why none of these plugins seem to check whether the damage event is actually cancelled? That should also break with things like WorldGuard, Protection zones and whatever else.
Apart from the plugin you (leon) posted should work just fine on 1.12 (it does, as you've seen) and my patch should make it work correctly (i.e. ignore cancelled events).
@AhmetDS I would ask the author of that plugin you posted (if you know him) to stop spawning ArmorStands for cancelled events. It also might remove other ArmorStands if they are very close to the player/mob being damaged, if I followed that code correctly.

damage indicator needs this plugin to work "https://dev.bukkit.org/projects/holoapi" but me posted damage indicator is dont need holoapi

:/ nevermind i think this problem not causing oldcombatmechanics so how to delete sword sweep attack effect?

The effect on the client side? So the particles?
The answer is "you can't" as that is purely client side. OCM can disable the damage, but not the client side particles sadly.

@AhmetDS Any update? Have you tried the build I posted?

yep it worked

thx man


[main] Update package versions

Something!
Work Items
Fixes #4

Issue  is not approved. Please make sure the issue is approved before continuing with the pull request.


How to handle task cancellation with ViewStore.send(_:while:)

I'm experimenting with integrating the ViewStore async support with the SwiftUI .task modifier and I can't seem to figure out how cancellation is supposed to work.
Looking at the source of ViewStore.suspend it looks like the iOS 14 implementation does handle cancellation but its unclear whether the iOS 15 version, that uses the AsyncPublisher API in Combine does handle cancellation.
The .task modifier in SwiftUI starts a task on appear and is supposed to cancel the task on disappear, or if the provided id parameter changes. In my scenario, I have a List and each view in the list has its own row store and view store. I'm trying to start a task when the row appears and I've got this working. As a simplified example:
struct RowState: Equatable, Identifiable {
  let id: UUID
  var isRunningTask: Bool = false
}

enum RowAction: Equatable {
  case runTask
  case taskFinished
}

let rowReducer = Reducer<...> { state, action, environment in
  switch action {
  case .runTask:
    // simulate some async work
    state.isRunningTask = true
    return Effect(value: .taskFinished)
      .delay(for: 2.0, on: DispatchQueue.main)
      .eraseToEffect()

  case .taskFinished:
    state.isRunningTask = false
    return .none
  }
}

In the view:
struct RowView: View {
  let store: Store<RowState, RowAction>

  var body: some View {
    Text("Is running task? \(viewStore.isRunningTask ? "Yes" : "No")")
        .task(id: viewStore.id) {
            await viewStore.send(.runTask, while: \.isRunningTask)
        }
  }
}

In the case where task is an expensive operation, like loading some asset from the network, how would we handle cancellation of whatever effect is triggered by .runTask when SwiftUI tries to cancel the task?
Its hard to tell exactly what is happening but I'm guessing that even if the task is being cancelled, all it is doing is cancelling the subscription to the change in the state of the underlying ViewStore - it does not actually cancel the effect returned from the reducer in the runTask action.
I guess what is really needed here is the ability to fire some action into the view store when the task is cancelled and then in the reducer we can use normal effect cancellation to cancel any running effect.

I've opened the PR above after experimenting with solutions to this and this seems to work nicely, at the expense of losing the simplified iOS 15 implementation that uses AsyncPublisher under the hood - I'm open to suggestions for making it work with that too.

Hey @lukeredpath have you explored the async-send-task-cancellation branch before? It's not exactly what you're after but it might inspire some additional ideas.
Regarding the actual issue though:

I'm guessing that even if the task is being cancelled, all it is doing is cancelling the subscription to the change in the state of the underlying ViewStore

That's correct. It might also mean that the state is no longer available for the reducer to perform the cancellation, similar to trying to cancel effects from .onDisappear { ... }. This makes me think you'd need an approach similar to cancelling effects for optional reducers.
You could introduce a helper that maps effects to cancellable ones. eg:
extension Reducer {
  func mapEffect(
    _ transform: @escaping (Effect<Action, Never>, State, Action, Environment)
      -> Effect<Action, Never>
  ) -> Self {
    Self { state, action, environment in
      let effect = self.run(&state, action, environment)
      return transform(effect, state, action, environment)
    }
  }

  func makeCancellable<CancellableAction, ID: Hashable>(
    action cancellableAction: CasePath<Action, CancellableAction>,
    id toCancellationId: @escaping (State) -> ID
  ) -> Self {
    self.mapEffect { effect, state, action, _ in
      cancellableAction ~= action
        ? effect.cancellable(id: toCancellationId(state))
        : effect
    }
  }
}

I typically use simplified versions of these helpers, but in your case, we can use the row id as the cancellation id (or wrap it in a Hashable struct).
So a list reducer could look something like this:
let listReducer = Reducer<ListState, ListAction, ListEnvironment>.combine(
  rowReducer
    .makeCancellable(action: /RowAction.runTask, id: \.id)
    .forEach(
      state: \.rows,
      action: /ListAction.row(id:action:),
      environment: { .init(mainQueue: $0.mainQueue) }
    ),

  Reducer { state, action, _ in
    switch action {
    case .addRowButtonTapped:
      state.rows.append(RowState())
      return .none

    case let .delete(indexSet):
      let ids = indexSet.map { state.rows.ids[$0] }
      state.rows.remove(atOffsets: indexSet)
      // return .cancel(ids: ids) // found a bug...
      return .merge(ids.map(Effect.cancel(id:)))

    case .row:
      return .none
    }
  }
)

That's just one possibility. You could also implement your PR as a standalone extension or use withTaskCancellationHandler { ... } inside your views.

We're currently using the PR as an extension in our app and its working well so far.
We have found one issue although its not really related to TCA - we found that if the collection of rows is changed (e.g. due to a refresh, or if the user changes their search term in a search interface) and the new collection contained rows with the same ID as before, the task on the row would not fire again - our best theory is that SwiftUI is somehow reusing the same view from before and therefore the task isn't firing.
To work around this, we generate a unique task ID for each row every time the collection is updated derived from the row ID and an additional seed ID and pass this id to the .task modifier in the view.

Closing this as it looks like the forthcoming concurrency updates will take care of this.


Update onprem.md

Change Description
Adding always a pulling before running the image, useful to stay updated with whatever version is currently published

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @elect86 ,
I strongly believe that we should not do this.  For instance, it means that users behind a poor Internet connection will have difficulty running lakefs.  Users on an expensive Internet connection will end up paying a lot.  Or, users can silently get a major version bump and things stop working for them with no information why.
IMHO the issues are mostly to do with the Docker latest tag.  I think it is a really poor tag to use in any setting: you literally have no idea what you will get.  Docker's behaviour regarding caching makes it even worse: what we would want to do here is always go to Docker Hub to see which image is latest, but then allow caching when read that image (by digest).
It is frustrating to have to do something that is incorrect in one of two ways because of an issue with some third piece of software.  But switching one problematic instruction for another might not be a fix.
So I oppose recommending this by default and with no warnings.  Would you find it useful if we instead added another sentence suggesting users try --pull alwyas if they need some feature and need to update their lakeFS?

I get it, ok then, I'll close it

Would you find it useful if we instead added another sentence suggesting users try --pull alwyas if they need some feature and need to update their lakeFS?

Sure


TS-3414 return false from approve if there's an error

https://financeit.atlassian.net/browse/TS-3414

@dobsonken the code here looks good except for an odd spacing issue. Could you also please add an rspec test to cover the new functionality? Basically it should test that the approve! method returns false if the performable_method returns false.


Vault Settings :: Currency

We should be able to select the coins like we do on IOS and Android.
The default coin is USD, but we need to save it on storage; once they change it, then we update it.

[ ] Create a table called settings where it has (language, currency, default chains list, ... )

fixed in #216


Fix def of granulosa cell

https://github.com/obophenotype/uberon/issues/656

Suggest "of mammals" be removed from the definition.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 10 Mar 2015 at 9:18

Still needs fixing.


Feat(eos_cli_config_gen): Added support for CVX client

Change Summary
Added support for CVX client command
Related Issue(s)
Fixes #1681
Component(s) name
arista.avd.eos_cli_config_gen
Proposed changes
Data Model
management_cvx:
  shutdown: false
  server_host:
    - < IPv4_address >
    - < IPv4_address >

Eg:
management_cvx:
  shutdown: false
  server_host:
  - <IP_ADDRESS>
  - <IP_ADDRESS>

How to test
molecule converge --scenario-name eos_cli_config_gen -- --limit management-cvx
Checklist
User Checklist

N/A

Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

The CVX client also supports the source-interface in case using loopback as source and vrf configuration in case source interface is in non-default vrf.
management cvx
  no shutdown
  server host <CVX-1_IP>
  server host <CVX-2_IP>
  server host <CVX-3_IP>
  source-interface Loopback0

management cvx
  server host <CVX-1_IP>
  server host <CVX-2_IP>
  server host <CVX-3_IP>
  vrf mgmt
  source-interface management 1
  no shutdown


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

error


whitespace fixes?

Hi sans

HELLO, DO YOU NEED A HELP????????????????

if sans is so great why haven't they made a sans 2

sans profile picture hi

hello


TestApplication has an API Key embedded in the source.

FYI: TestApplication.Program has someone's API key embedded. Not sure if you meant to expose this key to the public or not.

It's ok it's a test key we requested especially for running our unit tests.


Remove unused lint override

Coverage remained the same at 96.863% when pulling ffbff5b833952aa49d495f90937ac37eb95ce44f on captbaritone:sparse into 93c32d79a7a640187f1a929f1d77f2c55d31a76b on jashkenas:master.


Change gripper dimensions

Thanks for share your code. What do I need to change to work with a different gripper sizes? Like finger length and width, maximum opening, etc.

The geometry of gripper in visualization from Open3d can be changed in GraspnetAPI module, please refer to https://github.com/graspnet/graspnetAPI/blob/master/graspnetAPI/grasp.py. But this kind of change is not equivalent to correcting the actual gripper because the confidence score labels have generated under initial gripper. In my experience, if you want your gripper to be more consistent with the dataset, you could find the difference between the actual contact points and the contact points in visualization. Correct this difference by gripper length compensation with moving robot arm TCP.

Thank You.


Publish new version to NPM

Could you publish a new version to NPM please? A bug fix was recently merged that we need for a project that we're working on. Thanks in advance!

@keller-mark would you be the one to do this?

Yes, should be published as soon as this action completes https://github.com/vitessce/vitessce/actions/runs/12165475090/job/33929511972

Rad, thanks a ton!