kata will hang or stuck on running nginx on Ubuntu or Centos

kata will hang or stuck on running nginx on Ubuntu or centos with very high possibility
kata running on host as bare metal mode;
Kata runtime version:1.1.0 & 1.2.0
Host OS: Ubuntu: 16.04
Host OS: Centos: 7.3
nginx: 1.15.1 (nginx image is pulled from public image hub of docker.io)
Expected result
nginx running in kata container will never stuck or hang
Actual result
In Centos 7.3 or Ubuntu16.04,  kata container will hang or stuck after the nginx server being started more than 1 hour with very high possibility(more than 7 in 10;)
"docker stop" can not stop kata container;
"docker exec" can not enter kata container;
"kill -9" can not kill the kata container/runtime/ process;
docker & kata runtime will not response to any cmd;
need to reboot host os to restart the docker and kata;
There is never such issue if we switch runtime to runc to run the same nginx image;
Meta details
Paste the log and verify the same issue on kata 1.2.0:
Running kata-collect-data.sh version 1.2.0 (commit 0bcb32f) at 2018-08-31.13:53:55.157847694+0800.

Runtime is /bin/kata-runtime.
kata-env
Output of "/bin/kata-runtime kata-env":
[Meta]
  Version = "1.0.13"

[Runtime]
  Debug = false
  [Runtime.Version]
    Semver = "1.2.0"
    Commit = "0bcb32f"
    OCI = "1.0.1"
  [Runtime.Config]
    Path = "/usr/share/defaults/kata-containers/configuration.toml"

[Hypervisor]
  MachineType = "pc"
  Version = "QEMU emulator version 2.11.0\nCopyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers"
  Path = "/usr/bin/qemu-lite-system-x86_64"
  BlockDeviceDriver = "virtio-scsi"
  Msize9p = 8192
  Debug = false
  UseVSock = false

[Image]
  Path = "/usr/share/kata-containers/kata-containers-image_clearlinux_1.2.0_agent_fcfa054a757.img"

[Kernel]
  Path = "/usr/share/kata-containers/vmlinuz-<IP_ADDRESS>-135.1.container"
  Parameters = ""

[Initrd]
  Path = ""

[Proxy]
  Type = "kataProxy"
  Version = "kata-proxy version 1.2.0-1796218"
  Path = "/usr/libexec/kata-containers/kata-proxy"
  Debug = false

[Shim]
  Type = "kataShim"
  Version = "kata-shim version 1.2.0-0a37760"
  Path = "/usr/libexec/kata-containers/kata-shim"
  Debug = false

[Agent]
  Type = "kata"

[Host]
  Kernel = "3.10.0-862.3.2.el7.x86_64"
  Architecture = "amd64"
  VMContainerCapable = true
  [Host.Distro]
    Name = "CentOS Linux"
    Version = "7"
  [Host.CPU]
    Vendor = "GenuineIntel"
    Model = "Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz"

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

Runtime config file contents
Config file /etc/kata-containers/configuration.toml not found
Output of "cat "/usr/share/defaults/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 = "/usr/bin/qemu-lite-system-x86_64"
kernel = "/usr/share/kata-containers/vmlinuz.container"
image = "/usr/share/kata-containers/kata-containers.img"
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 = ""

# 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 = 2048

# 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 = 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

