MB-14734 Add closeout office information to shipment card for SCs

Jira ticket for this change
Summary
Added closeout office information to shipment card for Services counselor's PPM moves.
Logic is there for all, but no test data to see closeout offices for everything .I'd suggest using any NAVY and KKFA's CLSOFF to test as there are ample test data.  For the rest of KKFA.... there hasn't been closeout info selected by customer, so it will just be a dash -

If the PPM Shipment belongs to a customer in the Marine Corps/Navy/Coast Guard then the closeout office will show the GBLOC value (TVCB, NAVY, USCG)

If the PPM Shipment belongs to a customer in  ARMY or Air Force, the closeout / transportation office will display for CLSOFF and PPMSIT if you'd like to see ones with a location vs just blank/ '-'

Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Verification Steps for Author
These are to be checked by the author.

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 6bb1f038915594431234d68e1711faac2e748ccc

Yes, Thanks  for noticing Reggie, I've moved out of draft


devops: Switch setup-dev to using brew for pre-commit

As discussed on Discord: https://discord.com/channels/936728116712316989/1245267066823508041

Actually brew install maturin installs rust outside of rustup which causes the build to break! So instead this installs brew install pipx and then uses pipx, which is the recommended installer for maturin. It will check if maturin exists elsewhere and not attempt to install if it already exists.


CY-2445-Validate-Empty-Files

Added Validation for empty file , and a simple test

Update setup py plugin yaml and changelog txt. version 2.6.4.


rust-code-analysis: 0.0.23 -> 0.0.25

Diff: https://diff.rs/rust-code-analysis-cli/0.0.23/0.0.25
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 234507 run on aarch64-darwin 1

1 package built:

rust-code-analysis


[patch] Simplify loop signature

Patches a bug when instantiating multiple for nodes with variations in the output format, and simplifies the for-node signature.
Before:
from pyiron_workflow import Workflow

n = Workflow.create.for_node(
    body_node_class=Workflow.create.standard.Add,
    iter_on=("other",),
    obj=1,
    other=[1, 2]
)

Now:
from pyiron_workflow import Workflow

n = Workflow.create.for_node(
    body_node_class=Workflow.create.standard.Add,
    iter_on="other",
    obj=1,
    other=[1, 2]
)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 91.393%

Totals

Change from base Build<PHONE_NUMBER>7:
0.008%

Covered Lines:
2920

Relevant Lines:
3195

💛  - Coveralls


Centos RPM

Is it planned to do the  rpm for Centos8?
Is there any estimated date?
Thanks,

We're in the final phases of testing and should have it out in the next few days.

Sorry for the delay here, we originally made rpm packages for Centos7 only. Per your request we have now added Centos8 rpm packages as well which will be supported moving forwards.
https://keydb.dev/downloads.html


Feature/data record display

Feature: Data record display
Description

Data records are displayed in a table with the additional field data displayed in expandable nested table.
Delete record functionality also implemented

Commits

[x] Commits are well named.
[x] Commits have descriptive messages.
[x] Each commit introduces atomic changes (optional)

PR Scope

[x] PR is appropriately small.
[x] PR is focused on single problem.

PR Review

[x] Reviewers:

Vlad H.

Code Quality

[x] Consistent formatting.
[x] Functions are relatively small.
[x] Few instances of duplicate code.
[x] Few instances of dead code.

Some commented code present that will be used in a future pull request for features to edit the data records. Should be ignored for now.


fix: add a name to every controller we have

Previous to the version v0.19.0 of controller-runtime it was possible to have the same name for every controller, but in the new version this is not allow anymore by the following PR https://github.com/kubernetes-sigs/controller-runtime/pull/2902
Now we have a specific name for every controller and this may improve the logging process.
Closes #5640

/test depth=push


The type or namespace name 'System' could not be found

Environment data
dotnet --info output:
.NET Command Line Tools (2.1.103)

Product Information:
  Version:                       2.1.103
  Commit SHA-1 hash:  60218cecb5

Runtime Environment:
 OS Name:     Windows OS
 Version:        6.1.7601 OS
 Platform:      Windows
 RID:              win7-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.103\

Microsoft .NET Core Shared Framework Host
  Version  : 2.0.6
  Build      : 74b1c703813c8910df5b96f304b0f2b78cdf194d

VS Code version:
1.21.1
C# Extension version:
1.14.0
Issue:
I upgraded from VS Code 1.19 and C# Extension 1.13 to the latest VS Code and # Extension and all of sudden every reference is all messed up, but I'm able to do dotnet build without issues. Attached screenshot and trace logs from OmniSharp.
OmniSharp.log

@dmumladze I can confirm that CLI version 2.1.300-preview3-008443 seems to work for me, at least when creating a simple class library.

@rchande I deleted the entire source branch and did rebuild/restore from scratch..still the same.

@dmumladze Is there a way I could get access to this project in order to debug further? Also, I noticed one interesting discrepancy, but I'm not sure if it means anything: In your O# log, the project directory contains an obj directory (as you would expect after restore). However, in your screenshot, there's no obj directory visible. Any idea why that might be?

Also, @dmumladze if it's not possible for you to share all the source (.cs) files, would it be possible for you to share a version of the .csproj file with anything private removed? I suspect that that's where the problem lies...

@dmumladze One more question for you: I noticed that the output c:\Projects\ProjectCollection\ProjectName\Source\Middleware\Core\Common\OneCRM.Common\OneCRM.Common.csproj appears in your log. Can you confirm that you've run dotnet restore for that OneCRM.common project?

@object directory missing: It's hidden from .settings file
@OneCRM.common project: Restore runs Ok
Unfortunately I cannot share.

@dmumladze My current hypothesis is that something is going wrong when OmniSharp uses MSBuild to build your project that results in us not finding the right reference paths. I added some diagnostics to OmniSharp to collect more info. Please give this a try:
Install the 15.0-beta4 release of C# extension for VS Code: https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.15.0-beta4 (basically, download the .vsix file and use the extension manager in VS Code to "install from VSIX")
In "user settings", set 2 options:
"omnisharp.loggingLevel": "debug" : I think you already had this set, causes O# to log more info
"omnisharp.path": "latest": We added a new feature to the extension that will download the latest build of Omnisharp from https://github.com/OmniSharp/omnisharp-roslyn. In this case, I recently added https://github.com/OmniSharp/omnisharp-roslyn/pull/1151, which will log more project info
Then, do whatever you did to load your project and share your OmniSharp log again. Note that it will print lots of file paths. If you want to elide your username, go ahead, but try to leave paths as intact as possible. Hopefully this will help us diagnose what's happening on your machine.

