libcamera-still stops sending image data after just a few images

pi@raspberrypi4B:~ $ uname -a
Linux raspberrypi4B 5.10.83-v7l+ #1499 SMP Tue Dec 7 14:08:09 GMT 2021 armv7l GNU/Linux
pi@raspberrypi4B:~ $ libcamera-still --version
libcamera-apps build: 7617ec5cdba5-intree 14-12-2021 (16:39:38)
libcamera build: v0.0.0+3368-8ff5a8d5
pi@raspberrypi4B:~ $
RPi 4 - latest Bullseye with newer kernel
I was having issues with a color/exposure problem so I checked to see if I had the latest libcamera-apps.  I didn't so I attempted to compile them again.  They wouldn't compile so I downloaded the libcamera source and compiled that and libcamea-apps but libcamera-still would seg fault.  After posting on the RPi forum I learned that there is a kernel issue that requires a newer kernel.  I did an rpi-update for the latest kernel.  I recompiled libcamera, libepoxy and libcamera-apps.  I now have a new problem with libcamera-still.  It will take a few (varies from 1 to a dozen or more) and then locks up and no more data comes out.
The command line I am using is:   libcamera-still --nopreview --thumb none --timeout 0 --timelapse 1 --width 640 --height 480 --quality 80 --output -
Below is the end of the output to the terminal:
�GJM�O�@�o�,_c1��˃��z�Ԯ4�
*͖�-�0��ɴe��P	X�a��?��4�n��8��ҝ����m)Z�����"�tc)	��=�/�^��[y�Yc8 �
���n�Z�g�g�RK�$�O���b{-L���?���t�>WΣ~U�k��ɦ�g��@]",�� '�UG\���F����f�{b���>��	em�߿@j�Մ�&�H��k68Ғd��!�7C��������zm�~TQ|��9�LM��8�J2[�P�08&��۴������E��c��j��Qz�5]���	-����};�c�T��a��P-H�i$
b���d#�R�lXe#f�P��ԗrۅ2)P�+��-�Ⱦi������n���<�tA@�[H�=�QA` g�)�8�MG���^���L�U;��$��֜b�G�=3�L
�dv���p�N6�%X\P?��[0:19:51.702734798] [5180]  INFO Camera camera.cpp:1028 configuring streams: (0) 1296x972-YUV420
[0:19:51.703518154] [5184]  INFO RPI raspberrypi.cpp:730 Sensor: /base/soc/i2c0mux/i2c@1/ov5647@36 - Selected sensor format: 1296x972-SGBRG10_1X10 - Selected unicam format: 1296x972-pGAA
[0:19:51.723473730] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:19:51.723571993] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:19:51.723602839] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:19:51.723631890] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:19:51.723660923] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:19:51.723691640] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:19:51.723721394] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:19:51.723747335] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:19:51.723777182] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:19:51.723803344] [5225]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[0:19:51.726206014] [5184]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:19:51.902673763] [5180]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-YUV420 (1) 2592x1944-SGBRG10_CSI2P
[0:19:51.903424568] [5184]  INFO RPI raspberrypi.cpp:730 Sensor: /base/soc/i2c0mux/i2c@1/ov5647@36 - Selected sensor format: 2592x1944-SGBRG10_1X10 - Selected unicam format: 2592x1944-pGAA
[0:19:51.992697679] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:19:51.992828954] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:19:51.992892481] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:19:51.992951157] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:19:51.993005408] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:19:51.993081359] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:19:51.993137054] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:19:51.993187934] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 100,<PHONE_NUMBER> ]
[0:19:51.993246740] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:19:51.993298695] [5228]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 2
[0:19:51.997458259] [5184]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
This time when I ran the command I got about 4 images before it hung.  Like I said it varies but usually around that many before it stops.  Never runs for a minute or more.
I have a Java application that I wrote to do motion detection.  I has been running for a couple of years on Buster with raspistill.  Once you guys fixed the --thumb none and --output - issues it ran fine on Bullseye with libcamera-still except for the occasional color/exposure issue.  See the sample Java program below that demonstrates the method I'm using in my program to capture the images from libcamera-still (and before that raspistill).  It will run with Java 11 or later.  It formats a little funny here.
package com.knutejohnson.pi.camera;
import java.awt.;
import java.awt.event.;
import java.awt.image.;
import java.io.;
import java.util.;
import javax.imageio.;
import javax.swing.*;
public class Camera extends JFrame implements Runnable {
private static final long serialVersionUID = 1L;
private static final int WIDTH = 640;
private static final int HEIGHT = 480;
private final ImagePanel panel;
private final Thread thread;
private volatile ProcessHandle processHandle;
private volatile boolean stopFlag;
public Camera() {
    super("Camera");
    thread = new Thread(this);
    addWindowListener(new WindowAdapter() {
        public void windowOpened(WindowEvent we) {
            start();
        }
        public void windowClosing(WindowEvent we) {
            dispose();
        }
        public void windowClosed(WindowEvent we) {
            stop();
        }
    });
    panel = new ImagePanel();
    add(panel,BorderLayout.CENTER);
    pack();
    setVisible(true);
}

public void start() {
    if (thread.getState() == Thread.State.NEW) {
        thread.start();
    }
}

public void run() {
    try {
        ProcessBuilder builder = new ProcessBuilder(

//             "raspistill",
"libcamera-still",
"--nopreview",
"--thumb","none",
"--timeout","0",
"--timelapse","1",  // fast as it will go
"--width",Integer.toString(WIDTH),
"--height",Integer.toString(HEIGHT),
"--quality","80",
"--output","-");
        builder.redirectError(new File("/dev/null"));

        Process process = builder.start();
        processHandle = process.toHandle();

        InputStream is = process.getInputStream();
        ByteArrayOutputStream baos = new ByteArrayOutputStream();
        while (process.isAlive()) {
            int last = 0;
            int nextToLast = 0;
            int n;

            do {
                if ((n = is.read()) == -1)
                    throw new IOException("end of stdin stream");
                baos.write(n);
                nextToLast = last;
                last = n;
            } while (!(nextToLast == 0xff && last == 0xd9)) ;

            ByteArrayInputStream bais = new ByteArrayInputStream(
             baos.toByteArray());
            BufferedImage image = ImageIO.read(bais);
            System.out.println("image read");
            if (image != null)
                panel.setImage(image);
            baos.reset();
        }
    } catch (IOException ioe) {
        if (!stopFlag)
            System.out.println(ioe);
    }

    dispose();
}

public void stop() {
    stopFlag = true;
    processHandle.destroyForcibly();
}

public static void main(String[] args) {
    EventQueue.invokeLater(() -> new Camera());
}

private class ImagePanel extends JPanel {
    private static final long serialVersionUID = 1L;
    private BufferedImage image;

    public ImagePanel() {
        setPreferredSize(new Dimension(Camera.WIDTH,Camera.HEIGHT));
    }

    public void setImage(BufferedImage image) {
        this.image = image;
        repaint();
    }

    public void paintComponent(Graphics g) {
        if (image != null)
            g.drawImage(image,0,0,getWidth(),getHeight(),null);
    }
}

}

Running the following command
libcamera-still --nopreview --thumb none --timeout 0 --timelapse 1 --width 640 --height 480 --quality 80 --output -

seems fine for me on a Pi4 with imx219 running the latest libcamera version on Bullseye.
@knutegit, when you see your crash, are you also running your Java app with the piped output?  If so, can you just run the libcamera-still command on its own?
It might also help if you run with the camera-bug-report tool that comes in the libcamera-apps repo:
utils/camera-bug-report -c "libcamera-still --nopreview --thumb none --timeout 0 --timelapse 1 --width 640 --height 480 --quality 80"

Press Ctrl+C when the app crashes, and you will get a crash, and post the generated bug-report.txt file over here.  Note that I've removed the --output - when generating the bug report, otherwise the tool may not capture the log output correctly.

