BUG: Cannot compile on OpenIndiana

Describe your issue.
I am trying to compile scipy in OpenIndiana. I am using python 3.10, which was compiled with gcc version 10.3.0. I have installed successfully numpy using
pip3.10 install numpy
I have cloned the github code of scipy and when I enter
pip3.10 install . -v --user
compilation stops with
      |          ^~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/empty_iterator.hpp:39:19: warning: '{anonymous}::pythonic::types::empty_iterator& {anonymous}::pythonic::types::empty_iterator::operator++(int)' defined but not used [-Wunused-function]
     39 |   empty_iterator &empty_iterator::operator++(int)
        |                   ^~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/empty_iterator.hpp:34:19: warning: '{anonymous}::pythonic::types::empty_iterator& {anonymous}::pythonic::types::empty_iterator::operator++()' defined but not used [-Wunused-function]
     34 |   empty_iterator &empty_iterator::operator++()
        |                   ^~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/empty_iterator.hpp:29:8: warning: 'bool {anonymous}::pythonic::types::empty_iterator::operator<(const {anonymous}::pythonic::types::empty_iterator&) const' defined but not used [-Wunused-function]
     29 |   bool empty_iterator::operator<(empty_iterator const &) const
        |        ^~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/empty_iterator.hpp:24:8: warning: 'bool {anonymous}::pythonic::types::empty_iterator::operator!=(const {anonymous}::pythonic::types::empty_iterator&) const' defined but not used [-Wunused-function]
     24 |   bool empty_iterator::operator!=(empty_iterator const &) const
        |        ^~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/empty_iterator.hpp:19:8: warning: 'bool {anonymous}::pythonic::types::empty_iterator::operator==(const {anonymous}::pythonic::types::empty_iterator&) const' defined but not used [-Wunused-function]
     19 |   bool empty_iterator::operator==(empty_iterator const &) const
        |        ^~~~~~~~~~~~~~
  In file included from /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/NoneType.hpp:7,
                   from /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/slice.hpp:5,
                   from /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/core.hpp:36,
                   from scipy/interpolate/_rbfinterp_pythran.cpp:1:
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/builtins/id.hpp:36:8: warning: 'long int {anonymous}::pythonic::builtins::id(const bool&)' defined but not used [-Wunused-function]
     36 |   long id(bool const &t)
        |        ^~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/builtins/id.hpp:31:8: warning: 'long int {anonymous}::pythonic::builtins::id(const double&)' defined but not used [-Wunused-function]
     31 |   long id(double const &t)
        |        ^~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/builtins/id.hpp:26:8: warning: 'long int {anonymous}::pythonic::builtins::id(const long int&)' defined but not used [-Wunused-function]
     26 |   long id(long const &t)
        |        ^~
  In file included from /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/core.hpp:35,
                   from scipy/interpolate/_rbfinterp_pythran.cpp:1:
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/float.hpp:54:7: warning: 'static float {anonymous}::pythonic::from_python<float>::convert(PyObject*)' defined but not used [-Wunused-function]
     54 | float from_python<float>::convert(PyObject *obj)
        |       ^~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/float.hpp:50:6: warning: 'static bool {anonymous}::pythonic::from_python<float>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
     50 | bool from_python<float>::is_convertible(PyObject *obj)
        |      ^~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/float.hpp:36:13: warning: 'static long double {anonymous}::pythonic::from_python<long double>::convert(PyObject*)' defined but not used [-Wunused-function]
     36 | long double from_python<long double>::convert(PyObject *obj)
        |             ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/float.hpp:31:6: warning: 'static bool {anonymous}::pythonic::from_python<long double>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
     31 | bool from_python<long double>::is_convertible(PyObject *obj)
        |      ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/float.hpp:26:11: warning: 'static PyObject* {anonymous}::pythonic::to_python<float>::convert(float)' defined but not used [-Wunused-function]
     26 | PyObject *to_python<float>::convert(float d)
        |           ^~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/float.hpp:22:11: warning: 'static PyObject* {anonymous}::pythonic::to_python<double>::convert(double)' defined but not used [-Wunused-function]
     22 | PyObject *to_python<double>::convert(double d)
        |           ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/float.hpp:17:11: warning: 'static PyObject* {anonymous}::pythonic::to_python<long double>::convert(long double)' defined but not used [-Wunused-function]
     17 | PyObject *to_python<long double>::convert(long double d)
        |           ^~~~~~~~~~~~~~~~~~~~~~
  In file included from /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/core.hpp:34,
                   from scipy/interpolate/_rbfinterp_pythran.cpp:1:
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static long long int {anonymous}::pythonic::from_python<long long int>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:179:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    179 | PYTHONIC_INT_FROM_PYTHON(signed long long, LongLong)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<long long int>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:179:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    179 | PYTHONIC_INT_FROM_PYTHON(signed long long, LongLong)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static long long unsigned int {anonymous}::pythonic::from_python<long long unsigned int>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:178:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    178 | PYTHONIC_INT_FROM_PYTHON(unsigned long long, ULongLong)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<long long unsigned int>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:178:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    178 | PYTHONIC_INT_FROM_PYTHON(unsigned long long, ULongLong)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static long int {anonymous}::pythonic::from_python<long int>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:177:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    177 | PYTHONIC_INT_FROM_PYTHON(signed long, Long)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<long int>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:177:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    177 | PYTHONIC_INT_FROM_PYTHON(signed long, Long)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static long unsigned int {anonymous}::pythonic::from_python<long unsigned int>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:176:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    176 | PYTHONIC_INT_FROM_PYTHON(unsigned long, ULong)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<long unsigned int>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:176:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    176 | PYTHONIC_INT_FROM_PYTHON(unsigned long, ULong)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static int {anonymous}::pythonic::from_python<int>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:175:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    175 | PYTHONIC_INT_FROM_PYTHON(signed int, Int)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<int>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:175:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    175 | PYTHONIC_INT_FROM_PYTHON(signed int, Int)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static unsigned int {anonymous}::pythonic::from_python<unsigned int>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:174:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    174 | PYTHONIC_INT_FROM_PYTHON(unsigned int, UInt)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<unsigned int>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:174:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    174 | PYTHONIC_INT_FROM_PYTHON(unsigned int, UInt)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static short int {anonymous}::pythonic::from_python<short int>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:173:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    173 | PYTHONIC_INT_FROM_PYTHON(signed short, Short)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<short int>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:173:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    173 | PYTHONIC_INT_FROM_PYTHON(signed short, Short)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static short unsigned int {anonymous}::pythonic::from_python<short unsigned int>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:172:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    172 | PYTHONIC_INT_FROM_PYTHON(unsigned short, UShort)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<short unsigned int>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:172:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    172 | PYTHONIC_INT_FROM_PYTHON(unsigned short, UShort)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static signed char {anonymous}::pythonic::from_python<signed char>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:171:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    171 | PYTHONIC_INT_FROM_PYTHON(signed char, Byte)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<signed char>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:171:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    171 | PYTHONIC_INT_FROM_PYTHON(signed char, Byte)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:165:8: warning: 'static unsigned char {anonymous}::pythonic::from_python<unsigned char>::convert(PyObject*)' defined but not used [-Wunused-function]
    165 |   TYPE from_python<TYPE>::convert(PyObject *obj)                               \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:170:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    170 | PYTHONIC_INT_FROM_PYTHON(unsigned char, UByte)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:160:8: warning: 'static bool {anonymous}::pythonic::from_python<unsigned char>::is_convertible(PyObject*)' defined but not used [-Wunused-function]
    160 |   bool from_python<TYPE>::is_convertible(PyObject *obj)                        \
        |        ^~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:170:1: note: in expansion of macro 'PYTHONIC_INT_FROM_PYTHON'
    170 | PYTHONIC_INT_FROM_PYTHON(unsigned char, UByte)
        | ^~~~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<long long int>::convert(long long int)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:155:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    155 | PYTHONIC_INT_TO_PYTHON(signed long long)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<long long unsigned int>::convert(long long unsigned int)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:154:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    154 | PYTHONIC_INT_TO_PYTHON(unsigned long long)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<long unsigned int>::convert(long unsigned int)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:149:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    149 | PYTHONIC_INT_TO_PYTHON(unsigned long)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<int>::convert(int)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:148:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    148 | PYTHONIC_INT_TO_PYTHON(signed int)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<unsigned int>::convert(unsigned int)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:147:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    147 | PYTHONIC_INT_TO_PYTHON(unsigned int)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<short int>::convert(short int)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:146:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    146 | PYTHONIC_INT_TO_PYTHON(signed short)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<short unsigned int>::convert(short unsigned int)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:145:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    145 | PYTHONIC_INT_TO_PYTHON(unsigned short)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<signed char>::convert(signed char)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:144:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    144 | PYTHONIC_INT_TO_PYTHON(signed char)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<unsigned char>::convert(unsigned char)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:143:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    143 | PYTHONIC_INT_TO_PYTHON(unsigned char)
        | ^~~~~~~~~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:135:13: warning: 'static PyObject* {anonymous}::pythonic::to_python<char>::convert(char)' defined but not used [-Wunused-function]
    135 |   PyObject *to_python<TYPE>::convert(TYPE l)                                   \
        |             ^~~~~~~~~~~~~~~
  /tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran/pythonic/types/int.hpp:142:1: note: in expansion of macro 'PYTHONIC_INT_TO_PYTHON'
    142 | PYTHONIC_INT_TO_PYTHON(char)
        | ^~~~~~~~~~~~~~~~~~~~~~
  error: Command "c++ -m64 -Wno-unused-result -Wsign-compare -DNDEBUG -g -O3 -Wall -I/usr/openssl/1.1/include -I/usr/lib/amd64/libffi-3.2.1/include -DFFI_NO_RAW_API -D_REENTRANT -fPIC -DENABLE_PYTHON_MODULE -D__PYTHRAN__=3 -DPYTHRAN_BLAS_NONE -I/tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran -I/tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/numpy/core/include -I/tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/numpy/core/include -Ibuild/src.solaris-2.11-i86pc.64bit-3.10/numpy/distutils/include -I/opt/gnu/python/include/python3.10 -c scipy/interpolate/_rbfinterp_pythran.cpp -o build/temp.solaris-2.11-i86pc.64bit-3.10/scipy/interpolate/_rbfinterp_pythran.o -MMD -MF build/temp.solaris-2.11-i86pc.64bit-3.10/scipy/interpolate/_rbfinterp_pythran.o.d -std=c++11" failed with exit status 1

  ########### EXT COMPILER OPTIMIZATION ###########
  Platform      :
    Architecture: unsupported
    Compiler    : gcc

  CPU baseline  :
    Requested   : optimization disabled
    Enabled     : none
    Flags       : none
    Extra checks: none
    Requested   : optimization disabled

  CPU dispatch  :
    Enabled     : none
    Generated   : none
  CCompilerOpt.cache_flush[809] : write cache to path -> /opt/sources/BACKUP/scipy/scipy/build/temp.solaris-2.11-i86pc.64bit-3.10/ccompiler_opt_cache_ext.py

  ########### CLIB COMPILER OPTIMIZATION ###########
  Platform      :
    Architecture: unsupported
    Compiler    : gcc

  CPU baseline  :
    Requested   : optimization disabled
    Enabled     : none
    Flags       : none
    Extra checks: none
    Requested   : optimization disabled

  CPU dispatch  :
    Enabled     : none
    Generated   : none
  CCompilerOpt.cache_flush[809] : write cache to path -> /opt/sources/BACKUP/scipy/scipy/build/temp.solaris-2.11-i86pc.64bit-3.10/ccompiler_opt_cache_clib.py
  ERROR: Failed building wheel for scipy
