Aspect ratio incorrectly applied by Openbox

I am running glfw v3.2.1 on debian linux freshly compiled from source.  While the documentation warns that conflicting size limits may pose a problem, I have tried this with 800x600 and 4:3 as well as 1280x720 and 16:9 and both cases yield invalid enforced sizes of 800x599 and 1280x719.
Here is a screenshot:

Here is the code that produced that screenshot:
#include <stdio.h>
#include <GLFW/glfw3.h>

void wresize(GLFWwindow* window, int w, int h)
{
    fprintf(stdout, "Window Resized: %d, %d\n", w, h);
}

void fbresize(GLFWwindow* window, int w, int h)
{
    fprintf(stdout, "Framebuffer Resized: %d, %d\n", w, h);
}

int main(void)
{
    GLFWwindow* window;

    /* Initialize the library */
    if (!glfwInit())
        return -1;

    /* Create a windowed mode window and its OpenGL context */
    window = glfwCreateWindow(1280, 720, "Hello World", NULL, NULL);
    if (!window)
    {
        glfwTerminate();
        return -1;
    }

    /* enforce size restrictions */
    glfwSetWindowSizeLimits(window, 1280, 720, GLFW_DONT_CARE, GLFW_DONT_CARE);
    glfwSetWindowAspectRatio(window, 16, 9);

    /* set callbacks for window and framebuffer resize */
    glfwSetWindowSizeCallback(window, wresize);
    glfwSetFramebufferSizeCallback(window, fbresize);

    /* Make the window's context current */
    glfwMakeContextCurrent(window);

    /* Loop until the user closes the window */
    while (!glfwWindowShouldClose(window))
    {
        /* Render here */
        glClear(GL_COLOR_BUFFER_BIT);

        /* Swap front and back buffers */
        glfwSwapBuffers(window);

        /* Poll for and process events */
        glfwPollEvents();
    }

    glfwTerminate();
    return 0;
}

Removing the size limit and keeping the aspect ratio yields the same invalid initial window size. I am using openbox and a somewhat unusual triple-monitor configuration, but I don't think those would be related specifically.  Is anyone else able to confirm or experience this behavior?

I can't reproduce this on Debian Linux using Xfce desktop (with xfwm as window manager). With both size limits and aspect ratio limits enabled, the window and framebuffer both reach the intended 1280x720 resolution.
At a guess, the problem lies somewhere between glfw and Openbox window manager. Are you able to test a different window manager on the same machine?
NB: In testing this I found that size limits don't work at all on my machine with GLFW_DONT_CAREs as any of the arguments to glfwSetWindowSizeLimits. That's probably a separate issue...

On X11, all code for applying the specified limits to the window is inside the WM. GLFW only sets the associated window properties. Please run the xprop utility on the GLFW window and post the output.

@elmindreda, I have never used xprop, but these are pretty obvious:
WM_NORMAL_HINTS(WM_SIZE_HINTS):
		program specified minimum size: 1280 by 720
		program specified minimum aspect ratio: 16/9
		program specified maximum aspect ratio: 16/9

I assume that means glfw is doing the right thing in spite of the callback getting a size of 1280x719?

@tombsar, I did not want to make a mess of my host so I tried installing these desktop environments inside a VM:

gnome
kde
xfce
lxde
mate

With lxde (which runs openbox) I had invalid dimensions (1280x719), the same results when I ran openbox directly (like I do from my host).
I got valid dimensions from gnome (1280x720).
I was unable to get kde, xfce, or mate to fprintf; the cpu spiked and system became very unresponsive but no fprintf or any error messages were displayed (could be VM, could be conflicting packages, who knows...)  The lxde environment also spiked CPU but printed dimensions.

I encountered the bug from the go bindings, so I am out of my element.  Is this something I should open a ticket for with the openbox folks, and if so what should I add to the ticket?

@cdelorme Yes, it looks like GLFW and the bindings are passing the data along correctly. Please forward the bug to Openbox.

Just a quick update; I opened a bug report with openbox.

This seems to have been accepted and assigned at their end. Closing this.


Create JSON files

For the ejp-rd data metadata model create the json files :
Create JSON for the following entities:

BiologicalSample

BiologicalSamplePatient

Catalog

Catalog|BioBank

Catalog|PatientRegistry

Code

CodeSystem

Datetime

Eupid

Location

Organisation

PropertyValue

StudyDesign

Added a repo Issue #2


Allow mapping fully qualified measurement keys

@smitsanghavi @95-martin-orion Here's an implementation of fully qualified measurement key mapping. We'll eventually want to include allowing proper MeasurementKey types also, but that is a bigger change and this is enough to unblock control keys.
One behavior change is that it doesn't trim unmatched keys (see line 192 of circuit_operation_test), since that now would require unrolling the whole subcircuit, which may be expensive if there are many repetitions.

I realize that a path-inclusive remapping is needed soon but one of the main reasons for introducing MeasurementKey was to move away from this : separated string representation. This makes the code rely on brittle string parsing logic which may break if a user defined key has this character. Adding more support for it might be a regression and take more effort to move away from it.
The root cause of this is that MeasurementKey based functions still don't have full parity with all the string-based key methods. Let me get on this ASAP. I can have measurement_key_objs and with_measurement_key_obj_mapping ready this week.

Sounds good. I'll wait for that update. And really there's no particular rush on this if you're busy. AFAICT there's not a lot of work left to complete feedforward so I don't see any schedule risk. I was just anxious to get it out.


Add build sepc file option

Add "Build Spec File" option to project configuration.
The option specifies buildspecOverride to use alternative build spec file on build.
http://docs.aws.amazon.com/codebuild/latest/userguide/run-build.html

Thanks for your contribution, we're reviewing this right now.

I merged your pull request with some minor modifications. Thank you for your contribution and feel free to submit more!


make error

