Cannot find -lnpymath when building for Python 3.8

I try to build jetson inference in my Jetson Nano (2GB) with python3.8, because it's requirement for my project.
I follow instruction from https://github.com/dusty-nv/jetson-inference/issues/936 , by adding 3.8 in CMakeList.txt, however when I try to make (make -j$(nproc)), an error occured) .

79%] Built target camera-capture_autogen
[ 84%] Built target jetson-inference-python-36
Scanning dependencies of target jetson-inference-python-37
/usr/bin/ld: cannot find -lnpymath
collect2: error: ld returned 1 exit status
utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/build.make:283: recipe for target 'aarch64/lib/python/3.8/jetson_utils_python.so' failed
make[2]: *** [aarch64/lib/python/3.8/jetson_utils_python.so] Error 1
CMakeFiles/Makefile2:1243: recipe for target 'utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/all' failed
make[1]: *** [utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....

Numpy is already installed on my Python3.8, with version 1.23.2

@Aldhanekaa I haven't tried building jetson-inference with Python 3.8 on JetPack 4.x, but you will need to have the dev libraries installed for numpy (normally I do apt-get install python3-numpy), or you may need to make sure that cmake finds them

@Aldhanekaa I haven't tried building jetson-inference with Python 3.8 on JetPack 4.x, but you will need to have the dev libraries installed for numpy (normally I do apt-get install python3-numpy), or you may need to make sure that cmake finds them

ah I see. The error is resolved now by installing numpy, thanks for that. However new error occured;
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(abstract.o): In function `PyBuffer_FromContiguous':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/abstract.c:529:(.text+0x174c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/abstract.c:529:(.text+0x1750): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.8.a(object.o): In function `_PyObject_GetMethod':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:1143:(.text+0x2494): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.8.a(object.o): In function `_PyObject_LookupAttr':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x2b30): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x2c78): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x2db0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x2ef0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x3040): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(typeobject.o): In function `type_new':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/typeobject.c:2782:(.text+0x100f0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6404): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToTitlecase':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:69:(.text+0x6428): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x646c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x64bc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x650c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToDecimalDigit':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:110:(.text+0x655c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x65b4): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToDigit':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:127:(.text+0x6604): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x665c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x66ac): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x66fc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x674c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x679c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x67ec): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToUppercase':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:195:(.text+0x6814): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x685c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToLowercase':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:207:(.text+0x6880): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x68d0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToLowerFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:220:(.text+0x6910): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6988): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToTitleFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:236:(.text+0x69c8): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6a40): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToUpperFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:252:(.text+0x6a84): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6af8): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToLowerFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:220:(.text+0x6b3c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToFoldedFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:268:(.text+0x6b88): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6bdc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6c2c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6c7c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(posixmodule.o): In function `posix_initgroups':
/home/jn2gb-01/Documents/e/Python-3.8.0/./Modules/posixmodule.c:6981:(.text+0x5134): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(posixmodule.o): In function `posix_getgrouplist':
/home/jn2gb-01/Documents/e/Python-3.8.0/./Modules/posixmodule.c:6804:(.text+0x83cc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(myreadline.o): In function `PyOS_Readline':
/home/jn2gb-01/Documents/e/Python-3.8.0/Parser/myreadline.c:335:(.text+0x43c): dangerous relocation: unsupported relocation
collect2: error: ld returned 1 exit status
utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/build.make:283: recipe for target 'aarch64/lib/python/3.8/jetson_utils_python.so' failed
make[2]: *** [aarch64/lib/python/3.8/jetson_utils_python.so] Error 1
CMakeFiles/Makefile2:1243: recipe for target 'utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/all' failed
make[1]: *** [utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/all] Error 2
Makefile:129: recipe for target 'all' failed

It seems like an error from libpython3.8 (I guess?), but im 100% sure, I install python3.8.0 properly (from source). Well previously this once occurred, then I tried to reinstall python3.8.0, then theres error cannot find -lnpymath, now after I resolved the lnpymath error, the libpython3.8 error occurred again 😅.

@Aldhanekaa I haven't tried building jetson-inference with Python 3.8 on JetPack 4.x, but you will need to have the dev libraries installed for numpy (normally I do apt-get install python3-numpy), or you may need to make sure that cmake finds them

