add passReqToCallback parameter

It's usual for passport strategies - f.e. look at passport-local strategy.

Sure.  Can you add a test & update documentation as well?  Thanks!

Merged #71, which is near-duplicate.


[refactor] refactor EffectsEnvelope as Envelope

Looks like this is stacked on top of https://github.com/MystenLabs/sui/pull/4142? I think you can compare to that branch to get only the diff between them

@lxfind I opened this one so I don't have to open another one once we merge the TransactionEnvelope refactor.

What I meant is in the top you can compare this branch to the other branch, so that github will display the difference between the two branches.

@randall-Mysten Hey Randall, for PRs that are mostly code changes, after you reviewed the documentation change, please don't approve it yet, as we still need to review the code changes (otherwise PRs can merge once approved). Instead you can comment with something like "doc change LGTM" and etc. Thanks!

@kchalkias Oops, this is my fault. I have to merge the previous PR, then @lxfind will be able to review this one.

Please reopen if this is still a relevant issue. Closing stale PRs


Setup circleci ADC

Also, move all tests to use the project given in the environment variable, using buckets named after the project.

Okay - spanner samples were failing intermittently, but I think it's because both travis and circle were running at the same time and clobbering state. I'm going to merge and then turn off travis.


Updated deprecated links in high-availability-cluster.rst

Summary
Updated deprecated links in high-availability-cluster.rst
Ticket Link

NA

Hello @Rutam21,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.


Redirect path in logout

Issue and Steps to Reproduce
logout doesn't expose a callback uri option:
export declare const useOidc: (configurationName?: string) => {
    login: (callbackPath?: any) => any;
    logout: () => any;
    isLogged: boolean;
};
export declare const useOidcAccessToken: (configurationName?: string) => any;
export declare const useOidcIdToken: (configurationName?: string) => any;
//# sourceMappingURL=ReactOidc.d.ts.map

Versions
4.2.3
Screenshots
Expected
    login: (callbackPath?: any) => any;
    logout: (callbackPath?: string) => any;

Is there something else than appending the callbackPath to the logout endpoint that i'm missing ?

in oidc.ts
line 434
    async logoutAsync() { <--- HERE
        const oidcServerConfiguration = await this.initAsync(this.configuration.authority);
        // TODO implement real logout
        await this.destroyAsync();
        window.location.href = oidcServerConfiguration.endSessionEndpoint; <-- Add redirect
    }

Actual
Additional Details
I can open a PR for that If you want.

Installed packages:

Yes, there is a pr on appauth js about logout.
I was waiting for a merge from it. I will investigate next monday on it. If you have time, a pr would be very cool.
Thank you very much for your feeback.

This Pull Request merge would be nice => https://github.com/openid/AppAuth-JS/pull/198