I'm behind the proxy, and even though I set correct settings, I'm still not able to download neither extension nor "latest" per configuration you've provided ("omnisharp.path": "latest").
The proxy issue is something that's been there in VS Code for a long time. Note that I'm using proxy settings as below, but it never works (let's leave this as is for now).
"http.proxy": "http://DOMAIN%5Cusername:password@webproxy.blabla.net:8080",
"http.proxyStrictSSL": false,

OR
"http.proxy": "http://webproxy.blabla.net:8080"

So, back to the extension issue... I was only able to install C# Extension v1.15.0-beta4 from VSIX and manually download and install omnisharp-win-x64-1.29.1.zip as well as coreclr-debug-win7-x64.zip. Once I installed these three, then I modified the settings file with "omnisharp.path": "latest" and restarted VS Code. Then it failed with below.
Error occured in loading omnisharp from omnisharp.path
Could not start the server due to Error: Could not download the latest version file due to Error: 407

I removed "omnisharp.path": "latest" and restarted again. See attached.
OmniSharp.log

@dmumladze Try downloading this https://roslynomnisharp.blob.core.windows.net/releases/1.29.2-beta.139/omnisharp-win-x86.zip . Unzip it wherever you like and use the omnisharp.path setting to point at the omnisharp.exe within it.

OmniSharp will only process the first TFM in your project. Maybe try switching them?

@DustinCampbell I think switching isn't needed, since projects I'm opening in VS Code are the ones needed to be build for .NET Core.

Did you try and find that it didn't make a difference?

I suspect that this might be the same issue as https://github.com/OmniSharp/omnisharp-vscode/issues/2295

We've merged a fix to #2295 to OmniSharp. Try setting "omnisharp.path" in the VS Code settings to "latest". This will cause C# for VS Code to download and use the latest build of OmniSharp, which contains that fix.

@DustinCampbell We have stopped using VSCode for now... It is unfortunate, but it's the decision we made due to this and other issue. For the other issue, there seems to be solution in using a different NTLM lib.

@dmumladze Sorry to hear that. If you have time, it would be helpful to us (and other users) if you could confirm whether the fix for #2295 works for you.

not sure if this is related/helpful. I had two visual studio code instances open, one was my angular CLI project (which was open first) then I launched a new visual studio code instance and opened my C# project folder and received this error/issue.
after closing both and only opening my C# project the issue went away.

@rchande I tried with latest version 1.30.1 and logs are attached. Should I try your beta version fro which you'd provided the link in above comment?
1.30.1.txt

I'm seeing similar issue with Monaco editor.
Followed Che csharp LS setup script as reference to setup omnisharp and its dependencies.
Picked up a sample project from omnisharp test-projects and fired up the editor.
Editor: Monaco v0.13.0
Language client: monaco-languageclient v0.6.3
Omnisharp: v1.32.1
dotnet: sdk-2.1.302-linux

I am facing the same issues behind the proxy.
.NET Core SDK (reflecting any global.json):
Version:   2.1.401
Commit:    91b1c13032
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.14393
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\2.1.401\

Original issue has been fixed in ms-vscode.csharp-1.17.0, and proxy issue is still there, but workaround is easy:
Create folders (note the version 1.32.6; this is per version you download)
%userprofile%.vscode\extensions\ms-vscode.csharp-1.17.0.omnisharp\1.32.6
%userprofile%.vscode\extensions\ms-vscode.csharp-1.17.0.debugger\
Download and unzip the debugger and omnisharp packages manually, and restart vscode.
More on the proxy issue: Proxy authentication can be done either by NTLM, Digest, or Negotiate.. In my corp case it must be as NTLM, but VSCode is doing the Negotiate.. So, until that issue is resolved, I'm stuck with manual, which I don't and isn't as annoying as "'System' could not be found" issue I was getting earlier.
Thanks for the fix provided in 1.17.0 version!

Getting this with latest stuff.
CoreFx 3.0.0 preview 2
VSCode 1.30.2
c# extension 1.18.0-beta6
OmniSharp for Windows (.NET 4.6 / x64), Version = 1.32.11-beta.1
My personal home workstation, Nothing special about the network here.

@tdaniely Can you try installing .Net Core Build Tools as described here and checking if the error still reproduces?

I had those installed.
The error stopped when I installed VS 2019 Preview which comes with MSBuild 16.
The bundled MSBuild that comes with omnisharp did not work.
The MSBuild from updated VS 2017 did not work.
With the 2019 Preview installed I see no errors in VSC and <LangVersion>8.0</LangVersion> is working as expected.

Experiencing the same issue on macOS.
Attempted resolution:

Uninstall C# extension within VS Code
Reload VS Code
Exit VS Code
rm -rf ~/.vscode/extensions/ms-vscode.csharp-1.17.1/
Launch VS Code
Install C# extension
Restart VS Code
Wait for OmniSharp to download

Attempted with .NET Core 3.0 Preview 1:
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview-010184
 Commit:    c57bde4593

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.14
 OS Platform: Darwin
 RID:         osx.10.14-x64
 Base Path:   /usr/local/share/dotnet/sdk/3.0.100-preview-010184/

Host (useful for support):
  Version: 3.0.0-preview-27324-5
  Commit:  63a01b08e5

.NET Core SDKs installed:
  2.1.302 [/usr/local/share/dotnet/sdk]
  3.0.100-preview-010184 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview-19075-0444 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview-27324-5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

Attempted again with .NET Core 3.0 Preview 3:
NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview3-010431
 Commit:    d72abce213

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.14
 OS Platform: Darwin
 RID:         osx.10.14-x64
 Base Path:   /usr/local/share/dotnet/sdk/3.0.100-preview3-010431/

Host (useful for support):
  Version: 3.0.0-preview3-27503-5
  Commit:  3844df9537

.NET Core SDKs installed:
  2.1.302 [/usr/local/share/dotnet/sdk]
  3.0.100-preview-010184 [/usr/local/share/dotnet/sdk]
  3.0.100-preview3-010431 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview-19075-0444 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview3-19153-02 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview-27324-5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview3-27503-5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

C# extension constantly tells me I need to restore packages.  Upon restoring, it immediately prompts again.  However, my project doesn't rely on any NuGet packages:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netcoreapp3.0</TargetFramework>
    <LangVersion>8.0</LangVersion>
    <NullableReferenceTypes>true</NullableReferenceTypes>
    <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
  </PropertyGroup>

  <PropertyGroup Condition=" '$(Configuration)' == 'Debug' ">
  </PropertyGroup>

  <PropertyGroup Condition=" '$(Configuration)' == 'Release' ">
  </PropertyGroup>

</Project>

Here's what shows up when I click the Restore button:
  Persisting no-op dg to /Users/paul/git/Test/Test.Base/obj/Test.Base.csproj.nuget.dgspec.json
  Restore completed in 11.5 sec for /Users/paul/git/TEst/Test.Base/Test.Base.csproj.
Done: 0.

There are two warnings in the OmniSharp log:
[warn]: OmniSharp.MSBuild.PackageDependencyChecker
        Test.Base: Found implicit package reference 'Microsoft.NETCore.App', but none of the versions in the lock file ("3.0.0-preview-27324-5") satisfy [3.0.0, )
[warn]: OmniSharp.MSBuild.PackageDependencyChecker
        Test.Base: Did not find 'Microsoft.NETCore.App' in lock file.

Presumably 3.0.0-preview-27324-5 < 3.0.0.  Since I'm not explicitly specifying a version anywhere besides TargetFramework, and that TargetFramework works fine in VS 2019 Preview, I'm unsure how to proceed.

Confirmed that this remains an issue even with a fresh project created with dotnet new console.  The resulting csproj:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.0</TargetFramework>
  </PropertyGroup>

</Project>

I ran into this when installing 3.0.0-preview3 (was on 3.0.0-preview before).
Tried to set "omnisharp.path": "latest", but then got The SDK 'Microsoft.NET.Sdk' specified could not be found when the newest OmniSharp got installed. Then restarted VS Code and it wen't back to the "restore packages" loop and missing reference errors all over.
Then installed VS 2019 preview and it went back to normal (kudos @tdaniely !).
Some logs in case it helps (project path/name are anonymized):
Starting OmniSharp server at 4/5/2019, 4:32:05 PM
    Target: c:\Users\jrend\PATH\TO\PROJ

OmniSharp server started.
    Path: C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\OmniSharp.exe
    PID: 12660

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on Windows 6.2.9200.0 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 1 MSBuild instance(s)
            1: StandAlone 15.0 - "C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\msbuild\15.0\Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        MSBUILD_EXE_PATH environment variable set to 'C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\msbuild\15.0\Bin\MSBuild.exe'
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: StandAlone 15.0 - "C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\msbuild\15.0\Bin"
            CscToolExe = csc.exe
            CscToolPath = C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\msbuild\15.0\Bin\Roslyn
            MSBuildExtensionsPath = C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\msbuild
            MSBuildToolsPath = C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\msbuild\15.0\Bin
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in 'c:\Users\jrend\PATH\TO\PROJ'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in 'c:\Users\jrend\PATH\TO\PROJ'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in 'c:\Users\jrend\PATH\TO\PROJ'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location 'c:\Users\jrend\PATH\TO\PROJ' on host 17512.
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file 'c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj'.
c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj(1,1)
Microsoft.Build.Exceptions.InvalidProjectFileException: The SDK 'Microsoft.NET.Sdk' specified could not be found.  c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj
   at Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args)
   at Microsoft.Build.Evaluation.Evaluator`4.ExpandAndLoadImportsFromUnescapedImportExpressionConditioned(String directoryOfImportingFile, ProjectImportElement importElement, List`1& projects, Boolean throwOnFileNotExistsError)
   at Microsoft.Build.Evaluation.Evaluator`4.ExpandAndLoadImports(String directoryOfImportingFile, ProjectImportElement importElement)
   at Microsoft.Build.Evaluation.Evaluator`4.EvaluateImportElement(String directoryOfImportingFile, ProjectImportElement importElement)
   at Microsoft.Build.Evaluation.Evaluator`4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)
   at Microsoft.Build.Evaluation.Evaluator`4.Evaluate(ILoggingService loggingService, BuildEventContext buildEventContext)
   at Microsoft.Build.Evaluation.Project.Reevaluate(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings)
   at Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings)
   at Microsoft.Build.Evaluation.Project.Initialize(IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectLoadSettings loadSettings)
   at Microsoft.Build.Evaluation.Project..ctor(String projectFile, IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings)
   at Microsoft.Build.Evaluation.ProjectCollection.LoadProject(String fileName, IDictionary`2 globalProperties, String toolsVersion)
   at OmniSharp.MSBuild.ProjectLoader.EvaluateProjectFileCore(String filePath)
   at OmniSharp.MSBuild.ProjectLoader.BuildProject(String filePath)
   at OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.Load(String filePath, ProjectIdInfo projectIdInfo, ProjectLoader loader)
   at OmniSharp.MSBuild.ProjectManager.<>c__DisplayClass31_0.<LoadProject>b__0()
   at OmniSharp.MSBuild.ProjectManager.LoadOrReloadProject(String projectFilePath, Func`1 loader)

[fail]: OmniSharp.MSBuild.ProjectManager
        Attempted to update project that is not loaded: c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj

dotnet --info:
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100-preview3-010431
 Commit:    d72abce213

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17763
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview3-010431\