[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 = "/usr/libexec/kata-containers/kata-proxy"

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

[shim.kata]
path = "/usr/libexec/kata-containers/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.

[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.
internetworking_model="macvtap"

Image details
---
osbuilder:
  url: "https://github.com/kata-containers/osbuilder"
  version: "unknown"
rootfs-creation-time: "2018-08-13T22:51:39.765008919+0000Z"
description: "osbuilder rootfs"
file-format-version: "0.0.2"
architecture: "x86_64"
base-distro:
  name: "Clear"
  version: "24400"
  packages:
    default:
      - "iptables-bin"
      - "libudev0-shim"
      - "systemd"
    extra:

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

Initrd details
No initrd

Logfiles
Runtime logs
Recent runtime problems found in system journal:
time="2018-08-31T10:46:24.135592249+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae error="open /run/vc/sbs/a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae/devices.json: no such file or directory" name=kata-runtime pid=3826 sandbox=a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae sandboxid=a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae source=virtcontainers subsystem=sandbox
time="2018-08-31T13:26:57.646882091+08:00" level=error msg="Container a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae name=kata-runtime pid=15952 sandbox=a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae source=runtime
time="2018-08-31T13:26:57.695227659+08:00" level=error msg="Container a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae not ready, running or paused, cannot send a signal" arch=amd64 command=kill container=a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae name=kata-runtime pid=16016 sandbox=a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae source=runtime
time="2018-08-31T13:50:08.670452533+08:00" level=warning msg="fetch sandbox device failed" arch=amd64 command=create container=c140df3834e8db675926af8460b57cef246e750a1860dfd5d515cad259191766 error="open /run/vc/sbs/c140df3834e8db675926af8460b57cef246e750a1860dfd5d515cad259191766/devices.json: no such file or directory" name=kata-runtime pid=18283 sandbox=c140df3834e8db675926af8460b57cef246e750a1860dfd5d515cad259191766 sandboxid=c140df3834e8db675926af8460b57cef246e750a1860dfd5d515cad259191766 source=virtcontainers subsystem=sandbox

Proxy logs
Recent proxy problems found in system journal:
time="2018-08-31T13:26:57.618051166+08:00" level=fatal msg="channel error" error="accept unix /run/vc/sbs/a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae/proxy.sock: use of closed network connection" name=kata-proxy pid=3882 sandbox=a04b11bcef173cbd02b47c3d469b72a3c7123ec68b9647a8c0029472a4609cae source=proxy

Shim logs
No recent shim problems found in system journal.

Container manager details
Have docker
Docker
Output of "docker version":
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:23:03 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:25:29 2018
  OS/Arch:          linux/amd64
  Experimental:     false

Output of "docker info":
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 18.06.1-ce
Storage Driver: devicemapper
 Pool Name: docker1-thinpool
 Pool Blocksize: 524.3kB
 Base Device Size: 10.74GB
 Backing Filesystem: xfs
 Udev Sync Supported: true
 Data Space Used: 229.6MB
 Data Space Total: 29.88GB
 Data Space Available: 29.65GB
 Metadata Space Used: 118.8kB
 Metadata Space Total: 310.4MB
 Metadata Space Available: 310.3MB
 Thin Pool Minimum Free Space: 2.988GB
 Deferred Removal Enabled: true
 Deferred Deletion Enabled: true
 Deferred Deleted Device Count: 0
 Library Version: 1.02.146-RHEL7 (2018-01-22)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: kata-runtime runc
Default Runtime: kata-runtime
Init Binary: docker-init
containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e
runc version: 0bcb32f (expected: 69663f0bd4b60df09991c08812a60108003fa340)
init version: fec3683
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-862.3.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 15.27GiB
Name: localhost.localdomain
ID: OZTQ:BK7W:4HIC:MFGK:JTF3:5Y7H:PNJU:6EFK:67SH:FCFY:CJNG:KUJF
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 29
 Goroutines: 49
 System Time: 2018-08-31T13:53:55.47969715+08:00
 EventsListeners: 0
HTTP Proxy: http://child-prc.intel.com:913/
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Output of "systemctl show docker":
Type=notify
Restart=on-failure
NotifyAccess=main
RestartUSec=100ms
TimeoutStartUSec=0
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestamp=Fri 2018-08-31 13:49:09 CST
WatchdogTimestampMonotonic=12689068837
StartLimitInterval=60000000
StartLimitBurst=3
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=17885
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=success
ExecMainStartTimestamp=Fri 2018-08-31 13:49:08 CST
ExecMainStartTimestampMonotonic=12688097899
ExecMainExitTimestampMonotonic=0
ExecMainPID=17885
ExecMainCode=0
ExecMainStatus=0
ExecStart={ path=/usr/bin/dockerd ; argv[]=/usr/bin/dockerd -D --add-runtime kata-runtime=/usr/bin/kata-runtime --default-runtime=kata-runtime ; ignore_errors=no ; start_time=[Fri 2018-08-31 13:49:08 CST] ; stop_time=[n/a] ; pid=17885 ; 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=340971520
TasksCurrent=86
Delegate=yes
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
Environment=HTTP_PROXY=http://child-prc.intel.com:913/
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=18446744073709551615
LimitAS=18446744073709551615
LimitNPROC=18446744073709551615
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=62113
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=process
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=docker.service
Names=docker.service
Requires=basic.target
Wants=network-online.target system.slice
Conflicts=shutdown.target
Before=shutdown.target
After=systemd-journald.socket basic.target firewalld.service system.slice network-online.target
Documentation=https://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-container.conf
UnitFileState=disabled
UnitFilePreset=disabled
InactiveExitTimestamp=Fri 2018-08-31 13:49:08 CST
InactiveExitTimestampMonotonic=12688098378
ActiveEnterTimestamp=Fri 2018-08-31 13:49:09 CST
ActiveEnterTimestampMonotonic=12689068997
ActiveExitTimestamp=Fri 2018-08-31 13:49:07 CST
ActiveExitTimestampMonotonic=12687071866
InactiveEnterTimestamp=Fri 2018-08-31 13:49:08 CST
InactiveEnterTimestampMonotonic=12688079495
CanStart=yes
CanStop=yes
CanReload=yes
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Fri 2018-08-31 13:49:08 CST
ConditionTimestampMonotonic=12688097102
AssertTimestamp=Fri 2018-08-31 13:49:08 CST
AssertTimestampMonotonic=12688097102
Transient=no

Have kubectl
Kubernetes
Output of "kubectl version":
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:13:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Error from server (NotFound): the server could not find the requested resource

Output of "kubectl config view":
apiVersion: v1
clusters: []
contexts: []
current-context: ""
kind: Config
preferences: {}
users: []

Output of "systemctl show kubelet":
Type=simple
Restart=always
NotifyAccess=none
RestartUSec=10s
TimeoutStartUSec=1min 30s
TimeoutStopUSec=1min 30s
WatchdogUSec=0
WatchdogTimestampMonotonic=0
StartLimitInterval=0
StartLimitBurst=5
StartLimitAction=none
FailureAction=none
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
MainPID=0
ControlPID=0
FileDescriptorStoreMax=0
StatusErrno=0
Result=exit-code
ExecMainStartTimestamp=Fri 2018-08-31 13:53:49 CST
ExecMainStartTimestampMonotonic=12968309322
ExecMainExitTimestamp=Fri 2018-08-31 13:53:49 CST
ExecMainExitTimestampMonotonic=12968359830
ExecMainPID=18951
ExecMainCode=1
ExecMainStatus=255
ExecStart={ path=/usr/bin/kubelet ; argv[]=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_SYSTEM_PODS_ARGS $KUBELET_NETWORK_ARGS $KUBELET_DNS_ARGS $KUBELET_AUTHZ_ARGS $KUBELET_CADVISOR_ARGS $KUBELET_CGROUP_ARGS $KUBELET_CERTIFICATE_ARGS $KUBELET_EXTRA_ARGS ; ignore_errors=no ; start_time=[Fri 2018-08-31 13:53:49 CST] ; stop_time=[Fri 2018-08-31 13:53:49 CST] ; pid=18951 ; code=exited ; status=255 }
Slice=system.slice
MemoryCurrent=18446744073709551615
TasksCurrent=18446744073709551615
Delegate=no
CPUAccounting=no
CPUShares=18446744073709551615
StartupCPUShares=18446744073709551615
CPUQuotaPerSecUSec=infinity
BlockIOAccounting=no
BlockIOWeight=18446744073709551615
StartupBlockIOWeight=18446744073709551615
MemoryAccounting=no
MemoryLimit=18446744073709551615
DevicePolicy=auto
TasksAccounting=no
TasksMax=18446744073709551615
Environment=KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf\x20--kubeconfig=/etc/kubernetes/kubelet.conf KUBELET_SYSTEM_PODS_ARGS=--pod-manifest-path=/etc/kubernetes/manifests\x20--allow-privileged=true KUBELET_NETWORK_ARGS=--network-plugin=cni\x20--cni-conf-dir=/etc/cni/net.d\x20--cni-bin-dir=/opt/cni/bin KUBELET_DNS_ARGS=--cluster-dns=<IP_ADDRESS>\x20--cluster-domain=cluster.local KUBELET_AUTHZ_ARGS=--authorization-mode=Webhook\x20--client-ca-file=/etc/kubernetes/pki/ca.crt KUBELET_CADVISOR_ARGS=--cadvisor-port=0 KUBELET_CGROUP_ARGS=--cgroup-driver=cgroupfs KUBELET_CERTIFICATE_ARGS=--rotate-certificates=true\x20--cert-dir=/var/lib/kubelet/pki
UMask=0022
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=4096
LimitAS=18446744073709551615
LimitNPROC=62113
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=62113
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=journal
StandardError=inherit
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
AmbientCapabilities=0
MountFlags=0
PrivateTmp=no
PrivateNetwork=no
PrivateDevices=no
ProtectHome=no
ProtectSystem=no
SameProcessGroup=no
IgnoreSIGPIPE=yes
NoNewPrivileges=no
SystemCallErrorNumber=0
RuntimeDirectoryMode=0755
KillMode=control-group
KillSignal=15
SendSIGKILL=yes
SendSIGHUP=no
Id=kubelet.service
Names=kubelet.service
Requires=basic.target
Wants=system.slice
WantedBy=multi-user.target
Conflicts=shutdown.target
Before=multi-user.target shutdown.target
After=basic.target system.slice systemd-journald.socket
Documentation=http://kubernetes.io/docs/
Description=kubelet: The Kubernetes Node Agent
LoadState=loaded
ActiveState=activating
SubState=auto-restart
FragmentPath=/etc/systemd/system/kubelet.service
DropInPaths=/etc/systemd/system/kubelet.service.d/10-kubeadm.conf
UnitFileState=enabled
UnitFilePreset=disabled
InactiveExitTimestamp=Fri 2018-08-31 13:53:49 CST
InactiveExitTimestampMonotonic=12968367327
ActiveEnterTimestamp=Fri 2018-08-31 13:53:49 CST
ActiveEnterTimestampMonotonic=12968309373
ActiveExitTimestamp=Fri 2018-08-31 13:53:49 CST
ActiveExitTimestampMonotonic=12968360055
InactiveEnterTimestamp=Fri 2018-08-31 13:53:49 CST
InactiveEnterTimestampMonotonic=12968360055
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureJobMode=replace
IgnoreOnIsolate=no
IgnoreOnSnapshot=no
NeedDaemonReload=no
JobTimeoutUSec=0
JobTimeoutAction=none
ConditionResult=yes
AssertResult=yes
ConditionTimestamp=Fri 2018-08-31 13:53:49 CST
ConditionTimestampMonotonic=12968308505
AssertTimestamp=Fri 2018-08-31 13:53:49 CST
AssertTimestampMonotonic=12968308505
Transient=no

No crio

Packages
No dpkg
Have rpm
Output of "rpm -qa|egrep "(cc-oci-runtimecc-runtimerunv|kata-proxy|kata-runtime|kata-shim|kata-containers-image|linux-container|qemu-)"":
qemu-lite-data-2.11.0+git.a39e0b3e82-48.1.x86_64
qemu-vanilla-2.11.2+git.0982a56a55-46.1.x86_64
kata-linux-container-<IP_ADDRESS>-135.1.x86_64
kata-runtime-1.2.0+git.0bcb32f-47.1.x86_64
qemu-vanilla-data-2.11.2+git.0982a56a55-46.1.x86_64
qemu-vanilla-bin-2.11.2+git.0982a56a55-46.1.x86_64
kata-shim-1.2.0+git.0a37760-33.1.x86_64
kata-proxy-1.2.0+git.1796218-32.1.x86_64
qemu-lite-2.11.0+git.a39e0b3e82-48.1.x86_64
kata-shim-bin-1.2.0+git.0a37760-33.1.x86_64
kata-proxy-bin-1.2.0+git.1796218-32.1.x86_64
qemu-lite-bin-2.11.0+git.a39e0b3e82-48.1.x86_64
kata-containers-image-1.2.0-32.1.x86_64

Hi @zhiminghufighting - thanks for raising this!
Please could you paste the output of sudo kata-collect-data.sh into this issue as that will give us more information on the issue (particularly if you could recreate it with full debug enabled). Please check the output of that script before you paste it, to ensure there is no sensitive information in it too ;)

Sure, i am trying to reproduce it on kata 1.2.0 and check if there still exist.
Once issue is reproduced, i will run the .sh and paste the log to you.

/cc @egernst @GabyCT as they have both looked at this area with nginx/ab recently and may have some ideas already.

Do we have any new founds? thanks a lot!

Does it still exist when you use 1.2.0 or master?

I test nginx:latest with Kata runtime master on Centos: 7.4 for more than 1 hour and it works well.

I have tested nginx/ab with 1.2.0 extensively in the past. And did not see any issue.
@zhiminghufighting Can you provide more details?

@caoruidong, this issue will not be observed by just running a stable time.
Sometimes, kata nginx contianer run more than 12 or 24 hours, you can see nginx by "docker ps",
but if you use "docker stop xxxx" to stop it, it will no response;
or if you use "docker exec -ti xxxx /bin/bash" and you will fail to enter kata nginx;
This is only observed on centos 7.3 (3.10.0-862) and ubuntu 16.04.  It will not be oberserved on Debian 9.

@amshinde New founds:
On my centos 7.3(3.10.0-862), this issues will  be observed only by running with nginx image(pull from default docker hub).
No such issue can be observed when i use kata to launch centos/ubuntu/ images.

@zhiminghufighting  have you tried with use_vsock = true?  https://github.com/kata-containers/documentation/blob/master/VSocks.md#system-requirements

@zhiminghufighting Are you still experiencing this issue at all? If not, this issue may be stale and should be closed.


convert to reactjs project

i want to convert the https://github.com/jgraph/mxgraph project into reactjs completely and i dont know how to implement. i just want to import all JS files in a component that renders the graph. I hope you will respond me. Thanks in advance
PS: when i import all JS files, every function gets 'undefined'

Try : https://github.com/korbinzhao/mxgraph-editor

Thank you so much for considering ;)
Actually, i need the same toolbar and sidebar which is available in  the official mxgraph and that is the biggest problem to import now.
is there any easy way to  import the grapheditor/www/js/ files inside your react project?
Thanks in advance

maybe a start point:  https://github.com/korbinzhao/mxgraph-editor

Is this issue resolved?

Hi Dinesh,
Actually I am also having the same problem. Are you able solve this issue. If yes can you also mention how you added the same toolbar and sidebar in your react project.
Thanks in advance.

Hello @SandeepRCH  @dinesh-offl @davizucon ,
I wanted the same thing.. Any update about same toolbar and sidebar with react?
Thank you in advance.

Hello, mee too i'm trying to webpack the grapheditor example.
I'd like to avoid any particular framework and keep everything in plain js but unfortunately all questions and issue relate to Angular o react...
any suggestion is appreciated ;)


