[SPARK-11819][SQL] nice error message for missing encoder

before this PR, when users try to get an encoder for an un-supported class, they will only get a very simple error message like Encoder for type xxx is not supported.
After this PR, the error message become more friendly, for example:
No Encoder found for abc.xyz.NonEncodable
- field (class: "abc.xyz.NonEncodable", name: "a")
- field (class: "abc.xyz.MyClass", name: "b")
- root object (class: "abc.xyz.AnotherClass")

cc @marmbrus

Test build #46217 has started for PR 9810 at commit 3d9fcc9.

Test build #46217 has finished for PR 9810 at commit 3d9fcc9.

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/46217/
Test FAILed.

Test build #46220 has started for PR 9810 at commit 8d8d857.

Test build #46220 has finished for PR 9810 at commit 8d8d857.

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/46220/
Test FAILed.

This message looks great!

This is really cool.

Test build #46328 has started for PR 9810 at commit da13931.

Test build #46328 has finished for PR 9810 at commit da13931.

This patch fails Scala style 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/46328/
Test FAILed.

Test build #46329 has started for PR 9810 at commit ddb092a.

Test build #46329 has finished for PR 9810 at commit ddb092a.

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/46329/
Test FAILed.

retest this please.

Test build #46335 has started for PR 9810 at commit ddb092a.

Test build #46335 has finished for PR 9810 at commit ddb092a.

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/46335/
Test PASSed.

Merged build finished. Test PASSed.

Test build #46385 has started for PR 9810 at commit c263c14.

Test build #46385 has finished for PR 9810 at commit c263c14.

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/46385/
Test PASSed.

Thanks, merging to master and 1.6.

I think that this doesn't work on Scala 2.11: https://amplab.cs.berkeley.edu/jenkins/view/Spark-QA-Compile/job/Spark-Master-Scala211-Compile/2156/console

@JoshRosen , I think the reason maybe that, I defined some private methods in trait ScalaReflection and use them in object ScalaReflection extends ScalaReflection, seems scala 2.11 doesn't support this, let me change those methods to public and see if it works.


Pipenv can't install black because black is only a pre-release

Environment data

VS Code version: Version 1.34.0-insider
Extension version (available under the Extensions sidebar): 2019.3.6558
OS and version: macOS 10.14
Python version (& distribution if applicable, e.g. Anaconda): project is using 3.7.2, pyenv with global python set to 3.7.3
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pipenv
Relevant/affected Python packages and their versions: black 19.3b0

Expected behaviour
Black installs ok
Actual behaviour
Black fails to install because there are only beta releases and pipenv doesn't look for those by default
Steps to reproduce:

When the popup asks to select a linter, choose black and install it.

Pipenv will fail to install since --pre isn't provided

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Formatting with black failed.
You could either install the 'black' formatter, turn it off or use another formatter.
Error: Module 'black' not installed.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
Not Applicable

Output from terminal:
pipenv install black --dev      Mon Apr  8 21:53:53 2019
Installing black…
Adding black to Pipfile's [dev-packages]…
✔ Installation Succeeded
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
✘ Locking Failed!
[pipenv.exceptions.ResolutionFailure]:   File "/Users/erin/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pipenv/resolver.py", line 70, in resolve
[pipenv.exceptions.ResolutionFailure]:       req_dir=requirements_dir
[pipenv.exceptions.ResolutionFailure]:   File "/Users/erin/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pipenv/utils.py", line 746, in resolve_deps
[pipenv.exceptions.ResolutionFailure]:       req_dir=req_dir,
[pipenv.exceptions.ResolutionFailure]:   File "/Users/erin/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pipenv/utils.py", line 500, in actually_resolve_deps
[pipenv.exceptions.ResolutionFailure]:       resolved_tree = resolver.resolve()
[pipenv.exceptions.ResolutionFailure]:   File "/Users/erin/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pipenv/utils.py", line 415, in resolve
[pipenv.exceptions.ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]:       pipenv.exceptions.ResolutionFailure: ERROR: ERROR: Could not find a version that matches black
[pipenv.exceptions.ResolutionFailure]:       Skipped pre-versions: 18.3a0, 18.3a0, 18.3a1, 18.3a1, 18.3a2, 18.3a2, 18.3a3, 18.3a3, 18.3a4, 18.3a4, 18.4a0, 18.4a0, 18.4a1, 18.4a1, 18.4a2, 18.4a2, 18.4a3, 18.4a3, 18.4a4, 18.4a4, 18.5b0, 18.5b0, 18.5b1, 18.5b1, 18.6b0, 18.6b0, 18.6b1, 18.6b1, 18.6b2, 18.6b2, 18.6b3, 18.6b3, 18.6b4, 18.6b4, 18.9b0, 18.9b0, 19.3b0, 19.3b0
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.
 Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: ERROR: Could not find a version that matches black
Skipped pre-versions: 18.3a0, 18.3a0, 18.3a1, 18.3a1, 18.3a2, 18.3a2, 18.3a3, 18.3a3, 18.3a4, 18.3a4, 18.4a0, 18.4a0, 18.4a1, 18.4a1, 18.4a2, 18.4a2, 18.4a3, 18.4a3, 18.4a4, 18.4a4, 18.5b0, 18.5b0, 18.5b1, 18.5b1, 18.6b0, 18.6b0, 18.6b1, 18.6b1, 18.6b2, 18.6b2, 18.6b3, 18.6b3, 18.6b4, 18.6b4, 18.9b0, 18.9b0, 19.3b0, 19.3b0
There are incompatible versions in the resolved dependencies.
[pipenv.exceptions.ResolutionFailure]:       req_dir=requirements_dir
[pipenv.exceptions.ResolutionFailure]:   File "/Users/erin/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pipenv/utils.py", line 746, in resolve_deps
[pipenv.exceptions.ResolutionFailure]:       req_dir=req_dir,
[pipenv.exceptions.ResolutionFailure]:   File "/Users/erin/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pipenv/utils.py", line 500, in actually_resolve_deps
[pipenv.exceptions.ResolutionFailure]:       resolved_tree = resolver.resolve()
[pipenv.exceptions.ResolutionFailure]:   File "/Users/erin/.pyenv/versions/3.7.2/lib/python3.7/site-packages/pipenv/utils.py", line 415, in resolve
[pipenv.exceptions.ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]:       pipenv.exceptions.ResolutionFailure: ERROR: ERROR: Could not find a version that matches black
[pipenv.exceptions.ResolutionFailure]:       Skipped pre-versions: 18.3a0, 18.3a0, 18.3a1, 18.3a1, 18.3a2, 18.3a2, 18.3a3, 18.3a3, 18.3a4, 18.3a4, 18.4a0, 18.4a0, 18.4a1, 18.4a1, 18.4a2, 18.4a2, 18.4a3, 18.4a3, 18.4a4, 18.4a4, 18.5b0, 18.5b0, 18.5b1, 18.5b1, 18.6b0, 18.6b0, 18.6b1, 18.6b1, 18.6b2, 18.6b2, 18.6b3, 18.6b3, 18.6b4, 18.6b4, 18.9b0, 18.9b0, 19.3b0, 19.3b0
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.
 Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: ERROR: Could not find a version that matches black
Skipped pre-versions: 18.3a0, 18.3a0, 18.3a1, 18.3a1, 18.3a2, 18.3a2, 18.3a3, 18.3a3, 18.3a4, 18.3a4, 18.4a0, 18.4a0, 18.4a1, 18.4a1, 18.4a2, 18.4a2, 18.4a3, 18.4a3, 18.4a4, 18.4a4, 18.5b0, 18.5b0, 18.5b1, 18.5b1, 18.6b0, 18.6b0, 18.6b1, 18.6b1, 18.6b2, 18.6b2, 18.6b3, 18.6b3, 18.6b4, 18.6b4, 18.9b0, 18.9b0, 19.3b0, 19.3b0
There are incompatible versions in the resolved dependencies.

