building from source failed.

I've tried to build the lib inside docker container based on python:3.11-bullseye.
My flow was based on https://github.com/cloudflare/stpyv8/blob/master/.github/workflows/build-debian.yml
Here are the steps to reproduce:

apt install libboost-dev libboost-system-dev libboost-iostreams-dev libboost-python-dev curl procps pkg-config git vim
pip install --upgrade pip setuptools wheel pytest
export V8_DEPS_LINUX=0
export LDFLAGS="-L/usr/lib -L/usr/lib/x86_64-linux-gnu"
git clone https://github.com/cloudflare/stpyv8.git
cd stpyv8
python setup.py build

Log:
root@e0ecb9a903ee:/stpyv8# python setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-311
copying STPyV8.py -> build/lib.linux-x86_64-cpython-311
running build_ext
Cloning depot tools
Cloning into '/stpyv8/depot_tools'...
remote: Total 52686 (delta 33414), reused 52686 (delta 33414)
Receiving objects: 100% (52686/52686), 58.51 MiB | 32.79 MiB/s, done.
Resolving deltas: 100% (33414/33414), done.
Fetching Google V8 code
Running: gclient root
WARNING: Your metrics.cfg file was invalid or nonexistent. A new one will be created.
Running: gclient config --spec 'solutions = [
  {
    "name": "v8",
    "url": "https://chromium.googlesource.com/v8/v8.git",
    "deps_file": "DEPS",
    "managed": False,
    "custom_deps": {},
  },
]
'
Updating depot_tools...
using /tmp/goma_unknown as tmpdir
INFO: creating cache dir (/tmp/goma_unknown/goma_cache).
compiler_proxy is not running
Running: gclient sync --with_branch_heads
Updating depot_tools...
using /tmp/goma_unknown as tmpdir
compiler_proxy is not running

________ running 'git -c core.deltaBaseCacheLimit=2g clone --no-checkout --progress https://chromium.googlesource.com/v8/v8.git /stpyv8/_gclient_v8_t02qo1dy' in '/stpyv8'
Cloning into '/stpyv8/_gclient_v8_t02qo1dy'...
remote: Total 996907 (delta 802280), reused 996907 (delta 802280)
Receiving objects: 100% (996907/996907), 816.26 MiB | 33.92 MiB/s, done.
Resolving deltas: 100% (802280/802280), done.

[0:01:20] Still working on:
[0:01:20]   v8

[0:01:30] Still working on:
[0:01:30]   v8
1>Syncing projects:   0% ( 0/ 2)
[0:01:38] Still working on:
[0:01:38]   v8
Syncing projects: 100% (29/29), done.

________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth --bucket chromium-clang-format -s buildtools/linux64/clang-format.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>Downloading 1 files took 21.579749 second(s)
Hook 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth --bucket chromium-clang-format -s buildtools/linux64/clang-format.sha1' took 21.65 secs
Running hooks:  37% (12/32) wasm_spec_tests
________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-spec-tests/tests.tar.gz.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>0> Extracting 402 entries from test/wasm-spec-tests/tests.tar.gz to test/wasm-spec-tests/tests
Downloading 1 files took 5.491014 second(s)
Running hooks:  40% (13/32) wasm_js
________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-js/tests.tar.gz.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>0> Extracting 200 entries from test/wasm-js/tests.tar.gz to test/wasm-js/tests
Downloading 1 files took 10.175246 second(s)
Hook 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-js/tests.tar.gz.sha1' took 10.23 secs
Running hooks:  50% (16/32) sysroot_x86
________ running 'python3 build/linux/sysroot_scripts/install-sysroot.py --arch=x86' in '/stpyv8/v8'
Installing Debian bullseye i386 root image: /stpyv8/v8/build/linux/debian_bullseye_i386-sysroot
Downloading https://commondatastorage.googleapis.com/chrome-linux-sysroot/toolchain/de629dcc11a6ab1b11e6d66c4180a959c6290097/debian_bullseye_i386_sysroot.tar.xz
Running hooks:  53% (17/32) sysroot_x64
________ running 'python3 build/linux/sysroot_scripts/install-sysroot.py --arch=x64' in '/stpyv8/v8'
Installing Debian bullseye amd64 root image: /stpyv8/v8/build/linux/debian_bullseye_amd64-sysroot
Downloading https://commondatastorage.googleapis.com/chrome-linux-sysroot/toolchain/3bdb3503702d35520d101fc5eec9a8ab5353149f/debian_bullseye_amd64_sysroot.tar.xz
Running hooks:  71% (23/32) clang
________ running 'python3 tools/clang/scripts/update.py' in '/stpyv8/v8'
Downloading https://commondatastorage.googleapis.com/chromium-browser-clang/Linux_x64/clang-llvmorg-17-init-3874-g93a2fecc-1.tar.xz .......... Done.
Running hooks: 100% (32/32), done.
Running: git submodule foreach 'git config -f $toplevel/.git/config submodule.$name.ignore all'
Running: git config --add remote.origin.fetch '+refs/tags/*:refs/tags/*'
Running: git config diff.ignoreSubmodules all
Fetching the release tag information
Checkout Google V8 v11.1.277.14
Previous HEAD position was 692d8a972e [wasm-gc] Make GC and inlining configurable by Origin Trial
HEAD is now at ddb3086599 Version 11.1.277.14
Syncing Google V8 code
Updating depot_tools...
using /tmp/goma_unknown as tmpdir
compiler_proxy is not running
Syncing projects: 100% (29/29), done.

