1.13.0-beta4 fails to resolve output dll

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

Product Information:
 Version:            2.0.2
 Commit SHA-1 hash:  a04b4bf512

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.13
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.0.2/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d

VS Code version: 1.17.2
C# Extension version: C# 1.13.0-beta4
Steps to reproduce
tbh, I dno 😐
Expected  behavior
resolve output file correctly
Actual behavior
Starting OmniSharp server at 10/30/2017, 4:46:09 PM
    Target: /Users/bob/bitbucket/ourapps/bobapp/BOB.sln

OmniSharp server started wth Mono
    Path: /Users/bob/.vscode/extensions/ms-vscode.csharp-1.13.0-beta4/.omnisharp/omnisharp/OmniSharp.exe
    PID: 54944

[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Mono 15.0 - "/Library/Frameworks/Mono.framework/Versions/5.4.0/lib/mono/msbuild/15.0/bin"
            2: StandAlone 15.0 - "/Users/bob/.vscode/extensions/ms-vscode.csharp-1.13.0-beta4/.omnisharp/omnisharp/msbuild/15.0/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Mono 15.0 - "/Library/Frameworks/Mono.framework/Versions/5.4.0/lib/mono/msbuild/15.0/bin"
            CscToolPath = /Users/bob/.vscode/extensions/ms-vscode.csharp-1.13.0-beta4/.omnisharp/omnisharp/msbuild/15.0/Bin/Roslyn
            CscToolExe = csc.exe
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/Users/bob/bitbucket/ourapps/bobapp'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Found 2 Cake files.
[warn]: OmniSharp.Cake.CakeProjectSystem
        Cake script service not connected. Aborting.
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Initializing in /Users/bob/bitbucket/ourapps/bobapp
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Auto package restore: False
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Update workspace context
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Resolving projects references
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Detecting projects in '/Users/bob/bitbucket/ourapps/bobapp/BOB.sln'.
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: /Users/bob/bitbucket/ourapps/bobapp/BOB.csproj
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: /Users/bob/bitbucket/ourapps/bobapp/BOB.iOS/BOB.iOS.csproj
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: /Users/bob/bitbucket/ourapps/bobapp/BOB.Droid/BOB.Droid.csproj
[warn]: OmniSharp.MSBuild.ProjectFile.ProjectFileInfo
        AndroidManifest.xml //uses-sdk/@android:targetSdkVersion '25' is less than $(TargetFrameworkVersion) 'v8.0'. Using API-26 for ACW compilation.
[warn]: OmniSharp.MSBuild.ProjectFile.ProjectFileInfo
        The "ResolveLibraryProjectImports" task failed unexpectedly.
System.IO.FileNotFoundException: Could not load assembly 'Widex.BOB, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?
File name: 'Widex.BOB.dll'
  at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference reference, Mono.Cecil.ReaderParameters parameters) [0x00124] in <93e3fd215cb8496582dc8fb5d19f9914>:0
  at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve (System.String fullName, Mono.Cecil.ReaderParameters parameters) [0x00007] in <93e3fd215cb8496582dc8fb5d19f9914>:0
  at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve (System.String fullName) [0x00000] in <93e3fd215cb8496582dc8fb5d19f9914>:0
  at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.GetAssembly (System.String fileName) [0x00007] in <93e3fd215cb8496582dc8fb5d19f9914>:0
  at Xamarin.Android.Tasks.ResolveLibraryProjectImports.Extract (Java.Interop.Tools.Cecil.DirectoryAssemblyResolver res, System.Collections.Generic.ICollection`1[T] jars, System.Collections.Generic.ICollection`1[T] resolvedResourceDirectories, System.Collections.Generic.ICollection`1[T] resolvedAssetDirectories, System.Collections.Generic.ICollection`1[T] resolvedEnvironments) [0x0024c] in <32f51031eaf74a37ae16fa6aad9819c9>:0
  at Xamarin.Android.Tasks.ResolveLibraryProjectImports.Execute () [0x000f0] in <32f51031eaf74a37ae16fa6aad9819c9>:0
  at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute () [0x00023] in <76dd0031e0df4aa99d9befb4c4585c69>:0
  at Microsoft.Build.BackEnd.TaskBuilder+<ExecuteInstantiatedTask>d__26.MoveNext () [0x0022d] in <76dd0031e0df4aa99d9befb4c4585c69>:0
[fail]: OmniSharp.MSBuild.ProjectFile.ProjectFileInfo
        Could not load assembly 'Widex.BOB, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?  at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference reference, Mono.Cecil.ReaderParameters parameters) [0x00124] in <93e3fd215cb8496582dc8fb5d19f9914>:0
  at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve (System.String fullName, Mono.Cecil.ReaderParameters parameters) [0x00007] in <93e3fd215cb8496582dc8fb5d19f9914>:0
  at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve (System.String fullName) [0x00000] in <93e3fd215cb8496582dc8fb5d19f9914>:0
  at Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.GetAssembly (System.String fileName) [0x00007] in <93e3fd215cb8496582dc8fb5d19f9914>:0
  at Xamarin.Android.Tasks.GetAdditionalResourcesFromAssemblies+<>c__DisplayClass36_0.<Execute>b__1 () [0x000df] in <32f51031eaf74a37ae16fa6aad9819c9>:0
  at System.Threading.Tasks.Task.InnerInvoke () [0x0000f] in <ac812cae460544af83bd6cf54c5eee87>:0
  at System.Threading.Tasks.Task.Execute () [0x00010] in <ac812cae460544af83bd6cf54c5eee87>:0
[warn]: OmniSharp.MSBuild.MSBuildProjectSystem
        Failed to load project file '/Users/bob/bitbucket/ourapps/bobapp/BOB.Droid/BOB.Droid.csproj'.
/Users/bob/bitbucket/ourapps/bobapp/BOB.Droid/BOB.Droid.csproj

[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: /Users/bob/bitbucket/ourapps/bobapp/BOB.iOS.Tests/BOB.iOS.Tests.csproj
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: /Users/bob/bitbucket/ourapps/bobapp/BOB.UnitTests/BOB.UnitTests.csproj
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: /Users/bob/bitbucket/ourapps/bobapp/BOB.SoundClassVisualization/BOB.SoundClassVisualization.csproj
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Update project: BOB
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Update project: BOB.iOS
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Update project: BOB.iOS.Tests
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Update project: BOB.UnitTests
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Update project: BOB.SoundClassVisualization
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/Users/bob/bitbucket/ourapps/bobapp'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.Stdio.Program
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.Stdio.Program
        Configuration finished.
[info]: OmniSharp.Stdio.Program
        Omnisharp server running using Stdio at location '/Users/bob/bitbucket/ourapps/bobapp' on host 54896.

Since the error is coming through Xamarin's Android task, do you need to build first or do anything special?

@DustinCampbell project is already built, and I don't know about any special command 😐

Does this assembly exist anywhere?

Could not load assembly 'Widex.BOB, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile?

Very much so :)
Exists under the shared code project, under ./bin/Release/Widex.BOB.dll

