On new debian 8 installs using google_compute_engine virtualenv installed boto is broken

Not exactly sure what's going on here but we are now seeing:
  File "/home/lex/local/lib/python2.7/site-packages/boto/__init__.py", line 1216, in <module>
    boto.plugin.load_plugins(config)
  File "/home/lex/local/lib/python2.7/site-packages/boto/plugin.py", line 93, in load_plugins
    _import_module(file)
  File "/home/lex/local/lib/python2.7/site-packages/boto/plugin.py", line 75, in _import_module
    return imp.load_module(name, file, filename, data)
  File "/usr/lib/python2.7/dist-packages/google_compute_engine/boto/boto_config.py", line 29, in <module>
    from google_compute_engine import config_manager
ImportError: No module named google_compute_engine

Note that this is a virtualenv installed copy of boto which ends up failing with an error in google_compute_engines vendoring(?) of boto?

Hi, we'll see if we can figure out what is going on here. Can you describe why you are using a virtual env for boto and also how are you setting this up (which version etc) so we can reproduce?

# This file is automatically created at boot time by the /usr/lib/python
# 2.7/dist-packages/google_compute_engine/boto/boto_config.pyc script.
# Do not edit this file directly. If you need to add items to this file,
# create or edit /etc/boto.cfg.template instead and then re-run the
# script.

[GSUtil]
default_project_id =<PHONE_NUMBER>5
default_api_version = 2

[GoogleCompute]
service_account = default

[Plugin]
plugin_directory = /usr/lib/python2.7/dist-packages/google_compute_engine/boto

Yeah so that setups loading plugins from a package that doesn't exist in the virtualenv

Grab a normal GCE image from the current debian-8, create a virtualenv, install boto, try and import boto. Kaboom.

The old compute_auth.py plugin worked fine inside a virtualenv, the new plugin does not.

To summarize the issue:

The new Linux guest environment is installed via the google-compute-engine package GCE images.
The package is located in: /usr/lib/python2.7/dist-packages/google_compute_engine
The file that sets up credentials for boto is a part of the google-compute-engine package.
Running a virtualenv removes Python dist-packages from the PATH.

In order to use boto from inside a virtualenv, you can set your Python path with the command:
export PYTHONPATH="/usr/lib/python2.7/dist-packages/google_compute_engine"

You can also create a virtualenv that includes the system site packages (/usr/lib/python2.7/dist-packages/). However the previous boto configuration worked perfectly fine as the plugin it specified had no dependencies except boto itself. The new boto plugin requires google_compute_engine which can't easily be installed in the virtualenv as this package isn't available from pypi.

One of the reasons behind the improved packaging is to enable PyPI distribution of the Linux guest environment which is currently in progress.

In that case I'd recommend noting a work around for anyone else running their own code using boto on GCE create any virtualenvs with virtualenv --system-site-packages otherwise the on import exceptions are quite startling.

I've updated the README to include troubleshooting instructions for using boto.

We now have a PyPI package for the Linux guest environment.
The package is available using: pip install google-compute-engine.

I also got an error with boto installation in Python 3 on Google Dataproc instances running Debian 8.
I initialize a Dataproc cluster, install Python 3 and install google-compute-engine package with pip...
apt-get install -y python3 python3-dev python3-pip
pip3 install -v google-compute-engine

when I try to import boto in python 3 ...
python3 -c "import boto"
I get the following error:
File "/usr/local/lib/python3.4/dist-packages/boto/plugin.py", line 75, in _import_module
return imp.load_module(name, file, filename, data)
File "/usr/lib/python3.4/imp.py", line 235, in load_module
return load_source(name, filename, file)
File "/usr/lib/python3.4/imp.py", line 171, in load_source
module = methods.load()
File "/usr/share/google/boto/boto_plugins/compute_auth.py", line 18, in
import urllib2
ImportError: No module named 'urllib2'
After a long time of investigation, I guessed the problem. Boto saves its config in /etc/boto.cfg .
In Dataproc instances, the [Plugin] section of the config file is as follows, pointing to a directory with Python 2.7 code (which refers urllib2, not available in Python 3)
[Plugin]
plugin_directory = /usr/share/google/boto/boto_plugins
The  /etc/boto.cfg file is usually managed using scripts, so I just included this command in my bash script just after  google-compute-engine package install, to update /etc/boto.cfg with the correct plugin_directory (/usr/local/lib/python3.4/dist-packages/google_compute_engine/boto)
python3 -c "from google_compute_engine.boto.boto_config import BotoConfig; BotoConfig()"
Just sharing in the case anyone runs into the same problem involving this setup: Dataproc (Image version v1.0), Python3 and boto.

The Dataproc images have not updated to the new guest environment. When they next update their images, they should hopefully pick up the new guest environment and work the same as the standard Debian 8 images on Google Compute Engine.

Been hitting this (on travis-ci 14.04). Seems like google-compute-engine has a cyclic dependency on boto.

The suggested solution (adding system packages to the virtualenv or installing google-compute-engine into it) are not sufficient. Python virtualenvs are isolated from system packages (by default) for a reason, you want to be able to control where modules are imported from in a virtualenv. You should also not have to pip install a gce library into a virtualenv that doesn't use/need it just to be able to run boto.
I do find this to be an issue with boto itself, but google also has a responsibility here. I don't know why you can't just define the boto config file locally for projects using this, but if that's not the case can't you at least catch the import errors of google_compute_engine in the plugin you inject do nothing if google_compute_engine is not available?


Aysnc-connector: Merging L2/L3

Merging L2(hot data layer) and L3(cold data layer) in source code in order to unify the use of ShardingSphere.
Replacing SQL schema name to ShardingSphere Logical Schema Name.

Correspondence between logical schema name and real schema name are saving in dtc.yaml, using current data_lifecycle.HotDBName and data_lifecycle.ColdDBName.
Altering data_lifecycle.HotDBName and data_lifecycle.ColdDBName to specified filed named Logical_DB.

it's no necessary to merge L2 and L3 again cause that we can config both hot db and cold db in one shardingsphere instantce using two different logical db names, through current existing two threads.


cross-match with VSX

Consider to add a link to AAVSO VSX in neighbourhood. They have more than 2 millions of variable stars.
https://www.aavso.org/vsx/index.php

Thanks @pruzhinskaya for the feedback -- but they do not seem to allow URL query (query by position from URL) as the other. Do you have an example?

Ah nevermind -- I found a way in this thread https://www.aavso.org/direct-web-query-vsxvsp
I will implement it then!

For SNAD Viewer the data have been taken from VizieR: http://vizier.cds.unistra.fr/viz-bin/VizieR?-source=B%2Fvsx


'pure virtual method called' from TrackerKCF function.

Before reporting an issue please first check the
troubleshooting guide. If
the issue you're encountering is not solved thereby please state the following in your bugreport:

