Please update python dependencies in this repository

Dear authors,
I'm failed to install python dependencies via Anaconda. The reason is the version of dependencies is old, some dependencies even are decapitated. Update dependencies as you can, please.  Here is the error message from CondaEnvException:
`(magnet_env_) ➜  magnet git:(main) conda env create -f environment_GPU.yml
Collecting package metadata (repodata.json): done
Solving environment: done
Downloading and Extracting Packages
_libgcc_mutex-0.1    | 3 KB      | ############################################################################################################### | 100%
zlib-1.2.11          | 120 KB    | ############################################################################################################### | 100%
xz-5.2.5             | 438 KB    | ############################################################################################################### | 100%
blas-1.0             | 6 KB      | ############################################################################################################### | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: / Enabling nb_conda_kernels...
Status: enabled
done
Installing pip dependencies: | Ran pip subprocess with arguments:
['/home/lykas/miniconda3/envs/MagNet/bin/python', '-m', 'pip', 'install', '-U', '-r', '/exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt']
Pip subprocess output:
Collecting ase==3.20.1
Using cached ase-3.20.1-py3-none-any.whl (2.2 MB)
Collecting cvxopt==1.2.5
Using cached cvxopt-1.2.5-cp37-cp37m-manylinux1_x86_64.whl (11.6 MB)
Collecting googledrivedownloader==0.4
Using cached googledrivedownloader-0.4-py2.py3-none-any.whl (3.9 kB)
Collecting isodate==0.6.0
Using cached isodate-0.6.0-py2.py3-none-any.whl (45 kB)
Collecting joblib==0.16.0
Using cached joblib-0.16.0-py3-none-any.whl (300 kB)
Collecting llvmlite==0.35.0
Using cached llvmlite-0.35.0-cp37-cp37m-manylinux2010_x86_64.whl (25.3 MB)
Collecting networkx==2.5
Using cached networkx-2.5-py3-none-any.whl (1.6 MB)
Collecting numba==0.52.0
Using cached numba-0.52.0-cp37-cp37m-manylinux2014_x86_64.whl (3.2 MB)
Processing /home/lykas/.cache/pip/wheels/8c/76/0b/eb9eb3da7e2335e3577e3f96a0ae9f74f206e26457bd1a2bc8/prettytable-0.7.2-py3-none-any.whl
Processing /home/lykas/.cache/pip/wheels/be/2d/1f/87004485ec41ab6f625f9320fd23d4755f2d7fe8cbc60d85dd/python_louvain-0.14-py3-none-any.whl
Collecting rdflib==5.0.0
Using cached rdflib-5.0.0-py3-none-any.whl (231 kB)
Collecting scikit-learn==0.23.2
Using cached scikit_learn-0.23.2-cp37-cp37m-manylinux1_x86_64.whl (6.8 MB)
Collecting scipy==1.5.2
Using cached scipy-1.5.2-cp37-cp37m-manylinux1_x86_64.whl (25.9 MB)
Collecting threadpoolctl==2.1.0
Using cached threadpoolctl-2.1.0-py3-none-any.whl (12 kB)
Collecting torch-cluster==1.5.8
Using cached torch_cluster-1.5.8.tar.gz (38 kB)
Processing /home/lykas/.cache/pip/wheels/9f/98/e2/5e1e57b8ac9f135413e7d3b0399761e9243194864b4ffcf3d7/torch_geometric-1.6.3-py3-none-any.whl
Collecting torch-scatter==2.0.5
Using cached torch_scatter-2.0.5.tar.gz (20 kB)
Collecting torch-sparse==0.6.8
Using cached torch_sparse-0.6.8.tar.gz (34 kB)
Collecting torch-spline-conv==1.2.0
Using cached torch_spline_conv-1.2.0.tar.gz (12 kB)
Processing /home/lykas/.cache/pip/wheels/ac/5c/3a/a80e1c65880945c71fd833408cd1e9a8cb7e2f8f37620bb75b/torchfile-0.1.0-py3-none-any.whl
Collecting tqdm==4.54.0
Using cached tqdm-4.54.0-py2.py3-none-any.whl (69 kB)
Requirement already satisfied, skipping upgrade: matplotlib>=2.0.0 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from ase==3.20.1->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 1)) (3.3.1)
Requirement already satisfied, skipping upgrade: numpy>=1.11.3 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from ase==3.20.1->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 1)) (1.19.1)
Requirement already satisfied, skipping upgrade: six in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from isodate==0.6.0->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 4)) (1.15.0)
Requirement already satisfied, skipping upgrade: decorator>=4.3.0 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from networkx==2.5->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 7)) (4.4.2)
Requirement already satisfied, skipping upgrade: setuptools in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from numba==0.52.0->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 8)) (49.6.0.post20200814)
Requirement already satisfied, skipping upgrade: pyparsing in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from rdflib==5.0.0->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 11)) (2.4.7)
Requirement already satisfied, skipping upgrade: requests in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (2.24.0)
Requirement already satisfied, skipping upgrade: jinja2 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (2.11.2)
Requirement already satisfied, skipping upgrade: torch in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (1.6.0)
Requirement already satisfied, skipping upgrade: pandas in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (1.1.1)
Requirement already satisfied, skipping upgrade: h5py in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (3.1.0)
Requirement already satisfied, skipping upgrade: pillow>=6.2.0 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from matplotlib>=2.0.0->ase==3.20.1->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 1)) (7.2.0)
Requirement already satisfied, skipping upgrade: python-dateutil>=2.1 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from matplotlib>=2.0.0->ase==3.20.1->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 1)) (2.8.1)
Requirement already satisfied, skipping upgrade: certifi>=2020.06.20 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from matplotlib>=2.0.0->ase==3.20.1->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 1)) (2020.11.8)
Requirement already satisfied, skipping upgrade: kiwisolver>=1.0.1 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from matplotlib>=2.0.0->ase==3.20.1->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 1)) (1.2.0)
Requirement already satisfied, skipping upgrade: cycler>=0.10 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from matplotlib>=2.0.0->ase==3.20.1->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 1)) (0.10.0)
Requirement already satisfied, skipping upgrade: urllib3!=1.25.0,!=1.25.1,<1.26,>=1.21.1 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from requests->torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (1.25.10)
Requirement already satisfied, skipping upgrade: idna<3,>=2.5 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from requests->torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (2.10)
Requirement already satisfied, skipping upgrade: chardet<4,>=3.0.2 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from requests->torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (3.0.4)
Requirement already satisfied, skipping upgrade: MarkupSafe>=0.23 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from jinja2->torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (1.1.1)
Requirement already satisfied, skipping upgrade: future in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from torch->torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (0.18.2)
Requirement already satisfied, skipping upgrade: pytz>=2017.2 in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from pandas->torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (2020.1)
Requirement already satisfied, skipping upgrade: cached-property; python_version < "3.8" in /home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages (from h5py->torch-geometric==1.6.3->-r /exp/Chieh/magnet/condaenv.zhgaiuzn.requirements.txt (line 16)) (1.5.1)
Building wheels for collected packages: torch-cluster, torch-scatter, torch-sparse, torch-spline-conv
Building wheel for torch-cluster (setup.py): started
Building wheel for torch-cluster (setup.py): finished with status 'error'
Running setup.py clean for torch-cluster
Building wheel for torch-scatter (setup.py): started
Building wheel for torch-scatter (setup.py): finished with status 'error'
Running setup.py clean for torch-scatter
Building wheel for torch-sparse (setup.py): started
Building wheel for torch-sparse (setup.py): finished with status 'error'
Running setup.py clean for torch-sparse
Building wheel for torch-spline-conv (setup.py): started
Building wheel for torch-spline-conv (setup.py): finished with status 'error'
Running setup.py clean for torch-spline-conv
Failed to build torch-cluster torch-scatter torch-sparse torch-spline-conv
Installing collected packages: scipy, ase, cvxopt, googledrivedownloader, isodate, joblib, llvmlite, networkx, numba, prettytable, python-louvain, rdflib, threadpoolctl, scikit-learn, torch-cluster, tqdm, torch-geometric, torch-scatter, torch-sparse, torch-spline-conv, torchfile
Attempting uninstall: scipy
Found existing installation: scipy 1.1.0
Uninstalling scipy-1.1.0:
Successfully uninstalled scipy-1.1.0
Running setup.py install for torch-cluster: started
Running setup.py install for torch-cluster: finished with status 'error'
Pip subprocess error:
ERROR: Command errored out with exit status 1:
command: /home/lykas/miniconda3/envs/MagNet/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-oqd27ojh/torch-cluster/setup.py'"'"'; file='"'"'/tmp/pip-install-oqd27ojh/torch-cluster/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-kkbhrjo2
cwd: /tmp/pip-install-oqd27ojh/torch-cluster/
Complete output (57 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.7
creating build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/radius.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/rw.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/grid.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/init.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/graclus.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/knn.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/fps.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/nearest.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/sampler.py -> build/lib.linux-x86_64-3.7/torch_cluster
running build_ext
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-oqd27ojh/torch-cluster/setup.py", line 103, in
packages=find_packages(),
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/init.py", line 163, in setup
return distutils.core.setup(**attrs)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/core.py", line 148, in setup
dist.run_commands()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/wheel/bdist_wheel.py", line 290, in run
self.run_command('build')
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 87, in run
_build_ext.run(self)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 344, in build_extensions
self._check_abi()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 675, in _check_abi
check_compiler_abi_compatibility(compiler)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 248, in check_compiler_abi_compatibility
if not check_compiler_ok_for_platform(compiler):
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 208, in check_compiler_ok_for_platform
which = subprocess.check_output(['which', compiler], stderr=subprocess.STDOUT)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 411, in check_output
**kwargs).stdout
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['which', 'g++']' returned non-zero exit status 1.
ERROR: Failed building wheel for torch-cluster
ERROR: Command errored out with exit status 1:
command: /home/lykas/miniconda3/envs/MagNet/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-oqd27ojh/torch-scatter/setup.py'"'"'; file='"'"'/tmp/pip-install-oqd27ojh/torch-scatter/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-e3wqrnl8
cwd: /tmp/pip-install-oqd27ojh/torch-scatter/
Complete output (59 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.7
creating build/lib.linux-x86_64-3.7/torch_scatter
copying torch_scatter/init.py -> build/lib.linux-x86_64-3.7/torch_scatter
copying torch_scatter/placeholder.py -> build/lib.linux-x86_64-3.7/torch_scatter
copying torch_scatter/segment_csr.py -> build/lib.linux-x86_64-3.7/torch_scatter
copying torch_scatter/utils.py -> build/lib.linux-x86_64-3.7/torch_scatter
copying torch_scatter/segment_coo.py -> build/lib.linux-x86_64-3.7/torch_scatter
copying torch_scatter/scatter.py -> build/lib.linux-x86_64-3.7/torch_scatter
creating build/lib.linux-x86_64-3.7/torch_scatter/composite
copying torch_scatter/composite/init.py -> build/lib.linux-x86_64-3.7/torch_scatter/composite
copying torch_scatter/composite/logsumexp.py -> build/lib.linux-x86_64-3.7/torch_scatter/composite
copying torch_scatter/composite/softmax.py -> build/lib.linux-x86_64-3.7/torch_scatter/composite
copying torch_scatter/composite/std.py -> build/lib.linux-x86_64-3.7/torch_scatter/composite
running build_ext
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-oqd27ojh/torch-scatter/setup.py", line 83, in
packages=find_packages(),
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/init.py", line 163, in setup
return distutils.core.setup(**attrs)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/core.py", line 148, in setup
dist.run_commands()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/wheel/bdist_wheel.py", line 290, in run
self.run_command('build')
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 87, in run
_build_ext.run(self)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 344, in build_extensions
self._check_abi()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 675, in _check_abi
check_compiler_abi_compatibility(compiler)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 248, in check_compiler_abi_compatibility
if not check_compiler_ok_for_platform(compiler):
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 208, in check_compiler_ok_for_platform
which = subprocess.check_output(['which', compiler], stderr=subprocess.STDOUT)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 411, in check_output
**kwargs).stdout
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['which', 'g++']' returned non-zero exit status 1.
ERROR: Failed building wheel for torch-scatter
ERROR: Command errored out with exit status 1:
command: /home/lykas/miniconda3/envs/MagNet/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-oqd27ojh/torch-sparse/setup.py'"'"'; file='"'"'/tmp/pip-install-oqd27ojh/torch-sparse/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-x2_njwcb
cwd: /tmp/pip-install-oqd27ojh/torch-sparse/
Complete output (75 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.7
creating build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/transpose.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/coalesce.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/rw.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/convert.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/storage.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/select.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/sample.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/narrow.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/spmm.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/metis.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/init.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/tensor.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/eye.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/permute.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/utils.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/reduce.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/cat.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/masked_select.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/diag.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/spspmm.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/matmul.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/saint.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/index_select.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/mul.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/add.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/padding.py -> build/lib.linux-x86_64-3.7/torch_sparse
copying torch_sparse/bandwidth.py -> build/lib.linux-x86_64-3.7/torch_sparse
running build_ext
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-oqd27ojh/torch-sparse/setup.py", line 101, in
packages=find_packages(),
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/init.py", line 163, in setup
return distutils.core.setup(**attrs)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/core.py", line 148, in setup
dist.run_commands()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/wheel/bdist_wheel.py", line 290, in run
self.run_command('build')
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 87, in run
_build_ext.run(self)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 344, in build_extensions
self._check_abi()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 675, in _check_abi
check_compiler_abi_compatibility(compiler)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 248, in check_compiler_abi_compatibility
if not check_compiler_ok_for_platform(compiler):
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 208, in check_compiler_ok_for_platform
which = subprocess.check_output(['which', compiler], stderr=subprocess.STDOUT)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 411, in check_output
**kwargs).stdout
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['which', 'g++']' returned non-zero exit status 1.
ERROR: Failed building wheel for torch-sparse
ERROR: Command errored out with exit status 1:
command: /home/lykas/miniconda3/envs/MagNet/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-oqd27ojh/torch-spline-conv/setup.py'"'"'; file='"'"'/tmp/pip-install-oqd27ojh/torch-spline-conv/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-fqju561m
cwd: /tmp/pip-install-oqd27ojh/torch-spline-conv/
Complete output (52 lines):
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.7
creating build/lib.linux-x86_64-3.7/torch_spline_conv
copying torch_spline_conv/weighting.py -> build/lib.linux-x86_64-3.7/torch_spline_conv
copying torch_spline_conv/init.py -> build/lib.linux-x86_64-3.7/torch_spline_conv
copying torch_spline_conv/basis.py -> build/lib.linux-x86_64-3.7/torch_spline_conv
copying torch_spline_conv/conv.py -> build/lib.linux-x86_64-3.7/torch_spline_conv
running build_ext
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-oqd27ojh/torch-spline-conv/setup.py", line 87, in
packages=find_packages(),
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/init.py", line 163, in setup
return distutils.core.setup(**attrs)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/core.py", line 148, in setup
dist.run_commands()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/wheel/bdist_wheel.py", line 290, in run
self.run_command('build')
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 87, in run
_build_ext.run(self)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 344, in build_extensions
self._check_abi()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 675, in _check_abi
check_compiler_abi_compatibility(compiler)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 248, in check_compiler_abi_compatibility
if not check_compiler_ok_for_platform(compiler):
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 208, in check_compiler_ok_for_platform
which = subprocess.check_output(['which', compiler], stderr=subprocess.STDOUT)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 411, in check_output
**kwargs).stdout
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['which', 'g++']' returned non-zero exit status 1.
ERROR: Failed building wheel for torch-spline-conv
DEPRECATION: Could not build wheels for torch-cluster, torch-scatter, torch-sparse, torch-spline-conv which do not use PEP 517. pip will fall back to legacy 'setup.py install' for these. pip 21.0 will remove support for this functionality. A possible replacement is to fix the wheel build issue reported above. You can find discussion regarding this at https://github.com/pypa/pip/issues/8368.
ERROR: Command errored out with exit status 1:
command: /home/lykas/miniconda3/envs/MagNet/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-oqd27ojh/torch-cluster/setup.py'"'"'; file='"'"'/tmp/pip-install-oqd27ojh/torch-cluster/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-cju9t7co/install-record.txt --single-version-externally-managed --compile --install-headers /home/lykas/miniconda3/envs/MagNet/include/python3.7m/torch-cluster
cwd: /tmp/pip-install-oqd27ojh/torch-cluster/
Complete output (59 lines):
running install
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.7
creating build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/radius.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/rw.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/grid.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/init.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/graclus.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/knn.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/fps.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/nearest.py -> build/lib.linux-x86_64-3.7/torch_cluster
copying torch_cluster/sampler.py -> build/lib.linux-x86_64-3.7/torch_cluster
running build_ext
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-install-oqd27ojh/torch-cluster/setup.py", line 103, in
packages=find_packages(),
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/init.py", line 163, in setup
return distutils.core.setup(**attrs)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/core.py", line 148, in setup
dist.run_commands()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/command/install.py", line 61, in run
return orig.install.run(self)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/install.py", line 545, in run
self.run_command('build')
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 87, in run
_build_ext.run(self)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/distutils/command/build_ext.py", line 340, in run
self.build_extensions()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 344, in build_extensions
self._check_abi()
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 675, in _check_abi
check_compiler_abi_compatibility(compiler)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 248, in check_compiler_abi_compatibility
if not check_compiler_ok_for_platform(compiler):
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 208, in check_compiler_ok_for_platform
which = subprocess.check_output(['which', compiler], stderr=subprocess.STDOUT)
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 411, in check_output
**kwargs).stdout
File "/home/lykas/miniconda3/envs/MagNet/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['which', 'g++']' returned non-zero exit status 1.
----------------------------------------
ERROR: Command errored out with exit status 1: /home/lykas/miniconda3/envs/MagNet/bin/python -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-oqd27ojh/torch-cluster/setup.py'"'"'; file='"'"'/tmp/pip-install-oqd27ojh/torch-cluster/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-cju9t7co/install-record.txt --single-version-externally-managed --compile --install-headers /home/lykas/miniconda3/envs/MagNet/include/python3.7m/torch-cluster Check the logs for full command output.
failed
CondaEnvException: Pip failed`