The crash is just a stop.  If I'm running it from the command line libcamera-still just stops sending data.  I have to hit CTRL-C to get the prompt back.  When it stops in the Camera.java program it just blocks on the read.  The output in my original post was from the command line.
I don't know what camera I have.  The only marking on it is Raspberry Pi Camera rev 1.3.
Command line output from the camera-bug-report.  It stopped on its own, no CTRL-C was required:
pi@raspberrypi4B:~/libcamera-apps/utils $ ./camera-bug-report -c "libcamera-still --nopreview --thumb none --timeout 0 --timelapse 1 --width 640 --height 480 --quality 80"
[0:18:23.635716672] [4993]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3368-8ff5a8d5
[0:18:23.638649941] [4994] ERROR CameraSensor camera_sensor.cpp:535 'ov5647 10-0036': Camera sensor does not support test pattern modes.
[0:18:23.660976849] [4994]  INFO RPI raspberrypi.cpp:1256 Registered camera /base/soc/i2c0mux/i2c@1/ov5647@36 to Unicam device /dev/media3 and ISP device /dev/media0
[0:18:23.661153810] [4993]  INFO Camera camera.cpp:842 Pipeline handler in use by another process
[0:18:23.661443268] [4994] ERROR V4L2 v4l2_videodevice.cpp:1179 /dev/video16[15:cap]: Unable to request 0 buffers: Device or resource busy
[0:18:23.661657098] [4994] ERROR V4L2 v4l2_videodevice.cpp:1179 /dev/video15[14:cap]: Unable to request 0 buffers: Device or resource busy
[0:18:23.661815503] [4994] ERROR V4L2 v4l2_videodevice.cpp:1179 /dev/video14[13:cap]: Unable to request 0 buffers: Device or resource busy
[0:18:23.661968649] [4994] ERROR V4L2 v4l2_videodevice.cpp:1179 /dev/video13[12:out]: Unable to request 0 buffers: Device or resource busy
[0:18:23.662132405] [4994] ERROR V4L2 v4l2_videodevice.cpp:1179 /dev/video0[11:cap]: Unable to request 0 buffers: Device or resource busy
ERROR: *** failed to acquire camera /base/soc/i2c0mux/i2c@1/ov5647@36 ***
Bug report generated to bug-report.txt
Please upload this file when you create a new bug report at:
https://github.com/raspberrypi/libcamera-apps/issues/
pi@raspberrypi4B:~/libcamera-apps/utils $
bug-report.txt
So I ran the above from the ~/libcamera-apps/utils directory.  Running it from ~/bin I don't get the failed to acquire camera notice.
pi@raspberrypi4B:~/bin $ ../libcamera-apps/utils/camera-bug-report -c "libcamera-still --nopreview --thumb none --timeout 0 --timelapse 1 --width 640 --height 480 --quality 80"
[0:27:16.055986991] [6578]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3368-8ff5a8d5
[0:27:16.059042034] [6579] ERROR CameraSensor camera_sensor.cpp:535 'ov5647 10-0036': Camera sensor does not support test pattern modes.
[0:27:16.113054571] [6579]  INFO RPI raspberrypi.cpp:1256 Registered camera /base/soc/i2c0mux/i2c@1/ov5647@36 to Unicam device /dev/media3 and ISP device /dev/media0
[0:27:16.113762883] [6578]  INFO Camera camera.cpp:1028 configuring streams: (0) 1296x972-YUV420
[0:27:16.115862837] [6579]  INFO RPI raspberrypi.cpp:730 Sensor: /base/soc/i2c0mux/i2c@1/ov5647@36 - Selected sensor format: 1296x972-SGBRG10_1X10 - Selected unicam format: 1296x972-pGAA
[0:27:16.183371151] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:27:16.183522447] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:27:16.183549891] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:27:16.183571336] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:27:16.183680280] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:27:16.183722131] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:27:16.183766205] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:27:16.183802520] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:27:16.183862501] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:27:16.183886594] [6584]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[0:27:16.185635327] [6579]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:27:16.185663235] [6579]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:27:16.185679049] [6579]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:27:16.185693346] [6579]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:27:16.185707234] [6579]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:27:16.185720734] [6579]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[0:27:16.185734845] [6579]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
Bug report generated to bug-report.txt
Please upload this file when you create a new bug report at:
https://github.com/raspberrypi/libcamera-apps/issues/
bug-report.txt
I'm going to download and recompile again today, maybe I just missed an update somewhere.

It might also be worth adding the -v command to your libcamera-still command line to provide more verbose logging.

I found this in syslog.  It only happens when I run libcamera-still from my Java program, not from the command line.
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.581891] ------------[ cut here ]------------
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.581919] WARNING: CPU: 2 PID: 19849 at drivers/media/common/videobuf2/videobuf2-core.c:1956 __vb2_queue_cancel+0x1e0/0x258 [videobuf2_common]
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.581924] Modules linked in: 8021q garp stp llc ov5647 snd_soc_hdmi_codec brcmfmac brcmutil joydev v3d cfg80211 sg gpu_sched rfkill gpio_keys raspberrypi_hwmon i2c_mux_pinctrl i2c_brcmstb i2c_mux bcm2835_unicam v4l2_dv_timings v4l2_fwnode i2c_bcm2835 bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_codec(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common vc_sm_cma(C) snd_bcm2835(C) videodev mc vc4 rpivid_mem cec drm_kms_helper snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops dht11 nvmem_rmem industrialio uio_pdrv_genirq uio nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl squashfs ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG nf_conntrack_ftp xt_CT nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nft_counter nf_tables nfnetlink i2c_dev fuse drm drm_panel_orientation_quirks
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582335]  backlight ip_tables x_tables ipv6
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582364] CPU: 2 PID: 19849 Comm: libcamera-still Tainted: G        WC        5.10.83-v7l+ #1499
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582368] Hardware name: BCM2711
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582371] Backtrace:
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582388] [] (dump_backtrace) from [] (show_stack+0x20/0x24)
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582394]  r7:ffffffff r6:00000000 r5:60000013 r4:c12e6fd8
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582401] [] (show_stack) from [] (dump_stack+0xcc/0xf8)
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582408] [] (dump_stack) from [] (__warn+0xfc/0x114)
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582414]  r10:bf444474 r9:00000009 r8:bf3876b4 r7:000007a4 r6:00000009 r5:bf3876b4
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582417]  r4:bf38cf90 r3:c1205094
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582423] [] (__warn) from [] (warn_slowpath_fmt+0x70/0xd8)
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582427]  r7:000007a4 r6:bf38cf90 r5:c1205048 r4:00000000
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582440] [] (warn_slowpath_fmt) from [] (__vb2_queue_cancel+0x1e0/0x258 [videobuf2_common])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582445]  r9:bf402118 r8:c33c850c r7:00000001 r6:c33c83ac r5:c5853780 r4:c33c83ac
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582463] [] (__vb2_queue_cancel [videobuf2_common]) from [] (vb2_core_streamoff+0x28/0xbc [videobuf2_common])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582468]  r10:bf444474 r9:bf402118 r8:c33c850c r7:00000001 r6:c1205048 r5:c5853780
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582471]  r4:c33c83ac r3:00000001
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582488] [] (vb2_core_streamoff [videobuf2_common]) from [] (vb2_streamoff+0x24/0x64 [videobuf2_v4l2])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582492]  r5:c5853780 r4:00000001
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582505] [] (vb2_streamoff [videobuf2_v4l2]) from [] (vb2_ioctl_streamoff+0x4c/0x50 [videobuf2_v4l2])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582546] [] (vb2_ioctl_streamoff [videobuf2_v4l2]) from [] (v4l_streamoff+0x2c/0x30 [videodev])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582550]  r5:40045613 r4:bf3f3138
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582602] [] (v4l_streamoff [videodev]) from [] (__video_do_ioctl+0x234/0x460 [videodev])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582606]  r5:40045613 r4:c33c8520
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582657] [] (__video_do_ioctl [videodev]) from [] (video_usercopy+0x138/0x5f0 [videodev])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582662]  r10:00000000 r9:c78e3e3c r8:00000000 r7:c1205048 r6:00000000 r5:40045613
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582665]  r4:40045613
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582715] [] (video_usercopy [videodev]) from [] (video_ioctl2+0x20/0x24 [videodev])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582720]  r10:0000000b r9:c78e2000 r8:00000000 r7:c5853780 r6:c5853781 r5:c1205048
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582723]  r4:bf408090
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582772] [] (video_ioctl2 [videodev]) from [] (v4l2_ioctl+0x4c/0x60 [videodev])
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582802] [] (v4l2_ioctl [videodev]) from [] (sys_ioctl+0x1d4/0x8ec)
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582806]  r5:c1205048 r4:40045613
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582813] [] (sys_ioctl) from [] (ret_fast_syscall+0x0/0x28)
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582817] Exception stack(0xc78e3fa8 to 0xc78e3ff0)
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582822] 3fa0:                   b1907df4 b1907e04 0000000b 40045613 b19037c0 00000001
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582827] 3fc0: b1907df4 b1907e04 b19101c8 00000036 00703350 00000000 b6aa6124 007032f0
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582831] 3fe0: b6a75718 b2236564 b6a1ca4c b6b981ac
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582836]  r10:00000036 r9:c78e2000 r8:c0200204 r7:00000036 r6:b19101c8 r5:b1907e04
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582839]  r4:b1907df4
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582844] ---[ end trace 0435eb8b07001329 ]---
Dec 16 10:31:25 raspberrypi4B kernel: [ 4144.582851] videobuf2_common: driver bug: stop_streaming operation is leaving buf 01388e2c in active state
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919303] ------------[ cut here ]------------
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919330] WARNING: CPU: 2 PID: 19849 at drivers/media/common/videobuf2/videobuf2-core.c:1956 __vb2_queue_cancel+0x1e0/0x258 [videobuf2_common]
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919336] Modules linked in: 8021q garp stp llc ov5647 snd_soc_hdmi_codec brcmfmac brcmutil joydev v3d cfg80211 sg gpu_sched rfkill gpio_keys raspberrypi_hwmon i2c_mux_pinctrl i2c_brcmstb i2c_mux bcm2835_unicam v4l2_dv_timings v4l2_fwnode i2c_bcm2835 bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_codec(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common vc_sm_cma(C) snd_bcm2835(C) videodev mc vc4 rpivid_mem cec drm_kms_helper snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd syscopyarea sysfillrect sysimgblt fb_sys_fops dht11 nvmem_rmem industrialio uio_pdrv_genirq uio nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl squashfs ip6_tables ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG nf_conntrack_ftp xt_CT nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nft_counter nf_tables nfnetlink i2c_dev fuse drm drm_panel_orientation_quirks
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919747]  backlight ip_tables x_tables ipv6
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919774] CPU: 2 PID: 19849 Comm: libcamera-still Tainted: G        WC        5.10.83-v7l+ #1499
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919778] Hardware name: BCM2711
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919781] Backtrace:
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919796] [] (dump_backtrace) from [] (show_stack+0x20/0x24)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919802]  r7:ffffffff r6:00000000 r5:60000013 r4:c12e6fd8
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919809] [] (show_stack) from [] (dump_stack+0xcc/0xf8)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919817] [] (dump_stack) from [] (__warn+0xfc/0x114)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919822]  r10:ffffe000 r9:00000009 r8:bf3876b4 r7:000007a4 r6:00000009 r5:bf3876b4
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919826]  r4:bf38cf90 r3:c1205094
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919832] [] (__warn) from [] (warn_slowpath_fmt+0x70/0xd8)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919837]  r7:000007a4 r6:bf38cf90 r5:c1205048 r4:00000000
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919849] [] (warn_slowpath_fmt) from [] (__vb2_queue_cancel+0x1e0/0x258 [videobuf2_common])
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919854]  r9:00000000 r8:00000001 r7:c3432e40 r6:c33c83ac r5:c33c840c r4:c33c83ac
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919872] [] (__vb2_queue_cancel [videobuf2_common]) from [] (vb2_core_queue_release+0x28/0x48 [videobuf2_common])
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919877]  r10:ffffe000 r9:00000000 r8:00000001 r7:c3432e40 r6:c33c8520 r5:c33c840c
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919881]  r4:c33c83ac r3:c7496600
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919898] [] (vb2_core_queue_release [videobuf2_common]) from [] (_vb2_fop_release+0x74/0x94 [videobuf2_v4l2])
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919901]  r5:c5853780 r4:00000000
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919915] [] (_vb2_fop_release [videobuf2_v4l2]) from [] (unicam_v4l2_release+0x4c/0xd8 [bcm2835_unicam])
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919919]  r7:c3432e40 r6:c5853780 r5:c33c850c r4:c33c8290
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919957] [] (unicam_v4l2_release [bcm2835_unicam]) from [] (v4l2_release+0xd8/0xe4 [videodev])
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919961]  r9:00000000 r8:c39d9440 r7:c237c490 r6:000e001f r5:c5853780 r4:c33c8520
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919994] [] (v4l2_release [videodev]) from [] (__fput+0x90/0x25c)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.919997]  r5:c473ceb8 r4:c5853780
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920003] [] (__fput) from [] (____fput+0x18/0x1c)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920007]  r9:00000000 r8:c1356d6c r7:c367ae80 r6:c367b3d4 r5:c5853540 r4:c5853780
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920014] [] (____fput) from [] (task_work_run+0xb4/0xe4)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920021] [] (task_work_run) from [] (do_exit+0x498/0xb88)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920026]  r9:00000000 r8:c699ee44 r7:c78e3e94 r6:ffffe000 r5:c699ee00 r4:c367ae80
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920032] [] (do_exit) from [] (do_group_exit+0x50/0xe0)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920035]  r7:c2355400
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920042] [] (do_group_exit) from [] (get_signal+0x1c0/0xae0)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920047]  r7:c2355400 r6:00000008 r5:00000000 r4:00418004
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920053] [] (get_signal) from [] (do_work_pending+0x30c/0x5a8)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920058]  r10:c1205048 r9:fffffe30 r8:5ac3c35a r7:c78e3f44 r6:b6b958e8 r5:c78e3fb0
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920061]  r4:ffffe000
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920067] [] (do_work_pending) from [] (slow_work_pending+0xc/0x20)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920070] Exception stack(0xc78e3fb0 to 0xc78e3ff8)
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920075] 3fa0:                                     b1919ac8 00000005 00000000 00000000
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920079] 3fc0: 00000008 00000000 b1919ac8 0000019e 00000005 00000000 b2237680 00000000
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920084] 3fe0: 00000000 b22367c8 00000000 b6b958e8 80000010 b1919ac8
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920089]  r10:0000019e r9:c78e2000 r8:c0200204 r7:0000019e r6:b1919ac8 r5:00000000
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920092]  r4:00000008
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920097] ---[ end trace 0435eb8b0700132a ]---
Dec 16 10:31:33 raspberrypi4B kernel: [ 4152.920104] videobuf2_common: driver bug: stop_streaming operation is leaving buf 7737e506 in active state

