when cd kernels/selective_scan && pip install .  encountered this error

Building wheel for selective-scan (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [186 lines of output]
  torch.__version__  = 2.1.1+cu118

  CUDA_HOME = /home/xys/anaconda3/envs/mamba

  CUDA version:  11.8
  running bdist_wheel
  running build
  running build_ext
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py:424: UserWarning: There are no g++ version bounds defined for CUDA version 11.8
    warnings.warn(f'There are no {compiler_name} version bounds defined for CUDA version {cuda_str_version}')
  building 'selective_scan_cuda_oflex' extension
  creating /home/xys/paper_code/VMamba-main/kernels/selective_scan/build
  creating /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310
  creating /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc
  creating /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan
  creating /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex
  Emitting ninja build file /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/build.ninja...
  Compiling objects...
  Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
  [1/3] /home/xys/anaconda3/envs/mamba/bin/nvcc  -I/home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/torch/csrc/api/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/TH -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/THC -I/home/xys/anaconda3/envs/mamba/include -I/home/xys/anaconda3/envs/mamba/include/python3.10 -c -c /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_fwd.cu -o /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex/selective_scan_core_fwd.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O3 -std=c++17 -U__CUDA_NO_HALF_OPERATORS__ -U__CUDA_NO_HALF_CONVERSIONS__ -U__CUDA_NO_BFLOAT16_OPERATORS__ -U__CUDA_NO_BFLOAT16_CONVERSIONS__ -U__CUDA_NO_BFLOAT162_OPERATORS__ -U__CUDA_NO_BFLOAT162_CONVERSIONS__ --expt-relaxed-constexpr --expt-extended-lambda --use_fast_math --ptxas-options=-v -lineinfo -gencode arch=compute_60,code=sm_60 -gencode arch=compute_70,code=sm_70 -gencode arch=compute_80,code=sm_80 -gencode arch=compute_90,code=sm_90 --threads 4 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=selective_scan_cuda_oflex -D_GLIBCXX_USE_CXX11_ABI=0
  FAILED: /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex/selective_scan_core_fwd.o
  /home/xys/anaconda3/envs/mamba/bin/nvcc  -I/home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/torch/csrc/api/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/TH -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/THC -I/home/xys/anaconda3/envs/mamba/include -I/home/xys/anaconda3/envs/mamba/include/python3.10 -c -c /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_fwd.cu -o /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex/selective_scan_core_fwd.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O3 -std=c++17 -U__CUDA_NO_HALF_OPERATORS__ -U__CUDA_NO_HALF_CONVERSIONS__ -U__CUDA_NO_BFLOAT16_OPERATORS__ -U__CUDA_NO_BFLOAT16_CONVERSIONS__ -U__CUDA_NO_BFLOAT162_OPERATORS__ -U__CUDA_NO_BFLOAT162_CONVERSIONS__ --expt-relaxed-constexpr --expt-extended-lambda --use_fast_math --ptxas-options=-v -lineinfo -gencode arch=compute_60,code=sm_60 -gencode arch=compute_70,code=sm_70 -gencode arch=compute_80,code=sm_80 -gencode arch=compute_90,code=sm_90 --threads 4 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=selective_scan_cuda_oflex -D_GLIBCXX_USE_CXX11_ABI=0
  In file included from /usr/include/cuda_runtime.h:83,
                   from <command-line>:
  /usr/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
    138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
        |  ^~~~~
  In file included from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_fwd_kernel_oflex.cuh:7,
                   from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_fwd.cu:4:
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/c10/util/BFloat16.h:11:10: fatal error: cuda_bf16.h: 没有那个文件或目录
     11 | #include <cuda_bf16.h>
        |          ^~~~~~~~~~~~~
  compilation terminated.
  In file included from /usr/include/cuda_runtime.h:83,
                   from <command-line>:
  /usr/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
    138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
        |  ^~~~~
  In file included from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_fwd_kernel_oflex.cuh:7,
                   from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_fwd.cu:4:
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/c10/util/BFloat16.h:11:10: fatal error: cuda_bf16.h: 没有那个文件或目录
     11 | #include <cuda_bf16.h>
        |          ^~~~~~~~~~~~~
  compilation terminated.
  In file included from /usr/include/cuda_runtime.h:83,
                   from <command-line>:
  /usr/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
    138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
        |  ^~~~~
  In file included from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_fwd_kernel_oflex.cuh:7,
                   from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_fwd.cu:4:
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/c10/util/BFloat16.h:11:10: fatal error: cuda_bf16.h: 没有那个文件或目录
     11 | #include <cuda_bf16.h>
        |          ^~~~~~~~~~~~~
  compilation terminated.
  In file included from /usr/include/cuda_runtime.h:83,
                   from <command-line>:
  /usr/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
    138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
        |  ^~~~~
  In file included from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_fwd_kernel_oflex.cuh:7,
                   from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_fwd.cu:4:
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/c10/util/BFloat16.h:11:10: fatal error: cuda_bf16.h: 没有那个文件或目录
     11 | #include <cuda_bf16.h>
        |          ^~~~~~~~~~~~~
  compilation terminated.
  [2/3] /home/xys/anaconda3/envs/mamba/bin/nvcc  -I/home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/torch/csrc/api/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/TH -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/THC -I/home/xys/anaconda3/envs/mamba/include -I/home/xys/anaconda3/envs/mamba/include/python3.10 -c -c /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_bwd.cu -o /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex/selective_scan_core_bwd.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O3 -std=c++17 -U__CUDA_NO_HALF_OPERATORS__ -U__CUDA_NO_HALF_CONVERSIONS__ -U__CUDA_NO_BFLOAT16_OPERATORS__ -U__CUDA_NO_BFLOAT16_CONVERSIONS__ -U__CUDA_NO_BFLOAT162_OPERATORS__ -U__CUDA_NO_BFLOAT162_CONVERSIONS__ --expt-relaxed-constexpr --expt-extended-lambda --use_fast_math --ptxas-options=-v -lineinfo -gencode arch=compute_60,code=sm_60 -gencode arch=compute_70,code=sm_70 -gencode arch=compute_80,code=sm_80 -gencode arch=compute_90,code=sm_90 --threads 4 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=selective_scan_cuda_oflex -D_GLIBCXX_USE_CXX11_ABI=0
  FAILED: /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex/selective_scan_core_bwd.o
  /home/xys/anaconda3/envs/mamba/bin/nvcc  -I/home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/torch/csrc/api/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/TH -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/THC -I/home/xys/anaconda3/envs/mamba/include -I/home/xys/anaconda3/envs/mamba/include/python3.10 -c -c /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_bwd.cu -o /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex/selective_scan_core_bwd.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options ''"'"'-fPIC'"'"'' -O3 -std=c++17 -U__CUDA_NO_HALF_OPERATORS__ -U__CUDA_NO_HALF_CONVERSIONS__ -U__CUDA_NO_BFLOAT16_OPERATORS__ -U__CUDA_NO_BFLOAT16_CONVERSIONS__ -U__CUDA_NO_BFLOAT162_OPERATORS__ -U__CUDA_NO_BFLOAT162_CONVERSIONS__ --expt-relaxed-constexpr --expt-extended-lambda --use_fast_math --ptxas-options=-v -lineinfo -gencode arch=compute_60,code=sm_60 -gencode arch=compute_70,code=sm_70 -gencode arch=compute_80,code=sm_80 -gencode arch=compute_90,code=sm_90 --threads 4 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=selective_scan_cuda_oflex -D_GLIBCXX_USE_CXX11_ABI=0
  In file included from /usr/include/cuda_runtime.h:83,
                   from <command-line>:
  /usr/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
    138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
        |  ^~~~~
  In file included from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_bwd_kernel_oflex.cuh:7,
                   from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_bwd.cu:4:
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/c10/util/BFloat16.h:11:10: fatal error: cuda_bf16.h: 没有那个文件或目录
     11 | #include <cuda_bf16.h>
        |          ^~~~~~~~~~~~~
  compilation terminated.
  In file included from /usr/include/cuda_runtime.h:83,
                   from <command-line>:
  /usr/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
    138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
        |  ^~~~~
  In file included from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_bwd_kernel_oflex.cuh:7,
                   from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_bwd.cu:4:
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/c10/util/BFloat16.h:11:10: fatal error: cuda_bf16.h: 没有那个文件或目录
     11 | #include <cuda_bf16.h>
        |          ^~~~~~~~~~~~~
  compilation terminated.
  In file included from /usr/include/cuda_runtime.h:83,
                   from <command-line>:
  /usr/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
    138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
        |  ^~~~~
  In file included from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_bwd_kernel_oflex.cuh:7,
                   from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_bwd.cu:4:
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/c10/util/BFloat16.h:11:10: fatal error: cuda_bf16.h: 没有那个文件或目录
     11 | #include <cuda_bf16.h>
        |          ^~~~~~~~~~~~~
  compilation terminated.
  In file included from /usr/include/cuda_runtime.h:83,
                   from <command-line>:
  /usr/include/crt/host_config.h:138:2: error: #error -- unsupported GNU version! gcc versions later than 8 are not supported!
    138 | #error -- unsupported GNU version! gcc versions later than 8 are not supported!
        |  ^~~~~
  In file included from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_bwd_kernel_oflex.cuh:7,
                   from /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_core_bwd.cu:4:
  /home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/c10/util/BFloat16.h:11:10: fatal error: cuda_bf16.h: 没有那个文件或目录
     11 | #include <cuda_bf16.h>
        |          ^~~~~~~~~~~~~
  compilation terminated.
  [3/3] c++ -MMD -MF /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex/selective_scan_oflex.o.d -pthread -B /home/xys/anaconda3/envs/mamba/compiler_compat -Wno-unused-result -Wsign-compare -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /home/xys/anaconda3/envs/mamba/include -fPIC -O2 -isystem /home/xys/anaconda3/envs/mamba/include -fPIC -I/home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/torch/csrc/api/include -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/TH -I/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/include/THC -I/home/xys/anaconda3/envs/mamba/include -I/home/xys/anaconda3/envs/mamba/include/python3.10 -c -c /home/xys/paper_code/VMamba-main/kernels/selective_scan/csrc/selective_scan/cusoflex/selective_scan_oflex.cpp -o /home/xys/paper_code/VMamba-main/kernels/selective_scan/build/temp.linux-x86_64-cpython-310/csrc/selective_scan/cusoflex/selective_scan_oflex.o -O3 -std=c++17 -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=selective_scan_cuda_oflex -D_GLIBCXX_USE_CXX11_ABI=0
  ninja: build stopped: subcommand failed.
  Traceback (most recent call last):
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 2100, in _run_ninja_build
      subprocess.run(
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/subprocess.py", line 526, in run
      raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

  The above exception was the direct cause of the following exception:

  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/home/xys/paper_code/VMamba-main/kernels/selective_scan/setup.py", line 145, in <module>
      setup(
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/__init__.py", line 103, in setup
      return distutils.core.setup(**attrs)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
      return run_commands(dist)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
      dist.run_commands()
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
      self.run_command(cmd)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
      super().run_command(command)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/wheel/_bdist_wheel.py", line 378, in run
      self.run_command("build")
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
      super().run_command(command)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/command/build.py", line 131, in run
      self.run_command(cmd_name)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/dist.py", line 989, in run_command
      super().run_command(command)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 88, in run
      _build_ext.run(self)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 345, in run
      self.build_extensions()
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 873, in build_extensions
      build_ext.build_extensions(self)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 467, in build_extensions
      self._build_extensions_serial()
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 493, in _build_extensions_serial
      self.build_extension(ext)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/command/build_ext.py", line 249, in build_extension
      _build_ext.build_extension(self, ext)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/Cython/Distutils/build_ext.py", line 135, in build_extension
      super(build_ext, self).build_extension(ext)
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/setuptools/_distutils/command/build_ext.py", line 548, in build_extension
      objects = self.compiler.compile(
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 686, in unix_wrap_ninja_compile
      _write_ninja_file_and_compile_objects(
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 1774, in _write_ninja_file_and_compile_objects
      _run_ninja_build(
    File "/home/xys/anaconda3/envs/mamba/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 2116, in _run_ninja_build
      raise RuntimeError(message) from e
  RuntimeError: Error compiling objects for extension
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for selective-scan
Running setup.py clean for selective-scan
Failed to build selective-scan
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (selective-scan)
GPU: single 4090D
CUDA:11.8
torch:2.1.1
python:3.10
pls help me TAT

我遇到同样的问题，请问解决了吗

It seems like that your cuda library is not compatible with your gcc version. Try updating you cuda version.

I've encountered the same issue. Using g++ version 11 seems to fix it. Here is what I did:
First install g++-11
sudo apt install g++-11

add the following line to kernels/selective_scan/setup.py to explicitly specify the g++ version
def get_ext():
    cc_flag = []

    cc_flag.append("-ccbin=/usr/bin/g++-11")  # add this

    # ...

then the setup should work properly with pip install .. I suspect this is a compatibility issue with CUDA 11.8.


Preload bar does not work properly on Firefox 26.0

The preload bar only filled up about 3% and you cannot seek past the bar, even if the play head has passed it. However once the page has been refreshed the preload bar is immediately full and seeking is available.

Thanks for this! (6 years later)


Initial layout with SkShaper is slower

To reproduce:

Add tracing to RenderParagraph.performLayout
Run the following app:

import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool _showText = false;
  final List<Widget> children = List.generate(9, (index) {
    return ListTile(
      leading: CircleAvatar(
        child: Text('G$index}'),
      ),
      title: Text(
        'Foo contact from $index-th local contact',
        overflow: TextOverflow.ellipsis,
      ),
      subtitle: Text('+91 88888 8800$index'),
    );
  });

  @override
  Widget build(BuildContext context) {

    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: !_showText
          ? Container()
          : OverflowBox(
              alignment: Alignment.topCenter,
              maxHeight: double.infinity,
              child: Column(
                children: children,
              ),
            ),
      floatingActionButton: FloatingActionButton(
        onPressed: () {
          setState(() {
            _showText = !_showText;
          });
        },
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

Click the FAB once and in the trace look at the frame that layouts all the list tiles.

On a low-powered Android device with SkShaper enabled it takes on average 1.4ms per RenderParagraph layout for the three strings in the list tile. With libtxt this average is around 0.9ms.
Subsequent layouts of the same strings in "fresh" RenderParagraphs (pressing the FAB again and again to make the list tiles disappear and appear again) is faster. Both libtxt and SkShaper average around 0.5ms here.
The higher cost of the initial layout is significant because it happens at a time where the performance budget is already tight, e.g. when a new screen needs to be build for the first time. With libtext, it takes about 27ms to initially lay out all the RenderParagraphs in the list tiles, whereas with SkShaper it takes 36ms.

/cc @jason-simmons

If we don't have benchmarks that capture this, we should add some.

Some factors that are affecting performance on this example:

SkParagraph has higher fixed overhead for each layout call regardless of the contents of the text.
Libtxt/Minikin has a different caching strategy that will cache words within the text.  This example repeatedly lays out strings that mostly contain the same words, so Libtxt/Minikin's cache can save significant work.
SkParagraph's ellipsize implementation does more work but should produce higher quality results.

The difference between Libtxt and SkParagraph performance will depend on the workload.
I would expect SkParagraph to perform better on longer text strings with fewer repeated words.  In that case the fixed overhead is a smaller part of the overall layout time.  And for longer strings SkParagraph's strategy of making one HarfBuzz hb_shape call for the whole string may be faster than the Libtxt/Minikin per-word shaping and caching.
@Rusino

This is a trace of an SkParagraph ParagraphImpl::layout call for a paragraph containing one character.  This was captured on a low-powered device.

Some noteworthy parts:

computeCodeUnitProperties (18% of the total time).  This is calling ICU APIs to determine attributes of the characters in the text.
HarfBuzz hb_shape (18%)
append in SkShaper_HarfBuzz (12%) - this calls OneLineShaper's runBuffer and commitRunBuffer
OneLineShaper::finish (5%)
ParagraphCache::updateParagraph (10%)

Marking this as P3 as this is an active ongoing investigation. I don't see any concrete action items from it just yet. Perhaps a list of traces for https://github.com/flutter/flutter/issues/94063.

In WidgetsBinding process the Flutter framework will 'warm up text shaper', this operation will create string "-" and special the width constraint is 60 then engine will FontCollection and minikin::Layout the string. The purpose of that is reduce the app text layout when app running.
But the "warm up text shaper" is in Flutter.UI Thread, it will block the App lunch.
My question is: while app start, the engine dispatch a thread to warm up text shaper?

Anyone following this?

@JsouLiang this is more that laying out a new string is expensive the first time, rather than an initial call being expensive. There are some people actively working on this

“There are some people actively working on this” might i follow this active?

@goderbauer do we have a public doc on this, or anything to update on the issue here? My knowledge right now is we're working with the SkShaper folks to optimize layout for some common cases (renering static text that does not need to save/calculate offsets for cursor positioning, perhaps avoid ICU lookups on text we know ICU won't help), and potentially breaking up shaping and linebreaking so that it can be a two step process kicked off asynchronously.

I spent some time looking at SkParagraph profiles and trying to reduce data copying and other redundant work.
Some improvements that landed recently:
https://skia-review.googlesource.com/c/skia/+/483022
https://skia-review.googlesource.com/c/skia/+/481796
https://skia-review.googlesource.com/c/skia/+/481239

The example above is not a valid test for performance. It has text that is almost always repeating:
'Foo contact from $index-th local contact', '+91 88888 8800$index'.
As a result word-based cache in libtxt wins over whole string cache in SkParagraph. In real life, however, words repetitions happen  not so often. I suggest we fix the test (for instance, add $index to ALMOST all words in the line) and see how the results change.
I am fairly sure this is what causes the performance difference. SkParagraph shapes every line every time, libtxt - only indexes, combining the rest of the line from already shaped words (shaping is the most expensive operation!).
Now, we can optimize the initial layout performance anyway but I don't want it to be tied to this bug (SkParagraph is slower).
I also want to have a correct base line for future improvements.

Average initial RenderParagraph layout with SkParagraph: 1.384 ms
Average initial RenderParagraph layout with libtxt: 1.389 ms
@Rusino Your theory sounds plausible :). Is there a reason why SkParagraph shouldn't have a similar word-cache, though? Since it seems to give us a speed-up in some scenario?
Traces.zip
This is now with injecting the index everywhere:

What is the status of this issue?

We need to add this as a benchmark to CI.
SkShaper has made some improvements recently that should have improved this. It's shown in some benchmarks here: https://flutter-engine-perf.skia.org/e/?begin=1648251309&end=1649785870&queries=executable%3D._txt_benchmarks%26test%3DSkParagraphFixture_ShortLayout&requestType=0&xbaroffset=27006
I'm going to see if we can add this one to CI.

AFAICT all work items mentioned in this issue are complete. If there's any further follow-up required, it should be filed as a new issue.


fix: fire Magellan update event only where there is a change

Fix for #9068 and #10384. Fires update only where there is a change.

@coreysyms Also, could you submit PR from a branch on your own fork, instead of the main Foundation repo ? ;)

@coreysyms I fixed a bug (the event was not fired anymore when the active link were reset), and refactored the function.
@colin-marshall or @JeremyEnglert  Could you take a look at this please ?

There should be no breaking changes or new features, so I plan this for v6.4.4.

lgtm

Do we still need this branch here?

@DanielRuf No. Nice catch


fix: escaping path correct for the right click "add to .gitignore" action when containing opening square brackets "["

This PR closes #184898
This bug affected me now for a long time and I finally decided to try to fix it myself as it does not seem as a really complex bug.
What's the current problem?
Currently, there is an issue with one of the context menu options. If you are in the shipped source control extension (git) in a repository and right-click a changed file, you can select "Add to .gitignore". This will append the selected file path to the .gitignore file.
This works for most special characters. The only issue seems to be when dealing with open square brackets ("["). Closing square brackets are not a problem, but the opening ones cause git to not recognize the file path correctly. This will result in the file not properly excluded from future commits.
I think it has something to do, with .gitignore beeing parsed with regex capabilities by git and therefore interpreting the opening squared bracket as the start of an expression. The closing square bracket can never be the start of an expression and therefore does not cause any issues.
Solution
Opening square brackets have to be escaped properly. Escaping them will make git to recogine the path correctly in .gitignore.
I just used the same method already used in the same line of code to also replace these opening square brackets with an opening escaped square bracket
How to reproduce the initial issue

Create a new repository
add a file containing a open square bracket in the name, e.g."File[Name.txt"
go into the source control panel on the left side
right-click the file and select "Add to .gitignore"
You will see that the file will not be removed from the list of changed files but a entry is added to the .gitignore file

How to test this PR

Create a new repository
add a file containing a open square bracket in the name
go into the source control panel on the left side
right-click the file and select "Add to .gitignore"
the file is removed from the changes list, as the .gitignore entry is now correctly escaped

I sanity checked this behavior with "git status" to make sure it's not a pure vscode quirk with the internal .gitignore recognition for changes.
It appears that there are currently no automatic tests regarding these code parts.
Tested with git version 2.41.0.windows.1 on Windows 11

@JulianLegler, thank you very much for submitting the pull request along with the detailed description of the changes and how to test your changes. I have looked through them and decided to weak things a little to "future proof" in case there will be other special characters that we would want to escape. Closing this PR in favour of https://github.com/microsoft/vscode/pull/224777.


Cannot read property 'knexSchema' of undefined

Getting this error when trying to run the migration from zero (nothing in db & no previous migrations)
Stacktrace:
/node_modules/bluebird/js/release/async.js:61
        fn = function () { throw arg; };
                           ^

TypeError: Cannot read property 'knexSchema' of undefined
    at String.handlebars.registerHelper (/node_modules/schwifty-migrate-diff/lib/index.js:788:19)
    at eval (eval at createFunctionContext (/node_modules/handlebars/dist/cjs/handlebars/compiler/javascript-compiler.js:254:23), <anonymous>:6:173)
    at prog (/node_modules/handlebars/dist/cjs/handlebars/runtime.js:221:12)
    at execIteration (/node_modules/handlebars/dist/cjs/handlebars/helpers/each.js:51:19)
    at String.<anonymous> (/node_modules/handlebars/dist/cjs/handlebars/helpers/each.js:61:13)
    at eval (eval at createFunctionContext (/node_modules/handlebars/dist/cjs/handlebars/compiler/javascript-compiler.js:254:23), <anonymous>:8:31)
    at prog (/node_modules/handlebars/dist/cjs/handlebars/runtime.js:221:12)
    at execIteration (/node_modules/handlebars/dist/cjs/handlebars/helpers/each.js:51:19)
    at Object.<anonymous> (/node_modules/handlebars/dist/cjs/handlebars/helpers/each.js:61:13)
    at Object.eval [as main] (eval at createFunctionContext (/node_modules/handlebars/dist/cjs/handlebars/compiler/javascript-compiler.js:254:23), <anonymous>:5:34)
    at main (/node_modules/handlebars/dist/cjs/handlebars/runtime.js:175:32)
    at Object.ret (/node_modules/handlebars/dist/cjs/handlebars/runtime.js:178:12)
    at Object.ret [as build-table-create-list] (/node_modules/handlebars/dist/cjs/handlebars/compiler/compiler.js:526:21)
    at Object.invokePartialWrapper [as invokePartial] (/node_modules/handlebars/dist/cjs/handlebars/runtime.js:72:46)
    at Object.eval [as main] (eval at createFunctionContext (/node_modules/handlebars/dist/cjs/handlebars/compiler/javascript-compiler.js:254:23), <anonymous>:6:28)
    at main (/node_modules/handlebars/dist/cjs/handlebars/runtime.js:175:32)

I can provide the models if needed

@optii 🤔Thank you for posting this issue -- I wonder if the existence of the tables is required -- What you're doing is definitely a major use-case (seed the db with tables / correct columns and types!)

So this seems to stem from a joi schema that has a key named email in it:
Doesnt work:
Joi.object({
   email: Joi.string().email()
})

Does work:
Joi.object({
   test: Joi.string().email()
})

Update to this, the key email has nothing to do with it, this case seems to occur whenever a key is identical to the table name.
For example this will fail:
class Email extends Model {

   static get tableNamee() {
        return 'email';
   }

   static get joiSchema(){
        return Joi.object({ email: Joi.string().email() });
   }
}

Confirmed that this is reproducible ^^^

Done some debugging concerning this, all the generated objects seem to be correct and seem to have boiled down the problem to a context problem in the handlebars template, here is what i've "found":
I've run my tests against the Dog model that i added the key Dog to.
line 1 evaluates to ['Dog'] which seems correct to me
this context in the first {{#each }} (above) evalutes to 'Dog' as expected
line 4 evaluates to [ 'id', 'favoriteToy', 'name', 'Dog', 'ownerId' ] again this seems good to me
in this {{#each }} however things seem break:

this equals the correct values on each iteration. in order 'id' 'favoriteToy' 'name' 'Dog' 'ownerId' (again this looks good)
../this evaluates to Dog for each of the values except for when this equals Dog and in this case ../this evaluates to the @root object instead of Dog

I can't seem to work out why when this equals Dog the parent this is changed. I'm going to keep looking into this but if you've got any ideas :+1:

Okay seem to have a fix for this, maybe it's due to a circular reference ? I'll create a PR


red color filenames in "Search files by name" dropdown to match tabs

would be great if filename colors in the Search dropdown matched the colors in the file tabs
inconsistent, more mentally taxing to navigate:

consistent, easier to immediately visually see where i want to go, instead of having to read every file name:

often times, the main files i'm working on have errors and are colored red in the files tabs. this is really helpful. but i'm rarely moving my my mouse to click on tabs.  i do Cmd-P to open the dropdown of all my files and usually scroll from there.
it would make it easier to target my current working files if they showed up red in this dropdown, when they're red in the tabs.

/duplicate https://github.com/microsoft/vscode/issues/90301

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Enable to add custom layers (v-score for example)

JLPCB allows custom panelization which can be done on the user's side. They allow users to provide custom layer, for example vscore and they grove it out when given instructions to do so. However there is no way in this plugin to let consider (generate such layers)
Describe the solution you'd like
Have a 'manage layer' button which would could have checkboxes which layers would be considered. KiKit panelization plugin by default outputs of the v-cut information into the 'User.Comments' layer, this could be the default layer to be considered.

Is a custom selection actually needed or would it be sufficiant to just output the User.Comments by default?
A additional exported layer would not hurt even if its empty, right?

Resolved by #161


[instrumentation] convenience methods for chain spans

Spit balling here:
from openinference.instrumentation import agent, chain, trace

@agent(name="calculator-agent")
def agent():
   ....

@chain
def apply_parameters():
   ....

In addition I may want to imparatively create a span inside of a function body:
tracer = tracer_provider.get_tracer(__name__)

def some_llm_function(input):
   tracer.start_as_active_span(
                               kind="chain"
                                input) as span:
              # do work
               stan.set_output(output)


Clean up legacy code

Some scripts were added for backward compatibility and smooth upgrades more than a year ago.
Now they just increase complexity and do give any value.

I am running windows 8.1 and tried to run your script, but failed.  Should I upgrade to Windows 10?
I desperately need your script running because I need Varnish running on Windows environment.  And your scripts is the only hope I have now. Should I run 'Vagrant up' before executing 'init_project.sh'?  I got two VM running if I did 'Vagrant up' before 'init_project.sh'.   if I run 'Vagrant up' from command prompt as administrator, then there will be no VM, but still has many red line errors.  Please advise me.  Your earliest attention will be much appreciated.

Hi @ghost, I tested this project on Windows 10 some time ago and it worked.
Please do not run 'vagrant up' before 'init_project.sh'. Make sure to use git bash 2.7+ instead of native windows CLI because all scripts are written in bash.
Sorry for the delayed response.


rhash.c:448]: (error) Resource leak: fd

Source code is
if ((fd = fopen(filepath, "rb")) == NULL) return -1;
if ((ctx = rhash_init(hash_id)) == NULL) return -1;

Suggest add call to fclose( fd) inside last if.

Thanks!
Fixed by 8c332d48ec39dccf52d809cbac5673675f94533a.

The fix is included into RHash v1.3.6.


Video Conference Firefox

Hello,
I have an issue concerning Firefox during video conference.
When I call Chrome to Chrome, video works well.

Firefox get only audio. But When I record video, video is OK.
Why Firefox add only audio tag ?
Have you an idea ?
Thanks a lot.
Best regards
Vince

解决了吗？


Nightlies failing on ModelUnderstanding

The nightlies failed over the weekend on model-understanding.
The issue seems to be related to numpy, which had a release over the weekend along with Pandas, plotly, and seaborn. It started Friday night, after Dask had its release.
plot_data = fig.to_dict()["data"][0]
        assert plot_data["type"] == "bar"
>       assert plot_data["x"] == ["0", "1", "2"]
E       ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

Thanks for filing. I think first step is to merge this deps update PR as soon as @chukarsten finishes with the v0.30.2 release


Add deprecation notice for system.swap on windows

What does this PR do?
Adds deprecation notice to releasenotes.

our plans have changed: we'll re-introduce the system.mem.swap.* metrics on v6 because we've realized the system.swap.* in v6 were not exactly the same as v5's system.mem.swap.* metrics
Closing

(See follow-up here: https://github.com/DataDog/datadog-agent/pull/3582)


Suggestion to scale out our community : Create an organisation managed by dominikh

Hi @dominikh,
I need you to support this project even if you don't work full time on this project. I need you work as professionnal and scalling this community could be great !
Maybe, you could create a github organisation to manage this project and nominate maintainer.
Thank you for your answer,
Michael

I need you work as professionnal

I'd be happy to discuss pricing options for commercial support.

Maybe, you could create a github organisation to manage this project and nominate maintainer.

Instead of proposing a solution, start by describing the problem. Which problem that currently exists are you trying to solve? Note that I am asking for actual problems, not hypothetical ones.

I need you work as professionnal
My bad, sorry for my english.  I'm a professional who use your mode.

Which problem that currently exists are you trying to solve?
There is many issues/PR open that could help your work.

Creating an organisation wouldn't change that. Anyone is welcome to work on issues that affect them and send PRs; and I process PRs as time permits. If I wanted to, I could add collaborators to this repository, without the need for an organisation; but I don't want to. All decisions, especially code changes, would ultimately still have to go through me. Furthermore, making the organizational structure of the project more complex will waste more time on administration.
I realize that I haven't been investing terribly much time in go-mode recently. However, the project is overall in a pretty good spot. None of the open issues and PRs are all that important, they're mostly "nice to have" things, or about odd corner cases. Additionally, it's really a small project, not one that needs many maintainers. The project is perfectly usable on a day to day basis, and plenty of professionals are doing so.
tl;dr: you're always welcome to make contributions, but there's no need for an organisation or extra maintainers.

Sounds good ! :-)
Thank you for your answer.


Weird rendering artifacts with Path (something not supported?)

I have a problem rendering Path in React Native even though it works in web no problem, so I'm wondering if something in that Path is not working. Most icons are fine, but three of them have weird artifacts. At the moment this happens on Android, can't test on iOS.
Here's the code for one of the icons that is not working
<Svg viewBox="0 0 44 44" width="44" height="44">
  <G fillRule="evenodd">
    <Path d="M22 38.775C12.75 38.775 5.225 31.25 5.225 22 5.225 12.75 12.75 5.225 22 5.225c9.25 0 16.775 7.525 16.775 16.775 0 9.25-7.525 16.775-16.775 16.775m0-34.632c-9.846 0-17.857 8.01-17.857 17.857 0 9.846 8.01 17.857 17.857 17.857 9.846 0 17.857-8.01 17.857-17.857 0-9.846-8.01-17.857-17.857-17.857m-6.926 12.325h13.552v7.027c0 1.094-.891 1.985-1.985 1.985h-9.583a1.987 1.987 0 0 1-1.984-1.985v-7.027zm-1.083 7.027a3.07 3.07 0 0 0 3.067 3.067h9.583a3.07 3.07 0 0 0 3.067-3.067v-7.027h2.336v-1.083H14.532c-.043 0-.08.016-.12.024v-.024h-2.878v1.083h2.457v7.027zm3.002-13.087h9.713c1.002 0 1.828.772 1.913 1.753H15.08a1.922 1.922 0 0 1 1.912-1.753zm3.394-1.082h2.926v-.823h-2.926v.823zm-5.854 3.918h14.634a.541.541 0 0 0 .541-.542v-.375a3.005 3.005 0 0 0-3.002-3.001h-2.312V7.962a.54.54 0 0 0-.54-.54h-4.008a.54.54 0 0 0-.541.54v1.364h-2.312a3.005 3.005 0 0 0-3.001 3v.376a.54.54 0 0 0 .541.542zm8.82 18.02l-9.29.348a.593.593 0 0 1-.02-1.185l9.31.348v.49zm.678-1.524a5.691 5.691 0 0 1 4.616-2.34h3.518v1.082h-3.518a4.628 4.628 0 0 0-4.144 2.538 4.627 4.627 0 0 0 4.144 2.536h3.518v1.083h-3.518a5.693 5.693 0 0 1-4.616-2.34c-.039.01-.074.025-.116.027l-9.833.368a1.68 1.68 0 0 1-1.695-1.674c0-.924.753-1.675 1.676-1.675l9.852.368c.<IP_ADDRESS>.116.027zm3.05.833V29.49h5.085v1.083H27.08zm0 1.976v-1.083h5.085v1.083H27.08z" />
  </G>
</Svg>

On React Native this renders

And rendering on the web

I wonder why would this happen, might it be because of fillRule?
"react-native": "0.55.4",
"react-native-svg": "^6.3.1",

Fixed this, by exporting the icon using svgo plugin for sketch. Still not sure what was wrong with the original export though


Make examples section nicer.

Makes the example section nicer by including a bring explanation. Still include the screen cast, with comment that it is older.

@saroad2  These are just doc changes and are good to go. They fail CI due to existing flake8 issues in the code base.

Make changes as @tachyondecay suggested.


.NET5 Forms: Cancel edit on ListView triggers event AfterLabelEdit with args.Label is "" instead of null

The behavior of entering the label edit mode and leaving it without change or escape button was changed. In .NET-Framework and .NET-Core 3.1 the event "AfterLabelEdit" provides "LabelEditEventArgs" where the property "Label" is "null". In .NET5 the empty string is returned. So for now it is not possible to detect edit operation cancelation any more. The previous behavior should be established as it is also declared by the  event documentation.
Find attached a little demo with .NET5 and Core3.1 to validate different behavior.
WinFormsApp1.zip

Hey @RussKie, can you transfer please?


lun_write_align_histo sometimes does not contains value

A note for the community

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please let us know in a comment

Problem
Prometheus Agent somethimes throws an error:
expected value after metric, got "\n" ("INVALID") while parsing: "lun_write_align_histo{datacenter=\"X\",cluster=\"Y3\",lun=\"volume-daaeceef-b2f1-40eb-9c67-02f116bde267\",volume=\"cloud_y3_prod_vol2\",svm=\"iSCSI01Z3\",metric=\"1\"} \n"
# or:
expected value after metric, got "\n" ("INVALID") while parsing: "lun_write_align_histo{cluster=\"Y3\",datacenter=\"X\",lun=\"volume-ba544526-9c1b-4b01-b739-5d970f4132bf\",volume=\"cloud_y3_prod_vol2\",svm=\"iSCSI01Z3\",metric=\"2\"} \n"

and by directly querying the metrics provided by the application:
[PROD]<EMAIL_ADDRESS>~ # curl -s <IP_ADDRESS>:12006/metrics | grep -P "\}\s$"
lun_write_align_histo{datacenter="X",cluster="Y3",lun="volume-d198ff75-5472-4cef-ab95-18944d8347d5",svm="iSCSI01Z3",volume="cloud_y3_prod_vol2",metric="1"}
[PROD]<EMAIL_ADDRESS>~ # curl -s <IP_ADDRESS>:12006/metrics | wc -l
10253

This seems to have a negative effect on any querying of metrics, for the reason that another metric has holes in time.

I did not find any problems in the files /var/log/harvest/poller_*.log
Configuration
Exporters:
    prom-netapp01:
        exporter: Prometheus
        port: 12001
    prom-netapp02:
        exporter: Prometheus
        port: 12002
    prom-netapp03:
        exporter: Prometheus
        port: 12003
    prom-mgt1_z1_netapp:
        exporter: Prometheus
        port: 12004
    prom-mgt1_z2_netapp:
        exporter: Prometheus
        port: 12005
    prom-mgt1_z3_netapp:
        exporter: Prometheus
        port: 12006
Defaults:
    collectors:
        - Zapi
        - ZapiPerf
        - Rest
        - Ems
    use_insecure_tls: false
Pollers:
    netapp01.contoso.com:
        datacenter: X
        addr: -REDACTED-
        auth_style: basic_auth
        username: -REDACTED-
        password: -REDACTED-
        use_insecure_tls: true
        exporters:
            - prom-netapp01
    netapp02.contoso.com:
        datacenter: X
        addr: -REDACTED-
        auth_style: basic_auth
        username: -REDACTED-
        password: -REDACTED-
        use_insecure_tls: true
        exporters:
            - prom-netapp02
    netapp03.contoso.com:
        datacenter: X
        addr: -REDACTED-
        auth_style: basic_auth
        username: -REDACTED-
        password: -REDACTED-
        use_insecure_tls: true
        exporters:
            - prom-netapp03
    mgt1.krk1.contoso.com:
        datacenter: X
        addr: -REDACTED-
        auth_style: basic_auth
        username: -REDACTED-
        password: -REDACTED-
        use_insecure_tls: true
        exporters:
            - prom-mgt1_z1_netapp
    mgt1.krk2.prod.contoso.com:
        datacenter: X
        addr: -REDACTED-
        auth_style: basic_auth
        username: -REDACTED-
        password: -REDACTED-
        use_insecure_tls: true
        exporters:
            - prom-mgt1_z2_netapp
    mgt1.krk3.prod.contoso.com:
        datacenter: X
        addr: -REDACTED-
        auth_style: basic_auth
        username: -REDACTED-
        password: -REDACTED-
        use_insecure_tls: true
        exporters:
            - prom-mgt1_z3_netapp

Poller
mgt1.krk3.prod.contoso.com
Version
harvest version 23.08.0-1 (commit 874a1f87) (build date 2023-08-21T08:38:04-0400) linux/amd64
Poller logs
No response
OS and platform
CentOS Linux release 8.5.2111
ONTAP or StorageGRID version
2023/09/27 17:28:06 configuration error => poller [u2] not found
Additional Context
Model: AFF-A250
NetApp Release 9.12.1P5: Fri Jul 21 09:05:49 UTC 2023 ()
References
No response

Hi @LukaszWasko sounds like this may be intermittent?
For the cluster in question, can you run the following and paste the results?
(replace sar with the name of your poller)
bin/harvest zapi -p sar show data --object lun --counter write_align_histo

Could you send your log files for the poller in question? We should log something when this happens.

Closing.
@LukaszWasko please reopen if you see this issue again and provide info in https://github.com/NetApp/harvest/issues/2383#issuecomment-1737674582. Thanks


gather inspiration from the best flakes

Seen a lot of professionally written flakes, to name a few

https://git.sr.ht/~afontaine/home/tree
https://git.sr.ht/~bwolf/dotfiles/tree
https://github.com/Mic92/dotfiles
https://github.com/konradmalik/dotfiles - Konrad even enabled some CI/CD within his configuration with GitHub Actions; might help on #2

https://konradmalik.com/posts/2023/02/sops-nix-simple-secrets-management-for-nix/

https://github.com/EmergentMind/nix-config

https://unmovedcentre.com/technology/2024/03/22/secrets-management.html

example structure for multihost configuration

https://github.com/mwdavisii/nyx/tree/main/home
https://github.com/BirdeeHub/birdeeSystems/blob/582fe0c1123395c8cc0aa3a1bf6dfa3ce65dcfbb/flake.nix#L91-L115
https://github.com/BirdeeHub/birdeeSystems/tree/main/systems/PCs
https://github.com/lucasfabre/nixos-config/tree/main/system
https://github.com/mwdavisii/nyx
https://github.com/mwdavisii/nyx/tree/main/home
🌟 https://github.com/infinisil/system

https://github.com/gytis-ivaskevicius/flake-utils-plus
https://github.com/reckenrode/nixos-configs

In addition, if we're to define options within the flake, here's a list of supported types by Nix

https://github.com/NixOS/nixpkgs/blob/ea24372d132cf854937ef41d0d4091ca0e8f7ee9/lib/types.nix#L224-L1049
Official Nixpkgs manual
Module system deep dive

Some conversation from the forum of people trying to modularize home-manager configuration

Is this a good way to modularize home manager home.nix for home/work?

Conditional Implementation

Module System and Custom Options

# ./foo.nix
{ config, lib, pkgs, ... }:

with lib;

let
  cfg = config.programs.foo;
in {
  options.programs.foo = {
    enable = mkEnableOption "the foo program";

    package = mkOption {
      type = types.package;
      default = pkgs.hello;
      defaultText = literalExpression "pkgs.hello";
      description = "foo package to use.";
    };

    extraConfig = mkOption {
      default = "";
      example = ''
        foo bar
      '';
      type = types.lines;
      description = ''
        Extra settings for foo.
      '';
    };
  };

  config = mkIf cfg.enable {
    home.packages = [ cfg.package ];
    xdg.configFile."foo/foorc" = mkIf (cfg.extraConfig != "") {
      text = ''
        # Generated by Home Manager.

        ${cfg.extraConfig}
      '';
    };
  };
}

Option definitions are generally straight-forward bindings of values to option names

config = if config.services.httpd.enable then {
  environment.systemPackages = [ ... ];
  ...
} else {};

asked the Discord community for proposals and I've got this

https://git.proot.pl/Wroclaw/nixos-configuration

Solved in #7


Documentation for allowPartiallySucceededBuilds and allowFailedBuilds inputs are missing under the Yaml snippet

Documentation for allowPartiallySucceededBuilds and allowFailedBuilds inputs are missing under the Yaml snippet.

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

ID: b03d67d0-8738-72e6-dbe7-324c1784d4fc
Version Independent ID: bbb4d774-cd98-3ecb-7ccf-5f49e6f2b425
Content: Download Pipeline Artifacts task - Azure Pipelines
Content Source: docs/pipelines/tasks/utility/download-pipeline-artifact.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

Thanks for letting us know. This issue is fixed in our new task reference here:
https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/download-pipeline-artifact-v2?view=azure-pipelines&viewFallbackFrom=azure-devops
Please check it out and let us know what you think. Thank you.


Need to check Voice and Filter sizes when creating a new CRT

It is possible to create a CRT that overflows the available space in the Synergy address space.  Need to keep track of Filters and Voice sizes as we build the CRT and refuse to build a CRT that requires more space than will be available.
Unfortunately, the Synergy firmware will gladly load a "too big" CRT and overwrite parts of the DATA section of the address space -- and return a "success" status to Synergize :)   So can't rely on the firmware doing range checks!

Fixed for 2.4.0

Fixed for 2.4.0


Pass all 'other' event types to single function in makeRunnerCallback

As suggested in https://github.com/dodona-edu/papyros/pull/112#discussion_r844075522

However, maybe you want to offer a hybrid approach, i.e. if a callback for the type exists, use that callback, otherwise use the catch-all?

Sounds overcomplicated for users.


Hacker Face Vulnerability

Thank you for deciding to make a vulnerability report. To fix your issue, please answer these questions:
Which version are you using?
Some versions are not supported by security updates because of old age. To see the supported ones, click here.
v5.1.2 tag
What is happening?
Clearly describe what happened. If you can, please take screenshots.
On startup, a hacker face appears!

This has been added to our security database. View it here.


Infinite durability doesnt work?

I installed it just as shown, yet my weapons break, the mod is enabled... What could be wrong?

I installed it just as shown, yet my weapons break, the mod is enabled... What could be wrong?

Lot of cheats seems to don't work, i'm sorry, check here https://gamebanana.com/mods/games/7617 if theres is a better mod to do that, i'll test every cheat mod and remove the broken ones
Just before, do you play in 1.1.0 ? Maybe the memory address that the cheat patch change from the version.

I installed it just as shown, yet my weapons break, the mod is enabled... What could be wrong?

Lot of cheats seems to don't work, i'm sorry, check here https://gamebanana.com/mods/games/7617 if theres is a better mod to do that, i'll test every cheat mod and remove the broken ones
Just before, do you play in 1.1.0 ? Maybe the memory address that the cheat patch change from the version.

Yeah it's the 1.1.0 version. Thanks so much for the link, i looked at that website earlier but there's no mods to disable durability completely yet, it's just a matter of time though. Thanks so much for a quick response! Have a good day

Can confirm the mod above works well.

Have you tried with the cheats listed in this repo ?
Could be what you're looking for, I personally don't use them so I can't tell you if it works for sure but they seem to be updated fairly frequently.

Have you tried with the cheats listed in this repo ? Could be what you're looking for, I personally don't use them so I can't tell you if it works for sure but they seem to be updated fairly frequently.

No need, solved it above.


[Bug]: [Auto layout] No scroll seen in Deploy mode

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When we deploy a page with few widgets which need a scroll, we are not seeing a scroll
https://user-images.githubusercontent.com/104895602/219303326-69e774fe-2360-4b9e-8f97-aa0a7a967021.mp4
Steps To Reproduce

DnD about 10 widgets in the Auto layout Canvas
Switch to Deploy mode
Observe No scroll is seen

Public Sample App
No response
Issue video log
No response
Version
Deploy preview

Scroll is seen in Deploy mode, working fine, QA done @marks0351


"error: toolchain 'nightly-foo' is not installed" is confusing

This "not installed" message happens when the toolchain parser fails to parse the name and then considers it a "custom" toolchain. After that, the operation fails, and the reason is because there is no custom toolchain with that name.
It's confusing though because the user may have typo'd a channel name, not expecting it to be installed.

This is happening with curl https://sh.rustup.rs -sSf | sh as well on Arch Linux 64bit.

@Hoverbear it happens at install time on arch? That's weird...

Yes it seems to be working now though. Perhaps it was a connection error.

I am getting error: toolchain 'nightly' is not installed on two different platforms (OSX, Linux) after I do a curl https://sh.rustup.rs -sSf | sh
Machines are on different networks, so I am guessing connection problem is from rustup.rs server?
Even customizing options and selecting stable produces the same error with nightly message!

I'm experiencing the same problem as @gistub on my Mac. Here's a screenshot:

@Lisoph the non-existence of the files is expected (though certainly annoying for debugging). rustup should probably have a mode where it doesn't clean up temp files.
Well, this is pretty terrible bug. I'll try to look into it soon. Related to https://github.com/rust-lang-nursery/rustup.rs/issues/275 and https://github.com/rust-lang-nursery/rustup.rs/issues/277.

I'm seeing this as well:
error: toolchain 'stable' is not installed
rustup: command failed: /tmp/tmp.jBjZbBTkrb/rustup-init

I was using multirust previously and did not delete any directories.
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

@Lisoph @gistub FWIW I had the issue both of you. I had previously had multirust and I'd following the prompts from rustup to remote meta prior to installation but I still had the same error. For me, removing the ~/.multirust directory completely, and then re-running rustup-init fixed the problem for me.

Great digging @pauljt


German localization

initial german translation

Thanks a lot for taking the time to contribute a German localization!
Looks great, the only thing I noticed is the translations for zoom, rotation and layout are the same words as in English. I don't speak German and don't know if the German word is the same (or the English word is more commonly used in UIs) so I wanted to make sure that's correct and not that you didn't notice that you skipped them (that's happened to me more than once :)).

Perfect, I thought that may be the case but wanted to make sure.
I'll merge the PR and will try to make a build and a new release as soon as I have the time.
Thanks!

The German translation is now available in the latest release (2.4.3): https://github.com/binarynonsense/comic-book-reader/releases/tag/v2.4.3


auth0.Connection constructor strategy_version appears to be ignored

What happened?
The constructor argument of auth0.Connection strategy_version and corresponding Output appear to be ignored.
It does, however, work when using the options constructor arg/output.
Steps to reproduce
Create a connection like so:
    microsoft = auth0.Connection(
        'microsoft',
        enabled_clients=[client.id],
        strategy='windowslive',
        strategy_version=2
    )

does NOT create an Auth0 connection with strategy version 2 (it uses default strategy version 1). Similiarily, looking up an existing connection
auth0.Connection.get('msft', id=...)

does not return a strategy_version in its Outputs.
Expected Behavior
Auth0 connection created with strategy_version set to 2
Actual Behavior
Auth0 connection created with (default?) strategy_version set to 1
Versions used
CLI
Version      3.35.2
Go Version   go1.17.11
Go Compiler  gc
Host
OS       debian
Version  bookworm/sid
Arch     x86_64
Auth0 version: pulumi_auth0-2.11.0
Additional context
To actually set strategy version, one must use options. (i.e., the following WORKS):
    microsoft = auth0.Connection(
        'microsoft2',
        enabled_clients=[client.id],
        strategy='windowslive',
        options=auth0.ConnectionOptionsArgs(
            strategy_version=2
        ),
    )

Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Hi @ryanrasti
I apologise for the issue here - this is due to an old version of the schema in terraform that is migrating the state of the property. This should be omitted - I will get a new version of the provider upgraded and taken care of
Paul

Hi @ryanrasti - can you try the latest version of this provider and see if the issue persists? Thank you for your patience. 🙇♀

@guineveresaenger
Hi! I am using typescript<EMAIL_ADDRESS>and when I import a Connection with options.strategyVersion: 2, it gets ignored and imported with strategyVersion 0. So it does not seem to have worked.

It looks like upstream just merged a fix in this area: https://github.com/auth0/terraform-provider-auth0/pull/1024. As soon as they make a release, we'll update the pulumi provider.


Error while linting the checkout isml

I've just copied the checkout/checkout.isml in our custom storefront cartridge and i receive this error:
Please check if your node version is >=10.0.0. If it is, please report the above issues to https://github.com/FabiowQuixada/isml-linter and add these files to the ignore list while a fix is not available.
I'm with node 12 version

Hey @pasqualeper86 , thanks for reporting!
Can you please add more details to the issue you're having? For example:

Is there any other message before "Please check if your node version..."?
What is your ISML Linter configuration file content?
What ISML Linter version are you using?

I wasn't able to reproduce the issue you're reporting, please update ISML Linter to the latest version and let me know if the issue still occurs.
Thanks!

Hi @FabiowQuixada, simply updating the package the error is solved.
Thanks!


cant exit

Environment
knex:
latest
db:
Oracle Database 11g Express Edition Release <IP_ADDRESS>.0 - 64bit Production
OS:
osx 10.14.1
node:
10.9.0
const knex = require('knex');

const conn = knex({
    client: 'oracledb',
    connection: {
        connectString: 'localhost:9999/XE',
        user: 'utest',
        password: 'utestpwd',
        database: 'utest',
    }
});

conn.raw('select * from users').then(result => {
    console.log('result: ', result);
    return;
    console.log('end');
    process.exit(0);
}).catch(function (e) {
    console.log(e);
    process.exit(1);
});

this code can print the result, but it cant exit

you need to call conn.destroy() to release the pool. Also your process.exit(0) line is not executed.

@elhigu thank u


Add missing translations in messages

What changes were proposed in this pull request?
Added some missing values from merge
How was this patch tested?
Some UI tests failing after https://github.com/apache/ambari/pull/617. Will be fixed in future commits.

This is a trivial change and doesn't require a review. Merging

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/1112/
Test FAILed.
Test FAILured.


Wrong logic for save file

I want to save to the internal memory of the phone and this line does not allow me to do it
File directory = new File(Environment.getExternalStorageDirectory(), path);
Let the user decide where to save
File directory = new File(path);
thanks

Hi. Yes this will be now implemented because of the new restrictions of AndroidQ.
PixelShot will undergo a small refactoring. Stay tuned and thanks for the tip

Hey @evansgelist The library has been under a bigger refactoring and your feature requests is now also included. Read more about the changes in the readme


Links to download are not working

Hi, I'm not sure if it is right place to report it, but download links for
http://rubyinstaller.org/downloads/ does't work at all.
For a past few days when I'm trying to download windows binaries i got ERR_NAME_NOT_RESOLVED.
Is the site still alive?

It indeed is. All of the downloads are hosted from Bintray.
https://bintray.com/oneclick/rubyinstaller/rubyinstaller
Check to see if that link works.

Yep, works just fine.


Add llama 3 license

I hope that's all good now 🙈

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


chore(nginx-ingress): fix hpa issue

This will fix the issue where the HPA isn't able to read the metrics even when the resources of the controllers are set because the resources of the default-backend aren't set and both are using the same selectors

Selector labels on deployments are immutable and cannot be updated. This would be a major breaking change. Currently, there is work in progress to move this chart into the ingress-nginx repo and we are taking this opportunity to make breaking changes like this. Feel free to add this change there if it is not already fixed.

https://github.com/kubernetes/ingress-nginx/tree/master/charts/ingress-nginx
https://github.com/kubernetes/ingress-nginx/issues/5161

@ChiefAlexander what if we make it as optional so people who will be using the chart for the first time they have the ability to allow it.

That would be fine by me
/ok-to-test

@ChiefAlexander I have updated the PR accordingly, so please have a look and approve it if it is okay

/retest

/retest

/retest

/lgtm

/retest

/retest

Unfortunately this introduced a regression that broke the connection between the controller service and the pods (the selector no longer matches).  Can you please revert this change or fix forward?  Also, please add a regression test so that this does not recur.

This is a regression. Breaks service monitor for instance #21873. Only half of the component labels have been changed why? If to change then to change all labels... Moreover app.kubernetes.io/component breaks prometheus and prometheus operator servicemonitor.


🐛 [Bug] TRT Error when compiling ViT with Dynamic Shape

Bug Description

To Reproduce
Minimal reproducible code：
import torch
import torch_tensorrt
from transformers import ViTForImageClassification

model = ViTForImageClassification.from_pretrained('google/vit-base-patch16-224')
model = model.eval().cuda()

inputs = [
    torch_tensorrt.Input(
        min_shape=[1, 3, 224, 224],
        opt_shape=[4, 3, 224, 224],
        max_shape=[16, 3, 224, 224],
        dtype=torch.float32
    )
]
# inputs = torch_tensorrt.Input(shape=[2, 3, 224, 224], dtype=torch.float32)
trt_gm = torch_tensorrt.compile(model, "dynamo", inputs)

Expected behavior
Model should compile with Dynamic shapes.
But I got error:
WARNING:torch_tensorrt.dynamo._compiler:Node scaled_dot_product_attention of op type call_function does not have metadata. This could sometimes lead to undefined behavior.
WARNING:torch_tensorrt.dynamo._compiler:Some nodes do not have metadata (shape and dtype information). This could lead to problems sometimes if the graph has PyTorch and TensorRT segments.
INFO:torch_tensorrt.dynamo._compiler:Partitioning the graph via the fast partitioner
INFO:torch_tensorrt [TensorRT Conversion Context]:[MemUsageChange] Init CUDA: CPU +489, GPU +0, now: CPU 6268, GPU 2121 (MiB)
INFO:torch_tensorrt [TensorRT Conversion Context]:[MemUsageChange] Init builder kernel library: CPU +1906, GPU +354, now: CPU 8327, GPU 2475 (MiB)
WARNING:torch_tensorrt [TensorRT Conversion Context]:CUDA lazy loading is not enabled. Enabling it can significantly reduce device memory usage and speed up TensorRT initialization. See "Lazy Loading" section of CUDA documentation https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#lazy-loading
WARNING:torch_tensorrt.dynamo.conversion.converter_utils:Detected unparsable type in node formatting: <class 'torch.SymInt'>
WARNING:torch_tensorrt.dynamo.conversion.converter_utils:Detected unparsable type in node formatting: <class 'torch.SymInt'>
WARNING:torch_tensorrt.dynamo.conversion.converter_utils:Detected unparsable type in node formatting: <class 'torch.SymInt'>
INFO:torch_tensorrt.dynamo.conversion._TRTInterpreter:TRT INetwork construction elapsed time: 0:00:00.058611
INFO:torch_tensorrt [TensorRT Conversion Context]:Global timing cache in use. Profiling results in this builder pass will be stored.
ERROR:torch_tensorrt [TensorRT Conversion Context]:IBuilder::buildSerializedNetwork: Error Code 4: Internal Error (kOPT values for profile 0 violate shape constraints: [SLICE]-[aten_ops.expand.default]-[/vit_embeddings/expand]: ISliceLayer has out of bounds access on axis 0 Condition '<' violated: 3 >= 1.)
Traceback (most recent call last):
  File "/mnt/bn/hukongtao-infer-speed/mlx/users/kongtao.hu/codebase/EasyGuard_0617/speed_vit_test.py", line 27, in <module>
    trt_gm = torch_tensorrt.compile(model, "dynamo", inputs)
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/_compile.py", line 250, in compile
    trt_graph_module = dynamo_compile(
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/dynamo/_compiler.py", line 243, in compile
    trt_gm = compile_module(gm, inputs, settings)
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/dynamo/_compiler.py", line 431, in compile_module
    trt_module = convert_module(
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/dynamo/conversion/_conversion.py", line 107, in convert_module
    interpreter_result = interpret_module_to_result(module, inputs, settings)
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/dynamo/conversion/_conversion.py", line 88, in interpret_module_to_result
    interpreter_result = interpreter.run()
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/dynamo/conversion/_TRTInterpreter.py", line 350, in run
    assert serialized_engine
AssertionError

Environment

Additional context
Reference official documentation：
https://pytorch.org/TensorRT/user_guide/dynamic_shapes.html

Thanks for the repro. I've fixed this bug in this PR : https://github.com/pytorch/TensorRT/pull/3019

thank you for your reply~
I use the latest version and modify the code according to your PR， and I got another error：
WARNING:torch_tensorrt.dynamo.conversion.converter_utils:Detected unparsable type in node formatting: <class 'torch.SymInt'>
WARNING:torch_tensorrt.dynamo.conversion.converter_utils:Detected unparsable type in node formatting: <class 'torch.SymInt'>
INFO:torch_tensorrt.dynamo.conversion._TRTInterpreter:TRT INetwork construction elapsed time: 0:00:00.039768
INFO:torch_tensorrt [TensorRT Conversion Context]:Global timing cache in use. Profiling results in this builder pass will be stored.
INFO:torch_tensorrt [TensorRT Conversion Context]:Detected 1 inputs and 6 output network tensors.
INFO:torch_tensorrt [TensorRT Conversion Context]:Total Host Persistent Memory: 5552
INFO:torch_tensorrt [TensorRT Conversion Context]:Total Device Persistent Memory: 0
INFO:torch_tensorrt [TensorRT Conversion Context]:Total Scratch Memory: 48365568
INFO:torch_tensorrt [TensorRT Conversion Context]:[BlockAssignment] Started assigning block shifts. This will take 4 steps to complete.
INFO:torch_tensorrt [TensorRT Conversion Context]:[BlockAssignment] Algorithm ShiftNTopDown took 0.031924ms to assign 2 blocks to 4 nodes requiring 61210624 bytes.
INFO:torch_tensorrt [TensorRT Conversion Context]:Total Activation Memory: 61210624
INFO:torch_tensorrt [TensorRT Conversion Context]:Total Weights Memory: 10853632
INFO:torch_tensorrt [TensorRT Conversion Context]:Engine generation completed in 0.123574 seconds.
INFO:torch_tensorrt [TensorRT Conversion Context]:[MemUsageStats] Peak memory usage of TRT CPU/GPU memory allocators: CPU 3 MiB, GPU 100 MiB
INFO:torch_tensorrt [TensorRT Conversion Context]:[MemUsageStats] Peak memory usage during Engine building and serialization: CPU: 9363 MiB
INFO:torch_tensorrt.dynamo.conversion._TRTInterpreter:Build TRT engine elapsed time: 0:00:00.135388
INFO:torch_tensorrt.dynamo.conversion._TRTInterpreter:TRT Engine uses: 11179132 bytes of Memory
INFO:torch_tensorrt [TensorRT Conversion Context]:Serialized 1496 bytes of code generator cache.
INFO:torch_tensorrt [TensorRT Conversion Context]:Serialized 157388 bytes of compilation cache.
INFO:torch_tensorrt [TensorRT Conversion Context]:Serialized 16 timing cache entries
WARNING: [Torch-TensorRT] - CUDA lazy loading is not enabled. Enabling it can significantly reduce device memory usage and speed up TensorRT initialization. See "Lazy Loading" section of CUDA documentation https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#lazy-loading
Traceback (most recent call last):
  File "/mnt/bn/hukongtao-infer-speed/mlx/users/kongtao.hu/codebase/EasyGuard_0617/speed_vit_test.py", line 17, in <module>
    trt_gm = torch_tensorrt.compile(model, "dynamo", inputs)
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/_compile.py", line 249, in compile
    trt_graph_module = dynamo_compile(
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/dynamo/_compiler.py", line 243, in compile
    trt_gm = compile_module(gm, inputs, settings)
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/dynamo/_compiler.py", line 383, in compile_module
    submodule_inputs = partitioning.construct_submodule_inputs(submodule)
  File "/usr/local/lib/python3.9/dist-packages/torch_tensorrt/dynamo/partitioning/common.py", line 124, in construct_submodule_inputs
    raise AssertionError(
AssertionError: Input scaled_dot_product_attention does not contain metadata. Please ensure you have exported the graph correctly

Looking forward to your reply

@Hukongtao This error is because our lowering pass was not copying over the metadata of the attention op to it's replaced variant. I've pushed a fix now to the same PR : https://github.com/pytorch/TensorRT/pull/3019. Can you give it a try ?

@Hukongtao This error is because our lowering pass was not copying over the metadata of the attention op to its replaced variant. I've pushed a fix now to the same PR : #3019. Can you give it a try ?

LGTM


Trigger test and preprod deploy from staging and main branches #1657

I think this is good? In theory we only need to specify the branch like you did - so it should work like this.


Question - Connecting to Rserve from outside Heroku?

I followed your example to instantiate an Rserve service in Heroku.  But I am not sure how I am suppose to connect to it outside of Heroku from an Rserve Client.  I am using a Python Rserve client, but I cannot seem to figure out what port it is listening to.  Do you have any sample code on how you connected to your Rserve example?

Hi @jvagg
I'm looking into this.

Any progress on that? I'm having the same issue

Finally I solved this problem launching the rserve in a different process. I upload a spring boot application that forks a process with the rserve script. I'm using this buildpack to provision the heroku instance with the R runtime. I also use the spring boot app as an interface to the R engine, so I can call my R functions from my frontend using a REST API


Check if SSL certs exist before using

autoproxy should check that a given SSL cert exists before trying to use it and warn the user if the specified file is not usable.
This should prevent nginx from failing to reload when a bad SSL cert is passed

closed by https://github.com/rehabstudio/docker-autoproxy/commit/964ce1aefa362ffc4fa60cf3ae800f3b579f86f0


Documentation: Cookie Policy

Hi,
thanks for sharing this great project! Looks awesome!
However for the cookie policy we have to add the name of cookies the scripts set on a page. I've noticed the following cookie from unami on the page I've added the tracking javascript:
umami.auth

Does the script set any other cookie?
Unfortunately I do not find the max-age/expiration date for that cookie. May I ask you how long is the cookie stored?
From what I see I would say the following:
Cookie name: unami.auth
Max age: 1 day

Maybe a feature request: Add the option to rename that cookie to have a more custom way of using unami.

The tracking script doesn't set any cookies. umami.auth is the login cookie for your umami application. You're probably seeing it on the tracked page because it points to the domain where your umami is installed.

Hi @mikecao , thnaks for clarification!
Indeed, visiting the page with the tracking script in incognito modus doesn't show the cookie. Great!
May I ask you how do you count unique visitors?

May I ask you how do you count unique visitors?

@mbecker I also had the same question; just found it's explained here:

https://github.com/mikecao/umami/issues/27#issuecomment-677344693
https://github.com/mikecao/umami/issues/155#issuecomment-702391188

Not sure if I am right, but is this discussion with @mikecao ? There the user `` said:

Maybe that's not fully compliant, I don't know, so I went ahead and removed any mention of GDPR from the website.

But the GDPR info is still in the docs - https://umami.is/docs/faq
So is umami GDPR compliant?

@bernhardh A lot of the code has changed since umami was first released. Initially it used localStorage by default and that could be interpreted by some as using a cookie. Now the default behavior is to not store anything, so to the best of my knowledge it is GDPR compliant.


omit warning of brew upgrade

In newly version of homebrew when you execute brew upgrade you will
get the following:

Warning: brew upgrade with no arguments will change behaviour soon!
It currently upgrades all formula but this will soon change to require '--all'.
Please update any workflows, documentation and scripts!

I did a bit of testing and it seems you can't override the --all argument by adding a formula name after it (also the source seems to back this up too). ie. brewu git would still attempt to upgrade all formulae, and I'm not sure that would be the intended outcome.
Perhaps brewu should be a function that passes along its arguments to brew upgrade unless no arguments were passed, and in that case pass --all.
brewu() {
    [[ $# -eq 0 ]] && brew upgrade --all || brew upgrade "$@"
}

A function is the only way to make it work. Also, I always run brew update  before brew upgrade. Might as well eliminate brewU.

@sorin-ionescu I actually personally use brewU more often then running those individually, so I do like to have it

brewu will be the new brewU.

Oh I see what you are saying. Right on, sounds good
On Thu, Apr 30, 2015, 4:02 PM Sorin Ionescu<EMAIL_ADDRESS>wrote:

brewu will be the new brewU.
—
Reply to this email directly or view it on GitHub
https://github.com/sorin-ionescu/prezto/pull/858#issuecomment-97994930.

@sorin-ionescu Eliminate brewU is a good idea, but you mean embed brew update into new brewu or invoke brew update manually before brewu? The later one seems inconvenient and behaves different from the old brewU.

Don't invoke manually. Merge into brewu.

I think that's it. @sorin-ionescu

bump @sorin-ionescu

Is there a case where you only want to upgrade just one package instead of all? If you don't want to upgrade a specific package, you just brew pin it. The following may be better.
alias brewu='brew update && brew upgrade --all'`

Both brew pin formulae and brew upgrade formulae are essential in different situations, one is usually the opposite to the other, upgrade is for fewer packages to upgrade, pin is for fewer packages to NOT upgrade.
pin formulae
              Pin the specified formulae, preventing them from being upgraded when issuing the brew upgrade --all command.  See  also
              unpin.

upgrade [--all] [install-options] [formulae]
              Upgrade outdated, unpinned brews.

              Options for the install command are also valid here.

              If  --all is passed, upgrade all formulae. This is currently the same behaviour as without --all but soon --all will be
              required to upgrade all formulae.

              If formulae are given, upgrade only the specified brews (but do so even if they are pinned; see pin, unpin).

I know. My use of brew is as follows: I want to upgrade all packages, always, except for the ones I have pinned. I have never manually updated just one package.

My use case is almost the same as you, but I don't see cons of adding support for upgrade a single formulae, what you want is still there, nothing change, brewu is equal to brew update && brew upgrade --all

BTW, the following code is exactly the first version of this PR.
alias brewu='brew update && brew upgrade --all'`

@janka102 proposed the support for upgrade a single formulae, and you seems agreed at first, then I changed the code to what it is now.

Merged my own.


Not able to generate consistent assets

Hi, thank you for putting this together. The results shown in the demo are amazing. But for some reason, I am not able to create clean assets. The generated multi views look good but the 3D assets don't look good.  I tried one of the demo prompts as well.
Prompt : a motorbike
Multiview :

3D video :
https://github.com/3DTopia/LGM/assets/20456046/471c54ac-af6f-4651-8515-15cfff679484
Also, the exported meshes do not have color or texture information.

@rajatprasun Hi, unfortunately MVDream can be unstable sometimes. You can try with different random seeds, and examine the mv images first.
The mesh is exported in GLB, which is supposed to have texture. You can load it with blender or other 3D viewers to check.

Hey, I tried with different seeds as well and increased the iteration to 500 as well. The multi view look great but the 3D assets in the generated video are smeared or have noise.
For the texture part, I Imported the .ply file in blender for the bird from image-to-3d example and it looks like this:

I do not the texture from the image. Is this expected?

@rajatprasun Surely the model still have some limitations for complex prompts...
This ply file is the 3D Gaussians instead of the final mesh. You need to run convert.py on this ply file to get the final textured mesh. Since it takes ~1 minute to do this conversion, it's not included in the gradio demo.


Enter Survey Protocol into Survey Tool

Overview
In order to get feedback on RS, (i.e. baseline) we will send CX survey to all RS users. This is first survey so will also get feedback and tweak survey.
Participants
All RS Users
Background
To do

[ ] Enter questions into electronic survey tool
[ ] Test survey
[ ] Add link to the email

split up ticket into

enter into survey monkey
test with team


Include spectral all models define in likelihood package in the pyLikelihood interface.

Following the instructions here:
https://github.com/fermi-lat/Fermitools-conda/wiki/Contributing-to-the-Fermitools#pylikelihood

@donhorner Do we have documentation anywhere that lists all valid spectral models that should be accessible in Likelihood?

https://fermi.gsfc.nasa.gov/ssc/data/analysis/scitools/source_models.html

The dev build fermitools=2.0.6 should have all models in Likelihood implemented in pyLikelihood with the exception of SmoothDoubleBrokenPowerLaw, which is throwing an error at compile time.  Currently debugging that issue and will post an update when finished.

Ok, all models available in Likelihood should (hopefully) be available now in pyLikelihood as of the most recent fermitools=2.0.6 dev build.  @donhorner would you mind pinging someone to verify this?  It can be installed in a python3 environment using the command:
conda install -c conda-forge -c fermi/label/dev fermitools=2.0.6

I tested 2.0.6 and the missing Likelihood model all seem to be in pyLikelihood now.  I was able to stick them in the input XML file, and pylike was able to run a fit. Mis-naming a parameter in the XML file causes the fit to fail with a parameter not found error, so it definitely seems to be calling the model definitions in the code.


Check Bucket Boundaries Fails Upload an Object

Environment info

NooBaa Version: master (current 5.17)
Platform: NSFS NC (running in local machine with MacOS)

Actual behavior

When executing an S3 operation on a bucket - for example uploading an object we get an error that the upload failed.
Note: the origin of the error as will be described below is in the check bucket boundaries - it is relevant for more operations (listing objects in a bucket, etc.).

Expected behavior

Not to have this error.

Steps to reproduce

Create an account using the cli:  sudo node src/cmd/manage_nsfs account add --name <account-name> --new_buckets_path /tmp/nsfs_root1 --access_key <access-key> --secret_key <secret-key> --uid <uid> --gid <gid>.
Note: Before creating the account need to give permission to the new_buckets_path: chmod 777 /tmp/nsfs_root1.
Start the NSFS server with: sudo node src/cmd/nsfs --debug 5
Use the account's details for the alias: alias s3-nc-user-1='AWS_ACCESS_KEY_ID=<access-key> AWS_SECRET_ACCESS_KEY=<secret-key> aws --no-verify-ssl --endpoint-url https://localhost:6443'.
Create the bucket: s3-nc-user-1 s3 mb s3://shira-1001-bucket-1.
Create and Upload an object: touch hello_world.txt and then s3-nc-user-1 s3 cp hello_world.txt s3://shira-1001-bucket-1, see the error:

upload failed: ./hello_world.txt to s3://shira-1001-bucket-1/hello_world.txt An error occurred (AccessDenied) when calling the PutObject operation: Access Denied

Note: after changing this line in the config: config.NSFS_CHECK_BUCKET_BOUNDARIES = false; // SDSD and restarting the server (ctrl + c and rerun  sudo node src/cmd/nsfs --debug 5) we do not have an error:
s3-nc-user-1 s3 ls s3://shira-1001-bucket-1/
2024-07-02 13:32:07          0 hello_world.txt
More information - Screenshots / Logs / Other output
Logs from the server:
Jul-2 13:13:50.988 [nsfs/17208]    [L1] core.sdk.namespace_fs:: check_bucket_boundaries: fs_context { uid: 1001, gid: 1001, new_buckets_path: '/tmp/nsfs_root1', warn_threshold_ms: 100, backend: '', report_fs_stats: [Function (anonymous)] } file_path /tmp/nsfs_root1/shira-1001-bucket-1 this.bucket_path /tmp/nsfs_root1/shira-1001-bucket-1
2024-07-02 13:13:50.988168 [PID-17208/TID-259] [L1] FS::FSWorker::Begin: RealPath _path=/tmp/nsfs_root1/shira-1001-bucket-1
2024-07-02 13:13:50.988192 [PID-17208/TID-8707] [L1] FS::FSWorker::Execute: RealPath _path=/tmp/nsfs_root1/shira-1001-bucket-1 _uid=1001 _gid=1001 _backend=
2024-07-02 13:13:50.988212 [PID-17208/TID-8707] [L1] FS::FSWorker::Execute: RealPath _path=/tmp/nsfs_root1/shira-1001-bucket-1 _uid=1001 _gid=1001 geteuid()=1001 getegid()=1001 getuid()=1001 getgid()=1001
2024-07-02 13:13:50.988263 [PID-17208/TID-8707] [L1] FS::FSWorker::Execute: RealPath _path=/tmp/nsfs_root1/shira-1001-bucket-1  took: 0.018041 ms
2024-07-02 13:13:50.988284 [PID-17208/TID-259] [L1] FS::RealPath::OnOK: _path=/tmp/nsfs_root1/shira-1001-bucket-1 _full_path=/private/tmp/nsfs_root1/shira-1001-bucket-1
Jul-2 13:13:50.988 [nsfs/17208]    [L0] core.sdk.namespace_fs:: check_bucket_boundaries: the path /tmp/nsfs_root1/shira-1001-bucket-1 is not in the bucket /tmp/nsfs_root1/shira-1001-bucket-1 boundaries
Jul-2 13:13:50.990 [nsfs/17208]  [WARN] core.sdk.namespace_fs:: NamespaceFS: upload_object buffer pool cleanup error Error: Entry /tmp/nsfs_root1/shira-1001-bucket-1/hello_world.txt is not in bucket boundaries
    at Object.new_error_code (/Users/shiradymnik/SourceCode/noobaa-core/src/util/error_utils.js:16:26)
    at NamespaceFS._check_path_in_bucket_boundaries (/Users/shiradymnik/SourceCode/noobaa-core/src/sdk/namespace_fs.js:2541:31)
    at async NamespaceFS.upload_object (/Users/shiradymnik/SourceCode/noobaa-core/src/sdk/namespace_fs.js:1126:13)
    at async NsfsObjectSDK._call_op_and_update_stats (/Users/shiradymnik/SourceCode/noobaa-core/src/sdk/object_sdk.js:543:27)
    at async Object.put_object [as handler] (/Users/shiradymnik/SourceCode/noobaa-core/src/endpoint/s3/ops/s3_put_object.js:39:19)
    at async handle_request (/Users/shiradymnik/SourceCode/noobaa-core/src/endpoint/s3/s3_rest.js:150:19)
    at async Object.s3_rest [as handler] (/Users/shiradymnik/SourceCode/noobaa-core/src/endpoint/s3/s3_rest.js:65:9) {
  code: 'EACCES'
}
Jul-2 13:13:50.991 [nsfs/17208] [ERROR] core.endpoint.s3.s3_rest:: S3 ERROR <?xml version="1.0" encoding="UTF-8"?><Error>AccessDenied<Message>Access Denied</Message><Resource>/shira-1001-bucket-1/hello_world.txt</Resource><RequestId>ly494dmt-6yxcl2-f9x</RequestId></Error> PUT /shira-1001-bucket-1/hello_world.txt {"host":"localhost:6443","accept-encoding":"identity","content-type":"text/plain","user-agent":"aws-cli/2.15.36 Python/3.11.9 Darwin/23.4.0 source/arm64 prompt/off command/s3.cp","content-md5":"1B2M2Y8AsgTpgAmY7PhCfg==","expect":"100-continue","x-amz-date":"20240702T101350Z","x-amz-content-sha256":"UNSIGNED-PAYLOAD","authorization":"AWS4-HMAC-SHA256 Credential=Dwertyuiopasdfg11001/20240702/us-east-1/s3/aws4_request, SignedHeaders=content-md5;content-type;host;x-amz-content-sha256;x-amz-date, Signature=60bd00111e1602ed42773d4b464c5e580886ce1e3f92af472368a88b85d7886b","content-length":"0"} Error: Entry /tmp/nsfs_root1/shira-1001-bucket-1/hello_world.txt is not in bucket boundaries
    at Object.new_error_code (/Users/shiradymnik/SourceCode/noobaa-core/src/util/error_utils.js:16:26)
    at NamespaceFS._check_path_in_bucket_boundaries (/Users/shiradymnik/SourceCode/noobaa-core/src/sdk/namespace_fs.js:2541:31)
    at async NamespaceFS.upload_object (/Users/shiradymnik/SourceCode/noobaa-core/src/sdk/namespace_fs.js:1126:13)
    at async NsfsObjectSDK._call_op_and_update_stats (/Users/shiradymnik/SourceCode/noobaa-core/src/sdk/object_sdk.js:543:27)
    at async Object.put_object [as handler] (/Users/shiradymnik/SourceCode/noobaa-core/src/endpoint/s3/ops/s3_put_object.js:39:19)
    at async handle_request (/Users/shiradymnik/SourceCode/noobaa-core/src/endpoint/s3/s3_rest.js:150:19)
    at async Object.s3_rest [as handler] (/Users/shiradymnik/SourceCode/noobaa-core/src/endpoint/s3/s3_rest.js:65:9)

@shirady This only happens because you use /tmp/ and not /private/tmp/ as the bucket path on your Mac.
/tmp/ on Mac is a symlink to /private/tmp/ and when checking the boundaries we check the real path of the object /private/tmp/shira-1001-bucket-1/hello_world.txt is in the boundaries of the bucket path which is /tmp/shira-1001-bucket-1. If we do want to support bucket path as symlink it's a very small fix, @guymguym do you see a reason for not allowing bucket path to be a symlink?

@romayalon @shirady Same reason as we protect it for things inside a bucket - to avoid exposing sensitive data from the system. For example what if someone managed to set the bucket path to ln -s /etc /fs/bucketpath and then tried to download passwd, or worse - upload it... This config option is meant to prevent that by default. If you want to allow it for your dev env, override the config.

@guymguym, I don't understand what is the exact difference if this link is a symlink or an absolute path in which we protect it?
Currently, as I understand it what blocks a new_buckets_path is the check of in the CLI is_dir_rw_accessible and this dir will not be accessible to a user that is not uid and gid 0 (root) - which means that your concern of exposing sensitive data can happen if someone passes to the CLI, for example: sudo node src/cmd/manage_nsfs account add --name shira-path --new_buckets_path /etc/noobaa.conf.d --uid 0 --gid 0 (I took our config path as an example of a directory in /etc)
output (omitting details of access_key, secret_key and master_key_id):
{
  "response": {
    "code": "AccountCreated",
    "reply": {
      "_id": "6683f6f16a973327fcf08dfc",
      "name": "shira-path",
      "email": "shira-path",
      "creation_date": "2024-07-02T12:47:45.608Z",
      "access_keys": [
        {
          "access_key": "",
          "secret_key": ""
        }
      ],
      "nsfs_account_config": {
        "uid": 0,
        "gid": 0,
        "new_buckets_path": "/etc/noobaa.conf.d"
      },
      "allow_bucket_creation": true,
      "master_key_id": ""
    }
  }
}

I changed the title of the issue to match what I wrote in the commented above, and so we will define it and solve it.

@naveenpaul1 suggested on #8225 to add also a check for absolute paths when restricting path and new_buckets_path values.


Update free-programming-books-langs.md

[An Introduction to Statistical Learning with Applications in Python] link was changed. Existing link is dead.
What does this PR do?
Add resource(s) | Remove resource(s) | Add info | Improve repo
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

added in #10988


Balance 0 in explorer

in explorer it shows balance 0 but in wallet not 0. txhash doesn't show wallet addrees and its hard to understand.

Hello, you probably have a HDWallet, which changes the addresses. Are you sure you are requesting the correct address?

I use Kaspa Web Wallet

I use Kaspa Web Wallet

Please go to debug -> show UTXOs .. there you have the correct Tx-Id and your wallet address


Do you get a crash dialog?
Did it create a crash dump for you?
Does "termination" mean closing toolbox, or closing GW?

@BearsMan new launcher, not like that matters since it happens after the launcher is long out of the question.

Crash dialog? No, it just freezes the game until windows says it's not responding anymore.
No crashdump.
Upon closing the TB main window.

You able to take a screenshot of your UI before you close (and crash) the game?

https://youtu.be/Xa1-h4MHR-8

Some more information: fresh installations of TB, Windows v2004, also happening in a freshly installed VM. Not happening in the last TB release.

Sick tunes bro, what do you mean by "last TB release" ? I did make changes recently to stop this freezing/crashing from happening, but you've said this is using version 3.8.1 which is the latest?

All I get is a "ding" when closing GW with TB active. Have to double-check if it happens with 3.8.1

My last TB version was 3.7 I believe, but it might have been 3.8, it definitely wasn't happening with it however.

Debugging showed that Resources::Terminate hangs at worker.join();.
Not entirely sure why, but rebuilding the solution and replacing gwtoolboxdll.dll with the recompiled one got rid of the issue. When I use the 3.8.1 release tagged one however, it still happens.

Make sure you're recompiling the tagged 3.8.1 and not the latest commit on master to test

Same still holds true.

fixed https://github.com/HasKha/GWToolboxpp/commits/adb4522c082f15ad40627f996523916818736cf3


Changes made:

Used consistent indentation of 2 spaces throughout the code. Sorted import statements alphabetically and grouped them by type. Moved the definition of validateConfiguration() to a more appropriate location. Wrapped the body of the start() function in a try-catch block to handle any errors that might occur during initialization. Renamed the ex variable to error for consistency with the rest of the code. Changed the error message for unhandled promise rejections to be more descriptive. Moved the call to start() outside of the IIFE to make the code more readable.

Changes related to styling are not required at the moment.
Consistent styling will be part of future release