Other cuda versions

Hello :)
are you ever planning to publish version working with more recent coda versions? I would love to continue using you project, but it's a bit hard with newer pytorch versions.
Would be awesome! :)

I can look into it. Could you specify exactly which pytorch and CUDA version are you trying and what are the errors? Thanks.

Oh great!! :) Currently I'm trying to use 11.7 which is quite a bit newer. The traceback I get is the following:
`python -m pip install git+https://github.com/pawelswoboda/RAMA.git
Looking in indexes: https://pypi.org/simple, https://pypi.ngc.nvidia.com
Collecting git+https://github.com/pawelswoboda/RAMA.git
Cloning https://github.com/pawelswoboda/RAMA.git to /tmp/pip-req-build-wlbdfo5d
Running command git clone -q https://github.com/pawelswoboda/RAMA.git /tmp/pip-req-build-wlbdfo5d
Resolved https://github.com/pawelswoboda/RAMA.git to commit aee9ca4fd349e231d72d9bce25fa9b310d1d93dc
Running command git submodule update --init --recursive -q
Building wheels for collected packages: RAMA
Building wheel for RAMA (setup.py) ... |^[[C^[[^[[error
ERROR: Command errored out with exit status 1:
command: /opt/conda/bin/python -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-wlbdfo5d/setup.py'"'"'; file='"'"'/tmp/pip-req-build-wlbdfo5d/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-id03c28y
cwd: /tmp/pip-req-build-wlbdfo5d/
Complete output (164 lines):
running bdist_wheel
running build
running build_ext
build_with_torch:OFF
Testing gcc...
...has version 9.4.0
Found suitable gcc/g++ version gcc g++
-- The CXX compiler identification is GNU 9.4.0
-- The CUDA compiler identification is NVIDIA 11.7.99
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting CUDA compiler ABI info
-- Detecting CUDA compiler ABI info - done
-- Check for working CUDA compiler: /usr/local/cuda/bin/nvcc - skipped
-- Detecting CUDA compile features
-- Detecting CUDA compile features - done
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
Compiling without PyTorch support
-- pybind11 v2.7.1 dev1
CMake Warning (dev) at /opt/conda/share/cmake-3.23/Modules/CMakeDependentOption.cmake:89 (message):
Policy CMP0127 is not set: cmake_dependent_option() supports full Condition
Syntax.  Run "cmake --help-policy CMP0127" for policy details.  Use the
cmake_policy command to set the policy and suppress this warning.
Call Stack (most recent call first):
external/pybind11/CMakeLists.txt:98 (cmake_dependent_option)
This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning at external/pybind11/tools/pybind11Common.cmake:178 (message):
USE -DCMAKE_CXX_STANDARD=17 instead of PYBIND11_CPP_STANDARD
Call Stack (most recent call first):
external/pybind11/CMakeLists.txt:191 (include)
-- Found PythonInterp: /opt/conda/bin/python (found version "3.8.13")
-- Found PythonLibs: /opt/conda/lib/libpython3.8.so
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/pip-req-build-wlbdfo5d/build/temp.linux-x86_64-3.8
[ 16%] Building CUDA object src/CMakeFiles/multicut_message_passing.dir/multicut_message_passing.cu.o
[ 16%] Building CUDA object CMakeFiles/gpuMST_boruvka.dir/external/cudaMST/gpuMST/gpuMST.cu.o
[ 16%] Building CUDA object CMakeFiles/ECL-CC_11.dir/external/ECL-CC/ECL-CC_11.cu.o
[ 16%] Building CXX object src/CMakeFiles/multicut_text_parser.dir/multicut_text_parser.cpp.o
[ 20%] Linking CXX static library libmulticut_text_parser.a
[ 20%] Built target multicut_text_parser
/tmp/pip-req-build-wlbdfo5d/external/cudaMST/gpuMST/gpuMST.cu(138): warning #1444-D: function "__any"
/usr/local/cuda/bin/../targets/x86_64-linux/include/device_atomic_functions.h(178): here was declared deprecated ("__any() is deprecated in favor of __any_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")
[ 25%] Linking CUDA static library libECL-CC_11.a
[ 25%] Built target ECL-CC_11
[ 29%] Building CUDA object src/CMakeFiles/dCOO.dir/dCOO.cu.o
ptxas /tmp/tmpxft_00004130_00000000-6_gpuMST.ptx, line 65721; warning : Instruction 'vote' without '.sync' is deprecated since PTX ISA version 6.0 and will be discontinued in a future PTX ISA version
[ 33%] Linking CUDA static library libgpuMST_boruvka.a
[ 33%] Built target gpuMST_boruvka
[ 37%] Linking CUDA static library libdCOO.a
[ 37%] Built target dCOO
[ 50%] Building CUDA object src/CMakeFiles/edge_contractions_woc_thrust.dir/edge_contractions_woc_thrust.cu.o
[ 50%] Building CUDA object src/CMakeFiles/maximum_matching_vertex_based.dir/maximum_matching_vertex_based.cu.o
[ 50%] Building CUDA object src/CMakeFiles/conflicted_cycles_cuda.dir/conflicted_cycles_cuda.cu.o
[ 54%] Linking CUDA static library libmulticut_message_passing.a
[ 54%] Built target multicut_message_passing
[ 58%] Linking CUDA static library libconflicted_cycles_cuda.a
[ 58%] Built target conflicted_cycles_cuda
[ 62%] Building CUDA object src/CMakeFiles/dual_solver.dir/dual_solver.cu.o
[ 66%] Linking CUDA static library libmaximum_matching_vertex_based.a
[ 66%] Built target maximum_matching_vertex_based
[ 70%] Linking CUDA static library libdual_solver.a
[ 70%] Built target dual_solver
[ 75%] Linking CUDA static library libedge_contractions_woc_thrust.a
[ 75%] Built target edge_contractions_woc_thrust
[ 79%] Building CUDA object src/CMakeFiles/edge_contractions_woc.dir/edge_contractions_woc.cu.o
[ 83%] Linking CUDA static library libedge_contractions_woc.a
[ 83%] Built target edge_contractions_woc
[ 87%] Building CUDA object src/CMakeFiles/rama_cuda.dir/rama_cuda.cu.o
/tmp/pip-req-build-wlbdfo5d/external/CLI11/include/CLI/TypeTools.hpp(149): warning #20236-D: pragma "diag_suppress" is deprecated, use "nv_diag_suppress" instead
/tmp/pip-req-build-wlbdfo5d/external/CLI11/include/CLI/TypeTools.hpp(153): warning #20236-D: pragma "diag_default" is deprecated, use "nv_diag_default" instead
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<float,  ::thrust::device_allocator > ::device_vector(const thrust::device_vector<float,  ::thrust::device_allocator > &)") from a host device function("dCOO::dCOO") is not allowed
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<int,  ::thrust::device_allocator > ::device_vector(const thrust::device_vector<int,  ::thrust::device_allocator > &)") from a host device function("dCOO::dCOO") is not allowed
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<int,  ::thrust::device_allocator > ::device_vector(const thrust::device_vector<int,  ::thrust::device_allocator > &)") from a host device function("dCOO::dCOO") is not allowed
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<int,  ::thrust::device_allocator > ::~device_vector()") from a host device function("dCOO::~dCOO") is not allowed
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<int,  ::thrust::device_allocator > ::~device_vector()") from a host device function("dCOO::~dCOO") is not allowed
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<float,  ::thrust::device_allocator > ::~device_vector()") from a host device function("dCOO::~dCOO") is not allowed
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<float,  ::thrust::device_allocator > ::operator =(const thrust::device_vector<float,  ::thrust::device_allocator > &)") from a host device function("dCOO::operator =") is not allowed
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<int,  ::thrust::device_allocator > ::operator =(const thrust::device_vector<int,  ::thrust::device_allocator > &)") from a host device function("dCOO::operator =") is not allowed
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a host function("thrust::device_vector<int,  ::thrust::device_allocator > ::operator =(const thrust::device_vector<int,  ::thrust::device_allocator > &)") from a host device function("dCOO::operator =") is not allowed
/tmp/pip-req-build-wlbdfo5d/external/CLI11/include/CLI/TypeTools.hpp(149): warning #20236-D: pragma "diag_suppress" is deprecated, use "nv_diag_suppress" instead
/tmp/pip-req-build-wlbdfo5d/external/CLI11/include/CLI/TypeTools.hpp(153): warning #20236-D: pragma "diag_default" is deprecated, use "nv_diag_default" instead
[ 91%] Linking CUDA static library librama_cuda.a
[ 91%] Built target rama_cuda
[ 95%] Building CXX object src/CMakeFiles/rama_py.dir/rama_py.cpp.o
In file included from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/type_traits/is_trivially_relocatable.h:193,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/system/detail/sequential/copy.inl:24,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/system/detail/sequential/copy.h:61,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/system/detail/adl/copy.h:25,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/detail/copy.inl:22,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/detail/copy.h:90,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/detail/allocator/copy_construct_range.inl:21,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/detail/allocator/copy_construct_range.h:45,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/detail/contiguous_storage.inl:23,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/detail/contiguous_storage.h:234,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/detail/vector_base.h:30,
from /tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/device_vector.h:26,
from /tmp/pip-req-build-wlbdfo5d/include/dCOO.h:4,
from /tmp/pip-req-build-wlbdfo5d/include/rama_cuda.h:5,
from /tmp/pip-req-build-wlbdfo5d/src/rama_py.cpp:5:
/tmp/pip-req-build-wlbdfo5d/external/thrust/thrust/system/cuda/detail/guarded_cuda_runtime_api.h:38:10: fatal error: cuda_runtime_api.h: No such file or directory
38 | #include <cuda_runtime_api.h>
|          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [src/CMakeFiles/rama_py.dir/build.make:76: src/CMakeFiles/rama_py.dir/rama_py.cpp.o] Error 1
make[2]: *** [CMakeFiles/Makefile2:550: src/CMakeFiles/rama_py.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:557: src/CMakeFiles/rama_py.dir/rule] Error 2
make: *** [Makefile:338: rama_py] Error 2
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-req-build-wlbdfo5d/setup.py", line 120, in
setup(
File "/opt/conda/lib/python3.8/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/opt/conda/lib/python3.8/distutils/core.py", line 148, in setup
dist.run_commands()
File "/opt/conda/lib/python3.8/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/opt/conda/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 299, in run
self.run_command('build')
File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/opt/conda/lib/python3.8/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-req-build-wlbdfo5d/setup.py", line 33, in run
self.build_extension(ext)
File "/tmp/pip-req-build-wlbdfo5d/setup.py", line 118, in build_extension
subprocess.check_call(['cmake', '--build', '.', '--target', ext.name] + build_args, cwd=self.build_temp)
File "/opt/conda/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'rama_py', '--config', 'Release', '--', '-j8']' returned non-zero exit status 2.
ERROR: Failed building wheel for RAMA
Running setup.py clean for RAMA
Failed to build RAMA
Installing collected packages: RAMA
Running setup.py install for RAMA ... \0
manpath: can't open the manpath configuration file /etc/manpath.config
manpath: can't open the manpath configuration file /etc/manpath.config`

