Unable to use PHC time source in qemu guest.

Description of problem
Similar to #1279, we need to be able to keep guest time synchronized. Using ptp_kvm for a virtual PHC seems like an appropriate solution.
Expected result
According to the kernel configs in the packaging repository, it appears that CONFIG_PTP_1588_CLOCK_KVM is enabled. I'd expect a /dev/ptp0 interface to exist in the qemu guest.
Actual result
The char special file does not appear to be created. In a debug console, it looks like the kernel has support for ptp_kvm, but I'm unable to see or create the char device.
bash-4.4# dmesg -T | grep -i ptp
[Thu Mar  7 22:49:24 2019] PTP clock support registered
bash-4.4# grep ptp /proc/devices
250 ptp
bash-4.4# ls -l /dev/ptp0
ls: cannot access '/dev/ptp0': No such file or directory
bash-4.4# mknod /dev/ptp0 c 250 0
mknod: /dev/ptp0: Read-only file system

This issue is present in our kubernetes environments, but the below data was generated from a test environment using docker. I suspect the actual implementation matters little for this issue.
click here for data

# Meta details
Running kata-collect-data.sh version 1.5.1 (commit b1ef5212114ca866fd831f1620a374e02aad61e1-dirty) at 2019-03-08.11:01:14.224200419-0600.

Runtime is /root/go/src/github.com/kata-containers/runtime/kata-runtime.
kata-env
Output of "/root/go/src/github.com/kata-containers/runtime/kata-runtime kata-env":
[Meta]
  Version = "1.0.20"

[Runtime]
  Debug = true
  Trace = false
  DisableGuestSeccomp = false
  DisableNewNetNs = false
  Path = "/root/go/src/github.com/kata-containers/runtime/kata-runtime"
  [Runtime.Version]
    Semver = "1.5.1"
    Commit = "b1ef5212114ca866fd831f1620a374e02aad61e1-dirty"
    OCI = "1.0.1-dev"
  [Runtime.Config]
    Path = "/etc/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 3.1.50\nCopyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers"
  Path = "/opt/virtiofs/bin/qemu-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  EntropySource = "/dev/urandom"
  Msize9p = 8192
  MemorySlots = 10
  Debug = true
  UseVSock = false

[Image]
  Path = ""

[Kernel]
  Path = "/opt/virtiofs/vmlinuz"
  Parameters = "systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket"

[Initrd]
  Path = "/opt/virtiofs/kata-containers-initrd.img"

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.5.1-9faf7764002daf970e57c6584717a3380341b2dd"
  Path = "/opt/virtiofs/bin/kata-proxy"
  Debug = false

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.5.1-2dbd643783e0a141c91e375023631816a256d9c3"
  Path = "/opt/virtiofs/bin/kata-shim"
  Debug = true

[Agent]
  Type = "kata"

[Host]
  Kernel = "4.20.11-200.fc29.x86_64"
  Architecture = "amd64"
  VMContainerCapable = true
  SupportVSocks = false
  [Host.Distro]
    Name = "Fedora"
    Version = "29"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz"

[Netmon]
  Version = "kata-netmon version 1.5.1"
  Path = "/opt/virtiofs/bin/kata-netmon"
  Debug = true
  Enable = false

Runtime config files
Runtime default config files
/etc/kata-containers/configuration.toml
/usr/share/defaults/kata-containers/configuration.toml

Runtime config file contents
Output of "cat "/etc/kata-containers/configuration.toml"":
# Copyright (c) 2017-2018 Intel Corporation
#
# SPDX-License-Identifier: Apache-2.0
#

# XXX: WARNING: this file is auto-generated.
# XXX:
# XXX: Source file: "cli/config/configuration.toml.in"
# XXX: Project:
# XXX:   Name: Kata Containers
# XXX:   Type: kata

[hypervisor.qemu]
path = "/opt/virtiofs/bin/qemu-system-x86_64"
kernel = "/opt/virtiofs/vmlinuz"
initrd = "/opt/virtiofs/kata-containers-initrd.img"
image = ""
machine_type = "pc"

# Optional space-separated list of options to pass to the guest kernel.
# For example, use `kernel_params = "vsyscall=emulate"` if you are having
# trouble running pre-2.15 glibc.
#
# WARNING: - any parameter specified here will take priority over the default
# parameter value of the same name used to start the virtual machine.
# Do not set values here unless you understand the impact of doing so as you
# may stop the virtual machine from booting.
# To see the list of default parameters, enable hypervisor debug, create a
# container and look for 'default-kernel-parameters' log entries.
kernel_params = "systemd.unit=kata-containers.target systemd.mask=systemd-networkd.service systemd.mask=systemd-networkd.socket"

# Path to the firmware.
# If you want that qemu uses the default firmware leave this option empty
firmware = ""

# Machine accelerators
# comma-separated list of machine accelerators to pass to the hypervisor.
# For example, `machine_accelerators = "nosmm,nosmbus,nosata,nopit,static-prt,nofw"`
machine_accelerators=""

# Default number of vCPUs per SB/VM:
# unspecified or 0                --> will be set to 1
# < 0                             --> will be set to the actual number of physical cores
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores
default_vcpus = 1

# Default maximum number of vCPUs per SB/VM:
# unspecified or == 0             --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# > 0 <= number of physical cores --> will be set to the specified number
# > number of physical cores      --> will be set to the actual number of physical cores or to the maximum number
#                                     of vCPUs supported by KVM if that number is exceeded
# WARNING: Depending of the architecture, the maximum number of vCPUs supported by KVM is used when
# the actual number of physical cores is greater than it.
# WARNING: Be aware that this value impacts the virtual machine's memory footprint and CPU
# the hotplug functionality. For example, `default_maxvcpus = 240` specifies that until 240 vCPUs
# can be added to a SB/VM, but the memory footprint will be big. Another example, with
# `default_maxvcpus = 8` the memory footprint will be small, but 8 will be the maximum number of
# vCPUs supported by the SB/VM. In general, we recommend that you do not edit this variable,
# unless you know what are you doing.
default_maxvcpus = 0

# Bridges can be used to hot plug devices.
# Limitations:
# * Currently only pci bridges are supported
# * Until 30 devices per bridge can be hot plugged.
# * Until 5 PCI bridges can be cold plugged per VM.
#   This limitation could be a bug in qemu or in the kernel
# Default number of bridges per SB/VM:
# unspecified or 0   --> will be set to 1
# > 1 <= 5           --> will be set to the specified number
# > 5                --> will be set to 5
default_bridges = 1

# Default memory size in MiB for SB/VM.
# If unspecified then it will be set 2048 MiB.
default_memory = 4096
#
# Default memory slots per SB/VM.
# If unspecified then it will be set 10.
# This is will determine the times that memory will be hotadded to sandbox/VM.
#memory_slots = 10

# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons.
# This flag prevents the block device from being passed to the hypervisor,
# 9pfs is used instead to pass the rootfs.
disable_block_device_use = true

# Use virtio-fs instead of 9p for shared filesystems.
enable_virtio_fs = true
virtio_fs_daemon = "/opt/virtiofs/bin/virtiofsd"
virtio_fs_cache_size = 2

# Cache mode:
#
#  - none
#    Metadata, data, and pathname lookup are not cached in guest. They are
#    always fetched from host and any changes are immediately pushed to host.
#
#  - auto
#    Metadata and pathname lookup cache expires after a configured amount of
#    time (default is 1 second). Data is cached while the file is open (close
#    to open consistency).
#
#  - always
#    Metadata, data, and pathname lookup are cached in guest and never expire.
virtio_fs_cache = "none"

# Use shared version metadata
virtio_fs_shared_versions = false

# Block storage driver to be used for the hypervisor in case the container
# rootfs is backed by a block device. This is either virtio-scsi or
# virtio-blk.
block_device_driver = "virtio-scsi"

# Enable iothreads (data-plane) to be used. This causes IO to be
# handled in a separate IO thread. This is currently only implemented
# for SCSI.
#
enable_iothreads = false

# Enable pre allocation of VM RAM, default false
# Enabling this will result in lower container density
# as all of the memory will be allocated and locked
# This is useful when you want to reserve all the memory
# upfront or in the cases where you want memory latencies
# to be very predictable
# Default false
#enable_mem_prealloc = true

# Enable huge pages for VM RAM, default false
# Enabling this will result in the VM memory
# being allocated using huge pages.
# This is useful when you want to use vhost-user network
# stacks within the container. This will automatically
# result in memory pre allocation
enable_hugepages = true

# Enable swap of vm memory. Default false.
# The behaviour is undefined if mem_prealloc is also set to true
#enable_swap = true

# This option changes the default hypervisor and kernel parameters
# to enable debug output where available. This extra output is added
# to the proxy logs, but only when proxy debug is also enabled.
#
# Default false
enable_debug = true

# Disable the customizations done in the runtime when it detects
# that it is running on top a VMM. This will result in the runtime
# behaving as it would when running on bare metal.
#
#disable_nesting_checks = true

# This is the msize used for 9p shares. It is the number of bytes
# used for 9p packet payload.
#msize_9p = 8192

# If true and vsocks are supported, use vsocks to communicate directly
# with the agent and no proxy is started, otherwise use unix
# sockets and start a proxy to communicate with the agent.
# Default false
#use_vsock = true

# VFIO devices are hotplugged on a bridge by default.
# Enable hotplugging on root bus. This may be required for devices with
# a large PCI bar, as this is a current limitation with hotplugging on
# a bridge. This value is valid for "pc" machine type.
# Default false
#hotplug_vfio_on_root_bus = true

# If host doesn't support vhost_net, set to true. Thus we won't create vhost fds for nics.
# Default false
#disable_vhost_net = true
#
# Default entropy source.
# The path to a host source of entropy (including a real hardware RNG)
# /dev/urandom and /dev/random are two main options.
# Be aware that /dev/random is a blocking source of entropy.  If the host
# runs out of entropy, the VMs boot time will increase leading to get startup
# timeouts.
# The source of entropy /dev/urandom is non-blocking and provides a
# generally acceptable source of entropy. It should work well for pretty much
# all practical purposes.
#entropy_source= "/dev/urandom"

# Path to OCI hook binaries in the *guest rootfs*.
# This does not affect host-side hooks which must instead be added to
# the OCI spec passed to the runtime.
#
# You can create a rootfs with hooks by customizing the osbuilder scripts:
# https://github.com/kata-containers/osbuilder
#
# Hooks must be stored in a subdirectory of guest_hook_path according to their
# hook type, i.e. "guest_hook_path/{prestart,postart,poststop}".
# The agent will scan these directories for executable files and add them, in
# lexicographical order, to the lifecycle of the guest container.
# Hooks are executed in the runtime namespace of the guest. See the official documentation:
# https://github.com/opencontainers/runtime-spec/blob/v1.0.1/config.md#posix-platform-hooks
# Warnings will be logged if any error is encountered will scanning for hooks,
# but it will not abort container execution.
#guest_hook_path = "/usr/share/oci/hooks"

[factory]
# VM templating support. Once enabled, new VMs are created from template
# using vm cloning. They will share the same initial kernel, initramfs and
# agent memory by mapping it readonly. It helps speeding up new container
# creation and saves a lot of memory if there are many kata containers running
# on the same host.
#
# When disabled, new VMs are created from scratch.
#
# Default false
#enable_template = true

[proxy.kata]
path = "/opt/virtiofs/bin/kata-proxy"

# If enabled, proxy messages will be sent to the system log
# (default: disabled)
#enable_debug = true

[shim.kata]
path = "/opt/virtiofs/bin/kata-shim"

# If enabled, shim messages will be sent to the system log
# (default: disabled)
enable_debug = true

[agent.kata]
# There is no field for this section. The goal is only to be able to
# specify which type of agent the user wants to use.
agent_devmode = true

[netmon]
# If enabled, the network monitoring process gets started when the
# sandbox is created. This allows for the detection of some additional
# network being added to the existing network namespace, after the
# sandbox has been created.
# (default: disabled)
#enable_netmon = true

# Specify the path to the netmon binary.
path = "/opt/virtiofs/bin/kata-netmon"

# If enabled, netmon messages will be sent to the system log
# (default: disabled)
enable_debug = true

[runtime]
# If enabled, the runtime will log additional debug messages to the
# system log
# (default: disabled)
enable_debug = true
#
# Internetworking model
# Determines how the VM should be connected to the
# the container network interface
# Options:
#
#   - bridged
#     Uses a linux bridge to interconnect the container interface to
#     the VM. Works for most cases except macvlan and ipvlan.
#
#   - macvtap
#     Used when the Container network interface can be bridged using
#     macvtap.
#
#   - none
#     Used when customize network. Only creates a tap device. No veth pair.
#
#   - tcfilter
#     Uses tc filter rules to redirect traffic from the network interface
#     provided by plugin to a tap interface connected to the VM.
#
internetworking_model="macvtap"

# If enabled, the runtime will create opentracing.io traces and spans.
# (See https://www.jaegertracing.io/docs/getting-started).
# (default: disabled)
#enable_tracing = true

# If enabled, the runtime will not create a network namespace for shim and hypervisor processes.
# This option may have some potential impacts to your host. It should only be used when you know what you're doing.
# `disable_new_netns` conflicts with `enable_netmon`
# `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only
# with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false)
#disable_new_netns = true

Config file /usr/share/defaults/kata-containers/configuration.toml not found

KSM throttler
version
Output of " --version":
./data/kata-collect-data.sh: line 168: --version: command not found

systemd service
Image details
No image