With -v added.
pi@raspberrypi4B:~/bin/com/knutejohnson/pi/camera $ camera-bug-report -c "libcamera-still -v --nopreview --thumb none --timeout 0 --timelapse 1 --width 640 --height 480 --quality 80"
Options:
verbose: 1
info_text:#%frame (%fps fps) exp %exp ag %ag dg %dg
timeout: 0
width: 640
height: 480
output:
post_process_file:
rawfull: 0
preview: none
qt-preview: 0
transform: identity
roi: all
metering: centre
exposure: normal
ev: 0
awb: auto
flush: false
wrap: 0
brightness: 0
contrast: 1
saturation: 1
sharpness: 1
framerate: 30
denoise: auto
viewfinder-width: 0
viewfinder-height: 0
tuning-file: (libcamera)
lores-width: 0
lores-height: 0
mode: unspecified
viewfinder-mode: unspecified
encoding: jpg
quality: 80
raw: 0
restart: 0
timelapse: 1
framestart: 0
datetime: 0
timestamp: 0
keypress: 0
signal: 0
thumbnail width: 0
thumbnail height: 0
thumbnail quality: 0
latest:
immediate 0
Running without preview window
Opening camera...
[1:12:56.646765237] [20739]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3368-8ff5a8d5
[1:12:56.649968755] [20740] ERROR CameraSensor camera_sensor.cpp:535 'ov5647 10-0036': Camera sensor does not support test pattern modes.
[1:12:56.713048519] [20740]  INFO RPI raspberrypi.cpp:1256 Registered camera /base/soc/i2c0mux/i2c@1/ov5647@36 to Unicam device /dev/media3 and ISP device /dev/media0
Acquired camera /base/soc/i2c0mux/i2c@1/ov5647@36
Configuring viewfinder...
Viewfinder size chosen is 1296x972
[1:12:56.713724054] [20739]  INFO Camera camera.cpp:1028 configuring streams: (0) 1296x972-YUV420
[1:12:56.714538161] [20740]  INFO RPI raspberrypi.cpp:730 Sensor: /base/soc/i2c0mux/i2c@1/ov5647@36 - Selected sensor format: 1296x972-SGBRG10_1X10 - Selected unicam format: 1296x972-pGAA
Camera streams configured
Buffers allocated and mapped
Viewfinder setup complete
Requests created
[1:12:56.733538390] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[1:12:56.733627294] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[1:12:56.733654656] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[1:12:56.733677924] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[1:12:56.733707454] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[1:12:56.733731296] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[1:12:56.733777944] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[1:12:56.733800101] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[1:12:56.733828797] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[1:12:56.733849193] [20745]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[1:12:56.735574444] [20740]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:12:56.735602343] [20740]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:12:56.735618665] [20740]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:12:56.735634393] [20740]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:12:56.735649361] [20740]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:12:56.735664256] [20740]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:12:56.735679076] [20740]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
Camera started!
Viewfinder frame 0
Closing Libcamera application(frames displayed 0, dropped 0)
Camera stopped!
Tearing down requests, buffers and configuration
Camera closed
Bug report generated to bug-report.txt
Please upload this file when you create a new bug report at:
https://github.com/raspberrypi/libcamera-apps/issues/
bug-report.txt

Could you turn on libcamera verbose logging as well?  To do this, you need to set an environment variable before running:
export LIBCAMERA_LOG_LEVELS=RPI:0