It seems to work fine on my end. Perhaps cmake is not able to find the CUDA toolkit?
Could you try this procedure and send the log?

Sorry for the late reply!! during make -j 4 I get the following error
make -j 4
[  2%] Building CUDA object CMakeFiles/gpuMST_kruskal.dir/external/cudaMST/gpuMSTdpk/gpuMST.cu.o
[  6%] Building CXX object src/CMakeFiles/multicut_text_parser.dir/multicut_text_parser.cpp.o
[  6%] Building CUDA object CMakeFiles/ECL-CC_11.dir/external/ECL-CC/ECL-CC_11.cu.o
[  9%] Building CUDA object CMakeFiles/gpuMST_boruvka.dir/external/cudaMST/gpuMST/gpuMST.cu.o

[ 11%] Linking CXX static library libmulticut_text_parser.a
[ 11%] Built target multicut_text_parser
[ 13%] Building CUDA object src/CMakeFiles/multicut_message_passing.dir/multicut_message_passing.cu.o
/workspace/RAMA/external/cudaMST/gpuMST/gpuMST.cu(138): warning #1444-D: function "__any"
/usr/local/cuda/bin/../targets/x86_64-linux/include/device_atomic_functions.h(178): here was declared deprecated ("__any() is deprecated in favor of __any_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")

/workspace/RAMA/external/cudaMST/gpuMSTdpk/gpuMST.cu(165): warning #1444-D: function "__any"
/usr/local/cuda/bin/../targets/x86_64-linux/include/device_atomic_functions.h(178): here was declared deprecated ("__any() is deprecated in favor of __any_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")

[ 15%] Linking CUDA static library libECL-CC_11.a
[ 15%] Built target ECL-CC_11
[ 18%] Building CUDA object test/CMakeFiles/compute_offsets_test.dir/compute_offsets_test.cu.o
ptxas /tmp/tmpxft_000005d8_00000000-6_gpuMST.ptx, line 65721; warning : Instruction 'vote' without '.sync' is deprecated since PTX ISA version 6.0 and will be discontinued in a future PTX ISA version
ptxas /tmp/tmpxft_000005d5_00000000-6_gpuMST.ptx, line 96323; warning : Instruction 'vote' without '.sync' is deprecated since PTX ISA version 6.0 and will be discontinued in a future PTX ISA version
[ 20%] Linking CUDA static library libgpuMST_boruvka.a
[ 20%] Built target gpuMST_boruvka
[ 22%] Building CUDA object test/CMakeFiles/compute_unique_test.dir/compute_unique_test.cu.o
[ 25%] Linking CUDA static library libgpuMST_kruskal.a
[ 25%] Built target gpuMST_kruskal
[ 27%] Building CUDA object src/CMakeFiles/dCOO.dir/dCOO.cu.o
[ 29%] Linking CUDA executable compute_offsets_test
[ 29%] Built target compute_offsets_test
[ 31%] Building CUDA object test/CMakeFiles/cc_gpu_test.dir/cc_gpu_test.cu.o
[ 34%] Linking CUDA static library libmulticut_message_passing.a
[ 36%] Linking CUDA executable compute_unique_test
[ 36%] Built target multicut_message_passing
[ 36%] Built target compute_unique_test
[ 38%] Linking CUDA executable cc_gpu_test
[ 38%] Built target cc_gpu_test
[ 40%] Linking CUDA static library libdCOO.a
[ 40%] Built target dCOO
[ 43%] Building CUDA object test/CMakeFiles/multicut_message_passing_test.dir/multicut_message_passing_test.cu.o
[ 45%] Building CUDA object src/CMakeFiles/edge_contractions_woc_thrust.dir/edge_contractions_woc_thrust.cu.o
[ 47%] Building CUDA object src/CMakeFiles/conflicted_cycles_cuda.dir/conflicted_cycles_cuda.cu.o
[ 50%] Building CUDA object src/CMakeFiles/maximum_matching_vertex_based.dir/maximum_matching_vertex_based.cu.o
[ 52%] Linking CUDA executable multicut_message_passing_test
[ 52%] Built target multicut_message_passing_test
[ 54%] Linking CUDA static library libmaximum_matching_vertex_based.a
[ 54%] Built target maximum_matching_vertex_based
[ 56%] Building CUDA object test/CMakeFiles/maximum_matching_vertex_based_test.dir/maximum_matching_vertex_based_test.cu.o
[ 59%] Linking CUDA static library libconflicted_cycles_cuda.a
[ 59%] Built target conflicted_cycles_cuda
[ 61%] Building CUDA object test/CMakeFiles/conflicted_cycles_test.dir/conflicted_cycles_test.cu.o
[ 63%] Building CUDA object src/CMakeFiles/dual_solver.dir/dual_solver.cu.o
[ 65%] Linking CUDA static library libedge_contractions_woc_thrust.a
[ 65%] Built target edge_contractions_woc_thrust
[ 68%] Building CUDA object src/CMakeFiles/edge_contractions_woc.dir/edge_contractions_woc.cu.o
[ 70%] Linking CUDA executable maximum_matching_vertex_based_test
[ 70%] Built target maximum_matching_vertex_based_test
[ 72%] Linking CUDA static library libdual_solver.a
[ 72%] Built target dual_solver
[ 75%] Linking CUDA executable conflicted_cycles_test
[ 75%] Built target conflicted_cycles_test
[ 77%] Linking CUDA static library libedge_contractions_woc.a
[ 77%] Built target edge_contractions_woc
[ 79%] Building CUDA object src/CMakeFiles/rama_cuda.dir/rama_cuda.cu.o
[ 81%] Building CUDA object test/CMakeFiles/edge_contractions_woc_test.dir/edge_contractions_woc_test.cu.o
/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(149): warning #20236-D: pragma "diag_suppress" is deprecated, use "nv_diag_suppress" instead

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(153): warning #20236-D: pragma "diag_default" is deprecated, use "nv_diag_default" instead

[ 84%] Linking CUDA executable edge_contractions_woc_test
[ 84%] Built target edge_contractions_woc_test
/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<float,  ::thrust::device_allocator<float> > ::device_vector(const thrust::device_vector<float,  ::thrust::device_allocator<float> > &)") from a __host__ __device__ function("dCOO::dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::device_vector(const thrust::device_vector<int,  ::thrust::device_allocator<int> > &)") from a __host__ __device__ function("dCOO::dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::device_vector(const thrust::device_vector<int,  ::thrust::device_allocator<int> > &)") from a __host__ __device__ function("dCOO::dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::~device_vector()") from a __host__ __device__ function("dCOO::~dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::~device_vector()") from a __host__ __device__ function("dCOO::~dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<float,  ::thrust::device_allocator<float> > ::~device_vector()") from a __host__ __device__ function("dCOO::~dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<float,  ::thrust::device_allocator<float> > ::operator =(const thrust::device_vector<float,  ::thrust::device_allocator<float> > &)") from a __host__ __device__ function("dCOO::operator =") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::operator =(const thrust::device_vector<int,  ::thrust::device_allocator<int> > &)") from a __host__ __device__ function("dCOO::operator =") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::operator =(const thrust::device_vector<int,  ::thrust::device_allocator<int> > &)") from a __host__ __device__ function("dCOO::operator =") is not allowed

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(149): warning #20236-D: pragma "diag_suppress" is deprecated, use "nv_diag_suppress" instead

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(153): warning #20236-D: pragma "diag_default" is deprecated, use "nv_diag_default" instead

[ 86%] Linking CUDA static library librama_cuda.a
[ 86%] Built target rama_cuda
[ 90%] Building CXX object src/CMakeFiles/rama_py.dir/rama_py.cpp.o
[ 90%] Building CUDA object src/CMakeFiles/rama_text_input.dir/rama_text_input.cu.o
[ 93%] Building CXX object test/CMakeFiles/rama_cuda_test.dir/rama_cuda_test.cpp.o
In file included from /workspace/RAMA/external/thrust/thrust/type_traits/is_trivially_relocatable.h:193,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/sequential/copy.inl:24,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/sequential/copy.h:61,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/adl/copy.h:25,
                 from /workspace/RAMA/external/thrust/thrust/detail/copy.inl:22,
                 from /workspace/RAMA/external/thrust/thrust/detail/copy.h:90,
                 from /workspace/RAMA/external/thrust/thrust/detail/allocator/copy_construct_range.inl:21,
                 from /workspace/RAMA/external/thrust/thrust/detail/allocator/copy_construct_range.h:45,
                 from /workspace/RAMA/external/thrust/thrust/detail/contiguous_storage.inl:23,
                 from /workspace/RAMA/external/thrust/thrust/detail/contiguous_storage.h:234,
                 from /workspace/RAMA/external/thrust/thrust/detail/vector_base.h:30,
                 from /workspace/RAMA/external/thrust/thrust/device_vector.h:26,
                 from /workspace/RAMA/include/dCOO.h:4,
                 from /workspace/RAMA/include/rama_cuda.h:5,
                 from /workspace/RAMA/test/rama_cuda_test.cpp:1:
/workspace/RAMA/external/thrust/thrust/system/cuda/detail/guarded_cuda_runtime_api.h:38:10: fatal error: cuda_runtime_api.h: No such file or directory
   38 | #include <cuda_runtime_api.h>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [test/CMakeFiles/rama_cuda_test.dir/build.make:76: test/CMakeFiles/rama_cuda_test.dir/rama_cuda_test.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:639: test/CMakeFiles/rama_cuda_test.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