Initrd details
---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2019-03-06T15:59:58.599676444-0600Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Fedora"
  version: "28"
  packages:
    default:
      - "iptables"
      - "systemd"
    extra:

agent:
  url: "https://github.com/kata-containers/agent"
  name: "kata-agent"
  version: "1.5.1-d3759ee3ea680022ea16f39772a7d521a350ea0d"
  agent-is-init-daemon: "no"

Logfiles
Runtime logs
Recent runtime problems found in system journal:
time="2019-03-06T15:57:13.444935973-06:00" level=error msg="Container ID (02ce864de38f0f4f04d2763fc909514dd767f714be0ca62b092c48ac968c427a) does not exist" arch=amd64 command=delete container=02ce864de38f0f4f04d2763fc909514dd767f714be0ca62b092c48ac968c427a name=kata-runtime pid=17635 source=runtime
time="2019-03-06T15:57:13.503881917-06:00" level=error msg="Container ID (02ce864de38f0f4f04d2763fc909514dd767f714be0ca62b092c48ac968c427a) does not exist" arch=amd64 command=delete container=02ce864de38f0f4f04d2763fc909514dd767f714be0ca62b092c48ac968c427a name=kata-runtime pid=17652 source=runtime
time="2019-03-06T16:11:01.23767395-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c error="open /run/vc/sbs/283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c/devices.json: no such file or directory" name=kata-runtime pid=39445 sandbox=283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c sandboxid=283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c source=virtcontainers subsystem=sandbox
time="2019-03-06T16:11:06.609509228-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c name=kata-runtime pid=39445 source=runtime
time="2019-03-06T16:11:06.678539803-06:00" level=error msg="Container ID (283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c) does not exist" arch=amd64 command=delete container=283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c name=kata-runtime pid=39511 source=runtime
time="2019-03-06T16:11:06.726394736-06:00" level=error msg="Container ID (283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c) does not exist" arch=amd64 command=delete container=283cef3f2de9be64af661e4e2dc6725ba3ffd4c998b549224118dd301ac30b0c name=kata-runtime pid=39527 source=runtime
time="2019-03-06T16:13:37.05563557-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062 error="open /run/vc/sbs/876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062/devices.json: no such file or directory" name=kata-runtime pid=39653 sandbox=876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062 sandboxid=876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062 source=virtcontainers subsystem=sandbox
time="2019-03-06T16:13:58.139641832-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062 name=kata-runtime pid=39653 source=runtime
time="2019-03-06T16:13:58.177437273-06:00" level=error msg="Container ID (876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062) does not exist" arch=amd64 command=delete container=876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062 name=kata-runtime pid=39721 source=runtime
time="2019-03-06T16:13:58.238794533-06:00" level=error msg="Container ID (876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062) does not exist" arch=amd64 command=delete container=876427d056a8091934418ea14bd2a07b8a659a013be1cc0c5daed42cb3453062 name=kata-runtime pid=39737 source=runtime
time="2019-03-06T16:39:36.592385359-06:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 name=kata-runtime pid=40324 source=virtcontainers subsystem=kata_agent
time="2019-03-06T16:39:36.595663768-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 error="open /run/vc/sbs/3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60/devices.json: no such file or directory" name=kata-runtime pid=40324 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 sandboxid=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=virtcontainers subsystem=sandbox
time="2019-03-06T16:39:57.702302349-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 name=kata-runtime pid=40324 source=runtime
time="2019-03-06T16:39:57.740269694-06:00" level=error msg="Container ID (3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60) does not exist" arch=amd64 command=delete container=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 name=kata-runtime pid=40393 source=runtime
time="2019-03-06T16:39:57.794701913-06:00" level=error msg="Container ID (3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60) does not exist" arch=amd64 command=delete container=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 name=kata-runtime pid=40407 source=runtime
time="2019-03-06T16:48:52.347437154-06:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54 name=kata-runtime pid=40731 source=virtcontainers subsystem=kata_agent
time="2019-03-06T16:48:52.350702381-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54 error="open /run/vc/sbs/4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54/devices.json: no such file or directory" name=kata-runtime pid=40731 sandbox=4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54 sandboxid=4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54 source=virtcontainers subsystem=sandbox
time="2019-03-06T16:49:13.430396494-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54 name=kata-runtime pid=40731 source=runtime
time="2019-03-06T16:49:13.468943779-06:00" level=error msg="Container ID (4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54) does not exist" arch=amd64 command=delete container=4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54 name=kata-runtime pid=40801 source=runtime
time="2019-03-06T16:49:13.526304341-06:00" level=error msg="Container ID (4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54) does not exist" arch=amd64 command=delete container=4c5ccdd6687a2b1da6b575995a6cbc4bfdbec4c3218f6b181e90c0cc6b587c54 name=kata-runtime pid=40818 source=runtime
time="2019-03-06T16:50:30.011541968-06:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a name=kata-runtime pid=42267 source=virtcontainers subsystem=kata_agent
time="2019-03-06T16:50:30.014809936-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a error="open /run/vc/sbs/e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a/devices.json: no such file or directory" name=kata-runtime pid=42267 sandbox=e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a sandboxid=e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a source=virtcontainers subsystem=sandbox
time="2019-03-06T16:50:51.110720186-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a name=kata-runtime pid=42267 source=runtime
time="2019-03-06T16:50:51.14885632-06:00" level=error msg="Container ID (e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a) does not exist" arch=amd64 command=delete container=e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a name=kata-runtime pid=42334 source=runtime
time="2019-03-06T16:50:51.208266618-06:00" level=error msg="Container ID (e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a) does not exist" arch=amd64 command=delete container=e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a name=kata-runtime pid=42350 source=runtime
time="2019-03-06T16:52:04.174467212-06:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=3628042044ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67 name=kata-runtime pid=43515 source=virtcontainers subsystem=kata_agent
time="2019-03-06T16:52:04.177716154-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=3628042044ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67 error="open /run/vc/sbs/3628042044ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67/devices.json: no such file or directory" name=kata-runtime pid=43515 sandbox=3628042044ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67 sandboxid=3628042044ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67 source=virtcontainers subsystem=sandbox
time="2019-03-06T16:52:25.272339774-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=3628042044ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67 name=kata-runtime pid=43515 source=runtime
time="2019-03-06T16:52:25.310539353-06:00" level=error msg="Container ID<PHONE_NUMBER>ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67) does not exist" arch=amd64 command=delete container=3628042044ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67 name=kata-runtime pid=43584 source=runtime
time="2019-03-06T16:52:25.36422168-06:00" level=error msg="Container ID<PHONE_NUMBER>ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67) does not exist" arch=amd64 command=delete container=3628042044ab4213af7ef33b7f9c7f0838b4a12cb0e5a824005de27ae2af8c67 name=kata-runtime pid=43600 source=runtime
time="2019-03-06T16:57:26.980282035-06:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f name=kata-runtime pid=44634 source=virtcontainers subsystem=kata_agent
time="2019-03-06T16:57:26.983583141-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f error="open /run/vc/sbs/bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f/devices.json: no such file or directory" name=kata-runtime pid=44634 sandbox=bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f sandboxid=bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f source=virtcontainers subsystem=sandbox
time="2019-03-06T16:57:48.062311978-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f name=kata-runtime pid=44634 source=runtime
time="2019-03-06T16:57:48.100382657-06:00" level=error msg="Container ID (bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f) does not exist" arch=amd64 command=delete container=bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f name=kata-runtime pid=44700 source=runtime
time="2019-03-06T16:57:48.151752064-06:00" level=error msg="Container ID (bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f) does not exist" arch=amd64 command=delete container=bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f name=kata-runtime pid=44718 source=runtime
time="2019-03-06T17:35:23.508304629-06:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e name=kata-runtime pid=23484 source=virtcontainers subsystem=kata_agent
time="2019-03-06T17:35:23.511563897-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e error="open /run/vc/sbs/ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e/devices.json: no such file or directory" name=kata-runtime pid=23484 sandbox=ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e sandboxid=ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e source=virtcontainers subsystem=sandbox
time="2019-03-06T17:35:44.582393645-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e name=kata-runtime pid=23484 source=runtime
time="2019-03-06T17:35:44.620371151-06:00" level=error msg="Container ID (ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e) does not exist" arch=amd64 command=delete container=ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e name=kata-runtime pid=23553 source=runtime
time="2019-03-06T17:35:44.674762661-06:00" level=error msg="Container ID (ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e) does not exist" arch=amd64 command=delete container=ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e name=kata-runtime pid=23569 source=runtime
time="2019-03-06T18:04:08.788412728-06:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e name=kata-runtime pid=47385 source=virtcontainers subsystem=kata_agent
time="2019-03-06T18:04:08.791728604-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e error="open /run/vc/sbs/244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e/devices.json: no such file or directory" name=kata-runtime pid=47385 sandbox=244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e sandboxid=244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e source=virtcontainers subsystem=sandbox
time="2019-03-06T18:04:29.892048131-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e name=kata-runtime pid=47385 source=runtime
time="2019-03-06T18:04:29.928946326-06:00" level=error msg="Container ID (244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e) does not exist" arch=amd64 command=delete container=244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e name=kata-runtime pid=47456 source=runtime
time="2019-03-06T18:04:29.992183667-06:00" level=error msg="Container ID (244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e) does not exist" arch=amd64 command=delete container=244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e name=kata-runtime pid=47473 source=runtime
time="2019-03-07T16:49:22.061375921-06:00" level=debug msg="Could not retrieve anything from storage" arch=amd64 command=create container=abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836 name=kata-runtime pid=4668 source=virtcontainers subsystem=kata_agent
time="2019-03-07T16:49:22.064810171-06:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836 error="open /run/vc/sbs/abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836/devices.json: no such file or directory" name=kata-runtime pid=4668 sandbox=abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836 sandboxid=abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836 source=virtcontainers subsystem=sandbox
time="2019-03-07T16:49:43.156520558-06:00" level=error msg="Failed to check if grpc server is working: rpc error: code = Unavailable desc = transport is closing" arch=amd64 command=create container=abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836 name=kata-runtime pid=4668 source=runtime
time="2019-03-07T16:49:43.195171029-06:00" level=error msg="Container ID (abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836) does not exist" arch=amd64 command=delete container=abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836 name=kata-runtime pid=4735 source=runtime
time="2019-03-07T16:49:43.248791511-06:00" level=error msg="Container ID (abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836) does not exist" arch=amd64 command=delete container=abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836 name=kata-runtime pid=4755 source=runtime