Host (useful for support):
  Version: 3.0.0-preview3-27503-5
  Commit:  3844df9537

.NET Core SDKs installed:
  2.1.503 [C:\Program Files\dotnet\sdk]
  2.1.505 [C:\Program Files\dotnet\sdk]
  2.2.104 [C:\Program Files\dotnet\sdk]
  3.0.100-preview3-010431 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0-preview3-19153-02 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0-preview3-27503-5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.0.0-preview3-27504-2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

After restarting VS Code:
Starting OmniSharp server at 4/5/2019, 4:43:06 PM
    Target: c:\Users\jrend\PATH\TO\PROJ

OmniSharp server started.
    Path: C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\OmniSharp.exe
    PID: 17524

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on Windows 6.2.9200.0 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Visual Studio Community 2017 15.9.28307.586 - "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin"
            2: StandAlone 15.0 - "C:\Users\jrend\.vscode\extensions\ms-vscode.csharp-1.18.0\.omnisharp\1.32.14-beta.11\msbuild\15.0\Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Visual Studio Community 2017 15.9.28307.586 - "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin"
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in 'c:\Users\jrend\PATH\TO\PROJ'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[info]: OmniSharp.MSBuild.ProjectSystem
        No solution files found in 'c:\Users\jrend\PATH\TO\PROJ'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for 'c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in 'c:\Users\jrend\PATH\TO\PROJ'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location 'c:\Users\jrend\PATH\TO\PROJ' on host 1592.
[info]: OmniSharp.MSBuild.ProjectManager
        Successfully loaded project file 'c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj'.
[info]: OmniSharp.MSBuild.ProjectManager
        Adding project 'c:\Users\jrend\PATH\TO\PROJ\PROJ.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Update project: ffs
[warn]: OmniSharp.MSBuild.PackageDependencyChecker
        ffs: Did not find 'Microsoft.NETCore.App' in lock file.

