CRC 2.39.0 fails to start VM - Unable to determine VM's IP address

General information

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

CRC version
CRC version: 2.39.0+0849cb
OpenShift version: 4.16.0

CRC status
DEBU CRC version: 2.39.0+0849cb
DEBU OpenShift version: 4.16.0
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>2 bytes
WARN A new version (2.40.0) has been published on https://developers.redhat.com/content-gateway/file/pub/openshift-v4/clients/crc/2.40.0/crc-linux-amd64.tar.xz
DEBU Checking file: /home/itsme/.crc/machines/crc/.crc-exist
INFO Using bundle path /home/itsme/.crc/cache/crc_libvirt_4.16.0_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/itsme/.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>2 bytes
INFO Check if Podman binary exists in: /home/itsme/.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
DEBU libvirt group is active for the current user/process
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd service is running
DEBU Running 'systemctl status virtqemud.socket'
DEBU Command failed: exit status 4
DEBU stdout:
DEBU stderr: Unit virtqemud.socket could not be found.
DEBU virtqemud.socket is neither running nor listening
DEBU Running 'systemctl status libvirtd.socket'
DEBU libvirtd.socket is running
INFO Checking if a supported libvirt version is installed
       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/itsme/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_libvirt_4.16.0_amd64...
DEBU Using secret from configuration
INFO Creating CRC VM for OpenShift 4.16.0...
DEBU Found binary path at /home/itsme/.crc/bin/crc-driver-libvirt-amd64
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:43961
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-08-08T20:41:52+02:00" level=debug msg="About to check libvirt version"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Could not find storage pool 'crc', trying to create it"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Creating storage pool"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=info msg="Creating storage pool with XML <pool type=\"dir\">\n  <name>crc</name>\n  <target>\n    <path>/home/itsme/.crc/machines/crc</path>\n  </target>\n</pool>"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Activating pool 'crc'"
DEBU (crc) Calling .GetConfigRaw
DEBU Creating machine...
DEBU (crc) Calling .Create
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Preparing /home/itsme/.crc/machines/crc/crc.qcow2 for machine use"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="image creation took 140.6532ms"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Verifying executable bit set on /home/itsme/.crc/machines/crc"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Verifying executable bit set on /home/itsme/.crc/machines"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Verifying executable bit set on /home/itsme/.crc"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Verifying executable bit set on /home/itsme"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Verifying executable bit set on /home"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Defining VM..."
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Found q35 machine type"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2024-08-08T20:41:52+02:00" level=debug msg="Found q35 machine type"
DEBU (crc) DBG | time="2024-08-08T20:41:53+02: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/itsme/.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 (crc) DBG | time="2024-08-08T20:41:53+02:00" level=debug msg="Closing plugin on server side"
DEBU Checking file: /home/itsme/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/itsme/.crc/bin/crc-driver-libvirt-amd64
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:44749
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-08-08T20:41:53+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2024-08-08T20:41:53+02:00" level=debug msg="Fetching VM..."
INFO Starting CRC VM for openshift 4.16.0...
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2024-08-08T20:41:53+02:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2024-08-08T20:41:53+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2024-08-08T20:41:53+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2024-08-08T20:41:59+02:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2024-08-08T20:41:59+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2024-08-08T20:41:59+02:00" level=debug msg="Waiting for machine to come up 0/60"
DEBU (crc) DBG | time="2024-08-08T20:42:02+02:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2024-08-08T20:42:02+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2024-08-08T20:42:02+02:00" level=debug msg="Waiting for machine to come up 1/60"
DEBU (crc) DBG | time="2024-08-08T20:42:05+02:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2024-08-08T20:42:05+02:00" level=debug msg="Getting current state..."
.
.
DEBU (crc) DBG | time="2024-08-08T20:44:57+02:00" level=debug msg="Waiting for machine to come up 59/60"
DEBU Making call to close driver server
DEBU (crc) Calling .Close
DEBU (crc) DBG | time="2024-08-08T20:45:00+02:00" level=warning msg="Unable to determine VM's IP address, did it fail to boot?"
DEBU Successfully made call to close driver server
DEBU Making call to close connection to plugin binary
Error starting machine: Error in driver during machine start: Unable to determine VM's IP address, did it fail to boot?

The debug log shows DEBU systemd-networkd.service is not running, so I enabled and started it, but than crc start complains it cannot work with systemd-networkd.service, so I stopped and disabled it again.
I also see errors about systemctl status virtqemud.socket' which cannot be found (not running nor listening). It was my understanding that this should be available when installing libvirt-daemon-system`. I installed the following applications:
sudo apt install qemu-system qemu-kvm qemu-utils libvirt-daemon-system libvirt-clients bridge-utils virt-manager virtiofsd

Am I missing another library here?
I understand libvirtd is moving away from monolith to modules. I didn't get the modular approach to work though.
CRC config
- consent-telemetry : no
- cpus : 6
- memory : 12000

Host Operating System
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

Steps to reproduce

Booting QEMU from Windows 11 host (with 64 GB RAM) using a batch file with the following options (using networking mode NAT). I noticed the crc network runs in bridge mode and thought that might be a problem. I tried to run QEMU in bridge, but didn't get that to work together with SPICE (the image won't boot if I use bridge mode).
@echo off

setlocal enabledelayedexpansion

:: Define the QEMU executable
set "QEMU_EXE=qemu-system-x86_64.exe"

:: Define the image name you want to check
set "IMAGENAME=ubuntu_24_04_openshift"

:: Define the image path and name
set "IMAGE=%QEMU_VMS%\ubuntu_24_04_openshift.img"

:: Check if the QEMU process is running with the specified image
tasklist /v /fi "IMAGENAME eq %QEMU_EXE%" | findstr /i "%IMAGENAME%" >nul

:: Check the exit code of findstr
if %ERRORLEVEL% == 0 (
    echo QEMU is already running image %IMAGENAME%.  >nul
  if !errorlevel!==0 (
    start "" cmd /c virt-view.bat
  )
)

endlocal

Checked if NetworkManager is installed and running on Ubuntu guest. This was the case.

Installed QEMU and related applications on Ubuntu guest, enabled and started libvirtd:
sudo apt update
sudo apt install qemu-system qemu-kvm qemu-utils libvirt-daemon-system libvirt-clients bridge-utils virt-manager virtiofsd
sudo systemctl enable libvirtd
sudo systemctl start libvirtd

crc setup

crc start

crc config set cpus 6

crc config set memory 12000

Added the following to /etc/hosts oh Ubuntu guest:
<IP_ADDRESS> console-openshift-console.apps-crc.testing
<IP_ADDRESS> api.crc.testing

Expected
CRC to start succesfully and
Actual
crc start takes a long time, and log shows 60 tries to GetIP for crc.
Doing another start shows:
WARN A new version (2.40.0) has been published on https://developers.redhat.com/content-gateway/file/pub/openshift-v4/clients/crc/2.40.0/crc-linux-amd64.tar.xz
INFO Loading bundle: crc_libvirt_4.16.0_amd64...
INFO A CRC VM for OpenShift 4.16.0 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: 85ZcW-5NNFG-xrAG7-GrWN8

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

But a crc status shows:
CRC VM:          Running
OpenShift:       Unreachable (v4.16.0)
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     29.05GB
Cache Directory: /home/itsme/.crc/cache

The CRC VM is running, but OpenShift is unreachable because it didn't get an IP assigned?
Logs
Before gather the logs try following if that fix your issue
$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug  on http://gist.github.com/ and post the link in the issue.

output of crc start --log-level debug, see section 'CRC status' above.

virsh net-list --all
Name      State     Autostart   Persistent
--------------------------------------------
crc            active   yes            yes
default      active  yes            yes

nmcli connection
NAME                    UUID                                                                TYPE          DEVICE
netplan-ens3         bec3d02a-c9e5-3283-92ab-ee43a4246c85     ethernet    ens3
br-12289fa1b7f2   79dbbcf1-efb7-4917-86aa-ed554ce68698      bridge       br-12289fa1b7f2
br-1320b7416fbc  7d79898d-6661-4cde-9057-e1961fa6e1ec      bridge       br-1320b7416fbc
br-cea5fed94f89   5e19f443-e297-41d0-a1cc-a5553ac173d6       bridge      br-cea5fed94f89
lo                           b7e6b12c-1c2f-4708-9166-5c9a18fd27cd       loopback  lo
crc                         b266103a-b44d-4981-8707-ba982d53281b    bridge      crc
docker0                 c5784d34-1ac6-49bf-910e-63ddd34c699d     bridge      docker0
virbr0                     98714c75-c32e-4a6d-a7cd-c25ce7344ab8     bridge      virbr0

virsh net-dumpxml crc | grep -i dhcp
<dhcp>
</dhcp>

systemctl status libvirtd.service