________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-spec-tests/tests.tar.gz.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>0> Removed test/wasm-spec-tests/tests...
0> Extracting 399 entries from test/wasm-spec-tests/tests.tar.gz to test/wasm-spec-tests/tests
Downloading 1 files took 5.338898 second(s)
Running hooks:  40% (13/32) wasm_js
________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-js/tests.tar.gz.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>0> Removed test/wasm-js/tests...
0> Extracting 184 entries from test/wasm-js/tests.tar.gz to test/wasm-js/tests
Downloading 1 files took 4.957527 second(s)
Running hooks:  71% (23/32) clang
________ running 'python3 tools/clang/scripts/update.py' in '/stpyv8/v8'
Downloading https://commondatastorage.googleapis.com/chromium-browser-clang/Linux_x64/clang-llvmorg-16-init-17653-g39da55e8-2.tar.xz .......... Done.
Running hooks: 100% (32/32), done.
Generate build scripts for V8 (v11.1.277.14)
Done. Made 181 targets from 97 files in 225ms
Build V8 with ninja
ninja: Entering directory `out.gn/x64.release.sample'
[1897/1897] AR obj/libv8_monolith.a
building '_STPyV8' extension
creating build/temp.linux-x86_64-cpython-311
creating build/temp.linux-x86_64-cpython-311/src
gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.11 -c src/Context.cpp -o build/temp.linux-x86_64-cpython-311/src/Context.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/iostreams/device/file_descriptor.hpp:28,
                 from src/Exception.h:7,
                 from src/Isolate.h:4,
                 from src/Context.h:6,
                 from src/Context.cpp:1:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /usr/local/include/python3.11/Python.h:44,
                 from /usr/include/boost/python/detail/wrap_python.hpp:178,
                 from /usr/include/boost/python/detail/prefix.hpp:13,
                 from /usr/include/boost/python/args.hpp:8,
                 from /usr/include/boost/python.hpp:11,
                 from src/Utils.h:61,
                 from src/Exception.h:12,
                 from src/Isolate.h:4,
                 from src/Context.h:6,
                 from src/Context.cpp:1:
/usr/include/boost/python/object/make_instance.hpp: In instantiation of ‘static PyObject* boost::python::objects::make_instance_impl<T, Holder, Derived>::execute(Arg&) [with Arg = std::shared_ptr<CPlatform>; T = CPlatform; Holder = boost::python::objects::pointer_holder<std::shared_ptr<CPlatform>, CPlatform>; Derived = boost::python::objects::make_ptr_instance<CPlatform, boost::python::objects::pointer_holder<std::shared_ptr<CPlatform>, CPlatform> >; PyObject = _object]’:
/usr/include/boost/python/object/class_wrapper.hpp:42:37:   required from ‘static PyObject* boost::python::objects::class_value_wrapper<Src, MakeInstance>::convert(Src) [with Src = std::shared_ptr<CPlatform>; MakeInstance = boost::python::objects::make_ptr_instance<CPlatform, boost::python::objects::pointer_holder<std::shared_ptr<CPlatform>, CPlatform> >; PyObject = _object]’
/usr/include/boost/python/converter/as_to_python_function.hpp:27:61:   required from ‘static PyObject* boost::python::converter::as_to_python_function<T, ToPython>::convert(const void*) [with T = std::shared_ptr<CPlatform>; ToPython = boost::python::objects::class_value_wrapper<std::shared_ptr<CPlatform>, boost::python::objects::make_ptr_instance<CPlatform, boost::python::objects::pointer_holder<std::shared_ptr<CPlatform>, CPlatform> > >; PyObject = _object]’
/usr/include/boost/python/to_python_converter.hpp:83:9:   required from ‘boost::python::to_python_converter<T, Conversion, has_get_pytype>::to_python_converter() [with T = std::shared_ptr<CPlatform>; Conversion = boost::python::objects::class_value_wrapper<std::shared_ptr<CPlatform>, boost::python::objects::make_ptr_instance<CPlatform, boost::python::objects::pointer_holder<std::shared_ptr<CPlatform>, CPlatform> > >; bool has_get_pytype = true]’
/usr/include/boost/python/object/class_wrapper.hpp:37:8:   required from here
/usr/include/boost/python/object/make_instance.hpp:50:13: error: lvalue required as left operand of assignment
   50 |             Py_SIZE(instance) = offsetof(instance_t, storage);
      |             ^~~~~~~
/usr/include/boost/python/object/make_instance.hpp: In instantiation of ‘static PyObject* boost::python::objects::make_instance_impl<T, Holder, Derived>::execute(Arg&) [with Arg = std::shared_ptr<CIsolate>; T = CIsolate; Holder = boost::python::objects::pointer_holder<std::shared_ptr<CIsolate>, CIsolate>; Derived = boost::python::objects::make_ptr_instance<CIsolate, boost::python::objects::pointer_holder<std::shared_ptr<CIsolate>, CIsolate> >; PyObject = _object]’:
/usr/include/boost/python/object/class_wrapper.hpp:42:37:   required from ‘static PyObject* boost::python::objects::class_value_wrapper<Src, MakeInstance>::convert(Src) [with Src = std::shared_ptr<CIsolate>; MakeInstance = boost::python::objects::make_ptr_instance<CIsolate, boost::python::objects::pointer_holder<std::shared_ptr<CIsolate>, CIsolate> >; PyObject = _object]’
/usr/include/boost/python/converter/as_to_python_function.hpp:27:61:   required from ‘static PyObject* boost::python::converter::as_to_python_function<T, ToPython>::convert(const void*) [with T = std::shared_ptr<CIsolate>; ToPython = boost::python::objects::class_value_wrapper<std::shared_ptr<CIsolate>, boost::python::objects::make_ptr_instance<CIsolate, boost::python::objects::pointer_holder<std::shared_ptr<CIsolate>, CIsolate> > >; PyObject = _object]’
/usr/include/boost/python/to_python_converter.hpp:83:9:   required from ‘boost::python::to_python_converter<T, Conversion, has_get_pytype>::to_python_converter() [with T = std::shared_ptr<CIsolate>; Conversion = boost::python::objects::class_value_wrapper<std::shared_ptr<CIsolate>, boost::python::objects::make_ptr_instance<CIsolate, boost::python::objects::pointer_holder<std::shared_ptr<CIsolate>, CIsolate> > >; bool has_get_pytype = true]’
/usr/include/boost/python/object/class_wrapper.hpp:37:8:   required from here
/usr/include/boost/python/object/make_instance.hpp:50:13: error: lvalue required as left operand of assignment
/usr/include/boost/python/object/make_instance.hpp: In instantiation of ‘static PyObject* boost::python::objects::make_instance_impl<T, Holder, Derived>::execute(Arg&) [with Arg = std::shared_ptr<CContext>; T = CContext; Holder = boost::python::objects::pointer_holder<std::shared_ptr<CContext>, CContext>; Derived = boost::python::objects::make_ptr_instance<CContext, boost::python::objects::pointer_holder<std::shared_ptr<CContext>, CContext> >; PyObject = _object]’:
/usr/include/boost/python/object/class_wrapper.hpp:42:37:   required from ‘static PyObject* boost::python::objects::class_value_wrapper<Src, MakeInstance>::convert(Src) [with Src = std::shared_ptr<CContext>; MakeInstance = boost::python::objects::make_ptr_instance<CContext, boost::python::objects::pointer_holder<std::shared_ptr<CContext>, CContext> >; PyObject = _object]’
/usr/include/boost/python/converter/as_to_python_function.hpp:27:61:   required from ‘static PyObject* boost::python::converter::as_to_python_function<T, ToPython>::convert(const void*) [with T = std::shared_ptr<CContext>; ToPython = boost::python::objects::class_value_wrapper<std::shared_ptr<CContext>, boost::python::objects::make_ptr_instance<CContext, boost::python::objects::pointer_holder<std::shared_ptr<CContext>, CContext> > >; PyObject = _object]’
/usr/include/boost/python/to_python_converter.hpp:83:9:   required from ‘boost::python::to_python_converter<T, Conversion, has_get_pytype>::to_python_converter() [with T = std::shared_ptr<CContext>; Conversion = boost::python::objects::class_value_wrapper<std::shared_ptr<CContext>, boost::python::objects::make_ptr_instance<CContext, boost::python::objects::pointer_holder<std::shared_ptr<CContext>, CContext> > >; bool has_get_pytype = true]’
/usr/include/boost/python/object/class_wrapper.hpp:37:8:   required from here
/usr/include/boost/python/object/make_instance.hpp:50:13: error: lvalue required as left operand of assignment
error: command '/usr/bin/gcc' failed with exit code 1

For python:3.10-bulleye
root@62c5e4be9f79:/# apt install libboost-dev libboost-system-dev libboost-iostreams-dev libboost-python-dev curl procps pkg-config git vim
pip install --upgrade pip setuptools wheel pytest
export V8_DEPS_LINUX=0
export LDFLAGS="-L/usr/lib -L/usr/lib/x86_64-linux-gnu"
git clone https://github.com/cloudflare/stpyv8.git
cd stpyv8
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
pkg-config is already the newest version (0.29.2-1).
pkg-config set to manually installed.
procps is already the newest version (2:3.3.17-5).
curl is already the newest version (7.74.0-1.3+deb11u7).
git is already the newest version (1:2.30.2-1+deb11u2).
The following additional packages will be installed:
  javascript-common libboost-iostreams1.74-dev libboost-iostreams1.74.0 libboost-python1.74-dev libboost-python1.74.0 libboost-regex1.74-dev libboost-regex1.74.0 libboost-system1.74-dev libboost-system1.74.0 libboost1.74-dev libgpm2
  libjs-jquery libjs-sphinxdoc libjs-underscore libpython3-dev libpython3.9 libpython3.9-dev python3-dev python3.9-dev vim-common vim-runtime xxd
Suggested packages:
  apache2 | lighttpd | httpd libboost-doc libboost1.74-doc gccxml libboost-atomic1.74-dev libboost-chrono1.74-dev libboost-container1.74-dev libboost-context1.74-dev libboost-contract1.74-dev libboost-coroutine1.74-dev
  libboost-date-time1.74-dev libboost-exception1.74-dev libboost-fiber1.74-dev libboost-filesystem1.74-dev libboost-graph1.74-dev libboost-graph-parallel1.74-dev libboost-locale1.74-dev libboost-log1.74-dev libboost-math1.74-dev
  libboost-mpi1.74-dev libboost-mpi-python1.74-dev libboost-numpy1.74-dev libboost-program-options1.74-dev libboost-random1.74-dev libboost-serialization1.74-dev libboost-stacktrace1.74-dev libboost-test1.74-dev libboost-thread1.74-dev
  libboost-timer1.74-dev libboost-type-erasure1.74-dev libboost-wave1.74-dev libboost1.74-tools-dev libmpfrc++-dev libntl-dev libboost-nowide1.74-dev gpm ctags vim-doc vim-scripts
The following NEW packages will be installed:
  javascript-common libboost-dev libboost-iostreams-dev libboost-iostreams1.74-dev libboost-iostreams1.74.0 libboost-python-dev libboost-python1.74-dev libboost-python1.74.0 libboost-regex1.74-dev libboost-regex1.74.0 libboost-system-dev
  libboost-system1.74-dev libboost-system1.74.0 libboost1.74-dev libgpm2 libjs-jquery libjs-sphinxdoc libjs-underscore libpython3-dev libpython3.9 libpython3.9-dev python3-dev python3.9-dev vim vim-common vim-runtime xxd
0 upgraded, 27 newly installed, 0 to remove and 1 not upgraded.
Need to get 27.3 MB of archives.
After this operation, 229 MB of additional disk space will be used.
Do you want to continue?
(Reading database ... 23423 files and directories currently installed.)
Preparing to unpack .../00-xxd_2%3a8.2.2434-3+deb11u1_amd64.deb ...
Unpacking xxd (2:8.2.2434-3+deb11u1) ...
Selecting previously unselected package vim-common.
Preparing to unpack .../01-vim-common_2%3a8.2.2434-3+deb11u1_all.deb ...
Unpacking vim-common (2:8.2.2434-3+deb11u1) ...
Selecting previously unselected package javascript-common.
Preparing to unpack .../02-javascript-common_11+nmu1_all.deb ...
Unpacking javascript-common (11+nmu1) ...
Selecting previously unselected package libboost1.74-dev:amd64.
Preparing to unpack .../03-libboost1.74-dev_1.74.0-9_amd64.deb ...
Unpacking libboost1.74-dev:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-dev:amd64.
Preparing to unpack .../04-libboost-dev_<IP_ADDRESS>_amd64.deb ...
Unpacking libboost-dev:amd64 (<IP_ADDRESS>) ...
Selecting previously unselected package libboost-regex1.74.0:amd64.
Preparing to unpack .../05-libboost-regex1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-regex1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-regex1.74-dev:amd64.
Preparing to unpack .../06-libboost-regex1.74-dev_1.74.0-9_amd64.deb ...
Unpacking libboost-regex1.74-dev:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-iostreams1.74.0:amd64.
Preparing to unpack .../07-libboost-iostreams1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-iostreams1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-iostreams1.74-dev:amd64.
Preparing to unpack .../08-libboost-iostreams1.74-dev_1.74.0-9_amd64.deb ...
Unpacking libboost-iostreams1.74-dev:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-iostreams-dev:amd64.
Preparing to unpack .../09-libboost-iostreams-dev_<IP_ADDRESS>_amd64.deb ...
Unpacking libboost-iostreams-dev:amd64 (<IP_ADDRESS>) ...
Selecting previously unselected package libboost-python1.74.0.
Preparing to unpack .../10-libboost-python1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-python1.74.0 (1.74.0-9) ...
Selecting previously unselected package libpython3.9:amd64.
Preparing to unpack .../11-libpython3.9_3.9.2-1_amd64.deb ...
Unpacking libpython3.9:amd64 (3.9.2-1) ...
Selecting previously unselected package libpython3.9-dev:amd64.
Preparing to unpack .../12-libpython3.9-dev_3.9.2-1_amd64.deb ...
Unpacking libpython3.9-dev:amd64 (3.9.2-1) ...
Selecting previously unselected package libpython3-dev:amd64.
Preparing to unpack .../13-libpython3-dev_3.9.2-3_amd64.deb ...
Unpacking libpython3-dev:amd64 (3.9.2-3) ...
Selecting previously unselected package python3.9-dev.
Preparing to unpack .../14-python3.9-dev_3.9.2-1_amd64.deb ...
Unpacking python3.9-dev (3.9.2-1) ...
Selecting previously unselected package libjs-jquery.
Preparing to unpack .../15-libjs-jquery_3.5.1+dfsg+~3.5.5-7_all.deb ...
Unpacking libjs-jquery (3.5.1+dfsg+~3.5.5-7) ...
Selecting previously unselected package libjs-underscore.
Preparing to unpack .../16-libjs-underscore_1.9.1~dfsg-3_all.deb ...
Unpacking libjs-underscore (1.9.1~dfsg-3) ...
Selecting previously unselected package libjs-sphinxdoc.
Preparing to unpack .../17-libjs-sphinxdoc_3.4.3-2_all.deb ...
Unpacking libjs-sphinxdoc (3.4.3-2) ...
Selecting previously unselected package python3-dev.
Preparing to unpack .../18-python3-dev_3.9.2-3_amd64.deb ...
Unpacking python3-dev (3.9.2-3) ...
Selecting previously unselected package libboost-python1.74-dev.
Preparing to unpack .../19-libboost-python1.74-dev_1.74.0-9_amd64.deb ...
Unpacking libboost-python1.74-dev (1.74.0-9) ...
Selecting previously unselected package libboost-python-dev.
Preparing to unpack .../20-libboost-python-dev_<IP_ADDRESS>_amd64.deb ...
Unpacking libboost-python-dev (<IP_ADDRESS>) ...
Selecting previously unselected package libboost-system1.74.0:amd64.
Preparing to unpack .../21-libboost-system1.74.0_1.74.0-9_amd64.deb ...
Unpacking libboost-system1.74.0:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-system1.74-dev:amd64.
Preparing to unpack .../22-libboost-system1.74-dev_1.74.0-9_amd64.deb ...
Unpacking libboost-system1.74-dev:amd64 (1.74.0-9) ...
Selecting previously unselected package libboost-system-dev:amd64.
Preparing to unpack .../23-libboost-system-dev_<IP_ADDRESS>_amd64.deb ...
Unpacking libboost-system-dev:amd64 (<IP_ADDRESS>) ...
Selecting previously unselected package libgpm2:amd64.
Preparing to unpack .../24-libgpm2_1.20.7-8_amd64.deb ...
Unpacking libgpm2:amd64 (1.20.7-8) ...
Selecting previously unselected package vim-runtime.
Preparing to unpack .../25-vim-runtime_2%3a8.2.2434-3+deb11u1_all.deb ...
Adding 'diversion of /usr/share/vim/vim82/doc/help.txt to /usr/share/vim/vim82/doc/help.txt.vim-tiny by vim-runtime'
Adding 'diversion of /usr/share/vim/vim82/doc/tags to /usr/share/vim/vim82/doc/tags.vim-tiny by vim-runtime'
Unpacking vim-runtime (2:8.2.2434-3+deb11u1) ...
Selecting previously unselected package vim.
Preparing to unpack .../26-vim_2%3a8.2.2434-3+deb11u1_amd64.deb ...
Unpacking vim (2:8.2.2434-3+deb11u1) ...
Setting up libboost-system1.74.0:amd64 (1.74.0-9) ...
Setting up javascript-common (11+nmu1) ...
Setting up libboost1.74-dev:amd64 (1.74.0-9) ...
Setting up libgpm2:amd64 (1.20.7-8) ...
Setting up libboost-iostreams1.74.0:amd64 (1.74.0-9) ...
Setting up xxd (2:8.2.2434-3+deb11u1) ...
Setting up libpython3.9:amd64 (3.9.2-1) ...
Setting up vim-common (2:8.2.2434-3+deb11u1) ...
Setting up libboost-system1.74-dev:amd64 (1.74.0-9) ...
Setting up libboost-regex1.74.0:amd64 (1.74.0-9) ...
Setting up libboost-regex1.74-dev:amd64 (1.74.0-9) ...
Setting up libboost-dev:amd64 (<IP_ADDRESS>) ...
Setting up libjs-jquery (3.5.1+dfsg+~3.5.5-7) ...
Setting up vim-runtime (2:8.2.2434-3+deb11u1) ...
Setting up libboost-python1.74.0 (1.74.0-9) ...
Setting up libjs-underscore (1.9.1~dfsg-3) ...
Setting up vim (2:8.2.2434-3+deb11u1) ...
update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vim (vim) in auto mode
update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vimdiff (vimdiff) in auto mode
update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/rvim (rvim) in auto mode
update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/rview (rview) in auto mode
update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/vi (vi) in auto mode
update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/view (view) in auto mode
update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/ex (ex) in auto mode
update-alternatives: using /usr/bin/vim.basic to provide /usr/bin/editor (editor) in auto mode
Setting up libboost-system-dev:amd64 (<IP_ADDRESS>) ...
Setting up libpython3.9-dev:amd64 (3.9.2-1) ...
Setting up libboost-iostreams1.74-dev:amd64 (1.74.0-9) ...
Setting up libjs-sphinxdoc (3.4.3-2) ...
Setting up python3.9-dev (3.9.2-1) ...
Setting up libpython3-dev:amd64 (3.9.2-3) ...
Setting up libboost-iostreams-dev:amd64 (<IP_ADDRESS>) ...
Setting up python3-dev (3.9.2-3) ...
Setting up libboost-python1.74-dev (1.74.0-9) ...
Setting up libboost-python-dev (<IP_ADDRESS>) ...
Processing triggers for libc-bin (2.31-13+deb11u5) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Requirement already satisfied: pip in /usr/local/lib/python3.10/site-packages (22.3.1)
Collecting pip
  Downloading pip-23.0.1-py3-none-any.whl (2.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 17.8 MB/s eta 0:00:00
Requirement already satisfied: setuptools in /usr/local/lib/python3.10/site-packages (65.5.1)
Collecting setuptools
  Downloading setuptools-67.6.0-py3-none-any.whl (1.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.1/1.1 MB 95.9 MB/s eta 0:00:00
Requirement already satisfied: wheel in /usr/local/lib/python3.10/site-packages (0.38.4)
Collecting wheel
  Downloading wheel-0.40.0-py3-none-any.whl (64 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 64.5/64.5 kB 15.1 MB/s eta 0:00:00
Collecting pytest
  Downloading pytest-7.2.2-py3-none-any.whl (317 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 317.2/317.2 kB 54.9 MB/s eta 0:00:00
Collecting pluggy<2.0,>=0.12
  Downloading pluggy-1.0.0-py2.py3-none-any.whl (13 kB)
Collecting attrs>=19.2.0
  Downloading attrs-22.2.0-py3-none-any.whl (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.0/60.0 kB 14.8 MB/s eta 0:00:00
Collecting packaging
  Downloading packaging-23.0-py3-none-any.whl (42 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 42.7/42.7 kB 10.1 MB/s eta 0:00:00
Collecting exceptiongroup>=1.0.0rc8
  Downloading exceptiongroup-1.1.1-py3-none-any.whl (14 kB)
Collecting tomli>=1.0.0
  Downloading tomli-2.0.1-py3-none-any.whl (12 kB)
Collecting iniconfig
  Downloading iniconfig-2.0.0-py3-none-any.whl (5.9 kB)
Installing collected packages: wheel, tomli, setuptools, pluggy, pip, packaging, iniconfig, exceptiongroup, attrs, pytest
  Attempting uninstall: wheel
    Found existing installation: wheel 0.38.4
    Uninstalling wheel-0.38.4:
      Successfully uninstalled wheel-0.38.4
  Attempting uninstall: setuptools
    Found existing installation: setuptools 65.5.1
    Uninstalling setuptools-65.5.1:
      Successfully uninstalled setuptools-65.5.1
  Attempting uninstall: pip
    Found existing installation: pip 22.3.1
    Uninstalling pip-22.3.1:
      Successfully uninstalled pip-22.3.1
Successfully installed attrs-22.2.0 exceptiongroup-1.1.1 iniconfig-2.0.0 packaging-23.0 pip-23.0.1 pluggy-1.0.0 pytest-7.2.2 setuptools-67.6.0 tomli-2.0.1 wheel-0.40.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Cloning into 'stpyv8'...
remote: Enumerating objects: 2732, done.
remote: Counting objects: 100% (1456/1456), done.
remote: Compressing objects: 100% (530/530), done.
remote: Total 2732 (delta 892), reused 1386 (delta 846), pack-reused 1276
Receiving objects: 100% (2732/2732), 34.72 MiB | 68.77 MiB/s, done.
Resolving deltas: 100% (1702/1702), done.
root@62c5e4be9f79:/stpyv8# python setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-cpython-310
copying STPyV8.py -> build/lib.linux-x86_64-cpython-310
running build_ext
Cloning depot tools
Cloning into '/stpyv8/depot_tools'...
remote: Total 52686 (delta 33414), reused 52686 (delta 33414)
Receiving objects: 100% (52686/52686), 58.51 MiB | 37.71 MiB/s, done.
Resolving deltas: 100% (33414/33414), done.
Fetching Google V8 code
Running: gclient root
WARNING: Your metrics.cfg file was invalid or nonexistent. A new one will be created.
Running: gclient config --spec 'solutions = [
  {
    "name": "v8",
    "url": "https://chromium.googlesource.com/v8/v8.git",
    "deps_file": "DEPS",
    "managed": False,
    "custom_deps": {},
  },
]
'
Updating depot_tools...
using /tmp/goma_unknown as tmpdir
INFO: creating cache dir (/tmp/goma_unknown/goma_cache).
compiler_proxy is not running
Running: gclient sync --with_branch_heads
Updating depot_tools...
using /tmp/goma_unknown as tmpdir
compiler_proxy is not running

________ running 'git -c core.deltaBaseCacheLimit=2g clone --no-checkout --progress https://chromium.googlesource.com/v8/v8.git /stpyv8/_gclient_v8_4jj8te2v' in '/stpyv8'
Cloning into '/stpyv8/_gclient_v8_4jj8te2v'...
remote: Finding sources: 100% (4/4)
remote: Total 996911 (delta 802280), reused 996908 (delta 802280)
Receiving objects: 100% (996911/996911), 816.26 MiB | 34.48 MiB/s, done.
Resolving deltas: 100% (802280/802280), done.

[0:01:20] Still working on:
[0:01:20]   v8

[0:01:30] Still working on:
[0:01:30]   v8
1>Syncing projects:   0% ( 0/ 2)
[0:01:35] Still working on:
[0:01:35]   v8
Syncing projects: 100% (29/29), done.

________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth --bucket chromium-clang-format -s buildtools/linux64/clang-format.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>Downloading 1 files took 21.348850 second(s)
Hook 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth --bucket chromium-clang-format -s buildtools/linux64/clang-format.sha1' took 21.42 secs
Running hooks:  37% (12/32) wasm_spec_tests
________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-spec-tests/tests.tar.gz.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>0> Extracting 402 entries from test/wasm-spec-tests/tests.tar.gz to test/wasm-spec-tests/tests
Downloading 1 files took 5.892888 second(s)
Running hooks:  40% (13/32) wasm_js
________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-js/tests.tar.gz.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>0> Extracting 200 entries from test/wasm-js/tests.tar.gz to test/wasm-js/tests
Downloading 1 files took 5.100941 second(s)
Running hooks:  50% (16/32) sysroot_x86
________ running 'python3 build/linux/sysroot_scripts/install-sysroot.py --arch=x86' in '/stpyv8/v8'
Installing Debian bullseye i386 root image: /stpyv8/v8/build/linux/debian_bullseye_i386-sysroot
Downloading https://commondatastorage.googleapis.com/chrome-linux-sysroot/toolchain/de629dcc11a6ab1b11e6d66c4180a959c6290097/debian_bullseye_i386_sysroot.tar.xz
Running hooks:  53% (17/32) sysroot_x64
________ running 'python3 build/linux/sysroot_scripts/install-sysroot.py --arch=x64' in '/stpyv8/v8'
Installing Debian bullseye amd64 root image: /stpyv8/v8/build/linux/debian_bullseye_amd64-sysroot
Downloading https://commondatastorage.googleapis.com/chrome-linux-sysroot/toolchain/3bdb3503702d35520d101fc5eec9a8ab5353149f/debian_bullseye_amd64_sysroot.tar.xz
Running hooks:  71% (23/32) clang
________ running 'python3 tools/clang/scripts/update.py' in '/stpyv8/v8'
Downloading https://commondatastorage.googleapis.com/chromium-browser-clang/Linux_x64/clang-llvmorg-17-init-3874-g93a2fecc-1.tar.xz .......... Done.
Running hooks: 100% (32/32), done.
Running: git submodule foreach 'git config -f $toplevel/.git/config submodule.$name.ignore all'
Running: git config --add remote.origin.fetch '+refs/tags/*:refs/tags/*'
Running: git config diff.ignoreSubmodules all
Fetching the release tag information
Checkout Google V8 v11.1.277.14
Previous HEAD position was 692d8a972e [wasm-gc] Make GC and inlining configurable by Origin Trial
HEAD is now at ddb3086599 Version 11.1.277.14
Syncing Google V8 code
Updating depot_tools...
using /tmp/goma_unknown as tmpdir
compiler_proxy is not running
Syncing projects: 100% (29/29), done.

________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-spec-tests/tests.tar.gz.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>0> Removed test/wasm-spec-tests/tests...
0> Extracting 399 entries from test/wasm-spec-tests/tests.tar.gz to test/wasm-spec-tests/tests
Downloading 1 files took 10.489721 second(s)
Hook 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-spec-tests/tests.tar.gz.sha1' took 10.55 secs
Running hooks:  40% (13/32) wasm_js
________ running 'python3 third_party/depot_tools/download_from_google_storage.py --no_resume --no_auth -u --bucket v8-wasm-spec-tests -s test/wasm-js/tests.tar.gz.sha1' in '/stpyv8/v8'
0> Downloading<EMAIL_ADDRESS>0> Removed test/wasm-js/tests...
0> Extracting 184 entries from test/wasm-js/tests.tar.gz to test/wasm-js/tests
Downloading 1 files took 5.057477 second(s)
Running hooks:  71% (23/32) clang
________ running 'python3 tools/clang/scripts/update.py' in '/stpyv8/v8'
Downloading https://commondatastorage.googleapis.com/chromium-browser-clang/Linux_x64/clang-llvmorg-16-init-17653-g39da55e8-2.tar.xz .......... Done.
Running hooks: 100% (32/32), done.
Generate build scripts for V8 (v11.1.277.14)
Done. Made 181 targets from 97 files in 337ms
Build V8 with ninja
ninja: Entering directory `out.gn/x64.release.sample'
[1897/1897] AR obj/libv8_monolith.a
building '_STPyV8' extension
creating build/temp.linux-x86_64-cpython-310
creating build/temp.linux-x86_64-cpython-310/src
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/Context.cpp -o build/temp.linux-x86_64-cpython-310/src/Context.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/iostreams/device/file_descriptor.hpp:28,
                 from src/Exception.h:7,
                 from src/Isolate.h:4,
                 from src/Context.h:6,
                 from src/Context.cpp:1:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/Engine.cpp -o build/temp.linux-x86_64-cpython-310/src/Engine.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/python/converter/shared_ptr_to_python.hpp:12,
                 from /usr/include/boost/python/converter/arg_to_python.hpp:15,
                 from /usr/include/boost/python/call.hpp:15,
                 from /usr/include/boost/python/object_core.hpp:14,
                 from /usr/include/boost/python/args.hpp:22,
                 from /usr/include/boost/python.hpp:11,
                 from src/Utils.h:61,
                 from src/Engine.h:8,
                 from src/Engine.cpp:1:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/Exception.cpp -o build/temp.linux-x86_64-cpython-310/src/Exception.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/iostreams/device/file_descriptor.hpp:28,
                 from src/Exception.h:7,
                 from src/Exception.cpp:2:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