ah I see. The error is resolved now by installing numpy, thanks for that. However new error occured;
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(abstract.o): In function `PyBuffer_FromContiguous':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/abstract.c:529:(.text+0x174c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/abstract.c:529:(.text+0x1750): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.8.a(object.o): In function `_PyObject_GetMethod':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:1143:(.text+0x2494): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/libpython3.8.a(object.o): In function `_PyObject_LookupAttr':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x2b30): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x2c78): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x2db0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x2ef0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.a(object.o): relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `PyObject_GenericGetAttr' which may bind externally can not be used when making a shared object; recompile with -fPIC
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/object.c:961:(.text+0x3040): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(typeobject.o): In function `type_new':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/typeobject.c:2782:(.text+0x100f0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6404): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToTitlecase':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:69:(.text+0x6428): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x646c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x64bc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x650c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToDecimalDigit':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:110:(.text+0x655c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x65b4): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToDigit':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:127:(.text+0x6604): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x665c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x66ac): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x66fc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x674c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x679c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x67ec): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToUppercase':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:195:(.text+0x6814): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x685c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToLowercase':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:207:(.text+0x6880): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x68d0): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToLowerFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:220:(.text+0x6910): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6988): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToTitleFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:236:(.text+0x69c8): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6a40): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToUpperFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:252:(.text+0x6a84): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6af8): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToLowerFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:220:(.text+0x6b3c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `_PyUnicode_ToFoldedFull':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:268:(.text+0x6b88): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(unicodectype.o): In function `gettyperecord':
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6bdc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6c2c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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
/home/jn2gb-01/Documents/e/Python-3.8.0/Objects/unicodectype.c:55:(.text+0x6c7c): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(posixmodule.o): In function `posix_initgroups':
/home/jn2gb-01/Documents/e/Python-3.8.0/./Modules/posixmodule.c:6981:(.text+0x5134): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(posixmodule.o): In function `posix_getgrouplist':
/home/jn2gb-01/Documents/e/Python-3.8.0/./Modules/posixmodule.c:6804:(.text+0x83cc): dangerous relocation: unsupported relocation
/usr/bin/ld: /usr/local/lib/libpython3.8.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.8.a(myreadline.o): In function `PyOS_Readline':
/home/jn2gb-01/Documents/e/Python-3.8.0/Parser/myreadline.c:335:(.text+0x43c): dangerous relocation: unsupported relocation
collect2: error: ld returned 1 exit status
utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/build.make:283: recipe for target 'aarch64/lib/python/3.8/jetson_utils_python.so' failed
make[2]: *** [aarch64/lib/python/3.8/jetson_utils_python.so] Error 1
CMakeFiles/Makefile2:1243: recipe for target 'utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/all' failed
make[1]: *** [utils/python/bindings_python_3.8/CMakeFiles/jetson-utils-python-38.dir/all] Error 2
Makefile:129: recipe for target 'all' failed

It seems like an error from libpython3.8 (I guess?), but im 100% sure, I install python3.8.0 properly (from source). Well previously this once occurred, then I tried to reinstall python3.8.0, then theres error cannot find -lnpymath, now after I resolved the lnpymath error, the libpython3.8 error occurred again 😅.

well ChatGPT said, it caused by the mismatch of Python3.8 with my jetson architecture, well after I checked, it matches.

well, just info, I overwrited my  Jetson nano python3.6 with python3.8, fortunately so far there's no system error

I think I found the solution. To overcome this situation, I need to remake the project first (that intended for 3.6 & 3.7, so I delete 3.8 on CMakeLists.txt). Once I remade the project, I type sudo ldconfig . Then I tried to add 3.8 in CMakeLists.txt, however theres different new error -ljetson-utils-python-38, it already mentioned in this issue https://github.com/dusty-nv/jetson-inference/issues/936 (but still I havent figured out how to overcome the -ljetson-utils-python-38 error)

oh my bad,

I think I found the solution. To overcome this situation, I need to remake the project first (that intended for 3.6 & 3.7, so I delete 3.8 on CMakeLists.txt). Once I remade the project, I type sudo ldconfig . Then I tried to add 3.8 in CMakeLists.txt, however theres different new error -ljetson-utils-python-38, it already mentioned in this issue #936 (but still I havent figured out how to overcome the -ljetson-utils-python-38 error)

that's not the solution, turns out -ljetson-utils-python-38 error occured because I didnt add 3.8 into CMakeLists.txt inside utils/python folder

Ok I think this occurred because Python3.8 is built from source, previously when I try to install jetson inference with python3.7 (built from source) this error occurred however when I try to install jetson inference with python3.7 that was downloaded with apt-get there was no any error

Hello @Aldhanekaa , did you solve all the problems?

@jiefengsun yeah I did, what I did was using python3.7 that was installed with apt-get. Well previously I faced the same issue as this with python3.7, then I rebuilt the microsdcsrd image then I install python3.7 with apt-get

Thanks @Aldhanekaa , But I feel the package conflicts is a big issue if 3.7 is installed with apt-get. For example, if I install a numpy, use pip, will it install for python 3.6 or python 3.7. How did you manage this problem?
Also I found out that using conda virtual environment is not a good idea, because the packages in the Jetpack (eg., TensorRT, cuDNN) cannot be used in the virtual environment.

@jiefengsun yeah I did, what I did was using python3.7 that was installed with apt-get. Well previously I faced the same issue as this with python3.7, then I rebuilt the microsdcsrd image then I install python3.7 with apt-get

Thanks @Aldhanekaa , But I feel the package conflicts is a big issue if 3.7 is installed with apt-get. For example, if I install a numpy, use pip, will it install for python 3.6 or python 3.7. How did you manage this problem?
Also I found out that using conda virtual environment is not a good idea, because the packages in the Jetpack (eg., TensorRT, cuDNN) cannot be used in the virtual environment.

ah I see, first thing first if you install package with pip it will install the package for the python2.7. So make sure use pip3 for python3
However if you installed python3.7 on Jetson Nano with apt-get, the default python3 version still on 3.6 (if I'm not mistaken, python3 --version) , which means anything that you install with pip3 is for python3.6. It is so not recommended to change the default python3 version of Jetson board, so to install library for your python3.7 you need to install it directly /usr/bin/python3.7 -m pip
/usr/bin/python3.7 -m pip install numpy

@jiefengsun yeah I did, what I did was using python3.7 that was installed with apt-get. Well previously I faced the same issue as this with python3.7, then I rebuilt the microsdcsrd image then I install python3.7 with apt-get

Thanks @Aldhanekaa , But I feel the package conflicts is a big issue if 3.7 is installed with apt-get. For example, if I install a numpy, use pip, will it install for python 3.6 or python 3.7. How did you manage this problem?
Also I found out that using conda virtual environment is not a good idea, because the packages in the Jetpack (eg., TensorRT, cuDNN) cannot be used in the virtual environment.

ah I see, first thing first if you install package with pip it will install the package for the python2.7. So make sure use pip3 for python3
However if you installed python3.7 on Jetson Nano with apt-get, the default python3 version still on 3.6 (if I'm not mistaken, python3 --version) , which means anything that you install with pip3 is for python3.6. It is so not recommended to change the default python3 version of Jetson board, so to install library for your python3.7 you need to install it directly /usr/bin/python3.7 -m pip
/usr/bin/python3.7 -m pip install numpy

For your information, so far I couldn't install Jetson Inference on python3.7 virtualenv, what I did was let Jetson Inference library installed globally then I
virtualenv env -p /usr/bin/python3.7 --system-site-packages

@jiefengsun yeah I did, what I did was using python3.7 that was installed with apt-get. Well previously I faced the same issue as this with python3.7, then I rebuilt the microsdcsrd image then I install python3.7 with apt-get

Well by the way, when I encountered this issue Cannot find -lnpymath when building for Python 3.8 , sure it is necessary to uninstall the python3.8, however it's so difficult to uninstall because at the time I installed Python3.8 by building it from source, it is not easy as uninstall with apt-get. So since I was struggling to uninstall python3.8, I decided to rebuilt the image of my Jetson board 😅 . Installing python3 version by building from source gives me a trauma 😅😅


Hide bot token in errors

This fixes a potential[^1] security vulnerability -- if bot shows errors from teloxide to the user & for some reason network error happened[^2] the url of the request would be included in the error. Since TBA includes bot token in the error this may lead to token leakage.
This PR fixes that issue by removing the token from the urls of reqwest::Error, we try to redact only the token, but if we fail we remove the whole url.
This can be tested by using a very low timeout value for the http reqwest client:
let client = reqwest::Client::builder()
    .timeout(std::time::Duration::from_millis(1))
    .build()
    .unwrap();

let bot = Bot::from_env_with_client(client).auto_send();

// see if the token is redacted when network error (timeout) happens
// while sending common requests
let _ = dbg!(bot.get_me().await);

// see if the token is redacted when network error (timeout) happens
// while downloading files ("path" is unimportant as the timeout is so
// low the request probably won't even be sent)
let _ = dbg!(bot.download_file_stream("path").next().await);

For me this gives the following result:
[t.rs:26] bot.get_me().await = Err(
    Network(
        reqwest::Error {
            kind: Request,
            url: Url {
                scheme: "https",
                cannot_be_a_base: false,
                username: "",
                password: None,
                host: Some(
                    Domain(
                        "api.telegram.org",
                    ),
                ),
                port: None,
                path: "/token:redacted/GetMe",
                query: None,
                fragment: None,
            },
            source: TimedOut,
        },
    ),
)
[t.rs:31] bot.download_file_stream("path").next().await = Some(
    Err(
        reqwest::Error {
            kind: Request,
            url: Url {
                scheme: "https",
                cannot_be_a_base: false,
                username: "",
                password: None,
                host: Some(
                    Domain(
                        "api.telegram.org",
                    ),
                ),
                port: None,
                path: "/file/token:redacted/path",
                query: None,
                fragment: None,
            },
            source: TimedOut,
        },
    ),
)

Note that this branch is created from v0.4.4 tag and not master, since the latter has breaking changes and we want to release this fix as v0.4.5. We'll need to make a release from this branch directly.
[^1]: Note that there are recorded cases where the token got exposed.
[^2]: Note that this can theoretically be controlled by the user when
sending/downloading bigger files.

It seems like the timeline of events should be as follows:

@Hirrolot reviews this PR
I release a new teloxide-core version
We resolve conflicts with master (by merging master to this branch)
We merge this PR


How can I get originalObject in selected event

Hi.
How can I get originalObject in selected event?
for example in your example:
`
protected searchData = [
{ color: 'red', value: '#f00' },
{ color: 'green', value: '#0f0' },
{ color: 'blue', value: '#00f' },
{ color: 'cyan', value: '#0ff' },
{ color: 'magenta', value: '#f0f' },
{ color: 'yellow', value: '#ff0' },
{ color: 'black', value: '#000' }
];
constructor(private completerService: CompleterService) {
this.dataService = completerService.local(this.searchData, 'color', 'color');
}

<ng2-completer [(ngModel)]="searchStr" [datasource]="dataService" [minSearchLength]="0">
`
I want use value field but search in colors!
Thanks.

Same Question here!

#233 But not working

I use this and works for me:
(selected)="onItemSelect($event)"
and
onItemSelect(selected:CompleterItem){
if(selected)
this.selectedItem = selected.originalObject._id;
}

I agree with saostad's solution to the issue. But you must import the CompleterItem interface.
import { CompleterService, CompleterData, CompleterItem } from 'ng2-completer';


docs: enable GitHub discussions and remove link to spectrum

Spectrum seems to be pretty dead these days. I think we should just simply use GitHub discussions instead.
Not sure if the settings app has been updated to support "has_discussions" but if not it could just be enable manually.
@jonaskello I haven't enabled GitHub discussions on any other repo before so I'm not sure if there's any extra setup required. I'll leave this to you to merge :)

The change in config.yaml did not seem to have any effect so I enabled discussions in settings and added a badge for it in the readme.


Crash when resizing window with text in mod search field

Game crashes when the window is resized with any text in the mod search field. Just being selected or being empty does not cause the crash, however it is really slow for the window to be resized anyway.
My log: https://gist.github.com/Blayyke/1ec9c5b5a682f57d7e0d22359f2f3b2c
Log from calloatti: https://paste.ee/p/m9Rlk
Also worth pointing out is that the glassential stacktrace is printed every single time the text field is clicked. Does not cause any crashes though.

Figured this out, I did an oopsie


Approve gets re-requested occasionally

Describe the bug
I'm unsure if this is a bug with our config, or in gitstream.
We have a rule to require multiple approves if the PR is > than some estimated time. And also a rule that automatically assigns a review for a person based on the files changed and who created a PR:
  complex_review:
    if:
      - {{ calc.etr >= 5 }}
    run:
      - action: set-required-approvals@v1
        args:
          approvals: {{ 3 if (calc.etr >= 10) else 2 }}

  {% for item in teams %}
  assign_reviewer_files_{{ loop.index }}:
    if:
      - {{ files | match(list=item.files) | some }}
      - {{ item.team_members | reject(term=pr.author) | reject(list=pr.reviewers) | length >= 1 }}
    run:
      - action: add-reviewers@v1
        args:
          reviewers: {{ item.team_members | reject(term=pr.author) | reject(list=pr.reviewers) }}
  {% endfor %}

  {% for item in teams %}
  assign_team_reviewer_{{ loop.index }}:
    if:
      - {{ item.team_members | includes(term=pr.author) }}
      - {{ item.team_members | reject(term=pr.author) | reject(list=pr.reviewers) | length >= 1 }}
    run:
      - action: add-reviewers@v1
        args:
          reviewers: {{ item.team_members | reject(term=pr.author) | reject(list=pr.reviewers) }}
  {% endfor %}

// reject is added because gitstream would fail if it required a review from a person that created a PR and also codeowners who github adds automatically.
The issue doesn't occur on every PR, but sometimes if the PR is >= 10min, gitstream bot re-requests a review from the last person that approved the PR:

This causes the approve to never be accepted and an infinite loop.
To Reproduce
Provided above, not sure if I can create a reproduction as it requires a bit more complex setup than usual
Expected behavior
Approve shouldn't be re-requested

Hi, I'm still looking at this issue, but just from a quick look, you can also use fail_on_error: false in add-reviewers, and then you probably don't need the reject filter on the action itself.

@vim-zz thanks. Would gitstream still request a review from others? E.g. I have 3 people in the array, one of which is a codeowner - would the other 2 get a request for a review or would it skip everything?

It shouls still assign the other 2

Running into this also with a simpler rule. It's a bit annoying as when the review is re-requested it wipes out the 'team' review showing as finished on the PR. The required approval check still passes as an individual from the team has still approved but the re-request and pending team approval on the PR looks a bit strange.
For us, it seems to actually be happening to all our PRs that I can see. A member of the team approves and then the team gets re-requested. It does not occur if someone who is not in the required/assigned team approves.
We just put this new rule into place in the last couple of days.
Potentially adding a check for the rule to see if the team has already approved before running it could work but not sure if that's a good idea.
Not that the reason we're doing add-reviewers then require-reviewers with auto_assign false is because I thought that might have been causing it and was an attempt to fix it. Was the same behaviour with just a require-reviewers in our first rule below and also happens with the second rule (only using add-reviewers).
  qa_required_approval:
    if:
      - {{ not is.hotfix }}
      - {{ is.qa_required }}
    run:
      - action: add-reviewers@v1
        args:
          reviewers: [<org>/qa]
      - action: require-reviewers@v1
        args:
          reviewers: [<org>/qa]
          also_assign: false
  qa_approval:
    if:
      - {{ not is.hotfix }}
      - {{ not is.qa_required }}
    run:
      - action: add-reviewers@v1
        args:
          reviewers: [<org>/qa]


Draft & publish agile management blog

@AlexandracmONRR @cthomasONRR @eelzi-ONRR @lpgoldstein @greensomes please feel free to review and give input on my blog draft. https://doimspp.sharepoint.com/:w:/r/sites/NRRD/_layouts/15/Doc.aspx?sourcedoc={7adf1519-03b6-40ef-b5ce-b08d43f7a2b1}&action=edit&wdPid=1eee8b21

@Maroyafaied I completed my review. Looks great!

@Maroyafaied also reviewed. Had two tiny edits/comments. You make it sound so easy!


fix(foxy-donation): "other" option text input change event

The change event was being sent upon input, causing the element to
switch from "other" into one of the presets when the user was still
typing. The element will now only send a change event when the input
event is of type change, allowing the user to finish typing.
fix #36

Oh, sure! Much nicer.


Add  to fix examples for IE11

Related to:  https://github.com/vaadin/vaadin-grid/issues/544
This solution is aimed to get rid of
window.addEventListener('WebComponentsReady', function() {
  // Async call needed here for IE11 compatibility.
  Polymer.Base.async(function() {
    ...
  });
});

for each our example, which has JS scripts.
Diff between demo-snippet.html and vaadin-demo-snippet.html: https://www.diffnow.com/?report=fn2qb
It this solution is ok, I'll apply it to all our demos to make examples work in IE11.

This change is

Reviewed 4 of 4 files at r1.
Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks broke.

demo/advanced.html, line 134 at r1 (raw file):

        <script>
          document.addEventListener('WebComponentsReady', function() {

Can this be removed?

demo/common.html, line 3 at r1 (raw file):

<!-- Common imports for all examples -->
<link rel="import" href="../../iron-demo-helpers/demo-pages-shared-styles.html">
<link rel="import" href="./vaadin-demo-snippet.html">

Can you change to ../vaadin-demo-snippet.html

demo/index.html, line 101 at r1 (raw file):

    <vaadin-demo-snippet>
      <template>
        <!--

 are not visible in IE11 demo snippet.

demo/vaadin-demo-snippet.html, line 2 at r1 (raw file):

<!--
The following is copied and adapted for IE11 better support from https://github.com/PolymerElements/iron-demo-helpers/blob/master/demo-snippet.html

This file will probably be used in our other elements also so it's more beneficial to have this as own bower package. But I think that can be created in a different PR when we are introducing this fix to some other element.

Comments from Reviewable

If the price comes to maintaining <demo-snippet> fork, then I’d better have examples not working in IE11.
Srsly, these demos are not officially used neither as a documentation, nor for marketing the elements. I’m fine that examples don’t work in IE11 as they are. When I need to check something specific in IE11, I can make a separate demo page.
We used our example element a while ago, but turned out to be limiting more then beneficial.

Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks broke.

Comments from Reviewable

Maybe send a PR to PolymerElements/iron-demo-helpers?

Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks broke.

Comments from Reviewable

You're right @platosha
https://github.com/PolymerElements/iron-demo-helpers/pull/46
I'll revisit this issue when that PR will be merged.


dotnet test --blame does not work

Description
dotnet test --blame does not work.
root@b859639f95c8:/tmp/test# dotnet test --blame
MSBUILD : error MSB1001: Unknown switch.
Switch: --blame

Steps to reproduce

Create empty xunit project
dotnet new xunit
Run test with --blame
dotnet test --blame

Expected behavior
Test to run, and eventually create Sequence.xml
Actual behavior
root@b859639f95c8:/tmp/test# dotnet test --blame
MSBUILD : error MSB1001: Unknown switch.
Switch: --blame

Diagnostic logs
I believe this is not necessary.
Environment

Tested on Win10 with SDK 2.1.4
Easiest to reproduce is on docker: docker run -it --rm microsoft/dotnet

root@b859639f95c8:/tmp/test2# dotnet --info
.NET Command Line Tools (2.1.4)

Product Information:
 Version:            2.1.4
 Commit SHA-1 hash:  5e8add2190

Runtime Environment:
 OS Name:     debian
 OS Version:  9
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /usr/share/dotnet/sdk/2.1.4/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.5
  Build    : 17373eb129b3b05aa18ece963f8795d65ef8ea54

@nothrow --blame option in it's current form is for figuring out the faulty test in case of abort, where the host process crashes unexpectedly.
The sequence file gets generated only in abort scenarios.
So in your case, as per the repro steps, --blame would not generate the sequence file.

Looks like blame changes for dotnet test are not in right branch of dotnet-cli.  We will fix this. Meanwhile you can use dotnet vstest to create sequence file.
PS C:\Users\samadala\tmp\mstest-sample> dotnet vstest C:\Users\samadala\tmp\mstest-sample\bin\Debug\netcoreapp1.0\mstest-sample.dll /blame
Microsoft (R) Test Execution Command Line Tool Version 15.6.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
The active test run was aborted. Reason: Process is terminated due to StackOverflowException.

Attachments:
  C:\Users\samadala\tmp\mstest-sample\TestResults\58f19a61-6a3b-45e7-8e2a-7a231b1a6478\Sequence.xml

Test Run Aborted.

The active Test Run was aborted because the host process exited unexpectedly while executing following test(s):
tmp.UnitTest1.TestMethod1

@nothrow , the option is available in latest dotnet sdk https://github.com/dotnet/cli/releases/tag/v2.1.300-preview2-008530 , can you please try it again.

Closing the issue as this should work in latest dotnet sdk


pa1 for attention

This PR enhances the PA1 key for situation in which the keyboard is locked.
Experience has show z/VM to not handle the normal ATTN (telnet BRK=243). However, it appears to expect PA1 even when the keyboard should otherwise be locked - PA1 serves as a general attention key. This behavior has been observed when accessing z/OS applications through z/VM.

Hi Neil,
I meant to ask... do you happen to know what modifier I need to put in VS Code's settings.json to translate a key (say `) to PA1 or ATTN?