Operating system: Linux
The way you installed OpenCV: manual compilation
OpenCV version: 4.5.1
rustc version (rustc --version): 1.54
Attach the full output of the following command from your project directory:

pi@raspberrypi:~/project/rust/honeypot $ RUST_BACKTRACE=full cargo build -vv --release --example ucam007s06
       Fresh unicode-xid v0.2.2
       Fresh autocfg v1.0.1
       Fresh glob v0.3.0
       Fresh regex-syntax v0.6.25
       Fresh percent-encoding v2.1.0
       Fresh dunce v1.0.2
       Fresh maplit v1.0.2
       Fresh vcpkg v0.2.15
       Fresh smallvec v1.6.1
       Fresh cfg-if v0.1.10
       Fresh pkg-config v0.3.19
       Fresh scopeguard v1.1.0
       Fresh shlex v1.0.0
       Fresh lazy_static v1.4.0
       Fresh byteorder v1.4.3
       Fresh once_cell v1.8.0
       Fresh bytes v1.0.1
       Fresh system_shutdown v3.0.0
       Fresh lock_api v0.3.4
       Fresh proc-macro2 v1.0.28
       Fresh libc v0.2.99
       Fresh memchr v2.4.1
       Fresh semver v1.0.4
       Fresh quote v1.0.9
       Fresh jobserver v0.1.24
       Fresh time v0.1.44
       Fresh parking_lot_core v0.7.2
       Fresh mmal-sys v0.1.0-3
       Fresh rppal v0.11.3
       Fresh socket2 v0.4.1
       Fresh aho-corasick v0.7.18
       Fresh clang-sys v1.2.0
       Fresh num-traits v0.2.14
       Fresh syn v1.0.74
       Fresh cc v1.0.69
       Fresh parking_lot v0.10.2
       Fresh regex v1.5.4
       Fresh clang v1.0.3
       Fresh num-integer v0.1.44
       Fresh serde_derive v1.0.127
       Fresh thiserror-impl v1.0.26
       Fresh derivative v2.2.0
       Fresh rascam v0.0.2
       Fresh thiserror v1.0.26
       Fresh opencv-binding-generator v0.28.0
       Fresh serde v1.0.127
       Fresh chrono v0.4.19
       Fresh toml v0.5.8
       Fresh proc-macro-crate v1.0.0
       Fresh num_enum_derive v0.5.4