Proposed solution:

Add the --pre flag to the pipenv command when black is chosen and installed.

I propose adding a very very simple clause to https://github.com/erinxocon/vscode-python/blob/e441ed614fe9ccda1818e19acbba5ab8d82d772c/src/client/common/installer/pipEnvInstaller.ts#L33
        const args = ['install', moduleName, '--dev'];
        if (moduleName === 'black') {
            args.push('--pre');
        }
        return {
            args: args,
            execPath: pipenvName
        };

I am concerned though, this places the burden on the VS Code development team when black comes out with a non-pre version.  The other option could be to instruct the user to do this manually passing the --pre flag.  The reason I bring this up is that I believe, and @techalchemy can correct me if I'm wrong, but when --pre is passed as an argument this applies to the whole locking process and any package that has a pre-releases would end up being resolved and installed when the user might not expect.

@erinxocon, thanks for letting us know about this.  We'll look into it.

@ericsnowcurrently thanks!  I'm willing to work on a PR once a decision is reached on how to handle this edge case.  I helped develop pipenv and am very familiar with it's workings 🌈🍰🌈

this applies to the whole locking process and any package that has a pre-releases would end up being resolved and installed when the user might not expect.

Agreed, we will have to make an exception with black
Please feel free to submita PR with the pre flag just for black.
I.e. your suggestion is perfect


Add note on README about OSX install and PyTorch 1.1

Codecov Report

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

@@           Coverage Diff           @@
##           master     #939   +/-   ##
=======================================
  Coverage   60.26%   60.26%
=======================================
  Files          63       63
  Lines        5001     5001
  Branches      745      745
=======================================
  Hits         3014     3014
  Misses       1784     1784
  Partials      203      203

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 9ffeeb5...fabcbae. Read the comment docs.


Rails4 search

Basically all the changes you saw at the meeting today (6/27/17), with the addition of a few bug fixes in handling search results with no interactions.
To summarize:

Drug/Gene/Interactions view updates
Search form updates (preset filters, facelift)
Search results updates (sidebar with toggling, ambiguous vs definite matches)
Various visual fixes to site

Hey @yanyangfeng, it looks like there's a test failure here associated with filter chaining that needs to be addressed.

CI, test this.

closes #174


there is no index.min.js in npm package

it only has index.js, is this because of this problem?

@Kelin2025

Meh, forgot to build before packaging the app. Fixed in 2.0.2


Trigger don't work in tailwind modal

Hi, i have a strange situation. Datepicker works ok in a custom page, but when i try to show in a modal, trigger doesn't work and datepicker doesn't show.

As you can see, display:none is the status of the class, even when i focused or used custom trigger.
I tried without a modal and it's work ok...
Thanks in advance.

are you using teleport for modal?

Hi !
I think I had the same problem using the headlessui components.
This slide-over precisely https://tailwindui.com/components/application-ui/overlays/slide-overs#component-b76ed25b74c40b7f3a181393e2b7742f
I had to remove the <Dialog> to have it work

are you using teleport for modal?

Yes, i'm using teleport (headlessui use it). But recently i move from headlessui 1.0.0 to 1.1.0. I'm rollback that change and see if the issue still happens.

Hi !
I think I had the same problem using the headlessui components.
This slide-over precisely https://tailwindui.com/components/application-ui/overlays/slide-overs#component-b76ed25b74c40b7f3a181393e2b7742f
I had to remove the <Dialog> to have it work

Ok, thanks mate. But i need that  component. Also i tried without headlessui (build the modal by html) but still happens.

With headlessui 1.0.0 seems to work.
1.1.0 not work.
1.2.0 not work.

some trick,
<template>
<!-- @headlessui/vue -->
<litepie-datepicker ref="litepieRef"
      v-model="dateValue"
      @click="litepieRef.isShow = !litepieRef.isShow"
  ></litepie-datepicker>
<!-- @headlessui/vue -->
<template>

<script>
export default {
   setup() {
     const litepieRef = ref(null)

     return {
       litepieRef
     }
   }
}
</script>

some trick,
<template>
<!-- @headlessui/vue -->
<litepie-datepicker ref="litepieRef"
      v-model="dateValue"
      @click="litepieRef.isShow = !litepieRef.isShow"
  ></litepie-datepicker>
<!-- @headlessui/vue -->
<template>

<script>
export default {
   setup() {
     const litepieRef = ref(null)

     return {
       litepieRef
     }
   }
}
</script>

ohh Nice workaround!
Works great!
Thank you!

Nice, it works fine for me too !
Thank you very much :)

some trick,
<template>
<!-- @headlessui/vue -->
<litepie-datepicker ref="litepieRef"
      v-model="dateValue"
      @click="litepieRef.isShow = !litepieRef.isShow"
  ></litepie-datepicker>
<!-- @headlessui/vue -->
<template>

<script>
export default {
   setup() {
     const litepieRef = ref(null)

     return {
       litepieRef
     }
   }
}
</script>

Seems close when click outside the component does not work by this

To handling the click outside event, i add directive :
`app.directive('clickOutside', {
beforeMount: (selectedEl, binding) => {
selectedEl.eventSetDrag = () => {
selectedEl.setAttribute('data-dragging', 'yes')
}
selectedEl.eventClearDrag = () => {
selectedEl.removeAttribute('data-dragging')
}
selectedEl.eventOnClick = (event: MouseEvent) => {
const dragging = selectedEl.getAttribute('data-dragging')
// Check that the click was outside the el and its children, and wasn't a drag
if (
!(
selectedEl == event.target ||
selectedEl.contains(event.target)
) &&
!dragging
) {
// call method provided in attribute value
binding.value(event)
}
}
    const initListenerByElement = (el: Element | Document) => {
        el.addEventListener('touchstart', selectedEl.eventClearDrag)
        el.addEventListener('touchmove', selectedEl.eventSetDrag)
        el.addEventListener('click', selectedEl.eventOnClick)
        el.addEventListener('touchend', selectedEl.eventOnClick)
    }

    initListenerByElement(document)

    // Listener when the element is inside the drawer
    const elODrawers = document.querySelectorAll('.el-drawer')
    elODrawers.forEach(elDrawer => initListenerByElement(elDrawer))
},
unmounted: selectedEl => {
    const removeListenerByElement = (el: Element | Document) => {
        el.removeEventListener('touchstart', selectedEl.eventClearDrag)
        el.removeEventListener('touchmove', selectedEl.eventSetDrag)
        el.removeEventListener('click', selectedEl.eventOnClick)
        el.removeEventListener('touchend', selectedEl.eventOnClick)
    }

    removeListenerByElement(document)
    selectedEl.removeAttribute('data-dragging')

    // Remove Listener when the element is inside the drawer
    const elDrawers = document.querySelectorAll('.el-drawer')
    elDrawers.forEach(elDrawer => removeListenerByElement(elDrawer))
}

})`
Example usage :
`<label
v-click-outside="() => (elLitepieDatepicker.isShow = false)"
@click="elLitepieDatepicker.isShow = !elLitepieDatepicker.isShow"

Date Range
`


Try fixing bird-eye camera rolling behaviour when car flips over

Noticed that bird-eye camera might roll along when car flips over, tried solving such issue by moving the bird eye camera out of the vehicle group.
Total newbie in js/r3f and open source projects, any comments on such solution will be very much appreciated.

hey brian, i had to revert - it works well when the car flips but it doesnt follow the cars rotation no more, couldn't figure out how to fix it


I can't resume training

Hi!
How can I resume training?
It seems PSNR resets everytime I run the traning script again.
Thank you!

This is not something that is currently supported by this repo. I'll look into it as an enhancement though


Change to chef.io domain (nearly) everywhere

