Add a thread in ControllerLeadershipManager to periodically fetch controller leadership info

Add a thread in ControllerLeadershipManager to periodically fetch controller leadership info as a work-around of Helix callback delay
When the thread detects inconsistency between COntrollerLeadershipManager and HelixManager, log a warning and emit metrics

This is a work-around for the first problem described in https://github.com/apache/helix/issues/377

Codecov Report

Merging #4497 into master will increase coverage by 0.14%.
The diff coverage is 51.21%.

@@             Coverage Diff              @@
##             master    #4497      +/-   ##
============================================
+ Coverage     65.43%   65.57%   +0.14%
  Complexity       20       20
============================================
  Files          1068     1068
  Lines         55468    55503      +35
  Branches       8065     8070       +5
============================================
+ Hits          36297    36398     +101
+ Misses        16531    16459      -72
- Partials       2640     2646       +6

Impacted Files
Coverage Δ
Complexity Δ

...g/apache/pinot/common/metrics/ControllerMeter.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

...org/apache/pinot/controller/ControllerStarter.java
69.37% <100%> (+0.11%)
0 <0> (ø)
:arrow_down:

.../pinot/controller/ControllerLeadershipManager.java
63.15% <48.71%> (-11.27%)
0 <0> (ø)

...egation/function/customobject/MinMaxRangePair.java
75.86% <0%> (-24.14%)
0% <0%> (ø)

...e/operator/dociditerators/BitmapDocIdIterator.java
60.71% <0%> (-3.58%)
0% <0%> (ø)

...org/apache/pinot/client/DynamicBrokerSelector.java
69.69% <0%> (-3.04%)
0% <0%> (ø)

.../main/java/org/apache/pinot/client/Connection.java
47.61% <0%> (-2.39%)
0% <0%> (ø)

...not/broker/broker/helix/ClusterChangeMediator.java
76.92% <0%> (-2.2%)
0% <0%> (ø)

...ata/manager/realtime/RealtimeTableDataManager.java
41.17% <0%> (-1.48%)
0% <0%> (ø)

...ation/function/MinMaxRangeAggregationFunction.java
73.25% <0%> (-1.17%)
0% <0%> (ø)

... and 15 more

Continue to review full report at Codecov.

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


Agent crash on missing mask

Howdy, got a bug where an agent will crash if mask attack is specified but no mask is given:
2024/04/30 17:54:04 Received: DeleteFileRequest
2024/05/01 15:50:53 Received: JobStart
2024/05/01 15:50:53 unrecoverable handler error: error when handling message: using mask attack (3), but no mask was given

The error is now non-fatal as of (some time ago). It let's the user create the attack, but the attack instantly exits and gives the user an error.
Ideally this should be validated at submission time, rather then starting the attack. But, that can come later.


getContentChildren API docs should be clearer

API docs say, "CSS selector to choose the desired <content>."
This is a little confusing because each content element may contain a selector in its select attribute, but we don't match that selector, we need to specify a CSS selector that selects the content element itself.
Maybe say:
CSS selector that matches the desired <content> element. For example, the element:

    <content id="content1" select=".stuff"></content>

Matches the selectors `#content1`  or `content[select=".stuff"]`.

yes to this :+1:

:+1:

Still an issue in the legacy docs: https://www.polymer-project.org/2.0/docs/api/mixins/Polymer.LegacyElementMixin#method-getContentChildren


Add hotspot to scene

I saw that there is the function addHotSpot(). But is there a possibility to add the hotspot to a scene?
Something like viewer.addHotSpot("sceneId", options")

Yes, there is a possibility to add a hotspot to another scene.
It should work: https://github.com/Aykelith/pannellum/tree/hotspot_to_another_scene
Use the function: hotSpotToScene(sceneId, hs).

I removed the hotSpots from the config.
"default": {
"author": "Matthew Petroff",
"sceneFadeDuration": 1000,
"showZoomCtrl": false,
"showFullscreenCtrl": false,
"autoLoad": true,
"hotSpotDebug": true
},
"scenes": {},
//"hotSpots": [] // <-- this
Now it adds the hotSpot to the current scene.

I extended addHotSpot in b3123271124c5338554a408cb61ca7a52b153107 to have an optional sceneId parameter so it can be used to add hot spots to either the current scene or any other scene.


More than Two mod keys in a keybind fail to work.

Hyprland Version
❯ hyprctl version
Hyprland, built from branch HEAD at commit 03ebbe18ed8517ee22591eac82cd54322f42cb7d  (props: bump ver to 0.34.0).
Date: Mon Jan 1 12:03:15 2024
Tag: v0.34.0
flags: (if any)
Bug or Regression?
Bug
Description
I cannot create modifiers that contain more than two and have them work.  I am trying to create a hyper key which ought to be SUPER + CONTROL + ALT + SHIFT and a  meh key which ought to be CONTROL + ALT + SHIFT.    I can  bind with any combination of two but past that it does not work.
How to reproduce
Try to define a hyper key as  I specified in the description then attempt to use it.   It will fail to work.    Otherwise looking good.   I am able to define these keys in I3 with no problem.
Crash reports, logs, images, videos
No response

bind = CONTROL_SUPER_ALT_SHIFT, Y, exec, foot works for me

I wish it did work but it does not, I tried it in a
bind = CONTROL_ALT_SHIFT, r, exec, pkill rofi || rofi -show drun -modi
drun,filebrowser,run,window
(for meh key)
It did not work....CONTROL_SHIFT works just fine...and CONTROL_ALT worked
just fine.    Once I do CONTROL_ALT_SHIFT it does not work for me.   Do you
know if there is any kind of OS setting or keyboard setting that may be
causing me issues?    I am not using anykind of keyboard software just
flashing my ERGODOX_EZ
On Mon, Jan 15, 2024 at 12:41 PM MightyPlaza @.***>
wrote:

bind = CONTROL_SUPER_ALT_SHIFT, Y, exec, foot works for me
—
Reply to this email directly, view it on GitHub
https://github.com/hyprwm/Hyprland/issues/4450#issuecomment-1892633971,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA657BMJCWRHU2XQPW2P6QLYOVZ5JAVCNFSM6AAAAABB3VXVKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJSGYZTGOJXGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

what's the output of wev when pressing those keys?

i can't seem to find the R press in there
was it cut out?

Oh I did not press that on this example I just pressed the hyper key I have
on my ergodox, but I can go back and do it with the r added in to see if it
is picking it up.
On Mon, Jan 15, 2024 at 3:15 PM MightyPlaza @.***>
wrote:

i can't seem to find the R press in there
was it cut out?
—
Reply to this email directly, view it on GitHub
https://github.com/hyprwm/Hyprland/issues/4450#issuecomment-1892771603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA657BI5MQ7IEHZJX3DBPP3YOWL6JAVCNFSM6AAAAABB3VXVKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJSG43TCNRQGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

$mainMod = SUPER
$hyper = CONTROL_SHIFT_ALT_SUPER
$meh = CONTROL_SHIFT_ALT
$files = thunar
$term = xfce4-terminal
$scriptsDir = $HOME/.config/hypr/scripts
$UserScripts = $HOME/.config/hypr/UserScripts
rofi App launcher
bindr = $mainMod, $mainMod_L, exec, pkill rofi || rofi -show drun -modi
drun,filebrowser,run,window
bind = $mainMod, d, exec, pkill rofi || rofi -show drun -modi
drun,filebrowser,run,window
bind = $hyper, r, exec, pkill rofi || rofi -show drun -modi
drun,filebrowser,run,window
14:     wl_keyboard] key: serial: 582; time: 1828765; key: 37; state: 1
(pressed)
sym: Control_L    (65507), utf8: ''
[14:     wl_keyboard] modifiers: serial: 0; group: 16
depressed: 00000004: Control
latched: 00000000
locked: 00000010: Mod2
[14:     wl_keyboard] key: serial: 584; time: 1828765; key: 50; state: 1
(pressed)
sym: Shift_L      (65505), utf8: ''
[14:     wl_keyboard] modifiers: serial: 0; group: 16
depressed: 00000005: Shift Control
latched: 00000000
locked: 00000010: Mod2
[14:     wl_keyboard] key: serial: 586; time: 1828765; key: 64; state: 1
(pressed)
sym: ISO_Next_Group (65032), utf8: ''
[14:     wl_keyboard] key: serial: 587; time: 1828765; key: 133; state: 1
(pressed)
sym: Super_L      (65515), utf8: ''
[14:     wl_keyboard] modifiers: serial: 0; group: 16
depressed: 00000045: Shift Control Mod4
latched: 00000000
locked: 00000010: Mod2
[14:     wl_keyboard] key: serial: 589; time: 1829274; key: 27; state: 1
(pressed)
sym: R            (82), utf8: ''
[14:     wl_keyboard] key: serial: 590; time: 1829573; key: 27; state: 0
(released)
sym: R            (82), utf8: ''
[14:     wl_keyboard] key: serial: 591; time: 1829783; key: 37; state: 0
(released)
sym: Control_L    (65507), utf8: ''
[14:     wl_keyboard] modifiers: serial: 0; group: 16
depressed: 00000041: Shift Mod4
latched: 00000000
locked: 00000010: Mod2
[14:     wl_keyboard] key: serial: 593; time: 1829783; key: 50; state: 0
(released)
sym: Shift_L      (65505), utf8: ''
[14:     wl_keyboard] modifiers: serial: 0; group: 16
depressed: 00000040: Mod4
latched: 00000000
locked: 00000010: Mod2
[14:     wl_keyboard] key: serial: 595; time: 1829783; key: 64; state: 0
(released)
sym: Alt_L        (65513), utf8: ''
[14:     wl_keyboard] key: serial: 596; time: 1829783; key: 133; state: 0
(released)
sym: Super_L      (65515), utf8: ''
[14:     wl_keyboard] modifiers: serial: 0; group: 16
depressed: 00000000
latched: 00000000
locked: 00000010: Mod2
On Mon, Jan 15, 2024 at 3:19 PM Christopher Fair <
@.***> wrote:

Oh I did not press that on this example I just pressed the hyper key I
have on my ergodox, but I can go back and do it with the r added in to see
if it is picking it up.
On Mon, Jan 15, 2024 at 3:15 PM MightyPlaza @.***>
wrote:

i can't seem to find the R press in there
was it cut out?
—
Reply to this email directly, view it on GitHub
https://github.com/hyprwm/Hyprland/issues/4450#issuecomment-1892771603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA657BI5MQ7IEHZJX3DBPP3YOWL6JAVCNFSM6AAAAABB3VXVKOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJSG43TCNRQGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

any progress on this? I want to bind hyper to some fun stuff too but it is not working for me

I am having the same issue.

Actually it started working for me... I have no idea what I changed. I commented out some bind lines, it started working, I uncommented them, and things kept working.
It might be a shadowing/reloading issue? Or could be a misconfiguration issue on my end


Close on ESC

Is there an option to close on Escape key press?
Thank you

I'm doing like this and it's working.
$(document).keyup(function(e) {
	if (e.keyCode == 27) {
		iziToast.hide({}, '.iziToast');
	}
});

If is there a better way please let me know. Thanks

@pablo-pacheco. There is no option to close the Toast with the ESC key.
The idea of iziToast is to be something minimalistic and fast, and to allow you to open several at the same time. So I do not think this implementation would be feasible. But I will analyze it anyway.
Thank you!


