Installing Python dependencis Failed

ERROR: Command errored out with exit status 1: /home/praveen/Jarvis/jarvis_virtualenv/bin/python /home/praveen/Jarvis/jarvis_virtualenv/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpi03msa_5 Check the logs for full command output.
Install Python dependencies failed
Can you please help me ?

First of all can you the logs? would be nice because that is not a lot info there

I have the same problem but maybe it's because that I'm running it on Virtual Machine?
help is needed!
thank's

ERROR: Command errored out with exit status 1:
command: /home/nameless/Jarvis/jarvis_virtualenv/bin/python /home/nameless/Jarvis/jarvis_virtualenv/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpb2gp_t0x
cwd: /tmp/pip-install-nta5jkh1/scipy
Complete output (171 lines):
lapack_opt_info:
lapack_mkl_info:
customize UnixCCompiler
libraries mkl_rt not found in ['/home/nameless/Jarvis/jarvis_virtualenv/lib', '/usr/local/lib', '/usr/lib64', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
NOT AVAILABLE
openblas_lapack_info:
customize UnixCCompiler
customize UnixCCompiler
  libraries openblas not found in ['/home/nameless/Jarvis/jarvis_virtualenv/lib', '/usr/local/lib', '/usr/lib64', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
  NOT AVAILABLE

openblas_clapack_info:
customize UnixCCompiler
customize UnixCCompiler
  libraries openblas,lapack not found in ['/home/nameless/Jarvis/jarvis_virtualenv/lib', '/usr/local/lib', '/usr/lib64', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
  NOT AVAILABLE

atlas_3_10_threads_info:
Setting PTATLAS=ATLAS
customize UnixCCompiler
  libraries tatlas,tatlas not found in /home/nameless/Jarvis/jarvis_virtualenv/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /home/nameless/Jarvis/jarvis_virtualenv/lib
customize UnixCCompiler
  libraries tatlas,tatlas not found in /usr/local/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/local/lib
customize UnixCCompiler
  libraries tatlas,tatlas not found in /usr/lib64
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib64
customize UnixCCompiler
  libraries tatlas,tatlas not found in /usr/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib
customize UnixCCompiler
  libraries tatlas,tatlas not found in /usr/lib/x86_64-linux-gnu
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
<class 'numpy.distutils.system_info.atlas_3_10_threads_info'>
  NOT AVAILABLE

atlas_3_10_info:
customize UnixCCompiler
  libraries satlas,satlas not found in /home/nameless/Jarvis/jarvis_virtualenv/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /home/nameless/Jarvis/jarvis_virtualenv/lib
customize UnixCCompiler
  libraries satlas,satlas not found in /usr/local/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/local/lib
customize UnixCCompiler
  libraries satlas,satlas not found in /usr/lib64
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib64
customize UnixCCompiler
  libraries satlas,satlas not found in /usr/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib
customize UnixCCompiler
  libraries satlas,satlas not found in /usr/lib/x86_64-linux-gnu
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
<class 'numpy.distutils.system_info.atlas_3_10_info'>
  NOT AVAILABLE

atlas_threads_info:
Setting PTATLAS=ATLAS
customize UnixCCompiler
  libraries ptf77blas,ptcblas,atlas not found in /home/nameless/Jarvis/jarvis_virtualenv/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /home/nameless/Jarvis/jarvis_virtualenv/lib
customize UnixCCompiler
  libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/local/lib
customize UnixCCompiler
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib64
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib64
customize UnixCCompiler
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib
customize UnixCCompiler
  libraries ptf77blas,ptcblas,atlas not found in /usr/lib/x86_64-linux-gnu
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
<class 'numpy.distutils.system_info.atlas_threads_info'>
  NOT AVAILABLE

atlas_info:
customize UnixCCompiler
  libraries f77blas,cblas,atlas not found in /home/nameless/Jarvis/jarvis_virtualenv/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /home/nameless/Jarvis/jarvis_virtualenv/lib
customize UnixCCompiler
  libraries f77blas,cblas,atlas not found in /usr/local/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/local/lib
customize UnixCCompiler
  libraries f77blas,cblas,atlas not found in /usr/lib64
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib64
customize UnixCCompiler
  libraries f77blas,cblas,atlas not found in /usr/lib
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib
customize UnixCCompiler
  libraries f77blas,cblas,atlas not found in /usr/lib/x86_64-linux-gnu
customize UnixCCompiler
  libraries lapack_atlas not found in /usr/lib/x86_64-linux-gnu
<class 'numpy.distutils.system_info.atlas_info'>
  NOT AVAILABLE

lapack_info:
customize UnixCCompiler
  libraries lapack not found in ['/home/nameless/Jarvis/jarvis_virtualenv/lib', '/usr/local/lib', '/usr/lib64', '/usr/lib', '/usr/lib/x86_64-linux-gnu']
  NOT AVAILABLE

lapack_src_info:
  NOT AVAILABLE

  NOT AVAILABLE

setup.py:111: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
  import imp
setup.py:386: UserWarning: Unrecognized setuptools command ('dist_info --egg-base /tmp/pip-modern-metadata-l5_ywgou'), proceeding with generating Cython sources and expanding templates
  warnings.warn("Unrecognized setuptools command ('{}'), proceeding with "
Running from scipy source directory.
/tmp/pip-build-env-biqo5lkr/overlay/lib/python3.8/site-packages/numpy/distutils/system_info.py:624: UserWarning:
    Atlas (http://math-atlas.sourceforge.net/) libraries not found.
    Directories to search for the libraries can be specified in the
    numpy/distutils/site.cfg file (section [atlas]) or by setting
    the ATLAS environment variable.
  self.calc_info()
/tmp/pip-build-env-biqo5lkr/overlay/lib/python3.8/site-packages/numpy/distutils/system_info.py:624: UserWarning:
    Lapack (http://www.netlib.org/lapack/) libraries not found.
    Directories to search for the libraries can be specified in the
    numpy/distutils/site.cfg file (section [lapack]) or by setting
    the LAPACK environment variable.
  self.calc_info()
/tmp/pip-build-env-biqo5lkr/overlay/lib/python3.8/site-packages/numpy/distutils/system_info.py:624: UserWarning:
    Lapack (http://www.netlib.org/lapack/) sources not found.
    Directories to search for the sources can be specified in the
    numpy/distutils/site.cfg file (section [lapack_src]) or by setting
    the LAPACK_SRC environment variable.
  self.calc_info()
Traceback (most recent call last):
  File "/home/nameless/Jarvis/jarvis_virtualenv/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in <module>
    main()
  File "/home/nameless/Jarvis/jarvis_virtualenv/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
    json_out['return_val'] = hook(**hook_input['kwargs'])
  File "/home/nameless/Jarvis/jarvis_virtualenv/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py", line 133, in prepare_metadata_for_build_wheel
    return hook(metadata_directory, config_settings)
  File "/tmp/pip-build-env-biqo5lkr/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 157, in prepare_metadata_for_build_wheel
    self.run_setup()
  File "/tmp/pip-build-env-biqo5lkr/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 248, in run_setup
    super(_BuildMetaLegacyBackend,
  File "/tmp/pip-build-env-biqo5lkr/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 142, in run_setup
    exec(compile(code, __file__, 'exec'), locals())
  File "setup.py", line 505, in <module>
    setup_package()
  File "setup.py", line 501, in setup_package
    setup(**metadata)
  File "/tmp/pip-build-env-biqo5lkr/overlay/lib/python3.8/site-packages/numpy/distutils/core.py", line 135, in setup
    config = configuration()
  File "setup.py", line 403, in configuration
    raise NotFoundError(msg)
numpy.distutils.system_info.NotFoundError: No lapack/blas resources found.
----------------------------------------

ERROR: Command errored out with exit status 1: /home/nameless/Jarvis/jarvis_virtualenv/bin/python /home/nameless/Jarvis/jarvis_virtualenv/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py prepare_metadata_for_build_wheel /tmp/tmpb2gp_t0x Check the logs for full command output.
Install Python dependencies failed
This is the ERROR that i get

Sounds like this issue https://github.com/scipy/scipy/issues/9005, the solution showed there is to
sudo apt-get install gfortran libopenblas-dev liblapack-dev
sudo pip install scipy

More info can be found in this stackoverflow thread https://stackoverflow.com/questions/7496547/does-python-scipy-need-blas
Let me  know if it worked

This was the same for me  11Tuvork28  where I was not able to install all the dependencies but I was trying to install this on Kali linux, what I ended up doing was adding the main official Ubuntu repository in addition to the default kali repos but that still didn't work until I used the solution you provided which was to run the folowing commands in terminal
sudo apt-get install gfortran libopenblas-dev liblapack-dev
sudo pip install scipy
At this point I was able to build every wheel except for lxml as to which I am still looking for a solution.
Do you have any other suggestions here is the error I got or at least what I could see in terminal and copy:
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
    |           ^~~~~~~~~~

src/lxml/etree.c:231095:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231095 |   __pyx_codeobj__584 = (PyObject*)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__583, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_set_global_max_depth, 450, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__584)) __PYX_ERR(3, 450, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231107:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231107 |   __pyx_codeobj__586 = (PyObject)__Pyx_PyCode_New(2, 1, 4, 0, CO_OPTIMIZED|CO_NEWLOCALS|CO_VARKEYWORDS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__585, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_apply, 469, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__586)) __PYX_ERR(3, 469, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231119:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231119 |   __pyx_codeobj__588 = (PyObject)__Pyx_PyCode_New(2, 0, 2, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__587, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_tostring, 475, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__588)) __PYX_ERR(3, 475, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231131:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231131 |   __pyx_codeobj__590 = (PyObject)__Pyx_PyCode_New(2, 0, 2, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__589, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_deepcopy, 484, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__590)) __PYX_ERR(3, 484, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231143:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231143 |   __pyx_codeobj__592 = (PyObject)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__591, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_copy_2, 487, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__592)) __PYX_ERR(3, 487, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231155:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231155 |   __pyx_codeobj__594 = (PyObject)__Pyx_PyCode_New(2, 1, 10, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__593, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_write_output, 713, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__594)) __PYX_ERR(3, 713, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231167:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231167 |   __pyx_codeobj__596 = (PyObject)__Pyx_PyCode_New(1, 0, 5, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__595, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_unicode_2, 783, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__596)) __PYX_ERR(3, 783, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231190:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231190 |   __pyx_codeobj__599 = (PyObject)__Pyx_PyCode_New(2, 0, 9, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__598, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_parseXSL, 891, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__599)) __PYX_ERR(3, 891, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231202:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231202 |   __pyx_codeobj__601 = (PyObject)__Pyx_PyCode_New(3, 0, 5, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__600, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xslt_pxi, __pyx_n_s_set, 948, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__601)) __PYX_ERR(3, 948, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231214:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231214 |   __pyx_codeobj__603 = (PyObject)__Pyx_PyCode_New(5, 0, 5, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__602, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xsltext_pxi, __pyx_n_s_execute, 6, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__603)) __PYX_ERR(19, 6, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231226:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231226 |   __pyx_codeobj__605 = (PyObject)__Pyx_PyCode_New(4, 2, 9, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__604, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xsltext_pxi, __pyx_n_s_apply_templates, 22, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__605)) __PYX_ERR(19, 22, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231238:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231238 |   __pyx_codeobj__607 = (PyObject)__Pyx_PyCode_New(3, 2, 8, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__606, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_xsltext_pxi, __pyx_n_s_process_children, 74, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__607)) __PYX_ERR(19, 74, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231250:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231250 |   __pyx_codeobj__609 = (PyObject)__Pyx_PyCode_New(2, 0, 2, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__608, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_etree_pyx, __pyx_n_s_validate, 3522, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__609)) __PYX_ERR(0, 3522, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231262:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231262 |   __pyx_codeobj__611 = (PyObject)__Pyx_PyCode_New(2, 0, 2, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__610, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_etree_pyx, __pyx_n_s_assertValid, 3531, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__611)) __PYX_ERR(0, 3531, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231274:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231274 |   __pyx_codeobj__613 = (PyObject)__Pyx_PyCode_New(2, 0, 2, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__612, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_etree_pyx, __pyx_n_s_assert, 3541, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__613)) __PYX_ERR(0, 3541, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231286:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231286 |   __pyx_codeobj__615 = (PyObject)__Pyx_PyCode_New(7, 0, 7, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__614, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_etree_pyx, __pyx_n_s_append_log_message, 3550, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__615)) __PYX_ERR(0, 3550, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231298:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231298 |   __pyx_codeobj__617 = (PyObject)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__616, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_etree_pyx, __pyx_n_s_clear_error_log, 3555, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__617)) __PYX_ERR(0, 3555, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231310:34: note: in expansion of macro ‘__Pyx_PyCode_New’
231310 |   __pyx_codeobj__82 = (PyObject)__Pyx_PyCode_New(1, 0, 2, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__618, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_dtd_pxi, __pyx_n_s_itervalues, 163, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__82)) __PYX_ERR(20, 163, __pyx_L1_error)
|                                  ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231322:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231322 |   __pyx_codeobj__620 = (PyObject)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__619, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_dtd_pxi, __pyx_n_s_values, 170, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__620)) __PYX_ERR(20, 170, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231334:34: note: in expansion of macro ‘__Pyx_PyCode_New’
231334 |   __pyx_codeobj__83 = (PyObject)__Pyx_PyCode_New(1, 0, 3, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__621, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_dtd_pxi, __pyx_n_s_iterattributes, 223, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__83)) __PYX_ERR(20, 223, __pyx_L1_error)
|                                  ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231346:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231346 |   __pyx_codeobj__623 = (PyObject)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__622, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_dtd_pxi, __pyx_n_s_attributes, 233, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__623)) __PYX_ERR(20, 233, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231358:34: note: in expansion of macro ‘__Pyx_PyCode_New’
231358 |   __pyx_codeobj__84 = (PyObject)__Pyx_PyCode_New(1, 0, 3, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__624, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_dtd_pxi, __pyx_n_s_iterelements, 314, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__84)) __PYX_ERR(20, 314, __pyx_L1_error)
|                                  ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231370:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231370 |   __pyx_codeobj__626 = (PyObject)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__625, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_dtd_pxi, __pyx_n_s_elements, 324, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__626)) __PYX_ERR(20, 324, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231382:34: note: in expansion of macro ‘__Pyx_PyCode_New’
231382 |   __pyx_codeobj__85 = (PyObject)__Pyx_PyCode_New(1, 0, 3, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__627, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_dtd_pxi, __pyx_n_s_iterentities, 327, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__85)) __PYX_ERR(20, 327, __pyx_L1_error)
|                                  ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231394:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231394 |   __pyx_codeobj__629 = (PyObject)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__628, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_dtd_pxi, __pyx_n_s_entities, 337, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__629)) __PYX_ERR(20, 337, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231406:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231406 |   __pyx_codeobj__631 = (PyObject)__Pyx_PyCode_New(3, 0, 4, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__630, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_relaxng_pxi, __pyx_n_s_from_rnc_string, 154, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__631)) __PYX_ERR(21, 154, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231429:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231429 |   __pyx_codeobj__634 = (PyObject)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__633, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_debug_pxi, __pyx_n_s_bytes_used, 7, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__634)) __PYX_ERR(25, 7, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231441:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231441 |   __pyx_codeobj__636 = (PyObject)__Pyx_PyCode_New(1, 0, 1, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__635, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_debug_pxi, __pyx_n_s_blocks_used, 16, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__636)) __PYX_ERR(25, 16, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231453:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231453 |   __pyx_codeobj__638 = (PyObject)__Pyx_PyCode_New(1, 0, 2, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__637, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_debug_pxi, __pyx_n_s_dict_size, 25, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__638)) __PYX_ERR(25, 25, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231465:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231465 |   __pyx_codeobj__640 = (PyObject)__Pyx_PyCode_New(3, 0, 5, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__639, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_debug_pxi, __pyx_n_s_dump, 36, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__640)) __PYX_ERR(25, 36, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject ) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:231477:35: note: in expansion of macro ‘__Pyx_PyCode_New’
231477 |   __pyx_codeobj__642 = (PyObject)__Pyx_PyCode_New(3, 0, 4, 0, CO_OPTIMIZED|CO_NEWLOCALS, __pyx_empty_bytes, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_tuple__641, __pyx_empty_tuple, __pyx_empty_tuple, __pyx_kp_s_src_lxml_debug_pxi, __pyx_n_s_show, 66, __pyx_empty_bytes); if (unlikely(!__pyx_codeobj__642)) __PYX_ERR(25, 66, __pyx_L1_error)
|                                   ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject *) PyCode_New(
|                            ^~~~~~~~~~
src/lxml/etree.c: In function ‘__Pyx_CreateCodeObjectForTraceback’:
src/lxml/etree.c:411:11: error: too many arguments to function ‘PyCode_New’
411 |           PyCode_New(a, 0, k, l, s, f, code, c, n, v, fv, cell, fn, name, fline, lnos)
|           ^~~~~~~~~~
src/lxml/etree.c:247326:15: note: in expansion of macro ‘__Pyx_PyCode_New’
247326 |     py_code = __Pyx_PyCode_New(
|               ^~~~~~~~~~~~~~~~
In file included from /usr/include/python3.8/compile.h:5,
from /usr/include/python3.8/Python.h:138,
from src/lxml/etree.c:97:
/usr/include/python3.8/code.h:122:28: note: declared here
122 | PyAPI_FUNC(PyCodeObject *) PyCode_New(
|                            ^~~~~~~~~~
Compile failed: command 'x86_64-linux-gnu-gcc' failed with exit status 1
creating tmp
cc -I/usr/include/libxml2 -I/usr/include/libxml2 -c /tmp/xmlXPathInit14718k_3.c -o tmp/xmlXPathInit14718k_3.o
cc tmp/xmlXPathInit14718k_3.o -lxml2 -o a.out
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
ERROR: Failed building wheel for lxml

Are you still facing the issue? @utawkin2me @WolfsKing-93

Yes
Sent from ProtonMail mobile
-------- Original Message --------
On Sep 24, 2020, 2:56 PM, tuvork wrote:

Are you still facing the issue? @utawkin2me @WolfsKing-93
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Internal link on NuxtJs project

Hello,
I am using vue2-editor with nuxt.js and is it possible to put internal link  ?  Is same with  in vuejs ?
Many Thanks,

1.- In nuxt.config.js in the plugin section you must to write this:
plugins: [{ src<EMAIL_ADDRESS>ssr: false }
2.- You have to create a file named 'vue-editor.js' inside 'plugins' folder and write inside this:
`import Vue from 'vue'
import Editor from 'vue2-editor' //this is in my node_modules because i read in the doc they write another name, maybe by the old version I dont know, but you must to find the name in your node_modules
Vue.use(Editor)`
3.- In your Page or Component write the tag <vue-editor v-model="content"></vue-editor> and import the components and declare the 'content':


Omit Unused Data Prop

As mentioned in https://github.com/mozilla-services/react-jsonschema-form/issues/754 ,
We have a working solution for only returning the data actually used in the form. In addition to the problems stated in the reported issue, we also dont want passthrough unused data, even if we provided it originally. We just want to get the data from whatever is in the visible form. As stated, there is no super straight fwd solution, but we think we found a pretty reasonable and not too intrusive solution.
The idea is....
• Add a name attribute to all of the fields that is the json path to the form data, e.g. foo.bar.1.name (something that IMO should be there regardless of this solution).

Checkboxes no longer have randomly generated names

• onSubmit we can get all of the form elements and make a list of name attributes (the paths).
• use lodash _.pick(formData, [ARRAY_OF_FIELD_NAMES]) to get only the used data and return that as the formData.
We do this if they set the omitUnusedData prop to true otherwise it defaults to false and works as is.
My coworker @codegains helped me out a bit on this too.
==================
A couple things I wish were better...

I wish there was a more reliable way to generate the paths rather than doing string manipulation on the id.  But it was hard to access all the necessary data at the point of adding the name attribute.

The idToPath could fail if the consumer provides a idPrefix prop with an underscore .

@codegains update addresses both of the above. no longer an issue
The bonus of having these paths as the name attributes on the fields is that in the future you could potentially simplify your submit and changes with something like https://github.com/maxatwork/form2js (this is super old but basically it gathers formData based on the name attributes more like traditional html forms).

About the name omitUnusedData we were definitely mulling over a lot of names and this was the best we could come up with. Some other ideas were omitUnownedData or omitNonFormData. We didn't want to name it something like omitNonSchemaData because some data could be tied to some field in the schema, but not rendered because of a dependent not being met. Definitely open to suggestions though. Thanks!

About the name omitUnusedData we were definitely mulling over a lot of names and this was the best we could come up with. Some other ideas were omitUnownedData or omitNonFormData. We didn't want to name it something like omitNonSchemaData because some data could be tied to some field in the schema, but not rendered because of a dependent not being met. Definitely open to suggestions though. Thanks!

Some more ideas: omitDisallowedData or omitExtraData

any word on this MR ? would be super useful..

@epicfaace Is there anything else in the PR that you think we need to address?

I'm still kind of uncomfortable about requiring every custom widget to have a name attribute. For example, if I were to create a <div contenteditable> widget, then it would have to have a name attribute, which would be non-standard.
If that's the only way to go about this, then I understand -- but might not there be another way to do this that is agnostic to the DOM elements generated themselves?

@epicfaace we could potentially use a data- attribute instead. Something like data-name.  I like name better for form inputs but you are correct in saying it would be non-standard on a div element.
Another idea is to support both, so when we check the form for inputs we could look for name attributes OR the custom data-name attribute. I think that would solve your concerns. But I dont think there is any way around having to set an attribute of some kind if they want to use the omit prop

Yeah, good suggestions. I think using something like removeAdditional might be a feasible solution that is independent of the DOM, as long as it works with dependencies -- if https://github.com/epoberezkin/ajv/issues/970 is fixed. Is my thinking right here -- or am I missing another problem with this approach?

@epicfaace Well epoberezkin/ajv#970 is most likely the biggest problem with that approach, so I'm interested to see what they say, but I'm somewhat not optimistic that they will support that behavior. If you see this section of the docs https://github.com/epoberezkin/ajv#filtering-data, they mention that the standard is that everything not included in the properties is considered considered an additional property. Actual quote:

With the option removeAdditional: true the validation will pass for the object { "foo": "abc"} but will fail for the object {"bar": 1}. It happens because while the first subschema in oneOf is validated, the property bar is removed because it is an additional property according to the standard (because it is not included in properties keyword in the same schema).

However, I do agree with you that it should work like you are suggesting because of the fact that the validate returns false when there is a dependency and "additionalProperties": false is in the schema. That seems like an oversight in either the standard or ajv to me.
Another issue I foresee would be the the fact that we would have to add the additionalProperties: false config to all the sub-schemas programmatically for nested objects before filtering the data. Maybe it's not a big deal, but it could be messy. I've tried using removeAdditional: "all" in this fiddle: https://jsfiddle.net/tjaeger/aLd7zn6o/3/, but it doesn't seem to work at all. In epoberezkin/ajv#634, he says that adding additionalProperties: false to all objects and using removeAdditional: true is the correct approach.

Actually, basically the same problem as epoberezkin/ajv#970 happens with anyOf, oneOf, allOf, etc.  as well. See: https://jsfiddle.net/tjaeger/c98axmd0/24/, which they deemed to be working correctly. So, I wouldn't know how to get around this if we were to use removeAdditional.

@CodeGains I see, that makes sense, thanks for the detailed explanation.
What if we do this -- instead of querying for elements that are shown with a name attribute, we use the idSchema itself and see which keys are present there? That way our solution is not dependent on the DOM.

Hmm that might work, I'll try it out and see.

@epicfaace the problem I'm trying to overcome with the idSchema approach is that the array indexes are not in the idSchema object.

@CodeGains I don't think that should pose a problem. I wouldn't imagine needing to omit specific indexes using omitExtraData, although please correct me if I'm wrong.
Your idSchema could, for example, just look like this:
{
    "$id": "root",
    "tasks": {
        "$id": "root_tasks"
   }
}

And if your formData looks like this:
{
     "tasks": ["a", "b", "c"]
}

Then doing pick(formData, ["tasks"]) will still get you the data you need.

@epicfaace That's not really the problem I was thinking about. If the array was an array of objects and some object had extra values then if you picked the whole array, you would get those extra values.

@CodeGains you're right, here's an example: https://jsfiddle.net/epicfaace/dj37hvge/
It doesn't even seem that idSchema is generated correctly; I'd expect it to contain root_b once "b" shows up.

@epicfaace Wasn't able to work on this for a while, but now I think I'm pretty close to having a solution that doesn't depend on the DOM. Just to let you know not to close this yet. Thanks!

@codegains Perfect, thank you so much. Look forward to seeing it!

Yaay, I'm looking forward to see this merged in master! ;)

Yaay, I'm looking forward to see it live! Does it solve the issue replicable also in Schema dependencies on https://mozilla-services.github.io/react-jsonschema-form/ that:

You change the Conditional/Do you have any pets?* field to Yes: One and fill the value in How old is your pet?*
You change the Conditional/Do you have any pets?* field to Yes: More than one and select some option for Do you want to get rid of any?*
Now you can see that the formData contains values for both fields: How old is your pet?* and also Do you want to get rid of any?*

Yes, it should fix that. Sorry for the delay, now I'm having to create my own schema object similar to idSchema and refactor some stuff, because my solution was not working for dependencies within array objects. The schema object I am creating for the final solution should have contain arrays with each object in the array listing which fields are in use.

Need to rip out old changes, update docs, update tests. May just make another PR instead because it might be easier.
However, the current solution should be working in this branch if anyone wants to test it out. Set the defaultProp for omitExtraData to true in Form.js.

@CodeGains Hi, I've tried the branch, it seems to have issues with arrays where the items are $ref
meaning something like:
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    },
    "intro": {
      "type": "object",
      "properties": {
        "slides": {
          "type": "array",
          "items": {
            "$ref": "#/definitions/Slide"
          }
        }
      }
    }
  },
  "definitions": {
    "Slide": {
      ...
      ...
    }
  }
}

Using the above schema on some data it will remove "intro.slides" array from data...

@ValYouW  i think this project would really benefit from trying to resolve refs and allOfs first thing, before it does anything with it. It would keep the code in this project much simpler.. see example in this comment....
https://github.com/mozilla-services/react-jsonschema-form/issues/1237#issuecomment-477394478

Ah, thx for the reference...

@epicfaace what do you think about adding the libraries mentioned in https://github.com/mozilla-services/react-jsonschema-form/issues/1237#issuecomment-477394478 ?
If you always resolve the refs and allOfs right off the bat, we can get rid of some of the complexity in the current resolveSchema.  Let me know what you think. I would be willing to try and figure it out and make a PR if you think it would be worthwhile.

@ValYouW Nice catch, I'll try to fix that now. Worst case, is that I can resolve the references myself (like @travisdahl suggested) in my solution before building up my name schema.

I ended up using @cloudflare/json-schema-ref-loader which deref during "build time"...

I've created PR #1283 with the updated solution. I also fixed the problem @ValYouW mentioned.

close in favor of https://github.com/mozilla-services/react-jsonschema-form/pull/1283/files


As a Metric user I want opendata DB primary key to use bigint instead of integer

Opendata DB primary key sequence runs out of integer (int4) values in larger X-Road instances. Bigint should be used instead.
Software version:
1.1.1, 1.2.0
Host OS and version:
Ubuntu 20.04
The schema in anonymizer defines bigint as id column type:
https://github.com/nordic-institute/X-Road-Metrics/blob/64fb79deab605757054fe0081d8a11636526abd9/anonymizer_module/etc/field_data.yaml#L4
But id column type is discarded during schema object creation:
https://github.com/nordic-institute/X-Road-Metrics/blob/64fb79deab605757054fe0081d8a11636526abd9/anonymizer_module/opmon_anonymizer/iio/opendata_writer.py#L59
Then during creation of table id column type is hardcoded to be SERIAL:
https://github.com/nordic-institute/X-Road-Metrics/blob/64fb79deab605757054fe0081d8a11636526abd9/anonymizer_module/opmon_anonymizer/iio/postgresql_manager.py#L118
Example error log of anonymizer:
File \"/usr/lib/python3/dist-packages/opmon_anonymizer/iio/postgresql_manager.py\", line 58, in add_data
cursor.execute(query)psycopg2.errors.SequenceGeneratorLimitExceeded: nextval:
reached maximum value of sequence \"logs_id_seq\"<PHONE_NUMBER>)

Proposed solution:
Replace id SERIAL PRIMARY KEY with id BIGINT PRIMARY KEY GENERATED ALWAYS AS IDENTITY in postgresql_manager.py because SERIAL types are soft-deprecated:
https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_serial
Hotfix for existing installations (NB! This is slow operation that locks tables, may take hours to complete and requires at least 50% of free drive space):
ALTER TABLE logs ALTER COLUMN id TYPE BIGINT;
ALTER SEQUENCE logs_id_seq AS BIGINT MAXVALUE<PHONE_NUMBER>854775807;

Hello @VitaliStupin!
Thank you for reporting this. We will look into it.


Store: odd performance, while not using a lot of cpu/memory

Thanos, Prometheus and Golang version used:
thanos:v0.12.2
prometheus:v2.15.2
On Kubernetes
Object Storage Provider:
S3
What happened:
I have spikes in the store usage (delays, high Go Routine counts) , but this is not in line with actual cpu/memory usage from the thanos store.
What you expected to happen:
I would expect to see bottlenecks "somewhere" - especially in memory usage of the thanos store OR that it just runs stable. Not having massive spikes without seeing anything in memory/cpu usage (and IMO 0.2 increase in CPU is not much :) )
How to reproduce it (as minimally and precisely as possible):
No idea.
Cpu Usage at the time of the spike

