extlinux.conf is not found

Hi again!
Sorry for bothering you!
I'm trying to build a custom root filesystem based on you guide: https://codepyre.com/2019/08/building-custom-root-filesystems/
I'm building for Xavier NX production module (not -dev) and Jetpack 4.4.1. I have followed you guide with the only change being that I run
make image-32.4.4-nx-dev-jetpack-4.4.1
Instead of
make image-32.2-nano-dev-jetpack-4.2.1
But when I try to flash the device it exits with the following error:
/Linux_for_Tegra/rootfs/boot/extlinux/extlinux.conf is not found, exiting...
Full log:

./flash/flash.sh<PHONE_NUMBER>69.dkr.ecr.eu-north-1.amazonaws.com/l4t:32.4.4-nx-jetpack-4.4.1-image
docker run --rm -it --privileged -v /dev/bus/usb:/dev/bus/usb<PHONE_NUMBER>69.dkr.ecr.eu-north-1.amazonaws.com/l4t:32.4.4-nx-jetpack-4.4.1-image
Using rootfs directory of: /Linux_for_Tegra/rootfs
/Linux_for_Tegra/nv_tegra/nv-apply-debs.sh
Root file system directory is /Linux_for_Tegra/rootfs
Copying public debian packages to rootfs
Start L4T BSP package installation
QEMU binary is not available, looking for QEMU from host system
Found /usr/bin/qemu-aarch64-static
Installing QEMU binary in rootfs
/Linux_for_Tegra/rootfs /Linux_for_Tegra
Installing BSP Debian packages in /Linux_for_Tegra/rootfs
Selecting previously unselected package nvidia-l4t-core.
(Reading database ... 11581 files and directories currently installed.)
Preparing to unpack .../nvidia-l4t-core_32.4.4-20201016123640_arm64.deb ...
Pre-installing... skip compatibility checking.
Unpacking nvidia-l4t-core (32.4.4-20201016123640) ...
dpkg: dependency problems prevent configuration of nvidia-l4t-core:
 nvidia-l4t-core depends on libegl1; however:
  Package libegl1 is not installed.

dpkg: error processing package nvidia-l4t-core (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 nvidia-l4t-core
sudo ./flash.sh  jetson-xavier-nx-devkit-emmc mmcblk0p1
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 4.4
###############################################################################
# Target Board Information:
# Name: jetson-xavier-nx-devkit-emmc, Board Family: t186ref, SoC: Tegra 194,
# OpMode: production, Boot Authentication: NS,
###############################################################################
copying soft_fuses(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)... done.
./tegraflash.py --chip 0x19 --applet "/Linux_for_Tegra/bootloader/mb1_t194_prod.bin" --skipuid --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg --bins "mb2_applet nvtboot_applet_t194.bin" --cmd "dump eeprom boardinfo cvm.bin;reboot recovery"
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[   0.0015 ] Generating RCM messages
[   0.0022 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader /Linux_for_Tegra/bootloader/mb1_t194_prod.bin zerosbk
[   0.0028 ] Header already present for /Linux_for_Tegra/bootloader/mb1_t194_prod.bin
[   0.0050 ]
[   0.0055 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0061 ] Assuming zero filled SBK key
[   0.0062 ]
[   0.0068 ] tegrasign_v2 --key None --file /Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin --offset 2960 --length 1136 --pubkeyhash pub_key.key
[   0.0074 ] Assuming zero filled SBK key
[   0.0077 ]
[   0.0082 ] tegrahost_v2 --chip 0x19 0 --updatesigheader /Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin /Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.hash zerosbk
[   0.0107 ]
[   0.0114 ] tegrabct_v2 --chip 0x19 0 --sfuse tegra194-mb1-soft-fuses-l4t.cfg.pdf sfuse.bin
[   0.0120 ]
[   0.0126 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x19 0 --sfuses sfuse.bin --download rcm /Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin 0 0
[   0.0132 ] RCM 0 is saved as rcm_0.rcm
[   0.0152 ] RCM 1 is saved as rcm_1.rcm
[   0.0152 ] RCM 2 is saved as rcm_2.rcm
[   0.0152 ] List of rcm files are saved in rcm_list.xml
[   0.0152 ]
[   0.0153 ] Signing RCM messages
[   0.0159 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key --getmontgomeryvalues montgomery.bin
[   0.0165 ] Assuming zero filled SBK key
[   0.0169 ]
[   0.0169 ] Copying signature to RCM mesages
[   0.0175 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
[   0.0184 ]
[   0.0184 ] Boot Rom communication
[   0.0191 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml --skipuid
[   0.0196 ] RCM version 0X190001
[   0.1279 ] Boot Rom communication completed
[   1.1446 ]
[   2.1488 ] tegrarcm_v2 --isapplet
[   2.1515 ] Applet version 01.00.0000
[   2.3898 ]
[   2.3906 ] tegrarcm_v2 --ismb2
[   2.6535 ]
[   2.6543 ] tegrahost_v2 --chip 0x19 --align nvtboot_applet_t194.bin
[   2.6582 ]
[   2.6588 ] tegrahost_v2 --chip 0x19 0 --magicid PLDT --appendsigheader nvtboot_applet_t194.bin zerosbk
[   2.6595 ] adding BCH for nvtboot_applet_t194.bin
[   2.6612 ]
[   2.6624 ] tegrasign_v2 --key None --list nvtboot_applet_t194_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   2.6630 ] Assuming zero filled SBK key
[   2.6633 ]
[   2.6647 ] tegrahost_v2 --chip 0x19 0 --updatesigheader nvtboot_applet_t194_sigheader.bin.encrypt nvtboot_applet_t194_sigheader.bin.hash zerosbk
[   2.6661 ]
[   2.6668 ] tegrarcm_v2 --download mb2 nvtboot_applet_t194_sigheader.bin.encrypt
[   2.6675 ] Applet version 01.00.0000
[   2.9105 ] Sending mb2
[   2.9106 ] [................................................] 100%
[   2.9235 ]
[   2.9267 ] tegrarcm_v2 --boot recovery
[   2.9295 ] Applet version 01.00.0000
[   3.1727 ]
[   4.1770 ] tegrarcm_v2 --isapplet
[   4.4175 ]
[   4.4183 ] tegrarcm_v2 --ismb2
[   4.4189 ] MB2 Applet version 01.00.0000
[   4.6785 ]
[   4.6793 ] tegrarcm_v2 --ismb2
[   4.6799 ] MB2 Applet version 01.00.0000
[   4.9418 ]
[   4.9425 ] Retrieving EEPROM data
[   4.9426 ] tegrarcm_v2 --oem platformdetails eeprom cvm /Linux_for_Tegra/bootloader/cvm.bin
[   4.9432 ] MB2 Applet version 01.00.0000
[   5.2034 ] Saved platform info in /Linux_for_Tegra/bootloader/cvm.bin
[   5.2387 ]
[   5.2389 ] Rebooting to recovery mode
[   5.2420 ] tegrarcm_v2 --ismb2
[   5.2447 ] MB2 Applet version 01.00.0000
[   5.4820 ]
[   5.4820 ] Rebooting to recovery mode
[   5.4842 ] tegrarcm_v2 --reboot recovery
[   5.4861 ] MB2 Applet version 01.00.0000
[   5.7498 ]
Board ID(3668) version(200) sku(0001) revision(G.0)
creating dummy /Linux_for_Tegra/bootloader/badpage.bin
1+0 records in
1+0 records out
4096 bytes (4.1 kB, 4.0 KiB) copied, 2.2321e-05 s, 184 MB/s
copying bctfile(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-memcfg-p3668-0001-a00.cfg)... done.
copying bctfile1(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-memcfg-sw-override.cfg)... done.
copying device_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-bct-device-qspi-p3668.cfg)... done.
copying misc_cold_boot_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-misc-l4t.cfg)... done.
copying misc_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-misc-flash.cfg)... done.
copying pinmux_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-pinmux-p3668-a01.cfg)... done.
copying gpioint_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg)... done.
copying pmic_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-pmic-p3668-0001-a00.cfg)... done.
copying pmc_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-padvoltage-p3668-a01.cfg)... done.
copying prod_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-prod-p3668-0001-a00.cfg)... done.
copying scr_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-scr-cbb-mini-p3668.cfg)... done.
copying scr_cold_boot_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-scr-cbb-mini-p3668.cfg)... done.
copying bootrom_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-reset-p3668-0001-a00.cfg)... done.
copying dev_params(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-br-bct-qspi.cfg)... done.
Existing bootloader(/Linux_for_Tegra/bootloader/nvtboot_cpu_t194.bin) reused.
copying initrd(/Linux_for_Tegra/bootloader/l4t_initrd.img)... done.
	populating kernel to rootfs... done.
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[   0.0029 ] Generating signature
[   0.0037 ] tegrasign_v2 --key  --getmode mode.txt
[   0.0043 ] Assuming zero filled SBK key
[   0.0046 ]
[   0.0047 ] header_magic: 5614
[   0.0054 ] tegrahost_v2 --chip 0x19 --align 1_Image
[   0.0061 ]
[   0.0067 ] tegrahost_v2 --chip 0x19 0 --magicid DATA --appendsigheader 1_Image zerosbk
[   0.0073 ] adding BCH for 1_Image
[   0.5283 ]
[   0.5293 ] tegrasign_v2 --key  --list 1_Image_sigheader_list.xml --pubkeyhash pub_key.key
[   0.5298 ] Assuming zero filled SBK key
[   0.5573 ]
[   0.5587 ] tegrahost_v2 --chip 0x19 0 --updatesigheader 1_Image_sigheader.encrypt 1_Image_sigheader.hash zerosbk
[   0.8494 ]
[   0.8711 ] Signed file: /Linux_for_Tegra/bootloader/Image_sigheader.encrypt
Generate header for Image_sigheader.encrypt
Generate 16-byte-size-aligned base file for Image_sigheader.encrypt
Remove temporary file
done.
	populating initrd to rootfs... done.
	populating /Linux_for_Tegra/kernel/dtb/tegra194-p3668-all-p3509-0000.dtb to rootfs... done.
