x264 build failure - /usr/bin/bash -j invalid option

Host Environment
-OS: Windows 10 1903 18362.388
-Compiler: VS2017 v15.9.16 and VS2019 v16.3.2
To Reproduce
Steps to reproduce the behavior:
./vcpkg install x264
(My default triplet is x64-windows and vcpkg is built using the -win64 option)
Failure logs
-Cut and past the appropriate build messages from the console output.
This is the same for both VS2017 and VS2019 except for the vcpkg directory
SYSTEM@ANDROMEDA 10/06/2019 18:30:59 D:\Git\vs2019
->vcpkg install x264
The following packages will be built and installed:
x264[core]:x64-windows
Starting package 1/1: x264:x64-windows
Building package x264[core]:x64-windows...
-- Using cached D:/Git/vcpkg.downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Using source at D:/Git/vs2019/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Using generator make
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x64-windows-dbg
-- Configuring x64-windows-rel
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
Command failed: D:/Git/vcpkg.downloads/tools/msys2/msys64/usr/bin/bash.exe --noprofile --norc -c -j 17 make
Working Directory: D:/Git/vs2019/buildtrees/x264/x64-windows-dbg
See logs for more information:
D:\Git\vs2019\buildtrees\x264\build-x64-windows-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_make.cmake:123 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_make.cmake:24 (vcpkg_build_make)
ports/x264/portfile.cmake:33 (vcpkg_install_make)
scripts/ports.cmake:94 (include)
Error: Building package x264:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: x264:x64-windows
Vcpkg version: 2019.09.12-nohash
Additionally, attach any relevant sections from the log files above.
build-x64-windows-dbg-err.log
-Please attach any additional failure logs mentioned in the console output.
Additional context
This is from the latest vcpkg "git pull" from git to my two different VCPKG roots, one for VS2017 and one for VS2019, performed at ~ 18:00 US Eastern Time.

@JackBoosY
not correct
msys64/usr/bin/bash.exe --noprofile --norc -c -j 17 make
it must be
msys64/usr/bin/bash.exe --noprofile --norc -c make -j 17
https://github.com/microsoft/vcpkg/commit/72af04ffe5ac68ec008299797636b8c32aef2ad1
?
COMMAND ${MAKE} ${MAKE_OPTS} -j ${VCPKG_CONCURRENCY}

I have the same error and have been looking into working around it. -j is an option for make, but is being passed into bash instead.
The issue stems from scripts/cmake/vcpkg_build_make.cmake lines 55 and 57-58, where the make command is being set in the options. When the make command is assembled on line 124, it sticks in some extra options in the wrong spot.
line 124: ${MAKE} -j ${VCPKG_CONCURRENCY} ${MAKE_OPTS}
expands to: path/to/bash.exe --noprofile --norc -c -j <some number> make
instead of : path/to/bash.exe --noprofile --norc -c make -j <some number>
I changed line 55 to:
set(MAKE ${BASH} --noprofile --norc -c ${_VCPKG_PROJECT_SUBPATH}make)
line 57-58 to:
set(MAKE_OPTS "")
set(INSTALL_OPTS "install")

This gets around the error, though it might be better to move the -j option to MAKE_OPTS instead of subverting the options and adding it willy-nilly like it currently does.
Sadly, the build still fails when trying to do the rename on line 37 of the portfile.cmake for x254
file(RENAME ${CURRENT_PACKAGES_DIR}/bin/x264.exe ${CURRENT_PACKAGES_DIR}/tools/x264/x264.exe)
The error is
file RENAME failed to rename

    D:/Tools/vcpkg/packages/x264_x64-windows/bin/x264.exe

  to

    D:/Tools/vcpkg/packages/x264_x64-windows/tools/x264/x264.exe

  because: File exists

I find this odd because the x264_x64-windows\tools\x264 directory is completely empty, so I'm not sure what file it thinks exists. I also do not have a x264_x64-windows/bin directory.

I just updated vcpkg and - out of curiousity - tried to install x264, now getting the same error message as @oracleoftroy:
For x86-windows:
D:\Code\Repos\vcpkg>vcpkg install x264
The following packages will be built and installed:
    x264[core]:x86-windows
Starting package 1/1: x264:x86-windows
Building package x264[core]:x86-windows...
-- Using cached D:/Code/Repos/vcpkg/downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Using source at D:/Code/Repos/vcpkg/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Using generator make
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x86-windows-dbg
-- Configuring x86-windows-rel
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Building x86-windows-dbg
-- Building x86-windows-rel
-- Installing x86-windows-dbg
-- Installing x86-windows-rel
CMake Error at ports/x264/portfile.cmake:37 (file):
  file RENAME failed to rename

    D:/Code/Repos/vcpkg/packages/x264_x86-windows/bin/x264.exe

  to

    D:/Code/Repos/vcpkg/packages/x264_x86-windows/tools/x264/x264.exe

  because: File exists

Call Stack (most recent call first):
  scripts/ports.cmake:94 (include)

For x64-windows:
D:\Code\Repos\vcpkg>vcpkg install x264:x64-windows
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpk
The following packages will be built and installed:
    x264[core]:x64-windows
Starting package 1/1: x264:x64-windows
Building package x264[core]:x64-windows...
-- Using cached D:/Code/Repos/vcpkg/downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Using source at D:/Code/Repos/vcpkg/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Using generator make
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x64-windows-dbg
-- Configuring x64-windows-rel
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing x64-windows-dbg
-- Installing x64-windows-rel
CMake Error at ports/x264/portfile.cmake:37 (file):
  file RENAME failed to rename

    D:/Code/Repos/vcpkg/packages/x264_x64-windows/bin/x264.exe

  to

    D:/Code/Repos/vcpkg/packages/x264_x64-windows/tools/x264/x264.exe

  because: File exists

Call Stack (most recent call first):
  scripts/ports.cmake:94 (include)

The "toold" directory is stays empty during the building process, neither an "x264" subfolder nor an x264.exe are present there at any time, so I honestly don't know why the rename command fails. Maybe "copy" would be better here?

After updating vcpkg, getting the same problem here.
Stdout
Building package x264[core]:x64-windows...
-- Using cached D:/Repository/vcpkg/downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Using source at D:/Repository/vcpkg/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Using generator make
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x64-windows-dbg
-- Configuring x64-windows-rel
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Building x64-windows-dbg
-- Building x64-windows-rel
-- Installing x64-windows-dbg
-- Installing x64-windows-rel
CMake Error at ports/x264/portfile.cmake:37 (file):
  file RENAME failed to rename

    D:/Repository/vcpkg/packages/x264_x64-windows/bin/x264.exe

  to

    D:/Repository/vcpkg/packages/x264_x64-windows/tools/x264/x264.exe

  because: File exists

Call Stack (most recent call first):
  scripts/ports.cmake:94 (include)

Error: Building package x264:x64-windows failed with: BUILD_FAILED

make: Nothing to be done for 'default'. I'm looking into it.

Just ran into the same problem and looking forward to the fix

Hi @timautry, thanks for reporting this issue.
I've fixed it, please update vcpkg and rebuild x264.
Thanks.

Thank you @JackBoosY - works great on both latest builds of VS2017 and VS2019 - super work and I appreciate it very much. Take care and have a wonderful week!!!

I'm coming across a similar error message when trying to build x264. Let me know if I should post this as a new issue, I suspect it will be an easy fix as I am a novice and unfamiliar with compilers.
OS: Windows 10 1909
Compiler: VS 2019 16.6.3
C:\vcpkg-master> .\vcpkg install x264
Computing installation plan...
The following packages will be built and installed:
x264[core]:x86-windows
Starting package 1/1: x264:x86-windows
Building package x264[core]:x86-windows...
-- Using cached C:/vcpkg-master/downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Using source at C:/vcpkg-master/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x86-windows-dbg
-- Configuring x86-windows-rel
-- Building x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):
Command failed: C:/vcpkg-master/downloads/tools/msys2/msys64/usr/bin/make.exe -j 9 --trace -f Makefile all
Working Directory: C:/vcpkg-master/buildtrees/x264/x86-windows-dbg
See logs for more information:
C:\vcpkg-master\buildtrees\x264\build-x86-windows-dbg-out.log
C:\vcpkg-master\buildtrees\x264\build-x86-windows-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_make.cmake:200 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_make.cmake:24 (vcpkg_build_make)
ports/x264/portfile.cmake:29 (vcpkg_install_make)
scripts/ports.cmake:76 (include)
Error: Building package x264:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: x264:x86-windows
Vcpkg version: 2020.02.04-nohash
Additionally, attach any relevant sections from the log files above.
build-x86-windows-dbg-out.log
build-x86-windows-dbg-err.log

