KAFKA 8291 : System test fix

As titled, this PR changed the default reset policy to latest accidentally for system tests, which in fact was earliest:
parser.addArgument("--reset-policy")
                .action(store())
                .required(false)
                .setDefault("earliest")
                .type(String.class)
                .dest("resetPolicy")
                .help("Set reset policy (must be either 'earliest', 'latest', or 'none'");

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @guozhangwang @mumrah

https://jenkins.confluent.io/job/system-test-kafka-branch-builder/2539/ Test passed

LGTM! Thanks @abbccdda !


PrivateKey#toString returns incorrect result

Private key is random and it can happen that first byte is 0 in which case the resulting hex-encoded string is 62 characters long instead of 64 characters. Need to prefix this with 00

fixed this by 3233fb6 in pull request #85


fix: several fixes

Fixes
fix(repo): invisible failed environment pill
before

now

fix(repo/settings): new change visibility box danger buttons
before

now

fix(labels): invisible texts
before

now

fix(repo/settings): change visibility preview buttons colors
before

now

fix(settings): 2FA auth box header
before

now

Thanks!


camera module 3 raises memory error

This issue was first reported in the indilib.org forum:
https://indilib.org/forum/ccds-dslrs/12177-indi-libcamera-driver.html?start=168

But, I own a RaspiCam V3, which libcamera recognizes, but not the indi driver. Is there a plan to implement the new model?
...
The camera could take raw pictures. But it seems, that i've got a problem with the V2L2 driver in your script.

libcamera-hello --list-cameras
Available cameras
-----------------
0 : imx708_noir [4608x2592] (/base/soc/i2c0mux/i2c@1/imx708@1a)
    Modes: 'SRGGB10_CSI2P' : 1536x864 [120.13 fps - (0, 0)/4608x2592 crop]
                             2304x1296 [56.03 fps - (0, 0)/4608x2592 crop]
                             4608x2592 [14.35 fps - (0, 0)/4608x2592 crop]

=============================================================================================

./print_camera_information.py
[44:16:57.663063920] [21997]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[44:16:57.777647938] [22001]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media4 and ISP device /dev/media1
Found 1 cameras.

Camera 0:
{'Id': '/base/soc/i2c0mux/i2c@1/imx708@1a',
 'Location': 2,
 'Model': 'imx708_noir',
 'Rotation': 180}

[44:16:57.780730099] [21997]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[44:16:57.904930596] [22004]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media4 and ISP device /dev/media1
Camera properties:
{'ColorFilterArrangement': 0,
 'Location': 2,
 'Model': 'imx708_noir',
 'PixelArrayActiveAreas': (libcamera.Rectangle(16, 24, 4608, 2592),),
 'PixelArraySize': (4608, 2592),
 'Rotation': 180,
 'ScalerCropMaximum': (0, 0, 0, 0),
 'UnitCellSize': (1400, 1400)}

Raw sensor modes:
[44:16:57.913604842] [21997]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 1536x864-SBGGR10_CSI2P
[44:16:57.913984358] [22004]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 1536x864-SBGGR10_1X10 - Selected unicam format: 1536x864-pBAA
[44:16:57.931774476] [21997]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 2304x1296-SBGGR10_CSI2P
[44:16:57.932158047] [22004]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 2304x1296-SBGGR10_1X10 - Selected unicam format: 2304x1296-pBAA
[44:16:57.970528262] [21997]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 4608x2592-SBGGR10_CSI2P
[44:16:57.978747252] [22004]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 4608x2592-SBGGR10_1X10 - Selected unicam format: 4608x2592-pBAA
[44:16:58.033480856] [22004] ERROR V4L2 v4l2_videodevice.cpp:1248 /dev/video0[16:cap]: Not enough buffers provided by V4L2VideoDevice
Failed to allocate buffers.
Traceback (most recent call last):
  File "/home/dsl/Projects/indi_pylibcamera/./print_camera_information.py", line 20, in <module>
    pprint.pprint(picam2.sensor_modes)
  File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 475, in sensor_modes
    self.configure(temp_config)
  File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 978, in configure
    self.configure_(camera_config)
  File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 959, in configure_
    raise RuntimeError("Failed to allocate buffers.")
RuntimeError: Failed to allocate buffers.

================================================================================================
libcamera-raw -t 2000 -o test.raw
[44:22:07.691796128] [22053]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[44:22:07.815481259] [22055]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media4 and ISP device /dev/media1
Stream configuration adjusted
[44:22:07.816527084] [22053]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-YUV420 (1) 1536x864-SBGGR10_CSI2P
[44:22:07.816810729] [22055]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 1536x864-SBGGR10_1X10 - Selected unicam format: 1536x864-pBAA
Raw stream: 1536x864 stride 1920 format SBGGR10_CSI2P

When I understand right Libcamera does not get enough memory for testing the "4608x2592-SBGGR10_1X10" format. When you run  libcamera-raw it offers you only the formats "640x480-YUV420" and "1536x864-SBGGR10_CSI2P". The full size format that makes the memory trouble is missing.
Please edit /boot/cmdline.txt and add  cma=400M at the end. Reboot and try ./print_camera_information.py again.
If this does not help please provide more information:

Which Raspberry Pi version do you use?
Which OS have you installed?
Do you start with graphical user interface? (Is there a window manager running?)
Have you enabled (for instance with raspi-config->"Advanced Options") the GL Driver, Glamor or Wayland? These graphic accelerators can take too much memory.
Run grep -i cma /proc/meminfo and forward the result.
Run cat /boot/config.txt and forward result.
Run cat /boot/cmdline.txt and forward result.
Run cat /etc/os-release and forward result.
Run uname -a and forward result.
run apt list --installed | grep libcamera and forward result.
Run apt list --installed | grep picamera and forward result.
Run grep -i cma /proc/meminfo and forward result.

Similar topics are:

https://github.com/raspberrypi/picamera2/issues/46
https://forums.raspberrypi.com/viewtopic.php?t=346131
https://forum.arducam.com/t/64mp-failed-to-allocate-buffers-on-rpi-4-model-b/2878/18
https://docs.arducam.com/Raspberry-Pi-Camera/Pivariety-Camera/Troubleshooting/

Hi, seem that cma=400M works.
./print_camera_information.py
[0:01:42.075142391] [1674]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[0:01:42.203460173] [1678]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media1 and ISP device /dev/media2
Found 1 cameras.
Camera 0:
{'Id': '/base/soc/i2c0mux/i2c@1/imx708@1a',
'Location': 2,
'Model': 'imx708_noir',
'Rotation': 180}
[0:01:42.206140294] [1674]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[0:01:42.328354135] [1681]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media1 and ISP device /dev/media2
Camera properties:
{'ColorFilterArrangement': 0,
'Location': 2,
'Model': 'imx708_noir',
'PixelArrayActiveAreas': (libcamera.Rectangle(16, 24, 4608, 2592),),
'PixelArraySize': (4608, 2592),
'Rotation': 180,
'ScalerCropMaximum': (0, 0, 0, 0),
'UnitCellSize': (1400, 1400)}
Raw sensor modes:
[0:01:42.336425740] [1674]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 1536x864-SBGGR10_CSI2P
[0:01:42.336740468] [1681]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 1536x864-SBGGR10_1X10 - Selected unicam format: 1536x864-pBAA
[0:01:42.352519635] [1674]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 2304x1296-SBGGR10_CSI2P
[0:01:42.352823270] [1681]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 2304x1296-SBGGR10_1X10 - Selected unicam format: 2304x1296-pBAA
[0:01:42.386392251] [1674]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 4608x2592-SBGGR10_CSI2P
[0:01:42.386722646] [1681]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 4608x2592-SBGGR10_1X10 - Selected unicam format: 4608x2592-pBAA
[{'bit_depth': 10,
'crop_limits': (0, 0, 4608, 2592),
'exposure_limits': (9, 603302, None),
'format': SRGGB10_CSI2P,
'fps': 120.13,
'size': (1536, 864),
'unpacked': 'SRGGB10'},
{'bit_depth': 10,
'crop_limits': (0, 0, 4608, 2592),
'exposure_limits': (13, 875283, None),
'format': SRGGB10_CSI2P,
'fps': 56.03,
'size': (2304, 1296),
'unpacked': 'SRGGB10'},
{'bit_depth': 10,
'crop_limits': (0, 0, 4608, 2592),
'exposure_limits': (26, 1722331, None),
'format': SRGGB10_CSI2P,
'fps': 14.35,
'size': (4608, 2592),
'unpacked': 'SRGGB10'}]
Camera controls:
{'AeConstraintMode': (0, 3, 0),
'AeEnable': (False, True, None),
'AeExposureMode': (0, 3, 0),
'AeMeteringMode': (0, 3, 0),
'AfMetering': (0, 1, 0),
'AfMode': (0, 2, 0),
'AfPause': (0, 2, 0),
'AfRange': (0, 2, 0),
'AfSpeed': (0, 1, 0),
'AfTrigger': (0, 1, 0),
'AfWindows': ((0, 0, 0, 0), (65535, 65535, 65535, 65535), (0, 0, 0, 0)),
'AnalogueGain': (1.0, 16.0, None),
'AwbEnable': (False, True, None),
'AwbMode': (0, 7, 0),
'Brightness': (-1.0, 1.0, 0.0),
'ColourCorrectionMatrix': (-16.0, 16.0, None),
'ColourGains': (0.0, 32.0, None),
'Contrast': (0.0, 32.0, 1.0),
'ExposureTime': (26, 1722331, None),
'ExposureValue': (-8.0, 8.0, 0.0),
'FrameDurationLimits': (69669, 1722936, None),
'LensPosition': (0.0, 32.0, 1.0),
'NoiseReductionMode': (0, 4, 0),
'Saturation': (0.0, 32.0, 1.0),
'ScalerCrop': ((0, 0, 64, 64), (0, 0, 4608, 2592), (576, 0, 3456, 2592)),
'Sharpness': (0.0, 16.0, 1.0)}
Exposure time:
min: 26, max: 1722331, default: None
AnalogGain:
min: 1.0, max: 16.0, default: None
Next step, i try it in "real life"
So far, thanks a lot.
Sigvald

