Installation issues in installing finrl on Ubuntu 22.04 on aarch64

Describe the bug
Error during installation.
Already looked at this issue.
To Reproduce
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy
Linux ubuntuonmac 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:29:11 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

Create new environment using: conda create --name env_frl_py3_10 python==3.10
Activete it:conda activate env_frl_py3_10
Install foundation: pip install git+https://github.com/AI4Finance-Foundation/FinRL.git

Error
...dropped, too long...
Cython.Compiler.Errors.CompileError: sklearn/svm/_liblinear.pyx
  Error compiling Cython file:
  ------------------------------------------------------------
  ...
      if error_msg:
          # for SVR: epsilon is called p in libsvm
          error_repl = error_msg.decode('utf-8').replace("p < 0", "epsilon < 0")
          raise ValueError(error_repl)
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm.pyx:194:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
                         class_weight_label.data, class_weight.data)
      model = set_model(&param, <int> nSV.shape[0], SV.data, SV.shape,
                        support.data, support.shape, sv_coef.strides,
                        sv_coef.data, intercept.data, nSV.data, probA.data, probB.data)
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm.pyx:358:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
                        sv_coef.data, intercept.data, nSV.data,
                        probA.data, probB.data)

      cdef np.npy_intp n_class = get_nr(model)
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm.pyx:464:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
          n_class = 1
      else:
          n_class = get_nr(model)
          n_class = n_class * (n_class - 1) // 2
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm.pyx:570:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
      if error_msg:
          raise ValueError(error_msg)

      cdef np.ndarray[np.float64_t, ndim=1, mode='c'] target
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm.pyx:714:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.
  Traceback (most recent call last):
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
      return cythonize_one(*m)
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
      raise CompileError(None, pyx_file)
  Cython.Compiler.Errors.CompileError: sklearn/svm/_libsvm.pyx

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
      if error_msg:
          free_problem(problem)
          free_param(param)
          raise ValueError(error_msg)
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm_sparse.pyx:153:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
                            sv_coef.data, intercept.data,
                            nSV.data, probA.data, probB.data)
      #TODO: use check_model
      dec_values = np.empty(T_indptr.shape[0]-1)
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm_sparse.pyx:284:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
      #TODO: use check_model
      cdef np.npy_intp n_class = get_nr(model)
      cdef int rv
      dec_values = np.empty((T_indptr.shape[0]-1, n_class), dtype=np.float64)
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm_sparse.pyx:343:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
          n_class = get_nr(model)
          n_class = n_class * (n_class - 1) // 2

      dec_values = np.empty((T_indptr.shape[0] - 1, n_class), dtype=np.float64)
      cdef BlasFunctions blas_functions
      blas_functions.dot = _dot[double]
                               ^
  ------------------------------------------------------------

  sklearn/svm/_libsvm_sparse.pyx:412:29: Cannot assign type 'double (int, double *, int, double *, int) except * nogil' to 'dot_func'. Exception values are incompatible. Suggest adding 'noexcept' to type 'double (int, double *, int, double *, int) except * nogil'.
  Traceback (most recent call last):
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
      return cythonize_one(*m)
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
      raise CompileError(None, pyx_file)
  Cython.Compiler.Errors.CompileError: sklearn/svm/_libsvm_sparse.pyx
  warning: sklearn/tree/_criterion.pxd:57:45: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:58:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:59:48: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:60:57: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pxd:61:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pxd:62:59: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pxd:63:63: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_splitter.pxd:84:72: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_splitter.pxd:89:68: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:61:45: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:86:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:93:48: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:100:57: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:282:76: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:348:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:375:48: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:402:57: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:744:45: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:788:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:799:48: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:810:57: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:1032:45: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:1082:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pyx:1113:48: The keyword 'nogil' should appear at the end of the function signature line.
  Traceback (most recent call last):
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
      return cythonize_one(*m)
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
      raise CompileError(None, pyx_file)
  Cython.Compiler.Errors.CompileError: sklearn/tree/_splitter.pyx
  warning: sklearn/tree/_tree.pxd:61:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pxd:62:59: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pxd:63:63: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_splitter.pxd:84:72: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_splitter.pxd:89:68: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:57:45: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:58:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:59:48: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:60:57: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pyx:269:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pyx:416:76: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pyx:673:59: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pyx:685:70: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pyx:719:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:49:75: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:87:61: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:119:56: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:137:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:139:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:160:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:161:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:76:59: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:95:51: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:98:59: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:99:63: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:100:80: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...

          # Initial capacity
          cdef int init_capacity

          if tree.max_depth <= 10:
              init_capacity = (2 ** (tree.max_depth + 1)) - 1
                                                          ^
  ------------------------------------------------------------

  sklearn/tree/_tree.pyx:148:56: Cannot assign type 'double' to 'int'
  Traceback (most recent call last):
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
      return cythonize_one(*m)
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
      raise CompileError(None, pyx_file)
  Cython.Compiler.Errors.CompileError: sklearn/tree/_tree.pyx
  warning: sklearn/tree/_utils.pxd:49:75: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:87:61: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:119:56: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:137:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:139:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:160:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pxd:161:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pxd:61:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pxd:62:59: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_tree.pxd:63:63: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_splitter.pxd:84:72: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_splitter.pxd:89:68: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:57:45: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:58:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:59:48: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_criterion.pxd:60:57: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:76:59: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:95:51: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:98:59: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:99:63: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/neighbors/_quad_tree.pxd:100:80: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pyx:29:75: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pyx:114:61: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pyx:230:56: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pyx:318:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pyx:335:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pyx:493:40: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  warning: sklearn/tree/_utils.pyx:507:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
  performance hint: sklearn/tree/_utils.pyx:29:5: Exception check on 'safe_realloc' will always require the GIL to be acquired. Declare 'safe_realloc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:127:24: Exception check after calling '__pyx_fuse_9safe_realloc' will always require the GIL to be acquired. Declare '__pyx_fuse_9safe_realloc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:205:27: Exception check after calling 'heapify_up' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare 'heapify_up' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on 'heapify_up' to allow an error code to be returned.
  performance hint: sklearn/tree/_utils.pyx:225:29: Exception check after calling 'heapify_down' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare 'heapify_down' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on 'heapify_down' to allow an error code to be returned.
  performance hint: sklearn/tree/_utils.pyx:243:24: Exception check after calling '__pyx_fuse_10safe_realloc' will always require the GIL to be acquired. Declare '__pyx_fuse_10safe_realloc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:259:23: Exception check after calling 'heapify_up' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare 'heapify_up' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on 'heapify_up' to allow an error code to be returned.
  performance hint: sklearn/tree/_utils.pyx:281:29: Exception check after calling 'heapify_down' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare 'heapify_down' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on 'heapify_down' to allow an error code to be returned.
  performance hint: sklearn/tree/_utils.pyx:326:20: Exception check after calling '__pyx_fuse_3safe_realloc' will always require the GIL to be acquired. Declare '__pyx_fuse_3safe_realloc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:349:24: Exception check after calling '__pyx_fuse_3safe_realloc' will always require the GIL to be acquired. Declare '__pyx_fuse_3safe_realloc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:491:32: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:516:20: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:517:45: Exception check after calling 'get_median' will always require the GIL to be acquired. Declare 'get_median' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:520:47: Exception check after calling 'update_median_parameters_post_push' will always require the GIL to be acquired. Declare 'update_median_parameters_post_push' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:531:20: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:551:69: Exception check after calling 'get_weight_from_index' will always require the GIL to be acquired. Declare 'get_weight_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:554:68: Exception check after calling 'get_weight_from_index' will always require the GIL to be acquired. Declare 'get_weight_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:560:44: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:563:68: Exception check after calling 'get_weight_from_index' will always require the GIL to be acquired. Declare 'get_weight_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:573:20: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:574:45: Exception check after calling 'get_median' will always require the GIL to be acquired. Declare 'get_median' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:576:42: Exception check after calling 'remove' will always require the GIL to be acquired. Declare 'remove' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:577:49: Exception check after calling 'update_median_parameters_post_remove' will always require the GIL to be acquired. Declare 'update_median_parameters_post_remove' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:588:20: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:589:45: Exception check after calling 'get_median' will always require the GIL to be acquired. Declare 'get_median' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:592:28: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:595:39: Exception check after calling 'pop' will always require the GIL to be acquired. Declare 'pop' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:596:49: Exception check after calling 'update_median_parameters_post_remove' will always require the GIL to be acquired. Declare 'update_median_parameters_post_remove' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:607:28: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:614:28: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:635:44: Exception check after calling 'size' will always require the GIL to be acquired. Declare 'size' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:638:68: Exception check after calling 'get_weight_from_index' will always require the GIL to be acquired. Declare 'get_weight_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:645:69: Exception check after calling 'get_weight_from_index' will always require the GIL to be acquired. Declare 'get_weight_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:648:68: Exception check after calling 'get_weight_from_index' will always require the GIL to be acquired. Declare 'get_weight_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:656:53: Exception check after calling 'get_value_from_index' will always require the GIL to be acquired. Declare 'get_value_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:657:53: Exception check after calling 'get_value_from_index' will always require the GIL to be acquired. Declare 'get_value_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/tree/_utils.pyx:660:52: Exception check after calling 'get_value_from_index' will always require the GIL to be acquired. Declare 'get_value_from_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/utils/_cython_blas.pyx:20:5: Exception check on '_dot' will always require the GIL to be acquired. Declare '_dot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/utils/_cython_blas.pyx:33:5: Exception check on '_asum' will always require the GIL to be acquired. Declare '_asum' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/utils/_cython_blas.pyx:45:5: Exception check on '_axpy' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_axpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_axpy' to allow an error code to be returned.
  performance hint: sklearn/utils/_cython_blas.pyx:58:5: Exception check on '_nrm2' will always require the GIL to be acquired. Declare '_nrm2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/utils/_cython_blas.pyx:70:5: Exception check on '_copy' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_copy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_copy' to allow an error code to be returned.
  performance hint: sklearn/utils/_cython_blas.pyx:82:5: Exception check on '_scal' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_scal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_scal' to allow an error code to be returned.
  performance hint: sklearn/utils/_cython_blas.pyx:94:5: Exception check on '_rotg' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_rotg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_rotg' to allow an error code to be returned.
  performance hint: sklearn/utils/_cython_blas.pyx:107:5: Exception check on '_rot' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_rot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_rot' to allow an error code to be returned.
  performance hint: sklearn/utils/_cython_blas.pyx:124:5: Exception check on '_gemv' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_gemv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_gemv' to allow an error code to be returned.
  performance hint: sklearn/utils/_cython_blas.pyx:153:5: Exception check on '_ger' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_ger' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_ger' to allow an error code to be returned.
  performance hint: sklearn/utils/_cython_blas.pyx:183:5: Exception check on '_gemm' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_gemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_gemm' to allow an error code to be returned.

  Error compiling Cython file:
  ------------------------------------------------------------
  ...
          dec(end)
          # Construct our arguments
          cdef pair[ITYPE_t, DTYPE_t] args
          args.first = key
          args.second = value
          self.my_map.insert(end, args)
                             ^
  ------------------------------------------------------------

  sklearn/utils/_fast_dict.pyx:138:27: Cannot assign type 'iterator' to 'const_iterator'
  Traceback (most recent call last):
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
      return cythonize_one(*m)
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
      raise CompileError(None, pyx_file)
  Cython.Compiler.Errors.CompileError: sklearn/utils/_fast_dict.pyx
  warning: sklearn/utils/_openmp_helpers.pyx:1:0: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
  warning: sklearn/utils/_openmp_helpers.pyx:44:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
  performance hint: sklearn/utils/_seq_dataset.pyx:80:53: Exception check after calling '_get_next_index' will always require the GIL to be acquired. Declare '_get_next_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/utils/_seq_dataset.pyx:81:20: Exception check after calling '_sample' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_sample' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_sample' to allow an error code to be returned.
  performance hint: sklearn/utils/_seq_dataset.pyx:117:55: Exception check after calling '_get_random_index' will always require the GIL to be acquired. Declare '_get_random_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/utils/_seq_dataset.pyx:118:20: Exception check after calling '_sample' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_sample' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_sample' to allow an error code to be returned.
  performance hint: sklearn/utils/_seq_dataset.pyx:405:53: Exception check after calling '_get_next_index' will always require the GIL to be acquired. Declare '_get_next_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/utils/_seq_dataset.pyx:406:20: Exception check after calling '_sample' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_sample' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_sample' to allow an error code to be returned.
  performance hint: sklearn/utils/_seq_dataset.pyx:442:55: Exception check after calling '_get_random_index' will always require the GIL to be acquired. Declare '_get_random_index' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
  performance hint: sklearn/utils/_seq_dataset.pyx:443:20: Exception check after calling '_sample' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '_sample' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '_sample' to allow an error code to be returned.
  performance hint: sklearn/utils/_weight_vector.pyx:183:29: Exception check after calling 'reset_wscale' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare 'reset_wscale' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on 'reset_wscale' to allow an error code to be returned.
  performance hint: sklearn/utils/_weight_vector.pyx:188:17: Exception check after calling '__pyx_fuse_1_axpy' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '__pyx_fuse_1_axpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '__pyx_fuse_1_axpy' to allow an error code to be returned.
  performance hint: sklearn/utils/_weight_vector.pyx:190:17: Exception check after calling '__pyx_fuse_1_scal' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '__pyx_fuse_1_scal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '__pyx_fuse_1_scal' to allow an error code to be returned.
  performance hint: sklearn/utils/_weight_vector.pyx:194:13: Exception check after calling '__pyx_fuse_1_scal' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '__pyx_fuse_1_scal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '__pyx_fuse_1_scal' to allow an error code to be returned.
  performance hint: sklearn/utils/_weight_vector.pyx:356:29: Exception check after calling 'reset_wscale' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare 'reset_wscale' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on 'reset_wscale' to allow an error code to be returned.
  performance hint: sklearn/utils/_weight_vector.pyx:361:17: Exception check after calling '__pyx_fuse_0_axpy' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '__pyx_fuse_0_axpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '__pyx_fuse_0_axpy' to allow an error code to be returned.
  performance hint: sklearn/utils/_weight_vector.pyx:363:17: Exception check after calling '__pyx_fuse_0_scal' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '__pyx_fuse_0_scal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '__pyx_fuse_0_scal' to allow an error code to be returned.
  performance hint: sklearn/utils/_weight_vector.pyx:367:13: Exception check after calling '__pyx_fuse_0_scal' will always require the GIL to be acquired.
  Possible solutions:
      1. Declare '__pyx_fuse_0_scal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
      2. Use an 'int' return type on '__pyx_fuse_0_scal' to allow an error code to be returned.
  multiprocessing.pool.RemoteTraceback:
  """
  Traceback (most recent call last):
    File "/home/fabio/miniconda3/envs/env_frl_py3_10/lib/python3.10/multiprocessing/pool.py", line 125, in worker
      result = (True, func(*args, **kwds))
    File "/home/fabio/miniconda3/envs/env_frl_py3_10/lib/python3.10/multiprocessing/pool.py", line 48, in mapstar
      return list(map(*args))
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1345, in cythonize_one_helper
      return cythonize_one(*m)
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1321, in cythonize_one
      raise CompileError(None, pyx_file)
  Cython.Compiler.Errors.CompileError: sklearn/ensemble/_hist_gradient_boosting/splitting.pyx
  """

  The above exception was the direct cause of the following exception:

  Traceback (most recent call last):
    File "/home/fabio/.local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
  [ 1/55] Cythonizing sklearn/__check_build/_check_build.pyx
  [ 2/55] Cythonizing sklearn/_isotonic.pyx
  [ 3/55] Cythonizing sklearn/cluster/_dbscan_inner.pyx
  [ 4/55] Cythonizing sklearn/cluster/_hierarchical_fast.pyx
  [ 5/55] Cythonizing sklearn/cluster/_k_means_common.pyx
  [ 6/55] Cythonizing sklearn/cluster/_k_means_elkan.pyx
  [ 7/55] Cythonizing sklearn/cluster/_k_means_lloyd.pyx
  [ 8/55] Cythonizing sklearn/cluster/_k_means_minibatch.pyx
  [ 9/55] Cythonizing sklearn/datasets/_svmlight_format_fast.pyx
  [10/55] Cythonizing sklearn/decomposition/_cdnmf_fast.pyx
  [11/55] Cythonizing sklearn/decomposition/_online_lda_fast.pyx
  [12/55] Cythonizing sklearn/ensemble/_gradient_boosting.pyx
  [13/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/_binning.pyx
  [14/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/_bitset.pyx
  [15/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/_gradient_boosting.pyx
  [16/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/_loss.pyx
  [17/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/_predictor.pyx
  [18/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/common.pyx
  [19/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/histogram.pyx
  [20/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/splitting.pyx
  [21/55] Cythonizing sklearn/ensemble/_hist_gradient_boosting/utils.pyx
  [22/55] Cythonizing sklearn/feature_extraction/_hashing_fast.pyx
  [23/55] Cythonizing sklearn/linear_model/_cd_fast.pyx
  [24/55] Cythonizing sklearn/linear_model/_sag_fast.pyx
  [25/55] Cythonizing sklearn/linear_model/_sgd_fast.pyx
  [26/55] Cythonizing sklearn/manifold/_barnes_hut_tsne.pyx
  [27/55] Cythonizing sklearn/manifold/_utils.pyx
  [28/55] Cythonizing sklearn/metrics/_pairwise_fast.pyx
  [29/55] Cythonizing sklearn/metrics/cluster/_expected_mutual_info_fast.pyx
  [30/55] Cythonizing sklearn/neighbors/_ball_tree.pyx
  [31/55] Cythonizing sklearn/neighbors/_dist_metrics.pyx
  [32/55] Cythonizing sklearn/neighbors/_kd_tree.pyx
  [33/55] Cythonizing sklearn/neighbors/_partition_nodes.pyx
  [34/55] Cythonizing sklearn/neighbors/_quad_tree.pyx
  [35/55] Cythonizing sklearn/neighbors/_typedefs.pyx
  [36/55] Cythonizing sklearn/preprocessing/_csr_polynomial_expansion.pyx
  [37/55] Cythonizing sklearn/svm/_liblinear.pyx
  [38/55] Cythonizing sklearn/svm/_libsvm.pyx
  [39/55] Cythonizing sklearn/svm/_libsvm_sparse.pyx
  [40/55] Cythonizing sklearn/svm/_newrand.pyx
  [41/55] Cythonizing sklearn/tree/_criterion.pyx
  [42/55] Cythonizing sklearn/tree/_splitter.pyx
  [43/55] Cythonizing sklearn/tree/_tree.pyx
  [44/55] Cythonizing sklearn/tree/_utils.pyx
  [45/55] Cythonizing sklearn/utils/_cython_blas.pyx
  [46/55] Cythonizing sklearn/utils/_fast_dict.pyx
  [47/55] Cythonizing sklearn/utils/_logistic_sigmoid.pyx
  [48/55] Cythonizing sklearn/utils/_openmp_helpers.pyx
  [49/55] Cythonizing sklearn/utils/_random.pyx
  [50/55] Cythonizing sklearn/utils/_readonly_array_wrapper.pyx
  [51/55] Cythonizing sklearn/utils/_seq_dataset.pyx
  [52/55] Cythonizing sklearn/utils/_weight_vector.pyx
  [53/55] Cythonizing sklearn/utils/arrayfuncs.pyx
  [54/55] Cythonizing sklearn/utils/murmurhash.pyx
  [55/55] Cythonizing sklearn/utils/sparsefuncs_fast.pyx
      main()
    File "/home/fabio/.local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File "/home/fabio/.local/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 149, in prepare_metadata_for_build_wheel
      return hook(metadata_directory, config_settings)
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 366, in prepare_metadata_for_build_wheel
      self.run_setup()
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 480, in run_setup
      super(_BuildMetaLegacyBackend, self).run_setup(setup_script=setup_script)
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 311, in run_setup
      exec(code, locals())
    File "<string>", line 319, in <module>
    File "<string>", line 315, in setup_package
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/numpy/distutils/core.py", line 135, in setup
      config = configuration()
    File "<string>", line 201, in configuration
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/numpy/distutils/misc_util.py", line 1014, in add_subpackage
      config_list = self.get_subpackage(subpackage_name, subpackage_path,
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/numpy/distutils/misc_util.py", line 980, in get_subpackage
      config = self._get_configuration_from_setup_py(
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/numpy/distutils/misc_util.py", line 922, in _get_configuration_from_setup_py
      config = setup_module.configuration(*args)
    File "/tmp/pip-install-dh3tipcc/scikit-learn_564de7b1c977471ba69b9d643f5f0009/sklearn/setup.py", line 85, in configuration
      cythonize_extensions(top_path, config)
    File "/tmp/pip-install-dh3tipcc/scikit-learn_564de7b1c977471ba69b9d643f5f0009/sklearn/_build_utils/__init__.py", line 73, in cythonize_extensions
      config.ext_modules = cythonize(
    File "/tmp/pip-build-env-eoo56xj6/overlay/lib/python3.10/site-packages/Cython/Build/Dependencies.py", line 1145, in cythonize
      result.get(99999)  # seconds
    File "/home/fabio/miniconda3/envs/env_frl_py3_10/lib/python3.10/multiprocessing/pool.py", line 771, in get
      raise self._value
  Cython.Compiler.Errors.CompileError: sklearn/ensemble/_hist_gradient_boosting/splitting.pyx
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
\u00d7 Encountered error while generating package metadata.
\u2570\u2500> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

I try to go on with:
pip install Cython==0.29.36
pip install scikit-learn==1.0 --no-build-isolationc

But now I got issue with cvxpy:
...
Collecting cvxpy<1.1,>=1.0
Using cached cvxpy-1.0.31.tar.gz (947 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... error
error: subprocess-exited-with-error
\u00d7 Preparing metadata (pyproject.toml) did not run successfully.
\u2502 exit code: 1
\u2570\u2500> [1 lines of output]
error in cvxpy setup command: use_2to3 is invalid.

I'm not sure about the error but
it might be fixed with
apt-get install g++
actually I have received some errors (did not recall ) but I have fixed those error to install g++ .
It install C++ in ubuntu.


[BUG]: ModuleNotFoundError when using  tensorflow 2.17.0.

Before You Report a Bug, Please Confirm You Have Done The Following...

[X] I have updated to the latest version of the packages.
[X] I have searched for both existing issues and closed issues and found none that matched my issue.

RetinaFace's Version
0.0.17
Python Version
3.10.14
Operating System
Ubuntu 24.04 LTS
Dependencies
tensorboard==2.17.0
tensorboard-data-server==0.7.2
tensorflow==2.17.0
tensorflow-io-gcs-filesystem==0.37.1
retina-face==0.0.17
Reproducible example
hasFrame, frame = cap.read()
resp = RetinaFace.detect_faces(frame)
print(resp)

Relevant Log Output
Traceback (most recent call last):
  File "/home/myspace/anaconda3/envs/myenv/lib/python3.10/site-packages/retinaface/commons/package_utils.py", line 19, in validate_for_keras3
    import tf_keras
ModuleNotFoundError: No module named 'tf_keras'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "bla/bla/bla/scripts/MMST_Face_Detection_Module.py", line 39, in <module>
    from retinaface import RetinaFace
  File "/home/myspace/anaconda3/envs/myenv/lib/python3.10/site-packages/retinaface/RetinaFace.py", line 20, in <module>
    package_utils.validate_for_keras3()
  File "/home/myspace/anaconda3/envs/myenv/lib/python3.10/site-packages/retinaface/commons/package_utils.py", line 24, in validate_for_keras3
    raise ValueError(
ValueError: You have tensorflow 2.17.0 and this requires tf-keras package. Please run `pip install tf-keras` or downgrade your tensorflow.

Expected Result
No response
What happened instead?
After installing tf-keras (2.17.0), it seems to work:

WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
I0000 00:00:1723724774.766310  421430 cuda_executor.cc:1015] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero. See more at https://github.com/torvalds/linux/blob/v6.0/Documentation/ABI/testing/sysfs-bus-pci#L344-L355
24-08-15 15:26:16 - Directory /home/myspace/.deepface created
24-08-15 15:26:16 - Directory /home/myspace/.deepface/weights created
24-08-15 15:26:16 - retinaface.h5 will be downloaded from the url https://github.com/serengil/deepface_models/releases/download/v1.0/retinaface.h5
Downloading...
From: https://github.com/serengil/deepface_models/releases/download/v1.0/retinaface.h5
To: /home/myspace/.deepface/weights/retinaface.h5
100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 119M/119M [00:04<00:00, 29.6MB/s]
{'face_1': {'score': 0.9993606805801392, 'facial_area': [796, 138, 856, 223], 'landmarks': {'right_eye': [817.68085, 179.61206], 'left_eye': [845.1754, 174.52724], 'nose': [837.74194, 191.97112], 'mouth_right': [825.0055, 206.98227], 'mouth_left': [846.4441, 203.29948]}}}

Additional Info
No response

Exception message is clear You have tensorflow 2.17.0 and this requires tf-keras package. Please run pip install tf-keras or downgrade your tensorflow.
What makes you think this is a bug?

Hi,
Probably wrong label from my side. My apologies.
I just wanted to point that maybe would be nice to update the requirements or installation dependencies.
Best.

I cannot because if we add tf_keras dependency then users with tf < 2.17 will have trouble.


Multiple Switch and NIC has bootstrapping problem

Bad c_local value poisons the whole network..

Delay measurement does not work between two boards..

Problem can be solved, if new device joins the network is by default disabled.

closed.


Implement a RFC compliant URI parser

The http core types must define a RFC 3986 compliant URI parser.
Some good work has already been done by @Vexu on Zuri, and I feel like it would be great to embed it within the Zig HTTP core types library.
Pros:

Do not rewrite something from scratch

Cons:

I would love to build librairies only depending on the latest Zig version for the sake of not breaking things and moving at a controlled pace, but zuri depends preferably on Zig the master branch.

After the agreement of @Vexu, I decided to include zuri inside http.
As soon as the overall API is stable, we should ensure that the URI parser is RFC compliant and optimized :)
Cf: https://github.com/Vexu/zuri/issues/3


ERROR: Top blob 'data' produced by multiple sources

I have six channel image (2 RGB image concatenated). I want to train the model with these images using AlexNet. I packed the images into lmdb. Then I used the OTHER option for dataset and model, however I am getting the following error when I am creating the model .
ERROR: Top blob 'data' produced by multiple sources.
Creating layer train-data
Creating Layer train-data
Top blob 'data' produced by multiple sources.
Opened lmdb /home/super/datasets/7pixel/image-offer/multimodal-with-embedding/lmdb_database/train_labels

I am using standard AlexNet architecture.
My understanding of the error
I believe the AlexNet assume that the two are coming from both train and val. Can someone explain to me how to use multiple input.

Check out this popup for an explanation of how to filter layers: https://github.com/NVIDIA/DIGITS/pull/628#issuecomment-195137527
If you can't figure it out, paste the definition of the generated data layers for your train/val network and I'll point out the issue to you.

I read out these instructions and removed the TRAIN and VAL phase then DIGIT by default include all three phases i.e. TRAIN, VAL and DEPLOY. I am able to resolve the error however I didn't get the good results in terms of accuracy.
One interesting result that I obtained is that I have same accuracy value by using an AlexNet on multi input (2 images or 6 channel).  Other network consist of two identical AlexNets processing each image and then using a conc  layer.

I'm having the same problem with DIGITS 6 and it appears the layers are as per instructions. Here's the top portion of generated layers:
layer {
name: "train-data"
type: "Data"
top: "data"
top: "label"
include {
phase: TRAIN
}
transform_param {
mirror: true
crop_size: 227
}
data_param {
source: "/jobs/20170926-032526-f969/train_db/features"
batch_size: 5
backend: LMDB
}
}
layer {
name: "train-data"
type: "Data"
top: "data"
top: "label"
include {
phase: TRAIN
}
transform_param {
mirror: true
crop_size: 227
}
data_param {
source: "/jobs/20170926-032526-f969/train_db/labels"
batch_size: 5
backend: LMDB
}
}
layer {
name: "val-data"
type: "Data"
top: "data"
top: "label"
include {
phase: TEST
}
transform_param {
crop_size: 227
}
data_param {
source: "/jobs/20170926-032526-f969/val_db/features"
batch_size: 5
backend: LMDB
}
}
layer {
name: "val-data"
type: "Data"
top: "data"
top: "label"
include {
phase: TEST
}
transform_param {
crop_size: 227
}
data_param {
source: "/jobs/20170926-032526-f969/val_db/labels"
batch_size: 5
backend: LMDB
}
}

I want to detect road network from satellite images. i download dataset from Kaggle which was manchesett road dataset for road network detection.  I want to train the model with these images using AlexNet. My dataset successfully uploaded in DIGITS and it display datasets information as under:
Dataset
road_segmenataion1
Done 09:24:06 AM
DB backend: lmdb
Create train_db DB
Entry Count: 724
Feature shape (3, 1500, 1500)
Label shape (1, 1500, 1500)
Create val_db DB
Entry Count: 80
Feature shape (3, 1500, 1500)
Label shape (1, 1500, 1500)
But when i trained the  segmentation model in DIGITS then within 3 s it gives following error:
ERROR: Top blob 'data' produced by multiple sources.
Creating layer train-data
Creating Layer train-data
Top blob 'data' produced by multiple sources.
Opened lmdb /jobs/20201231-092027-c6cd/train_db/labels
As i am new user and little bit information about DIGIT. So please guide me where i am wrong.
Thanking you in advance


feat: Support AnonymousIdentity

and make it work (by not creating sender_sig and sender_pubkey fields)
This replaces the bogus DummyIdentity.
Also, remove the unused principal argument to sign (not sure what
the point was – doesn't the Identity know who it is?)
This fixes #58

Also, remove the unused principal argument to sign (not sure what the point was – doesn't the Identity know who it is?)

Not necessarily. Basically, the API needs to stay stateless, but I wanted to allow switching identity per request. Should you rebuild the agent every time for e.g. a round robin use case? Building an agent can be expensive (e.g. querying the replica for a root key), so I decided it was simpler to pass the principal returned by the identity. This is just a pattern where the identity object is in control, but the API is stateless (because an agent might be doing multiple requests in parallel and the order of calls isn't guaranteed).
If you have an idea on how to tackle this, let me know.

Also, remove the unused principal argument to sign (not sure what the point was – doesn't the Identity know who it is?)

Not necessarily. Basically, the API needs to stay stateless, but I wanted to allow switching identity per request. Should you rebuild the agent every time for e.g. a round robin use case? Building an agent can be expensive (e.g. querying the replica for a root key), so I decided it was simpler to pass the principal returned by the identity. This is just a pattern where the identity object is in control, but the API is stateless (because an agent might be doing multiple requests in parallel and the order of calls isn't guaranteed).
If you have an idea on how to tackle this, let me know.

Approving this. I just added some formatting.

Approving this. I just added some formatting.

Thanks!

Thanks!


TCPExpect test isn't isn't run on Windows

The TCPExpect test isn't currently run on Windows. But looking at the code, it looks like it should work. Is there a reason this is off? At the moment, this looks like a bit of oversight.
@Theodus ?

@SeanTAllen I don't see any reason why it shouldn't work, but I currently have no way of finding out. Maybe I'll figure out how to build pony on Windows today.


Compiler API Cleanup

Purpose
This PR will deprecate old BVM Compiler API.
Fixes #20038
Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #20039 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #20039   +/-   ##
=======================================
  Coverage    19.9%    19.9%
=======================================
  Files          55       55
  Lines        1437     1437
  Branches      218      218
=======================================
  Hits          286      286
  Misses       1138     1138
  Partials       13       13

Continue to review full report at Codecov.

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


No configuration file MC 1.12.2 Forge

Hello
I've installed DiscordIntegration-1.1.18 (MC 1.12) on a 1.12.2 MC Forge server.
I try to follow the wiki for the installation but the mod didn't create config file.
I've looked in /mods, /config but i can't find it, is there a command to do in game for create this config file ?

Same problem. There is the following message in the log
[14:21:57] [Server thread/INFO] [FML]: FML has found a non-mod file DiscordCraft-2.0.jar in your mods directory. It will now be injected into your classpath. This could severe stability issues, it should be removed if possible.

DiscordCraft is an different mod. Also it is client side...  That one have a link to this repo


[SPARK-9695] [ML] Add random seed Param to ML Pipeline

Add random seed Param to ML Pipeline

Merged build triggered.

Merged build started.

Test build #43894 has started for   PR 9158 at commit 2156015.

Test build #43894 has finished for   PR 9158 at commit 2156015.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class Pipeline(override val uid: String) extends Estimator[PipelineModel] with HasSeed

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43894/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #43923 has started for PR 9158 at commit 9822a26.

Test build #43923 has finished for PR 9158 at commit 9822a26.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class Pipeline(override val uid: String) extends Estimator[PipelineModel] with HasSeed \n

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43923/
Test PASSed.

Test build #47506 has started for   PR 9158 at commit 9822a26.

Test build #47506 has finished for   PR 9158 at commit 9822a26.

This patch fails PySpark unit tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
class Pipeline(override val uid: String) extends Estimator[PipelineModel] with HasSeed

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47506/
Test FAILed.

Build finished. Test FAILed.

Jenkins, test this please.

Test build #47582 has started for   PR 9158 at commit 9822a26.

Test build #47582 has finished for   PR 9158 at commit 9822a26.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
class Pipeline(override val uid: String) extends Estimator[PipelineModel] with HasSeed

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47582/
Test PASSed.

So this is a bit out of sync with master, how would feel about updating it? Maybe @jkbradley as the reporter of this JIRA could also take a look once that is done.

Test build #60879 has started for   PR 9158 at commit 9822a26.

Test build #60879 has finished for   PR 9158 at commit 9822a26.

This patch fails R style tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60879/
Test FAILed.

So also following up from @jkbradley's note on https://issues.apache.org/jira/browse/SPARK-7653 we don't currently expose HasSeed to the public so external models with seeds won't be able to implement it (using our public APIs). I think if we do go with this approach the most reasonable thing to do is to make HasSeed public but I'd love to hear others' thoughts on the matter.


Fix Vehicle attribute output in CLI

Fix a few formatting bugs in the CLI output where raw pointers are being used instead of their de-referenced values.

Thank you!


Losing authorization

I installed the integration and it works great. However after a few weeks it loses the authorization it seems. I guess the token expires after a while that makes sense. However I did not find a way to enter a new token. I did reinstall the integration but that is quite inconvenient. Is there a way to update the token from the HA interface?

When you pasted your token, did you paste a refresh token?

Same issue here. Won't refresh anymore, I assume I lost auth. No way to update token for some reason? Why can't we in the UI update the token.

Some thing happened to me, can’t remember which token I used but did a restart of HA this morning and the integration failed to load. Either we all used a refresh token which gets refreshed all at the same time or there was something happening on the Tesla side.

I regenerated a new refresh token and still can't get it to auth.

Please provide logs from tesla_custom and teslajsonpy. The component should create a prompt if it detects a relogin is necessary. Regardless you can remove and readd.

I never got that warning in my log. However HACS requested an update and after restarting the integration did prompt for a new refresh token, finally. This solved the errors.

Mine also required reauthentication today (the UI for reauthentication worked fine).
It seems like a coincidence that it happened to several people today?  Could there have been a hiccup in Tesla's servers that the integration interpreted as a permanently failed authentication or something?

Re-authentication through the UI fixed the integration for me

I added the following to my configuration.yaml:

logger:
  default: info
  logs:
    homeassistant.core: info
    homeassistant.components.command_line.switch: warning
    googleapiclient.discovery: warning
    custom_components.openei: warning
    custom_components.tesla_custom: debug
    custom_components.teslajsonpy: debug
    tesla_custom: debug
    teslajsonpy: debug

and I'm not seeing deeper logs.  When I attempt the config flow:
This error originated from a custom integration.
Logger: custom_components.tesla_custom.config_flow
Source: custom_components/tesla_custom/config_flow.py:172
Integration: tesla_custom (documentation, issues)
First occurred: 10:37:01 PM (1 occurrences)
Last logged: 10:37:01 PM

Authentication error: Need oauth credentials

Tesla reset the tokens for many users because someone manage to sniff tokens from 25 users.
https://twitter.com/david_colombo_/status/1481193771207380994

Hi everyone
Looks like I stirred up a hornets nest 😆
I did use the refresh token. Also I should mention I don't use HACS but used the manual install method by copying the files manual.

What do ya know, I just checked again just now and there is a reconfigure button that was not there yesterday. I swear. Put my new refresh token and boom problem solved.
No idea what happened. I think cannot be that the integration was update, could it?

Since it's working for you, I'm going to close this as resolved.


Default for import/extensions setting

Should include .js and maybe .mjs or whatever the proposed module extension is at that point, if it's looking solid.
May also want to create a no-ignored-extensions rule for debugging, or just add a debug print for each ignored file. (#300)

Should add a debug log of path ignored if extensions are not matched.


OpenID Support (progress tracking)

After discussion we decided to do it in the following way:

Redirect to a static page under this app for now, but the redirected page should be general, i.e. be able to handle all NDN namesaces instead of specific ones. The information of applied namespace should be passed via the state parameter.
The redirected page parses the search parameters and bounce all state back to the application. We plan to use Push API to do this notification.
Plan to use NDNts ndn-cert server if ndn-cxx is too hard to modify.

There will be another repo storing NDN cert related part.

dbd9098

We have setup the NDN-Cert server: https://github.com/tianyuan129/ndncert-oidc
The deployed app worked in our test. Consider this as done.


THRIFT-2156

code from pull request #1033 plus some refactoring added

@jeking + @tpcwang please feel free to comment

Looks good :+1:

Agree :+1:


Fix NullPointerException when calling image.write

JSONUtils already does it this way, so I modified the other classes to use the same pattern.
fixes #94

Looks good, thanks!


The example code to get this to bind to an input does not seem to work

I cannot get this working when passing in an 'el' property

You are correct. Although I included that in the docs it is currently not completed and will be in the next version (note the TODO alongside the header).
Sorry for not making that more explicit.


Compiler recursion limit under OS X compiling CoffeeScript

I recently found out from a tester that Duktape fails to evaluate coffee-script.js with the following error when my engine is run under OS X (Mavericks I believe):
RangeError: compiler recursion limit (line 8)

This is with version 1.9.3 of the CoffeeScript compiler, available here:
http://coffeescript.org/extras/coffee-script.js
I don't have access to a Mac to test this myself.  The same script compiles and runs fine on every Windows build I've done.

Deep C stack seems not to be enabled for OSX; could you try with -DDUK_OPT_DEEP_C_STACK?
If that fixes it, I'll change the default behavior for OSX to use a deep stack.

Still waiting on a response from my OS X tester, hang tight. :-)

DUK_OPT_DEEP_C_STACK indeed fixed the error.

Alright, I'll change OSX default to use deep stacks (like Windows and Linux). For now you can just keep that feature option in your build.

Out of curiosity, how much difference between the limits is there?  Are we talking an order of magnitude, or...?

More than an order of magnitude - the "shallow stack" mode is intended for targets which have really limited stacks (around 32-64kB). With #64 the default will be "deep stack" and you'll have to explicitly request a shallow stack because that's probably the better default.
I'm planning to remove the current C stack limits altogether (which are applied separately for compilation, regexps, etc), and instead allow the user to provide a stack check macro which can check for available stack space in a target specific manner. This check can then be added to a few critical places inside Duktape, so that the out-of-stack error happens only when needed and there'd be no need for guesstimating reasonable stack limits which is difficult to get right.

How would the user know how much stack space is left though?  Duktape itself is in a better position to make that determination, I would think, as it can count activations and you'd know best how many bytes are needed for each call, etc.
I'm assuming this stack-check macro, if it's implemented, will be part of the new duk_config system, yes?

The user would be able to write a function that could inspect a stack pointer and have the target specific information needed to figure out how much safe stack space still exists.
I don't see how Duktape could do that, considering that stack handling is entirely target specific.
Duktape currently tries to count recursion depth for the important places where arbitrary recusion may occur.
Yeah, this stack check macro would be part of duk_config.h with a no-op default.

Btw, note that even if stack frame size estimates in the recursion paths were close to correct, Duktape would have no idea what the safe stack size on a certain platform is. The current shallow/deep distinction is now roughly tuned for "unix-like" (deep) or ~64kB (shallow), but this is pretty coarse and perhaps even counterproductive.

That makes sense.  Keep in mind though that, as far as I am aware, many platforms may dynamically grow the stack.  So what is the ceiling one time may in fact be higher next time.
I guess it's not ever an exact science.  Even so, more granularity is always good thing.

Sure, if the stack is essentially "infinite", it would then be up to the user to decide what's the appropriate stack check limit (if any). Even if the platform grew the stack indefinitely, it may still be desirable to artificially limit stack to, say, 1 megabyte for containment reasons.

The OSX related change is now merged to master - reopen if it doesn't work for some reason (it was merged after #64 so there's a lot of trivia that may be broken).


Update register-devices.md

ttn-lw-cli complains with a warning message when the example device create command from this document is used:
Flag --app-eui has been deprecated, use the join-eui flag
This PR changes --app-eui to --join-eui.
(after writing the comments below) The documentation under https://www.thethingsindustries.com/docs/getting-started/cloud-hosted/tti-join-server/register-devices/ seems outdated and should rather looks like the commands under https://www.thethingsindustries.com/docs/devices/adding-devices/
Summary

...
Screenshots

...
Changes

...
...

Notes for Reviewers

...
Checklist

[x] Scope: The referenced issue is addressed, there are no unrelated changes.
[ ] Run Locally: Verified that the docs build using make server, posted screenshots, verified external links. Test with HUGO_PARAMS_SEARCH_ENABLED=true if style changes will affect the search bar.
[ ] New Features Marked: Documentation for new features is marked using the new-in-version shortcode, according to the guidelines in CONTRIBUTING.
[ ] Style Guidelines: Documentation obeys style guidelines in CONTRIBUTING.
[ ] Commits: Commit messages follow guidelines in CONTRIBUTING, there are no fixup commits left.

Using this specific command from the docs does not set the Network Layer parameters:

The assumption is that the default settings should be used. Is what I see correct, or do we need to add more flags to this device create command?

From https://clavisound.no-ip.info/minisites/ttn/docs/ttnv3.cli.php I see a better example command that does fill in the Network layer settings. I needed 3 more flags:
  --frequency-plan-id EU_863_870_TTN \
  --lorawan-version 1.0.2 \
  --lorawan-phy-version 1.0.2-b \

@adriansmares I think you'd be the most suitable person to take this

@jpmeijers @adriansmares what is the status of this PR? is this ready to merge?

I will leave the docs as is (since in 1.0.x terms, the JoinEUI is still called an AppEUI) and fix this on the stack side separately.


Syscall handler infra

Infrastructure for executing Cairo1 syscalls. Executes first GetExecutionInfo syscall, fails on next CallContract syscall:
...
about to call contract_address:<PHONE_NUMBER>, class_hash:<PHONE_NUMBER>, is_deprecated: 0
about to execute syscall: GetExecutionInfo
about to execute syscall: CallContract
...

A lot of code borrowed from Blockifier. @odesenfans there are a lot of TODOs in syscalls.cairo. This code is adapted from blockifier. I prefer to move it in one go, put not ready parts in comments with todos, then uncomment one by one in subsequent prs.

Is there no test for any of this code?

There is an integration test: https://github.com/keep-starknet-strange/snos/blob/29487c6a90cced41eef9b07ace49a4d1d9b74435/tests/os_on_blocks.rs#L38. It fails at some point after executing hints implemented here.


Duping

So you can pretty much dupe an item specifically the armor only
This is how it works:

Find a slot in one of their slots

Pick an item

An armor should pop up and then replace the item to get the armor

Throw it out of your inventory

and look at this lol

Thats pretty much it, pls fix this. Very good mod by the way! I like it.

i think the last image was duped leggings instead of boots so my bad on that one btw!

Come here to report the same thing and saw your report. Really hope this gets fixed soon.

Btw how did you get the villager to put the shield on their back? Is that another mod you're using?

im pretty sure i used a resource pack (Faithless) I dont think any mods would do it since all of the mods I used were either for fps boost, structure mods, and the villager one. If the villager didnt have the shield on their back then its def Faithless Resource pack.

Dont know whats causing it

jk i found the issue, fixed in 1.0.20


Migrate __RuntimeConfig_v1 to protobuf (nanopb)

Completed.  Closed in favor of moving additional work to #7.


Backup and Restore commands

Add backup and restore commands that export/import announcements/devices/applications

ttn discovery backup/restore file.json
ttn networkserver backup/restore file.json
ttn handler backup/restore devices/applications file.json

This is not going to get implemented in V2 anymore.


App get crashes when users launch the app after installing the app store build.

Frequency: 100%
** Repro App version:** App store build v1.8.0
Does not repro App version: Celo Alfa v1.8.0 (101848577)
Repro on device: Google pixel XL (8.1),
Does not repro Device: Moto G5s plus (8.1),
Repro Steps:

launch the play store
Install the latest celo alfajore build v1.8.0
launch the app after installing
Observe

Current Behavior: App get crash while launching the app
Expected Behavior: App should not crash while launching app
Attachment:

Android_Appcrash.mp4 (Bug observe at 08 Sec)

Hi @jmrossy i have verified this issue on updated play store build v1.8.1 and found that issue is not reproduced. Hence now closing ticket.
Verified Device on: Google pixel XL (8.1), Samsung Galaxy A70 (9.0), Samsung Note 9 (10)


Support setting default NPM repo when no npmrc is present

It appears that dependabot-core keeps the public NPM registry as the default in the case that there is no npmrc present in the repository in question, even when additional repos are specified via credentials.  This is causing dependabot-core to fail with a 404 when attempting to detect upgrades for internal libraries in our projects, which make the assumption that the default registry has been set to our internal one by the user/build environment.  I note that for python registries there is an option replaces-base to allow for setting the default registry, is there an equivalent for NPM registries? If not would you accept a PR for this functionality?

This sounds like something we should be able to fix without requiring configuration. Can you @-mention Dependabot in a PR or issue that it's creating? That will help me replicate and fix.

Unfortunately I can't link to a PR as this was using dependabot-core on our internal Github Enterprise installation, any other way I can help investigate?

Ah, OK.
My first hunch here is that adding a .npmrc file or .yarnrc file that declared a global registry (with or without credentials) would stop this behaviour, as it's likely coming from the RegistryFinder#global_registry method. Do you have one committed?

yes, adding such a .npmrc does indeed resolve the issue, the problem with this is I suspect we have a lot of repos that don't have this file.  We could of course do an exercise to add it to each of them, but I was wondering if it would be possible to set the default when invoking dependabot to avoid needing to do that.

Hmmm, Dependabot shouldn't be falling back to registry.npmjs.org anywhere else unless it can't find details of the dependency anywhere else. What line are you seeing the error from?

(I presume you're using the latest version of Dependabot Core, by the way?)

I've been using the dependabot-core docker image, pulled 7 days ago and invoked via dependabot-script with our NPM repo added to the credentials block. The error is:
  - Updating debug (from )…Traceback (most recent call last):
	23: from ./generic-update-script.rb:126:in `<main>'
	22: from ./generic-update-script.rb:126:in `each'
	21: from ./generic-update-script.rb:164:in `block in <main>'
	20: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:39:in `updated_dependency_files'
	19: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:148:in `updated_lockfiles'
	18: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:148:in `each'
	17: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:149:in `block in updated_lockfiles'
	16: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:120:in `package_lock_changed?'
	15: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:187:in `updated_package_lock_content'
	14: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:30:in `updated_lockfile_content'
	13: from /workspace/vendor/ruby/2.6.0/gems/dependabot-common-0.108.15/lib/dependabot/shared_helpers.rb:34:in `in_a_temporary_directory'
	12: from /usr/lib/ruby/2.6.0/tmpdir.rb:93:in `mktmpdir'
	11: from /workspace/vendor/ruby/2.6.0/gems/dependabot-common-0.108.15/lib/dependabot/shared_helpers.rb:37:in `block in in_a_temporary_directory'
	10: from /workspace/vendor/ruby/2.6.0/gems/dependabot-common-0.108.15/lib/dependabot/shared_helpers.rb:37:in `chdir'
	 9: from /workspace/vendor/ruby/2.6.0/gems/dependabot-common-0.108.15/lib/dependabot/shared_helpers.rb:37:in `block (2 levels) in in_a_temporary_directory'
	 8: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:34:in `block in updated_lockfile_content'
	 7: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:34:in `chdir'
	 6: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:35:in `block (2 levels) in updated_lockfile_content'
	 5: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:115:in `run_current_npm_update'
	 4: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:137:in `run_npm_updater'
	 3: from /workspace/vendor/ruby/2.6.0/gems/dependabot-common-0.108.15/lib/dependabot/shared_helpers.rb:141:in `with_git_configured'
	 2: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:139:in `block in run_npm_updater'
	 1: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:151:in `run_npm_top_level_updater'
/workspace/vendor/ruby/2.6.0/gems/dependabot-common-0.108.15/lib/dependabot/shared_helpers.rb:112:in `run_helper_subprocess': 404 Not Found - GET https://registry.npmjs.org/mshell-node-metrics - Not found (Dependabot::SharedHelpers::HelperSubprocessFailed)
	12: from ./generic-update-script.rb:126:in `<main>'
	11: from ./generic-update-script.rb:126:in `each'
	10: from ./generic-update-script.rb:164:in `block in <main>'
	 9: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:39:in `updated_dependency_files'
	 8: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:148:in `updated_lockfiles'
	 7: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:148:in `each'
	 6: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:149:in `block in updated_lockfiles'
	 5: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:120:in `package_lock_changed?'
	 4: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater.rb:187:in `updated_package_lock_content'
	 3: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:24:in `updated_lockfile_content'
	 2: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:41:in `rescue in updated_lockfile_content'
	 1: from /workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:181:in `handle_npm_updater_error'
/workspace/vendor/ruby/2.6.0/gems/dependabot-npm_and_yarn-0.108.15/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:320:in `handle_missing_package': The following source could not be reached as it requires authentication (and any provided details were invalid or lacked the required permissions): artifactory.skyscannertools.net/artifactory/api/npm/npm/ (Dependabot::PrivateSourceAuthenticationFailure)

The exact same setup correctly raises PRs when I add an npmrc to the repo in question specifying the default.

Honestly, I don't have many leads on this one, and without the ability to replicate it's going to take me many hours to try to MacGyver it out. If you want to debug locally I'd suggest walking through in a script and when you get to the file updater stage inspecting the .npmrc that Dependabot is generating (file_updater.send(:npm_lockfile_updater).send(:npmrc_content) should get it for you). My guess is that something is going wrong in generating that, and we can adjust the logic in NpmrcBuilder to fix that, but I can't help much more than that without a reproduction case.

OK, in that case the issue is almost certainly in here. That code takes all of the registries you've specified in credentials and loops through them, looking for any unscoped packages that use that registry. If it finds any then it declares it global.
For some reason that line isn't determining that any of the registries you're providing in your credentials are used globally. Hard to figure out why without looking through your lockfile, but making that check more robust is what will fix this.

We've been looking at fixing this, however we are now unable to recreate, so closing this issue.


Create CI.yml

Closes
Closes #1045

Description
Added file

Screenshots

Note to reviewers

Checklist:

[x] I have linked the PR to the correct issue.
[x] I have read the Contribution Guidelines
[x] I have built and tested the changes, and they do not break or show any errors.

@Vaishnavi-Patil2211 please merge this

Solve merge conflict


CYC-163 Fix Observer and Date format issues

Description
Closes #186
Closes #160
See CYC-163
Fixes improper date time formatting when adding a supplier via the create and update endpoints by casting dates to a Carbon datetime object
Adds a SaleObserver that automatically adjusts the delivery date of a paid sale as well as changing quantities upon sale of an object.
Fixes the PurchaseOrderObserver to change the delivery date to the current time when an object is delivered.
How to test

Login and ensure that a vendor can be created via the Add vendor button
Attempt to complete a Sale via the Sales interface
Change the status of a purchase order to PurchaseOrder::RECEIVED via tinker (the interface does not currently allow this.)

i'll be self-merging this due to time constraints.


Check for undefined before assigning Promise

Add a guard to using Promise - if Promise is not defined trying to assign it to something will cause a ReferenceError:
Fixes bug in #164

Makes sense - thanks :+1:

:+1: my bad.


feat(icon): add star_two icon

I would name this icon stars. 😊

Hi @umitkucuk our two star icon in the design file is below (i added the svg export for you). Can you replace it with the name "two_stars"?

@muratcorlu we also have three stars icon with the name "rating", maybe we can name it as three_stars? 😅

I thought prefixing the icon names with "star_" would be good for the alphabetic order;
star, star_double, star_triple (If there is no icon with more than three stars 😊)
What do you think? @muratcorlu @buseselvi

It's ready for review again.

We didn't rename rating icon here but I'm also a bit hesitant about renaming it since there can be some people who already use it. But to be honest, I see more icons those have names with context in trendyol, which does not make sense for a generic library. I'll create a separate issue for that.

@buseselvi I couldn't see this new icon in our Figma document. Can you sync it with same name?


[PRD-5778]-JDBC connection details still remains even after removing …

…from
Options tab for MsSQL connections.JDBC connection details still remains

set using pluginId insteadof constant
add unit test

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f core/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/src/org/pentaho/di/core/database/DatabaseMeta.java
  core/test-src/org/pentaho/di/core/database/DatabaseMetaTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.database.DatabaseMeta

Branch Change:  + 2.37%
Complexity Change:  + 1.15%
Instruction Change:  + 1.80%
Line Change:  + 1.61%
Method Change:  + 1.71%

org.pentaho.di.core.logging.KettleLogStore.new TimerTask() {...}

Branch Change:  + 50.00%
Complexity Change:  + 33.33%
Instruction Change:  + 75.68%
Line Change:  + 83.33%
Method Change:  + 50.00%

org.pentaho.di.core.logging.LoggingBuffer

Complexity Change:  + 1.72%
Instruction Change:  + 1.09%
Line Change:  + 1.53%
Method Change:  + 3.45%

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f core/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/src/org/pentaho/di/core/database/DatabaseMeta.java
  core/test-src/org/pentaho/di/core/database/DatabaseMetaTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.database.DatabaseMeta

Branch Change:  + 2.37%
Complexity Change:  + 1.15%
Instruction Change:  + 1.80%
Line Change:  + 1.61%
Method Change:  + 1.71%


Mbot2: Open Roberta Connector program serial monitor does not display output

The mbot2 robot has the functionality to write data to the serial port, but the ORC serial monitor does not display this data. This should be fixed

Tested source code on openroberta-connector. Supported robots (defined in robots.properties in the below commit) can now use the serial monitor in Open Roberta Connector program.
Related commit here.

Tested on mBot2 with latest Open Roberta Connector app (v1.6.3). Serial monitor works as expected.


Sync v2 is specced as /v3/sync on the new spec website

Link to problem area: https://spec.matrix.org/latest/client-server-api/#get_matrixclientv3sync
Issue
This is clearly sync v2, while v3 is still in MSC land

The "v3" in the endpoint name and in "Sync v3" mean different things.  /v3/sync is correct, as per MSC2844.  We may want to rename "Sync v3" to something else to reduce confusion, but that's an issue for the "Sync v3" proposal, and not a spec issue.

This was raised several times over the last year - it's unfortunate, but significantly lower priority than getting the feature out.