Hello,
I just checked and the package build fails both for x86 and x64 again as well, this time with a fatal MSYS2 error (it seems configure arguments are passed to link.exe instead, configure isn't run at all):
D:\Code\Repos\vcpkg>vcpkg install x264
Computing installation plan...
The following packages will be built and installed:
x264[core]:x86-windows
Starting package 1/1: x264:x86-windows
Building package x264[core]:x86-windows...
-- Downloading https://github.com/mirror/x264/archive/303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz...
-- Extracting source D:/Code/Repos/vcpkg/downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Applying patch uwp-cflags.patch
-- Using source at D:/Code/Repos/vcpkg/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
Command failed: D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/bin/bash.exe --noprofile --norc --debug -c " CC='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo' CXX='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo' LD='link.exe -verbose' AR='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/ar-lib lib.exe -verbose' RANLIB=':' CCAS=':' NM='dumpbin.exe -symbols -headers -all' DLLTOOL='link.exe -verbose -dll' ./../src/14d026c3bd-bca2ebf740/configure --build=x86_64-pc-mingw32 --target=i686-pc-mingw32 --host=i686-pc-mingw32 --enable-strip --disable-lavf --disable-swscale --disable-avs --disable-ffms --disable-gpac --disable-lsmash --disable-asm --enable-debug --disable-silent-rules --verbose --enable-shared --disable-static --prefix=/D/Code/Repos/vcpkg/installed/x86-windows/debug --bindir='${prefix}'/../tools/x264/debug/bin --sbindir='${prefix}'/../tools/x264/deb
ug/sbin --includedir='${prefix}'/../include --datarootdir='${prefix}'/share/x264"
Working Directory: D:/Code/Repos/vcpkg/buildtrees/x264/x86-windows-dbg
Error code: 1
See logs for more information:
D:\Code\Repos\vcpkg\buildtrees\x264\config-x86-windows-dbg-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_make.cmake:461 (vcpkg_execute_required_process)
ports/x264/portfile.cmake:15 (vcpkg_configure_make)
scripts/ports.cmake:76 (include)
Error: Building package x264:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: x264:x86-windows
Vcpkg version: 2020.02.04-nohash
Additionally, attach any relevant sections from the log files above.
D:\Code\Repos\vcpkg>
Find my log files attached, many thanks in advance for helping!
x264.zip

@VFoV Can you make sure your vcpkg is latest?

@VFoV Can you make sure your vcpkg is latest?

I've just reinstalled and ran the bootstrapping and integration and run the command:
C:\vcpkg-master> .\vcpkg update
Using local portfile versions. To update the local portfiles, use git pull.
No packages need updating.

@VFoV Can you make sure your vcpkg is latest?

Hello, I re-cloned vcpkg from the github page, re-ran the boostrapping and integration then ran .\vcpkg update. I then ran the x264 install again and
config.log
got this error:
Starting package 68/79: x264:x64-windows
Building package x264[core]:x64-windows...
-- Downloading https://github.com/mirror/x264/archive/303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz...
-- Extracting source C:/vcpkg/downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Applying patch uwp-cflags.patch
-- Using source at C:/vcpkg/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
Command failed: C:/vcpkg/downloads/tools/msys2/msys64/usr/bin/bash.exe --noprofile --norc --debug -c " CC='C:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo' CXX='C:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo' LD='link.exe -verbose' AR='C:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/ar-lib lib.exe -verbose' RANLIB=':' CCAS=':' NM='dumpbin.exe -symbols -headers -all' DLLTOOL='link.exe -verbose -dll' ./../src/14d026c3bd-bca2ebf740/configure --build=x86_64-pc-mingw32 --target=x86_64-pc-mingw32 --host=x86_64-pc-mingw32 --enable-strip --disable-lavf --disable-swscale --disable-avs --disable-ffms --disable-gpac --disable-lsmash --disable-asm --enable-debug --disable-silent-rules --verbose --enable-shared --disable-static --prefix=/C/vcpkg/installed/x64-windows/debug --bindir='${prefix}'/../tools/x264/debug/bin --sbindir='${prefix}'/../tools/x264/debug/sbin --includedir='${prefix}'/../include --datarootdir='${prefix}'/share/x264"
Working Directory: C:/vcpkg/buildtrees/x264/x64-windows-dbg
Error code: 1
See logs for more information:
C:\vcpkg\buildtrees\x264\config-x64-windows-dbg-out.log
config-x64-windows-dbg-out.log

Hello,
I'm back to this topic because I run into the very same issue as described by @VFoV when trying to build x264 x86 / x64 via vcpkg, here're the error messages:
x86-windows:
D:\Code\Repos\vcpkg>vcpkg install x264:x86-windows
Computing installation plan...
The following packages will be built and installed:
    x264[core]:x86-windows
Starting package 1/1: x264:x86-windows
Building package x264[core]:x86-windows...
-- Downloading https://github.com/mirror/x264/archive/303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz...
-- Extracting source D:/Code/Repos/vcpkg/downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Applying patch uwp-cflags.patch
-- Using source at D:/Code/Repos/vcpkg/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x86-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/bin/bash.exe --noprofile --norc --debug -c " CC='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo' CXX='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo' LD='link.exe -verbose' AR='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/ar-lib lib.exe -verbose' RANLIB=':' CCAS=':' NM='dumpbin.exe -symbols -headers -all' DLLTOOL='link.exe -verbose -dll' ./../src/14d026c3bd-bca2ebf740/configure --build=x86_64-pc-mingw32 --target=i686-pc-mingw32 --host=i686-pc-mingw32 --enable-strip --disable-lavf --disable-swscale --disable-avs --disable-ffms --disable-gpac --disable-lsmash --disable-asm --enable-debug --disable-silent-rules --verbose --enable-shared --disable-static --prefix=/D/Code/Repos/vcpkg/installed/x86-windows/debug --bindir='${prefix}'/../tools/x264/debug/bin --sbindir='${prefix}'/../tools/x264/deb
ug/sbin --includedir='${prefix}'/../include --datarootdir='${prefix}'/share/x264"
    Working Directory: D:/Code/Repos/vcpkg/buildtrees/x264/x86-windows-dbg
    Error code: 1
    See logs for more information:
      D:\Code\Repos\vcpkg\buildtrees\x264\config-x86-windows-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:461 (vcpkg_execute_required_process)
  ports/x264/portfile.cmake:15 (vcpkg_configure_make)
  scripts/ports.cmake:76 (include)

Error: Building package x264:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: x264:x86-windows
  Vcpkg version: 2020.06.15-nohash

x64-windows:
D:\Code\Repos\vcpkg>vcpkg install x264:x64-windows
Computing installation plan...
The following packages will be built and installed:
    x264[core]:x64-windows
Starting package 1/1: x264:x64-windows
Building package x264[core]:x64-windows...
-- Using cached D:/Code/Repos/vcpkg/downloads/mirror-x264-303c484ec828ed0d8bfe743500e70314d026c3bd.tar.gz
-- Using source at D:/Code/Repos/vcpkg/buildtrees/x264/src/14d026c3bd-bca2ebf740
-- Acquiring MSYS Packages...
-- Acquiring MSYS Packages... OK
-- Configuring x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/bin/bash.exe --noprofile --norc --debug -c " CC='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo' CXX='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo' LD='link.exe -verbose' AR='D:/Code/Repos/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/ar-lib lib.exe -verbose' RANLIB=':' CCAS=':' NM='dumpbin.exe -symbols -headers -all' DLLTOOL='link.exe -verbose -dll' ./../src/14d026c3bd-bca2ebf740/configure --build=x86_64-pc-mingw32 --target=x86_64-pc-mingw32 --host=x86_64-pc-mingw32 --enable-strip --disable-lavf --disable-swscale --disable-avs --disable-ffms --disable-gpac --disable-lsmash --disable-asm --enable-debug --disable-silent-rules --verbose --enable-shared --disable-static --prefix=/D/Code/Repos/vcpkg/installed/x64-windows/debug --bindir='${prefix}'/../tools/x264/debug/bin --sbindir='${prefix}'/../tools/x264
/debug/sbin --includedir='${prefix}'/../include --datarootdir='${prefix}'/share/x264"
    Working Directory: D:/Code/Repos/vcpkg/buildtrees/x264/x64-windows-dbg
    Error code: 1
    See logs for more information:
      D:\Code\Repos\vcpkg\buildtrees\x264\config-x64-windows-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:461 (vcpkg_execute_required_process)
  ports/x264/portfile.cmake:15 (vcpkg_configure_make)
  scripts/ports.cmake:76 (include)

Error: Building package x264:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: x264:x64-windows
  Vcpkg version: 2020.06.15-nohash

It looks as if configure arguments were passed to link.exe instead, but apparently the src itself is flawed: I tried to build the program using my personal MSYS2 installation and x86 failed with exactly the same "No C compiler found" error when running ./configure, while the x64 build succeeded. Maybe x264 does not support 32-bit builds in the first place? But even if that would be true it would unfortunately not explain why the x64-windows build also fails with vcpkg. Find all my logs attached, thank you!
x264.zip

In config.log:
checking for -Werror=unknown-warning-option... no
Failed commandline was:
--------------------------------------------------
F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo conftest.c  -D_WIN32_WINNT=0x0601 -DWIN32_LEAN_AND_MEAN -DWIN32 -D_WINDOWS -MDd -D_DEBUG -Ob0 -Od  -Wall -I. -I$(SRCPATH) -D_POSIX_C_SOURCE=200112L  -Werror=unknown-warning-option  -LF:/vcpkg/installed/x86-windows/debug/lib -VERBOSE -no-undefined -machine:x86  -o conftest
./../src/14d026c3bd-bca2ebf740.clean/configure: line 158: F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile: No such file or directory
--------------------------------------------------
Failed program was:
--------------------------------------------------
int main (void) {  return 0; }
--------------------------------------------------
checking for -lshell32... no
Failed commandline was:
--------------------------------------------------
F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo conftest.c  -D_WIN32_WINNT=0x0601 -DWIN32_LEAN_AND_MEAN -DWIN32 -D_WINDOWS -MDd -D_DEBUG -Ob0 -Od  -Wall -I. -I$(SRCPATH) -D_POSIX_C_SOURCE=200112L  -lshell32  -LF:/vcpkg/installed/x86-windows/debug/lib -VERBOSE -no-undefined -machine:x86  -o conftest
./../src/14d026c3bd-bca2ebf740.clean/configure: line 158: F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile: No such file or directory
--------------------------------------------------
Failed program was:
--------------------------------------------------
int main (void) {  return 0; }
--------------------------------------------------
checking whether windres works... no
Failed commandline was:
--------------------------------------------------
windres --target=pe-i386  -o conftest.o conftest.rc
/bin/sh: gcc: command not found
windres: preprocessing failed.
--------------------------------------------------
Failed program was:
--------------------------------------------------
0 RCDATA {0}
--------------------------------------------------
checking whether !WINAPI_FAMILY_PARTITION(WINAPI_PARTITION_DESKTOP) is true... no
--------------------------------------------------
./../src/14d026c3bd-bca2ebf740.clean/configure: line 189: F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile: No such file or directory
--------------------------------------------------
Failed program was:
--------------------------------------------------
#include <winapifamily.h>
#if !(!WINAPI_FAMILY_PARTITION(WINAPI_PARTITION_DESKTOP))
#error
#endif
--------------------------------------------------
x264 configure script
Command line options: "--build=i686-pc-mingw32" "--target=i686-pc-mingw32" "--host=i686-pc-mingw32" "--enable-strip" "--disable-lavf" "--disable-swscale" "--disable-avs" "--disable-ffms" "--disable-gpac" "--disable-lsmash" "--disable-asm" "--enable-debug" "--disable-silent-rules" "--verbose" "--enable-shared" "--disable-static" "--prefix=/F/vcpkg/installed/x86-windows/debug" "--bindir=${prefix}/../tools/x264/debug/bin" "--sbindir=${prefix}/../tools/x264/debug/sbin" "--includedir=${prefix}/../include" "--datarootdir=${prefix}/share/x264"

checking whether F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo works... no
Failed commandline was:
--------------------------------------------------
F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile cl.exe -nologo conftest.c -m32  -D_WIN32_WINNT=0x0601 -DWIN32_LEAN_AND_MEAN -DWIN32 -D_WINDOWS -MDd -D_DEBUG -Ob0 -Od  -Wall -I. -I$(SRCPATH) -D_POSIX_C_SOURCE=200112L    -m32 -LF:/vcpkg/installed/x86-windows/debug/lib -VERBOSE -no-undefined -machine:x86   -Wl,--large-address-aware -Wl,--dynamicbase,--nxcompat,--tsaware -o conftest
./../src/14d026c3bd-bca2ebf740.clean/configure: line 158: F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile: No such file or directory
--------------------------------------------------
Failed program was:
--------------------------------------------------
int main (void) {  return 0; }
--------------------------------------------------
DIED: No working C compiler found.

@Neumann-A Could you please take a look?
Thanks.

F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.16/compile: No such file or directory
Only have F:/vcpkg/downloads/tools/msys2/msys64/usr/share/automake-1.15 on my machine.

I think #11836 should fix this issue.

Looks good, let's hope for the best. Thank you all very much!

I close, I no longer use product.

Well, but other people, e.g. myself still do, you know? So please don't stop working on a fix, many thanks!

@Christsnatcher Anyway, I'm still tracking this issue.

@JackBoosY Thank you very much, that's really appreciated.


Hardware and Software I use Thorium on :)