Collision in LALR grammars

I may very well be a bit rusty on LALR grammars, but I can't find what I'm doing wrong with that one:
_expr          : or_test

?or_test       : and_test
               | or_test  "or"  and_test    -> binary_expr
?and_test      : _primary
               | and_test "and" _primary    -> binary_expr

_primary       : call_expr
               | ident
               | "(" _expr ")"

call_expr      : _expr "(" _expr ")"

ident          : NAME
NAME           : /[^\W\d][\w]*/
NUMBER         : /(0|([1-9][0-9]*))(\.[0-9]+)?([Ee][+-]?[0-9]+)?/
STRING         : /'[^']*'/

%ignore /[\t \f]+/

(This is a simplified version of a my complete grammar, which can be seen here: light.g).
I initialize my parser like that:
parser = Lark(f, parser='lalr', start='_expr')

This grammar gets me a lark.common.GrammarError: Collision .... The remainder of the error message doesn't seem to be deterministic, as I always get a different one. It seems like I can't handle recursion of the _expr rule with the call_expr. Looks pretty much like a left-recursion issue, which is quite surprising for a LALR parser.
Everything works fine with the Earley parser.

Hi, you are right!  This grammar can and should be accepted by a LALR parser.
But, it's not a left-recursion issue. The reason that it doesn't work for lark, is that Lark is currently missing a reduce-reduce resolution feature, which I never really needed so far. For example, I managed to write a complete grammar for Python without running into such a collision.
However, reduce-reduce resolution is on my TODO list, and it shouldn't be difficult to add. So if Earley isn't performant enough for your needs, let me know and I'll move it up the list.

Hey, thanks for the quick answer!
Earley seems to be doing the job so far. I'll have to work on code generation before parsing can be an issue, so I can move to the LALR later.

Great. Let me know if it ever becomes an issue.

Upon further inspection, this reduce-reduce collision is actually not resolvable within LALR(1).
PLY can handle some simplistic cases of reduce-reduce collisions, I presume using mechanisms specifically targeting those cases.
Alternatively, It might be possible to solve this collision, along with a wider range of collisions, using LALR(2).
However, both these non-general solutions take some non-trivial work, so I'm reluctant to implement them, unless there's a real need for them.
I'm angling towards a much wider solution, which is a hybrid Earley+LALR engine, that should give near-LALR performance even for non-LALR grammars, and should have no problem solving reduce-reduce collisions such as this. It will take a lot of work, but it should solve the problem in the general case, so that's where I prefer to strive.
I'm closing this issue. Please feel free to re-open it (or a new one) if you feel that it's necessary.


E2 doesn't keep values set with dupefinished() after refreshing it.

I usually set some values with dupefinished(). Everytime I reset the E2 when I changed something in it, all those settings are reset and those values are set to 0, instead of being kept like before.
I guess a quick fix would be to use if(first()|dupefinished()) to have values both when duping and when resetting the E2.
Before, the values set with dupefinished() would be unchangeable unless you redupe the e2, but remained what you set before, not going to be reset to 0 like it happens now.

What was happening before was a bug. The E2's vars should reset when the E2 resets.

Ah, so the solution to it is adding first() as I thought. Thanks for explanation.


[Bug]fixed traces bug for missing MDS id

Description
added parameter in flyout for mds
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@sumukhswamy Looks like app analytics has some import issues for header controls. Can you please take a look


Preview of online images in the form through HTMLWidget

In MM mobile 2.4.1, we have support for HTMLWidget. You can add a preview of the image in the form:

Feel free to improve and use the example project here:
https://app.merginmaps.com/projects/lutraconsulting/image-html-view/

This is good to link to mergin-media-sync - if user transfers image to mini with this widget he can see it in the form.


fixes #46839, ensure library_classes is cleared and free funcs are ca…

…lled
Co-authored-by: toasteater<EMAIL_ADDRESS>Co-authored-by: Jan Haller<EMAIL_ADDRESS>
Bugsquad edit: Fixes #46839

Thanks!

Cherry-picked for 3.3.


Command not found issue after last update

I'm getting these kind of logs in my console when I reload the path probably just after last update.
 Any help will be appreciated

You have to change the End-Of-Line characters of your zshrc file to \n (Line Feed, Unix style). You have it in macOS style (\r or Carriage Return).


Consider snap/flatpak packaging for Gitea

Gitea version (or commit ref): N/A
Git version: N/A
Operating system: Any GNU/Linux
Database (use [x]):

[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Not relevant

Log gist: N/A

User story: I am a regular user with no/minimal configuration needs. I just want to install Gitea and keep it up-to-date.
Proposed solution: Release a flatpak or snap package. Releasing in this format requires fewer procedural barriers and allows users to keep up-to-date even if their distro doesn't. (Although inclusion in, for example, Debian is still a worthy goal.) Both formats are well-supported across all distros.
There is an example of a Gogs snap package here: https://github.com/tbraeutigam/gogs-snap

Please see above -- a pull request for snap-packing gitea :+1:

resolved by #2568


More informative error message when python script can't be imported

At present if there is a problem when importing python script the exception is raised that is not very informative and looks like this:
Traceback (most recent call last):
  File "main.py", line 209, in <module>
    launcher_arguments=currDiag.get_launcher_arguments())
  File "./interface_scripts/projects.py", line 3021, in run_executable
    exit_on_warning)
  File "./interface_scripts/launchers.py", line 289, in execute
    self._execute_script(python_executable, project_info, verbosity, exit_on_warning)
  File "./interface_scripts/launchers.py", line 314, in _execute_script
    raise ValueError('The script %s can not be imported!' % python_executable)
ValueError: The script ./diag_scripts/sst_ESACCI.py can not be imported!

So there is no particular reason on why the script can't be imported and hence it's quite hard to debug. In my case, for example, the python module were missing, but from the error message there were no way to understand that. I suggest changing this part of launchers.py ether by adding at least
 print("Error while importing python script:", sys.exc_info())

that in my case would lead to:
('Error while importing python script:', (<type 'exceptions.ImportError'>, ImportError('No module named geoval.core.data',), <traceback object at 0x7f42ea5e29e0>))

or if you don't mind additional import use traceback module:
import traceback
...
try:
    exec cmd
except:
     print(cmd)
     print(traceback.format_exc())
     raise ValueError('The script %s can not be imported!' % python_executable)

that lead to:
import sst_ESACCI.py
Traceback (most recent call last):
  File "test.py", line 19, in <module>
    exec cmd
  File "<string>", line 1, in <module>
  File "./diag_scripts/sst_ESACCI.py", line 42, in <module>
    from sst_diagnostic import SeaSurfaceTemperatureDiagnostic
  File "./diag_scripts/aux/LMU_ESACCI-diagnostics/sst_diagnostic.py", line 1, in <module>
    from diagnostic import *
  File "./diag_scripts/aux/LMU_ESACCI-diagnostics/diagnostic.py", line 17, in <module>
    from geoval.core.data import GeoData
ImportError: No module named geoval.core.data

Traceback (most recent call last):
  File "test.py", line 23, in <module>
    raise ValueError('The script %s can not be imported!' % python_executable)
ValueError: The script sst_ESACCI.py can not be imported!

that is way easier to debug. I can do PR with this fix.

I fully support this. Please send PR.

Thanks, @bulli92 , did a PR, please have a look.

@koldunovn did you get reply or solve this problem?


E.Coli Under-represented K-mers

In Part 2, for Question 5, my Barplot for E.Coli Under-represented K-mers seems to be missing some of the K-mer names on my x-axis.

Have now fixed this after receiving an email response from Mark. I used the cex.names function.


Missing search record

