[BUG] [Fedora40][Laptop] OpenShift cluster becomes Unreachable

General information

OS: Linux
Hypervisor: KVM
Did you run crc setup before starting it (Yes/No)? Yes
Running CRC on: Laptop

CRC version
CRC version: 2.37.1+36d451
OpenShift version: 4.15.14

CRC status
CRC VM:          Running
OpenShift:       Unreachable (v4.15.0-0.okd-2024-02-23-163410)
RAM Usage:       647MB of 10.95GB
Disk Usage:      21.48GB of 32.68GB (Inside the CRC VM)
Cache Usage:     27.69GB
Cache Directory: /home/van/.crc/cache

CRC config
- consent-telemetry                     : yes
- preset                                : okd

Host Operating System
NAME="Fedora Linux"
VERSION="40 (Workstation Edition)"
ID=fedora
VERSION_ID=40
VERSION_CODENAME=""
PLATFORM_ID="platform:f40"
PRETTY_NAME="Fedora Linux 40 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:40"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f40/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=40
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=40
SUPPORT_END=2025-05-13
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Steps to reproduce

Run crc setup
Run crc start
Get Error running post start: Executing systemctl action failed:  ssh command error: command : sudo systemctl enable dnsmasq.service err     : Process exited with status 1 : Failed to enable unit: Unit file /etc/systemd/system/dnsmasq.service is masked.
Run systemctl unmask dnsmasq.service
Run crc start again
Get

INFO A CRC VM for OKD 4.15.0-0.okd-2024-02-23-163410 is already running
Started the OpenShift cluster.

The server is accessible via web console at:
  https://console-openshift-console.apps-crc.testing

Log in as administrator:
  Username: kubeadmin
  Password: PHX79-zmtbm-9PPmT-I9JMB

Log in as user:
  Username: developer
  Password: developer

Use the 'oc' command line interface:
  $ eval $(crc oc-env)
  $ oc login -u developer https://api.crc.testing:6443

NOTE:
This cluster was built from OKD - The Community Distribution of Kubernetes that powers Red Hat OpenShift.
If you find an issue, please report it at https://github.com/openshift/okd

Run eval $(crc oc-env)

Expected
Access the oc CLI and the OKD Web Console
Actual
When i run oc login -u developer https://api.crc.testing:6443 i get:
error: dial tcp <IP_ADDRESS>:6443: connect: connection refused - verify you have provided the correct host and port and that the server is currently running.

And aren't able to access the OKD Web Console

Logs when i ssh to the running crc VM
van@fedora:~$ crc ip
<IP_ADDRESS>
van@fedora:~$ ssh -i ~/.crc/machines/crc/id_ecdsa -o StrictHostKeyChecking=no<EMAIL_ADDRESS>
i get:
Fedora CoreOS 39.20240128.3.0
Tracker: https://github.com/coreos/fedora-coreos-tracker
Discuss: https://discussion.fedoraproject.org/tag/coreos

Last login: Fri Jun 14 18:49:51 2024 from <IP_ADDRESS>
[systemd]
Failed Units: 1
  qemu-guest-agent.service

Then root@crc:~# systemctl status qemu-guest-agent.service
× qemu-guest-agent.service - QEMU Guest Agent
     Loaded: loaded (/etc/systemd/system/qemu-guest-agent.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: exit-code) since Fri 2024-06-14 18:41:41 UTC; 9min ago
   Duration: 3ms
    Process: 1159 ExecStart=/usr/bin/qemu-ga --method=vsock-listen --path=3:1234 --blacklist=${BLACKLIST_RPC} -F${FSFREEZE_HOOK_PATHNAME} (code=exited, status=1/FAILURE)
   Main PID: 1159 (code=exited, status=1/FAILURE)
        CPU: 2ms

Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 5.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Start request repeated too quickly.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 14 18:41:41 crc systemd[1]: Failed to start qemu-guest-agent.service - QEMU Guest Agent.

Then journalctl -u qemu-guest-agent.service --since 18:38:30
Jun 14 18:41:41 crc systemd[1]: Started qemu-guest-agent.service - QEMU Guest Agent.
Jun 14 18:41:41 crc (qemu-ga)[1015]: qemu-guest-agent.service: Referenced but unset environment variable evaluates to an empty string: BLACKLIST_RPC
Jun 14 18:41:41 crc qemu-ga[1015]:<PHONE_NUMBER>.650499: critical: Failed to create socket: Address family not supported by protocol
Jun 14 18:41:41 crc qemu-ga[1015]:<PHONE_NUMBER>.650536: critical: failed to create guest agent channel
Jun 14 18:41:41 crc qemu-ga[1015]:<PHONE_NUMBER>.650538: critical: failed to initialize guest agent channel
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 1.
Jun 14 18:41:41 crc systemd[1]: Started qemu-guest-agent.service - QEMU Guest Agent.
Jun 14 18:41:41 crc (qemu-ga)[1071]: qemu-guest-agent.service: Referenced but unset environment variable evaluates to an empty string: BLACKLIST_RPC
Jun 14 18:41:41 crc qemu-ga[1071]:<PHONE_NUMBER>.753307: critical: Failed to create socket: Address family not supported by protocol
Jun 14 18:41:41 crc qemu-ga[1071]:<PHONE_NUMBER>.754795: critical: failed to create guest agent channel
Jun 14 18:41:41 crc qemu-ga[1071]:<PHONE_NUMBER>.754799: critical: failed to initialize guest agent channel
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 2.
Jun 14 18:41:41 crc systemd[1]: Started qemu-guest-agent.service - QEMU Guest Agent.
Jun 14 18:41:41 crc (qemu-ga)[1115]: qemu-guest-agent.service: Referenced but unset environment variable evaluates to an empty string: BLACKLIST_RPC
Jun 14 18:41:41 crc qemu-ga[1115]:<PHONE_NUMBER>.814844: critical: Failed to create socket: Address family not supported by protocol
Jun 14 18:41:41 crc qemu-ga[1115]:<PHONE_NUMBER>.815354: critical: failed to create guest agent channel
Jun 14 18:41:41 crc qemu-ga[1115]:<PHONE_NUMBER>.815373: critical: failed to initialize guest agent channel
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 3.
Jun 14 18:41:41 crc systemd[1]: Started qemu-guest-agent.service - QEMU Guest Agent.
Jun 14 18:41:41 crc (qemu-ga)[1145]: qemu-guest-agent.service: Referenced but unset environment variable evaluates to an empty string: BLACKLIST_RPC
Jun 14 18:41:41 crc qemu-ga[1145]:<PHONE_NUMBER>.840374: critical: Failed to create socket: Address family not supported by protocol
Jun 14 18:41:41 crc qemu-ga[1145]:<PHONE_NUMBER>.840388: critical: failed to create guest agent channel
Jun 14 18:41:41 crc qemu-ga[1145]:<PHONE_NUMBER>.840390: critical: failed to initialize guest agent channel
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 4.
Jun 14 18:41:41 crc systemd[1]: Started qemu-guest-agent.service - QEMU Guest Agent.
Jun 14 18:41:41 crc (qemu-ga)[1159]: qemu-guest-agent.service: Referenced but unset environment variable evaluates to an empty string: BLACKLIST_RPC
Jun 14 18:41:41 crc qemu-ga[1159]:<PHONE_NUMBER>.866131: critical: Failed to create socket: Address family not supported by protocol
Jun 14 18:41:41 crc qemu-ga[1159]:<PHONE_NUMBER>.866145: critical: failed to create guest agent channel
Jun 14 18:41:41 crc qemu-ga[1159]:<PHONE_NUMBER>.866147: critical: failed to initialize guest agent channel
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Scheduled restart job, restart counter is at 5.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Start request repeated too quickly.
Jun 14 18:41:41 crc systemd[1]: qemu-guest-agent.service: Failed with result 'exit-code'.
Jun 14 18:41:41 crc systemd[1]: Failed to start qemu-guest-agent.service - QEMU Guest Agent.
lines 16-43/43 (END)

Then i run:
root@crc:~# podman ps
CONTAINER ID  IMAGE                                   COMMAND     CREATED       STATUS         PORTS       NAMES
74e5ad82fc3e  quay.io/crcont/gvisor-tap-vsock:latest              3 months ago  Up 14 minutes              gvisor-tap-vsock
root@crc:~# podman logs 74e5ad82fc3e

And get:
...
ERRO[0889] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0890] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0891] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0892] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0893] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0894] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0895] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0896] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0897] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0898] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0899] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0900] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0901] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0902] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0903] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0904] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer
ERRO[0905] cannot connect to host: dial vsock host(2):1024: connect: connection reset by peer

Apreciate help and any hint where to continue debbuging this issue

@souovan when using the system mode networking then qemu-guest-agent.service can be ignored because it use vsock-listen method which is only part of user mode networking.  I would be more interested in the start/status logs. Can you try following and share the details?
$ crc delete
$ crc setup --log-level debug
$ crc start --log-level debug
$ crc status --log-level debug

it uses vsock-listen method which is only part of user mode networking.

For what it's worth, it should relatively easy to add vsock support to the VM on linux https://libvirt.org/formatdomain.html#vsock
Or we could at least add ConditionVirtualization=apple to qemu-guest-agent unit file.

Or we could at least add ConditionVirtualization=apple to qemu-guest-agent unit file since we only need it on macOS.

I tried this in https://github.com/crc-org/snc/pull/914

Hi @souovan, a temporal fix to use OKD ~4.15 is unmasking the dnsmasq after first crc start error and restart the VM with crc stop and crc start.
crc setup
crc start
# Wait for the dnsmasq error

ssh -i ~/.crc/machines/crc/id_ecdsa -o StrictHostKeyChecking=no core@$(crc ip)
# In the ssh connection run the following commands
sudo systemctl unmask dnsmasq.service
sudo systemctl stop qemu-guest-agent.service
sudo systemctl disable qemu-guest-agent.service
exit # Exit from the ssh connection

crc stop
crc start

