[SPRINT] Brainstorm DESC Baryon pasting projects details

[Brainstorm DESC Baryon pasting projects details]
[This sprint is dedicated to discuss the specific DESC related baryon-pasting projects we want to propose.]
Contacts: @marina-ricci @ethlau
Day/Time: Anytime on Mon, Tues or Wed.
Main communication channel: TBD
GitHub repo: TBD
Goals and deliverable
[The goal is to come up with a clear list of projects (defining if it should be DESC projects or not) and action items.]
Resources and skills needed
[Interest in the baryon pasting application.]
Detailed description
[add additional details  about the project]

Thank you for setting up the sprint! I prefer sometime between 8am - 11am ET / 2pm - 5pm CEST / 9pm - 12pm JST. I won't be available on Monday as I'll join BTK sprint, but Tuesday and Wednesday work for me.

2pm - 5pm CEST works for me generally on either day.

Thanks Marina for setting this up! I can do 2-3pm CEST on 10/26 (Tuesday) and 2-4:30pm CEST on 10/27 (Wednesday).

I am not available 3-4pm CEST / 9-10am EDT / 10-11pm JST on both Tuesday and Wednesday.


Get eval results from metadata

Fixes #596
No idea how to elegantly pass the SyntaxNode all the way down to the role, and I’m not super interested in figuring that out, it’s your call how to implement that.

Codecov Report
Attention: Patch coverage is 89.47368% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 80.98%. Comparing base (af2d197) to head (6d8447d).
Report is 7 commits behind head on master.

Files
Patch %
Lines

myst_nb/core/execute/base.py
87.50%
1 Missing :warning:

myst_nb/core/execute/inline.py
75.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #597      +/-   ##
==========================================
+ Coverage   80.97%   80.98%   +0.01%
==========================================
  Files          30       30
  Lines        2702     2714      +12
==========================================
+ Hits         2188     2198      +10
- Misses        514      516       +2

Flag
Coverage Δ

pytests
80.98% <89.47%> (+0.01%)
:arrow_up:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@agoose77 is there a way this can make it into this week’s release?

Hi @agoose77, would be great if you’d take a look!

I will hold this for now; we need to rectify the different ways that myst-nb and jupyterlab-myst perform caching of output expressions.

This just uses the user expression result that’s already stored in the metadata. It doesn’t touch how it’s being stored.
That doesn’t seem to have a potential for problems, or am I missing something?

This just uses the user expression result that’s already stored in the metadata. It doesn’t touch how it’s being stored.
That doesn’t seem to have a potential for problems, or am I missing something?

My initial concerns were around the way that execution should be handled. But your choice of wording has helped me to disambiguate the two cases; reading from a notebook when execution is disabled is something that we can (and should) to. I'll revisit this PR shortly (probably next week).

Hi, it’s been a month! Would be great if you could take a look here

Thanks @flying-sheep for your continued patience. I want to add support for inline-expressions in jupyter-cache as well, if we're going to get this one in. That way, all of our execution modes will support expressions. I'll circle back once the myst-nb release / JB cycle is done

Thanks for the update. I’d say merging this as-is would probably already add value, as it’s a tiny change with big effects.
Do you know what adding support for jupyter-cache would entail?

ping

@flying-sheep I know that you've already committed a fair number of cycles to this and other PRs in the stack. Thanks for your on-going patience.
I have clarified my qualms about merging this. I'd like to propose a change -- can you introduce a new executor class that subclasses the base executor, and move the expressions logic there? The intention is that other executors that don't support user expressions like direct should not mix cached expressions and fresh code-cell outputs.

All done.

I have clarified my qualms about merging this.

Yes, and then you said

My initial concerns were around the way that execution should be handled. But your choice of wording has helped me to disambiguate the two cases; reading from a notebook when execution is disabled is something that we can (and should) to.

So as far as I know, there are none left. If there are any left, please give me a list of all actionable suggestions you have.


Update for NPE 5  (WIP)

Update voor NPE 5

uses local package (Types)

Guess supersedes #1

@onovotny I think I gonna merge this, as the master is even not compiling. OK with you?

We can get a pipeline yaml setup for this

Do you mean we should setup appveyor?

I haven't built out the script yet, but this one is wired up to Pipelines:
https://github.com/NuGetPackageExplorer/Extensions.IlSpy/blob/master/azure-pipelines.yml


ROX-16953: Add additional debug and metrics endpoints

Checklist (N/A)

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

Testing Performed
go run cmd/scanner/main.go -certs ~/tmp/scanner-tls

And checks:
Pprof is secure and works:
% curl -k --fail --silent --show-error https://localhost:9095/debug/pprof -q | wc -l
45
% curl -k --fail --silent --show-error http://localhost:9095/debug/pprof -q | wc -l
curl: (22) The requested URL returned error: 400
0

It's not offered by the gRPC endpoint, and vice-versa:
% curl -k --fail --silent --show-error https://localhost:8443/debug/pprof -q | wc -l
curl: (22) The requested URL returned error: 415
0
% curl -k --fail --silent --show-error https://localhost:9095/v4.indexer -q | wc -l
curl: (22) The requested URL returned error: 404

Metrics works on non-http (needs a flag to enable HTTPS:
https://github.com/stackrox/stackrox/blob/f602abb270fdd02d6186472f794ae1b329367903/pkg/env/metrics.go#L26:
Output:
% curl -k --fail --silent --show-error https://localhost:9090/metrics -q | wc -l
curl: (35) OpenSSL/3.0.9: error:0A00010B:SSL routines::wrong version number
0
% curl --fail --silent --show-error http://localhost:9090/metrics -q | wc -l
218

/retest-required


Make e2e test working locally.

It would be nice to merge firstly https://github.com/tektoncd/results/pull/274
Signed-off-by: Oleksandr Andriienko<EMAIL_ADDRESS>

/close


Add github actions to run Rspec

Do you mind adding a description on this PR?
Do you know why github actions are not running on this PR?
I think we should enable github actions for this repo.

Github actions are enabled. maybe you have to force push the branch to let it work

I'm not sure, but we can try. Can you merge it?


attr function sets wrong value

Hi, I was implementing a drag and drop system with Raphael and noticed the attr-function setting wrong values. Since no one on SO could find a bug I was wondering if this is a Raphael.js bug. Here is the corresponding StackOverflow question http://stackoverflow.com/questions/32738491/raphael-js-attr-function-sets-wrong-value/32743655?noredirect=1#comment53329813_32743655 and a fiddle: http://jsfiddle.net/6ozsfdaf/

This may be a bug with the translation matrix calculations of Raphael. You can avoid the situation if you add an epsilon to both this.original_x and this.original_y. The problem seems to disappear if this.original_x and this.original_y are not exactly the same as the starting coordinates. Check out: http://jsfiddle.net/6ozsfdaf/13/

Found the problem. In Raphael, Raphael.parseTransformString()'s output is cached and reused. In your move() method, you modify the output of Raphael.parseTransformString(), and Raphael tries to use your modified array when you supply it with the same string. This happens when the first drag() event is registered. You ask it to parse the current place, and then update the output array of arrays with the new location. And then, way later, when this.up() is called, you supply the Raphael.parseTransformString() with the same string. Raphael then uses your modified array of arrays. This is the fixed fiddle: http://jsfiddle.net/6ozsfdaf/16/
And here is the code (use a new array of arrays to transform when moved each time):
this.move = function(dx, dy) {
var ts = [];
ts.push(new Array('t'));
ts[0][1] = this.original_x + dx;
ts[0][2] = this.original_y + dy;
this.attr({transform: ts.toString()});
};
This can also be fixed if Raphael.parseTransformString() always returned a copy of the original result.

Cool, thanks!


fix(node): Support passing "0" as port

Hello,
First of all, thank you very much for creating and maintaining this library, very exciting.
I have been playing with it today and I find the Node API to be great. Looking forward to some more extensive docs, but the source is pretty clear and I was able to figure out the usage.
The change I am proposing here is to support passing a zero (0) as a port to the server listen method. Since I will be instantiating multiple vite processes, I don't really care about the port, which is why I want Node to choose one at will. Usually, you can just pass a zero, and Node will select a random available port. However, since vite stores the exact port that was passed through options, it later fails because it tries to use 0 instead of an actual port resolved by Node.
This simple change should fix that, and from what I can tell, it should not be a breaking change.
Open to the feedback, of course, thanks!

I would prefer listener instead of listenResult

Agreed, I have implemented the change, thanks for the feedback.


Improved makefile

This PR improves the makefile. It adds the following functionality:

Clean and readable makefile layout, easily extendable
Support for compiling .c, .m, .cc, .cxx, .cpp and .mm files
Automatic dependency management

This means that make now detects changes in included header files and automatically recompiles the source files as needed

Support for running the compiled executable with make -- run args, where args get passed down to the executable

The -- is needed so that args that begin with -- aren't parsed as arguments for make

Support for make for distribution with make dist

Compiles cleanly with extra release flags
Codesigns binary with a codesigning certificate (can be set in line 5, defaults to "chunkwm-cert" as that is what I used for testing)
Creates a tarball with the signed binary and additional files (e.g. LICENSE.txt)
Calculates the SHA-256 checksum of the tarball

Support for manually cleaning the dependency, object and build files with make clean

I figured this might help, had a basic version of this for another project already so it wasn't all that much work.

I appreciate the effort, but I am probably gonna switch to a unity build for the core part of chunkwm.
A complete rebuild takes approximately 0.8seconds this way.
An optimizied build finishes in 1second.

Alright, closing this one then. Feel free to take whatever parts you think are useful.
Didn't even think about unity builds, but for a project this size it probably makes sense as long as you avoid some preprocessor shenanigans.


Background blocked out when using module (Yenders Scene Actors)

I have disabled every module and found that Dorako-UI is causing a conflict with Yenders Scene Actors module. Further troubleshooting of the module shows that the setting the Application Theme in the Dorako UI to CRB Inspired (dark) is the only setting that places a giant greyish box over the background as shown in the images I am posting. I just wanted to make you aware because I love the Dorako UI and the dark theme is by far my favorite. Unfortunately I can not use it at this time due to it hiding the background when scene actors are enabled.

That's a cool module, I might try that for next session.
Fixed for next release:

That is awesome and quick turn around. You all rock! Looking forward to the next release!


SIGGRAPH 2023 Paper Code

Code for proper benchmarking. Now we do test-time optimization for the eval cameras for both (1) the poses and (2) appearance codes.
Here are some results on the nerfstudio plane dataset. "pose", followed by "app"earance optimization works the best.

That's substantial improvement, bravo!

@ethanweber What's the current status for this? It would help a lot for researchers that are using nerfacto as a baseline method.

We are closing this PR and moving the code to the branch here with a corresponding tag here. We don't think these changes should be merged into the main branch, as described in the PR and tag. However, more polished contributions are welcome if a standardized way to evaluate methods is implemented in Nerfstudio. We used this branch to demonstrate a checkpoint of progress and write the paper for SIGGRAPH 2023.
Hopefully, this clarifies the timeline @MartinEthier.


Do connectivity check when candidate is added

When trickle is enabled do a connectivity check everytime a candidate
is added. Because we have a new candidate there is a chance we could
have a success this time.

Codecov Report

Merging #87 into master will increase coverage by 0.31%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
+ Coverage   75.56%   75.87%   +0.31%
==========================================
  Files          22       22
  Lines        1678     1683       +5
==========================================
+ Hits         1268     1277       +9
+ Misses        290      285       -5
- Partials      120      121       +1

Impacted Files
Coverage Δ

agent.go
76.44% <100%> (+0.56%)
:arrow_up:

selection.go
72.83% <0%> (+1.23%)
:arrow_up:

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 775bf98...7a3c082. Read the comment docs.


Update README.md

Error:
Type mismatch: cannot convert from Map<String, PushReceipt> to List< PushReceipt >

Original Code:
List receipts = response.getReceipts();

Change Code:
Map<String, PushReceipt> receipts = response.getReceipts();

Error message of original code

After modification

Message sent to app successfully

Thank you @Word-Word !


[bug]:

Is there an existing issue for this?

[X] I have searched the existing issues

OS
macOS
GPU
mps
VRAM
No response
What version did you experience this issue on?
latest version
What happened?
The auto-installation is finished, but when I open http://<IP_ADDRESS>:9090/, the browser shows "{hello: clash}" on the page. It doesn't show the dashboard correctly
Screenshots
No response
Additional context
No response
Contact Details
<EMAIL_ADDRESS>

could you please provide more details / screenshots? which version is this?


Auto-refresh of Insight Widgets

SQL Operations Studio Version:
0.26.7

Steps to Reproduce:
Currently - create new insight widget, manually click refresh to refresh the widget
could be beneficial to have configurable period where all insight widgets for the current managed DB/Server to be automatically re-ran returning a new set of results, this would make live statistics monitor able in graph format without remembering to click refresh periodically
(Apologies if this already exists - but can find no option/configuration to enable)

For reference existing Insight widget configuration:
   {
        "name": "Active Sessions",
        "gridItemConfig": {
            "sizex": 2,
            "sizey": 1,
            "col": 2,
            "row": 2
        },
        "widget": {
            "insights-widget": {
                "type": {
                    "count": {
                        "dataDirection": "vertical",
                        "dataType": "number",
                        "legendPosition": "none",
                        "labelFirstColumn": false,
                        "columnsAsLabels": false
                    }
                },
                "queryFile": "/Users/mark.jones/Documents/activesession.sql"
            }
        }

}


Finish #1 Sparkline directions PR

Finishes #1

Renames LTR/RTL to LeftToRight and RightToLeft
Adds tests
rebases the changes on the ~260 odd changes since this PR was originally cut.

I'm unsure how exactly to update PR #1 (which is a copy of another user's fork that is a PR against tui-rs). I didn't find an obvious way to do this using git or github, so went with cutting a branch in my fork and doing a new PR from there. If I've missed something obvious, please let me know. I know that it's fairly easy to do when you own the repo and the original requester marks the PR as updatable by maintainers, but this has several edge cases on top.