A search for Ann Alcock, born 1841 +/- 2 (FC1) or 1838-1841 (FC) A, search anywhere for census county and birth county found one born notts, census notts, thurgaton 1841 is found (age 3 birth year in FreeCEN1 but not found by a search in FC2.
James Alcock, same parameters finds him aged 1 in FreeCEN2, but 1 month in FreeCEN1 (only result for this search).

I was able to find these in Freecen2 - see attached screenshots

Ian Stimson wrote that
Freecen 2 is not finding what I know is in the system because I have the Freecen1 full and complete result printed in front of me.
In Freecen1 I entered Driver, John m, 1861 census, census county WRY. Nothing more. It found one John M in Pudsey and one in Silsden.
In Freecen2 I made the same entry and it did not find the Silsden entry.
Driver, John M, was born in 1856 in Silsden and baptised Jan 1857,
I have investigated and FC2 gives me
Detail	Individual
Birth County
Birth Place
Birth
Census
Census County
Census Place
View 1
John M DRIVER	Yorkshire	Pudsey	1802	1861	Yorkshire, West Riding	Pudsey
View 2
John M DRIVER	Yorkshire	Pudsey	1802	1871	Yorkshire, West Riding	Pudsey
View 3
John M DRIVER	Yorkshire	Silsden	1857	1891	Yorkshire, West Riding	Kildwick
I have found the Pudsey result in 1861 and 1871. I have found the Silsden result in 1891, but not 1861.
I have the FC1 result in Silsden aged 4.
I have now searched FC2 with only John. The record comes up in the list. The problem is that he is recorded as John Morris and so John M was not found.
The underlying reason is that FC2 has done an exact search for John M rather than a broader search. Is this intended?
Geoff

Potentail bug here: John Morris should be found in a John M search

The record can be found by using the wildcard functionality - see below:

According to our search stories on hand, the wildcard functionality is still to be developed.
Maybe we need to add a note to the search screen that the wildcard functionality is available.
Nevertheless a search of John M should have found the record without the wildcard. It is a bread and butter search for researchers.
Geoff
From: Anne Vandervord @.>
Sent: Thursday, June 8, 2023 1:12 AM
To: FreeUKGen/FreeCENMigration @.>
Cc: Geoff J @.>; State change @.>
Subject: Re: [FreeUKGen/FreeCENMigration] Missing search record (Issue #1318)
The record can be found by using the wildcard functionality - see below https://camo.githubusercontent.com/670d691a3eb694b17c4ce77e47a26ca9eb20e1e0007cc199d8a976cfcba0626f/68747470733a2f2f696d616765732e7a656e68756275736572636f6e74656e742e636f6d2f3630303961656363643630343239636237303038653564332f37393834646630392d616434312d343833612d626439642d353038616137626236363832 :
—
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1318#issuecomment-1581029103 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFOAAULULWUHIXRDSE3XKCK4BANCNFSM5HJP7AQA .
You are receiving this because you modified the open/close state.  https://github.com/notifications/beacon/AKCPIFKBMM2KSQI5XFJ4LHTXKCK4BA5CNFSM5HJP7AQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOLY6JN3Y.gif Message ID: @.*** @.***> >

I believe this issue affects FreeReg too. From what I can see it is just not built into the Search capabilities to incorporate the reduction of middle names(s) to initial letters.

This is a bread and butter problem. If a researcher enters John M they should find John Morris. Similarly if a researcher enters John Morris then they should find John M.
I have flagged this as a bug.
How difficult is it to fix please?
The problem is probably also with FreeREG because we started FreeCEN2 by importing their code and amending it. Hence the similarity.
Geoff

@geoffj-FUG I am not totally familiar with the code for searches but I believe this will be a pretty fundamental change to it.
I doubt there can be a quick fix but I might be wrong.
@Vino-S what is your assessment?

Moving this story to pending, awaiting systemwide resolution (please see Systemwide #287 https://app.zenhub.com/workspaces/system-wide-code-changes-5ccc857f10a32d7d637c8f48/board )

Placing on ice as this would be superseded by autosuggest


iPhone 14 Focus Distance

With the change in minimal focal distance on the standard camera with iPhone 14, I've found it harder to scan smaller barcodes. I have read articles about trying to force the macro camera / mode. Have others noticed the same issue or found ways around it?

This happens on iPhone 13 Pro aswell

I have also experienced this issue. There is usually an autofocus enabled property in AVFoundation but Im not sure how to access it and edit it and if that is even possible. @twostraws Any help with this one please?

I'm testing another barcode scanner and here is what I did to resolve the issue. I had to limit it to iPhone because it was causing issues on iPad and macOS so be careful where you use .builtInUltraWideCamera but this will help with the focus distance.
let deviceDiscoverySession = AVCaptureDevice.DiscoverySession(deviceTypes: [.builtInUltraWideCamera, .builtInWideAngleCamera], mediaType: AVMediaType.video, position: cameraPosition)

Maybe conditionally select the camera when instantiating can solve the problem?
Feel free to try to make a PR if you find something

I have opened a PR that uses the Ultra Wide Camera if available for the current device as a default parameter of the CodeScanner. It's a combination of what was proposed in previous comments here.

I believe this issue was resolved with the patches above but in the meantime I've found more info that the following devices might be the more up-to-date solutions.
AVCaptureDevice.DiscoverySession(deviceTypes: [.builtInTripleCamera, .builtInDualWideCamera, .builtInUltraWideCamera, .builtInWideAngleCamera, .builtInTrueDepthCamera], mediaType: AVMediaType.video, position: cameraPosition)


ImportError: No module named 'bs4'

I'm probably missing something obvious, but I've tried this on two systems so far (Workstation and Fusion), and received the same error both times. Am I missing a dependency? Using the wrong Python version?
root@kali:~/kali-tools# ./kali.py
Traceback (most recent call last):
File "./kali.py", line 9, in
from bs4 import BeautifulSoup, SoupStrainer
ImportError: No module named 'bs4'
root@kali:~/kali-tools# pip install bs4
Requirement already satisfied: bs4 in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: beautifulsoup4 in /usr/lib/python2.7/dist-packages (from bs4)

Hmm... Indeed. I think we're touching the "black magic" part of python here.
As you've correctly seen, "bs4" is for "Beautiful Soup", and I did install it exactly like you did. Two options in my opinion:

pip uninstall bs4, then install it system wide (something like sudo apt-get install python3-beautifulsoup)
remove the dependency. It is only used to leech the website, but not in the normal operations. So you can comment this line, and it should work exactly the same

Got it!
There were no results for "python3-beautifulsoup", but several others if you search the cache. Not sure what distro you're on?
root@kali:~/kali-tools# apt-cache search beautifulsoup
pypy-bs4 - error-tolerant HTML parser for PyPy
python-beautifulsoup - error-tolerant HTML parser for Python
python-bs4 - error-tolerant HTML parser for Python
python-bs4-doc - error-tolerant HTML parser for Python - documentation
python3-bs4 - error-tolerant HTML parser for Python 3
python-pynliner - CSS-to-inline-styles conversion tool for HTML - Python 2.x
python3-pynliner - CSS-to-inline-styles conversion tool for HTML - Python 3.x

"python-beautifulsoup" was already installed and up to date, so my next guess was "apt install python3-bs4". This got everything working perfect, no need to pip uninstall or remove the dependency. Thanks for the system wide tip, that got me right to it.

Sure thing. I'm also struggling with choosing between pip/apt for python packages, I try to got for system-wide whenever possible (hoping that this resolves dependencies), but the whole topic is still hacky to me.
Good that it works!


"pause after this song" does not work.

OS
Arch Linux (Manjaro 17.0.1 KDE Plasma 5.35.0)
Issue Descriptions:
When you have a queue of songs, the pause after this song option does nothing. At the end of the song, the next one plays (if there is another song in the queue.)
Steps to Reproduce:

queue songs, by playing an album
select the currently playing song, and in the burger menu press the "pause after this song" option
at the end of the song, the next one will start playing automatically

Used to work for me, but this also just started happening to me (Windows 10).

When will this update be available? I'm having this issue in 4.3.0 which is currently the latest from the site.

When will this update be available

Planning on an update this week, it's a complicated process with lots of manual steps though so no promises.

I started having this issue several weeks ago. Just installed the 4.4.0 update but it didn't fix any of my problems. Even though it was glitchy (presumably because of GPM sticking the front of the 'next' song on the end of the current song, leaving a second or three of interrupted music from that next track), I nonetheless used it all the time. TBH, I consider pause and the remote two of the best features.

@KS2Problema, you bring up another good point - how the feature, when it worked, played the beginning of the next song before pausing. I don't think it is the fault of GPM, however, but rather a separate bug with GPMDP. Case in point, if a user plays a single song from an album, the beginning of the next track does not play. I suppose we must wait until the bugfix for #2604 is released, then see if the glitch still affects the "Pause after this song" feature, at which point, if it does, we can open a new issue.

I just downloaded and tested this issue with 4.4.0. #2604 is not resolved.

The bit of the next song glued to the currently ending song is, indeed, a problem in Google's Chrome-browser based application, as well. It started when they introduced gapless play. (Which really is a nice feature; tradeoffs, eh?) In my experience, on my  system, the next-song-glitch  seems to occur if the next song is changed in the last half-minute to minute.

Windows 10, v4.4.1: does not work as well

Ubuntu 17.10 here. Player version 4.4.1. Issue is still present.

Windows 10, v4.5.0. Been seeing this issue since I first installed GPMDP (v4.4.0), still occurring.

I just discovered GPMDP and like it a lot. I was excited to see this feature because I would often wait until a song finished and pause before stepping away. Unfortunately, it doesn't work, as described in the issue description. I'm on Linux Mint 18.3.

This feature is still non-functional on MacOS 10.13.4 using GPMDP 4.5.0


WeblinkUtilities.InvokeResponseCallback invokes all callbacks

No filtering is performed on the attribute's target value to skip invoking on invalid callbacks.

This is resolved in v1.4.


Can't call RetroEnvironment::set_raw

Commit 90b72a8 ("Factor out a sys crate")  changed the first argument for RetroEnvironment::set_raw from &self to &mut self. However, RetroCore still receives non-mut references to RetroEnvironment in all of its functions. As a result, it's not possible to call set_raw any more.

I should really test these changes alongside my own emulator 😉. Do you have a use case for set_raw at the moment, or is this just some API roughness that you noticed?

I'm currently using set_raw for RETRO_ENVIRONMENT_GET_LOG_INTERFACE and RETRO_ENVIRONMENT_SET_HW_RENDER. I'd like to add proper support for both those features in libretro-rs, but until then I need to use set_raw.
I've already fixed this locally but I think I'll wait for my current PR to be merged before I rebase my branch and open a new PR for this.

Closed via #8


[Storage] [DataMovement] [Samples] Randomize Container Names

Randomize container name in DataMovement Sample to allow delete container delay between test runs.

API change check
API changes are not detected in this pull request.


cli: deprecate cockroach quit

PR: https://github.com/cockroachdb/cockroach/pull/49668
From release notes:

cockroach quit is now deprecated. Use the subcommands for cockroach node instead, and use termination signals to quit the cockroach process. [#49668][#49668] {% comment %}doc{% endcomment %}

This was addressed with #7304.


Returning Response From Before Pipeline

Prerequisites

[x] I have written a descriptive issue title
[x] I have verified that I am running the latest version of Nancy
[x] I have verified if the problem exist in both DEBUG and RELEASE mode
[x] I have searched open and closed issues to ensure it has not already been reported

Description
On Nancy v1 I used to have a little helper for modules that required Validation. Basically:
public abstract class ValidatedModule<T> : NancyModule, IValidateInput<T>
    {
        public T Input { get; set; }

        protected ValidatedModule()
        {
            this.ValidateInput();
        }
    }

    public interface IValidateInput<T> : INancyModule
    {
        T Input { get; set; }
    }

    public static class ValidateInputExtensions
    {
        public static void ValidateInput<T>(this IValidateInput<T> module)
        {
            module.Before.AddItemToStartOfPipeline(ctx =>
            {
                module.Input = module.BindAndValidate<T>();
                if (!module.ModelValidationResult.IsValid)
                {
                    return new ErrorResponse(module.ModelValidationResult.ToError(), ctx.Environment);
                }

                return null;
            });
        }
    }

public class ErrorResponse : JsonResponse<Error>
    {
        public ErrorResponse(Error model, INancyEnvironment environment) : base(model, new DefaultJsonSerializer(environment), environment)
        {
            StatusCode = model.StatusCode;
        }
    }

public static Error ToError(this ModelValidationResult modelValidationResult)
        {
            var errors =
                   Enumerable.ToArray<ValidationErrors>((from error in modelValidationResult.Errors
                        select new ValidationErrors { Field = error.Key, Errors = Enumerable.ToArray<string>(error.Value.Select(x => x.ErrorMessage)) }));

            return new Error()
            {
                Code = ErrorCodeValidation,
                Message = String.Join(" ", errors.SelectMany(x => x.Errors)),
                ValidationErrors = errors
            };
        }

On Nancy v1, ErrorResponse used to inherit from JsonResponse and I would just create it with a new serializer.
On Nancy v2 I switched to JsonResponse<Error>, but now I simply don't get any response at all when model validation fails. I think this has something to do with addition of the INancyEnvironment. I searched the issues but couldn't find much. Is this the correct way? Is there any way I can just return a model from a Before Hook and let content negotiation do it's way?
Steps to Reproduce
https://github.com/felipeleusin/NancyFX.BeforeResponse
Try to make a post request to /test without a name parameter and it will fail silently.
System Configuration
Windows 10, ASP.Net 4.6,

Nancy version: 2.0.0-alpha
Nancy host

[ ] ASP.NET
[X] OWIN
[ ] Self-Hosted
[ ] Other:

Other Nancy packages and versions: Nancy.Validation.FluentValidation, Nancy.Owin
Environment (Operating system, version and so on): Windows 10
.NET Framework version: 4.6
Additional information:

@felipeleusin did you resolve this? I was looking at this now and you provide a lot of code that used to work, but zero lines of code that does not work - making it hard to reproduce locally. Returning a Response from a Before-hook works in 2.x but the syntax is still a bit cumbersome (it'll be fixed before an RTM release)

Oh just seen your linked code 😄

I just added this to one of my modules
this.Before.AddItemToStartOfPipeline(ctx =>
{
    return new ErrorResponse(new RatPack { FirstName = "Nancy " }, ctx.Environment);
});

So it has nothing to do with  ctx.Environment as that is properly populated.

Is there any way I can just return a model from a Before Hook and let content negotiation do it's way?

Not yet. It is something I want to look into for 2.x RTM


ProteinPilot has datatypes defined

Datatypes are defined in it's own repository. We should remove them from the ProteinPilot repository.
Moreover, I think they can replaced with something already available in Galaxy. So no need to introduce yet another datatype.
The group datatype seems to be special, and there is a special wrapper to convert group to xml. If we include group2xml.exe XML $input $output into the ProteinPilot wrapper directly we can get rid of the datatype and one tool.
A TPP expert is needed here :)

ProteinPilot is not a TPP program - it is a really expensive commercial Windows only tool. Its users do wan the group file so I believe there needs to be a datatype.
I am uncertain as to whether we should automatically generate the XML files in tool - but people may have their own group files they wish to upload and convert so that tool likely should still exist.

Upps, sorry typo. s/TPP/PP/. Thanks for you input.
I think this tool needs some work and I will try hard to avoid working on none Open Source programs :)


Python background analyzer (PBA)

Describe your question
Can you optimize PBA? It took 2/3 of my total 12GB RAM when i was making some django app.

Thanks for the feedback.
We are working on a new language server aka analyzer that will provide better performance.  We are tracking its integration into VS at https://github.com/microsoft/PTVS/issues/5210. Thanks!

Is there any suggested work around for this for the time being?
I have a solution with both python and C#, should I consider splitting my solution for now when only working on C# code?

That's one way to do it. You could check your Python environment for packages that you don't need and uninstall them (or create a virtual env with the minimal packages, if you haven't already done that).  In theory it shouldn't matter as code not referenced should be ignored, but you never know, that might help. Also if you have large dictionaries / lists (as literals) in your code or in your libraries, that might contribute to it.


CI failures due to kine NULL prev_revision when ranging on /bootstrap

Seems to be flakey - doesn't occur on every run. May be triggered by https://github.com/k3s-io/k3s/pull/3422 but the underlying bug is in somewhere in Kine. There's another issue in that code, in that the kine client Delete operation doesn't use a transaction, which will cause it to fail because the kine server only supports transactional deletes - but that's not what's causing this.
Ref:

https://drone-publish.k3s.io/k3s-io/k3s/376/1/3
https://drone-pr.k3s.io/k3s-io/k3s/1267/1/3

time="2021-06-22T20:56:21.620608398Z" level=error msg="error while range on /bootstrap /bootstrap: sql: Scan error on column index 0, name \"prev_revision\": converting NULL to int64 is unsupported"
{"level":"warn","ts":"2021-06-22T20:56:21.620Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"endpoint://client-4bb28906-4404-4bba-a331-5f3076e58016/kine.sock","attempt":0,"error":"rpc error: code = Unknown desc = sql: Scan error on column index 0, name \"prev_revision\": converting NULL to int64 is unsupported"}
time="2021-06-22T20:56:21.621013908Z" level=fatal msg="starting kubernetes: preparing server: rpc error: code = Unknown desc = sql: Scan error on column index 0, name \"prev_revision\": converting NULL to int64 is unsupported"

Closing as this is mostly CI and bootstrap issues have been validated already


Auto indexing

I am confused on auto indexing. I cannot get it to work.
My model.
use Iverberk\Larasearch\Traits\SearchableTrait;

class Membership extends \Eloquent {

	// enable eleasticsearch
	use SearchableTrait;

This does not get auto indexed when new Membership record is posted to database. I have also seen this in docs. CallableTrait.
I have tried this on my model.
use Iverberk\Larasearch\Traits\SearchableTrait;
use Iverberk\Larasearch\Traits\CallableTrait;

class Membership extends \Eloquent {

	// enable eleasticsearch
	use SearchableTrait;
        use CallableTrait;

And get this error.
Trait method bootCallableTrait has not been applied, because there are collisions with other trait methods on Membership

How do i get Membership auto indexed when new records are posted?

The SearchableTrait already includes the CallableTrait so it doesn't need to be included again. That causes the error.
Did you include the ServiceProvider and run the paths command?

Yes I have included the ServiceProvider like so:
'providers' => array(

..................
'Iverberk\Larasearch\LarasearchServiceProvider',

	),

I have also wrtten the path.json file to /app/config/packages/iverberk/larasearch/paths.json
{
    "paths": {
        "Membership": [
            "mailingAddress",
            "primaryMember"
        ]
    },
    "reversedPaths": {
        "Membership": [
            ""
        ],
        "Address": [
            "membership"
        ],
        "Member": [
            "membership"
        ]
    }
}

Did initial index of Membership with --relations flag. The initial search works great. But when a new membership gets posted to database and I try to search for new membership it does not find.
So I do manual reindex and then do search and it finds it. For some reason it is not auto indexing???

no help here??? Is there a function I can manually call on update or create?

do you have to use eloquent for the create methods or can you use
DB::table('my_table')->inset($data)

Yes, you have to use eloquent.

i had an issue with auto indexing as well before i found that queue has an error try to see if ur queue has an error with this command
php artisan queue:listen

try to see if errors are showing

Yes i am using eloquent with:
$membership = new Membership;

$membership->save();

I also just have the stock /app/config/queue.php file. I have not touched it. Am I supposed to do something with this file?
I tried:
php artisan queue:listen

It does nothing except wait....I tried to post a new membership and it did nothing. Terminal is just in wait state.
Thank you very much for the help and giving this your attention.

If you haven't changed anything in config/queue.php then it should be executing queue jobs asynchronously meaning at page load. So whenever something is done to change a Model it should be  flagged to the queue system to be re-indexed, and should be done on the page load.
If this is not occurring I would look at your laravel.log after changing something and see if it's throwing any errors causing the ReindexJob to stop firing.

pfeiferchristopher
thanks for the advice. I have properly written the paths.json file and it has been saved to:
/app/config/packages/iverberk/larasearch/paths.json

I have also checked the logs and no errors there. I was wondering is there a way to call something like the below manually?
$membership = new Membership;

$membership->save();

$membership->reIndex();

Just running out of options and trying to maybe force it somehow.
Thanks again for everybody's help!

Help anybody???

Fiannly found out that jobs were being sent to queue but not being processed. I am on an ubuntu server and added this to to /etc/init/myqueue.conf
description "work queue"
start on filesystem
stop on runlevel [!2345]
respawn
respawn limit 5 2
script
exec /usr/bin/php /path/to/laravel/artisan queue:listen
end script

Then start the queue: "start myqueue". That's it, it will be automatically monitored and restarted in case of crash. No need for external daemons.


Fix shape inference for unsqueeze when axes are nagative

resolves #794
Signed-off-by: Tung D. Le<EMAIL_ADDRESS>

Jenkins Linux ppc64le Build #720 [push] Fix shape inference for ... started at 13:22

Jenkins Linux amd64 Build #1583 [push] Fix shape inference for ... started at 12:19

Jenkins Linux s390x Build #1581 [push] Fix shape inference for ... started at 13:19

Jenkins Linux s390x Build #1581 [push] Fix shape inference for ... passed after 46 min

Jenkins Linux amd64 Build #1583 [push] Fix shape inference for ... passed after 53 min

Jenkins Linux ppc64le Build #720 [push] Fix shape inference for ... passed after 57 min


Wrong binary installed on legacy NodeJS running via Rosetta

:wrench: Summary
We have some projects using older NodeJS versions 14.x which run in emulated mode (via Rosetta) on a macBook M1. This leads to issues with lefthook installation as proc.arch returns x64 in this case.
As a workaround we currently install lefthook globally on the system via brew.
Lefthook version
1.3.5
Steps to reproduce
Add lefthook to a project running a legacy NodeJS version.
Expected results
lefthoook-darwin-x86 is installed in node_modules
Actual results
lefthoook-darwin-x86 is installed in node_modules
Possible Solution
Check if a process runs via emulation via sysctl
https://stackoverflow.com/a/65347893

RTFM. Just found that there is a version that ships with all binaries. Guess this makes this issue obsolete then.

For people like me who were looking for the solution:
brew install lefthook

Also see https://github.com/evilmartians/lefthook/issues/166.


Fix context providers markdown code tags

Sometime in the last few days the formatting on the context providers doc page got a little messed up.  Probably just a diff/merge mistake.

The netlify deploy preview looks broken.  I doubt I could have caused that so going to assume that's just the current state.

Yup, the broken preview isn't on you. Thanks for catching this! Two merge mistakes in 24 hours...


Fix Prisma generate issue on first time install

Summary
When running this project for the first time, you will always get an error that the prisma client has not yet been generated. The current hotfix for this is to manually run prisma generate in the container. The previous version of the dockerfile contained a line for prisma generate, which seemed to silently fail. No client would be generated, and no errors would appear prior to the project failing to run.
We need either a way to generate the prisma client from the dockerfile, or an additional script that can generate the client on startup if it does not exist.

This could be a potential fix RUN $HOME/.poetry/bin/poetry run prisma generate


merge master into dev after 1.7.0 release

[x] Give a meaninful name to your PR, as it may end up being used in the release notes.
[x] Your code is flake8 compliant.
[x] Your code is python 3.6 compliant (specific python >3.6 syntax is currently not accepted).
[ ] If this is a new feature and not a bug fix, you've included the proper documentation in the ReadTheDocs documentation folder. https://github.com/DefectDojo/Documentation/tree/master/docs or provide feature documentation in the PR.
[ ] Model changes must include the necessary migrations in the dojo/db_migrations folder.
[ ] Add applicable tests to the unit tests.
[x] Add the proper label to categorize your PR.

@madchap @valentijnscholten
There is some commits from the last release that are in here and I'm not sure if that's correct.

The first commit in here from June is a bit weird, but maybe we missed one back then. Ideally we shouldn't make any other changes in this PR such as changing version numbers, but in practice it won't break anything I think.


Feature/holo 390 faucet smart contract

Describe Changes
I made this more better by doing ...

Faucet contract

Checklist before requesting a review

[x] I have performed a self-review of my code
[x] Code styles have been enforced
[x] All Hardhat tests are passing

Let's merge the PR #40 first and see if it creates conflicts to this branch before trying to merge it into experimental.


Additional kv:namespace tests

A bunch of commits that mostly flesh out the kv:namespace tests:

test: split kv tests out into their own file
test: move the temp directory handling to a helper function
add ignore words to spell checker
catch "yargs" errors
Fix spelling issues
fix: improve validation message for kv:namespace create
add tests for kv:namespace list
Improve the error message for bad kv:namespace delete commands

All polished up and ready for a final review (when you are back).


Starting a song in SONOS does not update the Homekit Status and vice-versa

Issue
Starting a song in SONOS does not update the Homekit Status and vice-versa
Log Messages

7/9/2021, 2:06:30 PMHOOBSSonosWARNINGwarning: heartbeat 6, drift 1842
7/9/2021, 2:06:30 PMHOOBSSonosRINCON_B8E93747354001400 [Manu’s Room Speakers]: associated S2 zone player
7/9/2021, 2:06:30 PMHOOBSSonosWARNINGwarning: RINCON_542A1B446C0A01400 [Sonos Roam]: rebooted {"name":"Sonos Roam","bootSeq":39,"oldBootSeq":38} -> 38
7/9/2021, 2:06:30 PMHOOBSSonosWARNINGwarning: heartbeat 7, drift 1275
7/9/2021, 2:06:30 PMHOOBSSonosWARNINGwarning: heartbeat 8, drift 279
7/9/2021, 2:06:32 PMHOOBSSonosWARNINGwarning: heartbeat 9, drift 1244
7/9/2021, 2:06:33 PMHOOBSSonosWARNINGwarning: heartbeat 10, drift 690
7/9/2021, 2:06:33 PMHOOBSSonosfound 33 S2 zone players in 21 zones
7/9/2021, 2:06:33 PMHOOBSSonos├─ Bachelor TV (+LS+RS)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_48A6B833315F01400 [Bachelor TV]: Sonos Beam (S14) (master, airPlay, tvIn)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_48A6B8AEB68801400 [Bachelor TV (LS)]: Sonos One SL (S22) (satellite)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_48A6B8AEB5CA01400 [Bachelor TV (RS)]: Sonos One SL (S22) (satellite)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Bachelor (L+R)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_48A6B8826D6C01400 [Bachelor (L)]: Sonos One (S18) (master, airPlay)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_48A6B8826E8C01400 [Bachelor (R)]: Sonos One (S18) (slave)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Basement
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_B8E9379BE5FA01400 [Basement]: Sonos Connect (ZP90) (master, audioIn)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Bathroom 2
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_5CAAFD6E59C401400 [Bathroom 2]: Sonos Play:1 (S1) (master)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Boost (invisible)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_7828CA74723601400 [Boost]: Sonos Boost (BR200) (master)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Dining Room
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_B8E9373AAD4601400 [Dining Room]: Sonos Play:3 (S3) (master)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Garage (Gym) (L+R)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_48A6B8FE5FA801400 [Garage (Gym) (L)]: Sonos One (S18) (master, airPlay)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_48A6B8FE5FDA01400 [Garage (Gym) (R)]: Sonos One (S18) (slave)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Garage (Workbench)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_B8E9379BE4FE01400 [Garage (Workbench)]: Sonos Connect (ZP90) (master, audioIn)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Guest Room
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_B8E937DDBC2A01400 [Guest Room]: Sonos Play:3 (S3) (master)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Hallway 0.5
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_5CAAFD6E5B5E01400 [Hallway 0.5]: Sonos Play:1 (S1) (master)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Kitchen Speakers (L+R)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_7828CAF131E601400 [Kitchen Speakers (L)]: Sonos One (S18) (master, airPlay)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_7828CAF131DA01400 [Kitchen Speakers (R)]: Sonos One (S18) (slave)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Living Room Speakers (L+R)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_5CAAFDFF2C6C01400 [Living Room Speakers (L)]: Sonos Play:5 (S6) (master, airPlay, audioIn)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_5CAAFD08DE3C01400 [Living Room Speakers (R)]: Sonos Play:5 (S6) (slave, audioIn)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Living Room TV (+Sub+RS+LS)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_5CAAFD1C788401400 [Living Room TV]: Sonos Playbar (S9) (master, tvIn)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_5CAAFD811B1201400 [Living Room TV (Sub)]: Sonos Sub (Sub) (satellite)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_5CAAFD6E65E201400 [Living Room TV (RS)]: Sonos Play:1 (S1) (satellite)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_5CAAFD6E652801400 [Living Room TV (LS)]: Sonos Play:1 (S1) (satellite)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Manu’s Room Speakers (+LS+RS)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_B8E93747354001400 [Manu’s Room Speakers]: Sonos Playbase (S11) (master, airPlay, tvIn)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_5CAAFD284C4C01400 [Manu’s Room Speakers (LS)]: Sonos Play:1 (S1) (satellite)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_5CAAFD60569001400 [Manu’s Room Speakers (RS)]: Sonos Play:1 (S1) (satellite)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Master Bathroom
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_5CAAFD96773601400 [Master Bathroom]: Sonos Play:1 (S1) (master)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Master Bedroom (L+R)
7/9/2021, 2:06:33 PMHOOBSSonos│  ├─ RINCON_5CAAFD967AC201400 [Master Bedroom (L)]: Sonos Play:1 (S1) (master)
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_5CAAFD9436D201400 [Master Bedroom (R)]: Sonos Play:1 (S1) (slave)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Office
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_B8E9379DA85401400 [Office]: Sonos Connect (ZP90) (master, audioIn)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Playroom
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_5CAAFD60583001400 [Playroom]: Sonos Play:1 (S1) (master)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Sonos Move
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_48A6B8E6C49601400 [Sonos Move]: Sonos Move (S17) (master, airPlay)
7/9/2021, 2:06:33 PMHOOBSSonos├─ Sonos Roam
7/9/2021, 2:06:33 PMHOOBSSonos│  └─ RINCON_542A1B446C0A01400 [Sonos Roam]: Sonos Roam (S27) (master, airPlay)
7/9/2021, 2:06:33 PMHOOBSSonos└─ Studio Port
7/9/2021, 2:06:33 PMHOOBSSonos   └─ RINCON_48A6B820B88001400 [Studio Port]: Sonos Port (S23) (master, airPlay, audioIn)
7/9/2021, 2:06:33 PMHOOBSSonosBachelor TV Sonos: remove stale characteristic Volume
7/9/2021, 2:06:33 PMHOOBSSonosBachelor TV: set Serial Number to "TV_48A6B833315F01400"
7/9/2021, 2:06:33 PMHOOBSSonosBachelor TV: set Manufacturer to "Sonos"
7/9/2021, 2:06:33 PMHOOBSSonosBachelor TV: set Model to "Beam (S14)"
7/9/2021, 2:06:33 PMHOOBSSonosBachelor TV: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:33 PMHOOBSSonosBachelor TV TV: set Active to 0
7/9/2021, 2:06:33 PMHOOBSSonosBachelor TV TV: set Configured Name to "Bachelor TV Sonos"
7/9/2021, 2:06:33 PMHOOBSSonosBachelor Sonos: remove stale characteristic Volume
7/9/2021, 2:06:33 PMHOOBSSonosBachelor L: set Serial Number to "TV_48A6B8826D6C01400"
7/9/2021, 2:06:33 PMHOOBSSonosBachelor L: set Manufacturer to "Sonos"
7/9/2021, 2:06:33 PMHOOBSSonosBachelor L: set Model to "One (S18)"
7/9/2021, 2:06:33 PMHOOBSSonosBachelor L: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:34 PMHOOBSSonosBachelor TV: set Active to 0
7/9/2021, 2:06:34 PMHOOBSSonosBachelor TV: set Configured Name to "Bachelor Sonos"
7/9/2021, 2:06:34 PMHOOBSSonosBasement Sonos: remove stale characteristic Volume
7/9/2021, 2:06:34 PMHOOBSSonosBasement: set Serial Number to "TV_B8E9379BE5FA01400"
7/9/2021, 2:06:34 PMHOOBSSonosBasement: set Manufacturer to "Sonos"
7/9/2021, 2:06:34 PMHOOBSSonosBasement: set Model to "Connect (ZP90)"
7/9/2021, 2:06:34 PMHOOBSSonosBasement: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:34 PMHOOBSSonosBasement TV: set Active to 0
7/9/2021, 2:06:34 PMHOOBSSonosBasement TV: set Configured Name to "Basement Sonos"
7/9/2021, 2:06:34 PMHOOBSSonosBathroom 2 Sonos: remove stale characteristic Volume
7/9/2021, 2:06:34 PMHOOBSSonosBathroom 2: set Serial Number to "TV_5CAAFD6E59C401400"
7/9/2021, 2:06:34 PMHOOBSSonosBathroom 2: set Manufacturer to "Sonos"
7/9/2021, 2:06:34 PMHOOBSSonosBathroom 2: set Model to "Play:1 (S1)"
7/9/2021, 2:06:34 PMHOOBSSonosBathroom 2: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:34 PMHOOBSSonosBathroom 2 TV: set Active to 0
7/9/2021, 2:06:34 PMHOOBSSonosBathroom 2 TV: set Configured Name to "Bathroom 2 Sonos"
7/9/2021, 2:06:34 PMHOOBSSonosDining Room Sonos: remove stale characteristic Volume
7/9/2021, 2:06:34 PMHOOBSSonosDining Room: set Serial Number to "TV_B8E9373AAD4601400"
7/9/2021, 2:06:34 PMHOOBSSonosDining Room: set Manufacturer to "Sonos"
7/9/2021, 2:06:34 PMHOOBSSonosDining Room: set Model to "Play:3 (S3)"
7/9/2021, 2:06:34 PMHOOBSSonosDining Room: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:35 PMHOOBSSonosDining Room TV: set Active to 0
7/9/2021, 2:06:35 PMHOOBSSonosDining Room TV: set Configured Name to "Dining Room Sonos"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Gym) Sonos: remove stale characteristic Volume
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Gym) L: set Serial Number to "TV_48A6B8FE5FA801400"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Gym) L: set Manufacturer to "Sonos"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Gym) L: set Model to "One (S18)"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Gym) L: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Gym) TV: set Active to 0
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Gym) TV: set Configured Name to "Garage (Gym) Sonos"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Workbench) Sonos: remove stale characteristic Volume
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Workbench): set Serial Number to "TV_B8E9379BE4FE01400"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Workbench): set Manufacturer to "Sonos"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Workbench): set Model to "Connect (ZP90)"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Workbench): set Firmware Revision to "13.1.4"
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Workbench) TV: set Active to 0
7/9/2021, 2:06:35 PMHOOBSSonosGarage (Workbench) TV: set Configured Name to "Garage (Workbench) Sonos"
7/9/2021, 2:06:35 PMHOOBSSonosGuest Room Sonos: remove stale characteristic Volume
7/9/2021, 2:06:35 PMHOOBSSonosGuest Room: set Serial Number to "TV_B8E937DDBC2A01400"
7/9/2021, 2:06:35 PMHOOBSSonosGuest Room: set Manufacturer to "Sonos"
7/9/2021, 2:06:35 PMHOOBSSonosGuest Room: set Model to "Play:3 (S3)"
7/9/2021, 2:06:35 PMHOOBSSonosGuest Room: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:35 PMHOOBSSonosGuest Room TV: set Active to 0
7/9/2021, 2:06:35 PMHOOBSSonosGuest Room TV: set Configured Name to "Guest Room Sonos"
7/9/2021, 2:06:35 PMHOOBSSonosHallway 0.5 Sonos: remove stale characteristic Volume
7/9/2021, 2:06:35 PMHOOBSSonosHallway 0.5: set Serial Number to "TV_5CAAFD6E5B5E01400"
7/9/2021, 2:06:35 PMHOOBSSonosHallway 0.5: set Manufacturer to "Sonos"
7/9/2021, 2:06:35 PMHOOBSSonosHallway 0.5: set Model to "Play:1 (S1)"
7/9/2021, 2:06:35 PMHOOBSSonosHallway 0.5: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:36 PMHOOBSSonosHallway 0.5 TV: set Active to 0
7/9/2021, 2:06:36 PMHOOBSSonosHallway 0.5 TV: set Configured Name to "Hallway 0.5 Sonos"
7/9/2021, 2:06:36 PMHOOBSSonosKitchen Speakers Sonos: remove stale characteristic Volume
7/9/2021, 2:06:36 PMHOOBSSonosKitchen Speakers L: set Serial Number to "TV_7828CAF131E601400"
7/9/2021, 2:06:36 PMHOOBSSonosKitchen Speakers L: set Manufacturer to "Sonos"
7/9/2021, 2:06:36 PMHOOBSSonosKitchen Speakers L: set Model to "One (S18)"
7/9/2021, 2:06:36 PMHOOBSSonosKitchen Speakers L: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:36 PMHOOBSSonosKitchen Speakers TV: set Active to 0
7/9/2021, 2:06:36 PMHOOBSSonosKitchen Speakers TV: set Configured Name to "Kitchen Speakers Sonos"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room Speakers Sonos: remove stale characteristic Volume
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room Speakers L: set Serial Number to "TV_5CAAFDFF2C6C01400"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room Speakers L: set Manufacturer to "Sonos"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room Speakers L: set Model to "Play:5 (S6)"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room Speakers L: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room Speakers TV: set Active to 0
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room Speakers TV: set Configured Name to "Living Room Speakers Sonos"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room TV Sonos: remove stale characteristic Volume
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room TV: set Serial Number to "TV_5CAAFD1C788401400"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room TV: set Manufacturer to "Sonos"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room TV: set Model to "Playbar (S9)"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room TV: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room TV TV: set Active to 0
7/9/2021, 2:06:36 PMHOOBSSonosLiving Room TV TV: set Configured Name to "Living Room TV Sonos"
7/9/2021, 2:06:36 PMHOOBSSonosManu’s Room Speakers Sonos: remove stale characteristic Volume
7/9/2021, 2:06:36 PMHOOBSSonosManu’s Room Speakers: set Serial Number to "TV_B8E93747354001400"
7/9/2021, 2:06:36 PMHOOBSSonosManu’s Room Speakers: set Manufacturer to "Sonos"
7/9/2021, 2:06:36 PMHOOBSSonosManu’s Room Speakers: set Model to "Playbase (S11)"
7/9/2021, 2:06:36 PMHOOBSSonosManu’s Room Speakers: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:37 PMHOOBSSonosManu’s Room Speakers TV: set Active to 0
7/9/2021, 2:06:37 PMHOOBSSonosManu’s Room Speakers TV: set Configured Name to "Manu’s Room Speakers Sonos"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bathroom Sonos: remove stale characteristic Volume
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bathroom: set Serial Number to "TV_5CAAFD96773601400"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bathroom: set Manufacturer to "Sonos"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bathroom: set Model to "Play:1 (S1)"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bathroom: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bathroom TV: set Active to 0
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bathroom TV: set Configured Name to "Master Bathroom Sonos"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bedroom Sonos: remove stale characteristic Volume
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bedroom L: set Serial Number to "TV_5CAAFD967AC201400"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bedroom L: set Manufacturer to "Sonos"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bedroom L: set Model to "Play:1 (S1)"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bedroom L: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bedroom TV: set Active to 0
7/9/2021, 2:06:37 PMHOOBSSonosMaster Bedroom TV: set Configured Name to "Master Bedroom Sonos"
7/9/2021, 2:06:37 PMHOOBSSonosOffice Sonos: remove stale characteristic Volume
7/9/2021, 2:06:37 PMHOOBSSonosOffice: set Serial Number to "TV_B8E9379DA85401400"
7/9/2021, 2:06:37 PMHOOBSSonosOffice: set Manufacturer to "Sonos"
7/9/2021, 2:06:37 PMHOOBSSonosOffice: set Model to "Connect (ZP90)"
7/9/2021, 2:06:37 PMHOOBSSonosOffice: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:37 PMHOOBSSonosOffice TV: set Active to 0
7/9/2021, 2:06:37 PMHOOBSSonosOffice TV: set Configured Name to "Office Sonos"
7/9/2021, 2:06:37 PMHOOBSSonosPlayroom Sonos: remove stale characteristic Volume
7/9/2021, 2:06:37 PMHOOBSSonosPlayroom: set Serial Number to "TV_5CAAFD60583001400"
7/9/2021, 2:06:37 PMHOOBSSonosPlayroom: set Manufacturer to "Sonos"
7/9/2021, 2:06:37 PMHOOBSSonosPlayroom: set Model to "Play:1 (S1)"
7/9/2021, 2:06:37 PMHOOBSSonosPlayroom: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:38 PMHOOBSSonosPlayroom TV: set Active to 0
7/9/2021, 2:06:38 PMHOOBSSonosPlayroom TV: set Configured Name to "Playroom Sonos"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Move Sonos: remove stale characteristic Volume
7/9/2021, 2:06:38 PMHOOBSSonosSonos Move: set Serial Number to "TV_48A6B8E6C49601400"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Move: set Manufacturer to "Sonos"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Move: set Model to "Move (S17)"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Move: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Move TV: set Active to 0
7/9/2021, 2:06:38 PMHOOBSSonosSonos Move TV: set Configured Name to "Sonos Move Sonos"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Roam Sonos: remove stale characteristic Volume
7/9/2021, 2:06:38 PMHOOBSSonosSonos Roam: set Serial Number to "TV_542A1B446C0A01400"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Roam: set Manufacturer to "Sonos"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Roam: set Model to "Roam (S27)"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Roam: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:38 PMHOOBSSonosSonos Roam TV: set Active to 0
7/9/2021, 2:06:38 PMHOOBSSonosSonos Roam TV: set Configured Name to "Sonos Roam Sonos"
7/9/2021, 2:06:38 PMHOOBSSonosStudio Port Sonos: remove stale characteristic Volume
7/9/2021, 2:06:38 PMHOOBSSonosStudio Port: set Serial Number to "TV_48A6B820B88001400"
7/9/2021, 2:06:38 PMHOOBSSonosStudio Port: set Manufacturer to "Sonos"
7/9/2021, 2:06:38 PMHOOBSSonosStudio Port: set Model to "Port (S23)"
7/9/2021, 2:06:38 PMHOOBSSonosStudio Port: set Firmware Revision to "13.1.4"
7/9/2021, 2:06:38 PMHOOBSSonosStudio Port TV: set Active to 0
7/9/2021, 2:06:38 PMHOOBSSonosStudio Port TV: set Configured Name to "Studio Port Sonos"
7/9/2021, 2:06:39 PMHOOBSSonosLiving Room Speakers Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosStudio Port Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosBathroom 2 Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosBasement Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosDining Room Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosGarage (Gym) Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosGarage (Workbench) Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosGuest Room Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosHallway 0.5 Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosKitchen Speakers Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosMaster Bathroom Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosOffice Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosPlayroom Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosBachelor TV Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosBachelor Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosLiving Room TV Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosManu’s Room Speakers Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosMaster Bedroom Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosSonos Move Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSSonosSonos Roam Sonos: get Remaining Duration: return 0s
7/9/2021, 2:06:39 PMHOOBSBachelor TV 63C3 is running on port 33481.
7/9/2021, 2:06:39 PMHOOBSBachelor L D5A9 is running on port 43067.
7/9/2021, 2:06:39 PMHOOBSBasement 1630 is running on port 34613.
7/9/2021, 2:06:39 PMHOOBSBathroom 2 A15F is running on port 46203.
7/9/2021, 2:06:39 PMHOOBSDining Room 2DFE is running on port 46825.
7/9/2021, 2:06:39 PMHOOBSGarage (Gym) L 25F7 is running on port 37493.
7/9/2021, 2:06:39 PMHOOBSGarage (Workbench) 9B9B is running on port 40793.
7/9/2021, 2:06:39 PMHOOBSGuest Room 412F is running on port 39581.
7/9/2021, 2:06:39 PMHOOBSHallway 0.5 BDBB is running on port 34821.
7/9/2021, 2:06:39 PMHOOBSKitchen Speakers L 6514 is running on port 39083.
7/9/2021, 2:06:40 PMHOOBSLiving Room Speakers L 1C30 is running on port 34811.
7/9/2021, 2:06:40 PMHOOBSLiving Room TV 39B8 is running on port 44045.
7/9/2021, 2:06:40 PMHOOBSManu’s Room Speakers 37F0 is running on port 41515.
7/9/2021, 2:06:40 PMHOOBSMaster Bathroom 2574 is running on port 37797.
7/9/2021, 2:06:40 PMHOOBSMaster Bedroom L A39A is running on port 35771.
7/9/2021, 2:06:40 PMHOOBSOffice 2D75 is running on port 40903.
7/9/2021, 2:06:40 PMHOOBSPlayroom D00D is running on port 39463.
7/9/2021, 2:06:40 PMHOOBSSonos Move 541B is running on port 40305.
7/9/2021, 2:06:40 PMHOOBSSonos Roam 1736 is running on port 35157.
7/9/2021, 2:06:40 PMHOOBSStudio Port F59C is running on port 38685.
7/9/2021, 2:06:40 PMHOOBSSonosWARNINGwarning: heartbeat 11, drift 7162
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGwarning: heartbeat 12, drift 6946
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGwarning: heartbeat 13, drift 6252
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGwarning: heartbeat 14, drift 5491
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGwarning: heartbeat 15, drift 4496
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGBachelor TV: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORBachelor TV: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGBachelor L: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORBachelor L: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGBasement: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORBasement: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGBathroom 2: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORBathroom 2: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGDining Room: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORDining Room: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGGarage (Gym) L: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORGarage (Gym) L: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGGarage (Workbench): warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORGarage (Workbench): error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGGuest Room: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORGuest Room: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGHallway 0.5: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORHallway 0.5: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGKitchen Speakers L: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORKitchen Speakers L: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGLiving Room Speakers L: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORLiving Room Speakers L: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGLiving Room TV: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORLiving Room TV: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGManu’s Room Speakers: warning: request 6: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORManu’s Room Speakers: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGMaster Bathroom: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORMaster Bathroom: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGMaster Bedroom L: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORMaster Bedroom L: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGOffice: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERROROffice: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGPlayroom: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORPlayroom: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGSonos Move: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORSonos Move: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGSonos Roam: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORSonos Roam: error: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosWARNINGStudio Port: warning: request 5: http status 412 Precondition Failed
7/9/2021, 2:06:41 PMHOOBSSonosERRORStudio Port: error: http status 412 Precondition Failed
7/9/2021, 2:06:42 PMHOOBSSonosWARNINGwarning: heartbeat 16, drift 4056
7/9/2021, 2:06:42 PMHOOBSSonosWARNINGwarning: heartbeat 17, drift 3534
7/9/2021, 2:06:42 PMHOOBSSonosWARNINGwarning: heartbeat 18, drift 2617
7/9/2021, 2:06:43 PMHOOBSSonosWARNINGwarning: heartbeat 19, drift 1856
7/9/2021, 2:06:43 PMHOOBSSonosWARNINGSonos Roam: warning: request 6: http status 412 Precondition Failed
7/9/2021, 2:06:43 PMHOOBSSonosERRORSonos Roam: error: http status 412 Precondition Failed
7/9/2021, 2:06:43 PMHOOBSSonosWARNINGSonos Move: warning: request 6: http status 412 Precondition Failed
7/9/2021, 2:06:43 PMHOOBSSonosERRORSonos Move: error: http status 412 Precondition Failed
7/9/2021, 2:06:43 PMHOOBSSonosWARNINGwarning: heartbeat 20, drift 1141
7/9/2021, 2:06:43 PMHOOBSSonosWARNINGwarning: heartbeat 21, drift 299
7/9/2021, 2:06:47 PMHOOBSSonosManu’s Room Speakers TV: set Active Identifier to "n/a"
7/9/2021, 2:06:52 PMHOOBSSonosWARNINGwarning: heartbeat 29, drift 807
7/9/2021, 2:06:57 PMHOOBSSonosBachelor Sonos: On changed from false to true
7/9/2021, 2:06:58 PMHOOBSSonosBachelor TV: set Active from 0 to 1
7/9/2021, 2:06:58 PMHOOBSSonosBachelor Sonos: On changed from true to true
7/9/2021, 2:06:58 PMHOOBSSonosWARNINGwarning: heartbeat 36, drift 342
7/9/2021, 2:07:02 PMHOOBSSonosLiving Room Speakers Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosStudio Port Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosBathroom 2 Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosBasement Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosDining Room Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosGarage (Gym) Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosGarage (Workbench) Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosGuest Room Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosHallway 0.5 Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosKitchen Speakers Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosMaster Bathroom Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosOffice Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosPlayroom Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosBachelor TV Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosBachelor Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosLiving Room TV Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosManu’s Room Speakers Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosMaster Bedroom Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosSonos Move Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:02 PMHOOBSSonosSonos Roam Sonos: get Remaining Duration: return 0s
7/9/2021, 2:07:13 PMHOOBSSonosBachelor Sonos: On changed from true to false
7/9/2021, 2:07:13 PMHOOBSSonosBachelor TV: set Active from 1 to 0
7/9/2021, 2:07:13 PMHOOBSSonosBachelor Sonos: On changed from false to false
Debug Files