In file included from /stpyv8/v8/include/v8-object.h:10,
                 from /stpyv8/v8/include/v8-array-buffer.h:13,
                 from /stpyv8/v8/include/v8.h:24,
                 from src/Utils.h:72,
                 from src/Exception.h:12,
                 from src/Exception.cpp:2:
/stpyv8/v8/include/v8-persistent-handle.h: In static member function ‘static void* ExceptionTranslator::Convertible(PyObject*)’:
/stpyv8/v8/include/v8-persistent-handle.h:116:43: warning: ‘*((void*)(& extractor)+64).v8::PersistentBase<v8::Value>::val_’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  116 |   V8_INLINE bool IsEmpty() const { return val_ == nullptr; }
      |                                           ^~~~
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/Isolate.cpp -o build/temp.linux-x86_64-cpython-310/src/Isolate.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/iostreams/device/file_descriptor.hpp:28,
                 from src/Exception.h:7,
                 from src/Isolate.h:4,
                 from src/Context.h:6,
                 from src/Isolate.cpp:1:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/Locker.cpp -o build/temp.linux-x86_64-cpython-310/src/Locker.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/iostreams/device/file_descriptor.hpp:28,
                 from src/Exception.h:7,
                 from src/Locker.h:3,
                 from src/Locker.cpp:1:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/Platform.cpp -o build/temp.linux-x86_64-cpython-310/src/Platform.o -std=c++17
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/STPyV8.cpp -o build/temp.linux-x86_64-cpython-310/src/STPyV8.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/iostreams/device/file_descriptor.hpp:28,
                 from src/Exception.h:7,
                 from src/STPyV8.cpp:2:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/Utils.cpp -o build/temp.linux-x86_64-cpython-310/src/Utils.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/python/converter/shared_ptr_to_python.hpp:12,
                 from /usr/include/boost/python/converter/arg_to_python.hpp:15,
                 from /usr/include/boost/python/call.hpp:15,
                 from /usr/include/boost/python/object_core.hpp:14,
                 from /usr/include/boost/python/args.hpp:22,
                 from /usr/include/boost/python.hpp:11,
                 from src/Utils.h:61,
                 from src/Utils.cpp:5:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -DBOOST_PYTHON_STATIC_LIB -I/stpyv8/v8/include -I/usr/local/include/python3.10 -c src/Wrapper.cpp -o build/temp.linux-x86_64-cpython-310/src/Wrapper.o -std=c++17
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_gcc_atomic.hpp:14,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:42,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/python/converter/shared_ptr_to_python.hpp:12,
                 from /usr/include/boost/python/converter/arg_to_python.hpp:15,
                 from /usr/include/boost/python/call.hpp:15,
                 from /usr/include/boost/python/object_core.hpp:14,
                 from /usr/include/boost/python/object.hpp:9,
                 from /usr/include/boost/python/tuple.hpp:10,
                 from /usr/include/boost/python/raw_function.hpp:10,
                 from src/Wrapper.cpp:5:
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
      | ^~~~~~~~~~~~~~~~~~~~