It seems that recent changes break the CMake/make. Here is a log from one of the travis build of homebrew-rdkit (https://travis-ci.org/hsiaoyi0504/homebrew-rdkit/jobs/362614009).
==> make -j2
Last 15 lines from /Users/travis/Library/Logs/Homebrew/rdkit/02.make:
                      ^
/tmp/rdkit-20180405-5805-1cky97r/Code/RDGeneral/LocaleSwitcher.cpp:75:5: error: use of undeclared identifier 'recursion'
    recursion++;
    ^
/tmp/rdkit-20180405-5805-1cky97r/Code/RDGeneral/LocaleSwitcher.cpp:77:5: error: use of undeclared identifier 'recursion'
    recursion--;
    ^
/tmp/rdkit-20180405-5805-1cky97r/Code/RDGeneral/LocaleSwitcher.cpp:78:10: error: use of undeclared identifier 'recursion'
  return recursion;
         ^
5 errors generated.
make[2]: *** [Code/RDGeneral/CMakeFiles/RDGeneral.dir/LocaleSwitcher.cpp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Code/RDGeneral/CMakeFiles/RDGeneral.dir/all] Error 2
make: *** [all] Error 2
Do not report this issue to Homebrew/brew or Homebrew/core!

I’ll take a look at this today.

I'm not duplicating this issue locally.  Could you point me at the travis builds please?  I'm having troubles finding them.

I'm blind, it's the link at the top.

It looks like some c++11 code snuck into the legacy branch:
https://github.com/rdkit/rdkit/blob/020024ee5cb612781239e4ca152a4a51f6ff1b1d/Code/RDGeneral/StreamOps.h#L371
we can fix this for brew by building the modern_cxx branch, I'll start this update.

Dear All,
I have those types lf errors with the new beta too with or without the brew install on my mac.
BR
Guillaume
Envoyé de mon iPhone

Le 6 avr. 2018 à 15:11, Brian Kelley<EMAIL_ADDRESS>a écrit :
It looks like some c++11 code snuck into the legacy branch:
https://github.com/rdkit/rdkit/blob/020024ee5cb612781239e4ca152a4a51f6ff1b1d/Code/RDGeneral/StreamOps.h#L371
we can fix this for brew by building the modern_cxx branch, I'll start this update.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

We'll fix this in our cmakelists.txt, but setting these environment
variables will help the non-brew builds for now (that recipe is finally
fixed I think)
export CXXFLAGS= "-std=c++11 -stdlib=libc++ -Wno-parentheses

-Wno-logical-op-parentheses -Wno-format"
export CFLAGS="-Wno-parentheses -Wno-logical-op-parentheses -Wno-format"
cmake ...
On Sat, Apr 7, 2018 at 5:03 AM, guillaume godin<EMAIL_ADDRESS>wrote:

Dear All,
I have those types lf errors with the new beta too with or without the
brew install on my mac.
BR
Guillaume
Envoyé de mon iPhone

Le 6 avr. 2018 à 15:11, Brian Kelley<EMAIL_ADDRESS>a écrit
:
It looks like some c++11 code snuck into the legacy branch:
https://github.com/rdkit/rdkit/blob/020024ee5cb612781239e4ca152a4a
51f6ff1b1d/Code/RDGeneral/StreamOps.h#L371
we can fix this for brew by building the modern_cxx branch, I'll start
this update.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rdkit/rdkit/issues/1809#issuecomment-379454233, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJbioL_HPfCIDtU7IitBm93JhgJhVH9-ks5tmID3gaJpZM4TJ7dG
.


test: make results of keymanager e2e tests deterministic

Motivation
Keystores are decrypted in parallel now (https://github.com/ChainSafe/lodestar/pull/5624) which means the order in which they are added to the validator store  (validatorStore.addSigner) is no longer deterministic.
https://github.com/ChainSafe/lodestar/blob/f07d97f5ff45e64ad45a00d9c829a4f0a899f055/packages/cli/src/cmds/validator/keymanager/impl.ts#L166
This makes the result of keymanager e2e non-deterministic and causes e2e tests to fail randomly.

However, the order of signers in validator store does not matter which means the assertion can be updated to check the response in an unordered way.
Description
This change makes results of keymanager e2e tests deterministic, we only need to check the presence of all keys in response, irrespective of their order.

:tada: This PR is included in v1.9.0 :tada:


HSV and zoneminder mjpeg source http, live ok but HSV record crash

Hi
first thanks for all job
I had camera from zoneminder, live is ok but when i wan't to start HSV record, he crash
Zoneminder flux is 1280*720
{
"name": "PorteHSV",
"motionTimeout": 15,
"unbridge": true,
"hsv": true,
"prebuffering": false,
"forcePrebuffering": false,
"prebufferLength": 4000,
"videoConfig": {
"source": "-i http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=50&maxfps=10&buffer=1000&user=julien&pass=pass",
"stillImageSource": "-i http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=single&monitor=2&scale=100&user=julien&pass=pass",
"maxStreams": 10,
"readRate": true,
"maxWidth": 1280,
"maxHeight": 720,
"maxFPS": 10,
"debug": true,
"vcodec": "libx264",
"stimeout": 0,
"audio": false
},
"mqtt": {
"motionTopic": "homebridge/porte",
"motionMessage": "on"
},
"videoanalysis": {
"active": false
}
},
On live feed all is ok
[15/01/2022, 17:02:32] [CameraUI] PorteHSV: Starting video stream: 1280x720, 30 fps, 299 kbps  [15/01/2022, 17:02:32] [CameraUI] PorteHSV: Stream command: /usr/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel level+verbose -re -i http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=50&maxfps=10&buffer=1000&user=julien&pass=pass -f lavfi -i anullsrc=cl=1 -shortest -an -sn -dn -r 30 -vcodec libx264 -pix_fmt yuv420p -color_range mpeg -f rawvideo -preset ultrafast -tune zerolatency -filter:v scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease,scale=trunc(iw/2)*2:trunc(ih/2)*2 -b:v 299k -bufsize 598k -maxrate 299k -payload_type 99 -ssrc 73102 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params iWuTVyu6K060X6y4zpgQlPKoYFw7Blms7cWMDEyb srtp://<IP_ADDRESS>:57778?rtcpport=57778&pkt_size=1318 -progress pipe:1 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [tcp @ 0x3b830a0] [verbose] Starting connection attempt to <IP_ADDRESS> port 80 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [tcp @ 0x3b830a0] [verbose] Successfully connected to <IP_ADDRESS> port 80 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info] Input #0, mpjpeg, from 'http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=50&maxfps=10&buffer=1000&user=julien&pass=pass': [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]   Duration: N/A, bitrate: N/A [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]     Stream #0:0: Video: mjpeg (Baseline), 1 reference frame, yuvj420p(pc, bt470bg/unknown/unknown, center), 640x360 [SAR 1:1 DAR 16:9], 25 tbr, 25 tbn, 25 tbc [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [Parsed_anullsrc_0 @ 0x3b8f5b0] [verbose] sample_rate:44100 channel_layout:'1 channels (FL)' nb_samples:1024 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info] Input #1, lavfi, from 'anullsrc=cl=1': [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]   Duration: N/A, start: 0.000000, bitrate: 352 kb/s [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]     Stream #1:0: Audio: pcm_u8, 44100 Hz, 1 channels (FL), u8, 352 kb/s [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info] Stream mapping: [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]   Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264)) [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info] Press [q] to stop, [?] for help [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [Parsed_scale_0 @ 0x3bca0e0] [verbose] w:min(1280,iw) h:min(720,ih) flags:'bicubic' interl:0 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [Parsed_scale_1 @ 0x3bf4fd0] [verbose] w:trunc(iw/2)*2 h:trunc(ih/2)*2 flags:'bicubic' interl:0 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [graph 0 input from stream 0:0 @ 0x3bf5c60] [verbose] w:640 h:360 pixfmt:yuvj420p tb:1/25 fr:25/1 sar:1/1 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [Parsed_scale_0 @ 0x3bca0e0] [verbose] w:640 h:360 fmt:yuvj420p sar:1/1 -> w:640 h:360 fmt:yuvj420p sar:1/1 flags:0x4 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [swscaler @ 0x3bf6990] [warning] deprecated pixel format used, make sure you did set range correctly [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [Parsed_scale_1 @ 0x3bf4fd0] [verbose] w:640 h:360 fmt:yuvj420p sar:1/1 -> w:640 h:360 fmt:yuv420p sar:1/1 flags:0x4 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [libx264 @ 0x3b84160] [info] using SAR=1/1 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [libx264 @ 0x3b84160] [info] using cpu capabilities: ARMv6 NEON [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [libx264 @ 0x3b84160] [info] profile Constrained Baseline, level 3.0, 4:2:0, 8-bit [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info] Output #0, rtp, to 'srtp://<IP_ADDRESS>:57778?rtcpport=57778&pkt_size=1318': [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]   Metadata: [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]     encoder         : Lavf58.45.100 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]     Stream #0:0: Video: h264 (libx264), 1 reference frame, yuv420p(tv, center), 640x360 [SAR 1:1 DAR 16:9], q=-1--1, 299 kb/s, 30 fps, 90k tbn, 30 tbc [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]     Metadata: [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]       encoder         : Lavc58.91.100 libx264 [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]     Side data: [15/01/2022, 17:02:32] [CameraUI] PorteHSV: [info]       cpb: bitrate max/min/avg: 299000/0/299000 buffer size: 598000 vbv_delay: N/A [15/01/2022, 17:02:33] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:33] [CameraUI] PorteHSV: [info] frame=    6 fps=0.0 q=38.0 size=      13kB time=00:00:00.16 bitrate= 653.5kbits/s dup=1 drop=0 speed=0.331x     [15/01/2022, 17:02:33] [CameraUI] PorteHSV: Getting the first frames took 0.722 seconds. [15/01/2022, 17:02:33] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:33] [CameraUI] PorteHSV: [info] frame=   12 fps= 12 q=37.0 size=      20kB time=00:00:00.36 bitrate= 442.0kbits/s dup=2 drop=0 speed=0.363x     [15/01/2022, 17:02:34] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:34] [CameraUI] PorteHSV: [info] frame=   19 fps= 12 q=38.0 size=      32kB time=00:00:00.60 bitrate= 441.3kbits/s dup=3 drop=0 speed=0.393x     [15/01/2022, 17:02:34] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:34] [CameraUI] PorteHSV: [info] frame=   24 fps= 12 q=36.0 size=      33kB time=00:00:00.76 bitrate= 349.3kbits/s dup=4 drop=0 speed=0.377x     [15/01/2022, 17:02:35] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:35] [CameraUI] PorteHSV: [info] frame=   31 fps= 12 q=36.0 size=      36kB time=00:00:01.00 bitrate= 293.2kbits/s dup=5 drop=0 speed=0.393x     [15/01/2022, 17:02:35] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:35] [CameraUI] PorteHSV: [info] frame=   37 fps= 12 q=34.0 size=      42kB time=00:00:01.20 bitrate= 284.0kbits/s dup=6 drop=0 speed=0.393x     [15/01/2022, 17:02:36] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:36] [CameraUI] PorteHSV: [info] frame=   43 fps= 12 q=35.0 size=      57kB time=00:00:01.40 bitrate= 330.8kbits/s dup=7 drop=0 speed=0.393x     [15/01/2022, 17:02:36] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:36] [CameraUI] PorteHSV: [info] frame=   49 fps= 12 q=34.0 size=      57kB time=00:00:01.60 bitrate= 293.1kbits/s dup=8 drop=0 speed=0.393x     [15/01/2022, 17:02:37] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:37] [CameraUI] PorteHSV: [info] frame=   55 fps= 12 q=32.0 size=      60kB time=00:00:01.80 bitrate= 273.1kbits/s dup=9 drop=0 speed=0.393x     [15/01/2022, 17:02:37] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:37] [CameraUI] PorteHSV: Reconfigure stream requested: 640x360, 30 fps, 132 kbps (Ignored) [15/01/2022, 17:02:37] [CameraUI] PorteHSV: [info] frame=   61 fps= 12 q=33.0 size=      74kB time=00:00:02.00 bitrate= 301.3kbits/s dup=10 drop=0 speed=0.393x     [15/01/2022, 17:02:38] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:38] [CameraUI] PorteHSV: [info] frame=   67 fps= 12 q=32.0 size=      75kB time=00:00:02.20 bitrate= 278.1kbits/s dup=11 drop=0 speed=0.393x     [15/01/2022, 17:02:38] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:38] [CameraUI] PorteHSV: [info] frame=   73 fps= 12 q=28.0 size=      80kB time=00:00:02.40 bitrate= 274.2kbits/s dup=12 drop=0 speed=0.393x     [15/01/2022, 17:02:39] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:39] [CameraUI] PorteHSV: [info] frame=   79 fps= 12 q=34.0 size=      94kB time=00:00:02.60 bitrate= 296.4kbits/s dup=13 drop=0 speed=0.393x     [15/01/2022, 17:02:39] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:40] [CameraUI] PorteHSV: [info] frame=   86 fps= 12 q=32.0 size=      96kB time=00:00:02.83 bitrate= 277.1kbits/s dup=14 drop=0 speed=0.398x     [15/01/2022, 17:02:40] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:40] [CameraUI] PorteHSV: [info] frame=   92 fps= 12 q=27.0 size=     102kB time=00:00:03.03 bitrate= 274.9kbits/s dup=15 drop=0 speed=0.398x     [15/01/2022, 17:02:40] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:41] [CameraUI] PorteHSV: [info] frame=   98 fps= 12 q=32.0 size=     119kB time=00:00:03.23 bitrate= 300.6kbits/s dup=16 drop=0 speed=0.398x     [15/01/2022, 17:02:41] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:41] [CameraUI] PorteHSV: [info] frame=  104 fps= 12 q=33.0 size=     120kB time=00:00:03.43 bitrate= 286.6kbits/s dup=17 drop=0 speed=0.397x     [15/01/2022, 17:02:41] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:42] [CameraUI] PorteHSV: [info] frame=  110 fps= 12 q=31.0 size=     123kB time=00:00:03.63 bitrate= 277.7kbits/s dup=18 drop=0 speed=0.397x     [15/01/2022, 17:02:42] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:42] [CameraUI] PorteHSV: [info] frame=  116 fps= 12 q=25.0 size=     131kB time=00:00:03.83 bitrate= 279.8kbits/s dup=19 drop=0 speed=0.397x     [15/01/2022, 17:02:42] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:43] [CameraUI] PorteHSV: [info] frame=  122 fps= 12 q=28.0 size=     136kB time=00:00:04.03 bitrate= 276.9kbits/s dup=20 drop=0 speed=0.397x     [15/01/2022, 17:02:43] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:43] [CameraUI] PorteHSV: [info] frame=  128 fps= 12 q=32.0 size=     150kB time=00:00:04.23 bitrate= 289.7kbits/s dup=21 drop=0 speed=0.397x     [15/01/2022, 17:02:43] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:44] [CameraUI] PorteHSV: [info] frame=  134 fps= 12 q=31.0 size=     153kB time=00:00:04.43 bitrate= 282.0kbits/s dup=22 drop=0 speed=0.397x     [15/01/2022, 17:02:44] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:44] [CameraUI] PorteHSV: [info] frame=  140 fps= 12 q=31.0 size=     166kB time=00:00:04.63 bitrate= 293.3kbits/s dup=23 drop=0 speed=0.397x     [15/01/2022, 17:02:44] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:45] [CameraUI] PorteHSV: [info] frame=  146 fps= 12 q=31.0 size=     168kB time=00:00:04.83 bitrate= 285.6kbits/s dup=24 drop=0 speed=0.397x     [15/01/2022, 17:02:45] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:45] [CameraUI] PorteHSV: [info] frame=  152 fps= 12 q=26.0 size=     174kB time=00:00:05.03 bitrate= 283.1kbits/s dup=25 drop=0 speed=0.397x     [15/01/2022, 17:02:45] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:46] [CameraUI] PorteHSV: [info] frame=  158 fps= 12 q=29.0 size=     179kB time=00:00:05.23 bitrate= 280.8kbits/s dup=26 drop=0 speed=0.396x     [15/01/2022, 17:02:46] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:46] [CameraUI] PorteHSV: [info] frame=  164 fps= 12 q=31.0 size=     198kB time=00:00:05.43 bitrate= 298.9kbits/s dup=27 drop=0 speed=0.396x     [15/01/2022, 17:02:46] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:47] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:47] [CameraUI] PorteHSV: [info] frame=  172 fps= 12 q=29.0 size=     203kB time=00:00:05.70 bitrate= 292.0kbits/s dup=29 drop=0 speed=0.401x     [15/01/2022, 17:02:47] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:47] [CameraUI] PorteHSV: [info] frame=  178 fps= 12 q=29.0 size=     208kB time=00:00:05.90 bitrate= 288.8kbits/s dup=30 drop=0 speed= 0.4x     [15/01/2022, 17:02:48] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:48] [CameraUI] PorteHSV: [info] frame=  184 fps= 12 q=22.0 size=     219kB time=00:00:06.10 bitrate= 294.6kbits/s dup=31 drop=0 speed= 0.4x     [15/01/2022, 17:02:48] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:48] [CameraUI] PorteHSV: [info] frame=  190 fps= 12 q=28.0 size=     230kB time=00:00:06.30 bitrate= 298.9kbits/s dup=32 drop=0 speed= 0.4x     [15/01/2022, 17:02:49] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:49] [CameraUI] PorteHSV: [info] frame=  196 fps= 12 q=28.0 size=     234kB time=00:00:06.50 bitrate= 295.2kbits/s dup=33 drop=0 speed= 0.4x     [15/01/2022, 17:02:49] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:49] [CameraUI] PorteHSV: [info] frame=  202 fps= 12 q=29.0 size=     239kB time=00:00:06.70 bitrate= 292.4kbits/s dup=34 drop=0 speed= 0.4x     [15/01/2022, 17:02:50] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:50] [CameraUI] PorteHSV: [info] frame=  208 fps= 12 q=28.0 size=     245kB time=00:00:06.90 bitrate= 291.3kbits/s dup=35 drop=0 speed= 0.4x     [15/01/2022, 17:02:50] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:50] [CameraUI] PorteHSV: [info] frame=  214 fps= 12 q=22.0 size=     255kB time=00:00:07.10 bitrate= 294.7kbits/s dup=36 drop=0 speed= 0.4x     [15/01/2022, 17:02:51] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:51] [CameraUI] PorteHSV: [info] frame=  220 fps= 12 q=28.0 size=     266kB time=00:00:07.30 bitrate= 298.8kbits/s dup=37 drop=0 speed=0.399x     [15/01/2022, 17:02:51] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:51] [CameraUI] PorteHSV: [info] frame=  226 fps= 12 q=29.0 size=     271kB time=00:00:07.50 bitrate= 295.7kbits/s dup=38 drop=0 speed=0.399x     [15/01/2022, 17:02:52] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:52] [CameraUI] PorteHSV: [info] frame=  232 fps= 12 q=28.0 size=     277kB time=00:00:07.70 bitrate= 294.3kbits/s dup=39 drop=0 speed=0.399x     [15/01/2022, 17:02:52] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:52] [CameraUI] PorteHSV: [info] frame=  238 fps= 12 q=28.0 size=     282kB time=00:00:07.90 bitrate= 292.1kbits/s dup=40 drop=0 speed=0.399x     [15/01/2022, 17:02:53] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:53] [CameraUI] PorteHSV: [info] frame=  244 fps= 12 q=22.0 size=     292kB time=00:00:08.10 bitrate= 295.5kbits/s dup=41 drop=0 speed=0.399x     [15/01/2022, 17:02:53] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:53] [CameraUI] PorteHSV: [info] frame=  250 fps= 12 q=29.0 size=     304kB time=00:00:08.30 bitrate= 299.7kbits/s dup=42 drop=0 speed=0.399x     [15/01/2022, 17:02:54] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:54] [CameraUI] PorteHSV: [info] frame=  257 fps= 12 q=31.0 size=     342kB time=00:00:08.53 bitrate= 328.0kbits/s dup=43 drop=0 speed= 0.4x     [15/01/2022, 17:02:54] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:54] [CameraUI] PorteHSV: [info] frame=  263 fps= 12 q=31.0 size=     349kB time=00:00:08.73 bitrate= 327.6kbits/s dup=44 drop=0 speed= 0.4x     [15/01/2022, 17:02:55] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:55] [CameraUI] PorteHSV: [info] frame=  269 fps= 12 q=31.0 size=     355kB time=00:00:08.93 bitrate= 325.7kbits/s dup=45 drop=0 speed= 0.4x     [15/01/2022, 17:02:55] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:55] [CameraUI] PorteHSV: [info] frame=  275 fps= 12 q=31.0 size=     363kB time=00:00:09.13 bitrate= 325.7kbits/s dup=46 drop=0 speed= 0.4x     [15/01/2022, 17:02:56] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:56] [CameraUI] PorteHSV: [info] frame=  281 fps= 12 q=32.0 size=     373kB time=00:00:09.33 bitrate= 327.7kbits/s dup=47 drop=0 speed= 0.4x     [15/01/2022, 17:02:56] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:56] [CameraUI] PorteHSV: [info] frame=  287 fps= 12 q=31.0 size=     380kB time=00:00:09.53 bitrate= 326.2kbits/s dup=48 drop=0 speed= 0.4x     [15/01/2022, 17:02:57] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:57] [CameraUI] PorteHSV: [info] frame=  293 fps= 12 q=30.0 size=     383kB time=00:00:09.73 bitrate= 322.3kbits/s dup=49 drop=0 speed= 0.4x     [15/01/2022, 17:02:57] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:57] [CameraUI] PorteHSV: [info] frame=  299 fps= 12 q=30.0 size=     389kB time=00:00:09.93 bitrate= 320.6kbits/s dup=50 drop=0 speed=0.399x     [15/01/2022, 17:02:58] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:58] [CameraUI] PorteHSV: [info] frame=  305 fps= 12 q=30.0 size=     397kB time=00:00:10.13 bitrate= 321.2kbits/s dup=51 drop=0 speed=0.399x     [15/01/2022, 17:02:58] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:58] [CameraUI] PorteHSV: [info] frame=  311 fps= 12 q=30.0 size=     404kB time=00:00:10.33 bitrate= 320.0kbits/s dup=52 drop=0 speed=0.399x     [15/01/2022, 17:02:59] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:59] [CameraUI] PorteHSV: [info] frame=  317 fps= 12 q=30.0 size=     410kB time=00:00:10.53 bitrate= 318.7kbits/s dup=53 drop=0 speed=0.399x     [15/01/2022, 17:02:59] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:02:59] [CameraUI] PorteHSV: [info] frame=  323 fps= 12 q=30.0 size=     415kB time=00:00:10.73 bitrate= 316.7kbits/s dup=54 drop=0 speed=0.399x     [15/01/2022, 17:03:00] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:00] [CameraUI] PorteHSV: [info] frame=  329 fps= 12 q=29.0 size=     423kB time=00:00:10.93 bitrate= 317.1kbits/s dup=55 drop=0 speed=0.399x     [15/01/2022, 17:03:00] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:00] [CameraUI] PorteHSV: [info] frame=  335 fps= 12 q=29.0 size=     429kB time=00:00:11.13 bitrate= 315.8kbits/s dup=56 drop=0 speed=0.399x     [15/01/2022, 17:03:01] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:01] [CameraUI] PorteHSV: [info] frame=  342 fps= 12 q=30.0 size=     436kB time=00:00:11.36 bitrate= 314.0kbits/s dup=57 drop=0 speed= 0.4x     [15/01/2022, 17:03:01] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:01] [CameraUI] PorteHSV: [info] frame=  347 fps= 12 q=30.0 size=     440kB time=00:00:11.53 bitrate= 312.8kbits/s dup=58 drop=0 speed=0.399x     [15/01/2022, 17:03:02] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:02] [CameraUI] PorteHSV: [info] frame=  354 fps= 12 q=30.0 size=     448kB time=00:00:11.76 bitrate= 312.1kbits/s dup=59 drop=0 speed= 0.4x     [15/01/2022, 17:03:02] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:02] [CameraUI] PorteHSV: [info] frame=  360 fps= 12 q=30.0 size=     454kB time=00:00:11.96 bitrate= 310.6kbits/s dup=60 drop=0 speed= 0.4x     [15/01/2022, 17:03:03] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:03] [CameraUI] PorteHSV: [info] frame=  366 fps= 12 q=30.0 size=     460kB time=00:00:12.16 bitrate= 309.8kbits/s dup=61 drop=0 speed= 0.4x     [15/01/2022, 17:03:03] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:03] [CameraUI] PorteHSV: [info] frame=  372 fps= 12 q=30.0 size=     469kB time=00:00:12.36 bitrate= 310.4kbits/s dup=62 drop=0 speed= 0.4x     [15/01/2022, 17:03:04] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:04] [CameraUI] PorteHSV: [info] frame=  378 fps= 12 q=30.0 size=     475kB time=00:00:12.56 bitrate= 309.4kbits/s dup=63 drop=0 speed= 0.4x     [15/01/2022, 17:03:04] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:04] [CameraUI] PorteHSV: [info] frame=  384 fps= 12 q=29.0 size=     481kB time=00:00:12.76 bitrate= 308.4kbits/s dup=64 drop=0 speed= 0.4x     [15/01/2022, 17:03:05] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:05] [CameraUI] PorteHSV: [info] frame=  390 fps= 12 q=30.0 size=     486kB time=00:00:12.96 bitrate= 307.2kbits/s dup=65 drop=0 speed= 0.4x     [15/01/2022, 17:03:05] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:05] [CameraUI] PorteHSV: [info] frame=  396 fps= 12 q=30.0 size=     495kB time=00:00:13.16 bitrate= 308.1kbits/s dup=66 drop=0 speed=0.399x     [15/01/2022, 17:03:06] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:06] [CameraUI] PorteHSV: [info] frame=  402 fps= 12 q=29.0 size=     502kB time=00:00:13.36 bitrate= 307.4kbits/s dup=67 drop=0 speed=0.399x     [15/01/2022, 17:03:06] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:06] [CameraUI] PorteHSV: [info] frame=  408 fps= 12 q=30.0 size=     511kB time=00:00:13.56 bitrate= 308.7kbits/s dup=68 drop=0 speed=0.399x     [15/01/2022, 17:03:07] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:07] [CameraUI] PorteHSV: [info] frame=  414 fps= 12 q=30.0 size=     517kB time=00:00:13.76 bitrate= 307.6kbits/s dup=69 drop=0 speed=0.399x     [15/01/2022, 17:03:07] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:07] [CameraUI] PorteHSV: [info] frame=  420 fps= 12 q=29.0 size=     526kB time=00:00:13.96 bitrate= 308.4kbits/s dup=70 drop=0 speed=0.399x     [15/01/2022, 17:03:08] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:08] [CameraUI] PorteHSV: [info] frame=  426 fps= 12 q=29.0 size=     532kB time=00:00:14.16 bitrate= 307.4kbits/s dup=71 drop=0 speed=0.399x     [15/01/2022, 17:03:08] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:08] [CameraUI] PorteHSV: [info] frame=  432 fps= 12 q=29.0 size=     537kB time=00:00:14.36 bitrate= 306.3kbits/s dup=72 drop=0 speed=0.399x     [15/01/2022, 17:03:09] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:09] [CameraUI] PorteHSV: [info] frame=  438 fps= 12 q=30.0 size=     543kB time=00:00:14.56 bitrate= 305.2kbits/s dup=73 drop=0 speed=0.399x     [15/01/2022, 17:03:09] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:09] [CameraUI] PorteHSV: [info] frame=  444 fps= 12 q=30.0 size=     551kB time=00:00:14.76 bitrate= 305.7kbits/s dup=74 drop=0 speed=0.399x     [15/01/2022, 17:03:09] [CameraUI] PorteHSV: Motion OFF (max detection time reached) [15/01/2022, 17:03:10] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:10] [CameraUI] PorteHSV: [info] frame=  450 fps= 12 q=29.0 size=     557kB time=00:00:14.96 bitrate= 305.1kbits/s dup=75 drop=0 speed=0.399x     [15/01/2022, 17:03:10] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:10] [CameraUI] PorteHSV: [info] frame=  456 fps= 12 q=30.0 size=     567kB time=00:00:15.16 bitrate= 306.0kbits/s dup=76 drop=0 speed=0.399x     [15/01/2022, 17:03:11] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:11] [CameraUI] PorteHSV: [info] frame=  462 fps= 12 q=30.0 size=     572kB time=00:00:15.36 bitrate= 305.0kbits/s dup=77 drop=0 speed=0.399x     [15/01/2022, 17:03:11] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:11] [CameraUI] PorteHSV: [info] frame=  468 fps= 12 q=30.0 size=     581kB time=00:00:15.56 bitrate= 305.5kbits/s dup=78 drop=0 speed=0.399x     [15/01/2022, 17:03:12] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:12] [CameraUI] PorteHSV: [info] frame=  474 fps= 12 q=29.0 size=     587kB time=00:00:15.76 bitrate= 304.8kbits/s dup=79 drop=0 speed=0.399x     [15/01/2022, 17:03:12] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:12] [CameraUI] PorteHSV: [info] frame=  480 fps= 12 q=30.0 size=     596kB time=00:00:15.96 bitrate= 305.6kbits/s dup=80 drop=0 speed=0.399x     [15/01/2022, 17:03:13] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:13] [CameraUI] PorteHSV: [info] frame=  487 fps= 12 q=31.0 size=     602kB time=00:00:16.20 bitrate= 304.5kbits/s dup=81 drop=0 speed= 0.4x     [15/01/2022, 17:03:13] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:13] [CameraUI] PorteHSV: [info] frame=  493 fps= 12 q=30.0 size=     610kB time=00:00:16.40 bitrate= 304.8kbits/s dup=82 drop=0 speed= 0.4x     [15/01/2022, 17:03:14] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:14] [CameraUI] PorteHSV: [info] frame=  499 fps= 12 q=30.0 size=     616kB time=00:00:16.60 bitrate= 304.1kbits/s dup=83 drop=0 speed= 0.4x     [15/01/2022, 17:03:14] [CameraUI] PorteHSV: [verbose] *** 1 dup! [15/01/2022, 17:03:14] [CameraUI] PorteHSV: [info] frame=  505 fps= 12 q=31.0 size=     650kB time=00:00:16.80 bitrate= 316.9kbits/s dup=84 drop=0 speed= 0.4x     [15/01/2022, 17:03:14] [CameraUI] PorteHSV: Stop stream requested [15/01/2022, 17:03:14] [CameraUI] PorteHSV: Stopped video stream. [15/01/2022, 17:03:14] [CameraUI] PorteHSV: FFmpeg exited with code: null and signal: SIGKILL (Expected)
But when i start record from motion
`15/01/2022, 17:01:09] [CameraUI] MQTT: on (homebridge/porte)
[15/01/2022, 17:01:09] [CameraUI] PorteHSV: Motion ON
[15/01/2022, 17:01:09] [CameraUI] PorteHSV: Video fragments requested from HSV
[15/01/2022, 17:01:09] [CameraUI] PorteHSV: Replacing audio with a dummy track, audio source not found or timed out during probe stream (recording)
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: Start recording...
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: Recording command: /usr/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -re -i http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=50&maxfps=10&buffer=1000&user=julien&pass=pass -f lavfi -i anullsrc=cl=1 -shortest -f mp4 -sn -dn -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level:v 3.1 -b:v 2000k -force_key_frames expr:eq(t,n_forced*4) -r 30 -vf scale=w=1920:h=1080:force_original_aspect_ratio=1,pad=1920:1080:(ow-iw)/2:(oh-ih)/2 -bsf:a aac_adtstoasc -acodec libfdk_aac -profile:a aac_low -ar 32k -b:a 64k -ac 1 -movflags frag_keyframe+empty_moov+default_base_moof -max_muxing_queue_size 1024 tcp://<IP_ADDRESS>:15213
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: Input #0, mpjpeg, from 'http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=50&maxfps=10&buffer=1000&user=julien&pass=pass':
Duration: N/A, bitrate: N/A
Stream #0:0
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: : Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 640x360 [SAR 1:1 DAR 16:9], 25 tbr, 25 tbn, 25 tbc
Input #1, lavfi, from 'anullsrc=cl=1':
Duration: N/A, start: 0.000000, bitrate: 352 kb/s
Stream #1:0: Audio: pcm_u8, 44100 Hz, 1 channels (FL), u8, 352 kb/s
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: Recording started
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: Stream mapping:
Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264))
Stream #1:0 -> #0:1 (pcm_u8 (native) -> aac (libfdk_aac))
Press [q] to stop, [?] for help
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: [swscaler @ 0x2d4abc0] deprecated pixel format used, make sure you did set range correctly
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: [libx264 @ 0x2cf0f90] using SAR=1/1
[libx264 @ 0x2cf0f90]
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: frame MB size (120x68) > level limit (3600)
[libx264 @ 0x2cf0f90] MB rate (244800) > level limit (108000)
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: [libx264 @ 0x2cf0f90] using cpu capabilities: ARMv6 NEON
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: [libx264 @ 0x2cf0f90] profile Constrained Baseline, level 3.1, 4:2:0, 8-bit
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: [libx264 @ 0x2cf0f90] 264 - core 160 - H.264/MPEG-4 AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html - options: cabac=0 ref=2 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=2000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: Output #0, mp4, to 'tcp://<IP_ADDRESS>:15213':
Metadata:
encoder         : Lavf58.45.100
Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 2000 kb/s, 30 fps, 15360 tbn, 30 tbc
Metadata:
encoder         : Lavc58.91.100 libx264
Side data:
cpb: bitrate max/min/avg: 0/0/2000000 buffer size: 0 vbv_delay: N/A
Stream #0:1: Audio: aac (libfdk_aac) (LC) (mp4a / 0x6134706D), 32000 Hz, mono, s16, 64 kb/s
Metadata:
encoder         : Lavc58.91.100 libfdk_aac
[15/01/2022, 17:01:10] [CameraUI] PorteHSV: frame=    6 fps=0.0 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=1 drop=0 speed=   0x
[15/01/2022, 17:01:11] [CameraUI] PorteHSV: frame=   10 fps=9.6 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=2 drop=0 speed=   0x
[15/01/2022, 17:01:11] [CameraUI] PorteHSV: frame=   16 fps= 10 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=3 drop=0 speed=   0x
[15/01/2022, 17:01:12] [CameraUI] PorteHSV: frame=   20 fps=9.8 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=3 drop=0 speed=   0x
[15/01/2022, 17:01:12] [CameraUI] PorteHSV: frame=   26 fps= 10 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=4 drop=0 speed=   0x
[15/01/2022, 17:01:13] [CameraUI] PorteHSV: frame=   32 fps= 10 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=5 drop=0 speed=   0x
[15/01/2022, 17:01:13] [CameraUI] PorteHSV: frame=   37 fps= 10 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=6 drop=0 speed=   0x
[15/01/2022, 17:01:15] [CameraUI] PorteHSV: frame=   44 fps=9.2 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=7 drop=0 speed=   0x
[15/01/2022, 17:01:15] [CameraUI] PorteHSV: frame=   50 fps=9.3 q=50.0 size=       1kB time=00:00:00.09 bitrate= 102.4kbits/s dup=8 drop=0 speed=0.0178x
[15/01/2022, 17:01:16] [CameraUI] PorteHSV: frame=   60 fps= 10 q=37.0 size=       1kB time=00:00:00.41 bitrate=  23.6kbits/s dup=10 drop=0 speed=0.0704x
[15/01/2022, 17:01:16] [CameraUI] PorteHSV: frame=   65 fps= 10 q=35.0 size=       1kB time=00:00:00.60 bitrate=  16.2kbits/s dup=11 drop=0 speed=0.0938x
[15/01/2022, 17:01:17] [CameraUI] PorteHSV: frame=   73 fps= 10 q=35.0 size=       1kB time=00:00:00.86 bitrate=  11.4kbits/s dup=12 drop=0 speed=0.122x
[15/01/2022, 17:01:17] [CameraUI] PorteHSV: frame=   80 fps= 11 q=35.0 size=       1kB time=00:00:01.08 bitrate=   9.0kbits/s dup=13 drop=0 speed=0.143x
[15/01/2022, 17:01:18] [CameraUI] PorteHSV: frame=   85 fps= 10 q=35.0 size=       1kB time=00:00:01.28 bitrate=   7.7kbits/s dup=14 drop=0 speed=0.157x
[15/01/2022, 17:01:18] [CameraUI] PorteHSV: Closing recording process
[15/01/2022, 17:01:18] [CameraUI] Resetting motion state because HSV closed recording with reason "3"
[15/01/2022, 17:01:18] [CameraUI] PorteHSV: FFMPEG socket closed during read for 8 bytes!
[15/01/2022, 17:01:18] [CameraUI] PorteHSV: Skip saving the recording, the file might be corrupted because the recording process was cancelled by HSV
[15/01/2022, 17:01:18] [CameraUI] PorteHSV: FFmpeg recording process exited (expected)
[15/01/2022, 17:01:24] [CameraUI] PorteHSV: Motion OFF - Motion handler timeout.`
Do you know why ? not good resolution ? i see encoding 1980 but source 1280
I'm on RPI4
Thanks for help

@fennec622
Can you post a screenshot from the camera's own settings? It works best with a H264 stream. The zone minder has a mjpeg stream. Can you change it to H264 in the camera settings?

ah sry i read the title now
If your camera does not provide a h264 stream, there is not much to do. Try disabling "readRate" in your config.json
Other settings looks good

Sreenshot from zoneminder ?
I don't think zoneminder can restream on H264

@fennec622
Nvm, if h264 is not possible, i dont need the screenshot.
Just disable "readRate" in your config.json and it should work

yeah read my last post ^^
disable "readRate" in your config.json

@fennec622
Nvm, if h264 is not possible, i dont need the screenshot.
Just disable "readRate" in your config.json and it should work

Thanks i try

Sorry same
[15/01/2022, 17:48:23] [CameraUI] MQTT: on (homebridge/porte)
[15/01/2022, 17:48:23] [CameraUI] PorteHSV: Motion ON
[15/01/2022, 17:48:23] [CameraUI] PorteHSV: Video fragments requested from HSV
[15/01/2022, 17:48:23] [CameraUI] PorteHSV: Replacing audio with a dummy track, audio source not found or timed out during probe stream (recording)
[15/01/2022, 17:48:23] [CameraUI] PorteHSV: Start recording...
[15/01/2022, 17:48:23] [CameraUI] PorteHSV: Recording command: /usr/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -i http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=50&maxfps=10&buffer=1000&user=julien&pass=220926Julon@ -f lavfi -i anullsrc=cl=1 -shortest -f mp4 -sn -dn -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level:v 3.1 -b:v 2000k -force_key_frames expr:eq(t,n_forced*4) -r 30 -vf scale=w=1920:h=1080:force_original_aspect_ratio=1,pad=1920:1080:(ow-iw)/2:(oh-ih)/2 -bsf:a aac_adtstoasc -acodec libfdk_aac -profile:a aac_low -ar 32k -b:a 64k -ac 1 -movflags frag_keyframe+empty_moov+default_base_moof -max_muxing_queue_size 1024 tcp://<IP_ADDRESS>:35206
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: Input #0, mpjpeg, from 'http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=50&maxfps=10&buffer=1000&user=julien&pass=220926Julon@':
Duration: N/A, bitrate: N/A
[15/01/2022, 17:48:24] [CameraUI] PorteHSV:     Stream #0:0: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 640x360 [SAR 1:1 DAR 16:9], 25 tbr, 25 tbn, 25 tbc
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: Input #1, lavfi, from 'anullsrc=cl=1':
Duration: N/A, start: 0.000000, bitrate: 352 kb/s
Stream #1:0: Audio: pcm_u8, 44100 Hz, 1 channels (FL), u8, 352 kb/s
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: Recording started
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: Stream mapping:
Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264))
Stream #1:0 -> #0:1 (pcm_u8 (native) -> aac (libfdk_aac))
Press [q] to stop, [?] for help
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: [swscaler @ 0x2845390] deprecated pixel format used, make sure you did set range correctly
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: [libx264 @ 0x27fdbc0] using SAR=1/1
[libx264 @ 0x27fdbc0] frame MB size (120x68) > level limit (3600)
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: [libx264 @ 0x27fdbc0] MB rate (244800) > level limit (108000)
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: [libx264 @ 0x27fdbc0] using cpu capabilities: ARMv6 NEON
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: [libx264 @ 0x27fdbc0] profile Constrained Baseline, level 3.1, 4:2:0, 8-bit
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: [libx264 @ 0x27fdbc0] 264 - core 160 - H.264/MPEG-4 AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html - options: cabac=0 ref=2 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=2000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: Output #0, mp4, to 'tcp://<IP_ADDRESS>:35206':
Metadata:
encoder         : Lavf58.45.100
Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 2000 kb/s, 30 fps, 15360 tbn, 30 tbc
Metadata:
encoder         : Lavc58.91.100 libx264
Side data:
cpb: bitrate max/min/avg: 0/0/2000000 buffer size: 0 vbv_delay: N/A
Stream #0:1: Audio: aac (libfdk_aac) (LC) (mp4a / 0x6134706D), 32000 Hz, mono, s16, 64 kb/s
Metadata:
encoder         : Lavc58.91.100 libfdk_aac
[15/01/2022, 17:48:24] [CameraUI] PorteHSV: frame=    7 fps=0.0 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=1 drop=0 speed=   0x
[15/01/2022, 17:48:25] [CameraUI] PorteHSV: frame=   13 fps= 13 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=2 drop=0 speed=   0x
[15/01/2022, 17:48:25] [CameraUI] PorteHSV: frame=   19 fps= 12 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=3 drop=0 speed=   0x
[15/01/2022, 17:48:26] [CameraUI] PorteHSV: frame=   25 fps= 12 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=4 drop=0 speed=   0x
[15/01/2022, 17:48:26] [CameraUI] PorteHSV: frame=   31 fps= 12 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=5 drop=0 speed=   0x
[15/01/2022, 17:48:27] [CameraUI] PorteHSV: frame=   37 fps= 12 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=6 drop=0 speed=   0x
[15/01/2022, 17:48:28] [CameraUI] PorteHSV: frame=   44 fps= 10 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=7 drop=0 speed=   0x
[15/01/2022, 17:48:29] [CameraUI] PorteHSV: frame=   50 fps= 10 q=40.0 size=       1kB time=00:00:00.09 bitrate= 102.4kbits/s dup=8 drop=0 speed=0.0193x
[15/01/2022, 17:48:29] [CameraUI] PorteHSV: [mpjpeg @ 0x27f56f0] Thread message queue blocking; consider raising the thread_queue_size option (current value: 8)
[15/01/2022, 17:48:29] [CameraUI] PorteHSV: frame=   58 fps= 11 q=37.0 size=       1kB time=00:00:00.35 bitrate=  27.9kbits/s dup=10 drop=0 speed=0.0641x
[15/01/2022, 17:48:30] [CameraUI] PorteHSV: frame=   64 fps= 11 q=36.0 size=       1kB time=00:00:00.53 bitrate=  18.4kbits/s dup=11 drop=0 speed=0.0878x
[15/01/2022, 17:48:30] [CameraUI] PorteHSV: frame=   71 fps= 11 q=36.0 size=       1kB time=00:00:00.76 bitrate=  12.8kbits/s dup=12 drop=0 speed=0.115x
[15/01/2022, 17:48:31] [CameraUI] PorteHSV: frame=   78 fps= 11 q=36.0 size=       1kB time=00:00:01.02 bitrate=   9.6kbits/s dup=13 drop=0 speed=0.143x
[15/01/2022, 17:48:31] [CameraUI] PorteHSV: frame=   83 fps= 11 q=36.0 size=       1kB time=00:00:01.18 bitrate=   8.3kbits/s dup=14 drop=0 speed=0.154x
[15/01/2022, 17:48:32] [CameraUI] PorteHSV: frame=   90 fps= 11 q=36.0 size=       1kB time=00:00:01.44 bitrate=   6.8kbits/s dup=15 drop=0 speed=0.171x
[15/01/2022, 17:48:33] [CameraUI] PorteHSV: Closing recording process
[15/01/2022, 17:48:33] [CameraUI] Resetting motion state because HSV closed recording with reason "3"
[15/01/2022, 17:48:33] [CameraUI] PorteHSV: FFMPEG socket closed during read for 8 bytes!
[15/01/2022, 17:48:33] [CameraUI] PorteHSV: Skip saving the recording, the file might be corrupted because the recording process was cancelled by HSV
[15/01/2022, 17:48:33] [CameraUI] PorteHSV: FFmpeg recording process exited (expected)
[15/01/2022, 17:48:38] [CameraUI] PorteHSV: Motion OFF - Motion handler timeout.