Add all the stuffz here

80% of the time I'm using Windows. I need to use Windows for work and I also like gaming, which is possible on Linux, but still a lot easier on Windows.  I work in healthcare.  Although we use computers all the time to record information, my work is not directly related to computers.

Operating System: Windows 11 23H2 10.0.22631.2861 as of today.
Hardware: Razer Blade 18 laptop, early 2023 edition.  Intel Core i9-13950HX processor, 64 gigabytes of DDR5 RAM running at 5,200 MHz, NVidia RTX 4090 Laptop GPU (16 GB GDDR6 VRAM).

10% of the time, I like playing around with Linux and I find that running Linux in WSL (under Windows) is the most convenient option. I write Python and build a few programs from source.  I have Ubuntu 23.10 installed in WSL and I added Thorium to my source list so I can use apt to update it.  i.e. I use the same laptop to run Thorium for Linux amd64.
I can run Thorium in a Window using WSL (or technically WSLg), which I think is Wayland and XWayland based.  However, I get better results running graphical apps through an X server, so I'm currently running Thorium through an X server called "x410".  So when I'm downloading or searching for stuff that is Linux related, I use the Linux (.deb) version of Thorium on the same laptop, basically running it in VM (i.e. WSL) while Windows is running.  WSL does a pretty good job at exposing the hardware (the number of threads, the GPU and the processor compiler options) to the user.  e.g. I can use WSL to compile a linux program using all available threads with 100% CPU usage, and thehe Nvidia GPU, including Cuda, is usable from WSL. I had a look at the work Alex put in to compile an optimized Chromium and I'm nowhere near as technically proficient as Alex.

10% of the time, I actually run Thorium on (almost) the equivalent of a Raspberry Pi, that runs under Termux and Proot on my Android Phone.  It's a Samsung Z Fold 5 so I actually get a usable screen when its unfolded.  Thorium for Raspi works perfectly.
All the best !

Thanks @Alex313031 , much appreciated.

@dbonner OK, so I couldn't use -march=raptorlake because it implies -mavxvnni which causes compilation errors in ffmpeg and libaom. However, I did use the AVX2 files and I can use -mtune=raptorlake. So it essentially will be an AVX2 build except the scheduling and SIMD dispatch will be tuned and optimized for 13th gen intel. I would be interested to see what performance gains it gets.
@ms178 After this, the plan is to compile AVX2 Linux release (which @dbonner you will probably also want for your 10% linux time), and then the Windows on ARM release, and finally the 32 Bit Windows 7 releases (which I screwed up by messing up a single line of code lol)

Sounds good. Happy to benchmark the 13th gen intel tuned Windows build too.

@dbonner @ms178 Your personal build and the AVX2 Linux build are ready!
I made a new repo called "thorium other" for builds that dont fit into any of the other repo's release sections.
@dbonner Here is your Raptorlake Windows release > https://github.com/Alex313031/Thorium-Other/releases/tag/119.0.6045.214-1
@ms178 Here is your AVX2 Linux release > https://github.com/Alex313031/Thorium-Other/releases/tag/119.0.6045.214

@Alex313031 Thanks so much. They are both working well.

@dbonner Can you run a speedometer and let me know what the raptorlake scores compared to vanilla thorium-win?

@Alex313031 I've benched the AVX2 vs the AVX build with Speedometer on my Haswell-Xeon, the scores are similar on both (around 154 - 156), albeit a little better and with less variance on the AVX2 build.

@Alex313031 Here's the Speedometer 2.1 scores.  These were done on a new profile with all optional extensions removed.  Raptorlake scored the same as Vanilla (approx 425). This probably means that everyone running the AVX2 build gets the benefit of Thorium's speed (which is good). :)
Thorium_RaptorLake M119.0.6045.214:
Summary: 423 +- 14
Detailed Results:
Iteration 1	387.8 runs/min
Iteration 2	407.2 runs/min
Iteration 3	416.1 runs/min
Iteration 4	427.3 runs/min
Iteration 5	416.9 runs/min
Iteration 6	417.9 runs/min
Iteration 7	432.3 runs/min
Iteration 8	432.3 runs/min
Iteration 9	435.5 runs/min
Iteration 10	459.5 runs/min
Arithmetic Mean:423 ± 14 (3.2%)
===================================
Thorium-Win-AVX2 M119.0.6045.214:
Summary: 425 +- 12
Detailed Results:
Iteration 1	390.8 runs/min
Iteration 2	433.3 runs/min
Iteration 3	402.2 runs/min
Iteration 4	430.4 runs/min
Iteration 5	425.1 runs/min
Iteration 6	432.0 runs/min
Iteration 7	443.0 runs/min
Iteration 8	435.7 runs/min
Iteration 9	437.5 runs/min
Iteration 10	418.3 runs/min
Arithmetic Mean:425 ± 12 (2.8%)

@dbonner Interesting. However, it is tuned for Raptorlake (meaning it takes advantage of the pipeline design and big.LITTLE architecture), so even though it achieved the same score, it is probably using less CPU to do so.


Note when giving up on workshop counts

We have space in each event to record how many people attended.
#514 already asks to break this out to track attrition - some people have actually been providing that.
Some, however, don't respond at all after 3-4 requests at which point I give up asking.  I want to record this but I'm not sure how.  Any ideas?

Hm - can you send me a list of workshops and I'll chase them? Sending us
a head count is a condition of using the name and logo.

I'll start making a list and share it with @gvwilson
It's not many but enough to note.