Proxy logs
Recent proxy problems found in system journal:
time="2019-03-06T16:39:41.566554605-06:00" level=info msg="[    2.839589] systemd[99]: Failed to add rule for system call ftime() / -10013, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.568270247-06:00" level=info msg="[    2.841261] systemd[99]: Failed to add rule for system call ssetmask() / -10061, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.569942351-06:00" level=info msg="[    2.842978] systemd[99]: Failed to add rule for system call break() / -10003, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.571605896-06:00" level=info msg="[    2.844649] systemd[99]: Failed to add rule for system call rtas() / -10187, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.573278583-06:00" level=info msg="[    2.846312] systemd[99]: Failed to add rule for system call prof() / -10039, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.575026323-06:00" level=info msg="[    2.847981] systemd[99]: Failed to add rule for system call create_module() / 174, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.576688271-06:00" level=info msg="[    2.849730] systemd[99]: Failed to add rule for system call _sysctl() / 156, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.57837796-06:00" level=info msg="[    2.851398] systemd[99]: Failed to add rule for system call vm86old() / -10072, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.580234529-06:00" level=info msg="[    2.853086] systemd[99]: Failed to add rule for system call s390_pci_mmio_write() / -10198, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.582085611-06:00" level=info msg="[    2.854944] systemd[99]: Failed to add rule for system call s390_runtime_instr() / -10196, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.583746284-06:00" level=info msg="[    2.856791] systemd[99]: Failed to add rule for system call gtty() / -10022, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.58542198-06:00" level=info msg="[    2.858458] systemd[99]: Failed to add rule for system call vm86() / -10071, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.58707899-06:00" level=info msg="[    2.860130] systemd[99]: Failed to add rule for system call mpx() / -10030, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.588740017-06:00" level=info msg="[    2.861787] systemd[99]: Failed to add rule for system call stime() / -10064, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.590406742-06:00" level=info msg="[    2.863447] systemd[99]: Failed to add rule for system call vserver() / 236, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.592093244-06:00" level=info msg="[    2.865106] systemd[99]: Failed to add rule for system call spu_run() / -10189, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.593872083-06:00" level=info msg="[    2.866792] systemd[99]: Failed to add rule for system call pciconfig_read() / -10087, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.595581682-06:00" level=info msg="[    2.868581] systemd[99]: Failed to add rule for system call sgetmask() / -10053, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.598210771-06:00" level=info msg="[    2.871227] systemd[99]: Failed to add rule for system call ulimit() / -10069, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.599861991-06:00" level=info msg="[    2.872915] systemd[99]: Failed to add rule for system call stty() / -10065, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.601553562-06:00" level=info msg="[    2.874575] systemd[99]: Failed to add rule for system call profil() / -10040, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.603260632-06:00" level=info msg="[    2.876256] systemd[99]: Failed to add rule for system call bdflush() / -10002, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.605097184-06:00" level=info msg="[    2.877963] systemd[99]: Failed to add rule for system call s390_pci_mmio_read() / -10197, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.606905096-06:00" level=info msg="[    2.879797] systemd[99]: Failed to add rule for system call pciconfig_iobase() / -10086, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.608693873-06:00" level=info msg="[    2.881612] systemd[99]: Failed to add rule for system call switch_endian() / -10191, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.610501774-06:00" level=info msg="[    2.883397] systemd[99]: Failed to add rule for system call pciconfig_write() / -10088, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.61218233-06:00" level=info msg="[    2.885215] systemd[99]: Failed to add rule for system call lock() / -10027, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.613871209-06:00" level=info msg="[    2.886885] systemd[99]: Failed to add rule for system call umount() / -10070, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.615537224-06:00" level=info msg="[    2.888583] systemd[99]: Failed to add rule for system call idle() / -10023, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.617208518-06:00" level=info msg="[    2.890239] systemd[99]: Failed to add rule for system call ftime() / -10013, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.618915772-06:00" level=info msg="[    2.891911] systemd[99]: Failed to add rule for system call ssetmask() / -10061, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.620577872-06:00" level=info msg="[    2.893615] systemd[99]: Failed to add rule for system call break() / -10003, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.622233995-06:00" level=info msg="[    2.895283] systemd[99]: Failed to add rule for system call rtas() / -10187, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.62390369-06:00" level=info msg="[    2.896938] systemd[99]: Failed to add rule for system call prof() / -10039, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.625606581-06:00" level=info msg="[    2.898608] systemd[99]: Failed to add rule for system call vm86old() / -10072, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.627461093-06:00" level=info msg="[    2.900309] systemd[99]: Failed to add rule for system call s390_pci_mmio_write() / -10198, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.629306888-06:00" level=info msg="[    2.902166] systemd[99]: Failed to add rule for system call s390_runtime_instr() / -10196, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.630979347-06:00" level=info msg="[    2.904012] systemd[99]: Failed to add rule for system call gtty() / -10022, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.632627353-06:00" level=info msg="[    2.905673] systemd[99]: Failed to add rule for system call vm86() / -10071, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.634284527-06:00" level=info msg="[    2.907332] systemd[99]: Failed to add rule for system call mpx() / -10030, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.635965322-06:00" level=info msg="[    2.908988] systemd[99]: Failed to add rule for system call stime() / -10064, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.637665187-06:00" level=info msg="[    2.910669] systemd[99]: Failed to add rule for system call spu_run() / -10189, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.63946661-06:00" level=info msg="[    2.912368] systemd[99]: Failed to add rule for system call pciconfig_read() / -10087, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:41.641169824-06:00" level=info msg="[    2.914170] systemd[99]: Failed to add rule for system call sgetmask() / -10053, ignoring: Numerical argument out of domain\n" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=agent
time="2019-03-06T16:39:57.66980931-06:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60/kata.sock: use of closed network connection" name=kata-proxy pid=40379 sandbox=3cf04bd375569f41beeee70997c27029ee0de32c454e176d1ea5d9d05a55ae60 source=proxy
time="2019-03-06T16:50:51.083028929-06:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a/proxy.sock: use of closed network connection" name=kata-proxy pid=42317 sandbox=e45d31ba14d3320df61cb04986a7776e95540209e843703fd00d1ee8d1f12b3a source=proxy
time="2019-03-06T16:57:48.033289806-06:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f/kata.sock: use of closed network connection" name=kata-proxy pid=44684 sandbox=bef6fa36c9d96e72937f6aa13f9b3f5db7e87b2d8a12ed6c983a7af09321c03f source=proxy
time="2019-03-06T17:35:44.558122344-06:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e/kata.sock: use of closed network connection" name=kata-proxy pid=23535 sandbox=ff9f197650fe917b707b87fd8b67c17f829b8d906fc3623ae12d011f10db147e source=proxy
time="2019-03-06T18:04:29.855432473-06:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e/kata.sock: use of closed network connection" name=kata-proxy pid=47439 sandbox=244294e254008436db701f132faed90336d592ea2644190558b363142237fe0e source=proxy
time="2019-03-07T16:49:43.124244317-06:00" level=fatal msg="failed to handle exit signal" error="close unix @->/run/vc/vm/abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836/kata.sock: use of closed network connection" name=kata-proxy pid=4719 sandbox=abace9ed4d97112d9357eb005c03e454f6758b62d1acc272ac6e4ef56c2da836 source=proxy