I fell down this rabbit hole after discovering that the built-in cookbook template still uses https://supermarket.getchef.com for the cookbook source.

LGTM

LGTM :+1:

Merged after a rebase in ee21e92531554caba449a09f33aa012216e915e7


Sunset time is showing Dawn time

In the upper right corner, it's showing the dawn time instead of the sunset time as you would expect.
Looks like it's just a typo on line 32 of the card contents file.

My bad, I changed by mistake when adding the 12h support. Thanks!


[CAMEL-10543] new logo

Nice and clean design :clap:

The shape of the Camel animal looks nice and elegant

Thanks. I wanted it to be minimalistic and aesthetically pleasant, while maintaining the distinctive camel shape.

+1; nice and clean

+1; nice and clean

I know Filip. He's good designer.
+1

Hi we are voting on the received proposals, the vote is open till 15.5. see all the proposals and cast the vote for the three designs you prefer the most.
Also read the news announcement on Camel blog.

Since the vote ended I'm closing the related PRs


More travis

Builds on gh-2 by moving from a "release" (i.e. all roles on galaxy) to a "latest" (i.e. all roles on github) strategy. Note: this is in preparation either for more thorough scanning tools (like https://github.com/nickjj/ansigenome#example-rebuild-output) or our own jenkins job for a "merge" strategy.

Current state needs special omero-common handling and then:

https://galaxy.ansible.com/openmicroscopy/cadvisor/
https://galaxy.ansible.com/openmicroscopy/mysql-backup/
https://galaxy.ansible.com/openmicroscopy/system-monitor-agent/

An aside while I work on getting this PR green since it may take a while:
ome-ansible-molecule-dependencies jamoore$ mkdir vendor; time for x in $(./repos.sh); do git clone --depth=1 git://github.com/openmicroscopy/$x vendor/openmicroscopy.${x##ansible-role-}; done
...
real	0m33.391s
user	0m0.412s
sys	0m1.119s

might be a fairly nice way to "get all
cc: @openmicroscopy/devops

Relaunched travis after a previously unseen issue:
=================================== FAILURES ===================================
_____________ test_omero_managedrepo[docker://omero-server-newdep] _____________
File = <class 'testinfra.modules.base.GNUFile'>
    def test_omero_managedrepo(File):
        d = File('/OMERO/ManagedRepository')
        assert d.is_directory
        assert d.user == 'omero-server'
        assert d.group == 'importer'
>       assert d.mode == 0o2775
tests/test_default.py:75:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <file /OMERO/ManagedRepository>
    @property
    def mode(self):
        # Supply a base of 8 when parsing an octal integer
        # e.g. int('644', 8) -> 420
>       return int(self.check_output("stat -c %%a %s", self.path), 8)
E       ValueError: invalid literal for int() with base 8: ''
../../../../virtualenv/python2.7.12/lib/python2.7/site-packages/testinfra/modules/file.py:209: ValueError

$ diff <(./repos.sh | ./update.py ) .travis.yml
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  594k  100  594k    0     0   497k      0  0:00:01  0:00:01 --:--:--  497k
26d25
< - ROLE=analysis-tools
30,32d28
< - ROLE=cli-utils
< - ROLE=debug-dumpallvars
< - ROLE=devspace
35d30
< - ROLE=haproxy
44d38
< - ROLE=munin-node
48d41
< - ROLE=nfs-share
53d45
< - ROLE=omero-common
59d50
< - ROLE=omero-web-apps
63,65d53
< - ROLE=prometheus
< - ROLE=prometheus-jmx
< - ROLE=prometheus-node

I think the following should work with the current dependencies, are the omitted for a reason?
- ROLE=omero-common
- ROLE=omero-web-apps
- ROLE=prometheus-jmx
- ROLE=prometheus-node

Prometheus only because they are newer than this PR. web-apps I fixed during this repo. common I'm no longer sure about.

Will handle other repos via follows them.


Impossible 'body' field required in GET

Description
I'm seeing an issue where generated typescript types result in some impossible types:
Type error: Argument of type '{ params: { path: { id: string; }; }; }' is not assignable to parameter of type 'FetchOptions<{ parameters: { path: { id: string; }; }; responses: ...snipped
  Property 'body' is missing in type '{ params: { path: { id: string; }; }; }' but required in type '{ body: never; }'.

  10 |
  11 | async function exampleGet() {
> 12 |   const { data, error } = await get(`/v1/endpoint`, {
     |                                                                             ^
  13 |     params: { path: { id: "todo" } },
  14 |   });
  15 | }

I am able to work around it by adding a field body: "" as never, which seems to be forcing TS into the right path.  body: undefined or body: null does not work either.
Reproduction
I used the latest versions of openapi-fetch, openapi-typescript, and an internal OpenAPI spec with only GETs in it.
Something relevant in the generated code seems to be:
export interface components {
...
  responses: never;
  parameters: never;
  requestBodies: never;  // <--
  headers: never;
  pathItems: never;
}

Expected result
I can work out the types in this scenario more easily.
Checklist

[X] I’m willing to open a PR (see CONTRIBUTING.md)

Thanks for filing! I’m going to be merging this repo with openapi-typescript for easier maintenance / bugfixes. I’ve migrated your issue here where we can continue tracking this


Token Metadata |        InvalidMintAuthority: Mint authority provided does not match the authority on the mint

how do i find the authority keypair on my drive?

how do i find the authority keypair on my drive?

How would I know where you put the authority keypair on your hard drive? :thinking:


[ESP32][chip-tool] Operational discovery fails using minimalmdns and server interactions

Problem
After successfully commissioning the all-clusters-app, chip-tool then attempts to send an OnOff toggle command - but the operational discovery fails every time.
chip-tool log:
➜  chip-tool-minimalmdns git:(sve) sudo ./chip-tool onoff toggle 1234 1
Password:
[1660326571236] [81521:5783018] CHIP: [DL] KVS will be written to: file:///tmp/chip_kvs
[1660326571244] [81521:5783018] CHIP: [DL] RequestCallbackOnPendingRead with no dispatch queue: callback may not work (might be ok in tests)
[1660326571248] [81521:5783018] CHIP: [DL] _Init
[1660326571248] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=0
[1660326571248] [81521:5783018] CHIP: [IN] UDP::Init bound to port=57094
[1660326571248] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=0
[1660326571248] [81521:5783018] CHIP: [IN] UDP::Init bound to port=63704
[1660326571248] [81521:5783018] CHIP: [IN] BLEBase::Init - setting/overriding transport
[1660326571248] [81521:5783018] CHIP: [IN] TransportMgr initialized
[1660326571248] [81521:5783018] CHIP: [FP] Initializing FabricTable from persistent storage
[1660326571248] [81521:5783018] CHIP: [TS] Last Known Good Time: 2022-08-12T10:31:42
[1660326571248] [81521:5783018] CHIP: [TS] Setting Last Known Good Time to firmware build time 2022-08-12T10:42:29
[1660326571249] [81521:5783018] CHIP: [FP] Fabric index 0x1 was retrieved from storage. Compressed FabricId 0x3CD98ACD03F42C7B, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1660326571250] [81521:5783018] CHIP: [FP] Fabric index 0x2 was retrieved from storage. Compressed FabricId 0xB9EB2EE43EB30E7E, FabricId 0x0000000000000002, NodeId 0x000000000001B669, VendorId 0xFFF1
[1660326571250] [81521:5783018] CHIP: [FP] Fabric index 0x3 was retrieved from storage. Compressed FabricId 0x9DDB5C230CD139F7, FabricId 0x0000000000000003, NodeId 0x000000000001B669, VendorId 0xFFF1
[1660326571252] [81521:5783018] CHIP: [ZCL] Using ZAP configuration...
[1660326571253] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en5 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571255] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on awdl0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571256] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on llw0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571257] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en3 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571257] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en3 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571258] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en1 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571258] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en1 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571259] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en2 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571259] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en2 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571260] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en4 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571260] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en4 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571261] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on bridge0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571261] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on bridge0 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571262] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on utun0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571263] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on utun1 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571264] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on utun2 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571265] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on utun1000 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571265] [81521:5783018] CHIP: [IN] CASE Server enabling CASE session setups
[1660326571265] [81521:5783018] CHIP: [IN] SecureSession[0x600000860000]: Allocated Type:2 LSID:36936
[1660326571265] [81521:5783018] CHIP: [SC] Allocated SecureSession (0x600000860000) - waiting for Sigma1 msg
[1660326571265] [81521:5783018] CHIP: [DIS] Updating services using commissioning mode 0
[1660326571266] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en5 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571267] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on awdl0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571268] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on llw0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571270] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en3 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571270] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en3 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571271] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en1 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571271] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en1 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571272] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en2 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571272] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en2 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571273] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en4 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571273] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on en4 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571274] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on bridge0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571274] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on bridge0 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571275] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on utun0 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571276] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on utun1 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571277] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on utun2 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:748: Inet Error 0x00000110: Address not found
[1660326571278] [81521:5783018] CHIP: [DL] MDNS failed to join multicast group on utun1000 for address type IPv6: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:788: OS Error 0x02000016: Invalid argument
[1660326571278] [81521:5783018] CHIP: [DIS] CHIP minimal mDNS started advertising.
[1660326571280] [81521:5783018] CHIP: [DL] Using wifi MAC for hostname
[1660326571280] [81521:5783018] CHIP: [DIS] Advertise operational node 3CD98ACD03F42C7B-000000000001B669
[1660326571281] [81521:5783018] CHIP: [DIS] Responding with _matter._tcp.local
[1660326571281] [81521:5783018] CHIP: [DIS] Responding with 3CD98ACD03F42C7B-000000000001B669._matter._tcp.local
[1660326571281] [81521:5783018] CHIP: [DIS] Responding with 3CD98ACD03F42C7B-000000000001B669._matter._tcp.local
[1660326571281] [81521:5783018] CHIP: [DIS] Responding with 88665A53BE19.local
[1660326571281] [81521:5783018] CHIP: [DIS] Responding with 88665A53BE19.local
[1660326571281] [81521:5783018] CHIP: [DIS] Responding with _I3CD98ACD03F42C7B._sub._matter._tcp.local
[1660326571281] [81521:5783018] CHIP: [DIS] CHIP minimal mDNS configured as 'Operational device'.
[1660326571283] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::aede:48ff:fe00:1122
[1660326571285] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571287] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571289] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571292] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571294] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571296] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571298] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571300] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571302] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571304] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571306] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571308] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571310] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571312] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571312] [81521:5783018] CHIP: [DIS] mDNS service published: _matter._tcp
[1660326571312] [81521:5783018] CHIP: [DL] Using wifi MAC for hostname
[1660326571312] [81521:5783018] CHIP: [DIS] Advertise operational node B9EB2EE43EB30E7E-000000000001B669
[1660326571314] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::aede:48ff:fe00:1122
[1660326571314] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571314] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571314] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571316] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571318] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571320] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571323] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571325] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571327] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571329] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571331] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571333] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571335] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571337] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571339] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571341] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571343] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571343] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571343] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571343] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571343] [81521:5783018] CHIP: [DIS] Responding with _matter._tcp.local
[1660326571343] [81521:5783018] CHIP: [DIS] Responding with B9EB2EE43EB30E7E-000000000001B669._matter._tcp.local
[1660326571343] [81521:5783018] CHIP: [DIS] Responding with B9EB2EE43EB30E7E-000000000001B669._matter._tcp.local
[1660326571343] [81521:5783018] CHIP: [DIS] Responding with 88665A53BE19.local
[1660326571343] [81521:5783018] CHIP: [DIS] Responding with 88665A53BE19.local
[1660326571343] [81521:5783018] CHIP: [DIS] Responding with _IB9EB2EE43EB30E7E._sub._matter._tcp.local
[1660326571343] [81521:5783018] CHIP: [DIS] CHIP minimal mDNS configured as 'Operational device'.
[1660326571346] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::aede:48ff:fe00:1122
[1660326571346] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571346] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571346] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571347] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571351] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571352] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571355] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571356] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571359] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571360] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571363] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571365] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571368] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571369] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571372] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571373] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571376] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571378] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571381] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571384] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571388] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571391] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571395] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571398] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571401] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571401] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571401] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571401] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571401] [81521:5783018] CHIP: [DIS] mDNS service published: _matter._tcp
[1660326571401] [81521:5783018] CHIP: [DL] Using wifi MAC for hostname
[1660326571401] [81521:5783018] CHIP: [DIS] Advertise operational node 9DDB5C230CD139F7-000000000001B669
[1660326571405] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::aede:48ff:fe00:1122
[1660326571405] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571405] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571405] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571406] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571409] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571410] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571413] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571414] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571417] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571418] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571421] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571423] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571426] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571427] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571430] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571431] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571435] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571436] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571439] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571443] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571446] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571450] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571453] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571457] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571460] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571460] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571460] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571460] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571460] [81521:5783018] CHIP: [DIS] Responding with _matter._tcp.local
[1660326571460] [81521:5783018] CHIP: [DIS] Responding with 9DDB5C230CD139F7-000000000001B669._matter._tcp.local
[1660326571460] [81521:5783018] CHIP: [DIS] Responding with 9DDB5C230CD139F7-000000000001B669._matter._tcp.local
[1660326571460] [81521:5783018] CHIP: [DIS] Responding with 88665A53BE19.local
[1660326571460] [81521:5783018] CHIP: [DIS] Responding with 88665A53BE19.local
[1660326571460] [81521:5783018] CHIP: [DIS] Responding with _I9DDB5C230CD139F7._sub._matter._tcp.local
[1660326571460] [81521:5783018] CHIP: [DIS] CHIP minimal mDNS configured as 'Operational device'.
[1660326571462] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::aede:48ff:fe00:1122
[1660326571462] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571462] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571462] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571463] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571466] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571468] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571469] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571472] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571474] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571475] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571478] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571480] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571481] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571484] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571487] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571487] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571490] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571493] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571493] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571496] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571498] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571499] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571502] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571505] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571505] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571509] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571511] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571513] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571516] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571518] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571521] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571523] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571526] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571527] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571530] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571532] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571535] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571536] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571536] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571537] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571537] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571537] [81521:5783018] CHIP: [DIS] mDNS service published: _matter._tcp
[1660326571537] [81521:5783018] CHIP: [DL] Using wifi MAC for hostname
[1660326571537] [81521:5783018] CHIP: [DIS] Advertise commission parameter vendorID=65521 productID=32769 discriminator=3840/15
[1660326571539] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::aede:48ff:fe00:1122
[1660326571539] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571539] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571539] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571540] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571543] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571545] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571546] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571549] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571551] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571552] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571555] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571557] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571558] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571561] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571563] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571563] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571566] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571568] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571569] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571572] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571574] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571575] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571578] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571580] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571581] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571584] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571586] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571588] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571592] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571594] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571597] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571599] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571602] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571604] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571608] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571610] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571613] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571615] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571615] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571615] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571615] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571615] [81521:5783018] CHIP: [DIS] Responding with _matterd._udp.local
[1660326571615] [81521:5783018] CHIP: [DIS] Responding with 29AEDFED03CC68D8._matterd._udp.local
[1660326571615] [81521:5783018] CHIP: [DIS] Responding with 88665A53BE19.local
[1660326571615] [81521:5783018] CHIP: [DIS] Responding with 88665A53BE19.local
[1660326571615] [81521:5783018] CHIP: [DIS] Responding with _V65521._sub._matterd._udp.local
[1660326571615] [81521:5783018] CHIP: [DIS] Responding with 29AEDFED03CC68D8._matterd._udp.local
[1660326571615] [81521:5783018] CHIP: [DIS] CHIP minimal mDNS configured as 'Commissioner device'.
[1660326571615] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::aede:48ff:fe00:1122
[1660326571615] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571615] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571615] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326571616] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571618] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571621] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571624] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::14c8:ae22:ffb6:42d
[1660326571624] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571626] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571629] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571632] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:846:906a:4b79:912f
[1660326571633] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571635] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571637] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571641] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:8d60:59a1:eba9:6e75
[1660326571641] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571643] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571646] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571649] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571650] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571652] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571654] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571658] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:fc10:e078:5de2:59ff
[1660326571658] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571660] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571663] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571666] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:2158:a65b:ff18:6b5c
[1660326571666] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571668] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571671] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571674] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:951d:fd2c:569b:45f0
[1660326571675] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571677] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571679] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571683] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from 2603:8080:2a00:9002:e5a0:7560:8114:8244
[1660326571683] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571688] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571690] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571690] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571695] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571697] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::44:28ff:fe95:4900
[1660326571698] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571703] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571705] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::adbf:27fb:99a5:29c2
[1660326571705] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571711] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571713] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::6c6e:42e5:880f:19cb
[1660326571713] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571719] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571720] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from fe80::ce81:b1c:bd2c:69e
[1660326571721] [81521:5783018] CHIP: [DIS] Broadcasting mDns reply for query from <IP_ADDRESS>
[1660326571721] [81521:5783018] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571721] [81521:5783018] CHIP: [DIS] mDNS broadcast full failed in 1 separate send attempts.
[1660326571721] [81521:5783018] CHIP: [DIS] Failed to advertise records: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326571721] [81521:5783018] CHIP: [DIS] mDNS service published: _matterd._udp
[1660326571721] [81521:5783018] CHIP: [CTL] System State Initialized...
[1660326571721] [81521:5783018] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1660326571721] [81521:5783018] CHIP: [CTL] Setting attestation nonce to random value
[1660326571721] [81521:5783018] CHIP: [CTL] Setting CSR nonce to random value
[1660326571721] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=5550
[1660326571721] [81521:5783018] CHIP: [IN] UDP::Init bound to port=5550
[1660326571721] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=5550
[1660326571721] [81521:5783018] CHIP: [IN] UDP::Init bound to port=5550
[1660326571721] [81521:5783018] CHIP: [IN] TransportMgr initialized
[1660326571721] [81521:5783018] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1660326571721] [81521:5783018] CHIP: [CTL] Setting attestation nonce to random value
[1660326571721] [81521:5783018] CHIP: [CTL] Setting CSR nonce to random value
[1660326571723] [81521:5783018] CHIP: [CTL] Generating NOC
[1660326571724] [81521:5783018] CHIP: [FP] Validating NOC chain
[1660326571724] [81521:5783018] CHIP: [FP] NOC chain validation successful
[1660326571724] [81521:5783018] CHIP: [FP] Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1660326571724] [81521:5783018] CHIP: [TS] Last Known Good Time: 2022-08-12T10:42:29
[1660326571724] [81521:5783018] CHIP: [TS] New proposed Last Known Good Time: 2021-01-01T00:00:00
[1660326571724] [81521:5783018] CHIP: [TS] Retaining current Last Known Good Time
[1660326571726] [81521:5783018] CHIP: [FP] Metadata for Fabric 0x1 persisted to storage.
[1660326571728] [81521:5783018] CHIP: [TS] Committing Last Known Good Time to storage: 2022-08-12T10:42:29
[1660326571731] [81521:5783018] CHIP: [CTL] Joined the fabric at index 1. Compressed fabric ID is: 0x0000000000000000
[1660326571731] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=5550
[1660326571731] [81521:5783018] CHIP: [IN] UDP::Init bound to port=5550
[1660326571731] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=5550
[1660326571731] [81521:5783018] CHIP: [IN] UDP::Init bound to port=5550
[1660326571731] [81521:5783018] CHIP: [IN] TransportMgr initialized
[1660326571731] [81521:5783018] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1660326571731] [81521:5783018] CHIP: [CTL] Setting attestation nonce to random value
[1660326571731] [81521:5783018] CHIP: [CTL] Setting CSR nonce to random value
[1660326571731] [81521:5783018] CHIP: [CTL] Generating NOC
[1660326571732] [81521:5783018] CHIP: [FP] Validating NOC chain
[1660326571732] [81521:5783018] CHIP: [FP] NOC chain validation successful
[1660326571732] [81521:5783018] CHIP: [FP] Updated fabric at index: 0x2, Node ID: 0x000000000001B669
[1660326571732] [81521:5783018] CHIP: [TS] Last Known Good Time: 2022-08-12T10:42:29
[1660326571732] [81521:5783018] CHIP: [TS] New proposed Last Known Good Time: 2021-01-01T00:00:00
[1660326571732] [81521:5783018] CHIP: [TS] Retaining current Last Known Good Time
[1660326571734] [81521:5783018] CHIP: [FP] Metadata for Fabric 0x2 persisted to storage.
[1660326571736] [81521:5783018] CHIP: [TS] Committing Last Known Good Time to storage: 2022-08-12T10:42:29
[1660326571738] [81521:5783018] CHIP: [CTL] Joined the fabric at index 2. Compressed fabric ID is: 0x0000000000000000
[1660326571738] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=5550
[1660326571738] [81521:5783018] CHIP: [IN] UDP::Init bound to port=5550
[1660326571738] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=5550
[1660326571738] [81521:5783018] CHIP: [IN] UDP::Init bound to port=5550
[1660326571738] [81521:5783018] CHIP: [IN] TransportMgr initialized
[1660326571738] [81521:5783018] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1660326571738] [81521:5783018] CHIP: [CTL] Setting attestation nonce to random value
[1660326571738] [81521:5783018] CHIP: [CTL] Setting CSR nonce to random value
[1660326571739] [81521:5783018] CHIP: [CTL] Generating NOC
[1660326571739] [81521:5783018] CHIP: [FP] Validating NOC chain
[1660326571739] [81521:5783018] CHIP: [FP] NOC chain validation successful
[1660326571740] [81521:5783018] CHIP: [FP] Updated fabric at index: 0x3, Node ID: 0x000000000001B669
[1660326571740] [81521:5783018] CHIP: [TS] Last Known Good Time: 2022-08-12T10:42:29
[1660326571740] [81521:5783018] CHIP: [TS] New proposed Last Known Good Time: 2021-01-01T00:00:00
[1660326571740] [81521:5783018] CHIP: [TS] Retaining current Last Known Good Time
[1660326571742] [81521:5783018] CHIP: [FP] Metadata for Fabric 0x3 persisted to storage.
[1660326571743] [81521:5783018] CHIP: [TS] Committing Last Known Good Time to storage: 2022-08-12T10:42:29
[1660326571745] [81521:5783018] CHIP: [CTL] Joined the fabric at index 3. Compressed fabric ID is: 0x0000000000000000
[1660326571745] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=5550
[1660326571745] [81521:5783018] CHIP: [IN] UDP::Init bound to port=5550
[1660326571745] [81521:5783018] CHIP: [IN] UDP::Init bind&listen port=5550
[1660326571745] [81521:5783018] CHIP: [IN] UDP::Init bound to port=5550
[1660326571745] [81521:5783018] CHIP: [IN] TransportMgr initialized
[1660326571771] [81521:5783037] CHIP: [TOO] Sending command to node 0x4d2
[1660326571771] [81521:5783037] CHIP: [CSM] FindOrEstablishSession: PeerId = [1:00000000000004D2]
[1660326571771] [81521:5783037] CHIP: [CSM] FindOrEstablishSession: No existing OperationalDeviceProxy instance found
[1660326571771] [81521:5783037] CHIP: [CTL] OperationalDeviceProxy[1:00000000000004D2]: State change 1 --> 2
[1660326571775] [81521:5783037] CHIP: [DIS] Insufficient parsers to process all SRV entries.
[1660326571775] [81521:5783037] CHIP: [DIS] Insufficient parsers to process all SRV entries.
[1660326571775] [81521:5783037] CHIP: [DIS] Insufficient parsers to process all SRV entries.
[1660326571775] [81521:5783037] CHIP: [DIS] Insufficient parsers to process all SRV entries.
[1660326571775] [81521:5783037] CHIP: [DIS] Insufficient parsers to process all SRV entries.
[1660326571775] [81521:5783037] CHIP: [DIS] Insufficient parsers to process all SRV entries.
[1660326571776] [81521:5783037] CHIP: [DIS] Insufficient parsers to process all SRV entries.
[1660326571776] [81521:5783037] CHIP: [DIS] Insufficient parsers to process all SRV entries.
[1660326571971] [81521:5783037] CHIP: [DIS] Checking node lookup status after 201 ms
[1660326572772] [81521:5783044] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326572772] [81521:5783044] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326572772] [81521:5783044] CHIP: [DIS] mDNS broadcast had only partial success: 7 successes and 2 failures.
[1660326574774] [81521:5783044] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326574775] [81521:5783044] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326574775] [81521:5783044] CHIP: [DIS] mDNS broadcast had only partial success: 7 successes and 2 failures.

