The connection to the server <IP_ADDRESS>:443 was refused

I followed the doc Kubernetes Installation with Vagrant & CoreOS to deploy a Kubernetes env. After the deployment using vagrant up, I can't access the cluster.
vagrant$ export KUBECONFIG="${KUBECONFIG}:$(pwd)/kubeconfig"
vagrant$ kubectl config use-context vagrant-multi
switched to context "vagrant-multi".
vagrant$ kubectl get nodes
The connection to the server <IP_ADDRESS>:443 was refused - did you specify the right host or port?

After ssh into c1,
vagrant$ vagrant ssh c1
CoreOS alpha (1045.0.0)
Last login: Fri May 13 07:24:04 2016 from <IP_ADDRESS>
Update Strategy: No Reboots
Failed Units: 2
  coreos-cloudinit-412108170.service
  update-engine.service
core@c1 ~ $ journalctl -u kubelet
-- No entries --
core@c1 ~ $ systemctl list-units
  UNIT                                                                                LOAD      ACTIVE     SUB          JOB   DESCRIPTION
  boot.automount                                                                           loaded    active     waiting            Boot partition Automount Point
  proc-sys-fs-binfmt_misc.automount                                                        loaded    active     waiting            Arbitrary Executable File Formats File System Automount Point
  sys-devices-pci0000:00-0000:00:01.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device loaded    active     plugged            VBOX_HARDDISK EFI-SYSTEM
  sys-devices-pci0000:00-0000:00:01.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda2.device loaded    active     plugged            VBOX_HARDDISK BIOS-BOOT
  sys-devices-pci0000:00-0000:00:01.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda3.device loaded    active     plugged            VBOX_HARDDISK USR-A
  sys-devices-pci0000:00-0000:00:01.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda4.device loaded    active     plugged            VBOX_HARDDISK USR-B
  sys-devices-pci0000:00-0000:00:01.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda6.device loaded    active     plugged            VBOX_HARDDISK OEM
  sys-devices-pci0000:00-0000:00:01.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda7.device loaded    active     plugged            VBOX_HARDDISK OEM-CONFIG
  sys-devices-pci0000:00-0000:00:01.1-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda9.device loaded    active     plugged            VBOX_HARDDISK ROOT
  sys-devices-pci0000:00-0000:00:01.1-ata1-host0-target0:0:0-0:0:0:0-block-sda.device      loaded    active     plugged            VBOX_HARDDISK
  sys-devices-pci0000:00-0000:00:03.0-virtio0-net-eth0.device                              loaded    active     plugged            Virtio network device
  sys-devices-pci0000:00-0000:00:08.0-virtio1-net-eth1.device                              loaded    active     plugged            Virtio network device
  sys-devices-platform-serial8250-tty-ttyS0.device                                         loaded    active     plugged            /sys/devices/platform/serial8250/tty/ttyS0
  sys-devices-platform-serial8250-tty-ttyS1.device                                         loaded    active     plugged            /sys/devices/platform/serial8250/tty/ttyS1
  sys-devices-platform-serial8250-tty-ttyS2.device                                         loaded    active     plugged            /sys/devices/platform/serial8250/tty/ttyS2
  sys-devices-platform-serial8250-tty-ttyS3.device                                         loaded    active     plugged            /sys/devices/platform/serial8250/tty/ttyS3
  sys-devices-virtual-tty-ttyprintk.device                                                 loaded    active     plugged            /sys/devices/virtual/tty/ttyprintk
  sys-subsystem-net-devices-eth0.device                                                    loaded    active     plugged            Virtio network device
  sys-subsystem-net-devices-eth1.device                                                    loaded    active     plugged            Virtio network device
  -.mount                                                                                loaded    active     mounted            /
  boot.mount                                                                               loaded    active     mounted            Boot partition
  dev-hugepages.mount                                                                      loaded    active     mounted            Huge Pages File System
  dev-mqueue.mount                                                                         loaded    active     mounted            POSIX Message Queue File System
  media.mount                                                                              loaded    active     mounted            External Media Directory
  run-user-500.mount                                                                       loaded    active     mounted            /run/user/500
  sys-kernel-debug.mount                                                                   loaded    active     mounted            Debug File System
  tmp.mount                                                                                loaded    active     mounted            Temporary Directory
  usr-share-oem.mount                                                                      loaded    active     mounted            /usr/share/oem
  usr.mount                                                                                loaded    active     mounted            /usr
  coreos-cloudinit-vagrant-user.path                                                       loaded    active     running            coreos-cloudinit-vagrant-user.path
  motdgen.path                                                                             loaded    active     waiting            Watch for update engine configuration changes
  systemd-ask-password-console.path                                                        loaded    active     waiting            Dispatch Password Requests to Console Directory Watch
  systemd-ask-password-wall.path                                                           loaded    active     waiting            Forward Password Requests to Wall Directory Watch
<EMAIL_ADDRESS>                                loaded    active     waiting            Watch for a cloud-config at /var/lib/coreos-install/user_data
  init.scope                                                                               loaded    active     running            System and Service Manager
  session-2.scope                                                                          loaded    active     running            Session 2 of user core
  audit-rules.service                                                                      loaded    active     exited             Load Security Auditing Rules
● coreos-cloudinit-412108170.service                                                       not-found failed     failed             coreos-cloudinit-412108170.service
  coreos-setup-environment.service                                                         loaded    active     exited             Modifies /etc/environment for CoreOS
  dbus.service                                                                             loaded    active     running            D-Bus System Message Bus
  early-docker.service                                                                     loaded    active     running            Early Docker Application Container Engine
  flanneld.service                                                                         loaded    activating start        start Network fabric for containers
<EMAIL_ADDRESS>                                                                     loaded    active     running            Getty on tty1
  kmod-static-nodes.service                                                                loaded    active     exited             Create list of required static device nodes for the current kernel
  ldconfig.service                                                                         loaded    active     exited             Rebuild Dynamic Linker Cache
  locksmithd.service                                                                       loaded    activating auto-restart       Cluster reboot manager
  sshd-keygen.service                                                                      loaded    active     exited             Generate sshd host keys
  sshd@1-<IP_ADDRESS>:22-<IP_ADDRESS>:62272.service                                               loaded    active     running            OpenSSH per-connection server daemon (<IP_ADDRESS>:62272)
<EMAIL_ADDRESS>                             loaded    active     exited             Load cloud-config from /usr/share/oem/cloud-config.yml
<EMAIL_ADDRESS>                                          loaded    active     exited             Load cloud-config from /var/tmp/hostname.yml
<EMAIL_ADDRESS>                                          loaded    active     exited             Load cloud-config from /var/tmp/networks.yml
  systemd-hwdb-update.service                                                              loaded    active     exited             Rebuild Hardware Database
  systemd-journal-catalog-update.service                                                   loaded    active     exited             Rebuild Journal Catalog
  systemd-journal-flush.service                                                            loaded    active     exited             Flush Journal to Persistent Storage
  systemd-journald.service                                                                 loaded    active     running            Journal Service
  systemd-logind.service                                                                   loaded    active     running            Login Service
  systemd-networkd.service                                                                 loaded    active     running            Network Service
  systemd-random-seed.service                                                              loaded    active     exited             Load/Save Random Seed
  systemd-resolved.service                                                                 loaded    active     running            Network Name Resolution
  systemd-sysctl.service                                                                   loaded    active     exited             Apply Kernel Variables
  systemd-sysusers.service                                                                 loaded    active     exited             Create System Users
  systemd-timesyncd.service                                                                loaded    active     running            Network Time Synchronization
  systemd-tmpfiles-setup-dev.service                                                       loaded    active     exited             Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service                                                           loaded    active     exited             Create Volatile Files and Directories
  systemd-udev-settle.service                                                              loaded    active     exited             udev Wait for Complete Device Initialization
  systemd-udev-trigger.service                                                             loaded    active     exited             udev Coldplug all Devices
  systemd-udevd.service                                                                    loaded    active     running            udev Kernel Device Manager
  systemd-update-done.service                                                              loaded    active     exited             Update is Completed
  systemd-update-utmp.service                                                              loaded    active     exited             Update UTMP about System Boot/Shutdown
  systemd-user-sessions.service                                                            loaded    active     exited             Permit User Sessions
  systemd-vconsole-setup.service                                                           loaded    active     exited             Setup Virtual Console
