Description
I get the following warnings once a minute:

2020-06-23 23:11:13,900 [salt.loaded.int.fileserver.roots:180 ][WARNING ][24993] Skipped invalid cache mtime entry in /var/cache/salt/master/roots/mtime_map: /srv/salt/a/b/c/ifcfg-eth0:0:1533517049.0

2020-06-23 23:11:13,901 [salt.loaded.int.fileserver.roots:180 ][WARNING ][24993] Skipped invalid cache mtime entry in /var/cache/salt

Describe the bug
QR Code Scanner fails to scan input fields on Send Transaction view when scanning QR Code contains an EIP-681 URI

Example URI

ethereum:0x46c69f4424043e720a704330748cf3c593656b9c

To Reproduce
Steps to reproduce the behavior:

1. Go to Send Transaction view
2. Click on QR Code scanner
3. Position QR Code in front of Webcam
4. QR Code scanner closes

I reinstalled a k3s cluster built with --no-extras and added `--k3s-extra-args="--flannel-backend=host-gw". The cluster failed to start.

I logged in and saw that the output of ps showed the following:

14760 ?        Ssl    0:40 /usr/local/bin/k3s server --cluster-init --tls-san 10.68.0.63 --flannel-backend=host-gw--n

Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

I have tried the classic .env with REACT_APP prefix, but it does not work, I guess that is only for react-script.
Does this package it support something similar?
Thanks

Description

We need a volunteer to update all the guides, terraform automation and cloud-config.txt to use the release 0.9.0

The assets are in this repo, so you shouldn't have too hard of a time finding stuff. Bear in mind we now have a dependency on docker-compose.yaml and that may need to be downloaded before faasd install.

Feel free to ask questions here.

The new cloud-config.t

There are numerous areas in the kernel where a heap allocation failure is being silently ignored, merely asserted against or otherwise mishandled. Assertions may suffice for allocations on initialization (where system bringup would otherwise be impossible), but allocation failures which may reasonably happen during runtime must be addressed.

See, for example, #1199; all the various calls to the