[CMake] Use llvm-config to locate Findzstd.cmake

LLVM17 now depends on -lzstd when the --link-static option is used. I.e:
$ llvm-config-16 --link-static --system-libs
-lrt -ldl -lm -lz -ltinfo -lxml2

$ llvm-config-17 --link-static --system-libs
-lrt -ldl -lm -lz -lzstd -ltinfo -lxml2

The current cmake rules aren't able to find the "Findzstd.cmake", resulting in a cmake error. This commit uses llvm-config --cmakedir to locate "Findzstd.cmake" which defines a set of rules to find zstd in the system. The zstd library is already installed as part of: https://github.com/apache/tvm/pull/15799/files#diff-c2c0605a8fdd4f5600690a8c7b1ec769882426af1b0ed01e8aaa0814e3a8f5dbR48

I was trying to fix the zstd dependency a while ago but it unfortunately didn't work out :(

BTW, Findzstd.cmake is supposed to provided by LLVM

Ah I missed #15479 thanks :)

BTW, Findzstd.cmake is supposed to provided by LLVM

Thanks that makes more sense. I wonder if we can rely on llvm-config --cmakedir to give the location instead? I can take a closer look tomorrow

tbh I'm not an expert and don't have much idea what the best approach is. happy to get this PR in if it works!

I feel like the new approach is more robust, but happy to revert @junrushao if you think otherwise

BTW could you confirm if it works with LLVM-17 on Windows? I was having some trouble prevo

I'm afraid I don't have a windows machine at hand to check

I think we should get this commit in anyways. In the worst case, it does no harm

Well, I got the error below on Windows:
D:\a\package\package>cd tvm

D:\a\package\package\tvm>rd /s /q build
The system cannot find the file specified.

D:\a\package\package\tvm>mkdir build

D:\a\package\package\tvm>cd build

