Add support for referencing subschemas by id.

Add support for $ref elements using a subschema's declared id value. This is supported by a an additional store in the RefResolver class that stores all id declared subschemas.

Hey @dfinlay thanks so much!
Would you mind elaborating a bit on what this is doing? Is this functionality you think is in the spec that's missing from jsonschema, or functionality you wish existed, or a convenience helper for functionality that exists already?

Sorry, I should have added some more commentary. This pull request adds support accessing subschemas by their id/$id keyword. This specifically addresses #341 as well.
A note on the implementation, I added the store_subschema to RefResolver, because I didn't want to be too intrusive in the changes.  I think it would be better to make RefResolver.store a dict of dicts, and use # to identify the root schema. Thoughts?
I'd like to add some more tests, but I was a bit lost in the the test structure. Guidance on where / how to add them would be appreciated.

Aha, awesome!
I have to definitely read this carefully -- the one general thing I'd say though is that I definitely want to restrict public changes to the $ref implementation (to RefResolver), because I have strong suspicion that it needs replacing entirely ( #346 ). So definitely if this can be done in a way that doesn't even add to the public interface, we should do that I think (so, e.g., is there actually a need to add the additional subschema_store parameter, or can it just be created by not overridable externally?)

I think it would be better to make RefResolver.store a dict of dicts, and use # to identify the root schema.

This sounds likely to be backwards incompatible with what the current thing asks for. But I probably have to read the changes here carefully to understand exactly.

I'd like to add some more tests, but I was a bit lost in the the test structure.

Yeah, sorry bout that :/. The tests for this seem very likely like they'd go in test_validators, alongside the 2 I see you modified, but I can follow up with a specific recommendation after I read the code.

Hey, haven't forgotten this, just still having some trouble figuring out how much of this is a bug fix and how much is new :/.
It's likely my own fuzzy knowledge of $ref that I never properly sat down to think about.
Still definitely hoping to find some time to think about this PR though. Sorry for the wait.

any news on this?

I should probably have been more proactive with this.  I needed to add more tests!  Also, looking back at this without rose-tinted glasses, there is as a problem with the implementation.  You cannot pass an object for validation against a defined subschema.  Instead, you can only validate subschema elements if they are children of root schema instance. This should be resolved before this change is merged.
Ideally, one should be able to pass a string id to the validator with an instance and have it validated against the schema w/ that ID, regardless of whether it is a subschema and root.
Here is an example of how you have to validate instances against subschemas now (Ignore the versions here, just an example).
schema = {
  "$schema": "http://json-schema.org/draft-06/schema#",
  "$id": "awesome.json",
  "title": "Awesome",
  "type": "object",
  "properties": {
    "name": {
      "title": "Awesome Name",
      "type": "string",
      "maxLength": 256,
      "default": ""
    },
    "sauce": {
      "$ref": "#awesome-sauce"
    }
  },
  "required": [
    "name",
    "sauce"
  ],
  "definitions": {
    "awesome-sauce": {
      "$id": "#awesome-sauce",
      "title": "Awesome Sauce",
      "description": "Sauce for your food that is quite awesome.",
      "enum": [
        "ranch",
        "french-onion",
        "au-jus",
        "misc",
        "recycled"
      ]
    }
  }
}

validator = jsonschema.Draft4Validator(schema)

data = dict(name="Dave's Homemade Ranch", sauce="ranch")

sauce = dict(sauce="ranch")

validator.validate(data)
> True

validator.validate(sauce)
> False

validator.validate(sauce, schema['definitions']['awesome-sauce'])
> True

Hi guys. Any news on this? I have a schema that validates on an online validator but is invalid when validated with jsonschema

Any updates on this?
I really need to refer to other json files!

Hello, what is the status of this?
It has been more than one year since the PR was created and jsonschema still fails parsing a schema with $refs pointing to custom $ids in the same schema (issue #341). It's sad that I'll need to modify my schema to be less expresive in order to verify it on Python (is there any other Python implementation with proper $ref support?).
Sorry for being hard, but it's really sad to see such a basic feature stalled for years, it makes me feel the project is dead! It is even referenced in the docs that jsonschema don't support this: https://json-schema.org/understanding-json-schema/structuring.html#using-id-with-ref.
Imagine how rare it is that this feature isn't supported to be mentioned on the official json schema guide!

@alvarogzp please feel free to read the comments on this ticket -- notably, the need for an upstream test case to be failing and fixed by this (if the existing ones do so, great).

It's sad that I'll need to modify my schema to be less expresive in order to use it on Python

Considering how composable jsonschema is, you absolutely do not, since you've got about 5 other options to choose from, not least of which being transforming your schema just before handing it to jsonschema, but please do save the guilt trip. It's a bit ridiculous to say such a thing, or create FUD around the project being dead which clearly can be seen not to be the case by just looking at the commit history.
jsonschema is an open source project.

Sorry about my previous post and language, it was totally inappropriate.
I'll try to be more proactive instead of just complaining.
I've been looking in the JSON-Schema-Test-Suite for any test fixed by this (as you suggested), and certainly there isn't. However, I found https://github.com/json-schema-org/JSON-Schema-Test-Suite/pull/225 which adds tests for it (the technical name is "Location-independent identifiers", and they are defined in https://tools.ietf.org/html/draft-handrews-json-schema-01#section-8.2.3). I'll try to help with that PR too.
Also, I have been testing this branch and found some issues regarding to the handling of the 'id' property (also mentioned on the comments above). I have fixed it, merged with master (there was a merge conflict) and added a small test to TestRefResolver (you can check the new test would fail against master and pass against this branch). The result is here, and the diff of my changes (without the merge commit) can be found here. Feel free to sync this branch with mine, or if you want I can create a new PR.
I tested the branch with the following schema and it validates properly (it doesn't on master):
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "title": "Test",
  "properties": {
    "test": { "$ref": "#test" }
  },
  "definitions": {
    "test": {
      "$id": "#test",
      "title": "A test string",
      "type": "string"
    }
  }
}

If there is more I can do, just tell me.
Thanks for the project, and sorry again!

Thanks, no hard feelings, and definitely thanks for the offer to help it is very much appreciated.
I think based on what you found upstream, yeah let's get that merged in there then first. I can review that upstream. Can you maybe have a look at that PR in the test suite, leave any comments there that you see, and then I can merge it (and possibly double check with @handrews to make sure he agrees, if he's available)?
Once that's done, we can come back here and have a look at the fix you put in as well, and maybe get this merged!

Any change that this PR will be merged one day?

Hey @jjmurre  -- do you think you'd be willing to help address the issues remaining above?

I'll have a look, see if I can find my way around the codebase.


Getting Started Example Chat Server is Pretty Advanced

Currently the getting started example is a chat server that includes several concepts that have yet to be explained like codecs. Would it better for readers if the example only used concepts explained in the guide? What could we replace the example with?

