wsk | Web starter kit for simple web font-end development | Style Language library

they are packages which need to be installed separately

see https://github.com/apache?q=openwhisk-package&type=&language=&sort= for details

We stopped maintaining OpenWhisk for Minikube a while ago. With the availability of a full-fledged Kubernetes cluster built-in to Docker Desktop on MacOS and Windows and kind (https://kind.sigs.k8s.io) being available on all of our platforms supporting Minikube was more work than it was worth.

This error also comes while accessing action as a package, the name of your package and action is the same. Try this

The way you've phrased this question makes me think your main issue is conflating the build step with the application "runtime" (as in, when users are using your application), like when dispatchForm.js would ever be run. Gulp is a tool to generate out your project, but this is meant to happen way before any users are interacting with your site.

The SO question you linked is having express render the pug pages at "runtime", which, architecturally, is pretty different from having it happen at the build step with gulp.

If I'm understanding what you want correctly, off the top of my head there's 3 main ways to do it. The first would be by having the client-side JS manipulate the dom and change the page appropriately. You could use pug for this, rendered into a JS library via something like rollup-plugin-pug (found via this SO answer).

The second would be having this be an api call to a server, which then renders a pug template (which is what the SO question you linked is doing).

Or third, you could do something like rendering out all possible pages you'd want your users to go to at build time, and just make the dispatchForm.js just be sending them to the appropriate pages. In this case I'd recommend defining out these options in one place (in say, a json file) and having that be the source of a gulp pipeline. It gets a little zany having gulp generate multiple files from a single file, but you can find a variety of ways people have done something similar like this github thread, this Stack Overflow answer, this gist, etc.

If you want stuff to happen "upon choice submit", that's way 1. So using rollup-plugin-pug, it would look something like (completely untested and off the top of my head):

This issue is fixed by adding the content url in valid domains list in the Connector Developer Dashboard.

wsk is of type Base *, not Base nor Derived.

It was initialised with a value that was (implicitly) converted from type Derived *. It points to a Base object, which so happens to reside within a Derived object.

That means that static_cast(wsk) will give you a value that points to a Derived.

It may be that the representation of wsk is the same number as the representation of static_cast(wsk), i.e. that the address of the Base object is the same as the address of the Derived object, but that is not guaranteed

at begininnging of figuraplaska.h add something like

After take a look here, I use the url param without ssl and it works:

One of the pre-warmed containers was removed after because it was used. The other is still pristine and remains around/not reclaimed. This is called a stem cell container. A container is subject to garbage collection later once it is specialized (initialized with user code).

The default idle timeout is 10 minutes though, not 15 per this configuration, unless overridden.

https://github.com/apache/incubator-openwhisk/blob/2f0155fb750ce8b5eef6d5b0f4e2e2db40e5a037/core/invoker/src/main/resources/application.conf#L103-L110

The number of stemcells is specific to a runtime and determined by the runtime manifest. For example: https://github.com/apache/incubator-openwhisk/blob/ce45d54c824ef6c3e5d98ce0b220b924c81e688b/ansible/files/runtimes.json#L45-L50

Once a stem cell container is used, a nanny process will replace it with a new container so that the number of pre-warmed containers should generally be constant.