Making Boot image... done.
Existing sosfile(/Linux_for_Tegra/bootloader/mb1_t194_prod.bin) reused.
Existing tegraboot(/Linux_for_Tegra/bootloader/nvtboot_t194.bin) reused.
Existing cpu_bootloader(/Linux_for_Tegra/bootloader/nvtboot_cpu_t194.bin) reused.
Existing mb2blfile(/Linux_for_Tegra/bootloader/nvtboot_recovery_t194.bin) reused.
Existing mtspreboot(/Linux_for_Tegra/bootloader/preboot_c10_prod_cr.bin) reused.
Existing mcepreboot(/Linux_for_Tegra/bootloader/mce_c10_prod_cr.bin) reused.
Existing mtsproper(/Linux_for_Tegra/bootloader/mts_c10_prod_cr.bin) reused.
Existing mb1file(/Linux_for_Tegra/bootloader/mb1_t194_prod.bin) reused.
Existing bpffile(/Linux_for_Tegra/bootloader/bpmp_t194.bin) reused.
copying bpfdtbfile(/Linux_for_Tegra/bootloader/t186ref/tegra194-a02-bpmp-p3668-a00.dtb)... done.
Existing scefile(/Linux_for_Tegra/bootloader/camera-rtcpu-sce.img) reused.
Existing camerafw(/Linux_for_Tegra/bootloader/camera-rtcpu-rce.img) reused.
Existing spefile(/Linux_for_Tegra/bootloader/spe_t194.bin) reused.
Existing drameccfile(/Linux_for_Tegra/bootloader/dram-ecc.bin) reused.
Existing badpagefile(/Linux_for_Tegra/bootloader/badpage.bin) reused.
Existing wb0boot(/Linux_for_Tegra/bootloader/warmboot_t194_prod.bin) reused.
Existing tosfile(/Linux_for_Tegra/bootloader/tos-trusty_t194.img) reused.
Existing eksfile(/Linux_for_Tegra/bootloader/eks.img) reused.
copying soft_fuses(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)... done.
copying dtbfile(/Linux_for_Tegra/kernel/dtb/tegra194-p3668-all-p3509-0000.dtb)... done.
Copying nv_boot_control.conf to rootfs
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[   0.0030 ] Generating signature
[   0.0039 ] tegrasign_v2 --key  --getmode mode.txt
[   0.0047 ] Assuming zero filled SBK key
[   0.0050 ]
[   0.0051 ] header_magic: d00dfeed
[   0.0060 ] tegrahost_v2 --chip 0x19 --align 1_tegra194-p3668-all-p3509-0000.dtb
[   0.0068 ]
[   0.0076 ] tegrahost_v2 --chip 0x19 0 --magicid DATA --appendsigheader 1_tegra194-p3668-all-p3509-0000.dtb zerosbk
[   0.0083 ] adding BCH for 1_tegra194-p3668-all-p3509-0000.dtb
[   0.0128 ]
[   0.0137 ] tegrasign_v2 --key  --list 1_tegra194-p3668-all-p3509-0000_sigheader.dtb_list.xml --pubkeyhash pub_key.key
[   0.0143 ] Assuming zero filled SBK key
[   0.0147 ]
[   0.0161 ] tegrahost_v2 --chip 0x19 0 --updatesigheader 1_tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt 1_tegra194-p3668-all-p3509-0000_sigheader.dtb.hash zerosbk
[   0.0188 ]
[   0.0192 ] Signed file: /Linux_for_Tegra/bootloader/tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt
Generate header for tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt
Generate 16-byte-size-aligned base file for tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt
Remove temporary file
done.
Making system.img...
/Linux_for_Tegra/rootfs/boot/extlinux/extlinux.conf is not found, exiting...

I've also seen the same error when trying to flash a custom rootfs on the nx-dev device using L4T 32.4.4 and Jetpack 4.4.1