[1660326578776] [81521:5783044] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on en5:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000041: No route to host
[1660326578776] [81521:5783044] CHIP: [DIS] Warning: Attempt to mDNS broadcast failed on utun1000:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:401: OS Error 0x02000033: Network is unreachable
[1660326578776] [81521:5783044] CHIP: [DIS] mDNS broadcast had only partial success: 7 successes and 2 failures.

[1660326581775] [81521:5783018] CHIP: [CTL] Shutting down the commissioner
[1660326581775] [81521:5783018] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1660326581775] [81521:5783018] CHIP: [CTL] Shutting down the controller
[1660326581775] [81521:5783018] CHIP: [DIS] OperationalDeviceProxy[1:00000000000004D2]: Cancelling incomplete address resolution as device is being deleted.
[1660326581775] [81521:5783018] CHIP: [IN] Expiring all sessions for fabric 0x1!!
[1660326581775] [81521:5783018] CHIP: [FP] Forgetting fabric 0x1
[1660326581775] [81521:5783018] CHIP: [TS] Pending Last Known Good Time: 2022-08-12T10:42:29
[1660326581775] [81521:5783018] CHIP: [TS] Previous Last Known Good Time: 2022-08-12T10:42:29
[1660326581775] [81521:5783018] CHIP: [TS] Reverted Last Known Good Time to previous value
[1660326581775] [81521:5783018] CHIP: [CTL] Shutting down the commissioner
[1660326581775] [81521:5783018] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1660326581775] [81521:5783018] CHIP: [CTL] Shutting down the controller
[1660326581775] [81521:5783018] CHIP: [IN] Expiring all sessions for fabric 0x2!!
[1660326581775] [81521:5783018] CHIP: [FP] Forgetting fabric 0x2
[1660326581775] [81521:5783018] CHIP: [TS] Pending Last Known Good Time: 2022-08-12T10:42:29
[1660326581775] [81521:5783018] CHIP: [TS] Previous Last Known Good Time: 2022-08-12T10:42:29
[1660326581775] [81521:5783018] CHIP: [TS] Reverted Last Known Good Time to previous value
[1660326581775] [81521:5783018] CHIP: [CTL] Shutting down the commissioner
[1660326581775] [81521:5783018] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1660326581776] [81521:5783018] CHIP: [CTL] Shutting down the controller
[1660326581776] [81521:5783018] CHIP: [IN] Expiring all sessions for fabric 0x3!!
[1660326581776] [81521:5783018] CHIP: [FP] Forgetting fabric 0x3
[1660326581776] [81521:5783018] CHIP: [TS] Pending Last Known Good Time: 2022-08-12T10:42:29
[1660326581776] [81521:5783018] CHIP: [TS] Previous Last Known Good Time: 2022-08-12T10:42:29
[1660326581776] [81521:5783018] CHIP: [TS] Reverted Last Known Good Time to previous value
[1660326581776] [81521:5783018] CHIP: [CTL] Shutting down the commissioner
[1660326581776] [81521:5783018] CHIP: [CTL] Stopping commissioning discovery over DNS-SD
[1660326581776] [81521:5783018] CHIP: [CTL] Shutting down the controller
[1660326581776] [81521:5783018] CHIP: [CTL] Shutting down the System State, this will teardown the CHIP Stack
[1660326581776] [81521:5783018] CHIP: [IN] SecureSession[0x600000860000]: Released - Type:2 LSID:36936
[1660326581778] [81521:5783018] CHIP: [DMG] IM WH moving to [Uninitialized]
[1660326581778] [81521:5783018] CHIP: [DMG] IM WH moving to [Uninitialized]
[1660326581778] [81521:5783018] CHIP: [DMG] IM WH moving to [Uninitialized]
[1660326581778] [81521:5783018] CHIP: [DMG] IM WH moving to [Uninitialized]
[1660326581778] [81521:5783018] CHIP: [DMG] All ReadHandler-s are clean, clear GlobalDirtySet
[1660326581778] [81521:5783018] CHIP: [BLE] CancelConnection
[1660326581778] [81521:5783018] CHIP: [DL] Inet Layer shutdown
[1660326581778] [81521:5783018] CHIP: [DL] BLE shutdown
[1660326581778] [81521:5783018] CHIP: [DL] System Layer shutdown
[1660326581778] [81521:5783018] CHIP: [TOO] Run command failure: ../examples/chip-tool/commands/common/CHIPCommand.cpp:418: CHIP Error 0x00000032: Timeout

