Adding beagleplay support

Initial PR -
Got the 'balena-image' target to run to completion. Made a pair of new beaglebone devices: beaglebone-play and beaglebone-play-k3r5.
The code compiles, but does not get past the u-boot stage.
This PR was created to allow the balena dev to inspect it.

Can one of the admins verify this patch?

Currently u-boot-ti-staging is having issues reading the EEPROM (assuming it does the same as the beaglebone-ai64). I have just pushed another MR in which I add some patches on top of it to force the board, you could do the same for the time being.It is worth to mention that the bootloader is currently work in progress in meta-ti.

Thanks @perezmeyer for your inputs. One of the biggest  changes I made was to drop the linux-beagleboard recipe in favor of the linux-bb.org recipe (this is what the stock meta-ti-bsp layer for the beagleplay board also uses).
Is that a bad idea ? (especially since the .bb file has the all important inherit kernel kernel-resin line in it.
I had to do this initially because of all the build errors I was getting in moving from u-boot to u-boot-ti-staging

Thanks @perezmeyer for your inputs. One of the biggest changes I made was to drop the linux-beagleboard recipe in favor of the linux-bb.org recipe (this is what the stock meta-ti-bsp layer for the beagleplay board also uses).
Is that a bad idea ? (especially since the .bb file has the all important inherit kernel kernel-resin line in it.
I had to do this initially because of all the build errors I was getting in moving from u-boot to u-boot-ti-staging

No, that's actually fine. I could boot the Beaglebone AI64 from an SD card using meta-ti's kernel and bootloader, this last one with some patches from the beaglebone one. They actually have almost no difference!
Now I could not boot from the eMMC, but looking at the differences it might explain why.
You could try creating a u-boot-ti-staging.bbappend file with at least:
# Use BeagleBone's u-boot until u-boot-ti-staging has the BBAI64 support upstreamed.
BRANCH:beaglebone-play= "v2023.04-ti-<IP_ADDRESS>"
UBOOT_GIT_URI:beaglebone-play = "git://git.beagleboard.org/beagleboard/u-boot.git"
SRCREV:beaglebone-play = "354f64f67e5b36df0027dbfbf071503b0071f4ed"

And check what happens

@perezmeyer - thanks for your prompt response ! I'll try this next week (travelling tomorrow).

@perezmeyer I (finally) got the balena OS boot sequence kicked off. Unfortunately, it fails to run to completion (see logs below):
Starting kernel ...

I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Secondary CPU 2 initializing
I/TC: Secondary CPU 2 switching to normal world boot
I/TC: Secondary CPU 3 initializing
I/TC: Secondary CPU 3 switching to normal world boot
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.10.162+ (oe-user@oe-host) (aarch64-poky-linux-gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP Thu Apr 6 21:42:04 UTC 2023
[    0.000000] Machine model: BeagleBoard.org BeaglePlay
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009c800000, size 3 MiB
[    0.000000] OF: reserved mem: initialized node ipc-memories@9c800000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009cb00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node m4f-dma-memory@9cb00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009cc00000, size 14 MiB
[    0.000000] OF: reserved mem: initialized node m4f-memory@9cc00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009da00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@9da00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009db00000, size 12 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@9db00000, compatible id shared-dma-pool
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000080000000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x000000009c7fffff]
[    0.000000]   node   0: [mem 0x000000009c800000-0x000000009e6fffff]
[    0.000000]   node   0: [mem 0x000000009e700000-0x000000009e77ffff]
[    0.000000]   node   0: [mem 0x000000009e780000-0x000000009fffffff]
[    0.000000]   node   0: [mem 0x00000000a0000000-0x00000000ffffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff]
[    0.000000] cma: Reserved 144 MiB at 0x00000000f4000000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: Trusted OS migration not required
[    0.000000] psci: SMC Calling Convention v1.2
[    0.000000] percpu: Embedded 32 pages/cpu s92952 r8192 d29928 u131072
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: GIC system register CPU interface
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[    0.000000] Kernel command line: console=ttyS2,115200n8 root=PARTUUID=2f8cd71b-02 rw rootfstype=ext4 rootwait
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000] Memory: 1764708K/2097152K available (16704K kernel code, 1996K rwdata, 5132K rodata, 62272K init, 693K bss, 184988K reserved, 147456K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]  Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[    0.000000] GICv3: 256 SPIs implemented
[    0.000000] GICv3: 0 Extended SPIs implemented
[    0.000000] GICv3: Distributor has no Range Selector support
[    0.000000] GICv3: 16 PPIs implemented
[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000001880000
[    0.000000] ITS [mem 0x01820000-0x0182ffff]
[    0.000000] GIC: enabling workaround for ITS: Socionext Synquacer pre-ITS
[    0.000000] ITS@0x0000000001820000: Devices Table too large, reduce ids 20->19
[    0.000000] ITS@0x0000000001820000: allocated 524288 Devices @80800000 (flat, esz 8, psz 64K, shr 0)
[    0.000000] ITS: using cache flushing for cmd queue
[    0.000000] GICv3: using LPI property table @0x00000000800c0000
[    0.000000] GIC: using cache flushing for LPI property table
[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000000800d0000
[    0.000000] arch_timer: cp15 timer(s) running at 200.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e2049d3e8, max_idle_ns:<PHONE_NUMBER>34 ns
[    0.000004] sched_clock: 56 bits at 200MHz, resolution 5ns, wraps every<PHONE_NUMBER>102ns
[    0.000361] Console: colour dummy device 80x25
[    0.000421] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=800000)
[    0.000434] pid_max: default: 32768 minimum: 301
[    0.000721] LSM: Security Framework initializing
[    0.000771] Yama: becoming mindful.
[    0.000919] AppArmor: AppArmor initialized
[    0.000928] TOMOYO Linux initialized
[    0.001056] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.001079] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.003490] rcu: Hierarchical SRCU implementation.
[    0.004814] Platform MSI: msi-controller@1820000 domain created
[    0.005111] PCI/MSI: /bus@f0000/interrupt-controller@1800000/msi-controller@1820000 domain created
[    0.005180] EFI services will not be available.
[    0.005864] smp: Bringing up secondary CPUs ...
[    0.014644] Detected VIPT I-cache on CPU1
[    0.014683] GICv3: CPU1: found redistributor 1 region 0:0x00000000018a0000
[    0.014697] GICv3: CPU1: using allocated LPI pending table @0x00000000800e0000
[    0.014765] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.023611] Detected VIPT I-cache on CPU2
[    0.023638] GICv3: CPU2: found redistributor 2 region 0:0x00000000018c0000
[    0.023649] GICv3: CPU2: using allocated LPI pending table @0x00000000800f0000
[    0.023689] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.032532] Detected VIPT I-cache on CPU3
[    0.032559] GICv3: CPU3: found redistributor 3 region 0:0x00000000018e0000
[    0.032570] GICv3: CPU3: using allocated LPI pending table @0x0000000080100000
[    0.032608] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.032703] smp: Brought up 1 node, 4 CPUs
[    0.032739] SMP: Total of 4 processors activated.
[    0.032746] CPU features: detected: 32-bit EL0 Support
[    0.032753] CPU features: detected: CRC32 instructions
[    0.032759] CPU features: detected: 32-bit EL1 Support
[    0.048201] CPU: All CPU(s) started at EL2
[    0.048270] alternatives: patching kernel code
[    0.049986] devtmpfs: initialized
[    0.060222] KASLR disabled due to lack of seed
[    0.060531] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>100000 ns
[    0.060580] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.065237] pinctrl core: initialized pinctrl subsystem
[    0.065941] DMI not present or invalid.
[    0.066730] NET: Registered protocol family 16
[    0.068699] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[    0.068862] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.069041] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.069121] audit: initializing netlink subsys (disabled)
[    0.069407] audit: type=2000 audit(0.068:1): state=initialized audit_enabled=0 res=1
[    0.069989] thermal_sys: Registered thermal governor 'fair_share'
[    0.069993] thermal_sys: Registered thermal governor 'bang_bang'
[    0.069999] thermal_sys: Registered thermal governor 'step_wise'
[    0.070004] thermal_sys: Registered thermal governor 'user_space'
[    0.070008] thermal_sys: Registered thermal governor 'power_allocator'
[    0.070697] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.070839] ASID allocator initialised with 65536 entries
[    0.099995] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.100017] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.100023] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.100029] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.101885] cryptd: max_cpu_qlen set to 1000
[    0.105370] raid6: skip pq benchmark and using algorithm neonx8
[    0.105392] raid6: using neon recovery algorithm
[    0.106329] k3-chipinfo 43000014.chipid: Family:AM62X rev:SR1.0 JTAGID[0x0bb7e02f] Detected
[    0.106807] vdd_3v3: supplied by vsys_5v0
[    0.107759] iommu: Default domain type: Translated
[    0.108563] SCSI subsystem initialized
[    0.108781] usbcore: registered new interface driver usbfs
[    0.108828] usbcore: registered new interface driver hub
[    0.108863] usbcore: registered new device driver usb
[    0.109390] mc: Linux media interface: v0.10
[    0.109416] videodev: Linux video capture interface: v2.00
[    0.109544] pps_core: LinuxPPS API ver. 1 registered
[    0.109550] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    0.109565] PTP clock support registered
[    0.109600] EDAC MC: Ver: 3.0.0
[    0.110387] omap-mailbox 29000000.mailbox: omap mailbox rev 0x66fc9100
[    0.111589] NetLabel: Initializing
[    0.111601] NetLabel:  domain hash size = 128
[    0.111605] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.111672] NetLabel:  unlabeled traffic allowed by default
[    0.112426] clocksource: Switched to clocksource arch_sys_counter
[    0.219359] VFS: Disk quotas dquot_6.6.0
[    0.219453] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.219645] FS-Cache: Loaded
[    0.220085] CacheFiles: Loaded
[    0.220660] AppArmor: AppArmor Filesystem Enabled
[    0.227805] NET: Registered protocol family 2
[    0.228076] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.229433] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    0.229666] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.229897] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.230122] TCP: Hash tables configured (established 16384 bind 16384)
[    0.230476] MPTCP token hash table entries: 2048 (order: 3, 49152 bytes, linear)
[    0.230606] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.230666] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.230911] NET: Registered protocol family 1
[    0.230937] NET: Registered protocol family 44
[    0.230953] PCI: CLS 0 bytes, default 64
[    0.412730] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    0.413346] kvm [1]: IPA Size Limit: 40 bits
[    0.414173] kvm [1]: vgic-v2@100010000
[    0.414201] kvm [1]: GIC system register CPU interface enabled
[    0.414321] kvm [1]: vgic interrupt IRQ9
[    0.414456] kvm [1]: Hyp mode initialized successfully
[    0.419185] Initialise system trusted keyrings
[    0.419429] workingset: timestamp_bits=46 max_order=19 bucket_order=0
[    0.425020] zbud: loaded
[    0.426735] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.427899] fuse: init (API version 7.32)
[    0.464441] xor: measuring software checksum speed
[    0.468482]    8regs           :  2464 MB/sec
[    0.471857]    32regs          :  2919 MB/sec
[    0.475761]    arm64_neon      :  2527 MB/sec
[    0.475766] xor: using function: 32regs (2919 MB/sec)
[    0.475784] Key type asymmetric registered
[    0.475791] Asymmetric key parser 'x509' registered
[    0.475849] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[    0.476059] io scheduler mq-deadline registered
[    0.478255] pinctrl-single 4084000.pinctrl: 34 pins, size 136
[    0.478775] pinctrl-single f4000.pinctrl: 171 pins, size 684
[    0.487187] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled
[    0.501945] brd: module loaded
[    0.640534] loop: module loaded
[    0.641132] zram: Added device: zram0
[    0.642466] megasas: 07.714.04.00-rc1
[    0.647255] tun: Universal TUN/TAP device driver, 1.6
[    0.647890] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    0.647899] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    0.647996] sky2: driver version 1.30
[    0.649062] VFIO - User Level meta-driver version: 0.3
[    0.649659] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.649738] ehci-pci: EHCI PCI platform driver
[    0.650339] usbcore: registered new interface driver uas
[    0.650380] usbcore: registered new interface driver usb-storage
[    0.650474] usbcore: registered new interface driver usbserial_generic
[    0.650518] usbserial: USB Serial support registered for generic
[    0.652142] i2c /dev entries driver
[    0.652365] Driver for 1-wire Dallas network protocol.
[    0.652491] DS1WM w1 busmaster driver - (c) 2004 Szabolcs Gyurko
[    0.654405] sdhci: Secure Digital Host Controller Interface driver
[    0.654419] sdhci: Copyright(c) Pierre Ossman
[    0.654719] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.655848] ledtrig-cpu: registered to indicate activity on CPUs
[    0.656284] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    0.656821] hid: raw HID events driver (C) Jiri Kosina
[    0.657071] usbcore: registered new interface driver usbhid
[    0.657077] usbhid: USB HID core driver
[    0.657921] optee: probing for conduit method.
[    0.657960] optee: revision 3.18 (4adb4a1f)
[    0.658364] optee: dynamic shared memory is enabled
[    0.658598] optee: initialized driver
[    0.659554] drop_monitor: Initializing network drop monitor service
[    0.660183] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
[    0.660245] IPVS: Connection hash table configured (size=4096, memory=32Kbytes)
[    0.660472] IPVS: ipvs loaded.
[    0.661254] NET: Registered protocol family 10
[    0.681731] Segment Routing with IPv6
[    0.681849] mip6: Mobile IPv6
[    0.681963] NET: Registered protocol family 17
[    0.682052] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    0.682240] Key type dns_resolver registered
[    0.682248] mpls_gso: MPLS GSO support
[    0.682586] registered taskstats version 1
[    0.682603] Loading compiled-in X.509 certificates
[    0.682780] zswap: loaded using pool lzo/zbud
[    0.683197] Key type .fscrypt registered
[    0.683206] Key type fscrypt-provisioning registered
[    0.688306] Btrfs loaded, crc32c=crc32c-generic
[    0.688504] AppArmor: AppArmor sha1 policy hashing enabled
[    0.699831] ti-sci 44043000.system-controller: ABI: 3.1 (firmware rev 0x0008 '8.5.3--v08.05.03 (Chill Capybar')
[    0.767369] omap-gpmc 3b000000.memory-controller: GPMC revision 6.0
[    0.767394] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000
[    0.770770] omap_i2c 4900000.i2c: bus 5 rev0.12 at 10 kHz
[    0.772780] at24 0-0050: supply vcc not found, using dummy regulator
[    0.796611] at24 0-0050: 4096 byte 24c32 EEPROM, writable, 1 bytes/write
[    0.800222] VDD_CORE: Bringing 750000uV into<PHONE_NUMBER>00uV
[    0.801092] VDD_CORE: supplied by vsys_5v0
[    0.802043] VDD_1V8: supplied by vsys_5v0
[    0.802932] VDD_1V2: supplied by vsys_5v0
[    0.803967] VDD_SD_3V3: supplied by vdd_3v3
[    0.805171] VDDA_0V85: supplied by VDD_1V8
[    0.806342] VDDA_1V8: supplied by vdd_3v3
[    0.807218] VDD_2V5: supplied by vdd_3v3
[    0.809737] input: tps65219-pwrbutton as<EMAIL_ADDRESS>[    0.810475] tps65219 0-0030: Setup as system-power-controller but pm_power_off function already registered, overwriting
[    0.810752] omap_i2c 20000000.i2c: bus 0 rev0.12 at 400 kHz
[    0.812443] omap_i2c 20010000.i2c: bus 1 rev0.12 at 10 kHz
[    0.814405] omap_i2c 20020000.i2c: bus 2 rev0.12 at 10 kHz
[    0.815804] omap_i2c 20030000.i2c: bus 3 rev0.12 at 400 kHz
[    0.816213] ti-sci-intr 4210000.interrupt-controller: Interrupt Router 5 domain created
[    0.816383] ti-sci-intr bus@f0000:interrupt-controller@a00000: Interrupt Router 3 domain created
[    0.816691] ti-sci-inta 48000000.interrupt-controller: Interrupt Aggregator domain 28 created
[    0.817018] ti-udma 485c0100.dma-controller: Number of rings: 82
[    0.819274] ti-udma 485c0100.dma-controller: Channels: 48 (bchan: 18, tchan: 12, rchan: 18)
[    0.822568] ti-udma 485c0000.dma-controller: Number of rings: 150
[    0.826994] ti-udma 485c0000.dma-controller: Channels: 35 (tchan: 20, rchan: 15)
[    0.830431] 4a00000.serial: ttyS1 at MMIO 0x4a00000 (irq = 15, base_baud = 3000000) is a 8250
[    0.831944] 2b300000.serial: ttyS0 at MMIO 0x2b300000 (irq = 18, base_baud = 3000000) is a 8250
[    0.833400] 2800000.serial: ttyS2 at MMIO 0x2800000 (irq = 29, base_baud = 3000000) is a 8250
[    2.358942] printk: console [ttyS2] enabled
[    2.365007] 2850000.serial: ttyS3 at MMIO 0x2850000 (irq = 30, base_baud = 3000000) is a 8250
[    2.373614] serial serial0: tty port ttyS3 registered
[    2.379430] omap8250 2860000.serial: PM domain pd:158 will not be powered off
[    2.386905] 2860000.serial: ttyS4 at MMIO 0x2860000 (irq = 31, base_baud = 3000000) is a 8250
[    2.395575] serial serial1: tty port ttyS4 registered
[    2.406575] am65-cpsw-nuss 8000000.ethernet: initializing am65 cpsw nuss version 0x6BA01103, cpsw version 0x6BA81103 Ports: 3 quirks:00000006
[    2.419584] am65-cpsw-nuss 8000000.ethernet: Use random MAC address
[    2.425854] am65-cpsw-nuss 8000000.ethernet: initialized cpsw ale version 1.5
[    2.432978] am65-cpsw-nuss 8000000.ethernet: ALE Table size 512
[    2.439742] am65-cpsw-nuss 8000000.ethernet: CPTS ver 0x4e8a010c, freq:500000000, add_val:1 pps:0
[    2.450268] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 19
[    2.461445] rtc-ti-k3 2b1f0000.rtc: registered as rtc1
[    2.570494] sdhci-am654 fa00000.mmc: parsing dt failed (-517)
[    2.570913] mmc0: CQHCI version 5.10
[    2.580505] wlan_en: supplied by vdd_3v3
[    2.585022] vdd_3v3_sd: supplied by vdd_3v3
[    2.590248] mikrobus:mikrobus_port_register: registering port mikrobus-0
[    2.590315] mikrobus mikrobus-0: mikrobus port 0 eeprom empty probing default eeprom
[    2.606367] bq32k 0-0068: Oscillator Failure. Check RTC battery.
[    2.612899] bq32k 0-0068: registered as rtc0
[    2.616469] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
[    2.617443] bq32k 0-0068: hctosys: unable to read the hardware clock
[    2.694585] mmc0: Command Queue Engine enabled
[    2.699059] mmc0: new HS200 MMC card at address 0001
[    2.704931] mmcblk0: mmc0:0001 TB2916 14.6 GiB
[    2.709733] mmcblk0boot0: mmc0:0001 TB2916 partition 1 4.00 MiB
[    2.715939] mmcblk0boot1: mmc0:0001 TB2916 partition 2 4.00 MiB
[    2.717451] it66121 2-004c: IT66121 revision 1 probed
[    2.722073] mmcblk0rpmb: mmc0:0001 TB2916 partition 3 4.00 MiB, chardev (236:0)
[    2.735876]  mmcblk0: p1 p2
[    2.952300] [drm] Initialized tidss 1.0.0 20180215 for 30200000.dss on minor 0
[    2.967854] tidss 30200000.dss: [drm] Cannot find any crtc or sizes
[    3.123065] debugfs: Directory 'pd:53' with parent 'pm_genpd' already present!
[    3.123423] sdhci-am654 fa00000.mmc: Got CD GPIO
[    3.123851] mmc2: CQHCI version 5.10
[    3.130416] debugfs: Directory 'pd:52' with parent 'pm_genpd' already present!
[    3.135477] mmc1: CQHCI version 5.10
[    3.138548] debugfs: Directory 'pd:51' with parent 'pm_genpd' already present!
[    3.156914] debugfs: Directory 'pd:182' with parent 'pm_genpd' already present!
[    3.165310] mmc2: SDHCI controller on fa20000.mmc [fa20000.mmc] using ADMA 64-bit
[    3.167141] input: gpio-keys as /devices/platform/gpio-keys/input/input1
[    3.178655] sdhci-am654 fa20000.mmc: card claims to support voltages below defined range
[    3.179984] of_cfs_init
[    3.184765] mmc1: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit
[    3.197662] of_cfs_init: OK
[    3.199594] mmc2: new high speed SDIO card at address 0001
[    3.265535] Freeing unused kernel memory: 62272K
[    3.295107] Checked W+X mappings: passed, no W+X pages found
[    3.298830] mmc1: new ultra high speed SDR104 SDHC card at address 0001
[    3.300803] Run /init as init process
[    3.308774] mmcblk1: mmc1:0001 SD32G 28.8 GiB
[    3.319949]  mmcblk1: p1 p2 p3 p4 < p5 p6 >
Starting version 250.5+
[    4.129872] zram0: detected capacity change from 0 to<PHONE_NUMBER>
[    4.199021] w1_master_driver w1_bus_master1: w1_search: max_slave_count 64 reached, will continue next search.
[   10.954740] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[   11.031350] EXT4-fs (mmcblk1p5): mounted filesystem with ordered data mode. Opts: (null)
[   11.397149] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[   13.280435] random: crng init done
[   13.293502] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[   13.364804] Not activating Mandatory Access Control as /sbin/tomoyo-init does not exist.
[   13.555653] systemd[1]: System time before build time, advancing clock.

