arch-x86,O3,KVM switching to full simulation bug

Describe the bug
When using the full system simulation m5_switch_cpu_addr followed by m5_exit or m5_exit_addr causes either the simulation to segfault or the simulated program to segfault(One might also see an unexpected jump, I am guessing that is the same bug).
Affects version
gem5 stable c890e6b113a59caeec3eea9bafea4a03a471f89d
gem5 Modifications
I have modified the config file, added my disk, and wrote a simple program to reproduce the bug. Also changed the default disk device for X86 KernelDiskWorkload to "/dev/sda".
https://github.com/Foxy-Boxes/gem5-bug, has the necessary changes.
To Reproduce
download this tarred image to the repo: https://drive.google.com/file/d/1qH7QNoz23UIyuU07Rf7AoEvS3Opvcl74/view?usp=sharing
scons build/X86/gem5.debug -j `nproc`
./one_time.sh
./make_disk.sh
./build/X86/gem5.debug ./configs/example/gem5_library/x86-ubuntu-run-with-kvm-test.py

Terminal Output
In the case where we get a segfault
warn: The `CustomResource` class is deprecated. Please use an `AbstractResource` subclass instead.
Global frequency set at<PHONE_NUMBER>000 ticks per second
warn: No dot file generated. Please install pydot to generate the dot file and pdf.
src/mem/dram_interface.cc:690: warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (4096 Mbytes)
src/sim/kernel_workload.cc:46: info: kernel located at: resources/vmlinux
src/base/statistics.hh:279: warn: One of the stats is a legacy stat. Legacy stat is a stat that does not belong to any statistics::Group. Legacy stat is deprecated.
      0: board.pc.south_bridge.cmos.rtc: Real-time clock set to Sun Jan  1 00:00:00 2012
board.pc.com_1.device: Listening for connections on port 3456
src/base/statistics.hh:279: warn: One of the stats is a legacy stat. Legacy stat is a stat that does not belong to any statistics::Group. Legacy stat is deprecated.
src/dev/intel_8254_timer.cc:128: warn: Reading current count from inactive timer.
board.remote_gdb: Listening for connections on port 7000
src/cpu/kvm/base.cc:169: info: KVM: Coalesced MMIO disabled by config.
src/cpu/kvm/base.cc:169: info: KVM: Coalesced MMIO disabled by config.
gem5 Simulator System.  https://www.gem5.org
gem5 is copyrighted software; use the --copyright option for details.

gem5 version <IP_ADDRESS>
gem5 compiled Mar  4 2024 20:46:18
gem5 started Mar  4 2024 20:56:29
gem5 executing on sapphire, pid 1654951
command line: ./build/X86/gem5.debug ./configs/example/gem5_library/x86-ubuntu-run-with-kvm-test.py

src/sim/simulate.cc:199: info: Entering event queue @ 0.  Starting simulation...
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x3a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xe1) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x309) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x30a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x30b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x38d) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x38e) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x38f) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x390) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc1) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc2) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc3) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc4) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc5) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc6) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc7) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc8) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x186) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x187) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x188) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x189) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x18a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x18b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x18c) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x18d) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x3f1) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x600) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x3f2) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x1c4) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x1c5) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x12) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x11) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d01) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d00) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000000) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000001) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000020) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000021) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000022) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000023) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000100) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000101) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000102) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000103) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000104) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000105) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000003) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000002) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000010) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000080) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000b0) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000073) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000106) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000107) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000108) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000ff) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f1) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f2) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f3) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f4) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f5) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d02) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d03) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d04) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d06) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d07) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x3b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x6e0) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x10a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x345) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x1a0) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4d0) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x9e) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x34) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xce) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x140) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x1fc) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x8b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x480) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48d) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48e) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48f) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x490) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x485) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x486) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x488) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48c) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x491) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc0010015) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d05) unsupported by gem5. Skipping.
src/dev/x86/pc.cc:117: warn: Don't know what interrupt to clear for console.
src/arch/x86/kvm/x86_cpu.cc:563: warn: cs limit (0xffffffff) and g (0) combination is illegal.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x3a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xe1) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x309) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x30a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x30b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x38d) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x38e) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x38f) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x390) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc1) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc2) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc3) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc4) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc5) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc6) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc7) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc8) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x186) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x187) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x188) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x189) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x18a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x18b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x18c) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x18d) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x3f1) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x600) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x3f2) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x1c4) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x1c5) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x12) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x11) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d01) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d00) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000000) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000001) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000020) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000021) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000022) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000023) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000100) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000101) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000102) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000103) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000104) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000105) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000003) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000002) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000010) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000080) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000b0) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000073) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000106) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000107) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x40000108) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000ff) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f1) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f2) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f3) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f4) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x400000f5) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d02) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d03) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d04) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d06) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d07) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x3b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x6e0) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x10a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x345) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x1a0) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4d0) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x9e) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x34) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xce) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x140) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x1fc) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x8b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x480) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48d) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48e) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48f) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x490) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x485) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x486) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x488) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48a) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48b) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x48c) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x491) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0xc0010015) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:1653: warn: kvm-x86: MSR (0x4b564d05) unsupported by gem5. Skipping.
src/arch/x86/kvm/x86_cpu.cc:563: warn: cs limit (0xffffffff) and g (0) combination is illegal.
src/arch/x86/kvm/x86_cpu.cc:563: warn: cs limit (0xffffffff) and g (0) combination is illegal.
src/arch/x86/interrupts.cc:530: hack: Assuming logical destinations are 1 << id.
warn: No behavior was set by the user for switch CPU. Default behavior is switching the CPU type of the processor and continuing.
src/sim/power_state.cc:105: warn: PowerState: Already in the requested power state, request ignored
switching cpus
src/sim/simulate.cc:199: info: Entering event queue @<PHONE_NUMBER>995.  Starting simulation...
src/mem/ruby/system/Sequencer.cc:668: warn: Replacement policy updates recently became the responsibility of SLICC state machines. Make sure to setMRU() near callbacks in .sm files!
gem5 has encountered a segmentation fault!

--- BEGIN LIBC BACKTRACE ---
./build/X86/gem5.debug(_ZN4gem515print_backtraceEv+0x32)[0x556a2e67fa47]
./build/X86/gem5.debug(+0x2b66e0e)[0x556a2e6a5e0e]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7f1c79c42520]
./build/X86/gem5.debug(_ZNKSt12__shared_ptrIN4gem57RequestELN9__gnu_cxx12_Lock_policyE2EE3getEv+0x10)[0x556a2d1560f4]
./build/X86/gem5.debug(_ZNKSt19__shared_ptr_accessIN4gem57RequestELN9__gnu_cxx12_Lock_policyE2ELb0ELb0EE6_M_getEv+0x1c)[0x556a2d1568a6]
./build/X86/gem5.debug(_ZNKSt19__shared_ptr_accessIN4gem57RequestELN9__gnu_cxx12_Lock_policyE2ELb0ELb0EEptEv+0x1c)[0x556a2d155f72]
./build/X86/gem5.debug(_ZN4gem57BaseCPU5mwaitEsPNS_6PacketE+0xee)[0x556a2e7f4a62]
./build/X86/gem5.debug(_ZN4gem52o37DynInst5mwaitEPNS_6PacketE+0x39)[0x556a2e9db517]
./build/X86/gem5.debug(_ZNK4gem510X86ISAInst5Mwait11completeAccEPNS_6PacketEPNS_11ExecContextEPNS_5trace10InstRecordE+0xa8)[0x556a2d7d5dc4]
./build/X86/gem5.debug(_ZN4gem52o37DynInst11completeAccEPNS_6PacketE+0xdc)[0x556a2e9d9f10]
./build/X86/gem5.debug(_ZN4gem52o37LSQUnit11executeLoadERKNS_14RefCountingPtrINS0_7DynInstEEE+0x2aa)[0x556a2ea23404]
./build/X86/gem5.debug(_ZN4gem52o33LSQ11executeLoadERKNS_14RefCountingPtrINS0_7DynInstEEE+0x6f)[0x556a2ea0fbb5]
./build/X86/gem5.debug(_ZN4gem52o33IEW12executeInstsEv+0x75a)[0x556a2e9f9738]
./build/X86/gem5.debug(_ZN4gem52o33IEW4tickEv+0x21e)[0x556a2e9fb3a8]
./build/X86/gem5.debug(_ZN4gem52o33CPU4tickEv+0x1c5)[0x556a2e9b7035]
./build/X86/gem5.debug(+0x2e75529)[0x556a2e9b4529]
./build/X86/gem5.debug(+0x2e7efc8)[0x556a2e9bdfc8]
./build/X86/gem5.debug(+0x2e7ed5a)[0x556a2e9bdd5a]
./build/X86/gem5.debug(+0x2e7eb54)[0x556a2e9bdb54]
./build/X86/gem5.debug(_ZNKSt8functionIFvvEEclEv+0x36)[0x556a2d0ea41a]
./build/X86/gem5.debug(_ZN4gem520EventFunctionWrapper7processEv+0x20)[0x556a2d19b40e]
./build/X86/gem5.debug(_ZN4gem510EventQueue10serviceOneEv+0x121)[0x556a2e693b75]
./build/X86/gem5.debug(_ZN4gem59doSimLoopEPNS_10EventQueueE+0x240)[0x556a2e6bc3a3]
./build/X86/gem5.debug(_ZN4gem58simulateEm+0x23e)[0x556a2e6bbe3a]
./build/X86/gem5.debug(+0x2241728)[0x556a2dd80728]
./build/X86/gem5.debug(+0x223f6e0)[0x556a2dd7e6e0]
./build/X86/gem5.debug(+0x223b26f)[0x556a2dd7a26f]
./build/X86/gem5.debug(+0x223b2da)[0x556a2dd7a2da]
./build/X86/gem5.debug(+0x151b027)[0x556a2d05a027]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(+0x128023)[0x7f1c7ab28023]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyObject_Call+0x5c)[0x7f1c7aae1fec]
/lib/x86_64-linux-gnu/libpython3.10.so.1.0(_PyEval_EvalFrameDefault+0x4b16)[0x7f1c7aa76776]
--- END LIBC BACKTRACE ---
For more info on how to address this issue, please visit https://www.gem5.org/documentation/general_docs/common-errors/

