FAILED: lib/libLLVMDemangle.so.14git

Hi everyone,
I could not build the project. I got a failure in linking lib/libLLVMDemangle.so.14git.  the llvm-project from (iree/third_party/llvm-project is checkout out to the commit b88f4f271bb3e18b0676f1a21caa2450fc0eeb88 as it is pointed in https://github.com/google/iree-llvm-sandbox/blob/main/pinned-llvm-version):
-- The C compiler identification is Clang 12.0.0
-- The CXX compiler identification is Clang 12.0.0
-- The ASM compiler identification is Clang
-- Found assembler: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/llvm-12.0.0-ovrjxofhcx5djzzqhhl6flbldnpispvm/bin/clang
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/llvm-12.0.0-ovrjxofhcx5djzzqhhl6flbldnpispvm/bin/clang - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/llvm-12.0.0-ovrjxofhcx5djzzqhhl6flbldnpispvm/bin/clang++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- clang project is enabled
-- clang-tools-extra project is enabled
-- compiler-rt project is disabled
-- cross-project-tests project is disabled
-- libc project is disabled
-- libclc project is disabled
-- libcxx project is disabled
-- libcxxabi project is disabled
-- libunwind project is disabled
-- lld project is disabled
-- lldb project is disabled
-- mlir project is enabled
-- openmp project is disabled
-- polly project is disabled
-- pstl project is disabled
-- flang project is disabled
-- iree_dialects project is enabled
-- sandbox project is enabled
-- Performing Test LLVM_LIBSTDCXX_MIN
-- Performing Test LLVM_LIBSTDCXX_MIN - Success
-- Performing Test LLVM_LIBSTDCXX_SOFT_ERROR
-- Performing Test LLVM_LIBSTDCXX_SOFT_ERROR - Success
-- Looking for dlfcn.h
-- Looking for dlfcn.h - found
-- Looking for errno.h
-- Looking for errno.h - found
-- Looking for fcntl.h
-- Looking for fcntl.h - found
-- Looking for link.h
-- Looking for link.h - found
-- Looking for malloc/malloc.h
-- Looking for malloc/malloc.h - not found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for signal.h
-- Looking for signal.h - found
-- Looking for sys/ioctl.h
-- Looking for sys/ioctl.h - found
-- Looking for sys/mman.h
-- Looking for sys/mman.h - found
-- Looking for sys/param.h
-- Looking for sys/param.h - found
-- Looking for sys/resource.h
-- Looking for sys/resource.h - found
-- Looking for sys/stat.h
-- Looking for sys/stat.h - found
-- Looking for sys/time.h
-- Looking for sys/time.h - found
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for sysexits.h
-- Looking for sysexits.h - found
-- Looking for termios.h
-- Looking for termios.h - found
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Looking for valgrind/valgrind.h
-- Looking for valgrind/valgrind.h - found
-- Looking for fenv.h
-- Looking for fenv.h - found
-- Looking for FE_ALL_EXCEPT
-- Looking for FE_ALL_EXCEPT - found
-- Looking for FE_INEXACT
-- Looking for FE_INEXACT - found
-- Looking for mach/mach.h
-- Looking for mach/mach.h - not found
-- Looking for histedit.h
-- Looking for histedit.h - not found
-- Looking for CrashReporterClient.h
-- Looking for CrashReporterClient.h - not found
-- Looking for linux/magic.h
-- Looking for linux/magic.h - found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Looking for pthread_getspecific in pthread
-- Looking for pthread_getspecific in pthread - found
-- Looking for pthread_rwlock_init in pthread
-- Looking for pthread_rwlock_init in pthread - found
-- Looking for pthread_mutex_lock in pthread
-- Looking for pthread_mutex_lock in pthread - found
-- Looking for dlopen in dl
-- Looking for dlopen in dl - found
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Looking for pfm_initialize in pfm
-- Looking for pfm_initialize in pfm - not found
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found ZLIB: /usr/lib64/libz.so (found version "1.2.7")
-- Looking for compress2
-- Looking for compress2 - found
-- Found LibXml2: /usr/lib64/libxml2.so (found version "2.9.1")
-- Looking for xmlReadMemory
-- Looking for xmlReadMemory - found
-- Performing Test Terminfo_LINKABLE
-- Performing Test Terminfo_LINKABLE - Success
-- Found Terminfo: /usr/lib64/libtinfo.so
-- Looking for xar_open in xar
-- Looking for xar_open in xar - not found
-- Looking for arc4random
-- Looking for arc4random - not found
-- Looking for backtrace
-- Looking for backtrace - found
-- backtrace facility detected in default set of libraries
-- Found Backtrace: /usr/include
-- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW
-- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - Success
-- Looking for __register_frame
-- Looking for __register_frame - found
-- Looking for __deregister_frame
-- Looking for __deregister_frame - found
-- Looking for __unw_add_dynamic_fde
-- Looking for __unw_add_dynamic_fde - not found
-- Looking for _Unwind_Backtrace
-- Looking for _Unwind_Backtrace - found
-- Looking for getpagesize
-- Looking for getpagesize - found
-- Looking for sysconf
-- Looking for sysconf - found
-- Looking for getrusage
-- Looking for getrusage - found
-- Looking for setrlimit
-- Looking for setrlimit - found
-- Looking for isatty
-- Looking for isatty - found
-- Looking for futimens
-- Looking for futimens - found
-- Looking for futimes
-- Looking for futimes - found
-- Looking for posix_fallocate
-- Looking for posix_fallocate - found
-- Looking for sigaltstack
-- Looking for sigaltstack - found
-- Looking for lseek64
-- Looking for lseek64 - found
-- Looking for mallctl
-- Looking for mallctl - not found
-- Looking for mallinfo
-- Looking for mallinfo - found
-- Looking for mallinfo2
-- Looking for mallinfo2 - not found
-- Looking for malloc_zone_statistics
-- Looking for malloc_zone_statistics - not found
-- Looking for getrlimit
-- Looking for getrlimit - found
-- Looking for posix_spawn
-- Looking for posix_spawn - found
-- Looking for pread
-- Looking for pread - found
-- Looking for sbrk
-- Looking for sbrk - found
-- Looking for strerror
-- Looking for strerror - found
-- Looking for strerror_r
-- Looking for strerror_r - found
-- Looking for strerror_s
-- Looking for strerror_s - not found
-- Looking for setenv
-- Looking for setenv - found
-- Looking for dlopen
-- Looking for dlopen - found
-- Looking for dladdr
-- Looking for dladdr - not found
-- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC_TV_NSEC
-- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC_TV_NSEC - Failed
-- Performing Test HAVE_STRUCT_STAT_ST_MTIM_TV_NSEC
-- Performing Test HAVE_STRUCT_STAT_ST_MTIM_TV_NSEC - Success
-- Looking for __GLIBC__
-- Looking for __GLIBC__ - found
-- Looking for pthread_getname_np
-- Looking for pthread_getname_np - found
-- Looking for pthread_setname_np
-- Looking for pthread_setname_np - found
-- Looking for proc_pid_rusage
-- Looking for proc_pid_rusage - not found
-- Performing Test HAVE_STD_IS_TRIVIALLY_COPYABLE
-- Performing Test HAVE_STD_IS_TRIVIALLY_COPYABLE - Success
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success
-- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
-- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB - Success
-- Performing Test LLVM_HAS_ATOMICS
-- Performing Test LLVM_HAS_ATOMICS - Success
-- Performing Test SUPPORTS_VARIADIC_MACROS_FLAG
-- Performing Test SUPPORTS_VARIADIC_MACROS_FLAG - Success
-- Performing Test SUPPORTS_GNU_ZERO_VARIADIC_MACRO_ARGUMENTS_FLAG
-- Performing Test SUPPORTS_GNU_ZERO_VARIADIC_MACRO_ARGUMENTS_FLAG - Success
-- Native target architecture is X86
-- Threads enabled.
-- Doxygen disabled.
-- Go bindings disabled.
-- Ninja version: 1.10.2.git
-- Found OCaml: /usr/bin/ocamlfind
-- OCaml bindings disabled, need ctypes >=0.4.
-- Found Python module pygments
-- Found Python module pygments.lexers.c_cpp
-- Found Python module yaml
-- LLVM host triple: x86_64-unknown-linux-gnu
-- LLVM default target triple: x86_64-unknown-linux-gnu
-- Performing Test C_SUPPORTS_FPIC
-- Performing Test C_SUPPORTS_FPIC - Success
-- Performing Test CXX_SUPPORTS_FPIC
-- Performing Test CXX_SUPPORTS_FPIC - Success
-- Building with -fPIC
-- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG
-- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG - Success
-- Performing Test C_SUPPORTS_WERROR_DATE_TIME
-- Performing Test C_SUPPORTS_WERROR_DATE_TIME - Success
-- Performing Test CXX_SUPPORTS_WERROR_DATE_TIME
-- Performing Test CXX_SUPPORTS_WERROR_DATE_TIME - Success
-- Performing Test CXX_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW
-- Performing Test CXX_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - Success
-- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG
-- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG - Success
-- Performing Test C_SUPPORTS_CXX98_COMPAT_EXTRA_SEMI_FLAG
-- Performing Test C_SUPPORTS_CXX98_COMPAT_EXTRA_SEMI_FLAG - Success
-- Performing Test CXX_SUPPORTS_CXX98_COMPAT_EXTRA_SEMI_FLAG
-- Performing Test CXX_SUPPORTS_CXX98_COMPAT_EXTRA_SEMI_FLAG - Success
-- Performing Test C_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG
-- Performing Test C_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG - Success
-- Performing Test CXX_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG
-- Performing Test CXX_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG - Success
-- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
-- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Success
-- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
-- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Success
-- Performing Test CXX_SUPPORTS_CLASS_MEMACCESS_FLAG
-- Performing Test CXX_SUPPORTS_CLASS_MEMACCESS_FLAG - Failed
-- Performing Test CXX_SUPPORTS_NOEXCEPT_TYPE_FLAG
-- Performing Test CXX_SUPPORTS_NOEXCEPT_TYPE_FLAG - Success
-- Performing Test CXX_WONT_WARN_ON_FINAL_NONVIRTUALDTOR
-- Performing Test CXX_WONT_WARN_ON_FINAL_NONVIRTUALDTOR - Success
-- Performing Test CXX_SUPPORTS_SUGGEST_OVERRIDE_FLAG
-- Performing Test CXX_SUPPORTS_SUGGEST_OVERRIDE_FLAG - Success
-- Performing Test CXX_WSUGGEST_OVERRIDE_ALLOWS_ONLY_FINAL
-- Performing Test CXX_WSUGGEST_OVERRIDE_ALLOWS_ONLY_FINAL - Success
-- Performing Test C_WCOMMENT_ALLOWS_LINE_WRAP
-- Performing Test C_WCOMMENT_ALLOWS_LINE_WRAP - Success
-- Performing Test C_SUPPORTS_STRING_CONVERSION_FLAG
-- Performing Test C_SUPPORTS_STRING_CONVERSION_FLAG - Success
-- Performing Test CXX_SUPPORTS_STRING_CONVERSION_FLAG
-- Performing Test CXX_SUPPORTS_STRING_CONVERSION_FLAG - Success
-- Performing Test C_SUPPORTS_MISLEADING_INDENTATION_FLAG
-- Performing Test C_SUPPORTS_MISLEADING_INDENTATION_FLAG - Success
-- Performing Test CXX_SUPPORTS_MISLEADING_INDENTATION_FLAG
-- Performing Test CXX_SUPPORTS_MISLEADING_INDENTATION_FLAG - Success
-- Performing Test LINKER_SUPPORTS_COLOR_DIAGNOSTICS
-- Performing Test LINKER_SUPPORTS_COLOR_DIAGNOSTICS - Failed
-- Performing Test C_SUPPORTS_FNO_FUNCTION_SECTIONS
-- Performing Test C_SUPPORTS_FNO_FUNCTION_SECTIONS - Success
-- Performing Test C_SUPPORTS_FFUNCTION_SECTIONS
-- Performing Test C_SUPPORTS_FFUNCTION_SECTIONS - Success
-- Performing Test CXX_SUPPORTS_FFUNCTION_SECTIONS
-- Performing Test CXX_SUPPORTS_FFUNCTION_SECTIONS - Success
-- Performing Test C_SUPPORTS_FDATA_SECTIONS
-- Performing Test C_SUPPORTS_FDATA_SECTIONS - Success
-- Performing Test CXX_SUPPORTS_FDATA_SECTIONS
-- Performing Test CXX_SUPPORTS_FDATA_SECTIONS - Success
-- Looking for os_signpost_interval_begin
-- Looking for os_signpost_interval_begin - not found
-- Found Python3: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/python-3.8.10-7f7fkeh4425fbs77caqo5hrxvkf4nuyw/bin/python3 (found suitable version "3.8.10", minimum required is "3.6") found components: Interpreter
-- Failed to get errc messages
-- Linker detection: GNU ld
-- Performing Test HAS_WERROR_GLOBAL_CTORS
-- Performing Test HAS_WERROR_GLOBAL_CTORS - Success
-- Performing Test LLVM_HAS_NOGLOBAL_CTOR_MUTEX
-- Performing Test LLVM_HAS_NOGLOBAL_CTOR_MUTEX - Success
-- Found Git: /usr/local/bin/git (found version "2.14.2")
-- Targeting X86
-- Looking for sys/resource.h
-- Looking for sys/resource.h - found
-- Clang version: 14.0.0
-- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG
-- Performing Test CXX_SUPPORTS_NO_NESTED_ANON_TYPES_FLAG - Success
-- Looking for include file sys/inotify.h
-- Looking for include file sys/inotify.h - found
-- Not building amdgpu-arch: hsa-runtime64 not found
-- Performing Test C_SUPPORTS_WERROR_IMPLICIT_FUNCTION_DECLARATION
-- Performing Test C_SUPPORTS_WERROR_IMPLICIT_FUNCTION_DECLARATION - Success
-- Performing Test C_SUPPORTS_WERROR_MISMATCHED_TAGS
-- Performing Test C_SUPPORTS_WERROR_MISMATCHED_TAGS - Success
-- Found Python3: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/python-3.8.10-7f7fkeh4425fbs77caqo5hrxvkf4nuyw/bin/python3 (found suitable version "3.8.10", minimum required is "3.6") found components: Interpreter Development.Module NumPy
-- Found python include dirs: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/python-3.8.10-7f7fkeh4425fbs77caqo5hrxvkf4nuyw/include/python3.8
-- Found python libraries:
-- Found numpy v1.21.0: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/py-numpy-1.21.0-yvzzz7obyoi23lozfv6vfv2xlg3qua4o/lib/python3.8/site-packages/numpy/core/include
-- Checking for pybind11 in python path...
-- found (/stck/moessadk/.local/lib/python3.8/site-packages/pybind11/share/cmake/pybind11)
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Failed
-- Performing Test HAS_FLTO_THIN
-- Performing Test HAS_FLTO_THIN - Failed
-- Found pybind11: /stck/moessadk/.local/lib/python3.8/site-packages/pybind11/include (found version "2.9.0")
-- Found pybind11 v2.9.0: /stck/moessadk/.local/lib/python3.8/site-packages/pybind11/include
-- Python prefix = '', suffix = '', extension = '.cpython-38-x86_64-linux-gnu.so
-- Performing Test C_SUPPORTS_WERROR_GLOBAL_CONSTRUCTOR
-- Performing Test C_SUPPORTS_WERROR_GLOBAL_CONSTRUCTOR - Success
-- Performing Test CXX_SUPPORTS_WERROR_GLOBAL_CONSTRUCTOR
-- Performing Test CXX_SUPPORTS_WERROR_GLOBAL_CONSTRUCTOR - Success
-- Building iree-dialects project at /stck/moessadk/Workspace/MLIR/iree/iree/llvm-external-projects/iree-dialects (into /stck/moessadk/Workspace/MLIR/iree/iree-llvm-sandbox/build/tools/iree_dialects)
-- Found python include dirs: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/python-3.8.10-7f7fkeh4425fbs77caqo5hrxvkf4nuyw/include/python3.8
-- Found python libraries:
-- Found numpy v1.21.0: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/py-numpy-1.21.0-yvzzz7obyoi23lozfv6vfv2xlg3qua4o/lib/python3.8/site-packages/numpy/core/include
-- Checking for pybind11 in python path...
-- found (/stck/moessadk/.local/lib/python3.8/site-packages/pybind11/share/cmake/pybind11)
-- Found pybind11: /stck/moessadk/.local/lib/python3.8/site-packages/pybind11/include (found version "2.9.0")
-- Found pybind11 v2.9.0: /stck/moessadk/.local/lib/python3.8/site-packages/pybind11/include
-- Python prefix = '', suffix = '', extension = '.cpython-38-x86_64-linux-gnu.so
-- iree_llvm_sandbox build directory: /stck/moessadk/Workspace/MLIR/iree/iree-llvm-sandbox/build/tools/sandbox
-- Enabling iree-dialects in sandbox
-- Found python include dirs: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/python-3.8.10-7f7fkeh4425fbs77caqo5hrxvkf4nuyw/include/python3.8
-- Found python libraries:
-- Found numpy v1.21.0: /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/py-numpy-1.21.0-yvzzz7obyoi23lozfv6vfv2xlg3qua4o/lib/python3.8/site-packages/numpy/core/include
-- Checking for pybind11 in python path...
-- found (/stck/moessadk/.local/lib/python3.8/site-packages/pybind11/share/cmake/pybind11)
-- Found pybind11: /stck/moessadk/.local/lib/python3.8/site-packages/pybind11/include (found version "2.9.0")
-- Found pybind11 v2.9.0: /stck/moessadk/.local/lib/python3.8/site-packages/pybind11/include
-- Python prefix = '', suffix = '', extension = '.cpython-38-x86_64-linux-gnu.so
-- Registering Bye as a pass plugin (static build: OFF)
-- LLVM FileCheck Found: /home/moessadk/Workspace/MLIR/llvm-project/build_spiro/bin/FileCheck
-- git version: v0.0.0 normalized to 0.0.0
-- Version: 1.6.0
-- Looking for shm_open in rt
-- Looking for shm_open in rt - found
-- Performing Test HAVE_CXX_FLAG_STD_CXX11
-- Performing Test HAVE_CXX_FLAG_STD_CXX11 - Success
-- Performing Test HAVE_CXX_FLAG_WALL
-- Performing Test HAVE_CXX_FLAG_WALL - Success
-- Performing Test HAVE_CXX_FLAG_WEXTRA
-- Performing Test HAVE_CXX_FLAG_WEXTRA - Success
-- Performing Test HAVE_CXX_FLAG_WSHADOW
-- Performing Test HAVE_CXX_FLAG_WSHADOW - Success
-- Performing Test HAVE_CXX_FLAG_WSUGGEST_OVERRIDE
-- Performing Test HAVE_CXX_FLAG_WSUGGEST_OVERRIDE - Success
-- Performing Test HAVE_CXX_FLAG_PEDANTIC
-- Performing Test HAVE_CXX_FLAG_PEDANTIC - Success
-- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS
-- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS - Success
-- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32
-- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32 - Success
-- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING
-- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING - Success
-- Performing Test HAVE_CXX_FLAG_WNO_DEPRECATED_DECLARATIONS
-- Performing Test HAVE_CXX_FLAG_WNO_DEPRECATED_DECLARATIONS - Success
-- Performing Test HAVE_CXX_FLAG_FNO_EXCEPTIONS
-- Performing Test HAVE_CXX_FLAG_FNO_EXCEPTIONS - Success
-- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING
-- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING - Success
-- Performing Test HAVE_CXX_FLAG_WD654
-- Performing Test HAVE_CXX_FLAG_WD654 - Failed
-- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY
-- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY - Success
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile
-- Performing Test HAVE_CXX_FLAG_COVERAGE
-- Performing Test HAVE_CXX_FLAG_COVERAGE - Success
-- Performing Test HAVE_GNU_POSIX_REGEX
-- Performing Test HAVE_GNU_POSIX_REGEX
-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
-- Performing Test HAVE_POSIX_REGEX
-- Performing Test HAVE_POSIX_REGEX
-- Performing Test HAVE_POSIX_REGEX -- success
-- Performing Test HAVE_STEADY_CLOCK
-- Performing Test HAVE_STEADY_CLOCK
-- Performing Test HAVE_STEADY_CLOCK -- success
-- Configuring done
-- Generating done
-- Build files have been written to: /stck/moessadk/Workspace/MLIR/iree/iree-llvm-sandbox/build
[1/3162] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o
[2/3162] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o
[3/3162] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o
[4/3162] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/RustDemangle.cpp.o
[5/3162] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/DLangDemangle.cpp.o
[6/3162] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/AArch64TargetParser.cpp.o
[7/3162] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ABIBreak.cpp.o
[8/3162] Building CXX object lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o
[9/3162] Linking CXX shared library lib/libLLVMDemangle.so.14git
FAILED: lib/libLLVMDemangle.so.14git
: && /stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/llvm-12.0.0-ovrjxofhcx5djzzqhhl6flbldnpispvm/bin/clang++ -fPIC -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -ffunction-sections -fdata-sections -O3 -DNDEBUG  -Wl,-z,defs -Wl,-z,nodelete   -Wl,-rpath-link,/stck/moessadk/Workspace/MLIR/iree/iree-llvm-sandbox/build/./lib  -Wl,-O3 -Wl,--gc-sections -shared -Wl,-soname,libLLVMDemangle.so.14git -o lib/libLLVMDemangle.so.14git lib/Demangle/CMakeFiles/LLVMDemangle.dir/Demangle.cpp.o lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangle.cpp.o lib/Demangle/CMakeFiles/LLVMDemangle.dir/MicrosoftDemangleNodes.cpp.o lib/Demangle/CMakeFiles/LLVMDemangle.dir/RustDemangle.cpp.o lib/Demangle/CMakeFiles/LLVMDemangle.dir/DLangDemangle.cpp.o  -Wl,-rpath,"\$ORIGIN/../lib" && :
/usr/bin/ld: lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o: réadressage inconnu (0x2a) dans la section « .text._ZNK4llvm16itanium_demangle4Node4dumpEv »
/usr/bin/ld: édition de lien finale en échec: Mauvaise valeur
clang-12: error: linker command failed with exit code 1 (use -v to see invocation)
[10/3162] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/ARMTargetParser.cpp.o
ninja: build stopped: subcommand failed.
-- Python version 3.8.10 (default, Jun 27 2021, 09:32:56)
[GCC 8.3.0] (/stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/python-3.8.10-7f7fkeh4425fbs77caqo5hrxvkf4nuyw/bin/python3)
CCACHE = True
-- Enabling IREE from /stck/moessadk/Workspace/MLIR/iree/iree
-- Using inferred llvm-project path: /stck/moessadk/Workspace/MLIR/iree/iree/third_party/llvm-project
WARNING: Project developers use ccache which is not installed
-- Running cmake:
  cmake -GNinja -B/stck/moessadk/Workspace/MLIR/iree/iree-llvm-sandbox/build -S/stck/moessadk/Workspace/MLIR/iree/iree/third_party/llvm-project/llvm -DLLVM_ENABLE_PROJECTS=mlir;clang;clang-tools-extra -DLLVM_TARGETS_TO_BUILD=X86 -DMLIR_INCLUDE_INTEGRATION_TESTS=ON -DLLVM_ENABLE_ASSERTIONS=ON -DBUILD_SHARED_LIBS=ON -DLLVM_INCLUDE_UTILS=ON -DLLVM_INSTALL_UTILS=ON -DLLVM_BUILD_EXAMPLES=ON -DMLIR_ENABLE_BINDINGS_PYTHON=ON -DPython3_EXECUTABLE=/stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/python-3.8.10-7f7fkeh4425fbs77caqo5hrxvkf4nuyw/bin/python3 -DCMAKE_BUILD_TYPE=Release -DLLVM_EXTERNAL_PROJECTS=iree_dialects;sandbox -DLLVM_EXTERNAL_SANDBOX_SOURCE_DIR=/stck/moessadk/Workspace/MLIR/iree/iree-llvm-sandbox -DLLVM_EXTERNAL_IREE_DIALECTS_SOURCE_DIR=/stck/moessadk/Workspace/MLIR/iree/iree/llvm-external-projects/iree-dialects -DCMAKE_C_COMPILER=/stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/llvm-12.0.0-ovrjxofhcx5djzzqhhl6flbldnpispvm/bin/clang -DCMAKE_CXX_COMPILER=/stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/llvm-12.0.0-ovrjxofhcx5djzzqhhl6flbldnpispvm/bin/clang++
-- Performing initial build: cmake --build /stck/moessadk/Workspace/MLIR/iree/iree-llvm-sandbox/build --target tools/sandbox/all mlir-opt mlir-translate mlir_runner_utils mlir_c_runner_utils llvm-mca llvm-objdump llc opt FileCheck
Traceback (most recent call last):
  File "configure.py", line 175, in <module>
    sys.exit(main(parse_arguments()))
  File "configure.py", line 169, in main
    subprocess.check_call(cmake_args, cwd=build_dir)
  File "/stck/sonics/spack_new/spack/opt/spack/linux-centos7-broadwell/gcc-8.3.0/python-3.8.10-7f7fkeh4425fbs77caqo5hrxvkf4nuyw/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', '/stck/moessadk/Workspace/MLIR/iree/iree-llvm-sandbox/build', '--target', 'tools/sandbox/all', 'mlir-opt', 'mlir-translate', 'mlir_runner_utils', 'mlir_c_runner_utils', 'llvm-mca', 'llvm-objdump', 'llc', 'opt', 'FileCheck']' returned non-zero exit status 1.

The actual error comes from the linker
/usr/bin/ld: lib/Demangle/CMakeFiles/LLVMDemangle.dir/ItaniumDemangle.cpp.o: réadressage inconnu (0x2a) dans la section « .text._ZNK4llvm16itanium_demangle4Node4dumpEv »
/usr/bin/ld: édition de lien finale en échec: Mauvaise valeur

According to this https://stackoverflow.com/questions/52737698/unable-to-compile-unrecognized-relocation-0x2a-in-section-text, you may need to update binutils on your machine.

Alternatively, try using lld, there should be an option in the configuration script (also cuts linking time 10x).

Thank you problem solved using lld

Problem solved by enabling lld in  configure.py


[ReapVoucher] Minor refactoring and move reap voucher prechecks from JS to dart

Closes #1580, only sending is still done in JS, which will be solved with #1540.

This also fixes a previously unknown issue that changing the network or the cid from the reap voucher page was hanging in an endless loop.

CI failes due to indexer backend, the rest of the integration tests work locally.


Trim npm package

See https://github.com/jakearchibald/idb-keyval/pull/81

Check the results here: https://bundlephobia.com/package/complaindate


Uncaught ReferenceError: $ is not defined

I noticed that the code coverage is only showing up sporadicly on pull requests. I'm not sure why I see it sometimes and why sometimes I don't.  I looked in the console and it seems like there's an error in one of the codecov listening scripts though.  Googling around makes it sound like it might be problem with jquery not being available.

I'm seeing this as well.

I'm seeing this too.  Likely needs to add an additional check for typeof $ === "undefined"

Yeah me too :(

Me too

...or simply remove usage of jQuery entirely, as addEventListener and postMessage are widely supported now.
@stevepeak Would you accept a PR on this? I proposed the change in #58

I hope this will be fixed. We're paying for your service and we don't even get a response from you.


Setup analytics to track user interactions

Update:
I am closing this issue for the following reasons:

The MB Search Branch is no longer in the route path.
The MB alpha branch is no longer in the route path.


fix CatalogRuleIndex

There was an error when creating the product index for catalog rules:
Argument 2 passed to Prettus\\Repository\\Events\\RepositoryEventBase::__construct() must be an instance of Illuminate\\Database\\Eloquent\\Model or null, instance of Illuminate\\Database\\Eloquent\\Builder given, called in /var/www/vendor/prettus/l5-repository/src/Prettus/Repository/Eloquent/BaseRepository.php on line 772

I found out that the Repositories which are used for that are not used correctly.

It's an error due to a new release of prettus. v2.6.43 don't work with bagisto


Add search box on People page

Based on this new functionality, you can search directly for a teacher's name. Thus, users no longer have to go through the entire list.

Codecov Report

Merging #92 into master will decrease coverage by 0.00%.
The diff coverage is 65.38%.

@@            Coverage Diff             @@
##           master      #92      +/-   ##
==========================================
- Coverage   58.31%   58.30%   -0.01%
==========================================
  Files          76       76
  Lines        5942     5984      +42
==========================================
+ Hits         3465     3489      +24
- Misses       2477     2495      +18

Impacted Files
Coverage Δ

lib/pages/people/view/people_page.dart
73.23% <65.38%> (-23.32%)
:arrow_down:

Continue to review full report at Codecov.

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


⚠ Bofrost.at has degraded performance

In 19c91e6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1387 ms

Resolved: Bofrost.at performance has improved in 4aa7ad2.


Remove husky and precommit, prepush, and git-hook scripts

Addresses https://github.com/infinitered/ignite-ir-boilerplate-andross/issues/120
Removes husky and git-hooks scripts from the boilerplate package.json

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


User suggestions based on follows

The algorithm is based on Pinterest's Pixie algorithm: https://medium.com/pinterest-engineering/an-update-on-pixie-pinterests-recommendation-system-6f273f737e1b. At a high level, the algorithm begins by selecting a set of "query nodes" from a user's following list and then runs a random walk per node, keeping track of the nodes visited during the walk. The most frequently visited nodes across all walks are the most "relevant" to the user and get returned as final suggestions. The suggestions are also shuffled so that is not a static list returned each time.
The suggestions are available on the Viewer type as a new field named suggestedUsers, which returns a `UserConnection:
  suggestedUsers(before: String, after: String, first: Int, last: Int): UsersConnection
    @goField(forceResolver: true)

It can be paginated like a typical cursor, but if no cursor is provided, it will generate a new set of recommendations.
Follow graph
The graph is represented as an adjacency list where the key is a user and the value is a list of users that the user follows. It is instantiated as a singleton using the sync.Map type to manage concurrent access and is refreshed periodically in the background every hour. I decided to keep the service in the backend since the graph itself is less than 300kb and could be moved to a separate service when we want to scale the service independently of the backend.
Selecting query nodes
Rather than selecting all follows, the algorithm selects 30 follows at random weighted by how recent the follow is. This keeps the execution time predictable and allows it to complete in real-time, but we can tune this to be any number.
Handling users with no followers
Each recommendation is saved to a table named recommendation_results which keeps track of how frequently a user gets recommended. This table is rolled up in a view that keeps track of the top 100 most frequently recommended users. We use this view for new users who have no followers, the idea being that this view is the "average" recommendation across all users.
Post-merge TODOs

[x] Add tests
[ ] Run migration to add the recommended_history table
[ ] Add refresh job to pg_cron to refresh top_recommended_users view

absolutely incredible stuff - worked like a charm with the frontend here: https://github.com/gallery-so/gallery/pull/1352


az network application-gateway ssl-cert create using KeyVault cert fails

Describe the bug
Trying to create an SSL certificate in Application Gateway using a KeyVault cert fails
Command Name
az network application-gateway ssl-cert create
Errors:
'Namespace' object has no attribute 'frontend_port'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az network application-gateway ssl-cert create -g {} --gateway-name {} --name {} --key-vault-secret-id {}

Expected Behavior
A cert is created in the gateway. It seems to work as the Listener using the cert is set up properly. But the actual command fails...
Environment Summary
Linux-4.19.128-microsoft-standard-x86_64-with-debian-bullseye-sid
Python 3.6.10
Installer: DEB

azure-cli 2.19.1

Additional Context

network

It seems like this started working again for some reason. We had 2 different problems end of last week. This, and one with Application Insight, that just "magically" started working again without any changes... Not sure why it was happening

@msyyc could verify whether it is service issue before.

I could not reproduce it. Does it ever happen after that?

Nope, it seems like it just started working for some reason...


Receive information about ignored text

Nice library - I like it!
My goal is to parse a certain programming language that has comments, and I would like to recover the information regarding these comments (e.g. the comment itself, or its position in the parsed text). The language has line ending comments (e.g. //) as well as block comments (e.g. /* .. */).
By using the '%ignore' directive to define a comment terminal (e.g. "%ignore COMMENT), the comments are truly ignored by the parser and I could not find a way to recover information about the comments.
Is there a way to receive information about ignored text pieces? Or, how would comments need to be described in Lark grammar to recover information about them?

See https://lark-parser.readthedocs.io/en/latest/recipes/

Thank you for pointing to this example. This seems to be exactly what I need!

Great. Closing the issue, but feel free to ask more questions.

Unfortunately, lexer callbacks are not supported by the default lexer used by the Earley parser, and I am not able to use the standard lexer in combination with the Early parser.
Could you consider adding an enhancement to the Earely parser to support also the lexer callback?

That would be complicated, because the Earley lexer isn't deterministic.
What happens if there's an ambiguity, and the two possible branches contain different comments?

I recognize that that the support for user callbacks may become more difficult. I see 2 options:

User callbacks are called during the dynamic lexing step, which means that a callback will be called multiple times, maybe with different arguments in the different branches. It's up to the callback function to handle these multiple calls.
The user callbacks are only called once the lexing/parsing is completed and the final branch is evaluated.

Coming back to my initial request to have extracted just comments that are described as ignored terminals, I came up with the following patch.
parser_frontends.py, line 143:
Old:
self.parser = xearley.Parser(parser_conf,
                             self.match,
                             ignore=lexer_conf.ignore,
                             resolve_ambiguity=resolve_ambiguity,
                             **kw
                             )

New:
self.parser = xearley.Parser(parser_conf,
                             self.match,
                             ignore=lexer_conf.ignore,
                             resolve_ambiguity=resolve_ambiguity,
                             user_callbacks=lexer_conf.callbacks,
                             **kw
                             )

xearley.py, line 7:
Old:
def __init__(self,  parser_conf, term_matcher, resolve_ambiguity=True, ignore = (), complete_lex = False):
    BaseParser.__init__(self, parser_conf, term_matcher, resolve_ambiguity)
    self.ignore = [Terminal(t) for t in ignore]
    self.complete_lex = complete_lex

New:
def __init__(self,  parser_conf, term_matcher, resolve_ambiguity=True, ignore = (), complete_lex = False, user_callbacks = ()):
    BaseParser.__init__(self, parser_conf, term_matcher, resolve_ambiguity)
    self.ignore = [Terminal(t) for t in ignore]
    self.complete_lex = complete_lex
    self.user_callbacks = user_callbacks

xearley.py, line 73:
Old:
# e.g. mandatory spacing.
for x in self.ignore:
    m = match(x, stream, i)
    if m:
        # Carry over any items still in the scan buffer, to past the end of the ignored items.

New:
# e.g. mandatory spacing.
for x in self.ignore:
    m = match(x, stream, i)
    if m:
        if x.name in self.user_callbacks:
            self.user_callbacks[x.name]( [m.group(), text_line, text_column] )
        # Carry over any items still in the scan buffer, to past the end of the ignored items.

This patch allows extracting the comments and to handle then them with the custom callback function.

For some reason I was very against the idea of calling the callbacks multiple times, but really I'm not sure why. If the user wants to take that performance hit, that's fine. And really, it's not such a huge difference, early is already pretty slow.
So if you want to submit this as a PR, I will accept it.
I'm still not sure what you're planning to do if there's more than one possible interpretation for comments? It might cause phantom comments to appear in your list.

Regarding my plan: I am planning to implement a programming language translator. The translated source code should keep as much as possible from the original source code, including the comments.
I will move forward with the implementation of the translator, and once the concept of the comment recuperation is validated I will submit the patch.

Sounds good! Looking forward to it.
Let me know if you have any questions, or want my input regarding the design or implementation.


Added a cask file for luxafor 1.2.7

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Thank you for the submission. In the future, please use x in checklists and Github will make them clickable.

Thanks @miccal for the merge and thanks @vitorgalvao for the code change and the info.


[RFE] Support JSON output for version command

Current situation
Neither kubectl-gadget, nor ig/gadgetctl provide JSON output for version command.
Impact
Some third-party applications implementing a UX (e.g. vscode AKS extension) need to parse output using regex.
Ideal future situation
Provide JSON version as kubectl does:
$ kubectl version -o json
{
  "clientVersion": {
    "major": "1",
    "minor": "25+",
    "gitVersion": "v1.25.0-alpha.1",
    "gitCommit": "2b51b2595ad63e59dcbab1f95620ed0ecc8c6d8c",
    "gitTreeState": "clean",
    "buildDate": "2022-06-15T19:40:34Z",
    "goVersion": "go1.18.3",
    "compiler": "gc",
    "platform": "linux/amd64"
  },
  "kustomizeVersion": "v4.5.4",
  "serverVersion": {
    "major": "1",
    "minor": "28",
    "gitVersion": "v1.28.3",
    "gitCommit": "04637423472f65e457a4106f5b831add7a4a71cf",
    "gitTreeState": "clean",
    "buildDate": "2023-11-03T12:16:48Z",
    "goVersion": "go1.20.10",
    "compiler": "gc",
    "platform": "linux/amd64"
  }
}

Further improvements
Initially it could provide just what we provide on default output. However, we could improve it to include gitCommit and other fields like kubectl does. Related to https://github.com/inspektor-gadget/inspektor-gadget/issues/1060.

Hey, I would love to work on it. Assign me!

@shivam200446 please be aware of #2446, that adds an interface to send the server information to the client. I think that'd be useful for this issue as well.

Hey, sorry for the inconvenience! I am getting confused about the issue. can I get some more insights and details?


update: otel-cli 0.2.0 -> 0.3.0

updates otel-cli from 0.2.0 to 0.3.0
see https://github.com/equinix-labs/otel-cli/releases/tag/v0.3.0 for changelog and release details
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

pushed another edit. new integration tests added examples utilizing sleep and echo binaries from coreutils, so added to the package closure and the existing main_test.go PATH substitution

Works fine now, I will merge this once ci ran.


Article on Easy Auth misses a key point that makes it pointless in most cases

There is a large article on Easy Auth, however it misses a key point which has wsted me a couple of days time.
The article resides in the ASP .NET Core documentation, so obviously it's aimed at people developing a web application. However, what the article fails to mention is that there is no way to get Easy Auth to work when running locally using Visual Studio without integrating an additional authentication package e.g. Microsoft.Identity.Web.
But if you are having to integrate Microsoft.Identity.Web into your application anyway, then Easy Auth isn't just pointless it's downright problematic, as you then unnecessarily have two authentication solutions attempting to work together.
As a consequence of this it seems to me that the use cases where Easy Auth is actually useful are extremely few and far between.
This should be highlighted to avoid wasting people's time.

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

ID: 75e17529-8b8a-1d67-f0e1-840d1d3ca990
Version Independent ID: 265645df-ef21-4631-1744-7014b3ee681a
Content: Authentication and authorization - Azure App Service
Content Source: articles/app-service/overview-authentication-authorization.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@Neutrino-Sunset
Thanks for your feedback! We will investigate and update as appropriate.

Regarding Visual Studio, the doc does point to https://learn.microsoft.com/en-us/azure/app-service/identity-scenarios, which states clearly that built-in authentication doesn't have VS integration. #please-close


Typings issues with AssetConvertion pallet

Hey team,
I'm experiencing an invalid type issue when trying to pass arguments to api.query.AssetConversion.Pools.getValue()
It can be observed at https://github.com/0xKheops/papi-experiments/tree/747123de7ddc2d5f9748a49434bf4e718f907d98
Notice the code runs fine and expected output is correct, it seems to be just a typing issue.
equivalent call in pjs :

Please have a look at this section of the docs 🙏
We will try our best to explain this better, but the gist of it is that inputing enums with Polkadot API shouldn't be done using plain js objects.
If you have a look at the types of getValue it shows this:

which means that you must pass exactly an Array of 2 objects with the following shape:
{ parents: number, interior: XcmV3Junctions }

The thing is: how can you create an XcmV3Junctions? The recommended way is to simply import the XcmV3Junctions enum creator, like this:
import { XcmV3Junctions } from "@polkadot-api/descriptors"

XcmV3Junctions.Here()

Once you know that, the DX is actually pretty amazing! Check this out:
https://github.com/polkadot-api/polkadot-api/assets/8620144/79163d0b-1dcb-4706-997f-5fc1f424912c
Alternatively you can use the Enum helper, like this:
https://github.com/polkadot-api/polkadot-api/assets/8620144/2f69b498-c01c-4ff9-a06b-93a05cc3fb19

that's great, thanks!


Add more kube-state-metrics

Note: Please remember to review the Datadog Contribution Guidelines
if you have not yet done so.
What does this PR do?

Tests changes made in https://github.com/DataDog/dd-agent/pull/3309
Updates metrics metadata

🚢  it

There's a couple of linting issues, you might also have to update the tests (see appveyor failure, travis didn't make it that far).


Add blank view, view header, variants for buttons, other tweaks

Overview
Some minor additions to support common use cases.
There is now a "ViewHeader" component which can be used for the top of a view.
I also added a "BlankView" with simple simplified properties to support common use cases; it has a title/subtitle and the ability to show back/close buttons.  If back/close buttons are displayed it will use a NavigationBar at the top, otherwise it will use a StatusBarBackground/ViewHeader.
An additional button variant called "light" has been added as well which uses the button color as the text color but with the light grey background.
Security
REMINDER: All file contents are public.

[x] I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc.

[x] Please verify that you double checked that .storybook/preview.js does not contain your participant access key details.
[x] There are no temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.

[x] These changes do not introduce any security risks, or any such risks have been properly mitigated.

Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.
Checklist
Testing

[ ] MyDataHelps iOS app
[ ] MyDataHelps Android app
[x] MyDataHelps website

Documentation

[x] I have added relevant Storybook updates to this PR as well.
[ ] If this feature requires a developer doc update, tag @CareEvolution/api-docs.

Consider "Squash and merge" as needed to keep the commit history reasonable on main.
Reviewers
Assign to the appropriate reviewer(s). Minimally, a second set of eyes is needed ensure no non-public information is published. Consider also including:

Subject-matter experts
Style/editing reviewers
Others requested by the content owner

I don't understand React, but the overall approach seems good to me. Just one possible security thing we might want to address, and I think it would actually be in MDH itself, not this PR:
Since the base64-encoded URL for the custom view tab includes the URL of the custom view and we whitelist the renderer url prefix, it's possible to send a participant a URL which renders a view that was never configured for that study.

It looks like at this point you do need to know the patientid. Otherwise it fails while trying to render the new view. But I'm not sure if we can count on that behavior.

Sorry, commented on wrong PR

Will be superceded shortly


Null character when serializeToJsonString is called on message

I found weird behavior, when I serialize message to json at the end there is null character \u0000.
I can't figure out why this is happening, in the end I'm sending this to temporal and deserializing on worker where it fails with Cannot decode json string
I have reproduce this here:
https://github.com/keboola/php-storage-driver-teradata/blob/746eb8f0b7ea7d1facc4041cf5d671999a5a581c/test.php
this is only object where encountered this
https://github.com/keboola/php-storage-driver-teradata/blob/zajca-kbc-2874/proto/table.proto#L199
git clone https://github.com/keboola/php-storage-driver-teradata.git
git checkout -b zajca-kbc-2874
composer install
php test.php

This is output when I run this script (note the end):
'{"credentials":{"@type":"type.googleapis.com/keboola.storageDriver.credentials.GenericBackendCredentials","host":"xxx","principal":"xxx","secret":"xxx","meta":{"@type":"type.googleapis.com/keboola.storageDriver.credentials.GenericBackendCredentials.TeradataCredentialsMeta","database":"xxx"}},"command":{"@type":"type.googleapis.com/keboola.storageDriver.command.table.TableImportFromFileCommand","formatTypeOptions":{"@type":"type.googleapis.com/keboola.storageDriver.command.table.TableImportFromFileCommand.CsvTypeOptions","columnsNames":["id","name","city","sex"],"delimiter":",","enclosure":"\\"","compression":"GZIP"},"filePath":{"root":"xxx","path":"xxx","fileName":"xxx"},"fileCredentials":{"@type":"type.googleapis.com/keboola.storageDriver.command.table.ImportExportShared.S3Credentials","key":"xxx","secret":"xxx","region":"eu-central-1"},"destination":{"path":["xxx"],"tableName":"xxx"},"importOptions":{"timestampColumn":"_timestamp","numberOfIgnoredLines":1,"dedupType":"INSERT_DUPLICATES"},"meta":{"@type":"type.googleapis.com/keboola.storageDriver.command.table.TableImportFromFileCommand.TeradataTableImportMeta"}}}' . "\0" . ''

This is what I see in debuger in my app:

Looks like you are using google/protobuf not protobuf-php/protobuf

Ah sorry, I missed correct repo.


⚠ Everything Hub has degraded performance

In 635e10e, Everything Hub (https://hub.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 8585 ms

Resolved: Everything Hub performance has improved in e4d9d63 after 5 minutes.


[as2_state_estimator] Add earth_geodetic in tf tree

Feature Description
Current tf tree only works with cartesian coordinates:
earth --> map --> odom --> baselink

Including wgs84 node in the tree will allow to transform also to/from geodetic coordinates:
wgs84 --> earth --> map --> odom --> baselink

As soon as the geodetic origin is set, the transformation between wgs84 and earth will be known and it will be static. Something similar happens with earth-map transformation (see #170).
The state estimator will absorb this complexity and the rest of the nodes would work equivalently with cartesian or geodetic coordinates.
Further implementations may also support other geodetic reference frames if needed.
Implementation Considerations
High level layers will command the controller through a new motion_reference topic (e.g. motion_reference/geopose).
void ControllerHandler::ref_geopose_callback(const geographic_msgs::msg::GeoPoseStamped::SharedPtr msg) {
  // pre-checks...

  geographic_msgs::msg::GeoPoseStamped geopose_msg = *msg;
  if (!tf_handler_.tryConvert(geopose_msg, input_pose_frame_id_)) {  // see footnote 1
    return;
  }
  ref_pose_                  = geopose_msg;
  motion_reference_adquired_ = true;

  if (!bypass_controller_) controller_ptr_->updateReference(ref_pose_);
}

tf handler will extend tryConvert method:
bool TfHandler::tryConvert(geographic_msgs::msg::GeoPoseStamped &_geopose,
                           const std::string &_target_frame) {
  // do some stuff and call convert
  geometry_msgs::msg::PoseStamped _pose = convert(_geopose, _target_frame);
}

and call a new convert implementation will receive a geopose and return a pose:
geometry_msgs::msg::PoseStamped TfHandler::convert(const geographic_msgs::msg::PoseStamped &_pose,
                                                   const std::string &target_frame,
                                                   const std::chrono::nanoseconds timeout) {
  // footnote 2: geopose_in --> pose_in (or similar)
  geometry_msgs::msg::PoseStamped pose_out;
  tf2::doTransform(_pose, pose_out,
                   tf_buffer_->lookupTransform(target_frame, _pose.header.frame_id,
                                               _pose.header.stamp, timeout));
  pose_out.header.frame_id = target_frame;
  pose_out.header.stamp    = _pose.header.stamp;
  return pose_out;
}

¹ Notice that with the given structure, tryConvert will fail since input and output will have now different types.
² doTransform use the same class types for input and output.

An alternative solution is to keep the use of Geometry Msgs PoseStamped, and indicate when it is geodesic or cartesian in the frame_id. In this way, the motion behaviors would work with both geodesic and Cartesian, and the motion references would not have to be extended. The tranformation will be done by the controller manager.
For that, TF Handler must be expand to interpret the frame_id wgs84 as geodesic and make the transformation to cartesian.
I think it is the most efficient way to not have to duplicate behaviors implementations, like having the Go To GPS and the Go To Cartesian. On the negative side, we would be encoding GPS information in a Pose message.

An alternative solution is to keep the use of Geometry Msgs PoseStamped, and indicate when it is geodesic or cartesian in the frame_id. In this way, the motion behaviors would work with both geodesic and Cartesian, and the motion references would not have to be extended. The tranformation will be done by the controller manager.

I think that we should not abuse the message types, I mean, we should not write a geodesic coordinates into a PoseStamped message.


Figure out the gas cost for verifying 20 signatures

Background
As per Jehan's feedback, we should figure out how much gas it cost to verify signatures on Terra. We should use https://docs.rs/cosmwasm-std/latest/cosmwasm_std/trait.Api.html#tymethod.secp256k1_verify and random 20 signatures which we need to verify to figure out the gas cost.
Why 20? Jehan's feedback was that if we were to compare it with other networks, approx 20 validators are holding 2/3 of staking power.
Done when

[ ] a new throwaway smart contract which calculates the gas is deployed to terra's mainnet
[ ] a gas cost is sent over to this github ticket so that we have it written down here as well
[ ] send it in discord in #paloma chain so that we can have a discussion to see if that's ok

@taariq @Vizualni terra1ndlz3aafxg2w34jvvkuglnwzh4pckzl043cl0r.

On testnet this uses 185357 gas. Testing on main.
☞ wasmd tx wasm execute $CONTRACT '{}' --amount 100upebble --from wallet $TXFLAG -y
gas estimate: 185357
logs: []
raw_log: '[]'
txhash: 3840CD027933AE3BEBC2507B33B2CE8B67170A39DE6E10F2D85E1D821E802F08

And on mainnet:

Transaction fee: 0.031809 UST
Gas Used: 116443

Thread in #paloma

Slightly better methodology in
Should probably have done this on testnet instead. In any case trying this

with 0 verifications
with 150 verifications

Gives us the gas amount per signature verification:
(247484 - 96036) / 150 = 1010


TypeError during Model Download

Whenever I try to download the model, I am facing the following error -
TypeError: 'odict_values' object does not support indexing
Trace-
TypeError                                 Traceback (most recent call last)
<ipython-input-4-e96c2c642dc5> in <module>()
5 model=Model(ws, 'sklearn_mnist')
6
----> 7 model.download(target_dir=os.getcwd(), exist_ok=True)
8
9 # verify the downloaded model file
~/anaconda/envs/dl/lib/python3.5/site-packages/azureml/core/model.py in download(self, target_dir, exist_ok, exists_ok)
531             raise AzureMLException(
532                 "Illegal state. Unpack={}, Paths in target_dir is {}".format(self.unpack, file_paths))
--> 533         model_path = os.path.commonpath(file_paths)
534         return model_path
535
~/anaconda/envs/dl/lib/python3.5/posixpath.py in commonpath(paths)
473         raise ValueError('commonpath() arg is an empty sequence')
474
--> 475     if isinstance(paths[0], bytes):
476         sep = b'/'
477         curdir = b'.'

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

ID: 89cb4f9c-34e0-b4df-f911-e083c420cee8
Version Independent ID: 5be8b3bb-fb17-175a-7ca0-d69cef414799
Content: Image classification tutorial: Deploy models - Azure Machine Learning service
Content Source: articles/machine-learning/service/tutorial-deploy-models-with-aml.md
Service: machine-learning
GitHub Login: @hning86
Microsoft Alias: haining

@adhishthite
Thanks for the feedback! We are currently investigating and will update you shortly.

@adhishthite We'd like to work with you further on this issue. Can you please email us at<EMAIL_ADDRESS>Please provide us with your subscription ID and the URL for this thread.
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

Hi,
I have the similar issue as well. Primarily using Databricks as my workbook environment. I already have a trained and registed model on my workspace:
rf = Model(ws, 'pumps_rf')
<azureml.core.model.Model at 0x7f66e160cda0>
rf.download(target_dir=Config.MODELS_DIR, exist_ok=True)
TypeError: 'odict_values' object does not support indexing
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<command-201219424688518> in <module>()
      1 rf = Model(ws, 'pumps_rf')
----> 2 rf.download(target_dir=Config.MODELS_DIR, exist_ok=True)

/databricks/python/lib/python3.5/site-packages/azureml/core/model.py in download(self, target_dir, exist_ok, exists_ok)
    531             raise AzureMLException(
    532                 "Illegal state. Unpack={}, Paths in target_dir is {}".format(self.unpack, file_paths))
--> 533         model_path = os.path.commonpath(file_paths)
    534         return model_path
    535

/local_disk0/pythonVirtualEnvDirs/virtualEnv-4c0e2c07-6518-455c-90be-b41917319fa1/lib/python3.5/posixpath.py in commonpath(paths)
    472         raise ValueError('commonpath() arg is an empty sequence')
    473
--> 474     if isinstance(paths[0], bytes):
    475         sep = b'/'
    476         curdir = b'.'

TypeError: 'odict_values' object does not support indexing

@YutongTie-MSFT , we are facing the exact same issue.
Downloading a model (model.download(target_dir='.', exist_ok=True)) works perfectly fine through Azure Notebooks, and exact same piece of code fails locally.
Trace
Traceback (most recent call last):
  File "local_examples/notebook_code.py", line 21, in <module>
    model.download(target_dir='.', exist_ok=True)
  File "/home/iva/nmbrs/ai_project/nmbrs_ai_v2/env/lib/python3.5/site-packages/azureml/core/model.py", line 533, in download
    model_path = os.path.commonpath(file_paths)
  File "/home/iva/nmbrs/ai_project/nmbrs_ai_v2/env/lib/python3.5/posixpath.py", line 474, in commonpath
    if isinstance(paths[0], bytes):
TypeError: 'odict_values' object does not support indexing

@YutongTie-MSFT I see exact same issue as well. was there any fix?


[CHALLENGE SUBMISSION] - Challenge 5

Please provide the following information for your submission:
What is your name? (First, Last)
Ethan Arrowood
Where is your GitHub Repo ?(With your challenge solution)
https://github.com/Ethan-Arrowood/25-days-of-serverless-2019/tree/master/NaughtyOrNice
What Challenge is this for? (Challenge number between 1 and 25)
Challenge 5
(Optional) Anything else we should know? e.g., language used, location, blog post?
TypeScript, Azure Functions, Azure Cognitive Services Text Analysis

nice, points for explaining the process

THANK YOU FOR YOUR #25DaysOfServerless SUBMISSION
We checked out your repository. We're thrilled to say your solution is now listed in our Hall of Fame
Thank you for your contributions!
This issue is now resolved! 🎉


Bug: Entity can't handle column named attributes

CodeIgniter4 Version
4.1.9
What happened?
When using attributes, as the property/attribute name of the Entity class, the Entity::setAttributes() method is called as a setter.
Names collision.
Steps to Reproduce
$e = new CodeIgniter\Entity\Entity();
$e->a = 1;
$e->attributes = [1, 2, 3];  // called the setAttributes method as a setter.
dd($e->toRawArray());

//$e->toRawArray() array (3)
//   0 => integer 1
//   1 => integer 2
//   2 => integer 3

Expected Output
//$e->toRawArray() array (2)
//    a => integer 1
//    attributes => array (3)
//        0 => integer 1
//        1 => integer 2
//        2 => integer 3

Anything else?
In Laravel prior to version 9, the custom setter and getter had the following format:
set/get + AttributeName + Attribute.
public function getFullNameAttribute()
{
    return "{$this->first_name} {$this->last_name}";
}

Until the update comes out, I offer my temporary solution. Wrap over "Entity"
`<?php
namespace App\Helpers;
use CodeIgniter\Entity\Entity;
class EntityModify extends Entity
{
private $clearFields = ["attributes","casts","datamap"];
//Фикс метода fill дабы все не ебнулось, когда в данных пришло что-то из списка ;)
public function fill(?array $data = null)
{
    if(is_array($data))
    {
        foreach (array_keys($data) as $key) {
            if (in_array($key, $this->clearFields, true)) {
                unset($data[$key]);
            }
        }
    }

    return parent::fill($data);
}

//Добавляем поля которые не должны быть в объекте описывающем таблицу но очень хочется их видеть в ответе  ;)
public function addMoreInfo($moreInfo)
{
    foreach ($moreInfo as $key => $value)
    {
        $this->attributes[$key] = $value;
    }
}

}`

In Laravel prior to version 9, the custom setter and getter had the following format:
set/get + AttributeName + Attribute.

What happened in Laravel 9?

Damn, I wish we could just rename the setAttributes method. That is by far the simplest solution.
I am wondering if that can be considered a bug, though. If others think so then I say we do that. That is preferable to any additional complexity in the logic that we would have to maintain, and it's the only method that would be affected by this.

Renaming the setAttributes() method seems to be the best solution.

@kenjis In version 9, the getter and setter is the method equivalent to the attribute name.
    protected function firstName(): Attribute
    {
        return Attribute::make(
            get: fn ($value) => ucfirst($value),
            set: fn ($value) => strtolower($value),
        );
    }

There is a possibility that there is an application that has its own Entity implementation with the appropriate setAttributes() method.
I do not consider it correct to rename the setAttributes() method, since the name fully reflects the essence of this method. I also think that the toRawArray() method should be called getAttributes().
Otherwise, any internal method that may be added in the future will need to be adapted instead of a friendly name.
It would be more correct to change the format of the names of setters and getters.

@the-gt99 Your proposal is a special case.
It will not work if the attributes attribute is required.

It is a much larger breaking change to update the format of the getters and setters and that's not something that could happen right now, I don't think. I'm a little leery of changing the name, honestly, but it's a pretty simple fix for people to change and I think it can legitimately be called a bug.
Naming it something like setEntityAttributes still keeps the meaning clear while fixing the issue. While I agree this is not a perfect fix, and I wouldn't be opposed to updating how it is handled in the future, I think the chances that someone will be trying to set an attribute named entityAttributes is slim enough that this can buy us time until we can do a bigger refactor.
I am very interested to from @MGatner @paulbalandan  and @samsonasik before we proceed with any changes though.

The current setX() and getX() are natural to me.
And as @lonnieezell says, changing them to something like setXAttribute() is a much larger breaking change.

The problem is that no matter how the setAttributes() method is renamed, there will be a chance that the method name will match the table field.
In any case, it will be BC.
But we need to consider all the consequences.

See my PR: #5763

For example, we add the Entity::setRelation() method.
It turns out that now the developer will not be able to use the relation attribute normally.
That is, with this approach, internal methods with names of the format set|get + something will be prohibited. Since this format is used for getters and setters.

@iRedds Probably I got you want to say.
If we want to add setRelation() and use it to set the relationship of entities,
we can't use it like that. It's too restrictive.

Removing setAttributes() seems a pretty big breaking change over simply stating in the docs that "attributes" is a reserved Entity name. I agree this should be changed in the future, but because of the collision we can't even deprecate this so it will take any dependent projects from functional to crash.
Personally I can't say specifics right now but I'm pretty sure some of my libraries extend setAttributes().

@MGatner @iRedds I fond another approach.
See #5781

I still think that for separate setters (mutators) it is necessary to change the name format. Like Laravel.

I think we will have to table this for the future. If this were a personal/company application I'd say we fix it right now, but it's not, and we have a contract with thousands of developers to not break their apps on a non major release. This rules out changing the naming scheme of the setters, or of the setAttributes method itself. As @MGatner suggested updating the docs to mention any currently reserved attribute/methods names is probably the best available option at the moment.
In the future, changing the naming scheme would be appropriate. The two options on the table at the moment are set{field}Attributes like Laravel, or _set{attribute} like Cake. I'm not sure what other systems use but that would be something to explore.

I'll also point out that this is precisely how Rails sets all model properties in bulk:
user = User.find params[:user_id]
user.attributes = filtered_params
user.save!

I have no need to mimic Rails but I mention it because I don't think it is wildly problematic to "reserve" attributes and then have it call setAttributes() on assignment.

@MGatner Do you mean RoR can't use attributes as a column name?

Correct. It is included in the (extensive) reserved word list.

I thought that the inability to use attributes was too great a limitation.
but Rails is like that, so we might as well make it a reserved word as well.

I'm not opposed to "deeper" solutions but I think this is the most straightforward for now.

Revisiting... @kenjis uodated the docs so attributes is now officially a reserved name. For other properties I propose that we require attribute set/get methods to be public. This will allow developers to implement protected function setRelation() without accidentally triggering on $entity->relation = $value, and is arguably the proper scoping already. It is confusing enough that set/get methods can be private or protected but still be called publicly by the magic methods for me to consider it a bug.

As for collision of methods that need to be public: I would still like to find a better solution in the future. I tend to name my entity methods without "get/set" because of this, which always feels like an undesirable concession: https://github.com/tattersoftware/codeigniter4-firebase/blob/develop/src/Firestore/Entity.php

Fixed by #7208


Added hangfire support

Context
We’ll shortly be adding a job to email QTS awardees and we could use a job library to simplify setting this up.
Changes proposed in this pull request
Add Hangfire to QT API and make the UI available at /_hangfire. The UI should require basic auth; those credentials should come from a Key Vault secret.
Guidance to review
N/A
Checklist

[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 Add Hangfire to QT API


forgotPassword is not affected by $throttling=false

While developing, I always turn throttling off just so that I don't hit the "too many requests" error all the time:
$auth = new \Delight\Auth\Auth($db, '', '', false);
This seems to work fine for stuff like
$auth->login($_POST['email'], $_POST['password'], 0);
... but when using
$auth->forgotPassword($_POST['email'], function ($selector, $token) {
        echo 'Send ' . $selector . ' and ' . $token . ' to the user (e.g. via email)';
});

... I still get the error "too many requests". Anything I can do to bypass this?

Thanks a lot!
This has been the only place where the $throttling option was not considered. Fixed in https://github.com/delight-im/PHP-Auth/commit/157a7095b0a4e12246923449e6083212438fc071.
Please try running
$ composer update delight-im/auth

to update the library to v8.2.1 and see if that changes the behavior.
By the way, passing null is generally cleaner than passing '', although in this case it does indeed not make any difference.

Seems to work! Thanks a lot for the quick fix and the tip regarding null!


Some suggestions

Hi,
I think this extension is great and I'm really appreciative for the effort you have put in!
I have some suggestions which could make this extension better:
Add a sass-lint integration, this would be really useful when auto-formating your code, it would read the .sass-lint.yml file in the root of your project and would use settings from there.
I would recommend adding an option to remove the '0' in decimal values that are below the integer of 1. For example,
instead of
transform: scale(0.6);
it would be
transform: scale(.6);
These are just my suggestions anyway, really liking this extension, thanks!

Thank you very much for your kind words. I was added Sass Lint configuration support in features roadmad, and I'll work on this when I get more free time. Thank you for your suggestion.

Sass lint support could be a WIN

I'm no longer maintain this extension. You can find more details in the project README. So I'll close this issue.


Client support for other methods than GET

The client has get and request methods, which should allow different types of HTTP methods. Would be nice if we'd have an interface for at least post, put and delete, allowing to set the request entity if needed.

And at least in some point, when using request the method module needs to be public to set the request method:
https://github.com/pimeys/hyper/commit/27a7454f265896bb5ff778242445ef852f9c1890

You should be able to use hyper::Method to access any of them: https://github.com/hyperium/hyper/blob/master/src/lib.rs#L41
I'm personally uncertain how many additional "helper" methods should exist, when you can customize the method, headers and body on a Request and then call client.request(req). There are several of these in 0.10, but I tried to be more conservative this time, figuring get was definitely needed. Perhaps also post, but I dislike how you may or may not need a body for POST, but defining a function would require making you choose...

Ok, didn't notice the methods are available in hyper module. Works now.

Since it seems the issue was just being able to use hyper::Method in Request::new, I'll close this for now. Proposals of convenience functions for Client are always welcome, ideally with examples supporting them.


Not registered for 0.1.1?

Can't find 0.1.1 when installing the ember-cli-pusher module (ember install ember-cli-pusher)

@ivanvotti believe you just need to create a release for 0.1.1

done:)


Animations don,t work when i scroll

Hi
I have no problem with wow, but animations only work when the page loads for first time, and when i scroll page animations don't work ..
Is there any thing that I haven't done yet ?

Hi @alihasaniGit ,
By default, when WOW is intialialized, animations are only run once, when you scroll to items, as you can see on official website.
But you can easily re-init the library though,  by calling NgwWowService.init()
i suggest adding this in your app main component, when done navigating to a page:
import { Component, OnInit, OnDestroy } from '@angular/core';
import { Router, NavigationEnd } from '@angular/router';
import { NgwWowService } from 'ngx-wow';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss']
})
export class AppComponent implements OnInit, OnDestroy {

  constructor(private router: Router, private wowService: NgwWowService){
    this.router.events.filter(event => event instanceof NavigationEnd).subscribe(event => {
      // Reload WoW animations when done navigating to page,
      // but you are free to call it whenever/wherever you like
      this.wowService.init();
    });
}

I have done your suggest. actually i put "NgwWowService" in my "HomePageComponent" (instead of appComponent) and i initialized wowService in the component's constructor as you said. totally i did all things that you said, but now when i scroll page, animations don't work, whereas they work at first page load ! (at the first time page loads)
Furthermore I think you have another mistake in your documentation in the section you have said "list wowjs in angular-cli as a global library". i mean this section :
   "scripts": [
        "../node_modules/wowjs/dist/wowjs.js"
      ],

When I got error and checked, I saw there is no "wowjs.js' file in "dist" folder. As you know it's name is wow.js. if I say correct, fix it ..
I waiting for your solution for animation problem ..
Thanks a lot friend ..

Hi,
I fixed the typo in the README.md (thanks again for reporting 👍 ).
Your issue with "animations only working at first page load" is difficult to diagnose.
Do you have a minimal repro project that i could checkout and try locally?

Please fix the typo problem in your documentation too.
Please wait. I want to try to fix problem. I'll let you know if i can't ..

Hi friend
I couldn't solve my problem, but I bring some information for you to get help.
The information I want to give are associated with some questions.
First one :
I put the pieces of code (you said in docs) this way :

Second one :
What should I do in this section? do I have to do any thing?

Third one :
As you saw in "Second one" section I put a debugger in the function but when an element reveals in the page debugger isn't called ..
Forth one :
When I give "wow fadeIn" class to an element, when I scroll to that, it's visibility is "hidden" and when I inspect (Chrome Console) on the element this is the view that I see :

Thanks for help ..

Hi @alihasaniGit ,
Once again, sorry because the documentation was missing another important info: referencing animate.css (which is installed and internally used by wowjsto actually animate items) in your project.
This can be achieved by either:

editing angular-cli.json as such:

      "styles": [
        "../node_modules/animated.css/animate.css"
      ],

or by importing in your main styles.scss (or styles.sass, styles.less, styles.styl) file as such:

...
@import "~animate.css/animate.css";
...

I have updated the docs accordingly an published v1.0.2 to NPM.
Also i clarified the rest of the documentation regarding your question on wowjs' Subscription (question 2): you don't need to subscribe to this.wowService.itemRevealed$ at all, for the library to work. I only mention that in the docs so that you know you can be notified when an item is revealed by wowjs in case this information might be useful for your use case.

Unfortunately I have the problem yet !
Did you notice to the "Forth one" section in the previous comment ?
Didn't it give you any clue ?

I think for someone the solution is to add the css class: (global)
.wow {
visibility: hidden;
}
Reference: https://stackoverflow.com/questions/23531064/wow-js-happens-on-page-load-and-not-on-scroll

Thanks for your input @henrykalex 👍
@alihasaniGit, @rituagrawal904 :  can you confirm it fixes your issue?

I have the problem yet, but thanks for your solution ..

I am with the same problem

My project uses the fullpage.js script. My solution for the wow script work in scroll page was change the option scrollBar for true in fullpage options.

I had the same issue, turned out it was because the window scroll event wasnt firing because I was scrolling inside a container div. The solution is designating the scrollContainer in the init options.
The types for NgwWowConfig are incorrect, it lists scrollContainer as an HTMLElement but it is actually a css selector so should be string.
My working config looks like this
this.wowService.init({
    scrollContainer: '#scrollContainer' as any
});

This is correct will there be a PR that address this?

Hi all,
I fixed the typing issue and released v2.0.1.
Thanks @attbgold for reporting

Thanks @mateusneves your solution saved my day.


docs: Cleanup in preparation for release 1.5.

Automated message from Dropbox CLA bot
@synicalsyntax, it looks like you've already signed the Dropbox CLA. Thanks!

Nice, these changes are great!  Merged, thanks @synicalsyntax!


Paf 49 test cert 2

What?
To access PRP1 we have to access the link via a secure way. So we have a self-signing certificate provided.
Why?
This is the most secure way for the services to talk to each other, we have set the NODE_AUTH=0 because as a self signing cert it does not have a recognised authority hence why we keep the following in the ims reolver deployment
```
- name: NODE_OPTIONS
value: "--use-openssl-ca"
`            {{ if or (eq .KUBE_NAMESPACE .BRANCH_ENV) (eq .KUBE_NAMESPACE .UAT_ENV) }}
            - name: NODE_TLS_REJECT_UNAUTHORIZED
              value: "0"`
We will need to add prod option in there.

## How?
So the best way for Node is to mount a config map as a persistent storage to store the cert then mount the config map as a volume in/etc/ss/certs and call it in the PAF app.

## Testing?
@shamiluwais had a look and will do some further verification that everything is as it is as we are currently facing a 504 and the logs are attached below

## Screenshots (optional)
![image](https://github.com/UKHomeOffice/paf/assets/125476151/281e1ac6-cf60-4a71-b25a-c884ef999174)
![image](https://github.com/UKHomeOffice/paf/assets/125476151/87e33d3a-8d65-4298-ae7f-4b40c890177a)

## Anything Else? (optional)
We are waiting for the error 504 to be resolved and then we can test but prior to this we did have a case id

## Screenshots (optional)
## Anything Else? (optional)
let me know if you need anything - so as for the cert we have it stored securely in hof-services config as a base64 encoded cert and called it via the deploy.sh script

can’t approve til it’s tested

Just fixed your PR, the headings weren't showing.  You had your backtiks in the wrong place


[BUG] "02 Start the server" doesn't work

Rancher Server Setup

Rancher version: 2.7
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details:
almalinux 9.1
fresh system
bare metal
podman, also docker ce 23

Information about the Cluster

Kubernetes version:
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

Custom
User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions:

root
Describe the bug

the container fails to start
To Reproduce

setenforce 0
// add http https to firewall, reload firewall (done via cockpit webui)
docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher

Result
Expected Result

A running and accessible rancher node via :80 or :443
Screenshots

Additional context

docker logs
INFO: Running k3s server --cluster-init --cluster-reset

ERROR:

time="2023-02-11T19:01:54Z" level=warning msg="remove /var/lib/rancher/k3s/agent/etc/k3s-api-server-agent-load-balancer.json: no such file or directory"

time="2023-02-11T19:01:54Z" level=info msg="Starting k3s v1.24.4+k3s1 (c3f830e9)"

time="2023-02-11T19:01:54Z" level=info msg="Managed etcd cluster bootstrap already complete and initialized"

time="2023-02-11T19:01:54Z" level=info msg="Starting temporary etcd to reconcile with datastore"

{"level":"info","ts":"2023-02-11T19:01:54.782Z","caller":"embed/etcd.go:131","msg":"configuring peer listeners","listen-peer-urls":["http://<IP_ADDRESS>:2400"]}

{"level":"info","ts":"2023-02-11T19:01:54.782Z","caller":"embed/etcd.go:139","msg":"configuring client listeners","listen-client-urls":["http://<IP_ADDRESS>:2399"]}

{"level":"info","ts":"2023-02-11T19:01:54.782Z","caller":"embed/etcd.go:308","msg":"starting an etcd server","etcd-version":"3.5.3","git-sha":"Not provided (use ./build instead of go build)","go-version":"go1.18.1","go-os":"linux","go-arch":"amd64","max-cpu-set":8,"max-cpu-available":8,"member-initialized":true,"name":"9cdd045aaa4a-6ceb887a","data-dir":"/var/lib/rancher/k3s/server/db/etcd-tmp","wal-dir":"","wal-dir-dedicated":"","member-dir":"/var/lib/rancher/k3s/server/db/etcd-tmp/member","force-new-cluster":true,"heartbeat-interval":"500ms","election-timeout":"5s","initial-election-tick-advance":true,"snapshot-count":10000,"snapshot-catchup-entries":5000,"initial-advertise-peer-urls":["http://<IP_ADDRESS>:2400"],"listen-peer-urls":["http://<IP_ADDRESS>:2400"],"advertise-client-urls":["http://<IP_ADDRESS>:2399"],"listen-client-urls":["http://<IP_ADDRESS>:2399"],"listen-metrics-urls":[],"cors":["*"],"host-whitelist":["*"],"initial-cluster":"","initial-cluster-state":"new","initial-cluster-token":"","quota-size-bytes":2147483648,"pre-vote":true,"initial-corrupt-check":true,"corrupt-check-time-interval":"0s","auto-compaction-mode":"","auto-compaction-retention":"0s","auto-compaction-interval":"0s","discovery-url":"","discovery-proxy":"","downgrade-check-interval":"5s"}

{"level":"info","ts":"2023-02-11T19:01:54.783Z","caller":"etcdserver/backend.go:81","msg":"opened backend db","path":"/var/lib/rancher/k3s/server/db/etcd-tmp/member/snap/db","took":"839.774µs"}

{"level":"info","ts":"2023-02-11T19:01:54.785Z","caller":"etcdserver/server.go:529","msg":"No snapshot found. Recovering WAL from scratch!"}

{"level":"info","ts":"2023-02-11T19:01:54.796Z","caller":"etcdserver/raft.go:556","msg":"forcing restart member","cluster-id":"b6c7ec2c9e50402b","local-member-id":"6d7c3a166a7ff3dc","commit-index":795}

{"level":"info","ts":"2023-02-11T19:01:54.796Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc switched to configuration voters=()"}

{"level":"info","ts":"2023-02-11T19:01:54.796Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc became follower at term 7"}

{"level":"info","ts":"2023-02-11T19:01:54.796Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"newRaft 6d7c3a166a7ff3dc [peers: [], term: 7, commit: 795, applied: 0, lastindex: 795, lastterm: 7]"}

{"level":"warn","ts":"2023-02-11T19:01:54.871Z","caller":"auth/store.go:1220","msg":"simple token is not cryptographically signed"}

{"level":"info","ts":"2023-02-11T19:01:54.883Z","caller":"mvcc/kvstore.go:415","msg":"kvstore restored","current-rev":758}

{"level":"info","ts":"2023-02-11T19:01:54.896Z","caller":"etcdserver/quota.go:94","msg":"enabled backend quota with default value","quota-name":"v3-applier","quota-size-bytes":2147483648,"quota-size":"2.1 GB"}

{"level":"info","ts":"2023-02-11T19:01:54.913Z","caller":"etcdserver/corrupt.go:46","msg":"starting initial corruption check","local-member-id":"6d7c3a166a7ff3dc","timeout":"15s"}

{"level":"info","ts":"2023-02-11T19:01:54.913Z","caller":"etcdserver/corrupt.go:116","msg":"initial corruption checking passed; no corruption","local-member-id":"6d7c3a166a7ff3dc"}

{"level":"info","ts":"2023-02-11T19:01:54.913Z","caller":"etcdserver/server.go:851","msg":"starting etcd server","local-member-id":"6d7c3a166a7ff3dc","local-server-version":"3.5.3","cluster-version":"to_be_decided"}

{"level":"info","ts":"2023-02-11T19:01:54.913Z","caller":"etcdserver/server.go:752","msg":"starting initial election tick advance","election-ticks":10}

{"level":"info","ts":"2023-02-11T19:01:54.914Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc switched to configuration voters=(7889244515196728284)"}

{"level":"info","ts":"2023-02-11T19:01:54.914Z","caller":"membership/cluster.go:421","msg":"added member","cluster-id":"b6c7ec2c9e50402b","local-member-id":"6d7c3a166a7ff3dc","added-peer-id":"6d7c3a166a7ff3dc","added-peer-peer-urls":["https://<IP_ADDRESS>:2380"]}

{"level":"info","ts":"2023-02-11T19:01:54.914Z","caller":"membership/cluster.go:584","msg":"set initial cluster version","cluster-id":"b6c7ec2c9e50402b","local-member-id":"6d7c3a166a7ff3dc","cluster-version":"3.5"}

{"level":"info","ts":"2023-02-11T19:01:54.914Z","caller":"api/capability.go:75","msg":"enabled capabilities for version","cluster-version":"3.5"}

{"level":"info","ts":"2023-02-11T19:01:54.915Z","caller":"embed/etcd.go:277","msg":"now serving peer/client/metrics","local-member-id":"6d7c3a166a7ff3dc","initial-advertise-peer-urls":["http://<IP_ADDRESS>:2400"],"listen-peer-urls":["http://<IP_ADDRESS>:2400"],"advertise-client-urls":["http://<IP_ADDRESS>:2399"],"listen-client-urls":["http://<IP_ADDRESS>:2399"],"listen-metrics-urls":[]}

{"level":"info","ts":"2023-02-11T19:01:54.915Z","caller":"embed/etcd.go:581","msg":"serving peer traffic","address":"<IP_ADDRESS>:2400"}

{"level":"info","ts":"2023-02-11T19:01:54.915Z","caller":"embed/etcd.go:553","msg":"cmux::serve","address":"<IP_ADDRESS>:2400"}

{"level":"info","ts":"2023-02-11T19:02:03.797Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc is starting a new election at term 7"}

{"level":"info","ts":"2023-02-11T19:02:03.797Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc became pre-candidate at term 7"}

{"level":"info","ts":"2023-02-11T19:02:03.797Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc received MsgPreVoteResp from 6d7c3a166a7ff3dc at term 7"}

{"level":"info","ts":"2023-02-11T19:02:03.797Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc became candidate at term 8"}

{"level":"info","ts":"2023-02-11T19:02:03.797Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc received MsgVoteResp from 6d7c3a166a7ff3dc at term 8"}

{"level":"info","ts":"2023-02-11T19:02:03.797Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"6d7c3a166a7ff3dc became leader at term 8"}

{"level":"info","ts":"2023-02-11T19:02:03.797Z","logger":"raft","caller":"etcdserver/zap_raft.go:77","msg":"raft.node: 6d7c3a166a7ff3dc elected leader 6d7c3a166a7ff3dc at term 8"}

{"level":"info","ts":"2023-02-11T19:02:03.908Z","caller":"etcdserver/server.go:2044","msg":"published local member to cluster through raft","local-member-id":"6d7c3a166a7ff3dc","local-member-attributes":"{Name:9cdd045aaa4a-6ceb887a ClientURLs:[http://<IP_ADDRESS>:2399]}","request-path":"/0/members/6d7c3a166a7ff3dc/attributes","cluster-id":"b6c7ec2c9e50402b","publish-timeout":"15s"}

{"level":"info","ts":"2023-02-11T19:02:03.908Z","caller":"embed/serve.go:98","msg":"ready to serve client requests"}

{"level":"info","ts":"2023-02-11T19:02:03.909Z","caller":"embed/serve.go:140","msg":"serving client traffic insecurely; this is strongly discouraged!","address":"<IP_ADDRESS>:2399"}

time="2023-02-11T19:02:03Z" level=info msg="Defragmenting etcd database"

{"level":"info","ts":"2023-02-11T19:02:03.910Z","caller":"v3rpc/maintenance.go:89","msg":"starting defragment"}

{"level":"info","ts":"2023-02-11T19:02:03.975Z","caller":"backend/backend.go:497","msg":"defragmenting","path":"/var/lib/rancher/k3s/server/db/etcd-tmp/member/snap/db","current-db-size-bytes":2396160,"current-db-size":"2.4 MB","current-db-size-in-use-bytes":2392064,"current-db-size-in-use":"2.4 MB"}

{"level":"info","ts":"2023-02-11T19:02:04.050Z","caller":"backend/backend.go:549","msg":"finished defragmenting directory","path":"/var/lib/rancher/k3s/server/db/etcd-tmp/member/snap/db","current-db-size-bytes-diff":0,"current-db-size-bytes":2396160,"current-db-size":"2.4 MB","current-db-size-in-use-bytes-diff":-4096,"current-db-size-in-use-bytes":2387968,"current-db-size-in-use":"2.4 MB","took":"139.901625ms"}

{"level":"info","ts":"2023-02-11T19:02:04.050Z","caller":"v3rpc/maintenance.go:95","msg":"finished defragment"}

time="2023-02-11T19:02:04Z" level=info msg="etcd temporary data store connection OK"

time="2023-02-11T19:02:04Z" level=info msg="Reconciling bootstrap data between datastore and disk"

time="2023-02-11T19:02:04Z" level=info msg="Cluster reset: backing up certificates directory to /var/lib/rancher/k3s/server/tls-1676142124"

time="2023-02-11T19:02:04Z" level=warning msg="Updating bootstrap data on disk from datastore"

time="2023-02-11T19:02:04Z" level=info msg="stopping etcd"

{"level":"info","ts":"2023-02-11T19:02:04.140Z","caller":"embed/etcd.go:368","msg":"closing etcd server","name":"9cdd045aaa4a-6ceb887a","data-dir":"/var/lib/rancher/k3s/server/db/etcd-tmp","advertise-peer-urls":["http://<IP_ADDRESS>:2400"],"advertise-client-urls":["http://<IP_ADDRESS>:2399"]}

{"level":"info","ts":"2023-02-11T19:02:04.141Z","caller":"etcdserver/server.go:1453","msg":"skipped leadership transfer for single voting member cluster","local-member-id":"6d7c3a166a7ff3dc","current-leader-member-id":"6d7c3a166a7ff3dc"}

time="2023-02-11T19:02:04Z" level=fatal msg="starting kubernetes: preparing server: start managed database: Managed etcd cluster membership was previously reset, please remove the cluster-reset flag and start k3s normally.  Create /etc/containers/nodocker to quiet msg.
host:
  arch: amd64
  buildahVersion: 1.27.3
  cgroupControllers:
  - cpuset
  - cpu
  - io
  - memory
  - hugetlb
  - pids
  - rdma
  - misc
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.1.4-1.el9.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.4, commit: 24a4eb8c5272ea46c28889a24fc0a9ba1f4b0c74'
  cpuUtilization:
    idlePercent: 98.71
    systemPercent: 0.16
    userPercent: 1.12
  cpus: 8
  distribution:
    distribution: '"almalinux"'
    version: "9.1"
  eventLogger: journald
  hostname: data.local
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.14.0-162.12.1.el9_1.x86_64
  linkmode: dynamic
  logDriver: journald
  memFree:<PHONE_NUMBER>8
  memTotal:<PHONE_NUMBER>6
  networkBackend: netavark
  ociRuntime:
    name: crun
    package: crun-1.5-1.el9.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 1.5
      commit: 54ebb8ca8bf7e6ddae2eb919f5b82d1d96863dea
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    exists: true
    path: /run/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_NET_RAW,CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: false
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.2.0-2.el9_0.x86_64
    version: |-
      slirp4netns version 1.2.0
      commit: 656041d45cfca7a4176f6b7eed9e4fe6c11e8383
      libslirp: 4.4.0
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.2
  swapFree:<PHONE_NUMBER>6
  swapTotal:<PHONE_NUMBER>6
  uptime: 0h 11m 56.00s
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  - journald
  network:
  - bridge
  - macvlan
  volume:
  - local
registries:
  search:
  - registry.access.redhat.com
  - registry.redhat.io
  - docker.io
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 1
    stopped: 0

You can't comment at this time — your comment is too long (maximum is 65536 characters).

https://pastebin.com/QJepfKDF

I am not an almalinux expert. However, I can see these panic logs from that pastebin url.
panic: F0217 14:09:36.199831      74 network_policy_controller.go:380] failed to run iptables command to create KUBE-ROUTER-INPUT chain due to running [/usr/bin/iptables -t filter -S KUBE-ROUTER-INPUT 1 --wait]: exit status 3: iptables v1.8.6 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

goroutine 10874 [running]:
k8s.io/klog/v2.(*loggingT).output(0x7eb5ea0, 0x3, 0x0, 0xc004a8c690, 0x1, {0x6469804?, 0x2?}, 0xc0000ae800?, 0x0)
	/go/pkg/mod/github.com/k3s-io/klog/v2@v2.60.1-k3s1/klog.go:820 +0x694
k8s.io/klog/v2.(*loggingT).printfDepth(0x7eb5ea0, 0x11?, 0x0, {0x0, 0x0}, 0x48cf9b?, {0x4cd8c99, 0x3b}, {0xc0059100c0, 0x2, ...})
	/go/pkg/mod/github.com/k3s-io/klog/v2@v2.60.1-k3s1/klog.go:630 +0x1f2
k8s.io/klog/v2.(*loggingT).printf(...)
	/go/pkg/mod/github.com/k3s-io/klog/v2@v2.60.1-k3s1/klog.go:612
k8s.io/klog/v2.Fatalf(...)
	/go/pkg/mod/github.com/k3s-io/klog/v2@v2.60.1-k3s1/klog.go:1496
github.com/cloudnativelabs/kube-router/pkg/controllers/netpol.(*NetworkPolicyController).ensureTopLevelChains(0xc00602ec00)
	/go/pkg/mod/github.com/k3s-io/kube-router@v1.5.1-0.20220630214451-a43bcd8511d2/pkg/controllers/netpol/network_policy_controller.go:380 +0x150c
github.com/cloudnativelabs/kube-router/pkg/controllers/netpol.(*NetworkPolicyController).Run(0xc00602ec00, 0xc00f497da0, 0xc000e50000, 0xc009730860)
	/go/pkg/mod/github.com/k3s-io/kube-router@v1.5.1-0.20220630214451-a43bcd8511d2/pkg/controllers/netpol/network_policy_controller.go:166 +0x16f
created by github.com/k3s-io/k3s/pkg/agent/netpol.Run
	/go/src/github.com/k3s-io/k3s/pkg/agent/netpol/netpol.go:135 +0xacc

This is not in the Rancher Support Matrix: https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-7-1/
I recommend this Helm CLI Quick Start. You may need to adjust k3s parameters to avoid panic.
https://ranchermanager.docs.rancher.com/getting-started/quick-start-guides/deploy-rancher-manager/helm-cli

Aparently nftables replace iptables. Not sure if only in Alma9 or if it's a RHEL thing in general or a Linux thing in general.
Gentoo wiki says https://wiki.gentoo.org/wiki/Nftables
I'm guessing before long k3s or rancher will have to adapt.
I installed Ubuntu 22.04 now and will close this issue.


chore: Update dependences to latest

Summary

Update dependences to latest

Resolves: #
Changes

Please provide a summary of what's being changed

User experience

Please share what the user experience looks like before and after this change

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[ ] I have performed a self-review of this change
[ ] Changes have been tested
[ ] Changes are documented

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5d971c0) 39.83% compared to head (72685ab) 39.80%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #144      +/-   ##
==========================================
- Coverage   39.83%   39.80%   -0.03%
==========================================
  Files          13       13
  Lines        1338     1339       +1
==========================================
  Hits          533      533
- Misses        805      806       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.