@rylev Maybe switch to a client example (#40). The chat example can be moved to the transport section then?

I agree with @rylev the chat example chat.rs contains lots of new concepts and chat-combinator.rs is not intuitive. I think we should first identify main actors, tasks and futures and then define they relationship. after that we should implement each task and connect them with channels clearly.


Allow use of process.stdout as one of bunyan streams

While process.stdout is not only a stream$Writable, but also a tty$WriteStream (https://github.com/facebook/flow/blob/master/lib/node.js#L1483), passing it as a bunyan stream causes errors.
Test was corrected to include originally failing case.
Original issue was caused by process.stdout being descendant of
tty$WriteStream and being not a stream$Writable.

Seems like a good addition @dolphin278 Thanks!


[libiconv] Build error

issue_body.md

debug log
D:\vcpkg>vcpkg install libiconv:x64-windows --debug
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Trying to load bundleconfig from D:\vcpkg\vcpkg-bundle.json
[DEBUG] Failed to open: D:\vcpkg\vcpkg-bundle.json
[DEBUG] Bundle config: readonly=false, usegitregistry=false, embeddedsha=nullopt, deployment=Git, vsversion=nullopt
[DEBUG] Metrics enabled.
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Using scripts-root: D:\vcpkg\scripts
[DEBUG] Using builtin-ports: D:\vcpkg\ports
[DEBUG] Using installed-root: D:\vcpkg\installed
[DEBUG] Using buildtrees-root: D:\vcpkg\buildtrees
[DEBUG] Using packages-root: D:\vcpkg\packages
[DEBUG] Using vcpkg-root: D:\vcpkg
[DEBUG] Using scripts-root: D:\vcpkg\scripts
[DEBUG] Using builtin-registry: D:\vcpkg\versions
[DEBUG] Using downloads-root: D:\vcpkg\downloads
[DEBUG] Detecting host with IsWow64Process2
Computing installation plan...
[DEBUG] CreateProcessW("D:\vcpkg\downloads\tools\cmake-3.25.1-windows\cmake-3.25.1-windows-i386\bin\cmake.exe" --version)
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1000: cmd_execute_and_stream_data() returned 0 after    53428 us
[DEBUG] CreateProcessW("D:\vcpkg\downloads\tools\cmake-3.25.1-windows\cmake-3.25.1-windows-i386\bin\cmake.exe" -DVCPKG_ROOT_DIR=D:/vcpkg -DPACKAGES_DIR=D:/vcpkg/packages -DBUILDTREES_DIR=D:/vcpkg/buildtrees -D_VCPKG_INSTALLED_DIR=D:/vcpkg/installed -DDOWNLOADS=D:/vcpkg/downloads -DVCPKG_MANIFEST_INSTALL=OFF -P "D:\vcpkg\buildtrees\0.vcpkg_tags.cmake")
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1001: cmd_execute_and_stream_data() returned 0 after    31486 us
The following packages will be built and installed:
libiconv:x64-windows -> 1.17#1
[DEBUG] CreateProcessW("C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -all -prerelease -legacy -products * -format xml)
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1002: cmd_execute_and_stream_data() returned 0 after    35596 us
[DEBUG] Trying to hash D:\vcpkg\scripts\toolchains/windows.cmake
[DEBUG] D:\vcpkg\scripts\toolchains/windows.cmake has hash 36b818778ba6f2c16962495caedb9a7b221d5be4c60de1cd3060f549319a9931
[DEBUG] Trying to hash D:\vcpkg\triplets\x64-windows.cmake
[DEBUG] D:\vcpkg\triplets\x64-windows.cmake has hash 4556164a2cd3dd6f4742101eabb46def7e71b6e5856faa88e5d005aac12a803c
Detecting compiler hash for triplet x64-windows...
[DEBUG] Found path: C:\Program Files\Git\cmd\git.exe
[DEBUG] CreateProcessW("C:\Program Files\Git\cmd\git.exe" --version)
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1003: cmd_execute_and_stream_data() returned 0 after    49561 us
[DEBUG] Detecting host with IsWow64Process2
[DEBUG] Found path: C:\Program Files\PowerShell\7\pwsh.exe
[DEBUG] CreateProcessW("C:\Program Files\PowerShell\7\pwsh.exe" --version)
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1004: cmd_execute_and_stream_data() returned 0 after   167978 us
[DEBUG] command line: cmd /c "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary/Build\vcvarsall.bat" -vcvars_ver=14.36.32532 amd64   2>&1 <NUL  & echo cdARN4xjKueKScMy9C6H & set
[DEBUG] CreateProcessW(cmd /c "C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary/Build\vcvarsall.bat" -vcvars_ver=14.36.32532 amd64   2>&1 <NUL  & echo cdARN4xjKueKScMy9C6H & set)
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1005: cmd_execute_and_stream_data() returned 0 after  1186500 us
[DEBUG] **********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.6.2
** Copyright (c) 2022 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: 'x64'
cdARN4xjKueKScMy9C6H
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\김혁\AppData\Roaming
CommandPromptType=Native
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=DESKTOP-53PU8LV
ComSpec=C:\WINDOWS\system32\cmd.exe
DevEnvDir=C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE
ExtensionSdkDir=C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs
EXTERNAL_INCLUDE=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\include;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\ATLMFC\include;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um
Framework40Version=v4.0
FrameworkDir=C:\Windows\Microsoft.NET\Framework64
FrameworkDir64=C:\Windows\Microsoft.NET\Framework64
FrameworkVersion=v4.0.30319
FrameworkVersion64=v4.0.30319
FSHARPINSTALLDIR=C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\FSharp\Tools
HOMEDRIVE=C:
HOMEPATH=\Users\김혁
HTMLHelpDir=C:\Program Files (x86)\HTML Help Workshop
INCLUDE=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\include;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\ATLMFC\include;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um
LIB=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\ATLMFC\lib\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\lib\x64;C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\lib\um\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.19041.0\ucrt\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.19041.0\um\x64
LIBPATH=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\ATLMFC\lib\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\lib\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\lib\x86\store\references;C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.19041.0;C:\Program Files (x86)\Windows Kits\10\References\10.0.19041.0;C:\Windows\Microsoft.NET\Framework64\v4.0.30319
LOCALAPPDATA=C:\Users\김혁\AppData\Local
LOGONSERVER=\DESKTOP-53PU8LV
NETFXSDKDir=C:\Program Files (x86)\Windows Kits\NETFXSDK\4.8
NUMBER_OF_PROCESSORS=16
OS=Windows_NT
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
Platform=x64
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 167 Stepping 1, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=a701
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Program Files\WindowsPowerShell\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
PUBLIC=C:\Users\Public
SystemDrive=C:
SystemRoot=C:\WINDOWS
TEMP=C:\Users\김혁\AppData\Local\Temp
TMP=C:\Users\김혁\AppData\Local\Temp
UCRTVersion=10.0.19041.0
UniversalCRTSdkDir=C:\Program Files (x86)\Windows Kits\10
USERDOMAIN=AzureAD
USERDOMAIN_ROAMINGPROFILE=AzureAD
USERNAME=김혁
USERPROFILE=C:\Users\김혁
VCIDEInstallDir=C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\VC
VCINSTALLDIR=C:\Program Files\Microsoft Visual Studio\2022\Community\VC
VCToolsInstallDir=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532
VCToolsRedistDir=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Redist\MSVC\14.36.32532
VCToolsVersion=14.36.32532
VisualStudioVersion=17.0
VS170COMNTOOLS=C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools
VSCMD_ARG_app_plat=Desktop
VSCMD_ARG_HOST_ARCH=x64
VSCMD_ARG_TGT_ARCH=x64
VSCMD_ARG_VCVARS_VER=14.36.32532
VSCMD_VER=17.6.2
VSINSTALLDIR=C:\Program Files\Microsoft Visual Studio\2022\Community
windir=C:\WINDOWS
PATH=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.36.32532\bin\HostX64\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\VC\VCPackages;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer;C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\bin\Roslyn;C:\Program Files\Microsoft Visual Studio\2022\Community\Team Tools\Performance Tools\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\Team Tools\Performance Tools;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\x64;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\FSharp\Tools;C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64;C:\Program Files (x86)\Windows Kits\10\bin\x64;C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64;C:\Windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools;C:\Program Files\PowerShell\7;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja;C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\VC\Linux\bin\ConnectionManagerExe
VSLANG=1033
VSCMD_SKIP_SENDTELEMETRY=1
VCPKG_COMMAND=D:/vcpkg/vcpkg.exe
WindowsLibPath=C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.19041.0;C:\Program Files (x86)\Windows Kits\10\References\10.0.19041.0
WindowsSdkBinPath=C:\Program Files (x86)\Windows Kits\10\bin
WindowsSdkDir=C:\Program Files (x86)\Windows Kits\10
WindowsSDKLibVersion=10.0.19041.0
WindowsSdkVerBinPath=C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0
WindowsSDKVersion=10.0.19041.0
WindowsSDK_ExecutablePath_x64=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\x64
WindowsSDK_ExecutablePath_x86=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools
X_VCPKG_RECURSIVE_DATA={}
__DOTNET_ADD_64BIT=1
__DOTNET_PREFERRED_BITNESS=64
__VSCMD_PREINIT_PATH=C:\Program Files\PowerShell\7;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0\
[DEBUG] CreateProcessW("D:\vcpkg\downloads\tools\cmake-3.25.1-windows\cmake-3.25.1-windows-i386\bin\cmake.exe" -DCURRENT_PORT_DIR=D:/vcpkg/scripts/detect_compiler -DCURRENT_BUILDTREES_DIR=D:/vcpkg/buildtrees/detect_compiler -DCURRENT_PACKAGES_DIR=D:/vcpkg/packages/detect_compiler_x64-windows -D_HOST_TRIPLET=x64-windows -DCMD=BUILD -DDOWNLOADS=D:/vcpkg/downloads -DTARGET_TRIPLET=x64-windows -DTARGET_TRIPLET_FILE=D:/vcpkg/triplets/x64-windows.cmake -DVCPKG_BASE_VERSION=2023-06-08 -DVCPKG_CONCURRENCY=17 -DVCPKG_PLATFORM_TOOLSET=v143 "-DGIT=C:/Program Files/Git/cmd/git.exe" -DVCPKG_ROOT_DIR=D:/vcpkg -DPACKAGES_DIR=D:/vcpkg/packages -DBUILDTREES_DIR=D:/vcpkg/buildtrees -D_VCPKG_INSTALLED_DIR=D:/vcpkg/installed -DDOWNLOADS=D:/vcpkg/downloads -DVCPKG_MANIFEST_INSTALL=OFF -P "D:\vcpkg\scripts\ports.cmake")
[DEBUG] -- Found external ninja('1.11.0').
[DEBUG] -- Configuring x64-windows
[DEBUG] [1/1] "D:/vcpkg/downloads/tools/cmake-3.25.1-windows/cmake-3.25.1-windows-i386/bin/cmake.exe" -E chdir ".." "D:/vcpkg/downloads/tools/cmake-3.25.1-windows/cmake-3.25.1-windows-i386/bin/cmake.exe" "D:/vcpkg/scripts/detect_compiler" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=D:/vcpkg/packages/detect_compiler_x64-windows" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=D:/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=D:/vcpkg" "-DZ_VCPKG_ROOT_DIR=D:/vcpkg" "-D_VCPKG_INSTALLED_DIR=D:/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
[DEBUG] -- The C compiler identification is MSVC 19.36.32532.0
[DEBUG] -- The CXX compiler identification is MSVC 19.36.32532.0
[DEBUG] #COMPILER_HASH#37ddf335dc10d14fa90c13a22cc1ec1cdbd1efcd
[DEBUG] #COMPILER_C_HASH#9ac2ea81ebb5df440e5701508eb661118eeb8f4c
[DEBUG] #COMPILER_C_VERSION#19.36.32532.0
[DEBUG] #COMPILER_C_ID#MSVC
[DEBUG] #COMPILER_CXX_HASH#9ac2ea81ebb5df440e5701508eb661118eeb8f4c
[DEBUG] #COMPILER_CXX_VERSION#19.36.32532.0
[DEBUG] #COMPILER_CXX_ID#MSVC
[DEBUG] -- Configuring done
[DEBUG] -- Generating done
[DEBUG] CMake Warning:
[DEBUG]   Manually-specified variables were not used by the project:
[DEBUG]
[DEBUG]     BUILD_SHARED_LIBS
[DEBUG]     CMAKE_INSTALL_BINDIR
[DEBUG]     CMAKE_INSTALL_LIBDIR
[DEBUG]     _VCPKG_ROOT_DIR
[DEBUG]
[DEBUG]
[DEBUG] -- Build files have been written to: D:/vcpkg/buildtrees/detect_compiler/x64-windows-rel
[DEBUG]
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1006: cmd_execute_and_stream_data() returned 0 after  1355442 us
[DEBUG]
[DEBUG] Detected compiler hash for triplet x64-windows: 37ddf335dc10d14fa90c13a22cc1ec1cdbd1efcd
[DEBUG] Trying to hash D:\vcpkg\ports\libiconv\0002-Config-for-MSVC.patch
[DEBUG] D:\vcpkg\ports\libiconv\0002-Config-for-MSVC.patch has hash 7eb9dded5bc1e34a02d2bfa88f8c1cf1f454b3cf5e82d0d0c45cf7bf45a54c19
[DEBUG] Trying to hash D:\vcpkg\ports\libiconv\0003-Add-export.patch
[DEBUG] D:\vcpkg\ports\libiconv\0003-Add-export.patch has hash e920b915952a0fb574a10538ac117e2d668465ea5353586296a923cb3319159d
[DEBUG] Trying to hash D:\vcpkg\ports\libiconv\0004-ModuleFileName.patch
[DEBUG] D:\vcpkg\ports\libiconv\0004-ModuleFileName.patch has hash 5405e2493fa1846788e2bb2fd62334d2d98d2a5fa47a36a52047608472125d46
[DEBUG] Trying to hash D:\vcpkg\ports\libiconv\clang-fortify.patch
[DEBUG] D:\vcpkg\ports\libiconv\clang-fortify.patch has hash 1e8bf046ffe3fe05d7b7485489a8aed80df5a084341c986a72b809aa91d9a500
[DEBUG] Trying to hash D:\vcpkg\ports\libiconv\portfile.cmake
[DEBUG] D:\vcpkg\ports\libiconv\portfile.cmake has hash eaa550cdedada1d2751461100f828bd856bc600632a08beecb1267b559698426
[DEBUG] Trying to hash D:\vcpkg\ports\libiconv\usage
[DEBUG] D:\vcpkg\ports\libiconv\usage has hash d7cbdf659f9d8a102889357ffb9957ce898867c64c20e6afbe736bd21a85a887
[DEBUG] Trying to hash D:\vcpkg\ports\libiconv\vcpkg-cmake-wrapper.cmake
[DEBUG] D:\vcpkg\ports\libiconv\vcpkg-cmake-wrapper.cmake has hash d83d9ca94c91ac33648d4286a7a7b855cf1abd53895e82832e389c3362d6c94f
[DEBUG] Trying to hash D:\vcpkg\ports\libiconv\vcpkg.json
[DEBUG] D:\vcpkg\ports\libiconv\vcpkg.json has hash e50251b8238ea5cf950f1688bd85c135bd3881d7bade4e655fa45c1a9925ff7f
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\execute_process.cmake
[DEBUG] D:\vcpkg\scripts\cmake\execute_process.cmake has hash 66a937b9c074422643135c319d1abadaa45484a664f1b160d4c163efb444a446
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_acquire_msys.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_acquire_msys.cmake has hash 4bae2ec8c9bd6647b87dd94bbee9d7d7fb740c361861051c7b32cb753d2c0f15
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_add_to_path.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_add_to_path.cmake has hash 5f5ae75cf37b2a58d1a8561ca96496b64cd91ec9a0afab0b976c3e5d59030bfe
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_apply_patches.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_apply_patches.cmake has hash 4c123ce6f9bf0c46adc8287b7bd6a40b5f5e8daa83623dd21bb8c568ad4421fc
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_backup_restore_env_vars.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_backup_restore_env_vars.cmake has hash 5621f3b6a9586ffc02d49a5032560a48ad291de1cce553b904588f0108648904
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_buildpath_length_warning.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_buildpath_length_warning.cmake has hash fa440f3734e34b462ef96f3e89f0a9c5a11b609110a15a162d24da9218693fd1
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_build_cmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_build_cmake.cmake has hash 5201d6149d85fff414f3fbbdc4c793e0b2aeeb6d249a5ae8cf15e39fef66b7e6
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_build_make.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_build_make.cmake has hash 665ce441da618e4270950034db2912f6a863689c260a8a889d4ad41ff84367ba
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_build_msbuild.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_build_msbuild.cmake has hash 9a8367ac19733fc51b8e7edc77968725d2efe1400aaf1fdd767bb329a7b04532
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_build_ninja.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_build_ninja.cmake has hash 9bafdd942fe41be20a868e0a41ea6f983895bacba2f257921b53d789c7ad8092
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_build_nmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_build_nmake.cmake has hash 918422e54a328b9dce1be8c06916d612de9cc24a18c65cc47f26d78e8c487440
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_build_qmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_build_qmake.cmake has hash cd00146eb665b004c527cf74986e392d2419610ace073bd6abb79d55a7912004
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_check_features.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_check_features.cmake has hash 3cdc889b7e6965ad5ddab803060aed2019c0177b6f314c7a5a947c01efa4db60
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_check_linkage.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_check_linkage.cmake has hash 2236edfea13af20524c17d73214e0e5111bf1c13a2fc46c7f2912a46abd0c1a8
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_clean_executables_in_bin.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_clean_executables_in_bin.cmake has hash 5f7427ddf120583cf1f429861989e937858ee7a8c4deb419dca6f3f2fee86a65
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_clean_msbuild.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_clean_msbuild.cmake has hash 67007e54dee8a38487b43228573d877ad270fc6bac7bf8849783d0c2a78ce501
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_common_definitions.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_common_definitions.cmake has hash ea01c5711c7da32d9037361edee123507cb3708fe43b40ab3ecbbd32872310e3
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_common_functions.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_common_functions.cmake has hash 5f07e6f6184a02dcd8fc058eed1747a6bb65ee4a8f524e717651674f0bd7904c
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_configure_cmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_configure_cmake.cmake has hash 9dfd362bd20613eaa83af55eb0f98c8cb50fd4826a65da74a0f1641da73497c2
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_configure_gn.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_configure_gn.cmake has hash c6637dbdb7c20b2e067c924eeb50605f7e3cc9e7c8c1434e53c9280134df11ba
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_configure_make.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_configure_make.cmake has hash c343ff83697bd19846f265de24cd8a39af50c4d9ad581de68f033cb92294c2f0
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_configure_meson.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_configure_meson.cmake has hash 23c481b5e1bb9d7a4877608fd327d7289601331c8a10259922a90aec5addf8a2
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_configure_qmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_configure_qmake.cmake has hash 54d2123ecd337643ce9f3b0e4ef48f092bee5aea84d0372d12d1cc5f209a6437
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_copy_pdbs.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_copy_pdbs.cmake has hash d57e4f196c82dc562a9968c6155073094513c31e2de475694143d3aa47954b1c
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_copy_tools.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_copy_tools.cmake has hash 3d45ff761bddbabe8923b52330168dc3abd295fa469d3f2e47cb14dce85332d5
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_copy_tool_dependencies.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_copy_tool_dependencies.cmake has hash 66eef4116a52fd8cba76d274f44904846df943a3fc52317871cf255733b2efc4
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_download_distfile.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_download_distfile.cmake has hash 2d57e1336ae9daab2f04c0623217094b026080d19bdca3a92396d68ea3e729c7
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_execute_build_process.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_execute_build_process.cmake has hash 4145b3b23fcc2dd94a0fe3c818b63fcea40854e5aa94d08dc83ddcc09727cedf
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_execute_in_download_mode.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_execute_in_download_mode.cmake has hash 75a3cabe04d6bbaf1f73555516dd3c492edbed22cea204835c3620db5d948851
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_execute_required_process.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_execute_required_process.cmake has hash 0c6f52ca848715efd88acfec9bdb2ed3b5f38a650baa6a614bf23ccc3eec150a
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_execute_required_process_repeat.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_execute_required_process_repeat.cmake has hash 4863f71de8d0fd53ed799c6a5d15795156ae0606ecb61489b7636a050e029e2b
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_extract_source_archive.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_extract_source_archive.cmake has hash a25e0132b36c30e9675f934042fb1164128864eeefa064ab8eabb1eb347aa381
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_extract_source_archive_ex.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_extract_source_archive_ex.cmake has hash ab9f5bd71a8e1ca4a56d5c09f248c2bc10ff8df3b600c3efb6cca34cba9ec3b7
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_fail_port_install.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_fail_port_install.cmake has hash aef80df96f7c83d79e7b03d132161d8071228e0f1c9eb61ba8b16354f0c9496c
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(7Z).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(7Z).cmake has hash d90166548324314112ecaebc73ae440419ff2393c4882ff6420ebacb57923ea0
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(ARIA2).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(ARIA2).cmake has hash 0d4fdc0e24f6bfff5246bbc92c29c1a3bf8996452c5f85c26b667735d78b1a0b
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(BAZEL).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(BAZEL).cmake has hash 4a22f3ef45670639e38af6040a3fb2c99b7c719082e2ce87e082c9f8ee91b840
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(BISON).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(BISON).cmake has hash 4df1053ab129f7b9ccd5d58baaa91628c9269e259a7239c7eaed795ff1cae1d1
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(CLANG).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(CLANG).cmake has hash bc9f8433d5ce5a51e45a79c7469cdd9fcad154488b33ff6353af3b29400af50d
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(DARK).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(DARK).cmake has hash f20fed20d3fbf637ac329e1aae27193485d9a2954ae5fb21b5f00272b387286d
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(DOXYGEN).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(DOXYGEN).cmake has hash e3dcfd0b6a64f77db57a00edd22171f426103a6235165c906a38826e75c041b7
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(FLEX).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(FLEX).cmake has hash<PHONE_NUMBER>bda4fb2b605adedd8cfed7ac53430178931ffd20d8b007cc89f26f
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GASPREPROCESSOR).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GASPREPROCESSOR).cmake has hash 0ff31ab283d7b78bc7af20cdbd66b5adc0432f00f126f8111003245908398c88
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GIT).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GIT).cmake has hash bb3644b8863c1a03c3c76cf8b13047557e05b22f4be7a13cb4ad00e72d7ad6b6
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GN).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GN).cmake has hash f6c65fce5a51b65b8d081b05f11ae186223b39d78d2eeaf836f66b4e2e515aa3
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GO).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GO).cmake has hash 9fd39e73f7e9bdf425a808b250fbdd07f42e9424319b9d7a66b9d5a08a6f0b51
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GPERF).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(GPERF).cmake has hash 51821386b816ca387803930f656ef5bab21ff940bd78481ff7d5be2b1dad08a6
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(JOM).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(JOM).cmake has hash 0bd0d635ecc1a9532d2c95f4f7d4a6ec5a69d210309745e02a549841770a7773
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(MESON).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(MESON).cmake has hash a8c8e3b3cb948ca4d7c8b0b6ecce4006f82a361ec60291afe597c2a7e24300b0
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(NASM).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(NASM).cmake has hash 4682f861100163f7d3290dd7c64c86dd63f1447c2726d4449a46bc821d8a0a21
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(NINJA).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(NINJA).cmake has hash c0d488f37ddbef505e2e3ffaf588bc1da18f64da68089c9d325affea1a62f1a6
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(NUGET).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(NUGET).cmake has hash b086c0d991f8aab5351180ab2922410d061b7765eea9d64245fbacfff16a96c9
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PATCHELF).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PATCHELF).cmake has hash 11f2f903a5c7334e72ddae2cc18ad9d14040731961a0455ef2cf63aa552bd6e8
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PERL).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PERL).cmake has hash e839596a2b9dba81d28d2df0f7ed5fe7e766f45bb8ab6130634a7f7269db1f09
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PKGCONFIG).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PKGCONFIG).cmake has hash e6e05b67513c71a95cf0dcd6f9f8a014c97d90ba82a874c8ce31a2b5ffb952b0
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PYTHON2).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PYTHON2).cmake has hash ed078b84af22461e59694ab205a5ba9d0eb77d094ea64fc5754f7e19644b052e
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PYTHON3).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(PYTHON3).cmake has hash bf78099b5a097427eb6fbaa1dabe3eccea50abbcfe37bfc89e6c9ad8c6c9cb90
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(RUBY).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(RUBY).cmake has hash d8f4817a1586c627d680bba1eea42194351746bacc02f35f2eedbb3cd8e021b2
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(SCONS).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(SCONS).cmake has hash a9e54f49772920491ef5ed5c4633869d917f92ba7a9b222771124eab16ea006b
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(SWIG).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(SWIG).cmake has hash 69cbee18ee009cd0b9da6ea9a028a66761abaa8eda3186ccc258b729122d6435
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(YASM).cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program(YASM).cmake has hash 452a03ef1963d7773b515dde97f783cf7db5b5ecb7ad2df7bf33c7612322820d
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_acquire_program.cmake has hash<PHONE_NUMBER>43bc3e10f7ae54acc4a6468478c28adb52c84a930d096ff56f76dd
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_find_fortran.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_find_fortran.cmake has hash 0a5d03ecbe6ebd8cc9a654bc8e0441f35167ec5452d44791fe9b1c453dbb2ed9
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_fixup_cmake_targets.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_fixup_cmake_targets.cmake has hash 7f777f83ca76540ed573d986ee53d1b3da1e45f49f3856c44c0773fec71cb49f
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_fixup_pkgconfig.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_fixup_pkgconfig.cmake has hash 588d833ff057d3ca99c14616c7ecfb5948b5e2a9e4fc02517dceb8b803473457
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_from_bitbucket.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_from_bitbucket.cmake has hash e875eb81fb8b06b08d0c97aed211b161dca3d1b7da8e562aa5ee8a8809e9e3d0
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_from_git.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_from_git.cmake has hash 8f27bff0d01c6d15a3e691758df52bfbb0b1b929da45c4ebba02ef76b54b1881
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_from_github.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_from_github.cmake has hash b743742296a114ea1b18ae99672e02f142c4eb2bef7f57d36c038bedbfb0502f
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_from_gitlab.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_from_gitlab.cmake has hash 656b2e2f210c6607908ae03771b049648b55213ef0a782135f90e44edb271fc5
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_from_sourceforge.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_from_sourceforge.cmake has hash 99f72faf1e7611ac9c367677457e29599d81bb86f204ec68a3f0df87a62f0922
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_get_program_files_platform_bitness.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_get_program_files_platform_bitness.cmake has hash 0c21ce7e9fcf7828f2e06f488f4675816b87942cfbf828c183f5bbcba8ae5fc7
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_get_windows_sdk.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_get_windows_sdk.cmake has hash 9fe97b3807d78c81b54b9512e920112baf68c2b4f5ce483b2764edada074b4ec
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_host_path_list.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_host_path_list.cmake has hash 1e8382b3a80fc7458293fce1659077dcacda9892eb63d911ae0330fdb1aedc2d
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_install_cmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_install_cmake.cmake has hash<PHONE_NUMBER>c6ad9e9ed1d9b073eb9969159b553f9d6f5bee529cde91769355ff
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_install_copyright.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_install_copyright.cmake has hash ba6c169ab4e59fa05682e530cdeb883767de22c8391f023d4e6844a7ec5dd3d2
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_install_gn.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_install_gn.cmake has hash 18f1e80697fca670452e1ff181850e546764cc7c5fa8cb5d6442266523af9806
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_install_make.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_install_make.cmake has hash 8d8145837ce718ef60778b50fea1af272146c9efa42367ec2d7726332ef29ab5
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_install_meson.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_install_meson.cmake has hash 715cf59e78124dcc0823803544dc12ca4ced4f46ebc43681f4f6cd23d3e99d92
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_install_msbuild.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_install_msbuild.cmake has hash d770323312cc635d641183bfa4a0c073f919c8a37b7d9b3576700b1e934f8cd4
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_install_nmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_install_nmake.cmake has hash e5540f04f33bc8eee3417da64e2c9a9aa2bc3dee62031238d7eb795ec31cb0b7
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_install_qmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_install_qmake.cmake has hash e9eedf4e8a942dbae43e25d0f7a38a8c3afe7761c5d9e042d1a52017e3dcebe6
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_list.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_list.cmake has hash f5de3ebcbc40a4db90622ade9aca918e2cf404dc0d91342fcde457d730e6fa29
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_minimum_required.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_minimum_required.cmake has hash 4da8ab803b83c8f1c7b6272298108b9f62a7cd0618e563242c8e584692534171
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_replace_string.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_replace_string.cmake has hash d43c8699ce27e25d47367c970d1c546f6bc36b6df8fb0be0c3986eb5830bd4f1
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\vcpkg_test_cmake.cmake
[DEBUG] D:\vcpkg\scripts\cmake\vcpkg_test_cmake.cmake has hash 8117a509de7f30dd5c1f4c35134c1b3180c0825ea03480aa4625e98ddd5476e6
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\z_vcpkg_apply_patches.cmake
[DEBUG] D:\vcpkg\scripts\cmake\z_vcpkg_apply_patches.cmake has hash 1ddc151897aa15415dab3f222c1cac1a4056c8ddff9e63b5b3fde1bb8e06ddb4
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\z_vcpkg_escape_regex_control_characters.cmake
[DEBUG] D:\vcpkg\scripts\cmake\z_vcpkg_escape_regex_control_characters.cmake has hash 439c52c6ea37cecad4474528fb3b8019f2538380b3771d986e3d7811d8e274b5
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\z_vcpkg_fixup_rpath.cmake
[DEBUG] D:\vcpkg\scripts\cmake\z_vcpkg_fixup_rpath.cmake has hash 9efca0dc9594c2c2f094444cfbdc777cdcb9639a01435628d551127f4f4d735e
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\z_vcpkg_forward_output_variable.cmake
[DEBUG] D:\vcpkg\scripts\cmake\z_vcpkg_forward_output_variable.cmake has hash ae3440b77321516f29f0b51e26b8ecb05fd31f63d33949dc406a502c300b04ff
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\z_vcpkg_function_arguments.cmake
[DEBUG] D:\vcpkg\scripts\cmake\z_vcpkg_function_arguments.cmake has hash 11721a8a42a2aa2f6f285d485b21aed55834c2029140661bd8e2f0b709288d77
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\z_vcpkg_get_cmake_vars.cmake
[DEBUG] D:\vcpkg\scripts\cmake\z_vcpkg_get_cmake_vars.cmake has hash ce74da978727f15cc4eab6fa8a9c27023f0b51ef654cfbf7df8f3409fb950c43
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\z_vcpkg_prettify_command_line.cmake
[DEBUG] D:\vcpkg\scripts\cmake\z_vcpkg_prettify_command_line.cmake has hash 97e4e92ac6e9da544fc7b9a6695e0d491c2c095ec265d8c0a90bcb8168873ca3
[DEBUG] Trying to hash D:\vcpkg\scripts\cmake\z_vcpkg_setup_pkgconfig_path.cmake
[DEBUG] D:\vcpkg\scripts\cmake\z_vcpkg_setup_pkgconfig_path.cmake has hash 9bdbca9a026715b07908bca9786799b200c704ae826e7eb52f8bdcd5ca697254
[DEBUG] Trying to hash D:\vcpkg\scripts\ports.cmake
[DEBUG] D:\vcpkg\scripts\ports.cmake has hash 5a8e00cedff0c898b1f90f7d129329d0288801bc9056562b039698caf31ff3f3
[DEBUG]
[DEBUG]   0002-Config-for-MSVC.patch|7eb9dded5bc1e34a02d2bfa88f8c1cf1f454b3cf5e82d0d0c45cf7bf45a54c19
[DEBUG]   0003-Add-export.patch|e920b915952a0fb574a10538ac117e2d668465ea5353586296a923cb3319159d
[DEBUG]   0004-ModuleFileName.patch|5405e2493fa1846788e2bb2fd62334d2d98d2a5fa47a36a52047608472125d46
[DEBUG]   clang-fortify.patch|1e8bf046ffe3fe05d7b7485489a8aed80df5a084341c986a72b809aa91d9a500
[DEBUG]   cmake|3.25.1
[DEBUG]   features|core
[DEBUG]   portfile.cmake|eaa550cdedada1d2751461100f828bd856bc600632a08beecb1267b559698426
[DEBUG]   ports.cmake|5a8e00cedff0c898b1f90f7d129329d0288801bc9056562b039698caf31ff3f3
[DEBUG]   post_build_checks|2
[DEBUG]   powershell|7.2.11
[DEBUG]   triplet|x64-windows
[DEBUG]   triplet_abi|4556164a2cd3dd6f4742101eabb46def7e71b6e5856faa88e5d005aac12a803c-36b818778ba6f2c16962495caedb9a7b221d5be4c60de1cd3060f549319a9931-37ddf335dc10d14fa90c13a22cc1ec1cdbd1efcd
[DEBUG]   usage|d7cbdf659f9d8a102889357ffb9957ce898867c64c20e6afbe736bd21a85a887
[DEBUG]   vcpkg-cmake-wrapper.cmake|d83d9ca94c91ac33648d4286a7a7b855cf1abd53895e82832e389c3362d6c94f
[DEBUG]   vcpkg.json|e50251b8238ea5cf950f1688bd85c135bd3881d7bade4e655fa45c1a9925ff7f
[DEBUG]   vcpkg_configure_make|c343ff83697bd19846f265de24cd8a39af50c4d9ad581de68f033cb92294c2f0
[DEBUG]   vcpkg_copy_pdbs|d57e4f196c82dc562a9968c6155073094513c31e2de475694143d3aa47954b1c
[DEBUG]   vcpkg_copy_tool_dependencies|66eef4116a52fd8cba76d274f44904846df943a3fc52317871cf255733b2efc4
[DEBUG]   vcpkg_download_distfile|2d57e1336ae9daab2f04c0623217094b026080d19bdca3a92396d68ea3e729c7
[DEBUG]   vcpkg_extract_source_archive|a25e0132b36c30e9675f934042fb1164128864eeefa064ab8eabb1eb347aa381
[DEBUG]   vcpkg_install_make|8d8145837ce718ef60778b50fea1af272146c9efa42367ec2d7726332ef29ab5
[DEBUG]   vcpkg_list|f5de3ebcbc40a4db90622ade9aca918e2cf404dc0d91342fcde457d730e6fa29
[DEBUG]
[DEBUG] Trying to hash D:\vcpkg\buildtrees\libiconv\x64-windows.vcpkg_abi_info.txt
[DEBUG] D:\vcpkg\buildtrees\libiconv\x64-windows.vcpkg_abi_info.txt has hash 500f4f34682398251ff6253f250b130685cb1d851531c63b371b0001255ec4f9
[DEBUG] Default binary cache path is: C:\Users\김혁\AppData\Local\vcpkg\archives
Restored 0 package(s) from C:\Users\김혁\AppData\Local\vcpkg\archives in 122 us. Use --debug to see more details.
Installing 1/1 libiconv:x64-windows...
Building libiconv:x64-windows...
[DEBUG] Detecting host with IsWow64Process2
[DEBUG] CreateProcessW("D:\vcpkg\downloads\tools\cmake-3.25.1-windows\cmake-3.25.1-windows-i386\bin\cmake.exe" -DALL_FEATURES= -DCURRENT_PORT_DIR=D:/vcpkg/ports/libiconv -D_HOST_TRIPLET=x64-windows -DFEATURES=core -DPORT=libiconv -DVERSION=1.17 -DVCPKG_USE_HEAD_VERSION=0 -D_VCPKG_DOWNLOAD_TOOL=BUILT_IN -D_VCPKG_EDITABLE=0 -D_VCPKG_NO_DOWNLOADS=0 -DZ_VCPKG_CHAINLOAD_TOOLCHAIN_FILE=D:/vcpkg/scripts/toolchains/windows.cmake -DCMD=BUILD -DDOWNLOADS=D:/vcpkg/downloads -DTARGET_TRIPLET=x64-windows -DTARGET_TRIPLET_FILE=D:/vcpkg/triplets/x64-windows.cmake -DVCPKG_BASE_VERSION=2023-06-08 -DVCPKG_CONCURRENCY=17 -DVCPKG_PLATFORM_TOOLSET=v143 "-DGIT=C:/Program Files/Git/cmd/git.exe" -DVCPKG_ROOT_DIR=D:/vcpkg -DPACKAGES_DIR=D:/vcpkg/packages -DBUILDTREES_DIR=D:/vcpkg/buildtrees -D_VCPKG_INSTALLED_DIR=D:/vcpkg/installed -DDOWNLOADS=D:/vcpkg/downloads -DVCPKG_MANIFEST_INSTALL=OFF -P "D:\vcpkg\scripts\ports.cmake")
-- Using cached libiconv-1.17.tar.gz.
-- Cleaning sources at D:/vcpkg/buildtrees/libiconv/src/v1.17-84a471678e.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/vcpkg/downloads/libiconv-1.17.tar.gz
-- Applying patch 0002-Config-for-MSVC.patch
-- Applying patch 0003-Add-export.patch
-- Applying patch 0004-ModuleFileName.patch
-- Applying patch clang-fortify.patch
-- Using source at D:/vcpkg/buildtrees/libiconv/src/v1.17-84a471678e.clean
-- Found external ninja('1.11.0').
-- Getting CMake variables for x64-windows
-- Using cached msys2-autoconf-wrapper-20221207-1-any.pkg.tar.zst.
-- Using cached msys2-automake-wrapper-20221207-1-any.pkg.tar.zst.
-- Using cached msys2-binutils-2.40-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libtool-2.4.7-3-x86_64.pkg.tar.zst.
-- Using cached msys2-make-4.4.1-1-x86_64.pkg.tar.zst.
-- Using cached msys2-pkgconf-1.9.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-which-2.21-4-x86_64.pkg.tar.zst.
-- Using cached msys2-bash-5.2.015-1-x86_64.pkg.tar.zst.
-- Using cached msys2-coreutils-8.32-5-x86_64.pkg.tar.zst.
-- Using cached msys2-file-5.44-5-x86_64.pkg.tar.zst.
-- Using cached msys2-gawk-5.2.1-2-x86_64.pkg.tar.zst.
-- Using cached msys2-grep-1~3.0-6-x86_64.pkg.tar.zst.
-- Using cached msys2-gzip-1.12-2-x86_64.pkg.tar.zst.
-- Using cached msys2-diffutils-3.9-1-x86_64.pkg.tar.zst.
-- Using cached msys2-sed-4.9-1-x86_64.pkg.tar.zst.
-- Using cached msys2-msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst.
-- Using cached msys2-autoconf2.71-2.71-1-any.pkg.tar.zst.
-- Using cached msys2-automake1.16-1.16.5-1-any.pkg.tar.zst.
-- Using cached msys2-libiconv-1.17-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libintl-0.21-2-x86_64.pkg.tar.zst.
-- Using cached msys2-zlib-1.2.13-1-x86_64.pkg.tar.zst.
-- Using cached msys2-tar-1.34-3-x86_64.pkg.tar.zst.
-- Using cached msys2-findutils-4.9.0-3-x86_64.pkg.tar.zst.
-- Using cached msys2-gmp-6.2.1-2-x86_64.pkg.tar.zst.
-- Using cached msys2-gcc-libs-11.3.0-3-x86_64.pkg.tar.zst.
-- Using cached msys2-libbz2-1.0.8-4-x86_64.pkg.tar.zst.
-- Using cached msys2-liblzma-5.4.1-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libzstd-1.5.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libreadline-8.2.001-3-x86_64.pkg.tar.zst.
-- Using cached msys2-mpfr-4.2.0-2-x86_64.pkg.tar.zst.
-- Using cached msys2-libpcre-8.45-3-x86_64.pkg.tar.zst.
-- Using cached msys2-m4-1.4.19-2-x86_64.pkg.tar.zst.
-- Using cached msys2-perl-5.36.0-1-x86_64.pkg.tar.zst.
-- Using cached msys2-ncurses-6.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libcrypt-2.1-4-x86_64.pkg.tar.zst.
-- Using msys root at D:/vcpkg/downloads/tools/msys2/d7266db249278763
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1007: cmd_execute_and_stream_data() returned -1073740791 after  5472167 us
error: building libiconv:x64-windows failed with: BUILD_FAILED
[DEBUG] CreateProcessW("C:\Program Files\Git\cmd\git.exe" "--git-dir=D:\vcpkg.git" "--work-tree=D:\vcpkg.git" -c core.autocrlf=false show "--pretty=format:%h %cd (%cr)" -s --date=short HEAD)
[DEBUG] ReadFile() finished with GetLastError(): 109
[DEBUG] 1008: cmd_execute_and_stream_data() returned 0 after    56394 us
[DEBUG] Detecting host with IsWow64Process2
Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+libiconv
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[libiconv]+Build+error&body=Copy+issue+body+from+D%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
[DEBUG] D:\a_work\1\s\src\vcpkg\commands.install.cpp(572):
[DEBUG] Time in subprocesses: 8408552us
[DEBUG] Time in parsing JSON: 1650us
[DEBUG] Time in JSON reader: 1170us
[DEBUG] Time in filesystem: 22593us
[DEBUG] Time in loading ports: 13075us
[DEBUG] Exiting after 8.7 s (8642690us)