D:\a\package\package\tvm\build>cmake -A x64 -Thost=x64       -G "Visual Studio 17 2022"       -DUSE_LLVM="llvm-config --link-static"       -DZLIB_USE_STATIC_LIBS=ON       -DUSE_RPC=ON       -DUSE_VULKAN=ON       ..
-- The C compiler identification is MSVC 1[9](https://github.com/mlc-ai/package/actions/runs/6766922543/job/18407590080#step:8:10).37.32825.0
-- The CXX compiler identification is MSVC 19.37.32825.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Build with RPC support...
-- Build with Graph Executor support...
-- Build with profiler...
-- Build with AOT Executor support...
-- Could NOT find GTest (missing: GTEST_LIBRARY GTEST_INCLUDE_DIR GTEST_MAIN_LIBRARY)
-- Didn't find the path to CCACHE, disabling ccache
-- Performing Test SUPPORT_CXX17
-- Performing Test SUPPORT_CXX17 - Success
-- VTA build is skipped in Windows..
-- Vulkan_INCLUDE_DIRS=C:/Miniconda/envs/tlcpack-build/Library/includeC:/Miniconda/envs/tlcpack-build/Library/include/spirv-toolsC:/Miniconda/envs/tlcpack-build/Library/include/spirv/unified1C:/Miniconda/envs/tlcpack-build/Library/include/spirv/unified1
-- Vulkan_LIBRARY=C:/Miniconda/envs/tlcpack-build/Library/lib/vulkan-1.lib
-- Vulkan_SPIRV_TOOLS_LIBRARY=C:/Miniconda/envs/tlcpack-build/Library/lib/SPIRV-Tools.lib
-- Build with Vulkan support
-- Use llvm-config=llvm-config --link-static
-- LLVM libdir: C:\Miniconda\envs\tlcpack-build\Library\lib
-- LLVM cmakedir: C:\Miniconda\envs\tlcpack-build\Library\lib\cmake\llvm
-- LLVM linker flag: psapi.lib
-- LLVM linker flag: shell32.lib
-- LLVM linker flag: ole32.lib
-- LLVM linker flag: uuid.lib
-- LLVM linker flag: advapi32.lib
-- LLVM links against zlib
-- Found ZLIB: C:/Miniconda/envs/tlcpack-build/Library/lib/zlibstatic.lib (found version "1.2.13")
CMake Error at C:/Miniconda/envs/tlcpack-build/Library/lib/cmake/llvm/Findzstd.cmake:39 (string):
  string sub-command REGEX, mode REPLACE: regex "$" matched an empty string.
Call Stack (most recent call first):
  cmake/utils/FindLLVM.cmake:177 (find_package)
  cmake/modules/LLVM.cmake:31 (find_llvm)
  CMakeLists.txt:544 (include)

-- Found zstd: C:/Miniconda/envs/tlcpack-build/Library/lib/zstd.lib
-- LLVM links against static zstd
-- LLVM linker flag under LLVM libdir: C:\Miniconda\envs\tlcpack-build\Library\lib/xml2.lib
-- Found LLVM_INCLUDE_DIRS=C:\Miniconda\envs\tlcpack-build\Library\include
-- Found LLVM_DEFINITIONS=-D_CRT_SECURE_NO_DEPRECATE;-D_CRT_SECURE_NO_WARNINGS;-D_CRT_NONSTDC_NO_DEPRECATE;-D_CRT_NONSTDC_NO_WARNINGS;-D_SCL_SECURE_NO_DEPRECATE;-D_SCL_SECURE_NO_WARNINGS;-DUNICODE;-D_UNICODE;-D__STDC_CONSTANT_MACROS;-D__STDC_FORMAT_MACROS;-D__STDC_LIMIT_MACROS
-- Found LLVM_LIBS=C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMWindowsManifest.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMXRay.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLibDriver.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDlltoolDriver.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMCoverage.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLineEditor.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMXCoreDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMXCoreCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMXCoreDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMXCoreInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMX86TargetMCA.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMX86Disassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMX86AsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMX86CodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMX86Desc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMX86Info.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMWebAssemblyDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMWebAssemblyAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMWebAssemblyCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMWebAssemblyUtils.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMWebAssemblyDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMWebAssemblyInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMVEDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMVEAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMVECodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMVEDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMVEInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSystemZDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSystemZAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSystemZCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSystemZDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSystemZInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSparcDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSparcAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSparcCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSparcDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSparcInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMRISCVTargetMCA.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMRISCVDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMRISCVAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMRISCVCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMRISCVDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMRISCVInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMPowerPCDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMPowerPCAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMPowerPCCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMPowerPCDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMPowerPCInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMNVPTXCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMNVPTXDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMNVPTXInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMSP430Disassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMSP430AsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMSP430CodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMSP430Desc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMSP430Info.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMipsDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMipsAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMipsCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMipsDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMipsInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLoongArchDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLoongArchAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLoongArchCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLoongArchDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLoongArchInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLanaiDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLanaiCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLanaiAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLanaiDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLanaiInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMHexagonDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMHexagonCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMHexagonAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMHexagonDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMHexagonInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBPFDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBPFAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBPFCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBPFDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBPFInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAVRDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAVRAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAVRCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAVRDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAVRInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMARMDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMARMAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMARMCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMARMDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMARMUtils.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMARMInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAMDGPUTargetMCA.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAMDGPUDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAMDGPUAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAMDGPUCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAMDGPUDesc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAMDGPUUtils.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAMDGPUInfo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAArch64Disassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAArch64AsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAArch64CodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAArch64Desc.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAArch64Utils.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAArch64Info.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMIntelJITEvents.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMOrcJIT.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMWindowsDriver.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMCJIT.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMJITLink.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMInterpreter.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMExecutionEngine.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMRuntimeDyld.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMOrcTargetProcess.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMOrcShared.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDWP.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDebugInfoLogicalView.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDebugInfoGSYM.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMOption.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMObjectYAML.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMObjCopy.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMCA.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMCDisassembler.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLTO.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMPasses.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMCFGuard.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMCoroutines.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMipo.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMVectorize.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMLinker.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMInstrumentation.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMFrontendOpenMP.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMFrontendOpenACC.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMFrontendHLSL.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMExtensions.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDWARFLinkerParallel.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDWARFLinker.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMGlobalISel.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMIRParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAsmPrinter.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSelectionDAG.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMCodeGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMTarget.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMObjCARCOpts.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMCodeGenTypes.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMIRPrinter.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMInterfaceStub.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMFileCheck.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMFuzzMutate.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMScalarOpts.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMInstCombine.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAggressiveInstCombine.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMTransformUtils.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBitWriter.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAnalysis.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMProfileData.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSymbolize.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDebugInfoBTF.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDebugInfoPDB.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDebugInfoMSF.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDebugInfoDWARF.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMObject.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMTextAPI.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMCParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMIRReader.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMAsmParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMMC.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDebugInfoCodeView.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBitReader.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMFuzzerCLI.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMCore.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMRemarks.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBitstreamReader.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMBinaryFormat.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMTargetParser.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMTableGen.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMSupport.lib;C:\Miniconda\envs\tlcpack-build\Library\lib\LLVMDemangle.lib;psapi.lib;shell32.lib;ole32.lib;uuid.lib;advapi32.lib;ZLIB::ZLIB;zstd::libzstd_static;C:\Miniconda\envs\tlcpack-build\Library\lib/xml2.lib
-- Found TVM_LLVM_VERSION=170
-- Build with LLVM
-- Set TVM_LLVM_VERSION=170
-- Build with contrib.random
-- Build with contrib.sort
-- Build with contrib.hybriddump
-- Git found: C:/Miniconda/envs/tlcpack-build/Library/bin/git.exe
-- Found TVM_GIT_COMMIT_HASH=2064d590300d1d593a4f705b7c51aec53d5ce3cb
-- Found TVM_GIT_COMMIT_TIME=2023-11-06 06:49:51 -0800
-- Could NOT find LIBBACKTRACE (missing: LIBBACKTRACE_STATIC_LIBRARY LIBBACKTRACE_INCLUDE_DIR)
-- Building with TVM Map...
CMake Error at D:/a/package/package/tvm/build/CMakeFiles/CMakeScratch/TryCompile-tnlfb1/CMakeLists.txt:2 (set):
-- Build with thread support...
  Syntax error in cmake code at
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD

    D:/a/package/package/tvm/build/CMakeFiles/CMakeScratch/TryCompile-tnlfb1/CMakeLists.txt:2

-- Configuring incomplete, errors occurred!
  when parsing string

    C:\Miniconda\envs\tlcpack-build\Library\lib\cmake\llvm

  Invalid character escape '\M'.

It seems CMAKE_INSTALL_LIBDIR is undefined: https://github.com/llvm/llvm-project/blob/main/llvm/cmake/modules/Findzstd.cmake#L39C31-L39C51. I wonder if adding -DCMAKE_INSTALL_LIBDIR=lib to the cmake command could help?


Change active audio/subtitle in Player

Hi,
Can we change audio/subtitle during playing?
Some content have more 1 subtitles or audios, and I would like to give to possibility to users to select and change it.
But I did'nt see those features in default Tizen.Multimedia.Player?
There are a solution?

Well, try this one.


WASM Bindings for the Account

Description of change
Adds WASM bindings for the account with a TypeScript minimal project and examples.
Links to any relevant issues
#304
Type of change

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] Enhancement (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Fix

How the change has been tested
Locally run the Typescript examples.

Please add documentation suggestions where you see fit.

Thanks @PhilippGackstatter  @cycraig  and @HenriqueNogara for the initial review I implemented most of the suggested changes.
regarding https://github.com/iotaledger/identity.rs/pull/574#discussion_r796623147  I'm not sure how dropping objects in WASM memory happens. Even forcing garbage collection in JS doesn't drop the account in the example. And in JS we can't expect the behavior of the garbage collector anyways, so I don't see any other way for the example but calling the free() method.

Thanks @cycraig for the second review, I implemented most of the suggestions. There's a couple of issues that we might wanna still do after this PR, PromiseVoid is one of them.
Regarding to createSignedData(..) I didn't change it because we voted on explicit naming. We can still discuss it if you think it is needed.


Button images for the search panel are not displayed

The images associated to the buttons do not appear in the search panel.

I use the version <IP_ADDRESS>.
I uninstalled and reinstalled the package and nothing changed.
Edit: To fix the problem I override the style of the search panel. I added the following snippet and I replaced the images of the buttons by my own images.
<ControlTemplate.Resources>
        <Style TargetType="{x:Type Button}" BasedOn="{StaticResource {x:Type Button}}"/>
</ControlTemplate.Resources>

I think it's not a problem with AvalonEdit Library. Maybe you have overwritten default Style of Button?


Update djb2.properties

Add lots of sprite names and some song names. Removed "mapfunction".

Thanks


port to 1.21.3

What and How?
port to 1.21.3
Why?
just because my paper server runs on it
Are there alternatives?
no not really
Checks

[X] I have used the search at least once to check if my idea has already been suggested and perhaps already implemented.

Anything else
No response

Should already support it, does it not work?

Sorry I apologize tuns out it does work although it seems as though I can't lag other players out only myself and when I unlag my self it doesnt unlag

From: srnyx @.>
Sent: Sunday, November 24, 2024 11:18 AM
To: srnyx/limitless-lag @.>
Cc: himynameiscool782 @.>; Author @.>
Subject: Re: [srnyx/limitless-lag] port to 1.21.3 (Issue #1)
Should already support it, does it not work?
—
Reply to this email directly, view it on GitHubhttps://github.com/srnyx/limitless-lag/issues/1#issuecomment-2496092436, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BNFOCWC7HRWUPENDMH3XMPL2CH35RAVCNFSM6AAAAABSMLFE36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJWGA4TENBTGY.
You are receiving this because you authored the thread.Message ID: @.***>

I can't lag other players out only myself

What happens when you try to use the command on someone else? What's sent in chat? Are you sure it isn't working?

when I unlag my self it doesnt unlag

Same as above, what's sent in chat when you run the command? And what happens if you run it again, does it say it disabled it again or that i re-enabled?

I think it fixed itself sorry for wasting your time

From: srnyx @.>
Sent: Sunday, November 24, 2024 11:40 AM
To: srnyx/limitless-lag @.>
Cc: himynameiscool782 @.>; Author @.>
Subject: Re: [srnyx/limitless-lag] port to 1.21.3 (Issue #1)
I can't lag other players out only myself
What happens when you try to use the command on someone else? What's sent in chat? Are you sure it isn't working?
when I unlag my self it doesnt unlag
Same as above, what's sent in chat when you run the command? And what happens if you run it again, does it say it disabled it again or that i re-enabled?
—
Reply to this email directly, view it on GitHubhttps://github.com/srnyx/limitless-lag/issues/1#issuecomment-2496100632, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BNFOCWFIQGODC24DWILD4T32CH6OZAVCNFSM6AAAAABSMLFE36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJWGEYDANRTGI.
You are receiving this because you authored the thread.Message ID: @.***>

I think it fixed itself sorry for wasting your time

you're good! glad it figured itself out 😄


python3 decode.py SyntaxError: invalid syntax

File "/home/zzt/sgnmt/cam/sgnmt/decoding/core.py", line 939
(fAcc, _) = reduce(lambda (f1,w1), (f2,w2):(f1w1 + f2w2, 1.0), x, (0.0, 1.0))
^
SyntaxError: invalid syntax

we currently only support Python 2.7.
Best, Felix

thanks. Can you give me some decode examples: ensemble tensor2tensor models  with different vocabulary.

Small update on this: Python 3 is now supported


Don't make source a required argument

Why do I have to provide a 'src' argument when there is already an option for a configuration file where you can specify source files? I want all my configuration in the configuration file, but I have to put this one bit of configuration in my Gruntfile.
I want to be able to either run jsdoc through grunt or on its own, but that is impossible with how grunt-jsdoc currently works. If I specify my source files in my jsdoc config file I get duplicates when I run jsdoc through grunt since it already has source files.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2299094-don-t-make-source-a-required-argument?utm_campaign=plugin&utm_content=tracker%2F294645&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F294645&utm_medium=issues&utm_source=github).

as from 1.1.0 also dest becomes optional when a config file is set.


TextBlock TextDecorations="Strikethrough" does nothing

Describe the bug
TextBlock TextDecorations="Strikethrough" does not show up.
To Reproduce
<TextBlock
    Text="There should be an strikethrough line on this text"
    TextDecorations="Strikethrough"/>

Expected behavior
There should be an strikethrough line on the text
Desktop (please complete the following information):

OS: Mac
Version 11.0.0.preview4

Additional context
Any other TextDecorationLocation works (Underline, BaseLine, etc)

Still an issue with latest release of version 11.1 also on Windows 11 (ARM).

Tested with 11.1.4 it seems to work now (Windows 11/x64).

Hi @xleon can you double check on your side if the issue is fixed?


errdefs: Provide a valid stack in all cases

Signed-off-by: Kenfe-Mickael Laventure<EMAIL_ADDRESS>

LGTM

@stevvooe those stacks are never displayed by default unless you use %+v.
If the grpc message has no additional information but the one from grpc. no stack will be generated. I just though I'd fix the inconsistency.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1410   +/-   ##
=======================================
  Coverage   40.81%   40.81%
=======================================
  Files          23       23
  Lines        2923     2923
=======================================
  Hits         1193     1193
  Misses       1452     1452
  Partials      278      278

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 1046064...4de2199. Read the comment docs.


compliation error

I am gettting:
error[E0716]: temporary value dropped while borrowed
  --> src/trainer/default/quant.rs:33:22
   |
15 |             let to_write: &[u8] = match self {
   |                 -------- borrow later stored here
...
33 |                     &x.to_le_bytes()
   |                      ^^^^^^^^^^^^^^^ creates a temporary value which is freed while still in use
34 |                 }
   |                 - temporary value is freed at the end of this statement
   |
   = note: consider using a `let` binding to create a longer lived value

@jdart1 that's very strange, I think it might be due to an outdated Rust version.
Regardless I'll be pushing a fix that should eliminate it wholly.

@jdart1 could you check if the issue is resolved?

Yes, it is no longer occurring.


:wrench: Fix up a few more effc++ items

test suite has these two failures, but the same tests fail even before this change:
21/70 Test #62: test-regression_all .................***Failed   12.56 sec
29/70 Test #61: test-regression_default .............***Failed   12.91 sec

The tests should succeed... Can you make sure you on the latest develop version?

What are the errors?

Ok, my bad. The failures were with gcc 4.9.3. When run under 5.4.0-6ubuntu1~16.04.5 everything passes.

Hm... GCC 4.9 should work as well. Could you post the errors?

And which compiler created the -Weffc++ warnings?

Original effc++ warnings were from icc (ICC) 11.0 20081105. I'll dig them up and post them here.
Sorry, never used ctest -- how can I get it to print the specific errors? I just get very general message currently:
$ ctest -R test-regression_default
Test project /nfs/orto/home/mkgumbel/clt_dev02/json/build
    Start 61: test-regression_default
1/1 Test #61: test-regression_default ..........***Failed    6.87 sec

0% tests passed, 1 tests failed out of 1

Label Time Summary:
default    =   6.87 sec (1 test)

Total Test time (real) =   6.94 sec

The following tests FAILED:
         61 - test-regression_default (Failed)
Errors while running CTest

thanks

You can use --output-on-failure.

Coverage remained the same at 100.0% when pulling 3fee464ebb0fd741fc8a595d1da45a8356a7a3e4 on mattismyname:develop into 0e3a0b730b8b23d6fdfabf7dc8193d3edd5f5593 on nlohmann:develop.

@mattismyname Could you comment on https://github.com/nlohmann/json/pull/858#pullrequestreview-81649476 and https://github.com/nlohmann/json/pull/858#pullrequestreview-81650164?

@mattismyname Could you please comment on https://github.com/nlohmann/json/pull/858#pullrequestreview-81649476 and https://github.com/nlohmann/json/pull/858#pullrequestreview-81650164? I would like to have this PR merged for the upcoming release.

Sorry for slowness

I've pushed the requested fixes to mattismyname/json develop branch.

Coverage remained the same at 100.0% when pulling 72bff90ed955421f4db98f272648afca565b72c8 on mattismyname:develop into 3113a52a7d148d7ad9567cf9d67fa67960beb3f1 on nlohmann:develop.

Thanks a lot!


RELATED: FET-975 Upgrade cssnano-preset-default to fix advisories in is-svg

Build succeeded (check pipeline).

https://checklist.intgdc.com/job/client-libs/job/gooddata-create-gooddata-react-app-unit-tests-zuul-docker-el7/328/ : SUCCESS in 30s
https://checklist.intgdc.com/job/compliance/job/gooddata-create-gooddata-react-app-oss-check/262/ : SUCCESS in 8s

Build succeeded (gate pipeline).

https://checklist.intgdc.com/job/compliance/job/gooddata-create-gooddata-react-app-merge-compliance-check/133/ : SUCCESS in 39s
https://checklist.intgdc.com/job/client-libs/job/gooddata-create-gooddata-react-app-unit-tests-zuul-docker-el7/329/ : SUCCESS in 1m 49s
https://checklist.intgdc.com/job/compliance/job/gooddata-create-gooddata-react-app-fossa-scanning-zuul-el7/98/ : FAILURE in 10m 43s (non-voting)


Add a configuration option for consecutive gateway errors

Introduce the possiblity to configure consecutive gateway errors for outlier detection as described by https://www.envoyproxy.io/docs/envoy/latest/api-v1/cluster_manager/cluster_outlier_detection.html and requested by https://github.com/istio/istio/issues/8082 .
This change is depending on the istio/api pull request https://github.com/istio/api/pull/617

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kyessenov
If they are not already assigned, you can assign the PR to them by writing /assign @kyessenov in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS
vendor/istio.io/api/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @arnecls. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/assign @kyessenov

I signed it!

🤔 Apparently I messed up the API / vendoring process.
Should I do a separate PR once https://github.com/istio/api/pull/617 has been accepted, or update this one?

Thanks for the PR. See my comment in API. You can close the API PR and treat the current consecutive_error as the consecutive_gateway_error instead. Make sure to update the corresponding ejection percent, etc..

I have a few concerns on merging consecutive_error and consecutive_gateway_error.

That would be a potential breaking change for people relying on the current behaviour
There are situations where you want to treat the two differently
More details on this are in the API-PR.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: kyessenov
If they are not already assigned, you can assign the PR to them by writing /assign @kyessenov in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/ok-to-test

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@arnecls can you send the same PR to release-1.0 branch as well? I would like to have this be available in Istio 1.0.1 (better start early with the right semantics).

@arnecls: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
365bdaaca8becef985ca276b9f20a648404415a1
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram will do


v0.8.6_05: Bubbles are not visible after loading bubble chart

SEVERITY: Critical
MODULE:  Bubble Chart
Platform: iPhone-4 (iOS 7.1) / Chrome
RELEASE: v0.8.6
STEPS TO REPRODUCE:

Navigate URL: http://static.gapminderdev.org/vizabi/release/v0.8.6/preview/bubblechart.html
Bubble chart page will be loaded
Note that bubbles are not visible

ACTUAL RESULTS:
Bubbles are not visible after loading bubble chart. If we click play after loading the chart, extremely small size bubbles are displayed but they cannot seen easily
EXPECTED RESULTS:
After loading the bubble chart, the bubbles should be visible properly
SCREENSHOT:

https://github.com/Gapminder/vizabi/pull/913

Retest Result: Pass
Platform:

iPhone-4 (iOS 7.1) / Chrome
iPhone-4 (iOS 7.1) / Safari

Testing Environment: http://static.gapminderdev.org/vizabi/develop/preview/bubblechart.html


Decouple Logical and Configurable Things

Hi mas @ariya , it's very interesting to find simple yet powerful tool like this. I'd like to contribute implementing on other languages, but seems it would be more easy if we firstly extract configurable things from code. Outcome of this PR is to make it easier to implement on other languages.
Feedback and suggestions are highly appreciated. Thank you!

Thank you @kenjihikmatullah for the PR.
While I appreciate the intent, IMO this is an unnecessary abstraction as there is no need to split code/functions/data to a separate source file, unless there is some other code that takes advantage of the separation.

@ariya thanks mas for the feedback. In that case, is it ok if I just try to implement in another language? Perhaps I will start with Python or Go

Closing this for now.


[Bug]: Taqueria.io does not have a robots.txt file

Describe the feature you would like
Implement a robots.txt file so crawlers can index the website properly
Is this feature solving a problem?
This issue surfaced in Moz with the following error:
Moz was unable to crawl your site on Feb 8, 2022. Our crawler was not able to access the robots.txt file on your site. This often occurs because of a server error from the robots.txt. Although this may have been caused by a temporary outage, we recommend making sure your robots.txt file is accessible and that your network and server are working correctly. Typically errors like this should be investigated and fixed by the site webmaster. [Read our troubleshooting guide.](https://moz.com/help/moz-pro/site-crawl/crawl-troubleshooting)
Please share any additional details you have?
Properly implementing robots.txt will help with SEO
Code of Conduct

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

Closing: addressed in #454


PERF: Variable-size minutely cache.

Use a variable-size cache for minutely pricing data.
Increase the default cache size for close to 3000, since close prices
are used in many places in the simulation as the best-known price of
assets. This dramatically speeds up algorithms that read the prices of
many assets without ordering them.

Coverage increased (+0.003%) to 87.57% when pulling fd9feafc4304e7e4ff7ea7162174bec76876e1dc on variable-cache into ba603928fda8d7985eb6f3d2deb9beec45c2297b on master.


Using multiple specs ( for multiple versions ) in a single CRD based library fail

a config.sonnet like this
local config = import 'jsonnet/config.jsonnet';

config.new(
  name='jaeger-operator',
  specs=[
    {
      output: '1.24',
      openapi: 'http://localhost:8001/openapi/v2',
      prefix: '^io\\.jaegertracing\\..*',
      crds: ['https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.24.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml'],
      localName: 'jaeger-operator',
    },
    {
      output: '1.25',
      openapi: 'http://localhost:8001/openapi/v2',
      prefix: '^io\\.jaegertracing\\..*',
      crds: ['https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.25.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml'],
      localName: 'jaeger-operator',
    },
  ]
)

when rendered will cause the last version to be loaded and used to render both of the 1.24 and the 1.25 output

https://github.com/jsonnet-libs/k8s/blob/master/scripts/gen.sh#L14 - all CRDS are extracted at once
https://github.com/jsonnet-libs/k8s/blob/master/scripts/gen.sh#L54 - all CRDS are added to the same tmp file
https://github.com/jsonnet-libs/k8s/blob/master/scripts/gen.sh#L74 - all CRDS are applied at once, with the latest one winning
https://github.com/jsonnet-libs/k8s/blob/master/scripts/gen.sh#L90 - all the output dirs are generated from the same CRDs

log example
++ mktemp
+ CRDFILE=/tmp/tmp.pEeEjA
++ mktemp
+ API_LOGFILE=/tmp/tmp.LCafij
+ '[' -n 'https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.24.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml
https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.25.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml' ']'
+ echo ''
+ ./bare-k3s
+ for URL in ${CRDS}
+ echo ---
+ echo 'Downloading https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.24.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml...'
+ curl -sL https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.24.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml
Downloading https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.24.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml...
+ for URL in ${CRDS}
+ echo ---
+ echo 'Downloading https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.25.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml...'
Downloading https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.25.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml...
+ curl -sL https://raw.githubusercontent.com/jaegertracing/jaeger-operator/v1.25.0/deploy/crds/jaegertracing.io_jaegers_crd.yaml
+ server_up
+ local i
++ seq 1 10
+ for i in $(seq 1 10)
+ local out
++ kubectl get --raw /healthz
+ out=
+ sleep 1
+ for i in $(seq 1 10)
+ local out
++ kubectl get --raw /healthz
+ out=
+ sleep 1
+ for i in $(seq 1 10)
+ local out
++ kubectl get --raw /healthz
+ out=
+ sleep 1
+ for i in $(seq 1 10)
+ local out
++ kubectl get --raw /healthz
+ out=ok
+ echo 'On try 4: ok'
+ return 0
On try 4: ok
+ kubectl apply -f /tmp/tmp.pEeEjA
customresourcedefinition.apiextensions.k8s.io/jaegers.jaegertracing.io created
customresourcedefinition.apiextensions.k8s.io/jaegers.jaegertracing.io configured
+ sleep 120
+ kubectl proxy
Starting to serve on <IP_ADDRESS>:8001
+ shopt -s dotglob
+ cp -r /config/skel/.github /config/skel/LICENSE /config/skel/README.md /config/skel/docs /config/skel/mkdocs.yml /config/skel/requirements.txt /output/github.com/jsonnet-libs/jaeger-operator-libsonnet
+ k8s-gen -o /output/github.com/jsonnet-libs/jaeger-operator-libsonnet -c /config/config.yml
Generating '1.24' from 'http://localhost:8001/openapi/v2, ^io\.jaegertracing\..*'
Generating '1.25' from 'http://localhost:8001/openapi/v2, ^io\.jaegertracing\..*'

You are right, that is a bug.

:+1: i was planning to have a look at it but had no time so i just created this for reference. If anyone gets to it before me cool otherwise i will give it a shot as soon as i can


precommit: introduce Black & docs

This is about eventually accepting Black formatting, which I know could be very opinionated, but at least take it as a suggestion to show how the codebase could look... In fact, using Ruff formatting, which claims compatibility with Black, see https://docs.astral.sh/ruff/formatter/#black-compatibility

There copuld be some cases when the formating is not your Cup of tea, but over all, I find the codebase more readable... :)

I can do with everything but the long lines.

it is one of the parameters, so what is your preferred line length?

Pep8's 79 characters.
@Borda

Nice. This looks done. Are done? Should I review? @Borda


Process Explorer Open in FullScreen

macOS
run in fullscreen mode
open the process explorer
🐛 the prices explorer window also opens in fullscreen mode...

Hi 👋🏽
Gonna take a look at this. It seems to be happening for 'Report issue' also.

Hi @RMacfarlane. Can I help you somehow to get this merged?

@agurodriguez Yep! Sorry for the delay, your change looks good. I'll merge it now. Thanks!


Fix clang (OSX) compatibily

1- makefile doesn't require headers as lib dependency
2-  should be explicitly declared

Thx


PDF Parser Bugs

Possible bugs: https://github.com/Nikololoshka/StankinScheduleEditor3
Other parser in TS: https://github.com/iPagar/rector-schedule-parser
Can steal from this repo: https://nikololoshka.github.io/#/stankin-schedule/storage

This parses as every second week for all 3 strings:


fixfix create table like need create_priv of existed table

create table like only need create_priv of newTable, and select_priv of existedTable
not need create_priv of existed table
ps: have already added cases in other PRs

run buildall

run cloud_p0

run cloud_p0

run buildall

run buildall

run buildall

run p0


Omit directories from symbol calculation

Do not try to calculate ctags or scope_query symbols on directories. Really this whole flow needs a bit of TLC.

agreed, we have a similar filter for lang_str as well. would be nice to consolidate all of this logic.


Problems to render Maps after camera.rotateAround with certain points

Issue details
_ Sometimes the rotateAround method belonging to the Camera class is faulty in rendering OrthogonalTiledMapRenderer or TiledMapRenderer. I think it's a possible problem, otherwise I beg your pardon.
I came across the reported problem using the method in question in the game I'm trying to do. I thought it was something wrong with my code. Again went over my studies in Camera classes, OrthographicCamera and Viewport. Even redid the exercise of page
https://github.com/libgdx/libgdx/wiki/Orthographic-camera
I made the inclusion of 2 more conditions within the handleInput method to rotate the screen with the rotateAround method and there were no problems with the rendering of Sprite.
But when the rotation occurs when using OrthogonalTiledMapRenderer or TiledMapRenderer rendering is weird depending on the point chosen for the rotateAround.
I posted a video. I used as an example to play the SuperKoalio. I ran two examples choosing 2 different positions to rotate the camera. In the right window the rotation takes place and the floor disappears. In the left window its just perfectly.
I had the same problem in my game as the right window.
https://www.youtube.com/watch?v=v35rHSwZhLE
Reproduction steps/code
-To reproduce the error. I added the code line
camera.rotateAround (new Vector3 (koala.position.x, koala.position.y, 0), new Vector3 (0,0,1), 1);
after the updateKoala (deltaTime) within the render () method, after the line 131.
In the video example, the left screen that usually works the koala starting position on the line 116 remained the same.
koala.position.set(20, 20);
On the right screen the koala position was initiated with
koala.position.set (30, 20);
line 134 needs to be deleted to Koala be the center point.
Version of LibGDX and/or relevant dependencies
_Just tested with v9.3
Stacktrace
//No stacktrace

Please select the affected platforms

[x ] Android
[?] iOS (robovm)
[?] iOS (MOE)
[?] HTML/GWT
[ x] Windows
[?] Linux
[?] MacOS

Thank you. Libgdx is amazing!

I edited, forgot to say that line 134 needs to be deleted to Koala be the center point.

Hi Tom.
Thank you for your help.
I was really afraid that the issue that I mentioned was something wrong I did.
I saw that you fixed.
I would like to ask, how do I use this fix?
I have the libgdx source code in Eclipse I tried to hunt this error, but neither came close. Just take a git push and do rebuid with ant.
But how I use this fix in my game that uses the jars libgdx? I used libgdx setup to put together this little game.
Speaking of game I saw BlobRun and Somali. They are really beautiful, not yet played, but hope one day reach this level.


apex deploy fails temporarily after apex init

If you have a bug report please let us know the following:

Operating system: OS X
Apex Version:  v0.10.2

When appropriate please also paste the debug log output using -ldebug or --log-level debug.
to reproduce
$ apex init

             _    ____  _______  __
            / \  |  _ \| ____\ \/ /
           / _ \ | |_) |  _|  \  /
          / ___ \|  __/| |___ /  \
         /_/   \_\_|   |_____/_/\_\

  Enter the name of your project. It should be machine-friendly, as this
  is used to prefix your functions in Lambda.

    Project name: apex

  Enter an optional description of your project.

    Project description:

  [+] creating IAM apex_lambda_function role
  [+] creating IAM apex_lambda_logs policy
  [+] attaching policy to lambda_function role.
  [+] creating ./project.json
  [+] creating ./functions

  Setup complete, deploy those functions!

    $ apex deploy