I am happy to read this!
Your camera has auto-focus. This is something I have not implemented in the driver (because I do not have such a camera). In fact I have no idea how to handle this and will need to g**gle it. I hope you will get focused images.
I continuously work on the indi_pylibcamera driver. It is worth to update your copy from time to time: do git pull in the indi_pylibcamera folder or just download it again.
If the driver works for you I would like to ask you for a favor: could you please make pictures of a terrestrial object with each raw mode (on tab "image settings" or "Bildeinstellungen") and send me the FITS files? If possible make a picture of something with red, green and blue colors and do not change camera position between the pictures. I will add a PNG test pattern to this repository in a few minutes. For instance you can open this test pattern on your PC and make pictures of your screen. Or you print the pattern and pin it on a tree. With these pictures I will check if the color channels are right, if the frames have zero- or garbage filled columns (the HQ camera has such columns!) and if the smaller sized raw frames use binning. Than I can use this information in the driver. For HQ and v1 camera I already did that.
Thank you!
Noch ein schönes Wochenende,
Ronald
(Wir können auch auf deutsch kommunizieren. Vielleicht sind aber auch noch andere Leute an der Lösung dieses Problems interessiert.)

PNG image with RGB testpattern is in subfolder "testpattern".

Hi Ronald,
as far as i could mention, the basic functions in kstars now do it properly.
As soon as the snow is over and we have a clear sky i try some pictures outside.
My great goal is to get the camera and the pi to work with an old tasco telescope. (T11)
That is because you didn't get 0,96 inch oculars. So i can use it for educational proposes in our aerea. (Lower Saxony)
I try to make the normal fotos for you with different aspects.
Sigvald

Hi,
I have to go just from the beginning. Something went wrong. I could start indiserver wit libcamera, start kstars and look for ekos config. Everthing seems ok, but no image would taken. Back to the shell. libcamera-hello fails also.
I documented my steps, so i probably i will find why.

Good morning Roland,
here a first status report. Well, I just reactivated my RPi3 B (vers. 1.2) with my old camera V2.1. As far as i can see, everthing works fine. Except there is a warning when i started your information program.
[1:37:12.618632049] [2206]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[1:37:12.691550856] [2207]  WARN RPI raspberrypi.cpp:1357 Mismatch between Unicam and CamHelper for embedded data usage!
[1:37:12.693051789] [2207]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx219@10 to Unicam device /dev/media3 and ISP device /dev/media0
Found 1 cameras.
Camera 0:
{'Id': '/base/soc/i2c0mux/i2c@1/imx219@10',
'Location': 2,
'Model': 'imx219',
'Rotation': 180}
Same warning occurs when starting indiserver.
Next steps playing around with EKOS an see if everthing works as suspected.
Then I try the V3 camera on the RPi3.
Nice weekend
SigvaldS

I had the same memory allocation error on a RPi Zero W and resolved it with
dtoverlay=vc4-fkms-v3d,cma-256
in /boot/config.txt
CS, Markus

Hi Roland,
still working to get mit Pi up and running. You have to be al little more patient.
Sigvald

Hello Sigvald,
No need to hurry. I hope you get the trouble managed.
Best Regards,
Ronald

Hi,
seems there are only minor problems left.
[21:28:26.913572751] [28429]  WARN IPAManager ipa_manager.cpp:114 Public key not valid
[21:28:26.917766237] [28429]  INFO Camera camera_manager.cpp:298 libcamera v0.0.4+40-e39f046f
[21:28:26.955445109] [28430]  WARN CameraSensorProperties camera_sensor_properties.cpp:245 No static properties available for 'imx708_noir'
[21:28:26.955683126] [28430]  WARN CameraSensorProperties camera_sensor_properties.cpp:247 Please consider updating the camera sensor properties database
[21:28:27.095526423] [28430]  INFO RPI raspberrypi.cpp:1487 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media0 and ISP device /dev/media1
[21:28:27.098508473] [28429]  INFO Camera camera.cpp:1028 configuring streams: (0) 2304x1296-YUV420
[21:28:27.100328070] [28430]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 2304x1296-SBGGR10_1X10 - Selected unicam format: 2304x1296-pBAA
Stream configuration adjusted
[21:28:32.314699981] [28429]  INFO Camera camera.cpp:1028 configuring streams: (0) 4608x2592-YUV420 (1) 4608x2592-SBGGR10_CSI2P
[21:28:32.321990535] [28430]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 4608x2592-SBGGR10_1X10 - Selected unicam format: 4608x2592-pBAA
Still capture image received
Bayer format is BGGR-10
nice sunday,
Sigvald

Hi,
just playing aroung with such options:
libcamera-still -o /home/User/Pictures/raw/test.jpg --shutter 110000000 -r -n --gain 1 --awbgains 1,1 --lens-position 0.0 --mode 4608:2592 --tuning-file /usr/share/libcamera/ipa/raspberrypi/imx708_noir.json
Looks pretty well.
Sigvald

Hi Roland,
seems i run into the next trouble. all libcamera-apps run fine. but kstars crashed, if i try indi_pylibamera driver.
indiserver -v ./indi_pylibcamera.py
2023-03-31T09:27:03: startup: indiserver -v ./indi_pylibcamera.py
2023-03-31T09:27:03: Driver ./indi_pylibcamera.py: pid=31980 rfd=6 wfd=6 efd=7
2023-03-31T09:27:03: listening to port 7624 on fd 5
2023-03-31T09:27:03: Local server: listening on local domain at: @/tmp/indiserver
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py: [66:03:37.129035619] [31980]  WARN IPAManager ipa_manager.cpp:114 Public key not valid
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py: [66:03:37.132382546] [31980]  INFO Camera camera_manager.cpp:298 libcamera v0.0.4+40-e39f046f
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py: [66:03:37.161121420] [31981]  WARN CameraSensorProperties camera_sensor_properties.cpp:245 No static properties available for 'imx708_noir'
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py: [66:03:37.161210012] [31981]  WARN CameraSensorProperties camera_sensor_properties.cpp:247 Please consider updating the camera sensor properties database
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py: [66:03:37.329959040] [31981]  INFO RPI raspberrypi.cpp:1487 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media1 and ISP device /dev/media0
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py: root-INFO- found cameras: [{'Model': 'imx708_noir', 'Location': 2, 'Rotation': 180, 'Id': '/base/soc/i2c0mux/i2c@1/imx708@1a'}]
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py: root-INFO- Parsed data from client:
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py:
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py:
2023-03-31T09:27:04: Driver ./indi_pylibcamera.py: root-INFO- End client data
2023-03-31T09:30:14: Client 9: new arrival from <IP_ADDRESS>:45754 - welcome!
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: root-INFO- Parsed data from client:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: root-INFO- End client data
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: root-INFO- Parsed data from client:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: On
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: root-INFO- End client data
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: root-INFO- connecting to camera /base/soc/i2c0mux/i2c@1/imx708@1a
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: root-INFO- closing camera
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: root-INFO- closing camera
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: root-INFO- opening camera
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: [66:06:47.319636752] [31980]  WARN IPAManager ipa_manager.cpp:114 Public key not valid
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: [66:06:47.323296675] [31980]  INFO Camera camera_manager.cpp:298 libcamera v0.0.4+40-e39f046f
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: [66:06:47.351590519] [31988]  WARN CameraSensorProperties camera_sensor_properties.cpp:245 No static properties available for 'imx708_noir'
2023-03-31T09:30:14: Driver ./indi_pylibcamera.py: [66:06:47.351665981] [31988]  WARN CameraSensorProperties camera_sensor_properties.cpp:247 Please consider updating the camera sensor properties database
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: [66:06:47.519293454] [31988]  INFO RPI raspberrypi.cpp:1487 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media1 and ISP device /dev/media0
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Initialization successful.
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Camera now open.
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: root-INFO- camera properties: {'Model': 'imx708_noir', 'Location': 2, 'Rotation': 180, 'PixelArraySize': (4608, 2592), 'PixelArrayActiveAreas': (libcamera.Rectangle(16, 24, 4608, 2592),), 'ColorFilterArrangement': 0, 'ScalerCropMaximum': (0, 0, 0, 0)}
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Camera configuration has been adjusted!
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: [66:06:47.535443465] [31980]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 1536x864-SBGGR10_CSI2P
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: [66:06:47.537228520] [31988]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 1536x864-SBGGR10_1X10 - Selected unicam format: 1536x864-pBAA
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Configuration successful!
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Camera configuration has been adjusted!
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: [66:06:47.566537353] [31980]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 2304x1296-SBGGR10_CSI2P
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: [66:06:47.568594368] [31988]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 2304x1296-SBGGR10_1X10 - Selected unicam format: 2304x1296-pBAA
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Configuration successful!
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Camera configuration has been adjusted!
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: [66:06:47.609495372] [31980]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 4608x2592-SBGGR10_CSI2P
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: [66:06:47.611427907] [31988]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 4608x2592-SBGGR10_1X10 - Selected unicam format: 4608x2592-pBAA
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Configuration successful!
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: Traceback (most recent call last):
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/././indi_pylibcamera.py", line 756, in
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: Exception in thread Thread-1:
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: Traceback (most recent call last):
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     self.run()
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/usr/lib/python3.9/threading.py", line 892, in run
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     device.run()
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/indidevice.py", line 737, in run
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     self._target(*self._args, **self._kwargs)
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/CameraControl.py", line 431, in __ExposureLoop
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     self.message_loop()
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/indidevice.py", line 716, in message_loop
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     self.checkAbort()
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/CameraControl.py", line 390, in checkAbort
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     vector.set_byClient(values)
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/././indi_pylibcamera.py", line 117, in set_byClient
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     if self.parent.openCamera():
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/././indi_pylibcamera.py", line 399, in openCamera
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     if self.parent.knownVectors["CCD_ABORT_EXPOSURE"]["ABORT"].value == ISwitchState.ON:
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/indidevice.py", line 607, in getitem
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     IText(name="CAMERA_UNITCELLSIZE", label="Pixel size", value=str(self.CameraThread.getProp("UnitCellSize"))),
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/CameraControl.py", line 275, in getProp
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     raise ValueError(f'vector list {self.name} has no vector {name}!')
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: ValueError: vector list knownVectors has no vector CCD_ABORT_EXPOSURE!
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py:     return self.CamProps[name]
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: KeyError: 'UnitCellSize'
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: stderr EOF
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: read EOF