Similar issue on mac too.
C# Extension version: 1.18.0
MacOs: Mojave 10.14.3
VS Code version: 1.32.3(1.32.3)
Issue: Every time I start my Unity project(C# project), I got a message.

Cannot open assembly '/Users/(MYNAME)/.vscode/extensions/ms-vscode.csharp-1.18.0/.omnisharp/1.32.14-beta.11/omnisharp/OmniSharp.exe': No such file or directory.
It is really weird cause my machine is mac, not window. (try to find .exe file on mac?)

My Solution: Comment out following line.
Preference: Open User Settings > Omnisharp: Path > Edit in settings.json >

{
"window.zoomLevel": 1,
"powermode.enabled": true,
"extensions.autoUpdate": false,
// "omnisharp.path": "latest" (Comment out this line)
}

Result:

    Starting OmniSharp on MacOS 10.14.3 (x64)

    DotNetPath set to dotnet

    Located 2 MSBuild instance(s)
        1: Mono 15.0 - "/Library/Frameworks/Mono.framework/Versions/5.16.0/lib/mono/msbuild/15.0/bin"
        2: StandAlone 15.0 - "/Users/(MY NAME)/.vscode/extensions/ms-vscode.csharp-1.18.0/.omnisharp/1.32.11/omnisharp/msbuild/15.0/Bin"

    Registered MSBuild instance: Mono 15.0 - "/Library/Frameworks/Mono.framework/Versions/5.16.0/lib/mono/msbuild/15.0/bin"
        CscToolPath = /Users/(MY NAME)/.vscode/extensions/ms-vscode.csharp-1.18.0/.omnisharp/1.32.11/omnisharp/msbuild/15.0/Bin/Roslyn
        CscToolExe = csc.exe

    Detecting Cake files in '/Users/(MY NAME)/AngularMonitor'.

    Could not find any Cake files

    Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.

    Detecting projects in '/Users/(MY NAME)/AngularMonitor/AngularMonitor.sln'.

    Queue project update for '/Users/(MY NAME)/AngularMonitor/Assembly-CSharp-Editor.csproj'

    Detecting CSX files in '/Users/(MY NAME)/AngularMonitor'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider

    Loading project: /Users/(MY NAME)/AngularMonitor/Assembly-CSharp-Editor.csproj

    Configuration finished.

    Omnisharp server running using Stdio at location '/Users/(MY NAME)/AngularMonitor' on host 12609.

    Successfully loaded project file '/Users/(MY NAME)/AngularMonitor/Assembly-CSharp-Editor.csproj'.

    Adding project '/Users/(MY NAME)/AngularMonitor/Assembly-CSharp-Editor.csproj'

    Update project: Assembly-CSharp-Editor

I got these messages on Output window, and Everything goes fine.

I am also having issues with Omnisharp, I've tried deleting everything, reinstalling on mac. I am getting a whole bunch of type or namespace errors, but when I use VS2019 it works just fine.
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Mono 15.0 - "/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin"
            2: StandAlone 15.0 - "/Users/jbejarano/.vscode/extensions/ms-vscode.csharp-1.19.0/.omnisharp/1.32.18/omnisharp/.msbuild/Current/Bin"
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        SUCCESS: Resolved to '/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Microsoft.Build.Utilities.Core.dll' (name-only).
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        SUCCESS: Resolved to '/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Microsoft.Build.Tasks.Core.dll' (name-only).
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        SUCCESS: Resolved to '/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Microsoft.Build.Framework.dll' (name-only).
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        SUCCESS: Resolved to '/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Microsoft.Build.dll' (name-only).
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Mono 15.0 - "/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin"
            CscToolPath = /Users/jbejarano/.vscode/extensions/ms-vscode.csharp-1.19.0/.omnisharp/1.32.18/omnisharp/.msbuild/Current/Bin/Roslyn
            CscToolExe = csc.exe
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Attempting to resolve 'Microsoft.CodeAnalysis.VisualBasic.Workspaces, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        FAILURE: Could not locate '/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Microsoft.CodeAnalysis.VisualBasic.Workspaces.dll'.
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Attempting to resolve 'Microsoft.CodeAnalysis.VisualBasic.Features, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
[dbug]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        FAILURE: Could not locate '/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Microsoft.CodeAnalysis.VisualBasic.Features.dll'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/Users/jbejarano/DTDMS.Eforms.AllServicesTest/apps/Fields'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.WorkspaceInitializer
        Project system 'OmniSharp.DotNet.DotNetProjectSystem' is disabled in the configuration.
[dbug]: OmniSharp.MSBuild.ProjectSystem
        MSBuild environment:
Mode: Standalone
RunningTests: False
RunningInVisualStudio: False
MSBuildToolsDirectory32: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin
MSBuildToolsDirectory64: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin
MSBuildSDKsPath: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/Sdks
CurrentMSBuildConfigurationFile: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/MSBuild.dll.config
CurrentMSBuildExePath: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin/MSBuild.dll
CurrentMSBuildToolsDirectory: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin
VisualStudioInstallRootDirectory:
MSBuildExtensionsPath: /Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/15.0/bin

Disable the C# plugin and the error messages will go away (KISS).

I had been dealing with the same issue for an hour. I have tried everything here and none of them worked but as a final try out, I uninstall C# extension once more, then reload, then install it again. Now it is working!  It must be a really weird bug.

Same issue. Only context I can provide other than the above is that this started occurring after updating the project to use .NET Core SDK 3.0.

SDK 2.2 was installed
Projects were created targeting v2.2
SDK 3.0 was installed
Project files were updated to target v3.0

At this point the errors started being reported in the Problems panel.

For some reason, updating Visual Studio 2019 to v16.3.3 (from v16.2.4). No clue why that would effect anything, but the errors suddenly went away part-way through that install.
Unfortunately, this means I don't have any errors to log for your investigation now. Hopefully someone else can provide.

OmniSharp uses msbuild from Visual Studio 2019 if it's installed on your machine.
The minimum version of msbuild needed for .NET Core 3.0 is 16.3, which only ships with VS 2019 16.3.x.
So if you had VS 2019 16.2, then OmniSharp used that msbuild and it was too old to support .NET Core 3.0 RTM which caused your errors.

If it's not installed, OmniSharp will use the msbuild version from the SDK? Or is the decision tree more complex than that?
Just getting a full understanding so I can communicate out to my organization.

if it's not installed, then it uses it's own bundled msbuild which is now version 16.3 (but a simpler version that cannot handle i.e some Unity projects or complex legacy frameworks, that's why VS is always preferred).
.NET Core 3.0 has raised the minimum msbuild level required from 16.0 to 16.3 between the final previews and RTM version, which caught us a bit off guard, that's why OmniSharp worked fine with previews but not RTM of .NET Core 3.0, as we used to ship with 16.0 - which is really what this entire issue has been about.
hope this explains

Installing VS 2019 16.3.x worked for me 👍

Explains perfectly. Thanks!

@Mr-Markus I'm facing the same issue, but i'm in Linux..., what to do?

I was having the same issue. Agree with the last explanation, upgraded my msbuild to 16.6 and works fine now!
I followed this https://github.com/OmniSharp/omnisharp-vscode/issues/3407#issuecomment-554111373 and installed mono via online pkg download as opposed to doing via brew

I am having the same issue with latest everything at this moment (vs & msbuild 16.7, vscode 1.47.3, omnisharp is 'latest').
My debug log of omnisharp is here
https://gist.github.com/majkinetor/d7985109c607ca9420e07cc4a2627f61
Can anybody help ? I hate to open VS just because of this.

does it work in VS? your omnisharp log has no errors so it's difficult to say

Yes, it works. It works with dotnet CLI too.
My omnisharp log shows missing namespaces
    "QuickFixes": [
      {
        "LogLevel": "Error",
        "Id": "CS0234",
        "Tags": [],
        "FileName": "c:\\Work\\_\\nil\\jafin2k\\top\\top-rest\\source\\service\\Top.Rest.Api\\Controllers\\Security\\RolesController.cs",
        "Line": 11,
        "Column": 20,
        "EndLine": 11,
        "EndColumn": 25,
        "Text": "The type or namespace name 'Model' does not exist in the namespace 'Top.Rest.Api' (are you missing an assembly reference?)",
        "Projects": [
          "Top.Rest.Api"
        ]
      },

yes, but those are compiler diagnostics, not OmniSharp errors. I was referring to the fact that there is nothing suspicious in OmniSharp loading process.
You can try the latest prerelease https://github.com/OmniSharp/omnisharp-vscode/releases/tag/v1.23.0-beta2 (make sure to remove "omnisharp.path":"latest" setting before).
Also, can you provide a repro project? btw. your problem is different from the one tracked in this thread which was related to discovery of system ref assemblies.

I will close this issue to avoid any further confusion.
The original issue tracked here was caused by MSBuild < 16.3 being used for .NET Core 3.x apps. We have raised the minimum discovered version of MSBuild in the meantime.

OK @filipw , I reported new problem at  #3962.


Automated Test for Sample 04.0

Feature #194
Upstream 1269
Description
Automated integration tests that run in CI should be added for samples to prevent the samples breaking due to changes in the EDC.
The scope of this story is to add automated integration tests for sample 04.0.
Note: it was decided that EDC integration tests should not rely on samples. However, it is desirable to have additional tests to make sure that the samples don't get broken.
Acceptance criteria

[x] Automated tests run in CI.

Tasks

[x] Create related an issue in upstream repository
[x] Verify sample matches current architecture of EDC
[x] Add integration test for sample
[x] Integrate integration test into CI

feature branch: https://github.com/agera-edc/DataSpaceConnector/tree/feature/1269-automated-tests-sample-040
sub-feature branch: https://github.com/agera-edc/DataSpaceConnector/tree/feature/1269/252-automated-test-in-sample-040

Upstream issue closed.
https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/1269


Remove Nuget reference to System.Net.WebSockets.Client

Since this page doesn't redirect to a different Net version (but previous net versions in the URL do), this API has been available since 4.6: https://docs.microsoft.com/en-us/dotnet/api/system.net.websockets?view=netframework-4.6

Fixed in bf1780a86b974f039b7fb8c0973efbfb47d533ca


[SPARK-41668][SQL] DECODE function returns wrong results when passed NULL

What changes were proposed in this pull request?

The DECODE function was implemented for Oracle compatibility. It works similar to CASE expression, but it is supposed to have one major difference: NULL == NULL
https://docs.oracle.com/database/121/SQLRF/functions057.htm#SQLRF00631
The Spark implementation does not observe this, however:
> select decode(null, 6, 'Spark', NULL, 'SQL', 4, 'rocks');

NULL

The result is supposed to be 'SQL'. This PR is to fix the issue.
Why are the changes needed?

Bug fix and Oracle compatibility.
Does this PR introduce any user-facing change?

Yes, DECODE function will return matched value when passed null, instead of always returning null.
How was this patch tested?

New UT.

cc @srielau @beliefer

Merging to master/3.3/3.2


Initial commit of TrackJoints behavior to request feedback and guidance.

I haven't used git in a while, so I am testing this initial PR, thank you!

Here is a video of this behavior in action, through a synced object: https://www.youtube.com/watch?v=sJUM4_aF3mI

The PR seems to have worked! You say it's an "initial" commit, so let us know when the feature is done, we're excited to check it out.

Thanks @stevenvergenz !  I guess my next question would be:
So far, I had the behavior inline in my app, so I haven't tested it as a behavior included in the altspace utilities yet.  In order to test this new behavior (and the options I'd like to add to it), do I need to compile the repo somehow?

Up to you if you want to expand on it now or commit it without the configuration options. That's ok with me, it is useful as it is. If you do intend to expand on it in a later PR, one concern might be that you'd have to introduce breaking changes to the interface, in order to add the configuration options (although I guess you could implement it in a way that doesn't change the interface)
Either way, adding an example along with the behavior would definitely be nice.

@brianpeiris Thank you for the feedback!  Ah, yes I see the conflict about submitting now without options and then breaking the interface later.  Is there a way for me to test the behavior locally as a registered behavior in the altspace namespace?
Well, the other thing is I guess I am not sure if joint cube size, joints and scale are the final options that devs would need, and I was hoping to get other devs to test it and give whatever feedback or requests they'd have.  But that would require changing the interface possibly multiple times and requiring multiple merges, which is more overhead for the main developers.
So it's a tiny bit of a catch-22, and I'm happy to proceed however you prefer!
Options:

I test locally with a few config options, if possible for me to add the behavior to the altspace namespace
We merge as is, and get feedback from devs for a bit

It might be beneficial for me to learn how to do option 1, I guess?
Thanks again!

It's definitely best to test locally. You should just be able to run npm install' and then 'npm run build' to re-build the altspace.js file in dist/. You should also run npm run docto check the generated documentation underdoc/. You can stick a simple example under examples/joint-collision.html` (or whatever you decide to call it).

@brianpeiris Ok great, I will try to test locally using npm.  I will also check the generated docs, and I will make an example file.  Will it be possible to update this PR with new and edited files, or will it require a new PR? (Sorry for all the questions!  Been three years since I used git). :)  Thank you!

No worries. Yes, any changes you push to your master branch will be reflected here, so no need for a new PR

Ah, it diffs a whole branch, got it.  Thanks!  I will keep the updates coming.

Hello @stevenvergenz and @brianpeiris !
I tried to test my new 'joint tracking' behavior locally today and have run into a couple of initial problems:

The version of gulp gave me issues and I had to uninstall and reinstall it?  I got some error like the one here
Some created files like tests/src/sync.js are generated with spaces instead of tabs or vice versa, so Travis fails
Even though the npm run build command does generate a new altspace library distribution file for me, the behavior is not found and 'altspace.utilities.behaviors.TrackJoints()returns anUndefined` error in my app.

Thank you!

Hey @evhan55. Yeah, the build process is in need of update, but it seems you've managed to get it working anyway. If you could, please exclude the bulit files and the changes to tests/src/sync.js from this PR, so that it's easier to review and merge. Generally PRs should only contains source code. The build and publish scripts will take care of generating the other files when we merge your changes.

@brianpeiris Great, sounds good!  I will exclude anything that is not in src then?

Oh hm I guess it needs the gulpfile too...

Yup, you should just need the behavior source and the gulpfile. Thanks!

@brianpeiris
So far for the PR:

JointCollisionEvents.js: joint collision behavior with two config options, list of joints to check and size of dummy joint cube
gulpfile.js: adding the new behavior file
joint-collision-touch.html: Example of using the JointCollisionEvents behavior to temporarily change the color of a cube when you touch it with your right index fingertip.  Synched for multiplayer.
joint-collision-push.html: Example of using the JointCollisionEvents behavior to push a blue cube around.  The red cube can be cursor-clicked to bring the blue one back to center (I wrote this before fullspace was available).  Synched for multiplayer.

Questions:

Should I also be committing doc files?  I didn't run that yet to check how they look, but I can do that.

@brianpeiris
This PR is ready for review/merge on my end.
No scaling handled yet, but I would rather wait for dev testing.
Thank you!

Thanks @evhan55, the PR looks a lot cleaner now. No need to include the docs in the PR, and yes I think it will be fine to leave the scaling implementation out for now.
I've left a few comments for you.

Thank you for the comments!  Will re-view, re-test, re-generate docs and ping you again @brianpeiris !

:+1: Merging this now. Will follow up with another PR for the fixes.


ci: add codecov.yaml file

What is changed and how it works?
Issue Number: Close #14995
What's Changed:
ci: add codecov.yaml file

Ref:

https://github.com/PingCAP-QE/ci/issues/2171

Related changes

None

Check List
Tests

No code

Side effects

None

Release note
None

/run-test

/run-test

/merge


TransportClient support

As far as I understand currently the transport wares only support local nodes and not the TransportClient.
Is this correct? Could it generally work to forward a http request via TransportClient to an external Node?

Closing as not backported yet to elasticsearch 2.x series. We can revisit it depending on the outcome from https://github.com/elastic/elasticsearch/issues/12721


Set file filter

From<EMAIL_ADDRESS>on 2013-05-15T16:50:59Z
Have option in Preferences-->Editor-->Advanced Settings to set the default file filter for the Open file dialog.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1392

From<EMAIL_ADDRESS>on 2013-06-29T14:11:00Z
That is ironic given that the current default restricts you one file type. Most software projects I am aware of have multiple files types involved and quite honestly I would prefer that the default file type would be All Files. I realize that others would disagree which is why I suggested the option. Let the user decide.

From ccordoba12 on 2013-06-28T21:51:15Z
I don't like this one because it's too specialized. I'd rather prefer to fix the previous issue you reported.
Status: Duplicate
Mergedinto: 1391

From ccordoba12 on 2013-06-29T14:28:12Z
It's true that the main filter is set only to Python files but that's because Spyder's Editor is an specialized Python editor. It's not that useful for other file types.
But if you think this feature is really important for you, please send us a patch, because we are fine with the current situation.


Monotonicity of 0's different result than no monotonicity set

df.csv
import lightgbm as lgb
import pandas as pd

df = pd.read_csv("df.csv")
y = df['y']
X = df.drop('y', axis=1)

model_class = lgb.sklearn.LGBMRegressor
params = {
          'min_child_samples': 1,
          'subsample': 0.7,
          'subsample_freq': 1,

          'random_state': 1234,
          'deterministic': True,

          'monotone_constraints': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
          }

model = model_class(**params)
model.fit(X, y)
preds=model.predict(X)
print(preds[0:20])

params.pop('monotone_constraints', None)
model = model_class(**params)
model.fit(X, y)
preds=model.predict(X)
print(preds[0:20])

This is MRE, but more complicated examples also do this and lead to arbitrarily different results for predictions.
[15.14082331 17.42164852 17.27809565 24.66228158 31.7912921  25.07472208
 38.66674383 30.14650357 24.10321141 19.28946953 23.59302071 19.06902673
 13.8462058  50.01765005 22.09789499 15.48053459 21.67382484 23.59418642
 16.14454625 20.21541095]
[15.11855937 17.458745   17.22814776 24.65581646 31.72203189 25.0968243
 38.65681328 30.14518504 24.03192297 19.31654484 23.60164724 19.06489953
 13.85319787 50.03306803 22.07789009 15.45374806 21.75793041 23.61585482
 16.14733807 20.18282579]

Thanks for this write-up and reproducible example! I ran this code tonight and can confirm I got the same results you reported.
Experimenting with this, I found that any of the following individual changes result in the predictions being identical:

removing parameter  subsample
adding "bagging_seed": 708 to params
removing monotone_constraints

test code (click me)
import lightgbm as lgb
import pandas as pd
import numpy as np

data_url = "https://github.com/microsoft/LightGBM/files/7831557/df.csv"
df = pd.read_csv(data_url)

y = df['y']
X = df.drop('y', axis=1)

model_class = lgb.sklearn.LGBMRegressor
params = {
    'min_child_samples': 1,
    'subsample_freq': 1,
    'random_state': 1234,
    'deterministic': True,
    'monotone_constraints': [0] * X.shape[1],
}

model = model_class(**params)
model.fit(X, y)
preds1 = model.predict(X)
print(preds1[0:20])

params.pop('monotone_constraints', None)
model = model_class(**params)
model.fit(X, y)
preds2 = model.predict(X)
print(preds2[0:20])

assert np.allclose(preds1, preds2)

This definitely seems like a bug, but it seems a bit more specific than "passing all 0s for monotone_constraints results in a different model".
I think it looks like:

Providing all 0s for monotone_constraints results in a different model than if monotone_constraints are not provided, if also using bagging.

I don't find the same result as you.  Adding bagging_seed doesn't help:

import pandas as pd

df = pd.read_csv("df.csv")
y = df['y']
X = df.drop('y', axis=1)

model_class = lgb.sklearn.LGBMRegressor
params = {
          'min_child_samples': 1,
          'subsample': 0.7,
          'subsample_freq': 1,

          'random_state': 1234,
          'bagging_seed': 708,
          'deterministic': True,

          'monotone_constraints': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
          }

model = model_class(**params)
model.fit(X, y)
preds=model.predict(X)
print(preds[0:20])

params.pop('monotone_constraints', None)
model = model_class(**params)
model.fit(X, y)
preds=model.predict(X)
print(preds[0:20])

gives
[15.09656531 17.43069474 17.27949377 24.68849732 31.7121405  25.07867232
 38.73125164 30.1278061  23.99720783 19.31545673 23.53189337 19.09648957
 13.87783463 50.01956777 22.1214959  15.44131316 21.7363739  23.6298187
 16.17185313 20.28922842]
[15.08843553 17.4425064  17.2973164  24.66865837 31.6657934  25.0441509
 38.66294203 30.1151615  24.02734721 19.33964692 23.52776624 19.10077709
 13.87791364 50.02051734 22.13321018 15.45728055 21.69579512 23.65150691
 16.16314868 20.26343255]

What version of lightgbm are you on and how did you install it? I tested this on latest master (https://github.com/microsoft/LightGBM/commit/305369ddfd6b977484a961c44f400126e4f69029)

>>> lgb.__version__
'<IP_ADDRESS>'

I can try on master.
But are you aware of a specific fix?

But are you aware of a specific fix?

No, I didn't know this issue existed until this bug report. Just trying to help narrow it down further.

Same result on latest from pypi  on different machine after only installing:
virtualenv jon
source jon/bin/activate
pip install numpy pandas sklearn lightgbm

and the same script using bagging_seed set gives:
[15.09656531 17.43069474 17.27949377 24.68849732 31.7121405  25.07867232
 38.73125164 30.1278061  23.99720783 19.31545673 23.53189337 19.09648957
 13.87783463 50.01956777 22.1214959  15.44131316 21.7363739  23.6298187
 16.17185313 20.28922842]
[15.08843553 17.4425064  17.2973164  24.66865837 31.6657934  25.0441509
 38.66294203 30.1151615  24.02734721 19.33964692 23.52776624 19.10077709
 13.87791364 50.02051734 22.13321018 15.45728055 21.69579512 23.65150691
 16.16314868 20.26343255]

version:
>>> lgb.__version__
'3.3.2'

3.3.2 is a special release that doesn't include most of the changes currently on master. It's just 3.3.1 + one small patch requested by the CRAN maintainers (see discussion in #4923).
To install from latest master:
git clone --recursive https://github.com/microsoft/LightGBM.git
cd python-package
python setup.py install

Same result:
[LightGBM] [Warning] Auto-choosing col-wise multi-threading, the overhead of testing was 0.000330 seconds.
You can set `force_col_wise=true` to remove the overhead.
[LightGBM] [Info] Total Bins 665
[LightGBM] [Info] Number of data points in the train set: 253, number of used features: 13
[LightGBM] [Info] Start training from score 22.522925
[15.09656531 17.43069474 17.27949377 24.68849732 31.7121405  25.07867232
 38.73125164 30.1278061  23.99720783 19.31545673 23.53189337 19.09648957
 13.87783463 50.01956777 22.1214959  15.44131316 21.7363739  23.6298187
 16.17185313 20.28922842]
[LightGBM] [Warning] Auto-choosing col-wise multi-threading, the overhead of testing was 0.000261 seconds.
You can set `force_col_wise=true` to remove the overhead.
[LightGBM] [Info] Total Bins 665
[LightGBM] [Info] Number of data points in the train set: 253, number of used features: 13
[LightGBM] [Info] Start training from score 22.522925
[15.08843553 17.4425064  17.2973164  24.66865837 31.6657934  25.0441509
 38.66294203 30.1151615  24.02734721 19.33964692 23.52776624 19.10077709
 13.87791364 50.02051734 22.13321018 15.45728055 21.69579512 23.65150691
 16.16314868 20.26343255]

>>> import lightgbm as lgb
>>> print(lgb.__version__)
<IP_ADDRESS>

Ah yeah you're right, I just tried again and got the same result you did. I crossed out the suggestion about bagging_seed in https://github.com/microsoft/LightGBM/issues/4936#issuecomment-1007878334, must have accidentally changed two things at once when I thought I was testing only that.


[CupertinoPageRoute] Gestures don't respond when clicking immediately after swiping back

The problem is that after I use cupertionPageroute, when I swipe back to the previous page on iOS device, there is a high probability that the first time I click on the content of the previous page, nothing happens until I click twice, especially when you are halfway through the slide. Let go, and then quickly click on the previous page. The online business here is very seriously affected.
video
https://user-images.githubusercontent.com/23304639/103204325-11c13800-4932-11eb-93c2-a0bce2b11723.mov
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel unknown, 1.22.4, on macOS 11.1 20C69 darwin-x64, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
[!] Android Studio (version 4.1)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] VS Code (version 1.52.1)
[✓] Connected device (2 available)
! Doctor found issues in 2 categories.
this is the mini example
main.dart
import 'package:flutter/material.dart';
import 'package:trace_startup/page.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: FlatButton(
        color: Colors.blue,
        onPressed: () {
          Navigator.push(context, CupertinoPageRoute(builder: (context) {
            return SecondPage();
          }));
        },
        child: Container(
          height: double.infinity,
          width: double.infinity,
          child: Center(
            child: Text(
              'push new page',
            ),
          ),
        ),
      ),
    );
  }
}