Welcome to balenaOS 3.1.8!

[   13.741436] systemd[686]: /lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1.
[   14.026876] systemd[1]: /lib/systemd/system/balena-host.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/balena-host.sock → /run/balena-host.sock; please update the unit file accordingly.
[   14.081965] systemd[1]: /lib/systemd/system/balena-engine.socket:7: ListenStream= references a path below legacy directory /var/run/, updating /var/run/balena-engine.sock → /run/balena-engine.sock; please update the unit file accordingly.
[  OK  ] Created slice Slice /system/balena-info.
[  OK  ] Created slice Slice /system/getty.
[  OK  ] Created slice Slice /system/modprobe.
[  OK  ] Created slice Slice /system/serial-getty.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Forward Password R…uests to Wall Directory Watch.
[  OK  ] Reached target Development features.
[  OK  ] Reached target Remote File Systems.
[  OK  ] Reached target Slice Units.
[  OK  ] Reached target Swaps.
[  OK  ] Listening on initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on User Database Manager Socket.
         Mounting Huge Pages File System...
         Mounting POSIX Message Queue File System...
         Mounting Kernel Debug File System...
         Mounting Kernel Trace File System...
         Mounting Temporary Directory /tmp...
         Starting Create List of Static Device Nodes...
         Starting Resin active root partition mount service...
         Starting Load Kernel Module configfs...
         Starting Load Kernel Module drm...
         Starting Load Kernel Module fuse...
         Starting Resin boot partition mount service...
         Starting Resin state partition mount service...
         Starting Rollback clear bo…boot crumb is still present...
         Starting Generate network …ts from Kernel command line...
         Starting Remount Root and Kernel File Systems...
         Starting Apply Kernel Variables...
         Starting Coldplug All udev Devices...
         Starting Setup Virtual Console...
         Starting Set the system clock from the build timestamp...