Please, next time, capture a log file and attach that, instead of pasting a lot of lines.
Damn, this is not logging the request that causes the precondition, but I suspect it's a SUBSCRIBE.
I need to see the log entries from when Homebridge starts.  In particular, the line showing the Homebridge ZP version, and the line showing the port of the web server.  Could you check what subscriptions that web server is reporting, see https://github.com/ebaauw/homebridge-zp#web-server?

Hi Eric,
You`re probably right, the listening IP does not make sense.
log (3).txt
Sonoslistening on http://<IP_ADDRESS>:34037/notify
Danny

That actually does make sense: it simply means the web server is listening on all interfaces.
You don't seem to have Homebridge debug mode enabled.  I need to see the debug messages by Homebridge ZP.  The Internal Server Error messages are in response the second request to each zone player.  The first request, a GET of device_description.xml has succeeded, so the zone players are reachable altrigh.  The second request is a SOAP call to get the ZoneGroupTopology state.  This call is known to fail when there's "too many" players in your household.  See https://github.com/ebaauw/homebridge-zp/issues/177.  Homebridge ZP should mitigate this by subscribing to ZoneGroupTopology events, but apparently none are received.
Can you please check that zp -H <IP_ADDRESS> -D info returns the info of the zone player?  You might also use the IP address of another zone player.  You should see debug messages similar to:
$ zp -D info
zp: sn-living: request 1: GET /xml/device_description.xml
zp: sn-living: request 1: 200 OK
zp: sn-living: request 2: POST /ZoneGroupTopology/Control GetZoneGroupStatex
zp: sn-living: request 2: POST /ZoneGroupTopology/Control GetZoneGroupStatex
zp: warning: sn-living: request 2: http status 500 Internal Server Error
zp: listening on http://<IP_ADDRESS>:53964/notify
zp: sn-living: request 3: SUBSCRIBE /ZoneGroupTopology/Event
zp: sn-living: request 3: 200 OK
zp: undefined: notify ZoneGroupTopology/Event
zp: sn-living: request 4: UNSUBSCRIBE /ZoneGroupTopology/Event
zp: sn-living: request 4: 200 OK
zp: sn-living: reached using local address 192.x.x.40
{
  "address": "192.x.x.71",
  "bootSeq": 174,
  "channel": "",
  "homeTheatre": true,
  "id": "RINCON_5CAAFD1FA0D701400",
  "lastSeen": 0,
  "modelName": "Sonos Playbar",
  "modelNumber": "S9",
  "name": "Living Room",
  "role": "master",
  "satellites": [
    "RINCON_5CAAFD7C941401400",
    "RINCON_5CAAFD7C940401400",
    "RINCON_949F3EAECB4801400"
  ],
  "sonosOs": "S2",
  "tvIn": true,
  "version": "13.1.4",
  "zone": "RINCON_5CAAFD1FA0D701400",
  "zoneDisplayName": "Living Room (+LS+RS+Sub)",
  "zoneName": "Living Room"
}
zp info: closed http://<IP_ADDRESS>:53964/notify

Note that I've deliberately broken the GetZoneGroupState, to simulate your situation.
If you don't see any output after the request 3: 200 OK, please capture the output of zp -H <IP_ADDRESS> -DDD info to a file, and attach that file.  This ludicrous amount of logging should tell me what's going on.

But if I look at my bridge address with the same port they are all there....

Missed that edit, sorry.  So the other zone players have registered with the listener, but not yet subscribed to any events.  The Sonos Move has subscribed to ZoneGroupTopology events, and Homebridge ZP seems to be waiting indefinitely for a notification.  My money's on a firewall blocking the incoming notifications.

Hi Eric,
I will get the Debug log.  For your information as soon as I reboot a Sonos Speaker it does register in Homekit (but still the on/off is not reflected in Sonos or vice-versa).  There is no firewall between the Speakers and Hoobs Server.  Everything is in the same subnet.
Thanks,
Danny

Thanks.  If you have access to the command line, it may be easier to experiment with zp.

Hi Eric, yes I do have access to the command line. I ssh to it but sorry maybe I missed something but I can run the zp command, maybe I`m not in the right mode or something.