page.dart
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

class SecondPage extends StatelessWidget{
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text("second page"),),
      body: Center(child: Text("second page"),),
    );
  }

}

Tried your code sample on iPhoneSE simulator, but didn't notice the issue. I was able to swipe from second screen to first properly.
https://user-images.githubusercontent.com/67046386/103211520-6d89c200-492e-11eb-9859-ed39cd2d0403.mov

flutter doctor -v

[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.5 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision<PHONE_NUMBER> (3 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (2 available)
    • sdk gphone x86 arm (mobile)         • emulator-5554
      • android-x86 • Android 11 (API 30) (emulator)
    • iPhone SE (2nd generation) (mobile) • 6C85835D-FBFD-4AB3-8DE8-B4FAD35E5367
      • ios         • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)

• No issues found!

Tried your code sample on iPhoneSE simulator, but didn't notice the issue. I was able to swipe from second screen to first properly.

I think your sliding range is too large. Try to release it when sliding to the middle, or use a real machine to simulate the side-slip effect, it is very easy to appear

@darshankawar look this Real machine example，Don't swipe  the pages to right edge with your fingers。This sliding effect is very common on large screen phones after iphone 11 pro max, so we have received a lot of feedback of this kind
https://user-images.githubusercontent.com/23304639/103214486-7b9a0b80-494b-11eb-959c-94faf192e89f.mov

Tried your code sample on iPhoneSE simulator, but didn't notice the issue. I was able to swipe from second screen to first properly.

I think your sliding range is too large. Try to release it when sliding to the middle, or use a real machine to simulate the side-slip effect, it is very easy to appear。

https://user-images.githubusercontent.com/23304639/103214641-f105dc00-494b-11eb-89cd-fdd40000b28f.mov

flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.5 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision<PHONE_NUMBER> (3 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (2 available)
    • sdk gphone x86 arm (mobile)         • emulator-5554
      • android-x86 • Android 11 (API 30) (emulator)
    • iPhone SE (2nd generation) (mobile) • 6C85835D-FBFD-4AB3-8DE8-B4FAD35E5367
      • ios         • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)

• No issues found!

CC @xster

cc @dkwingsmt

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.1, on macOS 11.2.2 20D80 darwin-x64, locale en-GB)
    • Flutter version 2.0.1 at /Users/tahatesser/Code/flutter_stable
    • Framework revision c5a4b4029c (4 days ago), 2021-03-04 09:47:48 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.54.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