● update-engine.service                                                                    masked    failed     failed             update-engine.service
<EMAIL_ADDRESS>           loaded    active     exited             Load cloud-config from /var/lib/coreos-vagrant/vagrantfile-user-data
  -.slice                                                                                loaded    active     active             Root Slice
  system-addon\x2dconfig.slice                                                             loaded    active     active             system-addon\x2dconfig.slice
  system-addon\x2drun.slice                                                                loaded    active     active             system-addon\x2drun.slice
  system-getty.slice                                                                       loaded    active     active             system-getty.slice
  system-sshd.slice                                                                        loaded    active     active             system-sshd.slice
  system-system\x2dcloudinit.slice                                                         loaded    active     active             system-system\x2dcloudinit.slice
  system-user\x2dcloudinit.slice                                                           loaded    active     active             system-user\x2dcloudinit.slice
  system.slice                                                                             loaded    active     active             System Slice
  user-500.slice                                                                           loaded    active     active             User Slice of core
  user.slice                                                                               loaded    active     active             User and Session Slice
  dbus.socket                                                                              loaded    active     running            D-Bus System Message Bus Socket
  docker.socket                                                                            loaded    active     listening          Docker Socket for the API
  early-docker.socket                                                                      loaded    active     running            Early Docker Socket for the API
  rkt-metadata.socket                                                                      loaded    active     listening          rkt metadata service socket
  sshd.socket                                                                              loaded    active     listening          OpenSSH Server Socket
  systemd-coredump.socket                                                                  loaded    active     listening          Process Core Dump Socket
  systemd-initctl.socket                                                                   loaded    active     listening          /dev/initctl Compatibility Named Pipe
  systemd-journald-audit.socket                                                            loaded    active     running            Journal Audit Socket
  systemd-journald-dev-log.socket                                                          loaded    active     running            Journal Socket (/dev/log)
  systemd-journald.socket                                                                  loaded    active     running            Journal Socket
  systemd-networkd.socket                                                                  loaded    active     running            Network Service Netlink Socket
  systemd-udevd-control.socket                                                             loaded    active     running            udev Control Socket
  systemd-udevd-kernel.socket                                                              loaded    active     running            udev Kernel Socket
  basic.target                                                                             loaded    active     active             Basic System
  cryptsetup.target                                                                        loaded    active     active             Encrypted Volumes
  getty.target                                                                             loaded    active     active             Login Prompts
  local-fs-pre.target                                                                      loaded    active     active             Local File Systems (Pre)
  local-fs.target                                                                          loaded    active     active             Local File Systems
  multi-user.target                                                                        loaded    active     active             Multi-User System
  network.target                                                                           loaded    active     active             Network
  paths.target                                                                             loaded    active     active             Paths
  remote-fs.target                                                                         loaded    active     active             Remote File Systems
  slices.target                                                                            loaded    active     active             Slices
  sockets.target                                                                           loaded    active     active             Sockets
  swap.target                                                                              loaded    active     active             Swap
  sysinit.target                                                                           loaded    active     active             System Initialization
  system-config.target                                                                     loaded    active     active             Load system-provided cloud configs
  time-sync.target                                                                         loaded    active     active             System Time Synchronized
  timers.target                                                                            loaded    active     active             Timers
  user-config.target                                                                       loaded    active     active             Load user-provided cloud configs
  logrotate.timer                                                                          loaded    active     waiting            Daily Log Rotation
  rkt-gc.timer                                                                             loaded    active     waiting            Periodic Garbage Collection for rkt
  systemd-tmpfiles-clean.timer                                                             loaded    active     waiting            Daily Cleanup of Temporary Directories

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
JOB    = Pending job for the unit.