2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: restart #0
2023-03-31T09:30:15: Driver ./indi_pylibcamera.py: pid=31994 rfd=7 wfd=7 efd=10
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py: [66:06:48.769748214] [31994]  WARN IPAManager ipa_manager.cpp:114 Public key not valid
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py: [66:06:48.773118067] [31994]  INFO Camera camera_manager.cpp:298 libcamera v0.0.4+40-e39f046f
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py: [66:06:48.802513398] [31995]  WARN CameraSensorProperties camera_sensor_properties.cpp:245 No static properties available for 'imx708_noir'
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py: [66:06:48.802606472] [31995]  WARN CameraSensorProperties camera_sensor_properties.cpp:247 Please consider updating the camera sensor properties database
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py: [66:06:48.967440771] [31995]  INFO RPI raspberrypi.cpp:1487 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media1 and ISP device /dev/media0
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py: root-INFO- found cameras: [{'Model': 'imx708_noir', 'Location': 2, 'Rotation': 180, 'Id': '/base/soc/i2c0mux/i2c@1/imx708@1a'}]
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py: root-INFO- Parsed data from client:
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py:
2023-03-31T09:30:16: Driver ./indi_pylibcamera.py: root-INFO- End client data
2023-03-31T09:30:16: Client 9: read: Connection reset by peer
2023-03-31T09:30:16: Client 9: shut down complete - bye!
i tried your new program, but get the same result.. with the default simulators everthing works well in kstars.
sincerly Sigvald

@SigvaldS42 Did you run KStars from remote machine or from Raspberry Pi device?
I had problems too using indi_pylibcamera driver from KStars installed on Raspberry Pi device. Remotely from Windows it worked just fine.
Did you used build-soft-latest.sh or build-soft-stable.sh script?
I resolved the issue with running the astro-soft-build script again using ./build-soft-stable.sh.
Installation instructions here:
https://saimons-astronomy.webador.com/1216039_rapspberry-pi-hq-camera-with-ekos-and-indi-libcamera-driver

Hi Simon, i tried both. Local and remote. As far as i'm remember i try the stable version. i'll could try the latest version in the afternoon.
Sigvald

Hello Roland and Simon,
i just did a new installation. for any reason there was no indi_pylibcamera.ini file. i correct that, uncomment the UnitCellSize and edited it to 1400. Then i compile the astro-soft-build with the stable shell.
But still new errors.
dsl@astropi4:~/Projects/indi_pylibcamera $ indiserver -v ./indi_pylibcamera.py
2023-03-31T21:00:44: startup: indiserver -v ./indi_pylibcamera.py
2023-03-31T21:00:44: Driver ./indi_pylibcamera.py: pid=2862 rfd=6 wfd=6 efd=7
2023-03-31T21:00:44: listening to port 7624 on fd 5
2023-03-31T21:00:44: Local server: listening on local domain at: @/tmp/indiserver
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py: [0:33:41.225062619] [2862]  WARN IPAManager ipa_manager.cpp:114 Public key not valid
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py: [0:33:41.227933162] [2862]  INFO Camera camera_manager.cpp:298 libcamera v0.0.4+40-e39f046f
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py: [0:33:41.253864643] [2863]  WARN CameraSensorProperties camera_sensor_properties.cpp:245 No static properties available for 'imx708_noir'
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py: [0:33:41.253932867] [2863]  WARN CameraSensorProperties camera_sensor_properties.cpp:247 Please consider updating the camera sensor properties database
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py: [0:33:41.391121921] [2863]  INFO RPI raspberrypi.cpp:1487 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media4 and ISP device /dev/media1
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py: root-INFO- found cameras: [{'Model': 'imx708_noir', 'Location': 2, 'Rotation': 180, 'Id': '/base/soc/i2c0mux/i2c@1/imx708@1a'}]
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py: root-INFO- Parsed data from client:
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py:
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py:
2023-03-31T21:00:45: Driver ./indi_pylibcamera.py: root-INFO- End client data
2023-03-31T21:02:01: Client 9: new arrival from <IP_ADDRESS>:60158 - welcome!
2023-03-31T21:02:01: Driver ./indi_pylibcamera.py: root-INFO- Parsed data from client:
2023-03-31T21:02:01: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:01: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:01: Driver ./indi_pylibcamera.py: root-INFO- End client data
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: root-INFO- Parsed data from client:
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: On
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: root-INFO- End client data
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: root-INFO- connecting to camera /base/soc/i2c0mux/i2c@1/imx708@1a
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: root-INFO- closing camera
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: root-INFO- closing camera
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: root-INFO- opening camera
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.595486899] [2862]  WARN IPAManager ipa_manager.cpp:114 Public key not valid
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.601328877] [2862]  INFO Camera camera_manager.cpp:298 libcamera v0.0.4+40-e39f046f
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.650832596] [2924]  WARN CameraSensorProperties camera_sensor_properties.cpp:245 No static properties available for 'imx708_noir'
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.650960098] [2924]  WARN CameraSensorProperties camera_sensor_properties.cpp:247 Please consider updating the camera sensor properties database
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.784418358] [2924]  INFO RPI raspberrypi.cpp:1487 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media4 and ISP device /dev/media1
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Initialization successful.
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Camera now open.
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: root-INFO- camera properties: {'Model': 'imx708_noir', 'Location': 2, 'Rotation': 180, 'PixelArraySize': (4608, 2592), 'PixelArrayActiveAreas': (libcamera.Rectangle(16, 24, 4608, 2592),), 'ColorFilterArrangement': 0, 'ScalerCropMaximum': (0, 0, 0, 0)}
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Camera configuration has been adjusted!
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.798242735] [2862]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 1536x864-SBGGR10_CSI2P
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.800219951] [2924]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 1536x864-SBGGR10_1X10 - Selected unicam format: 1536x864-pBAA
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Configuration successful!
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Camera configuration has been adjusted!
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.830947901] [2862]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 2304x1296-SBGGR10_CSI2P
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.832802708] [2924]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 2304x1296-SBGGR10_1X10 - Selected unicam format: 2304x1296-pBAA
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Configuration successful!
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Camera configuration has been adjusted!
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.870471320] [2862]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-XBGR8888 (1) 4608x2592-SBGGR10_CSI2P
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: [0:34:57.871614652] [2924]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 4608x2592-SBGGR10_1X10 - Selected unicam format: 4608x2592-pBAA
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: picamera2.picamera2-INFO- Configuration successful!
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: Traceback (most recent call last):
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/././indi_pylibcamera.py", line 756, in
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: Exception in thread Thread-1:
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: Traceback (most recent call last):
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     device.run()
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/indidevice.py", line 737, in run
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     self.message_loop()
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/indidevice.py", line 716, in message_loop
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     vector.set_byClient(values)
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/././indi_pylibcamera.py", line 117, in set_byClient
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     if self.parent.openCamera():
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/././indi_pylibcamera.py", line 399, in openCamera
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     IText(name="CAMERA_UNITCELLSIZE", label="Pixel size", value=str(self.CameraThread.getProp("UnitCellSize"))),
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/CameraControl.py", line 275, in getProp
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     self.run()
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     return self.CamProps[name]
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: KeyError: 'UnitCellSize'
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/usr/lib/python3.9/threading.py", line 892, in run
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     self._target(*self._args, **self._kwargs)
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/CameraControl.py", line 431, in __ExposureLoop
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     self.checkAbort()
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/CameraControl.py", line 390, in checkAbort
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     if self.parent.knownVectors["CCD_ABORT_EXPOSURE"]["ABORT"].value == ISwitchState.ON:
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:   File "/home/dsl/Projects/indi_pylibcamera/indidevice.py", line 607, in getitem
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py:     raise ValueError(f'vector list {self.name} has no vector {name}!')
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: ValueError: vector list knownVectors has no vector CCD_ABORT_EXPOSURE!
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: stderr EOF
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: read EOF

2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: restart #0
2023-03-31T21:02:02: Driver ./indi_pylibcamera.py: pid=2930 rfd=7 wfd=7 efd=10
2023-03-31T21:02:02: Client 9: read EOF
2023-03-31T21:02:02: Client 9: shut down complete - bye!
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py: [0:34:59.055680789] [2930]  WARN IPAManager ipa_manager.cpp:114 Public key not valid
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py: [0:34:59.058561129] [2930]  INFO Camera camera_manager.cpp:298 libcamera v0.0.4+40-e39f046f
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py: [0:34:59.085080183] [2931]  WARN CameraSensorProperties camera_sensor_properties.cpp:245 No static properties available for 'imx708_noir'
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py: [0:34:59.085148887] [2931]  WARN CameraSensorProperties camera_sensor_properties.cpp:247 Please consider updating the camera sensor properties database
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py: [0:34:59.220559585] [2931]  INFO RPI raspberrypi.cpp:1487 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media4 and ISP device /dev/media1
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py: root-INFO- found cameras: [{'Model': 'imx708_noir', 'Location': 2, 'Rotation': 180, 'Id': '/base/soc/i2c0mux/i2c@1/imx708@1a'}]
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py: root-INFO- Parsed data from client:
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py:
2023-03-31T21:02:03: Driver ./indi_pylibcamera.py: root-INFO- End client data
the normal libcamera-apps function as they should.
Seems we got a "nice" weekend. ;-o
Sigvald