Hmmm... I wonder if the problem is that OmniSharp is simply defaulting to "Debug". Could you place the following omnisharp.json file in your repo root and see if anything changes?
{
    "MsBuild": {
        "Configuration": "Release"
    }
|

Is there any chance you could share the project? I'd love to get this under the debugger and see what's happening.

Wish I could, and I cannot recreate the issue :(

@casz: I assume that this issue is still reproducible for you with the latest version of C# for VS Code (1.13) that was released a couple of days ago?

@DustinCampbell  I reproduce this issue with C# extension 1.13.0.
Follow below step:
1.run "dotnet new console" to create a C# console project.
2.open "program.cs" ,then the issue will reproduce.
I think this issue is caused by 2 msbuild instances, but the C# plugin doesn't locate right one.
The OmniSharp Log:
Starting OmniSharp server at 2017-11-10 17:46:03
    Target: c:\Users\Administrator\Desktop\test

OmniSharp server started
    Path: C:\Users\Administrator\.vscode\extensions\ms-vscode.csharp-1.13.0\.omnisharp\OmniSharp.exe
    PID: 4236

[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 2 MSBuild instance(s)
            1: Visual Studio Professional 2017 15.4.27004.2008 - "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin"
            2: StandAlone 15.0 - "C:\Users\Administrator\.vscode\extensions\ms-vscode.csharp-1.13.0\.omnisharp\msbuild\15.0\Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: Visual Studio Professional 2017 15.4.27004.2008 - "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin"
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in 'c:\Users\Administrator\Desktop\test'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Initializing in c:\Users\Administrator\Desktop\test
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Auto package restore: False
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Update workspace context
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Resolving projects references
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        No solution files found in 'c:\Users\Administrator\Desktop\test'
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: c:\Users\Administrator\Desktop\test\test.csproj
[warn]: OmniSharp.MSBuild.MSBuildProjectSystem
        Failed to load project file 'c:\Users\Administrator\Desktop\test\test.csproj'.
c:\Users\Administrator\Desktop\test\test.csproj(1,1)
Microsoft.Build.Exceptions.InvalidProjectFileException: 找不到指定的 SDK“Microsoft.NET.Sdk”。  c:\Users\Administrator\Desktop\test\test.csproj
   在 Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args)
   在 Microsoft.Build.Evaluation.Evaluator`4.ExpandAndLoadImportsFromUnescapedImportExpressionConditioned(String directoryOfImportingFile, ProjectImportElement importElement, List`1& projects, Boolean throwOnFileNotExistsError)
   在 Microsoft.Build.Evaluation.Evaluator`4.ExpandAndLoadImports(String directoryOfImportingFile, ProjectImportElement importElement)
   在 Microsoft.Build.Evaluation.Evaluator`4.EvaluateImportElement(String directoryOfImportingFile, ProjectImportElement importElement)
   在 Microsoft.Build.Evaluation.Evaluator`4.PerformDepthFirstPass(ProjectRootElement currentProjectOrImport)
   在 Microsoft.Build.Evaluation.Evaluator`4.Evaluate(ILoggingService loggingService, BuildEventContext buildEventContext)
   在 Microsoft.Build.Evaluation.Project.Reevaluate(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings)
   在 Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary(ILoggingService loggingServiceForEvaluation, ProjectLoadSettings loadSettings)
   在 Microsoft.Build.Evaluation.Project.Initialize(IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectLoadSettings loadSettings)
   在 Microsoft.Build.Evaluation.Project..ctor(String projectFile, IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings)
   在 Microsoft.Build.Evaluation.ProjectCollection.LoadProject(String fileName, IDictionary`2 globalProperties, String toolsVersion)
   在 OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.LoadProject(String filePath, String solutionDirectory, ILogger logger, MSBuildInstance msbuildInstance, MSBuildOptions options, ICollection`1 diagnostics, ImmutableArray`1& targetFrameworks)
   在 OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.Create(String filePath, String solutionDirectory, ILogger logger, MSBuildInstance msbuildInstance, MSBuildOptions options, ICollection`1 diagnostics)
   在 OmniSharp.MSBuild.MSBuildProjectSystem.LoadProject(String projectFilePath)

[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in 'c:\Users\Administrator\Desktop\test'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.Stdio.Program
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.Stdio.Program
        Configuration finished.
[info]: OmniSharp.Stdio.Program
        Omnisharp server running using Stdio at location 'c:\Users\Administrator\Desktop\test' on host 2664.

I want to know how can i select the second msbuild instance(StandAlone 15.0 - "C:\Users\Administrator.vscode\extensions\ms-vscode.csharp-1.13.0.omnisharp\msbuild\15.0\Bin") ?

@DustinCampbell Additionally, i also have installed vs2017 and C# module.

@DFVSQY THANKY YOU for finding a way to reproduce 🚀

@casz : This is not the same as the original issue that you filed here. @DFVSQY : it looks like you're encountering in https://github.com/OmniSharp/omnisharp-vscode/issues/1849.

A lot has changed with O# project loading since this issue was opened. If this is still a problem, please open a new issue at  https://github.com/OmniSharp/omnisharp-roslyn


As a user, I want to take notes and have the time I took them saved, so that I can see my notes chronologically and understand my timeline

Completed with #90. Timestamps are optional, but this gives the user flexibility and this is the suggested behaviour


No dependency substitution happens for Version Catalogs included as separate build

When using composite build and including Version Catalogs plugin project, no dependency substitution happens.
Expected Behavior
Dependency specified with GAV should be substituted with included build.

Current Behavior
settings.gradle:
enableFeaturePreview("VERSION_CATALOGS")

includeBuild("version-catalog")

dependencyResolutionManagement {
    versionCatalogs {
        libs {
            from("foo.bar:version-catalog:1.0.0-SNAPSHOT")
        }
    }
}

version-catalog/build.gradle:
plugins {
    id "version-catalog"
    id "maven-publish"
}

version = "1.0.0-SNAPSHOT"
group = "foo.bar"

publishing {
    publications {
        versionCatalog(MavenPublication) {
            from components.versionCatalog
        }
    }
}

catalog {
    versionCatalog {
        version("kotlin", "1.5.31")
        alias("org.jetbrains.kotlin.plugin.serialization").toPluginId("org.jetbrains.kotlin.plugin.serialization").versionRef("kotlin")
    }
}

Following exception is thrown:
FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all artifacts for configuration 'incomingCatalogForLibs0'.
> Could not find foo.bar:version-catalog:1.0.0-SNAPSHOT.
  Searched in the following locations:
    - file:/C:/Users/xxx/.m2/repository/foo/bar/version-catalog/1.0.0-SNAPSHOT/maven-metadata.xml
    - file:/C:/Users/xxx/.m2/repository/foo/bar/version-catalog/1.0.0-SNAPSHOT/version-catalog-1.0.0-SNAPSHOT.pom
  Required by:
      unspecified:unspecified:unspecified

* Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Exception is:
org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all artifacts for configuration 'incomingCatalogForLibs0'.
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.rethrowFailure(DefaultConfiguration.java:1419)
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration.access$3600(DefaultConfiguration.java:152)
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$DefaultResolutionHost.rethrowFailure(DefaultConfiguration.java:2031)
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationArtifactCollection.lambda$new$0(DefaultConfiguration.java:1975)
	at org.gradle.internal.model.CalculatedValueContainerFactory$SupplierBackedCalculator.calculateValue(CalculatedValueContainerFactory.java:81)
	at org.gradle.internal.model.CalculatedValueContainer$CalculationState.lambda$attachValue$0(CalculatedValueContainer.java:218)
	at org.gradle.internal.Try.ofFailable(Try.java:41)
	at org.gradle.internal.model.CalculatedValueContainer$CalculationState.attachValue(CalculatedValueContainer.java:213)
	at org.gradle.internal.model.CalculatedValueContainer.finalizeIfNotAlready(CalculatedValueContainer.java:186)
	at org.gradle.internal.model.CalculatedValueContainer.finalizeIfNotAlready(CalculatedValueContainer.java:177)
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationArtifactCollection.ensureResolved(DefaultConfiguration.java:2011)
	at org.gradle.api.internal.artifacts.configurations.DefaultConfiguration$ConfigurationArtifactCollection.getArtifacts(DefaultConfiguration.java:1988)
	at org.gradle.api.internal.catalog.DefaultVersionCatalogBuilder.maybeImportCatalogs(DefaultVersionCatalogBuilder.java:170)
	at org.gradle.api.internal.catalog.DefaultVersionCatalogBuilder.doBuild(DefaultVersionCatalogBuilder.java:134)
	at org.gradle.internal.lazy.UnsafeLazy.ensureValue(UnsafeLazy.java:39)
	at org.gradle.internal.lazy.UnsafeLazy.get(UnsafeLazy.java:34)
	at org.gradle.api.internal.catalog.DefaultVersionCatalogBuilder.build(DefaultVersionCatalogBuilder.java:120)
	at org.gradle.api.internal.catalog.DefaultDependenciesAccessors.generateAccessors(DefaultDependenciesAccessors.java:123)
	at org.gradle.configuration.BuildTreePreparingProjectsPreparer.generateDependenciesAccessorsAndAssignPluginVersions(BuildTreePreparingProjectsPreparer.java:92)
	at org.gradle.configuration.BuildTreePreparingProjectsPreparer.prepareProjects(BuildTreePreparingProjectsPreparer.java:54)
	at org.gradle.configuration.BuildOperationFiringProjectsPreparer$ConfigureBuild.run(BuildOperationFiringProjectsPreparer.java:52)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:56)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$run$1(DefaultBuildOperationExecutor.java:74)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.runWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:45)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:74)
	at org.gradle.configuration.BuildOperationFiringProjectsPreparer.prepareProjects(BuildOperationFiringProjectsPreparer.java:40)
	at org.gradle.initialization.VintageBuildModelController.prepareProjects(VintageBuildModelController.java:97)
	at org.gradle.initialization.VintageBuildModelController.doBuildStages(VintageBuildModelController.java:77)
	at org.gradle.initialization.VintageBuildModelController.prepareToScheduleTasks(VintageBuildModelController.java:64)
	at org.gradle.internal.build.DefaultBuildLifecycleController.lambda$prepareToScheduleTasks$0(DefaultBuildLifecycleController.java:104)
	at org.gradle.internal.build.DefaultBuildLifecycleController.lambda$withModelOrThrow$5(DefaultBuildLifecycleController.java:142)
	at org.gradle.internal.build.DefaultBuildLifecycleController.withModel(DefaultBuildLifecycleController.java:157)
	at org.gradle.internal.build.DefaultBuildLifecycleController.withModelOrThrow(DefaultBuildLifecycleController.java:140)
	at org.gradle.internal.build.DefaultBuildLifecycleController.prepareToScheduleTasks(DefaultBuildLifecycleController.java:102)
	at org.gradle.internal.buildtree.DefaultBuildTreeWorkPreparer.scheduleRequestedTasks(DefaultBuildTreeWorkPreparer.java:33)
	at org.gradle.internal.buildtree.DefaultBuildTreeLifecycleController.lambda$doScheduleAndRunTasks$1(DefaultBuildTreeLifecycleController.java:83)
	at org.gradle.composite.internal.DefaultIncludedBuildTaskGraph.withNewTaskGraph(DefaultIncludedBuildTaskGraph.java:94)
	at org.gradle.internal.buildtree.DefaultBuildTreeLifecycleController.doScheduleAndRunTasks(DefaultBuildTreeLifecycleController.java:82)
	at org.gradle.internal.buildtree.DefaultBuildTreeLifecycleController.lambda$fromBuildModel$0(DefaultBuildTreeLifecycleController.java:71)
	at org.gradle.internal.buildtree.DefaultBuildTreeLifecycleController.runBuild(DefaultBuildTreeLifecycleController.java:104)
	at org.gradle.internal.buildtree.DefaultBuildTreeLifecycleController.fromBuildModel(DefaultBuildTreeLifecycleController.java:69)
	at org.gradle.tooling.internal.provider.runner.AbstractClientProvidedBuildActionRunner.runClientAction(AbstractClientProvidedBuildActionRunner.java:56)
	at org.gradle.tooling.internal.provider.runner.ClientProvidedPhasedActionRunner.run(ClientProvidedPhasedActionRunner.java:53)
	at org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
	at org.gradle.internal.buildtree.ProblemReportingBuildActionRunner.run(ProblemReportingBuildActionRunner.java:47)
	at org.gradle.launcher.exec.BuildOutcomeReportingBuildActionRunner.run(BuildOutcomeReportingBuildActionRunner.java:69)
	at org.gradle.tooling.internal.provider.FileSystemWatchingBuildActionRunner.run(FileSystemWatchingBuildActionRunner.java:91)
	at org.gradle.launcher.exec.BuildCompletionNotifyingBuildActionRunner.run(BuildCompletionNotifyingBuildActionRunner.java:41)
	at org.gradle.launcher.exec.RootBuildLifecycleBuildActionExecutor.lambda$execute$0(RootBuildLifecycleBuildActionExecutor.java:40)
	at org.gradle.composite.internal.DefaultRootBuildState.run(DefaultRootBuildState.java:154)
	at org.gradle.launcher.exec.RootBuildLifecycleBuildActionExecutor.execute(RootBuildLifecycleBuildActionExecutor.java:40)
	at org.gradle.internal.buildtree.DefaultBuildTreeContext.execute(DefaultBuildTreeContext.java:40)
	at org.gradle.launcher.exec.BuildTreeLifecycleBuildActionExecutor.lambda$execute$0(BuildTreeLifecycleBuildActionExecutor.java:56)
	at org.gradle.internal.buildtree.BuildTreeState.run(BuildTreeState.java:53)
	at org.gradle.launcher.exec.BuildTreeLifecycleBuildActionExecutor.execute(BuildTreeLifecycleBuildActionExecutor.java:56)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionExecutor$3.call(RunAsBuildOperationBuildActionExecutor.java:61)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionExecutor$3.call(RunAsBuildOperationBuildActionExecutor.java:57)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:200)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:195)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:75)
	at org.gradle.internal.operations.DefaultBuildOperationRunner$3.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:153)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:68)
	at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:62)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.lambda$call$2(DefaultBuildOperationExecutor.java:79)
	at org.gradle.internal.operations.UnmanagedBuildOperationWrapper.callWithUnmanagedSupport(UnmanagedBuildOperationWrapper.java:54)
	at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:79)
	at org.gradle.launcher.exec.RunAsBuildOperationBuildActionExecutor.execute(RunAsBuildOperationBuildActionExecutor.java:57)
	at org.gradle.launcher.exec.RunAsWorkerThreadBuildActionExecutor.lambda$execute$0(RunAsWorkerThreadBuildActionExecutor.java:38)
	at org.gradle.internal.work.DefaultWorkerLeaseService.withLocks(DefaultWorkerLeaseService.java:211)
	at org.gradle.launcher.exec.RunAsWorkerThreadBuildActionExecutor.execute(RunAsWorkerThreadBuildActionExecutor.java:38)
	at org.gradle.tooling.internal.provider.ContinuousBuildActionExecutor.execute(ContinuousBuildActionExecutor.java:103)
	at org.gradle.tooling.internal.provider.SubscribableBuildActionExecutor.execute(SubscribableBuildActionExecutor.java:64)
	at org.gradle.internal.session.DefaultBuildSessionContext.execute(DefaultBuildSessionContext.java:46)
	at org.gradle.tooling.internal.provider.BuildSessionLifecycleBuildActionExecuter.lambda$execute$0(BuildSessionLifecycleBuildActionExecuter.java:56)
	at org.gradle.internal.session.BuildSessionState.run(BuildSessionState.java:69)
	at org.gradle.tooling.internal.provider.BuildSessionLifecycleBuildActionExecuter.execute(BuildSessionLifecycleBuildActionExecuter.java:55)
	at org.gradle.tooling.internal.provider.BuildSessionLifecycleBuildActionExecuter.execute(BuildSessionLifecycleBuildActionExecuter.java:37)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:36)
	at org.gradle.tooling.internal.provider.GradleThreadBuildActionExecuter.execute(GradleThreadBuildActionExecuter.java:25)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:63)
	at org.gradle.tooling.internal.provider.StartParamsValidatingActionExecuter.execute(StartParamsValidatingActionExecuter.java:31)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:58)
	at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:42)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:47)
	at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:31)
	at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:65)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:39)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:29)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:35)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:78)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.create(ForwardClientInput.java:75)
	at org.gradle.util.internal.Swapper.swap(Swapper.java:38)
	at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:75)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:63)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:84)
	at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:37)
	at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:104)
	at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:52)
	at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:297)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
	at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:61)