[  OK  ] Mounted Huge Pages File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted Kernel Trace File System.
[  OK  ] Mounted Temporary Directory /tmp.
[  OK  ] Finished Create List of Static Device Nodes.
[  OK  ] Finished Load Kernel Module configfs.
[  OK  ] Finished Load Kernel Module drm.
[  OK  ] Finished Load Kernel Module fuse.
[  OK  ] Finished Resin boot partition mount service.
[  OK  ] Finished Resin state partition mount service.
[  OK  ] Finished Rollback clear bo…ltboot crumb is still present.
[  OK  ] Finished Generate network units from Kernel command line.
[  OK  ] Finished Remount Root and Kernel File Systems.
[  OK  ] Finished Apply Kernel Variables.
[  OK  ] Finished Setup Virtual Console.
[  OK  ] Finished Set the system clock from the build timestamp.
         Mounting FUSE Control File System...
         Mounting Kernel Configuration File System...
         Starting OS configuration device key service...
         Starting Expand resin-data partition...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Finished Coldplug All udev Devices.
[  OK  ] Finished Create Static Device Nodes in /dev.
[  OK  ] Finished OS configuration device key service.
[  OK  ] Reached target Preparation for Local File Systems.
[  OK  ] Set up automount mnt-sysroot-inactive partition.
         Mounting /var/volatile...
         Starting Wait for udev To …plete Device Initialization...
[  OK  ] Finished Expand resin-data partition.
[  OK  ] Mounted /var/volatile.
         Starting Runtime development features management...
         Starting Resin data partition mount service...
         Mounting Bind mount for /etc/fake-hwclock...
         Starting Bind mount volatile /var/cache...
         Starting Bind mount volatile /var/lib...
         Starting Bind mount volatile /var/spool...
         Starting Bind mount volatile /srv...
[  OK  ] Finished Resin data partition mount service.
[  OK  ] Mounted Bind mount for /etc/fake-hwclock.
[  OK  ] Finished Bind mount volatile /var/cache.
[  OK  ] Finished Bind mount volatile /var/lib.
[  OK  ] Finished Bind mount volatile /var/spool.
[  OK  ] Finished Bind mount volatile /srv.
[  OK  ] Finished Runtime development features management.
         Mounting resin-data bind mount...
         Mounting Docker data mountpoint...
         Starting Restore/save the current clock...
[  OK  ] Mounted resin-data bind mount.
[  OK  ] Mounted Docker data mountpoint.
[  OK  ] Finished Restore/save the current clock.
[  OK  ] Reached target Local File Systems.
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Journal Service...
[  OK  ] Finished Tell Plymouth To Write Out Runtime Data.
[  OK  ] Started Journal Service.
         Starting Create Volatile Files and Directories...
[  OK  ] Finished Create Volatile Files and Directories.
         Starting Bind mount for /etc/NetworkManager/conf.d...
         Starting Bind mount for /e…NetworkManager/dispatcher.d...
         Starting Bind mount for /e…kManager/system-connections...
         Starting Bind mount for /etc/balena-supervisor...
         Starting Bind mount for /etc/docker...
         Starting Bind mount for /etc/hostname...
         Starting Bind mount for /etc/openvpn...
         Starting Bind mount for /etc/ssh/hostkeys...
         Starting Bind mount for /etc/udev/rules.d...
         Starting Bind mount for /home/root/.docker...
         Starting Bind mount for /home/root/.rnd...
         Starting Bind mount for /home/root/.ssh...
         Starting Bind mount for /u…hare/ca-certificates/balena...
         Starting Bind mount for /var/lib/NetworkManager...
         Starting Bind mount for /var/lib/bluetooth...
         Starting Bind mount for /var/lib/chrony...
         Starting Bind mount for /var/lib/systemd...
         Starting Record System Boot/Shutdown in UTMP...
[  OK  ] Finished Bind mount for /etc/NetworkManager/conf.d.
[  OK  ] Finished Bind mount for /etc/NetworkManager/dispatcher.d.
[  OK  ] Finished Bind mount for /e…orkManager/system-connections.
[  OK  ] Finished Bind mount for /etc/balena-supervisor.
[  OK  ] Finished Bind mount for /etc/docker.
[  OK  ] Finished Bind mount for /etc/hostname.
[  OK  ] Finished Bind mount for /etc/openvpn.
[  OK  ] Finished Bind mount for /etc/ssh/hostkeys.
[  OK  ] Finished Bind mount for /etc/udev/rules.d.
[  OK  ] Finished Bind mount for /home/root/.docker.
[  OK  ] Finished Bind mount for /home/root/.rnd.
[  OK  ] Finished Bind mount for /home/root/.ssh.
[  OK  ] Finished Bind mount for /u…/share/ca-certificates/balena.
[  OK  ] Finished Bind mount for /var/lib/NetworkManager.
[  OK  ] Finished Bind mount for /var/lib/bluetooth.
[  OK  ] Finished Bind mount for /var/lib/chrony.
[  OK  ] Finished Bind mount for /var/lib/systemd.
         Starting Load/Save Random Seed...
         Starting Rule-based Manage…for Device Events and Files...
[  OK  ] Finished Load/Save Random Seed.
[  OK  ] Finished Record System Boot/Shutdown in UTMP.
[  OK  ] Started Rule-based Manager for Device Events and Files.
         Starting Show Plymouth Boot Screen...
[   19.274055] k3-m4-rproc 5000000.m4fss: configured M4 for remoteproc mode
[   19.301257] remoteproc remoteproc0: request_firmware failed: -2
[   19.327540] platform 78000000.r5f: could not request atcm region for resource
[   19.334850] platform 78000000.r5f: failed to get internal memories, ret = -16
[   19.342181] k3_r5_rproc bus@f0000:bus@b00000:r5fss@78000000: k3_r5_core_of_init failed, ret = -16
[   19.351226] k3_r5_rproc bus@f0000:bus@b00000:r5fss@78000000: k3_r5_cluster_of_init failed, ret = -16
[   19.424280] davinci-mcasp 2b10000.mcasp: IRQ common not found
[   20.389047] hub 2-0:1.0: config failed, hub doesn't have any ports! (err -19)
[   41.334066] wl1271_sdio mmc2:0001:2: sdio write failed (-110)

After the last error message, the system reboots.
Any ideas what might be going on here ?

Thanks @perezmeyer - which discord server/channel should I try ?
(btw, I applied your bb-append change to get the u-boot-ti-staging sources from the beagleboard.org gitlab repo, but the failure mode is the same)

@delhiryder beagleboard.org in there you will see a beagleplay channel