Inside the VM dnsmasq service is not masked so I am not sure why it need to unmask.

@souovan when using the system mode networking then qemu-guest-agent.service can be ignored because it use vsock-listen method which is only part of user mode networking. I would be more interested in the start/status logs. Can you try following and share the details?
$ crc delete
$ crc setup --log-level debug
$ crc start --log-level debug
$ crc status --log-level debug

I'm running into the same issue on fedora. Here are some logs I can provide. I also tried unmasking, enabling and starting dnsmasq.service myself which works without errors.
crc setup --log-level debug
DEBU OpenShift version: 4.17.1
DEBU MicroShift version: 4.17.1
DEBU Running 'crc setup'
INFO Using bundle path /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64.crcbundle
DEBU resolv.conf file path: /run/systemd/resolve/stub-resolv.conf
DEBU Checking if systemd-resolved.service is running
DEBU Running 'systemctl status systemd-resolved.service'
DEBU systemd-resolved.service is already running
INFO Checking if running as non-root
INFO Checking if running inside WSL2
INFO Checking if crc-admin-helper executable is cached
DEBU Running '/home/my_username/.crc/bin/crc-admin-helper-linux-amd64 --version'
DEBU Found crc-admin-helper-linux-amd64 version 0.5.4
DEBU crc-admin-helper executable already cached
INFO Checking if running on a supported CPU architecture
DEBU GOARCH is amd64 GOOS is linux
INFO Checking if crc executable symlink exists
INFO Checking minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
INFO Check if Podman binary exists in: /home/my_username/.crc/bin/oc
INFO Checking if Virtualization is enabled
DEBU Checking if the vmx/svm flags are present in /proc/cpuinfo
DEBU CPU virtualization flags are good
INFO Checking if KVM is enabled
DEBU Checking if /dev/kvm exists
DEBU /dev/kvm was found
INFO Checking if libvirt is installed
DEBU Checking if 'virsh' is available
DEBU 'virsh' was found in /usr/bin/virsh
DEBU Checking 'virsh capabilities' for libvirtd/qemu availability
DEBU Running 'virsh --readonly --connect qemu:///system capabilities'
DEBU Found x86_64 hypervisor with 'hvm' capabilities
INFO Checking if user is part of libvirt group
DEBU Checking if current user is part of the libvirt group
DEBU Current user is already in the libvirt group
INFO Checking if active user/process is currently part of the libvirt group
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd service is running
DEBU Running 'systemctl status virtqemud.socket'
DEBU virtqemud.socket is running
INFO Checking if a supported libvirt version is installed
DEBU Checking if libvirt version is >=8.0.0
DEBU Running 'virsh -v'
INFO Checking if crc-driver-libvirt is installed
DEBU Checking if crc-driver-libvirt-amd64 is installed
DEBU Running '/home/my_username/.crc/bin/crc-driver-libvirt-amd64 version'
DEBU Found crc-driver-libvirt-amd64 version 0.13.9
DEBU crc-driver-libvirt-amd64 is already installed
INFO Checking crc daemon systemd service
DEBU Checking crc daemon systemd service
DEBU Checking if crc-daemon.service is running
DEBU Running 'systemctl --user status crc-daemon.service'
DEBU crc-daemon.service is running
INFO Checking crc daemon systemd socket units
DEBU Checking crc daemon systemd socket units
DEBU Checking if crc-http.socket is running
DEBU Running 'systemctl --user status crc-http.socket'
DEBU crc-http.socket is running
DEBU Checking if crc-http.socket has the expected content
DEBU Checking if crc-vsock.socket is running
DEBU Running 'systemctl --user status crc-vsock.socket'
DEBU crc-vsock.socket is running
DEBU Checking if crc-vsock.socket has the expected content
INFO Checking if systemd-networkd is running
DEBU Checking if systemd-networkd.service is running
DEBU Running 'systemctl status systemd-networkd.service'
DEBU Command failed: exit status 3
DEBU stdout: * systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             `-10-timeout-abort.conf
     Active: inactive (dead)
TriggeredBy: * systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
             man:org.freedesktop.network1(5)
   FD Store: 0 (limit: 512)
DEBU stderr:
DEBU systemd-networkd.service is not running
INFO Checking if NetworkManager is installed
DEBU Checking if 'nmcli' is available
DEBU 'nmcli' was found in /usr/bin/nmcli
INFO Checking if NetworkManager service is running
DEBU Checking if NetworkManager.service is running
DEBU Running 'systemctl status NetworkManager.service'
DEBU NetworkManager.service is already running
INFO Checking if dnsmasq configurations file exist for NetworkManager
INFO Checking if the systemd-resolved service is running
DEBU resolv.conf file path: /run/systemd/resolve/stub-resolv.conf
DEBU Checking if systemd-resolved.service is running
DEBU Running 'systemctl status systemd-resolved.service'
DEBU systemd-resolved.service is already running
INFO Checking if /etc/NetworkManager/dispatcher.d/99-crc.sh exists
DEBU Checking NetworkManager dispatcher file for crc network
DEBU Dispatcher file has the expected content
INFO Checking if libvirt 'crc' network is available
DEBU Checking if libvirt 'crc' network exists
DEBU Running 'virsh --connect qemu:///system net-info crc'
DEBU Checking if libvirt 'crc' definition is up to date
DEBU Running 'virsh --connect qemu:///system net-dumpxml --inactive crc'
DEBU libvirt 'crc' network has the expected value
INFO Checking if libvirt 'crc' network is active
DEBU Checking if libvirt 'crc' network is active
DEBU Running 'virsh --connect qemu:///system net-info crc'
DEBU libvirt 'crc' network is already active
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64.crcbundle exists
DEBU /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64.crcbundle exists
Your system is correctly setup for using CRC. Use 'crc start' to start the instance

crc start --log-level debug
DEBU OpenShift version: 4.17.1
DEBU MicroShift version: 4.17.1
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
DEBU No new version available. The latest version is 2.43.0
DEBU Checking file: /home/my_username/.crc/machines/crc/.crc-exist
INFO Using bundle path /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64.crcbundle
DEBU resolv.conf file path: /run/systemd/resolve/stub-resolv.conf
DEBU Checking if systemd-resolved.service is running
DEBU Running 'systemctl status systemd-resolved.service'
DEBU systemd-resolved.service is already running
INFO Checking if running as non-root
INFO Checking if running inside WSL2
INFO Checking if crc-admin-helper executable is cached
DEBU Running '/home/my_username/.crc/bin/crc-admin-helper-linux-amd64 --version'
DEBU Found crc-admin-helper-linux-amd64 version 0.5.4
DEBU crc-admin-helper executable already cached
INFO Checking if running on a supported CPU architecture
DEBU GOARCH is amd64 GOOS is linux
INFO Checking if crc executable symlink exists
INFO Checking minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>8 bytes
INFO Check if Podman binary exists in: /home/my_username/.crc/bin/oc
INFO Checking if Virtualization is enabled
DEBU Checking if the vmx/svm flags are present in /proc/cpuinfo
DEBU CPU virtualization flags are good
INFO Checking if KVM is enabled
DEBU Checking if /dev/kvm exists
DEBU /dev/kvm was found
INFO Checking if libvirt is installed
DEBU Checking if 'virsh' is available
DEBU 'virsh' was found in /usr/bin/virsh
DEBU Checking 'virsh capabilities' for libvirtd/qemu availability
DEBU Running 'virsh --readonly --connect qemu:///system capabilities'
DEBU Found x86_64 hypervisor with 'hvm' capabilities
INFO Checking if user is part of libvirt group
DEBU Checking if current user is part of the libvirt group
DEBU Current user is already in the libvirt group
INFO Checking if active user/process is currently part of the libvirt group
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd service is running
DEBU Running 'systemctl status virtqemud.socket'
DEBU virtqemud.socket is running
INFO Checking if a supported libvirt version is installed
DEBU Checking if libvirt version is >=8.0.0
DEBU Running 'virsh -v'
INFO Checking if crc-driver-libvirt is installed
DEBU Checking if crc-driver-libvirt-amd64 is installed
DEBU Running '/home/my_username/.crc/bin/crc-driver-libvirt-amd64 version'
DEBU Found crc-driver-libvirt-amd64 version 0.13.9
DEBU crc-driver-libvirt-amd64 is already installed
INFO Checking crc daemon systemd socket units
DEBU Checking crc daemon systemd socket units
DEBU Checking if crc-http.socket is running
DEBU Running 'systemctl --user status crc-http.socket'
DEBU crc-http.socket is running
DEBU Checking if crc-http.socket has the expected content
DEBU Checking if crc-vsock.socket is running
DEBU Running 'systemctl --user status crc-vsock.socket'
DEBU crc-vsock.socket is running
DEBU Checking if crc-vsock.socket has the expected content
INFO Checking if systemd-networkd is running
DEBU Checking if systemd-networkd.service is running
DEBU Running 'systemctl status systemd-networkd.service'
DEBU Command failed: exit status 3
DEBU stdout: * systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             `-10-timeout-abort.conf
     Active: inactive (dead)
TriggeredBy: * systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
             man:org.freedesktop.network1(5)
   FD Store: 0 (limit: 512)