Of the workshops listed here (https://amy.software-carpentry.org/workshops/reports/workshop_issues), everyone from Aug 1, 2015 up until one week from present day has been asked at least 1-2 times, some more often.   I typically send a "How'd it go? Send us counts/other data" email within a week after the workshop ends.
I'll continue to go farther back through the rest of 2015.

I've mailed the instructors of every workshop for which we don't have
attendance figures up to the end of September 2015.  Responses are
starting to come back (as are bounced messages); I'll update AMY as I
get stuff.

OK, I agree with @maneesha that we need a way to mark a workshop as "giving up on collecting data". I think this should be the same tag that we use for instructor training events that are so far in the past that people who attended them are officially deemed unlikely to ever complete.  "stalled" doesn't seem like the right tag, so how about "closed"?  We used to use that term to mean "closed enrolment", i.e., only people from a particular institution could enrol, but I don't think we're doing that any more. @pbanaszkiewicz thoughts as well?

@gvwilson we can't use attendance field to indicate the fact that we'll not going to get any numbers for these particular workshops.
I think we need to add one more tag just for that…

stalled is available but should be used in two other contexts, I don't want it to be used here as well
closed brings ambiguity since we have a Event.completed field
no updates? Or is there a single word in English that means "no chance getting new data"?

I think we're going to wind up using all the synonyms.  @maneesha any
thoughts?

I'm not sure what word to use.  We are using stalled to refer to Events where contact was initiated but then went nowhere and Instructors who started training but aren't going to finish.  We could use stalled if it applied attendance count and not the event itself.
@pbanaszkiewicz I think the closest to a single word in English is the phrase "lost cause."

On Tue, Nov 24, 2015 at 09:20:58AM -0800, Piotr Banaszkiewicz wrote:

no updates? Or is there a single word in English that means "no
chance getting new data"?

Unresponsive?

+1 to "unresponsive" for workshops that we were negotiating with but
that don't look like they're going to materialize.
I suggest "finalized" for instructor training events that are old enough
that we're giving up on participants, and for regular workshops where
we're giving up on collecting information about attendance.

"Unresponsive" might be right for workshops where we aren't going to get an attendance count.
It's not quite right for the workshops where we were negotiating but nothing's going to happen.  Many times it's not that they were unresponsive, but we were in contact and it's that timing, budget, etc. wasn't working out and they backed out.  So I prefer "stalled" there.

Okay, I'll add "unresponsive" to the #581 as well as a help_text with meanings of some of the options there ("stalled", "unresponsive").


How to run PDF plugin?

Hi there!
Please tell -- how to run PDF plugin? I have already run legacy SupermemoAssistant, but what to do next? Ctrl+Win+i doesn't work.

Hello,
You need the new SuperMemoAssistant which you can find here https://github.com/supermemo/SuperMemoAssistant.
You have to compile it yourself for now, until the beta starts.

hello,
I need to know how to compile SMA in order to run the pdf plugin.
I ask if there is any way to run the plugin with a script, in the same way that the supermemo occlussion is executed, which works very well for me.
thanks for your work, the oclussion plugin It helped me a lot

Hi, i am still waiting how to compile SMA to run pdf plugin and image oclussion. Sorry but i am not a programer because of that i need help to compile

Please check https://github.com/supermemo/SuperMemoAssistant for instructions.


Is OAS a safe acronym for OpenAPI Spec?

Should we call OpenAPI Spec as OAS, as Organization of American States also uses the same acronym?
http://www.oas.org/en/
https://twitter.com/OAS_official
This conflict also causes issues with searching it on google or twitter. Even #OAS (hashtag) has been collectively used by people to refer to both.
https://twitter.com/search?src=typd&q=%23OAS
Thanks,
Muhammad

Yes. And the OAI is also https://www.openarchives.org. A lot of acronyms have multiple meanings, sometimes even the same field.


IntendedFor missing file error not specific to number of missing files

If one of the files listed in the IntendedFor field does not exist, the error raised states that all of the files listed don't exist. Example:
/sub-010029/ses-02/fmap/sub-010029_ses-02_acq-GEfmap_run-02_phasediff.nii.gz
'IntendedFor' property of this fieldmap ('ses-02/func/sub-010029_ses-02_task-rest_acq-AP_run-02_bold.nii.gz,ses-02/func/sub-010029_ses-02_task-rest_acq-PA_run-02_bold.nii.gz') does not point to an existing file. Please mind that this value should not include subject level directory ('/sub-010029/').
In this example, 'ses-02/func/sub-010029_ses-02_task-rest_acq-AP_run-02_bold.nii.gz' actually does exists and 'ses-02/func/sub-010029_ses-02_task-rest_acq-PA_run-02_bold.nii.gz' does not. However, the error states that both don't exist.

@jbwexler I tried recreating the error with latest version on bids but failed.. however was able to generate error using bids-validator installed on TACC.
Can you install latest version and check if missing IntendedFor file error is generated..?
Looks like newer version is not generating the error wheee intended for files are missing.


New quiz regarding..

I think we should increase the number of the quiz and we should do it with more effective and efficient method.

Ok we will work on that


chore: release 1.0.0

:robot: I have created a release *beep* *boop*
1.0.0 (2024-12-09)
Features

trying again from 0 (65dc207)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/leouchoapedreira/fix-release-please/releases/tag/v1.0.0 :sunflower:


Fix the issue with TypeError hasHeader is not a function

When deploying to netlify or AWS (both depend on AWS-lambda)
The SSR components (using getServerSideProps fails with the following
error:
  ERROR	TypeError: res.hasHeader is not a function
    at sendPayload (/var/task/pages/test.js:5787:41)
    at renderReqToHTML (/var/task/pages/test.js:1773:13)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Module.render (/var/task/pages/test.js:1816:22)

This is caused by nextjs trying to use the default node hasHeader
method here: https://github.com/zeit/next.js/blob/v9.3.1/packages/next/next-server/server/send-payload.ts#L25
This commit fix the issue reported here: zeit/next.js#11223
which I could verify also happening on our stack by adding the method
that mimics the nodeJS method (using res.getHeader(name) internally wrapping it
in boolean response)
Previously fixed for next-aws-lambda in #329
also fix the header inconsistencies previously fixed for next-aws-lambda in #331

Thanks again 🙏

What's the ETA of this getting into release?

I've just published it. Should be available in<EMAIL_ADDRESS>🎉


Source code for updated clustering tutorial

The source code for the updated ML.NET clustering tutorial. Uses a new "dynamic" API.
Rather than edit existing sample code:
https://github.com/dotnet/samples/tree/master/machine-learning/tutorials/IrisClustering
I've decided to use it as the starting point for a new solution presented in this PR.
Thus, this PR is safe to merge to master. It wouldn't break any existing references in the dotnet/docs repo.
Supports dotnet/docs#9620
I'll delete the old clustering code after the PR in the docs repo is merged.
/cc: @JRAlexander

@rpetrusha thanks!


Add overflow scroll to plots

Plots that plot individual MA's will cut off if enough MA's are selected

Fixed in 069c792


Changed from Role/RoleBinding to ClusterRole/ClusterRoleBinding

This PR updates the Role to be a ClusterRole and RoleBinding to be ClusterRoleBinding. Role now grants permission to the hive.openshift.io api groups and clusterdeployments resources.
Signed-off-by: Tejas Parikh<EMAIL_ADDRESS>

/lgtm

/lgtm


Disabled element won't show tooltip

 <button
	onClick={onCheckoutPress}
     className="button primary font-14 font-400 full"
     disabled={true}
     data-tip="Disabled"
     data-for="checkout-button"
 >
     Save
 </button>

 <ReactToolTip
       id="checkout-button"
/>

The tooltip won't show if button is disabled.

Same issue here, but it only occurs with (disabled) buttons, not all elements.
As a workaround, I wrapped my disabled button inside a span element :

    <button disabled={true}>Click</button>

I was bit by the same issue. Good idea on the workaround

+1, guess i'm doing the workaround 🤕

Hm, don't really like the wrapping workaround, as it can mess up things like menu items etc, that rely on a certain DOM structure. I think a very common scenario is to want to show a tool-tip if a button is disabled, to explain to the  user why it's disabled.

Keep the button inside the  tags then you can get the tooltip for disabled buttons. This is the best you can do instead of using warning
         <button disabled> Save </button>

Hm, don't really like the wrapping workaround, as it can mess up things like menu items etc, that rely on a certain DOM structure. I think a very common scenario is to want to show a tool-tip if a button is disabled, to explain to the user why it's disabled.

can't stress this more.

I haven't full tested it yet, but I have a situation where wrapping in  ...  it makes tooltip appear, but don't disappear.

+1

If you have another tag in disabled button you can set tooltip on it as well.

The workaround that worked best for me is to put the span inside the button:
<button disabled={true}>

    Click

</button>

^ you have to style the span though to be full height of the button, otherwise the tip will trigger only over the text.

this is probably gonna be hard to solve without introducing some higher-level code (which, i'm not sure is desired for this library); the issue stems from the native behavior of disabled elements (see this demo for an illustration of this behavior).
details:
the way that react-tooltip responds to user interaction relies on binding native dom events to the button (namely, mouseenter and focus), as seen in the source code, on the main file.
these events are not triggered by the user agent, if the element is marked as disabled. W3C's recommendation on this states that engines should prevent dispatching click events, but apparently vendor implementations have broadened this definition (or probably there's a spec in place that i'm not aware of).

also, here's my current take for a workaround:
export default const FormControl = ({
  tag: FormControlType,
  ...props
}) => {
  const tooltipAttributes = Object.entries(props)
    .filter(([key, value]) => key.startsWith('data-'))
    .reduce((accum, [key, value]) => {
      accum[key] = value
      return accum
    }, {})

  return props.disabled && tooltipAttributes['data-tip'] ? (

      <FormControlType {...props} />

  ) : (
    <FormControlType {...props} {...tooltipAttributes} />
  )
}

this implementation has an obvious limitation; it assumes all data-* attributes belong to react-tooltip, but other then that, it's just a convenient way to encapsulate all that wrapper shenanigans into a nice package.
example usage:
const Button = ({className = '', ...props}) => (
  <FormControl
    {...props}
    tag="button"
    className={`drifter-button ${className}`}
  />
)

it can also be used for its declarative abstraction-level of form-control components, that is - we can include CSS rules that are common to buttons, inputs, selects etc. (ever found yourself constantly repeating stuff like outline: 0 across form control components? i know i did..).

The workaround that worked best for me is to put the span inside the button:
<button disabled={true}>

    Click

</button>

Works great, thanks :)

updating rc-tooltip to latest version made it work


Support Python 3.9 with dbt >= 0.20.0

If we do decide to release on PyPi there's a GitHub action we can recycle from SQLFluff that automatically publishes when you make a new GitHub release.

If we do decide to release on PyPi there's a GitHub action we can recycle from SQLFluff that automatically publishes when you make a new GitHub release.

That'd be great.  I'll look back at my notes for what was left to do before publishing to PyPi.


On Premise Support Clarity Needed

The main docs page for Application Insights (https://docs.microsoft.com/en-us/azure/application-insights/app-insights-overview) says your "application can run anywhere - it doesn't have to be hosted in Azure."
This page (https://docs.microsoft.com/en-us/azure/application-insights/app-insights-profiler) seems to hint that it does need to be in Azure.  (The language is all about what Azure offerings it is compatible with.)
A clear statement on this would be a nice addition.

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

ID: c30bf4fa-902a-c12d-179f-1829c0b967be
Version Independent ID: 6b3c7ae8-f3bb-dc4b-ed5b-a6e2190dacfd
Content: Profile live web apps on Azure with Application Insights Profiler
Content Source: articles/application-insights/app-insights-profiler.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@Vaccano Thank you for the feedback!  We are doing a bit of research and will get back to you shortly.

@Vaccano While there are features that require the Azure Portal, you can use the Application Insights SDK without an Azure account.  An example of this can be found in the following document that talks about viewing Application Insights telemetry in Visual Studio while debugging (pay attention to the note in blue):
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-asp-net
I tried this out myself and was able to get it to work.  Note that I updated the SDK but did not click on "Get Started" in Application Insights Configuration.

Does that answer your question?

@Vaccano to add on to @kobulloc-MSFT's response, in general for App Insights your app can run anywhere. In Azure, on-prem, or in another public cloud. The caveat is that while the app can run anywhere it still needs to be able to communicate with Azure. We list the firewall requirements in this doc. So as long as your app isn't air gapped and can accommodate the necessary firewall exceptions,  you should be able to take advantage of App Insights.

@kobulloc-MSFT - My personal question is answered.  But in interest of the clarity of the docs, it may be nice to indicate in the "Enable Profiler for your Web Apps web app" that those are the instructions for your service if it is hosted in Azure.
The absence of any other instructions seems to indicate that there are no other options.
Again, this is just for others going down the path I did.  I, personally, am not confused on this issue any more.
Thank you for all your help!

@Vaccano Thanks for the feedback and for flagging this for us to take a second look. We have gotten further clarification and added the following to the docs. The change will publish to the public repo this afternoon.

Which then links to this:


NATIVE and HOST vars don't work properly from config.mak

The top-level Makefile interprets the NATIVE, HOST, and TARGET variables before including config.mak, and thus does not fully honor settings made for them in config.mak. Apparently they were only tested via the command line, which is the intended usage, but this intent is not made clear in the documentation and is a regression vs old versions. Specifically:

NATIVE doesn't work at all from config.mak; the only place it's used is in the logic to set HOST:=$(TARGET), before the include.
HOST is supposed to set the default BUILD_DIR and OUTPUT location in a way that doesn't clash with separate builds where HOST is unset (=build). If HOST is set via config.mak, potentially-clashing defaults will be used.

I'm not sure how to fix this, or if it can be fixed, since there is an intent that config.mak can inspect the value of HOST (set via NATIVE) and possibly the values of BUILD_DIR and OUTPUT, and that it can override them.

Fixed by commit 5dd1a49567567c1eada595dbceff7672a1855792


CSV Download Endpoint

Description
Adds a new search endpoint to allow downloading a CSV of search results. This PR also simplifies the implementation & testing of the search endpoint by removing paths related to deprecated Document tables.
Type of change
Please select the option(s) below that are most relevant:

[ ] Bug fix
[x] New feature
[ ] Breaking change

How Has This Been Tested?
Tests added to search route validation.
Reviewer Checklist

[ ] The PR represents a single feature (small driveby fixes are also ok)
[ ] The PR includes tests that are sufficient for the level of risk
[ ] The code is sufficiently commented, particularly in hard-to-understand areas
[ ] Any required documentation updates have been made
[ ] Any TODOs added are captured in future tickets
[ ] No FIXMEs remain

Note: tests required non-overlapping document titles, so I slightly modified the test data loaded into the opensearch container (hence the changes to the json files).


[FLINK-18517][k8s][release-1.10] Bump fabric8 version from 4.5.2 to 4.9.2

What is the purpose of the change

Fix the issue FLINK-17416 that Flink on K8s could not work on java 8u252 in release-1.10 branch

Brief change log

Update version in pom.xml
Update the NOTICE file.
Update related tests since fabric8 kubernetes-client changed the behavior of Quantity#getAmount

Verifying this change

Existing unit tests
E2E tests

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@tillrohrmann I have updated the PR. Please have a look again.
BTW, i will create another hotfix PR for master and release-1.11 branch for correcting dependencies in Kubernetes pom and notice file.

@flinkbot run travis

@flinkbot run travis

@flinkbot run travis

@flinkbot run travis

cc @tillrohrmann The travis have given the green pass. And all the K8s related e2e tests run successfully.
BTW, I have created a dedicated ticket FLINK-18749 to remove the com.github.mifmif:generex:1.0.2 in master and release-1.11 branch.

Merging this PR now into the release-1.10 branch.

Merged via 183dfc30b4790a2ee02378170f62ea07ee26aab0


training error

D:\anaconda3\envs\TAPE\lib\site-packages\accelerate\accelerator.py:432: FutureWarning: Passing the following arguments to Accelerator is deprecated and will be removed in version 1.0 of Accelerate: dict_keys(['dispatch_batches', 'split_batches', 'even_batches', 'use_seedable_sampler']). Please pass an accelerate.DataLoaderConfiguration instead:
dataloader_config = DataLoaderConfiguration(dispatch_batches=None, split_batches=False, even_batches=True, use_seedable_sampler=True)
warnings.warn(
Traceback (most recent call last):
File "E:\PycharmProjects\TAPE-main\core\trainLM.py", line 24, in
run(cfg)
File "E:\PycharmProjects\TAPE-main\core\trainLM.py", line 12, in run
trainer.train()
File "E:\PycharmProjects\TAPE-main\core\utils.py", line 80, in wrapper
ret = func(*args, **kw)
File "E:\PycharmProjects\TAPE-main\core\LMs\lm_trainer.py", line 119, in train
self.trainer.train()
File "D:\anaconda3\envs\TAPE\lib\site-packages\transformers\trainer.py", line 1624, in train
return inner_training_loop(
File "D:\anaconda3\envs\TAPE\lib\site-packages\transformers\trainer.py", line 1653, in _inner_training_loop
train_dataloader = self.get_train_dataloader()
File "D:\anaconda3\envs\TAPE\lib\site-packages\transformers\trainer.py", line 852, in get_train_dataloader
return self.accelerator.prepare(DataLoader(train_dataset, **dataloader_params))
File "D:\anaconda3\envs\TAPE\lib\site-packages\torch\utils\data\dataloader.py", line 238, in init
assert prefetch_factor > 0
TypeError: '>' not supported between instances of 'NoneType' and 'int'

It appears to be a Python environment issue rather than a technical issue related to this project.


[SegmentGeneratorConfig Cleanup] Make PinotOutputFormat use table config and schema to create segments

Refactor PinotOutputFormat related classes to use table config and schema to create segments

This PR uses a SchemaBuilder.addTime method that I removed in https://github.com/apache/incubator-pinot/pull/5349 FYI


Differentiate between owned and watched accounts in drop down selector

When you watch an account eg 5Fer9CC593nS2JTsS4SFC3iWT7M2cwcVWqixjAQ9uPDKg8Jg all of the pure's and multisigs that the address is behind will also appear as options in the drop-down selector.
The issue here is that is confusing for a user to know which addresses belong to their own setup and which come from an account that is being watched.

It would be good to differentiate in the list which addresses are being watched from the addresses that are part of the user's own setup. Perhaps with an eye or telescope emoji.
Background:
"There's no way to know what multisig/pure proxy a user want to see.
I think the confusion could be lowered if we could show clearly that the reason an account is in the dropdown is because of a watched account? The only way I would find easy to understand would be with :eyes: emoji next to the identicon or something :)"
Originally posted by @Tbaut in https://github.com/ChainSafe/Multix/issues/161#issuecomment-1560182488

I think one cool way to have this and still be subtle would be to add after or before the batch, an eye outlines icon (inside the badge style still) HiOutlineEye from https://react-icons.github.io/react-icons/icons?name=hi2

ideally, and if that's working well, we could have a tooltip that would tell "watched account" or something. I'm not a fan of tooltips because it's not great for mobile, but it's insignificant enough for this one.


Create demo apps for users to test

Might be useful to have a couple of apps for users to view and test with.
I recently created https://github.com/emcniece/ZeroconfDemo which is a pure Cordova example. It would be nice to have an Ionic example as well.
The app should be able to demonstrate both watching and registering services.
ToDo:

Create app demo monorepo with platform-specific subdirectories
Add README build instructions within each platform directories
Reference troubleshooting instructions on becvert/cordova-plugin-zeroconf

I think an average developer should be able to understand and apply the instructions in the README. I don't think demos are necessary and for the least I don't want to add demos to this repo. This is stuff that need maintenance too... I want to keep it lightweight. Thanks

Ah, I should have added that to the initial comment - yes I agree that demos should not be part of this repo.
I'm happy to create an external repo and scaffold a few apps. Given how many users raise issues around basic usage of the plugin, having functional examples to point to seems like it would save us some support time.
You're correct, this introduces more maintenance, and I would like to play with a bit of CI for this new repo to help reduce overhead. I'm happy to maintain this outside of here.
@becvert would you accept a PR for adding some external repo links to the README?

Closing old issue. Feel free to reopen.


Zone Aware Routing - Mesh expansion and VM only enviornment

Evaluate whether Zone aware routing works for Mesh expansion and VM only enviornments.

@costinm : ^^

AFAIK it works - but needs testing.
@vilobhmm  - if you have some time, please check it, if it works we can document it in 0.8.
( code is using ServiceEntry labels to set the equivalent of the zone aware node annotations)


chore: refresh package lock

:tada: This PR is included in version 2.0.5 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Docs: How should you handle <title> for SEO?

Answer from Jake:

in the last I've populated <title> using a best guess from the url, then use js to set it properly later

Answer from me:

I think we've previously done not too different (default to site-wide <title>, later switch when can)

We verified this morning that presence of <title> in <head> followed by <title> later in <body> is not a workaround folks can rely on. That only works if there's no <title> defined in <head> previously. I think the idea of a best guess or default set using JS later is prolly a good answer.

I was thinking a little about this and was considering moving app shell to have a more API like response rather than just the HTML partial.
This way we could easily extract the HTML partial, Styles and extra info, like the page title, from a JSON response. Thoughts?

This should now be solved per 4cd96213292c579c2da5adad37baacdf7f6df53b if I understood correctly. Can has confirm/bug close if so? :)

Yup yup.
Static render now pulls in a unique title for first render - this will be what the crawl bot should see. In app shell the title is altered by title from the json api.


Implement remaining texture wrapping modes

This PR mostly implements the previously-unsupported wrapping modes: two
disequal wrapping modes in the S- and T-directions, and MIRROED_REPEAT for any
direction. Blender doesn't support these through the "Extension" property on the
Image Texture node so they are implemented by inserting nodes to transform the
texcoords before feeding them into the texture node.
The complete set of nodes that can feed into the Image Texture node now like
this (you can see the nodes are now positioned nicely too)

The wrapping mode frame splits the texcoord into its components, applies group
nodes that do the wrapping formulas, and then combines them again. The wrapping
formulas are

Two new groups were added to node_groups.json to handle these. The group for
REPEAT looks like

When you compute x mod 1 with a Modulo node, you get an output with the same
sign as x, so the Add and Less Than nodes are there to get a result in the range
[0, 1).
The group for MIRRORED_REPEAT looks like

The first frame computes x' = x mod 2 (with the same correction to get a number
in [0, 2)). The last frame lerps between x' and 2-x' using an interpolation that
is either 0 or 1 based on whether x' is less or greater than 1. AFAICT, there is
no pre-made node that does lerping for values (unlike RGBs and Shaders, which
have MixNodes).
There is no group for clamping (which is too bad because it would be the
simplest one ^^). Clamping is handled by just passing the coordinate on through
because we set the "Extension" property on the Image Texture node to do clamping
directly.
(And obviously if both directions use clamp or repeat, we forgo creating the
Wrapping Mode frame and just set the "Extension" property correctly.)
If you view the sample TextureSettingTest in the Rendered view, the wrapping
mode tests are now all correct

There are two problems with this approach.
The first is accidental and Blender-specific: you do have to look in the
Rendered view because Blender appears to always use repeat for the "Extension"
of Image Textures in the Material view. So textures that should use clamping
look wrong in the Material view. This could be (partially, see below) mitigated
by using a "useless" group to do clamping even when the Image Texture is set to
do clamping itself.
The second is essential and conceptual: the wrapping mode should properly
interact with filtering, and just changing the texture coordinates does not.
This means that small errors are possible when the wrapped coordinate is very
near the border of the texture because the samples used for filtering that "lie
just outside the border" are determined by the real wrapping mode.
Here is an example using linear filtering. Suppose we have a 2x1 texture. There
are two samples, a and b, which lie at respectively (1/3, 1/2), and (2/3, 1/2)
in the [0,1]x[0,1] texture space. If we have a texcoord of t = (-1/2, 1/2), then
if the wrapping mode were really CLAMP_TO_EDGE (in the S-direction), sampling
at t would give a. However, if the wrapping mode was really REPEAT and we only
emulated CLAMP_TO_EDGE by transforming t to t' = (0, 1/2), sampling there
would give (a+b)/2, not a, because the samples that are selected for filtering
are determined by the real wrapping mode, which thinks t' is half-way between a
at (1/3, 1/2) and b repeated at (-1/3, 1/2).
So if we emulate CLAMP_TO_EDGE on a texture that is really REPEAT, points near
the edge might be influenced by samples waaay on the other side of the texture.
There is a similar error if we emulate MIRRORED_REPEAT.
For a real mode of CLAMP_TO_EDGE, there are also errors but they are not as bad,
which is why this is how I chose to implement things.

Obviously emulating clamping if the real mode is CLAMP_TO_EDGE is perfect.
Emulating MIRRORED_REPEAT is also perfect, since the samples that lie just
outside the border are the same as those on the inside.
The error is in REPEAT, when a point near the border should be influenced by a
sample on the inside of the border and another near the border on the opposite
side of the image, but it is only influenced by the first of these ie. we
should have (a+b)/2 but we actually only have a, if we were to continue the
example above. This is in some sense less bad than having a point be
influenced by a sample it isn't supposed to be, because we can still think of
this as a RPEAT texture, it just basiclly uses NEAREST filtering for points
very close to the borders. Additionally, REPEAT textures are usually periodic,
so the first and last sample in a row (or column) are close together, so there
usually isn't much difference between a and (a+b)/2.

Which is all mostly just to register the fact that this implementation method
for wrapping is not perfect.
One more thing: Blender can't set the filtering in the s- and t-directions
independantly. This PR also selects the "best" of the two filters in the glTF to
use (previously I had just arbitrarily used the first) where LINEAR is better
than NEAREST. This is similar to cinghiale's idea to use the strongest of the two
magnifications for a camera's magnification.

The history looks weird for the same reason as #32.

About clipping not working in the Material view, see https://developer.blender.org/T53468.

@scurest I merged #31 and #32 now keeping the history (should not use the github interface which squashes history by default). While number #36 merges without conflict, this one has a conflict. I think, only line 564 moved for some strange reason and should be in line 310 instead. Can you check?
I would merge your other two PRs and release version 0.4. Then I'd hand over the repository to you as you run the show anyway. Okay with you?

@kson Thanks a lot! Yeah, this branch is a sibling to master now. Actually if you merge #36 you'll get the changes from this PR too and Github will probably mark this one as merged automatically. But if you want, how about this instead: I can close these two PRs and open a new PR for my current master. That has all the changes from these two plus some more like support for animating material properties and working CUBICSPLINE interpolation, and it won't have any conflicts so it should be an easy merge. You could do a 0.4 release after that. How's that sound?
If you don't want it anymore I can take it. I'm not sure how deployment or CI works though. If you want to keep it but just don't have time to review PRs you could make me a collaborator and I could push my own stuff and handle some of the issues for you. Honestly if you get my master branch merged the importer will be really close to being feature-complete so things will probably settle into maintenance mode soon. The biggest thing on the horizon is probably Blender's 2.8 release.

@scurest You should have received an invite as collaborator. Both solution would make sense for me, I just don't want to be the bottleneck nor earn the credits that belong to a larger part to you.
I think a new PR could make sense. Looking forward for the new functionality. Material animations sound great. Any good scenes to test those?

@ksons Cool, I got it, thanks! #40 is the new PR.
I don't know any examples in the wild. But you can now do things like animate the offset of a texture transform with a STEP animation to play a 2D animation on a quad. This file plays an explosion animation: https://www.filedropper.com/bomb_1 (hope that file host works). Put your 3D View in Rendered mode because Blender doesn't update the Material view when material animations play.

Sounds good. The Link to filedropper doesn't work for me.


Documentation for Debugging Process of Weird Station Bug

Just a place to write down the process of how this is being debugged so that it isn't lost to time.
@bergerkiller Feel free to comment on this :)
The base of this commit trail is fe1a77b

Step 1
Print the sign information and the action that triggered the execution.
Since there is only 1 sign that does this weird thing, the prints only happen to a specific sign.
https://github.com/bbayu123/TrainCarts/blob/972969915c28774310345ca222f87cea99ac7271/src/main/java/com/bergerkiller/bukkit/tc/signactions/SignActionStation.java#L38-L43

Current Observation
Since I limited it to only the affected sign, it appears to be printing GROUP_ENTER -> REDSTONE_CHANGE
[12:22:18] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[12:22:18] [Server thread/INFO]: GROUP_ENTER
[12:22:45] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[12:22:45] [Server thread/INFO]: REDSTONE_CHANGE

Related Logs
Trains have gone stuck now, related logs:
@bergerkiller Can you advice next step of debugging?
[14:13:35] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:13:35] [Server thread/INFO]: GROUP_ENTER
[14:14:01] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:14:01] [Server thread/INFO]: REDSTONE_CHANGE
[14:14:18] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:14:18] [Server thread/INFO]: GROUP_ENTER
[14:14:46] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:14:46] [Server thread/INFO]: REDSTONE_CHANGE
[14:15:02] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:15:02] [Server thread/INFO]: GROUP_ENTER
[14:15:13] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:15:13] [Server thread/INFO]: REDSTONE_CHANGE
[14:17:28] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:17:28] [Server thread/INFO]: GROUP_ENTER
[14:17:54] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:17:54] [Server thread/INFO]: REDSTONE_CHANGE
[14:18:02] [Server thread/INFO]: org.bukkit.craftbukkit.v1_17_R1.block.CraftSign@b4b986de
[14:18:02] [Server thread/INFO]: REDSTONE_CHANGE
[14:37:55] [Server thread/WARN]: [SSCM] Train LR101-2 has stopped moving! Please head to location (city, -416.15137, 65.0625, -1203.16049) to dislodge the train!
[14:39:55] [Server thread/WARN]: [SSCM] Train LR301-1 has stopped moving! Please head to location (city, -411.50568, 68.0625, -1304.26482) to dislodge the train!
[14:39:55] [Server thread/WARN]: [SSCM] Train LR102-2 has stopped moving! Please head to location (city, -496.51645, 65.02291, -1451.96183) to dislodge the train!
[14:39:55] [Server thread/WARN]: [SSCM] Train LR102-1 has stopped moving! Please head to location (city, -411.5, 66.53563, -1253.45448) to dislodge the train!