ERROR: Could not build wheels for scipy, which is required to install pyproject.toml-based projects

Reproducing Code Example
NOT A PYTHON ERROR

Error message
NOT A PYTHON ERROR MESSAGE

SciPy/NumPy/Python version information
1.21.4 sys.version_info(major=3, minor=10, micro=0, releaselevel='final', serial=0)

Hi @asyropoulos. Did you follow the compilation guides from the developer's documentation?

Also, since the above error log shows that something is wrong with pythran, I have installed the following:
$ pip3.10 install pythran -v --user
Using pip 21.3.1 from /export/home/aposyro/.local/lib/python3.10/site-packages/pip (python 3.10)
Collecting pythran
Using cached pythran-0.10.0-py3-none-any.whl (4.3 MB)
Collecting beniget~=0.4.0
Using cached beniget-0.4.1-py3-none-any.whl (9.4 kB)
Collecting ply>=3.4
Using cached ply-3.11-py2.py3-none-any.whl (49 kB)
Collecting gast~=0.5.0
Using cached gast-0.5.3-py3-none-any.whl (19 kB)
Requirement already satisfied: numpy in /export/home/aposyro/.local/lib/python3.10/site-packages (from pythran) (1.21.4)
Installing collected packages: gast, ply, beniget, pythran
changing mode of /export/home/aposyro/.local/bin/pythran to 755
changing mode of /export/home/aposyro/.local/bin/pythran-config to 755
Successfully installed beniget-0.4.1 gast-0.5.3 ply-3.11 pythran-0.10.0

So OpenIndiana is based on Illuminos, which is a new Unix/BSD-like OS (https://www.openindiana.org/overview/illumos/) - guess you're one of the first people trying to build SciPy there.
It's unclear to me what the problem is - there's a bunch of compiler warnings, but only the last line errors (breaking lines at 80 chars for readability):
  error: Command "c++ -m64 -Wno-unused-result -Wsign-compare -DNDEBUG -g -O3
  -Wall -I/usr/openssl/1.1/include -I/usr/lib/amd64/libffi-3.2.1/include
  -DFFI_NO_RAW_API -D_REENTRANT -fPIC -DENABLE_PYTHON_MODULE -D__PYTHRAN__=3
  -DPYTHRAN_BLAS_NONE
  -I/tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/pythran
  -I/tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/numpy/core/include
  -I/tmp/pip-build-env-myi6tepl/overlay/lib/python3.10/site-packages/numpy/core/include
  -Ibuild/src.solaris-2.11-i86pc.64bit-3.10/numpy/distutils/include
  -I/opt/gnu/python/include/python3.10 -c
  scipy/interpolate/_rbfinterp_pythran.cpp -o
  build/temp.solaris-2.11-i86pc.64bit-3.10/scipy/interpolate/_rbfinterp_pythran.o
  -MMD -MF
  build/temp.solaris-2.11-i86pc.64bit-3.10/scipy/interpolate/_rbfinterp_pythran.o.d
  -std=c++11" failed with exit status 1

The order of build flags looks odd, nothing else jumps out for me.
@serge-sans-paille does anything look familiar to you?

@asyropoulos can you share the full log, I suspect an error before the warnings extracted :-)

@serge-sans-paille is the expert for fixing the issue. In the meantime you might be able to complete compilation by setting the environment variable SCIPY_USE_PYTHRAN=0

@serge-sans-paille I am attaching the full log here. Now I rebuilding using SCIPY_USE_PYTHRAN=0
OUT.txt

Rebuilding with SCIPY_USE_PYTHRAN=0 was successful.
OUT2.txt