Please provide the config-x64-windows-dbg-err.log and config-x64-windows-dbg-out.log logs under the buildtrees directory of vcpkg.

libiconv.zip
all datas under the buildtrees

I could install this port successfully with the latest vcpkg 2023-06-08-19a3cb921a585fce63c0651f56a991a5a08bdc60, could you please run following commands in your vcpkg folder:
1. git pull
2. .\bootstrap-vcpkg.bat
3. .\vcpkg install libiconv:x64-windows --binarysource=clear

After reinstalling visual studio it works fine.
Thanks.

Ok, then I will close this issue.


Error sia_server.py", line 50, in handle_line line = str.strip(data.decode("ascii"))

Hi,
sometimes I get this error in the log:
2021-01-18 20:50:04 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pysiaalarm/aio/sia_server.py", line 50, in handle_line
line = str.strip(data.decode("ascii"))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x89 in position 20: ordinal not in range(128)
I cat give more examples or info if needed
Version of the custom_component and HA setup (version, OS, etc)
SIA
v0.3.10
HA
Version core-2021.1.4
supervisor-2021.01.5
Operating System Raspbian GNU/Linux 10 (buster)
Docker version 19.03.13
Configuration
Describe the bug
Debug log
2021-01-18 20:50:04 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pysiaalarm/aio/sia_server.py", line 50, in handle_line
line = str.strip(data.decode("ascii"))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x89 in position 20: ordinal not in range(128)

