fix(lint): apply ruff format

Description:
This pull request includes several changes to the confluent_kafka-stubs package, primarily focusing on adding future annotations and minor formatting adjustments.
Formatting Adjustments:

Cleaned up indentation & added from __future__ import annotations to multiple files to enable postponed evaluation of type annotations. This change improves forward compatibility and type hinting performance. (confluent_kafka-stubs/__init__.pyi, confluent_kafka-stubs/_model/__init__.pyi, confluent_kafka-stubs/_util/__init__.pyi, confluent_kafka-stubs/_util/conversion_util.pyi, confluent_kafka-stubs/_util/validation_util.pyi, confluent_kafka-stubs/admin/__init__.pyi, confluent_kafka-stubs/admin/_acl.pyi, confluent_kafka-stubs/admin/_group.pyi, confluent_kafka-stubs/admin/_metadata.pyi, confluent_kafka-stubs/admin/_resource.pyi, confluent_kafka-stubs/admin/_scram.pyi, confluent_kafka-stubs/avro/cached_schema_registry_client.pyi, confluent_kafka-stubs/avro/error.pyi, confluent_kafka-stubs/avro/load.pyi, confluent_kafka-stubs/avro/serializer/__init__.pyi, confluent_kafka-stubs/avro/serializer/message_serializer.pyi, confluent_kafka-stubs/cimpl.pyi, confluent_kafka-stubs/deserializing_consumer.pyi) [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18]

Added trailing commas to the AvroProducer and AvroConsumer class constructors to improve code readability and maintainability. (confluent_kafka-stubs/avro/__init__.pyi) [1] [2]

Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] All code follows the project's coding style and conventions.
[x] I have performed a self-review of my own code.
[x] My changes generate no new warnings or errors.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding updates to the documentation.

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use default resolution for viewport_debug example

Objective
The viewport_debug example opens a window that is physically very large. Probably larger than the screen for the majority of machines.
Solution
Remove the custom resolution and adjust the pixel coordinates so that everything lines up.
At the default resolution, everything is still whole numbers even without adjusting the viewport coordinates.

Ping @ickshonpe

Ah I was super confused for a moment, forgot that I even wrote this thing. The changes look fine, though we should probably scrap this eventually and have a proper example that explains the different Val variants in detail etc.

I guess though there could be a problem with this if the default resolution is changed in the future?

we should probably scrap this eventually and have a proper example that explains the different Val variants in detail etc.

Agreed.

I guess though there could be a problem with this if the default resolution is changed in the future?

I suppose we could explicitly define the resolution. It's not really much of a concern but


[workloadmeta/dump] Scrub sensitive data

What does this PR do?
Scrubs sensitive data from the output of the workload-list command.
Motivation
The output can contain sensitive information. For example, if the api key is passed as an ENV to the agent container, because envs appear in the output of workload-list --verbose.
Describe how to test/QA your changes
Run the agent with docker/containerd passing the api key as an ENV. Run agent workload-list --verbose and check that in the Env variables section of the agent container, the api key has been cleaned-up with *s.
Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[x] The appropriate team/.. label has been applied, if known.
[x] A release note
has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[x] If applicable, docs team has been notified or
an issue has been opened on the documentation repo.
[x] If applicable, the need-change/operator and need-change/helm labels have been applied.
[x] If applicable, the config template
has been updated.

I wasn't aware about that general rule. Let's keep as it is then, for consistency.


add page margin, page orientation, paper size options

update code for php-cs-fixer

added unit test

update code for php-cs-fixer and infection

updated to use enum and dedicated class for PageMargin.
by the way, any idea why running this command locally:
git fetch origin --no-tags --prune --depth=1 4.x 3f0c3dbbfe2db2f6215eafddd9614b693ba1046b
make code-coverage INFECTION_ARGS='--logger-github'

outputs:
0 mutations were generated:
       0 mutants were killed
       0 mutants were configured to be ignored
       0 mutants were not covered by tests
       0 covered mutants were not detected
       0 errors were encountered
       0 syntax errors were encountered
       0 time outs were encountered
       0 mutants required more time than configured

Metrics:
         Mutation Score Indicator (MSI): 0%
         Mutation Code Coverage: 0%
         Covered Code MSI: 0%

update code for infection MSI

@cresjie whenever you push a commit I get notified, no need to comment every commit to ping me 😉


[BUG] seccomp_init() failed

General information

OS: Linux / macOS / Windows
Fedora 37

Hypervisor: KVM / Hyper-V / hyperkit / vfkit
KVM

Did you run crc setup before starting it (Yes/No)?
Yes

Running CRC on: Laptop / Baremetal-Server / VM
Baremetal

CRC version
# Put `crc version` output here
$ crc version
CRC version: 2.15.0+cc05160
OpenShift version: 4.12.5
Podman version: 4.3.1

CRC status
# Put `crc status --log-level debug` output here
crc status --log-level debug
DEBU CRC version: 2.15.0+cc05160
DEBU OpenShift version: 4.12.5
DEBU Podman version: 4.3.1
DEBU Running 'crc status'
CRC VM:          Stopped
OpenShift:       Stopped (v4.12.0-0.okd-2023-02-18-033438)
RAM Usage:       0B of 0B
Disk Usage:      0B of 0B (Inside the CRC VM)
Cache Usage:     32.48GB
Cache Directory: /home/jj/.crc/cache

CRC config
# Put `crc config view` output here
crc config view
- consent-telemetry                     : no
- preset                                : okd

Host Operating System
# Put the output of `cat /etc/os-release` in case of Linux
# put the output of `sw_vers` in case of Mac
# Put the output of `systeminfo` in case of Windows

cat /etc/os-release
NAME="Fedora Linux"
VERSION="37 (Workstation Edition)"
ID=fedora
VERSION_ID=37
VERSION_CODENAME=""
PLATFORM_ID="platform:f37"
PRETTY_NAME="Fedora Linux 37 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:37"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f37/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=37
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=37
SUPPORT_END=2023-11-14
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Steps to reproduce

crc delete
crc setup
crc start

Expected
A running okd instance -
Actual
An error install
Logs
# tail -f crc.log
-device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \
-audiodev '{"id":"audio1","driver":"none"}' \
-vnc <IP_ADDRESS>:0,audiodev=audio1 \
-device '{"driver":"cirrus-vga","id":"video0","bus":"pcie.0","addr":"0x1"}' \
-object '{"qom-type":"rng-random","id":"objrng0","filename":"/dev/urandom"}' \
-device '{"driver":"virtio-rng-pci","rng":"objrng0","id":"rng0","bus":"pci.5","addr":"0x0"}' \
-msg timestamp=on
2023-04-04T14:08:33.267526Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: Failed to write msg. Wrote -1 instead of 12.
2023-04-04T14:08:33.267547Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: vhost_backend_init failed: Protocol error
2023-04-04 14:08:33.333+0000: shutting down, reason=failed
---
[root@darkstar qemu]# tail -f crc-fs0-virtiofsd.log
seccomp_init() failed
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
seccomp_init() failed
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
seccomp_init() failed
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
seccomp_init() failed

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.

can you post the output of $ crc setup --log-level debug to understand which step is actually failing?

$crc setup
INFO Using bundle path /home/jj/.crc/cache/crc_okd_libvirt_4.12.0-0.okd-2023-02-18-033438_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 minimum RAM requirements
INFO Checking if crc executable symlink exists
INFO Creating symlink for crc executable
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
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Checking crc daemon systemd service
INFO Checking crc daemon systemd socket units
INFO Checking if systemd-networkd is running
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if dnsmasq configurations file exist for NetworkManager
INFO Checking if the systemd-resolved service is running
INFO Checking if /etc/NetworkManager/dispatcher.d/99-crc.sh exists
INFO Checking if libvirt 'crc' network is available
INFO Checking if libvirt 'crc' network is active
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if /home/jj/.crc/cache/crc_okd_libvirt_4.12.0-0.okd-2023-02-18-033438_amd64.crcbundle exists
Your system is correctly setup for using CRC. Use 'crc start' to start the instance
``
then,

crc start
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 minimum RAM requirements
INFO Checking if crc executable symlink exists
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
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Checking crc daemon systemd socket units
INFO Checking if systemd-networkd is running
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if dnsmasq configurations file exist for NetworkManager
INFO Checking if the systemd-resolved service is running
INFO Checking if /etc/NetworkManager/dispatcher.d/99-crc.sh exists
INFO Checking if libvirt 'crc' network is available
INFO Checking if libvirt 'crc' network is active
INFO Loading bundle: crc_okd_libvirt_4.12.0-0.okd-2023-02-18-033438_amd64...
INFO Creating CRC VM for okd 4.12.0-0.okd-2023-02-18-033438...
INFO Generating new SSH key pair...
INFO Generating new password for the kubeadmin user
INFO Starting CRC VM for okd 4.12.0-0.okd-2023-02-18-033438...
Error starting machine: Error in driver during machine start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T14:31:29.380340Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: Failed to write msg. Wrote -1 instead of 12.
2023-04-04T14:31:29.380365Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: vhost_backend_init failed: Protocol error')