systemctl status NetworkManager
     NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
     Active: active (running) since Thu 2024-08-08 20:19:18 CEST; 39min ago
       Docs: man:NetworkManager(8)
    Process: 11993 ExecReload=/usr/bin/busctl call org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager Reload u 0 (code=exit>
   Main PID: 920 (NetworkManager)
      Tasks: 4 (limit: 38418)
     Memory: 22.1M (peak: 125.2M)
        CPU: 2.876s
     CGroup: /system.slice/NetworkManager.service
             /usr/sbin/NetworkManager --no-daemon

Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8874] device (crc): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface->
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8877] device (crc): state change: unavailable -> disconnected (reason 'connection-assumed', sys-ifa>
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8882] device (crc): Activation: starting connection 'crc' (b266103a-b44d-4981-8707-ba982d53281b)
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8885] device (crc): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'externa>
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8886] device (crc): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8888] device (crc): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8890] device (crc): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8982] device (crc): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'externa>
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8987] device (crc): state change: secondaries -> activated (reason 'none', sys-iface-state: 'extern>
Aug 08 20:51:58 itsme NetworkManager[920]: <info>  [1723143118.8990] device (crc): Activation: successful, device activated.

Older (related?) bugs/posts?
I have seen older other similar bugs around here:

https://github.com/crc-org/crc/issues/2732

Eventually was solved by starting libvirtd if I understand correctly. In my case libvirtd is started.

https://github.com/crc-org/crc/issues/2397

@Manfred73 Hi, If I understood correctly you are trying to run crc on a ubuntu VM which is running on windows machine. Why can't you directly use crc on that windows machine ? In past we also issue which raised by users are using nested virt (check the label) and in your case also it is same. We don't perform nested virtualization so not even sure why it is happen, Also we recently did 2.40.0 release try that and see if that works (it fixes one of the issue https://github.com/crc-org/machine-driver-libvirt/pull/122 if underlying hardware is AMD one)

I want to use an Ubuntu/Linux image with crc and other tooling pre installed for training purposes, so I can easily share the image. Some users will have macOS, some Linux and some Windows. First I tried Virtual Box, but understood that doesn't work at all with nested virt and crc. I understood QEMU did supporr this.
Are there workarounds for this, or assigning IP manually.
I will try the newer version also.

Check the logs under /var/log/libvirt/qemu/crc.log and see if there is any error, otherwise VM should able to get the IP automatic. Also you can try following if that help
$ crc delete
$ crc cleanup
$ crc config set network-mode user
$ crc setup
$ crc start

I do see one error related to libvirtd in the crc.log (see log attached):
crc.log
libvirt:  error : libvirtd quit during handshake: Input/output error
2024-08-08 22:07:04.951+0000: shutting down, reason=failed
2024-08-09 05:21:30.494+0000: Starting external device: virtiofsd

I also followed the steps you mentioned before, but without the crc config set network-mode user. I have tried them again, including this option which seems to do something.
I did crc delete followed by crc cleanup:
$ crc config set network-mode user
Network mode changed. Please run `crc cleanup` and `crc setup`.

It suggests I do crc cleanup again, which results in an error (unexpected AppArmor template file /etc/apparmor.d/libvirt/TEMPLATE.qemu, cannot configure it automatically):
$ crc cleanup
INFO Removing vsock configuration
INFO Removing 'crc' network from libvirt
INFO Removing /etc/NetworkManager/dispatcher.d/99-crc.sh file
INFO Cleaning up AppArmor configuration
INFO Removing crc daemon systemd socket units
INFO Removing crc daemon systemd service
INFO Removing crc's virtual machine
INFO Removing crc libvirt storage pool
INFO Removing CRC Specific entries from user's known_hosts file
INFO Removing hosts file records added by CRC
INFO Removing pull secret from the keyring
INFO Removing older logs
unexpected AppArmor template file /etc/apparmor.d/libvirt/TEMPLATE.qemu, cannot configure it automatically
Network mode changed. Please run `crc cleanup` and `crc setup`.

Then crc setup:
$ crc setup
INFO Using bundle path /home/itsme/.crc/cache/crc_libvirt_4.16.4_amd64.crcbundle
INFO Checking if running as non-root
INFO Checking if running inside WSL2
INFO Checking if crc-admin-helper executable is cached
INFO Checking if running on a supported CPU architecture
INFO Checking if crc executable symlink exists
INFO Creating symlink for crc executable
INFO Checking minimum RAM requirements
INFO Check if Podman binary exists in: /home/itsme/.crc/bin/oc
INFO Checking if Virtualization is enabled
INFO Checking if KVM is enabled
INFO Checking if libvirt is installed
INFO Checking if user is part of libvirt group
INFO Checking if active user/process is currently part of the libvirt group
INFO Checking if libvirt daemon is running
WARN No active (running) libvirtd systemd unit could be found - make sure one of libvirt systemd units is enabled so that it's autostarted at boot time.
INFO Starting libvirt service
INFO Using root access: Executing systemctl daemon-reload command
INFO Using root access: Executing systemctl start libvirtd
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Checking crc daemon systemd service
INFO Setting up crc daemon systemd service
INFO Checking crc daemon systemd socket units
INFO Setting up crc daemon systemd socket units
INFO Checking if AppArmor is configured
INFO Updating AppArmor configuration
INFO Using root access: Updating AppArmor configuration
INFO Using root access: Changing permissions for /etc/apparmor.d/libvirt/TEMPLATE.qemu to 644
INFO Checking if vsock is correctly configured
INFO Setting up vsock support
INFO Using root access: Setting CAP_NET_BIND_SERVICE capability for /home/itsme/bin/crc executable
INFO Using root access: Creating udev rule for /dev/vsock
INFO Using root access: Changing permissions for /etc/udev/rules.d/99-crc-vsock.rules to 644
INFO Using root access: Reloading udev rules database
INFO Using root access: Loading vhost_vsock kernel module
INFO Using root access: Creating file /etc/modules-load.d/vhost_vsock.conf
INFO Using root access: Changing permissions for /etc/modules-load.d/vhost_vsock.conf to 644
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if /home/itsme/.crc/cache/crc_libvirt_4.16.4_amd64.crcbundle exists
Your system is correctly setup for using CRC. Use 'crc start' to start the instance

Now, doing a crc start gives the following error (failed to expose port <IP_ADDRESS>:2222 -> <IP_ADDRESS>:22: listen tcp <IP_ADDRESS>:2222: bind: address already in use):
I have github locally installed on Ubuntu guest as docker, using ports 2222:22.
$ crc start -p ~/bin/pull-secret.txt --log-level debug
DEBU CRC version: 2.40.0+a14925
DEBU OpenShift version: 4.16.4
DEBU MicroShift version: 4.16.4
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>2 bytes
DEBU No new version available. The latest version is 2.40.0
DEBU Checking file: /home/itsme/.crc/machines/crc/.crc-exist
INFO Using bundle path /home/itsme/.crc/cache/crc_libvirt_4.16.4_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/itsme/.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>2 bytes
INFO Check if Podman binary exists in: /home/itsme/.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
DEBU libvirt group is active for the current user/process
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd service is running
DEBU Running 'systemctl status virtqemud.socket'
DEBU Command failed: exit status 4
DEBU stdout:
DEBU stderr: Unit virtqemud.socket could not be found.
DEBU virtqemud.socket is neither running nor listening
DEBU Running 'systemctl status libvirtd.socket'
DEBU libvirtd.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/itsme/.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 AppArmor is configured
INFO Checking if vsock is correctly configured
DEBU Running 'getcap /home/itsme/bin/crc'
DEBU Checking file: /home/itsme/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_libvirt_4.16.4_amd64...
DEBU Using secret from configuration
INFO Creating CRC VM for OpenShift 4.16.4...
DEBU Found binary path at /home/itsme/.crc/bin/crc-driver-libvirt-amd64
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:36177
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-08-12T22:20:55+02:00" level=debug msg="About to check libvirt version"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Validating storage pool"
DEBU (crc) Calling .GetConfigRaw
DEBU Creating machine...
DEBU (crc) Calling .Create
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Preparing /home/itsme/.crc/machines/crc/crc.qcow2 for machine use"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="image creation took 77.478378ms"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Verifying executable bit set on /home/itsme/.crc/machines/crc"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Verifying executable bit set on /home/itsme/.crc/machines"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Verifying executable bit set on /home/itsme/.crc"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Verifying executable bit set on /home/itsme"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Verifying executable bit set on /home"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Defining VM..."
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Found q35 machine type"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2024-08-12T22:20:55+02:00" level=debug msg="Found q35 machine type"
DEBU (crc) DBG | time="2024-08-12T22:20:56+02: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/itsme/.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/itsme/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/itsme/.crc/bin/crc-driver-libvirt-amd64
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:46607
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-08-12T22:20:56+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2024-08-12T22:20:56+02:00" level=debug msg="Fetching VM..."
INFO Starting CRC VM for openshift 4.16.4...
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
failed to expose port <IP_ADDRESS>:2222 -> <IP_ADDRESS>:22: listen tcp <IP_ADDRESS>:2222: bind: address already in use

crc status shows:
$ crc status
CRC VM:          Stopped
OpenShift:       Stopped (v4.16.4)
RAM Usage:       0B of 0B
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     27.61GB
Cache Directory: /home/itsme/.crc/cache

libvirt:  error : libvirtd quit during handshake: Input/output error
2024-08-08 22:07:04.951+0000: shutting down, reason=failed
2024-08-09 05:21:30.494+0000: Starting external device: virtiofsd

I think following explain it, looks like libvirt is not working at all properly and VM is not running, you can check status of the VM using sudo virsh list --all and might see the VM in stopped state. This might be the reason why ssh is failing.

I create a complete new Ubuntu image and right after that installed prerequisites for crc (docker, libvirt):
sudo apt install qemu-system qemu-kvm qemu-utils libvirt-daemon-system libvirt-clients bridge-utils virt-manager virtiofsd

Right after that installed crc:
crc config set network-mode user
crc setup
crc start

libvirt service is running:
libvirtd.service - libvirt legacy monolithic daemon
     Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: enabled)
     Active: active (running) since Tue 2024-08-13 23:41:18 CEST; 6min ago
TriggeredBy: libvirtd.socket
             libvirtd-admin.socket
             libvirtd-ro.socket
       Docs: man:libvirtd(8)
             https://libvirt.org/
   Main PID: 1070 (libvirtd)
      Tasks: 26 (limit: 32768)
     Memory: 36.3M (peak: 42.4M)
        CPU: 1.312s
     CGroup: /system.slice/libvirtd.service
             1070 /usr/sbin/libvirtd --timeout 120
             1244 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             1245 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
             3224 /usr/libexec/virtiofsd --fd=34 -o source=/home/itsme

Aug 13 23:41:19 itsme dnsmasq[1244]: using nameserver <IP_ADDRESS>#53
Aug 13 23:41:19 itsme dnsmasq[1244]: read /etc/hosts - 8 names
Aug 13 23:41:19 itsme dnsmasq[1244]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names
Aug 13 23:41:19 itsme dnsmasq-dhcp[1244]: read /var/lib/libvirt/dnsmasq/default.hostsfile
Aug 13 23:41:19 itsme libvirtd[1070]: libvirt version: 10.0.0, package: 10.0.0-2ubuntu8.3 (Ubuntu)
Aug 13 23:41:19 itsme libvirtd[1070]: hostname: itsme
Aug 13 23:41:19 itsme libvirtd[1070]: ignoring socket '/home/itsme/.crc/machines/crc/docker.sock'
Aug 13 23:41:51 itsme libvirtd[1070]: End of file while reading data: Input/output error
Aug 13 23:43:49 itsme libvirtd[1070]: End of file while reading data: Input/output error
Aug 13 23:46:58 itsme libvirtd[1070]: End of file while reading data: Input/output error

crc status shows:
CRC VM:          Running
OpenShift:       Unreachable (v4.16.4)
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     27.61GB
Cache Directory: /home/itsme/.crc/cache

sudo virsh list --all shows:
 Id   Name   State
----------------------
 1    crc    running

In the crc.log I still see ssh handshake errors:
2: read: connection reset by peer\n - sleeping 1s"
time="2024-08-13T23:46:54+02:00" level=debug msg="retry loop: attempt 75"
time="2024-08-13T23:46:54+02:00" level=debug msg="Running SSH command: exit 0"
time="2024-08-13T23:46:54+02:00" level=debug msg="Using ssh private keys: [/home/itsme/.crc/machines/crc/id_ecdsa /home/itsme/.crc/cache/crc_libvirt_4.16.4_amd64/id_ecdsa_crc]"
time="2024-08-13T23:46:57+02:00" level=debug msg="SSH command results: err: ssh: handshake failed: read tcp <IP_ADDRESS>:48438-><IP_ADDRESS>:2222: read: connection reset by peer, output: "
time="2024-08-13T23:46:57+02:00" level=debug msg="error: Temporary error: ssh command error:\ncommand : exit 0\nerr     : ssh: handshake failed: read tcp <IP_ADDRESS>:48438-><IP_ADDRESS>:2222: read: connection reset by peer\n - sleeping 1s"

and in /var/log/libvirt/qemu/crc.log still one handhake errors:
libvirt:  error : libvirtd quit during handshake: Input/output error

We can only debug more around this if it can reproduce in our testing/dev environment and which is not the case :( . There is lot of things depend for failure like base/guest HyperVisor and also underlying hardware. As I told before nested-virt tests are not something we perform or encourage users to do it. If possible try on native hypervisor to see if it still fails instead nested-virt.


Add UTMJ as a university in Github Education

Add UTMJ as a university in Github Education

@muhidinutmj Thank you for your patience while waiting for a review and processing your request. Pull request merged.

Thank you @philipto


Cannot switch languages, application menu gets selected when click L alt + shift

My Setup

Operating System: Xubuntu 18.04
App Version: 2.16.0
Installation type:
package manager .deb

[x] I have tested with the latest version
[x] I can simulate the issue easily

Description

Current Behavior

This menus get selected when I try to switch languages when typing (Left shift + Left alt buttons), thus resulting I cannot type after switching input languages.
Expected Behavior

Just type normally after language switching. Actually this was working few versions earlier. It's broken now.

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.
Thank you!


pull request for e2e test at 01/05/2017 08:56:11

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


Date field - keyboard comes up on mobile

Is there a way to disable the keyboard from popping up on the datepicker field?

Closing for lack of action.


DO NOT MERGE pseudo Fix bug: Ensure that the last segement will be delete.

This PR need more work in order to solve the another  problem  6e33cd4e0adc340e352f80636d34bdc89054825a.
The bug is a corner case that happens when the someone try to delete the last segment.
Upon a request to delete the last segment is issued, the list of available segments is an empty (availableSegments.isEmpty() == true ), the the last segments will not be dropped.

Looks good to me. I'm curious why this was present in the first place.

I think the reason for having the check was given by @gianm in this commit https://github.com/druid-io/druid/commit/6e33cd4e0adc340e352f80636d34bdc89054825a. Maybe he can chime in to make sure this won't break his intended change.

That change fixed a bug in which the coordinator would drop all segments if it started running cleanup before it finished polling the metadata storage for available segments for the first time. That happened once in our cluster and it wasn't fun :)
There may have been a similar bug for coordinators that lose leadership, since when that happens their availableSegments are cleared out, but their stuff-doer threads keep running for a bit (until they realize they're supposed to stop). The change in 6e33cd4 would have fixed that too, if it existed.

So :-1: unless there is another strategy in place for preventing the coordinator from doing whacky things when availableSegments is empty due to recently having gained or lost leadership.

I remember this bug. Agree with @gianm that we cannot make this change.
:-1:

Can we get a test for that case?

@drcrallen i have the test part of our CI pipeline, do you mean a unit test ?

@b-slim We cannot merge this PR as is, during periods of ZK connectivity issues where leadership is won and lost, these changes will cause all segments in your cluster to be dropped. One thing that would be useful is a unit test where we can reproduce the bug in question and we can have a discussion about the best way to fix things.

@b-slim : What @fjy said :)

@drcrallen and @fjy.
Reproducing the BUG is fairly easy you can try deleting all the segments and you will see that some of them won't be gone.
Understanding why this happens it is straightforward from the code in this PR.
I do understand that we can not merge this since it will cause another problem, i am fine with that, we have a work around the leak bug.
Now the question is: Should i close this PR and submit an issue or how should i proceed ?
Finally i will be more than happy to discuss a general fix for both problems

@b-slim : You should probably submit an issue regardless of the solution approach since it is technically an issue. If you are able to publicly disclose any workaround that would be preferable as well. Also please link to Gian's comment above in the issue so that it is clear any solution must account for that scenario. This PR should be fine to keep the solution in because it keeps the discussion history, but as long as the issue has a link here it is not at all required and at your discretion. If it is not ready for review yet, please either change the title to indicate as such (something like Fix bug: Ensure that the last segement will be delete (DO NOT MERGE YET)) or just closing this PR and re-opening when you're ready for review. Note that github doesn't like to re-open pull requests when the commit history has changed on the PR, so don't rebase until the PR is open unless you're trying to just close and forget this PR (which is fine)
TL;DR
File Issue: yes.
New PR or this one: your choice.

@drcrallen thanks for the clarification, i did changed the description.

Given that we don't really have a good fix for this issue yet, I am going to close this PR until we have a better solution. @b-slim do you mind filing a corresponding issue so we don't forget about this.

Parag Jain asked,
"@tdingus are you hitting this - #1274
Do you have a single segment in the cluster ? Are you getting any error while deleting ?
"
Yes. I have a single segment in the cluster. I don't see any error log while deleting. If I should expect any error log, where should I look for it.
thanks


Version 3.0 --> Carthage support!

This PR is based primarily off of: https://github.com/Roobiq/RBQFetchedResultsController/pull/57 by @ataibarkai. I needed to continue his awesome work to make sure Cocoapods still worked and then did a general file/folder clean up.

@ataibarkai I couldn't push to your fork, so I created this branch that includes all of your changes and then I added further work to clean up everything and ensure Cocoapods still works. Please review... and because the bulk of the work is yours, feel free to create a new branch off of this and a new PR. Would rather the PR be based on your request to merge.

@ataibarkai I would suggest that you create a new branch off of this and then rebase your commits so that you can squash the history a bit. A lot of those commits are directory changes that I then had to adjust a bit, so might as well squash them down so the history is cleaner. I can then merge a PR off of that.

Can you please change it back that was not me but an evil gf

How can I regain the ability to install with pics again

@bigfish24 ok looks great.
I'll try to get to it in the next 1-2 days.

This PR supersedes this one: https://github.com/Roobiq/RBQFetchedResultsController/pull/61

@bigfish24 just submitted the (hopefully final!) pull request.
I'm sorry it took me a little while, I was a bit busy over the last few days.
Thanks for your help + extra tidy-ups.
I'll see what extra changes you've made and try to replicated them on the RealmMapView project, hopefully we can put that one behind us too pretty soon.
Might take me a little while though, I'm going to be fairly busy over the next 2 weeks or so.

@ataibarkai awesome thanks for the help with this. I was going to check out what needs to be done with the map view too. I am out of town this weekend, so won't be till next week though. Will merge your PR this afternoon.

@bigfish24 👍👍👍


⚠ Cioos National CKAN Sitemap has degraded performance

In f5ac4e1, Cioos National CKAN Sitemap (https://catalogue.cioos.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 24584 ms

Resolved: Cioos National CKAN Sitemap performance has improved in d155aaf after 4 minutes.


Retrieving logged in user from resulting application

Hi
When I login with this to my server, is there anyway of passing the username/email address in some way to the web app the user ends up in, or is it necessary for the user to log in again to the end app to get a login?

@amlwwalker there is option -pass-basic-auth=true: pass HTTP Basic Auth, X-Forwarded-User and X-Forwarded-Email information to upstream.
If your app work on php then check phpinfo() for global variable _SERVER['X-Forwarded-User/Email'].
By the way this is just a guess.


Update examples and documentation for backend compatibility

Fix #9
Signed-off-by: Alexandre Beslic<EMAIL_ADDRESS>

Coverage remained the same at 84.082% when pulling 9039aadee214c8e2a2e45325143d4f37d6c7c0cd on update_docs into 0c128f602bfaff683d8872133b85dd3be2b80430 on master.


test(linter): add more tests fo rules-of-hooks

closes #6651

#7683  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 5, 10:17 AM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.

🙏🏻 Thanks!


Return special error for end of queue [phab:D2205]

Created by salguarnieri at 2018-02-27 21:51:48:
#2652 changed what was expected to be returned when the end of a queue is reached.

schroederc accepted this revision at 2018-03-01 17:20:00

salguarnieri closed via commit 46c73059665ca01d304244a0e91305b078976346 at 2018-03-01 17:21:30


The JSON string is not formed correctly (ID)

Describe the bug
there is an error in the generation of the JSON.
The ID can also contain letters (z.B. BF) and must be in "".
Client [ESPWeatherLSD-39B225] Cannot parse "ESPWeatherLSD-39B225/data/LSDWetterSensor": {"id":000000BF,"ch":0,"battery_ok":1,"temp_c":16.9,"humidity":59,"wind_gust":0.0,"wind_avg":0.4,"wind_dir":202.5,"rain":28.8,"rain_d":0.0,"rain_w":0.0,"rain_m":0.0}
The line 427 in the BresserWeatherSensorMQTTCustom.ino
old
     sprintf(&mqtt_payload[strlen(mqtt_payload)], "\"id\":%08X", weatherSensor.sensor[i].sensor_id);
new
     sprintf(&mqtt_payload[strlen(mqtt_payload)], "\"id\":\"%08X\"", weatherSensor.sensor[i].sensor_id);

Fixed in https://github.com/matthias-bs/BresserWeatherSensorReceiver/commit/b880b30ded0a883a4586234dc6080ff23caf6dca and https://github.com/matthias-bs/BresserWeatherSensorReceiver/commit/6191c8ec74d3b4c2c7d80f2e61b48953bf70de9c.

N.B. All three sensors I used for testing have only the digits 0...9 in there IDs - that's why I did not notice this problem.

Yes.
Kann geschlossen werden.
Danke


cortex_m: linker.ld: Remove fw_info extabis section code

Will be implemented with zephyr_linker_sources() instead.
Signed-off-by: Øyvind Rønningstad<EMAIL_ADDRESS>

That's done https://github.com/NordicPlayground/fw-nrfconnect-nrf/blob/1d8b907d6f073d1f0d7180f3a07a70a5b2efa58c/subsys/fw_info/CMakeLists.txt#L9 here right?

That's done https://github.com/NordicPlayground/fw-nrfconnect-nrf/blob/1d8b907d6f073d1f0d7180f3a07a70a5b2efa58c/subsys/fw_info/CMakeLists.txt#L9 here right?

Yep

DNM until NordicPlayground/fw-nrfconnect-nrf#1378 is merged or equivalent PR

This needs to go in first so west.yml can be fixed in NordicPlayground/fw-nrfconnect-nrf#1378.

So stuff will be broken between the time between this is merged and  NordicPlayground/fw-nrfconnect-nrf#1378 is merged?

So stuff will be broken between the time between this is merged and NordicPlayground/fw-nrfconnect-nrf#1378 is merged?

It's like it always is when merging something into fw-nrfconnect-zephyr. We'll try to merge this right before, update west.yml, and then merge NordicPlayground/fw-nrfconnect-nrf#1378.

Got it, adding DNM label so that this is not merged by accident until the other PR is ready to merge then :)

So stuff will be broken between the time between this is merged and NordicPlayground/fw-nrfconnect-nrf#1378 is merged?

It's like it always is when merging something into fw-nrfconnect-zephyr. We'll try to merge this right before, update west.yml, and then merge NordicPlayground/fw-nrfconnect-nrf#1378.

What will be "broken", exactly? I'm confused.
The reason we use SHAs as revisions in west.yml is so we can update the entire NCS atomically with a single commit to nrf. Changes from other repositories are done by updating the SHAs. So although master/master might not work from time to time, that's not what's being distributed to others.

This looks like a straightforward revert of 4cc4339; why not just use 'git revert' so that 'west ncs-loot' knows the patch is gone? That way it will disappear entirely in the next rebase.

Good point, will change to revert.

Some checks failed. Please fix and resubmit.
Gitlint issues
1: UC2 Body does not contain a 'Signed-off-by:' line
Identity/Emails issues
86ca4b5ff144a25fbf719ce684df360bed699d7c: author email (Øyvind Rønningstad<EMAIL_ADDRESS>needs to match one of the signed-off-by entries.
Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.

History in this repository has been rewritten. Please rebase this PR.


Use standard pattern to initialization Heat defaults

Removing debug pod ...
error: unable to upgrade connection: container container-00 not found in pod oko-19-xpqjm-master-0-debug_openstack-kuttl-tests

/test openstack-operator-build-deploy-kuttl


Use FakeProviderForBackendV2()

FakeProvider() was removed in the latest release of qiskit-ibm-runtime

 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.


fix: handle change on country selection

The onChange does not trigger when country is updated which is unexpected
The didChange was not called because of which the form was on a bad state
fix: handle change on country selection

Thanks.
Could you

update the changelog to add an entry this bug was fixed
add a test so this doesn't break in the future.


Serialize maps as json when passed to jsonify to allow API based frontend

map objects should be jsonificable

Can you explain more?

from flask import jsonify
from flask_googlemaps import Map

@app.route('/')
    map = Map(......)
    return jsonify(map=map)

When accessed that url should return a json with map values
{map : {
  identifier:...
  markers: ...
  ...
  ...
}}

I think the flask jsonify code is well documented, related to this issue. I want to take this one if you guys are ok with it. Or are you already on this @vmesel ?

No problem @chicao ! Go on!

Hey @rochacbruno,
I did some stuff regarding the Markup setup of javascript and html  that I'm not sure if is acceptable. I passed the .js and .html through the json.dumps function so if somebody wants to load the map using AJAX, it might be possible.
However, I tried to create a view this dynamically to load the GMaps through JQuery AJAX function, referencing the jsonify routes of polygons and polylines maps, but everytime I tried to load dynamically it returned a JS Reference error of the google lib.  IDK if it's even a requirement, so let me know if there is anything I should fix.


chore: Update to run on Python 3.6 to Python 3.10.

G'day mate.
Updates to pyproject.toml:
I have updated the python requires so autoclasstoc can run on up to Python 3.10.
I have updated the Trove classifiers to reflect the Python versions.
I have tested locally using Tox for all the Python versions listed.
py36: commands succeeded
py37: commands succeeded
py38: commands succeeded
py39: commands succeeded
py3.10: commands succeeded
py38pypy: commands succeeded
py39-docs: commands succeeded
congratulations :)
cheers

Sorry, this dropped off my radar.  Thanks for the PR!


Updated readme issue link

I updated the issue link since this seems to be the official repo for the package.
Is there a way we can enable the issues for this repo?

@j4qfrost please open issues for this repository

Sorry I was busy on other projects and this got lost in spam. Opened the issues. @passsy @leoafarias


[REQUEST] please support ipv6 for masternode

Current masternode setup only supports ipv4
As one of the leading crypto currencies on the market, will be great to support ipv6
Thanks

This was discussed many times on dash.org/forum.
TL;DR: not sooner the IPv6 adoption rises to some meaningful levels, see https://www.google.com/intl/en/ipv6/statistics.html etc. OR when we drop everything that requires direct IP access to masternodes (like mixing) OR when we switch to some kind of custom routing for such cases (which is going to be much slower and require much more traffic IMO).

@UdjinM6
other MN coins using ipv6
so i don't get where the complexity is coming from?
should be able to support ipv4, ipv6, and tor

Did you even take the time to read into the discussions WHY masternode entries other than IPv4 are not supported?
The complexity comes from the fact the you are not able to properly route between the different networks without the help of another overlay network - which none of the coins has afaik.
E.g. tell me: How is a IPv4-only connected wallet supposed to connect to a Tor listed masternode during mixing?
We are well aware that 150 MN coins copied our masternode code and re-enabled IPv6/Tor list entries, but they do not actually use these entries for something useful.
But maybe you know something we don't know, so: What "other MN coin" is actually using the nodes for something different than locking up coins and have them idling around?

Technical discussion on the issue here: https://github.com/dashpay/dash/pull/1065
TL;DR: the Dash team didn't want to have to disable ipv6 for MNs, but there are technical reasons this change was made, and it was for the health of the network (as @schinzelh said, ipv4 only nodes couldn't connect to ipv6 nodes). With ipv4-only as it is now, all MNs are able to provide a benefit to the entire network (not just ipv6 nodes).

Closing issue as it's a duplicate and this is a known, intentional Dash network architecture decision.


Bugfix for SitePicker

Q
A

Bug fix?
[ x ]

New feature?
[ x ]

New sample?
[ ]

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Fixed a bug where the selected sites would not load into the property pane. Also reordered the documentation alphabetically.

Thank you @nsoeth for the fix!


Contribute: instructions for setting up a develop/test environment

We need explicit instructions for setting up a local environment that is appropriate for development and testing.
Note that we have a list of software that is required; see https://github.com/keptn/lifecycle-toolkit/issues/1000 .  This PR is to create instructions about what to do and in what order.
Contributes to https://github.com/keptn/lifecycle-toolkit/issues/972

hey @StackScribe I would like to work on this😁

closing in favor of https://github.com/keptn/lifecycle-toolkit/issues/1887


Consider the extensibility of Client and RequestBuilder

See some early discussion in #346
The two main approaches I can think of here are similar to the ones used to make types fully extendable in iron - namely embedding a TypeMap in these structs to allow storing arbitrary metadata and using modifiers to manipulate them.
TypeMap allows adding new fields and modifier enables adding new builder-style methods. Plugins can be used to add new getters by building on TypeMap, but I think they might be a bit heavy for hyper.
That this features so prominently in the design of iron makes me think that this might be a bit much for hyper to do vs. a higher-level client abstraction; it's possible this kind of stuff just doesn't belong.

Isn't this belong to #373? I looked at modifiers and I like the idea to use them for the client.

That this features so prominently in the design of iron makes me think that this might be a bit much for hyper to do vs. a higher-level client abstraction; it's possible this kind of stuff just doesn't belong.

What is the goal of hyper? I know hyper is currently more low level, but I think people will need an HTTP client like Pythons requests lib. Since we already provide a client we should be able to make this client powerful.

I don't think an extensions or whatever map needs to be on Client. Any extensions desired can be handled by a higher level Client, as https://github.com/hyperium/hyper/issues/346#issuecomment-82574384 states.
Modifiers may make creating a new Client more ergonomic, as opposed to one-off methods like set_redirect_policy, but without an extensions map to edit, they lose much of their worth.
@pyfisch The goal is to provide a fast, correct, and safe implementation of HTTP. I'm less interested in including specializations that only some people need (when I look at npm's request package and see hawk and aws options, I shudder). It should be ergonomic to use, such that if someone thinks "Hey, I need to make some HTTP requests", they can use hyper without wanting to faceroll their keyboard.