Attached is the tcpdump for the iterations.
mdns_esp32_ephemeral_5353.pcap.zip
####System Configurations:
When compiling chip-tool (on macOS) with:
scripts/examples/gn_build_example.sh examples/chip-tool chip-tool-minimalmdns-noephemeral chip_mdns=\"minimal\" chip_inet_config_enable_ipv4=true chip_use_ephemeral_port_for_mdns_unicast_query=true

Building with minimalmdns rather than avahi, utilizing ephemeral ports, and enabling server interactions with chip-tool as the Controller

// Modifying examples/chip-tool/commands/common/CHIPCommand.cpp
factoryInitParams.enableServerInteractions = true;

Using regular ESP32 build with all-clusters-app.
Proposed Solution
Operations should be successful always regardless of using avahi or CHIP's minimalmdns solution.

And as another note, when enableServerInteractions is set to FALSE for chip-tool, operational discovery works just fine and the chip-tool controller is able to send OnOff toggle commands no problem.
mdns_esp32_nosrv.pcap.zip

I'm not able to reproduce what you're seeing on my Mac.
Compiling chip-tool with enableServerInteractions set to false, it's not able to even complete commissioning when I use minimalmdns. Taking out the chip_mdns then makes it work for me.
I'm not sure using minimalmdns on Mac is a supported use-case.
@andreilitvin @bzbarsky-apple @woody-apple would you know?