Good morning everybody.
i have to raise a all-clear signal.
Sometimes it's better to look at everything instead of doing something right from memory.
I just used the indi_pylibcamera-main directory to start indiserver and changed in EKOS thr camera headword to indi_pylibcamery.py
What should i say, everthing works allright.
Lets see what happen after a reboot.
So Roland should receive the RGB-shots this weekend.
CS Sigvald --- still raing here :-(

ok guys,
"WARN IPAManager ipa_manager.cpp:114 Public key not valid" is solved. openssl and co. are not installed by default. it's now corrected. there is a hint at libcamera git readme.
the warinings about the imx708_noir are on focus of the libcamera developers and will be eliminated with the next offical update.
so everything is fine now. thank you for your support.
Any further questions, let me know.
Sigvald

Hi Sigvald,
I am happy that you do not get errors anymore. I was already confused about the log you sent.
Wish you a nice weekend with better weather,
Ronald

wtf! sorry, but after cold start i got this:
libcamera-hello
Made X/EGL preview window
[0:14:46.029946331] [2298]  INFO Camera camera_manager.cpp:298 libcamera v0.0.4+55-ac7511dc
[0:14:46.090283869] [2302]  WARN CameraSensorProperties camera_sensor_properties.cpp:245 No static properties available for 'imx708_noir'
[0:14:46.090509346] [2302]  WARN CameraSensorProperties camera_sensor_properties.cpp:247 Please consider updating the camera sensor properties database
[0:14:46.421429111] [2302]  INFO RPI raspberrypi.cpp:1487 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media1 and ISP device /dev/media2
[0:14:46.424677442] [2298]  INFO Camera camera.cpp:1028 configuring streams: (0) 2304x1296-YUV420
[0:14:46.425847255] [2302]  INFO RPI raspberrypi.cpp:857 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 2304x1296-SBGGR10_1X10 - Selected unicam format: 2304x1296-pBAA
[0:14:48.113368559] [2306] ERROR IPARPI cam_helper_imx708.cpp:250 PDAF data in unsupported format
[0:14:48.246387907] [2306] ERROR IPARPI cam_helper_imx708.cpp:250 PDAF data in unsupported format
[0:14:49.146414030] [2306] ERROR IPARPI cam_helper_imx708.cpp:250 PDAF data in unsupported format
[0:14:50.112378794] [2306] ERROR IPARPI cam_helper_imx708.cpp:250 PDAF data in unsupported format
[0:14:50.146367564] [2306] ERROR IPARPI cam_helper_imx708.cpp:250 PDAF data in unsupported format
[0:14:51.112270121] [2306] ERROR IPARPI cam_helper_imx708.cpp:250 PDAF data in unsupported format
[0:14:51.145940009] [2306] ERROR IPARPI cam_helper_imx708.cpp:250 PDAF data in unsupported format
[0:14:51.178844744] [2306] ERROR IPARPI cam_helper_imx708.cpp:250 PDAF data in unsupported format
ok, so still searching for bugs
Sigvald

Oh no!!! Libcamera still has errors.
Does libcamera --list-cameras  work without errors? Output for my HQ camera is:
cam@indicam01:~ $ libcamera-hello --list-cameras
Available cameras
-----------------
0 : imx477 [4056x3040] (/base/soc/i2c0mux/i2c@1/imx477@1a)
    Modes: 'SRGGB10_CSI2P' : 1332x990 [120.05 fps - (696, 528)/2664x1980 crop]
           'SRGGB12_CSI2P' : 2028x1080 [50.03 fps - (0, 440)/4056x2160 crop]
                             2028x1520 [40.01 fps - (0, 0)/4056x3040 crop]
                             4056x3040 [10.00 fps - (0, 0)/4056x3040 crop]

Does libcamera-raw -o test.raw work without errors? My HQ cam shows:
cam@indicam01:~ $ libcamera-raw -o test.raw
[0:18:34.396960133] [4663]  INFO Camera camera_manager.cpp:299 libcamera v0.0.4+22-923f5d70
[0:18:34.559259886] [4664]  INFO RPI raspberrypi.cpp:1476 Registered camera /base/soc/i2c0mux/i2c@1/imx477@1a to Unicam device /dev/media3 and ISP device /dev/media0
Stream configuration adjusted
[0:18:34.567978819] [4663]  INFO Camera camera.cpp:1028 configuring streams: (0) 640x480-YUV420 (1) 2028x1520-SBGGR12_CSI2P
[0:18:34.571954789] [4664]  INFO RPI raspberrypi.cpp:851 Sensor: /base/soc/i2c0mux/i2c@1/imx477@1a - Selected sensor format: 2028x1520-SBGGR12_1X12 - Selected unicam format: 2028x1520-pBCC
Raw stream: 2028x1520 stride 3072 format SBGGR12_CSI2P

It also created a large test.raw file.

Hello Roland,
did the attached files fullfill your need for testpatterns?
Otherwise let me know.
Sigvald
Raw-Testpattern.zip

Hi, next update.
I'm not sure why libcamera-hello have such strange behavior.
But to make it clear. Kstars with indi_pylibcamera works fine without any errors or warnings.
So you should possible close this issue.
Thank you for your support and help.
Sigvald

Hello Sigvald,
thank you for the test pictures. I see there that the image sizes 2304x1296 and 1536x864 are done with 2x2 binning.
A minute ago I updated the binning table in the driver. With the new version the binning will automatically change when you select a raw mode. In opposite, when you change binning (X and Y must be equal!) automatically a fitting raw mode gets selected.

The screen shot is from my HQ camera. You will have 3 other raw modes.
When taking pictures you can change binning (and raw mode) with the binning input in the Ekos camera tab:

Best Regards,
Ronald

Hello Ronald,
until now, everthing works fine without any error or waring.

Next step, to implement all at my telescope.
CS Sigvald

No communication since one year. I will close this issue.


Restructure

Docs Build status updates of commit fe9dafc:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/_old/concepts/Cards/cards-actions.md
:warning:Warning

Details

msteams-platform/_old/concepts/Cards/cards-reference.md
:warning:Warning

Details

msteams-platform/_old/concepts/Cards/cards.md
:warning:Warning

Details

msteams-platform/_old/concepts/activity-feed.md
:warning:Warning

Details

msteams-platform/_old/concepts/apps/apps-design.md
:warning:Warning

Details

msteams-platform/_old/concepts/apps/apps-overview.md
:warning:Warning

Details

msteams-platform/_old/concepts/apps/apps-package.md
:warning:Warning

Details

msteams-platform/_old/concepts/apps/apps-upload.md
:warning:Warning

Details

msteams-platform/_old/concepts/authentication/auth-bot-AAD.md
:warning:Warning

Details

msteams-platform/_old/concepts/authentication/auth-flow-bot.md
:warning:Warning

Details

msteams-platform/_old/concepts/authentication/auth-flow-tab.md
:warning:Warning

Details

msteams-platform/_old/concepts/authentication/auth-oauth-card.md
:warning:Warning

Details

msteams-platform/_old/concepts/authentication/auth-tab-AAD.md
:warning:Warning

Details

msteams-platform/_old/concepts/authentication/authentication.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bot-conversations/bots-cards.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bot-conversations/bots-conv-channel.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bot-conversations/bots-conv-personal.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bot-conversations/bots-conv-proactive.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bot-conversations/bots-conversations.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bot-conversations/bots-message-format.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-context.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-create.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-files.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-menus.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-notification-only.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-notifications.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-overview.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-test.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-text-formats.md
:warning:Warning

Details

msteams-platform/_old/concepts/bots/bots-with-tabs.md
:warning:Warning

Details

msteams-platform/_old/concepts/calls-and-meetings/call-notifications.md
:warning:Warning

Details

msteams-platform/_old/concepts/calls-and-meetings/calls-meetings-bots-overview.md
:warning:Warning

Details

msteams-platform/_old/concepts/calls-and-meetings/debugging-local-testing-calling-meeting-bots.md
:warning:Warning

Details

msteams-platform/_old/concepts/calls-and-meetings/real-time-media-concepts.md
:warning:Warning

Details

msteams-platform/_old/concepts/calls-and-meetings/registering-calling-bot.md
:warning:Warning

Details

msteams-platform/_old/concepts/concepts-overview.md
:warning:Warning

Details

msteams-platform/_old/concepts/connectors/connectors-creating.md
:warning:Warning

Details

msteams-platform/_old/concepts/connectors/connectors-using.md
:warning:Warning

Details

msteams-platform/_old/concepts/connectors/connectors.md
:warning:Warning

Details

msteams-platform/_old/concepts/deep-links.md
:warning:Warning

Details

msteams-platform/_old/concepts/messaging-extensions/create-extensions.md
:warning:Warning

Details

msteams-platform/_old/concepts/messaging-extensions/messaging-extensions-common.md
:warning:Warning

Details

msteams-platform/_old/concepts/messaging-extensions/messaging-extensions-overview.md
:warning:Warning

Details

msteams-platform/_old/concepts/messaging-extensions/search-extensions.md
:warning:Warning

Details

msteams-platform/_old/concepts/outgoingwebhook.md
:warning:Warning

Details

msteams-platform/_old/concepts/tabs/cross-domain.md
:warning:Warning

Details

msteams-platform/_old/concepts/tabs/tabs-configurable.md
:warning:Warning

Details

msteams-platform/_old/concepts/tabs/tabs-configuration.md
:warning:Warning

Details

msteams-platform/_old/concepts/tabs/tabs-content.md
:warning:Warning

Details

This comment lists only the first 50 files in the pull request.

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/old/samples/app-templates.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/old/samples/code-samples.md).
Line 0: [Warning] Invalid file link:(~/old/samples/code-samples.md).
Line 0: [Warning] Invalid file link:(~/old/samples/code-samples.md).
Line 0: [Warning] Invalid file link:(~/old/samples/code-samples.md).
Line 0: [Warning] Invalid file link:(~/old/samples/code-samples.md).

msteams-platform/_old/concepts/Cards/cards-actions.md

Line 24: [Warning] Invalid file link:(~/concepts/cards/cards-actions#adaptive-card-actions).
Line 135: [Warning] Invalid file link:(~/concepts/task-modules/task-modules-bots.md).
Line 214: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).

msteams-platform/_old/concepts/Cards/cards-reference.md