Sorry, my github notifications aren't working and I just saw this.
I would guess they introduced an EGL dependency which needs to be installed in the root filesystem prior to flashing. NVIDIA does some dirty stuff in flashing where they install with dpkg instead of  apt and bypass the installation of dependent packages. If you follow the Building Root Filesystems With Desktop UI Support blog post do you have the same issue?
I have an NX dev kit, I'll try to repro, but I have to set up a new linux machine first, but I won't be able to test against the production NX module scripts.
@rippetoej Thanks for additional data point.
If you follow the basic flashing containers with the NVIDIA supplied rootfs and it flashes, then we're likely looking at an issue where they have packages which are required but they aren't telling us about (see #39).

Thanks for the suggestions, yeah it seems to be a problem with missing dependencies. I'll try to install those to the rootfs and get back!

The NVIDIA supplied rootfs did indeed flash fine, so I went through the debs they install in apply_binaries.sh and looked for any missing dependencies. I was missing a few, namely
libgstreamer-plugins-bad1.0-0
device-tree-compiler
libunwind8
I suspect one of those last two are to blame for the error we are seeing here. After installing the above depenceies using chroot in my rootfs and rebuilding the flashing container, this error went away.

When I last did it, I had to install python2 and python3 as well as the three you listed. I'm happy you got it working. @rippetoej .

@idavis thanks for pointing me in the right direction!

@oscarthorn - Any luck? It seems that @rippetoej has confirmed the missing dependencies.

@oscarthorn @idavis After flashing, I noticed the serial console on the dev kit USB port was not being created. Turns out the systemd service that starts this up was failing due to a few additional missing dependencies. I solved the issue by installing the following
net-tools (for ifconfig)
bridge-utils (for brctl)
I also installed network-manager, but I don't think that was needed. I'm not sure that this makes much difference to you based on whatever your carrier board is, but if you use the usb device port for serial console, this might affect you.

Thanks @rippetoej .  I've installed network-manager in the past which seems to fix wi-fi issues in the custom rootfs.

@oscarthorn I'm going to close this in a couple days as resolved unless you're still having issues.

@idavis So sorry for not getting back to you sooner!
Installing the dependencies seems to have helped some but it still does not work, it complains about a lot more missing dependencies now. For reference I installed
libgstreamer-plugins-bad1.0-0
device-tree-compiler
libunwind8
python
python3
Here is the new log:
docker run --rm -it --privileged -v /dev/bus/usb:/dev/bus/usb<PHONE_NUMBER>69.dkr.ecr.eu-north-1.amazonaws.com/l4t:32.4.4-nx-jetpack-4.4.1-image
Using rootfs directory of: /Linux_for_Tegra/rootfs
/Linux_for_Tegra/nv_tegra/nv-apply-debs.sh
Root file system directory is /Linux_for_Tegra/rootfs
Copying public debian packages to rootfs
Start L4T BSP package installation
QEMU binary is not available, looking for QEMU from host system
Found /usr/bin/qemu-aarch64-static
Installing QEMU binary in rootfs
/Linux_for_Tegra/rootfs /Linux_for_Tegra
Installing BSP Debian packages in /Linux_for_Tegra/rootfs
Selecting previously unselected package nvidia-l4t-core.
(Reading database ... 13744 files and directories currently installed.)
Preparing to unpack .../nvidia-l4t-core_32.4.4-20201016123640_arm64.deb ...
Pre-installing... skip compatibility checking.
Unpacking nvidia-l4t-core (32.4.4-20201016123640) ...
Setting up nvidia-l4t-core (32.4.4-20201016123640) ...
Selecting previously unselected package jetson-gpio-common.
(Reading database ... 13792 files and directories currently installed.)
Preparing to unpack .../jetson-gpio-common_2.0.11_arm64.deb ...
Unpacking jetson-gpio-common (2.0.11) ...
Selecting previously unselected package python-jetson-gpio.
Preparing to unpack .../python-jetson-gpio_2.0.11_arm64.deb ...
Unpacking python-jetson-gpio (2.0.11) ...
Selecting previously unselected package python3-jetson-gpio.
Preparing to unpack .../python3-jetson-gpio_2.0.11_arm64.deb ...
Unpacking python3-jetson-gpio (2.0.11) ...
Selecting previously unselected package nvidia-l4t-3d-core.
Preparing to unpack .../nvidia-l4t-3d-core_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-3d-core (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-apt-source.
Preparing to unpack .../nvidia-l4t-apt-source_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-apt-source (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-camera.
Preparing to unpack .../nvidia-l4t-camera_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-camera (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-configs.
Preparing to unpack .../nvidia-l4t-configs_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-configs (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-cuda.
Preparing to unpack .../nvidia-l4t-cuda_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-cuda (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-firmware.
Preparing to unpack .../nvidia-l4t-firmware_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-firmware (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-graphics-demos.
Preparing to unpack .../nvidia-l4t-graphics-demos_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-graphics-demos (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-gstreamer.
Preparing to unpack .../nvidia-l4t-gstreamer_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-gstreamer (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-init.
Preparing to unpack .../nvidia-l4t-init_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-init (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-initrd.
Preparing to unpack .../nvidia-l4t-initrd_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-initrd (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-jetson-io.
Preparing to unpack .../nvidia-l4t-jetson-io_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-jetson-io (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-multimedia-utils.
Preparing to unpack .../nvidia-l4t-multimedia-utils_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-multimedia-utils (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-multimedia.
Preparing to unpack .../nvidia-l4t-multimedia_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-multimedia (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-oem-config.
Preparing to unpack .../nvidia-l4t-oem-config_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-oem-config (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-tools.
Preparing to unpack .../nvidia-l4t-tools_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-tools (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-wayland.
Preparing to unpack .../nvidia-l4t-wayland_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-wayland (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-weston.
Preparing to unpack .../nvidia-l4t-weston_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-weston (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-x11.
Preparing to unpack .../nvidia-l4t-x11_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-x11 (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-xusb-firmware.
Preparing to unpack .../nvidia-l4t-xusb-firmware_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-xusb-firmware (32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-kernel-dtbs.
Preparing to unpack .../nvidia-l4t-kernel-dtbs_4.9.140-tegra-32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-kernel-dtbs (4.9.140-tegra-32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-kernel-headers.
Preparing to unpack .../nvidia-l4t-kernel-headers_4.9.140-tegra-32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-kernel-headers (4.9.140-tegra-32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-kernel.
Preparing to unpack .../nvidia-l4t-kernel_4.9.140-tegra-32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-kernel (4.9.140-tegra-32.4.4-20201016123640) ...
Selecting previously unselected package nvidia-l4t-bootloader.
Preparing to unpack .../nvidia-l4t-bootloader_32.4.4-20201016123640_arm64.deb ...
Unpacking nvidia-l4t-bootloader (32.4.4-20201016123640) ...
Setting up jetson-gpio-common (2.0.11) ...
Setting up python-jetson-gpio (2.0.11) ...
Setting up python3-jetson-gpio (2.0.11) ...
dpkg: dependency problems prevent configuration of nvidia-l4t-3d-core:
 nvidia-l4t-3d-core depends on libx11-6; however:
  Package libx11-6 is not installed.
 nvidia-l4t-3d-core depends on libxext6; however:
  Package libxext6 is not installed.

dpkg: error processing package nvidia-l4t-3d-core (--install):
 dependency problems - leaving unconfigured
Setting up nvidia-l4t-apt-source (32.4.4-20201016123640) ...
Pre-installing... skip changing source list.
dpkg: dependency problems prevent configuration of nvidia-l4t-camera:
 nvidia-l4t-camera depends on libgles2; however:
  Package libgles2 is not installed.
 nvidia-l4t-camera depends on nvidia-l4t-3d-core (= 32.4.4-20201016123640); however:
  Package nvidia-l4t-3d-core is not configured yet.

dpkg: error processing package nvidia-l4t-camera (--install):
 dependency problems - leaving unconfigured
Setting up nvidia-l4t-configs (32.4.4-20201016123640) ...
dpkg: dependency problems prevent configuration of nvidia-l4t-cuda:
 nvidia-l4t-cuda depends on nvidia-l4t-3d-core (= 32.4.4-20201016123640); however:
  Package nvidia-l4t-3d-core is not configured yet.

dpkg: error processing package nvidia-l4t-cuda (--install):
 dependency problems - leaving unconfigured
Setting up nvidia-l4t-firmware (32.4.4-20201016123640) ...
dpkg: dependency problems prevent configuration of nvidia-l4t-graphics-demos:
 nvidia-l4t-graphics-demos depends on libgles2; however:
  Package libgles2 is not installed.
 nvidia-l4t-graphics-demos depends on libwayland-egl1; however:
  Package libwayland-egl1 is not installed.
 nvidia-l4t-graphics-demos depends on libx11-6; however:
  Package libx11-6 is not installed.
 nvidia-l4t-graphics-demos depends on libxkbcommon0; however:
  Package libxkbcommon0 is not installed.
 nvidia-l4t-graphics-demos depends on nvidia-l4t-3d-core (= 32.4.4-20201016123640); however:
  Package nvidia-l4t-3d-core is not configured yet.

dpkg: error processing package nvidia-l4t-graphics-demos (--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-l4t-gstreamer:
 nvidia-l4t-gstreamer depends on libasound2; however:
  Package libasound2 is not installed.
 nvidia-l4t-gstreamer depends on libgles2; however:
  Package libgles2 is not installed.
 nvidia-l4t-gstreamer depends on libwayland-egl1; however:
  Package libwayland-egl1 is not installed.
 nvidia-l4t-gstreamer depends on libx11-6; however:
  Package libx11-6 is not installed.
 nvidia-l4t-gstreamer depends on libxext6; however:
  Package libxext6 is not installed.
 nvidia-l4t-gstreamer depends on nvidia-l4t-camera (>> 32.4-0); however:
  Package nvidia-l4t-camera is not configured yet.
 nvidia-l4t-gstreamer depends on nvidia-l4t-camera (<< 32.5-0); however:
  Package nvidia-l4t-camera is not configured yet.
 nvidia-l4t-gstreamer depends on nvidia-l4t-cuda (>> 32.4-0); however:
  Package nvidia-l4t-cuda is not configured yet.
 nvidia-l4t-gstreamer depends on nvidia-l4t-cuda (<< 32.5-0); however:
  Package nvidia-l4t-cuda is not configured yet.

dpkg: error processing package nvidia-l4t-gstreamer (--install):
 dependency problems - leaving unconfigured
Setting up nvidia-l4t-init (32.4.4-20201016123640) ...
dpkg: dependency problems prevent configuration of nvidia-l4t-multimedia-utils:
 nvidia-l4t-multimedia-utils depends on libcairo2; however:
  Package libcairo2 is not installed.
 nvidia-l4t-multimedia-utils depends on libdatrie1; however:
  Package libdatrie1 is not installed.
 nvidia-l4t-multimedia-utils depends on libfontconfig1; however:
  Package libfontconfig1 is not installed.
 nvidia-l4t-multimedia-utils depends on libgles2; however:
  Package libgles2 is not installed.
 nvidia-l4t-multimedia-utils depends on libharfbuzz0b; however:
  Package libharfbuzz0b is not installed.
 nvidia-l4t-multimedia-utils depends on libpangoft2-1.0-0; however:
  Package libpangoft2-1.0-0 is not installed.
 nvidia-l4t-multimedia-utils depends on libpixman-1-0; however:
  Package libpixman-1-0 is not installed.
 nvidia-l4t-multimedia-utils depends on libx11-6; however:
  Package libx11-6 is not installed.
 nvidia-l4t-multimedia-utils depends on libxext6; however:
  Package libxext6 is not installed.
 nvidia-l4t-multimedia-utils depends on libxrender1; however:
  Package libxrender1 is not installed.

dpkg: error processing package nvidia-l4t-multimedia-utils (--install):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of nvidia-l4t-multimedia:
 nvidia-l4t-multimedia depends on libasound2; however:
  Package libasound2 is not installed.
 nvidia-l4t-multimedia depends on libcairo2; however:
  Package libcairo2 is not installed.
 nvidia-l4t-multimedia depends on libdatrie1; however:
  Package libdatrie1 is not installed.
 nvidia-l4t-multimedia depends on libfontconfig1; however:
  Package libfontconfig1 is not installed.
 nvidia-l4t-multimedia depends on libgles2; however:
  Package libgles2 is not installed.
 nvidia-l4t-multimedia depends on libharfbuzz0b; however:
  Package libharfbuzz0b is not installed.
 nvidia-l4t-multimedia depends on libpango-1.0-0; however:
  Package libpango-1.0-0 is not installed.
 nvidia-l4t-multimedia depends on libpangocairo-1.0-0; however:
  Package libpangocairo-1.0-0 is not installed.
 nvidia-l4t-multimedia depends on libpangoft2-1.0-0; however:
  Package libpangoft2-1.0-0 is not installed.
 nvidia-l4t-multimedia depends on libpixman-1-0; however:
  Package libpixman-1-0 is not installed.
 nvidia-l4t-multimedia depends on libx11-6; however:
  Package libx11-6 is not installed.
 nvidia-l4t-multimedia depends on libxext6; however:
  Package libxext6 is not installed.
 nvidia-l4t-multimedia depends on libxrender1; however:
  Package libxrender1 is not installed.
 nvidia-l4t-multimedia depends on nvidia-l4t-3d-core (= 32.4.4-20201016123640); however:
  Package nvidia-l4t-3d-core is not configured yet.
 nvidia-l4t-multimedia depends on nvidia-l4t-cuda (= 32.4.4-20201016123640); however:
  Package nvidia-l4t-cuda is not configured yet.
 nvidia-l4t-multimedia depends on nvidia-l4t-multimedia-utils (= 32.4.4-20201016123640); however:
  Package nvidia-l4t-multimedia-utils is not configured yet.

dpkg: error processing package nvidia-l4t-multimedia (--install):
 dependency problems - leaving unconfigured
Setting up nvidia-l4t-oem-config (32.4.4-20201016123640) ...
Setting up nvidia-l4t-tools (32.4.4-20201016123640) ...
Setting up nvidia-l4t-wayland (32.4.4-20201016123640) ...
dpkg: dependency problems prevent configuration of nvidia-l4t-weston:
 nvidia-l4t-weston depends on libcairo2; however:
  Package libcairo2 is not installed.
 nvidia-l4t-weston depends on libevdev2; however:
  Package libevdev2 is not installed.
 nvidia-l4t-weston depends on libgles2; however:
  Package libgles2 is not installed.
 nvidia-l4t-weston depends on libinput10; however:
  Package libinput10 is not installed.
 nvidia-l4t-weston depends on libjpeg-turbo8; however:
  Package libjpeg-turbo8 is not installed.
 nvidia-l4t-weston depends on libpixman-1-0; however:
  Package libpixman-1-0 is not installed.
 nvidia-l4t-weston depends on libpng16-16; however:
  Package libpng16-16 is not installed.
 nvidia-l4t-weston depends on libwayland-cursor0; however:
  Package libwayland-cursor0 is not installed.
 nvidia-l4t-weston depends on libwayland-egl1; however:
  Package libwayland-egl1 is not installed.
 nvidia-l4t-weston depends on libxkbcommon0; however:
  Package libxkbcommon0 is not installed.

dpkg: error processing package nvidia-l4t-weston (--install):
 dependency problems - leaving unconfigured
Setting up nvidia-l4t-x11 (32.4.4-20201016123640) ...
Setting up nvidia-l4t-xusb-firmware (32.4.4-20201016123640) ...
Pre-installing xusb firmware package, skip flashing
Setting up nvidia-l4t-kernel (4.9.140-tegra-32.4.4-20201016123640) ...
Setting up nvidia-l4t-bootloader (32.4.4-20201016123640) ...
Pre-installing bootloader package, skip flashing
Setting up nvidia-l4t-initrd (32.4.4-20201016123640) ...
Setting up nvidia-l4t-jetson-io (32.4.4-20201016123640) ...
Setting up nvidia-l4t-kernel-dtbs (4.9.140-tegra-32.4.4-20201016123640) ...
Setting up nvidia-l4t-kernel-headers (4.9.140-tegra-32.4.4-20201016123640) ...
Unpacking kernel headers...
Processing triggers for nvidia-l4t-kernel (4.9.140-tegra-32.4.4-20201016123640) ...
Errors were encountered while processing:
 nvidia-l4t-3d-core
 nvidia-l4t-camera
 nvidia-l4t-cuda
 nvidia-l4t-graphics-demos
 nvidia-l4t-gstreamer
 nvidia-l4t-multimedia-utils
 nvidia-l4t-multimedia
 nvidia-l4t-weston
sudo ./flash.sh  jetson-xavier-nx-devkit-emmc mmcblk0p1
###############################################################################
# L4T BSP Information:
# R32 , REVISION: 4.4
###############################################################################
# Target Board Information:
# Name: jetson-xavier-nx-devkit-emmc, Board Family: t186ref, SoC: Tegra 194,
# OpMode: production, Boot Authentication: NS,
###############################################################################
copying soft_fuses(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)... done.
./tegraflash.py --chip 0x19 --applet "/Linux_for_Tegra/bootloader/mb1_t194_prod.bin" --skipuid --soft_fuses tegra194-mb1-soft-fuses-l4t.cfg --bins "mb2_applet nvtboot_applet_t194.bin" --cmd "dump eeprom boardinfo cvm.bin;reboot recovery"
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[   0.0016 ] Generating RCM messages
[   0.0024 ] tegrahost_v2 --chip 0x19 0 --magicid MB1B --appendsigheader /Linux_for_Tegra/bootloader/mb1_t194_prod.bin zerosbk
[   0.0029 ] Header already present for /Linux_for_Tegra/bootloader/mb1_t194_prod.bin
[   0.0052 ]
[   0.0059 ] tegrasign_v2 --key None --getmode mode.txt
[   0.0064 ] Assuming zero filled SBK key
[   0.0064 ]
[   0.0070 ] tegrasign_v2 --key None --file /Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin --offset 2960 --length 1136 --pubkeyhash pub_key.key
[   0.0076 ] Assuming zero filled SBK key
[   0.0079 ]
[   0.0085 ] tegrahost_v2 --chip 0x19 0 --updatesigheader /Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin /Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.hash zerosbk
[   0.0112 ]
[   0.0119 ] tegrabct_v2 --chip 0x19 0 --sfuse tegra194-mb1-soft-fuses-l4t.cfg.pdf sfuse.bin
[   0.0125 ]
[   0.0131 ] tegrarcm_v2 --listrcm rcm_list.xml --chip 0x19 0 --sfuses sfuse.bin --download rcm /Linux_for_Tegra/bootloader/mb1_t194_prod_sigheader.bin 0 0
[   0.0137 ] RCM 0 is saved as rcm_0.rcm
[   0.0157 ] RCM 1 is saved as rcm_1.rcm
[   0.0158 ] RCM 2 is saved as rcm_2.rcm
[   0.0158 ] List of rcm files are saved in rcm_list.xml
[   0.0158 ]
[   0.0158 ] Signing RCM messages
[   0.0163 ] tegrasign_v2 --key None --list rcm_list.xml --pubkeyhash pub_key.key --getmontgomeryvalues montgomery.bin
[   0.0169 ] Assuming zero filled SBK key
[   0.0174 ]
[   0.0174 ] Copying signature to RCM mesages
[   0.0180 ] tegrarcm_v2 --chip 0x19 0 --updatesig rcm_list_signed.xml
[   0.0189 ]
[   0.0189 ] Boot Rom communication
[   0.0194 ] tegrarcm_v2 --chip 0x19 0 --rcm rcm_list_signed.xml --skipuid
[   0.0200 ] RCM version 0X190001
[   0.1321 ] Boot Rom communication completed
[   1.1473 ]
[   2.1492 ] tegrarcm_v2 --isapplet
[   2.1499 ] Applet version 01.00.0000
[   2.3893 ]
[   2.3901 ] tegrarcm_v2 --ismb2
[   2.6455 ]
[   2.6466 ] tegrahost_v2 --chip 0x19 --align nvtboot_applet_t194.bin
[   2.6648 ]
[   2.6656 ] tegrahost_v2 --chip 0x19 0 --magicid PLDT --appendsigheader nvtboot_applet_t194.bin zerosbk
[   2.6662 ] adding BCH for nvtboot_applet_t194.bin
[   2.6680 ]
[   2.6688 ] tegrasign_v2 --key None --list nvtboot_applet_t194_sigheader.bin_list.xml --pubkeyhash pub_key.key
[   2.6695 ] Assuming zero filled SBK key
[   2.6698 ]
[   2.6711 ] tegrahost_v2 --chip 0x19 0 --updatesigheader nvtboot_applet_t194_sigheader.bin.encrypt nvtboot_applet_t194_sigheader.bin.hash zerosbk
[   2.6726 ]
[   2.6733 ] tegrarcm_v2 --download mb2 nvtboot_applet_t194_sigheader.bin.encrypt
[   2.6739 ] Applet version 01.00.0000
[   2.9093 ] Sending mb2
[   2.9094 ] [................................................] 100%
[   2.9229 ]
[   2.9238 ] tegrarcm_v2 --boot recovery
[   2.9245 ] Applet version 01.00.0000
[   3.1808 ]
[   4.1826 ] tegrarcm_v2 --isapplet
[   4.4261 ]
[   4.4270 ] tegrarcm_v2 --ismb2
[   4.4275 ] MB2 Applet version 01.00.0000
[   4.6815 ]
[   4.6823 ] tegrarcm_v2 --ismb2
[   4.6829 ] MB2 Applet version 01.00.0000
[   4.9418 ]
[   4.9426 ] Retrieving EEPROM data
[   4.9427 ] tegrarcm_v2 --oem platformdetails eeprom cvm /Linux_for_Tegra/bootloader/cvm.bin
[   4.9433 ] MB2 Applet version 01.00.0000
[   5.2035 ] Saved platform info in /Linux_for_Tegra/bootloader/cvm.bin
[   5.2382 ]
[   5.2382 ] Rebooting to recovery mode
[   5.2390 ] tegrarcm_v2 --ismb2
[   5.2395 ] MB2 Applet version 01.00.0000
[   5.4774 ]
[   5.4774 ] Rebooting to recovery mode
[   5.4783 ] tegrarcm_v2 --reboot recovery
[   5.4790 ] MB2 Applet version 01.00.0000
[   5.7404 ]
Board ID(3668) version(200) sku(0001) revision(G.0)
creating dummy /Linux_for_Tegra/bootloader/badpage.bin
1+0 records in
1+0 records out
4096 bytes (4.1 kB, 4.0 KiB) copied, 2.1821e-05 s, 188 MB/s
copying bctfile(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-memcfg-p3668-0001-a00.cfg)... done.
copying bctfile1(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-memcfg-sw-override.cfg)... done.
copying device_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-bct-device-qspi-p3668.cfg)... done.
copying misc_cold_boot_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-misc-l4t.cfg)... done.
copying misc_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-misc-flash.cfg)... done.
copying pinmux_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-pinmux-p3668-a01.cfg)... done.
copying gpioint_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-gpioint-p3668-0001-a00.cfg)... done.
copying pmic_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-pmic-p3668-0001-a00.cfg)... done.
copying pmc_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-padvoltage-p3668-a01.cfg)... done.
copying prod_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra19x-mb1-prod-p3668-0001-a00.cfg)... done.
copying scr_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-scr-cbb-mini-p3668.cfg)... done.
copying scr_cold_boot_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-scr-cbb-mini-p3668.cfg)... done.
copying bootrom_config(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-bct-reset-p3668-0001-a00.cfg)... done.
copying dev_params(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-br-bct-qspi.cfg)... done.
Existing bootloader(/Linux_for_Tegra/bootloader/nvtboot_cpu_t194.bin) reused.
copying initrd(/Linux_for_Tegra/bootloader/l4t_initrd.img)... done.
	populating kernel to rootfs... done.
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[   0.0017 ] Generating signature
[   0.0023 ] tegrasign_v2 --key  --getmode mode.txt
[   0.0028 ] Assuming zero filled SBK key
[   0.0030 ]
[   0.0031 ] header_magic: 5614
[   0.0037 ] tegrahost_v2 --chip 0x19 --align 1_Image
[   0.0042 ]
[   0.0047 ] tegrahost_v2 --chip 0x19 0 --magicid DATA --appendsigheader 1_Image zerosbk
[   0.0053 ] adding BCH for 1_Image
[   0.5302 ]
[   0.5311 ] tegrasign_v2 --key  --list 1_Image_sigheader_list.xml --pubkeyhash pub_key.key
[   0.5316 ] Assuming zero filled SBK key
[   0.5623 ]
[   0.5635 ] tegrahost_v2 --chip 0x19 0 --updatesigheader 1_Image_sigheader.encrypt 1_Image_sigheader.hash zerosbk
[   0.8394 ]
[   0.8610 ] Signed file: /Linux_for_Tegra/bootloader/Image_sigheader.encrypt
Generate header for Image_sigheader.encrypt
Generate 16-byte-size-aligned base file for Image_sigheader.encrypt
Remove temporary file
done.
	populating initrd to rootfs... done.
	populating /Linux_for_Tegra/kernel/dtb/tegra194-p3668-all-p3509-0000.dtb to rootfs... done.
Making Boot image... done.
Existing sosfile(/Linux_for_Tegra/bootloader/mb1_t194_prod.bin) reused.
Existing tegraboot(/Linux_for_Tegra/bootloader/nvtboot_t194.bin) reused.
Existing cpu_bootloader(/Linux_for_Tegra/bootloader/nvtboot_cpu_t194.bin) reused.
Existing mb2blfile(/Linux_for_Tegra/bootloader/nvtboot_recovery_t194.bin) reused.
Existing mtspreboot(/Linux_for_Tegra/bootloader/preboot_c10_prod_cr.bin) reused.
Existing mcepreboot(/Linux_for_Tegra/bootloader/mce_c10_prod_cr.bin) reused.
Existing mtsproper(/Linux_for_Tegra/bootloader/mts_c10_prod_cr.bin) reused.
Existing mb1file(/Linux_for_Tegra/bootloader/mb1_t194_prod.bin) reused.
Existing bpffile(/Linux_for_Tegra/bootloader/bpmp_t194.bin) reused.
copying bpfdtbfile(/Linux_for_Tegra/bootloader/t186ref/tegra194-a02-bpmp-p3668-a00.dtb)... done.
Existing scefile(/Linux_for_Tegra/bootloader/camera-rtcpu-sce.img) reused.
Existing camerafw(/Linux_for_Tegra/bootloader/camera-rtcpu-rce.img) reused.
Existing spefile(/Linux_for_Tegra/bootloader/spe_t194.bin) reused.
Existing drameccfile(/Linux_for_Tegra/bootloader/dram-ecc.bin) reused.
Existing badpagefile(/Linux_for_Tegra/bootloader/badpage.bin) reused.
Existing wb0boot(/Linux_for_Tegra/bootloader/warmboot_t194_prod.bin) reused.
Existing tosfile(/Linux_for_Tegra/bootloader/tos-trusty_t194.img) reused.
Existing eksfile(/Linux_for_Tegra/bootloader/eks.img) reused.
copying soft_fuses(/Linux_for_Tegra/bootloader/t186ref/BCT/tegra194-mb1-soft-fuses-l4t.cfg)... done.
copying dtbfile(/Linux_for_Tegra/kernel/dtb/tegra194-p3668-all-p3509-0000.dtb)... done.
Copying nv_boot_control.conf to rootfs
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands

[   0.0017 ] Generating signature
[   0.0023 ] tegrasign_v2 --key  --getmode mode.txt
[   0.0028 ] Assuming zero filled SBK key
[   0.0030 ]
[   0.0031 ] header_magic: d00dfeed
[   0.0037 ] tegrahost_v2 --chip 0x19 --align 1_tegra194-p3668-all-p3509-0000.dtb
[   0.0042 ]
[   0.0047 ] tegrahost_v2 --chip 0x19 0 --magicid DATA --appendsigheader 1_tegra194-p3668-all-p3509-0000.dtb zerosbk
[   0.0053 ] adding BCH for 1_tegra194-p3668-all-p3509-0000.dtb
[   0.0084 ]
[   0.0092 ] tegrasign_v2 --key  --list 1_tegra194-p3668-all-p3509-0000_sigheader.dtb_list.xml --pubkeyhash pub_key.key
[   0.0096 ] Assuming zero filled SBK key
[   0.0099 ]
[   0.0110 ] tegrahost_v2 --chip 0x19 0 --updatesigheader 1_tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt 1_tegra194-p3668-all-p3509-0000_sigheader.dtb.hash zerosbk
[   0.0148 ]
[   0.0150 ] Signed file: /Linux_for_Tegra/bootloader/tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt
Generate header for tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt
Generate 16-byte-size-aligned base file for tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt
Remove temporary file
done.
Making system.img...
/Linux_for_Tegra/rootfs/boot/extlinux/extlinux.conf is not found, exiting...

I figure I could try to install every depenecy listed in the error but I'm wondering if something else is going on?

By the way I'm using the Debootstrap method, does that matter? I'll try the image version tomorrow!

I see lots of package dependency errors in your log. Scan through that output and look for "Package XXX is not installed ", then install those packages in your custom rootfs. To help you get started, at the end of the configuration step, it says this
Errors were encountered while processing:
 nvidia-l4t-3d-core
 nvidia-l4t-camera
 nvidia-l4t-cuda
 nvidia-l4t-graphics-demos
 nvidia-l4t-gstreamer
 nvidia-l4t-multimedia-utils
 nvidia-l4t-multimedia
 nvidia-l4t-weston

These are the packages with missing dependencies.

Yeah, I'll try that tomorrow!

@oscarthorn Any news?

@oscarthorn  I'm going to close this in a couple days as resolved unless you're still having issues.


feat: colored jars with names

Resolves #435
I did the coloring and naming in one go, apologies for the large changeset.
In short:

Jar #0 is now Jar A, etc.
Short form is used in detail views
Long form (full flavor name) is used in main views
Colors added to wallet overview

We could definitely go nuts with the details, i.e. add color to the little jar icons where appropriate, etc. I decided to not go nuts in this PR, we can implement this later as a nice-to-have.
The goal of this PR is to get rid of 0/1/2/3/4 to not confuse noobs too much, and switch to A/B/C/D/E.
📸 Screenshots

👉 More screenshots below the fold 👇

📷🌚 More dark mode screenshots

📷🌝 More light mode screenshots

Oh, nice, using first-letter css is way smarter! Thanks! 😅


[Issue 173] Cluster update no longer expects config to be passed as an argument.

…lag and not as an argument, should now be consistent with all other config dependent commands.

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #173
Special notes for your reviewer:
Release note:

I saw this too late this morning and didn't follow up in time. I don't think this is fixed.
I just pulled from kraken cnct/master and ran
kraken cluster update --config $HOME/.kraken/<existing-cluster>.yaml --update-nodepools <bogusNodes>
and it still tries to pull from a default config.yaml.
Moreover, when I create a fake default config.yaml, it tries using that file with the above command (i.e. even if I'm pointing at another config file), as before.
I realize that the above command is not what we are supposed to use for update per the docs (the docs have you not use the --config flag) but it is confusing enough that it would be easy to do, and the least we can do is have it not result in actual clusters being updated.

@guineveresaenger can you please verify you are using master with the latest code changes. Also please use absolute path to the config file as you define above. If the problem persist please consider opening a new ticket. The behavior here is at the moment consistent with the rest of the tools, so if you dont believe they should behave that way we should definitely change it. It does affect everything else so should be changed with that in mind, with a new ticket of course.

@alejandroEsc
Apologies for my above comment. I was not using the latest built kraken binary.
It is now necessary to pass --config to update action as well.
However:

If --config fails to get passed, kraken will still attempt to use the default config. Example:

./kraken cluster update $HOME/.kraken/guinlog.yaml --update-nodepools someNode
config file path not given, using default config file location (/Users/guin/.kraken/config.yaml)```
- The docs should be updated to reflect the need for --config, because otherwise the use will definitely run into the above problem.

I created issues #184 (bug fix) and #185 (documentation) to address these problems.


[docs] Refine navigation setup

The Problem/Issue/Bug:
As demonstrated by the changes in #4293, the combined section and on-page sidebar navigation can get in the way of browsing a section or page—which is its sole purpose:

The problem isn’t just limited to suggested FAQ page revisions, though. The same imbalance is demonstrated on the Extending and Customizing Environments page:

How this PR Solves The Problem:
This PR makes a few changes to the theme configuration to balance things out and make the navigation more useful for browsing:

Separates the on-page table of contents from section navigation by disabling navigation.integrate. This makes it easier to focus on the flow of an entire section, or of a page, without confusing the two or overloading one side of the page—and with a negligible impact on line length.
Limits on-page table of contents to two levels (toc_depth: 2), which further emphasizes (and encourages!) thoughtful organization without overloading the table of contents.
Uses frontmatter to hide the table of contents on pages where it takes visual attention without offering any value.
Enables instant loading with navigation.instant, which seems to work well and speed up browsing—which translates to better user experience.
Enables navigation.tracking so the address bar updates with current anchors on scroll.
Slightly reorganizes the landing page’s sidebar to include a “Settling In” section meant for post-install adventures. (Currently, installation steps wander into configuration and community details, with an awkward vertical space.)

The result is cleaner, more balanced, and easier to navigate despite varying page organization and length:

Manual Testing Instructions:
https://ddev.readthedocs.io/en/stable/developers/testing-docs/#preview-changes
Automated Testing Overview:
n/a
Related Issue Link(s):
Part of this overall effort:

#4188

Release/Deployment notes:
n/a

I like it! I especially like the "Installing" and "Settling in" sectionals. It's possible though that "Settling in" is too jargony for non-English-first-language folks.

Good point! Maybe “Getting Started” would be more appropriate given that it’s the “Start!” page and we’ve just finished installing?

Make sure you look at this with a smaller screen, like phone. I find navigating the mkdocs-material menus on the phone complicated, but reading straight through is wonderful. I've taken to reading docs like this on phone just reading and using the "next" on the bottom. Anyway, the right-hand menu you've got on on the web browser is not available at all as far as I know on the phone.

This doesn’t change the mobile navigation UX from its current form, where the table of contents is (thoughtfully, I think) isolated to its own submenu:

Let me know when you're ready to pull.

Just updated “Settling In” to “Getting Started”—pull whenever you’d like!


Readme Twitter example

In Readme, the line
twt = Twitter(app_key="xxx", app_secret="xxx", oauth_token="xxx",
    oauth_token_secret="xxx")

shouldn't it be:
  twt = Twitter(api_key="xxx", api_secret="xxx", access_token="xxx", access_token_secret="xxx")
to match apis.py implementation?
class Twitter(API):
    def __init__(self, api_key, api_secret, access_token, access_token_secret):

As stated in the Readme the examples only apply to socialreaper version 0.3.0 on PyPI, which uses the old naming convention.
The examples will be updated when complete documentation is written

As stated in the Readme the examples only apply to socialreaper version 0.3.0 on PyPI, which uses the old naming convention.
The examples will be updated when complete documentation is written

@ScriptSmith Pipl Service.


Complete the introduction of Baidu Translate in README and change the endpoint to https

Is there any particular reason to use http? If not, I think we should use https.
I also added the description of the cost of Baidu Translate and LingoCloud Translate in the README.
Sorry for messing up the last PR.

Hi. Sorry I've been away for a while. Will look into this soon.


Add GitHub corner

The current corner is not transparent:

Can we switch to https://github.com/tholman/github-corners?


Corrected Timeout Documentation

Corrected the documentation of the Timeout property.
See: https://github.com/AsterNET/AsterNET/issues/61
I am not sure how I could change the default timeout value. It may be a part of the SendAction method that sends a 0 when it shouldn't.

Documentation change approved.


Basic implementation of Version Guard.

Version Guard is a command-line tool which is used in the Azure SDK pipelines to check whether a given name and version of a package is correct based on the names and versions of packages that have been released previously. The goal is to detect versioning errors in pipelines as early as possible.
For example if we have released<EMAIL_ADDRESS>then there is no point building the code to release it again, nor should we attempt to release -preview.5 or lower. However it would be acceptable to produce either<EMAIL_ADDRESS>or<EMAIL_ADDRESS>Version Guard answers the following simple question - is this given version number valid for release. If it is then the program returns a zero exit code, if not it returns a non-zero exit code.
(version-guard) implemented as a .NET Global Tool which can be installed on Windows, macOS and Linux using the following command:
dotnet tool install --global Microsoft.Azure.Sdk.Tools.VersionGuard --version 0.1.0-preview.1 --add-source https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk/nuget/v3/index.json

Once installed you can use the following command-line to check to see whether the version details you are passing on on the command-line:
$ version-guard --registry nuget --package-name Azure.Core --package-version 1.0.0-preview.6
ERROR: Package<EMAIL_ADDRESS>was already found on NuGet.org, consider updating the verison number.

/azp run tools - version-guard - ci

/azp run tools - version-guard - ci

/azp run tools - version-guard - ci


[Feature Request] Make Temporalio.Testing to a seperate nuget out of Temporalio

Is your feature request related to a problem? Please describe.
Temporalio.Testing is currently a part of the Temporalio package. I think it is better to decouple so we don't distribute test code to production

Describe the solution you'd like

make Temporalio.Testing into a separate nuget
make Temporalio not reference Temporalio.Testing

This is more "test helpers" but they are harmless if not used (i.e. don't bring in extra dependencies). Technically this code is totally valid in production if people want to use it there, we make no recommendations on that. If you're concerned about certain code using certain packages, you may be able to use a linter. We primarily only keep things in separate versioned packages if they cause dependency issues.


Interest in migrating to v2 of Tauri

I tried migrating the project to v2 of Tauri today which was surprisingly easy.
Most of the work involved changing how state management and permissions work, as well as changing imports for the IPC
Now my question would be, would you be interested in upgrading? If so, I can spin up a PR or you can take over the changes.
Changes needed for a quick migration can be found here

@curtisy1 Thanks for taking this up. I am very much interested in migrating to v2 but did not have the bandwidth to do so and I was also worried that it may introduce some breaking changes that could take too much time to fix.
I can raise the PR and I will go through it and will do some thorough testing to make sure everything is working.

I created a PR at #37 that you can have a look at


Temporarily revert "Add exclude-tautologies option to reason commands."

This reverts commit 709b88ee84bd7896f258509b3f6449adcd41d4f6.
Need to wait until pipeline upgrades ODK version.

cc @kltm @dougli1sqrd

@balhoff This matches what I'd expect for our old ODK.
Noting:
https://github.com/geneontology/pipeline/issues/135
https://github.com/geneontology/pipeline/issues/136


Update readme

This PR restructures the readme.

small fix: AppVeyor badget now shows status of the master branch instead of the latest push across all branches
removed Sauerbraten features section: we are not Sauerbraten and have refered to our wiki for our own features all the way along, we also certainly didn't convice anyone to try out Inexor with that
renamed "First steps" (What first steps for what purpose?? Not clear at all) to "Join us" and moved a few other information into this section
fixing URLs

I will merge this Sunday without vetos.

It has the same base and I cherry-picked but the hash changed and now it is not counted as merged?
Okay..

Merged with 1d69190905b3e0099da6533a708dae99be0ff56a


Fix some issues with the jubeat1 release

tl;dr:

NVRAM config overwrite wasn't working and people were getting confusing crashes as a result of the game failing to initialise.
Error messages weren't being rotated, which is really just annoying

First PR to the github, let me know if I've missed anything new!

snuck in an extra little change to close the crash issue. I checked bootstrap.xml and we are indeed missing it. Technically it should be crashing in copious too, but I note that most of the new games don't have that in their gamestart.bat, so I imagine konami changed their logic at some point.


Support for Flutter 3.0

When will new release for Flutter 3.0, most of the packages are already migrated, but this one remains outdated for quite of time.

When https://github.com/flutter/flutter/issues/103630 hits Flutter production releases, we will start supporting it. Hopefully Flutter will release this soonish. This issue is sadly blocking a LOT of plugins, not just the HERE SDK.

Yes, I noticed. After making some changes in package and lauching the app, after back button HereMap widget shrinks in really odd way. Ok, thank you for quick response.

this issue seems to be fixed in the flutter 3.3.0 beta.

Alright, it seems that Flutter is on 3.3 version officially. Any near future plans?

Yes, currently we started testing the latest Flutter version if it fixes all the issues.

Any updates?

Hi,
we plan the next release for the upcoming weeks. Sorry for the delay.

Hi,
I hope in the next sprint we can start on a new release

What didn’t i get ? Isnt this solved with the <IP_ADDRESS> here sdk flutter ?

Thank you for pointing this out. Noticed on <IP_ADDRESS>: This release of the HERE SDK requires Flutter 3.3.2. and Dart 2.18.

Hi,
yes, we support Flutter 3.3.2 since <IP_ADDRESS> but unfortuantely the blocking Flutter issue remain.

https://github.com/flutter/flutter/issues/112929
https://github.com/flutter/flutter/issues/89558
https://github.com/flutter/flutter/issues/113051
https://github.com/flutter/flutter/issues/112917

We can update the ref app but it will not solve not all issues with Android 12.

Hi, the support of the HERE SDK 4.12.10 and Flutter 3.3.2 was merged into the master today.


speed up oasis-node pruning

Currently, the node operators docs:
https://docs.oasis.dev/operators/joining-the-testnet.html#configuring-the-oasis-node
suggest running oasis-node with
tendermint:
  abci:
    prune:
      strategy: keep_n
      num_kept: 86400

This resulted in processing 3-4 blocks per second for catching up the network on my local PC with SSD. When I set the prune strategy to none, the throughput increased to ~30 blocks/s which is a huge leap.
I suggest we look into speeding up the prunning operation. Maybe we should prune the tree in a batch (e.g. every 1000 blocks?). Do we have any info on how much space prunning actually saves? Or maybe we use a hybrid approach where for catching up the network, we don't do prunning, and for just following it, we can prune each block?

This is slow because using the pruner requires 1 db lookup and a mountain of deletes per block.  I'm not sure if batching would actually save all that much, the lookup is probably fairly cheap, the delete(s) are likely not.

Do we have any info on how much space prunning actually saves?

A lot.  That's why there's a pruner in the first place.

Or maybe we use a hybrid approach where for catching up the network, we don't do prunning, and for just following it, we can prune each block?

So if I spin up a node when the network has been running for a month, I need to store every single ABCI state version for all of history up to the time I'm caught up?

After 3 days, the serverdir is 9.2GiB big (623K blocks) and I decided to run oasis-node with keep_n strategy. I'm getting very slow prune notifications now (every two seconds):
{"caller":"prune.go:138","latest_version":623404,"level":"debug","module":"abci-mux/pruner","msg":"Prune: Delete","pruned_version":40157,"ts":"2019-11-27T06:29:10.022365875Z"}
{"caller":"prune.go:138","latest_version":623404,"level":"debug","module":"abci-mux/pruner","msg":"Prune: Delete","pruned_version":40158,"ts":"2019-11-27T06:29:12.048162566Z"}
{"caller":"prune.go:138","latest_version":623404,"level":"debug","module":"abci-mux/pruner","msg":"Prune: Delete","pruned_version":40159,"ts":"2019-11-27T06:29:14.068497576Z"}
{"caller":"prune.go:138","latest_version":623404,"level":"debug","module":"abci-mux/pruner","msg":"Prune: Delete","pruned_version":40160,"ts":"2019-11-27T06:29:16.108130267Z"}
{"caller":"prune.go:138","latest_version":623404,"level":"debug","module":"abci-mux/pruner","msg":"Prune: Delete","pruned_version":40161,"ts":"2019-11-27T06:29:18.12803558Z"}
{"caller":"prune.go:138","latest_version":623404,"level":"debug","module":"abci-mux/pruner","msg":"Prune: Delete","pruned_version":40162,"ts":"2019-11-27T06:29:20.146050691Z"}
{"caller":"prune.go:138","latest_version":623404,"level":"debug","module":"abci-mux/pruner","msg":"Prune: Delete","pruned_version":40163,"ts":"2019-11-27T06:29:22.171625901Z"}
{"caller":"prune.go:138","latest_version":623404,"level":"debug","module":"abci-mux/pruner","msg":"Prune: Delete","pruned_version":40164,"ts":"2019-11-27T06:29:24.220972902Z"

The node will never be synced this way, so I disabled prunning.

This was done.


Fix and improve OfferList UI

Adjusted the layout, made it look less wonky when you change the window size.


Add custom margin properties

For smaller screens it would be useful to have some margin on the side.
I added small tweaks to add it.

Hi @MattUV can you please look at it?

Hi! I'm sorry I'm not at home at the moment, I'll have more time to look at your pull request next week 😉

Hi, do you have any updates?


No matching definition when using deferred_type

In answering a question on Stackoverflow, I came across an issue that I don't fully understand. Disregarding whether you actually need to use a deferred_type, the following fails:
import numpy as np
import numba as nb

spec = [('x', nb.float64)]

@nb.jitclass(spec)
class EarthModel:
    def __init__(self, x):
        self.x = x

earth_model_type = nb.deferred_type()
earth_model_type.define(EarthModel.class_type.instance_type)

@nb.jit(nb.float64(nb.float64[:, :], nb.float64[:, :], nb.float64[:, :], earth_model_type))
def test(x, y, z, em):
    return em.x

when running:
em = EarthModel(9.9)
x = np.random.normal(size=(3,3))
y = np.random.normal(size=(3,3))
z = np.random.normal(size=(3,3))

test(x, y, z, em)

with the error:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-15-d98a87d86d5c> in <module>
      4 z = np.random.normal(size=(3,3))
      5
----> 6 test(x, y, z, em)

~/miniconda2/envs/numba-latest/lib/python3.7/site-packages/numba/dispatcher.py in _explain_matching_error(self, *args, **kws)
    498         msg = ("No matching definition for argument type(s) %s"
    499                % ', '.join(map(str, args)))
--> 500         raise TypeError(msg)
    501
    502     def _search_new_conversions(self, *args, **kws):

TypeError: No matching definition for argument type(s) array(float64, 2d, C), array(float64, 2d, C), array(float64, 2d, C), instance.jitclass.EarthModel#6231b36d8<x:float64>

If you instead allow numba to jit the function without supplying types:
import numpy as np
import numba as nb

spec = [('x', nb.float64)]

@nb.jitclass(spec)
class EarthModel:
    def __init__(self, x):
        self.x = x

@nb.jit(nopython=True)
def test(x, y, z, em):
    return em.x

and then this works and the result of test.signatures is:
[(array(float64, 2d, C),
  array(float64, 2d, C),
  array(float64, 2d, C),
  instance.jitclass.EarthModel#623186470<x:float64>)]

so the types look pretty similar. Of course everything works fine if you specify the types, but instead define earth_model_type = EarthModel.class_type.instance_type directly instead of using the deferred_type.

The reason for the error is that numba did not register a conversion of the deferred-type from its defined-type.  It can be easily fixed by adding a can_convert_from() method to DeferredType.
But, should it?
I expect the DeferredType to be used only as the type of fields of aggregates that can refer to itself.


Hover over image under point / rect as well

When hovering over an image with points or rectangles on it, the image hover preview suddenly disappears when we hover over a point or rectangle. This is particularly annoying because the position of the point or rectangle boundary is usually the most interesting place to inspect the image.

Will fix after

#1615


As a developer, I need continuous integration for building the project.

CI will allow us to enforce code coverage standards and enable us to catch any errors that may happen when anyone makes changes.

codeship, travis, or something else?

I think Travis would work well, that seems to be the standards across GitHub at least. Any thoughts?

:+1: sounds good

I added a .travis.yml and activated travis for the project. Seems to run fine :-)
https://travis-ci.org/mlex/karma-spec-reporter/builds/90263003

@mlex thanks


Updates [and backports]

Hey, I found this an awesome idea! And I want to use it in my resources pack, where I backport a lot of things, but I mostly can't do sounds, because of the limits of the sounds.json. This is a very cool mod, I don't want it to get abondened. We need more mods like this.

please, I really can't build a respack on it if it's only for one version


Specialise dyn_ref to improve value detection

I think dyn_ref should be specialised where possible to support objects from other realms (for which regular instanceof check would fail).
For example, it's more reliable to use Array::is_array instead of current instanceof Array for .dyn_ref::<js_sys::Array>(), JsValue::is_object for .dyn_ref::<Object>() and probably also existing methods for primitives for conversions to js_sys::Number, js_sys::JsString and so on.

Can you describe what you mean by 'other realms'? Can you also elaborate on some instances that return true for is_object but false for dyn_ref::<Object>?

A realm is like a new environment with its own set of globals and all that. https://github.com/tc39/proposal-realms
Related example: if you create a new iframe and get its window's Array, then [] instanceof iframeWindow.Array  isn't true.

Can you also elaborate on some instances that return true for is_object but false for dyn_ref::<Object>?

We must be using typeof x === "object" && x !== null for is_object.

Can you also elaborate on some instances that return true for is_object but false for dyn_ref::?

I described some of these instances in a relevant, although slightly different issue https://github.com/rustwasm/wasm-bindgen/issues/1366 - if you create a prototype-less object using Object.create(null), it's not an instance of Object and dyn_ref won't detect it, but it's still a JavaScript object in a wider sense.

Can you describe what you mean by 'other realms'?

In JavaScript, you can pass values between different "realms", and they each will have own prototype chain which prevents instanceof from working.
This is why some types provide own methods for their detection like Array.isArray, or why people used to do Object.prototype.toString.call(value) === '[object Array]' before that methods was added to the language.
Examples of such realms are iframes on the browser side and vm module in Node.js. Arguably, passing values between them might is more of an edge case, but when you do run into it, it's nice to be covered instead of having to debug weird type errors.

Btw, while looking into #1087, I realised that this above is needed not only for prototype-less Objects and cross-realm interaction, but also for new primitives which don't have automatic boxing.
Currently these are:

Symbol
BigInt

and for both instanceof check will return false when used on a corresponding primitive, because they're not objects, and so dyn_ref and dyn_into fail to recognise them too.
Example:
#[wasm_bindgen]
pub fn symbol_to_string_1(s: Symbol) -> JsString {
	s.to_string()
}

#[wasm_bindgen]
pub fn symbol_to_string_2(s: JsValue) -> JsString {
	s.dyn_into::<Symbol>().unwrap().to_string()
}

#[wasm_bindgen]
pub fn symbol_to_string_3(s: JsValue) -> JsString {
	if s.is_symbol() {
		s.unchecked_into::<Symbol>().to_string()
	} else {
		panic!("Not a symbol")
	}
}

Results:
> require('./pkg').symbol_to_string_1(Symbol('x'))
'Symbol(x)'
> require('./pkg').symbol_to_string_2(Symbol('x'))
panicked at 'called `Result::unwrap()` on an `Err` value: JsValue(Symbol(x))', src/libcore/result.rs:997:5
> require('./pkg').symbol_to_string_3(Symbol('x'))
'Symbol(x)'

@alexcrichton Do you think at least this particular instance should be considered a bug? (it certainly looks like one, as there is no way to go from JsValue to Symbol without unchecked right now)


Add new edge to modern browsers

Fixes #726
Since current edge is based on chromium, it should be listed in modern browsers. Also it is used as default browser by many developers.
Since version 79, it's based on Chromium.

 All committers have signed the CLA.

@chrisdothtml @rtsao Bump!


bug: B hint not showing at start of line

In this screenshot, the first character v should be hinted by B.
I've submitted a pull request with a possible fix.

Hmm I don't see your PR for this - or is the fix in your other open PR?

Still getting there, have a merge conflict to resolve. Won't be too long.

Sorry, no rush! Just thought you meant you'd already submitted it :)

I perhaps should have submitted the PR and then mentioned I had submitted it. Wasn't expecting a) the merge conflict and b) a super fast turn around!

Haha yeah, just happened to be working on this at the same time! No worries, I have done the same

PR made, #53


fix(select-state): typescript infers machine state rather than any

:tada: This PR is included in version 1.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter i2c for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.i2c
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E029] Node.js 16 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '12' } }" at package.json.
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 2.5.1 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E036] @iobroker/testing 2.6.0 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[ ] :heavy_exclamation_mark: [E157] js-controller 2.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E254] Versions "0.0.8, 0.0.7" listed at common.news at io-package.json do not exist at NPM. Please remove from news section.

WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W127] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W132] Many "common.news" found in io-package.json. Repository builder will truncate at 7 news. Please remove old news.
[ ] :eyes: [W134] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W135] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W154] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W953] .npmignore found - consider using package.json object "files" instead.

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 13 Sep 2024 11:18:39 GMT based on commit 8db0f9bb52960116fb2b24429ecb43dd7795421d
ioBroker.repochecker 3.0.5

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[E955] iob_npm.done not found in .npmignore
:thumbsup:Thanks for fixing the issues.

This issue has been updated by ioBroker Check and Service Bot
The following issues have been fixed
[W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
:thumbsup:Thanks for fixing the issues.
The following issues are new and have been added
[W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Executable is defined by entry "main" at package.json.


Ubuntu puppeteer 'executablePath' and launch issue

I'm running puppeteer on ubuntu and i'm having issue with the latest chromium (62.0.3188.0) the puppeteer installs, for some reason it doesn't support ffmpeg, i've tried to use other revisions and pointing it to another (chrome) installation via 'executablePath'. but then the puppeteer just launches the browser and gets stuck on the launch.
any help would be greatly appreciated

Chromium doesn't support codecs like mp3 out of the box. You'll need an official distribution for that.
In the past, I've had success on ubunutu with the latest chrome package (chrome 62 now):
wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - &&\
sh -c 'echo "deb http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list' &&\
apt-get update &&\
apt-get install -y google-chrome-unstable

You're using browser.launch({executablePath: 'google-chrome-unstable'});?

thank you! that really solved it.

MP3 support should be coming to Chromium soon though. The patents have now expired to it. Not sure when the work on that is planned (having a hard time finding the issue in crbug.) But, Google Legal as I understand it has approved bringing it to the open-source side.


Update version to 21.67.1

Bump to v21.67.1

Merging in in Max's absence so it can be picked up by the Dependabot check tomorrow morning.


Page header philsherry

Change the page header structure
The current design pattern seems like it could be built a little better.
The page title reads "Check your answers — GOV.UK elements",
which isn't how the h1 reads. Having a span in the h1 gives
differing results, depending on the assistive technology used.
• VoiceOver reads:
"Heading level onetwo items. GOV.UK elements. Check your answers."
("onetwo" read as one word)
• NVDA reads:
"Heading level one. GOV.UK elements. Heading level one. Check your answers."
• JAWS reads:
"GOV.UK elements. Check your answers. Heading level one."
This new version splits the page name (h1) and the section name (p) –
which are now in the correct source order – and then positions the section
name above with CSS. This keeps the pattern visually identical, but brings
added accessibility wins.
The user can skip to the first header and they'll hear just the page title.
• VoiceOver reads:
"Heading level one. Check your answers."
• NVDA reads:
"Heading level one. Check your answers."
• JAWS reads:
"Heading level one. Check your answers."
The next element reads out the section name, with some visually-hidden content.
• VoiceOver reads:
"This section is [section name]"
• NVDA reads:
"This section is [section name]"
• JAWS reads:
"This section is [section name]"

@selfthinker can you please advise on these changes to the structure of the headings for govuk-elements?

@philsherry Thanks for your PR, sorry it's taken so long for me to get to it. I've asked Anika on our accessibility team to review.

Sorry, I've just been looking through some old issues and found my name here. Either I hadn't seen it at first or forgotten about it.
I will be on leave next week and will likely not have time to look at this before then. But I will put it on my todo list and look at it when I get back.

@selfthinker have you had chance to review this?

Sorry, I had looked into this a couple of months ago but delayed responding and then forgot about it.
Back then I also discussed with @edwardhorsford and we agreed that having this type of page header which has essentially two types of headers in one doesn't make sense in the context of GOV.UK Elements. It doesn't make sense to repeat "GOV.UK elements" above every h1.
That makes it quite difficult to review.
It would make sense on an example page to show how to style it and when to use it. But even then how to mark it up depends on the context. Sometimes what you proposed would make sense, other times it wouldn't.
It wouldn't make sense for the most common type where something above the main heading tells you which type of document a page is, for example https://www.gov.uk/guidance/grenfell-tower-fire-june-2017-support-for-people-affected
I wonder if it makes sense to a) remove "GOV.UK elements" everywhere and b) create a section under Typography which shows this component in different contexts.
Do we know which other contexts we have across government?

Following the launch of the GOV.UK Design System, GOV.UK Elements will now only get major bug fixes and security patches.
We have taken this same problem into consideration in some updates to the GOV.UK Design System.
Thanks for raising, sorry it has taken so long to reply.


remove workaround to refresh mounted secrets/configmaps in Tasks section

Following the conversation in #32513 , delete a workaround in the docs (instead of propagating that workaround to other docs pages).

/lgtm

LGTM to me too
/approve jk prow u dont know me like that


Added tickers_types

Added ticker_types func and tests

Codecov Report

Merging #2 (941c2f9) into master (e661808) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #2   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            8        14    +6
=========================================
+ Hits             8        14    +6

Impacted Files
Coverage Δ

src/reference_api.jl
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


gds read/write corruption (SREF)

Describe the bug
using the GDSReader and GDSWriter to test on some file created by klayout. The reader reports "corruption, expect XY...". And the klayout also reports "corruption" on file written by GDSWriter.
Expected Behavior
After this process:
klayout create file -> GDSReader -> GDSWriter -> klayout read file
we shall get the same layout file (clean XOR result)
Environment
Linux 3.10.0
cmake 3.27.2
CXX compiler GNU 9.5.0
anyway, this doesn't matter

To Reproduce
read/write a gds file with SREF record: lib_test.gds
Relevant log output
No response
Screenshots
No response
Additional Context
I suggest the fix is:
>git diff
diff --git a/src/odb/src/gdsin/gdsin.cpp b/src/odb/src/gdsin/gdsin.cpp
index 7e5804d..3affd59 100644
--- a/src/odb/src/gdsin/gdsin.cpp
+++ b/src/odb/src/gdsin/gdsin.cpp
@@ -397,9 +397,9 @@ dbGDSElement* GDSReader::processSRef()
     sref->_transform = processSTrans();
   }

-  readRecord();
   if (_r.type == RecordType::COLROW) {
     sref->_colRow = {_r.data16[0], _r.data16[1]};
+    readRecord();
   } else {
     sref->_colRow = {1, 1};
   }
diff --git a/src/odb/src/gdsin/gdsout.cpp b/src/odb/src/gdsin/gdsout.cpp
index fb8db0f..460642e 100644
--- a/src/odb/src/gdsin/gdsout.cpp
+++ b/src/odb/src/gdsin/gdsout.cpp
@@ -361,7 +361,6 @@ void GDSWriter::writeSRef(dbGDSSRef* sref)
   } else {
     r.type = RecordType::AREF;
   }
-  r.type = RecordType::SREF;
   r.dataType = DataType::NO_DATA;
   writeRecord(r);

Thanks.  Do you have the klayout script to perform the xor comparison?
You could also have opened a PR since you already know the fix.


KAFKA-3616: Make kafka producers/consumers injectable for KafkaStreams

Ticket: https://issues.apache.org/jira/browse/KAFKA-3616

@kawamuray Could you rebase?
A couple of general comments:

Move DefaultClientSupplier into streams/processor/internals as it does not need to be public interface.
Could you also create a MockClientSupplier which uses the MockProducer and MockConsumer and add a unit test to validate that the clients are generated as expected?

@guozhangwang Thanks for reviewing, rebased and addressed your comments with following up unit test fixes.
For your two comments:

Move DefaultClientSupplier into streams/processor/internals as it does not need to be public interface.

Actually, I was thinking below as the practical use since I'm expecting that in most cases only producer or consumer is the injection target. What do you think of?
KafkaStreams streams = new KafkaStreams(topology, config, new DefaultKafkaClientSupplier() {
    @Override
    public Producer<byte[], byte[]> getProducer(Map<String, Object> config) {
        return new MyKafkaProducer<>(...);
    }
});

Could you also create a MockClientSupplier which uses the MockProducer and MockConsumer and add a unit test to validate that the clients are generated as expected?

Ack. Addressed by: c2a5a5a and 8b13ced.

LGTM overall, Jenkins failure are not related (filed separate JIRA).
About the DefaultClientSupplier: in general I'd prefer to keep things private until we see common requirement for them to be public, since vice versa cannot be easily done due to backward incompatibility. Thoughts?

About the DefaultClientSupplier: in general I'd prefer to keep things private until we see common requirement for them to be public, since vice versa cannot be easily done due to backward incompatibility. Thoughts?

Okay, as all methods of DefaultKafkaClientSupplier are fairly easy to re-implemented by users, let me follow your advice ATM :+1:

Merged to trunk and cherry-picked to 0.10.0.


Kibana visualization: Fix the appearance of timestamp and region

Try to fix the timezone to us-east time

Done


Add e2e install testing

This pull request expands e2e testing to include the install page.
#21490 is the parent issue, and these changes should hopefully catch future regressions of that nature. From what I can tell the actual error occurred during page rendering.
The ability to actually perform an install during e2e testing is limited at the moment. I've added more details inside the relevant test, but this is my first contribution and so I felt it might be helpful to get some feedback on the right approach to expanding the coverage.

Keep note that the e2e test is currently not totally reliable. I have not debugged it but it seems to fail pretty often though the tests pass as "flaky", like in the current run from this branch:
  1 flaky
    [webkit] › example.test.e2e.js:9:1 › Load Homepage

So if you can figure out what that problem is, we could maybe disable this "flaky" mechanism.


[Fix-6347][Master]fix bug the first schedule_time is error in complement data

fix bug #6347  fix bug the first schedule_time is error in complement data
the first scheduler_time setting cannot be 'start_date'
It should be obtained according to the first of timing list .

Codecov Report

Merging #6351 (40cb625) into dev (b71f6ae) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                dev    #6351      +/-   ##
============================================
- Coverage     38.91%   38.86%   -0.06%
+ Complexity     3222     3219       -3
============================================
  Files           637      637
  Lines         25436    25451      +15
  Branches       2767     2770       +3
============================================
- Hits           9899     9892       -7
- Misses        14633    14651      +18
- Partials        904      908       +4

Impacted Files
Coverage Δ

...r/server/master/runner/MasterSchedulerService.java
0.00% <0.00%> (ø)

...er/server/master/runner/WorkflowExecuteThread.java
0.00% <0.00%> (ø)

...lphinscheduler/service/process/ProcessService.java
38.66% <0.00%> (-0.61%)
:arrow_down:

...olphinscheduler/rpc/remote/NettyClientHandler.java
41.86% <0.00%> (-9.31%)
:arrow_down:

...inscheduler/common/thread/ThreadPoolExecutors.java
19.23% <0.00%> (-1.93%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.35% <0.00%> (-1.70%)
:arrow_down:

Continue to review full report at Codecov.

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


Add category filter for news post

Fixes #290
Missing frontend component for filtering and also category inside of the news content.

Changes are done.


Receiving empty Buffer in characteristic.on()

When subscribing a characteristic it give an empty buffer.
Here is my code running on rpi4 with Debian Buster:
await characteristic.startNotifications()
characteristic.on('valuechanged', buffer => {
  console.log(buffer) // Show empty Buffer: <Buffer >
})

await characteristic.readValue() // Trigger the callback

Found out that my BLE sensor was faulty.

Found out that my BLE sensor was faulty.


Order details: notes rendering

Without adding any line in the backend, it would be quite nice if the customer could be able to insert blank line and go back at the beginning of the line to let its text breathe.

Currently, if the user tries to do that, it looks like that:

Currently, the code looks like that:
{% for note in notes %}
  {{ note.date }}

{{ note.text }}

{% endfor %}

If we add to the paragraphs this single CSS instruction:
.order-details__total p {
  white-space: pre-wrap;
}

We get:

What do you think about this rendering issue? I also think that we should/ could edit a little bit the note template's structure to make it better.

I like it. Depending on the level of sanitization we currently have, we could even consider allowing basic formatting but that could backfire with customers making everything large and bold.

I'm not a CSS expert but I'm wondering why the styling is applied to the .order-details__total class which seems to be responsible for rendering only the total, so why this affects the notes? Maybe there is something wrong with the template structure. Anyway, it looks much better after your changes.

@elwoodxblues woops, that's true. I only did the changes in the element section of the inspector. I never put the edits in the SASS file. And I also just looked, the notes are not in their section which should be corrected.
From my tests, doing those changes doesn't break anything.
Index: templates/order/details.html
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- templates/order/details.html	(date<PHONE_NUMBER>000)
+++ templates/order/details.html	(date<PHONE_NUMBER>000)
@@ -62,7 +62,8 @@
         {% endif %}
       {% endif %}
       {% include "order/_ordered_items_table.html" %}
-        {% if notes %}
+

+          {% if notes %}

{% trans "Notes" context "Order notes list" %}

           {% for note in notes %}

@@ -90,15 +91,14 @@

{{ note.content }}

           {% endfor %}
         {% endif %}
-      {% if order.is_open %}
-

+        {% if order.is_open %}
           <form method="post" class="form-group">
             {% csrf_token %}
             {% bootstrap_form note_form display_labels=False %}
             <input type="submit" value="Submit" class="btn primary" />
           </form>
-

-      {% endif %}
+        {% endif %}
+

 {% endblock content %}

Could you open a PR with the changes when you have time?

Sure! Do I put the css change as well?

I guess so. If it improves the notes rendering than we should add it, but in the proper selector. I see that in _order-details.scss file there is .order-notes class, so probably there?

Yes, of course! :+1:
I will do that as soon as I can.


Awesome

this is awesome!

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

ID: 77957bce-73f9-6b80-df53-34563ae053a0
Version Independent ID: 491c6d7e-6254-b7ce-0df4-fc345f2707f3
Content: Sign up your organization to use Azure Active Directory
Content Source: articles/active-directory/fundamentals/sign-up-organization.md
Service: active-directory
GitHub Login: @eross-msft
Microsoft Alias: lizross

@xxCrazyII Thanks for your feedback.  We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Improve README description of what Slipstream is

Closing this, as it was done via https://github.com/dennis/slipstream/pull/45

Closing this, as it was done via https://github.com/dennis/slipstream/pull/45


Selected rows lost when updating data

I've implemented a lazy load scroll using code below. I'm using state for rowsSelected , but as soon as I change the state of my rows by adding more rows,  the rows are added to the table, but the selected rows are cleared. I've seen another example of how to maintain filters, but that's at the column level. I'm not sure what else to do here since I already have the  rowsSelected property on the options set to use state. Any ideas would be great. Thanks
    $("div[class^='MUIDataTable-responsive']").on(
        'scroll',
        _.throttle(this.doScroll, 200)  //loads the next page of data if we hit bottom of scroll bar
      );

options = {
    rowsSelected: this.state.rowsSelected,
    print: false,
    download: false,
    filter: false,
    filterType: "checkbox",
    responsive: "scrollMaxHeight",
    selectableRows: "multiple",
    selectableRowsOnClick: false,
    pagination: false,
    fixedHeader: true,
    fixedHeaderOptions: {
        xAxis: false,
        yAxis: true
    },
    onRowsSelect: (rowsSelected, allRows) => {
        this.setState({ rowsSelected: allRows.map(row => row.dataIndex) });
    }
  };

   <MUIDataTable ref="muiTable"
                data={this.state.rows}
                columns={this.columns}
                options={this.options}
                />

Solved my own issue with the help of @SaberMage in this issue:
https://github.com/gregnb/mui-datatables/issues/807
All I did was tried moving my options from the class property down to the tag itself and it worked.  Don't completely understand why but something with having the options declared in the tag itself made the selected rows persist.
<MUIDataTable ref="muiTable"
data={this.state.rows}
columns={this.columns}
options={{
......................
}}
/>


FastRTPS v1.10.0 payload data is truncated by 4 bytes. [8152]

When reading data using RTPSReader, incoming change data is truncated by 4 bytes. The remote system runs under RTI Connext DDS.
There were no problems with version 1.9.4.
Expected Behavior
Test code running under FastRTPS v1.9.4:
plemu@userv:/mnt/data/rtps94/build/fastrtps/examples/C++/RTPSTest_registered/bin$ ./RTPSTest_registered reader
Starting RTPS example
Registering Reader
Press Enter to stop the Reader.
Received: 48 147112
000000: 00 01 00 00 00 00 00 00 00 00 00 00 01 00 00 00  ................
000010: 00 00 00 00 00 00 00 20 5c 2f 41 40 00 00 00 00<EMAIL_ADDRESS>000020: 00 00 00 00 07 00 00 00 6d 73 35 38 33 37 00 00  ........ms5837..
Received: 48 147113
000000: 00 01 00 00 00 00 00 00 00 00 00 00 01 00 00 00  ................
000010: 00 00 00 00 00 00 00 40 33 33 41 40 00 00 00 00<EMAIL_ADDRESS>000020: 00 00 00 00 07 00 00 00 6d 73 35 38 33 37 00 00  ........ms5837..

Received: 48 147115
000000: 00 01 00 00 00 00 00 00 00 00 00 00 01 00 00 00  ................
000010: 00 00 00 00 00 00 00 e0 a3 30 41 40 00 00 00 00<EMAIL_ADDRESS>000020: 00 00 00 00 07 00 00 00 6d 73 35 38 33 37 00 00  ........ms5837..

Current Behavior
Test code running under FastRTPS v1.10.0:
plemu@userv:/mnt/data/rtps10/build/fastrtps/examples/C++/RTPSTest_registered/bin$ ./RTPSTest_registered reader
Starting RTPS example
Registering Reader
Press Enter to stop the Reader.
 \OA@....
000020: 00 00 00 00 07 00 00 00 6d 73 35 38              ........ms58

Steps to Reproduce
Unfortunately, I can't provide the steps for playback. Writer part is closed-source. Reader part source code is attached.
A trace comparison showed that the 4-byte difference between 1.10.0 and 1.9.4 starts with the inlineQosSize value returned by the updateCacheChangeFromInlineQos function.
System information

Fast-RTPS version: tag: v1.10.0
OS: Ubuntu 18.04.4
Network interfaces: eth0 (<IP_ADDRESS>)

Additional resources

Reader source code
sampleData.pcapng.zip
Wireshark packet dissect

Frame 1: 170 bytes on wire (1360 bits), 170 bytes captured (1360 bits) on interface 0
    Interface id: 0 (en0)
        Interface name: en0
        Interface description: Ethernet
    Encapsulation type: Ethernet (1)
    Arrival Time: Apr  8, 2020 10:52:16.390668000 MSK
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time:<PHONE_NUMBER>.390668000 seconds
    [Time delta from previous captured frame: 0.000000000 seconds]
    [Time delta from previous displayed frame: 0.000000000 seconds]
    [Time since reference or first frame: 0.000000000 seconds]
    Frame Number: 1
    Frame Length: 170 bytes (1360 bits)
    Capture Length: 170 bytes (1360 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: eth:ethertype:ip:udp:rtps]
    [Coloring Rule Name: UDP]
    [Coloring Rule String: udp]
Ethernet II, Src: Raspberr_cc:5f:8b (b8:27:eb:cc:5f:8b), Dst: AsustekC_a4:75:e7 (40:16:7e:a4:75:e7)
    Destination: AsustekC_a4:75:e7 (40:16:7e:a4:75:e7)
        Address: AsustekC_a4:75:e7 (40:16:7e:a4:75:e7)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: Raspberr_cc:5f:8b (b8:27:eb:cc:5f:8b)
        Address: Raspberr_cc:5f:8b (b8:27:eb:cc:5f:8b)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: IPv4 (0x0800)
Internet Protocol Version 4, Src: <IP_ADDRESS>, Dst: <IP_ADDRESS>
    0100 .... = Version: 4
    .... 0101 = Header Length: 20 bytes (5)
    Differentiated Services Field: 0x00 (DSCP: CS0, ECN: Not-ECT)
        0000 00.. = Differentiated Services Codepoint: Default (0)
        .... ..00 = Explicit Congestion Notification: Not ECN-Capable Transport (0)
    Total Length: 156
    Identification: 0xb328 (45864)
    Flags: 0x4000, Don't fragment
        0... .... .... .... = Reserved bit: Not set
        .1.. .... .... .... = Don't fragment: Set
        ..0. .... .... .... = More fragments: Not set
        ...0 0000 0000 0000 = Fragment offset: 0
    Time to live: 64
    Protocol: UDP (17)
    Header checksum: 0x2cec [validation disabled]
    [Header checksum status: Unverified]
    Source: <IP_ADDRESS>
    Destination: <IP_ADDRESS>
User Datagram Protocol, Src Port: 41315, Dst Port: 7413
    Source Port: 41315
    Destination Port: 7413
    Length: 136
    Checksum: 0xbee8 [unverified]
    [Checksum Status: Unverified]
    [Stream index: 0]
    [Timestamps]
        [Time since first frame: 0.000000000 seconds]
        [Time since previous frame: 0.000000000 seconds]
Real-Time Publish-Subscribe Wire Protocol
    Magic: RTPS
    Protocol version: 2.3
        major: 2
        minor: 3
    vendorId: 01.01 (Real-Time Innovations, Inc. - Connext DDS)
    guidPrefix: ac10011a0000006200000001
        hostId: 0xac10011a
        appId: 0x00000062
        instanceId: 0x00000001
    Default port mapping: domainId=0, participantIdx=1, nature=UNICAST_USERTRAFFIC
        [domain_id: 0]
        [participant_idx: 1]
        [traffic_nature: UNICAST_USERTRAFFIC (3)]
    submessageId: INFO_TS (0x09)
        Flags: 0x01, Endianness bit
            0... .... = Reserved: Not set
            .0.. .... = Reserved: Not set
            ..0. .... = Reserved: Not set
            ...0 .... = Reserved: Not set
            .... 0... = Reserved: Not set
            .... .0.. = Reserved: Not set
            .... ..0. = Timestamp flag: Not set
            .... ...1 = Endianness bit: Set
        octetsToNextHeader: 8
        Timestamp: Apr  8, 2020 07:52:16.386869998 UTC
    submessageId: DATA (0x15)
        Flags: 0x07, Data present, Inline QoS, Endianness bit
            0... .... = Reserved: Not set
            .0.. .... = Reserved: Not set
            ..0. .... = Reserved: Not set
            ...0 .... = Reserved: Not set
            .... 0... = Serialized Key: Not set
            .... .1.. = Data present: Set
            .... ..1. = Inline QoS: Set
            .... ...1 = Endianness bit: Set
        octetsToNextHeader: 92
        0000 0000 0000 0000 = Extra flags: 0x0000
        Octets to inline QoS: 16
        readerEntityId: ENTITYID_UNKNOWN (0x00000000)
            readerEntityKey: 0x000000
            readerEntityKind: Application-defined unknown kind (0x00)
        writerEntityId: 0x80008402 (Application-defined writer (with key): 0x800084)
            writerEntityKey: 0x800084
            writerEntityKind: Application-defined writer (with key) (0x02)
        writerSeqNumber: 10762
        inlineQos:
            PID_KEY_HASH
                parameterId: PID_KEY_HASH (0x0070)
                parameterLength: 16
                guid: 33b80eed:cc3aae2f:bd3ac1c6:b7c2073e
            PID_SENTINEL
                parameterId: PID_SENTINEL (0x0001)
        serializedData
            encapsulation kind: CDR_LE (0x0001)
            encapsulation options: 0x0000
            serializedData:<PHONE_NUMBER>0000000100000000000000000000c0cccc3a40…

@DimaRU Please check with #1138, which should fix this issue.

@DimaRU Please check with #1138, which should fix this issue.

As #1138 has been merged, please check with 1.10.x branch

I check against 1.10.x branch, now all work as expected. Thank you.  👍🏻


Update borer-compat-circe, borer-core to 1.8.0

Updates

io.bullet:borer-compat-circe
io.bullet:borer-core

from 1.7.2 to 1.8.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.bullet" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "io.bullet" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report

Merging #331 (76c541a) into main (b66e126) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #331   +/-   ##
=======================================
  Coverage   88.76%   88.76%
=======================================
  Files          91       91
  Lines        2778     2778
  Branches       72       72
=======================================
  Hits         2466     2466
  Misses        312      312

Impacted Files
Coverage Δ

src/main/scala/kinesis/mock/instances/borer.scala
38.88% <ø> (ø)

Continue to review full report at Codecov.

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


Revert "Add optional endpoint flag for API response caching"

Reverts api3dao/ois#16 as it was decided that this flag should instead live in triggers.rrp[n] of config.json. For some discussion see: https://github.com/api3dao/airnode/pull/1372#discussion_r942044155

Oh, I was not even aware we did this. 👍 LGTM