Hi,
I forked react-oidc and fitted it to a "merged" AppAuth (https://github.com/arssly/AppAuth-JS).
Logout seems to work fine with react-oidc sample app.

Here is my feature branch : https://github.com/bonnetb/react-oidc/tree/feat/logout
(not to be merged before https://github.com/openid/AppAuth-JS/pull/198 is merged)

Awesome @bonnetb thank you,
May you set a message on https://github.com/openid/AppAuth-JS/pull/198, it would be cool a merge from them :)

Do you have any news about this ?
I'm really concerned with and the lib AppAuth-JS sems to be off ...

Me too, may be we will need to implement it here.

Seems like AppAuth-JS hasn't been updated in a year. I wonder if it has become dead?

Yearh, I will try to email the team.
I am thinking to take the owership of it and ask openid team to certify their own library.
For example:
axa-fr/appauthjs

I'am waiting for any news from them => https://github.com/openid/AppAuth-JS/issues/209
If no news, I will fork it and ask openid team to certify the fork :/

I made https://github.com/AxaGuilDEv/react-oidc/pull/761
But It does seem to work with the identityServer demo.

Is there any solution for the Identity Server? To redirect on logout?

I will investigate


feat: add blas/base/dznrm2

Description

What is the purpose of this pull request?

This RFC proposes to add a routine to find the euclidean norm of a complex double-precision floating-point vector as defined in BLAS Level 1 routines. Specifically adding @stdlib/blas/base/dznrm2 is proposed.
Related Issues

Does this pull request have any related issues?

None.
Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@aman-095 LMK when this PR is ready for review.

Hey, @kgryte, I have added C and Fortran implementation to this.


Active build configuration warning

With current CMT code base, any project gets a warning from CppTools about. This is with presets on, but even if the currently selected configure preset does define CMAKE_BUILD_TYPE.
The build configurations generated do not contain the active build configuration. Using 'Debug' for CMAKE_BUILD_TYPE instead of 'null' to ensure that IntelliSense configurations can be found.

@andreeis can you share the repro for this?  And also run CMake: Log Diagnostics and share it here.

Here you go. I am not noticing any hint. Also, on linux it doesn't happen and the below is on windows.

Expand C/C++ Log Diagnostics
-------- Diagnostics - 2/2/2022, 1:25:50 AM
Version: 1.7.1
Current Configuration:
{
"name": "Win32",
"includePath": [
"${workspaceFolder}/"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.18362.0",
"compilerPath": "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\cl.exe",
"cStandard": "c17",
"cppStandard": "c++17",
"intelliSenseMode": "windows-msvc-x64",
"compilerArgs": [],
"intelliSenseModeIsExplicit": false,
"cStandardIsExplicit": false,
"cppStandardIsExplicit": false,
"mergeConfigurations": false,
"compilerPathIsExplicit": false,
"configurationProvider": "ms-vscode.cmake-tools",
"browse": {
"path": [
"${workspaceFolder}/"
],
"limitSymbolsToIncludedHeaders": true
}
}
Custom browse configuration:
{
"browsePath": [
"c:/work/projects/cmaketools/test1.10/quickstart1/out/build/cfgvs2019x64/cmakefiles",
"c:/work/projects/cmaketools/test1.10/quickstart1/out/build/cfgvs2019x64/cmakefiles/9a5977fd6c1ef9d5456a0b2a0cdf454e",
"c:/work/projects/cmaketools/test1.10/quickstart1"
],
"compilerPath": "c:/program files (x86)/microsoft visual studio/2019/buildtools/vc/tools/msvc/14.28.29910/bin/hostx64/x64/cl.exe",
"compilerArgs": []
}
Custom configurations:
[ C:\Work\Projects\CMakeTools\Test1.10\QuickStart1\main.cpp ]
{
"defines": [
"WIN32",
"_WINDOWS"
],
"includePath": [],
"compilerPath": "c:/program files (x86)/microsoft visual studio/2019/buildtools/vc/tools/msvc/14.28.29910/bin/hostx64/x64/cl.exe",
"compilerArgs": [
"/DWIN32",
"/D_WINDOWS",
"/W3",
"/GR",
"/EHsc",
"/MDd",
"/Zi",
"/Ob0",
"/Od",
"/RTC1"
]
}
Translation Unit Mappings:
[ C:\Work\Projects\CMakeTools\Test1.10\QuickStart1\main.cpp ]:
C:\WORK\PROJECTS\CMAKETOOLS\TEST1.10\QUICKSTART1\MAIN.CPP
Translation Unit Configurations:
[ C:\Work\Projects\CMakeTools\Test1.10\QuickStart1\main.cpp ]:
Process ID: 35856
Memory Usage: 17 MB
Compiler Path: c:/program files (x86)/microsoft visual studio/2019/buildtools/vc/tools/msvc/14.28.29910/bin/hostx64/x64/cl.exe
Includes:
C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\BUILDTOOLS\VC\TOOLS\MSVC\14.28.29910\INCLUDE
C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\UM
C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\UCRT
C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\SHARED
C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\WINRT
C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.18362.0\CPPWINRT
Defines:
WIN32
_WINDOWS
WIN32
_WINDOWS
Standard Version: ms_c++14
IntelliSense Mode: windows-msvc-x64
Other Flags:
--rtti
Total Memory Usage: 17 MB
------- Workspace parsing diagnostics -------
Number of files discovered (not excluded): 5045
Number of files parsed: 4

Expand CMake Tools Output Channel
[main] Safe constructing new CMakeTools instance
[variant] Constructing VariantManager
[main] Constructing new CMakeTools instance
[main] Starting CMakeTools second-phase init
[variant] Loaded new set of variants
[main] CMakeTools instance initialization complete.
[kit] Reading kits file C:\Users\andris\AppData\Local\CMakeTools\cmake-tools-kits.json
[kit] Successfully loaded 36 kits from C:\Users\andris\AppData\Local\CMakeTools\cmake-tools-kits.json
[kit] Not reading non-existent kits file: c:\Work\Projects\CMakeTools\Test1.10\QuickStart1.vscode\cmake-kits.json
[presetController] Reading presets file c:\Work\Projects\CMakeTools\Test1.10\QuickStart1\CMakePresets.json
[presetController] Successfully validated presets in c:\Work\Projects\CMakeTools\Test1.10\QuickStart1\CMakePresets.json
[main] Resolving the selected configure preset
[main] Loading new configure preset into CMake driver
[main] Resolving the selected build preset
[main] Loading new build preset into CMake driver
[main] Resolving the selected test preset
[main] Loading new test preset into CMake driver
[extension] Configuring workspace on open file:///c%3A/Work/Projects/CMakeTools/Test1.10/QuickStart1
[main] Starting new CMake driver
[main] Starting CMake driver
[cmakefileapi-driver] Creating instance of CMakeFileApiDriver
[driver] Initializating base driver using preset
[driver] CMakeDriver configure preset set to CfgVS2019X64
[driver] CMakeDriver build preset set to BuildFromCfgVS2019X64
[driver] CMakeDriver test preset set to TestFromCfgVS2019X64
[cache] Reading CMake cache file c:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/build/CfgVS2019X64/CMakeCache.txt
[cache] Parsing CMake cache string
[cache] Reading CMake cache file c:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/build/CfgVS2019X64/CMakeCache.txt
[cache] Parsing CMake cache string
[cmakefileapi-parser] Read reply folder: c:\Work\Projects\CMakeTools\Test1.10\QuickStart1\out\build\CfgVS2019X64.cmake\api\v1\reply
[cmakefileapi-parser] Found index files: ["cache-v2-3907fec7dec0371c28c2.json","codemodel-v2-239ae46a1fae5fa2653f.json","directory-.-Debug-d0094a50bb2071803777.json","directory-.-MinSizeRel-d0094a50bb2071803777.json","directory-.-Release-d0094a50bb2071803777.json","directory-.-RelWithDebInfo-d0094a50bb2071803777.json","index-2022-02-02T07-16-46-0205.json","target-ALL_BUILD-Debug-a13120f62a16846c36d2.json","target-ALL_BUILD-MinSizeRel-a13120f62a16846c36d2.json","target-ALL_BUILD-Release-a13120f62a16846c36d2.json","target-ALL_BUILD-RelWithDebInfo-a13120f62a16846c36d2.json","target-Continuous-Debug-63c8ede2cf40f8a22f08.json","target-Continuous-MinSizeRel-63c8ede2cf40f8a22f08.json","target-Continuous-Release-63c8ede2cf40f8a22f08.json","target-Continuous-RelWithDebInfo-63c8ede2cf40f8a22f08.json","target-Experimental-Debug-7683d1076167fda91ee5.json","target-Experimental-MinSizeRel-7683d1076167fda91ee5.json","target-Experimental-Release-7683d1076167fda91ee5.json","target-Experimental-RelWithDebInfo-7683d1076167fda91ee5.json","target-Nightly-Debug-9971f51fce3e8b1867de.json","target-Nightly-MinSizeRel-9971f51fce3e8b1867de.json","target-Nightly-Release-9971f51fce3e8b1867de.json","target-Nightly-RelWithDebInfo-9971f51fce3e8b1867de.json","target-NightlyMemoryCheck-Debug-c922b253a7ec7e3a19ab.json","target-NightlyMemoryCheck-MinSizeRel-c922b253a7ec7e3a19ab.json","target-NightlyMemoryCheck-Release-c922b253a7ec7e3a19ab.json","target-NightlyMemoryCheck-RelWithDebInfo-c922b253a7ec7e3a19ab.json","target-QuickTest-Debug-02aa8e8e7210ce231d05.json","target-QuickTest-MinSizeRel-f12a38e2a8c7c1d0cb02.json","target-QuickTest-Release-83298b692081ff0fcf27.json","target-QuickTest-RelWithDebInfo-fe878c0200b6181c4746.json","target-ZERO_CHECK-Debug-36800e54d5ddac5bf6c1.json","target-ZERO_CHECK-MinSizeRel-36800e54d5ddac5bf6c1.json","target-ZERO_CHECK-Release-36800e54d5ddac5bf6c1.json","target-ZERO_CHECK-RelWithDebInfo-36800e54d5ddac5bf6c1.json","toolchains-v1-eda23bf84c60b4bc0df1.json"]
[driver] Setting new variant Debug
[main] Configuring folder: QuickStart1
[main] Saving open files before configure/build
[driver] Start configure
[driver] Running pre-configure checks and steps
[cmakefileapi-driver] Configuring using preset
[cmakefileapi-driver] Invoking CMake C:\Program Files\CMake\bin\cmake.EXE with arguments ["-DCMAKE_BUILD_TYPE=Debug","-DCMAKE_INSTALL_PREFIX=c:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/install/CfgVS2019X64","-Sc:/Work/Projects/CMakeTools/Test1.10/QuickStart1","-Bc:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/build/CfgVS2019X64","-G","Visual Studio 16 2019","-T","host=x64","-A","x64"]
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=c:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/install/CfgVS2019X64 -Sc:/Work/Projects/CMakeTools/Test1.10/QuickStart1 -Bc:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/build/CfgVS2019X64 -G "Visual Studio 16 2019" -T host=x64 -A x64
[cache] Reading CMake cache file c:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/build/CfgVS2019X64/CMakeCache.txt
[cache] Parsing CMake cache string
[cmake] -- Selecting Windows SDK version 10.0.18362.0 to target Windows 10.0.22000.
[cpptools] The build configurations generated do not contain the active build configuration. Using "Debug" for CMAKE_BUILD_TYPE instead of "null" to ensure that IntelliSense configurations can be found
[cmake] -- Configuring done
[cmake] -- Generating done
[cmake] -- Build files have been written to: C:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/build/CfgVS2019X64
[cmakefileapi-parser] Read reply folder: c:\Work\Projects\CMakeTools\Test1.10\QuickStart1\out\build\CfgVS2019X64.cmake\api\v1\reply
[cmakefileapi-parser] Found index files: ["cache-v2-3907fec7dec0371c28c2.json","codemodel-v2-239ae46a1fae5fa2653f.json","directory-.-Debug-d0094a50bb2071803777.json","directory-.-MinSizeRel-d0094a50bb2071803777.json","directory-.-Release-d0094a50bb2071803777.json","directory-.-RelWithDebInfo-d0094a50bb2071803777.json","index-2022-02-02T09-24-13-0810.json","target-ALL_BUILD-Debug-a13120f62a16846c36d2.json","target-ALL_BUILD-MinSizeRel-a13120f62a16846c36d2.json","target-ALL_BUILD-Release-a13120f62a16846c36d2.json","target-ALL_BUILD-RelWithDebInfo-a13120f62a16846c36d2.json","target-Continuous-Debug-63c8ede2cf40f8a22f08.json","target-Continuous-MinSizeRel-63c8ede2cf40f8a22f08.json","target-Continuous-Release-63c8ede2cf40f8a22f08.json","target-Continuous-RelWithDebInfo-63c8ede2cf40f8a22f08.json","target-Experimental-Debug-7683d1076167fda91ee5.json","target-Experimental-MinSizeRel-7683d1076167fda91ee5.json","target-Experimental-Release-7683d1076167fda91ee5.json","target-Experimental-RelWithDebInfo-7683d1076167fda91ee5.json","target-Nightly-Debug-9971f51fce3e8b1867de.json","target-Nightly-MinSizeRel-9971f51fce3e8b1867de.json","target-Nightly-Release-9971f51fce3e8b1867de.json","target-Nightly-RelWithDebInfo-9971f51fce3e8b1867de.json","target-NightlyMemoryCheck-Debug-c922b253a7ec7e3a19ab.json","target-NightlyMemoryCheck-MinSizeRel-c922b253a7ec7e3a19ab.json","target-NightlyMemoryCheck-Release-c922b253a7ec7e3a19ab.json","target-NightlyMemoryCheck-RelWithDebInfo-c922b253a7ec7e3a19ab.json","target-QuickTest-Debug-02aa8e8e7210ce231d05.json","target-QuickTest-MinSizeRel-f12a38e2a8c7c1d0cb02.json","target-QuickTest-Release-83298b692081ff0fcf27.json","target-QuickTest-RelWithDebInfo-fe878c0200b6181c4746.json","target-ZERO_CHECK-Debug-36800e54d5ddac5bf6c1.json","target-ZERO_CHECK-MinSizeRel-36800e54d5ddac5bf6c1.json","target-ZERO_CHECK-Release-36800e54d5ddac5bf6c1.json","target-ZERO_CHECK-RelWithDebInfo-36800e54d5ddac5bf6c1.json","toolchains-v1-eda23bf84c60b4bc0df1.json"]
[cache] Reading CMake cache file c:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/build/CfgVS2019X64/CMakeCache.txt
[cache] Parsing CMake cache string
[cache] Reading CMake cache file c:/Work/Projects/CMakeTools/Test1.10/QuickStart1/out/build/CfgVS2019X64/CMakeCache.txt
[cache] Parsing CMake cache string
[cpptools] The build configurations generated do not contain the active build configuration. Using "Debug" for CMAKE_BUILD_TYPE instead of "null" to ensure that IntelliSense configurations can be found
[cpptools] The build configurations generated do not contain the active build configuration. Using "Debug" for CMAKE_BUILD_TYPE instead of "null" to ensure that IntelliSense configurations can be found

Expand CMakePresets.json
{
"version": 2,
"configurePresets": [
{
"name": "CfgVS2019X64",
"displayName": "CfgVS2019X64",
"description": "CfgVS2019X64",
"generator": "Visual Studio 16 2019",
"toolset": "host=x64",
"architecture": "x64",
"binaryDir": "${sourceDir}/out/build/${presetName}",
"environment": {
"MyEnv_Variable_CfgVS2019X64": "MyEnv_Value_CfgVS2019X64"
},
"cacheVariables": {
"CMAKE_BUILD_TYPE": "Debug",
"CMAKE_INSTALL_PREFIX": "${sourceDir}/out/install/${presetName}"
}
}
],
"buildPresets": [
{
"name": "BuildFromCfgVS2019X64",
"description": "BuildFromCfgVS2019X64",
"displayName": "BuildFromCfgVS2019X64",
"environment": {
"MyEnv_Variable_BuildFromCfgVS2019X64": "MyEnv_Value_BuildFromCfgVS2019X64"
},
"inheritConfigureEnvironment": true,
"configurePreset": "CfgVS2019X64"
}
],
"testPresets": [
{
"name": "TestFromCfgVS2019X64",
"description": "TestFromCfgVS2019X64",
"displayName": "TestFromCfgVS2019X64",
"environment": {
"MyEnv_Variable_TestFromCfgVS2019X64": "MyEnv_Value_TestFromCfgVS2019X64"
},
"inheritConfigureEnvironment": false,
"configurePreset": "CfgVS2019X64"
}
]
}

Can you also share the CMake: Log Diagnostics?  C/C++ has a command with a similar name, I'm looking for the CMake one.

Of course, I forgot about that one.

Expand CMake Log Diagnostics
{
"os": "win32",
"vscodeVersion": "1.63.2",
"cmtVersion": "1.10.0",
"configurations": [
{
"folder": "c:\Work\Projects\CMakeTools\Test1.10\QuickStart1",
"cmakeVersion": "3.21.3",
"configured": true,
"generator": "Visual Studio 16 2019",
"usesPresets": true,
"compilers": {}
}
],
"cpptoolsIntegration": {
"isReady": true,
"hasCodeModel": true,
"activeBuildType": "",
"buildTypesSeen": [
"Debug",
"Release",
"MinSizeRel",
"RelWithDebInfo"
],
"requests": [],
"responses": [],
"partialMatches": [],
"targetCount": 7,
"executablesCount": 1,
"librariesCount": 0,
"targets": [
{
"name": "ALL_BUILD",
"type": "UTILITY"
},
{
"name": "Continuous",
"type": "UTILITY"
},
{
"name": "Experimental",
"type": "UTILITY"
},
{
"name": "Nightly",
"type": "UTILITY"
},
{
"name": "NightlyMemoryCheck",
"type": "UTILITY"
},
{
"name": "QuickTest",
"type": "EXECUTABLE"
},
{
"name": "ZERO_CHECK",
"type": "UTILITY"
}
]
},
"settings": [
{
"communicationMode": "automatic",
"useCMakePresets": "always",
"configureOnOpen": true
}
]
}

mac also has this bug too

I am running into the same or a very similar error. Using Ubuntu with gcc, the CMake project uses a toolchain generated by Conan. I also am using CMake presets.
I install two configurations (Debug and Release) with Conan, the CMakePresets.json generated by Conan has two configurations:
    "configurePresets": [
        {
            "name": "Debug",
            "displayName": "Debug Config",
            "description": "Debug configure using 'Unix Makefiles' generator",
            "generator": "Unix Makefiles",
            "cacheVariables": {
                "CMAKE_POLICY_DEFAULT_CMP0091": "NEW",
                "CMAKE_BUILD_TYPE": "Debug"
            },
            "toolchainFile": "/home/chris/conantest/build/generators/conan_toolchain.cmake",
            "binaryDir": "/home/chris/conantest/cmake-build-debug"
        },
        {
            "name": "Release",
            "displayName": "Release Config",
            "description": "Release configure using 'Unix Makefiles' generator",
            "generator": "Unix Makefiles",
            "cacheVariables": {
                "CMAKE_POLICY_DEFAULT_CMP0091": "NEW",
                "CMAKE_BUILD_TYPE": "Release"
            },
            "toolchainFile": "/home/chris/conantest/build/generators/conan_toolchain.cmake",
            "binaryDir": "/home/chris/conantest/cmake-build-release"
        }
    ],
    "buildPresets": [
        {
            "name": "Debug",
            "configurePreset": "Debug"
        },
        {
            "name": "Release",
            "configurePreset": "Release"
        }
    ],

I've noticed that the cpptools warning always occurs when switching to a configuration that has not been built last. E.g. I configure "Debug", build "Debug", switch to "Release", then it would show

[cpptools] The build configurations generated do not contain the active build configuration. Using "Debug" for CMAKE_BUILD_TYPE instead of "Release" to ensure that IntelliSense configurations can be found

If I then build in Release mode and switch the config back to "Debug", it shows

[cpptools] The build configurations generated do not contain the active build configuration. Using "Release" for CMAKE_BUILD_TYPE instead of "Debug" to ensure that IntelliSense configurations can be found

Output of CMake: Log Diagnostics:
{
  "os": "linux",
  "vscodeVersion": "1.67.1",
  "cmtVersion": "1.10.0",
  "configurations": [
    {
      "folder": "/home/chris/conantest",
      "cmakeVersion": "3.23.1",
      "configured": true,
      "generator": "Unix Makefiles",
      "usesPresets": true,
      "compilers": {
        "CXX": "/usr/bin/c++"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Release"
    ],
    "requests": [
      "file:///home/chris/conantest/soxrtest.cpp"
    ],
    "responses": [
      {
        "uri": "file:///home/chris/conantest/soxrtest.cpp",
        "configuration": {
          "defines": [
            "_GLIBCXX_USE_CXX11_ABI=0",
            "NDEBUG"
          ],
          "includePath": [
            "/home/chris/.conan/data/soxr/0.1.3/_/_/package/fcf0f374adec7fe3c03d5a485bea5cbf91c66ab4/include"
          ],
          "compilerPath": "/usr/bin/c++",
          "compilerArgs": [
            "-m64",
            "-O3",
            "-DNDEBUG"
          ]
        }
      }
    ],
    "partialMatches": [],
    "targetCount": 1,
    "executablesCount": 1,
    "librariesCount": 0,
    "targets": [
      {
        "name": "soxrtest",
        "type": "EXECUTABLE"
      }
    ]
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": true
    }
  ]
}

I think the problem lies in
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Release"
    ],

The cpptools extension only seems to see the last-built build type but the active build type can be different.

I see this  behavior on Windows with MSVC / Ninja generator.
{
  "os": "win32",
  "vscodeVersion": "1.69.2",
  "cmtVersion": "1.11.26",
  "configurations": [
    {
      "folder": "c:\\Dev\\Projects\\Work\\XXXXXXXXX\\YYYYYYYYY-client",
      "cmakeVersion": "3.23.2",
      "configured": true,
      "generator": "Ninja",
      "usesPresets": true,
      "compilers": {
        "C": "C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.32.31326/bin/Hostx86/x64/cl.exe",
        "CXX": "cl.exe"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "",
    "buildTypesSeen": [
      "Debug"
    ],
    "requests": [
      "file:///c%3A/Dev/Projects/Work/XXXXXXXXX/YYYYYYYYY-client/src/Abc/TaAbcBrowserItem.cpp"
    ],
    "responses": [
      {
        "uri": "file:///c%3A/Dev/Projects/Work/XXXXXXXXX/YYYYYYYYY-client/src/Abc/TaAbcBrowserItem.cpp",
        "configuration": {
          "includePath": [
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/out/build/windows-debug/src",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/src",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/out/build/windows-debug/src/XXXXXXXXX_autogen/include",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/src/render",
            "c:/program files (x86)/intel/oneapi/vtune/2022.2.0/sdk/include",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/third-party/Abc-cmake/Abc_binary_95.7.18+g0d6005e+chromium-95.0.4638.69_windows64",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/third-party/Abc-cmake/include",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/gfxd3d11_test/source/engine",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/gfxd3d11_test/source/gui",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/gfxd3d11_test/source/math",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/gfxd3d11_test/source/test",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/gfxd3d11_test/source/util",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/gfxd3d11_test/source",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/external/source/freetype/include",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/external/source/freetype/include/freetype",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/coreplatform.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_environment.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_include.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_types.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_environment/arch/x86.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_environment/arch/x86_64.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_environment/compiler/clang.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_environment/compiler/gcc.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_environment/compiler/msvc.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_environment/os/linux.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include/avc/_platform/_environment/os/windesktop.h",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libavccore/include",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libgfxd3d11/include",
            "c:/dev/projects/work/XXXXXXXXX/YYYYYYYYY-client/submodules/dcn/libgfx/include",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include/qtcore",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/mkspecs/win32-msvc",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include/qtquick",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include/qtgui",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include/qtqml",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include/qtnetwork",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include/qtqmlmodels",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include/qtopengl",
            "c:/dev/projects/qt/6.2.0/msvc2019_64/include/qtquickcontrols2"
          ],
          "defines": [
            "Abc_MAJOR_VERSION=95",
            "Abc_MULTI_THREADED_MSG_LOOP=true",
            "Abc_OSR_ENABLED=true",
            "Abc_RESOURCE_DIR=\"C:/Dev/Projects/Work/XXXXXXXXX/YYYYYYYYY-client/web-root\"",
            "Abc_URI_ROOT=\"http://nc.XXXXXXXXX.io\"",
            "NOMINMAX",
            "QT_CORE_LIB",
            "QT_GUI_LIB",
            "QT_NETWORK_LIB",
            "QT_OPENGL_LIB",
            "QT_QMLMODELS_LIB",
            "QT_QML_DEBUG",
            "QT_QML_LIB",
            "QT_QUICKCONTROLS2_LIB",
            "QT_QUICK_LIB",
            "TA_Abc_DOM_LAYOUT_SYNC=false",
            "TA_Abc_JSBIND_LAYOUT_SYNC=true",
            "TA_CSV_TEST_DATA_PATH=\"C:/Dev/Projects/Work/XXXXXXXXX/YYYYYYYYY-client/data/tas_small.csv\"",
            "TA_PROFILE_LATENCY=false",
            "TA_USE_OLD_FLIP_MODEL=true",
            "UNICODE",
            "VTUNE_PROFILE",
            "WIN32",
            "WIN32_LEAN_AND_MEAN",
            "WIN64",
            "_ENABLE_EXTENDED_ALIGNED_STORAGE",
            "_UNICODE",
            "_WIN64",
            "__STDC_CONSTANT_MACROS",
            "__STDC_FORMAT_MACROS"
          ],
          "compilerPath": "c:/program files/microsoft visual studio/2022/community/vc/tools/msvc/14.32.31326/bin/hostx86/x64/cl.exe",
          "compilerArgs": [],
          "compilerFragments": [
            "/DWIN32 /D_WINDOWS /W3 /GR /EHsc /MDd /Zi /Ob0 /Od /RTC1",
            "/EHsc",
            "-Zc:__cplusplus",
            "-permissive-",
            "-utf-8",
            "-std:c++20"
          ]
        }
      }
    ],
    "partialMatches": [],
    "targetCount": 8,
    "executablesCount": 1,
    "librariesCount": 5,
    "targets": [
      {
        "name": "dll_wrapper",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "XXXXXXXXX",
        "type": "EXECUTABLE"
      },
      {
        "name": "XXXXXXXXX_autogen",
        "type": "UTILITY"
      },
      {
        "name": "XXXXXXXXX_autogen_timestamp_deps",
        "type": "UTILITY"
      },
      {
        "name": "freetype",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "gfxd3d11_test",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "libgfx",
        "type": "STATIC_LIBRARY"
      },
      {
        "name": "libgfxd3d11",
        "type": "STATIC_LIBRARY"
      }
    ]
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": false
    }
  ]
}

I solved the issue by calling cmake -DCMAKE_BUILD_TYPE=Debug <cmakelist_folder> because the variable was not set before (despite building with VSCode). You can also edit it visually with cmake.
With this, it worked as expected.

Same issue. Windows, CMake tools, Ninja.
Couldn't get @1621 's solution to work -DCMAKE_BUILD_TYPE=Debug seems to have no effect for me.

I meet same issue on ubuntu/gcc, in my case, the problem is caused by 2 line in CMakeLists.txt which defined different BUILD_TYPE again.
set(CMAKE_BUILD_TYPE Release)
set(CMAKE_CXX_FLAGS "-std=c++14 -O3 -DMINIGLOG=ON"),
vscode worked as expected after comment those two lines

This is still an issue as of today, with DEBUG I am still getting this warning message and most importantly th e debug buttion isn't working because of this (https://github.com/microsoft/vscode-cmake-tools/issues/1412), people, including me, have fixed the debug button issue by changing DEBUG to Debug.

Hi, I'm also facing this issue on macOS,

here is the diagnostics log
{
  "os": "darwin",
  "vscodeVersion": "1.78.0",
  "cmtVersion": "1.14.31",
  "configurations": [
    {
      "folder": "/Users/***/***",
      "cmakeVersion": "3.25.0",
      "configured": true,
      "generator": "Xcode",
      "usesPresets": true,
      "compilers": {}
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "",
    "buildTypesSeen": [
      "Debug",
      "Release",
      "MinSizeRel",
      "RelWithDebInfo"
    ],
    "requests": [],
    "responses": [],
    "partialMatches": [],
    "targetCount": 75,
    "executablesCount": 9,
    "librariesCount": 25,
    "targets": []
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": false
    }
  ]
}

I've already built the solution from the terminal using cmake --preset <preset_name>, so CMake cache is already populated, but I'm still getting this warning.
If it helps,

here is the relevant part of my `CMakePresets.json`
{
  "version": 6,
  "cmakeMinimumRequired": {
    "major": 3,
    "minor": 25,
    "patch": 0
  },
  "configurePresets": [
    {
      "name": "common",
      "hidden": true,
      "binaryDir": "${sourceDir}/build/${presetName}",
      "warnings": {
        "dev": true,
        "uninitialized": true,
        "unusedCli": true
      }
    },
    {
      "name": "macos",
      "hidden": true,
      "generator": "Xcode",
      "cacheVariables": {
        "CMAKE_OSX_ARCHITECTURES": "arm64;x86_64"
      },
      "condition": {
        "type": "equals",
        "lhs": "${hostSystemName}",
        "rhs": "Darwin"
      }
    },
    {
      "name": "debug",
      "hidden": true,
      "cacheVariables": {
        "CMAKE_BUILD_TYPE": "Debug",
        "CMAKE_CXX_FLAGS": "-DDEBUG_CONFIG",
        "DEBUG_CONFIG": "TRUE"
      }
    },
    {
      "name": "macos-debug",
      "displayName": "macOS-Debug",
      "description": "Debug configuration intended for day-to-day development",
      "inherits": [
        "common",
        "macos",
        "debug"
      ]
    }
  ],
  "buildPresets": [
    {
      "name": "macos-debug",
      "displayName": "macOS-Debug",
      "description": "Debug configuration intended for day-to-day development",
      "configurePreset": "macos-debug"
    }
  ]
}

Thanks!

Fix is merged in and should be included in the 1.15 release.

Fix is merged in and should be included in the 1.15 release.
I still meet this warning with v1.15.31

[cpptools] The build configurations generated do not contain the active build configuration. Using "Release" for CMAKE_BUILD_TYPE instead of "Debug" to ensure that IntelliSense configurations can be found

@andreeis still seeing this using v1.17.16. Am I doing something wrong?
CMakePresets.json:
{
  "version": 6,
  "configurePresets": [
    {
      "name": "ninja-multi-vcpkg",
      "hidden": true,
      "generator": "Ninja Multi-Config",
      "binaryDir": "${sourceDir}/out/build/${presetName}",
      "installDir": "${sourceDir}/out/install/${presetName}",
      "toolchainFile": "$env{VCPKG_ROOT}/scripts/buildsystems/vcpkg.cmake",
      "architecture": {
        "value": "x64",
        "strategy": "external"
      },
      "cacheVariables": {
        "VCPKG_HOST_TRIPLET": "${presetName}",
        "VCPKG_TARGET_TRIPLET": "${presetName}"
      }
    },
    {
      "name": "static",
      "hidden": true,
      "cacheVariables": {
        "RLS_STATIC": "ON"
      }
    },
    {
      "name": "x64-mingw-static",
      "description": "MinGW64 w/static linkage",
      "inherits": [
        "ninja-multi-vcpkg",
        "static"
      ]
    },
    {
      "name": "x64-windows-static",
      "description": "MSVC w/static linkage",
      "inherits": [
        "ninja-multi-vcpkg",
        "static"
      ]
    }
  ],
  "buildPresets": [
    {
      "name": "Debug",
      "hidden": true,
      "configuration": "Debug"
    },
    {
      "name": "MinSizeRel",
      "hidden": true,
      "configuration": "MinSizeRel"
    },
    {
      "name": "Release",
      "hidden": true,
      "configuration": "Release"
    },
    {
      "name": "x64-mingw-static-debug",
      "configurePreset": "x64-mingw-static",
      "description": "MinGW64 Debug w/static linkage",
      "inherits": [
        "Debug"
      ]
    },
    {
      "name": "x64-mingw-static-minsizerel",
      "configurePreset": "x64-mingw-static",
      "description": "MinGW64 MinSizeRel w/static linkage",
      "inherits": [
        "MinSizeRel"
      ]
    },
    {
      "name": "x64-mingw-static-release",
      "configurePreset": "x64-mingw-static",
      "description": "MinGW64 Release w/static linkage",
      "inherits": [
        "Release"
      ]
    },
    {
      "name": "x64-windows-static-debug",
      "configurePreset": "x64-windows-static",
      "description": "MSVC Debug w/static linkage",
      "inherits": [
        "Debug"
      ]
    },
    {
      "name": "x64-windows-static-minsizerel",
      "configurePreset": "x64-windows-static",
      "description": "MSVC MinSizeRel w/static linkage",
      "inherits": [
        "MinSizeRel"
      ]
    },
    {
      "name": "x64-windows-static-release",
      "configurePreset": "x64-windows-static",
      "description": "MSVC Release w/static linkage",
      "inherits": [
        "Release"
      ]
    }
  ]
}

Output:
[cpptools] The build configurations generated do not contain the active build configuration. Using "Debug" for CMAKE_BUILD_TYPE instead of "MinSizeRel" to ensure that IntelliSense configurations can be found

Update: This only happens for MinSizeRel.

Bug still here, and IntelliSense was completely borken.


Beautify error on macOS Sierra: Can't locate YAML/Tiny.pm

Description
Beautify fails to run on my macOS Sierra machine.
Code used & Steps to Reproduce
I stored the following as test.tex and ran Atom Beautify: Beautify Editor
\begin{center}
\begin{Large}
\bf Big Text
\end{Large}
\end{center}

The error I receive is the following
Can't locate YAML/Tiny.pm in @INC (you may need to install the YAML::Tiny module) (@INC contains: /Library/Perl/5.18/darwin-thread-multi-2level /Library/Perl/5.18 /Network/Library/Perl/5.18/darwin-thread-multi-2level /Network/Library/Perl/5.18 /Library/Perl/Updates/5.18.2 /System/Library/Perl/5.18/darwin-thread-multi-2level /System/Library/Perl/5.18 /System/Library/Perl/Extras/5.18/darwin-thread-multi-2level /System/Library/Perl/Extras/5.18 .) at /Library/TeX/texbin/latexindent line 39. BEGIN failed--compilation aborted at /Library/TeX/texbin/latexindent line 39.

Debug
Here is a link to the debug.md Gist: https://gist.github.com/birnstiel/3791b54c1acb0884d40becf2e26a51c7
Checklist
I have checked all the boxes in the checklist.

I have the same error on macOS Sierra. Has anyone come up with a solution?

I got it working, but it might be longer than you are interested in.
sudo cpan Unicode::GCString
sudo cpan App::cpanminus
sudo cpan YAML::Tiny
sudo perl -MCPAN -e 'install "File::HomeDir"'

You may not need all of them. I got this (the last three lines with my edit of the cpanm typo) from https://github.com/ketan/BeautifyLatex
I'd suggest looking at those.
Now, to get those lines to work, my gzip was broken and I had to install it. I did so with my MacPorts installation
I will try to answer questions, but I have no idea why these work.  I was just following instructions, then noting the error that stated that I might need to install Unicode::GCString when perl latexindent executed in the directory where latexindent is located failed.

Yesss, this worked for me. I used all 4, I needed at least the Unicode::GCString and the YAML::Tiny, not sure if the others were necessary.

On Sep 4, 2017, at 9:56 PM, Joseph C. Slater<EMAIL_ADDRESS>wrote:
I got it working, but it might be longer than you are interested in.
sudo cpan Unicode::GCString
sudo cpan App::cpanminus
sudo cpan YAML::Tiny
sudo perl -MCPAN -e 'install "File::HomeDir"'
You may not need all of them. I got this (the last three lines with my edit of the cpanm typo) from https://github.com/ketan/BeautifyLatex https://github.com/ketan/BeautifyLatex
I'd suggest looking at those.
Now, to get those lines to work, my gzip was broken and I had to install it. I did so with my MacPorts installation
I will try to answer questions, but I have no idea why these work. I was just following instructions, then noting the error that stated that I might need to install Unicode::GCString when perl latexindent executed in the directory where latexindent is located failed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/Glavin001/atom-beautify/issues/1792#issuecomment-327071117, or mute the thread https://github.com/notifications/unsubscribe-auth/ABtkWVnBUgXPFn4R35Qq7mdzSo2tSGLiks5sfNRzgaJpZM4OoOx7.

You have no idea how lucky you were that this unknowledgeable hacker lucked upon a solution! I just got lucky somehow. Glad you have it now.

@josephcslater Thank you so much. I solved my problem following your advice.

Sadly, I am getting the same error, even after executing the cpan commands above.
[13:15:06] Formatting failed with exit code 2
[13:15:06] stderr: Can't locate YAML/Tiny.pm in @INC (you may need to install the YAML::Tiny module) (@INC contains: /usr/local/texlive/2017/texmf-dist/scripts/latexindent /Library/Perl/5.18/darwin-thread-multi-2level /Library/Perl/5.18 /Network/Library/Perl/5.18/darwin-thread-multi-2level /Network/Library/Perl/5.18 /Library/Perl/Updates/5.18.2/darwin-thread-multi-2level /Library/Perl/Updates/5.18.2 /System/Library/Perl/5.18/darwin-thread-multi-2level /System/Library/Perl/5.18 /System/Library/Perl/Extras/5.18/darwin-thread-multi-2level /System/Library/Perl/Extras/5.18 .) at /usr/local/texlive/2017/texmf-dist/scripts/latexindent/LatexIndent/GetYamlSettings.pm line 20.
BEGIN failed--compilation aborted at /usr/local/texlive/2017/texmf-dist/scripts/latexindent/LatexIndent/GetYamlSettings.pm line 20.
Compilation failed in require at /usr/local/texlive/2017/texmf-dist/scripts/latexindent/LatexIndent/LogFile.pm line 19.
BEGIN failed--compilation aborted at /usr/local/texlive/2017/texmf-dist/scripts/latexindent/LatexIndent/LogFile.pm line 19.
Compilation failed in require at /usr/local/texlive/2017/texmf-dist/scripts/latexindent/LatexIndent/Document.pm line 25.
BEGIN failed--compilation aborted at /usr/local/texlive/2017/texmf-dist/scripts/latexindent/LatexIndent/Document.pm line 25.
Compilation failed in require at /Library/TeX/texbin/latexindent line 27.
BEGIN failed--compilation aborted at /Library/TeX/texbin/latexindent line 27.

Any clue what I can do now? Perl 5.18, macOS Sierra 10.12.6.

The first line looks like the clue. Tiny.pm isn't installed. Keep in mind, the commands above are specific to my system. Look for your installation of cpan and make sure that the one on your path is running.
Further: don't give me too much credit. I have no idea what the black magic is that makes this all work. I just got luck and figured this out. It was close to a miracle that I did.

Hey, somehow I got it fixed too now, but I have not much clue as how I did it.
In total I ran:
sudo cpan Unicode::GCString
sudo cpan App::cpanminus
sudo cpan YAML::Tiny
sudo perl -MCPAN -e 'install "File::HomeDir"'

sudo /usr/bin/cpan5.18 Unicode::GCString
sudo /usr/bin/cpan5.18 App::cpanminus
sudo /usr/bin/cpan5.18 YAML::Tiny
sudo /usr/bin/perl5.18 -MCPAN -e 'install "File::HomeDir"'

But after that it still gave me errors.
From https://github.com/James-Yu/LaTeX-Workshop/issues/376#issuecomment-381274613 I ran:
sudo cpan Log::Log4perl
sudo cpan Log::Dispatch

Then, from https://github.com/ketan/BeautifyLatex, I ran:
$ sudo cpan App::cpanminus
$ sudo cpan YAML::Tiny
$ sudo perl -MCPAN -e 'install "File::HomeDir"'

and now it works. I have no clue why.
Thanks @josephcslater for trying to help though :)

I really appreciate you posting what you did. Humorously, I had this problem again, forgot my solution, googled it, and found my post.  Glad it works.

I had the errors discussed above and installed all the suggested cpan packages. Now I get the following problem:
Cannot write to 'indent.log': Permission denied at /Library/Perl/5.18/Log/Dispatch/File.pm line 100.

I don't know how it all works, but it seems like it's trying to write the file "indent.log" to a location where you are not allowed to. I don't have Log (the directory) on my machine. You might want to look at line 100 of FIle.pm and see where it's trying to write.

Log4perl hasn't been required since 2021 :)
All contributions to the project welcome :)
Chris (author of latexindent)

The easiest way to get latexindent work on macOS is through brew install latexindent.


change double ellipsis to single, see issue #88

PR for style issue in #88

LGTM, thanks for your contribution.


Add support for longer domain names in nginx_proxy

Fixes #243
Currently, server_names_hash_bucket_size is set to 32, which is fine in most cases but prevents longer domain names from working. In my case, I ran into the need to increase the size when creating a  server_name like the following: subdomain.mydomain.duckdns.org

Please update the changelog and pump the version +0.1.


Equalizer: Height equalisation only occurs developer tools are open

Height equalisation only occurs developer tools are open in any browser.

Chrome, FireFox, and Safari, no dev tools. Seems to be working fine. Do you have JavaScript disabled for some reason?

I do not. I've seen similar posts on the Foundation Forum without response. Here is a video example on some tabs. However the bug is not limited to just tabs.
https://www.dropbox.com/s/tsbid2li4jjw60x/equalizer.mov?dl=0

Just updated to the latest version of Foundation 6 and this is even buggier than before. Applying height 0px the majority of the time.

Solved this issue. It was due to me fading elements in and it calculating the height during the fade-in which results in it calculating a height of 0. Any ideas how I can still fade my elements in without this being an issue?


Validate image dimensions

Current dependencies on/for this PR:

main

PR #534   👈

This stack of pull requests is managed by Graphite.


ASH26 Amcrest Security/Flood Light

``Is your feature request related to a problem? Please describe.
'Illuminator' is not discovered on set up.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
Add a "advanced" mode to allow users to select their own lights as a catch-all for such circumstances.
Additional context
I already have this set up using shell commands, but for whatever reason they are not very reliable on my machine via HA.
For this particular camera/light the API does not return the white light correctly. See below.
For my unit:
Lighting_V2[0][0][1]
is the flood light controller
where as the api returns
Lighting_V2[0][2][1]
which does nothing (that i can see anyway)
Also the integration does not even pick anything up that is a light apart from the IR
Command:
http://floodlight.lan/cgi-bin/configManager.cgi?action=getConfig&name=Lighting_V2
Response:
table.Lighting_V2[0][0][0].Correction=50
table.Lighting_V2[0][0][0].LightSwitchDelay=0
table.Lighting_V2[0][0][0].LightType=InfraredLight
table.Lighting_V2[0][0][0].MiddleLight[0].Angle=50
table.Lighting_V2[0][0][0].MiddleLight[0].Light=50
table.Lighting_V2[0][0][0].Mode=Auto
table.Lighting_V2[0][0][0].Sensitive=3
table.Lighting_V2[0][0][1].Correction=50
table.Lighting_V2[0][0][1].LightSwitchDelay=0
table.Lighting_V2[0][0][1].LightType=WhiteLight
table.Lighting_V2[0][0][1].Mode=Off
table.Lighting_V2[0][0][1].NearLight[0].Angle=50
table.Lighting_V2[0][0][1].NearLight[0].Light=50
table.Lighting_V2[0][0][1].Sensitive=3
table.Lighting_V2[0][1][0].Correction=50
table.Lighting_V2[0][1][0].LightSwitchDelay=0
table.Lighting_V2[0][1][0].LightType=InfraredLight
table.Lighting_V2[0][1][0].MiddleLight[0].Angle=50
table.Lighting_V2[0][1][0].MiddleLight[0].Light=50
table.Lighting_V2[0][1][0].Mode=Auto
table.Lighting_V2[0][1][0].Sensitive=3
table.Lighting_V2[0][1][1].Correction=50
table.Lighting_V2[0][1][1].LightSwitchDelay=0
table.Lighting_V2[0][1][1].LightType=WhiteLight
table.Lighting_V2[0][1][1].Mode=Off
table.Lighting_V2[0][1][1].NearLight[0].Angle=50
table.Lighting_V2[0][1][1].NearLight[0].Light=50
table.Lighting_V2[0][1][1].Sensitive=3
table.Lighting_V2[0][2][0].Correction=50
table.Lighting_V2[0][2][0].LightSwitchDelay=0
table.Lighting_V2[0][2][0].LightType=InfraredLight
table.Lighting_V2[0][2][0].MiddleLight[0].Angle=50
table.Lighting_V2[0][2][0].MiddleLight[0].Light=50
table.Lighting_V2[0][2][0].Mode=Auto
table.Lighting_V2[0][2][0].Sensitive=3
table.Lighting_V2[0][2][1].Correction=50
table.Lighting_V2[0][2][1].LightSwitchDelay=0
table.Lighting_V2[0][2][1].LightType=WhiteLight
table.Lighting_V2[0][2][1].Mode=Off
table.Lighting_V2[0][2][1].NearLight[0].Angle=50
table.Lighting_V2[0][2][1].NearLight[0].Light=50
table.Lighting_V2[0][2][1].Sensitive=3

I found what appears to be the code block that is stopping the light from being discovered
custom_components/dahua/init.py Line 482
    def supports_illuminator(self) -> bool:         """         Returns true if this camera has an illuminator (white light for color cameras).  For example, the         IPC-HDW3849HP-AS-PV does         """         return "table.Lighting_V2[{0}][0][0].Mode".format(self._channel) in self.data
This could also assist with this question from #52
I can try and stab at it myself, but I've never made an integration before and a lot of this code is bigger than anything I've ever made.
I'll see if I can through together a method similar to the doorbell check using the ASH model until something better can be put together by someone smarter.

I've started to work on this. This is what it'll look like. The options will be: Off, On, Strobe.
This seem OK? I should have this done tomorrow.

The security light feature is released in https://github.com/rroller/dahua/releases/tag/0.9.28

Resolving this issue now that the security light (illuminator) is now supported with this integration. Please reopen if you have any issues.

WOW! great work! thank you!

Just set up my Amcrest floodlight using this integration and I’m not getting the Illuminator toggle. Is there any additional setup needed?

The main main integration currently does not support Amcrest Floodlights, try using PR 141


GDC Leaderboard tasks

[x]  Add endpoint to delete based on name or email
[x] Host API
[x] Host SPA - https://sentaur-survivor.com/
[x] Fork this repo and leaderboard into sentry-demos
[x] https://github.com/sentry-demos/sentaur-leaderboard
[x] https://github.com/sentry-demos/sentaur-survivor
[x] Upload debug symbols API (GCP cloud build)
[x] Upload debug symbols SPA (GHA build)
[ ] Sentry tracing (works locally but not on GCP?)
[ ] Bump Unity SDK with tracing fix, update game
[X] Authentication of POST
[x] Add repos to GitHub integration and code mappings (done)
[ ] Set up suspect commits
[ ] Change sqlite to postgres

Code changes are trivial, it's more about hosting

[ ] Endpoint/querystring that returns broken JSON on the AntiCheat project
Something like exiting early before closing the json array:

        if (context.Request.Query["game-over"].FirstOrDefault() is not null)
        {
            _logger.LogInformation("Game play ended!");
            return;
        }
        // here it writes the end of the JSON object so we're bailing early

Stretch goal:
Endpoint that runs the raffle with the following logic:
everyone who plays get at least 1 entry
top players #6-10 gets 2 entries
top players $3-5 gets 3 entries
player #2 gets 4 entries
player #1 gets 5 entries

Stack trace linking doesn't seem to work:

https://github.com/getsentry/sentry/issues/67107


remake overlay

The current status is, that the overlay is moveing in front of the player with the player as canvas object.
The idea is to load another scene over the game scene.
Storypoints: 1
DoD:
The overlay should be a seperate scene and not inside the game scene.

Replaced by https://github.com/Gamify-IT/issues/issues/44.


Fix incompatibility with oauth2client v2.0.0

Several bits moved to contrib subpackage of oauth2client

Closed? What happened?

There was just more to it


feat: Add Livepeer Image Provider

Relates to:

Risks
Low, only effects users using the new Livepeer provider.

Background
What does this PR do?
Adds Livepeer as a model provider for image generation.
In a separate PR we will be adding the LLM generation for Livepeer provider as well, this is a clean separation with for image gen for now.
What kind of change is this?
Feature that adds functionality, non-breaking.

Documentation changes needed?
Yes, I have a commit with doc changes ready. Will push them after this PR for correct API doc links.

Testing
Where should a reviewer start?
Detailed testing steps

Install and build from scratch to ensure no build errors. There are no new packages added with Livepeer.

Add a free gateway into the .env under LIVEPEER_GATEWAY_URL=
Here is one for testing https://gateway.livepeer-eliza.com

Set IMAGE_GEN= to TRUE in the .env

Add "imageModelProvider": "livepeer" to your character file.

Run start your character and open up the dialog box with pnpm start:client

Ask it to generate an image, it will show up in the eliza/agent/generatedImages/ folder

Credits
Credit to https://github.com/UD1sto/ (ElizaOS contributor) for doing most the work.

So sick!


Added check for -g and -gu for windows platform

@hpohekar Unfortunately e.g., s=pf.launch_fluent(mode="solver", show_gui=True, additional_arguments="-g") is still allowed and it starts in -g mode. The check needs to be more comprehensive.

@hpohekar Unfortunately, e.g., s=pf.launch_fluent(mode="solver", show_gui=True, additional_arguments="-g") is still allowed and it starts in -g mode. The check needs to be more comprehensive.

Done. Thank you.

As per previous comment. Perhaps we could also add a test for the expected behaviour.

Done. Thank you.

@hpohekar, please look at the current implementation. @seanpearsonuk, the tests should run locally without any issues, however though we have a case that should launch fluent in '-g' mode in linux as well. Let's see if the tests behave as we expect them to :).

Yes, looks good. Thank you.


fix: wait for healthy database on squash

What kind of change does this PR introduce?
Bug fix https://github.com/supabase/cli/issues/2071
What is the new behavior?
Oversight when starting shadow db.
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 57.74%

Files with Coverage Reduction
New Missed Lines
%

internal/gen/keys/keys.go
5
11.76%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
6386

Relevant Lines:
11060

💛  - Coveralls


add netdata demo site

This PR will cause prometheus to scrape every server from my-netdata.io demo sites every 60 seconds.
Basically it is a demo of this tutorial.
@ktsaou can I connect cloudalchemy demo site with my-netdata.io ?

sure, of course...

Thanks!


net: tracing: fix sys_track_socket_init() declaration

Function declaration does not match definition causing a compilation error when CONFIG_TRACING_OBJECT_TRACKING is enabled.

@jukkar Could you take a look at this?  Seems to be a compilation issue added by 7bb4013d8e378df4605183dac48fd339f111dc5d
I can reproduce this with the config options:
CONFIG_TRACING=y
CONFIG_TRACING_CTF=y
CONFIG_TRACING_BACKEND_RAM=y
CONFIG_TRACING_OBJECT_TRACKING=y


I can't uninstall gomon.

What OS do you use? If Windows, you can confirm where is gomon.exe via where gomon. If you want to uninstall, just remove it.

If Linux or OSX, which gomon.


rename from humantime_to_duration to parse_datetime

@Benjscho WDYT?

I fear this destroyed the auto update. See my comment.
Also installation fails now:
╰─> cargo uninstall coreutils
    Removing C:\Users\xxxxx\.cargo\bin\coreutils.exe
╰─> cargo install coreutils
    Updating crates.io index
  Installing coreutils v0.0.19
    Updating crates.io index
error: failed to compile `coreutils v0.0.19`, intermediate artifacts can be found at `C:\Users\xxxxx\AppData\Local\Temp\cargo-installlPgsr5`

Caused by:
  no matching package named `humantime_to_duration` found
  location searched: registry `crates-io`
  required by package `uu_date v0.0.19`
      ... which satisfies dependency `date = "^0.0.19"` of package `coreutils v0.0.19`

I don't think it is related. I think it is because I yanked the crate.
I revert it, could you please try again?
https://crates.io/crates/humantime_to_duration/0.3.1

Yeah that fixed it:
   Installed package `coreutils v0.0.19` (executable `coreutils.exe`)


[HOLD for payment 2023-09-06] [HOLD for payment 2023-09-04] [$1000] Web - Request a money - Clicking on the avatar open a wrong profile

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open a chat room from LHN
request a money
hover the avatar and click to open the profile

Expected Result:
the profile should be correct
Actual Result:
the wrong profile is opened
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: v1.3.52-5
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/94339432-2d48-47db-a07b-ff74c0b01c05
https://github.com/Expensify/App/assets/115492554/5e30a169-da96-47fc-a1a2-e23620377520
Expensify/Expensify Issue URL:
Issue reported by: @misgana96
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691692716326279
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01bdaad0efa1ea99ef
Upwork Job ID:<PHONE_NUMBER>761824768
Last Price Increase: 2023-08-13
Automatic offers:

spcheema | Contributor | 26150022

Proposal
Please re-state the problem that we are trying to solve in this issue.
Clicking on the avatar opens a different profile.
What is the root cause of that problem?
In ReportActionItemSingle the MultipleAvatars component is inside a PressableWithoutFeedback even if you click outside the avatars you get the same result because it always calls showActorDetailswhich uses actorAccountID and in this case, we could use secondaryUserDetails information.
What changes do you think we should make in order to solve the problem?

Implement same as in group header which only shows the tooltips. We could disable the pressable if there is more than 1 actor in the action e.g. IOU. Include in shouldDisableDetailPage the validation of displayAllActors to avoid pressable.
Do nothing, this seems to be a desired behavior

What alternative solutions did you explore? (Optional)

I feel like if we fix this we should fix it everywhere at once if possible. For example I'd expect to open up the correct profile depending on the avatar I click in the header of a request too

Cool, I think I'd expect to open a profile anytime I click an avatar but that conversation can be had elsewhere

Lets go ahead and get this case fixed!

@MitchExpensify should we create a thread in slack to discuss the expected behavior of this case? Just so we can focus the proposal in one of the alternatives.

Thanks for the information @MitchExpensify updated my proposal for solving this interaction. A solution that could be used in other components an that is incremental to avoid regressions

Proposal from @daordonez11 looks good to me https://github.com/Expensify/App/issues/24389#issuecomment-1673904083 - deep implementation can be discussed during code check
🎀 👀 🎀 C+ reviewed

Ok ok - @pecanoro based on the history of proposals:

@daordonez11 was first who identified the root case of the issue
Both main ideas of the proposal were correct to fix - but after slack discussion decision was made to fix in different manner
@spcheema added Optional solution in his proposal (which potentially will fix the issue) - before we get confirmation how exactly issue should be fixed

I reviewed the whole conversation and the proposal and I actually think we should fix MultipleAvatars to always show the participant list. There is no point in solving this bug and then having this potential bug in other places or not having multiple avatars open the page in other cases like the IOU request.

Thanks for clearing it out @pecanoro we can discuss that in the PR so we can make it generic for participantlist or specific actor! Agree with @narefyev91 to focus on specific interactions directly on the PR. Will wait for the engineer review to discuss details of implementation and wait for assignation.

Yes, I want to make it consistent, I think clicking multiple avatars should open this view, the same as we do for group chats:

For sure! Regarding my proposal we can use all the handlers and let the parent component decide for example with a Boolean property in MultipleAvatars: showParticipants, if we want to show it always we can default it as true and disable it in specific parents or we want to change it gradually default false and send true in this case. Finally we have to remove the Pressable parent component in all the cases that it applies.
Ps: will update my proposal with this idea.

@pecanoro if we decide to move with opening right menu - when we click on multiple avatars - i will suggest to move forward with @spcheema proposal - https://github.com/Expensify/App/issues/24389#issuecomment-1674071628 - his main idea was to implement as you expected

Yeah agree with @narefyev91  @spcheema was the first to propose using the participants as generic solution also I would recommend adding a handler so it can be reused in MultipleAvatars instead of only ReportActionItemSingle as currently proposed.

Ok, awesome! Assigning @spcheema to the issue!

@spcheema Yeah, in that case, since there is only "one" direct participant, let's show the user profile, I think that is a great idea.

Payment summary:
Reporter: $250 misgana96 (Upwork)
C: $1000 @spcheema (Upwork)
C+: $1000 @narefyev91 (Upwork)

Payment summary:
Reporter: $250 misgana96 (Upwork) C: $1000 @spcheema (Upwork) C+: $1000 @narefyev91 (Upwork)

Hey @MitchExpensify! I'm from Callstack - no needs for payment in Upwok :-)

Payment summary:
Reporting: @misgana96 $250 (Upwork)
C: @spcheema $1000 (Upwork)
C+: @narefyev91 $1000 (Upwork)

Bump on the BZ steps in the meantime @narefyev91 👍

The PR that introduced the bug has been identified. Link to the PR - it was a new implementation - in that case we do not have any regression PR
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment - no comments
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion - no discussions
Determine if we should create a regression test for this bug - no regression test needed - we covered a lot during working on that issue

Payment summary:
Reporting: @misgana96 $250 (Upwork) C: @spcheema $1000 (Upwork) C+: @narefyev91 $1000 (Upwork)
Also worth mentioning - @narefyev91 does not require payment (Contractor)

Paid @spcheema
Offer sent for payment @misgana96

I realize I issued payment too early, my mistake. Hopefully no regressions occur and we can sort out anything after the fact. Sorry about that!

@MitchExpensify This PR had a regression, so the amounts are a bit off 🙈

Gah, thanks @pecanoro. Just my luck that the only issue I've ever paid too early had a regression and the payment was wrong 😆
@spcheema yes if you could refund while I sort this out that would be great. Sorry for the bother 🙇

Isn’t regression considered on prod?🧐 or for issues/bugs?

I'm not sure I follow this question. Mind rephrasing?
Seeing as we reduce C and C+ payment by 50% for regressions, and this issue had this regression, the updated payment summary is:
Reporting: @misgana96 $250 (Upwork)
C: @spcheema $500 (Upwork)
C+: @narefyev91 $500 (Upwork)

Isn’t regression considered on prod?🧐 or for issues/bugs?

It can be either, dev, stag or prod as long as the bug wasn't caught during the PR review process.

Paid according to this update! Thanks everyone

Accepted. Thanks @MitchExpensify


Error: ENOENT: no such file or directory, open '/c:/Users/anesingh/Desktop/ProjectName/DEV/CSDEV/Apex.log'

Getting this Error when right clicked on log and selected Show log Analysis
Machine OS : - Windows 10
Vs code version :- Recent

Duplicate of #4

This has been fixed in 1.3.4 so I will close.


Fix coverage - exclude typetest.py file from coverage reporting

Coverage increased (+7.5%) to 100.0% when pulling 7bc79c99538018d9c852353422f26cd496bc1be9 on 7-1-fix-coverage-excluded-files into 8b55e8c7bde22da5a36a63702c60abb28acc0b0f on 7-change-result-type-order.


[AJ-1472] Handle non-JSON error responses from create workspace API

If the create workspace endpoint returns a non-JSON error response, then the NewWorkspaceModal gets stuck displaying the loading animation/message forever.
A bug report from a user suggests that this may be happening sometimes.
This handles non-JSON error responses and shows "Unknown error." in that case.

Ignoring the failed end to end test... it timed out creating an Azure cloud environment, which is unrelated to this.


[BEAM-2195] support conditional operators

Support conditional operators(CASE, NULLIF, COALESCE).
@XuMingmin can you please take a look?

R: @XuMingmin
R: @jbonofre

Changes Unknown when pulling 302117400fa309bb4e136b225dacd1f2cba37749 on xumingming:BEAM-2195-support-conditional-operators into ** on apache:DSL_SQL**.

Merged, you can close this PR. Thanks !

Changes Unknown when pulling 302117400fa309bb4e136b225dacd1f2cba37749 on xumingming:BEAM-2195-support-conditional-operators into ** on apache:DSL_SQL**.


Setup CI/CD.

AC:

Automatic deploy to staging and prod envs in firebase on merge of PR
basic test setup done. (If there are tests then they should be run)

Ich denke, hier können wir mit 5Minds unterstützen.

IIUC ist https://github.com/ImmunHelden/ImmunHelden.de/pull/54 der erste Schritt hier.
@c0un7-z3r0 ist das noch Todo / In Progress? Wenn fertig dann gern Rebase & Merge.
Ich kann gern testen, aber sonst selbst leider nicht viel beitragen.

@weliveindetail currently we do not have manual deploys with github actions yet. So I suggest to go the GitFlow way as described here. https://datasift.github.io/gitflow/IntroducingGitFlow.html
So meaning on develop branch we merge the PRs this is getting deployed to the dev envs.
Then when we want to deploy to production a new feature we can do this by merging develop into master. Would right now probably skip the release branch idea just to keep it simple.


Combine work-request errors into single reconcileError event.

Combine work-request errors into single reconcileError event so that processing of this single recent event would provide information about the status of the machine.
Related Fixes #383

The change is only the second commit, the previous commit are already merged into main branch. The output of unittests:

make test
fatal: No names found, cannot describe anything.
GOBIN=/home/opc/cluster-api-provider-oci/hack/tools/bin ./scripts/go_install.sh sigs.k8s.io/controller-runtime/tools/setup-envtest setup-envtest v0.0.0-20230131074648-f5014c077fc3
kube-builder assets: /home/opc/.local/share/kubebuilder-envtest/k8s/1.24.2-linux-amd64
KUBEBUILDER_ASSETS="/home/opc/.local/share/kubebuilder-envtest/k8s/1.24.2-linux-amd64" go test -coverprofile=coverage.out ./...
?       github.com/oracle/cluster-api-provider-oci      [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/config [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/metrics        [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks    [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/base  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/base/mock_base        [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute       [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement     [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/computemanagement/mock_computemanagement      [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine       [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/containerengine/mock_containerengine  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity      [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity        [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/loadbalancer/mock_lb  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/workrequests  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/workrequests/mock_workrequests        [no test files]
?       github.com/oracle/cluster-api-provider-oci/feature      [no test files]
?       github.com/oracle/cluster-api-provider-oci/version      [no test files]
ok      github.com/oracle/cluster-api-provider-oci/api/v1beta1  92.555s coverage: 23.4% of statements
ok      github.com/oracle/cluster-api-provider-oci/api/v1beta2  0.053s  coverage: 14.6% of statements
ok      github.com/oracle/cluster-api-provider-oci/cloud/ociutil        0.025s  coverage: 15.9% of statements
ok      github.com/oracle/cluster-api-provider-oci/cloud/scope  22.261s coverage: 76.1% of statements
ok      github.com/oracle/cluster-api-provider-oci/cloud/util   0.748s  coverage: 61.1% of statements
ok      github.com/oracle/cluster-api-provider-oci/controllers  2.559s  coverage: 59.2% of statements
ok      github.com/oracle/cluster-api-provider-oci/exp/api/v1beta1      32.768s coverage: 15.3% of statements
ok      github.com/oracle/cluster-api-provider-oci/exp/api/v1beta2      0.065s  coverage: 4.8% of statements
ok      github.com/oracle/cluster-api-provider-oci/exp/controllers      0.996s  coverage: 56.3% of statements
go tool cover -func=coverage.out -o coverage.txt
go tool cover -html=coverage.out -o coverage.html

e2e tests
Ran 7 of 28 Specs in 3084.062 seconds
SUCCESS! -- 7 Passed | 0 Failed | 0 Pending | 21 Skipped


[DOCS][MINOR][JSTimers.js] Fixed "constants" typo

Motivation
oss-typos DC workshop: rid the world of typos.
Test Plan
Manual spell checker reporting duty.
Release Notes

[DOCS][MINOR][JSTimers.js] Fixed "constants" typo

Thanks for the fix! Could you just sign the CLA so we can merge this?

@facebook-github-bot shipit

@facebook-github-bot shipit


Use Ruby instead of SQL to migrate data

During testing on preview the migration took approximately 40 minutes to run during which time no inserts would be possible. Iterating over all of the rows in Ruby and updating them one by one is much slower but doesn't lock the whole table. Tests on a MacBook Pro showed the migration to take about 4-5 hours but can be left running in the background whilst petitions are still being signed.

LGTM.


Add list_ endpoints for node testing

In this PR I propose an implementation of 3 new endpoints for the miden node:

list_accounts - Lists all accounts in the store
list_nullifiers - Lists all nullifiers in the store
list_notes - Lists all notes in the store

Proposed and closing: #97
These testing endpoints will help us to monitor the current state of the node through grpc requests.

As discussed with @bobbinth I have represented the following:
List of nullifiers as: repeated tsmt.NullifierLeaf nullifiers = 1;
https://github.com/0xPolygonMiden/miden-node/blob/59984a5d4969053c55edf148c978a30b0ada23e9/proto/proto/tsmt.proto#L23-L26
List of notes as: repeated note.Note notes = 1;
https://github.com/0xPolygonMiden/miden-node/blob/59984a5d4969053c55edf148c978a30b0ada23e9/proto/proto/note.proto#L7-L17
List of notes as: repeated account.Account accounts = 1;
For now Account is an empty message
This is what we discussed for reference:

Questions:

Would you or another member have guidance on what should we include in these messages?

To be able to test the endpoints we should be able to add notes and nullifiers to the db. Is there a way to add notes or nullifiers to the db manually? (potentially through apply_block, but is there another way?)

Why is there a TODO: on top of the Note message saying remove this message as it can be replaced by an internal domain type in the Store component

Could you clarify why we have an API on the rpc crate and on the store crate? (What is the need of the RPC if I can directly communicate with the Store?)

Thank you

Looks good! Thank you! This is not a full review yet. I left a couple of comments inline, but to answer your questions:

Would you or another member have guidance on what should we include in these messages?

I think the notes and nullifiers endpoints look fine. I left a comment about what could go into the account message.

Why is there a TODO: on top of the Note message saying remove this message as it can be replaced by an internal domain type in the Store component

Previously, this message was not used in any requests/responses - so, we wanted to remove it. But now, since you are using it, we could probably get rid of the TODO.

Could you clarify why we have an API on the rpc crate and on the store crate? (What is the need of the RPC if I can directly communicate with the Store?)

Usually, only the RPC endpoint would be exposed publicly and store would be accessible only by going through the RPC. But since we are doing this for testing, it probably will be fine to expose the store endpoint directly and so we don't need to route them through RPC.

To be able to test the endpoints we should be able to add notes and nullifiers to the db. Is there a way to add notes or nullifiers to the db manually? (potentially through apply_block, but is there another way?)

I think apply_block is the only one - but it is probably also fairly complicated to do for testing purposes (though, @plafer would know better). We should have a better way of testing these things. One other way could be to ingest some dummy data at genesis. Let's create an issue to discuss this.

Well understood for the above points.
I have not been able to connect to the rpc for now. I was only able to make calls to the store directly. Will look into why that is.
Created an issue #127.

As requested by @bobbinth, I will add my next PR's not as a fork of the repo but directly as a branch of main.
I will merge this one as is for now if that is okay to not have to move all updates and will start doing so in further updates.


Engine load balancing strategy

1. Describe the feature
The last engine is acquired by default. Is there any plan to support other engine load balancing strategies?
Such as load balancing according to the current number of sessions of the engine.

Good idea, actually we have some discussion about this internal.
Maybe we can have something like engine pool to provide the ability of load balancing. And about the strategies, we can support round robin, session/statment-number-weight-based or other user defined strategy which is used the interface provided by this framework.
As you konw, Kyuubi is stateless in a cluster so it should be considered first how to share the engine pool status between several Kyuubi services. So we need more details and  some design of this.
It's also very helpful if you can share some use case of this feature.

For engine, we'd call it service discovery, not load balancing. The engine discovery logic is better to bind with client requests, a.k.a, JDBC connections, as an engine is stateful with cache tables, udf, etc. We already have implemented 3 share levels, CONNECTION/USER/SERVER for different kinds of usage scenarios.

For CONNECTION mode, the engine and all states are within a JDBC connection.
For USER mode, the engine and all states might/could share across all JDBC connections of a user with a subDomain if any.

For The last engine is acquired by default, it's a potential bug since 1.2.0-rcs as a distributed lock for engine creation. When an engine is created but killed forcefully and externally, the service uri of this engine will not get cleared. And another thread might get a malformed engine after it gains the lock. For this part, I think we need to introduce a retry and recreation of engine

Hi @ulysses-you @yaooqinn
A simple implementation of this feature in #802 , can you help me review it and give some suggestions?


fix encoding to utf-8 twice

with this fix I'm able to print non-ascii strings as utf-8 strings, not as bytes representation:
like купить, not b'\xd0\xba\xd1\x83\xd0\xbf...

Thanks! I really need to figure out the best way of handling utf-8 strings. This seems to work well tho. Merged :)


new release 0.3.3-Possible Ban

Possible Ban still appearing with new release :(
Can someone tell me how to fix this or sign in with Google Account where I have no problems,
Ive tried two different accounts with same issue

same problem.
 Logging into a google account with the current API results in instaban, so it was removed. Try creating a new PTC account, go through the tutorial on the phone app, then try to log in. Accounts seem to be banned about every 2-5 days after using the API, so you will just need to keep creating new accounts.

I am so curious that you do not have javaScript error when running more than 1 window?

Logged into PTC with Phone and worked fine. still saying possible ban and this is the third account created?!? :(

Strange, possibly firewall blocking the program?

@galaxy9999 I do. I've had the same issue for many releases, since maybe 0.1.1 or something. But normally, I just use a spreadsheet to manage accounts and scan locations. The javascript error seems to not affect the scan location if I don't move the location marker, so I just ignore it. I've tried logging out and back in until there isn't an error, and it shows the correct location, but since it doesn't really affect the scan location, I typically just ignore it instead of wasting my time doing that.

Interesting, my JavaScript error definitely affect the scan location on all even # of the windows I opened. :/

@galaxy9999 Are you sure it does? Mine will show the marker at the wrong place, typically the location of the previous login window, but the actual scan location is correct. Try turning on scan locations on the first window opened, and for each additional instance, even if it is showing the wrong location, don't move it, and see in the first window if it is actually scanning the correct location.


[Bug] When I browse 3D images, the image does not display on my mobile phone, there will be a gray area; but most mobile phones can do it, PC is also ok;

Describe the Bug
https://v1.cornerstonejs.org/live-examples/volumeViewport3D
When accessing this address, the mobile phone will be abnormal

Steps to Reproduce
No demos of the cornerstone can be previewed
Model: HONOR V30P.
System: HarmonyOS 4.2.0.
Processor: HUAWEI Kirin 990 5G
The current behavior
All stack, volume and 3d volume cannot be previewed, they are all gray squares
The expected behavior
You can preview the volume and 3d volume normally
OS
HarmonyOS 4.2.0
Node version
18.20.2
Browser
Wechat browser 8.0.54

@sedghi i can confirm that cornerstone3d rendering is broken on mobile for stack and 3d, i am using a Pixel phone and it used to work a few weeks ago

the v1 link is rendering correctly

我可以确认 Cornerstone3D 渲染在移动设备上的 Stack 和 3D 渲染已损坏，我使用的是 Pixel 手机，几周前它曾经可以工作

Yes, only on my device, not on other devices; the error prompt is "Failed to load OES_texture_float_linear. Texture filtering is not available for * 32F internal formats."

Yes, only on my device, not on other devices; the error prompt is "Failed to load OES_texture_float_linear. Texture filtering is not available for * 32F internal formats."

@sedghi i can confirm that cornerstone3d rendering is broken on mobile for stack and 3d, i am using a Pixel phone and it used to work a few weeks ago

Yes, only on my device, not on other devices; the error prompt is "Failed to load OES_texture_float_linear. Texture filtering is not available for * 32F internal formats."

@zhr6675 Are you testing the latest? since i see you sent a v1 link, test this one
https://www.cornerstonejs.org/live-examples/volumeviewport3d
https://www.cornerstonejs.org/live-examples/stackbasic
@daker Our tests passes right now on pixel 7 and iphone
https://github.com/cornerstonejs/cornerstone3D/blob/main/playwright.config.ts#L35-L59

Tested with below link on OnePlus 7T & Android 12. 8 GB RAM, Chrome Browser
https://www.cornerstonejs.org/live-examples/volumeviewport3d
Getting

@iconsys same thing for me, can you also check the stackbasic demo ?

Does this example run in your device
https://kitware.github.io/vtk-js/examples/VolumeMapperBlendModes.html

@sedghi it doesn't work on latest chrome but works on FF mobile, someone made PR #3194

Does our example render fine in FF?

Does our example render fine in FF?

Yes

Hahaha (laughing through the pain)

此示例是否在您的设备中运行
https://kitware.github.io/vtk-js/examples/VolumeMapperBlendModes.html

I don't have an image here, just a white 3D shadow


Logs are not correlated to traces

Hi there, I'm seeing an issue that the logs are not correlated with traces, and the hint is

and in APM page, I can only find very few traces are attached with only one log. Most of them are not correlated at all.
Originally I tested in my dev environment and everything went well, but after deployed to actual servers, this issue came out.
My instinct is that the agent samples too much as what it is mentioned in your official document:

Agent sampling: Reduces the resources and network used by the Agent for sending traces to the backend. Configurable, default to a maximum of 10 traces per second.

Additional environment details (Operating System, Cloud provider, etc):
Our infrastructure is fully containerized in k8s and running in AWS.
Please advise, thanks in advance.

Hi 👋
Since this involves various areas of the product, my advice is to try and reach out to support because they have broader knowledge and they might help you investigate deeper. The problem might not be in the agent. If by any chance it is, we'll be able to communicate further by means of that channel.
We can update this issue later based on how we move forward.

@gbbr thank u! I'm currently in a discussion with the support engineers and will update once it's figured out.
cheers.

Fixed, was caused by trace sampling and wrongly defined json formats.


Adjust chain.runtime_events indexes

@lukaw3d found that the /events endpoint was slow when a related account was not specified in the query (rel=oasis12345). The explain analyze of the query:
oasisindexer=*> explain analyze SELECT
            evs.round,
            evs.tx_index,
            evs.tx_hash,
            evs.tx_eth_hash,
            evs.timestamp,
            evs.type,
            evs.body,
            evs.evm_log_name,
            evs.evm_log_params,
            tokens.symbol,
            CASE -- NOTE: There are three queries that use this CASE via copy-paste; edit both if changing.
                WHEN tokens.token_type = 20 THEN 'ERC20'
                WHEN tokens.token_type = 721 THEN 'ERC721'
                ELSE NULL -- Our openapi spec doesn't allow us to output this, but better this than a null value (which causes nil dereference)
            END AS token_type,
            tokens.decimals
        FROM chain.runtime_events as evs
        -- Look up the oasis-style address derived from evs.body.address.
        -- The derivation is just a keccak hash and we could theoretically compute it instead of looking it up,
        -- but the implementing/importing the right hash function in postgres would take some work.
        LEFT JOIN chain.address_preimages AS preimages ON
            DECODE(evs.body ->> 'address', 'base64')=preimages.address_data AND
            preimages.context_identifier = 'oasis-runtime-sdk/address: secp256k1eth' AND
            preimages.context_version = 0
        LEFT JOIN chain.evm_tokens as tokens ON
            (evs.runtime=tokens.runtime) AND
            (preimages.address=tokens.token_address)
        WHERE evs.runtime='sapphire' and evs.evm_log_signature=decode('ddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef', 'hex') order by evs.round desc, evs.tx_index, evs.type, evs.body::text limit 1000 offset 0;

Limit  (cost=1075.95..10567.32 rows=1000 width=723) (actual time=23671.368..23673.820 rows=85 loops=1)
   ->  Nested Loop Left Join  (cost=1075.95..2688767.17 rows=283172 width=723) (actual time=23671.366..23673.808 rows=85 loops=1)
         Join Filter: ((evs.runtime = tokens.runtime) AND ((preimages.address)::text = (tokens.token_address)::text))
         ->  Gather Merge  (cost=1075.68..2680973.89 rows=283172 width=699) (actual time=23671.305..23673.486 rows=85 loops=1)
               Workers Planned: 2
               Workers Launched: 2
               ->  Incremental Sort  (cost=75.65..2647288.79 rows=117988 width=699) (actual time=22244.970..23642.661 rows=28 loops=3)
                     Sort Key: evs.round DESC, evs.tx_index, evs.type, ((evs.body)::text)
                     Presorted Key: evs.round
                     Full-sort Groups: 1  Sort Method: quicksort  Average Memory: 85kB  Peak Memory: 85kB
                     Worker 0:  Full-sort Groups: 2  Sort Method: quicksort  Average Memory: 89kB  Peak Memory: 89kB
                     Worker 1:  Full-sort Groups: 1  Sort Method: quicksort  Average Memory: 67kB  Peak Memory: 67kB
                     ->  Nested Loop Left Join  (cost=0.98..2642904.24 rows=117988 width=699) (actual time=719.131..23641.814 rows=28 loops=3)
                           ->  Parallel Index Scan Backward using ix_runtime_events_round on runtime_events evs  (cost=0.56..1782310.29 rows=117988 width=652) (actual time=717.539..23635.467 rows=28 loops=3)
                                 Index Cond: (runtime = 'sapphire'::runtime)
                                 Filter: (evm_log_signature = '\xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef'::bytea)
                                 Rows Removed by Filter: 372147
                           ->  Index Scan using ix_address_preimages_address_data on address_preimages preimages  (cost=0.42..7.28 rows=1 width=69) (actual time=0.206..0.207 rows=1 loops=85)
                                 Index Cond: (address_data = decode((evs.body ->> 'address'::text), 'base64'::text))
                                 Filter: ((context_identifier = 'oasis-runtime-sdk/address: secp256k1eth'::text) AND ((context_version)::integer = 0))
         ->  Materialize  (cost=0.28..6.05 rows=1 width=66) (actual time=0.001..0.001 rows=0 loops=85)
               ->  Index Scan using evm_tokens_pkey on evm_tokens tokens  (cost=0.28..6.04 rows=1 width=66) (actual time=0.045..0.045 rows=0 loops=1)
                     Index Cond: (runtime = 'sapphire'::runtime)
 Planning Time: 4.599 ms
 Execution Time: 23674.186 ms

The issue is that postgres is scanning backwards by round and filtering by evm_log_signature, and is not using the existing index on evm_log_signature because of the order by round desc. This PR updates the index to be more useful to the query. No other queries use this index.
New timings
 Limit  (cost=1063.44..6580.68 rows=1000 width=686) (actual time=63.622..219.231 rows=348 loops=1)
   ->  Nested Loop Left Join  (cost=1063.44..1529621.18 rows=277051 width=686) (actual time=63.620..219.173 rows=348 loops=1)
         Join Filter: ((evs.runtime = tokens.runtime) AND ((preimages.address)::text = (tokens.token_address)::text))
         Rows Removed by Join Filter: 3757
         ->  Gather Merge  (cost=1058.94..1391053.60 rows=277051 width=663) (actual time=63.521..216.633 rows=348 loops=1)
               Workers Planned: 2
               Workers Launched: 2
               ->  Incremental Sort  (cost=58.92..1358075.02 rows=115438 width=663) (actual time=35.149..95.806 rows=116 loops=3)
                     Sort Key: evs.round DESC, evs.tx_index, evs.type, ((evs.body)::text)
                     Presorted Key: evs.round
                     Full-sort Groups: 3  Sort Method: quicksort  Average Memory: 91kB  Peak Memory: 91kB
                     Worker 0:  Full-sort Groups: 5  Sort Method: quicksort  Average Memory: 123kB  Peak Memory: 132kB
                       Pre-sorted Groups: 9  Sort Method: quicksort  Average Memory: 54kB  Peak Memory: 277kB
                     Worker 1:  Full-sort Groups: 1  Sort Method: quicksort  Average Memory: 27kB  Peak Memory: 27kB
                     ->  Nested Loop Left Join  (cost=1.00..1353520.19 rows=115438 width=663) (actual time=4.419..91.201 rows=116 loops=3)
                           ->  Parallel Index Scan Backward using ix_runtime_events_evm_log_signature on runtime_events evs  (cost=0.56..525875.96 rows=115438 width=616) (actual time=1.611..69.041 rows=116 loops=3)
                                 Index Cond: ((runtime = 'sapphire'::runtime) AND (evm_log_signature = '\xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef'::bytea))
                           ->  Index Scan using ix_address_preimages_address_data on address_preimages preimages  (cost=0.43..7.16 rows=1 width=68) (actual time=0.182..0.182 rows=1 loops=348)
                                 Index Cond: (address_data = decode((evs.body ->> 'address'::text), 'base64'::text))
                                 Filter: ((context_identifier = 'oasis-runtime-sdk/address: secp256k1eth'::text) AND ((context_version)::integer = 0))
         ->  Materialize  (cost=4.49..42.15 rows=28 width=65) (actual time=0.000..0.001 rows=12 loops=348)
               ->  Bitmap Heap Scan on evm_tokens tokens  (cost=4.49..42.01 rows=28 width=65) (actual time=0.041..0.073 rows=28 loops=1)
                     Recheck Cond: (runtime = 'sapphire'::runtime)
                     Heap Blocks: exact=4
                     ->  Bitmap Index Scan on evm_tokens_pkey  (cost=0.00..4.49 rows=28 width=0) (actual time=0.029..0.031 rows=28 loops=1)
                           Index Cond: (runtime = 'sapphire'::runtime)
 Planning Time: 3.607 ms
 Execution Time: 219.412 ms
(28 rows)

I also updated the tx_hash and eth_tx_hash indexes to better match the ones in chain.runtime_transactions

oh it's because the query wants some quite sophisticated ordering. the index is only sorted down to round, so it doesn't know about how the tx_index and event type are ordered within that. so it's sorting all matching events, ever

oh it's because the query wants some quite sophisticated ordering. the index is only sorted down to round, so it doesn't know about how the tx_index and event type are ordered within that. so it's sorting all matching events, ever

But "all matching events" in this case is ... only 348 of them (rows=348), no? And it takes about 150ms (actual time=63.521..216.633) to sort them, somehow. I must be reading something wrong :)

no it's this one from the events side of the join
               ->  Incremental Sort  (cost=58.92..1358075.02 rows=115438 width=663) (actual time=35.149..95.806 rows=116 loops=3)
                     Sort Key: evs.round DESC, evs.tx_index, evs.type, ((evs.body)::text)
                     Presorted Key: evs.round

Thanks for the thorough testing!

on prod mainnet, both my query and the original query take forever

Hm the index wasn't applied to either production or staging yet, so it makes sense that the original query is slow. Seems like your optimized query would also benefit from the index, so I tested it out.
 I'm on the fence as to whether to include the updated query in this PR - the optimized query is more complex but the performance speedup is certainly noticable so I think overall I'm leaning towards it.

same query went from 3 minutes to 1 second after rerunning a few times

Probably the postgres cache. I confirmed that both queries slow significantly (> 1min) after removing the index.


Deployment - PostgreSQL Flexible Server by Azure Portal (InternalServerError)

Hi,
i occur this problem about a day now. Deploying PostgreSQL Flexible server worked for me normally in the past (3 months last time). Now it throws "InternalServerError" no matter the settings - which is by the azure portal validated and ok.
I dont know if I can give more info except batch of numbers which probably wont help.
{
"status": "Failed",
"error": {
"code": "InternalServerError",
"message": "An unexpected error occured while processing the request. Tracking ID: '4ff64595-b790-49e8-a4e5-e4ce51577bdf'"
}
}
Any idea? Should I just wait and try next day and next day ?
Thanks in advance

Seems not related to Azure CLI commands

Seems not related to Azure CLI commands

Sorry, I am still quite new to GitHub :-) I just clicked "report problem" in official azure documentation,

Please reopen if you find the issue is related to Azure CLI commands.

After like 20 tries, trying to change every single option I finally succeed. The problem was in admin username "Dissidence" is simply not accepted. Worked two times ok with just different username.


[C++][Parquet] Remove unneeded LZ4-related code

The LZ4 algorithm is not used for the Parquet LZO compression type. We should remove the unneeded dependency from the thirdparty toolchain and build.
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
Note: This issue was originally created as PARQUET-614. Please see the migration documentation for further details.

Wes McKinney / @wesm:
PR here: https://github.com/apache/parquet-cpp/pull/103

Wes McKinney / @wesm:
Issue resolved by pull request 103
https://github.com/apache/parquet-cpp/pull/103