warning: In file included from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/dnn.hpp:7,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/dnn.cpp:1:
warning: /usr/local/include/opencv4/opencv2/dnn/shape_utils.hpp: In function ‘bool cv::dnn::dnn4_v20210301::isAllOnes(const MatShape&, int, int)’:
warning: /usr/local/include/opencv4/opencv2/dnn/shape_utils.hpp:248:33: warning: comparison of integer expressions of different signedness: ‘size_t’ {aka ‘unsigned int’} and ‘int’ [-Wsign-compare]
warning:      for (size_t i = startPos; i < endPos; i++)
warning:                                ~~^~~~~~~~
warning: In file included from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/dnn.hpp:7,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/manual-dnn.cpp:1:
warning: /usr/local/include/opencv4/opencv2/dnn/shape_utils.hpp: In function ‘bool cv::dnn::dnn4_v20210301::isAllOnes(const MatShape&, int, int)’:
warning: /usr/local/include/opencv4/opencv2/dnn/shape_utils.hpp:248:33: warning: comparison of integer expressions of different signedness: ‘size_t’ {aka ‘unsigned int’} and ‘int’ [-Wsign-compare]
warning:      for (size_t i = startPos; i < endPos; i++)
warning:                                ~~^~~~~~~~
warning: At global scope:
warning: cc1plus: warning: unrecognized command line option ‘-Wno-return-type-c-linkage’
warning: cc1plus: warning: unrecognized command line option ‘-Wno-deprecated-copy’
warning: At global scope:
warning: cc1plus: warning: unrecognized command line option ‘-Wno-return-type-c-linkage’
warning: cc1plus: warning: unrecognized command line option ‘-Wno-deprecated-copy’
warning: In file included from /usr/local/include/opencv4/opencv2/mcc.hpp:35,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/mcc.cpp:2:
warning: /usr/local/include/opencv4/opencv2/mcc/ccm.hpp:73:25: warning: multi-line comment [-Wcomment]
warning:                          /// k_R & 0 & 0\\
warning:                          ^
warning: /usr/local/include/opencv4/opencv2/mcc/ccm.hpp:80:25: warning: multi-line comment [-Wcomment]
warning:                          /// k_R=mean(R_{li}')/mean(R_{li})\\
warning:                          ^
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp: In function ‘Result<cv::line_descriptor::KeyLine> cv_line_descriptor_KeyLine_KeyLine()’:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::angle’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::angle’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::class_id’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::class_id’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::octave’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::octave’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::response’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::response’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::size’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::size’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::startPointX’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::startPointX’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::startPointY’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::startPointY’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::endPointX’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::endPointX’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::endPointY’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::endPointY’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::sPointInOctaveX’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::sPointInOctaveX’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::sPointInOctaveY’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::sPointInOctaveY’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::ePointInOctaveX’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::ePointInOctaveX’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::ePointInOctaveY’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::ePointInOctaveY’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::lineLength’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::lineLength’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: In file included from /usr/local/include/opencv4/opencv2/line_descriptor.hpp:45,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:2:
warning: /usr/local/include/opencv4/opencv2/line_descriptor/descriptor.hpp:102:28: warning: ‘ret.cv::line_descriptor::KeyLine::numOfPixels’ is used uninitialized in this function [-Wuninitialized]
warning:  struct CV_EXPORTS_W_SIMPLE KeyLine
warning:                             ^~~~~~~
warning: /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/line_descriptor.cpp:347:33: note: ‘ret.cv::line_descriptor::KeyLine::numOfPixels’ was declared here
warning:     cv::line_descriptor::KeyLine ret;
warning:                                  ^~~
warning: At global scope:
warning: cc1plus: warning: unrecognized command line option ‘-Wno-return-type-c-linkage’
warning: cc1plus: warning: unrecognized command line option ‘-Wno-deprecated-copy’
warning: cc1plus: warning: unrecognized command line option ‘-Wno-return-type-c-linkage’
warning: cc1plus: warning: unrecognized command line option ‘-Wno-deprecated-copy’
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/objdetect.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::DetectionROI&}; _Tp = cv::DetectionROI; _Alloc = std::allocator<cv::DetectionROI>]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::DetectionROI>::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::DetectionROI*, std::vector<cv::DetectionROI> >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/objdetect.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfDetectionROI_push(std::vector<cv::DetectionROI>*, cv::DetectionROI*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::DetectionROI*, std::vector<cv::DetectionROI> >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/objdetect.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfDetectionROI_insert(std::vector<cv::DetectionROI>*, size_t, cv::DetectionROI*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::DetectionROI*, std::vector<cv::DetectionROI> >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/optflow.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::optflow::GPCPatchDescriptor&}; _Tp = cv::optflow::GPCPatchDescriptor; _Alloc = std::allocator<cv::optflow::GPCPatchDescriptor>]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::optflow::GPCPatchDescriptor>::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::optflow::GPCPatchDescriptor*, std::vector<cv::optflow::GPCPatchDescriptor> >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::optflow::GPCPatchDescriptor>::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::optflow::GPCPatchDescriptor*, std::vector<cv::optflow::GPCPatchDescriptor> >’} changed in GCC 7.1
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/optflow.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfGPCPatchDescriptor_push(std::vector<cv::optflow::GPCPatchDescriptor>*, cv::optflow::GPCPatchDescriptor*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::optflow::GPCPatchDescriptor*, std::vector<cv::optflow::GPCPatchDescriptor> >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/optflow.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfGPCPatchDescriptor_insert(std::vector<cv::optflow::GPCPatchDescriptor>*, size_t, cv::optflow::GPCPatchDescriptor*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::optflow::GPCPatchDescriptor*, std::vector<cv::optflow::GPCPatchDescriptor> >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/ml.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::ml::DTrees::Node&}; _Tp = cv::ml::DTrees::Node; _Alloc = std::allocator<cv::ml::DTrees::Node>]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::ml::DTrees::Node>::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::ml::DTrees::Node*, std::vector<cv::ml::DTrees::Node> >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/ml.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfDTrees_Node_push(std::vector<cv::ml::DTrees::Node>*, cv::ml::DTrees::Node*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::ml::DTrees::Node*, std::vector<cv::ml::DTrees::Node> >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/ml.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfDTrees_Node_insert(std::vector<cv::ml::DTrees::Node>*, size_t, cv::ml::DTrees::Node*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::ml::DTrees::Node*, std::vector<cv::ml::DTrees::Node> >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::Point_<double>&}; _Tp = cv::Point_<double>; _Alloc = std::allocator<cv::Point_<double> >]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::Point_<double> >::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::Point_<double>*, std::vector<cv::Point_<double> > >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfPoint2d_push(std::vector<cv::Point_<double> >*, cv::Point2d*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Point_<double>*, std::vector<cv::Point_<double> > >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfPoint2d_insert(std::vector<cv::Point_<double> >*, size_t, cv::Point2d*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Point_<double>*, std::vector<cv::Point_<double> > >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::Point3_<double>&}; _Tp = cv::Point3_<double>; _Alloc = std::allocator<cv::Point3_<double> >]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::Point3_<double> >::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::Point3_<double>*, std::vector<cv::Point3_<double> > >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfPoint3d_push(std::vector<cv::Point3_<double> >*, cv::Point3d*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Point3_<double>*, std::vector<cv::Point3_<double> > >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfPoint3d_insert(std::vector<cv::Point3_<double> >*, size_t, cv::Point3d*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Point3_<double>*, std::vector<cv::Point3_<double> > >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::Rect_<double>&}; _Tp = cv::Rect_<double>; _Alloc = std::allocator<cv::Rect_<double> >]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::Rect_<double> >::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::Rect_<double>*, std::vector<cv::Rect_<double> > >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfRect2d_push(std::vector<cv::Rect_<double> >*, cv::Rect2d*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Rect_<double>*, std::vector<cv::Rect_<double> > >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfRect2d_insert(std::vector<cv::Rect_<double> >*, size_t, cv::Rect2d*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Rect_<double>*, std::vector<cv::Rect_<double> > >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::Scalar_<double>&}; _Tp = cv::Scalar_<double>; _Alloc = std::allocator<cv::Scalar_<double> >]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::Scalar_<double> >::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::Scalar_<double>*, std::vector<cv::Scalar_<double> > >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfScalar_push(std::vector<cv::Scalar_<double> >*, cv::Scalar*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Scalar_<double>*, std::vector<cv::Scalar_<double> > >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_insert_aux(std::vector<_Tp, _Alloc>::iterator, _Arg&&) [with _Arg = cv::Scalar_<double>; _Tp = cv::Scalar_<double>; _Alloc = std::allocator<cv::Scalar_<double> >]’:
warning: /usr/include/c++/8/bits/vector.tcc:382:7: note: parameter passing for argument of type ‘std::vector<cv::Scalar_<double> >::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::Scalar_<double>*, std::vector<cv::Scalar_<double> > >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfScalar_insert(std::vector<cv::Scalar_<double> >*, size_t, cv::Scalar*)’:
warning: /usr/include/c++/8/bits/vector.tcc:142:6: note: parameter passing for argument of type ‘const __gnu_cxx::__normal_iterator<cv::Scalar_<double>*, std::vector<cv::Scalar_<double> > >’ changed in GCC 7.1
warning:       _M_insert_aux(__pos, std::move(__x_copy._M_val()));
warning:       ^~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Scalar_<double>*, std::vector<cv::Scalar_<double> > >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::Vec<double, 3>&}; _Tp = cv::Vec<double, 3>; _Alloc = std::allocator<cv::Vec<double, 3> >]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::Vec<double, 3> >::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::Vec<double, 3>*, std::vector<cv::Vec<double, 3> > >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfVec3d_push(std::vector<cv::Vec<double, 3> >*, cv::Vec3d*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Vec<double, 3>*, std::vector<cv::Vec<double, 3> > >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfVec3d_insert(std::vector<cv::Vec<double, 3> >*, size_t, cv::Vec3d*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::Vec<double, 3>*, std::vector<cv::Vec<double, 3> > >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const double&}; _Tp = double; _Alloc = std::allocator<double>]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<double, std::allocator<double> >::iterator’ {aka ‘__gnu_cxx::__normal_iterator<double*, std::vector<double, std::allocator<double> > >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOff64_push(std::vector<double, std::allocator<double> >*, double)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<double*, std::vector<double, std::allocator<double> > >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/core.hpp:1,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/core.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOff64_insert(std::vector<double, std::allocator<double> >*, size_t, double)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<double*, std::vector<double, std::allocator<double> > >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/text.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::text::ERStat&}; _Tp = cv::text::ERStat; _Alloc = std::allocator<cv::text::ERStat>]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::text::ERStat>::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::text::ERStat*, std::vector<cv::text::ERStat> >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/text.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfERStat_push(std::vector<cv::text::ERStat>*, cv::text::ERStat*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::text::ERStat*, std::vector<cv::text::ERStat> >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/text.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfERStat_insert(std::vector<cv::text::ERStat>*, size_t, cv::text::ERStat*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::text::ERStat*, std::vector<cv::text::ERStat> >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/stitching.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::detail::CameraParams&}; _Tp = cv::detail::CameraParams; _Alloc = std::allocator<cv::detail::CameraParams>]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::detail::CameraParams>::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::detail::CameraParams*, std::vector<cv::detail::CameraParams> >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/stitching.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfDetail_CameraParams_push(std::vector<cv::detail::CameraParams>*, cv::detail::CameraParams*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::detail::CameraParams*, std::vector<cv::detail::CameraParams> >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/stitching.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfDetail_CameraParams_insert(std::vector<cv::detail::CameraParams>*, size_t, cv::detail::CameraParams*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::detail::CameraParams*, std::vector<cv::detail::CameraParams> >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
warning: /usr/include/c++/8/bits/vector.tcc: In member function ‘void std::vector<_Tp, _Alloc>::_M_realloc_insert(std::vector<_Tp, _Alloc>::iterator, _Args&& ...) [with _Args = {const cv::detail::MatchesInfo&}; _Tp = cv::detail::MatchesInfo; _Alloc = std::allocator<cv::detail::MatchesInfo>]’:
warning: /usr/include/c++/8/bits/vector.tcc:413:7: note: parameter passing for argument of type ‘std::vector<cv::detail::MatchesInfo>::iterator’ {aka ‘__gnu_cxx::__normal_iterator<cv::detail::MatchesInfo*, std::vector<cv::detail::MatchesInfo> >’} changed in GCC 7.1
warning:        vector<_Tp, _Alloc>::
warning:        ^~~~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:64,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/stitching.cpp:1:
warning: /usr/include/c++/8/bits/stl_vector.h: In function ‘void cv_VectorOfDetail_MatchesInfo_push(std::vector<cv::detail::MatchesInfo>*, cv::detail::MatchesInfo*)’:
warning: /usr/include/c++/8/bits/stl_vector.h:1085:4: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::detail::MatchesInfo*, std::vector<cv::detail::MatchesInfo> >’ changed in GCC 7.1
warning:     _M_realloc_insert(end(), __x);
warning:     ^~~~~~~~~~~~~~~~~
warning: In file included from /usr/include/c++/8/vector:69,
warning:                  from /usr/local/include/opencv4/opencv2/core/types.hpp:53,
warning:                  from /usr/local/include/opencv4/opencv2/core.hpp:57,
warning:                  from /home/pi/.cargo/registry/src/github.com-1285ae84e5963aae/opencv-0.53.1/src_cpp/ocvrs_common.hpp:15,
warning:                  from /home/pi/project/rust/honeypot/target/release/build/opencv-a019d0640432863e/out/stitching.cpp:1:
warning: /usr/include/c++/8/bits/vector.tcc: In function ‘void cv_VectorOfDetail_MatchesInfo_insert(std::vector<cv::detail::MatchesInfo>*, size_t, cv::detail::MatchesInfo*)’:
warning: /usr/include/c++/8/bits/vector.tcc:149:2: note: parameter passing for argument of type ‘__gnu_cxx::__normal_iterator<cv::detail::MatchesInfo*, std::vector<cv::detail::MatchesInfo> >’ changed in GCC 7.1
warning:   _M_realloc_insert(begin() + (__position - cbegin()), __x);
warning:   ^~~~~~~~~~~~~~~~~
       Fresh num_enum v0.5.4
       Fresh opencv v0.53.1
       Fresh e_drone v21.8.1
       Fresh e_drone_rpi v21.7.1
       Fresh honeypot v0.1.0 (/home/pi/project/rust/honeypot)
warning: unreachable expression
  --> examples/ucam007s06.rs:60:2
   |
32 | /     loop
33 | |     {
34 | |         let time_sleep = time::Duration::from_millis(1);
35 | |         thread::sleep(time_sleep);
...  |
57 | |         }
58 | |     }
   | |_____- any code following this expression is unreachable
59 |
60 |       Ok(())
   |       ^^^^^^ unreachable expression
   |
   = note: `#[warn(unreachable_code)]` on by default

warning: 1 warning emitted

    Finished release [optimized] target(s) in 0.27s
pi@raspberrypi:~/project/rust/honeypot $

Source code
extern crate honeypot;

use std::{thread, time};
use opencv::video::Tracker;
use opencv::tracking::prelude::*;
//use opencv::tracking::*;
use opencv::{prelude::*, videoio, Result};

fn main() -> Result<()> {
    let mut cam = videoio::VideoCapture::new(-1, videoio::CAP_V4L2).unwrap();

    let param: opencv::tracking::TrackerKCF_Params = opencv::tracking::TrackerKCF_Params::default()?;
    let mut tracker = <dyn TrackerKCF>::create(param)?;
    //let mut tracker = TrackerKCF::create(param)?;

    let mut bounding_box = opencv::core::Rect::new(100, 100, 50, 50);
    let mut count: i32 = 0;
    let mut m = opencv::core::Mat::default();

    loop
    {
        let time_sleep = time::Duration::from_millis(1);
        thread::sleep(time_sleep);

        match cam.read(&mut m)
        {
            Ok(flag) =>
            {
                if flag == true
                {
                    if count == 0
                    {
                        tracker.init(&m, bounding_box)?;
                    }
                    else
                    {
                        tracker.update(&m, &mut bounding_box)?;
                    }

                    count = count + 1;
                }
            },

            _ => {},
        }
    }

	Ok(())
}

Result
pi@raspberrypi:~/project/rust/honeypot $ cargo run --release --example ucam007s06
warning: unreachable expression
  --> examples/ucam007s06.rs:60:2
   |
32 | /     loop
33 | |     {
34 | |         let time_sleep = time::Duration::from_millis(1);
35 | |         thread::sleep(time_sleep);
...  |
57 | |         }
58 | |     }
   | |_____- any code following this expression is unreachable
