graphcache: (perhaps) svelte: cache in storage's write method doubled if slow query

@urql/svelte: 0.1.3
@urql/exchange-graphcache: 2.3.3 and 2.3.4
Steps to reproduce

go on fullscreen REPL

open browser Dev Tools

click on "Posts"; let it load...

API for albums sleeps for about 4 seconds on purpose

when albums are downloaded see in console the latest batch {}

Expected behavior
It only contains albums objects.
Actual behavior
It contains both albums and todos objects. Todos comes from the first query it already completed!
Additional context
batch: {} come from urql.js file:
write: async batch => {
  console.log("batch:", batch);
  ...
}

It's the same on my localhost, not a Codesandbox fault.
Codesandbox project.

That's intended this is due to commutativity, your query for albums dispatched first and then the one for todo's meaning that this could lead to inconsistent data.
That's why if the last query applies before the one before it will be tentatively applied and reiterated after. This is intended to make offline work consistently

Amazing. Thanks.


Numpy version error reported in Home Assistant Configuration Validation

Since upgrading to the latest version of HA that I get an error with my previously working samsungtv_tizen integration.
Platform error media_player.samsungtv_tizen - Requirements for samsungtv_tizen not found: ['numpy==1.21.1'].
Could this be a new instance of issue #158?

Error logged when I try to restart without commenting out the integration in configuration.yaml
Log Details (ERROR)
Logger: homeassistant.components.homeassistant
Source: components/homeassistant/init.py:163
Integration: Home Assistant Core Integration (documentation, issues)
First occurred: 10:26:57 (1 occurrences)
Last logged: 10:26:57
The system cannot restart because the configuration is not valid: Platform error media_player.samsungtv_tizen - Requirements for samsungtv_tizen not found: ['numpy==1.21.1'].