Shim logs
Recent shim problems found in system journal:
time="2019-02-28T16:23:48.594514768-06:00" level=info msg="copy stdout failed" container=5d981f014864b35297af16c7e85d7d3d0206fbd1cc7eac70fac57d1717e21940 error="rpc error: code = Unknown desc = read /dev/ptmx: input/output error" exec-id=5d981f014864b35297af16c7e85d7d3d0206fbd1cc7eac70fac57d1717e21940 name=kata-shim pid=1 source=shim
time="2019-02-28T16:56:29.476344186-06:00" level=info msg="copy stdout failed" container=3e6da50dd1ed0563305ee5793ed7b8337a9ed3bf0bb8637bee8fd8af145f0751 error="rpc error: code = Unavailable desc = transport is closing" exec-id=3e6da50dd1ed0563305ee5793ed7b8337a9ed3bf0bb8637bee8fd8af145f0751 name=kata-shim pid=1 source=shim
time="2019-02-28T16:56:29.477439958-06:00" level=error msg="failed waiting for process" container=3e6da50dd1ed0563305ee5793ed7b8337a9ed3bf0bb8637bee8fd8af145f0751 error="rpc error: code = Unavailable desc = transport is closing" exec-id=3e6da50dd1ed0563305ee5793ed7b8337a9ed3bf0bb8637bee8fd8af145f0751 name=kata-shim pid=1 source=shim

Throttler logs
No recent throttler problems found in system journal.

Container manager details
Have docker
Docker
Output of "docker version":
Client:
 Version:         1.13.1
 API version:     1.26
 Package version: docker-1.13.1-65.git1185cfd.fc29.x86_64
 Go version:      go1.11.5
 Git commit:      1185cfd/1.13.1
 Built:           Tue Feb 12 17:46:58 2019
 OS/Arch:         linux/amd64

Server:
 Version:         1.13.1
 API version:     1.26 (minimum version 1.12)
 Package version: docker-1.13.1-65.git1185cfd.fc29.x86_64
 Go version:      go1.11.5
 Git commit:      1185cfd/1.13.1
 Built:           Tue Feb 12 17:46:58 2019
 OS/Arch:         linux/amd64
 Experimental:    false

Output of "docker info":
Containers: 93
 Running: 0
 Paused: 0
 Stopped: 93
Images: 44
Server Version: 1.13.1
Storage Driver: overlay2
 Backing Filesystem: xfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: kata-runtime oci runc