Please disrgard what I said about the syslog messages only showing up when I run it from Java.  I hadn't actually stopped libcamera-still with the CTRL-C yet.  They are the same.
pi@raspberrypi4B:~/bin/com/knutejohnson/pi/camera $ export LIBCAMERA_LOG_LEVELS=RPI:0
pi@raspberrypi4B:~/bin/com/knutejohnson/pi/camera $ camera-bug-report -c "libcamera-still -v --nopreview --thumb none --timeout 0 --timelapse 1 --width 640 --height 480 --quality 80"
Options:
verbose: 1
info_text:#%frame (%fps fps) exp %exp ag %ag dg %dg
timeout: 0
width: 640
height: 480
output:
post_process_file:
rawfull: 0
preview: none
qt-preview: 0
transform: identity
roi: all
metering: centre
exposure: normal
ev: 0
awb: auto
flush: false
wrap: 0
brightness: 0
contrast: 1
saturation: 1
sharpness: 1
framerate: 30
denoise: auto
viewfinder-width: 0
viewfinder-height: 0
tuning-file: (libcamera)
lores-width: 0
lores-height: 0
mode: unspecified
viewfinder-mode: unspecified
encoding: jpg
quality: 80
raw: 0
restart: 0
timelapse: 1
framestart: 0
datetime: 0
timestamp: 0
keypress: 0
signal: 0
thumbnail width: 0
thumbnail height: 0
thumbnail quality: 0
latest:
immediate 0
Running without preview window
Opening camera...
[1:18:12.587465425] [21544]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3368-8ff5a8d5
[1:18:12.590457915] [21545] ERROR CameraSensor camera_sensor.cpp:535 'ov5647 10-0036': Camera sensor does not support test pattern modes.
[1:18:12.653051928] [21545]  INFO RPI raspberrypi.cpp:1256 Registered camera /base/soc/i2c0mux/i2c@1/ov5647@36 to Unicam device /dev/media3 and ISP device /dev/media0
[1:18:12.653100867] [21545] DEBUG RPI raspberrypi.cpp:1060 Unable to acquire a Unicam instance
Acquired camera /base/soc/i2c0mux/i2c@1/ov5647@36
Configuring viewfinder...
[1:18:12.653543761] [21544] DEBUG RPI raspberrypi.cpp:505 Try color space JPEG
Viewfinder size chosen is 1296x972
[1:18:12.653768253] [21544] DEBUG RPI raspberrypi.cpp:505 Try color space JPEG
[1:18:12.653885499] [21544] DEBUG RPI raspberrypi.cpp:505 Try color space JPEG
[1:18:12.653915885] [21544]  INFO Camera camera.cpp:1028 configuring streams: (0) 1296x972-YUV420
[1:18:12.654032834] [21545] DEBUG RPI raspberrypi.cpp:166 Format: 640x480 fmt SGBRG10 Score: 3296 (best 3296)
[1:18:12.654077699] [21545] DEBUG RPI raspberrypi.cpp:166 Format: 1296x972 fmt SGBRG10 Score: 1000 (best 1000)
[1:18:12.654100752] [21545] DEBUG RPI raspberrypi.cpp:166 Format: 1920x1080 fmt SGBRG10 Score: 1349.67 (best 1000)
[1:18:12.654123620] [21545] DEBUG RPI raspberrypi.cpp:166 Format: 2592x1944 fmt SGBRG10 Score: 1567 (best 1000)
[1:18:12.654148913] [21545] DEBUG RPI raspberrypi.cpp:166 Format: 640x480 fmt SGBRG8 Score: 4296 (best 1000)
[1:18:12.654766732] [21545]  INFO RPI raspberrypi.cpp:730 Sensor: /base/soc/i2c0mux/i2c@1/ov5647@36 - Selected sensor format: 1296x972-SGBRG10_1X10 - Selected unicam format: 1296x972-pGAA
[1:18:12.655024165] [21545] DEBUG RPI raspberrypi.cpp:762 Setting ISP Output0 to 1296x972-YU12
[1:18:12.655193331] [21545] DEBUG RPI raspberrypi.cpp:776 Stream ISP Output0 has color space JPEG
[1:18:12.655220291] [21545] DEBUG RPI raspberrypi.cpp:836 Setting ISP Output1 (internal) to 648x486-YU12
Camera streams configured
Buffers allocated and mapped
Viewfinder setup complete
Requests created
[1:18:12.674071594] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[1:18:12.674152381] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[1:18:12.674179655] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[1:18:12.674202245] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[1:18:12.674255332] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[1:18:12.674296772] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[1:18:12.674353302] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[1:18:12.674388576] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[1:18:12.674432719] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[1:18:12.674467752] [21553]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[1:18:12.676089344] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for Unicam Image
[1:18:12.676186351] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 1 for Unicam Image
[1:18:12.676222977] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 2 for Unicam Image
[1:18:12.676255695] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 3 for Unicam Image
[1:18:12.676287951] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 4 for ISP Output0
[1:18:12.676328724] [21545]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:18:12.676346037] [21545]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:18:12.676360813] [21545]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:18:12.676378737] [21545]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:18:12.676393180] [21545]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:18:12.676407956] [21545]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:18:12.676422250] [21545]  INFO RPISTREAM rpi_stream.cpp:133 No buffers available for ISP Output0
[1:18:12.676436749] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.676471411] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
Camera started!
[1:18:12.737472514] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 0
[1:18:12.737553986] [21545] DEBUG RPI raspberrypi.cpp:1015 queueRequestDevice: New request.
[1:18:12.737592352] [21545] DEBUG RPI raspberrypi.cpp:1015 queueRequestDevice: New request.
[1:18:12.737613091] [21545] DEBUG RPI raspberrypi.cpp:1015 queueRequestDevice: New request.
[1:18:12.737632255] [21545] DEBUG RPI raspberrypi.cpp:1015 queueRequestDevice: New request.
[1:18:12.740702552] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.740763434] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:12.740782950] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:12.740814576] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 0
[1:18:12.742330958] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.742367639] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:12.748498047] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.748529136] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for Unicam Image
[1:18:12.748593333] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 4, timestamp:<PHONE_NUMBER>000
[1:18:12.748617885] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 4 for ISP Output0
[1:18:12.748672212] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.748694006] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.748745278] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.748863950] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
[1:18:12.748927017] [21545] DEBUG RPI raspberrypi.cpp:1794 Dropping frame at the request of the IPA (7 left)
[1:18:12.763666346] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 1
[1:18:12.786401926] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 1, timestamp:<PHONE_NUMBER>000
[1:18:12.786469048] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:12.786485676] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:12.786517098] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 1
[1:18:12.787444825] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 1, timestamp:<PHONE_NUMBER>000
[1:18:12.787477933] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:12.793499021] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 1, timestamp:<PHONE_NUMBER>000
[1:18:12.793527554] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 1 for Unicam Image
[1:18:12.793574419] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 4, timestamp:<PHONE_NUMBER>000
[1:18:12.793596732] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 4 for ISP Output0
[1:18:12.793666927] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.793689184] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.793736438] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.793832556] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
[1:18:12.793879199] [21545] DEBUG RPI raspberrypi.cpp:1794 Dropping frame at the request of the IPA (6 left)
[1:18:12.796980177] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 2
[1:18:12.819715091] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 2, timestamp:<PHONE_NUMBER>000
[1:18:12.819780676] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:12.819799026] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:12.819829244] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 2
[1:18:12.820577159] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 2, timestamp:<PHONE_NUMBER>000
[1:18:12.820610173] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:12.826677812] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 2, timestamp:<PHONE_NUMBER>000
[1:18:12.826731213] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 2 for Unicam Image
[1:18:12.826786244] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 4, timestamp:<PHONE_NUMBER>000
[1:18:12.826810093] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 4 for ISP Output0
[1:18:12.826859883] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.826880696] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.826948521] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.827967479] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
[1:18:12.828044988] [21545] DEBUG RPI raspberrypi.cpp:1794 Dropping frame at the request of the IPA (5 left)
[1:18:12.833702655] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 3
[1:18:12.853037921] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 3, timestamp:<PHONE_NUMBER>000
[1:18:12.853108931] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:12.853129892] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:12.853280893] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 3
[1:18:12.854458332] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 3, timestamp:<PHONE_NUMBER>000
[1:18:12.854496180] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:12.860592703] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 3, timestamp:<PHONE_NUMBER>000
[1:18:12.860623422] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 3 for Unicam Image
[1:18:12.860772664] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 4, timestamp:<PHONE_NUMBER>000
[1:18:12.860797606] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 4 for ISP Output0
[1:18:12.860955347] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.861000157] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.861161083] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.861851022] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
[1:18:12.861915533] [21545] DEBUG RPI raspberrypi.cpp:1794 Dropping frame at the request of the IPA (4 left)
[1:18:12.865695193] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 4
[1:18:12.886354400] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.886424762] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:12.886442278] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:12.886474738] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 0
[1:18:12.887552299] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.887586221] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:12.893685560] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.893715908] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for Unicam Image
[1:18:12.897267316] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 4, timestamp:<PHONE_NUMBER>000
[1:18:12.897316366] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 4 for ISP Output0
[1:18:12.897596297] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.897632607] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.897859933] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 5
[1:18:12.898136568] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.899065202] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
[1:18:12.899166376] [21545] DEBUG RPI raspberrypi.cpp:1794 Dropping frame at the request of the IPA (3 left)
[1:18:12.919644696] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 1, timestamp:<PHONE_NUMBER>000
[1:18:12.919752462] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:12.919770052] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:12.919914869] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 1
[1:18:12.921137266] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 1, timestamp:<PHONE_NUMBER>000
[1:18:12.921174539] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:12.930079130] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 1, timestamp:<PHONE_NUMBER>000
[1:18:12.930132606] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 1 for Unicam Image
[1:18:12.930216633] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 4, timestamp:<PHONE_NUMBER>000
[1:18:12.930244297] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 4 for ISP Output0
[1:18:12.930339119] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.930363209] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.930416573] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.930483380] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 6
[1:18:12.931529723] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
[1:18:12.931646043] [21545] DEBUG RPI raspberrypi.cpp:1794 Dropping frame at the request of the IPA (2 left)
[1:18:12.952958805] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 2, timestamp:<PHONE_NUMBER>000
[1:18:12.953026594] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:12.953043925] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:12.953196926] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 2
[1:18:12.954337332] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 2, timestamp:<PHONE_NUMBER>000
[1:18:12.954372717] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:12.960737043] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 2, timestamp:<PHONE_NUMBER>000
[1:18:12.960784501] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 2 for Unicam Image
[1:18:12.960839698] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 4, timestamp:<PHONE_NUMBER>000
[1:18:12.960864047] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 4 for ISP Output0
[1:18:12.960908616] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output0
[1:18:12.962867522] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 1 for ISP Output0
[1:18:12.963230276] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 2 for ISP Output0
[1:18:12.963546925] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 3 for ISP Output0
[1:18:12.964034554] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.964087845] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.964165706] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.964238883] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 7
[1:18:12.966575874] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
[1:18:12.966674845] [21545] DEBUG RPI raspberrypi.cpp:1794 Dropping frame at the request of the IPA (1 left)
[1:18:12.986269025] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 3, timestamp:<PHONE_NUMBER>000
[1:18:12.986335795] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:12.986352553] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:12.986507535] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 3
[1:18:12.987567673] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 3, timestamp:<PHONE_NUMBER>000
[1:18:12.987602910] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:12.994903666] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 3, timestamp:<PHONE_NUMBER>000
[1:18:12.994955086] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 3 for Unicam Image
[1:18:12.995031910] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 4, timestamp:<PHONE_NUMBER>000
[1:18:12.995086663] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.995109327] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:12.995180430] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:12.996161614] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
[1:18:12.996284026] [21545] DEBUG RPI raspberrypi.cpp:1794 Dropping frame at the request of the IPA (0 left)
[1:18:12.996852405] [21545] DEBUG RPI raspberrypi.cpp:1392 frame start 8
[1:18:13.019589504] [21545] DEBUG RPI raspberrypi.cpp:1592 Stream Unicam Image buffer dequeue, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:13.019661144] [21545] DEBUG RPI raspberrypi.cpp:1943 Could not find matching embedded buffer
[1:18:13.019678049] [21545] DEBUG RPI raspberrypi.cpp:1950 Returning bayer frame without a match
[1:18:13.019713675] [21545] DEBUG RPI raspberrypi.cpp:1887 Signalling signalIspPrepare: Bayer buffer id: 0
[1:18:13.020709042] [21545] DEBUG RPI raspberrypi.cpp:1509 Input re-queue to ISP, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:13.020749075] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer -1 for ISP Input
[1:18:13.026937384] [21545] DEBUG RPI raspberrypi.cpp:1620 Stream ISP Input buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:13.026984082] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for Unicam Image
[1:18:13.027061036] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output0 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:13.027143879] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Output1 buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:13.027167709] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output1
[1:18:13.027243608] [21545] DEBUG RPI raspberrypi.cpp:1648 Stream ISP Stats buffer complete, buffer id 0, timestamp:<PHONE_NUMBER>000
[1:18:13.028284896] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Stats
Viewfinder frame 0
Closing Libcamera application(frames displayed 0, dropped 0)
[1:18:13.028681258] [21545] DEBUG RPI raspberrypi.cpp:1015 queueRequestDevice: New request.
[1:18:13.028718050] [21545] DEBUG RPISTREAM rpi_stream.cpp:237 Queuing buffer 0 for ISP Output0
Camera stopped!
Tearing down requests, buffers and configuration
Camera closed
Bug report generated to bug-report.txt
Please upload this file when you create a new bug report at:
https://github.com/raspberrypi/libcamera-apps/issues/
bug-report.txt