Updated Pause Menu

This branch resolves issue #129 with a refined and new sleek look to the pause menu! The pause menu can be opened and closed by pressing the escape key, on top of being able to select the new 'continue' option to return to the game to give the user some flexibility and freedom while playing! The options menu has also been changed to a separate scene as it gets reused more than once, so I thought it would be more efficient to simply use the same scene. There is also a main menu button that takes the player to the main menu before they're able to quit the game! All functional.

Can this please have a proper description for a pull request? With description, link to issues this will resolve, etc

I added a border as in design mockup # 1 and I would like some feedback for it as I thought the menu looked empty without some kind of box (balance is a design convention!) I also am not sure about the thickness of the box, and also the background. I was thinking about shrinking the dark background to be just for the pause box... Feedback much appreciated...

In PlanetDetection.cs Line 40 add   && Time.timeScale != 0 to the if statement


Fill the gap between poutine and semgrep rules

https://github.com/semgrep/semgrep-rules/blob/develop/yaml/github-actions/security/allowed-unsecure-commands.yaml
https://github.com/semgrep/semgrep-rules/blob/develop/yaml/github-actions/security/curl-eval.yaml
https://github.com/contributor-assistant/github-action/blob/master/.github/workflows/notify-about-new-pr-via-slack.yml#L17
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run

I have added workflow_run scenario here https://github.com/messypoutine/gravy-overflow/blob/main/.github/workflows/level1.yml#L34-L43

Create curl | bash rule in experiemental repo

Research epic on deno run , curl | X , etc.

Closed when we added insecure command


Change square bracket and strict directory condition

I think it would be better to use double square bracket in if condtion instead of single square bracket, and to use -d conditional option instead of -e.

Can't merge f80dafb because it doesn't work with git submodules. -e is used because .git is a regular file in submodules.

Sorry for this mistake. I fixed it. Can be merged?


ValueError('need more than 1 value to unpack',) in windows

Not able to save files in windows environment.
ValueError('need more than 1 value to unpack',)
db_file_storage/storage.py in _get_storage_attributes, line 70

This is easily fixed add
"import os"
to the top and then change line 70 from
mimetype_field, filename) = name.split('/')
to
mimetype_field, filename) = name.split(os.sep)

@geojacobm6 and @MrxTee
Unfortunately I can't test the lib in Windows or Mac at the moment.
After 54b920bef78cc176f1d3dd04a0c2a07c511dadeb and MrxTee's 34205bc818742374a531fe2126fd91dd355cb2c2, I believe that the problem should be fixed.
If possible, could you clone the repo and run python manage.py test inside the demo_and_tests directory so I can make sure the issue is fixed, please?

Thanks, it is working now.


Handle conflicting experiments when opening

When opening a trace with the same name as another experiment, the experiment
that contains it will have a conflict on the server. The client should
retry posting it with a different name until it succeeds or another
error occurs.
The title of the trace viewer should also be updated to represent the
actual name of the experiment.
Signed-off-by: Geneviève Bastien<EMAIL_ADDRESS>

This goes with Trace server commit: https://git.eclipse.org/r/#/c/163272/

I updated the patch, and also added the management of the trace conflict, even though there is no such conflicts anymore from the trace server, but if we add some, it will be handled here.


bsuite_tutorial.ipynb error - load bsuite environments as OpenAI gym-

Hey there!
Thanks for open sourcing this tool for understanding better behavior in RL agents  :)
There seems to be an error in the colab tutorial when executing load bsuite environments as OpenAI gym cell
#@title Simple to load bsuite environments as OpenAI gym

from bsuite.utils import gym_wrapper
raw_env = bsuite.load_from_id(bsuite_id='memory_len/0')
env = gym_wrapper.GymWrapper(raw_env)
isinstance(env, gym.Env)

might
env = gym_wrapper.GymWrapper(raw_env)

be
env = gym_wrapper.GymFromDMEnv(raw_env)

,  like the  documentation pinpoints ?
My apologies for not submitting a PR here, I was not able to access the Colab doc .
Have a nice day !

You are right. We renamed the class soon after launch and did not update this colab. We'll fix it as you suggest. Thanks for spotting this!

Fixed - thanks!

Awesome!
Just realized the method is also called at the end of the tutorial , in Build your own agents however you like! cell , in case that you also might want to change that .
from baselines.common.vec_env import dummy_vec_env
from baselines.ppo2 import ppo2
from bsuite.utils import gym_wrapper
import tensorflow as tf

SAVE_PATH_PPO = '/tmp/bsuite/ppo'

def _load_env():
  raw_env = bsuite.load_and_record(
      bsuite_id='bandit_noise/0',
      save_path=SAVE_PATH_PPO, logging_mode='csv', overwrite=True)
  return gym_wrapper.GymWrapper(raw_env)
env = dummy_vec_env.DummyVecEnv([_load_env])

ppo2.learn(
    env=env, network='mlp', lr=1e-3, gamma=.99,
    total_timesteps=10000, nsteps=100)

Thanks again for fixing it ^^

Thanks again, I have just updated that part as well.


add String() method to Point

fix #89

Just some optional comments.
I'm curious how you found this repository given its low numbers of stars and the fact that we haven't advertised it =)

Hi, I am both a novice go (game) player and a beginner go (language) developer, so I like your project :) I found it on https://issuehub.io searching by tag ...

Cool, thanks for the PR!


Allow SSL configuration at webapp level

JIRA link

Change description
Allows configuration of an SSL certificate to an app service
Needs a separate ARM template because the SSL binding needs the custom hostname to have been created, but its created as a sub resource currently, also it needed a dependsOn for the certificate resource being created before the webapp but the certificate resource is only created when required.
A separate ARM template makes it a lot easier to conditionally create the resources, seems fine to me unless there's any ARM template experts here who can advise on a better way of doing it?
This has been tested locally on a webapp I created, will test it fully with IDAM before merge
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Tested on idam in perftest:


HDDS-10343. Remove dependency on jsr305

What changes were proposed in this pull request?
Remove dependency on jsr305:

remove CheckForNull annotation (used in 2 places)
exclude as transitive dependency
add as provided for ozone-csi module, which does not compile without it

https://issues.apache.org/jira/browse/HDDS-10343
How was this patch tested?
CI:
https://github.com/adoroszlai/ozone/actions/runs/7855042071

Thanks @adoroszlai for the contribution and @szetszwo for review.

Thanks @nandakumar131, @szetszwo for the review.


Numpy 1.24 breaks master.

Description of the issue
Numpy 1.24 was released recently (see release notes) and it breaks master branch.
Using alias for built-in types was deprecated in Numpy 1.20 (See https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated) and was finally removed in the 1.24 release. As a result, all cirq code that uses aliases for built-in types like np.bool breaks.
Specifically, we'd need to fix the the proper_repr function to use bool instead of np.bool, which would end up changing the repr of a bunch a Cirq classes.
https://github.com/quantumlib/Cirq/blob/db33aad5699976bcb896e8cc5dc6db3598aef257/cirq-core/cirq/_compat.py#L143
Other occurrences of np.bool are in repr and repr_inward files, which can be updated directly to use bool instead of np.bool.  Specifically, the following two files:
https://github.com/quantumlib/Cirq/blob/db33aad5699976bcb896e8cc5dc6db3598aef257/cirq-google/cirq_google/json_test_data/cirq.google.EngineResult.repr#L1
https://github.com/quantumlib/Cirq/blob/db33aad5699976bcb896e8cc5dc6db3598aef257/cirq-core/cirq/protocols/json_test_data/TrialResult.repr_inward#L1
Cirq version
1.1.0.dev

Another source of conflict is that numba (a Cirq dependency due to cirq-contrib)  supports numpy only upto 1.23; so we are blocked on them before we can upgrade to 1.24. See https://numba.readthedocs.io/en/stable/user/installing.html#compatibility
For now, I will limit numpy version to 1.23 and then we can work on the upgrade once numba adds support for 1.24.

can we add a comment to the requirements.txt linking to this issue so it's clear why we're restricting the version

Is anyone assigned to this high priority issue?

I think this should be unblocked by https://github.com/quantumlib/Cirq/pull/5991 and a new release of numba that now supports numpy 1.24 (https://numba.readthedocs.io/en/stable/user/installing.html#compatibility)

sweeeet! Regardless of what numba is doing, we can un-pin it in our dependencies, yes?

I think so, let's find out - https://github.com/quantumlib/Cirq/pull/6149

Is there a plan to release soon with numpy 1.24 support?


Not compiling on Android

The problem is a missing ; here (line 42 in VolumeControl.java)

trying it with PhoneGap Build, i see the same error in logs

In iOS it fails because of the DLog statements that don't get included apparently, I did a quick fix for that as well on my own fork ( sy1vain/cordova-plugin-volume-control ) , will do a pull request here.

Thanks for the contribution sy1vain. Currently I have few time to dedicate to the project, but I will try to launch a release version soon.


Export lineage relationships in a file