Normally, npm installs zp to /usr/bin or /usr/local/bin (depending on how NodeJS was installed).  If it cannot be found, try npx zp, instead of zp.

Unfortunately, it still does not work...
hoobs@hoobs:/usr/bin $ zp
-bash: zp: command not found
hoobs@hoobs:/usr/bin $ npx zp
npx: installed 2 in 4.755s
command not found: zp
hoobs@hoobs:/usr/bin $ cd /usr/local/bin
hoobs@hoobs:/usr/local/bin $ zp
-bash: zp: command not found
hoobs@hoobs:/usr/local/bin $ npx zp
npx: installed 2 in 4.745s
command not found: zp
:(

You might try and search for it.  It's .../node_modules/homebridge-zp/cli/zp.js, but I don't know how Hoobs installs plugins.  Normally npm creates a symlink to this file in /usr/bin or /usr/local/bin.
Normally, the current directory isn't in your PATH, so doing a cd /usr/bin won't make a difference, unless you try ./zp.

Unfortunately, I`m still having issue running the pluggin in CLI.... but I received this in the logging now....
7/14/2021, 7:43:18 PMHOOBSERROR(node:16295) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added to [ZpClient]. Use emitter.setMaxListeners() to increase limit
7/14/2021, 7:43:18 PMHOOBSERROR(Use node --trace-warnings ... to show where the warning was created)
7/14/2021, 7:48:17 PMHOOBSERROR(node:16295) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 init listeners added to [ZpClient]. Use emitter.setMaxListeners() to increase limit
Thanks,
Danny

Logs attached from zp.js.
zpdebug169.log
zpdebug188.log

Noticed you published 1.3.4 so I upgraded the plugin.  Now I get "412 Precondition failed" error responses.  See attached log.
zp-postupdate-412.log

Logs attached from zp.js.

Brilliant, thanks!
In your first log from the Move at <IP_ADDRESS> log, the GetZoneGroupState actually succeeds, but reports "only" 19 zone player in the installation.  In your second log from the Play:1 at <IP_ADDRESS>, the GetZoneGroupState fails, but the fallback succeeds, reporting 34 zone players, including the Move from the other log.  Did you capture these logs shortly after each other?  That would mean the topology hasn't been synced between the zone players, which I haven't seen before.

Noticed you published 1.3.4 so I upgraded the plugin. Now I get "412 Precondition failed" error responses.

That's to be expected; on larger installations the call to GetZoneGroupState, see #131 and #177.  As a fallback, Homebridge ZP subscribes to events from the ZoneGroupTopology service to receive the layout of the installation.  Afaik, these two methods are the only way to know whether a zone player should be exposed, or is part of a stereo pair or home theatre setup and should be hidden.
The issue you're facing is that the fallback fails as well.  I'm trying to understand why, in particular if it's something going wrong with Homebridge ZP, or if it's simply because your network is too large.
The post update log looks kinda good, in that Homebridge ZP finds some zone players, but not all.  It looks like Homebridge ZP has found 33 zone players through UPnP, but only exposes half of them.  I really need to see the full Homebridge log, from the start of Homebridge through it running for a couple of minutes, while Homebridge DEBUG mode is enabled.
I see some attention points:
 7/16/2021, 1:53:31 PMHOOBSSonosRINCON_48A6B8E6C49601400 [Sonos Move]: associated S2 zone player

Homebridge ZP picks a Move as associated zone player (it typically pick the first to respond).  That's a bad idea, as the Move (and the Roam) are battery powered, and mobile, so they're likely to leave the network.  Homebridge ZP should probably see if it can find another zone player.
7/16/2021, 1:53:51 PMHOOBSSonosWARNINGwarning: RINCON_5CAAFD9439F001400 [<IP_ADDRESS>]: no ZoneGroupTopology event received in 15s

The fallback fails for the Hallway 2 zone player, after which Homebridge ZP exposed the confirmed zone players.  So for these, the fallback as succeeded.  That would mean including the SUBSCRIBE to ZoneGroupTopology.  However, the subsequent SUBSCRIBE to GroupManagement fails for all 13 zones.
Since, you found a way to run zp, could you try zp -H <IP_ADDRESS> -D topology and zp -H <IP_ADDRESS> -D eventlog?  I half expect/hope that both will succeed.  Could you then try the same for .188 and for .187?  If they fail, could you please capture the debug output when specifying -DDD?

Hi Eric,
There are the file you requested.
zp -H <IP_ADDRESS> -D eventlog.log
zp -H <IP_ADDRESS> -D topology.log
zp -H <IP_ADDRESS> -DDD topology.log
zp -H <IP_ADDRESS> -D eventlog.log
zp -H <IP_ADDRESS> -D topology.log
zp -H <IP_ADDRESS> -DDD topology.log
Thanks a lot for your help,
Danny

Ok, I think I understand what's happening.  Your zone players are running out of resources, and don't accept additional subscriptions.  Each zone player only supports a limited number of subscriptions (I think per service), see #68.  Zone players subscribe to each other's events to maintain their mesh network, notably DeviceProperties and GroupManagement, maybe also ZoneGroupTopology.  Hence Homebridge ZP's attempts to subscribe to these services fail.  I think the latest release is more forgiving on startup, but that doesn't make up for the missing info because of the failed subscriptions.
There used to be a diagnostics page on the zone player (somewhere under http://<IP_ADDRESS>:1400/status), where you could monitor what subscriptions had been made on it (that's how I know the zone player subscribe with each other).  Unfortunately, they disabled that.  I know of no other way to verify this.  See also https://bsteiner.info/articles/hidden-sonos-interface.
Do you use the Sonos app?  I think you might see weird behaviour there as well.  If you're up to it, you might sniff the network traffic between the Sonos app and the zone players (it's unencrypted); I'm fairly certain it'll show similar errors.
I'm afraid there's little I can do; this is a limit in the zone player firmware, maybe even in the hardware.  I wouldn't be surprised if the limit on older zone players is lower than on newer zone players.  The limit of 32 zone players per installation (household) is very real, I'm afraid.  Granted, Homebridge ZP is a little more demanding than the Sonos app when it comes to the number subscriptions used.  I might be able to optimise that, although that will be a non-trivial change.  I don't think I can fully work around it, though.
Even then, the zone players themselves fail to maintain the mesh network properly.  You might check http://<IP_ADDRESS>:1400/support/review.  That should give an overview of all zone players this zone player knows.  Each player should know all others, but from your earlier logs, they don't.
You might also try a zp -H <IP_ADDRESS> -D topology -v.  This will try and get the topology from each zone player known to <IP_ADDRESS>.  With -DD it will log the responses converted to JSON, but it's still a bit tedious to analyse these.

Thanks Eric!  I will see if I can go down to 32.  I might remove my bridge and replace to Play1 with a SONOS Port to stay at 32 and see if this is solving the issue.

Beta v1.4.0-1 should be a bit more forgiving on startup, and should replace the associated zone player when a battery-powered one had been selected earlier.

In a bit of an experimental mood, I ran 33 instances of zp eventlog in parallel.
When running against my old Sonos Connect, the only zone player in my S1 household, the subscription for each service fails at the 33rd instance.
When running against my PlayBar, in my S2 household with 11 zone players in 6 zones, some subscriptions fail earlier:

Service
Fails at Instance
Subscriptions# zp + # HbZP + Rest

/AlarmClock
33
32 + 0 + 0

/DeviceProperties
23
22 + 0 + 10 zone players

/ZoneGroupTopology
33
32 + 0 + 0

/GroupManagement
22
21 + 1 + 10 zone players

/HTControl
33
32 + 0 + 0

/MediaServer/ContentDirectory
30
29 + 0 + 3 ??

/MediaRenderer/RenderingControl
31
30 + 1 + 1 ??

/MediaRenderer/AVTransport
31
30 + 1 + 1 ??

/MediaRenderer/GroupRenderingControl
32
31 + 1 + 0

/MediaRenderer/VirtualLineIn
31
30 + 0 + 2  ??

I think the following conclusions are valid:

There is a limit of 32 subscriptions per service, at least on my zone players.
To manage the mesh network, each zone player subscribes to the DeviceProperties and GroupManagement services of all other zone players.  With 32 zone players in a household, that would leave room for only one API client to subscribe to these services.  Homebridge ZP should not subscribe to these services.
Homebridge ZP doesn't use DeviceProperties, so we're good there, but it relies on GroupManagement to know when zones are grouped or ungrouped.  Maybe the same info can be retrieved from ZoneGroupTopology instead.
I'm not exactly sure who the remaining subscribers are to ContentDirectory , RenderingControl, AVTransport, and VirtualLineIn.  Maybe they're stale subscriptions from a crashed Sonos app.  Maybe some UPnP client has found these services (they're generic services on the generic MediaServer and MediaRenderer sub devices).  Homebridge ZP doesn't subscribe to ContentDirectory nor VirtualLineIn; it does use RenderingControl and AVTransport.

Great test Eric!  That might explain a lot.   From what I`m understanding now, I might not have the choice to go under 32 devices.  I will have to figure out a way to remove 2 speakers....
Thanks for your great work!
Danny

I’m working on ditching the use of GroupManagement by Homebridge ZP.  My understanding is that a network of up to 33 zone players would then work.  The v1.4.0-x betas already pick a non-battery-powered zone player as associated zone player, and support multiple households.    Of course, you cannot sync music across multiple households, but you should be able to control all households using a single Homebridge ZP instance.  I would probably move more than two players to the new household, just to keep some slack.

Thanks Eric!  Very curious to try version 1.4.0. :)