$ apex deploy
   • creating function         function=hello
   ⨯ Error: function hello: InvalidParameterValueException: The role defined for the function cannot be assumed by Lambda.
    status code: 400, request id: f03f8b02-469b-11e6-9ebb-958132979df1

# wait 5 seconds
$ apex deploy
   • creating function         function=hello
   • created alias current     function=hello version=1
   • function created          function=hello name=apex_hello version=1

logs
$ apex logs --log-level debug
   • loading functions in functions
   • loading function in functions/hello
   • inferring runtime         function=hello
   • inferred runtime          function=hello runtime=nodejs4.3
   • enter                     group=/aws/lambda/apex_hello
   • request                   group=/aws/lambda/apex_hello start=1468154641131
   • not found                 group=/aws/lambda/apex_hello
   • exit                      group=/aws/lambda/apex_hello
   • conditional flush         above_duration=24h0m0s above_size=500 age=11m3.781933857s size=7
   • close

I think there's a delay in the setup of the IAM role which causes the deploy to fail on the first few seconds. After those few seconds, deploy seems to work fine.

Woah interesting, I've never noticed a delay there

There can be a delay with creating these resources (pretty common in the AWS APIs), we would need to use the waitFor(...) command to wait for the role to be created.

@tj I doubt it's noticeable unless you create a new AWS account regularly? or delete your AMI role regularly? I think @DavidTPate's solution should make new users' DX a little better.

