Mac OS Catalina installation error torch-scatter

📚 Installation

Installation of torch-scatter fails with AssertionError: Torch not compiled with CUDA enabled
Environment

OS: MacOS Catalina 10.15.1
Python version: 3.6.9
PyTorch version: 1.3
CUDA/cuDNN version: NA
GCC version: 11.0.0
How did you try to install PyTorch Geometric and its extensions (pip, source): Yes! Pip & Source
Any other relevant information:

Checklist

[x] I followed the installation guide.
[x] I cannot find my error message in the FAQ.
[ ] I set up CUDA correctly and can compile CUDA code via nvcc.
[X] I have cloned the repository and tried a manual installation from source.
[ ] I do have multiple CUDA versions on my machine.
[ ] I checked if the official extension example runs on my machine.
[ ] The official extension example runs on my machine.

Additional context
Although I am running on my macbook with no GPU, I have downloaded CUDA and added the cuda directories to the path variables.
`sudo ln -s /usr/local/cuda/lib /usr/local/cuda/lib64
export PATH=/usr/local/cuda/bin:$PATH
export DYLD_LIBRARY_PATH=/usr/local/cuda/lib:$DYLD_LIBRARY_PATH
export CPATH=/usr/local/cuda/include:$CPATH
`

Log

No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda'
running install
running bdist_egg
running egg_info
writing torch_scatter.egg-info/PKG-INFO
writing dependency_links to torch_scatter.egg-info/dependency_links.txt
writing top-level names to torch_scatter.egg-info/top_level.txt
reading manifest file 'torch_scatter.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'torch_scatter.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.7-x86_64/egg
running install_lib
running build_py
running build_ext
building 'torch_scatter.scatter_cuda' extension
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/Users/dimitricoukos/opt/anaconda3/envs/geo/include -arch x86_64 -I/Users/dimitricoukos/opt/anaconda3/envs/geo/include -arch x86_64 -I/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include -I/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -I/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/TH -I/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/THC -I/usr/local/cuda/include -I/Users/dimitricoukos/opt/anaconda3/envs/geo/include/python3.6m -c cuda/scatter.cpp -o build/temp.macosx-10.7-x86_64-3.6/cuda/scatter.o -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=scatter_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
cuda/scatter.cpp:18:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(src);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:19:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(index);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:20:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(out);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:26:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(src);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:27:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(index);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:28:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(out);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:34:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(src);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:35:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(index);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:36:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(out);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:37:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(arg);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:43:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(src);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:44:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(index);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:45:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(out);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
cuda/scatter.cpp:46:3: warning: 'type' is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a
      drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use
      tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
  CHECK_CUDA(arg);
  ^
cuda/scatter.cpp:3:36: note: expanded from macro 'CHECK_CUDA'
#define CHECK_CUDA(x) AT_ASSERTM(x.type().is_cuda(), #x " must be CUDA tensor")
                                   ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/ATen/core/TensorBody.h:241:3: note: 'type' has been explicitly marked
      deprecated here
  C10_DEPRECATED_MESSAGE("Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement...
  ^
/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/include/c10/util/Deprecated.h:28:44: note: expanded from macro
      'C10_DEPRECATED_MESSAGE'
# define C10_DEPRECATED_MESSAGE(message) [[deprecated(message)]]
                                           ^
14 warnings generated.
Traceback (most recent call last):
  File "setup.py", line 59, in
    packages=find_packages(),
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/setuptools/__init__.py", line 145, in setup
    return distutils.core.setup(**attrs)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/dist.py", line 955, in run_commands
    self.run_command(cmd)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/setuptools/command/install.py", line 67, in run
    self.do_egg_install()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/setuptools/command/install.py", line 109, in do_egg_install
    self.run_command('bdist_egg')
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 172, in run
    cmd = self.call_command('install_lib', warn_dir=0)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 158, in call_command
    self.run_command(cmdname)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/setuptools/command/install_lib.py", line 11, in run
    self.build()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/command/install_lib.py", line 107, in build
    self.run_command('build_ext')
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/dist.py", line 974, in run_command
    cmd_obj.run()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 84, in run
    _build_ext.run(self)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/command/build_ext.py", line 339, in run
    self.build_extensions()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 372, in build_extensions
    build_ext.build_extensions(self)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/command/build_ext.py", line 448, in build_extensions
    self._build_extensions_serial()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/command/build_ext.py", line 473, in _build_extensions_serial
    self.build_extension(ext)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 205, in build_extension
    _build_ext.build_extension(self, ext)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/command/build_ext.py", line 533, in build_extension
    depends=ext.depends)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/distutils/ccompiler.py", line 574, in compile
    self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 288, in unix_wrap_compile
    "'-fPIC'"] + cflags + _get_cuda_arch_flags(cflags)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1021, in _get_cuda_arch_flags
    capability = torch.cuda.get_device_capability()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/cuda/__init__.py", line 320, in get_device_capability
    prop = get_device_properties(device)
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/cuda/__init__.py", line 325, in get_device_properties
    _lazy_init()  # will define _get_device_properties and _CudaDeviceProperties
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/cuda/__init__.py", line 196, in _lazy_init
    _check_driver()
  File "/Users/dimitricoukos/opt/anaconda3/envs/geo/lib/python3.6/site-packages/torch/cuda/__init__.py", line 94, in _check_driver
    raise AssertionError("Torch not compiled with CUDA enabled")

torch-scatter believes you have CUDA installed since it finds the respective cuda directories, but since you have no GPU the installation fails. Try running python setup.py install --cpu to fix this :)

Thank you!!!


cmd/compile: compute builtin import data directly from source files

builtin.go contains the export data for the built-in and unsafe package. It is created by running mkbuiltin.go which runs a special compilation over the sources in the builtin directory and then extracts the export data.
A change to the export data format requires a careful multi-step process to update the data in builtin.go; see issue #15835.
Investigate generation of the builtin and unsafe package export data directly from the source files (they are small). This would eliminate the need for builtin.go and mkbuiltin.go and corresponding tests and make it much easier to play with export format changes.

Bumping priority here. Not sure if @griesemer or @mdempsky is the one working on it.

This is now a duplicate of #17508 which has been fixed.

https://go-review.googlesource.com/c/31433/ removed the need to handle the unsafe package via builtin.go.
https://go-review.googlesource.com/c/31493/ generates builtin.go directly from the source and uses the go/* libs to do so.


Video player support

Would really like this for WebChat.

Also, there may be Audio player support.

It is useful to include this, but give it some careful thought.  As a user, I do not want video notifications or live tiles appearing on my PC or Phone.  Consider implementation rules for auto-play, volumes etc

From Action Center developer platform side (uses UWP renderer)...

Missing renderer requirement that downloading the resource must go through the ResourceResolver, so that we can download the resource ourselves through our own caching code
We would need the OnMediaStarted and OnMediaEnded event to know to keep the toast on screen while the user is watching it, and then 5 secs after the media ends, dismiss the toast (unless more user interaction is occurring)

We would need someone from the UX side to chime in on this, but I'd imagine we initially would disable the inline playback.
For hosts that don't support hit targets and interactivity (like Timeline), they would need a way to configure it so that it just displays the thumbnail (without any play button), since it's only the entire card that is clickable, rather than specific content on the card that's clickable. Seems like that might already be possible with what's described here but writing that down just to make sure.