When gem5 does not segfault but the simulation jumps to an unexpected location, this is the m5term output:
Linux version 6.0.0+ (berk@sapphire) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils) 2.36.1) #17 SMP Tue Nov 14 00:17:15 UTC 2023
Command line: earlyprintk=ttyS0 console=ttyS0 lpj=7999923 root=/dev/sda1 disk_device=/dev/sda
x86/fpu: x87 FPU will use FXSAVE
signal: max sigframe size: 1440
BIOS-provided physical RAM map:
BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
BIOS-e820: [mem 0x000000000009fc00-0x00000000000fffff] reserved
BIOS-e820: [mem 0x0000000000100000-0x00000000bfffffff] usable
BIOS-e820: [mem 0x00000000ffff0000-0x00000000ffffffff] reserved
printk: bootconsole [earlyser0] enabled
NX (Execute Disable) protection: active
SMBIOS 2.5 present.
DMI:  , BIOS  06/08/2008
tsc: Fast TSC calibration failed
last_pfn = 0xc0000 max_arch_pfn = 0x400000000
Disabled
x86/PAT: MTRRs disabled, skipping PAT initialization too.
CPU MTRRs all blank - virtualized system.
x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC
found SMP MP-table at [mem 0x000f0050-0x000f005f]
ACPI: Early table checksum verification disabled
ACPI: RSDP 0x00000000000F01C0 000024 (v02       )
ACPI: XSDT 0x00000000000F0208 000024 (v01                 00000000      00000000)
ACPI BIOS Error (bug): Invalid table length 0x24 in RSDT/XSDT (20220331/tbutils-289)
Zone ranges:
  DMA      [mem 0x0000000000001000-0x0000000000ffffff]
  DMA32    [mem 0x0000000001000000-0x00000000bfffffff]
  Normal   empty
Movable zone start for each node
Early memory node ranges
  node   0: [mem 0x0000000000001000-0x000000000009efff]
  node   0: [mem 0x0000000000100000-0x00000000bfffffff]
Initmem setup node 0 [mem 0x0000000000001000-0x00000000bfffffff]
On node 0, zone DMA: 1 pages in unavailable ranges
On node 0, zone DMA: 97 pages in unavailable ranges
Intel MultiProcessor Specification v1.4
MPTABLE: OEM ID:
MPTABLE: Product ID:
MPTABLE: APIC at: 0xFEE00000
Processor #0 (Bootup-CPU)
Processor #1
IOAPIC[0]: apic_id 2, version 20, address 0xfec00000, GSI 0-23
Processors: 2
smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[mem 0xc0000000-0xfffeffff] available for PCI devices
Booting paravirtualized kernel on bare hardware
clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>391419 ns
setup_percpu: NR_CPUS:8192 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
percpu: Embedded 51 pages/cpu s168296 r8192 d32408 u1048576
Built 1 zonelists, mobility grouping on.  Total pages: 775424
Kernel command line: earlyprintk=ttyS0 console=ttyS0 lpj=7999923 root=/dev/sda1 disk_device=/dev/sda
Unknown kernel command line parameters "disk_device=/dev/sda", will be passed to user space.
Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
mem auto-init: stack:off, heap alloc:off, heap free:off
Memory: 3074332K/3145336K available (8197K kernel code, 1725K rwdata, 2396K rodata, 1136K init, 1344K bss, 70748K reserved, 0K cma-reserved)
rcu: Hierarchical RCU implementation.
rcu: 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=2.
rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies.
rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
NR_IRQS: 524544, nr_irqs: 440, preallocated irqs: 16
rcu: srcu_init: Setting srcu_struct sizes based on contention.
Console: colour dummy device 80x25
printk: console [ttyS0] enabled
printk: console [ttyS0] enabled
printk: bootconsole [earlyser0] disabled
printk: bootconsole [earlyser0] disabled
APIC: Switch to symmetric I/O mode setup
ExtINT not setup in hardware but reported by MP table
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
tsc: Unable to calibrate against PIT
tsc: No reference (HPET/PMTIMER) available
tsc: Marking TSC unstable due to could not calculate TSC khz
Calibrating delay loop (skipped) preset value.. 15999.84 BogoMIPS (lpj=7999923)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
process: using mwait in idle threads
Last level iTLB entries: 4KB 512, 2MB 8, 4MB 4
Last level dTLB entries: 4KB 512, 2MB 8, 4MB 4, 1GB 0
Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
Spectre V2 : Kernel not compiled with retpoline; no mitigation available!
Spectre V2 : Vulnerable
Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
Speculative Store Bypass: Vulnerable
Freeing SMP alternatives memory: 20K
smpboot: CPU0: Hygon Fake gem5 x86_64 CPU (family: 0xf, model: 0x25, stepping: 0x1)
Performance Events: Broken PMU hardware detected, using software events only.
Failed to access perfctr msr (MSR c0010007 is 0)
rcu: Hierarchical SRCU implementation.
rcu: 	Max phase no-delay instances is 400.
smp: Bringing up secondary CPUs ...
x86: Booting SMP configuration:
.... node  #0, CPUs:      #1
smp: Brought up 1 node, 2 CPUs
smpboot: Max logical packages: 2
smpboot: Total of 2 processors activated (31999.69 BogoMIPS)
devtmpfs: initialized
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>275000 ns
futex hash table entries: 512 (order: 3, 32768 bytes, linear)
NET: Registered PF_NETLINK/PF_ROUTE protocol family
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(1325376000.267:1): state=initialized audit_enabled=0 res=1
thermal_sys: Registered thermal governor 'step_wise'
thermal_sys: Registered thermal governor 'user_space'
cpuidle: using governor ladder
PCI: Using configuration type 1 for base access
HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages
HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page
ACPI: Interpreter disabled.
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>PTP clock support registered
PCI: Probing PCI hardware
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffffffff]
pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
pci 0000:00:04.0: [8086:7111] type 00 class 0x010180
pci 0000:00:04.0: reg 0x20: [io  0x0000-0x000f]
pci 0000:00:04.0: reg 0x30: [mem 0x00000000-0x000007ff pref]
pci 0000:00:04.0: legacy IDE quirk: reg 0x10: [io  0x01f0-0x01f7]
pci 0000:00:04.0: legacy IDE quirk: reg 0x14: [io  0x03f6]
pci 0000:00:04.0: legacy IDE quirk: reg 0x18: [io  0x0170-0x0177]
pci 0000:00:04.0: legacy IDE quirk: reg 0x1c: [io  0x0376]
pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
vgaarb: loaded
clocksource: Switched to clocksource refined-jiffies
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
pnp: PnP ACPI: disabled
NET: Registered PF_INET protocol family
IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)
tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)
TCP: Hash tables configured (established 32768 bind 32768)
UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
NET: Registered PF_UNIX/PF_LOCAL protocol family
pci 0000:00:04.0: BAR 6: assigned [mem 0xc0000000-0xc00007ff pref]
pci 0000:00:04.0: BAR 4: assigned [io  0x1000-0x100f]
pci_bus 0000:00: resource 4 [io  0x0000-0xffff]
pci_bus 0000:00: resource 5 [mem 0x00000000-0xffffffffffff]
PCI: CLS 0 bytes, default 64
platform rtc_cmos: registered platform RTC device (no PNP device found)
workingset: timestamp_bits=62 max_order=20 bucket_order=0
fuse: init (API version 7.36)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler mq-deadline registered
io scheduler kyber registered
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 8250
Linux agpgart interface v0.103
brd: module loaded
loop: module loaded
Loading iSCSI transport class v2.0-870.
st: Version 20160209, fixed bufsize 32768, s/g segs 256
SCSI Media Changer driver v0.25
ata_piix 0000:00:04.0: enabling device (0000 -> 0001)
ata_piix 0000:00:04.0: PCI->APIC IRQ transform: INT A -> IRQ 16
scsi host0: ata_piix
scsi host1: ata_piix
ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1000 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1008 irq 15
e1000: Intel(R) PRO/1000 Network Driver
e1000: Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
igb: Intel(R) Gigabit Ethernet Network Driver
igb: Copyright (c) 2007-2014 Intel Corporation.
igbvf: Intel(R) Gigabit Virtual Function Network Driver
igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
ixgbe: Copyright (c) 1999-2016 Intel Corporation.
ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver
ixgbevf: Copyright (c) 2009 - 2018 Intel Corporation.
ixgb: Intel(R) PRO/10GbE Network Driver
ixgb: Copyright (c) 1999-2008 Intel Corporation.
Fusion MPT base driver 3.04.20
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.20
Fusion MPT FC Host driver 3.04.20
Fusion MPT SAS Host driver 3.04.20
Fusion MPT misc device (ioctl) driver 3.04.20
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor=10,220)
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-pci: OHCI PCI platform driver
uhci_hcd: USB Universal Host Controller Interface driver
i8042: PNP: No PS/2 controller found.
i8042: Probing ports directly.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mousedev: PS/2 mouse device common for all mice
fail to initialize ptp_kvm
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered PF_PACKET protocol family
IPI shorthand broadcast: enabled
Unstable clock detected, switching default tracing clock to "global"
If you want to keep using the local clock, then add:
  "trace_clock=local"