DEBU stderr:
DEBU systemd-networkd.service is not running
INFO Checking if NetworkManager is installed
DEBU Checking if 'nmcli' is available
DEBU 'nmcli' was found in /usr/bin/nmcli
INFO Checking if NetworkManager service is running
DEBU Checking if NetworkManager.service is running
DEBU Running 'systemctl status NetworkManager.service'
DEBU NetworkManager.service is already running
INFO Checking if dnsmasq configurations file exist for NetworkManager
INFO Checking if the systemd-resolved service is running
DEBU resolv.conf file path: /run/systemd/resolve/stub-resolv.conf
DEBU Checking if systemd-resolved.service is running
DEBU Running 'systemctl status systemd-resolved.service'
DEBU systemd-resolved.service is already running
INFO Checking if /etc/NetworkManager/dispatcher.d/99-crc.sh exists
DEBU Checking NetworkManager dispatcher file for crc network
DEBU Dispatcher file has the expected content
INFO Checking if libvirt 'crc' network is available
DEBU Checking if libvirt 'crc' network exists
DEBU Running 'virsh --connect qemu:///system net-info crc'
DEBU Checking if libvirt 'crc' definition is up to date
DEBU Running 'virsh --connect qemu:///system net-dumpxml --inactive crc'
DEBU libvirt 'crc' network has the expected value
INFO Checking if libvirt 'crc' network is active
DEBU Checking if libvirt 'crc' network is active
DEBU Running 'virsh --connect qemu:///system net-info crc'
DEBU libvirt 'crc' network is already active
DEBU Checking file: /home/my_username/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64...
INFO Creating CRC VM for OKD 4.15.0-0.okd-2024-02-23-163410...
DEBU Found binary path at /home/my_username/.crc/bin/crc-driver-libvirt-amd64
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:36107
DEBU () Calling .GetVersion
DEBU Using API Version 1
DEBU () Calling .SetConfigRaw
DEBU () Calling .GetMachineName
DEBU (crc) Calling .GetMachineName
DEBU (crc) Calling .DriverName
DEBU Running pre-create checks...
DEBU (crc) Calling .PreCreateCheck
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="About to check libvirt version"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Validating storage pool"
DEBU (crc) Calling .GetConfigRaw
DEBU Creating machine...
DEBU (crc) Calling .Create
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Preparing /home/my_username/.crc/machines/crc/crc.qcow2 for machine use"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="image creation took 25.367509ms"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Verifying executable bit set on /home/my_username/.crc/machines/crc"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Setting executable bit set on /home/my_username/.crc/machines/crc"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Verifying executable bit set on /home/my_username/.crc/machines"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Verifying executable bit set on /home/my_username/.crc"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Verifying executable bit set on /home/my_username"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Verifying executable bit set on /home"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Defining VM..."
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Found q35 machine type"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Found q35 machine type"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="disk image capacity is already<PHONE_NUMBER>4 bytes"
INFO Generating new SSH key pair...
INFO Generating new password for the kubeadmin user
DEBU Created /home/my_username/.crc/machines/crc/.crc-exist
DEBU Machine successfully created
DEBU Making call to close driver server
DEBU (crc) Calling .Close
DEBU Successfully made call to close driver server
DEBU Making call to close connection to plugin binary
DEBU Checking file: /home/my_username/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/my_username/.crc/bin/crc-driver-libvirt-amd64
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:45195
DEBU () Calling .GetVersion
DEBU Using API Version 1
DEBU () Calling .SetConfigRaw
DEBU () Calling .GetMachineName
DEBU (crc) Calling .GetBundleName
DEBU (crc) Calling .GetState
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Fetching VM..."
INFO Starting CRC VM for okd 4.15.0-0.okd-2024-02-23-163410...
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2024-10-31T08:53:01+01:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="IP address: <IP_ADDRESS>"
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=info msg="Found IP for machine: <IP_ADDRESS>"
DEBU (crc) Calling .GetConfigRaw
DEBU Waiting for machine to be running, this may take a few minutes...
DEBU retry loop: attempt 0
DEBU (crc) Calling .GetState
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="Getting current state..."
DEBU Machine is up and running!
DEBU (crc) Calling .GetState
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="Getting current state..."
DEBU (crc) Calling .GetIP
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="IP address: <IP_ADDRESS>"
INFO CRC instance is running with IP <IP_ADDRESS>
DEBU (crc) Calling .GetIP
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2024-10-31T08:53:06+01:00" level=debug msg="IP address: <IP_ADDRESS>"
DEBU Waiting until ssh is available
DEBU retry loop: attempt 0
DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/my_username/.crc/machines/crc/id_ed25519 /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64/id_ecdsa_crc]
DEBU SSH command results: err: dial tcp <IP_ADDRESS>:22: connect: no route to host, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : dial tcp <IP_ADDRESS>:22: connect: no route to host
 - sleeping 1s
DEBU retry loop: attempt 1
DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/my_username/.crc/machines/crc/id_ed25519 /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64/id_ecdsa_crc]
DEBU SSH command results: err: dial tcp <IP_ADDRESS>:22: connect: no route to host, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : dial tcp <IP_ADDRESS>:22: connect: no route to host
 - sleeping 1s
DEBU retry loop: attempt 2
DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/my_username/.crc/machines/crc/id_ed25519 /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64/id_ecdsa_crc]
DEBU SSH command results: err: dial tcp <IP_ADDRESS>:22: connect: no route to host, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : dial tcp <IP_ADDRESS>:22: connect: no route to host
 - sleeping 1s
DEBU retry loop: attempt 3
DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/my_username/.crc/machines/crc/id_ed25519 /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64/id_ecdsa_crc]
DEBU SSH command results: err: dial tcp <IP_ADDRESS>:22: connect: no route to host, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : dial tcp <IP_ADDRESS>:22: connect: no route to host
 - sleeping 1s
DEBU retry loop: attempt 4
DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/my_username/.crc/machines/crc/id_ed25519 /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64/id_ecdsa_crc]
DEBU SSH command results: err: dial tcp <IP_ADDRESS>:22: connect: no route to host, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : dial tcp <IP_ADDRESS>:22: connect: no route to host
 - sleeping 1s
DEBU retry loop: attempt 5
DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/my_username/.crc/machines/crc/id_ed25519 /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64/id_ecdsa_crc]
DEBU SSH command results: err: dial tcp <IP_ADDRESS>:22: connect: no route to host, output:
DEBU error: Temporary error: ssh command error:
command : exit 0
err     : dial tcp <IP_ADDRESS>:22: connect: no route to host
 - sleeping 1s
DEBU retry loop: attempt 6
DEBU Running SSH command: exit 0
DEBU Using ssh private keys: [/home/my_username/.crc/machines/crc/id_ed25519 /home/my_username/.crc/cache/crc_okd_libvirt_4.15.0-0.okd-2024-02-23-163410_amd64/id_ecdsa_crc]
DEBU SSH command results: err: <nil>, output:
INFO CRC VM is running
DEBU Using root access: disable core user password
DEBU Running SSH command: sudo passwd --lock core
DEBU SSH command results: err: <nil>, output: Locking password for user core.
passwd: Success
DEBU Running SSH command: cat /home/core/.ssh/authorized_keys
DEBU SSH command results: err: Process exited with status 1, output:
INFO Updating authorized keys...
DEBU Creating /home/core/.ssh/authorized_keys with permissions 0644 in the CRC VM
DEBU Running SSH command: <hidden>
DEBU SSH command succeeded
DEBU Running SSH command: rm /home/core/.ssh/authorized_keys.d/ignition
DEBU SSH command results: err: <nil>, output:
DEBU Using root access: Get device id
DEBU Running SSH command: sudo /usr/sbin/blkid -t TYPE=xfs -o device
DEBU SSH command results: err: <nil>, output: /dev/vda4
DEBU Using root access: Growing /dev/vda4 partition
DEBU Running SSH command: sudo /usr/bin/growpart /dev/vda 4
DEBU SSH command results: err: Process exited with status 1, output: NOCHANGE: partition 4 is size 63961055. it cannot be grown
DEBU No free space after /dev/vda4, nothing to do
DEBU Configuring shared directories
DEBU (crc) Calling .GetSharedDirs
DEBU (crc) DBG | time="2024-10-31T08:53:34+01:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2024-10-31T08:53:34+01:00" level=debug msg="Found q35 machine type"
INFO Configuring shared directories
DEBU Using root access: Creating /home/my_username
DEBU Running SSH command: sudo mkdir -p /home/my_username
DEBU SSH command results: err: <nil>, output:
DEBU Mounting tag dir0 at /home/my_username
DEBU Using root access: Mounting /home/my_username
DEBU Running SSH command: sudo mount -o context="system_u:object_r:container_file_t:s0" -t virtiofs dir0 /home/my_username
DEBU SSH command results: err: <nil>, output:
DEBU Using root access: make root Podman socket accessible
DEBU Running SSH command: sudo chmod 777 /run/podman/ /run/podman/podman.sock
DEBU SSH command results: err: <nil>, output:
DEBU Creating /etc/dnsmasq.d/crc-dnsmasq.conf with permissions 0644 in the CRC VM
DEBU Running SSH command: <hidden>
DEBU SSH command succeeded
DEBU Running SSH command: systemctl status dnsmasq.service
DEBU SSH command results: err: Process exited with status 3, output: ○ dnsmasq.service
     Loaded: masked (Reason: Unit dnsmasq.service is masked.)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
DEBU Using root access: Executing systemctl enable dnsmasq.service
DEBU Running SSH command: sudo systemctl enable dnsmasq.service
DEBU SSH command results: err: Process exited with status 1, output:
DEBU Making call to close driver server
DEBU (crc) Calling .Close
DEBU (crc) DBG | time="2024-10-31T08:53:34+01:00" level=debug msg="Closing plugin on server side"
DEBU Successfully made call to close driver server
DEBU Making call to close connection to plugin binary
Error running post start: Executing systemctl action failed:  ssh command error:
command : sudo systemctl enable dnsmasq.service
err     : Process exited with status 1
: Failed to enable unit: Unit file /etc/systemd/system/dnsmasq.service is masked.

crc status --log-level debug
DEBU OpenShift version: 4.17.1
DEBU MicroShift version: 4.17.1
DEBU Running 'crc status'
CRC VM:          Running
OpenShift:       Unreachable (v4.15.0-0.okd-2024-02-23-163410)
RAM Usage:       626.8MB of 10.95GB
Disk Usage:      21.48GB of 32.68GB (Inside the CRC VM)
Cache Usage:     27.69GB
Cache Directory: /home/my_username/.crc/cache