The spec lacks size handling guidance for video. I think it should work like this:

Width is always 100% of the parent container's
Height is dynamically computed by the media player so as to respect the video's aspect ration

What's more problematic IMO though (and I'm talking about the HTML implementation but it would probably apply to all platforms) is that each browser has its own controls implementation; they all look very different and they can't be styled. They will look quite bad inside a card, especially the audio player which can't even be sized.
Therefore I believe we should own the controls, but that's a significantly higher investment unless we keep it simple, e.g. play/pause, maybe mute, but no seek nor volume sliders.

Doing the play overlay button as an image in HostConfig is actually not that great a solution. Allowing the styling of the button to be done in CSS is a much better option and satisfies the customization needs. Besides, the design, at least for the HTML media player, calls for more than just the play button to be done as an overlay, and therefore additional properties would have to be added to HostConfig to handle the other button(s).
I suggest we either:
Change the design and remove the property from HostConfig, and let hosts customize buttons via other means
Or make honoring the HostConfig property optional if the host has a better way to handle customization.

I'm just discovering that since we last discussed and agreed on the spec, new requirements have been added, namely OnMediaClicked, OnMediaStarting, OnMediaPaused, OnMediaStopped (what's the difference between puase and stop?) and maxMediaSize.
These were never reviewed. What gives?

The original spec was ambiguous and missing elements. For example, it didn't distinguish whether OnMediaStopped included paused (which would be needed by hosts), and it was completely missing scenario requirements.
In fact, we still don't have full scenario requirements. I'm trying to talk to hosts today to determine the actual scenario requirements so that we can be sure we have the correct set of events (hosts might even need to be able to dynamically pause the video, for example)

There was no ambiguity: these events were not part of the original spec, and we never reviewed them. Plus, these events don't need to be spec'ed here because they have nothing to do with the Adaptive Card format, they are features of the renderer that can technically be exposed in different ways depending on the platform.
The spec above says "potentially, hosts need to be able to..." which doesn't seem like a strong requirement nor that there is a concrete scenario that needs the feature.

As a matter of fact, you added all these to the spec 2 days ago @andrewleader.

Yes there was ambiguity, that is an absolute fact witnessed by the devs who were attempting to develop this and had questions, since it was ambiguous (for example, the spec said that first frame of video is displayed unless author provides a poster, but the spec also said that the poster is displayed (or host default poster is displayed), so it's ambiguous what's supposed to be displayed.
The "Potentially" one is an incomplete requirement, that's why it says potentially. We're trying to gather scenario requirements from hosts to determine whether those are needed.

My opinion, as I shared here is that there is no need to allow for Play button customization in HostConfig. This is going too far for very little value add. I think every host should simply be responsible for choosing their own defaults, including size etc.
Besides, the desired UI (for the HTML renderer at least) is this one:

So it would be one thing to allow for the Play button customization, but what about the Rewind button?
I think we need to change the spec. We can always add support for button customization later if we actually realize it's necessary, but it really doesn't strike me as necessary (nor practical) at the moment.

The play button customization is only for the initial play button... Once clicked, the actual play/pause/rewind/volume controls appear (which cannot be customized).
You can certainly imagine that Teams would want a purple-themed initial play button, etc. I'll check with some of the hosts to see if they actually require this functionality though, I'm not sure if they explicitly asked Matt for that functionality.

The design for HTML calls for the same button to be used. The big play button changes into a big Pause button when clicked, then back to Play when clicked again. When the video is playing, the button automatically disappears if the mouse cursor moves outside the boundaries of the video or stays idle for a moment. It appears again as the mouse moves over the video.
I think it should be possible for a renderer, be it the HTML one or anything other, to achieve the above design without being tied to using two different buttons. Said another way, I don't think there should be a requirement as to the UI of the video player for as long as it exposes the functional features described in this spec.

The functional features in the spec require a initial play button to be displayed along with the poster, and when clicked, the poster disappears, video starts playing, and full media controls appear. If you disagree with the spec, then we have to have a conversation about that.

Here's an example of why the initial play button and the media-loaded play button need to be different... in bots:

Bots use media controls at the bottom, with a time scrub bar. But they want a large initial play button.
Facebook Messenger does the same...

In your case, where there's no media bar at the bottom, it certainly would make sense to re-use the same icon, but that's not the only case.

So just to be clear - Bot clients that use the HTML renderer (WebChat for instance) will not get the experience you are showing above; they will get the experience I outlined and provided a screenshot of. In other words:

No tracking bar,
No volume control
No countdown
No full screen control

Just the two big play and pause buttons.
That is, as I mentioned before, unless:

Your team is willing to lend a hand and do the work
Or we rely on the default control layout provided by each browser's media player implementation, which is often ugly and isn't stylable

I do understand it's not the only case, but I am also saying that handling the richer case (like in the shots you included above) still doesn't require Play button customization in HostConfig, even if the buttons are different. The only value add of having it in HostConfig (with the complexities it leads to) is to, say, have the button as pictured in the bottom card of your first screen shot used in your second screenshot. It is not the case in your screenshot and the value add of supporting that is very, very low IMO.

Thanks, we'll have to check with WebChat if that's acceptable then. I'll start a mail.

Requirements from WebChat:

Full-screen: required, will probably get user asks if we don't have it.

Volume control: probably we will only need mute feature, but not fine-grained volume control.

Seek bar: need discussion. It depends on the video length. IMO, minimum bar is last 10s + next 30s. People expect a way to seek with full screen video.

BTW, we will need to support some forms of transcript for accessibility.

Can't believe we missed closed captions/accessibility! D'oh!

Thanks @andrewleader. Now we need to have a conversation around it and decide together which of these requirements we decide to actually make part of the spec.
To be upfront, though, if we decide that any of these is indeed required, then the HTML implementation will simply use the built-in player on all platforms, enabling every feature that can possibly be enabled. The implementation will be super cheap, but there will be no way to re-style the controls.
However, even if HTML uses the built-in player, I still believe we should reconsider the spec for the Play button and even the Poster. Here is what I suggest and why:

Built-in players on most platforms handle the "initial state" (thumbnail + play button) automatically. It is disputable that the experience we'd provide with Poster + HostConfig-configured default Play button would be any better, and the spec doesn't explain why we want to do it that way in the first place. Here is the default state in Chrome, for instance (from https://www.w3schools.com/html/html5_video.asp) (note BTW that I believe the controls in Chrome were just recently redesigned, they didn't use to look that good AFAICR):

Media player controls have events to indicate when the player couldn't load, allowing us to fall back to a degraded experience. I believe that's when the default poster should be used

In that degraded experience, at least in HTML, the default Play button is undesirable, because we already know the video can't be played and the best fallback experience we can implement would be to open it in another browser tab, which would use the same built-in player...

On the caption front, this is how it's done in HTML:
<video width="320" height="240" controls>
  <source src="forrest_gump.mp4" type="video/mp4">
  <source src="forrest_gump.ogg" type="video/ogg">
  <track src="subtitles_en.vtt" kind="subtitles" srclang="en" label="English">
  <track src="subtitles_no.vtt" kind="subtitles" srclang="no" label="Norwegian">
</video>

It is likely we will have to add another property to the Media element to support text tracks, although I do not know how other platforms do it.
While I am at it, I think we should also re-consider displaying the poster for Audio. Why can't card authors do a poster if they want to using an Image, and why is there a need for a default poster for an Audio stream?
So let's please spend some time soon and re-discuss this spec.

Reasons for the "initial state" (thumbnail + play button)

A default "thumbnail" provided by a video is never great. Anyone who's published videos on YouTube knows that - that's why thankfully they added the ability to provide custom thumbnails.
By being given a thumbnail image, we don't have to download the video, saving unnecessary downloads. Otherwise, the media control would have to download the first 5-10 seconds of the video (the first frame of the video can often be blank, so first frame isn't an option). Users aren't always going to play the video, so downloading it can be unnecessary - we only want to download when it's actually requested by the user.

Why can't card authors do a poster if they want to using an Image

They can? Isn't that what we wrote in the spec?

why is there a need for a default poster for an Audio stream?

The default poster is currently shared between video and audio... definitely might make sense to have those separated, so that a host could have none or a different default poster for audio.

I'll schedule a meeting with everyone soon!

Many (most?) video files have an embedded cover image; retrieving it is hardly more expensive than downloading an image separately, and happens very fast.
I think we need to be realistic when it comes to the developer experience - do we really want card authors to generate custom, separate poster images for all the videos they put in their cards, even though the video itself likely already has an embedded cover picture? Do we expect that the Media element will be most used to display videos owned by the card author or videos owned by a third party? If the latter, do we really think it's a realistic/acceptable workfow for card authors to go extract poster from a video they don't own, and store it separately on their side?
You mention YouTube - our solution will not handle YouTube videos, since AFAIK one can only embed a YouTube player for that. Are we sure we do not want to support YouTube videos?
I meant Image with a capital I, as in an Adaptive Image element.

More thoughts. Say we do require the poster as per the spec:

The Media element will stretch to the entire width of it parent container, in most cases the card itself
The aspect ratio of the video is a piece of information embedded in the video stream
The  player in HTML (and most likely on every other platform) will adjust its height so as to respect the video’s aspect ratio

So we have a choice to make here:

We let the player pick its own optimal height in order to respect the video’s aspect ratio

In that case, what are the dimensions we recommend for the poster?
If the dimensions of the poster do not match the video’s aspect ration, the player’s height will change as the video starts playing, creating a jarring effect

We force a specific aspect ratio for the player itself, essentially we compute its height as a multiple of its width. Then we document that ratio as the one card authors should use for their poster. There are several drawbacks:

A widescreen video will likely always have horizontal black bars in the embedded player
A 3:2 video will appear smaller than it could with vertical black bars left and right
There is still no guarantee that the card author will have respected the documented recommended aspect ratio, so there is no guarantee the poster itself will fit well within the space reserved in the card, leading to either:

Black bars
Or the posted being truncated which could cut off the text it contains

We force the player into the poster's aspect ratio

Essentially we are in the same situation as the previous bullet, it's just that the size of the player has been determined differently (but still not based on the actual video's aspect ratio)