/usr/include/boost/detail/iterator.hpp:13:1: note: ‘#pragma message: This header is deprecated. Use <iterator> instead.’
   13 | BOOST_HEADER_DEPRECATED("<iterator>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
g++ -pthread -shared -L/usr/lib -L/usr/lib/x86_64-linux-gnu build/temp.linux-x86_64-cpython-310/src/Context.o build/temp.linux-x86_64-cpython-310/src/Engine.o build/temp.linux-x86_64-cpython-310/src/Exception.o build/temp.linux-x86_64-cpython-310/src/Isolate.o build/temp.linux-x86_64-cpython-310/src/Locker.o build/temp.linux-x86_64-cpython-310/src/Platform.o build/temp.linux-x86_64-cpython-310/src/STPyV8.o build/temp.linux-x86_64-cpython-310/src/Utils.o build/temp.linux-x86_64-cpython-310/src/Wrapper.o -L/stpyv8/v8/out.gn/x64.release.sample/obj/ -L/usr/local/lib -lboost_system -lboost_iostreams -lv8_monolith -lboost_python310 -lrt -o build/lib.linux-x86_64-cpython-310/_STPyV8.cpython-310-x86_64-linux-gnu.so
/usr/bin/ld: cannot find -lboost_python310
collect2: error: ld returned 1 exit status
error: command '/usr/bin/g++' failed with exit code 1

For the images' python:3.9-bulleye and python:3.8-bulleye I got success build.
@buffer looks like it happens only with py310 and py311. Could you please share your opinion?

:\ Current solution is to use golang rogchap.com/v8go. Works excellent out of the box.
Thanks for your time.

Sorry for off topic, but in my opinion people could be found useful information here.
Another approach is to install node and run JS script passing directly as a system command.
as an example of the script.
// prepare env
docuemnt = Object;
document._____ = Object; // etc

var xxx = "your script here"

console.log(xxx);

@buffer thank you for your good job and quickly answer!


Comparison to TransformVariables and Bijectors?

Hi, from the README this looks very similar to TransformVariables, and to some special cases of Bijectors. How is this package different from those? It would be helpful to have some details on this in the README, to help users know which of the three packages is the best fit for their use case.

I confess that I had forgotten that TransformVariables exists, but it does seem to fill a slightly different niche from this package at present, but it's not impossible that there's a way to unify the two packages.
AFAICT the primary conceptual differences are that ParameterHandling.jl is interested in completely arbitrary data structures, whereas TransformVariables.jl is interested specifically in the bijections utilised when working with random variables, and ParameterHandling breaks down into two steps what TransformVariables does in one.
TransformVariables
IIUC, TransformVariables.jl exposes (in addition to a number of transforms, and operations on those transforms) one function for constructing transformations which map from vectors of reals to other data structures, whose values respect certain constraints:
# My understanding based on these docs: https://tamaspapp.eu/TransformVariables.jl/stable/#The-as-constructor-and-aggregations
t = as(T, data...) # "constructor"
t = as(data....) # used for "aggregations"

t is then a callable which maps from dimension(t) to a structured + constrained representation of the data. For example,
as(Real, 0.0, ∞)

maps the real line to the positive reals, and
t = as((μ = asℝ, σ = asℝ₊, τ = asℝ₊, θs = as(Array, 8)))

maps from 11-dimensional Euclidean space to a NamedTuple.
My suspicion is that TransformVariables is in principle able to operate on fairly arbitrary data structures -- my impression is that the current focus is numbers, arrays or numbers, and named tuples.
ParameterHandling
ParameterHandling.jl exposes a two-function API, rather than one:
x_flat, unflatten = flatten(x)
ParameterHandling.value(x)

flatten maps an arbitrary data structure to a vector and a closure (known by convention as unflatten) satisfying:
x_flat isa Vector{<:Real}
unflatten(x_flat) == x

flatten is purely a "rearranging" operation -- it takes a data struture containing numbers and constructs a vector containing those numbers in a deterministic manner. unflatten is the inverse of this "rearranging" operation.
Separately, ParameterHandling.jl defines a collection of things which subtype AbstractParameter. For example
x = positive(5.0)
x isa ParameterHandling.Positive
ParameterHandling.value(x) == 5.0

x represents a positive number. Upon calling positive, 5.0 is mapped to the real line via Bijectors.Log (or something like that), and placed inside a Positive <: AbstractParameter. When ParameterHandling.value is called upon a Positive, Bijectors.exp is called on the wrapped value, and its output returned.

One could implement the example from TransformVariables in ParameterHandling as follows:
# TransformVariables version.
t = as((μ = asℝ, σ = asℝ₊, τ = asℝ₊, θs = as(Array, 8)))

# ParameterHandling vesion.
x_flat, unflatten = flatten((
    μ=5.0,
    σ=positive(2.0),
    τ=positive(1.1),
    θs=randn(8),
))

# The same transformation in either framework.
x_tv = t(x_flat)
x_ph = ParameterHandling.value(unflatten(x_flat))

all(map(isapprox, x_tv, x_ph)) # return true

Notable Differences
These APIs are really quite similar, but there are a few differences. The TransformVariables interface allows one to specify the transform without providing an initial value, whereas ParameterHandling builds the transform from the initial value. For the simple examples above, this distinction isn't particularly important. It's possible that the ParameterHandling interface is a little more convenient in that it provides the initial value in the transformed space, whereas I think you'd have to separately write x_flat = TransformVariables.inverse(t)(x) to get it using TransformVariables.
The ParameterHandling approach has the minor advantage that things like Vector{Float64}s that don't have any particular constraints don't need to have any additional stuff attached to them (no call to as) -- you can just put them in your data structure as-is.
I think the differences start to really show when you consider doing something more compicated like
x = deferred(Normal, 5.0, positive(1.0))
x_flat, unflatten = flatten(x)
ParameterHandling.value(x)

The deferred function constructs a Deferred object which is just another AbstractParameter which eats a callable and its arguments, and whose value is produced by first calling ParameterHandling.value on its arguments, then calling the callable on said arguments. The point of this is to allow the user to work with arbitrary data structures that know nothing about ParameterHandling -- Normal knows nothing about Positive parameters.
Presumably TransformVariables could handle stuff like this with some modification / extension, but I'm not completely sure how you would make sense of things like logdetjacobian etc in that context. Probably there's a reasonable definition.
Conversely, ParameterHandling doesn't have anything to say about logdetjacobian, but it could certainly be extended to do so in cases where it makes sense.
The reason that we went down the route of requiring that you provide us with an actual piece of data to apply flatten and value to in ParameterHandling was because it avoids having to add functionality to specify "this thing will build a transformation which maps from a vector of reals to this type with these dimensions etc". If you actually have a bit of data, you know precisely what structure the transformation should map to.
@cscherrer does this make sense?

Thanks @willtebbutt , this is really helpful. It seem like this approach could make it more flexible about types, so you could put easily use StaticArrays, for example. Is that right?
deferred looks really useful! Very nice way of writing things :)
For calls like positive(2.0), is the value just a way of getting the type, or does it serve another purpose?
Given the similarities to TransformVariables, do you think there is a nice way to have them under a common interface?