I think this is great!

Thanks! :)


Added Existence Simulator Desktop Edition

Adds a link to Existence Simulator Desktop Edition to the homepage to continue support for the franshise.

Add https:// infront of the link. Else it's a local link thing


[Question]: use a vhdx into docker container

Is your question not already answered in the FAQ?

[X] I made sure the question is not listed in the FAQ.

Is this a general question and not a technical issue?

[X] I am sure my question is not about a technical issue.

Question
I have been able to use a new W11 installation into a container. That's great.
I would like to use a preconfigured Windows image into a docker container. Is it possible?
I tried with a vhdx or a iso files but without success.
As far as my understanding, this repository does not work for this puspose. Am I correct?
Is there any way to achieve that target? What I need is apreconfigured windows machine to instantiate as many times as needed.
Thanks.

Hi,
Yes, you install your Windows, your applications, etc. In the end, you have a windows.base file. If you create a second container, for example, you can use this file, and you'll have your preinstalled Windows image. I hope that's clear.

Thank you for the reply.
I did it, but porta didn't work. For example, if I want to have two
machines one on 8006 and the orther one on 8007, the second one cannot be
accessed via vnc. I also tried to recompile the whole image exposing more
ports, but in this case nothing can be accessed via vnc. Any further
suggestions?
Thank you in avance.
Il Mar 16 Lug 2024, 18:48 MikeLaMenace @.***> ha
scritto:

Hi,
Yes, you install your Windows, your applications, etc. In the end, you
have a windows.base file. If you create a second container, for example,
you can use this file, and you'll have your preinstalled Windows image. I
hope that's clear.
—
Reply to this email directly, view it on GitHub
https://github.com/dockur/windows/issues/651#issuecomment-2231385339,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ4NMRBBA4Z2QUFFH3AOD33ZMVFE5AVCNFSM6AAAAABK6CGWESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZRGM4DKMZTHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Did you create two Docker Compose files then?
Exemple >> https://www.borninthe80s.fr/2024/07/17/poc-fournir-des-environnements-windows-sur-des-hotes-linux-via-docker/

Ok, I found the problem of the ports. My fault in configuration. It works.
Sorry.
What is not working now is the image created from the configured windows
container.
What I have done is create the image from already configured container:
docker commit <container_id> custom-windows-image
Then I put that image reference into the compose file to create new
containers like:
services:
windows:
image:  custom-windows-image:latest
container_name: windows-node1
...
windows-2:
image: custom-windows-image:latest
container_name: windows-node2
...
But starting the containers: docker-compose up -d
Windows is downloaded and installed from 0 and the already configured image
seems to be not used at all.
Where is my mistake? :)
Thanks.
Il giorno mer 17 lug 2024 alle ore 10:49 Marco Filippeschi <
@.***> ha scritto:

Great link.
That script will be useful, for sure.
Thank you very much!
But I still have some questions, if you do not mind. :)

my purpose is to use an already existing windows image (already
configured) to "clone" the other containers, but the problem is exposed
ports. If I use the image created from a container obtained from a
docker/windows image, it seems to work only the port used in the first
creation process of the container (the one started from initial
docker/windows installation).
the script is useful to have a line to follow, but my use case is
clone/create windows containers starting from the one already configured
once needed. For example:
a) I have docker container running W11 configured with some SWs running
and settings (it uses 8006 port for vnc, it uses user1 and the machine name
is windows1)
b) I would create an image from that, to be used just in case to create a
new container (let's say windows2, with user2 and port 8007)

I am having trouble doing that.
Thank you in advance for eventual further support.
Il giorno mer 17 lug 2024 alle ore 01:44 MikeLaMenace <
@.***> ha scritto:

Did you create two Docker Compose files then?
Exemple >>
https://www.borninthe80s.fr/2024/07/17/poc-fournir-des-environnements-windows-sur-des-hotes-linux-via-docker/
—
Reply to this email directly, view it on GitHub
https://github.com/dockur/windows/issues/651#issuecomment-2232001508,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ4NMRDGYZL3UIMJADG7573ZMWV67AVCNFSM6AAAAABK6CGWESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZSGAYDCNJQHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

In my opinion, you should install Windows, and then retrieve the data.img that you will use as the "source". Next, create your Docker Compose files, but before starting, copy your data.img into the directory. You'll see that the OS is already installed.

Ok, let's say I have a vhdx file containing windows data.
How should I handle it? Should I create a new image to be used in the
docker-compose file or can it be handled directly by the docker-compose
file?
How? :)
Thanks.
Il giorno mer 17 lug 2024 alle ore 12:09 MikeLaMenace <
@.***> ha scritto:

In my opinion, you should install Windows, and then retrieve the data.img
that you will use as the "source". Next, create your Docker Compose files,
but before starting, copy your data.img into the directory. You'll see that
the OS is already installed.
—
Reply to this email directly, view it on GitHub
https://github.com/dockur/windows/issues/651#issuecomment-2232937158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJ4NMRA6W54R44ERUBGNR53ZMY7ERAVCNFSM6AAAAABK6CGWESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZSHEZTOMJVHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I don't know about that. "At worst," just reinstall directly in the correct format. I don't know the format used by Dockurr for its .img. Maybe it's the native QEmu format... If necessary, try converting the VHDX to .img via this guide. That's what I would try otherwise.

this good ?