yeah, I've seen this sometimes during testing, not yet in real systems, are you using encryption? because if so, there are random numbers added to a message as padding and those sometimes cause this, let me know and I will see if I can catch this in the code.

yeah, I've seen this sometimes during testing, not yet in real systems, are you using encryption? because if so, there are random numbers added to a message as padding and those sometimes cause this, let me know and I will see if I can catch this in the code.

I have the same issue and yes - it's when encryption is enabled
2021-01-19 11:51:11 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/pysiaalarm/aio/sia_server.py", line 50, in handle_line
    line = str.strip(data.decode("ascii"))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x84 in position 1: ordinal not in range(128)
2021-01-19 11:51:16 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/pysiaalarm/aio/sia_server.py", line 50, in handle_line
    line = str.strip(data.decode("ascii"))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x80 in position 12: ordinal not in range(128)

I have the same issue and yes - it's when encryption is enabled
2021-01-19 11:51:11 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/pysiaalarm/aio/sia_server.py", line 50, in handle_line
    line = str.strip(data.decode("ascii"))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x84 in position 1: ordinal not in range(128)
2021-01-19 11:51:16 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/pysiaalarm/aio/sia_server.py", line 50, in handle_line
    line = str.strip(data.decode("ascii"))
UnicodeDecodeError: 'ascii' codec can't decode byte 0x80 in position 12: ordinal not in range(128)

