HTTP/TCP packets originating from Opnsense towards LAN interfaces seem to disappear

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
I posted the issue here but have yet to receive a response. Hence, this report. Please accept my apologies for potentially increasing the workload of opnsense's awesome team!
Upgraded from 23.x (latest release for business) to 24.4.1. Still on ISC DHCP with only IPv4; KEA not yet enabled. Intra- and Inter- VLAN packet routing works like a charm. No configuration or rule changes were made since. However, any outbound TCP (or sometimes UDP) packets in FW-->(any)VLAN direction on standard (e.g. 80, 443) or non-standard (e.g. 8080) ports do not get processed. ICMP pings to the same LAN hosts are fine. All other intra-VLAN nodes, inter-VLAN nodes, and even external nodes (e.g. web client on a cellular connection) can reach the address:ports in question. Just not the packets originating from FW. Example of such packets are telegraf metrics, crowdsec-lapi requests, or even simple requests from ssh/console like curl -vi --connect-timeout n <url> timeout.
Reverting to previous environment restores normalcy.
Steps to demonstrate issue

3 hosts in the mix here to illustrate the issue. a) Opnsense FW b) homeassistant (<IP_ADDRESS>) c) portainer (<IP_ADDRESS>)
Check reachability of hosts on VLAN 3 (opt7, main, IP range <IP_ADDRESS>/23) and then VLAN 100 (opt6, IP range <IP_ADDRESS>/24) from Opnsense FW.

ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=64 time=0.409 ms
...

ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=64 time=0.369 ms
..

Check routing towards the same hosts from Opnsense FW.

traceroute <IP_ADDRESS>
traceroute to <IP_ADDRESS> (<IP_ADDRESS>), 64 hops max, 40 byte packets
 1  homeassistant (<IP_ADDRESS>)  0.464 ms  0.167 ms  0.175 ms
...
traceroute <IP_ADDRESS>
traceroute to <IP_ADDRESS> (<IP_ADDRESS>), 64 hops max, 40 byte packets
 1  portainer (<IP_ADDRESS>)  0.359 ms  0.133 ms  0.241 ms

Check for port 443 exposure and attempt a simple curl request from one host to another - to test inter-VLAN reachability at application level. It works as intended.