The reason that we went down the route of requiring that you provide us with an actual piece of data to apply flatten and value to in ParameterHandling was because it avoids having to add functionality to specify "this thing will build a transformation which maps from a vector of reals to this type with these dimensions etc". If you actually have a bit of data, you know precisely what structure the transformation should map to.

This is great. We're working through some similar issues in MeasureTheory, and I've started working more and more in terms of testvalues, with basically the same motivation.
Thanks for the detailed description!

It seem like this approach could make it more flexible about types, so you could put easily use StaticArrays, for example. Is that right?

Exactly. Indeed, some SparseMatrixCSC functionality was recently added.

For calls like positive(2.0), is the value just a way of getting the type, or does it serve another purpose?

Well in the particular case of positive it really is about the type, but more generally info about the data itself is needed to know how to implement flatten and value.

Given the similarities to TransformVariables, do you think there is a nice way to have them under a common interface?

Probably. You could certainly implement TransformVariables in terms of ParameterHandling -- maybe the converse is true also? I wonder whether @tpapp has any thoughts?


Visual bug

Well, background is a linear gradient with breakpoint at 70% and svg triangle is placed at 70% from bottom. Your browser has to miscalculate something ;/
I'll check it this night :)


Implement MII interface with feature flag

The eth/v2 module of embassy-stm32 currently only supports RMII (reduced media independent interface) interfaces with 9 pins. However some chips only/better support a MII interface with 14 pins. With this PR, I want to propose adding support for MII interfaces to embassy.
Credits to figuring this out go to my colleague @KloolK, who sat down last year and implemented the necessary changes in a commit here for an older version of embassy.
This PR is meant as discussion basis. Introducing MII as a feature was the least noisy to show the necessary changes. However in the current setup, the features are not additive. Having separate structs for MII and RMII may be a better solution.

very nice!
instead of using Cargo features, could you make it into separate new_mii, new_rmii constructors? This makes it consistent with how other drivers work, e.g. uart has new, new_with_rtscts etc, FMC has separate constructors for the amount of bits/banks.

code looks good, can you fix CI?