Ah i see, its because FPS. Its too low.
Can you change FPS to > 20 in the camera settings?

Yes for limit CPU usage in analyse in zoneminder i degrease to 10 FPS
I try to 20
thanks

With live i have fps 30
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: Stream command: /usr/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel level+verbose -i http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=100&maxfps=30&buffer=1000&user=julien&pass=pass -f lavfi -i anullsrc=cl=1 -shortest -an -sn -dn -r 30 -vcodec libx264 -pix_fmt yuv420p -color_range mpeg -f rawvideo -preset ultrafast -tune zerolatency -filter:v scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease,scale=trunc(iw/2)*2:trunc(ih/2)*2 -b:v 299k -bufsize 598k -maxrate 299k -payload_type 99 -ssrc 4769339 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params 6aqiOrNflZ+aB82gUFD45NAZ9IQhsWHJBRtd0HbY srtp://<IP_ADDRESS>:51776?rtcpport=51776&pkt_size=1318 -progress pipe:1
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [tcp @ 0x404e000] [verbose] Starting connection attempt to <IP_ADDRESS> port 80
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [tcp @ 0x404e000] [verbose] Successfully connected to <IP_ADDRESS> port 80
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info] Input #0, mpjpeg, from 'http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=100&maxfps=30&buffer=1000&user=julien&pass=220926Julon@':
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info]   Duration: N/A, bitrate: N/A
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info]     Stream #0:0: Video: mjpeg (Baseline), 1 reference frame, yuvj420p(pc, bt470bg/unknown/unknown, center), 1280x720 [SAR 1:1 DAR 16:9], 25 tbr, 25 tbn, 25 tbc
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [Parsed_anullsrc_0 @ 0x405a500] [verbose] sample_rate:44100 channel_layout:'1 channels (FL)' nb_samples:1024
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info] Input #1, lavfi, from 'anullsrc=cl=1':
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info]   Duration: N/A, start: 0.000000, bitrate: 352 kb/s
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info]     Stream #1:0: Audio: pcm_u8, 44100 Hz, 1 channels (FL), u8, 352 kb/s
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info] Stream mapping:
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info]   Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264))
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [info] Press [q] to stop, [?] for help
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [Parsed_scale_0 @ 0x4055870] [verbose] w:min(1280,iw) h:min(720,ih) flags:'bicubic' interl:0
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [Parsed_scale_1 @ 0x405f7b0] [verbose] w:trunc(iw/2)*2 h:trunc(ih/2)*2 flags:'bicubic' interl:0
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [graph 0 input from stream 0:0 @ 0x4060440] [verbose] w:1280 h:720 pixfmt:yuvj420p tb:1/25 fr:25/1 sar:1/1
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [Parsed_scale_0 @ 0x4055870] [verbose] w:1280 h:720 fmt:yuvj420p sar:1/1 -> w:1280 h:720 fmt:yuvj420p sar:1/1 flags:0x4
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [swscaler @ 0x40ad4e0] [warning] deprecated pixel format used, make sure you did set range correctly
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [Parsed_scale_1 @ 0x405f7b0] [verbose] w:1280 h:720 fmt:yuvj420p sar:1/1 -> w:1280 h:720 fmt:yuv420p sar:1/1 flags:0x4
[15/01/2022, 18:23:58] [CameraUI] PorteHSV: [libx264 @ 0x404f090] [info] using SAR=1/1
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [libx264 @ 0x404f090] [info] using cpu capabilities: ARMv6 NEON
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [libx264 @ 0x404f090] [info] profile Constrained Baseline, level 3.1, 4:2:0, 8-bit
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info] Output #0, rtp, to 'srtp://<IP_ADDRESS>:51776?rtcpport=51776&pkt_size=1318':
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info]   Metadata:
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info]     encoder         : Lavf58.45.100
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info]     Stream #0:0: Video: h264 (libx264), 1 reference frame, yuv420p(tv, center), 1280x720 [SAR 1:1 DAR 16:9], q=-1--1, 299 kb/s, 30 fps, 90k tbn, 30 tbc
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info]     Metadata:
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info]       encoder         : Lavc58.91.100 libx264
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info]     Side data:
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info]       cpb: bitrate max/min/avg: 299000/0/299000 buffer size: 598000 vbv_delay: N/A
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [verbose] *** 1 dup!
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [verbose] *** 1 dup!
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [verbose] *** 1 dup!
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [info] frame=   17 fps=0.0 q=39.0 size=      19kB time=00:00:00.53 bitrate= 299.4kbits/s dup=3 drop=0 speed=   1x
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: Getting the first frames took 0.763 seconds.
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [verbose] *** 1 dup!
[15/01/2022, 18:23:59] [CameraUI] PorteHSV: [verbose] *** 1 dup!
[15/01/2022, 18:24:00] [CameraUI] PorteHSV: [verbose] *** 1 dup!
[15/01/2022, 18:24:00] [CameraUI] PorteHSV: [info] frame=   34 fps= 32 q=36.0 size=      35kB time=00:00:01.10 bitrate= 261.3kbits/s dup=6 drop=0 speed=1.05x
[15/01/2022, 18:24:00] [CameraUI] PorteHSV: [verbose] *** 1 dup!
But on HSV record just fps 18 max i don't know why
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: Start recording...
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: Recording command: /usr/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -i http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=100&maxfps=30&buffer=1000&user=julien&pass=pass -f lavfi -i anullsrc=cl=1 -shortest -f mp4 -sn -dn -vcodec libx264 -pix_fmt yuv420p -profile:v baseline -level:v 3.1 -b:v 2000k -force_key_frames expr:eq(t,n_forced*4) -r 30 -vf scale=w=1920:h=1080:force_original_aspect_ratio=1,pad=1920:1080:(ow-iw)/2:(oh-ih)/2 -bsf:a aac_adtstoasc -acodec libfdk_aac -profile:a aac_low -ar 32k -b:a 64k -ac 1 -movflags frag_keyframe+empty_moov+default_base_moof -max_muxing_queue_size 1024 tcp://<IP_ADDRESS>:12533
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: Input #0, mpjpeg, from 'http://<IP_ADDRESS>/zm/cgi-bin/nph-zms?mode=jpeg&monitor=2&scale=100&maxfps=30&buffer=1000&user=julien&pass=pass':
Duration: N/A, bitrate: N/A
Stream #0:0: Video: mjpeg (Baseline), yuvj420p(pc, bt470bg/unknown/unknown), 1280x720 [SAR 1:1 DAR 16:9], 25 tbr, 25 tbn, 25 tbc
[15/01/2022, 18:25:31] [CameraUI] PorteHSV:
Input #1, lavfi, from 'anullsrc=cl=1':
Duration: N/A, start: 0.000000, bitrate: 352 kb/s
Stream #1:0: Audio: pcm_u8, 44100 Hz, 1 channels (FL), u8, 352 kb/s
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: Recording started
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: Stream mapping:
Stream #0:0 -> #0:0 (mjpeg (native) -> h264 (libx264))
Stream #1:0 -> #0:1 (pcm_u8 (native) -> aac (libfdk_aac))
Press [q] to stop, [?] for help
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: [swscaler @ 0x3694b10] deprecated pixel format used, make sure you did set range correctly
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: [libx264 @ 0x3655da0] using SAR=1/1
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: [libx264 @ 0x3655da0] frame MB size (120x68) > level limit (3600)
[libx264 @ 0x3655da0] MB rate (244800) > level limit (108000)
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: [libx264 @ 0x3655da0] using cpu capabilities: ARMv6 NEON
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: [libx264 @ 0x3655da0] profile Constrained Baseline, level 3.1, 4:2:0, 8-bit
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: [libx264 @ 0x3655da0] 264 - core 160 - H.264/MPEG-4 AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html - options: cabac=0 ref=2 deblock=1:0:0 analyse=0x1:0x111 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=6 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=abr mbtree=1 bitrate=2000 ratetol=1.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
[15/01/2022, 18:25:31] [CameraUI] PorteHSV: Output #0, mp4, to 'tcp://<IP_ADDRESS>:12533':
Metadata:
encoder         : Lavf58.45.100
Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 2000 kb/s, 30 fps, 15360 tbn, 30 tbc
Metadata:
encoder         : Lavc58.91.100 libx264
Side data:
cpb: bitrate max/min/avg: 0/0/2000000 buffer size: 0 vbv_delay: N/A
Stream #0:1: Audio: aac (libfdk_aac) (LC) (mp4a / 0x6134706D), 32000 Hz, mono, s16, 64 kb/s
Metadata:
encoder         : Lavc58.91.100 libfdk_aac
[15/01/2022, 18:25:32] [CameraUI] PorteHSV: frame=   10 fps=0.0 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=2 drop=0 speed=   0x
[15/01/2022, 18:25:32] [CameraUI] PorteHSV: [mpjpeg @ 0x36496f0] Thread message queue blocking; consider raising the thread_queue_size option (current value: 8)
[15/01/2022, 18:25:32] [CameraUI] PorteHSV: frame=   19 fps= 18 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=3 drop=0 speed=   0x
[15/01/2022, 18:25:33] [CameraUI] PorteHSV: frame=   29 fps= 18 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=5 drop=0 speed=   0x
[15/01/2022, 18:25:33] [CameraUI] PorteHSV: frame=   38 fps= 18 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=6 drop=0 speed=   0x
[15/01/2022, 18:25:34] [CameraUI] PorteHSV: frame=   44 fps= 15 q=0.0 size=       1kB time=00:00:00.00 bitrate=N/A dup=7 drop=0 speed=   0x
[15/01/2022, 18:25:35] [CameraUI] PorteHSV: frame=   53 fps= 15 q=39.0 size=       1kB time=00:00:00.22 bitrate=  43.9kbits/s dup=9 drop=0 speed=0.0625x
[15/01/2022, 18:25:35] [CameraUI] PorteHSV: frame=   64 fps= 15 q=32.0 size=       1kB time=00:00:00.53 bitrate=  18.4kbits/s dup=11 drop=0 speed=0.128x
[15/01/2022, 18:25:36] [CameraUI] PorteHSV: frame=   72 fps= 15 q=31.0 size=       1kB time=00:00:00.83 bitrate=  11.8kbits/s dup=12 drop=0 speed=0.175x
[15/01/2022, 18:25:37] [CameraUI] PorteHSV: frame=   79 fps= 15 q=31.0 size=       1kB time=00:00:01.08 bitrate=   9.0kbits/s dup=13 drop=0 speed=0.202x
[15/01/2022, 18:25:37] [CameraUI] PorteHSV: frame=   88 fps= 15 q=32.0 size=       1kB time=00:00:01.34 bitrate=   7.3kbits/s dup=15 drop=0 speed=0.227x
[15/01/2022, 18:25:38] [CameraUI] PorteHSV: frame=   95 fps= 15 q=31.0 size=       1kB time=00:00:01.60 bitrate=   6.1kbits/s dup=16 drop=0 speed=0.247x
[15/01/2022, 18:25:38] [CameraUI] PorteHSV: frame=  104 fps= 15 q=31.0 size=       1kB time=00:00:01.92 bitrate=   5.1kbits/s dup=17 drop=0 speed=0.274x
[15/01/2022, 18:25:39] [CameraUI] PorteHSV: frame=  110 fps= 15 q=31.0 size=       1kB time=00:00:02.11 bitrate=   4.7kbits/s dup=18 drop=0 speed=0.28x
[15/01/2022, 18:25:39] [CameraUI] PorteHSV: frame=  119 fps= 15 q=31.0 size=       1kB time=00:00:02.36 bitrate=   4.2kbits/s dup=20 drop=0 speed=0.292x
[15/01/2022, 18:25:40] [CameraUI] PorteHSV: frame=  126 fps= 15 q=31.0 size=       1kB time=00:00:02.62 bitrate=   3.7kbits/s dup=21 drop=0 speed=0.303x
[15/01/2022, 18:25:40] [CameraUI] PorteHSV: Closing recording process
[15/01/2022, 18:25:40] [CameraUI] Resetting motion state because HSV closed recording with reason "3"
[15/01/2022, 18:25:40] [CameraUI] PorteHSV: FFMPEG socket closed during read for 8 bytes!
[15/01/2022, 18:25:40] [CameraUI] PorteHSV: Skip saving the recording, the file might be corrupted because the recording process was cancelled by HSV
[15/01/2022, 18:25:40] [CameraUI] PorteHSV: FFmpeg recording process exited (expected)
[15/01/2022, 18:25:46] [CameraUI] PorteHSV: Motion OFF - Motion handler timeout.