Dear @hazdzz,
Thank you for your issue. Indeed, we realized that using this conda create tool may fail, and that's why we have "Installation method 2 (manual installation)". Whether using the .yml files can work also depends on your other environment specifications. Hope this helps!
Best,
Yixuan He (Sheryl)


Database reconnect utility (Resolves #233)

Description of PR

A automated way to reconnect to the database if the connection is dropped and also retry queries.
What component(s) does this PR affect?

[x] Back-End (Database, Microservices, Containers, etc)
[ ] Front-End (Flask, API, etc)
[ ] Docs
[ ] Build System

Does the PR require changes on other components? If yes, please mark the components:

[ ] Back-End (Database, Microservices, Containers, etc)
[ ] Front-End (Flask, API, etc)
[ ] Docs
[ ] Build System

Related Issue

Resolves #233
Solution

Type

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Docs update
[ ] None of the above

Checklist:

[x] I have read the contributing guide and my code conforms to the guidelines.
[ ] This change requires a change in the documentation.
[ ] I have updated the documentation accordingly.

@slowr pending error for the PR listener impl (not to forget):
 database - 2019-09-21 18:15:26,822 - ERROR @ _retrieve_most_recent_config_hash: failed to retrieved most recent config hash in db
backend           | Traceback (most recent call last):
backend           |   File "database.py", line 1482, in _retrieve_most_recent_config_hash
backend           |     )[0]
backend           | IndexError: list index out of range