Hi @souovan, a temporal fix to use OKD ~4.15 is unmasking the dnsmasq after first crc start error and restart the VM with crc stop and crc start.
crc setup
crc start
Wait for the dnsmasq error
ssh -i ~/.crc/machines/crc/id_ecdsa -o StrictHostKeyChecking=no core@$(crc ip)
In the ssh connection run the following commands
sudo systemctl unmask dnsmasq.service
sudo systemctl stop qemu-guest-agent.service
sudo systemctl disable qemu-guest-agent.service
exit # Exit from the ssh connection
crc stop
crc start

This seems to work. Not sure if disabling the qemu-guest agent has any impact. for some reason the dnsmasq.service is masked inside the VM

@AlexStorm1313 Are you using crc with OKD bundle?

@AlexStorm1313 Are you using crc with OKD bundle?

Yes that's correct

@praveenkumar Yes that's correct.


MB 9633 Payment request hide/show details styling adjustments

Description
This branch fixes a layout bug in the Payment requests card that allowed the items to get too close together and the buttons for View Documents and Show request details to overlap at common screen widths on desktop. This branch re-works some of the flex logic for this component, as well as establishes a min-width for the main content area of the office app (more to come of this - this should be done for all areas of the office app, users should not be seeing the broken mobile states of these components we are not supporting due to this being a desktop-only app).
Reviewer Notes
I don't like that I have added loose styling to the office.scss file. I will follow up with an additional PR that will create a style sheet for this logic and load it in as a module like the rest of the office styles. I felt like I was reaching too far out of the scope of this PR to be doing it here.
Setup
make db_dev_e2e_populate
make server_run
make office_client_run

-> log in as TOO
-> http://officelocal:3000/moves/NOESTW/payment-requests
Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots
Before:

After

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against ba119eebfbc0242b64477f36ad4e37e8539bf041


Add complementary color for text to be clearly visible

Fix for issue https://github.com/adobe/brackets/issues/10923

@prafulVaishnav Can you post a screenshot of how it would appear with your fix- either here or in the issue.

@prafulVaishnav As mentioned by @njx, you should test it out with other themes like mystique as well.

@rroshan1 Here is the snapshot.

@nethip Preview (marked in red) will remain same for all themes

Looks good.. Merging it.


Where to find my TxID for specfic transaction?

Hi,
I did have a recent transaction but I need the specific transaction ID for this event.
Could you please help me where to find that txID?
Thank you very much.

You can find your transactions and their txId on hiveblocks.com


use full build of consola for development time

Context: https://github.com/unjs/nitro/issues/1761
We automatically use lighter build of consola for production but for development, we can keep using fancy logger.

@cany748 Thanks a lot for the fix!
I'm trying to import consola to log requests received by nitro but I still have an unformatted version of consola, what's the right way to import it?
For now I'm doing it this way:
import { consola } from 'consola'

consola.box({
  title: `Request at ${time}`,
  message: `[${event.method}] ${event.path}`
})

Thanks in advance for your advice

@cany748 Thanks a lot for the fix!
I'm trying to import consola to log requests received by nitro but I still have an unformatted version of consola, what's the right way to import it?
For now I'm doing it this way:
import { consola } from 'consola'

consola.box({
  title: `Request at ${time}`,
  message: `[${event.method}] ${event.path}`
})

Thanks in advance for your advice

Do you need the full version of consola in production mode? Try this:
// nitro.config.ts
export default defineNitroConfig({
  imports: { imports: [{ name: "consola", from: "consola" }] },
  unenv: { alias: { consola: "consola" } },
});

And use the auto-imported consola.

@cany748 Thanks a lot for the fix!
I'm trying to import consola to log requests received by nitro but I still have an unformatted version of consola, what's the right way to import it?
For now I'm doing it this way:
import { consola } from 'consola'

consola.box({
  title: `Request at ${time}`,
  message: `[${event.method}] ${event.path}`
})

Thanks in advance for your advice

Do you need the full version of consola in production mode? Try this:
// nitro.config.ts
export default defineNitroConfig({
  imports: { imports: [{ name: "consola", from: "consola" }] },
  unenv: { alias: { consola: "consola" } },
});

And use the auto-imported consola.

@cany748 Thank you very much, it works!
(I had to put this config in the nitro key of nuxt.config.ts because nuxt warned me that nitro.config.ts cannot be used with nuxt)
I only need consola in dev, will this method be only effetive in dev or also in production (after build)?
I have a second question, why do we have to add these options to access consola when you've made the fix above which seemed to no longer mock the full build of consola in dev?

I only need consola in dev, will this method be only effetive in dev or also in production (after build)?

The full version of consola will be available in Production mode

I have a second question, why do we have to add these options to access consola when you've made the fix above which seemed to no longer mock the full build of consola in dev?

try updating the dependencies


[Indexing] Gem step does not work

Hello Yan,
It seems that I have a problem in the indexing step. The BWT index works fine. But the gem-indexer fails to run.
I collected a log file as well as list of files that are generated so far:
Run_Log.txt
List_of_Files.txt

Hi Amin,
Can you upload the "./REF_GNM-mm9_BMajor_Chr7_109933500-112066500.fasta.log" file?
Thank you.
Yan

Thank you for your response Yan.
Please find attached the log file.
REF_GNM-mm9_BMajor_Chr7_109933500-112066500.fasta.log

It seems that the log file does not provide any useful information.
I suggest you try running the program with the absolute path instead of the relative path.
Tell me if it works or not.
I will try to fix the problem to make lamsa more friendly.
Yan

Hi,
I just can not see the error happen on my server.
Please make sure that you have enough space on your disk
Actually I also want to know if you can run GEM normally independently (without lamsa).
Yan

Hello Yan,
I have more information regarding this issue.

I was able to run your script in another machine.
I think the problem has something to do with an illegal instruction in "gem-indexer_generate". I tried to remove redirections to get the output on terminal. This is what I see:

Creating sequence and location files... done.
Computing DNA BWT (likely to take long)... done.
Generating index (likely to take long)...
/bin/sh: line 1: 19609 Illegal instruction     gem-indexer_generate --append -i ./ref.fasta.fmi_dna-cont -o ./ref.fasta.gem -s 32 --index_type fmi-dna -b ./ref.fasta.fmi_dna-bwt --mm-tmp-prefix "/tmp/mm_new-" >> ./ref.fasta.log 2>&1
Fatal error: exception Failure("Command 'echo "-------gem-indexer_generate" >> ./ref.fasta.log && gem-indexer_generate --append -i ./ref.fasta.fmi_dna-cont -o ./ref.fasta.gem -s 32 --index_type fmi-dna -b ./ref.fasta.fmi_dna-bwt --mm-tmp-prefix "/tmp/mm_new-" >> ./ref.fasta.log

gem-indexer error. (./ref.fasta.log)

Hi Amin,
For the "illegal instruction", I think this is because the complied GEM-indexer in not compatible with your machine.

Here is the Installation Instruction of GEM. You can try to download the old-cpu version of GEM via the link: https://sourceforge.net/projects/gemlibrary/files/gem-library/Binary pre-release 3/GEM-binaries-Linux-x86_64-core_2-20130406-045632.tbz2/download
Just replace decompression them in the "gem" directory.
Tell me if it works or not.
Yan

Hello Yan,
I tested the script in the old server (using different available versions of GEM library). I can tell that same error pops up everytime. Just for future reference, here is some information about this server:
bash$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             2
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 23
Model name:            Intel(R) Xeon(R) CPU           E5410  @ 2.33GHz
Stepping:              10
CPU MHz:               2333.000
BogoMIPS:              4655.03
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              6144K
NUMA node0 CPU(s):     0-7

On the other hand, I can confirm that it does work in several new servers that I tested. This is good enough for me.
Thank you for taking the time to respond to this issue. I will close the issue.

Hi Amin,
For the "illegal instruction", I think this is because the complied GEM-indexer in not compatible with your machine.

Here is the Installation Instruction of GEM: http://algorithms.cnag.cat/wiki/Installation_instructions.
You can try to download the old-cpu version of GEM via the link: https://sourceforge.net/projects/gemlibrary/files/gem-library/Binary pre-release 3/GEM-binaries-Linux-x86_64-core_2-20130406-045632.tbz2/download
Just decompress them in the "gem" directory.
Tell me if it works or not.
Yan

If it is related the "Illegal instruction" error of GEM, you may want to try different machine/server to see if it can work.


add instructions to deploy in Azure with Azure standard template for …

…windows 2012 R2

@jbondpdx can someone from the docs team review this?
@danieloa Thanks for the contribution! We are going to look it over, but if you don't mind, I'd like you to clean up your commit message a bit.
Can you add (docs) to the front of your commit summary, then make sure that the summary is only around 50 characters? Then put a space in and add a bit of a commit message body breaking lines at 72 characters. Take a look at http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html or http://chris.beams.io/posts/git-commit/ for more information on this.


feat: update runtime v2 doc

Summary
Update Docs:

add createRoot、 render、renderString、renderStreaming 、createRequestHandler function doc
mark bootstrap and createApp will be deprecated
update new runtime hooks list
support src/entry.tsx custom entry when enable source.enableCustomEntry
support src/entry.server.tsx to custom ssr entry

Related Links

Checklist

[x] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

maybe we can add some summary for the pr

maybe we can add some summary for the pr

done


QUIC for 3.3.0

Review carefully: we've tested the code decently well (thanks @nibanks). The branch wladd/quic-comparison-branch has everything squashed down to ease review. I renamed our feature to boring-quic-api in this branch as the first big change, hopefully everywhere it needed to happen in the build system.

Looks like some more work needed for CI to work, will update in a bit.

Looks like all checks pass modulo the fuzzer, but that seems to have run fine other times?

I do not understand what the difference is between the two fuzzer builds. @tmshort any ideas?

i wouldn't worry about it. The one tagged (pull_request) is likely only run on an actual pull request, and is more comprehensive than the one tagged (push) which would happen on all pushes to the repo (even if they don't become a PR).

The CIFuzz (pull_request) has almost always failed.

Any updates here @wbl ?