on the kernel command line
ata1.00: ATA-7: M5 IDE Disk, , max UDMA/66
ata1.00: 16514064 sectors, multi 0: LBA
scsi 0:0:0:0: Direct-Access     ATA      M5 IDE Disk      n/a  PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 16514064 512-byte logical blocks: (8.46 GB/7.87 GiB)
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
EXT4-fs (sda1): mounted filesystem without journal. Quota mode: none.
VFS: Mounted root (ext4 filesystem) on device 8:1.
devtmpfs: mounted
Freeing unused kernel image (initmem) memory: 1136K
Write protecting the kernel read-only data: 14336k
Freeing unused kernel image (text/rodata gap) memory: 2040K
Freeing unused kernel image (rodata/data gap) memory: 1700K
rodata_test: all tests were successful
Run /sbin/init as init process
Run /etc/init as init process
Run /bin/init as init process
process '/usr/sbin/m5' started with executable stack
Hello world
m5 mem already mapped.

Expected behavior
This is what we are trying to execute:
#include <gem5/m5ops.h>
#include <stdio.h>
#include "m5_mmap.h"
int main()
{
    m5op_addr = 0xFFFF0000;
    map_m5_mem();
    printf("Hello world\n");
    m5_switch_cpu_addr();
    while (1)
        ;
    m5_exit_addr(0);
}

Therefore I would expect an infinite loop after the "Hello world\n" print.
Host Operating System
Ubuntu 22.04
Host ISA
X86
Compiler used
g++ 11.4
Additional information
This bug is at least as old as the commit 1db206b9d371b14cb9150e37aef444d1d59db025 on stable

I have not changed the switching behavior and I expect this to work, this is still a bug in the simulation.

I have not changed switching behavior and this is still a bug in the simulator, I am using a workaround to avoid this situation. If I had time I would attempt fixing it but for now I will continue to use the workaround.

Hello, my name is Lukas and I’m working with my partner Emily on a final project for our Virtualization class. We are Computer Science at the University of Texas at Austin and currently enrolled in CS360V Virtualization, taught by Dr. Chidambaram (VJ). As part of our coursework, we are required to contribute to a few issues within an open-source repository relevant to the class.
After reviewing the gem5 repository, we believe that the particular issue aligns well with our objectives and skill set and were wondering if we may be assigned to this issue. If that's possible, before proceeding, we wanted to ask if there are any additional details or considerations regarding this issue that we should be aware of. We are committed to completing all three issues by May 6th to the best of our abilities.
Thank you for considering our request.
Emily and Lukas

Awesome! Yes, please feel free to try to tackle this issue. If you have any questions, don't hesitate to ask. @BobbyRBruce has successfully reproduced the issue, but we haven't had the resources to fix it. Hopefully Ivana's comment above gives you a starting point.

Has anyone fixed these bugs? I encountered the same issues while trying to run x86-ubuntu-run-with-kvm.py in my disk-image.

@lllzy040620, I don't think this is fixed. If you know how to resolve it, please feel free to create a PR with your changes. Thank you.

@ivanaamit I resolved this issue by downgrading gem5 from version 24.0.1 to 22.0.1. I believe the problem might have been caused by an incompatibility between the gem-resource's version and gem5.

In fact, I just followed the README to set up Gem5 and Gem5-resource. Details are recorded in this https://github.com/orgs/gem5/discussions/1302.


TN, USA State & County Data is all Zeros or Null

TN USA Data is All Zeros or Null for 3/30/2020.

What file

What file

Timeseries csv

My apologies on not providing enough information.  It is affecting at least Timeseries.csv and data.csv

I have rechecked the files and the missing data is now included in the data sets.

Thank you for following up, I'm glad it's fixed now!


Improve article : 2211.05961v2

Describe the issue
Description: Macro text appearing instead of being evaluated
Feel free to attach a screenshot (or document) link below:
Auto Fill Data - !!! Please do not edit below this line !!!

Id: 47917d28-a8f7-40b2-abb8-a8d67973a53e


Fix/classes

Hey Charlie,
it's me again, I removed some unnecessary (double) css classes.
Best,
Tom

Hi Tom,
Thanks for your work and your PR !
Regards,
Charlie

Hi Tom,
Thanks for your work and your PR !
Regards,
Charlie


feat: add unit test for createLBStatus

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
refers #2400
Special notes for reviewers:

Release note:

NONE

/ok-to-test

Looks good I think, just needs a rebase.

@dulek please take a look now

bump @dulek @pierreprinetti

Please squash the commits before this can be merged.

/approve
I'm leaving approval, will lgtm once it's squashed.

@pierreprinetti @dulek Can you please approve this now? I did the rebase, there is addition of another test in this PR because the authors are adding test in b/w of the file rather than appending things at the end which is the major cause of all this conflicts & errors.

PLease review again @pierreprinetti , I have made all requested changes


Include Python down level validation in CI

We've hit a few times where Python code uses newer 3.10 features that then cause failures in supported down-level versions we only catch during the release pipeline. We should add some CI validation of version features so that we don't end up getting surprised.

We can use black to check for any post-3.8 syntax. @idavis  knows more.


No module named itertools

I am seeing a strange error:
cobe$ cobe init
Traceback (most recent call last):
  File "/usr/local/bin/cobe", line 9, in <module>
    load_entry_point('cobe==2.1.1', 'console_scripts', 'cobe')()
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 519, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2630, in load_entry_point
    return ep.load()
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2310, in load
    return self.resolve()
  File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2316, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "build/bdist.linux-i686/egg/cobe/control.py", line 6, in <module>
  File "build/bdist.linux-i686/egg/cobe/commands.py", line 12, in <module>

  File "build/bdist.linux-i686/egg/cobe/bot.py", line 3, in <module>
  File "build/bdist.linux-i686/egg/irc/client.py", line 67, in <module>
ImportError: No module named itertools

However from the python console:
>>> import itertools
>>> itertools
<module 'itertools' (built-in)>
>>> itertools.count()
count(0)

The above results is after cloning the master branch and running $ python setup.py install

I'm getting the exact same thing. Did you figure out what was going on?
Traceback (most recent call last):
  File "/usr/local/bin/cobe", line 9, in <module>
    load_entry_point('cobe==2.1.1', 'console_scripts', 'cobe')()
  File "build/bdist.macosx-10.10-x86_64/egg/pkg_resources/__init__.py", line 519, in load_entry_point

  File "build/bdist.macosx-10.10-x86_64/egg/pkg_resources/__init__.py", line 2630, in load_entry_point

  File "build/bdist.macosx-10.10-x86_64/egg/pkg_resources/__init__.py", line 2310, in load

  File "build/bdist.macosx-10.10-x86_64/egg/pkg_resources/__init__.py", line 2316, in resolve

  File "/usr/local/lib/python2.7/site-packages/cobe/control.py", line 6, in <module>
    from . import commands
  File "/usr/local/lib/python2.7/site-packages/cobe/commands.py", line 12, in <module>
    from .bot import Runner
  File "/usr/local/lib/python2.7/site-packages/cobe/bot.py", line 3, in <module>
    import irc.client
  File "/usr/local/lib/python2.7/site-packages/irc/client.py", line 67, in <module>
    from jaraco.util.itertools import always_iterable
ImportError: No module named itertools

Ah! jaraco.util.itertools is a great clue. Looks like it's a module that the irc library is trying to pull in. I'll dig a little bit.

Excellent, I can reproduce this now too. Thanks for that second trace, @aferriss.

Well, the good news is that a new version of the irc library fixes it. The bad news is that it adds 13 (!) new dependencies to cobe.
Version 2.1.2 has been uploaded to PyPI and should fix this issue. Thanks to both of you!

Thanks Peter, working great now!

I am still having this issue. Any update? I'm a total noob at this, but heres the error I'm getting:
$ cobe init
Traceback (most recent call last):
File "/usr/local/bin/cobe", line 5, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2707, in
working_set.require(requires)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 686, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 584, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: PyStemmer==1.3.0

@BenP51 You're having a different issue (they look similar because all Python tracebacks look similar). You are missing the PyStemmer module, which cobe requires.
When you install cobe with tools like pip install cobe or easy_install cobe, it should be pulled in automatically. Try one of those and see if it fixes the issue.