Could you please try beta v1.4.0-3?

Sure, is it available now ?
On Sat, Jul 24, 2021 at 10:12 AM Erik Baauw @.***>
wrote:

Could you please try beta v1.4.0-3?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ebaauw/homebridge-zp/issues/180#issuecomment-886059331,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEWERJMDZM45TZZKTL623TTZLC4LANCNFSM5ADHGSNQ
.

Yes, just published it.

Should be working in v1.4.0.

Hi Eric!
I can confirm that it’s working now! :)
Danny
On Sat, Jul 31, 2021 at 09:08 Erik Baauw @.***> wrote:

Should be working in v1.4.0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ebaauw/homebridge-zp/issues/180#issuecomment-890346166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEWERN4FAMQU7XCZ72PG5DT2PYTVANCNFSM5ADHGSNQ
.

A huge thank you man!
On Sat, Jul 31, 2021 at 09:08 Erik Baauw @.***> wrote:

Should be working in v1.4.0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ebaauw/homebridge-zp/issues/180#issuecomment-890346166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEWERN4FAMQU7XCZ72PG5DT2PYTVANCNFSM5ADHGSNQ
.

How many zone players in a single household?

33 speakers and I try back the bridge.  So 34 total.  All working well :)
On Sat, Jul 31, 2021 at 15:28 Erik Baauw @.***> wrote:

How many zone players in a single household?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ebaauw/homebridge-zp/issues/180#issuecomment-890394404,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEWERKTVBLBVRNBEU6APO3T2RFFZANCNFSM5ADHGSNQ
.


Brightness control works on one of two identical monitors

Checklist

[X] I have searched for existing issues
[X] I have looked through the Monitor Troubleshooting wiki
[X] I have updated MonitorControl to the latest version (using v2.0.0 via homebrew)

Describe the issue
Brightness control works only for one monitor. When changing the brightness, the HUD appears on both monitors, and the MonitorControl menu shows the brightness being lower on both, but the actual brightness on one of the monitors remains unchanged.
Expected behavior
When pressing the brightness buttons on my keyboard, i expected brightness to change on both monitors simultaneously. Instead, only one monitor's brightness changes.
Additional context
Monitors are in 4K60 HDR mode.
 I have two HP Envy 27 Inch monitors with proper DP cables. Can confirm only works for 1 monitor.

Another clue to what's happening here. If I adjust the brightness for the first monitor listed in the menu, it changes the brightness only for one monitor. Changing the brightness for the second monitor listed also changes the same monitor.
Perhaps brightness changes are only applied to the first monitor of each make/model?

Duplicate of #49


Run Windows notifiarr client in background

I would like to run the client purely in the background.
Upon startup, it just makes a terminal window but I would like to have it run entirely from the tray instead.
I've tried using both nssm and Task Scheduler to try and achieve this effect but the client doesn't start.