Hi,
in my case the encryption is not enabled.
In the log I find different codes in different positions:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x94 in position 20: ordinal not in range(128)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe7 in position 23: ordinal not in range(128)
UnicodeDecodeError: 'ascii' codec can't decode byte 0x83 in position 20: ordinal not in range(128)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 21: ordinal not in range(128)
Although the message, just before the error, is correctly decoded, It seens it is lost

Hi,
in my case the encryption is not enabled.
In the log I find different codes in different positions:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x94 in position 20: ordinal not in range(128)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe7 in position 23: ordinal not in range(128)
UnicodeDecodeError: 'ascii' codec can't decode byte 0x83 in position 20: ordinal not in range(128)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 21: ordinal not in range(128)
Although the message, just before the error, is correctly decoded, It seens it is lost

Should be fixed now, please go into the custom components and change the manifest to mention package version: 2.0.9b4 and let me know! @scorbacella and @j2ko

Should be fixed now, please go into the custom components and change the manifest to mention package version: 2.0.9b4 and let me know! @scorbacella and @j2ko

Also just created new beta release for the integration which should have the fix for this as well.

Also just created new beta release for the integration which should have the fix for this as well.

can you check if you still see this after updating to the latest (v0.5.0b4)?

Hi Eduard, for me the last working release is the v0.4.0-beta.2.
What test can I do for you?
Just a question: if I reinstall the 0.5 beta 4 can I rollback to 0.4 beta 2 later? I don't see this version in the list of the available version in HACS.
Thanks

I just checked the difference in package and should be better now (made it as "wide" of a match as possible.). Sorry that it took some time, but hopefully this fixes it. I also changed the HA event format, to just include the whole SIA_Event in there, so you might need to check that if you are using attributes or event as trigger for automations.

I can confirm that I do not see this issue anymore after updating to the v0.5.0-beta.9 version.
@eavanvalkenburg Is there any stable version available with this fix?

yeah, I think so, the proper release of the package has it, and I think that is also included in the latest beta of this custom component, and that version is used in the official integration of HA.


Polymorphic component options in definition

There are a couple features regarding polymorphic component definitions that I think could be useful:

The ability to define the default intrinsic element type in the definition.
The ability to narrow the element options available in the as prop.

const Header = styled("header", {});

// Footer extends Header, but is still a "header" element.
const Footer = styled(Header, {});

const Page = () => (
  <Box>
    My site
    Site content
    2021
   {/* Awkward ⬆ */}
  </Box>
);

Possible Solutions

An as property in the definition

const Footer = styled(Header, {
  as: {
    default: "footer",
    // The `as` prop is narrowed to these options
    options: ["header", "footer", "div"],
  },
});

The default element as the third argument, with the as property as an array:

const Footer = styled(
  Header,
  {
    as: ["header", "footer", "div"],
  },
  "footer"
);

Thanks for the consideration!

A couple use cases where I think this could be especially useful:

I want to create a Heading component and narrow it to h1-h6 elements only
I want to create a Text element, and narrow it down to only elements that accept text as children

It would also be nice to be able to mark the as prop as required:
const Heading = styled(Header, {
  as: {
    required: true,
    default: "h1", // discriminated union error (can't combine required and default)
    options: ["h1", "h2", "h3", "h4", "h5", "h6"],
  },
});

And, to be able to define variants based on the intrinsic element:
const Heading = styled(Header, {
  as: {
    required: true,
    // default: "h1",
    options: ["h1", "h2", "h3", "h4", "h5", "h6"],
  },
  variants: {
    as: {
      // typed from options array above (if provided)
      h1: {
        fontSize: "$3xl",
      },
      h2: {
        fontSize: "$2xl",
      },
      h3: {
        fontSize: "$xl",
      },
      h4: {
        fontSize: "$lg",
      },
      h5: {
        fontSize: "$sm",
      },
      h6: {
        fontSize: "$xs",
      },
    },
  },
});

Hey, @gojutin! I believe the first feature described above relates closely to https://github.com/modulz/stitches/discussions/507 😄