Default Runtime: oci
Init Binary: /usr/libexec/docker/docker-init-current
containerd version:  (expected: aa8187dbd3b7ad67d8e5e3a15115d3eef43a7ed1)
runc version: N/A (expected: 9df8b306d01f59d3a8029be411de015b7304dd8f)
init version: N/A (expected: 949e6facb77383876aeff8a6944dde66b3089574)
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.20.11-200.fc29.x86_64
Operating System: Fedora 29 (Server Edition)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 2
CPUs: 56
Total Memory: 503.8 GiB
Name: hostname-redacted
ID: 4CFM:RVQE:L2KE:PBLP:ALAT:FE2G:VVEK:UXTN:R4WC:3DJP:YMFS:4WNE
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 17
 Goroutines: 23
 System Time: 2019-03-08T11:01:17.529939402-06:00
 EventsListeners: 0
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: true
Registries: docker.io (secure), registry.fedoraproject.org (secure), quay.io (secure), registry.access.redhat.com (secure), registry.centos.org (secure), docker.io (secure)

Output of "systemctl show docker":
Type=simple
Restart=on-abnormal
NotifyAccess=none
RestartUSec=100ms
TimeoutStartUSec=infinity
TimeoutStopUSec=1min 30s
RuntimeMaxUSec=infinity
WatchdogUSec=0
WatchdogTimestamp=Tue 2019-03-05 17:33:02 CST
WatchdogTimestampMonotonic=573065334
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=2576
ControlPID=0
FileDescriptorStoreMax=0
NFileDescriptorStore=0
StatusErrno=0
Result=success
UID=[not set]
GID=[not set]
NRestarts=0
ExecMainStartTimestamp=Tue 2019-03-05 17:33:02 CST
ExecMainStartTimestampMonotonic=573065295
ExecMainExitTimestampMonotonic=0
ExecMainPID=2576
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd-current ; argv[]=/usr/bin/dockerd-current -D --add-runtime oci=/usr/libexec/docker/docker-runc-current --add-runtime kata-runtime=/opt/virtiofs/bin/kata-runtime --default-runtime=oci --containerd /run/containerd.sock --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --init-path=/usr/libexec/docker/docker-init-current $OPTIONS $DOCKER_STORAGE_OPTIONS $DOCKER_NETWORK_OPTIONS $ADD_REGISTRY $BLOCK_REGISTRY $INSECURE_REGISTRY $REGISTRIES ; ignore_errors=no ; start_time=[Tue 2019-03-05 17:33:02 CST] ; stop_time=[n/a] ; pid=2576 ; code=(null) ; status=0/0 }
ExecReload={ path=/bin/kill ; argv[]=/bin/kill -s HUP $MAINPID ; ignore_errors=no ; start_time=[n/a] ; stop_time=[n/a] ; pid=0 ; code=(null) ; status=0/0 }
Slice=system.slice
ControlGroup=/system.slice/docker.service
MemoryCurrent=607318016
CPUUsageNSec=[not set]
TasksCurrent=78
IPIngressBytes=18446744073709551615
IPIngressPackets=18446744073709551615
IPEgressBytes=18446744073709551615
IPEgressPackets=18446744073709551615
Delegate=no
CPUAccounting=no
CPUWeight=[not set]
StartupCPUWeight=[not set]
CPUShares=[not set]
StartupCPUShares=[not set]
CPUQuotaPerSecUSec=infinity
IOAccounting=no
IOWeight=[not set]
StartupIOWeight=[not set]
BlockIOAccounting=no
BlockIOWeight=[not set]
StartupBlockIOWeight=[not set]
MemoryAccounting=yes
MemoryLow=0
MemoryHigh=infinity
MemoryMax=infinity
MemorySwapMax=infinity
MemoryLimit=infinity
DevicePolicy=auto
TasksAccounting=yes
TasksMax=8192
IPAccounting=no
Environment=GOTRACEBACK=crash
EnvironmentFiles=/run/containers/registries.conf (ignore_errors=no)
EnvironmentFiles=/etc/sysconfig/docker (ignore_errors=yes)
EnvironmentFiles=/etc/sysconfig/docker-storage (ignore_errors=yes)
EnvironmentFiles=/etc/sysconfig/docker-network (ignore_errors=yes)
UMask=0022
LimitCPU=infinity
LimitCPUSoft=infinity
LimitFSIZE=infinity
LimitFSIZESoft=infinity
LimitDATA=infinity
LimitDATASoft=infinity
LimitSTACK=infinity
LimitSTACKSoft=8388608
LimitCORE=infinity
LimitCORESoft=infinity
LimitRSS=infinity
LimitRSSSoft=infinity
LimitNOFILE=1048576
LimitNOFILESoft=1048576
LimitAS=infinity
LimitASSoft=infinity
LimitNPROC=1048576
LimitNPROCSoft=1048576
LimitMEMLOCK=16777216
LimitMEMLOCKSoft=16777216
LimitLOCKS=infinity
LimitLOCKSSoft=infinity
LimitSIGPENDING=2063406
LimitSIGPENDINGSoft=2063406
LimitMSGQUEUE=819200
LimitMSGQUEUESoft=819200
LimitNICE=0
LimitNICESoft=0
LimitRTPRIO=0
LimitRTPRIOSoft=0
LimitRTTIME=infinity
LimitRTTIMESoft=infinity
OOMScoreAdjust=0
Nice=0
IOSchedulingClass=0
IOSchedulingPriority=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardInputData=
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SyslogLevel=6
SyslogFacility=3
LogLevelMax=-1
SecureBits=0
CapabilityBoundingSet=cap_chown cap_dac_override cap_dac_read_search cap_fowner cap_fsetid cap_kill cap_setgid cap_setuid cap_setpcap cap_linux_immutable cap_net_bind_service cap_net_broadcast cap_net_admin cap_net_raw cap_ipc_lock cap_ipc_owner cap_sys_module cap_sys_rawio cap_sys_chroot cap_sys_ptrace cap_sys_pacct cap_sys_admin cap_sys_boot cap_sys_nice cap_sys_resource cap_sys_time cap_sys_tty_config cap_mknod cap_lease cap_audit_write cap_audit_control cap_setfcap cap_mac_override cap_mac_admin cap_syslog cap_wake_alarm cap_block_suspend
AmbientCapabilities=
DynamicUser=no
RemoveIPC=no
MountFlags=
PrivateTmp=no
PrivateDevices=no
ProtectKernelTunables=no
ProtectKernelModules=no
ProtectControlGroups=no
PrivateNetwork=no
PrivateUsers=no
PrivateMounts=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
UtmpMode=init
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
LockPersonality=no
RuntimeDirectoryPreserve=no
RuntimeDirectoryMode=0755
StateDirectoryMode=0755
CacheDirectoryMode=0755
LogsDirectoryMode=0755
ConfigurationDirectoryMode=0755
MemoryDenyWriteExecute=no
RestrictRealtime=no
RestrictNamespaces=no
MountAPIVFS=no
KeyringMode=private
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=registries.service sysinit.target rhel-push-plugin.socket system.slice docker-containerd.service
Wants=docker-storage-setup.service
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=shutdown.target multi-user.target
After=sysinit.target systemd-journald.socket network.target registries.service basic.target system.slice docker-containerd.service docker-storage-setup.service
Documentation=http://docs.docker.com
Description=Docker Application Container Engine
LoadState=loaded
ActiveState=active
SubState=running
FragmentPath=/usr/lib/systemd/system/docker.service
DropInPaths=/etc/systemd/system/docker.service.d/kata-containers.conf
UnitFileState=enabled
UnitFilePreset=disabled
StateChangeTimestamp=Tue 2019-03-05 17:33:02 CST
StateChangeTimestampMonotonic=573065335
InactiveExitTimestamp=Tue 2019-03-05 17:33:02 CST
InactiveExitTimestampMonotonic=573065335
ActiveEnterTimestamp=Tue 2019-03-05 17:33:02 CST
ActiveEnterTimestampMonotonic=573065335
ActiveExitTimestamp=Tue 2019-03-05 17:33:02 CST
ActiveExitTimestampMonotonic=572846544
InactiveEnterTimestamp=Tue 2019-03-05 17:33:02 CST
InactiveEnterTimestampMonotonic=572867496
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
NeedDaemonReload=no
JobTimeoutUSec=infinity
JobRunningTimeoutUSec=infinity
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Tue 2019-03-05 17:33:02 CST
ConditionTimestampMonotonic=573064232
AssertTimestamp=Tue 2019-03-05 17:33:02 CST
AssertTimestampMonotonic=573064232
Transient=no
Perpetual=no
StartLimitIntervalUSec=10s
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
SuccessAction=none
InvocationID=b28fb9401e324179a3a65593f0647771
CollectMode=inactive