Caused by: org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find foo.bar:version-catalog:1.0.0-SNAPSHOT.
Searched in the following locations:
  - file:/C:/Users/xxx/.m2/repository/foo/bar/version-catalog/1.0.0-SNAPSHOT/maven-metadata.xml
  - file:/C:/Users/xxx/.m2/repository/foo/bar/version-catalog/1.0.0-SNAPSHOT/version-catalog-1.0.0-SNAPSHOT.pom
    unspecified:unspecified:unspecified

* Get more help at https://help.gradle.org

BUILD FAILED in 482ms

Context
We have multiple SCM repositories within our department. core for shared libraries and impl ones which depends on core.
Within the core library we want to have a version-catalog plugin which can be used within core repo itself (as an included build) and within impl repositories (with composition builds enabled/disabled).
Your Environment
Gradle 7.2.

Is there any workaround I can try?

This isn't a bug but a consequence of the design. The project you want to import is in the same build. This means that itself, would have access to the catalog defined in settings. Therefore, it cannot participate in the definition of the catalog.
The workaround is easy: instead of using a project to declare your catalog, make it a distinct build and include it.

Thanks for the information.
I have tried your suggestion, but it didn't work for me. Or I do not know how to apply it:
settings.gradle:
includeBuild("plugin-version-catalog")

dependencyResolutionManagement {
    versionCatalogs {
        libs {
            from("_g_:plugin-version-catalog:_v_")
        }
    }
}

And I got this error:
Could not resolve all artifacts for configuration 'incomingCatalogForLibs0'.
> Could not find g:a:v.
  Searched in the following locations:
...
Possible solution:
 - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

So no dependency substitution happened. Am I missing something?

mmm, no you're correct, I thought the substitution would automatically apply but it's not the case.

So should I close this very issue and create new one describing the substitution problem with composite build?

I would appreciate it if you could simply edit this one to describe the correct issue with included builds, I was planning to have this same discussion and use this ticket if that bug existed.

The ticket is updated. Thank you for your help.

@little-fish i got mine working. when you have multiple included builds, the order in the settings.gradle.kts does matter.

A similar (but probably different) issue occurs for a dependency defined inside a catalog, where the dependency's project is then included as a composite build:
[libraries]
my-lib = "group:my-lib:1.0.0"

api(libs.my.lib)

./gradlew assemble --include-build ../my-lib/

The expectation is that we will substitute the included ../my-lib composite build, for the catalog-defined libs.my.lib. But that does not happen. Instead we get the same error, "Could not find group:my-lib:1.0.0", despite the composite build.

Facing the same issue.. Im using gradle 7.2. Any workaround for this?

@big-guy i see milestone for this is 8.0 RC1/ 8.1 RC1 which is way long. Is there any work around for now in 7.2 or above versions?

After hours on this, I managed to make it work by renaming the published catalog artifact from version-catalog to versioncatalog:
Producer:
publishing {
    publications {
        register<MavenPublication>("catalog") {
            from(components["versionCatalog"])
            group = "com.org"
            artifactId = "versioncatalog"
            version = "1.0"
        }
    }

    repositories { ... }
}

Consumer:
dependencyResolutionManagement {
    repositories { .. }
    versionCatalogs {
        create("libs").from("com.org:versioncatalog:1.0")

        // fails with "Could not resolve all artifacts for configuration 'incomingCatalogForLibs0'."
        // create("libs").from("com.org:version-catalog:1.0")
    }

After hours on this, I managed to make it work by renaming the published catalog artifact from version-catalog to versioncatalog:
Producer:
//build.gradle.kts
publishing {
    publications {
        register<MavenPublication>("catalog") {
            from(components["versionCatalog"])
            group = "com.org"
            artifactId = "versioncatalog"
            version = "1.0"
        }
    }

    repositories { ... }
}

Consumer:
//settings.gradle.kts
dependencyResolutionManagement {
    repositories { .. }
    versionCatalogs {
        create("libs").from("com.org:versioncatalog:1.0")

        // fails with "Could not resolve all artifacts for configuration 'incomingCatalogForLibs0'."
        // create("libs").from("com.org:version-catalog:1.0")
    }

More context

The artefactId was declared as version-catalog for weeks and still works on some colleagues' machines (tested on the same branch)
It stopped working for me when I published a new version to maven local. I changed the version to my local catalog, and once I tried to add the previous back, I got the error.
I manually deleted all catalogs from our maven registry (yolo), and published a new one using the changes, still same error.
I tried deleted .m2 (maven local) folder and .gradle/caches
✅ Publishing to maven local works with version-catalog as artefactId

Tried with 8.0 RC2 but problem remain. Using includeBuild '' does not substitute the one pointed out from settings.gradle
dependencyResolutionManagement {
externalLibs {
from("g..v")
}
}
}

Any news on this one?
I'm using the Setting API to generate the catalog:
class SciJavaCatalogPlugin : Plugin<Settings> {

    override fun apply(settings: Settings) {

        settings.dependencyResolutionManagement.versionCatalogs.addGeneratedCatalog() // this is generated
    }
}

but still no dependency substitution takes place..

Same with 8.4

I know its not the best solution, but works as a workaround, temporary!
You can directly point to your toml file from your version catalog project for a composite build.
Like so:
  versionCatalogs {
    libs {
      from(files("pathToVersionCatalogRepo/libs.versions.toml"))
    }
  }

still facing issue with gradle version-8.5

I see why it is happening. In module file the versionCatalogElements variant is missing.
"variants": [     {       "name": "versionCatalogElements",       "attributes": {         "org.gradle.category": "platform",         "org.gradle.usage": "version-catalog"       },       "files": [         {           "name": "gradle-version-catalog-0.1.1-SNAPSHOT.toml",           "url": "gradle-version-catalog-0.1.1-SNAPSHOT.toml",           "size": 18559,           "sha512": "xxxxx",           "sha256": "xxxxxxx",           "sha1": "xxxxxxxxxxxxx",           "md5": "xxxxxxxxxxxxxxx"         }       ]     }   ]
If in module file this is present when it will work.
Most of the time when i publish i see apiElements and runtimeElements variants not versionCatalogElements.
Not use which publish configuration make this possible to add versionCatalogElements variants

You probably publish the java component instead of the versionCatalog component.

You probably publish the java component instead of the versionCatalog component.

I tried with java it is same. With java the mavenPublishLocal is setting variant as apiElements and runtimeElements
expected is versionCatalogElements variant
I think the issue is with Jfrog publish which ignores the versionCatalog which holds versionCatalogElements  and publishs only publishMaven which holds apiElements and runtimeElements
Created a issue:
https://github.com/jfrog/artifactory-gradle-plugin/issues/113
Not sure it is gradle issue or jfrog plugin issue.

I tried with java it is same. With java the mavenPublishLocal is setting variant as apiElements and runtimeElements
expected is versionCatalogElements variant.

Sure, you did the opposite of what I said.

I think the issue is with Jfrog publish

Quite possible, I often heard of strange things in their plugin.
Afaik, you can just use maven-publish and do not use their plugin.

I tried with java it is same. With java the mavenPublishLocal is setting variant as apiElements and runtimeElements
expected is versionCatalogElements variant.

Sure, you did the opposite of what I said.

I think the issue is with Jfrog publish

Quite possible, I often heard of strange things in their plugin. Afaik, you can just use maven-publish and do not use their plugin.

Do you have any sample how can we use maven-publish to publish the artifacts in Jfrog artifactory.

Nope, sorry, never used Artifactory, but I know that multiple people were pretty happy to just use maven-publish and get rid of the JFrog plugin. But if you have further questions to that, I suggest you ask somewhere else like the Forums, Slack, or StackOverflow, as it slightly gets a bit off-topic here. :-)