Good thoughts on the aspect ratio... Expanding on those some and giving them labels

Option A: Display poster and video each in their own aspect ratio

Means height might change when user first plays the video

Option B: Use the video's aspect ratio

Means we first have to pre-load some of the video (metadata) to obtain the aspect ratio (can be 44 MB as tested in HTML with Edge)
Not an option for some hosts due to size of download

Option C: Use the poster's aspect ratio

Means if the video is a different aspect, the video will have black bars

Option D: We always use a fixed aspect ratio, like 16:9

Means no matter what, some authors will always have black bars on their videos
Not a good option since lots of videos will suffer with no way of author fixing it

Seems like the best option is Option A. We would tell authors that they should use the same aspect ratio on the poster as the video, but worst case (should be uncommon), the height changes when it starts playing... but at least there's never any black bars.
The second best option seems like Option C. But I think the height changing would be preferred over black bars.
If we were allowed to pre-download some of the video, Option B would seem ideal. But even if we did that, the poster would get downloaded first, and then the video size info would come in later... so we still would have to make a decision on how to size the content before the video gets loaded (and we need to make a decision on how to size the content before the poster gets loaded too...).
Basically, there's three stages there...

Nothing loaded yet - Use default 16:9 aspect ratio while requesting poster and video?
Poster loaded - Now use poster aspect ratio?
Video loaded - Now use video aspect ratio?

So the size could change twice within 2 seconds... that could be wonky. Then again, authors can fix this by just providing the correct aspect ratio.
So I say Option A is the best... it should be a minority that authors don't provide the correct aspect ratio, and even if they don't, a small jump in height won't be the end of the world.

Looking at Edge and Chrome's default  behavior, they both do A, e.g. they start with some specific height and then update it when they have loaded enough data to know what the video's aspect ratio is. So I agree A seems to be the best option here.
Given that it is also true we want to minimize to amount of data loaded (e.g. not load the video until the user decides to play it) and that my assumption that most videos have an embedded thumbnail image is apparently false (and even if it were true, browsers apparently all fetch the full video immediately as the page is loaded), I do agree that the poster is required.
I am still not sold on the HostConfig-configurable Play button though, but we can discuss that at the meeting Andrew will setup.

Documentation is done and in the mahiding/site1.1 branch.

cc: @compulim

Completed for the 1.1 release

this version of adaptive card( playing video) is supported in which which channel? can i use it in webchat?

Hey @amity5020, please ask that question on the Bot Framework WebChat issues. I believe the latest version of WebChat is running Adaptive 1.1, but they would know!

Hi @dclaux , @matthidinger! I have a question about Adaptive Cards 1.1 in Microsoft Teams. Recently when I tried to post a card in 1.1 version Teams did not display it, instead showing the "fallbacktext". I wanted to display media.
How to upgrade Teams to use 1.1 SDK?

