goog.module applying @const on exports makes ES6 classes unable to be subclassed

When using goog.module() with ES6 subclasses [1] and accessControls enabled [2] the compiler errors with:
example/child.js:6: ERROR - example.Child is not allowed to extend final class example.Parent.
  constructor() {
  ^

Per John's comment on CLD this is because exports are marked as @const and @const on classes is an alias for @final. This same code compiles fine with accessControls disabled.
https://groups.google.com/forum/#!topic/closure-library-discuss/rAZZdcL9QM0
[1] example files
example/parent.js
goog.module('example.Parent');

exports = class Parent {
  constructor() {
    console.log('parent');
  }
};

example/child.js
goog.module('example.Child');

const Parent = goog.require('example.Parent');

exports = class Child extends Parent {
  constructor() {
    super();
    console.log('child');
  }
};

example/app.js
goog.module('example.App');

const Child = goog.require('example.Child');

let c = new Child();
console.log(c);

[2] compiler command line
java -jar third_party/closure-compiler/upstream/compiler.jar --compilation_level=ADVANCED_OPTIMIZATIONS --js example/*.js --jscomp_error=* --jscomp_off=inferredConstCheck --hide_warnings_for=[synthetic --language_in=ECMASCRIPT6_STRICT --language_out=ECMASCRIPT5_STRICT --entry_point=goog:example.App

I just came across this myself. Same thing happens with CommonJS Modules.
I'll need a fix for this pretty quick. What are the implications of requiring an explicit @final?

I think if we change from rewriting the JSDoc to using the AST "const" annotation we can get the "const"-ness we need for type inferrence without the @final implication

I think I have the same problem, but disabling accessControl might lead to other issue, is there another workaround?

If we aren't going to fix this, we should disable support for final classes.

We discussed this at the meeting yesterday. There was general support for chaning @final to mean only non-subclassable and @const to mean only non-reassignable, but @blickly seemed to think that @concavelenz had some objection to that at one point. John do you remember what the objection was?

No objection here except that we already use it to mean "@const".  I thought that this was true of jsdoc as well but I don't see that when I looked today.

I'm fine with @final implying @const - just not the other way around.

This is moot if you avoid "default"-style exports in favor of "exports.MyClass = ...".
Still, agree it should be fixed.

I believe this is fixed by https://github.com/google/closure-compiler/commit/ab9bf81.


Add immediate and bitwise expressions

Adding two more expressions we will need in the VPN app.

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Built-in support for stem blocks

I'm using Asciidoctor to convert a programming text book from print to electronic format. Therefore, I need epub, mobi, and PDF to be able to handle math expressions.
Please can you add stem support to asciidoctor-epub3?

Does this work yet? If so, what are the exact steps needed?

I've been trying to follow all the threads and think that the solution is now to use asciimath which will render as mathml in HTML, epub, and pdf.
However, I cannot get it to work in epub3 or pdf.
I have installed the asciimath gem, and an adoc file containing the following:
[asciimath]
++++
k_{n+1} = n^2 + k_n^2 - k_{n-1}
++++

[asciimath]
++++
sqrt(4) = 2
++++

stem:[sqrt(4) = 2]

\$sqrt(4) = 2\$

it all renders fine in HTML with the following command: asciidoctor -a stem sample.adoc
However, if I try using the pdf or epub 3 backends:
asciidoctor -a stem -r asciidoctor-epub3  -b epub3 sample.adoc
asciidoctor -a stem -r asciidoctor-pdf  -b pdf sample.adoc

I get the following error:
asciidoctor: WARNING: conversion missing in backend pdf for stem
I am running asciidoctor v 1.5.4.

@paulvickers are you using asciidoctor-mathematical as described in https://github.com/asciidoctor/asciidoctor-pdf/issues/45. (Alternatively, you can use the mathoid treeprocessor). If loaded correctly, the extension should be replacing stem nodes with image nodes. That way, the converter never even sees the stem nodes.
The fact that Asciidoctor is complaining about the missing conversion for stem tells me you aren't using either the asciidoctor-mathematical or mathoid-treeprocessor extensions. Right now, using an extension is the only approach for converting stem blocks that works in both Asciidoctor PDF and EPUB3.
I know it's frustrating that we don't have an official solution for this yet. We're going to get there. There's just a lot to do right now.

@mojavelinux: here's what happens with both. First, trying to use mathoid:
asciidoctor -a stem -r asciidoctor-epub3 -r./lib/httlap-blocks -r ./lib/mathoid-treeprocessor.rb -b epub3 sample.adoc

Result:
asciidoctor: FAILED: /Volumes/SSD Disk/git Repos/test/sample.adoc: Failed to load AsciiDoc document - asciidoctor: FAILED: /Volumes/SSD Disk/git Repos/test/content.adoc: Failed to load AsciiDoc document - Failed to open TCP connection to localhost:16000 (Connection refused - connect(2) for "localhost" port 16000)

Trying to use AD-mathematical:
asciidoctor -a stem -r asciidoctor-epub3 -r./lib/httlap-blocks -r asciidoctor-mathematical -b epub3 sample.adoc

Result:
conversion missing in epub3 backend for stem
conversion missing in epub3 backend for stem

I have attached the spine and content files (I've appended a .txt extension to allow me to attach them).
content.adoc.txt
sample.adoc.txt

The problem is that none of the stem instances in your sample are handled by the extension. Asciidoctor Mathematical only processes latexmath stem blocks. In your example, you have two AsciiMath stem blocks and one inline stem expression.
Here's a content.adoc that will work:
[latexmath]
++++
k_{n+1} = n^2 + k_n^2 - k_{n-1}
++++

[latexmath]
++++
\sqrt(4) = 2
++++

asciidoctor-mathematical is calculating the image target path incorrectly so it fails to embed when using Asciidoctor PDF unless you set the imagesoutdir attribute to .. This is a known issue. See https://github.com/tstumm/asciidoctor-mathematical/issues/8.

First, trying to use mathoid:

The mathoid extension requires some extra setup that is documented here: https://github.com/asciidoctor/asciidoctor-extensions-lab/blob/master/lib/mathoid-treeprocessor/setup.sh. However, I haven't tested it recently. It is definitely still lab material :)

D'oh! [latexmath] it is. This then has the unfortunate result of super jumbo sized equations in the epub3 output. Seems like asciidoctor-mathematical isn't the all round performer I need it to be. I want to generate HTML, pdf, epub, and Kindle mobi with some mathematical content in all versions. At this point I'm tempted just to render all the equations as pngs myself and embed them as images. Grrrr....
Therefore, I tried the mathoid-treeprocessor route again but still can't get it to work.

setup.sh seems to be out of date. I replaced the link to the wikimedia git repo with
git clone -b integration --recursive https://github.com/mojavelinux/mathoid

which makes that bit of the script not fall over and provides a mathoid folder with main.js/
I have manually installed npm, librsvg (via Homebrew), and phantomjs as the setup.sh was throwing errors. Now it runs without comment.
The next bit in setup.sh says:
# Make sure you can run the following command:
#
# cd mathoid
# phantomjs main.js
#
# Then visit the following URL in your browser:
#
# http://localhost:16000/?q=x^2&type=asciimath
#
# You should see x to the power of 2 rendered.

The browser session using http://localhost:16000/?q=x^2&type=asciimath gives the error:
This page contains the following errors:

error on line 1 at column 1252: Attribute xlink:href redefined
Below is a rendering of the page up to the first error.

(there is nothing after that).
When I go to my test project and run:
asciidoctor  -r asciidoctor-epub3 -r mathoid-treeprocessor -b epub3 sample.adoc

I get the error
paulvickers@PaulVickerssPro test $ asciidoctor  -r asciidoctor-epub3 -r mathoid-treeprocessor -b epub3 sample.adoc --trace
/usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- mathoid-treeprocessor (LoadError)
	from /usr/local/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /usr/local/bin/gems/asciidoctor-1.5.4/lib/asciidoctor/cli/options.rb:219:in `block in parse!'
    from /usr/local/bin/gems/asciidoctor-1.5.4/lib/asciidoctor/cli/options.rb:217:in `each'
    from /usr/local/bin/gems/asciidoctor-1.5.4/lib/asciidoctor/cli/options.rb:217:in `parse!'
    from /usr/local/bin/gems/asciidoctor-1.5.4/lib/asciidoctor/cli/options.rb:33:in `parse!'
    from /usr/local/bin/gems/asciidoctor-1.5.4/lib/asciidoctor/cli/invoker.rb:21:in `initialize'
    from /usr/local/bin/gems/asciidoctor-1.5.4/bin/asciidoctor:12:in `new'
    from /usr/local/bin/gems/asciidoctor-1.5.4/bin/asciidoctor:12:in `<top (required)>'
    from /usr/local/bin/asciidoctor:22:in `load'
    from /usr/local/bin/asciidoctor:22:in `<main>'

Is this a problem with my ruby installation, or a problem with mathoid? I'm puzzled by the reference to site_ruby as the ruby that gets executed at the command line is the one installed by homebrew.

UPDATE: facepalm
Checked Activity Monitor which showed an orphaned phantomjs process running. Killed that and ran again and got a pdf as output but with no math in it. Using the test.adoc from the extensionslab repo:
= _Precompiled_ Math!

[stem#equation1]
++++
"d"(bbp,bbq) = sqrt((p_1 - q_1)^2 + (p_2 - q_2)^2)
++++

Compile with
asciidoctor  -r asciidoctor-pdf -r ./lib/mathoid-treeprocessor  -b pdf test.adoc --trace

Get the following output:
asciidoctor: WARNING: could not embed image: /Volumes/SSD Disk/git Repos/test/equation1.svg; Duplicate attribute "xlink:href"
Line: 23
Position: 7155
Last 80 unconsumed characters:

The generated svg file is not an equation but text containing an error message "This page contains the following errors..."

Seems like asciidoctor-mathematical isn't the all round performer I need it to be. I want to generate HTML, pdf, epub, and Kindle mobi with some mathematical content in all versions. At this point I'm tempted just to render all the equations as pngs myself and embed them as images.

That's why the mathoid processor is such an all-around champion.
I'll have a look at the mathoid processor and see if I can bring it up to date. That should hopefully help move things along. Stay tuned.

I'll have a look at the mathoid processor and see if I can bring it up to date. That should hopefully help move things along. Stay tuned.

That'll be great, thanks! Any idea what's causing the epub3 backend to throw the to_ios error?

Any idea what's causing the epub3 backend to throw the to_ios error?

9/10 it's not adhering the the project structure requirements describe at https://github.com/asciidoctor/asciidoctor-epub3#declaring-the-spine

Hmmm.... Okay, thought I'd already got that covered. I did realise that some of the declarations were before the book title, so here's the revised spine:
= TEST
Paul Vickers
v1.0, 2014-04-15
:doctype: book
:producer: Asciidoctor
:keywords: Asciidoctor, samples, e-book, EPUB3, KF8, MOBI, Asciidoctor.js
:copyright: CC-BY-SA 3.0
:icons: font
:imagesdir: Images
:stem:

include::content.adoc[]

And here's the content.adoc
Here is some maths in a block

[asciimath]
++++
k_{n+1} = n^2 + k_n^2 - k_{n-1}
++++

And another block.
[asciimath]
++++
sqrt(4) = 2
++++

Here is some inline maths asciimath:[a=4^2].

The command: asciidoctor  -r asciidoctor-epub3 -r ./lib/mathoid-treeprocessor -b epub3 sample.adoc --trace executes without errors now. But here's the output:

I notice though in https://github.com/asciidoctor/asciidoctor-extensions-lab/issues/71#issuecomment-240054559 that the whole mathoid architecture has changed. Mine is still using phantomJs so I'll take a look at the newer version now.

Asciidoctor EPUB3 currently requires the imagesdir attribute to be images
(all lowercase).
Even then, we'll need to make sure the images make it into the correct
directory for use with the EPUB3 converter. I checked PDF, but not EPUB3
yet.

With the :imagesdir: variable correctly set:

The stem blocks are huge, and the inline still not being rendered as math.

:+1:
The sizing is the next step. Right now, the images will expand to the space they are given. We can allow a width attribute to be defined on the stem block, then pass that to the image block that the extension creates.
It's true that inline stem macros are not yet supported. The challenge here is that Asciidoctor doesn't provide a way to hook into inline nodes in a Treeprocessor yet. We'll have to take a different approach, perhaps by extending the converter.

https://github.com/fabmen/asciidoctor-epub3/commit/95addc15f501dea3ec70b53ef8aedf31e4254311 has some code using AsciiMath to convert stem blocks to MathML, possibly we should use it.

Okay, it's finally time to fix this six-year-old issue. #346 adds support for MathML blocks. It doesn't handle inline stems (yet), I plan to add that soon.


GH-36479: [C++][FlightRPC] Use gRPC version detected by find_package()

Rationale for this change
We don't need to use try_compile() by using gRPC version detected by find_package().
What changes are included in this PR?
Use  gRPC version detected by find_package().
Are these changes tested?
Yes.
Are there any user-facing changes?
No.

Closes: #36479

@github-actions crossbow submit -g nightly-tests -g nightly-packaging -g nightly-release


Show a toast message if there is an available update to a connected KeepKey

Overview
We currently alert a KeepKey user of any available updates to their device's firmware or bootloader in the KeepKey settings menu.
We should make this more visible by showing a toast as well.
References and additional details
Use the same logic as the menu system to determine update status.
We have a useKeepKeyVersions.ts hook available that tracks this.
Acceptance Criteria
A toast displays when a connected KeepKey has an available update.
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
One day.
Sponsor / Stakeholder
GitHub: 0xApotheosis
Discord: 0xApotheosis#2503
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

@NeOMakinG to pick this up once Product has reviewed.

To make the toast clickable we will need to use a custom alert component, see the update app toast in App.tsx. We should use the solid variant of the alert component.

@reallybeard @NeOMakinG does this still need product review or can we remove that tag?

@reallybeard @NeOMakinG does this still need product review or can we remove that tag?

Should we display the toast only one time at the first connection? And then store the fact that it's been dismissed for a couple of days until showing it again?
Or should we display it every time we visit the app?

@reallybeard @NeOMakinG does this still need product review or can we remove that tag?

Should we display the toast only one time at the first connection? And then store the fact that it's been dismissed for a couple of days until showing it again?
Or should we display it every time we visit the app?

Its in their best interest to update, so I would every time they connect the wallet but haven't update it yet.

@reallybeard @NeOMakinG does this still need product review or can we remove that tag?

Should we display the toast only one time at the first connection? And then store the fact that it's been dismissed for a couple of days until showing it again?
Or should we display it every time we visit the app?

Its in their best interest to update, so I would every time they connect the wallet but haven't update it yet.

Thanks for the reply, considering we don't need product input anymore :+1:


Change 2D navigation mesh baking to use floating point coordinates

Replaces internal uses of Clipper2 integer structs to their floating point equivalents.
Solves https://github.com/godotengine/godot/issues/87138.
Note that the float structs are slower because they need to up- and downscale everything to an integer grid.
In turn this avoids baking problems caused by geometry layouts with sloppy float decimal points.

Thanks!


Use buffered iterators to speed up the search

Currently, op_iter functions use Vec to collect op results to vec and returns vec.into_iter().
I recommend use buffered lock-free iterator generator crate - buter or similar
For example, it will look like this:
//! before
let mut vec = Vec::with_capacity(...);
self.each(..., |link| {
    vec.push(link);
    Continue
});
vec.into_iter()

//! after
let writer = self.buter.writer();
self.each(..., |link| {
    writer.extend(Some(link));
    Continue
});
writer.into_iter()

You also need to create benches to compare with the old implementation.
Check out iter bench


When DynamoDB DescribeEndpoints is used, wrong scheme may be tacked on the result

Describe the bug
I saw this problem in the context of the new AWS DynamoDB Shell (https://github.com/awslabs/dynamodb-shell), which is written using the AWS C++ SDK.
I ask it to use a specific endpoint URL, e.g., http://localhost:8000 (i.e., a local installation such as DynamoDB Local or ScyllaDB Alternator).
It turns out that the C++ SDK doesn't use this endpoint URL immediately, but rather tries to run a DescribeEndpoints request on this URL, to get a better (?) endpoint. The relevant code looks like this (it's repeated many times in generated code):
      DescribeEndpointsRequest endpointRequest;
      auto endpointOutcome = DescribeEndpoints(endpointRequest);
      if (endpointOutcome.IsSuccess() && !endpointOutcome.GetResult().GetEndpoi
nts().empty())
      {
        const auto& item = endpointOutcome.GetResult().GetEndpoints()[0];
        ...
        endpoint = Aws::String(SchemeMapper::ToString(m_clientConfiguration.scheme)) + "://" + item.GetAddress();

The problem here is that no matter what the original endpoint URL was, the new endpoint built here will always use some default scheme (and that defaults to "https"), which in this example is incorrect - the local installation used http, not https.
Note that this problem is not reproducible in DynamoDB Local, because it appears that (I don't know why) that implementation simply doesn't implement the DescribeEndpoints request - so the SDK skips the attempt to rediscover the endpoint. But ScyllaDB Alternator does implement DescribeEndpoints, so this bug is exposed.
Expected Behavior
The C++ SDK should either trust the given endpoint (like http://localhost:8000) without second-guessing it with a DescribeEndpoints request, or if DescribeEndpoints is used, it should take the scheme not from some default configuration (namely, "https") but rather from the original endpoint (in this example, "http").
Current Behavior
When running DDBSH_ENDPOINT_OVERRIDE=http://localhost:8000 ddbsh against ScyllaDB Alternator serving DynamoDB API on http://localhost:8000, we get the following output:
ddbsh - version 0.6.1
[ddbsh.cpp, 188], Connection Failed. . .
	curlCode: 35, SSL connect error
us-east-1 (*)>

Note the bizarre "SSL connect error" coming from an http, not https endpoint. With wireshark, we can see what really happened. The C++ SDK sent a DescribeEndpoints to http://localhost:8000 and it responded with localhost:8000. The C++ SDK then tacked on the beginning an "https://" (the default scheme in the default client configuration), and came up with a new endpoint URL https://localhost:8000, so it then started sending SSL requests on port 8000, which is an unencrypted HTTP server, so it didn't work (wireshark shows that the broken request is repeated multiple times, until finally giving many seconds later and producing this SSL connect error.
Reproduction Steps
See details above.
As I noted above, this issue cannot be reproduced on DynamoDB Local because they chose not to implement the DescribeEndpoints requests, so the broken scheme logic is skipped. But it can reproduced on ScyllaDB Alternator which does implement DescribeEndpoints. I guess it can also be reproduced on AWS DynamoDB if a user deliberately chooses to use the http scheme but this code will revert it to use https instead (the result will be working, but use an unintended scheme).
Possible Solution
No response
Additional Information/Context
No response
AWS CPP SDK version used
1.11.107
Compiler and Version used
gcc (GCC) 12.3.1
Operating System and version
Linux, Fedora 37

By the way, looking more closely at the SDK code (https://github.com/aws/aws-sdk-cpp/blob/main/generated/src/aws-cpp-sdk-dynamodb/source/DynamoDBClient.cpp), it seems that if the DescribeEndpoints request fails (as I believe is the case in DynamoDB Local), it is retried before every single request. This too, I think, is a bug. It makes sense to cache (even if for a relatively short duration) the knowledge that the request failed instead of retrying it before each and every single request.

Hello @nyh ,
Thank you very much for your detailed submission. We really appreciate you sharing your feedback and work.
You are right the SDK should be using the endpoint provided in the endpoint override. It would also be a better behavior to not have to change the default scheme through the client configuration when an endpoint is provided through endpoint override.
I will work on a fix for this issue and will post an update here once it is released.
Thank you once again for your time and collaboration.
Sincerely,
Yasmine

This should be fixed in 1.11.148.
Thank you very much for bringing this up to our attention.
Best regards,
Yasmine


[20.09]  pythonPackages.pyscreenshot: add missing dependencies

Motivation for this change
Backport to release-20.09 the following PRs (apparently, this has not been done):

#98895
#98898
#98922

Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Adding an imports check
diff --git a/pkgs/development/python-modules/pyscreenshot/default.nix b/pkgs/development/python-modules/pyscreenshot/default.nix
index 7967caf6178..dc92239fbbb 100644
--- a/pkgs/development/python-modules/pyscreenshot/default.nix
+++ b/pkgs/development/python-modules/pyscreenshot/default.nix
@@ -28,6 +28,8 @@ buildPythonPackage rec {
   # recursive dependency on pyvirtualdisplay
   doCheck = false;

+  pythonImportsCheck = [ "pyscreenshot" ];
+
   meta = with lib; {
     description = "python screenshot";
     homepage = "https://github.com/ponty/pyscreenshot";

reveals a missing pillow dependency:
Check whether the following modules can be imported: pyscreenshot
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "<string>", line 1, in <lambda>
  File "/nix/store/z65l1jqvxa58zzwwa3bvglb6asj4y8cv-python3-3.8.5/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/nix/store/zwbrw49cj30zhkfybn656jli14fznwp8-python3.8-pyscreenshot-2.2/lib/python3.8/site-packages/pyscreenshot/__init__.py", line 4, in <module>
    from pyscreenshot.childproc import childprocess_backend_version
  File "/nix/store/zwbrw49cj30zhkfybn656jli14fznwp8-python3.8-pyscreenshot-2.2/lib/python3.8/site-packages/pyscreenshot/childproc.py", line 5, in <module>
    from pyscreenshot.imcodec import codec
  File "/nix/store/zwbrw49cj30zhkfybn656jli14fznwp8-python3.8-pyscreenshot-2.2/lib/python3.8/site-packages/pyscreenshot/imcodec.py", line 3, in <module>
    from PIL import Image
ModuleNotFoundError: No module named 'PIL'
builder for '/nix/store/n1ryi6j4mjm17ddjrxs62qfic7z2wnmc-python3.8-pyscreenshot-2.2.drv' failed with exit code 1

Yes, you are right. I’ll add a PR ASAP to master and backport it here once accepted. Meanwhile, I mark this pr as draft.

Result of nixpkgs-review pr 99244 1

8 packages built:

python27Packages.entrypoint2
python27Packages.pyscreenshot
python37Packages.entrypoint2
python37Packages.mss
python37Packages.pyscreenshot
python38Packages.entrypoint2
python38Packages.mss
python38Packages.pyscreenshot

Yes, you are right. I’ll add a PR ASAP to master and backport it here once accepted. Meanwhile, I mark this pr as draft.

Upstream should also be notified that they aren't declaring a necessary dependency


build fails on AArch64 (A64FX), Fedora 33

... because it is made for x86-64 only?

There are compilers for AArch64 here: https://github.com/ldc-developers/ldc/releases
What error do you get in particular?

(base) [jw@cn06 silq]$ ./dependencies-release.sh
--2021-04-07 09:03:17--  https://github.com/ldc-developers/ldc/releases/download/v1.22.0/ldc2-1.22.0-linux-x86_64.tar.xz
Connecting to <IP_ADDRESS>:8080... connected.
Proxy request sent, awaiting response... 302 Found
Location: https://github-releases.githubusercontent.com/2174666/34d26d00-b01c-11ea-871d-e621aa0a9b88?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210407%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210407T070317Z&X-Amz-Expires=300&X-Amz-Signature=b0f1d61aafcaff275ee6f059d5447029b1f716485f4a2682f83cf043f422da09&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=2174666&response-content-disposition=attachment%3B filename%3Dldc2-1.22.0-linux-x86_64.tar.xz&response-content-type=application%2Foctet-stream [following]
--2021-04-07 09:03:17--  https://github-releases.githubusercontent.com/2174666/34d26d00-b01c-11ea-871d-e621aa0a9b88?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20210407%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210407T070317Z&X-Amz-Expires=300&X-Amz-Signature=b0f1d61aafcaff275ee6f059d5447029b1f716485f4a2682f83cf043f422da09&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=2174666&response-content-disposition=attachment%3B filename%3Dldc2-1.22.0-linux-x86_64.tar.xz&response-content-type=application%2Foctet-stream
Connecting to <IP_ADDRESS>:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 57756788 (55M) [application/octet-stream]
Saving to: 'ldc2-1.22.0-linux-x86_64.tar.xz'
ldc2-1.22.0-linux-x86_64.tar.  89%[===========================================>      ]  49.16M  5.61MB/s    eta 2s     ^C
(base) [jw@cn06 silq]$
It downloads a x86-64 type version for ldc. yum install ldc works on my machine.


What's the issue with javascript dynamic hooks ?

Issues with Dynamic-Hooks RC-1 #3250
Could someone explain why it's not working as intended ?

Please don't open a new issue to ask when another issue will be fixed.


Get a empty folder(~)   when decrypting the files

RMS SDK generates a empty folder when decrypting the files, . Please see the following screenshot:

Fixed in: https://github.com/AzureAD/rms-sdk-for-cpp/pull/107


Appstudio update test-custom-default-branch-bxhu

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nyrh-on-pull-request-
creating pipelinerun test-simple-build-nyrh-on-pull-request- in namespace build-e2e-aqmu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-ufgi-on-pull-request-
creating pipelinerun test-simple-build-ufgi-on-pull-request- in namespace build-e2e-aqmu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-mcmm-on-pull-request-
creating pipelinerun test-simple-build-mcmm-on-pull-request- in namespace build-e2e-aqmu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-nwtb-on-pull-request-
creating pipelinerun test-simple-build-nwtb-on-pull-request- in namespace build-e2e-aqmu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-lqle-on-pull-request-
creating pipelinerun test-simple-build-lqle-on-pull-request- in namespace build-e2e-aqmu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-simple-build-imul-on-pull-request-
creating pipelinerun test-simple-build-imul-on-pull-request- in namespace build-e2e-aqmu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test-annotations-mijr-on-pull-request-
creating pipelinerun test-annotations-mijr-on-pull-request- in namespace build-e2e-aqmu-tenant has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request


riak-cs-debug update

There were a lot of updates made to riak-debug that have not yet been pulled into riak-cs-debug. This PR looks to correct that.
These changes have not yet been tested, though, and definitely need to be checked on Ubuntu and Solaris before being merged.

Looks nice, but I don't have Solaris env. Anybody?

The script will hang forever if there is no rel/riak-cs/bin/.././data/generated.configs/app.*.config file, e.g., because CS hasn't been run for the first time yet.
But aside from that, it appears to work correctly on Solaris: SunOS oi151a-64-0 5.11 oi_151a i86pc i386 i86pc Solaris

On Ubuntu, this script failed:
root@vagrant-ubuntu-trusty-64:~# riak-cs-debug
....EE../usr/sbin/riak-cs-debug: 577: [: !: unexpected operator
<EMAIL_ADDRESS>

Thank you for the effort to update from latest riak-debug. :bowtie: I left a few comments.

Changes are included in #1236.


compiling for iOS doesn't work

Describe the bug
Hi,
I can't compile a freshly created app, neither in cli, nor in Xcode.
It might be because of my setup - but the errors look frb related.
Steps to reproduce

flutter_rust_bridge_codegen create neo

cd neo

flutter pub get

flutter_rust_bridge_codegen generate

flutter run
... leads to the first error: Failed to build iOS app
Lexical or Preprocessor Issue (Xcode): 'UIKit/UIKit.h' file not found

open iOS/Runner.xcworkspace

run in xcode
... leads to the second error: '/Users/patmuk/Library/Developer/CoreSimulator/Devices/6066442D-018C-43C8-9352-126293114557/data/Containers/Bundle/Application/62BF8BF5-BC44-4C27-A506-7AA2CC104BD9/Runner.app/Frameworks/rust_lib_neo.framework/rust_lib_neo' (no such file), '/usr/lib/rust_lib_neo.framework/rust_lib_neo' (no such file, not in dyld cache), 'rust_lib_neo.framework/rust_lib_neo' (no such `file),

Logs
1. error (this might be related to my setup on my machine):

› flutter run
Launching lib/main.dart on iPhone 15 Pro in debug mode...
Running Xcode build...
 └─Compiling, linking and signing...                        600ms
Xcode build done.                                            4.7s
Failed to build iOS app
Lexical or Preprocessor Issue (Xcode): 'UIKit/UIKit.h' file not found
/Users/patmuk/code/own/sherry/examples/clean_setup/neo/build/ios/Debug-iphonesimulator/Flutter.framework/Headers/FlutterAppDelegate.h:7:8

Parse Issue (Xcode): Could not build module 'Flutter'
/Users/patmuk/code/own/sherry/examples/clean_setup/neo/ios/Runner/GeneratedPluginRegistrant.h:9:8

Could not build the application for the simulator.

[        ] Error launching application on iPhone 15 Pro.
[   +1 ms] "flutter run" took 10,521ms.
[   +1 ms]
           #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
           #1      RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:815:9)
           <asynchronous suspension>
           #2      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1389:27)
           <asynchronous suspension>
           #3      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
           <asynchronous suspension>
           #4      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #5      FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:355:9)
           <asynchronous suspension>
           #6      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
           <asynchronous suspension>
           #7      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)
           <asynchronous suspension>
           #8      run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:119:9)
           <asynchronous suspension>
           #9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
           <asynchronous suspension>
           #10     main (package:flutter_tools/executable.dart:90:3)
           <asynchronous suspension>

The second error in Xcode - this looks like FRB related:
This happens after the build, while starting the app in the simulator:
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument(s): Failed to load dynamic library 'rust_lib_neo.framework/rust_lib_neo': dlopen(rust_lib_neo.framework/rust_lib_neo, 0x0001): tried: '/Users/patmuk/Library/Developer/Xcode/DerivedData/Runner-ecekxoupksbccjbtmtxskagsrudn/Build/Products/Debug-iphonesimulator/rust_lib_neo.framework/rust_lib_neo' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRootrust_lib_neo.framework/rust_lib_neo' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/usr/lib/swift/rust_lib_neo.framework/rust_lib_neo' (no such file), '/usr/lib/swift/rust_lib_neo.framework/rust_lib_neo' (no such file, not in dyld cache), '/Users/patmuk/Library/Developer/CoreSimulator/Devices/6066442D-018C-43C8-9352-126293114557/data/Containers/Bundle/Application/62BF8BF5-BC44-4C27-A506-7AA2CC104BD9/Runner.app/Frameworks/rust_lib_neo.framework/rust_lib_neo' (no such file), '/usr/lib/rust_lib_neo.framework/rust_lib_neo' (no such file, not in dyld cache), 'rust_lib_neo.framework/rust_lib_neo' (no such file), '/Library/Developer/CoreSimulator/Volumes/iOS_21E213/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 17.4.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/rust_lib_neo.framework/rust_lib_neo' (no such file)
#0      _open (dart:ffi-patch/ffi_dynamic_library_patch.dart:11:43)
#1      new DynamicLibrary.open (dart:ffi-patch/ffi_dynamic_library_patch.dart:22:12)
#2      new ExternalLibrary.open (package:flutter_rust_bridge/src/platform_types/_io.dart:39:47)
#3      loadExternalLibraryRaw.<anonymous closure>.<anonymous closure> (package:flutter_rust_bridge/src/loader/_io.dart:72:29)
#4      _tryOpen (package:flutter_rust_bridge/src/loader/_io.dart:93:20)
#5      loadExternalLibraryRaw.<anonymous closure> (package:flutter_rust_bridge/src/loader/_io.dart:68:22)
#6      loadExternalLibraryRaw.tryAssumingNonPackaged (package:flutter_rust_bridge/src/loader/_io.dart:49:22)
#7      loadExternalLibraryRaw (package:flutter_rust_bridge/src/loader/_io.dart:66:12)
#8      loadExternalLibrary (package:flutter_rust_bridge/src/loader/_io.dart:14:10)
#9      BaseEntrypoint._loadDefaultExternalLibrary (package:flutter_rust_bridge/src/main_components/entrypoint.dart:129:13)
#10     BaseEntrypoint.initImpl (package:flutter_rust_bridge/src/main_components/entrypoint.dart:48:31)
#11     RustLib.init (package:neo/src/rust/frb_generated.dart:25:20)
#12     main (package:neo/main.dart:6:17)
#13     _runMain.<anonymous closure> (dart:ui/hooks.dart:301:23)
#14     _delayEntrypointInvocation.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:297:19)
#15     _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)

As far as I remember the file in question was called 'rust_builder', not 'rust_lib_neo'? The rename sounds good, but doesn't seem to work for me.

### Expected behavior

_No response_

### Generated binding code

_No response_

### OS

MacOS 14.3.1.

### Version of `flutter_rust_bridge_codegen`

2.0.0-dev.32

### Flutter info

```shell
flutter doctor -v
[✓] Flutter (Channel stable, 3.19.5, on macOS 14.3.1 23D60 darwin-arm64, locale en-US)
    • Flutter version 3.19.5 on channel stable at /opt/homebrew/Caskroom/flutter/3.19.2/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 300451adae (3 weeks ago), 2024-03-27 21:54:07 -0500
    • Engine revision e76c956498
    • Dart version 3.3.3
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /nix/store/vb5b7nzyxxviz368hbjaz4985crlv88d-android-sdk-env/share/android-sdk
    • Platform android-34, build-tools 30.0.3
    • ANDROID_HOME = /nix/store/vb5b7nzyxxviz368hbjaz4985crlv88d-android-sdk-env/share/android-sdk
    • ANDROID_SDK_ROOT = /nix/store/vb5b7nzyxxviz368hbjaz4985crlv88d-android-sdk-env/share/android-sdk
    • Java binary at: /nix/store/4p6pjavr2q7m94vbbxs6hjz22rwq8chs-zulu-ca-jdk-17.0.10/bin/java
    • Java version OpenJDK Runtime Environment Zulu17.48+15-CA (build 17.0.10+7-LTS)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.2

[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] VS Code (version 1.79.2)
    • VS Code at /Users/patmuk/Library/Mobile Documents/com~apple~CloudDocs/Desktop/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (2 available)
    • iPhone 15 Pro (mobile) • 6066442D-018C-43C8-9352-126293114557 • ios          • com.apple.CoreSimulator.SimRuntime.iOS-17-4 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64 • macOS 14.3.1 23D60 darwin-arm64

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Version of clang++
16.0.6
Additional context
I assume that this is very much related to the setup on my machine ... I tried doing this with nix, but gave up and installed the toolchain normally (except clang (InstalledDir: /nix/store/ww7lviar1xyd5az6y763yp5wigvwn3m8-clang-16.0.6/bin) which should not matter).
I would appreciate any help pointing me in the right direction to solve the issue!
flutter create and cargo create work both fine - thus it is something in FRB (but most probably in rust_builder).

Oh, actually flutter create nf and flutter run lead to the same error in cli ('UIKit/UIKit.h' file not found), but the project runs fine in Xcode. So FRB related might only be my second issue.
(Nevertheless, any help with the first would be great as well!)

Hmm, if flutter create yields error, then I guess it may be more Flutter-related, and maybe ask in flutter github / stackoverflow / etc. Btw, If XCode runs well, I guess environment variables (especially those related to header search paths) may worth a check.

Yes, thanks - I think as well that it is more environment related.
But the second issue ‚rust-lib-neo‘ not found, sounds FRB related (?). However, I saw that I installed cocoapods via nix as well - will undo that and report if that helped.

But the second issue ‚rust-lib-neo‘ not found, sounds FRB related (?).

I also get quite confused... since it works pretty well on CI as well as real computers. Anyway, if your first problem is solved and 2nd one is still there, feel free to ping me!

@fzyzcjy I can't believe, but installing cocoapods via sudo gem install cocoapods and removing it from nix fixed the problem!
All is fine, in cli and Xcode now.
I assume that nix installed an old version of cocoapods, as it used the old ruby shipped with MacOS. I installed the latest ruby and latest cocoapods - and now both issues are solved :)
As always, thanks for your quick help @fzyzcjy and sorry for bothering!

Happy to see it is solved!


Orbit issues

Hello, whenever i have tried to use orbit caroussel wich appear when i click on a lightbox the caroussel doesn't load and i have to resize the windows

to anyone who have the same problem as me you have to put $(window).trigger('resize') in the javascript


Jest migration

Coverage remained the same at 100.0% when pulling 26a34423cb67fc5b584de4fdfc5138cdf9052cd9 on features/jest into e69dc0c578d3c268f1e17171bd7ff5c9773acfc6 on master.

Coverage remained the same at 100.0% when pulling 26a34423cb67fc5b584de4fdfc5138cdf9052cd9 on features/jest into e69dc0c578d3c268f1e17171bd7ff5c9773acfc6 on master.

Coverage remained the same at 100.0% when pulling 26a34423cb67fc5b584de4fdfc5138cdf9052cd9 on features/jest into e69dc0c578d3c268f1e17171bd7ff5c9773acfc6 on master.


Explicitly enable lead controller resource

Description
This PR explicitly enables lead controller resource.
The purpose of this feature is to logically separate per-table functionality in all clusters.
After enabling lead controller resource, the controller host listed under CONTROLLER/LEADER ZNode only denotes the helix lead controller in the cluster.
The lead Pinot controller for each of the tables can be found by the following APIs:
Get the leaders for all the tables in the cluster
GET /leader/tables
Given a table name, return the partition id and lead controller instance id
GET /leader/tables/{tableName}
The RESOURCE_ENABLED config is to be removed whenever we release 0.8 or later version of Pinot.
Details can be found in doc: https://cwiki.apache.org/confluence/display/PINOT/Controller+Separation+between+Helix+and+Pinot
Upgrade Notes
Does this PR prevent a zero down-time upgrade? (Assume upgrade order: Controller, Broker, Server, Minion)

[ ] Yes (Please label as backward-incompat, and complete the section below on Release Notes)

Does this PR fix a zero-downtime upgrade introduced earlier?

[ ] Yes (Please label this as backward-incompat, and complete the section below on Release Notes)

Does this PR otherwise need attention when creating release notes? Things to consider:

New configuration options
Deprecation of configurations
Signature changes to public methods/interfaces
New plugins added or old plugins removed

[ ] Yes (Please label this PR as release-notes and complete the section on Release Notes)

Release Notes
This PR explicitly enabled lead controller resource. The controller host listed in CONTROLLER/LEADER ZNode only denotes the helix lead controller in the cluster. The actual logic (like controller periodic tasks, realtime segment completion) of Pinot lead controller is distributed to each of the Pinot only controllers.
After enabling this feature, Helix controller and Pinot controller don't have to be run in the same hardware.
Documentation
See https://cwiki.apache.org/confluence/display/PINOT/Controller+Separation+between+Helix+and+Pinot

Codecov Report

Merging #6725 (8603bff) into master (8dbb70b) will decrease coverage by 30.21%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master    #6725       +/-   ##
===========================================
- Coverage   73.83%   43.61%   -30.22%
===========================================
  Files        1396     1402        +6
  Lines       67765    67915      +150
  Branches     9807     9821       +14
===========================================
- Hits        50035    29622    -20413
- Misses      14485    35816    +21331
+ Partials     3245     2477      -768

Flag
Coverage Δ

integration
43.61% <100.00%> (+0.09%)
:arrow_up:

unittests
?

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

Impacted Files
Coverage Δ

...ot/controller/helix/core/util/HelixSetupUtils.java
86.51% <100.00%> (-1.27%)
:arrow_down:

...c/main/java/org/apache/pinot/common/tier/Tier.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/data/MetricFieldSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/stream/LongMsgOffset.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/core/util/fst/FSTBuilder.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/pinot/spi/config/table/TableType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/pinot/spi/data/DateTimeFieldSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/pinot/spi/env/PinotConfiguration.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/pinot/core/upsert/RecordLocation.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../org/apache/pinot/spi/data/DimensionFieldSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 896 more

Continue to review full report at Codecov.

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


Echo is not finding any devices

I installed ha-bridge, tried to discover new devicas and always failing. Was tried also use link button before discovery.
ha-bridge installed on ubuntu together with Domoticz. I can see in ha-bridge yeelights from Domoticz just fine.
Echo gen 1 located on the same subnet as ha-bridge.
Log below
018-11-01 14:36:31,085 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge startup sequence... 2018-11-01 14:36:31,246 [main] INFO  com.bwssystems.HABridge.BridgeSettings - reading from config file: /home/xxxxxxx/habridge/data/habridge.config 2018-11-01 14:36:32,922 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.1) initializing.... 2018-11-01 14:36:33,737 [main] INFO  spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public 2018-11-01 14:36:34,328 [main] INFO  com.bwssystems.HABridge.SystemControl - System control service started.... 2018-11-01 14:36:34,814 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket... 2018-11-01 14:36:34,848 [main] WARN  com.bwssystems.HABridge.util.UDPDatagramSender - UDP Response Port is in use, starting loop to find open port for 20 tries - configured port is: 50000 2018-11-01 14:36:34,867 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Socket initialized to: 50001 2018-11-01 14:36:34,891 [main] INFO  com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created. 2018-11-01 14:36:34,940 [main] INFO  com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured. 2018-11-01 14:36:34,948 [main] INFO  com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured. 2018-11-01 14:36:34,949 [main] INFO  com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured. 2018-11-01 14:36:34,950 [main] INFO  com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured. 2018-11-01 14:36:34,956 [main] INFO  com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured. 2018-11-01 14:36:34,957 [main] INFO  com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured. 2018-11-01 14:36:34,957 [main] INFO  com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured. 2018-11-01 14:36:34,958 [main] INFO  com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created. 2018-11-01 14:36:34,961 [main] INFO  com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created. 2018-11-01 14:36:34,964 [main] INFO  com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created. 2018-11-01 14:36:34,965 [main] INFO  com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured. 2018-11-01 14:36:34,970 [main] INFO  com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured. 2018-11-01 14:36:34,971 [main] INFO  com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. 2018-11-01 14:36:34,973 [main] INFO  com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured. 2018-11-01 14:36:34,974 [main] INFO  com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured. 2018-11-01 14:36:34,975 [main] INFO  com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured. 2018-11-01 14:36:35,067 [main] INFO  com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured. 2018-11-01 14:36:35,069 [main] INFO  com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created. No Broadlinks configured. 2018-11-01 14:36:35,135 [main] WARN  com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data/group.db - Does not exist or is not readable. continuing... 2018-11-01 14:36:35,135 [main] INFO  com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....  2018-11-01 14:36:36,115 [main] INFO  com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started.... 2018-11-01 14:36:36,218 [Thread-0] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ... 2018-11-01 14:36:36,219 [Thread-0] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on <IP_ADDRESS>:80 2018-11-01 14:36:36,639 [Thread-0] ERROR com.bwssystems.HABridge.HABridge - Could not start ha-bridge webservice on port [80] due to: Address already in use 2018-11-01 14:45:48,376 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge startup sequence... 2018-11-01 14:45:48,389 [main] INFO  com.bwssystems.HABridge.BridgeSettings - reading from config file: /home/xxxxxx/habridge/data/habridge.config 2018-11-01 14:45:48,586 [main] INFO  com.bwssystems.HABridge.HABridge - HA Bridge (v5.2.0) initializing.... 2018-11-01 14:45:48,698 [main] INFO  spark.staticfiles.StaticFilesConfiguration - StaticResourceHandler configured with folder = /public 2018-11-01 14:45:48,729 [main] INFO  com.bwssystems.HABridge.SystemControl - System control service started.... 2018-11-01 14:45:48,803 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - Initializing UDP response Socket... 2018-11-01 14:45:48,804 [main] INFO  com.bwssystems.HABridge.util.UDPDatagramSender - UDP response Socket initialized to: 50000 2018-11-01 14:45:48,806 [main] INFO  com.bwssystems.HABridge.plugins.http.HTTPHome - HTTP Home created. 2018-11-01 14:45:48,811 [main] INFO  com.bwssystems.HABridge.plugins.harmony.HarmonyHome - Harmony Home created. No Harmony devices configured. 2018-11-01 14:45:48,811 [main] INFO  com.bwssystems.HABridge.plugins.NestBridge.NestHome - Nest Home created. No Nest configured. 2018-11-01 14:45:48,812 [main] INFO  com.bwssystems.HABridge.plugins.hue.HueHome - Hue passthru Home created. No Hue passtrhu systems configured. 2018-11-01 14:45:48,818 [main] INFO  com.bwssystems.HABridge.plugins.hal.HalHome - HAL Home created. No HAL devices configured. 2018-11-01 14:45:48,829 [main] INFO  com.bwssystems.HABridge.plugins.mqtt.MQTTHome - MQTT Home created. No MQTT Clients configured. 2018-11-01 14:45:48,830 [main] INFO  com.bwssystems.HABridge.plugins.hass.HassHome - HomeAssistant Home created. No HomeAssistants configured. 2018-11-01 14:45:48,830 [main] INFO  com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome - HomeWizard Home created. No HomeWizard gateways configured. 2018-11-01 14:45:48,834 [main] INFO  com.bwssystems.HABridge.plugins.exec.CommandHome - Command Home for system program execution created. 2018-11-01 14:45:48,835 [main] INFO  com.bwssystems.HABridge.plugins.tcp.TCPHome - TCP Home created. 2018-11-01 14:45:48,836 [main] INFO  com.bwssystems.HABridge.plugins.udp.UDPHome - UDP Home created. 2018-11-01 14:45:48,836 [main] INFO  com.bwssystems.HABridge.plugins.vera.VeraHome - Vera Home created. No Veras configured. 2018-11-01 14:45:48,837 [main] INFO  com.bwssystems.HABridge.plugins.fibaro.FibaroHome - Fibaro Home created. No Fibaros configured. 2018-11-01 14:45:48,837 [main] INFO  com.bwssystems.HABridge.plugins.domoticz.DomoticzHome - Domoticz Home created. 2018-11-01 14:45:48,849 [main] INFO  com.bwssystems.HABridge.plugins.somfy.SomfyHome - Somfy Home created. No Somfys configured. 2018-11-01 14:45:48,850 [main] INFO  com.bwssystems.HABridge.plugins.lifx.LifxHome - LifxDevice Home created. No LifxDevices configured. 2018-11-01 14:45:48,851 [main] INFO  com.bwssystems.HABridge.plugins.openhab.OpenHABHome - OpenHAB Home created. No OpenHABs configured. 2018-11-01 14:45:48,857 [main] INFO  com.bwssystems.HABridge.plugins.fhem.FHEMHome - FHEM Home created. No FHEMs configured. 2018-11-01 14:45:48,858 [main] INFO  com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome - Broadlink Home created. No Broadlinks configured. 2018-11-01 14:45:48,881 [Thread-0] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - == Spark has ignited ... 2018-11-01 14:45:48,882 [Thread-0] INFO  spark.embeddedserver.jetty.EmbeddedJettyServer - >> Listening on <IP_ADDRESS>:80 2018-11-01 14:45:48,886 [main] WARN  com.bwssystems.HABridge.dao.GroupRepository - Error reading the file: data/group.db - Does not exist or is not readable. continuing... 2018-11-01 14:45:48,886 [main] INFO  com.bwssystems.HABridge.devicemanagmeent.DeviceResource - HABridge device management service started....  2018-11-01 14:45:48,941 [main] INFO  com.bwssystems.HABridge.hue.HueMulator - Hue emulator service started.... 2018-11-01 14:45:49,009 [main] INFO  com.bwssystems.HABridge.HABridge - Traceupnp: upnp config address: <IP_ADDRESS>-useIface:true on web server: <IP_ADDRESS>:80 2018-11-01 14:45:49,010 [main] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Description xml service started.... 2018-11-01 14:45:49,015 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener starting.... 2018-11-01 14:45:49,015 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Interface: ens160 matches upnp config address of IP address: /<IP_ADDRESS> 2018-11-01 14:45:49,016 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: Adding ens160 to our upnp join interface set. 2018-11-01 14:45:49,017 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - UPNP Discovery Listener running and ready.... 2018-11-01 14:45:52,424 [qtp977301491-12] INFO  com.bwssystems.HABridge.hue.HueMulator - Traceupnp: hue api user create requested for device type: test_ha_bridge#<IP_ADDRESS> and username: 7b4edb35de6447e6a6481f68d065b3b5 2018-11-01 14:46:00,470 [qtp977301491-9] INFO  com.bwssystems.HABridge.SystemControl - Link button pressed.... 2018-11-01 14:46:30,470 [Timer-1] INFO  com.bwssystems.HABridge.LinkButtonPressed - Link button time ended.... 2018-11-01 14:46:36,812 [qtp977301491-11] INFO  com.bwssystems.HABridge.SystemControl - Link button pressed.... 2018-11-01 14:47:06,814 [Timer-2] INFO  com.bwssystems.HABridge.LinkButtonPressed - Link button time ended.... 2018-11-01 14:47:57,564 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:57457 2018-11-01 14:47:58,215 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:57457 2018-11-01 14:47:58,866 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:57457 2018-11-01 14:47:59,517 [main] INFO  com.bwssystems.HABridge.upnp.UpnpListener - Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:57457 2018-11-01 14:48:01,523 [qtp977301491-14] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: <IP_ADDRESS>:80 filled in with address: <IP_ADDRESS>:80 2018-11-01 14:48:01,586 [qtp977301491-15] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: <IP_ADDRESS>:80 filled in with address: <IP_ADDRESS>:80 2018-11-01 14:48:01,618 [qtp977301491-9] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: <IP_ADDRESS>:80 filled in with address: <IP_ADDRESS>:80 2018-11-01 14:48:02,091 [qtp977301491-9] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: <IP_ADDRESS>:80 filled in with address: <IP_ADDRESS>:80 2018-11-01 14:48:02,195 [qtp977301491-13] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: <IP_ADDRESS>:80 filled in with address: <IP_ADDRESS>:80 2018-11-01 14:48:02,223 [qtp977301491-14] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: <IP_ADDRESS>:80 filled in with address: <IP_ADDRESS>:80 2018-11-01 14:48:02,239 [qtp977301491-16] INFO  com.bwssystems.HABridge.upnp.UpnpSettingsResource - Traceupnp: request of description.xml from: <IP_ADDRESS>:80 filled in with address: <IP_ADDRESS>:80
bridge on <IP_ADDRESS>, I see only request coming from QNAP on .254

You have something running on port 80 already as  the error in your log identifies. Please make sure you have read your log and understand the errors before posting.
2018-11-01 14:36:36,639 [Thread-0] ERROR com.bwssystems.HABridge.HABridge - Could not start ha-bridge webservice on port [80] due to: Address already in use

@audiofreak9 do you mean, that there is no way that  habridge and alexa work together?
What is the reason?

Not saying that at all, just letting you know currently others are having issue with Gen 3 and HA-Bridge discovery.  @bwssytems is aware of the reported issue.

Is there any way to keep ha-bridge running on another port than 80 (there is my apache) and let echo dot gen. 3 find the devices? Something like a rewrite-rule inside apache?
Today i switched from echo dot gen. 2 to gen. 3 and now i have the same issue.

Thanks dir your answer :-) As i explained in my post. The ip adress of my Echo dot 3rd gen is <IP_ADDRESS>.

@Bratensosse Sorry about that, read to quickly. Interesting that the ha-bridge is replying but the echo is not asking for the next step which is to get the description.xml. Try changing the "UPNP Send Delay" in bridge control to 250.

@bwssytems Thank you for helping me. Unfortunately that is not the solution. The log file looks like before changing the upnp send delay. Do you have other solution proposal, that can i try?

The only thing I can say is to look into your network setup as others have gotten the gen 3 to work. If you are willing to dig down, doing a network sniff with wireshark or tcpdump would be the next thing and would help me.

That sounds quite complicate. I have to understand how tcpdump works and how i create the data you need first. But i will try it. Do you have the comand for tcpdump?

The only thing I can say is to look into your network setup as others have gotten the gen 3 to work.

Could the way the WiFi is configured be affecting the discovery process that is affecting some users and some devices? Im thinking if the WiFi is configured for both 2.4 & 5Ghz with same or separate SSID, devices may be connecting to different bands, and could (but shouldn't) affect the UPnP discovery process, depending on how the WiFi network is configured?

Hi,
@craigski: thanks for your comment. I disabled the 5Ghz Wifi for testing. But still the same problem
@bwssytems: i installed tcpdump on my bananapi (<IP_ADDRESS> with habridge) and made a run while alexa is looking for new devices and the link button is pressed. I used this call promt:  sudo tcpdump -i eth0 host <IP_ADDRESS>
<IP_ADDRESS> is the echo dot. Here you can see the result:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
21:28:35.698563 IP amazon-xxxxxxxxxx.local.50000 > <IP_ADDRESS>.1900: UDP, length 94
21:28:35.698695 IP amazon-xxxxxxxxxx.local.50000 > <IP_ADDRESS>.1900: UDP, length 101
21:28:35.698720 IP amazon-xxxxxxxxxx.local.50000 > <IP_ADDRESS>.1900: UDP, length 94
21:28:35.698739 IP amazon-xxxxxxxxxx.local.50000 > <IP_ADDRESS>.1900: UDP, length 101
21:28:35.708189 IP amazon-xxxxxxxxxx.local.50000 > <IP_ADDRESS>.1900: UDP, length 94
21:28:35.708668 IP amazon-xxxxxxxxxx.local.50000 > <IP_ADDRESS>.1900: UDP, length 101
21:28:35.880924 ARP, Request who-has amazon-xxxxxxxxxx.local tell fritz.repeater.local, length 46
21:28:35.882710 ARP, Request who-has amazon-xxxxxxxxxx.local tell octopi.local, length 46
21:28:35.951312 ARP, Request who-has amazon-xxxxxxxxxx.local tell bananapi, length 28
21:28:36.013126 ARP, Request who-has amazon-xxxxxxxxxx.local tell Notebook.local, length 46
21:28:36.875149 ARP, Request who-has amazon-xxxxxxxxxx.local tell fritz.repeater.local, length 46
21:28:36.915623 ARP, Request who-has amazon-xxxxxxxxxx.local tell octopi.local, length 46
21:28:36.944498 ARP, Request who-has amazon-xxxxxxxxxx.local tell bananapi, length 28
21:28:37.002115 ARP, Request who-has amazon-xxxxxxxxxx.local tell Notebook.local, length 46
21:28:37.875757 ARP, Request who-has amazon-xxxxxxxxxx.local tell fritz.repeater.local, length 46
21:28:37.944494 ARP, Request who-has amazon-xxxxxxxxxx.local tell bananapi, length 28
21:28:37.955641 ARP, Request who-has amazon-xxxxxxxxxx.local tell octopi.local, length 46
21:28:37.963611 ARP, Request who-has amazon-xxxxxxxxxx.local tell Notebook.local, length 46
21:28:38.964198 ARP, Request who-has amazon-xxxxxxxxxx.local tell Notebook.local, length 46
21:28:38.970833 ARP, Request who-has amazon-xxxxxxxxxx.local tell bananapi, length 28
21:28:39.964498 ARP, Request who-has amazon-xxxxxxxxxx.local tell bananapi, length 28
21:28:40.964489 ARP, Request who-has amazon-xxxxxxxxxx.local tell bananapi, length 28
21:28:51.316898 ARP, Request who-has amazon-xxxxxxxxxx.local tell easy.box.local, length 46
^C
23 packets captured
23 packets received by filter
0 packets dropped by kernel
xxxxxx means, that i have blacked out the name of my echo dot
Do you see any  reason why it still not work?

@Bratensosse are you 100% sure the IP address of echo is .42? What is IP of your laptop/PC?
Im also seeing the SSDP M-SEARCH in log every second or so, but that's coming from a windows 10 PC on my network, maybe you are doing a trace on wrong IP?

@bwssytems can you help me understand the UPnP log. When I initiate a discovery I see the following lines in log:

Traceupnp: hue lights list requested by user: xxxxxxx from address: <IP_ADDRESS>

Traceupnp: hue api user create requested for device type: test_ha_bridge#<IP_ADDRESS> and username: uuuuuuuuuuu

Traceupnp: request of description.xml from: <IP_ADDRESS>:8081 filled in with address: <IP_ADDRESS>:8081

During normal operation I see the following every 1 second or so from my Windows 10 PC:

Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50413

.34 is my Gen2 Echo Dot that I initiated search from
.124 is my Pi/HABridge
.56 is a windows 10 PC
It seems the service 'SSDP Discovery' service on windows is creating these 'SSDP M-SEARCH' requests, I proved this by disabling the service on Windows PC, now my HABridge log is a lot cleaner.
I'm wondering if there are multiple devices on a network, they are all generating these SSDP M-SEARCH requests, maybe the network is flooded with them, and is interfering in the Echo discovery process that takes 20 seconds or so?

@Bratensosse see my post here:
https://github.com/bwssytems/ha-bridge/issues/1022#issuecomment-447318634
Re tcpdump, here is what I used to resolve my issue:
I was using SSH to connect to Pi/HABridge, I excluded this in the following  below
sudo tcpdump -v host <ip address of Pi> and not host <ip address of PC> -w tcpdump80link2new.cap
Run your discovery, then review the tcpdump:
tcpdump -qns 0 -A -r tcpdump80link2new.cap

@craigski Since upnp is a broadcast system in itself, there maybe other applications looking for a service. That is why you will see those requests in the HA-bridge log as we need to interrogate the search request to see if it is for the "Hue" service.
The other messages are the handshake after discovery of the ha-bridge service and are pertinent as it means the requester (the echo) has found the bridge and is requesting the lights info.

Thx for your help. I am quite sure, that i use the correct IP of my echo :-)
@craigski i used your promt while i start the discovery twice. Before i did that, i stopped other services like fhem and samba server on my bananapi to reduce the data:
sudo tcpdump -v host <IP_ADDRESS> and not host <IP_ADDRESS> -w output.dat
sudo tcpdump -qns 0 -A -r output.dat
For explanation:
x.x.x.42: Echo dot
x.x.x.19: My PC (conected to Bananapi via ssh)
x.x.x.2: Bananapi with habridge
x.x.x.1: local router
I really hope, that you can analyse the reason why it still not work... thanks a lot!
Here is the result:-):
E..L.G@.@.1......Q..{.{.8tX#.....................st.....?.......j........Nt
21:15:02.897946 IP xx.xx.xx.xx.xxx > <IP_ADDRESS>.123: UDP, length 48
<EMAIL_ADDRESS>       ./U......Nt......&u......1.
21:15:03.495523 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 46
...........{;x................................
21:15:03.495586 ARP, Reply <IP_ADDRESS> is-at 02:d2:0b:01:76:67, length 28
............vg.......{;x....
21:15:16.125895 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
21:15:16.633848 IP <IP_ADDRESS>.1900 > <IP_ADDRESS>.1900: UDP, length 317
<EMAIL_ADDRESS>* HTTP/1.1
HOST: <IP_ADDRESS>:1900
CACHE-CONTROL: max-age=100
LOCATION: http://<IP_ADDRESS>:80/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.19.0
NTS: ssdp:alive
hue-bridgeid: 02D20BFFFE017667
NT: uuid:2f402f80-da50-11e1-9b23-02d20b017667
USN: uuid:2f402f80-da50-11e1-9b23-02d20b017667
21:15:17.122281 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
21:15:18.122245 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
21:15:19.166015 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
21:15:20.162233 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
21:15:21.162225 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
21:15:33.491787 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 46
...........{;x................................
21:15:33.491852 ARP, Reply <IP_ADDRESS> is-at 02:d2:0b:01:76:67, length 28
............vg.......{;x....
21:15:36.752347 IP <IP_ADDRESS>.1900 > <IP_ADDRESS>.1900: UDP, length 317
<EMAIL_ADDRESS>* HTTP/1.1
HOST: <IP_ADDRESS>:1900
CACHE-CONTROL: max-age=100
LOCATION: http://<IP_ADDRESS>:80/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.19.0
NTS: ssdp:alive
hue-bridgeid: 02D20BFFFE017667
NT: uuid:2f402f80-da50-11e1-9b23-02d20b017667
USN: uuid:2f402f80-da50-11e1-9b23-02d20b017667

@Bratensosse I can't see a correlation with the tcpdumps you have posted and the log file on 4/12/2018. The UPnP log shows some network traffic on port 80 of the bananapi/ha-bridge, the tcpdumps dont.
Start tcpdump again, initiate a discover from the Echo, ie 'Alexa, discover devices' then when discovery has finished, stop tcpdump, should be 20 secs or so.
I dont think the discovery is starting in your tcpdumps above.

@craigski i did dtart dcpdump again while discover alexa two times and the link button was pressed. again i stopped other services on the banana pi.
i will post the log of the habridge and the result of the dcpdump:

12-15-2018 09:23:03.229
INFO
HA Bridge startup sequence...
com.bwssystems.HABridge.HABridge

12-15-2018 09:23:03.312
INFO
reading from config file: /home/pi/habridge/data/habridge.config
com.bwssystems.HABridge.BridgeSettings

12-15-2018 09:23:06.339
INFO
HA Bridge (v5.2.1) initializing....
com.bwssystems.HABridge.HABridge

12-15-2018 09:23:06.439
INFO
StaticResourceHandler configured with folder = /public
spark.staticfiles.StaticFilesConfiguration

12-15-2018 09:23:06.517
INFO
System control service started....
com.bwssystems.HABridge.SystemControl

12-15-2018 09:23:06.840
INFO
Initializing UDP response Socket...
com.bwssystems.HABridge.util.UDPDatagramSender

12-15-2018 09:23:06.862
INFO
UDP response Socket initialized to: 50000
com.bwssystems.HABridge.util.UDPDatagramSender

12-15-2018 09:23:06.884
INFO
HTTP Home created.
com.bwssystems.HABridge.plugins.http.HTTPHome

12-15-2018 09:23:06.917
INFO
Harmony Home created. No Harmony devices configured.
com.bwssystems.HABridge.plugins.harmony.HarmonyHome

12-15-2018 09:23:06.941
INFO
Nest Home created. No Nest configured.
com.bwssystems.HABridge.plugins.NestBridge.NestHome

12-15-2018 09:23:06.947
INFO
Hue passthru Home created. No Hue passtrhu systems configured.
com.bwssystems.HABridge.plugins.hue.HueHome

12-15-2018 09:23:06.955
INFO
HAL Home created. No HAL devices configured.
com.bwssystems.HABridge.plugins.hal.HalHome

12-15-2018 09:23:06.961
INFO
MQTT Home created. No MQTT Clients configured.
com.bwssystems.HABridge.plugins.mqtt.MQTTHome

12-15-2018 09:23:06.968
INFO
HomeAssistant Home created. No HomeAssistants configured.
com.bwssystems.HABridge.plugins.hass.HassHome

12-15-2018 09:23:06.974
INFO
HomeWizard Home created. No HomeWizard gateways configured.
com.bwssystems.HABridge.plugins.homewizard.HomeWizardHome

12-15-2018 09:23:06.991
INFO
Command Home for system program execution created.
com.bwssystems.HABridge.plugins.exec.CommandHome

12-15-2018 09:23:06.999
INFO
TCP Home created.
com.bwssystems.HABridge.plugins.tcp.TCPHome

12-15-2018 09:23:07.011
INFO
UDP Home created.
com.bwssystems.HABridge.plugins.udp.UDPHome

12-15-2018 09:23:07.017
INFO
Vera Home created. No Veras configured.
com.bwssystems.HABridge.plugins.vera.VeraHome

12-15-2018 09:23:07.023
INFO
Fibaro Home created. No Fibaros configured.
com.bwssystems.HABridge.plugins.fibaro.FibaroHome

12-15-2018 09:23:07.031
INFO
Domoticz Home created. No Domoticz devices configured.
com.bwssystems.HABridge.plugins.domoticz.DomoticzHome

12-15-2018 09:23:07.037
INFO
Somfy Home created. No Somfys configured.
com.bwssystems.HABridge.plugins.somfy.SomfyHome

12-15-2018 09:23:07.050
INFO
LifxDevice Home created. No LifxDevices configured.
com.bwssystems.HABridge.plugins.lifx.LifxHome

12-15-2018 09:23:07.059
INFO
OpenHAB Home created. No OpenHABs configured.
com.bwssystems.HABridge.plugins.openhab.OpenHABHome

12-15-2018 09:23:07.067
INFO
FHEM Home created. No FHEMs configured.
com.bwssystems.HABridge.plugins.fhem.FHEMHome

12-15-2018 09:23:07.091
INFO
Broadlink Home created. No Broadlinks configured.
com.bwssystems.HABridge.plugins.broadlink.BroadlinkHome

12-15-2018 09:23:07.202
WARN
Error reading the file: data/group.db - Does not exist or is not readable. continuing...
com.bwssystems.HABridge.dao.GroupRepository

12-15-2018 09:23:07.203
INFO
HABridge device management service started....
com.bwssystems.HABridge.devicemanagmeent.DeviceResource

12-15-2018 09:23:07.241
INFO
== Spark has ignited ...
spark.embeddedserver.jetty.EmbeddedJettyServer

12-15-2018 09:23:07.253
INFO
>> Listening on <IP_ADDRESS>:80
spark.embeddedserver.jetty.EmbeddedJettyServer

12-15-2018 09:23:07.423
INFO
Hue emulator service started....
com.bwssystems.HABridge.hue.HueMulator

12-15-2018 09:23:07.688
INFO
Traceupnp: upnp config address: <IP_ADDRESS>-useIface:false on web server: <IP_ADDRESS>:80
com.bwssystems.HABridge.HABridge

12-15-2018 09:23:07.693
INFO
Description xml service started....
com.bwssystems.HABridge.upnp.UpnpSettingsResource

12-15-2018 09:23:07.731
INFO
UPNP Discovery Listener starting....
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:23:07.733
INFO
Traceupnp: Interface: eth0 valid usable IP address: /<IP_ADDRESS>
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:23:07.736
INFO
Traceupnp: Adding eth0 to our upnp join interface set.
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:23:07.737
INFO
Traceupnp: Interface: lo valid usable IP address: /<IP_ADDRESS>
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:23:07.738
INFO
Traceupnp: Adding lo to our upnp join interface set.
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:23:07.739
INFO
UPNP Discovery Listener running and ready....
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:23:43.502
INFO
Traceupnp: hue api user create requested for  device type: test_ha_bridge#<IP_ADDRESS> and username:  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
com.bwssystems.HABridge.hue.HueMulator

12-15-2018 09:24:21.448
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:21.701
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:21.955
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:22.135
INFO
Link button pressed....
com.bwssystems.HABridge.SystemControl

12-15-2018 09:24:22.209
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:22.214
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:22.467
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:22.721
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:22.974
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:22.976
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:23.229
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:23.482
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:23.735
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:23.737
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:23.990
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:24.243
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:24.496
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:24.498
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:24.750
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:25.004
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:25.257
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:25.258
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:25.511
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:25.764
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:26.017
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:43.097
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:43.350
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:43.603
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:43.857
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:43.861
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:44.113
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:44.366
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:44.396
INFO
Link button pressed....
com.bwssystems.HABridge.SystemControl

12-15-2018 09:24:44.619
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:44.621
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:44.874
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:45.128
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:45.381
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:45.382
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:45.635
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:45.888
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:46.141
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:46.143
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:46.396
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:46.650
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:46.903
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:46.904
INFO
Traceupnp: SSDP M-SEARCH packet from <IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:47.157
INFO
Traceupnp: send upnp discovery template 1 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:47.410
INFO
Traceupnp: send upnp discovery template 2 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:47.663
INFO
Traceupnp: send upnp discovery template 3 with response address: <IP_ADDRESS>:80 to address: /<IP_ADDRESS>:50000
com.bwssystems.HABridge.upnp.UpnpListener

12-15-2018 09:24:52.137
INFO
Link button time ended....
com.bwssystems.HABridge.LinkButtonPressed

12-15-2018 09:25:14.398
INFO
Link button time ended....
com.bwssystems.HABridge.LinkButtonPressed

reading from file output.dat, link-type EN10MB (Ethernet)
09:24:21.703491 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:22.213277 IP <IP_ADDRESS>.1900 > <IP_ADDRESS>.1900: UDP, length 317
<EMAIL_ADDRESS>* HTTP/1.1
HOST: <IP_ADDRESS>:1900
CACHE-CONTROL: max-age=100
LOCATION: http://<IP_ADDRESS>:80/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.19.0
NTS: ssdp:alive
hue-bridgeid: 02D20BFFFE017667
NT: uuid:2f402f80-da50-11e1-9b23-02d20b017667
USN: uuid:2f402f80-da50-11e1-9b23-02d20b017667
09:24:22.699907 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:23.699901 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:24.752212 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:25.749922 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:26.749925 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:41.504187 IP <IP_ADDRESS>.123 > <IP_ADDRESS>.123: UDP, length 48
E..L.h<EMAIL_ADDRESS>09:24:41.527821 IP <IP_ADDRESS>.123 > <IP_ADDRESS>.123: UDP, length 48
E..L.6@.;............{.{.8iM$......:.......j..6..HS...8.......8....b..8...s.
09:24:42.835332 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 46
...........{;x................................
09:24:42.835389 ARP, Reply <IP_ADDRESS> is-at 02:d2:0b:01:76:67, length 28
............vg.......{;x....
09:24:43.351636 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:43.860393 IP <IP_ADDRESS>.1900 > <IP_ADDRESS>.1900: UDP, length 317
<EMAIL_ADDRESS>* HTTP/1.1
HOST: <IP_ADDRESS>:1900
CACHE-CONTROL: max-age=100
LOCATION: http://<IP_ADDRESS>:80/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.19.0
NTS: ssdp:alive
hue-bridgeid: 02D20BFFFE017667
NT: uuid:2f402f80-da50-11e1-9b23-02d20b017667
USN: uuid:2f402f80-da50-11e1-9b23-02d20b017667
09:24:44.349913 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:45.349907 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:46.397840 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:47.389907 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:48.389899 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:25:04.076670 IP <IP_ADDRESS>.1900 > <IP_ADDRESS>.1900: UDP, length 317
<EMAIL_ADDRESS>* HTTP/1.1
HOST: <IP_ADDRESS>:1900
CACHE-CONTROL: max-age=100
LOCATION: http://<IP_ADDRESS>:80/description.xml
SERVER: Linux/3.14.0 UPnP/1.0 IpBridge/1.19.0
NTS: ssdp:alive
hue-bridgeid: 02D20BFFFE017667
NT: uuid:2f402f80-da50-11e1-9b23-02d20b017667
USN: uuid:2f402f80-da50-11e1-9b23-02d20b017667
09:25:12.504213 IP <IP_ADDRESS>.123 > <IP_ADDRESS>.123: UDP, length 48
E..L<EMAIL_ADDRESS>   ....N/.m.{.{.8.........G..........8..`V...8.......8... {..8.....
09:25:12.532066 IP <IP_ADDRESS>.123 > <IP_ADDRESS>.123: UDP, length 48
<EMAIL_ADDRESS>       .F...8.......8...._..8.....
09:25:12.898950 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 46
...........{;x................................
09:25:12.899013 ARP, Reply <IP_ADDRESS> is-at 02:d2:0b:01:76:67, length 28
............vg.......{;x....

@Bratensosse I have a hunch. I can see no traffic from your Echo to your Pi. There are many ARP requests that are not being responded to. I think the WiFi that your echo is connected to is in guest mode / device isolation. This means that the echo can see the default gateway, but no other devices on the network. Please check your WiFi configuration that your Echo is connected to.

I use to have an issue with my Phone grabbing the IP of my HA-Bridge even though my Pi was set to use a static IP. This prevented Alexa from seeing my devices sometimes. Reserving the IP of my PI in my router solved this for me. I actually reserved the IP for all my HA devices which has improved reliability.

@craigski thanks for your answer. I checked my wifi settings. My guest mode is disabled. So that can not be the reason. But i do not find something like a "device isolation" or something like that. I checked the wifi configuration as well as the Lan configuration.
it is very annoying :-(
@tuicemen i my IPs for Pi and echo dot already reserved in my router. it is easier to find them :-)

@Bratensosse If you look at your last tcpdump, you will see an ARP request from your router requesting MAC address of Pi, and your Pi responding, this is normal behaviour:
09:24:42.835332 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 46
...........{;x................................
09:24:42.835389 ARP, Reply <IP_ADDRESS> is-at 02:d2:0b:01:76:67, length 28
............vg.......{;x....
Look a little lower and you will see an ARP request from Pi but NO reply to your Echo, this is abnormal:
09:24:44.349913 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:45.349907 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:46.397840 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:47.389907 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
09:24:48.389899 ARP, Request who-has <IP_ADDRESS> tell <IP_ADDRESS>, length 28
............vg.............*
Something on your network is not configured correctly, your LAN is unable to see the Echo on WiFi. Once the habridge/pi is able to communicate with the Echo, there will be more chance that habridge will function :)

Looking at your devices in first tcpdump you have something called fritz.repeater, I assume this is your wireless extender? Is you echo connected to that? Is Guest mode turned on on that fritzrepeater?
I did a google 'fritz repeater guest mode'
page 31 ?
https://gzhls.at/blob/ldb/b/6/f/2/21e18129a05bb198cb28c9bddb1da59b93e2.pdf
21:28:35.880924 ARP, Request who-has amazon-xxxxxxxxxx.local tell fritz.repeater.local, length 46
21:28:36.915623 ARP, Request who-has amazon-xxxxxxxxxx.local tell octopi.local, length 46
21:28:36.944498 ARP, Request who-has amazon-xxxxxxxxxx.local tell bananapi, length 28
21:28:37.002115 ARP, Request who-has amazon-xxxxxxxxxx.local tell Notebook.local, length 46
21:28:51.316898 ARP, Request who-has amazon-xxxxxxxxxx.local tell easy.box.local, length 46

@craigski you are very attentively :-)
yes it is an wireless extender to use Wifi in my cellar where my workshop is. There are Wifi connected 3D-Printer with a cam streaming the video while printing. This video stream can be seen on wifi and Lan connected devices. But maybe you are right.  For testing your guess i can switch off the repeater and i will try it again. So Thanks for that idea.

Ok, i switched off the wifi repeater and any other wifi device which is not in use (TV, iPad..) and tried it again with the same result. Then i tried to open habridge on my test pi (pi zero w). So the conection is not over LAN (habridge)<->router <->wifi (echo dot) rather wif(pi zero w with habridge)i<->router<->wifi(echo dot). Well, the result is the same.
I borrow a amazon smart plug to test the wifi<->wifi conection. If the used protokoll is similar to habridge, maybe i can locate the problem.

FWIW, I ran into a similar situation yesterday, where Alexa on my Echo dot 2 wouldn't detect any new devices and reported my existing devices offline (which wasn't the case as HA-Bridge was running and functioning just fine). On a hunch, after reading this thread I rebooted the router and that did the trick :-P


Liveintent docs update

We updated some wording around LiveIntent User Id module.

confirmed that identifiersToResolve is already supported by the module. merging.


hostPort does not work

I've deployed this 9-machine bundle into a KVM-virtualized environment managed by MAAS. After deployment, I feed the following manifest to Kubernetes:
apiVersion: v1
kind: Pod
metadata:
name: nginx-host
spec:
containers:

image: caseydavenport/nginx
imagePullPolicy: IfNotPresent
name: nginx-host
ports:

containerPort: 80
hostPort: 8081
restartPolicy: Always

My expectation would be that the Kubernetes node where the Pod is deployed creates a port mapping between port 8081 on the host and port 80 on the container, but that is not the case. No port on the host is ever made available. Is this related to using Flannel and CNI?

Aye, hostPort doesn't work when using CNI. See https://github.com/kubernetes/kubernetes/issues/23920 (long read)
Actually, it looks like they fixed this upstream with CNI 0.6.0 (which we already ship), but we need to update our CNI configurations to include the portMap plugin. See this example - note the .conflist extension and the portMap plugin definition.
Here's the config we currently ship for Flannel: https://github.com/juju-solutions/charm-flannel/blob/master/templates/10-flannel.conf

Our workaround has been to use hostNetwork: true instead of hostPort, e.g. here.
I'mma work on the proper fix, though, and hopefully get that out with our next release.

Any idea when these changes will be available in the Charm store?

Alternatively, I guess I just need to build the flannel Charm myself locally and use that in my bundle, right? I've never built a Charm myself. Any quick pointers?

A test build with this fix is currently on the charm store in my namespace, at cs:~cynerva/flannel-5 (or cs:~cynerva/flannel channel edge).
Keep in mind on some clouds, if you intend to use hostPort and access that port from outside the cluster, you'll need to expose the port with juju run --unit kubernetes-worker/0 open-port 12345 for whichever worker unit hosts the pod.
Hopefully in about an hour here, we'll get this pushed to the ~containers namespace's edge channels. With any luck, we might be able to get this out to stable later this week. Worst case, early January.

@Cynerva if you're using hostPort on a public cloud, does flannel check the API server for which ports should be opened and do the open-port or will users just need to do that still themselves?

if you're using hostPort on a public cloud, does flannel check the API server for which ports should be opened and do the open-port or will users just need to do that still themselves?

Users will need to do the open-port themselves. Having the flannel or kubernetes-worker charm do this intelligently is an interesting idea, but likely not as trivial as it sounds. I won't be pursuing it as part of this issue at least.

The fixes for this are now available on edge channels for cs:~containers/flannel, cs:~containers/canal, and cs:~containers/calico

Fixes in cs:~containers/flannel-39 works for me. Thanks!


Upgrade dependencies to fix warnings

need to review dependencies vulnerability for CAWS.
Building a project is not enough locally. Difference in dates of dependencies can ruin functionality and security. (/*)
have a ready scheme for build release before major update!
check all corners for upcoming months as develop can progress
consider way and create roadmap to Kotlin 2.0 .

Duplicate #80, though, dependencies check fx. setup Dependabot would be nice.
Kotlin 2.0 should be considered only after carp.core adopts it.


Mcp9600 acs71020

Added drivers and sample code for Microchip mcp9600 I2C thermocouple amplifier and Allegr acs71020 AC volt/amp/power chip.
Both drivers work for basic functionality , discovery and error reporting. Extended functionality has not been implemented yet for triggers (temp on thermocouple, zero crossing or over error on acs71020)
Doc folders on both drivers with data sheets.
Sample code compiled and tested for both chips.
added sensor values to sensor.h
/** Thermocouple Temp*/
SENSOR_CHAN_THERMOCOUPLE_TEMP,
/** Thermocouple Temp*/
SENSOR_CHAN_DIFF_TEMP,
/** Thermocouple Temp*/
SENSOR_CHAN_COLD_TEMP,
/** Power in Watts **/
SENSOR_CHAN_POWER,

Not sure why my GitHub create/updates the .DS_Store or if that is normal.

Working on cleaning up code and will resubmit as two separate pull requests for each driver added


When downloading the data, there is a warning

I have regisered ImageNet using my school email and got the permission. But when I run:
python tools/download_image.py --user myaccount --key accountpassword --save_dir ../images/ --hop 2  &
I got a list of  warnings:
does not have class ***. Do you forgot to download the picture??

I have fixed it

I have the same question. How to fix it?