Description
The docs confused me a bit today: the Renderers page lists the gpg renderer as a text renderer. At the same time the salt.rendereres.gpg page uses it as a data renderer (last in the pipeline). This confused me for

This feature enables the ipsec backend for Flannel in the k3sup install command

Expected Behaviour

An additional flag to k3sup install should enable ipsec for Flannel as

Is your feature request related to a problem? Please describe.
I have a custom path on my NextJS app that I want to route through a custom Lambda@Edge function of my own, but this code overrides it even if I provide it i

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):

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

About this question, here is a unified reply.

We need to see this place where one is the definition and load the configuration.

https://github.com/sipeed/MaixPy/blob/master/components/micropython/port/builtin_py/board.py

If you don't provide the configuration, you won't get the concrete variable.

If it is SIPEED published hardware, the appropriate configuration is provided here.

htt

Hello,
Thank you for your work.
Would it be possible to add npm tasks to automatically publish to the Firefox and Chrome stores?
It is possible with:
https://www.npmjs.com/package/web-ext-submit FF
https://www.npmjs.com/package/chrome-webstore-upload-cli Chrome

I will submit a PR if I find some time :/

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