Actually I am not able to make it works.
I am trying the last option I was thinking about: copy files from storage folder of container (data.img, windows.base, windows.boot, ...) in order to use them in new container creation process (I do not know how to do that yet). I hope those files clone exactly the configured image in a new container without installing Windows from zero as dockurr/windows project does.
I am spending to much time looking for a solution to my task, but I am still not finding it. :(
I cannot understand how to use a custom image instead of standard windows installation one.
I suppose the reference in the readme file is related to a different image for installation...
... use a local file instead, by binding it in your compose file in this way:
volumes:
  - /home/user/example.iso:/custom.iso

At the end I have been able to use a previous container windows image using files from /storage folder of container.
The files data.img, windows.base, etc... copied in a new docker image, can be used to create containers all with the same windows image.
This solved my needs, but I am afraid some binding are lost because I cannot see anymore the content of oem folder in the container directly in the oem folder on windows, mounted as volume like:
volumes:       - ./scripts:/oem
I can see the scripts folder content in the oem folder of the container, but nor into the oem folder in Windows.
Is there anyway to restore the volume mounting?


Motion sensor automation no longer working since 1.9.3 upgrade

Describe The Bug:

I had previously working Home app automation setup which was triggered by one of my Simplisafe motion detectors, specifically the one in the garage. However, it stopped working once I upgraded to the latest 1.9.3 plugin.
To Reproduce:

Occurs each time the automation runs, i.e. each time the motion detector triggers an event
Expected behavior:

Normally when the automation trigger I had it setup to turn on a couple of my garage lights.
Environment:

Plugin version:
1.9.3
Node.js Version:
14.7.5
NPM Version:
6.14.14
Homebridge Version:
1.4.0
Operating System:
Docker running on Synology NAS

Homebridge Config:

{
    "bridge": {
        "name": "Homebridge 494A",
        "username": "0E:6E:B4:3C:49:4A",
        "port": 52532,
        "pin": "031-45-154"
    },
    "accessories": [],
    "platforms": [
        {
            "name": "Config",
            "port": 8581,
            "auth": "form",
            "theme": "auto",
            "tempUnits": "f",
            "lang": "auto",
            "platform": "config"
        },
        {
            "name": "Nest",
            "access_token": "xxx",
            "googleAuth": {
                "issueToken": " xxx",
                "cookies": "xxx"
            },
            "platform": "Nest"
        },
        {
            "refreshToken": "xxx",
            "options": {
                "ffmpegCodec": "libx264",
                "alertCheckRate": 10,
                "alertCooldownRate": 180,
                "importantOnly": true,
                "motionDetection": true,
                "streamingSwitch": true,
                "announcementsSwitch": true,
                "audioSwitch": true,
                "fieldTest": false
            },
            "platform": "Nest-cam"
        },
        {
            "name": "Home Alarm",
            "cameras": true,
            "debug": true,
            "sensorRefresh": 15,
            "persistAccessories": true,
            "resetSimpliSafeId": false,
            "cameraOptions": {
                "enableHwaccelRpi": false
            },
            "platform": "homebridge-simplisafe3.SimpliSafe 3"
        }
    ]
}

Screenshots:

Logs:

Link to logs
Paste Homebridge Logs here

[2/18/2022, 8:53:15 PM] [Homebridge UI] Changes to config.json saved.
[2/18/2022, 8:53:22 PM] [Homebridge UI] Homebridge restart request received
[2/18/2022, 8:53:23 PM] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[2/18/2022, 8:53:23 PM] [Homebridge UI] Sending SIGTERM to Homebridge
[2/18/2022, 8:53:23 PM] Got SIGTERM, shutting down Homebridge...
[2/18/2022, 8:53:28 PM] [HB Supervisor] Homebridge Process Ended.
Setup Payload:
X-HM://0023ISYWY8INV
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

[2/18/2022, 8:53:45 PM] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge 494A) is running on port 52532.
[2/18/2022, 8:53:45 PM] [Home Alarm] SimpliSafe credentials refresh was successful
[2/18/2022, 8:53:45 PM] [Home Alarm] Discovering devices from SimpliSafe
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Dining Room' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"013228d0","type":4,"name":"Dining Room","deviceGroupID":0,"status":{},"setting":{"off":0,"home":0,"home2":0,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Motion Sensor 'Dining Room' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Nook' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"01328e6e","type":4,"name":"Nook","deviceGroupID":0,"status":{},"setting":{"off":0,"home":0,"home2":0,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Motion Sensor 'Nook' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Deck' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0144c326","type":5,"status":{"triggered":false},"name":"Deck","deviceGroupID":0,"setting":{"off":0,"home":1,"home2":1,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Dining Room' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0144df11","type":5,"status":{"triggered":false},"name":"Dining Room","deviceGroupID":0,"setting":{"off":0,"home":1,"home2":1,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Front Door' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0144df03","type":5,"status":{"triggered":false},"name":"Front Door","deviceGroupID":0,"setting":{"off":0,"home":1,"home2":1,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Garage' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0144c37c","type":5,"status":{"triggered":false},"name":"Garage","deviceGroupID":0,"setting":{"off":0,"home":1,"home2":1,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Kitchen' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0144df7c","type":5,"status":{"triggered":false},"name":"Kitchen","deviceGroupID":0,"setting":{"off":0,"home":1,"home2":1,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Nook' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0144c481","type":5,"status":{"triggered":false},"name":"Nook","deviceGroupID":0,"setting":{"off":0,"home":1,"home2":1,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Patio Door' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0144c316","type":5,"status":{"triggered":false},"name":"Patio Door","deviceGroupID":0,"setting":{"off":0,"home":1,"home2":1,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Side Door' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0144c38e","type":5,"status":{"triggered":false},"name":"Side Door","deviceGroupID":0,"setting":{"off":0,"home":1,"home2":1,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered sensor 'Garage' from SimpliSafe: {"flags":{"offline":false,"lowBattery":false,"swingerShutdown":false},"serial":"0185f4c1","type":4,"status":{},"name":"Garage","deviceGroupID":0,"setting":{"off":2,"home":2,"home2":0,"away":1,"away2":1,"instantTrigger":false}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Discovered camera 'Living Room' from SimpliSafe: {"staleSettingsTypes":[],"upgradeWhitelisted":false,"model":"SS003","uuid":"91644c02fc1992ac72499c5c203c672b","uid":4524869,"sid":4798919,"cameraSettings":{"spotlight":{"enableColorNightMode":false},"videoFlip":{"enable":false,"verticalFlip":false,"horizontalFlip":false},"alarmState":{"recordOnAlarm":true,"recordOnCount":true,"spotlightFlashOnAlarm":true,"sirenOnAlarm":true},"cameraName":"Living Room","pictureQuality":"1080p","nightVision":"auto","statusLight":"on","micSensitivity":100,"micEnable":true,"speakerVolume":75,"motionSensitivity":50,"shutterHome":"closedAlarmOnly","shutterAway":"open","shutterOff":"closedAlarmOnly","wifiSsid":"betabob","canStream":false,"canRecord":false,"pirEnable":true,"vaEnable":true,"notificationsEnable":true,"enableDoorbellNotification":true,"doorbellChimeVolume":"off","privacyEnable":false,"hdr":true,"vaZoningEnable":false,"vaZoningRows":0,"vaZoningCols":0,"vaZoningMask":[],"maxDigitalZoom":10,"supportedResolutions":["480p","720p","1080p"],"admin":{"tinyYolo":{"numFramesToAnalyze":5,"confidenceThreshold":0.9,"positiveFramesThreshold":0.5},"powerControl":{"disabled":false},"IRLED":0,"pirSens":0,"statusLEDState":1,"lux":"lowLux","motionDetectionEnabled":false,"motionThresholdZero":0,"motionThresholdOne":10000,"levelChangeDelayZero":30,"levelChangeDelayOne":10,"audioDetectionEnabled":false,"audioChannelNum":2,"audioSampleRate":16000,"audioChunkBytes":2048,"audioSampleFormat":3,"audioSensitivity":50,"audioThreshold":50,"audioDirection":0,"bitRate":284,"longPress":2000,"kframe":1,"gopLength":40,"idr":1,"fps":20,"firmwareVersion":"<IP_ADDRESS>","netConfigVersion":"","camAgentVersion":"","lastLogin":1645202028,"lastLogout":1645202027,"pirSampleRateMs":800,"pirHysteresisHigh":2,"pirHysteresisLow":10,"pirFilterCoefficient":1,"logEnabled":true,"logLevel":3,"logQDepth":20,"firmwareGroup":"public","irOpenThreshold":445,"irCloseThreshold":840,"irOpenDelay":3,"irCloseDelay":3,"irThreshold1x":388,"irThreshold2x":335,"irThreshold3x":260,"dbm":0,"vmUse":160248,"resSet":17952,"uptime":1158565.59,"wifiDisconnects":0,"wifiDriverReloads":0,"statsPeriod":3600000,"sarlaccDebugLogTypes":0,"odProcessingFps":8,"odObjectMinWidthPercent":6,"odObjectMinHeightPercent":24,"odEnableObjectDetection":true,"odClassificationMask":2,"odClassificationConfidenceThreshold":0.95,"odEnableOverlay":false,"odAnalyticsLib":2,"odSensitivity":85,"odEventObjectMask":2,"odLuxThreshold":445,"odLuxHysteresisHigh":4,"odLuxHysteresisLow":4,"odLuxSamplingFrequency":30,"odFGExtractorMode":2,"odVideoScaleFactor":1,"odSceneType":1,"odCameraView":3,"odCameraFOV":2,"odBackgroundLearnStationary":true,"odBackgroundLearnStationarySpeed":15,"odClassifierQualityProfile":1,"odEnableVideoAnalyticsWhileStreaming":false,"wlanMac":"d4:9c:dd:78:a4:5d","region":"us-east-1","enableWifiAnalyticsLib":false,"ivLicense":""},"pirLevel":"medium","odLevel":"medium"},"cameraStatus":{"firmwareVersion":"<IP_ADDRESS>","netConfigVersion":"","camAgentVersion":"","lastLogin":1645202028,"lastLogout":1645202027,"wlanMac":"d4:9c:dd:78:a4:5d","fwDownloadVersion":"","fwDownloadPercentage":0,"recovered":false,"recoveredFromVersion":"","batteryPercentage":0,"_id":"60fb5ca34de2bb0b74d26f8f","initErrors":[],"speedTestTokenCreated":1643108551},"__v":0,"supportedFeatures":{"providers":{"webrtc":"none","recording":"simplisafe","live":"simplisafe"},"audioEncodings":["speex"],"resolutions":["480p","720p","1080p"],"_id":"60fb5ca34de2bb0b74d26f90","pir":true,"videoAnalytics":false,"privacyShutter":true,"microphone":true,"fullDuplexAudio":false,"wired":true,"battery":false,"networkSpeedTest":false,"speaker":true,"spotlight":false,"colorNightMode":false,"videoFlip":false,"doorbell":false,"videoAnalyticsZones":false,"pairedToBasestation":false,"siren":false,"videoEncoding":"h264","aspectRatio":"16:9"},"subscription":{"enabled":true,"freeTrialActive":false,"freeTrialUsed":false,"freeTrialEnds":0,"freeTrialExpires":0,"planSku":"SSVM1","price":0,"expires":1629764387,"storageDays":30,"trialUsed":false,"trialActive":false,"trialExpires":0},"status":"online","currentState":{"idle":true,"liveStreaming":false,"recording":false,"otaDownloading":false,"otaFlashing":false,"batteryCharging":false,"ts":1645246427}}
[2/18/2022, 8:53:49 PM] [Home Alarm] Detected running in docker, initializing with docker-bundled ffmpeg
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'SimpliSafe 3' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing alarm state
[2/18/2022, 8:53:49 PM] [Home Alarm] Cached accessory {32cc32ea-1e3c-4edc-ad44-efc509fc2604} not matched to a SimpliSafe device
[2/18/2022, 8:53:49 PM] [Home Alarm] Cached accessory {ee312321-5e16-40d9-a283-ccf193fb8f0c} not matched to a SimpliSafe device
[2/18/2022, 8:53:49 PM] [Home Alarm] Cached accessory {99413bd4-f70e-42d5-bd21-2ec87d51fd78} not matched to a SimpliSafe device
[2/18/2022, 8:53:49 PM] [Home Alarm] Cached accessory {a996bcaa-0898-43c0-87d3-305cd2bd06db} not matched to a SimpliSafe device
[2/18/2022, 8:53:49 PM] [Home Alarm] Cached accessory {9187ae09-93e1-48bb-a03d-30fb385d8b38} not matched to a SimpliSafe device
[2/18/2022, 8:53:49 PM] [Home Alarm] Cached accessory {bf775cf0-49c5-416f-821e-00959e655cf8} not matched to a SimpliSafe device
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Deck' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing sensor state
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Dining Room' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing sensor state
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Front Door' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing sensor state
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Garage' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing sensor state
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Kitchen' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing sensor state
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Nook' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing sensor state
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Patio Door' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing sensor state
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Side Door' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Refreshing sensor state
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Living Room' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Initializing SS device 'Garage' with cached accessory
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current open, battery state for Deck: false, false
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current open, battery state for Dining Room: false, false
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current open, battery state for Front Door: false, false
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current open, battery state for Garage: false, false
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current open, battery state for Kitchen: false, false
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current open, battery state for Nook: false, false
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current open, battery state for Patio Door: false, false
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current open, battery state for Side Door: false, false
[2/18/2022, 8:53:49 PM] [Home Alarm] Updated current state for SimpliSafe 3: OFF
[2/18/2022, 8:53:49 PM] [Home Alarm] Now listening for real time SimpliSafe events.
[2/18/2022, 8:53:50 PM] [Nest] initing thermostat (P) "Hallway Thermostat": deviceId: CCA7C10000132BFB structureId: ebb7f801-b76e-11eb-b9e8-0ac9ae7c0a36
[2/18/2022, 8:53:50 PM] [Nest] initing thermostat (P) "Family Room Thermostat": deviceId:<PHONE_NUMBER>90DD4F structureId: 3d909370-37de-11e4-bc04-22000b438db5
[2/18/2022, 8:53:50 PM] [Nest] initing home_away_sensor "Home Occupied - Home": deviceId: ebb7f801-b76e-11eb-b9e8-0ac9ae7c0a36 structureId: ebb7f801-b76e-11eb-b9e8-0ac9ae7c0a36
[2/18/2022, 8:53:50 PM] [Nest] initing home_away_sensor "Home Occupied - Percy's Place": deviceId: 3d909370-37de-11e4-bc04-22000b438db5 structureId: 3d909370-37de-11e4-bc04-22000b438db5
[2/18/2022, 8:53:50 PM] [Nest] initing temp_sensor (P) "Bedroom": deviceId: 18B430C0035AEF4B structureId: ebb7f801-b76e-11eb-b9e8-0ac9ae7c0a36
[2/18/2022, 8:53:50 PM] [Nest] initing protect "Hallway": deviceId: 18B4300041871DCD structureId: ebb7f801-b76e-11eb-b9e8-0ac9ae7c0a36
[2/18/2022, 8:53:50 PM] [Nest] initing protect "Bedroom": deviceId: 18B4300041872174 structureId: ebb7f801-b76e-11eb-b9e8-0ac9ae7c0a36
[2/18/2022, 8:53:50 PM] [Nest] initing protect "Garage": deviceId: 18B4300041870D28 structureId: ebb7f801-b76e-11eb-b9e8-0ac9ae7c0a36
[2/18/2022, 9:02:37 PM] [Home Alarm] Sensor refresh received an error from the SimpliSafe API: {
type: 'SettingsInProgress',
message: 'The Settings Requested are already being modified and cannot be accessed at this time',
code: '200',
statusCode: 409,
props: {}
}
[2/18/2022, 9:17:22 PM] [Home Alarm] Sensor refresh received an error from the SimpliSafe API: {
type: 'SettingsInProgress',
message: 'The Settings Requested are already being modified and cannot be accessed at this time',
code: '200',
statusCode: 409,
props: {}
}
[2/18/2022, 9:27:59 PM] [Homebridge UI] Starting terminal session
[2/18/2022, 9:28:39 PM] [Homebridge UI] Terminal session ended.
[2/18/2022, 9:31:22 PM] [Homebridge UI] Starting terminal session
[2/18/2022, 9:36:35 PM] [Home Alarm] Sensor refresh received an error from the SimpliSafe API: {
type: 'SettingsInProgress',
message: 'The Settings Requested are already being modified and cannot be accessed at this time',
code: '200',
statusCode: 409,
props: {}
}
[2/18/2022, 9:38:10 PM] [Home Alarm] Sensor refresh received an error from the SimpliSafe API: {
type: 'SettingsInProgress',
message: 'The Settings Requested are already being modified and cannot be accessed at this time',
code: '200',
statusCode: 409,
props: {}
}
[2/18/2022, 9:40:15 PM] [Homebridge UI] Terminal session ended.
[2/18/2022, 9:31:47 PM] Registering platform 'homebridge-config-ui-x.config'
[2/18/2022, 9:31:47 PM] ---
[2/18/2022, 9:31:47 PM] Publishing bridge accessory (name: Homebridge, publishInfo: {
username: 'CC:22:3D:E3:CE:30',
port: undefined,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: undefined
}).
HAP-NodeJS:Advertiser Preparing Advertiser for 'Homebridge CAD8' using bonjour-hap backend! +0ms
Setup Payload:
X-HM://0023ISYWYYWZQ
Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

HAP-NodeJS:EventedHTTPServer Server listening on [::]:37240 +0ms
HAP-NodeJS:Advertiser Starting to advertise 'Homebridge CAD8' using bonjour-hap backend! +47ms
[2/18/2022, 9:31:47 PM] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge) is running on port 37240.
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open:  +60s
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open:  +60s
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open:  +1m
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open:  +1m

I don't understand, I thought I used the template correctly...

Thanks, can you also send the logs from when you actually trigger the motions sensor? (Again with debug enabled)

Thanks for the quick response. Those logs were during the times that the motion sensor triggered, but what's weird is that the trigger event itself did not seem to generate any log activity. Any suggestions?

Hmm, yea. You have ‘instant alerts’ enabled for that sensor? Ie you do get a SS notification?

Yup, and I do still get the SS notifications. Let me do it again a couple of more times right now to verify that the event itself does not generate a log entry

OH wait, I maybe didn't answer your question correctly. I had "secret alerts" enabled and I am receiving SS secret notifications, but I do NOT have "instant trigger" turn on, if that's what you were referring to....but I never did even when it was working correctly. Turning instant trigger would be a problem for me as then it would sound the alarm as soon as I open the garage door.

And yeah, the triggering itself is definitely not creating log entries.

Sorry sorry, secret alerts. Ok I’m going to have to dig out the motion sensor and test (at some point)

Thanks. Btw, I run a “goodnight” automation which enables my SS alarm, and it seems ever since I upgraded to the latest plugin the Home app comes back with an “error” when I run it..though it appears the automation ran successfully. If you’re interested I can enable debugging and send you the logs for that as well.

Sure. One thing I noticed from your logs is you have some outdated devices. You can uncheck “persist accessories” and restart the plug-in (then can re-enable it) to clear those out. I would definitely backup HomeKit before doing that (look up Controller+), but wonder if that might help.
I have the same automation, no issues with it.

There’s an app called “Controller for Homekit”…is that what you’re referring to?

Yes thats the one.
And you were right, there was a silly error that broke motion sensors, its sorted out and will be in the next release.

You’re referring to my original problem or my “goodnight” issue in terms of being addressed in the next release?

The motion sensor issue

Looks like I have to upgrade to the “pro” version of the app in order to do backups

Oh, so should I just do nothing for now and wait, or still uncheck “persist accesories” ?

Unchecking ‘persist accessories’ and then restarting will remove old devices which might clarify the ‘good night’ thing. But I would backup first just in case. It’s up to you, app is well worth it imho, I have broken my HK setup many times and restoring is super easy (there are some caveats).
I suppose it’s up to you.

Okay, looks like I get a free trial of the pro version before I need to commit long term, so I’ll do that. Thanks again, will try all this out later today and report back.

Well, I went ahead and backed up my Homekit config and unchecked "persist accessories". No change to either the motion detector automation behavior nor the "goodnight" error. Will send you some logs later today for the latter.

The fix to the motion sensor was not released yet…

Okay, I ran my "goodnight" automation while in debug mode. Here's the Homebridge log:
/homebridge # DEBUG=* homebridge -D
ciao:init Loading ciao v1.1.3... +0ms
HAP-NodeJS:Advertiser Initializing HAP-NodeJS v0.10.0 ... +0ms
[2/19/2022, 4:48:28 PM] config.json (/root/.homebridge/config.json) not found.
[2/19/2022, 4:48:28 PM] ---
[2/19/2022, 4:48:30 PM] Loaded plugin<EMAIL_ADDRESS>[2/19/2022, 4:48:30 PM] Registering platform 'homebridge-config-ui-x.config'
[2/19/2022, 4:48:30 PM] ---
[2/19/2022, 4:48:30 PM] Publishing bridge accessory (name: Homebridge, publishInfo: {
username: 'CC:22:3D:E3:CE:30',
port: undefined,
pincode: '--**',
category: 2,
bind: undefined,
mdns: undefined,
addIdentifyingMaterial: true,
advertiser: undefined
}).
HAP-NodeJS:Advertiser Preparing Advertiser for 'Homebridge CAD8' using bonjour-hap backend! +0ms
Setup Payload:
X-HM://0023ISYWYYWZQ
Scan this code with your HomeKit app on your iOS device to pair with Homebridge:
Or enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘

HAP-NodeJS:EventedHTTPServer Server listening on [::]:42091 +0ms
HAP-NodeJS:Advertiser Starting to advertise 'Homebridge CAD8' using bonjour-hap backend! +52ms
[2/19/2022, 4:48:30 PM] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge) is running on port 42091.
HAP-NodeJS:EventedHTTPServer Currently 0 hap connections open:  +60s
The automation itself didn't seem to create any log entries.
And here is the tail of the normal log:
[2/19/2022, 4:47:59 PM] [Homebridge UI] Starting terminal session
[2/19/2022, 4:48:58 PM] [Home Alarm] Setting target state to HOME, 0
[2/19/2022, 4:48:58 PM] [Nest] Setting cooling threshold temperature to 25.6 °C / 78.08 °F
[2/19/2022, 4:48:58 PM] [Nest] Setting heating threshold temperature to 17.2 °C / 62.96 °F
[2/19/2022, 4:49:00 PM] [Home Alarm] Updated alarm state: {"state":"HOME","stateUpdated":1645318140,"exitDelay":0}
[2/19/2022, 4:49:04 PM] [Home Alarm] Alarm received event: HOME_ARM
[2/19/2022, 4:49:10 PM] [Nest] Setting heating threshold temperature to 18.900000000000002 °C / 66.02 °F
[2/19/2022, 4:49:10 PM] [Home Alarm] Setting target state to OFF, 3
[2/19/2022, 4:49:10 PM] [Nest] Setting cooling threshold temperature to 25.6 °C / 78.08 °F
[2/19/2022, 4:49:12 PM] [Home Alarm] Updated alarm state: {"state":"OFF","stateUpdated":1645318152,"exitDelay":0}
[2/19/2022, 4:49:16 PM] [Home Alarm] Alarm received event: ALARM_DISARM
[2/19/2022, 4:51:00 PM] [Homebridge UI] Terminal session ended.
fyi I ran my "goodnight" automation followed by my "good morning" automation.

Any idea when the next plugin version might be released?

[2/19/2022, 4:48:58 PM] [Home Alarm] Setting target state to HOME, 0
[2/19/2022, 4:49:00 PM] [Home Alarm] Updated alarm state: {"state":"HOME","stateUpdated":1645318140,"exitDelay":0}
[2/19/2022, 4:49:04 PM] [Home Alarm] Alarm received event: HOME_ARM

This looks like everything is working fine... 6 seconds later its set to off but Im guessing that was you turning it off. So all good?
I was waiting to release to make sure there wasn't another issue.

+1 on this motion sensor issue... looking forward to the update!

Just released =)