I have tested it quite a bit just for QA, must have just been lucky there, but yeah we should have something like that for sure

I am experiencing this, but it has not resolved after a few seconds. It was closer to a minute or two.
This is a fresh AWS account. Same conditions as above.

Yikes, I guess we might as well use CloudFormation if it's going to take that long, for my testing it was quick enough that there was no perceptual delay, curious why it's so eventual on their end haha

FYI we observed this once; included a mention in intro blog post in case others saw it too http://www.starkandwayne.com/blog/quick-guide-to-deploying-golang-to-aws-lambda-using-apex/


INSERT A FRAMERATE AND CONFIRM WITH "ENTER"

I am attempting to execute the start.sh
after installing your repo on ubuntu 16.04
This machine has go properly installed and its graphics libs setup
Did not attempt to troubleshoot this however giving you this feedback
might help
stens@bodhisattva ~/other_src/gopath/src/github.com/SimonWaldherr/cgolGo $ ./start.sh
INSERT A FRAMERATE AND CONFIRM WITH "ENTER" [15]
./start.sh: 4: read: Illegal option -s
PRESS "R" FOR A RANDOM MAP OR "F" TO LOAD FROM A FILE [R]
./start.sh: 7: read: Illegal option -n
./start.sh: 9: [: unexpected operator
./start.sh: 14: [: unexpected operator
./start.sh: 19: [: unexpected operator
./start.sh: 19: [: unexpected operator
./start.sh: 22: [: unexpected operator
./start.sh: 22: [: unexpected operator

ideas ?

hi @scottstensland, please test it again.
sorry for the late response.

Solved  !    nicely done

is there a reason you reopened the issue again?

no ... just so you can see my acknowledgement the fix worked ... thanks again

thanks :)


Extended FAB properties have odd behavior

Sum up

[ ] FAB.isExtended does not create an extended FAB
[ ] FAB does not animate changes in shape

Thought I'd fix https://github.com/flutter/flutter/issues/111770 right quick and noticed that the FAB did not behave as expected per this comment https://github.com/flutter/flutter/issues/111770#issuecomment-1255265283
I thought the FAB would automatically animate itself when I changed its config using the extended constructor. I am not sure if this is an incorrect assumption but I thought it has some of this already built in. Maybe it needs and AnimatedContainer for this?
Then I noticed the docs seem to think so, but only if you use isExtended?
  /// The [Scaffold] animates the appearance of ordinary floating
  /// action buttons with scale and rotation transitions. Extended
  /// floating action buttons are scaled and faded in.
  final bool isExtended;

However, setting the isExtended in the base constructor doesn't actually create an extended FloatingActionButton.

https://user-images.githubusercontent.com/16964204/227065069-170fd4d9-31ef-44ec-8c5b-cebb70def7bf.mov
Here is the sample code I came up with for https://github.com/flutter/flutter/issues/111770:
// Copyright 2014 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

// Flutter code sample for [FloatingActionButton].

import 'package:flutter/material.dart';

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

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

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: FabExample(),
    );
  }
}

class FabExample extends StatefulWidget {
  const FabExample({super.key});

  @override
  State<FabExample> createState() => _FabExampleState();
}

class _FabExampleState extends State<FabExample> {
  bool isExtended = true;

  bool handleScrollNotification(ScrollNotification notification) {
    bool shouldExtend = isExtended;
    if (notification is ScrollStartNotification) {
      shouldExtend = false;
    } else if (notification is ScrollEndNotification) {
      shouldExtend = true;
    }
    if (isExtended != shouldExtend) {
      setState(() {
        // React to a change in isExtended
        isExtended = shouldExtend;
      });
    }
    return false;
  }

  @override
  Widget build(BuildContext context) {
    final Widget floatingActionButton = isExtended
        ? FloatingActionButton.extended(
      onPressed: () {
        // Add your onPressed code here!
      },
      backgroundColor: Colors.green,
      icon: const Icon(Icons.add),
      label: const Text('Create'),
    )
        : FloatingActionButton(
      onPressed: () {
        // Add your onPressed code here!
      },
      backgroundColor: Colors.green,
      child: const Icon(Icons.add),
    );

    return Scaffold(
      appBar: AppBar(
        title: const Text('FloatingActionButton Sample'),
      ),
      body: NotificationListener<ScrollNotification>(
        onNotification: handleScrollNotification,
        child: ListView.builder(
          itemCount: 10,
          itemBuilder: (BuildContext context, int index) {
            return Card(child: ListTile(title: Text('ListTile $index')));
          },
        ),
      ),
      floatingActionButton: floatingActionButton,
    );
  }
}

related https://github.com/flutter/flutter/issues/104393

CC @gspencergoog - does this problem overlap with the FAB changes you've been working on?

I'm not sure. I'll have to test the example with my updated code. I suspect it might fix this issue, since the ElevatedButton should animate when it changes shape/size.

I'm not sure. I'll have to test the example with my updated code. I suspect it might fix this issue, since the ElevatedButton should animate when it changes shape/size. (and the updated FAB is based on ElevatedButton).

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

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

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

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      themeMode: ThemeMode.light,
      theme: ThemeData(useMaterial3: true),
      darkTheme: ThemeData(useMaterial3: true, brightness: Brightness.dark),
      home: const Example(),
    );
  }
}