What is the rcc_h5 config about? I cannot find it in the Cargo.toml of embassy-stm32. There is one part of the code guarded by #[cfg(rcc_h5)], but for my board, it takes the `#[cfg(not(rcc_h5))] path so I cannot even test if the RMII setting is fine there.

they come from here https://github.com/embassy-rs/embassy/blob/main/embassy-stm32/build.rs#L54
in particular rcc_h5 is active on stm32h5 chips.

Thanks for the info @Dirbaio ! I'd like to fix the CI, but I have a hard time reproducing the issue locally. Which steps are necessary to run ci.sh locally? I could not find cargo batch with either cargo install cargo-batch, cargo search cargo-batch or on Google. Running the commands in isolation asks for a nightly compiler due to the out-dir parameter, so feel like there is too much difference between what CI does and how I attempt to reproduce it.
As far as I can tell, the issue in CI stems from the fact that I changed the public API of Ethernet::new only in v2 to the two functions Ethernet::new_rmii and Ehternet::new_mii. Unfortunately, I could not find a combination of cfg directives to make CI happy and without being able to reproduce it locally, I do not want to waste CI minutes by pushing again and again.
Here in the ethernet module, we conditionally include either the v1 or v2 version of the ethernet module implementation. In the test, I tried a few combinations and ultimately settled on this:
#[cfg(not(eth_v2))]
let device = Ethernet::new(
    ...
);

#[cfg(eth_v2)]
let device = Ethernet::new_rmii(
    ...
);

From the error in CI, it looks like the test code tries to use the v1 function Ethernet::new where the module only provides the v2 function Ethernet::new_rmii.:
error[E0599]: no function or associated item named `new` found for struct `embassy_stm32::eth::Ethernet` in the current scope
   --> /ci/code/tests/stm32/src/bin/eth.rs:75:28
    |
75  |     let device = Ethernet::new(
    |                            ^^^ function or associated item not found in `Ethernet<'_, _, _>`

...

error: could not compile `embassy-stm32-tests` (bin "eth") due to previous error
     target: Target(CompileTarget { name: "thumbv7em-none-eabi" })
     features: ["chrono", "eth", "rng", "stm32h563zi"]

I imagine the problem is that the flags passed to build the test binary are different from the flags passed to build the embassy-stm32 library. However I did not find any mention of eth_v2 in the build.rs, Cargo.toml or anywhere outside of the one usage in embassy-stm32/src/eth/mod.rs, thus I am not sure for which test case I should add them (if that is at all the right approach). Do you have a hint?

Which steps are necessary to run ci.sh locally?

cargo install --git https://github.com/embassy-rs/cargo-batch
./ci.sh

Unfortunately, I could not find a combination of cfg directives to make CI happy and without being able to reproduce it locally, I do not want to waste CI minutes by pushing again and again.

CI tells you at the end
error: could not compile `embassy-stm32-tests` (bin "eth") due to previous error
     target: Target(CompileTarget { name: "thumbv7em-none-eabi" })
     features: ["chrono", "eth", "rng", "stm32h563zi"]

so to reproduce
cd tests/stm32
cargo build --release --target thumbv7em-none-eabi --features stm32h563zi

ah yes the issue is the eth_v2 cfgs are only available within the embassy-stm32 crate. so it'll always pick the not(eth_v2) one.
This reveals an inconsistency between v1 and v2 though! and consistency between versions matters. Maybe we should name v1 new_rmii too? or perhaps name the functions in v2 new and new_mii. since RMII seems way more widely used.

or perhaps name the functions in v2 new and new_mii

ended doing this. Also fixed some fun issue with PC2_C pins in stm32-data...
thanks for the PR!


Issue #767: Temporarily disable leaking TCP adapter benchmarks tests

Follows https://github.com/google/benchmark/blob/main/docs/user_guide.md#disabling-benchmarks

Codecov Report
Base: 27.38% // Head: 27.38% // No change to project coverage :thumbsup:

Coverage data is based on head (6f5a613) compared to base (a4eceda).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #777   +/-   ##
=======================================
  Coverage   27.38%   27.38%
=======================================
  Files         132      132
  Lines       31691    31691
  Branches     5083     5083
=======================================
  Hits         8679     8679
  Misses      21907    21907
  Partials     1105     1105

Flag
Coverage Δ

unittests
27.38% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Change schema_migration: true option to ecto_query: :schema_migrations

This pull request, based on this discussion, adds an option to a preload query so that they can be filtered out when using Multi tenancy with foreign keys
This pull request changes the schema_migration: true option to ecto_query: :schema_migration
This change is linked to https://github.com/elixir-ecto/ecto/pull/4503

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Restricting the range according to the initial date chosen.

Added the possibility of having a dynamic range date limit enabled according to the initial date.
For example we want a daterangepicker that when choosing an initial date it will only has available to choose the next 15 days.
Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@googlebot I signed it!


Attempting to follow a BlueSky account from mastodon results in the follow "pending"

See the screenshot. I clicked "follow" on my BlueSky profile from mastodon. Initially it said "following". But when I refresh, it says "pending".

Which Mastodon account did you do this from?

Yes, same happened to me today!

Which Mastodon account did you do this from?

From https://mastodon.social/@sharoz

Can all restrictions about who is allowed to follow an account be removed? I don't see the value in such a limitation.

I'm open to other suggestions on how to filter out spam like https://conspirator0.substack.com/p/federation-and-political-spam !

I understood that the bluesky account sharing posts has to have a display name and profile picture. But a mastodon account that wants to follow it also needs that? Is the reason the mastodon needs to go through the antispam measure in case it wants to reply?
(Not disagreeing with you about antispam measures. Just trying to understand.)

Good question! Yes, the anti-spam measures currently apply to accounts as a whole; BF isn't yet granular on which requirements it imposes for reading vs writing. That could be a good feature request though! I've updated this issue's title to track that.


Database Projects - Add existing file

This PR fixes #14383

In-line with Visual Studio behavior:

SQL files will be automatically added to build <Build Include="..." />
All other files will be added as <None Include="..." />

If the file has been previously excluded, the <Build/None Remove="..." /> will be removed before adding the Include (if necessary).
For SDK-style projects, if the SQL file falls under default glob, no <Build Include="..." /> will be added.

I'll add some steps to the test plans too after this is checked in

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

30 of 38 (78.95%)  changed or added relevant lines in 4 files are covered.
8 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.05%) to 48.252%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-database-projects/src/models/project.ts
24
25
96.0%

extensions/sql-database-projects/src/controllers/projectController.ts
4
11
36.36%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-database-projects/src/controllers/projectController.ts
8
42.38%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
14740

Relevant Lines:
29011

💛  - Coveralls

The "Should handle adding existing items to project" test is failing, so please make sure to fix it before checking in. Thanks!

@kisantia the test failure is fixed. It came from the test case I added for adding existing file from outside the project root. There was nothing wrong with the source code, just had to tweak the test code a bit regarding relative paths and Linux specifics.

@kisantia the test failure is fixed. It came from the test case I added for adding existing file from outside the project root. There was nothing wrong with the source code, just had to tweak the test code a bit regarding relative paths and Linux specifics.

Awesome, glad it just needed a small fix. Should be good to check in then after the PR validation finishes!


Feature/video queue

Related to #22

Added VideoQueue component to queue multiple video sources to run after each other
Fixed some code indentions
Fixed NREX when an otherwise empty event is requested. In that case the state object will be serialized as null and the video property cannot be set on it
Added Example in Example project
Added Readme Example

Thanks for this interesting contribution - I'll hopefully get time to review it within the next couple of days.

Defend your position

Sory i could not resist ...

@SQL-MisterMagoo @JPVenson Pushing this over the finish line would be a great addition to this amazing library.  I recently upgraded my solution from .net 5 to .net 8 and the control is still going strong!  I appreciate all time and hardwork dedicated to this library.

Thanks for the additional features

Yaaay


Feature/add guild onboarding

Summary
This PR is supposed to add guild onboarding functionality
Checklist

[x] I have run nox and all the pipelines have passed.
[ ] I have made unittests according to the code I have added/modified/deleted.

Related issues

I've implemented classes & routes
TODO:

[ ] Add missing AuditLogActionType's
[ ] Add missing AuditLogChangeKey's
[ ] Add utility functions in the classes (roles field instead of role_ids, etc)
[ ] special endpoint for GuildOnboarding, making it easier to edit/create guild onboardings
[ ] adding tests

Just to make this clear, this is far from finished.

Does someone have an idea what the hell this is i couldn't figure out to do a DROPWDOWN prompt. is this not doable with the guild settings ui and is api only?

Does someone have an idea what the hell this is ? Icouldn't figure out how to do a DROPWDOWN prompt. is this not doable with the guild settings ui and is api only?

At the moment a Dropdown prompt will be used if you have more then 12 prompts. Its automatically set by discord and cannot be directly changed, only by changing the amount of prompts.


Check Google Play Console report about compatibility with Android

All the warning are coming from within the Android WebView.(mostly from org.chromium.content.browser.selection classes).
Cordova team does not think that anything could be fixed on cordova level.
Both Android and Chromium are made by Google team, the proposal is to wait next patch and keep moitoring their issues.
https://stackoverflow.com/questions/51988819/android-p-api-28-what-does-the-strictmode-policy-violation-smartselectionev
https://github.com/apache/cordova-android/issues/737


111raw

Source name
111raw
Source link
https://111raw.com/
Source language
japanese
Other details
No response
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I will fill out all of the requested information in this form.

duplicate of #284


Command errored out when installing modred

