Impacted versions:
13.0 Documentation
Steps to reproduce:
go to https://www.odoo.com/documentation/13.0/reference/javascript_api.html#

Expected behavior:
https://www.odoo.com/documentation/12.0/reference/javascript_api.html#

There's a section about Uninstall existing npm, but the recommendations for upgrading are scattered in the issues.

The relationship between node, npm and nvm is not clear and it's not obvious if upgrading npm should be done through nvm or at least in a way that doesn't break nvm.

As a new custodian user, I'm trying to understand the usage of variables in policies. There seems to be multiple types of variables.

A non-exhaustive list for a beginner can be:

• vars in a policy yaml
• [standard runtime variables for in

Ex:

&& rm -rf \
         /var/lib/apt/lists/* \
         /tmp/* \
         /var/tmp/* \
         /usr/share/man \
         /usr/share/doc \
-        /usr/share/doc-base
+        /usr/share/doc-base \
+        /root/.cache/pip

Ref: https://pip.pypa.io/en/stable/reference/pip_install/#caching

It would be nice to have a healthcheck without writing YAML file.
I'm starting minio service, and it has 2 routes k8s style Liveness and Readiness. More here https://docs.min.io/docs/minio-monitoring-guide.html

Is it make any sense to implement such a feature?

Add documentation comments to all of the VmOrTemplate operations methods

Detailed description of the problem

from #164 :

We are trying to provide an update for the Lychee Cloudron app. The current version is 3.1.6 and the new version will be 3.2.8-fixed. Since this is for Cloudron, the built-in updater is disabled, since on Cloudron apps run on a read-only filesystem. For reference, our app packaging code can be found at https://git.cloudron.io/cloudron/lyche

Hey there! Asking here as I couldn't answer this from the docs: is there a way we can run Toodles on a project (Node.js in this case), and generate a bunch of HTML/CSS/JS files that we can host along with other static reports we generate on every PR?

# fc29
dnf install -y docker docker-compose

# docker-1.13.1-62.git9cb56fd.fc29.src.rpm
# docker-compose-1.22.0-2.fc29.src.rpm

What's a good way to make this (only installing from a limited set of package repos) optional?

There is a ton of documentation here and that's great, however, the first introduction to this tool is overwhelming and should be simplified. You may want to move some of the more stable documentation to the Wiki and reference it from the ReadMe.

Is this a bug or feature request?

FR

What is the current behavior?

not in the tree

What is the expected or desired behavior?

should be under the section "System"

A window may wish to be moved to a different workspace. This should be handled in client_message_event.

In order to do this, we need to be able to move an arbitrary client to a workspace. This can be achieved by factoring out the client {cutting,pasting} logic from op_{cut,paste} into their own functions.

_NET_WM_DESKTOP also needs to be added to ewmh_net_atoms.

Describe the solution you'd like

The Samples for Steeltoe 3.0 (master) need to reflect the updates we have added.
This ticket requests a complete review of the Samples in the repo to update them for the latest implementation.