Hey @tposzytek, Teams hasn't updated to 1.1 yet as far as I'm aware. There's nothing you can do, as the Teams app itself needs to update to the newest version of Adaptive Cards. We've shared your feedback with them.
However, what you can do is **leave the "version" property set to "1.0". It's actually a minVersion property, where you're specifying the minimum version you require to be rendered. So, if you want your card to still be rendered (and any new 1.1 features will be ignored, simply leave it as "version": "1.0"! Does that work for you?

Hi! Thanks for the answer. Unfortunately when using version 1.0 the Media card is absolutely not being displayed. So this doesn’t work for me since I wanted to use that particular feature 😊
From: Andrew Leader<EMAIL_ADDRESS>Sent: poniedziałek, 27 maja 2019 18:42
To: microsoft/AdaptiveCards<EMAIL_ADDRESS>Cc: Tomasz Poszytek<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/AdaptiveCards] Media player support (#196)
Hey @tposzytekhttps://github.com/tposzytek, Teams hasn't updated to 1.1 yet as far as I'm aware. There's nothing you can do, as the Teams app itself needs to update to the newest version of Adaptive Cards. We've shared your feedback with them.
However, what you can do is **leave the "version" property set to "1.0". It's actually a minVersion property, where you're specifying the minimum version you require to be rendered. So, if you want your card to still be rendered (and any new 1.1 features will be ignored, simply leave it as "version": "1.0"! Does that work for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/AdaptiveCards/issues/196?email_source=notifications&email_token=AMCPVG2ZPTAT7A7R2GRBPIDPXQFOTA5CNFSM4DGJOMK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKGCXY#issuecomment-496263519, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMCPVG5QNWKLAMSBK626T5TPXQFOTANCNFSM4DGJOMKQ.


Bug: @lexical/link TOGGLE_LINK_COMMAND not working

Lexical version: "@lexical/link": "^0.12.2",
I tried creating a link from this command. I added a button, and on clicking it, i can't seem to add the hyperlink on the editor.

Link to code example:
Here's the code:
const [isLink, setIsLink] = useState<boolean>(false)
<span
            role="button"
            onClick={() => {
              setIsLink((prev) => !prev)
              editor.dispatchCommand(TOGGLE_LINK_COMMAND, {
                url: 'https://www.google.com/',
              })
            }}
            className={`${
              isLink ? 'bg-slate-300' : ''
            } hover:bg-slate-500 hover:cursor-pointer w-6 h-6 flex justify-center items-center`}
          >
            A
          </span>

The current behavior
The link is not created

The expected behavior
Link should be created

Did you add LinkNode to your nodes in the EditorConfig?
If so, please provide a code sandbox so I can repro.

I have the LinkNode added to my project, with the dispatch command as above and this works for me, in the latest version. I think this issue can be closed.


HTTP Error 403 Forbidden

bundle_info = abd.default18_bd() always end up with NETWORK error such as 403 fobiden or conection closed by the server
Is there some way I can download basic files required for most simple AFQ tutorial, thus i can finish using GroupAFQ to get all tracts ?

Cell In[15], line 1
----> 1 bundle_info = abd.default18_bd()
File e:\codall\envs\DIPY\Lib\site-packages\AFQ\api\bundle_dict.py:62, in default18_bd()
[61](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/api/bundle_dict.py:61) def default18_bd():
---> [62](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/api/bundle_dict.py:62)     templates = afd.read_templates(as_img=False)
[63](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/api/bundle_dict.py:63)     templates['ARC_roi1_L'] = templates['SLF_roi1_L']
[64](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/api/bundle_dict.py:64)     templates['ARC_roi1_R'] = templates['SLF_roi1_R']
File e:\codall\envs\DIPY\Lib\site-packages\AFQ\data\fetch.py:729, in read_templates(as_img, resample_to)
[726](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:726) logger.debug('loading AFQ templates')
[727](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:727) tic = time.perf_counter()
--> [729](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:729) template_dict = _fetcher_to_template(
[730](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:730)     fetch_templates,
[731](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:731)     as_img=as_img,
[732](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:732)     resample_to=resample_to)
[734](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:734) toc = time.perf_counter()
[735](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:735) logger.debug(f'AFQ templates loaded in {toc - tic:0.4f} seconds')
File e:\codall\envs\DIPY\Lib\site-packages\AFQ\data\fetch.py:93, in _fetcher_to_template(fetcher, as_img, resample_to)
[91](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:91) if isinstance(resample_to, str):
[92](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:92)     resample_to = nib.load(resample_to)
---> [93](file:///E:/codall/envs/DIPY/Lib/site-packages/AFQ/data/fetch.py:93) files, folder = fetcher()
...
File e:\codall\envs\DIPY\Lib\urllib\request.py:643, in HTTPDefaultErrorHandler.http_error_default(self, req, fp, code, msg, hdrs)
[642](file:///E:/codall/envs/DIPY/Lib/urllib/request.py:642) def http_error_default(self, req, fp, code, msg, hdrs):
--> [643](file:///E:/codall/envs/DIPY/Lib/urllib/request.py:643)     raise HTTPError(req.full_url, code, msg, hdrs, fp)
HTTPError: HTTP Error 403: Forbidden

The templates are also available here:
https://figshare.com/articles/dataset/Templates_for_Automated_Fiber_Quantification_from_Diffusion_MRI_data/3381517
https://figshare.com/articles/dataset/Tract_probability_maps_for_automated_fiber_quantification/6270434
https://figshare.com/articles/dataset/Templates_for_Automated_Fiber_Quantification_of_corpus_callosum_from_Diffusion_MRI_data/3381523
If you put the templates and probability maps in a folder ~/AFQ_data/templates and the callosum templates in a folder ~/AFQ_data/callosum_templates the software should be able to find them.


Implement Bounded Iterator

Waiting on Bound to be merged with rust-lang/rust#20082.
§ describing bounded iterators in the RFC
fn range(&self, min: Bound<u32>, max: Bound<u32>) -> RangedItems<'a, u32>;

See https://doc.rust-lang.org/stable/std/collections/struct.BTreeSet.html#method.range for new API.


[BUG] Getting crash while parsing url on release builds (with minifyEnabled = true).

Was unable to pull logs due to it being minified release build.

Hello @jasperx21
Thank you for reporting the bug
Can you please provide the link(s) which were leading to a crash on parsing?
Thanks

all links were crashing for me, try anything.
This was the exception: https://stackoverflow.com/questions/40703857/android-jsoup-exceptionininitializererror

Okay, I will test this out and review your PR too.
Thank you

@jasperx21 Can you also please link this issue to the PR you created.

I don't see any option to link these. Can you try?

[Closed] See #18


sql in

// SQL:
// select * from db where id in ( 1, 2, 3 )
// JS:
db.run( 'select * from db where id in ( ? )', [ [ 1, 2, 3 ] ] )
// 'select * from db where id in ( null )'

Closing as dupe of https://github.com/TryGhost/node-sqlite3/issues/762


Update Flatbuffers toolchain

This task is automatically imported from the old Task Issue Board and it was originally created by Wojciech Daniło.
Original issue is here.

Description
The Old Flatbufferes version has several problems and is hard to be installed on some systems.
Resources
Flatbuffers has released 2.0.0 which overhauls rust support and fixes numerous bugs.
Tasks:

[ ] Upgrade both the engine and IDE to be compatible with the new flatc version.
[ ] Split up the flatbuffers schemas into multiple organised files.

Whatever version is picked please let's avoid using another package manager (like congo?) and simply fetch binaries directly from GH for the specific platform.

Whatever version is picked please let's avoid using another package manager (like congo?) and simply fetch binaries directly from GH for the specific platform.

Yes, absolutely. conda was used only because for older releases flatbuffers was only providing Windows binary.


[Task] <When importing and exporting monitoring, support export collectors, configure collectors when importing>

Description
当前v1.4.0版本，导出监控没有采集器信息，导入后使用默认采集器，应该在导入时支持配置
Task List
-[ ]导出监控采集器信息
-[ ]在导入时支持配置采集器

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Description
In the current version v1.4.0, there is no collector information for export monitoring, and the default collector is used after importing, which should support configuration when importing
Task List
-[ ]Export monitoring collector information
-[ ]Support configuration collectors during import

确实有问题，你这边修复一下？

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

There is indeed a problem, can you fix it here?

确实有问题，你这边修复一下？

ok，我有空看看

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

There is indeed a problem, can you fix it here?

ok, I have time to take a look


Bakgrunnur

This tweak shows a dot in apps working in the background. When I install Dock Indicators, this dot disappears.
Hope you can fix this.

Dock Indicators hides the labels so I assume its part of the label.


APP-15961 - Remove references to collection

Need to regenerate gql after rule-service PR is merged


Add the option of disabling the default converters

This allows completely modifying the converter chain, making it possible to also work with / replace the default converters.
This allows code like
var toMarkdown = require('to-markdown');
var converters = require('to-markdown/lib/md-converters').slice(0, -1); // disable "everything"-converter
converters.push({
  filter: function() { return true; },
  replacement: function(content) { return content; }
}); // doesn't return tag anymore

toMarkdown("<unknown>HTML</unknown>", { noDefaultConverters: true, converters: converters });

Thanks for your contribution.
The converters option prepends any converters to the default converters, so there’s no need to disable the "everything" converter since it will be overridden by the one you pass in. Your example is equivalent to:
var converters = [{
  filter: function() { return true; },
  replacement: function(content) { return content; }
}];

toMarkdown('<unknown>HTML</unknown>', { converters: converters })

However, it is not very clear that the converters option extends rather than overrides.
Perhaps it should override? That way you’d be able to disable all converters by passing in converters: []. If the default converters were (officially) publicly exposed, extending would be possible by doing something like:
var myConverters = […]

toMarkdown('…', {
  converters: myConverters.concat(toMarkdown.defaultConverters)
})

What do you reckon?

I think the expected behaviour would be for it to overwrite and have some way to use the default converters, however I wanted to avoid breaking backwards-compat.
However, you're right, since one can just append a catch-all converter at the end of custom converters, it would never reach the default converters, so this is not even necessary. So I guess all good?

Yep, cool.
I’ll add another issue regarding the clarity of the converters option.
Thanks again!


Image's platform does not match for Raspberry Pi 4

Greetings, I am trying to use DDNS in a docker container for namesilo using the docker run command provided in the github. My issue is that it seems like arm64/v8 isn't supported and there are only amd64 builds available. I am running a Raspberry Pi 4 via dietpi/raspbian. Any chance to add additional support for this?
`root@DietPi:~/docker# docker run -d --name ddns -v /docker/namesilo/:/home/NameSilo-DDNS:rw charles94jp/ddns
--restart=always
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
e815e9a71dfd8c7cc7ed752086f299e90a854c726b9321e2a1938061e4a60c5d`
Thank you

I rebuilt the image and pushed it to docker hub.

https://hub.docker.com/r/charles94jp/ddns/tags

Please try again. Delete the old image first and then pull the new one.
If it still doesn't work, you can clone the repository and build the docker image manually

Thank you, I was able to get my docker run command to load. But I am unable to find any configuration or any other files in my /docker/namesilo/ folder. Could you please tell me how to generate this in a container? My command that I ran is same as above but I will paste below
docker run -d --name ddns -v /docker/namesilo/:/home/NameSilo-DDNS:rw charles94jp/ddns

How do I know if the updates have successfully been pushed to Namesilo? I don't see any logs in Portainer's view of DDNS' logs
I have 2 DNS records created in namesilo already.

Hostname blank, Type A, IP is my home IP (already entered before doing this app)
Hostname jellyfin, Type A, IP is my home IP (already entered before doing this app)

My conf.json looks like this:
{
    "domains": [
        "jellyfin.mydomain.com", "mydomain.com"
    ],
    "key": "my api key",
    "frequency": 600,
    "mail_host": "",
    "mail_port": "",
    "mail_user": "",
    "mail_pass": "",
    "receivers": [""],
    "email_after_reboot": false,
    "auto_restart": true,
    "email_every_update": false

Updates can be viewed through the log.
In the case of docker, because -v /docker/namesilo/:/home/NameSilo-DDNS:rw was used during docker run
You can run /docker/namesilo/ddns-docker to view the logs, or just view the file /docker/namesilo/log/DDNS.log


Bug: Rule "no-unused-variables" does not recognize variables used in scenario name, step tables, or step strings

Rule "no-unused-variables" does not recognize when variables are used in:

scenario names
step tables
step strings

Examples:
Feature: Rule "no-unused-variables" bugs

  Scenario Outline: Examples variable <variable> is in the scenario name
    Given this
    When I do that
    Then something should happen
    Examples:
      | variable |
      | foo      |
      | bar      |

  Scenario Outline: Examples variable is in a step table
    Given this:
      | <variable> |
    When I do that
    Then something should happen
    Examples:
      | variable |
      | foo      |
      | bar      |

  Scenario Outline: Examples variable is in a step string
    Given this
    When I do that
    Then this should display:
      """
        <variable>
      """
    Examples:
      | variable |
      | foo      |
      | bar      |

Result:
node ./node_modules/gherkin-lint ./features/testRule.feature -c ./.gherkin-lintrc
.../cucumber/features/testRule.feature
  8     Examples table variable "variable" is not used in any step    no-unused-variables
  18    Examples table variable "variable" is not used in any step    no-unused-variables
  30    Examples table variable "variable" is not used in any step    no-unused-variables

For Scenario Outline: Examples variable <variable> is in the scenario name, I'm not sure if this is best practice.  My team seems to have gotten creative with naming conventions and this actually makes the report more clear with dynamic naming.  I'll leave it up to the community to decide if this should be supported.
The other two examples seems clear cut bugs to me.

Thanks for the bug report!
I wasn't aware that you can use step arguments, or variables in scenario names. Since Gherkin/cucumber support both of those operations, the linter should support it too.
I put up a fix in #128 (I used your examples in the unit tests so tyvm for those!)

Fix published with v2.13.2


Create apt-get package

Is there a reason I can't currently install this lib with apt-get?

We don't plan to support distribution of the compiler as a Linux package. Someone else would have to do it.


chore(main): release 1.15.2

:robot: I have created a release beep boop
1.15.2 (2023-09-15)
Bug Fixes

add gap between events (3252979)
blank screen after requesting verification mail (c17f4c9)
blank screen after verifying email (06f66b2)
do not require login to verify email (cffaeda)

Miscellaneous Chores

Update Flyer (0f031ed)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rotex1800/registration/releases/tag/v1.15.2 :sunflower:


D2 file not generating

In command line, we use dictim -a -t temp.edn -w in.d2 -o out.d2 to generate the out.d2 file. But when we remove -w i.e. without the d2 file is not generating.
Following command does not produce the out.d2 file
dictim -a -t temp.edn in.d2 -o out.d2

There was a bug in the non-watch apply template code path, so the -t option wasn't being picked up. Fixed in v0.8.7
Also, your usage is wrong. Should be:
dictim -a < in.d2 -t temp.edn

(to be consistent with other non-watch variants of commands like compile, parse..)
This will dump output to the terminal, so to put it in a file, add  > out.d2 on the end, e.g.
dictim -a < in.d2 -t temp.edn > out.d2

Thanks, will try it out in latest release. That was quick.


Support POST and PUT methods for vROps payloads.

NOTE: This change impacts the routes of multiple shims -- user changes
may be required after updating.
vROps uses POST for creates and updates to alerts while using PUT for
cancelling. Added support for both methods. In order to support this,
some routes now required an <ALERTID> to specify certain options such as
<NUMRESULTS>. In the case of bugzilla, a separate endpoint needed to be
added.

OK, instead of supporting a second bugzilla endpoint, both were merged forcing that a TOKEN be specified. Now, a - can be used to skip the TOKEN in favor of basic auth.

All tests included and passing -- merging


ADD filters  type is value ,Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object with keys {s%2C e%2C c}&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Bug description

How to reproduce the bug

Go Dashboards
add type is value filter , save!
click filter

Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[x] I have searched Superset docs and Slack and didn't find a solution to my problem.
[x] I have searched the GitHub issue tracker and didn't find a similar bug report.
[x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Is this a customized version of Superset? Or could you give us an example filter (using example datasets) that causes this? I/we haven't seen this... and it seems like everyone would be running into it.

Did you manage to solve your problem?
I'm encountering the same issue as this
Thank you!


"having field = value" in select statement can't work correctly

if I have the sql like:  select name, count(1) as num from table group by name having num = 5
the "num = 5" can not  work correctly because of this use 【==】comparison operation on two Double type values, the code is in the following file:
sql4es/src/main/java/nl/anchormen/sql4es/model/expression/SimpleComparison.java

if(this.comparisonType == Type.EQUAL) return leftValue == rightValue;
if(this.comparisonType == Type.GREATER_THAN) return leftValue > rightValue;
if(this.comparisonType == Type.GREATER_THAN_OR_EQUAL) return leftValue >= rightValue;
if(this.comparisonType == Type.LESS_THAN) return leftValue < rightValue;
if(this.comparisonType == Type.LESS_THAN_OR_EQUAL) return leftValue <= rightValue;

if this can use: return leftValue.equals(rightValue); ?

You are right that this poses a problem and I think your fix is suffice. I will see if I can update it soon.
ps would be better to implement the HAVING as a pipeline aggregation and let ES handle it but that would be future work.

I have added the proposed fix which is released in version <IP_ADDRESS>. Please test if this version works for you as it should


DATETIME PICKER lags on some device

Hello,
tried to use the DATETIME PICKER on one of the page ..
The typing inside the teatarea lags by 4-5 secs, and inline picker rendering is fatal.
Phone ASUS-5
Please assist me for the same.

How the textarea related to picker? As for Android, don't use rotate effect to improve performance, Android is just slow

Closing as no further response/discussion


Does not work in exclusive full screen mode at 1920x1080.

Does not work in exclusive full screen mode at 1920x1080, black screen for the loaded game. Its fine in windowed or borderless windowed. Can only hear audio, switching to windowed restores the game video screen.

Does this happens for all the games? I couldn't reproduce this for some reason. What's in your interp-mod.ini?

It was happening on all games, I have a 120 hz monitor but exclusive fullscreen runs at 60hz. Running a 980ti nvidia. It's working now....strange. I had fast vsync on and ultra frame latency enabled.  Attaching my interp-mod.ini. Tried reproducing the issue but unable to, had a windows update as well. Closing issue.
interp-mod.zip


System Events got an error: Can’t get login item "IPFS Desktop"

2019-05-24T12:07:10.926Z error: Error: 36:68: execution error: System Events got an error: Can’t get login item "IPFS Desktop". (-1728)

    at ChildProcess.<anonymous> (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/node_modules/applescript/lib/applescript.js:49:13)
    at ChildProcess.emit (events.js:182:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
2019-09-06T11:36:35.896Z error: [ipfsd] addr must be a string, Buffer, or another Multiaddr

My IPFS config. Looks like it's something to do with the multiple addresses I have setup for API/Gateway?
⨎ cat ~/.ipfs/config
{
  "API": {
    "HTTPHeaders": {
      "Access-Control-Allow-Credentials": [
        "true"
      ],
      "Access-Control-Allow-Methods": [
        "PUT",
        "POST",
        "GET"
      ],
      "Access-Control-Allow-Origin": [
        "http://example.com"
      ],
      "Server": [
        "go-ipfs/0.4.17"
      ]
    }
  },
  "Addresses": {
    "API": [
      "/ip4/<IP_ADDRESS>/tcp/5001",
      "/ip6/::1/tcp/5002"
    ],
    "Announce": [],
    "Gateway": ["/ip4/<IP_ADDRESS>/tcp/3003", "/ip4/<IP_ADDRESS>/tcp/3004"],
    "NoAnnounce": [],
    "Swarm": [
      "/ip4/<IP_ADDRESS>/tcp/3000",
      "/ip4/<IP_ADDRESS>/tcp/3001/ws"
    ]
  },
  "Bootstrap": [
    "/dnsaddr/bootstrap.libp2p.io/ipfs/QmNnooDu7bfjPFoTZYxMNLWUQJyrVwtbZg5gBMjTezGAJN",
    "/dnsaddr/bootstrap.libp2p.io/ipfs/QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa",
    "/dnsaddr/bootstrap.libp2p.io/ipfs/QmbLHAnMoJPWSCR5Zhtx6BHJX9KiKNN6tpvbUcqanj75Nb",
    "/dnsaddr/bootstrap.libp2p.io/ipfs/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt",
    "/ip4/<IP_ADDRESS>/tcp/4001/ipfs/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ",
    "/ip4/<IP_ADDRESS>/tcp/4001/ipfs/QmSoLPppuBtQSGwKDZT2M73ULpjvfd3aZ6ha4oFGL1KrGM",
    "/ip4/<IP_ADDRESS>/tcp/4001/ipfs/QmSoLSafTMBsPKadTEgaXctDQVcqN88CNLHXMkTNwMKPnu",
    "/ip4/<IP_ADDRESS>/tcp/4001/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64",
    "/ip4/<IP_ADDRESS>/tcp/4001/ipfs/QmSoLer265NRgSp2LA3dPaeykiS1J6DifTC88f5uVQKNAd",
    "/ip6/2604:a880:1:20::203:d001/tcp/4001/ipfs/QmSoLPppuBtQSGwKDZT2M73ULpjvfd3aZ6ha4oFGL1KrGM",
    "/ip6/2400:6180:0:d0::151:6001/tcp/4001/ipfs/QmSoLSafTMBsPKadTEgaXctDQVcqN88CNLHXMkTNwMKPnu",
    "/ip6/2604:a880:800:10::4a:5001/tcp/4001/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64",
    "/ip6/2a03:b0c0:0:1010::23:1001/tcp/4001/ipfs/QmSoLer265NRgSp2LA3dPaeykiS1J6DifTC88f5uVQKNAd",
    "/ip4/<IP_ADDRESS>/tcp/4002/ipfs/QmSeJDTNXyVtGCKyjZ79HGknuLaEdttm7VreA1cwefNa39"
  ],
  "Datastore": {
    "BloomFilterSize": 0,
    "GCPeriod": "1h",
    "HashOnRead": false,
    "Spec": {
      "mounts": [
        {
          "child": {
            "path": "blocks",
            "shardFunc": "/repo/flatfs/shard/v1/next-to-last/2",
            "sync": true,
            "type": "flatfs"
          },
          "mountpoint": "/blocks",
          "prefix": "flatfs.datastore",
          "type": "measure"
        },
        {
          "child": {
            "compression": "none",
            "path": "datastore",
            "type": "levelds"
          },
          "mountpoint": "/",
          "prefix": "leveldb.datastore",
          "type": "measure"
        }
      ],
      "type": "mount"
    },
    "StorageGCWatermark": 90,
    "StorageMax": "10GB"
  },
  "Discovery": {
    "MDNS": {
      "Enabled": true,
      "Interval": 10
    }
  },
  "Experimental": {
    "FilestoreEnabled": false,
    "Libp2pStreamMounting": false,
    "P2pHttpProxy": false,
    "QUIC": false,
    "ShardingEnabled": false,
    "UrlstoreEnabled": false
  },
  "Gateway": {
    "APICommands": null,
    "HTTPHeaders": {
      "Access-Control-Allow-Headers": [
        "X-Requested-With",
        "Range"
      ],
      "Access-Control-Allow-Methods": [
        "GET"
      ],
      "Access-Control-Allow-Origin": [
        "*"
      ]
    },
    "PathPrefixes": [],
    "RootRedirect": "",
    "Writable": false
  },
  "Identity": {
    "PeerID": "QmaFBzZTyz3ibDumf9kUTno7xSFoa36ateG7uoithtY855",
    "PrivKey": "[REDACTED]"
  },
  "Ipns": {
    "RecordLifetime": "",
    "RepublishPeriod": "",
    "ResolveCacheSize": 128
  },
  "Mounts": {
    "FuseAllowOther": false,
    "IPFS": "/ipfs",
    "IPNS": "/ipns"
  },
  "Pubsub": {
    "DisableSigning": false,
    "Router": "",
    "StrictSignatureVerification": false
  },
  "Reprovider": {
    "Interval": "12h",
    "Strategy": "all"
  },
  "Routing": {
    "Type": "dht"
  },
  "Swarm": {
    "AddrFilters": null,
    "ConnMgr": {
      "GracePeriod": "20s",
      "HighWater": 900,
      "LowWater": 600,
      "Type": "basic"
    },
    "DisableBandwidthMetrics": false,
    "DisableNatPortMap": false,
    "DisableRelay": false,
    "EnableRelayHop": false
  }
}

@alanshaw I believe the System Events error can be easily ignored (please try toggling Launch at login on settings to enable and disable to see if it seems to work). That error generally happens when we tell AutoLaunch to make sure it is disabled and it was never enabled so there it is not registered on the Login items. So can be ignored.
The true problem here is the ipfsd error I believe. As far as I can tell just by looking at your settings is that we assume config.Addresses.API/Gateway is a string and forgot the possibility of it being an array!
I will take a look at this ASAP.

@alanshaw go-ipfs config does not say API and Gateway can be arrays. Can they?

Since go-ipfs 0.4.18 - https://github.com/ipfs/go-ipfs-config/pull/11
Any chance you can send a PR to fix the go-ipfs config documentation?

I will! Thanks!

Hmm... Currently we check if the ports are available and suggest updating them if they're busy. Now I'm wondering... an array as the API or Gateway address implicates an infinite amount of port collisions...
Currently we have dialogs for:

API+Gateway collision.
API collision.
Gateway collision.

I'm wondering if it's better to show a dialog per port collision. I doubt there will be many anyways... but it can happen! What do you think?


sfx_x64.cab has an invalid digital signature

Issue Title
sfx_x64.cab has an invalid digital signature
General
In the process of installing Microsoft .NET Core SDK 3.0.100-preview, error ocurred and prompted "A file that is required cannot be installed because the cabinet file C:\ProgramData\Package Cache{849917F8-9A15-34CD-B971-A7478B010F70}V<IP_ADDRESS>\sfx_x64.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. "
Plus, my system environment ： Windows Server 2008 R2 Enterprise Service Pack 1, no internet connection. Thanks.

I encountered the same problem, but it was solved. Because your computer needs to connect to Microsoft to register a signature when installing the .NET Core environment, you must ensure that your computer is connected to the external network, otherwise this error will occur.

缺少数字证书：
microsoft root certificate authority 2010
microsoft root certificate authority 2011
解决办法：
一、先安装数字证书；
找一台正常装了VS2015的电脑，Win+R打开运行，输入certmgr.msc，打开证书管理界面。我们从自己电脑导出一个，我的win7 系统。
导出及导入步骤如下：
1.开始→运行→certmgr.msc
2，展开：证书→受信任的根证书颁发机构→证书
3.右击展开菜单，所有任务→导入
4.剩下的，就是选择你下载好的cer文件，然后无限下一步了。
二、证书安装成功以后，安装Microsoft Visual C++ 2015 Redistributable
下载地址：https://www.microsoft.com/en-us/download/details.aspx?id=48145
三、安装Windows补丁
下载地址：https://support.microsoft.com/en-us/kb/2533623
四、重启电脑，再次安装.net core hosting和skd，安装成功。

Had a similar situation while mine error file was sfx_x86.cab,
and resolved using @hsb0307 's reply.
When I rancertmgr.msc on my no-internet-connection Windows Server 2008 R2 Standard sp1,
there was only microsoft root certificate authority 2010 but no microsoft root certificate authority 2011.
So I exported it from my VS2017-installed laptop, imported to that server, ran the installation with repair, and everything were good.
Thanks @hsb0307

For fixing the problem just import these three certificates from https://github.com/fhazraty/MicrosoftCertificates to "Trusted Root Certification Authorities" in certmgr.msc


\color and \text together, will not render.

I have this formula that will not render, but if you remove the color command, it will render.
$\tau_{\color{Green}\text{rms}}$
KaTeX will render it correctly.
Environment:
MathJax.js v2.7.5
AsciiMath Input Jax v2.7.5
MathML Input Jax v2.7.5
TeX Input Jax v2.7.5
CommonHTML Output Jax v2.7.5
PreviewHTML Output Jax v2.7.5
mml Element Jax v2.7.5
AssistiveMML Extension v2.7.5
MathEvents Extension v2.7.5
MathMenu Extension v2.7.5
MathZoom Extension v2.7.5
TeX/AMSmath Extension v2.7.5
TeX/AMSsymbols Extension v2.7.5
TeX/noErrors Extension v2.7.5
TeX/noUndefined Extension v2.7.5
accessibility-menu Extension v1.5.0
asciimath2jax Extension v2.7.5
fast-preview Extension v2.7.5
mml2jax Extension v2.7.5
tex2jax Extension v2.7.5
Chrome v67.0.3396.99

The default \color comment in MathJax does not work quite the same as in LaTeX.  It takes two arguments, the first being the color and the second being the thing to be colored, whereas the LaTeX \color macro takes one argument (the color), and makes everything that follows it be in that color.   Therefore, in MathJax, your expression acts essentially like
\tau_{\color{Green}{\text}{rms}}

where only \text is the second argument, and when that \text is processed, it has been separated from its argument, causing the "missing argument" error that you are getting.  So one solution would be to brace the second argument to \color, as in
\tau_{\color{Green}{\text{rms}}}

Alternatively, you can load the color extension to get a LaTeX-compatible version of \color.  Either add it to your configurations TeX extensions list, or use \require{color} within the first math expression that needs color:
\require{color}
\tau_{\color{Green}\text{rms}}

Either one will work.


Remove testing dependency on language server

This change removes the dependency of testing activation on language server. Currently it does not provide a substitute for the language server symbol provider. I will be adding that separately when implementing the testing controller. I will use the symbol provider script that uses AST to get the required location (we may even use TS code to find the location). For now this PR ensures that testing activation is not blocked on LS activation.
Closes https://github.com/microsoft/vscode-python-internalbacklog/issues/239

@jakebailey FYI. There is lot of work pending but this is happening :) finally


Yaso

@pwntester I am not sure what's happening here but it doesn't feel right.

This PR looks like a spam to me. No valid comments and it has all old commits so I am not really sure if it was a mistake or an intentional move.
I am closing it so no one would use this for now. @pwntester please reopen if you see any value.


Fix address format in genesis files

Consistent prefix of all genesis address values with 0x.

Pull Request Test Coverage Report for Build 117

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.946%

Totals

Change from base Build 115:
0.0%

Covered Lines:
129

Relevant Lines:
133

💛  - Coveralls

why is genesis states a different file?


Option to view actual QOH on detail page

What is the motivation for adding/enhancing this feature?

There should be a product store setting that lets companies choose if they want to show systemic QOH on their cycle count product detail page to help users during their count.
This setting should be blocked unless the user has FULFILL_INVCUNT_ADMIN or INV_COUNT_ADMIN
@appurvajain please make draft Product Store Setting data for this and add it here as a comment, I will review.
@Dhiraj1405 make a mockup for this referencing the latest cycle count detail page and also make a setting for it on the settings page.

Sure, will add the mockup here in sometime.

Sure, will add the draft data here.
On Thu, Apr 13, 2023 at 4:55 PM Dhiraj Nagar @.***>
wrote:

Sure, will add the mockup here in sometime.
—
Reply to this email directly, view it on GitHub
https://github.com/hotwax/inventory-count/issues/169#issuecomment-1506797509,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3AVXGQBGYRUXHOOESKJHPLXA7PENANCNFSM6AAAAAAW2OHBHE
.
You are receiving this because you were assigned.Message ID:
@.***>

<Enumeration enumId=“QOH_INV_COUNTAPP” enumName=“QOH in Inventory Count app“ enumTypeId="PROD_STR_STNG"/>

Enum ID: INV_CNT_VIEW_QOH
Enum ID like this allows all inventory count related settings to be identified together more easily since it's in a prefix. The word "view" gives a clear understanding of what verb we're allowing.
enumName: View QOH while inventory counting"
enumDesc: Please come up with a good enum description

@dt2patel
enumDesc: Allows the user to see current QOH from HotWax OMS on the product detail page of the Inventory Count app to help users during the periodic cycle count.

@dt2patel Please review
Count page:
Upload page:
Note: The count on the Upload page is updated count

Setting Card:

I tweaked the designs slightly on your Figma file, but other than that I think we're good to go

@appurvajain please paste the final enum id here and also commit it to OMS upgrade data

@adityasharma7 this issue is all set to start dev work I think, let me know if we have any blockers here

The final enum data and product store setting data:


WPF DLLs are loaded when EXE is targeting .NET Framework

Symptoms:
When starting an EXE targeting the full .NET Framework, three WPF assemblies are loaded: "PresentationFramework", "WindowsBase" and "PresentationCore". This loading is not neccessary and costs at my Workstation aprox 100ms while starting up a small sample application with 6 controls (about 5% startup time).
Cause:
The System.Windows.Input.ICommand interface was originally member of the PresentationFramework assembly.
Later the ICommand interface was forwarded to System assembly.
Too bad, the ICommand still has attached a TypeConverterAttribut targeting System.Windows.Input.CommandConverter, which is still located in PresentationFramework assembly.
During startup the TypeConverters are evaluated and cause loading these WPF assemblies.
You can see it in this Visual Studio Output when runnig ControlCatalog.Desktop.exe:
'ControlCatalog.Desktop.exe' (CLR v4.0.30319: ControlCatalog.Desktop.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\PresentationFramework\v4.0_<IP_ADDRESS>__31bf3856ad364e35\PresentationFramework.dll'. Cannot find or open the PDB file.
'ControlCatalog.Desktop.exe' (CLR v4.0.30319: ControlCatalog.Desktop.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\WindowsBase\v4.0_<IP_ADDRESS>__31bf3856ad364e35\WindowsBase.dll'. Cannot find or open the PDB file.
'ControlCatalog.Desktop.exe' (CLR v4.0.30319: ControlCatalog.Desktop.exe): Loaded 'C:\WINDOWS\Microsoft.Net\assembly\GAC_64\PresentationCore\v4.0_<IP_ADDRESS>__31bf3856ad364e35\PresentationCore.dll'. Cannot find or open the PDB file.

Possible Fix:
A single change in Portable.Xaml.XamlType (I do not know, if it is a good place, but it works)
    virtual XamlValueConverter<TypeConverter> LookupTypeConverter() {
            var t = UnderlyingType;
            if (t == null)
                return null;

#if WPF_COMMAND_CONVERTER_FIX
            // PURPOSE: Prevent loading of WPF PresentationFramework assemblies when compiling against full dotnet framework.
            // TECHNOTE: ICommand is forwarded from PresentationFramework to System, but CommandConverter (TypeConverter) still lives there...
            // Even in dotnet core, but here is the assembly not resolvable.
            // Under dotnet framework fix this with a self written TypeConverter or null.
            // This saves about 100ms / ~5% startup time of a very simple application.
            if (t == typeof(System.Windows.Input.ICommand)) {
                // If we need a TypeConverter return a self written one (e.g. AvaloniaCommandConverter)
                //return SchemaContext.GetValueConverter<TypeConverter>(typeof(AvaloniaCommandConverter), this);
                // If we do not need a TypeConverter, simply return null.
                return null;
            }
#endif //WPF_COMMAND_CONVERTER_FIX

            var converterName = CustomAttributeProvider.GetTypeConverterName(false);
            if (converterName != null)
                return SchemaContext.GetValueConverter<TypeConverter>(Type.GetType(converterName), this);
            ...
    }

The original CommandConverter states that it can converts from/to string type. If such a conversion to RoutedCommand is neccessary, Avalonia will have to implement its own WPF agnostic CommandConverter.
Note:
There is also a ValueSerializer attached, it has the same reference to PresentationFramework, but it seems it is not evaluated in Avalonia.
Hope this helps!
Avalonia is an impressive Framework!
Regards, Gerhard

Please open up a Pull Request for this so that we can thoroughly check and test the changes you propose! :smile:

I have same problem. when i run the app with normal .Net Framework all the commands stop working.

We don't use Portable.Xaml anymore


[fix] #1049: Add support for export-from to no-extraneous-dependencies

Fixes #1049, since this one ended up biting me today!

Coverage decreased (-0.2%) to 96.344% when pulling ffe346e73063787b763a2d3e4651fee14cb37349 on marcusdarmstrong:master into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.

Coverage decreased (-0.2%) to 96.344% when pulling ffe346e73063787b763a2d3e4651fee14cb37349 on marcusdarmstrong:master into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.

Coverage decreased (-0.2%) to 96.344% when pulling ffe346e73063787b763a2d3e4651fee14cb37349 on marcusdarmstrong:master into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.

Coverage decreased (-0.2%) to 96.344% when pulling ffe346e73063787b763a2d3e4651fee14cb37349 on marcusdarmstrong:master into 112a0bf442e52b25cd7029a9905df2508e191ac1 on benmosher:master.


mobilenet training schedule

can you give me some suggestions about the training parameters while training the mobile net version?

@lzx1413  I simply follow the same strategy for vgg version while the initial lr for COCO is 0.004 using 32 batchsize ( 0.002 for VGG).

thanks