https://youtu.be/2ScIAsZYkDg This video indicates that the system is working as intended

Supplimentary images relating to the logs

Cause has been discovered:
If the train has a GroupActionWaitState, repowering the station will cause the train to re-centre onto the station


added "file"-attribute in JUnit testcase-tag

This can be used by platforms like CircleCI to parallelize tests automatically based on timing-data.

@ciaranmcnulty I used a Placeholder for the Directory Separator as discussed in the previous PR #1335 .
If you have a minute to spare, could you give it a review?
Thanks!

Let me fix the Scrutinizer tests first..

@ciaranmcnulty Scrutinizer is now ok.
Also fixed a too greedy preg_replace in FeatureContext::fileXmlShouldBeLike that ate up any attribute after the time="-IGNORE-VALUE-"-attribute.
$fileContent = preg_replace('/time="(.*)"/', 'time="-IGNORE-VALUE-"', $fileContent);

has become:
$fileContent = preg_replace('/time="(.*)"/U', 'time="-IGNORE-VALUE-"', $fileContent);

Should be good for review now.

@ciaranmcnulty Any idea how I can prevent the "rating" of the file JUnitFeatureElementListener.php from going down to a "B" in Scrutinizer..? It seems a bit ominuous without any explication :thinking:

@ciaranmcnulty Sorry for the late reply. I was held up by some other projects. I fixed the scrutinizer checks. Could you please take a look at the PR? Thanks!


