Lanelet2 import not working inside ros2 docker environment

Hi,
Unfortunately i get the following errors when I try to execute the python3 -c "import lanelet2" inside the docker environment with ROS2 (Foxy).
After building the image running the command docker run -it lanelet2:1.2.0 /bin/bash -c "source /home/developer/workspace/install/setup.bash && python3 -c \"import lanelet2\"" results in the same errors.
The Following ARGs are set in the Dockerfile:
DISTRIBUTION=20.04
ROS_DISTRO=foxy
ROS=ros2
DEV=1

The host machine is running Ubuntu 20.04 as well.
Hopefully you can help me circumvent this issue.
Kind regards
Valentin
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'

From a quick glance, the lanelet2 dockerfile does not contain the build config to generate python bindings by default, you would need to build lanelet2 with
catkin config --cmake-args -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPYTHON_VERSION=<python version>
(you can also find this command in the readme under the section "Python3")

Thank you for answering.
I added the flags and unfortunately there were already warnings while building.
The command I ran was colcon build --cmake-args -DCMAKE_BUILD_TYPE=Debug -DMRT_SANITIZER=checks -DMRT_ENABLE_COVERAGE=1 -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPYTHON_VERSION=3.8.
colcon build --cmake-args -DCMAKE_BUILD_TYPE=Debug -DMRT_SANITIZER=checks -DMRT_ENABLE_COVERAGE=1 -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPYTHON_VERSION=3.8

Starting >>> mrt_cmake_modules
--- stderr: mrt_cmake_modules
CMake Warning:
  Manually-specified variables were not used by the project:

    CATKIN_INSTALL_INTO_PREFIX_ROOT
    MRT_ENABLE_COVERAGE
    MRT_SANITIZER

---

Finished <<< mrt_cmake_modules [0.60s]
Starting >>> lanelet2_core

