issue with make command

Note:  this project uses git submodules in the source tree.
if you haven't already, run the following command from
the project's root directory:
       git submodule update --init

-- distro ID:       Ubuntu
-- distro version:  18.04
-- distro codename: bionic
-- using patched FindCUDA.cmake
-- CUDA version: 10.2
-- CUDA 10.2 detected (aarch64), enabling SM_53 SM_62
-- CUDA 10.2 detected (aarch64), enabling SM_72
-- system arch:  aarch64
-- output path:  /home/global/jetson-inference/build/aarch64
-- BUILD_EXPERIMENTAL disabled
-- Copying /home/global/jetson-inference/c/depthNet.h
-- Copying /home/global/jetson-inference/c/detectNet.h
-- Copying /home/global/jetson-inference/c/imageNet.h
-- Copying /home/global/jetson-inference/c/poseNet.h
-- Copying /home/global/jetson-inference/c/segNet.h
-- Copying /home/global/jetson-inference/c/tensorConvert.h
-- Copying /home/global/jetson-inference/c/tensorNet.h
-- Copying /home/global/jetson-inference/calibration/randInt8Calibrator.h
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- found Qt5Widgets version:  5.9.5
-- found Qt5Widgets defines:  -DQT_WIDGETS_LIB;-DQT_GUI_LIB;-DQT_CORE_LIB
-- found Qt5Widgets library:  Qt5::Widgets
-- found Qt5Widgets include:  /usr/include/aarch64-linux-gnu/qt5/;/usr/include/aarch64-linux-gnu/qt5/QtWidgets;/usr/include/aarch64-linux-gnu/qt5/QtGui;/usr/include/aarch64-linux-gnu/qt5/QtCore;/usr/lib/aarch64-linux-gnu/qt5//mkspecs/linux-g++
-- camera-capture:  building as submodule of /home/global/jetson-inference/tools
-- jetson-utils:  building as submodule, /home/global/jetson-inference
-- NVMM zero-copy memory:  ENABLE_NVMM=ON
-- Copying /home/global/jetson-inference/utils/URI.h
-- Copying /home/global/jetson-inference/utils/XML.h
-- Copying /home/global/jetson-inference/utils/alphanum.h
-- Copying /home/global/jetson-inference/utils/commandLine.h
-- Copying /home/global/jetson-inference/utils/csvReader.h
-- Copying /home/global/jetson-inference/utils/csvWriter.h
-- Copying /home/global/jetson-inference/utils/filesystem.h
-- Copying /home/global/jetson-inference/utils/logging.h
-- Copying /home/global/jetson-inference/utils/mat33.h
-- Copying /home/global/jetson-inference/utils/pi.h
-- Copying /home/global/jetson-inference/utils/rand.h
-- Copying /home/global/jetson-inference/utils/timespec.h
-- Copying /home/global/jetson-inference/utils/csvReader.hpp
-- Copying /home/global/jetson-inference/utils/csvWriter.hpp
-- Copying /home/global/jetson-inference/utils/json.hpp
-- Copying /home/global/jetson-inference/utils/camera/gstCamera.h
-- Copying /home/global/jetson-inference/utils/camera/v4l2Camera.h
-- Copying /home/global/jetson-inference/utils/codec/gstBufferManager.h
-- Copying /home/global/jetson-inference/utils/codec/gstDecoder.h
-- Copying /home/global/jetson-inference/utils/codec/gstEncoder.h
-- Copying /home/global/jetson-inference/utils/codec/gstUtility.h
-- Copying /home/global/jetson-inference/utils/codec/nvbuf_utils.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaBayer.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaColormap.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaColorspace.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaCrop.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaDraw.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaFilterMode.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaFont.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaGrayscale.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaMappedMemory.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaMath.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaNormalize.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaOverlay.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaPointCloud.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaRGB.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaResize.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaUtility.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaVector.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaWarp.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaYUV.h
-- Copying /home/global/jetson-inference/utils/cuda/cudaAlphaBlend.cuh
-- Copying /home/global/jetson-inference/utils/cuda/cudaFilterMode.cuh
-- Copying /home/global/jetson-inference/utils/display/glBuffer.h
-- Copying /home/global/jetson-inference/utils/display/glCamera.h
-- Copying /home/global/jetson-inference/utils/display/glDisplay.h
-- Copying /home/global/jetson-inference/utils/display/glEvents.h
-- Copying /home/global/jetson-inference/utils/display/glTexture.h
-- Copying /home/global/jetson-inference/utils/display/glUtility.h
-- Copying /home/global/jetson-inference/utils/display/glWidget.h
-- Copying /home/global/jetson-inference/utils/image/imageFormat.h
-- Copying /home/global/jetson-inference/utils/image/imageIO.h
-- Copying /home/global/jetson-inference/utils/image/imageLoader.h
-- Copying /home/global/jetson-inference/utils/image/imageWriter.h
-- Copying /home/global/jetson-inference/utils/image/loadImage.h
-- Copying /home/global/jetson-inference/utils/image/imageFormat.inl
-- Copying /home/global/jetson-inference/utils/input/devInput.h
-- Copying /home/global/jetson-inference/utils/input/devJoystick.h
-- Copying /home/global/jetson-inference/utils/input/devKeyboard.h
-- Copying /home/global/jetson-inference/utils/network/Endian.h
-- Copying /home/global/jetson-inference/utils/network/IPv4.h
-- Copying /home/global/jetson-inference/utils/network/NetworkAdapter.h
-- Copying /home/global/jetson-inference/utils/network/Socket.h
-- Copying /home/global/jetson-inference/utils/threads/Event.h
-- Copying /home/global/jetson-inference/utils/threads/Mutex.h
-- Copying /home/global/jetson-inference/utils/threads/Process.h
-- Copying /home/global/jetson-inference/utils/threads/RingBuffer.h
-- Copying /home/global/jetson-inference/utils/threads/Thread.h
-- Copying /home/global/jetson-inference/utils/threads/Event.inl
-- Copying /home/global/jetson-inference/utils/threads/Mutex.inl
-- Copying /home/global/jetson-inference/utils/threads/RingBuffer.inl
-- Copying /home/global/jetson-inference/utils/video/videoOptions.h
-- Copying /home/global/jetson-inference/utils/video/videoOutput.h
-- Copying /home/global/jetson-inference/utils/video/videoSource.h
-- trying to build Python bindings for Python versions:  2.7;3.6;3.7
-- detecting Python 2.7...
-- found Python version:  2.7 (2.7.17)
-- found Python include:  /usr/include/python2.7
-- found Python library:  /usr/lib/aarch64-linux-gnu/libpython2.7.so
-- CMake module path:  /home/global/jetson-inference/utils/cuda;/home/global/jetson-inference/utils/python/bindings
-- NumPy ver. 1.13.3 found (include: /usr/lib/python2.7/dist-packages/numpy/core/include)
-- found NumPy version:  1.13.3
-- found NumPy include:  /usr/lib/python2.7/dist-packages/numpy/core/include
-- detecting Python 3.6...
-- found Python version:  3.6 (3.6.5)
-- found Python include:  /usr/local/include/python3.6m
-- found Python library:  /usr/local/lib/libpython3.6m.a
-- CMake module path:  /home/global/jetson-inference/utils/cuda;/home/global/jetson-inference/utils/python/bindings
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'numpy'
-- NumPy not found
-- detecting Python 3.7...
-- Python 3.7 wasn't found
-- Copying /home/global/jetson-inference/utils/python/examples/camera-viewer.py
-- Copying /home/global/jetson-inference/utils/python/examples/cuda-examples.py
-- Copying /home/global/jetson-inference/utils/python/examples/cuda-from-cv.py
-- Copying /home/global/jetson-inference/utils/python/examples/cuda-from-numpy.py
-- Copying /home/global/jetson-inference/utils/python/examples/cuda-to-cv.py
-- Copying /home/global/jetson-inference/utils/python/examples/cuda-to-numpy.py
-- Copying /home/global/jetson-inference/utils/python/examples/gl-display-test.py
-- Copying /home/global/jetson-inference/utils/python/examples/video-viewer.py
-- trying to build Python bindings for Python versions:  2.7;3.6;3.7
-- detecting Python 2.7...
-- found Python version:  2.7 (2.7.17)
-- found Python include:  /usr/include/python2.7
-- found Python library:  /usr/lib/aarch64-linux-gnu/libpython2.7.so
-- CMake module path:  /home/global/jetson-inference/utils/cuda;/home/global/jetson-inference/python/bindings;/home/global/jetson-inference/python/bindings/../../utils/python/bindings
-- NumPy ver. 1.13.3 found (include: /usr/lib/python2.7/dist-packages/numpy/core/include)
-- found NumPy version:  1.13.3
-- found NumPy include:  /usr/lib/python2.7/dist-packages/numpy/core/include
-- detecting Python 3.6...
-- found Python version:  3.6 (3.6.5)
-- found Python include:  /usr/local/include/python3.6m
-- found Python library:  /usr/local/lib/libpython3.6m.a
-- CMake module path:  /home/global/jetson-inference/utils/cuda;/home/global/jetson-inference/python/bindings;/home/global/jetson-inference/python/bindings/../../utils/python/bindings
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'numpy'
-- NumPy not found
-- detecting Python 3.7...
-- Python 3.7 wasn't found
-- Copying /home/global/jetson-inference/python/examples/depthnet.py
-- Copying /home/global/jetson-inference/python/examples/depthnet_utils.py
-- Copying /home/global/jetson-inference/python/examples/detectnet-snap.py
-- Copying /home/global/jetson-inference/python/examples/detectnet.py
-- Copying /home/global/jetson-inference/python/examples/imagenet.py
-- Copying /home/global/jetson-inference/python/examples/my-detection.py
-- Copying /home/global/jetson-inference/python/examples/my-recognition.py
-- Copying /home/global/jetson-inference/python/examples/posenet.py
-- Copying /home/global/jetson-inference/python/examples/segnet.py
-- Copying /home/global/jetson-inference/python/examples/segnet_utils.py
-- Configuring done
-- Generating done
-- Build files have been written to: /home/global/jetson-inference/build
[ 38%] Built target jetson-utils
[ 51%] Built target jetson-inference
[ 53%] Built target imagenet
[ 55%] Built target imagenet-console
[ 56%] Built target imagenet-camera
[ 57%] Built target depthnet
[ 59%] Built target detectnet-camera
[ 60%] Built target detectnet
[ 61%] Built target detectnet-console
[ 63%] Built target posenet
[ 65%] Built target segnet-camera
[ 66%] Built target segnet
[ 67%] Built target segnet-console
[ 68%] Automatic MOC for target camera-capture
[ 68%] Built target camera-capture_autogen
[ 72%] Built target camera-capture
[ 74%] Built target camera-viewer
[ 76%] Built target video-viewer
[ 78%] Built target gl-display-test
[ 84%] Built target jetson-utils-python-27
[ 84%] Linking CXX shared library ../../../aarch64/lib/python/3.6/jetson_utils_python.so
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(abstract.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_add_one_to_index_F' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(abstract.o): In function PyBuffer_FromContiguous':
/tmp/Python-3.6.5/Objects/abstract.c:502:(.text+0x1aa4): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(abstract.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_add_one_to_index_C' which may bind externally can not be used when making a shared object; recompile with -fPIC /tmp/Python-3.6.5/Objects/abstract.c:502:(.text+0x1aa8): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(typeobject.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol PyType_GenericAlloc' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(typeobject.o): In function type_new': /tmp/Python-3.6.5/Objects/typeobject.c:2681:(.text+0x10974): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord': /tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x5fa4): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_ExtendedCase' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToTitlecase': /tmp/Python-3.6.5/Objects/unicodectype.c:69:(.text+0x5fc8): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord': /tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x600c): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x605c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x60ac): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToDecimalDigit': /tmp/Python-3.6.5/Objects/unicodectype.c:110:(.text+0x60fc): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord': /tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x6154): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToDigit': /tmp/Python-3.6.5/Objects/unicodectype.c:127:(.text+0x61a4): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord': /tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x61fc): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x624c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x629c): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x62ec): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x633c): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x638c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_ExtendedCase' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToUppercase':
/tmp/Python-3.6.5/Objects/unicodectype.c:195:(.text+0x63b4): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord':
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x63fc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_ExtendedCase' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToLowercase':
/tmp/Python-3.6.5/Objects/unicodectype.c:207:(.text+0x6420): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord':
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x6470): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_ExtendedCase' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToLowerFull':
/tmp/Python-3.6.5/Objects/unicodectype.c:220:(.text+0x64b0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord':
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x6528): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_ExtendedCase' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToTitleFull':
/tmp/Python-3.6.5/Objects/unicodectype.c:236:(.text+0x6568): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord':
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x65e0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_ExtendedCase' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToUpperFull':
/tmp/Python-3.6.5/Objects/unicodectype.c:252:(.text+0x6624): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord':
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x6698): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_ExtendedCase' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToLowerFull':
/tmp/Python-3.6.5/Objects/unicodectype.c:220:(.text+0x66dc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_ExtendedCase' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function _PyUnicode_ToFoldedFull':
/tmp/Python-3.6.5/Objects/unicodectype.c:268:(.text+0x6728): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(unicodectype.o): In function gettyperecord':
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x677c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC /tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x67cc): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(unicodectype.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _PyUnicode_TypeRecords' which may bind externally can not be used when making a shared object; recompile with -fPIC
/tmp/Python-3.6.5/Objects/unicodectype.c:55:(.text+0x681c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_setresgid':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:5173:(.text+0x293c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Uid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_setresuid':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:5139:(.text+0x29f4): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function posix_initgroups':
/tmp/Python-3.6.5/./Modules/posixmodule.c:6213:(.text+0x4b0c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_setregid':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:2789:(.text+0x4bf4): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_setegid':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:2724:(.text+0x4ca8): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_setgid':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:2821:(.text+0x4d50): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Uid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_setreuid':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:2756:(.text+0x4df4): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Uid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_seteuid':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:2693:(.text+0x4ea8): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Uid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_setuid':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:2662:(.text+0x4f50): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_fchown':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:741:(.text+0x66c4): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Uid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:741:(.text+0x66c8): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(posixmodule.o): In function posix_getgrouplist': /tmp/Python-3.6.5/./Modules/posixmodule.c:6033:(.text+0x7b1c): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_lchown': /tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:780:(.text+0xa3a4): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Uid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:780:(.text+0xa3bc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Gid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libpython3.6m.a(posixmodule.o): In function os_chown':
/tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:700:(.text+0xb038): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.6m.a(posixmodule.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol _Py_Uid_Converter' which may bind externally can not be used when making a shared object; recompile with -fPIC /tmp/Python-3.6.5/./Modules/clinic/posixmodule.c.h:700:(.text+0xb088): dangerous relocation: unsupported relocation /usr/bin/ld: /usr/local/lib/libpython3.6m.a(myreadline.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol PyOS_StdioReadline' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.6m.a(myreadline.o): In function `PyOS_Readline':
/tmp/Python-3.6.5/Parser/myreadline.c:319:(.text+0x43c): dangerous relocation: unsupported relocation
collect2: error: ld returned 1 exit status
utils/python/bindings_python_3.6/CMakeFiles/jetson-utils-python-36.dir/build.make:257: recipe for target 'aarch64/lib/python/3.6/jetson_utils_python.so' failed
make[2]: *** [aarch64/lib/python/3.6/jetson_utils_python.so] Error 1
CMakeFiles/Makefile2:1130: recipe for target 'utils/python/bindings_python_3.6/CMakeFiles/jetson-utils-python-36.dir/all' failed
make[1]: *** [utils/python/bindings_python_3.6/CMakeFiles/jetson-utils-python-36.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

See https://github.com/dusty-nv/jetson-inference/issues/1441#issuecomment-1157814067


[Docs] Tutorial section on how users can take this library and setup a simple one page webapp

We should provide documentation on getting started with this library for new users.

A quickstart for setting up a one page app from scratch has been added, see here.


A little change for the cdn redirection.

My ISP take the cdn  for local network.The resource always be redirected the cdn server.It must be make a new connection by the connect-url.

quicklisp-client/quicklisp/http.lisp should be modify,please.


Create Early Adopter "Package" Artifact Listing

Describe the issue
We will be looking to on-board early adopter candidates soon for the MVP & conduct a series of workshops & need to put together a list of artifacts to be included in the package
Which Sprint Priority is this issue related to?
Milestone 14
Additional context
Add any other context, attachments or screenshots
Definition of done

List of artifacts captured
Teams workspace, wiki, link to all the pieces
Reviewed by CP team & PO

Created the "Early Adopter Program" channel as well as starting a wiki with placeholders for content


CTECH-1552: Adds whitespace to check forked PR flow.

Signed-off-by: Paul Saunders<EMAIL_ADDRESS>Pull Request Checklist

[x] Read the contributing guidelines
[x] Tests pass

Description of the PR
A test to ensure that the forked PR flow works.  This PR should be closed and not merged once proven to work.

/LGTM

/LGTM

all good now. closing.


Component stubs stop working for grand children when registered globally

Version
1.0.0-beta.20
Reproduction link
https://codesandbox.io/s/7krlyqn310
Steps to reproduce

Have a look at the TestComponent.spec.js
See how the stub for the child component works correctly and the test passes
See how the stub for the grand child component does not work and the test fails

What is expected?
The test for the grand child should pass as it was stubbed.
What is actually happening?
The test fails because the stub does not apply.

This only seems to be an issue with components that are registered globally. The error did not occur when the sub-componentes were registered locally.
We experienced this bug when we upgraded from beta.16 to beta.20. The transition component which is stubbed per default suddenly stopped working in nested components.

I think the reason this is happening is because at the moment stubs only works on the direct children, not the children's children.  I didn't know this was even working in previous versions.
One work around is to use find and pass the component:
expect(wrapper.find(GrandChildComponent).exists()).toBe(true)

Or you simply pass an object with a name property:
expect(wrapper.find({ name: "grand-child-component" }).exists()).toBe(true);

Maybe related to #649 - a 'dive' or depth API might let you stub on varying levels or depths.

This is a bug, stubs should be applied to all child components

This actually is a problem with how you're stubbing.
First you were using Vue Test Utils beta.16 which would stop circular references, because the class had the name of the component it would throw an error (this has been fixed to only throw if the component name is the same).
Second, you were trying to find the element using a -stub suffix on the class, which is not added when it's stubbed.
Third, the TestComponent wasn't rendering the ChildComponent.
I've added these fixes to your code sample: https://codesandbox.io/s/jpo3lo2569.
There's a passing test for stubbing nested components in the Vue Test Utils—https://github.com/vuejs/vue-test-utils/blob/dev/test/specs/mounting-options/stubs.spec.js#L135

Thanks for having a look at the issue and providing a solution. But I think I am missing something from your fixed code sample: There are two console logs in the test runs which show the html generated for the components.
In the first test you can see that the child component stub is applied (div.child-component-class exists).
In the second test you can see that the grand child component stub is not applied. The generated html still shows a div with the text "I am the grand child". If the stub would be applied then it should be replaced by a div.grand-child-component with no content. Thats what I was originally testing for.
Clarification on that would be appreciated :)

Sorry, yes this is in fact a bug.

This is fixed in master, and will be included in the next release.
For now, a quick solution is to use localVue:
import { createLocalVue } from '@vue/test-utls'

const localVue = createLocalVue()
localVue.component('child-component', Child)
mount(TestComponent, {
  localVue
})

Hello,
is this solved?
When I try to use a grandchild component,
which is defined in his father, I get the error saying if the component has been registered correctly.
Thank you,
Regards,

@Igor-Dataka and anyone else that ran into this problem and got taken to this GitHub issue via search engines: It doesn't seem that vue-test-utils supports a situation where the child component contains a dynamic <component> that can render into a <router-link> but the above solution is sufficient to resolve the issue.
import { describe, expect, jest, it } from '@jest/globals';
import { createLocalVue, mount, RouterLinkStub } from '@vue/test-utils';

import MyComponent from './MyComponent';

describe('MyComponent component', () => {
  it('renders with default props', () => {
    const localVue = createLocalVue();
    localVue.component('router-link', RouterLinkStub);

    const wrapper = mount(MyComponent, {
      localVue
    });

    expect(true);
  });

Yeah, I don't think this is supported. Stubs are applied before the runtime, so I suspect that's the reason - the stubs are applied before the dynamic behavior.
I have found that writing unit tests around routing logic is generally brittle and generates more work/maintenance then value, I generally recommend against unit testing that sort of thing.


"on ()" keyword ignored in alert IF statement when loaded from rules file

What did you do?
I added lines similar to the following (one recording rule, multiple alerts) to my rules file and restarted my Prometheus server:
workhours=day_of_week() < bool 6 * hour() >= bool 13 * hour() < bool 22
ALERT rateAlert_server_datafeed
IF rate(server_datafeed[10m]) == 0 and on () workhours == 1
LABELS { topic = "datafeed", }
ANNOTATIONS {
summary = "Topic datafeed on {{ $labels.job }} has not received a message for at least 10 minutes",
subject = "No messages for topic datafeed on {{ $labels.job }}",
}
What did you expect to see?
On the Prometheus Status|Rules page I expected to see something like this:
workhours{} = day_of_week() < BOOL 6 * hour() >= BOOL 13 * hour() < BOOL 22
ALERT rateAlert_server_datafeed
IF rate(server_datafeed[10m]) == 0 and on () workhours == 1
LABELS {topic="datafeed"}
ANNOTATIONS {subject="No messages for topic datafeed on {{ $labels.job }}", summary="Topic datafeed on {{ $labels.job }} has not received a message for at least 10 minutes"}
What did you see instead? Under which circumstances?
On the Prometheus Status|Rules page I saw something like this with the IF statement missing the "on ()" keyword:
workhours{} = day_of_week() < BOOL 6 * hour() >= BOOL 13 * hour() < BOOL 22
ALERT rateAlert_server_datafeed
IF rate(server_datafeed[10m]) == 0 and workhours == 1
LABELS {topic="datafeed"}
ANNOTATIONS {subject="No messages for topic datafeed on {{ $labels.job }}", summary="Topic datafeed on {{ $labels.job }} has not received a message for at least 10 minutes"}
Environment

System information:

Linux 2.6.32-358.el6.x86_64 x86_64

Prometheus version:

prometheus, version 1.2.1 (branch: master, revision: dd66f2e94b2b662804b9aa1b6a50587b990ba8b7)
build user:       root@fd9b0daff6bd
build date:       20161010-15:58:23
go version:       go1.7.1

Alertmanager version:

Prometheus configuration file:

Alertmanager configuration file:

Logs:

The issue is that the printer only shows vector matching related keywords if any matching labels are provided. I guess we'll need a way to indicate whether a field was set, bool pointers or an additional field come to my mind.


Render time issue

Hi, thanks for your work on this project! Very helpful & easy to use.
I had a question on rendering time:
I have 50-100 formulas displayed on a page, and it often takes ~5 minutes for all of them to render. For pages with only 1-2 formulas, it usually takes about 5 seconds, but this is also suboptimal as the user can see the unformatted text.
Do you have any suggestions to (a) speed up the render process or (b) prevent displaying until render is complete? (thinking something like Template.subscriptionsReady, where you can display a spinner if not ready).
Thanks!

@arshs It's good to hear that this library is useful. Thanks!
I've been experiencing performance problems with MathJaX as well, and I don't think I have a complete solution/ answer for you. One thing that I would suggest is to use caching:
https://github.com/apendua/meteor-mathjax#caching-formulas
At least when the formula is rendered for the second time, it will be much faster. BTW, have you tried the latest version of MathJaX? I believe they're actively developing the library so there might have been some improvements to rendering times.
Regarding (b), yes it's a good idea to have a "loading" state so that you can display some kind of placeholder while the formula is being rendered. This is not implemented at the moment, but shouldn't be difficult. Would you like to contribute and add this kind of functionality?

Gotcha, thanks for the response. Yes, I'm using mathjax 2.7.0 (will try 2.7.2 now).
Will take a look at what that functionality involves (still new to this); bit backlogged at the moment (isn't everyone...) but will try when i free up.


rocm4.0 extra tuning for SWDEV-250694

Full rocm 4.0 tuning details: https://github.com/ROCmSoftwarePlatform/Tuna/issues/296
This PR addressed Jira:  http://ontrack-internal.amd.com/browse/SWDEV-250694

@daniellowell  this PR's binaries were merged with develop before PR https://github.com/ROCmSoftwarePlatform/MIOpen/pull/612 went in. I will need to merge the binaries - now that https://github.com/ROCmSoftwarePlatform/MIOpen/pull/612 is in develop before we merge this PR. FYI


Annotate single sample output with gnomAD allele frequencies and add BED output

This PR enables annotation of the single sample pipeline's output with gnomAD allele frequencies.
It modifiesmodule07.wdl to optionally annotate the vcf with allele frequencies from an external resource if the right parameters are supplied.
In addition, a version of the single sample pipeline's output is supplied in BED format in addition to VCF.

I didn't update the sv-pipeline docker for this one yet, either -- figured that could be batched with https://github.com/broadinstitute/gatk-sv/pull/36 (and https://github.com/broadinstitute/gatk-sv/pull/26 if it's going to be ready shortly)


[micro-dash] No longer publishing cjs?

I noticed that v13 has only .mjs files and the bundles UMD output is gone. This is problematic because when I run with ts-node, I get:
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module<EMAIL_ADDRESS>
Does anyone know how to solve this?

Good question, and one I'm going to have to deal with at work before we can upgrade Angular 13. s-libs uses the Angular CLI for its buildchain and tooling, and it no longer produces UMD bundles.
I'm afraid I'm not very well versed with ts-node. What version of it are you at? This SO answer says version 10 would fix ... an error someone had that might be relevant?

I saw that SO post as well, but have yet to get ts-node or node-dev to actually work with mjs modules.

Have you looked at https://github.com/TypeStrong/ts-node/issues/1007? I seem to have gotten a little further with it, but it didn't solve everything for me yet. Maybe you'll have more luck?

I briefly attempted to get ts-node to accept the .mjs files in v13 of micro-dash, but no success to report yet. For now I'm sticking with v12 since v13 seems broken as far as Typescript is concerned :(

Found this https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c

Looks like a good resource. Has it helped?

I've started a little hobby project, and was able to consume the .mjs files following the advice at https://github.com/TypeStrong/ts-node/issues/1007. Here's my config:
// package.json
{ "type": "module" }

// tsconfig.json
{
  "compilerOptions": {
    "module": "ESNext",
    "target": "ES2020",
    "types": ["node"],
    "moduleResolution": "node",
    "sourceMap": true
  }
}

And some sample import syntax:
import { property } from '@s-libs/micro-dash';
import * as tf from '@tensorflow/tfjs-node';
import * as fs from 'fs';
import * as readline from 'readline';
import { INPUT_SIZE } from './build-vgg-model.js';
import { ImageInfo } from './image-info.js';

(Note that the last two imports are actually typescript files, but still have the .js suffix. Which is weird, but it's what they say to do 🤷♀.

Just cleaning up a few old, open tickets that don't have action items for me


Updated colab_facets.ipynb to make the atlas_url and sprite feature work using base64 data url.

Problem:
The atlas and sprite feature is missing in the current Colab notebook example.  The atlas_url feature in the current Colab example didn't work directly using local files and regular url.  There is no easy way to pass the image using atlas_url from Colab.
Solution:
The solution is to read image from the file and convert it into base64 string.  Then create a base64 image url from the string and pass the base64 image url directly into atlas_url.
Added new dive example showing the atlas_url and sprite feature.  The notebook works in Colab and is able to show the visualizaiton properly.

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!

Thanks for putting this together @jsiddique . Could you instead put this atlas example in a new ipynb file in the facets_dive directory? I think it makes sense to have it as a standalone Dive example notebook, separate from the simple one at the top-level directory.
After you do that, if its OK with you I might copy the two external files it depends on to our what-if-tool public cloud bucket so that the URLs they point to are connected to the project itself and update the notebook to point to those new URLs. Also perhaps you could add a comment in the notebook about how the atlas image file was created.

@jameswex Thanks for the suggestions.  Based on your comment I have reverted my previous commit and rolled back the changes I made to colab_facets.ipynb.  I have created a new standalone colab Dive example notebook in facets_dive directory.  The name of the file is colab_dive_atlas_demo.ipynb
Also added some comments in the notebook about how the atlas image file was created. Let me know if the changes are OK.
Definitely OK with me to copy the two external files in what-if-tool public cloud bucket. I have updated the notebook to point to those new URLs.

Thanks again @jsiddique . I also added a link to this notebook in the Facets Dive README


Strategy matrix doesn't support excluding some combinations

Currently, Strategy::matrix is defined as a List { mapKey : Text, mapValue : List Text }:
https://github.com/regadas/github-actions-dhall/blob/master/types/Strategy.dhall
However, Github Actions supports having an exclude key that is a list of records (not Text):
https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-excluding-configurations-from-a-matrix
Currently it's not possible to specify an exclude field in the matrix, because it doesn't match the type.

Hi @erwan! Thanks for the report!
Do you feel you can find some time to propose a fix? 😄 🙏

Actually I tried, but I don't know how to fix it! I couldn't find a way to type the exclude field.
It's too generic, we would want a list of objects that can have any key. I couldn't find how to do that in dhall...


fix(tests) JSON fixture was slightly invalid

lol I'm working in local and have this fixed already :)

i'm resolving some more issues then pushing my update


Turn on LED of a scene according to circumstances

Good evening,
I tried to configure a scene switch in a way that the LED of the respective switche turns on in regards of the status of some other entities in Home Assistant.
For example: If a light is turned on in the house, the switch turns on the white led an if all is off it turns off again.
Is there a possibility to get that working in an easy way?
The only thing i found out so far is that i could put a different config to the device but i couldn't figure out if i can change only a single part of the config. If i have to put a whole config, can i store a config somewhere and call it up?

If a SmartButton triggers a job, and the job contains "flag_values", the LED of the SmartButton lights up depending on the flag state.
Create your own SystemFlag
POST /api/system/flags {"symbol": "dancing", "value": true, "name": "Party"}
Add your SystemFlag to your job which is called by the SmartButton.
PUT /api/jobs/{job_id} {"flag_values": [{"flag": {flag_id}, "value": true}]}
When you press the SmartButton it's party time and the LED lights up.
You can end the party with another job "value": false or with PATCH /api/system/flags/{id} {"value": false}


mime/multipart: CreateFormFile defaults content-type to application/octet-stream

What version of Go are you using (go version)?

$ go version 1.11.5

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/melissazhang/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/melissazhang/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.11.5/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.11.5/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/melissazhang/src/babel-fish/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/bx/54d6qfbs7g19jps4b60rnkq00000gp/T/go-build334342869=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
createFormFile always defaults content type to application/octet-stream which is not always the case.
What did you expect to see?
Should allow you to customize or it should detect the content type
What did you see instead?
Defaults to application/octet-stream

You can use CreatePart which lets you customize it however you like.  CreateFormField is a convenience function.  (And I don't see where CreateFormField sets the Content-Type at all.)

@ianlancetaylor this is where content-type is set https://github.com/golang/go/blob/master/src/mime/multipart/writer.go#L145

That is CreateFormFile.  You filed this bug against CreateFormField.

@ianlancetaylor nice catch! updated

OK.  But it's still true that CreateFormFile is just a simple wrapper around CreatePart.  We can't really change CreateFormFile without breaking the Go 1 compatibility guarantee (https://golang.org/doc/go1compat).

/cc @bradfitz just in case you want to weigh in. It sounds like this should be closed, based on the feedback from @ianlancetaylor on this issue.

Yeah, I agree with Ian. We can't break compatibility and it's already possible to set other content-types with the other methods.


Firmware problems using SR300 Development Kit

I purchased the SR300 Development kit online through this link:
http://click.intel.com/intelrrealsensetm-developer-kit-featuring-sr300.html
I ran into issues after following your install instructions (failed with uvcvideo: Unknown video format errors after running the ./scripts/patch-uvcvideo-16.04.simple.sh).
I cannot load the relevant firmware on it because it is not recognized by the Intel Realsense DCM. I noticed that it comes up in the device manager as "Blaster Senz3D VF0810". Is this a different model entirely from the SR300?
The information online is very sparse, and if I can't even get it recognized by the DCM to upload firmware I am kind of screwed :(

Required Info

Camera Model
SR300 (VF0810)

Firmware Version
Uknown

Operating System & Version
16.04

Kernel Version (Linux Only)
4.4

Build System
N.A.

Hi @HugoCMU
As a starting point could you please share the results of lsusb, ls /sys/class/video4linux and sudo dmesg | tail -n 50. You should be able to see a device with vendor ID 8086 (Intel) and product ID 0aa5 (the SR300).
Not all video formats required by the SR300 has been up-streamed, but ./scripts/patch-uvcvideo-16.04.simple.sh should be able to address that.
I have found a similar issue reported here.
On Windows, do you see any new imaging devices in the device manager when connecting the camera?

I found another Windows 10 computer and I was able to get the camera recognized and the latest firmware v<IP_ADDRESS>37 installed. (Link: https://downloadcenter.intel.com/download/25044/Intel-RealSense-Depth-Camera-Manager). I tested the camera using the Windows SDK and both the depth and color camera are working. (Link: https://software.intel.com/en-us/intel-realsense-sdk/download)
Output of lsusb shows the Creative camera, as well as some USB3.0 hubs.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 005: ID 8086:0aa5 Intel Corp.
Bus 002 Device 004: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 041e:409b Creative Technology, Ltd
Bus 001 Device 006: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 005: ID 093a:2532 Pixart Imaging, Inc.
Bus 001 Device 003: ID 04ca:004b Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of ls /sys/class/video4linux shows 2 video devices. Both of them are Intel Realsense cameras:
$ cat /sys/class/video4linux/video0/name
Intel(R) RealSense(TM) Camera S
$ cat /sys/class/video4linux/video1/name
Intel(R) RealSense(TM) Camera S

The relevant part of the dmesg | tail shows the camera connected, but there is still the unknown video format errors from before:
[317410.113859] usb 2-5: new SuperSpeed USB device number 4 using xhci_hcd
[317410.132677] usb 2-5: New USB device found, idVendor=05e3, idProduct=0616
[317410.132685] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[317410.132689] usb 2-5: Product: USB3.0 Hub
[317410.132693] usb 2-5: Manufacturer: GenesysLogic
[317410.134635] hub 2-5:1.0: USB hub found
[317410.134924] hub 2-5:1.0: 2 ports detected
[317410.993717] usb 1-5.2: new full-speed USB device number 7 using xhci_hcd
[317411.170642] usb 1-5.2: config 1 has an invalid interface number: 3 but max is 2
[317411.170650] usb 1-5.2: config 1 has no interface number 2
[317411.240791] usb 1-5.2: New USB device found, idVendor=041e, idProduct=409b
[317411.240799] usb 1-5.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[317411.240804] usb 1-5.2: Product: BlasterX Senz3D VF0810
[317411.240808] usb 1-5.2: Manufacturer: Creative Technology Ltd
[317411.240811] usb 1-5.2: SerialNumber:<PHONE_NUMBER>34
[317411.385789] input: Creative Technology Ltd BlasterX Senz3D VF0810 as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5.2/1-5.2:1.3/0003:041E:409B.0006/input/input25
[317411.442226] hid-generic 0003:041E:409B.0006: input,hiddev0,hidraw4: USB HID v1.11 Device [Creative Technology Ltd BlasterX Senz3D VF0810] on usb-0000:00:14.0-5.2/input3
[317412.569848] usb 2-5.1: new SuperSpeed USB device number 5 using xhci_hcd
[317412.586698] usb 2-5.1: New USB device found, idVendor=8086, idProduct=0aa5
[317412.586705] usb 2-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[317412.586710] usb 2-5.1: Product: Intel(R) RealSense(TM) Camera SR300
[317412.586714] usb 2-5.1: Manufacturer: Intel(R) RealSense(TM) Camera SR300
[317412.588261] uvcvideo: Found UVC 1.10 device Intel(R) RealSense(TM) Camera SR300 (8086:0aa5)
[317412.590398] input: Intel(R) RealSense(TM) Camera S as /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5.1/2-5.1:1.0/input/input26

[317412.590982] uvcvideo: Unknown video format 435a4e49-b602-480f-978c-e4e88ae89b89
[317412.590989] uvcvideo: Unknown video format 52494150-8536-4841-b6bf-8fc6ffb083a8
[317412.591052] uvcvideo: Found UVC 1.10 device Intel(R) RealSense(TM) Camera SR300 (8086:0aa5)
[317412.592797] uvcvideo: Unable to create debugfs 2-5 directory.
[317412.593021] input: Intel(R) RealSense(TM) Camera S as /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5.1/2-5.1:1.2/input/input27

Re-ran the ./scripts/patch-uvcvideo-16.04.simple.sh script and it seems like the Product name on dmesg has changed, and is now SR300 as opposed to Creative BlasterX Senz3D.
[  172.199012] usb 2-5.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  172.199017] usb 2-5.1: Product: Intel(R) RealSense(TM) Camera SR300
[  172.199021] usb 2-5.1: Manufacturer: Intel(R) RealSense(TM) Camera SR300
[  172.200844] uvcvideo: Found UVC 1.10 device Intel(R) RealSense(TM) Camera SR300 (8086:0aa5)
[  172.203172] input: Intel(R) RealSense(TM) Camera S as /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5.1/2-5.1:1.0/input/input26
[  172.203754] uvcvideo: Unknown video format 435a4e49-b602-480f-978c-e4e88ae89b89
[  172.203762] uvcvideo: Unknown video format 52494150-8536-4841-b6bf-8fc6ffb083a8
[  172.203827] uvcvideo: Found UVC 1.10 device Intel(R) RealSense(TM) Camera SR300 (8086:0aa5)
[  172.205653] uvcvideo: Unable to create debugfs 2-5 directory.
[  172.205935] input: Intel(R) RealSense(TM) Camera S as /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5.1/2-5.1:1.2/input/input27

Hi @HugoCMU , please run "cpp-enumerate" demo and send the camera FW version: e.g.
"Device 0 - Intel RealSense SR300:
Serial number:<PHONE_NUMBER>54
Firmware version: <IP_ADDRESS>
USB Port ID: \.\USB#VID_0424&PID_5..."
The unrecognized formats that you see in dmesg log are additinal SR300 formats used exclusively during production activities, and are not publicly available.
We still need to understand why these descriptors haven't been removed correctly in your case, but other than dmesg warnings, it should not impact camera operation -  and you should be able to stream depth, infrared and color as advertised.
Please check and update.

The firmware version is as follows:
Device 0 - Intel RealSense SR300:
 Serial number:<PHONE_NUMBER>97
 Firmware version: <IP_ADDRESS>
 USB Port ID: 2-1

The output of the  SR300-live-test script shows all of the tests passing, although there seems to be different results when run consecutively though...
All tests passed (39291 assertions in 42 test cases)

Hello,
Our lab brought new Blaster-X sensz3D camera. After lots of struggle found the this camera not support linux. But, successfully access the camera using gstreamer.
Does any have any working solution to access the camera in Opencv or ROS.


Trying to receive SDO messages in SDO client over the CO_SDOclient_receive

Hi, I am trying to receive messages over the RXFIFO in the SDO client, but every time a message is comming the function rejects its due to the SDO_C->state is in CO_SDO_ST_IDLE. How I can change this state, there is some function that I need to configure for starting receiving data?
Maybe I need to configure CO_SDOclientDownloadInitiate or CO_SDOclientUploadInitiate?
if (SDO_C->state != CO_SDO_ST_IDLE && DLC == 8U
&& (!CO_FLAG_READ(SDO_C->CANrxNew) || data[0] == 0x80)
) {

SDO client is complex, please read the docs or see CANopenLinux for implementation. Or try to use PDO instead SDO.

Hi, In this case I need to configure such a 50 SDOs in the CANopen bus between two devices. I am using an STM32 microcontroller with RTOS (no S.O Linux). Could you tell me, where the docs are?

CO_SDOclient.h contains quite useful information with example.
But make sure, you understand CANopen, SDO, PDO, etc. correctly: see the standard, wikipedia, internet, docs here, but the easiest way may be just reading canopenbook.com for example.

There is any manner to read a int16_t variable over read_SDO() function?, the function that returns the variable is a fifo that returns an array of uint8_t
int16_t overTemperatureLimit = 0;
read_SDO(SDO_C, NODE, 0x3020, 0x04, overTemperatureLimit, sizeof(overTemperatureLimit), &readSize);


Add operation guide of bucket rewrite tool

Signed-off-by: Ben Ye<EMAIL_ADDRESS>

[ ] I added CHANGELOG entry for this change.
[x] Change is not relevant to the end user.

Changes

This pr adds an operation guide of using bucket rewrite tool.
It covers three use cases:

Delete series in the obj store
Relabel series labels in the obj store
Modify local Prometheus TSDB blocks

Verification

Cool

Is there an api ?


stivale2: Add the any video header tag

Implements the any video header tag for stivale2, also improves make_header_tag to allow for attributes (and by extension doc comments) for the generated setters.
Documentation:
https://github.com/stivale/stivale/blob/master/STIVALE2.md#any-video-header-tag

Well actually ignore that review for now since making it a u64 would be more useful since if you plan to add a new acceptable value for the preference field for a custom bootloader, you dont have to go to the hassle of cloning and adding a new variant in the enum and they can just use the value as it is.
So LGTM!

Thanks @JCapucho!


Event validation improvements

This is a laundry list of issues and improvements. This issue might be split up as it is updated.
Event validation does not currently check constraints -- at least in some cases. (Needs to be verified, and failing cases should be added here.) If confirmed, this can be considered a bug.
Event validation should be enhanced to show warnings.

Deprecations should be flagged as warnings, along with what should be done instead.
Missing recommended fields should be flagged as warnings.

@rmouritzen-splunk Here is an example of validation passing while there are none of the at_least_one constraints present in an event:
The Event Log Activity class has this constraint: At least one attribute must be present: log_file, log_name, log_provider, log_type, log_type_id:

When I omit all of those at_least_one attributes from the log, it still passes validation. Here is a sample log and curl command that can be used for testing:
Sample Log:
{
  "activity_id": 1,
  "activity_name": "Create",
  "actor": {
    "session": {
      "uid": "0x7A3E5"
    },
    "user": {
      "domain": "ATTACKRANGE",
      "name": "Administrator",
      "uid": "ATTACKRANGE\\Administrator"
    }
  },
  "category_name": "System Activity",
  "category_uid": 1,
  "class_name": "Registry Key Activity",
  "class_uid": 1008,
  "device": {
    "hostname": "win-dc-1796611.attackrange.local",
    "os": {
      "name": "Windows",
      "type": "Windows",
      "type_id": 100
    },
    "type": "Unknown",
    "type_id": 0
  },
  "dst_endpoint": {
    "hostname": "win-dc-1796611.attackrange.local"
  },
  "log_name": "Security",
  "log_type_id": 1,
  "message": "The audit log was cleared.",
  "metadata": {
    "event_code": "1102",
    "log_name": "Security",
    "log_provider": "Microsoft-Windows-Eventlog",
    "original_time": "10/09/2020 09:10:56 AM",
    "product": {
      "name": "Microsoft Windows",
      "vendor_name": "Microsoft"
    },
    "profiles": [
      "host"
    ],
    "sequence": 228829,
    "uid": "86eec1bb-ace7-41ba-9f76-961a35f040c2",
    "version": "1.0.0-rc.2"
  },
  "severity": "Informational",
  "severity_id": 1,
  "status": "Success",
  "status_id": 1,
  "time":<PHONE_NUMBER>000,
  "type_name": "Registry Key Activity: Create",
  "type_uid": 100801,
  "unmapped": {
    "EventType": "4",
    "OpCode": "Info",
    "TaskCategory": "Log clear"
  }
}

Curl Command:
curl -X POST "https://schema.ocsf.io/api/validate" -H "accept: application/json" -H "content-type: application/json" -d "{ \"activity_id\": 1, \"activity_name\": \"Clear\", \"actor\": { \"session\": { \"uid\": \"0x7A3E5\" }, \"user\": { \"domain\": \"ATTACKRANGE\", \"name\": \"Administrator\", \"uid\": \"ATTACKRANGE\\\\Administrator\" } }, \"category_name\": \"System Activity\", \"category_uid\": 1, \"class_name\": \"Event Log Activity\", \"class_uid\": 1008, \"device\": { \"hostname\": \"win-dc-1796611.attackrange.local\", \"os\": { \"name\": \"Windows\", \"type\": \"Windows\", \"type_id\": 100 }, \"type\": \"Unknown\", \"type_id\": 0 }, \"dst_endpoint\": { \"hostname\": \"win-dc-1796611.attackrange.local\" }, \"message\": \"The audit log was cleared.\", \"metadata\": { \"event_code\": \"1102\", \"log_name\": \"Security\", \"log_provider\": \"Microsoft-Windows-Eventlog\", \"original_time\": \"10/09/2020 09:10:56 AM\", \"product\": { \"name\": \"Microsoft Windows\", \"vendor_name\": \"Microsoft\" }, \"profiles\": [ \"host\" ], \"sequence\": 228829, \"uid\": \"4e018c20-e924-4855-9f0e-36dc804f52de\", \"version\": \"1.3.0-dev\" }, \"severity\": \"Informational\", \"severity_id\": 1, \"status\": \"Success\", \"status_id\": 1, \"time\":<PHONE_NUMBER>000, \"type_name\": \"Event Log Activity: Clear\", \"type_uid\": 1008, \"unmapped\": { \"EventType\": \"4\", \"OpCode\": \"Info\", \"TaskCategory\": \"Log clear\" }}"

Validation Result (passes):

The event validation does not look at constraints at all, which explains why this check isn't working.

This also appears to pertain to https://github.com/ocsf/ocsf-schema/pull/1078


localization

Added pt-BR descriptions, pure qwerty layout and screenshots

@Luan1Carlos2 I need you to create another PR with some fixes. See comments in this PR.


Taiko-going-fire

Describe the feature request
Description of the feature request here.
Describe alternatives you've considered
Description of the alternatives you've considered here.
Additional context
Additional context here.

waiting...

waiting...

for what?


improvement: Add slots to password-related forms.

Allows the sign in, register and reset forms to be customised by way of a named slot.

Looks great! I think what we can do is basically this (in a different PR)

make a guide called "customizing AshAuthenticationPhoenix"
set the stage (using the builtin live view can get you off to the races quickly.
explain what the simple default looks like
say "but you're likely going to want your own liveviews at some point, so here is one you can copy to get started"
acknowledge that these components are a beginning, and PRs will be accepted to add more overrides/slots/configurations (after vetting them of course).

And then I think we can be reactive at that point.


Bugfix: serialize iterable commands

Summary of the Pull Request
Fixes a bug where top-level iterable commands were not serialized.
PR Checklist

[X] Closes #10365
[X] Tests added/passed

Detailed Description of the Pull Request / Additional comments

Command::ToJson:

iterable commands deserve the same treatment as nested commands

ActionMap:

Similar to how we store nested commands, iterable commands need to be handled separately from standard commands. Then, when generating the name map, we make sure we export the iterable commands at the same time we export the nested commands.

While working on this bugfix, I realized that another bug exists:
{
    "name": "${profile.name}",
    "command": { "action": "newTab", "profile": "${profile.name}" },
    "iterateOn": "profiles"
},
{
    "name": "${profile.name}",
    "commands": [ { "command": "newTab" } ]
}

Here, the settings model exports these commands to the command palette as one entry in the name map (the iterable command). This is wrong though, because really the user is explicitly asking for a command named "${profile.name}".
However, this bug already exists in v1.8, but in a different manifestation.
Here's the encountered behaviors:

this PR: iterable command wins
v1.8 & main: whichever command is added second wins (in the case above, nested command)
expected: no conflict

This bugfix brings us closer to a world where this new bug is fixed. We would need to mess with how we expand commands. But (a) that's too risky for a hotfix and (b) this is a really obscure bug.
@DHowett Thoughts?

@DHowett  Thoughts?

I'd say just.. file it and we can move on. :smile:


Fails to build on ppc64/Linux

The failure message is:
templates/GenericTemplate.hs:77:4:
    Illegal bang-pattern (use -XBangPatterns):
    ! i

Tried with ghc 7.6.1 / alex 3.0.2.

Likely already fixed by 41e3758b5cc8fc85b7901f59270f6ce550d5ea98


tooltips on the column headers of recordset appear twice

There is a delay between the two tooltips. One tooltip looks normal, the other one uses a bigger font and show up on the bottom of the column header.
https://www.gudmap.org/chaise/recordset/#2/Protocol:Protocol@sort(RID)

This has been fixed and merged into master. Looks like this "bug" has been in our project for quite some time now..


feat: graphsync

https://crates.io/crates/graphsync

Added graphsync to support content replication #224.


chore: fix typos in ibctesting package

Description
This pr fixes typos in ibctesting package.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 81.61%. Comparing base (1c0c756) to head (ad1233f).
Report is 55 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5919      +/-   ##
==========================================
+ Coverage   81.59%   81.61%   +0.02%
==========================================
  Files         199      198       -1
  Lines       15167    12114    -3053
==========================================
- Hits        12375     9887    -2488
+ Misses       2326     1765     -561
+ Partials      466      462       -4

see 172 files with indirect coverage changes


git-auto-fetch not able to handle AddKeysToAgent yes

Describe the bug
After cd into a git repository with git-auto-fetch enabled it asks for the ssh passphrase but it's not possible to enter it.
To Reproduce

Enable plugin git-auto-fetch
Get ssh key with passphase that is used to pull git repos
Add AddKeysToAgent yes to ~/.ssh/config
exec zsh
start ssh-agent (e.g. eval $(ssh-agent)) (Do not add ssh key!)

Expected behavior
Either soft fail (1) or be able to enter passphrase (2).
Screenshots or recordings

System:

OS: Manjaro
Zsh version: zsh 5.7.1 (x86_64-pc-linux-gnu)
Terminal emulator: Irrelevant but Tilix

Correction: AddKeysToAgent is not necessary to trigger this. Specifying one or more IdentityFiles will also trigger this bug.


gdal3 ci

Follow up to https://github.com/georust/gdal/pull/85
Tests are currently failing on gdal3 (on both mac and linux)

@michaelkirk Nice scripts!  Looking through some of the proj tests that have failed, it seems the test case indeed covers gdal 3.0 also.   See for example:
#[test]
fn from_epsg_to_wkt_proj4() {
    let spatial_ref = SpatialRef::from_epsg(4326).unwrap();
    let wkt = spatial_ref.to_wkt().unwrap();
    // TODO: handle proj changes on lib level
    #[cfg(not(feature = "gdal_3_0"))]
    assert_eq!("GEOGCS[\"WGS 84\",DATUM[\"WGS_1984\",SPHEROID[\"WGS 84\",6378137,298.257223563,AUTHORITY[\"EPSG\",\"7030\"]],AUTHORITY[\"EPSG\",\"6326\"]],PRIMEM[\"Greenwich\",0,AUTHORITY[\"EPSG\",\"8901\"]],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]],AUTHORITY[\"EPSG\",\"4326\"]]", wkt);
    #[cfg(feature = "gdal_3_0")]
    assert_eq!("GEOGCS[\"WGS 84\",DATUM[\"WGS_1984\",SPHEROID[\"WGS 84\",6378137,298.257223563,AUTHORITY[\"EPSG\",\"7030\"]],AUTHORITY[\"EPSG\",\"6326\"]],PRIMEM[\"Greenwich\",0,AUTHORITY[\"EPSG\",\"8901\"]],UNIT[\"degree\",0.0174532925199433,AUTHORITY[\"EPSG\",\"9122\"]],AXIS[\"Latitude\",NORTH],AXIS[\"Longitude\",EAST],AUTHORITY[\"EPSG\",\"4326\"]]", wkt);
    let proj4string = spatial_ref.to_proj4().unwrap();
    assert_eq!("+proj=longlat +datum=WGS84 +no_defs", proj4string.trim());
}

It seems to expect the feature gdal_3_0 to be set.  Could you add this feature tag in CI for 3.0?  This might fix many of the issues.
Some of the raster tests are being run on a png file, which seems to have been fixed upstream to not give any GIS metadata (scale, offset).  Might be prudent to use a geotiff here (see "tinymarble.png").  We could convert the png into a tiff as follows:
# from inside fixtures/ directory
gdalwarp -to SRC_METHOD=NO_GEOTRANSFORM -te 0 0 100 50 tinymarble.png tinymarble.tif

This will create a tinymarble.tif file;  then we could modify the failing tests to use tinymarble.tif instead.  Specifically, tests get_offset and get_scale in src/raster/tests.rs .  should now pass on both gdal versions.

An  update:
GDAL 2.0 builds passing on linux (ubuntu trusty) and macos.
GDAL 3.0 build on macos is failing these two tests:
---- raster::tests::test_get_offset stdout ----
thread 'raster::tests::test_get_offset' panicked at 'assertion failed: `(left == right)`
  left: `None`,
 right: `Some(0.0)`', src/raster/tests.rs:347:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
---- raster::tests::test_get_scale stdout ----
thread 'raster::tests::test_get_scale' panicked at 'assertion failed: `(left == right)`
  left: `None`,
 right: `Some(1.0)`', src/raster/tests.rs:339:5
failures:
    raster::tests::test_get_offset
    raster::tests::test_get_scale
test result: FAILED. 69 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out

https://travis-ci.org/github/georust/gdal/jobs/722360412#L298
these the the problematic lines:
gdal_sys::GDALGetRasterScale(self.c_rasterband, &mut pb_success)
and
gdal_sys::GDALGetRasterOffset(self.c_rasterband, &mut pb_success)
On macos, both fail because pb_success != 1

Some of the raster tests are being run on a png file, which seems to have been fixed upstream to not give any GIS metadata (scale, offset).

Interestingly, GDAL 3.0 build on linux (ubuntu bionic) is passing these same tests:
https://travis-ci.org/github/georust/gdal/jobs/722360408#L857
Does that debunk the theory that it's just a matter of a bad PNG @rmanoka?
For context, I'm not familiar with GDAL, or even explicitly using it. This was all in pursuit of updating to the latest geo-types, but figured I should have a working test suite first.

This will create a tinymarble.tif file; then we could modify the failing tests to use tinymarble.tif instead. Specifically, tests get_offset and get_scale in src/raster/tests.rs . should now pass on both gdal versions.

Also, just tried this, and tests still failing for me.

@michaelkirk   Found this relevant issue on OSGeo/gdal.  It seems like it changed with release 3.1.0.  The linux CI might be passing because it is 3.x but < 3.1.0.  The issue also suggests the same behavior for tif files, so I was wrong there.   Unfortunately, we can't use the feature flag as the regression is between 3.0 and 3.1.0.
Could you try this:  once you have the tinymarble.tif ; run:
gdal_edit -scale 1.2 -offset 12 file.tif

Then, in the test, we should look for these two values (instead of 1.0, 0.0).   Now that we're setting explicit non-default values, I'm hoping it will reflect in the calls.

Thanks for your guidance @rmanoka, I think this PR is now ready for review.

Hi, thank you for your contribution. This kind of issue is why i ceated the "Feature_gated_versions" branch which i intend to merge into master soon. It splits gdal 2 and 3 and add Features for different versions.
However, i am away for the next 10 days. Untill then think i can't review or merge PRs.

This kind of issue is why i ceated the "Feature_gated_versions" branch which i intend to merge into master soon. It splits gdal 2 and 3 and add Features for different versions.

To be clear, the issue here was not one of a new feature being added or removed. Rather, the behavior of an existing method changed and we weren't running CI to test that version.

Oh sorry if i got it wrong. There are so many issues related to the versioning i thought it is one of them.

Could you update this PR to reflect the changes in version handling?

Could you update this PR to reflect the changes in version handling?

Done! Provided CI passes this should be good to go.


Username/Password

Hey there,
The XL does not offer API access at the moment.
But it still works if you use the user password shown on the printer!

We should receive our first XL in two months. We will check that it works well at that time. But normally no problem because it is the same code as for the MINI and MK4.

We tested for the XL: it works


fix web store submission by requiring client secret

we also need to change inside the guides to provide the client secret inside keys.json most likely

Sure will fix now


Detections are only motorcycles ?

Hello !
Thanks for this great work, and for having released it !
Testing the code, and especially the output detections, I have the feeling that all detection are class 3 (that is motorcycles)
Am I doing something wrong ?
Thanks for your feedback and great work again
LS

I also encountered the same problem, did you solve it?


Show descriptions for repeating groups

If a repeating group has a description, it is now shown below the label when rendering the repeating group, unstyled. If there is no description, an invisible, empty div is created.
Kitchen sink:

This will make everything just work in Screendoor as soon as it's released (and we're using the latest version), since we already store the description from the formbuilder.
Before:

After (no description) -- should look the same:

After (with description) -- wow!

The description in the preview also automatically updates as you edit the field description in formbuilder, the same way labels do.

Should we bump the version gate min version # for repeating groups in screendoor to whatever version this will be as well?

I think we can make this a product decision, as this isn't really a fix for breaking something. I'm totally happy to bump the version, but if we don't the worst thing that'll happen to someone using an older version will be that repeating groups work, but just don't have descriptions.

I vote for bumping it.

Sounds good. I'll merge and release this and then open a PR bumping the min version in Screendoor.


SplitText not working

Do have a look. I need this library in my project to integrate.
Also please assign me. I will also try to fix it if I can.
Are unit tests written for the functions?

This works for me
ctx := context.TODO()

splitter := textsplitter.NewRecursiveCharacter()
splitter.ChunkOverlap = 100

text := documentloaders.NewText(f)
splitted, err := text.LoadAndSplit(ctx, splitter)

var docChunks = make([]schema.Document, 0)
	for _, d := range splitted {
		d.Metadata = // your meta here
		docChunks = append(docChunks, d)
	}
spew.Dump(docChunks)

Closing as the above sample was provided.


Biome encountered an unexpected error

This is a bug in Biome, not an error in your code, and we would appreciate it if you could report it to https://github.com/biomejs/biome/issues/ along with the following information to help us fixing the issue:

Source Location: crates/biome_service/src/configuration/linter/mod.rs:167:18
Thread Name: biome::worker_7
Message: internal error: entered unreachable code: the rule is turned off, it should not step in here

I assume it's related to this section of my biome.json config:
"overrides": [
  {
    "include": ["infrastructure/**"],
    "linter": {
      "rules": {
        "suspicious": {
          "noConsoleLog": "off"
        }
      }
    }
  }
],

Expected result
Biome does not ask me to report an issue.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Please create a reproduction, so we can easily help you

This might be a duplicate of #691?

Probably, but still, I would like to have a repository to test. The issue is open for a week without updates from OP, I close it.

Respectfully, your client asks me to report it. Not to do any extra work to create a reproduction. Creating an issue for a problem I do not care about is low effort for me. Creating a repository to reproduce the issue is not.
Maybe it should say: “We might not do anything with it unless you also create a repository with a reproduction.”?
I realize your time is valuable, so I’m totally on board with that. But so is mine, so it’s nice to know how useful just ‘reporting’ the issue is.


Pressing  shift-enter not working when creating chat posts

it should create a newline in the post

Can you provide more information to replicate?
On my local dev machine, I created two separate accounts and from three different browsers (FF, Safari, and Chrome) I'm able to shift-enter to create a new line in a chat in all three.
However, I see that Chrome does not auto-update as messages are sent from FF and Safari. FF and Safari seem to update the chat as I create new posts.

you're right, its working for me now. maybe what i meant was when editing chat posts. its doing weird things there

Ah okay, I'll take a look at editing and see what's different


Update licenses_gov.qmd

I did another more comprehensive edit. I removed the info on the other agencies as that is no longer relevant and added more explicit instructions.  I still need to find the reference for CC0 for data. I have seen it recently but couldn't find it immediately.

Hi @eeholmes, did you want some eyes on this and #8? I wasn't sure if I was assigned on purpose or perhaps automatically!

@k-doering-NOAA The Resource Book has branch protection on, which will ping a reviewer for a pull request. I can turn off though probably good to have more than me aware of big edits like this.

Sorry @eeholmes I'm happy to review when you would like an extra pair of eyes on something! I did glance over the changes here and they looked really great!


Message Classification - Delay Message Replay

As a user of the queue-triage application
It should be possible to mark a message for resending at some point in the future

Code commited.  Waiting on other PR merges


AndroidX migration & updated target sdk to 28

I have migrate the library and sample to AndroidX and i have update the target sdk to 28 version
https://github.com/EverythingMe/overscroll-decor/issues/70

@pandelisgreen13 thanks for this. I'll review asap.

nice PR @pandelisgreen13 .
though, I would suggest to make the target and compile sdk point to sdk 29. Unless there's something that's preventing you from using it.
@d4vidi are you gonna merge this one ? If merged, I think this PR is going to help a lot.


gold: Doesn't correctly set rpath in certain instances

I'll get back to documenting this.

(triage) @abbradar Can you check whether this still happens?

At least for crawl it works now; I'm not sure if it's fixed or something in crawl has changed.

Then we should close this until it happens again. @jagajaga


feat: added statcord plugin

This allows Statcord integration with @sapphire/framework bots. Statcord is a statistics platform for discord bots.

Closing this as discussed on Discord. Once you have published the package we will create awesome-sapphire repository and list it there.


feat: accept negative padding for default_component_configs.indent.padding

With the following config, the outcome still has an extra padding on the left by default as you can see on line lua/neo-tree in the picture.
I would like to delete this extra space by setting default_component_configs.indent.padding to a negative value to work around this feature.
require("neo-tree").setup({
  hide_root_node = true,
  default_component_configs = {
    indent = {
      padding = 0,
      -- padding = -2, -- This will work with this PR
    },
  },
})

Current Behavior
(The white line is the edge of the shell window)

default_component_configs.indent.padding = 0

default_component_configs.indent.padding = -2

Expected Behavior

default_component_configs.indent.padding = -2

Again, thanks for the awesome plugin,
@pysan3

Codecov Report

Merging #424 (1aba03b) into main (fa5018b) will decrease coverage by 0.11%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #424      +/-   ##
==========================================
- Coverage   53.24%   53.13%   -0.12%
==========================================
  Files          45       45
  Lines        5388     5392       +4
==========================================
- Hits         2869     2865       -4
- Misses       2519     2527       +8

Impacted Files
Coverage Δ

lua/neo-tree/sources/common/components.lua
59.90% <50.00%> (-0.19%)
:arrow_down:

lua/neo-tree/sources/filesystem/init.lua
60.33% <0.00%> (-2.11%)
:arrow_down:

lua/neo-tree/utils.lua
49.17% <0.00%> (-0.28%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fa5018b...1aba03b. Read the comment docs.

Thanks for the feedback ;)
Yes, that very well suites what I want but I wasn't confident enough to go into the function and touch any variables.
Could I ask you kindly to add this feature?
Anyways, closing this PR.


Unable to compile the driver for DuckDB 0.9.2 over Metabase 0.48.7

Hi @AlexR2D2,
I'm trying to compile the driver without success for the release 0.9.2. This is quite important if you want to test the integration between Metabase and the DuckDB cloud based platform Motherduck.
Is there any possibility for you to add a section in the documentation to explain how to compile the driver with the latest 0.48.7 release of Metabase?
I'm trying using a WSL Ubuntu image and seems like Clojure is not able to pick up the project files.
This is the error i got when running:
clojure -X:build:drivers: :driver :duckdb
{:clojure.main/message
 "Execution error (FileNotFoundException) at java.io.FileInputStream/open0 (FileInputStream.java:-2).\n-X:build:drivers: (No such file or directory)\n",
 :clojure.main/triage
 {:clojure.error/class java.io.FileNotFoundException,
  :clojure.error/line -2,
  :clojure.error/cause "-X:build:drivers: (No such file or directory)",
  :clojure.error/symbol java.io.FileInputStream/open0,
  :clojure.error/source "FileInputStream.java",
  :clojure.error/phase :execution},
 :clojure.main/trace
 {:via
  [{:type java.io.FileNotFoundException,
    :message "-X:build:drivers: (No such file or directory)",
    :at [java.io.FileInputStream open0 "FileInputStream.java" -2]}],
  :trace
  [[java.io.FileInputStream open0 "FileInputStream.java" -2]
   [java.io.FileInputStream open "FileInputStream.java" 219]
   [java.io.FileInputStream <init> "FileInputStream.java" 157]
   [java.io.FileInputStream <init> "FileInputStream.java" 112]
   [clojure.lang.Compiler loadFile "Compiler.java" 7575]
   [clojure.main$load_script invokeStatic "main.clj" 475]
   [clojure.main$script_opt invokeStatic "main.clj" 535]
   [clojure.main$script_opt invoke "main.clj" 530]
   [clojure.main$main invokeStatic "main.clj" 664]
   [clojure.main$main doInvoke "main.clj" 616]
   [clojure.lang.RestFn applyTo "RestFn.java" 137]
   [clojure.lang.Var applyTo "Var.java" 705]
   [clojure.main main "main.java" 40]],
  :cause "-X:build:drivers: (No such file or directory)"}}

Thanks for the great work and long live the Ducks!

try my patch
https://github.com/AlexR2D2/metabase_duckdb_driver/pull/25

Added the section How to build the DuckDB .jar plugin yourself at the end of the main page


Cannot dismiss when showing animation is in progress.

Calling dismiss immediately after calling show shows the popup and never dismisses it.

Here too. The UIView category methoddismissPresentingPopup also doesn't do anything. Tapping on the popup does remove it.


[version 1.2.4] $ionicScrollDelegate not work on android #5629

Short description of the problem:
$ionicScrollDelegate.resize does not work on android
What behavior are you expecting?
I have a directive which can change the height a lot, in this situation,  $ionicScrollDelegate.resize() is needed. it can work with ios with ionic 1.1.1, but if I update ionic to version after 1.1.1. it can not work on android.
I can not reproduce this issue in web browser, so I can not provide a reproduce codepen.
So I will post my reproduce steps as clear as possible:
1. create a ionic project with blank template.
ionic start test blank

2. create a directive with following template and js.
Directive html:

    install

      name

      {{ job.customer_name }}

      tel

      {{ job.customer_phone }}

      address

      {{ job.district }}/{{ job.customer_address }}

      model

      {{ job.product_info }}

appointment_date

          {{ job.appointment_date }}

assigner

          {{ job.assigner }}

assign_time

          {{ job.assign_time }}

remark

        {{ job.remark }}

state

        {{ job.state }}

list

name

                {{ item.item.name }}

count

                {{ item.count }}

{{arrowTip}}

      <button class="button button-small button-positive card_button"
              ng-if="!job.can_accept" ng-click="handle(job)">
        handle
      </button>

Directive js:
angular.module('jobCard', [])

  .directive('jobCard', function ($ionicScrollDelegate, $timeout) {
    return {
      restrict: 'AE',

      scope: {
        job: '=',
      },

      templateUrl: 'js/jobCard/jobCard.html',

      link: function (scope, elem, attr) {

        scope.data = {};
        scope.data.showDetail = false;
        scope.arrowTip = 'show';

        scope.jobCardToggle = function () {
          scope.data.showDetail = !scope.data.showDetail;
          if (scope.data.showDetail) {
            scope.arrowTip = 'hide';
          } else {
            scope.arrowTip = 'show';
          }

          $timeout(function () {
            $ionicScrollDelegate.resize();
          }, 0);
        };
      }
    }
  });

3.  add following code to index.html

<ion-content class="has-header">
  <job-card></job-card>
  <job-card></job-card>
  <job-card></job-card>
  <job-card></job-card>
</ion-content>

4. add android project and run the app in Genymotion simulation "Motorola Moto X - 4.3".
Click one of the "show" button in the cards, which will make the card become higher.
##expected result: The height of scroll bar should updated correctly.
##real result: The height of scroll bar doesn't update.
PS:

if I roll back ionic to 1.1.1, the issue can not reproduce.
if I change android version to 4.2 or 6.0, the issue can not reproduce.

A strange issue, I am not sure if I have described clearly, if not, please let me know.

@njleonzhang, are you able to use crosswalk?  That might resolve the issue.

@danbucholtz, we can not use crosswalk, it is too heavy for us.
Can you reproduce our issue according to my description？

@njleonzhang, everything seems to be working fine for me with Android 4.4 and the latest Ionic.  I am running your app/code but I don't see any issues with scrolling.  I am clicking the show buttons to resize the app.
Can you check if this is still any issue with the latest Ionic?  Can you provide a codepen that I can observe this issue in?
Thanks,
Dan

@danbucholtz, I have claimed:

issue occur when I run the app in Genymotion simulation "Motorola Moto X - 4.3".
The ionic I uses is 1.2.4. If I roll back ionic to 1.1.1, the issue can not reproduce.
If I change android version to 4.2 or 6.0, the issue can not reproduce.

I can also reproduce this issue on a physical device whose OS is android 4.3. so it seems the issue only occur on android 4.3 with ionic higher than 1.1.1

Hello! So I have tested on my Android devices to see if I can reproduce on any other versions of Android. I tested on a Nexus 7 running 6.0.1, a Nexus 6 running the Android N dev preview and a moto x 2014 running Android 5.1. And was not able to reproduce this issue. It seems as if the issue only happens on a single version of Android, 4.3. Is the reason you didn't want to use crosswalk because it made your apk's bigger? I definitely understand that concern but I think that the better html5 support, the consistency it provides on older versions of Android like 4.3, and the pretty massive performance increases it gives you on older versions of Android outweight the increase in apk size. I'd love to hear your thoughts on this (: thanks

@jgw96 Yeah, it seems a issue only on android 4.3 with ionic after 1.1.1.
As you mentioned, the size increasing brought by crosswalk is our concern.
Our APK is about 4Mb, but if we use crosswalk, it may become about 25Mb(I forget the precise value), it is too big for us.
"better html5 support, the consistency and pretty massive performance", hummmm, sounds great. we will consider it. but currently, it is better if you can fix this issue.
I think you should be able to reproduce this issue following the steps I described.
use "Genymotion simulation "Motorola Moto X - 4.3" to run the app.

@njleonzhang Hello! So unfortunately because this issue only happens on a certain older version of android (4.3) and cannot be reproduced on any version of android that is newer i do not think this is a fix that we can put into the framework as it may break something with newer versions of Android. We do recommend that our users use crosswalk for any version of android before 4.4.4 as the android webview before 4.4.4 is very fragmented. I understand fully that this can be frustrating, but the good thing is that android 4.3 only has a 3% (http://developer.android.com/about/dashboards/index.html) market share at this point (in fact, the moto x device you are emulating with in Genymotion received updates all the way to Android 5.1.1 if im not mistaken) and this will only get better as newer android devices and newer versions of Android come out. Thanks for using Ionic! And feel free to continue to open issues with us in the future! I am going to close this issue, but please feel free to comment back.

@jgw96 I am sorry to get this response. Anyway, thanks to your effort. In addition, if possible, would you please add this issue to your known issue list, so that other developers can be aware of it.


Default exported properties order

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/874
Originally created by @bencodezen on 2019-08-13 14:21:28

This still may be an iterative task after this effort, but I'd like to get to a point where when someone is contributing new code on the frontend, they know the exact line of code they should be adding their import, function, or property due to a convention. The aspects that come to mind that would have such a convention are below. Each is assigned the convention I'm thinking at the moment (but don't really care, just want consistency and zero guess work):

imports (alphabetical where all 3rd party come before app specific with an empty line dividing the two groups)
components and stores export defaults (there's a best practice here, but I can't find the reference)

and the components, computeds, actions, mapGetter/Action/etc. within (alphabetical)

markup attribute order (there's a best practice here, but I can't find the reference)

Thoughts? Any other suggestions?
Again, this is likely an iteration after this update so feel free to set to MWPS.

View 1 previous comment from the original issue on GitLab


[WIP] use stable version of msbuild

A (hopefully) proper re-implementation of #3875.  I'm also running a full internal build on this same PR.

@brettfo is this still a thing?

Yes, this will be a thing again shortly, once I finish converting the vsintegration projects to the SDK.


Removed Fable.PowerPack

Fixed code at some places, everything should compile.
Fulma.FormBuilder obviously needs some work.
Should fix #114

Thank you :)


list shopcarts

As a service manager
I need to list shopcarts
So that customer can view it
Details & Assumptions:

shopcart already exists

Acceptance Criteria:
Given a shopcart
When requests to see existing shopcart
Then shopcart is listed

details added


Segfault for large problems when using Broyden

This line
fjac = prev_fjac + &
    matmul((delf-matmul(prev_fjac,delx)),&
    transpose(delx))/delxmag2

will segfault on intel for a large problem (e.g., n=1406, m=1200).
What can we do about it?

see this discussion: https://fortran-lang.discourse.group/t/automatic-arrays-and-intrinsic-array-operations-to-use-or-not-to-use/4070


Add annotations for method overrides and interface implementations.

Hello
This adds basic support for annotating overrides of methods for classes as well as interface implementations (both in a different color). The annotations are added to the default gutter when the markers are registered (at the same time as the goto markers). I've also let the annotations as well as the goto markers be reset and rescanned when a file is saved.
On the PHP side, I also provided isImplementationOf and isOverrideOf, as I thought it would be really nice to be able to have tooltips on the annotation or be able to click through to the respective class (we already have the information anyway), but I haven't been able to figure out how to do this yet and figured that even in its current state, this is already useful and we can always add it later.
Hopefully this will be a major help for people that often work with subclasses and interfaces so they can easily see what method originates from a base class or an interface.
@Peekmo For when you get back and are able to review this: I merged most of my pull requests in my fork's master branch, some of them will generate minor conflicts which I've already resolved there. If it's easier for you, I can always create a larger pull request, you can pull the changes from there, or simply view them to see the conflict resolution I performed.

Hello,
An amazing feature !
I'll try it next week. For conflicts, you can open a large PR where you're referencing all the previous ones that are not merge today. I'll merge everything at once if it seems okey.
Thank you vers much !