gcc failing

Hi,
Thanks for your code. When I am trying to compile make.sh based on your instruction on centos-7 with titan-x gpu and cuda-8.0 I am getting the following error. Could you please help me setting this up properly. Many thanks.
running build_ext
skipping 'model/utils/bbox.c' Cython extension (up-to-date)
skipping 'pycocotools/_mask.c' Cython extension (up-to-date)
Compiling nms kernels by nvcc...
/home/kalyanb/Desktop/faster-rcnn/lib/model/nms
Including CUDA code.
['/home/kalyanb/Desktop/faster-rcnn/lib/model/nms/src/nms_cuda_kernel.lib', '/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/ATen.lib', '/usr/local/cuda-8.0/lib/x64/cudart.lib', '/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/_C.lib']
generating /tmp/tmp8otu47o2/_nms.c
setting the current directory to '/tmp/tmp8otu47o2'
running build_ext
building '_nms' extension
creating home
creating home/kalyanb
creating home/kalyanb/Desktop
creating home/kalyanb/Desktop/faster-rcnn
creating home/kalyanb/Desktop/faster-rcnn/lib
creating home/kalyanb/Desktop/faster-rcnn/lib/model
creating home/kalyanb/Desktop/faster-rcnn/lib/model/nms
creating home/kalyanb/Desktop/faster-rcnn/lib/model/nms/src
gcc -pthread -B /home/kalyanb/anaconda3/envs/pytorch/compiler_compat -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DWITH_CUDA -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/THC -I/usr/local/cuda-8.0/include -I/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/include -I/home/kalyanb/anaconda3/envs/pytorch/include/python3.5m -c _nms.c -o ./_nms.o
In file included from /home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THVector.h:5:0,
from /home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/TH.h:12,
from _nms.c:492:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_polevl\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:134:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (size_t i = 0; i <= len; i++) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:134:3: note: use option -std=c99 or -std=gnu99 to compile your code
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_polevlf\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:142:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (size_t i = 0; i <= len; i++) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_trigamma\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:260:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (int i = 0; i < 6; ++i) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_trigammaf\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:278:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (int i = 0; i < 6; ++i) {
^
Traceback (most recent call last):
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/unixccompiler.py", line 118, in _compile
extra_postargs)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/ccompiler.py", line 909, in spawn
spawn(cmd, dry_run=self.dry_run)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/spawn.py", line 36, in spawn
_spawn_posix(cmd, search_path, dry_run=dry_run)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/spawn.py", line 159, in _spawn_posix
% (cmd, exit_status))
distutils.errors.DistutilsExecError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 51, in _build
dist.run_command('build_ext')
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 533, in build_extension
depends=ext.depends)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/ccompiler.py", line 574, in compile
self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/unixccompiler.py", line 120, in _compile
raise CompileError(msg)
distutils.errors.CompileError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "build.py", line 49, in
ffi.build()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/init.py", line 184, in build
_build_extension(ffi, cffi_wrapper_name, target_dir, verbose)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/init.py", line 108, in _build_extension
outfile = ffi.compile(tmpdir=tmpdir, verbose=verbose, target=libname)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/api.py", line 697, in compile
compiler_verbose=verbose, debug=debug, **kwds)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/recompiler.py", line 1520, in recompile
compiler_verbose, debug)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 22, in compile
outputfilename = _build(tmpdir, ext, compiler_verbose, debug)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 58, in _build
raise VerificationError('%s: %s' % (e.class.name, e))
cffi.error.VerificationError: CompileError: command 'gcc' failed with exit status 1
Compiling roi pooling kernels by nvcc...
/home/kalyanb/Desktop/faster-rcnn/lib/model/roi_pooling
Including CUDA code.
['/home/kalyanb/Desktop/faster-rcnn/lib/model/roi_pooling/src/roi_pooling.lib', '/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/ATen.lib', '/usr/local/cuda-8.0/lib/x64/cudart.lib', '/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/_C.lib']
generating /tmp/tmpfqbf6tlj/_roi_pooling.c
setting the current directory to '/tmp/tmpfqbf6tlj'
running build_ext
building '_roi_pooling' extension
creating home
creating home/kalyanb
creating home/kalyanb/Desktop
creating home/kalyanb/Desktop/faster-rcnn
creating home/kalyanb/Desktop/faster-rcnn/lib
creating home/kalyanb/Desktop/faster-rcnn/lib/model
creating home/kalyanb/Desktop/faster-rcnn/lib/model/roi_pooling
creating home/kalyanb/Desktop/faster-rcnn/lib/model/roi_pooling/src
gcc -pthread -B /home/kalyanb/anaconda3/envs/pytorch/compiler_compat -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DWITH_CUDA -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/THC -I/usr/local/cuda-8.0/include -I/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/include -I/home/kalyanb/anaconda3/envs/pytorch/include/python3.5m -c _roi_pooling.c -o ./_roi_pooling.o
In file included from /home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THVector.h:5:0,
from /home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/TH.h:12,
from _roi_pooling.c:492:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_polevl\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:134:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (size_t i = 0; i <= len; i++) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:134:3: note: use option -std=c99 or -std=gnu99 to compile your code
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_polevlf\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:142:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (size_t i = 0; i <= len; i++) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_trigamma\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:260:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (int i = 0; i < 6; ++i) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_trigammaf\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:278:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (int i = 0; i < 6; ++i) {
^
Traceback (most recent call last):
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/unixccompiler.py", line 118, in _compile
extra_postargs)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/ccompiler.py", line 909, in spawn
spawn(cmd, dry_run=self.dry_run)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/spawn.py", line 36, in spawn
_spawn_posix(cmd, search_path, dry_run=dry_run)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/spawn.py", line 159, in _spawn_posix
% (cmd, exit_status))
distutils.errors.DistutilsExecError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 51, in _build
dist.run_command('build_ext')
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 533, in build_extension
depends=ext.depends)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/ccompiler.py", line 574, in compile
self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/unixccompiler.py", line 120, in _compile
raise CompileError(msg)
distutils.errors.CompileError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "build.py", line 49, in
ffi.build()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/init.py", line 184, in build
_build_extension(ffi, cffi_wrapper_name, target_dir, verbose)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/init.py", line 108, in _build_extension
outfile = ffi.compile(tmpdir=tmpdir, verbose=verbose, target=libname)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/api.py", line 697, in compile
compiler_verbose=verbose, debug=debug, **kwds)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/recompiler.py", line 1520, in recompile
compiler_verbose, debug)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 22, in compile
outputfilename = _build(tmpdir, ext, compiler_verbose, debug)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 58, in _build
raise VerificationError('%s: %s' % (e.class.name, e))
cffi.error.VerificationError: CompileError: command 'gcc' failed with exit status 1
Compiling roi align kernels by nvcc...
/home/kalyanb/Desktop/faster-rcnn/lib/model/roi_align
Including CUDA code.
['/home/kalyanb/Desktop/faster-rcnn/lib/model/roi_align/src/roi_align_kernel.lib', '/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/ATen.lib', '/usr/local/cuda-8.0/lib/x64/cudart.lib', '/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/_C.lib']
generating /tmp/tmp9zecd3ms/_roi_align.c
setting the current directory to '/tmp/tmp9zecd3ms'
running build_ext
building '_roi_align' extension
creating home
creating home/kalyanb
creating home/kalyanb/Desktop
creating home/kalyanb/Desktop/faster-rcnn
creating home/kalyanb/Desktop/faster-rcnn/lib
creating home/kalyanb/Desktop/faster-rcnn/lib/model
creating home/kalyanb/Desktop/faster-rcnn/lib/model/roi_align
creating home/kalyanb/Desktop/faster-rcnn/lib/model/roi_align/src
gcc -pthread -B /home/kalyanb/anaconda3/envs/pytorch/compiler_compat -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DWITH_CUDA -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/THC -I/usr/local/cuda-8.0/include -I/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/include -I/home/kalyanb/anaconda3/envs/pytorch/include/python3.5m -c _roi_align.c -o ./_roi_align.o
In file included from /home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THVector.h:5:0,
from /home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/TH.h:12,
from _roi_align.c:492:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_polevl\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:134:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (size_t i = 0; i <= len; i++) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:134:3: note: use option -std=c99 or -std=gnu99 to compile your code
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_polevlf\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:142:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (size_t i = 0; i <= len; i++) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_trigamma\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:260:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (int i = 0; i < 6; ++i) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_trigammaf\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:278:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (int i = 0; i < 6; ++i) {
^
Traceback (most recent call last):
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/unixccompiler.py", line 118, in _compile
extra_postargs)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/ccompiler.py", line 909, in spawn
spawn(cmd, dry_run=self.dry_run)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/spawn.py", line 36, in spawn
_spawn_posix(cmd, search_path, dry_run=dry_run)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/spawn.py", line 159, in _spawn_posix
% (cmd, exit_status))
distutils.errors.DistutilsExecError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 51, in _build
dist.run_command('build_ext')
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 533, in build_extension
depends=ext.depends)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/ccompiler.py", line 574, in compile
self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/unixccompiler.py", line 120, in _compile
raise CompileError(msg)
distutils.errors.CompileError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "build.py", line 48, in
ffi.build()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/init.py", line 184, in build
_build_extension(ffi, cffi_wrapper_name, target_dir, verbose)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/init.py", line 108, in _build_extension
outfile = ffi.compile(tmpdir=tmpdir, verbose=verbose, target=libname)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/api.py", line 697, in compile
compiler_verbose=verbose, debug=debug, **kwds)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/recompiler.py", line 1520, in recompile
compiler_verbose, debug)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 22, in compile
outputfilename = _build(tmpdir, ext, compiler_verbose, debug)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 58, in _build
raise VerificationError('%s: %s' % (e.class.name, e))
cffi.error.VerificationError: CompileError: command 'gcc' failed with exit status 1
Compiling roi crop kernels by nvcc...
/home/kalyanb/Desktop/faster-rcnn/lib/model/roi_crop
Including CUDA code.
['/home/kalyanb/Desktop/faster-rcnn/lib/model/roi_crop/src/roi_crop_cuda_kernel.lib', '/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/ATen.lib', '/usr/local/cuda-8.0/lib/x64/cudart.lib', '/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/_C.lib']
generating /tmp/tmp4uv8u0la/_roi_crop.c
setting the current directory to '/tmp/tmp4uv8u0la'
running build_ext
building '_roi_crop' extension
creating home
creating home/kalyanb
creating home/kalyanb/Desktop
creating home/kalyanb/Desktop/faster-rcnn
creating home/kalyanb/Desktop/faster-rcnn/lib
creating home/kalyanb/Desktop/faster-rcnn/lib/model
creating home/kalyanb/Desktop/faster-rcnn/lib/model/roi_crop
creating home/kalyanb/Desktop/faster-rcnn/lib/model/roi_crop/src
gcc -pthread -B /home/kalyanb/anaconda3/envs/pytorch/compiler_compat -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DWITH_CUDA -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH -I/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/THC -I/usr/local/cuda-8.0/include -I/home/kalyanb/anaconda3/envs/pytorch/bin/Lib/site-packages/torch/lib/include -I/home/kalyanb/anaconda3/envs/pytorch/include/python3.5m -c _roi_crop.c -o ./_roi_crop.o
In file included from /home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THVector.h:5:0,
from /home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/TH.h:12,
from _roi_crop.c:492:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_polevl\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:134:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (size_t i = 0; i <= len; i++) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:134:3: note: use option -std=c99 or -std=gnu99 to compile your code
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_polevlf\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:142:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (size_t i = 0; i <= len; i++) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_trigamma\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:260:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (int i = 0; i < 6; ++i) {
^
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h: In function \u2018TH_trigammaf\u2019:
/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/../../lib/include/TH/THMath.h:278:3: error: \u2018for\u2019 loop initial declarations are only allowed in C99 mode
for (int i = 0; i < 6; ++i) {
^
Traceback (most recent call last):
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/unixccompiler.py", line 118, in _compile
extra_postargs)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/ccompiler.py", line 909, in spawn
spawn(cmd, dry_run=self.dry_run)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/spawn.py", line 36, in spawn
_spawn_posix(cmd, search_path, dry_run=dry_run)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/spawn.py", line 159, in _spawn_posix
% (cmd, exit_status))
distutils.errors.DistutilsExecError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 51, in _build
dist.run_command('build_ext')
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/command/build_ext.py", line 533, in build_extension
depends=ext.depends)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/ccompiler.py", line 574, in compile
self._compile(obj, src, ext, cc_args, extra_postargs, pp_opts)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/distutils/unixccompiler.py", line 120, in _compile
raise CompileError(msg)
distutils.errors.CompileError: command 'gcc' failed with exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "build.py", line 49, in
ffi.build()
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/init.py", line 184, in build
_build_extension(ffi, cffi_wrapper_name, target_dir, verbose)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/torch/utils/ffi/init.py", line 108, in _build_extension
outfile = ffi.compile(tmpdir=tmpdir, verbose=verbose, target=libname)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/api.py", line 697, in compile
compiler_verbose=verbose, debug=debug, **kwds)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/recompiler.py", line 1520, in recompile
compiler_verbose, debug)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 22, in compile
outputfilename = _build(tmpdir, ext, compiler_verbose, debug)
File "/home/kalyanb/anaconda3/envs/pytorch/lib/python3.5/site-packages/cffi/ffiplatform.py", line 58, in _build
raise VerificationError('%s: %s' % (e.class.name, e))
cffi.error.VerificationError: CompileError: command 'gcc' failed with exit status 1