In file included from /workspace/RAMA/external/thrust/thrust/type_traits/is_trivially_relocatable.h:193,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/sequential/copy.inl:24,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/sequential/copy.h:61,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/adl/copy.h:25,
                 from /workspace/RAMA/external/thrust/thrust/detail/copy.inl:22,
                 from /workspace/RAMA/external/thrust/thrust/detail/copy.h:90,
                 from /workspace/RAMA/external/thrust/thrust/detail/allocator/copy_construct_range.inl:21,
                 from /workspace/RAMA/external/thrust/thrust/detail/allocator/copy_construct_range.h:45,
                 from /workspace/RAMA/external/thrust/thrust/detail/contiguous_storage.inl:23,
                 from /workspace/RAMA/external/thrust/thrust/detail/contiguous_storage.h:234,
                 from /workspace/RAMA/external/thrust/thrust/detail/vector_base.h:30,
                 from /workspace/RAMA/external/thrust/thrust/device_vector.h:26,
                 from /workspace/RAMA/include/dCOO.h:4,
                 from /workspace/RAMA/include/rama_cuda.h:5,
                 from /workspace/RAMA/src/rama_py.cpp:5:
/workspace/RAMA/external/thrust/thrust/system/cuda/detail/guarded_cuda_runtime_api.h:38:10: fatal error: cuda_runtime_api.h: No such file or directory
   38 | #include <cuda_runtime_api.h>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[2]: *** [src/CMakeFiles/rama_py.dir/build.make:76: src/CMakeFiles/rama_py.dir/rama_py.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:550: src/CMakeFiles/rama_py.dir/all] Error 2
/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(149): warning #20236-D: pragma "diag_suppress" is deprecated, use "nv_diag_suppress" instead

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(153): warning #20236-D: pragma "diag_default" is deprecated, use "nv_diag_default" instead

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(149): warning #20236-D: pragma "diag_suppress" is deprecated, use "nv_diag_suppress" instead

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(153): warning #20236-D: pragma "diag_default" is deprecated, use "nv_diag_default" instead

[ 95%] Linking CXX executable rama_text_input
[ 95%] Built target rama_text_input
make: *** [Makefile:136: all] Error 2

/While running cmake it should print which CUDA version is being used in first few lines. Could you check that?

Perhaps some CUDA related paths are not set correctly. It is running fine on my end with this setup:
export CUDA_HOME=/usr/lib/cuda-11.7/
export CUDA_PATH=${CUDA_HOME}
export CUDAToolkit_ROOT=${CUDA_HOME}
export PATH=${CUDA_HOME}/bin${PATH:+:${PATH}}
export CPATH=${CUDA_HOME}/include${CPATH:+:${CPATH}}
export LD_LIBRARY_PATH=${CUDA_HOME}/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}

This is what I get:
cmake ..
-- The CXX compiler identification is GNU 9.4.0
-- The CUDA compiler identification is NVIDIA 11.7.99
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting CUDA compiler ABI info
-- Detecting CUDA compiler ABI info - done
-- Check for working CUDA compiler: /usr/local/cuda/bin/nvcc - skipped
-- Detecting CUDA compile features
-- Detecting CUDA compile features - done

I have made a small change in the master branch, please check with the latest code.

Thank you!! :) managed to install the C++ version but had to add all the additional git packages to a safe path on the cluster
git config --global --add safe.directory /workspace/code/RAMA/external/thrust/dependencies/cub

I was not able to install python version yet and I suspect it's also because of this. Since the clone of the reps and pulling of the submodules is happening within the pip command I can't add them to the safe path. Can you maybe tell me which commands are run one after another by the python -m pip install git+https://github.com/pawelswoboda/RAMA.git command? Maybe I can just run them one after another and then it works.
Unfortunately I can't add the paths to the safe path from the beginning since it is stored to some temporary directory using pip install which I can't set in advance.

Great. The sequence of commands you wrote should install the python bindings.

Oh man I'm sorry it did not work out but we are close I think:
:/workspace/RAMA# python setup.py install
running install
/opt/conda/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/opt/conda/lib/python3.8/site-packages/setuptools/command/easy_install.py:156: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
running bdist_egg
running egg_info
creating RAMA.egg-info
writing RAMA.egg-info/PKG-INFO
writing dependency_links to RAMA.egg-info/dependency_links.txt
writing top-level names to RAMA.egg-info/top_level.txt
writing manifest file 'RAMA.egg-info/SOURCES.txt'
reading manifest file 'RAMA.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'RAMA.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_ext
build_with_torch:OFF

Testing gcc...
...has version 9.4.0
Found suitable gcc/g++ version gcc g++
-- The CXX compiler identification is GNU 9.4.0
-- The CUDA compiler identification is NVIDIA 11.7.99
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting CUDA compiler ABI info
-- Detecting CUDA compiler ABI info - done
-- Check for working CUDA compiler: /usr/local/cuda/bin/nvcc - skipped
-- Detecting CUDA compile features
-- Detecting CUDA compile features - done
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
Compiling without PyTorch support
-- pybind11 v2.7.1 dev1
CMake Warning (dev) at /opt/conda/share/cmake-3.23/Modules/CMakeDependentOption.cmake:89 (message):
  Policy CMP0127 is not set: cmake_dependent_option() supports full Condition
  Syntax.  Run "cmake --help-policy CMP0127" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.
Call Stack (most recent call first):
  external/pybind11/CMakeLists.txt:98 (cmake_dependent_option)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning at external/pybind11/tools/pybind11Common.cmake:178 (message):
  USE -DCMAKE_CXX_STANDARD=17 instead of PYBIND11_CPP_STANDARD
Call Stack (most recent call first):
  external/pybind11/CMakeLists.txt:191 (include)

-- Found PythonInterp: /opt/conda/bin/python (found version "3.8.13")
-- Found PythonLibs: /opt/conda/lib/libpython3.8.so
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- Configuring done
-- Generating done
-- Build files have been written to: /workspace/RAMA/build/temp.linux-x86_64-3.8
[  4%] Building CUDA object CMakeFiles/ECL-CC_11.dir/external/ECL-CC/ECL-CC_11.cu.o
[  8%] Building CUDA object src/CMakeFiles/multicut_message_passing.dir/multicut_message_passing.cu.o
[ 12%] Building CUDA object CMakeFiles/gpuMST_boruvka.dir/external/cudaMST/gpuMST/gpuMST.cu.o
[ 16%] Building CXX object src/CMakeFiles/multicut_text_parser.dir/multicut_text_parser.cpp.o
[ 20%] Linking CXX static library libmulticut_text_parser.a
[ 20%] Built target multicut_text_parser
/workspace/RAMA/external/cudaMST/gpuMST/gpuMST.cu(138): warning #1444-D: function "__any"
/usr/local/cuda/bin/../targets/x86_64-linux/include/device_atomic_functions.h(178): here was declared deprecated ("__any() is deprecated in favor of __any_sync() and may be removed in a future release (Use -Wno-deprecated-declarations to suppress this warning).")

[ 25%] Linking CUDA static library libECL-CC_11.a
[ 25%] Built target ECL-CC_11
[ 29%] Building CUDA object src/CMakeFiles/dCOO.dir/dCOO.cu.o
ptxas /tmp/tmpxft_000016f3_00000000-6_gpuMST.ptx, line 65721; warning : Instruction 'vote' without '.sync' is deprecated since PTX ISA version 6.0 and will be discontinued in a future PTX ISA version
[ 33%] Linking CUDA static library libgpuMST_boruvka.a
[ 33%] Built target gpuMST_boruvka
[ 37%] Linking CUDA static library libdCOO.a
[ 37%] Built target dCOO
[ 41%] Building CUDA object src/CMakeFiles/edge_contractions_woc_thrust.dir/edge_contractions_woc_thrust.cu.o
[ 45%] Building CUDA object src/CMakeFiles/maximum_matching_vertex_based.dir/maximum_matching_vertex_based.cu.o
[ 50%] Building CUDA object src/CMakeFiles/conflicted_cycles_cuda.dir/conflicted_cycles_cuda.cu.o
[ 54%] Linking CUDA static library libmulticut_message_passing.a
[ 54%] Built target multicut_message_passing
[ 58%] Linking CUDA static library libmaximum_matching_vertex_based.a
[ 58%] Built target maximum_matching_vertex_based
[ 62%] Linking CUDA static library libconflicted_cycles_cuda.a
[ 62%] Built target conflicted_cycles_cuda
[ 66%] Building CUDA object src/CMakeFiles/dual_solver.dir/dual_solver.cu.o
[ 70%] Linking CUDA static library libdual_solver.a
[ 70%] Built target dual_solver
[ 75%] Linking CUDA static library libedge_contractions_woc_thrust.a
[ 75%] Built target edge_contractions_woc_thrust
[ 79%] Building CUDA object src/CMakeFiles/edge_contractions_woc.dir/edge_contractions_woc.cu.o
[ 83%] Linking CUDA static library libedge_contractions_woc.a
[ 83%] Built target edge_contractions_woc
[ 87%] Building CUDA object src/CMakeFiles/rama_cuda.dir/rama_cuda.cu.o
/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(149): warning #20236-D: pragma "diag_suppress" is deprecated, use "nv_diag_suppress" instead

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(153): warning #20236-D: pragma "diag_default" is deprecated, use "nv_diag_default" instead

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<float,  ::thrust::device_allocator<float> > ::device_vector(const thrust::device_vector<float,  ::thrust::device_allocator<float> > &)") from a __host__ __device__ function("dCOO::dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::device_vector(const thrust::device_vector<int,  ::thrust::device_allocator<int> > &)") from a __host__ __device__ function("dCOO::dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::device_vector(const thrust::device_vector<int,  ::thrust::device_allocator<int> > &)") from a __host__ __device__ function("dCOO::dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::~device_vector()") from a __host__ __device__ function("dCOO::~dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::~device_vector()") from a __host__ __device__ function("dCOO::~dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<float,  ::thrust::device_allocator<float> > ::~device_vector()") from a __host__ __device__ function("dCOO::~dCOO") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<float,  ::thrust::device_allocator<float> > ::operator =(const thrust::device_vector<float,  ::thrust::device_allocator<float> > &)") from a __host__ __device__ function("dCOO::operator =") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::operator =(const thrust::device_vector<int,  ::thrust::device_allocator<int> > &)") from a __host__ __device__ function("dCOO::operator =") is not allowed