Hi Neil,
I meant to ask... do you happen to know what modifier I need to put in VS Code's settings.json to translate a key (say ` ) to PA1 or ATTN?

In VS Code, I think the only issue I've ever had was with function keys - because they are often trapped by VS Code itself instead of passing on to the terminal. For PA1 and ATTN:
Session: NONE> help keys
KEYS:
 ATTN           - Ctrl+C or Alt+A
 CLEAR          - Ctrl+L or Alt+C
 DROP session   - Ctrl+W
 ENTER          - Enter
 End            - End
 eraseeof       - Ctrl+K or Shift+End
 Escape         - Esc
 Next session   - Alt+PgDn
 Open URL       - Ctrl+O or mouse click
 PA1            - Alt+1 or Alt+Insert
 PA2            - Alt+2 or Alt+Home
 PA3            - Alt+3
 PF1-12         - F1-12
 PF13-24        - Shift+F1-12
 Prev session   - Alt+PgUp
 Word Left      - Alt+Left
 Word Right     - Alt+Right

Ctrl+C should work for ATTN unless connected through z/VM. Alt+1 should work for PA1. On MacOS, I believe that you would use Option+1 for PA1.
If you want some custom actionsin the VS Code terminal, you may want to check out these:

https://code.visualstudio.com/docs/getstarted/keybindings
https://code.visualstudio.com/docs/terminal/advanced#_keybinding-and-the-shell