Incompatible Execution Context

About a week ago, the action has begun to fail consistently. The error message suggests it is trying to use an execution context that my runner does not support. My runner is the latest version, self-hosted x86 (Linux).
Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node20' is not supported, use 'docker', 'node12' or 'node16' instead.')
   at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs)
   at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)

My action configuration is below.
name: Enforce PR-Issue Link Policy
on: [pull_request]

jobs:
  enforce-pr-issue-link-policy:
    runs-on: [self-hosted, linux]
    container: ubuntu:latest
    permissions:
        issues: read
        pull-requests: write
    steps:
      - uses: nearform-actions/github-action-check-linked-issues@v1
        id: check-linked-issues
        with:
          exclude-branches: "release/**, dependabot/**"
          comment: false

Any suggestions?

In the last release we upgraded the action to run on Node 20. In hindsights, we could have bumped a major version.
You can either stay on the previous version or bump your runner as described here.


Join forces?

Hi Alex,
As a quest to better learn pandas I created a series of exercises in a different form than yours.
I would like to know if you might to be interested to contribute in any way to my repo or if I can use the your exercises.
Thanks

Hi Guilherme, thanks for getting in touch. I really like the format of your exercises and the use of notebooks! I think the focus on individual topics will be of great value to people exploring pandas.
I'd be very happy to see if there's anything I can contribute to your series of exercises. In the meantime, please feel free to use/adapt any of the questions in my repo in whatever way you like.
Alex