@portainer:~$ nc -4nzvw 5 <IP_ADDRESS> 443
Connection to <IP_ADDRESS> 443 port [tcp/*] succeeded!
@portainer:~$ nc -4nuzvw 5 <IP_ADDRESS> 443
(base) maumau@portainer:~$
<!-- Notice here that HTTP3 over UDP/QUIC is disabled on web-servers
<!-- from homeassistant host
# netstat -tulnp | grep 443
tcp        0      0 <IP_ADDRESS>:443             <IP_ADDRESS>:*               LISTEN      10436/docker-proxy
tcp        0      0 :::443                  :::*                    LISTEN      10444/docker-proxy
-->
@portainer:~$ curl -ki --connect-timeout 5 https://homeassistant.esco.ghaar
HTTP/2 200
server: nginx
date: Sat, 06 Jul 2024 18:48:24 GMT
content-type: text/html; charset=utf-8
content-length: 4148
referrer-policy: no-referrer
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=31536000; includeSubDomains
... (truncated the full HTTP response)

Now, execute step 3 by replacing one of the hosts with Opnsense firewall

nc -4nzvw 5 <IP_ADDRESS> 443
nc: connect to <IP_ADDRESS> port 443 (tcp) failed: Operation timed out
nc -4nuzvw 5 <IP_ADDRESS> 443
Connection to <IP_ADDRESS> 443 port [udp/*] succeeded!
...
<!--
Opnsense's interpretation of 443 being opened for UDP is wrong here. As in step 3, only TCP on 443 is active!
-->
...
# curl -kvi --connect-timeout 5 https://homeassistant.esco.ghaar
* Host homeassistant.esco.ghaar:443 was resolved.
* IPv6: (none)
* IPv4: <IP_ADDRESS>
*   Trying <IP_ADDRESS>:443...
* ipv4 connect timeout after 4999ms, move on!
* Failed to connect to homeassistant.esco.ghaar port 443 after 5002 ms: Timeout was reached
* Closing connection
curl: (28) Failed to connect to homeassistant.esco.ghaar port 443 after 5002 ms: Timeout was reached

Expected behavior
Opnsense should establish HTTPS/TCP connection, or even basic TCP connection to hosts on various VLANs.
Describe alternatives you considered
Please refer to above. Reverting to Opnsense 23.x (last known business version) restores normalcy.
Screenshots
If applicable, add screenshots to help explain your problem.
Relevant log files
If applicable, information from log files supporting your claim.
Additional context
Few additional considerations which i grappled with:

Does this issue always happen?
Mostly yes, but every so often (once in a few hours or so) a TCP request in FW-->Host direction slips through. Evidence:

#nc -4znvw 10 <IP_ADDRESS> 443
Connection to <IP_ADDRESS> 443 port [tcp/*] succeeded!
<!-- immediately following which another series of requests fail -->
...
#nc -4znvw 10 <IP_ADDRESS> 443
nc: connect to <IP_ADDRESS> port 443 (tcp) failed: Operation timed out
# nc -4znvw 10 <IP_ADDRESS> 443
nc: connect to <IP_ADDRESS> port 443 (tcp) failed: Operation timed out

What is going on at TCP/IPv4 level?
a. Are the FW originating HTTP(s) over TCP packets sent over the wire?
Yes
b. If so, is the switch network eating it up? (due to say bad VLAN configuration
No
c. Is the receiving host not responding at TCP level?
** No**. Receiving host does issue TCP SYN ACKs
d. Are receiving hosts packets blocked by FW rules?
Answer: No
e. Are receiving hosts packets received at the FW interface?
Answer: Yes

Packet capture from opt6 (VLAN 100) to illustrate packet behavior can be seen below. Same behavior for main/opt7 interface is also observed. :
Servers
vlan0.100	2024-06-28
07:37:50.442037	f4:90:ea:00:9f:72	00:50:56:82:d8:b4	ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.31315 > <IP_ADDRESS>.8080: Flags [S], cksum 0x8070 (correct), seq 445912424, win 65535, options [mss 8960,nop,wscale 12,sackOK,TS val<PHONE_NUMBER> ecr 0], length 0
Servers
vlan0.100	2024-06-28
07:37:50.442400	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xe967 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:51.442697	f4:90:ea:00:9f:72	00:50:56:82:d8:b4	ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.31315 > <IP_ADDRESS>.8080: Flags [S], cksum 0x7c87 (correct), seq 445912424, win 65535, options [mss 8960,nop,wscale 12,sackOK,TS val<PHONE_NUMBER> ecr 0], length 0
Servers
vlan0.100	2024-06-28
07:37:51.443231	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xe57e (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:52.462713	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xe182 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:53.642675	f4:90:ea:00:9f:72	00:50:56:82:d8:b4	ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.31315 > <IP_ADDRESS>.8080: Flags [S], cksum 0x73ef (correct), seq 445912424, win 65535, options [mss 8960,nop,wscale 12,sackOK,TS val<PHONE_NUMBER> ecr 0], length 0
Servers
vlan0.100	2024-06-28
07:37:53.643161	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xdce6 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:55.662758	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xd502 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:57.842474	f4:90:ea:00:9f:72	00:50:56:82:d8:b4	ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.31315 > <IP_ADDRESS>.8080: Flags [S], cksum 0x6387 (correct), seq 445912424, win 65535, options [mss 8960,nop,wscale 12,sackOK,TS val<PHONE_NUMBER> ecr 0], length 0
Servers
vlan0.100	2024-06-28
07:37:57.842885	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xcc7e (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:38:01.966765	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xbc62 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0

Is there an MTU mismatch issue here? Step /2/ shows FW with mtu:9000 (downsampled at ether layer) with host mtu:1500 (downsampled at ether layer). Changing host mtu to be same as FW results in same behavior. Please see attached tcpdump.zip which includes pcap and json.

tcpdump.zip

Could there be an intermittent issue w/ network drivers for the ice card involved?
** Doesn't seem so**, Also, if that were to be the case then it should manifest across all VLANs? There are certain oddities about ice messages but these seemed also to be there in 23.x (if memory serves me right).

Copyright (c) 1992-2021 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 13.2-RELEASE-p11 stable/24.1-n255023-99a14409566 SMP amd64
FreeBSD clang version 14.0.5 (https://github.com/llvm/llvm-project.git llvmorg-14.0.5-0-gc12386ae247c)
VT(vga): resolution 640x480
CPU: AMD EPYC 3251 8-Core Processor                  (2495.44-MHz K8-class CPU)
  Origin="AuthenticAMD"  Id=0x800f12  Family=0x17  Model=0x1  Stepping=2
  Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
  Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
  AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
  AMD Features2=0x35c233ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX>
  Structured Extended Features=0x209c01a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA>
  XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
  AMD Extended Feature Extensions ID EBX=0x1007<CLZERO,IRPerf,XSaveErPtr,IBPB>
  SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
  TSC: P-state invariant, performance statistics
real memory  =<PHONE_NUMBER>4 (65534 MB)
avail memory =<PHONE_NUMBER>4 (63586 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <INSYDE WALLABY>
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 1 package(s) x 2 cache groups x 4 core(s) x 2 hardware threads
FreeBSD/SMP Online: 1 package(s) x 2 cache groups x 4 core(s)
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
random: unblocking device.
ioapic0: MADT APIC ID 128 != hw id 0
ioapic1: MADT APIC ID 129 != hw id 0
ioapic0 <Version 2.1> irqs 0-23
ioapic1 <Version 2.1> irqs 24-55
Launching APs: 7 5 1 3 2 6 4
random: entropy device external interface
wlan: mac acl policy registered
kbd0 at kbdmux0
WARNING: Device "spkr" is Giant locked and may be deleted before FreeBSD 14.0.
vtvga0: <VT VGA driver>
efirtc0: <EFI Realtime Clock>
efirtc0: registered as a time-of-day clock, resolution 1.000000s
smbios0: <System Management BIOS> at iomem 0x7945e000-0x7945e01e
smbios0: Version: 3.0, BCD Revision: 3.0
aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS,SHA1,SHA256>
acpi0: <INSYDE WALLABY>
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 350
Event timer "HPET1" frequency 14318180 Hz quality 350
Event timer "HPET2" frequency 14318180 Hz quality 350
atrtc0: <AT realtime clock> port 0x70-0x71 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
apei0: <ACPI Platform Error Interface> on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <base peripheral, IOMMU> at device 0.2 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> at device 1.3 on pci0
pci1: <ACPI PCI bus> on pcib1
nvme0: <Generic NVMe Device> mem 0x80900000-0x80903fff at device 0.0 on pci1
pcib2: <ACPI PCI-PCI bridge> at device 1.4 on pci0
pci2: <ACPI PCI bus> on pcib2
igb0: <Intel(R) I210 Flashless (Copper)> port 0x5000-0x501f mem 0x80800000-0x8081ffff,0x80820000-0x80823fff at device 0.0 on pci2
igb0: NVM V0.6 imgtype6
igb0: Using 1024 TX descriptors and 1024 RX descriptors
igb0: Using 4 RX queues 4 TX queues
igb0: Using MSI-X interrupts with 5 vectors
igb0: Ethernet address: f4:90:ea:00:a2:06
igb0: netmap queues/slots: TX 4/1024, RX 4/1024
pcib3: <ACPI PCI-PCI bridge> at device 1.5 on pci0
pci3: <ACPI PCI bus> on pcib3
igb1: <Intel(R) I210 Flashless (Copper)> port 0x4000-0x401f mem 0x80700000-0x8071ffff,0x80720000-0x80723fff at device 0.0 on pci3
igb1: NVM V0.6 imgtype6
igb1: Using 1024 TX descriptors and 1024 RX descriptors
igb1: Using 4 RX queues 4 TX queues
igb1: Using MSI-X interrupts with 5 vectors
igb1: Ethernet address: f4:90:ea:00:a2:07
igb1: netmap queues/slots: TX 4/1024, RX 4/1024
pcib4: <ACPI PCI-PCI bridge> at device 1.6 on pci0
pci4: <ACPI PCI bus> on pcib4
igb2: <Intel(R) I210 Flashless (Copper)> port 0x3000-0x301f mem 0x80600000-0x8061ffff,0x80620000-0x80623fff at device 0.0 on pci4
igb2: NVM V0.6 imgtype6
igb2: Using 1024 TX descriptors and 1024 RX descriptors
igb2: Using 4 RX queues 4 TX queues
igb2: Using MSI-X interrupts with 5 vectors
igb2: Ethernet address: f4:90:ea:00:a2:08
igb2: netmap queues/slots: TX 4/1024, RX 4/1024
pcib5: <ACPI PCI-PCI bridge> at device 1.7 on pci0
pci5: <ACPI PCI bus> on pcib5
igb3: <Intel(R) I210 Flashless (Copper)> port 0x2000-0x201f mem 0x80500000-0x8051ffff,0x80520000-0x80523fff at device 0.0 on pci5
igb3: NVM V0.6 imgtype6
igb3: Using 1024 TX descriptors and 1024 RX descriptors
igb3: Using 4 RX queues 4 TX queues
igb3: Using MSI-X interrupts with 5 vectors
igb3: Ethernet address: f4:90:ea:00:a2:09
igb3: netmap queues/slots: TX 4/1024, RX 4/1024
pcib6: <ACPI PCI-PCI bridge> at device 3.1 on pci0
pci6: <ACPI PCI bus> on pcib6
ice0: <Intel(R) Ethernet Network Adapter E810-XXV-2 - 1.37.11-k> mem 0x7fcfc000000-0x7fcfdffffff,0x7fcfe010000-0x7fcfe01ffff at device 0.0 on pci6
ice0: Loading the iflib ice driver
ice0: The DDP package was successfully loaded: ICE OS Default Package version <IP_ADDRESS>, track id 0xc0000001.
ice0: fw 6.2.9 api 1.7 nvm 3.20 etid 8000d853 netlist 3.20.5000-1.e.0.495c77bc oem 1.3146.0
ice0: Using 8 Tx and Rx queues
ice0: Reserving 8 MSI-X interrupts for iRDMA
ice0: Using MSI-X interrupts with 17 vectors
ice0: Using 1024 TX descriptors and 1024 RX descriptors
ice0: Ethernet address: f4:90:ea:00:9f:72
ice0: PCI Express Bus: Speed 8.0GT/s Width x8
ice0: Firmware LLDP agent disabled
ice0: link state changed to UP
ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: FC-FEC/BASE-R, Autoneg: False, Flow Control: None
ice0: netmap queues/slots: TX 8/1024, RX 8/1024
ice1: <Intel(R) Ethernet Network Adapter E810-XXV-2 - 1.37.11-k> mem 0x7fcfa000000-0x7fcfbffffff,0x7fcfe000000-0x7fcfe00ffff at device 0.1 on pci6
ice1: Loading the iflib ice driver
ice1: DDP package already present on device: ICE OS Default Package version <IP_ADDRESS>, track id 0xc0000001.
ice1: fw 6.2.9 api 1.7 nvm 3.20 etid 8000d853 netlist 3.20.5000-1.e.0.495c77bc oem 1.3146.0
ice1: Using 8 Tx and Rx queues
ice1: Reserving 8 MSI-X interrupts for iRDMA
ice1: Using MSI-X interrupts with 17 vectors
ice1: Using 1024 TX descriptors and 1024 RX descriptors
ice1: Ethernet address: f4:90:ea:00:9f:73
ice1: PCI Express Bus: Speed 8.0GT/s Width x8
ice1: Firmware LLDP agent disabled
ice1: link state changed to UP
ice1: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: FC-FEC/BASE-R, Autoneg: False, Flow Control: None
ice1: netmap queues/slots: TX 8/1024, RX 8/1024
pcib7: <ACPI PCI-PCI bridge> at device 7.1 on pci0
pci7: <ACPI PCI bus> on pcib7
pci7: <unknown> at device 0.0 (no driver attached)
pci7: <encrypt/decrypt> at device 0.2 (no driver attached)
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x80200000-0x802fffff at device 0.3 on pci7
xhci0: 64 bytes context size, 64-bit DMA
usbus0: waiting for BIOS to give up control
ice1: Module is not present.
ice1: Possible Solution 1: Check that the module is inserted correctly.
ice1: Possible Solution 2: If the problem persists, use a cable/module that is found in the supported modules and cables list for this device.
ice1: link state changed to DOWN
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
pcib8: <ACPI PCI-PCI bridge> at device 8.1 on pci0
pci8: <ACPI PCI bus> on pcib8
pci8: <unknown> at device 0.0 (no driver attached)
pci8: <encrypt/decrypt> at device 0.1 (no driver attached)
hdac0: <AMD X370 HDA Controller> mem 0x80180000-0x80187fff at device 0.3 on pci8
ax0: <AMD 10 Gigabit Ethernet Driver> mem 0x80160000-0x8017ffff,0x80140000-0x8015ffff,0x80188000-0x80189fff at device 0.4 on pci8
ax0: Using 2048 TX descriptors and 2048 RX descriptors
ax0: Using 8 RX queues 8 TX queues
ax0: Using MSI-X interrupts with 12 vectors
ax0: Ethernet address: f4:90:ea:00:a2:0a
ax0: xgbe_config_sph_mode: SPH disabled in channel 0
ax0: xgbe_config_sph_mode: SPH disabled in channel 1
ax0: xgbe_config_sph_mode: SPH disabled in channel 2
ax0: xgbe_config_sph_mode: SPH disabled in channel 3
ax0: xgbe_config_sph_mode: SPH disabled in channel 4
ax0: xgbe_config_sph_mode: SPH disabled in channel 5
ax0: xgbe_config_sph_mode: SPH disabled in channel 6
ax0: xgbe_config_sph_mode: SPH disabled in channel 7
ax0: RSS Enabled
ax0: Receive checksum offload Enabled
ax0: VLAN filtering Enabled
ax0: VLAN Stripping Enabled
ax0: Checking GPIO expander validity
ax0: GPIO configuration valid
ax0: xgbe_phy_sfp_signals: port_sfp_inputs: 0x7
ax0: xgbe_phy_sfp_detect: mod absent
ax0: netmap queues/slots: TX 8/2048, RX 8/2048
ax1: <AMD 10 Gigabit Ethernet Driver> mem 0x80120000-0x8013ffff,0x80100000-0x8011ffff,0x8018a000-0x8018bfff at device 0.5 on pci8
ax1: Using 2048 TX descriptors and 2048 RX descriptors
ax1: Using 8 RX queues 8 TX queues
ax1: Using MSI-X interrupts with 12 vectors
ax1: Ethernet address: f4:90:ea:00:a2:0b
ax1: xgbe_config_sph_mode: SPH disabled in channel 0
ax1: xgbe_config_sph_mode: SPH disabled in channel 1
ax1: xgbe_config_sph_mode: SPH disabled in channel 2
ax1: xgbe_config_sph_mode: SPH disabled in channel 3
ax1: xgbe_config_sph_mode: SPH disabled in channel 4
ax1: xgbe_config_sph_mode: SPH disabled in channel 5
ax1: xgbe_config_sph_mode: SPH disabled in channel 6
ax1: xgbe_config_sph_mode: SPH disabled in channel 7
ax1: RSS Enabled
ax1: Receive checksum offload Enabled
ax1: VLAN filtering Enabled
ax1: VLAN Stripping Enabled
ax1: Checking GPIO expander validity
ax1: GPIO configuration valid
ax1: xgbe_phy_sfp_signals: port_sfp_inputs: 0x7
ax1: xgbe_phy_sfp_detect: mod absent
ax1: netmap queues/slots: TX 8/2048, RX 8/2048
isab0: <PCI-ISA bridge> at device 20.3 on pci0
isa0: <ISA bus> on isab0
uart2: <16x50 with 256 byte FIFO> iomem 0xfedc9000-0xfedc9fff,0xfedc7000-0xfedc7fff irq 3 on acpi0
uart2: console (115384,n,8,1)
hwpstate0: <Cool`n'Quiet 2.0> on cpu0
Timecounter "TSC-low" frequency<PHONE_NUMBER> Hz quality 1000
Timecounters tick every 1.000 msec
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
ugen0.1: <AMD XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <AMD XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
nvd0: <TS1TMTE662T2> NVMe namespace
nvd0: 976762MB<PHONE_NUMBER> 512 byte sectors)
Trying to mount root from zfs:zroot/ROOT/default []...
uhub0: 8 ports with 8 removable, self powered
ice1: link state changed to UP
ice1: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: FC-FEC/BASE-R, Autoneg: False, Flow Control: None
igb1: link state changed to UP
ice0: Module is not present.
ice0: Possible Solution 1: Check that the module is inserted correctly.
ice0: Possible Solution 2: If the problem persists, use a cable/module that is found in the supported modules and cables list for this device.
ice0: Link is up, 25 Gbps Full Duplex, Requested FEC: RS-FEC, Negotiated FEC: FC-FEC/BASE-R, Autoneg: False, Flow Control: None
intsmb0: <AMD FCH SMBus Controller> at device 20.0 on pci0
smbus0: <System Management Bus> on intsmb0
driver bug: Unable to set devclass (class: ppc devname: (unknown))
ig4iic0: <Designware I2C Controller> iomem 0xfedc2000-0xfedc2fff irq 10 on acpi0
iicbus0: <Philips I2C bus (ACPI-hinted)> on ig4iic0
ig4iic1: <Designware I2C Controller> iomem 0xfedc3000-0xfedc3fff irq 11 on acpi0
iicbus1: <Philips I2C bus (ACPI-hinted)> on ig4iic1
ig4iic2: <Designware I2C Controller> iomem 0xfedc4000-0xfedc4fff irq 12 on acpi0
iicbus2: <Philips I2C bus (ACPI-hinted)> on ig4iic2
ig4iic3: <Designware I2C Controller> iomem 0xfedc5000-0xfedc5fff irq 6 on acpi0
iicbus3: <Philips I2C bus (ACPI-hinted)> on ig4iic3
ig4iic4: <Designware I2C Controller> iomem 0xfedc6000-0xfedc6fff irq 14 on acpi0
iicbus4: <Philips I2C bus (ACPI-hinted)> on ig4iic4
ig4iic5: <Designware I2C Controller> iomem 0xfedcb000-0xfedcbfff irq 15 on acpi0
iicbus5: <Philips I2C bus (ACPI-hinted)> on ig4iic5
lo0: link state changed to UP
amdsmn0: <AMD Family 17h System Management Network> on hostb0
amdtemp0: <AMD CPU On-Die Thermal Sensors> on hostb0
pflog0: permanently promiscuous mode enabled
lagg0: link state changed to UP
vlan0: changing name to 'vlan0.1'
vlan1: changing name to 'vlan0.100'
ice0: Failed to add VLAN filters:
ice0: - vlan 100, status -14
ice0: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 100, status -14
ice1: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan2: changing name to 'vlan0.120'
ice0: Failed to add VLAN filters:
ice0: - vlan 120, status -14
ice0: Failure adding VLAN 120 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 120, status -14
ice1: Failure adding VLAN 120 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan3: changing name to 'vlan0.121'
ice0: Failed to add VLAN filters:
ice0: - vlan 121, status -14
ice0: Failure adding VLAN 121 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 121, status -14
ice1: Failure adding VLAN 121 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan4: changing name to 'vlan0.140'
ice0: Failed to add VLAN filters:
ice0: - vlan 140, status -14
ice0: Failure adding VLAN 140 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 140, status -14
ice1: Failure adding VLAN 140 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan5: changing name to 'vlan0.2'
ice0: Failed to add VLAN filters:
ice0: - vlan 2, status -14
ice0: Failure adding VLAN 2 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 2, status -14
ice1: Failure adding VLAN 2 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan6: changing name to 'vlan0.250'
ice0: Failed to add VLAN filters:
ice0: - vlan 250, status -14
ice0: Failure adding VLAN 250 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 250, status -14
ice1: Failure adding VLAN 250 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan7: changing name to 'vlan0.3'
ice0: Failed to add VLAN filters:
ice0: - vlan 3, status -14
ice0: Failure adding VLAN 3 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 3, status -14
ice1: Failure adding VLAN 3 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
igb1: link state changed to DOWN
igb1: link state changed to UP
wg0: changing name to 'wg1'
wg1: link state changed to UP
tun1: changing name to 'ovpns1'
tun2: changing name to 'ovpns2'
tun3: changing name to 'ovpns3'
ovpns3: link state changed to UP
WARNING: attempt to domain_add(netgraph) after domainfinalize()
ovpns3: link state changed to DOWN
Trying to mount root from zfs:zroot/ROOT/default []...
lagg0: link state changed to DOWN
vlan0.1: link state changed to DOWN
vlan0.2: link state changed to DOWN
vlan0.100: link state changed to DOWN
vlan0.3: link state changed to DOWN
vlan0.140: link state changed to DOWN
vlan0.250: link state changed to DOWN
vlan0.121: link state changed to DOWN
vlan0.120: link state changed to DOWN
vlan0: changing name to 'vlan0.1'
ice0: Failed to add VLAN filters:
ice0: - vlan 1, status -14
ice0: Failure adding VLAN 1 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 1, status -14
ice1: Failure adding VLAN 1 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan1: changing name to 'vlan0.100'
ice0: Failed to add VLAN filters:
ice0: - vlan 100, status -14
ice0: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 100, status -14
ice1: Failure adding VLAN 100 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan2: changing name to 'vlan0.120'
ice0: Failed to add VLAN filters:
ice0: - vlan 120, status -14
ice0: Failure adding VLAN 120 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 120, status -14
ice1: Failure adding VLAN 120 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan3: changing name to 'vlan0.121'
ice0: Failed to add VLAN filters:
ice0: - vlan 121, status -14
ice0: Failure adding VLAN 121 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 121, status -14
ice1: Failure adding VLAN 121 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan4: changing name to 'vlan0.140'
ice0: Failed to add VLAN filters:
ice0: - vlan 140, status -14
ice0: Failure adding VLAN 140 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 140, status -14
ice1: Failure adding VLAN 140 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan5: changing name to 'vlan0.2'
ice0: Failed to add VLAN filters:
ice0: - vlan 2, status -14
ice0: Failure adding VLAN 2 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 2, status -14
ice1: Failure adding VLAN 2 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan6: changing name to 'vlan0.250'
ice0: Failed to add VLAN filters:
ice0: - vlan 250, status -14
ice0: Failure adding VLAN 250 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 250, status -14
ice1: Failure adding VLAN 250 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
vlan7: changing name to 'vlan0.3'
ice0: Failed to add VLAN filters:
ice0: - vlan 3, status -14
ice0: Failure adding VLAN 3 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ice1: Failed to add VLAN filters:
ice1: - vlan 3, status -14
ice1: Failure adding VLAN 3 to main VSI, err ICE_ERR_ALREADY_EXISTS aq_err OK
ovpns3: link state changed to UP
lagg0: link state changed to UP
vlan0.1: link state changed to UP
vlan0.2: link state changed to UP
vlan0.100: link state changed to UP
vlan0.3: link state changed to UP
vlan0.140: link state changed to UP
vlan0.250: link state changed to UP
vlan0.121: link state changed to UP
vlan0.120: link state changed to UP
igb1: link state changed to DOWN
igb1: link state changed to UP
igb1: link state changed to DOWN
igb1: link state changed to UP
ice0: promiscuous mode enabled
ice1: promiscuous mode enabled
lagg0: promiscuous mode enabled
vlan0.100: promiscuous mode enabled
ice0: promiscuous mode disabled
ice1: promiscuous mode disabled
lagg0: promiscuous mode disabled
vlan0.100: promiscuous mode disabled

Environment
Version 	24.4.1
Architecture 	amd64
Commit 	77b950d6f
Mirror https://opnsense-update.deciso.com/${SUBSCRIPTION}/FreeBSD:13:amd64/24.4
CPU AMD EPYC 3251 8-Core Processor (8 cores, 8 threads)
HW DEC4040

if 23.10.x works as expected but 24.1 doesn't, the first question is what the difference is in generated ruleset (/tmp/rules.debug). Would it be possible to collect both on the exact same configuration? Common issues in these cases relate to reply-to and route-to rules .

@AdSchellevis Many thanks for the prompt reply! Looking into 24.4.1 (current) /tmp, I see:
 ll r*
-rw-r--r--  1 root  wheel  63696 Jul  6 00:57 rules.debug
-rw-r--r--  1 root  wheel  63696 Jul  6 00:57 rules.debug.old

Both rules file are of the same size and created at the same time? I assume this would mean no changes across the upgrade?

A reinstall with 23.10 and update to the latest version in the 23.10 branch would be best indeed, then test if the issue is indeed not there and collect evidence.
If you want to exclude pf as most likely cause of your issue before reinstalling, I sometimes temporary disable pf as well using pfctl -d then check local connectivity and enable it again (pfctl -d). When local communication works without pf enabled, it's either a policy based routing rule (route-to/reply-to) or a nat issue.

Thank @AdSchellevis. I'll be remote (to FW in question) for the next few weeks. So, a full blown downgrade w/ console access might be a tall order until then.
The following didn't make a dent in the issue:

Disable pf using pfctl -d
curl failed

root@MorikCage:~ # curl -vi --connect-timeout 5 http://homeassistant.esco.ghaar
* Host homeassistant.esco.ghaar:80 was resolved.
* IPv6: (none)
* IPv4: <IP_ADDRESS>
*   Trying <IP_ADDRESS>:80...
* ipv4 connect timeout after 4999ms, move on!
* Failed to connect to homeassistant.esco.ghaar port 80 after 5002 ms: Timeout was reached
* Closing connection
curl: (28) Failed to connect to homeassistant.esco.ghaar port 80 after 5002 ms: Timeout was reached

Tried /2/ again after a few minutes. Same result. Although i suspect state tables were still active?
Enabled pf via pfctl -e

I could also attempt a step 2.5 with pfctl -F all to see whether that helps. But, I doubt it as my rules haven't changed between the two releases.
Would there be any other files besides:

/tmp/rules.debug
dmesg >> /tmp/dmsg.out
from 23.10 which you'd recommend for collection to aid in the diagnosis? I ask so that when I do the downgrade I can collect the right information.

well, if it doesn't work when pf is disabled in full (state table doesn't matter in that case), the question is if there is a valid default gateway installed and the interface used has a valid netmask.
netstat -nr4
ifconfig

LAN (from any host on any VLAN) <--> LAN (from any host on any VLAN), rules permitting, works as expected
LAN (from any host on any VLAN) --> WAN (e.g. google, bing, my own external websites) work wonderfully as well.
Reverse direction also works for HTTP (80-->443), HTTPS (443) and Wireguard port. No other ports are exposed externally.  I'll remove MAC addresses and such shortly.
Yes, access to internet (NAT) isn't a problem. The issue is only for traffic which originates from OpnSense e.g. syslog to a syslog server on lan, or Telegraf metrics destined for influxdb on lan, CrowdSec http notification to a LAPI on lan, simple curl requests to anywhere on any lan etc.

I wouldn't suspect the firewall to be honest, my next step would be to capture the traffic on both ends (packet capture on the firewall and on the target for the traffic between both hosts).
These type of issues usually relate to wrong gateways on the client in which case traffic does not return to the expected host.

Thank you for your continued guidance @AdSchellevis . Initially, I too had the suspicion that it must have been me (by virtue of network configuration changes) which would've caused this issue. But, few aspects don't support that conclusion:

Literally the only change was Opnsense 23.10-->24.4. Opnsense originated traffic towards VLAN was fine.
Looking at the tcpdump captures at Opnsense interface (opt6) from initial message, one can see that opt6 (same goes for other opt interfaces) does receive a SYN-ACK in response to its SYN. But, application logic (i.e. something above the TCP/IPv4 stack in opnsense) does not receive delivery of the SYN-ACKs. This causes TCP/IPv4 stack on opnsense to repeat SYN. Re-pasting for brevity

Servers
vlan0.100	2024-06-28
07:37:50.442037	f4:90:ea:00:9f:72	00:50:56:82:d8:b4	ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.31315 > <IP_ADDRESS>.8080: Flags [S], cksum 0x8070 (correct), seq 445912424, win 65535, options [mss 8960,nop,wscale 12,sackOK,TS val<PHONE_NUMBER> ecr 0], length 0
Servers
vlan0.100	2024-06-28
07:37:50.442400	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xe967 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:51.442697	f4:90:ea:00:9f:72	00:50:56:82:d8:b4	ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.31315 > <IP_ADDRESS>.8080: Flags [S], cksum 0x7c87 (correct), seq 445912424, win 65535, options [mss 8960,nop,wscale 12,sackOK,TS val<PHONE_NUMBER> ecr 0], length 0
Servers
vlan0.100	2024-06-28
07:37:51.443231	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xe57e (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:52.462713	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xe182 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:53.642675	f4:90:ea:00:9f:72	00:50:56:82:d8:b4	ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.31315 > <IP_ADDRESS>.8080: Flags [S], cksum 0x73ef (correct), seq 445912424, win 65535, options [mss 8960,nop,wscale 12,sackOK,TS val<PHONE_NUMBER> ecr 0], length 0
Servers
vlan0.100	2024-06-28
07:37:53.643161	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xdce6 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:55.662758	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xd502 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:37:57.842474	f4:90:ea:00:9f:72	00:50:56:82:d8:b4	ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.31315 > <IP_ADDRESS>.8080: Flags [S], cksum 0x6387 (correct), seq 445912424, win 65535, options [mss 8960,nop,wscale 12,sackOK,TS val<PHONE_NUMBER> ecr 0], length 0
Servers
vlan0.100	2024-06-28
07:37:57.842885	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xcc7e (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0
Servers
vlan0.100	2024-06-28
07:38:01.966765	00:50:56:82:d8:b4	f4:90:ea:00:9f:72	ethertype IPv4 (0x0800), length 74: (tos 0x2,ECT(0), ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.8080 > <IP_ADDRESS>.31315: Flags [S.], cksum 0xbc62 (correct), seq<PHONE_NUMBER>, ack 445912425, win 43440, options [mss 1460,sackOK,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>,nop,wscale 9], length 0

Both curl and nc exhibit really odd behavior. Latter recognizes tcp/443 as udp/443.
Intermittent allowance of connection establishment for FW-originated traffic from FW-->VLAN host(s) tells me its something to do w/ pf and/or rules.

#nc -4znvw 10 <IP_ADDRESS> 443
Connection to <IP_ADDRESS> 443 port [tcp/*] succeeded!
<!-- immediately following which another series of requests fail -->
...
#nc -4znvw 10 <IP_ADDRESS> 443
nc: connect to <IP_ADDRESS> port 443 (tcp) failed: Operation timed out
# nc -4znvw 10 <IP_ADDRESS> 443
nc: connect to <IP_ADDRESS> port 443 (tcp) failed: Operation timed out

If gateways were incorrectly configured on client(s) (pretty much all of the 150+ hosts in the network) then reachability issues would've manifested one way or another. Packet drop stats on those hosts are 0 when other LAN hosts / clients are involved.

I'm a bit out of clues I'm afraid, I suspect there is a logical explanation, but tracking this exceeds my current community support time.


Emcee Railtie cant Modify frozen Array

I'm installing a Rails project from scratch using Bower+Emcee, following this tutorial: http://stackoverflow.com/questions/26884022/google-polymer-with-rails-4
When I get to step 3 or 4
 rails g bower_rails:initialize
 rails g emcee:install

I get this error
/home/lluarteg/.rvm/gems/ruby-2.2.2@project2/bundler/gems/emcee-a47ed9852328/lib/emcee/railtie.rb:12:in `unshift': can't modify frozen Array (RuntimeError)
from /home/lluarteg/.rvm/gems/ruby-2.2.2@project2/bundler/gems/emcee-  a47ed9852328/lib/emcee/railtie.rb:12:in `block in <class:Railtie>'
from /home/lluarteg/.rvm/gems/ruby-2.2.2@project2/gems/railties-4.2.1/lib/rails/initializable.rb:30:in `instance_exec'
...

I'm using Rails 4.2.1 and Ruby 2.2.2
This is how my Gemfile looks
source 'https://rubygems.org'
ruby "2.2.2"

# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
gem 'rails', '4.2.1'
# Use postgresql as the database for Active Record
gem 'pg'
# Use SCSS for stylesheets
gem 'sass-rails', '~> 5.0'
# Use Uglifier as compressor for JavaScript assets
gem 'uglifier', '>= 1.3.0'
# Use CoffeeScript for .coffee assets and views
gem 'coffee-rails', '~> 4.1.0'
# See https://github.com/rails/execjs#readme for more supported runtimes
# gem 'therubyracer', platforms: :ruby

# Use jquery as the JavaScript library
gem 'jquery-rails'
# Turbolinks makes following links in your web application faster. Read more: https://github.com/rails/turbolinks
gem 'turbolinks'
# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
gem 'jbuilder', '~> 2.0'
# bundle exec rake doc:rails generates the API under doc/api.
gem 'sdoc', '~> 0.4.0', group: :doc

# Use ActiveModel has_secure_password
# gem 'bcrypt', '~> 3.1.7'

gem 'rails_12factor', group: :production
# Use Puma as the app server
gem 'puma'

# Use Capistrano for deployment
# gem 'capistrano-rails', group: :development

gem 'bower-rails'
gem 'emcee', github: 'ahuth/emcee'

group :development, :test do
  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
  gem 'byebug'

  # Access an IRB console on exception pages or by using <%= console %> in views
  gem 'web-console', '~> 2.0'

  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
  gem 'spring'
end

@lomefin try add to your gem file
gem "sprockets", "< 3.0.0"

Thank you @lomefin for the report, and thanks @brovikov for a potential work-around. This project is no longer under development, so hopefully the work-around works for you, or hopefully you can find something else that suites your needs.

The suggested fix-around worked. But, it took sprockets from v3.1.0 down to 2.12.3. I question whether that is the best, long-term fix for this issue.

That's definitely not a good long-term fix for the issue. Unfortunately, this project is no longer under development. Sorry!

@brovikov it worked. thx.
@ahuth any chance we can find someone to maintain it? I myself can not do because I'm working with iOS and Rails APIs more than with Rails front end. But I certainly would be happy to use emcee from time to time for my front end projects.

@ahuth maybe we can reach out to webcomponents and polymer communities?

Hey, @alexvbush. Somebody can certainly fork the repo. I don't want to put in the time to find someone to maintain it, though. Sorry!


AMBARI-24372 How alert count is presented for config errors/warnings/suggestions confusing and misleading

How was this patch tested?
21823 passing (29s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3340/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3342/
Test PASSed.


Investigate Razor depending on LiveShare being installed.

https://github.com/aspnet/AspNetCore/issues/8023#issuecomment-468767402

Was just bit by this. @chucker saved me a lot of time tracking this down.
In my case I have Live Share installed but manually disabled.

Turns out the core issue is due to Microsoft.VisualStudio.Liveshare.dll not being available for MEF discovery. Therefore, our Razor.LiveShare services explode and result in those services falling out of the MEF graph.


Failed to run: unknown token type

Installed the plugin and everything seems to work well until the scheduled publish time happens, at which point I get the following error:
This schedule failed to run.

execution failed: {"error":{"description":"unknown token type \"\"","type":"httpBadRequest"}}

Seems to happen for every scheduled document.
Team plan, Studio is on v2.29.8, private dataset, and I'm an admin user.

Same here. Non-Profit Plan, Studio version 2.29.8, private dataset and admin user

@corygibbons @tillschweneker
Thanks for raising this – we're currently aware of schedule error messages not being super helpful right now.
I'm also able to repro this issue – even with simple schedules that shouldn't otherwise fail. We're investigating and will get back here shortly.

I can confirm this issue has since been fixed – please do let us know if you continue to have issues here!

Thanks @robinpyon, seems to be working well now 🎉


[WIP] intel-{gmmlib,media-driver}: 18.4.1 -> 19.1

Motivation for this change
EDIT: err looks like intel-media-driver doesn't actually have a 19.1 tag yet, not sure what I was grabbing (and am running! haha).
no tag for intel-media-sdk yet, only 19.1.pre3 so far.
hopefully out soon :).
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

closes #58683

gmmlib v19.1.2 and media-driver v19.1.0 are published :)

Oh, hooray! I'll bump this in a few!
On Wed, 24 Apr 2019 13:20:27 -0700, Renaud<EMAIL_ADDRESS>wrote:

gmmlib v19.1.2 and media-driver v19.1.0 are published :)
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/pull/58546#issuecomment-486409906Non-text part: text/html


consider the second argument of qgrep#open in vimscript to be the input

I was looking for some vim command to automatically search with qgrep for the word under the cursor. This was a pain to do with normal! and execute, so I looked if it was possible to pass the command QgrepSearch some arguments. I'm still a noob in vimscript but didn't see a lot of use from the qgrep#open arguments, excepts from the first one which was the mode.
So I simply added a way to check if another second argument was provided, and if it is, consider it as the default first input.
With that change, it now because way easier to make vimscript command for qgrep. For example (tested on my side) :
:execute "QgrepSearch" expand("<cword>")
launches qgrep with, as default input, the current word under the cursor. And you can go way crazier with that :)
I'm also a noob in PR, so tell me if there's something I could do better.

This looks good, thanks!


[bug] Exclude withTamagui on api routes

Describe the bug
I just noticed that tamagui is added to API routes, especially when trying to add @vercel/og it fails because withTamagui is added. Is there a way to exclude withTamagui from API-routes?
To Reproduce
Compile and look at the output API file.
npm create tamagui@latest

Make your changes and then push and link it here. 🙏🙏🙏🙏🙏
System Info (please complete the following information):
Output of npx envinfo --system --npmPackages --binaries --browsers
  System:
    OS: macOS 12.0.1
    CPU: (8) x64 Apple M1
    Memory: 22.01 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.17.1 - ~/.nvm/versions/node/v16.17.1/bin/node
    Yarn: 3.2.4 - ~/.nvm/versions/node/v16.17.1/bin/yarn
    npm: 8.15.0 - ~/.nvm/versions/node/v16.17.1/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Chrome: 108.0.5359.124
    Safari: 15.1

[ ] yarn.lock or similar
[ ] If it's a specific file, add //! debug to the top (the ! works in esbuild compiled packages but not necessary always) and include that (only for compiler, but helps to know if it's on or off).
[ ] Run your server/bundler with DEBUG=tamagui and include that output at the bottom.

This is the logic here, I copied from other plugins that look for the non-next non-api loaders:
https://github.com/tamagui/tamagui/blob/master/packages/loader/src/plugin.ts#L67
If you find that file in your local app<EMAIL_ADDRESS>or something like that you can try modifying it and seeing what works? Would be helpful if you find some patch.

@pontusab if you can do me a favor and check/close if this if fixed

I can confirm adding this to withTamagui works but I haven't looked into why yet:
https://github.com/tamagui/tamagui/blob/master/packages/next-plugin/src/withTamagui.ts#L319

const cssRules = webpackConfig.module.rules.find(
          (rule) =>
            Array.isArray(rule.oneOf) &&
            rule.oneOf.some(
              ({ test }) =>
                typeof test === 'object' &&
                typeof test.test === 'function' &&
                test.test('filename.css')
            )
        ).oneOf.filter(x => x.issuerLayer !== 'api')

Hm that would just disable all CSS support I'd imagine breaking the app... because the filter will clone it and so not mutate the original.

Yo, closing some old issues, that code looks odd to me but if you can check one more time would be super helpful.


fix Fix sending commiting rpc to FE twice problem

this pr check transaction status before sending delete bitmap task to be, if transaction status is committed or visible, it no need to recalculate delete bitmap again, just retrun rpc success to be
pick pr:https://github.com/apache/doris/pull/41395

run buildall


docs: fix markdown formatting

Fixes #TODO
Motivation
I found some tildes while reading field reference and thought it's typo of strikethrough.
Modifications

Verification

@terrytangyuan Thank you for reviewing. At first I changed .md only in https://github.com/argoproj/argo-workflows/commit/7a5510e6a6d5536a92377dca540d381bcb0e0fef (and CI/Codegen failed)
then, I pushed https://github.com/argoproj/argo-workflows/pull/11206/commits/9efd2dc8885fd1880a95d51c487f695142b5f266 including docgen.go (and all CI passed). additional fix needed?


Could not load file or assembly Newtonsoft.Json version <IP_ADDRESS>

Just added the stylecop analyzer nuget package to my VS 2015 and getting lots of the same error below:

Warning	AD0001	Analyzer 'StyleCop.Analyzers.OrderingRules.SA1208SystemUsingDirectivesMustBePlacedBeforeOtherUsingDirectives' threw an exception of type 'System.IO.FileNotFoundException' with message 'Could not load file or assembly 'Newtonsoft.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.'.

Cannot find any way to fix the issue. I have tried replacing the newtonsoft.json.dll in the package directory with the net45 version and this did not make the warning go away.
Any help?
Thanks

What version of StyleCop Analyzers have you installed?
Are you using any other analyzers? If so, which one(s)?

Just had the same issue. Looks like Newtonsoft.Json package installs with errors because of the script execution policy.
So I run windows PowerShell: set-ExecutionPolicy Unrestricted -scope CurrentUser
Uninstalled both StyleCop.Analyser and Newtonsoft.Json packages
Installed StyleCop.Analyser (latest stable) and now it is working.

Looks like Newtonsoft.Json package installs with errors because of the script execution policy.

This is confusing to be, because you shouldn't need to "install" Newtonsoft.Json to use StyleCop Analyzers.

💭  I think he means that the install.ps1 file executed during NuGet package install is causing the problem. A quick search on Google revealed that more people have this issue and setting the execution policy solves it.

Our install scripts are signed, but I just noticed the certificate has since expired. All packages I could find, including those from Microsoft, no longer contain signatures in the scripts. It appears the problem was fixed in a more recent release of the NuGet extension for Visual Studio.
@DavidRooney @RodionovDmitry If you upgrade the NuGet Package Manager extension in Visual Studio, it  should install the package without problems.

Fixed in #2351 .


Opening new windows and tabs - update link

See https://github.com/nhsuk/nhsuk-service-manual-community-backlog/issues/324#issuecomment-988117252

Change made in branch review/1-subtitles. To go live with this branch.

Ready for release


Feature Request: Access restriction on roads

The information whether a road is accessible to the general public is currently missing from the vector tiles.
It would be convenient if the access restrictions would be conflated somehow, as on OSM, the access schema is quite complex. E.g. relevant for car drivers is not only access but also motor_vehicle.

It's not too hard to process the access schema server-side to derive access for car/pedestrian/bike. Generally for rendering you want to simplify access levels into yes, some cases, and not the general public. It's not obvious if we should do that or the styles should.
We also want to avoid having three access attributes on every single road - we don't need to know that cars are allowed on a residential road because that's the norm and to include that property on every road would inflate tile size.

Right, I think a single access value that applies for the expected vehicle type would be fine for the purpose of displaying a restriction on the map. Suggestions:

For all roads down to service roads (but except pedestrian roads), only the access and motor_vehicle key is considered. This means that if there is an access restriction for trucks only, this information is not included in the layer, which is fine for general purpose base maps, IMO

For values...

designated coalesces to yes

permissive coalesces to either yes or limited. I think the latter would be better

customers, destination, agricultural, forestry, delivery, discouraged coalesces to limited

permit coalesces to limited. I think it is mostly used for residential parking (residential parking permits). So, in that regard a bit similar as destination for roads.

(bicycle, horse, ... etc) dismount coalesces to no

military, private coalesce to no

all other values are ignored


Test suite

Description
Integrating test suite with GHActions

Codecov Report

Merging #31 into master will decrease coverage by 50.13%.
The diff coverage is 36.87%.

@@             Coverage Diff             @@
##           master      #31       +/-   ##
===========================================
- Coverage   90.94%   40.80%   -50.14%
===========================================
  Files          15       21        +6
  Lines         574      647       +73
  Branches       42       48        +6
===========================================
- Hits          522      264      -258
- Misses         41      383      +342
+ Partials       11        0       -11

Impacted Files
Coverage Δ

stockroom/cli.py
0.00% <0.00%> (ø)

stockroom/core.py
0.00% <0.00%> (ø)

stockroom/external/__init__.py
0.00% <0.00%> (ø)

stockroom/external/importer/__init__.py
0.00% <0.00%> (ø)

stockroom/external/importer/base.py
0.00% <0.00%> (ø)

...ockroom/external/importer/torchvision_importers.py
0.00% <0.00%> (ø)

stockroom/external/importer/utils.py
0.00% <0.00%> (ø)

stockroom/keeper.py
0.00% <0.00%> (ø)

stockroom/parser.py
0.00% <0.00%> (-100.00%)
:arrow_down:

stockroom/storages/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 24 more

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 21a040a...3799272. Read the comment docs.


Fix Shoot status transitioning to Failed too early

What this PR does / why we need it:
Fix Shoot status transitioning to Failed too early.
Steps to reproduce the issue:

Create a Shoot with OS extension which is currently not present on the Seed

Delete the OS extension controller deployment to make sure that the extension ManagedResource won't be healthy to be able to reproduce clearly the issue

Ensure that the Shoot is marked as Failed after 1m as the required OS extension is not ready. We rather want to mark the Shoot as Failed after retries for 24h.

Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

NONE

/kind/bug


feat: Add interface macAddress field

Codecov Report

Merging #35 (9e9a747) into main (3bbfb97) will increase coverage by 0.56%.
The diff coverage is 53.12%.

@@            Coverage Diff             @@
##             main      #35      +/-   ##
==========================================
+ Coverage   35.72%   36.28%   +0.56%
==========================================
  Files           3        3
  Lines         949      981      +32
==========================================
+ Hits          339      356      +17
- Misses        560      573      +13
- Partials       50       52       +2

Impacted Files
Coverage Δ

pkg/controller/vm_controller.go
21.83% <0.00%> (-0.48%)
:arrow_down:

pkg/controller/vm_webhook.go
44.08% <73.91%> (+1.46%)
:arrow_up:

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


abseil on windows, and a speed up of the abseil compilation

I figure this will be useful when you dig into a windows compilation. I have a cmake project that looks a lot like mach: (https://github.com/meshula/LabSlang)
During iteration, I've been frustrated that the official CMakeLists.txt from the abseil project is one of the biggest time consumers of the build, and for such a small value to the project.
I made a little shim project, and managed to organize abseil into almost a single-header-library. I got the abseil portion part of the glfw/dawn/tint build down from minutes to seconds.
There were some peculiarities in dawn's CMakeLists.txt that I sorted out which required the library to be broken into two specific. This wouldn't be necessary for mach's zig build.
It was a bit of a puzzle to organize the .cc files so they don't conflict with each other, and I needed to set the WINDOWS_LEAN_AND_MEAN and NOMINMAX macros. There's no significance to the file names I used, they are just left over from the thought process I had when I was trying to find the minimum organization of includes that would work.
I expect the single-header version of abseil will benefit the mach build, and the macros will be needed when you start the windows port.
Please feel free to borrow anything you want from what I did. It's here:
https://github.com/meshula/LabSlang/tree/main/abseil
I think adding my cpp files to this repo, and building those instead of the direct abseil files would be a speed win, and a start on a windows port.

@meshula really, thank you a ton for sending this, it's super interesting info and very timely.

I got the abseil portion part of the glfw/dawn/tint build down from minutes to seconds.

Are you suggesting here that out of all the Dawn compilation (including dependencies), abseil takes minutes on its own? That's insane and I really wouldn't have expected that at all! Especially given Dawn itself seems to take just, what, like 5-10 minutes overall to compile? Very curious if you have any more concrete numbers around this, I'll be trying to gather them myself as well

The header-only abseil approach is interesting. I'm not sure I fully understand so I'm hoping you can help me:

Why does a header-only approach end up being faster to compile? From what I can tell you are #includeing all the same files, so I'm not sure I follow why that would be faster to compile than going abseil->lib->linking - maybe it's reducing the amount of abseil code included in the final lib so you avoid linker times or something?

Did your structuring of numbers, str-format, and strings have a meaningful reason behind it? Why not place all #include in a single file?

I'll try to do some timing later.

why faster?

When you cmake, specifically, on Windows, the abseil build is comprised of 52 individual  targets, each with one or two files in it. Each target takes several seconds for the build system to visit, and that's why it takes minutes. Glomming all the files together means that the build is paying for three start ups.
I don't know how much this problem is due to cmake or msbuild ~ it feels like both treat abseil in a pathological way, it may be irrelevant for zig build.

The cmake files for dawn explicitly link strings.lib, and str-format.lib. I needed therefore two non-empty libs to satisfy dawn's cmake, because my goal was to not have to patch dawn in any way. numbers came about because absl-numbers has many conflicts when globbed with the files in str-format, and at first I thought it might make sense to move all of it out.

A combination of logic and intuition based on experience with other giant monster libs like boost and folly. It took a couple of hours, until I got a working dawn build with no symbols duplicated or missing.

some measurements:
win10 desktop
cmake + msbuild / 9 minutes
cmake + msbuild + abseil_unity / 8 minutes
abseil cmake / 1 minute
abseil unity / 2.5s
dawn/gpu zig build, fast win10 build fails in abseil due to pthreads
mac desktop
cmake + xcode, / 4 minutes
cmake + xcode + abseil_unity / 3 minutes 30 seconds
abseil cmake / 30 seconds
abseil unity / 1.5s
dawn/gpu zig build, fast mac, 5m 12s

Thanks a TON for the info here, this is all super useful for me


Update object data

/test test-hybriddeployable-operator-amd64

we shall enhance testing for update as well. It seems current test only check the existence of the instance, rather than check if the content is updated or not.
https://github.com/IBM/hybriddeployable-operator/blob/76654f72fffa26cee52ce27881fc38b0c6196d27/pkg/controller/hybriddeployable/hybriddeployable_controller_test.go#L238

two lines down , the test makes sure the payload's been actually updated. That covers the spec (or data for configmaps). I'll add some more tests for labels and annotations

/lgtm

/approved

/approve


get_balancer error

Hi
Kong Version: v2.2.1
errinfo
2021/05/13 01:57:15 [error] 79749#0: *9753678 [lua] balancer.lua:616: get_balancer(): balancer not found for php, will create it, client: xxxxx, server: kong, request: "GET xxx", host: "xxxx.xxx.xxx"
2021/05/13 01:57:17 [error] 79737#0: *9779974 [lua] balancer.lua:616: get_balancer(): balancer not found for php, will create it, client: xxxxxx, server: kong, request: "xxxxx", host: "xxx.xxx.xxx"
Is it normal to create the same balance frequently？
If not, how should I deal with it

Hi @tutorguai!
It's normal to have upstream being created just when they're needed. You can check at those messages that this happened in two different workers (PIDs 79749 and 79737). It's possible that you'll get this message for all workers, it's just an informative message that the mentioned upstream was known but still not ready for that worker when the request was received.
It will be an issue only if get this message repeated for the same PID.
As this is not a problem I'm closing this issue. Please feel free to reopen it if you find an issue with it. Anyway, I recommend upgrading to the last version as we've made a lot of improvements in the last releases.

Thank you for your answer

it's just an informative message that the mentioned upstream was known but still not ready for that worker when the request was received.

Given that, why does Kong log this message at "error" level?


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit a2b003f:
:clock10: Pending: waiting for processors (25 builds ahead of you)
:warning: Docs Build is busy, currently there are 25 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit a2b003f:
:clock10: Full build: the average full build time is 5 min(s) 48 sec(s), this is based on the last 30 build(s) for this repository.

Docs Build status updates of commit a2b003f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

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.


Switch back to bytecode

To swap over to bytecode, the changes in Compile.hs from https://github.com/haskell/ghcide/pull/836/commits/dc8526a70f752afb3fc2a615a9a04257193816b2 should be enough
For the call to unload, see https://github.com/wz1000/ghcide/commit/39d3fff427138be179e533b2779d05564671596c  from https://github.com/wz1000/ghcide/tree/reload-th
If we are using bytecode, we don't need to call unloadObj. However, the implementation could be better, by figuring out which modules are "stable", so don't need to be unloaded.
The other commit in the reload-th branch is also needed for the correctness of recompilation checking. It does need to be adapted for bytecode though.
Note that I can reproduce the test failure from this PR even before we started using object code. (Indeed, I believe the root cause of #672 is the same as the root cause of this)
Originally posted by @wz1000 in https://github.com/haskell/ghcide/pull/853#issuecomment-705725481

See also #854

Fixed by #873


Update staff_rename.lua

These two little changes fix the error under RGPLua 0.67
att: @jwink75

This pull request is no longer compatible with the master branch. Please update it, and I'll merge it.


Build better examples

The current example app is a really simple approach on what can be done with ViewAnimator. Even though the library is not complex to integrate and use on your own projects it would be nice to show how to use different animations in different scenarios.
I'd be replicating the app should on the animations Complex header.

Added the good first issue label, I'd really appreciate anyone who wants to send a PR with a simple implementation (it doesn't have to be the example above). Any use case that you feel ViewAnimator animations look good 😄


Enable AI assisted code review

Prototype github workflow feature to enable AI assisted code review
For another Slack repo (https://github.com/fxchen/kaldb/pull/1/files), here's what the results look like

The code review from my fork https://github.com/fxchen/slack-gradle-plugin/pull/1


gaps.outer.top vs the notch

Long, long time Yabai user here trying out AeroSpace. After about one day I'm pretty sure I'm a convert. Brilliant work @nikitabobko!
That said, I have a question regarding gaps.outer.top. It seems that on the display with a "notch", the padding is in relation to the bottom of the notch. Whereas displays without a notch, the padding is in relation to the actual top of the display. This makes the gap between the top of a window and my bar (SketchyBar) drastically larger/smaller on each display. Is there any way to account for this (eg. display specific setting)?
Maybe a screenshot will help illustrate better than my description. The left side is my MacBook Pro and the right is my external.

Is there any way to account for this (eg. display specific setting)?

Now it's not possible. But I agree that it'd be nice to have display specific settings for the gaps

Ok, I'm glad to know there wasn't something I was missing.
I will say, for my use case, an option to disregard the notch would also suffice. I'd take a crack at a PR but I have zero experience with Swift to date.

Alternatively, it would be nice to be able to change gaps using hotkey. It would be useful when I'm using 2 displays and I switch to 1.

Alternatively, it would be nice to be able to change gaps using hotkey. It would be useful when I'm using 2 displays and I switch to 1.

What is the use case for workspace-specific gaps?
In my head, there are two use cases for gaps:

Aesthetics. In this case, users use the same gaps on all workspaces
Practical. To make it easier to distinguish between windows

@nikitabobko to solve the problem mentioned in this issue. When I work on two displays I don't mind much that the top gap is bigger on my side (built-in)  display, but when I switch to mac only then the gap is annoying and takes to much space, so I need to adjust my config to reduce it.
As you said, right now it's not possible to fix this bug, so it could work as a workaround temporarily. If the bug is fixed, then changing gaps dynamically is not needed either.

@johnallen3d I fixed it here: #98

@johnallen3d I fixed it here: https://github.com/wojciech-kulik/AeroSpace/commit/51a2ca70021ef1f9b969161932d5240c3e504fbb
If you can build the project manually, you can try my fork before it's properly fixed here :).
I'm using this solution with sketchybar and it works well :).

Per-monitor gaps are released in 0.8.0-Beta

Work perfectly, thanks @wojciech-kulik and @nikitabobko!


figure out how to resolve templates on a default resolver

resolver.resolve(fullName) just looks on Ember.TEMPLATES, but something else in an application does the work of moving

this seems no longer relevant, closing due to age


fix: /emails/batch expects reply_to instead of replyTo

closes #421

Hope they merge this soon.

I need this PR :)


Feature Request: macOS Support for Hyperlight

Are there any plans to add macOS as a supported platform for Hyperlight? Since macOS has the Hypervisor.framework, it seems doable—projects like libkrun have already made use of it.
This would be great for macOS developers who want to test their apps locally before deployment. Macs are pretty popular among developers, and with Apple Silicon getting ridiculously powerful (plus nested virtualization coming to macOS), I think this feature would be super valuable.
Thanks for considering it!

Hypervisor.framework support has been a feature I've wanted for a long time. Right now, the issue isn't so much about writing the hypervisor implementation for it, but rather the process model that we currently support is limited by Hypervisor.framework. Hypervisor.framework supports only 1 VM per process. Hyperlight can use KVM and Hyper-V to create thousands of VM instances per process.
We have discussed changing the process model to support this use case. That would be a pretty big chunk of work.
We have also discussed exposing Hypervisor.framework support with the caveat that for local OSX dev you'd only be able to start a single VM instance.
Thoughts?

Thanks for the clarification. For macOS development, I think that's an acceptable trade-off.
Since macOS isn't likely to be a deployment platform, the aim is to be able to build and test apps locally before deploying on Linux machines, having one VM per process should work fine. If needed, one could orchestrate multiple processes to handle multiple VMs.
I get that changing the process model would be a big task and I wish I could help with the implementation but I don't have enough experience with VMMs to contribute meaningfully.

Would creating more processes be a workaround? It may seem odd and obviously won't work so well for a massive number of processes, but Activity Monitor, Google Chrome and LibreWolf each have more than a dozen processes at present.

Would creating more processes be a workaround? It may seem odd and obviously won't work so well for a massive number of processes, but in Activity Monitor on my Mac, Google Chrome and LibreWolf each have more than a dozen processes at present.

I think that is totally reasonable for local dev. However, it would be a bit different than the current programming model of Hyperlight and will probably need some sort of IPC mechanism to replicate the programming model.


Is this up to date with Tailwind 3.3.3?

Love the idea behind this Nick. I see that hasn't been an update in 3 years. I was just wondering if it supports all of the latest Tailwind classes at the time of writing (Sept 19, 2023). Or if this project is no longer active...
Thanks!
Sebastian

Hi, I'm Luca, the new project mantainer. Look at the latest rewrite - it should be on pair with Tailwind 3.3 !  :wink:


add api.IsEqual -> (0, 1) and api.IsDifferent  -> (0, 1)

currently we have AssertIsEqual and AssertIsDifferent, which don't allow composability and use in conjunction with api.Select for example.

But we have api.IsZero and can implement the methods as api.IsEqual(a,b) = api.IsZero(api.Sub(a,b)) and api.IsDifferent(a,b) = api.Sub(1, api.IsZero(a,b)).
I'd rather have fewer than more methods in API to make implementing it (GKR, field emulation, turboPLONK etc.) easier.

fair point, for my immediate use case that's probably enough...  that being said, for the examples you cite (field emulation, turboPLONK) there may be more efficient way to encode the statement, and, for field emulation in particular, I wanted something independent of other APIs, but that's probably too niche.


IDs are advertised for [build invocation, workspace, user] to allow cross referencing invocations and linking invocations of the same user and workspace

This change brings two new “features”, both internal at this point.
Scope IDs
Within a build invocation, IDs for the invocation, workspace and user are now available. The latter two are persisted in the invocation's root project and Gradle user home dir respectively. The build invocation ID is unique for each invocation.
The build scan plugin will read all IDs and associate them with the scan. This will enable forwards/backwards navigation in time for builds of the same workspace and/or user. It also allows linking related scans, which leads to …
Reused output origin build ID
When task outputs are reused, the build ID of the producer build is advertised if it is known. This is captured by the build scan plugin. This allows linking from a scan that reused outputs, to the scan of the build that produced those outputs, if a scan exists for it.
This applies to incremental build and build cache.
Notes
No new public API is introduced in this change. Eventually, the build ID will be exposed to users so that they can record it and use it to find build scans. For example, recording the build ID in the metadata of published JARs and using that to find out about the build that produced the artifact later in time, via the build scan.

@lptr @big-guy @wolfs You'll want to at least look at the changes around the origin metadata for cached artifacts. This change adds buildId.

@lptr @big-guy @wolfs please go ahead and leave your feedback here. I'll address it in a subsequent change set.


Suggestion:Hope can auto cast again after x seconds

Some kind of fish are mostly catched in certain seconds. it will save much time if can auto cast again after certain seconds when no fish catched. XD

Thats what the Timer options are for, if X amount of time is passed, the current cast will be canceled and recasted again


[Bug] Branch coverage incorrect in async static class methods

Describe the bug
When using monocart coverage reports, branches inside static async class methods are shown as else uncovered when using monocart
To Reproduce

Version:

monocart-coverage-report - 2.10.1
c8 - 10.1.2

Node Version: 22.4.1
Have you tried the latest version (including node), and does the issue still exist? yes
Steps to reproduce the actual behavior:

Write a simple class with a static async method containing an if statement (see reproduction)
Write a straight forward test to cover the branch (see reproduction)
Run the test with monocart coverage reports:⇒ c8 --experimental-monocart node Uncovered.test.js
--------------|---------|----------|---------|---------|-------------------
File          | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------|---------|----------|---------|---------|-------------------
All files     |     100 |       50 |     100 |     100 |
 Uncovered.js |     100 |       50 |     100 |     100 | 3
--------------|---------|----------|---------|---------|-------------------

Run the test without monocart coverage reports:⇒ c8 node Uncovered.test.js
--------------|---------|----------|---------|---------|-------------------
File          | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------|---------|----------|---------|---------|-------------------
All files     |     100 |      100 |     100 |     100 |
 Uncovered.js |     100 |      100 |     100 |     100 |
--------------|---------|----------|---------|---------|-------------------

Expected behavior
In both instances the coverage should be 100% as all lines and branches are in fact covered.
Errors or Screenshots
Any captured error messages, or add screenshots to help explain your problem.
Make a minimal reproduction
package.json
{
  "type": "module",
  "dependencies": {
    "c8": "^10.1.2",
    "monocart-coverage-reports": "^2.10.1"
  }
}

Uncovered.js
export class Uncovered {
    static async uncovered(active) {
        if (active) throw new Error('Active');

        return !active;
    }
}

Uncovered.test.js
import * as assert from 'node:assert';
import {Uncovered} from './Uncovered.js';

assert.equal(await Uncovered.uncovered(false), true);

await assert.rejects(async () => Uncovered.uncovered(true), {
    name: 'Error',
});

Run the following:
npm install
c8 node Uncovered.test.js  # see the 100% coverage output
c8 --experimental-monocart node Uncovered.test.js  # see the 50% branch coverage output

Additional context
While this may be down to some strange interactions with c8 I was unable to trigger this behaviour in the normal c8 coverage checks.
I was unable to reproduce this issue with a normal named async or synchronous function:
async function uncovered(active) {
    if (active) throw new Error('Active');

    return !active;
}

I was unable to reproduce this issue with a synchronous static class method:
export class Uncovered {
    static uncovered(active) {
        if (active) throw new Error('Active');

        return !active;
    }
}

I was unable to reproduce this issue with an async instance method:
export class Uncovered {
    async uncovered(active) {
        if (active) throw new Error('Active');

        return !active;
    }
}

In my specific use case I've been able to work around this to achieve 100% branch coverage by moving the if statement into a synchronous static method on the class like so:
export class Uncovered {
    static checkActive(active) {
        if (active) throw new Error('Active');
    }
    static async uncovered(active) {
        this.checkActive(active);

        return !active;
    }
}

This then results in 100% branch coverage:
⇒ c8 --experimental-monocart node Uncovered.test.js
--------------|---------|----------|---------|---------|-------------------
File          | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
--------------|---------|----------|---------|---------|-------------------
All files     |     100 |      100 |     100 |     100 |
 Uncovered.js |     100 |      100 |     100 |     100 |
--------------|---------|----------|---------|---------|-------------------

I can reproduce it simply with following
class StaticAsync {
    static async covered(active) {
        // should be covered
        if (active) {
            return 1;
        }
        return 2;
    }
}

await StaticAsync.covered(false);
await StaticAsync.covered(true);

It should be a issue related to static which is similar to #37
I will figure out how to fix it.

Please try<EMAIL_ADDRESS>

Hi @cenfun I can confirm this has resolved the issue, thank you for sorting this out!


Remove build file generation

With https://github.com/google/llvm-bazel/pull/11, we will use
handwritten Bazel BUILD files.

I actually want to merge this one before #11 because I currently have things set up to traverse LLVM commits and run the generation script, tagging new commits on this repo. Don't want that to happen when #11 is merged. It will append the generated build file to your handwritten one


Radio FX crashing TeamSpeak

When plugin activated and someone start talking, it's crashing my TS. At first it happend when I activate plugin in the middle of a talk, now it's happening all the time when people start talking.

Hm ok, couldn't replicate this (ofc I tested basic functionality).
Any chance you could up the crashdump file somewhere for me? (%appdata%/TS3client/)

ts3dump_1485809726310.zip
ts3dump_1485809659853.zip
ts3dump_1485809560213.zip
I noticed that now it don't crash TS when i connect to server with already activated plugin, but when i reload it, it crashes

Well, I found and fixed one crash that's triggered if the Radio FX ui is open when disabling or reloading the plugin.

@KantiOM also check which other plugins you have enabled. Sometimes plugin combinations cause crashes.

@Bluscream all other plugins disabled, also I restared TS after doing it. So only RadioFX working, and still crashing.

An update for RadioFX is now up and should be automatically installed if the addon was installed from within the client.
Not entirely sure if it fixes the issue, however fixes an issue.


missing dataset

Dear fellow scholars,
I would like to retrain this interesting project but I do not see a link to the dataset.
On this link http://graphics.unibas.it/www/HumanSegmentation/index.md.html, the dataset is not available.
Thank you,
Adrian

Hi @szat.
Thanks for the interest!
In 4 Resources on the project page is indicated that you have to send an email to request the dataset (red email icon). I'm sorry if it wasn't clear. Please, send an email to<EMAIL_ADDRESS>Best regards,
Monica


Stylelint and Prettier: Update configuration.

Changes

Update eslint-config-prettier, less, prettier.
Replace stylelint-config-prettier with stylelint-config-standard and stylelint-less.
Move Prettier config to package.json (per https://github.com/prettier/prettier-vscode/issues/3007)
Lint files.

Testing

PR checks should pass and the summaries component (for example) should be unchanged.

Notes

This drops legacy IE support in the heroes.

Aligning config with https://github.com/cfpb/consumerfinance.gov/pull/7881


Add coverage for India

Is your feature request related to a problem? Please describe.
Finally was able to get a trace from the KIA mobile app for INDIA users , have the tracefile and will send it across
Describe the solution you'd like
Add coverage to India users, Have shared the traffic trace file to<EMAIL_ADDRESS>.
Please let me know if you need more information.

@fuatakgun absolutely. Thank you for taking a look, currently running HA via RPI. But can run the same locally with your input. please let me know.

Just checking back @fuatakgun. Please let me know if I can add or contribute further towards this 😊🙏

@fuatakgun I am also interested in testing this if it works in India.

@PrathikGopal , can you please share the logs again? sorry for missing this

@PrathikGopal , can you please share the logs again? sorry for missing this

Sent it over to you 😊👍🏽

well received

@fuatakgun, did you get a chance to look at this? Thanks for considering this. I also drive a Kia in India, please let me know if I can help in some way. Thanks a lot for your efforts.

@fuatakgun still awaiting eagerly 👍 incase you need the logs let me know.

Library is updated to work with India region in india branch in my repo. https://github.com/gowthamgowtham/hyundai_kia_connect_api.
I've tested for a Hyundai vehicle. Not sure if Kia needs any changes, may be the URLs?
It was forked couple of months ago. Some cleanup might be necessary. The repo has a executable script india.py to test if it works for you.

Could you create a pull request?

Library is updated to work with India region in india branch in my repo. https://github.com/gowthamgowtham/hyundai_kia_connect_api.
I've tested for a Hyundai vehicle. Not sure if Kia needs any changes, may be the URLs?
It was forked couple of months ago. Some cleanup might be necessary. The repo has a executable script india.py to test if it works for you.

@gowthamgowtham - It would be great if you could please create a pull request for this. Really appreciate your help with this.

Sorry I could not reply sooner. I will get to creating pull request sometime this weekend. Thank your for your patience!
Meanwhile, I am just curious to know if anyone in India had any success with this code?

@gowthamgowtham I can test this for Kia India however cant seem to find the india.py file in your repo?. Any idea

@sajid2310 heres the file,
https://github.com/gowthamgowtham/hyundai_kia_connect_api/blob/india/india.py
@gowthamgowtham  Will test it later today and update.

doesnt work for KIA, URL is different https://prd.in-ccapi.kia.connected-car.io:8080

any updates?

Are there any updates on this? Will this be merged with master anytime soon?

@fuatakgun Thanks for your time on this, anyway i could be of help in speeding this up?

+1

I encourage one of you to try take this on.   It was close to done here. https://github.com/Hyundai-Kia-Connect/hyundai_kia_connect_api/issues/499

Hi! Has anyone got it working, ill be happy to assist, i have a HA and a Kia Carnival. Dont know python but can try and assist to get it working.

+1
I've HA and Blue Link (Venue)

Still need someone to step up who is within the region and work on the above linked PR.


Ollama version check and update if version is outdated

Closes #117

Crazy. when there is a Ollama service running, the version message is different.


We probably need to run PDB structures through PDBFixer or minimizer first

Looks like the structure is exploding.

Think this is fixed for test systems.


alternative trancript : outstanding from tco1  discussion (one transcript with CDS does not code for a protein)

https://github.com/pombase/pombase-chado/issues/852
tco1 one transcript/isoform does not code for a protein, (i.e. it is not expressed/not associated with ribosomes)
Therefore we need a way to indicate this (and to suppress the reading frame appearing in the contig maps).
I checked  EMBL and they have no suitable qualifier.
/translationally_repressed_isoform ?
in https://github.com/pombase/pombase-chado/issues/852 KIm also suggested adding a ncRRNA 'type' ?
Note that @bahler thought tco1 non-coding isoform should be curaed in the same way as pho84
For now, we will keep separate and revisit once we know more about the different mechanisms.
@juanmatacambridge

I think that here we decided to have a qualifier to apply to the transcript which is not translated. Will discuss.


fatal: Needed a single revision, Unable to find current origin/v1.74 revision in submodule path 'third_party/UHDM'

systemverilog-plugin/third_party/surelog$ git submodule update --remote --merge
fatal: Needed a single revision
Unable to find current origin/v1.74 revision in submodule path 'third_party/UHDM'

@timkpaine any idea?

I’m trying to repro locally but theres a lot going on in “systemverilog-plugin” which is now “synlig” (??) and has also changed default branch from master to main.

Actually I got the same error doing a recursive update in Surelog


Master

pull request test

@zackrabie Please don't use public repos for testing out GitHub!!! Thanks.


chore(ci): set stylua action version

Describe what this PR does / why we need it
Fixes failing stylua action check.
Describe how you did it
Set version field of stylua-action, in accordance with usage: https://github.com/JohnnyMorganz/stylua-action#usage.
Describe how to verify it
Take a look at current commits in master and recently open PRs. They are failing the stylua action check. This PR is not failing that check.
Special notes for reviews
I'm not sure if latest actually makes sense here. Just picked a working value.
Checklist

[ ] Passing tests and linting standards
[ ] Documentation updates in README.md and doc/octo.txt

Good catch! Thanks @maxenglander


Disable typo tolerance on attributes - disableOnAttributes

Previously we were using disableTypoToleranceOnAttributes in Algolia. I am aware that typo tolerance can be disabled as per the docs, however this is not covered in this library.
How can we use disableOnAttributes in meilisearch-rails?

Hello @jeremylynch
What version of the rails package are you using? There is a great chance you might be using an older package that doesn't this feature.

We are using 0.7.2, the latest available version as of 17th September

Hello @jeremylynch,
Sorry for the inconvenience. You are right and there is an existing issue about the topic here. We hope to add support for the typo tolerance settings very soon.
Hope this helps. Thank you very much.

I think I can close this issue since this is planned in the https://github.com/meilisearch/meilisearch-rails/issues/146 :)


move BeforeSaveChanges before ProcessEvents

https://github.com/JasperFx/marten/discussions/3004

@jeremydmiller everything is ok? maybe set plan to merge?

@borgez It's a breaking change in behavior. I can't take this in. What was the purpose of this? Why did you need this?

@jeremydmiller
I want to add general data like uid, etc... to the event, and expected behavior: projections handle this changes in "inline" mode.
The current behavior doesn't seem quite as expected because the changes are applied to projections before the hook.
Maybe then add another hook for this case like BeforeApplyChanges, but it doesn't seem very good?
The test describes my case:
      public override void BeforeSaveChanges(IDocumentSession session)
      {
          var streams = session.PendingChanges.Streams();
          foreach (var stream in streams)
          {
              foreach (var e in stream.Events)
              {
                  if (e.Data is EnrichedUserEvent eueb)
                  {
                      eueb.Actor = "some user from identity";
                  }
              }
          }
      }

@jeremydmiller maybe add hook BeforeEventProcessing?

@jeremydmiller revorked


submanifests: optional: Bump nanopb to 0.4.9

Sync upstream and get the latest tagged version 0.4.9.

@nashif @carlescufi can you help review

@pdgendt , need an update to the release notes?

Added release note

Isn't it a bit late to take module updates?

Isn't it a bit late to take module updates?

This was one of the concerns I had brought up in the last Release meeting.  A few of our modules are needing updates and the maintainers are working on it, but the time lines are not lining up with the 4.0 release.  I don't think we came to any final conclusion during that discussion.  Likely want to have this discussion not on the PR though :-)


Provide more cases in example

https://github.com/Saul-Mirone/milkdown/discussions/178

https://github.com/Saul-Mirone/milkdown/discussions/349

https://github.com/Saul-Mirone/milkdown/discussions/409

Hello, Since a lot of docs is misssing in zh-hans-docs, is there any plan to fill zh-CN documents?
If it needs, I'm glad to help to translate to zh.

I'm working on it and I think will be finished within this week.


the trait DatabasePool is not implemented for Pool<sqlx::Any>

Hello.
How create object SessionAnyPool if use "Pool<Any>"?
sqlx::any::install_default_drivers();
let any_pool = AnyPoolOptions::new()
    .max_connections(10)
    .connect("sqlite://test.db").await.unwrap();
let session_any_pool = axum_session_auth::SessionAnyPool::new(any_pool);

you will need to implement it like
https://github.com/AscendingCreations/AxumSession/blob/main/src/databases/postgres.rs
as we do not have SQLx Any in our list due to issues it was having before.  Our Any provides a way to use any of the currently made and set databases that we currently support.
so for your case you might not need SQLx Any and instead just use Postgres and SQlite and use the separate parts with our SessionAnyPool.  I have updated the Any Example to show you this. https://github.com/AscendingCreations/AxumSession/tree/main/examples/any

thanks for the example. I thought it was strange that there was a problem with creating a SessionAnyPool. It would be logical to create any_pool and pass it there.

atm there is not, but if you want you can submit a PR to add downcast_ref and downcast_mut.


Support multiple log files

List them all at top of file as links

Try putting all log files into common schema: IP, Timestamp, Details, Status.  For example, in HTTP the details are the http command, in auth it's just the body of the log entry. Status for HTTP is the return status number and for auth it's whether or not the log entry was informational, successful login, or denied. Either way, entries suggestive of hacking or probing should be red. (Maybe probing should be orange?)


Support working directory

Support changing the working directory for the mixin step
Update schema with descriptions

@vdice Fixed!


Break snowplow docusaurus plugin out into its own thing

Right now the docs use a local plugin for sending along snowplow events. It would be cool to make this a standalone plugin.

This will be taken care of in separate repo


imhex: 1.27.1 -> 1.29.0

Description of changes
updates the imhex package from version 1.27.1 to 1.29
you can see the changelog here https://github.com/WerWolv/ImHex/releases/tag/v1.29.0
between this last version and this one it's now able to build with capstone 4 and just disables the capstone 5 only features so -DUSE_SYSTEM_CAPSTONE=OFF was no longer needed
this also fixes a minor issue with it including _schema.json files in the releases which would log a warning when you started it

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

fixed double commit issue

Thanks for your first contribution, keep'em coming !


Unexpected warning from v4l2

No sure we should be aware of this warning message or not. I saw this warning message in my setup.
Setup
Linux raspberry 6.6.20+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux
Raspberry Pi 5
Raspberry Pi Camera Module 3
libcamera v0.3.0+65-6ddd79b5
libpisp version v1.0.6 b567f0455680 17-06-2024
picamera2 0.3.19
Sample Code
from picamera2 import Picamera2

picam2 = Picamera2()
picam2.still_configuration.main.size = (4608, 2592)
picam2.still_configuration.main.format = 'BGR888'
picam2.configure('still')
picam2.close()

Yes, that's normal, libcamera can be a bit "chatty" sometimes. You can quieten it down by putting something like
LIBCAMERA_LOG_LVELS=*:3

in your .bashrc or typing it in the terminal window.


Issues

1.The Shell Command is totally useless When Ever I type Any Commands even a simple one it does not  work
2. Keylogger is good but i can't keep scrolling and clicking There should be easier way to do it
3.there is no login portal in  panel if the link is the only way to access. anyone can access without the admin permission
4. There should be option of the app like auto clicker or when we want we can click on victim screen
5. The admin panel also hangs sometime

Can you list the commands which you have used.
For better performance , only fewer records are loaded at a time.
Use localhost or your private vps.
Why?
Can you record a video and elaborate more , upon how to reproduce this.

1.man,cat,echo
2.yeah But there should Option To record ONLY WhatsApp messages . whenever WhatsApp open the Keylogger should start automatically
3.but login page Looks Good i can access it from any device most probably But not needed Now
4.Cause its like using the Phone we can do more functions
5.i given it at telegram

Can you list the commands which you have used.
For better performance , only fewer records are loaded at a time.
Use localhost or your private vps.
Why?
Can you record a video and elaborate more , upon how to reproduce this.

1.man,cat,echo
2.yeah But there should Option To record ONLY WhatsApp messages . whenever WhatsApp open the Keylogger should start automatically
3.but login page Looks Good i can access it from any device most probably But not needed Now
4.Cause its like using the Phone we can do more functions
5.i given it at telegram

cat , echo and all other adb commands are working perfectly, seems like you have some issue on your end. If you can share some screenshots it would be better.
This isn't how keylogger is meant to work.
Use localhost or a private VPS.
Ok!!
Where?

any tutorial to make it work on vps?

It's the same process you do on your local computer.
The only difference is you will be doing that on VPS.


[feature request] Prop for day of week format

Currently month headers have the format dd hardcoded for week days (that resolves to “Su Mo Tu We Th Fr Sa” in English).
In my case, the default translation for pt-BR shipped in Moment.js resolves to “Dom 2ª 3ª 4ª 5ª 6ª Sáb”, very unusual here. A better format would be ddd.
I guess even in English or other languages, one could like to set ddd (or even dddd for full names). So a prop like weekDayFormat for components would be nice.

This should be addressed in v12.6.0


Constraint name consistancy

Should we drop the word Constraint from constraint names a la DefiningAlleleContext and DefiningLocationContext or are those constraints special for some reason?
Then update schema to reflect this decision.

We are leaving Constraint suffixes on subclassed Constraints.  We started to add different terms like Context but that wasn't any better.  We also began removing Constraint from the subclasses altogether but we could come up with a better name for copyConstraint so it seemed prudent to just leave Constraint on the end of all subclassed Constraints

Closing this for the 1.0 version unless others thing it's worth re-opening.


Back button stops working after some rotations

Back button stops working after some rotations (landscapeRight > landscapeRight > landscapeRight)
  self.navigationController?.popViewController(animated: true) doesn't do anything after (landscapeRight > landscapeRight > landscapeRight)

https://stackoverflow.com/questions/51723160/popviewcontroller-doesnt-work-after-rotation

I don't know hot but your player causes it if I remove it everything works fine


ci: auto-approve backports

backports currently need manual approval, which is unnecessary since they have been approved already.

@mergifyio backport v3