I have done that before, didn't work. Un install cobe and followed what you asked. Still not working.
Date: Fri, 9 Oct 2015 07:39:10 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [cobe] No module named itertools (#20)
@BenP51 You're having a different issue (they look similar because all Python tracebacks look similar). You are missing the PyStemmer module, which cobe requires.
When you install cobe with tools like pip install cobe or easy_install cobe, it should be pulled in automatically. Try one of those and see if it fixes the issue.
—
Reply to this email directly or view it on GitHub.


File cannot be downloaded when throughput throttled

Which version of the AzCopy was used?
10.16.0 and 10.20.1
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
azcopy copy "https://.blob.core.windows.net/.pdf***" "C:\test1.pdf" --cap-mbps 10 --log-level INFO --output-type text
azcopy copy "https://.blob.core.windows.net/.pdf***" "C:\test1.pdf" --cap-mbps 10 --log-level INFO --output-type text --block-size-mb 3
What problem was encountered?
File is 13MB. If I try to download, it stucks. There is no result like failed or completed.
How can we reproduce the problem in the simplest way?
try download files bigger than 10 MB and give --cap-mbps smaller than 20.
Have you found a mitigation/solution?
If --cap-mbps parameter is 4 times bigger than --block-size-mb parameter, download will be completed.

@mustafakemalsigirci are you getting any error in the console when running either command? Could you set the log level to DEBUG and share the latest logs in the HOME/.azcopy directory?

Hi @gapra-msft , than you for your response. There is no ant error in console log. Log files are here.

238addd9-5d08-3346-78c5-4ee2044fb899.log
238addd9-5d08-3346-78c5-4ee2044fb899-chunks.log
238addd9-5d08-3346-78c5-4ee2044fb899-scanning.log

It seems like you are running an old version of AzCopy, is this reproducible in the latest as well?

yes, you can repeat in 10.20.1 version as well
Android için Outlookhttps://aka.ms/AAb9ysg edinin

From: Gauri Prasad @.>
Sent: Thursday, September 21, 2023 9:03:26 PM
To: Azure/azure-storage-azcopy @.>
Cc: mustafakemalsigirci @.>; Mention @.>
Subject: Re: [Azure/azure-storage-azcopy] File cannot be downloaded when throughput throttled (Issue #2380)
It seems like you are running an old version of AzCopy, is this reproducible in the latest as well?
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-azcopy/issues/2380#issuecomment-1730057606, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZ4LUACYVO6GKXRWXE435WDX3R6O5ANCNFSM6AAAAAA457TEP4.
You are receiving this because you were mentioned.Message ID: @.***>

There is no any other process. I just run azcopy.

Hi @mustafakemalsigirci I believe the issue here is that --cap-mbps is in megaBITS per second and --block-size-mb is in megBYTES. This is also documented in the azcopy CLI help. If you adjust your cap-mbps parameter and convert it to megaBITS per second, it should resolve your issue. Closing this for now as this is the resolution. In case you are still experiencing the issue after following this advice, please feel free to reopen.

I dont want to use block size parameter. This was work around solution. Why copy fails when cap mbps is set? Could you solve the problem?
Android için Outlookhttps://aka.ms/AAb9ysg edinin

From: Gauri Prasad @.>
Sent: Monday, September 25, 2023 7:18:09 PM
To: Azure/azure-storage-azcopy @.>
Cc: mustafakemalsigirci @.>; Mention @.>
Subject: Re: [Azure/azure-storage-azcopy] File cannot be downloaded when throughput throttled (Issue #2380)
Hi @mustafakemalsigircihttps://github.com/mustafakemalsigirci I believe the issue here is that --cap-mbps is in megaBITS per second and --block-size-mb is in megBYTES. This is also documented in the azcopy CLI help. If you adjust your cap-mbps parameter and convert it to megaBITS per second, it should resolve your issue. Closing this for now as this is the resolution. In case you are still experiencing the issue after following this advice, please feel free to reopen.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-azcopy/issues/2380#issuecomment-1734071964, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZ4LUAEGXDNSS6CDDVFA5OLX4GVEDANCNFSM6AAAAAA457TEP4.
You are receiving this because you were mentioned.Message ID: @.***>

@mustafakemalsigirci ah I see. This will take a little more investigation, but I believe it could be because AzCopy computes a block size without considering the cap mbps parameter. Reopened to continue investigation.

Thank you very much !
Android için Outlookhttps://aka.ms/AAb9ysg edinin

From: Gauri Prasad @.>
Sent: Monday, September 25, 2023 7:59:56 PM
To: Azure/azure-storage-azcopy @.>
Cc: mustafakemalsigirci @.>; Mention @.>
Subject: Re: [Azure/azure-storage-azcopy] File cannot be downloaded when throughput throttled (Issue #2380)
Reopened #2380https://github.com/Azure/azure-storage-azcopy/issues/2380.
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-storage-azcopy/issues/2380#event-10465407715, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZ4LUACNRBAXXVG5FATWI5TX4G2AZANCNFSM6AAAAAA457TEP4.
You are receiving this because you were mentioned.Message ID: @.***>

Curiously I'm getting request size greater than pacer target. When Enqueuing chunk. when using --cap-mbps 32 --block-size-mb 4, as well as --cap-mbps 33 --block-size-mb 4. So the workaround of using a block size 1/8 * the cap doesn't always work.

  I dont know where these people were trained or who hired them but they should all be fired.  Just a terrible toolset

Still failing for me with the latest azcopy and storage explorer. Might be nice if I could download files without slowing my coworkers.

In Linux, by imposing restrictions on the OS side, I was able to avoid download errors.
# modprobe ifb
# ip link set dev ifb0 up
# modprobe act_mirred
# tc qdisc add dev eth0 ingress handle ffff:
# tc filter add dev eth0 parent ffff: protocol ip u32 match u32 0 0 flowid 1:1 action mirred egress redirect dev ifb0
# tc qdisc add dev ifb0 root handle 1: htb default 10
# tc class add dev ifb0 parent 1:1 classid 1:10 htb rate 10mbit

azcopy command execute..

# tc qdisc del dev eth0 ingress handle ffff:
# tc qdisc del dev ifb0 root handle 1: htb
# rmmod ifb


check test

You have not changed the workflow. It still only compiles the application and does not run the tests. I am also not sure if changing the xls files is enough. I think there is something wrong with the test cases as well.


Can we delete branch "improvs"?

It hasn't been touched for ages. Maybe it was just forgotten after a merge.

Sure thing, I'll go ahead and delet it


Developing process

Hi guys!
Currently i am working on some redux lib and trying to discover your really great project.
And i don't understand how you develop it?
I see examples and commands in package.json, but i have to rebuild the whole lib each time i change something.
I can plug redux-form to my own example and use it from src or use webpack alias, but I think i miss something, give me advise please.

@erikras @mihirsoni Can you share your experience?

@VladimirPal for this type of stuff it'll probably be better if you ping @erikras at Twitter


A11y_AzureDataStudio(Schema,Dacpac,Backup)_ExtractDacpac_ExtractDacpacSettings_Keyboard:The first focus is present on the next button.

“Check out Accessibility Insights!- Identify accessibility bugs before check-in and make bug fixing faster and easier.”
#A11yMAS; #A11yTCS; #A11y_ADS_Schema_Dacpac_Backup; #Azure Data Studio; #DesktopApp; #Win10; #MAS2.4.3; #Keyboard;
Environment Details:
Application Name: Azure Data Studio
Application Version:1.10.0-insider (user setup)
Commit: 1ff9a2e
Electron: 4.2.7
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362
Additional Details:
MAS References:MAS2.4.3
Repro Steps:

Launch Azure Data Studio application.
Connect to server with windows credentials.
Navigate to Extensions from left menu.
Search & install Dacpac extension.
Navigate to Connections from left menu.
Expand the server connected in step 2.
Right click an on prem database and select Data-tier application wizard from Context menu.
Select second radio button.
Navigate till next button & hit enter.

Actual:
On hitting enter from step 9 , the page "select Extract Dacpac Settings" opens and the focus is present on the "Next" button.
Same issue is observed for:
1.Export Bacpac Settings:
Follow the exact above steps but select the fourth radio button
Expected:
The focus as soon as the page is opened should be present on the first interactive control ie"Source server" drop down.
Recommendations:
Refer below link which is repository of bug fixes code snippets: https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
If the keyboard user needs to change the data that is autocompleted in the fields, he would have to take an extra effort in doing so. As well as the flow of the content will not be know to the user.
MAS Reference:
MAS2.4.3:https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={0de7fbe1-ad7e-48e5-bcbb-8d986691e2b9}
Attachment for Reference:
#6798A11y_AzureDataStudio(Schema,Dacpac,Backup)_ExtractDacpac_ExtractDacpacSettings_Keyboard.pptx

The issue still reproduces in the below version
Version: 1.12.0-insider
Commit: a584aca96997a18ecedee73a575536332e542718
Date: 2019-09-19T07:58:50.448Z
VS Code 1.38.0
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362
#6798 A11y_AzureDataStudio(Schema,Dacpac,Backup)_ExtractDacpac_ExtractDacpacSettings_Keyboard.pptx

Seems to have regressed again!

@udeeshagautam yes in-case the user wants to change the auto filled fields, the focus needs to be present at the first interactive element.

@fsteffi thanks for the clarification but I want to mention that the focus can go to fields through Shift + Tab or equivalent if someone explicitly wanted to change but for regular flow they shouldn't need to change. that's why the question on where the default focus should be.

@udeeshagautam the shift+tab navigation can be usesd but it would require unnecessary efforts that can be avoided by simple navigation. Even if they don't want to change the details , the first focus needs to be on the first dropdown this would help screen reader users navigate through all the information present on screen.

We discussed with Ryan and Alexandria on the workaround that

controls can be accessed through shift + tab
The page would announce itself when changed (so that the screen reader user is aware that the current focus after clicking the next button on previous page changed)

This is okay workaround to live with for now as per Ryan hence we are clsong the bug. Please let us know if the worakaround doenst work.


let VideoDisplayStore/VideoPanel understand existence of multiple videos (currently only understand one)

needed by #113

Question: how to set activeVideoId? In other words, how to know which video to display?

next

[ ] when tap "play video"
[ ] when tap a log entry, and want to seek into the video


Flutter Desktop: Allow using native Flutter widgets in MenuBar applications

Use case
Many desktop applications utilize the menubar to give customers direct access to sticky-functionality. On MacOS menubar applications tend to be on the top right side of your screen and have customizable UIs (Not to be confused with the typical left hand side menubar list). For example, here's a screenshot from 1Password:

Flutter currently supports adding a menubar to your desktop applications but AFAIK there's no way to customize the UI of that menubar besides just adding lists and items.
If you are writing a desktop application in Swift, the menu bar's UI is fully customizable where you can specify its window size and add images, buttons, lists and anything you would normally add to the main application's window. See this tutorial for an example: https://medium.com/macoclock/how-to-make-a-macos-menu-bar-app-bfdbbcd76077
Proposal
It would be great if we can write menubar applications with fully supported Flutter widgets on desktop applications such as the one above.

This is a duplicate of https://github.com/flutter/flutter/issues/23600, which I'm currently working hard on.  Also, take a look at the design proposal.

Thank you for the links!

@gspencergoog the proposal is talking about cascading menus which on macOS is typically on the left hand side of the bar. What this proposal is for is actually the right hand side of the bar where clicking on the application icon toggles a UI that is not restricted to menu items, but to any widget you'd like to draw on a screen.
I'm still reading the issue/design-doc, but will the proposal allow us to inject a flutter widget of any kind to a menu bar screen?
If not, let me know if I should re-open this issue. Thanks!

Ahh, the re-use of the term "menu bar items" confused me.  Indeed, my proposal doesn't address building a system menu-bar add-on with Flutter, only building a (regular) menu bar with items in it.
Sorry I didn't read more closely. Reopening.

I have created a GitHub Template for building macOS menu bar application with flutter using NSStatusBar and NSPopOver
You can check out this repo if interested:
https://github.com/mynameiskenlee/flutter_macos_menubar_example

This is the closest thing I can find https://github.com/troncoso/flutter_menubar_app_example
I'm also surprised this issue hasn't gotten the attention that much. But I do add a vote to this proposal.

Passing the 1 year mark, I'd love to ask if there are any updates here. Thanks!

I found another source here: https://blog.whidev.com/menu-bar-extra-flutter-macos-app/, but it doesn't work as expected. The icon renders at the top, but clicking it doesn't trigger any action.


tilegrid.json: Update utilities to use latest format

The tilegrid.json conversion was incomplete, the following utilities relied on the old format:

fasm2frame.py
segprint2fasm.py
segprint.py

#139 adds bridge fields and code to solve this in the short term, but in the long term utilities should likely converge.  Suggestion to resolve is to add cabilities to the prjxray library that hide the underlying file format from the various utilities, and expose a usable API for interacting with the underlying database.

https://github.com/SymbiFlow/prjxray/pull/159 makes some progress on this

#167 converts fasm2frame.py and bits2fasm.py

Close this? There's a little lingering in htmlgen, but that has a dedicated issue (https://github.com/SymbiFlow/prjxray/issues/173)

utils/segprint.py is not converted yet.


BREAKING CHANGE(web): Switch Button to v3 design tokens and remove inverted variant #DS-1445

Description

Additional context

Issue reference

coverage: 79.191%. remained the same
when pulling c83e7df30b0a26ad363f492690f5df074c4f1e71 on bc/v3-tokens-button
into 3fdd3bad682a794b94d81e9e91f64f5df1a412ed on feat/v3-tokens-tabs.


[type: refactor] refactor cache-plugin.

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #3136 (f0ee560) into master (8f1aeaf) will decrease coverage by 0.47%.
The diff coverage is 31.57%.

@@             Coverage Diff              @@
##             master    #3136      +/-   ##
============================================
- Coverage     58.61%   58.13%   -0.48%
+ Complexity     4485     4446      -39
============================================
  Files           711      713       +2
  Lines         20252    20289      +37
  Branches       1863     1865       +2
============================================
- Hits          11870    11795      -75
- Misses         7338     7446     +108
- Partials       1044     1048       +4

Impacted Files
Coverage Δ

...va/org/apache/shenyu/plugin/cache/CachePlugin.java
0.00% <0.00%> (ø)

...apache/shenyu/plugin/cache/config/CacheConfig.java
50.00% <ø> (ø)

...ache/shenyu/plugin/cache/read/CacheReadPlugin.java
0.00% <0.00%> (ø)

...g/apache/shenyu/plugin/cache/utils/CacheUtils.java
22.22% <ø> (ø)

...u/plugin/cache/handler/CachePluginDataHandler.java
46.87% <30.00%> (ø)

...ava/org/apache/shenyu/common/enums/PluginEnum.java
96.00% <100.00%> (ø)

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
68.75% <0.00%> (-31.25%)
:arrow_down:

...admin/controller/ShenyuHttpRegistryController.java
77.77% <0.00%> (-22.23%)
:arrow_down:

...in/disruptor/RegisterServerDisruptorPublisher.java
52.94% <0.00%> (-11.77%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
52.12% <0.00%> (-11.71%)
:arrow_down:

... and 33 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 8f1aeaf...f0ee560. Read the comment docs.


weighted Transformer

There is a new paper out with a faster learning and bit bit better BLEU score for the transformer architecture called Weighted Transformer Network for Machine Translation:
https://arxiv.org/abs/1711.02132
but i think there is no open source implementation available

Thank you


core: fix: using async rate limiter methods in async code

Description: Replaced blocking (sync) rate_limiter code in async methods.
Issue: #26913
Dependencies: N/A
Twitter handle: no need 🤗

Thank you @esciara


Can't install R kernel in Jupyter Lab Desktop app

I have always used this procedure inside an R session for the standard jupyter lab R kernal installation:
install.packages("devtools")
devtools::install_github("IRkernel/IRkernel")
IRkernel::installspec()
Anyway, the same procedure seems not to work for Jupyter Lab Desktop app.
Any help is appreciated. Thanks

To install R Kernel in JupyterLab Desktop follow the instructions in https://github.com/jupyterlab/jupyterlab-desktop/blob/master/user-guide.md#customizing-the-bundled-python-environment (i.e. set appropriate permissions to the environment) but then at the point, when %pip install scikit-learn example is suggested please run %conda install -c conda-forge r-irkernel instead. Please note that this will install a new copy of R from conda (which may use up a bit of space).
Please leave a comment sharing your experience: did it work for you? Is this what you would expect? Should we include it in the user guide, or do we need a different solution?

I've tried this (on Windows 10) and it seems to have worked.
However, it seems like I can only pick one kernel per notebook. Is it possible to use the R and python kernels side-by-side?

Kind of. You can install rpy2 to access R from the Python kernel and then use magics see https://rpy2.github.io/doc/v3.4.x/html/generated_rst/notebooks.html

It would be great to have details of how to install alternative kernels in the README or at least a link from the README to some instructions.
I've just followed this through on macOS with success.

Kind of. You can install rpy2 to access R from the Python kernel and then use magics see rpy2.github.io/doc/v3.4.x/html/generated_rst/notebooks.html

let's try

open ~/Library/jupyterlab-desktop/jlab_server, find under it share/jupyter/kernels/
install kernel (I just did it with https://github.com/evcxr/evcxr/tree/main/evcxr_jupyter)
copied installed files into kernel directory

 $ butuzov  ~/Library/jupyterlab-desktop/jlab_server/share/jupyter/kernels
 > tree
.
├── python3
│   ├── kernel.json
│   ├── logo-32x32.png
│   ├── logo-64x64.png
│   └── logo-svg.svg
└── rust
    ├── kernel.js
    ├── kernel.json
    ├── lint-LICENSE
    ├── lint.css
    ├── lint.js
    ├── logo-32x32.png
    ├── logo-64x64.png
    ├── logo-LICENSE.md
    └── version.txt

2 directories, 13 files

now you have new kernel and you can use it!


Unable to Launch FancyZones Layout Editor

Microsoft PowerToys version
0.60.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones Editor
Steps to reproduce
Attempt to launch FancyZones Layout Editor.
✔ Expected Behavior
Launch FancyZones Layout Editor.
❌ Actual Behavior
Error message popped up requesting that I report this bug.  Unable to proceed and open FancyZones Layout Editor.
Other Software
No response

/reportbug

Possibly a duplicate of #19223. We should check this when we have the bug report.


CP-24819 Enum now has 3 arguments

Commit 3494cda409dd7529c02ce599cda60300f18c7ea1 in xen-api.git
introduced a change to the Enum data constructor, which now takes 3
arguments. This requires changing it here. The new argument is simply
being ignored.
Signed-off-by: Christian Lindig<EMAIL_ADDRESS>

Looks good thanks!


merged impl of allow un-'shared' refinements #7037

I've rebased the work on #7037 after pulling a bunch of the changes on that branch back to master. I've done everything possible to minimize the diff.
This was a lot of work because this is a huge patch and there were a lot of conflicts, and I can't guarantee its's 100% working still.

This PR has been closed as a result of moving Ceylon to the Eclipse Foundation, not as a judgement of its value. We are unfortunately unable to restore it ourselves, but if you feel this PR should be reopened, please rebase your work on the current master and create a new PR. Thanks, and sorry for the inconvenience.


Device name resolution fails with multiple common words.

I have a lot of devices like
Floor Room, for example "Ground Kitchen".
So there will also be
1st Kitchen
Ground Bath
1st Bath
etc...
Tahoma doesn't let me call up these names, as there is no word that occurs only in one of them.
Would it be possible to allow for quote strings to be used in a future version?
Like
open sunscreen "1st Kitchen Left Atrium" (where 1st Kitchen Left Atrium is the name of the device registered with Tahoma's servers?
best
Tobias

Yes I could make it like I have made it for sensors.
I have made it just for sensors, because we can ask for many sensors in one time with just a part of the name and a specific sensor with [""] and because we can have many sensors in the same room.
I will try to make it for other devices(not only sensors) and let you know, but for now, there is always a solution to find the unic word. For instance :
1st Kitchen --> kitchen
Ground Bath --> ground
1st Bath -- bath.
I will make it and give you a zip file to test and I wil publish it if it's working. I think next week. If you have any other suggestions let me know now, because when I edit the code the longest work is to publish on github and pypi because I have to modify the code for each and it's the longest part. Excuse me for my english ;-)

That would be awesome!
I'm currently working on a little UI tool for Windows to control my sunscreens - this "issue" is the only problem I have right now :)
If I get it done, I'll host it on Github, maybe it will be useful for others, too.

Hello, could try this zip file and let me know if you find a bug ?
Thanks
tahoma-main.zip

It works great, thanks so much!!
One small thing:
If the name of the device is also part of the name of other devices, I need to write 'Name'. If it is not, then "Name".
Would it be possible to make this consistent?
Also a small typo: "Choose a UNIC part" should be UNIQUE.
See the print from console below.
F:\Portable Applications\tahoma>python3 tahoma.py close sunscreen "Erker"
There is more than one match. The  you gave is not exact. Choose a UNIC part of word from this results as  argument or use [''] with the full name : ['EG Erker links', 'EG Erker rechts ', 'EG Erker mitte', 'Erker']
See tahoma --list-names for help.
F:\Portable Applications\tahoma>python3 tahoma.py close sunscreen 'Erker'
Output action : CLOSE sunscreen Erker
with url : io://2026-9407-8819/5862570
F:\Portable Applications\tahoma>python3 tahoma.py close sunscreen "Kueche links"
Output action : CLOSE sunscreen Kueche links
with url : io://2026-9407-8819/5642491
F:\Portable Applications\tahoma>python3 tahoma.py close sunscreen 'Kueche links'
There is no match. The  you gave is not exact. Did you mean : ['EG Erker links', 'EG Erker rechts ', 'Schlafzimmer ', 'EG Erker mitte', 'Balkon', 'Kueche vorne', 'Studio', 'Kueche links', 'Erker', 'Wohnzimmer', 'Bad', 'Treppenhaus'] ? Choose a UNIC part of word from this results as  argument or use [''] with the full name
If you don't find your device in this results try tahoma --getlist
See tahoma --list-names for help.

OK I will correct this on next update. Thanks


BoundTreeView on Wisej: child icons with wrong left spacing

BoundTreeView on Wisej: child icons with wrong left spacing.
The spacing is correct on drag & drop but is wrong again as soon as the form is refreshed.

This happens on duplicate nodes.

It was cauused by an unfiltered double call to BindingContextChanged event. Solved by pull request #101

Is showing again after #116

Fixed by Wisej release.


IronValidatorBehavior overridden method not called

IronValidatorBehavior.validate is called in JS but the Dart code of the overridden validate method isn't called.
https://github.com/bwu-dart-contributing/polymer_elements/blob/demo2/demo/web/iron_validatable_behavior/cats_only.dart#L25

In the iron-validatable-behavior it seems to work. Investigating further ...

The difference is that in the iron-validatable-behavior validate(value) is called directly on the Dart instance of <cats-only> while in iron-validator-behavior it is called from the JS code of IronValidatatorBehavior https://github.com/dart-lang/polymer_elements/blob/master/lib/src/iron-validator-behavior/iron-validator-behavior.html#L57-L57

Can you try adding @eventHandler to that method? I think the issue is just that the method wasn't being exported to the JS Element, and since its a JS behavior thats where it looks.

Yup, that works. Why, oh why, didn't I think of that myself :scream_cat:


Documented precision keyword argument of GeoHash GIS function.

To be backported to 1.9 and 1.10.

By the way, at this point, we don't update the 1.9 docs except for critical updates so as not to introduce untranslated text in the translated docs.


Remove console logging from release builds

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


Update Monitor Query Samples, Quickstarts, and Documentation based on final consistency review

Tracking issue to update all Samples and related documentation based on the final September Release consistency review
/cc @scottaddie

[ ] Move DateTimeRange to Azure Monitor Query
[ ] Throw exception on partial error
[ ] Add new option in LogsQueryOption to disable throwing exception on partial error
[ ] Include an enum LogsQueryResultStatus in LogsQueryResult to indicate if the result is success, failure or partial failure.
[ ] Retain code and message only in ResponseError (core type). Remove all other fields and update ToString() method to include details available in inner error.

@nisha-bhatia PTAL

Related: https://github.com/Azure/azure-sdk-for-net/issues/23580


More examples of lightning mainnet applications

Hi
Added another example of lightning applications where one can pay with lightning and also instantly cash out using lightning.

Hej, thanks for the link. This is not meant to be a directory of individual apps, but I'll put a link to https://lnapps.info/ there instead.


Detaching ItemsControl multiple times crashes

I've found out that detaching ItemsControl from the parent and then attaching it to the same parent again will crash it when we try to detach again.
Managed to reproduce it in ControlCatalog with such codebehind:
    public class TestVm
    {
        public string Name { get; set; }
    }

    public class ButtonPage : UserControl
    {
        private readonly Decorator _panelHost;
        private readonly ItemsControl _panel;

        public ButtonPage()
        {
            AvaloniaXamlLoader.Load(this);

            _panelHost = this.FindControl<Decorator>("PanelHost");
            _panel = this.FindControl<ItemsControl>("Panel");

            _panel.Items = new List<TestVm>
            {
                new TestVm { Name = "Test 0" },
                new TestVm { Name = "Test 1" },
                new TestVm { Name = "Test 2" },
                new TestVm { Name = "Test 3" }
            };
        }

        public void MovePanel(object sender, RoutedEventArgs e)
        {
            _panelHost.Child = null;

            _panelHost.Child = _panel;
        }
    }

And XAML:
<Decorator x:Name="PanelHost">
      <ItemsControl x:Name="Panel">
        <DataTemplate>
          <Border BorderThickness="1" Background="{DynamicResource ThemeBorderMidColor}"
                  BorderBrush="{DynamicResource ThemeBorderMidColor}" Margin="0,0,2,0">
            <StackPanel Orientation="Horizontal">
              <TextBlock Margin="4,0,0,0" Text="{Binding Name}" />
              <Rectangle Margin="2,0,0,0" Width="1"
                         Fill="{DynamicResource ThemeBorderMidColor}" />
              <Panel Background="#373737" />
            </StackPanel>
          </Border>
        </DataTemplate>
      </ItemsControl>
    </Decorator>

After calling MovePanel once all items in ItemsControl will get Parent set to null. Second call will crash with: https://gist.github.com/MarchingCube/055e69b9737157f986fec5334de0d127

Ok, worked out what's happening here:

ItemsControl is detached, along with the ContentPresenters which display the items.

ItemsControl.LogicalChildren remains unchanged - it contains the children of each ContentPresenter

ItemsControl is reattached, ContentPresenter.OnAttachedToLogicalTree()  is called which resets the child creation state: we're now in a new tree, so we need to re-evaluate the DataTemplate which produced the Child

ItemsControl.LogicalChildren remains unchanged

A measure takes place, ContentPresenter.UpdateChild() is called which re-evaluates the DataTemplate, creating a new control. The old control is removed

ItemsControl.LogicalChildren remains unchanged, but now the control it contains has been removed

The ItemsControl is detached
The ItemsControl is re-attached. OnAttachedToLogicalTree is fired along the added tree, but the tree now contains controls in ItemsControl.LogicalChildren that have actually been removed
It throws, this is invalid state

This is very similar to #3328, but with a different cause. It only occurs in ItemsControl and not e.g. ListBox because in ListBox a ListBoxItem container is added to the logical tree instead of adding the control directly.


Adds deprecated flag

Adds a deprecated flag to the frontmatter of articles, similar to the Preview flag.
Closes #4852

@sabinadams can you pls request a review from @nilubava when you're ready with this PR?


XMPP PubSub

Please add support for XMPP.
By adding support for XMPP, I namely mean to Atom Over XMPP (XEP-0277 and XEP-0472) which is utilizing XEP-0060: Publish-Subscribe (PubSub) which allows to host "rich" content on XMPP.
This is a visual demonstration to prove that subject matter https://video.xmpp-it.net/w/vNqcMooy3pqRAZ8Yb8grr1
Rivista XJP is an HTTP gateway to deliver posts from the XMPP network.
See also:

https://xmpp.org/extensions/xep-0060.html
https://xmpp.org/extensions/xep-0277.html
https://xmpp.org/extensions/xep-0472.html
https://blasta.woodpeckersnest.eu/help/about/xmpp/pubsub
https://join.movim.eu/

For example, the journal at https://mov.im/blog/edhelas is not hosted at mov.im; rather, it is hosted inside an account at XMPP server movim.eu which is conveyed by the Movim instance at mov.im.
Please join to JDev group chat if you want more help or information https://search.jabber.network/search?q=jdev

This does not seem to be within the scope of the project.

I would argue, and state that:
XMPP PubSub has a structural form. Each node contains items and each
item is represented by an ID (i.e. Item ID).
The standard by which Atom Over XMPP is designed is Atom Syndication
Format, which is parsable by Lagrange.
I have made a plugin for Dillo to handle XMPP PubSub.
@.***/thread/JF6NB5UXXYB6D7GYCAD5FDZ6WTLFQJBO/
This is indeed a start of observation, and I am waiting for
feedbacks from the people of the Dillo community.
In what circumstances may I raise this subject matter again?

The link is
https://lists.mailman3.com/hyperkitty/list/dillo-dev___mailman3.com/thread/JF6NB5UXXYB6D7GYCAD5FDZ6WTLFQJBO/
Replace ___ by @


feat: use sikula derive

Also, clean up some compiler warnings.

I also split up the test in order to see what exactly fails.


GradleKotlinScriptTest: Temporarily disable the test on Travis

For unknown reasons, Travis has problems downloading
gradle-kotlin-dsl-5.1.1-20190108191351+0000-all.zip, although both
locally and on AppVeyor the test passes. So just disable it for now.
[1] https://travis-ci.com/heremaps/oss-review-toolkit/builds/135240146#L3110
Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

Superseded by https://github.com/heremaps/oss-review-toolkit/pull/1942.


Credentials in some cases are appended without newline

I had an issue with the action today where lines to the .config/git/credentials were appended without newline.
Example:
https://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET@github.comhttps://foo:REMOVED_SECRET<EMAIL_ADDRESS>
I'm using:

A self-hosted runner running Amazon Linux 2
setup-git-credentials v2.0.6

I solved it by removing the credentials file and re-running the ci, for some reason this time it decided to add newlines, but I have no idea why and what is the cause of this.
<EMAIL_ADDRESS><EMAIL_ADDRESS>
I can provide more info if needed, let me know.

I solved it by removing the credentials file and re-running the ci, for some reason this time it decided to add newlines, but I have no idea why and what is the cause of this.

Do you mean you removed the github secret and re-created it? I can't imagine what would cause this, except for wrong data in the github secret itself.
Maybe on a Windows runner there might be issues with Unix newlines, but even that would be surprising to me.

I mean I moved ~/config/git/credentials to ~/config/git/credentials.back and reran the ci. I agree it's very weird, but it kept failing before and worked after this fix.

Unlike the GitHub-hosted runners, self-hosted runners keep their state. I don't think setup-git-credentials takes that into account, and instead just assumes to start with a clean state every time. Running this action multiple times will just append the secret over and over again to the file.

I was wondering something similar regarding the multiple lines. I'm not sure if this is intended, but in the code I'm seeing the a flag being used on fs.writeFile. (https://github.com/fusion-engineering/setup-git-credentials/blob/master/src/main.ts#L19)
Assuming I have the right docs (https://nodejs.org/api/fs.html#file-system-flags) this means new values are appended to the existing file.
Would it be better to replace the existing value instead? I think this would be flag w?

We should only add things that aren't already there. But right now this action simply isn't designed to be used in a self-hosted runner where the state is kept between runs.

Ah, I see, we also weren't adding a trailing newline, so that's why all the credentials ended up duplicated on a single line.
#12 should fix this.


Plots: Line 5

https://github.com/NQCD/NonadiabaticMolecularDynamics.jl/blob/685eb31fd86a54c6f21ef75f4e61bdd389960dd4/docs/src/nonadiabaticmodels/analyticmodels.md#L5
I really like this page.
What does this tip mean for anyone using the code? Do they have to load them in with the `using' statement? If so, can you put that into the examples, so it's really blindingly obvious?

I think it would be best to show things like that. The examples need to work exactly as they are displayed in the manual without doing anything extra.


chore: Add issue template

🛠 Fixes Issue
Closes #4

👨💻 Changes proposed

Added issue templates of types

Docs issue/request
Bug report
Feature request

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
Add feature label to the issue for auto labeling. The rest two (bug and documentation) are by default there

looks great! ty

Welcome, just don't forget to add the feature label (As I mentioned above in the note) ;)


initial version, tested locally with my API key

Josh, I thought you had merged this!

Thank you. Josh. I hope all is well with you.


spk init -f loaded configurations adds ">-" continuation sequence that might have issues with spk commands

Possible issue from a customer. We should verify:

it is suspected that if the file is provided during "spk init", the init process will form a new config.yaml file that contains ">-" continuation sequence for manifest properties.  This will cause the pipeline created by "spk hld install-manifest-pipeline" to fail.
Removing these characters and regenerating the pipeline fixes the issue.

Moreover errors given my spk are not helpful

In case of an error values provided in the manifest, error does not have sufficient level of detail to understand what the issue is.
info:    Attempting to authenticate with Azure DevOps organization 'Epi Change Feed Org' using PAT '************************************************qjdq'
error:   Error connecting Azure DevOps Git API
error:   Error occurred installing pipeline for HLD to Manifest pipeline
error:   Cannot read property 'value' of null

@yradsmikham have you been able to verify this?

@andrebriggs I am unable to reproduce the error that the user is seeing. After being able to generate a config.yaml with ">-", I was able to get past the authentication error shown.
Do we know where the ">-" is appearing in their config.yaml?

the >- e.g.
key: >-fakeSJGTxa8Rq+0ZtAF33LAr0hh+CamlzdBFz27wRQupLde4DmwDb5hBGRd930nQYm6j0ZiEN5Myo67Y39PtA==

is generated by yaml.safeDump function to avoid this, we can add lineWidth option.
e.g.
aml.safeDump(data, { lineWidth: 5000 });

having lineWidth as a large integer.

@dennisseah the problem is, I was able to successfully authenticate with Azure DevOps with the ">-" appended to the beginning of the key parameter. I'm wondering if the ">-" was maybe part of the access_token variable? In which case, when the execution occurs, it was unable to parse the PAT and caused the authentication to Azure DevOps to fail.
Either way, if that's the case. We can bump the lineWidth. I was just unable to verify.

I just tried appending ">-" in other areas of the config.yaml (i.e. before the access_token) and was still able to successfully authenticate with Azure DevOps.
config.yaml:
azure_devops:
  access_token: >-
    <access_token>
  hld_repository: 'https://dev.azure.com/yvradsmi/spk-services/_git/fabrikam-hld'
  manifest_repository: 'https://dev.azure.com/yvradsmi/spk-services/_git/fabrikam-manifests'
  infra_repository: 'https://dev.azure.com/yvradsmi/spk-services/_git/fabrikam-tf-template'
  org: yvradsmi
  project: spk-services
infra:
  terraform: v0.12.6
  helm: v2.14.3
  git: 2.17.1
  az: 2.0.71
introspection:
  dashboard:
    image: 'mcr.microsoft.com/k8s/bedrock/spektate:latest'
    name: spektate
  azure:
    account_name: ydawgie
    table_name: storage-account-table-name
    partition_key: storage-account-table-partition-key
    key: >-
      <key>
    source_repo_access_token: source_repo_access_token
    service_principal_id: <sp_id>
    service_principal_secret: <secret>
    subscription_id: <sub_id>
    tenant_id: <tenant_id>
    resource_group: yvonne
key_vault_name: null

output:
 ✘  ~/microsoft/yradsmikham/spk   master ●  spk hld install-manifest-pipeline
info:    Attempting to authenticate with Azure DevOps organization 'yvradsmi' using PAT '************************************************bcjq'
info:    Successfully connected to Azure DevOps Git API!
info:    Fetched DevOps Client
info:    Attempting to create new pipeline: fabrikam-hld-to-fabrikam-manifests defined in repository:https://dev.azure.com/yvradsmi/spk-services/_git/fabrikam-hld, branch: master, filePath: manifest-generation.yaml
info:    Creating pipeline for definition

Yes, @yradsmikham >- will not cause problem when reading the value. It is just a convention that yaml has when the string is too long.

Okay, so maybe as a workaround for now, we bump the lineWidth to something like 5500. This should hopefully allow the customer to avoid running into the issue.
Thoughts?
@dennisseah @andrebriggs


Write all fields on insert action

Write both standard and extended fields on insert action
fix #3411

Merged, thanks for the fix. Do you think there are any other corner cases that we need to test to make sure queries are working correctly?

There might be, but now I hope unlikely.
But testing is never too much.


Question about how a queue working

Is the same row in queue table picked twice or more for task processing if processing mode is USE EXTERNAL EXECUTOR and task takes time to executes?
if so how to avoid it?

If a task is picked up then it immediately postponed. Postpone duration is specified in https://github.com/yoomoney/db-queue/blob/master/db-queue-core/src/main/java/ru/yoomoney/tech/dbqueue/settings/FailureSettings.java#L21
So if task proccessing takes longer than postpone duration then it will be picked up second time.
This behaviour is relevant to all tasks processing modes.
You can avoid it by specifiying long postpone duration.

much obliged.


Send user second email

When a user sends a comment, we will send a confirmation email to ourselves and them to let them know we will be in contact within ** hours.

If the first email is sent then a confirmation email will also be sent to the user letting them know how long until we reply.


Questions about this project

First of all, congratulations on this project.
I would like to ask if the current Python API implementation covers all of the Sourcetrail DB kind of data/fields, or if some features are still missing.

Hello @pidgeon777,
Thanks for the feedback :)
Yes, this API covers all the basic Sourcetrail data types as you can see here. These types directly come from
the original SourceTrail SQLite tables.
You should be able to manipulate all the types, but some high-level API might be missing. If you have any specific use cases in mind, we could consider adding these functionalities to the existing API.

Closing the issue. Please reopen it if a specific feature is missing.


untrack stackdumps; *.stackdump

Summary

Untracking StackDump files through .gitignore
Most of the programs like shell (bash) crashes it generates StackDump; *.stackdump file(s)
Such files are only for low level debugging purpose and shouldn't be tracked
PS: When using integrated terminals on IDEs it's common to have these files especially on Win m/c :)

Changelog
[Internal] [Changed] - Untracking Stack Dumps; *.stackdump files
Test Plan

[NO-CODE] Diff

Note: Using [skip ci] to avoid ci compute wastage. Init CI workflow manually if necessary.


Duplication of query params

craft.pagination.render(
  pageInfo,
  'numeric',
  {
    includePrevNext: true
  }
)

If I have this path:
http://localhost/finishes?search=hello
and the I click for example next page link I get this:
http://localhost/finishes/p2?search=hello?search=hello

Fixed in v1.0.2


Document async iterators and generators

Cross-filed from https://bugzilla.mozilla.org/show_bug.cgi?id=1483152
Documentation for https://tc39.github.io/proposal-async-iteration/
(this shipped in Firefox 57, see bug 1352312)
Iteration protocol reference page:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Iteration_protocols needs to talk about the async iteration protocol.

Symbol.asyncIterator

Docs could probably be derived from Symbol.iterator https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol/iterator
It's already listed on the Symbol page: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol#Well-known_symbols
New page to be created here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol/asyncIterator
Compat data update here: https://github.com/mdn/browser-compat-data/blob/master/javascript/builtins/Symbol.json#L58
New interactive example here: https://github.com/mdn/interactive-examples/tree/master/live-examples/js-examples/symbol

for-await-of

Needs to be listed here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements#Iterations
New reference page here: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for-await-of
New compat data entry here: https://github.com/mdn/browser-compat-data/blob/master/javascript/statements.json
New interactive example here: https://github.com/mdn/interactive-examples/tree/master/live-examples/js-examples/statement

Async generators
We have https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*, maybe it would be worth doing an extra reference page about async function* ? Then you would create e.g. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function* maybe. Also add compat data and interactive example again, like for the other two above.
APIs that use async iterators / generators
I don't know all the APIs that use async iteration, but it seems like Streams are async iterables, so it might be interesting to look into our streams docs and update them if necessary https://developer.mozilla.org/en-US/docs/Web/API/Streams_API
Guide page updates

We have https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Iterators_and_generators
Unfortunately we have no dedicated guide page yet on async JS programming. We want to create that at some point, though. See https://bugzilla.mozilla.org/show_bug.cgi?id=1305261
More brainstorming on that here: https://docs.google.com/document/d/1ko8Xt5JaFVuXjEOHSyhw8MaxKPTbKiX6Qc7EXtczKUA/edit?ts=5b55b98b#heading=h.5tv0p4d6vqmu

Misc

Joe Medley contributed this: https://github.com/mdn/interactive-examples/pull/1036, check if it is integrated nicely.

Hey @chrisdavidmills! I'm actually working on getting this list done with @Elchi3 and Daniel Ehrenburg over here - we've been able to complete a lot of the items on this list.  Feel free to jump in over there and help out!

@jahzielv that's wonderful — thanks for the heads-up!
I will jump in if I get any time, although the MDN JS docs in particular are more @Elchi3 's area of expertise. You are in good company already ;-)


Setting DPI for the G500s triggers assertion

I have the Logitech G500s and running the dpi set command causes an assertion error.
$ sudo tools/ratbag-command dpi set 800 /dev/input/event5
ratbag-command: libratbag.c:925: ratbag_resolution_set_dpi: Assertion `profile->device->driver->write_resolution_dpi' failed.

I think this happens because the operation is not implemented.

indeed, we can't change the hidpp10 resolutions yet, still figuring out how the profile looks exactly in memory

This reminds me a question I have about resolutions in libratbag. What is "dpi set" supposed to do exactly?

Change the resolution for the current mode, in the (current) permanent profile?
Switch to a mode with the corresponding resolution?
Set the current resolution as a temporary setting?

I guess it is the first one. But the third would be interesting too for changing the resolution while playing one game or for implementing a software "dpi shift" button.
The second one is problematic. The windows software tries to do it when clicking on a mode but it does not work correctly. What it does is just setting the current resolution (with 0x63), and not even bothering setting the LEDs accordingly. The problem is that the commands 0x63 (resolution) and 0x51 (LEDs) temporarily change the settings of the current mode. The settings are still there if you switch to another mode and back (with the +/- buttons), until you restore the settings with 0x63 and 0x51 or reload the profile with 0x0F. I don't think there is way (at least with the G500/G500s) to get/switch the current resolution mode (tell me if I am wrong).

all the ratbag-command options work on the active profile/resolution/button/etc. unless specified otherwise. so dpi set is "set the dpi for the currently active resolution of the currently active profile".
that's all I ever want it to do tbh, libratbag is about configuring the device after all. if there's a need for temporary settings or something more complex like runtime dpi-switching this should be in a separate tool using libratbag to change on the fly. but that logic would be outside the library and the basic commands we provide, stuff like that gets complicated very quickly and it's hard to make it a generic library layer option.

Okay but then you can remove support for the G5, since there is nothing to do with it (no hardware profile, only temporary settings).

but that temporary setting is still stored in the hw right? even if it's not persistent across unplugs.
if so, the device would still count has having one profile

Yes, they are hardware settings. I have just made more test with the G5 (2007/blue&black) and it does not behave the same way than the G500.

0x63 switch the resolution mode (not what I describe above). It works like the +/- buttons have been pressed except that it does not change the LEDs and that you can access a hidden 1600 dpi mode (only 400, 800 and 2000 are accessible from the buttons).
0x51 change the LEDs status but the setting is lost after switching mode with the buttons (the G500 keeps it).
the button settings are changed with "Individual features" (0x01), buttons are grouped by pair (+/- and tilt wheel) and have only two settings: default (change resolution or horizontal wheel) or generic buttons. I don't know how that would fit in ratbag profiles.
I think the polling rate (0x64) is the same though.

Regarding 0x63 - give this one a try please:
https://github.com/whot/libratbag/tree/wip/hidpp10-sensor-resolution
Note the commit message though, this really does change the "current" resolution, it doesn't write it to a profile as I'd like it to long term. It's a hack for testing until we fix the profile handling.
So just to reiterate: what we currently do here isn't what I'd like it to do long-term.
Regarding 0x51: that should be a setting in 0x01, FEATURE_BIT_R2_HOST_SW_CONTROLS_LEDS
Regarding the button settings: that's something we'll have to somehow fix through the "special" button actions. Benjamin and I talked about this a couple of weeks ago, but my jetlagged brain is a bit blurry atm.

Regarding 0x51: that should be a setting in 0x01, FEATURE_BIT_R2_HOST_SW_CONTROLS_LEDS

This feature is not available on the mice I tested (G5 and G500). Not all features are supported by every device. See the features documentation.

ok thanks, I'll double-check this tomorrow and test this here to make sure. this one we have docs for.

Regarding 0x63 - give this one a try please:
https://github.com/whot/libratbag/tree/wip/hidpp10-sensor-resolution

It worked the first time. But then my resolution is not in my profile and ratbag-command fails before doing anything.
ratbag raw: Fetching current resolution
ratbag raw:   expected_header:		?? 00 81 63
ratbag raw:   expected_error_dev:	10 00 8f 81 63 00 00
ratbag raw: output report: 10 00 81 63 00 00 00
ratbag raw: input report:  10 00 8f 81 63 02 00
ratbag raw:     HID++ error from the device (0): ERR_INVALID_ADDRESS (02)
ratbag raw:   expected_header:		?? 00 83 63
ratbag raw:   expected_error_dev:	10 00 8f 83 63 00 00
ratbag raw: output report: 10 00 83 63 00 00 00
ratbag raw: input report:  11 00 83 63 04 00 04 00 80 02 00 00 8f 00 00 8f 00 00 ff ff
ratbag raw:   received: 11 00 83 63 04 00 04 00 80 02 00 00 8f 00 00 8f 00 00 ff ff
ratbag debug: driver match found: Logitech HID++1.0
Error: Failed to retrieve the active resolution

The resolution (0x0004) is read correctly, but I think it fails to match it with an existing mode in my profile.

sorry, I forgot to mention that. this is expected behaviour and a result of us changing the active resolution only, not the profile-based one. so it'll only work once after plugging in, unless you pick a resolution that's in the profile.
did you test this on the G5 or the G500? it's still using the scheme3 (long report), I was hoping the G5 uses the short report and works (I can't test this here)

This is the G500. I don't expect the G5 to work because of this comment.


Feat: subscriptions support

@sgalichkin could you proceed with review please? The order might be API - protocol - internals - tests - sample producer/consumer.
I have also simplified the API as we discussed, the changes are visible in the second commit.

@678098 FYI, Ankur is okay to simplify Java Subscription API if it makes sense