[✓] Connected device (3 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS 14.4
    • macOS (desktop)        • macos                     • darwin-x64     • macOS 11.2.2 20D80 darwin-x64
    • Chrome (web)           • chrome                    • web-javascript • Google Chrome 88.0.4324.192

• No issues found!

[✓] Flutter (Channel master, 2.1.0-11.0.pre.145, on macOS 11.2.2 20D80 darwin-x64, locale en-GB)
    • Flutter version 2.1.0-11.0.pre.145 at /Users/tahatesser/Code/flutter_master
    • Framework revision a0ba646408 (3 days ago), 2021-03-05 22:09:03 -0500
    • Engine revision f751d04fa0
    • Dart version 2.13.0 (build 2.13.0-107.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.54.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

[✓] Connected device (3 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS 14.4
    • macOS (desktop)        • macos                     • darwin-x64     • macOS 11.2.2 20D80 darwin-x64
    • Chrome (web)           • chrome                    • web-javascript • Google Chrome 88.0.4324.192

• No issues found!

Looking at it more in detail it seems like animation curve combined with the inner workings of route might be the problem here.
https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/cupertino/route.dart#L735
Currently the dismissal animation is using the curve Curves.fastLinearToSlowEaseIn
I added some debug traces to see the animation-value and timestamps, here's a snippet how it looks close to the end of the animation.
...
flutter: buildTransitions 0.013482164725324042<PHONE_NUMBER>382) <---  barely visible as only 1% of the width is shown
flutter: buildTransitions 0.010625395290166484<PHONE_NUMBER>399)
flutter: buildTransitions 0.008203684573317105<PHONE_NUMBER>415)
flutter: buildTransitions 0.006376271156842028<PHONE_NUMBER>432)
flutter: buildTransitions 0.004842631100606232<PHONE_NUMBER>448)
flutter: buildTransitions 0.003644510584527083<PHONE_NUMBER>465)
flutter: buildTransitions 0.0027178166513320834<PHONE_NUMBER>482)
flutter: buildTransitions 0.0019632494060380923<PHONE_NUMBER>498)
flutter: buildTransitions 0.001398682602685053<PHONE_NUMBER>515)
flutter: buildTransitions 0.0009542743748859328<PHONE_NUMBER>532)
flutter: buildTransitions 0.0006366329552504046<PHONE_NUMBER>548)
flutter: buildTransitions 0.00039868855001279346<PHONE_NUMBER>565)
flutter: buildTransitions 0.00023982897851249074<PHONE_NUMBER>582)
flutter: buildTransitions 0.00013001372356491459<PHONE_NUMBER>599)
flutter: buildTransitions 0.00006018844980637539<PHONE_NUMBER>615)
flutter: buildTransitions 0.000023578998342599355<PHONE_NUMBER>632)
flutter: buildTransitions 0.000005529384273339488<PHONE_NUMBER>648)
flutter: buildTransitions 4.4712767222065963e-7<PHONE_NUMBER>665)   <--- animation will now stop as it reached ~0
flutter: AnimationStatusListener->AnimationStatus.dismissed<PHONE_NUMBER>684)  <--- status has changed, will trigger pop

As you can see, the value is almost 0 ( == barely visible at the very right edge) for about 300ms before the AnimationStatus is equal to dismissed. This means it will look like it is popped, but is still there.
Only when the status has changed to AnimationStatus.dismissed, it will call stopUserGesture
https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/cupertino/route.dart#L773
Digging further it turns out stopGesture actually blocks user-input.
https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/routes.dart#L832
This means it will by the current design block any input for some time (even though the user is not seeing anything of the previous modal) before the user can interact again. The time will depend on how far to the right you drop it, so if you drop it far to the right it will barely affect the user, but if you make a quick swipe-to-dismiss on the left side on the screen, the user will be heavily affected.

@chunhtai @TahaTesser @gspencergoog
I found that this issue was the reason for blocking the user-input during the userGesture. I tried to remove this line and can confirm the feeling was much smoother as a new tap on the previous page would respond immediately. (However with some side-effects afterwards of course). Do you have any suggestion on how to solve this in another way where it doesn't have to be blocked?
Currently the feeling is not smooth as some taps are not responding, specially when using an actual device.

@xster

Is there a schedule to solve this problem?

thanks for @proformance modification, problem sovled(but maybe other things break).
For anyone can't find related line inhttps://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/routes.dart
// before modification
  bool get _shouldIgnoreFocusRequest {
    return widget.route.animation?.status == AnimationStatus.reverse ||
      (widget.route.navigator?.userGestureInProgress ?? false);
  }
// after modification
  bool get _shouldIgnoreFocusRequest {
    return widget.route.animation?.status == AnimationStatus.reverse; // ||
      //(widget.route.navigator?.userGestureInProgress ?? false);
  }

Just found this issue, after doing a bit of work to improve the fidelity to the iOS behavior. I believe that the core issue here will be resolved once my PR (https://github.com/flutter/flutter/pull/95757) lands, but would appreciate any eyes from folks here on whether there's anything I've missed?

Just found this issue, after doing a bit of work to improve the fidelity to the iOS behavior. I believe that the core issue here will be resolved once my PR (https://github.com/flutter/flutter/pull/95757) lands, but would appreciate any eyes from folks here on whether there's anything I've missed?

With https://github.com/flutter/flutter/issues/54090#issuecomment-609908042 and @willlockwood's PR it seems it then would be working as intended.
/cc @chunhtai should we repurpose this bug into documentation request?

So is there any news about the issue?

@darshankawar Is this still reproducible on master now that https://github.com/flutter/flutter/pull/95757 has been merged?
CC @MitchellGoodwin

@justinmc #95757 was reverted shortly after the merge

@darshankawar Is this still reproducible on master now that #95757 has been merged?

I am unable to replicate this on iOS device and simulator. The swipe works properly on first tap:
https://user-images.githubusercontent.com/67046386/192947693-7983b733-1d54-4635-ba31-1d9aef372ec4.mov
https://user-images.githubusercontent.com/67046386/192947781-d696e372-bbb9-46d9-ab26-3a998929c9d9.MP4

 runnable code sample

import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: ElevatedButton(
      //  color: Colors.blue,
        onPressed: () {
          Navigator.push(context, CupertinoPageRoute(builder: (context) {
            return SecondPage();
          }));
        },
        child: Container(
          height: double.infinity,
          width: double.infinity,
          child: Center(
            child: Text(
              'push new page',
            ),
          ),
        ),
      ),
    );
  }
}