Add patches to resolve CVE-2024-24786 in node-driver-registrar

Description of changes:
Fixes CVE-2024-24786
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm
/approve


Package examples with installation

I am open to not doing this, but it feels sort of nice to give such things to people.
On the other hand, they'll be down in some awkward place, and everyone can just copy the example code from here.

How about an example gallery like librosa's? Then the code is easy to browse and download

I believe the right emoji here is :+100000000:


Wip process sidecar memory

Note: This is a PR to test a change and how it will be handled in Travis CI.
We discussed in tech retro how testing failure cases that require a delayed job (Delayed::Worker.new) will make the test itself throw an error.
We want to see whether our tests can make it thru Travis without throwing an error on tests that are meant to show validation errors.
It is possible to disable delayed jobs for testing purposes. Set Delayed::Worker.delay_jobs = false to execute all jobs realtime.

Delayed::Worker.new.work_off
Thanks for contributing to cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:

An explanation of the use cases your change solves

Links to any other associated PRs

[ ] I have reviewed the contributing guide

[ ] I have viewed, signed, and submitted the Contributor License Agreement

[ ] I have made this pull request to the master branch

[ ] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

Closing this since the Travis CI testing is complete.
Also just as an FYI, since both of you have commit access you don't actually have to make a PR to test this. You can push directly to the branch and Travis will run against the commits. Just go to the commit log for the branch and click on the red Xs. Here's an example:


Doc links updated to new docs site

Issue
https://github.com/gravitee-io/issues/issues/9386
Description
Doc links updated to new docs site where relevant. Exceptions are when the links point to specific versions of the docs e.g. related to version migrations.

created a new one


Support for loading graph store data in lgraph (c++ end)

Open a graph store from path
Get graph schema from opened store.
Code reformat in lgraph
Persist graph schema info when creating and restoring backups.

Fixes #952

OK to merge if we are blocked by the helm test failure.

If possible, please address the issues raised by codefactor in the CI checks.

If possible, please address the issues raised by codefactor in the CI checks.

Oh okay, I thought it was because the ci task ran for a long time and failed because it timed out

If possible, please address the issues raised by codefactor in the CI checks.

CodeFactor issues fixed


FnRefs are a problem

I finally wrote a memory bug in subdoc and it was painful and i miss not having memory bugs.
The bug was using a fnref as an lvalue, which then is left with a dangling ref to a lambda. This is forbidden in the docs but I forgot. We need that clang-tidy to prevent it, or change FnRefs to heap alloc and be more like DynFnRef (like DynError) to do type-erasure to the heap.

This is resolved, as FnRefs are gone. We now have the concepts and type-erased DynFn which can be referenced or boxed.
Fixed by https://github.com/chromium/subspace/pull/356


Update-Module places modules in user path (even when running as Administrator)