--- stderr: lanelet2_core
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_core/test/test_area.cpp: In constructor ‘TestArea::TestArea()’:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_core/test/test_area.cpp:29:3: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
   29 |   TestArea() {
      |   ^~~~~~~~
---

[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
[Processing: lanelet2_core]
Finished <<< lanelet2_core [8min 13s]
Starting >>> lanelet2_io
Starting >>> lanelet2_traffic_rules
Starting >>> lanelet2_maps
Finished <<< lanelet2_maps [0.94s]
[Processing: lanelet2_io, lanelet2_traffic_rules]
Finished <<< lanelet2_traffic_rules [59.1s]
Starting >>> lanelet2_routing
[Processing: lanelet2_io, lanelet2_routing]
Finished <<< lanelet2_io [1min 53s]
Starting >>> lanelet2_projection
Finished <<< lanelet2_projection [15.0s]
Starting >>> lanelet2_matching
--- stderr: lanelet2_routing
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_lanelet_or_area_path.cpp: In member function ‘virtual void LaneletOrAreaTest::SetUp()’:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_lanelet_or_area_path.cpp:26:8: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
   26 |   void SetUp() override {
      |        ^~~~~
In file included from /home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_visualization.cpp:7:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h: In member function ‘void lanelet::routing::tests::RoutingGraphTestData::initLineStrings()’:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h:230:8: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
  230 |   void initLineStrings() {
      |        ^~~~~~~~~~~~~~~
In file included from /home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_graph_container.cpp:7:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h: In member function ‘void lanelet::routing::tests::RoutingGraphTestData::initLineStrings()’:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h:230:8: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
  230 |   void initLineStrings() {
      |        ^~~~~~~~~~~~~~~
In file included from /home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_route.cpp:5:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h: In member function ‘void lanelet::routing::tests::RoutingGraphTestData::initLineStrings()’:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h:230:8: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
  230 |   void initLineStrings() {
      |        ^~~~~~~~~~~~~~~
In file included from /home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_relations.cpp:6:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h: In member function ‘void lanelet::routing::tests::RoutingGraphTestData::initLineStrings()’:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h:230:8: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
  230 |   void initLineStrings() {
      |        ^~~~~~~~~~~~~~~
In file included from /home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing.cpp:9:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h: In member function ‘void lanelet::routing::tests::RoutingGraphTestData::initLineStrings()’:
/home/developer/workspace/src/lanelet2/lanelet2/lanelet2_routing/test/test_routing_map.h:230:8: note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without
  230 |   void initLineStrings() {
      |        ^~~~~~~~~~~~~~~
---

[Processing: lanelet2_matching, lanelet2_routing]
[Processing: lanelet2_matching, lanelet2_routing]
[Processing: lanelet2_matching, lanelet2_routing]
Finished <<< lanelet2_routing [3min 9s]
Starting >>> lanelet2_validation
Finished <<< lanelet2_validation [29.5s]
Finished <<< lanelet2_matching [2min 37s]
Starting >>> lanelet2_python
[Processing: lanelet2_python]
[Processing: lanelet2_python]
[Processing: lanelet2_python]
[Processing: lanelet2_python]
[Processing: lanelet2_python]
Finished <<< lanelet2_python [2min 55s]
Starting >>> lanelet2_examples
[Processing: lanelet2_examples]
Finished <<< lanelet2_examples [33.1s]
Starting >>> lanelet2
--- stderr: lanelet2
CMake Warning:
  Manually-specified variables were not used by the project:

    MRT_ENABLE_COVERAGE
    MRT_SANITIZER

---

Finished <<< lanelet2 [0.63s]

Summary: 12 packages finished [16min 27s]
  4 packages had stderr output: lanelet2 lanelet2_core lanelet2_routing mrt_cmake_modules

Trying to import by calling python3 -c "import lanelet2" again results in the same errors.
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct pointer_iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct extended_type_info_typeid'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct oserializer'
/usr/include/boost/serialization/singleton.hpp:181:12: runtime error: reference binding to null pointer of type 'const struct iserializer'

I already tried rebuilding twice. Each time ending in the same result.
Here are the contents of my current Dockerfile
# The ubuntu distro to use
ARG DISTRIBUTION=20.04
FROM ubuntu:${DISTRIBUTION} AS lanelet2_deps

# Select the ros distro
ARG ROS_DISTRO=foxy

# The ros version of that distro (either ros or ros2)
ARG ROS=ros2

# If true, build docker container for development
ARG DEV=1

SHELL ["/bin/bash", "-c"]

# basics
RUN set -ex; \
    if [ "${ROS_DISTRO}" = "melodic" ] || [ "${ROS_DISTRO}" = "kinetic" ]; \
        then export PY_VERSION=python; \
        else export PY_VERSION=python3; \
    fi; \
    if [ "$DEV" -ne "0" ]; then \
        export DEV_PACKAGES="clang-format-11 clang-tidy-11 clang-11 i${PY_VERSION} nano lcov"; \
    fi; \
    apt-get update && \
    DEBIAN_FRONTEND=noninteractive apt-get install -y \
        bash-completion \
        build-essential \
        curl \
        git \
        cmake \
        keyboard-configuration \
        locales \
        lsb-core \
        lib${PY_VERSION}-dev \
        software-properties-common \
        sudo \
        wget \
        ${DEV_PACKAGES} && \
    locale-gen en_US.UTF-8 && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*

# locale
ENV LANG=en_US.UTF-8 \
    LANGUAGE=en_US:en \
    LC_ALL=en_US.UTF-8 \
    ROS_DISTRO=${ROS_DISTRO} \
    ROS=${ROS} \
    DEV=${DEV}

# install ROS
RUN set -ex; \
    export KEY_FILE=/usr/share/keyrings/ros-archive-keyring.gpg && \
    curl -sSL https://raw.githubusercontent.com/ros/rosdistro/master/ros.key -o $KEY_FILE && \
    echo "deb [signed-by=$KEY_FILE] http://packages.ros.org/${ROS}/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros.list

# dependencies for lanelet2
RUN if [ "${ROS_DISTRO}" = "melodic" ] || [ "${ROS_DISTRO}" = "kinetic" ]; \
        then export PY_VERSION=python; \
        else export PY_VERSION=python3; \
    fi; \
    apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y \
        libgtest-dev \
        libboost-all-dev \
        libeigen3-dev \
        libgeographic-dev \
        libpugixml-dev \
        libboost-python-dev \
        ${PY_VERSION}-rospkg \
        ros-$ROS_DISTRO-ros-environment && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*

# ros version specific dependencies
RUN set -ex; \
    if [ "${ROS_DISTRO}" = "melodic" ] || [ "${ROS_DISTRO}" = "kinetic" ]; \
        then export PY_VERSION=python; \
        else export PY_VERSION=python3; \
    fi; \
    if [ "$ROS" = "ros" ]; \
        then export ROS_DEPS="ros-$ROS_DISTRO-catkin ros-$ROS_DISTRO-rosbash ${PY_VERSION}-catkin-tools"; \
        else export ROS_DEPS="ros-$ROS_DISTRO-ament-cmake python3-colcon-ros ros-$ROS_DISTRO-ros2cli"; \
    fi; \
    apt-get update && \
    DEBIAN_FRONTEND=noninteractive apt-get install -y $ROS_DEPS && \
    apt-get clean && \
    rm -rf /var/lib/apt/lists/*

# create a user
RUN useradd --create-home --groups sudo --shell /bin/bash developer && \
    mkdir -p /etc/sudoers.d && \
    echo "developer ALL=(ALL) NOPASSWD: ALL" > /etc/sudoers.d/developer && \
    chmod 0440 /etc/sudoers.d/developer

# environment, dependencies and entry points
RUN apt-get update
RUN apt-get install -y python3-colcon-common-extensions
USER developer

ENV HOME /home/developer
WORKDIR /home/developer/workspace

RUN set -ex; \
    sudo chown -R developer:developer /home/developer && \
    if [ "$ROS" = "ros" ]; then export SPACE="devel"; else export SPACE="install"; fi; \
    echo "export ROS_HOSTNAME=localhost" > /home/developer/.bashrc && \
    echo "source /opt/ros/$ROS_DISTRO/setup.bash" >> /home/developer/.bashrc && \
    echo "source /home/developer/workspace/${SPACE}/setup.bash || true" >> /home/developer/.bashrc

# setup workspace, add dependencies
RUN set -ex; \
    cd /home/developer/workspace && \
    mkdir -p /home/developer/workspace/src && \
    if [ "$ROS" = "ros" ]; then \
      source /home/developer/.bashrc && \
      catkin init; \
    fi; \
    git clone https://github.com/KIT-MRT/mrt_cmake_modules.git /home/developer/workspace/src/mrt_cmake_modules

# second stage: get the code
FROM lanelet2_deps AS lanelet2_src

# bring in the code
COPY --chown=developer:developer . /home/developer/workspace/src/lanelet2

# update dependencies
RUN git -C /home/developer/workspace/src/mrt_cmake_modules pull

# third stage: build
FROM lanelet2_src AS lanelet2

# build
RUN set -ex; \
    if [ "$DEV" -ne "0" ]; then \
      export CMAKE_ARGS="-DCMAKE_BUILD_TYPE=Debug -DMRT_SANITIZER=checks -DMRT_ENABLE_COVERAGE=1 -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPYTHON_VERSION=3.8"; \
    else \
      export CMAKE_ARGS="-DCMAKE_BUILD_TYPE=Release -DCMAKE_BUILD_TYPE=RelWithDebInfo -DPYTHON_VERSION=3"; \
    fi; \
    if [ "$ROS" = "ros" ]; then \
      export CONFIGURE="catkin config --cmake-args $CMAKE_ARGS"; \
      export BUILD_CMD="catkin build --no-status"; \
    else \
      export CONFIGURE=true; \
      export BUILD_CMD="colcon build --cmake-args $CMAKE_ARGS"; \
    fi; \
    source /opt/ros/$ROS_DISTRO/setup.bash && \
    env && \
    $CONFIGURE && \
    $BUILD_CMD && \
    if [ "$DEV" -eq "0" ]; then \
      rm -rf build logs; \
    fi

Maybe you have another idea?

The "issue" is related to you building the docker container in DEV=1 mode. This causes a debug build in which gcc's sanitizers are enabled. This is good for checking for memory issues or potential undefined behavior, but also finds a few false positives (e.g. the ones in boosts serialization library). They should just be warnings and not cancel execution of the code. To get rid of them, simply build with disabled DEV mode.

DEV=0 indeed gets rid of the problem. Thank you very much.
In the meantime I used the ros:foxy-ros-base docker image and installed lanelet2 via PyPi which also worked 👍🏼


[PATCH] RFC1213-MIB::atTable indices are not encoded/resolved correctly

Version: Branch master at commit 0f32c00d89eae2f86b2282ffc50805e059be5492
pysnmp/smi/mibs/RFC1213-MIB.py defines the atNetAddress index of atTable erroneously as IpAddress, while the correct type is NetworkAddress.  Since the two types have different OID encoding (NetworkAddress is equivalent to the modern InetAddressType-InetAddress combo and has an extra octet at the beginning which specifies the address type), PySNMP fails to encode or decode atNetAddress index.
To reproduce:
import pysnmp.debug
from pysnmp.smi.builder import MibBuilder
from pysnmp.smi.view import MibViewController
from pysnmp.smi.rfc1902 import ObjectIdentity
from pysnmp.proto.rfc1155 import IpAddress
from pysnmp.proto.rfc1902 import ObjectName
import user

builder = MibBuilder()
builder.loadModules('RFC1213-MIB')
view = MibViewController(builder)

pysnmp.debug.setLogger(pysnmp.debug.Debug('all'))

ident = ObjectIdentity('RFC1213-MIB', 'atIfIndex', 7, IpAddress('<IP_ADDRESS>'))
ident.resolveWithMib(view)
print(ident.getOid())

ident2 = ObjectIdentity(ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>'))
ident2.resolveWithMib(view)
print(ident2.getMibSymbol())

Results in:
2017-10-06 10:37:45,703 pysnmp: running pysnmp version 4.4.1
2017-10-06 10:37:45,703 pysnmp: debug category 'all' enabled
2017-10-06 10:37:45,792 pysnmp: trying DirMibSource('/Users/eugene.kim/.pysnmp/mibs')
2017-10-06 10:37:45,792 pysnmp: addMibSources: new MIB sources [ZipMibSource('pysnmp/smi/mibs'), ZipMibSource('pysnmp/smi/mibs/instances'), DirMibSource('pysnmp_mibs'), DirMibSource('/Users/eugene.kim/.pysnmp/mibs')]
2017-10-06 10:37:45,792 pysnmp: indexMib: re-indexing MIB view
2017-10-06 10:37:45,795 pysnmp: getNodeNameByOid: resolved :<IP_ADDRESS>.<IP_ADDRESS>.1.1 -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry', 'atIfIndex').()
2017-10-06 10:37:45,795 pysnmp: resolved ('RFC1213-MIB', 'atIfIndex', 7, IpAddress(hexValue='8ff801b1')) into prefix ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.1.1') and suffix ()
2017-10-06 10:37:45,795 pysnmp: getNodeNameByOid: resolved :(1, 3, 6, 1, 2, 1, 3, 1, 1) -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry').()
2017-10-06 10:37:45,795 pysnmp: resolved indices are (Integer32(7), IpAddress(hexValue='8ff801b1'))
<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.248.1.177
2017-10-06 10:37:45,795 pysnmp: resolving <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS> as OID or label
2017-10-06 10:37:45,796 pysnmp: getNodeNameByOid: resolved :<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS> -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry', 'atIfIndex').<IP_ADDRESS>.1.177
2017-10-06 10:37:45,796 pysnmp: resolved (ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>'),) into prefix ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.1.1') and suffix ObjectName('<IP_ADDRESS>.1.177')
2017-10-06 10:37:45,796 pysnmp: getNodeNameByOid: resolved :<IP_ADDRESS>.<IP_ADDRESS>.1.1 -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry', 'atIfIndex').()
2017-10-06 10:37:45,796 pysnmp: resolved prefix ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.1.1') into MIB node MibTableColumn((1, 3, 6, 1, 2, 1, 3, 1, 1, 1), Integer32())
2017-10-06 10:37:45,796 pysnmp: getNodeNameByOid: resolved :(1, 3, 6, 1, 2, 1, 3, 1, 1) -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry').()
Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/Users/eugene.kim/Work/ESI/snmp2es/z.py", line 20, in <module>
    ident2.resolveWithMib(view)
  File "/Users/eugene.kim/venvs/playground36/lib/python3.6/site-packages/pysnmp-4.4.1-py3.6.egg/pysnmp/smi/rfc1902.py", line 450, in resolveWithMib
  File "<string>", line 1223, in getIndicesFromInstId
pysnmp.smi.error.SmiError: Excessive instance identifier sub-OIDs left at MibTableRow((1, 3, 6, 1, 2, 1, 3, 1, 1), None): 177

Note:

The OID-encoded atNetAddress <IP_ADDRESS> lacks the NetworkAddress type selector value 1 at the beginning;
The buggy code could not resolve a correctly encoded index (ident2) because it did not expect the NetworkAddress type selector value before the IP address literal.  What happened instead is: 1) the buggy code erroneously decoded the address as <IP_ADDRESS> (the type selector value plus the first 3 sub-identifiers of the IP address), then 2) raised an exception upon seeing 177, which the last octet of the IP address.

#87 fixes this issue (note: #87 requires etingof/pyasn1#85), to yield correct result:
2017-10-06 10:49:52,165 pysnmp: running pysnmp version 4.4.1
2017-10-06 10:49:52,166 pysnmp: debug category 'all' enabled
2017-10-06 10:49:52,254 pysnmp: trying DirMibSource('/Users/eugene.kim/.pysnmp/mibs')
2017-10-06 10:49:52,254 pysnmp: addMibSources: new MIB sources [ZipMibSource('pysnmp/smi/mibs'), ZipMibSource('pysnmp/smi/mibs/instances'), DirMibSource('pysnmp_mibs'), DirMibSource('/Users/eugene.kim/.pysnmp/mibs')]
2017-10-06 10:49:52,254 pysnmp: indexMib: re-indexing MIB view
2017-10-06 10:49:52,256 pysnmp: getNodeNameByOid: resolved :<IP_ADDRESS>.<IP_ADDRESS>.1.1 -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry', 'atIfIndex').()
2017-10-06 10:49:52,256 pysnmp: resolved ('RFC1213-MIB', 'atIfIndex', 7, IpAddress(hexValue='8ff801b1')) into prefix ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.1.1') and suffix ()
2017-10-06 10:49:52,256 pysnmp: getNodeNameByOid: resolved :(1, 3, 6, 1, 2, 1, 3, 1, 1) -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry').()
2017-10-06 10:49:52,257 pysnmp: resolved indices are (Integer32(7), NetworkAddress().setComponentByPosition(0, IpAddress(hexValue='8ff801b1')))
<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>
2017-10-06 10:49:52,257 pysnmp: resolving <IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS> as OID or label
2017-10-06 10:49:52,257 pysnmp: getNodeNameByOid: resolved :<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS> -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry', 'atIfIndex').<IP_ADDRESS>.1.177
2017-10-06 10:49:52,257 pysnmp: resolved (ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>'),) into prefix ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.1.1') and suffix ObjectName('<IP_ADDRESS>.1.177')
2017-10-06 10:49:52,257 pysnmp: getNodeNameByOid: resolved :<IP_ADDRESS>.<IP_ADDRESS>.1.1 -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry', 'atIfIndex').()
2017-10-06 10:49:52,257 pysnmp: resolved prefix ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.1.1') into MIB node MibTableColumn((1, 3, 6, 1, 2, 1, 3, 1, 1, 1), Integer32())
2017-10-06 10:49:52,257 pysnmp: getNodeNameByOid: resolved :(1, 3, 6, 1, 2, 1, 3, 1, 1) -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry').()
2017-10-06 10:49:52,258 pysnmp: resolved indices are (Integer32(7), NetworkAddress().setComponentByPosition(0, IpAddress(hexValue='8ff801b1')))
('RFC1213-MIB', 'atIfIndex', (Integer32(7), NetworkAddress().setComponentByPosition(0, IpAddress(hexValue='8ff801b1'))))

Note:

The atNetAddress of <IP_ADDRESS> is now correctly encoded as <IP_ADDRESS>.177;
A correctly formatted instance OID is now correctly decoded.

Thank you for your PR!
Do you really need/use the change introduced in https://github.com/etingof/pyasn1/pull/85 ? I do not see where Choice.clone with non-None value is used. Can you please elaborate?

It's actually in MibTableRow.getInstIdFromIndices() which is used for index-to-OID resolution.  Without it, the repro code results in an error:
2017-10-06 14:24:24,090 pysnmp: running pysnmp version 4.4.1
2017-10-06 14:24:24,090 pysnmp: debug category 'all' enabled
2017-10-06 14:24:24,180 pysnmp: trying DirMibSource('/Users/eugene.kim/.pysnmp/mibs')
2017-10-06 14:24:24,180 pysnmp: addMibSources: new MIB sources [DirMibSource('/Users/eugene.kim/Work/ESI/snmp2es/pysnmp/pysnmp/smi/mibs'), DirMibSource('/Users/eugene.kim/Work/ESI/snmp2es/pysnmp/pysnmp/smi/mibs/instances'), DirMibSource('pysnmp_mibs'), DirMibSource('/Users/eugene.kim/.pysnmp/mibs')]
2017-10-06 14:24:24,181 pysnmp: indexMib: re-indexing MIB view
2017-10-06 14:24:24,183 pysnmp: getNodeNameByOid: resolved :<IP_ADDRESS>.<IP_ADDRESS>.1.1 -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry', 'atIfIndex').()
2017-10-06 14:24:24,183 pysnmp: resolved ('RFC1213-MIB', 'atIfIndex', 7, IpAddress(hexValue='8ff801b1')) into prefix ObjectName('<IP_ADDRESS>.<IP_ADDRESS>.1.1') and suffix ()
2017-10-06 14:24:24,183 pysnmp: getNodeNameByOid: resolved :(1, 3, 6, 1, 2, 1, 3, 1, 1) -> ('iso', 'org', 'dod', 'internet', 'mgmt', 'mib-2', 'at', 'atTable', 'atEntry').()
Traceback (most recent call last):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/Users/eugene.kim/Work/ESI/snmp2es/z.py", line 16, in <module>
    ident.resolveWithMib(view)
  File "/Users/eugene.kim/Work/ESI/snmp2es/pysnmp/pysnmp/smi/rfc1902.py", line 505, in resolveWithMib
    instIds = rowNode.getInstIdFromIndices(*self.__args[2:])
  File "<string>", line 1242, in getInstIdFromIndices
TypeError: clone() takes 1 positional argument but 2 were given

This is actually for backward compatibility with SNMPv1: I believe NetworkAddress is the only non-simple ASN.1 type used as a table index, and in SNMPv2 NetworkAddress was replaced by a combination of two simple types (InetAddressType and InetAddress).
The precise use case I am really aiming at is the ability to pass ObjectIdentity with vanilla objects as table indices, e.g. in the example above, the interface ID 7 was specified as a plain int and not as Integer32.  This is internally handled by passing the syntax's clone() method with 7, or actually whichever index value supplied to ObjectIdentity (as the value parameter), as the value parameter.  Since the “value” of a NetworkAddress is an IpAddress, I thought it would make sense to plumb a similar path.
To be technically correct, a Choice has exactly one component, and not a value.  But since that component is singular, I thought it would be sensible to approximate that component to a “value,” even though the concept of a value is apparently only for simple ASN.1 types.

Yes, that makes sense to me.
Given this special treatment of the Choice value, would it make sense to implement NetworkAddress.clone() rather than at Choice.clone()? That way it would be all contained within pysnmp...

That was the original design, then it occurred to me that there may be other Choice-based index types which will require similar cloning logic.
However, after seeing that SNMPv2-SMI now allows only simple-type indices, I agree that we don't need to clutter PyASN1 anticipating something that is already disallowed by the RFC.  :)
I'll update this PR to revert to the original version.  Please disregard the PyASN1 PR.

I agree, that looks less intrusive to me. Thank you!

Commit fd163fe moves clone() to NetworkAddress.

Merged


fix: add configurable evictIdleConnections

Summary

With periodic polling, datafile fetches may fail with timeout intermittently.
Add configurable "evictIdleConnections" to HttpProjectConfigManager to force close persistent connection after idle time (evict after 1min idle time by default).

Test plan
Issues

OASIS-7421

Pull Request Test Coverage Report for Build 1693

28 of 28 (100.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.03%) to 90.377%

Files with Coverage Reduction
New Missed Lines
%

core-httpclient-impl/src/main/java/com/optimizely/ab/HttpClientUtils.java
1
83.33%

Totals

Change from base Build 1690:
0.03%

Covered Lines:
4480

Relevant Lines:
4957

💛  - Coveralls

Pull Request Test Coverage Report for Build 1693

28 of 28 (100.0%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.03%) to 90.377%

Files with Coverage Reduction
New Missed Lines
%

core-httpclient-impl/src/main/java/com/optimizely/ab/HttpClientUtils.java
1
83.33%

Totals

Change from base Build 1690:
0.03%

Covered Lines:
4480

Relevant Lines:
4957

💛  - Coveralls


Fix test run and deprecation warnings

rake test failed with the following error:
W, [2017-03-19T08:04:17.060025 #39975]  WARN -- :       This usage of the Code Climate Test Reporter is now deprecated. Since version
      1.0, we now require you to run `SimpleCov` in your test/spec helper, and then
      run the provided `codeclimate-test-reporter` binary separately to report your
      results to Code Climate.

      More information here: https://github.com/codeclimate/ruby-test-reporter/blob/master/README.md

Followed instructions for setting up codeclimate for v1.
Also addressed deprecation warnings Use assert_nil if expecting nil from ...

@mpapis Sorry to bother you with this, but I am having some trouble getting the tests to run locally and in CI.  I will tell my story below.
First I cloned the repo, bundle installed, and ran rake.  The test run failed with the following message:
W, [2017-03-19T08:04:17.060025 #39975]  WARN -- :       This usage of the Code Climate Test Reporter is now deprecated. Since version
      1.0, we now require you to run `SimpleCov` in your test/spec helper, and then
      run the provided `codeclimate-test-reporter` binary separately to report your
      results to Code Climate.

      More information here: https://github.com/codeclimate/ruby-test-reporter/blob/master/README.md

First I tried pinning the version of codeclimate-test-reporter to be < 1.0 where the breaking change was.  That removed the error and I was able to run the tests.  I was not sure if this was the right path so I removed the version from the Gemfile and followed the upgrade instructions on code climate.  The tests ran after this so I pushed up what I had.
My question here is how do you want to handle the version of codeclimate-test-reporter.  Should I

move it out of the Gemfile and into the gem spec as dev dependency with a version
leave it in the Gemfile without a version and add a Gemfile.lock so the version is pinned until explicitly updated
leave it in the Gemfile and pin it to a version there
some other option I have not listed

The first build on travis (https://travis-ci.org/oauth-xx/oauth-ruby/jobs/212709467) failed all ruby versions with:
Error running 'env GEM_HOME=/home/travis/.rvm/gems/ruby-2.3.0@global GEM_PATH= /home/travis/.rvm/rubies/ruby-2.3.0/bin/ruby -d /home/travis/.rvm/src/rubygems-dd3e10136ae73051a7888955414eea246e85d00b/setup.rb --no-ri --no-rdoc',
showing last 15 lines of /home/travis/.rvm/log/1489938160_ruby-2.3.0/rubygems.install.log
[2017-03-19 15:42:42] /home/travis/.rvm/rubies/ruby-2.3.0/bin/ruby
current path: /home/travis/.rvm/src/rubygems-dd3e10136ae73051a7888955414eea246e85d00b
GEM_HOME=/home/travis/.rvm/gems/ruby-2.3.0
PATH=/home/travis/.rvm/gems/ruby-2.3.0/bin:/home/travis/.rvm/gems/ruby-2.3.0@global/bin:/home/travis/.rvm/rubies/ruby-2.3.0/bin:/home/travis/.rvm/bin:/home/travis/bin:/home/travis/.local/bin:/home/travis/.gimme/versions/go1.4.2.linux.amd64/bin:/usr/local/phantomjs/bin:/home/travis/.nvm/v0.10.36/bin:./node_modules/.bin:/usr/local/maven-3.2.5/bin:/usr/local/clang-3.4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin
GEM_PATH=/home/travis/.rvm/gems/ruby-2.3.0:/home/travis/.rvm/gems/ruby-2.3.0@global
command(8): env GEM_HOME=/home/travis/.rvm/gems/ruby-2.3.0@global GEM_PATH= /home/travis/.rvm/rubies/ruby-2.3.0/bin/ruby -d /home/travis/.rvm/src/rubygems-dd3e10136ae73051a7888955414eea246e85d00b/setup.rb --no-ri --no-rdoc
Exception `LoadError' at /home/travis/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems.rb:1241 - cannot load such file -- rubygems/defaults/operating_system
Exception `LoadError' at /home/travis/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems.rb:1250 - cannot load such file -- rubygems/defaults/ruby
Exception `LoadError' at /home/travis/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55 - cannot load such file -- did_you_mean
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory @ dir_chdir - bundler/lib
The command "rvm rubygems master --force" failed and exited with 1 during .

I did some googling but not much turned up for the error message so I tried removing the step that was causing the error before_install: rvm rubygems master --force.  The next build only ruby 2.2 passed I assume because that is the preloaded ruby or something.  So I looked at the defaults for travis and since we have a gemfile thought we could remove the install step and also saw the default rake task will run the tests and travis runs rake by default so I removed the custom steps to see what would happen.  All builds except the ruby 2.0 passed.  Checking that build (https://travis-ci.org/oauth-xx/oauth-ruby/builds/212731232) it looks like some version of nokogiri is getting included that is not compatible with ruby 2.0.  Figuring it was not an option to stop supporting ruby 2.0 just so we can run tests I rolled back the build changes I made.  Then I went with the first option of pinning codeclimate-test-reporter to a version before 1.0 since that was the setup of the last successful build.  The build failed again with the error above.  I am wondering how you would like to address this.

pin nokogiri to a version that supports ruby 2.0
stop supporting ruby 2.0
some other option I have not listed

Sorry for the long story.  I just wanted to get all the info up here.  I am happy to go any route that works for you.

Hey @jcamenisch, nice catch.
Sorry I haven't showed up earlier. I've been busy.
Does #140 fix all you wanted? 😄

@thejamespinto Fantastic!  Thanks!  Going to close this one.

Glad I could help : )


Edit CacheUI broken since last release?

Brief Issue Summary
I thought some of the latest PRs broke something then I saw the last release reproduces as well.
Run the command "Edit CMake Cache (UI)" and instead of seeing the table, there is an error popup on bottom-right with this message:
"Error loading webview: Error: Could not register service worker: InvalidStateError: Failed to register a ServiceWorker: The document is in an invalid state..."
I debugged a little and so far I didn't notice anything outstanding in CMake Tools code base, I'll investigate more. It's possible this may end up sent to another team related to VSCode.
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response

@andreeis According to your description I can't reproduce the problem you are talking about, here are my steps to reproduce it can you give some suggestions?
ENV:
VS Code: 1.89.1
CMake tools: 1.18.39
C/C++:1.20.5
Repro steps recording:
1. Create a new folder and open it with vscode.
2. Create a CMakeLists.txt file and add the following code:
cmake_minimum_required(VERSION 3.5)
project(Test)
add_executable(Test main.cpp)
3. Create a main.cpp file and add the following code:
#include
auto main() -> int { std::cout << "hello world" << std::endl; }
4. Run command:"CMake:Configure"
5. Run command:"CMake:Edit CMake Cache(UI)"
Actual results：

I tested with the most recent version of the extension and this doesn't reproduce, closing.


Update method

Is there an update method that will update the current options?
I'm getting the seat plan input from the user as leftCol rightCol and rowNum, so user for example can create aa_aaa with 2 and 3 or a_aa with 1 and 2 and so on.
When user clicks on submit I need to be able to update the plan accordingly.

No, currently there's no update option like that. I think the safest solution will be to get rid of the map container and create a new div for the new map.

It doesn't work. I need to somehow dump all the data plugin created. When I create a new map the numbers continue from where the old one left.

Ok I've managed to do that also.


Feature/askar

Add askar and bbs

I don't think we want the merge commit included in this PR. Could we rebase on HL main?


Fix unstable CI/CD build

Summary
CI/CD pipeline started failing for this project without changes to the codebase. Restart of the build did not change the result.
Steps to Reproduce
Jenkins Build
Expected Results
Build success
Actual Results (including error logs, if applicable)
Build failure
Reproducible

[ ] Always
[x] Sometimes
[ ] Non-Reproducible

Version/Tag number
Current (master branch)
Environment setup
Jenkins
Additional Information
Likely some dependency has changed significantly enough to case this issue.

Blocked. This is related to upstream issue with rspec-puppet: https://github.com/rodjek/rspec-puppet/issues/810.

Something upstream got fixed in the last day-or-two making the builds green again. Closing.


Aux Window: Full screen Terminal Window Input Lag

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

VS Code Version: Version: 1.85.0 (Universal)
OS Version: Darwin arm64 22.5.0
Terminal input doesn't work ( is too slow almost feels like not working ) when using Full Screen in Aux Window.
Steps to Reproduce:
Open Aux Terminal Window In Full Screen Mode or make it Full screen afterwords.
https://github.com/microsoft/vscode/assets/39730881/ed5c03cf-bcc2-4bca-859e-74c23bdba515

This seems to be working in OSS Dev container.

This looks to me like a case of scheduling something on the main window which gets throttled once hidden.
@Tyriar is the terminal using scheduler for rendering such as RAF or runWhenIdle?

I can reproduce and its pretty bad.

off-topic: is there a way to move panel to separate window. e.g. bottom drawer or individually like terminal, debug console ?

PR fixing it https://github.com/xtermjs/xterm.js/pull/4912


alternating rows background color persistence

Hi there,
alternating rows background color is not maintained after sorting
Expected behavior:
alternating rows background color should be maintained after sorting
Thanks
Enrico
TableFilter version: v0.6.39 or greater
Browser and version: IE11 and Chrome Version 64.0.3282.119 (Official Build) (32-bit)
OS and version: Windows 7 Enterprise
Problem started happening recently, didn't happen in an older version of
TableFilter: Yes
Problem can be reliably reproduced, doesn't happen randomly: Yes
A working example reproducing the issue
`

Defectivity Request: TBR

IdLot nameOperationAuthorCreation DateDefectivity Reference

49631811G883Stefania08 Jun 2018 14:22Michele430105494720Nunzio03 Apr 2018 16:31Michele40144898819Paola07 Mar 2018 17:42Giovanna162049761556Marina22 May 2017 13:54Silvia125316700952Gabriella06 Apr 2017 17:39Noemi109516700295Giulia23 Mar 2017 08:31Lucia

`

Hi @enrico28, tx for pointing this out, this is fixed starting from v0.6.41.
Have a look at online demos, eg: http://www.tablefilter.com/sort.html to see the fix.
Cheers

Btw, I confirm it was introduced by v0.6.39... unfortunate regression

Hi,
I am deeply sorry, but even with version v0.6.41
I have the same behavior in my context
After a series of sorting, the background of all the rows is white
Thanks
Enrico

It depends on the browser.
Everything works correctly with Chrome, but not with IE11
Cheers

Ok @enrico28 I just posted a codepen with your HTML table and associated config that works with IE11:
https://codepen.io/koalyptus/pen/XYeMVW
IE now needs an additional polyfill to support the name property of a function, eg:
<EMAIL_ADDRESS>from https://github.com/JamesMGreene/Function.name
It was the first one I found on github/npm, no particular reason to use this one.
Cheers

Hi,
I knew I had to use es6-promise.min.js with IE11
Now I have also added Function.name.js and it works as expected.
Thanks a lot
Enrico


BUG Report

Empty Proxy File, Running flood witout proxy
Arent they supposed to download? If not where doI get them

Figured it out but the attack doesnt do anything

first what is your target protected with, what method did you u use, are your proxies working, how many threads etc. Info please


Edit buttons appear even when logged out

Clicking or mousing over should inform a user that they need to log in.

Done.


Refactor LogicManagerTest, ModelManagerTest and QuickCacheTest

Resolves #93.

Codecov Report

Merging #86 into master will increase coverage by 4.35%.
The diff coverage is 55.55%.

@@             Coverage Diff              @@
##             master      #86      +/-   ##
============================================
+ Coverage     54.31%   58.66%   +4.35%
- Complexity      399      434      +35
============================================
  Files            86       86
  Lines          1716     1708       -8
  Branches        197      196       -1
============================================
+ Hits            932     1002      +70
+ Misses          704      627      -77
+ Partials         80       79       -1

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/quickcache/logic/commands/Feedback.java
52.00% <ø> (ø)
8.00 <0.00> (ø)

...in/java/quickcache/logic/commands/OpenCommand.java
83.33% <0.00%> (-16.67%)
4.00 <1.00> (+1.00)
:arrow_down:

...n/java/quickcache/logic/commands/StatsCommand.java
84.61% <0.00%> (-15.39%)
4.00 <1.00> (+1.00)
:arrow_down:

...c/main/java/quickcache/logic/parser/CliSyntax.java
83.33% <ø> (-6.67%)
1.00 <0.00> (ø)

src/main/java/quickcache/model/QuickCache.java
92.00% <ø> (+4.00%)
12.00 <0.00> (+1.00)

.../java/quickcache/logic/commands/CommandResult.java
83.87% <100.00%> (-2.62%)
13.00 <1.00> (-1.00)

...ain/java/quickcache/model/flashcard/Flashcard.java
94.59% <100.00%> (+2.28%)
21.00 <0.00> (-1.00)
:arrow_up:

...in/java/quickcache/model/flashcard/Statistics.java
67.85% <0.00%> (-3.58%)
11.00% <0.00%> (-1.00%)

src/main/java/quickcache/model/UserPrefs.java
80.64% <0.00%> (+3.22%)
10.00% <0.00%> (+1.00%)

... and 13 more

Continue to review full report at Codecov.

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


react/destructuring-assignment ignoreClassFields does not support nested objects

Using this rule:
        "react/destructuring-assignment": [
            "warn",
            "always",
            {
                "ignoreClassFields": true
            }
        ],

This code:
export default class Thing extends React.Component {
    state = {
        alpha: false,
        beta: this.props.beta,
        charlie: null,
    };
    // ...
}

Generates this warning:
[eslint] Must use destructuring props assignment (react/destructuring-assignment)

Version information:
$ npm ls eslint
<EMAIL_ADDRESS>/Users/adam.babcock/Source/cxlint/client
├──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>extraneous

$ npm ls eslint-plugin-react
<EMAIL_ADDRESS>/Users/adam.babcock/Source/cxlint/client
├──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>extraneous

I think that this is a bug, but also, you shouldn’t ever be using props in initial constructor state - you want getDerivedStateFromProps. Otherwise when props change, you might forget to update “beta”

@ljharb Agreed. I'm going through existing code applying lint fixes and this situation popped up. The whole pattern in this particular file needs to be rewritten / refactored but for now I'm focusing on lint issues.

What about uncontrolled components though? If the component accepts a "defaultValue" prop, I think it only needs to be "translated" to state once on initialization, and after that the value is managed via component's state.

That’d be an edge case, and even then I’d say the component should rerender when it gets an updated prop.

@Jmenache note that your pattern is not correct unless you also use setState in componentWillReceiveProps - and the replacement for that pair is indeed to use gDSFP.

@ljharb I think the post recommends using a key instead of componentWillReceiveProps with this pattern, so that it creates a new component and goes through the constructor again.

Certainly that's another workaround, but that seems much less performant and clean.

@ljharb As counter intuitive as it is, the article explains that it is usually not slower, and sometimes faster.

Note
While this may sound slow, the performance difference is usually insignificant. Using a key can even be faster if the components have heavy logic that runs on updates since diffing gets bypassed for that subtree.

I agree it is not pretty and I would most likely try using the other recommended solution if I have a choice, but this pattern helped me a few times dealing with legacy code.


feature: Support make jobserver protocol

Make has already for some time used jobserver protocol such that when a sub-make is run, top-make decides whether more processes can be spawned. This is a requirement for -jN option to work with nested makes. Recently, there's a PR to add jobserver client support to ninja as well. I propose buildstream to implement the actual jobserver part (at least fifo, can use also pipe) and mounts relevant fifo into build sandbox. There is also the part of setting MAKEFLAGS and declaring where the job server is. When this setup is fully in place and user passes --max-jobs to BuildStream, it can actually take effect over all sandboxes allowing high -jN option to safely be used without worrying about overloading the system.
The specification is in https://www.gnu.org/software/make/manual/html_node/Job-Slots.html and client implementation PR for ninja is in https://github.com/ninja-build/ninja/pull/2506. The PR also contains Apache-licensed Python code that implements the server that can be used as inspiration.

Open questions is how a project should opt-in. In my opinion user opt-in is not necessary. Either an element works correctly with jobserver or then it doesn't.

I think this might need some new limit in addition to max-jobs. There should be a global limit (limited by cores) and a per-sandbox-limit (which translates to memory usage). Not all builds can parallelize arbitrarily but those that do may result in running of memory on especially larger runners.


Expose release time through https://pub.dartlang.org/api

We currently expose the various versions through the API. It would also be useful to have the date and time the version was released.

AFAICT these should be modified in the pub_server project. We delegate these API calls to ShelfPubServer, and timestamp could be added probably in the following locations:

https://github.com/dart-lang/pub_server/blob/master/lib/shelf_pubserver.dart#L282
https://github.com/dart-lang/pub_server/blob/master/lib/shelf_pubserver.dart#L236

This issue was moved to dart-lang/pub_server#14


fix prevent parquet page reader print much warning logs

Proposed changes
Prevent parquet page reader print much warning logs.


Incorrect comment in EIP-3448 implementation

Pull Request
No response
What happened?
This comment defines deploy code size:
  function _metaProxyFromMemory (address targetContract, uint256 offset, uint256 length) internal returns (address addr) {
    ...
@>    // The size is deploy code + contract code + calldatasize - 4 + 32.
      addr := create(0, start, sub(ptr, start))
    }
  }

Struggled some time to figure out what is calldata in this context. Eventually this comment was copied from previous function where it used the whole calldata except 4 bytes selector.
This will be right comment because length exactly defines metadata length:
  function _metaProxyFromMemory (address targetContract, uint256 offset, uint256 length) internal returns (address addr) {
   ...
-     // The size is deploy code + contract code + calldatasize - 4 + 32.
+     // The size is deploy code + contract code + length + 32.
      addr := create(0, start, sub(ptr, start))
    }
  }

Relevant log output
No response

https://github.com/ethereum/ERCs/pull/429


More control over mipmaps

Right now all images that are imported create mipmaps at runtime. This can be undesirable for pixel-art, producing a blurry image. We should have a way to disable it for certain images.

This is now implemented


irmin-pack: add test that raises Invalid_depth

NOTE - I have had a go at this issue but am not sure its the correct approach hence I havent updated the CHANGES yet.
It looks like the Invalid_depth exception is raised in two places, on Inode's Internal.of_concrete_exn and also when doing a find (or more specifically unsafe_find).

of_concrete_exn (included in this PR): the Inode_intf.Internal.of_concrete type has been changed to include an optional ?depth=0 parameter.  This allows to call it with the wrong depth which then surfaces the Invalid_depth exception.  My worry is that this is a bit too heavy handed and exposes the wrong API / type for of_concrete?  Also, if changed here should it be changed for other of_concrete funcs e.g. for Portable.Proof.of_concrete?

Inode.unsafe_find (not included in this PR): I was looking into this today and (inspired by test/irmin-pack/test_inode.test_intermediate_inode_as_root ) I have been trying the strategy of using Inode.unsafe_find at an incorrect depth in order to try and get the Invalid_depth exception to surface.  The problem is that this exception is first converted into an Error ... type (c.f. here which is then swallowed in Inode.integrity_check  ) because I guess the values that are constructed in the test cases are such that these integrity checks pass.

So I was wondering

is this a reasonable approach to trying to get the Invalid_depth exception to be raised?
if so, how I might go about constructing an inode tree that wont pass the integrity check - maybe one that has an empty non-root maps?

@metanivek I had a go yesterday with your suggestions - hopefully I got the right idea?
I had to change the test Context module into a functor to allow to switch between the Inode and Inode_mock,
I wondered about doing the same thing for Inode_permutations_generator but settled on passing in the appropriate Inter.Val.index function instead.

closes #1668

@metanivek thanks v much for the review - I've just pushed up those changes you suggested, for the second one I went with the first class module approach.


Crash when pressing hardware back button on initialisation screen

Build Number: 1.1.0-beta.1
Description: Opening mobile when no initialisation has been done. Press the hardware back button. App closes and says "Unfortunately, mSupply Mobile has stopped"
Reproducible: Yes
Reproduction Steps:

Clear app data
Open app
Press hardware back button

Repeat 2 and 3 as much as you like.
Comments:
Not major as users will rarely see this screen beyond initial set up, and the crash is inconsequential.
But it may be related to #365 .

Also mentioned in: https://github.com/sussol/mobile/issues/365
Logged as: undefined is not a function (evaluating 'this.intervalIds[typeof Symbol==="function"?Symbol.iterator:"@@iterator"]()')
Origin: sussol-utilities/lib/Scheduler.js
Explanation: When sussol-utilities package is compiled using with babel es2015 preset, for of loop in clearAll function compiles to use Symbol, seems to be no polyfill for Symbol. There are numerous issues re: this problem, even a feature request: https://react-native.canny.io/feature-requests/p/polyfill-es6-symbol and good explanation here: https://github.com/redux-saga/redux-saga/issues/54
Solutions:

compile sussol-utilites using es2015-loose preset or react preset.
replace for of with forEach
in index.android.js, before main import import 'babel-polyfill' (increase app size but help with future compatibility)

What do you think Chris ?

Re. above comment, for of was replaced with canonical for loop at sussol-utilities 0.4.4, which is now in use by mSupply Mobile

This is no longer occurring, closing


Remove alias model in getAllModels

We should not return alias for getAllModels. Current implementation could not distinguish between anonymous model and alias. Need to figure out the solution.

@iscai-msft @lmazuel @timotheeguerin
I don't know whether the following understanding for alias model is right. Alias model is actually a syntax helper for defining an anonymous model. Each time you use it, it will be a new anonymous model. For the following TypeSpec, two Test in body will be convert to two different anonymous models. So, getAllModels should also return two models with generated name.
alias Test = {
  name: string;
};

@route("/one")
@put
op one(body: Test): NoContentResponse;

@route("/two")
@put
op two(body: Test): NoContentResponse;

Yeah nearly in that alias is not limited to models but any expression. It's just a way to provide a reusable expression that has not actual name in the type graph

@tadelesh can you help me understand why you need to distinguish between an anonymous model that was written inline vs an anonymous model that came from an alias.  To me these don't have any unique behavior in a client library.

@tadelesh can you help me understand why you need to distinguish between an anonymous model that was written inline vs an anonymous model that came from an alias. To me these don't have any unique behavior in a client library.

@m-nash regarding the original goal to removing alias model from getAllModels, this is my question. But for now, I believe we do not need to specially handle the anonymous model from alias. It is just an anonymous model and we should return it from getAllModels as a normal model. I think this should be a non-issue.
@iscai-msft @lmazuel  what do you think?

yeah you shouldn't do any special handling for model coming from alias. Alias are a concept that is internal to the typespec compiler in a sense. It shouldn't have any mapping in emitters(Exception with a few that would want to show back the original syntax like ref doc generation or api view).


Add documentation for X509_cmp and related APIs

Fixes: #9088
Functions documented in this commit: X509_cmp, X509_NAME_cmp,
X509_issuer_and_serial_cmp, X509_issuer_name_cmp, X509_subject_name_cmp,
X509_CRL_cmp, X509_CRL_match

Checklist

[x] documentation is added or updated

Thanks for the comments! I addressed some wording and grammar issues.

This may not be specific to the documentation but I feel X509_cmp and X509_CRL_cmp should just return a kind of Boolean. Not sure if the errors have any specific meaning. May be caller needs to check validity of the parameters before calling the method. memcmp does not throw an error for example.
There is no natural ordering in certs or CRLs. Why unnecessarily create one?
While for name like comparisons there is a dictionary ordering and ideally should be respected. The names entries are kind of considered in an ordered sequence.
@InfoHunter, @mspncp, @mspncp please review and suggest what is ideal>

This may not be specific to the documentation but I feel X509_cmp and X509_CRL_cmp should just return a kind of Boolean.

Thanks for your feedback. However, changing the return type would break the API, so it is impossible to do it.

Not sure if the errors have any specific meaning. May be caller needs to check validity of the parameters before calling the method. memcmp does not throw an error for example.

This is what I suggested to @InfoHunter: to find out which errors can occur and document them in the manual page.

There is no natural ordering in certs or CRLs. Why unnecessarily create one?
While for name like comparison there is a dictionary ordering and ideally should be respected. The name entries are kind of considered in an ordered sequence.

Being a C++ developer, one use case comes immediately to my mind: types which have an ordering can be used as key type in a  map : key -> value. It does not matter whether the ordering has a special meaning to humans or not. The ordering is needed, because maps are usually implemented as (balanced) binary tries of <key,value> nodes, where the nodes are ordered according to the ordering of the key type.

Of course also C developers can benefit from the ordering by using qsort() and bsearch() for efficient lookup.

@mspncp and @slontis, excellent thoughts. In fact, when it comes to X509_STORE the default lookups are not the best. One can think of a B-tree based store with say subject name ordering. It may be ideal in that case to order X509_cmp to compare on names and only resolve over to hash of DER encoding with memcmp as a fail over.

I think it would be very helpful if you could find out and describe the possible error cases in more detail and give the user guidance how to deal with the quirks of the API properly.

This is what I suggested to @InfoHunter: to find out which errors can occur and document them in the manual page.

There are two calls to d2i_X509_NAME in the X509_NAME_cmp function for making sure the encoding of the raw data is correct and up-to-date. d2i_X509_NAME might fail and this is the reason why X509_NAME_cmp as a comparison function will also fail. This reason is not complex and could be documented, but is it really necessary to reveal this much of internal information here?

This may not be specific to the documentation but I feel X509_cmp and X509_CRL_cmp should just return a kind of Boolean.

Thanks for your feedback. However, changing the return type would break the API, so it is impossible to do it.

Another choice is to provide new APIs like X509_is_equal and X509_CRL_is_equal to just return 0 and 1 if the two compared entities are the same or not.

Ping @openssl/committers

Fixed all nits pointed out by @mattcaswell

Pushed to master (4bfe304ea8) and 1.1.1 (ea5d4b89cc), thanks!

Hi @sambitdash , since this PR has been merged I will close this one and we can still discuss about the certificate comparison requirements if you have any ;-)


Update nodes.md

另外建议：control-plane 这类专有名词还是不要翻译成中文好一些。

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.
It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address.  Check your existing CLA data and verify that your email is set on your git commits.
If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at<EMAIL_ADDRESS>

done！

Invalid fix.
/close


[SITES] https://www.bbc.com

First please check that it is really an issue with the library, and not some special case of website:
[ ] There is no paywall
[ ] You do not have to be logged in to see the articles
[ ] You tried using a common browser user agent in your configuration / call
[ ] The website is not in the list of well known problematic sites
Your report as follows:
Website that does not parse correctly:

https://www.bbc.com

Some sample urls that I have tried

https://www.bbc.com/news/world-australia-67832905
https://www.bbc.com/news/business-67470876

The exact code i used to test this articles/website

import newspaper

url = "https://www.bbc.com/news/business-67470876"
result = newspaper.article(url)
print(result.text)
# the text is empty

** What parts of the article are missing / not parsed correctly **
[ ] Text Content
Other information, remarks, messages, etc:
It was working until a few days ago. I am using the package with version 0.9.2

Thank you for responding.
I am not blocked by the BBC. Most other fields are non empty like title, authors and even html which seems to have the text of the article. Just the 'text' field in the output which used to be populated earlier is now empty.
I noticed that the website UI of the BBC has changed. I think that could be the reason for this issue.
I am unable to import newspaper after installing the v 0.9.3. There seems to be some dependency issue which I am trying to figure out. But I don't think this could be the problem.

I am unable to import newspaper after installing the v 0.9.3. There seems to be some dependency issue which I am trying to figure out. But I don't think this could be the problem.

What's the error. I did in fact change how dependencies are installed.

I am not blocked by the BBC. Most other fields are non empty like title, authors and even html which seems to have the text of the article. Just the 'text' field in the output which used to be populated earlier is now empty.

You are right, there seems to be an issue with bbc. I will investigate it

The html component of the response seems to have the text content although not in a contiguous paragraph form. Maybe that is something to look at.
I tried v0.9.3 on google colab. Regarding the error while importing newspaper, this is what I got when I did pip install:

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
bigframes 0.24.0 requires pandas<2.1.4,>=1.5.0, but you have pandas 2.2.1 which is incompatible.
google-colab 1.0.0 requires pandas==1.5.3, but you have pandas 2.2.1 which is incompatible.
Successfully installed feedparser-6.0.11 newspaper4k-0.9.3 numpy-1.26.4 pandas-2.2.1 requests-file-2.0.0 sgmllib3k-1.0.0 tldextract-5.1.1 tzdata-2024.1

When I try to import after installation, I get this error:

On subject of bbc and dates why does bbc article prepend date to _text string now?
e.g.
Published\n\n8 March\n\n
source https://www.bbc.co.uk/news/uk-england-london-68511760

interesting about playwright and textise.
Content for bbc seems to be in the main page render as well as attached via some nonce window object.
e.g.
<script nonce>
window.__INITIAL_DATA__={}
</script>


feature(validation): add validation for dynamic metadata

Signed-off-by:<PHONE_NUMBER><EMAIL_ADDRESS>Description
All components should strictly verify dynamic metadata. For unknown keys in yaml or metadata passed in from  dapr runtime api, errors should be intercepted to avoid unexpected result.
Issue reference
Please reference the issue this PR will close: #[5040]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

I think this is a good addition, but have you seen this issue? https://github.com/dapr/components-contrib/issues/2014 @berndverst  and I have been working on a new proposal for “component metadata” and I’m going to open the first PR today. That will also include some information about what metadata is required and what kind of fields are expected (strings, numbers, enums…)
The current proposal does NOT include runtime validation like your PR. However, I think perhaps your PR could be built on top of the “component metadata” to leverage the same data?

I think this is a good addition, but have you seen this issue? #2014 @berndverst and I have been working on a new proposal for “component metadata” and I’m going to open the first PR today. That will also include some information about what metadata is required and what kind of fields are expected (strings, numbers, enums…)
The current proposal does NOT include runtime validation like your PR. However, I think perhaps your PR could be built on top of the “component metadata” to leverage the same data?

Thanks. @ItalyPaleAle .
I will check if the current Issue or PR has similar content before apply an Issue or PR next time. This way I can also discuss directly on the issue.

If you have feedback on the design please provide it on that issue too!

This kind of change should not have been made without a proposal issue being raised and discussed / approved by all maintainers first.
I will close this issue at this time because there is no approved proposal that this PR is based on.


Get all keys stored

How can I get all stored keys in localstorage?
If there isn't this feature can be implemented??

Maybe Object.keys($localStorage) can help you? :)
Note that Object.keys will also give you $reset and $default (functions on the $localStorage object). Which you'll have to filter out if you do not want them.
Alternative $window.localStorage provides access to Storage item.

Sure I forgot that $localStorage is an object :( thank you!


House robber 2

hey @ayu8, I want to add this solution in CPP into the DP folder, please assign this to me and add this under hacktoberfest label

Hello @ayu8 sir, I want to contribute my efforts on this problem.
plz assign it to me under hacktoberfest22.

@Akash-moon
Please find some other issue
@123shanawaz is already doing this

@ayu8 @Akash-moon yes I am doing this......

Ok Np @123shanawaz @ayu8 .


Log-in

As a user I want to be able to log in to the application so that I get access to my own account.

Acceptance criteria:  When the user inputs their correct password and username it should direct them to their personal account.

I linked the issue to the PR

this issue was started to be implemented (android side) but not finished and now is out of scope, due to lack of time and also because it's not a priority


Remove recipient from RecordsWrite for non-protocol based message

This looks like a leftover artifact from a previous design choice which is no longer applicable.

Done.


Invariants in known containers

Check type invariants for what is inside:

a list
an array
an option
a ref

I had to add a field in Translation.type_ in order to have access to the argument of the type constructors.
This PR is incompatible with PR #51.

Closing because it is stale.


[KOGITO-612] - Add topics to image metadata

See:
https://issues.jboss.org/browse/KOGITO-612
In this PR we're adding the label org.kie/messaging/topics when the runtime defines Kafka topics:
{
  "labels" : [ {
    "org.kie/messaging/topics" : "kogito-usertaskinstances-events,kogito-processinstances-events,visaapplications,visasrejected,visasapproved",
    "prometheus.io/path" : "/metrics",
    "prometheus.io/scheme" : "http",
    "prometheus.io/port" : "8080",
    "prometheus.io/scrape" : "true"
  } ]
}

@ricardozanini isn't this quarkus specific solution as it relies on mp basedproperties? How would we support spring boot based service?

I'm closing this one since we won't differentiate Quarkus and Springboot. The CLI/CR will have an input for users to specify their topics if needed on https://issues.jboss.org/browse/KOGITO-611


Update typo in example

The code snippet as provided doesn’t run, because there's no such thing as a "JsonDerializer". This fixes the example.

Codecov Report

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

@@          Coverage Diff           @@
##           master    #417   +/-   ##
======================================
  Coverage    93.1%   93.1%
======================================
  Files         206     206
  Lines        3175    3175
  Branches      263     263
======================================
  Hits         2956    2956
  Misses        219     219

Continue to review full report at Codecov.

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

Thank you @alexwlchan! Can you construct a commit message following this guide?

Can you construct a commit message following this guide?

Done.

Hi @alexwlchan, thanks so much for your contribution! Your PR has been merged in 156a540.


Why are you using $timeout  0?

Hi, bro
Could you tell me the reason Why are you using $timeout at the end of source code?
I am confused, thanks much

return $timeout((function() {
      return flexsliderDiv.flexslider(options);
}), 0);

Yup I found myself having to use $timeout(function { ... }, 0) in place of $(document).ready(function() {...})); This is because angular manipulates the DOM after the page has loaded. You can sometimes see angular expressions update after the pages have loaded when the CPU is a little busy. The timeout function ensures that the code is run zero milliseconds after angular has finished processing the document. I loath using it as it doesn't feel natural but once you get used to it... it's not so bad... It's certainly worth the tradeoff against the functionality angular provides.

I had a nasty situation that had to call angular.copy() right after angular.merge(). Seems that wrapping angular.copy inside $timeout with 0 timeout makes sure angular.merge() finished properly.


new block column: uniswap prices

the user somehow specifies which pools they would like to watch, such as ETH/USDC
when showing the block list do some eth_calls to figure out the price as of each block
in the future, generalize this to any eth_call users might want to track the result of?

This has a couple components:

add support for reading from configuration files
read new column definitions (addresses and calldata) from the configuration file (this might be a partial solution to #13)
fetch per-block results from the provider
cache the results in sled


1.0 System introduction

close #202

* Er også selv skyldig, men når man skriver uni rapporter burde man ikke skrive "vi", "jeg" og sådan noget. Det er bedre f.eks. at skrive "It was decided" instead of "we decided".

Where appropriate "our" and "we" is not a problem. But yes it should not be in this introduction to a chapter.

Also seems overly verbose and takes large parts of what is in the next parts.


Unable to build with rust-1.51.0

error[E0277]: cannot multiply-assign `<E as ScalarEngine>::Fr` by `&&<E as ScalarEngine>::Fr`
   --> /var/tmp/portage/net-p2p/piratewallet-lite-1.0.5/work/cargo_home/gentoo/bellman-0.6.0/src/gadgets/test/mod.rs:131:24
    |
131 |         tmp.mul_assign(&coeff);
    |                        ^^^^^^ no implementation for `<E as ScalarEngine>::Fr *= &&<E as ScalarEngine>::Fr`
    |
    = help: the trait `MulAssign<&&<E as ScalarEngine>::Fr>` is not implemented for `<E as ScalarEngine>::Fr`
help: consider further restricting the associated type
    |
122 | ) -> E::Fr where <E as ScalarEngine>::Fr: MulAssign<&&<E as ScalarEngine>::Fr> {
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0277]: cannot multiply-assign `<E as ScalarEngine>::Fr` by `&&<E as ScalarEngine>::Fr`
   --> /var/tmp/portage/net-p2p/piratewallet-lite-1.0.5/work/cargo_home/gentoo/bellman-0.6.0/src/groth16/generator.rs:389:39
    |
389 |                         at.mul_assign(&beta);
    |                                       ^^^^^ no implementation for `<E as ScalarEngine>::Fr *= &&<E as ScalarEngine>::Fr`
    |
    = help: the trait `MulAssign<&&<E as ScalarEngine>::Fr>` is not implemented for `<E as ScalarEngine>::Fr`
help: consider further restricting the associated type
    |
324 |     ) where <E as ScalarEngine>::Fr: MulAssign<&&<E as ScalarEngine>::Fr> {
    |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0277]: cannot multiply-assign `<E as ScalarEngine>::Fr` by `&&<E as ScalarEngine>::Fr`
   --> /var/tmp/portage/net-p2p/piratewallet-lite-1.0.5/work/cargo_home/gentoo/bellman-0.6.0/src/groth16/generator.rs:390:39
    |
390 |                         bt.mul_assign(&alpha);
    |                                       ^^^^^^ no implementation for `<E as ScalarEngine>::Fr *= &&<E as ScalarEngine>::Fr`
    |
    = help: the trait `MulAssign<&&<E as ScalarEngine>::Fr>` is not implemented for `<E as ScalarEngine>::Fr`
help: consider further restricting the associated type
    |
324 |     ) where <E as ScalarEngine>::Fr: MulAssign<&&<E as ScalarEngine>::Fr> {
    |       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0277`.
error: could not compile `bellman`

This issue turns out to be a duplicate of my own issue.