Hi Alex,
Thank you for your message! I'm glad you liked the exercises.  After completing all topics, my plan is to create all topics in one exercise/dataset analysis and to rank the exercises to difficult level.
If have any idea or would like to contribute creating something, I would be glad to pull your request!
Best,
Gui


veebooru support?

Can we get support for veebooru.com?

Can we get support for veebooru.com?

All code for the PHP-Booru has been released: https://github.com/elitetheespeon/PHP-Booru/
There is a public API in the engine and it can easily be extended for use in this project (has not been documented yet though.)


SAG Mill Sandstone Recipe == item dupe

well, it is only sand but endless niter/saltpeter is a bit game breaking
the sag mill outputs more sand than used in the recipe when using dark steel ball, maybe tune it by default a bit more to the pulverizer, like main output 2 sand always and secondary ONLY niter/saltpeter with slightly higger 25% chance

Fixed via https://github.com/SleepyTrousers/EnderIO/commit/b22832fd6af02430c06cc206ac041f940c4da92f

not fixed imho, i commented on the commit

the new builds are pretty more balanced


Android] User should not able to proceed for the payment or payment request using his/her own number.

App version: zero-sync build: Staging build v1.5.0 (101548577)
Repro on:  Galaxy Grand Prime (5.1.1), Samsung J7 Prime (6.0.1)
Testing Account:<PHONE_NUMBER>/Backup Kay
Pre-Condition: User should save his/her number in the contact list.
Repro Steps:

Launch the app.
Tap on + Tab.
Search the user’s own number.
Tap on it and try to proceed for payment.
Observe Payment received activity is shown on the Activity section from the wallet tab.

Investigation: total Celo dollars amount is not changed.
Impact: Total Celo dollars amount does not match with Activity shown on the Activity section.
Current Behavior: User should not be able to proceed for the payment or payment request using his/her own number.
Expected Behavior: User-friendly message should show.
Attachment: Android_PaymentWithOwnNumber.mp4 (Bug observe after 39 sec)

We intentionally want to allow sending to yourself. It's useful for dev testing and/or users who want to test a transaction without losing money

Okay, thanks for the update.


Feature/constraints model

Context
Completed models to handle price optimisation constraints and created basic tests.
Changes

Added Constraint model
Added ConstraintParameter model
Added ConstraintParameterRelationship model
Removed Weight and RequiredHyperparameter models (currently not relevant, will add SavedModel model in future PR)
Created basic tests

Considerations
Will add SavedModel model and related endpoint in the future to handle trained models.
A ConstraintBlock is basically one set of many Constraints which will be used in a price optimisation process.
A Constraint is essentially a single equation, e.g. x + y <= 0
A ConstraintBlock has several ConstraintParameters, which appear in the Constraint equations, thus, they have a ManyToMany relationship which is modeled using the ConstraintParameterRelationship.

Just to clarify:

So a ConstraintParameter's name is something like a particular item? By extension, all constraints in a constraint block will always have the same few constraint parameters to use in the equation?
What is the Constraint's name? Is it just a generic name for identification purposes e.g. Constraint1, Constraint2?
For the coefficient on ConstraintParameterRelationship, is it referring to "0" like in the example x + y <= 0?
If I understand correctly. This is the current class Diagram and my issue with it is there is too much interdependence between the classes:

Why not shift the coefficient as a field under Constraint instead and model it like that?

Yes, a ConstraintParameter will be like "Fish Burger Price", "Big Mac Price", etc. All Constraints in a ConstraintBlock should reuse ConstraintParameters.
A Constraint's name can be like "Big Mac more expensive than fish burger", or "No arbitrage fries". I think Meng Siong's constraints also had some names.
Sorry, the one you mentioned should be another field under Constraint, I forgot to add. The coefficient under ConstraintParameterRelationship is for example "x + 2y <= 0", ConstraintParameter needs the coefficient of 2.
The reason why we need ConstraintParameterRelationship is because of the coefficient.


Installation Dependencies

https://github.com/zerossl/zerossl-bot/blob/705969881fad29497feb376a0e198fbae8d98746/README.md?plain=1#L10
https://github.com/zerossl/zerossl-bot/blob/705969881fad29497feb376a0e198fbae8d98746/zerossl-bot.sh#L16
If I'm reading these correctly, the instructions should specify python is required too.

@miqrogroove Have added the missing information to the installation instructions.


Sachin

Added "Publish Test reports" and "Generate code coverage reports" to Gulp and Grunt tasks. Also written some unit tests for the same.

Hi @Sachin077, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Sachin Aggarwal). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Add opengraph-image and twitter-image

https://nextjs.org/docs/app/api-reference/file-conventions/metadata/opengraph-image
It'd be nice if the site had these properties defined so it looked better when the link is shared.

Hey @Johngeorgesample
Assign this to me so i add open graph image for the site.


Update manage-authentication-in-database-engine-powershell.md

On line 67. in the Set-Location statement, the drive name needs to have a colon to be recognized as a drive name.
Also, I changed the DOS commands to PoSh commands (lines 66, 67), since this is PoSh.

@JediSQL : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


cleo does not handle SIGPIPE / errno.EPIPE

Discovered this trying to work around sdispater/poetry#106 doing something along the lines of poetry show -v | head -n1 | ...
Using the GreetCommand given in the README:
% python app.py | head
Console Tool

Usage:
  command [options] [arguments]

Options:
  -h, --help                      Display this help message
  -q, --quiet                     Do not output any message
  -V, --version                   Display this application version
      --ansi                      Force ANSI output

  [BrokenPipeError]
  [Errno 32] Broken pipe