Thank you for the logs!
I'm afraid I don't see anything obvious going wrong from them, but I will keep looking.  If there are any further details you could provide, please do post them here!

I've just gone through a process as follows:

Plugged an ov5647 into my Pi 4B (I see this is what you're using).
Installed a fresh Bullseye using Raspberry Pi Imager tool.
Let it start up and apply all updates. Rebooted.
Run sudo rpi-update. Rebooted.
Worked through the build instructions for libcamera, libepoxy and libcamera-apps (choosing the "non-Lite" options where I had a choice). For libcamera I first checked out the revision that you listed with libcamera-still --version, ditto for libcamera-apps.
My kernel, libcamera and libcamera-apps all report the same versions as you.
Finally I ran the exact command you give at the top.

As Naush did, I have found it runs with no problems. I have left it running for minutes at a time.
@knutegit Are you able to perform this exact experiment starting with a completely clean Bullseye image? If that still fails for you then I wonder if we're going to have to start swapping our cameras or cables, but maybe we should run that experiment first and see if it reveals anything. Thanks!

Same Pi 4 2GB, same camera, new bullseye, rpi-update, recompiled libcamera, libepoxy and libcamera-apps.
pi@raspberrypi:~/bin $ uname -a
Linux raspberrypi 5.10.87-v7l+ #1502 SMP Fri Dec 17 15:13:41 GMT 2021 armv7l GNU/Linux
pi@raspberrypi:~/bin $ libcamera-still --version
libcamera-apps build: 7617ec5cdba5-intree 17-12-2021 (10:13:31)
libcamera build: v0.0.0+3368-8ff5a8d5
No change.  The first time I ran the libcamera-still I got no image data.  Subsequently I got a few before it hung.  This is very frustrating for both of us I think :-).

It all seems very mysterious. I'm starting to wonder a little bit about trying to swap out things like cameras/cables/SD cards (depending on whether you have spares). Do you have a particularly long ribbon cable or anything?

I don't think it is the camera or the cable.  When I switch to the legacy camera stack it runs fine.  The ribbon cable is short about 6 inches.  I used a different SD card for the previous test.
This version is running continuously on my Pi3 and not hanging.  It has other issues but it doesn't hang.
pi@camerapi:~ $ libcamera-still --version
libcamera-apps build: 19190467dbd2-intree 03-12-2021 (20:23:56)
libcamera build: v0.0.0+3156-f4070274
Something changed between that one and the current one I'm using:
libcamera-apps build: 7617ec5cdba5-intree 16-12-2021 (10:15:05)
libcamera build: v0.0.0+3368-8ff5a8d5
Oh and when I did the previous test with a new bullseye that one had a libcamera-apps dated today I think.  I'll update it and see if that makes any difference.

Today's libcamera-apps didn't make any difference.

I'm wondering whether the fresh Pi 4 image you made is clean and free of any private information? If so you could maybe upload it and then I could try it?

I would be happy to upload it if you can tell me how.  But I think I have figured out where the problem is.  I moved the fresh image SD card to my Pi3 that has a version 2, I think, camera.  It's been running now just over 6800 images.  That made me try to think what were the differences between my Pi3 and the Pi4 I had been using.  I tried removing all of the dtoverlays and the arm_boost=1 that wasn't in the Pi3.  Still didn't run very long on the Pi4, so I changed Pi4s to an older one without the 3 little chips in a triangle.  It is just now approaching 1000 images.  There is something different in the way libcamera works between those two types of Pi4s.  It runs fine on the Pi3 and the Pi4 1.1 and won't run on the Pi4 1.4.  The only difference between them is the 1.1 is 4GB and 1.4 2GB.

I'm using a Pi 4 4GB revision 1.4 and it seems fine. Setting total_mem=2048 in my config.txt doesn't change the behaviour either. So it all seems to remain very baffling.

Well I guess we'll just have to forget this one for now.  I thought I had it figured out there for a minute.  I'm going to post the original problem I had before I couldn't get libcamera to run on my Pi4.

I've pretty well convinced myself that this problem was the specific Pi4 that I was using.  It worked for you on your Pi4 1.4 and it works on the new Pi4 1.4 that I got a few days ago.  It still doesn't work on the old one, who knows why.

This may be down to a power supply issue.  Could you swap the power supply from the known working board to the not working board and try again?
Given this does not seem software related, feel free to close this down if you are satisfied with the resolution.

I tried it with 6 different power supplies and that one Pi4 1.4 has a problem.  My other one works just fine.  I think we should close this issue unless/until something else shows up.

This issue is now fixed see #234


Implement an id generator in class book

-All good! 👍

I would suggest to create the elements with document create Element instead of using innerHTML


SetNoDataValue performance regression

In terms of prepearing #567 (notebook) I notcied that:
# any dataframe with rasters
rs = spark.read.raster(assets.limit(1), tile_dimensions=(512, 512), buffer_size=2, catalog_col_names=["band"])

# Set LC 8 NoData to zero
rsnd = rs.select(rf_with_no_data(rs.band, 0).alias("band"))

# save a hillshade raster to the disk as a tiff (nodata is set via rf_with_no_data)
rsnd \
  .limit(1) \
  .select(rf_hillshade(rsnd.band, azimuth=315, altitude=45, z_factor=1, target="data")) \
  .write.geotiff("lc8-hillshade.tiff", "EPSG:32718")