Thank you!  Glad to have these back.

Verified that my motion sensor automation is working again...thanks again @shamoon !


Issue with k8s.io/docs/tutorials/kubernetes-basics/explore/explore-interactive/

This is a...

[ ] Feature Request
[x ] Bug Report

Problem:
Left panel scrollbar does not work. I am using Firefox 60.02 on  LinuxMInt.
Proposed Solution:
Page to Update:
https://kubernetes.io/...

@scanlanp, could you please provide a screenshot?

The error is in the <section id "tutorial" where the tutorial resizer is
overlapping the scroll. Reduce the resizer width or get rid of it
altogether.
On Thu, Sep 20, 2018 at 1:51 PM, Shubheksha<EMAIL_ADDRESS>wrote:

@scanlanp https://github.com/scanlanp, could you please provide a
screenshot?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/10351#issuecomment-423154568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWdHA5NoulKq4W6JNXtiiw4E7ZoN_HKks5uc4EzgaJpZM4Wx8KL
.

--
Patrick MJ Scanlan


Add ability to configure the consent message for the splash page on the provider

upstream: https://github.com/cisco-open/terraform-provider-meraki/issues/152

closed upstream because it isn't implemented in the API, will request again once API supports it


The pull request cannot be activated because the source and/or the target branch no longer exists, or the requested refs are not branches