This issue is still happening with Gradle 8.7. In my particular case the versionCatalogElements look correct:
  "variants": [
    {
      "name": "versionCatalogElements",
      "attributes": {
        "org.gradle.category": "platform",
        "org.gradle.usage": "version-catalog"
      },
      "files": [
        {
          "name": "abc-1.0.toml",
          "url": "abc-1.0.toml",
          "size": 355,
          "sha512": "44fff65d061c73135f5c8ca2c9c6c317dffbaa2a3d1f4451a8f0fb63da89ed02a7d8a29206bbe86575385c3f8c53470bbf91f1d9180f39d792590027d8a44ab0",
          "sha256": "b8234795c2a50e7a48c1dbf6243677f7b007f8178755c74ebed9e711b926bca4",
          "sha1": "5cb09fcb43dffc9bce0300c64087d4327feb59b9",
          "md5": "04f7cbf418055d2e78b94db18070fe9b"
        }
      ]
    }
  ]

The catalog is published like this:
apply plugin: 'version-catalog'
apply plugin: 'maven-publish'

catalog {
    versionCatalog {
        from files('../gradle/libs.versions.toml')
    }
}

publishing {
    publications {
        maven(MavenPublication) {
            from components.versionCatalog
        }
    }
}

Testing the same going through maven local works fine.

I have the same problem. I am using version-catalog in a separate project which is then deployed to Github Packages, but for development/testing I want to include it in the main app project using includeBuild.
version-catalog module in a VersionCatalog directory which has its' own settings.gradle:
group = "my.group"
version = project.findProperty("version") ?: "0.0.0"

catalog {
    versionCatalog {
        from(files("../gradle/libs.versions.toml"))
    }
}