Line 56: [Warning] Invalid file link:(~/concepts/cards/cards-actions.md).
Line 60: [Warning] Invalid file link:(~/concepts/cards/cards-format.md).
Line 216: [Warning] Invalid file link:(~/concepts/cards/cards-actions.md#adaptive-card-actions).
Line 235: [Warning] Invalid file link:(~/concepts/cards/cards-format.md).
Line 374: [Warning] Invalid file link:(~/concepts/cards/cards-format.md).
Line 386: [Warning] Invalid file link:(~/get-started/code.md#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 477: [Warning] Invalid file link:(~/get-started/code.md#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 503: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot.md).
Line 538: [Warning] Invalid file link:(~/concepts/cards/cards-format.md).

msteams-platform/_old/concepts/Cards/cards.md

Line 9: [Warning] Invalid file link:(~/concepts/cards/cards-actions).
Line 13: [Warning] Invalid file link:(~/concepts/cards/cards-reference#adaptive-card).
Line 20: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 30: [Warning] Invalid file link:(~/concepts/connectors/connectors).
Line 32: [Warning] Invalid file link:(~/concepts/connectors/connectors#access-existing-office-365-connectors-from-microsoft-teams).
Line 38: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 42: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 42: [Warning] Invalid file link:(~/concepts/messaging-extensions).
Line 46: [Warning] Invalid file link:(~/concepts/cards/cards-reference).

msteams-platform/_old/concepts/activity-feed.md

Line 82: [Warning] Invalid file link:(~/concepts/deep-links.md).
Line 89: [Warning] Invalid file link:(~/concepts/bots/bots-notification-only.md).

msteams-platform/_old/concepts/apps/apps-design.md

Line 19: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 20: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 21: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 29: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 30: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 30: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 31: [Warning] Invalid file link:(~/concepts/connectors/connectors).
Line 32: [Warning] Invalid file link:(~/concepts/compose-extensions).
Line 33: [Warning] Invalid file link:(~/concepts/custom-bot).

msteams-platform/_old/concepts/apps/apps-overview.md

Line 15: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview.md).
Line 16: [Warning] Invalid file link:(~/concepts/bots/bots-overview.md).
Line 17: [Warning] Invalid file link:(~/concepts/connectors/connectors.md).
Line 18: [Warning] Invalid file link:(~/concepts/compose-extensions.md).
Line 19: [Warning] Invalid file link:(~/concepts/activity-feed.md).
Line 20: [Warning] Invalid file link:(~/concepts/outgoingwebhook.md).
Line 22: [Warning] Invalid file link:(~/concepts/apps/apps-package.md).
Line 24: [Warning] Invalid file link:(~/get-started/get-started-app-studio.md).
Line 26: [Warning] Invalid file link:(~/concepts/apps/apps-design.md).
Line 26: [Warning] Invalid file link:(~/resources/design/overview.md).
Line 28: [Warning] Invalid file link:(~/concepts/apps/apps-upload.md).
Line 36: [Warning] Invalid file link:(~/get-started/get-started-dotnet-app-studio.md).
Line 37: [Warning] Invalid file link:(~/get-started/get-started-nodejs-app-studio.md).

msteams-platform/_old/concepts/apps/apps-package.md

Line 10: [Warning] Invalid file link:(~/concepts/apps/apps-upload.md).
Line 19: [Warning] Invalid file link:(~/get-started/get-started-app-studio.md).
Line 21: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md).

msteams-platform/_old/concepts/apps/apps-upload.md

Line 15: [Warning] Invalid file link:(~/resources/dev-preview/developer-preview-intro.md).
Line 17: [Warning] Invalid file link:(~/concepts/bots/bots-test.md#talk-to-your-bot-directly-by-id).
Line 23: [Warning] Invalid file link:(~/concepts/apps/apps-package.md).
Line 50: [Warning] Invalid file link:(~/resources/dev-preview/developer-preview-intro.md).
Line 85: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration.md).
Line 107: [Warning] Invalid file link:(~/concepts/connectors/connectors.md).
Line 128: [Warning] Invalid file link:(~/concepts/apps/apps-package.md).
Line 128: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md).

msteams-platform/_old/concepts/authentication/auth-bot-AAD.md

Line 15: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).
Line 19: [Warning] Invalid file link:(~/concepts/authentication/auth-configure).
Line 56: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).
Line 58: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).

msteams-platform/_old/concepts/authentication/auth-flow-bot.md

Line 49: [Warning] Invalid file link:(~/concepts/authentication/auth-bot-AAD.md).

msteams-platform/_old/concepts/authentication/auth-flow-tab.md

Line 42: [Warning] Invalid file link:(~/concepts/authentication/auth-tab-AAD).
Line 43: [Warning] Invalid file link:(~/concepts/authentication/auth-silent-AAD).

msteams-platform/_old/concepts/authentication/auth-oauth-card.md

Line 18: [Warning] Invalid file link:(~/concepts/authentication/authentication).
Line 47: [Warning] Invalid file link:(~/concepts/authentication/authentication).
Line 54: [Warning] Invalid file link:(~/concepts/authentication/auth-configure).

msteams-platform/_old/concepts/authentication/auth-tab-AAD.md

Line 15: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-tab).
Line 21: [Warning] Invalid file link:(~/concepts/authentication/auth-configure).
Line 27: [Warning] Invalid file link:(~/concepts/tabs/tabs-content).
Line 27: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 49: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).
Line 86: [Warning] Invalid file link:(~/concepts/tabs/tabs-context).
Line 140: [Warning] Invalid file link:(~/concepts/authentication/auth-silent-AAD).
Line 142: [Warning] Invalid file link:(~/concepts/authentication/auth-bot-AAD).

msteams-platform/_old/concepts/authentication/authentication.md

Line 15: [Warning] Invalid file link:(~/concepts/authentication/auth-oauth-card).
Line 23: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-tab).
Line 24: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-bot).
Line 30: [Warning] Invalid file link:(~/concepts/authentication/auth-tab-AAD).
Line 31: [Warning] Invalid file link:(~/concepts/authentication/auth-bot-AAD).
Line 32: [Warning] Invalid file link:(~/concepts/authentication/auth-silent-AAD).

msteams-platform/_old/concepts/bots/bot-conversations/bots-cards.md

Line 9: [Warning] Invalid file link:(~/concepts/cards/cards.md).
Line 11: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations.md).
Line 13: [Warning] Invalid file link:(~/concepts/cards/cards-reference.md).
Line 15: [Warning] Invalid file link:(~/concepts/cards/cards-actions.md).

msteams-platform/_old/concepts/bots/bot-conversations/bots-conv-channel.md

Line 22: [Warning] Invalid file link:(~/concepts/apps/apps-overview.md).
Line 28: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md).
Line 28: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md#creating-a-channel-conversation).
Line 34: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations.md#teams-channel-data).
Line 50: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md#team-member-or-bot-addition).
Line 52: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md).
Line 52: [Warning] Invalid file link:(~/concepts/bots/bots-context.md#fetching-the-team-roster).
Line 61: [Warning] Invalid file link:(~/resources/design/overview.md).
Line 115: [Warning] Invalid file link:(~/get-started/code.md#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 197: [Warning] Invalid file link:(~/concepts/bots/bots-context.md).

msteams-platform/_old/concepts/bots/bot-conversations/bots-conv-personal.md

Line 9: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel.md).
Line 11: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md).
Line 21: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md).
Line 23: [Warning] Invalid file link:(~/resources/design/overview.md).

msteams-platform/_old/concepts/bots/bot-conversations/bots-conv-proactive.md

Line 21: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md#team-member-or-bot-addition).
Line 21: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel.md).
Line 21: [Warning] Invalid file link:(~/concepts/bots/bots-context.md#fetching-the-team-roster).

msteams-platform/_old/concepts/bots/bot-conversations/bots-conversations.md

Line 17: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel.md).
Line 18: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-personal.md).
Line 20: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md).
Line 34: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md).
Line 48: [Warning] Invalid file link:(~/concepts/cards/cards-reference.md).
Line 56: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-message-format.md).
Line 59: [Warning] Invalid file link:(~/concepts/bots/bots-text-formats.md).
Line 61: [Warning] Invalid file link:(~/concepts/cards/cards-format.md).
Line 81: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md#channel-updates).
Line 145: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel.md#-mentions).
Line 155: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md#channel-updates).
Line 159: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md#team-name-updates).
Line 162: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md#channel-updates).
Line 199: [Warning] Invalid file link:(~/concepts/cards-actions.md).
Line 270: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md#starting-personal-conversations).
Line 271: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md#creating-a-channel-conversation).
Line 273: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md).

msteams-platform/_old/concepts/bots/bot-conversations/bots-message-format.md

Line 69: [Warning] Invalid file link:(~/concepts/cards/cards-format.md).

msteams-platform/_old/concepts/bots/bots-context.md

Line 22: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md#bot-or-user-added-to-a-team).
Line 124: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md#team-member-or-bot-addition).

msteams-platform/_old/concepts/bots/bots-create.md

Line 14: [Warning] Invalid file link:(~/get-started/get-started.md).
Line 20: [Warning] Invalid file link:(~/get-started/get-started-app-studio.md).
Line 36: [Warning] Invalid file link:(~/resources/general/debug.md).
Line 40: [Warning] Invalid file link:(~/concepts/apps/apps-package.md).
Line 40: [Warning] Invalid file link:(~/concepts/apps/apps-upload.md).
Line 41: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview.md).
Line 41: [Warning] Invalid file link:(~/concepts/apps/apps-design.md#map-your-scenario-to-teams-capabilities).

msteams-platform/_old/concepts/bots/bots-files.md

Line 33: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md#bots).

msteams-platform/_old/concepts/bots/bots-menus.md

Line 18: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md#botscommandlists).

msteams-platform/_old/concepts/bots/bots-notification-only.md

Line 15: [Warning] Invalid file link:(~/concepts/activity-feed.md).
Line 44: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md).
Line 45: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md#starting-personal-conversations).
Line 46: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md#creating-a-channel-conversation).

msteams-platform/_old/concepts/bots/bots-notifications.md

Line 17: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations.md).
Line 42: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-channel.md#best-practice-welcome-messages-in-teams).
Line 125: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-personal.md#best-practice-welcome-messages-in-personal-conversations).

msteams-platform/_old/concepts/bots/bots-overview.md