Hello,
I get error  while following the document: https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-almacceleratorpowerplatform-upgrade-config#updating-the-pipelines-in-azure-devops
ERROR: TF401398: The pull request cannot be activated because the source and/or the target branch no longer exists, or the requested refs are not branches

Thanks for reporting this @phecke, we have a new experience to setup ALM projects that is under the AA4PP Admin App (Model Driven App). We will update this doc to include the new experience. If you need help, please create a question under https://github.com/microsoft/coe-starter-kit/issues and wr can follow up from there.
Thanks

We should move this discussion to https://github.com/microsoft/coe-starter-kit/issues , we need more information since we were not able to reproduce the situation.


[Event Request] Codeunit 229 "Document-Print" OnBeforePrintSalesOrderOnBeforeGetSalesOrderUsage

Describe the request
Hello, would it be possible to add OnBeforePrintSalesOrderOnBeforeGetSalesOrderUsage event on PrintSalesOrder() procedure in codeunit 229 "Document-Print", like this:
    procedure PrintSalesOrder(SalesHeader: Record "Sales Header"; Usage: Option "Order Confirmation","Work Order","Pick Instruction")
    var
        ReportSelection: Record "Report Selections";
        ReportUsage: Enum "Report Selection Usage";
        IsPrinted: Boolean;
        IsHandled: Boolean;
    begin
        IsHandled := false;
        OnBeforePrintSalesOrderOnBeforeGetSalesOrderUsage(SalesHeader, Usage, IsHandled); // New event
        if IsHandled then
            exit;

        if SalesHeader."Document Type" <> SalesHeader."Document Type"::Order then
            exit;

        ReportUsage := GetSalesOrderUsage(Usage);

        SalesHeader.SetRecFilter();
        CalcSalesDisc(SalesHeader);
        OnBeforePrintSalesOrder(SalesHeader, ReportUsage.AsInteger(), IsPrinted);
        if IsPrinted then
            exit;

        ReportSelection.PrintWithDialogForCust(
            ReportUsage, SalesHeader, GuiAllowed, SalesHeader.FieldNo("Bill-to Customer No."));
    end;

    [IntegrationEvent(false, false)]
    local procedure OnBeforePrintSalesOrderOnBeforeGetSalesOrderUsage(var SalesHeader: Record "Sales Header"; Usage: Option "Order Confirmation","Work Order","Pick Instruction"; var IsHandled: Boolean) // New event
    begin
    end;

Additional context
We have cases where we need to exist PrintSalesOrder() procedure based on the Sales Header Document Type before the CalcSalesDisc() procedure. The event at the beginning of CalcSalesDisc() does not fit our needs because CalcSalesDisc() is also used in other code places where we need a standard flow of this procedure.
Internal work item: AB#504112

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 16993.


Instructions for 10-bit Butteraugli

I'm trying to use 10-bit Butteraugli on Linux.
The provided 1.0.0 final executables all complain that aomenc needs to be built with DCONFIG_TUNE_BUTTERAUGLI=1, so it doesn't seem to be enabled there.
I compiled the source .tar.gz attached to the 1.0.0 final release with DCONFIG_TUNE_BUTTERAUGLI=1, but then I get the same message that the official aomenc 3.8.0 gives me:
Stream #0:0: Video: rawvideo (Y3[11][10] / 0xA0B3359), yuv420p10le(tv, progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 745750 kb/s, 23.98 fps, 23.98 tbn
    Metadata:
      encoder         : Lavc59.37.100 rawvideo
Pass 1/2 frame    1/0    0:00               0.00 fpsStream 0: Failed to encode frame: Invalid parameter
    Only 8 bit depth images supported in tune=butteraugli mode.

I also tried the Endless_possibility_JXL_testing branch, but the result is exactly the same. Is the Butteraugli tune for 10-bit pixel formats not part of the final release anymore? Any older releases worth trying?
If I'm just doing something stupid or missing another CMake option, please provide a short hint or compile instructions in the ReadMe :)

That is correct. This is a weird behavior though.
Anyway, I don't work on aom-av1-psy anymore.


Hover doesn't always disappear after exit

Seems like sometimes the hover exit is not working as expected, as the item is still marked as if it was still being hovered.
Code to reproduce it:
fun main() = singleWindowApplication {
    LazyColumn {
        items(count = 10) { i ->
            Text(
                text = "Item number $i",
                modifier = Modifier.clickable {}
            )
        }
    }
}

GIF showing the problem where I hover the list's items and sometimes some of them keep being hovered when the mouse is not on top them:

OS: Ubuntu 20.04 & Manjaro with KDE
Compose Desktop Version: 1.0.0-beta5 (started happening since the first version that included the hovering)