crc start  --log-level debug
DEBU CRC version: 2.15.0+cc05160
DEBU OpenShift version: 4.12.5
DEBU Podman version: 4.3.1
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>4 bytes
DEBU No new version available. The latest version is 2.15.0
DEBU Checking file: /home/jj/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/jj/.crc/bin/crc-driver-libvirt
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:39589
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="2023-04-04T17:12:07+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2023-04-04T17:12:07+02:00" level=debug msg="Fetching VM..."
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="2023-04-04T17:12:07+02:00" level=debug msg="Closing plugin on server side"
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/jj/.crc/bin/crc-admin-helper-linux --version'
DEBU Found crc-admin-helper-linux version 0.0.12
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 minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>4 bytes
INFO Checking if crc executable symlink exists
INFO Checking if Virtualization is enabled
DEBU Checking if the vmx/svm flags are present in /proc/cpuinfo
DEBU CPU virtualization flags are good
INFO Checking if KVM is enabled
DEBU Checking if /dev/kvm exists
DEBU /dev/kvm was found
INFO Checking if libvirt is installed
DEBU Checking if 'virsh' is available
DEBU 'virsh' was found in /usr/bin/virsh
DEBU Checking 'virsh capabilities' for libvirtd/qemu availability
DEBU Running 'virsh --readonly --connect qemu:///system capabilities'

DEBU Found x86_64 hypervisor with 'hvm' capabilities
INFO Checking if user is part of libvirt group
DEBU Checking if current user is part of the libvirt group
DEBU Current user is already in the libvirt group
INFO Checking if active user/process is currently part of the libvirt group
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd service is running
DEBU Running 'systemctl status virtqemud.socket'
DEBU virtqemud.socket is running
INFO Checking if a supported libvirt version is installed
DEBU Checking if libvirt version is >=3.4.0
DEBU Running 'virsh -v'
INFO Checking if crc-driver-libvirt is installed
DEBU Checking if crc-driver-libvirt is installed
DEBU Running '/home/jj/.crc/bin/crc-driver-libvirt version'
DEBU Found crc-driver-libvirt version 0.13.5
DEBU crc-driver-libvirt 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 listening
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 listening
DEBU Checking if crc-vsock.socket has the expected content
INFO Checking if systemd-networkd is running
DEBU Checking if systemd-networkd.service is running
DEBU Running 'systemctl status systemd-networkd.service'
DEBU Command failed: exit status 3
DEBU stdout: * systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; disabled; preset: disabled)
     Active: inactive (dead)
TriggeredBy: * systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
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 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/jj/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_okd_libvirt_4.12.0-0.okd-2023-02-18-033438_amd64...
DEBU Checking file: /home/jj/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/jj/.crc/bin/crc-driver-libvirt
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:44399
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="2023-04-04T17:12:15+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=debug msg="Fetching VM..."
INFO Starting CRC VM for okd 4.12.0-0.okd-2023-02-18-033438...
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=warning msg="Failed to start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T15:12:15.085467Z qemu-system-x86_64: -device {\"driver\":\"vhost-user-fs-pci\",\"id\":\"fs0\",\"chardev\":\"chr-vu-fs0\",\"tag\":\"dir0\",\"bus\":\"pci.1\",\"addr\":\"0x0\"}: Failed to write msg. Wrote -1 instead of 12.\n2023-04-04T15:12:15.085488Z qemu-system-x86_64: -device {\"driver\":\"vhost-user-fs-pci\",\"id\":\"fs0\",\"chardev\":\"chr-vu-fs0\",\"tag\":\"dir0\",\"bus\":\"pci.1\",\"addr\":\"0x0\"}: vhost_backend_init failed: Protocol error')"
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="2023-04-04T17:12:15+02:00" level=debug msg="Closing plugin on server side"
Error starting machine: Error in driver during machine start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T15:12:15.085467Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: Failed to write msg. Wrote -1 instead of 12.
2023-04-04T15:12:15.085488Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: vhost_backend_init failed: Protocol error')

preset                                : okd

We do not provide support for the OKD bundle. Issues using this preset have to be filed at: https://github.com/okd-project/okd/issues
If you can try to run the openshift preset and see if you also experience these issues, we might be able to help you.

@jsliacan Can you try to run on a fully updated Fedora 37 machine, without any additional installs, and see if you get the same results? Note: I have not seen them on my system(s). @praveenkumar @cfergeau WDYT?

@praveenkumar. This starts virtiofsd, but something in the protocol fails; seccomp initialization does not pass.
Error starting machine: Error in driver during machine start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T15:12:15.085467Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: Failed to write msg. Wrote -1 instead of 12.
2023-04-04T15:12:15.085488Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: vhost_backend_init failed: Protocol error')

@eskuai are you running with a non-standard kernel? selinux enabled? Anything else installed on the machine that might have changed sysctl, kernel or other parameters?

I think that podman was before ... or no message ...
I'll try to reset all, restart again ...
maybe:
INFO Downloading bundle: /home/jsanz/.crc/cache/crc_libvirt_4.12.5_amd64.crcbundle...

a) Non standard kernel ? ... yes ...
b) TO-DO:  Check using fedora kernel
c) selinux is disabled ...

Non standard kernel ? ... yes ...

Unsupported in that case. We only test and provide support for the distribution provided kernels.
It is stil interesting to understand what you have done, but I am sure we can not do much for you.

Right,
INFO Checking if dnsmasq configurations file exist for NetworkManager
INFO Checking if the systemd-resolved service is running
INFO Checking if /etc/NetworkManager/dispatcher.d/99-crc.sh exists
INFO Checking if libvirt 'crc' network is available
INFO Checking if libvirt 'crc' network is active
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if /home/jj/.crc/cache/crc_libvirt_4.12.5_amd64.crcbundle exists
INFO Getting bundle for the CRC executable
INFO Downloading bundle: /home/jj/.crc/cache/crc_libvirt_4.12.5_amd64.crcbundle...
2.98 GiB / 2.98 GiB [-----------------------------------------------------------------------------------------------------------------------------------------] 100.00% 27.26 MiB p/s
INFO Uncompressing /home/jj/.crc/cache/crc_libvirt_4.12.5_amd64.crcbundle
crc.qcow2:  11.82 GiB / 11.82 GiB [-----------------------------------------------------------------------------------------------------------------------------------------] 100.00%
oc:  124.65 MiB / 124.65 MiB [----------------------------------------------------------------------------------------------------------------------------------------------] 100.00%
Your system is correctly setup for using CRC. Use 'crc start' to start the instance

And now
 crc config view
- consent-telemetry                     : yes

[jj@darkstar ~]$ crc start  --log-level debug
DEBU CRC version: 2.15.0+cc05160
DEBU OpenShift version: 4.12.5
DEBU Podman version: 4.3.1
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>4 bytes
DEBU No new version available. The latest version is 2.15.0
DEBU Checking file: /home/jj/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/jj/.crc/bin/crc-driver-libvirt
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:39589
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="2023-04-04T17:12:07+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2023-04-04T17:12:07+02:00" level=debug msg="Fetching VM..."
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="2023-04-04T17:12:07+02:00" level=debug msg="Closing plugin on server side"
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/jj/.crc/bin/crc-admin-helper-linux --version'
DEBU Found crc-admin-helper-linux version 0.0.12
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 minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>4 bytes
INFO Checking if crc executable symlink exists
INFO Checking if Virtualization is enabled
DEBU Checking if the vmx/svm flags are present in /proc/cpuinfo
DEBU CPU virtualization flags are good
INFO Checking if KVM is enabled
DEBU Checking if /dev/kvm exists
DEBU /dev/kvm was found
INFO Checking if libvirt is installed
DEBU Checking if 'virsh' is available
DEBU 'virsh' was found in /usr/bin/virsh
DEBU Checking 'virsh capabilities' for libvirtd/qemu availability
DEBU Running 'virsh --readonly --connect qemu:///system capabilities'

DEBU Found x86_64 hypervisor with 'hvm' capabilities
INFO Checking if user is part of libvirt group
DEBU Checking if current user is part of the libvirt group
DEBU Current user is already in the libvirt group
INFO Checking if active user/process is currently part of the libvirt group
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd service is running
DEBU Running 'systemctl status virtqemud.socket'
DEBU virtqemud.socket is running
INFO Checking if a supported libvirt version is installed
DEBU Checking if libvirt version is >=3.4.0
DEBU Running 'virsh -v'
INFO Checking if crc-driver-libvirt is installed
DEBU Checking if crc-driver-libvirt is installed
DEBU Running '/home/jj/.crc/bin/crc-driver-libvirt version'
DEBU Found crc-driver-libvirt version 0.13.5
DEBU crc-driver-libvirt 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 listening
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 listening
DEBU Checking if crc-vsock.socket has the expected content
INFO Checking if systemd-networkd is running
DEBU Checking if systemd-networkd.service is running
DEBU Running 'systemctl status systemd-networkd.service'
DEBU Command failed: exit status 3
DEBU stdout: * systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; disabled; preset: disabled)
     Active: inactive (dead)