Through the use of ephemeral ports, I don't see what the issue would be with using the Matter provided minimalmdns solution over Avahi?

I'm not sure using minimalmdns on Mac is a supported use-case.

It's not particularly.  It's not tested, and last I tried it some of the broadcast stuff it tries to do by default does not work on Mac.

I don't see what the issue would be with using the Matter provided minimalmdns solution over Avahi?

What does Avahi have to do with anything?  On Mac what's used when using "platform" mdns is the built-in mdns bits in MacOS, not Avahi.

@s-mcclain - don't use minmdns on mac.


torch.jit.script PyG models

Javier did it to old IN model

If you want to assign to me, I can give it a shot :)

Sounds great!   It seems like we can essentially do it after the model definition and just in the training class?
For future reference, this is your commit from the old repo.

So essentially we might just modify this single line here

I tried that very lazily and got
Module 'InteractionNetwork' has no attribute 'inspector' (This attribute exists on the Python module, but we failed to convert Python type: 'torch_geometric.nn.conv.utils.inspector.Inspector' to a TorchScript type. Only tensors and (possibly nested) tuples of tensors, lists, or dictsare supported as inputs or outputs of traced functions, but instead got value of type Inspector.. Its type was inferred; try adding a type annotation for the attribute.):

so there might be some things to be sorted out.