It's giving you a window because Windows has switched to a new "Terminal" and things are a bit different.
See the Windows installation instructions for a description of host to use conhost.exe to make the Terminal window go away. I'll remove the console window entirely in the next release.

To use nssm, you need to pass USEGUI=false as an environment variable. This will disable the system tray and allow the app to run purely in the background as a system service.

Did you have any questions?


[testing] when running interactive bail out quick on error

Scope & Purpose
bypass all report logic and hot exit if in interactive mode and SUT is not healthy anymore.

Unrelated errors in Jenkins.


fix ReferenceError

per #2

This fixes the first error, but now we're not passing the _rev or something correctly? Getting a 409 from the put:
➜  couchdb-role-switcher git:(main) ✗ ROLE=foo COUCH_URL=https://medic:password@192-168-68-26.my.local-ip.co:8443 node .
Found 16 total users.

Error!: 409 - {"error":"conflict","reason":"Document update conflict."}

See stack trace below for details.

StatusCodeError: 409 - {"error":"conflict","reason":"Document update conflict."}
    at new StatusCodeError (/home/mrjones/Documents/MedicMobile/couchdb-role-switcher/node_modules/request-promise-core/lib/errors.js:32:15)
    at Request.plumbing.callback (/home/mrjones/Documents/MedicMobile/couchdb-role-switcher/node_modules/request-promise-core/lib/plumbing.js:104:33)
    at Request.RP$callback [as _callback] (/home/mrjones/Documents/MedicMobile/couchdb-role-switcher/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at Request.self.callback (/home/mrjones/Documents/MedicMobile/couchdb-role-switcher/node_modules/request/request.js:185:22)
    at Request.emit (events.js:196:13)
    at Request.<anonymous> (/home/mrjones/Documents/MedicMobile/couchdb-role-switcher/node_modules/request/request.js:1154:10)
    at Request.emit (events.js:196:13)
    at IncomingMessage.<anonymous> (/home/mrjones/Documents/MedicMobile/couchdb-role-switcher/node_modules/request/request.js:1076:12)
    at Object.onceWrapper (events.js:284:20)
    at IncomingMessage.emit (events.js:201:15)

I'll work on this more soon!


Ie 11 Image loading Issues outside the viewport

Hi @tuupola ,
I am using currently the v1 version of your plugin and on internet explorer images that  are not in the viewport after page scroll they are not loaded, just the placeholder image is displayed. (Initial images in the viewport are properly loaded.)
Issue encountered just on the internet explorer, on other browsers everything works properly.
If a resize the browser they start to appear.
Have someone else encountered this problem, or do you have some kind of workaround for this?
I can send you demo page as well, where the problem appears.
Thanks.

This has been fixed via #417.


Readme typos and structure

Found some typos and duplicated camps and the structure could also some restructuring.
API could also use a documentation.

be free to open PR about those changes! :)


Node 16 is deprecated for GitHub Actions

Using the current version (v2) of this action in GitHub workflows will result in a warning message from GitHub.
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-tools/yaml-outputs@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
This is a helpful action, and it would be great to continue using it while keeping the workflow output clean and uncluttered with non-actionable messages.

Upgrading to Node 20 will need to happen by May 13, 2024. See this announcement.
I have updated this repo to work with Node 20 and conform to the latest type-script GitHub Action Template covered under this PR #27. Hopefully the maintainers of this project will accept it.

Merged! Thanks @spkane for opening the issue and thanks @bcramer-c1 for the contribution.


Add optional list for .ignore files

Feature Request
How about adding an option to pass extra list of .*ignore files to install command, to get more flexibility to end user? Something like:
xdpm install --ignore-files ".gitignore, .xdignore, .npmignore"

Now it's hardcoded value here https://github.com/AdobeXD/xdpm/blob/master/commands/install.js#L83
Use case
I've added main.js file to .gitignore, because it's not expected for me to have a git diff after each new build. As result I can't use xdpm to automate my build process.
I'm ready to implement this feature and create a PR, if there are no objections

Closed with #40


feat(included): generate new image with version 10.11.0

add the cypress/included:10.11.0 . This also bumps the base docker image to node 16.17.1 and uses chrome 106, FF 105, and Edge

Wait, why did we bump the node version? We should match the electron node version. See https://github.com/cypress-io/cypress/blob/develop/.node-version

according to the guide we are supposed to bump it. Is that not actually the case?

Important ⚠ please use cypress/browsers Docker image with the latest Node version matching the major version of Node included with Cypress. For example, if Cypress is shipping 16.5.0 and the latest 16.x is 16.14.0, ship the included image with Node 16.14.0.

I think we should be OK. Internally we have been on 16.16.0 for a bit over a month with the electron upgrade, but have been shipping included with 16.14.2

@AtofStryker we need to match the shipped Cypress version when we create the image that goes with the release. I'm not sure if this repo doc is 1:1 with the binary release vs just how to create/manage images in the repo.

@AtofStryker we need to match the shipped Cypress version when we create the image that goes with the release. I'm not sure if this repo doc is 1:1 with the binary release vs just how to create/manage images in the repo.

OK ill get it updated!


Save your work

The Text-Fabric browser should save the input fields in a file, so that you can resume working where you left off

Done. Available in next release.