Some data discovery platforms like Amundsen have options to visualize data lineage relationships at a glance on the moment that you are exploring data. But you need to bring your own lineage metadata, Im really interested in an option to export the lineage relations in a file (csv or json) so I can pass that to the amundsen extractor. In the case of the basic lineage extractor of amundsen uses a single .CSV file with the structure: source_table , target_table
If this file is a JSON , additional info can put it in there. So we could filter per type: CREATE_VIEW or CREATE_TABLE operations

Hi @gabola24,
Thanks for opening this issue! starting from version 0.1.3 we now support exporting the lineage and its attributes (query type, update time, duration, etc) to two files - 'lineage_graph.gpickle' and 'graph_attributes.gpickle'. We used this serialization format as this is very common when working with graphs. Please let me know if this helps with your use case.
thanks!


Clean up GA-ed feature gates

/kind cleanup
Release note:

The GA-ed `CachedRuntimeClients`,  `AdminKubeconfigRequest`, `DenyInvalidExtensionResources` and `UseDNSRecords ` feature gates are removed and can no longer be specified via the `--feature-gates` flags.

/lgtm


nixos/installer: simplify and document wifi setup

Motivation for this change
The wpa_supplicant service in the NixOS installer is unusable because
the control socket is disabled and /etc/wpa_supplicant.conf ignored.
The manual currently recommends manually starting the daemon and using
wpa_passphrase, but this requires figuring out the interface name,
driver and only works for WPA2 personal networks.
By enabling the control socket, instead, a user can configure the
network via wpa_cli (or wpa_gui in the graphical installer), which
support more advanced network configurations.
Things done

[x] Built iso_minimal
[x] Built manual
[x] Connected to a network using wpa_cli
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This only applies to the minimal installer which doesn't have NetworkManager if I understand correctly. If you use the "graphical" installer, network manager is enabled and you can use nmtui which is far easier, being a terminal gui. I recall using nmtui when I didn't get a graphical session.

This only applies to the minimal installer which doesn't have NetworkManager if I understand correctly

While the manual specifically says minimal installer, I guess the instructions will work even when running NetworkManager.

If you use the "graphical" installer, network manager is enabled and you can use nmtui which is far easier, being a terminal gui

To save time, I've never downloaded the graphical installer so I couldn't say.
The minimal installer doesn't have nmtui, though:  configuring a wifi network was painful enough to open this PR.

So the small download did waste your time. :thinking:
I'd hate for more people to have to go through that, even with the instructions. Are you interested in packaging a similar tui for wpa supplicant? A script exist but looks unmaintained.

Squashed commits.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/better-wifi-ux-on-the-non-graphical-installer/23030/8


perl: use pkgs.zlib instead of bundled zlib

Description of changes
perl currently contains it's own bundled zlib-1.2.11, which is vulnerable to CVE-2018-25032, and is used when building the core module Compress::Raw::Zlib.
It is built by perl and is separate from perlPackages.CompressRawZlib.
This PR patches perl to use pkgs.zlib instead when building this core module.
# To check what zlib version is used
perl -MCompress::Raw::Zlib -E 'say Compress::Raw::Zlib::zlib_version();'

https://github.com/pmqs/Compress-Raw-Zlib/issues/6
Cc: @alyssais
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build perl

@GrahamcOfBorg build pkgsCross.aarch64-multiplatform.perl534
@GrahamcOfBorg build pkgsCross.armv7l-hf-multiplatform.perl534
@GrahamcOfBorg build pkgsMusl.perl534
@GrahamcOfBorg build pkgsi686Linux.perl534
@GrahamcOfBorg build perl534
@GrahamcOfBorg build pkgsCross.aarch64-multiplatform.perlPackages.HTTPDaemon

For 21.11 I assume we'll wait for upstream to release versions with updated bundled zlib?  I suspect that adding the external runtime dependency on zlib might be a bit intrusive for stable.

For 21.11 I assume we'll wait for upstream to release versions with updated bundled zlib? I suspect that adding the external runtime dependency on zlib might be a bit intrusive for stable.

Agree :+1:

This appears to have broken pkgsStatic.perl.  That's on me for not testing this at the time.  I haven't looked into why it broke yet.

https://github.com/arsv/perl-cross/pull/129


[Bug] Union Failure, Different Datatypes

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
In the union for ap_ar_enhanced, there are incompatible types. Department ID seems to fail here. If you cast the department ID to a string, then the model runs without issue.
Relevant error log or model output
"Writing runtime sql for node "model.sage_intacct.sage_intacct__ap_ar_enhanced"
BigQuery adapter: https://console.cloud.google.com/bigquery?project=...
BigQuery adapter: Retry attempt 1 of 1 after error: BadRequest('Column 13 in UNION ALL has incompatible types: STRING, INT64 at [143:5]')"

Expected behavior
Here is one of the offending lines:
ap_bill_item.department_id,
And here is the fix:
cast(ap_bill_item.department_id as string) as department_id,
The other offending line also requires a similar fix:

ar_invoice_item.department_id, ->
cast(ar_invoice_item.department_id as string) as department_id,

dbt Project configurations
I have the default setting of true for  sage_intacct__using_invoices, sage_intacct__using_bills.
Package versions
From packages.yml:

package: fivetran/sage_intacct
version: 0.2.2

What database are you using dbt with?
bigquery
dbt Version
1.6, for some reason dbt --version in the IDE isn't working.
Additional Context
No response
Are you willing to open a PR to help address this issue?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

This is my first time using the package.
I think that fix will definitely work. I'll look forward to that fix coming down the pipeline.

this is in v0.2.1 of the source package! so the transform package will automatically pick it up


File not found exception coming for fullName "Intense.Themes.Navigation" in ARM configuration

I already had Intense framework for Split view in my app. I just added "Ink Toolbar control for Universal Windows apps" from https://visualstudiogallery.msdn.microsoft.com/58194dfe-df44-4c4e-893a-1eca40675269
After that app us working fine in x64 and x86 configuration. However, if I select ARM configuration to install app into my Win 10 mobile. It builds fine and deploys the app, but while running the app, it failed with below error:

Here is the error:

I just added this InkToolbar control to your Splitview sample. Immediately, i was able to repro the issue. "App on the Phone failing with above exception"

Hello, I think I have the same problem under Windows Phone (Windows 10 no pb) with InkToolbar.

Cannot deserialize XBF metadata type list as 'Navigation' was not found in namespace 'Intense.Themes'. [Line: 12 Position: 37]

Same exception Intense.Themes.Navigation !


webseed of the torrent is causing memory leak in transmission-daemon

when adding the torrent file from https://mirror.manjaro-sway.download/manjaro-sway/manjaro-sway.torrent after a few minutes transmission-daemon gets killed by OOM killer due to the system running out of RAM.
I assume that that is caused by the web seed (as there are no other peers than me)
I also raised a issue on the transmission repo in case it is a issue with my torrent client

Oh, wow. I wouldn't know how we could have an impact, as the mktorrent command looks very basic.

it downloads ~50MB from the webseed and then (allegedly) downloads for a few minutes at ~90MB/s (if internet is fast enough and no speed limit is set) while the progress bar doesn't move any further.
It then gets killed once the 1G of RAM gets full by transmission-daemon allocating memory at download speed
(it has only been the last 2 releases where the webseed even worked in some way, before then I downloaded the files from the github release page into the transmission downloads directory and then seeded for everyone else who would have wanted to download it via torrent)

it has only been the last 2 releases where the webseed even worked

that is true, I just recently fixed the path for the webseed. sad this didn't work out so far. thanks for looking into it tho!

in qbittorrent for me it looks less like a memory leak, but after some seconds it is absurdly slow.

in transmission, I can see the issue you describe. It starts with a high 9-11Mb/s but never progresses after having downloaded the small files. The .iso files remain at 0% while the download indicator stagnates around 10Mb/s

@all-contributors please add @2L3R4 for reporting a bug

I wonder if there is something about the file somehow "changing" between the local filesystem and after it is being uploaded to s3. For regular downloads I get top speed anyhow:

one more note: until this is clarifies, we could just decide to disable the torrent file link. I am serving the files via cloudflare r2 and will thus have no egress fees anyway. I always liked the idea of having a torrent option tho.

we dropped the whole torrent feature for now.


AWS Security Hub: set 'active' flag default to False

Fixes issue #3714

makes sense to me.

makes sense to me.


fix change cloud rebalance config to masterOnly=true

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run p0

run p0


yaws no longer works as rebar dependency