59 |
60 |       Ok(())
   |       ^^^^^^ unreachable expression
   |
   = note: `#[warn(unreachable_code)]` on by default

warning: 1 warning emitted

    Finished release [optimized] target(s) in 0.51s
     Running `target/release/examples/ucam007s06`
pure virtual method called
terminate called without an active exception
Aborted
pi@raspberrypi:~/project/rust/honeypot $

I'm going to make a tracking example.
C++, python examples are working well.
So I'm sure that I have made some mistakes.
But I couldn't find what is wrong.
Please help me.
Many thanks in advance.

Can you please share the C++ and Python examples that you used as a source for the Rust code?

import cv2
import sys

#(major_ver, minor_ver, subminor_ver) = (cv2.__version__).split('.')￼

if __name__ == '__main__' :

    # Set up tracker.
    # Instead of MIL, you can also use

    tracker = cv2.TrackerKCF_create()

    # Read video
    video = cv2.VideoCapture(-1)

    # Exit if video not opened.
    if not video.isOpened():
        print("Could not open video")
        sys.exit()

    # Read first frame.
    ok, frame = video.read()
    if not ok:
        print("Cannot read video file")
        sys.exit()

    # Define an initial bounding box
    bbox = (287, 23, 86, 320)

    # Uncomment the line below to select a different bounding box
    bbox = cv2.selectROI(frame, False) # GUI Function

    # Initialize tracker with first frame and bounding box
    ok = tracker.init(frame, bbox)

    while True:
        # Read a new frame
        ok, frame = video.read()
        if not ok:
            break

        # Start timer
        timer = cv2.getTickCount()

        # Update tracker
        ok, bbox = tracker.update(frame)

        # Calculate Frames per second (FPS)
        fps = cv2.getTickFrequency() / (cv2.getTickCount() - timer);

        # Draw bounding box
        if ok:
            # Tracking success
            p1 = (int(bbox[0]), int(bbox[1]))
            p2 = (int(bbox[0] + bbox[2]), int(bbox[1] + bbox[3]))
            cv2.rectangle(frame, p1, p2, (255,0,0), 2, 1)
        else :
            # Tracking failure
            cv2.putText(frame, "Tracking failure detected", (100,80), cv2.FONT_HERSHEY_SIMPLEX, 0.75,(0,0,255),2)

        # Display FPS on frame
        cv2.putText(frame, "FPS : " + str(int(fps)), (100,50), cv2.FONT_HERSHEY_SIMPLEX, 0.75, (50,170,50), 2);

        cv2.imshow('Tracking', frame)

        # Exit if ESC pressed
        k = cv2.waitKey(1) & 0xff
        if k == 27 : break