publishing {
    val artifactId = "version-catalog"

    publications {
        create<MavenPublication>("libs") {
            from(components["versionCatalog"])

Then I'm trying to include it in the main app settings.gradle file:
includeBuild("../VersionCatalog")

...

dependencyResolutionManagement {
    versionCatalogs {
        val externalLibs by creating {
            from("my.group:version-catalog:1.0.0")
        }

I can see that the project has been added and I can browse it using IDE, but changes to version-catalog in VersionCatalog directory doesn't seem to override remotely deployed version catalog.
Should it work this way or there is some issue with this configuration?

I am affected by this bug. I used to be able to sidestep this issue by declaring a bogus substitution, like:
includeBuild("catalog-build") {
  dependencySubstitution {
    substitute(module("com.package:whatever")).using(project(":"))
  }
}

dependencyResolutionManagement {
  versionCatalogs {
    create("libs") {
      from("com.package:whatever")
    }
  }
}

But this stopped working on 8.10


Pangram Checker Game added

PR Description 📜
Game added sucessfully.
Fixes #4563

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[x] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Damini2004 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@ishita-43  My pr doesnt contain game folder, assests,main readme ?

You should add your game image into asset folder of the repo  and also add your game entry into main readme.md file of the repo

and your pr is showing 576+ files which is impossible forme to see errors instead you should add only your game folder and make pr on that after forking the repo and locally cloning that into your environment

@ishita-43 idk but this repo having several problem while creating pr.

@ishita-43 idk but this repo having several problem while creating pr.

did you cloned the repo after forking on your local system

@ishita-43 idk but this repo having several problem while creating pr.

would you be able to make new pr request following the steps bellow - https://github.com/GSSoC24/Contributor


Remove /lgtm munger.

Should go in around the same time as https://github.com/kubernetes/test-infra/pull/985.

This change is

You have no idea how happy I am to see this gone

/lgtm

Looks like this change doesn't compile.

k8s.io/contrib/mungegithub/mungers
mungers/approval-handler.go:86: undefined: getCommentsAfterLastModified
godep: go exit status 2

Yeah, I've noticed. Still lgtm once it does (it removes a function used
somewhere else in the package)
On Thu, Nov 3, 2016, 2:40 PM Anirudh Ramanathan<EMAIL_ADDRESS>wrote:

Looks like this change doesn't compile.
k8s.io/contrib/mungegithub/mungers
mungers/approval-handler.go:86: undefined: getCommentsAfterLastModified
godep: go exit status 2
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/contrib/pull/1987#issuecomment-258282515,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB1xrDBf2s4d2j-idZhboVeQHOkr9PQDks5q6lTdgaJpZM4Ko7p7
.

Still good, if not better :-)

prow should go first. Both at the same time should still work.

and then let's run a test PR before merging this?

/lgtm cancel

/lgtm

:)

That's awesome :)

@apelisse let's see you try :)

https://github.com/kubernetes/kubernetes/pull/34864#issuecomment-258288047

/lgtm

(once we're gating on approval rather than lgtm we can get rid of that check)

/lgtm


stderr from build script still does not get saved anywhere

Consider this build script:
use std::io::Write;
fn main(){
    write!(::std::io::stderr(), "boom").unwrap();
    write!(::std::io::stdout(), "woaw").unwrap();
}

the stdout output gets saved into output file, but stderr is dropped. Would be nice if the stderr was also saved in this manner.

Sounds reasonable to me!


Allow for arrays of data (to create photosets)

Overlaps https://github.com/tumblr/tumblr.js/pull/23

cool - thanks @KevinTCoughlin


parse_user_agent matches all strings

The regex ^(?P<name>[^/ ]*[^0-9/(]*)(/(?P<version>[^/ ]*))?([ /].*)?$ matches the empty string with name; and since version is optional (but can include linebreaks) and the last group catches everything but linebreaks, there is always a match at lib/user_agent.py line 8.
This means that match is never None so:

Test coverage can't be 100% for lib/user_agent.py
The TestUserAgentParsing test is futile (since it will trivially pass as parse_user_agent is never None)
Other places where some user_agent is None test is carried out (e.g. 1, 2), the else clause cannot be reached and therefore coverage can never be 100%.

Also, nowhere currently uses user_agent['version'].
I think the only option for fixing this bug it to use stricter RegEx (making the version required, or preventing name matching with the empty string). Changing the guard conditions from match is None can always be done by changing the RegEx pattern, which is cleaner.
I'll happily update this, just need some advice on what we actually want to match!

I think we can probably just replace the conditional with an assert match is not None.  The intent is more to split a string, and I bet the if user_agent is None was just there so that future code can assume it was something.

Sounds good. Should we remove the branches where it's assumed user_agent = None?
I assume we'd also change TestUserAgentParsing so that all we're doing is running through the testcases.

@zulipbot claim

Yeah, that makes sense to me.


Failed to Analyze spark 1.6 history application

We compiled dr-elephant (customSHSWork branch), and deployed it on our hadoop yarn cluster for test, we tried both REST api SparkFetcher and spark.fetchers.FSFetcher and failed to load recent jobs (mapreduce jobs can be successfully loaded). Look forward to any tips. Thanks!
here is the log:
04-11-2018 15:47:09 INFO  [ForkJoinPool-3-worker-57] com.linkedin.drelephant.spark.fetchers.SparkRestClient : creating SparkApplication by calling REST API at http://myhost:23764/api/v1/applications/application_1521785315204_12497/logs to get eventlogs
04-11-2018 15:47:09 INFO  [dr-el-executor-thread-0] com.linkedin.drelephant.spark.fetchers.SparkFetcher : Succeeded fetching data for application_1521785315204_12497
**04-11-2018 15:47:09 ERROR [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : None.get
04-11-2018 15:47:09 ERROR [dr-el-executor-thread-0] com.linkedin.drelephant.ElephantRunner : java.util.NoSuchElementException: None.get
	at scala.None$.get(Option.scala:313)
	at scala.None$.get(Option.scala:311)
	at** com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic$Evaluator$$anonfun$getErrorsSeverity$1.apply(StagesWithFailedTasksHeuristic.scala:83)
	at com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic$Evaluator$$anonfun$getErrorsSeverity$1.apply(StagesWithFailedTasksHeuristic.scala:79)
	at scala.collection.immutable.List.foreach(List.scala:318)
	at com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic$Evaluator.getErrorsSeverity(StagesWithFailedTasksHeuristic.scala:79)
	at com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic$Evaluator.x$1$lzycompute(StagesWithFailedTasksHeuristic.scala:143)
	at com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic$Evaluator.x$1(StagesWithFailedTasksHeuristic.scala:143)
	at com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic$Evaluator.stagesWithOOMError$lzycompute(StagesWithFailedTasksHeuristic.scala:143)
	at com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic$Evaluator.stagesWithOOMError(StagesWithFailedTasksHeuristic.scala:143)
	at com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic.apply(StagesWithFailedTasksHeuristic.scala:42)
	at com.linkedin.drelephant.spark.heuristics.StagesWithFailedTasksHeuristic.apply(StagesWithFailedTasksHeuristic.scala:31)
	at com.linkedin.drelephant.analysis.AnalyticJob.getAnalysis(AnalyticJob.java:265)
	at com.linkedin.drelephant.ElephantRunner$ExecutorJob.run(ElephantRunner.java:175)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)

looks like spark 1.6 history server cannot support StagesWithFailedTasksHeuristic, we remove this config in HeuristicConf.xml and FetcherConf.xml, then spark job is analyzed normally and shows on web ui

looks like spark 1.6 history server cannot support StagesWithFailedTasksHeuristic, we remove this config in HeuristicConf.xml and FetcherConf.xml, then spark jobs are analyzed normally and show on web ui.

looks like spark 1.6 history server cannot support StagesWithFailedTasksHeuristic, we remove this configuration in HeuristicConf.xml and FetcherConf.xml, then spark jobs are analyzed normally and show on web ui.


set up regression test for uncached/cached interaction with manycore bridge

@tommydcjung Should this be closed? There is a testbench that looks like this, but I don't know its status

Closed because we're not supporting the manycore bridge at the moment


Statamic 5 Support

Thank you for the contribution! I've gone over the upgrade guide and saw that there are some changes to the testing setup. If you don't mind, I'd like to take the opportunity to go over updating that, as well as the CI/CD setup.

Resolved via #7

@stefangalescu Thanks! Something I am going through while installing the latest release. Just thought I should let you know.
  Error

  Interface "Facade\IgnitionContracts\ProvidesSolution" not found

  at vendor/stefangalescu/statamic-heroicons/src/Exceptions/IncorrectEngineException.php:10
      6▕ use Facade\IgnitionContracts\ProvidesSolution;
      7▕ use Facade\IgnitionContracts\Solution;
      8▕ use StefanGalescu\Heroicons\Exceptions\Solutions\IncorrectEngineSolution;
      9▕
  ➜  10▕ class IncorrectEngineException extends Exception implements ProvidesSolution
     11▕ {
     12▕     protected $message;
     13▕
     14▕     public function __construct()

      +13 vendor frames

  14  artisan:13
      Illuminate\Foundation\Application::handleCommand(Object(Symfony\Component\Console\Input\ArgvInput))

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1


How to determine if device supports getMediaSources/aka live stream?

Is there a way to detect if a device supports the live stream method? I would like to be able to detect this so that I can prove the static image functionality to those clients.

From here: http://stackoverflow.com/questions/12885896/getusermedia-how-to-detect-if-the-device-actually-has-a-camera
...it's suggested...

You can use MediaStreamTrack.getSources. This returns a list of video and audio devices connected to the PC. This does not require user permission.
You can then pass the ID to getUserMedia to get the desired media device.

I haven't tried it myself. Hope that helps.

QuaggaJS has a hard dependency on webrtc-adapter and by using some kind of feature detection you could then decide which method to use:
if (navigator.mediaDevices && typeof navigator.mediaDevices.getUserMedia === 'function') {
  // safely access `navigator.mediaDevices.getUserMedia`
}

After a quick check, the aforementioned condition returns:

Microsoft Edge: true
Chrome: true
Firefox: true
IE 11: false

Please close this issue if you got it working for you


warning for those editing pkg/client

I've seen people edit pkg/client and become confused by why there changes disappear, or don't show up or this or that on the CI.
#417 is merely the most recent manifestation.
I wanted something a bit more catchy than README, so that's my explanation for the file name.

let's twiddle the generated files names (to have a 'zz' or something like that in them). People won't notice a warning file - at least I wouldn't have.

For informer-gen & lister-gen the only knob we have is adjusting the --output-packageflag.
If clients are in clientset_generated, then perhaps the informers and listers should be in a similarly named directory?

Or we could move everything into some kind of pkg/generated

I would really like that but I was wondering what that would mean for people trying to import our generated code - which I think is the main usecase for checking in this stuff.

LGTM
One thing we do to handle this type of concern in upstream is have a 'verify' script that regenerates all the code and verifies that there are no changes relative to what's in the tree.  We need that here.

I think this is a good start. I'd like to see other suggestions discussed and possibly implemented in follow ups.
I am merging this.


[Issue]: AutoGen Studio  | Error with Azure OpenAI key

Describe the issue
Hi team many thanks for your Azure setting suggestions.
I have followed @victordibia suggestions and set all Azure setings for both "User Proxy" and "Primary" agents . Also removed all models from the list and just set this Azure model created. If I try wih OpenAI everything runs fine. I have set the code "export AZURE_OPENAI_API_KEY=zzzzzzzz" previous to launching AutoGen Studio.
As soon as I try sending the mesage "Hello" in a new PlayGround session, Im getting this error. AttributeError: 'NoneType' object has no attribute 'model_dump'.
Maybe Im missing something? Thanks in advance.
az_userproxy (to az_primary_assistant):

hello

--------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogenstudio/web/app.py", line 68, in add_message
    response_message: Message = chatmanager.chat(
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogenstudio/chatmanager.py", line 29, in chat
    flow.run(message=f"{message_text}", clear_history=False)
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogenstudio/workflowmanager.py", line 196, in run
    self.sender.initiate_chat(
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogen/agentchat/conversable_agent.py", line 621, in initiate_chat
    self.send(self.generate_init_message(**context), recipient, silent=silent)
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogen/agentchat/conversable_agent.py", line 398, in send
    recipient.receive(message, self, request_reply, silent)
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogen/agentchat/conversable_agent.py", line 551, in receive
    reply = self.generate_reply(messages=self.chat_messages[sender], sender=sender)
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogen/agentchat/conversable_agent.py", line 1193, in generate_reply
    final, reply = reply_func(self, messages=messages, sender=sender, config=reply_func_tuple["config"])
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogen/agentchat/conversable_agent.py", line 716, in generate_oai_reply
    extracted_response = model_dump(extracted_response)
  File "/home/xxxx/.local/lib/python3.10/site-packages/autogen/_pydantic.py", line 37, in model_dump
    return model.model_dump()
AttributeError: '**NoneType**' object has no attribute '**model_dump**'

Steps to reproduce
No response
Screenshots and logs
No response
Additional Information
No response

It looks like the Azure OpenAI returns a None value in the response message. Can you post your pyautogen version, openai version. Thanks!
@yenif @maxim-saplin @sonichi for awareness

@iokinpardo ,
Can you confirm if you are able to use your Azure endpoint from python with AutoGen?
This way we can triangulate if the issue is with your credentials, autogen or the autogenstudio implementation.

JIC, I also tried using Autigen Studio running it locally from sources (it was quite a challenge). I added Azure models to both clients and one of the workflows (General Agent Workflow) and I am getting Error code: 404 - {'error': {'code': '404', 'message': 'Resource not found'}}.
Happy to diagnose the issue yet I am out of my reverse engineering capacity today :) Can someone point at a complete instruction explaining how to run and debug the solution?
P.S.: here's my draft of my steps that made the UI open:
cd samples/apps/autogen-studio/frontend
npm install -g gatsby-cli
npm install -g yarn
yarn install yarn build
cd ..
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
python -m autogenstudio.cli ui --port 8081

There was also an error of scratch folder non existing, had to manually open user/{GUID} and make directory there

Thanks @victordibia .
How can I check AutoGen case with my Azure Keys? Btm I have just beeing runing with AG Studio, so don't know very much how to launch "Autogen Engine". Is it already installed with AG Studio or should I install it? What are the steps to follow to cofirm the correct performance with Azure keys?
Thanks in advance.

Thanks @victordibia .
Finally I have been able to update the latest AutoGen Studio version where Models are configured individually and I have been able to set Azure based ones properly. Many thanks.
Now I have couple of doubts:

Is it possible for Agents to set "Max Consecutive Auto Reply" to 1 as this could let us run more eficiently during testing process? And in cases where Agents are able to answer accurately in 1 unique step too.

Which configuration prevails? The ones set under Workflows for internal Agents? Or the ones configured on Agents, and then being used on Workflows? Because it seems that we can have some configurations predefined for Agents, but just will be used the ones set on Agents inside Workflows, right?

@ekzhu .. I just had a session where we encounted the same None Type error with AOAI models.
Some inputs were fine, others had the issue. Specifically, when the input is "hello" in a two agent setup, we see that error.


./get-libsnark fails

./get-libsnark terminates with:
make: *** No rule to make target 'clean'.  Stop.
Could it be libsnark's Transition to CMake?

The latest version of libsnark is no longer compatible. Add
git checkout deprecated-master

in the get-libsnark file to specify the specific version of libsnark.

It still doesn't work, and I continuelly got the same errors.

It still doesn't work, and I continually got the same errors.


Configure props of type PlainSearchParameters instead of SearchParameters (react-instantsearch)

🐛 Current behavior
In version 7.12.2 or react-instantsearch, I get this TypeError when adding a Configure component to my app :
Type '{ hitsPerPage: number; insideBoundingBox: string; }' is not assignable to type 'IntrinsicAttributes & PlainSearchParameters'.
In connectors/configure/connectConfigure.d.ts, you have :
export type ConfigureConnectorParams = {
    /**
     * A list of [search parameters](https://www.algolia.com/doc/api-reference/search-api-parameters/)
     * to enable when the widget mounts.
     */
    searchParameters: PlainSearchParameters; // <--- shouldn't this be SearchParameters ?
};

🔍 Steps to reproduce

Open the react Instant Search CodeSandBox template, then install dependencies
Go to the Configure component in App.tsx
Notice that hitsPerPage doesn't appear in autocomplete

Live reproduction
https://codesandbox.io/p/sandbox/github/algolia/instantsearch/tree/templates/react-instantsearch
💭 Expected behavior
Configure props should work as advertised in the documentation : https://www.algolia.com/doc/api-reference/widgets/configure/react/#props
Package version
react-instantsearch 7.12.2
Operating system
any
Browser
all
Code of Conduct

[X] I agree to follow this project's Code of Conduct

The sandbox you linked shows that configure is working fine (no typescript error). I recognise this behaviour from a previously fixed bug (see #5658), but that's merged and released. I wonder if you somehow ended up with a stale dependency of algoliasearch-helper somewhere? Can you reproduce this in a blank example?

You are correct. My mistake, I must have had a stale dependency somewhere.

Glad you have a solution!


graphql-relay

Looks like you removed graphql-relay as a dependency.  I see that graphql/types/user.js still references it though:
import {
  GraphQLObjectType,
  GraphQLString,
} from 'graphql';
import {
  globalIdField,
} from 'graphql-relay';

I end up with the following error:

[nodemon] 1.11.0
[nodemon] to restart at any time, enter rs
[nodemon] watching: .
[nodemon] starting babel-node ./foundation/devServer
module.js:471
throw err;
^
Error: Cannot find module 'graphql-relay'

Is the plan to completely remove all use of relay?

I'm stuck dead in the water. Here's what I've done...

cloned the repo
$ yarn
$ npm start

And I get this output...
api/config.js file was generated
[nodemon] 1.11.0
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `babel-node ./foundation/devServer`
module.js:471
    throw err;
    ^

Error: Cannot find module 'graphql-relay'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/dev/serverless-graphql-apollo/graphql/types/user.js:7:1)
    at Module._compile (module.js:570:32)
    at loader (/dev/serverless-graphql-apollo/node_modules/babel-register/lib/node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .js] (/dev/serverless-graphql-apollo/node_modules/babel-register/lib/node.js:154:7)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
[nodemon] app crashed - waiting for file changes before starting..

It doesn't look it is on the master branch yet.  The develop branch has the fix.  You can probably just paste the update from https://github.com/andykenward/serverless-graphql-apollo/commit/ca3cbc5c1ffc06519982ed3902a010020259af7d too.

Worked perfectly, thanks @marc-at!

You can also just yarn add graphql-relay

just removed it in a cleanup PR https://github.com/serverless/serverless-graphql-apollo/pull/95


Support multiple accounts?

Does this workflow support multiple accounts? (And if not, can it be implemented?)

It doesn't support multiple accounts at the moment, and yes, it would be possible to implement it. But I'm afraid I don't have time to work on it anytime soon. Pull requests are more than welcome!


There might be a wording error on this page

[Enter feedback here]
If no background constant is specified, the background is black, and if no foreground constant is specified, the text is black. For example, the following combination produces black text on a white background.
should it be
If no background constant is specified, the background is black, and if no foreground constant is specified, the text is white. For example, the following combination produces black text on a white background.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 46f0eb74-9b09-16ab-5894-af4d96361bac
Version Independent ID: 8eb4eea7-dd66-2bc8-9052-7de8495f26f1
Content: Console Screen Buffers - Windows Console
Content Source: docs/console-screen-buffers.md
Product: console
GitHub Login: @bitcrazed
Microsoft Alias: richturn

I believe that if no foreground constant is specified, the foreground is black (no foreground constant = 0x0 in the low nybble of the attribute byte = color 0)
Do you have an application that reproduces "no foreground = white"?


Similarity kernel implementation?

Hi all!
I am reading https://doi.org/10.1039/C6CP00415F and I would like to use a global similarity kernel, as defined in Equation 18, which basically gives information about mixed-species components:

Is this feature available in dscribe? Or perhaps could you show me the corresponding source code to be modified? In the end it's just about adding a customised function that lives between 0 and 1. For instance;

Many thanks in advance.
Best,
Alejandro

Hi @alejandroarche!
The SOAP output from dscribe contains all of the information needed for the vector $\vec{p}$ in that equation you shared, as explained in the documentation.
In that same documentation page, you can see how the output vector is ordered, and you can also get a part belonging to a specific $\alpha$, $\beta$ species pair with SOAP.get_.location(alpha, beta).
So if I understood the alchemical kernel correctly, you should be able to build it from the dscribe SOAP output. It would look something like this:
import numpy as np
from dscribe.descriptors import SOAP
from ase.build import molecule
from ase import Atoms

# Setup two systems that have completely different species.
system_1 = Atoms(symbols=['H'], positions=[[0,0,0]])
system_2 = Atoms(symbols=['O'], positions=[[0,0,0]])

# Set up the SOAP descriptor
species = ['H', 'O']
soap = SOAP(
    species=species,
    periodic=False,
    r_cut=2,
    sigma=0.5,
    n_max=6,
    l_max=6,
)

# Create power spectrums. A "normal" kernel would see these two SOAP vectors as
# completely different as they dont share any species.
p_1 = soap.create(system_1, centers=[0])
p_2 = soap.create(system_2, centers=[0])

# Define dummy "alchemical" kernel
kernel = {
    ("H", "H"): 1,
    ("H", "O"): 1,
    ("O", "H"): 1,
    ("O", "O"): 1,
}

# Calculate similarity between p_1 and p_2: our dummy kernel says that H and O
# are chemically identical, so the similarity will be very big (note that the
# kernel is not normalized).
similarity = 0
for alpha_1 in species:
    for beta_1 in species:
        for alpha_2 in species:
            for beta_2 in species:
                # TODO: Here I only use the same-species terms, which is a
                # major simplification. The same-species terms have a smaller
                # size than cross-species terms due to the fact that dscribe
                # does not store the symmetric elements. To have shapes that
                # are compatible for the dot-product, you would have to
                # re-create the dropped terms here manually. Maybe the SOAP
                # descriptor should have flag that disables the dropping out of
                # these terms? See also issue #48
                if alpha_1 == beta_1 and alpha_2 == beta_2:
                    similarity += np.dot(
                        p_1[0, soap.get_location([alpha_1, beta_1])],
                        p_2[0, soap.get_location([alpha_2, beta_2])]
                    ) * kernel[alpha_1, alpha_2] * kernel[beta_1, beta_2]

print(similarity)

The only catch is that the dscribe output has removed some of the symmetric elements, which don't carry any extra information. This means that the size of a same-species portion of the vector is actually smaller than a cross-species portion of the vector and you can't take their dot product directly. You would first need to need to reintroduce those dropped out parts manually. Issue #48 might help to understand this a bit more.
It should be possible to introduce a flag in SOAP that disables the dropping out of these symmetric parts. That would just require a bit of digging around in the codebase (see e.g. here). We would be more than happy to include such a PR.


[Crash] Crash on autosave

Application has crashed: C++ exception
mods/BeardLib-Editor-master/Classes/ProjectManager.lua:241: attempt to index local 'mod' (a nil value)

SCRIPT STACK

save_main_xml() @mods/BeardLib-Editor-master/Classes/ProjectManager.lua:117
save_main_xml() @mods/BeardLib-Editor-master/Classes/Map/InEditorOptions.lua:340
@mods/BeardLib-Editor-master/Classes/Map/InEditorOptions.lua:290

I may have tried to duplicate an element while the autosave was occurring but that may be unrelated

that was unrelated, crashed while i was not actively working on a map

Are you running maps through the 'Maps' folder? other frameworks are not supported at the moment.

yes it's in the maps folder, also normal saves cause the crash too

Nevermind my project has been doing this thing where it splits the narrative and the map for some reason


Cookie banner in skillmap

There is a url parameter to dismiss the cookie.

Also seeing Usabilla tag pop up

@Jaqster do you want the usabilla tag hidden in this view? it could be useful if the user has feedback on this page

Hmmm... yeah, that's true.  If they click on that Feedback tag while the Sprite Editor is open can they give feedback on it?

no, it looks like if you choose "specific feedback" it only lets you select the entire iframe, and not things in the iframe

Then is it possible to hide the Feedback tab (or put it behind) when a modal window like the Sprite Editor pops up?  Not a big deal for bigger screens, but for small screens when the modal takes up the whole screen it's weird to have the Feedback tab floating over it...

@Jaqster hmm, i think it might be a little messy to sync the visibility of the sprite editor between the iframe and the outside. but i could hide it from the iframe view altogether (no usabilla when you're "inside" a card), if it's more in the way than useful


Collect and test refactoring approaches scoring by sfilter

Not relevant after this change https://github.com/alex-d-bondarev/sfilter/commit/dd640c9c03522d29d5ed48f45e4f9da94e08f3ca


Add SBT test dependency example in README

This library is incredibly helpful and many Scala developers will be interested to use it too.

Well, I believe that without that Scala users also can use this tool, but ok, I can merge that ;-)


No video sync on a non rgbic strip

Due to there being no segments you cannot use the video sync option

sadly yes, though since I don't have access to a strip without RGBIC I can't help on this.
Open to anyone who can submit a PR

sadly i dont have an android and i dont know any way else of looking at the bluetooth log

how do you send the data to the device as i cannot work it out i have found the format of the packets for my device

there is a small box where you can test out custom commands.


CODEOWNERS: Add missing trailing / on some directories

Gets rid of some warnings from check_compliance.py:
Wrong syntax: /home/ulf/z/subsys/fs/fcb
Wrong syntax: /home/ulf/z/subsys/fs/nvs
Wrong syntax: /home/ulf/z/subsys/storage

Codecov Report

Merging #13721 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13721   +/-   ##
=======================================
  Coverage   52.24%   52.24%
=======================================
  Files         307      307
  Lines       45413    45413
  Branches    10508    10508
=======================================
  Hits        23726    23726
  Misses      16898    16898
  Partials     4789     4789

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 17cc291...592f184. Read the comment docs.


Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
i have not changed anything yet

use haxe 4.2.5 for now

use lime test windows -debug its better

yes but does that fix the issue?

I tried it and it made no difference

you need to use haxe 4.2.5

use lime test windows -debug its better

yes but does that fix the issue?

yes :trollface:

I tried it and it made no difference

My Haxe Version: 4.2.5
in Main.hx
Under
ClientPrefs.loadDefaultKeys();

Change addChild to
addChild(new FlxGame(game.width, game.height, game.initialState, #if (flixel < "5.0.0") game.zoom, #end game.framerate, game.framerate, game.skipSplash, game.startFullscreen));

i also got this issue while using kade 1.8
and im thinking you need to use haxe 4.2.5

i also got this issue while using kade 1.8
and im thinking you need to use haxe 4.2.5

this ain't the place to make issues for kade engine


Distribution strategy

Do we include JS bundles in the GitHub repo?

@jverkoey is mildly skeptical, but many other projects do it
@traviskaufman is probably also interested

Should probably have 3 targets:

Raw source, complete with Flow annotations and experimental Babel syntaxes
Closure-friendly build that converts Flow annotations and experimental syntax into JSDoc and ES2015.  Let Closure handle any transformations beyond that (including, perhaps, parsing import/export).
Single-file bundle, for browsers

Release process should generate the above targets, run the appropriate tests on each, and push to the relevant places
Do we host the browser-friendly bundle on a CDN?

Loosely-related: https://github.com/material-motion/material-motion-experiments-js/issues/3

Skeptical only insofar as the amount it affects day-to-day code review. If every diff needs to regenerate a large file then this will introduce a decent amount of technical overhead to code review, rollbacks, and diff workflows.
If the assets are only generated on release then this skepticism is lessened.

Turned this in to a milestone: https://github.com/material-motion/material-motion-experiments-js/milestone/6


How to disable drag and drop in mobile resolution

Hi everybody,
I wonder how to disable drag and drop in mobile resolution.
It's possible?

isDraggable and isResizable should allow you to do this easily. https://github.com/STRML/react-grid-layout#grid-layout-props

@cp Could you show me an example?

<ReactGridLayout isDraggable=false isResizable=false layout={layout} cols={12} rowHeight={30} width={1200}>

a

b

c

</ReactGridLayout>

@cp but how to put
isDraggable={false}
isResizable={false}

only when you are in cellular resolution?

This library looks like it could be a good solution: https://github.com/contra/react-responsive

@cp To resolve this problem , it really is necessary to install a library?
I'm sad about it 😭

Just add a resize handler to the window, measure its width & toggle the bool based on some width (like 768).

Question: is it possible to set the isDraggable and isResizable attributes run-time?
I wrapped around ResponsiveReactGridLayout into a container react element and placed an Edit Mode on/off switch. That button sets the editMode state of the container, which passes down the isDraggable and isResizable properties according to the switch. So far this seems like not working for me. I start with both props false, but when I supposedly re-render the elements, the edit mode does not turn on for real.

@MrCsabaToth That's indeed possible, and is how I have my app set up. It's likely a bug in how your app is passing props to RGL.

@cp Do you have source code example? Do you set the isDraggable / isResizable globally fo the layout or individually for the items? If you set it inidvidually, how do you set it (or do you set it at all) for the whole layout at the same time?

Do you have source code example? Do you set the isDraggable / isResizable globally fo the layout or individually for the items? If you set it inidvidually, how do you set it (or do you set it at all) for the whole layout at the same time?

@cp


Using the middleware doesn't sweep the flash

I tried using the middleware as documented (by replacing the ActionDispatch::Flash middleware with it).
I was getting my messages, but some messages were getting 'stuck' in session.  I think it's because if the ActionDispatch::Flash middleware doesn't run, the Flash object never gets swept.  The rack environment contains two copies of the FlashHash: one under a flash key, and another copy serialized into the session cookie.  The one in the session cookie never dies, and the messages are never swept.
I found that by using config.middleware.insert_before ActionDispatch::Flash, CacheableFlash::Middleware (instead of swap), everything works as expected.

Please consider switching to https://github.com/leonid-shevtsov/unobtrusive_flash


Contradictory statements on order of lookups

The document “OpenType Layout Common Table Formats” states: “To implement features, a client applies the lookups in the order the lookup definitions occur in the LookupList. As a result, within the GSUB or GPOS table, lookups from several different features may be interleaved during text processing.”
This statement contradicts statements in the descriptions of most shaping engines, which describe several sequential stages of feature application, each with a defined set of features to be applied within the stage, and sometimes requiring that features are applied one by one.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1cb42967-20ca-9270-4572-65315127fcc5
Version Independent ID: 1fa413f1-71cf-ac2a-0999-70dd5d8ac4cd
Content: OpenType layout common table formats - Typography
Content Source: typographydocs/opentype/spec/chapter2.md
Product: typography

Not really contradictory within the OT spec, but does ignore the larger context that a client may process certain sets of features in sequential stages. That would be good clarification to add.

Is there any relevant client that “applies the lookups in the order the lookup definitions occur in the LookupList”?

Every implementation should for whatever features get processed in the same shaping stage.

Let me rephrase my question using your terminology: Is there any relevant client that does not break the lookups in the LookupList into separate sets of features in sequential stages?
Also, is there any shaping engine that, for all stages that it defines, “applies the lookups in the order the lookup definitions occur in the LookupList”?

Let's take feature application in USE as an example: during GSUB processing, it processes features in six groups,

First, "Default glyph pre-processing group": locl, ccmp, nukt, akhn
Second, "Reordering group": rphf, pref
Third, "Orthographic unit shaping group"
Fourth (after a re-ordering pass), "Topographical features, GSUB": isol, init, medi, fina
Fifth, "Standard typographic presentation, GSUB": abvs, blws, calt, clig, haln, liga, pres, psts, rclt, rlig, vert, vrt2
Sixth, "Custom substitution features requested by the application"

(Actually, I would have thought groups 5 and 6 would be combined, since group 5 includes features like liga that are optional but on by default. But issues for the USE spec would be separate from issues for this part of the OT spec.)
Within each group, features get associated with some sub-runs within the string, and then lookup processing is done across the string. Whatever lookups are associated with the features in that group, all of those lookups will get processed one at a time in the order they occur within the LookupList table.
So, for example, suppose the Feature tables in the feature list for features in the first group have lookupListIndices[] arrays as follows:

akhn: lookupListIndices = [17, 22]
ccmp: lookupListIndices = [19, 8]
locl: lookupListIndices = [2, 31, 10]
nukt: lookupListIndices = [12, 18]

Then in that feature-processing stage, the following lookups would be applied in this order:

2, 8, 10, 12, 17, 18, 19, 22, 31

That's how all "clients" should be implemented.
What I was meaning earlier is that this is consistent with what is currently stated in the OT spec, but that the OT spec doesn't clarify that clients may partition features into different groups that each get processed in stages, one group of features at a time. So that's what I was thinking out to be clarified in the spec.

Addendum: the USE spec (in describing the first group) has a statement on the order of lookup processing that reflects what the OT spec says:

Lookups associated with any of these features will be triggered in the lookup-order specified by the font developer. It is possible to interleave lookups for different features.

Now, that is immediately followed by this:

The order of features given here is recommended.

I don't understand what the intent of that is. The OT spec states, regarding the FeatureList,

The FeatureRecord array is arranged alphabetically by FeatureTag names.

So that last statement in the USE spec doesn't seem to make sense to me. But that is an issue for the USE spec, not the OT spec.

_“To implement features, a client applies the lookups in the order the lookup definitions occur in the LookupList. As a result, within the GSUB or GPOS table, lookups from several different features may be interleaved during text processing.”

This text is interpretable in a way that makes it technically accurate, but it is imprecise. It should convey that some features are applied by shaping engines in set order or in processing blocks, but that within processing blocks LookupList order determines the order in which the client applies lookups and, hence, within processing blocks lookups from different features may be interleaved.

So that last statement in the USE spec doesn't seem to make sense to me. But that is an issue for the USE spec, not the OT spec.

It’s shorthand for ‘the order of lookups associated to features given here is recommended’. It’s a perennial problem in talking about OTL that features are the thing with shared labels between fonts—while the lookups that are actually what we often need to talk about have either arbitrary names in sources or numbers in the LookupList. So we fall back on talking about feature order when what we're really talking about is the order of the lookups associated to the features.

Whatever lookups are associated with the features in that group, all of those lookups will get processed one at a time in the order they occur within the LookupList table.

Not true for the reordering group of the USE – the documentation says “These features are applied individually in this order, rphf, pref”.

This text is interpretable in a way that makes it technically accurate, but it is imprecise...

As the quoted text was from the USE spec, please open an issue on that as you deem appropriate. (No point discussing further here.)

@NorbertLindenberg

Not true for the reordering group of the USE...

I amended my earlier comment to address that case. Please see the revised comment. My general point still holds.

I amended my earlier comment to address that case. Please see the revised comment.

Got it – sorry for missing that earlier.

My general point still holds.

You’re still saying that clients “may partition features”. We haven’t identified any client that does not partition them, so the spec should be clear that partitioning is the normal case, with a remote possibility that some client may lump all features into the same subset.

I think "may" is sufficient, but the wording could indicate it's not _un_common. IIRC, MS's "generic" engine which was used for Latin, Cyrillic, and other scripts did not do any partitioning of features in that way. So, I'm sure it's not true for all "clients".
In any case, as long as this spec points out that that's a permitted possibility, it's up to shaping specs to indicate what partitioning if any is done.

I think even the most generic shaping engines might still be processing locl and ccmp before other features. I think it would be worthwhile to point out that shaping engines commonly prioritise some features independently of lookup order, and that shaping for some scripts requires processing blocks of features (e.g. pre- and post-reordering blocks for Indic scripts).

I think it would be worthwhile to point out that shaping engines commonly prioritise some features independently of lookup order, and that shaping for some scripts requires processing blocks of features (e.g. pre- and post-reordering blocks for Indic scripts).

That's along the lines of what I was thinking would be appropriate.

Proposed change for the next version: add the following note in the Features and Lookups section after the note about GSUB preceding GPOS:

Note: A client may process GSUB features in ordered stages, with particular features processed in each stage. A client may also perform certain operations on glyph sequences, such as re-ordering of glyphs, before or between these stages. Such processing is required for correct support of many scripts. Details on such script-specific processing is outside the scope of this specification. Within any such feature-processing stage, however, lookups referenced by the features applied in that stage must be processed in LookupList order.

The "may" wording is problematic because it gives the impression that it's up to the client to choose what to do.
I suggest a more direct note saying that "many script-specific shaping engines process features in stages and only within each stage the lookups are applied by increasing lookup-index."

I don't think the "may" wording is problematic here since this is a very general context—what is true of feature/lookup processing in the general case. It's noted that this will be required for implementation of some scripts, and leaves the details to some separate specification(s).

There seems to be an implicit assumption here that shaping engines cannot be mentioned in the “spec” part of the OpenType documentation. Why is that? It should be clear to everybody that you can’t have a functional OpenType implementation without shaping engines (and assorted shaping-related functionality that’s yet to be  documented), and that you can’t create a font for any but the simplest scripts if you don’t understand the shaping engine(s) supporting the script(s) of the font.

I don't see how it will make a lick of difference here if "shaping engines" are mentioned instead of "applications". But it would introduce a need in this spec to explain what is meant by the term. I don't see the point.

Applications using OpenType number in the millions, and we don’t know their developers, so it’s impossible to know what they all do and impossible to standardize their behavior. As a result, we’re stuck with “may” wording and fuzzy recommendations.
Rendering systems with shaping engines number in the single digits (I know of five), and we mostly know their developers, so it’s quite possible to find out what they do and to standardize them. It allows us to describe reality, as in “Most clients process GSUB features in ordered stages...”.
There are many other parts of the spec that would benefit from this improvement in clarity.

I'm not opposed to the direction you're suggesting... at some point. But this change in this one place would have no effect, and would just make the spec less coherent. To have any significant value it would need to be something done systematically. That means touching probably hundreds of places in the spec, as well as a coherent discussion somewhere of the architectural model that's assumed. Even if the change weren't that big, the ROI is unclear: it's not going to change the handful of shaping engine implementations, or any font development tools.
So, sure, at some point. I'm not inclined to start piecemeal now. I'd give much higher priority to dealing with issues that really are impacting implementations now; e.g., #191, #310, #363, #407, #455, #535, #560, #569, #576, and several others. Many of these require time to get input and discussion, so I can work on some lower impact suggestions in the meantime; like #347, #509, maybe even #519 (a more localized but still very big change that you've also asked for).


Explain requirements not met for expedition?

KanColleHelpers is already capable of listing requirements not met for a specify fleet.
I'm just thinking about how to use this feature: now available expeditions are in blue circles, maybe other expeditions can be grayed out and some tooltips can be added to gray circles indicating requirements not met.
The API is already designed for the ease of translation: Requirements are actually defined as algebraic data type, for example Flagship (ShipDrum 2) is saying "flagship should at least carry two drums", values can be distinguished by javascript instanceof.
Let me know whether you are interested in this. Going to sleep, will response late.

hm this is interesting, though I doubt we'll need to implement this immediately on the panel. We already have users complaining about spoon-feeding and asking for settings to turn it off. We can retain the blue circles on panel, but the advice for unqualified expedition might be better for the Strategy Room.

I see what he's concerning. And here are some suggestions:

hide these blue circles for fleet 1, as it doesn't seem necessary. Sorry that I forgot to do this after adapting to the new API.
change the way it works: after my very first hack, I often find myself looking at the list of numbers and see if the intended one is there, maybe we can just keep a drop-down list somewhere. It show nothing by default, but if user choose one expedition, then we print out requirements not met. We can have more features in strategy rooms, but I think it's still good to have this in devtools page, as the strategy room doesn't seem to be responsive about fleet member / equipment changes.

The same person in question pretty much got worked up over the unpolished edges of KC3 Kai and called it quits, hopefully I can try and alleviate the issue a bit.

alright, wrote a response to that guy, didn't notice it was the same person complaining
about the expedition, I see the point about not needing to show all qualified, but instead its true that players first decide on the expedition to go to, and build the fleet from there, not the other way around. :+1:

will be included in #685


My Calendar Block in RTL language should change direction of drawing days from right to left and start day of week should be changed to.

Is there an existing issue for this?

[X] I have searched the existing issues

Version of Corteza
2023.3.6
Current Behavior
When I use My Calendar in CRM application, when language is 'fa', Calendar type is correctly jalali but direction of calendar block and start day of week is incorrect.
inactive days in calendar is still painted according to gregorian calendar.
Expected Behavior
Direction of days  should be from right to left , and start day of week should be 'شنبه'  or 'saturday'.
inactive days in calendar in month view should be painted according to jalali calendar.
Steps To Reproduce

change 'preferred language' in user profile.
select 6 dot to return to main page.
select CRM application
go to home page

Environment and versions
No response
Anything else?
I RTL languages , Calendar type in calendar block (or Date picker component) should be changed according to selected language and country culture.

Thanks for reporting it

it seems RTL is not in top of your periority list, because other module like report does not support rtl too. and of course controls like datepicker, calendar and kanban board should support other calendars too. it is a lot of work to do

Branch: 2023.9.x-feature-update-full-calendar-to-fix-persian-cal-issues
I managed to adjust the text direction according to the currently selected language by updating the cal library to the then latest verison but a lot of styles are broken for the different calendar views (day, month, week, agenda). What I would do is wait for a version where the styles aren't so broken


Update sql-database-understanding-dtus.md

DTU stands for database throughput unit not database transaction unit.  While DTU is a representation of the overall ability of the database to process transactions it's not an exact correlation.  For consistency with the other pages on the Azure product pages/documentation we should be using database throughput throughout (see for example: https://azure.microsoft.com/en-us/pricing/details/sql-database/) .  I've also added an metaphor of horsepower to help people understand the notion of DTU in terms that most people are at least familiar with.  Please let me know if you have any questions or would like to discuss!

Hi @twright-msft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@rothja
FYI

I believe that we are making the decision to actually rebrand this to "Transaction Unit" across all of the existing content. The articles that have most recently been published use this as the term. I'll confirm this though and I connect you to the people who decided to make this rebranding.


Use mergequeue for dependabot auto merges

Keeps the same auto-merge behavior (for semver-minor updates) but changes it to use our mergequeue.
This improves DX because it prevents dependabot merges from bypassing the queue and also means that sanity
tests for these PRs don't fail (they run with the correct env)

Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[ ] :no_entry: No

Type of change

[ ] :sunflower: Feature
[ ] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Supportability/Tests
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

#3591

Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

LGTM! I may copy this! :)

Will confirm once we see a dependabot PR use this.


extract_patches.py not working properly

Hi @vqdang @simongraham ,
I am relatively new to hovernet and am having problems with running the training. After running extract_patches.py, i have the following dataset folder generated:
-> hover_net/dataset/training_data/consep/consep/train/540x540_164x164
-> hover_net/dataset/training_data/consep/consep/valid/540x540_164x164

However, these folders are empty. Could you please advise if I'm missing anything? Thank you very much for your time.

How long did it take to extract patches? Maybe it didn't actually extract any patches and it just created the directories. Make sure the path to your original data is correct.


Investigating support GraphQL

What would you like to be added:
FYI https://graphql.org/

GraphQL is a query language for your API, and a server-side runtime for executing queries using a type system you define for your data.

The benifit is Get many resources in a single request
As how to support GraphQL, i donot have a clear thought right now.  Any comments are welcomed.
Why is this needed:
Currently, if we want to check a workload and its correslated resources, we must do many queries.  With graphQL supported, this can be largely saved.

do you means something like ELK api?

In what way to query and output the log?  add command kurator logs ？

After searching more, i found https://github.com/onelittlenightmusic/kubernetes-graphql does exactly what I want.
Read https://scientya.com/search-kubernetes-world-with-graphql-1c57888c2f22 for more details.
unfortunately, I did not install it successfully according to the guide.

hi @hzxuzhonghu , what do you think of this.
https://github.com/hasura/graphql-engine

unfortunately, I did not install it successfully according to the guide.

I successfully installed using helm. FYI
helm repo add graphql-mesh https://onelittlenightmusic.github.io/graphql-mesh-docker/helm-chart
helm repo up
helm install my-graphql-mesh graphql-mesh/graphql-mesh

http://<IP_ADDRESS>:31713/

Does it support open API convert?

We need automatically do this, can make use of kubernetes' swagger.json

@hzxuzhonghu I think this is good, what do you think.
https://docs.cloudgraph.dev/querying-kubernetes-data

It seems this https://github.com/cloudgraphdev/cloudgraph-provider-kubernetes#supported-services is not automatically converted, while https://github.com/onelittlenightmusic/kubernetes-graphql make use of graphqlMesh, which can convert from a swagger.json

FYI how graphql-mesh handles openapi  https://www.graphql-mesh.com/docs/handlers/handlers-introduction


Add middle click to close tab functionality

On clicking a tab, "switch to tab" if the mouse is left-clicked, otherwise "close the tab" if the mouse is middle clicked

handleClick now bound in constructor (not render())

Mouse click native events now assigned to descriptive variables

Nice 👍

If you use BetterTouchTool (or equivalent) you could map a middle click to a gesture 😄

👍 Everything is working.
@rauchg that's ready to merge.