I jit compiled the MLPs within the IN for now (which works out of the box), so hopefully that already gives us some boost.

This is the message if I try to just jit the whole IN:
Module 'InteractionNetwork' has no attribute 'inspector' (This attribute exists on the Python module, but we failed to convert Python type: 'torch_geometric.nn.conv.utils.inspector.Inspector' to a TorchScript type. Only tensors and (possibly nested) tuples of tensors, lists, or dictsare supported as inputs or outputs of traced functions, but instead got value of type Inspector.. Its type was inferred; try adding a type annotation for the attribute.):
  File "/scratch/gpfs/kl5675/micromamba/envs/gnn/lib/python3.10/site-packages/torch_geometric/nn/conv/message_passing.py", line 564

        self._explain = explain
        self.inspector.inspect(self.explain_message, pop_first=True)
        ~~~~~~~~~~~~~~ <--- HERE
        self._user_args = self.inspector.keys(methods).difference(
            self.special_args)

did look into this more

I think pytorch no longer works on jit.script/jit.trace. The new way seems to be jit.compile:
https://pytorch.org/tutorials/intermediate/torch_compile_tutorial.html#torch-compile-tutorial

And with lightning: https://lightning.ai/blog/training-compiled-pytorch-2.0-with-pytorch-lightning/


Setup greenkeeper

Or setup dependabot instead.

:tada: This issue has been resolved in version 2.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Dupe wireless crafting terminal

Do you know a way to solve this dupe in the wireless craft terminal?
https://imgur.io/a/LbZnTIk

Not sure what's going on there, but this is the wrong repo.


Saving docker image as tar to build folder

Closes #424

Closing this for now, as I left some additional considerations here: https://github.com/polywrap/monorepo/issues/424
In its current state, I think this would hurt the tool-chains future to put the image in the build folder. Apologies for the naive guidance, but I think there's a pretty cool future ahead if we explore this further.


Youngman-d-coder Demo Project in C

First pull request, please review!

Okay!
Where will i put my Python files when I am done!

@Youngman-d-coder For now it is not neccesary to care much about pythonsince this is just a demo project to get people to understand the workflow. for future project, you would not need to have your special directoyr

Thanks!


Make @angular-devkit/core/node/resolve independent of node_modules resolution

🚀 Feature request
Description
The custom resolution provided by @angular-devkit/core/node/resolve reimplements the node_module resolution algorithm, which doesn't work for package manages that don't use node_modules (yarn 2 with plug'n'play, npm tink if that gets revived).
Describe the solution you'd like
Replace the custom node_modules implementation with calls to either require.resolve with the paths option or to a require function created using createRequire.
These functions work regardless of the used package manager (yarn 1, yarn 2 with pnp, npm, pnpm, …)
Describe alternatives you've considered

Override the resolution, using either

setResolveHook
a patch applied to the @angular-devkit/core package via yarn 2's patch protocol or via a yarn plugin

Explicitly query the yarn PnP API, but that would require plug'n'play-specific logic in the resolution file.

That code is currently deprecated and unused by the CLI.  Based on the deprecation process, it should be eligible for removal by the next major release.

I did some digging and it turns out I had one dependency still on version 0.803, updating that to 0.900 fixed it the issues.
Thanks!


Can you provide Linux commands support in vs code terminal in windows?

VSCode Version:
OS Version:

Steps to Reproduce:

Reproduces without extensions: Yes/No

Why would they do such a thing? Why should it be editor's responsibility to simulate non-native command-line tools for you? Just use a different terminal.

Thanks for the comment. What terminal do you suggest and how do you
configure it to work with vs code?Appreciate your time!
On Dec 17, 2017 7:05 AM, "Přemysl Karbula"<EMAIL_ADDRESS>wrote:
Why would they do such a thing? Why should it be editor's responsibility to
simulate non-native command-line tools for you? Just use a different
terminal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/40369#issuecomment-352250944,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVgcJ8uc8_l3hNhqRaKDZ0c0XLf_GmsSks5tBQOTgaJpZM4RElFW
.

If you're on Windows and want your terminal be more linux-like, you can use*, for example,* Git's MINGW64 shell (if you have Git installed). To use that as terminal in vscode, just have something like this in your vscode settings:
    "terminal.integrated.shell.windows": "C:\\Program Files\\Git\\bin\\bash.exe",

If you use WSL you should be able to use "native" Linux shell inside your Windows installation of Visual Studio Code. Try looking here for more info: https://github.com/Microsoft/vscode/issues/22317

@smuuf Perfect ,  I am closing the issue
Here are some other tips i came across while researching the issue. sharing in case if there are others looking for the same answer-
"Press and hold Ctrl + ` to open terminal. Inside terminal type 'bash' without the quotations to use gitbash in terminal. Note: Make sure you have gitbash installed on your machine.
If you wish to use powershell again, just type 'powershell' without the quotations in terminal. To use Windows command line type 'cmd' in terminal.
The setting you choose will be used as your default."


[Android][Animated] Fix IllegalStateException in looped timing native animation

Motivation
This PR fixes regression introduced in #17896 with IllegalStateException being thrown in FrameBasedAnimationDriver.
After investigating it seemed that the root cause was the code responsible for looping animations that was setting next frame time by adding the frame interval to the current time. In some circumstances the next frame would run earlier than that and as a result the calculated frame index was negative.
Here is the stacktrace as reported by @axemclion https://github.com/facebook/react-native/pull/17896/files#r170007224
Caused by: java.lang.IllegalStateException: Calculated frame index should never be lower than 0
	at com.facebook.react.animated.FrameBasedAnimationDriver.runAnimationStep(FrameBasedAnimationDriver.java:60)
	at com.facebook.react.animated.NativeAnimatedNodesManager.runUpdates(NativeAnimatedNodesManager.java:444)
	at com.facebook.react.animated.NativeAnimatedModule$1.doFrameGuarded(NativeAnimatedModule.java:100)
	at com.facebook.react.uimanager.GuardedFrameCallback.doFrame(GuardedFrameCallback.java:29)

Test Plan
Run native animated tests suite. Run RNTester and scroll to the loop animation and see it working correctly
Related PRs
#17896
Release Notes
[ANDROID][BUGFIX][Animated] - Fix exception thrown by timing animation when looping

@facebook-github-bot shipit


add Frankenwallet builder tool