class SecondPage extends StatelessWidget{
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text("second page"),),
      body: Center(child: Text("second page"),),
    );
  }

}

 master flutter doctor -v

dhs@Dhss-MacBook-Pro ~ % flutter doctor -v
[✓] Flutter (Channel master, 3.4.0-34.0.pre.7, on macOS 12.2.1 21D62 darwin-x64,
    locale en-GB)
    • Flutter version 3.4.0-34.0.pre.7 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f22f1344bd (37 minutes ago), 2022-09-29 00:13:42 -0400
    • Engine revision c003042e52
    • Dart version 2.19.0 (build 2.19.0-252.0.dev)
    • DevTools version 2.17.0

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 105.0.5195.125

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

@darshankawar Thanks for checking!
It's strange that this isn't reproducible anymore if https://github.com/flutter/flutter/pull/95757 was reverted...  Can anyone else still reproduce this on master?  If not then I guess we can close this.

Doesn't look to be a "first click" issue, more of a "fast click" issue. If you flick the CupertinoPageRoute closed from the left, it'll move across the screen pretty quickly and look gone, but still take some time to dispose the page widget. Only after it is disposed does the background become responsive.
The example by @darshankawar doesn't show the issue because he clicks the background pretty slowly in comparison to how a real user would interact. If you quickly swipe a route closed, then click, the issue is still reproducible.

Thanks for the response, let's keep this open as something that should be fixed then.

I can confirm the issue is very much reproducible, it's not just iOS.

code sample
import 'package:flutter/cupertino.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const CupertinoApp(
      theme: CupertinoThemeData(brightness: Brightness.light),
      home: FirstPage(),
    );
  }
}

class FirstPage extends StatelessWidget {
  const FirstPage({super.key});

  @override
  Widget build(BuildContext context) {
    return CupertinoPageScaffold(
      navigationBar: const CupertinoNavigationBar(
        middle: Text('FirstPage'),
      ),
      child: Center(
        child: CupertinoButton(
            onPressed: () {
              Navigator.push(
                context,
                CupertinoPageRoute<Widget>(
                  builder: (_) => const SecondPage(),
                ),
              );
            },
            child: const Text('Go to SecondPage')),
      ),
    );
  }
}

class SecondPage extends StatelessWidget {
  const SecondPage({super.key});

  @override
  Widget build(BuildContext context) {
    return CupertinoPageScaffold(
      navigationBar: const CupertinoNavigationBar(
        middle: Text('SecondPage'),
      ),
      child: Center(
        child: CupertinoButton(
          onPressed: () {
            Navigator.pop(context);
          },
          child: const Text('Pop'),
        ),
      ),
    );
  }
}

Steps

Go to the second page by pressing the button on the first page.
Swipe back to go back and immediately click the button on the first page.

I also included the Navigator.pop button on the second page, the issue doesn't reproduce when calling this instead of swiping back
Results
The button on the first page won't respond for a short time.
https://user-images.githubusercontent.com/48603081/194162130-d7dc2670-e2dc-454b-96b8-5e28380bdcbf.mov
https://user-images.githubusercontent.com/48603081/194162145-3e6d72a9-4468-464f-9f88-2e50a3b3d3ea.mov

thanks for @proformance modification, problem sovled(but maybe other things break).
For anyone can't find related line inhttps://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/routes.dart
// before modification
  bool get _shouldIgnoreFocusRequest {
    return widget.route.animation?.status == AnimationStatus.reverse ||
      (widget.route.navigator?.userGestureInProgress ?? false);
  }
// after modification
  bool get _shouldIgnoreFocusRequest {
    return widget.route.animation?.status == AnimationStatus.reverse; // ||
      //(widget.route.navigator?.userGestureInProgress ?? false);
  }

I believe it's not CupertinoPageRoute specific either, because this fixed the issue for me.

To be clear: Still very much an issue. The patch above made it usable, but, for example when opening a different route while the current one is closing, there's a weird jump in the animation. Where it previously wouldn't have responded at all it now does respond, but with a weird animation jump

To be clear: Still very much an issue. The patch above made it usable, but, for example when opening a different route while the current one is closing, there's a weird jump in the animation. Where it previously wouldn't have responded at all it now does respond, but with a weird animation jump

That's a great observation, given the sample reproduces the issue when swiping back with CupertinoPageRoute, this description is useful for anyone running into this issue or when trying to fix it.

Has any news ?

Sorry we haven't gotten to this yet. This isn't actively being worked on yet, but it is high on my list once I finish a few other issues, unless someone else gets to it first.

I make this as a temporary solution try fix this bug.
https://gist.github.com/FantaZZ/5a568ef74630196e32b3b461141e1360
It was copy from CupertinoRouteTransitionMixin.buildPageTransitions basically.
Only change this https://gist.github.com/FantaZZ/5a568ef74630196e32b3b461141e1360#file-custom_cupertino_page_route_builder-dart-L275
I holp it is useful for someone.

any updates?

I'm not currently working on this, but I'm leaving it assigned as this, and other route transition issues are immediate on my list after I finish the current larger issues on my queue. If someone wants to take a crack at it before then, feel free to submit a PR or reach out.

I'm facing the same issue with MaterialPageRoute, if you wait a little bit it works fine but if you tap something immediately after going back it doesn't work.

@yiiim does https://github.com/flutter/flutter/pull/153765 also fix this?

@yiiim does #153765 also fix this? Is this a dup of #48225?

Yes, the same issue.


modify objectFit.orientation to append instead of replacing the node's className

Tested on Windows 7 IE 11 && Windows 8.1 IE 11, works as before.

Sorry, seems to have conflicts - can you resolve them so I can merge it?

conflicts resolved, tested again.
By the way is this the correct view for IE:

Compared to Chrome:

Is that because of the extra element in IE?

No it’s not. IE has a bit weird behavior unfortunately with the current polyfill.


no-easy-keys for doom

How do I accomplish disabling arrow keys and other keys
to stick more to evil-mode as in this wonderful Emacs way
package?
http://danamlund.dk/emacs/no-easy-keys.html

Have you tried installing the package?

I do. It works only if I turn evil-mode off in doom. Because doom uses evil as default.
What I mean is that a package or function similar to this one in doom-evil-on...

"added the is:invalid label" - if it is invalid why they do not point h
where in the manual it deals with this issue?

Using this package only makes sense, if evil is deactivated.

I have tested this way.
That's why I asked about something similar to be used in doom-evil-on
Thx anyway.
On Sat, Jul 4, 2020 at 5:57 PM Michael Wernthaler<EMAIL_ADDRESS>wrote:

Using this package only makes sense, if evil is deactivated.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hlissner/doom-emacs/issues/3508#issuecomment-653811466,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKLPRKLIQ6QY7LTPALZCYN3RZ6JSVANCNFSM4OQB6S4A
.

You may close this now


Selective Loading

I'm using a library that apparently uses selective loading to determine which JS files to load, e.g. it has a .ios.js and .android.js file.  This appears to be tripping up webpack on require.  This feels like a big deal to workaround, but I was curious if you had run into something like this yet.
https://github.com/xinthink/react-native-material-kit

This feature is being tracked in #120


Amend the project milestone tasks

We will need a solid rationale to merge WasmEdge support upstream into the official Substrate repo. So, we changed the order of tasks to complete the performance eval first and then to propose a merge PR. That means shifting the PR task from milestone 2 to 3.
We have also found that the Substrate approach of using host functions requires a lot of changes in the WasmEdge Rust SDK. That has caused a delay and extra engineering work for the project (already completed). We will keep the total project budget the same, but respectfully ask for each milestone payment to stay the same to account for the extra work needed for milestone 2.
Signed-off-by: Michael Yuan<EMAIL_ADDRESS>Project Abstract

Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.

Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[ ] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[ ] I have read the application guidelines.
[ ] A BTC, Ethereum (USDT/USDC/DAI) or Polkadot/Kusama (aUSD) address for the payment of the milestones is provided inside the application.
[ ] The software delivered for this grant will be released under an open-source license specified in the application.
[ ] The initial PR contains only one commit (squash and force-push if needed).
[ ] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

 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.


chore(charts/sftpgo): bump version to 2.5.1

Same as #189 but with the most recent version

thanks for the quick merge, works fine for me.


update .travis.yml

Removes my email from .travis.yml as I don't need to get 15+ emails a day about this repo anymore :)

Thanks for your help in getting Docker set up!

No problem!


Update main to 1.63.0 and dev to 1.65.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

This is failing as rust_dev is not part of the channel sources. Should this be re-added?

I think so, IIUC it was removed in https://github.com/conda-forge/rust-activation-feedstock/pull/23/commits/fc33737420a51df8606c71d4fe404c1c677ebac7 so that 1.62.1 and 1.63.0 could both be released on main with https://github.com/conda-forge/rust-activation-feedstock/pull/23
cc @isuruf

