text:
python dev ctrl fails to install on Raspi Ubuntu

python dev ctrl fails to build on Raspi Ubuntu (both on server and desktop ubuntu versions on raspi), Failed building wheel for dbus-python.  while the same seem to work fine on x86 ubuntu
**pip3 install out/host/controller/python/chip-0.0-cp38-cp38-linux_aarch64.whl
Processing ./out/host/controller/python/chip-0.0-cp38-cp38-linux_aarch64.whl
Collecting dbus-python
Downloading dbus-python-1.2.16.tar.gz (576 kB)
|████████████████████████████████| 576 kB 3.0 MB/s
Collecting pgi
Downloading pgi-0.0.11.2.tar.gz (239 kB)
|████████████████████████████████| 239 kB 8.1 MB/s
Building wheels for collected packages: dbus-python, pgi
Building wheel for dbus-python (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py'"'"'; file='"'"'/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-bgp_kby0
cwd: /tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/
Complete output (217 lines):
running bdist_wheel
running build
creating /tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/build
creating /tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/build/temp.linux-aarch64-3.8
checking whether make supports nested variables... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define EXTENSIONS... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... no
checking whether make supports the include directive... no
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking dependency style of gcc... none
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking for native Windows host... no
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert aarch64-unknown-linux-gnu file names to aarch64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert aarch64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for inline... inline
checking for gawk... (cached) gawk
checking for python... /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/bin/python
checking for a version of Python >= '2.1.0'... yes
checking for a version of Python >= '2.7'... yes
checking for the distutils Python package... yes
checking for Python include path... -I/usr/include/python3.8
checking for Python library path... -L/usr/lib -lpython3.8
checking for Python site-packages path... /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/lib/python3.8/site-packages
checking python extra libraries... -lcrypt -lpthread -ldl  -lutil -lm -lm
checking python extra linking flags... -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
checking consistency of all components of python development environment... yes
checking for python version... 3.8
checking for python platform... linux
checking for python script directory... ${prefix}/lib/python3.8/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python3.8/site-packages
checking python module: sphinx... no
checking python module: sphinx_rtd_theme... no
checking for dbus-run-session... /usr/bin/dbus-run-session
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DBUS... yes
checking for GLIB... yes
checking whether C compiler accepts -Werror=unknown-warning-option... no
checking whether C compiler accepts -Wno-suggest-attribute=format... yes
checking whether C compiler accepts -fno-strict-aliasing... yes
checking whether C compiler accepts -Wdeprecated-declarations... yes
checking whether C compiler accepts -Wno-duplicated-branches... yes
checking whether C compiler accepts -Wno-inline... yes
checking whether C compiler accepts -Wno-redundant-decls... yes
checking whether C compiler accepts -Wno-switch-default... yes
checking whether C compiler accepts -Wno-write-strings... yes
checking whether C compiler accepts -Wnested-externs... yes
checking whether C compiler accepts -Wmissing-prototypes... yes
checking whether C compiler accepts -Wstrict-prototypes... yes
checking whether C compiler accepts -Wdeclaration-after-statement... yes
checking whether C compiler accepts -Wimplicit-function-declaration... yes
checking whether C compiler accepts -Wold-style-definition... yes
checking whether C compiler accepts -Wjump-misses-init... yes
checking whether C compiler accepts -Wall... yes
checking whether C compiler accepts -Wextra... yes
checking whether C compiler accepts -Wundef... yes
checking whether C compiler accepts -Wwrite-strings... yes
checking whether C compiler accepts -Wpointer-arith... yes
checking whether C compiler accepts -Wmissing-declarations... yes
checking whether C compiler accepts -Wredundant-decls... yes
checking whether C compiler accepts -Wno-unused-parameter... yes
checking whether C compiler accepts -Wno-missing-field-initializers... yes
checking whether C compiler accepts -Wformat=2... yes
checking whether C compiler accepts -Wcast-align... yes
checking whether C compiler accepts -Wformat-nonliteral... yes
checking whether C compiler accepts -Wformat-security... yes
checking whether C compiler accepts -Wsign-compare... yes
checking whether C compiler accepts -Wstrict-aliasing... yes
checking whether C compiler accepts -Wshadow... yes
checking whether C compiler accepts -Winline... yes
checking whether C compiler accepts -Wpacked... yes
checking whether C compiler accepts -Wmissing-format-attribute... yes
checking whether C compiler accepts -Wmissing-noreturn... yes
checking whether C compiler accepts -Winit-self... yes
checking whether C compiler accepts -Wredundant-decls... (cached) yes
checking whether C compiler accepts -Wmissing-include-dirs... yes
checking whether C compiler accepts -Wunused-but-set-variable... yes
checking whether C compiler accepts -Warray-bounds... yes
checking whether C compiler accepts -Wreturn-type... yes
checking whether C compiler accepts -Wswitch-enum... yes
checking whether C compiler accepts -Wswitch-default... yes
checking whether C compiler accepts -Wduplicated-cond... yes
checking whether C compiler accepts -Wduplicated-branches... yes
checking whether C compiler accepts -Wlogical-op... yes
checking whether C compiler accepts -Wrestrict... yes
checking whether C compiler accepts -Wnull-dereference... yes
checking whether C compiler accepts -Wdouble-promotion... yes
checking whether C compiler accepts -Wno-error=duplicated-branches... yes
checking whether C compiler accepts -Wno-error=inline... yes
checking whether C compiler accepts -Wno-error=redundant-decls... yes
checking whether C compiler accepts -Wno-error=switch-default... yes
checking whether C compiler accepts -Wno-error=write-strings... yes
checking whether C compiler accepts -Wno-error=unused-parameter... yes
checking whether C compiler accepts -Wno-error=missing-field-initializers... yes
checking whether C compiler accepts -Werror=unknown-warning-option... (cached) no
checking whether the linker accepts -Wl,--as-needed... yes
checking whether the linker accepts -Wl,--as-needed... yes
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -Wl,-z,noexecstack... yes
checking whether the linker accepts -Wl,-z,noexecstack... yes
checking whether the linker accepts -Wl,--no-as-needed... yes
checking whether the linker accepts -Wl,--fatal-warnings... yes
checking whether the linker accepts -Wl,-fatal_warnings... no
checking whether the linker accepts -Wl,--no-as-needed... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating dbus-gmain/Makefile
config.status: creating dbus-python.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: error: in /tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/build/temp.linux-aarch64-3.8':   config.status: error: Something went wrong bootstrapping makefile fragments       for automatic dependency tracking.  Try re-running configure with the       '--disable-dependency-tracking' option to at least be able to build       the package (albeit without support for automatic dependency tracking).   See config.log' for more details
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py", line 85, in
setup(
File "/home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/lib/python3.8/site-packages/setuptools/init.py", line 145, in setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 223, in run
self.run_command('build')
File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py", line 56, in run
subprocess.check_call([
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/configure', '--disable-maintainer-mode', 'PYTHON=/home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/bin/python', '--prefix=/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/build/temp.linux-aarch64-3.8/prefix']' returned non-zero exit status 1.
ERROR: Failed building wheel for dbus-python
Running setup.py clean for dbus-python
Building wheel for pgi (setup.py) ... done
Created wheel for pgi: filename=pgi-0.0.11.2-py3-none-any.whl size=181783 sha256=53ef6f90963070274943f12da0004d8c2d25abf112f6bce1abbc8bd89dad045e
Stored in directory: /home/ubuntu/.cache/pip/wheels/17/ee/39/e8766b9714c8a5534fa309b8b2a64f358196d8b951e573a153
Successfully built pgi
Failed to build dbus-python
Installing collected packages: pgi, dbus-python, chip
Running setup.py install for dbus-python ... error
ERROR: Command errored out with exit status 1:
command: /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py'"'"'; file='"'"'/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-1orrdwrf/install-record.txt --single-version-externally-managed --compile --install-headers /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/include/site/python3.8/dbus-python
cwd: /tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/
Complete output (219 lines):
running install
running build
creating /tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/build
creating /tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/build/temp.linux-aarch64-3.8
checking whether make supports nested variables... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define EXTENSIONS... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... no
checking whether make supports the include directive... no
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking dependency style of gcc... none
checking build system type... aarch64-unknown-linux-gnu
checking host system type... aarch64-unknown-linux-gnu
checking for native Windows host... no
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert aarch64-unknown-linux-gnu file names to aarch64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert aarch64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for inline... inline
checking for gawk... (cached) gawk
checking for python... /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/bin/python
checking for a version of Python >= '2.1.0'... yes
checking for a version of Python >= '2.7'... yes
checking for the distutils Python package... yes
checking for Python include path... -I/usr/include/python3.8
checking for Python library path... -L/usr/lib -lpython3.8
checking for Python site-packages path... /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/lib/python3.8/site-packages
checking python extra libraries... -lcrypt -lpthread -ldl  -lutil -lm -lm
checking python extra linking flags... -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
checking consistency of all components of python development environment... yes
checking for python version... 3.8
checking for python platform... linux
checking for python script directory... ${prefix}/lib/python3.8/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python3.8/site-packages
checking python module: sphinx... no
checking python module: sphinx_rtd_theme... no
checking for dbus-run-session... /usr/bin/dbus-run-session
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DBUS... yes
checking for GLIB... yes
checking whether C compiler accepts -Werror=unknown-warning-option... no
checking whether C compiler accepts -Wno-suggest-attribute=format... yes
checking whether C compiler accepts -fno-strict-aliasing... yes
checking whether C compiler accepts -Wdeprecated-declarations... yes
checking whether C compiler accepts -Wno-duplicated-branches... yes
checking whether C compiler accepts -Wno-inline... yes
checking whether C compiler accepts -Wno-redundant-decls... yes
checking whether C compiler accepts -Wno-switch-default... yes
checking whether C compiler accepts -Wno-write-strings... yes
checking whether C compiler accepts -Wnested-externs... yes
checking whether C compiler accepts -Wmissing-prototypes... yes
checking whether C compiler accepts -Wstrict-prototypes... yes
checking whether C compiler accepts -Wdeclaration-after-statement... yes
checking whether C compiler accepts -Wimplicit-function-declaration... yes
checking whether C compiler accepts -Wold-style-definition... yes
checking whether C compiler accepts -Wjump-misses-init... yes
checking whether C compiler accepts -Wall... yes
checking whether C compiler accepts -Wextra... yes
checking whether C compiler accepts -Wundef... yes
checking whether C compiler accepts -Wwrite-strings... yes
checking whether C compiler accepts -Wpointer-arith... yes
checking whether C compiler accepts -Wmissing-declarations... yes
checking whether C compiler accepts -Wredundant-decls... yes
checking whether C compiler accepts -Wno-unused-parameter... yes
checking whether C compiler accepts -Wno-missing-field-initializers... yes
checking whether C compiler accepts -Wformat=2... yes
checking whether C compiler accepts -Wcast-align... yes
checking whether C compiler accepts -Wformat-nonliteral... yes
checking whether C compiler accepts -Wformat-security... yes
checking whether C compiler accepts -Wsign-compare... yes
checking whether C compiler accepts -Wstrict-aliasing... yes
checking whether C compiler accepts -Wshadow... yes
checking whether C compiler accepts -Winline... yes
checking whether C compiler accepts -Wpacked... yes
checking whether C compiler accepts -Wmissing-format-attribute... yes
checking whether C compiler accepts -Wmissing-noreturn... yes
checking whether C compiler accepts -Winit-self... yes
checking whether C compiler accepts -Wredundant-decls... (cached) yes
checking whether C compiler accepts -Wmissing-include-dirs... yes
checking whether C compiler accepts -Wunused-but-set-variable... yes
checking whether C compiler accepts -Warray-bounds... yes
checking whether C compiler accepts -Wreturn-type... yes
checking whether C compiler accepts -Wswitch-enum... yes
checking whether C compiler accepts -Wswitch-default... yes
checking whether C compiler accepts -Wduplicated-cond... yes
checking whether C compiler accepts -Wduplicated-branches... yes
checking whether C compiler accepts -Wlogical-op... yes
checking whether C compiler accepts -Wrestrict... yes
checking whether C compiler accepts -Wnull-dereference... yes
checking whether C compiler accepts -Wdouble-promotion... yes
checking whether C compiler accepts -Wno-error=duplicated-branches... yes
checking whether C compiler accepts -Wno-error=inline... yes
checking whether C compiler accepts -Wno-error=redundant-decls... yes
checking whether C compiler accepts -Wno-error=switch-default... yes
checking whether C compiler accepts -Wno-error=write-strings... yes
checking whether C compiler accepts -Wno-error=unused-parameter... yes
checking whether C compiler accepts -Wno-error=missing-field-initializers... yes
checking whether C compiler accepts -Werror=unknown-warning-option... (cached) no
checking whether the linker accepts -Wl,--as-needed... yes
checking whether the linker accepts -Wl,--as-needed... yes
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether the linker accepts -Wl,-z,noexecstack... yes
checking whether the linker accepts -Wl,-z,noexecstack... yes
checking whether the linker accepts -Wl,--no-as-needed... yes
checking whether the linker accepts -Wl,--fatal-warnings... yes
checking whether the linker accepts -Wl,-fatal_warnings... no
checking whether the linker accepts -Wl,--no-as-needed... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating dbus-gmain/Makefile
config.status: creating dbus-python.pc
config.status: creating config.h
config.status: executing depfiles commands
config.status: error: in /tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/build/temp.linux-aarch64-3.8':     config.status: error: Something went wrong bootstrapping makefile fragments         for automatic dependency tracking.  Try re-running configure with the         '--disable-dependency-tracking' option to at least be able to build         the package (albeit without support for automatic dependency tracking).     See config.log' for more details
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py", line 85, in
setup(
File "/home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/lib/python3.8/site-packages/setuptools/init.py", line 145, in setup
return distutils.core.setup(attrs)
File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/lib/python3.8/site-packages/setuptools/command/install.py", line 61, in run
return orig.install.run(self)
File "/usr/lib/python3.8/distutils/command/install.py", line 589, in run
self.run_command('build')
File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py", line 56, in run
subprocess.check_call([
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/configure', '--disable-maintainer-mode', 'PYTHON=/home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/bin/python', '--prefix=/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/build/temp.linux-aarch64-3.8/prefix']' returned non-zero exit status 1.
----------------------------------------
ERROR: Command errored out with exit status 1: /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py'"'"'; file='"'"'/tmp/pip-install-vs_8gjp3/dbus-python_0d18bc5798974885b2ed8594239d89d2/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-1orrdwrf/install-record.txt --single-version-externally-managed --compile --install-headers /home/ubuntu/chipCode/chip_0121/connectedhomeip/.environment/pigweed-venv/include/site/python3.8/dbus-python Check the logs for full command output.

Close the issue , for raspi we need to install pydbus. Verified both on Ubuntu desktop and server raspi.

Close the issue , for raspi we need to install pydbus. Verified both on Ubuntu desktop and server raspi.

repo: project-chip/connectedhomeip


text:
[CI] Disable TestDiscovery

Problem
It seems like the CI workload on Darwin is making TestDiscovery.yaml failing a lot.
Change overview

Disable it until I found a proper way to fix it

@vivien-apple - is this on darwin only ? Darwin CI seems flaky, but linux seems more stable.

Yes @andy31415 there's cross talk.
@vivien-apple said he'd have a better fix for this tomorrow, but this will unblock CI for now.

source: gharchive/pull-request

authors: andy31415 vivien-apple woody-apple

license_type: permissive

license_source: github-api


text:
Move out the weak functions of MatterGetAccessPrivilegeFor_XX

Problem
#19706
The MatterGetAccessPrivilegeFor_XX in the src/app/util/privilege-storage.cpp sometimes does not override the weak functions in src/app/RequiredPrivilege.cpp. Looks like we call the GetAccessPrivilege functions only in the included header file src/app/RequiredPrivilege.h. As described in #20538 , the linker might just link the first found (weak) function codes and will not link the strong functions in another file objects anymore.
Change overview
Move the weak functions out of the src/app/RequiredPrivilege.cpp.
Testing
CI

Close since #21220 merged


text:
Add endpoint 0 on the all-clusters-app

Problem
The all-clusters-app endpoints count currently starts from 1. This PR add a endpoint 0 and
activate some clusters on it:

Basic
Descriptor
General Commissioning
Binding
Group Key Management
Network Commissioning

The main reason to do it is because the Descriptor cluster for endpoint 0 as a special
behavior, where it list all the endpoints on the node.
Summary of changes

Add endpoint O to all-clusters-app.zap
Activate required clusters on it
Deactivate some clusters on other endpoints since they are now turned on on the endpoint 0
Regen the gen/ folder

@vivien-apple conflict here.
@saurabhst @msandstedt ?

Snif. CI is broken because someone has again forgotten to land some changes generated from the templates. I really need to finish #5459.

@vivien-apple please fix the style issue

@vivien-apple please fix the style issue

@yufengwangca I'm not sure what to do here. I have already force-pushed twice to trigger the restyler but it seems to not run. That's strange since it seems to be the same issue with https://github.com/project-chip/connectedhomeip/pull/6059

@vivien-apple removed restyled-ignore tag, could you rebase your branch to the tot of master and do another force push?

authors: vivien-apple woody-apple yufengwangca


text:
api package name change

Current behavior:
api package name is "ruleapi" which in an import looks redundant: github.com/project-flogo/rules/ruleapi
Expected behavior:
I think "github.com/project-flogo/rules/api" would look cleaner
What is the motivation / use case for changing the behavior?
Additional information you deem important (e.g. I need this tomorrow):

The code may look a bit odd like api.NewRule "ruleapi." makes is clearer, though there is stutter in the import statement

You can always alias the import to ruleapi if you think it makes the code looker cleaner:
import (
...
ruleapi "github.com/project-flogo/rules/api"
)

I think its important to have a clean import path.

The end user facing api looks better off with ruleapi than simply api. Yes, an alias can work here. But then it becomes optional for end user to use an alias.
Another cleanup candidate is ruleaction for a flogo action can simply be action.

@vpatil-tibco I'm not sire I agree with you. rules/ruleapi is a bit redundant, obviously its an api for rules when its nested under that package. Perhaps calling it something different, all together? Secondly, an alias being optional is fine, the dev can alias it to whatever makes sense for them.

@mellistibco I agree to the base issue logged by @fm-tibco
But from an oob usage perspective, i feel ruleapi.NewRule looks cleaner than api.NewRule. Also my take on this comes from the fact that i haven't encountered an user facing api package, there might be just that i haven't come across one.
So really 2 options, if we are all ok with api then use that else find a better package name.

Closing this - lets keep it as ruleapi itself

source: gharchive/issue

authors: balamg fm-tibco mellistibco vpatil-tibco

repo: project-flogo/rules


text:
Implement registration-retry with exponential backoff

Pull request for Implement registration-retry with exponential backoff #118

I'm not sure if we want this TBH, exponential backoff is ok, but a device can take too much time on that. Also, the flow will change when https://github.com/project-flotta/flotta-operator/pull/179 got merged, and I can finish the work on this:
https://github.com/project-flotta/flotta-device-worker/pull/128
So not sure if it something that we should spend time here.

I'm not sure if we want this TBH, exponential backoff is ok, but a device can take too much time on that. Also, the flow will change when project-flotta/flotta-operator#179 got merged, and I can finish the work on this: #128
So not sure if it something that we should spend time here.

The change in the workflow that would impact the usefulness of this issue is that the device will first create enroll request, so it will be known by the system and then, the admin user can approve the enrollment. Meaning that the device is already UP so the registration should not fail much time so it won't be necessary to have exponential retries as we would not save any relevant resources.
Correct?

Yup, no registration will happens at all.

authors: eloycoto gabriel-farache

repo: project-flotta/flotta-device-worker


text:
Sources filter functionality

Describe the bug
There are some issues with filtering for the new sources page.

There is no results row when a filter is applied. As a user, I'm expecting to clear filters similarly to the details pages. Currently, the only way to clear a filter is to delete the previous filter string and press enter.

The filter does not accept partial strings. This could be an issue for the back-end API to solve. (In that case, please file an issue with koku.) However, I could not match "hccm", only exact matches (e.g., "hccm-vmware") are found.

To Reproduce
Steps to reproduce the behavior:

Go to 'Overview'
Click on 'Add Sources'
Enter a filter such as 'hccm'
See error

Expected behavior
As a user, I should be able to clear individual filters. I should also be able to add partial filters.
Screenshots
Partial string:

Full String:

Additional context
See https://docs.google.com/document/d/1_t1dV00l9j529vSWduzAkqtnGlLtlFE7e8zidylkGKo/edit?ts=5ca4eef3

@nlcwong @dlabrecq @dayleparker
Current state:

[x] filter does accept partial strings: name=boaz will return any source that contains "boaz" in its name
[x] filter does "AND" on type and name: name=boaz&type=OCP will return all OpenShift sources that contain "boaz" in their name
-[ ] filter does "OR" on name/type: name=[boaz,david] will return all sources that their names contain "boaz" or "david" (e.g. david-1, 1-boaz-david, david-boaz, boaz-23, davidistheman).

repo: project-koku/koku-ui


text:
Update Dashboard to Match High Fidelity Mockups

User Story
Impacts
UI
UI Details
Need to update the look of the dashboard to match the mockup here: https://redhat.invisionapp.com/share/BJN9KGLTUD8#/screens
Acceptance Criteria

[ ] Dashboard cards match the high fedelity mockups.

I believe this can be closed as #78 was merged


text:
lang: Build should error when PDA payer is not marked mutable

We should be able to parse the accounts at compile time and inspect the payer field to ensure it's marked mutable, giving the developer a more informative error than the current Cross-program invocation with unauthorized signer or writable account.

-> Anchor should check that the Payer is both mutable and a Signer at compile time to avoid this issue.
Ran into this problem earlier when executing an instruction with CPI using Multisig Program. This mutable/signer check does not show up when executed with the Anchor client, so some discrepancy there.

closed by https://github.com/project-serum/anchor/pull/1271

authors: armaniferrante iurage paul-schaaf

repo: project-serum/anchor


text:
Remove usage of deprecated package pkg/errors

The project has looking for maintainers, and was later archived.
See https://github.com/pkg/errors/issues/245

Closing as solved in #1262

authors: andaaron nicoldr

repo: project-zot/zot


text:
Add default styling for castgroup with braces

@martindholmes The encoding pattern isn't quite what I had on the whiteboard. To make the three containers, I've put a castGroup inside the castGroup element. Then we can style the child castGroup as a simple list. The second container is the metamark. The third container is the roleDesc.
You'll find this encoding in lemdo/data/texts/douai/main/emdDouai_Mac.xml
<castGroup>
              <castGroup>
                  <castItem xml:id="emdDouai_Mac_malcolm">
                  <role>Malcolme</role>
              </castItem>
             <castItem xml:id="emdDouai_Mac_donalbain">
                <role>Donalbaine</role>
              </castItem>
              </castGroup>
            <metamark>}</metamark>
           <roleDesc>his sons</roleDesc>
          </castGroup>

Reassign to @LEMDO-PM for documentation after we have a plan.

I don't think we should really do default styling for this, because every case will be different. I think we have to supply the style on a case-by-case basis, no?

This is what I've gone with in this case, slightly modifying the encoding:
<castGroup style="display: flex; flex-direction: row; align-items: center;">
    <castGroup>
        <castItem xml:id="emdDouai_Mac_malcolm">
            <role>Malcolme</role>
        </castItem>
        <lb/>
        <castItem xml:id="emdDouai_Mac_donalbain">
            <role>Donalbaine</role>
        </castItem>
    </castGroup>
    <metamark style="transform: scaleY(3); transform-origin: center; margin: 0 1em;">}</metamark>
    <roleDesc>his sons</roleDesc>
</castGroup>

So what we're saying is: there's a row of three items, a castGroup, a metamark, and a roleDesc; they are vertically-aligned to the center; there's a line break between the two cast items; and the parenthesis is stretched. This is fairly plain and comprehensible, and it gives us the required output.

I think this is probably now a documentation issue; we have a good, simple, working example, and with documentation people can easily follow it.

authors: JanelleJenstad martindholmes

repo: projectLEMDO/lemdoIssues

license: MIT


text:
plugins: don't pass namespace arg to OSBS methods

Blocked by:

projectatomic/osbs-client#334
bkabrda/flexmock#14 (need to wait for new release so that we may use it on Travis)

Ready to merge.

I think there are two useful things to do:

pass namespace to the Configuration constructor
stop passing namespace to the various API functions

The first one makes sense to do now, whlie the second one introduces incompatible behaviour (i.e. requires newer osbs-client in order to work the same).

You're right. Will update the patch.

I've updated the patch to only pass namespace to Configuration constructor.
When/how we should do the other thing?

LGTM
So now atomic-reactor will work correctly with osbs-client versions since https://github.com/projectatomic/osbs-client/pull/334 when using a non-default namespace.
I guess we don't want to stop passing namespace keyword arguments to API calls until there's no chance of using an osbs-client version older than when the namespace change was pulled in. Before that change, the namespace configuration parameter was ignored. :-(

lgtm, very nice work Martin!

I think we should merge this and open a new issue to track the removal of namespace keyword arguments for API functions.

So, this PR is no longer blocked by the osbs-client change. What about flexmock?

Travis has the new flexmock so the test here pass. The test also pass on my machine with the old flexmock, which is sorta weird ... whoever is going to review it, can you perhaps run the tests first (under Python 3) and let me know if they don't pass?

Running py.test-3 tests with python-flexmock-0.9.7-2.fc23 here gives failures:
tests/plugins/test_check_and_set_rebuild.py FFFFFF
tests/plugins/test_import_image.py ....FFF.F...
tests/plugins/test_store_metadata.py FF

LGTM, merging.

Thanks! The tests should pass with python-flexmock-0.10.2-1.fc23, soon to be in updates-testing.

authors: TomasTomecek mmilata twaugh

repo: projectatomic/atomic-reactor

license_source: bigquery


text:
Initial imagebuilder buildstep plugin

Introduces an alternate method for running the docker build with imagebuilder. Can be configured with the following in reactor-config-map:
default_image_build_method: imagebuilder
Or per repo in container.yaml:
override_image_build: imagebuilder
A scratch build of imagebuilder for testing in the buildroot is available at http://download.eng.bos.redhat.com/brewroot/work/tasks/7796/15977796/imagebuilder-0.0.1-1.git.0.71d05b5.el7.x86_64.rpm
Commits are structured to review individually.

One other thing to bring up about this implementation: as nothing was validating container.yaml with schema before, users could see new failures to read their existing container.yaml once this is rolled out. That is one reason only the new property is actually using the new SourceConfig reader; the others are continuing to roll their own yaml reading. A failure in the SourceConfig reader just means that the config is considered empty and there are errors logged, so only the new property is affected by the schema validation. I think it would be best if everything reading container.yaml did it via SourceConfig eventually but didn't want to make that change immediately. Feedback welcome however.

Yes, I'm in favour of validation everywhere.

Added commits (currently last 4) to address feedback and rebased. Schema validation is applied everywhere and can fail the build. PTAL :)

Very well done!

Updated release notes draft:

New container build plugin using imagebuilder with ability of choosing default approach per environment, as well as, per repository.

@sosiouxme Can you refresh the imagebuilder rpm link? I'm getting a 404...

authors: ben-alkov lcarva sosiouxme twaugh


text:
Look for default config file and helper exec file in source dir first

We put all defaults in container-storage-setup.conf and look for this
file in /usr/lib/container-storage-setup. Instead first look for this
file in source dir where container-storage-setup is present and if not
found look in /usr/lib/
It solves one main problem that is one does not have to do "make install"
to test the code. Everything needed is available in source code itself.
It also helps if during code development, if one introduces a new default
variable, then without doing "make install" one can test their code.
During migration from docker-storage-setup to container-storage-setup also
it continues to work. Otherwise without this change, script can't find
container-storage-setup.conf in /usr/lib/container-storage-setup/ and
breaks down.
Signed-off-by: Vivek Goyal vgoyal@redhat.com

@rhatdan PTAL

I am not sure why tests are not kicking in.

@jlebon it took almost 3 mins for tests to kick in. Is it expected.

LGTM

@rh-atomic-bot r+ 6bd7557

authors: rhatdan rhvgoyal

repo: projectatomic/container-storage-setup


text:
Quickstart documentation is incorrect

Expected Behavior

The quickstart guide provides working instructions.
Current Behavior

Looking at the Getting Started guide in the section for kubernetes requirements it says Calico is tested with k8s 1.24 and newer. In the section immediately after that it says to provide the --network-plugin=cni flag to the kubelet however this cannot work as that flag was removed in 1.24 as per: https://github.com/kubernetes/kubernetes/pull/106907
What is the correct way of providing this configuration in a world with k8s 1.24 or newer And with something like containerd?

I think the quickstart doc is correct, and has the exact commands you need in it.https://docs.tigera.io/calico/latest/getting-started/kubernetes/quickstart

@ctauchen A docs bug for you

@lwr20 @ctauchen I don't see a linked fix - is this one closeable?

Fixed with https://github.com/tigera/docs/pull/790

authors: caseydavenport ctauchen lwr20 rbjorklin

repo: projectcalico/calico


text:
Changes for Calico v3.9.1

[ ] Tests
[ ] Documentation
[ ] Release note

None required

Deploy preview for calico ready!
Built with commit 8c0fba3d198f4eed7b31f4d4513120c3de68ca95
https://deploy-preview-2884--calico.netlify.com


text:
malformed HTTP Response

Bug description
When I'm using the following command:
kubectl get ns --kubeconfig=alice-oil-oil.kubeconfig --insecure-skip-tls-verify

I get the following error message: Unable to connect to the server: malformed HTTP response "\x00\x00\x12\x04\x00\x00\x00\x00\x00\x00\x03\x00\x00\x00\x80\x00\x04\x00\x01\x00\x00\x00\x05\x00\xff\xff\xff\x00\x00\x04\b\x00\x00\x00\x00\x00\x7f\xff\x00\x00\x00\x00\b\a\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01"
How to reproduce
Run the create-user.sh script using alice-oil as the first and oil as the second parameter.
Create a tenant which is owned by the user alice-oil.
Install capsule-proxy with the following helm command:
helm upgrade --install capsule-proxy projectcapsule/capsule-proxy \
   --namespace capsule-system \
   --set crds.install=true \
   --set ingress.enabled=true \
   --set ingress.className="nginx" \
   --set ingress.hosts[0].host="capsule.mh.com" \
   --set ingress.hosts[0].paths[0]="/" \
   --set ingress.tls[0].secretName="capsule-proxy-tls" \
   --set ingress.tls[0].hosts[0]="capsule.mh.com" \
   --set certManager.issuer.name="self-signed" \
   --set certManager.issuer.kind="ClusterIssuer" \
   --set certManager.generateCertificates=true \
   --set ingress.annotations."nginx\.ingress\.kubernetes\.io/backend-protocol"="HTTPS" \
   --set ingress.annotations."nginx\.ingress\.kubernetes\.io/force-ssl-redirect"='"true"' \

Set https://capsule.mh.com as the proxy-url in the alice-oil-oil.kubeconfig.
NOTE: Make sure to use a host which can be resolved by your system e.g. capsule.mh.com is probably not resolving on your system.
Expected behavior
I expected to be able to create the namespace like in the usual manner.
Logs
If applicable, please provide logs of capsule.
In a standard stand-alone installation of Capsule,
you'd get this by running kubectl -n capsule-system logs deploy/capsule-proxy.
Additional context
# capsule-proxy ingress rule

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    meta.helm.sh/release-name: capsule-proxy
    meta.helm.sh/release-namespace: capsule-system
    nginx.ingress.kubernetes.io/backend-protocol: HTTPS
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
    nginx.ingress.kubernetes.io/ssl-passthrough: "false"
  creationTimestamp: "2024-12-05T11:12:14Z"
  generation: 1
  labels:
    app.kubernetes.io/instance: capsule-proxy
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: capsule-proxy
    app.kubernetes.io/version: 0.8.0
    helm.sh/chart: capsule-proxy-0.8.0
  name: capsule-proxy
  namespace: capsule-system
  resourceVersion: "352513"
  uid: ba2d2be4-f706-4802-9d0d-ff2455dd6a99
spec:
  ingressClassName: nginx
  rules:
  - host: capsule.mh.com
    http:
      paths:
      - backend:
          service:
            name: capsule-proxy
            port:
              number: 9001
        path: /
        pathType: ImplementationSpecific
  tls:
  - hosts:
    - capsule.mh.com
    secretName: capsule-proxy-tls
status:
  loadBalancer:
    ingress:
    - ip: 192.168.56.100

Capsule-Proxy version: latest
Helm Chart version: capsule-proxy-0.8.0     app-version: 0.8.0
Kubernetes version:
Client Version: v1.31.1
Kustomize Version: v5.4.2
Server Version: v1.31.1

Thanks for the report, @naivary.
May I ask you if you're using a token-based authentication, or relying on the client-certificate one?
Furthermore, how do you ensure NGINX uses the right certificate for the TLS connection to the upstream servers? AFAIK, you should specify one.

I'm using a client-certificate one e.g. X.509 certificate via the script. How should I specify the correct certificate?

Unfortunately, it wouldn't work: you're performing a TLS termination at the Ingress Controller, and the client certificates are not proxy-passed to the upstream servers.
You have multiple options here:

TLS/SSL passthrough to Capsule Proxy (and client certificate auth will work)
TLS/SSL termination at the Ingress Controller, and proxy pass to plain HTTP with Bearer Token
TLS/SSL termination at the Ingress Controller, and upstream to Capsule Proxy in HTTPS (this is the most challenging, and however, you'll lose client-certificate authentication)

I will try it! Thank you. You got any sources for the first option? I'm using a nginx ingress controller

I configured my nginx ingress controller to allow SSL Passthrough and used int for the ingress rule too but still get the same error.
Using the following kubeconfig:
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURCVENDQWUyZ0F3SUJBZ0lJWmNaaW1JQ0Q5VDB3RFFZSktvWklodmNOQVFFTEJRQXdGVEVUTUJFR0ExVUUKQXhNS2EzVmlaWEp1WlhSbGN6QWVGdzB5TkRFeE1USXhNekkyTURGYUZ3MHpOREV4TVRBeE16TXhNREZhTUJVeApFekFSQmdOVkJBTVRDbXQxWW1WeWJtVjBaWE13Z2dFaU1BMEdDU3FHU0liM0RRRUJBUVVBQTRJQkR3QXdnZ0VLCkFvSUJBUURMUXI1ZkpWREhDOE9nY0lyYzlWUzlkT0ZxdDVzSjI5NGhsdis2ajhKV0tMaTU0T3J2K3gvSUp6ejgKanQ2WmNMOERoaGtlMkdFQnE5SVV6dHAxNlhiSjZQb3FidTdmSUlSSm1iY1pldWJ5MHo4eTJTNFZ6RzFVdWQrWQpESytyOU1GNEJITUozUjdOOHh1QmtoWDdFa0tZd0p0dnlHSUFROGdveVV2Q1lQN3hFSUp0ZTE5S3F0K1l4Wm1yClFET0lyaWJTNXVNRzFpYXZhZ0V3V2JSNkE1QUkvVVgrNzBaTmVQdlJHT2JOQXZQUFBxZE1pakxoUlJNYTg4OUQKZ1duY2hBcU42czBuc1RjRWdnMVIrOCtvOWRYL00rY3ZtQmEwbk82U3hwb2E1OUFxeTlyNXkzU1o3RDc3MVJPTApSYmhRSlZBUGdvL25CQ0I0b3J3UzRTWlM0dk85QWdNQkFBR2pXVEJYTUE0R0ExVWREd0VCL3dRRUF3SUNwREFQCkJnTlZIUk1CQWY4RUJUQURBUUgvTUIwR0ExVWREZ1FXQkJRR3hCTEVESkpSTjNCeU53Vnh3VEhuaFAwdkRqQVYKQmdOVkhSRUVEakFNZ2dwcmRXSmxjbTVsZEdWek1BMEdDU3FHU0liM0RRRUJDd1VBQTRJQkFRQzVoZURWdzc5VgptYmMxeG1KZVJrdkVIUnpLbDU0YW5ObjBDZ3ZLQ2tJVWxibWgyZE9JbVUza3M4RU83VEFBcTlDUDZvckdvS0VZCnJFTU9VUGRmRUdNOTVMeXpxanlPWUFaejYzZHdBZGJNb01NRkJRZ2FXZzZUeE41enBkRnRldGFEMlhEWXlPK0IKYXZZcEc4WStRYzVvbHZqQU84OW05RFV5UGM1MEtpNnh5TlBlOFA5Wldnb3NWUkFxdzdRb3p4ZHNFOTMzVkxJegpWVk1pT25nOExJQ3hNc0oyeVdrSEpTRkxLdmpvdkprTnA3Ym1heFlrNVFCSGQ0WHR3Tk1GeExNSHdyMFcyNGhQCi9rM1RYUE13RGxoZThNQ052WDFiTVA0NmxEYkZCc2cwLzQ0NGlhbXNncG1CMVN3OFhleEc3YytlNThRc3J1alEKOVhiaWpudTlLYXAwCi0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K
    proxy-url: https://capsule.mh.com
    server: https://192.168.56.61:6443
  name: cluster.local
contexts:
- context:
    cluster: cluster.local
    user: alice-oil
  name: alice-oil-oil
current-context: alice-oil-oil
kind: Config
preferences: {}
users:
- name: alice-oil
  user:
    client-certificate: alice-oil-oil.crt
    client-key: alice-oil-oil.key

I solved the issue.
For nobody running into the same problem:

Make sure that your ingress controller has ssl-passthrough option turned on
Set the SSL-Passthrough for the ingress rule which is getting generated by capsule-proxy
Change the server option in used kubeconfig to the host of the capsule-proxy ingress rule.

Thanks for sharing the solution, and glad you get it sorted out on your own!

authors: naivary prometherion

repo: projectcapsule/capsule-proxy


text:
install error

hlo sir sandep bhai ,
when i try to innsall asnmap and mapcidr  . i always get same error,
package errors is not in std (/usr/lib/go/bin/src/errors)
package bufio is not in std (/usr/lib/go/bin/src/bufio)
package crypto/tls is not in std (/usr/lib/go/bin/src/crypto/tls)
package encoding/json is not in std (/usr/lib/go/bin/src/encoding/json)
plzz help

and my go env
export PATH=$PATH:/usr/local/go/bin
export GOPATH=/home/rahul/go/bin
#export GOBIN=$GOPATH/bin
#export PATH=$PATH:$GOBIN
export GOROOT=/usr/lib/go/bin

Your environment variables seem to be set incorrectly. Here's how you should set them:

GOROOT should point to the location where Go is installed. For a default installation, this is usually /usr/local/go.
GOPATH should point to your workspace directory, not the bin directory. If your workspace is in /home/rahul/go, then GOPATH should be set to that.
GOBIN should be set to the bin directory inside your workspace, i.e., $GOPATH/bin.

repo: projectdiscovery/asnmap


text:
Feat errkit

Proposed Changes

errkit is new go package that aims to be replacement of existing err packages, it is built upon from experiences and issues of errorutil and is drop in replacement for many known popular packages errors github.com/pkg/errors go.uber.go/multierr and fits well in existing error package style/ecosystem

https://github.com/projectdiscovery/utils/blob/389764fb85e2f64490474159c4a2b5aad4a7b51e/errkit/README.md?plain=1#L1-L58

@Mzack9999 , merging it now because to test this in other projects of pdcp , a new release is necessary since there is a conflicting version upgrade between shuffledns(uses latest version) vs current one( is based out on previous version not latest)
if you find any bugs/issues we can fix that in follow up PR 😄

repo: projectdiscovery/utils


text:
RS display problem

hello, I have been using Sondehub for almost 3 years, but for about 8 days we have noticed a very big slowdown in the display of the RS and this on 3 PCs, 1 Tablet, and 1 Phone, it becomes very difficult to be able to follow a probe, and we are 5 people to have the same problem, the BETA version works perfectly well before, well done and thank you for your work

Thanks for the report @14ri004 . We are looking into options to resolve this, it seems to be regression from when we switched to websockets. Do you happen to know if this is a CPU, Memory or Network limitation?

hello, we've been doing it for about 8 days, it's lagging, very slow screen display, see blocked, the processor is running at maximum, with the BETA version everything was perfect, I use Intel Core 2 duo 2.0Ghz and 2.8Ghz, friends use I5 and I7 and the problem is the same, before the probe appears on the Sondehub screen, it happens 5 to see 10mn and whatever the internet connection and the PC used, I hope you find the solution, and thank you for your help.

Thanks for the information @14ri004 . as a work around, if you know the serial number for the radiosonde you can filter the website to just that serial, eg : https://sondehub.org/#!q=T0440081

The problem is that we cannot get the number, the probe is not visible on SondeHub, otherwise yes I know the manipulation, as long as there are not many websock messages, c  'is OK, but from 200/300 finished no longer possible to display the new probes, today after 1h30 and multiple restart of SondeHub, the probes that I wanted to follow were still invisible.

Hi @14ri004 I just pushed some changes to our testing branch that might help you out. Can you check https://testing.v2.sondehub.org when the next radiosonde is released and report back if this resolves your issue?

hello, yes ok we will do the tests and I will come back to you to inform you of the result, thank you

perfect, we tested the test probehub with 4 people? and the detection as well as the navigation in the page was very good, no more slowing down like yesterday, thank you

Thanks for the feedback :)

repo: projecthorus/sondehub-tracker


text:
Portal does not keep host alive

If you have the portal open for a while without any activity and then you go and edit a script, it is quite likely that the script change will not be picked up, because the host has gone idle. You hit the save button and it goes blue, but nothing appears in the logs about your changes being detected.
I believe there are a number of similar cases that can come up, where actions in the portal do not feel like they are working correctly because the host is not running. The most direct solution is to make sure that the portal keeps the host alive.

Dup of #79, which is supposed to have been fixed.

authors: davidebbo paulbatum

repo: projectkudu/WebJobsPortal


text:
httpPlatformHandler path is overwritten during deploy on Azure

I have a web.config somewhere in sub-app's wwwroot/ with
        <handlers>
            <add name="httpplatformhandler" path="/api/*" verb="*" modules="httpPlatformHandler" resourceType="Unspecified" />
        </handlers>

after the kudu_sync everything else in this file is kept (and copied over to the correct wwwroot) but the httpPlatformHandler is replaced with
        <handlers>
            <add name="httpplatformhandler" path="*" verb="*" modules="httpPlatformHandler" resourceType="Unspecified" />
        </handlers>

losing the "api" part which breaks delivery of the static content which is configured in
    <system.web>
        <compilation debug="true" targetFramework="4.0" />
        <httpHandlers>
            <add verb="*" type="Nancy.Hosting.Aspnet.NancyHttpRequestHandler" path="api/*"/>
            <add verb="*" type="System.Web.StaticFileHandler" path="*"/>
        </httpHandlers>
    </system.web>

The question is am I misusing the handler or not using the kudu correctly? The third option would be a bug in kudu.

Note that Kudu just uses standard dotnet/msbuild commands, and doesn't have its own logic for these transforms. So my guess is that you'd see the same behavior locally if you ran the same commands.
You can go to Kudu Console and download the deployment script from the Tools menu, which will help you investigate.

ah. right. it's dnu publish not kudu.
thanks!
case closed.

authors: davidebbo durilka

repo: projectkudu/kudu


text:
Unable to install with projectriff/kafka instance.

I have a cluster thats empty and healthy:
[ec2-user@ip-10-0-0-28 ~]$ kubectl get -n riff-system all
No resources found.

install the single node kafka ( helm install --name riff-kafka --namespace riff-system projectriff/kafka)and confirm its running
NAME                                    READY     STATUS    RESTARTS   AGE
riff-kafka-kafka-5f96b558bc-d5zwq       1/1       Running   0          1m
riff-kafka-zookeeper-56dd5fd86d-h4nvs   1/1       Running   0          1m

Then install riff per the GettingStarted docs (helm install projectriff/riff --name projectriff --namespace riff-system --set kafka.create=true --set rbac.create=false)
The HTTP gateway and topic controllers never successfully start:
[ec2-user@ip-10-0-0-28 ~]$ kubectl get -n riff-system po
NAME                                                   READY     STATUS             RESTARTS   AGE
projectriff-riff-function-controller-b4849f776-dmsfq   1/1       Running            0          31s
projectriff-riff-http-gateway-7dbdc9cd48-29hs8         0/1       CrashLoopBackOff   2          31s
projectriff-riff-topic-controller-8567cc4d66-shz2d     0/1       CrashLoopBackOff   2          31s
riff-kafka-kafka-5f96b558bc-d5zwq                      1/1       Running            0          3m
riff-kafka-zookeeper-56dd5fd86d-h4nvs                  1/1       Running            0          3m

With logs that look like this:
[ec2-user@ip-10-0-0-28 ~]$ kubectl logs  -n riff-system projectriff-riff-http-gateway-7dbdc9cd48-29hs8
panic: kafka: client has run out of available brokers to talk to (Is your cluster reachable?)

goroutine 1 [running]:
main.main()
        /go/src/github.com/projectriff/riff/http-gateway/cmd/http-gateway.go:37 +0x3fe

Is this a doc error for the getting started, or something more?

Upon further review - it appears that the issue is the name of the kafka install has to be transport.
[ec2-user@ip-10-0-0-28 ~]$ kubectl get -n riff-system po
NAME                                                   READY     STATUS    RESTARTS   AGE
projectriff-riff-function-controller-b4849f776-4thxr   1/1       Running   0          45s
projectriff-riff-http-gateway-7dbdc9cd48-bzbq4         1/1       Running   0          45s
projectriff-riff-topic-controller-8567cc4d66-dqkrf     1/1       Running   0          45s
transport-kafka-5bcbd48cf-zskqj                        1/1       Running   0          1m
transport-zookeeper-659c7cf898-l9m5k                   1/1       Running   0          1m

I'll fix the doc and send a PR.

@mcowger We just made a change just now to this behavior so that Kafka is installed via the projectriff chart. You should no longer need to install Kafka separately. It looks like you may have caught the small window between the PR being merged to master and the updated helm chart being available via our repository.
Try again and let us know how it goes.
Sorry about that.

We are in the middle of a change to the Helm chart and the docs for the next 0.0.6 release so the GettingStarted doesn't reflect the current 0.0.5 release.
If you want to install version 0.0.5 then follow https://github.com/projectriff/riff/blob/v0.0.5/Getting-Started.adoc
If you want to install the current 0.0.6-snapshot version then follow https://github.com/projectriff/riff/blob/master/Development-Helm-install.adoc

Indeed it does look like I hit that window :).
Using the Development instructions I was able to deploy correctly.   Feel free to drop the PR associated with this.

I noticed the helm delete --purge command used the wrong release name, fixed that to be projectriff in master now. Thanks for trying riff, just be aware that if you use the latest snapshot versions things could occasionally break.

authors: mcowger scothis trisberg

repo: projectriff/riff


text:
Can I add labels on dates?

I tried add the text to dates with JsonObject, but the text is empty.
class EventDecorator(jsonTotal: JSONObject, dates: HashSet<String>) : DayViewDecorator {
    val totalData = jsonTotal
    val dates: HashSet<String> = dates
    var dDay = ""
    var label = ""
    override fun shouldDecorate(day: CalendarDay): Boolean {
        dDay = getDay(day.year, day.month, day.day)
        label = totalData.getString(dDay)
        return dates.contains(dDay)
    }

    override fun decorate(view: DayViewFacade) {
        view.addSpan(DotSpan(5f, Color.RED))
        // view.addSpan(AddTextToDates(label))
    }

    fun getDay(year: Int, month: Int, day: Int): String {
        val dDay = "$year-" + String.format(
            "%02d",
            month + 1
        ) + "-" + String.format("%02d", day)
        return dDay
    }
}

I think you can use this guide to do it, but I don't know how to increase height of row to display this text. Maybe it will be overlap.
https://stackoverflow.com/questions/61008523/add-text-to-dates-in-material-calendarview


text:
Update build

Update Go to 1.21.
Update minimum Go version to 1.19.
Fixup deprecated io/ioutil.
Move errcheck excludes inline.

Hi, this is the first time I've contributed here but I don't think it's cool to close the MR without any info and open one in // for this.
We could have made this one evolve to reach the desired standard.
https://github.com/prometheus-community/ipmi_exporter/pull/169
Thanks in any case for the update.

Hello, it's possible to create a release ?

@jplanckeel Sure, would you like to help with this? You would need to edit the CHANGELOG.md and VERSION files.
We generally only list the user visible changes, not mechanical updates like Go versions or other maintenance PRs.

there have been quite a few version upgrades of GO and deps, this could be a good thing.  In addition, it would provide users with a tag other than latest or master for their production.
I'll prepare the MR for you. You're more in favor of a fix or minor bump

The PR : https://github.com/prometheus-community/ipmi_exporter/pull/173
Thank you 👍

authors: SuperQ jplanckeel


text:
Fix build problems

This will fix the errcheck problems, and it might have an impact on the go generate part.
It indeed looks like Circle somehow keeps GOPATH in the environment for external commands (via go generate or the errcheck command), while Travis somehow removes it or builds outside of it or whatever. More investigation needed, but this removes a few parts of the equation at least.

Same conclusion for me: one way or another, Travis CI changed something to their setup and it acts as if the project was outside of GOPATH. I noticed that it automatically exports GO111MODULE=auto too recently. I wish there was a changelog somewhere...

That's a lead... Still I don't quite get why the go generate part is affected in that way. If they still build within GOPATH, the GO111MODULE=auto should re-create the original go behavior. But somehow, it wants modules, but that doesn't seem to work in the sub dir... or something... Anyway, let's get this merged (on green) so that we have one less thing to distract us from the go generate problem.

@simonpasquier fine to merge this?

Since you closed #1748 in lieu if this, I guess yes. Just want to get master green again. Merging now...

Thanks for this @beorn7! I'll dig further to understand what has changed and broke...

repo: prometheus/alertmanager


text:
allow CORS for api GET and OPTIONS

Ideally I would also like to access POST and DELETE methods, but that probably doesn't make sense from a security perspective?

Thanks 👍

authors: fabxc vanesa


text:
Mounting in FastAPI's APIRouter doesn't expose anything

I've tried to use FastAPI's APIRouter & mount the ASGI app in the router, however the endpoint is not being exposed. It simply returns 404.

Assuming you mapped it to /metrics/ try doing curl yourapp/metrics/ instead of curl yourapp/metrics, the trailing slash matters

I actually mount it on /metrics and it's not available either with or without a trailing slash.

authors: RedKinda mdczaplicki


text:
cpuinfo: Enable for all 32-bit ARM CPUs

Repurpose the ARMv6 cpuinfo for all ARM CPUs. CPU info format likely is
not dependent on instruction set version.
Signed-off-by: Christian Svensson bluecmd@google.com
Fixes #291

This fixes the compilation for ARM 32-bit, but the current parsing code only works for kernels older than v3.8.
I think there is value to merging this while the format question is resolved - if nothing else to allow 32-bit ARM to build.
WDYT @discordianfish ?

One thing we could do here is to build a set of tests that run on different architectures/kernels. This could be done by adding to the buildkite setup we have for the node_exporter.
With buildkite, we run a few different build agents under KVM/QEMU, so we're not dependent on the limited platforms available on CircleCI.

Fixing the parsing itself can be done in another PR, so LGTM.

authors: SuperQ bluecmd discordianfish

repo: prometheus/procfs


text:
Missing MetricMetaData in Golang Package

What did you do?
I'm trying to convert Prometheus RemoteWrite requests to OpenTelemetry format. In the protoformat from the WriteRequest: https://github.com/prometheus/prometheus/blob/main/prompb/remote.proto
i see there is a MetricMetaData field. however if i check the golang package: https://pkg.go.dev/github.com/prometheus/prometheus/prompb#WriteRequest
i don't see the MetricMetaData in there.
I'm wondering where the metadata is in the golang package

The pkg.go.dev documentation is unfortunately far out of date because we last tagged a Go module release in 2018.
Here's a version generated today: https://gowalker.org/github.com/prometheus/prometheus/prompb#WriteRequest

If you go get github.com/prometheus/prometheus@v1.8.2-0.20210720123808-b1ed4a0a663d (see https://github.com/thanos-io/thanos/blob/1205a222cb1e1be4862ef39b4c3a9c538056cf83/go.mod#L63) it should be up to date.

You can use go get github.com/prometheus/prometheus@release-2.30 to get a specific release.

authors: LeviHarrison TomL-dev roidelapluie

repo: prometheus/prometheus


text:
tsdb: Remove mmMaxTime in memSeries

mmMaxTime is only used for WAL replay, but we keep that variable with the memSeries all the time. This PR removes it, with negligible impact in loading WAL.
Benchmark:
benchmark                                                                                old ns/op      new ns/op      delta
BenchmarkLoadWAL/batches=10,seriesPerBatch=100,samplesPerSeries=7200,exemplarsPerSeries=0,mmappedChunkT=0-10          289870573      294268771      +1.52%
BenchmarkLoadWAL/batches=10,seriesPerBatch=100,samplesPerSeries=7200,exemplarsPerSeries=36,mmappedChunkT=0-10         293923760      295168250      +0.42%
BenchmarkLoadWAL/batches=10,seriesPerBatch=100,samplesPerSeries=7200,exemplarsPerSeries=72,mmappedChunkT=0-10         293735146      298376448      +1.58%
BenchmarkLoadWAL/batches=10,seriesPerBatch=100,samplesPerSeries=7200,exemplarsPerSeries=360,mmappedChunkT=0-10        321855188      329008365      +2.22%
BenchmarkLoadWAL/batches=10,seriesPerBatch=10000,samplesPerSeries=50,exemplarsPerSeries=0,mmappedChunkT=0-10          307255323      320213292      +4.22%
BenchmarkLoadWAL/batches=10,seriesPerBatch=10000,samplesPerSeries=50,exemplarsPerSeries=2,mmappedChunkT=0-10          332511927      333360771      +0.26%
BenchmarkLoadWAL/batches=10,seriesPerBatch=1000,samplesPerSeries=480,exemplarsPerSeries=0,mmappedChunkT=0-10          106346488      107618996      +1.20%
BenchmarkLoadWAL/batches=10,seriesPerBatch=1000,samplesPerSeries=480,exemplarsPerSeries=2,mmappedChunkT=0-10          108636521      111356991      +2.50%
BenchmarkLoadWAL/batches=10,seriesPerBatch=1000,samplesPerSeries=480,exemplarsPerSeries=5,mmappedChunkT=0-10          110351396      111606796      +1.14%
BenchmarkLoadWAL/batches=10,seriesPerBatch=1000,samplesPerSeries=480,exemplarsPerSeries=24,mmappedChunkT=0-10         128928656      129701490      +0.60%
BenchmarkLoadWAL/batches=100,seriesPerBatch=1000,samplesPerSeries=480,exemplarsPerSeries=0,mmappedChunkT=3800-10      1083695083     1113460792     +2.75%
BenchmarkLoadWAL/batches=100,seriesPerBatch=1000,samplesPerSeries=480,exemplarsPerSeries=2,mmappedChunkT=3800-10      1095597292     1147324917     +4.72%
BenchmarkLoadWAL/batches=100,seriesPerBatch=1000,samplesPerSeries=480,exemplarsPerSeries=5,mmappedChunkT=3800-10      1124581458     1171130084     +4.14%
BenchmarkLoadWAL/batches=100,seriesPerBatch=1000,samplesPerSeries=480,exemplarsPerSeries=24,mmappedChunkT=3800-10     1350186209     1351729792     +0.11%

I wonder if the benchmarks are creating data which triggers the situation where it helps?
When I made this change I was using a real WAL to check the effect.

I can try it with a real-world WAL as well.

I tried WAL replay on 8GB of WAL, and this PR is 0.8-3% slower. There were no mmap chunks on the disk, so the WAL replay also creates them in the process, so the slowdown could be the disk write or this change. Either way, I don't think that is a big difference to have the variable around.

There were no mmap chunks on the disk

Is that a valid test?  With 15 second scrape, mmap data is ~30 minutes old while the WAL goes back ~3 hours, so most of it gets skipped.  If you tested with no mmap files you wouldn't see this.

Closing this as I dont plan to pursue this further unless really needed

authors: bboreham codesome


text:
Correctly stringify GROUP_x modifiers without labels

Since rule evaluations work via String(), this fixes evaluation of
rules containing GROUP_x modifiers without labels. This change is the
minimal bugfix (so that we can release a fixed version without
risk). It does not intend to implement any additional features (like
allowing GROUP_LEFT() or ON() or even ON - see discussion in
https://github.com/prometheus/prometheus/issues/1597 ).
@fabxc @brian-brazil
This will be merged into the release-0.19 branch because we have to release it as 0.19.2 ASAP.
It fixes #1676 , which breaks rule evaluation in subtle ways, e.g. alerts will cease to fire and only the logs will tell you so.

:+1:

:+1:

That's the second time this happened. This would have been the time to finally hand in an AST object rather than re-parsing the rule every time as planned roughly a year ago.

Sure. That would be the proper solution. What I tried here is to apply the minimum viable change to fix a critical bug.

authors: beorn7 fabxc grobie juliusv


text:
Cut v1.3.0-beta.0

This is a breaking change to the Kubernetes service discovery. This is ok as the Kubernetes SD is in beta status. It requires a configuration change. See prometheus/docs#601 for documentation on the configuration.
@brian-brazil @fabxc @juliusv @grobie @beorn7

I guess we'll wait for https://github.com/prometheus/prometheus/pull/2078#issuecomment-254539237

Yes.
Otherwise, this looks good to me.

Fix is in . Since this is only a beta version, let's go with that.
Perhaps rebase this on top of the fix to avoid confusion.
:+1:

Can we get #2096 in also as it's a bugfix?

Yes, please.
Feel free to merge #2096 .

Will rebase tomorrow, then we'll do the release :)

Rebased and updated the changelog. PTAL @beorn7 @brian-brazil @fabxc

👍

:+1:

authors: beorn7 brancz brian-brazil fabxc


text:
Added go-conntrack for monitoring http connections

Hi, I'd like to get more familiar with Prometheus, and this is my first contribution.
With this change you get these metrics:
# HELP net_conntrack_dialer_conn_attempted_total Total number of connections attempted by the given dialer a given name.
# TYPE net_conntrack_dialer_conn_attempted_total counter
net_conntrack_dialer_conn_attempted_total{dialer_name="default"} 1
# HELP net_conntrack_dialer_conn_closed_total Total number of connections closed which originated from the dialer of a given name.
# TYPE net_conntrack_dialer_conn_closed_total counter
net_conntrack_dialer_conn_closed_total{dialer_name="default"} 0
# HELP net_conntrack_dialer_conn_established_total Total number of connections successfully established by the given dialer a given name.
# TYPE net_conntrack_dialer_conn_established_total counter
net_conntrack_dialer_conn_established_total{dialer_name="default"} 1
# HELP net_conntrack_dialer_conn_failed_total Total number of connections failed to dial by the dialer a given name.
# TYPE net_conntrack_dialer_conn_failed_total counter
net_conntrack_dialer_conn_failed_total{dialer_name="default",reason="refused"} 0
net_conntrack_dialer_conn_failed_total{dialer_name="default",reason="resolution"} 0
net_conntrack_dialer_conn_failed_total{dialer_name="default",reason="timeout"} 0
net_conntrack_dialer_conn_failed_total{dialer_name="default",reason="unknown"} 0
# HELP net_conntrack_listener_conn_accepted_total Total number of connections opened to the listener of a given name.
# TYPE net_conntrack_listener_conn_accepted_total counter
net_conntrack_listener_conn_accepted_total{listener_name="http"} 10
# HELP net_conntrack_listener_conn_closed_total Total number of connections closed that were made to the listener of a given name.
# TYPE net_conntrack_listener_conn_closed_total counter
net_conntrack_listener_conn_closed_total{listener_name="http"} 8

Fixes #2169

A bit of user feedback: conntrack is usually associated with Linux kernel connection tracking feature, seeing net_conntrack metric names makes it  a bit confusing

@redbaron I also had that confusion. That would be something to take up with upstream.

It's not possible to customize the metric names, that would indeed mean a change in the go-conntrack library.

This looks generally okay, but is going to cause some conflicts with recent changes plus changes to 2.0. To minimise disruption would you mind making this change against the dev-2.0 branch?

ok, was just busy with rebasing on master. I see failing tests for the file discovery, is that a know issue at the moment?
time="2017-10-05T16:20:51+02:00" level=error msg="Error reading file "fixtures/_test_valid.yml": yaml: did not find expected node content" source="file.go:200"
time="2017-10-05T16:20:51+02:00" level=error msg="Error reading file "fixtures/_test_valid.json": unexpected end of JSON input" source="file.go:200"
time="2017-10-05T16:20:51+02:00" level=error msg="Error reading file "fixtures/_test_valid.json": invalid character ']' looking for beginning of value" source="file.go:200"
time="2017-10-05T16:20:52+02:00" level=error msg="Error reading file "fixtures/_test_valid.json": invalid character ']' looking for beginning of value" source="file.go:200"
time="2017-10-05T16:20:52+02:00" level=error msg="Error reading file "fixtures/_test_invalid_nil.json": unexpected end of JSON input" source="file.go:200"
time="2017-10-05T16:20:52+02:00" level=error msg="Error reading file "fixtures/_test_valid.json": invalid character ']' looking for beginning of value" source="file.go:200"
time="2017-10-05T16:20:52+02:00" level=error msg="Error reading file "fixtures/_test_invalid_nil.json": nil target group item found" source="file.go:200"
time="2017-10-05T16:20:52+02:00" level=error msg="Error reading file "fixtures/_test_valid.json": invalid character ']' looking for beginning of value" source="file.go:200"
time="2017-10-05T16:21:07+02:00" level=error msg="Error reading file "fixtures/_test_invalid_nil.json": invalid character ']' looking for beginning of value" source="file.go:200"
time="2017-10-05T16:21:07+02:00" level=error msg="Error reading file "fixtures/_test_valid.json": invalid character ']' looking for beginning of value" source="file.go:200"
time="2017-10-05T16:21:07+02:00" level=error msg="Error reading file "fixtures/_test_valid.yml": yaml: did not find expected node content" source="file.go:200"
time="2017-10-05T16:21:07+02:00" level=error msg="Error reading file "fixtures/_test_valid.yml": yaml: did not find expected node content" source="file.go:200"
time="2017-10-05T16:21:07+02:00" level=error msg="Error reading file "fixtures/_test_valid.yml": yaml: did not find expected node content" source="file.go:200"
--- FAIL: TestFileSD (16.62s)
	file_test.go:95: Unexpected target groups [], we expected a failure here.
FAIL
FAIL	github.com/prometheus/prometheus/discovery/file	16.634s

btw: I tried to configure go-conntrack for as many discoveries as possible, but for several discoveries the http client is well hidden in their SDK, so I had no chance to do anything. If they use the default transport they will at least be monitored, only without an own label, but if not they won't be visible in the metrics at all. :/

or several discoveries the http client is well hidden in their SDK, so I had no chance to do anything.

That's fine, this will at least let us monitor some of them.

I see failing tests for the file discovery, is that a know issue at the moment?

Tests should be passing on both master and dev-2.0.

Ok, moved my changes to the dev-2.0 branch and edited the base branch of this PR. Let's see what happens, never did that before ;)

Thanks!

authors: brian-brazil redbaron slintes


text:
Implement new snap-label-to-grid ODE Action - dsl_ode_action_label_snap_to_grid_new

Objects labels are anchored to the Object's bbox which can fluctuate greatly from frame to frame. This make reading the object label difficult as it jumps around in view with the upper left corner of the bbox.
New ODE Action to snap the Object label to the closest point on a defined 2D grid. This has the effect stabilizing the box and only moving it as the object moves through the frame.
/**
 * @brief Creates a uniquely named "Snap Object Label to Grid " ODE Action that moves
 * the object label to the closes location on a 2D grid measured over the frame.
 * @param[in] name unique name for the "Snap Object Label to Grid ODE Action.
 * @param[in] module_width width of each module (square) in the grid in pixels.
 * @param[in] module_height height of each module (square) in the grid in pixels.
 * @return DSL_RESULT_SUCCESS on success, one of DSL_RESULT_ODE_ACTION_RESULT otherwise.
 */
DslReturnType dsl_ode_action_label_snap_to_grid_new(const wchar_t* name,
    uint module_width, uint module_height);

Merged into the v0.30.alpha dev branch


text:
docs: provide docs for Log Analytics resource type Scraper

Related to: https://github.com/tomkerkhove/promitor/pull/2132

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

repo: promitor/docs


text:
feature request: optimize prompt

optimize prompt like https://promptperfect.jina.ai/

unused

authors: liruifengv phodal

repo: prompt-engineering/click-prompt


text:
Cannot set custom provider for LLM grader override

As per the docs https://www.promptfoo.dev/docs/configuration/expected-outputs#overriding-the-llm-grader
We should be able to use custom providers for the LLM grading.
However, when setting custom provider via any of the methods (defaultTest.options and assertion.provider), the following error is thrown
Error: Invariant failed: Provider supplied to llm-rubric must have an id at invariant (/usr/local/share/npm-global/lib/node_modules/promptfoo/node_modules/tiny-invariant/dist/tiny-invariant.cjs.js:14:11) at getGradingProvider (/usr/local/share/npm-global/lib/node_modules/promptfoo/dist/src/matchers.js:50:38) at matchesLlmRubric (/usr/local/share/npm-global/lib/node_modules/promptfoo/dist/src/matchers.js:118:31) at runAssertion (/usr/local/share/npm-global/lib/node_modules/promptfoo/dist/src/assertions.js:383:55) at runAssertions (/usr/local/share/npm-global/lib/node_modules/promptfoo/dist/src/assertions.js:49:30) at Evaluator.runEval (/usr/local/share/npm-global/lib/node_modules/promptfoo/dist/src/evaluator.js:182:74) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /usr/local/share/npm-global/lib/node_modules/promptfoo/dist/src/evaluator.js:418:25
Providing the id, as suggested by the error does not matter.
The same custom provider works fine when set as the configuration file's "providers" property.
Below is the promptfooconfig.yaml file that reproduces the issue for me.

prompts: [prompt.yaml]
providers: [../../providers/custom.js]
defaultTest:
assert:
- type: llm-rubric
options:
provider: [../../providers/custom.js]
rubricPrompt:
- role: system
content: >-
Grade the output by the following specifications, keeping track of the points scored:

        Did the output include code? +1 point
        Was the output in markdown format? +1 point
        Is the output relevant to the {{ query }}? +1 point

        Calculate the score and pass the test if total points is greater than 2.5.
        Output must be in the following JSON format:
        {pass: true, score: number, reason: string}
    - role: user
      content: 'Output: {{ output }}'

tests: tests/user-prompts.csv

The workaround I have found is to set provider as a string.
Setting the provider as object and providing id as below, does not work.
defaultTest:   assert:     - type: llm-rubric   options:     provider:        ../../providers/custom.js:         id: 'evaluator'

Hi @AnkitTheCoder, a bit late to this issue but the correct setup would be to set provider: ../../providers/custom.js, as you found.  The provider property on Assertion is a string.

authors: AnkitTheCoder typpo

repo: promptfoo/promptfoo


text:
WIP: feat: Add Cloudflare AI Provider

Closes #647
This is a work in progress I wanted to put up for initial feedback. I still need to test it a bunch more locally and update the docs as well.

@typpo Anything else major besides docs that you think might be missing, assuming a correct implementation on my part of the CF API calls?

Note to self, look at https://github.com/promptfoo/promptfoo/pull/711/files for inspiration on examples + docs

@typpo the line changes related to formatting are due to VS code auto-format. I tried to remove then by running npm run format but that command generated a MASSIVE diff so I think you might want to consider enforcing the styling in CI in a separate effort

Nice change!  This looks pretty much ready to go.  Hopefully @CamdenClark can find the time to verify this weekend, otherwise I'll figure out how to get myself set up on Cloudflare AI :)

Nice change! This looks pretty much ready to go. Hopefully @CamdenClark can find the time to verify this weekend, otherwise I'll figure out how to get myself set up on Cloudflare AI :)

I got to it! It works on my machine!
Thanks for taking this up, I got super distracted and forgot to do it :sweat:
In the future it would be cool to get LoRA support but that's not necessary to merge in my opinion.
Feel free to tag me on a non-draft PR if you want another review.

one other thing you might want to know -- I had to build promptfoo on a new machine with node 22 and I got some weird C++ errors with better-sqlite. Might want to put a note recommending node 20

@CamdenClark thanks for testing for me....
@typpo im working now on the docco after fixing the failing tests today. Would you mind please re-triggering the CI test workflow so that I can verify that worked? Assuming thats green, and once I push one more commit for the docs and a few more examples, then this should be good to go (though I'll do a final rebase against master before un-drafting it)

@typpo this is now done and awaiting final review + green CI

🎉 Amazing work @jacobdr and thanks @CamdenClark for helping too!

authors: CamdenClark jacobdr typpo


text:
Wrong rank of related objects with save cascade

Hi,
Incorrect data into "bien_charge", u can check "test" and "sortable_rank" columns.
http://sandbox.propelorm.org/58f8213
Correct "bien_charge"
http://sandbox.propelorm.org/bea9033
Probably a bug due to Propel, because the only thing that changes is the call to "save" function before or after instantiation, and i don't think this is the expected behavior.
Thanks.

I have a second bug with scope parameter of sortable behavior.
Adding multiple objects before saving causes a bad "rank", it's the same value "1" for each objects !
http://sandbox.propelorm.org/dab1e08
However, it works when I call the "save" function before to add the next object...
http://sandbox.propelorm.org/dff3d40
Thanks again.

I am the only one with these problems?

Any news about this issue?

Is someone able to make a PR here with suggested changes?

authors: dereuromark ktounet pierregaste

license: mit


text:
feat: add NewFileBucket func

Enables the possibility to initialize FileBuckets from external packages

@msbarry would it be cleaner here to make Path an exported field?

@msbarry would it be cleaner here to make Path an exported field?

Only if you want it to be readable.  Otherwise it's kind of nice to have a function that all creation goes through in case you want to insert some logic, path normalization, etc.

Thanks for the PR!

authors: bdon jzs msbarry

repo: protomaps/go-pmtiles


text:
fix(extra712): changed Macie service detection

Context
Reference issue 1279 in regards to a better way of determining Macie status.
Description
Instead of looking for an IAM role and guessing that Macie may be enabled, directly querying get-macie-session status will determine the current state.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Hi @williambrady, good catch!
I have added some changes to this PR such as adding regional context and handling of errors.
Thank you for the contribution 😄

authors: sergargar williambrady

repo: prowler-cloud/prowler


text:
有没有办法可以不安装插件使用

用了几台电脑做试验，有几台直接可以使用不需要安装swithomage插件，但是有台就不行，由于安装插件后不能正常浏览网页，要来回切换。所以想问下，这到底是哪方面的区别，有没有可以不安装插件的解决办法，毕竟插件只支持chrome，如果用IE或者微信直接打开链接就没法下载了！
谢谢大神回答

确实好奇怪，我这台也不用安装插件。我也不知道这个插件有何意义。

改变嗅探模式没什么用，什么办法都用了，就是必须装插件，但是有几台，直接解压就可以用了，不用安装swithomage

其实，插件安装不麻烦，就是切换模式麻烦，另外只是安装插件的话，IE和微信直接打开的链接不能支持，好想研究出不用安装插件的电脑里是多了什么

嗅探模式就是改IE的代理信息，如果chrome没改什么的话也是跟着走IE 。swithomage就是代理的扩展，装了后chrome就不走IE的代理信息了

哦哦哦，懂了，但是我改了嗅探模式，仍然没有用，IE的代理信息看过是跟我不用安装插件的电脑是一样的，chrome也没改什么，应该是跟着IE走，所以也就是两个都不能用，感谢大神

repo: proxyee-down-org/proxyee-down


text:
encoding not implemented gzip, deflate, br

Thanks for this lib however some content encoding not implemented gzip, deflate, br , will be much better to add them

Thanks for raising this suggestion @korolossamy. These are definitely features that I plan to implement in the future when I have time. You are always welcome to open a new Pull Request with the suggested changes 🙏 .

authors: bokklu korolossamy

repo: proxykingdom/proxy-client


text:
Use the module together with another module: react-native-super-grid

@prscX :
Hi, I would like to get the same effect that you see in the image, the number 3.
Image: https://raw.githubusercontent.com/willowtreeapps/spruce-ios/master/imgs/extensibility-tests.gif
To make the grid-view, use: react-native-super-grid.
But I can not get the same result.
Here is a code example: https://snack.expo.io/Sk2gfsZUM
How can I do?
P.Š.
Is it possible to reset animation on command to be able to repeat it?

Thanks @Angelk90 for raising the query.
Coming weekend I will try to mirror the same behaviour and update you with the solution.
Thanks
Pranav

Hi @Angelk90, Apologies for the delay.
First I would like to thank you for creating a grid sample using react-native-super-grid.
With few changes in source provided by you, I am able to achieve the similar effect. I have updated App.js Example and created this as base example.
Can you please verify it once by downloading Example from master branch.
Please let me know in case still improvements are required. Please find below changes I have made to your source in order to achieve the similar effect:

let sortWith = new CorneredSort(60); decreased interObjectDelay value to 60
let animateWith = DefaultAnimations.growAnimator(1000); used growAnimator animation
animator={{ propertyName: "translationY"}) changed property name to translationY instead of translationX

Thanks
Pranav

@prscX : I try the example does not seem to work properly, the colors are not loaded.
P.Š.
     let sortWith = new CorneredSort (60);
     let animateWith = DefaultAnimations.growAnimator (1000);
If the variables are declared in the state, should it work correctly or not?
Because in my case where I should use it the component is not found in the render but
in a function.

Hi @Angelk90,  Just now I have downloaded the latest library and example please find below result which I have received:

Transit Images

Ideally variable accessed through state should work perfectly well. Can you please refer example App.js class where I have achieved similar animation
Thanks
Pranav

@prscX :
Link: https://snack.expo.io/H1gaYSCLM
I do not understand why in this example I created, the module does not seem to work.

Are you trying to run the app using expo? If yes it will not work because expo is not bundling native linked libraries. Please try to run the example using xcode.
Thanks
Pranav

This specific error I am not sure, ideally it should have worked since it is trying to load expo bundled native library only.
Thanks
Pranav

@prscX :  I'm not running it on Expo, that was just to show you the code. P. S. Then strange that certain modules that have a native part work on Expo.

Hi @Angelk90, Did you found any solution for the problem?
Thanks
Pranav

@prscX :
I could not find a solution.
If I have defined, in the state:
    this.state = {
      sortWith: new CorneredSort(60),
      animateWith: DefaultAnimations.growAnimator(1000),
}

And use:
<Spruce
 sortWith={this.state.sortWith}
 animateWith={this.state.animateWith}

The change in values should work, is not it?

Hi @Angelk90, I have never tried through state props. Ideally it should work, coming weekend I will try this using provided example.
Thanks
Pranav

repo: prscX/react-native-spruce


text:
Adding section on SDF memory usage.

This addresses issue #2 regarding memory usage of the SDF data structure for use in production simulations.

LGTM

authors: gonuke pshriwise

repo: pshriwise/dissertation


text:
Update os-lib_2.13 to 0.10.1

About this PR
📦 Updates com.lihaoyi:os-lib_2.13 from 0.6.3 to 0.10.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.lihaoyi", artifactId = "os-lib_2.13" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.lihaoyi", artifactId = "os-lib_2.13" }
}]

labels: library-update, early-semver-major, semver-spec-minor, commit-count:1

Superseded by #57.

repo: pstutz/scala-fullstack


text:
Enable an admin user to download key metadata for all the publications in each bucket

Fields exported should include:
Publication: Title
Publication: DOI
Publication: DOI Verification Status
Publication: Preferred Version
Publication: Publication date
Publication: Abstract
Publication: ID (within RMD)
File: ID (within RMD)
File: Filename
File: Download link
File: Version
File: License
File: Set statement
File: Checked for set statement
File: Embargo date
File: Checked for embargo date
File: Author's access ID
File: Wrong version email last sent on
I still need to finalize the list here -- there may also be other fields we'd want to export.

We are prioritizing #997, #978, and #965 instead of doing this.

repo: psu-libraries/researcher-metadata


text:
Card suggestion: documentation

When playing it with the OpenFisca community, they pointed out that it is not uncommon that separate actors are responsible for documentation, which means that an object card for Documentation could be useful.

As icon I suggest one of these:

Notebook
Dividers
Paper sheet

Maybe we go with Notebook for 1.0?

authors: Ainali ericherman

repo: publiccodenet/governance-game


text:
Bug | The adv is not able to see the full transcript

The transcript is truncated during the hearing:
The Exit Hearing text is misaligned

Hi @devarajd94  This Issue is fixed

Hi @Ramu-kandimalla
This issue is resolved in UAT.
STEPS TO REPRODUCE:

Start Hearing of a Case by Judge.
Join hearing by Advocate/Litigant.
Add Transcription, check scroll option in both users hearing page.

Verified

authors: Ramu-kandimalla bhuvanyuguru devarajd94

repo: pucardotorg/dristi


text:
Refactor tar decompress

Closes #1522

Successfully ran the liberate:dump_log_ids on staging - the events now show the number of updated and deleted bibs

repo: pulibrary/bibdata


text:
Eliminate case sensitivity in hyper-linked search functionality (Keywords, for example)

linked keywords in DPUL are case sensitive with search. "Christianity" and "christianity" show up as separate search queries/results.  As a researcher, it is essential that I am able to discover everything within that keyword/search parameter, regardless of capitalization.
Example collection with keywords (currently unpublished - sign in to view): https://dpul.princeton.edu/sae_sri_lanka_dissidents/browse/collection-of-tissa-balasuriya

This is probably because it's keywords_ssim vs keywords_tesim.

@tpendragon observed that keywords weren't included in the default search

The functionality here is provided by blacklight's link_to_search. I really think this is the intended behavior. It's actually being renamed link_to_facet. Facet values don't provide the kind of string processing that other types of fields do because it's expected that they be very precise. Generally a data cleanup would be used to resolve this type of problem. If keyword was selected as a facet value for this collection the faceted search results will also suffer from this same issue until the data is cleaned. @tpendragon do you have a different perspective?

It seems like the standard way to fix this is to present facets from a field without the lowercase, but facet via a field with lowercase. I'm not sure if Blacklight can display differently, and I don't think we're indexing into a field which lowercases but doesn't tokenize.
Options to fix:

Clean up the non-lowercased keys.
Do 1, but also make it so keyword lowercases on save.
Add a special field type in solr which lowercases but doesn't tokenize, and index keywords into there.

2 is probably easiest and most complete?

And then also capitalize them (sentence case) on presentation, I assume. Since most of them are capitalized.
This seems like a reasonable solution.

@kelea99 the keywords are now being forced to lowercase on import. I reindexed the collection in question. Could you let me know if this resolves the issue?

Testing now.  tested capitalized terms in search bar and it works, but throws back different results. I would assume this is due to other case sensitive metadata bits we haven't addressed. What I will say is the standardization of the keywords by forcing all lowercase works, and works well. So the request for Keywords has been fulfilled. I have sent to Ellen to test and will confirm with her today as well, @hackartisan , and update here if we can close the ticket.

Looks great, @hackartisan! Approved by Stakeholder, too. Closing ticket

authors: hackartisan kelea99 tpendragon

repo: pulibrary/dpul


text:
Copy all holding fields, not just the last one.

Closes #980

Coverage increased (+0.01%) to 79.051% when pulling debbf6988fc799ea99cf7e2eb50f4355bed4beee on multiple_866 into a52590896a204eabfc735895485de45142784749 on alma.

Coverage increased (+0.01%) to 79.051% when pulling debbf6988fc799ea99cf7e2eb50f4355bed4beee on multiple_866 into a52590896a204eabfc735895485de45142784749 on alma.

authors: coveralls tpendragon