Solved it by adding these lines to make.sh
export CXXFLAGS="-std=c++11"
export CFLAGS="-std=c99"
export PATH=/usr/local/cuda-8.0/bin${PATH:+:${PATH}}
export CPATH=/usr/local/cuda-8.0/include${CPATH:+:${CPATH}}
export LD_LIBRARY_PATH=/usr/local/cuda-8.0/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}

thk

it is useful!


⚠ Samsung has degraded performance

In 4395950, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2308 ms

Resolved: Samsung performance has improved in 1cb11e1.


Optimize COUNT(1): Change the sentinel value's type for COUNT(*) to Int64

Which issue does this PR close?
Closes #9943.
Rationale for this change
Make COUNT(1) equivalent to COUNT(*).
What changes are included in this PR?
Change the type of COUNT_STAR_EXPANSION to ScalarValue::Int64.
Are these changes tested?
Yes, with revised existing tests and a new one that tests the optimization for count(1) case.
Are there any user-facing changes?

Might as well try whether /benchmark works as intended now.

Thanks again @gruuya


typo in normalization denominator in parallel retention?

In the parallel retention code, the normalization denominator uses .sum(dim=-1, keepdim=True).abs()
def parallel_forward(self, qr, kr, v, mask):
      bsz, tgt_len, embed_dim = v.size()
      vr = v.view(bsz, tgt_len, self.num_heads, self.head_dim).transpose(1, 2)
      qk_mat = qr @ kr.transpose(-1, -2) # bsz * m * tgt_len * tgt_len
      qk_mat = qk_mat * mask
      # invariant after normalization
      qk_mat = qk_mat / qk_mat.detach().sum(dim=-1, keepdim=True).abs().clamp(min=1)
      output = torch.matmul(qk_mat, vr)
      output = output.transpose(1, 2)
      return output