class Example extends StatefulWidget {
  const Example({super.key});

  @override
  State<Example> createState() => _ExampleState();
}

class _ExampleState extends State<Example> {
  bool shrinked = false;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Floating Action Button'),
      ),
      body: Center(
       child: ElevatedButton(
        style: ElevatedButton.styleFrom(
          minimumSize: shrinked ? const Size(80, 80) : const Size(250, 80),
        ),

        onPressed: () {}, child: const Text('ElevatedButton')),
      ),
      bottomNavigationBar: BottomAppBar(
        child: Center(
          child: ElevatedButton(
            onPressed: () {
              setState(() {
                shrinked = !shrinked;
              });
            },
            child: const Text('Shrink ElevatedButton'),
          ),
        ),
      ),
    );
  }
}

ElevatedButton doesn't seem to animated when changing min size.
https://user-images.githubusercontent.com/48603081/228068388-b9481fe7-e92e-4577-849c-2c25dda528c1.mov

FloatingActionButton.extended(isExtended: false) and FloatingActionButton() are not same
FAB.extended when not extended has extra padding on right

FloatingActionButton.extended()
FloatingActionButton.extended(isExtended: false)
FloatingActionButton()


feat: add a heatmap

desktop
mobile

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

color for gray squares should be #F8F9FB.
Also can we apply less spacing between the 2 rows of data? looks really spacious rn. Attaching designs

attaching color scale

This Pull Request was merged without enough reviews
Please go here to review and +1

This Pull Request was merged without enough reviews
Please go here to review and +1


Tracking progress towards completion.

Is there a way to estimate "progress towards completion" in the context of either timely or differential?  Let's say we pushed some updates to DD, advanced the timestamp and are now calling step_or_park in a loop waiting for the probe to report that all updates have successfully propagated through the pipeline.  This can take a long time, e.g., when populating the pipeline with initial data or when processing a small update that triggers large amount of recomputation.  In these situations it may be nice to comfort the user with a little progress bar showing approximately how much longer they have to wait.
@frankmcsherry, do you happen to have some magic up your sleeve that might help here? :)
@Kixiron, @RDambrosio016.