rebar looks for .app and .app.src files.  The yaws.app.src is now yaws.app.src.in, so rebar fails with:
DEBUG: is_app_available, looking for App yaws with Path "/Users/sugiyama/work/git/clones/flowforwarding/loom/tapestry/deps/yaws"
WARN:  Expected /Users/sugiyama/work/git/clones/flowforwarding/loom/tapestry/deps/yaws to be an app dir (containing ebin/*.app), but no .app found.
ERROR: Dependency dir /Users/sugiyama/work/git/clones/flowforwarding/loom/tapestry/deps/yaws failed application validation with reason:
{missing_app_file,"/Users/sugiyama/work/git/clones/flowforwarding/loom/tapestry/deps/yaws"}.
Works with yaws-1.98.

Hi @vinoski, I was wondering what release this fix was put into and if it still applies. It seems as though I'm having exactly the same problems on all versions I've tried.

@nbrady-techempower: the fix is in Yaws 1.99 and newer. You might want to check the version of rebar you're using, as different versions have had issues with this sort of thing over the years. I believe 2.6.1 is the latest released version of rebar.

@vinoski Ah, always when I'm looking in the wrong place. Was part of the enterprise version of erlang I was using. Thanks so much!


Get Code to Work Again

===== Finish by next Thursday plez

well it runs...

Facebook API is dead


Hardcoded list of options in index.js

Starting on line 13 you are defining a list of hardcoded command-line options. I see the benefit for "hidden", since its gets stringified. But on the other hand people might get confused since "inject", "ssl-key" and "ssl-cert" will be ignored. What’s about passing all options directly to "args" without any filtering?
Regards,
Johannes

Makes sense, could you submit a pull request pls?

Of course, not a big deal at all. But I worry about issue #5 ...


Expand integration documentation

From JeremyParish, he suggested the following list of articles to add to our documentation under the  integration section.
I was thinking of having a page or section for many different things projects tend to ask questions about or need help with:

[ ] How to transfer CW20 tokens between zones
[ ] How to validate IBC token transfers
[ ] How to integrate onto Mintscan
[ ] How to integrate onto Coin Gecko
[ ] How to add a pool onto the Trade page
[ ] How to add a token onto the Assets page
[ ] How to register onto Assetlists
[ ] How to register onto Cosmos Chain Registry
[ ] How to create a pool on Osmosis
[ ] How to add External Incentive Gauges onto Pools page
[ ] How to add External Incentives to a pool
[ ] How to propose onboarding onto the External Incentive Matching program
[ ] How to propose onboarding a pool for Osmosis Liquidity Mining Rewards
[ ] How to sponsor a Twitter Contest
[ ] Request Social Media promotion
etc.
I know that some of these, like, adding gauges or creating pools, is already documented elsewhere (under Develop, I believe), but I have it again as it seems to be part of the natural flow for integration.

Have started on a few of these:

How to add a token onto the Assets page
How to register onto Assetlists
How to register onto Cosmos Chain Registry
How to transfer CW20 tokens between zones

intent to work on a few more very soon:

How to add a pool onto the Trade page
How to add External Incentive Gauges onto Pools page

as well, being a member of the OMM, I'd like to work on marketing-relayed pages:

How to sponsor a Twitter Contest
Request Social Media promotion

I also don't have any issue discussing with other projects for a new ones like:

How to add Assets to info.osmosis.zone (I can discuss with Imperator on this)
How to add Assets to Comsos Tokens page (Sunny used to work for Tendermint, so he might know)
How to integrate onto Mintscan (no idea whom to talk to so far)

also, I think we are in dire need of assistance for relaying, hence I propose:

Shop for Relayer as a Service (RaaS) Providers
and
Request support for setting up a Relayer
To go along with: How to validate IBC token transfers

finally, thought it might be nice to have one:

How to enlist onto Map of Zones

This is amazing :fire: :fire: :fire:
We will setup a call next week to go over the best layout and location on the UI for these docs and the other you are working on.
Links on the WIP from his fork:
https://github.com/JeremyParish69/docs/blob/main/integrate/frontend.md
https://github.com/JeremyParish69/docs/blob/main/integrate/registration.md


Create a Well-Informed README

can you provide overview of app??

can you provide overview of app??
Frame and Enhance the given piece of information in your own words keepin' in mind user-friendliness and technical help...:

VoyageVista - Explore the World
Welcome to VoyageVista, your ultimate destination for seamless international travel bookings without the burden of additional charges. Our platform is meticulously crafted to enhance your journeys, ensuring a truly effortless and global experience.
Key Features:
Effortless Bookings: Indulge in a smooth booking experience with our intuitive and user-friendly interface.
Global Accessibility: Discover and book flights, accommodations, and activities spanning international borders.
Transparent Pricing: Bid farewell to hidden fees and unnecessary charges for a clear and honest transaction.
Streamlined Efficiency: Save valuable time through our simplified booking process.
How to Navigate:
Discover: Explore an extensive array of destinations, flights, hotels, and activities tailored to your preferences.

Book: Finalize your booking securely and effortlessly through our seamless platform.
Journey: Embark on your adventure with confidence, knowing your bookings are in capable hands.
Contributions Are Welcome:
Enhance VoyageVista with your contributions! Whether you have innovative suggestions, spot bugs, or wish to introduce new features, feel free to get involved by:
Submitting Issues: Report bugs or propose improvements through our GitHub repository.
Fork & Pull Requests: Directly contribute by forking the repository and submitting pull requests.
Feedback Loop
Your insights are invaluable to us. Reach out to our support team for any inquiries, feedback, or concerns.
Thank you for entrusting VoyageVista with your travel needs. Bon voyage!

Please assign me this issue. I am interested in fixing this issue

Please assign me this issue. I am interested in fixing this issue

Assigned you, 1 day for this, all the best👍🏻

@Sneha123-zudo Good Job❕

@Sneha123-zudo Good Job❕


Keep subgraph

We want to publish a new repo with a Keep network subgraph. This should make external dApp development much easier, since indexing can be taken care of. It'll also potentially enable caching for the dashboard.
Should be able to expose:

[ ] grant supply schedule
[ ] total staked amount
[ ] keep types
[ ] random beacon

[ ] requests
[ ] entries

@mhluongo @Shadowfiend I created this issue in the keep core repo, but I don't have permissions to put keep core issues in other backlogs (i.e. dapp & liquidity, sprintboard) ... can you fix? Right now this is only in Growth and it should be other place.


Text Analytics Track 2 Beta 3

This Epic is for tracking issues related to Text Analytics Track 2 Preview 3.

Beta 3 released:
https://oss.sonatype.org/#nexus-search;gav~com.azure~azure-ai-textanalytics~~~~kw,versionexpand


corenlp.client.TimeoutException: Timeout when executing Tregex query

I am trying to use the Tregex for pattern matching and I get the following error:
corenlp.client.TimeoutException: Timeout when executing Tregex query
I have no problem using the annotator and the pipeline but I do not know why I am getting the Timeout exception when I am trying to use Tregex. I read something here about checking if the server is alive or to cold start the server but I do not know what exactly to do. Any help would be appreciated.
And, just in case you may want to know, my input text is too short: "He had to leave early because he was feeling bad." Even the same example which is provided in test_client.py does not work while the pipeline itself works pretty well. I also tried some of the other suggested solutions (like increasing the timeout time in client class) but non of them works.

Do you resolve this problem? I am getting the same error using TRegex in CoreNLP python wrapper.

@xzegga Not yet! For now, I ended up parsing the raw text of the parser output and coming up with some regular expressions.

I have the same issue with CoreNLP 3.91, but no problem with 3.8. My issue is with Semgrex.
I'm running either 3.8/3.91 as a local server with Java 10
java  --add-modules java.se.ee -mx4g -cp "*" edu.stanford.nlp.pipeline.StanfordCoreNLPServer -port 9000 -timeout 60000
Referenced in python with:

corenlpProps = {}
corenlpProps["inputFormat"] = "text"
corenlpProps["outputFormat"] = "json"
corenlpProps["serializer"] = "edu.stanford.nlp.pipeline.ProtobufAnnotationSerializer"
corenlpProps["tokenize.options"] = "ptb3Escaping=false,invertible=true"
corenlpProps["timeout"] = "60000"
client = corenlp.CoreNLPClient(start_server=False, endpoint="http://localhost:9000", annotators="tokenize ssplit".split(),
properties=corenlpProps)

and I tried .ensure_alive() before running Semgrex:
client.ensure_alive()
output = client.semgrex(fragment,                              pattern=SemgrexRule,                              filter=False)
but still get the timeout right away with 3.91:
File "C:\gitProjects\momo\venv\lib\site-packages\corenlp\client.py", line 244, in __regex     raise TimeoutException(r.text) corenlp.client.TimeoutException: Timeout when executing Semgrex query


No matching attestations found for attestationData

Describe the bug
Running multiNodeSingleThread.test.ts with 128 validators per node and there are errors like this:
2021-03-30 17:57:28 [NODE 1 VALI 128-255] error: Failed to produce aggregate and proof message=No matching attestations found for attestationData
Error: No matching attestations found for attestationData
    at ValidatorApi.getAggregatedAttestation (/Users/tuyennguyen/Projects/workshop/lodestar/packages/lodestar/src/api/impl/validator/validator.ts:123:13)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at AttestationService.aggregateAttestations (/Users/tuyennguyen/Projects/workshop/lodestar/packages/validator/src/services/attestation.ts:273:19)
    at Timeout._onTimeout (/Users/tuyennguyen/Projects/workshop/lodestar/packages/validator/src/services/attestation.ts:212:13)

Expected behavior
At least there should be 1 attestation coming from that same aggregator
Steps to Reproduce
yarn test:sim:singleThreadMultiNode

@tuyennhv Could you upload the logFile in debug level? It would help see if the attestations are actually received from gossip

This is the debug log:
issue_2298_debug.log

Our current validator client implementation does not guarantee that the aggregation step happens strictly after publishing the attestation
If this API call is significantly delayed
https://github.com/ChainSafe/lodestar/blob/ea5e141daebce417f92f58520f7ea5741ce9a4e0/packages/validator/src/services/attestation.ts#L220
The timeout wrapping this call will fire and may be executed before completing the above if the beacon node is overloaded
https://github.com/ChainSafe/lodestar/blob/ea5e141daebce417f92f58520f7ea5741ce9a4e0/packages/validator/src/services/attestation.ts#L212

Fixed with validator client refactor


 Can we have a YML support? If you can onboard me with the code stacks, I'll be happy to help.

Unfortunately the requirement for json comes from packer itself.. this project is only a plugin for packer

See a related issue in packer here: https://github.com/hashicorp/packer/issues/1768
Closing for now as we cannot help with that. feel free to re-open

Thanks @yuval-k


Add Pubsub example

This is the create pubsub sample.

[ ] Add appcallback.proto
[ ] Implement AppCallback server for subscription
[ ] Create Publish sample
[ ] Add README

@zeiz I filed the issue to track pubsub example.

@youngbupark I'll take on this issue if it's not currently being worked on. Thanks


chart not visible in helm search after upload to chartmuseum

I've created a new chart locally and added it to the my chartmuseum with the command curl --data-binary<EMAIL_ADDRESS>http://REPOURL:REPOPORT/api/charts.
However, helm search doesn't show the updated version or new chart and If I updated the chart, helm fetch fetches the old version, until I re-add the repo with helm repo add NAME URL with the same name as before.
Is refreshing the available chart list a missing or undocumented feature of helm? Or did I just overlook the helm-parameter?

Closing the issue, since I noticed that the info can be updated with helm repo update.


Update bench, please

It must be recognized that the implementation of itoa is very good, although it would have to be tested with large numbers. But as I said the buffer is not ok. I still have to go over things, but if you can update the results. Thank you :smile:

There is no significant performance improvement/depletion after last benchmark update.
Could you tell me why the buffer implementation is not ok?

Sorry, just remove target directory and Cargo.lock. It's ~10us  better in big_table. Sailfish ~35us and yarte Send ~25us in my i7-7700HQ 2.8Ghz.

I've updated the benchmark results.
sailfish 0.1.1 is even faster than 0.1.0. However it seems that Yarte is sometimes a bit faster than sailfish.

I just started


@BindView(R2.id xx ) in lib not work

@BindView(R2.id.textview)
TextView textview;

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.act);
    ButterKnife.bind(this);
    Log.e("zjw", "   title   " + textview);

}

print   title   null
click textview nouse

There's no enough information here to make this report actionable. Please include information such as how you're configuring your build, whether the generated code is present in the build/ folder, if you're using ProGuard, etc.

just a demo no ProBuard
project build.gradle
buildscript {
repositories {
jcenter()
}
dependencies {
classpath 'com.android.tools.build:gradle:2.1.2'
classpath 'com.neenbedankt.gradle.plugins:android-apt:1.8'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
app build.gralde
apply plugin: 'com.android.application'
apply plugin: 'android-apt'
android {
compileSdkVersion 24
buildToolsVersion "24.0.0"
defaultConfig {
    applicationId "com.yanyuanquan.android.butterknifedemo"
    minSdkVersion 15
    targetSdkVersion 24
    versionCode 1
    versionName "1.0"
}
buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

}
dependencies {
compile fileTree(include: ['*.jar'], dir: 'libs')
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:24.1.1'
compile 'com.jakewharton:butterknife:8.2.1'
apt 'com.jakewharton:butterknife-compiler:8.2.1'
compile project(':helper')
}
lib build.gradle
apply plugin: 'com.android.library'
apply plugin: 'com.jakewharton.butterknife'
apply plugin: 'com.neenbedankt.android-apt'
buildscript {
repositories {
mavenCentral()
}
dependencies {
classpath 'com.jakewharton:butterknife-gradle-plugin:8.2.1'
}
}
android {
compileSdkVersion 24
buildToolsVersion "24.0.0"
defaultConfig {
    minSdkVersion 15
    targetSdkVersion 24
    versionCode 1
    versionName "1.0"
}
buildTypes {
    release {
        minifyEnabled false
        proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
    }
}

}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
testCompile 'junit:junit:4.12'
compile 'com.android.support:appcompat-v7:24.1.1'
compile 'com.jakewharton:butterknife:8.2.1'
}
THIS All
Please Help me   Thank you !

If you turn on ButterKnife logging in the application what do the logs show when attempting to bind that class?

I create  a demo
https://github.com/guider/ButterknifeDemo
maybe you can check out and check where I have error 3Q

@JakeWharton
I create a demo
https://github.com/guider/ButterknifeDemo
maybe you can check out and check where I have error 3Q

yeah  !  I have solve  THx

What was the problem?
On Fri, Aug 5, 2016 at 1:04 AM 张金伟<EMAIL_ADDRESS>wrote:

yeah ! I have solve THx
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JakeWharton/butterknife/issues/698#issuecomment-237755998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEQR3VOOGAK1voZZ71Xfcf6Qr2g2gks5qcsRagaJpZM4JdU0v
.

@guider How did you solve the problem?

This is a solution http://blog.csdn.net/ytzys/article/details/53243438

@guider How did you solve the problem?


Clints

This might be my most important OSS contribution ever. :bow_and_arrow: Thank you. :bow_and_arrow:

lol


DEC840 USB console

On the DEC840 the USB console is ttyu0 not ttyU0, so the default configuration in /etc/ttys doesn't work.
You can see the kernel messages at boot with console="efi", but you can't login or install from the USB serial console because of this limitation.
changing ttyU0 to ttyu0 and kill -HUP 1 makes the console usable.
Can we get this supported out of the box?

@feld you shouldn't need anything (it should work out of the box), if this machine is a little bit older, you might need to change the bios settings as described at https://docs.opnsense.org/hardware/serial_connectivity.html#legacy-uart-vs-uefi-serial


API/inspect container no longer returns path in Volumes map

As of 1.8.x, inspecting a container no longer returns the path to the persistent volume under the Volumes map, but instead in the Mounts slice (therefore unkeyed!) entries. For example:
 "Volumes": {
            "/etc/nginx/certs": {},
            "/var/cache/nginx": {}
        },

...
"Mounts": [
         {
            "Name": "bb9d6cf96309ae1c15984764a148022395edf1fa3f9399a8a99c3763be2fa612",
            "Source": "/var/lib/docker/volumes/bb9d6cf96309ae1c15984764a148022395edf1fa3f9399a8a99c3763be2fa612/_data",
            "Destination": "/var/cache/nginx",
            "Driver": "local",
            "Mode": "",
            "RW": true
        },
        {
            "Name": "ec61b53e4faf593997241230429e19a3b2d956dfb56ee87eacf80e5fd5773b99",
            "Source": "/var/lib/docker/volumes/ec61b53e4faf593997241230429e19a3b2d956dfb56ee87eacf80e5fd5773b99/_data",
            "Destination": "/etc/nginx/certs",
            "Driver": "local",
            "Mode": "",
            "RW": true
        }
    ],

Note that the documentation still states that the Volumes map contains the host path and r/w status.

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Where is that wrong documentation? https://docs.docker.com/reference/api/docker_remote_api_v1.20/#inspect-a-container seems correct to me. The Volumes map is still in the config object but not in the main object any more.

The userguide: https://docs.docker.com/userguide/dockervolumes/#locating-a-volume. The api docs are correct for v1.20 but, nowhere can i find mention of this significant change, other than diff'ing the docs.
As a aside, listing all the mount points as an array containing all mounts (not just volumnes) vs a hash keyed by destination makes actually using the info much more difficult.

Thanks @cybercode! This is now fixed (not yet published to the website) in https://github.com/docker/docker/issues/15671


Respect operating system filesystem standards

We should use something like $XDG_CONFIG_HOME/coda on Linux, maybe Library/Preferences/coda on macOS, and maybe FOLDERID_RoamingAppData on Windows.

We should split up ~/.coda-config into these locations

closing, see #6105 for an up-to-date discussion of this issue.


fix: making it easier to listen for the ELEMENT_ENABLED event

@galelis I changed the trigger target for ELEMENT_ENABLED because the change has only been live for a short while; however, I added another trigger target for ELEMENT_DISABLED, as others may depend on the event being broadcasted from the element (hint: Asteris does)

LGTM! :)

@galelis it's blowing up for me in the after/beforeEach hooks. Any chance I could get you to take a peak? Not 100% familiar with cornerstone's test suite.

Coverage increased (+0.3%) to 65.839% when pulling 67e3ca247cc79871561dcd874e36da3b2ae45fd4 on dannyrb:master into ea9c4ca75488c6b79549c2bc437dc039b178d575 on cornerstonejs:master.


Someway to decrease build time?

When installing on Arch Linux via yay, the build time is ~4 minutes.
Is there some way to provide builds for this to the AUR setup, or decrease build times?
I realize 4 minutes isn't that much, but it's consistently 4-5x as long as the rest of the system update process.

Memory usage also seemed to have exploded over the past releases. I am running an older secondary arch system with only 4gb of ram and when trying to compile, the entire system freezes. I didn't have the time to investigate further but using the mise-bin package obviously helped by avoiding compiling

yeah if possible using binary packages is better. You can also try changing settings like lto. I'd accept a PR for a new profile like "fast-release" or something that we could use for things like AUR.

Switching to thin LTO helps to speed up the build process quite a lot indeed: on my machine instead of 1m17s it becomes 20s. Disabling LTO completely doesn't make it any quicker though.
I wonder, how much worse the performance is with thin LTO instead of fat? So far I noticed that the binary is 4M smaller with fat LTO.

lto is now disabled by default


Refactor eval script

This PR merges the existing ppo_gridnet_eval_duel.py and ppo_gridnet_eval.py into a single script that could evaluate a trained RL bot against both built-in bot and other RL bot.

@xluox I am merging this now but this change might be relevant to you :)


Multiple vpn user from a lan to my opnsense server

Hi everybody,
I have a lan with 4 computers in siteA
and in siteB, i have a opnsense serveur with VPN.
It work fine but only for one computer (client vpn)
If someone is siteA is connected to siteB, other client can't connect to vpn server.
Any suggestion to permet all computer in siteA lan to access siteB in same time ?
Thank you for  your help
OPNsense 16.7.14

This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue,
just let us know, so we can reopen the issue and assign an owner to it.


MM-20311: plugin signing permalink

Summary
Point the system console help link re: plugin signing at https://mattermost.com/pl/default-plugin-signing. Note that this permalink does not yet route anywhere, and shows an error message on mattermost.com, but will be replaced in advance of the v5.18 release.
Ticket Link
Fixes: https://mattermost.atlassian.net/browse/MM-20311

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4373.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed


Display "GB" and "MB" instead of "Gb" and "Mb"

The correct way to display file size, storage and consumed bandwidth is B, KB, MB, GB, TB and not b, Kb, Mb, Gb, Tb.
"B" mean "byte", "b" - bit. They are quite different.
I still see "Mb" and "Gb" in many places.

File size abbreviations was renamed


Modify AboutUs and README

As a developer, I can read the documentation so that I can credit the original developers of the project.

Modified my AboutUs.md section.
Modified README to include attribution for icons changed in UI


Retrieved a null token

When I call getToken method, I retrieve a null token, I don't understand why. I've got any error log  ...
@ionic/cli-utils  : 1.12.0
ionic (Ionic CLI) : 3.12.0
global packages:
cordova (Cordova CLI) : 7.0.1

local packages:
Cordova Platforms : ios 4.4.0
Ionic Framework   : ionic1 1.3.2

System:
Android SDK Tools : 25.2.5
ios-deploy        : 1.9.0
ios-sim           : 5.0.8
Node              : v8.0.0
npm               : 5.0.0
OS                : macOS Sierra
Xcode             : Xcode 9.0 Build version 9A235

Misc:
backend : legacy`

I've got this problem on iOS 10.2.1 (iPhone 5C) but on iOS 10.3.3 (iPhone 6) it still works.

Same here, any news with these?
None of the solutions in other issues work.
I'm using latest versions of cordova and this plugin

For some reason, when I use cordova add plugin cordova-plugin-firebase,
the version 0.1.24 I get doesn't have the latest changes to /scripts/after_prepare.js
I fixed this by manually download the zip file from GitHub and place it in my node_modules directory.

@kelkmere 👍
Same problem (on android), solved it exactly as you described. Thank you!

@robertarnesson are you going to publish a new releasae anytime soon?

Indeed, cordova add plugin cordova-plugin-firebase downloads an outdated version, which has a bug in the after_prepare hook, so the firebase config files are not copied over to the platforms correctly. Use cordova plugin add https://github.com/arnesson/cordova-plugin-firebase.git --save or download the zip file and place it in plugins directory. Thank you @kelkmere

I experienced the same thing. Would be good to get a new release soon with the correct/latest /scripts/after_prepare.js. My solution was to peg to version 0.1.23 and have not had any problems since.


fix: allow role specification for single task executions

TL;DR
Adds support for providing a value for authRole when launching a single task execution. This value will be reused if relaunching a single task execution.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[x] Code documentation added
[x] Any pending items have an associated Issue

Complete description

Added new input/state to the task from workflow for handling a role type and value. This value is required and will default to IAM for now. I might add a follow-up PR to store the last choice in localStorage to make it easier for those using k8s service accounts.
Added unit tests to verify all requirements
Updated code for relaunching an execution to support passing through the authRole value from the previous execution.
Added a section header for the inputs area to distinguish it from the role input. Added a special case handler for when there are no inputs so that we don't render a header and description with no corresponding controls.

Tracking Issue
https://github.com/lyft/flyte/issues/582
Follow-up issue
NA
Screenshots

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


Run the git BFG repo cleaner

The initial commit for this repository contained way more files and data than now, so the git history is pretty heavy size wise. I would like to run the BFG repo cleaner on it to get rid of all those old files in the git history that we cleaned up.
PR #48 is a good reference for the file types that got deleted.

Before running the BFG cleaner, this repository has a size of 4.61 GB on disk, which includes all of the git history and everything stored in it. If I sum the sizes of the files and directories within the repo (in the current version), it's a little less than 2.9 GB. 2.86 GB of those are the limb darkening folder, and all the rest is a little over 1 MB.
So it does actually make sense to run the cleaner, since we might reduce the size of the repo significantly.

I used these websites to do this:

https://rtyley.github.io/bfg-repo-cleaner/      - this is the original website and this is where you can download the BFG

https://torchbox.com/blog/how-remove-unwanted-files-your-git-repository/     - just another pretty website explaining the same thing

https://github.com/firemodels/fds/wiki/The-BFG-Repo-Cleaner                         - and another good website about it

Note how the BFG will protect your latest commit on all branches, so we are not running the risk of losing anything we actually want.

I just realized that the push limit of the cleaned up repo is usually 2GB. Since we would still be above that even after the cleanup, we might not actually be able to do this. I will try and report back as I go along.

Supposedly, this did something... it failed to push to some remote refs that I didn't even know were there. It seems to have compressed the repo to about 1.5 GB but that's not what I see when I make a fresh clone.
Here is the terminal output in case somebody wants to know what happened, but I am closing this issue now:

Also, this totally deleted the branch for PR #86 and closed that PR without merging, oops... I will make a new branch and a new PR for this.

I realized that one motivation to clean out the repo is also to speed up the CI, since that checks the repo out every single time it runs. Might be worth to look into this at a later point.


Localization/translation

I would like to request filipino translation contribution thru github.

There's a thread about translations. Participate there please.

Hi. Can I have the file for translation thru github?
On Feb 10, 2018 12:00 AM, "woky"<EMAIL_ADDRESS>wrote:

Closed #280 https://github.com/ZencashOfficial/arizen/issues/280.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ZencashOfficial/arizen/issues/280#event-1466949922,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhjYgESyrNkTh2smVv-ufirllFpYaIWLks5tTGuBgaJpZM4R-PZZ
.

@vinzruzell see #173


Create left-handed cursors

I would like to suggest the development of left-handed cursors specifically for the Sugar Learning Platform. I am Ryan Cunningham, a left-hander myself (whom you might have found in prior contact with one of your team), and the existing left-handed Comix cursor set for X11 may be insufficient for Sugar.

Thanks.  Great work.
I've also changed the directory name in Makefile.am updated configure.ac, and pushed as 788054d.

Thanks @rcunning01. :-)


search inside webarchive | pinterest full user | tumblr is missing | facebook doesn't work

you should add a way to post only specific items from an user, example
"bodybuilding books inside user a" instead of showing me all books uploaded
about pinterest, a quick way to add the whole user

vimeo not just by search, but even videos by channel

Looks like you are in wrong repository.

what is wrong. it's your product and such things are still missing and sometimes huge limited

500px, Gfycat and the 18+ Gfycat version are not available too


Cannot create a pdf in the current directory

innsmouth {python3} [master] >>>  python main.py out.pdf
The directory out.pdf does not exist, exiting.

Check if master works now.

Works


Empty list causes all evaluations to hang

First of all, thank you for the library. It's awesome to use.
I was going through some examples in Joy of Clojure and noticed if you use an empty list () evaluating any forms after it hangs.

Evaluating the empty list itself and any forms before it is fine. Evaluating the whole buffer works too. Commenting out the empty list fixes the issue.

Nothing major, I doubt any real-world code will encounter this issue. But, it is odd.

Thanks! Pushed 4.3.1


CUDA out of memory with T4 GPU

Describe the bug
Model I am using is LayoutLM.
The problem arises when using:
My own modified scripts: python3 -m torch.distributed.launch --nproc_per_node=4 examples/run_xfun_ser.py --model_name_or_path microsoft/layoutxlm-base --output_dir /tmp/test-ner --do_train --do_eval --lang zh --max_steps 1000 --warmup_ratio 0.1 --fp16 --per_device_train_batch_size 2 --per_device_eval_batch_size 1 --max_seq_length 512
Expected behavior
A clear and concise description of what you expected to happen.
The traceback is:
Traceback (most recent call last):
  File "examples/run_xfun_ser.py", line 297, in <module>
    main()
  File "examples/run_xfun_ser.py", line 46, in main
    model_args, data_args, training_args = parser.parse_args_into_dataclasses()  # Use the arguments as parameters for the ModelArguments classes.
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/hf_argparser.py", line 187, in parse_args_into_dataclasses
    obj = dtype(**inputs)
  File "<string>", line 67, in __init__
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/training_args.py", line 570, in __post_init__
    if is_torch_available() and self.device.type != "cuda" and (self.fp16 or self.fp16_full_eval):
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/file_utils.py", line 1470, in wrapper
    return func(*args, **kwargs)
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/training_args.py", line 717, in device
    return self._setup_devices
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/file_utils.py", line 1460, in __get__
    cached = self.fget(obj)
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/file_utils.py", line 1470, in wrapper
    return func(*args, **kwargs)
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/training_args.py", line 702, in _setup_devices
    torch.distributed.init_process_group(backend="nccl")
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 455, in init_process_group
    barrier()
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 1960, in barrier
    work = _default_pg.barrier()
RuntimeError: CUDA error: out of memory
Traceback (most recent call last):
  File "examples/run_xfun_ser.py", line 297, in <module>
    main()
  File "examples/run_xfun_ser.py", line 46, in main
    model_args, data_args, training_args = parser.parse_args_into_dataclasses()  # Use the arguments as parameters for the ModelArguments classes.
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/hf_argparser.py", line 187, in parse_args_into_dataclasses
    obj = dtype(**inputs)
  File "<string>", line 67, in __init__
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/training_args.py", line 570, in __post_init__
    if is_torch_available() and self.device.type != "cuda" and (self.fp16 or self.fp16_full_eval):
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/file_utils.py", line 1470, in wrapper
    return func(*args, **kwargs)
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/training_args.py", line 717, in device
    return self._setup_devices
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/file_utils.py", line 1460, in __get__
    cached = self.fget(obj)
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/file_utils.py", line 1470, in wrapper
    return func(*args, **kwargs)
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/training_args.py", line 702, in _setup_devices
    torch.distributed.init_process_group(backend="nccl")
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 455, in init_process_group
    barrier()
  File "/data00/home/someone/miniconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/distributed/distributed_c10d.py", line 1960, in barrier
    work = _default_pg.barrier()
RuntimeError: CUDA error: out of memory

Environments

Platform: Debian
Python version: Python 3.7.9
PyTorch version: 1.7.1+cu101
GPU: Tesla T4 (16G)

I am using T4 GPU by the way. @ranpox

If we run without torch.distributed.launch, such as python3 -u examples/run_xfun_ser.py --model_name_or_path microsoft/layoutxlm-base --output_dir /tmp/test-ner-35 --do_train --do_eval --lang zh --max_steps 1000 --warmup_ratio 0.1 --fp16 --per_device_train_batch_size 2 --per_device_eval_batch_size 2, we will have the following error:
    main()
  File "/data00/home/someone/projects/unilm/layoutlmft/examples/run_xfun_ser.py", line 241, in main
    train_result = trainer.train(resume_from_checkpoint=checkpoint)
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/trainer.py", line 1120, in train
    tr_loss += self.training_step(model, inputs)
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/trainer.py", line 1522, in training_step
    loss = self.compute_loss(model, inputs)
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/transformers/trainer.py", line 1556, in compute_loss
    outputs = model(**inputs)
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 161, in forward
    outputs = self.parallel_apply(replicas, inputs, kwargs)
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py", line 171, in parallel_apply
    return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 86, in parallel_apply
    output.reraise()
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/_utils.py", line 428, in reraise
    raise self.exc_type(msg)
RuntimeError: Caught RuntimeError in replica 0 on device 0.
Original Traceback (most recent call last):
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/nn/parallel/parallel_apply.py", line 61, in _worker
    output = module(*input, **kwargs)
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/data00/home/someone/projects/unilm/layoutlmft/layoutlmft/models/layoutlmv2/modeling_layoutlmv2.py", line 864, in forward
    return_dict=return_dict,
  File "/data00/home/someone/anaconda3/envs/layoutlmft/lib/python3.7/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/data00/home/someone/projects/unilm/layoutlmft/layoutlmft/models/layoutlmv2/modeling_layoutlmv2.py", line 779, in forward
    position_ids=visual_position_ids,
  File "/data00/home/someone/projects/unilm/layoutlmft/layoutlmft/models/layoutlmv2/modeling_layoutlmv2.py", line 668, in _calc_img_embeddings
    embeddings = visual_embeddings + position_embeddings + spatial_position_embeddings
RuntimeError: The size of tensor a (4) must match the size of tensor b (2) at non-singleton dimension 0

Hi tengerye,
For the first OOM issue, would you mind to try to reduce the batch_size to 1 and test it again? And can you monitor the GPU memory usage at that time?
For the second issue, seems there are some implementation issues from your code, so you can log the size of visual_embeddings, position_embeddings, spatial_position_embeddings. And I would assume the batch size of these three tensor are different, so we can do the following debugging process.

@wgx998877 Thank you for your kind reply.
For the first issue, batch_size=1 works, but it is not essentially a OOM issue. The reason is the T4 GPU has 16G memory, which is surely capable for the batch_size=2.
After all, I have located the problem. It will be triggered if you run without DDP but with multiple GPUs. In more details, the error rises because the Detectron2 does not support DP while huggingface does.
In my humble option, I would suggest decouple the training from the huggingface framework.


fish: NixOS module is broken because of /share/fish/vendor_completions.d

Issue description
The fish NixOS module, enabled by programs.fish.enable = true; is broken for me on the nixos-unstable channel. I first commented over on the PR which I believe caused this: https://github.com/NixOS/nixpkgs/pull/14526#discussion_r69010724.
Steps to reproduce
When I sudo nixos-rebuild switch I get this:
cannot create directory `/nix/store/m3rrr54qspwiwyzn4gjrys36km6jz1g6-system-path//share/fish/vendor_completions.d': No such file or directory at /nix/store/xz5k60frmvvrj16lf7b0d8h3p0l4l7xw-builder.pl line 186.
builder for ‘/nix/store/bm5q3hs3pnijrjx1yrr647pslmzl986g-system-path.drv’ failed with exit code 2
cannot build derivation ‘/nix/store/z8bwgpzs4wiiv72rm4anc4mx1ixph1w2-nixos-system-conway-16.09pre85931.125ffff.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/z8bwgpzs4wiiv72rm4anc4mx1ixph1w2-nixos-system-conway-16.09pre85931.125ffff.drv’ failed

There is a broken-looking path in there with a double slash: /nix/store/m3rrr54qspwiwyzn4gjrys36km6jz1g6-system-path//share/fish/vendor_completions.d.
I later realized this error only occurs if you have no packages with /share/fish/vendor_completions.d. So, technically, I can work around this error by adding docker to environment.systemPackages. This also means that to reproduce you must remove any packages with that path.
Technical details

System: NixOS 16.09pre85931.125ffff (Flounder)
Nix version: 1.11.2
Nixpkgs version: 16.09pre85931.125ffff

That doesn’t seem to be the fault of the fish module, as this minimal system shows, which builds just fine:
nix-build -E '(import <nixpkgs/nixos> { configuration = { programs.fish.enable = true; }; }).vm'

What is the last commit where it still works? Has it worked at all in the past?

@Profpatsch Ah, nice example. Sorry for jumping to conclusions.
I minimized my error-inducing config and ended up with this, which you should be able to reproduce the problem with:
nix-build -E '(import <nixpkgs/nixos> { configuration = { programs.fish.enable = true;  services.xserver = { enable = true; desktopManager.kde5.enable = true; }; }; }).vm'

I'm not sure yet what part of KDE5 triggers the problem.

FYI: I have the same issue and I don't have kde5 enabled.

@rasendubi can you create an invocation like the ones above?

I've tried to do that yesterday but failed. I'll be busy during the week but will try again next weekend.
FWIW, my full config is available at github -- adding programs.enable.fish = true; breaks it for me.

The problem seems environment.pathsToLink = [ "/share" ]; which is enabled by e.g. KDE and some others:
nix-build -E '(import <nixpkgs/nixos> { configuration = { programs.fish.enable = true; environment.pathsToLink = ["/share"]; }; }).vm'

I confirm I have this in my config, too.

Found and fixed the issue. See https://github.com/NixOS/nixpkgs/pull/16821.

So I think this was ultimately fixed by https://github.com/NixOS/nixpkgs/pull/16828? I'll check it out later when I have access to NixOS.


Sanitize supports only one tag

Whether it was made intentionally or not, src/sanitize.js supports only one <em> tag. Are you planning to add some more important tags ( i.e <script>) or better yet let a developer himself to pass a Regex as an argument?

I suppose there should be also some support of tags with attributes, i.e. <em data-foo='bar'> will not be properly sanitized as the opening tag doesn't match /<em>|<\/em>/g.

Purpose of this utility is unclear. Maybe we should remove it instead of trying to build yet another sanitizing engine.

I think it would be a nice little feature over ramda/lodash libraries. As best to my knowledge only lodash has some sort of 'sanitizing engine' (https://lodash.com/docs/#escape), but it works a little bit different.

@Tom910 we really need the third opinion =)

/cc @osorokotyaga

We already have string/escape, and building another sanitize tool will be overkill to library purpose, so I'll better remove it at all.


add free text field (int / float) option

add the option to mold the trees with a manually typed amount of water

Done and closed due to several pull requests. See this issue https://github.com/technologiestiftung/giessdenkiez-de/issues/352


use babylon instead of espree

since it supports experimental features and Flow (#364)
PS: I have a branch working locally, will push it soon.

v0.9.0 just shipped with this by default!

This is huge, thank you :+1:


Corrected minor typo in README.md

Found minor type in readme: "waterfall charts can be provided". Corrected to "waterfall charts can provide".

Thanks! I made the suggested change.


Move mirror routes to a different function in galley/pkg/config/analysis/analyzers/virtualservice/util.go

Bug description
The utility function getRouteDestinations returns the routes and the mirrors. This is an issue both because the name of the function is misleading, and also because the routes and mirrors aren't on the same branch of the YAML tree and so it becomes impossible to tell from context where the error is if a url happens to be duplicated.
We should move the mirror paths into a separate util function, fix the analyzers, and make the error messages clearer.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure

@jasonwzm @monsteredc FYI