This is python TrackingKCF example.


Crash after wifi init attempt

I'm getting the following error when attempting to run the two endpoints example. I am using an ESP32 (WROOM) under platformio. I downloaded v1.0.0-beta.3, unzipped it, and copied all of src into lib/esp32-arduino-matter.
I then put all the code from that example into main-matter.cpp and disabled my existing main.cpp. There should be no other code really getting built.
Any pointers on if this an issue on my end would be appreciated. I'm also rebuilding the library myself in case there's any config settings I need to tune.
Error
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13104
load:0x40080400,len:3036
entry 0x400805e4
E (98) wifi:invalid magic number 7, call WIFI_INIT_CONFIG_DEFAULT to init config
E (99) esp_matter_core: Error initializing Wi-Fi stack

abort() was called at PC 0x400d32ec on core 1

Backtrace: 0x40083b89:0x3ffd8470 0x40093ced:0x3ffd8490 0x400994dd:0x3ffd84b0 0x400d32ec:0x3ffd8530 0x400d2df6:0x3ffd8550 0x400d31a1:0x3ffd8580 0x400d2d19:0x3ffd85b0 0x400f9e36:0x3ffd8650

ELF file SHA256: 12f6421243296673

Rebooting...

Platformio.ini
[env]
lib_deps =

build_unflags =
    '-std=gnu++11'

build_flags =
    '-std=gnu++17'

[env:esp32dev]
platform = espressif32
board = esp32dev
framework = arduino

monitor_speed = 115200

board_build.partitions=min_spiffs.csv # I'm not really sure if this is a file I was supposed to create or copy-down or if it's just a magic file name

lib_deps =
    ${env.lib_deps}

build_unflags =
    ${env.build_unflags}

build_flags =
    ${env.build_flags}

esptool.py output
--> esptool.py  --chip esp32 flash_id
esptool.py v4.3
Found 4 serial ports
Serial port /dev/cu.usbserial-0001
Connecting......................
Chip is ESP32-D0WD-V3 (revision v3.0)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: cc:db:a7:16:18:14
Uploading stub...
Running stub...
Stub running...
Manufacturer: 5e
Device: 4016
Detected flash size: 4MB
Hard resetting via RTS pin...