There is a lingering PR #321 that I need to clean up before merging, which would expose progress information in a logging channel. Depending on what makes it in, it could report either the outstanding capabilities in the system (messages counts on channels, and retained capabilities in operators) or the frontier of outstanding capabilities ("what's holding up the system").
I think this is the most obvious form of progress to report; there is also scheduling information about how many times and for how long various operators have been executed, but timely doesn't know too much about whether they are making progress when invoked.
Operator can also use their own custom logging if there is a clearer notion of progress that the operators can invoke (perhaps they have internal queues they are working to drain; timely wouldn't know about them, but the operators can still hook into the logging and report them).


Fix example for Basis * Vector3 in documentation

Description
This MR fixes an invalid example in the Basis documentation, fixes https://github.com/godotengine/godot-docs/issues/9394
I opted to change the inputs instead of the outputs, because it seemed strange to have two identical basis vectors. Plus this allows some of the inputs to be negative
Actions performed

Cloned both projects, symlinked them together and ran the build both before and after the changes to confirm they show up where expected
Retested the GDScript example in editor to confirm the new example gives the promised result
⚠ Did not test the C# example. Though I have no reason to believe it should run any different
Checked the original MR to see if there were any comments about this example to be aware of
Ran pre-commit hooks (4 passed, rest skipped)

Although I'd be more in favour of correcting the "Prints" statement, this is correct, too. Thank you for cleaning after me.

Any specific reason?
If desired, I have no problem changing it - either to the original
  var my_basis = Basis(Vector3(1, 1, 1), Vector3(1, 1, 1), Vector3(0, 2, 5))
  print(my_basis * Vector3(1, 2, 3)) # Prints (3, 9, 18)

or a hybrid that just barely changes the inputs to make them different
  var my_basis = Basis(Vector3(1, 1, 1), Vector3(1, -1, 1), Vector3(0, 2, 5))
  print(my_basis * Vector3(1, 2, 3)) # Prints (3, 5, 18)

or to some new example like
  # Basis that swaps the x/z axis and doubles the scale
  var my_basis = Basis(Vector3(0, 2, 0), Vector3(2, 0, 0), Vector3(0, 0, 2))
  print(my_basis * Vector3(1,2,3)) # Prints (4, 2, 6)

It is mostly to keep the numbers simpler and easier to digest (although a transformation is anything but simple at a glance).
I like the new example you proposed.

I rebased the PR to fix the (temporary) CI issue, and did the couple tweaks I had suggested while at it.

Thanks! And congrats for your first merged Godot contribution :tada:


Enable CachingConfigurer customization

#179 rebased against master.
Fixes #159.

This adds Spring Boot dependency to the context module - something we prefer to avoid. CachingConfigurer customisation will be possible after we move all cache related configuration to autoconfigure module.


How to change default color of FluentMenuButton

🙋 Documentation Request
The docs are showing how to change the default color for a FluentMenuButton in runtime but not how to do change the default colors.
I've tried all possible Style parameters already.
<FluentMenuButton @ref=menubutton Text="Optionen" Items="@items" OnMenuChanged="HandleOnMenuChanged" ButtonStyle="background-color: #D83B01;" />

You need to do that in the same way, ie. with the Design Token. Look at the razor tab at https://www.fluentui-blazor.net/MenuButton#menubuttontoselectac but you would need the HandleOnMenuChanged code in OnAfterRenderAsync and use the color you want of course.
Probably wise to read up on how the desing tokens work: https://www.fluentui-blazor.net/DesignTokens.
Closing this as it is not actionable from our side.


Add option to set custom Environment variables

As a NewRelic User
I want to add option to start java with newrelica Agent
So that I can monitor Kafka

fixed in #39


Retrying runs results in negative run timers in the UI

This was observed so far in the case of retries:

#265 might have actually fixed this. Please validate.

Fixed by #265.


Missing scope in Discord OAuth2

Package version
^4.1.0
Node.js and npm version
NodeJS 16.6.1
NPM 7.20.5
Sample Code (to reproduce the issue)
Discord authentication need the identify scope to work properly, on the other hand, the email scope is optional:
https://github.com/adonisjs/ally/blob/3400eb99c9889a6a843f8058b0a07150d99734f8/src/Drivers/Discord/index.ts#L80
The documentation about the user fetch: https://discord.com/developers/docs/resources/user#get-current-user
Here what I had to do to fix temporarily my code:
const allyConfig: AllyConfig = {
  /*
	|--------------------------------------------------------------------------
	| Discord driver
	|--------------------------------------------------------------------------
	*/
  discord: {
    driver: 'discord',
    clientId: Env.get('DISCORD_CLIENT_ID'),
    clientSecret: Env.get('DISCORD_CLIENT_SECRET'),
    callbackUrl: Env.get('DISCORD_REDIRECT_URI'),
    scopes: ['identify', 'email'],
  },
}

https://github.com/Bricklou/supportlauncher-market/blob/1f53017fc238bdf218ceb2308235da860b616a35/config/ally.ts#L20-L33

Hey @Bricklou! 👋
Would you mind sending a PR?

Yes, no problem


cz.msebera.android:httpclient:4.3.6  methods count:5935

That is not a good idea! I met a 65k limit.

Thats still much less than Google play services which comes to more than 20,000. Android Studio handles it without trouble. Add multiDexEnabled true to your gradle.
android {
    compileSdkVersion 23
    buildToolsVersion '23.0.1'

    defaultConfig {
        .
        .
        **multiDexEnabled true**
    }


AssignmentML4.ipynb not compatible with Python 3.9 which is the only one available on Watson

@romeokienzler week 4 assignment of the Advanced machine learning and signal processing course on Coursera needs some updates. Many students and I are stuck on it and can't validate the course because of it. It seems that the provided systemml version is not compatible with Python 3.9, but works only until Python 3.8, which for some reason can't be selected in Watson studio as it always says "Notebook environments with Python 3.8 are restricted to notebooks that are already using them. Choose an environment with Python 3.9 instead."
Here are the available versions (the notebook doesn't work with the option Default Python 3.8 + Watson NLP (beta)):

The error occurs in cell 6 when calling MLContext(spark). This is the error: TypeError: 'JavaPackage' object is not callable
Thank you.

@romeokienzler same problem here, please update the assignment, so it runs on the new Watson Studio environment without giving errors just because of out-dated libraries / environments / packages. Thank you!

Someone is assigned to take care of it...

@GhostOfGreg can u pse try again by re-importing the latest version? should be fixed now..


Configuration#3:Step#1: simulating alpha_S=0.4, matter: q_0=1 | matterlbt: q_0=1.5: matterlbt05

run the simulation with the above config by jetscape,
transfer the final state hadron to the related directory named as config-XX-final-state-hadrons
after doing step1 on all 12 simulations go to step 2 for the configurationX

ported into Excel for overleaf


Many broken links

Feedback
Hello, very nice project!!
Unfortunately, many hyperlinks in the README are broken:

[ ] https://spideroak.com/encryptr (file: README.md, status code: 404)
[ ] https://www.mitro.co (file: README.md, error: CERT_HAS_EXPIRED)
[ ] https://passopolis.com (file: README.md, error: ECONNRESET)
[ ] https://mattrubin.me/authenticator/ (file: README.md, error: CERT_HAS_EXPIRED)
[ ] https://www.arg0.net/encfs (file: README.md, status code: 404)
[ ] https://www.peazip.org/ (file: README.md, error: ECONNRESET)
[ ] https://12bytes.org/7750 (file: README.md, status code: 404)
[ ] https://www.surespot.me (file: README.md, error: EPROTO)
[ ] https://blog.torproject.org/category/tags/tor-messenger (file: README.md, status code: 404)
[ ] keybase.io/inv/6d7deedbc1 (file: README.md, status code: 404)
[ ] https://ricochet.im (file: README.md, error: CERT_HAS_EXPIRED)
[ ] https://mailhero.io (file: README.md, error: ERR_TLS_CERT_ALTNAME_INVALID)
[ ] https://ricochet.im/ (file: README.md, error: CERT_HAS_EXPIRED)
[ ] https://chrome.google.com/webstore/detail/https-everywhere/gcbommkclmclpchllfjekcdonpmejbdp?hl=en (file: README.md, status code: 404)
[ ] https://addons.mozilla.org/en-GB/firefox/addon/https-everywhere/ (file: README.md, status code: 404)
[ ] https://addons.mozilla.org/en-GB/firefox/addon/script-safe/ (file: README.md, status code: 404)
[ ] https://addons.mozilla.org/en-US/firefox/addon/site-bleacher/ (file: README.md, status code: 404)
[ ] https://addons.mozilla.org/en-US/firefox/addon/lightbeam-3-0/ (file: README.md, status code: 404)
[ ] http://trackmenot.io/resources/trackmenot2009.pdf (file: README.md, status code: 404)
[ ] https://chrome.google.com/webstore/detail/trackmenot/cgllkjmdafllcidaehjejjhpfkmanmka (file: README.md, status code: 404)
[ ] https://xumi.ca/xumi-security/ (file: README.md, error: ECONNRESET)
[ ] https://www.deseat.me (file: README.md, error: ECONNRESET)
[ ] /5_Privacy_Respecting_Software.md#mix-networks (file: README.md, status code: 400)
[ ] http://www.squidguard.org (file: README.md, error: ECONNRESET)
[ ] https://nymtech.neteu (file: README.md, error: ENOTFOUND)
[ ] https://awesome.tilde.fun/d/23-list-of-dns-servers (file: README.md, error: DEPTH_ZERO_SELF_SIGNED_CERT)
[ ] https://geekwire.co.uk/privacy-and-security-focused-dns-resolver/ (file: README.md, error: ENOTFOUND)
[ ] https://nixnet.services/dns (file: README.md, status code: 404)
[ ] https://www.anrdoezrs.net/click-9242873-13842740 (file: README.md, error: ECONNREFUSED)
[ ] https://www.kqzyfj.com/l5115shqnhp4E797DC8467D69A6D (file: README.md, error: ECONNREFUSED)
[ ] https://github.com/mothran/mongol (file: README.md, status code: 404)
[ ] https://www.vindohosting.com (file: README.md, error: ENOTFOUND)
[ ] https://rackbone.ch (file: README.md, error: ECONNRESET)
[ ] https://datacell.is (file: README.md, error: EHOSTUNREACH)
[ ] https://filesend.standardnotes.org (file: README.md, error: ENOTFOUND)
[ ] https://chrome.google.com/webstore/detail/geekmarks-client/nhiodffdihhkdlkfmpmmnanekkbbfkgk (file: README.md, status code: 404)
[ ] https://addons.mozilla.org/en-US/firefox/addon/freedommarks/ (file: README.md, status code: 404)
[ ] https://dev.lemmy.ml (file: README.md, error: ERR_TLS_CERT_ALTNAME_INVALID)
[ ] https://bittube.tv (file: README.md, error: ECONNRESET)
[ ] http://pen.io (file: README.md, error: ECONNRESET)
[ ] https://canopy.cr/tonic (file: README.md, error: ENOTFOUND)
[ ] https://libreddit.spike.codes/ (file: README.md, error: ECONNRESET)
[ ] https://github.com/bitcoin/bips/blob/main/bip-0174.mediawiki (file: README.md, status code: 404)
[ ] https://www.paylasso.com (file: README.md, error: ECONNRESET)
[ ] https://www.xda-developers.com/what-is-custom-rom-android/ (file: README.md, status code: 404)
[ ] https://www.tens.af.mil/ (file: README.md, error: ECONNRESET)
[ ] https://www.ipredia.org (file: README.md, error: ENOTFOUND)
[ ] https://dave-theunsub.github.io/clamtk/ (file: README.md, status code: 404)
[ ] https://github.com/mirinsoft/sharpapp (file: README.md, status code: 404)
[ ] https://www.armadito.com (file: README.md, error: ECONNRESET)
[ ] https://play.google.com/store/apps/details?id=com.thhkstudio.hasskit (file: README.md, status code: 404)
[ ] https://snips.ai (file: README.md, error: CERT_HAS_EXPIRED)
[ ] https://www.privalytics.io (file: README.md, error: ECONNRESET)
[ ] https://play.google.com/store/apps/details?id=edu.mit.privatekit (file: README.md, status code: 404)
[ ] https://play.google.com/store/apps/details?id=wangdaye.com.geometricweather (file: README.md, status code: 404)
[ ] https://openelec.tv (file: README.md, error: ECONNRESET)
[ ] https://www.openflixr.com (file: README.md, status code: 520)
[ ] http://noddity.com (file: README.md, error: ENOTFOUND)
[ ] https://bitbucket.org/ymarks (file: README.md, status code: 404)
[ ] https://github.com/Runscope/requestbin (file: README.md, status code: 404)
[ ] https://molo.ch (file: README.md, error: CERT_HAS_EXPIRED)
[ ] /.github/CONTRIBUTING.md (file: README.md, status code: 400)

For avoiding reopening an issue for that, I post here.
I found this guy that seem to maintain a working version of lightbeam : https://gitlab.com/chikl/lightbeam/


VSC not deleting old extensions

Type: Bug
VSC not deleting old extensions, previous version with name_ver_<IP_ADDRESS>.1. is leaved, and new update have new dirs, etc.
I reported time ago (203) this issue and looks it is back
VS Code version: Code 1.77.0 (7f329fe6c66b0f86ae1574c2911b681ad5a45d63, 2023-03-29T10:02:16.981Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: Yes

This issue is related to VS Code, please file it in  https://github.com/microsoft/vscode/issues


Reorganize and expand data-sources endpoints

To reorganize data-sources, partly in line with the requirements in #362, I propose the following:
Associate all endpoints with the data-sources namespace. In other words, all endpoints affecting the data sources begin with /data-sources/. The changes would be as follows:

/data-sources GET method becomes /data-sources/all
/data-sources POST method becomes /data-sources/add
/data-sources-by-id/{data_source_id} becomes /data-sources/by-id/{data_source_id} for both GET and PUT methods
/data-sources-map becomes /data-sources/map
/data-sources-needs-identifications becomes /data-sources/needs-identification
Concomitant with the changes proposed in #367, add a /data-sources/link-to-agency endpoint, which associates a data source with an existing agency (POST), obtains information about an existing link (GET), updates an existing link (PUT) or deletes an existing link (DELETE).

The rationale for this is as follows:

This helps consolidate relevant endpoints into a singular namespace, which will help with organization of the documentation and reduce redundancy.
Breaking up the GET and POST methods of /data-sources enables better clarity in endpoint logic, and additionally enables performing #365 to add a GET method to /data-sources/add which retrieves all columns which can be added.
This will make it easier to expand data-sources logic in the future, by associating them with a separate namespace.
The data-sources/link-to-agency endpoint enables us to add management of linking logic between data sources and agencies, which previously was only done by https://github.com/Police-Data-Accessibility-Project/data-sources-mirror and by directly interfacing with the database, rather than through an endpoint.

The namespace idea is a good one. Most of these make sense to me. My comments here apply, but what about:
GET data-sources/ gets all (I think we should prefer the search endpoint for most use cases)
GET data-sources/{data_source_id} gets one
GET data-sources/id/{data_source_id} could be used if needed
POST data-sources/ adds one
PUT data-sources/{data_source_id} changes one
GET data-sources/search gets multiple too

We might just want to talk this through, though. It's pretty foundational

Resolved, more or less!


Build(deps-dev): Bump eslint from 8.16.0 to 8.17.0 (#3606)

Pull request opened by the merge tool on behalf of #3606

Merged in 02a7cc0fe177eec2ecab13a11a3621837070ccba


Source Map support (debugging of C# sources)

http://forums.bridge.net/forum/general/feature-requests/158-source-maps-support
Duplicate:
http://forums.bridge.net/forum/community/help/584

#22

Source Map support should be included in the Bridge 2.0 release, although might need to wait until 2.1.

Here is a related issue (#931):
"Integrate Chrome debugging into Visual Studio"

Related to #1308.

One more request http://forums.bridge.net/forum/general/open-discussions/1714-bridge-net-v2-0-in-hiding?p=2830#post2830

+1
I don't really care about the integrated debugging, but emitting source maps for the purposes of navigating large bridge projects would be useful. I have quite a large library that is filled with anonymous methods and it can be quite hard to identify where it lives in javascript. Is there anything specific preventing this from working? I presume Cecil can provide maps from IL back to the original C# source file / line numbers etc.

There are some changes to the Bridge compiler architecture that are required before source maps can be supported properly. These changes are being worked on right now, and we hope to include source map support in the Bridge 16.0 release.

I've been working on some async code today (a test framework supporting Task-returning tests) and debugging the code is a bit of a nightmare because of the rewriting to support tasks:

If source maps would make this easier (I don't know, I've never actually used them) then it definitely gets a big vote from me!

+1

@geoffreymcgill Do you have any rough estimate on when this might be implemented? I'm working on a test framework and when you double-click a test in Visual Studio I can't jump to the correct file to edit the test currently. I don't want to rush, but if this is a long way off, it might make sense for me to try and workaround this in the meantime (such as trying to infer the filename from the fully qualified type). If this might come next month, I can wait, but if it's 6 months away it's probably worth me trying to come up with something.

Hi @DanTup – This is one of our highest priority items, although we have to finish up Bridge 16.0 and 16.1 first. That's going to take us at least several months down the road.
The goal is still to include in Bridge 17.0. Unfortunately, we cannot provide a time frame. I'd say six months is a relatively realistic timeframe, although it depends on how smooth Bridge 16.0 and 16.1 go.
I wish we could speed up our progress, but we just don't have the resources required to allocate to Bridge that we wish we had.

Thanks for the info! We understand how things are; it's useful having a rough idea of how far away things are to help us make decisions. It seems like it's probably worth me putting something basic in to try and infer the filename from the type to make it easier to work on.

Source Map feature is implemented, merged into master branch and available at dev.deck.net.
It will be released with 16.0.0-beta2 as well.
A short introduction on Source Map in Deck.

@LeonidVeriga This looks great! :) So when do we get beta2? ;)

@DanTup, no firm date but good chances for this week.

The -beta2 release is scheduled for June 5th. There are a few more features we need to get into this release. Unfortunately, we cannot release any sooner. Lots of good stuff coming.
https://dev.deck.net will be updated with the latest master branch on May 30th.

@DanTup, it might not work very well for async code, see #2812.

@michaelcheers Thanks for the info. I haven't had chance to look at it yet; though my desire was more about fixing up stack traces and making it so you can double-click a test in VS Test Explorer and jump to the correct code, which I don't think should be affected by this.


Publish to maven

I tried to find this in some maven repository, but was not successful. Is there any maven source I could use?

This project is derived from the TopBraid SPIN API (with no major changes until now).
I guess you can try using the TopQuadrant maven repo for a quick start
Check http://topbraid.org/spin/api/

What is the minimum that can be done to get a first release out to maven?
On the principle of "release early, release often", I suggest a target of a functioning project and at least a test suite outline (maybe as little as one test - the step is to have the basic test structure available for PRs).

Regarding the test suite, would it be desirable to release TopQuadrant's original SPIN tests as part of spinrdf? In the TQ codebase, they were managed separately from the SPIN API, because some tests depend on other parts of the codebase that can't be released. So some exploration would be necessary to identify how much of the tests could be feasibly released.
Or better to start from scratch?

Getting setup to deploy to central shouldn't be hard - I've done it before for org.seaborne. It took a couple of days elapsed. Seems to me better to try that route and use a 3rd part repo as a fallback measure.

@cygri - Yes, releasing what tests can be separated out would be good.  IIRC some (In don't know what proportion) are entwined with the general graph handling framework.
If they can easier to be extract, pulling the code out and starting from fragments would be useful.
A contribution that is starting from scratch or another system isn't incompatible, just more tests.

Looking forward :)

Hello everyone,

Getting setup to deploy to central shouldn't be hard - I've done it before for org.seaborne. It took a couple of days elapsed. Seems to me better to try that route and use a 3rd part repo as a fallback measure.

Github release (https://github.com/spinrdf/spinrdf/releases) with a tag 3.0.0-SNAPSHOT will give the opportunity to use this API immediately using jitpack.io

It would be nice to have pre-release in Github to be able to use jitpack repo.

@cygri any update on those tests?

@namedgraph I'm afraid not. This slipped down the priority list.

The topbraid repository I used for spinrdf recently went away and in order to not having to rely on another external repository (jitpack) I created an unofficial maven central release of the state of this repository (commit https://github.com/spinrdf/spinrdf/commit/9541068a6a0a869cc6bc7795d5eca34a78defc2e):

Updated pom snippet

Release command used: git checkout aksw-develop && mvn -P aksw gitflow:release-start gitflow:release-finish && git checkout aksw-master && mvn -P aksw clean install deploy

Dependency:

<dependency>
  <groupId>org.aksw.thirdparty.org.spinrdf</groupId>
  <artifactId>spinrdf</artifactId>
  <version>2.0.0</version>
</dependency>


Causes crash on launch with Spectrum mod, on Fabric 1.19.2

crash-2022-09-30_00.12.45-client.txt
Mod in question: Spectrum

Duplicate of #69

Noted, thank you! Managed to get it running now.


Host documentation on Github pages

This is something that I have seen some other crates do, and it would be quite helpful for users of this crate. I have no idea how Github pages are set up though. @mattnenterprise what is your opinion on this?

https://github.com/huonw/travis-cargo can help with this.

I think this would be a great thing to do.

I have used https://github.com/huonw/travis-cargo to create documentation. A link to it is in the README.  So I am going to consider this finished unless someone has something else to add.

Looks good :)


Remove roletoken enable/disable option

Removed the roletoken option for backward compatibility.

Codecov Report

Merging #59 into master will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #59      +/-   ##
==========================================
- Coverage   86.76%   86.69%   -0.07%
==========================================
  Files          14       14
  Lines         642      639       -3
==========================================
- Hits          557      554       -3
  Misses         75       75
  Partials       10       10

Impacted Files
Coverage Δ

config/config.go
100.00% <ø> (ø)

usecase/authz_proxyd.go
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 4123ee7...7761d48. Read the comment docs.

Can help to check the pipeline?
The tag is empty.
https://app.circleci.com/pipelines/github/yahoojapan/authorization-proxy/322/workflows/8e58f988-9126-4f9d-9f5b-50a4abf0a9c8/jobs/901/parallel-runs/0/steps/0-103

@WindzCUHK
I think it's because I didn't tag it before I changed the title of the PR.
I did a rerun and it worked.
https://circleci.com/gh/yahoojapan/authorization-proxy/905?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

LGTM


nuitka and pendulum not working when using --standalone

Hi,
This is my version of nuitka:
0.6.5
Python: 3.6.8 (default, Aug  7 2019, 17:28:10)
Executable: /usr/bin/python3
OS: Linux
Arch: x86_64

Using python 3.6.8 from a CentOS package (not pyenv)
This is a 2-lines python program to reproduce the error:
sh-4.2# more test.py
import pendulum
print(pendulum.now().isoformat())

The python script works:
sh-4.2# python3 test.py
2019-11-08T20:40:45.336649+00:00

Things do work when using just --follow-imports
python3 -m nuitka --remove-output --follow-imports --include-package pendulum.locales  test.py
[...]
sh-4.2# ls -lh
-rwxr-xr-x 1 root root 5.1M Nov  8 20:42 test.bin
-rw-r--r-- 1 root root   51 Nov  8 20:40 test.py
sh-4.2# ./test.bin
2019-11-08T20:43:29.119512+00:00

But when using  --standalone, the created binary can t load:
sh-4.2# python3 -m nuitka --remove-output --follow-imports --standalone --include-package pendulum.locales  test.py
[...]
sh-4.2# ls ./test.dist/
_asyncio.so	    _codecs_kr.so     _dbm.so	       _lzma.so		    _socket.so	 grp.so		  libgdbm.so.4	       libncursesw.so.5      libstdc++.so.6  readline.so
_bisect.so	    _codecs_tw.so     _decimal.so      _multibytecodec.so   _sqlite3.so  libbz2.so.1	  libgdbm_compat.so.4  libpanelw.so.5	     libtinfo.so.5   select.so
_blake2.so	    _crypt.so	      _elementtree.so  _multiprocessing.so  _ssl.so	 libcom_err.so.2  libgssapi_krb5.so.2  libpcre.so.1	     libuuid.so.1    termios.so
_bz2.so		    _csv.so	      _gdbm.so	       _opcode.so	    _struct.so	 libcrypto.so.10  libk5crypto.so.3     libpython3.6m.so.1.0  libz.so.1	     test
_codecs_cn.so	    _ctypes.so	      _hashlib.so      _pickle.so	    array.so	 libexpat.so.1	  libkeyutils.so.1     libreadline.so.6      math.so	     unicodedata.so
_codecs_hk.so	    _curses.so	      _heapq.so        _posixsubprocess.so  audioop.so	 libffi.so.6	  libkrb5.so.3	       libselinux.so.1	     mmap.so	     zlib.so
_codecs_iso2022.so  _curses_panel.so  _json.so	       _random.so	    binascii.so  libfreebl3.so	  libkrb5support.so.0  libsqlite3.so.0	     pendulum
_codecs_jp.so	    _datetime.so      _lsprof.so       _sha3.so		    fcntl.so	 libgcc_s.so.1	  liblzma.so.5	       libssl.so.10	     pyexpat.so

sh-4.2# ./test.dist/test
Traceback (most recent call last):
  File "/quantivly/test.dist/test.py", line 1, in <module>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 656, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 626, in _load_backward_compatible
  File "/quantivly/test.dist/pendulum/__init__.py", line 9, in <module pendulum>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 656, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 626, in _load_backward_compatible
  File "/quantivly/test.dist/pendulum/datetime.py", line 11, in <module pendulum.datetime>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 656, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 626, in _load_backward_compatible
  File "/quantivly/test.dist/pendulum/date.py", line 10, in <module pendulum.date>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 656, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 626, in _load_backward_compatible
  File "/quantivly/test.dist/pendulum/helpers.py", line 43, in <module pendulum.helpers>
  File "/quantivly/test.dist/pendulum/formatting/difference_formatter.py", line 12, in __init__
  File "/quantivly/test.dist/pendulum/locales/locale.py", line 38, in load
ValueError: Locale [en] does not exist.

Any way to fix that?
looks like pyinstaller also had trouble with pendulum in the past
https://github.com/pyinstaller/pyinstaller/issues/3528
but i can t make nuitka work
thanks!

Supporting pendulum requires a few changes to Nuitka plugins:

Timezone data for pytz and pytzdata must be copied as data files to the script's .dist folder. Good to have that now!
pendulum itself insists on finding certain folders (which contain Python source only) at runtime. So those must be copied just like data files - which is unfortunate, but no killer.

I uploaded these changes to the Nuitka's jorj branch, which you can download as your new Nuitka version. You would end up having Nuitka v0.6.6rc7.
I also updated hinted compilation scripts to support these changes.

If you are unsure how to replace your Nuitka installation with something like the jorj branch, I can also send you a ZIP for the changed plugins, which you can use to replace your existing ones - drop a post here.

@benoitscherrer - any feedback?
This should be resolved by now ...

Hi Jorj,
So sorry for the late reply. I got caught into something else and didn't
come back to this.
Do you have an approximative idea of the time frame for this to be in the
main branch?
Until then yes the zip would be really helpful.
Thanks so much
Best
Benoit
On Sat, Dec 14, 2019, 07:17 Jorj X. McKie<EMAIL_ADDRESS>wrote:

@benoitscherrer https://github.com/benoitscherrer - any feedback?
This should be resolved by now ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Nuitka/Nuitka/issues/568?email_source=notifications&email_token=AFSOI3SBQQ6RHD44XXWSOXLQYTFGNA5CNFSM4JK6TTQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG4BKUQ#issuecomment-565712210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFSOI3RPKKETBHYG6AJICETQYTFGNANCNFSM4JK6TTQA
.

It is in 0.6.6 release whatever it is. So I am closing this for now, re-open as necessary


How can i map DTI data to CIFTI space ?

Is it available to map non-HCP DTI data to CIFTI ?

Hello Dr. Dickie,
I am interested in the first scenario you mention above - projecting diffusion metrics (MD and NODDI metrics) to the cortex for further analysis. Do you recommend myelin-style mapping vs ribbon-constrained to help account for partial voluming? If you have any example code for this use case, it would be much appreciated. Thanks!
Jeremy

Hello Dr. Dickie,
I am interested in the first scenario you mention above - projecting diffusion metrics (MD and NODDI metrics) to the cortex for further analysis. Do you recommend myelin-style mapping vs ribbon-constrained to help account for partial voluming? If you have any example code for this use case, it would be much appreciated. Thanks!
Jeremy

Hi Jeremy,
I am also trying to project NODDI metrics to the cortex for further analysis. I'm wondering if you figured this out/have any examples you could share?
It would be much appreciated!
Thanks,
Maya


Add dagger support

Hi,
Any luck with http://square.github.io/dagger/ ?

To the best of my knowledge there is no concrete solution due to how Dagger builds the graph/configuration. One has to provide explicit -keepnames entries for anything any module @Provides.

This worked for me
-keep class dagger.** { *; }
-keepclassmembers,allowobfuscation class * {
    @javax.inject.* *;
    @dagger.* *;
    <init>();
}
-keep class **$$ModuleAdapter
-keep class **$$InjectAdapter
-keep class **$$StaticInjection
-keep class javax.inject.** { *; }
-dontwarn dagger.internal.codegen.**
-dontwarn dagger.producers.internal.**
-dontwarn dagger.shaded.auto.common.**

I added a Dagger config from another PR. See https://github.com/krschultz/android-proguard-snippets/blob/master/libraries/proguard-square-dagger.pro. If that doesn't work we can revise it, but it was fairly close to what @ivazhnov suggested so worth a shot.


oidc: move reusable_worfklow_used field to the correct event

This should fix the reusable_workflow_used data quality issues we're seeing, which stem from us originally trying to get it at file_upload time, where the request has only a limited view into the original minted token's OIDC claims.
We instead now collect this field during mint_token, where the full set of OIDC claims is available to us.
h/t @miketheman for pointing this out, cc @facutuesca

also LGTM


Would there be a file to record all the dependencies in a machine readable way?

Recording all dependencies in a machine-readable file could be very helpful for users who always want to build and use the latest version of Centipede (e.g., FuzzBench, OSS-FUZZ).
For example, I just noticed that Centipede now requires OpenSSL(libssl-dev) to build, and updated FuzzBench accordingly, I would really appreciate it if we could do that automatically : )
(I really like the way you use clang-flags.txt to store flags.)

We don't have such a file right now.
It could be something simple, like install-dependencies-linux.sh that would apt-get, or some such. Will that work?
Current deps that I can think of:

bazel (to build centipede)
-lcrypto (from openssl) to build
clang (to build Centipede and then to build targets)
llvm-symbolize / objdump (at runtime)

(fresh clang is preferred as always, so it's a special case)
BTW, yes, requiring libssl-dev is a recent change. Before that bazel would pull boringssl sources, but it appeared to be too noisy (fresh clang would reject boringssl sources)

It could be something simple, like install-dependencies-linux.sh that would apt-get, or some such. Will that work?

Yes! That would be fantastic : )
That list of deps look pretty complete as well.
Just a minor question on Clang: I reckon we prefer clang-15 specifically, as we need its dataflow tracing feature?

not sure. The instrumentation (tracing loads and stores) has been in LLVM for a while, so clang-15 will work.
But the weak default implementations are there for just a week or so, and (citation needed) won't make it to clang-15.
You need weak default implementations with some build systems that build not only the fuzz targets but also other binaries
and those binaries won't link w/o weak default implementations.
I.e. most likely you will need fresh clang from trunk for tracing loads and stores.
clang-flags.txt currently does not contain trace-loads


ApidocsController#index returning "failed to parse JSON/YAML response"

I believe I have everything set up correctly, but when I go to the /apidocs endpoint, it serves me json rather than Swagger UI.
ApidocsController:
class ApidocsController < ActionController::Base
  include Swagger::Blocks

  swagger_root do
    key :swagger, '2.0'
    info do
      key :version, '3.0'
      key :title, 'My API'
      key :description, "The latest version of API"
    end
    key :host, 'localhost:3000'
    key :basePath, '/api/v3'
    key :consumes, ['application/json']
    key :produces, ['application/json']
  end

  # A list of all classes that have swagger_* declarations.
  SWAGGERED_CLASSES = [
    Api::V3::UsersController,
    User,
    self,
  ].freeze

  def index
    render json: Swagger::Blocks.build_root_json(SWAGGERED_CLASSES)
  end
end

route.rb:
resources :apidocs, only: [:index]
public/apidocs/index.html for Swagger UI:
window.swaggerUi = new SwaggerUi({
  url: '/apidocs',
  ...
});

the result:

nvm, got it to work!

@peyterkim Can you share the solution for others who might stumble on this issue? If it's simple.

@peyterkim Yes i am stuck at this point . can you tell me the solution
?


Bug: Cannot mount data folder from a network share

Describe the bug
When attempting to mount the data folder from a folder on a network share, I get the following error:
Data mounting error
More details:

Win 10, running using the following docker-compose file: Docker Compose file
Notable in the file above, I've created an archivebox_data cifs volume mounted to my NAS's UNC path.  I use this system on other compose files without issues.
The data folder was originally created on my C drive, then copied to the NAS after it started filling up my drive.

Steps to reproduce

Using the above docker compose file, run docker compose up.  To replicate, you will need to change the network share location.

This is likely due to a permissions issue, archivebox cannot use drives that coerce permissions to be owned by root (common mistake when setting up a network mount).
Can you check that you have CIFS set up to allow non-root ownership of files?