Steps to reproduce
In an elevated powershell core window, choose a module from system path (not user path) and issue Update-Module for it:
PS C:\Users\Leandro> $env:PSModulePath
C:\Users\Leandro\Documents\PowerShell\Modules;C:\Program Files\PowerShell\Modules;c:\program files\windowspowershellcore\Modules;C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules
PS C:\Users\Leandro> Gci "C:\Program Files\PowerShell\Modules\Az.Automation"

    Directory: C:\Program Files\PowerShell\Modules\Az.Automation

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        17/02/2019    21:25                1.1.0
d-----        08/03/2019    22:55                1.1.1
d-----        06/04/2019    11:24                1.2.0

PS C:\Users\Leandro> update-module AZ.Automation -verbose
VERBOSE: Checking for updates for module 'Az.Automation'.
VERBOSE: Repository details, Name = 'PSGallery', Location = 'https://www.powershellgallery.com/api/v2/'; IsTrusted = 'True'; IsRegistered = 'True'.
VERBOSE: Using the provider 'PowerShellGet' for searching packages.
VERBOSE: Using the specified source names : 'PSGallery'.
VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2/' and PackageManagementProvider is 'NuGet'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='Az.Automation'' for ''.
VERBOSE: Total package yield:'1' for the specified package 'Az.Automation'.
VERBOSE: Performing the operation "Update-Module" on target "Version '1.2.0' of
module 'Az.Automation', updating to version '1.2.1'".
VERBOSE: The installation scope is specified to be 'CurrentUser'.
VERBOSE: The specified module will be installed in 'C:\Users\Leandro\Documents\PowerShell\Modules'.
VERBOSE: An update for the module 'Az.Automation' was found with version '1.2.1'.
VERBOSE: The specified Location is 'NuGet' and PackageManagementProvider is 'NuGet'.
VERBOSE: Downloading module 'Az.Automation' with version '1.2.1' from the repository 'https://www.powershellgallery.com/api/v2/'.
VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='Az.Automation'' for ''.
VERBOSE: Package 'Az.Accounts' is already installed.
VERBOSE: Package 'Az.Accounts' is already installed.
VERBOSE: InstallPackage' - name='Az.Automation', version='1.2.1',destination='C:\Users\Leandro\AppData\Local\Temp\1176232375'
VERBOSE: DownloadPackage' - name='Az.Automation', version='1.2.1',destination='C:\Users\Leandro\AppData\Local\Temp\1176232375\Az.Automation.1.2.1\Az.Automation.1.2.1.nupkg', uri='https://www.powershellgallery.com/api/v2/package/Az.Automation/1.2.1'
VERBOSE: Downloading 'https://www.powershellgallery.com/api/v2/package/Az.Automation/1.2.1'.
VERBOSE: Completed downloading 'https://www.powershellgallery.com/api/v2/package/Az.Automation/1.2.1'.
VERBOSE: Completed downloading 'Az.Automation'.
VERBOSE: InstallPackageLocal' - name='Az.Automation', version='1.2.1',destination='C:\Users\Leandro\AppData\Local\Temp\1176232375'
VERBOSE: Validating the 'Az.Automation' module contents under 'C:\Users\Leandro\AppData\Local\Temp\1176232375\Az.Automation.1.2.1' path.
VERBOSE: Test-ModuleManifest successfully validated the module manifest file 'C:\Users\Leandro\AppData\Local\Temp\1176232375\Az.Automation.1.2.1'.
VERBOSE: Validating the authenticode signature and publisher of the catalog file or module manifest file of the module 'Az.Automation'.
VERBOSE: Catalog file 'Az.Automation.cat' is not found in the contents of the module 'Az.Automation' being installed.
VERBOSE: For publisher validation, current module 'Az.Automation' with version '1.2.1' with publisher name '' from root certificate authority ''. Is this module signed by Microsoft: 'False'.
VERBOSE: For publisher validation, using the previously-installed module 'Az.Automation' with version '1.2.0' under 'C:\Program Files\PowerShell\Modules\Az.Automation\1.2.0' with publisher name '' from root certificate authority ''. Is this module signed by Microsoft: 'False'.
VERBOSE: Checking for possible command collisions for the module 'Az.Automation' commands.
VERBOSE: Module 'Az.Automation' was installed successfully to path 'C:\Users\Leandro\Documents\PowerShell\Modules\Az.Automation\1.2.1'.
PS C:\Users\Leandro> Gci "C:\Program Files\PowerShell\Modules\Az.Automation"

    Directory: C:\Program Files\PowerShell\Modules\Az.Automation

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        17/02/2019    21:25                1.1.0
d-----        08/03/2019    22:55                1.1.1
d-----        06/04/2019    11:24                1.2.0

PS C:\Users\Leandro> gci "C:\Users\Leandro\Documents\PowerShell\Modules\Az.Automation"

    Directory: C:\Users\Leandro\Documents\PowerShell\Modules\Az.Automation

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----        26/04/2019    22:30                1.2.1

PS C:\Users\Leandro>

Expected behavior
Module should be placed in the system path (in my example "C:\Program Files\PowerShell\Modules\Az.Automation")