python version 3.7.0
numpy version 1.17.4
Platform: windows
pip install modred
Collecting modred
Using cached https://files.pythonhosted.org/packages/ff/d9/9b65b1ffee0015b7191c63da691f9899e13f23728fc40449206e2f96e470/modred-2.0.4.post6.tar.gz
ERROR: Command errored out with exit status 1:
command: 'c:\users\XXXX\appdata\local\programs\python\python37-32\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\XXXX\AppData\Local\Temp\1\pip-install-k4ro1oo_\modred\setup.py'"'"'; file='"'"'C:\Users\XXXX\AppData\Local\Temp\1\pip-install-k4ro1oo_\modred\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base 'C:\Users\XXXX\AppData\Local\Temp\1\pip-install-k4ro1oo_\modred\pip-egg-info'
cwd: C:\Users\XXXX\AppData\Local\Temp\1\pip-install-k4ro1oo_\modred
Complete output (5 lines):
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\XXXX\AppData\Local\Temp\1\pip-install-k4ro1oo_\modred\setup.py", line 20, in
if any(w in ['*a', '*alpha'] for w in parsed_version):
TypeError: 'Version' object is not iterable
----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

I have met the same error. How can I fix this?

I have met the same error. How can I fix this?

There is something wrong with the current setup.py on PyPI.  We have fixed it, but have not put out the new release yet.  You should install from source for now.  Clone the git repo and follow the instructions for installing from source (basically, you need to run python setup.py install).  That should work.  You may also want to build the new documentation, which will reflect other changes made in the codebase for this upcoming release.

There is something wrong with the current setup.py on PyPI.  We have fixed it, but have not put out the new release yet.  You should install from source for now.  Clone the git repo and follow the instructions for installing from source (basically, you need to run python setup.py install).  That should work.  You may also want to build the new documentation, which will reflect other changes made in the codebase for this upcoming release.


add new ssh host: all the '' disappeared

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.74.3
OS Version: win 10

Steps to Reproduce:

ctrl + shift + p
type 'remote ssh: connect to host'
select 'add new ssh host'
input 'ssh -i C:\Users\jiangying.ssh\mypem.pem<EMAIL_ADDRESS>
you will see all the  '' all disappeared

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.75.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

You will have to escape the \, just as you would in a shell

You will have to escape the \, just as you would in a shell

I don't need to in powershell, just type ssh -i C:\Users\jiangying.ssh\mypem.pem<EMAIL_ADDRESS>and enter


Connecting jtag to the 10x2 headers

Hello good people,
I have been working on a project using esp32 and debugging works great when i use the adbus (20pins internal row) using the ft2232hl v3 board, However when i try to hook up jtag to the external (10x2 row, bdbus) header, the led4 is glowing red and openocd is unable to locate the device.. i have tried hooking up the minimal setup; tdo, tdi, tms, tck, gnd and vcc and also tried adding the reset and the vtref but to no avail, is this a hardware configuration issue or maybe an openocd one? do i need to tell the driver/openocd to use the bdbus instead somehow?
the led4 seem to turn on red only when i connect the TDI pin, hopes this help
Would love to get some assistant regrading this issue or maybe understand what am i doing wrong
Best regards

my bad, had to change it in the openocd cfg, seems to be working now, however both leds are now active for some reason (which is not the same behavior as using the adbus)


Bring back the support for arrow-rs

While implementing a data source for DataFusion, I found this great library.
Unfortunately v0.5.0 does not support the list type, v0.6.0 added the support for lists and others but arrow2 is incompatible with DataFusion.
Until arrow-rs and arrow2 are merged, can you consider supporting arrow-rs or provide some compat utility to convert between arrow's RecordBatch and arrow2's Chunk?
https://docs.rs/datafusion/latest/datafusion/physical_plan/trait.RecordBatchStream.html

@elbaro Thanks for your comment. Re-adding arrow support again is definitely on my mental todo list. However, the non-semver compliance and very frequent releases of arrow-rs creates all kinds of work. I have not yet decided how to handle this.
In the meantime you could try to first build the arrow2 arrays and then convert them to arrow arrays via the FFI interface. Without having tested it you should be able to chain together these functions:

arrow2::ffi::export_field_to_c
arrow2::ffi_export_array_to_ce
arrow::ffi::ArrowArray::new

Something along the lines:
fn convert_arrow2_to_arrow(array: Box<dyn Array>, field: &Field) -> arrow::ffi::ArrowArray {
  let array = arrow2::ffi::export_array_to_c(array);
  let schema = arrow2::ffi::export_field_to_c(field);

  let array = unsafe { std::mem::transmute<_, arrow::ffi::FFI_ArrowArray>(array) };
  let schema = unsafe { std::mem::transmute<_, arrow::ffi::FFI_ArrowSchema>(schema) };

  arrow::ffi::ArrowArray::new(array, schema)
}

You can find a fully worked example how to build a record batch from arrow2 arrays here.

Thanks! With the example code I managed to export Rust types to datafusion.
struct A {
    f1: i64,
    f2: u32,
    f3: String,
    f4: Vec<u64>,
}
let items = vec![
    A {
        f1: 123,
        f2: 777,
        f3: "aaa".to_string(),
        f4: vec![100, 200, 300],
    },
    A {
        f1: 456,
        f2: 888,
        f3: "bbb".to_string(),
        f4: vec![400, 500, 600],
    },
];
let fields = serialize_into_fields(&items, TracingOptions::new())?;
let arrays = serialize_into_arrays(&fields, &items)?;

let batch = convert_to_record_batch(arrays, &fields)?;
let ctx = SessionContext::new();
ctx.register_batch("table1", batch)?;
let df = ctx.sql("SELECT * FROM table1").await?;
df.show().await?;

+-----+-----+-----+-----------------+
| f1  | f2  | f3  | f4              |
+-----+-----+-----+-----------------+
| 123 | 777 | aaa | [100, 200, 300] |
| 456 | 888 | bbb | [400, 500, 600] |
+-----+-----+-----+-----------------+

Implemented in serde_arrow=0.6.0-rc.2

@elbaro would you be up for an experiment?  I just published serde_arrow=0.6.0-rc.2 with direct support for arrow serialization. You need to select the arrow version you would like to use by using the corresponding feature arrow-35 or arrow-36. Then you can use serde_arrow::arrow::*. I will include a link to the docs, once they are built.

        let fields = serde_arrow::arrow::serialize_into_fields(
            &items,
            serde_arrow::schema::TracingOptions::new(),
        )?;
        let arrays = serde_arrow::arrow::serialize_into_arrays(&fields, &items)?;
        let batch = ::arrow::record_batch::RecordBatch::try_new(
            Arc::new(::arrow::datatypes::Schema::new(fields)),
            arrays,
        )?;

produced
Error:
   0: Invalid argument error: column types must match schema types, expected
LargeList(Field { name: "element", data_type: UInt64, nullable: false, dict_id: 0, dict_is_ordered: false, metadata: {} }) but found
LargeList(Field { name: "item", data_type: UInt64, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} }) at column index 3

manually setting nullable to true of false didn't change the error.
fields = fields.into_iter().map(|f| f.with_nullable(true or false)).collect();

Thanks a lot for trying it out. This was super helpful: I added additional checks for the data types to the tests and there are issues in multiple places.

I pushed v0.6.0-rc.3 with quite a bit of fixes. Now null handling should be more robust (and better tested).  At least in my tests your issues should be fixed.