RequestBuilder is no more (on master).


Make worker error propagate to client

What changes are proposed in this pull request?
This PR can fix the OOM Error no longer reply to client issue.
2022-10-19 11:41:38,397 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 60006 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:42:38,404 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 120013 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:43:38,409 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 180018 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:44:38,415 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 240024 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:45:38,418 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 300027 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:46:38,424 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 360033 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:47:38,428 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 420037 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:48:38,418 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 480027 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:49:38,427 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 540036 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:50:38,436 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 600045 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:51:38,446 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 660055 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader
2022-10-19 11:52:38,451 WARN  GrpcBlockingStream - Client did not receive message from stream, will wait again. totalWaitMs: 720060 clientClosed: false clientCancelled: false serverClosed: false description: Zero Copy GrpcDataReader

I did the following changes

After patched this PR, client will receive the error and choose another worker
2022-10-19 12:07:56,324 WARN  GrpcBlockingStream - Received error io.grpc.StatusRuntimeException: INTERNAL: XXX for stream (Zero Copy GrpcDataReader)
2022-10-19 12:07:56,338 WARN  AlluxioFileInStream - Failed to read block 268435456 of file /NOTICE4 from worker WorkerNetAddress{host=localhost, containerHost=, rpcPort=29999, dataPort=29999, webPort=30000, domainSocketPath=, tieredIdentity=TieredIdentity(node=localhost, rack=null)}. This worker will be skipped for future read operations, will retry: alluxio.exception.status.InternalException: XXX (Zero Copy GrpcDataReader).