# save a hillshade raster to the disk as a tiff (without nodata set)
rs \
  .limit(1) \
  .select(rf_hillshade(rs.band, azimuth=315, altitude=45, z_factor=1)) \
  .write.geotiff("lc8-hillshade-all.tiff", "EPSG:32718")```

The usage of  rf_with_no_data makes computation ~x600 slower than without it.
rf_with_no_data

vanilla

Ah, that is due to the fact that in this case the nodata tile was set to ~300 tiles which forced deserialization, setting the nodata value and the follow up serialization of all tiles.
Results with the correclty set limits (two top rows (13, 12) are with the rf_with_no_data used, two bottom (11, 10) - without):

Closing it for now.


trying to build locally fails with [copy-webpack-plugin] unable to locate 'analysis.json'

Indeed, my mistake, sorry. I added missing script in package.json.
You can also run yarn analyze before manually before starting.

cheers, I get it to build now


modbam support

Hi,
Thanks for making this tool available. In your recent preprint you mention a version that supports modbam, would you be able to update this repository to include this feature? Thanks!

+1


[R-package] introduce Dataset methods set_field() and get_field()

Contributes to #4543, as part of #4310.
This PR proposes the following changes in the R package:

deprecates Dataset$getinfo() (with a warning its name will be changed to get_field())
deprecates Dataset$setinfo() (with a warning its name will be changed to set_field())
adds method Dataset$get_field(field_name) to Dataset, matching the Python package

https://github.com/microsoft/LightGBM/blob/8a90ea3f267a81a529e3f069cc13e0f6320e7989/python-package/lightgbm/basic.py#L1939

adds method Dataset$set_field(field_name, data) should be added to Dataset, matching the Python package

https://github.com/microsoft/LightGBM/blob/8a90ea3f267a81a529e3f069cc13e0f6320e7989/python-package/lightgbm/basic.py#L1890

Notes for Reviewers
I only added new tests, but left existing tests with getinfo() and setinfo() in place, so that those methods are still tested as long as they exist in the package.

Update Dataset$setinfo() here

Done in https://github.com/microsoft/LightGBM/pull/4571/commits/a7459875a0fa42a827a0dbf82390ee346baa27b1

Not sure whether we should update here
https://github.com/microsoft/LightGBM/blob/master/docs/FAQ.rst#i-used-setinfo-tried-to-print-my-lgb-dataset-and-now-the-r-console-froze. WDYT?

I think it's ok to leave that alone for now, since the functions are being deprecated but not removed yet. That entire FAQ section probably deserves some updates and revisions, to check if the issues listed there still exist in recent versions. But that could be done in a separate PR.

iiinteresting, I see this error on the lint job

Some R documentation files have changed. Please re-generate them and commit those changes.

I did re-generate the docs before pushing. Maybe there was a new release of {roxygen2} or something. I'll investigate this later today!

Maybe there was a new release of {roxygen2} or something

Yes, there was a new release (7.1.2) a few days ago: https://cran.r-project.org/web/packages/roxygen2/index.html.
But it also looks like there are a few local changes I forgot to git add 😆
Regenerated the docs with {roxygen} 7.1.2 and added the requested changes in https://github.com/microsoft/LightGBM/pull/4571/commits/e92a28ed0033f097632f9fc7564ac446142e8adc

Shall we also update here in the FAQ documentation? Will set_field encounter the same problem?

Other modifications LGTM. They seem to be simple renaming. And thanks @StrikerRUS for detecting the minor mistakes.

Shall we also update here in the FAQ documentation? Will set_field encounter the same problem?

ah! I answered this in https://github.com/microsoft/LightGBM/pull/4571#issuecomment-924516705 actually. I don't think we need to worry about it for this PR. That particular question was added in #976 (4 years ago), so it might not even be relevant any more. I'd prefer to take updating the FAQ as a separate task.


Wallet View token update fix

Simplify the wallet page token update.

Ensure filters work 'live' (previously they didn't).
Ensure tokens are updated as they are discovered (this was previously delayed until a refresh).

@JamesSmartCell confused as to what this PR is, please be more clear.

Sorry I thought the comment above was OK.
Ensure filters work 'live' (previously they didn't).
On the wallet page there are a set of filters, namely 'all', 'currency' and 'assets'. When the user clicks on one of these filters, the expected behaviour would be that the tokens are filtered accordingly. For example if the user clicks on 'currency' filter tab they would expect to see only token cards showing native currencies.
During testing, we noticed they didn't update live, there was a noticeable delay and usually you'd manually refresh to see the change.
This PR mainly fixes that issue.
The other issue that was noticed was that it was taking a while for the tokens discovered during the transaction sync to appear in the wallet view. This was down to the way the Recycle view works and required a little re-factor to get it working reliably.
Most of these issues were discovered during the Multi-Token support going in, but they benefit the wallet pre-multi-Token support and I felt the upgrade could be in its own PR, since it is focussed in one area.


feat: output json

Resolves #173

@pngwn Can you try this in your workflow and see if --json works as expected for you?
        run: API_URL=https://pkg.pr.new pnpx pkg-pr-new@https://d61368b4.stackblitz-cr.pages.dev/stackblitz-labs/pkg.pr.new/pkg-pr-new@183 publish './js/*' './client/js' --comment=off

You can just try different variations of --json on this command.

I shall try!

Works beautifully for stdout: https://github.com/gradio-app/gradio/actions/runs/10469032256/job/28991194562?pr=9153#step:5:150
And so does the JSON file option: https://github.com/gradio-app/gradio/actions/runs/10469152056/job/28991538458?pr=915
Thank youuuuuuuuu!
One question, it is also possible to install via link@pr number, would that still work?

Thank you so much, yes it'd be possible but I did not put it in the
metadata because you can easily access the pr number from github
environment vars.
So you can construct the pr url easily for yourself.
Let me know if you have any questions, and if this can be merged ❤
On Tue, 20 Aug 2024, 13:16 pngwn, @.***> wrote:

Works beautifully for stdout:
https://github.com/gradio-app/gradio/actions/runs/10469032256/job/28991194562?pr=9153#step:5:150
And so does the JSON file option:
https://github.com/gradio-app/gradio/actions/runs/10469152056/job/28991538458?pr=915
Thank youuuuuuuuu!
One question, it is also possible to install via @.*** number, would
that still work?
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz-labs/pkg.pr.new/pull/183#issuecomment-2298438128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBMICG5QLEQJEHJ43J6AG3ZSMF75AVCNFSM6AAAAABMZGSOGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJYGQZTQMJSHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

That's great thanks!
Yep this looks perfect to merge from my end!

Thank you so much!
On Tue, 20 Aug 2024, 15:53 pngwn, @.***> wrote:

That's great thanks!
Yep this looks perfect to merge from my end!
—
Reply to this email directly, view it on GitHub
https://github.com/stackblitz-labs/pkg.pr.new/pull/183#issuecomment-2298728478,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBMICEGWLMGFVDU6HVDMLLZSMYLZAVCNFSM6AAAAABMZGSOGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJYG4ZDQNBXHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


refactor(state table): remove commit_no_data_expected

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
To me, the StateTable::commit_no_data_expected introduced unnecessary mental burden. Developers have to somehow track whether the state is dirty or not in executors, while this information is clearly known by state table itself.
This PR removes the unnecessary method, and uniformly uses commit instead. Inside commit, the state table will branch according to StateTable::is_dirty so that the calling cost is not changed.
I'm doing benchmark to test the performance impact.
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

I believe it was introduced as an optional assertion for developers.

Yes. However things get complicated after we introducing state cleaning. Even without data changed, updating state cleaning watermark will also require commit instead of commit_no_data_expected, which forces executors to take too much care of the internal details of state table.

Did some nexmark bench on q0 in normal mode, q4~q9,q18 in eowc mode, results show almost no difference.


Azure AD Connect configration

Hello!
Could you please advice how to configure Azure AD Connect to support Federation and Password hash synchronization?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c6ff701b-a0fa-2ca5-ddba-40cedaaf0a38
Version Independent ID: db655cc8-030e-6801-a01a-1a795e717620
Content: Azure AD Connect and federation
Content Source: articles/active-directory/hybrid/how-to-connect-fed-whatis.md
Service: active-directory
GitHub Login: @billmath
Microsoft Alias: billmath

@AlekseySokol Thanks for your feedback! We will investigate and update as appropriate.

Hi @AlekseySokol ,
You just need to select "Federation with ADFS" at the first step in the AD Connect Wizard and then select Password Hash at one of the later steps so that you can have both.
(This blog talks a bit about this. http://www.enowsoftware.com/solutions-engine/a-closer-look-at-azure-ad-connect-–-part-2)
There are a number of good guides out there that you can reference. https://azure.microsoft.com/en-us/resources/videos/configuring-ad-fs-for-user-sign-in-with-azure-ad-connect/
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-password-hash-synchronization

Hope this helps! If you have further questions please revert them to MSDN as we are moving away from product questions in the doc comments. https://social.msdn.microsoft.com/Forums/en-US/home?forum=WindowsAzureAD


util-linux: 2.39.2 -> 2.39.3

Changes: https://github.com/util-linux/util-linux/compare/v2.39.2...v2.39.3
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@GrahamcOfBorg eval


Input type number on PrimeNG component

Description
When generating a form through a JSON Schema, the fields generated by declaring a property of type number emit a string instead of a floating point number, causing validation to fail.
Minimal Reproduction
Cannot reproduce on Stackblitz since loading the default PrimeNG template throws ENOENT: No such file or directory., '/dev/null'.
More on that here.

Input JSON
{ "schema": {   "id": "http://sample.com/sample-number-form",   "title": "Number Test Form",   "properties": {     "NumberInput": {       "type": "number",       "title":"Simple Number Input"     }   } } }

Generated Form

Environment

Angular version: 17.0.2
Formly version: 6.2.2

Additional context
It is apparent from the interpolation of form.value on the right that the value emitted is a string, as opposed to a number, or more specifically, a floating point number, which is what the number type is supposed to represent in the JSON Schema syntax.

This issue has been fixed and released as part of v6.3.3 release.
Please let us know, in case you are still encountering a similar issue/problem.
Thank you!


[MINOR][PYTHON] Better error message when Python worker crushes

What changes were proposed in this pull request?
This PR improves the Python UDF error messages to be more actionable.
Why are the changes needed?
Suppose you face a segfault error:
from pyspark.sql.functions import udf
import ctypes
spark.range(1).select(udf(lambda x: ctypes.string_at(0))("id")).collect()

The current error message is not actionable:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  ...
get_return_value
    raise Py4JJavaError(
py4j.protocol.Py4JJavaError: An error occurred while calling o82.collectToPython.
: org.apache.spark.SparkException: Job aborted due to stage failure: Task 15 in stage 1.0 failed 1 times, most recent failure: Lost task 15.0 in stage 1.0 (TID 31) (<IP_ADDRESS> executor driver): org.apache.spark.SparkException:
Python worker exited unexpectedly (crashed)

After this PR, it fixes the error message as below:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  ...
get_return_value
    raise Py4JJavaError(
py4j.protocol.Py4JJavaError: An error occurred while calling o59.collectToPython.
: org.apache.spark.SparkException: Job aborted due to stage failure: Task 15 in stage 0.0 failed 1 times, most recent failure: Lost task 15.0 in stage 0.0 (TID 15) (<IP_ADDRESS> executor driver): org.apache.spark.SparkException:
Python worker exited unexpectedly (crashed). Consider setting 'spark.sql.execution.pyspark.udf.faulthandler.enabled'
or 'spark.python.worker.faulthandler.enabled' configuration to 'true' forthe better Python traceback.

So you can try this out
from pyspark.sql.functions import udf
import ctypes
spark.conf.set("spark.sql.execution.pyspark.udf.faulthandler.enabled", "true")
spark.range(1).select(udf(lambda x: ctypes.string_at(0))("id")).collect()

that now shows where the segfault happens:
Caused by: org.apache.spark.SparkException: Python worker exited unexpectedly (crashed): Fatal Python error: Segmentation fault

Current thread 0x00007ff84ae4b700 (most recent call first):
  File "/.../envs/python3.9/lib/python3.9/ctypes/__init__.py", line 525 in string_at
  File "<stdin>", line 1 in <lambda>
  File "/.../lib/pyspark.zip/pyspark/util.py", line 88 in wrapper
  File "/.../lib/pyspark.zip/pyspark/worker.py", line 99 in <lambda>
  File "/.../lib/pyspark.zip/pyspark/worker.py", line 1403 in <genexpr>
  File "/.../lib/pyspark.zip/pyspark/worker.py", line 1403 in mapper

Does this PR introduce any user-facing change?
Yes, it fixes the error message actionable.
How was this patch tested?
Manually tested as above.
Was this patch authored or co-authored using generative AI tooling?
No.

Merged to master.


Try to make the comparison more fair

As mentioned in #2, this are my changes attempting to make the overall comparison more fair.
The Zig client turned out to be significantly slower when run in a loop. I'm an absolute Zig beginner, so a review of especially that code would be really great, if you find the time for it. I feel like there must be something that I've done wrong, as the client was the fastest when only run once.

Since you're now forcing the client to be reused and therefore the connection to remain open you should consider disabling nagle's algorithm on the server. The response body is <16 bytes and therefore is affecting the response time.
diff --git a/zig-http-server/src/main.zig b/zig-http-server/src/main.zig
index eeb03fe..49898c4 100644
--- a/zig-http-server/src/main.zig
+++ b/zig-http-server/src/main.zig
@@ -14,6 +14,8 @@ fn runServer(server: *http.Server, allocator: std.mem.Allocator) !void {
         });
         defer response.deinit();

+        try std.os.setsockopt(response.connection.stream.handle, std.os.IPPROTO.TCP, std.os.TCP.NODELAY, &std.mem.toBytes(@as(c_int, 1)));
+
         while (response.reset() != .closing) {
             // Handle errors during request processing.
             response.wait() catch |err| switch (err) {
@@ -57,8 +59,7 @@ fn handleRequest(response: *http.Server.Response, allocator: std.mem.Allocator)
         // Write the response body.
         try response.do();
         if (response.request.method != .HEAD) {
-            try response.writeAll("Zig ");
-            try response.writeAll("Bits!\n");
+            try response.writeAll("Zig Bits!\n");
             try response.finish();
         }
     } else {

Are the benchmarks take rust-ureq as a base? I'm getting the following results:
Summary
  rust-ureq ran
    1.10 ± 0.15 times faster than rust-hyper
    1.21 ± 0.23 times faster than rust-reqwest
    1.50 ± 0.19 times faster than go-http-client
    1.68 ± 0.25 times faster than rust-attohttpc
    1.71 ± 0.29 times faster than zig-http-client
    3.92 ± 0.48 times faster than curl
   10.84 ± 1.37 times faster than python-http-client

seems more reasonable, std.http beating well seasoned and optimized libraries off of the bat with basically no focus towards speed was a bit questionable.

I guess I'm not very experienced in reading benchmarks. So how one can tell the speed comparison of Zig's std.http against the other ones from the current output?

@orhun hyperfine takes whatever is fastest as base and then lists the rest in decreasing performance.
Also, the performance can vary a lot due to different hardware, software and global configs. For example, I have a global cargo config that tells rustc to target my CPU with --target-cpu=native, which can make differences.
In general, this comparison is tough, because you test across different languages and across the network (well loopback, but still). Would we for example only compare Rust crates against each other, we could use a benchmarking library and have more consistent results.
For the speed comparison, I'd say it's not the fastest, but that's normal. All the other clients have been around for quite a long while, so they're more battle tested and optimized, as @truemedian mentioned.
When it comes to comparing the Zig and the Rust server, it's likely a similar story, as the hyper crate has been around for a long time and is used in tons of projects. So they have tons of optimizations under the hood.
It would be very interesting to see how the std.http package develops over time. Meaning, once it's part of an official release, might be worth tracking the performance over the upcoming releases. Like Zig 0.11, 0.12, 0.13... releases compared.

Thank you for the insight and implementation! 🐻


WIP – Print more measurements of student profile timing

Notes

@kevinrobinson, this branch is my first WIP crack at investigating #1386. My plan is to find the student who triggered Logentry alerts, copy their data down locally, and use this profiling to see which parts of assembling @serialized_data take the most time on the server.
What do you think about eventually shipping some version of this branch to production? Then we'd have lots of fine-grained student profile timing data in the logs on an ongoing basis.

@kevinrobinson Ship this or close it? Slowness in the student profile page doesn't seem to be a big issue anymore and we haven't heard slowness complaints since we shipped the memory improvements, so I could go either way.

It seems great to get more latency data in general.  But I think it depends on whether we think we'll take action on that data in the next week or two.  If so, let's ship it and do that!  And if not, it's easy to add in this great kind of profiling when we do want to do something about it, so nothing much is lost if we close.

@kevinrobinson OK! I don't think we'll take action in the next week or two so I'll close.


Possible to integrate with cfs:s3?

I prefer to use cfs:s3 because it offers more features than the other s3 package from Orion. In my case I really require the beforeWrite, transformWrite, transformRead, etc methods that are available to modify image files with ImageMagick. It also deletes the image stored in S3 when you do something like
Images.findOne().remove(function(error, success){
  console.log(success)
});

Yes you can.
Look the s3 package and make it fit for you.
You can also read here
#8


cannot enter toolbox from zsh shell

simply because the base image does not contain zsh. installing it fixes the problem of course
exec failed: container_linux.go:337: starting container process caused "exec: \"/usr/bin/zsh\":
stat /usr/bin/zsh: no such file or directory"
exit status 1

another small issue is that zsh does not expect PS1 but this not much of a problem

one way to fix this would be to make sure that $SHELL is present in toolbox. if not fallback to bash. or even better install $SHELL in toolbox

The fallback to Bash if $SHELL is unavailable is already addressed by commit 912f3000a9e4a43f and commit 48ddba630642507f in Git master. Sadly, those are not part of the 0.0.1 release, which is why you are still suffering from the problem.

oh, should have checked the code first :) closing this. thanks


Fix isna, allna and anyna deprecations

Also fix some uses of all(isna(x)) and any(isna(x)), and avoid computing
the number of missing values twice in describe().
@ararslan I'm not sure whether I should bump the dependency on DataArrays. AFAICT this form worked before the deprecation was added, since it's possible since Julia 0.5, right?

Mmm, unfortunately this doesn't work with 0.3.12 (on Julia 0.5):
julia> isna.(DataArray(1:2))
2-element DataArrays.DataArray{Int64,1}:
 0
 0

So we'll either have to make a new 0.3.x release for DataArrays (but then we cannot mark this as a dependency for DataFrames), or drop support for Julia 0.5.

So we'll either have to make a new 0.3.x release for DataArrays

I tried add 0.5 support back to DataArrays but it was too difficult and I decided I didn't care enough. Since there's a release candidate now for 0.6 it's probably fine to drop 0.5 here.

Let's drop 0.5 support then. I've changed the PR to do that.

Let's merge this?


glOrtho

Is there any alternative to glOrtho? because i cant find this function in this library :(

That's legacy opengl, you might need to import the opengl functions with another library that lets you select the version, legacy is opengl 1.x-2.x

Thats a legacy function and is deprecated, to use it you have to create a context for Opengl 1.x, 2.x and generate the bindings for that specific version, here is an example, look at the build.rs and how it creates the context https://github.com/arnodb/torus_trooper_rs


Parameterize jenkins plugin repository and add support for core plugins

This is useful when you want jenkins to download plugins from an enterprise repository.
Repository base url can be redefined and accept a maven style layout. When necessary plugins can use a different groupId:
dynamicparameter : {
    version: "0.2.0",
    group_id: "com.seitenbau.jenkins.plugins"
}

As for the core plugin support this should fix https://github.com/jenkinsci/puppet-jenkins/issues/118
Simply set core to the core plugins that you want to upgrade:
matrix-auth : {
    version: "1.2",
    core: true
}

This functionality was merged in #190.  This PR can be closed.

@backuitist Actually, #190 didn't fully cover this functionality.  However, I'm going to close this PR due to code drift and lack of activity.  Please feel free to reopen it in the future.


Patch schemas/nl.basjes/yauaa_context/jsonschema/1-0-0

Added "UNKNOWN" to the enum for deviceClass

Closing in favor of #979


RecursionError: maximum recursion depth exceeded while calling a Python object

Looks like the master branch of this action is broken since a couple of days/weeks back?
 "" "" "true" "" "" ""
running checkov on directory: .
Traceback (most recent call last):
  File "/usr/local/bin/checkov", line 5, in <module>
    run()
  File "/usr/local/lib/python3.9/site-packages/checkov/main.py", line 69, in run
    scan_reports = runner_registry.run(root_folder=root_folder, external_checks_dir=external_checks_dir,
  File "/usr/local/lib/python3.9/site-packages/checkov/common/runners/runner_registry.py", line 30, in run
    scan_report = runner.run(root_folder, external_checks_dir=external_checks_dir, files=files,
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/runner.py", line 57, in run
    self.parser.parse_directory(directory=root_folder,
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 77, in parse_directory
    self._parse_directory(dir_filter=lambda d: self._check_process_dir(d))
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 117, in _parse_directory
    self._internal_dir_load(sub_dir, module_loader_registry, dir_filter)
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 237, in _internal_dir_load
    self._process_vars_and_locals(directory, var_value_and_file_map, module_data_retrieval)
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 277, in _process_vars_and_locals
    if self._process_vars_and_locals_loop(file_data,
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 411, in _process_vars_and_locals_loop
    return process_items_helper(out_definitions.items, out_definitions, outer_context, False)
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 404, in process_items_helper
    if process_items_helper(lambda: enumerate(value), value, new_context, True):
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 395, in process_items_helper
    if self._process_vars_and_locals_loop(value, eval_map_by_var_name, relative_file_path,
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 411, in _process_vars_and_locals_loop
    return process_items_helper(out_definitions.items, out_definitions, outer_context, False)
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 395, in process_items_helper
    if self._process_vars_and_locals_loop(value, eval_map_by_var_name, relative_file_path,
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 411, in _process_vars_and_locals_loop
    return process_items_helper(out_definitions.items, out_definitions, outer_context, False)
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 395, in process_items_helper
    if self._process_vars_and_locals_loop(value, eval_map_by_var_name, relative_file_path,
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 411, in _process_vars_and_locals_loop
    return process_items_helper(out_definitions.items, out_definitions, outer_context, False)
  File "/usr/local/lib/python3.9/site-packages/checkov/terraform/parser.py", line 404, in process_items_helper
[...]
RecursionError: maximum recursion depth exceeded while calling a Python object

Hi @MPV  thank you for reporting this. i have hard time reproducing this one.
can you share a terraform code sample here or via DM at http://slack.bridgecrew.io/ ?

I ended up being able to reproduce this without this action by just using checkov, like this:
$ checkov -d .
[...]

And I found the terraform code that breaks it (by commenting out different pieces until checkov started working again):
resource "google_kms_crypto_key" "sops" {
  name       = "sops"
  key_ring   = google_kms_key_ring.sops.self_link
  depends_on = [google_kms_crypto_key.sops] # <-------------- this line specifically

  lifecycle {
    prevent_destroy = true
  }
}

As it turns out, that's a circular dependency.

I ended up being able to reproduce this without this action by just using checkov, like this:
$ checkov -d .
[...]

And I found the terraform code that breaks it (by commenting out different pieces until checkov started working again):
resource "google_kms_crypto_key" "sops" {
  name       = "sops"
  key_ring   = google_kms_key_ring.sops.self_link
  depends_on = [google_kms_crypto_key.sops] # <-------------- this line specifically

  lifecycle {
    prevent_destroy = true
  }
}

As it turns out, that's a circular dependency.

So I guess we can close this issue. 😅

So I guess we can close this issue. 😅


Updated handler.

Updating the command handler to Discord.js v13 and making it easier to use, such as a new README.md file with all information of the handler and for newbies coders, added connotations in the code, so they can identify what the code actually do.

Maybe I'm gonna do some optimization in the code in the future and even a slash commands handler. Stay tuned.


RouteCollection missing from 4.x?

I'm wondering if (doubtful) RouteCollection is missing from 4.x or if it no longer comes standard?
My AppServiceProvider used to share the collection on my container like:

$container = $this->getContainer();
$container->share(RouteCollection::class, function () use ($container) {
return new RouteCollection($container);
});

But that no longer seems possible, looking to see if I have to figure out how to do it now, or like I said, if RouteCollection is just missing.

It’s not missing, but it has been renamed to Router, please be aware that there are quite a few more changes in 4.x too.
Sent from my iPhone

On 12 Oct 2018, at 05:30, alturic<EMAIL_ADDRESS>wrote:
I'm wondering if (doubtful) RouteCollection is missing from 4.x or if it no longer comes standard?
My AppServiceProvider used to share the collection on my container like:
`
$container = $this->getContainer();
$container->share(RouteCollection::class, function () use ($container) {
return new RouteCollection($container);
});
`
But that no longer seems possible, looking to see if I have to figure out how to do it now, or like I said, if RouteCollection is just missing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix messages being truncated

You're currently stopping the stream when encountering .\r\n but this means such a message:
Hi,

I like pasta.

My regards
.

Would get truncated at pasta. This makes sure we're looking for the actual end of message period (alone on a new line) instead of any period that is at the end of a line.

Closes #13

Not sure how to add a test for this one

There aren't many tests for the connection command. I am still figuring out a way to simulate a socket connection in phpunit


Dpdk backend: Allow non-constant arguments to mirror_packet extern

Removed the checks for allowing only constant arguments to mirror_packet extern.
The "mirror" instruction in DPDK assembly expects both the arguments in metadata. Hence, move instruction is inserted to move the argument to metadata if not already present in metadata

Closing as upstreamed.


Android force close/kill does not disconnect from device

We got an app where we can search for specific devices, connect to them and monitor a specific characteristic.
If we manually disconnect the device, we can find it and connect immediately after the disconnect, but when we kill/force close the app on Android, sometimes we can't find the device (because it is still connected) and we get data via monitoring for several minutes.
How can we drop the connection completely by close/kill?
Things we tried:
hook on root.componentWillUnmount: trigger manager.destroy():
-> Java code gets called, but problem still remains
hook on root.componentWillUnmount: trigger connectedDevices.cancelConnection():
-> Java code gets called, but problem still remains
Use restoreStateIdentifier and restoreStateFunction:
-> It seems like every time we close the app a new Manager gets created, as restoreStateFunction gets called several times after exiting. The restoredData is always "null"
If this is not the right place to ask such questions i can move it on Stackoverflow :)
Thanks in advance!

Seems like this is not related to react-native-ble-plx library.
If anyone stumbles upon this error:
For us cause of the problem is the background-service of
https://github.com/mauron85/react-native-background-geolocation
which is restarting in the background if kille/closed.
It should be fixed with an update.


Caching node_modules

Our install job is taking 5 minutes to perform the npm ci. It would be good to cache node_modules based on package-lock.json and perhaps also on the node version to minimize the time it takes to run tests. Is this a good idea?

https://github.com/actions/cache/blob/main/examples.md#node---npm
says:
"Note: It is not recommended to cache node_modules, as it can break across Node versions and won't work with npm ci"

https://github.com/actions/cache/blob/main/examples.md#node---npm
says:
"Note: It is not recommended to cache node_modules, as it can break across Node versions and won't work with npm ci"

Correct. But including the Node version in the cache key + skip running npm ci on cache hit works great from experience 👍

Closing this based on the subjectivity of user interaction. Thank you for opening an issue here!


Esteem Surfer [ver 2.1.0 Web App Client] App gives error message and fails to publish post

Description
When I click on "Post" I keep getting two error messages
Expected behavior
I expected it to publish my post
Steps to reproduce
Launch the app
Enter the post, click on "post"
Devise used
HP Elitebook 8460p
Windows [8.1]
App version. Current version
Screenshot to reproduce the bug

App Github link - https://github.com/esteemapp/esteem-surfer
My Github link https://github.com/Mistakili

Thanks for reporting @Mistakili  but this issue is not directly related to eSteem Surfer. May be a temporary blockchain issue. Closing...


Issue#128 solved

Solved Speech Rate Bug in a Spelling Template Simulator

Don't add app.iml, and other project files that are generally ignored by present gitignore configuration.

Closed via 1f80476