However, in the chunkwise retention, the normalization uses .abs().sum(). From my perspective, .abs().sum() is better than .sum().abs() for the normalization denominator since real values may cancel with each other during the summation. So is it a typo here?

We used .abs().sum() in our internal code base. I fixed this issue at https://github.com/microsoft/torchscale/commit/fdd8838a756c7c435d7f8a1e4303e150dfac7442 . Thanks for pointing out this.


Toggle off certain features & fix various bugs

Please make sure your pull request complies with these guidelines:

[x] Use same formatting

[x] Changes must have been tested on PMMP.

[x] Unless it is a minor code modification, you must use an IDE.

[x] Have a detailed title.

What does the PR change?

Fixed /f top with large negative/positive numbers crashing server. (#128)
Fixed /f claim with large radiuses for circle/square toggles crashing server. (#128)
Fixed /f promote on an offline user crashing server. (#128)
NEW: Added ability to disable any commands. (#128)
NEW: Added ability to disable autoclaim, unclaimall, square, and circle claims. (#128)
NEW: Added ability to configure max radiuses for circle/square claims. (#128)

Testing Environment

PHP:
PMMP:
OS:

Why did you remove all the subcommands for /f claim and /f unclaim?
Why did you remove /f enemy?
You should be loading the virions using devirion plugin, NOT adding the libs directly.

Why did you remove all the subcommands for /f claim and /f unclaim?
Why did you remove /f enemy?
You should be loading the virions using devirion plugin, NOT adding the libs directly.

when we do the /f claim circle<PHONE_NUMBER>99999999999999999999999 or other it crashes the server, I removed the f enemy but I think I'm going to put it back and offer people to activate or deactivate it.

we cant even cherry pick the good stuff out because it's all in one single commit

we cant even cherry pick the good stuff out because it's all in one single commit

What do you want to take? You want me to do multiple commits? One for subcommands and the others

I did everything as you advised me if you have any suggestions or advice I will listen to them

I will review this next month.

I put everything you advise, thank you very much

We should just add command blacklisting instead, probably.

Having set limit for the /f top "PHP_INT_MAX" does not fix the main bug which is /f top power or member<PHONE_NUMBER>99999 and -999999999999999

Why this PR deals with so many things..
By the way, limiting to PHP_INT_MAX will probably not suffice for commands that require complex calculations or database calls. As it could lead to hidden performance issues.

All commands that have an int can cause a crash, they should all be fixed at the same time

@dadodasyra thanks for the feedback.
I'll most likely cherrypick the commits from this PR instead of merging.
About PHP_INT_MAX, should we just set the maximum to some reasonable limit instead then? like 100000.
@FahZohh Agreed. Maybe a helper function to validate numbers. Not sure what the best way to handle this is.

so we need to put a limit of 100000 for all commands that contain an int, but I have a question that won't do like last time or an extremely large number would probably result in an int overflow thus causing it to become a float ?

Having set limit for the /f top "PHP_INT_MAX" does not fix the main bug which is /f top power or member<PHONE_NUMBER>99999 and -999999999999999

Oh, I see why this is still the case.
foreach (array_slice($factions, $page * self::PAGE_LENGTH, self::PAGE_LENGTH) as $rank => $faction)

Page being multiplied by 10 here, so it'll just turn back into a float here.

This should be a better solution. We set the max as the number of possible factions, instead of PHP_INT_MAX.

ok, seems to be merging. don't feel like cherrypicking so weee


lineage-integrator-api includes additional logging implementation

The lineage-integrator-api module has a dependency:
        implementation("commons-logging:commons-logging:${commonsloggingVersion}")

This causes a warning when checking for duplicate logging frameworks, ie when building the lineage sample connector:
* What went wrong:
Could not determine the dependencies of task ':shadowJar'.
> Could not resolve all dependencies for configuration ':runtimeClasspath'.
   > Could not resolve commons-logging:commons-logging:1.2.
     Required by:
         project : > org.odpi.egeria:lineage-integrator-api:3.15 > io.openlineage:openlineage-java:0.18.0
         project : > org.odpi.egeria:lineage-integrator-api:3.15 > io.openlineage:openlineage-java:0.18.0 > org.apache.httpcomponents:httpclient:4.5.13
      > Module 'commons-logging:commons-logging' has been rejected:
           Cannot select module with conflict on capability 'dev.jacomet.logging:commons-logging-impl:1.0' also provided by [org.springframework:spring-jcl:5.3.24(runtimeElements)]
   > Could not resolve org.springframework:spring-jcl:5.3.24.
     Required by:
         project : > org.odpi.egeria:lineage-integrator-api:3.15 > org.odpi.egeria:ffdc-services:3.15 > org.springframework:spring-core:5.3.24
      > Module 'org.springframework:spring-jcl' has been rejected:
           Cannot select module with conflict on capability 'dev.jacomet.logging:commons-logging-impl:1.0' also provided by [commons-logging:commons-logging:1.2(runtime)]

This may cause logging framework issues and should be resolved through adapter configuration - such as making use of jcl-over-slf4j
See https://www.alibabacloud.com/blog/598223 for some suggestions

See PR #7458 and https://github.com/odpi/egeria/actions/runs/4299969609
This is a run from the PR that bumps the plugin version to perform a more thorough check.
For now will leave the plugin at the current version since

more changes will be introduced by our spring changes
this logging issue needs investigation

If this is fixed before then, this plugin can be updated at the same time
We should also test (runtime) the lineage support after making a change
@mandy-chessell I don't think there's any fvt coverage yet. is this something you have planned? what's the best way to validate any change here. We need to check with v4, and after new spring updates in any case

Further investigation shows this affects many (most?) modules - it is NOT specific to lineage.
#7489 implemented a fix to dependencies to ensure only a single implementation is used ie in this case with slf4j bridge being used as the commons logging implementation (and slfj itself being implemented by logback in our application)


Update README.md

@OrenYunger Please take a look at the updates I made to the readme file and approve the PR if you're OK with the changes.


Using @logtail/edge causes huge increase in GB-s footprint on cloudflare

Hello, I'm using @logtail/edge in a cloudflare pages application with _worker.js. The web server is hono.
I recently added @logtail/edge to my app and my usage increased from around 60 GB-s to 2.3k GB-s

For now I have removed logging and will update the thread with how the usage looks post removal.

Update: the issue is gone after removing logtail.
FYKI The increase is around 6x which IMHO make logtail unusable in production on cloudflare.

It's likely depending on your region the huge increase in usage is just awaiting the response from the server to confirm the logs have been written, is there anyway for you to check what percent of the runtime is spent idling? it might be that serverless logging could use a rework to just pop off log requests without batching and never await them as the loss of a few logs due to network issues is less important then the massive increase in cost


Update Dockerfile - fix missing dependencies

There were some utilities missing: python, make, g++. Also node version was too old - current node builds without problems. @swederik please, merge it
PR Checklist

[x] Brief description of changes
[ ] Links to any relevant issues
[x] Required status checks are passing
[ ] User cases if changes impact the user's experience
[ ] @mention a maintainer to request a review

Thanks! I don't know why Python would be necessary to run the build, though?

It happens during node-gyp invokation - looks like there is some build happening under the hood.


FREME NER life version may be down

See attached CURL requests. The one going to FREME dev works, the other not. This was reported from Martin Wunderlich, see
https://twitter.com/martin_wun/status/755711296922853376
curl-requests-live-versus-dev-version.txt

@fsasaki , @jnehring: the service is up again

@sandroacoelho what happened?

I just connect in the server and checked using ps that the service was not available, then I restart it. I will check our logs and tell you the root cause.

Thank you. I stopped FREME NER on freme-live on monday, uploaded the new version and started it as part of the 0.8 release. 10 minutes after the start I got an exception: java.lang.OutOfMemoryError: Java heap space. Then I just restarted FREME NER and this time it worked. Maybe its again the out of memory error.

There still seem to be some issues, see from
https://twitter.com/martin_wun/status/755735015938482176

the 502 is gone and has changed to a 400

I checked
http://api.freme-project.eu/doc/current/freme-showcase/xml-to-rdf.html
and it is borken too. It uses the life version of FREME NER. Nothing has chanced in the demo javascript code recently.

FREME NER itself is running. http://api.freme-project.eu/current/e-entity/freme-ner/documents?language=de&dataset=dbpedia&informat=text&input=Welcome to Berlin%2C the capital of Germany! returns data coming from FREME NER. I will further investigate this.

The problem happened both on freme-live and freme-dev. Somehow FREME NER was started in a strange way for both servers. I stopped both packages and restarted them. Now http://api.freme-project.eu/doc/current/freme-showcase/xml-to-rdf.html seems to work.
@fsasaki can you please verify that it works now?

works, thanks!


Initial update to the technology-usage rules to add java-dependency condition

Closing the PR as alternative solution has been implemented to add additional location:https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_git/appcat-cli-java/pullrequest/580398


Implement QUIC-HTTP framing

Implement HTTP framing, as defined in the spec, here:
https://tools.ietf.org/html/draft-ietf-quic-http-11#section-4
I've started the process with the SETTINGS frame, here:
https://github.com/djc/quinn/blob/pre-quicr-quinn/src/http/frame.rs

Any progress?

Not yet, we've been focusing on updating our spec compliance to the latest draft. Would you like to help out? I'm happy to mentor!

Sorry, I am busy recently. I am happy to do this in the future.

No problem, I figured it was worth asking. We'll get to it eventually, hopefully somewhat soon.

Hey! I'd like to start working on this next !

@stammw great! The idea here is just to implement the bytes-to-types and types-to-bytes code for the data structures defined in the HTTP spec. Ideally the module would include unit tests that just check whether round-tripping works as expected. I think it would make sense to use the Codec trait as is used for example in the frame module (which should provide good examples).
Let us know if you have questions!

It might be worth leveraging types from the http crate, though I'm not sure how much work might be required on their end to play well with HTTP3 concepts.

I don't think the frames match the HTTP spec itself, so I don't think you'll find much to use from the http crate.
I forgot to mention it, but I agree that a separate crate would make sense. To disambiguate the HTTP protocol version, I think it would be good to call it quinn-h3.

Hey,
What do you think about how I should handle the QPACK encoded frames (HEADERS, including PUSH_PROMISE ones) ?

Return HttpFrame variant that contains raw Bytes
Return HttpFrame variant that contains a stubbed QPACK type
Do not implement them for the moment

In the interest of being able to run tests, stubbing them out seems most practical. Unless there's some conceivable use for the raw data other than immediately decompressing it?

Actually, I think QPACK wouldn't be a data type but a trait. So stubbing and using raw types inside variants might be more or less the same solution. And at the and the encode -> decode -> compare should still be writable even if the given part would have to be changed afterward?
I wonder how much effort it would be to finish the existing QPACK PR... I worry that #130 will be blocked until then eventually.

closed via #130


fix(radio): onChange trigger twice when uncheck

🤔 这个 PR 的性质是？

[x] 日常 bug 修复
[ ] 新特性提交
[ ] 文档改进
[ ] 演示代码改进
[ ] 组件样式/交互改进
[ ] CI/CD 改进
[ ] 重构
[ ] 代码风格优化
[ ] 测试用例
[ ] 分支合并
[ ] 其他

🔗 相关 Issue
https://github.com/Tencent/tdesign-react/issues/1421

💡 需求背景和解决方案

📝 更新日志

fix(radio): onChange trigger twice when uncheck

[x] 本条 PR 不需要纳入 Changelog

☑ 请求合并前的自查清单
⚠ 请自检并全部勾选全部选项。⚠

[x] 文档已补充或无须补充
[x] 代码演示已提供或无须提供
[x] TypeScript 定义已补充或无须补充
[x] Changelog 已提供或无须提供

Codecov Report

Merging #1422 (2054186) into develop (8a9ef3a) will increase coverage by 1.88%.
The diff coverage is 52.34%.

@@             Coverage Diff             @@
##           develop    #1422      +/-   ##
===========================================
+ Coverage    61.00%   62.88%   +1.88%
===========================================
  Files         1030     1031       +1
  Lines        17933    17983      +50
  Branches      4121     4135      +14
===========================================
+ Hits         10940    11309     +369
+ Misses        6993     6674     -319

Impacted Files
Coverage Δ

src/alert/_example/operation.jsx
60.00% <0.00%> (-40.00%)
:arrow_down:

src/collapse/_usage/index.jsx
0.00% <0.00%> (ø)

src/config-provider/_example/global.jsx
100.00% <ø> (ø)

src/date-picker/DateRangePickerPanel.tsx
10.29% <0.00%> (-0.08%)
:arrow_down:

src/date-picker/_example/panel.jsx
33.33% <0.00%> (-16.67%)
:arrow_down:

src/date-picker/base/Header.tsx
42.66% <0.00%> (-1.17%)
:arrow_down:

src/dialog/RenderDialog.tsx
65.51% <0.00%> (+5.17%)
:arrow_up:

src/form/Form.tsx
67.85% <0.00%> (ø)

src/message/_example/close-function.jsx
41.66% <ø> (ø)

src/popconfirm/_example/describe.jsx
100.00% <ø> (ø)

... and 49 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Expected errors

Necessary for https://github.com/LionWeb-io/lionweb-typescript/pull/93
(I'd prefer to squash-merge.)

Maybe we could add a description of the __TestExpectation.json files somewhere?

Maybe we could add a description of the __TestExpectation.json files somewhere?

Good point that I forgot about. Will make an issue so we don't forget (as hard).


[Spike] Using cli tools to push objects to storage may result in performance issues

Currently we consume the upstream solution to pushing output artifacts to s3 via s3 cli tools, in our case aws s3, this may not scale, or result in performance dregadations, such as time outs, bottlenecks, etc.
The purpose of this task is to investigate the current solution, identify these performance issues, and suggest solutions.

We should confirm the behavior of s3 artifact passing in v2 as well, and if it differs with v1.

Migrated to Jira: https://issues.redhat.com/browse/RHOAIENG-1642


Provide information about runtime version

This is a bit of a controversial request but sometimes it is being mentioned that feature X is coming with version Y, but how does one see the version of runtime running your app?
Are there plans to display this in portal/via CLI?
Could be something like az mesh app version --name foo --resource-group bar.

For most features, this is an artifact of Mesh and SF being developed so closely together that it is hard for us to remember to use the correct nomenclature (ie 6.4 is actually 2018-09-01-preview api version).
There are some features which aren't tied to an api verison.  Container image caching is a recent example.  Where during an interim period, performance of the environments that you are deploying in might differ.  For this reason, I could see some properties of the runtime environment being exposed.


New package: pnpm.pnpm.preview version 9.0.0-alpha.4

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Maybe need approval from @zkochan

Will this be installed now by default? It shouldn't be. It is not the latest version of pnpm.

Will this be installed now by default? It shouldn't be. It is not the latest version of pnpm.

Upgrades stay within a PackageIdentifier. This is the recommended way for separating preview versions, to prevent upgrading gold version users to a preview version, while allowing preview users an easy install path.


feat: --continue-on-error to produce .olean file even if elaboration fails

Implementation of the lean side of #3567. Passing --continue-on-error to lean will cause it to produce an .olean file even if the file had an error, but it will still return error code 1 so lake will still not continue after it.
@tydeu How do you think lake should handle this? The issue is that because lean returns a nonzero error code (and I think it would be misleading for it not to), lake will immediately stop the running thread (compileO calls proc which calls error) and all dependent targets will also fail (IIUC). Should proc take a continueOnError flag?

One other issue to consider is how partial build should be factor into Lake's traces. That is, module should be rebuilt in the future, so Lake somehow needs to invalidate the trace such it that it will trigger a rebuild.

I actually disagree with this to some extent: It should be fine for lake to cache the failure and assume that re-elaborating the file assuming up to date inputs should produce exactly the same failure. The only complication is that lake would need to buffer and replay the output instead of re-running the compiler. (This is also what cargo does when you re-run a failed build without any source changes.) Changes that would make the build succeed should already be handled by the usual invalidation mechanisms - either the file or its dependencies should need to be changed, and then it will be rebuilt as normal.

The only complication is that lake would need to buffer and replay the output instead of re-running the compiler.

To some lesser degree this is already desirable for non-error diagnostics in successful builds

drafting pending RFC acceptance


⚠ API - Lens has degraded performance

In 5521b44, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 360 ms

Resolved: API - Lens performance has improved in af3c960 after 6 minutes.


Research making starknet.js available in the shell

Allow interaction with Starknet.js from the Remix IDE terminal section.

dup #177


Jammy - Ubuntu22.04 support ?

This version fails on Jammy because the nfsv4_servicehelper is set to the default idmapd in params, which does not exist in ubuntu.
Is there any view on when Jammy tests are finished and the module is supported?
error:
Error: Systemd start for idmapd failed!
journalctl log for idmapd:
-- No entries --
Error: /Stage[main]/Nfs::Server::Service/Service[idmapd]/ensure: change from 'stopped' to 'running' failed: Systemd start for idmapd failed!
journalctl log for idmapd:
-- No entries --

Hey, are there any differences between 20.04 and 22.04?

Thx for the reply, I will clone, test and get back to you.

I will test it in #157

The patch in #157 works for me at least, but I haven't studied in details if there are any changes between focal and jammy.

This issue can probably be closed now?

Yes, thanks!


Script to create and assign DMWM workflows

Partially fixes #5042 . The second needs a few error handling (dataset not in DBS or phedex...)
@juztas please review
@ticoann is it the right place for this script?

Yes it is the right place

Just updated the acqera for relvals.

Don't merge yet, I'm still cooking a few changes.

Code updated, now one can:

specify a directory to search for templates (will be DMWM or Integration, I still need to update them in another PR)
specify a single template name for creation/assignment
cloning of the official repo is no longer enforced.


False notifications with Inventory Management

When using the transfer/sort/stack buttons in Inventory Management, a bunch of notifications are generated when they shouldn't

Fixed in 1.2.0:
https://modrinth.com/mod/roundaround-pickup-notifications/version/1.2.0+1.19
https://modrinth.com/mod/roundaround-pickup-notifications/version/1.2.0+1.18.2


No checkboxes on feature list from transcriptomics experiment

3.1.118alpha
Other tables have checkboxes.

https://github.com/PATRIC3/p3_web/blob/master/public/js/p3/widget/TranscriptomicsGeneGrid.js#L21
When I  use custom store and turn on selector field, it breaks because it tries to access store before it gets created.
instrumentation.js:20 TypeError: Cannot read property 'getIdentity' of null(…) "TypeError: Cannot read property 'getIdentity' of null     at row (/js/dgrid/List.js:813:20)     at Object.disabled (/js/p3/widget/GridSelector.js:19:34)     at renderInput (/js/p3/widget/GridSelector.js:171:15)     at Object.column.renderHeaderCell (/js/p3/widget/GridSelector.js:203:5)     at eval (/js/dgrid/Grid.js:213:39)     at createRowCells (/js/dgrid/Grid.js:144:6)     at renderHeader (/js/dgrid/Grid.js:201:19)     at inherited (/js/dojo/_base/declare.js:189:30)     at renderHeader (/js/dgrid/extensions/ColumnReorder.js:158:9)     at inherited (/js/dojo/_base/declare.js:189:30)"
One workaround is commenting these two line,
https://github.com/PATRIC3/p3_web/blob/master/public/js/p3/widget/GridSelector.js#L170-L171
Dustin, what do you think?

The same issue is present on protein family and pathway pages.
-Maulik

#1218


Menu does not close after page navigation 🧱

The mobile menu component currently does not close when a menu item is clicked. This requires the user to click the ❌ on the top right of the screen in order to close the menu.
The expected behavior, however, is to close the menu automatically when a menu item is clicked.

Resolved by #153.


Radius parser

WIP packing/parsing of RADIUS packets.

Looks good, it'd be nice to get those line lengths down a bit, but not super important for right now


Editor camera, right click & drag - rotation is unpredictable.

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Windows 10 x64, Godot 3.0 alpha 2
Issue description:
A right click and drag to rotate the editor camera, rotates the camera to unpredictable directions,
Steps to reproduce:
Right click on your scene to rotate editor camera, while mouse is moving.

When you hold the right mouse button, freelook mouse is enabled (use W/A/S/D/Q/E to move). To pan the camera, hold the middle mouse button and move the mouse.


Create filestore for insight

What this PR does / why we need it:
Sorry for including big changes in this one PR.
Create filestore for insight and...

create List function to get data as insight data points
create GetReports function to get data as report
create Put function to update of create report on filestore

Which issue(s) this PR fixes:
ref #1142
Does this PR introduce a user-facing change?:

NONE

Fix two bugs

Process GetReports or List with daily and dates that straddles months unsuccessfully
When we pass getPointsMonths dates that the next month does not have that day, an infinite loop occurs. Because of this behavior.

/golinter fmt

@nghialv Thanks for your reviews. Fixed them :D

@nghialv Thanks for your review!
Fixed them all :D

@sanposhiho Nice. Thank you. Let me do a review.

@sanposhiho Thanks for your great work. I have just left some nits. Please fix them and let's talk about which data structure should be applied (map or sorted list).

@nghialv Fixed them, thanks :D

@nghialv thanks for your reviews, fixed them.

@sanposhiho Thanks for your great work. I have just left 2 nits.
/lgtm

@sanposhiho Thanks for your great work. I have just left 5 nits.
/lgtm

@nghialv Thanks, fixed them.

@sanposhiho Thank you. Great job!
/lgtm
(Waiting for a approval from one of another dev.)

@sanposhiho Looks pretty neat. A big thank you goes out to you!
/approve


Support for opening_hours

According to taginfo opening_hours currently is used on 121 274 way. One example can be found here: https://www.openstreetmap.org/way/227495652
The implementation for :conditional should be enhanced and add support for the opening_hours tag.

I think, this is also part of #374


Stylelint: Consider switching to a community-maintained config

Maintaining a custom config like this is not easy, especially in the long run.
How about moving to a community-maintained config?
Benefits

Less time spent on dev stack, more time on coding.
A well-tested config means less bugs and pitfalls in the config itself.
Using something close to a community standard improves interoperability and helps new developers read and understand the code more quickly.

Proposal

remove current default config
add stylelint-config-standard for plain CSS (is it necessary at all?)
add stylelint-config-standard-scss for SCSS
keep optional config defining properties order

A quick test in spirit-web resulted in this project-specific .stylelintrc config:
{
  "extends": [
    "stylelint-config-standard-scss",
    "@lmc-eu/stylelint-config/optional"
  ],
  "rules": {
    "indentation": 4,
    "selector-class-pattern": [
      "^lmc-([A-Z][a-zA-Z0-9]*)((--|__)[a-z0-9]+)*$",
      {
        "message": "Expected class selector to be in format `lmc-MyComponent__element`, `lmc-MyComponent--modifier`"
      }
    ]
  }
}

Violated rules were: indentation (we had 4 spaces instead of 2), string-quotes (single quotes were used instead of double quotes), scss/dollar-variable-empty-line-before (blank lines between Sass variable groups needed to be removed), and selector-class-pattern (kebab case against our SUIT CSS naming convention). I kept our indentation, specified custom selector-class-pattern, and gave in to the other rules. But anything may be changed the way we want it.
To be fair, more tests on larger code bases may be necessary to see a bigger picture.
Extending
If we need more strict rules, our config can be extended as we wish in the future. The point is that most of the settings will already be there.

Well, good idea. But I see here one problem in case of updates. Because with those community configuration I need to create new version every time one of those community configuration updates. So there is a chain of updates: stylelint-config-standard -> @lmc-eu/stylelint-config -> projects.
And thoose updates should't be needed or wanted. That is my first concern.
I also do not know what is a better way. Try to push community standards to the teams and project or melt project rules on which are developers used to into this config?
The second variant was used for creation of this config because there was plenty of rules on which we all agreed and were created long time ago.
I see here some parallel with eslint configs. There are also "standard" and "recommended" community versions but also company specific like "airbnb" which extends nothing or "strv" which done it same way.
So this is not only question of how to keep config short and clean but in particular how to maintain it and push changes forward.

This is another point to use what you suggests: https://github.com/lmc-eu/cookie-consent-manager/pull/138


JSON upload for batch and product accepts values for greyed out fields

I created JSON and set flags to true, even they are grayed out and shouldn't be maintainable (because the functions are deactivated)
result is: fields were accepted and changed, see result in UI

@steinso2 is this an important fix for MVP1? it will  require new validation code for something that should not happen by accident...

Even if we only consider the field which is part of the scope of MVP1: "enable expired expiration date", it shouldn't be changeable using json.
We can control it procedural but it has to be clear to all, because I was surprised that it is changeable by json.
In functional requirement we stated;
Only fields used in MVP1 are allowed to be used in json file (procedural control in user manual).
If flags/fields in json has different value than defined in the rules for MVP1, it shall fail from processing and shown in “failed import logs” with the relevant error message
Lets see what the others think


Customisation of drawer icon in Native Base

Please provide a method or some means to edit the menu/drawer icon on the left.
It's too narrow and can't change its color

@chetnadaffodil Please follow customization section of NativeBase docs

Hi, can you please post the code you already used to implement native base drawer ?


SOLR-17492: Introduce recommendations of WAYS of running Solr from small to massive

https://issues.apache.org/jira/browse/SOLR-17492
Description
Addi recommendations of best practices for deploying Solr
Solution
I am starting with my approach, just to get us moving.  I would love the wisdom of the community.  We have many areas where different folks have knowledge, and it's all pretty tribal.   I'd like to get it all written down so folks don't have to relearn the same thing over and over.
Tests
no tests, but do need eye balls!

We have diagrams generated in our Markdown!

Whether you're just getting started with Solr or looking to fine-tune an existing setup, these practical tips and real-world scenarios may help you get the most out of this powerful search platform.
Best Practices for Using Solr
1.Run Solr as a Cluster for Better Performance
Solr works best when deployed as a cluster. Start with at least three nodes for fault tolerance and scalability, and scale horizontally as your needs grow.

Sharding and Replication: Break your data into shards for parallel processing and use replicas for redundancy. A good starting point is two replicas per shard, but adjust this based on your workload.

Optimize Indexing: Carefully plan your schema to ensure efficient indexing and querying. Use dynamic fields and copy fields where appropriate to keep things flexible without overloading your system.

Caching for Speed: Solr provides powerful caching options like query, document, and filter caches. Use these for frequently accessed data to speed up query times significantly.

Tune the JVM: Since Solr is Java-based, JVM tuning is crucial. Adjust heap size to balance memory usage and garbage collection. Monitor GC logs and experiment with policies like G1GC or CMS for optimal performance.

2. Always Use Solr in Cloud Mode
For a robust, scalable setup, Solr Cloud Mode is the way to go. This setup requires ZooKeeper, which manages cluster coordination, leader election, and configuration.

ZooKeeper’s Role: ZooKeeper ensures your Solr cluster runs smoothly by handling shard placement, failover, and configuration changes dynamically.

Backups and Security:
-Always back up your Solr and ZooKeeper data regularly. Use Solr's built-in backup tools or external snapshot mechanisms for safety.
-Secure your cluster with SSL/TLS, and set up role-based access control, ideally with tools like Apache Ranger. If Ranger isn’t an option, manual permissions management works too.

Monitoring is Essential: Keeping an eye on your Solr cluster is crucial for ensuring smooth operations. A great place to start is the Solr Web UI, which provides a user-friendly interface to monitor metrics like query performance, index health, and cache usage. It's easy to use and perfect for quickly spotting any issues. For more advanced needs, you may integrate tools like Prometheus and Grafana for custom dashboards and alerting. However, I should mention that I don’t have direct experience with Prometheus or Grafana specifically when working with Solr.

Using Scenarios: Real-World Applications of Solr
1. Managing Solr for a Large Dataset
I used open-source Solr as a search engine for a mobile app. Instead of interacting with Solr directly, I managed the setup via ZooKeeper APIs. Here’s what that looked like:

Cluster Configuration:
The cluster handled over 100 TB of data spread across 11 physical machines, each running 16 Solr instances.
Sharding and Replication:
Data was stored in shards, with each shard having two replicas to ensure fault tolerance and load balancing.
Data Storage:
Data was stored directly on the local file system, which was a great fit for this use case.
Management Approach:
Instead of accessing Solr directly, I managed the system via ZooKeeper APIs. This approach, even with an embedded ZooKeeper, worked efficiently under heavy load.

2.Using Solr with Cloudera and HDFS
Another scenario involved deploying Solr in a Cloudera ecosystem with HDFS for storage. Here’s what worked and what didn’t:

Cluster Management:
ZooKeeper handled cluster coordination, while Ranger (and previously Sentry) managed permissions.
Challenges:
Occasionally, node failures caused HDFS file locks, which were difficult to resolve without downtime. These required manual fixes and a lot of patience!

If you’ve got questions or need help with something specific, just let me know. I’m happy to share more!


Implement ALLVARS InitPrec for XSTS

For the CFA formalism in the EXPL domain we have an ALLVARS option for the initial precision, that will simply track all variables from the beginning. Sometimes this is useful (especially if programs are deterministic). We could also do this for XSTS, it's not difficult.

Resolved in #99

Resolved in #99


Bot only reclycing?

2016-08-13 02:25:05,149 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 296 space left in bag.
2016-08-13 02:25:16,116 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 296 space left in bag.
2016-08-13 02:25:19,597 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 296 space left in bag.
2016-08-13 02:25:34,989 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 296 space left in bag.

@Frankjensens Can you please post the relevant section of your configuration (default is "configs/config.json")
{
"type": "RecycleItems",
"config": {
"min_empty_space": 15,
"item_filter": {
"Pokeball":       { "keep" : 100 },
"Potion":         { "keep" : 10 },
"Super Potion":   { "keep" : 20 },
"Hyper Potion":   { "keep" : 30 },
"Revive":         { "keep" : 30 },
"Razz Berry":     { "keep" : 100 }
}
}
},

I only acces my bot through this website http://pokemongoup.xyz/ . With this said I am not familiar with any of this and I certainly have no knowledge what so ever of coding.
So this relevant section of my configuration is only aquired with the desktop app or?

We can't provide support for someone else's bot


fix for https://github.com/pagespeed/mod_pagespeed/issues/1623

https://github.com/pagespeed/mod_pagespeed/issues/1623

I signed it!

I signed it!

I signed it!


chore: pinning version of secp256k1

Description
Pin our version of @types/secp256k1 as it has has caused the build to be broken for weeks.

This doesn't seem to have fixed the problem on master? Not sure why

This doesn't seem to have fixed the problem on master? Not sure why


Changes following public Beta launch

Trello card
https://trello.com/c/zZB9Comq/1907-teaching-in-further-education-tife-page-changes
Context
Less content is needed on this page, because FE has it's own site (just launched into private Beta). FE team want to add a line "You don't need a degree to teach in further education." No other new content.
Guidance to review
Do not merge yet.

I think the reduced content makes sense @Tomcowan1 and means that all future content changes (eg bursaries) will only need to be made on the FE site.
One suggested change - link is not quite right. Other than that, happy to approve and then merge when appropriate.

Hi @gemmadallmandfe Huw's happy, as am I. So, when you're ready we're good to merge :-) .


🐛  Check for empty DownsyncObjectTest

Summary
This PR adds validation checking to BindingPolicy regarding the prohibition on an empty DownsyncObjectTest, and updates the statement in the API about how validation errors are reported.
This PR adds this validation in two ways, because the first way does not work and I do not understand why. Hopefully it is some small thing that can be rectified, which is why I have not abandoned it. The first technique adds some validation to the JSON schema for BindingPolicy, but the kube-apiserver accepts this extra validation without complaint but also trashes it so that it has no effect (it empties out the schemas in the array value of the anyOf, so they all trivially validate; the integration test displays the returned CRD, where you can see the trashed schemas). This PR has a second commit which adds checking in the binding controller.
Related issue(s)
Fixes #2500

/cc @waltforme
/cc @vMaroon
/cc @cwiklik

The force-push to adabae73b fixes the validation so that it works, undoes the addition of checking to the binding controller, and adds a note about this prohibition to the user-facing doc (which was not wrong, because it refers the reader to the API, which already states the prohibition).

/lgtm

/cc @pdettori
/cc @clubanderson

/cc @ezrasilvera
/cc @nirrozenbaum

We may need to update docs/content/direct/contributor.md to mention the new integration tests.

/lgtm

/approve


fix: Cherry pick chart change v0.33.x

Fixes #N/A
Description
Templates karpenter-crd charts so that apiserver is able to correctly perform lookups if upgrading/installing to this version with webhooks disabled.
How was this change tested?
Webhook test suite.
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

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 77.815%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
5349

Relevant Lines:
6874

💛  - Coveralls


Task notes do not render correctly inside note references (in the preview)

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[x] Views.  Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[x] Markdown.  Markdown features, such as syntax support and features

Describe the bug
Task notes do not show information (checkbox, prio, due date etc) when embedded in a note reference. I found this in the note preview, haven't tested with publish. Aggravatingly, in another note with the same reference, one of the tasks renders correctly. This persists through reloading the window and restarting VSCode.
To Reproduce
Steps to reproduce the behavior:

Create a task note (call it note A)
[[Link]] to note A from another note B
![[Reference]] to note B from another note C
View the note preview of C

Expected behavior
Link to task note, inside the note reference, shows additional information (checkbox, prio, due date, etc) beyond just the name.
Screenshots
If applicable, add screenshots to help explain your problem.
Preview of a note reference showing the bugged links:

A note reference in a different file renders one of the tasks but not the others:

Referenced note seems to render correctly on its own:

Desktop (please complete the following information)

OS: Windows 11 (Windows_NT x64 10.0.22000)
Browser (if with published websites; include version): [e.g. chrome, safari]
Versions (all that apply to bug):

Dendron Extension: 0.113.1
VS Code version: 1.71.2
Dendron CLI:

Additional context
Frontmatter of the first task in the screenshots:
---
id: 0xquc81kkfnp64r365ilg75
title: Roommate Agreement
desc: ''
updated:<PHONE_NUMBER>382
created:<PHONE_NUMBER>058
status: ''
due: '2022-09-16T17:00'
priority: high
owner: ''
---

Frontmatter of the third one which is rendering correctly in the second screenshot:
---
id: 5w5h59su9rlw13iwyemhkfq
title: 582 Homework 1
desc: ''
updated:<PHONE_NUMBER>334
created:<PHONE_NUMBER>029
status: w
due: '2022-09-26T23:59'
priority: high
owner: ''
---

Dendron Log file
Please attach the output of > Dendron:Dev: Open Logs here
dendron.log

Thanks @samuelxyz for reporting the bug 🙏 . We'll investigate and report here when the fix is out

This should be fixed after Dendron v0.116. Feel free to comment here if this is still an issue.


Feature Request: Toggle Trade Notifications

Similar to issue #120
Owner command to turn on / off chat notifications of a trade received.
Example command naming:
!TradeNotificationsOn
!TradeNotificationsOff

Same as #120


Some trash modules need to be removed

I got some trash modules when I trying search react on The Party Modules page. https://deno.land/x?query=react
Could you remove these trash modules?
BTW, do you have any solution to prevent more trash landing on Deno?

This has been resolved.


taterclient-ddnet: init at 8.6.0

Add the package taterclient-ddnet.
This is a DDNet-based client that is very popular and used in the community.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 346206 run on x86_64-linux 1

1 package built:

taterclient-ddnet

Result of nixpkgs-review pr 346206 run on aarch64-darwin 1

Result of nixpkgs-review pr 346206 run on aarch64-darwin 1

For some reason nixpkgs-review doesn't detect the new package on darwin?
Anyway, both ddnet and this package build fine, but don't start because theey both try to load libsteam_api.dylib:
dyld[28513]: Library not loaded: /nix/store/9qcrq72n5qvfx1skajjnw4067bsv2d5c-ddnet-18.4/lib/libsteam_api.dylib
  Referenced from: <8FFD8DC0-2313-3485-9855-CB77FB0F038F> /nix/store/9qcrq72n5qvfx1skajjnw4067bsv2d5c-ddnet-18.4/bin/DDNet
  Reason: tried: '/nix/store/9qcrq72n5qvfx1skajjnw4067bsv2d5c-ddnet-18.4/lib/libsteam_api.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/nix/store/9qcrq72n5qvfx1skajjnw4067bsv2d5c-ddnet-18.4/lib/libsteam_api.dylib' (no such file), '/nix/store/9qcrq72n5qvfx1skajjnw4067bsv2d5c-ddnet-18.4/lib/libsteam_api.dylib' (no such file), '/usr/local/lib/libsteam_api.dylib' (no such file), '/usr/lib/libsteam_api.dylib' (no such file, not in dyld cache)
fish: Job 1, 'result/bin/DDNet' terminated by signal SIGABRT (Abort)

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 346206

x86_64-linux

:white_check_mark: 3 packages built:

ddnet
ddnet-server
taterclient-ddnet

I noticed that the .desktop file points at the wrong binary (Exec=DDNet %u) and also has a name that conflicts with DDNet (share/applications/ddnet.desktop )

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 346206

x86_64-linux

:white_check_mark: 3 packages built:

ddnet
ddnet-server
taterclient-ddnet


Pinch to zoom doesn't work under Linux

Reported by @rade.

Chrome / FF not responding to pinch to zoom gesture under Linux. It should zoom in / out on the node canvas.
Works under OSX but the sensitivity is very low.

Interestingly this does work with my track pad, but not my touch screen. And Google Maps is similarly affected. I suspect this is a driver issue, and not in fact a Scope bug.


Decimal literals with underscores

As requested by @xymus in PR #1588, the support of underscores in decimal literals is added to the parser in this PR

Cool! :shipit: !

I think that the strip_underscore is unnecessary and that to_i should deals with the various integer representation.
But this improve the complexity of everything so +1 for the current PR as an additional step towards this goal.


[DO_NOT_MREGE] Enhance dependent UCJs reput

Ref

https://nanopay.atlassian.net/browse/NP-5455

Changes

Load dependent UCJs right before reput
Do not reput dependent UCJs already being GRANTED
Fix failure to lookup existing ucj when system is updating the status of the ucj for capability with associatedEntity=REAL_USER

Closed, no longer relevant.


add note to the README.md

explain that an ECR repository will be created, if one doesn't already exist, as this may not be expected or obvious behaviour

Good point! Do you think it's worth making this an option one day?

An option might make it more explicit and less magic, but it was actually super handy, I liked that it created the repo. What was confusing on the first run was this error message:
An error occurred (RepositoryNotFoundException) when calling the DescribeRepositories operation

So I thought I'll go create one, but there it was!


Hide just one y-axes out of 3 in the grouped bar chart

I have a grouped bar chart, 3 columns for each group.
Can I hide only one y-axe column out of 3 but still show the hidden column's data in the tooltip?
This is my code:
`$.ajax({
type: 'GET',
url: "data/recoverability.json",
dataType: "json",
success: function( response ) {
var datascource = response;
BarChartGroupedLoad(datascource);
},
error: function (textStatus, errorThrown) {
console.log("Error with json data");
}
});
function BarChartGroupedLoad(jsonData) {
var chartjsValues = [];
var chartjsLabels = [];
var chartjsMonths = [];

chartjsMonths = jsonData.months;

for (var i = 0; i < jsonData.dataset.length; i++) {
	var d = {};

	d.data = jsonData.dataset[i].data;
	d.label = jsonData.dataset[i].label
	d.backgroundColor = jsonData.dataset[i].backgroundColor

	chartjsValues.push(d);
}

var barChart = $("#barChart-grouped");

var myChart = new Chart(barChart, {
	type: 'bar',
	data: {
		labels: chartjsMonths,
		datasets: chartjsValues
	},
	options: {
		scales: {
			yAxes: [{
				ticks: {
					beginAtZero:true
				}
			}]
		},
		tooltips: {
			mode: 'index'
		}
	}
});

}`
This is json:
{   "months": ["April 2017","May 2017","June 2017","July 2017","August 2017","September 2017"],   "dataset": [     {      "label":"worked",       "data": [1020,495,875,325,225,3120], 	  "backgroundColor": "#8cd1f3"     },     { 	  "label":"net-revenue",       "data": [1100,0,875,325,225,3050], 	  "backgroundColor": "#d6dade"     },     { 	  "label":"difference",       "data": [80,-495,0,0,0,-70], 	  "backgroundColor": "#f4f4f4"     }   ] }

@sashkanz so you want to hide one of the bars, but still show it in the tooltip?

@etimberg that's correct, hide 1 out of 3 in each group but show all of them in the tooltip.

@sashkanz I don't think there is a good way to do that unfortunately. The tooltip never receives the items that are from hidden datasets. You could modify https://github.com/chartjs/Chart.js/blob/master/src/core/core.interaction.js#L32 to not check if the dataset is visible or not

Closing as there is currently no way to avoid this and for the majority of charts it doesn't make sense to include hidden datasets. Modifying the code above is the best way to achieve this


Allow additional properties in ‘placeholder’ formats…

This eases the migration by allowing publishing
apps to send all required data to the publishing
api, without actually making the switch to the
new format.

We're going to do this differently.