Sorry I think balls ended up on floors as Ive forgotten to poke. I've made the comparison branch and gotten this one to what I think is reviewable state but another set of eyes would be helpful. So take a look or reremind me what I need to do first.

Thanks @richsalz for looking it over. I'll fix up the comments if no one else chimes in with more soon in a separate commit.

Sorry, I haven't followed up here in a while. I just updated https://github.com/microsoft/msquic/pull/4274 to use the latest commit here with the latest version of MsQuic and I am seeing build failures on Ubuntu 24.04. Note, the last time I tried this, we didn't build for 24.04 yet, so this isn't necessarily a recent break, but it is a regression from previous v3 openssl.
https://github.com/microsoft/msquic/actions/runs/9974479617/job/27562154754#step:8:2184
/usr/bin/ld: ../../../../_deps/opensslquic-build/openssl3/lib/libssl.a(libssl-lib-ssl_lib.o): in function `SSL_CTX_free':
ssl_lib.c:(.text+0x93f1): undefined reference to `OSSL_STACK_OF_X509_free'
/usr/bin/ld: ../../../../_deps/opensslquic-build/openssl3/lib/libssl.a(libssl-lib-ssl_lib.o): in function `SSL_dup':
ssl_lib.c:(.text+0x9e44): undefined reference to `OSSL_STACK_OF_X509_free'
/usr/bin/ld: ../../../../_deps/opensslquic-build/openssl3/lib/libssl.a(libssl-lib-ssl_lib.o): in function `ossl_ssl_connection_free':
ssl_lib.c:(.text+0xa262): undefined reference to `OSSL_STACK_OF_X509_free'
/usr/bin/ld: ssl_lib.c:(.text+0xa540): undefined reference to `OSSL_STACK_OF_X509_free'
/usr/bin/ld: ../../../../_deps/opensslquic-build/openssl3/lib/libssl.a(libssl-lib-ssl_lib.o): in function `SSL_CTX_new_ex':
ssl_lib.c:(.text+0xa6fc): undefined reference to `OPENSSL_LH_set_thunks'
/u
...

@nibanks I'll look into that failure: if those things got redefined to be macros or functions across versions, maybe its a build picking up wrong things sort of issue, but we should know that for sure and I'll go attack it.  What's the easiest way for me to locally reproduce where I can poke around the image/reproduce in CI: open a junk pr to MSQuic?

@nibanks I'll look into that failure: if those things got redefined to be macros or functions across versions, maybe its a build picking up wrong things sort of issue, but we should know that for sure and I'll go attack it. What's the easiest way for me to locally reproduce where I can poke around the image/reproduce in CI: open a junk pr to MSQuic?

Do you want to try to repro locally or just let MsQuic CI/CD do the heavy lifting? If you want to use MsQuic, yeah, just make a draft PR and I will approve the automation to run.

I think I've got to play with it locally just to understand. But wait,

cd /__w/msquic/msquic/build/linux/x86_openssl3/src/tools/interopserver && /usr/bin/cmake -E cmake_link_script CMakeFiles/quicinteropserver.dir/link.txt --verbose=1
/usr/bin/c++ --sysroot=/ -Og -fno-omit-frame-pointer -ggdb3 CMakeFiles/quicinteropserver.dir/InteropServer.cpp.o -o /__w/msquic/msquic/artifacts/bin/linux/x86_Debug_openssl3/quicinteropserver  -Wl,-rpath,"$ORIGIN:__w/msquic/msquic/artifacts/bin/linux/x86_Debug_openssl3" /__w/msquic/msquic/artifacts/bin/linux/x86_Debug_openssl3/libmsquic.so.2.4.0 ../../../obj/Debug/libplatform.a ../../../obj/Debug/liblogging.a ../../../_deps/opensslquic-build/openssl3/lib/libssl.a /usr/lib/x86_64-linux-gnu/libcrypto.so -ldl /usr/lib/x86_64-linux-gnu/libatomic.so.1 /usr/lib/x86_64-linux-gnu/libnuma.so.1

Is it just me or is it linking the new libssl.a to the system libcrypto.so? Then I'm not surprised it doesn't work, as those got introduced in patch openssl@5c42ced

Ah, you're right! It's all our builds with the -UseSystemOpenSSLCrypto flag, which statically links libssl, but dynamically links libcrytpo (for FIPS). This passed on previous versions/commits, but is failing now. How are we supposed to handle this?

My first reaction is why on earth would you expect this to work out nicely, and why do you need it: is there some other way to get what you want here? Note that the fips module is entirely unaffected by this issue as that dynamically loads with a much more restricted interface.

Alternatively try 3.3 as the system version, but that might have other issues

My first reaction is why on earth would you expect this to work out nicely, and why do you need it: is there some other way to get what you want here? Note that the fips module is entirely unaffected by this issue as that dynamically loads with a much more restricted interface.

We need to dynamically link to the system libcrypto for FIPS compliance (because we can't bring our own binary). But we cannot link to the system libssl because it's not the quictls fork. This has worked out so far for previous v1 and v3 versions of openssl.

Alternatively try 3.3 as the system version, but that might have other issues

I don't think we had to specify anything version specific in the past. Any suggestions on how we'd test this out?

My first reaction is why on earth would you expect this to work out nicely, and why do you need it: is there some other way to get what you want here? Note that the fips module is entirely unaffected by this issue as that dynamically loads with a much more restricted interface.

We need to dynamically link to the system libcrypto for FIPS compliance (because we can't bring our own binary). But we cannot link to the system libssl because it's not the quictls fork. This has worked out so far for previous v1 and v3 versions of openssl.

That's odd: they were supposed to have limited fips issues to fips.so, but maybe you're doing something different.

Alternatively try 3.3 as the system version, but that might have other issues

I don't think we had to specify anything version specific in the past. Any suggestions on how we'd test this out?

Ideally just an apt-get update and install the new version ahead of running the existing script. Not really sure about where it is in ubuntu.

What's the status of this PR?

I'd like more than just Rich's approval on it, given the size and scope and the number of decisions I had to make that people could possibly have issues with. Please take a look and either approve or say what you want to change.

Built fine with the latest ngtcp2 and all tests passed.  Thank you for great work.
Once thing, that is I do not know whether it is the issue of original openssl, but the generated pkgconfig file is broken.  libdir lacks lib directory.

I just pushed the latest to https://github.com/microsoft/msquic/pull/4274 to run it all again. If only our 'use system libcrypto' tests fail, I'm fine for merging this. I still need to figure out a solution for that though...

@nibanks I agree, let's merge this once your results are known.

@nibanks it looks like it's just the usesystem openssl tests failing, but I'm not that familiar with your tests.
@tatsuhiro-t pkgconfig is a bit of a black box to me I'm afraid. If you would be so kind, open another issue after we merge this where we can solve that problem.

I'm sorry. I just haven't had the time to follow up on this. I will see if I can make progress tomorrow morning, otherwise, don't wait on me.

@wbl All right. Lets move on.  Will check after the merge to check that it is still an issue.

I have two questions related to this merge, not sure it's the best place to ask, sorry in advance.
Would it be possible to get a release with quic patchset on top of openssl-3.3.2, it has two CVE fixed in it ?
Do we need to build this quictls with enable-quic & no-boring-ssl-api ?
I tried applying openssl 3.3.0->3.3.2 patchset on top of quictls-3.3.0 but when enabling quic with boring ssl api disable, I get these errors:
Test Summary Report
-------------------
25-test_verify.t                      (Wstat: 512 (exited 2) Tests: 193 Failed: 2)
  Failed tests:  127, 129
  Non-zero exit status: 2
70-test_quic_multistream.t            (Wstat: 256 (exited 1) Tests: 2 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
70-test_quic_tserver.t                (Wstat: 256 (exited 1) Tests: 1 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
75-test_quicapi.t                     (Wstat: 512 (exited 2) Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
90-test_quicfaults.t                  (Wstat: 512 (exited 2) Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
90-test_sslapi.t                      (Wstat: 512 (exited 2) Tests: 4 Failed: 2)
  Failed tests:  1, 3
  Non-zero exit status: 2
Files=314, Tests=2882, 436 wallclock secs ( 7.35 usr  0.40 sys + 358.88 cusr 35.17 csys = 401.80 CPU)
Result: FAIL

It has been merged, but we're no longer actively working on 3.3+quic.  We are instead focused on the quictls/quictls fork.
If the community wants to take over maintenance of this branch, feel free.  We can add committers as needed.


Ability to archive & purge older fundraiser data

Probably need to break archive out from this.   The request is that the archive can be accessible from the system itself


Use Angular Selectize without the Selectize tag

Hello,
Is it possible to use angular selective without the selective tag since I think this create problems with validation?
Thank you,
Miguel

Can you elaborate on what the validation issue is?

I meant W3C validation ... In my opinion Selectize is an improvement to an already existing HTML tag, so according to one of Angular creators, the select tag should be used.
It should be only use a selectize tag if this would be a complete new feature.
And then there is the W3C validation problem ...

Are you sure this is working? I had the following with a previous version of Angular Selectize:
<select data-ng-model="subscriber.country" data-placeholder="Country" name="country" data-selectize="model.countries" data-options="model.countries.options"></select>

This stopped working the moment I updated to the current version ...

I think you need to change data-selectize="model.countries" to just data-selectize

That didn't work ... BTW, model.countries is the following:
$scope.model = {
  countries: {
    labelField: 'Name',
    maxItems: 1,
    persist: false,
    required: true,
    valueField: 'Id'
  }
};

oh. in that case do <select data-ng-model="subscriber.country" data-placeholder="Country" name="country" data-selectize config="model.countries" data-options="model.countries.options"></select>

Yes, that solved it ... Thanks

no problem
On Wed, Jan 28, 2015 at 2:37 PM, Miguel Moura<EMAIL_ADDRESS>wrote:

Yes, that solved it ... Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/machineboy2045/angular-selectize/issues/27#issuecomment-71931787
.


Button "action" should only fire by default is the pointer is Over the button

The Button exposes an onUp event with an isOver parameter. The user must manually check isOver to determine if the "click was real". This is confusing at least.
Proposal:

Add an onClick event that will only fire when the "up" occurs over the button. The onUp would still be fired to avoid breaking changes.

A minor breaking change would be the callback/context supplied to the constructor as these would be wired to the onClick event. (I am not a fan of their usage to begin with..)

FWIW, the use of checking isOver will also produce false-positives as the pointer may be released over the button even though the button was never pressed (ie. it is only 'overed').

Closing off (as you fixed it in your PR).


Fix sample data

Pull Request Test Coverage Report for Build 501

24 of 28 (85.71%) changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 88.199%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/model/util/SampleDataUtil.java
23
27
85.19%

Totals

Change from base Build 499:
0.08%

Covered Lines:
2272

Relevant Lines:
2576

💛  - Coveralls


Port: "Enable multiple scopes for single serviceUrl host" to javascript v3 sdk

https://github.com/microsoft/BotBuilder-V3/pull/215

This is apparently not required in javascript v3, since the MicrosoftAppCredential is created on every incoming activity, and the cache is based on the entire serviceUrl, not just host:
https://github.com/microsoft/BotBuilder-V3/blob/main/Node/core/src/bots/ChatConnector.ts#L249


openssl 3.0.3: error when running openssl speed ffdh

When running openssl speed with the  command, openssl speed -seconds 1 -multi 256 ffdh, the following errors are reported:
40E747F2327F0000:error:1C80006A:Provider routines:dh_plain_derive:output buffer too small:../providers/implementations/exchange/dh_exch.c:162:
If the value for multi is reduced to around 30, the errors are not reported.
attached:log for command
command.log

Fix in #18777


loaders: Add Blockscout ABI support

Resolves issue #149
Overview
This PR implements the BlockscoutABILoader to enable loading ABIs from Blockscout's API.
To do

[x] Implement BlockscoutABILoader
[x] Add tests

Hi @shazow, thanks for reviewing! I don't believe there are any concerns with this PR. It's ready to be merged.

@yohamta Thank you for working on this!!


Fix missing arguments to tls_cert_request resource

what

Fix missing arguments to tls_cert_request resource
Use bullet points to be concise and to the point.

why

So that it works correctly.

/test all

/terratest


errors middleware customize the response status (http_response:404 -> 200)

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you expect to see?
When configuring middlewares and error middleware, can you customize the response status code through parameters? For example, configure status:"404", query:"/404.html", and expect the browser to receive an HTTP response that displays 200. nginx can do this. nginx can refer to: error_page 404 =200 /50x.html; Thank you,

Thank you.


render-pages only renders index.html

npm run render-pages does render a nice index.html but about/index.html and count/index.html end up as empty files.

Thanks for the info, it "worked fine on my machine" but then I realized I get the same result as you on Netlify. I'll check out what's going on.

@craftedsystems Could you bump your hyperapp-site-generator version to 0.0.18, and tell me if the renders work properly now? I did a async rookie mistake and only ran properly on my machine because of the slow CPU facepalm
I finally found the root cause of the instability now, thanks!

fixed in new version. thx


[DEVX-1338] Sauce Test Report JSON

Create and attach at sauce-test-report.json to the job.
Example job:
https://app.saucelabs.com/tests/7b6c7b4a6ca24b15a5f09abf94e2a471

PS: I still need to fix the reliance on the build (12.x) pipeline, but that has to wait till we regain admin access.


Rigid body damping angular / linear is flipped

Check out this setter:
https://github.com/notgiven688/jitterphysics2/blob/e80205d51c3947efaf926d38c121800302be6ceb/src/Jitter2/Dynamics/RigidBody.cs#L189C1-L198C6
The setter call first param angular and second param linear, but when setting the values it set linear as first and angular as second, flipping them.
Looks like a mistake.
Also please add individual setter / getter for damping types. Thanks!

Fixed the reversal.

Also please add individual setter / getter for damping types.
This will not be implemented to avoid confusion (multiple ways of doing things).


Bulk deletion of places by Admin

As an Admin I want to delete existent places in the list so that it will be easier to clear data with places quicker.
Mockup:
Acceptance criteria:

System shall display a "Delete" button and checkboxes near each of the row in the list of places in the Admin page.

An admin can click "Delete" button.

WHEN Admin checks more that one row THEN he/she can click "Delete" button.

WHEN an admin clicks "Delete" button, THEN popup with the next information appears:
a. Text - "Are you sure you want to delete these items?"
b. "Yes" button
c. "Cancel" button

WHEN an admin clicks "Yes" button, THEN checked rows should be removed from the list of places.

WHEN an admin clicks "Cancel" button, THEN checked rows should be visible in list of places.

This story was added to US 113


Replace Traefik with kamal-proxy

Kamal now uses our custom proxy kamal-proxy. The proxy responds to a deploy command which tells it which container to send requests to. It then waits for the container to respond on its healthcheck URL and returns once that is successful.
Changes this brings:

The app, proxy and accessories will now run in a custom network called "kamal". This allows us to use the container id as a stable hostname that will survive container restarts.
No need for cordfiles, which were a hack used to stop Traefik from sending request to a container to make it unhealthy. Kamal-proxy just sends traffic where we tell it to.
The healthcheck config has been removed. Containers are healthchecked externally be the proxy waiting for the healthcheck URL to return 200s. For non proxy containers (jobs etc), there is a new readiness_timeout option, which is used to wait for them to be ready. You can still set a custom healthcheck using the options config which allows you to pass custom options to docker run.

To enable proper multi-app support:

All files except for audit logs and locks for an app will be stored in .kamal/apps/#{service}[-#{destination}], so they can be easily removed by removing that folder.

Upgrading:

To upgrade from Kamal 1.x you need to run kamal proxy upgrade to upgrade the proxy containers. This will remove Traefik and boot the proxy and app containers in the kamal docker network. There will be a similar downgrade command added to Kamal 1.9 to reverse the process.
You'll also need to reboot accessories to move them into the kamal network.
You'll need to rename the pre-traefik-reboot and post-traefik-reboot hooks to pre-proxy-reboot and post-proxy-reboot.

Config changes:

traefik & healthcheck both removed
set proxy: true not traefik: true for non primary role roles that use a proxy
options for kamal-proxy, go under the proxy setting:
hosts - a list of hosts that should be forwarded to this app by the proxy. Allows multiple apps to use the same server and proxy, and have the requests routed by the host. Currently the proxy only supports one host
ssl - requires hosts to be set if enabled, if enabled it will automatically set up HTTPS via Let's Encrypt. Should only be used with one server!
app_port - the port on the application that we will proxy (default 80)
deploy_timeout - how long kamal-proxy waits for the container to come up (default 30 seconds)
response_timeout - how long kamal-proxy waits for a response (default 30 seconds)
healthcheck - configure the healthcheck URL, interval and timeout
buffering - configure request and response buffering, max request and response size and memory buffer size
logging - log extra request and response headers
forward_headers - whether to forward X-Forwarded-For and X-Forwarded-Proto, defaults to false

This is exciting! I haven't looked through the whole PR but just had a couple of questions come to mind, quotes added for context.

The app, proxy and accessories will now run in a custom network called "kamal". This allows us to use the container id as a stable hostname that will survive container restarts.

How will this work if you're currently using networks? Or if you're hosting multiple apps on the same server? I'm guessing the custom options just get added along with the default kamal network. By default this should give us more of a docker compose experience which is really nice, being able to connect to db for a host accessory for instance. There's a decent amount of questions around networking with Kamal that this will help address.
hosts - a list of hosts that should be forwarded to this app by the proxy. Allows multiple apps to use the same server and proxy, and have the requests routed by the host. Currently the proxy only supports one host
ssl - requires hosts to be set if enabled, if enabled it will automatically set up HTTPS via Let's Encrypt. Should only be used with one server!

SSL is one of the more difficult things to get going with traefik, is Thruster no longer the replacement for traefik? If an app does need to support multiple hosts, how would we go about that? I have multiple apps at the moment that utilize more than one host. Should the ssl section say requires host and not hosts?

@djmb Appreciate the context! I forgot about Thruster actually running within the container, makes sense.


feat(demos): AsyncStateAdapter for CQRS using

Extensible command source events list to allow flexibility on api service classes;

Hi @mfp22 , I've gotten some free time and implemented a new version of my async state adapter solution using state-adapt.
My guidelines were:

Allow consistent use of a CQRS backend server. In this case it is not unusual that a command response has no body. Due that, I have to handle command response apart from entity or list change;
As the CQRS way is not compliant with the REST way, I need to extend adapter event sources (actions) to accommodate different commands. The right place to do that is in the api service layer;
However, REST operations ought to supported by adapter as well;
App components will consume store resources through the api service layer.
Api services layer is not injected services. This is intentional to allow different store instances to be used in the same scope (injected services are singleton). The service factory is a injectable service instead;

As a matter of fact, I’m satisfied with this implementation and wonder what you think about it.
Unfortunately I couldn’t figure out how to use getHttpsources you have mentioned. If you don’t mind sending some hints, I’ll appreciate it.

Thanks for checking in with me a couple months ago @rodzappa . Sorry for the long absence. I have had a series of AngularJS/Angular upgrade projects that have taken some time, but I've found some time here and there to add some improvements to StateAdapt. I am working with HeroDevs to get some regular StateAdapt time even during upgrade projects, so I hope to make improvements to StateAdapt more regularly going forward.
I am really grateful for your early contributions to StateAdapt @rodzappa . I have needed to make some major changes I didn't anticipate. I have a couple of others in mind as well. I would ask for your patience as I flesh out more of the core aspects of StateAdapt. I'm excited about these changes. I thought StateAdapt was fun to work with before, but I think it's going to be really special now. The most recent change I made was creating a createSelectors function for memoization of multiple selectors simultaneously. I haven't published this yet, but you can read about it in the file I just committed: https://github.com/state-adapt/state-adapt/blob/26b70b8b82d010664ea5b2803cf1e6865379ea68/apps/docs/src/app/concepts/adapters.md
I need to be more open about my plans and ideas for StateAdapt. I'm going to create issues for each task I plan on implementing from now on to give an opportunity for more people to see what I'm up to and provide feedback.
I am very opinionated about StateAdapt, and I want a lot of control in the early process. I'm going to be very selective about code contributions, at least until I feel I have adequately expressed the core philosophies driving the project in documentation, code and examples.
I am going to close this and provide my own example using HTTP soon. I'm sorry, I underestimated the work open sourcing a library takes! But I promise I'll get to it soon. But it is very important to me to keep sources independent from the reusable adapters, as I explained in the documentation: https://state-adapt.github.io/concepts/sources#no-multiple-events

@rodzappa Glad to hear it. I'm gradually working on the issues I wanted to finish before 1.0 and some docs design improvements are currently taking my time. I may have gotten carried away with some SVG animations, but we'll see if it convey some concepts... I also haven't had the chance to work on it over the last 4 weeks because of a demanding project with HeroDevs. I might get some time in between projects a week from now. Thanks for staying with it and let me know if you do see any problems.
If I were to guess, I would say April would be most probable for the release, but if the next HeroDevs client takes a while to be ready it might come before that.


fix(resolution): Fix resolution of querystringed imports in ESM files

Note: This PR is built on top of https://github.com/vercel/nft/pull/322 which I took over because @lobsterkatie is currently out.

Currently, there are two problems with the way @vercel/nft handles ESM imports with querystrings (import * as something from './someFile?someQuerystring';):

It treats the ? as it would any other character. As a result, it fails to resolve such imports to the non-querystringed files to which they correspond. (In the above example, it looks for a file named someFile?someQuerystring.js and, as one would expect, doesn't find it.) While this is the correct behavior for require calls in CJS files, it doesn't match the way that Node handles ESM imports (which is to strip the querystring off before attempting to resolve the file).
In cases where a custom resolve method is provided, and that custom method does strip querystrings from ESM imports, the querystrings are then not put back on before the imported module is processed. This matters, for example, in cases where readFile is also overridden, with a method whose output is affected by the querystring's value. (Webpack is such a system, so one place this shows up is in Next.js's NextTraceEntryPointsPlugin.)

This fixes both of those problems by selectively stripping and re-adding the querystring in ESM imports at various points in the nodeFileTrace lifecycle. More specifically, in resolveDependecy and in emitDependency and its helpers, we strip the querystring (and/or don't add it back), with the exception of:

When we're marking a path  as seen, we keep the querystring so that having a different querystring makes the process run again.
When we're calling readFile, we keep the querystring, since some implementations of readFile, including the one in the nft webpack plugin, read different modules out of memory with different querystrings).
When we're calling resolve, we add the querystring back in, since this is also something which can be supplied by the user, and and the user-supplied version might care about query strings.
When we're caching analysis results, we keep the querystring, since again here, we may have different code to analyze if we have a different querystring.
When we're making the recursive call to emitDependency, we add the querystring back in, since we need it there to be able to start the whole cycle over.

Notes:

Because the behavior here depends on whether or not a module is ESM, I needed to pass cjsResolve to the recursive call of emitDependency. Rather than change emitDependency's signature, I opted to make emitDependency a wrapper for an inner function (analyzeAndEmitDependency) with the updated signature. Recursive calls now go to the inner function.
For context, we on the @sentry/nextjs team are interested in this because we use a webpack loader to insert in the dependency tree a proxy module for each page, which allows us to automatically wrap users' exported functions (getServerSideProps and friends, API route handlers, etc). To do this, we replace the code from /path/to/pages/somePage.js with our proxy code, which includes an import from './somePage?__sentry_wrapped__'. When webpack then crawls our proxy module looking for dependencies, the querystring tricks it into thinking it hasn't yet dealt with that page, so it forwards it to our loader a second time rather than skipping it. When our loader sees the querystring, it knows the code replacement has already been done, and returns the original page code untouched, thereby preserving the continuity of the dependency tree. This fix ensures that @vercel/nft successfully traces the modified tree.
The unit test testing that this doesn't break the (already correct) behavior in CJS when dealing with files with question marks in their names (cjs-querystring) required a little gymnastics in order to not break CI on Windows. It turns out that skipping the test on Windows wasn't enough - the mere fact that a file exists with a ? in its name is enough to cause Windows not to even be able to check out the commit. Therefore, the file is stored without any punctuation in its name, and before the tests run on non-Windows platforms, it is copied to a version which does have the punctuation, and which is git-ignored to enforce it not ending up in the repo in the future by accident. The dummy, no-punctuation version is stored in a folder in order to differentiate its path from that of the punctuated version by more than just the punctuation. That way, if the punctuated version is found, it's clear it's not just because the punctuation is somehow being ignored.

Fixes getsentry/sentry-javascript#5998.
Fixes #319.

@styfle New PR because @lobsterkatie is out over the holidays. You mind taking a look? It's the same changes but with the feedback on url.parse you wrote.
Btw, feel free to push any changes you want to make directly to this PR!

@lforst There are merge conflicts in the original PR as well as this PR

We don't need this anymore


add ros2_controllers as exec dependency

fixes #49
once merged, I believe this needs a re-release

Holding this PR to the next Foxy sync

Foxy sync is out! Merging!


Error while using dl_docs with a high enough --last_days parameter (or none)

Description of the bug
The command pytr dl_docs --debug --last_days xxx . (and pytr dl_docs --debug . is terminating with an error message.
To Reproduce
Steps to reproduce the behavior:

Go to 'folder I've always been using'
Ran the command pytr dl_docs --debug .
See error

Expected behavior
All documents etc. being successfully downloaded.
Error log
2024-11-01 09:20:57+0100 timeline  INFO     494/494: xxx -- Fertig - 2024-10-01T07:53:44
2024-11-01 09:20:57+0100 dl        DEBUG    File Transaktionsbestätigung\ Transaktionsbestätigung - xxx.pdf already in queue. Append document id 0f49107a-79df-4c79-8a78-51357cdecbba...
2024-11-01 09:20:57+0100 dl        DEBUG    file Transaktionsbestätigung\ Transaktionsbestätigung - xxx (0f49107a-79df-4c79-8a78-51357cdecbba).pdf already exists. Skipping...
2024-11-01 09:20:57+0100 timeline  INFO     Received all details
2024-11-01 09:20:57+0100 transactions INFO     Write deposit entries
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Scripts\pytr.exe\__main__.py", line 7, in <module>
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\pytr\main.py", line 219, in main
    asyncio.get_event_loop().run_until_complete(dl.dl_loop())
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\asyncio\base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\pytr\dl.py", line 81, in dl_loop
    await self.tl.process_timelineDetail(response, self)
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\pytr\timeline.py", line 175, in process_timelineDetail
    export_transactions(dl.output_path / 'all_events.json', dl.output_path / 'account_transactions.csv', sort = dl.sort_export)
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\pytr\transactions.py", line 51, in export_transactions
    lines = formatter.format_header() + "".join(lines)
                                        ^^^^^^^^^^^^^^
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\pytr\transactions.py", line 47, in <lambda>
    events = map(lambda x: Event.from_dict(x), timeline)
                           ^^^^^^^^^^^^^^^^^^
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\pytr\event.py", line 109, in from_dict
    fees, isin, note, shares, taxes = cls._parse_type_dependent_params(
                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\pytr\event.py", line 148, in _parse_type_dependent_params
    shares, fees = cls._parse_shares_and_fees(event_dict)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\xxx\AppData\Local\Programs\Python\Python311\Lib\site-packages\pytr\event.py", line 213, in _parse_shares_and_fees
    return return_vals["shares"], return_vals.get("fees", None)
           ~~~~~~~~~~~^^^^^^^^^^
KeyError: 'shares'

Environment

OS: Win10
pytr version: 0.3.0

Additional context
I've noticed, that using e.g. --last_days 320 works fine, but at roughly 340 days the error is thrown. There are 228 results at 320 days (which still works), and the error is thrown at 340 days with 238 results.

You probably have a currently ill supported event type in your timeline. Could you close in on the problematic event by varying the date and share its (redacted) json entry?

Hi there,
having the same issue here.
Usually I'm downloading with the following command pytr dl_docs --last_days 0 --workers 16 C:\tmp\TR
I've tracked it down with varying the --last_days parameter:

working: 300-304 days
not working: 305-365 days

This date is from today calculated the 02.01.2024. Maybe there is an issue with the change of the year?

So the problem starts 333d ago from today (03.11.2024) on 06.12.2023. According to the TR log nothing happend on that day, but on 07.12 I bought a bond (which does not seem to be traded on TR anymore).
from events_with_documents.json:
{
    "action": {
        "payload": "xxx",
        "type": "timelineDetail"
    },
    "amount": {
        "currency": "EUR",
        "fractionDigits": 2,
        "value": -xxx.xx
    },
    "badge": null,
    "details": {
        "id": "xxx",
        "sections": [
            {
                "action": {
                    "payload": "XS2326497802",
                    "type": "instrumentDetail"
                },
                "data": {
                    "icon": "logos/bondissuer-529900381YTPHVY9AI06/v2",
                    "status": "executed",
                    "subtitleText": null,
                    "timestamp": "2023-12-07T06:59:36.156+0000"
                },
                "title": "Du hast xxx,xx €  investiert",
                "type": "header"
            },
            {
                "action": null,
                "data": [
                    {
                        "detail": {
                            "functionalStyle": "EXECUTED",
                            "text": "Ausgeführt",
                            "type": "status"
                        },
                        "style": "plain",
                        "title": "Status"
                    },
                    {
                        "detail": {
                            "action": null,
                            "text": "Kauf",
                            "trend": null,
                            "type": "text"
                        },
                        "style": "plain",
                        "title": "Orderart"
                    },
                    {
                        "detail": {
                            "action": null,
                            "text": "Anleihe Apr. 2026",
                            "trend": null,
                            "type": "text"
                        },
                        "style": "plain",
                        "title": "Asset"
                    }
                ],
                "title": "Übersicht",
                "type": "table"
            },
            {
                "action": {
                    "payload": {
                        "sections": [
                            {
                                "action": null,
                                "title": "Transaktion",
                                "type": "title"
                            },
                            {
                                "action": null,
                                "data": [
                                    {
                                        "detail": {
                                            "action": null,
                                            "text": "xxx,xx €",
                                            "trend": null,
                                            "type": "text"
                                        },
                                        "style": "plain",
                                        "title": "Nominale"
                                    },
                                    {
                                        "detail": {
                                            "action": null,
                                            "text": "xx,xx %",
                                            "trend": null,
                                            "type": "text"
                                        },
                                        "style": "plain",
                                        "title": "Kurs"
                                    },
                                    {
                                        "detail": {
                                            "action": null,
                                            "text": "xxx,xx €",
                                            "trend": null,
                                            "type": "text"
                                        },
                                        "style": "highlighted",
                                        "title": "Order"
                                    }
                                ],
                                "title": null,
                                "type": "table"
                            },
                            {
                                "action": null,
                                "data": [
                                    {
                                        "detail": {
                                            "action": null,
                                            "text": "xxx,xx €",
                                            "trend": null,
                                            "type": "text"
                                        },
                                        "style": "plain",
                                        "title": "Order"
                                    },
                                    {
                                        "detail": {
                                            "action": null,
                                            "text": "x,xx €",
                                            "trend": null,
                                            "type": "text"
                                        },
                                        "style": "plain",
                                        "title": "Stückzinsen"
                                    },
                                    {
                                        "detail": {
                                            "action": null,
                                            "text": "x,xx €",
                                            "trend": null,
                                            "type": "text"
                                        },
                                        "style": "plain",
                                        "title": "Gebühr"
                                    },
                                    {
                                        "detail": {
                                            "action": null,
                                            "text": "xxx,xx €",
                                            "trend": null,
                                            "type": "text"
                                        },
                                        "style": "highlighted",
                                        "title": "Gesamt"
                                    }
                                ],
                                "title": null,
                                "type": "table"
                            }
                        ]
                    },
                    "type": "infoPage"
                },
                "data": [
                    {
                        "detail": {
                            "action": null,
                            "text": "x,xx €",
                            "trend": null,
                            "type": "text"
                        },
                        "style": "plain",
                        "title": "Gebühr"
                    },
                    {
                        "detail": {
                            "action": null,
                            "text": "xxx,xx €",
                            "trend": null,
                            "type": "text"
                        },
                        "style": "highlighted",
                        "title": "Gesamt"
                    }
                ],
                "title": "Transaktion",
                "type": "table"
            },
            {
                "action": null,
                "data": [
                    {
                        "action": {
                            "payload": "https://traderepublic-data-production.s3.eu-central-1.amazonaws.com/timeline/xxx",
                            "type": "browserModal"
                        },
                        "detail": "07.12.2023",
                        "id": "xxx",
                        "local_filepath": "Abrechnung\\2023-12-07 Abrechnung - Anleihe Apr. 2026.pdf",
                        "postboxType": "SECURITIES_SETTLEMENT",
                        "title": "Abrechnung"
                    },
                    {
                        "action": {
                            "payload": "https://traderepublic-data-production.s3.eu-central-1.amazonaws.com/timeline/xxx",
                            "type": "browserModal"
                        },
                        "detail": "07.12.2023",
                        "id": "xxx",
                        "local_filepath": "Kosteninformation\\2023-12-07 Kosteninformation - Anleihe Apr. 2026.pdf",
                        "postboxType": "COSTS_INFO_BUY_V2",
                        "title": "Kosteninformation"
                    }
                ],
                "title": "Dokumente",
                "type": "documents"
            },
            {
                "action": null,
                "data": [
                    {
                        "detail": {
                            "action": {
                                "payload": {
                                    "contextCategory": "NHC",
                                    "contextParams": {
                                        "chat_flow_key": "NHC_0029_wealth_bonds_past_trade_execution",
                                        "groupId": "xxx",
                                        "timelineEventId": "xxx"
                                    }
                                },
                                "type": "customerSupportChat"
                            },
                            "icon": "logos/timeline_communication/v2",
                            "style": "highlighted",
                            "type": "listItemAvatarDefault"
                        },
                        "style": "plain",
                        "title": "Report a issue"
                    }
                ],
                "title": "Hilfe",
                "type": "table"
            }
        ]
    },
    "eventType": "ORDER_EXECUTED",
    "has_docs": true,
    "icon": "logos/bondissuer-529900381YTPHVY9AI06/v2",
    "id": "xxx",
    "source": "timelineTransaction",
    "status": "EXECUTED",
    "subAmount": null,
    "subtitle": "Kauforder",
    "timestamp": "2023-12-07T06:59:36.156+0000",
    "title": "Anleihe Apr. 2026"
}

Thanks for sharing the bond event entry @evo-de. You can use the PR for a quick fix that leaves the shares csv field empty.
As I read the event entry, TR provides neither the number of bond shares nor the price of one bond share, and as we lack TR's exact discount rate formula, the coupon payment dates, and a high precision interest rate, I believe we can't precisely infer the number of shares bought as of now (please correct me if my understanding is wrong).
Also, as there might be other bond related events that are currently not supported, I would suggest renaming the issue to something like "Support for bonds" to collect such issues.


DCOS-11759: [2/2] disable fields in Container, Health Checks and Volumes section

This PR introduces a feature where certain fields are disabled depending on the runtime environment. This needs also to be applied to the networking section as soon as it is done.
Mesos Runtime

UCR Runtime:

Docker Runtime:

mesosphere-ci retest this please

I get some errors when I try and test this out.

@Poltergeist Rebased the branch and fixed the lock icon. Code looks good to me. Great job! 💯  Feel free to merge once the test pass.


docs(CONTRIBUTING) pnpm init

pnpm init is not an interactive command. Thus, it does not need -y flag. In fact, it fails with the -y flag.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Looks good to me @MEnnabah  - Please can you sign this 👆


Implement Tabs

Problem
The tabs should show:

[ ] Groupings with individual insights functions
[ ] Show/hide
[ ] Summary component (Insight functions have any number of the following: map component, summary component and dashboard details component.)

Proposed Solution
Implement this.

@cchristelis , how do you calculate the size of the task? I'm just curious. Because for me this task is not the size of 2.

@dimasciput, I added that as an estimate of the remainder of the issue. Let's update it if it was a way off estimation.


feat: allow students to view grades

This pull request is to add a feature of viewing grades. This feature allows students to views their grades for all the courses they are currently registered for in the semester.
The changes are:

Create a database for the grades
Add teacher's comments to the assignment for a student

This branch is perfect!


Suggestion: run example remotely

Issue
Example(s) can be run remotely, in the Deno style.
Details
I created a local config file:
import { rollup } from<EMAIL_ADDRESS>const options = {
  input<EMAIL_ADDRESS>  output: {
    dir: "./dist",
    format: "es",
    sourcemap: true
  },
};
const bundle = await rollup(options);
await bundle.write(options.output);

which can then be run with deno run. If you change example/rollup.build.ts to use the full URL rather than a local file, you can then run it with deno run -A --unstable<EMAIL_ADDRESS>I think this is better for people wanting to try it out. In fact, people can fork the repo and edit their fork to try different things. No need to install anything.

Hey @probins 👋
Good shout! We can update the various READMEs to point out that the example can be run without installing or cloning anything ☺It certainly is one of the cool features of Deno!

Hey @probins 👋
Good shout! We can update the various READMEs to point out that the example can be run without installing or cloning anything ☺It certainly is one of the cool features of Deno!

wow, that was a fast response 😄
Wandering off-topic ... if you're updating the main Readme, you should fix the Contributing link too.

wow, that was a fast response 😄
Wandering off-topic ... if you're updating the main Readme, you should fix the Contributing link too.

wow, that was a fast response 😄
Wandering off-topic ... if you're updating the main Readme, you should fix the Contributing link too.

Ah oops 😅 yep good spot!

wow, that was a fast response 😄
Wandering off-topic ... if you're updating the main Readme, you should fix the Contributing link too.

Ah oops 😅 yep good spot!

If you spot anything else, feel free to raise another issue / a PR to fix 🚀

If you spot anything else, feel free to raise another issue / a PR to fix 🚀


Fixes 785

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 96cc943c949c58807c6876733a9355bee3f44494
https://deploy-preview-8240--docsdocker.netlify.com


ci: treat warning as err on ci

In case we forget to fix some warnings or the code may not pass the latest rust compiler check or clippy lint, we should treat all warnings as error when checking on CI.
@ngaut @siddontang @disksing @zhangjinpeng1987 PTAL

LGTM

LGTM


Error when setting breakpoint

I don't have a minimal example yet or an idea of what part of my code is necessary to share, but for now I'll just dump this here:
julia> breakpoint(parse, (JMain.Sentences.Sentence, String))
ERROR: AssertionError: llvmf != C_NULL
 in get_function_addr(::Type{T}) at /Users/malmaud/.julia/v0.5/Gallium/src/Hooking/Hooking.jl:438
 in _breakpoint_concrete at /Users/malmaud/.julia/v0.5/Gallium/src/Gallium.jl:802 [inlined]
 in breakpoint(::Function, ::Tuple{DataType,DataType}) at /Users/malmaud/.julia/v0.5/Gallium/src/Gallium.jl:811
 in eval(::Module, ::Any) at ./boot.jl:231
 in macro expansion at ./REPL.jl:92 [inlined]
 in (::Base.REPL.##1#2{Base.REPL.REPLBackend})() at ./event.jl:46

Are you sure you have a matching method? Did you mean
breakpoint(parse, (Type{JMain.Sentences.Sentence}, String))

Admittedly not the best error message ;)

Oh woops, thanks.