alluxio-bot, check this please

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-2.9 please

alluxio-bot, cherry-pick this to branch-2.9 please

@beinan I think after this change, the worker would still be in an unstable state and not crash even client tries on another worker. I think the correct behavior would be to crash the worker after the reply. What's your opinion?

@jja725 You are right. From the RPC handler thread an uncaught ex will only crash the RPC thread instead of the worker process. This somewhat fall under the same category as https://github.com/Alluxio/alluxio/issues/16381, using ProcessUtils.fatalError() is not a great practice, we should define a way to propagate the error to the main thread and crash there.


Update to TypeScript v2

When will we have TypeScript v2 support for this extension? I don't see any pull requests related to it, or issues for that matter besides various tidbits.

Unclear - hopefully soonish.
For now you can use the Additional Flags feature to support most of the TypeScript 2.1 stuff, and grunt-ts already supports using any compiler you want.  Hopefully it shouldn't take more than a few minutes to get nearly everything working for you with TypeScript 2.1 and grunt-ts.
The main cause for the delay is there are some new TypeScript features in 2.x that are technically only supported via tsconfig.json (since they're arrays and that's awkward to pass on the command line so the TypeScript team doesn't support it).  So, we need to add support for it via grunt options and this is going to mean some major effort to switch our tsc calling mechanism to temporary tsconfig.json files.

Awesome, thanks for the response @nycdotnet, I'll try out those flags and see if I can get something working.

Closing.


Login flow UI

Add screens and components to auth navigation based on the ui and design theme.

I wanna start working on this


[Bug]: German support page still online and states Electron is compatible with Windows 7

Preflight Checklist

[X] I have read the Contributing Guidelines for this project.
[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for a bug report that matches the one I want to file, without success.

Electron Version
28.0.0
What operating system are you using?
Windows
Operating System Version
Windows 10
What arch are you using?
x64
Last Known Working Electron version
No response
Expected Behavior
The German support page is still available in the documentation
Here is the link: https://www.electronjs.org/de/docs/latest/tutorial/unterstützung
Actual Behavior
The content of the page should be updated to the content of the page in the English version of the documentation
Here is the support page in English: https://www.electronjs.org/docs/latest/tutorial/support
Testcase Gist URL
No response
Additional Information
It seems like an outdated German version of the electron website is still online. Accessing the outdated link and then clicking the logo shows the old website, which is a bit broken.

This seems to be an issue with how the build flow just uploads the build without cleaning up old files from previous builds that don't need to be there anymore.
I've been doing this manually in static storage whenever this crops up, but we should find a cleaner way of doing things. 🤔

This page should 404 at least now. Thanks for the report @flavienbonvin! We have an old issue open for problems like this so I'll track it there: https://github.com/electron/website/issues/139


Advanced Types

I'm submitting a ...

[x] feature request

Advanced Types.

Resolved in https://github.com/RommelTJ/LearningTypeScript/pull/21


Make Sass imports less broad

This PR replaces globals/common import in each component with only the necessary partials.
There is already a test that checks if individual component Sass files compile.
Note: i've placed typography partials at the end of imports to make it a bit easier to do the work of making typography imports conditional.
https://trello.com/c/unO51Rno/830-make-sass-imports-dependencies-less-broad

Seems fine to me, the main problem is that we were importing files that output CSS.
So could solve this by chunking the imports better too.


Add Au Central endpoints

Fixes #44845

@Potapy4 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Potapy4 - Thanks, I just got back from vacation and after reviewing your proposed change, I need to confirm this with engineering before I approve.

I just heard back from engineering and the job runtime URL is incorrect.  It should be - ac-jobruntimedata-prod-su1.azure-automation.net. Once you fix this I can approve for merge.  Thanks!

@MGoedtel fixed


Docker container issue

when a docker PostgreSQL container get crash/stop how could i recover data . is it any possible to recover ?

If your data is mounted as a volume you can try starting a new container from it, otherwise if it's corrupted then this comment might help you.
Going to close since this isn't an issue with the image and should be asked over at the Docker Community Forums, the Docker Community Slack, or Stack Overflow


feat: icon requires aria-hidden or aria-label

Purpose
Closes #707
Approach
Type IconProps to require either aria-hidden or aria-label
Testing
Icon stories.
Risks
Breaking change: current integrators will need to retro-apply either attribute to all <Icon> instances.
I don't like this risk, I'd introduce the attributes as optional for now.

What do you think about the Risk?

If it defaults to something, it's no longer required 🙈
It won't be any different than having no extra types at all.

Right, it would not.
Then it would be - hiding unless a label is set.
Maybe that's also fine?

As discussed I'll leave this PR open as a breaking change being introduced, for us to merge later on when we're ready for 2.0

Yes, that's fine 👍
However, if you could still take a look at failing build please 😏


Make translation note filenames use the correct language code.

Currently, TN files must be named en_tn_-.tsv (ex: en_tn_59-TIT.tsv)
tC should replace en_ with the language abbreviation (ex: hi_) to the TN files that it creates.  This will mean that a TN file pair will look like:
en_tn_57-TIT.tsv  | hi_tn_57-TIT.tsv
DoD: opening a new file with en_tn_ will replace 'en' with the chosen language abbreviation and create the file with the target language abbreviation in the repo. Opening a file without a language code does not strip anything away.

@birchamp Per this issue, should the toolbar have the target name. It currently shows the source name:

@birchamp See above post.
Also, wanted to confirm some things...

UTN files are the only resource types that include in the filename the language id and resource type. So to some extent, this is a problem of own making... any idea why UTN is different in this respect? Should it be?
To trap this and fix it, I think the following will work:

if source and target repos are not the same (ie, this is a translation task, not an editing/update task)
if target file is a UTN file (the format with the entangled filename prefix)
then correct the the UTN prefix so that it match the target repo instead of the source repo.

@RoyalSix @ancientTexts-net Steps to reproduce and status with first push (still not working):

in an org different from unfoldingWord (may not be required), create a UTN resource repo. For example in have an org named "mandolyte". I created a new repo named ru_tn for Russian Translation Notes.
then running tc-create, select the org, the UTN resource type, and Russian (or whatever), say Titus.
the current production code creates the branch with commits against en_tn_57-TIT.tsv when it should be named ru_tn_57-TIT. The target file context is not in Gitea-React-Toolkit. It is in tc-create-app. Well you can see what I have changed.
I have intercepted the UTN case and when the target repo is different, then correct the target filename.
This fixes that part, but it does not load the file.
Be sure to consult the console.log... I have a number of debug statements there and there are some HTTP 500 errors that may be relevant.

Be sure to read the above comment as well. This whole problem would not exist if the filenames did not have the repo name as a prefix. Not sure why they do when no other resource type does this.

TargetFile.context.js:42 TargetFileContextProvider() targetRepo, filepath, _filepath, sourceFile {id: 52515, owner: {…}, name: "ru_tn", full_name: "mandolyte/ru_tn", description: "testing for issue #325", …} en_tn_66-JUD.tsv ru_tn_66-JUD.tsv {name: "en_tn_66-JUD.tsv", path: "en_tn_66-JUD.tsv", sha: "c91562c9a78609ed811821213899b0166a4a97b7", type: "file", size: 17331, …}
TargetFile.context.js:42 TargetFileContextProvider() targetRepo, filepath, _filepath, sourceFile {id: 52515, owner: {…}, name: "ru_tn", full_name: "mandolyte/ru_tn", description: "testing for issue #325", …} en_tn_66-JUD.tsv ru_tn_66-JUD.tsv {name: "en_tn_66-JUD.tsv", path: "en_tn_66-JUD.tsv", sha: "c91562c9a78609ed811821213899b0166a4a97b7", type: "file", size: 17331, …}
TargetFile.context.js:42 TargetFileContextProvider() targetRepo, filepath, _filepath, sourceFile {id: 52515, owner: {…}, name: "ru_tn", full_name: "mandolyte/ru_tn", description: "testing for issue #325", …} en_tn_66-JUD.tsv ru_tn_66-JUD.tsv {name: "en_tn_66-JUD.tsv", path: "en_tn_66-JUD.tsv", sha: "c91562c9a78609ed811821213899b0166a4a97b7", type: "file", size: 17331, …}
TargetFile.context.js:42 TargetFileContextProvider() targetRepo, filepath, _filepath, sourceFile {id: 52515, owner: {…}, name: "ru_tn", full_name: "mandolyte/ru_tn", description: "testing for issue #325", …} en_tn_66-JUD.tsv ru_tn_66-JUD.tsv {name: "en_tn_66-JUD.tsv", path: "en_tn_66-JUD.tsv", sha: "c91562c9a78609ed811821213899b0166a4a97b7", type: "file", size: 17331, …}

Will this affect tC? @birchamp

@ancientTexts-net Please note that I added to the DOD. If the file doesn't have a language code, nothing should get stripped away.

@ancientTexts-net Noticed these lines in Translatable.js. These conditions and assumptions are not valid for tN as long as the language code is part of the filename.
    if (
      filepath &&
      sourceFile &&
      targetFile &&
      filepath === sourceFile.filepath &&
      filepath === targetFile.filepath
    ) {

@ancientTexts-net Noticed these lines in Translatable.js. These conditions and assumptions are not valid for tN as long as the language code is part of the filename.
    if (
      filepath &&
      sourceFile &&
      targetFile &&
      filepath === sourceFile.filepath &&
      filepath === targetFile.filepath
    ) {

Originally I was assigned to this but was unable to make it work. Never did figure out why. I looked up my branch so you can see what I was thinking of doing:
https://github.com/unfoldingWord/tc-create-app/compare/bugfix-cn-325-lang-id-in-trans-filename
@ancientTexts-net Of course, you can read all my notes above in this issue made as I discovered things.

Originally I was assigned to this but was unable to make it work. Never did figure out why. I looked up my branch so you can see what I was thinking of doing:
https://github.com/unfoldingWord/tc-create-app/compare/bugfix-cn-325-lang-id-in-trans-filename
@ancientTexts-net Of course, you can read all my notes above in this issue made as I discovered things.

@ancientTexts-net don't use ensurefile for multiple checks

Check en prefix, then ensurefile noprefix

@RobH123 needs to weigh in on the new filename scheme before we can continue.

@ancientTexts-net
After a lot of deliberation, it was determined that it is preferable to keep the names as is and wait until the conversion to the 7 column format is done.  The converter will be written to change the file name as well.


Add design document for LMS.

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

Put a hold on this to discuss with the OTC..
In particular the new API and what is supported/not supported need to be discussed.

May I ask for a requirement that if any signing operation is implemented that it can be disabled at built time, leaving only verification operations available?
LMS is something that should never been implemented in a generic software system, NIST and NSA as well recommend that LMS and XMSS signatures are implemented only in Hardware, and the reason is that duplicating state is catastrophic, and in software duplicating state is as simple as restarting a machine after a crash where updates didn't get to disk, or copying around files.
We do not want to give our users a knife that has cyanide laced razor blades for a handle.

May I ask for a requirement that if any signing operation is implemented that it can be disabled at built time, leaving only verification operations available?
LMS is something that should never been implemented in a generic software system, NIST and NSA as well recommend that LMS and XMSS signatures are implemented only in Hardware, and the reason is that duplicating state is catastrophic, and in software duplicating state is as simple as restarting a machine after a crash where updates didn't get to disk, or copying around files.
We do not want to give our users a knife that has cyanide laced razor blades for a handle.

There is no intention of implementing the sign operation..

Thanks for your input @rjrelyea

I would go even further that what Simo said.
I consider not only presence of signature creation a problem, but signature verification too.
Safe use of any stateful hash based signature formats absolutely and unequivocally depends on the signature operation being performed in hardware. Doing it in a way that allows for disaster recovery, over 10, or 20+ years of use, is orders of magnitude harder still. That means that there will be very few originators of such signatures. Which means they will be used in very few places.
In case we have widely deployed implementations that can verify such signatures, there definitely will be people that don't know better and actually implement and use signature creation in software. So, just presence of signature verification is an incentive to do the wrong thing.
As such, I don't think openssl should ship with any code that can do LMS verification. It can have support for providers that support it (to support the hardware modules), but I think including verification code is a mistake. If there are specific users asking for it, it should be a separate provider module, not part of OpenSSL proper. Users should not be able to expect that LMS is supported out of the box.
See also: Nuclear Non-proliferation Treaty

I would go even further that what Simo said.
I consider not only presence of signature creation a problem, but signature verification too.
Safe use of any stateful hash based signature formats absolutely and unequivocally depends on the signature operation being performed in hardware. Doing it in a way that allows for disaster recovery, over 10, or 20+ years of use, is orders of magnitude harder still. That means that there will be very few originators of such signatures. Which means they will be used in very few places.
In case we have widely deployed implementations that can verify such signatures, there definitely will be people that don't know better and actually implement and use signature creation in software. So, just presence of signature verification is an incentive to do the wrong thing.

There is no state associated with the signature verification, so I dont agree. There are many things in crypto that you can do wrong if you dont know what you are doing.
@t-j-h Would you care to respond to why we should do HSS signature and key generation in OpenSSL.

My point is that there is a difference between "it's hard to do it correctly" and "there's literally at most double digit number of corporations in the world that will be able to do a production deployment correctly".

While I agree that with hubert that only a handful of entities will be able to correctly deploy keygen and signatures, I don't agree verification will necessarily be wrong. Those handful of entities will be creating signatures that millions of users may need to verify. The use cases for these signature algorithms are basically sign an object once and many people verify that signature over the course of the next couple of decades.
Anyone with enough skill to replace the signature/keygen portion will also have enough skill to know the dangers of not doing this with hardware tokens. The guidance is pretty widespread.

And if we expect that only a handful of entities will be creating such signatures, why would we want to have code for verifying them when processing any and all signatures?
Reasonably there are two usages for stateful signatures: root CAs and signing software/firmware. In both cases you know a priori if you'll need support for a stateful hash signature. So if that need arises, the code can load the necessary provider ahead of time.
There's another reason for not including it in OpenSSL proper: stateful signatures are very much a transitionary, niche technology. Long term we will end up using stateless hash signatures, lattice based, or something else still. By including it in OpenSSL, the project commits to supporting them for a long time.

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 61 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 92 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 123 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 154 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 61 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 91 days ago

This PR is in a state where it requires action by @openssl/otc but the last update was 122 days ago

Considering the recent additions to the EVP_PKEY_ sign and verify functionality, maybe this needs an update?  Is the new interface ready enough so this can simply be a matter of writing provider code?

I am in the process of writing the code..

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 30 days ago

This PR is in a state where it requires action by @openssl/committers but the last update was 61 days ago


rancher Metadata timeout

Hi,
When I start galera stack y have this error in log of all image galera-conf
 Error: Get http://rancher-metadata/2015-07-25/version: dial tcp: i/o timeout

Rancher Version:1.0.1-RC3
Docker Version: 1.10.3
thank

@oema We don't recommend users using RC releases (as they are haven't been validated through our QA team.
Did you see these same issues in v1.0.0?

I have similar with with Rancher 1.0.1. Actually I have seen various failures and occasionally it worked.
The way to access Rancher metadata in our case is through a proxy running on Rancher so http://rancher-metadata is accessible from outside of Rancher containers/hosts by setting proper proxy.
hao.ding@:~$ export http_proxy=http://proxy-as-rancher-container:3128
hao.ding@:~$ curl http://rancher-metadata/
hao.ding@:~$ curl http://rancher-metadata/ -v
*   Trying <IP_ADDRESS>...
* Connected to proxy-as-rancher-container (<IP_ADDRESS>) port 3128 (#0)
> GET http://rancher-metadata/ HTTP/1.1
> Host: rancher-metadata
> User-Agent: curl/7.43.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 404 Not Found
< Server: Apache-Coyote/1.1
< Content-Length: 0
< Date: Thu, 28 Apr 2016 00:51:29 GMT
<
* Connection #0 to host proxy-as-rancher-container left intact
hao.ding@:~$
hao.ding@:~$ curl http://rancher-metadata
hao.ding@:~$
hao.ding@:~$ curl --header 'Accept: application/json' 'http://rancher-metadata/2015-07-25'
hao.ding@:~$
hao.ding@:~$ curl http://rancher-metadata

<title>403 Forbidden</title>

403 Forbidden

nginx

hao.ding@:~$ curl http://rancher-metadata

<title>403 Forbidden</title>

403 Forbidden

nginx

hao.ding@:~$ curl http://rancher-metadata -v
* Rebuilt URL to: http://rancher-metadata/
*   Trying <IP_ADDRESS>...
* Connected to proxy-as-rancher-container (<IP_ADDRESS>) port 3128 (#0)
> GET http://rancher-metadata/ HTTP/1.1
> Host: rancher-metadata
> User-Agent: curl/7.43.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 OK
< Access-Control-Allow-Origin: *
< Date: Thu, 28 Apr 2016 00:59:08 GMT
< Content-Length: 29
< Content-Type: text/plain; charset=utf-8
< X-Cache: MISS from 9e739fb68901
< X-Cache-Lookup: MISS from 9e739fb68901:3128
< Via: 1.1 9e739fb68901 (squid/3.5.15)
< Connection: keep-alive
<
2015-07-25
2015-12-19
latest
* Connection #0 to host proxy-as-rancher-container left intact
hao.ding@:~$ curl http://rancher-metadata
hao.ding@:~$ curl http://rancher-metadata --connect-timeout 30 --retry 5
hao.ding@:~$ curl http://rancher-metadata -v
* Rebuilt URL to: http://rancher-metadata/
*   Trying <IP_ADDRESS>...
* Connected to proxy-as-rancher-container (<IP_ADDRESS>) port 3128 (#0)
> GET http://rancher-metadata/ HTTP/1.1
> Host: rancher-metadata
> User-Agent: curl/7.43.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 404 Not Found
< Server: Apache-Coyote/1.1
< Content-Length: 0
< Date: Thu, 28 Apr 2016 01:00:19 GMT
<
* Connection #0 to host proxy-as-rancher-container left intact
hao.ding@:~$ curl http://rancher-metadata -v
* Rebuilt URL to: http://rancher-metadata/
*   Trying <IP_ADDRESS>...
* Connected to proxy-as-rancher-container (<IP_ADDRESS>) port 3128 (#0)
> GET http://rancher-metadata/ HTTP/1.1
> Host: rancher-metadata
> User-Agent: curl/7.43.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< X-B3-Sampled: 1
< X-B3-SpanId: 367ddafadee5480a
< X-B3-TraceId: 367ddafadee5480a
< X-Application-Context: dce-service-gateway:8765
< Content-Type: application/json;charset=UTF-8
< Transfer-Encoding: chunked
< Date: Thu, 28 Apr 2016 01:04:16 GMT
<
* Connection #0 to host proxy-as-rancher-container left intact
{"links":[{"rel":"self","href":"http://rancher-metadata"},{"rel":"api","href":"http://rancher-metadata/api"},{"rel":"docs","href":"http://rancher-metadata/docs/api-documentation.html"},{"rel":"swagger","href":"http://rancher-metadata/webjars/swagger-ui/2.1.0/index.html?url=http://rancher-metadata/api-docs"}]}hao.ding@:~$
hao.ding@:~$
hao.ding@:~$ curl http://rancher-metadata --connect-timeout 30 --retry 5 -v
* Rebuilt URL to: http://rancher-metadata/
*   Trying <IP_ADDRESS>...
* Connected to proxy-as-rancher-container (<IP_ADDRESS>) port 3128 (#0)
> GET http://rancher-metadata/ HTTP/1.1
> Host: rancher-metadata
> User-Agent: curl/7.43.0
> Accept: */*
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 404 Not Found
< Server: Apache-Coyote/1.1
< Content-Length: 0
< Date: Thu, 28 Apr 2016 01:04:52 GMT
<
* Connection #0 to host proxy-as-rancher-container left intact

Hmmm... my problem might because of the LB setting with the proxy container. Need check more

@oema If you can try v1.0.1, please let me know if you still have issues.
@JayHaoDing When you can, provide an update on whether yours is regarding a proxy container.

@oema @JayHaoDing If either of you are still facing issues, please open a new one.


32bit Linux Binaries

I'm currently trying to set up multiboot functionality on a drive that is already running 32bit Linux. Trying to transplant the working game to a 64bit OS has gone poorly, so I wanted to ask if it a 32bit SGL release was possible.
If it can be done, but isn't a combination you plan to support, I'm also happy to build it myself. Appreciate the help.

Closing as I found a workaround while staying on 64bit Linux.

Sorry for the late reply.
32-bit releases should be possible but I expect this to be quite some work to add it to the build process. Some additional unknowns might be that some dependency might not built for 32-bit (properly) anymore.

Closing as I found a workaround while staying on 64bit Linux.

Curious what's the workaround that you found, do you mind sharing?
In general, I was wondering about your reasons for going for a 32-bit only platform still and what's holding you back from running this on 64-bit.

Curious what's the workaround that you found, do you mind sharing?
In general, I was wondering about your reasons for going for a 32-bit only platform still and what's holding you back from running this on 64-bit.

The short version is that I was trying to migrate something that was running on an older 32bit linux install to a Ubuntu 18 16bit and launch via SGL. Originally that wasn't working well, but I closed this after fighting long enough with that executable to get it running on the 64bit drive with SGL.
Due to some dependency hell issues, plus that executable hard coding paths it was looking for, I had trouble launching it via SGL (and also had trouble debugging what was wrong.) Instead, I tried getting the other applications running on that old 32bit linux drive and this worked, which is when I realized that I wouldn't be able to use SGL to launch them from there.


Only check digest on EOF

Fixes issue
On a partial tar read, closing the reader should not compare the digest. Fixes #502.

Describe the change
This moves the digest compare to only run after an EOF.

How to verify it
regctl image get-file alpine /etc/hosts

Changelog text
Fix digest check when running regctl image get-file

Please verify and check that the pull request fulfills the following requirements

[X] Tests have been added or not applicable
[X] Documentation has been added, updated, or not applicable
[X] Changes have been rebased to main
[X] Multiple commits to the same code have been squashed

Thank you!


Update "Next Task" to show Halo.Fi

The modal that shows after you claim (Next Task) needs to be updated to invite people to participate in the Halo.Fi campaign.
Copy was requested here: https://www.notion.so/gooddollar/68e052612b764adca4b26046d3310e06?v=ce8af698453747beaf6f9849f128aee6&p=0420384b8c2c4969a987e6e755627d52&pm=s
@L03TJ3 This needs to be released Wednesday before claim time
@drptiago Can you please set everything up to track clicks on this card?

Yes, we are properly tracking the events post claim, when the option is "INVITE_SHARE" @patpedrosa
So we have the invite share "task" and "share".

As soon we remove the invite_share button from there, this event will not make more sense, so we can:
Option 1: Use a bit.ly link, so we can track any clicks here and make a manual comparison with the number of claims.
Option 2: Put an event in the button "POST_CLAIM_CTA" or something like this.
Currently the "invite_share" from "task" triggers 15k events a month, so adding this event is not a problem in terms of events limit.

done here: https://github.com/GoodDollar/GoodDAPP/commit/f785b2aca130fa5f20c18670ddaef4eaedf571fa

@L03TJ3 no event was triggered when I click in start earning rewards
I expect to see the event POST_CLAIM_CTA to track how many users click on the button.  We can also use another name as NEXT_TASK_CTA to better fit the name we are using in this feature.
Also, send the link as property, so we can track different campaigns.

was fixed here: https://github.com/GoodDollar/GoodDAPP/commit/7dec79c00ad51b2c8814f60ab695dc78de71b615
deployed to prod now

@patpedrosa should we remove this modal?

Old issue and is already replaced with a newer task, so closing


[transport:ws] [data] close. code: 1006, reason: unknown reason

hello
I'm building Streamedian Test
System Environment：windows10
Log：
Client paused
Client started
[mse] Media source opened: open
[info] ------------- Info ---------------------
[info] License expires at : Invalid expiration time
[info] Requested domain : localhost
[info] -----------------------------------------
[client:rtsp] OPTIONS rtsp://<IP_ADDRESS>:554/H264/1/main/av_stream RTSP/1.0
 CSeq: 1
 User-Agent: SFRtsp 0.3

[mse] Media source ended: closed
[mse] Media source closed: closed
[mse] Media source opened: open
[client:rtsp] RTSP/1.0 200 OK
 CSeq: 1
 Public: OPTIONS, DESCRIBE, PLAY, PAUSE, SETUP, TEARDOWN, SET_PARAMETER, GET_PARAMETER
 Date: Wed, Sep 04 2019 14:40:19 GMT

[client:rtsp] DESCRIBE rtsp://<IP_ADDRESS>:554/H264/1/main/av_stream RTSP/1.0
 Accept: application/sdp
 CSeq: 2
 User-Agent: SFRtsp 0.3

[client:rtsp] RTSP/1.0 401 Unauthorized
 CSeq: 2
 WWW-Authenticate: Digest realm="54c41585c95e", nonce="efd2d12442bb4d9026b38c30f0beec3e", stale="FALSE"
 WWW-Authenticate: Basic realm="54c41585c95e"
 Date: Wed, Sep 04 2019 14:40:19 GMT

[client:rtsp] Basic realm="54c41585c95e"
[client:rtsp] DESCRIBE rtsp://<IP_ADDRESS>:554/H264/1/main/av_stream RTSP/1.0
 Accept: application/sdp
 CSeq: 3
 User-Agent: SFRtsp 0.3
 Authorization: Basic YWRtaW46YWRtaW45OTk5

[client:rtsp] RTSP/1.0 200 OK
 CSeq: 3
 Content-Type: application/sdp
 Content-Base: rtsp://<IP_ADDRESS>:554/H264/1/main/av_stream/
 Content-Length: 479

 v=0
 o=-<PHONE_NUMBER>871997<PHONE_NUMBER>871997 IN IP4 <IP_ADDRESS>
 s=Media Presentation
 e=NONE
 b=AS:5050
 t=0 0
 a=control:rtsp://<IP_ADDRESS>:554/H264/1/main/av_stream/
 m=video 0 RTP/AVP 96
 c=IN IP4 <IP_ADDRESS>
 b=AS:5000
 a=recvonly
 a=x-dimensions:1920,1080
 a=control:rtsp://<IP_ADDRESS>:554/H264/1/main/av_stream/trackID=1
 a=rtpmap:96 H265/90000
 a=Media_header:MEDIAINFO=494D4B48010200000400050000000000000000000000000000000000000000000000000000000000;
 a=appversion:1.0
[parser:sdp] Ignored unknown SDP directive: e=NONE
[parser:sdp] Ignored unknown SDP directive: b=AS:5050
[parser:sdp] Ignored unknown SDP directive: c=IN IP4 <IP_ADDRESS>
[parser:sdp] Ignored unknown SDP directive: b=AS:5000
[client:rtsp] SDP contained 1 track(s). Calling SETUP for each.
[client:rtsp] setup track: video
[remuxer] ontracks:
[transport:ws] [data] close. code: 1006, reason: unknown reason

system event viewer

How can I solve it?

莫名其妙好了

我也碰到这个问题了，一直在ontracks不动了，请问是什么原因啊

Html5 does not support  a=rtpmap:96 H265/90000
Need use h264
чт, 31 дек. 2020 г., 10:47 smellycat-tong<EMAIL_ADDRESS>
我也碰到这个问题了，一直在ontracks不动了，请问是什么原因啊
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Streamedian/html5_rtsp_player/issues/135#issuecomment-752833506,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEFIYKL2UYTSLRKV2J7VZ7TSXPX3JANCNFSM4ITN5EHQ
.


add test if a Alice and Bob create a dispute and A lice wins on https://github.com/kleros/kleros-api/blob/develop/tests/integration/contracts.test.js

Isn't this the same thing as tests/integration/disputeResolution.test.js


Lowlevel refactor tracker

Type of Issue
Select the type of issue:

[ ] Bug report (to report a bug)
[ ] Feature request (to request an additional feature)
[x] Tracker (I am just using this as a tracker)
[ ] Refactor request
[ ] Documentation Ask

Checklist
Parent issue: #337

[ ] minecraft :

[x] cuberite_process.py:

[x] from droidlet.perception import build_shape_scene

[x] place_blocks.py -> new folder cuberite
[x] repo.py -> delete and fix paths
[x] size_words.py moved to interpreter
[x] block_data -> craftassit_cuberite
[x] build_utils - delete and moved functions to base_util
[x] mc_util cleanup
[x] wait_for_cuberite.py move functions
[x] move all relevant functions to craftassist_cuberite_utils
[x] minecraft_specs/read_images.py:

[x] remove value for home_dir
[x] cleanup + refactor

[x] client/generate_recipes.py delete ?

[x] locobot :

[x] locobot_mover.py:

[x] from droidlet.perception.robot import RGBDepth
[x] from droidlet.interpreter.robot.objects import Marker, Pos

[x] locobot_mover_utils.py:=

[x] fix : from droidlet.lowlevel.locobot.rotation import yaw_pitch to from .rotation import yaw_pitch

[x] locobot_util:

[x] duplicate : group_by function (same in base_util)
[x] duplicate hash_user function (same in base_util)
[x] shasum_file duplicate check
[x] class TimingWarn might be a duplicate with base_util
[x] euclid_dist
[x] manhat_dist
[x] XYZ, POINT_AT_TARGET, IDM , Block, Hole , T = TypeVar("T")

[x] tests:

[x] import in test_mover: from droidlet.lowlevel.locobot.locobot_mover import LoCoBotMover
[x] from droidlet.lowlevel.locobot.locobot_mover_utils import in test_utils

[ ] remote_locobot.py:

[x] add use_dslam to docstring (go_to_relative, go_to_absolute
[ ] code for transform_pose is duplicated in depth_utils
[x] in_global missing in docstring for get_current_pcd

[x] fix import open3d as o3d in RGBDepth

[x] refactor base_util:
[ ] add tests for lowlevel
[x] move shapes and shape_helpers to lowlevel from perception (cuberite was using this so agent cannot send from perception)
[x]  remove imports from other modules in base_utils

[x] from droidlet.perception.craftassist.shape_helpers import SHAPE_NAMES, SHAPE_HELPERS, bid, SHAPE_FNS, shape_to_dicts

[ ] check droidlet.lowlevel.minecraft.mc_util for duplicate functions

This is now done


Theme "pastel-on-dark" should not specify an absolute font size

In pastel-on-dark.css we have this:
.cm-s-pastel-on-dark.CodeMirror {
	background: #2c2827;
	color: #8F938F;
	line-height: 1.5;
	font-size: 14px;
}

The font size should not be absolute. It should use a relative unit, as in liquibyte.css.

Frankly, probably neither of those themes should specify any kind of font-size. I think a PR to at least remove the size in pastel-on-dark seems sane. Can you make one?

@vincentwoo sure


"E688: More targets than List items" when pressing \rj to jump to definition of a symbol

I press  \rj  to jump to the definition of a c++ symbol and I get:
Error detected while processing function <lambda>6[1]..rtags#HandleResults[11]..rtags#ExecuteHandlers[6]..rtags#JumpToHandler:
line   11:
E688: More targets than List items
line   15:
E121: Undefined variable: jump_file
E116: Invalid arguments for function rtags#jumpToLocation(jump_file, lnum, col)
E15: Invalid expression: rtags#jumpToLocation(jump_file, lnum, col)

It also does not jump to the definition, presumably as a result of the error.
It happens all the time.  I used to be able to run vim-rtag without problems
but I've re-created my setup with the latest version of the tools and now it
no longer works.
I'm using the latest vim-rtag plugin version from git (via Vundle):
commit 054cd8970eda8e222fc5b4c7b88d2a8727d34f25
Author: lyuts<EMAIL_ADDRESS>Date:   Mon Jul 10 21:55:38 2017 -0700

    Set s:rtagsAsync to 0 to not break older version of vim when async is
    not available.

I'm also using using the latest version of rtags from git:
commit 65c8f03ff0112ce5c5e11aff6867ad0eb9019e63
Author: Anders Bakken<EMAIL_ADDRESS>Date:   Sat Jul 15 09:19:36 2017 -0700

    Issue #1004. Support regex (-Z) for --find-symbols.

And the latest version of Vim from git on Linux x86_64 (xubuntu-16.04):
:version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jul 17 2017 18:00:30)
Included patches: 1-727
Compiled by dope@pel-desktop
Huge version with GTK3 GUI.

E688: More targets than List items
Looks like a plugin error. You usually get this for something like this: :let [a, b, c] = [1, 2], so I would go ahead and create an issue at the plugin issue tracker for that.

Looks like a plugin error.

Ah sorry, I thought I opened this ticket in the git repo of the vim-rtag plugin, but I did it in the vim github repo by mistake.  I'll open it in https://github.com/lyuts/vim-rtags  instead.
Closing this one.


[TypeError] distributions() got an unexpected keyword argument 'path'

[x] I am on the latest Poetry version (poetry 1.0.0b9)
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] I executed the failing command in debug mode (-vvv option).

Version information:

CentOS Linux release 7.6.1810 (running in a virtual machine)
Python 3.6.5
Poetry 1.0.0b9
project.toml

Issue
Hi, I am just trying out Poetry, and I think I have found a bug in Python version compatibility layer:
$  poetry install -vvv

Using virtualenv: /home/vagrant/secret

[TypeError]
distributions() got an unexpected keyword argument 'path'

Traceback (most recent call last):
  File "/home/vagrant/secret/lib64/python3.6/site-packages/clikit/console_application.py", line 131, in run
    status_code = command.handle(parsed_args, io)
  File "/home/vagrant/secret/lib64/python3.6/site-packages/clikit/api/command/command.py", line 120, in handle
    status_code = self._do_handle(args, io)
  File "/home/vagrant/secret/lib64/python3.6/site-packages/clikit/api/command/command.py", line 171, in _do_handle
    return getattr(handler, handler_method)(args, io, self)
  File "/home/vagrant/secret/lib64/python3.6/site-packages/cleo/commands/command.py", line 92, in wrap_handle
    return self.handle()
  File "/home/vagrant/secret/lib64/python3.6/site-packages/poetry/console/commands/install.py", line 48, in handle
    self.io, self.env, self.poetry.package, self.poetry.locker, self.poetry.pool
  File "/home/vagrant/secret/lib64/python3.6/site-packages/poetry/installation/installer.py", line 55, in __init__
    installed = self._get_installed()
  File "/home/vagrant/secret/lib64/python3.6/site-packages/poetry/installation/installer.py", line 488, in _get_installed
    return InstalledRepository.load(self._env)
  File "/home/vagrant/secret/lib64/python3.6/site-packages/poetry/repositories/installed_repository.py", line 20, in load
    metadata.distributions(path=env.sys_path), key=lambda d: str(d._path),

Under inspection, inspect_metadata.metadata.distributions indeed does not have the path kwarg:
$ python
Python 3.6.5 (default, Apr 10 2018, 17:08:37)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import importlib_metadata as metadata
>>> import inspect
>>> print(inspect.getsource(metadata.distributions))
def distributions():
    """Get all ``Distribution`` instances in the current environment.

    :return: An iterable of ``Distribution`` instances.
    """
    return Distribution.discover()

Sorry, I did not realize that import-metadata is a third-party package. For some reason I had import-metadata==0.20. Technically it satisfies the requirements, but does not work, as you can see. Running poetry update import-metadata installed import-metadata==1.2.0 and fixed the issue.