@perezmeyer Quick update: After applying patches to the linux-bb.org, u-boot-ti-staging **and linux-firmware recipes, based upon suggestions from the good folks at the BeaglePlay channel on the Beagleboard discord server, I was still seeing the same errors and failures. Thankfully, someone thought that it may be a brownout/undervoltage issue, and suggested a power supply with more wattage. I ordered an official Raspberry Pi4 power supply, and the reboot problem has gone away.
Going to be pushing some more changes here (related to updated recipes and the patch to the DISTRO_BOOTCMD.

@delhiryder You wrote:

90f108b Checkpoint: Changed the linux-bb.org, linux-firmware and u-boot-ti-staging tags (to try and get rid of some errors). Yocto build is failing, but should be (relatively) easy to fix.

Is it perhaps failing like in https://github.com/balena-os/balena-beaglebone/pull/586#issuecomment-1747074441 ?

@perezmeyer I think I got past the latest (yocto) build error. I am now trying to get the following warning/errors resolved:
[  367.720466] wl1271_sdio mmc2:0001:2: sdio write failed (-110)
[  376.982472] wl1271_sdio mmc2:0001:2: sdio write failed (-110)
[  386.232489] wl1271_sdio mmc2:0001:2: sdio write failed (-110)
[  386.897179] wlcore: ERROR firmware boot failed despite 3 retries

These appear to settle down after about 400 seconds.

Excellent! Remember I am not part of the Balena stuff, but ping me if I can be of any help.

Be sure to rebase master in your branch. The beagleBone ai64 stuff is (almost all) there.


adding tech stack badges in readme

i would like to add tech stack badges and shields in readme . it makes the readme look more pretty and give better information about the technologies used.
please assign me this issue as gssoc contribution
example:

kindly follow the template and propose your issue
Please do follow the project readme template


Splash screen

Ref: Issue #11
This Installs react-native-splash-screen(https://github.com/crazycodeboy/react-native-splash-screen) while creating a new project with ignite new command by installing the package and patching a pre-configured diff that includes example splash images and a bunch of changes.
How it looks:

- iOS

- Android

@kevinvangelder It was from the initial idea of these two:

Splash screen should be loaded, as soon as possible, before the bundle is loaded, which needs to be handled on native level for both iOS and Android. It requires changes on project files and configurations in /ios and /android directory structure that we don't include in the boilerplate.
From the convo with @ryanlntn, the best practice to avoid the white flicker is to use react-native-splash-screen. (White  flicker issue: https://github.com/facebook/react-native/issues/1402)


Tag API Test Cases for Multi-Viewer

New Test Cases for TAG APIs for Multi-Viewer
Clearly describe the problem and solution
Issue: The test cases for adding/removing Tags do not consider Multi-viewer
Solution: New  test cases are added that add/remove tags using Multi-viewer
Relevant issue number(s) if applicable
Did you run npm run lint from the viewer or parliament directory (whichever you are making changes to) and correct any errors
Yes
Did you Ensure that all tests still pass by navigating to the tests directory and running ./tests.pl --viewer
Yes
License
I confirm that this contribution is made under an Apache 2.0 license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@awick , can you please review the PR when time permits and provide your suggestion. The changes are as follows:

Tag API test cases for Multi-viewer. The test case were failing due to the _update endpoint of the MultiES
Fixed the test cases by making changes in the MultiES _update endpoint.

Looks good, please change all the tags to unique values, even though you are adding/removing, it will make future debugging easier if there is a problem. Maybe add a M up front, MTAGTEST1 etc

Looks good, please change all the tags to unique values, even though you are adding/removing, it will make future debugging easier if there is a problem. Maybe add a M up front, MTAGTEST1 etc

Thank you for the suggestions. Made the change accordingly.


Update to RC2?

Will there be an update to RC2 ? :) Cause I havn't seen any working service discovery for asp.net core RC2 yet.

@Tazer There are RC2 bits on the dev branch... I'll be merging those bits into master in the near future....
You can look at the Fortune Teller sample in the dev branch to see how to use it standalone ... i.e. on your desktop .... or as an app pushed to CloudFoundry.
https://github.com/SteelToeOSS/Samples/tree/dev/Discovery
Dave

Noticed it :) that's way I closed the item.
Thanks for an reply anyway
On Fri, 17 Jun 2016, 18:08 Dave Tillman<EMAIL_ADDRESS>wrote:

@Tazer https://github.com/Tazer There are RC2 bits on the dev branch...
I'll be merging those bits into master in the near future....
You can look at the Fortune Teller sample in the dev branch to see how to
use it standalone ... i.e. on your desktop .... or as an app pushed to
CloudFoundry.
https://github.com/SteelToeOSS/Samples/tree/dev/Discovery
Dave
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SteelToeOSS/Discovery/issues/1#issuecomment-226811352,
or mute the thread
https://github.com/notifications/unsubscribe/AAIGWkfp4z7iyl8DDs-Oc9FErNlwMGzHks5qMsZkgaJpZM4I4O0H
.

Hey @Tazer! I love that you're interested in our project. I was curious how you found out about it, and what's the driving factor in your interest. Thanks for any info!


scrolling needs to be lowered on "scheduled downloads" tab

Hello,
The scrolling function is really hard to use, please lower the ticks. thanks

Closed with commit fb781c56d915871feb3561b2fc4f9a42046327af


The shouldAdvanceTime option seems to cause Jest Test environment to clear during the test

The shouldAdvanceTime option seems to cause Jest Test environment to clear during the test.

FakeTimers version : 9.1.2 as a dependency of<EMAIL_ADDRESS>Environment : MacOS, Jest
Example URL : None (Testing in Jest)
Other libraries you are using: postgres.js

What did you expect to happen?
As expected, not calling jest.useFakeTimers(); causes the error ReferenceError: setImmediate is not defined when running something like sql'SELECT 1 AS one' using the postgres.js library.
Calling jest.useFakeTimers(); should set up fake timers usable by the Jest environment. We no longer get the error ReferenceError: setImmediate is not defined as expected.
However, since we don't provide a shouldAdvanceTime option, the default is false. Timers don't run so calling something like sql'SELECT 1 AS one' never completes as the postgres.js library relies on these timers (the test times out). This is my guess.
We expect passing a value for the option of { shouldAdvanceTime: true }, enabling the timer tick option, will cause the timers to work as expected by the library allowing the query to complete.
What actually happens
Passing shouldAdvanceTime as a config option to function install(config) causes the ReferenceError: setImmediate is not defined to throw again.
How to reproduce
I've debugged down to this section of code: https://github.com/sinonjs/fake-timers/blob/main/src/fake-timers-src.js#L1683-L1686 . When those lines of code are enabled and jest.useFakeTimers({ shouldAdvanceTime: true }); is called (or even if we hard code the value within the fake-timers code) then the error ReferenceError: setImmediate is not defined shows up.
If we comment out those lines of code, the ReferenceError: setImmediate is not defined goes away but the test eventually times out.
It looks like, when those lines of code are enabled, somehow the Jest framework ends up tearing down the environment early: causing jest.useRealTimers() to be called before the test completes.

can you put together a reproduction? setImmediate is only available in Node env, so I assume the issue is simply that you are using JSDOM env. Hard to say without a reproduction, tho 🙂

Yeah, I have been looking at this for the last ten minutes and think it comes down to something related to what @SimenB says. Hard to look into without a repro.
If you look for setImmediatePresent in the code, you will see that that timer is only ever added if it is present in the environment, advancing timers or not: https://github.com/sinonjs/fake-timers/blob/main/src/fake-timers-src.js#L998.
So it might be something related to what _global refers to that causes this. Maybe _global is bound to different things due to something I cannot immediately see (related to JSDom and async behavior)?

can you put together a reproduction? setImmediate is only available in Node env, so I assume the issue is simply that you are using JSDOM env. Hard to say without a reproduction, tho 🙂

yep. I updated the jest.config.ts and things started to work.
import type {
  Config,
} from 'jest';

const integrationTestConfig: Config = {
  preset: 'ts-jest',
  testEnvironment: 'node',
  // testEnvironment: 'jsdom', -- results in the error
  testMatch: [
    '**/*.integration.spec.ts',
  ],
  collectCoverageFrom: [
    './packages/**/src/*.ts',
  ],
};

export default integrationTestConfig;

Thank you!

Thank you again!


Jenkins homepage is ok for CONFIGURE_JENKINS without READ

A user should be able to configure only, without READ permission, so a CONFIGURE_JENKINS should be able to show the Jenkins homepage without needing READ.

We let permissions as it is, and Overall/Read will be needed for the CONFIGURE user.


Give Codacy a bit of love

Given that Codacy is the centralized static analysis tool, we should keep it as clean as possible.
Let's spend some time deciding what inspections do we want on Codacy.

Considering this closed via https://github.com/apereo/cas/pull/2310 for now


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app/src/atom.js:55:11)
StatusBarSummaryView.render (/Users/andrei/.atom/packages/linter/lib/statusbar-summary-view.coffee:11:21)

Closing as dupe of #343.


Library does not work without SSR

As surfaced in #19, it appears that this library does not work correctly without ssr enabled. This is very odd and will bear some investigating. I have asked for help in the solid discord server, hopefully they can help me get to the bottom of this.
Reproduction here.
EDIT: additional reproduction without solid-start

@OmarGoubail tagging you since you encountered this issue.

@OmarGoubail tagging you since you encountered this issue.

Will try to investigate also, will let you know if I find anything.

Also created an issue here.

I spend sometime trying to to figure out what's going on here are my findings so far, I basically created a new project using vite in the library workspace to test with and I tested with the component from the discussion I opened
import { Component, createSignal, For, onMount, createEffect } from 'solid-js';
import { LexicalComposer, PlainTextPlugin, ContentEditable, HistoryPlugin } from 'lexical-solid';
import { OnChangePlugin } from 'lexical-solid/LexicalOnChangePlugin';
import { useLexicalComposerContext } from 'lexical-solid/LexicalComposerContext';
import { $getRoot, EditorState } from 'lexical';

const theme = {};

function onError(error: Error) {
  console.error('Lexical error:', error);
}

const Editor: Component = () => {
  const [editor] = useLexicalComposerContext();
  const [editorContent, setEditorContent] = createSignal<string>('');
  const [debugLog, setDebugLog] = createSignal<string[]>([]);

  const addToDebugLog = (message: string) => {
    setDebugLog((prev) => [...prev, `${new Date().toISOString()}: ${message}`]);
    console.log(message);
  };

  const printEditorContent = () => {
    editor.getEditorState().read(() => {
      const root = $getRoot();
      const content = root.getTextContent();
      setEditorContent(content);
      addToDebugLog(`Editor content: "${content}"`);
    });
  };

  const onEditorChange = (editorState: EditorState) => {
    editorState.read(() => {
      const root = $getRoot();
      const content = root.getTextContent();
      setEditorContent(content);
      addToDebugLog(`Editor state changed. Content: "${content}"`);
    });
  };

  createEffect(() => {
    return editor.registerUpdateListener(({editorState}) => {
      console.log('App: Editor updated', editorState.toJSON());
    });
  });

  createEffect(() => {
    const rootElement = editor.getRootElement();
    console.log('App: Editor root element', rootElement);
  });

  createEffect(() => {
    const rootElement = editor.getRootElement();
    if (rootElement) {
      console.log('App: Root element attributes', rootElement.getAttributeNames());
      console.log('App: Root element data-lexical-editor', rootElement.getAttribute('data-lexical-editor'));
    }
  });

  onMount(() => {
    addToDebugLog('Editor component mounted');
    printEditorContent();
  });

  return (
    <>
      <PlainTextPlugin
        contentEditable={<ContentEditable />}
        placeholder={
Enter some text...
}
        errorBoundary={(error) => {
          addToDebugLog(`ErrorBoundary: ${error.toString()}`);
          return
Error: {error.toString()}
;
        }}
      />
      <HistoryPlugin delay={2000} />
      <OnChangePlugin onChange={onEditorChange} />
      <button onClick={printEditorContent}>Print Editor Content</button>

Current Editor Content:

{editorContent()}

Debug Log:

          <For each={debugLog()}>
            {(log) =>
{log}
}
          </For>

    </>
  );
};