list [--raw] [--format FORMAT] [--] [<namespace>]

Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='UTF-8'>
BrokenPipeError: [Errno 32] Broken pipe
% echo $?
0

This is the cause of https://github.com/sdispater/poetry/issues/839. In that issue I reference a StackOverflow post with a solution. Here is the short version:
# in cleo/outputs/stream_output.py
from signal import signal, SIGPIPE, SIG_DFL
signal(SIGPIPE, SIG_DFL)

The process writing to the pipe will now be terminated when it receives SIGPIPE (i.e. when the other end of the pipe is closed prematurely), rather than raising a BrokenPipeError.
I would be more than willing to put together a PR for this since it's very little code.

Facing the same issue while doing the same thing. @zmitchell did you ever figure out a solution that doesn't require editing the source?


Subtitles named in the wrong episode order (starts at 2nd subtitle for 1st episode)

renamethemsubs.exe on Windows 10 renames episode 2 subtitles for episode 1 and uses the first episodes subtitle on the last episode
what am I doing wrongt?

I discovered why this is happening. The whole process can get screwed if the episodes have a number in the title, so it would make sense to update it to somehow ignore any other numbers in the string if SXXEXX exists?
I ended up removing the numbers in the titles for all episodes (which were a lot) I had already removed (1), (2), (3), (4), (5), (6), (7), (8) which were multi-part episodes in the season, you can see I forgot (9) in the above screenshot.
Only when all of the numbers were removed, did the subtitles rename correctly.


[WR] add exception column to results table and fill on fail

Pivotal Card
What do you think this as a start? We'd add the cause of the exception to the results table for it to then be shown on the Metis side.

I'm not sure about actually showing the exception to the user, but this is helpful. What about adding an end time to the results table?

I was initially starting with that but the card says we should add as much detailed information as possible -- which makes sense. Just saying the feed failed doesn't really help. Unless we can assume we'll always be handling anything that throws an exception, in which case it may not matter. I'll check with Maria.  :)

LGTM


Adding Scalar to mocked functions

Discussed in https://github.com/rajivsarvepalli/mock-alchemy/discussions/153

Originally posted by jonyscathe October  6, 2021
Hi,
We are using a lot of scalar() in our project: https://docs.sqlalchemy.org/en/14/orm/query.html#sqlalchemy.orm.Query.scalar
Usually to get a single value as per SQLAlchemys example session.query(Item.id, Item.name).scalar()
Is there currently any way to do this with mock-alchemy?
Currently the best option I seem to have seems to be after creating a mock_session to make a new boundary lambda for scalar() such as:
def get_scalar(rows: list[Any]) -> Any:
    if len(rows) == 1:
        for key in rows[0].__mapper__.c.keys():
            if getattr(rows[0], key) is not None:
                return getattr(rows[0], key)
    elif len(rows) > 1:
        raise MultipleResultsFound("Multiple rows were found for scalar()")
    else:
        return None

mock_session = UnifiedAlchemyMagicMock(
        data=[...]
)
mock_session.boundary['scalar']= lambda x: get_scalar(x)
mock_session.scalar = AlchemyMagicMock(side_effect=partial(mock_session._get_data, _mock_name='scalar'))

Is there some better way to be mocking scalar with the UnifiedAlchemyMagicMocks?
Or if there is the best way, could we get scalar() added to the standard boundary dict?

Per Discussion, adding scalar to default boundary dict.


Could not start debug with pnpm project.

Describe the bug
Could not start debug with pnpm project than do not has direct vite dependency, and "vitest.commandLine" could not be applied to debug.
To Reproduce
Steps to reproduce the behavior on the example project:

Edit 'package.json' and remove vite.
Install pnpm globally
change package manager to 'pnpm' in setup.mjs. (do not use npm install or yarn before，if so，remove node_modules).
Start a debug with the extension.
The debug session closed with error: "cannot find module 'vite'"

Expected behavior
Successfully run the debug.
Additional context
I tried to use different methods to start vitest in terminal，all the flollwing commands are run successfully.
pnpx vitest
npx vitest
./node_modules/.bin/vitest

but the following command could not run with pnpm:
node ./node_modules/vitest/vitest.mjs

with the same error mentioned previously.
also, I've edited "vitest.commandLine" to different values and it seems have no impact on debug.
Running and watch has no issues.
Possibly a minor change here?
https://github.com/vitest-dev/vscode/blob/dd70a041b8d955ed821b53684104a1f630044ea0/src/runHandler.ts#L291
Environment
{
"System": {
"OS": "macOS 12.5"
},
"Binaries": {
"Node": {
"version": "14.16.0",
"path": "~/.nvm/versions/node/v14.16.0/bin/node"
},
"Yarn": {
"version": "1.22.19",
"path": "~/.nvm/versions/node/v14.16.0/bin/yarn"
},
"npm": {
"version": "6.14.11",
"path": "~/.nvm/versions/node/v14.16.0/bin/npm"
}
},
"IDEs": {
"VSCode": {
"version": "1.69.2",
"path": "/usr/local/bin/code"
}
},
"npmPackages": {
"vite": {
"installed": "2.9.14",
"wanted": "^2.9.9"
},
"vitest": {
"installed": "0.12.10",
"wanted": "^0.12.6"
}
}
}

The same goes for me. I have a project using pnpm (dayjs v2.0 e.g. branch next) and when I updated Vitest from v0.17.0 to v0.21.1 I got the above mentioned effect. The tests run without problems in the test pane of VSCode.
My environment:
OS: windows 10
node: v16.15.1
VSCode: 1.70.0
Vitest Extension: 0.2.24
When starting the debug session in the debug pane of VSCode, I get the following output in the (debuggers?) terminal:
D:\Projekte\github\dayjs-2.0> d: && cd d:\Projekte\github\dayjs-2.0 && cmd /C "set "NODE_OPTIONS=--require "c:/Program Files/Microsoft VS Code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js" --inspect-publish-uid=http" && set "VSCODE_INSPECTOR_OPTIONS={"inspectorIpc":"\\\\.\\pipe\\node-cdp.5392-1.sock","deferredMode":false,"waitForDebugger":"","execPath":"C:\\Program Files\\nodejs\\node.exe","onlyEntrypoint":false,"autoAttachMode":"always","fileCallback":"C:\\Users\\ENTWIC~1\\AppData\\Local\\Temp\\node-debug-callback-7142848cae1a20bf"}" && "C:\Program Files\nodejs\node.exe" .\node_modules\vitest\vitest.mjs run tests\constructor.test.ts "
Debugger attached.
 MISSING DEP  Can not find dependency 'vite'

? Do you want to install vite? » (y/N)

complaining about a missing vitest. Looking in the node_modules directory, vitest is instaleed not in the node_modules directory directly, but in the subdirectory node_modules of the vitest directory:

Same for me with pnpm. pnpm test works just fine, and my custom debug vscode task works just fine. I'm on windows.

My pnpm project is fixed this problem with that .vscode/settings.json.
{
    "vitest.commandLine": "pnpm vitest"
}

env

pnpm vitest --version

vitest/0.33.0 linux-x64 node-v20.8.0

pnpm --version

8.7.5

OS

mcr.microsoft.com/devcontainers/javascript-node:20-bookworm

log
/usr/local/bin/node ./node_modules/vitest/vitest.mjs vitest /app/tests/xxx.spec.ts -t sample fetch mock should GET done rignt --api.port 41355 --api.host <IP_ADDRESS>
DEV  v0.33.0 /app
vendor-cli-api.iriqwoerupo.js:12594
API started at http://<IP_ADDRESS>:41355

Broken my config after update to vitest v1.*.*..
vitest.commandLine: "pnpm vitest" in the settings.json is also not working.

[INFO 4:06:23 AM] Vitest Workspace [app]: Vitest version = undefined

env

OS: Linux 4fbc5bb9c4a8 <IP_ADDRESS>-microsoft-standard-WSL2 # 1 SMP Mon Aug 7 19:01:48 UTC 2023 x86_64 GNU/Linux
Vitest: vitest/1.3.1 linux-x64 node-v20.11.0
VSCode

Version: 1.86.2 (system setup)
Commit: 903b1e9d8990623e3d7da1df3d33db3e42d80eda
Date: 2024-02-13T19:40:56.878Z
Electron: 27.2.3
ElectronBuildId: 26908389
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22631

PoC
https://github.com/ShortArrow/poc_vitest_extension_in_devcontainer

This should be fixed in pre-release 0.5.0 and higher. Note that the extension now requires Vitest 1.4.0 or higher.


Process h265d - use C++ primitives: memcpy => std::copy

Issue: MDP-50957

Please take a closer look at umc_media_data.h
Original:
virtual void* GetDataPointer(void) { return m_pDataPointer; }
Now:
virtual uint8_t* GetDataPointer(void) { return m_pDataPointer; }
This method was changed because std::copy function does not accept void* as 3 parameter.


Support Per-app Language Preferences

Android 13 introduced the option for users to set a per-app language preference. It would be nice if we could support this too.

I will work on it


1.1.x: add pins for libgcc,libstdcxx

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Anaconda just updated toolchains and associated libraries. One of the changes is breaking out libgomp into its own library.
This PR addresses 1.1.x: let's pin to libraries before this change.
Subsequent patches will be needed for any feedstocks that use OpenMP to use these pins and arguably we should add them across the board to the host section of feedstocks.
https://github.com/open-ce/open-ce/issues/315
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

On hold. Anaconda pulled the new libgcc and toolchain packages for now.


[satellite] Add security advisory link for 6.9.10

https://access.redhat.com/errata/RHSA-2022:8532

Will become visible with #2861.


Number does not required localization

Coverage decreased (-0.01%) to 35.408% when pulling 109dbabf2b7953949ac298ca1dcf58b56cf92e7b on qingweibinary:qingwei/trivial_fix_on_digit into 61d06d9b3ca4873849b8a1eb57689983aac161ef on binary-com:master.

Rofl. My mistake ;)


get cashflow null dataframe

I can't get the data
I saw a project compiled by a friend myself, I tried to compile
pip install git+https://github.com/rodrigobercini/yfinance.git
but failed
(venv) D:\windows\soft\git_code\yfinance>pip install git+https://github.com/rodrigobercini/yfinance.git
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting git+https://github.com/rodrigobercini/yfinance.git
Cloning https://github.com/rodrigobercini/yfinance.git to c:\users\admini~1\appdata\local\temp\pip-req-build-m23hr4cs
Running command git clone -q https://github.com/rodrigobercini/yfinance.git 'C:\Users\ADMINI~1\AppData\Local\Temp\pip-req-build-m23hr4cs'
ERROR: Command errored out with exit status 1:
command: 'd:\code\python\stock\venv\scripts\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\ADMINI~1\AppData\Local\Temp\pip-
req-build-m23hr4cs\setup.py'"'"'; file='"'"'C:\Users\ADMINI~1\AppData\Local\Temp\pip-req-build-m23hr4cs\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"',
open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base 'C:\Users\ADMINI~1
AppData\Local\Temp\pip-pip-egg-info-slz7aivr'
cwd: C:\Users\ADMINI~1\AppData\Local\Temp\pip-req-build-m23hr4cs
Complete output (5 lines):
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\ADMINI~1\AppData\Local\Temp\pip-req-build-m23hr4cs\setup.py", line 17, in
with io.open(path.join(here, 'README.rst'), encoding='utf-8') as f:
FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\ADMINI~1\AppData\Local\Temp\pip-req-build-m23hr4cs\README.rst'
----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
Feeling missing files README.rst
help me

hey there!
I've updated my fork, it should be working now. Just be aware that the fork extracts inconsistent data for non-US tickers.

hey there!
I've updated my fork, it should be working now. Just be aware that the fork extracts inconsistent data for non-US tickers.

cool


test on notify

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Looks good