TriggeredBy: * systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
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 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/jj/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_okd_libvirt_4.12.0-0.okd-2023-02-18-033438_amd64...
DEBU Checking file: /home/jj/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/jj/.crc/bin/crc-driver-libvirt
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:44399
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="2023-04-04T17:12:15+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=debug msg="Fetching VM..."
INFO Starting CRC VM for okd 4.12.0-0.okd-2023-02-18-033438...
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2023-04-04T17:12:15+02:00" level=warning msg="Failed to start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T15:12:15.085467Z qemu-system-x86_64: -device {\"driver\":\"vhost-user-fs-pci\",\"id\":\"fs0\",\"chardev\":\"chr-vu-fs0\",\"tag\":\"dir0\",\"bus\":\"pci.1\",\"addr\":\"0x0\"}: Failed to write msg. Wrote -1 instead of 12.\n2023-04-04T15:12:15.085488Z qemu-system-x86_64: -device {\"driver\":\"vhost-user-fs-pci\",\"id\":\"fs0\",\"chardev\":\"chr-vu-fs0\",\"tag\":\"dir0\",\"bus\":\"pci.1\",\"addr\":\"0x0\"}: vhost_backend_init failed: Protocol error')"
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="2023-04-04T17:12:15+02:00" level=debug msg="Closing plugin on server side"
Error starting machine: Error in driver during machine start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T15:12:15.085467Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: Failed to write msg. Wrote -1 instead of 12.
2023-04-04T15:12:15.085488Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: vhost_backend_init failed: Protocol error')
[jj@darkstar ~]$
[jj@darkstar ~]$
[jj@darkstar ~]$
[jj@darkstar ~]$
[jj@darkstar ~]$ crc stop
Instance is already stopped
[jj@darkstar ~]$ crc delete
Do you want to delete the instance? [y/N]: y
Deleted the instance
[jj@darkstar ~]$ crc config view
- consent-telemetry                     : no
- preset                                : okd
[jj@darkstar ~]$ crc config preset ''
Modifies crc configuration properties.
Properties:

* bundle                                     Bundle path/URI - absolute or local path, http, https or docker URI (string, like 'https://foo.com/crc_okd_libvirt_4.12.0-0.okd-2023-02-18-033438_amd64.crcbundle', 'docker://quay.io/myorg/crc_okd_libvirt_4.12.0-0.okd-2023-02-18-033438_amd64.crcbundle:2.15.0' default '/home/jj/.crc/cache/crc_okd_libvirt_4.12.0-0.okd-2023-02-18-033438_amd64.crcbundle' )
* consent-telemetry                          Consent to collection of anonymous usage data (yes/no)
* cpus                                       Number of CPU cores (must be greater than or equal to '4')
* disable-update-check                       Disable update check (true/false, default: false)
* disk-size                                  Total size in GiB of the disk (must be greater than or equal to '31')
* enable-cluster-monitoring                  Enable cluster monitoring Operator (true/false, default: false)
* enable-experimental-features               Enable experimental features (true/false, default: false)
* enable-shared-dirs                         Mounts host's home directory at '/' in the CRC VM (true/false, default: true)
* host-network-access                        Allow TCP/IP connections from the CRC VM to services running on the host (true/false, default: false)
* http-proxy                                 HTTP proxy URL (string, like 'http://my-proxy.com:8443')
* https-proxy                                HTTPS proxy URL (string, like 'https://my-proxy.com:8443')
* ingress-http-port                          HTTP port to use for OpenShift ingress/routes on the host (1024-65535, default: 80)
* ingress-https-port                         HTTPS port to use for OpenShift ingress/routes on the host (1024-65535, default: 443)
* kubeadmin-password                         User defined kubeadmin password
* memory                                     Memory size in MiB (must be greater than or equal to '9216')
* nameserver                                 IPv4 address of nameserver (string, like '<IP_ADDRESS> or <IP_ADDRESS>')
* network-mode                               Network mode (user or system)
* no-proxy                                   Hosts, ipv4 addresses or CIDR which do not use a proxy (string, comma-separated list such as '<IP_ADDRESS>,<IP_ADDRESS>/24')
* preset                                     Virtual machine preset (valid values are: podman, openshift and okd)
* proxy-ca-file                              Path to an HTTPS proxy certificate authority (CA)
* pull-secret-file                           Path of image pull secret (download from https://console.redhat.com/openshift/create/local)
* skip-check-admin-helper-cached             Skip preflight check (true/false, default: false)
* skip-check-bundle-extracted                Skip preflight check (true/false, default: false)
* skip-check-crc-network                     Skip preflight check (true/false, default: false)
* skip-check-crc-network-active              Skip preflight check (true/false, default: false)
* skip-check-crc-symlink                     Skip preflight check (true/false, default: false)
* skip-check-daemon-systemd-sockets          Skip preflight check (true/false, default: false)
* skip-check-daemon-systemd-unit             Skip preflight check (true/false, default: false)
* skip-check-dnsmasq-network-manager-config  Skip preflight check (true/false, default: false)
* skip-check-kvm-enabled                     Skip preflight check (true/false, default: false)
* skip-check-libvirt-driver                  Skip preflight check (true/false, default: false)
* skip-check-libvirt-group-active            Skip preflight check (true/false, default: false)
* skip-check-libvirt-installed               Skip preflight check (true/false, default: false)
* skip-check-libvirt-running                 Skip preflight check (true/false, default: false)
* skip-check-libvirt-version                 Skip preflight check (true/false, default: false)
* skip-check-network-manager-dispatcher-file Skip preflight check (true/false, default: false)
* skip-check-network-manager-installed       Skip preflight check (true/false, default: false)
* skip-check-network-manager-running         Skip preflight check (true/false, default: false)
* skip-check-ram                             Skip preflight check (true/false, default: false)
* skip-check-root-user                       Skip preflight check (true/false, default: false)
* skip-check-supported-cpu-arch              Skip preflight check (true/false, default: false)
* skip-check-systemd-networkd-running        Skip preflight check (true/false, default: false)
* skip-check-systemd-resolved-running        Skip preflight check (true/false, default: false)
* skip-check-user-in-libvirt-group           Skip preflight check (true/false, default: false)
* skip-check-virt-enabled                    Skip preflight check (true/false, default: false)
* skip-check-vsock                           Skip preflight check (true/false, default: false)
* skip-check-wsl2                            Skip preflight check (true/false, default: false)

Usage:
  crc config SUBCOMMAND [flags]
  crc config [command]

Available Commands:
  get         Get a crc configuration property
  set         Set a crc configuration property
  unset       Unset a crc configuration property
  view        Display all assigned crc configuration properties

Flags:
  -h, --help   help for config

Global Flags:
      --log-level string   log level (e.g. "debug | info | warn | error") (default "info")

Use "crc config [command] --help" for more information about a command.
[jj@darkstar ~]$ crc config view
- consent-telemetry                     : no
- preset                                : okd
[jj@darkstar ~]$ crc config set preset podman
Changes to configuration property 'preset' are only applied when the CRC instance is created.
If you already have a running CRC instance with different preset, then for this configuration change to take effect, delete the CRC instance with 'crc delete', setup it with `crc setup` and start it with 'crc start'.
[jj@darkstar ~]$ crc config view
- consent-telemetry                     : no
- preset                                : podman
[jj@darkstar ~]$ crc start  --log-level debug
DEBU CRC version: 2.15.0+cc05160
DEBU OpenShift version: 4.12.5
DEBU Podman version: 4.3.1
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>4 bytes
DEBU Got bundle path: /home/jj/.crc/cache/crc_podman_libvirt_4.3.1_amd64.crcbundle
file '/home/jj/.crc/cache/crc_podman_libvirt_4.3.1_amd64.crcbundle' does not exist
[jj@darkstar ~]$ crc start
file '/home/jj/.crc/cache/crc_podman_libvirt_4.3.1_amd64.crcbundle' does not exist
[jj@darkstar ~]$ crc config view
- consent-telemetry                     : no
- preset                                : podman
[jj@darkstar ~]$ crc start
file '/home/jj/.crc/cache/crc_podman_libvirt_4.3.1_amd64.crcbundle' does not exist
[jj@darkstar ~]$ rm -rf .crc
[jj@darkstar ~]$ crc setup
CRC is constantly improving and we would like to know more about usage (more details at https://developers.redhat.com/article/tool-data-collection)
Your preference can be changed manually if desired using 'crc config set consent-telemetry <yes/no>'
Would you like to contribute anonymous usage statistics? [y/N]: y
Thanks for helping us! You can disable telemetry with the command 'crc config set consent-telemetry no'.
INFO Using bundle path /home/jj/.crc/cache/crc_libvirt_4.12.5_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 Caching crc-admin-helper executable
INFO Using root access: Changing ownership of /home/jj/.crc/bin/crc-admin-helper-linux
INFO Using root access: Setting suid for /home/jj/.crc/bin/crc-admin-helper-linux
INFO Checking if running on a supported CPU architecture
INFO Checking minimum RAM requirements
INFO Checking if crc executable symlink exists
INFO Creating symlink for crc executable
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
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Installing crc-driver-libvirt
INFO Checking crc daemon systemd service
INFO Checking crc daemon systemd socket units
INFO Checking if systemd-networkd is running
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if dnsmasq configurations file exist for NetworkManager
INFO Checking if the systemd-resolved service is running
INFO Checking if /etc/NetworkManager/dispatcher.d/99-crc.sh exists
INFO Checking if libvirt 'crc' network is available
INFO Checking if libvirt 'crc' network is active
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if /home/jj/.crc/cache/crc_libvirt_4.12.5_amd64.crcbundle exists
INFO Getting bundle for the CRC executable
INFO Downloading bundle: /home/jj/.crc/cache/crc_libvirt_4.12.5_amd64.crcbundle...
2.98 GiB / 2.98 GiB [-----------------------------------------------------------------------------------------------------------------------------------------] 100.00% 27.26 MiB p/s
INFO Uncompressing /home/jj/.crc/cache/crc_libvirt_4.12.5_amd64.crcbundle
crc.qcow2:  11.82 GiB / 11.82 GiB [-----------------------------------------------------------------------------------------------------------------------------------------] 100.00%
oc:  124.65 MiB / 124.65 MiB [----------------------------------------------------------------------------------------------------------------------------------------------] 100.00%
Your system is correctly setup for using CRC. Use 'crc start' to start the instance
[jj@darkstar ~]$ crc config view
- consent-telemetry                     : yes
[jj@darkstar ~]$
[jj@darkstar ~]$
[jj@darkstar ~]$ crc start  --log-level debug
DEBU CRC version: 2.15.0+cc05160
DEBU OpenShift version: 4.12.5
DEBU Podman version: 4.3.1
DEBU Running 'crc start'
DEBU Total memory of system is<PHONE_NUMBER>4 bytes
DEBU No new version available. The latest version is 2.15.0
DEBU Checking file: /home/jj/.crc/machines/crc/.crc-exist
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/jj/.crc/bin/crc-admin-helper-linux --version'
DEBU Found crc-admin-helper-linux version 0.0.12
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 minimum RAM requirements
DEBU Total memory of system is<PHONE_NUMBER>4 bytes
INFO Checking if crc executable symlink exists
INFO Checking if Virtualization is enabled
DEBU Checking if the vmx/svm flags are present in /proc/cpuinfo
DEBU CPU virtualization flags are good
INFO Checking if KVM is enabled
DEBU Checking if /dev/kvm exists
DEBU /dev/kvm was found
INFO Checking if libvirt is installed
DEBU Checking if 'virsh' is available
DEBU 'virsh' was found in /usr/bin/virsh
DEBU Checking 'virsh capabilities' for libvirtd/qemu availability
DEBU Running 'virsh --readonly --connect qemu:///system capabilities'
DEBU Found x86_64 hypervisor with 'hvm' capabilities
INFO Checking if user is part of libvirt group
DEBU Checking if current user is part of the libvirt group
DEBU Current user is already in the libvirt group
INFO Checking if active user/process is currently part of the libvirt group
INFO Checking if libvirt daemon is running
DEBU Checking if libvirtd service is running
DEBU Running 'systemctl status virtqemud.socket'
DEBU virtqemud.socket is running
INFO Checking if a supported libvirt version is installed
DEBU Checking if libvirt version is >=3.4.0
DEBU Running 'virsh -v'
INFO Checking if crc-driver-libvirt is installed
DEBU Checking if crc-driver-libvirt is installed
DEBU Running '/home/jj/.crc/bin/crc-driver-libvirt version'
DEBU Found crc-driver-libvirt version 0.13.5
DEBU crc-driver-libvirt 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 listening
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 listening
DEBU Checking if crc-vsock.socket has the expected content
INFO Checking if systemd-networkd is running
DEBU Checking if systemd-networkd.service is running
DEBU Running 'systemctl status systemd-networkd.service'
DEBU Command failed: exit status 3
DEBU stdout: * systemd-networkd.service - Network Configuration
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; disabled; preset: disabled)
     Active: inactive (dead)
TriggeredBy: * systemd-networkd.socket
       Docs: man:systemd-networkd.service(8)
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 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/jj/.crc/machines/crc/.crc-exist
INFO Loading bundle: crc_libvirt_4.12.5_amd64...
DEBU Cannot load secret from configuration: empty path
DEBU Using secret from keyring
INFO Creating CRC VM for openshift 4.12.5...
DEBU Found binary path at /home/jj/.crc/bin/crc-driver-libvirt
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:46067
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="2023-04-04T17:31:15+02:00" level=debug msg="About to check libvirt version"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Activating pool 'crc'"
DEBU (crc) Calling .GetConfigRaw
DEBU Creating machine...
DEBU (crc) Calling .Create
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Preparing /home/jj/.crc/machines/crc/crc.qcow2 for machine use"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="image creation took 6.663459ms"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Verifying executable bit set on /home/jj/.crc/machines/crc"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Verifying executable bit set on /home/jj/.crc/machines"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Verifying executable bit set on /home/jj/.crc"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Setting executable bit set on /home/jj/.crc"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Verifying executable bit set on /home/jj"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Verifying executable bit set on /home"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Defining VM..."
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Found q35 machine type"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Found x86_64 hypervisor with 'hvm' capabilities"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Found q35 machine type"
DEBU (crc) DBG | time="2023-04-04T17:31:15+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/jj/.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="2023-04-04T17:31:15+02:00" level=debug msg="Closing plugin on server side"
DEBU Checking file: /home/jj/.crc/machines/crc/.crc-exist
DEBU Found binary path at /home/jj/.crc/bin/crc-driver-libvirt
DEBU Launching plugin server for driver libvirt
DEBU Plugin server listening at address <IP_ADDRESS>:44839
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="2023-04-04T17:31:15+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Fetching VM..."
INFO Starting CRC VM for openshift 4.12.5...
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=warning msg="Failed to start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T15:31:15.272360Z qemu-system-x86_64: -device {\"driver\":\"vhost-user-fs-pci\",\"id\":\"fs0\",\"chardev\":\"chr-vu-fs0\",\"tag\":\"dir0\",\"bus\":\"pci.1\",\"addr\":\"0x0\"}: Failed to write msg. Wrote -1 instead of 12.\n2023-04-04T15:31:15.272381Z qemu-system-x86_64: -device {\"driver\":\"vhost-user-fs-pci\",\"id\":\"fs0\",\"chardev\":\"chr-vu-fs0\",\"tag\":\"dir0\",\"bus\":\"pci.1\",\"addr\":\"0x0\"}: vhost_backend_init failed: Protocol error')"
DEBU Making call to close driver server
DEBU (crc) Calling .Close
DEBU (crc) DBG | time="2023-04-04T17:31:15+02:00" level=debug msg="Closing plugin on server side"
DEBU Successfully made call to close driver server
DEBU Making call to close connection to plugin binary
Error starting machine: Error in driver during machine start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T15:31:15.272360Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: Failed to write msg. Wrote -1 instead of 12.
2023-04-04T15:31:15.272381Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"dir0","bus":"pci.1","addr":"0x0"}: vhost_backend_init failed: Protocol error')
[jj@darkstar ~]$

Which kernel do you run? With standard parameters?

$ rpm -qa | grep kernel
kernel-6.1.14-200.fc37.x86_64

$ cat /etc/default/grub
GRUB_CMDLINE_LINUX="resume=/dev/mapper/system-swap00 rd.lvm.lv=system/root00 rd.lvm.lv=system/swap00 rhgb quiet"

$ uname -na
Linux ncentre 6.1.14-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Feb 26 00:13:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

This is what I would expect as a standard distro provided kernel. If you compile your own kernel, we can not provide support for this.

rpm -qa | grep kernel
kernel-srpm-macros-1.0-15.fc37.noarch
libreport-plugin-kerneloops-2.17.4-1.fc37.x86_64
abrt-addon-kerneloops-2.15.1-6.fc37.x86_64
kernel-core-6.1.18-200.fc37.x86_64
kernel-modules-6.1.18-200.fc37.x86_64
kernel-6.1.18-200.fc37.x86_64
kernel-modules-extra-6.1.18-200.fc37.x86_64
kernel-devel-6.1.18-200.fc37.x86_64
kernel-modules-core-6.2.7-200.fc37.x86_64
kernel-core-6.2.7-200.fc37.x86_64
kernel-modules-6.2.7-200.fc37.x86_64
kernel-tools-libs-6.2.6-200.fc37.x86_64
kernel-tools-6.2.6-200.fc37.x86_64
kernel-6.2.7-200.fc37.x86_64
kernel-modules-extra-6.2.7-200.fc37.x86_64
kernel-headers-6.2.6-200.fc37.x86_64
kernel-devel-6.2.7-200.fc37.x86_64
kernel-modules-core-6.2.8-200.fc37.x86_64
kernel-core-6.2.8-200.fc37.x86_64
kernel-modules-6.2.8-200.fc37.x86_64
kernel-6.2.8-200.fc37.x86_64
kernel-modules-extra-6.2.8-200.fc37.x86_64
kernel-devel-6.2.8-200.fc37.x86_64

<..>
cat /etc/default/grub
GRUB_TIMEOUT=8
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="resume=UUID=79079bd3-81dd-4163-a14d-e9c122075a87 rhgb quiet delayacct nohugeiomap udev.log_priority=3 audit=0 transparent_hugepage=never systemd.unified_cgroup_hierarchy=1 cgroup_no_v1=all selinux=0 mitigations=off retbleed=off amd_pstate.shared_mem=1 nowatchdog  rd.driver.pre=vfio-pci iommu=pt "
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true
GRUB_HIDDEN_TIMEOUT_QUIET=false

<..>
uname -na
Linux darkstar 6.2.9 #7 SMP PREEMPT_DYNAMIC Thu Mar 30 13:33:47 CEST 2023 x86_64 x86_64 x86_64 GNU/Linux

mitigations=off retbleed=off

I understand you are about performance, however we are about consistency and a secure environment. We do not test with these kind of changes.

@jsliacan No need to verify this for now; non-standard setup

mitigations=off retbleed=off

I understand you are about performance, however we are about consistency and a secure environment. We do not test with these kind of changes.

Just think, that I am java programmer, learning k8s-oc ... That's my own pc...

@gbraad
Ok, restart using fedora kernel ...  you're right, it seems working perfect!  [at now]
 crc config view
- consent-telemetry                     : yes
$ crc start
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 minimum RAM requirements
INFO Checking if crc executable symlink exists
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
INFO Checking if a supported libvirt version is installed
INFO Checking if crc-driver-libvirt is installed
INFO Checking crc daemon systemd socket units
INFO Checking if systemd-networkd is running
INFO Checking if NetworkManager is installed
INFO Checking if NetworkManager service is running
INFO Checking if dnsmasq configurations file exist for NetworkManager
INFO Checking if the systemd-resolved service is running
INFO Checking if /etc/NetworkManager/dispatcher.d/99-crc.sh exists
INFO Checking if libvirt 'crc' network is available
INFO Checking if libvirt 'crc' network is active
INFO Loading bundle: crc_libvirt_4.12.5_amd64...
INFO Starting CRC VM for openshift 4.12.5...
INFO CRC instance is running with IP <IP_ADDRESS>
INFO CRC VM is running
INFO Updating authorized keys...
INFO Configuring shared directories
INFO Check internal and public DNS query...
INFO Check DNS query from host...
INFO Verifying validity of the kubelet certificates...
INFO Starting kubelet service
INFO Waiting for kube-apiserver availability... [takes around 2min]

So sorry by my mistake.. I dont think that it could be a kernel config issue ... minishift , minikube ... works ok ..
Tx

kernel config issue

sorry, but it actually looks like it. Seccomp is a security framework that is part of the kernel, hence my questions directly pointing at this. Virtiofsd might trigger a certain path that does not work correctly, as this is a driver for the filesharing between the VM and the host (which uses the kernel's virtio). This is not something Minishift or minikube uses (we worked on these before).

FYI,
Something running in :
DEBU (crc) DBG ---  msg="GetIP called for crc"
My mistake:
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2023-04-04T18:15:46+02:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2023-04-04T18:15:46+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2023-04-04T18:15:46+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2023-04-04T18:15:46+02:00" level=warning msg="Failed to start: virError(Code=1, Domain=10, Message='internal error: qemu unexpectedly closed the monitor: 2023-04-04T16:15:46.308870Z qemu-system-x86_64: -device {\"driver\":\"vhost-user-fs-pci\",\"id\":\"fs0\",\"chardev\":\"chr-vu-fs0\",\"tag\":\"dir0\",\"bus\":\"pci.1\",\"addr\":\"0x0\"}: Failed to write msg. Wrote -1 instead of 12.\n2023-04-04T16:15:46.308890Z qemu-system-x86_64: -device {\"driver\":\"vhost-user-fs-pci\",\"id\":\"fs0\",\"chardev\":\"chr-vu-fs0\",\"tag\":\"dir0\",\"bus\":\"pci.1\",\"addr\":\"0x0\"}: vhost_backend_init failed: Protocol error')"
DEBU Making call to close driver server

<..>
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
seccomp_init() failed

fedora kernel:
INFO Starting CRC VM for openshift 4.12.5...
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2023-04-04T18:25:44+02:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2023-04-04T18:25:44+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2023-04-04T18:25:44+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2023-04-04T18:25:50+02:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2023-04-04T18:25:50+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2023-04-04T18:25:50+02:00" level=debug msg="IP address: <IP_ADDRESS>"
DEBU (crc) DBG | time="2023-04-04T18:25:50+02:00" level=info msg="Found IP for machine: <IP_ADDRESS>"
DEBU (crc) Calling .GetConfigRaw

<..>
virtio_session_mount: Waiting for vhost-user socket connection...
virtio_session_mount: Received vhost-user socket connection
virtio_loop: Entry
fv_queue_set_started: qidx=0 started=1
fv_queue_set_started: qidx=1 started=1
fv_queue_thread: Start for queue 0 kick_fd 10
fv_queue_thread: Start for queue 1 kick_fd 13

@gbraad
And again, you're right, ...
Enable seccomp to safely execute untrusted bytecode (SECCOMP)  - N -
Ok,
TO-DO .. enable it , compile and test ...

Ok, ...
uname -a Linux darkstar 6.2.9 #8 SMP PREEMPT_DYNAMIC Tue Apr  4 18:56:10 CEST 2023 x86_64 x86_64 x86_64 GNU/Linux
`Enable seccomp to safely execute untrusted bytecode (SECCOMP) - Y -
And ...
DEBU (crc) Calling .GetState
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Fetching VM..."
INFO Starting CRC VM for openshift 4.12.5...
DEBU Updating CRC VM configuration
DEBU (crc) Calling .GetConfigRaw
DEBU (crc) Calling .Start
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Starting VM crc"
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Validating network"
DEBU (crc) DBG | time="2023-04-04T18:59:04+02:00" level=debug msg="Validating storage pool"
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="Getting current state..."
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="IP address: <IP_ADDRESS>"
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=info msg="Found IP for machine: <IP_ADDRESS>"
DEBU (crc) Calling .GetConfigRaw
DEBU Waiting for machine to be running, this may take a few minute`s...
DEBU retry loop: attempt 0
DEBU (crc) Calling .GetState
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="Getting current state..."
DEBU Machine is up and running!
DEBU (crc) Calling .GetState
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="Getting current state..."
DEBU (crc) Calling .GetIP
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="GetIP called for crc"
DEBU (crc) DBG | time="2023-04-04T18:59:09+02:00" level=debug msg="Getting current state..."

OMG!


Pre-trained checkpoints

Thanks for the repo,
Are there pre-trained model checkpoints available?
Thanks

I'm training Hengshuang's model now, but only with ModelNet40 and S3DIS data. I'll let you know when it's done.

Thanks for the repo,
Are there pre-trained model checkpoints available?
Thanks

I am looking for the same thing, I even wrote to the authors of the paper but they didn't answer me

Please download here:
https://drive.google.com/file/d/1WxzsRYmhXQDCc4ctLGeVUM0ReBOi9bIC/view?usp=sharing
I trained the model for 180 epochs (at that time I miscalculated the training time, so I only got about 180 epochs before my machine shutting down). The instance accuracy is 90.16.
The reported accuracy in this repo is 91.7 with 200 epochs. So, today I continued the training but could not achieve higher accuracy. Please let me know if this is sufficient for you. If not, I can give another try by training from scratch, hopefuly to get the similar accuracy.


expressions not allowed for array types

Expected Behavior
Samples that use expressions for values of array types should pass schema check.
Actual Behavior
Samples that have an expression in place of an actual array raise an error when checked against schema.
Steps to Reproduce the Problem

Test each sample against schema with ajv:
ajv -c ajv-formats -s workflows.yaml -d iterate_googleapis_translate.workflows.json
Output will include error:  {
    instancePath: '/1/translateToFrench/for/in',
    schemaPath: '#/properties/in/type',
    keyword: 'type',
    params: { type: 'array' },
    message: 'must be array'
 },

there is a way to accept multiple types, and the validators will only apply to the relevant types. So something like the below should work for in:
        "in": {
          "description": "A list expression\nhttps://cloud.google.com/workflows/docs/reference/syntax/iteration",
          "type": [ "array", "string" ],
          "pattern": "^\\${.+}$"
        },


Unable to use configuration with URI Parts

Currently, if I specify the Rabbit Host Parts via topology config, I get a a NPE when it is trying to configure the connection. It looks up HA Hosts and fails because it is null (not specified). If I use "" for Hosts, it fails again trying to use the value as a host. The Config.getFromMap() needs to check for null before trying .toString().
I fixed this in a pull request.

Same issue. It is currently not possible to configure it via the topology config unless you define rabbitmq.ha.hosts, see  [https://github.com/ppat/storm-rabbitmq/blob/master/src/main/java/io/latent/storm/rabbitmq/config/ConnectionConfig.java#L176]
Any reason not to fix it?


⚠ Bofrost.es has degraded performance

In 26f473c, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 2558 ms

Resolved: Bofrost.es performance has improved in 3c51b04 after 6 minutes.


The kubectl deploy package is out of sync with the kcctl version

Describe the Bug
The kubectl deploy package is out of sync with the kcctl version
Versions Used
Kubernetes: V1.23.6
Kubeclipper: master
Environment
How many nodes and their hardware configuration:
CentOS 7.7 / 1 masters: 4cpu/8g
Screenshot

/assign @lixd

assign @qinyer

/assign @qinyer


Configuring Linters not supported by any extension

System
Does this issue occur when all extensions are disabled?: Yes
Version: 1.82.2
Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
Date: 2023-09-14T05:51:20.981Z
Electron: 25.8.1
ElectronBuildId: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Linux 20.04 x64 5.15.0-84-generic snap
Question
:point_right:  I used to have linters configured in settings inside devcontainer.json, but now linters are managed through extensions. How can we now configure other linters (ie.: pydocstyle) if they do not have an specific extension? Thank you.

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Filter push down need consider alias columns

Describe the bug
Filter push down not consider alias columns
To Reproduce
Logical plan
Received plan for execution: Limit: 50000
  Projection: #LINEORDER.LO_SHIPMODE, #TEST1
    Projection: #LO_SHIPMODE AS LINEORDER.LO_SHIPMODE, #testBITMAPCOUNTDISTINCT(_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_) AS TEST1
      Aggregate: groupBy=[[#LO_SHIPMODE]], aggr=[[testBITMAPCOUNTDISTINCT(#_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_)]]
        Projection: #LO_SHIPMODE, #dummy_LINEORDER_LO_SUPPKEY, #_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_
          Filter: #LO_SHIPMODE IN ([CAST(Int32(1) AS Utf8), CAST(Int32(2) AS Utf8), CAST(Int32(3) AS Utf8), CAST(Int32(4) AS Utf8), CAST(Int32(5) AS Utf8)])
            Projection: #LO_ORDERKEY, #LO_LINENUMBER, #LO_CUSTKEY, #LO_PARTKEY, #dummy_LINEORDER_LO_SUPPKEY, #LO_ORDERDATE, #LO_ORDERPRIORITY, #LO_SHIPPRIORITY, #LO_QUANTITY, #LO_EXTENDEDPRICE, #LO_ORDTOTALPRICE, #LO_DISCOUNT, #LO_TAX, #LO_COMMITDATE, #LO_SHIPMODE, #_KY_COUNT__, #_KY_COUNT_DISTINCT_LINEORDER_LO_ORDERKEY_, #_KY_COUNT_DISTINCT_LINEORDER_LO_SHIPPRIORITY_LINEORDER_LO_SUPPKEY_, #_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_, #_KY_PERCENTILE_APPROX_LINEORDER_LO_EXTENDEDPRICE_, #_KY_APPROX_TOPN_SUM_LINEORDER_LO_EXTENDEDPRICE_, #_KY_APPROX_BITOPN_SUM_LINEORDER_LO_EXTENDEDPRICE_, #_KY_APPROX_SUM_TOPN_LINEORDER_LO_EXTENDEDPRICE_, #_KY_APPROX_SUM_BITOPN_LINEORDER_LO_EXTENDEDPRICE_, #dummy_LINEORDER__KY_SUM_LINEORDER_LO_EXTENDEDPRICE_, #dummy_LINEORDER__KY_MAX_LINEORDER_LO_EXTENDEDPRICE_
              Projection: #ssb<EMAIL_ADDRESS>AS LO_ORDERKEY, #ssb<EMAIL_ADDRESS>AS LO_LINENUMBER, #ssb<EMAIL_ADDRESS>AS LO_CUSTKEY, #ssb<EMAIL_ADDRESS>AS LO_PARTKEY, Utf8("1") AS dummy_LINEORDER_LO_SUPPKEY, #ssb<EMAIL_ADDRESS>AS LO_ORDERDATE, #ssb<EMAIL_ADDRESS>AS LO_ORDERPRIORITY, #ssb<EMAIL_ADDRESS>AS LO_SHIPPRIORITY, #ssb<EMAIL_ADDRESS>AS LO_QUANTITY, #ssb<EMAIL_ADDRESS>AS LO_EXTENDEDPRICE, #ssb<EMAIL_ADDRESS>AS LO_ORDTOTALPRICE, #ssb<EMAIL_ADDRESS>AS LO_DISCOUNT, #ssb<EMAIL_ADDRESS>AS LO_TAX, #ssb<EMAIL_ADDRESS>AS LO_COMMITDATE, #ssb<EMAIL_ADDRESS>AS LO_SHIPMODE, #ssb<EMAIL_ADDRESS>AS _KY_COUNT__, #ssb<EMAIL_ADDRESS>AS _KY_COUNT_DISTINCT_LINEORDER_LO_ORDERKEY_, #ssb<EMAIL_ADDRESS>AS _KY_COUNT_DISTINCT_LINEORDER_LO_SHIPPRIORITY_LINEORDER_LO_SUPPKEY_, #ssb<EMAIL_ADDRESS>AS _KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_, #ssb<EMAIL_ADDRESS>AS _KY_PERCENTILE_APPROX_LINEORDER_LO_EXTENDEDPRICE_, #ssb<EMAIL_ADDRESS>AS _KY_APPROX_TOPN_SUM_LINEORDER_LO_EXTENDEDPRICE_, #ssb<EMAIL_ADDRESS>AS _KY_APPROX_BITOPN_SUM_LINEORDER_LO_EXTENDEDPRICE_, #ssb<EMAIL_ADDRESS>AS _KY_APPROX_SUM_TOPN_LINEORDER_LO_EXTENDEDPRICE_, #ssb<EMAIL_ADDRESS>AS _KY_APPROX_SUM_BITOPN_LINEORDER_LO_EXTENDEDPRICE_, Utf8("1") AS dummy_LINEORDER__KY_SUM_LINEORDER_LO_EXTENDEDPRICE_, Utf8("1") AS dummy_LINEORDER__KY_MAX_LINEORDER_LO_EXTENDEDPRICE_
                TableScan: ssb@test_udaf_cube_update@17179869183 projection=Some([0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44])

logical plan optimize
Calculated optimized plan: Limit: 50000
  Projection: #LINEORDER.LO_SHIPMODE, #TEST1
    Projection: #LO_SHIPMODE AS LINEORDER.LO_SHIPMODE, #testBITMAPCOUNTDISTINCT(_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_) AS TEST1
      Aggregate: groupBy=[[#LO_SHIPMODE]], aggr=[[testBITMAPCOUNTDISTINCT(#_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_)]]
        Projection: #LO_SHIPMODE, #_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_
          Projection: #LO_SHIPMODE, #_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_
            Projection: #ssb<EMAIL_ADDRESS>AS LO_SHIPMODE, #ssb<EMAIL_ADDRESS>AS _KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_
              Filter: #LO_SHIPMODE IN ([Utf8("1"), Utf8("2"), Utf8("3"), Utf8("4"), Utf8("5")])
                TableScan: ssb@test_udaf_cube_update@17179869183 projection=Some([12, 37]), partial_filters=[#LO_SHIPMODE IN ([Utf8("1"), Utf8("2"), Utf8("3"), Utf8("4"), Utf8("5")])]

physical plan optimize

create_physical_plan optimized plan: Limit: 50000
  Projection: #LINEORDER.LO_SHIPMODE, #TEST1
    Projection: #LO_SHIPMODE AS LINEORDER.LO_SHIPMODE, #testBITMAPCOUNTDISTINCT(_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_) AS TEST1
      Aggregate: groupBy=[[#LO_SHIPMODE]], aggr=[[testBITMAPCOUNTDISTINCT(#_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_)]]
        Projection: #LO_SHIPMODE, #_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_
          Projection: #LO_SHIPMODE, #_KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_
            Projection: #ssb<EMAIL_ADDRESS>AS LO_SHIPMODE, #ssb<EMAIL_ADDRESS>AS _KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_
              Filter: #LO_SHIPMODE IN ([Utf8("1"), Utf8("2"), Utf8("3"), Utf8("4"), Utf8("5")])
                TableScan: ssb@test_udaf_cube_update@17179869183 projection=Some([12, 37]), partial_filters=[#LO_SHIPMODE IN ([Utf8("1"), Utf8("2"), Utf8("3"), Utf8("4"), Utf8("5")])]

in logical plan Filter: #LO_SHIPMODE IN  is after alias Projection: #LO_ORDERKEY
After optimize Filter is before Projection.
cause :
ERROR  Could not create physical plan: Error during planning: No field named '<unqualified>.LO_SHIPMODE'. Valid fields are 'ssb<EMAIL_ADDRESS>'ssb<EMAIL_ADDRESS>
Expected behavior
could find alias col
Additional context
Add any other context about the problem here.

@alamb  PTAL  I consider change in_list col  alias name to origin name in  optimize? Is this solution ok ?  Specifically, you are proposing:
            Projection: #ssb<EMAIL_ADDRESS>AS LO_SHIPMODE, #ssb<EMAIL_ADDRESS>AS _KY_COUNT_DISTINCT_LINEORDER_LO_SUPPKEY_
              Filter: #LO_SHIPMODE IN ([Utf8("1"), Utf8("2"), Utf8("3"), Utf8("4"), Utf8("5")])  <-- **** This filter should be `#ssb<EMAIL_ADDRESS>IN ....`
                TableScan: ssb@test_udaf_cube_update@17179869183 projection=Some([12, 37]), partial_filters=[#LO_SHIPMODE IN ([Utf8("1"), Utf8("2"), Utf8("3"), Utf8("4"), Utf8("5")])]

If I read your conclusion corrctly, I think you are saying that the filter added by the filter pushdown rule is remapping the names somehow.  Same idea as you, i am working on it 😊


chore: bdd-nh-1585012920 to 0.0.1

chore: Promote bdd-nh-1585012920 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


add some toString() methods for logging

Signed-off-by: Markus Rathgeb<EMAIL_ADDRESS>

Please implement it in a same way as it is done for Volume, Item and Media classes (i.e. use String.format()) for uniformity.

Do you also want to drop the variable names?
I assume it is not common readable for e.g. MediaStatus as it contains a lot of members.
WDYT?

@vitalidze ping...
I changed the toString() methods so it fits to Volume, Item and Media.
I still miss your reply about the variable names.
I am also not sure how you would like to format Collections.

I still miss your reply about the variable names.

It makes sense to add variable names, I think colon separated, something like this:
Media{url: %s, contentType: %s, duration: %s}

If you agree with such format then please if possible change it everywhere.
Thank you!

One little addition: I think such format is applicable only for classes with more than one field. For example for Namespace I think we can just leave the Namespace{%s} format.

Looks good to me. Merged. Thank you very much!


[DOC] Operator tutorial typo

Change in the documentation
Notice that the welcome message has changed from "Welcome to FaaS: Fibonacci as a Service!" to "Welcome to Fib3r: Fibonacci as a Service!".
Whereas actually it should read:
Notice that the welcome message has changed from "Welcome to FaaS: Fibonacci as a Service!" to "Fib3r: Math at the speed of the internet!".

Fixed, thanks: https://github.com/open-feature/openfeature.dev/commit/b780cc805f81deaac4cdb2481033885f84f67bf0


Fix for WFMP-209, Can't use maven http transport with maven < 3.9

Issue: https://issues.redhat.com/browse/WFMP-209
The maven-resolver dependencies are not needed by the plugin. We must rely on default Maven handling of the transport aspects.

@jamezp , the remaining failure is un-related to this change. This build image tests failed in some previous runs.

Yes, I've been thinking about disabling these tests for Windows as they seem flaky. I guess I should dig into why they are flaky first though :)


Insufficient readme, what "application type" to choose in google cloud ?

Full steps to reproduce the issue:

Using gyb unix executable on macbook, download from gyb-1.37-macos-x86_64-MacOS10.13.6.tar.xz
Execute command:

Administrators-MacBook-Pro-6:gyb user$ ./gyb --email<EMAIL_ADDRESS>--action estimate
ERROR: Please configure a project

To make GYB run you will need to populate the client_secrets.json file. Try
running:

./gyb --action create-project --email<EMAIL_ADDRESS>

[Errno 2] No such file or directory: '/Users/user/Downloads/gyb/client_secrets.json'Administrators-MacBook-Pro-6:gyb user$

Execute command:

Administrators-MacBook-Pro-6:gyb user$ ./gyb --action create-project --email<EMAIL_ADDRESS>
Go to the following link in your browser:

	https://gyb-shortn.jaylee.us/hv2xxx

Enter verification code:

Go to the link provided, click to allow "GAM Project Creation" make changes in my gmail account.
Verfication code show up, i copy that
Back to my terminal, i put the verification code, then press enter:

Enter verification code: 4/0gEiu-XzqeO1wAF5qxxxxxxxxxCPIPcxKk9YYa2SPuclPQVEQRvoq8
Creating project "Got Your Back Project"...
Checking project status...
 enabling API drive.googleapis.com...
 enabling API gmail.googleapis.com...
 enabling API groupsmigration.googleapis.com...
 enabling API vault.googleapis.com...
Creating Service Account
Please go to:

https://console.developers.google.com/apis/credentials/consent/edit?createClient&newAppInternalUser=true&project=gyb-project-xxx-xxx-xxx

1. Enter "GYB" for "Application name".
2. Leave other fields blank. Click "Save" button.
3. Choose "Other". Enter a desired value for "Name". Click the blue "Create" button.
4. Copy your "client ID" value.

Enter your Client ID:

Open the link in browser, Enter "GYB" for "Application name". Leave other fields blank. Click "Save" button.
Then this page show up:

https://drive.google.com/file/d/1XtOmLb6lf9Bhr80ZT-HHgdRKXcgEsdJo/view?usp=sharing

What to choose in the "Application Type" ? Please put more details in the wiki. Thanks.

We need to choose Desktop app as the Application Type during creating an OAuth Client ID.
https://github.com/jay0lee/got-your-back/issues/277#issuecomment-645040380

We hit this issue yesterday as well.
GYB asks you to choose "Other" as the OAuth Client Type - but there is no such option:

If you pick "Web application", which seems a reasonable guess, it will fail - later on it will say "Error 400: redirect_uri_mismatch":

Hence, I think the code should be updated to change from "Other" to "Desktop app".

This was also reported in #272 and fixed in #273


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test

Docs Build status updates of commit 09df309:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-25-05-29-19 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-25-05-29-19

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.


Explorer windows still tend to get incorrect focus

Not a major issue, nonetheless pretty annoying in the daily workflow - if there are many explorer windows and the user switches screens a few times it often happens that the wrong one gets focus (especially on "my computer").
Is there no way to remember window handles and set focus accordingly (alt+tab is also quite visible and ugly)?

I had noticed this behavior but it hadn't annoyed me enough to change it.  The reason it happens is because My Computer has the ahk_exe of "explorer.exe". I've updated the window check in this commit: b5ec31308c36c1ea0a9ee5585bb878183e0cfd99
I agree that the alt+tab thing is a bit hacky but I don't know of a better way to do it. Any suggestions?

I just do simple scripting, but I'll look into it at some point.
Anyways, thanks for the commit, explorer got a little bit less annoying today ^^.

This is fixed now. I use winget,,list + a dll  call to check the windows desktop to find the appropriate window to focus


Add HONEYPIE by JAWNY

Song Name
HONEYPIE
Artist Name
JAWNY
Source
Youtube
Youtube Link
https://youtu.be/Wgw6tJ8yz9M?si=fVK4hIaRi44KGPjk
Direct File Link
No response
Song ID
467339
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 108590176

reject
popular songs like "At the Speed of light" are too inconvenient to be replaced by smth unrelated and are therefore usually rejected.
Note that you can still use the song yourself, but it won't be public


new update to hellow

new update
new changes
new update to hello
new workflow to check the status of pipeline
hello update

Issue # (if applicable)
Closes #.
Reason for this change

Description of changes

Description of how you validated changes

Checklist

[ ] My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

:arrow_right: Integ test deployment request submitted to integ-test-pipeline :arrow_left:
A maintainer must now check the pipeline and add the pr-linter/integ-test-checked label once the pipeline succeeds.


Add model graph to logger

add graph to visualize models in the logger (tensorboard in this case)

It might be a good idea to integrate aim support before merging this in

stale, closing


Work in progress: Support sound

Mount /dev/snd of the host to a container as a volume.
Fix: https://github.com/debarshiray/toolbox/issues/58
It tested with liquidwar game inside containers, the sound works well.

It doesn't work if an application using sound drivers on the host.

Close this issue until finding a solution and keep talking about it in the issue, #58


audioCodec doesn't recognize 'aac' or 'libfdk-aac'

Hi,
I want to convert mp3 to aac and stream it to s3. My code is as below. Now when I try to use audioCodec as 'aac' or 'libfdk-aac'. It throws the error. Note that ffmpeg is compiled with 'libfdk-aac' and working fine from command line.
Any inputs/fixes ?
                                                        var proc = new ffmpeg({source:uploadedFiles[0].fd})
					           .audioCodec('aac')
					           .audioChannels(1);

                                                                             proc.on('error', function(err) {
								      		console.log('An error occurred: ' + err.message);
									  })
									  .on('end', function() {
											console.log('audio uploaded successfully!');

           									 })
									  .pipe(upload(opts));

What is the error ?

Hi,
The error it sends is as below.
An error occurred: ffmpeg exited with code 1: pipe:1: Invalid argument
Thanks,
Mayur

You have to specify a format when outputting to a pipe (.format('something')). You could have seen the full error by inspecting the second and third arguments to the error event handler (they contain ffmpeg stdout/stderr).
The error you get on Linux also indicates that either your ffmpeg version does not support aac or you don't have the necessary libraries installed.

Closing this as no feedback was given. Feel free to reopen, though.


Add OpenAPI via Aide after migration to Axum

https://docs.rs/aide/latest/aide/axum/index.html

Utopia is worth checking out. https://github.com/juhaku/utoipa


undefined is not an object problem

Hi
I want to test codes in this page: https://reactnavigation.org/docs/intro
And I get an error message:
undefined is not an object (evaluating this.props.navigation.navigate)
The problem is from this line:
const { navigate } = this.props.navigation;
When I remove this line it shows the screen completly just after click in the buttin error happen. but with this line program starts with error!
What is this problem reason and how I can fix it?

Is the component the screen of a navigator as seen in the example above in https://reactnavigation.org/docs/intro#Introducing-Stack-Navigator ?

@matthamil
Sorry I can't understand you clearly but if you mean using StackNavigator part, It's code is like below:
const SimpleApp = StackNavigator({
Home: { screen: HomeScreen },
Chat: { screen: ChatScreen },
});

Change the AppRegistry line to render SimpleApp.

Can you post your full code?

I meet the same problem, how do you fix it?

@IcyCC Can you post your code?

I write these in index.android.js
const HomeNav = StackNavigator(
    {

        HomeMain: {
            screen: HomePage,
            navigationOptions: {
                headerLeft: null
            }
        },
    }
);
const MovieNav = StackNavigator(
    {

        MovieMain: {
            screen: MoviePage,
            navigationOptions: {
                headerLeft: null
            }
        },
        Choose:{
            screen: MovieChoose
        },
        Card:{
            screen:MovieCard
        }
    }
);

const Ticket = TabNavigator({
        Main: { screen: HomeNav },
        Movie:{screen:MovieNav},
        Social:{screen:SocialPage},
        Setting:{screen:SettingPage},

    },
    {tabBarPosition:'bottom'}
)
AppRegistry.registerComponent('Ticket', () => Ticket);

And when I write
export default class MovieCard extends Component {
    constructor(props)
    {
        super(props);

    }

    render() {
        const { navigate } = this.props.navigation;
        return (
            <TouchableOpacity >
            <View >
            <Image style={style.bgImage} source={{uri:this.props.imgUrl}} />
                <Text style={style.tittle}>{this.props.tittle}</Text>
                <Text style={style.detail}>{this.props.detail}</Text>
            </View>
            </TouchableOpacity>
        );
    }
}

the error happen . And I put  const { navigate } = this.props.navigation; in other component there no error

@IcyCC Do you have a repo with the entire source code? It's hard to tell from what you posted to see where the bug is. It could be an issue with incorrect import names.

like this ?https://github.com/IcyCC/Ticket-app

@IcyCC You are trying to render a MovieCard component without explicitly passing navigation down as a prop. https://github.com/IcyCC/Ticket-app/blob/master/components/MoviePage/MovieContainer.js#L35

Thank you !!! I get it!You did me a big favor！

I'm having the same issue with the sample code from: https://reactnavigation.org/docs/intro#Introducing-Stack-Navigator
I basically copied and pasted the code into my editor (with the small difference that here I export the default HomeScreen and removed the AppRegistry). When I open it on Expo, I get the error: "undefined is not an object (evaluating 'this.props.navigation.navigate)'".
Any help? It's a bit frustrating that the example from the documentation does not work :)
Thank you in advance!
Fred
import React from 'react';
import {
AppRegistry,
Button,
Text,
View,
} from 'react-native';
import { StackNavigator } from 'react-navigation';
class ChatScreen extends React.Component {
static navigationOptions = {
title: 'Chat with Lucy',
};
render() {
return (

Chat with Lucy

);
}
}
export default class HomeScreen extends React.Component {
static navigationOptions = {
title: 'Welcome',
};
render() {
const { navigate } = this.props.navigation;
return (

Hello, Chat App!
<Button
onPress={() => navigate('Chat')}
title="Chat with Lucy"
/>

);
}
}
const TheApp = StackNavigator({
Home: { screen: HomeScreen },
Chat: { screen: ChatScreen },
});

Getting the same error with the example from the documentation here: https://facebook.github.io/react-native/docs/navigation.html
`
import React from 'react';
import { Alert, AppRegistry, Text, TextInput, View } from 'react-native';
import {
StackNavigator,
} from 'react-navigation';
export default class HomeScreen extends React.Component {
static navigationOptions = {
title: 'Welcome',
};
render() {
const { navigate } = this.props.navigation;
return (
<Button
title="Go to Jane's profile"
onPress={() =>
navigate('Profile', { name: 'Jane' })
}
/>
);
}
}
class ProfileScreen extends React.Component {
static navigationOptions = {
title: 'Welcome',
};
render() {
const { navigate } = this.props.navigation;
return (
Here we are
);
}
}
const App = StackNavigator({
Home: { screen: HomeScreen },
Profile: { screen: ProfileScreen },
});
`
Any idea what might be wrong?  I will be happy to send a PR to update the documentation if we can manage to understand the problem here.

It looks like you are exporting your screen components. You should be exporting the navigator. If you render the screen components, you will not have access to navigation as a prop because the navigator did not render them. If you render the navigator, it will pass navigation as a prop down to any children screen components.

Thanks @matthamil ! Is there any up-to-date documentation on that?

It is documented here: https://reactnavigation.org/docs/navigators/navigation-prop#Screen-Navigation-Prop, although this isn't the first time someone has encountered this problem. If you know a way to word the documentation better to prevent this from happening for other users, feel free to open a PR to help everyone out :)

Sure thing! It's a bit frustrating that the Hello World example in the Getting Started does not work :)
I will check the link you sent, try to reproduce it here and send a PR with updated documentation.
Thank you so much!
---q

@matthamil Having the same problem - can you give more explicit instructions on how to pass navigation as a prop?  Thanks! :)

@pmuldoon86 I managed to set my navigation correctly after watching this screencast:
https://hackernoon.com/getting-started-with-react-navigation-the-navigation-solution-for-react-native-ea3f4bd786a4
It shows some basic tab + stack navigation hints that's exactly what I was looking for.
If you're writing a normal screen, you have to "export" it in the end of the code to make sure it can be navigated to:
import React, {Component} from 'react';
import { ScrollView, Text } from 'react-native';
`import React, {Component} from 'react';
import { ScrollView, Text } from 'react-native';
class Tools extends Component {
render() {
return (

Hello!

);
}
}
export default Tools;
`

@pmuldoon86 Within your screen component, you have access to this.props.navigation. You can pass the prop down to child components like so:
render() {
  return <MyOtherComponent navigation={this.props.navigation}/>
}

This is no different from how you would pass props down in React because that's exactly what it is :)

I'm going to close this issue for now. This seems to be a fairly common issue, so I will see how the documentation describes how navigation works as a prop. Feel free to submit a PR to improve our documentation if you find it lacking. 👍
I am assuming that one of these solutions resolves your problem @payamka. If your issue is not resolved, please comment or open another issue.

Thanks!

If using Expo, you need something like this: export default SimpleApp
not AppRegistry.registerComponent('SimpleApp', () => SimpleApp);

@matthamil
Hi Matt, I am hoping you can help me.  I have been working on the same problem the past three days, trying everything. It seems like you have been able to help people solve this problem in the past.  Somehow "navigation" is not being passed to my "navigated" components. I have tried putting the StackNavigator code everywhere - own file, like it is now, in App.js, in the files of one of my components.  Nothing has worked.  Here is a link to my repository..  https://github.com/rscharfer/mobileflashcards
Do you think you can help?  The StackNavigator code is in stack.js currently.

I was having the same issue. It was solved by changing onPress={() => this.navigation.navigate(data)} to onPress={() => this.props.navigation.navigate(data)}.

Login.js
import React, { Component } from 'react';
import {
Platform,
StyleSheet,
Text,
View,
Button,
TouchableOpacity,
} from 'react-native';
import { StackNavigator } from 'react-navigation';
import Logo from '../components/Logo';
import Form from '../components/Form';
export default class Login extends Component<{}> {
static navigationOption = {
  title: 'React Courses',
}

  render() {
    const { navigate } = this.props.navigation;
    return (
      <View style={styles.container}>
        <Logo/>
        <Form type="Login"/>
        <View style={styles.signupViewText}>
            <Text style={styles.signupText}>Don't have an account yet? </Text>
            <TouchableOpacity onPress={this.onTap}>
              <Text style={styles.signupButton}> SignUp</Text>
            </TouchableOpacity>
            <Button
              onPress={() => navigate('SignupPage')}
              title='React Native Courses'
            />
        </View>

      </View>

);

}
}
const styles = StyleSheet.create({
container: {
flexGrow: 1,
alignItems: 'center',
},
signupViewText: {
flexGrow: 1,
flexDirection: 'row',
},
signupText: {
// color: 'rgba(255, 255, 255, 0.6)',
color: '#ff0000',
fontSize: 16,
},
signupButton: {
fontSize: 16,
color: '#000099',
fontWeight: '500',
},
});
SignupPage.js
import React, { Component } from 'react';
import {
StyleSheet,
Text,
View,
Button,
} from 'react-native';
import { StackNavigator } from 'react-navigation';
import Logo from '../components/Logo';
import Form from '../components/Form';
export default class SignupPage extends Component<{}> {
static navigationOption = {
  title: 'React Native Courses',
}

render() {
    const { navigate } = this.props.navigation;
    return (
      <View style={styles.container}>
            <Button
              onPress={() => navigate('Login')}
              title='React Courses'
            />
        </View>

    );
  }
}

const styles = StyleSheet.create({
    container: {
        flexGrow: 1,
        alignItems: 'center',
    },
  });

Never use stack navigation in 'index.android.js' file
if we intend to use navigation in 'index.android.js'. this line execute ' this.props.navigation'before the component is registered in App registry. that is the reason we get
Error:
undefined is not an object (evaluating this.props.navigation.navigate)
Code for navigation
// index.android.js file
import React, { Component } from 'react';
import {
Platform,
StyleSheet,
Text,
AppRegistry,
StatusBar,
View
} from 'react-native';
import MainActivity from './src/components/MainActivity';
type Props = {};
class HelloUser extends Component {
render() {
return ( );
}
}
AppRegistry.registerComponent('CommunityApp', () => HelloUser);

// MainActivity.js
import React, {
Component
} from 'react';
import {
AppRegistry, WebView,TouchableOpacity, StyleSheet, FlatList, Platform, Image, Text,
View, Button
} from 'react-native';
import {
StackNavigator
}
from 'react-navigation';
import ThirdActivity from './ThirdActivity';
import pin from '../utils/pin.png';
class MainActivity extends Component {
static navigationOptions = {
title: 'Welcome',
};
FunctionToOpenSecondActivity = () => {this.props.navigation.navigate('Second');}
FunctionToOpenThirdActivity = () => {this.props.navigation.navigate('Third');}
render() {
return ( < View style = {
stylesMainActivity.Container  } >
  < View style = {stylesMainActivity.TopContainer} >
  < Image style = { stylesMainActivity.picture} source = {pin} />
  < /View>

  < View style = {stylesMainActivity.MiddleContainer} >
  < Image style = { stylesMainActivity.picture} source = {pin} />
  < /View>

  < View style = {stylesMainActivity.BottomContainer} >

  <TouchableOpacity style={stylesMainActivity.BottomContainer } onPress={
   this.FunctionToOpenSecondActivity}>
   < Image style = { stylesMainActivity.picture} source = {pin} />
   < Image style = { stylesMainActivity.picture} source = {pin} />
  </TouchableOpacity>
  < /View>

  < Button onPress = { this.FunctionToOpenThirdActivity}
  title = 'Click Here To Open Third Activity' / >
  < /View>
);

}
}

Undefined is not an object error message occuring in line
appRegistery.registerComponent('albums', () => App);


Assign proper listener priority

The bed listener is currently listening on a medium (default) priority, but is only used for monitoring.
Therefore it should use the monitoring level to ensure that the event was already handled by all other listeners which can potentially modify this event.
The current behaviour can cause issues with plugins which use high or highest priority on the bed enter event to cancel the event. They do this because they want to make the final decision if the player is allowed to enter the bed.
Currently harbor would already mark these players as sleeping, altohugh they are not because the event was canceled afterwards.

Awesome! I actually didn't know what the use of the MONITOR priority was until now- looks like it's perfect for this situation. Guess you learn something new every day.
Thanks for the contribution, I'll merge this in now.