const App: Component = () => {
  const initialConfig = {
    namespace: 'MyEditor',
    theme,
    onError,
  };

  onMount(() => {
    console.log('App component mounted');
  });

  return (

Lexical Solid Debug

      <LexicalComposer initialConfig={initialConfig}>
        <Editor />
      </LexicalComposer>

  );
};

export default App;

Editor Initialization: The LexicalComposer component is initializing correctly, but there are issues when it comes to rendering child components ( I think ).
Component Mounting: The App and LexicalComposer components are mounting successfully, but the error occurs before the editor's root element can be set.
Editor State: The initial editor state is being created with a default paragraph, but this state isn't being properly passed to child components.

Attempted Solutions:

Tried wrapping the editor creation in an onMount effect to ensure it's only created after the component is mounted.
Attempted to use a signal for the editor state in the LexicalComposer.

Will spend more time on this later but I think I am going to try using lexical directly next to understand more about the lexical lifecycle and how it can fit in with Solid.

Thanks. I'll look at this in more detail later.
It was suggested to me that I try start from scratch using just lexical and solid, package that, and see if I can reproduce the issue.

Yes, I came to this conclusion also.

I have lexical-solid running in a Solid JS / Vite project where SSR isn't present.
You need to manually call LexicalEditor.prototype.setRootElement(el: HTMLElement) inside Solid's onMount()
onMount(() => {
  store.editor.setRootElement(elementRef)
})

This is because Lexical checks an elements el.documentOwner.defaultView which is null for refs until Solid's onMount lifecycle.

@arksouthern thanks for reporting your findings (I also see your reddit post). I'll look into what code needs to changed for this and release a fix soon.

Closed by f6525b6ca1a397a0e4c3bbef579e9b5ebdfdd628 and released as v0.12.1.
Thank you @OmarGoubail and @arksouthern for reporting and investigating!


Cancle a Running Pipeline update status as failed

I expect the status to be cancled after a cancle, but when already running it shows failed

I can submit an PR based on the changes suggested in #1430


add support for self-managed app search

replaces https://github.com/logstash-plugins/logstash-output-appsearch/pull/9
fixes #4

@peterskim12 hi! I've performed the changes and tested both locally against self managed 0.1.0-beta5 and saas app search instances. what do you think?

my reason to expect only part of the URL on the url parameter is that when you use on prem app search the UI gives you the endpoint to use and has a "copy" url button, that only copies http://localhost:port, it doesn't copy the rest of the url.
I also added path more as future proof setting, so that folks can change from /api/as/v1 to something else if necessary.
I'll improve the error handling so that using host + path returns an error.

hi @yaauie, can you give me a final lgtm? I think all concerns have been addressed, thanks for the review 👍


pulpMd is eating _ in tables and files

If I get this input file to pulpMd
Name | Type | Description
---- | ---- | -----------
credit_transaction_number | string | TODO: add comment.

credit_transaction_number

I get this as output
| Name   | Type   | Description        |
|--------|--------|--------------------|
| number | string | TODO: add comment. |

credittransactionnumber

This is not correct by any definition. :)

cc @favadi

I tracked it down to github.com/Kunde21/markdownfmt , which does not correctly render emphasis nodes; and indeed, even the texts **transaction** or _transaction_ or  *transaction* are all rendered incorrectly.
credit_transaction_number both can and doesn't have to be interpreted as credit<i>transaction</i>number, I guess depending on markdown definition.
And replacing credit_transaction_number by credit\_transaction\_number indeed stops this from happening.

Closing this issue, opening new one in markdownfmt


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 10:57:29 on 2023.06.10
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 1, errors out: 0
Original problem ID: 28495
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=28495

Problem has been resolved in 3m 4s at 11:00:33 on 2023.06.10
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 28495


The container app is not focused by clicking "Click to view resource" in Activity Log window after creating it

OS: All
Build Version: 20220706.3
Regression: Not a regression
Repro Steps:

Create a container app.
Click "Click to view resource" in Activity Log window.
Check whether the container app is focused.

Expect:
The container app is focused.
Actual:
The container app is not focused.

This might be happening because reveal resource only looks for top level resource nodes. But since container apps are under container environments, it isn't able to find and reveal it.


Configuration format rework

This is the massive PR you've all been waiting for!
We're replacing XML as the configuration language with a custom, s-expression based configuration syntax named yuck.
yuck puts a lot of focus on providing clean, readable and useful error messages where possible, and aims to at some point allow for the implementation of advanced development-tooling such as a language server. To achieve that, eww is now split up into several crates:

yuck: the main configuration syntax parser, API to deal with parsed ASTs and the datastructures that represent a basic interpreted eww configuration file.
simplexpr: (weird name, I don't care) The parser and evaluator for the inline infix expressions eww allows for. These where previously possible to use in {} within string literals. This crate provides not only the AST structure and evaluation logic, but also the dynval value, which is a string-value that may be interpreted as a value of other types depending on where it is used. DynVal is thus the main primitive value type used for typejuggling, and replaces PrimVal from the old eww codebase.
eww_shared_util: a small crate that provides types and functions used across some of the other crates. Mainly, it provides the Span type used throughout the codebase.
eww: The core eww codebase. This contains all of the server-logic, GTK related code, as well as anything else not directly related to the configuration file.

This PR is still work in progress for several reasons:

Error handling could still take a good bit of improvement. Not only do I still see multiple places where better diagnostics could be provided, but also I still see some issues with how the code is structured right now. As this is not a "breaking" change in any way, I might merge this PR before all of those error-handling related tasks are fully done - I don't want to block the syntax migration longer than necessary just to pursue some form of "PR-purity" or whatever.
The documentation needs to be adjusted - this is not yet done at all. @manderio has agreed to help me out here
The examples need to be migrated to the new syntax
A release / tag before the rework should be made, so people that don't want to migrate right away don't have to search through hundrets of commits to find the version prior to the rework
I want to find an alternative syntax for string literals that doesn't conflict with " in shell-scripts - this shouldn't be hard, I just don't know what syntax to choose yet

However - this is a bold statement, but:
It should be usable. There might still be dealbreaking bugs, I haven't tested everything - if there are, please leave a comment here.
If you want to be the early adopter, feel free to give this a try! The syntax is (most likely, I'll not rule it out 100%, but it's very unlikely) not gonna go through any big changes - if any at all, those will be minor changes of keywords or some additions to syntax. So if your stuff that you do now works, it'll most likely continue working once this is fully finished!
Have fun!
PS: Note that this PR may get some force pushes still, as I do want to clean up the commit history - so maybe don't build big branches on top of this right now
Notes / TODOs

[x] Allow comments in simplexprs
[x] Include shell error message in script-execution failures, and mention "Failed to execute script" in the error message explicitly

10/10 commit messages ngl

This is great, after very little time spent on rewriting my bar in yuck it runs impressively well.
How would you like to handle issues though? Would you like to have them in the comments here, or opened a issue with [config format rework][bug] in the title?
So far I have manly two things observed: absolute sizes in geometry are not working and one issue with a widget only holding a box with a literal not initialising until after the first reload.
All in all great work!!!

I think it makes sense to keep any issues with the new config as comments here until it's merged.
Could you share your config where you are encountering these bugs?

This are the relevant snippets of my yuck config (I believe I can safely omit the other windows and widgets, right?):
(defwidget workspaces []
    (box :class "workspaces" :orientation "h" :space-evenly true :halign "start"
     (literal :content {wm-tags})))

(deflisten wm-tags "scripts/getleftwmstate_yuck")

(defwindow tags
           :screen 0
           :focusable true
           :windowtype "dock"
           :geometry (geometry :x "41%" :y "8px" :width "19%" :height "34px")
           :reserve (struts :side "top" :distance "55px")
  (workspaces))

This is the GTK-Waring I get immediately after launching eww and opening the tags window
~ >>> eww logs

(eww:2085618): Gtk-WARNING **: 07:44:52.617: Negative content width -25 (allocation 1, extents 13x13) while allocating gadget (node button, owner GtkButton)

This is the output of the getleftwmstate_yuck script (each WM update outputs a new line):
 (button :class "ws-button-busy" :onclick "wmctrl -s 0" ``) (button :class "ws-button-busy" :onclick "wmctrl -s 1" ``) (button :class "ws-button-busy" :onclick "wmctrl -s 2" ``) (button :class "ws-button-mine" :onclick "wmctrl -s 3" ``) (button :class "ws-button-busy" :onclick "wmctrl -s 4" `ﲾ`) (button :class "ws-button" :onclick "wmctrl -s 5" `·`) (button :class "ws-button" :onclick "wmctrl -s 6" `·`) (button :class "ws-button" :onclick "wmctrl -s 7" `·`) (button :class "ws-button" :onclick "wmctrl -s 8" `·`))

Regarding the mentioned 'geometry bug' that was just me missing some colons before the 'y', 'width' and 'height'. So this might be nice to have an error or warning if there are keywords are missing colons.

about your use of the literal:
I'm assuming you're getting an error along the lines of

if that is actually your output - read the error :eyes:
(deflisten ...) is indeed supposed to monitor the output of a command, not a file. the example was broken here - it should be tail -f path for the desired effect.
I added some improved error messages regarding the geometry error you made.

Ooops, my bad, I copy-pasted the wrong line for the literal. This is the actual output of the script:
(box :orientation "h" :class "workspaces" :space-evenly "true" :halign "center" (button :class "ws-button-busy" :onclick "wmctrl -s 0" ``) (button :class "ws-button-busy" :onclick "wmctrl -s 1" ``) (button :class "ws-button-busy" :onclick "wmctrl -s 2" ``) (button :class "ws-button-mine" :onclick "wmctrl -s 3" ``) (button :class "ws-button-busy" :onclick "wmctrl -s 4" `ﲾ`) (button :class "ws-button" :onclick "wmctrl -s 5" `·`) (button :class "ws-button" :onclick "wmctrl -s 6" `·`) (button :class "ws-button" :onclick "wmctrl -s 7" `·`) (button :class "ws-button" :onclick "wmctrl -s 8" `·`))

Your error messages are so good, really as helpful as actual rust compiler errors!
I guess except buttons not being clickable everything works now as it should. This is really great!

@VuiMuich The buttons should be clickable, at least they are for me :eyes: can you verify that it's not just the wmctrl thing not working or sth?