I realized that the Stitches API already enables you to narrow the as prop, as well as specify styles for each polymorphic variant, just by specifying it explicitly in the variants property:
  variants: {
    as: {
      h1: {
        fontSize: "$3xl",
      },
      h2: {
        fontSize: "$2xl",
      },
      ...

Closing in favor of #507


solarized+tabs  ⇢  Text Wrapper failure

Info: - OS: window10 - Logseq ver: 20220830nightly - Theme ver: i have issue on SolExt theme with my custom.css?
Description:
① The Text Wrapper plugin does not work when using the solarized plugin theme and the tabs plugin is enabled. Specifically, when the text is selected, the Text Wrapper plugin's hover action bar will cover the text, which will affect the experience. As shown below

② But also using the solarized plugin theme, when I turn off the tabs plugin, Text Wrapper plug-in use will not have any problems, will not happen to block the selected text, as shown below

③ If the theme is not using the solarized plugin, turning on the tabs plugin will not affect the use of the Text Wrapper plugin either

Screenshots

check v2.1.5

still failure

update to latest, maybe reload LS (Ctrl+R)
just checked again (maybe LS 0.8.3 broke something, but not) - it works...

update , it is okey


Simulation being executed ONLY AFTER user confirmed desire to continue with transaction

I used a mix of docs, readme and the following VDO (https://youtu.be/nKRZ1R2BC4Q?t=587) to familiarize myself with Chainlink functions.
While doing so I came across the following behavior, which appears to deviate from the behavior outlined in the docs/tutorial videos. I hope I am not wrong about this ;) :
EXPECTED BEHAVIOR:

Executed npx hardhat functions-request --network polygonMumbai --contract [contractid] --subid [subid]
Code contained in the function will be simulated and run locally
CLI will provide a simulated result
CLI will THEN estimate fees and asks user to confirm that they are willing to proceed

OBSERVED BEHAVIOR (see screenshot below):

Executed npx hardhat functions-request --network polygonMumbai --contract [contractid] --subid [subid]
CLI estimated fees and asks user to confirm that they are willing to proceed
Only AFTER the user responded with YES will the function be simulated and run locally
CLI will provide a simulated result

Other than that, its a great example, and a wonderful 'getting started' experience.

Looks like the following line in ~/tasks/Functions-client/request.js got pushed down in the order of execution during the following commit: https://github.com/smartcontractkit/functions-hardhat-starter-kit/commit/0bd72821c5343a1266860382602efdf40712ca9c
Line in question:
const request = await generateRequest(requestConfig, taskArgs)
Will try to submit a PR to propose a fix.

Thank you for raising this issue!
I think we need to make a few changes in order for this logic to work for both single Functions requests and Automation Functions requests.
I have filed an internal ticket to resolve.

Resolved in develop
Thank you for raising!


Etcher from source error in Debian

What Etcher version are you running?
v1.0.0-beta.10 - 2016-06-27

What operating system and architecture are you running Etcher in?
Linux huayra 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux

What is the behaviour you're experiencing? How can we reproduce it?
I clone the repo, do "npm install" :

npm WARN package.json<EMAIL_ADDRESS>'repositories' (plural) Not supported.
npm WARN package.json Please pick one as the 'repository' field
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm ERR! notsup Unsupported
npm ERR! notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: x64

npm ERR! System Linux 3.16.0-4-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/alumno/programas/etcher
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.21
npm ERR! code EBADPLATFORM
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/alumno/programas/etcher/npm-debug.log
npm ERR! not ok code 0

and when execute "electron ."  The app  starts empty.

DevTools LOG:
Uncaught Error: Module did not self-register.
Uncaught Error: [$injector:modulerr] Failed to instantiate module Etcher due to:
Error: [$injector:nomod] Module 'Etcher' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.5.7/$injector/nomod?p0=Etcher
    at /home/alumno/programas/etcher/node_modules/angular/angular.js:68:12
    at /home/alumno/programas/etcher/node_modules/angular/angular.js:2075:17
    at ensure (/home/alumno/programas/etcher/node_modules/angular/angular.js:1999:38)
    at module (/home/alumno/programas/etcher/node_modules/angular/angular.js:2073:14)
    at /home/alumno/programas/etcher/node_modules/angular/angular.js:4608:22
    at forEach (/home/alumno/programas/etcher/node_modules/angular/angular.js:321:20)
    at loadModules (/home/alumno/programas/etcher/node_modules/angular/angular.js:4592:5)
    at createInjector (/home/alumno/programas/etcher/node_modules/angular/angular.js:4514:19)
    at doBootstrap (/home/alumno/programas/etcher/node_modules/angular/angular.js:1751:20)
    at bootstrap (/home/alumno/programas/etcher/node_modules/angular/angular.js:1772:12)
    at angularInit (/home/alumno/programas/etcher/node_modules/angular/angular.js:1657:5)
    at /home/alumno/programas/etcher/node_modules/angular/angular.js:31468:5
    at HTMLDocument.trigger (/home/alumno/programas/etcher/node_modules/angular/angular.js:3198:7)
    at defaultHandlerWrapper (/home/alumno/programas/etcher/node_modules/angular/angular.js:3488:11)
    at HTMLDocument.eventHandler (/home/alumno/programas/etcher/node_modules/angular/angular.js:3476:9)
http://errors.angularjs.org/1.5.7/$injector/modulerr?p0=Etcher&p1=Error%3A%…umno%2Fprogramas%2Fetcher%2Fnode_modules%2Fangular%2Fangular.js%3A3476%3A9)

Tnks for help.

Hi @DiegoAccorinti ,
Thanks for reaching out! Sadly, installing Etcher's dependencies is not as simple as doing an npm install. The whole process of configuring NPM to make use of Electron's v8 runtime when compiling dependencies is outlined in our CONTRIBUTING guide: https://github.com/resin-io/etcher/blob/master/docs/CONTRIBUTING.md#running-locally.
In summary:

You'll need to have the exact NodeJS version being used by the current Etcher's Electron version to avoid binary incompatibility (which at the time is v6.1.0).

You'll need to configure npm with the following environment variables:

export npm_config_disturl=https://atom.io/download/atom-shell
export npm_config_target=<ELECTRON_VERSION>
export npm_config_runtime=electron

At the time of this writing, the electron version we use if 1.1.1.

You'll need to run npm install with the --build-from-source option, to avoid pre-compiled packaged from being downloaded.

You'll need to install bower dependencies as well.

Let me know if you still get stuck in any of the above steps!

Hi @jviotti , tnks for respond.

You'll need to have the exact NodeJS version being used by the current Etcher's Electron version
to avoid binary incompatibility (which at the time is v6.1.0).

i downloaded and installed 6.0  , don't found 6.1  at https://nodejs.org/download/nightly/

You'll need to configure npm with the following environment variables

OK

You'll need to run npm install with the --build-from-source option, to avoid pre-compiled packaged from being downloaded.

OK !

You'll need to install bower dependencies as well.

OK !
only rest:
alumno@huayra:~/programas/etcher$ bower install
alumno@huayra:~/programas/etcher$ electron .
and it's READY.

tnks very much!
Diego.

Hi @DiegoAccorinti ,
I'm glad to hear you got it working! Enjoy, and don't hesitate to speak to us in out Gitter chat channel (https://gitter.im/resin-io/etcher) if there's anything else we can do for you.


Grouping AMI channels together + multi-channel cut API improvements

AMI can be a great testbed for multi-channel capabilities in Lhotse, so I'm making a few improvements in its preparation sript. The idea is that we can construct a CutSet with entries like this:

I'll still need to add tests so this is not finished.

Codecov Report

Merging #87 into master will decrease coverage by 0.13%.
The diff coverage is 42.85%.

@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
- Coverage   93.04%   92.91%   -0.14%
==========================================
  Files          37       37
  Lines        2717     2723       +6
==========================================
+ Hits         2528     2530       +2
- Misses        189      193       +4

Impacted Files
Coverage Δ

lhotse/cut.py
87.76% <33.33%> (-0.72%)
:arrow_down:

lhotse/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

I extended the PR to make it even easier to work with multi-channel cuts - now the load_features and load_audio methods on MixedCut can return either the mono-mix, or all the component tracks just before mixing, i.e. with offsets and SNRs applied to them, if they are defined.
I checked how it works on some AMI recordings (the plot_tracks_audio/features method use the updated mixing mechanism):

(BTW the difference in feature-domain mix is quite noticable from the time-domain mix when using 4 channels, but this is not likely that we're going to use it this way, rather a sanity check if all works OK in addition to unit tests)
It's ready for a final review and merge.

Great!
On Mon, Sep 28, 2020 at 12:06 PM Piotr Żelasko<EMAIL_ADDRESS>wrote:

I extended the PR to make it even easier to work with multi-channel cuts -
now the load_features and load_audio methods on MixedCut can return
either the mono-mix, or all the component tracks just before mixing, i.e.
with offsets and SNRs applied to them, if they are defined.
I checked how it works on some AMI recordings (the
plot_tracks_audio/features method use the updated mixing mechanism):
[image: image]
https://user-images.githubusercontent.com/15930688/94389538-1b15eb00-011e-11eb-928e-624556f0c722.png
(BTW the difference in feature-domain mix is quite noticable from the
time-domain mix when using 4 channels, but this is not likely that we're
going to use it this way, rather a sanity check if all works OK in addition
to unit tests)
It's ready for a final review and merge.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pzelasko/lhotse/pull/87#issuecomment-699757641, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZFLOY7YTFGQBAT6ENHFALSIADV3ANCNFSM4R3KH3CQ
.


Links in readme for XPlat Release Notes to samples are wrong

VSTS Extension you are using
XPlatform
Where are you running it?
VSTS marketplace
Version of Extension/Task
2.2.2.
Expected behaviour and actual behaviour
The links for the sample templates in the VSIX template readme are invalid. This is because the they have moved in the repo.
Steps to reproduce the problem
Follow the links, get 404 errors

Fixed in 2.3.2


Token to create orgA/repo from orgB template

I have been trying to enable a Github Workflow that should be able to create a new repo at orgA, using a template repo from orgB, I don't believe there is a chance to support this since the GitHub Apps tokens are scoped to an individual account or a specific org afaik, but it could be pretty useful to have a way to support this using GitHub Apps.
These are the steps, I'm trying to use:
      - name: Generate a token
        id: generate-token
        uses: actions/create-github-app-token@v1
        with:
          app-id: ${{ secrets.ZCLOUD_BOT_APP_ID }}
          private-key: ${{ secrets.ZCLOUD_BOT_APP_PRIVATE_KEY }}
          owner: ${{ github.event.inputs.repo-org }}

      - name: Create the new repo
        id: create-repo
        env:
          GITHUB_TOKEN: ${{ steps.generate-token-template.outputs.token }}
        run: |
          gh repo create ${{ github.event.inputs.repo-org }}/${{ github.event.inputs.repo-name }} \
            --internal \
            --template ${{ github.repository }}

This is similar to Issue 45, but I can't use the matrix approach since permission to both orgs is required between the same command exec.

Unless the template repository is open source, I don't think this is possible with a GitHub App installation access token, because by design an installation access token only has access to the account that the installation belongs to. There are no cross-account installations

Thanks for the clarification @gr2m 👌🏼, my workaround for this was to git checkout the repo using the GitHub Workflow token, clean the git repo history, and then use the GitHub App access token to create the new repo.
      - name: Generate a token
        id: generate-token
        uses: actions/create-github-app-token@v1
        with:
          app-id: ${{ secrets.BOT_APP_ID }}
          private-key: ${{ secrets.BOT_APP_PRIVATE_KEY }}
          owner: ${{ github.event.inputs.repo-org }}

      - name: Checkout template repo
        id: checkout
        uses: actions/checkout@v4

      - name: Initialize the new repo
        id: init-repo
        run: |
          ## clean git
          rm -rf .git

          ## set git config
          git config --global init.defaultBranch main

          ## commit initial files
          git init
          git config user.name "${{ vars.BOT_APP_NAME }}[bot]"
          git config user.email "${{ secrets.BOT_APP_ID }}+${{ vars.BOT_APP_NAME<EMAIL_ADDRESS>          git add .
          git commit -m "initial commit [skip ci]"

      - name: Create the new repo
        id: create-repo
        env:
          GITHUB_TOKEN: ${{ steps.generate-token.outputs.token }}
        run: |
          gh repo create ${{ github.event.inputs.repo-org }}/${{ github.event.inputs.repo-name }} \
            --internal \
            --source=. \
            --remote=upstream \
            --push
        ##--template ${{ github.repository }}


[DropDown] ui simple dropdown  does not work on mobiles

It works on computer's browsers but IT DOES NOT WORK on Mobiles :iphone: (Safari, Chrome).
See the link below:
https://reactgirl.github.io/portifolio/issue01.html

This seems to work in Chrome on Android but doesn't in Chrome or Safari on iOS.

https://github.com/Semantic-Org/Semantic-UI/issues/6575

Is there anything new with this? This is coming up for my project.

A thing Semantic Framework is dead.

How come? It's still wildly in use

Hasn't been updated since October 2018. In March 2018 @jlukic said:

SUI is used in production for many large apps, and will continue to receive patch/release updates about every month or so at a pace that is reasonable.

He did follow through with that goal until October when 2.8 was released and he disappeared again. fomantic/Fomantic-UI has been active since at least June 2018 and are still doing regular releases and planning for the future of the framework.
If Semantic works for you then you can keep using it mostly fine, but if you want new features (calendar, slider, toasts, updated icons, emojis) or bug fixes that have been outstanding on this repo for some time then I would highly recommend you transition to Fomantic. It can be a drop in replacement, from my experience.

Thank you, I will look into it


aboud bluetooth detected

PSMoveConfigTool not detected though bluetooth is inserted in the USB.
and, PSMoveService display [bluetooth_get_host_address - Failed to find a bluetooth radio].
Where is it wrong?

This sounds like a troubleshooting question. Please post it to the Google group instead of the issues page.
https://groups.google.com/forum/#!forum/psmoveservice
If we determine that it's an actual bug, we'll create an issue for it.


ALL TEN PERCENT STOCK BOARDS

CORRECTION: EPA TOPIC: ENVIROMENTAL TOOLS:

CORRECTION TO DATA MOVER: DATA DOWNLOADER: PATH DOWNLOAD\FTP\LIBRARY?


Keyp wallet

This PR adds Keyp wallet as an option for connecting to the app. Keyp wallet will appear and function the same as a standard EOA wallet, with the exception of showing the keyp account username in the wallet component instead of the wallet address.
Keyp wallet
https://docs.usekeyp.com/
Keyp provides an Ethereum wallet that is not custodied by the end user, but can be accessed via Keyp account authentication.
Concepts
Authentication
Connecting a Keyp wallet requires the user to authenticate with the Keyp API. The API then redirects back to the app, where user details (i.e. wallet address, username) are stored in the session using next-auth.
Chain
Keyp wallets are cross-chain. For contract writes, the chain is specified in the configuration of the Keyp client. The client will be determined by a .env var KEYP_CLIENT_ID.
useJBWallet() hook
Previously we've used useWallet() to get connected wallet details, like userAddress and chain. We should now rely on useJBWallet(), which wraps useWallet() as well as the connected Keyp wallet details via useSession(). The useJBWallet().keyp.chain object is simply a helper property for consistency with  that matches the chain of readProvider.

90% of this PR is just replacing useWallet() instances.

WalletContext / WalletProvider
Previously we've used the useWallet().connect function to connect a wallet, which includes its own modal UI. We'll now use components provided in WalletProvider to connect a wallet, which includes a modal for choosing either an EOA wallet or a keyp wallet, then allowing the user to connect accordingly. By placing these components in a context provider at the top of the tree, we can enable the login sequence anywhere (i.e. from the Navbar button, the pay modal, or the transactor hook)
Transactions
The Transactor automatically handles transactions from Keyp wallets alongside EOA wallets. Keyp wallet transactions are sent to the Keyp API, added to the TxHistoryContext, and tracked the same as transactions from EOA wallets. Components initiating transactions don't need any changes.
Keyp db user authentication
Keyp wallet API does not support signatures. Because the user must authenticate via Keyp to connect their Keyp wallet, we bypass the wallet signature when creating or logging in a DB user with a Keyp wallet.

guessing we can close this ? :(

@peripheralist gonna close, just doing some cleanup. Will pin this PR somewhere in Discord incase we need to come back and steal some stuff from it.


An error occurred. Error message: "fetch failed". Please consider reporting this error at

An error occurred. Error message: "fetch failed". Please consider reporting this error at

Yes, I'm aware of this issue affecting several installations of giscus. It doesn't seem to affect https://giscus.app or my own website, though, so I'm not sure what the issue is. I'm at work at the moment so I can't fix this until later tonight.

Same here, I think it's a general issue at the moment.

ok thanks,I thought it was my network problem, but it seems it isn't

It doesn't seem to affect https://giscus.app or my own website, though

Comments in https://giscus.app seem to be down as well.

Ah, just realised that I was logged in to giscus.app and my website so I didn't see the issue. Yeah the cache server seems to have gone offline for some reason. I've restarted, now it should work again. Thanks for reporting!


doc: add Customization document Traditional Chinese Translation

Traditional Chinese Translation
Co-authored-by: Echoring<EMAIL_ADDRESS>

Can you add links from the other docs to this one?


Update policy-csp-update.md

We have MDMs who need to be aware that the value of 32 has been deprecated as a supported value for branch readiness level on Win. 10 version 1903 and beyond. Please update ASAP.

@ManikaDhiman Please review this PR that updates deprecated value of 32 in the Policy CSP article. Thank you.

@officedocsbot assign @e0i


[ISSUE #1526] update all map fetch value

Made changes for fetching value using the key from the map as per suggestion in #1526
Fixes #1526
Documentation

Does this pull request introduces a new feature? no
If yes, how is the feature documented? not applicable
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation

please solve the conflict @venu-prasanna

hi，@venu-prasanna , may I know why this pr modify GRCP proto generate file?

@xwm1992  SimpleMessage in grpc proto is in wrong status after generated .

Task :eventmesh-common:compileJava FAILED
FAILURE: Build failed with an exception.

/Users/fys/project/test/incubator-eventmesh/eventmesh-common/src/main/java/org/apache/eventmesh/common/protocol/grpc/protos/SimpleMessage.java:81: 错误: 程序包RFequestHeader不存在
                        RFequestHeader.Builder subBuilder = null;
                                      ^

This's should be a wrong merge.  This is no RFequestHeader ( Should be RequestHandler )  .


version not found

I'm trying install specific version for my ember-data and after running this command
$ ember install<EMAIL_ADDRESS>I got:
version not found<EMAIL_ADDRESS>Error: version not found<EMAIL_ADDRESS> at setData (/Users/u/Projects/iRonin/time_tracking/web-app-ember/node_modules/ember-cli/node_modules/npm/lib/cache/add-named.js:137:12)   at RES (/Users/u/Projects/iRonin/time_tracking/web-app-ember/node_modules/ember-cli/node_modules/npm/node_modules/inflight/inflight.js:23:14)   at f (/Users/u/Projects/iRonin/time_tracking/web-app-ember/node_modules/ember-cli/node_modules/npm/node_modules/once/once.js:17:25)   at fixName (/Users/u/Projects/iRonin/time_tracking/web-app-ember/node_modules/ember-cli/node_modules/npm/lib/cache/add-named.js:29:5)   at saved (/Users/u/Projects/iRonin/time_tracking/web-app-ember/node_modules/ember-cli/node_modules/npm/lib/cache/caching-client.js:173:7)   at FSReqWrap.oncomplete (fs.js:95:15)
Is it possible to install 1.1.2 or should I update ember-data?

Arghh .. I forgot to publish that @rafaltrojanowski .. keep forgetting to npm publish after I make a new version. Anyway .. just did that .. so thanks for the reminder :)


Unity crash always

Well, I have a problem. Unity crashes at any time that I play the scene, I reviewed the issues and this is caused because of the library is looking for the Language Model.
I tried cloning the repository using git lfs clone ..., but this neither works.

Hey there!
I'm sorry to hear that you're having some trouble with the PocketSphinx example. Although I'm going to need some more information here. Do you encounter any errors when Unity crashes?
Also could you check the size of your language model file, then provide me with the file-size?
Thanks!

Hi @Funnyguy77, I don't any idea if I have any language model file, does this repo include one?
Also, if not, where can I find one? I don't exactly how to build although I know where is the tutorial on the official cmusphinx website.
Thanks for your quick response!

Here it is
Assets/StreamingAssets/en-us.tar

Ok, I have this file, but I don't see any reference of "StreamingAssets" in code, neither any unzip method and neither any documentation related about what to do with this file. Sorry, I'm missing something. Thanks for your help @jin-archipin !!


Scene Graph

Is your feature request related to a problem? Please describe.
N/A
Describe the solution you'd like
Translate scene graph code from old uTernion library
Describe alternatives you've considered
N/A
Additional context
N/A

Consider Unity-like implementation.


--disable-direct-write stopped working

VSCode Version: 1.6.0
OS Version: Windows 7

Steps to Reproduce:

add --disable-direct-write when starting vscode

Related: https://bugs.chromium.org/p/chromium/issues/detail?id=579678
This behaviour makes vscode unusable for me as I work with clear type disabled and use Courier New as font to get pixel perfect font rendering (at least that's how it was before 1.6). All font rendering in vscode is now blurry. I have a standard dpi display (~96dpi).

EDIT: I downgraded to 1.5.3 now. Nice crisp fonts again...

@letmaik I am playing around with a newer version of Electron and was wondering if you could give this build a try that includes it to see if something has changed with this issue: https://az764295.vo.msecnd.net/insider/d47c8ba23ff35913052db316aaeef1bb92b0dd99/VSCode-win32-1.8.0-insider.zip
Thanks

@bpasero I just tested it with the --disable-direct-write flag but no improvement.

They (Chrome) might have taken out this feature for good...

Todays VS Code insider build comes with Electron 1.6.x, would be interesting to hear if this update solves this issue for anyone: http://code.visualstudio.com/Download#insiders

This is clearly an upstream issue (see the linked Chromium issue) and won't be fixed by Google, unfortunately. So, I guess, let's all switch to high-DPI displays and live our lives, I got one now.

--disable-directwrite-for-ui source

@eamodio Afaik this option is only for the UI elements like the main application menu, not for regular content.

oh you're right..
well not quite the same thing as directwrite font fallback but this improves the clarity of the content for me --disable-lcd-text+--disable-font-antialiasing.
also available (optional, overkill) --ppapi-antialiased-text-enabled=0 --ppapi-subpixel-rendering-setting=0 --disable-composited-antialiasing=1

It's not pixel perfect though with Courier New, right?


Darwin 8.6.2 installation problem

I attempted to use ghcup to install GHC 8.6.2 on OS X (High Sierra, 10.13.6). After ghcup fetched the GHC package and began installation, I ultimately saw a great many lines like
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: /Users/.../.ghcup/ghc/8.6.2/lib/ghc-8.6.2/rts/libHSrts_thr_p.a(elf_reloc_aarch64.thr_p_o) has no symbols
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: /Users/.../.ghcup/ghc/8.6.2/lib/ghc-8.6.2/rts/libHSrts_thr_p.a(elf_util.thr_p_o) has no symbols
/Library/Developer/CommandLineTools/usr/bin/ranlib: file: /Users/.../.ghcup/ghc/8.6.2/lib/ghc-8.6.2/rts/libHSrts_thr_p.a(Select.thr_p_o) has no symbols

and then the installation terminated with
"utils/ghc-cabal/dist-install/build/tmp/ghc-cabal-bindist" copy libraries/ghc-prim dist-install "strip" '' '/Users/.../.ghcup/ghc/8.6.2' '/Users/.../.ghcup/ghc/8.6.2/lib/ghc-8.6.2' '/Users/.../.ghcup/ghc/8.6.2/share/doc/ghc-8.6.2/html/libraries' 'v p dyn'
dyld: Library not loaded: /usr/local/opt/gmp/lib/libgmp.10.dylib
  Referenced from: /private/var/folders/lm/ybj5rc1d5mq7523vdb2fry240000gn/T/tmp.M17dAytH/ghc-8.6.2/libraries/base/dist-install/build/libHSbase-<IP_ADDRESS>-ghc8.6.2.dylib
  Reason: image not found
make[1]: *** [install_packages] Abort trap: 6
make: *** [install] Error 2
Failed to install, consider updating this script via: ghcup upgrade

Can you show the output of ghcup debug-info? Additionally, a complete log via ghcup --verbose install 8.6.2 would be helpful.

@phadej Yikes! I had no idea that was a GHC issue, but that makes sense. As a I test I tried ghcup install which did successfully install a working ghc == 8.4.4 on my Darwin system. So I'll close this since it's not a ghcup issue. Thanks!

By the way, I wanted to say: thank you so much for writing this tool! I love it!

Is this requirement documented somewhere? I think the next user might have the same problem. These issues should be documented e.g. here https://www.haskell.org/ghc/download_ghc_8_6_2.html#binaries and our documentation/error messages should point users directly to it. Otherwise this is a usability issue.

@hasufell AFAICT the issue is a bug in the GHC build process that is slated to be fixed in a future release, maybe 8.6.3.

GHC 8.6.3 is out with the fix

Great! That makes me wonder if ghcup could blacklist 8.6.2 on Darwin to help people avoid the issue. :) Thanks for the update.

We already have a tag bad for ghc versions: https://github.com/haskell/ghcup/blob/master/.available-versions#L8
But I haven't really decided on how to use it yet. Because ghcup should be non-interactive... how would you tell the user he's installing a bad version? Basically, he can or should run ghcup list first, no?

how would you tell the user he's installing a bad version?

One possibility is to make ghcup require an extra argument like --force when installing something tagged with bad. If that argument is missing, bail and report an error that the bad thing cannot be installed unless the user is totally sure (via --force).


Autocomplete displays duplicated names for arguments

With this commit, when you invoke the auto complete, it prints duplicate names for the arguments.
I think this line should be reverted back to:
fmt.Fprintf(buf, "${%d:%s}", i+1, name)

Margo version: r18.03.23-1
Thanks.

@arsham thanks for spotting this,  I will release a fix tomorrow.


Trying to generate React bindings in non-tsx files?

Apologies if this is not the right place for questions, but I've started porting a site build system I have from Webpack to Fuse-box and ran into a snag. I would appreciate any input.
The project in question uses TypeScript 2.2 + React + Redux + PostCSS. This is my current attempt at a build script:
const fsbx = require("fuse-box");

fsbx.FuseBox.init({
    homeDir: "src/",
    outFile: "./dist2/app.js",
    sourceMap: {
        bundleReference: "app.js.map",
        outFile: "./dist2/app.js.map",
    },
    plugins: [
        fsbx.TypeScriptHelpers(),
    ]
}).devServer(">[ts/main.tsx]");

When I run this, I get this message:
$ node build
16:30:54 : Launching dev server on port 4444
  → Typescript config:  \tsconfig.json
Acorn error: Unexpected token (13:4)
File: D:\<...>\src\ts\data\stores\reducers\search.ts

11      React.createElement("string", null,
12          "):ISearch => ",
13      ,
14          " ",
15          React.createElement(model_1.ISearch, null,
16              "Object.assign(",
17              ", state, ",

So it's apparently trying to interpret that file as a React file, and tripping on the comma at line 13. But it's not what the file is; it's just a reducer to a Redux store. This is its full contents:
import { Action, handleActions } from "redux-actions";
import { ISearch } from "./../model";
import {
	CLEAR_SEARCH_TEXT,
	SET_SEARCH_TEXT,
} from "./../actions";

const initialState:ISearch = <ISearch>{
	text: "",
};

export default handleActions<ISearch, any>({
	[SET_SEARCH_TEXT]: (state:ISearch, action:Action<string>):ISearch => {
		return <ISearch>Object.assign({}, state, {
			text: action.payload,
		});
	},
	[CLEAR_SEARCH_TEXT]: (state:ISearch, action:Action<void>):ISearch => {
		return <ISearch>Object.assign({}, state, {
			text: "",
		});
	},
}, initialState);

A wild guess is that it's getting tripped by the < and > in the generics method declaration, but that seems... silly.
Anyone know what I'm doing wrong? The tsx-ish examples I've found are all over the place and they just mention automatic ts/tsx interpretation.
My tsconfig, for reference:
{
	"compilerOptions": {
		"target": "es6",
		"module": "commonjs",
		"strictNullChecks": true,
		"noUnusedParameters": false,
		"noUnusedLocals": true,
		"noImplicitAny": true,
		"noImplicitThis": true,
		"noImplicitReturns": true,
		"sourceMap": true,
		"jsx": "react"
	},
	"include": [
<EMAIL_ADDRESS>		"./src/ts/**/*"
	],
	"exclude": [
		"./dist/**"
	],
	"compileOnSave": false
}

Update: it seems the part that's tripping the compiler is any <...> cast, not the generic method. In the above case, all <ISearch>... casts cause it to fail. Replacing it by the other casting syntax (... as ISearch) makes it work.
After fixing search.ts above, another file was running into the same problem. This was was the faulty code:
if (this.sequences[i] !== null) {
	(<FweenSequence>this.sequences[i]).update();
} else {

Changing it to this fixes the issue:
if (this.sequences[i] !== null) {
	(this.sequences[i] as FweenSequence).update();
} else {

So there we go.

@zeh hi!
It seems like fusebox does not understand your .ts file.
Acorn error: Unexpected token (13:4)
File: D:\<...>\src\ts\data\stores\reducers\search.ts

You should not be seeing that. This one \src\ts\data\stores\reducers\search.js what it should have transpiled to.
Also, there might be an issue with the latest TypeScript 2.2, I am not sure if it helps dropping the version, but that definitely looks like a bug. Could you try typescript 2.1.6 + cleaning the cache?
Thanks

Hey @nchanged, thanks for the response.
Same error on TS 2.1.6 + cleared cache.
I managed to get past that error by removing all <ISearch> casts though. So it's still an error, but at least one that can be circumvented.

@zeh good one.
Can you confirm that the code that bugged up compiles without problems with just using the typescript compiler? All I am saying, can we blame fusebox?
Thanks.

@nchanged It definitely compiles. Castings might be uncommon but it's legal TypeScript and I currently use it within my webpack/tsc build with no problem.

Can I kindly ask you to take a look at this piece
Do you think it might be somewhat different from the CLI interface? And if you have an idea how to fix it, please share ;-)

@zeh as a fellow user of fusebox, if you can share an example project I will hack hard at it till I get it to work for you :rose:

@nchanged Thanks so much for the link. I see now what the issue is.
Because fuse-box is calling typescript.transpileModule for the file without passing its filename, the TypeScript transpiler doesn't know whether to interpret the source as a .ts or a .tsx file. Therefore it follows tsconfig's value: if jsx is set to react, it will always interpret the file as .tsx.
As per the API documentation:

Usually TypeScript compiler uses file extension to determine if file should be parsed as '.tsx' or '.ts'. The same rule is applied during single file transpilation if the file name is provided. If the file name is omitted, then compiler will check if the jsx options is specified. If it is set and is not JsxEmit.None, then source text will be interpreted as '.tsx'.

I've submitted a small PR that attempts to do so, so fuse-box will follow tsc's behavior more closely.

Now. With that said, <...> casts does seem to be a TypeScript issue. It's reported here: #6897.
The gist of it is: sure, <X>... castings are legal, but break the compiler in tsx files, therefore they are not recommended. Using ...as X seems to be the recommended way.
My current webpack/tsc/babel stack was following the compiler behavior, and that's why it was working.
@basarat Thanks. I was going to do that, but decide to take a look at the source and ended up running into the solution earlier than I expected.

Closed; fixed by #216. Thanks @nchanged.

@zeh stunning! thanks a billion!

but they're not recommended anyway

True. I always use as https://basarat.gitbooks.io/typescript/content/docs/types/type-assertion.html :rose:


Respect stream argument for openAI

Description
stream is set inside of convertArgs based off of the config or defaulted to true. By overriding it here, you make it impossible to set it as anything different inside the config.
Checklist

[x] The base branch of this PR is dev, rather than main
[ ] The relevant docs, if any, have been updated or created

Screenshots
[ For visual changes, include screenshots. ]
Testing
[ For new or modified features, provide step-by-step testing instructions to validate the intended behavior of the change. ]

@Lash-L Are you using
"completionOptions": {
        "stream": true
      }

to set stream: false?
I think this is partially a problem of ill-defined logic, but rather than forcing all of the instances of _streamComplete to also support non-streaming, it would be better to call _streamComplete vs. _complete depending on whether stream is set to true or false

@Lash-L Are you using

"completionOptions": {

        "stream": true

      }

to set stream: false?
I think this is partially a problem of ill-defined logic, but rather than forcing all of the instances of _streamComplete to also support non-streaming, it would be better to call _streamComplete vs. _complete depending on whether stream is set to true or false

Yeah, that's what I am currently doing - your approach seems much better. I'll see if I can change it

So the problem with calling stream complete vs complete is that complete calls _streamChat, which in turn calls _legacystreamComplete.

I see what you mean. Seems what we should do here is write _complete so that it uses its own logic instead of _streamChat, and generally untangle the logic where everything points toward _streamChat

https://github.com/continuedev/continue/pull/2700
did this for ollama

Hey @Lash-L, I'm going to close this for now since the scope has changed a bit—I think the right thing to do here is untangle the _streamChat and _streamComplete functions first

Hey @Lash-L, I'm going to close this for now since the scope has changed a bit—I think the right thing to do here is untangle the _streamChat and _streamComplete functions first

Sounds good, thank you!


Update go.mod

Updated go.mod for installing conventions, currently trying to install dsieve with go install github.com/trickest/dsieve produces:
go: github.com/trickest/dsieve@latest: <EMAIL_ADDRESS>parsing go.mod:
        module declares its path as: dsieve
                but was required as: github.com/trickest/dsieve

Thanks a lot @six2dez!