Could you also sum up in a comment the issue with the DB duplicates that comes up with the new approach for db writes?

:running: Benchmark Results :running:

BGP Updates (updates/sec): 644
Hijacks Detected (hijacks/sec): 25

:running: Benchmark Results :running:

BGP Updates (updates/sec): 704
Hijacks Detected (hijacks/sec): 27

:running: Benchmark Results :running:

BGP Updates (updates/sec): 630
Hijacks Detected (hijacks/sec): 23

:running: Benchmark Results :running:

BGP Updates (updates/sec): 636
Hijacks Detected (hijacks/sec): 27

:running: Benchmark Results :running:

BGP Updates (updates/sec): 725
Hijacks Detected (hijacks/sec): 28

:running: Benchmark Results :running:

BGP Updates (updates/sec): 702
Hijacks Detected (hijacks/sec): 26

LGTM!


⚠ SpeakUpForHope.org has degraded performance

In f9b507d, SpeakUpForHope.org (https://www.speakupforhope.org) experienced degraded performance:

HTTP code: 200
Response time: 29663 ms

Resolved: SpeakUpForHope.org performance has improved in 5ab8d50 after 41 minutes.


Adds configuration element for tunnel for JNLP agent

This is to allow to set -tunnel on the JNLP agent

@lsegal Mind having a look?

bump :)

bump :)


Feat/eightbitlab blurview

Summary
Trying to make the utilisation of this library easier on Android (ref and hooks doesn't work easily with this library).
Removing the necessity of viewRef on Android AND now the BlurView can have children just like on iOS.
Following this issue recommendations :
https://github.com/react-native-community/react-native-blur/issues/350

Test Plan

What's required for testing (prerequisites)?
Nothing. I just updated the native library on Android
What are the steps to reproduce (after prerequisites)?
Just use the library without needing to add viewRef on Android.
Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[X] I have tested this on a device and a simulator
[X] I added the documentation in README.md
[X] I mentioned this change in CHANGELOG.md
[X] I updated the typed files (TS and Flow)
[X] I added a sample use of the API in the example project (example/App.js)

Hello, good job! Tried to use this commit, got error com.cmcewen.blurview.BlurringView cannot be cast to android.view.ViewGroup

Hi, could you try to clean the build folders. There are no mention of BlurringView in my branch I think.

Finally, it worked! Thank you!

Hey @Kureev (or any other maintainers), would be great if this could get merged.

I'll try this PR today after work and merge it if everything is fine.
Many thanks for working on this 🙌

@Daavidaviid thank you for awesome work.
Could you please replace all mentions of 500px-android-blur to BlurView in links in README?
It can be a little confusing if you click on 500px-android-blur link but see another library :)

Oh I didn't pay attention. It's corrected

Once this gets merged in, when can we expect a release that contains this feature? This seems like a really impactful feature.

@Kureev Just want to kindly ask about status of this PR.
Have you had a chance to try it?
And one more question: whether is it possible to release a new version on npm as it get merged?

Can confirm that the code works. Example is a bit off, but I will fix it in my follow-up commit.
Great job, and thank you one more time for your contribution!

Would be nice if the version of this package was bumped

I might be missing something, but when I tried this with React Navigation on Android to blur a BottomTabBar, the blur worked properly, but the entire screen was "dimmed".
Doing something like this:
<BlurView
      style={{
        position: 'absolute',
        left: 0,
        right: 0,
        bottom: 0
      }}
      blurType={'dark'}
      intensity={100}
>
  <BottomTabBar {...this.props} />
</BlurView>

Hey, awesome update!
I may have found a few bugs:

If you have multiple BlurViews on the same screen, it seems like only the first one is working. 2nd one is not transparent anymore? Maybe it's blurred two times?

It seems like border-radius is not working.

With blurType="dark" the entire screen is dimmed. With blurType="light" , it works as expected.

Hmm... BlurView component drops the performance of the app significantly, even if the blurred component would be tiny.
Could there be a bug that it always blurs the whole screen, but then it shows only the blurred part?
It would explain the bugs that happen when overflow: hidden is not set.

I experience this too. I've decided to skip this, even though the designer is really unhappy

@Frans-L @elan I have the same issue even with the current released version (3.4.1). So I don't think it has something to do with this pr

I was able to work around the full-screen issue I was having by:

Using overlayColor={'transparent'}
Putting a translucent element below the others to perform the darkening.

Putting borderRadius and overflow of hidden on a container element does work for rounding.

to fix your issue, add overflow style property to its parent.

@Frans-L ~ ah yes, you are correct, this also solves the issue 👍

Can you be so kind to follow-up on the docs update and/or compose a separate PR/PRs for any issues you find? I'm not that active in this repo anymore, but I promise to review your changes if you cc me there 🙏

I experience this too. I've decided to skip this, even though the designer is really unhappy

This library is not ready for any Android app in production sadly.

https://github.com/react-native-community/react-native-blur/issues/365


[TechDocs] Use DocsSyncroniser logger to get doc build logs

Hey, I just made a Pull Request!
Closes #10335
This adds the DocsSyncroniser logger as an additional transport to the logger that streams build events to the frontend, so they can also be used from the backend.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hello! It seems like there might have been something not to do with these changes that caused the two action failures, e.g. Error: Input required and not supplied: github-token seems like it might be an intermittent error- could I have some assistance rerunning these please?

...seems like it might be an intermittent error- could I have some assistance rerunning these please?

You got it!

I'm keen to have a go at this to get it sorted, but keen for some guidance before coming back with a PR that's not what the team is looking for