Thanks, the error is crystal clear: _P is a reserved macro under you system, which is totally valid (identifiers starting with _ followed by a capital letter are reserved. Pythran should mangle the name of these identifiers to avoid such situations. As a workaround, renaming the python identifier _P to something else. should work too.

Thank you very much for the quick reply, I will have a closer look at it tomorrow.

In file /usr/include/iso/ctype_iso.h which is included from /usr/include/ctype.h there are the following definitions, which cause the problem:
#ifdef  __cplusplus
extern "C" {
#endif
#define _U      0x00000001      /* Upper case /
#define _L      0x00000002      / Lower case /
#define _N      0x00000004      / Numeral (digit) /
#define _S      0x00000008      / Spacing character /
#define _P      0x00000010      / Punctuation /
#define _C      0x00000020      / Control character /
#define _B      0x00000040      / Blank /
#define _X      0x00000080      / heXadecimal digit */

gotcha!

Fixed in #15580, but there's no backport to the 1.8 series yet

This fix was included in scipy 1.8.1, closing.


Avoid presenting for new installation

Is your feature request related to a problem?
Hi, is it possible to show only if the app is already installed and open? so only after the first update?
What solution would you like?

What alternatives have you considered?

Any additional context?
No response

Yes, you can simply subclass the WhatsNewEnvironment and implement your very own logic when and how a WhatsNew gets presented to a user. Read more here.

Hey Sven, can you add an example.


Add a db.$query function to perform queries using the existing transaction

From the discussion:
This won't use the transaction:
await db.$transaction(async () => {
  await db.$adapter.query(`some sql`)
})

Let's add a $query that will use it:
await db.$transaction(async () => {
  await db.$query(`some sql`)
})

By the way, I would appreciate if you could somehow expose the current raw pg connection (client) for the active transaction.
The reason I'm asking is because I developed a set of hacks to run Objection/Knex transacting code inside a orchid/pqb transaction (for reusing legacy code). The only way I was able to pull the current connection was db.user.internal.transactionStorage.getStore().client, but:

The store is typed incorrectly as AdapterBase not TransactionState.
The code becomes coupled to a certain ORM table, because transactionState only lives in a local variable in orchidORM().

These are minor nuances, so not a big deal if it's hard to achieve or leads to unwanted implications.

The idea was to hide the transaction object completely so that transactions are fully managed by the ORM.
Currently, until db.$query is not implemented, you can use db.user.internal.transactionStorage.getStore().adapter as a workaround to get the object of the AdapterBase type that has the query method, why you don't like this type?
TransactionState is the object returned by getStore(), it contains the db adapter.

The code becomes coupled to a certain ORM table

It's a single transactionStore for a whole ORM, and a separate transactionState is created for each transaction, I don't see any problems here

The idea was to hide the transaction object completely so that transactions are fully managed by the ORM.

Absolutely! This is all not needed when using Orchid only. However in a mixed environment, I want to pass the pg connection to legacy and/or third-party code.

get the object of the AdapterBase type that has the query method, why you don't like this type?

Because I need the actual raw pg connection which I can then trick knex to use when it calls my fake acquireConnection.

TransactionState is the object returned by getStore(), it contains the db adapter.

Oh. Indeed it does now. I was testing with orchid-orm 0.4.14, the store was typed and structured differently. In 0.6.0, I see it has adapter which I can cast to TransactionAdapter to pull client in a type-safe way. Thanks.

I don't see any problems here

The problem is that the orchid-knex adapter is dependent on specific orchid db (it uses hard-wired db.user which other dbs may not have). If there were something like db.$transactionAdapter that wouldn't be the case.

Added $query and $queryArrays methods: docs
The transaction client is still not easy to obtain, not sure how to make and if it is worth making this clearer, for now you can define such a helper:
import { PoolClient } from 'pg';

const getTransactionClient = (q: Query): PoolClient => {
  return q.internal.transactionStorage.getStore()!.adapter.client as PoolClient;
}

getStore() will return undefined in case it's not called inside a transaction.
adapter.client has type unknown for the future when we'll have support for more than just pg.

Thanks! That helper is just fine. This is an edge-case operation anyway.

For the reference, the actual code would be:
await db.$transaction(async () => {
  const client = getTransactionClient(db.$queryBuilder)
})

yes, exactly


[bug]: Error in documentation of combobox

Describe the bug
There's an error in the documentation of Combobox ( https://ui.shadcn.com/docs/components/combobox ). The components after the CommandInput needs to wrapped around CommandList according to the Command docs ( https://ui.shadcn.com/docs/components/command ).

Affected component/components
Combobox
How to reproduce

Go to the code for the examples given in the Combobox docs ( https://ui.shadcn.com/docs/components/combobox )
Running that code as a component gives an error.

Codesandbox/StackBlitz link
https://ui.shadcn.com/docs/components/combobox#combobox
Logs
No response
System Info
none

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

I will be fixing this. Not a bug, its just a typo ig.

I will be fixing this. Not a bug, its just a typo ig.

I initially marked it as a bug instead of a typo because it's not just a simple spelling mistake, it causes an error that is quite complex to debug, especially for newbies like me. However, if it's not a significant issue, I will use the 'typo' label instead in the future.

Quick fix for this: Just wrap your <CommandEmpty> and <CommandGroup> with <CommandList>

Quick fix for this: Just wrap your <CommandEmpty> and <CommandGroup> with <CommandList>

Yes, I just reported so that the documentation can be fixed.

Same problem, it almost cost me a morning to check if there are any problems with my understanding of react

I was banging my head for 3 days on this particular issue, tried several different things, and for a newbie, as @Invito101 said not easy to find out what is causing this issue until I decided to look at the issue log. was such a simple fix. I agree this needs to be updated in the document, otherwise people like me almost would have given up on combobox and used something else just because we couldnt get to this...


return"field" in Module will be evaluated as returntrue or returnfalse

Bug report
Hi, Webpack team. I found a bug when I upgrade it's version in my work project.
in version 5.71.0, there is a commit eb5d12415052b58098aee261c42ffc85aa20b03b.
It can evaluate the statement like "Component" in React to true on build time.
However, the is a edge case:
function foo() {
  return"Component" in "React"
}

that will be transformed to "returntrue". It misses a space before "true"

What is the current behavior?
returntrue or returnfalse will be a transformed result.
And will cause runtime error as returntrue is not defined
If the current behavior is a bug, please provide the steps to reproduce.
reproduce
I create a PR for fix it. #15760.
comment this line https://github.com/webpack/webpack/pull/15760/files#diff-82d9a7fff0d25b8895057d34b65f83eb05cc28f11ed58132609ea7c565030745R113
and run
 yarn jest test/TestCasesDevelopment.test.js -t harmony-export-import-specifier

the test will produce an error:

What is the expected behavior?
Should be transformed to return true or return false

Other relevant information:
webpack version:  5.71.0
Node.js version: v16.14.1
Operating System: Linux
Additional tools: N/A

/cc @vankop maybe related to in feature

this is merged in main branch, please wait for release..

fixed in webpack@latest


Installation Error

It's giving me this error when installing the requirements:
Successfully built fast-bss-eval ctc-segmentation pyworld ci-sdr antlr4-python3-runtime jaconv lit distance
Failed to build sentencepiece
ERROR: Could not build wheels for sentencepiece, which is required to install pyproject.toml-based projects

apologies for the late response...
which OS are you using... windows or ubuntu? Also if you can share screenshot of the error

resolved


mTLS works between client and IBM MQ if the client keystore has certificate only for serverAuth, not clientAuth

As the title mentions,  mTLS works between client and IBM MQ if the client keystore has certificate only for serverAuth, not clientAuth.  But should not be the case.
for example, folloing the official guide here https://developer.ibm.com/tutorials/configuring-mutual-tls-authentication-java-messaging-app/ and we can establish the mTLS connection successfully and the client log has the following Produced client Certificate handshake message
javax.net.ssl|DEBUG|1E|pool-1-thread-1|2023-10-24 15:00:55.214 UTC|CertificateMessage.java:330|Produced client Certificate handshake message (
"Certificates": [
  "certificate" : {
    "version"            : "v3",
    "serial number"      : "2A FC D8 2F BB 31 14 F4",
    "signature algorithm": "SHA256withRSA",
    "issuer"             : "CN=openshift-service-serving-signer@1628590423",
    "not before"         : "2023-10-09 10:17:28.000 UTC",
    "not  after"         : "2025-10-08 10:17:29.000 UTC",
    "subject"            : "CN=jms-bulk-messaging.fate-sample-app-dev.svc",
    "subject public key" : "RSA",
    "extensions"         : [
      {
        ObjectId: <IP_ADDRESS>.4.1.23<IP_ADDRESS>.1 Criticality=false
      },
      {
        ObjectId: <IP_ADDRESS> Criticality=false
        AuthorityKeyIdentifier [
        KeyIdentifier [
        0000: 0A 3C 75 40 B5 A3 8B F3   88 E9 C0 68 52 FE 03 1C<EMAIL_ADDRESS>        0010: E3 80 3D DE                                        ..=.
        ]
        ]
      },
      {
        ObjectId: <IP_ADDRESS> Criticality=true
        BasicConstraints:[
          CA:false
          PathLen: undefined
        ]
      },
      {
        ObjectId: <IP_ADDRESS> Criticality=false
        ExtendedKeyUsages [
          serverAuth
        ]
      },
      {
        ObjectId: <IP_ADDRESS> Criticality=true
        KeyUsage [
          DigitalSignature
          Key_Encipherment
        ]
      },
      {
        ObjectId: <IP_ADDRESS> Criticality=false
        SubjectAlternativeName [
          DNSName: jms-bulk-messaging.fate-sample-app-dev.svc
          DNSName: jms-bulk-messaging.fate-sample-app-dev.svc.cluster.local
        ]
      },
      {
        ObjectId: <IP_ADDRESS> Criticality=false
        SubjectKeyIdentifier [
        KeyIdentifier [
        0000: 98 E7 99 77 B0 3A ED AA   21 51 65 D6 44 34 45 48  ...w.:..!Qe.D4EH
        0010: B0 1E 10 48                                        ...H
        ]
        ]
      }
    ]},
  "certificate" : {...},
  "certificate" : {...}
]
)

More specifically the certificate has the field
        ExtendedKeyUsages [
          serverAuth
        ]

and in my understand, it should prevent the mTLS handshake being successful because it doesn't have clientAuth.  But it seems that the IBM MQ doesn't care about ExtendedKeyUsages.

The TLS handshake is managed as part of the IBM MQ software, and I don't think anything you've mentioned is related to this sample repository.  Can I please suggest that you raise this as a support ticket against the MQ software?


Create plant detail view page

This needs to be a new page component that looks like an encyclopedia article for each plant, with the live feed on the right side as with the rest of the site.

Existing plants in database become the datastore for this feature. They stop being favorites records.
We will need to also add a new collection for Favorites, where each Favorite record in this collection is just a pointer to a user and a pointer to a plant.

There will be a 1:1 relationship between Plants in our database, and Species records in the Trefle database. The data in Plants should be as complete as possible an archive of the response from the Trefle species detail endpoint.

As with the existing UserFavorites functionality, the detail page should fetch the information through the Trefle API, but with the added functionality that it first checks to see if the Plant record exists in the local collection.


feat(es/typescript): inline enum

Description:
Inline enum if possible.
BREAKING CHANGE:
Related issue (if exists):

Does this fix #940?

Partially.
It does not work across files.


upgrade dependencies based on security offers

Fixes Security Issues
Tested

As long as it has been thoroughly tested that none of the dependencies break anything :)

The problem when they do not serve very well, for instance some of the dependencies reported high usage of CPU which was also an issue on Haaukins platform. It may have a link or not, but it is better to update dependencies since they are improving bugs/issues and other important features in their repository as well.
I have tested functionalities and common points on Haaukins after update, it did not complain anything, I might miss something but this is why Haaukins has development/staging server as well. What I think is that, it would be nice to run it for some time, on staging server to extensive tests if you think it is required.

I am thinking to merge the changes to develop. What are your feedbacks @Lanestolen and @Mikkelhost  ?


Error compiling due to wasm-bindgen version

Hi,
first of all nice work. I was wondering if you could lend me a hand, since I am experiencing and issue when trying to compile using cargo leptos watch. The error is the following:
   Finished dev [unoptimized + debuginfo] target(s) in 44.24s        Cargo finished cargo build --package=rusty_llama --lib --target-dir=/home/albert/Desktop/llama-rust/target/front --target=wasm32-unknown-unknown --no-default-features --features=hydrate        Front compiling WASM Error: at/home/albert/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-leptos-0.2.17/src/compile/front.rs:47:30`
Caused by:
0: at /home/albert/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-leptos-0.2.17/src/compile/front.rs:122:10
1:
   it looks like the Rust project used to create this wasm file was linked against
   version of wasm-bindgen that uses a different bindgen format than this binary:

     rust wasm file schema version: 0.2.89
        this binary schema version: 0.2.92

   Currently the bindgen format is unstable enough that these two schema versions
   must exactly match. You can accomplish this by either updating this binary or
   the wasm-bindgen dependency in the Rust project.

   You should be able to update the wasm-bindgen dependency with:

       cargo update -p wasm-bindgen --precise 0.2.92

   don't forget to recompile your wasm file! Alternatively, you can update the
   binary with:

       cargo install -f wasm-bindgen-cli --version 0.2.89

   if this warning fails to go away though and you're not sure what to do feel free
   to open an issue at https://github.com/rustwasm/wasm-bindgen/issues!`

I have tried with both options, using cargo update -p wasm-bindgen --precise 0.2.92 and cargo install -f wasm-bindgen-cli --version 0.2.89, but it doesn't seem to work. Any ideas?
Thank you very much

I had a similar issue, switching the to wasm version 0.2.89 in the Cargo.toml file and disabling the metal feature in Cargo.toml worked for me.

Hi @darrenkim247,
I tried your suggestion and now I am getting the following error when compiling:
error[E0433]: failed to resolve: use of undeclared crate or module `futures`
 --> src/app.rs:4:5
  |
4 | use futures::stream::SplitSink;
  |     ^^^^^^^ use of undeclared crate or module `futures`

error[E0432]: unresolved import `futures`
  --> src/app.rs:27:9
   |
27 |     use futures::{SinkExt, StreamExt};
   |         ^^^^^^^ use of undeclared crate or module `futures`

error[E0599]: no method named `split` found for struct `gloo_net::websocket::futures::WebSocket` in the current scope
    --> src/app.rs:39:45
     |
39   |         let (sender, mut recv) = connection.split();
     |                                             ^^^^^ method not found in `WebSocket`
     |
    ::: /home/albert/.cargo/registry/src/index.crates.io-6f17d22bba15001f/futures-util-0.3.30/src/stream/stream/mod.rs:1582:8
     |
1582 |     fn split<Item>(self) -> (SplitSink<Self, Item>, SplitStream<Self>)
     |        ----- the method is available for `gloo_net::websocket::futures::WebSocket` here
     |
     = help: items from traits can only be used if the trait is in scope
help: the following trait is implemented but not in scope; perhaps add a `use` for it:
     |
1    + use futures_util::stream::stream::StreamExt;
     |

Some errors have detailed explanations: E0432, E0433, E0599.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `rusty_llama` (lib) due to 3 previous errors

The strange thing is that the futures module is present in the cargo.toml file. Any ideas?

You might have to remove the 'optional' tag from the futures module present in Cargo.toml. Afterwards, remove "futures" as a dependency in csr, hydrate, or ssr

The targets should have unique names.
Consider changing their names to be unique or compiling them separately.
This may become a hard error in the future; see https://github.com/rust-lang/cargo/issues/6313.
Compiling rusty_llama v0.1.0 (C:\Users\ASUS ExpertBook\source\repos\rusty_llama)
error[E0432]: unresolved import api::ws
--> src/main.rs:3:5
|
3 | use api::ws;
|     ^^^^^^^ no ws in api
For more information about this error, try rustc --explain E0432.
error: could not compile rusty_llama (bin "rusty_llama") due to 1 previous error
I get this error, so how I can fix it :_(

The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see rust-lang/cargo#6313. Compiling rusty_llama v0.1.0 (C:\Users\ASUS ExpertBook\source\repos\rusty_llama) error[E0432]: unresolved import api::ws --> src/main.rs:3:5 | 3 | use api::ws; | ^^^^^^^ no ws in api
For more information about this error, try rustc --explain E0432. error: could not compile rusty_llama (bin "rusty_llama") due to 1 previous error
I get this error, so how I can fix it :_(

I got rid of this error by removing the use api::ws. I did change tokio dependancy to tokio = { version = "1", features = ["full"] } aswell so that may have done something as well, but not checked.


topLevelAwait is still under experimental section

Feature request

According to the latest docs, topLevelAwait should be used via experimental section. In the same time, top level await is already a part of specification (stage 4). I think it's time already to remove it from experimental section.
What is the expected behavior?
Excluded topLevelAwait from experimental section.
What is motivation or use case for adding/changing the behavior?
No reason to consider this feature as experimental since it's already in specification.
How should this be implemented in your opinion?
Just exclude this option and this behaviour should be enabled by default.
Are you willing to work on this yourself?
no

Hello, yeah, you are right, I think we can enable it by default
@TheLarkInn What do you think?

@alexander-akait @TheLarkInn Hello, are there any updates?

@iSokrat  Yeah, do you want to send a PR, I think we are ready to enable it by default

@alexander-akait  Didn't plan to do this is initially, maybe, some day I could do this but not for now. In case if there is someone else who wants to do this - feel free to prepare needed changes


Add Persian website translation

There was Persian translation added in this PR: https://github.com/ro31337/libretaxi/pull/435 for application.
It was not yet merged to master at the moment of writing, and it's on the way (it's our priority). But what we need now the website http://libretaxi.org translated to Persian. It's important, because Telegram is wide-spread in Persian speaking countries.
You just need to translate index.html in this repository. It's pure HTML. You can skip adding links to every page, I can take care of them.
Thank you! <3 <3 <3

This PR: https://github.com/ro31337/libretaxi-www/pull/21

@danialbehzadi thanks for your contribution. Language will be added to the app in a day or two.


Suggestion: When feature file is empty cucumber fails silently

While trying to write some .feature file I forgot to write something in a .feature file.
To my big surprise the build succeeds eventhough there is something in stderr.
I would like to suggest that the build fails in case that there is something in stderr.

As this project is now deprecated, CommerceHub will not be contributing further on this ticket.  Please feel free to fork the project and work on it further yourself under the terms of the project license if desired.


Traveltime maps

Proximity maps based on least cost paths and frictions (in raster.py)

Function to calculate the costs of travelling for LPG can be taken from raster.py

A Technology subclass for LPG and another for Biomass where the travel time datasets are read. These datasets can be previously produced using the Layer classes. Ideally, we should create a method under the OnSSTOVE class, which creates all of these layers automatically, based on the tech_specs file and adds them to the right subclasses, but for now we can handle it like this:
#create model
nepal = OnSSTOVE(project_crs=3857, cell_size=(1000, 1000))
output_directory = 'test'
nepal.output_directory = output_directory

#read and reproject population
path = r"data\population_npl_2018-10-01.tif"
os.makedirs('test/rasters/population', exist_ok=True)
population = RasterLayer('rasters', 'population', layer_path=path, resample='sum')
population.reproject(3857, 'test/rasters/population', 1000, 1000)

#read tech_specs
path = r"05. OnSSTOVE test case\GQ_test_file_tech_specs.csv"
nepal.read_tech_data(path)

#read LPG supply points and friction layer
path = r"data\Nepal_Gas_12Jun2021_Final4.shp"
lpg_supply = VectorLayer('vector', 'LPG_supply', layer_path=path)
os.makedirs('test/vector/LPG_supply', exist_ok=True)
lpg_supply.reproject(3857, 'test/vector/LPG_supply')

path = r"data\2020_motorized_friction_surface.geotiff"
mot_friction = RasterLayer('rasters', 'Mot_friction', layer_path=path, resample='average')
os.makedirs('test/rasters/Mot_friction', exist_ok=True)
mot_friction.align(population.path, 'test/rasters/Mot_friction')

#add the friction layer to the lpg supply points and calculate travel time
lpg_supply.add_friction_raster(mot_friction)
lpg_supply.travel_time('test/vector/LPG_supply')

#add travel time (distance_raster) to the LPG technology and calculate transport costs
nepal.techs['LPG'].travel_time = lpg_supply.distance_raster
nepal.techs['LPG'].transportation_cost()

The travel time will be saved as a RasterLayer in the travel_time variable of the LPG class and the transport cost as a numpy array in the transport_cost variable.


[3.11] Improve locking in Async Logger (#19989)

Scope & Purpose
*Right now the Logger holds a very large lock. The lock is held whenever the background thread flushes a queued log message, which is potentially slowed down by IO. If we try to do a new direct log entry in that period we need to wait for this lock to be released. With this PR the Lock is changed such that: We get a WriteLock whenever we modify the Loggers we use, but we only take a read-lock when we let the loggers print. This way we can have two or more threads using the loggers.
In turn the output message of the Logger, which does the IO operation, is guarded with a WriteLock.
In addition this PR adds an upper bound to the amount of messages in the queue. This is right now hard-coded and should not have effect under normal circumstances. If the logging is configured to use an extremely slow device we protect us here against accumulating too much memory in log messages. If the Limit is reached, we will start to directly log the message, which will have a performance impact. Also this may change the ordering of Log messages.
*
Note to reviewer: Please take extra care, this PR fiddles with Locks, and has potential to introduce undesired dead-locks.
This potentially fixes: https://arangodb.atlassian.net/browse/BTS-1273

[x] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[ ] Backport for 3.11: (Please link PR)
[ ] Backport for 3.10: (Please link PR)

Related Information
(Please reference tickets / specification / other PRs etc)

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket: https://arangodb.atlassian.net/browse/BTS-1273
[ ] Design document:

Jenkins green:
https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/32037/


silly question

Hi All,
I've not had time yet to investigate an actual firmware swap using this yet.
However, something came to mind.
In the description you describe searching the code for suitable points to call to achieve various things.
The bootloader in these items is almost guaranteed to be the same for all....
Have you searched the bootloader for suitable jump points?
I'm sure there is a non-encrypted dump in the SDK... if not, my python flasher mod includes a decrypter...
br,
Simon

I have to agree though that this is super weird and more likely are probably only a some different bootloaders out there and we may have seen all of them already. It may make a lot of sense to try and pool these together from the different devices and see if there may be a very small number of different chains which can be tried on a device blindly in a reasonably short period of time.


Pass the DB_PORT in case of mysql

It seems like the variable DB_PORT isn't passed to temporal-sql-tool when the DB is mysql.

What was changed

Why?

Checklist

Closes

How was this tested:

Any docs updates needed?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks!


Feat: User alpine docker images to speed up build time

I’ve tried using an alpine image, turns out it had no gcc installed. Attempting to manually install what’s needed is more time consuming than using a non-alpine image.
Deciding to stick with the current go image and closing this issue.


Fix accuracy circle color not being set correctly

Closes #482

Android color ints are not supported in Expressions so we need to convert them to RGBA strings. Try
locationFeature.addStringProperty(PROPERTY_ACCURACY_COLOR, PropertyFactory.colorToRgbaString(accuracyColor));

instead of pushing the Android int @cammace.


nixos/pam: add fingerprint auth ordering

Description of changes
Add option to allow use of a password if you cannot Ctrl+C fingerprint authentication (due to a lack of a shell). Described in Arch Wiki and one potential discussion thread
Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@RaitoBezarius I saw you reviewed another Pam PR, could you take a look at this?
I noticed you wanted a test included on the  other PR - I'm not sure how to form an independent test for this PR that wouldn't be fluff, since it seems to be just an ordering thing. But I can write one up if you'd like.

@RaitoBezarius I saw you reviewed another Pam PR, could you take a look at this?
I noticed you wanted a test included on the other PR - I'm not sure how to form an independent test for this PR that wouldn't be fluff, since it seems to be just an ordering thing. But I can write one up if you'd like.

I still need a test for any PAM PRs that I judge having the potential of breaking things (almost all of them), that's my policy.
If you can provide a test, we can proceed.

@RaitoBezarius I added a test as requested, and also added the other existing tests to the pam passthru.tests attribute for automatic testing in the future.

Also please cleanup the commit history according to the CONTRIBUTING guide

Closing this, as the refactor of the main Pam module to allow explicit ordering of contents is a more generalized solution that addresses the original concern of this PR!


refactor: add data attributes in TaskFieldRenderer instead of returning them

Description

TaskFieldRenderer now adds the data attributes to an HTMLelement instead of returning them (At the end of the day, this is what we need the data attributes for)
Reworked tests to show this behaviour
TaskLineRenderer calls to get the data attributes are shorter, taskToHtml more readable and comprehensive
AttributeDictionary now used only in TaskFieldRenderer.test.ts

Motivation and Context

Simpler code
Prepare to for further refactoring to make rendering and layout code more flexible towards new features
Get rid of DataAttributes in src (Possible in test as well, but need to update tests, probably good for another PR)

How has this been tested?
Modified unit tests.
Types of changes

[x] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[x] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[x] My change has adequate Unit Test coverage.

Terms

[x] My contribution follow this project's contributing guide
[x] I agree to follow this project's Code of Conduct

OK I'm going to push a tiny change and then merge...


Help the Play team in its Pillarbox investigations

As a Play SRG team member I would like to better understand Pillarbox so that I can better understand what to do in my own product.
Hints
See related Play SRG issue.
Acceptance criteria

The Pillarbox team remains available for any help the Play team might need.

Tasks

[x] Ask the Play team how we can help.

We have informed the Play SRG team that we are available when needed and already discussed some topics. It might be superfluous to keep a dedicated task in our backlog, though.


Linking module fails when user has uninstalled Mail.app

Description
I set up linking to send an email using 'mailto:anyone@anywhere.com?subject=hi' as the URL.  When I clicked the link it crashes... because the user has REMOVED the mail app!
Reproduction

On a test device, remove the mail app.
Add the following code after adding the required dependencies:
Linking.openURL('mailto:anyone@anywhere.com?subject=hi').catch(err => console.error('An error occurred', err));

Solution
I'm not quite sure tbh.
Additional Information

React Native version: 0.40
Platform: iOS.
Development Operating System: Mac OSX 10.12.3
Dev tools: XCode 8.2.1,
Device: iOS 10

We're cutting down on the number of outstanding issues, in order to allow us to focus. I'm closing this issue because it has been open for over 60 days with no activity. If you think it should still be opened let us know why.

This is still an issue - please reopen

@lprhodes do you happen to have more information about the cause of the crash? Any logs or specific error message? This sounds like something that can be easily fixed by checking if the system supports opening the URL.

I'll follow up with the crash report later but basically messages:// is returning that it's supported so you then go to open it but it crashes because it's been deleted. It wouldn't be so much of an issue but "catch" doesn't work so the app has no choice but to crash
On 1 Jun 2017, 4:15 AM +1000, Héctor Ramos<EMAIL_ADDRESS>wrote:

Reopened #13114.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Fully native apps do manage to not crash when performing the same functionally. I'll figure it out and submit a PR
On 1 Jun 2017, 4:15 AM +1000, Héctor Ramos<EMAIL_ADDRESS>wrote:

Reopened #13114.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I found some references in the code to a change introduced in iOS 9 where the developer must whitelist schemes in Info.plist under the LSApplicationQueriesSchemes key. The expected behavior for opening a non-whitelisted scheme is for the operation to fail silently however.

Yeah it’s not that unfortunately (though admittedly I did forget about that so I spent some time scratching my head). That correctly fails silently.
On 1 Jun 2017, 6:07 AM +1000, Héctor Ramos<EMAIL_ADDRESS>wrote:

I found some references in the code to a change introduced in iOS 9 where the developer must whitelist schemes in Info.plist under the LSApplicationQueriesSchemes key. The expected behavior for opening a non-whitelisted scheme is for the operation to fail silently however.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I have the issue with a mailto:email link.
Linking.canOpenURL return supported = true when actually Mail.app is uninstalled and crashes the app when Linking.openURL is called, the catch is not called.

I have the same here.

hey @lprhodes @drpiou did you guys figure out a work around for this?
I think ideally, it would open up some default emailer eg: inbox (google) or gmail and only throw an error if no emailer is found.


clothes showing up when I remove shirt of my ped

whenever I remove shirt of my ped , there appears a new shirt on the ped I dont know whats the issue

@vineetkotian56 you have custom clothes added to your server. You need to set the right numbers in game/build/client.js. Search for {male:[[1,0]],female:[[1,0]]}}


Wireframes

Work with the students to define a project direction that would be interesting in both a classroom setting, and of potentially intrinsic interest, to the audience. Sketch a mockup of the interface for the developers to work with.

Thanks Pauline for the sketch, Moritz and Sophia for the inputs & brainstorming.


Upgraded to qcop>=0.5.1 and qcio>=0.8.1 to fix QCElemental default sn…

…eaky rotation and translation of Molecule coordinates without user consent.

Adding py.typed to qcio and qcop now has mypy issues. Fix in a separate PR.


turn off warning for UnmarshalXML, MarshalXML, MarshalXMLAttr, UnmarshalXMLAttr

It's implementation of standard xml interface, what kind of comments do you expect here? In most cases it will be something like:
//Unmarshal XXX
//Marshal XXX

Do you really think that it will improve somehow quality of documentation?
E.g. there is no warning about String()
P.S.: right now, in some cases, we have to comment that stuff to 'pass rules' of quality code (e.g.: https://github.com/avelino/awesome-go/issues/2024)

Do you really think that it will improve somehow quality of documentation?

It is generally better not to assume stupidity or hostility. Instead of thinking that we somehow love unnecessary comments, you could assume the simpler and less offending option: nobody thought to add these methods to the list of exceptions, and nobody asked for them to be on the list yet, either.

P.S.: right now, in some cases, we have to comment that stuff to 'pass rules' of quality code (e.g.: avelino/awesome-go#2024)

Surely golint cannot be made responsible for how people use it. In fact, the README specifically states that

The suggestions made by golint are exactly that: suggestions. Golint is not perfect, and has both false positives and false negatives. Do not treat its output as a gold standard

Sorry, if it sounded offended - nothing like that.
I created ticket because maybe it's good idea to remove such warnings. But the same time it was a question to get idea why they exists - maybe I missed something and they are here on purpose.


Org members can only see databases in db list that they created

db list in an org appears to only be populated by the databases that the user created.  However, org members can operate on those database just fine if they know its name (create token, shell, destroy).
Could be a database list cache issue.

@CodingDoug do you still see this happening? Should be fixed by #535.
Please close if doesn't happen anymore.


Add DocShadow

Original repo: https://github.com/CXH-Research/DocShadow-SD7K

Wonderful! Thanks for everything!


Fix missing location validator in mssql-dbms-registered

Of course yes. Actually the non-registered dbms service applies this validator. It is a missing in registered dbms service.
Even though there is exception, I think this validator is mainly for spelling checking.


BlazeClient withTcpNodelay(true) is not working on AIX

I am using http4s 0.20.9 on AIX 7.2
Blaze client performs very poorly. (following code)
    val client: Resource[IO, Client[IO]] = BlazeClientBuilder[IO](blockingEC)
      .withRequestTimeout(90.seconds)
      .withIdleTimeout(15.seconds)
      .withTcpNoDelay(true)
      .resource

With jetty client, no problem.
    val clientJetty = Resource.make(IO.delay {
      val jettyClient = new HttpClient()
      jettyClient.setTCPNoDelay(true)
      jettyClient
    })(_ => IO.pure(())).flatMap(JettyClient.resource[IO](_))

I reviwed source code but applyChannelOption is there!

I'm sorry nobody got back to this sooner.  I need more details on "very poorly", and I don't have access to an AIX machine to chase this.  If this still happens on a still supported version (0.21 or later), please reopen, and we'll see what we can figure out.


controllers: don't retry unrecoverable k8s API errors

It is possible that a write to an object in kubernetes can make it
inherently invalid. For instance, exceeding etcd's 1MB storage limit. In
this case, there is no point to retrying over and over again, since
it'll never recover. Also, having unrecoverable retries clogs the
working queues, preventing more useful work from being done, and also
makes unnecessary requests to the k8s API, making us hit our API request
throttling limit.
Here, we're considering that any .Create() or .Update() that results in
an HTTP 422 "Unprocessable Entity" error is unrecoverable. We can check
that by calling kerrors.IsInvalid(err).
Closes #15

This has been superseded by #91.


During broadcasting the stream has been struck & blur several times

Hi,
We are facing two problems in iOS platform while review your demo example app “LFLiveKit”.

During broadcasting the stream has been struck & blur several times. We also changed the resolution but not fixed.
Reference :
1.  http://<IP_ADDRESS>//WebRTCAppEE//streams//Stream_cn7qBtwKcptQ.mp4

Technical Stack
iOS Version : 10.15.7
Xcode : 12.2
Swift : 4.2
Please help us to solve this problem.  Thanks in advance.

how i can fix issue #358 . Thanks


lb_config priority not parsed in rancher-compose.yml

Rancher versions:
rancher/server: 1.6.0 - 1.6.5
rancher/agent: 1.2.2 - 1.2.5
Infrastructure Stack versions:
healthcheck: 0.3.1
ipsec: 0.11.2
network-services: 0.7.0
scheduler: 0.7.5
kubernetes (if applicable): na
Docker version: (docker version,docker info preferred)
v1.12.6 - 17.03.2-ce
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
RancherOS v1.1.0 (4.9.45)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
AWS
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
ha w external DB
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

deploy load balancer with selector rules
deploy service with lb_config in either docker-compose.yml or rancher-compose.yml

rancher-compose.yml
version: '2'
services:
  webapp:
    scale: 1
    start_on_create: true
    lb_config:
      certs: []
      port_rules:
      - hostname: example.com
        path: /
        target_port: 80
        priority: 20

Expected Results:
rancher-compose.yml
version: '2'
services:
  webapp:
    scale: 1
    start_on_create: true
    lb_config:
      certs: []
      port_rules:
      - hostname: example.com
        path: /
        target_port: 80
        priority: 20

Actual Results:
rancher-compose.yml
version: '2'
services:
  webapp:
    scale: 1
    start_on_create: true
    lb_config:
      certs: []
      port_rules:
      - hostname: example.com
        path: /
        target_port: 80

I got the same issue, plus, I found that internal loadbalaner is implemented with a shortest match algorithm when parsing the path attributes.
For example, for the following rancher-compose.yml, both of the requests for /app and /application will be routed to web1.
version: '2'
services:
  web1:
    scale: 1
    start_on_create: true
    lb_config:
      port_rules:
      - path: /app
        target_port: 80
  web2:
    scale: 1
    start_on_create: true
    lb_config:
      port_rules:
      - path: /application
        target_port: 80

@yamingwa I think for the second case, you can try path: /app/ instead of path: /app.

@yasker Thanks for your reply. It works.
However, I think it will be better if we can implement the prioriry attribute in service side rancher-compose.yml, right?
Moreover, this shortest match algorithm is not implemented by rancher loadbalancer, but by haproxy with a path_beg method in acl rule.

@yamingwa The priorities should be there, but it seems not exposed when exporting. We're checking it.

@yasker there is no priority field in the schema of targetPortRule  (/v2-beta/schemas/targetportrule)

@loganhz @yasker yes, today we only support priority for the port rules of the LB service, not the target service port rules. We should see if we should enable it on per targetPortRule basis

Thanks for your report!
With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.
If you think we should keep this issue open, please let me know.


Create RetryHelper instance only at sendRequest() method

This plugin sometimes hung up(processing stopped but doesn't finish with error).
To avoid this problem I changed implementation to create RetryHelper only at ElasticsearchHttpClient.sendRequest() and close RetryHelper every time.

Problem is still existing.
I may overlooked something.

I found job hang always happens when I don't specify following config.
exec:
  min_output_tasks: 1
``

Thank you for fixing.

I found job hang always happens when I don't specify following config.
Probably embulk-base-resetclient doesn't works properly when output task > 1.

Can you investigate this issue before merging this PR into master? I think that we need to know the severity and the extent of the impact by this issue.

@muga Thanks. Yeah, it's better to check embulk-base-restclient or Embulk more.
But this fix should better than current version.


Standardized container image for gofmt and lint

Having a standardized image allows uniform application of format and
lint checking across multiple host platforms.    It also makes it easier to maintain the common rules over-time.
Signed-off-by: Chris Evich<EMAIL_ADDRESS>

/approve

Could you add some README to ./contrib/gate/ to describe the purpose of it?
For CI, the image should still be build locally to avoid a chicken-egg bootstrapping problem for PRs changing those scripts.

Could you add some README to ./contrib/gate/ to describe the purpose of it?

Oh sure, good idea.  Should it have anything more than a link to CONTRIBUTING.md?

For CI, the image should still be build locally to avoid a chicken-egg bootstrapping problem for PRs changing those scripts.

Yes this is true, though hopefully a fairly rare event.  It would be possible to automate this, but I'll leave that as a learning exercise for someone else :D

Oh sure, good idea. Should it have anything more than a link to CONTRIBUTING.md?

Just a short description plus the link sounds good to me, thanks a lot.

@cevich, thanks! LGTM
Can you squash the commits into a single one, so we can merge it?

@vrothberg done, and I added a lil more text to the readme.

@baude PTAL.  What I plan to do in .cirrus.yml is set the checkout directory to /usr/src/libpod instead of a volume-mount.   Can that work with papr and openshift?  If not, let me know what changes you'd like and I'll do 'em.

/lgtm


Get. BottomSheet Animation effect stuck

ATTENTION: DO NOT USE THIS FIELD TO ASK SUPPORT QUESTIONS. USE THE PLATFORM CHANNELS FOR THIS.
Fill in the template. Issues that do not respect the model will be closed.
Describe the bug
Get. BottomSheet Animation effect stuck
The get. bottomSheet animation effect is stuck, which is more obvious if there are multiple Bottom_sheets
Reproduction code
NOTE: THIS IS MANDATORY, IF YOUR ISSUE DOES NOT CONTAIN IT, IT WILL BE CLOSED PRELIMINARY)
example:
To Reproduce
Expected behavior
Optimize the animation transition curve
Screenshots
If applicable, add screenshots to help explain your problem.
Flutter Version:
2.8.1
Getx Version:
lastet
Describe on which device you found the bug:
ex: any
Minimal reproduce code

I've tested it and it's a little bit different than showCupertinoModalPopup animation,

The animation is not very smooth


Update GenevAERS web site with CII Badge sticker

Folks
a. I am trying to locate who has access to the HTML source for the site https://genevaers.org/
b. I would like to add the CII Badge sticker to that page
c. here is the HTML code to be added
<imgsrc="https://bestpractices.coreinfrastructure.org/projects/4181/badge">
d. it will reflect the current status of this badge which currently is approved and in a GREEN status
many thanx
bob

Kip and I have access and can add it to the site
Get Outlook for Androidhttps://aka.ms/ghei36

From: bobmcc9 @.>
Sent: Sunday, March 14, 2021 9:02:51 PM
To: genevaers/community @.>
Cc: Subscribed @.***>
Subject: [genevaers/community] Update GenevAERS web site with CII Badge sticker (#110)
Folks
a. I am trying to locate who has access to the HTML source for the site https://genevaers.org/
b. I would like to add the CII Badge sticker to that page
c. here is the HTML code to be added
<imgsrc="https://bestpractices.coreinfrastructure. org/projects/4181/badge">
d. it will reflect the current status of this badge which currently is approved and in a GREEN status
many thanx
bob
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/genevaers/community/issues/110, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOWICQMVN5FPQQF6PWXZLQDTDVTEXANCNFSM4ZFULHMQ.

The badge has been added to the sidebar menu on the right side of the page


Wireshark BT5 Plans / Timeline?

Just wondering if this tool will be updated for BT5 or not, and if so, what timeline does that look like

Seconding this. Anyone working on support for BT5 already?

BT5 support would be great :)

@viet-nguyen-matternet, @sandeshworld, @Mf-ff99.  It is done.  If you have the nRF52840 dongle with the latest sniffer installed on the dongle, the latest dissector should work.  be sure the latest nrf sniffer plugin is installed in wireshark as well.  It provides sniffing options such as "Scan and follow devices on LE Coded Phy".  This will "follow" the BT5 frames.


How to get the status code of the API response

Hello everyone. I have a question regarding the HTTP responses and how I can inspect the status code.
Let's say we have this code
return this.client.customers
      .get(customerId)
      .then((response: CustomerObject) => response as VoucherifyCustomer)
      .catch((error) => {
          // Handle error
      });

How can we inspect the status code of the response when there is an error?

Hello @redjolr
The status code should always be included in the code property of the error object.
Example:
voucherify.customers
	.get('non_existing_customer')
	.then(result => {
		console.log('Result: ', result)
	})
	.catch(error => {
		console.log('Error: %j', error.code)
	})

Output is:
Error: 404

I am closing this issue for now, feel free to re-open in case of more questions

Hello @darekg11
But why haven't you guys typed this code field? It does not exist in any type definitions that I looked at (like VoucherifyError for example)

@redjolr Let me reopen this issue, I will try to take a look at it tomorrow and see if we can release new version with patch bump 🤔

Dear @redjolr I did some investigation and came up with following conclusions:

In case of promise rejection type is always any, it can not be casted: https://github.com/Microsoft/TypeScript/issues/6283#issuecomment-240804072 + https://github.com/microsoft/TypeScript/issues/39680#issuecomment-1328976622 so I could add VoucherifyAPIError type but person using SDK would still need to explictly cast error in catch like so:

.catch((error: VoucherifyAPIError)

which I find cumbersome 🤔

Even in case of solution mentioned above the error is not always going to be related to Voucherify because in case of network failure, ie: timeout -  error is going to come back from axios itself so it won't have any of Voucherify related fields.

I don't have a strong opinion on how this should be approached.

@redjolr do you mean that AxiosError should be thrown instead of that current custom object?
If so then this is going to be a breaking change and I would like to avoid that

Generally speaking if there is connection error, for example: timeout / not reachable DNS or whatever else then error thrown will indeeed be the one from Axios
See example:
const { VoucherifyServerSide } = require('@voucherify/sdk')

const voucherify = VoucherifyServerSide({
	applicationId: '5452e923-810c-4880-83fb-65202fab8e28',
	secretKey: '6a0f56de-b5a8-4893-bedd-79711134108b',
	apiUrl: 'https://notasdadadawe.com',
})

voucherify.customers
	.get('non_existing_customer')
	.then(result => {
		console.log('Result: ', result)
	})
	.catch(error => {
		console.log(error)
	})

....long error
    _currentUrl: 'https://notasdadadawe.com/v1/customers/non_existing_customer',
    [Symbol(kCapture)]: false
  },
  response: undefined,
  isAxiosError: true,
  toJSON: [Function: toJSON]

In such case, the error is AxiosError, in any other case when request reached the API and there was no timeout then rejected errror should always contain code field.
I don't really see a way to type all of this to make it work in all cases.

@darekg11  Thank you for your insight to the problem. However we still have the problem of the untyped code field. I would suggest to improve the VoucherifyError type like this:
VoucherifyError {
  code?: HttpStatusCode,
  name: string;
  message: string;
  stack?: string;
}

In addition, you can include the underlying error that causes the VoucherifyError in another field like this:
VoucherifyError {
  code?: HttpStatusCode,
  name: string;
  message: string;
  stack?: string;
  cause: AxiosError | unknown;
}

The cause field would contain the original error. In this way, you can expose the original error, without causing a breaking change as you mentioned in one of your previous comments.

@redjolr Thank your for your insights
It's still going to be breaking change for some people that might right now check if error has isAxiosError property.
In your approach (if I understand you correctly), this would no longer works since that would be now under cause property.
On top of that I just assumed people use isAxiosError field, they still might rely on some other field and it's hard to provide it all

@darekg11 Ok, but can you at the very least add the optional code?: HttpStatusCode, field to VoucherifyError ?

@redjolr yes that is okay, I was trying to come up with solution to throw only single error in all of those cases to not require devs to do (for simplicity):
error: VouchieryError | AxiosError

but it's impossible without breaking change

HttpStatusCode won't be added.
We really do not want add any extra dependencies to that SDK, it's just going to be a simple number type

HttpStatusCode won't be added. We really do not want add any extra dependencies to that SDK, it's just going to be a simple number type

Yeah that's ok. Just number is enough

+1 @redjolr
I also need this, otherwise, I cannot handle errors correctly.

+1 @redjolr

Hello @redjolr @ActionSeeker @amado10
Could you please take a look at following pull request: https://github.com/voucherifyio/voucherify-js-sdk/pull/188 to make sure that it solves your issue?

@darekg11 Thanks for the PR. I see that you only improved the typing of the VoucherifyError. I take it that you are not planning to add the cause: AxiosError | unknown; field inside the VoucherifyError?

@darekg11 It is useful to inspect the HttpError body response. We would like to log that. That would be very useful when we face a critical error in Production to understand what caused it

@darekg11 Also if I have to deal with a next version major bump of the SDK, I may as well create an API client layer by myself right now, then write the code twice to

@redjolr I will add cause field.
Major bump won't happen anytime soon, I am just noting stuff down as it comes to make sure that everything is covered.

@darekg11 Greatly appreciated :pray:

@redjolr Sorry I am not 100 % convinced to including bare axios error object by default in VouchierfyError
The downside for me is that for all current user of this SDK this would start printing plaintext used API Keys to console if somebody is doing straight:
console.log(error)
And for some of our customer this might be treated as sensitive data leak.
Would you be OK with new option passed to SDK that you must set explicitly to true in order to have that field exposed?

@redjolr I have pushed commit: 7dbd4678c040a9828d52bcd83011360318c8de7f
Please let me know if this is sufficient solution for you

Hello @redjolr @ActionSeeker @amado10
SDK in version 2.1.7 was released and should be available in NPM registry shortly.
This release contains changes from:
https://github.com/voucherifyio/voucherify-js-sdk/pull/188
https://github.com/voucherifyio/voucherify-js-sdk/pull/190
Mainly:

proper typing of VoucherifyError
possibility to include root cause Axios error in VoucherifyError via property exposeErrorCause - you can read more here: https://github.com/voucherifyio/voucherify-js-sdk#-error-handling

Thank you for your patience and your feedback


Issue #4244

Feature request: Docker image build (parameterized_docker_build.sh) lacks option for AVX2 optimization #4244

Can one of the admins verify this patch?

@hholst80 thank you for doing this. Please sign the CLA.
@tensorflow-jenkins test this please.

I signed it!


Request render mode doesn't always work with 3D Tiles or Models

If I fly from home view to a tileset in request render mode (and the tileset isn't cached), the flight happens but nothing ever gets rendered until I manually force one.
Does Cesium automatically trigger a render on flight complete?  Shouldn't it?
CC @ggetz

I can make this happen all of the time in ion because the preview window has nothing else going on (no world imagery or terrain) so a tileset is the only thing that needs to load and Cesium is missing an internal render request somewhere.

As a workaround, I ended up adding a setTimeout in the flyTo complete callback I was using, (just a straight up requestRender didn't work, it had to be on several hundred ms delay)

@mramato It doesn't trigger one by default. It could.
I believe nothing is rendered because the tileset is not selected by rendering, therefore nothing begins loading. So there may a more direct way to make sure the tileset begins loading in request render mode than the flyTo completing. I'll take a look soon.

Do we already trigger a render every time a ajax request completes?  If not, could this be something where it's fetching content but doesn't render the content once it's fetched?
Otherwise, I'll leave it to your expertise.  Thanks.

We should really try to fix this for the next release. requestRender bugs on our end will make it hard for end users to use the feature and inserting random render calls in user code to work around it kind of negates the point.

I ran into another issue where the tileset doesn't clear from the globe on scene.primitives.remove.  calling scene.requestRender after remove didn't work either, I had to call scene.forceRender.

I'm running into similar problems with 3D model loading.

Here's a trivial way to reproduce this with Sandcastle direct link:
var viewer = new Cesium.Viewer('cesiumContainer', {
    requestRenderMode: true
});

var model = Cesium.Model.fromGltf({
    url: '../../../../Apps/SampleData/models/CesiumMilkTruck/CesiumMilkTruck-kmc.glb',
    scene: viewer.scene,
    modelMatrix: Cesium.Transforms.eastNorthUpToFixedFrame(Cesium.Cartesian3.fromDegrees(1, 2, 10000))
});

setTimeout(function () {
    viewer.scene.primitives.add(model);
    viewer.scene.requestRender();

    model.readyPromise.then(function () {
        var r = model.boundingSphere.radius;

        var center = Cesium.Matrix4.multiplyByPoint(model.modelMatrix, model.boundingSphere.center, new Cesium.Cartesian3());
        var heading = Cesium.Math.toRadians(-130.0);
        var pitch = Cesium.Math.toRadians(-25.0);
        var range = r * 3.5;
        viewer.scene.camera.lookAt(center, new Cesium.HeadingPitchRange(heading, pitch, range));
    });
}, 1000);

It doesn't happen every time (because race condition), but most of the time the model.readyPromise will never resolve until the user interfaces with the window or resizes the screen (even though we call requestRender after adding the primitive)
@ggetz does this help narrow down the issue?

Apologies for bumping this (via my #7489). I wanted to check if there was a target release for resolving this, or if there was anything I could do to help with its resolution. Thanks!

@KermMartian we don't have a specific release target, but we're hoping to look into this soon.  There are a few other things in-progress we need to finish first though.
If you're interested in looking into a fix, we would be happy to review a pull request!  @ggetz should be able to give some suggestions for where to look for the problem

@likangning93 @lilleyse @ggetz this is the issue I was mentioning yesterday.

I'm enthused if this is going to be addressed soon. :) I'm not pleased with our current solution, which is to not use the request render mode.

A lot has changed since this issue was written.  Can someone verify that there are still actual problems here?
@KermMartian one workaround I've used successfully is to just request a render at least once a second with the below code:
function requestRenderBug() {
    if (!viewer.isDestroyed()) {
        viewer.scene.requestRender();
        setTimeout(requestRenderBug, 1000);
    }
}
setTimeout(requestRenderBug, 1000);

Gets you most of the benefit while avoiding the bug.

I just ran into this using the latest Cesium, so definitely still a problem.

The problem is that Model requires at least one update before it becomes ready (and possibly more if asynchronous is true since the JobScheduler may take a few frames before it becomes ready) but update is never called until a user action occurs that triggers requestRender.
One approach is for scene to keep a list of primitives that still need updating request render until the list is empty. Another is for scene to listen to model load events like it does for RequestScheduler, TaskProcessor, and Globe. Neither approach is super well defined at the moment.

A lot has changed since this issue was written. Can someone verify that there are still actual problems here?

I can still reproduce the bug with model.readyPromise not resolving until a render is forced by something like resizing the browser window - updated Sandcastle. This is happening in sandcastle.cesium.com on CesiumJS 1.88.
But, I cannot reproduce this issue locally, even on older versions of CesiumJS, both built and unbuilt. Even if I host a .glb to load on a local server as opposed to linking to it with a relative filepath, I still cannot reproduce locally. Has this ever been an issue in local development?

I just ran into this issue (or something very similar) while developing locally. I was able use what @mramato did above and resolve the issue. I noticed that the issue was only happening on Chrome (Brave and Chromium), but Firefox updates immediately without issue. I am able to reproduce this behavior with the sandcastle.

Open @ebogo1's updated Sandcastle
Allow the page to load
Click Run in the top-left
The viewer should reload

On Chrome the zoomed out earth view should be shown:

If the user changes the size of the window or otherwise interacts with the viewer, the milk truck is shown.
On Firefox, the milk truck is shown immediately.
Versions

Brave Browser <IP_ADDRESS>
Chromium 97.0.4692.99 Arch Linux
Mozilla Firefox 96.0.2
Linux 5.16.2-arch1-1 x86_64 GNU/Linux

https://github.com/CesiumGS/cesium/issues/6898#issuecomment-991353207 describes why it's happening. We haven't done anything to fix it yet.

@ptrgags @lilleyse Did the glTF/3D Tiles next refactor happen to address this issue?

No, it was not addressed as part of the refactor.
I don't think it's too hard to implement though:

Call scene.requestRender() when a tile is moved to the processing queue to ensure at least one update is called
Call scene.requestRender() in processTiles if length is greater than 0

Additionally so that individual models work:

Call scene.requestRender() in processLoader

One problem is that scene is not really accessible to either of these. So some sort of requestRender function might need to be added to FrameState.

Additionally so that individual models work:

Call scene.requestRender() in processLoader

One problem is that scene is not really accessible to either of these. So some sort of requestRender function might need to be added to FrameState.

Request render mode has been causing me issues with models not loading until the user performs an action that forces a render. Like mentioned earlier in this thread, it can take multiple render calls before a model is ready and shows. In the processLoader method, I added the lambda frameState.afterRender.push(() => true); and it appears to make models load correctly. Of course, its rendering at its full rate until the model is ready but after they show, the rendering stops as desired.

After https://github.com/CesiumGS/cesium/pull/11059 and adding requestRender to the loaders, I can no longer replicate. I did update the sandcastle example to use the newer APIs.
Closing this as fixed.

@ggetz I'm confused by the new example. The doc for request render mode includes the following:

If true, rendering a frame will only occur when needed as determined by changes within the scene.

I could be wrong, but historically adding a primitive to the scene was considered an internally detected "Change within the scene", but in your example it seems you have to call requestRender after adding the primitive. Did something change? At the very least, the documentation probably need to be a little clearer hear around when a render needs to be specifically requested.


Cloudflare Pages - Auth endpoints

I tried the registering using the cloudflare deployment you provided and I get a 400 error. I'm having the same error when deploying myself and was wondering if this issue is related to differences in deploying through Wrangler CLI versus automatic Git integration.

I've deployed both "manually" and after connecting my github account to Pages. Interestingly the issue is more apparent when using automatic deployments. The function fails to upload with a seemingly obscure error and with manual it doesn't seem to capture the functions either although "_routes.json" exists.

My one question would be, what is the correct Base url to set for env, as I haven't seen this documented for Nuxt auth. should it include "https://" and does a leading slash at the end matter. Just trying to debug this to from what I've known
Environment includes:

<EMAIL_ADDRESS>Node 18 LTS
Workers runtime version - --compatibility-date=2023-08-31
For Pages automatic integration - Build system 2
Nuxt Starter with no extra dependencies - as is

Hi,
I agree that debugging for edge runtimes is tricky. The way I do this is by running the build command locally. Then I would run the application. If an error is thrown (in your case), I would search for its location on the server bundle (in your case it's 9295:39).
The baseURL should be a valid url, for example http://localhost:3000. With or without the trailing slash it doesn't matter.
Make sure that you have set nitro.preset in nuxt config to cloudlflare-pages.

I appreciate the quick response, can you verify that it doesn't work for any of the preview links you posted?
I have the same 400(Bad request) error and I've done everything to test it locally with no avail.
Vercel edge https://nuxt-auth-demo.vercel.app/
Netlify edge https://nuxt-auth-demo.netlify.app/
Cloudflare pages https://nuxt-auth-c35.pages.dev/
It seems to be a malformed request/reponse object. I haven't tested out the Google Oauth option and just want email auth

The demo works ok. Can you check the message error returned? Also, do you know any other email providers that support HTTP api?

Sure I found postmark to be quite pleasant but I haven't tested it yet. https://postmarkapp.com/developer/api/email-api

Sure I found postmark to be quite pleasant but I haven't tested it yet. https://postmarkapp.com/developer/api/email-api. This plus cloudflare email routing should be a good combination for DNS/domain management. Btw in my original post, the first image is of the demo but the error is very ambiguous and is a 400 error(unsure how to get more in depth on the details)

Update on the email providers. I would like to propose that you add resend API. I've tested postmark and the drawbacks became more apparent along with the pricing. I think adding resend as the default email provider would make a lot of sense with ease of setup. I'd like to hear what you think of their pricing as well. It would help more people find this repo or at least consider it since a problem I had was not wanting to go through sendgrid and it completely went over my head when first setting up the environment variables. Its all good I can use the custom provider as well. https://resend.com/docs/api-reference/introduction

I prefer not to set a default provider because this would be subjective. Any provider that supports REST API can be supported by the module regardless of their pricing model. I agree that Postmark's free tier is very limited compared to others such as Sendgrid, Resend, Mailgun.. If no one requested it, it simply won't be added. Since you find Resend convenient and me too, I will add it on the next release.


Support for Workload Identity Federation

This is a blocking issue in adoption of this since we are supposed to be only using WIF for all our service connections.
Not supporting WIF on means this is seen as a security issue.

This is a blocking issue in adoption of this since we are supposed to be only using WIF for all our service connections.
Not supporting WIF on means this is seen as a security issue.

+1 on this, is there a timeline for this ask?

Requesting all to contact Matt Basile.

Could this request please be prioritized?
We are making more use of Synapse and if this functionality could be implemented, it would help us immensely.
Is there a timeline/roadmap available for this to be addressed?

Any update on this request?

Hi team, we also need this- we have switched to WIF Service Connections because of Microsoft's recommendation. Any news on when WIF will be supported for Synapse?

Hi, this is also affecting our team after migration to WIF Service Connections.

It's a major show stopper for adoption of this in our org as well. Any timeline?


Adjust version numbers

Summary
trivial adjustment without Issue.
I removed "Alpha build" from 9.5.0, added 9.5.1
I left 9.4.4 for the moment. We won't benefit from reports stating wrong number.

Can we get a second review/merge on this please @dnnsoftware/approvers

Actually this is a release management task and it does not affect code, I gonna go ahead and merge it as per our release management review rules.