116 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
core@c1 ~ $ systemctl list-units | grep kube
core@c1 ~ $ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::a00:27ff:fe89:25dc  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:89:25:dc  txqueuelen 1000  (Ethernet)
        RX packets 1357  bytes 143116 (139.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1163  bytes 132458 (129.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::a00:27ff:fec9:fa05  prefixlen 64  scopeid 0x20<link>
        ether 08:00:27:c9:fa:05  txqueuelen 1000  (Ethernet)
        RX packets 28  bytes 5948 (5.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 41  bytes 4489 (4.3 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 6  bytes 498 (498.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6  bytes 498 (498.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

core@c1 ~ $ netstat -tulpn
(No info could be read for "-p": geteuid()=500 but you should be root.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp6       0      0 :::22                   :::*                    LISTEN      -
udp        0      0 <IP_ADDRESS>:68            <IP_ADDRESS>:*                           -
udp6       0      0 fe80::a00:27ff:fe89:546 :::*

No service is running on port 443.
And I've already updated the git repo to the latest commit 03f86ac

I've got the same problem. For me it worked yesterday (it downloaded CoreOS-alpha-1032.1.0-hvm (ami-75730a15) ).
Today it downloads CoreOS-alpha-1045.0.0-hvm (ami-d3629fb3).
In journalctl I've got following log:
May 13 08:51:13 ip-10-0-0-19.us-west-2.compute.internal kubelet-wrapper[3434]: image: using image from file /usr/share/rkt/stage1-fly.aci
May 13 08:51:13 ip-10-0-0-19.us-west-2.compute.internal kubelet-wrapper[3434]: run: open /usr/share/rkt/stage1-fly.aci.asc: no such file or directory
May 13 08:51:13 ip-10-0-0-19.us-west-2.compute.internal systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
May 13 08:51:13 ip-10-0-0-19.us-west-2.compute.internal systemd[1]: kubelet.service: Unit entered failed state.
May 13 08:51:13 ip-10-0-0-19.us-west-2.compute.internal systemd[1]: kubelet.service: Failed with result 'exit-code'.
May 13 08:51:23 ip-10-0-0-19.us-west-2.compute.internal systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.
May 13 08:51:23 ip-10-0-0-19.us-west-2.compute.internal systemd[1]: Stopped kubelet.service.
May 13 08:51:23 ip-10-0-0-19.us-west-2.compute.internal systemd[1]: Started kubelet.service.

@dixudx It can take some time for the services to come up. Can you get the log of the kubelet? journalctl -u kubelet?

Getting the same error when following the tutorial.
journalctl -u kubelet:

May 13 14:10:11 localhost kubelet-wrapper[1713]: image: using image from file /usr/share/rkt/stage1-fly.aci
May 13 14:10:11 localhost kubelet-wrapper[1713]: run: open /usr/share/rkt/stage1-fly.aci.asc: no such file or directory
May 13 14:10:11 localhost systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
May 13 14:10:11 localhost systemd[1]: kubelet.service: Unit entered failed state.
May 13 14:10:11 localhost systemd[1]: kubelet.service: Failed with result 'exit-code'.
May 13 14:10:21 localhost systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.

```

@dixudx: I had the same problem today even though my cluster configuration (running in AWS) was working fine. It seems like a problem with the latest CoreOS alpha AMI (CoreOS-alpha-1045.0.0, ami-46ff772a). Downgrading to previous AMI (CoreOS-alpha-1032.1.0, ami-8d74fde1) did the trick for me.
Since you are using the same CoreOS version I was, maybe you are experiencing the same problem. Try using an earlier version.

Running this in vagrant, same issue with the alpha-1032.1.0

This is due to an issue in the latest CoreOS alpha: https://github.com/coreos/bugs/issues/1282
@AlmaasAre You are seeing the same error output below in v1032.1.0?
open /usr/share/rkt/stage1-fly.aci.asc: no such file or directory
Can you confirm os version by running cat /etc/os-release

@aaronlevy
vagrant$ vagrant ssh c1
CoreOS alpha (1045.0.0)
Last login: Fri May 13 07:24:04 2016 from <IP_ADDRESS>
Update Strategy: No Reboots
Failed Units: 2
  coreos-cloudinit-412108170.service
  update-engine.service

The version of CoreOS is CoreOS alpha (1045.0.0)

@philips I destroyed all the instances and rebuilt them. The same errors still occurred.
vagrant$ vagrant status
Current machine states:

e1                        running (virtualbox)
e2                        running (virtualbox)
e3                        running (virtualbox)
c1                        running (virtualbox)
c2                        running (virtualbox)
w1                        running (virtualbox)
w2                        running (virtualbox)

This environment represents multiple VMs. The VMs are all listed
above with their current state. For more information about a specific
VM, run `vagrant status NAME`.

vagrant$ vagrant ssh c1
CoreOS alpha (1045.0.0)
Last login: Sat May 14 06:06:59 2016 from <IP_ADDRESS>
Failed Units: 2
  coreos-cloudinit-562055073.service
  update-engine.service
core@c1 ~ $ journalctl -u kubelet
-- No entries --
core@c1 ~ $ journalctl -f -u kubelet
-- Logs begin at Sat 2016-05-14 06:04:53 UTC. --
^C
core@c1 /etc/systemd $ systemctl list-unit-files | grep kubelet
kubelet.service                        disabled
core@c1 /etc/systemd $ ls
bootchart.conf  coredump.conf  journal-remote.conf  journal-upload.conf  journald.conf  logind.conf  network  resolved.conf  system  system.conf  timesyncd.conf  user  user.conf

Actually kubelet is not enabled. There is no doubt no service will run on port 443 and the connection is refused.

@aaronlevy I have the similar with alpha-1032.1.0
CoreOS alpha (1032.1.0) Last login: Sat May 14 12:30:47 2016 from <IP_ADDRESS> Failed Units: 1   coreos-cloudinit-539161959.service
coreos-cloudinit-539161959.service                                 loaded failed failed

My failure was due to launching from windows and dos cariage return screwing up the install scripts, I ran dos2unix on the files and had no failed services on vagrant up. However none of my services actually started but I think that is unrelated to this issue.

beta channel (1010.3.0) works for me. alpha and stable don't.
core@localhost ~ $ cat /etc/os-release
NAME=CoreOS
ID=coreos
VERSION=1010.3.0
VERSION_ID=1010.3.0
BUILD_ID=2016-05-05-0730
PRETTY_NAME="CoreOS 1010.3.0 (MoreOS)"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

@dixudx

running journalctl -u kubelet
May 14 17:00:24 localhost kubelet-wrapper[1555]: E0514 17:00:24.921573    1555 event.go:202] Unable to write event: 'Post http://<IP_ADDRESS>:8080/api/v1/namespaces/default/events: dial tcp <IP_ADDRESS>:8080: connection refused' (m
May 14 17:00:29 localhost kubelet-wrapper[1555]: W0514 17:00:29.690894    1555 manager.go:408] Failed to update status for pod "_()": Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/pods/kube-apiserver-<IP_ADDRESS>: di
May 14 17:00:29 localhost kubelet-wrapper[1555]: W0514 17:00:29.691023    1555 manager.go:408] Failed to update status for pod "_()": Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/pods/kube-controller-manager-172.17
May 14 17:00:29 localhost kubelet-wrapper[1555]: W0514 17:00:29.691130    1555 manager.go:408] Failed to update status for pod "_()": Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/pods/kube-proxy-<IP_ADDRESS>: dial t
May 14 17:00:29 localhost kubelet-wrapper[1555]: W0514 17:00:29.691233    1555 manager.go:408] Failed to update status for pod "_()": Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/pods/kube-scheduler-<IP_ADDRESS>: di
May 14 17:00:34 localhost kubelet-wrapper[1555]: E0514 17:00:34.922813    1555 event.go:202] Unable to write event: 'Post http://<IP_ADDRESS>:8080/api/v1/namespaces/default/events: dial tcp <IP_ADDRESS>:8080: connection refused' (m
May 14 17:00:36 localhost kubelet-wrapper[1555]: E0514 17:00:36.979359    1555 kubelet.go:1764] Failed creating a mirror pod for "kube-apiserver-<IP_ADDRESS>_kube-system(fe526ebd0d4f824a977453f27071d2be)": Post http://127.0.0.
May 14 17:00:36 localhost kubelet-wrapper[1555]: W0514 17:00:36.980390    1555 manager.go:408] Failed to update status for pod "_()": Get http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/pods/kube-apiserver-<IP_ADDRESS>: di
May 14 17:00:37 localhost kubelet-wrapper[1555]: E0514 17:00:37.985139    1555 kubelet.go:1764] Failed creating a mirror pod for "kube-apiserver-<IP_ADDRESS>_kube-system(fe526ebd0d4f824a977453f27071d2be)": namespaces "kube-sys
May 14 17:00:39 localhost kubelet-wrapper[1555]: E0514 17:00:39.996764    1555 kubelet.go:1764] Failed creating a mirror pod for "kube-scheduler-<IP_ADDRESS>_kube-system(967e140df40ec8506c3772b9b2350fef)": namespaces "kube-sys
May 14 17:00:40 localhost kubelet-wrapper[1555]: E0514 17:00:40.998579    1555 kubelet.go:1764] Failed creating a mirror pod for "kube-scheduler-<IP_ADDRESS>_kube-system(967e140df40ec8506c3772b9b2350fef)": namespaces "kube-sys
May 14 17:00:41 localhost kubelet-wrapper[1555]: I0514 17:00:41.756673    1555 kubelet.go:1165] Successfully registered node <IP_ADDRESS>
May 14 17:00:44 localhost kubelet-wrapper[1555]: W0514 17:00:44.667546    1555 request.go:627] Throttling request took 154.672568ms, request: PATCH:http://<IP_ADDRESS>:8080/api/v1/namespaces/default/events/<IP_ADDRESS>.144e7dbd32
May 14 17:00:44 localhost kubelet-wrapper[1555]: W0514 17:00:44.867487    1555 request.go:627] Throttling request took 194.683779ms, request: PATCH:http://<IP_ADDRESS>:8080/api/v1/namespaces/default/events/<IP_ADDRESS>.144e7dbd32
May 14 17:00:45 localhost kubelet-wrapper[1555]: W0514 17:00:45.067432    1555 request.go:627] Throttling request took 195.269787ms, request: PATCH:http://<IP_ADDRESS>:8080/api/v1/namespaces/default/events/<IP_ADDRESS>.144e7dbd32
May 14 17:00:45 localhost kubelet-wrapper[1555]: W0514 17:00:45.268747    1555 request.go:627] Throttling request took 197.332501ms, request: PATCH:http://<IP_ADDRESS>:8080/api/v1/namespaces/default/events/<IP_ADDRESS>.144e7dbd32
May 14 17:00:45 localhost kubelet-wrapper[1555]: W0514 17:00:45.467423    1555 request.go:627] Throttling request took 193.648142ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:45 localhost kubelet-wrapper[1555]: W0514 17:00:45.670622    1555 request.go:627] Throttling request took 199.808155ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:45 localhost kubelet-wrapper[1555]: W0514 17:00:45.867488    1555 request.go:627] Throttling request took 192.526737ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:46 localhost kubelet-wrapper[1555]: W0514 17:00:46.068306    1555 request.go:627] Throttling request took 195.944512ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:46 localhost kubelet-wrapper[1555]: W0514 17:00:46.267527    1555 request.go:627] Throttling request took 192.974583ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:46 localhost kubelet-wrapper[1555]: W0514 17:00:46.468570    1555 request.go:627] Throttling request took 196.712591ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:46 localhost kubelet-wrapper[1555]: W0514 17:00:46.668133    1555 request.go:627] Throttling request took 191.818019ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:46 localhost kubelet-wrapper[1555]: W0514 17:00:46.867573    1555 request.go:627] Throttling request took 195.834716ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:47 localhost kubelet-wrapper[1555]: W0514 17:00:47.068113    1555 request.go:627] Throttling request took 191.340291ms, request: PATCH:http://<IP_ADDRESS>:8080/api/v1/namespaces/default/events/<IP_ADDRESS>.144e7dbd32
May 14 17:00:47 localhost kubelet-wrapper[1555]: W0514 17:00:47.271317    1555 request.go:627] Throttling request took 199.400464ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:47 localhost kubelet-wrapper[1555]: W0514 17:00:47.478771    1555 request.go:627] Throttling request took 195.475753ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:47 localhost kubelet-wrapper[1555]: W0514 17:00:47.668744    1555 request.go:627] Throttling request took 174.298305ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:47 localhost kubelet-wrapper[1555]: W0514 17:00:47.867233    1555 request.go:627] Throttling request took 194.596807ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:48 localhost kubelet-wrapper[1555]: W0514 17:00:48.067639    1555 request.go:627] Throttling request took 197.591491ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:48 localhost kubelet-wrapper[1555]: W0514 17:00:48.267527    1555 request.go:627] Throttling request took 196.16472ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:48 localhost kubelet-wrapper[1555]: W0514 17:00:48.467531    1555 request.go:627] Throttling request took 195.796106ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:00:48 localhost kubelet-wrapper[1555]: W0514 17:00:48.668619    1555 request.go:627] Throttling request took 191.811241ms, request: POST:http://<IP_ADDRESS>:8080/api/v1/namespaces/kube-system/events
May 14 17:01:15 localhost kubelet-wrapper[1555]: E0514 17:01:15.188429    1555 manager.go:309] NetworkPlugin cni failed on the status hook for pod 'kube-dns-v11-euy8w' - invalid CIDR address: Device "eth0" does not exist

@dixudx Works now, just took a while to boot up :)

The same issue still occurred on latest version 1047.0.0.
vagrant$ vagrant status
Current machine states:

e1                        running (virtualbox)
e2                        running (virtualbox)
e3                        running (virtualbox)
c1                        running (virtualbox)
c2                        running (virtualbox)
w1                        running (virtualbox)
w2                        running (virtualbox)

This environment represents multiple VMs. The VMs are all listed
above with their current state. For more information about a specific
VM, run `vagrant status NAME`.
vagrant$ export KUBECONFIG="${KUBECONFIG}:$(pwd)/kubeconfig"
vagrant$ kubectl config use-context vagrant-multi
switched to context "vagrant-multi".
vagrant$ kubectl get nodes
The connection to the server <IP_ADDRESS>:443 was refused - did you specify the right host or port?

vagrant$ vagrant ssh c1
CoreOS alpha (1047.0.0)
Last login: Sun May 15 13:12:03 2016 from <IP_ADDRESS>
Failed Units: 2
  coreos-cloudinit-192295069.service
  update-engine.service
core@c1 ~ $ journalctl -u kubelet
-- No entries --
core@c1 ~ $ cat /etc/os-release
NAME=CoreOS
ID=coreos
VERSION=1047.0.0
VERSION_ID=1047.0.0
BUILD_ID=2016-05-14-0118
PRETTY_NAME="CoreOS 1047.0.0 (MoreOS)"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"
core@c1 ~ $ journalctl -f -u kubelet
-- Logs begin at Sun 2016-05-15 13:09:40 UTC. --
^C
core@c1 ~ $ systemctl list-unit-files | grep kubelet
kubelet.service                        disabled

@AlmaasAre what do you mean taking a while to boot up on version 1032.1.0. Did you perform some manual operations. The services of CoreOS are managed by systemd.
core@c1 ~ $ systemctl list-unit-files | grep kubelet
kubelet.service                        disabled

From the above log, the service kubelet is disabled, not even in activating status, which means service kubelet is not currently governed or triggered by other services.

@dixudx Sorry, the kubelet service took a while to start.

Same issue here:
$ vagrant ssh c1
CoreOS alpha (1045.0.0)
Last login: Thu May 19 14:00:54 2016 from <IP_ADDRESS>
Update Strategy: No Reboots
Failed Units: 1
update-engine.service
core@c1 ~ $ cat /etc/os-release
NAME=CoreOS
ID=coreos
VERSION=1045.0.0
VERSION_ID=1045.0.0
BUILD_ID=2016-05-11-2111
PRETTY_NAME="CoreOS 1045.0.0 (MoreOS)"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"
core@c1 ~ $ journalctl -u kubelet
..
..
May 19 14:04:19 c1 systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.
May 19 14:04:19 c1 systemd[1]: Stopped kubelet.service.
May 19 14:04:19 c1 systemd[1]: Starting kubelet.service...
May 19 14:04:19 c1 systemd[1]: Started kubelet.service.
May 19 14:04:19 c1 kubelet-wrapper[2433]: image: using image from file /usr/share/rkt/stage1-fly.aci
May 19 14:04:19 c1 kubelet-wrapper[2433]: run: open /usr/share/rkt/stage1-fly.aci.asc: no such file or directory
May 19 14:04:19 c1 systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
May 19 14:04:19 c1 systemd[1]: kubelet.service: Unit entered failed state.
May 19 14:04:19 c1 systemd[1]: kubelet.service: Failed with result 'exit-code'.
May 19 14:04:30 c1 systemd[1]: kubelet.service: Service hold-off time over, scheduling restart.
May 19 14:04:30 c1 systemd[1]: Stopped kubelet.service.
May 19 14:04:30 c1 systemd[1]: Starting kubelet.service...
May 19 14:04:30 c1 systemd[1]: Started kubelet.service.
May 19 14:04:30 c1 kubelet-wrapper[2464]: image: using image from file /usr/share/rkt/stage1-fly.aci
May 19 14:04:30 c1 kubelet-wrapper[2464]: run: open /usr/share/rkt/stage1-fly.aci.asc: no such file or directory
May 19 14:04:30 c1 systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE
May 19 14:04:30 c1 systemd[1]: kubelet.service: Unit entered failed state.
May 19 14:04:30 c1 systemd[1]: kubelet.service: Failed with result 'exit-code'.
core@c1 ~ $ systemctl | grep kube
kubelet.service                                                                          loaded    activating auto-restart kubelet.service
core@c1 ~ $ netstat -tulpn
(No info could be read for "-p": geteuid()=500 but you should be root.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp6       0      0 :::22                   :::*                    LISTEN      -
udp        0      0 <IP_ADDRESS>:8472            <IP_ADDRESS>:*                           -
udp        0      0 <IP_ADDRESS>:68            <IP_ADDRESS>:*                           -
udp6       0      0 fe80::a00:27ff:fe89:546 :::*                                -
core@c1 ~ $ systemctl list-unit-files
UNIT FILE                              STATE
boot.automount                         static
proc-sys-fs-binfmt_misc.automount      static
org.freedesktop.hostname1.busname      static
org.freedesktop.import1.busname        static
org.freedesktop.locale1.busname        static
org.freedesktop.login1.busname         static
org.freedesktop.machine1.busname       static
org.freedesktop.network1.busname       static
org.freedesktop.resolve1.busname       static
org.freedesktop.systemd1.busname       static
org.freedesktop.timedate1.busname      static
dev-disk-by\x2dlabel-OEM.device        static
boot.mount                             static
dev-hugepages.mount                    static
dev-mqueue.mount                       static
media-configdrive.mount                static
media-configvirtfs.mount               static
media-ovfenv.mount                     static
media.mount                            static
proc-fs-nfsd.mount                     static
proc-sys-fs-binfmt_misc.mount          static
proc-xen.mount                         static
sys-fs-fuse-connections.mount          static
sys-kernel-config.mount                static
sys-kernel-debug.mount                 static
tmp.mount                              static
usr-share-oem.mount                    static
var-lib-machines.mount                 static
var-lib-nfs-rpc_pipefs.mount           static
coreos-cloudinit-vagrant-user.path     static
motdgen.path                           static
systemd-ask-password-console.path      static
systemd-ask-password-wall.path         static
<EMAIL_ADDRESS>                 static
<EMAIL_ADDRESS>                static
<EMAIL_ADDRESS>                   static
audit-rules.service                    disabled
auth-rpcgss-module.service             static
<EMAIL_ADDRESS>                      disabled
blk-availability.service               disabled
calico-node.service                    disabled
clean-ca-certificates.service          static
console-getty.service                  disabled
console-shell.service                  disabled
<EMAIL_ADDRESS>             static
coreos-cloudinit-vagrant-mkdir.service static
<EMAIL_ADDRESS>     disabled
coreos-metadata.service                disabled
coreos-setup-environment.service       disabled
coreos-tmpfiles.service                static
dbus-org.freedesktop.hostname1.service static
dbus-org.freedesktop.import1.service   static
dbus-org.freedesktop.locale1.service   static
dbus-org.freedesktop.login1.service    static
dbus-org.freedesktop.machine1.service  static
dbus-org.freedesktop.network1.service  disabled
dbus-org.freedesktop.resolve1.service  disabled
dbus-org.freedesktop.timedate1.service static
dbus.service                           static
debug-shell.service                    disabled
dhcpcd.service                         disabled
dm-event.service                       disabled
docker.service                         disabled
early-docker.service                   disabled
emergency.service                      static
etcd.service                           static
etcd2.service                          disabled
extend-filesystems.service             static
flanneld.service                       enabled
fleet.service                          disabled
fstrim.service                         static
<EMAIL_ADDRESS>                       disabled
<EMAIL_ADDRESS>                  static
initrd-cleanup.service                 static
initrd-parse-etc.service               static
initrd-switch-root.service             static
initrd-udevadm-cleanup-db.service      static
ip6tables-restore.service              disabled
ip6tables-store.service                disabled
ip6tables.service                      indirect
iptables-restore.service               disabled
iptables-store.service                 disabled
iptables.service                       indirect
iscsid-initiatorname.service           static
iscsid.service                         disabled
issuegen.service                       static
kmod-static-nodes.service              static
kubelet.service                        enabled
ldconfig.service                       static
locksmithd.service                     disabled
logrotate.service                      static
lvm2-lvmetad.service                   disabled
lvm2-monitor.service                   disabled
<EMAIL_ADDRESS>                 static
mcstrans.service                       disabled
<EMAIL_ADDRESS>         static
<EMAIL_ADDRESS>           static
<EMAIL_ADDRESS>                       static
mdmonitor.service                      static
motdgen.service                        static
multipathd.service                     disabled
nfs-idmapd.service                     static
nfs-mountd.service                     static
nfs-server.service                     disabled
nfs-utils.service                      static
nfsd.service                           disabled
ntpd.service                           disabled
ntpdate.service                        disabled
polkit.service                         static
pwcheck.service                        disabled
quotaon.service                        static
realmd.service                         static
remount-root.service                   static
remount-usr.service                    static
rescue.service                         static
rkt-gc.service                         static
rkt-metadata.service                   disabled
rngd.service                           disabled
rpc-idmapd.service                     static
rpc-mountd.service                     static
rpc-statd-notify.service               static
rpc-statd.service                      static
rpcbind.service                        disabled
rsyncd.service                         disabled
saslauthd.service                      disabled
<EMAIL_ADDRESS>                disabled
setup-nsswitch.service                 static
sntp.service                           disabled
ssh-key-proc-cmdline.service           disabled
sshd-keygen.service                    static
sshd.service                           disabled
<EMAIL_ADDRESS>                        static
sssd.service                           disabled
<EMAIL_ADDRESS>            static
systemd-ask-password-console.service   static
systemd-ask-password-wall.service      static
<EMAIL_ADDRESS>           static
systemd-binfmt.service                 static
systemd-bootchart.service              disabled
systemd-bus-proxyd.service             static
<EMAIL_ADDRESS>            static
systemd-exit.service                   static
systemd-firstboot.service              static
systemd-fsck-root.service              static
<EMAIL_ADDRESS>                static
systemd-halt.service                   static
<EMAIL_ADDRESS>    static
systemd-hibernate.service              static
systemd-hostnamed.service              static
systemd-hwdb-update.service            static
systemd-hybrid-sleep.service           static
systemd-importd.service                static
systemd-initctl.service                static
systemd-journal-catalog-update.service static
systemd-journal-flush.service          static
systemd-journal-gatewayd.service       indirect
systemd-journal-remote.service         indirect
systemd-journal-upload.service         disabled
systemd-journald.service               static
systemd-kexec.service                  static
systemd-localed.service                static
systemd-logind.service                 static
systemd-machine-id-commit.service      static
systemd-machined.service               static
systemd-modules-load.service           static
systemd-networkd-wait-online.service   disabled
systemd-networkd.service               disabled
<EMAIL_ADDRESS>              disabled
systemd-poweroff.service               static
systemd-quotacheck.service             static
systemd-random-seed.service            static
systemd-reboot.service                 static
systemd-remount-fs.service             static
systemd-resolved.service               disabled
systemd-rfkill.service                 static
systemd-suspend.service                static
systemd-sysctl.service                 static
systemd-sysusers.service               static
systemd-timedated.service              static
systemd-timesyncd.service              disabled
systemd-tmpfiles-clean.service         static
systemd-tmpfiles-setup-dev.service     static
systemd-tmpfiles-setup.service         static
systemd-udev-settle.service            static
systemd-udev-trigger.service           static
systemd-udevd.service                  static
systemd-update-done.service            static
systemd-update-utmp-runlevel.service   static
systemd-update-utmp.service            static
systemd-user-sessions.service          static
systemd-vconsole-setup.service         static
tcsd.service                           disabled
tpmd.service                           disabled
update-ca-certificates.service         static
update-engine-stub.service             disabled
update-engine.service                  masked
user-cloudinit-proc-cmdline.service    static
<EMAIL_ADDRESS>              static
user-config-ovfenv.service             static
user-configdrive.service               static
user-configvirtfs.service              static
<EMAIL_ADDRESS>                        static
uuidd.service                          indirect
<EMAIL_ADDRESS>                      static
xenserver-pv-version.service           static
-.slice                                static
machine.slice                          static
system.slice                           static
user.slice                             static
dbus.socket                            static
dm-event.socket                        disabled
docker.socket                          disabled
early-docker.socket                    disabled
fleet.socket                           static
git-daemon.socket                      disabled
iscsid.socket                          disabled
lvm2-lvmetad.socket                    disabled
multipathd.socket                      disabled
rkt-metadata.socket                    disabled
sshd.socket                            disabled
syslog.socket                          static
systemd-bus-proxyd.socket              static
systemd-coredump.socket                static
systemd-initctl.socket                 static
systemd-journal-gatewayd.socket        disabled
systemd-journal-remote.socket          disabled
systemd-journald-audit.socket          static
systemd-journald-dev-log.socket        static
systemd-journald.socket                static
systemd-networkd.socket                disabled
systemd-rfkill.socket                  static
systemd-udevd-control.socket           static
systemd-udevd-kernel.socket            static
uuidd.socket                           disabled
basic.target                           static
bluetooth.target                       static
busnames.target                        static
cryptsetup-pre.target                  static
cryptsetup.target                      static
ctrl-alt-del.target                    disabled
default.target                         static
early-docker.target                    static
emergency.target                       static
exit.target                            disabled
final.target                           static
getty.target                           static
graphical.target                       static
halt.target                            disabled
hibernate.target                       static
hybrid-sleep.target                    static
initrd-fs.target                       static
initrd-root-fs.target                  static
initrd-switch-root.target              static
initrd.target                          static
kexec.target                           disabled
local-fs-pre.target                    static
local-fs.target                        static
machines.target                        disabled
multi-user.target                      static
network-online.target                  static
network-pre.target                     static
network.target                         static
nfs-client.target                      disabled
nss-lookup.target                      static
nss-user-lookup.target                 static
paths.target                           static
poweroff.target                        disabled
printer.target                         static
reboot.target                          disabled
remote-fs-pre.target                   static
remote-fs.target                       disabled
rescue.target                          disabled
rpcbind.target                         static
shutdown.target                        static
sigpwr.target                          static
sleep.target                           static
slices.target                          static
smartcard.target                       static
sockets.target                         static
sound.target                           static
suspend.target                         static
swap.target                            static
sysinit.target                         static
system-config.target                   static
system-update.target                   static
time-sync.target                       static
timers.target                          static
umount.target                          static
user-config.target                     static
fstrim.timer                           disabled
logrotate.timer                        static
<EMAIL_ADDRESS>             static
rkt-gc.timer                           disabled
systemd-tmpfiles-clean.timer           static
update-engine-stub.timer               disabled
295 unit files listed.

Also with newer box 1053.2.0, still an issue:
vagrant ssh c1
CoreOS alpha (1053.2.0)
Last login: Tue May 24 17:24:05 2016 from <IP_ADDRESS>
Failed Units: 1
  update-engine.service

i tryed to vagrant up with 1010.5.0 and 1053.2.0 .... no luck.
localbox$ kubectl get nodes
The connection to the server <IP_ADDRESS>:443 was refused - did you specify the right host or port?
cannot find the error. journal -f shows a loop while downloading/trying to start flannel.

This seems to be touching on a few different issues. I'll try and touch on them, but if you are still having an issue, please open a new ticket (at this point this issue covers a few different issues).
Originally, there was an error where the rkt-fly stage1 could not be found (coreos/bugs#1282) -- this should be resolved in all alpha/beta/stable channels.
the "update-engine.service" failed unit is actually because we disable auto-updates to slightly improve the user-experience of not having a server reboot immediately on first boot. But nothing is broken.
@wmangano would you mind opening a new issue if you are still having problems? It might have to do with flannel not being able to contact etcd -- but if it's still and issue we can dig further.

for those who just stumble onto this issue, the downloads do often take a while as discussed above.  to confirm that your downloads are still in transit, you can:

vagrant ssh c1 (or other nodes in your cluster)
look at the kubelets log, journalctl -u kubelet.  look at the bottom for a download progress update!

@cdaringe
Just spent a bunch of time hunting this down as well.
Could some output be put onto stdout/console so that this isn't such a mystery to the uninitiated?
I think it would save a lot of people some trouble and hunting. I think it would be very helpful.
Thanks,
Matt

Another option might just to put a blocking loop at the end of the vagrant script which waits for the api-server to be available (and outputs something like "waiting for api..."

Opened https://github.com/coreos/coreos-kubernetes/issues/806 to track this

I think a lot of user are using coreos-kubernetes so why nobody there would update the configs to help us?
kubelet service is not enabled by default so I started it like,
systemctl list-unit-files | grep kubelet
kubelet.service                        disabled
sudo systemctl start kubelet
sudo systemctl enable kubelet
Then I had issue says,
coreos-cloudinit[905]: 2018/08/29 22:36:54 Failed to apply cloud-config: Unit etcd2.service not found.
Aug 29 22:51:25 w1 flannel-wrapper[1588]: E0829 22:51:25.555657    1588 main.go:349] Couldn't fetch network config: client: etcd cluster is unavailable or misconfigured; error #0: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused
I searched and found this,
https://github.com/coreos/bugs/issues/2395
They say both etcd2 and fleet are deprecated on CoreOs.
Docs says Docker is used by default, and I didn't update to use Rockets, but in reality Rockets are working instead of Docker by default!
core@w2 ~ $  rkt list
UUID		APP		IMAGE NAME					STATE		CREATED		STARTED		NETWORKS
28ec0fc9	hyperkube	quay.io/coreos/hyperkube:v1.7.3_coreos.0	running		27 minutes ago	27 minutes ago
8997c8bb	hyperkube	quay.io/coreos/hyperkube:v1.7.3_coreos.0	exited garbage	1 hour ago	1 hour ago
dd3086fa	hyperkube	quay.io/coreos/hyperkube:v1.7.3_coreos.0	exited garbage	53 minutes ago	53 minutes ago
ec7268f7	flannel		quay.io/coreos/flannel:v0.10.0			running		1 minute ago	1 minute ago
But seems it listens only on <IP_ADDRESS>, so other workers can't connect to it,
tcp        0      0 <IP_ADDRESS>:2379          <IP_ADDRESS>:*               LISTEN      -
Aug 29 22:24:38 w3 flannel-wrapper[1322]: E0829 22:24:38.741764    1322 main.go:349] Couldn't fetch network config: client: etcd cluster is unavailable or misconfigured; error #0: dial tcp <IP_ADDRESS>:2379: getsockopt: connection refused


Docs dead link

Documentation link https://keycard.status.im/api/ in README is dead. Please update.
Thanks

Also, an URL to 'android installer' targets discontinued project that has readme-redirect link to another repo, so could be updated as well... Unless it is intended, in that case, it would be a good idea to say(write) so.

Thanks for the report, fixed!


Enable pylint rules to prefer list and dict literal syntax

https://pylint.readthedocs.io/en/latest/user_guide/messages/refactor/use-dict-literal.html
https://pylint.readthedocs.io/en/latest/user_guide/messages/refactor/use-list-literal.html

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

30 of 30 (100.0%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.37%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3399

Relevant Lines:
3564

💛  - Coveralls


tweet-limit doesn't work as option

https://dev.twitter.com/web/embedded-timelines/parameters
It seams that only chrome option works :-/

doing something like that
        twitter-timeline(
              ng-if="slug == 'beauty'"
              twitter-timeline-type='list'
              twitter-timeline-owner-screen-name='"sylv3k"'
              twitter-timeline-slug='"beauty"'
              twitter-timeline-options='{"tweet-limit": 2, "theme": "dark", "chrome": "noheader nofooter noborders transparent"}')

tweet-limit have no effect.

"height": 900 … works well.

Thanks for the report! I'll check this out when I get a chance.

You have to use the syntax that Twitter requires for their factory functions (not the embedded widgets). Here's a reference. Basically, replace tweet-limit with tweetLimit.


Gitpod support

Use case
To ease contributions by providing a zero install process like gitpod.io. Also mentioned in #1076
Solution/User Experience
Fork project and open in gitpod.io before making PR requests. This is already available for the typescript version
Just adding .gitpod.yml would be enough
# This configuration file was automatically generated by Gitpod.
# Please adjust to your needs (see https://www.gitpod.io/docs/config-gitpod-file)
# and commit this file to your remote git repository to share the goodness with others.

tasks:
  - init: make dev

I have test this, and it already works:

Alternative solutions
There is already support for CodeSpaces, but this is not open to all developers.
Acknowledgment

[X] This feature request meets Lambda Powertools Tenets
[X] Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript

This seems to be a general issue with Gitpod slowing down sometimes when running the unit tests.

Note, this was mentioned in another issue but no tracking issue was logged?


Added Profile

@siriuswapnil  contribute to https://github.com/Ishaan28malik/Get-Dev-Resources instead


Test classes for SuppyItem and Inventory classes added

Codecov Report

Merging #126 (1521224) into master (5d8a885) will increase coverage by 0.74%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #126      +/-   ##
============================================
+ Coverage     70.85%   71.59%   +0.74%
- Complexity      593      596       +3
============================================
  Files            97       97
  Lines          2000     2007       +7
  Branches        231      231
============================================
+ Hits           1417     1437      +20
+ Misses          505      491      -14
- Partials         78       79       +1

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/Inventory.java
92.59% <100.00%> (+10.77%)
:arrow_up:

...main/java/seedu/address/model/item/SupplyItem.java
78.57% <100.00%> (+28.57%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-24-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1607

Questions ?
Please refer to the Backport tool documentation


Update the README file

hey @Aaryanbanga , I created a repo but really need your help with crafting a better read me file.


Rasa Action servers makes everything slow

Hey,  I just test rasa with a minimal and default  example on the same laptop. Chatting over shell or a UI is rather slow, because of the action server I think. So without using any advanced stuff or model you get a large latency by just using the server.
In v1 of rasa before the action server this was not the case (if I remember correctly).
Is there a way to avoid this or just not using the action server and using just the plain actions.py?

Thanks for submitting this feature request 🚀 @ArjaanBuijk will get back to you about it soon! ✨

@tide90 ,
Thanks for reporting this.
Can you please post details of your experience, including the rasa version and your test bot, to the rasa community forum?
Feel free to tag me in your forum post and I will try to help you find the cause.

@ArjaanBuijk  I just recognized that without anything and just sending an query to the action server and back takes about 2 second  for. Just used one of the example on the github example folder. SO It think it just the http request which takes so long, but why and how can you make it faster?
So it would be nice if someone could clarify or maybe it is too trivial and wonder why no one else hat this issue...


fix: issues with firebase dependencies

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This fixes firebase dependency collection. Note: this still needs to be improved but we are working within the limits of firebase, which is that it doesn't upload our beautifully trace node_modules but insists on rerunning an npm install in the cloud.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Sorry for late merge!


Updated callout in view of debug.

There were

Became

Red color is confusing me and I tried to find errors in logs . Please merge :)

we could apply the status color instead, as it is in the status field.

Possible. Beginning you can merge my PR, neutral view.

Changing color sounds better to me.

Thanks!


Add logback-classic dependency

This is being "moved" from kiwi-parent. See #132 in kiwi-parent.

In reality, we already defined logback-classic and logback-core in the BOM, but were using thelogback.version property inherited from kiwi-parent. The logback dependency and version are both removed in kiwi-parent 2.0.0, so we only need to define version properties for these dependencies.


Pin button becomes inactive a while after pressing

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Actions Performed:

Open the app, login with any account.
In LHN, Tap on an user that you have any conversation before, click on the Pin button at the top.
Notice that the Pin button becomes active then inactive in a while.

Expected Result:
Pin button shouldn’t blink after pressing.
Actual Result:
The Pin button becomes active then inactive in a while.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] iOS / native

Version Number: 1.2.54-2
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/212497544-d1c8f0bd-8742-4d8a-a52e-36cb204d1f3c.MP4
Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1673540030046229
View all open jobs on GitHub

This issue has not been updated in over 14 days.  eroding to Weekly issue.

This issue has not been updated in over 15 days.  eroding to Monthly issue.
P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!


add missing d2gs s->c packets

see https://d2mods.info/forum/viewtopic.php?t=62821

https://webcache.googleusercontent.com/search?q=cache%3AktxiPaN-wkAJ%3Awww.blizzhackers.cc%2Fviewtopic.php%3Ft%3D444264 &cd=1&hl=en&ct=clnk&gl=fr

https://github.com/dkuwahara/OmegaBot/blob/398128b4cbc96194065da510a7482c521ecf6f90/Connections/Readers/D2gsReader.cs#L14

Example of implementation of packet by size :
"D2GS_SETBYTEATTR": ["array",{"count":2, "type": "lu8"}]

That makes it unusable but will make it possible to get next packets.

https://github.com/eezstreet/OpenD2/blob/master/Shared/D2Packets.hpp

https://github.com/dkuwahara/OmegaBot/blob/master/Connections/Readers/D2gsReader.cs#L14

done


prevent empty matching macros to stop events propagation

#47 - in the handleEvent, the _findMatchingMacros can return an empty array. The check for match if(matchingMacros) will return true for an empty array result and therefore stop the event propagation for that key pressed. if(matchingMacros) replaced with if(isPresent(matchingMacros)) and test added

Released in v0.3.3


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

https://github.com/mzaks/Entitas
https://github.com/mzaks/Entitas-Swift

Other Corrected URLs

Was
Now

http://slideshare.net/sschmid/uniteeurope-2015
http://www.slideshare.net/sschmid/uniteeurope-2015

Thanks! :)

:tada:


[ Direct2D1 ] Exception is thrown by any input in TextBox if TextAlignment="Center"

MCVE:
    <TextBox
        MinWidth="120"
        HorizontalAlignment="Center"
        VerticalAlignment="Center"
        TextAlignment="Center" />

Details about exception:
Exception thrown: 'System.InvalidOperationException' in Avalonia.Layout.dll
An unhandled exception of type 'System.InvalidOperationException' occurred in Avalonia.Layout.dll
Invalid Arrange rectangle.

Version: 0.9.0-preview8
Related: #3294

It was fixed already somewhere.


Plan to support free-threaded Python

In free-threaded build, importing pydantic_core currently results in a segmentation fault. PyO3 v0.23 introduces support for free-threaded Python and addresses this issue. Is there any short-term plan to migrate to PyO3 0.23?
Currently I see the following blockers:

Jiter support for free-threaded Python (https://github.com/pydantic/jiter/pull/165)
Making SerializationCallable Sync, which isn't because of CollectWarnings and SerRecursionState contain RefCells
Replacing IntoPy/ToPyObject by IntoPyObject
Replacing calls to deprecated APIs (*_bound methods, into_py/to_object)

Yes, I was testing PyO3 0.23 (when it was just a git branch) in #1450 and plan to proceed further with that upgrade this week.
There is potentially additional work required beyond your list to actually make free-threaded support ok, both here and in pydantic (where there are a bunch of caches which may or may not be thread-safe).

PyO3 has now been bumped but there's a build failure on aarch64 main. I'm trying to identify the cause. Before we can call free-threaded Python supported we should probably add extensive testing here and downstream in the pydantic main Python repo. I think this is realistically a Pydantic 2.11 feature cc @sydney-runkle


[Test] Write Unit Tests for find_duplicates Function

Describe the test request
I would like to add unit tests for the find_duplicates function to ensure its accuracy and reliability. These tests should cover various scenarios, including cases with:
No duplicates found
Multiple duplicates found
Edge cases, such as empty directories or files with the same name but different content
Motivation
Writing unit tests for the find_duplicates function is crucial to maintain code quality and ensure that any future changes do not introduce regressions. By verifying the function's behavior across different scenarios, we can ensure that it consistently provides accurate results, which is essential for user trust and satisfaction with TwinTrim.
Steps to Reproduce
Set Up Test Environment:
Clone the repository and set up the testing framework (e.g., unittest or pytest).
Create Test Cases:
Test Case 1: Provide a directory with no duplicate files and assert that the result is an empty list.
Test Case 2: Provide a directory with multiple duplicates and assert that the function correctly identifies all duplicates.
Test Case 3: Test with a directory that contains a mix of files, some of which are duplicates, and assert the expected output.
Test Case 4: Test with an empty directory and assert that the result is an empty list.
Example Code Snippet:
python
Copy code
import unittest
from twintrim import find_duplicates
class TestFindDuplicates(unittest.TestCase):
def test_no_duplicates(self):
result = find_duplicates('/path/to/empty_directory')
self.assertEqual(result, [])
def test_multiple_duplicates(self):
    result = find_duplicates('/path/to/test_directory_with_duplicates')
    self.assertEqual(result, ['file1.txt', 'file2.txt'])  # Replace with actual expected duplicates

def test_edge_case(self):
    result = find_duplicates('/path/to/directory_with_non_duplicate_files')
    self.assertEqual(result, [])

if name == 'main':
unittest.main()
Additional context
The current implementation of the find_duplicates function lacks comprehensive testing, which poses a risk for future code changes. By adding these unit tests, we can create a safety net that ensures any modifications to the function maintain its intended behavior. Additionally, the tests will serve as documentation for how the function is expected to behave in different scenarios.

A duplicate issue, well you asked for this. This is your second warning @Jaswithadabbiru , any more invalid issues and you'll face serious consequences includign but not limited to ban fromt he repoisitory and disciplinary actions. Closing this now.


WIP: introduce configurable PVC

reports directory is initialized in deployment as EmptyDir
EmptyDir is replaced with PVC
The Pod reboots after deployment modification
PVC is configurable thru the CR
If no PVC config is provided, a default is used
packaged tar files use a timestamp in filename instead of uuid

Codecov Report

Merging #58 (4c90670) into master (e8b956b) will decrease coverage by 1.57%.
The diff coverage is 38.29%.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
- Coverage   85.35%   83.78%   -1.58%
==========================================
  Files           9        9
  Lines        1195     1227      +32
==========================================
+ Hits         1020     1028       +8
- Misses        114      135      +21
- Partials       61       64       +3

Flag
Coverage Δ

unittests
83.78% <38.29%> (-1.58%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

controllers/kokumetricsconfig_controller.go
65.03% <30.95%> (-4.57%)
:arrow_down:

packaging/packaging.go
82.95% <100.00%> (+0.15%)
:arrow_up:

sources/handler.go
96.49% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e8b956b...4c90670. Read the comment docs.

Codecov Report

Merging #58 (4c90670) into master (e8b956b) will decrease coverage by 1.57%.
The diff coverage is 38.29%.

@@            Coverage Diff             @@
##           master      #58      +/-   ##
==========================================
- Coverage   85.35%   83.78%   -1.58%
==========================================
  Files           9        9
  Lines        1195     1227      +32
==========================================
+ Hits         1020     1028       +8
- Misses        114      135      +21
- Partials       61       64       +3

Flag
Coverage Δ

unittests
83.78% <38.29%> (-1.58%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

controllers/kokumetricsconfig_controller.go
65.03% <30.95%> (-4.57%)
:arrow_down:

packaging/packaging.go
82.95% <100.00%> (+0.15%)
:arrow_up:

sources/handler.go
96.49% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e8b956b...4c90670. Read the comment docs.


new installation of the SDK ( 3bot2 container) "could not setup alerthandler"

Installed the 3bot SDK from scratch:
/tmp/sjx containers-delete
/tmp/jsx threebot

Installation successful but starting kosmos:
root@3bot:~# kosmos
could not setup alerthandler
Sat 28 14:24:31 ASECLASSES/JSBase.py - 379 - _logging_enable_check              : EXCEPTION:
    AttributeError("'MyEnv_' object has no attribute 'log_includes'")
--TRACEBACK------------------
/sandbox/lib/jumpscale/jumpscale_generated.py in bcdb
    1357    self._bcdb =  BCDBFactory()
/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py in __init__
    59    self.__init_class()
/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py in __init_class
    142    self._logger_set(children=False, parents=False)
/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py in _logger_set
    407    if not self._logging_enable_check():
/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py in _logging_enable_check
    379    if check(j.core.myenv.log_includes) and not check(j.core.myenv.log_excludes):
-----------------------------

Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/sandbox/lib/jumpscale/Jumpscale/data/bcdb/__init__.py", line 28, in flush_bcdb
    for bcdb in j.data.bcdb.find():
  File "/sandbox/lib/jumpscale/jumpscale_generated.py", line 1357, in bcdb
    self._bcdb =  BCDBFactory()
  File "/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py", line 66, in __init__
    self._init(**kwargs)
  File "/sandbox/lib/jumpscale/Jumpscale/data/bcdb/BCDBFactory.py", line 23, in _init
    self._path = j.sal.fs.getDirName(os.path.abspath(__file__))
  File "/sandbox/lib/jumpscale/jumpscale_generated.py", line 1737, in fs
    self._fs =  SystemFS()
  File "/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py", line 59, in __init__
    self.__init_class()
  File "/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py", line 142, in __init_class
    self._logger_set(children=False, parents=False)
  File "/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py", line 407, in _logger_set
    if not self._logging_enable_check():
  File "/sandbox/lib/jumpscale/Jumpscale/core/BASECLASSES/JSBase.py", line 379, in _logging_enable_check
    if check(j.core.myenv.log_includes) and not check(j.core.myenv.log_excludes):
AttributeError: 'MyEnv_' object has no attribute 'log_includes'
root@3bot:~#

Did a pull from all the repo's:
oot@3bot:/sandbox/code/github/threefoldtech# for name in `ls`
> do
> cd $name
> echo $name
> git branch
> git pull
> cd ..
> done
home
* master
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
Already up to date.
jumpscaleX_builders
* development
Already up to date.
jumpscaleX_core
* development
remote: Enumerating objects: 62, done.
remote: Counting objects: 100% (62/62), done.
remote: Compressing objects: 100% (34/34), done.
remote: Total 62 (delta 35), reused 43 (delta 28), pack-reused 0
Unpacking objects: 100% (62/62), done.
From github.com:threefoldtech/jumpscaleX_core
   4f8f7a4f..f1f97c13  unstable              -> origin/unstable
   802ec5f0..796be412  unstable_jsxcontainer -> origin/unstable_jsxcontainer
Already up to date.
jumpscaleX_libs
* development
remote: Enumerating objects: 9, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 9 (delta 4), reused 6 (delta 3), pack-reused 0
Unpacking objects: 100% (9/9), done.
From github.com:threefoldtech/jumpscaleX_libs
   6d460b5..f1b5a29  unstable   -> origin/unstable
Already up to date.
jumpscaleX_libs_extra
* development
remote: Enumerating objects: 19, done.
remote: Counting objects: 100% (19/19), done.
remote: Compressing objects: 100% (19/19), done.
remote: Total 19 (delta 5), reused 6 (delta 0), pack-reused 0
Unpacking objects: 100% (19/19), done.
From github.com:threefoldtech/jumpscaleX_libs_extra
   63e156a..d89e7d6  unstable   -> origin/unstable
Already up to date.
jumpscaleX_threebot
* development
Already up to date.
jumpscaleX_weblibs
* master
Already up to date.

Did not solve it.

Saw that there were updates to the unstable branch regardind logging.  Checked out unstable and development and both still do'nt start kosmos
root@3bot:~# kosmos
could not setup alerthandler
Sun 29 10:43:44 ASECLASSES/JSBase.py - 379 - _logging_enable_check              : EXCEPTION:
    AttributeError("'MyEnv_' object has no attribute 'log_includes'")

was something people we working on for another feature / bug.  for future documention and installation usage will create and use a seperate branch
Issues no longer relevant


Adds Universal Link & AASA Testing Tool

Thanks for your contribution! This is a template that can make it easier when submitting your contribution:
Your Project: getuniversal.link
Project URL: _http://getuniversal.link/_
Category: Tools
Description: This is a tool for developers that helps test Universal Link behavior and helps to verify integrity of the Apple App Site Association file.
Demo: https://getuniversal.link/youtube.com
Tutorial Video: https://www.youtube.com/watch?v=HvhMCTELX70
Social Proof: https://iosdevweekly.com/issues/661
Inclusion requirements:

[ ] Has 50 GitHub stargazers or more
[X] Only one project/change is in this pull request
[ ] Isn't an archived project
[ ] Has more than one contributor
[ ] Has unit tests, integration tests or UI tests
[ ] Addition in alphabetical order (bottom of category)
[ ] Supports iOS 12 / tvOS 10 or later
[ ] Supports Swift 4 or later
[ ] Has a commit from less than 2 years ago
[ ] Has a clear README in English

:heart: Awesome iOS Contributors

@aryamansharda Thanks for contributing!


ESP-IDF example?

The description says this supports ESP-IDF framework, but I don't see any example or guide to setup in that framework.
BTW I see that https://github.com/m5stack/M5Stack-IDF was archived, so is this supposed to be the new home?

Hello @phatpaul
Currently there is no sample code available for ESP-IDF, but this library works as a component of ESP-IDF.
Place the M5Unified and M5GFX folders in the components folder of your project.
After that you can use them by putting #include <M5Unified.h> in your source files.
Please use ESP-IDF v4.x.x since ESP-IDF v5.x.x is not yet supported.
Since M5Unified is a latecomer, I would like to maintain it as much as possible to solve the dissatisfaction of the earlier libraries.

Hello @lovyan03
Is there a reference ESP-IDF v4.x.x build? I tried building a hello world image using your instructions of placing said folders on the components folder, and I got different build errors on v4.1.4 and v4.4.3 on my hello word project.
#include <M5Unified.h>

void setup(){
  M5.begin();
  M5.Lcd.printf("hello world");
}

void loop() {
  M5.update();

}

When I ran idf.py build on v4.4.2 and v4.4.3 these errors are thrown
[4/6] Linking CXX executable m5core2test.elf
FAILED: m5core2test.elf

And then
esp-idf-v4.4.2/components/freertos/port/port_common.c:135: undefined reference to `app_main'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
ninja failed with exit code 1

I apologize for the inconvenience, but examples is configured for ArduinoESP32.
For ESP-IDF, you need to prepare your own app_main function.
The setup function and loop function are not necessary for ESP-IDF because they are Arduino rules.

hello @hp27596
I apologize for the inconvenience, but examples is configured for ArduinoESP32.
For ESP-IDF, you need to prepare your own app_main function.
The setup function and loop function are not necessary for ESP-IDF because they are Arduino rules.

I understand. Pardon my ignorance as there was not a lot of examples or guides to begin with to work with the library.
How would one get started with using the library as a component of ESP IDF? From what I gathered it might look something like this. Can you point us to the right direction?
#include <Arduino.h>
#include <M5Unified.h>

extern "C" void app_main()
{
    initArduino();
    M5.begin();
    M5.Display.printf("Hello world!");
}

Is that correct?

@hp27596
I don't see any particular problem with your way of writing.
M5Unified is designed to be ArduinoESP32 library independent.
If the functionality you need is included in ArduinoESP32, you can add it.

Hello @lovyan03
Thanks for your help.
I've found the culprit of the problem. This needs to be in the main folder's CMakeLists.txt for ESP IDF to compile. Other than that there's a few quirks that I've worked out too.
set(SOURCES main.cpp)
I finally have a working demo which is great. I'm leaving the repo here in case anyone is interested in using the library in bare ESP IDF like I do and want some working examples.
https://github.com/hp27596/m5core2idfdemo

Hi, thank you for this great library. Not many vendors support esp-idf.
I could just add a new board into platformio.ini file and the M5Stack AtomS3 worked well with the existing code. The cool stuff is now the small Atom display, which works too.
This is the configuration in platformio.ini:
[env:m5stack-atoms3]
platform = espressif32
board = m5stack-atoms3
framework = espidf
build_flags = -DM5STACK_ATOMS3
lib_deps =<EMAIL_ADDRESS>

This ticket can be closed as resolved; as people indicate it works and are happy with this.


Write unit tests for common model implementations

Model 'M' should be trained and tested on a pre-defined (possibly synthetic) data set and the test results should be within some reasonable bounds.

In optimization package, solvers should be tested on common synthetic data sets to see if they reasonably converge.

In the data pipes package, write unit tests to test composability and function of the data pipes API

This is a super set of the aims of #5 .

Added test suits for the following models as a start.

Feed forward neural networks: 3b9fc1ff31f1cbe7d8535fcc3806dd8683c260a2
Generalized Linear Models (regression): cdf0d4ad658ad47fff6ec3582bb69759284e1b14


Fix PVC not cleaned up error

Signed-off-by: dongyun.xzh<EMAIL_ADDRESS>
Ⅰ. Describe what this PR does
Fix PVC not cleaned up error.
The cause is: the time difference between PVC Deletion Operation and the existence check may be too short for the controller to decide whether the PVC is successfully cleaned.
This PR modifies the code to a wait-until style to make sure the PVC is deleted when the func is returned.
Ⅱ. Does this pull request fix one issue?

fixes #2139
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.

pkg/ddc/*/delete_volume_test.go

Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

@TrafalgarZZZ Could you enhance test code coverage?

/lgtm
/approve


DeprecationWarning from loaderUtils

When I run build, I get the feedback information from console：
(node:1670) DeprecationWarning: loaderUtils.parseQuery() received a non-string value which can be problematic, see https://github.com/webpack/loader-utils/issues/56
parseQuery() will be replaced with getOptions() in the next major version of loader-utils.

<EMAIL_ADDRESS>

@kidney Yep loader-utils >= v1.0.0 had a API breaking change API getOptions I'm on it :), feel free to ignore this warning meanwhile

It's still there, right?

@NekR Which version of postcss-loader ?

"postcss-loader": "^2.0.6",
I'm not 100% sure if it's postcss-loader, but I got it when I started updating postcss related things, including the loader.

Nevermind, I found the problematic one, it was css-loader. Thanks!

For those following this chain here is the issue in css-loader.