Another error logged, will hold my hands up I have no idea what this lot actually means...
Logger: homeassistant.util.package
Source: util/package.py:99
First occurred: 10:24:41 (3 occurrences)
Last logged: 10:26:57
Unable to install package numpy==1.21.1: error: subprocess-exited-with-error × Building wheel for numpy (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [241 lines of output] Running from numpy source directory. Processing numpy/random/_bounded_integers.pxd.in Processing numpy/random/_philox.pyx Processing numpy/random/_pcg64.pyx Processing numpy/random/_mt19937.pyx Processing numpy/random/_common.pyx Processing numpy/random/sfc64.pyx Processing numpy/random/generator.pyx Processing numpy/random/mtrand.pyx Processing numpy/random/bounded_integers.pyx.in Processing numpy/random/bit_generator.pyx Cythonizing sources blas_opt_info: blas_mkl_info: customize UnixCCompiler libraries mkl_rt not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE blis_info: libraries blis not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_info: libraries openblas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE accelerate_info: NOT AVAILABLE atlas_3_10_blas_threads_info: Setting PTATLAS=ATLAS libraries tatlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_3_10_blas_info: libraries satlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_blas_threads_info: Setting PTATLAS=ATLAS libraries ptf77blas,ptcblas,atlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_blas_info: libraries f77blas,cblas,atlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/system_info.py:2026: UserWarning: Optimized (vendor) Blas libraries are not found. Falls back to netlib Blas library which has worse performance. A better performance should be easily gained by switching Blas library. if self.calc_info(blas): blas_info: libraries blas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/system_info.py:2026: UserWarning: Blas (http://www.netlib.org/blas/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [blas]) or by setting the BLAS environment variable. if self.calc_info(blas): blas_src_info: NOT AVAILABLE /tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/system_info.py:2026: UserWarning: Blas (http://www.netlib.org/blas/) sources not found. Directories to search for the sources can be specified in the numpy/distutils/site.cfg file (section [blas_src]) or by setting the BLAS_SRC environment variable. if self.calc_info(blas): NOT AVAILABLE non-existing path in 'numpy/distutils': 'site.cfg' lapack_opt_info: lapack_mkl_info: libraries mkl_rt not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_lapack_info: libraries openblas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_clapack_info: libraries openblas,lapack not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE flame_info: libraries flame not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_3_10_threads_info: Setting PTATLAS=ATLAS libraries lapack_atlas not found in /usr/local/lib libraries tatlas,tatlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries tatlas,tatlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_3_10_threads_info'> NOT AVAILABLE atlas_3_10_info: libraries lapack_atlas not found in /usr/local/lib libraries satlas,satlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries satlas,satlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_3_10_info'> NOT AVAILABLE atlas_threads_info: Setting PTATLAS=ATLAS libraries lapack_atlas not found in /usr/local/lib libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries ptf77blas,ptcblas,atlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_threads_info'> NOT AVAILABLE atlas_info: libraries lapack_atlas not found in /usr/local/lib libraries f77blas,cblas,atlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries f77blas,cblas,atlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_info'> NOT AVAILABLE lapack_info: libraries lapack not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/system_info.py:1858: 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. return getattr(self, 'calc_info{}'.format(name))() lapack_src_info: NOT AVAILABLE /tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/system_info.py:1858: 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. return getattr(self, 'calc_info{}'.format(name))() NOT AVAILABLE numpy_linalg_lapack_lite: FOUND: language = c define_macros = [('HAVE_BLAS_ILP64', None), ('BLAS_SYMBOL_SUFFIX', '64')] Warning: attempted relative import with no known parent package /tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py:275: UserWarning: Unknown distribution option: 'define_macros' warnings.warn(msg) running bdist_wheel running build running config_cc unifing config_cc, config, build_clib, build_ext, build commands --compiler options running config_fc unifing config_fc, config, build_clib, build_ext, build commands --fcompiler options running build_src build_src building py_modules sources creating build creating build/src.linux-x86_64-3.9 creating build/src.linux-x86_64-3.9/numpy creating build/src.linux-x86_64-3.9/numpy/distutils building library "npymath" sources Could not locate executable gfortran Could not locate executable f95 Could not locate executable ifort Could not locate executable ifc Could not locate executable lf95 Could not locate executable pgfortran Could not locate executable nvfortran Could not locate executable f90 Could not locate executable f77 Could not locate executable fort Could not locate executable efort Could not locate executable efc Could not locate executable g77 Could not locate executable g95 Could not locate executable pathf95 Could not locate executable nagfor Could not locate executable frt don't know how to compile Fortran code on platform 'posix' Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in  main() File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main json_out['return_val'] = hook(**hook_input['kwargs']) File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 261, in build_wheel return _build_backend().build_wheel(wheel_directory, config_settings, File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 211, in build_wheel return self._build_with_temp_dir(['bdist_wheel'], '.whl', File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 197, in _build_with_temp_dir self.run_setup() File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 248, in run_setup super(BuildMetaLegacyBackend, File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 142, in run_setup exec(compile(code, file, 'exec'), locals()) File "setup.py", line 447, in  setup_package() File "setup.py", line 439, in setup_package setup(**metadata) File "/tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/core.py", line 169, in setup return old_setup(**new_attr) File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/init.py", line 165, in setup return distutils.core.setup(**attrs) File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 148, in setup dist.run_commands() File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands self.run_command(cmd) File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/wheel/bdist_wheel.py", line 299, in run self.run_command('build') File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/command/build.py", line 61, in run old_build.run(self) File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/distutils/command/build.py", line 135, in run self.run_command(cmd_name) File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/tmp/pip-build-env-46o3f2tw/overlay/lib/python3.9/site-packages/setuptools/distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/command/build_src.py", line 144, in run self.build_sources() File "/tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/command/build_src.py", line 155, in build_sources self.build_library_sources(*libname_info) File "/tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/command/build_src.py", line 288, in build_library_sources sources = self.generate_sources(sources, (lib_name, build_info)) File "/tmp/pip-install-u2gd1sn/numpy_51c52882c8134aeab5f3243d94aebdf6/numpy/distutils/command/build_src.py", line 378, in generate_sources source = func(extension, build_dir) File "numpy/core/setup.py", line 666, in get_mathlib_info raise RuntimeError("Broken toolchain: cannot link a simple C program") RuntimeError: Broken toolchain: cannot link a simple C program [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for numpy ERROR: Could not build wheels for numpy, which is required to install pyproject.toml-based projects WARNING: You are using pip version 22.0.3; however, version 22.1.2 is available. You should consider upgrading via the '/usr/local/bin/python3 -m pip install --upgrade pip' command.
Unable to install package numpy==1.21.1: error: subprocess-exited-with-error × Building wheel for numpy (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [241 lines of output] Running from numpy source directory. Processing numpy/random/_bounded_integers.pxd.in Processing numpy/random/_philox.pyx Processing numpy/random/_pcg64.pyx Processing numpy/random/_mt19937.pyx Processing numpy/random/_common.pyx Processing numpy/random/_sfc64.pyx Processing numpy/random/_generator.pyx Processing numpy/random/mtrand.pyx Processing numpy/random/_bounded_integers.pyx.in Processing numpy/random/bit_generator.pyx Cythonizing sources blas_opt_info: blas_mkl_info: customize UnixCCompiler libraries mkl_rt not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE blis_info: libraries blis not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_info: libraries openblas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE accelerate_info: NOT AVAILABLE atlas_3_10_blas_threads_info: Setting PTATLAS=ATLAS libraries tatlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_3_10_blas_info: libraries satlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_blas_threads_info: Setting PTATLAS=ATLAS libraries ptf77blas,ptcblas,atlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_blas_info: libraries f77blas,cblas,atlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/system_info.py:2026: UserWarning: Optimized (vendor) Blas libraries are not found. Falls back to netlib Blas library which has worse performance. A better performance should be easily gained by switching Blas library. if self._calc_info(blas): blas_info: libraries blas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/system_info.py:2026: UserWarning: Blas (http://www.netlib.org/blas/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [blas]) or by setting the BLAS environment variable. if self._calc_info(blas): blas_src_info: NOT AVAILABLE /tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/system_info.py:2026: UserWarning: Blas (http://www.netlib.org/blas/) sources not found. Directories to search for the sources can be specified in the numpy/distutils/site.cfg file (section [blas_src]) or by setting the BLAS_SRC environment variable. if self.calc_info(blas): NOT AVAILABLE non-existing path in 'numpy/distutils': 'site.cfg' lapack_opt_info: lapack_mkl_info: libraries mkl_rt not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_lapack_info: libraries openblas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_clapack_info: libraries openblas,lapack not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE flame_info: libraries flame not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_3_10_threads_info: Setting PTATLAS=ATLAS libraries lapack_atlas not found in /usr/local/lib libraries tatlas,tatlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries tatlas,tatlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_3_10_threads_info'> NOT AVAILABLE atlas_3_10_info: libraries lapack_atlas not found in /usr/local/lib libraries satlas,satlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries satlas,satlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_3_10_info'> NOT AVAILABLE atlas_threads_info: Setting PTATLAS=ATLAS libraries lapack_atlas not found in /usr/local/lib libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries ptf77blas,ptcblas,atlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_threads_info'> NOT AVAILABLE atlas_info: libraries lapack_atlas not found in /usr/local/lib libraries f77blas,cblas,atlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries f77blas,cblas,atlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_info'> NOT AVAILABLE lapack_info: libraries lapack not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/system_info.py:1858: 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. return getattr(self, 'calc_info{}'.format(name))() lapack_src_info: NOT AVAILABLE /tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/system_info.py:1858: 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. return getattr(self, 'calc_info{}'.format(name))() NOT AVAILABLE numpy_linalg_lapack_lite: FOUND: language = c define_macros = [('HAVE_BLAS_ILP64', None), ('BLAS_SYMBOL_SUFFIX', '64')] Warning: attempted relative import with no known parent package /tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py:275: UserWarning: Unknown distribution option: 'define_macros' warnings.warn(msg) running bdist_wheel running build running config_cc unifing config_cc, config, build_clib, build_ext, build commands --compiler options running config_fc unifing config_fc, config, build_clib, build_ext, build commands --fcompiler options running build_src build_src building py_modules sources creating build creating build/src.linux-x86_64-3.9 creating build/src.linux-x86_64-3.9/numpy creating build/src.linux-x86_64-3.9/numpy/distutils building library "npymath" sources Could not locate executable gfortran Could not locate executable f95 Could not locate executable ifort Could not locate executable ifc Could not locate executable lf95 Could not locate executable pgfortran Could not locate executable nvfortran Could not locate executable f90 Could not locate executable f77 Could not locate executable fort Could not locate executable efort Could not locate executable efc Could not locate executable g77 Could not locate executable g95 Could not locate executable pathf95 Could not locate executable nagfor Could not locate executable frt don't know how to compile Fortran code on platform 'posix' Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in  main() File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main json_out['return_val'] = hook(**hook_input['kwargs']) File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 261, in build_wheel return _build_backend().build_wheel(wheel_directory, config_settings, File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 211, in build_wheel return self._build_with_temp_dir(['bdist_wheel'], '.whl', File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 197, in _build_with_temp_dir self.run_setup() File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 248, in run_setup super(_BuildMetaLegacyBackend, File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 142, in run_setup exec(compile(code, file, 'exec'), locals()) File "setup.py", line 447, in  setup_package() File "setup.py", line 439, in setup_package setup(**metadata) File "/tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/core.py", line 169, in setup return old_setup(**new_attr) File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/init.py", line 165, in setup return distutils.core.setup(**attrs) File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 148, in setup dist.run_commands() File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands self.run_command(cmd) File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/wheel/bdist_wheel.py", line 299, in run self.run_command('build') File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/command/build.py", line 61, in run old_build.run(self) File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/build.py", line 135, in run self.run_command(cmd_name) File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/tmp/pip-build-env-i_tsckaq/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/command/build_src.py", line 144, in run self.build_sources() File "/tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/command/build_src.py", line 155, in build_sources self.build_library_sources(*libname_info) File "/tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/command/build_src.py", line 288, in build_library_sources sources = self.generate_sources(sources, (lib_name, build_info)) File "/tmp/pip-install-pccl2yca/numpy_c8743351910e4a8ab9c141bf40616d05/numpy/distutils/command/build_src.py", line 378, in generate_sources source = func(extension, build_dir) File "numpy/core/setup.py", line 666, in get_mathlib_info raise RuntimeError("Broken toolchain: cannot link a simple C program") RuntimeError: Broken toolchain: cannot link a simple C program [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for numpy ERROR: Could not build wheels for numpy, which is required to install pyproject.toml-based projects WARNING: You are using pip version 22.0.3; however, version 22.1.2 is available. You should consider upgrading via the '/usr/local/bin/python3 -m pip install --upgrade pip' command.
Unable to install package numpy==1.21.1: error: subprocess-exited-with-error × Building wheel for numpy (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [241 lines of output] Running from numpy source directory. Processing numpy/random/_bounded_integers.pxd.in Processing numpy/random/_philox.pyx Processing numpy/random/_pcg64.pyx Processing numpy/random/_mt19937.pyx Processing numpy/random/_common.pyx Processing numpy/random/_sfc64.pyx Processing numpy/random/_generator.pyx Processing numpy/random/mtrand.pyx Processing numpy/random/_bounded_integers.pyx.in Processing numpy/random/bit_generator.pyx Cythonizing sources blas_opt_info: blas_mkl_info: customize UnixCCompiler libraries mkl_rt not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE blis_info: libraries blis not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_info: libraries openblas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE accelerate_info: NOT AVAILABLE atlas_3_10_blas_threads_info: Setting PTATLAS=ATLAS libraries tatlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_3_10_blas_info: libraries satlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_blas_threads_info: Setting PTATLAS=ATLAS libraries ptf77blas,ptcblas,atlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_blas_info: libraries f77blas,cblas,atlas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/system_info.py:2026: UserWarning: Optimized (vendor) Blas libraries are not found. Falls back to netlib Blas library which has worse performance. A better performance should be easily gained by switching Blas library. if self._calc_info(blas): blas_info: libraries blas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/system_info.py:2026: UserWarning: Blas (http://www.netlib.org/blas/) libraries not found. Directories to search for the libraries can be specified in the numpy/distutils/site.cfg file (section [blas]) or by setting the BLAS environment variable. if self._calc_info(blas): blas_src_info: NOT AVAILABLE /tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/system_info.py:2026: UserWarning: Blas (http://www.netlib.org/blas/) sources not found. Directories to search for the sources can be specified in the numpy/distutils/site.cfg file (section [blas_src]) or by setting the BLAS_SRC environment variable. if self.calc_info(blas): NOT AVAILABLE non-existing path in 'numpy/distutils': 'site.cfg' lapack_opt_info: lapack_mkl_info: libraries mkl_rt not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_lapack_info: libraries openblas not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE openblas_clapack_info: libraries openblas,lapack not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE flame_info: libraries flame not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE atlas_3_10_threads_info: Setting PTATLAS=ATLAS libraries lapack_atlas not found in /usr/local/lib libraries tatlas,tatlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries tatlas,tatlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_3_10_threads_info'> NOT AVAILABLE atlas_3_10_info: libraries lapack_atlas not found in /usr/local/lib libraries satlas,satlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries satlas,satlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_3_10_info'> NOT AVAILABLE atlas_threads_info: Setting PTATLAS=ATLAS libraries lapack_atlas not found in /usr/local/lib libraries ptf77blas,ptcblas,atlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries ptf77blas,ptcblas,atlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_threads_info'> NOT AVAILABLE atlas_info: libraries lapack_atlas not found in /usr/local/lib libraries f77blas,cblas,atlas not found in /usr/local/lib libraries lapack_atlas not found in /usr/lib libraries f77blas,cblas,atlas not found in /usr/lib <class 'numpy.distutils.system_info.atlas_info'> NOT AVAILABLE lapack_info: libraries lapack not found in ['/usr/local/lib', '/usr/lib'] NOT AVAILABLE /tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/system_info.py:1858: 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. return getattr(self, 'calc_info{}'.format(name))() lapack_src_info: NOT AVAILABLE /tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/system_info.py:1858: 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. return getattr(self, 'calc_info{}'.format(name))() NOT AVAILABLE numpy_linalg_lapack_lite: FOUND: language = c define_macros = [('HAVE_BLAS_ILP64', None), ('BLAS_SYMBOL_SUFFIX', '64')] Warning: attempted relative import with no known parent package /tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py:275: UserWarning: Unknown distribution option: 'define_macros' warnings.warn(msg) running bdist_wheel running build running config_cc unifing config_cc, config, build_clib, build_ext, build commands --compiler options running config_fc unifing config_fc, config, build_clib, build_ext, build commands --fcompiler options running build_src build_src building py_modules sources creating build creating build/src.linux-x86_64-3.9 creating build/src.linux-x86_64-3.9/numpy creating build/src.linux-x86_64-3.9/numpy/distutils building library "npymath" sources Could not locate executable gfortran Could not locate executable f95 Could not locate executable ifort Could not locate executable ifc Could not locate executable lf95 Could not locate executable pgfortran Could not locate executable nvfortran Could not locate executable f90 Could not locate executable f77 Could not locate executable fort Could not locate executable efort Could not locate executable efc Could not locate executable g77 Could not locate executable g95 Could not locate executable pathf95 Could not locate executable nagfor Could not locate executable frt don't know how to compile Fortran code on platform 'posix' Traceback (most recent call last): File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in  main() File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main json_out['return_val'] = hook(**hook_input['kwargs']) File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 261, in build_wheel return _build_backend().build_wheel(wheel_directory, config_settings, File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 211, in build_wheel return self._build_with_temp_dir(['bdist_wheel'], '.whl', File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 197, in _build_with_temp_dir self.run_setup() File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 248, in run_setup super(_BuildMetaLegacyBackend, File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 142, in run_setup exec(compile(code, file, 'exec'), locals()) File "setup.py", line 447, in  setup_package() File "setup.py", line 439, in setup_package setup(**metadata) File "/tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/core.py", line 169, in setup return old_setup(**new_attr) File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/init.py", line 165, in setup return distutils.core.setup(**attrs) File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 148, in setup dist.run_commands() File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands self.run_command(cmd) File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/wheel/bdist_wheel.py", line 299, in run self.run_command('build') File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/command/build.py", line 61, in run old_build.run(self) File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/command/build.py", line 135, in run self.run_command(cmd_name) File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command self.distribution.run_command(command) File "/tmp/pip-build-env-oevqhpq2/overlay/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command cmd_obj.run() File "/tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/command/build_src.py", line 144, in run self.build_sources() File "/tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/command/build_src.py", line 155, in build_sources self.build_library_sources(*libname_info) File "/tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/command/build_src.py", line 288, in build_library_sources sources = self.generate_sources(sources, (lib_name, build_info)) File "/tmp/pip-install-sr5o5ca1/numpy_22b2844e6c1141c88ea7c1edc169542c/numpy/distutils/command/build_src.py", line 378, in generate_sources source = func(extension, build_dir) File "numpy/core/setup.py", line 666, in get_mathlib_info raise RuntimeError("Broken toolchain: cannot link a simple C program") RuntimeError: Broken toolchain: cannot link a simple C program [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for numpy ERROR: Could not build wheels for numpy, which is required to install pyproject.toml-based projects WARNING: You are using pip version 22.0.3; however, version 22.1.2 is available. You should consider upgrading via the '/usr/local/bin/python3 -m pip install --upgrade pip' command.

Same issue with numpy here, in the full error log I found:
2022-07-05 22:47:19 ERROR (SyncWorker_2) [homeassistant.util.package] Unable to install package numpy==1.21.1: ERROR: Cannot install numpy==1.21.1 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
2022-07-05 22:47:19 ERROR (MainThread) [homeassistant.config] Platform error: media_player - Requirements for samsungtv_tizen not found: ['numpy==1.21.1'].
Not sure which other integration or if HA-core is using the other numpy

same. will rollback a few versions till this one is addressed.
2022-07-11 09:37:47 ERROR (SyncWorker_8) [homeassistant.util.package] Unable to install package numpy==1.21.1: ERROR: Cannot install numpy==1.21.1 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
2022-07-11 09:37:57 ERROR (SyncWorker_8) [homeassistant.util.package] Unable to install package numpy==1.21.1: ERROR: Cannot install numpy==1.21.1 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
2022-07-11 09:38:07 ERROR (SyncWorker_8) [homeassistant.util.package] Unable to install package numpy==1.21.1: ERROR: Cannot install numpy==1.21.1 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
2022-07-11 09:38:07 ERROR (MainThread) [homeassistant.config] Platform error: media_player - Requirements for samsungtv_tizen not found: ['numpy==1.21.1'].

I just released a new version with an updated numpy version


Styles.Load member is not available

Hello team!
I've been trying to do some simple stuff, using provided samples as a foundation.
There's an issue with styling, basically I can't get it to work. I am trying to customize a ListBox to display an image as well as a text block inside one item.
For example, if I'll use the following inside the Styles.xaml, the view of the listbox with classes [ "folder" ] won't change it's appearance:

<ListBox>
	<ListBox.Styles>
		<Style Selector="ListBox.folder">
			<Setter Property="ItemTemplate">
				<ItemTemplate>
					<Border CornerRadius="3" Padding="5" Background="Azure">
						<StackPanel Orientation="Horizontal">
							<Image Source="{SvgImage Assets/Icons/folder.svg}"/>
							<TextBlock Text="{Binding}"/>
						</StackPanel>
					</Border>
				</ItemTemplate>
			</Setter>
		</Style>
	</ListBox.Styles>
</ListBox>

I've noticed that in this sample Styles.Load method was used on the line 34.
However, if I'll try to use the same method, I'll get FS0039 error which tells me that this member is not available:

Now, the samples are using project references instead of the nuget packages, so I am not sure if this is related to some kind of a breaking changes caused by the recent updates or something else.
My packages are the following:

Could you please take a look and let me know what am I doing wrong here? Any tips/hints/advices are much appreciated.
P.S. Thanks for your tremendous work on FuncUI!

Should be picked up from https://github.com/fsprojects/Avalonia.FuncUI/blob/1cdf7a6a241279c98e7b0b2ca1cea6e98b1cb170/src/Avalonia.FuncUI/Helpers.fs#L17 I think? (though there does appear to be a duplicate copy of the function in the control catalog app as well)

Hello @Numpsy
You're right, I've missed to open Avalonia.FuncUI module. For some reason VS did not propose it.
Appreciate your help!


url_for Attempting to generate a URL from non-sanitized Rails 5

Hi I'm upgrading to rails 5 and notices that I get this error when using the url_for
the error
Attempting to generate a URL from non-sanitized

https://github.com/plataformatec/devise/wiki/How-To:-Send-emails-from-subdomains
# app/helpers/subdomain_helper.rb

module SubdomainHelper
  def with_subdomain(subdomain)
    subdomain = (subdomain || "")
    subdomain += "." unless subdomain.empty?
    host = Rails.application.config.action_mailer.default_url_options[:host]
    [subdomain, host].join
  end

  def url_for(options = nil)
    if options.kind_of?(Hash) && options.has_key?(:subdomain)
      options[:host] = with_subdomain(options.delete(:subdomain))
    end
    super
  end
end

Hello @Frank004, thanks for your report.
It looks like the example on the wiki must be updated to work with rails 5.
The wiki is maintained by the community, so if you discover another solution please contribute with your findings back.
I think the problem has to do with the strong parameters. I found some questions on Stack Overflow that may be helpful:

https://stackoverflow.com/questions/38308130/generate-a-url-from-non-sanitized-request-parameters
https://stackoverflow.com/questions/42801654/rails-5-attempting-to-generate-a-url-from-non-sanitized-request-parameters
https://stackoverflow.com/questions/40479006/rails-5-attempting-to-generate-a-url-from-non-sanitized-request-parameters-ho

If you need more help, please ask a question on StackOverflow. There we have a wider community that can to help you. We reserve the issues tracker for issues only.
Thank you again!


Automated cherry pick of #7264: fix: 避免status_code>=400并且resp为空时err为nil

Cherry pick of #7264 on release/3.3.
#7264: fix: 避免status_code>=400并且resp为空时err为nil

Codecov Report

Merging #7265 into release/3.3 will decrease coverage by 2.34%.
The diff coverage is 0.08%.

@@              Coverage Diff               @@
##           release/3.3   #7265      +/-   ##
==============================================
- Coverage         6.78%   4.44%   -2.35%
==============================================
  Files              676     280     -396
  Lines           118955   65223   -53732
==============================================
- Hits              8076    2898    -5178
+ Misses          110267   62129   -48138
+ Partials           612     196     -416

Flag
Coverage Δ

#aFlag
4.44% <0.08%> (-2.35%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/compute/models/cachedimages.go
2.07% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/capabilities.go
0.00% <0.00%> (ø)

pkg/compute/models/cloudaccounts.go
5.82% <0.00%> (-0.25%)
:arrow_down:

pkg/compute/models/cloudproviderregions.go
0.26% <0.00%> (ø)

pkg/compute/models/cloudproviders.go
0.88% <0.00%> (+0.02%)
:arrow_up:

pkg/compute/models/cloudregions.go
1.58% <0.00%> (-0.05%)
:arrow_down:

pkg/compute/models/cloudsync.go
0.00% <0.00%> (ø)

pkg/compute/models/dbinstance_backups.go
2.91% <0.00%> (-0.04%)
:arrow_down:

pkg/compute/models/dbinstance_skus.go
2.79% <0.00%> (+0.18%)
:arrow_up:

pkg/compute/models/dbinstancenetworks.go
0.80% <0.00%> (-0.09%)
:arrow_down:

... and 418 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 8a6ee6c...6ac8c2b. Read the comment docs.


[REQ] Push beta4 to F-Droid

Can beta4 code be pushed to F-Droid or it is responsability of the F-Droid team to pull the changes? F-Droid build status says highest metadata version is beta3.

yeap (I'm waiting https://github.com/jonjomckay/fritter/issues/229 :P)

beta5 installed from F-Droid. Thanks!


Main 2

opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly

Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Github Issue # or road-map entry, if available:

Description of changes:

Why these changes are required?

What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)

Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)

TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)

Is it backport from main branch? (If yes, please add backport PR # and commits #)

By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1212 (2a60701) into main (2371ae4) will decrease coverage by 46.69%.
The diff coverage is 26.66%.

@@              Coverage Diff              @@
##               main    #1212       +/-   ##
=============================================
- Coverage     64.56%   17.87%   -46.70%
+ Complexity     3177      742     -2435
=============================================
  Files           245      245
  Lines         17147    17192       +45
  Branches       3038     3051       +13
=============================================
- Hits          11071     3073     -7998
- Misses         4529    13613     +9084
+ Partials       1547      506     -1041

Impacted Files
Coverage Δ

...earch/security/privileges/PrivilegesEvaluator.java
7.87% <0.00%> (-58.09%)
:arrow_down:

...curity/privileges/PrivilegesEvaluatorResponse.java
0.00% <0.00%> (-80.00%)
:arrow_down:

...g/opensearch/security/support/ConfigConstants.java
83.33% <ø> (-11.12%)
:arrow_down:

...org/opensearch/security/filter/SecurityFilter.java
27.64% <28.57%> (-47.95%)
:arrow_down:

...rch/security/transport/SecurityRequestHandler.java
48.22% <28.57%> (-26.97%)
:arrow_down:

...ava/org/opensearch/security/auth/UserInjector.java
14.66% <37.50%> (-75.19%)
:arrow_down:

...search/security/transport/SecurityInterceptor.java
54.23% <40.00%> (-23.75%)
:arrow_down:

...va/org/opensearch/security/auth/RolesInjector.java
21.42% <50.00%> (-63.19%)
:arrow_down:

.../org/opensearch/security/auth/BackendRegistry.java
16.66% <100.00%> (-42.71%)
:arrow_down:

...org/opensearch/security/ssl/util/CertFromFile.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 199 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 2371ae4...2a60701. Read the comment docs.


Dealing with large documents

Hi!
First of all thanks, I have only just started looking at adminMongo but so far it looks great.
I have a database which has some collections that contain large documents (around 10Mb each) and this means that when you click on the collection it basically freezes.
I was wondering if there was any way to get around this?
I noticed that someone already asked about async loading of large documents (issue #18) but your reply was that this was out of scope, but it really would be a great feature.
Any ideas for workarounds in the meantime? E.g. set pagination to 1 for certain collections?
Best regards,
Eric

Anyone care to assist with this issue or give some pointers? I don't even know where to start.

In the meantime I have come to the conclusion that Mongo is not really made for very large documents, so I guess you could argue it's not really a limitation of adminMongo.

I've been reading about GridFS but don't really know how it would fit into the application.
Other apps do it so I might need to have a look how it is done.

Thought I'd add to this since it's relevant.
I've got a database of 36812 documents (Collection is 243 MB). Whenever I try to view the Collection it just freezes and crashes the tab. The limit is set to 5 documents per page.

I'm having the same issue, 35 documents - 454MB and it freezes. I tried adding index to the fields but no luck

@aconital  I figured it's better to use something like Robomongo (windows application) to access the DB for larger operations.

@aconital That means you have ran out of 32MB that is allocated by Mongo. You should add an index to the sort field.
https://docs.mongodb.com/manual/reference/limits/#Sort-Operations


Upload custom Contributor Agreement

DAO members should be able to upload a custom Contributor Agreement and then it should be enforced when new contributors tribute deliverables in exchange for sweat tokens.
KaliDAO smart contract allows DAO docs to be update. We need to design a way to distinguish docs of different types on-chain and then implement click-wrap for each at the appropriate places in the UI.
For example if a new Operating Agreement is uploaded, then all token holders need to acknowledge that they read it before they can interact with the DAO.
Similarly if DAO's Terms of Service change after a majority vote, that again should be a DAO wide click-wrap acceptance for further interactions with the DAO.
For Contributor Agreement, there should be a click-wrap dialog somewhere in the task submission flow.


fix(login): don't load state until the user is authenticated

What this PR does 📖

This PR doesn't load state.json until the user logs in.  Unfortunately, the Router created for Uplink depends on state, meaning the router couldn't be used for the auth pages. I got around this by using a prop to conditionally render the correct page: authentication, create new user, or an entry point to the rest of the app.
authentication needs warp_runner . This is started by the bootstrap Element. At this point the app can't receive events from warp but it can command Tesseract and MultiPass through a channel.
after logging in, an app_bootstrap Element is created, which loads the state, makes it shared, and loads the app element
the app element listens for warp events, creates a router, and defaults to the ChatLayout
the route strings were moved into a struct for better readability .

Additional features

Translations for the UnlockLayout and CreateAccountLayout have been added
fix the PopoutPlayer
the login flow has been changed to login automatically when the correct pin is entered. also, when creating an account, the pin is entered on the unlock page and carries over to the create account page.

Which issue(s) this PR fixes 🔨

Resolve #97 #93 #98 #99 #117

Special notes for reviewers 🗒
Additional comments 🎤

I noticed this error while testing the new commits. When User is logging and it is a fresh account each time they type a key it will say "need to create an account" if its an account thats already made it will say "wrong password" each time they type a key. I messaged Stu to see if he wanted to fix in this PR or a new ticket, he is going to add into this PR 👍
https://user-images.githubusercontent.com/93608357/211882616-1f10640f-c1c5-4ad8-b832-2a22d62dc337.mov


Store original window state to allow cleanup when extension disabled

When no atom could be found, this should indicate that the titlebar is not hidden and thus this information should be stored for future reference.
Fixes #63

I don't think guessing this is going to work, especially since all gnome apps don't have title bar, as well as many other very used apps, like chromium. I don't think this is the right way to go here. Can you explain a bit more what is going on ?

See #63 for a use case. The original state is not kept here.
Checking decoration would be indeed a good thing. But even without it works fine, as setting the atom simply does not take any effect then. And as the atom is generally set for undecorated windows as well in "setHideTitlebar", I did not bother to introduce this distinction here.
But you get the point that currently the original state is not always recorded and therefore not always correctly restored? As I said it's not a big deal, Pixel Saver should not be disabled very often. And you can simply close the application to get the title back. But to be a good citizen, proper cleanup should be worth some effort.

OMG! I've changed the wrong method! The fix must go into "getOriginalState()"

I've pushed an extended version that explicitly deals with the different window states instead of just using a boolean.
I can reproduce the behavior described in #63 with both 3.14 and 3.18 and this PR fixes it. Please let me know if you need any further information. Thanks.


fix typo in matrix selection example

The current example does not work. Need to use dataView.matrix.columns.levels when creating the selection id for columns.

@toresenneseth : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @toresenneseth,
I'm verifying your suggestion with the development team.
Thanks,
Kesem

@maggiesMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

**[@# Create a list of dictionaries with new data
avocados_list = [HTPPS://
{1936: 1960, 1963: 1978, 1982: 1984},
{1988: 1993, 1997: 1998, 1991: 2008},
]
Convert list into DataFrame
avocados_2021 = 1988
Print the new DataFrame
____](HTPPS:// Basic Policy X.509)**EB6296000


chore(*) refactor jenkinsfile

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


Replace deprecated methods

Those two will cause warnings when in debug mode, starting in Kirby 3.3.0.
Best to switch to the v3 equivalents.

Thank you for your pr, @distantnative.


Allow custom buf.yaml file for linting

Currently, the plugin performs linting like:
 runBufCommand(
                        project,
                        owner,
                        workingDirectory,
                        listOf("lint", "--error-format=json"),
                        expectedExitCodes = setOf(0, BUF_EXIT_CODE_FILE_ANNOTATION),
                    )

using default Buf settings.
In case the project follows a different configuration - e.g. uses buf.yaml with except block:
version: v1
deps:
- buf.build/googleapis/googleapis
breaking:
  ignore_unstable_packages: true
  use:
  - FILE
lint:
  allow_comment_ignores: true
  use:
  - COMMENTS
  - DEFAULT
  - PACKAGE_NO_IMPORT_CYCLE
  - UNARY_RPC
  except:
  - RPC_RESPONSE_STANDARD_NAME
  - RPC_REQUEST_RESPONSE_UNIQUE

The plugin reports a warning with a suggestion to apply a fix, which contradicts the project's configuration.
A solution would be to provide a setting with path to buf.yaml to be used for lining.
E.g.
configFileContent = readFrom(project.bufSettings.state.bufConfigPath)
 runBufCommand(
                        project,
                        owner,
                        workingDirectory,
                        listOf("lint", "--error-format=json", "--config="+configFileContent),
                        expectedExitCodes = setOf(0, BUF_EXIT_CODE_FILE_ANNOTATION),
                    )

Can you provide a sample project or describe the layout of your project? Where is the buf.yaml located relative to the project and the .proto files?
You may also be interested in https://buf.build/docs/migration-guides/migrate-v2-config-files. In v2 configs, you can easily add a buf.yaml at the root of the project and point to modules which are stored in subdirectories.

Thank you for your response highly appreciated!
And for the link, in particular, I missed the migration.
Our layout is a bit sophisticated, so I try first to describe it and provide a project if needed.
We have a project with proto files, which are there for self-service for all teams (to create/update/retire services and their protos).
We also provide a bespoke CLI for running various linting rules which are made as a combination of internal requirements and most of Buf rules - but not all (a few got disabled in favor of custom ones).
Updating the CLI and its rules happens in the background for users without any actions required from their side.
Some portion (or even the majority) of users have the buf-plugin (with default Buf rules) installed, and it provides false-positive warnings for disabled rules in CLI, which we cannot control.
So we have only an option to force users to delete the plugin (maybe by writing our own one).
Alternatively, we could release the actual effective buf.yaml configuration along with the CLI update and use it in the plugin - provided there will be such an option in the plugin itself.
Similar to what IntelliJ provides for JSON schemas - it can pick them from the URL directly or load them from the filesystem, relative or absolute to the project.
Hope it explains a bit about the problem.

We have a project with proto files, which are there for self-service for all teams (to create/update/retire services and their protos).

Would it be possible to include a buf.yaml file with the buf lint config rules you wish to enforce in this proto project, or is the desire to keep it entirely behind the bespoke CLI?

Alternatively, we could release the actual effective buf.yaml configuration along with the CLI update and use it in the plugin - provided there will be such an option in the plugin itself.

There are two options I could think of:

Disabling 'Continuous background linting' under Tools/Buf. Since linting is enforced elsewhere with a custom CLI, this will disable running it in the Buf plugin. You could investigate the File Watcher plugin or other Tools->External Tools to run your bespoke CLI.
There is already an option in the plugin to specify custom arguments for buf breaking - we could support this for buf lint too. This way you could pass a --config <path/to/buf.yaml> argument with the custom lint config.

We could include with CLI updates the buf.yaml in the project with protos, although it's not as convenient as pointing to a static URL with the latest version of the configuration.
As far, as I've gathered, IntelliJ also doesn't provide an option to check in the default plugin configuration (e.g. disable continuous linting or change custom arguments for buf breaking for all users) in the project files, only a list of them?


Can we add version of react-scripts when invoking --version from CLI?

Unless I'm misunderstanding your question, this is already supported.
create-react-app myapp<EMAIL_ADDRESS>

@pdillon I think you was misunderstanding his questoin.. @ericnakagawa seems asked about create-react-app --version
$ create-react-app --version
$ create-react-app version: 0.5.0

@ericnakagawa react-scripts doesn't come with create-react-app. When you create-react-app my-app, it is then download the latest version of react-scripts from npm. Therefore, there is nothing such as a version of react-scripts in create-react-app --version.
Moreover, because react-scripts doesn't come with create-react-app, it is possible to use create-react-app with a forked version of react-scripts. That is @pdillon comment.

I think there is some misunderstanding here, as noted by the commenters. There is no "inherent" react-scripts version in create-react-app. By default it always installs the latest. So I'm not sure how this could be actionable for us.


Update "discord.py" to "discord.py==0.16.12" in requirements.txt

Change discord.py to discord.py==0.16.12 been getting alot of problem, for some reason it installed right when i had it as just discord.py weird some people may have a problem like this or maybe discord has now started using rewrite when one installs discord.py idk but chnage it to discord.py==0.16.12 in case

Temporary fix for the YoutubeDL error on token


Formatting "time" for stats

We're currently showing the number of seconds as they are (e.g. "71.2 sec") in the progress var. We need to format it properly ("1m:11.2s", or "00:01:11s", or something). We might need context-sensitive formattings.
Blocks #12.
Requirements

[x] Create custom formatting functions for this use case and others
[x] Display user-friendly time in the progress bar

Implemented in 229ccfe757bf2b7606d876aeb0e9ba6f98f8b330.


Fix ansible job error reason

closes OSPRH-11068

/test all

/test all

I think what @owalsh suggested makes sense. failed >0 (failed pods) does not mean failed job and we don't need to tell the user that the job has failed. I worked on a change like that yesterday but forgot to push it https://github.com/openstack-k8s-operators/openstack-operator/compare/main...rabi:openstack-operator:fix_nil?expand=1

/cherry-pick 18-fr1

/cherry-pick 18.0-fr1


allow to specify sandbox environment for testing in the constructor

This could be overriden by passing an instance of a HttpClient with base_url already set to sandbox, but this approach seems more straightforward and easier to use

looks good, thanks


feat: add rule disallowing loops

Disallows loops according to https://github.com/camunda/zeebe/pull/13025.
The algorithm works as follows:

Find all elements that can be part of a loop
For each of them, try and find a loop
Report an error once the first loop has been found

Loop on a single process level

Nested loop on a single process level

Loop on multiple process levels

Loop with call activity

Ignored loop

Closes https://github.com/camunda/bpmnlint-plugin-camunda-compat/issues/100

Oh no, I wasn't done with this, hence I hadn't assigned anyone. 🙈 Anyway, the handling of call activities was missing. Here's a follow-up pull request: https://github.com/camunda/bpmnlint-plugin-camunda-compat/pull/130

What complexity does this algorithm have (with respect to the number of flow elements per process)? And hence, what is the run-time cost for a larger diagram.

Let me figure this out.

https://github.com/camunda/bpmnlint-plugin-camunda-compat/pull/102#issuecomment-1701015301

You can create a PR as a draft if you want to signal that it is not ready (yet).

You can create a PR as a draft if you want to signal that it is not ready (yet).

I know, you reviewed within the shot timespan between marking it as ready and pushing the final commit. 😅

Great results. Good thing is that rule execution is async, that means that overall interaction is not blocking.


Removed the UDP protocol for the required ports.

As per internal confirmation and https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2#bkmk_identity only TCP is required. UDP is not relevant for the agent communication.

@tvuylsteke,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

This changes have already been made. This PR can be closed.


try to reconnect to the primary pis from time to time from pid

It would be nice if the pid would try to reconnect to his primary pis from time to time to get the infrastructure layout back as it was at start

Reconnect is done when SMS status was send and 5 minutes till last check to reach primary pis was done.

closed


Bubbling is ignored when one of handlers in the chain fails

Monolog version 1, 2, 3
The default behavior is to ignore bubbling if something goes wrong inside a handler.
Look at this part of the code.
https://github.com/Seldaek/monolog/blob/60ad5183b5e5d6c9d4047e9f3072d36071dcc161/src/Monolog/Logger.php#L325-L334
Imo, errors in some handlers must not affect other handlers if bubble options is set.

It is the default mode that errors abort operation so you notice any logging issue hopefully. If you don't care or have unreliable handlers you can wrap them in WhatFailureGroupHandler instance(s) to suppress the errors and keep going.

@Seldaek Thank you for reply. All http/tcp-based handlers are unreliable. Socket stream does the same.
https://github.com/Seldaek/monolog/blob/60ad5183b5e5d6c9d4047e9f3072d36071dcc161/src/Monolog/Handler/SocketHandler.php#L376-L403
Anyway, maybe it's a good idea to explain it in docs? Because, this topic is confusing and users expect imho the behaviour I described.
P.S. For my purposes I implemented also error handling of handle function fails. I also log that data to get info when tcp-based handler fails. You may check this approach for the inspiration. https://github.com/BETER-CO/yii2-beter-logging/blob/master/src/Handler/ProcessHandleResultTrait.php

So, I added 2 features: stats for handling time distribution and the amount of failures/successful calls. If you are ok, I'm ready to bring those handlers to monolog as HandlerWithStats and some extended features to track handle exceptions and process them from the application.

Yes, socket handlers are unreliable, and I wouldn't recommend using them for that reason. Using UDP or syslog then some background process pushing logs to another system via TCP in a more reliable manner and out of band from the application process makes a lot more sense IMO. But for small scale stuff the socket handlers are ok and convenient as things work most of the time.
I am not really interested in adding more handlers to maintain here so if you like to publish yours please do so as a standalone package - you can then list it here https://github.com/Seldaek/monolog/wiki/Third-Party-Packages


Extra reference docs support

Status
Ready
Related Issues
related: https://github.com/demisto/etc/issues/23431
Description
Support for extra content docs which are not part of the content repo such as native integrations and external integrations. Add some docs:

syslog
remote access
saml 2.0 - okta

Screenshots
Paste here any images that will help the reviewer

@kirbles19 please review:

https://github.com/demisto/content-docs/edit/extra-ref-docs/content-repo/extra-docs/integrations/remote-access.md?pr=%2Fdemisto%2Fcontent-docs%2Fpull%2F113
https://github.com/demisto/content-docs/edit/extra-ref-docs/content-repo/extra-docs/integrations/syslog.md?pr=%2Fdemisto%2Fcontent-docs%2Fpull%2F113
https://github.com/demisto/content-docs/edit/extra-ref-docs/content-repo/extra-docs/integrations/saml-okta.md?pr=%2Fdemisto%2Fcontent-docs%2Fpull%2F113

These have been migrated from zendesk

These two look like they could use some work

https://github.com/demisto/content-docs/edit/extra-ref-docs/content-repo/extra-docs/integrations/remote-access.md?pr=%2Fdemisto%2Fcontent-docs%2Fpull%2F113
https://github.com/demisto/content-docs/edit/extra-ref-docs/content-repo/extra-docs/integrations/syslog.md?pr=%2Fdemisto%2Fcontent-docs%2Fpull%2F113

This one is in tech docs

https://github.com/demisto/content-docs/edit/extra-ref-docs/content-repo/extra-docs/integrations/saml-okta.md?pr=%2Fdemisto%2Fcontent-docs%2Fpull%2F113


default capital Esh question

Hi Amit & Denis!
In the new website, you say that we should use a different shape for the default capital Esh than Denis settled on with me earlier.
I was wondering if this is a soft recommendation ( maybe because the localization offered is itself at least very clear )  or if it has become very clear recently that this is the way to go. As far as I understand it, this is what happened with capital Eng form changing and the old form being turned into a localized version. If that's the case, did that clarity come from population size like it did with Eng?

In short, the capital-Σ form is more historical as it was used in orthographies that now use the digraph sh. More recent reference documents of other orthographies using the letter use the large-ʃ form. The rationale for large-ʃ form is that is is used in reference documents of languages using the letter, whereas the capital-Σ form was used in reference documents of languages that do not use the letter anymore. Additionaly the large-ʃ form is recognizable.
The Σ capital form is used in:

the 1927 Africa Alphabet
the Ga orthography from the 1930s until 1975 when ʃ was replaced by the digraph sh
Mali’s Alphabets et règles d’orthographes des langues nationales  [Mali national languages alphabets and orthography] used the letter for Bambara from 1982 until it was replaced by the digraph sh in the 1991 revision.

The large-ʃ capital form is used in:

the 1978 edition of the African Reference Alphabet; note the alphabet was initially lowercase-only and capitals were added before publication; 1982 revision by Mann and Dalby has only lowercase letters.
the Alphabet scientifique des langues du Gabon [Scientific Alphabet of Gabon languages] published in 1989 has both uppercase and lowercase.
in the 2015 edition of the Alphabet national guinéen [Guinean National Alphabet] for the Bassari [bsc] orthography; the 1989 edition does not seem to have used capitals.

For the Gabonese languages, the ASG is mostly intended for and used in scholarly works. Linguistic journal articles and some dictionaries do use it. Out of the languages described in the document the letter may be used in Bekwel [bkw], Fang Ntumu and Fang Nzaman [fan], Lembaama [mbm], Omenye Mpoŋwɛ and Omenye Ŋkomi [mye], Ʃake [sak], Ʃiwa [N/A], Yinzɛbi [nzb]. In practice, alphabets of some of those language use by some authors do not seem to use ʃ, for example the orthography used in the Yinzɛbi Bible translation does not use ʃ. There is also the alphabet of the Orthographe des langues du Gabon [Gabon language orthography]  from 1999 which uses digraphs and underlined letters instead of Latin extended letters.
For Guinean languages, it’s difficult to assess to what extent the national alphabet or in particular this letter is used. A few documents I was able to verify do use the alphabet. But it doesn’t look that it has been used to the same extent as national alphabet in other countries.

Thanks @moyogo for the detailed explanation. Based on this info, it seems like we don't need to change the guidance since the alternate form would only be available if someone were to use and Esh in Ga text instead of an sh digraph. Does that sounds correct to you?

Thanks what it sounds like to me too. Thanks Denis!
On Wed, Feb 8, 2023 at 10:02 AM Neil S Patel @.***>
wrote:

Thanks @moyogo https://github.com/moyogo for the detailed explanation.
Based on this info, it seems like we don't need to change the guidance
since the alternate form would only be available if someone were to use and
Esh in Ga text instead of an sh digraph. Does that sounds correct to you?
—
Reply to this email directly, view it on GitHub
https://github.com/JamraPatel/font-lang-support-afr/issues/13#issuecomment-1422733953,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQUQXI6FVCG6S4GTDBJPMLWWOYPJANCNFSM6AAAAAAUUZUS6E
.
You are receiving this because you authored the thread.Message ID:
@.***>


[FLINK-19839][e2e] Properly forward test exit code to CI system

Due to a recent change, the exit code of e2e tests was not forwarded properly anymore.
This CI build demonstrates that failures are forwarded properly: https://dev.azure.com/rmetzger/Flink/_build/results?buildId=8556&view=results

Thanks for the quick review. Merging!


ejbca-pki/revoke endpoint ignores private key

The revoke endpoint for EJBCA will merrily revoke any cert for which you have the Serial Number. Vault 'PKI', on the other hand, requires the private key to be presented to revoke.
We consider this desired functionality: without accepting and validating the private key it would allow anyone with access to the endpoint and knowledge of a cert's serial number to revoke that cert.  This is a problem as we expose multiple roles to generate certs and expect that we can only revoke for certificates in our possession.

Hi @verdantvestibule!
Thank you for submitting this issue and bringing this vulnerability to our attention. This will be addressed in Version 1.2 in this PR.


Change default header representation to bytes.

Resolves #154.
After this, we're very close to being ready to go for 3.0.

Yeah, handily when we had to solve this the first time (to allow bytes through) almost all the problems went away.


Rewrite of emoji-clock plugin based on emoji plugin

Hi @afh, thank you for your contribution. We better not add a dependency even if it means repeating the emojis. Otherwise, people who use this plugin will find that it doesn't work because they don't have the emoji plugin enabled, and we don't have an easy way to track or manage plugin dependencies yet.

I understand and had similar thoughts. Yet from a developer's perspective I find the revised implementation so much cleaner.
Is tracking or managing plugin dependencies on the oh-my-zsh roadmap?

I understand and had similar thoughts. Yet from a developer's perspective I find the revised implementation so much cleaner.

I agree that one simple logic is better than a case switch. Back when I first encountered this plugin I thought of having an associative array of clocks but never got to implement it. Maybe you can go this way? I like that you're using prompt sequences instead of date which is an external command.
So :+1: to this PR but lose the dependency on emoji.

Is tracking or managing plugin dependencies on the oh-my-zsh roadmap?

There was some talk about it, mostly around having a better loading system, and I think we let the discussion dry out because there were already solutions out there. There's antigen which is a great tool and FWIW it could be used by oh-my-zsh like node uses npm, ruby uses bundler, etc. But no, there's nothing on the roadmap both in terms of discussion and of implementation. Maybe you can get the ball rolling? :wink:

I amended this pull request, so it uses a associative array for the emojis, copied from the emoji plugin
instead depending on the latter.
I'll have a look at antigen, thanks. Where would be the right place to get the :soccer: rolling?

Actually, I think the current code is cleaner and clearer.


DBZ-4603 Remove parameters from config example and link to PG doc

DBZ-4603
Removes parameters from the configuration example that were set to invalid values ( max_replication_slots and max_wal_senders ),  and adds a cross reference to the PG documentation.
Local Antora build verifies that the content renders correctly for upstream. The content is conditionalized for community use only, so no changes render in the downstream docs.

Slightly reworded (as these options are not so much about performance) and squashed.


refactor: use vcpkg features to control dependencies

Sometimes we want to compile without the tests, or without the tests for
the examples. With this change we can express that by just turning vcpkg
features on or off. Because -DBUILD_TESTING=ON is a well-known flag,
we use it to enable the testing features too.

This is ready for review now.  To see this in action, look at #290.


Issue with HorizontalPodAutoscaler apiVersion

Helm is choking on deploying the chart due to autoscaling/v2beta1 being removed as of  Kubernetes v1.25:
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#horizontalpodautoscaler-v125
The apiVersion autoscaling/v2 has been available since Kubernetes v1.23.
I'll submit a pull request with an updated template.

@jliedy thanks for reporting. Taking a look now.

Hey, I've submitted pull request #67 .  The new API requires a structure change to the spec.

Awesome.  I've tested this in my k8s cluster and the HPA is getting created appropriately.  Thanks for the quick merge!


Pull out high-level interfaces as an extended example

An attempt to tackle #82, by putting all the code that tries to manage environments & installation into a separate buildtool_demo package, which does not get installed.
This will break things for anyone who was relying on the high-level functionality being in pep517, but I don't see any way to clean it up without doing that.
The functions for loading & checking the build-system info are retained as part of the real package, in pep517.pyproject.

Suggestion: move it into examples/*, to clearly denote that it's an example and make room for us to add additional things if there are any.

OK, I've moved it into an examples/ folder; I agree that's neater. After some fiddling with CI, the tests embedded in that example are working again.

Thanks @pradyunsg :-)

How do we plan to manage the rollout of this change?

I'd probably wait until a new python-build release/python-build gets into PyPA, so that we can recommend that as an alternative.

@FFY00 any ETA on that? anything to help with that?

I need to fix some simple issues and probably improve the test suite a bit. I don't think it should take too long.

Am I correct in understanding that this removes pep517.build? Was there ever a deprecation warning on this?
I guess I should have taken more seriously the warnings that it wasn't necessarily ready for production use, but given that this was the only PEP 517 build front-end for several years, I would kind of expect it to keep working at least for a while. I'll now have to run around and pin the versions on a bunch of my projects now.
If the justification is "we'll get a release of python-build soon, and we'll release this after that", that... doesn't seem like a long enough overlap.

I should note that pep517.build is included in this guide to automatic publishing with Github Actions on packaging.python.org.
There's a good chance that it's pretty widely used.

IMHO this should be done at shortest 6 months post python-build release to stop hundreds of ci failing all of sudden, and emmit a warning in the meantime about moving to python build. Definitely way to early to proceed with this.

Also, @jaraco's skeleton relies on this CLI IIRC + I've seen it used in many other places. I use it in projects and I guess since I've put this command into the guide that doesn't help.
So I second the call to have a proper depreciation period + have some effort to clean up the widely used recommendations from tutorials and other examples. While it is not a big deal for me to pin the version, it'd be challenging for folks who are less familiar with packaging.

(Another +1 for "this will break CI on every repo I own", so definitely a slowerish release would be super appreciated here too).

If I hold off releasing this change, will everyone stop filing issues about all the shortcomings of pep517.build? That's what led to this PR - I wrote the simplest possible PEP 517 frontend as a proof of concept and a starting point for serious frontends, and I failed to make it clear that that's what it was, so everyone's treating this quick sketch like it's meant to be the gold standard.
E.g. a proper build frontend would set up an isolated build environment (using something like venv), and let the user control how build dependencies were satisfied (e.g. get packages from this private index, or ignore the build requirements from the package and install these things instead). It would provide a way to pass config settings to the backend, probably options to control its output. Maybe optimisations for building multiple packages together. pep517.build does none of these things!

@takluyver I think would be better to make a release that starts emiting that warning instead of just holding off with the release. So users can know they need to migrate in the next (6) months? If you do the release in two months it will still be an abrupt removal without some warning emited beforehand...

Maybe we should hold off on even the warning until python-build is ready? I'm not sure a warning is much use if it can't suggest what to do instead.
Maybe once we can point people to python-build, it won't even be necessary to remove this. To be honest, I hadn't realised just how many people were relying on it. I don't want to break everybody's workflow, I just want to somehow make it clear that the pep517 package is primarily meant as a component for building PEP 517 frontends (like pip), not a frontend in itself.

Maybe we should hold off on even the warning until python-build is ready?

I think it's ready. The latest release 0.0.4 should be good as first release. We don't have to move the project under PyPa to recommend it IMHO (but eventually will move under PyPa... but that's not end user facing change).

@takluyver that's a good option too. I think the major reason pep517.build got popular is mainly because pip only has pip wheel but there's no command for producing source dists. I wanted to use pip for this but couldn't and didn't want to resort to calling setuptools directly.
I didn't realize you were annoyed by pep517.build bug reports (I don't think I posted any but still...). May I suggest that as a part of this effort, we could configure a custom issue template chooser? https://docs.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser
There's an example config @ https://github.com/pypa/pip/blob/master/.github/ISSUE_TEMPLATE/config.yml and the preview is here https://github.com/pypa/pip/issues/new/choose.
The idea is that we could add an item that has an external link to python-build instead of an issue creation button. This way, you could redirect some of this traffic to the right place. Plus you can add some text description explaining that folks shouldn't create issues but rather switch the tool...

Aha, I hadn't seen the python-build release yet. Thanks @FFY00!
So, how does this plan look:

[ ] Point to python-build in the README & possibly issue templates (thanks @webknjaz )
[ ] Make a new branch from before this PR was merged
[ ] Add a deprecationg warning when pep517.build is used
[ ] Release a version with the warning - possibly after a bit of a wait, to give people a chance to start moving to python-build and flush out any bugs there.

I've made a branch inc-pep517.build. I can't spend much time on this right now, but PRs are welcome for warnings & links in the documentation. Other PyPA people with access should feel free to merge stuff if they're confident in it - I don't want to be the bottleneck.

Thanks @takluyver! I was reading this and was gonna propose making a branch for the new stuff and I'm glad that you did that already. 🙃
The only thing I'd say is we should have a deprecation warning for all of the pep517 CLI stuff, since all of it is going to go away. Off the top if my head, that means also including a warning on pep517.check.

#91 exists as the tracking issue and the place for further discussion. :)


How much time does it take ?

I ran the program,i put python3 dac.py -xp proxies.txt (i made a proxies list 170 proxies) and it takes a long time...what should i do?does it actually run or just crash?

use the -v flag to see what's going on, most likely getting captcha'd

Kys


Dumping error obviously because of subchannel data

Version
32 bit, AnsiBuild, 20230909T161424
Describe the bug
This is a retry of dumping a problematic disc (Pokemon) from #70. There it was said:

The last 150 sectors indicate "lead-out", not Track 15. It's irregular.
LBA[220537, 0x35d79]: P[ff], Q[41aa0100000000490237f14f]{ Data,      Copy NG,                  LeadOut  , Idx[01], RMSF[00:00:00], AMSF[49:02:37]}, RtoW[0, 0, 0, 0]
LBA[220538, 0x35d7a]: P[ff], Q[41aa0100000100490238aaf1]{ Data,      Copy NG,                  LeadOut  , Idx[01], RMSF[00:00:01], AMSF[49:02:38]}, RtoW[0, 0, 0, 0]
LBA[220539, 0x35d7b]: P[ff], Q[41aa01000002004902395402]{ Data,      Copy NG,                  LeadOut  , Idx[01], RMSF[00:00:02], AMSF[49:02:39]}, RtoW[0, 0, 0, 0]

For this reason, app can't get the correct data sector length. I have no idea now.

Now I gave it a try with the most current version. I still cannot dump the disc, but I am not sure, if it is still the exact problem. in the _subReadable.txt the sectors from above now don't tell LeadOut anymore:
LBA[220537, 0x35d79]: P[ff], Q[41aa0100000000490237f14f]{ Data,      Copy NG,                  Track[aa], Idx[01], RMSF[00:00:00], AMSF[49:02:37]}, RtoW[0, 0, 0, 0]

Please just close this issue, if it is still the same problem and there isn't much one can do.
Log file
I put everything but the bin and scm files into this:
Pokemon.zip
console.log contains everything that was written to the console (I shortened the sector reads between first and last with [...])

Track[aa] is LeadOut.

Ah, I wasn't sure about the naming concept for these special tracks.
Not sure if it might be a relief, but Redumper also cannot create a useful image with that disc. CloneCD it'll stay then for that one :) thx for looking!


Increase inventory canary scalability

If there are too many packages, the canary will time out and metrics will no longer be available for operators.

@Chriscbr I saw a related pull request was merged for this issue, can this now be closed?

@gabewomble For this issue I was more thinking about when our package library gets larger and increasing the timeout is no longer an option since there's a 15 minute limit on Lambda functions.


ci: Run tests on 32-bit (386) as well

Related to https://github.com/hairyhenderson/gomplate/issues/2121 - there are some alignment bugs in go-fsimpl that went unnoticed. Testing on a 32-bit architecture in CI should help!

Nice. this caught #719.


[Help Wanted] In the wild!

If you are using XState in a project/at your company, please post it here!
I'm working on a new "In the wild" docs section (related: #172) and I would absolutely ❤ to highlight projects that are using XState (version 3 or 4).
If you have:

a (personal?) project in production that is using XState (front-end or back-end)
OR are at a company that is using XState internally
AND you would be happy and willing to share that you're using it

Please post it here. 😄🙏
Thanks in advance! 💙

At https://bridge21.com/ we are re-writing our site using XState 3 and react-automata. It's a game changer.
Our onboarding is complex with many loops in the process.  The stateMachine pattern reduces fragility, making it way easier to add features without breaking past work. I love being able to see the entire app in the visualizer.
Our stateMachine has about 90 states so far!  All of them quiet necessary.
react-automata makes building state dependent interfaces easy <State is={['*.onboarding.*', '*.returnCustomer.*']}> ... </State>

It's not much but I made a Pomodoro Clock emulator using React and XState with no other intermediary library. I'm using Hooks to subscribe individual components to an XState service.

Sorry I can't say anything "official" one way or the other, but I thought you'd like to know that we're starting up an internal proof-of-concept at my company to explore the use of XState.
We're really interested in the potential of pairing up designers and developers (leveraging something like Sketch) to work together on application flows and behaviours. We can see a lot of use-cases for this approach.
Depending on how things turn out, I hope to circle back with more details in the future.

@adamkl That's awesome, please keep me in the loop! One of the major goals for XState is to be integrated into design environments, similar to https://overflow.io.

Working on a POS system with my clients currently. I'll ask them if they'd be cool with me putting it up as an "in the wild" example. I'm sure they'll be fine with it, but I don't want to jump the gun if they have objections.

Deployed to production in Kong to handle form states (error, loading, modal, fetch machines etc.) https://konghq.com/products/kong-manager/

Using XState in 4D Healthware's frontend app.
We are using XState extensively.

We are using XState at Meru Health in our React Native app for managing many interactions. I just gave a presentation of using XState at React Helsinki - check it out! 😊

I used XState in a touchable app for the Royal Tyrrell Museum (Alberta - Canada) and documented its use in this article: "Modeling a Screensaver with a Statechart, a real use case".

Used XState for the navigation of a keg analytics web-app BinaryBeer.

Used XState to model data fetching and filtering of a collection of products 👉 stimm.com

Note: Filtering is done client side for platform limitations

Using xstate like crazy in https://serviceworkies.com and all my future games.

We're now using xstate to power a couple of the more complicated interactions at my place in our Behavior Insights Engine at Maritz.

I'm busy establishing a new company, developing a variety of applications, have removed Redux and Flow from the stack and introduced Typescript and XState. It will have add a learning curve for junior devs who join the team, but also teach a rather fundamental lesson instead of just learning a technology (how I feel about Redux).

It will have add a learning curve for junior devs who join the team

That's expected 😅 But I would love to know what the difficult parts are so I can improve documentation and make more examples. Thanks!

That's expected 😅 But I would love to know what the difficult parts are so I can improve documentation and make more examples. Thanks!

I don't mind putting together different basic scenarios that can be referenced in the documentation to help understand concepts. XState is a powerful library but I feel that it has a lot of possible options without clarity when to implement which possible solution, maybe if you have a solid foundation in computer science and state machines it would be more clear. The objective of the scenarios would be
to expect users do not have that much experience. That would obviously help the junior devs and anyone else who is learning XState. I am still creating a prototype application to learn XState when done I dont mind sharing that code and breaking it up into different use cases. Let me know what you would suggest etc...
I would like to see this library grow and be more adopted.

One of the things I'm releasing soon is an update to the visualizer (https://statecharts.github.io/xstate-viz) which will allow developers to share visualizations and copy/paste JavaScript/TypeScript machines, and start playing around with them. I feel like playing around with the visualizer is a great way to quickly grasp the concept of state machines and statecharts.

I've become familiar with the Xstate Docs and really like the style and format. However...
While the sections focus beautifully on implementation details there is virtually no mention of patterns and architecture.
If there is one thing that helps new learners (especially beginners) it is being able to understand implementation details clearly within the context of patterns and architecture, and in relation to other patterns and architecture.
The Redux Docs are an excellent example of this presentation of detail in context. These two articles, by the same author of the Docs, provide even more context and opportunity for understanding:
https://blog.isquaredsoftware.com/2017/05/idiomatic-redux-tao-of-redux-part-1/
I know how hard it is to write good documentation but I think this kind of addition would be of significant benefit. It would dramatically improve comprehension.
I would like to help if there was an opportunity. Even if it was to give feedback from a beginner's level.

@nick-walt let's move this discussion to a new issue: https://github.com/davidkpiano/xstate/issues/552

@davidkpiano
Ok, I can remove my post and repost a modified version there. Thanks 🙏

Using it in El Tablero Club Café to power some components, i'm migrating every component from useState to xState
Want to add model based testing in the future

Hi! We're using XState in an increasing number of places on TED.com as well as in some of our conference experience applications.

That's awesome @VinSpee! I know that @jonbellah was exploring using it there.

Yes! It's made it into production a few places now

The state-channel crypto wallet at daicard.io (source code is part of the Indra monorepo) is using xstate lightly w plans to utilize it more heavily down the road.

The state-channel crypto wallet at https://daicard.io (source code is part of the Indra monorepo) is using xstate lightly w plans to utilize it more heavily down the road.

The "statechannels project" is also currently using xstate heavily to specify how a standard state channel wallet should behave. The daicard wallet, which is based on the counterfactual framework, will be migrating to the standard state channels framework once it's production-ready.
We hope that these specifications can be turned into wallet implementations in different environments!

Using xstate internally at Morgan Stanley for implementing a mission critical project's auto-save behavior, including debouncing, service error retries and sort of that. More to come, we're buying in. We're interested to see the development of xstate. The visualizer is a must-have and I had to make a custom build with an updated xstate version in it, because a bug in the 4.6.* line affected my machine.

@sarimarton We are working on updating the visualizer and add dev tools (which will be much more useful than the visualizer for your workflow) by the end of the year!

To elaborate on @jonbellah 's work, my favorite state machine at the moment is used for a digital signage app that transitions slides based on time and server data.

there i no public link for now, so we use that in booking service

Our team at Blizzard leveraged xstate for the first time (via xstate-react) to control the various states on our beta signup panel on the official World of Warcraft Shadowlands website.

Our team at Blizzard leveraged xstate for the first time (via xstate-react) to control the various states on our beta signup panel on the official World of Warcraft Shadowlands website.

That's awesome.

I'm using XState at Koordinates to power an Electron app we are using. Lots to learn, lots of patterns to figure out, but I'm finding XState great to work with.
First React project I have done without Redux. Just XState + RxJS.

We've recently started using it at Flipgrid across a couple of our repos. Love it ❤


Implemented SSL user authentication setup

With this change added, one can use a dict with extra information to be added to socket creation on load_ssl_context.
Adding a more complex set of parameters to ssl_context, when using Flask, for example, will be possible through a new valid instance of ssl context, such as:
from flask import Flask
app = Flask(__name__)
ssl_context = {
		'cert_file': 'auth/server/crt.crt',
		'pkey_file': 'auth/server/key.key',
		'ca_certs': 'auth/server/ca.crt',
		'cert_reqs': ssl.CERT_REQUIRED
	}
	app.run(debug=True, ssl_context=ssl_context)

If possible - and valid, returned values from SSLSocket.getpeercert  will be stored into environ['SOCKET_PEER_CERT'].

You can't put keys in environ like that unless it's in the WSGI standard. Do other WSGI servers do that? For example, Gunicorn supports peer certs but doesn't set that key. Werkzeug's development server is only meant to be used during development, so anything that relied on environ['SOCKET_PEER_CERT'] would be tied to Werkzeug and not be deployable.

This modification was originally conceived to allow a Flask server to provide routes to authenticated users by simply comparing the requester's user name obtained from packet decryption (i.e., the common name)  with the database information.
Any suggestions of places to add the common name information, then?

I understand the principal behind client certs, and have used them myself to authenticate users. However, there is no standard name for the cert in the environ, and it's not Werkzeug's place to define that.
In Nginx, I add a directive to put the cert value in the HTTP environ that is sent to the WSGI server. The key is defined by me in the directive and matches what I use in the app. For example, https://serverfault.com/questions/622855/nginx-proxy-to-back-end-with-ssl-client-certificate-authentication.
You'd need to find an existing standard for the key name, or open a PEP to modify the WSGI spec for that. I am not familiar with that process, it's something you'd need to investigate.
I would prefer that users continue to handle SSL at the web server level. Again, Werkzeug's server is only for development, so anything special added to it is not portable to other WSGI servers.

PEP 3333 says:

A server or gateway should attempt to provide as many other CGI
variables as are applicable.  In addition, if SSL is in use, the server
or gateway should also provide as many of the Apache SSL environment
variables [5] as are applicable, such as HTTPS=on and
SSL_PROTOCOL.

The linked resource lists SSL_CLIENT_CERT. So there's the existing standard for the key name.

When this option is enabled, additional CGI/SSI environment variables are created: SSL_SERVER_CERT, **SSL_CLIENT_CERT** and SSL_CLIENT_CERT_CHAINn (with n = 0,1,2,..). These contain the PEM-encoded X.509 Certificates of server and client for the current HTTPS connection and can be used by CGI scripts for deeper Certificate checking.

@davidism  is this the demanded standardization?

Looks good to me.

Looks good to me, that's why I added a thumbs up to it.

shouldn't that be enough to accept the pull request, then?

@barsand that means you need to rename your environ name to the one @edk0 suggested.

@barsand that means you need to rename your environ name to the one @edk0 suggested.

Done. Thank you for the head's up, @lepture !

However, your patch failed the test cases.

I've applied some global code style cleanup and changes, and as a result this PR will no longer merge. Would you mind recreating it against the current mater? Sorry for the inconvenience.


Sync fork with upstream

Keeping our fork up to date.

This is no longer up-to-date. I have rebased the probot change on top of the upstream master.


Update action.ps1

This is a fix for:
SecDevOps---CondaDependabot Dependabot CVEs Count: 0
ForEach-Object: /home/runner/work/actions/advanced-security/dependabot-epss-action/v0/action.ps1:136
Line |
136 |  …  = $Dependabot_Alerts_CVEs | ForEach-Object { $epssHash[$] } | Where …
|                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Index operation failed; the array index evaluated to null.
Error: Process completed with exit code 1.
To stop the process from erroring out if no CVEs exist.

addresses #3

Aye, it would be nice to cover all the repos in our org with this safety check, some are very small repos.


Formatting crashes when muon is not installed

Not sure what's best - prompt the user and auto-install (similar to the python extension's use of Black/autopep8), or simply inform the user.

Output:
2023-10-13 09:49:49.106 Swift-MesonLSP.exe[24744:2334] ignoring unknown notification MessageDecodingError(code: LanguageServerProtocol.ErrorCode(rawValue: -32601), message: "method not found: textDocument/willSave", id: nil, messageKind: LanguageServerProtocol.MessageDecodingError.MessageKind.notification)
2023-10-13 09:49:49.126 Swift-MesonLSP.exe[24744:2334] MesonServer: Request<textDocument/formatting(99)>
2023-10-13T09:49:49+1000 info LanguageServer::MesonServer : [LanguageServer] Formatting c:/.../src/meson.build
2023-10-13T09:49:49+1000 warning LanguageServer::MesonServer : [LanguageServer] Unable to find c:/.../src/meson.build in memfiles
2023-10-13T09:49:49+1000 error LanguageServer::MesonServer : [LanguageServer] Unable to format file
2023-10-13 09:49:49.133 Swift-MesonLSP.exe[24744:2334] MesonServer: Response<textDocument/formatting(99)>
[Error - 9:49:49 AM] Request textDocument/formatting failed.
  Message: Either failed to read the input file or to format using muon
  Code: -32603
2023-10-13 09:49:49.180 Swift-MesonLSP.exe[24744:2334] MesonServer: Notification<textDocument/didSave>
2023-10-13T09:49:49+1000 info LanguageServer::MesonServer : [LanguageServer] [Save] Dropping c:/.../src/meson.build from memcache

Looks like the github mirror builds windows binaries, it just doesn't seem to store any artifacts (perhaps only the repo owner can access them).
I'd be happy with a BYO binary on PATH - muon is a little bleeding-edge right now, so it'd be nice to pin to some version I know works.

Right you are! How awesome, thanks for this massive usability bump! ^_^