@conda-forge-admin, rerender

Thanks @isuruf


Remove env/date.list, this file is now created by prow-build-docker.sh

Also updated the readme

/lgtm
/approve


1065 query filter with adjustment and test

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #1065

This uses the type checking @vicb used in his PR.

As discussed offline we should use:
https://github.com/vicb/nodejs-datastore/commit/184f0ede1a897a5ae18f6d3d93bad5d7cec995ce


Community section missing?

Trying to follow the documentation on https://nuxtseo.com/og-image/getting-started/getting-familar-with-nuxt-og-image
but it links to places like
https://github.com/harlan-zw/nuxt-og-image/blob/main/src/runtime/components/Templates/Community/SimpleBlog.vue
which no longer exist

Have things changed recently?

Looks like @yoo-minho recently fixed this up for us :raised_hands:


Minor binlog doc change

Change /bl to -bl to follow other places where / was replaced with - in help texts and documentation.
@dotnet-bot skip ci

Thanks, @dasMulli!


storagecluster: Use correct CephCluster name when ...

... waiting for CephCluster to create NooBaa. Without this, the
contoller will not create a NooBaa resource.
New generator functions have been added to create the prefixed
CephCluster name, and these functions are used wherever the name of the
CephCluster is required.
The unit tests also have been updated to use new mock objects for
CephCluster created with the above functions.

/assign @jarrpa
@Jarrpa all tests pass, including the e2e tests.


Update the metadata docs for Kubeflow v1.0

Update the metadata doc section for KF1.0 . The major change is to update the backend instruction to use gRPC service.

/assign @zhenghuiwang

/close


Every new project has a certain little warning in test output, unclear what is causing this

error polygon1 ValidationError: Feature is outside of boundary
at Module.clipToPolygonFeatures (file:///workspaces/test-three/node_modules/@seasketch/geoprocessing/src/toolbox/genPreprocessor.ts:155:11)
at clipToOceanEez (/workspaces/test-three/src/functions/clipToOceanEez.ts:52:10)

@twelch I'm not able to reproduce this so far. I created two test features like this:
npx tsx scripts/genRandomPolygon.ts --outDir examples/features --filename polygon1.json --bbox "[135.31244183762126,-1.1731109652985907,165.67652822599732,13.445432925389298]"
npx tsx scripts/genRandomPolygon.ts --outDir examples/features --filename polygon2.json

The only new output I'm seeing is this deprecation notice: [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
I initialized with 7.0.0-experimental-getFeatures-and-friends.8


 Please contact our support team so we can triage your PR, so that we can make sure it's handled appropriately.
Background

Results

Fixes https://github.com/OctopusDeploy/Issues/issues/... (optional public issue)
Fixes https://github.com/OctopusDeploy/ResearchAndDevelopment/issues/... (optional private issue)
See How we use GitHub Issues (including this flowchart
Before

After

How to review this PR

Quality :heavy_check_mark:

Pre-requisites

[ ] I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
[ ] I have considered informing or consulting the right people, according to the ownership map.
[ ] I have considered appropriate testing for my change.

[sc-66386]

We ended up going a more involved path, so this PR can be closed


Deployment of Jaeger Query 1.7 failing on AWS EKS

I am working on upgrading our Jaeger deployment on AWS EKS to Jaeger 1.7, and am running into a crashloopbackoff state with Jaeger Query. All other components install correctly.
We are using an Elastic Search back end via the AWS ES service. When the pod attempts to start, it fails, and returns a "Could not create static assets handler","error":"Cannot load index.html" error via kubectl logs. Our prior install runs without issue using Jaeger Query 1.5.
Logs and pod description from Kubectl are attached.
1.7query_pod.log
1.7query_crash.log

Are you building Jaeger yourself or using official images (btw, 1.8 is out)
We recently changed how the UI assets are distributed, they are now compiled directly into the binary rather than sitting on the file systems and requiring the query service to be pointed to them.

Thanks guyz It's working after removing static files line
  jaeger-query:
    image: jaegertracing/jaeger-query
    container_name: jaeger-query
    networks:
      - applogs
    environment:
      - SPAN_STORAGE_TYPE=elasticsearch
      - ELASTIC_PASSWORD=$ELASTIC_PASSWORD
      - no_proxy=localhost
    ports:
      - "16686:16686"
      - "16687:16687"
    command:
      [
        "--es.server-urls=http://elasticsearch:9200",
        "--span-storage.type=elasticsearch",
        "--log-level=debug",
        "--es.username=elastic",
        "--es.password=$ELASTIC_PASSWORD",
        # "--query.static-files=/go/jaeger-ui/",   // REMOVED THIS LINE AND STARTED WORKING
      ]
    depends_on:
      - jaeger-agent


pageserver/http: remove status code boilerplate from swagger spec

Problem
We specify a bunch of possible error codes in the pageserver api swagger spec. This is error prone and annoying to work with. https://github.com/neondatabase/cloud/pull/11907 introduced generic error handling on the control plane side, so we can now clean up the spec.
Summary of changes

Remove generic error codes from swagger spec
Update a couple route handlers which would previously return an error without a msg field in the response body.

Tested via https://github.com/neondatabase/cloud/pull/12340
Fixes https://github.com/neondatabase/cloud/issues/7238
Checklist before requesting a review

[X] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

Tested via https://github.com/neondatabase/cloud/pull/12340

Thanks for doing that.
@mtyazici if the control plane compiles and e2e tests pass, does that give us a good certainty that the removed error codes won't cause issues?  I'm thinking especially of the 409/412 cases that might be explicitly used in some logic somewhere.

Tested via neondatabase/cloud#12340

Thanks for doing that.
@mtyazici if the control plane compiles and e2e tests pass, does that give us a good certainty that the removed error codes won't cause issues? I'm thinking especially of the 409/412 cases that might be explicitly used in some logic somewhere.

There's some failures on https://github.com/neondatabase/cloud/pull/12340. Trying to disentangle test flakiness from the change.

@mtyazici if the control plane compiles and e2e tests pass, does that give us a good certainty that the removed error codes won't cause issues? I'm thinking especially of the 409/412 cases that might be explicitly used in some logic somewhere.

I now see we retry on any error when checking for 404 on resource deletion instead of 409/412. Could be better to fix that logic as well if it's better.

There's some failures on https://github.com/neondatabase/cloud/pull/12340. Trying to disentangle test flakiness from the change.

Failures seem to be related to how PR is titled, the tests are passing which shows there is no actual problem.

Failures seem to be related to how PR is titled, the tests are passing which shows there is no actual problem.

I retriggered the tests and they passed. Likely just flakes.

Tests are passing on https://github.com/neondatabase/cloud/pull/12340. I think we should be ok to merge.


help with app extension

I have an app extension for my Rn app which needs  react-native-vector-icons.  The icons aren't showing up, presumably because I need to tell Xcode about them in some way?
I've added libRNVectorIcons.a to the linked libraries... can't see what else to do.  Any ideas?

Ah, needed to specify the app extension as a target for each of the resources.


How to use the dict type observation

Hi,
I want to use the custom environment, I created a new environment following the steps in the document, the observation is defined as Dict type, but I got an error:
Traceback (most recent call last):
  File "/data/projects/20240628/xuance/procthor_ppo.py", line 18, in <module>
    runner = get_runner(method=parser.method,
  File "/data/projects/20240628/xuance/xuance/common/common_tools.py", line 243, in get_runner
    runner = REGISTRY_Runner[args.runner](args)
  File "/data/projects/20240628/xuance/xuance/torch/runners/runner_drl.py", line 27, in __init__
    self.agent = REGISTRY_Agents[self.config.agent](self.config, self.envs)
  File "/data/projects/20240628/xuance/xuance/torch/agents/policy_gradient/ppoclip_agent.py", line 32, in __init__
    self.policy = self._build_policy()
  File "/data/projects/20240628/xuance/xuance/torch/agents/policy_gradient/ppoclip_agent.py", line 60, in _build_policy
    representation = self._build_representation(self.config.representation, self.config)
  File "/data/projects/20240628/xuance/xuance/torch/agents/agent.py", line 192, in _build_representation
    representation = REGISTRY_Representation["Basic_MLP"](
  File "/data/projects/20240628/xuance/xuance/torch/representations/mlp.py", line 41, in __init__
    self.model = self._create_network()
  File "/data/projects/20240628/xuance/xuance/torch/representations/mlp.py", line 47, in _create_network
    mlp, input_shape = mlp_block(input_shape[0], h, self.normalize, self.activation, self.initialize,
KeyError: 0

The value of the input_shape is:{'rgb': (3, 480, 640), 'semantic': (3, 480, 640)} and the error shows that the network can not parse input_shape correctly.
Can you help me to solve this problem?
Thanks

The documents for customized environments are updated and removed to https://xuance.readthedocs.io/en/latest/documents/usage/new_envs.html.. You can try your customized envs with the newest version of XuanCe (v1.2.1).

OK, thanks for your reply.