Missing dialyzer types file after update to 1.16.0 release

Our CI started failing after the new 1.16.0 release with this error when running dialyzer:
Starting Dialyzer
[
  check_plt: false,
  init_plt: '/home/runner/work/app/priv/plts/dialyzer.plt',
  files: [...],
  warnings: [:unknown]
]
:dialyzer.run error: File not found: /home/runner/work/_temp/.setup-beam/otp/lib/dialyzer-5.0.3/ebin/erl_bif_types.beam

Halting VM with exit status 1

Here are some details from the action:
Set up Job
Current runner version: '2.305.0'
Operating System
  Ubuntu
  22.04.2
  LTS
Runner Image
  Image: ubuntu-22.04
  Version: 20230611.1
  Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20230611.1/images/linux/Ubuntu2204-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20230611.1
Runner Image Provisioner
  <IP_ADDRESS>
GITHUB_TOKEN Permissions
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v3' (SHA:c85c95e3d7251135ab7dc9ce3241c5835cc595a9)
Download action repository 'erlef/setup-beam@v1' (SHA:61e01a43a562a89bfc54c7f9a378ff67b03e4a21)
Download action repository 'actions/cache@v3' (SHA:88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8)
Complete job name: dialyzer

Run erlef/setup-beam@v1
  with:
    otp-version: 25.1.2
    elixir-version: 1.14.2
    github-token: ***
    install-hex: true
    install-rebar: true
    version-type: loose
    disable_problem_matchers: false
    hexpm-mirrors: https://builds.hex.pm/

  env:
    MIX_ENV: test
Installing Erlang/OTP OTP-<IP_ADDRESS> - built on ubuntu-22.04
  /usr/bin/tar zx --strip-components=1 --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/535393dd-1764-4615-b1c6-5214c62fe946 -f /home/runner/work/_temp/6029d3a7-20aa-43d1-b180-ae82fdf10993
  /opt/hostedtoolcache/otp/ubuntu-22.04/OTP-<IP_ADDRESS>/x64/Install -minimal /opt/hostedtoolcache/otp/ubuntu-22.04/OTP-<IP_ADDRESS>/x64
  Installed Erlang/OTP version
  /opt/hostedtoolcache/otp/ubuntu-22.04/OTP-<IP_ADDRESS>/x64/bin/erl -version
  Erlang (SMP,ASYNC_THREADS) (BEAM) emulator version <IP_ADDRESS>
Using Elixir v1.14.2 (built for Erlang/OTP 25)
Installing Elixir v1.14.2-otp-25
  /usr/bin/unzip -o -q /home/runner/work/_temp/16ea814d-2362-4ba4-8252-02591c1e1326
  Installed Elixir version
  /opt/hostedtoolcache/elixir/1.14.2-otp-25/x64/bin/elixir -v
  Erlang/OTP 25 [erts-<IP_ADDRESS>] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [jit:ns]

  Elixir 1.14.2 (compiled with Erlang/OTP 25)
Running mix local.rebar,--force
  /opt/hostedtoolcache/elixir/1.14.2-otp-25/x64/bin/mix local.rebar --force
  * creating /home/runner/.mix/elixir/1-14/rebar3
Running mix local.hex,--force
  /opt/hostedtoolcache/elixir/1.14.2-otp-25/x64/bin/mix local.hex --force
  * creating /home/runner/.mix/archives/hex-2.0.6

Yeah I'm seeing this as well. I'm currently working around it by using v1.15.4:
    - name: Setup elixir
      uses<EMAIL_ADDRESS>

Not sure where this issue is coming from. Can you create an example repo. that replicates the issue? Our CI is passing, so it's either incomplete or it's some other edge case we'll need to handle.

In the meantime, if you want, you can add to our test cases a replica or your inputs, to see if the error surfaces, here.

Also, maybe related to https://github.com/jeremyjh/dialyxir/issues/506.

@doughsay please try to remove the cache from your github actions that your repo is using. It helped in our case.
In the repo go to Actions -> Management -> Caches and remove the caches that your PR/branch is using and run the job again.

Confirmed that deleting the cache resolved the issue on 1.16 without needing to pin to 1.15.