Memory usage at the time of the spike

Cache hits

Latency

Go Routines

Further information
  # Maximum size of items held in the index cache.
  indexCacheSize: 18GB
  # Maximum size of concurrently allocatable bytes for chunks.
  chunkPoolSize: 10GB
  # Maximum amount of samples returned via a single series call. 0 means no limit.
  # NOTE: for efficiency we take 120 as the number of samples in chunk (it cannot be bigger than that),
  # so the actual number of samples might be lower, even though the maximum could be hit.
  grpcSeriesSampleLimit: 0
  # Maximum number of concurrent Series calls.
  grpcSeriesMaxConcurrency: 40
  # Repeat interval for syncing the blocks between local and remote view.
  syncBlockDuration: 3m
  # Number of goroutines to use when syncing blocks from object storage.
  blockSyncConcurrency: 40

What I've tried
I've increased the indexCacheSize. Even though my memory usage for the store is < 10gb, it seems to have a possitive effect on the avg amount of Go Routines AND the severity of the spikes. This seems really odd.
More practically explained between the differences by two examples:
indexCacheSize: 10gb
Pod memory usage: 8 GB
Spikes for ~2000 go routines

indexCacheSize: 18gb
Pod memory usage: 9 GB
Spikes for ~1000 go routines

So it LOOKS (I'm really not sure if this is just coincidence) that increasing the indexCacheSize does more than it might seem to do.

Traced the real high spikes back to this Go Routine:
314 @ 0x4313d0 0x44d587 0x44d55d 0xd9621e 0x45f261
#	0x44d55c	time.Sleep+0x12c						/usr/local/go/src/runtime/time.go:105
#	0xd9621d	github.com/minio/minio-go/v6.Client.newRetryTimer.func2+0x8d	/go/pkg/mod/github.com/minio/minio-go/v6@v6.0.49/retry.go:79

Traced it back to: github.com/minio/minio-go/v6 v6.0.49 which is used in Thanos version 0.12.2
This version of minio-go has this issue: https://github.com/minio/minio-go/issues/1259 which is fixed by this PR: https://github.com/minio/minio-go/pull/1260 which is included in minio-go version 6.0.52.
Thanos version 0.13 uses github.com/minio/minio-go/v6 v6.0.56 which should resolve this issue.
I will update our Thanos soon, and post my feedback.

Upgrading to > 0.12.2 (in my case 0.14, but 0.13 should work too) resolved my issues.

We encountered the same in Thanos v0.31.0
Any one else faced this ?
Thanks


Issue on orders get

Hello,
I'm trying to get all orders from an user, but only thing that I receive is an error. I've posted below the error and also the code that I use on receiving the orders. Is this a bug or I am doing anything wrong?
error: GraphQL Errors: Internal error. Looks like something went wrong on our end. Request ID: 0835140f-3150-4dd1-950d-718d002d998a (include this in support requests).: Undefined location
code: await ShopifyCheckout.instance         .getAllOrders(await ShopifyAuth.currentCustomerAccessToken)
Thank you for your work on this library!
Kind regards,
Iosif

Hey, will try to look into it in the next few days.

Have you tried hard coding the customerAccessToken and not awaiting it?
Just print the customerAccessToken and insert it to the getAllOrders function as the param.
Or save the await ShopifyAuth.currentCustomerAccessToken to a variable before and execute it again with the usage of the variable.

Hello, sorry for the late response. The issue still persists. Have you checked on your end if this functionallity still works? It may also be an issue on shopify side. I'm currently using an development store but I gave full permissions on api to my shopify private app.

Hey, sorry that it took quite a while, the problem seems to be a really dumb one.
The problem is most likely the sort key, the Shopify api allows the RELEVANCE sortkey but somehow it doesn't work with it.
I tried the exact same query now 1. with sortkey: PROCESSED_AT and 2. with sorkey: RELEVANCE.
The processed at sortkey works, long story short try changing the sortkey.

The problem is most likely the sort key, the Shopify api allows the RELEVANCE sortkey but somehow it doesn't work with it.
I tried the exact same query now 1. with sortkey: PROCESSED_AT and 2. with sorkey: RELEVANCE.
The processed at sortkey works, long story short try changing the sortkey.

Hey, no worries for the late response. I have just tested it and it works, changing the sortkey did the trick! Thanks a lot!

Hey, no worries for the late response. I have just tested it and it works, changing the sortkey did the trick! Thanks a lot!


Support for HDP 2.5

Need to modify rpm scripts so that 2.5 gets integrated correctly.

Some python functions has been changed:
stderr:
Traceback (most recent call last):
  File "/var/lib/ambari-agent/cache/stacks/HDP/2.2/services/SCDF/package/scripts/scdf_shell.py", line 39, in <module>
    ScdfShell().execute()
  File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 280, in execute
    method(env)
  File "/var/lib/ambari-agent/cache/stacks/HDP/2.2/services/SCDF/package/scripts/scdf_shell.py", line 31, in install
    self.configure(env)
  File "/var/lib/ambari-agent/cache/stacks/HDP/2.2/services/SCDF/package/scripts/scdf_shell.py", line 36, in configure
    scdf(name='shell')
  File "/var/lib/ambari-agent/cache/stacks/HDP/2.2/services/SCDF/package/scripts/scdf.py", line 48, in scdf
    recursive=True
  File "/usr/lib/python2.6/site-packages/resource_management/core/base.py", line 147, in __init__
    raise Fail("%s received unsupported argument %s" % (self, key))
resource_management.core.exceptions.Fail: Directory['/var/log/scdf'] received unsupported argument recursive

Looks like parameter name has been changed.
   Directory(params.limits_conf_dir,
-            recursive=True,
+            create_parents = True,

Need to investigate how new version definition file works in 2.5 as for default choice new yum repos are not added but those are available if you choose 2.5(default version definition) during a cluster install.

Keeping this as is. Possible work for extension/mpack in a separate tickets in a future.


chore: add LICENSE doc

Description of the Changes
Please add a detailed description of the change, whether it's an enhancement or a bugfix.
If the PR is related to an open issue please link to it.
Checklist

[ ] Changes have been done against master branch, and PR does not conflict
[ ] New unit / functional tests have been added (whenever applicable)
[ ] Test are passing in local environment
[ ] Docs have been updated
[ ] PR title is follow the Conventional Commits convention: <type>[optional scope]: <description>, e.g: fix: prevent racing of requests

This change is

Looks good 👍

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[BUG] --auto parameter

Maybe i missed something or what ,but....:
c:\Users\karbantartokac\Desktop\z>dex encrypt --auto 1.dat 1.enc
-960996e0m Your generated passphrase is: September
←[36mℹ←[0m Using XChaCha20-Poly1305 for encryption
←[36mℹ←[0m Encrypting 1.dat (this may take a while)
←[32m✔←[0m Successfully hashed your key [took 2.96s]
←[32m✔←[0m Encryption successful! File saved as 1.enc [took 0.60s]
c:\Users\karbantartokac\Desktop\z>dex decrypt 1.enc 1.kii
Password: September
←[36mℹ←[0m Using XChaCha20-Poly1305 for decryption
←[36mℹ←[0m Decrypting 1.enc (this may take a while)
←[32m✔←[0m Successfully hashed your key [took 2.85s]
Error: Unable to decrypt your master key (maybe you supplied the wrong key?)
Am i do something wrong ?!

It seems so. September is not a valid password that Dexios will generate - have you tried using "Windows Terminal"? The icons aren't rendering correctly which suggests you're using cmd - this is advised against throughout the OS-specific documentation.
I'll give it a shot using cmd and see if I can reproduce shortly.

I use win10 ,on a restricted user account. Yes. Cmd.exe.
Real "screenshot" : :D

September is not a key that --auto should be generating, so either this is an issue with cmd.exe output (which I have mentioned in the docs, here), or something is broken on Windows specifically. I'll load up a Windows VM and take a look.
Is Dexios installed via cargo?

This works for me, within cmd as well as the Terminal application.
What version of Windows are you using? Have you tried the terminal application?

No,precompiled latest binary.

I was able to reproduce this issue with the precompiled binary, but installing through cargo makes everything work flawlessly. I'll take a deeper look into this, but for now I'd recommend not using --auto on Windows with the pre-compiled binary (until this issue is fixed).

Doesnt work even in Windows PowerShell. Btw thank you!

Doesnt work even in Windows PowerShell. Btw thank you!

I know. I'm not too sure what's causing this issue, as I'd expect pre-compiled binaries to behave the same way.

Tried 3rd party terminal ,called Console2 from sf.net. Doesnt work,too.... (use it daily @ home)

Yeah - it's an issue with the pre-compiled binary itself. I'm not sure why, or how. I need to take a deeper look into it, but I'll remove the pre-compiled binary for now.


Refactor schema loading to follow ATTRTYP documentation

https://msdn.microsoft.com/en-us/library/cc223224.aspx

Do you think it is possible to load the schema (and especially the list of OID Prefix) from AD remotely (without reading directly the file ntsd.dit)?

You can load the schema through regular LDAP. AFAIK the prefix table is only exposed through MS-DRSR. The schema can also be replicated through this protocol.
I use a simple static schema when doing replication instead of loading it from DC, because it would be an overkill in situations when you want to replicate a single account.
BTW if you are interested in prefix table parsing, look at the source code of mimikatz.

Thanks for the tip! I'll look at MS-DRSR a bit more.

I'm now loading the Prefix Table from the DRS_MSG_GETCHGREPLY_V6 object (it is pretty simple to do it). But, my issue is the same as I have before, I don't get the prefixes for extended attributes in my AD.
e.g. I add the attribute in the AD Schema: "ssn" with the OID: 1.2.840.1135<IP_ADDRESS>00.142 but I don't get the prefix in the response object. Because of that, AD returns the ID:<PHONE_NUMBER> and I can't translate it to an OID. Any idea?

Yep, as I understand it, the prefix of that particular OID is hardcoded into ntdsa.dll (as are 30+ other prefixes) and is physically not present in the ntds.dit file. Take a look at my PrefixMap code. I first load the hardcoded prefixes and then load the rest of them from the DB.
Specifically, prefix 1.2.840.113556.1.4 is added using this call:
this.AddBuiltinPrefix(9, "2A864886F7140104");

Actually, I have the prefix in properly loaded from the MS-DRSR request: {[18467, 1.2.840.1135<IP_ADDRESS>00]}
Now, I need to find a way to map the ID<PHONE_NUMBER> to the prefix 18467 and the "value" 142.
BTW, I can send a pull request with the hardcoded prefix 0 to 38 if you think it would be useful.

That would be nice of you. Also, if you could please add string representations of OIDs as comments.

ok, it's done, I've created the pull request.


Remove ToolStart.php entry point

Once existing usage has been removed from Wikimedia Toolforge tool, this can be removed.
This is part of the deprecated interface whereby tools include /data/project/intuition directly on Toolforge, and does not relate to the composer package (for which removal would be less controversial as existing users wouldn't be affected given they would need to upgrade first).

Per legacy documentation at https://github.com/Krinkle/intuition/wiki/Documentation/4065f84748e7ac21303af215f2ddf3fb5b6d255d, Toolforge tool authors that use ToolStart.php will likely contain the phrase Intuition/ToolStart.php somewhere in the tool's code.

Thanks to @bd808, we've now got a list of tools to work from at https://phabricator.wikimedia.org/P7852. I have reduced the results to only matches without vendor/composer/auto (false positives, unrelated), and included it below as checklist:

[ ] ./etwikibots/public_html/common/lib.php
[ ] ./hotarticles/public_html/pageviews/public_html/_head2.php
[ ] ./jarry-common/public_html/i18n.php
[ ] ./jarry-common/public_html/libs/i18n.php
[ ] ./langviews/_head.php
[ ] ./langviews/public_html/_head.php
[ ] ./langviews-test/_head.php
[ ] ./langviews-test/public_html/_head.php
[ ] ./list/src/wmf-tool-list/lib/basetool/LocalConfig-krinkledev.php
[ ] ./list/src/wmf-tool-list/lib/basetool/LocalConfig.php
[ ] ./list/src/wmf-tool-list/lib/basetool/LocalConfig-wmflabs-intuition.php
[ ] ./list/src/wmf-tool-list/lib/basetool/sample-toollabs-LocalConfig.php
[ ] ./massviews/_head.php
[ ] ./massviews/public_html/_head.php
[ ] ./massviews-test/_head.php
[ ] ./massviews-test/public_html/_head.php
[ ] ./mc8/public_html/shared.php
[ ] ./mediaviews/_head.php
[ ] ./mediaviews/public_html/_head.php
[ ] ./metaviews/_head.php
[ ] ./metaviews/public_html/_head.php
[ ] ./meta/xtools/modules/WebTool.php
[ ] ./newwebtest/xtools_old/public_html/WebTool.php
[ ] ./newwebtest/xtools/public_html/WebTool.php
[ ] ./pageviews/_head.php
[ ] ./pageviews/public_html/_head.php
[ ] ./pageviews-test/_head.php
[ ] ./pageviews-test/public_html/_head.php
[ ] ./raun/Raun/index.php
[ ] ./raun/Raun/index-rewrite.php
[ ] ./redirectviews/_head.php
[ ] ./redirectviews/public_html/_head.php
[ ] ./refill/versions/stable/config/config.backup.php
[ ] ./siteviews/_head.php
[ ] ./siteviews/public_html/_head.php
[ ] ./templatetransclusioncheck/public_html/index2.php
[ ] ./templatetransclusioncheck/public_html/index.php
[ ] ./templatetransclusioncheck/public_html/test/index.php
[ ] ./topviews/_head.php
[ ] ./topviews/public_html/_head.php
[ ] ./topviews-test/_head.php
[ ] ./topviews-test/public_html/_head.php
[ ] ./tour/git/wmf-tool-tour/vendor/krinkle/toollabs-base/LocalConfig-krinkledev.php
[ ] ./tour/git/wmf-tool-tour/vendor/krinkle/toollabs-base/LocalConfig.php
[ ] ./tour/git/wmf-tool-tour/vendor/krinkle/toollabs-base/LocalConfig-wmflabs-intuition.php
[ ] ./tour/git/wmf-tool-tour/vendor/krinkle/toollabs-base/sample-toollabs-LocalConfig.php
[ ] ./tsreports-dev/src/intuition/libs/basetool/LocalConfig-krinkledev.php
[ ] ./tsreports-dev/src/intuition/libs/basetool/LocalConfig-wmflabs-intuition.php
[ ] ./tsreports-dev/src/intuition/libs/basetool/sample-toollabs-LocalConfig.php
[ ] ./userviews/_head.php
[ ] ./userviews/pageviews/public_html/_head.php
[ ] ./userviews/public_html/_head.php
[ ] ./wikiinfo/src/wmf-tool-wikiinfo/vendor/krinkle/toollabs-base/LocalConfig-krinkledev.php
[ ] ./wikiinfo/src/wmf-tool-wikiinfo/vendor/krinkle/toollabs-base/LocalConfig-wmflabs-intuition.php
[ ] ./wikiinfo/src/wmf-tool-wikiinfo/vendor/krinkle/toollabs-base/sample-toollabs-LocalConfig.php
[ ] ./wikiviewstats2/dev/functions.php
[ ] ./wikiviewstats2/dev/TsIntuition/includes/libs/ts-krinkle-basetool/sample-LocalConfig.php
[ ] ./wikiviewstats2/intuition/includes/libs/basetool/sample-LocalConfig.php
[ ] ./wikiviewstats2/wvs_modules/I18n.php
[ ] ./wikiviewstats/wvs_modules/I18n.php
[ ] ./xstools/modules/WebTool.php
[ ] ./xtools-articleinfo/modules/WebTool.php
[ ] ./xtools-mab-dev/modules/WebTool.php
[ ] ./xtools/modules/WebTool-backup.php
[ ] ./xtools/modules/WebTool.php
[ ] ./xtools-pages/vendor/composer/autoload_static.php

@MusikAnimal Could you take a look at the pageviews-related entries?
From what I can tell these tools no longer use messages from the library, which means it should be fairly straight-forward to load the library from composer instead.

I've e-mailed the following maintainers:

Kentaur at Wikitech (for etwikibots),
Kaldari at Wikitech (for hotarticles),
Jarry1250 at Wikitech (for jarry-common),
Microchip08 at Wikitech  (for mc8),
Kenrick95 at Wikitech (for raun),
Chameleon at no:User:Chameleon222 (for templatetransclusioncheck).

Hi @Krinkle , thanks for the notice!
For "raun", these two files that you mentioned are located in a folder that's no longer in use by the tool. So I just removed that folder from Toolforge. 😁
Thanks!

Perfect. I've checked it off the list. Thanks @kenrick95!

I've frozen the shared installation at /data/project/intuition to v0.7.0.
This means it is now safe to remove the deprecated ToolStart.php or break PHP5 support in new releases, because this legacy entry point on the Toolforge will stay exactly as it is today.


[improvement] offer a better select defaults usage

ElementUI version
1.0.4
What is Expected?
<el-select v-model="value" placeholder="请选择" :options="options"></el-select>

We can use select this way as default.
What is actually happening?
Now we have to repeat the below everywhere:
<el-select v-model="value" placeholder="请选择">
   <el-option
       v-for="item in options"
      :label="item.label"
      :value="item.value">
    </el-option>
</el-select>

I'm afraid what you suggest is less flexible, e.g. it'll be difficult to assign if a specific option is disabled, and to apply custom templates for options, you'll probably have to write render functions, which is not as intuitive as writing templates directly.
We'll keep it this way.

I don't mean to replace the current way.
Just add to default slot.
What I mean is use
<el-select v-model="value" placeholder="请选择" :options="options"></el-select>

just for short as
<el-select v-model="value" placeholder="请选择">
   <el-option
       v-for="item in options"
      :label="item.label"
      :value="item.value">
    </el-option>
</el-select>


No need for REs

https://github.com/apache/www-site/blob/9f860a8bcd6e5b0172857f6587e4a5ecb82a62eb/theme/plugins/asfgenid.py#L42
The fixups don't currently use REs.
They would be simpler as string replacements.
Alternative, change to use something like:
(re.compile(r'<(/?(script|style|iframe))'), '<\1')

This example did not work properly. I tried, but then reverted it.


update Kristof's description

Note: I've asked Kristof if he didn't send us a picture on purpose and if so, suggested that we could do a stylized image for him. (Maybe we shouldn't just publish his picture without asking, given that he's working with the state commissioner for data protection 😁)
I'll update this PR with his picture once I've heard back from him.

got a higher-res picture, merging this now


TypeScript implementation

Major updates to the application, including some minor breaking changes.
The public updates (that make it less Microsoft-specific) are still in
development; this represents trying to get it ready for updates.

These changes are not finished and there are still some additional refactorings to come in.
I am merging this into dev and master to help make it clear that the goods are coming soon and to encourage more eyes.


Adding override for supportedIdentityProviders erases all userPoolClient settings

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.18..1
Amplify CLI Version
10.7.3
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes, but other overrides in the same file
Describe the bug
I am trying to add a SAML provider to my cognito user pool after running amplify override auth, which works great with the following code:
// override.ts
import { AmplifyAuthCognitoStackTemplate } from "@aws-amplify/cli-extensibility-helper";

export function override(resources: AmplifyAuthCognitoStackTemplate) {
  resources.addCfnResource(
    {
      type: "AWS::Cognito::UserPoolIdentityProvider",
      properties: {
        UserPoolId: { Ref: "UserPool" },
        ProviderName: "Azure",
        ProviderDetails: {
          MetadataURL:
            "https://login.microsoftonline.com/<active_directory_id>/federationmetadata/2007-06/federationmetadata.xml?appid=<app_id>",
        },
        ProviderType: "SAML",
        AttributeMapping: {
          email:
            "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress",
        },
        IdpIdentifiers: ["Azure"],
      },
    },
    "Azure"
  );
}

The problem then comes in when I try to add the new SAML provider to the User Pool Clients (regular and web) to add the new SAML option to the Hosted UI.
I have tried with the following:
// NOT CORRECT, adds new client, need to modify existing
  resources.addCfnResource(
    {
      type: "AWS::Cognito::UserPoolClient",
      properties: {
        SupportedIdentityProviders: ["Azure"],
        UserPoolId: { Ref: "UserPool" },
      },
    },
    "Add Azure to supportedIdentityProviders"
  );

  // THROWS ERROR
  // Type '{ attrClientSecret: string; attrName: string; userPoolId: string; accessTokenValidity: number; allowedOAuthFlows: string[]; allowedOAuthFlowsUserPoolClient: boolean | IResolvable; ... 21 more ...; node: ConstructNode; }' is missing the following properties from type 'CfnUserPoolClient': inspect, cfnProperties, renderProperties, _cfnProperties, and 27 more.
  resources.userPoolClientWeb = {
    supportedIdentityProviders: [
      "Azure",
      ...resources.userPoolClientWeb.supportedIdentityProviders,
    ],
    ...resources.userPoolClientWeb
  };

  // THROWS ERROR on amplify push
  // resources.userPoolClientWeb.supportedIdentityProviders is not iterable
  resources.userPoolClientWeb.supportedIdentityProviders = [
    "Azure",
    ...resources.userPoolClientWeb.supportedIdentityProviders,
  ];

  // ERASES ALL OTHER SUPPORTED IDENTITY PROVIDERS AND OTHER HOSTED UI SETTINGS
  resources.userPoolClientWeb.supportedIdentityProviders = ["Azure"];

  // ERASES ALL OTHER SUPPORTED IDENTITY PROVIDERS AND OTHER HOSTED UI SETTINGS
  const userPoolClientWeb = resources.userPoolClientWeb;
    const baseClient = Array.isArray(userPoolClientWeb.supportedIdentityProviders)
      ? userPoolClientWeb.supportedIdentityProviders
      : [userPoolClientWeb.supportedIdentityProviders];
    // resources.userPoolClient.addPropertyOverride("SupportedIdentityProviders", [
    //   ...baseClient,
    //   "Azure",
    // ]);
    resources.userPoolClientWeb.supportedIdentityProviders = [
      ...baseClient,
      "Azure",
    ];

I have logged resources.userPoolClient and it returns the following, noting the undefined in the original supportedIdentityProviders:
userPoolClientWeb: [Circular *1],
    userPoolClient: CfnUserPoolClient {
      node: [ConstructNode],
      stack: [Circular *2],
      logicalId: '${Token[AmplifyAuthCongitoStack.UserPoolClient.LogicalID.676]}',
      cfnOptions: {},
      rawOverrides: {},
      dependsOn: [Set],
      cfnResourceType: 'AWS::Cognito::UserPoolClient',
      _cfnProperties: [Object],
      attrClientSecret: '${Token[TOKEN.677]}',
      attrName: '${Token[TOKEN.678]}',
      userPoolId: '${Token[TOKEN.675]}',
      accessTokenValidity: undefined,
      allowedOAuthFlows: undefined,
      allowedOAuthFlowsUserPoolClient: undefined,
      allowedOAuthScopes: undefined,
      analyticsConfiguration: undefined,
      callbackUrLs: undefined,
      clientName: '<resource_name>_app_client',
      defaultRedirectUri: undefined,
      enablePropagateAdditionalUserContextData: undefined,
      enableTokenRevocation: undefined,
      explicitAuthFlows: undefined,
      generateSecret: '${Token[TOKEN.680]}',
      idTokenValidity: undefined,
      logoutUrLs: undefined,
      preventUserExistenceErrors: undefined,
      readAttributes: undefined,
      refreshTokenValidity: '${Token[TOKEN.679]}',
      supportedIdentityProviders: undefined,
      tokenValidityUnits: [Object],
      writeAttributes: undefined,
      [Symbol(@aws-cdk/core.DependableTrait)]: [Object]
    },

Expected behavior
I expected to be able to do one of the previous methods for overriding, either customizing directly as shown in the docs, or using the addPropertyOverride method.
This instead removes all settings other than the newly added supported provider. See the screenshots below for the comparison:
Original, before trying to override

New, after overriding

Reproduction steps

Create a new barebones React app
amplify add auth, add a provider such as google
amplify push
amplify override auth
Modify the override.ts file to match the file in the bug and create a new SAML resource
Try to override the supportedIdentityProviders field on either userPoolClient or userPoolClientWeb
Check the client in the Cognito console and notice that Hosted UI no longer works or has any of the default settings

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @tannerabread, was able to find a workaround by using the following.
import { AmplifyAuthCognitoStackTemplate } from "@aws-amplify/cli-extensibility-helper";

export function override(resources: AmplifyAuthCognitoStackTemplate) {
  resources.addCfnResource(
    {
      type: "AWS::Cognito::UserPoolIdentityProvider",
      properties: {
        UserPoolId: { Ref: "UserPool" },
        ProviderName: "Azure",
        ProviderDetails: {
          MetadataURL:
            "<microsoft url>",
        },
        ProviderType: "SAML",
        AttributeMapping: {
          email:
            "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress",
        },
        IdpIdentifiers: ["Azure"],
      },
    },
    "Azure"
  );

  resources.userPoolClient.supportedIdentityProviders = [
    "LoginWithAmazon",
    "Azure",
  ];
  resources.userPoolClient.logoutUrLs = [
    "http://localhost:3000/",
  ];
  resources.userPoolClient.callbackUrLs = [
    "http://localhost:3000/oauth2/idpresponse",
  ];

  resources.userPoolClient.allowedOAuthFlows = ["code"];
  resources.userPoolClient.allowedOAuthScopes = ["openid", "email", "profile"];
  resources.userPoolClient.allowedOAuthFlowsUserPoolClient = true;
}

observed when using ...resources.userPoolClient.supportedIdentityProviders to append to resource it fails with an iterable error and observed the attribute value was undefined

Would be good if addCfnResource returned a reference to the CfnResource created, so it could be used in addDependency calls, like so:
import { AmplifyAuthCognitoStackTemplate, AmplifyProjectInfo } from '@aws-amplify/cli-extensibility-helper';

export function override(resources: AmplifyAuthCognitoStackTemplate, amplifyProjectInfo: AmplifyProjectInfo) {
  const my_sso = resources.addCfnResource({
    type: "AWS::Cognito::UserPoolIdentityProvider",
    properties: {
      AttributeMapping: { [...] },
      ProviderName: "MySSO",
    }
  }, "new-social-provider");

  resources.userPoolClientWeb.supportedIdentityProviders = [ "MySSO" ];
  resources.userPoolClientWeb.addDependency(my_sso);
}

Today this is not possible because resources.addCfnResource returns void... 👎


Swagger Doc

Hi there,
i am able to generate the json using following code in my class library, i was wondering if there is a way to pass this string of json to a webapi or asp.net web application so that i can show the UI generated by  NSwag.AspNetCore.
var document = Task.Run(async () => await generator.GenerateForControllersAsync(controllers))
.GetAwaiter().GetResult();
thanks in advanced!

thanks for your help, however i have another issue and i was wondering if you can help:
when i generate the swagger and show the swaggerUI, the json string return does not include the route attributes, what i have is the following:
[McdHttpRoute("api/Swagger/[action]")]
[McdVersion(1, 0)]
public interface ISwagger : IMcdFeature
{
    [McdHttpGet("api/v1/Swagger")]
    [McdQueue("Mcd.Contracts.Framework.Swagger.GetSwaggerDoc")]
    Task<SwaggerResponse> GetSwaggerDoc(McdRequest request);
}

however GenerateForControllersAsync is only getting the methods instead of the actual routes which in this case would be api/Swagger and api/v1/Swagger
thanks in advanced


Light Theme does not work

In addition to the issues that are already open, the .theme-light CSS class also does not work.

the comfy theme does not support light mode so it gets broke when you do that


[BD-46] docs: update component's theme variables on theme change

Description
Add ability to update component's theme SCSS variables on theme change. This is the first iteration of this feature, during development of design tokens we will improve on this PR to also display actual computed values.
Deploy Preview
https://deploy-preview-1683--paragon-openedx.netlify.app/
Merge Checklist

[x] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[x] Does your change adhere to the documented style conventions?
[x] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[x] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[x] Were your changes tested in the example app?
[x] Is there adequate test coverage for your changes?
[x] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @viktorrusakov!
When this pull request is ready, tag your edX technical lead.

@viktorrusakov 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

:tada: This PR is included in version 20.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tasks entered via browser not being numbered in console

When I add tasks via the web (after issuing todolist web), and return to the command line and enter: todolist list, the tasks that were added via the browser are not numbered. Instead they all have a value of 0. As a result, if you enter todolist d 0, it will just delete the highest task in the list with a 0 next to it.
screenshot

I was attempting to track down the bug, but it appears that the code to handle adding tasks via the web is done in Javascript, and in an S3 bucket.

Thanks for the report.
We will check this bug ASAP.
PRs are welcome!

@gammons
Currently the web interface requires the use of network connection so that it can receive necessary files such as style sheets and script files.  It turns out that bugs in those out-of-repo files are not fixable.
While there is still ways to fix this, I think it is more elegant to include those remote files into the source first, and then fix them accordingly.
Any comments?

@marcelluseasley sorry for the delay here.  I just pushed a fix for this now.  it's available in 0.5.3 of todolist.


#3780: Do not display wrong warning when loading ".js" or ".json"

Issue: https://github.com/storybooks/storybook/issues/3780
Description: https://github.com/storybooks/storybook/issues/3780#issuecomment-402491084

Can you please merge from master?

Done. Let's wait for the builds.


about code

Thank you for sharing your paper, do you have any plans to open source your code?

Thanks for your interest!
I think it will be released soon.


Bounding check for m_offset

Hi
we are using SBE template from ftp://ftp.cmegroup.com/SBEFix/Production/Templates/running using -fsanitize=address. During testing our application with american fuzzy lop I found that we got several crashes.
Crashes were caused by BAD_ACCESS during filed reading, like:
 std::uint64_t transactTime() const     {         return SBE_LITTLE_ENDIAN_ENCODE_64(*((std::uint64_t *)(m_buffer + m_offset + 0)));     }
in case when input data was corrupted m_offset contains wrong value, which cause crash as a result.
My proposal is to add bounding check.

What type of checking and where do you suggest? And what type of corruption is this?

as initial input parameter we receive buffer and buffer size.
so, we can check if offset is less that buffer size.  And in case, when not - throw exception.
It's not a corruption, but we trying to deference pointer, which points far away from original data.
as a result we have undefined behaviour. In my case - application crashes.

There already is a check of offset with respect to buffer length in the codecs reset when it sets position. This catches situations where the acting block length, offset, and buffer pointer are not in agreement with the buffer length.
Do you have bounds checks disabled?
Is there a test missing from https://github.com/real-logic/simple-binary-encoding/blob/master/sbe-tool/src/test/cpp/BoundsCheckTest.cpp for catching this?

SBE_NO_BOUNDS_CHECK macro is not defined.
I have one entity inside another one
it looks like:
`
class Internal
{
private:
char *m_buffer;
std::uint64_t m_bufferLength;
std::uint64_t m_offset;
std::uint64_t m_actingVersion;
inline void reset(char *buffer, const std::uint64_t offset, const std::uint64_t bufferLength, const std::uint64_t actingVersion)
{
    if (SBE_BOUNDS_CHECK_EXPECT(((offset + 3) > bufferLength), false))
    {
        throw std::runtime_error("buffer too short for flyweight [E107]");
    }
    m_buffer = buffer;
    m_bufferLength = bufferLength;
    m_offset = offset;
    m_actingVersion = actingVersion;

}
...};
class Main
{
private:
char *m_buffer;
std::uint64_t m_bufferLength;
std::uint64_t *m_positionPtr;
std::uint64_t m_blockLength;
std::uint64_t m_count;
std::uint64_t m_index;
std::uint64_t m_offset;
std::uint64_t m_actingVersion;
Internal m_internal;
public:
    inline void wrapForDecode(char *buffer, std::uint64_t *pos, const std::uint64_t actingVersion, const std::uint64_t bufferLength)
    {
        m_buffer = buffer;
        m_bufferLength = bufferLength;
        m_internal.wrap(m_buffer, *pos, actingVersion, bufferLength);
        m_blockLength = m_dimensions.blockLength();
        m_count = m_dimensions.numInGroup();
        m_index = -1;
        m_actingVersion = actingVersion;
        m_positionPtr = pos;
        *m_positionPtr = *m_positionPtr + 3;
    }

`
So it looks like I have this check - but it doesn't solve my issue.

Thaks you.
Yes, this check is enabled.
In my case issue was caused by wrong application logic:
I have 2 decoding operations where second depend from first one.
As a result I pass wrong buffer size to second decode.

Thanks! Glad you found it.


Private methods cannot be final

Running on PHP 8 this warning is coming out

Private methods cannot be final as they are never overridden by other classes in /home/bigfoot/Progetti/CreateYourDish/Web/vendor/thunderer/platenum/src/Enum/ConstantsEnumTrait.php on line 12

@bigfoot90 thanks for reporting this issue. I fixed it in #26 and released v0.3.2. Let me know if you have any other questions. :)


Allow for subsampling when inputting large training data

When the total number of instances is large, the computation time of most scikit-learn trainers becomes unacceptably long.
In early iterations of multiple instance learning, it may not be necessary to include all instances in the training data.
Therefore, we will add a function to adjust the amount of subsamples used for training according to the progress of convergence of multiple instance learning.

It might be better to allow the user to set the learning schedule freely by allowing the learned learner to be given as an argument.

Should the subsampling be for bags or instances?
The advantage of the method performed on bags is its simplicity. Because of its simplicity, this method goes well with the solution of giving a trained model as an argument. However, if the number of bags is not large, there is a concern that the accuracy will deteriorate.
The method for instances is more complicated in that you need to change the values of lower_threshold and upper_threshold. For example, if you want to subsample by a factor of 10, you should multiply lower_threshold and upper_threshold by 0.1. If this makes the lower_threshold and upper_threshold too small, the target instance may not be included in any of the subsamples. Therefore, you may need to change the subsample ratio for each bag.

We can get the posterior probability that the number of target instances does not reach the lower limit, and conversely, the posterior probability that the number of target instances exceeds the upper limit. Let's use this.

how about Kernel Approximation?

The following policy is a good one.

Added support for skorch and sklearn.
Add online argument to fit method.
When the online argument is true, allow bags to use tf.data.Dataset or torch's DataLoader instead of np.ndarray's list.


Train and test cost

Hi, sorry to bother u again.
I’d like to know the training and testing times. I’ve noticed that testing takes an especially long time. For example, using two A100 GPUs, testing Mevis required 24 hours.

Hi @yahooo-m, sorry for the late reply.
Typically, we use 8 GPUs for fast inference. When you try to use 2 GPUs, please remember to set SUBSET_NUM=2 in the run_inference_mevis.sh script.
I have tried to reproduce your case as using 2 A10 GPUs. The estimated time is 3~4 hours.
A100 GPUs should be faster than A10 GPUs in theory.

I may suggest first check your transformer version. Different transformer version, especially old version, can slow down the process. Also ensure you really load the model into GPUs.
After that, you may try to break down the inference time to three parts, 1) data loading and saving, 2) inference of MLLM, 3) inference of SAM, to see where is the bottleneck.

Hey, dear author, I've also encountered the above problem in H100. So, I checked the evaluation process following your instructions, and that's what I found:

load image time cost:  13.122689247131348
model time cost:  26.453353881835938
post optimize time cost:<PHONE_NUMBER>9771118
Also, I encountered the flash-attention problem while the mllm was inferring: You are not running the flash-attention implementation, expect numerical differences. The transformer version is the same.

Hi @Lexarymade , thanks for the info.
I also have the warning regarding flash-attn during inference. It does not affect the inference speed on my side.
I will try to find an H100 GPU to test the latency.
Btw, what is the post optimize time cost in your test?

@Lexarymade @JosephPai I also checked my inference time and changed different versions of torch and flash-attn. The inference speed is still slow.  Have u fix it? @Lexarymade

Hi @yahooo-m, I tried to run the evaluation using another server with 8 L40S (48G) GPUs. Even without turning on flash attention, the evaluation can finish within 1 hour. When reducing the number of GPUs to 2, the evaluation is estimated to finish with about 4 hours.
Unfortunately I am not able to reproduce your issue on my side. Maybe you need to check the time usage for each component, including 1) loading video time, 2) MLLM inference time (only one time for each video), 3) SAM inference time (depending on number of frames), 4) saving results (depending on number of frames). If you have successfully put the model on GPU, the inference of MLLM and SAM should be fast.
I highly suspect the data IO part, as some videos may contain a lot of frames.

@Lexarymade , yes you are correct. Ref-DAVIS datasets is annotated by four annotators. The final metric number is the average of them.


Cleaning SegmentAssignmentStrategyTest

Observed that the test is flaky because of the external view delay.
Change the code to look at the idealstate for segment assignment instead of the external view.

Codecov Report

Merging #1661 into master will decrease coverage by 21.97%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #1661       +/-   ##
===========================================
- Coverage   67.79%   45.82%   -21.98%
===========================================
  Files         829      829
  Lines       40256    40256
  Branches     5303     5303
===========================================
- Hits        27293    18447     -8846
- Misses      11126    20141     +9015
+ Partials     1837     1668      -169

Impacted Files
Coverage Δ

...core/io/reader/impl/v2/BitUnpackResultWrapper.java
0% <0%> (-100%)
:arrow_down:

...core/query/planner/SequentialQueryPlannerImpl.java
0% <0%> (-100%)
:arrow_down:

...om/linkedin/pinot/client/SimpleBrokerSelector.java
0% <0%> (-100%)
:arrow_down:

...gregation/function/CountMVAggregationFunction.java
0% <0%> (-100%)
:arrow_down:

.../transport/common/ReplicaSelectionGranularity.java
0% <0%> (-100%)
:arrow_down:

.../reader/impl/v1/VarByteChunkSingleValueReader.java
0% <0%> (-100%)
:arrow_down:

...din/pinot/pql/parsers/pql2/ast/OptionsAstNode.java
0% <0%> (-100%)
:arrow_down:

...aggregation/function/SumMVAggregationFunction.java
0% <0%> (-100%)
:arrow_down:

...harding/ReplicaGroupSegmentAssignmentStrategy.java
0% <0%> (-100%)
:arrow_down:

...ers/pql2/ast/PredicateParenthesisGroupAstNode.java
0% <0%> (-100%)
:arrow_down:

... and 429 more

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 093cea3...acba0c4. Read the comment docs.


Refreshing Preferences (user settings) page loses Account and credit card info

Rancher Versions: 4/5
Steps to Reproduce:

Go to user settings
Refresh page

Results: The Account and credit card sections disappear.  Error in console:
Assertion Failed: You modified "access.identity" twice on <ui@service:access::ember423> in a single render. It was rendered in "component:identity-avatar" and modified in "component:settings/user-info". This was unreliable and slow in Ember 1.x and is no longer supported. See https://github.com/emberjs/ember.js/issues/13948 for more details.
Error

@tfiduccia were you seeing this before or after setting up a payment option?

@westlywright - I didn't setup any payment info.  And I noticed that it did eventually come back, but it just took forever.  Also I got an console error:
ember-cli-live-reload.js:7 GET http://caas.rancher.io:49153/livereload.js net::ERR_CONNECTION_REFUSED
Then after a couple of minutes it shows up with this error in console:
ember.debug.js:18015 Assertion Failed: You modified "hasCattleSystem" twice on <ui@controller:authenticated::ember773> in a single render. It was rendered in "component:page-header" and modified in "component:settings/user-info". This was unreliable and slow in Ember 1.x and is no longer supported. See https://github.com/emberjs/ember.js/issues/13948 for more details.

Version - 5/24
Verified fixed


Sign change when doing math gives invalid number

Bug:
>>> d = tomlkit.parse('x=-3.1415')
>>> d['x'] *= -1
>>> print(tomlkit.dumps(d))

returns:
a=+3.1415

>>> d['x'] *= -1
>>> print(tomlkit.dumps(d))

returns:
a=--3.1415

Subsequent parsing raises tomlkit.exceptions.InvalidNumberError.
Of course there is an easy workaround using type conversion: d['x'] = float(d['x'])*-1.

Hi James, thanks for your time!
I can confirm that this issue doesn't appear in tomlkit 3.