/usr/local/cuda/bin/../targets/x86_64-linux/include/vector_types.h(423): warning #20011-D: calling a __host__ function("thrust::device_vector<int,  ::thrust::device_allocator<int> > ::operator =(const thrust::device_vector<int,  ::thrust::device_allocator<int> > &)") from a __host__ __device__ function("dCOO::operator =") is not allowed

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(149): warning #20236-D: pragma "diag_suppress" is deprecated, use "nv_diag_suppress" instead

/workspace/RAMA/external/CLI11/include/CLI/TypeTools.hpp(153): warning #20236-D: pragma "diag_default" is deprecated, use "nv_diag_default" instead

[ 91%] Linking CUDA static library librama_cuda.a
[ 91%] Built target rama_cuda
[ 95%] Building CXX object src/CMakeFiles/rama_py.dir/rama_py.cpp.o
In file included from /workspace/RAMA/external/thrust/thrust/type_traits/is_trivially_relocatable.h:193,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/sequential/copy.inl:24,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/sequential/copy.h:61,
                 from /workspace/RAMA/external/thrust/thrust/system/detail/adl/copy.h:25,
                 from /workspace/RAMA/external/thrust/thrust/detail/copy.inl:22,
                 from /workspace/RAMA/external/thrust/thrust/detail/copy.h:90,
                 from /workspace/RAMA/external/thrust/thrust/detail/allocator/copy_construct_range.inl:21,
                 from /workspace/RAMA/external/thrust/thrust/detail/allocator/copy_construct_range.h:45,
                 from /workspace/RAMA/external/thrust/thrust/detail/contiguous_storage.inl:23,
                 from /workspace/RAMA/external/thrust/thrust/detail/contiguous_storage.h:234,
                 from /workspace/RAMA/external/thrust/thrust/detail/vector_base.h:30,
                 from /workspace/RAMA/external/thrust/thrust/device_vector.h:26,
                 from /workspace/RAMA/include/dCOO.h:4,
                 from /workspace/RAMA/include/rama_cuda.h:5,
                 from /workspace/RAMA/src/rama_py.cpp:5:
/workspace/RAMA/external/thrust/thrust/system/cuda/detail/guarded_cuda_runtime_api.h:38:10: fatal error: cuda_runtime_api.h: No such file or directory
   38 | #include <cuda_runtime_api.h>
      |          ^~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [src/CMakeFiles/rama_py.dir/build.make:76: src/CMakeFiles/rama_py.dir/rama_py.cpp.o] Error 1
make[2]: *** [CMakeFiles/Makefile2:550: src/CMakeFiles/rama_py.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:557: src/CMakeFiles/rama_py.dir/rule] Error 2
make: *** [Makefile:338: rama_py] Error 2
Traceback (most recent call last):
  File "setup.py", line 120, in <module>
    setup(
  File "/opt/conda/lib/python3.8/site-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/opt/conda/lib/python3.8/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/opt/conda/lib/python3.8/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/opt/conda/lib/python3.8/site-packages/setuptools/command/install.py", line 74, in run
    self.do_egg_install()
  File "/opt/conda/lib/python3.8/site-packages/setuptools/command/install.py", line 116, in do_egg_install
    self.run_command('bdist_egg')
  File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/opt/conda/lib/python3.8/site-packages/setuptools/command/bdist_egg.py", line 164, in run
    cmd = self.call_command('install_lib', warn_dir=0)
  File "/opt/conda/lib/python3.8/site-packages/setuptools/command/bdist_egg.py", line 150, in call_command
    self.run_command(cmdname)
  File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/opt/conda/lib/python3.8/site-packages/setuptools/command/install_lib.py", line 11, in run
    self.build()
  File "/opt/conda/lib/python3.8/distutils/command/install_lib.py", line 107, in build
    self.run_command('build_ext')
  File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "setup.py", line 33, in run
    self.build_extension(ext)
  File "setup.py", line 118, in build_extension
    subprocess.check_call(['cmake', '--build', '.', '--target', ext.name] + build_args, cwd=self.build_temp)
  File "/opt/conda/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'rama_py', '--config', 'Release', '--', '-j8']' returned non-zero exit status 2.

Please try again with latest master.

It is working!!! Thank you soooo much :)


video_player does nor support interlaced video streams.

I have tried Video Player plug-in for Flutter( video_player 0.10.8+1) example code on Android platform with video stream that is interlaced, and was sadly surprised that it does not de-interlace the video...
Tried the same stream with Exoplayer and it does the job.
so I am little confused as i know that video_player uses exoplayer on Android...
Could it be related to flutter architecture?
Any suggestions?

Any Idea why the same exoplayer started through flutter engine can not deinterlace the video?
And if I start exoplayert nativeli it deinterlace video just fine.

Hello, have same issue if needed we can provide stream for tests


Fix uniqueness of PrestaShop versions

Questions
Answers

Description?
Because of a wrong way of removing version duplicates, in some cases, multiple entry of the same PrestaShop version could be added to the prestahop.json file. This PR aims to fix this by changing the way uniqueness is done.

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Related to https://github.com/PrestaShop/PrestaShop/issues/30866

How to test?
Not ready yet but will be: See that after multiple runs, https://integration-api.prestashop-project.org/prestashop doesn't contain duplicate versions of PrestaShop

Possible impacts?

Related to https://github.com/PrestaShop/PrestaShop/issues/30866


Debugging not working.

There is something wrong with sourcemaps I think.
I can't get debugging correspond to correct lines in ts.
Here are some screenshots:
http://stackoverflow.com/questions/40279812/debugging-angular-cli-in-webstorm?noredirect=1

I have same problem.
It seems that old mapfiles loaded.

am having same problem.  debugging was working until I reached a certain number of components (around 20) then it become impossible to set proper breakpoints: either they weren't hit or off by x number of lines.

I was able to fix this by following the upgrade steps in the readme.
I upgraded from 1.0.0-beta.18 to 1.0.0-beta.19-3.
I'm working against master, so I also did a git pull in my local repo and ran npm link again.

beta.18 had a sourcemap problem which was fixed and released in beta19-3. If you can find me a way to repro in a brand new beta.19-3 project I'm happy to look at it.


No such service : ol1

Env:
Harbor CLI version: 0.1.9
==========================
Harbor active services:
webui
==========================
Client: Docker Engine - Community
 Version:    27.2.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.16.2
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.2
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 1
  Running: 1
  Paused: 0
  Stopped: 0
 Images: 1
 Server Version: 27.2.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
 runc version: v1.1.14-0-g2c9f560
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
 Kernel Version: <IP_ADDRESS>-microsoft-standard-WSL2
 Operating System: Ubuntu 24.04.1 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 20
 Total Memory: 15.49GiB
 Name: Tom2024
 ID: 1ec0703a-6d34-4969-ae93-6d711f141527
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  <IP_ADDRESS>/8
 Live Restore Enabled: false

Hi, thanks for trying out Harbor!
Harbor CLI version: 0.1.9

ol1 was just released today in scope of v0.1.24, so please try updating to the most recent version. Update might not work smoothly yet, in that instance resort to manual checkout of the v0.1.24 tag (or simply latest main)

Somehow it works now, maybe some time delay.


[main] Upgrade to latest dependencies

update hack hash in pkg -izabelacg
/cc knative/func-approvers
/assign knative/func-approvers
Produced by: knative-extensions/knobots/actions/update-deps

/approve
/lgtm


Makefile and pom.xml changes

Changes to reflect Makefile and pom.xml changes to include the hadoop-openstack dependency as a profile named object_storage so that we can build CaffeOnSpark using make build object_storage=1

CLA is valid!

I see that the pom.xml file was already corrected in the other PR#162. Sorry for that.

Please combine this PR into #162.

Done. Closing this PR.


[UI] Sorting in the "Projects monitoring" table

Add the sorting in the "Projects monitoring" page table for the following columns:
Project name
Start time
End time
Progress
Status

"Progress" sorting doesn"t sort


Authenticating Using GitHub App for GitHub Runner Scaler Jobs

Using GitHub App for authentication by specifying appKey for scale-rule-auth does not work. The log keeps coming up with the error in the snip below.

Can someone please help me on how to authenticate with appKey instead of personalAccessToken

@kabal2010
It looks like your issue is resolved since you closed this thread.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.

@RamanathanChinnappan-MSFT
I move it to https://github.com/microsoft/azure-container-apps since it's the dedicated repo for Azure Container Apps.


Bring AutoGen to dotnet?