Managed to reproduce on Mac, but it is really-really difficult

I have noticed that it happens much more in my Manjaro KDE installation than on Ubuntu, not sure why tho. Not sure if it's the desktop environment or there is something different in the build process (like different JDK). In any case, still happens in Ubuntu even if it's less.

I have the same problem on Windows. Reproducibility is easy:
@OptIn(ExperimentalAnimationApi::class)
fun main() = singleWindowApplication {
    val interactionSource = MutableInteractionSource()
    val isHovered by interactionSource.collectIsHoveredAsState()
    Box(Modifier.size(100.dp).background(Color.Gray).hoverable(interactionSource)) {
        if (isHovered) {
            Text("Hovered")
        }
    }
}

https://user-images.githubusercontent.com/284263/141658149-f00844e3-856b-46c7-b125-5b2b0105f176.mp4

In 1.0.0-rc4 reproduced with scrollbar an heavy lazy list:
https://user-images.githubusercontent.com/5963351/143503791-519ba86f-d053-46c3-b810-d0521f0defa8.mp4
With light lazy list it is hard to reproduce.

With rc5 the issue seems to be solved when simply hovering with the cursor, however, when hovering an item in a lazy list and then scrolling, it still sometimes ends up with a hovered line that shouldn't be.

My usecase https://github.com/JetBrains/compose-jb/issues/1324#issuecomment-968131533 behave exactly the same in latest RC5. Windows 11.

My usecase #1324 (comment) behave exactly the same in latest RC5. Windows 11.

Can you check on 0.0.0-feature-test28112021-dev491? It will be rc6 tomorrow

My usecase #1324 (comment) behave exactly the same in latest RC5. Windows 11.

Actually, I reproduced it. The issue in your snippet. It should be:
val interactionSource = remember { MutableInteractionSource() }

I really sorry, lame mistake. My non-simiplified usecase works correctly with RC5. THX.

Can you check on 0.0.0-feature-test28112021-dev491? It will be rc6 tomorrow

Does this version include https://github.com/JetBrains/androidx/pull/135?

Does this version include JetBrains/androidx#135?

Yes, it includes this fix

The hover issue when scrolling still persists but it's less common.

Can you check if this works in 1.0.0-rc12?
There was one more change regarding this issue.
On my PC it works in all tested cases.

In 1.0.0-rc12 seems to work nicely 🥳 Good job and thanks @igordmn !

It appears, it haven't completely fixed in 1.0.0. The new found cases should be fixed in 1.1.0

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


How to set subtitle area

When processing a video, I get the warning:
"No subtitle area has been set. Video will be processed in full screen. As a result, the final outcome might be suboptimal."
@backend/main.py:
ymin, ymax, xmin, xmax = self.sub_area
How do I set this area?

in backend/config.py you can set STTN_SKIP_DETECTION to False
This will auto detect subtitle area.
I believe you can also set STTN_SKIP_DETECTION= true and uncomment backend/main.py line 917 (sub_area = (ymin, ymax, xmin, xmax)) to manually set the values of subtitle area


Response to the gh-1836-demo example.

I have looked at the demo and taken that and other comments and reorganised the approach to the Mock to Mini Accumulo changes.
This pull request branch has only a few changes outlining how I will go about progressing gh-1836.
It was noted for the gh-1836-demo that as the Mini Accumulo Cluster should behave exactly as full Accumulo we shouldn't need any MiniAccumuloStore sub classes. This does indeed work but given the normal mechanism used by Gaffer to identify a store type is the class name specified in the properties files. This means the MiniAccumuloStore and SingleUseMiniAccumuloStore classes are needed for identification purposes, unless I have misunderstood something in this area.
The new MiniAccumuloStore class extends AccumuloStore with no changes to functionality.
The new SingleUseMiniAccumuloStore extends MiniAccumuloStore in exactly the same manner as SingleUseAccumuloStore extends AccumuloStore.
They are extended in this way rather than SingleUseMiniAccumuloStore extending SingleUseAccumuloStore to replicate the AccumuloStore object hierarchy.
Control of the decision whether to start a MiniAccumuloCluster, and the starting and stopping it, is handled by the new AccumuloTestClusterManager class. This takes an AccumuloProperties object in its constructor and reads it to find the store class. If it is a Mini Accumulo one it sets up and starts a MiniAccumuloCluster and updates the properties with the zookeeper details. If not it just returns.
Creation of the object is called at the beginning of a test suite, often through the @BeforeClass annotated method.
At the end of a test suite (@AfterClass) the close method is called to close and tidy away the Mini Accumulo Cluster if one has been started. The test suite will have kept the reference to the AccumuloTestClusterManager object for this purpose.
There are three tests converted from using Mock to Mini:
AccumuloStoreITs from the demo is suitably modified to use the new AccumuloTestClusterManager. This is slightly odd looking as for this test the constructors receive the properties. This prevents use of the @BeforeClass as that has to be a static method so cannot use instance attributes.
GetDataFrameOfElementsHandlerTest is a spark-accumulo test that was constructed to set up its store only from properties. This was among the tests that previously had a lot of duplicated code. They will now have an abstract superclass, AbstractPropertiesDrivenTest, to handle most of the repeating setup.
AccumuloStoreTest is an example of the most common types of unit tests. This had explicit Mock handling as part of the tests, in some cases with SingleUseMockAccumuloStore being instantiated by individual tests. This has been converted to reuse of a pair of mini accumulo clusters for all the tests.
In all the test examples above I have avoided declaration of the MiniAccumuloStore and SingleUseMiniAccumuloStore classes as far as possible, instead having any necessary Store declarations being for AccumuloStore.
Is this closer to what was expected?

Thanks @phosphorbronze50. That sounds a lot more in-tune with my thinking at least. Have you made these changes in your other pull request? And if so is it ready for a second review?

Codecov Report

Merging #2286 into develop will increase coverage by 1.64%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             develop    #2286      +/-   ##
=============================================
+ Coverage      66.15%   67.80%   +1.64%
+ Complexity      2413     2119     -294
=============================================
  Files            911      792     -119
  Lines          30431    27038    -3393
  Branches        3750     3309     -441
=============================================
- Hits           20133    18332    -1801
+ Misses          8712     7316    -1396
+ Partials        1586     1390     -196

Impacted Files
Coverage Δ
Complexity Δ

.../federatedstore/schema/FederatedViewValidator.java
86.11% <100.00%> (ø)
0.00 <0.00> (ø)

...r/bitmap/serialisation/json/BitmapJsonModules.java
0.00% <0.00%> (ø)
0.00% <0.00%> (ø%)

...binaryoperator/ReservoirLongsSketchAggregator.java
100.00% <0.00%> (ø)
2.00% <0.00%> (ø%)

...tiles/serialisation/KllFloatsSketchSerialiser.java
44.44% <0.00%> (ø)
4.00% <0.00%> (ø%)

...ap/function/aggregate/RoaringBitmapAggregator.java
100.00% <0.00%> (ø)
2.00% <0.00%> (ø%)

...ality/serialisation/HyperLogLogPlusSerialiser.java
38.46% <0.00%> (ø)
6.00% <0.00%> (ø%)

.../binaryoperator/ReservoirLongsUnionAggregator.java
100.00% <0.00%> (ø)
2.00% <0.00%> (ø%)

...binaryoperator/ReservoirItemsSketchAggregator.java
100.00% <0.00%> (ø)
2.00% <0.00%> (ø%)

.../binaryoperator/ReservoirItemsUnionAggregator.java
100.00% <0.00%> (ø)
2.00% <0.00%> (ø%)

...ty/serialisation/json/HllSketchJsonSerialiser.java
61.53% <0.00%> (ø)
3.00% <0.00%> (ø%)

... and 250 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 5d1a433...c7ee334. Read the comment docs.

Because of the nature of the changes and the need to revisit everything in the last pull request branch I am going to abandon the previous one and move ahead with this one, bringing the changes from the other through to this one as required.

Seems sensible. Do you mind if I close both pull requests so you can re-open this one when you're ready for it to be reviewed?

Closing both pull requests is fine with me.


lockBasedBuilder and expirationAfterWrite

Hello, while trying to build a HazelcastLockBasedProxyManager I stumbled upon what I think is a bug,
if I use
HazelcastLockBasedProxyManager<String> proxyManager = Bucket4jHazelcast.lockBasedBuilder(map).expirationAfterWrite(expiration).build();
I'll get a UnsupportedOperationException with the message "Expiration-after-write is not supported"
but If I use the deprecated constructor, it works as expected.
ClientSideConfig config = ClientSideConfig.getDefault().withExpirationAfterWriteStrategy(expiration);
proxyManager = new HazelcastLockBasedProxyManager<>(map, config);
I'm using bucket4j_jdk11-hazelcast 8.13.1

Sounds good! Thank you.

Will be released soon in the scope of 8.14.0


Update ai-textanalytics-readme.md

Docs Build status updates of commit 4ebe2f1:
:clock10: Full build: the average full build time is 145 min(s) 24 sec(s), this is based on the last 382 build(s) for this repository.

already in smoke-test

Docs Build status updates of commit 4ebe2f1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/ai-textanalytics-readme.md
:white_check_mark:Succeeded
View (azure-python)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Added the acid2 example and some fixes to render it quite nice

Acid2 renderd in Firefox (left) and Chrome (right).
The eye's are done very tricky in acid2 (a object element in a object element in a object element)
I've added support for background-attachment: fixed and a fix for Chrome using 0 as default z-index.

Thanks for the pull request! I've added a few inline comments.

I've added the test and removed the acid2 example, while adding the test I found a bug with background position and borders, fixed that too.

Any updates on this? I do really need support of background-attachment:fixed from this pull request.

I could create a pull request with just the background-attachment: fixed; fix.


Profile the ice40_import_routing_from_icebox script and make it fast

