Do you want to request a feature or report a bug?

Expected behaviour

Mention is not treated as link for create preview card

Actual behaviour

Mastodon is thinking that mention from misskey is a link, and fetch for preview_card
![image](https://user-images.githu

When using AUFS as the storage driver in docker (or podman, etc.) then the maximum number of layers that can have data is "42".

This is because each layer that has data is unpacked into the file-system and then union mounted over each other. AUFS only allows a maximum of 42 layers to be mounted over each other.

The hard-limit is 127 data layers which is due to the maximum number of argu

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Is your feature request related to a problem? Please describe.
After draining a node from the Host overview page, agent logs show errors because there is no longer an agent on the node for Portainer to talk to. In the log you may see this error error: failed to read /sys/bus/pci/deviceserror: failed to read /sys/bus/pci/devices

Describe the solution you'd like
Redirect to Cluster

Currently when adding an item to your cart, it only updates the cart counter graphic for that browser instance, not all connected clients. Using SignalR it should be relatively straightforward to update the cart counter on all connected clients.

The problem as far as I understand is that libfoo.so's only knowledge about libcuda.so is its SONAME, which is libcuda.so.1, so a binary wanting to link in libfoo.so needs to know who to find libcuda.so.1 in order to verify the available symbols. Generally, ld's suggestion is to use -rpath-link to provide the path to the library, but the nvidia docker repository doesn't come with the symlink to li

Hi, I'm Yevgeny Pats Founder of Fuzzit - Continuous fuzzing as a service platform.

We have a free plan for OSS and I would be happy to contribute a PR if that's interesting.
The PR will include the following

• go-fuzz fuzzers (This is generic step not-connected to fuzzit)
• Continuous Fuzzing of master branch which will generate new

Expected behavior

skaffold debug recognizes my openfaas CRD and deploys it (even if it's not debuggable)

Actual behavior

skaffold debug fails because a CRD is being used in one of the manifests under deploy.kubectl.manifests:

skaffold debug -v=debug

The steps to get the laravel-horizon container up and running properly are very confusing, and not "officially" documented anywhere.

I've followed this and this, and while it appears to finally be working now, I don't know which of the steps I followed were actually necessary, and which may just