any insights on how to introduce AutoGen to the world of dotnet? It would be truly exciting to witness the potential of multi-agent collaboration in helping dotnet developers to create highly intelligent applications.
@sonichi @luisquintanilla @JakeRadMSFT
Update on 2023/10/22
I'm going to answer my own question here.
I have recently developed a dotnet-version AutoGen, with both code and packages available on GitHub at the following repository: [AgentChat](https://github.com/LittleLittleCloud/AgentChat.
To utilize the package, simply add the nightly build feed from the following URL:

https://www.myget.org/F/agentchat/api/v3/index.json

The features currently supported include:

Connection to OpenAI models
Two-agent chat
Group chat
Function calling

However, some functionalities are not yet available, such as:

Python code execution
Support for LLMs other than those mentioned

Moreover, AgentChat provides some unique functionalities thanks to dotnet feature

typed FunctionCall using source generator: automatically generate FunctionDefinition based on structural comments.
Dotnet code execution: run dotnet script on dotnet interactive.

Here's how to add the package:
<ItemGroup>
    <PackageReference Include="AgentChat.Core" />
    <!-- Adding AgentChat.GPT will enable connection to OpenAI models -->
    <PackageReference Include="AgentChat.OpenAI" />
</ItemGroup>

Further Notes

Please note that this SDK is still in its nascent stage and as such, there's no stable version released yet.
The following steps will involve introducing additional notebook examples, and expanding support for other LLMs.
Collaborative contributions are always welcome.

Makes sense to me especially the potential for integration with existing .NET libraries and tools.
From a repo / ownership perspective I'm happy to follow the AutoGen community lead here.

Step 1 could be: test how well C# works with LLM. For example, create a C# coding agent by modifying the default system message of AssistantAgent, and a C# execution agent by extending execute_code in code_utils.py to support C# code.
It that works well,
Step 2: ask autogen agent to convert python code to C# :)

@sonichi
Step 1 already been tested. MLNet-task-101 is fully driven by dynamic group chat and dotnet

Nice. A PR with C# agents is welcome.

I am considering making that PR !

Bring AutoGen to Semantic Kernel

Would the user proxy agent have to be extended so that it could recognise and execute c# code as opposed to python?
Dotnet has a docker image for a runtime as well as the sdk, so it would also be really nice if the user proxy agent could execute the dotnet code via the docker container.

@dazinator No IMO, we can just provide a function_call called run_dotnet and let llm decide how to execute the code.

@LittleLittleCloud
dotnet interactive looks good. It does appear to execute a different dialect of c# than "standard" c# though, not sure whether that would need any special consideration.
I thought of docker just as means to employ or control the build and execution environment. Its common in dotnet projects to use docker multistage builds - so a dockerfile has a build stage which uses the sdk image to compile the code, and a run stage which uses the runtime image to execute those binaries. The run image could be pushed  to a container registry for onwards deployment for example.
I guess I'm too new to this project to decide if any of that is really desirable in this case. It sounds like dotnet interactive could make that all go away.
My dream use case for autogen would be that I'd want to use it to develop simple dotnet command line applications that could be onwards deployed. For me this would mean not only producing c# code to fulfil a certain task but building that code using the sdk and running it, testing it etc. It's not typical to build run and distribute dotnet apps as 'dotnet interactive' apps so again this is where I was thinking of docker.

To enable such experience, one of the challenges is how to construct a workflow that can be used to incremental editing/improving a workspace or project, rather than a single file. I don't have a very clear answer for that question now, but feel free to provide any thought on it.

I was thinking at a very high level, I'd want to structure something like a dev team, consisting of:

Product Owner Role (user proxy agent)

initiates work by providing a "user story"
is asked to clarify any requirements

Developer (assistant agent)

planning phase

tries to break down user story into set of actionable tasks
if has any questions around the requirements, asks the product owner for clarification

development phase

iterate on the tasks until the code passes QA

e.g might be a task to create the new dotnet project, then add specific classes and tests that implement the required functionality.

let QA know when something is completed for testing.
if QA reports any issues then ask any clarifying questions to QA and then plan a task to fix it.

QA (assistant)

take the output from developer assistant and try to run it.
if the code passes QA checks then TERMINATE

else report any issues back to Developer assistant.

Something like that.
I'm order to try to eliminate some of the complexity, I thought it might be a good idea if this team was always focused on producing an entirely new dotnet project - I.e so it doesn't have to understand any pre-existing code base. I'm not sure how much this helps as I guess if the developer agent has to iterate on its own output then to some degree it has to be able to "understand" the output it has produced in a prior iteration.
I'm completely knew to all this, and I have no feel for whats actually possible yet - so this was going to be my thesis for getting stuck into and learning about this project and just what is possible right now.

Sorry I have no idea about the workspace / single file issue. I thought I had seen another open source project that is able to iterate on a code base containing multiple files, perhaps it was AutoGPT.. but I can't remember :-(

Sorry I have no idea about the workspace / single file issue. I thought I had seen another open source project that is able to iterate on a code base containing multiple files, perhaps it was AutoGPT.. but I can't remember :-(

chatdev. possibly

could you add support for local llm's heres a template that im using that works for me
config_list = [
{
"api_type": "open_ai",
"api_base": "https://yyyyyyyyyy-5001.proxy.runpod.net/v1",
"api_key": "sk-1111111111111111111111111111111111111111"
}
]

.NET Interactive can also run a “csproj” via a Project Kernel. That is something Try .NET does it and we could expand that to fit the scenario emitting a reusable le project / solution
Dr Diego Colombo
(he/him)
Principal software engineer
.NET Interactive https://github.com/dotnet/interactive

From: JunkBoy76 @.>
Sent: Saturday, October 28, 2023 3:58:22 AM
To: microsoft/autogen @.>
Cc: Comment @.***>
Subject: Re: [microsoft/autogen] Bring AutoGen to dotnet? (Issue #48)
could you add support for local llm's heres a template that im using that works for me
config_list = [
{
"api_type": "open_ai",
"api_base": "https://yyyyyyyyyy-5001.proxy.runpod.net/v1",
"api_key": "sk-1111111111111111111111111111111111111111"
}
]
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/autogen/issues/48#issuecomment-1783688424 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAC3WBHTQNMNMC725SILSFDYBR7F5BFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI3DAMZUGYYTGOBXGCSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJWHAYDCMRQGA3TDAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDCOJRHE3DONRWGQ3YFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI3DAMZUGYYTGOBXGCTXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I just don't see any future for multiple codebases unless there is first class support. Things are always going to end up missing, or different, maybe even architecturally or conceptually.

Looks like Qdrant has built support for AutoGen. It'd be interesting to test out the integration in .NET.

Hi @LittleLittleCloud ! Is this still being worked on? If so, how are you keeping up to date with the broader Python counterpart, including beta features?

Which beta feature are you talking about 😀
Get Outlook for iOShttps://aka.ms/o0ukef

From: Erhan Kartaltepe @.>
Sent: Wednesday, November 29, 2023 4:01:35 AM
To: microsoft/autogen @.>
Cc: Mention @.>; Author @.>; Comment @.>; Assign @.>
Subject: Re: [microsoft/autogen] Bring AutoGen to dotnet? (Issue #48)
Hi @LittleLittleCloudhttps://github.com/LittleLittleCloud ! Is this still being worked on? If so, how are you keeping up to date with the broader Python counterpart, including beta features?
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/autogen/issues/48#issuecomment-1830632473 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEAYLOXS4LRMNCEP6TZZWS3YGY7KBBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI3DAMZUGYYTGOBXGCSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJWHAYDCMRQGA3TDAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDCOJRHE3DONRWGQ3YFJDUPFYGLJLMMFRGK3FFOZQWY5LFVI3DAMZUGYYTGOBXGCTXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you were mentioned.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I just don't see any future for multiple codebases unless there is first class support. Things are always going to end up missing, or different, maybe even architecturally or conceptually.

Does this mean you're in favor of merging #924 ? My initial thoughts:

It's difficult for me to imagine it not being disruptive in terms of issues and PRs.
Every dotnet issue and PR will need to be tagged as such.
We will likely end up with many additional issues which go unresolved for long periods of time unless the port has parity with the Python module.
Installing the Python module direct from the repo will pull the dotnet port into the project each time.
My IDE will index symbols from the port (Maybe this can be handled).
Is there a nexus between the main Python module and the dotnet port? Do they interop in some way?

Note: Currently, if I wanted to made use of something in dotnet, I would probably use pythonnet or similar.
Might it be easier for future humans to deal with wrapping the existing module for use in dotnet?

IronPython comes to mind, though I have never used it.
I think there are other ways to wrap a Python module in dotnet as well. The laziest way would probably be to bundle python.
A path to automated transpile would be cool.

Is there a nexus between the main Python module and the dotnet port? Do they interop in some way?

one of the things we are pondering is about using the work in .NET Interactive as a mean of interoperability.

Great to see someone is working on getting AutoGen in .Net!
I also want to point people to https://github.com/SciSharp/BotSharp
Which is a comparable multi-agent llm framework. Check it out!

Porting the source code of AutoGen to .NET/TypeScript/Rust/etc. ist exactly the kind of work, which a system like AutoGen should be able to do.


Can't select certain main module files (.xquery)

I've noticed this bug some time ago but I always work around it. I know when you create a new Run configuration you can select only main modules and not library modules. However, I have some main modules that can't be selected for some reason.
I've tried changing the file name, deleting parts of the content, but I can't really locate why this happens.
even when I only leave this script
xquery version "3.1" encoding "UTF-8"; 1
It doesn't make a difference most of the times. It only randomly starts working after a while.

Can you please first of all clarify what you mean by "can't be selected"? Does it mean that you can't run it? Or does not allow for "auto-generation" of run config (e.g. pressing ctrl-shift-f10)?
Can you please share the screenshots of the right-click menu in the contents of the file when it doesn't work? Also screenshot of the list of 'Run selectbox' in the menu bar would be helpful from the moment when it doesn't work. Please also let me know if there are any errors in the "gutter" area on files that don't allow "selection".
Please let me know if creation of the new run configuration for the file manually (Run -> Edit configurations -> "+" button (Add New Configuration) -> XQuery Main Module) works fine (e.g. lets you do that and actually run it)?

OK sorry for being vague. I had no idea you can create a new configuration by right clicking at the content of the file. I was just trying to manually create a new run configuration. I only have trouble selecting the main module at the screen of the manual run configuration. If I right click in the context of the main module and I select Create filename, it works.
I'm uploading a screenshot, I hope this helps

Can you please try with the latest version (released yesterday)? I did some changes to use the new API for running.

Unfortunately it still isn't working. Here is the file I'm trying to use https://my.pcloud.com/publink/show?code=XZTBPbZVhoPP14rCym1hcUvCqVtshxU2K7k

I understand that the issue only happens when you try to create manually and you are not able to select files on the list of files. I'm fixing that issue. If there's any other problem related to this functionality, please raise a new issue.

If you'd like to get the latest build of the plugin you should be able to build it yourself by following collaboration page and the running
gradlew.bat dist
The built zip file should be in build/distributions. You can use this file to install plugin from disk.
If this doesn't work just let me know and I can prepare the zip for you.


Enabling WhatsApp sharing

Enables WhatsApp Sharing
Closes #236
➕ Changes Introduced

Added WhatsApp icon to the top left corner of the screen via the html file.
Added corresponding event listener in the js file to open Whatsapp in a new tab.
Added code to create the message to be shared.

📷 Screenshots

Thank you for your valuable contribution :)
you can join this open source community for more - https://chat.whatsapp.com/ELpn6eu6b1A0lPXZ9Fr8nO


Pending channel close

Hey guy I've been waiting for a channel close confirmation for 3 weeks and it still says "confirming", probably because onchain fees went up during the closing. The balance of my LDK wallet is 0 BTC and my onchain wallet is't showing the closing tx.
Where's my money bro 👽
you can check the logs:
rn-ldk.log.txt

Same thing happened to me but thanks to Blackhathacker111 who helped me recover all my funds,message him on telegram his telegram username is  https://t.me/Blackhathacker111

Johnnyrickk stfu scammer


Cryptic error when creating a team with a whitespace via api

Gitea version (or commit ref): b9ae16d
Operating system: Debian
Can you reproduce the bug at https://try.gitea.io:

[x] Probably

Description
When creating a new team via the api which contains a whitespace, the api returns the following cryptic error:
[{"fieldNames":["Name"],"classification":"AlphaDashDotError","message":"AlphaDashDot"}]

After digging around in the code for two hours I finally found out the error was caused by a whitespace in the name.
I'd whish to get a more specific error message in that case, googling didn't help much either.

Maybe added a not empty or required to the form tag?

@lunny sounds like a good idea

I'm facing the same issues. I would expect an API to give a proper error message why the validation failed. Otherwise one has to brute force it until it works..

Isn't the message clear? AlphaDashDot means the field should contains alpha or dot or dash .....


Enable MAVEN Parallel Test

According to Maven parallel test, we can run tests in parallel.

Looks good to me, but please could you rebase. The tests should be fixed then.


jupyter.widget.version open call should only take place when the kernel is Python

The version check does not seem to cause any issues, but it does print an error message on the js console. Maybe this check should look at the kernel.info and be performed only for Python kernels.
Something along the lines of this https://github.com/jupyter-incubator/declarativewidgets/blob/7659d9def805b4f7066abeedb3225c09ac153522/elements/urth-viz-ipywidget/urth-viz-ipywidget.html#L104

I think that it is ok to have an error in the js console. We don't prevent other kernels to implement the check!

@SylvainCorlay true... maybe reduce it to a warning?

Good point! 👍 for a warning instead of an error.


Add html option to popover/tooltip

There is an html option for popover/tooltip again. The option is defaulted to true.
Having this option allows us to force the popover to use the .text() method to set the title and content of the popover no matter if bootstrap thinks it detects html or not. The problem is that jQuery seems to unescape values grabbed with the .attr() method, so even if you escape <script>alert('data');</script> to <script>alert("data")</script> and set it as your data-content, bootstrap will get the unescaped value from .attr(), detect that this is html and use the .html() method to set the content of the popover causing an XSS issue. Forcing the use of the .text() method by setting the html option to false lets us make sure that doesn't happen.

<script>alert("data")</script>

<script>alert("data")</script>


The proxy cannot be used

hi! this is a good project ,because jakarta websocket not support proxy, can we use tyrus ClientManager ?
thx

Sigh, it isn't modular
So I asked to go back to raw so we can build distributions, adding it in denies any hope of deploying anything you build.... unless you break the golden rule of never run a JDK in production...
What do you mean doesn't support proxies,

hi! this is a good project ,because jakarta websocket not support proxy, can we use tyrus ClientManager ?
thx

Hello, can you please be more specific about which functionality you need?

hi! this is a good project ,because jakarta websocket not support proxy, can we use tyrus ClientManager ?
thx

Hello, can you please be more specific about which functionality you need?

because don't use proxy, i can't use whatsapp.

hi! this is a good project ,because jakarta websocket not support proxy, can we use tyrus ClientManager ?
thx

Hello, can you please be more specific about which functionality you need?

because don't use proxy, i can't use whatsapp.

Oh, so whatsapp is blocked in your country and you need to use a proxy to connect to it?

hi! this is a good project ,because jakarta websocket not support proxy, can we use tyrus ClientManager ?
thx

Hello, can you please be more specific about which functionality you need?

because don't use proxy, i can't use whatsapp.

Oh, so whatsapp is blocked in your country and you need to use a proxy to connect to it?

yes, i must use a  proxy to connect  it

I want to know when to support Java 11，i see you say   that it might not be important to support Java 11 as of now

I want to know when to support Java 11，i see you say that it might not be important to support Java 11 as of now

Yeah, I've chosen to wait for Java 17 as it will be a LTS. For now, only Java 16 is supported

I want to know when to support Java 11，i see you say that it might not be important to support Java 11 as of now

Yeah, I've chosen to wait for Java 17 as it will be a LTS. For now, only Java 16 is supported

ok , i see. thanks

@hwck I think I ran into your issue -
Pre-connecting the container to the websocket works to override proxies/configs without any dependency or implementation specific configs -
Configure the client with the appropriate proxy settings as per, you can use an empty listener as the client connection overrides that during initialization
https://docs.oracle.com/en/java/javase/15/docs/api/java.net.http/java/net/http/HttpClient.html#newWebSocketBuilder()
HttpClient client = HttpClient.newHttpClient();
		CompletableFuture<WebSocket> ws = client.newWebSocketBuilder()
		                                        .header("Origin","https://web.whatsapp.com")
		                                        //.header("Host","web.whatsapp.com")
		                                        .buildAsync(URI.create("wss://web.whatsapp.com/ws"), new WebSocket.Listener()
		                                        {
			                                        @Override
			                                        public void onOpen(WebSocket webSocket)
			                                        {
				                                        WebSocket.Listener.super.onOpen(webSocket);
			                                        }

			                                        @Override
			                                        public CompletionStage<?> onText(WebSocket webSocket, CharSequence data, boolean last)
			                                        {
				                                        return WebSocket.Listener.super.onText(webSocket, data, last);
			                                        }

			                                        @Override
			                                        public CompletionStage<?> onBinary(WebSocket webSocket, ByteBuffer data, boolean last)
			                                        {
				                                        return WebSocket.Listener.super.onBinary(webSocket, data, last);
			                                        }

			                                        @Override
			                                        public CompletionStage<?> onPing(WebSocket webSocket, ByteBuffer message)
			                                        {
				                                        return WebSocket.Listener.super.onPing(webSocket, message);
			                                        }

			                                        @Override
			                                        public CompletionStage<?> onPong(WebSocket webSocket, ByteBuffer message)
			                                        {
				                                        return WebSocket.Listener.super.onPong(webSocket, message);
			                                        }

			                                        @Override
			                                        public CompletionStage<?> onClose(WebSocket webSocket, int statusCode, String reason)
			                                        {
				                                        return WebSocket.Listener.super.onClose(webSocket, statusCode, reason);
			                                        }

			                                        @Override
			                                        public void onError(WebSocket webSocket, Throwable error)
			                                        {
				                                        WebSocket.Listener.super.onError(webSocket, error);
			                                        }
		                                        });

		WebSocket webSocket1 = ws.get();

@Auties00 This method actually removes the need for JSR entirely, and makes the web socket control java native lol
Is it worth a PR? I'm doing a bit deeper testing but it looks very promising


Crash/exception on macOS Ventura when numpy not explicitly imported

Long-time user of sounddevice, somewhat baffled by an issue I have hit today.
I recently upgraded my M1 MacBook Pro to macOS Ventura, and have found that even simple scripts that use sounddevice are failing to run, including many long-standing scripts that I have previously run without issues. Here's a MWE:
import time
import sounddevice as sd

def audio_callback(out_data, frames, time, status):
    out_data[:] = 0

with sd.OutputStream(callback=audio_callback):
    while True:
        time.sleep(0.1)

When I run the above in arm64 architecture, the script crashes with a SIGBUS:
Bus error: 10

If I run the same script using intel64, I get:
Exception ignored from cffi callback <function _StreamBase.__init__.<locals>.callback_ptr at 0x10c8fbb00>:
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/sounddevice.py", line 859, in callback_ptr
    data = _array(
           ^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/sounddevice.py", line 2702, in _array
    import numpy as np
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/__init__.py", line 388, in <module>
    raise RuntimeError(msg)
RuntimeError: Polyfit sanity test emitted a warning, most likely due to using a buggy Accelerate backend.
If you compiled yourself, more information is available at:
https://numpy.org/doc/stable/user/building.html#accelerated-blas-lapack-libraries
Otherwise report this to the vendor that provided NumPy.
UserWarning: The value of the smallest subnormal for <class 'numpy.float64'> type is zero.

I tried reinstalling Python (3.9/3.10,3.11), reinstalling latest sounddevice (0.4.6) and numpy (1.25.2) via pip, but the issue persists.
I've also reproduced this on two other laptops here running Ventura, one M1 and one x86, both using pip to install. I don't have any earlier macOS versions or non-Apple laptops to test on right now.
Resolution / workaround
Finally, I tried adding an explicit import numpy to the top of the script, and it resolves the issue. I'm not clear what is happening here, or why this has only recently started occurring - this explicit import certainly wasn't needed previously.
Looking at sounddevice.py, I can see that it should import numpy on demand when needed, but it doesn't seem to successfully do so.
Any advice welcomed!

Thanks for reporting this, this is an interesting and quite strange issue!
I don't know what's the underlying cause, but it's great that you found out that import numpy resolves the issue.

Looking at sounddevice.py, I can see that it should import numpy on demand when needed, but it doesn't seem to successfully do so.

Yeah, looks like it.
In #488, I'm trying to call import numpy earlier, can you please try if that also works for you (without using import numpy in your script)?

@mgeier Yes, that fixes it! Thank you!
Very curious one. I guess maybe it's something to do with importing numpy from a cffi callback? I know I've had a few issues on recent Macs with CFFI and memory protection, but I've never really dived deep enough to properly understand it. 🤷🏻♂

I guess it is related to importing it from the callback, but I don't know whether it's because of how CFFI does things, or because it is called from a a thread that's not created by Python, or maybe something entirely different.

Long-time user of sounddevice, somewhat baffled by an issue I have hit today.
I recently upgraded my M1 MacBook Pro to macOS Ventura, and have found that even simple scripts that use sounddevice are failing to run, including many long-standing scripts that I have previously run without issues. Here's a MWE:
import time
import sounddevice as sd

def audio_callback(out_data, frames, time, status):
    out_data[:] = 0

with sd.OutputStream(callback=audio_callback):
    while True:
        time.sleep(0.1)

When I run the above in arm64 architecture, the script crashes with a SIGBUS:
Bus error: 10

If I run the same script using intel64, I get:
Exception ignored from cffi callback <function _StreamBase.__init__.<locals>.callback_ptr at 0x10c8fbb00>:
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/sounddevice.py", line 859, in callback_ptr
    data = _array(
           ^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/sounddevice.py", line 2702, in _array
    import numpy as np
  File "/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/site-packages/numpy/__init__.py", line 388, in <module>
    raise RuntimeError(msg)
RuntimeError: Polyfit sanity test emitted a warning, most likely due to using a buggy Accelerate backend.
If you compiled yourself, more information is available at:
https://numpy.org/doc/stable/user/building.html#accelerated-blas-lapack-libraries
Otherwise report this to the vendor that provided NumPy.
UserWarning: The value of the smallest subnormal for <class 'numpy.float64'> type is zero.

I tried reinstalling Python (3.9/3.10,3.11), reinstalling latest sounddevice (0.4.6) and numpy (1.25.2) via pip, but the issue persists.
I've also reproduced this on two other laptops here running Ventura, one M1 and one x86, both using pip to install. I don't have any earlier macOS versions or non-Apple laptops to test on right now.
Resolution / workaround
Finally, I tried adding an explicit import numpy to the top of the script, and it resolves the issue. I'm not clear what is happening here, or why this has only recently started occurring - this explicit import certainly wasn't needed previously.
Looking at sounddevice.py, I can see that it should import numpy on demand when needed, but it doesn't seem to successfully do so.
Any advice welcomed!

Importing lumpy fixed it thank you so much been looking all over the internet for this


pretained model Page does not exist

when i open the pretained model Page,there is no pretrained models

will

coming soon

uploaded


Convert to TypeScript, rework support for React 18, Refresh latest logic from JotForm

I don't use pnpm so haven't checked in the lock file.
I also haven't checked the storybook, I was testing on a separate project.
Fixed #5.

@awc120 this PR isn't published to NPM yet so that issue isn't from this. To use this PR just copy the https://github.com/mg-aceik/jotform-react/blob/main/lib/index.tsx into your solution.

can we publish this?

@mg-aceik would it be possible to generate so we can release this update?

@mg-aceik can we get this published?

Someone else will need to take over the requested changes here, I'm not using Jotform anymore - switched to Paperform.


On offline NE, show last connection on card and list views (next-heartbeat)

@0xbase12
I think this needs api work too: we don't have the next-heartbeat on this view, where we need it.
On the details view with endpoint /api/nuvlabox-status/<id> I find it, but not from /api/nuvlabox or api/nuvlabox-cluster.
Am I missing something?

Call with @0xbase12 : Fetching nuvlabox-status from Edges overview page.


Add batch subgroup verification, batched bucket addition, parallelisation

Verification for 2 million BW6 points: 6-7s on 8 cores.

As we discussed on Slack, let’s switch to a non-recursive bucket test, at least as a first step. I don’t think your get_num_buckets is optimizing m. Let n be the number of group elements we wish to check subgroup membership for, s be the security parameter, and r be the ratio of the cost of a subgroup membership test to a group addition. The formula I derived for finding m=log2(M) is to find the value 2 ≤ m ≤ floor(log2(n)) that minimizes ceil(s/m) * (n + Mr).
What's the smallest cofactor for BW6? Just trying to figure out if it's worth it to use the small exponent test.

Here's the equation I derived for optimizing the recursive bucket test, where d is the recursion depth and 2 ≤ md ≤ ... ≤ m1 ≤ floor(log2(n)).

TODO: pass an Rng parameter for batch verify bucket assignment randomness, and use fiat-shamir for the seed for no_std as a compromise. Need to split seed into multiple new seeds to use on multiple threads.

Reference doc of current progress courtesy of Psi

Deleted the reference doc @jon-chuang because it had errors as I pointed out in Slack. I still believe the cost equation above is guaranteed to give us more than lambda bits security. The (1+r) factor should be actually be replaced with just r, but r is like 280 for us, so this won't make much of a difference. Happy to copy my thoughts over from Slack justifying the cost equation above.
Anyway, determining the cost function for lambda bits security is for future reference only, as we decided to go with the non-recursive version for this initial PR and circle back on the recursive version if we have time before the trusted setup ceremony begins.

Can this be closed?


disable cgo and use alpine image

build with CGO_ENABLED=0 to output standalone binary
run the binary from alpine docker image

If we are going to put a single go binary in a container, why not run it in a scratch container?

If we are going to put a single go binary in a container, why not run it in a scratch container?

while the idea might be valid, I have no experience with scratch as opposed to alpine, it seems that scratch doesn't have package manager or any locale settings in the environment or shell of any sort - I'm not sure how that will work for us and I can definitely tell that I used to log in with ash on a lot of our alpine images before so not being able to do that might be crippling

If we are going to put a single go binary in a container, why not run it in a scratch container?

while the idea might be valid, I have no experience with scratch as opposed to alpine, it seems that scratch doesn't have package manager or any locale settings in the environment or shell of any sort - I'm not sure how that will work for us and I can definitely tell that I used to log in with ash on a lot of our alpine images before so not being able to do that might be crippling

Those are all true. As we discussed on Discord, the aim here was to drop the 800MB Debian image and going to Alpine brings that to 18MB which is already fine. No need to go further down.


[Feature] List of failed tests with folded logs

Is it possible to generate a list of failed tests, where each entry is only the test name and folded and clickable to show the logs? This would give a better overview of the test failures, with possibility to open and see logs if needed.

I didn't see this issue until now. Is https://github.com/test-summary/action/pull/53 what you're hoping for?

I didn't see this issue until now. Is #53 what you're hoping for?

Yes! An overview of failed tests with expandable tracebacks is really helpful when find and fixing test failures!
Thanks!


How to config force use Python3 for all builds?

Hi,
I had a build environment integration with some other conponents. The build environment has Python2 and Python3. But the default /usr/bin/python points to python2 due some reasons.
Also virtualenv is not available in my environment. So I'd like to check whether there is some way to config the connectedhomeip builds use "python3" instead of "python"?
As I'm facing below error when build all-cluster examples:
ninja: Entering directory `out/all-cluster'
[450/514] ACTION //third_party/connectedhomeip/third_party/pigweed/repo/pw_build:python_lint(//third_party/connectedhomeip/build/toolchain/custom:custom)
FAILED: gen/third_party/connectedhomeip/third_party/pigweed/repo/pw_build/python_lint.pw_pystamp
python ../../examples/all-clusters-app/linux/third_party/connectedhomeip/third_party/pigweed/repo/pw_build/py/pw_build/python_runner.py --gn-root ../../examples/all-clusters-app/linux/ --current-path ../../examples/all-clusters-app/linux/third_party/connectedhomeip/third_party/pigweed/repo/pw_build --default-toolchain=//third_party/connectedhomeip/build/toolchain/custom:custom --current-toolchain=//third_party/connectedhomeip/build/toolchain/custom:custom --touch gen/third_party/connectedhomeip/third_party/pigweed/repo/pw_build/python_lint.pw_pystamp --capture-output -- ../../examples/all-clusters-app/linux/third_party/connectedhomeip/third_party/pigweed/repo/pw_build/py/pw_build/nop.py
  File "../../examples/all-clusters-app/linux/third_party/connectedhomeip/third_party/pigweed/repo/pw_build/py/pw_build/python_runner.py", line 36
    def _parse_args() -> argparse.Namespace:
                      ^

Thanks!

Python3 seems like a reasonable minimal requirement to build CHIP: python2 sunset date is Jan 1 2020: https://www.python.org/doc/sunset-python-2/#:~:text=We have decided that January,as soon as you can.
I would prefer to not make any sort of effort towards trying to  support python2 as that takes development resources.

Set script_executable to python3 in your dotfile (.gn)
https://gn.googlesource.com/gn/+/master/docs/reference.md#other-help-topics-gn-file-variables


std::char::from_digit not working with print_char()

extern crate rustbox;

use rustbox::{Color, RustBox};
use std::char::from_digit;
use rustbox::Key;

fn main() {

    let rustbox = RustBox::init(Default::default()).ok().unwrap();
    for x in 0..rustbox.width() - 1 {
           rustbox.print_char(x, 0, rustbox::RB_NORMAL, Color::Black, Color::Cyan, '-');
    }

    for y in 0..rustbox.height() - 1 {
           rustbox.print_char(0, y + 1, rustbox::RB_NORMAL, Color::Black, Color::Blue, from_digit(y as u32, 10).unwrap());
    }

    loop {
        rustbox.present();
        match rustbox.poll_event(false) {
            Ok(rustbox::Event::KeyEvent(key)) => {
                match key {
                    Key::Char('q') => { break; }
                    _ => { }
                }
            },
            Err(e) => panic!("{}", e),
            _ => { }
        }
    }

}

The following program does not print anything to the screen whereas changing the from_digit() call to a hardcoded char value makes it run fine.

Sorry for this one, this is the expected behavior :) from_digit() takes a single digit and not a number. Converting the number to a string solves the issue.


work firewall blocks YTM beta feature, how to revert?

Is there a way i can revert via config files (linux, debian 64-bit) to the original?  I hit the 'YTM (beta)' button but now all i get is my work firewall blocking page, where it worked fine before with google play.
I've tried uninstalling, but it seems there might still be some files that keep the 'BETA' settings alive.

I just noticed this button on my task bar and was able to swap it out..  Sorry for the ticket!


[WebToolsE2E][Aspire] Running "azd init" to initialize Aspire-Samples/OrleansVoting solution fails with error: "configuring ingress for project voting-fe: the transport property of all bindings should match".

REGRESSION INFO: Worked fine on Aspire 8.0.0-preview.3.24105.21
INSTALL STEPS

Clean machine: Win11 x64 23h2 ENU
Install VS 17.10 Preview 2 [ Includes Aspire 8.0.0-preview.4.24129.7 ]
Apply NuGet dotnet-tools Feeds
Install Docker Desktop for Windows
Install azd [1.7.0-beta.1-daily]

REPRO STEPS

Clone aspire-samples repo from main branch
Checkout the preview.4 branch
Update Aspire version in Directory.Packages.props to latest 8.0.0-previeew.4.24129.7
Open samples\OrleansVoting.sln
Build solution
Deploy using azd

Open the solution folder in a Command Prompt
Runing 'azd init', select 'Use code in the current directory' > Confirm and continue initializing my app, type a new environment name, press enter

ACTUAL:
ERROR: configuring ingress for project voting-fe: the transport property of all bindings should match

EXPECTED
Running 'azd init' successfully

@ReubenBond @davidfowl @bradygaster is it possible to make the Orleans sample deployable via AZD?

This is a new error - it was possible to deploy Orleans to ACA in Preview 3

OK thanks. Who should I assign this to?

I suppose it's me, but I don't know how we fix this. The issue seems to be that we have some internal (TCP) and external (HTTP(S)) endpoints. I'm not sure how we can express that in AZD:
"bindings": {
  "orleans-silo": {
    "scheme": "tcp",
    "protocol": "tcp",
    "transport": "tcp"
  },
  "orleans-gateway": {
    "scheme": "tcp",
    "protocol": "tcp",
    "transport": "tcp"
  },
  "http": {
    "scheme": "http",
    "protocol": "tcp",
    "transport": "http"
  },
  "https": {
    "scheme": "https",
    "protocol": "tcp",
    "transport": "http"
  }
}

That's new for preview.4?

Yes, in p3 we weren't modelling the internal endpoints in the app model. We added that in p4 so that we could have DCP allocate ports on launch to prevent port conflicts when running with > 1 replica. We could hide those internal endpoints when publishing the manifest, as a workaround, but we ultimately need a better solution.

ACA does support additional TCP ingress ports for a service but AZD doesn't currently support configuring them based on the Aspire manifest.
@davidfowl I know you were looking at this recently. Is this tracked anywhere yet?

Ah seems it's tracked here: https://github.com/Azure/azure-dev/issues/3267

Not repro on latest preview.5 branch using VS 17.10 Preview 3 [Includes Aspire 8.0.0-preview.5.24201.12]


"/" should serve the admin

Right now "/" is not a valid route on our HTTP server.
One has to type HOSTNAME:PORT/ui/ to get an admin UI.
/ should give back index.html.
all of the static content should only be accessible under ui/ or static/ (or whatever)

Could I make a suggestion that you maybe have / return a JSON metadata representation with information about the deployed system. This is a really handy pattern for services deployed in larger environments and helps with infrastructure introspection and usability, especially when you have numerous instances of the same service.  Along with information about the deployed service, versions and such it could also include a field with information about the UI path to make it discoverable.

all of the static content should only be accessible under ui/ or static/ (or whatever)

I personally prefer the latter: static.

So to clarify.
We serve the UI and the API on the same port.
I was saying to serve the UI index.html on "/",
and have the UI serve as a way to document the UI.
Francois already added UI links at the bottom of the UI pages to
show what API calls are made.
We could have this a  cluster conf & cluster state api endpoint on api/.
I'm ok to discuss having it on / but I feel hosting the UI is better there.
Opinions @kstaken @guilload ?

I tend to agree with index.html at the root. The rationale would be: all our API endpoints have the prefix /api so why not use the root for the UI.

I'm rethinking serving the UI at the root.
The UI has currently 5 routes:

/
/search
/indexes
/indexes/:indexId
/clusters/members

Like we isolated the API URLs, I think doing the same for the UI makes sense.
Moreover, as you said, the UI will not be the primary way and I would expect in the future the root endpoint to return a JSON containing some information about the version/build.
As for now, I think a simple redirect '/' -> '/ui' would be convenient for our short-term goal of "smoothen the user journey.".

Redirect is good enough


add video path testRunInfo

What is your Test Scenario?
I would like to know the path of the video associated with the running test
What are you suggesting?
To add a videoPath property to the testRunInfo

Hi @philipgriffin
Your use case is a part of Sending custom data to reporter  enhancement. Track this issue to be notified about our progress.
As a workaround, you can pass the 'video path' option to reportTestDone method via meta  parameter.


Does SecretManagement.LastPass work with cygwin64 installed lastpass.cli?

I am having problem with making SecretManagement.LastPass find my cygwin64 installed lastpass.cli.
Tried different variation of :
Register-LastPassVault -Name 'Vault' -Path "C:\cygwin64\bin\lpass.exe"
Always:
throw "lpass executable not found or installed."
When trying Connect-LastPass -Vault 'Vault' -User xxxx
Should it work?

I think it should... It's probably getting stuck here:
https://github.com/TylerLeonhardt/SecretManagement.LastPass/blob/main/SecretManagement.LastPass.Extension/SecretManagement.LastPass.Extension.psm1#L109
it shouldn't be wrapping in quotes because then Get-Command fails


Ask for Telegram username (optional)?

May be useful to skip the "We've selected you... now let's talk on Telegram" email

Contacting people directly on a medium that doesn't randomly mark messages as spam and deliver them to /dev/null seemed a good idea, but it's not that important, really...
Consider that any data on a person we won't select is "useless" and "fills" the database, too.

In fact... so... closed asd


useInfiniteQuery not fetching all the data

Describe the bug
When using infinite queries the data array does not contain all returned results.
I added an infinite scroll to a table component that does an initial request and then refetches the data with an added filter
It looks something like this:
// Some code cut for brevity

() => {
const [logs, setLogs] = useState([]);
const source = CancelToken.source();
const scrollId = useSelector((state) => state.scrollId);
const filters = useSelector((state) => state.filters);
const total = useSelector((state) => state.total);
const onPagination = useCallback(fetchMore)
const addFilters = () => {
source.cancel();
dispatch(resetScrollAction())
dispatch(addFiltersAction())
};
const { remove, fetchMore } = useInfiniteQuery('logs', getLogs.bind(null, filters, scrollId, source), {
    retry: false,
    refetchOnWindowFocus: false,
    refetchInterval: Infinity,
    staleTime: Infinity,
    refetchOnReconnect: false,
    cacheTime: Infinity,
    getFetchMore: (last, all) => all?.flat().length < total,
    onSuccess(data) {
        setLogs(data.filter(Boolean).flat()); // Returns not complete list of results
     },
})

useEffect(() => {
addFilters() // setting up a new search with added filter parameters
},[])

useEffect(() => {
remove() // Purge cache and refetch the query when filters change
}, [filters])

// ...
}

Expected behavior
After purging the cache the data should be refetched and infinite scroll should return all results.
Additional context
The first result it always returned. Then some of the next pagination results are missing.
I removed all options for auto refetching / retrying as I would like to decide myself when to require data.
EDIT: Same thing if I don't modify the filters at all  - so while dong regular scrolling not all data is returned even though according to redux dev tools the fetch succeeded.

Ok managed to fix this. The problem was I set a very low debouce interval on my scroll meaning some data was requested in quick succession which might have caused it to not be persisted correctly or so I'm guessing. After setting a minimum debouce of 1s the problem went away.

Quick question: why are you „syncing“ the data manually to state in onSuccess rather then just using the data that is returned from useInfiniteQuery ?

This looks to be a misunderstanding of how queries work. They have their own state and syncing state from them to local state should be unnecessary. Please open a new issue with a codesandbox (hopefully forked from an existing working example) that shows the unexpected functionality a bit better.

@tannerlinsley i'm new to using react-query and in general the documentation is good and the implementation it's simple, especially for those who have used apollo, swr... but i'm really not understand useInfiniteQuery. I'm doing an implementation with nextjs and i need SSR but the prop comes from server are different from client! on the client the data mutates?
I followed the implementation examples, and i have this:
Request
export async function fetchCollections(options?: Options) {
  const endpoint = getApiEndpoint('getCollections');

  try {
    const currentPage = options?.params?.page;
    const { data } = await request.get(endpoint, {
      params: merge({}, { limit: 24 }, options?.params)
    });

    return {
      data: data?.data,
      nextPage: +currentPage + 1,
      total: data?.total
    };
  } catch (error) {
    throw handleRequestError(error);
  }
}

Page component
const { data, fetchMore, isLoading, isSuccess } = useInfiniteQuery(
  collectionsType,
  async (key, page = 1) => await fetchCollections({ params: { page } }),
  { getFetchMore: lastGroup => lastGroup?.nextPage }
);

return (
  <List>
    {map(data, (collections, index: number) => (
      <Fragment key={index}>
        {map(collections.data, (collection: CollectionProps) => (
          <CollectionItem
            key={collection.id}
            {...collection}
          />
        ))}
    </Fragment>
  ))}
</List>
):

// SSR
export async function getServerSideProps() {
  const queryCache = new QueryCache();
  const { data, total } = await queryCache.prefetchQuery(collectionsType, fetchCollections);

  return {
    props: {
      data,
      dehydratedState: dehydrate(queryCache),
      namespacesRequired: ['common', 'collections'],
      total
    }
  };
}

But i'm getting this

and the data mutates? something bad?


[Feature request] Spline chart functionality

The library looks great! Do you have plans on supporting spline and areaspline charts?
There is a great doc with a variety of options for types of line interpolations:

This is a good idea. Spline is something that is seriously needed.

@sweetyams We'd love to! We're currently working on making these as easy to use as we can, as well as contribution guidelines. Charts sure have plenty of use cases, so this'll help people to add stuff they wish to :)

I added spline functionality to a line type chart, it is also supported with area (regionFill).
It can be toggled with: lineOptions { spline: true }.
see fork: https://github.com/nniclas/charts.git


Actually keeping the process alive if an error occurs

If you have a syntax error in your code the grunt process will fallover which is pretty annoying and contrary to what keepAlive is supposed to do. This commit fixes this behaviour. The only issue is that watchify appears to need to have been built successfully otherwise it just hangs so I've had to add a check to see if it has already built successfully otherwise it will fail.

This problem appears to be back for me


internal: fix direction issues of "example layouts"

Describe the bug

fixed in https://github.com/paranext/paranext-core/pull/1049


Install @babel/plugin-proposal-class-properties

This plugin is aimed to enable proposal features to our app. Like states in a class component.

We don't need this feature because at this time babel suports this.


Make JabbR localizable

I think JabbR should adopt a way to make the UI localizable.
I've already checked how jQueryUI components, such as the DatePicker uses external resources.
For formatted strings, we could use a function with parameters ? eg. : enteredRoom: function(nick, room) { return nick + ' just entered room ' + room; }, but there are certainly better ways to do this.
I could help to translate and organize resources, but I prefer that one of the main contributors start with overall architecture.

This plugin also helps: https://github.com/jquery/globalize
Maybe ask server for resource file?

That was exactly that kind of advices I was looking for :)
I love the File.lang.js convention for including resources, where datas are stored as simple javascript object. It could allow dynamic loading and/or static linking based on needs. If you want to force your ui in a certain language, you can. If you want to load it based on browser languages, it's also possible.

FYI jQuery/Globalize is what was once the globalization library in ASP.NET AJAX. You might think that's a bad thing :) But it was one of the gems of it. It's based on the rich .NET globalization information, which is why there's like 300+ cultures supported. Also, and more importantly, jQueryUI is planning on using it for its own globalization in the future. So it's got a backing and a future, probably.

Any progress on this?