Thanks for your patience on us getting back to you on this!  The approach in this PR seems reasonable, but my primary concern is that the overall backend logs could become quite verbose for those who are less interested in having these logs come through.
I see a couple of possible ways to take that into consideration:
Configuration
You could imagine having a new configuration setting like techdocs.captureBuildLogs, which you could use to determine whether or not to add the logger as you've done in this PR.
Injection
A more flexible option would be to introduce a new, optional buildLogger (or similarly named) argument to the createRouter function (perhaps only on the OutOfTheBoxDeploymentOptions type, since it's only relevant for "prepared/generated in backstage backend" deployment configuration).  This could then be passed into the DocsSynchronizer and used as you've done it here (and it could either default to a void logger, or only conditionally log if it's set).
I'd maybe encourage the latter, as it not only gives the flexibility of "do I want these logs or not," but also "can I treat these logs differently?"  You could achieve the same effect as you have here by passing the logger twice:
// Capture build logs in the same place / format as TechDocs backend logs
await createRouter({
  // ...
  logger: env.logger,
  buildLogger: env.logger,
});

// Capture build logs in a distinct way
await createRouter({
  // ...
  logger: env.logger,
  buildLogger: customLogger,
});

// Do not capture build logs (same behavior as today)
await createRouter({
  // ...
  logger: env.logger,
});

Thank you so much! The injection method sounds really interesting, I'll take a stab at implementing it over the weekend

Hello @emmaindal! I think I have the injection working, I've just pushed the changes (will fix up the signing now)


constrain version of base package installed with cli

cli.rb recipe will not constrain the version of the base cdap package installed (via package dependency of the cdap-cli package, causing CDAP-8213.
This simply adds a package resource to explicitly install it first.  This technically may be duplicate resource when running fullstack. I can split out the "base package install" into its own recipe if anyone feels strongly, but may be overkill.

travis fixes in #197


Unable to launch Bot Framework Composer

I am unable to launch Bot Framework Composer. I get an error as shown in the Pic below.
Details:

BFC version = 2.1.2
Launching this behind a corporate network
Proxy setting done and verified.

Can anyone guide on how to overcome this issue (not sure if this is a bug, hence reporting this as a issue)

Hi @mys2kor.
Used a fresh Composer 2.1.2 C# bot, and I'm not able to reproduce this issue from my end.
Environment:

Windows 11
Composer 2.1.2
Node v14.20.0
.NET Core Runtime 3.1

After creating C# Empty Bot Template in Composer 2.1.2, It is able to start without issues.

@mys2kor, to clarify: are you using Node (Preview) or C# Composer bot?

@ramfattah  I was not even able to go that far. I get this error when I try to open the Application. One time the application opened & I was able to login to the company azure account. Then I choose Node (Preview) and selected the 2nd option (bot with language I think). It showed the Downloading for a while and then got struck at Building run time. Even after 30-40minutes, nothing happened. So I closed the application.

My environment is
Environment:
Windows 10
Composer 2.1.2 & 2.1.1 (I tried with both versions)
Node v16.14.2
.NET Core Runtime 3.1 (I an not sure about this)

@mys2kor, could you please try to uninstall Composer and delete the following directories:

Uninstall Composer

If installed for local user, delete: C:\Users<USER>\AppData\Local\Programs\Bot Framework Composer
If installed for all users, delete: C:\program files\bot framework composer

Download and install the latest version of Composer and try again.

Try the above steps and let me know if you still get that error message. Thanks.

@ramfattah I have done clean installation (uninstall, restart the PC, reinstall) more than 10times since 2 days on both 2.1.1 & 2.1.2 versions. No Use.
However, just now I stumbled upon something. I use https://github.com/genotrance/px/  as a HTTP(s) proxy server. When Px is running, I get the error I am getting during the launch. If the Px is not running, I do not get this error.
Please also not that after the launch happens, I need to have PX running to login to my Azure account if not I cannot login to my Azure account!
Also, The window to install is popping up on its own once in a while.(Pic attached)
I have moved the .exe file to a different folder so, I am 100% sure I have not clicked on it at all & still yet the install window pops up!
I am available on Teams if you want to have a quick call.

@ramfattah I have been able to to a 'work around' of this issue by doing the following
a. When installing BFC (2.1.1 or 2.1.2), we need Px to be running, else it will not install.
b. However, during the launch of BFC, Px SHOULD NOT be running!!! Else we get the error I shared with you.
c. When logging into BFC (we have to login every time we launch the application!), we again need Px to be running else we get ‘No Azure Directories Found” error.
Also, When I close the program the window to install is popping up ! Not sure why but it does !!!
Bu there is now another issue. Reporter here https://github.com/microsoft/BotFramework-Composer/issues/9333

@mys2kor
Could you please run Composer in debug mode using the following directions and attempt to reproduce the failure?
Then send the output of the debugging console window.
Steps to run Composer in debug mode:

Completely close Composer if already open
Go to Composer's install location (mine is at C:\Users{username}\AppData\Local\Programs\Bot Framework Composer)
Open Windows command line terminal in that directory
run set DEBUG=composer*
run the executable from the terminal.

Ex: in CMD: run "Bot Framework Composer.exe"

You have enabled debugging successfully if you see prefixed composer:____  in the log:

We will take a look at the log to see what is the cause of this issue.
Let me know if you have any questions. Thanks.

@ramfattah
The pics of the Logs are below.
I get the error when I try to open BFC when Px is running (no error when Px is not running).

Thank you @mys2kor for sharing the logs.

@mys2kor
have you had a chance to follow Configure a proxy server documentaion?
https://docs.microsoft.com/en-us/composer/configure-composer-proxy?tabs=windows
It describes how to configure a proxy server to allow Composer to access resources.

@ramfattah Yes. I have followed the configured the proxy server as given in the link above.

Hi @tonyanziano, any ideas regarding this issue?

We started with this issue today, we are trying to reproduce the error.

@ceciliaavila any update on this?

Hi @mys2kor, @ramfattah, @johnataylor, @tracyboehrer, we were able to reproduce this issue by following the next steps:

TLDR: we couldn’t find a solution nor workaround for this issue, since it could be related to the px program, the proxy, or Application Insights not supporting Headers + Body when it comes in the content response when retrieving the AppId (more information).

Run the genotrance/px program with a custom proxy (px --proxy=x.x.x.x --debug).

Start Composer from the terminal with the following environment variables (DEBUG=composer* no_proxy=localhost https_proxy=http://localhost:3128 http_proxy=http://localhost:3128, how to configure env variables).

Note: when using Composer from the source code, set the APPINSIGHTS_INSTRUMENTATIONKEY=xxx env variable, otherwise it will not fail.

Steps to cause the issue

Note: not all proxies fail with the 'request-context' issue, so probably could be a proxy misconfiguration issue.
Note: these steps don’t always make Composer fail, in any case, keep trying the following steps with different proxies or combinations (always involves the Microsoft login dialog).
Note: here are the list of proxies we used to test this (they are gathered from the https://free-proxy-list.net/ website just for testing purposes)

<IP_ADDRESS>:8080 (FAIL)
<IP_ADDRESS>:1088 (FAIL)
<IP_ADDRESS>:3128 (NOT FAIL)

a. Open Composer, click on the 'Sign in' button and then close the Microsoft login dialog.
b. Change the px proxy by cancelling the current running command instance, and repeat the step 1 (without closing Composer).
c. Click on the 'Sign in' button and close the Microsoft login dialog again.
d. Close and open Composer (should fail).
e. Even changing to another proxy that have the possibility to have the same issue, it will continue failing.

More information
This issue is being raised by the Application Insights library when it tries to log something, the failure is originated when gathering the AppId from the Application Insights resource under the API Access section (url to gather the AppId https://dc.services.visualstudio.com/api/profiles/<APPINSIGHTS_INSTRUMENTATIONKEY>/appId).
Moreover, this URL according to the Application Insights' code, should only return the AppId (uuid format), but instead when the proxy returns the Headers and Body in the content response, it makes the request-context header variable fail when is set, due to invalid values.
Furthermore, diving deeper into the px's code (python) we discovered that is saving the headers into the same buffer data as the page's body when creating the HTTP bridge. This HTTP bridge is being executed when the CURL method isn't 'CONNECT' as when it is working as expected.
Additional Context
- We couldn’t find a workaround for this issue, since Application Insights is integrated into Composer and the variable APPINSIGHTS_INSTRUMENTATIONKEY cannot be changed at runtime (without having a value, so the Application Insights' code is never setup).
- Even if the Application Insights is accessing the URL and returns anything other than the AppId, it will fail if the request-context header isn't in the right format (e.g. it could return an HTML page (with a failure), Header + Body, etc).
- We believe this issue is either originated from the px program, the proxy configuration, or the Application Insights library not supporting the possibility of receiving Headers and Body in the content response (more information) when sending messages through an HTTP proxy (https proxy is not supported according to Application Insights' code).
Images
px program using the same buffer data (wfile) for the headers.

Application Insights when receiving the request from https://dc.services.visualstudio.com/api/profiles/<APPINSIGHTS_INSTRUMENTATIONKEY>/appId, that comes with the Headers and Body in the same content response.

The current version of https://github.com/genotrance/px cannot be used with Bot Framework Composer


operator: ingress on GKE doesn't work

Describe the bug
» kubectl describe ingresses.extensions vault                                                         (bonifaidobk6a/default)
Name:             vault
Namespace:        default
Address:          <IP_ADDRESS>
Default backend:  vault:8200 (<IP_ADDRESS>:8200)
Rules:
  Host  Path  Backends
  ----  ----  --------
  *     *     vault:8200 (<IP_ADDRESS>:8200)
Annotations:
  nginx.ingress.kubernetes.io/backend-protocol:  HTTPS
  ingress.kubernetes.io/backends:                {"k8s-be-30882--bcb59d1076ba8df3":"Unknown"}
  ingress.kubernetes.io/forwarding-rule:         k8s-fw-default-vault--bcb59d1076ba8df3
  ingress.kubernetes.io/protocol:                https
  ingress.kubernetes.io/secure-backends:         true
  ingress.kubernetes.io/target-proxy:            k8s-tp-default-vault--bcb59d1076ba8df3
  ingress.kubernetes.io/url-map:                 k8s-um-default-vault--bcb59d1076ba8df3
Events:
  Type     Reason  Age    From                     Message
  ----     ------  ----   ----                     -------
  Normal   ADD     38m    loadbalancer-controller  default/vault
  Warning  Sync    37m    loadbalancer-controller  Error during sync: error running backend syncing routine: unable to find nodeport {default/vault/8200 31568 8200 HTTP 8200 false <nil>} in any service
  Normal   CREATE  37m    loadbalancer-controller  ip: <IP_ADDRESS>
  Warning  Sync    19m    loadbalancer-controller  Error during sync: error running backend syncing routine: unable to find nodeport {default/vault/8200 31312 8200 HTTP 8200 false <nil>} in any service

To Reproduce

Get a GKE cluster with HTTP load balancing enabled
kubectl apply -f kubectl apply -f operator/deploy/operator-rbac.yaml
kubectl apply -f kubectl apply -f operator/deploy/operator.yaml
kubectl apply -f kubectl apply -f operator/deploy/rbac.yaml
kubectl apply -f kubectl apply -f operator/deploy/cr.yaml

Hi @bonifaido ,  that's a quick fix. I've pulled the latest changes and tried it again on my cluster but still I'm seeing the same error. I deleted all existing ones, changed serviceType to NodePort and deployed those four resources files on my cluster.
Any suggestion?

Thie change is only available currently on the master branch, so please try to change the operator image to master.

I am certain that I'm on git master branch and I can see the changes from the PR as I did the git pull.

Please run kubectl describe on the operator deployment and attach the Vault CR.

$ kubectl describe deployment  vault-operator
Name:               vault-operator
Namespace:          default
CreationTimestamp:  Thu, 30 May 2019 12:54:56 -0400
Labels:
Annotations:        deployment.kubernetes.io/revision: 1
kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{"prometheus.io/port":"8383","prometheus.io/scrape":"true"},"name":"...
prometheus.io/port: 8383
prometheus.io/scrape: true
Selector:           name=vault-operator
Replicas:           1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:       Recreate
MinReadySeconds:    0
Pod Template:
Labels:           name=vault-operator
Service Account:  vault-operator
Containers:
vault-operator:
Image:      banzaicloud/vault-operator:latest
Port:       8383/TCP
Host Port:  0/TCP
Command:
vault-operator
Liveness:   http-get http://:8080/ delay=4s timeout=1s period=10s #success=1 #failure=1
Readiness:  http-get http://:8080/ready delay=4s timeout=1s period=10s #success=1 #failure=1
Environment:
WATCH_NAMESPACE:   (v1:metadata.namespace)
POD_NAME:          (v1:metadata.name)
OPERATOR_NAME:    vault-operator
Mounts:
Volumes:
Conditions:
Type           Status  Reason

Available      True    MinimumReplicasAvailable
Progressing    True    NewReplicaSetAvailable
OldReplicaSets:
NewReplicaSet:   vault-operator-b8c5c566c (1/1 replicas created)
Events:

Okay, so the operator is still using latest (which is the latest release), please change the tag to master.

Great. It is working.


error on large files

I get a markdown_conversion_failed_because_of_read_failed error when tying to upload a 12k line json file, is it timing out on upload or something?, replacing the file with a smaller one works fine.

I think you should advise Slack support, it seems that it is an issue with their API

I'm also having this problem.
Could someone explain what are the real limitations we have in the files.upload endpoint?

@McSlurryHole have you find the answer?

@idoshamun It's been 8 months so I don't quite remember but I did contact slack and it was a problem with their API. from memory there was a certain flag I had to set or something, you can probably close this issue.

thanks for the quick answer :)


next/previous commenting range command doesn't work

I'm on a mac. setting it to be option+f10 works though

I realized they only work if I've made a comment in the particular editor.

it started to work the moment I had at least one comment in the edtior

@meganrogge did the original keybinding work after you added comment? Even before adding a comment I'm seeing the command work.

that keybinding still doesn't work for me (maybe my keyboard or something)...? but also, when I use a different keybinding, it does try to run the command. I'm now seeing this error.
Cannot read properties of undefined (reading 'getActiveRange')
``

![Screenshot 2023-09-22 at 8 18 37 AM](https://github.com/microsoft/vscode/assets/29464607/5e12c8b2-4c12-43c8-ba84-94e3c16a0e0f)

I have confirmed that the default keyboard shortcut works on mac: cmd+k cmd+option+down-arrow.
There's probably something up with your keybindings that's causing this. You could try the "Developer: Toggle Keyboard Shortcuts Troubleshooting" command and see what it outputs.
I'm fixing this error though: https://github.com/microsoft/vscode/issues/193728#issuecomment-1731600635

removed bug because tracking in that other issue


What does %H parse?

I have a standard NCSA log format, to which every line has two extra fields: the scheme (http or https), and the virtual host name.
So I’m specifying a custom format:
goaccess \
     --date-format "%d/%b/%Y" \
     --time-format "%H:%M:%S" \
     --log-format "%h %^[%d:%t %^] \"%r\" %s %b \"%R\" \"%u\" %H %v” \
     ...

According to the manpage, that should be correct:
       %v     The canonical Server Name of the server serving the request (Virtual Host).
...
       %H     The request protocol.

Now in my generated reports, I see virtual hostnames, but they are formatted like this:
ttp example.com
ttps example.com
ttp example.net
ttps example.net

Am I using %H correctly? If not, can the manpage elaborate what it means by “The request protocol” by citing a few examples?

Hi @remino
If you get a line from Apache LOG or NGinX LOG, you will see similar to:
<IP_ADDRESS> - - [21/Sep/2024:18:09:08 +0000] "GET /Something-is-Here.html HTTP/1.1"
So, the keyword HTTP/1.1 is "request protocol" identified with %H.
At Manual in Specifiers Section you can read more about this here.
In truly, nowadays, it is have possible values like: HTTP/1.0,  HTTP/1.1 or HTTP/2.0.
That means very old protocol 1.0, http/https 1.1 and http/https 2.
And so, probability it will have http/3.0 for new one!


Duplicates

Fixes #209.
And improves fake operation generation :

Generation of duplicates with +/- 1 day
Generation of twice the same operation on the same import

Very nice idea to make the fake account generator create duplicate operations! Thank you for this PR. A few things to fix before it can land.

Looks perfect, cheers!


Create Python If-Else.py

I found that the solutions for python is missing in this repository. So, I am adding them

Adding a new file- "python"

Sorry, this repo is currently not accepting pull requests for new solutions (please see new contributing.md file). Thank you.


AP computation for Revisited Oxford/Paris datasets

Hi, congratulations on the great work and thanks for providing this reference implementation!
I have a question regarding AP computation. The convention for the Oxford/Paris datasets (and their revisited extensions) is to use an interpolation method, by averaging two adjacent precision points then multiplying by the recall step (see implementation by @filipradenovic here, and my reimplementation here). This is different from the "finite sum" method (Wikipedia reference), which I believe is the one used by sklearn.metrics.average_precision_score -- which is used by your code. Please correct me if I am wrong here :)
So, if what I state above about your code is correct, I am wondering what the mAP figures would be if you use the different mAP convention.
To illustrate the differences in implementation, here is a toy example, where the AP computed by the sklearn implementation is much higher than the one computed by the convention of Oxf/Par datasets (0.5 versus 0.3333):
# similarities and labels.
s = [3, 4, 1, 2]
y = [1, 0, 1, 0]

# computed from the library used in your code, produces AP=0.5.
from sklearn.metrics import average_precision_score
sklearn_ap = average_precision_score(y, s)
print("sklearn AP: %f" % sklearn_ap)

# computed from Revisited dataset convention, using my code, produces AP=0.333333.
# Note: see installation instructions at: https://github.com/tensorflow/models/blob/master/research/delf/INSTALL_INSTRUCTIONS.md
from delf.python.detect_to_retrieve import dataset
import numpy as np
ranks = []
for rank, i in enumerate(np.argsort(-np.array(s))):
  if y[i]:
    ranks.append(rank)
revisited_ap = dataset.ComputeAveragePrecision(ranks)
print("revisited AP: %f" % revisited_ap)

Overall, my guess would be that the results would not differ by that much since these datasets are large, but it would be good if can be sure of that. Also, as I said above, I may have missed something, so please feel free to correct me :)

Hi @andrefaraujo,
You are right, sklearn.metrics.average_precision_score uses the "finite sum" method, which is different from the "interpolation" method used by Radenovic et al. in the Revisited versions of Oxford5K and Paris6K. This is something that we overlooked, so thank you so much for pointing it out.
I updated the code using your AP computation function and re-run all the evaluations, and in line with your guess, the difference between both implementations is less significant if the dataset and the number of relevant images is large. In the worst case, the AP figure decreases by less than half point. For example, these are the different mAPs for RParis6K and ROxford5K:
Using the "finite sum" method:
RParis6K (med/hard) = 80.35 / 61.03
RParis6K (med/hard) = 67.36 / 42.76

Using the "interpolation" method:
RParis6K (med/hard) = 80.31 / 60.86
RParis6K (med/hard) = 67.13 / 42.26

In any case, I agree that our evaluation should also follow the dataset convention, so in addition to updating the code, I will also update the numbers in the README showing the new AP computation, and check if there's any case in our experiments where this difference can be more significant and problematic.
Thanks again! :)

Thanks for the quick response, @almazan ! Great that we can compare everything using the exact same metrics now.
Can you please reply to this thread once results are updated in the README?

Hi @andrefaraujo, I just updated the numbers in the README using the "interpolation" method fo the AP computation. Thanks again for pointing this out! :)

Thanks again! :)

Adding some resources to this discussion, maybe something will benefit from seeing it:

Simple example of "interpolation" AP computation: revisitop issue #2
Original "interpolation" implementation from the Oxford Buildings dataset that set the trend: compute_ap.cpp


Can't send message in active VIM window

This came to me via DM in Discord from Manuel#1982
im trying to figure out how to send a message to the active wim window
/run SELECTED_CHAT_FRAME.editBox:SetText("test message") ChatEdit_SendText(SELECTED_CHAT_FRAME.editBox, 0)
this is working on the default whisper tabs but wont on the wim ones
thank you

Thanks, he messaged me as well. I replied to him. For record I will respond here as well:
You'll want to look for WIM.EditBoxInFocus. If it isn't nil, then you'll want to SetText to it. The SendText function will not work in WIM however. You will need to use WoW's API to send messages directly to the user. You can get the selected user like this:
if (WIM.EditBoxInFocus ~= nil) then
    local user = WIM.EditBoxInFocus:GetParent().theUser
    local isWhisper = WIM.EditBoxInFocus:GetParent().type == 'whisper'
    if (isWhisper) then
         SendChatMessage("My special message", "WHISPER", nil, user)
    end
end

Unfortunately that is a lot and limits you in your macro size.
I'll see about adding something to do all this for you. Where you can just execute a command to send a message in the window currently in focus. I'm not sure when I will get around to that yet... Might be in the new year.

I just pushed an update with the tool you need. The caveat is that the editbox must be focused so you wont be able to keybind it because you'd be typing in the box instead, you'd have to click the macro.
/run WIM.sendToFocused("This is my message")
It takes a separate parameter to match the window type if you only want it to sent to chat windows for example and not a whisper.
/run WIM.sendToFocused("This is for chat windows only, whispers will not get it.", "chat")
Hope that accomplishes what you're looking for.


in-toto attestations (ITE-6) as a formatter.

This PR implements the basic support for https://github.com/tektoncd/chains/issues/65.
The formatter uses type hinting to be able to extract information to prepare the in-toto attestation.

Closing this in favour of https://github.com/tektoncd/chains/pull/89 which is rebased.


Could not find module 'SwiftSMTP' for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator

Hey, I'm using this library and it works on a real device.
But when I try building for a simulator, I get:

Could not find module 'SwiftSMTP' for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator, at: /Users/user/Library/Developer/Xcode/DerivedData/myapp-gvdqdjdvdskiwrduhviuliugsnuz/Build/Products/Debug staging-iphonesimulator/SwiftSMTP.swiftmodule

I'm running on Apple silicon M1, Xcode 13.4.1
Any idea how to solve this?

I don''t believe this is specific to SwiftSMTP.  Perhaps some of these suggestions will help you:
From Apple's developer's forum:
https://developer.apple.com/forums/thread/123614
And on Stackoverflow here:
https://stackoverflow.com/questions/56957632/could-not-find-module-for-target-x86-64-apple-ios-simulator


Update README.md

update READMe to remove some whitespace

@0xJepsen can you take a look at this and let me know if it looks better? Github's in line markdown renderer is fidgety and not allowing me to put Pluto in the same line as the logo but i made other changes


fix title count to exclude config keys (presetColors, disable)

Fix the count displayed in the Panel Title to not include the non-css variable config keys

appreciate the fix! could you include a patch changeset and we'll get this merged


Introduce Support for Response Headers

Description
Response Headers can now be documented.
Closes #445
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Added new unit test to notarize a route documenting response headers, and verify the generated OAS contains the headers.
Locally ran a playground where responseHeaders() is called and verified they appeared on the /docs page.

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have updated the CHANGELOG in the Unreleased section
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

awesome, ty 🚀


New formatter options usedn in README

Coverage remained the same at 100.0% when pulling 4c99c0ee5fb48a176d1a7c60d53e13ea3f703172 on readme-fix into 50d067c0bcafd093cd55c26cdd1e9e8b37cd08ed on master.

Coverage remained the same at 100.0% when pulling 4c99c0ee5fb48a176d1a7c60d53e13ea3f703172 on readme-fix into 50d067c0bcafd093cd55c26cdd1e9e8b37cd08ed on master.


Problem installing idb-connector

Hello,
I am trying to install idb-connector to execute SQL queries on DB2 (IBM i V7R2). My npm is in version 6.4.1, and node in version 10.15.0. And I'm having a problem. Here is the log debug generated during install process.
Thank you in advance for your help.
2019-03-04T13_49_38_994Z-debug.log

Why are you running the npm install from /QOpenSys/pkgs/bin?

Sorry, it was just my last test.
From my test application (SQLquerySample), I have this log file.
2019-03-04T16_37_43_480Z-debug.log
I don't have package.json for my test application. Is it mandatory to install the idb-connector ?
Sorry for my questions, I am a beginner in node.js.
Thank you for your quick answer !

No, it's not required - it's just a warning. The problem is here:
1156 verbose stack Error<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
1156 verbose stack spawn ENOENT
1156 verbose stack     at ChildProcess.<anonymous> (/QOpenSys/pkgs/lib/nodejs10/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
1156 verbose stack     at ChildProcess.emit (events.js:182:13)
1156 verbose stack     at maybeClose (internal/child_process.js:962:16)
1156 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
1157 verbose pkgid<EMAIL_ADDRESS>1158 verbose cwd /www/NodeJs10/SQLquerySample
1159 verbose OS400 7.2
1160 verbose argv "/QOpenSys/pkgs/lib/nodejs10/bin/node" "/QOpenSys/pkgs/bin/npm" "i" "idb-connector"
1161 verbose node v10.15.0
1162 verbose npm  v6.4.1

The problem is that it's falling back to building the package instead of downloading the pre-built. I think this is something for @dmabupt or @abmusse to look at.

@GautierFR
Few lines standout from the log file:
1139 warn lifecycle npm is using /QOpenSys/pkgs/lib/nodejs10/bin/node but there is no node binary in the current PATH. Use the--scripts-prepend-node-pathoption to include the
 1141 verbose lifecycle<EMAIL_ADDRESS>PATH: /QOpenSys/pkgs/lib/nodejs10/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/www/NodeJs10/SQLquerySample/node_modules/idbconnector/node_modules/.bin:/www/NodeJs10/SQLquerySample/node_modules/.bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin 1142 verbose lifecycle<EMAIL_ADDRESS>CWD: /www/NodeJs10/SQLquerySample/node_modules/idb-connector
Is /QOpenSys/pkgs/bin on your path?
run echo $PATH
I suspect this issue is related to your PATH. Looks like /QOpenSys/pkgs/bin is not on your path.
It could be using an older OPS version of node from /QOpenSys/usr/bin.
You can try appending /QOpenSys/pkgs/bin to your path with:
PATH=/QOpenSys/pkgs/bin:$PATH

Thank you very much. It was the path problem.
With PATH=/QOpenSys/pkgs/bin:$PATH in CALL QP2TERM, I get the right installation

<EMAIL_ADDRESS>added 67 packages from 29 contributors and audited 98 packages in 15.286s
found  [92m0 [0m vulnerabilities

@GautierFR
Glad that solved your problem. One thing to note is that the above only sets the PATH for your current session. If you want to add /QOpenSys/pkgs/bin to your PATH permanently you can add it to your .profile file see the docimentation here


[Prefactoring] Document env struct

Fixes #

Proposed Changes

Prefactoring for KafkaBroker with dataplane-per-broker-resource
Document env struct

Release Note

Docs

/test integration-tests_eventing-kafka-broker_main

/cherry-pick release-1.7


Maintain scroll positions both Y and X position.

Hi, can we make scroll position state so that during page navigation for large list we don't have to scroll from start position.

@GhazanfarKhan Currently, this is not possible out of the box, but you can remember and set scroll position manually.
I will think about this feature.
Related to: #24

Well I used react-window library with your component, since my list are huge I dont want them to render all. react-window also provide scroll position and helper method to move to index or item.
Thanks.

Well I used react-window library with your component, since my list are huge I dont want them to render all. react-window also provide scroll position and helper method to move to index or item.
Thanks.

Could you share your code for show the integration with react-window?


can't connect multiple times to victim when using payload

when built with payload enabled, most of the times the "victim" enters a state which is no more able to be connected by the "attacker" after the first time.
I.E. , following that log line from the victim
INFO: inject execute procedure
another connection from the attacker results in the attacker going timeout and no "attacker authenticated" lines logged on the victim

Hi @FoSoFix. And thanks for trying badcat.

most of the times the "victim" enters a state which is no more able to be connected by the "attacker" after the first time.

That is odd, but I'd say that your payload is possibly crashing. When payload is enabled, badcat just configures Tor server and launches the payload in a new process, thus, I hardly think there is a problem there. It may be the case that our patches to Tor are causing this issue, changing some flow in the virtual connection, I may need to run some tests to confirm that.
Would you provide the steps reproduce the issue?


Exclude electron module from browserify transform in pre 9.0.0

If left in, electron does not properly load the electron module but instead tries to load the app binary directly via the path.txt.
I believe the correct course of action should be to exclude the electron module from the browserify transform. This allows electron to load the module via the built in node require() in electron. It seems electron does some magic for it's own module by loading from its asar.
Note: I'm not sure which branch I should use for pre 9.0.0 patches like this. Let me know if anything needs to change.

will close as we won't be working on v8 more in this repo. thanks!


Secondary keybindings to restore previous functionality

Description
UPDATE: As suggested here this PR has been expanded to restore all the mnemonic keybindings that were removed in https://github.com/napari/napari/pull/3072/files as secondary shortcuts.
Supersedes https://github.com/napari/napari/pull/4696

This PR makes the experience of annotating labels layers much nicer.
It adds a keybinding where you hold "F" to activate flood fill mode, and automatically deactivates when you release the key.
This is similar to the keybinding where you hold "Space"r to activate pan-zoom mode, which also automatically de-activates when you release the key.
Advantages
The benefits of this PR are:
1. A simpler, less annoying workflow when annotating labels, and

2. It conforms more with the behaviour of other image software (Paintera using "F" to fill, so does the Microscopy Image Browser, etc.) This makes it more natural for users to remember and use, especially if they are familiar with other tools.

An example
Previously, if you were annotating a lot of blobs with different label ids on an image, you
1. Select paint mode (hotkey shortcut "2")

2. Draw the outline of your object (click and drag with the left mouse button)

3. Select flood fill mode (hotkey shortcut "3")

4. Click inside the outline you have just drawn

5. Increment the label id (hotkey shortcut "+")
   ... and continue from step one again.

With this PR, assuming you are already starting in paint mode you can:
1. Draw the outline of your object (click and drag with the left mouse button)

2. Hold the "F" key down and click the region you want to fill

3. Increment the label id (hotkey shortcut "+")
   ... and continue from step one again. I find this is a lot more natural to use in practice.

Type of change
* [ ]  Bug-fix (non-breaking change which fixes an issue)

* [x]  New feature (non-breaking change which adds functionality)

* [ ]  Breaking change (fix or feature that would cause existing functionality to not work as expected)

* [x]  This change requires a documentation update

How has this been tested?
* [x]  I've added a new test to `napari/layers/labels/_tests/test_labels_keybindings.py`, where the test structure is modeled off the pan-zoom keybinding tests used for other layers.

Final checklist:
* [x]  My PR is the minimum possible work for the desired functionality

* [x]  I have commented my code, particularly in hard-to-understand areas

* [?] I have made corresponding changes to the documentation

* [x]  I have added tests that prove my fix is effective or that my feature works

* [ ]  If I included new strings, I have used `trans.` to make them localizable.
  For more information see our [translations guide](https://napari.org/docs/dev/guides/translations.html).

Awesome :D

Works perfectly—I did have to napari --reset though, maybe due to a clash with my keybinds? I may have set/unset that keybind before.

Works perfectly—I did have to napari --reset though, maybe due to a clash with my keybinds? I may have set/unset that keybind before.

Yes. Because there is no migration mechanism for keybind.

Note: this isn't exactly a new feature or keybinding, according to the docs this should already be the case:

You can quickly select the fill bucket by pressing the F key when the labels layer is selected.

https://github.com/napari/napari/blob/main/docs/howtos/layers/labels.md?plain=1#L261-L262

Good catch! When keybinds were overhauled in https://github.com/napari/napari/pull/3072 the docs weren't updated. Maybe should just add back all the old mnemonic keybinds as secondary keybinds, to match the docs?

Good catch! When keybinds were overhauled in #3072 the docs weren't updated. Maybe should just add back all the old mnemonic keybinds as secondary keybinds, to match the docs?

Yes, definitely!

Related: it would also be better for the discoverability of shortcuts if the docs were substantially improved. There is some information here, but it's not very readable: https://napari.org/stable/guides/preferences.html?highlight=shortcuts#shortcuts

Yup, some more user-centric docs would be a good idea. I had previously made a related Issue:
https://github.com/napari/napari/issues/5033

@napari/core-devs I've updated this PR to merge in main and use the new app model shortcut format. I've picked B for the preserve labels shortcut to try to meet all the constraints of:

left side of keyboard
not a bare modifier (which app-model doesn't support anyway)
not a combination but a single key

Also, 2 was duplicated on shapes layer in main, so I've changed the transform mode to 7 there.
Pending tests, I think this should be ready to merge in the later slots of the PR party. 😃 🥳

I have no idea why docs is failing, but it seems unrelated to this PR:
generating gallery...
generating gallery for gallery... [  1%] 3D_paths.py
WARNING: Error drawing visual <Volume at 0x7fb2106a9280>
Aborted (core dumped)

The other check failures are also related to the recent typing updates I think. So I think this should be ready to merge!


Some minor refactoring of azcore

Moved ARM resource ID types and helpers to an internal package so they can be leveraged elsewhere.  The public versions are type-aliased to the matching internal implementations.
policyFunc has moved to the shared package so it can be used elsewhere. Sanitizing of URLs has been split into its own function. Moved a func-local constant to the shared package.

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

The tracing work will build on these changes, and I wanted to keep them separate to simplify the review.  There should be no functional changes.


Rethink src/helpers/responsiveness

Why
Responsive sizes are not consistent with sizes used in the designs or the rest of RCL
What
Change
const sizes = {
  desktop: 1280,
  phone: 600,
  tablet: 720,
};

to
const sizes = {
    l: 992,
    m: 768,
    s: 576,
    xl: 1200,
    xs: 0,
};

or similar

I think this change is pretty aggressive as it has the potential to break the layout on the most client of this library 😨
I beleive
const sizes = {
    l: 992,
    m: 768,
    s: 576,
    xl: 1200,
    xs: 0,
};

it's the specs you get in Shopfront @endymion1818 ?
I think it's fair for Shopfront to have different breakpoints due to the intricacy of the layout in certain pages.
I think though all the other apps are sticking to this one?
const sizes = {
  desktop: 1280,
  phone: 600,
  tablet: 720,
};

https://github.dns.ad.zopa.com/zopaUK/shopfront/blob/master/src/components/tokens.ts#L35
Going forward we're gooing to be using these breakpoints, still quite different though.
https://www.zopa.com/borrowing-power
Without one of those extra breakpoints we couldn't have made the layout on tablet for this page.
I understand where you're coming from with Shopfront being a unique beast; but we are also mindful that we want to be as close to the react-components as possible, and uniform with the rest of Zopa.

what's the exact reasoning behind picking these breakpoints? When building our grid I mimicked bootstrap grid and there is some logic behind it https://github.com/twbs/bootstrap/issues/14894

@endymion1818 @thegrinder I'm gonna close this in the next few days as I don't see much activity related to it 😴
In case we think it's still relevant lets try to materialise it into formal API suggestions 👍

OK, happy to close this issue. I've recently got word of a 3rd design iteration, we can hopefully standardise our approach across all platforms then.


Setting system environment variables before meteor app is started.

Hello, I tried digging into your electrify code to see where I could include an additional script to set system environment variables before the meteor app is started.
My use case is that I want to create an electron app but point meteor to my hosted compose.io mongodb servers. I initially was going to set all my information in Meteor's settings.json... However settings.json is well known to not allow us to set the port for the mongo instance and other information.
If you would have any guidance on the chain of calls that happen up to and including the start of the meteor server I would love to do a PR for an enhancement to allow for other users to do what I'm aiming for!
Thanks,
Ethan

Quick update. It looks like I would modify main.js in .electrify/app and require a script at the top of the file that sets all of the system environment variables.

@ethanwillis main.js is an automated generated file, how did you achieve requiring script at top of it ???


Isle of Man Code IM Doesn't Work

Setting country to IM in configuration.yaml results in the check configuration button reporting invalid country data. IM is in the list of support countries.
Configuration invalid!
Invalid config for [binary_sensor.workday]: Country is not supported. for dictionary value @ data['country']. Got 'IM'. (See ?, line ?).
There is a note in GB section for Isle of Man to use IM.

Well, that's a bug. Thanks for reporting this!
I looked into this briefly and here is what I found:
The available country list is filtered by __base__ [undocumented Python?] attribute here https://github.com/dr-prodigy/python-holidays/blob/390f59c386b15485c78550a6b4c017b7a6e09f67/holidays/utils.py#L287
It works for usual cases (direct inheritance) and fails for more complex cases when country is derived from another HolidayBase based class.
Next step.
The list_supported_countries (and at least list_supported_financial) needs to be reworked to include all supported Alpha-2 country codes.
I'll file a fix for the issue later today.

Merged, thank you! 👍


Create ZoomHandler

Due to the way that the Highlight component handles the mouse events,
it is pretty much required that it is one of the last children of the XYPlot.
Since it renders a transparent rect over the entire XYPlot it currently disables
any mouse events for controls lower in the dom tree.
If the Highlight component is moved higher in the dom tree, then the onMouseLeave
event will fire when a lower component is hovered over.
The ZoomHandler delegates the handling of the mouse events to the XYPlot itself.
The XYPlot now holds a collection of Event objects that will be passed to the children,
where they can subscribe to the ones that they are interested in.
When the appropriate Event in the XYPlot is fired, it will execute the callbacks for all listeners.
This approach does not cause the XYPlot to re-render, and only the listeners that perform an
operation in their callback will be re-rendered.
Also created a useStateWithGet that wraps a useState call and also provides a memoized getState method.
Since the getState method is only created once for the component, it will not trigger re-renders when
listed in the dependencies of useEffect / useCallback. This drastically cuts down the number of
event handlers that are subscribed / unsubscribed.

Any ideas on a better name for ZoomHandler ?

I am not the greatest to find names, I think ZoomHandler is fine!

Converting this back to a draft as I want to change up the api a bit.
The zoom handler doesn't actually zoom anything... it just handles the selection
I'm going to change it to just handle the selection, and I'll make a separate component for the draggable window that Highlight has (although this may be in a separate PR)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Chris Thomas seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[BEAM-6859] align teardown with setup calls also for empty streaming …

…batches
This PR aligns teardown with setup calls. Currently, for empty batches in streaming for DoFns setup is called, but teardown isn't. [1]
This PR removes the call to setup. An alternative implementation could be to add
diff --git a/runners/spark/src/main/java/org/apache/beam/runners/spark/translation/SparkProcessContext.java b/runners/spark/src/main/java/org/apache/beam/runners/spark/translation/SparkProcessContext.java
index 830778fe95..97a4c288d9 100644
--- a/runners/spark/src/main/java/org/apache/beam/runners/spark/translation/SparkProcessContext.java
+++ b/runners/spark/src/main/java/org/apache/beam/runners/spark/translation/SparkProcessContext.java
@@ -58,6 +58,7 @@ class SparkProcessContext<FnInputT, FnOutputT, OutputT> {

     // skip if partition is empty.
     if (!partition.hasNext()) {
+      DoFnInvokers.invokerFor(doFn).invokeTeardown();
       return new ArrayList<>();
     }

This was implemented before, but the call to teardown was dropped and afterwards the call to setup was moved on some refactoring so that this issue was accidentally introduced.
[1] https://issues.apache.org/jira/browse/BEAM-6859

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @echauchot

Thanks for this fix @adude3141

Run Spark Validates Runner

Run Spark ValidatesRunner

Thx for your review,  @echauchot


Telemetry data missing since March

As detailed on the private thread

@adhiambovivian Can we please investigate this issue and make necessary fixes. Thank you

@RabebOthmani  confirm if the data is available. Thx


Plugins fix galore

Fix for all current plugins build problems. Also updates the plugins tutorial in docs.
Also, please see #242.

Thanks for that!


DXVA2

Hi all :)
I'm a little confused how the DXVA2 works!! I just need to run the Test Application inside WPFMediaKit solution or need I do some configuration to work whit DXVA2?
I am asking because when I play a video (4k) with WPFMediaKit application it is consuming more than 80% of CPU and just consume about 20% of GPU. I want to render the video with GPU not CPU and I can do that programmatically.
Anyone can help me please??

AFAIK you have to use EvrPresenter if you want to use DXVA2: compile the EvrPresenter from the source code and set the VideoRenderer property.

Yes.. I forgot this issue, but I had already found the solution!
So, I can leave here some steps to work with WPF-MediaKit:
1- Install, for example, K-Lite Codec Pack
2- Open "Lav Video" tool and change "Hardware Decoder to use" field to DXVA2
3- Open EvrPresenter solution and  compile it
4- Open WPF-MediaKit solution and replace the EvrPresenter.ddl on "Test Application" project to EvrPresenter.ddl generated in the previous step
5- In MainWindow.xaml add VideoRenderer="EnhancedVideoRenderer" in <controls:MediaUriElement tag: <controls:MediaUriElement x:Name="mediaUriElement" VideoRenderer="EnhancedVideoRenderer" Grid.Row="1" Margin="4"></controls:MediaUriElement>; .... Or you can simple change the default value in VideoRendererProperty property to VideoRendererType.EnhancedVideoRenderer
6- Compile and start the "Test Application"
You can use DXVA Checker to see if your graphic card support DXVA and if you are using DXVA to render the video!!

What happen if the video card has no DXVA and the EvrPrenter is used? Will be video still visible? I do not have a machine with such video card to test it. Thanks.

The video will work well, but it will not use the GPU to render the video!
You can test render a video with or without DXVA with the same graphic card. You just need to change the "Hardware Decoder to use" field to DXVA2 or NONE value on Lav Video Tool.
The results of my tests are:
Without DXVA

a 4K video used +-68.81% CPU and  +-26.78% GPU.

With DXVA

the same 4K video used +-4% CPU and  +-50% GPU

With VMR9 instead EVR:

the same 4k video used +-40% CPU and +-26% GPU

My purpose is only to use GPU to render the video and leave CPU free to do other things!

Thanks for the info. It's pity EVR without DXVA takes more CPU than VMR9. We distribute a public app and also want to use GPU if possible. But since DXVA is desabled by default and EVR takes more CPU then VMR9 without EVR, I think we keep using VMR9.

Yes, make sense!
I was searching how we can user DXVA automatically and I have 2 option:

When we install the K-Lite Codec pack, there is an option we can change to use DXVA for default, but if we forgot to change it on installation, we will not use DXVA.. Of course, we can change this option later, but if we have 100000 machines running a WPF application is a little bit complicated to do this!!

We have this project (https://github.com/Nevcairiel/LAVFilters) where we can try to change it to use DXVA and then we can create our own installer. After, when we will deploy our solution, it can install the LAV Filter Codecs automatically using DXVA.

If you have more option, please share with us :)

LAV DXVA should be configurable at runtime, e.g. see
http://forum.doom9.org/archive/index.php/t-156191-p-69.html search the code lavVideoSettings. I have not tried that yet. I am still a newbie in this Window video stuff so I will have to figure out if and how it's possible to plug this code into the WPF-MediaKit.

I am also a newbie with this stuff..
I found that the WPF can use MediaElement to render videos.
So, if we are using WPF, why we need WPF-MediaKit? We can use MediaElment directly on our project. It is easier and faster to implement!
There is any reason to use WPF-MediaKit instead of MediaElement?

MediaElement is very limited. With the WpfMediaKit you can control the video source at really low level.
Sent from my HAL 9000 terminal.
Excuse the typos and/or any trapped astronauts in the airlock
On Nov 13, 2016, at 11:45 AM, ASantos007 <notifications<EMAIL_ADDRESS>wrote:
I am also a newbie with this stuff..
I found that the WPF can use MediaElement to render videos.
So, if we are using WPF, why we need WPF-MediaKit? We can use MediaElment directly on our project. It is easier and faster to implement!
There is any reason to use WPF-MediaKit instead of MediaElement?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Sascha-L/WPF-MediaKit/issues/24#issuecomment-260200534, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGe0ENmGTTGs34l_cc2xufF7ZO7IYL4Wks5q90ybgaJpZM4Ki5oF.

@ASantos007 closing this issue, if you need something more, reopen it, please.


Migrate testing to github actions

For example, see https://github.com/ExecutableBookProject/sphinx-book-theme/blob/master/.github/workflows/tests.yml

done in #77


Fixed NuGet dependencies. Samples didn't work anymore

Hi @leonmeijer, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

I just released 2.0 and updated all the samples. Thanks!


Run goimports in CI, with a third section for local imports

What does this PR do?
Runs goimports to verify imports are correctly formatted, including putting local imports in a third section.
Motivation
We've long had a style guide suggesting putting local imports in a third section, but with no enforcement we (mostly me) have gotten this wrong in 600+ files.
Additional Notes

This may be a bit slow -- maybe too slow to run in inv test?
This will run in all of the unit-tests jobs.  Should it not do so, and instead run in a new goimports job so that it's clear when it fails what has gone wrong?
This may be annoying for people whose editors are not configured with the -local option.  Is it safe to assume that such annoyance will lead to updating those editor settings?

Possible Drawbacks / Trade-offs
This PR will ping EVERYONE.  It's automatic, so I don't think there's need for everyone to review the import changes, nor will I necessarily wait for everyone to approve.
Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

@ofek's advice was a complete rewrite, so I've force-pushed.  Same effect, though!

Hm, --fix appears to have only fixed some of the issues.  Some of the missed files have tags, so maybe it's tags-related?  But for example pkg/flare/archive_test.go does not have tags, yet --fix isn't reformatting it.  But goimports -w -local .. ./pkg/flare does fix it.  Ideas?

Hm, --fix appears to have only fixed some of the issues. Some of the missed files have tags, so maybe it's tags-related? But for example pkg/flare/archive_test.go does not have tags, yet --fix isn't reformatting it. But goimports -w -local .. ./pkg/flare does fix it. Ideas?

Build tags does seem to be part of the puzzle, but I don't understand either the archive_test.go case

I can't even see how --fix works from looking at the golangci_lint source.

Ah, an upgrade of golangci-lint fixed things.

..and then I realized I had a very old version installed -- the version already specified in internal/tools is fine, once I ran inv install-tools

Thanks -- I am looking at that right now.  If I can find a fix, I'll do it, otherwise I'll leave it to you.

It looks like the issue is that all blank lines are removed after the template is rendered, putting all of the imports in one section.  gofmt sorts them, but does not separate them into sections.  I'll leave the fix to you.

Hm, it also appears that golangci-lint only operates on some (random?) subset of files at once -- I keep getting new errors in CI.  I'll keep hacking away.

I think inv golangci-lint locally is missing submodules, so I ran
for dir in $(git ls-files pkg cmd | grep 'go\.mod' |grep /| grep -v github | sed 's!/go.mod!!'); do
  (cd $dir &&
  golangci-lint run --fix --timeout 10m0s --build-tags 'process jetson etcd apm cri otlp systemd clusterchecks netcgo gce ec2 containerd python zlib zk jmx consul kubeapiserver podman fargateprocess secrets docker kubelet orchestrator' ./...
)
done

It looks like golangci-lint is very particular about build flags.  It has missed +linux, even running on a linux host.
I'm going to try automating this with goimports itself, but we'll see if that's effective and/or fast.

It turns out that there's no efficient way to enforce this, so we're just going to not enforce it.  I've pushed commits which only

add docs recommending three sections and how to configure your editor to do so automatically
apply a one-time fix of all go source files