wmctrl from the terminal works fine.
But I just realized it might actually be leftwm handling windows of type "dock" a bit odd.

Whie you are at the example: may I suggest to actually use 'minute' instead of 'min' I am not sure if related, but I got a view panics every now and then but since I changed it they are gone. (Unfortunatelly I fixed a lot of other things along changing this so I can't be sure it was this causing panics, but I figured it might be at least for 'the user' better to not confuse 'min' as in 'minimal' and minute...)

@VuiMuich "focusable" doesn't even exist on X anymore here, it's been replaced by the windowtype option and wm-ignore if you need it
where do you mean it should use minute? 🤔

@VuiMuich "focusable" doesn't even exist on X anymore here, it's been replaced by the windowtype option and wm-ignore if you need it

Thanks for the hint. Something came up shortly IRL so, probably won't have a further look at it before the weekend.

where do you mean it should use minute?

in eww.yuck:
(defpoll month :interval "10h" "date '+%b'")
(defpoll minute :interval "10s" "date '+%M'")
(defpoll hour :interval "1m" "date '+%H'")

The battery-remaining variable is empty according to eww state

Just a small side note: Eww has that variable built in https://elkowar.github.io/eww/magic-vars.html#eww_battery
But I'm not sure if it works with the new configuration format (yet).

Just as I started to test steps needed to reproduce the problem with buttons they suddenly just worked. I have no real idea what changed, as I haven't noticed anything related in the latest commits.
Now there is just one more thing: As reported in #123 and #193 GTK sometimes has it's own opinion on the height of windows. Right now though my window for the workspace-buttons has the config defined height of 34px and only grows to the GTK-determined height of 44px after the first reload. This possibly is related to this window only containing content from a literal I guess.
An obvious workaround of course is to set window height in the config to the 44px GTK is going to set anyways...

mostly a note to self that error messages like these could take some improvement

The battery-remaining variable is empty according to eww state

Just a small side note: Eww has that variable built in https://elkowar.github.io/eww/magic-vars.html#eww_battery
But I'm not sure if it works with the new configuration format (yet).

I tried this, but (this is probably new, right?) it returns a literal: {"BAT0": { "status": "Discharging", "capacity": 41 }, "total_avg": 41.1} but I have no idea how to access the fields.

The battery-remaining variable is empty according to eww state

Just a small side note: Eww has that variable built in https://elkowar.github.io/eww/magic-vars.html#eww_battery
But I'm not sure if it works with the new configuration format (yet).

I tried this, but (this is probably new, right?) it returns a literal: {"BAT0": { "status": "Discharging", "capacity": 41 }, "total_avg": 41.1} but I have no idea how to access the fields.

It's not new. you can do '${EWW_BATTERY["BAT0"].status}' for example

It's not new. you can do '${EWW_BATTERY["BAT0"].status}' for example

Ohh, thanks, didn't know that $ is needed.

another small issue: when a monitor is configured that doesn't exist, things like 100% for window dimensions break, without any warning. stuff otherwise seems to work. a good warning would be good here

A pr of 116 commits...
Truly astounding

note: checks failing because of https://github.com/rust-lang/rust/issues/88043 - nightly moment

Awesome! :tada:
Congrats on this milestone achievment! :partying_face:


Adding support for the sparse simulator (#1338)

e2e build failure is expected, since this feature requires updates to the build logic as well. The updates on all feature branches including the updates to the build logic has been confirmed separately via the release pipeline.


Rework abstraction creation to work with LSHIFT

Close, because I have revamped the program structure (id_scheme).


[BUG] res is not a function

The docs mention that the res function can be used to get data from the response body. However it is an object, not a function, in scripting and vars.

After printing the stringified object I can see that res is the object described here, and it cannot be called like a function.
I'm using v1.1.1 on Windows 10.

@joe-gre Totally agree that the docs you linked are miss-leading. In the mean-time, reference the Javascript docs for accessing the response data.

Thanks, yeah I'm currently using res.getBody().

Closing this issue as it could not be recreated in the latest version of Bruno v1.20.0


fix: improve correctness of neovim version checking

Checking only the minor version is not technically correct for this check. It probably won't be a big deal because 1.0 is quite a bit away, but this does protect against this.

Thanks for the PR!


Releasing Milestone 1.8

I think a release is overdue.  I'm currently working on a release as well as documenting how I do a release.  Pull request to follow for release preparation.  This pull request will be closed when the release is completed.
This covers all pull requests merged since PR #47.

TODO

Update CHANGELOG.md
Write a RELEASE.md document.
Open a PR merging points 1 and 2.
Perform the release based on documentation in RELEASE.md.

This has been released.  It will not show up in Jenkins central for at least 8 hours.  I'll close this issue when I've verified the release shows up and upgrading from Jenkins Central is good.

From the plugin release F.A.Q. in case anybody is wondering.

The release shows up in the release repository.
http://updates.jenkins-ci.org/update-center.json is updated every 6 hours, so there's some delay before the new version shows up in the update center.
The last infrastructure build is 1152 which ran on May 17, 2015 11:41:00 AM.  So we've got at least 3 hours or more before the next run.

It was fun digging through and learning how it worked.

Interesting, here's the source for the update site generator.

I have confirmed that the release is available and it works.


Capture menu missing in admin

The menu to do captures on customer payments is missing inte the admin section for orders!
We used this plugin before omg another site and there we had a menu that allowed us to capture incoming payments.
"PayEx Payment Actions" but on this new site this section is missing?

@kemikal hi, which version of the plugin do you use?


add SupplementaryFeatures options (such as public holidays)

The solution does currently not allow to add SupplementaryFeatures such as public holidays.
It overwrites InputDataConfig when creating the Predictor without taking into account any SupplementaryFeatures passed in the forecast-default config file.

Thanks for your feedback and feature request @pasard ! I can confirm that this is the current behavior of the solution. We've put this into our backlog and will consider how to add this feature.

This is now fixed in version 1.3.0!


Update .cargo/config section of writing-shader-crates.md

Resolves #157
Improves the .cargo/config section because the instruction weren't quite correct.

Thanks so much! 🍻🍻


Problems creating a wrapper cookbook around chef-prometheus

Since the default recipe runs the template command and accumulator among other things, there is no way to include_recipe "prometheus" in a wrapper cookbook that wants to override attributes or do the work of figuring out what prometheus jobs should be set up.
Am I missing something?

You can use the job_config_template_name and job_config_cookbook_name attributes to override the template used to use the one in your wrapper cookbook.

How would I use the prometheus_job LWRP in that case? I can't call the LWRP without include_recipe "prometheus" which will have already generated the prometheus.yaml

As long as your wrapper cookbook depends on the prometheus cookbook in the metadata.rb, you should be able to use the LWRP before you include the recipe I think.


Input Parameter for Area Of Influence tool

The inputs for walk/drive time now are in seconds. This means that a user would have to know, or rather, google, how many seconds are in 15 minutes and so on. Would it be possible to make the input be minutes instead? Might be easier for users to understand.

dupe! Thanks!


Revert volcano changes

What this PR does / why we need it:
Remove all related codes for batch job feature, need take special care on modified files.
Special notes for your reviewer:
Release note:

@k82cn

/lgtm
/approve

@TommyLike , please help to continue the revert work of that.

@k82cn  There are two testcases are skipped due to uncertain root cause, would like to have this merged first and then track&fix them respectively

/lgtm


Can't lookup already confirmed transaction

The graphql query:
query GetTx {
  node_transaction(
    where: {
      transaction: {
        hash: {
          _eq: "\\x45fdd101bce6b63c1c128f0fcbec111d93f304a3e09db4706229d60a417109c6"
        }
      }
    }
  ) {
    transaction {
      hash
    }
  }
}

returns:
{
  "data": {
    "node_transaction": []
  }
}

even though the transaction has been confirmed . Maybe because it's the coinbase?

@EDIT1: It's possible to find this transaction by looking up the block it was included in:
query GetTxFromBlock {
  node_block(
    where: {
      block: {
        height: {
          _eq: 784836
        }
      }
    }
  ) {
    block {
      hash
      height

      transactions(
        where: {
          transaction: {
            hash: {
              _eq: "\\x45fdd101bce6b63c1c128f0fcbec111d93f304a3e09db4706229d60a417109c6"
            }
          }
        }
      ) {
        transaction {
          hash
        }
      }
    }
  }
}

returns:
{
  "data": {
    "node_block": [
      {
        "block": {
          "hash": "\\x000000000000000003ab734df9176286ea22513052eb4ee1e239cfa6249ee514",
          "height": "784836",
          "transactions": [
            {
              "transaction": {
                "hash": "\\x45fdd101bce6b63c1c128f0fcbec111d93f304a3e09db4706229d60a417109c6"
              }
            }
          ]
        }
      }
    ]
  }
}

@EDIT2: The following query also works:
query GetTx {
  transaction(
    where: {
      hash: {
        _eq: "\\x45fdd101bce6b63c1c128f0fcbec111d93f304a3e09db4706229d60a417109c6"
      }
    }
  ) {
    hash
  }
}

Thanks for opening an issue. It looks like you got this figured out?
I know the flow of transactions from node_transaction to block_transaction (immutable) + node_block isn't very obvious – Chaingraph probably needs some better guides to introduce how the database models chain activity. This data model sets us up well for long-term scaling considerations though (avoiding some duplication and enabling time-based partitioning).
node_transaction is essentially the observed "mempool" for each connected node. The transactions then get organized into block_transactions, which are immutable even when particular nodes switch between accepted chain tips. Only node_block is changed when a particular node changes its mind about the state of the network, and the matching _history tables record changes to the various temporary tables.


Accessible view buttons are always enabled even if can not cycle further

Testing #229460
In the Github Copilot walkthrough accessible view. It is not possible to move further than 5 levels down as there are 5 steps. I can however continue pressing on the up and down arrows, as they are always enabled.

@meganrogge is there a way for the content providers to enable/disable the button status?

no, this would be tricky to do because providers iterate through results one by one vs providing all upfront. pretty sure there's an issue open for this already, but fine with me to track this here.
The accessibility solution for this that is implemented in some places (chat responses for ex) is to alert with the index and total count when navigating between them.

I don't think I'll get to this


When thousand separator is change to be a dot, it allows only to input number < 10,000

Please use this fiddle:
https://jsfiddle.net/rsj41ny7
Try to type five 9's (99999). You will see the problem,
Regards
Jaime

Add: { numeralDecimalMark: ',' }
https://jsfiddle.net/k2n18vfL/

Thanks. So, even when the number is integer, decimal mark should be specified. Good to know.


Update the install rules to latest.

They have fixes that should work on freeBSD, i.e. they
might start working on MacOS.
Signed-off-by: Henner Zeller<EMAIL_ADDRESS>

Codecov Report

Merging #1396 (fd6fa92) into master (a1b5473) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1396   +/-   ##
=======================================
  Coverage   92.90%   92.90%
=======================================
  Files         340      340
  Lines       23832    23832
=======================================
  Hits        22141    22141
  Misses       1691     1691

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


SlackClient added

SlackClient added so that breakout signals can be shared via Slack

Nice addition, I'd use this! Left a couple of comments about where to put user configurable details.

Will try to find time to make the changes so that they are properly reflected in the secrets.json file


Explorer selelect file loses focus when a file added / removed from folder

In the explorer tree, I was trying to add a .gitignore file. At the same time, a process was running which was adding / deleting files in the same folder. Each time a file was added / removed the explorer tree lost focus. So it was impossible to add the new file, since before I could "right click", "new file" then enter the new name a temp file addition / deletion took focus away and the new file vanished.

I don't think this is a duplicate - it may be that a fix for #71315 also fixes this though.


Outputflag

What this PR does / why we need it:
Adds output flag to the path to generate the base files in the repo's directory

Special notes for your reviewer:
Release note:

everything LGTM


Add an update_theming() to all elements

A catch all way to support dynamic-in-code theming for those who want to alter the way elements look from within the code rather than via a theme file.
The idea is to follow the nested dictionary structure of the .json files we currently use for theming but just pass those theming blocks directly an element rather than the element having to go fetch them from the theme file.
Proposed interface
Updating a single colour for a button:
button.update_theming({'colours': {'normal_bg': '#FF0000'}})

Implementation
I think it's likely we can refactor the current rebuild_from_changed_theme_data() functions to branch based on going to the theme file or reacting to a passed in dictionary of theming blocks.
Issues
This won't work smoothly together with dynamic updating of UI themes from editing the theme file, but I doubt they are features that really have overlapping use cases.
Editing theme files and having that show up in a live demo is for programmers/designers tweaking UI appearance parameters, whereas dynamically changing an elements theming is probably for some in-game effect when you don't want to make a new element for whatever reason.
My original design anticipated that users would be a lot more comfortable destroying and recreating elements when they wanted them to change, but it seems many users want to keep the same element objects around and change everything about them them with function calls instead.

Seems like a good idea -- separating data from whether it resides in a file or is provided dynamically is definitely best practice.
Additional opportunity here -- when doing the scrollbar work, I noticed we have a lot of duplicated theming code (setting up the same parameters for borders, or text), and it would be nice to factor those out so that standard theme items are set in one place. Doing this cleanly is probably a combination of object hierarchy -- subclasses setting their specific values then calling super() to add standard values -- and possibly separate methods for, say, text theming which not all classes use.
Also agree that people tend to want to change an existing element rather than recreate it. There is potentially a performance win there as well.
One other thought -- perhaps for theming (if not in general) have some flag that indicates whether we're in development or production mode, to handle stuff like updating if the theme file changes, which in production is just a waste of CPU.


Persist sorting information after deleting queue

While sorting is already persisted via URL, it would be great to persist it via LocalStorage too.
Case:

Sort queues
Enter detailed view
Delete queue
Sorting is dropped

Hello, Thanks for your input! :)
We have started to look into this!


App.use(path, ...) Does Not Mount at '//'

Router instance mounted explicitly at '//' exposes routes when path begins only with a single /:
const TestRoutes = express.Router();

TestRoutes.get('/drop/table/:table', (req, res) => {
  // drop table
  res.send(`Dropped table '${req.params.table}'`);
});

TestRoutes.get('/', sendListOfTestRoutes);

if (TEST) app.use('//', TestRoutes);

app.listen();

Expected behavior is that navigating to http://hostname/ would bypass this Router, but instead Express serves the list of test routes mounted within the router at //.

Changing mount location to /// fixes the issue, so I believe the rightmost character is being stripped if it's a /.  Fixing this could involve only stripping the character if it's immediately preceded with a valid URL character other than a /.


KYLIN-4001 Allow user-specified time format using real-time

Allow user-specified time format using real-time
I found that real-time only supports millisecond timestamp, does not support second timestamp and  Date type like '2019-01-01 11:11:11'.
I add a LongTimeParser and a DateTimeParser and page configuration
You can configure tsParser, tsPattern on the page that creates the streaming table.

for date :
{ "timestamp":"2019-04-29 11:11:11","gmv":1.1 }
tsParser=org.apache.kylin.stream.source.kafka.DateTimeParser
tsPattern=yyyy-MM-dd HH:mm:ss

for second  :
{ "timestamp":"1556618887","gmv":1.1 }
tsParser=org.apache.kylin.stream.source.kafka.LongTimeParser
tsPattern=S

for millisecond :
{ "timestamp":"1556618887000","gmv":1.1 }
tsParser=org.apache.kylin.stream.source.kafka.LongTimeParser
tsPattern=MS

Can one of the admins verify this patch?

I am really sorry, this is the first time I submitted the source code to the open source community. I skipped checkstyle, and now this version has been checked by checkstyle.xml.

Pull Request Test Coverage Report for Build 4435

20 of 49 (40.82%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 27.824%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

stream-source-kafka/src/main/java/org/apache/kylin/stream/source/kafka/LongTimeParser.java
10
14
71.43%

stream-core/src/main/java/org/apache/kylin/stream/core/source/MessageParserInfo.java
0
6
0.0%

stream-source-kafka/src/main/java/org/apache/kylin/stream/source/kafka/TimedJsonStreamParser.java
8
14
57.14%

stream-source-kafka/src/main/java/org/apache/kylin/stream/source/kafka/DateTimeParser.java
0
13
0.0%

Totals

Change from base Build 4426:
0.008%

Covered Lines:
22775

Relevant Lines:
81855

💛  - Coveralls

Codecov Report

Merging #624 into master will increase coverage by <.01%.
The diff coverage is 34.69%.

@@             Coverage Diff              @@
##             master     #624      +/-   ##
============================================
+ Coverage     25.34%   25.34%   +<.01%
- Complexity     5841     5844       +3
============================================
  Files          1379     1382       +3
  Lines         81808    81855      +47
  Branches      11465    11467       +2
============================================
+ Hits          20733    20746      +13
- Misses        59054    59084      +30
- Partials       2021     2025       +4

Impacted Files
Coverage Δ
Complexity Δ

...ache/kylin/stream/source/kafka/DateTimeParser.java
0% <0%> (ø)
0 <0> (?)

...he/kylin/stream/core/source/MessageParserInfo.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../kylin/stream/source/kafka/AbstractTimeParser.java
100% <100%> (ø)
1 <1> (?)

...lin/stream/source/kafka/TimedJsonStreamParser.java
71.76% <50%> (-4.95%)
12 <0> (ø)

...ache/kylin/stream/source/kafka/LongTimeParser.java
57.14% <57.14%> (ø)
3 <3> (?)

...he/kylin/dict/lookup/cache/RocksDBLookupTable.java
72.97% <0%> (-5.41%)
6% <0%> (-1%)

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 c04694b...e5291b4. Read the comment docs.

Hi, could you please update your commit?

Use correct git user name/ user email which can link to your github profile page
Merge your commit into two commit, one for backend change, another for front end change
Create a JIRA, describe the problem you found, how you solve it, and attach manual test screen shot
Use KYLIN-XXXX in your git commit message

Thank you so much~

could you merge all commits into 2 commits?


Create zebra-cli stub crate

Motivation

We want to own our zebra-* crates on crates.io
Solution

This is a stub crate for a binary named zebra-cli.
Review

Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?

[ ] Does it change concurrent code, unsafe code, or consensus rules?

[ ] How do you know it works? Does it have tests?

Follow Up Work

Please update Cargo.lock to make the builds and CI checks pass.

Please update Cargo.lock to make the builds and CI checks pass.

Done 👍 https://github.com/ZcashFoundation/zebra/pull/6484/commits/d4a77f954f66a3f7e5c36b535a09c2eeee47d25f

Do we also want to add a zebra-tx crate, to match zcash-tx?
I'm not sure if we'll ever have one, and it seems like a low priority, so it's ok to say "no that's not needed".

Perhaps not in this PR

Do we also want to add a zebra-tx crate, to match zcash-tx?

Could we add a command in zebra-cli or a binary in zebra-utils instead?

Do we also want to add a zebra-tx crate, to match zcash-tx?

Could we add a command in zebra-cli or a binary in zebra-utils instead?

Yeah I blew away the stub contents of the crate, which included at least one sub-command; I wouldn't mind supporting the zcash-tx behavior in zebra-cli

Do we also want to add a zebra-tx crate, to match zcash-tx?

Could we add a command in zebra-cli or a binary in zebra-utils instead?

Yeah I blew away the stub contents of the crate, which included at least one sub-command; I wouldn't mind supporting the zcash-tx behavior in zebra-cli

(I blew it away because it was just a demo I made pulling in some unified address parsing code and displaying it as a a QR code)

Do we also want to add a zebra-tx crate, to match zcash-tx?

Could we add a command in zebra-cli or a binary in zebra-utils instead?

This PR is about reserving the crate name in case we decide we want one in future.
So if we're pretty sure we'll never have a zebra-tx crate, it's not a priority.


Can the 'MAX_MACOS_DOCK_RECENT_ENTRIES' be changed to configurable?

Can the 'MAX_MACOS_DOCK_RECENT_ENTRIES' be changed to configurable? I have a lot of projects to manage, and the dock right button can be easily opened.
only 5 folders is too little...

@bpasero
see https://github.com/Microsoft/vscode/blob/ec1ca5ec204c42757ac5cbc53a3e250116fb5658/src/vs/platform/history/electron-main/historyMainService.ts#L191


new react example with react hooks

I created a working example of the react-js-buy example with the new react hooks syntax.
React is moving away from component classes in 16.8.1
Context: https://reactjs.org/docs/hooks-intro.html
Thanks :)

This is pretty awesome, thanks. But maybe we should make this a new example instead of modifying the old one? It could be called react-hooks-js-buy-sdk? Hooks are brand new so I'm wary of just replacing the existing one.

Yea, I can definitely do that.
Unless you want to just leave the pull request open just for other's reference. At some time in the future the non-component class syntax for react will become the standard, I assume?

Up to you 😄 But yeah I assume it will become the standard at some point.


Why can't I add cleverbot?

I've been looking over the internet for hours now trying to figure out how to add cleverbot to my bot and I've gotten no results.. can you help me?

this is not rly an issue with discord.js is it


feat: add prettier-plugin-sh

This PR adds prettier-plugin-sh and removes shfmt.
Note: it makes some minor modifications to the way our .sh files looked before. I tried setting some of the parser options based on the docs but nothing seemed to work so left it as is. It uses the default options based on mvdan/sh

Whats the motivation behind this?


Building details box

When you click on a building in the overview, a box pops up where you can edit some things about the building:

You can set the building level manually.
You can add "labels" to the building (that's just a string of words separated by spaces)
You can delete (untrack) the building.
Maybe: you can add a short note to the building. Maybe, because space is an issue, since this goes to sync. This would have to be like a tweet, 140 chars or something >.<

Once this is implemented, we can do away with the "remove" column in the overview, and implement another feature I'll introduce in another ticket.
This box should be available in trade.js and management.js, too, for the specific building.

Oh and, if we make this box display also the current state of a building, then we can reuse: pop this up also when the user clicks on any of the circle thingies in the nav screen, and fix #25 while we're at this.


draft: Add DM communications

Closes #8

@No767 I believe I fix most of the issues (aside from formatting or pyright, but I will later today)

I'll be submitting a review fairly soon


Disable spinn_test

@yifeif Instead of disabling the entire test, can you just comment out this line? https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/eager/python/examples/spinn/spinn_test.py#L420
The flaky part is the ML training part. All other parts shouldn't be flaky and I'd like to be covered.
Sorry about the inconvenience.


[Frontend][onnx]fix TopK can`t get k value

when i import onnx model superpoiny . i found i can`t get the k value.  The k value maybe save in parameters. So we can get it from param. I fix it.
cc: @MatthewARM @jwfromm @AndrewZhaoLuo

@ah-cheng when you import from relay, do you set freeze_params=True? That should solved the problem.
I think the issue here is if you don't the k param might be runtime dependent and we need to use dyn.topk or something.

Ahh, thanks for your time, @AndrewZhaoLuo when I set the freeze_params=True. I solved  this problem.
And when I first follow the code , It dose use the dyn.topk. the k param saved in params as a var.  but I dont know why i cant get the k param.
BTW, when i commit this PR, I want to add a unit test case. but when i run "python test_forward.py". I get a error.
firstly, I set "test_topk("llvm", tvm.cpu())" and run "python test_forward.py" ,but i get a error as follow:

then I use "verify_topk([12, 12, 12], 5, 1)", continue run. then i found the args is a int.

Is this a question in test unit case please?
or can we  fix the error as:
args = [self.visit(node.slice)] if isinstance(self.visit(node.slice), int) else self.visit(node.slice)


TUMBLR.IOS.APP-DEMO

https://github.com/user-attachments/assets/7b668273-e7fd-43ab-a5e7-223b5f180235
https://github.com/user-attachments/assets/0f9998e3-d009-487b-9151-46362921e8de

`
https://github.com/user-attachments/assets/7b668273-e7fd-43ab-a5e7-223b5f180235
https://github.com/user-attachments/assets/0f9998e3-d009-487b-9151-46362921e8de`


proxybased_external_services: module to enable dynamic redirects to services based on an http header

This PR adds the new proxybased_external_services module, which extends Jitsi's original external_services module to allow redirection of different clients to different services based on an HTTP header in the requests.
This is useful, for example, if internal clients should use different turn servers than external clients.

Hi @shawnchin, do you have time to review this PR?
If no, my suggestion is to merge it.

@emrahcom I'm afraid I don't currently have the bandwidth to review. Happy to merge.

@fluxxcode thanks for your contribution! Can you take a look at  the luacheck issues please?

@shawnchin The luacheck issues should be resolved now :)


pull request for e2e test at 01/19/2017 06:56:17

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


Issue in ground-truth trajectories in TAP-Vid Kinetics pickle files

Hi,
When trying to evaluate TAP-IR on TAP-Vid Kinetics, the reported model accuracy is much lower than reported in the paper.
I tried debugging this, and when visualizing the predictions vs ground-truth (by manually setting write_viz = True in supervised_point_prediction.SupervisedPointPrediction_eval_epoch, which runs viz_utils.write_visualization) I noticed that the ground truth trajectories are behaving very "weird", and move around the frames instead of "sticking" to a specific point (TAP-IR trajectories made much more sense and properly tracked objects). This was the case for many videos.
I was able to evaluate the models on TAP-Vid DAVIS properly.
Do you have any idea what might be the cause of this? I have no clue what might be the issue.
I ran the following code (I set query_mode="first" to make the visualization clearer).
python ./tapnet/experiment.py \
--config=./tapnet/configs/tapir_config.py \
--jaxline_mode=eval_tapvid_kinetics_q_first \
--config.checkpoint_dir=./tapnet/checkpoints_tapir/ \
--config.experiment_kwargs.config.kinetics_points_path=<path_to_tapvid_kinetics_pkl_files_dir>

The directory contains files [0000_of_0010.pkl, ..., 0009_of_0010.pkl]. I generated the TAP-Vid Kinetics files by following the instructions on https://github.com/google-deepmind/tapnet/tree/main/data#downloading-and-processing-tap-vid-kinetics
(Average after 27 videos)
{'average_jaccard': 0.242, 'average_pts_within_thresh': 0.334, 'jaccard_1': 0.081, 'jaccard_16': 0.402, 'jaccard_2': 0.163, 'jaccard_4': 0.246, 'jaccard_8': 0.316, 'loss_occ': 0.829, 'occlusion_accuracy': 0.745, 'position_loss': 52.873, 'pts_within_1': 0.127, 'pts_within_16': 0.560, 'pts_within_2': 0.229, 'pts_within_4': 0.329, 'pts_within_8': 0.428}

Here are two example visualization of predictions vs ground-truth trajectories for videos 2 & 3 in TAP-Vid Kinetics (I changed plt.scatter from diamond shape to plus sign for ground-truth trajectories, to make the visualization clearer).
This phenomena happens in most videos.
https://github.com/google-deepmind/tapnet/assets/43016459/d118ba09-a97c-49eb-9b1a-9440f62587cf
https://github.com/google-deepmind/tapnet/assets/43016459/34770655-a461-48e2-b8ab-91f17f0fab86

Unfortunately I can't see the video you've posted.  Maybe try some external hosting like google drive?

Nevermind, I reloaded and somehow they're working now.  This definitely looks like a framerate issue.  Our annotations assume the tensor of video frames is extracted at 25fps, so you need to make sure the ffmpeg command you used to decode the videos into frames is set up correctly.  Our script should do it, but it might not work if the framerate for the source videos is set incorrectly.  It's hard to say more without knowing how you downloaded the original videos.
If you got DAVIS working, would you mind closing your other bug?

Others haven't been reporting the same issue, so I'm closing due to inactivity.


raster calculator approach

the raster still does not render in QGIS or ArcPro. The file size is still too large. Maybe we should start over. Let me re-describe the problem, and you can re-invent the solution.
The input raster is a classified landcover raster with 255 classes, and only a handful of them contain values. I'd like each of the classes previously provided to be separated into their own raster.
I wonder if the solution is a "raster calculator", where the formula for the new raster is "where raster = " ? I just tested that with QGIS and it worked

I apologize for the confusion. I appreciate your patience. It seems that using a "raster calculator" approach might be a more efficient solution for your problem. Here's a new Python script that uses gdal_calc.py to perform the calculation for each class you are interested in:
import os
import subprocess
from osgeo import gdal

def separate_rasters_by_color(input_file, output_folder, color_values):
    print("Separating rasters by color...")

    # Check if GDAL is installed and gdal_calc.py is available
    try:
        subprocess.run(["gdal_calc.py", "--version"], check=True, capture_output=True)
    except FileNotFoundError:
        print("Error: gdal_calc.py is not available. Please install GDAL and ensure gdal_calc.py is in your system's PATH.")
        return

    for color_value in color_values:
        output_file = os.path.join(output_folder, f"{color_value}_global.tif")
        print(f"Processing color value {color_value}")

        # Run gdal_calc.py to create a new raster with the specified color_value
        calc_command = [
            "gdal_calc.py",
            "-A", input_file,
            "--outfile=" + output_file,
            "--calc=logical_and(A=={}, 1)".format(color_value),
            "--NoDataValue=0",
            "--co=COMPRESS=LZW"
        ]
        try:
            subprocess.run(calc_command, check=True)
            print(f"Successfully created raster for color value {color_value}")
        except subprocess.CalledProcessError as e:
            print(f"Error creating raster for color value {color_value}: {e}")

This script will use the gdal_calc.py utility to create separate rasters for each class specified in the color_values list. The input file should be the classified landcover raster, and the output_folder should be the directory where you want to store the separated rasters.
You can run the function like this:
input_file = "path/to/your/input/raster.tif"
output_folder = "path/to/your/output/folder"
color_values = [1, 2, 3, 4, 5]  # Replace this with the list of class numbers you are interested in
separate_rasters_by_color(input_file, output_folder, color_values)

Please let me know if this solution works for you, or if you have any other issues.


Unable to resolve nonexistent file

@CGNonofr ,
it seems with latest version, I started to have this problem. (please see below description)

use monaco-vscode-api 1.82.5, monaco editor v0.43.0, and then initialize the editor with javascript or typescript language.
go to the web page that has the editor in it, and then type var foo = "foo"; console.log(foo);
and then hold key "Command" in Mac or "Ctrl" in Windows, and mouse hover over foo, it will produce the error Unable to resolve nonexistent file

the error doesn't impact the monaco editor service usage though, but wondering if you have any insights on how to suppress that?
Thank you a lot.

Are you using the typescript-language-features extension? Can you try with the last version? Are you able to reproduce in the demo?

tested, can't be reproduced in latest version. closing this now. thanks.

@CGNonofr
sorry for the confusion, it seems in the latest version I can still reproduce it.
recorded a short video for reference.
also providing a public repo for you to reproduce. https://github.com/OliverwengFiltered/monaco-test
https://github.com/CodinGame/monaco-vscode-api/assets/28814939/3087e605-d19d-4950-8ecc-03623cc36e44

It's very difficult to navigate your repo as is contains the node_modules and the dist files.
I didn't find how you enabled the typescript intellisense and what you're using for it

removed dists and added readme here: https://github.com/OliverwengFiltered/monaco-test
and in terms of typescript/javascript intellisense, It was default enabled by monaco editor I believe.

Instead of using the monaco typescript intellisense, I suggest you use the typescript-language-features vscode extension instead by importing @codingame/monaco-vscode-typescript-language-features-default-extension