The current ice40_import_routing_from_icebox.py takes a long time to run. Currently the script is written to make it easy to understand and debug the rr_graph. There is plenty of room for optimization and making it fast!
Someone should profile it and make it fast!

Duplicate of #196


Enemy system

There will be multiple enemy types, with undecided variations in behavior and complexity, so this system is likely to be refactored and evolved over time.
To start, let's aim for basic enemies that are unaware of the player, and don't have any weapons. They themselves deal damage to the player, and take damage by the player's weapon charges. They could also reverse player damage via a powerup that makes the player invincible for a short time.

#8


Bad UX when swithcing languages

Hi, I just wanted to share with you the problematic workflow I encounter:

I access React docs, eg to read about ErrorBoundaries
I get redirected to the French version automatically
However, the translation of technical conept is actually more confusing than helpful when you are used to work in English. For instance "Périmètres d'erreur": it's nice to have an intelligible French translation of course, but "Perimètre" and "Boundary" have nothing in common and might be actually hard to find more documentations in English afterward. Another use case: I want to share this piece of docs to React beginner on Discord or elsewhere so I need the English version
I switch to English via the locale switcher
I get redirected to the home page :(
I have trouble finding the page back since the URL is also translated

This workflow could be vastly improved by simply keeping the current page when we switch languages

You can switch to react english site very easily.
All you have to do is replace https://fr.reactjs.org/ with https://reactjs.org/  in the URL.
Also if you think the French translation is confusing feel free to raise a issue and PR here https://github.com/reactjs/fr.reactjs.org/

I have trouble finding the page back since the URL is also translated

This shouldn't happen? The URLs are not translated generally. Can you share a translated URL so that we can have a look into that?

Yeah sorry I didn't describe the workflow quite right:

Indeed the the URL is not translated so you can change the URL
However usually you'll click on "languages" and hit a list of language, but at that point precisely you lose the page. You would need a "?from=the-page" query param for instance
I answer a lot of questions and check the docs often so it can quickly become an issue to change the URL everytime

I strongly second the OP. The localization in this form is a massive setback in using the website. The Hungarian translation is most probably not even remotely interested to the vast majority of Hungarian developers, and the way the sentence structures are mirrored into Hungarian makes it painful to read. The language chooser should keep me on the same page, and the preferred language should be persisted in a cookie.

The Hungarian translation is most probably not even remotely interested to the vast majority of Hungarian developers, and
the way the sentence structures are mirrored into Hungarian makes it painful to read.

You can add suggestions regarding Hungarian translation here https://github.com/reactjs/hu.reactjs.org/

The language chooser should keep me on the same page, and the preferred language should be persisted in a cookie.

@gaearon  thoughts?


Errors after enabling vite

Environment
Nuxt CLI v3.0.0-rc.8                                                                                18:19:53
RootDir: /Users/roman.vzn/WebstormProjects/cms-front                                                                                18:19:54
Nuxt project info:                                                                                18:19:54

Operating System: Darwin
Node Version:     v16.14.2
Nuxt Version:     2.16.0-27616340.013f051b
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      bridge, ssr, target, head, css, styleResources, plugins, components, buildModules, modules, axios, dayjs, i18n, publicRuntimeConfig, build, vuetify, googleFonts, loading, loadingIndicator, toast, generate, storybook, resolve, serverHandlers, devServerHandlers
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Reproduction
nuxi dev
Describe the bug
After start command (yarn dev) i got this errors

Additional context
No response
Logs
No response

Same error with npm

@danielroe here is a minimal reproduction repo: https://github.com/Towerism/nuxt-bridge-vite-fails-imports
my team encountered this, and as a result we cannot enable vite. I was going to create an issue, but I noticed this issue first. I hope this reproduction repo helps!

Close it pls. I really didnt find the time to send details


[computer-use-demo] Tool execution hangs on large outputs - Buffer handling improvement proposalWhen using the computer-use-demo tool with commands that produce large outputs (e.g., directory listings with many files), the tool execution gets stuck and becomes unresponsive after about 5 minutes. The only workaround is refreshing the page.

Root Cause Analysis
The tool execution hang appears to stem from several implementation issues:
bash.py Implementation Issues:
Hard-coded 120-second timeout (_timeout = 120.0)
Inefficient buffer handling (polling with 0.2s delay)
Entire buffer decoded at once
No streaming/chunking of large outputs
Current problematic implementation:
Current inefficient approach in bash.py
async def run(self, command: str):
# Entire output loaded into memory at once
returncode, output, error = await run(
command,
timeout=120.0  # Hard-coded timeout
)
return CLIResult(output=output, error=error)  # No chunking
Impact on Users
This issue severely impacts users when:
Listing directories with >1000 files (output >16KB)
Reading large log files
Running system queries that return substantial data Users must refresh the page every 5 minutes, breaking their workflow and losing command history.
Base Architecture Findings:
ToolResult class supports output combination
No built-in streaming support
Error handling focuses on immediate failures rather than timeouts
Proposed Solutions
Buffer Handling (Priority 1):
Example implementation approach:
async def run(self, command: str):
CHUNK_SIZE = 8000
async for chunk in stream_command(command):
if len(chunk) > CHUNK_SIZE:
yield process_chunk(chunk)
else:
yield chunk
Implement chunked reading instead of full buffer decode
Add output streaming capabilities
Consider increasing timeout for known large operations
Add buffer size monitoring
Error Handling (Priority 2):
Add specific timeout recovery mechanisms
Implement automatic retry logic for buffer overflows
Add progress indicators for long-running operations
Result Management (Priority 3):
Add streaming result support to ToolResult class
Implement progressive output updates
Add memory usage monitoring
Alternative Approaches Considered:
Process spawning: Split large commands into smaller sub-processes
Output pagination: Add --max-output flag to limit initial output
Client-side caching: Store partial results to prevent complete reruns
Looking forward to feedback on these approaches, particularly the chunked implementation example.

Update: I need to correct my initial analysis - further investigation revealed a different root cause.
The timeout issues were not related to buffer handling or large outputs as initially suspected, but rather stemmed from event loop management. Here's what I found:
ACTUAL ROOT CAUSE:

Random timeout errors were occurring due to premature event loop closure
Issue manifested as "timed out: bash has not returned in 120.0 seconds and must be restarted"
Problem occurred with both small and large outputs, indicating it wasn't buffer-related

THE FIX:
The solution was much simpler than my original proposal. The key change was making the stop() method properly async and awaiting process termination:
async def stop(self):
    if self._process.returncode is None:
        self._process.terminate()
        await self._process.wait()  # Ensure process termination

TESTING RESULTS: The fix has been tested with various scenarios including:

Background processes
Multiple parallel processes
Mixed stdout/stderr operations
Rapid successive commands
Complex process management
All tests passed without timeout errors, regardless of output size.

Therefore, I'm retracting my original buffer handling improvement proposal as it was addressing the wrong problem. The simpler event loop management fix appears to have resolved the timeout issues.

I apologize for any confusion my initial analysis may have caused. This is a good reminder that thorough investigation can sometimes reveal simpler solutions than initially suspected.


peazip: 9.4.0 -> 9.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/peazip/peazip/releases.
meta.description for peazip is: Cross-platform file and archive manager
meta.homepage for peazip is: https://peazip.github.io
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.5.0 with grep in /nix/store/3m3spvqvbqk1ahd30q8gf3vcf0r04g1y-peazip-9.5.0
found 9.5.0 in filename of file in /nix/store/3m3spvqvbqk1ahd30q8gf3vcf0r04g1y-peazip-9.5.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
peazip

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3m3spvqvbqk1ahd30q8gf3vcf0r04g1y-peazip-9.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A peazip https://github.com/r-ryantm/nixpkgs/archive/fbfdecbe90a1c29f018eddd5e49859221808f2de.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/fbfdecbe90a1c29f018eddd5e49859221808f2de#peazip

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3m3spvqvbqk1ahd30q8gf3vcf0r04g1y-peazip-9.5.0
ls -la /nix/store/3m3spvqvbqk1ahd30q8gf3vcf0r04g1y-peazip-9.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

peazip

Maintainer pings
cc @auroraanna for testing.

Some more changes should be done because peazip now supports using the compression programs in PATH.

Superseded by #263848.


Fail gracefully if Service Worker support is not available

P0 because demo-ing opening Squoosh from Android browsers on Chorme OS at CDS.
When opening the locally-running version of squoosh, SW works if the host is localhost, but due to http://crbug.com/848063, we need to specify the IP of the Linux container. That's no a secure origin, so Squoosh doesn't load.

Squoosh doesn’t fail when the ServiceWorker doesn’t load. I just tested it with an alias for localhost where SW will fail to install and squoosh keeps working fine for me. What error are you seeing?

You reported this as an issue for Chrome OS. Please include this sort of stuff in your issues in the future. Especially when time is tight and things are labelled as “P0” it is important that we don’t spend time on guessing conditions under which an error occurred.
I don’t have mobile Chrome at my disposal right now, but Squoosh works for me on desktop Firefox with a non-secure origin.

@dandv with Chrome Dev Summit on Monday, everything's P0 right now. Right now I'm having trouble seeing how a service worker install failure would lead to Squoosh not loading. Squoosh doesn't depend on a service worker, so without it everything should just work, but not offline.
Without detailed recreation steps there's not a lot we can do here.

Sorry for being insufficiently clear about the platform. I'm trying to get Squoosh to run on Chrome OS 70.0.3538.76 (Official Build) beta (64-bit), using node v10.13.0. At the moment npm start doesn't launch the server due to #259, but if I check out 3c757bb2b2f47eef43bad15094dcc3dfad9c1619, I can run the server.
The problem at that point is that I see the checkerboard screen in both Android Chrome Beta 71 and Android Firefox 63:

My (hasty) guess was that SW didn't load because that IP is not a secure origin, since I saw the same checkerboard screen with Firefox 60 ESR, which that turned out to have disabled SW.

Managed to connect Chrome Dev Tools running on Crostini to Android Chrome Dev (thanks @smibarber). Here's what's happening when trying to load the local instance (at commit 3c757bb2b2f47eef43bad15094dcc3dfad9c1619) from the Crostini IP:

That error is expected and does not break the app (I see it locally as well over a non-secure origin). I can not reproduce this behavior on my end with Firefox or Chrome, so not quite sure what to do.
What version are you running?

2ca97ef5866f66b1baaa3655f4a66427190f732a fixed it, thanks!


NOT SAVING X PATH OR LINK ON WINDOWS 10

after refresh only intervals and quantity save pls need help quick!!!!

Once you update setting in Extension options you need to refresh target page or URL to fetch new information and work on it.

This is some limitation from chrome browser.


Unsupported sql column, Postgres, int8range

Hello, when trying jet(2.6.0) on a Postgres table that has column with a Postgres range type 'int8range', the jet generator emits some errors:
[SQL Builder] Unsupported sql column '<column_name> int8range', using StringColumn instead.
Is there a way to customize current generator to support this column type, or request to add this as new feature?

Hi. Yeah, since the latest version it is possible. You can find more info in the wiki page.

ah, ok, nice, will try that out for PG's int8range, thanks!


Test ticket for Github FS Integration

 FreshService Ticket ID: 115 FreshService Ticket Agent: Sai Madhan FreshService Ticket Agent Email<EMAIL_ADDRESS>Ticket Priority: Low FreshService Ticket Description: Test ticket Ticket attachments : 1.Freshservice-logo.png

Agent Sai Madhan linked FreshService ticket 115 to this issue


run gogs as root user in containe

Is it possible to run gogs as root user in containe?
I just create a new container which use centos7 as base image and run gogs by setting entrypoit with '/app/gogs/gogs web'. It start up OK, but config user as root in install page failed when setuping gogs.
The notice is as following:

Additionally, Could someone tell me why gogs need set a user to run. Why not run gogs by default user?

no such issue on https://github.com/fabric8io/docker-gogs, so close it here.


Maybe move devtools to a separate page?

It isn't very comfort to use devtools in "modal".

I agree. In next version a planned to make an editor with settings groups, theme editor, e.t.c for advanced users on separate page. Current solution is the simplest one, but as a workaround you can copy text from the text area, paste it into JSON editor and then past it back.

is there anyway to make it... commit forever? every 10ish minutes i have to reopen the panel and click "apply" again

This will appear the next release. Also text format will be simplified.


validate the safetensors file

enhance is_model_safetensors,  add the check for safetensors file
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Functional tests have been added, if necessary.
[ ] E2E Workflow tests have been added, if necessary.

Thanks for the PR @reidliu41, this is great! I've felt for a while that we needed a stronger check for safetensors files
Could you look at the failing unit test?

Thanks for the PR @reidliu41, this is great! I've felt for a while that we needed a stronger check for safetensors files Could you look at the failing unit test?

thanks for reply, fixed it

hi guys, please feel free to share ideas.

This PR predates some recent Mergify changes, thus no automerge - merging manually


Add configurabe goals to XP tracker plugin

I wanted configurable goals in the XP tracker plugin, so here's what I have. I opted to just add to the existing UI. I know about #507, but I figured I'd write the feature first and figure out the exact UI later.
So the two UI changes are the addition of the "Set Goal.." button and a secondary progress bar when a goal is set on a skill tracker. When a goal is set, the second bar has the original behavior, showing the progress within the current level. (there is a config option to disable this bar)

Also the new dialogs for setting a goal:

Hmm, I feel like this is feature that OSRS client have and we are just re-implementing it at different place.

What do you mean? Is there an existing visual goal tracking plugin?

Yes, in the client directly, it's not plugin. Right click the XP icon, you can set goals there etc.

Wow, no kidding. I didn't know about that. I think the plugin version is a bit easier to work with, and more information could be added to it. But good to know.

Made some changes based on feedback. No more dialogs, the Set Goals.. button toggles a panel below the info panel that lets you set goals:

This also now supports XP goals as well as level goals.

Closing this PR, it suffered from scope creep when I went to make the goals persistent and synced between clients. If I were to pick this up again, it may be more useful to just augment Jagex's goal tracker interface, maybe connecting that to the xptracker panel.


Core bug with busy timeout (not working)

As per #155 and #1155 there still seems to be an issue with busy timeout not being respected.
The timeout option in new Database is not respected.  For example, we set it to 10 seconds, and it sometimes immediately throws an error when the database is busy.

Hi, could you provide a reproduce-able example?

Just out of curiosity, as there is nothing happening on the way down from setting the timeout on a new Database instance in JavaScript into the actual C function of sqlite: You are defining the timeout in milliseconds and you are not creating new instances of the database from several threads with different timeouts?

and it sometimes immediately throws an error when the database is busy.

That does not mean the timeout does not work. SQLite does not guarantee that the timeout is respected. In case of a deadlock it will immediately throw SQLITE_BUSY.

The presence of a busy handler does not guarantee that it will be invoked when there is lock contention. If SQLite determines that invoking the busy handler could result in a deadlock, it will go ahead and return SQLITE_BUSY to the application instead of invoking the busy handler.

https://www.sqlite.org/c3ref/busy_handler.html

better-sqlite3 doesn't do anything with the "busy timeout" except pass it directly to the underlying SQLite3 library. So this can't be an issue with better-sqlite3. I recommend posting on the SQLite forum: https://sqlite.org/forum/forum


[#167810062] Improve user management resilience

What
A couple of small changes to improve how we handle the scenario when a user doesn't all 3 of:

A record in CF
A record in UAA
A record in paas-accounts

How to review

Code review
Deploy to your dev env
Test it

[x] Invite a user to your dev env with permissions on an org
[x] visit the org members page
[x] check you can see the user
[x] delete their UAA account
[x] leave their CF records alone
[x] visit the org members page
[x] see that you don't see the invited user in the list

Who can review
Anyone

LGTM from a code review but I haven't tested it in my dev env yet.
Thoughts about adding some expectations around whether the user is displayed or not in the test? https://github.com/alphagov/paas-admin/pull/405/files#diff-1307065c0898353db545a4fe89c15535R167
I.e. it does not contain the broken user GUID

Thoughts about adding some expectations around whether the user is displayed or not in the test?

Good shout.

LGTM did the steps and it worked, 🎉 :shipit:


intelligently caching the JSON data

For setting the source and initializing the fuzzyhound, we do this.
function setsource(url, keys, output) {

    $.getJSON(url).then(function (response) {
        fuzzyhound.setOptions({
            source: response,
            keys: keys,
            output_limit: 200,  // Return up to N result, 0 to disable
            //output_map: output,
            output_map: function(root){ final_item = removeTags(root.item); console.log (final_item); return final_item; },
        })
    });
}

```Let's assume our url is this

`blah.blah.com/blah.js
`
And we have also this:

`$.ajaxSetup({cache: true});
`
This is great for efficiency but, what if the blah.js is changed on the server, ( say a spelling error has been fixed in it ), how do you make sure people who already cached the blah.js earlier in their browser gets the latest and greatest blah.js?

Would the following trick work?

`url = 'blah.blah.com/blah.js?version=' .getFileModificationDate("... /blah.js");
`
So whenever the file changes, I can change the version number on the URL of the setSource, either programmatically in an unattended fashion or manually.

In that case, would  "$.ajaxSetup({cache: true}); " still be serving the older file?

Or is there a better way to address this intelligent caching?

The version= is the right idea.
I usually put a hash of the content as the version instead of a date. That way you know if it truly changed.
Computing hash from file io can be expensive so you can have a cache of that on the server.
I think cache: true will still respect downloading new version.

I can confirm that attaching the version DEFINITELY works and cache:true does not cause any problem. cache: true still respects the version number. If the version number did not change, then cache:true allows you to read content from cache. If the number has changed, I do notice the delay of downloading the requested content.
setsource("https://... blah.blah.js?version=<?php echo blp_getFileModifDate('/...blah...blah.js');?>");
is the best way to handle it.
function blp_getFileModifDate($filePath) {
            // you can hit this with the  f:// start or / start.
            // it can resolve the file name either way.

            if ( blp_startsWith($filePath,'/')) {
                $filePath = YOUR_SERVER_ROOTPATH_HERE_WITHOUT_THE_FINAL_SLASH . $filePath;
                if ( !file_exists($filePath)) {
                    return 0;
                }
            } else {
                if ( !file_exists($filePath)) {
                    return 0;
                }
            }
            // if we are here, that means the file name has been resolved and found.
            return filemtime($filePath);

        }

The next improvement would be to deploy some sort of the gzip'ping on the fly, which I will explore next.
And this SO may have the answer:  https://stackoverflow.com/questions/6478304/zip-a-json-object-before-sending-in-php


Exception: your device doesn't support credential manager

When I am trying to register a passkey on my Redmi Android 14, it is giving me an exception saying 'Your device doesn't support credential manager

Hey @omeremp. Which version of the package are you using?
This appears to be a device specific issue. There is not much documentation about the error, but I found one comment by an Android contributor who acknowledged the issue. They apparently fixed it in version 1.2.1 of the credential manager library (https://github.com/android/identity-samples/issues/70). We use this version since version passkeys v2.0.5.


Proxy Authentication Required

Hello,
I am installing Conduit for the first time but keep getting a Proxy Authentication error. I am using a Windows pc in our corporate environment. I have proxy settings set in my environment variables that allow me to use PaaS and Cloud Foundry okay however I cannot install this plugin. Is there any other alternatives for this or any ideas to help me? Thanks...
Searching CF-Community for plugin conduit...
Get https://plugins.cloudfoundry.org/list: Proxy Authentication Required
FAILED

Hi Michael,
An alternative approach is to download a release from this repo, and install it with cf install-plugin /path/to/release.
Regards,
Andy

@AP-Hunt  Oh ok grand I'll give that a go sure thanks!

Let me know how it goes, and we'll get this closed off or help further :+1:

@AP-Hunt You can close this issue thanks