Debugging further, the matter start lines are what trigger the wifi error message:
void setup() {
...
  // Start Matter device
  esp_matter::start(on_device_event);

The lines that actually cause the fault are the ones immediately after that start call:
void setup() {
...
   PrintOnboardingCodes(
     chip::RendezvousInformationFlags(chip::RendezvousInformationFlag::kBLE));

I figured it out. It turned out the default espressif32 platform version was something like 6.0.1 whereas this needs 6.1.0. I didn't catch that until just now after a series of debugging steps. The fix is update your platformio.ini to look like:
[env:esp32devarduino]
platform =<EMAIL_ADDRESS>board = esp32dev
framework = arduino

board_build.partitions=min_spiffs.csv

I'll discuss long-term documentation for in #31.


UX Legal Notice language

Where to find the issue
Page legal notice
Describe the issue
Text is complete in english. But why?

Hi @mrascher-cosee Could you please be more specific about the documents you are referring to? Is this something in the app, one the website, or on Github?

@tkowark sure:
Android -> open menu -> App information ->Legal Notice (Rechtliche Hinweise)

Thank you for the clarification. These are the licenses of third party open source components used within the app and included for legal reasons. As mandated by many of the licenses themselves, the copy of the license provided the project shall be used. Hence, they are all in english.


Refactor - remove payment related logic from summary controller

Is your feature request related to a problem? Please describe.
Related to #786 webhookData is generated too early. So instead of generating it, then amending the data, when the application and payment is successful, then generate the data to be sent to the webhook. All the summary page needs is the totals to show to the user.
Describe the solution you'd like

  makePostRouteHandler() { needs to do less. I think it just needs to redirect to /status - which will do the subsequent rerouting to gov.pay (if it has to)
move generation of webhookData and calls to gov.uk pay API to /status. when a user hits submit on summary page, redirect to /status

It would make more sense to generate webhook and output data in something like runner/src/server/services/statusService.ts. Then statusService will call to webhookService. We should put a new method on webhookService.. something like generateWebhookData, instead of asking the summaryViewModel to do it.. since it's meant to only generate a viewModel for the summary page.

cc @superafroman

@jenbutongit is this done?


Updates allennlp version

I was about to do just this, but got nervous that the other libraries are not updated too.  We'll see if the tests pass ;-)

Aww. Let me re-iterate my opinion that hub tests need to run on every PR, and PRs do not get merged until hub tests finish.
Because I can guarantee you that we fix this now, and next week it'll be broken again.

The trouble is that you can't really make that work, as you'd have to merge code in a separate repo in order to get the PR to pass CI, and that means that the hub CI has to depend on a PR branch of the main repo, and it just doesn't work.


Add a preference for remembering the window state

Original ticket:
https://sourceforge.net/p/djv/feature-requests/76/

Tentatively adding to 2.0.7...

I've added settings for restoring both the window's position and size.


Fixed the index.ipynb Hyperlinks

Hello,
This PR aims to fix #1062. Have fixed all the Hyperlinks with the correct file & directory. Cheers :)

Merged! Thanks!

Merged! Thanks!

Well spotted, thanks @jorgepiloto !

Well spotted, thanks @jorgepiloto !

I have pushed the commits with the requested change

I have pushed the commits with the requested change


Maximum length of the code index sequence

Hello there!
In your paper you mention that: "The maximum length of the code index sequence is T = 50."
Is this number(50) based on the maximum length of motion that is generated (196)?
Consequently, if we want to re-train the model with double the length of generated motion shall we also double T from 50 to 100?
Thank you in advance!

Hi~
(50) is based on the maximum length of motion that is generated (196). We downsample 4 times for the vector quantization, you can set T from 50 to 100 to train the model with double the length (396) of generated motion.

Thank you very much!

Hi~ (50) is based on the maximum length of motion that is generated (196). We downsample 4 times for the vector quantization, you can set T from 50 to 100 to train the model with double the length (396) of generated motion.

Is there an analysis of this? Have you tried different downsample times? For example, if I use T = 25 when training with max_motion_length=196, or T=50 training with max_motion_length=396
Second, I can see that the max_motion_length seems not used anywhere, there is only a process in the dataloader to drop the data that > 200 frames. May I ask why there is such a discrepancy?

We find that downsampling by a factor of 8 may lead to training collapse as well as performance degradation.
We follow previous work[1] to drop the data that > 200 frames for a fair comparison.
[1] https://github.com/EricGuo5513/text-to-motion


How to get access token problem

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
Not sure whether it's an issue.
I am going to retrieve m_accessToken from CBLAuthDelegate in debug mode. However, sometimes it shows the access token but sometimes not (It shows m_accessToken = ""). I know each CA/agent works on its own thread, so is it timing problem? Would you provide some suggestion? (I read the document and it mentions the access token is valid for one hour, so I assume I should receive it (same access token) all the time within one hour until it gets refreshed later, then new token should be shown.
What is the expected behavior?
get access token, something like: "Atza|IwEBIH0ciXtEtlNrwEYb6CXAhOQUHZuGyZnhMrDha-R5IKKdD15NlCJHLTD7dJZn
888****6qi6gtY_a3qGeyc9Xxpe7yWVl2Cbr7anPHss6cXhtbNR92bAHgB-MJn78H0X0Ba1bUR83ywDodV4wv8JCepspSiOhvQkA8JVPXiVP3_7i5ibnwywYKOjGGa0cQTCJ-MrrIwz5gbq9fnrSMMZ2X6NAx0EzuwdUCREG3NGFs5Ga9TfBcKyEcibfi-vQIRyfpvE9rjp9kaD6a8G5E9lnO3OGdwMZvoUF264KaCJLOU2D68bfiv57JPcpwbR1NVa4l8-"
What behavior are you observing?
m_accessToken=""
Provide the steps to reproduce the issue, if applicable:
Running app in debug mode multiple times
Tell us about your environment:
Mac
What version of the AVS Device SDK are you using?
  <1.20.0>

Tell us what hardware you're using:

[X ] Desktop / Laptop
[ ] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[X ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @ssalexa Thanks for reaching out. Could you provide more information about how you are trying to access the authToken? Are you calling getAuthToken() method directly on CBLAuthDelegate?
Since the auth token could be in a process of refreshing, you should make sure that you check for the current authorization state to see if its REFRESHED and then call the getAuthToken() method.
Here is an example in code on how to make sure you always get a valid authToken:
https://github.com/alexa/avs-device-sdk/blob/master/CapabilitiesDelegate/src/DiscoveryEventSender.cpp#L133


Cannot dynamically update TMX map using CocosSharp.Forms with Xamarin.Forms

##Overview
When using CocosSharpView controls hosted in Xamarin.Forms to load a Tiled TMX hex map, however when using methods such as .SetTileGID, RemoveTile or ExtractTile, application hangs then crashes with no error in output window.
##Steps to replicate

Download attached sample
Build and Deploy to Android device or Emulator
Click on ChangeTile Button to call TilemapLayer.RemoveTile
Observe application becomes unresponsive

The methods are being called in the TestMapPage.xaml.cs file within the Handle_Clicked method.
##Expected resulted
To be able to dynamically update the map using .SetTileGID, RemoveTile or ExtractTile methods without having application to freeze

VS bug #732191

@ammarMheir  this doesn't appear to be a components issue. Its eiter and issue with CocosSharp itself, or with Xamarin.Forms.  The Xamarin.Forms references in the sample project are several major releases old.
Regards


Custom widgets

Custom widget implementations need to define several details. It turns out this is not trivial, though the following provides good inspiration for a design.
Size
The widget should return a SizeRules as e.g. Theme::size_rules. This requires some details, e.g. a draw object (to generate text dimensions), the axis, and the DPI.
Drawing
The question here is over which API should user-implemented widgets do their drawing? Some options:

kas::draw::Draw: a fixed draw trait; does not allow themes to influence custom widgets; does not allow direct access to things like wgpu::Device
generic draw object with user-specified bounds (e.g. a hypothetical kas_wgpu::DrawWgpu); allows lower-level drawing but still does not allow theme influence; additionally, use of generics will require some redesign of widget traits
theme: we could require themes to implement a larger API including things like "draw_button_surface"; this allows higher-level draw operations at the cost of a much bigger Theme API
draw trait(s) + theme colour: hybrid approach allowing some theming of custom widgets

Probably the best answer here is the most complex one: extend the Theme trait API and allow direct access to draw traits via generics, along with theme colours.
Alternative (also for size): allow custom widget classes, and use a theme-extension to draw this. This option requires much of the above still: high-level draw operations in the Theme trait, theme colours, access to low-level draw devices.
Event handling
This is covered already by the event::Handler trait (may require tweaking).
Errata
Further details which should be customisable:

alignment
whether the widget accepts keyboard grabs

Providing the custom implementations
We already allow custom widgets (e.g. all make_widget output is a custom widget). We just need the API to specify the details.
Event handling
As noted above, this is already possible via implementation of the parameterised kas::event::Handler trait.
Size + drawing
The straightforward option would be to add Custom(&dyn CustomDrawable) option to kas::class::Class; unfortunately this must be object-safe thus restricts us to the Draw trait defined with kas's core (so not traits from kas_wgpu and not parameterised traits like Theme, although that could possibly be made un-parameterised).
To allow use of parameterised / external APIs, we should instead add draw/size functions to the Widget trait, and allow user implementations.
Misc. functions
Possibly we should move functions like alignments to the Widget trait with a default implementation around the class-provided version (or just drop the class provided version). This implies also that users should be able to implement Widget manually.

Since solutions require modifications to the Widget trait, I will re-open #9.

Custom widgets are now possible using the "theme" helpers SizeHandle and DrawHandle (see also this comment). The details of these two traits still need fleshing out, but this merely means adding/tweaking a feature, not a large change.
Exemplar: the CheckBox widget now does not require any special details to implement (besides the theme providing a "checkbox" drawable element; the theme should draw all standard elements with a lower-level draw API available on demand).


Add OpenSSL FFM code

Also port the TLS testsuite improvements from 10.1.
APR TLS testing uses only the OpenSSL parameter (and skips JSSE and OpenSSL FFM) to avoid looking weird while running only once.

The rationale behind this is long term support of Tomcat 9.0.

FFM support is likely desirable starting with the Java 25 LTS release
Java 25 cannot be used to compile Tomcat 9.0
Testsuite improvements for TLS from 10.1+ are needed in the long run

Ant javac task provides a solution to these issues by specifying a javac executable, which will then be used to compile the FFM related classes. Requiring a FFM enabled javac makes building releases more complicated but works and allows moving forward.
A new ${java-ffm.home} property needs to be specified and needs to point to a JDK 22+ with javac. The javac version used will be logged in the release properties so that the build can be reproduced (although it will obviously be more error prone than before).


Enhance to hide login button for IE <= 9

Button does nothing--it fails silently.  Can't tell what's going on until one opens the debugger console, where one sees the message “Aborted the Sign-In process to avoid sending password over insecure connection.”  Better to just hide the button from the display.

Has anything changed since this conversation ended? I am not able to access the demo briefing book (http://<IP_ADDRESS>/briefingbook/default.htm) on IE 9.
The error received for each failed book:
"RequestError: Unable to load http://<IP_ADDRESS>/briefingbook/proxy/proxy.ashx?https://www.arcgis.com/sharing/rest/content/items/...."

@SaraFlecher Nothing has changed on this. The application (http://<IP_ADDRESS>/briefingbook/default.htm)  is not setup to use https: site protocol so it will not work on IE9. However, we have tested this internal and IE9 does work when properly Secured.


Use dist vs. dir for default output name

You are hard-coding dir vs. dist for your output dir: https://github.com/Reza9472/StaticSiteGenerator/blob/main/index.js#L141

Fixed


fix return type in example

I guess this was a copy/paste mistake?

Can one of the admins verify this patch? (see README)

Thanks.


Limit resources that can be accessed trough the proxy

When using this proxy to expose kubernetes api to external (read: non-trusted) users a very helpful option would be to limit what API groups are exposed trough proxy. This way one can be sure that the external user is only allowed to interact with certain APIs (eg. allow interacting only Deploymens or a cusom resource but do not allow user to list Nodes for example).
Would a PR for his make sense?

I've been kicking around a similar idea, so a PR would be welcome!  I don't want to implement this specific use case though.  I'm thinking either a webhook or a WASM "plugin"?  My thought is that given a payload and user.Info I should be able to make any authorization decision I want.  WDYT?

Not clear why we need to mix authentication and authorization in one tool. Why we can't deny access to some API groups via native RBAC objects in kubernets: clusterroles, roles, rolebindings?

@omelnyk1 RBAC is pretty basic in how it does authorization.  You could use an admission controller too, depending on how you want to implement it.  You may also want to control access based on which network admins come from, which you can't do with RBAC.  It's an additional option.


Token indices sequence length is longer than the specified maximum sequence length for this model

Hi,
I was using llama recipe local inference.
But I get the warning:
Token indices sequence length is longer than the specified maximum sequence length for this model (1998 > 512). Running this sequence through the model will result in indexing errors
I thought the default token length was 4096 but it seems to be 512. Any idea how to explicitly set it to 4096?
Thanks.

Hi @biaoyanf
Could you kindly try with the updated repo and 3.1 models(s) please?
Let me know if you run into any issues


Archery adapter

This moves the cpp-micro benchmark to use ArcheryAdapter, so it will handle all its own measuring, munging, and posting to conbench.
As of writing, my arrow install is still breaking such that I can't call archery benchmark run properly, so I can't do a full conbench cpp-micro end-to-end test, which we should presumably find a way to do before merging.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
20 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.06%) to 87.444%

Files with Coverage Reduction
New Missed Lines
%

benchmarks/cpp_micro_benchmarks.py
8
79.49%

benchmarks/tests/test_cpp_micro_benchmarks.py
12
55.56%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
1372

Relevant Lines:
1569

💛  - Coveralls

Ah crap, I realized I think I forgot to copy all the arrow_info type metadata over to ArcheryAdapter...I'll probably need a little PR to fix that

This is fantastic! Thank you. Especially love:

We should wait on merging this until the arrow_info is copied over to ArcheryAdapter, yeah?
Then we can run a test benchmark at https://buildkite.com/apache-arrow/arrow-bci-benchmark-build-test yeah?

We should wait on merging this until the arrow_info is copied over to ArcheryAdapter, yeah?

Hmm, so currently arrow_info() uses pyarrow.cpp_build_info, and I'm not sure

if the pyarrow version will necessarily correspond to the C++ code being benchmarked (at certain points with my installs it certainly wouldn't; on CI I'm less worried), and
if this should actually be part of ArcheryAdapter, since
a. it would add a dep on pyarrow we don't want, and
b. it would make it explicitly arrow-centric, which brings into question why it lives in benchadapt at all.

So probably we should insert build info from here, but I'm still not sure where the best place to get it from is. We could keep getting it from pyarrow, I guess, which would be the same as what we're currently doing.

This seems like another place where a user of an adapter might need to craft their own version setters, yeah?

This passed finally! So it's ready for review again. I wouldn't necessarily use this as an example of how adapters should be called; there's a lot of mess here to make it integrate with {benchmarks}.


[feature]mourse follow

When one person is painting, other people can know the current painting position, otherwise only by dragging or zooming the canvas to know the current painting position

Hi, closing this as we won't be adding new features to this version of tldraw. Check https://github.com/tldraw/tldraw for the latest!


Fix scrolling behind lightbox on mobile devices

In the first commit, I simply bumped the z-index of the close button because it was impossible to close the lightbox on small mobile screens. It's kind of separate, but was needed to test better on mobile.
This fixes the page scrolling behind the lightbox on mobile devices. The way it works is by setting the HTML element's CSS position to static and setting its top to the body's scrollTop. After the lightbox is closed, the body's scrollTop is set back to what it was prior to the lightbox being opened. This prevents scrolling on mobile devices without the side effect of scrolling to the top of the page.
This is important to implement before swipe to navigate and pinch to zoom gestures.

Works prefect, thanks!


More visual indications for client cell

Description
show some nice, visual indication of certain values for:

treatment count
recent treatment
upcoming treatment

use icons/shapes, colors, bars, ...
if there have been no treatments yet, highlight extra ordinary! as those are not yet treated clients.
Doings

[x] use symbols for count of treatments
[x] recent treatment bar
[x] upcoming treatment via adaptive text only (FTM)
[x] feinschliff colors for recent bar (das lila nicht so darken)

Notes

evtl doch ABC kategorien einfuehren...
in kombination damit waere es toll die clients sortieren zu koennen ;)

done


Typo

Codecov Report

Merging #3 (73b3ded) into main (3cd72aa) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   97.61%   97.61%
=======================================
  Files           4        4
  Lines          42       42
  Branches        8        8
=======================================
  Hits           41       41
  Misses          1        1

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 3cd72aa...73b3ded. Read the comment docs.

Thanks!


raspberry pi: C++ grpc build error

What version of gRPC and what language are you using?
v1.27.3 for C++
What operating system (Linux, Windows,...) and version?
Distributor ID:	Raspbian`
Description:	Raspbian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

What runtime / compiler are you using (e.g. python version or version of gcc)
gcc --version
gcc (Raspbian 8.3.0-6+rpi1) 8.3.0

What did you do?
I followed the build instructions
git clone -b v1.27.3 https://github.com/grpc/grpc
cd grpc
git submodule update --init
mkdir -p cmake/build
cd cmake/build
cmake ../.. -DgRPC_INSTALL=ON -DCMAKE_BUILD_TYPE=Release
make -j4

I also tried v.1.26.0 with the same exact result
What did you expect to see?
Expected to see successful build, it build properly on my x86 Ubuntu 18.04
What did you see instead?
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc: In member function ‘virtual void PerAEADTest_UnalignedInput_Test::TestBody()’:
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc:545:54: error: requested alignment 64 is larger than 8 [-Werror=attributes]
   alignas(64) uint8_t key[EVP_AEAD_MAX_KEY_LENGTH + 1];
                                                      ^
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc:546:58: error: requested alignment 64 is larger than 8 [-Werror=attributes]
   alignas(64) uint8_t nonce[EVP_AEAD_MAX_NONCE_LENGTH + 1];
                                                          ^
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc:547:39: error: requested alignment 64 is larger than 8 [-Werror=attributes]
   alignas(64) uint8_t plaintext[32 + 1];
                                       ^
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc:548:32: error: requested alignment 64 is larger than 8 [-Werror=attributes]
   alignas(64) uint8_t ad[32 + 1];
                                ^
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc:566:75: error: requested alignment 64 is larger than 8 [-Werror=attributes]
   alignas(64) uint8_t ciphertext[sizeof(plaintext) + EVP_AEAD_MAX_OVERHEAD];
                                                                           ^
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc:574:45: error: requested alignment 64 is larger than 8 [-Werror=attributes]
   alignas(64) uint8_t out[sizeof(ciphertext)];
                                             ^
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc: In member function ‘virtual void PerAEADTest_Overflow_Test::TestBody()’:
/home/pi/git/grpc/third_party/boringssl/crypto/cipher_extra/aead_test.cc:588:50: error: requested alignment 64 is larger than 8 [-Werror=attributes]
   alignas(64) uint8_t key[EVP_AEAD_MAX_KEY_LENGTH];
                                                  ^`

Anything else we should know about your project / environment?
I tried it on rasperry pi 4 (2GB RAM) and raspberry pi 3, same exact result.

I have the same problem. Someone have a idea when that could be fix? There are some workaround meanwhile?

I was able to build, here's what I did
1- I edited grpc/third_party/boringssl/CMakeLists.txt and removed -Werror from GCC flags, that way it will continue to build on warnings. The only warnings I saw where in test functions, so I'm assuming the build is ok except I want to run tests on a raspberry pi
2- I added atomic to target_link_libraries in grpc/CMakeLists.txt and +LDFLAGS += -latomic in grpc/Makefile, for raspberry pi std::atomic to link
3- I also had to do the same for protobuf, add +LDFLAGS="$LDFLAGS -latomic" in grpc/third_party/protobuf/configure.ac to link successfully
please let me know if there are any adverse effects that I don't see, it would be nice if the team consider adding the switches for arm raspberry pi builds

This problem itself seems specific to boringssl, and your workaround seems fine to me till boringssl fixes it.
(Having different knobs for different platforms might be worthwhile but I don't think specific problem warrants it.)

@pluggee Could you share where in the file you make the changes detailed in 2 and 3? I'm having the same issue.


Optiboot/Arduino compatibility

Hi,
This is very much what I wanted some time ago. As they say, "Great minds..." or "fools seldom differ"
I'm not sure if you have just implemented an optiboot-like bootloader for flashforth, or if you have made an optiboot+arduino-compatible bootloader that can load both arduino sketches and optiforth binaries
What I was wanting to achieve is:

Make a FF+Optiboot default factory rom for arduinos that runs FF out of the box, but is still fully arduino usable i.e you can load arduino sketches into it. (perhaps/probably losing FF when you do)

a FF binary that is loadable into an optiboot/optiforth arduino from the arduino environment without needing an AVR programmer, and without rendering the AVR incompatible with arduino. Once flashed with Optiboot or Optiforth, FF becomes an option for an arduino user to try, without sacrificing arduino compatibility

The endgame is being able to buy an OptibootFlashForth ready to run off aliexpress
Initial discussion about using Optiboot in FF
Optiboot ref to writing flash

Hi,
I've implemented an Optiboot-LIKE bootloader for my FlashForth-derivate. It's capable of burning Arduino-sketches, but won't start it correctly, because it's left by jumping to the OptiForth-warm-start-vector (in the very last word preceeding the bootloader), instead of jumping to FLASH address 0x0000 to start an Arduino-application.
Furthermore it contains the interrupt-vector-table. Thereby the Do_Spm-vector of actual Optiboot configurations conflicts with the INT0-vector in the OptiForth environment.
Both issues need to be solved to make it an universal Arduino-/OptiForth-bootloader (but there is not a byte left in the bootloader section)
Greets bitflipser

Hi,
I've implemented an Optiboot-LIKE bootloader for my FlashForth-derivate. It's capable of burning Arduino-sketches, but won't start it correctly, because it's left by jumping to the OptiForth-warm-start-vector (in the very last word preceeding the bootloader), instead of jumping to FLASH address 0x0000 to start an Arduino-application.
(Furthermore it contains the interrupt-vector-table. Thereby the Do_Spm-vector of actual Optiboot configurations conflicts with the INT0-vector in the OptiForth environment.)
Correction:
The Do-Spm-vector resides in the upper word of the Reset-vector. So that's NOT an issue.
(Both issues need) Only this issue needs to be solved to make it an universal Arduino-/OptiForth-bootloader (but there is not a byte left in the bootloader section).
Ideas?
Greets bitflipser

Done!
Try 'OptiForth56d_boot_beta.hex' rsp. 'OptiForth56d_beta.hex'.
Greets bitflipser

Very exciting! I wish I was able to try it at the moment (tools locked-down out of reach)
How different is your bootloader from Optiboot?
Do you think it can be mainlined into Optiboot in the future?
I assume it is 512bytes in size.
Are the changes from Flashforth mainline significant or trivial?

After some month of trying and testing:
It's not possible to modify OptiForth to work with Optiboot itself, because Optiboot does not contain the interrupt-vector-table, which is essential for OptiForth to function.
So far OptiForth is written and tested for ATmega328/P only. It is optimized for this controller and does not run on other parts of the AVR-family without changes.   This is one of the reasons it does not fit to the Flashforth mainline.
And: the changes in code, memory usage and data structure are really significant ... again: it does not fit to the Flashforth mainline.
I now released version 5.6d with fully Optiboot-compatible bootloader.