it point to test result page: https://github.com/Yikun/spark/runs/4803229384
details run_id: https://api.github.com/repos/Yikun/spark/actions/runs/1692697888, contains the status of Build and test


[Reflection] Remove DEPENDENT_TEMPLATE2 macro

The Clang version checks introduced in #16212 and #16221 do not work well.
The clang_major macro is defined differently for Apple builds of Clang,
and the APPLE_CC macro is obsolete and not useful. The good news is that
those checks appear to be unnecessary. The version of Clang used with
Swift 4.2 (based on LLVM 6.0) accepts the code without the template keyword
in the places where the DEPENDENT_TEMPLATE2 macro was being used.
This also corrects a mistake in #16221 where the non-Clang/GCC definition
of DEPENDENT_TEMPLATE was changed to use the template keyword.

@swift-ci please test

Thanks Bob!

The Linux failures here are happening on other PRs and are not related to this change. I'm going to go ahead and merge this to unblock master-next testing.


Move down campaign name and tagline on mobile action page

Need to build in some logic to rework line spacing on positioning on mobile. Here are some more comments about the specific designs:

need to tighten up line spacing between different elements so everything fits closer to bottom of the image.

need to tighten up line spacing between different elements so everything fits closer to bottom of the image but also need to have everything moved down on mobile if there is not sponsor or scholarship info.

This has been fixed!


Points & polygons position inconsistent in grid view mode (needs spatial coordinates)

🐛 Bug

Points and polygons do not share spatial coordinates with images they are selected from. This means when you switch grid view on/off points & polygons no longer overlay the image.
This is just one example of what we're trying to fix with the discussion around spatial coordinates at https://github.com/napari/napari/issues/763. I think the self-contained example in this issue could be useful as a test case.
To Reproduce
Steps to reproduce the behavior:

Open napari with an image.

$ ipython --gui=qt
Python 3.7.5 (default, Oct 31 2019, 15:18:51) [MSC v.1916 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 7.10.1 -- An enhanced Interactive Python. Type '?' for help.
In [1]: import napari
In [2]: napari.__version__
Out[2]: '0.2.3+104.g0d1c812'
In [3]: from skimage.data import astronaut, camera
In [4]: viewer = napari.Viewer()
In [5]: viewer.add_image(camera())

Add a points layer, and select some points on the image.

Click the "grid mode" view.

Expected behavior

Points and polygons should share spatial coordinates with the underlying image data, and always be displayed overlaid regardless of which image mode (grid-view/2D/3D) is selected.
Environment

Please copy and paste the information at napari info option in help menubar here:

napari: 0.2.3+104.g0d1c812
Platform: Windows-10-10.0.17763-SP0
Python: 3.7.5 (default, Oct 31 2019, 15:18:51) [MSC v.1916 64 bit (AMD64)]
Qt: 5.13.2
PySide2: 5.13.2
VisPy: 0.6.3
NumPy: 1.17.4
SciPy: 1.3.3
scikit-image: 0.16.2
Dask: 2.8.1

GL version: 4.5.0 - Build <IP_ADDRESS>72
MAX_TEXTURE_SIZE: 16384

Any other relevant information:

Additional context

Relevant issues: https://github.com/napari/napari/issues/763

@GenevieveBuckley actually this issue is somewhat orthogonal to the world coordinates. Grid mode does not modify world coordinates. This is what we would call world2canvas, and grid mode adds a translate transform to each layer so that they are separated on the canvas. But the world coordinates of each layer are preserved.
To overlay the points on the image, you need to add stride=2 to the grid mode call. (There is no way to do this in the GUI yet, but it could be done with a modal popup like the one @tlambert03 added to the play button.) Then things work as expected.
This will be necessary even after we switch to properly separating world2canvas and data2world transforms.
One idea I had is that layers could be in groups, ie you could have non-uniform strides in the grid mode, so you could have a group of three layers offset from another group of two layers. This might be useful e.g. if you want to see an image, its segmentation, and points, together with another image and points (but no segmentation), in order to register the segmentation.
Overall, this requires a bit of fiddling with our layer list interactions, but it could happen before or after the world coordinates.

One idea I had is that layers could be in groups

I think this could be very useful, especially if there was support for hierarchies within groups.
Eg: you will often have two or more treatment groups, with multiple samples in each group, and many cells in each sample. Being able to group them and toggle the visibility on/off for different subsets of the hierarchy would help you see if, say, all the cells from a single sample were messed up (maybe the slide was stored improperly or something - this is a terrible example because I'm a physicist not a biologist, but you can see how it would be useful!)

To overlay the points on the image, you need to add stride=2 to the grid mode call.

This is not a generally applicable solution, is it? It should work in the example I have here where there is one image and one points layer, but if there are an arbitrary number of images and an arbitrary number of points/polygon layers, all added to the viewer in a random order - am I right in thinking your suggestion may not work in a more general case?

but if there are an arbitrary number of images and an arbitrary number of points/polygon layers, all added to the viewer in a random order

Correct: you need to have some sort of regular cadence. Layers can be rearranged so the random order is not a huge concern, but you can't mix and match image layers with corresponding points and others without, for example.

you can't mix and match image layers with corresponding points and others without, for example.

To me this suggests something probably needs to be re-thought about the data models/objects. I'm not sure how, but maybe @sofroniewn has some thoughts?

I think this could be very useful, especially if there was support for hierarchies within groups.

I like this idea. This will also be relevant when thinking about the true multicanvas stuff in #760 - here I'm imagining more flexibility like being able to assign layers or groups to particular canvases. This will overcome the limitations of the current stride approach, but agreed will require some re-thought around models / objects.
I think when we work on #760 it will be a natural time to work on this too. Does that sound about right?

I wonder if linked layers could be used to adress this?
They're available in the GUI via contextual menu (though would be nice to have a visual indicator...)
Linked layers would be stacked in grid view?


Some confusion about Tensorflow Distributed Training（The amount of synchronized data is much larger than the theoretical value）

Issue type
Support
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
TF1.14
Custom code
No
OS platform and distribution
Linux Ubuntu 20.04
Mobile device
No response
Python version
2
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
As far as I know, TensorFlow uses ring allreduce, which seems to mean that the number of synchronized data should be [2 * (N -1)/N ]* number of parameters * 4bytes(Reduce Scatter + All Gather), N represents the number of workers. If we do some simplification, this should be like:
(2 * number of parameters * 4bytes)
The distributed approach I adopt is：
train_distribute=tf.contrib.distribute.CollectiveAllReduceStrategy(num_gpus_per_worker=0)
On the other hand, I conducted a simple experiment，my model parameters are like this:
Layer (type)                 Output Shape              Param #
=================================================================
dense (Dense)                (None, 16)                176
_________________________________________________________________
dense_1 (Dense)              (None, 1)                 17
=================================================================
Total params: 193
Trainable params: 193
Non-trainable params: 0

This should result about:2 * 193 * 4 = 1544bytes, but in fact, I caught around 2500 bytes of sending packages when I use tcpdump to capture package about tensorflow at one worker node.
Why there have such a big gap? Is this related to the tensorflow environment I am using(Kubeflow+Tensorflowtraining operator in K8s)? May I ask if there exists a more accurate formula?
Standalone code to reproduce the issue
This is the code I am using：
https://github.com/kubeflow/training-operator/blob/master/examples/tensorflow/distribution_strategy/estimator-API/keras_model_to_estimator.py

Relevant log output
No response

I understand what you mean, but this API used to be available...right？
Due to some reasons, I may not be able to migrate and use the relevant version of TF2. In fact, the above code can run successfully and obtain good training results using TF1.14 and CollectiveAllReduceStrategy API. The only point I am confused about is why there is a much larger communication volume between workers than the theoretical value.
Looking forward to your reply, and have a nice day~

@certainly-cyber,
The API tf.contrib.distribute.CollectiveAllReduceStrategy is not available and as it is part of the deprecated tf.contrib
CollectiveAllReduceStrategy is MultiWorkerMirrorStrategy. CollectiveAllReduceStrategy is a name we used in the implementation. Please refer to documentations of MultiWorkerMirrorStrategy.

Also CollectiveAllReduceStrategy reduces computation overhead by distributing it across workers, there's additional overhead associated with transferring data between workers. This overhead can include serialization, deserialization, and network latency, all of which can contribute to a larger communication volume than the theoretical minimum. Thank you!

Okay, I got it. Thank you again for your answer~
By the way, if I have adopted MultiWorkerMirroredStrategy, can we accurately calculate (or roughly estimate) the amount of data that needs to be synchronized? I have already know how to use model parameters for estimation, but I think it's not accurate enough:) Such like what the format of the synchronized message will be like, or what is the proportion of overhead information? Thank you!

@certainly-cyber,
In MultiWorkerMirroredStrategy, the synchronized messages primarily consist of gradients associated with the model's weights and biases. These gradients are numerical tensors representing the direction and magnitude for updating the model parameters during training.
https://www.tensorflow.org/api_docs/python/tf/distribute/MultiWorkerMirroredStrategy
Also this is not the bug/feature request, Kindly file the issue on TensorFlow Forum . There is also a larger community that reads questions there. Thank you!

ok, I got it~Thanks again for your answer, I'll keep exploring, thank you and have a nice day~

ok, I got it~
Thanks again for your answer, I'll keep exploring, thank you and have a nice day！

@certainly-cyber,
Glad the issue was resolved. Could you please feel free to move this issue to closed status. Thank you!

Sure, my pleasure.
Thanks again~


shell autocomplete

in often times we use the shell command to debug or ensure something, but there's a small problem which is we don't have auto-complete when we press the tab.
so I decided to make a pull request to add this feature

fixes #3941

Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[ ] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

Readline isn't guaranteed to be installed, so you need to account for that.

I think the readline it's a built-in module?

Yes, but it's only available on some platforms, and depends on how Python was compiled.

I wish you add this feature if possible, it's very helpful in our development env.
Regards, Abdelhadi

Ok, but you need to address the comment I made. Paying that your want me to merge it isn't really helpful on its own.

@davidism, I'm not talking to merge my own, but wish if you add this feature, it's very helpful.


Create 2021-07-14 posts

Links for review:
EN: https://deploy-preview-45--blog-tbs.netlify.app/2021/07/14/effective-links
FR: https://deploy-preview-45--blogue-sct.netlify.app/2021/07/14/liens-plus-efficaces


docs(rtd): Expand documentation

This adds

Examples
Contributing

In addition, it delegates more thorough install instructions to a dedicated installation page

[x] This contribution adheres to CONTRIBUTING.md.
[x] New tests have been created for any new features or regression tests for bugfixes.
[x] tox successfully runs, including unit tests and style checks (see CONTRIBUTING.md).

Coverage remained the same at 64.179% when pulling ebd64151b5e7432d85d7fc009894aa6ffd0dd2e5 on epage:docs into d7d9fc9f4e33f02c77cedd68ca5eb4f3326fea5b on ni:master.

Coverage remained the same at 64.179% when pulling 16e7a2a85d64e11aec9a8f7d7a5ff77ea07fcde9 on epage:docs into d7d9fc9f4e33f02c77cedd68ca5eb4f3326fea5b on ni:master.


Cannot set AUv2 plugin display name to something other than the OUTPUT_NAME parameter.

Hello,
Would there be opposition to having a PRODUCT_NAME or PLUGIN_NAME argument added to target_add_auv2_wrapper() that sets the AudioComponents / name field in the Info.plist without affecting the output file name?
VST3 & CLAP seem to read the title of the plugin from the clap_plugin_descriptor's name field which works great for my usecase. However, I plan to have a colon and space in the title of my future plugin such like "PluginTitle: Module". I cannot create a file on macOS with a colon in the filename.

Never mind. After some experimentation I discovered that AUv2 does not seem to like a colon in the name regardless. Closing this.

Yeah AUv2 uses ":" in the info plist name to separate the manufacturer from the plugin name.