Line 14: [Warning] Invalid file link:(~/concepts/outgoingwebhook.md).
Line 20: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md).
Line 26: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations.md).
Line 28: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview.md).
Line 28: [Warning] Invalid file link:(~/concepts/messaging-extensions/messaging-extensions-overview.md).
Line 47: [Warning] Invalid file link:(~/get-started/get-started-app-studio.md).
Line 51: [Warning] Invalid file link:(~/concepts/outgoingwebhook.md).
Line 61: [Warning] Invalid file link:(~/get-started/get-started-nodejs-app-studio.md).
Line 62: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview.md).
Line 62: [Warning] Invalid file link:(~/get-started/design.md#designing-a-great-bot).
Line 62: [Warning] Invalid file link:(~/concepts/tabs/tabs-static.md).
Line 63: [Warning] Invalid file link:(~/concepts/bots/bots-create.md).
Line 64: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations.md).
Line 64: [Warning] Invalid file link:(~/get-started/code.md#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 65: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-cards.md).
Line 66: [Warning] Invalid file link:(~/concepts/bots/bots-notifications.md).
Line 67: [Warning] Invalid file link:(~/concepts/bots/bots-notification-only.md).
Line 68: [Warning] Invalid file link:(~/concepts/bots/bots-context.md).
Line 69: [Warning] Invalid file link:(~/concepts/bots/bots-menus.md).
Line 70: [Warning] Invalid file link:(~/concepts/bots/bots-files.md).
Line 71: [Warning] Invalid file link:(~/concepts/bots/bots-with-tabs.md).
Line 72: [Warning] Invalid file link:(~/concepts/bots/bots-test.md).

msteams-platform/_old/concepts/bots/bots-test.md

Line 15: [Warning] Invalid file link:(~/concepts/apps/apps-package.md).
Line 15: [Warning] Invalid file link:(~/get-started/get-started-app-studio.md).
Line 15: [Warning] Invalid file link:(~/concepts/apps/apps-upload.md).
Line 27: [Warning] Invalid file link:(~/resources/general/debug.md#locally-hosted).

msteams-platform/_old/concepts/bots/bots-text-formats.md

Line 28: [Warning] Invalid file link:(~/concepts/cards/cards-reference).
Line 49: [Warning] Invalid file link:(~/concepts/bots/bots-conversations#cards).

msteams-platform/_old/concepts/bots/bots-with-tabs.md

Line 17: [Warning] Invalid file link:(~/concepts/authentication/authentication.md).
Line 23: [Warning] Invalid file link:(~/concepts/deep-links.md).

msteams-platform/_old/concepts/calls-and-meetings/call-notifications.md

Line 10: [Warning] Invalid file link:(~/concepts/calls-and-meetings/registering-calling-bot.md#creating-a-new-bot-or-adding-calling-capabilities-to-an-existing-bot).

msteams-platform/_old/concepts/calls-and-meetings/calls-meetings-bots-overview.md

Line 28: [Warning] Invalid file link:(~/concepts/calls-and-meetings/requirements-considerations-application-hosted-media-bots.md).
Line 36: [Warning] Invalid file link:(~/concepts/calls-and-meetings/registering-calling-bot.md).
Line 36: [Warning] Invalid file link:(~/concepts/calls-and-meetings/registering-calling-bot.md#add-microsoft-graph-permissions).
Line 37: [Warning] Invalid file link:(~/concepts/calls-and-meetings/debugging-local-testing-calling-meeting-bots.md).
Line 38: [Warning] Invalid file link:(~/concepts/calls-and-meetings/requirements-considerations-application-hosted-media-bots.md).
Line 38: [Warning] Invalid file link:(~/concepts/calls-and-meetings/real-time-media-concepts.md).
Line 39: [Warning] Invalid file link:(~/concepts/calls-and-meetings/call-notifications.md).

msteams-platform/_old/concepts/calls-and-meetings/debugging-local-testing-calling-meeting-bots.md

Line 10: [Warning] Invalid file link:(~/resources/general/debug.md).
Line 24: [Warning] Invalid file link:(~/concepts/calls-and-meetings/calls-meetings-bots-overview.md).

msteams-platform/_old/concepts/calls-and-meetings/real-time-media-concepts.md

Line 56: [Warning] Invalid file link:(~/concepts/calls-and-meetings/requirements-considerations-application-hosted-media-bots#real-time-media-bot-development-requires-cnet-and-windows-server).

msteams-platform/_old/concepts/calls-and-meetings/registering-calling-bot.md

Line 12: [Warning] Invalid file link:(~/concepts/calls-and-meetings/registering-calling-bot.md#add-microsoft-graph-permissions).
Line 32: [Warning] Invalid file link:(~/concepts/bots/bots-create.md).
Line 34: [Warning] Invalid file link:(~/concepts/bots/bots-create.md#bots-and-microsoft-azure).

msteams-platform/_old/concepts/concepts-overview.md

Line 17: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 18: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 19: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 20: [Warning] Invalid file link:(~/concepts/cards/cards).
Line 21: [Warning] Invalid file link:(~/concepts/authentication).
Line 22: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 23: [Warning] Invalid file link:(~/concepts/connectors/connectors).
Line 24: [Warning] Invalid file link:(~/concepts/bots/bots-notification-only).
Line 25: [Warning] Invalid file link:(~/concepts/messaging-extensions).
Line 26: [Warning] Invalid file link:(~/concepts/task-modules/task-modules-overview).
Line 27: [Warning] Invalid file link:(~/concepts/deep-links).

msteams-platform/_old/concepts/connectors/connectors-creating.md

Line 13: [Warning] Invalid file link:(~/concepts/apps/apps-package.md).
Line 53: [Warning] Invalid file link:(~/concepts/authentication/auth-flow-tab.md).
Line 76: [Warning] Invalid file link:(~/concepts/apps/apps-package.md#icons).
Line 134: [Warning] Invalid file link:(~/concepts/connectors/connectors-using.md#setting-up-a-custom-incoming-webhook).
Line 138: [Warning] Invalid file link:(~/concepts/apps/apps-upload.md#upload-your-package-into-a-team-or-conversation-using-the-store).

msteams-platform/_old/concepts/connectors/connectors-using.md

Line 33: [Warning] Invalid file link:(~/concepts/cards/cards.md).
Line 186: [Warning] Invalid file link:(~/concepts/apps/apps-package.md#icons).

msteams-platform/_old/concepts/connectors/connectors.md

Line 17: [Warning] Invalid file link:(~/concepts/connectors/connectors-using.md).
Line 18: [Warning] Invalid file link:(~/concepts/connectors/connectors-creating.md).

msteams-platform/_old/concepts/deep-links.md

Line 17: [Warning] Invalid file link:(~/concepts/tabs/tabs-context.md).
Line 19: [Warning] Invalid file link:(~/concepts/bots/bots-overview.md).
Line 19: [Warning] Invalid file link:(~/concepts/connectors/connectors.md).
Line 37: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md).
Line 48: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration.md).
Line 53: [Warning] Invalid file link:(~/concepts/tabs/tabs-context.md).

msteams-platform/_old/concepts/messaging-extensions/create-extensions.md

Line 221: [Warning] Invalid file link:(~/concepts/apps/apps-upload.md).
Line 239: [Warning] Invalid file link:(~/concepts/task-modules/task-modules-overview.md#the-taskinfo-object).
Line 290: [Warning] Invalid file link:(~/concepts/task-modules/task-modules-overview.md#the-taskinfo-object).
Line 317: [Warning] Invalid file link:(~/concepts/messaging-extensions/search-extensions.md#authentication).
Line 371: [Warning] Invalid file link:(~/concepts/cards/cards.md#adaptive-cards).

msteams-platform/_old/concepts/messaging-extensions/messaging-extensions-common.md

Line 3: [Warning] Invalid file link:(~/get-started/code.md#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 3: [Warning] Invalid file link:(~/concepts/cards/cards.md).
Line 3: [Warning] Invalid file link:(~/get-started/code.md#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 3: [Warning] Invalid file link:(~/concepts/cards/cards.md).
Line 3: [Warning] Invalid file link:(~/get-started/code.md#microsoft-teams-extensions-for-the-bot-builder-sdk).
Line 3: [Warning] Invalid file link:(~/concepts/cards/cards.md).
Line 9: [Warning] Invalid file link:(~/concepts/bots/bots-create.md).
Line 9: [Warning] Invalid file link:(~/concepts/bots/bots-create.md).
Line 9: [Warning] Invalid file link:(~/concepts/bots/bots-create.md).
Line 15: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md#composeextensions).
Line 15: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md#composeextensions).
Line 15: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md#composeextensions).

msteams-platform/_old/concepts/messaging-extensions/messaging-extensions-overview.md

Line 27: [Warning] Invalid file link:(~/concepts/messaging-extensions/search-extensions.md).
Line 28: [Warning] Invalid file link:(~/concepts/messaging-extensions/create-extensions.md).

msteams-platform/_old/concepts/messaging-extensions/search-extensions.md

Line 81: [Warning] Invalid file link:(~/concepts/apps/apps-upload.md).
Line 142: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conversations.md#receiving-messages).
Line 251: [Warning] Invalid file link:(~/concepts/cards/cards-reference.md#thumbnail-card).
Line 252: [Warning] Invalid file link:(~/concepts/cards/cards-reference.md#hero-card).
Line 253: [Warning] Invalid file link:(~/concepts/cards/cards-reference.md#office-365-connector-card).
Line 254: [Warning] Invalid file link:(~/concepts/cards/cards-reference.md#adaptive-card).
Line 256: [Warning] Invalid file link:(~/concepts/cards/cards.md).
Line 258: [Warning] Invalid file link:(~/concepts/cards-actions.md).
Line 260: [Warning] Invalid file link:(~/concepts/cards/cards-reference.md#office-365-connector-card).
Line 485: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md#validdomains).

msteams-platform/_old/concepts/outgoingwebhook.md

Line 265: [Warning] Invalid file link:(~/concepts/bots/bot-conversations/bots-conv-proactive.md).

msteams-platform/_old/concepts/tabs/cross-domain.md

Line 23: [Warning] Invalid file link:(~/resources/schema/manifest-schema#validdomains).
Line 23: [Warning] Invalid file link:(~/concepts/apps/apps-package).

msteams-platform/_old/concepts/tabs/tabs-configurable.md

Line 28: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 28: [Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove).
Line 29: [Warning] Invalid file link:(~/concepts/tabs/tabs-content).
Line 29: [Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove#removing-a-tab).
Line 31: [Warning] Invalid file link:(~/concepts/deep-links).

msteams-platform/_old/concepts/tabs/tabs-configuration.md

Line 10: [Warning] Invalid file link:(~/concepts/apps/apps-package.md).
Line 17: [Warning] Invalid file link:(~/resources/design/framework/tabs.md).
Line 77: [Warning] Invalid file link:(~/resources/general/requirements.md).
Line 85: [Warning] Invalid file link:(~/concepts/tabs/tabs-context.md).
Line 85: [Warning] Invalid file link:(~/concepts/authentication/authentication.md).
Line 93: [Warning] Invalid file link:(~/concepts/tabs/tabs-content.md).
Line 97: [Warning] Invalid file link:(~/concepts/deep-links.md).
Line 98: [Warning] Invalid file link:(~/concepts/tabs/tabs-content.md).
Line 98: [Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove.md).
Line 101: [Warning] Invalid file link:(~/concepts/tabs/cross-domain.md).
Line 101: [Warning] Invalid file link:(~/resources/schema/manifest-schema.md).
Line 105: [Warning] Invalid file link:(~/concepts/tabs/tabs-update-remove.md#removing-a-tab).

msteams-platform/_old/concepts/tabs/tabs-content.md

Line 9: [Warning] Invalid file link:(~/concepts/tabs/tabs-configuration).
Line 11: [Warning] Invalid file link:(~/concepts/tabs/tabs-context).
Line 11: [Warning] Invalid file link:(~/get-started/design#designing-a-great-tab).
Line 14: [Warning] Invalid file link:(~/samples/code-samples).
Line 20: [Warning] Invalid file link:(~/resources/general/requirements).
Line 26: [Warning] Invalid file link:(~/concepts/deep-links).
Line 30: [Warning] Invalid file link:(~/samples/code-samples).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Adding additional dictionaries to snap client through dialog fails

My Setup

Operating System: Ubuntu 19.10
App Version: 2.17.9
Installation type: snap

[ x ] I have tested with the latest version
[ x ] I can simulate the issue easily

Description

When trying to add additional languages using the "Browse for language..." dialog, the following error is returned:
Error copying dictionary file: Error invoking remote method 'spell-checking/install-dictionaries': [object Object

Perusing through dmesg logs, I found this seemingly related message:
[lun mar 30 19:05:25 2020] audit: type=1400 audit(1585588096.824:281): apparmor="DENIED" operation="open" profile="snap.rocketchat-desktop.rocketchat-desktop" name="/run/mount/utab" pid=20716 comm="rocketchat-desk" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


attackHook cant use fuctions based off of attacker

function attackHook(a,v){
if(Entity.getMobSkin(a)=="mob/dinos/trex_wild.png"){
clientMessage("The Function Is called");
Entity.setHealth(v, Entity.getHealth(v) - 10);
}
}
Im not even getting the client messgae

That is because attackHook is designed for only when the player attacks, not when a mob attacks.  (or at least I'm very sure that is the case)

Ok thank you i figured it out. How do i clod-se issue?

nvm


Block Clarification

It would be beneficial to have on the documentation if "Actively block the email or file sharing from taking place" being enabled in the DLP policy means that encrypted emails or files would also be blocked. If so, how is Microsoft seeing the encrypted contents?

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

ID: ce36344d-67bf-68cb-5004-9ac6f27ebf51
Version Independent ID: 89a7d7e7-c643-eb06-d844-b97b80633b68
Content: Create, test, and tune a DLP policy - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/create-test-tune-dlp-policy.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

HI @FrankMcGovern  Thanks for your question. Microsoft DLP will search the unencrypted meta data of the items, but not the encrypted contents.  See: https://docs.microsoft.com/en-us/microsoft-365/compliance/encryption-sensitivity-labels?view=o365-worldwide#considerations-for-encrypted-content
Thanks
Chris


How to configure ssl pinning in this module

Enable ssl pinning option globally in this project

how can we configure ssl pinning in this project any one done that with this library


Add "n through n" (for-each loop)

Looking at the tutorial, this:
for each y in 1 to 5 do
  display(y)
end

Doesn't display 5. (1 2 3 4)
I propose another expression:
for each y in 1 through 5 do
  display(y)
end

Which displays 1 2 3 4 5.
Alternatively, 1 up to 5?
Through definition regarding this:

During the whole of a period of time until the end of it.

I made it not include the upper bound because when you work with arrays, the length of an array is always one more than the index of the last element, although if you can iterate directly over the items of an array using for each, it might not matter.
I wouldn't want to change the range syntax to 1 up to 5 because you can include a by clause to make it 5 to 0 by -1, which wouldn't make sense with 5 up to 0 by -1.
Speaking of which, I just realized that the code generated for for each loops that iterate backwards is broken! D:

Sure! Having the through syntax there couldn't hurt, though, could it? :stuck_out_tongue_winking_eye:

I'll think about it, but first I need to make it work! :P

For future reference, @nanalan did this.


Add scheme/authority prefix

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/5813/
Test FAILed.

alluxio.job.migrate.MigrateIntegrationTest.migrateDirectory is flaky

alluxio-bot, merge this please


delete obj.prop; notifyPath("obj.prop") doesn't notify

Description
delete this.object.property;
// The following line doesn't notify, even if object.property previously had a defined value.
this.notifyPath("object.property");

Steps to Reproduce
<link rel="import" href="../bower_components/polymer/polymer-element.html" />
<dom-module id="test-element">
	<template>
		object.property is [[object.property]]
	</template>
	<script>
		class TestElement extends Polymer.Element {
			static get is() { return "test-element"; }
			static get properties() {
				return {
					object: {
						type: Object,
						value: () => { return { property: 1 }; },
					}
				};
			}
			ready() {
				super.ready();
				this.set("object.property", 2);

				delete this.object.property;
				this.notifyPath("object.property");
			}
		};
		customElements.define(TestElement.is, TestElement);
	</script>
</dom-module>

...

Expected Results
The text "object.property is" is shown.
Actual Results
The text "object.property is 2" is shown.
Browsers Affected

[x] Chrome
[x] Firefox

Versions

Polymer: v2.0.1
webcomponents: v1.0.1

this.set("object.property", undefined); doesn't do anything either.

The issue here is that object path values are not stored (other than during "one turn" of data propagation). Therefore any "set" or "notify" is seen a change because it's dirty checked against no value; however, a change from undefined to undefined is not considered a change.The rules around this are documented here but they are complex and we're open to improving this. We'll leave this issue open for tracking improvements to the current behavior.
Currently, we recommend that you do this.set("object.property", null); where possible. Another option is to override _shouldPropertyChange and handle this case explicitly.


Humongous amounts of data

Can this library handle HUMONGOUS rows of data in a memory-reasonable manner?

@power-f-GOD

https://github.com/adazzle/react-data-grid/issues/1846


Orderbook pin mode: Move with mid OR pin to price

The current implementation of the Orderbook works out a sensible place to centre the order book when it first loads (based mid, with some rules to handle auctions etc). It then stays pinned to that price. if the mid price moves suddenly out of view, the user will not see it.
This ticket to enhance the behaviour so that the view will stayed pinned to the mid price when ever it updates. Unless the user has manually scrolled the order book, if this has happened then the book stays pinned to that price.
A button should appear in "pinned to price mode" that allows the user to re-pin the view to the mid.

Closing as completed as part of:

https://github.com/vegaprotocol/frontend-monorepo/pull/312


Fixed broadcast receiver leaking when FlutterNativeView is destroyed.

:sparkles: Bug Fix
:arrow_heading_down: Currently, when the FlutterNativeView is destroyed and there is a registration to the LocationManagerMODE_CHANGED_ACTION broadcast receiver, then the broadcast receiver is leaked (a warning is printed as well to the logs by Android system)
:new: What is the new behavior (if this is a feature change)?
A PluginRegistry.ViewDestroyListener is implemented and registered. If the FlutterNativeView is destroyed, then the broadcast receiver is unregistered.
:boom: Does this PR introduce a breaking change?
No.
:bug: Recommendations for testing
This is Android only change. Try situations where the FlutterNativeView is destroyed and a listener attached to the serviceStatus stream. This is my first Pull request ever, so I would advise extra caution.
:memo: Links to relevant issues/docs
Did not create an issue, but should have done.
:thinking: Checklist before submitting

[x ] All projects build
[ x] Follows style guide lines (code style guide)
[ x] Relevant documentation was updated
[ -] Rebased onto current develop

I'm going to close this myself, because in fact my issue still persists and the IntentReceiver is leaked. Im using the plugin in a background isolate (aka a background FlutterNativeView) and there the broadcast receiver is leaked despite me calling FlutterNativeView.destroy() in Service.onDestroy().


Fake PR for ICLA: please ignore it.

Used for fake PR to check on the ICLA

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9581/
Test PASSed.

@luoli523 Could you close this PR after you are done with it?


feat: custom rpc calls settings (responsive)

RPC Call settings for different screen sizes
These settings allow your app to manage which RPC calls are made depending on whether it's being used on a large screen, like a desktop, or a small screen, like a smartphone.
  <RainbowKitProvider
    responsiveRpcSettings={{
      balance: {
        largeScreen: true,
        smallScreen: false,
      },
      ensName: {
        largeScreen: true,
        smallScreen: false,
      },
      ensAvatar: {
        largeScreen: true,
        smallScreen: false,
      },
      transactions: {
        largeScreen: true,
        smallScreen: false,
      },
    }}
  >
    {/* Your App */}
  </RainbowKitProvider>;

@DanielSinclair Is it worth mentioning in the docs that if user disables ensName, but enables ensAvatar they won't get the ens avatar image. Because in order to get ensAvatar wagmi requires the ensName.

Closing this for now since this will be a whole separate feature. Will simplify this in another PR.


How much would (stable) specialization help?

See https://github.com/Ixrec/rust-orphan-rules/issues/1 for more history, but the basic links are:
Specialization RFC: https://github.com/rust-lang/rfcs/pull/1210
Most recent blog post on making specialization sound: http://aturon.github.io/2018/04/05/sound-specialization/
This issue is for gathering feedback on whether or not stabilizing specialization actually solves use cases that are forbidden by the orphan rules today (since the orphan and overlap rules are intertwined). Since specialization is implemented on nightly, it should be possible to test and verify that it really does help, even if you can't use it for real yet.

Play. With the current implementation of specialisation, I cannot write:
struct Wrap<X>(X);

impl<S, T: From<S>> From<Wrap<S>> for Wrap<T> {
    fn from(w: Wrap<S>) -> Self {
        Wrap(T::from(w.0))
    }
}

I suspect this is simply a case of lacking the commonly-referred to "lattice rules" (see here).

Play. With the current rules, I cannot write impl TryFrom<T> for MyStruct for a generic T.
use std::convert::TryFrom;
trait MyTrait {}
struct MyStruct;

impl<T> TryFrom<T> for MyStruct where T: MyTrait {
    type Error = ();
    fn try_from(t: T) -> Result<Self, Self::Error> {
        unimplemented!()
    }
}

Err hold on, that doesn't compile on nightly either. Ignore me.


Analyzes regarding Duplicate Reimbursements

Detecting duplicate Reimbursements using dhash.
The last commit has the notebook to detect duplicate Reimbursements. It uses hash and hamming distance.
The other files concerns future implementation as: CFMT block (Compact Fourier Mellin Transform) to be more precise during the detection.
It is related to issue: #32

Hi @silviodc, thanks for the contribuition!
What I did to test this PR:

Clone the project:

$ git clone git@github.com:datasciencebr/serenata-de-amor.git

Change to serenata's folder:

$ cd serenata-de-amor

The steps to run the project:

$ conda update conda
$ conda create --name serenata_de_amor python=3
$ source activate serenata_de_amor
$ ./setup

Change to @silviodc's branch:

$ git checkout -b silviodc-silvio-cardoso master
$ git pull https://github.com/silviodc/serenata-de-amor.git silvio-cardoso

Open the jupyter notebook from the project:

$ jupyter notebook

Access http://localhost:8888/notebooks/research/develop/2017-05-05-silvio-Detecting-duplicates.ipynb

I really liked your work on it, looks real impressive!
Is there something that you are aiming to do more?
There is only one thing that I'll ask you, and then for me we can merge it!

Is there something that you are aiming to do more?

No. I guess i finished with these analyses.


The .DS_Store file needs to be ignored in .gitignore file

The .DS_Store file needs to be ignored in .gitignore file

Implemented in https://github.com/fabric8-analytics/fabric8-analytics-github-events-monitor/pull/25


Packaged google-api-php-client-services is deprecated

You include the google-api-php-client-services in the zip file, at \vendor\google\apiclient-services
The included version, uses the v2 of the AndroidPublisher API, as you can see in \vendor\google\apiclient-services\src\Google\Service\AndroidPublisher. This version has been deprecated, and will stop working on Dec 1 2019. Please update it to the latest version of the google-api-php-client-services library, which uses V3.

Version 2.4.0 and its archives provide v3 of the Android Publisher API.

It seems that we are both rights, as you only updated it in the regular php version, but in the php54 version you still have the old one.
https://github.com/googleapis/google-api-php-client/releases/download/v2.4.0/google-api-php-client-2.4.0.zip has V3
but...
https://github.com/googleapis/google-api-php-client/releases/download/v2.4.0/google-api-php-client-2.4.0_PHP54.zip has V2

Ah, you're 100% correct, I apologize. We'll figure out how to address this.

@lionscribe I've updated the archive attached to the latest release. Let me know if you have further issues.

@jdpedrie
google/apiclient": "^2.0",
I used to version, Do I need to update ?

@hto this issue only applies to the packaged downloadable archives found on the releases page. If you are installing via composer, you are fine.

We will make sure to package with the newest version of apiclient-services for all future releases.


Upgrade for-own dependency

This bump was just cutting the 0.1.5 version as 1.0.0 so this should be fine as a patch bump

Thanks!


Fix typo causing bad rendering (extra backtick)

Before:

After:

Good catch! Thanks @krassowski 🚀


ZXSensor Driver Sample

Not to be merged until: https://github.com/androidthings/contrib-drivers/pull/64 is merged (and released). This code won't compile until contrib drivers:#64 is released
Shows use of the ZXSensor contrib driver.
The example can be changed to sample UART or I2C.
Fritzing diagrams have been added for RPI.

closed due to another driver being written before this one


Quick review of queue-interop with some comments

Hi @makasim
I viewed queue-interop a few months ago but never had time to properly give some feedback when you started the project, sorry.
Having worked on PSR-11, I can give you a bit of advices if you ever want to push this on the PHP-FIG for a PSR. So here we go:
PHP 5 vs PHP 7:
I saw you discussed the issue here (#2). You decided to go for PHP 5 support a few month ago, but the tide has turned since then. Then newly passed PSR-15 is PHP 7+ only and upcoming PSR will be PHP 7+. So you should definitely target PHP 7 now.
Naming:
The interfaces are named PsrXxx. For instance PsrMessage. "Psr" does not add any value. On the other hand, you like the Interface suffix. I know many people feel it's wrong to have an Interface suffix (I'm part of those), but there has been a poll on the PHP-FIG mailing list 2 years ago and it was decided to go with the suffix.
So you should rename your interfaces this way:

PsrMessage => MessageInterface

Immutability:
PSR-7 objects (RequestInterface and ResponseInterface) are immutable. This is a very nice property to have as it prevents a number of side-effect bugs. It could be useful to have that in Queue-interop also (so you could drop all the setters from Message and replace those with withXxx methods).
Scope:
This is a big one. I think your interfaces have way too many methods. You want to cover all the existing features of all queuing systems. Maybe you should rather target what all systems have in common (i.e. send and consume) rather than putting all possible features of all systems in your interface.
For instance:
PsrProducer::setDeliveryDelay seems highly suspicious to me. First of all, the "delivery delay" notion could belong to a message rather than to a producer. It can be nice for producers to have default values, but this is an implementation detail, it has nothing to do in an interface. Then, an interface with setters is usually a code smell (if you want to know why, see https://ocramius.github.io/extremely-defensive-php/)
I really don't have much time to look in depth at queue-interop, but if you can get some people interested on the PHP-FIG mailing list (I know, it's hard), I'm sure you could get a ton of feedback that would probably change quite radically the structure of your interfaces. I started this way with container-interop, and it's really a great learning opportunity when you have all those skilled people looking at your code. So give it another try and try to gather some more feeedback, it's worth it!

@moufmouf  Don't have time to answer though I surely do.
Thanks for the feedback

[x] PHP 5 vs PHP 7 - https://github.com/queue-interop/queue-interop/pull/13
[ ] Naming - https://github.com/queue-interop/queue-interop/pull/14
[ ] Immutability
[ ] Scope

PsrProducer::setDeliveryDelay seems highly suspicious to me.

We followed JMS specification here. It is a standard in Java world.
It looked strange to me too, but having worked with that for some time I admit there is a logic behind that design.

I really don't have much time to look in depth at queue-interop, but if you can get some people interested on the PHP-FIG mailing list (I know, it's hard)

Tried to mail on their mailing list, reach representatives and so on, without luck.
https://groups.google.com/forum/?fromgroups#!searchin/php-fig/queue|sort:date/php-fig/CcFN7zr90Wo/trM1Ii9KBAAJ


2 energy databus hosting failures

1:
Hallo beisammen,
https://moss.tools.dbpedia.org/annotate
reagiert mit
There was an exception while trying to navigate to 'annotate' with the exception message 'HTTP 502 error making the query: Bad Gateway'
Carsten
2:
Hallo beisammen,
https://energy.databus.dbpedia.org/app/publish-wizard  führt zu „Sorry can’t find that“
Carsten

OEO Class not found in OEM metadata. Maybe it is something small. VOID finds it.

We need to migrate the energy databus asap and update to the lastest version. That should resolve the second issue.

Hi, issue 1 is already resolved since the mods sparql endpoint was restartet.
@kurzum Its not clear what the problem with this class is, if its nowhere annotated nothing gets found. Are you sure its in the actual metadata somewhere? Can you pinpoint the metadata/databus identifier it was used in?
here an example of a working query:

@yum-yab actually this could be a good way to test future versions of MOSS. Could you write a query that lists all classes that should be successfull in retrieving sth via the OEP Metadata search?
Limit 10 should be enough.

This is not strictly a 2.1.0 task, should this be moved to migration?


fix fn check if it is a generator

fixes #57
isinstance(config["handler"], types.GeneratorType) doesn't work as expected in this case because it should be run against the job result. using inspect is the proper way to handle this after the previous refactor was applied

There is also another bug in the code where the streaming callback url is not correct and simply sending to the completed callback

Partial fix in main, please rebase the PR.

Functionality in main, thank you for the PR!


API doc issue:build

Thank you for taking the time to file an issue!
This tracker is for issues related to:

Analyzer
Common Front End (CFE) and kernel
Dart core libraries ("dart:async", "dart:io", etc.)
Dart VM
dart2js
dartfix
dev_compiler

Some other pieces of the Dart ecosystem are maintained elsewhere. Please
file issues in their repository:

Dart language: https://github.com/dart-lang/language
Dart website: https://github.com/dart-lang/site-www
Flutter: https://github.com/flutter/flutter
Linter: https://github.com/dart-lang/linter
dartfmt: https://github.com/dart-lang/dart_style

If you aren't sure, file the issue here and we'll find the right home for it.
In your issue, please include:

Dart SDK Version (dart --version)
Whether you are using Windows, MacOSX, or Linux (if applicable)
Whether you are using Chrome, Safari, Firefox, Edge (if applicable)

Missing some or all of the above might make the issue take longer or be
impossible to act on.
If you simply have a question, consider starting with Stack Overflow:
https://stackoverflow.com/questions/tagged/dart
For a real-time response, consider our Gitter channel:
https://gitter.im/dart-lang/sdk

@mrvicfeng could you please elaborate on the issue, it is unclear from the description above what kind of API doc issue you are running into.

Closing this due to lack of info.  Please create a new one with the info requested in the original message.