No kubectl

Packages
No dpkg
Have rpm
Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-ksm-throttler|kata-containers-image|linux-container|qemu-)"":

Hi @dylanzr - I suspect you cannot do the mknod as by default the container will have limited linux system capabilities. You probably want to add a --cap-add=MKNOD to the container run command:
https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities
and see if that gets you further.
Ultimately though, I guess we would want to be doing this outside the container workload, and maybe in the VM guest 'mini-os', before the container is launched. In k8s maybe it would be done as a priv container run beside the workload. I'll leave those thoughts to @mcastelino and @amshinde

Hello @grahamwhaley, thanks for the reply. I might have been unclear, but the output in the results is in the vm guest 'mini-os' via the debug console, rather than in the container itself.

@dylanzr - ah, thanks. Hmm, so, I suspect the rootfs is mounted as ro (as indicated by the message - you could check via mount at that command prompt). So, you probably need to have the device node made in the roofs itself by the rootfs.sh. How that is done might depend on which base distro is being used for the rootfs. I'll leave @jcvenegas to add more details - he's the expert on that code ;-)

@dylanzr If you are using the debug console, I think you are not seeing the /dev/ptp0 device because of this line:
https://github.com/kata-containers/documentation/blame/master/Developer-Guide.md#L649
Have you set PrivateDevices=yes line in your debug service? If you comment out that line, you should be able to see all the guest devices on the debug console.
@grahamwhaley I am not able to recall why we have that in the debug service. Do you remember?

@dylanzr I will  take a look at #1279 to see if we can package chrony service in our guest to manage time synchronization.

@amshinde - good catch! https://github.com/kata-containers/documentation/pull/404 raised to remove that option from the dev guide.

Thanks, all!
I'll try to get a dev console spun-up without the PrivateDevices option later today.

Great - thanks @dylanzr. And thanks for the inspiration for https://github.com/kata-containers/runtime/pull/1387 ;)


Segfault when calling insert_calendar with String-key hash

Not sure if this an issue with the gem itself, but I can consistently reproduce this issue:
https://bugs.ruby-lang.org/issues/11675
If the hash keys are symbols, it throws ArgumentError (unknown keyword: summary), which is a relevant error here.

The segfault itself is a ruby issue. That said, the README is clear in saying hash keys must be symbols, not strings.


Bump target to iOS7, introduce nullability, always async, and separate storage from queue

Hi! Have a look please
I've updated README accordingly. Idea is:

introduce QueueJob to avoid direct using NSDictinary for creating jobs (plan to add to Job max retry times, expiration date, fire date, etc)
introduce nullability to prepare for Swift migration
decoupling storage from queue using EDQueuePersistentStorage brotocoli :)
adding some basic tests on top of that (to be continued)

Very cool. Taking a look now.

Overall this is great. Thanks for pulling this together @gelosi . I left you a few comments and notes for discussion.

Hi Andrew
Cool! Thank you for a quick feedback. This is a very start. I will try to offer some idea on 'built-in' persistent storage. As I suppose apps which using  already some sqlite wrapper different from FMDB might stay aside. That is my approach. Ideally - having ready-to go fmdb submodule (as default dependency). And reduce persistent storage interface requirements to CRUD :)
—
RO
On Fri, Feb 19, 2016 at 7:04 PM, Andrew Sliwinski
<EMAIL_ADDRESS>wrote:

Overall this is great. Thanks for pulling this together @gelosi . I left you a few comments and notes for discussion.
Reply to this email directly or view it on GitHub:
https://github.com/thisandagain/queue/pull/22#issuecomment-186334292

@thisandagain so, shaping better approach. Have a look please.


gpu version int_nbit_split_embedding_codegen_lookup_function not support indices and offsets with uint64 dtype

This PR removes uint32 indices protection in quant/embedding_modules.py. Nevertheless, when indices and offsets inputs of uint64 dtype are provided, int_nbit_split_embedding_codegen_lookup_function triggers a RuntimeError: expected scalar type Int but found Long on the GPU. Would it be possible to add support for the uint64 dtype on GPU devices?

It what cases would it be necessary to use uint64?

It what cases would it be necessary to use uint64?

In certain scenarios, the uint32 data type is insufficient to contain the indices for user_id and several combo feature.

@tiankongdeguiji Hi, let me bring this to the FBGEMM team's attention and get back to you.


Update README.md

update locale props in readme

reasoning: this should be included since the component supports locale as a prop and is not documented within the readme

Coverage remained the same at 97.368% when pulling d428fb0d27ffc5694f4d59745f15e6a2e018ce53 on denistsoi:patch-2 into 2a209bd4f11a84ff4543fbde930fed60dcbc0f68 on xgfe:master.


Test boundary overrun still throws exception

