-
Updated
May 30, 2021 - JavaScript
edge
Here are 545 public repositories matching this topic...
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
-
Updated
Aug 3, 2021 - Go
-
Updated
Aug 27, 2021 - HTML
Issue Summary
The stack generated has issues with the name of the regeneration queue when setting a domain name as name for the bucket (it doesn't pass the name constraints).
Actual behavior
The stack can not be created
Expected behavior
Be able to create the stack :)
Steps to reproduce
- Create an app with some page that needs dynamic regeneration and try to put it o
Description
If the Triton server build fails due to any reason, I have to delete the /tmp/citritonbuild/<backend> folders to prevent the next rebuild from throwing git repo already exists error.
Triton Information
r21.05
I am building the Triton server myself.
To Reproduce
uninstall one of the dependency needed by a backend.
run build.py with all the backends enabled
-
Updated
Aug 24, 2021 - JavaScript
SQL Insert Statement
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
-
Updated
Jul 16, 2021 - Go
-
Updated
Aug 30, 2021 - Go
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 :/
-
Updated
May 3, 2021 - JavaScript
The virtio_scsi driver enqueues buffers to the eventq but does not actually handle them on completion. The following events could be reported to the driver which require some action to be taken:
- transport reset: This may occur as a result of hotplug events or a device being reset. Sense codes cannot be relied on when new devices or busses appear, so this event needs to be handled.
- asynchro
-
Updated
Jul 6, 2021 - Dockerfile
-
Updated
Jul 13, 2021 - C++
Add events and logs in key places during service processing, such as allocate and release EIP, GoBGP synchronization Nexthop, Layer2 mode selection Node
-
Updated
Jul 21, 2021 - D
-
Updated
Aug 23, 2021 - Jupyter Notebook
Metrics support
It would be useful if Kuiper supported file-based rule and stream provisioning (i.e. importing) on startup. Currently rules and streams need to be created by someone using the client, or an application requesting creation via the Kuiper REST API.
Supporting file-based provisioning would allow someone to deploy Kuiper with a pre-defined set of streams and rules, removing the need for someone (or
-
Updated
Aug 11, 2021 - C++
Improve this page
Add a description, image, and links to the edge topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the edge topic, visit your repo's landing page and select "manage topics."


Describe the solution you'd like
It would be nice to have a way to control whether a VM starts on boot or not. Maybe a new
autostartoption to salt.states.virt.running and/or salt.states.virt.defined? Or maybe a new function?Describe alternatives you've considered
I'll probably use salt.modules.virt.set_autostart for now.