It seems this is not an action issue (since we don't control local caches) - and you can use the action's lower level version as part of the cache restore key - so I'll close this for now. Feel free to re-open, or comment, to continue the discussion. On another note, I'll probably look into how to automate (or provide tools for...) in the context of the action itself.

@starbelly, @ericmj, do you think e.g. the action should output its own version so it could be used as part of the cache restore key? I know we've been around this subject in the past, but don't know if you have better ideas on how to "attack" this problem. Thanks.

Yeah I have the same issue
      - name: Setup Elixir and Erlang versions
        uses: erlef/setup-beam@v1
        with:
          elixir-version: ${{ env.ELIXIR_VERSION }}
          otp-version: ${{ env.OTP_VERSION }}

@apoorv-2204, did you try clearing the cache? This new action version introduced new elements in the filesystem that might cause issues with the currently cached elements.

Solution

This issue is Solved by cleaning the cache.
Thank you team


feat(proxy) add kong response latency header

Summary
Adds X-Kong-Response-Latency to responses that where caused by errors, or short-circuiting plugins. This header is never added if ngx.ctx.KONG_PROXIED=true, which we set at the end of the access phase (and thus prior balancer phase — tells about intent to proxy, but further errors may occur in balancer too).
Issues resolved
Fix #2767

the scope of this particular PR, hence I'm adding the comment outside of the review, as discussion.

The commit:
https://github.com/Kong/kong/pull/4998/commits/beceafacad0d8e2ea53d0a1b6eaa4bbc51842ea1 adds quite extensive tests for the happy case. It means it does not add tests for unhappy case (e.g. short-circuiting, or errors happening on any phase or with Nginx), and so no tests added for KONG_RESPONSE_LATENCY, but on the bright side, a whole lot of other have now quite extensive tests.
So trying to limit the scope-creep here, can we leave that testing for later?


Possible to add custom data attribute & ID in hits template root element?

Hello,
I'd like to put search results into a Salvattore Masonry Grid , but am having trouble getting the "data-columns" attribute & element ID added to the "ais-hits" root container.
Currently I'm getting:

ITEM CONTENT

What I need to acheive is:

ITEM CONTENT

Is this possible?
Thanks kindly!

@proudlygeek I think you did it also? Can you share us the way you did?

Hi @jthcc we currently only supports giving a template per hits.
We are thinking about giving the users the possibility to provide their own full hits template (so you will have to iterate yourself the hits in the template).
We are not sure right now this would be the best solution.
In the meantime what you can do is create a custom widget:
var myHitsWidget = {
  _container: $('#myHits'),
  getConfiguration: function() {
    return {
      hitsPerPage: 50
    }
  },
  init: function() {
    // if you need some jQuery code here, do it
  },
  render: function(args) {
    var out = '';
    args.results.hits.forEach(function(hit) {
      out += '...'; // do whatever you want here, any html structure
    });
    this._container.html(html);
  }
};

search.addWidget(myHitsWidget);

moved to #771


⚠ Bofrost.be has degraded performance

In d985f1c, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1419 ms

Resolved: Bofrost.be performance has improved in 947027f after 6 minutes.


TCM organ syndrome selection

new multi combobox to define syndroms (use same infra as TCM properties)
add new field "(haupt)anliegen" (wish of the client what to treat)

// in general add more domain logic to software

replaced by #117


New user mailing list

New user mailing list
Subscribe by sending an empty mail to:
<EMAIL_ADDRESS>with the subject:
subscribe esmvaltool
or
subscribe esmvaltool FIRSTNAME LASTNAME
Caveats

confirmation mail after subscription is in German
confirmation mail is send with a delay of some hours

Alternatively
The admin of the list can people manually (single or bulk).
Archive
A public archive is available at https://www.listserv.dfn.de/sympa/arc/esmvaltool
Background
The old mailing list was broken and the archive was not public. So we removed it from the docs #1556 .

I will add this to the docu if you think this is useful.

confirmation mail after subscription is in German

:beer:

I will add this to the docu if you think this is useful.

 For redundancy.

we can add the esmvaltool-ukesm mailing list too<EMAIL_ADDRESS>but that will change to<EMAIL_ADDRESS>soon so by the time you guys sort out ze german one we'll be ready changed too :beer:


Whitespace are wrongly decoded when transforming pdf to html

Bug Report 🐛
Transform of this specific pdf file https://www.decathlon.fr/static/2019/LP/services/global-services/V21/assets/cgv.pdf leads to text with missing whitespaces.
Expected Behavior
Launching markus transform --input cgv.pdf --from pdf --to markdown | head -n 5 should give
1

CONDITIONS GÉNÉRALES DE VENTE www.decathlon.fr

Current Behavior
It gives the following content with missing whitespace
1

CONDITIONSGÉNÉRALESDEVENTEwww.decathlon.fr

Possible Solution

Steps to Reproduce
wget https://www.decathlon.fr/static/2019/LP/services/global-services/V21/assets/cgv.pdf
markus transform --input cgv.pdf --from pdf --to markdown

Context (Environment)
I'm working on the Open Terms Archive and we use this Accord Project to transform digital services documents into markdown in order to track changes overtime.
Desktop

OS: macOS
NodeJs
Version: v16.13.1 or v14.19.1

Detailed Description
After some investigation, the problem seems to be when transforming from pdf to html.
markus transform --input cgv.pdf --from pdf --to html | head -n 6

already gives

1

CONDITIONSGÉNÉRALESDEVENTEwww.decathlon.fr

Using an online pdf to html converter seems to be working fine. I tried this one https://pdf.online/convert-pdf-to-html and got proper white spaces
Thanks

This appears to be a limitation in the version of pdf.js we are using to convert from PDF to structured text. This PDF file is essentially a set of binary streams, where each stream contains a set of x,z positions for individual characters. I am investigating if we there are some pdf.js configuration options that can provide better results...

Thanks for the report. You should be able to test this using the unstable version of markdown-cli until the next release is created.

Works very well, thank you so much for the fast resolution


Use unsafe_get in nnvm

The equality test of type_info() compares the memory addresses of type structures in most compiler implementations. When these structures of the same type cross shared boundaries, they will have different memory addresses, causing the issue of #2233. This patch along with https://github.com/dmlc/dmlc-core/pull/489 should fix the issue.

Thanks, @changlan !


Created a new friendly message

Created a new friendly message that is shown when the extension identifies that the defined port is being used by another process. This PR is about issue #38.

Thank you so much for your help, @gustavosimon! 😃


Address #115 where progress bars did not display correctly

Based on the suggestion from @dbaldon ( https://github.com/blargity/toolkit-for-ynab/issues/115#issuecomment-177597447 ), this update is meant to keep the progress bars and the goal indicator present between multiple months.

@egens, since you originally built these, do these changes raise any flags for you?

@blargity I'm ok, that is great bug fix.
As I think, classes Set logic should be reworked to not using .split for elements classes. There is a mistake of mine because
changedNodes.has('navlink-budget') && changedNodes.has('active')
is not equal to
node.hasClass('navlink-budget') && node.hasClass('active')
that was before.
What do you think?

Before you commit this change you should know that there are other
conditions under which the function needs to be driven. For instance if you
add a goal or remove a goal. That said, the function should be driven when
on the account (register) screen. To prevent that I added a check for
'ynab-grid'. However, there are a few instances where 'ynab-grid' wasn't
present but several other 'ynab-grid-?' were there. To me this is getting
pretty clunky. I think it would better if we could find something that we
knew would only be present on the Budget screen.
Also, these same checks are done in the Goals Indicator code. Sounds like a
common routine to know if we're on the Budget screen would be very useful.
On Mon, Feb 1, 2016 at 4:43 AM, egens<EMAIL_ADDRESS>wrote:

@blargity https://github.com/blargity I'm ok, that is great bug fix.
As I think, classes Set logic should be reworked to not using .split for
elements classes. There is a mistake of mine because
changedNodes.has('navlink-budget') && changedNodes.has('active')
is not equal to
node.hasClass('navlink-budget') && node.hasClass('active')
that was before.
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/blargity/toolkit-for-ynab/pull/149#issuecomment-177907069
.

I just noticed in Nathanael's initial email that goal-indicator/main.js was
listed so that's good.
On Mon, Feb 1, 2016 at 8:44 AM, David Baldon<EMAIL_ADDRESS>wrote:

Before you commit this change you should know that there are other
conditions under which the function needs to be driven. For instance if you
add a goal or remove a goal. That said, the function should be driven when
on the account (register) screen. To prevent that I added a check for
'ynab-grid'. However, there are a few instances where 'ynab-grid' wasn't
present but several other 'ynab-grid-?' were there. To me this is getting
pretty clunky. I think it would better if we could find something that we
knew would only be present on the Budget screen.
Also, these same checks are done in the Goals Indicator code. Sounds like
a common routine to know if we're on the Budget screen would be very
useful.
On Mon, Feb 1, 2016 at 4:43 AM, egens<EMAIL_ADDRESS>wrote:

@blargity https://github.com/blargity I'm ok, that is great bug fix.
As I think, classes Set logic should be reworked to not using .split for
elements classes. There is a mistake of mine because
changedNodes.has('navlink-budget') && changedNodes.has('active')
is not equal to
node.hasClass('navlink-budget') && node.hasClass('active')
that was before.
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/blargity/toolkit-for-ynab/pull/149#issuecomment-177907069
.

@egens, yeah, I couldn't see a way to say, "We're on this nav link and it's active" from the changes digest itself. I did this in Reports. Not sure if it's the best way but it works:
 this.observe = function(changedNodes) {
  if (changedNodes.has('navlink-budget') || changedNodes.has('navlink-accounts')) {
    // Just query the node on the page now and see its status.
    if ($('.navlink-budget').hasClass('active') || $('.navlink-accounts').hasClass('active')) {
      // The user has left the reports page.
      // We're no longer the active page.
      ...
    }
  }
};

To me, having a play with this it improves the feature. I'm more than happy to include pull requests to run this elsewhere or similar, but I'll go ahead and merge in as it'd be better to have it some of the time than none of the time. :-)

@dbaldon, if you want something that's only on the Budget screen, @mhum found changedNodes.has('budget-header-flexbox') if that helps.


Weekly Scheduling Problem

What language and solver does this apply to?
Python, Routing
Describe the problem you are trying to solve.
@Mizux Would be great if you can point me towards a solution that has been framed for the below through or tools
We have a travel time matrix for all the locations
The locations have multiple time windows which fall at the same time frame but on different days of the week. While some locations may have multiple time windows, others only have a single time window where order can be served,
The trucks have capacity constraints. They can only take up-to a certain amount of load in lbs.
The trucks also have travel constraints. Trucks can only travel max 'X' hours in day. And after 'X' hours, a break-time of 'Y' hours needs to be provided and then the truck should restart again the next day and continue to serve orders until all orders on its manifest are served.
The objective is to serve all orders and minimize the number of trucks used along with distance traveled.

Please use the mailing list.

Can you please share the mailing list

That was the link given in the create issue page in the modeling section.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le lun. 31 août 2020 à 15:34, Surya-Vijayakumar<EMAIL_ADDRESS>a écrit :

Can you please share the mailing list
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/2141#issuecomment-683781866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3NV6UULMNC53NJXSSTSDORHXANCNFSM4QNYV6IQ
.


[TASK] Clean up unused doc resources/schemas

Description
Currently there are many resources and schemas defined in the docs that are unused. These will lead to confusion and clutter. Models with circular dependencies also cause errors on the latest version of the Swagger libraries we are using. These models should be removed or updated to avoid this whenever possible.
Acceptance Criteria

[ ] All unused resources/schemas defined in the docs have been removed
[ ] All dependencies have been upgraded to the latest versions

This will be handled by #624


Add PKCS8 and multi CA support

Hi,
This PR adds support for PKCS#8 private keys in key.pem file. Also I replaced generateCertificate call with generateCertificates to read all certificates from ca.pem file in order to support multiple certificate authority. In order to make testing simpler I introduced ssl factory interface and moved ssl test that can be run without docker to DockerCertificatesTest.
This PR is important when one uses external tools to manage and rotate certificates (e.g. ipa).

Codecov Report

Merging #678 into master will increase coverage by 0.51%.
The diff coverage is 92.3%.

@@             Coverage Diff              @@
##             master     #678      +/-   ##
============================================
+ Coverage     63.96%   64.48%   +0.51%
+ Complexity      591      588       -3
============================================
  Files           134      134
  Lines          2589     2610      +21
  Branches        318      322       +4
============================================
+ Hits           1656     1683      +27
+ Misses          786      780       -6
  Partials        147      147

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 ab1e007...fe328d8. Read the comment docs.

cc @rohansingh @mattnworb Since I'm not very familiar with these certs.

Fixed comment from @davidxia

checkstyle :(

Well, I fixed checkstyle, but one build failed. Is that something with stability?


[question]Problems encountered in pl.js

Describe the issue
@evoL I encountered a confusing problem when solving an error. Although grudnia  and  grudzień both represent December, is it reasonable to have inconsistent input and output :)?
To Reproduce
Steps to reproduce the behavior:
moment.locale('pl')
console.log('grudnia-MMMM', moment('grudnia', 'MMMM', true).format('MMMM')) // grudzień

Source Code
https://github.com/moment/moment/blob/develop/src/locale/pl.js#L51
// pl.js
months: function (momentToFormat, format) {
        if (!momentToFormat) {
            return monthsNominative;
        } else if (format === '') {
            // Hack: if format empty we know this is used to generate
            // RegExp by moment. Give then back both valid forms of months
            // in RegExp ready format.
            return (
                '(' +
                monthsSubjective[momentToFormat.month()] +
                '|' +
                monthsNominative[momentToFormat.month()] +
                ')'
            );
        } else if (/D MMMM/.test(format)) {
            return monthsSubjective[momentToFormat.month()];
        } else {
            return monthsNominative[momentToFormat.month()];
        }
    },

<EMAIL_ADDRESS>thanks in advance

Hello,
It's unclear to me what the issue is here. Could you please elaborate on what you want to achieve?
It's true that the form grudnia isn't correct on its own. It's used only in conjunction with numerals, think "5. grudnia". That said, I think it's alright that we're on the loose side when it comes to parsing. Moment can be used to parse user-provided strings and we don't have control over what people are writing :)
Now, when it comes to formatting dates, we can actually strive to make the output grammatically correct. This is exactly what happens here: Moment parses a grammatically incorrect month name (since it lacks a numeral), but recognizes the correct month anyway. When Moment formats the month name, it outputs it in the correct case.
Again, I think this is a good trade-off to make — be forgiving when parsing, strive for correctness when formatting. However, let me know your thoughts on this; I'm all ears :)

Hi, Thank you very much for your quick reply. I hope the input and output are equal in the same tokens. I may need to change my plan 😿, as you said, we don't have control over what people are writing :).
moment('grudnia', 'MMMM', true).format('MMMM') === 'grudnia' // true


add ignore scripts to npmrc

Initial checklist

[x] I read the support docs
[x] I read the contributing guide
[x] I agree to follow the code of conduct
[x] I searched issues and couldn’t find anything (or linked relevant results below)
[x] If applicable, I’ve added docs and tests

Description of changes
add ignore install scripts to npmrc

broken

fixed, typescript update removed the need for some previous ignores/expected errors


Expand parent links for ordered_related_items

Introduce rules to allow for named link types to have other types to be
recursed on.
Before you could only expand on the same type as the first level, this
lets you expand different types by supplying an array of levels.
eg: ['parent', 'parent_taxons', 'parent'] would expand the parent at
level one, parent_taxons at level two, and parents for all levels
greater then n, (the size of the array), the last element being the
"sticky" recursive element. so for array of size 1, it would recurse on just
that element.
This also introduces the ability to expanded recursively for multiple
parent_taxons.
ruby bench/downstream_payload.rb
Many reverse dependencies: 4bda0be5-3e65-4cc1-850c-0541e95a40ca
..........  4.160000   0.190000   4.350000 (  9.104915)
queries: 198
Many forward dependencies: 5f4f1e91-7631-11e4-a3cb-005056011aef
..........  2.240000   0.070000   2.310000 (  3.923168)
queries: 180
No dependencies: 23e13323-874f-4210-aad3-ca6ade9206f8
..........  0.120000   0.010000   0.130000 (  0.189995)
queries: 120
Single link each way: 00012147-49f6-4e90-be1f-e50bb719f53d
..........  0.180000   0.010000   0.190000 (  0.337268)
queries: 180

@kevindew I did a quick refactoring of this. Still could go further, but might be more beneficial for someone else to do that.


[Bug] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Today, most likely after another z2m update, I can't say for sure, the plugin restarts cyclically and multiplied an unsupported accessory named coordinator. i added it's ieee address to exceptions, but it didn't help. i had to delete it from the accessory cache and had a hard time starting the plugin. of course I didn't change the mqtt version.
Related devices
No response
Related Devices
No response
Steps To Reproduce
No response
Expected behavior
No response
Device entry
No response
Status update
No response
Messages from this plugin
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: Living Room Main Light 6 (0xa4c1388a09cdf1f4)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: 0x00158d00079c32a2 (0x00158d00079c32a2)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: 0xa4c138e891447cb0 (0xa4c138e891447cb0)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: Living Room Main Lights (1001)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: Living Room Wall Lights (1002)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: Living Room Bookshelf Lights (1003)
[12/27/2023, 4:49:47 AM] Registering accessory 'homebridge-airrohr.airrohr'
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Connected to MQTT server
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Zigbee2MQTT is ONLINE
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Using Zigbee2MQTT v1.34.0-dev (identified via zigbee2mqtt/bridge/info)
[12/27/2023, 4:49:48 AM] [homebridge-z2m] New accessory: Coordinator
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')
[12/27/2023, 4:49:48 AM] [homebridge-z2m] New accessory: Coordinator
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')
[12/27/2023, 4:58:25 AM] [homebridge-z2m] New accessory: Coordinator

[12/27/2023, 4:58:25 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)

[12/27/2023, 4:58:25 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')

[12/27/2023, 4:58:25 AM] [homebridge-z2m] New accessory: Coordinator

[12/27/2023, 4:58:25 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)

[12/27/2023, 4:58:25 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')

[12/27/2023, 4:58:26 AM] [homebridge-z2m] New accessory: Coordinator

[12/27/2023, 4:58:26 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)

[12/27/2023, 4:58:26 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')

This plugin
latest beta but on release same result
Homebridge
1.7.0
Zigbee2MQTT
1.34.0-dev commit: 265d280e
Homebridge Config UI X (if applicable)
latest

[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Living Room Main Light 6 (0xa4c1388a09cdf1f4)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: 0x00158d00079c32a2 (0x00158d00079c32a2)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: 0xa4c138e891447cb0 (0xa4c138e891447cb0)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Living Room Main Lights (1001)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Living Room Wall Lights (1002)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Living Room Bookshelf Lights (1003)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Coordinator (0x00124b002a1aa3c4)
TypeError: Cannot read properties of null (reading 'vendor')
at isDeviceDefinition (/usr/local/lib/node_modules/homebridge-z2m/src/z2mModels.ts:302:72)
at Zigbee2mqttAccessory.updateDeviceInformation (/usr/local/lib/node_modules/homebridge-z2m/src/platformAccessory.ts:418:30)
at new Zigbee2mqttAccessory (/usr/local/lib/node_modules/homebridge-z2m/src/platformAccessory.ts:98:10)
at Zigbee2mqttPlatform.addAccessory (/usr/local/lib/node_modules/homebridge-z2m/src/platform.ts:575:19)
at Zigbee2mqttPlatform.configureAccessory (/usr/local/lib/node_modules/homebridge-z2m/src/platform.ts:474:10)
at /usr/local/lib/node_modules/homebridge/src/bridgeService.ts:328:25
at Array.filter ()
at BridgeService.restoreCachedPlatformAccessories (/usr/local/lib/node_modules/homebridge/src/bridgeService.ts:288:69)
at ChildBridgeFork.startBridge (/usr/local/lib/node_modules/homebridge/src/childBridgeFork.ts:186:24)

I'm not running dev myself, just the 1.34.0 release of Zigbee2MQTT and I'm not experiencing this.
Can you check that using the actual released version solves this?
Also, van you share the contents of the MQTT message published to zigbee2mqtt/bridge/devices ?

I'm not running dev myself, just the 1.34.0 release of Zigbee2MQTT and I'm not experiencing this. Can you check that using the actual released version solves this?
Also, can you share the contents of the MQTT message published to zigbee2mqtt/bridge/devices ?

I don't know how to copy whole topic, it's huge, because I have localise the pictures. ;-(
[{"definition":null,"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce","genTime"],"output":["ssIasZone","ssIasWd"]},"configured_reportings":[],"scenes":[]},"110":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"12":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"13":{"bindings":[],"clusters":{"input":["genOta"],"output":[]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"3":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"4":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"47":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"5":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"6":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"8":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Coordinator","ieee_address":"0x00124b002a1aa3c4","interview_completed":true,"interviewing":false,"network_address":0,"supported":true,"type":"Coordinator"},{"definition":{"description":"MiJia light intensity sensor","exposes":[{"access":1,"description":"Remaining battery in %, can take up to 24 hours before reported.","label":"Battery","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Voltage of the battery in millivolts","label":"Voltage","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":5,"description":"Raw measured illuminance","label":"Illuminance","name":"illuminance","property":"illuminance","type":"numeric"},{"access":5,"description":"Measured illuminance in lux","label":"Illuminance (lux)","name":"illuminance_lux","property":"illuminance_lux","type":"numeric","unit":"lx"},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":"data:image/jpeg;base64,[encoded data, 7984 characters]","model":"GZCGQ01LM","options":[{"access":2,"description":"Calibrates the illuminance value (percentual offset), takes into effect on next report of device.","label":"Illuminance calibration","name":"illuminance_calibration","property":"illuminance_calibration","type":"numeric"},{"access":2,"description":"Calibrates the illuminance_lux value (percentual offset), takes into effect on next report of device.","label":"Illuminance lux calibration","name":"illuminance_lux_calibration","property":"illuminance_lux_calibration","type":"numeric"}],"supports_ota":false,"vendor":"Xiaomi"},"disabled":false,"endpoints":{"1":{"bindings":[{"cluster":"msIlluminanceMeasurement","target":{"endpoint":1,"ieee_address":"0x00124b002a1aa3c4","type":"endpoint"}}],"clusters":{"input":[],"output":[]},"configured_reportings":[{"attribute":"measuredValue","cluster":"msIlluminanceMeasurement","maximum_report_interval":3600,"minimum_report_interval":15,"reportable_change":500}],"scenes":[]}},"friendly_name":"Living Room Light Sensor","ieee_address":"0x04cf8cdf3c786645","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.sen_ill.mgl01","network_address":35651,"power_source":"Battery","supported":true,"type":"EndDevice"},{"date_code":"12-24-2021","definition":{"description":"Mi power plug ZigBee","exposes":[{"features":[{"access":7,"description":"On/off state of the switch","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":5,"description":"Instantaneous measured power","label":"Power","name":"power","property":"power","type":"numeric","unit":"W"},{"access":1,"description":"Sum of consumed energy","label":"Energy","name":"energy","property":"energy","type":"numeric","unit":"kWh"},{"access":1,"description":"Temperature of the device","label":"Device temperature","name":"device_temperature","property":"device_temperature","type":"numeric","unit":"°C"},{"access":7,"description":"Enable/disable the power outage memory, this recovers the on/off mode after power failure","label":"Power outage memory","name":"power_outage_memory","property":"power_outage_memory","type":"binary","value_off":false,"value_on":true},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":"data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAYABgAAD/4QCMRXhpZgAATU0AKgAAAAgABQESAAMAAAABAAEAAAEaAAUAAAABAAAASgEbAAUAAAABAAAAUgEoAAMAAAABAAIAAIdpAAQAAAABAAAAWgAAAAAAAABgAAAAAQAAAGAAAAABAAOgAQADAAAAAQABAACgAgAEAAAAAQAAAJagAwAEAAAAAQAAAJYAAAAA/+0AOFBob3Rvc2hvcCAzLjAAOEJJTQQEAAAAAAAAOEJJTQQlAAAAAAAQ1B2M2Y8AsgTpgAmY7PhCfv/bAEMABgQFBgUEBgYFBgcHBggKEAoKCQkKFA4PDBAXFBgYFxQWFhodJR8aGyMcFhYgLCAjJicpKikZHy0wLSgwJSgpKP/bAEMBBwcHCggKEwoKEygaFhooKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKP/AABEIAJYAlgMBIgACEQEDEQH/xAAbAAEAAgMBAQAAAAAAAAAAAAAAAwQBAgUGCP/EADYQAAIBAwIDBgQFAgcAAAAAAAABAgMEESExBRJRBhMiQWFxIzKBkRRCUpKhFVMkM2Jj0dLh/8QAFQEBAQAAAAAAAAAAAAAAAAAAAAH/xAAVEQEBAAAAAAAAAAAAAAAAAAAAEf/aAAwDAQACEQMRAD8A+qAAAAAAAjc+gEgIeeRnnkBKCLml1Mc0uoEwIeaXUcz6gTAijUa31JIyUtgMgAAAAAAAAAAAANKj2RGZk8zfoYAAAAAAMMGQBgynh5Bh7gWFqgaUnmBuAAAAAAAAAMTfLFvoZyQ3EvCl1AipvLZIQ03iZNkAaVKtOm1zyUc7ZPP9p+J17a5oWtt4XUjzOTWiRxq9WrVppXNXvIrxJcqWv0LB7mnUhUjzU5KS6ojldUIy5XUipJ4x6lDsxNT4PQx5I4nG69O17R04yiuapKEk/fQg9fUqRpwc5vEVq30IqV1RqtqnUTa3MXUFWs6sGsqcGv4PEWy5KX+HqSo82slDRN7ZA98mns0/YM8Vwfitxb8Wp21eo6lOrlRk1qmvL1PagSUdmiQipPxEoAAAAAAAAGPIqV5ZqPoi2yhUfxJe4G0PnJiunsWAKHFeGUuJU4d43CpD5Jrdf+HCvOzl2rebpV4VZpeGCjhy/k9aNAOH2Ttbyz4aqN9S7urGT0Uk9M6HK7Z8E4jxDivD7nhsKclS/wAzmny7STXv5nsQBHST7mCmsPGqPKW/Z+9d3VVaUKdu5ycZQll4zpoevMaAcKx7N29teQuqtWpWqw1hzJJJ9TujfbUAZhpJE2SBEwGcjIADIAAyYZkAYOfcaVpL1Oic+9WK/ugNEy2tUinHYtU34EBucvj7uY22beXLDabS1S6nUMNKSaksp6NAc7g97+IoxhPSpFYZ0jzV7bz4bdwqUc93J+H/AK/8HoLepKpSjKUZRbWzWAJdDn8auvwtlLlfxJ+GKL55vj9O5q3sc0pd0vDBrVNsCx2blcThLvKjlRh4VnzZ3CCxt1a20KUfJa+rJwBLHWKIupLS+QDYAAAABkAACjxBYnB+heKfEV4IP1Aqw1LVF5popwZZtnlSXRgTgADDSe6zg2MDIAAADDMmAGSSjsyM3o/M/YCYYQAGMAyAAAAFbiCzbt9GiyRXazbVF6AcqL0NqFbkrpN4UtCLOEVqsssDvA5FtxHu/BWy4+UludOnXpVFmE4v6gbmTHMuq+5jmj+pfcCveXtO0rWlKrCvKVzV7qDp0ZTUXyuWZtLEVhPV4WcLdotGveQX54r6mO9p/rj9wNzBp31L+5D7mruKK3qR+4EpvR3bKNS8j8tLxN+fkdChBwpJS+bd+4EgAAAAAAABpVWaU11TNwB5+TwipVe5ZufBUlF+TwUqst8AaZzInhsV6e5YTwBtkxkhr1lTwt5PZFGtfSVWNNayks74WEB1fIwsZOPTvpylTjKGHPOUnrFeWS5Rry72Ed1LKefIC5kyao2gBe4ZS7y4Ta8MNWdsqcNpd3bpv5p6/QtgAAAAAAAAAABx+NW7Xx4LT83ocObeT2bSaaayn5HGvOCqcnO2ko/6JbfQDj0ibJPHhl1F47rPs0bLh13/AGv5QHPuKCrNPOJJYz6dCtKzm/mUGvU7a4bdfoX7kZ/pd0/yx/cBxqVny6ZjFeiLNKnGmtN+r3OiuFXP+3+42XCbjzlT+4FDzLVlRdetGKWm7fRFiHCavN8SpBL01OpbW8LenywXu3uwJUsLC2MgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAf/Z","model":"ZNCZ02LM","options":[{"access":2,"description":"Calibrates the power value (percentual offset), takes into effect on next report of device.","label":"Power calibration","name":"power_calibration","property":"power_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for power, takes into effect on next report of device.","label":"Power precision","name":"power_precision","property":"power_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the energy value (percentual offset), takes into effect on next report of device.","label":"Energy calibration","name":"energy_calibration","property":"energy_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for energy, takes into effect on next report of device.","label":"Energy precision","name":"energy_precision","property":"energy_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device.","label":"Device temperature calibration","name":"device_temperature_calibration","property":"device_temperature_calibration","type":"numeric"},{"access":2,"description":"State actions will also be published as 'action' when true (default false).","label":"State action","name":"state_action","property":"state_action","type":"binary","value_off":false,"value_on":true}],"supports_ota":true,"vendor":"Xiaomi"},"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","genGroups","genIdentify","genOnOff","genBinaryOutput","genScenes","genTime","genPowerCfg","genDeviceTempCfg"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[],"clusters":{"input":["genAnalogInput"],"output":["genAnalogInput","genGroups"]},"configured_reportings":[],"scenes":[]},"3":{"bindings":[],"clusters":{"input":["genAnalogInput"],"output":["genAnalogInput"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Test Plug","ieee_address":"0x00158d0003c73ba7","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.plug","network_address":5917,"power_source":"Mains (single phase)","supported":true,"type":"Router"},{"date_code":"","definition":{"description":"Multiprise with 4 AC outlets and 2 USB super charging ports (16A)","exposes":[{"access":7,"description":"Controls the behavior when the device is powered on after power loss","label":"Power-on behavior","name":"power_on_behavior","property":"power_on_behavior","type":"enum","values":["off","previous","on"]},{"endpoint":"l1","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l1","label":"State","name":"state","property":"state_l1","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"endpoint":"l2","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l2","label":"State","name":"state","property":"state_l2","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"endpoint":"l3","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l3","label":"State","name":"state","property":"state_l3","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"endpoint":"l4","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l4","label":"State","name":"state","property":"state_l4","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"endpoint":"l5","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l5","label":"State","name":"state","property":"state_l5","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":"data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAASABIAAD/4Q4FRXhpZgAATU0AKgAAAAgACAEGAAMAAAABAAIAAAESAAMAAAABAAEAAAEaAAUAAAABAAAAbgEbAAUAAAABAAAAdgEoAAMAAAABAAIAAAExAAIAAAAkAAAAfgEyAAIAAAAUAAAAoodpAAQAAAABAAAAtgAAAAAAAABIAAAAAQAAAEgAAAABQWRvYmUgUGhvdG9zaG9wIENDIDIwMTQgKE1hY2ludG9zaCkAMjAyMDowOTozMCAyMDoxODo0NQAABZAAAAcAAAAEMDIyMZAEAAIAAAAUAAAA+KABAAMAAAABAAEAAKACAAQAAAABAAAAlqADAAQAAAABAAAAlgAAAAAyMDIwOjA5OjMwIDE2OjI3OjMyAGh0dHA6Ly9ucy5hZG9iZS5jb20veGFwLzEuMC8APD94cGFja2V0IGJlZ2luPSLvu78iIGlkPSJXNU0wTXBDZWhpSHpyZVN6TlRjemtjOWQiPz4gPHg6eG1wbWV0YSB4bWxuczp4PSJhZG9iZTpuczptZXRhLyIgeDp4bXB0az0

[{"definition":null,"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"10":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"11":{"bindings":[],"clusters":{"input":["ssIasAce","genTime"],"output":["ssIasZone","ssIasWd"]},"configured_reportings":[],"scenes":[]},"110":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"12":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"13":{"bindings":[],"clusters":{"input":["genOta"],"output":[]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"3":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"4":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"47":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"5":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"6":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]},"8":{"bindings":[],"clusters":{"input":[],"output":[]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Coordinator","ieee_address":"0x00124b002a1aa3c4","interview_completed":true,"interviewing":false,"network_address":0,"supported":true,"type":"Coordinator"},{"definition":{"description":"MiJia light intensity sensor","exposes":[{"access":1,"description":"Remaining battery in %, can take up to 24 hours before reported.","label":"Battery","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Voltage of the battery in millivolts","label":"Voltage","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":5,"description":"Raw measured illuminance","label":"Illuminance","name":"illuminance","property":"illuminance","type":"numeric"},{"access":5,"description":"Measured illuminance in lux","label":"Illuminance (lux)","name":"illuminance_lux","property":"illuminance_lux","type":"numeric","unit":"lx"},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":" ","model":"GZCGQ01LM","options":[{"access":2,"description":"Calibrates the illuminance value (percentual offset), takes into effect on next report of device.","label":"Illuminance calibration","name":"illuminance_calibration","property":"illuminance_calibration","type":"numeric"},{"access":2,"description":"Calibrates the illuminance_lux value (percentual offset), takes into effect on next report of device.","label":"Illuminance lux calibration","name":"illuminance_lux_calibration","property":"illuminance_lux_calibration","type":"numeric"}],"supports_ota":false,"vendor":"Xiaomi"},"disabled":false,"endpoints":{"1":{"bindings":[{"cluster":"msIlluminanceMeasurement","target":{"endpoint":1,"ieee_address":"0x00124b002a1aa3c4","type":"endpoint"}}],"clusters":{"input":[],"output":[]},"configured_reportings":[{"attribute":"measuredValue","cluster":"msIlluminanceMeasurement","maximum_report_interval":3600,"minimum_report_interval":15,"reportable_change":500}],"scenes":[]}},"friendly_name":"Living Room Light Sensor","ieee_address":"0x04cf8cdf3c786645","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.sen_ill.mgl01","network_address":35651,"power_source":"Battery","supported":true,"type":"EndDevice"},{"date_code":"12-24-2021","definition":{"description":"Mi power plug ZigBee","exposes":[{"features":[{"access":7,"description":"On/off state of the switch","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":5,"description":"Instantaneous measured power","label":"Power","name":"power","property":"power","type":"numeric","unit":"W"},{"access":1,"description":"Sum of consumed energy","label":"Energy","name":"energy","property":"energy","type":"numeric","unit":"kWh"},{"access":1,"description":"Temperature of the device","label":"Device temperature","name":"device_temperature","property":"device_temperature","type":"numeric","unit":"°C"},{"access":7,"description":"Enable/disable the power outage memory, this recovers the on/off mode after power failure","label":"Power outage memory","name":"power_outage_memory","property":"power_outage_memory","type":"binary","value_off":false,"value_on":true},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":" ","model":"ZNCZ02LM","options":[{"access":2,"description":"Calibrates the power value (percentual offset), takes into effect on next report of device.","label":"Power calibration","name":"power_calibration","property":"power_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for power, takes into effect on next report of device.","label":"Power precision","name":"power_precision","property":"power_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the energy value (percentual offset), takes into effect on next report of device.","label":"Energy calibration","name":"energy_calibration","property":"energy_calibration","type":"numeric"},{"access":2,"description":"Number of digits after decimal point for energy, takes into effect on next report of device.","label":"Energy precision","name":"energy_precision","property":"energy_precision","type":"numeric","value_max":3,"value_min":0},{"access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device.","label":"Device temperature calibration","name":"device_temperature_calibration","property":"device_temperature_calibration","type":"numeric"},{"access":2,"description":"State actions will also be published as 'action' when true (default false).","label":"State action","name":"state_action","property":"state_action","type":"binary","value_off":false,"value_on":true}],"supports_ota":true,"vendor":"Xiaomi"},"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","genGroups","genIdentify","genOnOff","genBinaryOutput","genScenes","genTime","genPowerCfg","genDeviceTempCfg"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]},"2":{"bindings":[],"clusters":{"input":["genAnalogInput"],"output":["genAnalogInput","genGroups"]},"configured_reportings":[],"scenes":[]},"3":{"bindings":[],"clusters":{"input":["genAnalogInput"],"output":["genAnalogInput"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Test Plug","ieee_address":"0x00158d0003c73ba7","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.plug","network_address":5917,"power_source":"Mains (single phase)","supported":true,"type":"Router"},{"date_code":"","definition":{"description":"Multiprise with 4 AC outlets and 2 USB super charging ports (16A)","exposes":[{"access":7,"description":"Controls the behavior when the device is powered on after power loss","label":"Power-on behavior","name":"power_on_behavior","property":"power_on_behavior","type":"enum","values":["off","previous","on"]},{"endpoint":"l1","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l1","label":"State","name":"state","property":"state_l1","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"endpoint":"l2","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l2","label":"State","name":"state","property":"state_l2","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"endpoint":"l3","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l3","label":"State","name":"state","property":"state_l3","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"endpoint":"l4","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l4","label":"State","name":"state","property":"state_l4","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"endpoint":"l5","features":[{"access":7,"description":"On/off state of the switch","endpoint":"l5","label":"State","name":"state","property":"state_l5","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"}],"type":"switch"},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":" ","model":"WP33-EU/WP34-EU","options":[{"access":2,"description":"State actions will also be published as 'action' when true (default false).","label":"State action","name":"state_action","property":"state_action","type":"binary","value_off":false,"value_on":true}],"supports_ota":false,"vendor":"LELLKI"},"disabled":false,"endpoints":{"1":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x00124b002a1aa3c4","type":"endpoint"}}],"clusters":{"input":["genIdentify","genGroups","genScenes","genOnOff","manuSpecificBosch","manuSpecificTuya_3","genBasic"],"output":["genOta","genTime"]},"configured_reportings":[{"attribute":"onOff","cluster":"genOnOff","maximum_report_interval":65000,"minimum_report_interval":0,"reportable_change":1}],"scenes":[]},"2":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x00124b002a1aa3c4","type":"endpoint"}}],"clusters":{"input":["genGroups","genScenes","genOnOff","manuSpecificTuya_3"],"output":[]},"configured_reportings":[{"attribute":"onOff","cluster":"genOnOff","maximum_report_interval":65000,"minimum_report_interval":0,"reportable_change":1}],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":["greenPower"]},"configured_reportings":[],"scenes":[]},"3":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x00124b002a1aa3c4","type":"endpoint"}}],"clusters":{"input":["genGroups","genScenes","genOnOff","manuSpecificTuya_3"],"output":[]},"configured_reportings":[{"attribute":"onOff","cluster":"genOnOff","maximum_report_interval":65000,"minimum_report_interval":0,"reportable_change":1}],"scenes":[]},"4":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x00124b002a1aa3c4","type":"endpoint"}}],"clusters":{"input":["genGroups","genScenes","genOnOff","manuSpecificTuya_3"],"output":[]},"configured_reportings":[{"attribute":"onOff","cluster":"genOnOff","maximum_report_interval":65000,"minimum_report_interval":0,"reportable_change":1}],"scenes":[]},"5":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x00124b002a1aa3c4","type":"endpoint"}}],"clusters":{"input":["genGroups","genScenes","genOnOff","manuSpecificTuya_3"],"output":[]},"configured_reportings":[{"attribute":"onOff","cluster":"genOnOff","maximum_report_interval":65000,"minimum_report_interval":0,"reportable_change":1}],"scenes":[]}},"friendly_name":"Power Strip","ieee_address":"0xa4c1381a6adee8f4","interview_completed":true,"interviewing":false,"manufacturer":"_TZ3000_air9m6af","model_id":"TS011F","network_address":54302,"power_source":"Mains (single phase)","supported":true,"type":"Router"},{"date_code":"20180525","definition":{"description":"Aqara wireless switch","exposes":[{"access":1,"description":"Remaining battery in %, can take up to 24 hours before reported.","label":"Battery","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Voltage of the battery in millivolts","label":"Voltage","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":1,"description":"Triggered action (e.g. a button click)","label":"Action","name":"action","property":"action","type":"enum","values":["single","double","triple","quadruple","hold","release"]},{"access":1,"description":"Temperature of the device","label":"Device temperature","name":"device_temperature","property":"device_temperature","type":"numeric","unit":"°C"},{"access":1,"description":"Number of power outages (since last pairing)","label":"Power outage count","name":"power_outage_count","property":"power_outage_count","type":"numeric"},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":" ","model":"WXKG11LM","options":[{"access":2,"description":"Calibrates the device_temperature value (absolute offset), takes into effect on next report of device.","label":"Device temperature calibration","name":"device_temperature_calibration","property":"device_temperature_calibration","type":"numeric"},{"access":2,"description":"Set to false to disable the legacy integration (highly recommended), will change structure of the published payload (default true).","label":"Legacy","name":"legacy","property":"legacy","type":"binary","value_off":false,"value_on":true}],"supports_ota":false,"vendor":"Xiaomi"},"disabled":false,"endpoints":{"1":{"bindings":[],"clusters":{"input":["genBasic","genMultistateInput","genIdentify"],"output":["genBasic"]},"configured_reportings":[],"scenes":[]}},"friendly_name":"Square Knob","ieee_address":"0x00158d0006b47627","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.remote.b1acn01","network_address":15672,"power_source":"Battery","software_build_id":"3000-0001","supported":true,"type":"EndDevice"},{"date_code":"20191118","definition":{"description":"MiJia light intensity sensor","exposes":[{"access":1,"description":"Remaining battery in %, can take up to 24 hours before reported.","label":"Battery","name":"battery","property":"battery","type":"numeric","unit":"%","value_max":100,"value_min":0},{"access":1,"description":"Voltage of the battery in millivolts","label":"Voltage","name":"voltage","property":"voltage","type":"numeric","unit":"mV"},{"access":5,"description":"Raw measured illuminance","label":"Illuminance","name":"illuminance","property":"illuminance","type":"numeric"},{"access":5,"description":"Measured illuminance in lux","label":"Illuminance (lux)","name":"illuminance_lux","property":"illuminance_lux","type":"numeric","unit":"lx"},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":" ","model":"GZCGQ01LM","options":[{"access":2,"description":"Calibrates the illuminance value (percentual offset), takes into effect on next report of device.","label":"Illuminance calibration","name":"illuminance_calibration","property":"illuminance_calibration","type":"numeric"},{"access":2,"description":"Calibrates the illuminance_lux value (percentual offset), takes into effect on next report of device.","label":"Illuminance lux calibration","name":"illuminance_lux_calibration","property":"illuminance_lux_calibration","type":"numeric"}],"supports_ota":false,"vendor":"Xiaomi"},"disabled":false,"endpoints":{"1":{"bindings":[{"cluster":"msIlluminanceMeasurement","target":{"endpoint":1,"ieee_address":"0x00124b002a1aa3c4","type":"endpoint"}}],"clusters":{"input":["genBasic","msIlluminanceMeasurement","genIdentify","genPowerCfg"],"output":["genIdentify"]},"configured_reportings":[{"attribute":"measuredValue","cluster":"msIlluminanceMeasurement","maximum_report_interval":3600,"minimum_report_interval":15,"reportable_change":500}],"scenes":[]}},"friendly_name":"Hall Light Sensor","ieee_address":"0x04cf8cdf3c78d4fe","interview_completed":true,"interviewing":false,"manufacturer":"LUMI","model_id":"lumi.sen_ill.mgl01","network_address":2229,"power_source":"Battery","software_build_id":"2019\u0000www.","supported":true,"type":"EndDevice"},{"date_code":"20201111","definition":{"description":"TRADFRI LED bulb GU10 345/380 lumen, dimmable, white spectrum","exposes":[{"features":[{"access":7,"description":"On/off state of this light","label":"State","name":"state","property":"state","type":"binary","value_off":"OFF","value_on":"ON","value_toggle":"TOGGLE"},{"access":7,"description":"Brightness of this light","label":"Brightness","name":"brightness","property":"brightness","type":"numeric","value_max":254,"value_min":0},{"access":7,"description":"Color temperature of this light","label":"Color temp","name":"color_temp","presets":[{"description":"Coolest temperature supported","name":"coolest","value":250},{"description":"Cool temperature (250 mireds / 4000 Kelvin)","name":"cool","value":250},{"description":"Neutral temperature (370 mireds / 2700 Kelvin)","name":"neutral","value":370},{"description":"Warm temperature (454 mireds / 2200 Kelvin)","name":"warm","value":454},{"description":"Warmest temperature supported","name":"warmest","value":454}],"property":"color_temp","type":"numeric","unit":"mired","value_max":454,"value_min":250},{"access":7,"description":"Color temperature after cold power on of this light","label":"Color temp startup","name":"color_temp_startup","presets":[{"description":"Coolest temperature supported","name":"coolest","value":250},{"description":"Cool temperature (250 mireds / 4000 Kelvin)","name":"cool","value":250},{"description":"Neutral temperature (370 mireds / 2700 Kelvin)","name":"neutral","value":370},{"description":"Warm temperature (454 mireds / 2200 Kelvin)","name":"warm","value":454},{"description":"Warmest temperature supported","name":"warmest","value":454},{"description":"Restore previous color_temp on cold power on","name":"previous","value":65535}],"property":"color_temp_startup","type":"numeric","unit":"mired","value_max":454,"value_min":250}],"type":"light"},{"access":2,"description":"Triggers an effect on the light (e.g. make light blink for a few seconds)","label":"Effect","name":"effect","property":"effect","type":"enum","values":["blink","breathe","okay","channel_change","finish_effect","stop_effect"]},{"access":7,"description":"Controls the behavior when the device is powered on after power loss","label":"Power-on behavior","name":"power_on_behavior","property":"power_on_behavior","type":"enum","values":["off","on","toggle","previous"]},{"access":7,"description":"Advanced color behavior","features":[{"access":2,"description":"Controls whether color and color temperature can be set while light is off","label":"Execute if off","name":"execute_if_off","property":"execute_if_off","type":"binary","value_off":false,"value_on":true}],"label":"Color options","name":"color_options","property":"color_options","type":"composite"},{"access":1,"description":"Link quality (signal strength)","label":"Linkquality","name":"linkquality","property":"linkquality","type":"numeric","unit":"lqi","value_max":255,"value_min":0}],"icon":" ","model":"LED2005R5","options":[{"access":2,"description":"Controls the transition time (in seconds) of on/off, brightness, color temperature (if applicable) and color (if applicable) changes. Defaults to 0 (no transition).","label":"Transition","name":"transition","property":"transition","type":"numeric","value_min":0},{"access":2,"description":"When enabled colors will be synced, e.g. if the light supports both color x/y and color temperature a conversion from color x/y to color temperature will be done when setting the x/y color (default true).","label":"Color sync","name":"color_sync","property":"color_sync","type":"binary","value_off":false,"value_on":true},{"access":2,"description":"State actions

I'm running into the same (had been working fine for some time) on both -dev and non-dev latest branch. I am running on docker as well, this just started today.

I'm running into the same (had been working fine for some time) on both -dev and non-dev latest branch. I am running on docker as well, this just started today.

removing the cached accessory helped and the plugin started, though the original error is weird

copypaste.txt

Unfortunately the contents of that file seems to be incomplete. It's supposed to be a JSON, but when I try to format it, it's missing a part at the end.

Seems that I have implemented this check incorrectly.
It also seems that there are now (e.g. starting the latest Zigbee2MQTT release) devices that do not contain a vendor.
If someone can share the entries from zigbee2mqtt/bridge/devices that do not contain a vendor, that would be great. Not sure when I'll have time to patch this though, but I do want to make sure that there's no other keys missing/optional now.

Seems that I have implemented this check incorrectly. It also seems that there are now (e.g. starting the latest Zigbee2MQTT release) devices that do not contain a vendor.
If someone can share the entries from zigbee2mqtt/bridge/devices that do not contain a vendor, that would be great. Not sure when I'll have time to patch this though, but I do want to make sure that there's no other keys missing/optional now.

https://drive.google.com/file/d/1W02wXoL2mWNjZCNlTeapq-Jpllg0hJiu/view?usp=sharing

Closing this issue. Let's continue in #794


rpm package of chronos 3.0.0/3.0.1

Where can I find chronos3.0.0 rpm package ? I wanted to install it through Ansible.

There's no RPM. I do not publish one.
https://github.com/mesos/chronos#packaging


[SPARK-12592][SQL][WIP] Converts resolved logical plan back to SQL

This PR tries to enable Spark SQL to convert resolved logical plans back to SQL query strings.  For now, the major use case is to canonicalize Spark SQL native view support.
The major entry point is SQLBuilder.toSQL, which returns an Option[String] if the logical plan is recognized.
The current version is still in WIP status, and is quite limited.  Known limitations include:

The logical plan must be analyzed but not optimized
The optimizer erases Subquery operators, which contain necessary scope information for SQL generation.  Future versions should be able to recover erased scope information by inserting subqueries when necessary.

The logical plan must be created using HiveQL query string
Query plans generated by composing arbitrary DataFrame API combinations are not supported yet.  Operators within these query plans need to be rearranged into a canonical form that is more suitable for direct SQL generation.  For example, the following query plan
Filter (a#1 < 10)
 +- MetastoreRelation default, src, None

need to be canonicalized into the following form before SQL generation:
Project [a#1, b#2, c#3]
 +- Filter (a#1 < 10)
     +- MetastoreRelation default, src, None

Otherwise, the SQL generation process will have to handle a large number of special cases.

Only a fraction of expressions and basic logical plan operators are supported in this PR
Support for window functions, generators, and cubes etc. will be added in follow-up PRs.

This PR leverages HiveCompatibilitySuite for testing SQL generation in a "round-trip" manner:

For all select queries, we try to convert it back to SQL
If the query plan is convertible, we parse the generated SQL into a new logical plan
Run the new logical plan instead of the original one

If the query plan is inconvertible, the test case simply falls back to the original logic.
TODO

[ ] Fix failed test cases
[ ] Support for more basic expressions and logical plan operators (e.g. distinct aggregation etc.)
[ ] Comments and documentation

The jira ticket is linked incorrectly I think.

The jira ticket is linked incorrectly I think.

@liancheng this looks cool!
I was wondering why we are bound to SQL? Is this because of Hive? I was thinking of the following, we could also store the logical plan's json representation. This should alot easier to (de)serialize. Could we store that in the Hive metadata store?
Another idea I was having. If a view is defined in HQL, we could also store that in some way with the query execution. This saves us a serialization/deserialization trip, and allows the user to recognize his own query.

@hvanhovell the problem with the json representation is stability. The json one is pretty tied to our internal implementation, and as a result would be hard to stabilize. Of course, we can also design our own stable json representation, but at that point we are really just re-inventing the SQL wheel.

Test build #48657 has started for PR 10541 at commit ef5dac2.

@rxin Thanks for helping explaining this.
@hvanhovell Would also like to add that, once fully implemented, SQL statement generation itself can be quite useful, and not limited to native view support. One example is random query generation in integration tests.

Test build #48660 has started for PR 10541 at commit 4963676.

Test build #48657 has finished for PR 10541 at commit ef5dac2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48657/
Test FAILed.

Test build #48660 has finished for PR 10541 at commit 4963676.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48660/
Test FAILed.

Hm, seems that my last fixes introduced bug related to UDF handling. Looking into it.

Test build #48665 has started for PR 10541 at commit 70af178.

The following two test cases always fail when executed with other test cases, but always pass when executed separately:

HiveCompatibilitySuite.select_as_omitted
HiveCompatibilitySuite.router_join_ppr

Both test cases complain table src not found when failing. Probably because of side effects done in test cases executed earlier. Still investigating.

According to local testing result, now 75% query plans in HiveCompatibilitySuite can be successfully converted to SQL query strings.

Test build #48667 has started for PR 10541 at commit 1d5dd3b.

Test build #48665 has finished for PR 10541 at commit 70af178.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48665/
Test FAILed.

Test build #48667 has finished for PR 10541 at commit 1d5dd3b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48667/
Test FAILed.

Merged build finished. Test FAILed.

@liancheng
One thing about testing infrastructure: It is a good idea to use the existing Hive compatibility tests to bootstrap your test coverage. However, for every test failure that you find, we should create unit tests specifically built for the SQL conversion and increase the coverage of that. In the long run, we should not depend on the Hive compatibility tests.

Test build #48763 has started for PR 10541 at commit 1e50288.

Test build #48763 has finished for PR 10541 at commit 1e50288.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
case class Subquery(alias: String, child: LogicalPlan) extends UnaryNode

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48763/
Test FAILed.

Test build #48779 has started for PR 10541 at commit 1796540.

Test build #48781 has started for PR 10541 at commit a8805dd.

Test build #48781 has finished for PR 10541 at commit a8805dd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48781/
Test PASSed.

Merged build finished. Test PASSed.

Test build #48779 has finished for PR 10541 at commit 1796540.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48779/
Test FAILed.

Tests finally pass! (The last build failure was actually triggered by an older commit.)

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48822/
Test FAILed.

Merged build finished. Test FAILed.

test this please

Test build #48828 has started for PR 10541 at commit 83e28fc.

Test build #48828 has finished for PR 10541 at commit 83e28fc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48828/
Test PASSed.

Added support for more expressions and logical plans. Now 94.2% queries in HiveCompatibilitySuite are covered (window functions are not included in this suite). Unsupported expressions and logical plans are listed in the PR description, and can be done in follow-up PRs.
cc @yhuai

Removed the WIP tag.

@rxin SQL generation dedicated test cases are added in HiveQLSQLBuilderSuite. Bugs found by round-trip tests in HiveCompatibilitySuite are covered there.

Test build #48860 has started for PR 10541 at commit 2e784b9.

Test build #48860 has finished for PR 10541 at commit 2e784b9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48860/
Test FAILed.

Test build #48894 has started for PR 10541 at commit c118a35.

Does this version support data source tables? Also, we need to move ComputeCurrentTime to optimizer, right?

The framework of generating sql looks good. We can use follow-up prs to support more operators.

Test build #48894 has finished for PR 10541 at commit c118a35.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48894/
Test PASSed.

Merged build finished. Test PASSed.

@yhuai For data source tables, I only explicitly supported Parquet tables. Other data sources can be added in follow-up PRs. And yes, I forgot to move ComputeCurrentTime to the optimizer. Thanks for reminding.

Moved ComputeCurrentTime to the optimizer.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48904/
Test FAILed.

Test build #48906 has started for PR 10541 at commit 11807bd.

Test build #48906 has finished for PR 10541 at commit 11807bd.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48906/
Test FAILed.

Test build #48940 has started for PR 10541 at commit a304392.

Test build #48940 has finished for PR 10541 at commit a304392.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48940/
Test FAILed.

Test build #48949 has started for PR 10541 at commit 2073e30.

Test build #48949 has finished for PR 10541 at commit 2073e30.

This patch fails from timeout after a configured wait of `250m`.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class ComputeCurrentTimeSuite extends PlanTest

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48949/
Test FAILed.

test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48974/
Test FAILed.

test this please

Test build #48996 has started for PR 10541 at commit 2073e30.

Test build #48996 has finished for PR 10541 at commit 2073e30.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class ComputeCurrentTimeSuite extends PlanTest

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48996/
Test PASSed.

Let's also create a jira for supporting persisted data source tables.

Test build #49026 has started for PR 10541 at commit 97cd39e.

LGTM pending jenkins.

Test build #49026 has finished for PR 10541 at commit 97cd39e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/49026/
Test PASSed.

Merging to master.

Thanks all for the review!


(#371) Pre-stage CI-jobs' script changes to work with Makefile changes.

Upcoming PR #332 changes Makefile targets to build the library. Those
changes will require changes to the commands invoked by CI-jobs to build
and test the library. This commit pre-stages those CI-build script
changes, so that the upcoming Makefile changes can be tested independently
before they are merged to /main. (This change depends on PR #372, which
adds minimal support for 'help' target to Makefile.)

Hi, @rtjohnso - I assigned this CI-scripts review to you, which goes on top of (after) the fix for PR #372 . That one is also assigned to you.
This is a song-and-dance we have to play to smooth out the pavement for integrating your Makefile changes upcoming under PR #332.
If you can do a quick review & sign-off of the previous PR; i.e. PR #372 ), I have to do some manual testing of this PR's changes to apply them to the pipeline, after merging that to /main.
It's confusing ... and late on a Friday. Let's see what you can do ... or I'll wait till Monday.

Thanks for reviewing this at short-notice, @ajhconway and also for looking at https://github.com/vmware/splinterdb/pull/372.
I am going to merge this to /main, so I can go back to re-stabilizing Rob's Makefile rework on top of these CI-infra changes.


Decouple renderer from view

After code analysis by @enicolasgomez , we should look into decoupling the renderer from the view. This way it will separate the rendering code from the view, and make it easier to update rendering libraries in the future.

@zsinnema I think that no matter if we'll be using an other 3d library or not, this is something that should be improved.

Here's the Pull request ready for this task:
https://github.com/MetaCell/open-physiology-viewer/pull/52


Double orders issue

Expected behavior
After a customer has paid using the Mollie Payment module then 1 order must be created.
Actual behavior
Most orders are created properly. But we have already seen 3x on different PrestaShops that sometimes an order is created 2x. A few important notes:

We noticed that the double orders were all paid via Rabobank. (betalen.rabobank.nl)
The first order has a transaction ID, the second does not.
The 2 double orders have exactly the same times.
The 2 orders have the same CART ID
The 2 orders both have their own ORDER ID

Environment
PrestaShop version: 16.1.23 / <IP_ADDRESS>
Mollie module version: 3.3.5
PHP version: Current PHP version: 5.6.40 / 7.2.2

Hi @wouterb038 ,
Unfortunately Prestashop's order validation is prone to race conditions so this may happen from time to time. We're still looking for ways to minimize this problem. One (partial) solution you could try right now is to add a UNIQUE constraint to the referencecolumn of the ps_orders table (replace ps_ with your own prefix).
Kind regards


[WIP] Classifier upgrade and examples updates

export new classifier from [2016, 2017, 2018] nvd feed
update integratino example

Signed-off-by: Marek Cermak<EMAIL_ADDRESS>modified:   examples/example_app_integration.ipynb
new file:   examples/export/classifier.1531218732.518835.checkpoint

@CermakM Your image is available in the registry: docker pull MISSING_REGISTRY_NAME/MISSING_IMAGE_NAME:SNAPSHOT-PR-20

@CermakM Your image is available in the registry: docker pull MISSING_REGISTRY_NAME/MISSING_IMAGE_NAME:SNAPSHOT-PR-20

@CermakM Your image is available in the registry: docker pull MISSING_REGISTRY_NAME/MISSING_IMAGE_NAME:SNAPSHOT-PR-20

@CermakM Your image is available in the registry: docker pull MISSING_REGISTRY_NAME/MISSING_IMAGE_NAME:SNAPSHOT-PR-20


updated checkout-ui-extensions to latest 0.19.0

WHY are these changes introduced?
We need to update the cli template for scaffolded extensions to use version 0.19.0. This package was just released today.
WHAT is this pull request doing?
Bumps up the version number.
Tophatting
Scaffold a new app with a Checkout UI extension and validate the version 0.19.0 is present in the package.json of the app.
Post-release steps
N/A

[ ] I've made sure that any changes to dev or deploy have been reflected in the the documentation.

Measuring impact
How do we know this change was effective? Please choose one:

[ ] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[ ] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[ ] I've considered possible documentation changes

I had trouble tophatting this. Trying to scaffold an extension still gave me version 0.18.0 of @shopify/checkout-ui-extensions still. I recall I had this issue the last time I bumped the versions as well.
These are the steps we are using:

Clone the cli repo
Within the cli repo, run yarn create-app --path ~
Within the app path, run yarn shopify app scaffold extension

🎩 success when creating a new app/extension


[$250] Chat - Size of text cursor is smaller when returning to any chat via browser back button

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.58-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Go to FAB > Start chat
Create a group chat
Split bill in the group chat
Click on the split preview > Click any split member > Click Message
In 1:1 DM, click on the IOU preview
Click on the header subtitle to return to 1:1 DM
Click browser back button until app returns to the group chat in Step 3

Expected Result:
The size of text cursor will remain the same when returning to group chat via browser back button
Actual Result:
The size of text cursor is smaller when returning to group chat via browser back button
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/04307fb8-cb63-4e23-b779-80bf212633d1
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e868dd4a424eb130
Upwork Job ID:<PHONE_NUMBER>755960832
Last Price Increase: 2024-04-05
Automatic offers:

paultsimura | Reviewer | 0

We think that this bug might be related to #vip-vsp

@marcaaron  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Seems possibly more related to markdown changes.

@thienlnam I asked for a re-test to see. It kinda feels like this would be broken everywhere (sorry if I end up wrong on that hunch).

Definitely possible - I'll add it to the main tracking list. But seems pretty harmless and I don't think needs to be a blocker

Cool. If you are not passionate about it. Then I'm gonna pop the label off.

p.s. confirmed with QA that this is not limited to Group Chats.

Opening this to external contributors!

Proposal
Please re-state the problem that we are trying to solve in this issue.
The size of text cursor is smaller when returning to group chat via browser back button
What is the root cause of that problem?
In here, we didn't check if the height is positive before returning the value. The height could be 0 if the parent element was not fully rendered in the DOM yet.
So on layout change, when we use the method to get the element height here to use as maxHeight, we're getting 0 as the height when returning to the chat via browser back button (and the composer container was not fully rendered in DOM yet), leading to the input height becomes very small and the cursor size is small.
What changes do you think we should make in order to solve the problem?

In here, if the height is 0, we should return auto as the height. So in the next layout effect trigger, when the composer container has been rendered in DOM, it will have positive height and will show in the UI correctly.
if (!height) {
  return 'auto';
}

What alternative solutions did you explore? (Optional)
NA

I'll take a look at it later today! 👀

Makes sense to me! 🙌🏻

If @paultsimura decides to go with your proposal @nkdengineer you can make a PR directly to react-native-live-markdown and we'll try pushing it forward 👀

@BartoszGrajdek  @paultsimura this PR is ready for preview.

PR is merged Mel! Waiting for payment day

Ah nice, thanks @paultsimura! 👍

@paultsimura this PR is ready for preview.

Payment summary:

Contributor: @nkdengineer $250
Contributor+: @paultsimura $250

Please apply or request!

We don't close issues until we get them paid out - but we can remove this from the tracking issue

bump @nkdengineer!

Hi @dylanexpensify, sorry for the delay, I've applied to the job https://www.upwork.com/jobs/~01e868dd4a424eb130

offer sent!

Ah, thanks for the catch, agree. Updated offer, and will pay out $500 in Upwork

@paultsimura paid last week! But just sent bonus along!

@nkdengineer waiting for you to accept offer!

@dylanexpensify I accepted the offer. But the offer was for $250 so I guess a bonus of $250 will be sent too.
Thanks 🙇

Correct! all done btw


Having issues with cron

How do you get cron running?  Some docs say that cron auto runs every 15 minutes not seeing that happen.  I have even tried mounting a script to the 15min cron with no success.  Is there something I am missing?
Should I be running site crons from the host?  This may be a wodby/php issue.

Not sure where you found the information about 15 minutes, normally you don't need cron for your local environment. Nevertheless, you can run cron by launching another php container with the overriden command like we do in our tests.


Add Azure Security for DevOps to CI Pipeline

Interesting, it errors on main.paramaters.json (as I expected, due to the azd ENV=default syntax) but still claims to upload the sarif, so I guess it works? Do the uploaded issues seem correct to you?
Error: An exception occurred while analyzing template /home/runner/work/azure-search-openai-demo/azure-search-openai-demo/infra/main.bicep with parameters file /home/runner/work/azure-search-openai-demo/azure-search-openai-demo/infra/main.parameters.json

Alerts: https://github.com/Azure-Samples/azure-search-openai-demo/security/code-scanning?query=pr%3A557+tool%3Atemplateanalyzer+is%3Aopen

I've set it to only collect the errors now and not fail the build/CI process so we can work through them.

@tonybaloney Okay, I somehow hadn't realized that it could upload the sarif even after an error, that opens the door to using this one more repos. Next you can try to resolve one of the issues and see if the alert gets closed. :)


Has anyone got this to work well with Probuilder?

Hi, been using the tool for a while, I started using Probuilder, but the issue is that the outline is broken apart.

Okay, so you just smooth the normals to fix it, right? Well, you can't use the smoothing utility in the toon shader because you can't input a probuilder mesh. So I use the smoothing tool in Probuilder...

Now that fixes the outline issue, but the faces look all weird. And changing the UV in the UV editor does nothing!
Has anyone got the outliner to work nice using Probuilder without messing up mesh faces?
I like the Smoothing tool that the shader uses because it doesn't alter the faces.

Probuilder should support exporting it's objects to barebones Unity meshes, which you can then pass to the smoothing utility.
https://forum.unity.com/threads/probuilder-convert-to-mesh.1027114/


Replace verbose domain second display with enhanced title

Replaces verbose second display with title tags
Adds css to distinguish tags with title attributes
Fixes bug in support tickets and getObjectByLabelLazily filtering on id

Coverage increased (+0.02%) to 82.329% when pulling aeaaed238ed78ca5a911e5e2c43b0d3b9c3d7193 on eatonphil:domain-description-title into 62c0a999ddfec0fab6c234842dba7e8fc4d5fd86 on linode:master.

can we delay the dotted underline pattern? it makes me think these fields are inline editable

Coverage increased (+0.02%) to 82.329% when pulling c3585c66b6299eda1ec4fce23f443ef23719c0bb on eatonphil:domain-description-title into 62c0a999ddfec0fab6c234842dba7e8fc4d5fd86 on linode:master.


Docker

closes #30

[x] Dockerise
[x] Deploy package to GitHub Container Registry https://github.com/orgs/EddieHubCommunity/packages/container/package/api

@khattakdev yes you are right, that will need to be added 👍


[SPARK-40481][CORE] Ignore stage fetch failure caused by decommissioned executor

What changes were proposed in this pull request?
Add a config spark.stage.ignoreDecommissionFetchFailure to control whether ignore stage fetch failure caused by decommissioned executor when count spark.stage.maxConsecutiveAttempts
Fetch failure only be ignored when executors are in below condition:

Waiting for decommission start
Under decommission process

Fetch failure might not be ignored when executors are in below condition, but this is best effort approach based on current mechanism.

Stopped or terminated after finishing decommission
Under decommission process, then removed by driver with other reasons

Why are the changes needed?
When executor decommission is enabled, there would be more stage failure caused by FetchFailed from decommissioned executor, further causing whole job's failure. One reason is decommissioning executor won't wait all FetchData requests to be finished, it will self-exit when no running tasks and migration finished. It would be better not to count such failure in spark.stage.maxConsecutiveAttempts. AWS EMR already supported this. Please refer https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-spark-configure.html
Does this PR introduce any user-facing change?
Yes
How was this patch tested?
Added test in DAGSchedulerSuite

The following claims seems to be too general to be true. Could you be more specific, @warrenzhu25 ?

When executor decommission is enabled, there would be many stage failure caused by FetchFailed from decommissioned executor,

cc @holdenk too

Updated description.

Thank you for the swift updates, @warrenzhu25 .

I made a few comments. BTW, thank you for working on this area, @warrenzhu25 .

Can one of the admins verify this patch?

@dongjoon-hyun Any more comments?

Sorry. I was too busy about 3.3.1 preparation. Will resume the review again for this new improvement.


Renamed the package to be more unique

Current dependencies on/for this PR:

main

PR #8   👈

This stack of pull requests is managed by Graphite.


DatasetInfo/DepositorSetupInfo naming

Making JSON output names consistent with AnalysisPlan where attributes representing object_id's end with _id as in:

dataset_id
depositor_setup_info_id
etc

Updates

Direct File Upload
[ ] updated to be consistent with GET DatasetInfo
Make this more complete (e.g. full DatasetInfo)
Get Dataset info

updated tests to reflect attribute updates
creator_id
creator_name

Depositor Setup Info

creator_id
creator_name

closing with #799


Feature Request

Somewhat different than what @jakovkacan requested, is it possible to add a feature where the user can opt out of seeing the broadcasted message? So like maybe /togglebroadcastview (or tbv or something like that) which makes it so only that user running the command doesn't receive the autobroadcasts?

That is definitely a feature I may add in a coming update.


Not usable on Intel macs

Overview
I couldn't use this on an Intel Mac. For some reason, it could not load custom models (miniqa or distilbert), the only model that works is NativeEmbeddings
Here is the logs:
2023-08-09 17:28:57.802134+0800 BasicExample [50044:803119] Metal API Validation Enabled
2023-08-09 17:28:59.012154+0800 BasicExample[50044:8031191 [espresso
[Espresso::handle ex plan] exception=Espresso exception: "Invalid state": inner product kernel p.has biases is true, but biases were not found! [Exception from Layer: 24:x_9_cast.
2023-08-09 17:28:59.012343+0800 BasicExample[50044:803119] [coremll Error computing NN outputs -1
2023-08-09 17:28:59.012400+0800 BasicExample[50044:803119] [coreml] Failure in
-executePlan:error:.
Failed to generate a test input vector

I'm totally clueless at this point. Can you give some pointer @ZachNagengast
PS: I'm using a remote mac to test. Happy to give you access for debugging.
EDIT: I did some more testing and looks like the CoreML model can only run on CPU or Neural Engine, not GPU.

I don't understand why the tests all pass with Github Actions, on x86_64 machine 😅
My uneducated guess is that in the tests, it uses CPU only and not GPU (Metal). What do you think? @ZachNagengast

Thanks for the info, investigating.

@longseespace I'm having trouble replicating this on my machine, can you try out the PDFExample and see if it persists? The BasicExample is really pared down and may be missing some stuff needed to run distilbert on it, but the PDFExample uses distilbert by default.

@ZachNagengast I'm going to share the remote mac I used to replicate the issue (via DM on Twitter). It's not the problem with distilbert but any coreml model converted from huggingface (I think). I tested with miniqa and got the same issue.

Follow up: appeared to be an issue with xcode in macOS 12, recommended using macOS 13 or above to build apps with this lib.

@ZachNagengast can you share more info on that? I've been building PDF Pals on macOS 13.

@longseespace It was just that remote mac you sent to test out, it was running macOS 12. The target is ok to be macOS 13 just as long as the underlying operating system is also macOS 13 or above.

Hello @ZachNagengast @longseespace
This error is still present, how to overcome this error or how to fix it


Support returning entities from commands

Currently when you call a command, such as create:
ROM.command(:users).create.call(name: 'Test', email<EMAIL_ADDRESS>
The return value is a hash, in most cases it would be useful to return an entity, or collection of entities, this should be relatively simple to implement, suggested API for configuration is:
class CreateUser < ROM::Commands::Create[:memory]
  register_as :create
  relation :users
  result :one, as: :entity # The as: :entity option here
end

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9945847-support-returning-entities-from-commands?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F155789&utm_medium=issues&utm_source=github).

Wondering about Virtus style syntax for this, i.e.
class CreateUser < ROM::Commands::Create[:memory]
  register_as :create
  relation :users
  result Array[User]
end
class CreateUser < ROM::Commands::Create[:memory]
  register_as :create
  relation :users
  result User
end

no, sorry this can't be done like that - first of all it requires model constants to be defined when commands are loaded, secondly it makes command now how to instantiate objects (which is not their responsibility), thirdly - I really don't like that syntax anymore, it can't be used consistently and requires more complexity, it's going away in virtus 2.0.

Yeah, thought about it when I went to bed last night, realise why you mentioned some kind of DI container as this method relies on constructor mass-assignment.

This is done in #187 - pls take a look, I'd like to merge it in :)


update to latest

Need latest as it supports wifi on the portenta

@AndyBlightLeeds I'm not sure how to fix this? The using command line instructions tells me its up to date?

@nfry321 As discussed, create a new branch and merge the change to the repos file into that. Much easier!


install package error: npm-3.5.2 install of alarmFeed in alarm package gives ENOTDIR error

Environment details:
local deployment on self-built kubernetes cluster
Kubernetes version: 1.23.3
ubuntu version: 20.04.4 LTS (kernel: Linux 5.13.0-51-generic)
Steps to reproduce the issue:

use the openwhisk-deploy-kube project provided helm charts to install openwhisk
all other pods are ok, but the owdev-install-packages keeps failing

I had labeled my node as invoker.
Provide the expected results and outputs:
owdev-install-packages pod has status Completed
Provide the actual results and outputs:
owdev-install-packages pod has status Completed
Additional information you deem important:
This happened last week when re-deploy openwhisk.
After doing some investigation, I found the problem is the npm package install for alarm package. I inspected the log of the failing pods and successfully reproduced issue by interactively launching the container. The owdev-install-package pod uses container image by openwhisk/tols/ow-utils/Dockerfile. The npm installed by apt has the version:
{ npm: '3.5.2',
  ares: '1.14.0',
  cldr: '32.0.1',
  http_parser: '2.7.1',
  icu: '60.2',
  modules: '57',
  nghttp2: '1.30.0',
  node: '8.10.0',
  openssl: '1.0.2n',
  tz: '2017c',
  unicode: '10.0',
  uv: '1.18.0',
  v8: '6.2.414.50',
  zlib: '1.2.11' }

Install fails for the openwhisk-deploy-kube/helm/openwhisk/configMapFiles/installPackages/myTask.sh at L104
#####
# Install the catalog for the Alarm provider
#####

if [ "$OW_INSTALL_ALARM_PROVIDER" == "yes" ]; then
    cd /
    git clone https://github.com/apache/openwhisk-package-alarms.git

    pushd /openwhisk-package-alarms
        git checkout $OW_GIT_TAG_OPENWHISK_PACKAGE_ALARMS
        ./installCatalog.sh $WHISK_AUTH $WHISK_API_HOST_URL $WHISK_API_HOST_URL worker0 $PROVIDER_DB_URL $ALARM_DB_PREFIX || exit 1
    popd
fi

Looking at the log of failed pod, problem is the npm install command at L95 in openwhisk-package-alarms/installCatalog.sh
cp -f alarmFeed_package.json package.json
npm install

The output:
<EMAIL_ADDRESS>/openwhisk-package-alarms/action
├──<EMAIL_ADDRESS>extraneous
├──<EMAIL_ADDRESS>extraneous
├──<EMAIL_ADDRESS>extraneous
├──<EMAIL_ADDRESS>extraneous
├──<EMAIL_ADDRESS>extraneous
└─┬<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>No license field.
npm ERR! Linux 5.13.0-51-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v8.10.0
npm ERR! npm  v3.5.2
npm ERR! path<EMAIL_ADDRESS>npm ERR! code ENOTDIR
npm ERR! errno -20
npm ERR! syscall open

npm ERR! ENOTDIR: not a directory, open<EMAIL_ADDRESS>npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /openwhisk-package-alarms/action/npm-debug.log

That seems to be an issue of using old version of npm. A recent issue under npm/cli here also report their application suddenly broke last week.

It can be fixed by using a newer version of npm in the docker image of ow-utils. Configuring the helm charts in openwhisk-deploy-kube to use the updated image, I have successfully deployed it as before.

Thank you for reporting this.
Why don't you contribute the change to fix the issue as you already clearly analyzed the culprit?

Thank you for reporting this. Why don't you contribute the change to fix the issue as you already clearly analyzed the culprit?

Sure. I'd love to :). Opened a PR here #5261. As for the contribution guideline, I have submitted signed Apache CLA, waiting for the reply.

Update of image tags at openwhisk-deploy-kube helm charts has been merged.

@hugy718 Nice! Thank you for the contribution.