In an async Task test, the following exception was thrown:
The active test run was aborted. Reason: Test host process crashed : Unhandled exception. System.AggregateException: An error occurred while writing to logger(s). (There is no currently active test.)
 ---> System.InvalidOperationException: There is no currently active test.
   at Xunit.Sdk.TestOutputHelper.QueueTestOutput(String output) in /_/src/xunit.execution/Sdk/Frameworks/TestOutputHelper.cs:line 61
   at Neovolve.Logging.Xunit.TestOutputLogger.WriteLog(LogLevel logLevel, EventId eventId, String message, Exception exception)
   at Neovolve.Logging.Xunit.TestOutputLogger.WriteLogEntry[TState](LogLevel logLevel, EventId eventId, TState state, String message, Exception exception, Func`3 formatter)
   at Neovolve.Logging.Xunit.FilterLogger.Log[TState](LogLevel logLevel, EventId eventId, TState state, Exception exception, Func`3 formatter)
   at Microsoft.Extensions.Logging.Logger.<Log>g__LoggerLog|14_0[TState](LogLevel logLevel, EventId eventId, ILogger logger, Exception exception, Func`3 formatter, List`1& exceptions, TState& state)
   --- End of inner exception stack trace ---
   at Microsoft.Extensions.Logging.Logger.ThrowLoggingError(List`1 exceptions)
   at Microsoft.Extensions.Logging.Logger.Log[TState](LogLevel logLevel, EventId eventId, TState state, Exception exception, Func`3 formatter)
   at Microsoft.Extensions.Logging.Logger`1.Microsoft.Extensions.Logging.ILogger.Log[TState](LogLevel logLevel, EventId eventId, TState state, Exception exception, Func`3 formatter)
   at Neovolve.Logging.Xunit.CacheLogger.WriteLogEntry[TState](LogLevel logLevel, EventId eventId, TState state, String message, Exception exception, Func`3 formatter)
   at Neovolve.Logging.Xunit.FilterLogger.Log[TState](LogLevel logLevel, EventId eventId, TState state, Exception exception, Func`3 formatter)
   at Microsoft.Extensions.Logging.LoggerMessage.<>c__DisplayClass10_0`1.<Define>g__Log|0(ILogger logger, T1 arg1, Exception exception)

The existing try/catch should catch any exception rather than just InvalidOperationException.

In this case, the exception was thrown because the logging configuration allowed it


Breast Cancer Prediction

💥 Proposal
I am a GSSoC Contributor, I want to add new project under Machine Learning Section that is Breast Cancer Prediction
I will be importing the dataset from the scikit-learn library and will be using logistic regression algorithm for this project, Please assign this issue to me.

Hi,
I'm Babar Rasheed (Contributor GSSOC'23).
I will be using the sci-kit-learn datasets for this project. I can give you my best as a data scientist.

@adityabachu  - you can go ahead! We are assigning you 21 days for this project, after which it will be assigned to someone else if not completed. All the best!
Name the file as: algorithm_dataset.ipynb and link it in the readme of the labeled directory as algorithm - dataset.


Fix lighting_dirty flag bug

In rare circumstances, changing the geometry data attached to an instance, there was the opportunity for the lighting_dirty flag to get out of sync, which could lead to access to a stale light RID, and warnings or worse.
This PR fixes the problem by ensuring the lighting is always updated on the instance when first adding GeometryData.
Fixes #41360
Conditions for bug

On the same iteration, a light is removed, which unpairs the Light and Geometry data, and sets lighting_dirty to true
Before the instance has the opportunity to have its lighting list updated, the GeometryData is deleted and replaced by new GeometryData. The flag defaults to false, and thus the instance lighting is never updated.
When the instance lighting list is later hit, it reads the RID for the deleted light, and flags warnings etc.

Notes

This was incredibly difficult to find for such a simple bug :grin: ... see the issue for details of the debugging process (a good day and half on this).

Reproduction Project
Run this project before and after the PR (click loads of times with the mouse to add the omni lights):
OmnilightBug_Cutdown4.zip

Thanks!


AccessbilityInfo error from react-native 0.56

Environment
React Native Environment Info:
System:
OS: Windows 10
CPU: x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 6.59 GB / 11.91 GB
Binaries:
Yarn: yarn install v0.27.5
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.64s. - C:\Users\Jayric Mok\AppData\Roaming\npm\yarn.CMD
npm: 6.1.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-173.4720617
Description
I tried to create a new react native project v 0.56, but stuck at this error when metro bundle starting.
Loading dependency graph, done.
error: bundling failed: Error: Unable to resolve module AccessibilityInfo from C:\RN\TESTProject\node_modules\react-native\Libraries\react-native\react-native-implementation.js: Module AccessibilityInfo does not exist in the Haste module map
This might be related to https://github.com/facebook/react-native/issues/4968
To resolve try the following:

Clear watchman watches: watchman watch-del-all.
Delete the node_modules folder: rm -rf node_modules && npm install.
Reset Metro Bundler cache: rm -rf /tmp/metro-bundler-cache-* or npm start -- --reset-cache.  4. Remove haste cache: rm -rf /tmp/haste-map-react-native-packager-*.
at ModuleResolver.resolveDependency (C:\RN\TESTProject\node_modules\metro\src\node-haste\DependencyGraph\ModuleResolution.js:167:1306)
at ResolutionRequest.resolveDependency (C:\RN\TESTProject\node_modules\metro\src\node-haste\DependencyGraph\ResolutionRequest.js:80:16)
at DependencyGraph.resolveDependency (C:\RN\TESTProject\node_modules\metro\src\node-haste\DependencyGraph.js:237:485)
at Object.resolve (C:\RN\TESTProject\node_modules\metro\src\lib\transformHelpers.js:116:25)
at dependencies.map.result (C:\RN\TESTProject\node_modules\metro\src\DeltaBundler\traverseDependencies.js:298:29)
at Array.map ()
at resolveDependencies (C:\RN\TESTProject\node_modules\metro\src\DeltaBundler\traverseDependencies.js:294:16)
at C:\RN\TESTProject\node_modules\metro\src\DeltaBundler\traverseDependencies.js:159:33
at Generator.next ()
at step (C:\RN\TESTProject\node_modules\metro\src\DeltaBundler\traverseDependencies.js:239:307)
BUNDLE  [android, dev] ....../index.js ░░░░░░░░░░░░░░░░ 1.1% (2/19), failed.

react-native version
react-native-cli: 2.0.1
react-native: 0.56.0
Package
{
  "name": "TESTProject",
  "version": "0.0.1",
  "private": true,
  "scripts": {
	"start": "node node_modules/react-native/local-cli/cli.js start",
	"test": "jest"
  },
  "dependencies": {
	"react": "16.4.1",
	"react-native": "0.56.0"
  },
  "devDependencies": {
	"babel-jest": "23.4.0",
	"babel-preset-react-native": "5",
	"jest": "23.4.1",
	"react-test-renderer": "16.4.1"
  },
  "jest": {
	"preset": "react-native"
  }
}

same here

Me too

Duplicate of #19953

me too

same here would anybody find the solution for it?

I found a way.   "react-native": "^0.56.0"  =>  "react-native": "^0.55.4" in package.json