Actual behavior
Module was placed in the user path (in my example "C:\Users\Leandro\Documents\PowerShell\Modules\Az.Automation"

Environment data

PS C:\Users\Leandro> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.2.0
PSEdition                      Core
GitCommitId                    6.2.0
OS                             Microsoft Windows 10.0.17763
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Install-Module -Name xxx -Scope CurrentUser
update-Module -Name xxx -Scope CurrentUser
see
https://docs.microsoft.com/en-us/powershell/module/powershellget/install-module?view=powershell-5.1

These modules were installed using -Scope AllUsers.
Update-Module doesn't expose an -Scope parameter:
PS C:\Users\Leandro> Get-Help Update-Module

NAME
    Update-Module

SYNTAX
    Update-Module [[-Name] <string[]>] [-RequiredVersion <string>]
    [-MaximumVersion <string>] [-Credential <pscredential>] [-Proxy <uri>]
    [-ProxyCredential <pscredential>] [-Force] [-AllowPrerelease]
    [-AcceptLicense] [-WhatIf] [-Confirm] [<CommonParameters>]

ALIASES
    upmo

REMARKS
    Get-Help cannot find the Help files for this cmdlet on this computer. It
    is displaying only partial help.
        -- To download and install Help files for the module that includes
    this cmdlet, use Update-Help.
        -- To view the Help topic for this cmdlet online, type: "Get-Help
    Update-Module -Online" or
           go to https://go.microsoft.com/fwlink/?LinkID=398576.

uninstall-module,then install-module -Scope CurrentUser

@chuanjiao it seems the goal here is to have update-module correctly work for modules in the system path. It doesn't look like @lwajswaj wants the module to be in the user-specific path.

Yes, exactly. I'm expecting modules to be updated in the system path
El sáb., 27 abr. 2019 11:23, vexx32<EMAIL_ADDRESS>escribió:

@chuanjiao https://github.com/chuanjiao it seems the goal here is to
have update-module correctly work for modules in the system path. It
doesn't look like @lwajswaj https://github.com/lwajswaj wants the
module to be in the user-specific path.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PowerShell/PowerShell/issues/9482#issuecomment-487290095,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABREDHHIZMZ3O2FGLGLGBO3PSROVLANCNFSM4HI3FNTQ
.

@lwajswaj You should move your issue to PowerShellGet repository instead.
The behavior is located here  :  Get-InstallationScope.ps1#L2

Determine scope. We prefer CurrentUser scope even if the older module is installed for AllUsers, unless:
old module is installed for all users, we are elevated, AND using Windows PowerShell
This is to mirror newer behavior of Install-Module.

OK, the issue with this preference is it doesn't play well when module is required at system level such as modules needed to be executed by SYSTEM or a Service Account (like the case of an Azure DevOps hosted agent).


feat/cluster-name-and-version-gitops

Add cluster name to avoid name collision on AWS.
Add version-gitops to clone specific branch when clone gitops repo.

closed in favor of #82


Optimize docker shared volume bindings

Look into improving docker performance using the new cached property (https://docs.docker.com/docker-for-mac/osxfs-caching/).

Fixed in https://github.com/Frojd/Wagtail-Pipit/commit/1213f987ea9d39063f5846844da1aadabd00d3f7


Update REST API to latest OT-BR-POSIX (TZ-217)

In the latest release the webui and REST API was added to the ESP-OTBR, but not all of the components are added to this API. Would it be possible to update the API with the latest upstream from OTBR?
https://github.com/openthread/ot-br-posix/pulls?q=is%3Apr+rest+is%3Aclosed+author%3Aagners

@FutureCow Thanks for reporting, we will check and add the missing APIs.

Updating to the latest REST API will enable adding and ESP thread border router to Home Assistant; see this discussion for details https://community.home-assistant.io/t/openthread-border-router-support/540715/33

I've done some exploratory research on this, and it appears that the missing APIs in the discussion https://community.home-assistant.io/t/openthread-border-router-support/540715/33 are not the cause for the Home Assistant rejection. The key API mentioned in that thread is /node/dataset/active which is the same endpoint as /node/active-dataset-tlvs which according to this post https://community.home-assistant.io/t/openthread-border-router-support/540715/16 the /node/dataset/active was changed to /node/active-dataset-tlvs. Just for fun I copied the route from /node/active-dataset-tlvs to /node/dataset/active but Home Assistant still did not find the Open Thread Border Router.
Are there any other endpoints that are not implemented that Home Assistant is looking for?

In fact, in the latest ot-br-posix REST API, /node/active-dataset-tlvs has been replaced by /node/dataset/active. This is the related pull request: https://github.com/openthread/ot-br-posix/pull/1682
It is normal for the current ESP Thread Border Router to not recognize /node/dataset/active because we are still using the old URL /node/active-dataset-tlvs. We are actively updating our esp-thread-br codes to be consistent with ot-br-posix.
If you change /node/active-dataset-tlvs in esp_br_web_base.h to /node/dataset/active, and use this URL in the browser, then you should be able to get the following data (unless BR does not has an active dataset).

However, if you only change the URL definition in esp_br_web_base.h, then data that BR actually returns is active dataset tlvs. It just a test for getting more useful information.

If you want to have a look at the information exchanged between Home Assistant and ot-br-posix, best would probably be to connect over http, and have a look at the traffic using Wireshark or tcpdump.
Alternatively, you can use ncat as a logging proxy.

If you want to have a look at the information exchanged between Home Assistant and ot-br-posix, best would probably be to connect over http, and have a look at the traffic using Wireshark or tcpdump.
Alternatively, you can use ncat as a logging proxy.

Awesome thanks for the stackoverflow. I was able to get tcpflow to work properly sudo tcpflow -p -i wlan0 -c port 8081 > ~/posix-logs
I got the following:
Host: <IP_ADDRESS>:8081
User-Agent: HomeAssistant/2023.10.5 aiohttp/3.8.5 Python/3.11
Accept: text/plain
Accept-Encoding: gzip, deflate

<IP_ADDRESS>.08081-<IP_ADDRESS>.52054: HTTP/1.1 200 OK
Access-Control-Allow-Headers: Access-Control-Allow-Headers, Origin,Accept, X-Requested-With, Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers
Access-Control-Allow-Methods: DELETE, GET, OPTIONS, PUT
Access-Control-Allow-Origin: *
Connection: close
Content-Type: text/plain
Content-Length: 210

0E08000000000001000035060004001FFFE00708FDC91BB75D18F9AB0C0402A0F7F8051000112233445566778899AABBCCDDEEFF030E4F70656E54687265616444656D6F0410445F2B5CA6F2A93A55CE570A70EFEECB000300000F0208111111112222222201021234
<IP_ADDRESS>.52070-<IP_ADDRESS>.08081: GET /node/ba-id HTTP/1.1
Host: <IP_ADDRESS>:8081
User-Agent: HomeAssistant/2023.10.5 aiohttp/3.8.5 Python/3.11
Accept: */*
Accept-Encoding: gzip, deflate

<IP_ADDRESS>.08081-<IP_ADDRESS>.52070: HTTP/1.1 200 OK
Access-Control-Allow-Headers: Access-Control-Allow-Headers, Origin,Accept, X-Requested-With, Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers
Access-Control-Allow-Methods: DELETE, GET, OPTIONS, PUT
Access-Control-Allow-Origin: *
Connection: close
Content-Type: application/json
Content-Length: 34

"C2C745CB342E150B5C251048237562BA"
<IP_ADDRESS>.52084-<IP_ADDRESS>.08081: GET /node/dataset/active HTTP/1.1
Host: <IP_ADDRESS>:8081
User-Agent: HomeAssistant/2023.10.5 aiohttp/3.8.5 Python/3.11
Accept: text/plain
Accept-Encoding: gzip, deflate

<IP_ADDRESS>.08081-<IP_ADDRESS>.52084: HTTP/1.1 200 OK
Access-Control-Allow-Headers: Access-Control-Allow-Headers, Origin,Accept, X-Requested-With, Content-Type, Access-Control-Request-Method, Access-Control-Request-Headers
Access-Control-Allow-Methods: DELETE, GET, OPTIONS, PUT
Access-Control-Allow-Origin: *
Connection: close
Content-Type: text/plain
Content-Length: 210

0E08000000000001000035060004001FFFE00708FDC91BB75D18F9AB0C0402A0F7F8051000112233445566778899AABBCCDDEEFF030E4F70656E54687265616444656D6F0410445F2B5CA6F2A93A55CE570A70EFEECB000300000F0208111111112222222201021234

I'll keep digging, but it does look like the /node/ba-id is what I'm currently missing.

Finally! While I've had to hack and hardcode the string currently, because I'm not great at C I got the thread border router added to homeassistant.
The key is that the /node/dataset/active needs to be in plain/text and there cannot be any quotes. Just using the existing active dataset tlvs runs it through JSON which adds quotes at the beginning of the string, and the current implementation only returns JSON.

@FutureCow @laptopfreek0 The active/pending dataset REST APIs have been added in this commit: https://github.com/espressif/esp-thread-br/commit/0b08a3a37c1868b9b4d1d782074c35ef8f9154c0.
The current supported REST APIs are listed here: https://docs.espressif.com/projects/esp-thread-br/en/latest/codelab/web-gui.html#thread-rest-apis
Thanks for your support, let us know if any further question or issues.


Ignore potential PermissionErrors on Windows while packing, in case of both loose and packed objects

In this line:
https://github.com/giovannipizzi/disk-objectstore/blob/4d493174c1354603b21ed8d623f487660a050d24/disk_objectstore/container.py#L897
I should probably put a guard for PermissionErrors if the file is being used, and ignore on Windows (it's ok to leave back some loose objects, they won't be used anymore since they are packed - and at some point they will be closed by the original process, and the next packing will clean those up).

In order to avoid concurrency issues, I will stop deleting objects right away, and move the deletion of leftover loose objects in a maintenance operation (see comments in #37 and #43)


Remote terminal error: Command $setUnicodeVersion not found

  ERR IPC Command $setUnicodeVersion not found: Error: IPC Command $setUnicodeVersion not found
    at RemoteTerminalChannel.call (/home/jeanpierre/gitrepos/vscode/out/vs/server/remoteTerminalChannel.js:96:19)
    at ChannelServer.onPromise (/home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/common/ipc.js:259:35)
    at ChannelServer.onRawMessage (/home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/common/ipc.js:232:33)
    at /home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/common/ipc.js:177:73
    at Emitter.fire (/home/jeanpierre/gitrepos/vscode/out/vs/base/common/event.js:435:38)
    at BufferedEmitter.fire (/home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/common/ipc.net.js:380:35)
    at PersistentProtocol._receiveMessage (/home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/common/ipc.net.js:659:41)
    at /home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/common/ipc.net.js:515:83
    at Emitter.fire (/home/jeanpierre/gitrepos/vscode/out/vs/base/common/event.js:435:38)
    at ProtocolReader.acceptChunk (/home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/common/ipc.net.js:194:37)
    at /home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/common/ipc.net.js:163:61
    at Emitter.fire (/home/jeanpierre/gitrepos/vscode/out/vs/base/common/event.js:435:38)
    at /home/jeanpierre/gitrepos/vscode/out/vs/base/parts/ipc/node/ipc.net.js:423:42
    at afterWrite (internal/streams/writable.js:466:5)
    at onwrite (internal/streams/writable.js:446:7)
    at InflateRaw.afterTransform (internal/streams/transform.js:103:3)
    at Zlib.processCallback (zlib.js:586:8)

Created PR #136171 fixing this


npm package contains wrong chrome binary for Linux ARM (Raspberry Pi 3, Raspbian)

For Linux ARM, the npm package contains a wrong chrome binary.
Tell us about your environment:

Puppeteer version: 1.1.1
Platform / OS version: Raspberry Pi 3 / Raspbian Stretch, fully updated as of 2018-02-28
Node.js version: v8.9.4

What steps will reproduce the problem?
$ npm i --save puppeteer
$ ./node_modules/puppeteer/.local-chromium/linux-536395/chrome-linux/chrome
-bash: ./node_modules/puppeteer/.local-chromium/linux-536395/chrome-linux/chrome: cannot execute binary file: Exec format error
$ file ./node_modules/puppeteer/.local-chromium/linux-536395/chrome-linux/chrome
./node_modules/puppeteer/.local-chromium/linux-536395/chrome-linux/chrome: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, not stripped

mark,the same

I had a similar problem about a month ago. Check the comments toward the bottom of issue #550 for a workaround.

You cant use the chromium built library from puppeteer on PI.  You need to update your built in chromium on the PI and use that one in your code.  See @scissorsneedfoodtoo's comment above.
For builds on ARM they should disable building of the chromium by default since it does not work or fix it so it will run.  Confuses many people it seems.

@Austinb any step-by-step way to fix this?

See #550

Dupe of #550.


Allow to edit custom set of rows

Current situation
User needs to select either from selecting a custom set of rows by writing a custom SELECT statement or to edit first x rows returned by the database on a built-in basic SELECT query. User is not able to edit the rows returned by the custom SELECT statement.
Working with Microsoft SQL Management Studio as well as with SQL Operations Studio is quite uncomfortable when I want to patch the data in the database manually. On the other hand, I found doing the same in MySQL Workbench as much more satisfying.
Inspiration
MySQL Workbench has a single view which combines both running custom queries as well as updating values in rows returned by the custom queries. It also allows to see and copy the queries it is about to use to save the changes into the database.
Proposal
Combine the SELECT/SQL and EDIT views so that the user can edit results of selects as long as it is makes sense (the engine can track where and how to put the updated value to the database).
I also like that I can copy the UPDATE SQL queries generated by the MySQL Workbench and use them elsewhere (for example, add them to a migration script).

This would be extremely useful!

Probably a duplicate of #302 though


Parse an xml string in the spark data frame

Hi Everyone,
I have a json message which contains an xml column.
How ever with using the xml reader alone i will be only able to read the xml column alone. This strips the other columns other than the xml message. Is there is any solution to this problem.
ex : source date
+----+---------+-------------------------------------------------------+
|  id|accountid|                                                xmldata|
+----+---------+-------------------------------------------------------+
|1001|    12346|<AccountSetup xmlns:xsi="test"><Customers test="test...|
|1002|    12346|<AccountSetup xmlns:xsi="test"><Customers test="test...|
|1003|    12346|<AccountSetup xmlns:xsi="test"><Customers test="test...|
|1004|    12347|<AccountSetup xmlns:xsi="test"><Customers test="test...|
+----+---------+-------------------------------------------------------+

the target data needs to be somethinglike this
  +----------+--------------------+--------------------+--------------+--------------------+-------+....
| id  |accountId |   AcctNbr|         AddlParties|           Addresses|ApplicationInd|       Beneficiaries|ClassCd|....
    +----------+--------------------+--------------------+--------------+--------------------+-------+....
 |1000 |12346  |AAAAAAAAAA|[[Securities Amer...|[WrappedArray([D,...|             T|[WrappedArray([11...|     35|....
    +----------+--------------------+--------------------+--------------+--------------------+-------+....

Have you tried https://github.com/databricks/spark-xml#parsing-nested-xml ?

Thanks srowen. I am able to parse the record.

I've a similar use case where I need to parse nested XML. I've discovered that the function schema_of_xml drops the first node of the XML string.
Is there any particular reason to this ?

You'd have to provide an example?


Quiz bot captcha

hello friends, can someone explain to me how I make a quiz using this library?

the captcha quiz will be activated as soon as a user joins the group
I want to kind of make a capctha, just like the print. Thank you very much in advance.

I don't think that the issue section is the right place for that.
Please try the support group in Telegram: https://t.me/PHP_Telegram_Bot_Support
Maybe someone else can help you there.

Okay, thank you.