Morning!
Just realizing that I wanted to say Windows Terminal and not VS Code. It's Terminal's settings.json that requires ANSI codes that I'm looking for (for PA1 and ATTN).

I think you want to check out https://learn.microsoft.com/en-us/windows/terminal/customize-settings/actions#send-input. It describes how to bind a key to terminal input.
The terminal input value that you want for PA1 is documented in #53 in the expected code(s) column.


Add closing bracket

In the Why Attribute Routing? section, the last sentence of the first paragraph starts with an opening bracket:

(For more information about ...

...but the closing bracket is missing and I have added it.

Thank you once again for your help, @ericmutta!

Thanks @scottaddie for accepting my PRs, the ASP.NET docs are awesome!
I have avoided the technology for over a decade worrying it would be "too complicated" but the docs put that fear to rest and now I love ASP.NET! Thanks to you and the rest of the docs team for the work you do...it matters! :pray:


Release 3.10

Перед публикацией необходимо запросить обновление темплейта от Натальи (после регрессии) #1105
Релизный билд - Release 3.10.432
UPD: Release 3.10.434

[x] DEV team should create the release build
[x]  DEV team should check, that the backend version is correct and working smoothly
[x]  DEV team should update the compatibility matrix
[x]  Product Owner should conduct acceptance testing
[x]  Design Team should conduct acceptance testing
[x]  QA team should conduct regress testing
[x]  BA team should update the release notes of the plugin in Google Chrome extensions
[x]  DEV team publishes the plugin to the Chrome Web Store
[x] УБРАТЬ КОСТЫЛЬ В ТЕМПЛЕЙТЕ

Done.


Improview

added new hooks + cleaned up code + update deps (Next & react) + added support for next-image

@levimykel Updated

@levimykel final round done


ref.hasChild(prop)	does not equal ref.prop != null as the docs says

I have this setup where the intent is to make both value optional, but if you write key1 you must also write key2 at the same time. If you write only key2 it is ok.
path /keys/{uid} is AutoLoginKeys
{
    read() { auth.uid == uid }
    write() { auth.uid == uid }
}

type AutoLoginKeys
{
    key1 : String | Null,
    key2 : String | Null

    write()
    {
        (this.key1 != null && this.key2 != null) ||
        (this.key1 == null)
    }
}

This is the generated code
    "keys": {
      "$uid": {
        ".validate": "newData.hasChildren()",
        "key1": {
          ".validate": "newData.isString()"
        },
        "key2": {
          ".validate": "newData.isString()"
        },
        "$other": {
          ".validate": "false"
        },
        ".write": "(newData.child('key1').val() != null && newData.child('key2').val() != null || newData.child('key1').val() == null) && auth.uid == $uid",
        ".read": "auth.uid == $uid"
      }
    }

It uses .child(prop).val() instead of ref.hasChild(prop) that the doc claims.

The doc only describes how to convert your firebase rules to bolt. How a bolt definition translate to firebase rules is an implementation detail.
Does it matter that it uses newData.child('key1').val() != null instead of newData.hasChild('key1'). AFAIK, using either is correct; maybe one is more efficient but that's not a documentation issue.


Release version 2.0.0

Functional

[x] Confirm that the most recent PHPUnit changelogs have been checked and that the library is still feature complete for those versions supported within the PHPUnit version constraints.
[x] Update the VERSION constant in the phpunitpolyfills-autoload.php file. - PR #132
[x] Composer: check if any dependencies/version constraints need updating. - N/A

Release

[x] Add changelog for the release - PR #132
Verify that a release link at the bottom of the CHANGELOG.md file has been added.
[x] Merge this PR.
[x] Make sure all CI builds are green.
[x] Tag the release (careful, GH defaults to 2.x!).
[x] Create a release from the tag (careful, GH defaults to 2.x!) & copy & paste the changelog to it.
Make sure to copy the links to the issues and the links to the GH usernames from the bottom of the changelog!
[x] Close the milestone.
[x] Open a new milestone for the next release.
[x] If any open PRs/issues which were milestoned for the release did not make it into the release, update their milestone.

Announce

[x] Tweet about the release.

Release tweet: https://twitter.com/jrf_nl/status/1666183162769166339
Release toot: https://phpc.social/@jrf_nl/110499198870250067


Remove unused fields in primitive full trigger and unused utility functions

This PR removes an unused field ExprRepr and an unused utility function for it. It was added when developing the new error message format. However, our design has evolved since then and this field is no longer needed. This should lead to a slight reduction of build time and artifact size overhead.
Depends on PR #62

Makes sense to me! This was used only for debugging-print representations of the triggers, right?

Not really. This was introduced in one of intermediate error message formats, but not needed anymore for the concise new message format.


cmd/go: 'go install mod/mainpkg' installs a binary with a version suffix

As demonstrated in https://golang.org/cl/128137, the current behavior of go get and go install for main binaries appends a complete version suffix to the name of the binary.
This is somewhat related to #24667, but more severe. I'm not sure when the bug was introduced.
CC: @rsc @myitcv
env GO111MODULE=on

go mod init example.com/m

# get of a binary should install it to $GOPATH/bin
# BUG: vgo-tour should be installed as vgo-tour, not<EMAIL_ADDRESS>go get research.swtch.com/vgo-tour
exec<EMAIL_ADDRESS>stdout 'Hello, world.'
rm<EMAIL_ADDRESS>
# install of a binary should install it to $GOPATH/bin
# BUG: vgo-tour should be installed as vgo-tour, not<EMAIL_ADDRESS>go install research.swtch.com/vgo-tour
exec<EMAIL_ADDRESS>stdout 'Hello, world.'

This is because the directory where that command lives is called<EMAIL_ADDRESS>in the module cache. (Still a bug but that explains the bug.)

This is also further complicated if you have a replace directive to a local directory, because then the directory name of the replacement is used. It took me ages to work out why I had gopherjs and<EMAIL_ADDRESS>in my GOBIN.


Understand how go-nats uses gnatsd cluster IPs when connect to IPv6 address

See https://github.com/nats-io/gnatsd/issues/676
I'm not sure if this is a problem with go-nats or gnatsd.
But we have an application that appears to be 'discovering' the IPv4 local address of a remote gnatsd server, even though we are not publishing it in DNS.
We are assuming this is being advertised by the gnatsd server, based on the IPs it is listening on.

Turns out using the "no_advertise" option in gnatsd fixed this.


Code Design with Play 2.5

Hi,
I am quite new to the play framework and jongo.
My question is how to design your code with Play 2.5. As play uses dependency injection now and therefore a PlayJongo object needs to be injected, I think that static methods like "users()" is the wrong approach. Lets say I have a class User. How should I design the code?

It's a good question. At the moment I'm using static methods and all works fine. But should be better that someone explains exactly how to use PlayJongo using injection.

Please take a look to my comment to How to use PlayJongo from static context? question.


[NewPlugin] Zack Orndorff binja-xtensa 0.5

Please add my plugin to the repository.
Yes, I've read the instructions, especially the part about creating an actual release and creating the tag.
I either used the UI, or the hub command to create a real release.
Author: Zack Orndorff
Repo name: binja-xtensa
Release: 0.5
Link to release: https://github.com/zackorndorff/binja-xtensa/releases/tag/0.5

Heh, ninja update, I forgot to link to GitHub urls for images in my README.
Fixed in 0.5.1: https://github.com/zackorndorff/binja-xtensa/releases/tag/0.5.1

Added, thanks!


ngl-viewer: module reloading should have a blacklist (numpy, ...)

Traceback (most recent call last):
File "/Users/jbnoel/devel/node.gl/pynodegl-utils/pynodegl_utils/viewer.py", line 875, in _reload_scripts
self._reload_unsafe(initial_import)
File "/Users/jbnoel/devel/node.gl/pynodegl-utils/pynodegl_utils/viewer.py", line 834, in _reload_unsafe
reload(module)
File "/Users/jbnoel/bundle/stupeflix/lib/python2.7/site-packages/numpy/_globals.py", line 29, in
raise RuntimeError('Reloading numpy._globals is not allowed')

From Ultron
BLACK_LIST = [
"posixpath",  # returned when importing os.path
"pkg_resources",  # name is not the same when importing pkg_resources (builtin)
"numpy",  # Reloading numpy._globals is not allowed
"matplotlib",  # issue reloading tri
"six",  # used by dragon test (six.moves.urllib.parse, import httpbin)
"nose",  # used by dragon test
"Queue",  # used by dragon test
"stashy", "unittest"  # Jarvis legacy
]


🙏 Help Wanted: No Top Level Material UI 4 Imports

To make moving moving to Material UI 5 easier we need to stop using top level imports with Material UI 4 in all the frontend plugins. To help with this we have added an optional ESLint rule - no-top-level-material-ui-4-imports - which has an auto fix function to migrate the imports for us.
We need help getting this added to each of the plugins and validating there are no regressions (CI will handle this, if it's green we are good).
Process
The process is pretty easy, we'll use the adr plugin for this example:

Fork the backstage/backstage repo
Run yarn install
Open the project in your code editor
Navigate to the /plugins/adr folder
Open the .eslintrc.js file
Modify the file so it looks like this:

module.exports = require('@backstage/cli/config/eslint-factory')(__dirname, {
  rules: {
    '@backstage/no-top-level-material-ui-4-imports': 'error',
  },
});

Now when you run yarn lint you should get errors saying: "Top level imports for Material UI are not allowed"
To fix the errors run: yarn lint --fix
At this point the process is complete, commit the changes and create a PR making sure to follow the contributing guidelines

Note: it's possible that there are errors in the CI from this, you'll need to address those as they come up. Feel free to comment on this issue if you get stuck along the way.

Completed Examples
The Azure DevOps, DevTools, and Linguist plugins have been completed already and you can look at those if you need examples.
List of Plugins
The following list of plugins need to be migrated (as of 2024-04-07):
@backstage/app-defaults
@backstage/dev-utils
@backstage/frontend-app-api
@backstage/frontend-plugin-api
@backstage/integration-react
@backstage/test-utils
@backstage/plugin-auth-react
@backstage/plugin-azure-sites
@backstage/plugin-catalog-react
@backstage/plugin-cicd-statistics
@backstage/plugin-config-schema
@internal/plugin-todo-list
@backstage/plugin-git-release-manager
@backstage/plugin-github-actions
@backstage/plugin-github-pull-requests-board
@backstage/plugin-graphiql
@backstage/plugin-home-react
@backstage/plugin-ilert
@backstage/plugin-kubernetes-react
@backstage/plugin-org-react
@backstage/plugin-scaffolder-react
@backstage/plugin-search-react
@backstage/plugin-signals-react
@backstage/plugin-techdocs-react
@backstage/plugin-todo

When https://github.com/backstage/backstage/pull/23466 gets merged you can generate an up to date list by running: node scripts/list-no-top-level-material-ui-4-imports.js but make sure to check for any active PRs as well

Anyone looking at this?  I can do it if no one else is doing it.

Note:
imports of ThemeProvider are autofixed to
import ThemeProvider from '@material-ui/core/ThemeProvider'; but should be
import { ThemeProvider } from '@material-ui/core/styles';

FYI - I've updated the list of plugins that need to be migrated yesterday (2024-04-07). I did not check if there are any open PRs for these so please do that before moving forward. Thanks!!!

updated list:
WIP (following links to this issue):
#23913
@backstage/plugin-git-release-manager

#23916
@backstage/plugin-home-react

#24068
@backstage/plugin-techdocs-react

#24134
@backstage/app-defaults
app-next-example-plugin
@backstage/frontend-app-api
@backstage/frontend-plugin-api
@backstage/integration-react

pending:
@backstage/plugin-auth-react
@backstage/plugin-azure-sites
@backstage/plugin-catalog-react
@backstage/plugin-cicd-statistics
@backstage/plugin-config-schema
@internal/plugin-todo-list
@backstage/plugin-github-actions
@backstage/plugin-github-pull-requests-board
@backstage/plugin-graphiql
@backstage/plugin-ilert
@backstage/plugin-kubernetes-react
@backstage/plugin-org-react
@backstage/plugin-scaffolder-react
@backstage/plugin-search-react
@backstage/plugin-signals-react

Added a new fix for the fixer 😆 here https://github.com/backstage/backstage/pull/24138
this should solve all the wrong fixes on https://github.com/backstage/backstage/pull/23913 PR

Is this still open or left to continue?

Thanks everyone! 🙏


Hooking into collision/constraints

Hi,
Possibly odd question. Is it possible to hook into Cannon's collision or constraint handling, so as to simulate obstructions that depend on data that Cannon doesn't know about?
The use case is for a nontrivial voxel scene, where it's not feasible to create a rigid body for every voxel. If there was a way to, say, hook into wherever Cannon resolves collisions, I could inspect each body's position and velocity and create the extra collisions I need.
Or alternately, if there's some event I could catch after bodies have been given new velocities but before collisions are resolved, then I imagine I could keep a pool of static cube or plane objects, and move them to the needed positions.
Is such a thing is possible with Cannon, or could it be done if I hacked in a new event that fires partway through the step function?

Hi,
I think the easiest way to do this is to create a new Shape class that can compute its AABB, look up voxel data etc. And then write a collision handler function or two for the Narrowphase. I'm not 100% sure but it should be possible to patch these things onto the built Cannon lib.
This commit shows everything I needed to do to implement Trimesh and its collision against plane, it might be useful: https://github.com/schteppe/cannon.js/commit/b45172f1729431a08dabb4fe71b39054b5bc0094

Ahh, that makes sense. Now that I look closely, it would need to closely mirror the implementation of Heightfield, right? And basically the only code needed would be a shape class to report infinite broadphase sizes, and the relevant nearphase test functions?

Yes, you got it!

That sounds a lot more doable than I'd thought. Thanks!


[DOC] New cluster setting related to aggregation query

What do you want to do?

[ ] Request a change to existing documentation
[x] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Tell us about your request. Provide a summary of the request and all versions that are affected.
I am adding a new cluster setting search.max_aggregation_rewrite_filters to be able to dynamically change the threshold of the rewritten filters number. This is a non-negative integer and 0 means disable this optimization, currently defaults to 24.
We probably should add the document for this new setting here https://opensearch.org/docs/latest/install-and-configure/configuring-opensearch/search-settings/
What other resources are available? Provide links to related issues, POCs, steps for testing, etc.
https://github.com/opensearch-project/OpenSearch/pull/13179

Hi @bowenlan-amzn , what is your ETA for producing the doc PR? To meet entrance criteria, the PR must be open and in review by 4/30. Thanks!

@hdhalter I created the PR to add the change #7033


asciishade still does not build

Hello developer,
I reached out on IRC about building asciishade and received this guidance:
20:11 <+chzz> darkmage_> asciibird is trash compared to my editor
20:11 <+chzz> you gonna merge that meson patch so people can build it, big boy?
20:11 <+darkmage_> chzz: type 'make' in the project folder big boy
20:12 <+chzz> darkmage_: yeah it doesn't work because you get the library flags wrong
20:12 <+darkmage_> the library flags are correct
20:12 <+chzz> lolol
20:12 <+darkmage_> submit your system configuration in a bug report

When I try to build asciishade I get this:
chz@bingularity ~/src/asciishade2/asciishade $ make
gcc -Wall -Werror -c tools.c -lncursesw  -o tools.o
gcc -Wall -Werror -c canvas.c -o canvas.o
gcc -Wall -Werror -c colors.c -lncursesw  -o colors.o
gcc -Wall -Werror -c hud.c -lncursesw  -o hud.o
gcc -Wall -Werror main.c tools.o canvas.o colors.o hud.o -lncursesw  -o asciishade
/usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../x86_64-pc-linux-gnu/bin/ld: /tmp/cctwdeuS.o: undefined reference to symbol 'keypad'
/usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../x86_64-pc-linux-gnu/bin/ld: /lib64/libtinfow.so.6: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
Makefile:15: recipe for target 'asciishade' failed
make: *** [asciishade] Error 1

This means the libraries are not set correctly. I do not understand what is expected in terms of "system configuration", since plenty of other projects that use ncurses build completely fine on my system. Why is that?
Sincerely,
chzz chatman

Not enough information to reproduce the bug. Re-submit with more information.


Distracting console.log statement

I've suddenly started seeing this in my console:
maxAge 50 2

I believe this is coming from redux-devtools somewhere, though I'm not 100% sure as I can only see minified code.

PS: I'm using the Chrome extension

PS: I'm using the Chrome extension

That’s where it’s coming from, and it’s been fixed there so an update should be available soon.


Change coroutines cmake script

[x] Make building coroutines a more general way
[x] Add custom flags (e.g. \await:heapelide)
[x] Add support on mac os

Done


Slayer icon not showing proper points or streak

Before the update, upon login, it displayed points as well as streak, now it doesn't?

i guess you need have done task to update points and streak

check gem/helm


Update CHANGELOG

Documentation
Description
the CHANGELOG is missing some features; this PR adds those.
helps with #350
Why should this be added
HackTJ Live is waiting on PR #361 to be added to the next stable release of django-dbbackup—I'm sure lots of other projects are waiting for other features/bug fixes. This PR might also fully clean up #350, which means a new release could be made now.
Checklist

[ ] Tests are passing
[ ] Documentation has been added or amended for this feature / update

Thanks I will merge this in before the next release.


Rename MultithreadEventExecutorGroup to MultiThreadEventExecutorGroup…

… and MultithreadEventLoopGroup to MultiThreadEventLoopGroup
Motivation:
We should rename MultithreadEventExecutorGroup and MultithreadEventLoopGroup to MultiThread... to be more inline with SingleThreadEventExecutor / SingleThreadEventLoop.
Modifications:
Rename classes.
Result:
More consistent naming.

Even if it is wrong, this doesn't seem worth the churn. But it's also not clear it is wrong, since one would be written "single thread" but the other is virtually always "multi-thread" or "multithread".

@ejona86 well it really is not so much churn in reality... It only is so much churn in this PR as we changed on how we construct EventLoopGroups. In 4.1 really almost no-one did use MultithreadEvent*Group directly.

@ejona86 WDYT ?

As I mentioned, it's not clear that the new name is superior. To mirror SingleThread it seems it would need to be MultipleThread. Multithread seems an appropriate casing today.

https://en.wikipedia.org/wiki/Thread_(computing)#Single_threading
https://en.wikipedia.org/wiki/Thread_(computing)#Multithreading
I remember you asked me to rename it to MultiThread* long time ago, but I told you Multithread is actually correct. :-)

Alright lets close this one then


Interpolate raw body

Adds variable interpolation of raw string request bodies.
An isolated unit test of this bit can be run with:
npm run test-hoc test/unit/shim/request.js

Closes #32.

LGTM, merging. Thanks @bookmoons!


Add more condition filter to Advance Search

Is your feature request related to a problem? Please describe.
Currently, advanced search has a limited field to search, but in daily work with OM we have some need for search with more conditions. For example, we try to filter and explore only tables with lineage or description. Or filter by a range of dates which table was updated or created.
Describe the solution you'd like
Define some flags and add filters like "description" "Lineage" to allow users to quickly filter this case. Or expand the field to allow in advance search to support more cases.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Example case:

we create a bot for each type of case using API like 'UpdateDescriptionBot'
So for audit, we want to go to UI and filter out the last entity updated by UpdateDescriptionBot


[LLC] release for azure-messaging-webpubsubservice with LLC

https://github.com/Azure/azure-sdk-for-python/pull/21235
https://github.com/Azure/azure-sdk-for-python/pull/21393

https://github.com/Azure/azure-sdk-for-python/pull/21688


Not able to fetch output for add functionality in Calculator usercase

Env :
Test data
NUm 1 = 3
Num 2 = 5
Steps to reproduce

execute the calculator use case with above test data
Addition functionality

Expected result : Should get the output value 8
Actual result : Getting exception at fetching the result after addition is done

@MareesR please take it up


Expected at least one HPO term per patient, but received none for patient Reuter2020

Instead of this error message:
Expected at least one HPO term per patient, but received none for patient VanDongen2019_P2
Expected at least one HPO term per patient, but received none for patient VanDongen2019_P12
Expected at least one HPO term per patient, but received none for patient Reuter2020

It would be better to state:
23 phenopackets removed from analysis because no HPO terms were found: VanDongen2019_P2, VanDongen2019_P12, Reuter2020...

Related to #120


When spawning processes in browser plugins to run applications, in certain circumstances the plugin fails to shut down

What is your Test Scenario?
When creating a browser plugin that enables tests on Apple Simulators, I built a build pipeline in Azure DevOps on Mac that ran a single test. The browser provider code is here: https://github.com/bsmithb2/testcafe-browser-provider-idevices/ and includes the example test as well as the pipeline configuration.
The browser provider goes through the process of resetting the iphone's caches and then opening Safari in the same way that Appium does - through running an XCUITest to control the device.
This works fine on high powered build devices because the TestCafe app opens fast enough to run the test and trigger XCUITest's check to see that nothing is happening on the device before closure. On a 2018 15" i7 MBP it's about 1.2 seconds.
In Azure DevOps the test runs for about 1.4 seconds then fails. It seems that the Simulator types in the URL for the testcafe service, but then fails to see the start of a test. Adding a five second sleep after attempting to load the URL allows testcafe to continue. https://github.com/bsmithb2/testcafe-browser-provider-idevices/pull/12/commits/30da96bac7f045c799e39b7abd8a7f02905b2f0b
My belief is that the slower performance of the Azure DevOps agent means that the TestCafe service never completes the connection request before the simulator is shut down, which leads to the heartbeat never triggering.
What is the Current behavior?
Testcafe tests don't start running, and no logging is provided that enables you to identify this.
What is the Expected behavior?
Provide additional logging during browser plugin start (at least from a debug perspective) that enables provider creators to understand why the service is timing out (say for example because the heartbeat failed prior to the successful initiation of the first test)
What is your web application and your TestCafe test code?

Test Suite 'testApplicationUITests' passed at 2020-09-02 22:56:09.572.
	 Executed 1 test, with 0 failures (0 unexpected) in 26.480 (26.481) seconds
Test Suite 'testApplicationUITests.xctest' passed at 2020-09-02 22:56:09.573.
	 Executed 1 test, with 0 failures (0 unexpected) in 26.480 (26.482) seconds
Test Suite 'All tests' passed at 2020-09-02 22:56:09.574.
	 Executed 1 test, with 0 failures (0 unexpected) in 26.480 (26.484) seconds
2020-09-02 22:56:10.142 xcodebuild[4482:48341] [MT] IDETestOperationsObserverDebug: 40.061 elapsed -- Testing started completed.
2020-09-02 22:56:10.142 xcodebuild[4482:48341] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2020-09-02 22:56:10.142 xcodebuild[4482:48341] [MT] IDETestOperationsObserverDebug: 40.061 sec, +40.061 sec -- end

Test session results, code coverage, and logs:
	/Users/runner/Library/Developer/Xcode/DerivedData/testApplication-crwymenpiuxagyagerpplogjxwea/Logs/Test/Test-testApplication-2020.09.02_22-55-28-+0000.xcresult

** TEST SUCCEEDED **

Testing started on 'iPhone 11'
exit: code:0 signal:null

close: code:0 signal:null

called closebrowser

called dispose

ERROR The Safari 13.1.2 / iOS 13.6 browser disconnected. This problem may appear when a browser hangs or is closed, or due to network issues.

Type "testcafe -h" for help.
npm ERR! Test failed.  See above for more details.

##[error]Bash exited with code '1'.
Finishing: run tests

Screenshots:

Steps to Reproduce:

Remove Thread.sleep from XCUITest.
Run azure-pipelines.yml in an Azure DevOps build pipeline. Free is fine.

Your Environment details:

testcafe version:                   1.9.1
node.js version:                   8.17.0 x64
browser name and version: iPhone11 and Safari 13 Simulator
platform and version:  macOS 10.15 on Azure DevOps
other:

Thank you for your inquiry. I agree that we should need more logging in TestCafe. Currently, we use the debug to output debug logs. If you have a list of specific places where logging could help you when debugging your plugin, could you please share it here or make a PR that outputs the necessary information via the debug module?


Where is the exe and how do I use this?

Github is new to me so how does any of this work? Where and how do I run this editor?

This project is an SDK, which means it's really only useful for programmers.
You can find an example script showing usage here: https://github.com/lmaydev/OpenConstructionSet/blob/main/OpenConstructionSet.Example.Scar.PathFindingFix/Program.cs


Dropped use of idamOwner,super-user and admin-user accounts.

JIRA link
https://tools.hmcts.net/jira/browse/SIDM-7109
Change description
Used BeforeSuite functionality to create user accounts utilising random email format:
<EMAIL_ADDRESS>Stored default forename, surname and password in config and re-used for each random account
Delete account post-test-suite using teardownAll functionality
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

https://github.com/hmcts/idam-user-dashboard/blob/5a8ab461d89547899bbd05a02a45f580f7974380/src/test/functional/shared/random-data.ts#L18
In the random test data, can we change this email domain to @local.test - otherwise the gov.uk servers will probably try handle this data


Improve the way we record files on S3

Part of https://github.com/opencollective/opencollective/issues/3753
Require https://github.com/opencollective/opencollective/issues/6345

[x] We would like to better organize the files on S3 with subfolders. Suggested: :imageType/:uuid.:extension.
[x] We want to store the filename on S3. We'll either or (both):

Store as S3 metadata (see Content-Disposition: attachment; filename="foo.bar")
Or use the filename in path (e.g. :imageType/:uuid/:filename.:extension)

Resolved by https://github.com/opencollective/opencollective-api/pull/8443


Cache timezone

Cache user's timezone to prevent numerous queries to ip-api.com

added to session variable


Compile errors for enumeration referencing super

I was trying to structure my protos directory and ran into a compile error that I haven't been able to fix. I've extended your snazzy shirt example with the below directory structure and sizes.proto and items.proto files respectively:
protos
    |-items
           |-items.proto
    | -sizes
           |-sizes.proto

syntax = "proto3";

package snazzy.size;

enum Size {
    SMALL = 0;
    MEDIUM = 1;
    LARGE = 2;
}

syntax = "proto3";

package snazzy.items;

import "sizes/sizes.proto";

message Shirt {
	string color = 1;
	snazzy.size.Size size = 2;
}

The rust compiler cannot find the enumeration via super reference:
#[derive(Clone, Debug, PartialEq, Message)]                                      ^^^^^^^ Could not find size in super
#[derive(Clone, Debug, PartialEq, Message)]
pub struct Shirt {
    #[prost(string, tag="1")]
    pub color: String,
    #[prost(enumeration="super::size::Size", tag="2")]
    pub size: i32,
}

Any thoughts on how I can work around this or if I'm missing something in the setup?

What does your .rs file containing the include! calls look like?  I think in this case the include! calls need to be in module trees which mimic the proto packages.  You can see an example of this here: https://github.com/danburkert/prost/blob/master/tests/src/packages/mod.rs#L5-L14.

Got it - thanks for pointing me to the test examples. I ended up needing to restructure the proto packages and nest the module trees similar to your example.
Thanks!

This latest fix fixed the compile errors I previously reported.
Thanks!

Ah, sorry about that.  I should have put two and two together that you were likely hitting that.  I'm planning on doing a 0.2.1 soon in order to get the fix out, because I think it's likely to be a common issue (I ran into it independently).

0.2.1 has been published, and includes the fix.  Thanks for the report!


Make CRD version configurable

Fixes #1089
Adds config.ResourceConfig.APIVersion to be able to
override the generated version for a CRD

Issue #, if available: #1089
Description of changes:
This PR proposes a new configuration field named APIVersion (JSON-serialized name api_version) in config.ResourceConfig that allows overriding versions of specific CRDs generated by the Crossplane codegen pipeline. If a specific version string is not configured for a CRD-type, the default version specified with the --version command-line argument is used for backwards-compatibility. An example configuration overriding the version for the CloudFront Distribution resource is as follows:
resources:
  "Distribution":
    api_version: "v1beta1"
ignore:
  resource_names:
    - FieldLevelEncryptionProfile
    - Invalidation
    - KeyGroup
    - OriginRequestPolicy
    - PublicKey
    - StreamingDistribution
    - RealtimeLogConfig
    - MonitoringSubscription
    - FieldLevelEncryptionConfig
  field_paths:
    - DistributionConfig.CallerReference
    - Origins.Quantity
    - OriginAccessIdentityConfig.CallerReference

An example invocation ack-generate crossplane cloudfront --output <output path> --generator-config-path generator-config.yaml using the above configuration yields the following file structure:
❯ tree
.
├── apis
│   └── cloudfront
│       ├── v1alpha1
│       │   ├── zz_cache_policy.go
│       │   ├── zz_cloud_front_origin_access_identity.go                                                                                [0/941]
│       │   ├── zz_doc.go
│       │   ├── zz_enums.go
│       │   ├── zz_function.go
│       │   ├── zz_groupversion_info.go
│       │   ├── zz_response_headers_policy.go
│       │   └── zz_types.go
│       └── v1beta1
│           ├── zz_distribution.go
│           ├── zz_doc.go
│           ├── zz_enums.go
│           ├── zz_groupversion_info.go
│           └── zz_types.go
├── generator-config.yaml
├── go.mod
├── go.sum
└── pkg
    └── controller
        └── cloudfront
            ├── cachepolicy
            │   ├── zz_controller.go
            │   └── zz_conversions.go
            ├── cloudfrontoriginaccessidentity
            │   ├── zz_controller.go
            │   └── zz_conversions.go
            ├── distribution
            │   ├── zz_controller.go
            │   └── zz_conversions.go
            ├── function
            │   ├── zz_controller.go
            │   └── zz_conversions.go
            └── responseheaderspolicy
                ├── zz_controller.go
                └── zz_conversions.go

12 directories, 26 files

Without the resources configuration block, all resources are under v1alpha1 version as expected:
❯ tree .
.
├── apis                                                                                [0/1036]
│   └── cloudfront
│       └── v1alpha1
│           ├── zz_cache_policy.go
│           ├── zz_cloud_front_origin_access_identity.go
│           ├── zz_distribution.go
│           ├── zz_doc.go
│           ├── zz_enums.go
│           ├── zz_function.go
│           ├── zz_groupversion_info.go
│           ├── zz_response_headers_policy.go
│           └── zz_types.go
├── generator-config.yaml
├── go.mod
├── go.sum
└── pkg
    └── controller
        └── cloudfront
            ├── cachepolicy
            │   ├── zz_controller.go
            │   └── zz_conversions.go
            ├── cloudfrontoriginaccessidentity
            │   ├── zz_controller.go
            │   └── zz_conversions.go
            ├── distribution
            │   ├── zz_controller.go
            │   └── zz_conversions.go
            ├── function
            │   ├── zz_controller.go
            │   └── zz_conversions.go
            └── responseheaderspolicy
                ├── zz_controller.go
                └── zz_conversions.go

11 directories, 22 files

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

/ok-to-test

/approve
Looks good but I will let @jaypipes approve on new GeneratorConfig field name.
And I will also let @A-Hilaly to approve as he is working on supporting multi-version CRs for ACK controllers.

Looks like this change is only impacting ackgenerate crossplane and doesn't touch any other components. I'm fine with merging this if it's solving crossplane issue and satisfies their versioning criterias. However ACK and crossplane CRD versioning philosophies will take different paths.
I pinged @ulucinar and @muvaf on slack to chat about this subject
/hold for now

Hi @A-Hilaly,
I saw some existing work around supporting multiple versions for the generated CRDs, and I think you are referring to that work. This implementation follows @muvaf's suggestion here. Let's get together as you suggested to discuss the path we would like to take.

Thanks @ulucinar ! Meeting scheduled tomorrow with Upbound folks @ulucinar and @muvaf.
Unholding the PR
/unhold

/retest

/retest all

/test all

/test s3-controller-test

@muvaf, as detailed in the description of this PR, we will need to move generator-config.yamls to unversioned API group roots. And for resources with API version configurations, we will generate CRDs at the storage API version.

/test all

Thank you @A-Hilaly, very much appreciated!


IGNITE-18555 .NET: Thin 3.0: Enable Gradle daemon in tests

--no-daemon removed to speed up local test execution
IGNITE_DOTNET_GRADLE_OPTS env var added to TC to keep the existing behavior: https://ci.ignite.apache.org/admin/editBuildParams.html?id=buildType:ApacheIgnite3xGradle_Test_RunNetTests

LGTM


chore: invalidate all older sessions

A new cookie name is used for sessions, so all older sessions will no longer
be valid.
I could not really test this, cause there is a ton of required env variables,
but I checked the source for nextauth and it should work :tm:
I didn't run prettier, cause it formatted a lot of unrelated files, which would pollute the PR

yeah I tried this but we then need to check for and handle invalid sessions which led to some secondary issues and I didn't have the time to handle that properly. Will look into it over the weekend

Old sessions shouldn't be an issue
This will simply look for a different cookie.
The existence of another (old) cookie is irrelevant.


Optional credentials (IRSA/WebIdentity)

Make credentials optional.
This allows avoiding static credentials, for example on EKS with IRSA: https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts.html

I forgot to mention that I don't write much typescript, so please feel free to implement a different way :)


Failing to deploy

Describe the bug
After pressing deploy, it gets to step 5 and stops.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
Failed to load XML file.
To Reproduce

Install a few mods like the ones I have
Press deploy
watch error log

Expected behaviour
mods deploy as expected
System Info (please complete the following information):

Linux Flavour: Steam Deck (SteamOS
Window Manager: KDE Plasma
Lamp Version: 1.0.11

Additional context
Add any other context about the problem here.

Huh. After trying it like 10 times, it now works right after I submitted the issue. Weird.

Thats strange, was it a permissions issue. I've heard steamdecks can be tempermental

ill be marking this as complete for now as i do not know the cause.


Revert "Bump typescript from 4.5.5 to 4.8.3"

Reverts libscie/ResearchEquals.com#679.
Should not have been merged as #533 is blocked.


quantum-transfer-learning /c2q_transfer_learning_ants_bees.ipynb

with n_epochs=30 I get accuracy of 0.47. but you mentioned
"Remark: To reproduce the results of [the paper], num_epochs should be set to 30 which may take many hours. We suggest to first try with num_epochs=1, just to check that everything runs smoothly."

Hi @mehrnia, the code in this repo is not maintained. I recommend that you go to the PennyLane demo on Quantum Transfer Learning instead.


Enable Open/Delivery Reporting

What?

Change timestamp from Ms to Sec.
Enable Open/Delivery Reporting

CC @pusher/mobile

Codecov Report

Merging #39 into master will decrease coverage by 0.28%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
- Coverage   66.25%   65.97%   -0.29%
==========================================
  Files          29       27       -2
  Lines         726      720       -6
  Branches       13       13
==========================================
- Hits          481      475       -6
  Misses        245      245

Impacted Files
Coverage Δ

Sources/NetworkService.swift
0% <0%> (ø)
:arrow_up:

Tests/FeatureFlagsTests.swift
100% <100%> (ø)
:arrow_up:

Tests/TrackTests.swift
100% <100%> (ø)
:arrow_up:

Tests/SDKTests.swift
100% <100%> (ø)
:arrow_up:

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 9366337...3b53cfc. Read the comment docs.