rc3 worked for the example. Option<> also worked.
struct A {
    f1: i64,
    f2: Option<u32>,

Field { name: "f1", data_type: Int64, nullable: false, dict_id: 0, dict_is_ordered: false, metadata: {} },
Field { name: "f2", data_type: UInt32, nullable: true, dict_id: 0, dict_is_ordered: false, metadata: {} },

Thanks for testing and the feedback!


Ego-centric information from all sumo vehicles

Possible solution could be putting sensors on sumo vehicles and record the observations of them (according to Tucker).
We can provide one example that records ego-centric information from only one sumo vehicle for @YuechengLiu first, then maybe we record all of them later.

I realize that in this example https://github.com/huawei-noah/SMARTS/blob/master/examples/observation_collection_for_imitation_learning.py, it has been able to get observations for the sumo-controlled vehicles. Thanks!

Confirmed with @YuechengLiu , the current observation_collection_for_imitation_learning.py has already satisfied their use case, closing this issue now


Add an 'EntityTableColumn' component that for easier Table Entity creation

Proposed Feature
After pushing #33 into PR, I realized that there is a helpful change that could be made to the tables. Instead of trying to put the change onto that PR, I decided to make another issue for it. Basically, I want to reduce the amount of props that are on the table and make it easier to customize the columns in the table.
Figma Link: https://www.figma.com/design/pEKOr5N9RJqUNwGoFGXN1Q/Mockups?node-id=82-33&t=Lx76vdymKdNlyPqh-1
Acceptance Criteria

[ ] The component should be located at src/components/entityTable/EntityTableHeader
[ ] Make sure all features are well documented with JSDoc. Here is a guide for more info.
[ ] Make sure that the headers contribute to the table's archetype.
[ ] Move all header based options to the EntityTableHeader props.

This issue has been merged into #33 and will be apart of that PR. Closing issue.


Ambiguous use of 'placeholderText'

I am getting this Ambiguous use of 'placeholderText' when I try to set the placeholderText from code.

Hello @jerryOkafor
What PinCodeTextField's version do you use?


Docusaurus

Pull request checklist
Switching to docusaurus
Before creating the PR
Make sure that:

[ ] You've read the contribution guidelines.
[ ] You've previewed your changes locally.

Describe the change

Issue fixed

Impacted parts

For content changes:

[ ] Documentation content
[ ] Documentation page organization

For tool changes:

[ ] Github Actions workflow
[ ] Build and QA tools (for example, lint or vale)
[ ] MkDocs configuration
[ ] GitHub integration

After creating your PR and tests have finished
Make sure that:

[ ] You've fixed any issues raised by the tests.
[ ] You've previewed your changes (see preview link added in the PR comments)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: bgravenorst:x: EzzahhhYou have signed the CLA already but the status is still pending? Let us recheck it.


ETags are wrong when serving files from the Nix store with nginx

Describe the bug
#48337 doesn't seem to have properly fixed the bug; the ETag appears to be shared between all files of the same derivation.
To reproduce
emily@renko ~> curl -sI https://mew.build/ | grep etag
etag: "iqhlq2b7rmki16cgyf1ll2wiimb6fk6x"
emily@renko ~> curl -sI https://mew.build/notes.html | grep etag
etag: "iqhlq2b7rmki16cgyf1ll2wiimb6fk6x"

Expected behaviour
Distinct ETags for distinct paths.

@yegortimoshenko I can't figure out why this would be happening from looking at the #48337 code; could you take a look at this? Happy to provide whatever debugging context is needed.

ETags are per-resource, at least as far as I understand RFC 7232, which speaks in terms of target resources:

Conditional request preconditions are based on the state of the
target resource as a whole (its current value set) or the state as
observed in a previously obtained representation (one value in that
set). [...]

In which case, if true, it shouldn't matter if all resources share the same ETag (this patch is using Nix store hash as ETag, BTW). Do you run into any issues with the current behavior?

That makes sense, on second thought, given that it's usually derived from the mtime... I can imagine clients being broken enough to globally cache based on it, but I haven't experienced it yet in practice.
My preferred approach would be to just hash the entire Nix store path, which would ensure a more unique ETag without meaningful overhead, but the current approach is probably fine.


ISPN-13606 Fix NPE in PooledConnectionDeployIT

https://issues.redhat.com/browse/ISPN-13606

merged! thanks @tristantarrant !


Slang Module Name management for filament

Use Slang to rename modules deterministically rather than using the hacky obfuscation tactic

Currently has a lot of generated files so I'm assuming not ready for review

We could consider using Morty: https://github.com/pulp-platform/morty


Modify interface of generating sql tokens

Ref #2732

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Pull Request Test Coverage Report for Build 8918

19 of 24 (79.17%)  changed or added relevant lines in 8 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.002%) to 62.577%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-rewrite/src/main/java/org/apache/shardingsphere/core/rewrite/SQLRewriteEngine.java
8
9
88.89%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/wrapper/PreparedStatementExecutorWrapper.java
0
2
0.0%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/communication/jdbc/wrapper/StatementExecutorWrapper.java
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-orchestration/sharding-orchestration-core/src/main/java/org/apache/shardingsphere/orchestration/internal/util/IpUtils.java
3
76.0%

Totals

Change from base Build 119:
0.002%

Covered Lines:
8605

Relevant Lines:
13751

💛  - Coveralls


Removal of selector and pathValues with slight get clean-up.

This removes the selector and path values.  Most of the edits were to the unit tests.

#368 #453


Importing into 2020.1.6f1 causes pink material with no errors

Any idea what could be going on here? HDRP 8.2.0

Well, 2020 is a whole different thing. Didn't try it on 2020 yet so can't comment but pink material means shader compilation error.  Could there be a problem or an inconsistency with your Shader Graph version rather than HDRP version? Or maybe if you open the shader in shader graph and try to see any errors in there?
As I said, not sure :)

Ah so I checked this again, looks like it's throwing Assertion failed on expression: '0 == m_CurrentBufferBindMask[kUnityPerDraw]'
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr, Boolean&)

Nevermind I found the issue, the unity package doesn't include the 3WaveGenerator so the Water shader graph can't find that sub graph.

I cannot seem to find anything about this generator. Can you paste a link here?

It’s not in the Unity package - it’s under the shaders directory. You need to download it from there.


Fixed #33450 -- Made integer primary keys no longer cast to UUID when filtering a GenericRelation on a model with a UUID primary key.

It closes ticket 33450
This issue was related to when attempting to filter on a model that had a GenericRelation whose primary key was not the usual default primary key type of BigAutoField (in the bug report a UUIDField was being used as the primary key instead).
The ticket suggests the casting was the issue however after further investigation it was casting correctly but when it was being applied was incorrect. The ORM was using TTag's primary key type instead of TIntegration's type (which is the default BigAutoField). This still filtered correctly on SQLite but it would still show the query value as<PHONE_NUMBER>01.
All tests pass under SQLite by simply running runtests.py in the tests directory.

@jdboisvert Do you have time to keep working on this?

Closing due to inactivity.


new feature filter by category

filtered by category button

Thank you for your contribution, @mahdanidn! @all-contributors please add @mahdanidn as code.


add use_orig_params to FullyShardedDataParallelPlugin

What does this PR do?

Fixes #1161

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Can this option be initialized by passing fsdp_use_orig_params = true  in the config file? E.g.
fsdp_config:
  ...
  fsdp_use_orig_params: true


Clarify which Service Account Labels and Annotations are required

Is your feature request related to a problem? Please describe.
Kinda. With the recent v1.0.0 breaking change of making azure.workload.identity/use required in a Pod but optional in a Service Account, the documentation was modified by adding a Required column in some tables, but I think, to make things clear/consistent, that it needs to be added in all the other tables too.
Describe the solution you'd like
All the Service Account Labels and Annotations tables should have a "Required" column to make it clear which labels and annotations are required.
That would make all the tables consistent with each others.
Describe alternatives you've considered
Additional context

Closed with https://github.com/Azure/azure-workload-identity/pull/860


[wip] refactor - split + test + add blocked/manual states

WIP
pytest plugins like the manual marker one add manual/blocked outcomes
lets account for them here

closing in for #33


OCPBUGS-11383: Sync proxy TrustedCA to guest cluster

What this PR does / why we need it:

Sync Proxy TrustedCA ConfigMap to guest cluster
Add proxy TrustedCA to MachineConfigServer trusted bundle
Append proxy TrustedCA to oauth master CA bundle

This PR is a split from https://github.com/openshift/hypershift/pull/2240, but without the e2e test which was failing due to an incorrect configuration of the test proxy server.
This should be followed up by a new PR with an e2e to validate proxy setup works with a TrustedCA once a solution is found.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #OCPBUGS-11383
Checklist

[ ] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

Can you please link the OCP bug this fixes and use the HCP for the follow up to automate e2e.
Can you please also add to the PR desc the reason with split both in two separate PRs?
/approve

/jira refresh

/cherry-pick release 4.13

/cherry-pick release-4.12


Need to know if a screen was presented form a "More" tab in a UITabBarController

Thoughts on adding a method that tells the user if a Screen was presented from the "More" tab in a UITabBarController?
Basically:
def more?
   self.parentViewController.is_a?(UIMoreNavigationController)
end

Thoughts on the name of the method? This will likely be untestable :cry:

Will self.parentViewController always be present, or should we protect against nil ? Otherwise, I'm good with this.


Do not check for metadata during schema comparison

Signed-off-by: remzi<EMAIL_ADDRESS>close #4660
Just to keep resolveRelation in sync with Spark's code

build

build


Differences in Heroku behavior

I'm trying to deploy a new staging environment with the buildpack. However, it is not working as throws error "Selenium::WebDriver::Error::UnknownError (invalid argument: can't kill an exited process)", despite I have the same configuration on both heroku machines. They have the same Firefox, Ubuntu and Geckodriver version.
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.4 LTS
Release:	18.04
Codename:	bionic

Looking at the build log, I noticed some differences in the libraries installed (see here highlighted differences). Why are they not installing the same libraries? How can we be sure to install correctly all of them?

I was able to fix the problem installing a buildpack
heroku buildpacks:add --index 1 heroku-community/apt
and creating an Aptfile that include the following libraries
libcairo2 libcairo-gobject2 libxt6 libsm6 libice6 libgtk-3-0

HI @arsandov, I'm running into the same error, and I was hoping to confirm whether it was the same issue you had.
In your highlighted differences, is the left side your original production environment, and the right side your new staging environment?
Appreciate if you're able to confirm :)

Hey @RishiHQ! I'm happy to help you. Actually, left side is set as production. The solution used to install the buildpack was the same than above. However, at the moment I wrote this issue we didn't notice that because it was one out dozens things we tried on production until it worked, and even after removing the "heroku-community/apt" buildpack and the "Aptfile", new deployments with "heroku-integrated-firefox-geckodriver" (left side) kept installing these dependencies without our knowledge.

@RishiHQ I will update my answer. We set a new environment and again faces some issue, now I found the problem source, this buildpack doesn't install Firefox dependencies, I noticed looking at this https://github.com/thopd88/heroku-buildpack-firefox/blob/master/bin/compile#L59 so, adding the complete list in the Aptfile that is used by
heroku buildpacks:add --index 1 heroku-community/apt
fixed the issue. Here is the list of dependencies I added:
libappindicator1 libasound2 libatk1.0-0  libatk-bridge2.0-0 libcairo-gobject2 libgconf-2-4 libgtk-3-0 libice6 libnspr4 libnss3 libsm6 libx11-xcb1 libxcomposite1 libxcursor1 libxdamage1 libxfixes3 libxi6 libxinerama1 libxrandr2 libxss1 libxt6 libxtst6 fonts-liberation

Hi @arsandov,
I would like to thank you from the bottom of my heart. For some reason, I lost this thread, but on re-discovering it (with on and off debugging for 2 months), I have gotten this to work!
Thank you!

@arsandov thanks for posting the issue. The latest compile includes the relevant libraries needed. You can avoid installing multiple buildpacks and keep your heroku slug size to a minimum.