Including getstarted: page for which I am trying to follow the originally outlined advice (https://github.com/cardano-foundation/developer-portal/issues/742#issuecomment-1253486376) of keeping it local.  This page is a digest, and in some cases an update, of the material at the web site link... for operators to quickly scan & see if applies to their workflow.  (see latest draft of Builder Tool markdown)
Other than that it is an outgrowth of the comment here in the Air Gap aritcle since I think there could be more progress in the area of Cardano secure workflow & Air Gap environments if more people knew about this tool.  In fact the Frankenwallet instructions were the basis for writing the Air Gap page itself.

(last commit to resolve merge conflict; I think because last Showcases array entry had not been comma-terminated at current HEAD of staging)

☝ yet another merge conflict.  I think these are inevitable every time PRs are merged out of chronological order when they are all added at the same point in the code (the end of the Showcases array). 😑


RKE Template creation warning

Under the documentation for creating RKE templates:
https://rancher.com/docs/rancher/v2.x/en/admin-settings/rke-templates/creating-and-revising/#creating-a-template
Might be helpful to provide a warning/information blurb that once a cluster is "managed" by an RKE template, it cannot be disconnected and the option to uncheck "Use an existing RKE Template and revision" is greyed out and unavailable

Closing this issue because it is addressed in this commit https://github.com/rancher/docs/commit/164d548380f5a6c5a26d3fe4f1800607a6983113


Add support to uninstall an extension from servers' local gallery

Right now I miss the possibility to uninstall an extension from the local extension gallery of the Azure DevOps Server instance. This would be very helpful during extension development. Right now I have a work around with a pure REST call (DELETE {server_url}/_apis/gallery/publishers/{publisher}/extensions/{extensionId}) which does the trick but I would love to see this supported by tfx cli so I don't need to handle authentication on my own.
Thank you in advance. :)

Should be pretty straightforward. Will add this in an update today.

Fixed in 0.7.5

By the way, the command is tfx extension unpublish.

merci


Cmap decoding exception

When I am trying to get an font cmap, I get an exception
You can download the font here: https://www.dafont.com/puritan.font
Sample:
from fontTools.ttLib.ttFont import TTFont

ttFont = TTFont("PURIB10.TTF")
cmap_table = ttFont["cmap"].getcmap(3,1)

print(cmap_table.cmap)

Which raise this exception:
Traceback (most recent call last):
  File "c:\Users\admin\Desktop\from fontTools.ttLib.tables.py", line 6, in <module>
    print(cmap_table.cmap)
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\tables\_c_m_a_p.py", line 289, in __getattr__
    self.ensureDecompiled()
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\tables\_c_m_a_p.py", line 278, in ensureDecompiled
    self.decompile(None, None)  # use saved data.
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\tables\_c_m_a_p.py", line 928, in decompile
    self.cmap = _make_map(self.ttFont, charCodes, gids)
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\tables\_c_m_a_p.py", line 17, in _make_map
    glyphNames = font.getGlyphNameMany(gids)
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\ttFont.py", line 649, in getGlyphNameMany
    glyphOrder = self.getGlyphOrder()
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\ttFont.py", line 520, in getGlyphOrder
    glyphOrder = self["post"].getGlyphOrder()
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\ttFont.py", line 442, in __getitem__
    table = self._readTable(tag)
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\ttFont.py", line 459, in _readTable
    table.decompile(data, self)
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\tables\_p_o_s_t.py", line 36, in decompile
    self.decode_format_2_0(data, ttFont)
  File "C:\Users\admin\AppData\Local\Programs\Python\Python310\lib\site-packages\fontTools\ttLib\tables\_p_o_s_t.py", line 93, in decode_format_2_0
    maxIndex = max(indices)
ValueError: max() arg is an empty sequence

Why is it happening?
What can I do to avoid it.

are you a bot?

oh no, sorry, it looks like it's Github acting weird: https://www.githubstatus.com/

Yes, github has some issue and I was getting a lot of error when I tried to open the issue.
I am sorry ^^'

no worries. I believe your font has a faulty post table, it has post.numGlyphs set to 0, whereas the spec says it sould be equal to maxp.numGlyphs (258 in that particular font).
I'm nost sure what fonttools should do in this case, whether we can/should try to recover from this situation somehow.

maybe this should suffice to allow decompiling that post table, but I'm not 100% sure /cc @justvanrossum
diff --git a/Lib/fontTools/ttLib/tables/_p_o_s_t.py b/Lib/fontTools/ttLib/tables/_p_o_s_t.py
index dba637117..c04af50fd 100644
--- a/Lib/fontTools/ttLib/tables/_p_o_s_t.py
+++ b/Lib/fontTools/ttLib/tables/_p_o_s_t.py
@@ -90,7 +90,7 @@ class table__p_o_s_t(DefaultTable.DefaultTable):
         if sys.byteorder != "big":
             indices.byteswap()
         data = data[2 * numGlyphs :]
-        maxIndex = max(indices)
+        maxIndex = max(indices, default=0)
         self.extraNames = extraNames = unpackPStrings(data, maxIndex - 257)
         self.glyphOrder = glyphOrder = [""] * int(ttFont["maxp"].numGlyphs)
         for glyphID in range(numGlyphs):

@justvanrossum Have you missed anthrotype message?

It would be helpful if you could check whether the suggested patch fixes your issue.

I am not 100% sure if it does what it need.
There a difference in length between the cmap and the maxp.numGlyphs.
from fontTools.ttLib.ttFont import TTFont

ttFont = TTFont("PURIB10.TTF")
cmap_table = ttFont["cmap"].getcmap(3,1)

print(len(cmap_table.cmap)) # print 251
print(ttFont["maxp"].numGlyphs) # print 258

Have you an idea if fonttools missed some glyphs or if the maxp.numGlyphs is simply wrong?

I am not 100% sure if it does what it need.

It would be helpful if you try: apply the patch, and see if  the error goes away. If not, what is the next error?

There a difference in length between the cmap and the maxp.numGlyphs.

There usually isn't  a 1-1 relationship between the number of code points in a cmap and the number of glyphs in the font. Some glyphs may be unencoded (for example they are only used as components, or they are only accessible via a GSUB feature), while other glyphs may be encoded multiple times under different code points.

I am not 100% sure if it does what it need.

It would be helpful if you try: apply the patch, and see if the error goes away. If not, what is the next error?

There isn't any other error


WIP feature: add job to test connectivity to tcp service

Try to add a job to test connectivity to a TCP service inside a k8s cluster.
TODO:

push the tcptest image to kong repo
add more parameters for testing
discuss about other kinds of "tests", http/https/tls/udp ?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #336 (0725d4e) into main (633ccee) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 0725d4e differs from pull request most recent head 2aa69f5. Consider uploading reports for the commit 2aa69f5 to get more accurate results

@@          Coverage Diff          @@
##            main    #336   +/-   ##
=====================================
  Coverage   9.30%   9.30%
=====================================
  Files          5       5
  Lines        763     763
=====================================
  Hits          71      71
  Misses       687     687
  Partials       5       5

Help us with your feedback. Take ten seconds to tell us how you rate us.

I'm really not sure about this approach. Last we had talked I thought we were going to add a tool that deploys a temporary LoadBalancer type Service to the cluster, so that in this way we can just test using the Go library and not need a new image and all this other stuff.
What was wrong with the LoadBalancer approach?

The reason why I proposed this approach (OR, the cons for LoadBalancer approach):

LoadBalancer may not be supported by all kinds of clusters. If a cluster does not provide a LoadBalancer service, the temp lb solution could not be used.
The new temporary service is not exactly the same thing as the original one. So the result may not be 100% prove that the original service could/could not be accessed.

Cons for this approach:

We need to maintain extra code and image to deploy the jobs inside cluster.

The LoadaBalancer solution is here: #338. We could consider which solution would be accepted.

In a testing environment we control the cluster environment and can guarantee LoadBalancer functionality is available, and additionally that deals with the problem utilizing Kubernetes native APIs that can be injected into any test rather than a job that needs to be maintained as a separate tool. I am highly in favor of us taking the LoadBalancer approach instead for these reasons.


Fix broken adapters for PSX controllers in HID & USB module

With the refactor of the API, the adapters for the PSX controllers in the hid-usb module were left broken.

Mostly completed in cdf5f58aa85bae2c7773553acb8dfed62b534a23.