Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Yes. As I wrote, ngrok is optional. It's all described in the "how it works" section [1]. The default mechanism requires action concurrency though, which not all Openwhisk deployments have (apparently IBM cloud functions do not yet (?)). Alternatively there is a third option that should always work, but is slow. It uses tricks with activation records. This is picked automatically if concurrency is not available. There is currently still a bug [2] where this detection doesn't work in all cases. [1] https://github.com/adobe/wskdebug#how-it-works [2] https://github.com/adobe/wskdebug/issues/30 Cheers, Alex From: Michele Sciabarra Sent: Wednesday, February 19, 2020 10:04 To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request But is it possible to use without ngrok? I mean, if I have to run everything behind a firewall with the standalone openwhisk, does it work? -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Wednesday, February 19, 2020 7:02 PM Bertrand wrote: > IIUC there's no bundling of ngrok with wskdebug and users have to download > ngrok separately? Not quite. Their npm client library is bundled with wskdebug, and this is licensed under BSD-2-Clause. When you run wskdebug you have the option to specify —ngrok on the command line which will by default use their free tier service, or you could also use their paid plans if you want to (I think). Free tier is enough for wskdebug though. Cheers, Alex
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Hi, On Wed, Feb 19, 2020 at 7:02 PM Alexander Klimetschek wrote: > Bertrand wrote: > > IIUC there's no bundling of ngrok with wskdebug and users have to download > > ngrok separately? > Not quite. Their npm client library is bundled with wskdebug, and this is > licensed under BSD-2-Clause... Ok, BSD 2 clause is fine as per [1], > When you run wskdebug you have the option to specify —ngrok on the command > line which will by > default use their free tier service, or you could also use their paid plans > if you want to (I think) I think mentioning this in the module's README or in the --ngrok help option text would be sufficient - I don't think anything banned by [1] is being redistributed so you just want to warn users that by default they are led to use that service. -Bertrand [1] https://apache.org/legal/resolved.html
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
But is it possible to use without ngrok? I mean, if I have to run everything behind a firewall with the standalone openwhisk, does it work? -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Wednesday, February 19, 2020 7:02 PM Bertrand wrote: > IIUC there's no bundling of ngrok with wskdebug and users have to download > ngrok separately? Not quite. Their npm client library is bundled with wskdebug, and this is licensed under BSD-2-Clause. When you run wskdebug you have the option to specify —ngrok on the command line which will by default use their free tier service, or you could also use their paid plans if you want to (I think). Free tier is enough for wskdebug though. Cheers, Alex
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Bertrand wrote: > IIUC there's no bundling of ngrok with wskdebug and users have to download > ngrok separately? Not quite. Their npm client library is bundled with wskdebug, and this is licensed under BSD-2-Clause. When you run wskdebug you have the option to specify —ngrok on the command line which will by default use their free tier service, or you could also use their paid plans if you want to (I think). Free tier is enough for wskdebug though. Cheers, Alex
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
On Wed, Feb 19, 2020 at 1:44 AM Alexander Klimetschek wrote: > Their npm library used in wskdebug has the BSD-2-Clause license (not MIT) > [2], which should be fine for Apache. > Not sure if that optional integration / use of their service needs another > legal check for ASF?... IIUC there's no bundling of ngrok with wskdebug and users have to download ngrok separately? If that's correct that's totally fine from the ASF's point of view, especially as ngrok is not required to use wskdebug. -Bertrand
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
We can look at it when wskdebug is contributed ... at this point development is technically paused since I cannot make changes to it otherwise we'd have to do a new grant to Apache, but there is also no openwhisk repo yet to work on it But my idea is that action loop should accept some DEBUG_PORT env var that would enable debugging and set the debug port in the respective language runtime (depends on the language). That's it. The agents that take care of proxying from remote Openwhisk to local container are working independent of the container. It's just how to start the container locally in debug mode and with debug port open. Cheers, Alex From: Michele Sciabarra Sent: Wednesday, February 12, 2020 06:27 To: Alexander Klimetschek Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Can you explain how it works and how I can adapt to actionloop? There is some documentation in the video but I was unable to read it. I tried to give a look at the code but it was not clear. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "mich...@sciabarra.com" , "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Wednesday, February 12, 2020 2:19 AM And regarding actionloop specifically: when I looked at it last year, it seemed that the generic actionloop container would just need a flag (such as an environment variable) to enable debugging, which wskdebug could set automatically if it sees an actionloop based kind. Then each specific actionloop language container would use this to run the language runtime inside the container with debugging enabled and open a debug port, which would also be passed through as env var. Environment variables are good for this, as this makes it impossible to change them in a real production Openwhisk environment (as only the openwhisk invoker can set these, and they would only have an effect on start of the container/app). While wskdebug can easily set these as well. Cheers, Alex From: Alexander Klimetschek Sent: Tuesday, February 11, 2020 17:06 To: mich...@sciabarra.com ; dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > : Standalone OpenWhisk running in a docker container, because the debugger > (and the IDE) runs in another docker container. I guess this isn't really a scenario that wskdebug is built for, because in this case you have full control over what happens in that local openwhisk and debug ports of action containers can be visible in your host. IIUC this might be what you are doing already - not sure I fully grasped that however. wskdebug is generally meant for debugging when you are using a remote Openwhisk (say IBM Cloud or Adobe I/O Runtime) and you have no other choice. Many/most action developers will not themselves be able to spin up a local openwhisk, and sometimes you really need to debug in the real environment, not a local copy. But ignoring that, I wonder what exactly is failing when you run wskdebug inside a container? In theory it should be feasible. Might be something that can be fixed. Cheers, Alex From: Michele Sciabarra Sent: Tuesday, February 4, 2020 08:18 To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request The main reason because I tried my own approach instead of using wskdebug, that I tried, is because I was unable to make it work from within a docker container. My setup is: Standalone OpenWhisk running in a docker container, because the debugger (and the IDE) runs in another docker container. I need this setup because I want to provide a very simple installation, a wskide command that will setup the development environment. If I run the debugger from the standalone openwhisk works. But I have problems to add also the IDE that requires also node. So the prerequisites to run the whole thing would be a java of a given version, a node of the right version and docker. So I decided to go for a full dockerized solution. I have a launcher, written in go, that starts standalone openwhisk running in a docker container, and another container with the debugger and the editor (theia). In this setup, wskdebug does not work. It tries to do something with docker and does not work. I was unable to understand what is wrong, I tried to read the code but I do not follow it. For this reason I simply put an action in debug mode (using the runtime) and then I connected from the ide. It is more straightforward. There are still some issues to sync. But everything is open for discussion, I am more than happy if I can re-use wskdebug. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject:
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
First of all, ngrok is optional. It is not used by default, only if you use "--ngrok". See the "how it works" description [1] that talks about the 3 different "proxy" methods that wskdebug supports today. Their npm library used in wskdebug has the BSD-2-Clause license (not MIT) [2], which should be fine for Apache. Not sure if that optional integration / use of their service needs another legal check for ASF? [1] https://github.com/adobe/wskdebug#how-it-works [2] https://www.npmjs.com/package/ngrok Cheers, Alex From: Carlos Santana Sent: Friday, February 14, 2020 08:38 To: dev@openwhisk.apache.org Cc: Alexander Klimetschek Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request About ngrok I have being using inlets as an alternative to ngrok and the license is MIT which is good one. https://github.com/inlets/inlets - Carlos Santana @csantanapr On Feb 14, 2020, at 10:33 AM, Michele Sciabarra wrote: Yes I have a big advantage, in the fact I control the proxy. I read your documentation and from what I see it works in a very similar way: you "decorate" the action with your own action, while I am actually working at the proxy level. But for the rest the concept is similar: create a tunnel to reach the action, whenever it is. I started to dissect the code, and I noticed you use ngrok for creating a tunnel. I am trying to understand what it is exactly, but is this? https://ngrok.com/ What is the license state? It looks like to be proprietary code coupled with a proprietary service that happens to have a free (as a beer) but not open source version. Is it correct? Is it appropriate/acceptable for an apache project? -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "mich...@sciabarra.com" , "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Wednesday, February 12, 2020 2:06 AM : Standalone OpenWhisk running in a docker container, because the debugger (and the IDE) runs in another docker container. I guess this isn't really a scenario that wskdebug is built for, because in this case you have full control over what happens in that local openwhisk and debug ports of action containers can be visible in your host. IIUC this might be what you are doing already - not sure I fully grasped that however. wskdebug is generally meant for debugging when you are using a remote Openwhisk (say IBM Cloud or Adobe I/O Runtime) and you have no other choice. Many/most action developers will not themselves be able to spin up a local openwhisk, and sometimes you really need to debug in the real environment, not a local copy. But ignoring that, I wonder what exactly is failing when you run wskdebug inside a container? In theory it should be feasible. Might be something that can be fixed. Cheers, Alex *From:* Michele Sciabarra *Sent:* Tuesday, February 4, 2020 08:18 *To:* dev@openwhisk.apache.org *Subject:* Re: Preview of a OpenWhisk IDE & Debugger... and an help request The main reason because I tried my own approach instead of using wskdebug, that I tried, is because I was unable to make it work from within a docker container. My setup is: Standalone OpenWhisk running in a docker container, because the debugger (and the IDE) runs in another docker container. I need this setup because I want to provide a very simple installation, a wskide command that will setup the development environment. If I run the debugger from the standalone openwhisk works. But I have problems to add also the IDE that requires also node. So the prerequisites to run the whole thing would be a java of a given version, a node of the right version and docker. So I decided to go for a full dockerized solution. I have a launcher, written in go, that starts standalone openwhisk running in a docker container, and another container with the debugger and the editor (theia). In this setup, wskdebug does not work. It tries to do something with docker and does not work. I was unable to understand what is wrong, I tried to read the code but I do not follow it. For this reason I simply put an action in debug mode (using the runtime) and then I connected from the ide. It is more straightforward. There are still some issues to sync. But everything is open for discussion, I am more than happy if I can re-use wskdebug. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Tuesday, February 04, 2020 5:02 PM Hi Michele, please note that wskdebug [1] is a debugger for any kind. Nodejs has the best out of the box support since that’s what we are exclusively using right now. Other languages can already be supported using the right command line arguments (ports, docker command etc), which is
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
About ngrok I have being using inlets as an alternative to ngrok and the license is MIT which is good one. https://github.com/inlets/inlets - Carlos Santana @csantanapr > On Feb 14, 2020, at 10:33 AM, Michele Sciabarra wrote: > > Yes I have a big advantage, in the fact I control the proxy. > I read your documentation and from what I see it works in a very similar way: > you "decorate" the action with your own action, while I am actually working > at the proxy level. But for the rest the concept is similar: create a tunnel > to reach the action, whenever it is. > > I started to dissect the code, and I noticed you use ngrok for creating a > tunnel. I am trying to understand what it is exactly, but is this? > https://ngrok.com/ > > What is the license state? It looks like to be proprietary code coupled with > a proprietary service that happens to have a free (as a beer) but not open > source version. Is it correct? Is it appropriate/acceptable for an apache > project? > > -- > Michele Sciabarra > mich...@sciabarra.com > > > > - Original message - > From: Alexander Klimetschek > To: "mich...@sciabarra.com" , > "dev@openwhisk.apache.org" > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Wednesday, February 12, 2020 2:06 AM > >> : Standalone OpenWhisk running in a docker container, because the debugger >> (and the IDE) runs in another docker container. > > I guess this isn't really a scenario that wskdebug is built for, because in > this case you have full control over what happens in that local openwhisk and > debug ports of action containers can be visible in your host. IIUC this might > be what you are doing already - not sure I fully grasped that however. > > wskdebug is generally meant for debugging when you are using a remote > Openwhisk (say IBM Cloud or Adobe I/O Runtime) and you have no other choice. > Many/most action developers will not themselves be able to spin up a local > openwhisk, and sometimes you really need to debug in the real environment, > not a local copy. > > But ignoring that, I wonder what exactly is failing when you run wskdebug > inside a container? In theory it should be feasible. Might be something that > can be fixed. > > Cheers, > Alex > > > *From:* Michele Sciabarra > *Sent:* Tuesday, February 4, 2020 08:18 > *To:* dev@openwhisk.apache.org > *Subject:* Re: Preview of a OpenWhisk IDE & Debugger... and an help request > > The main reason because I tried my own approach instead of using wskdebug, > that I tried, is because I was unable to make it work from within a docker > container. > > My setup is: Standalone OpenWhisk running in a docker container, because the > debugger (and the IDE) runs in another docker container. > > I need this setup because I want to provide a very simple installation, a > wskide command that will setup the development environment. If I run the > debugger from the standalone openwhisk works. But I have problems to add also > the IDE that requires also node. So the prerequisites to run the whole thing > would be a java of a given version, a node of the right version and docker. > > So I decided to go for a full dockerized solution. I have a launcher, written > in go, that starts standalone openwhisk running in a docker container, and > another container with the debugger and the editor (theia). In this setup, > wskdebug does not work. It tries to do something with docker and does not > work. I was unable to understand what is wrong, I tried to read the code but > I do not follow it. > > For this reason I simply put an action in debug mode (using the runtime) and > then I connected from the ide. It is more straightforward. There are still > some issues to sync. But everything is open for discussion, I am more than > happy if I can re-use wskdebug. > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message - > From: Alexander Klimetschek > To: "dev@openwhisk.apache.org" > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Tuesday, February 04, 2020 5:02 PM > > Hi Michele, > > please note that wskdebug [1] is a debugger for any kind. Nodejs has the best > out of the box support since that’s what we are exclusively using right now. > Other languages can already be supported using the right command line > arguments (ports, docker command etc), which is how Java worked. Given this > new __OW_DEBUG_PORT env variable, it can be set with wskdebug using > —dockerArgs. Contributions are welcome to make this more automatic based on > the kind/image version of the action :-) > > FYI, On the contribution front, I will work on the legal documents this or > next week. > > [1] https://github.com/adobe/wskdebug > > Cheers, > Alex > > Von: Michele Sciabarra > Gesendet: Monday, February 3, 2020 2:27:15 AM > An: dev@openwhisk.apache.org > Betreff: Re:
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Legal questions about licensing can be submitted to the LEGAL Jira project by the way. On Fri, Feb 14, 2020 at 09:33 Michele Sciabarra wrote: > Yes I have a big advantage, in the fact I control the proxy. > I read your documentation and from what I see it works in a very similar > way: you "decorate" the action with your own action, while I am actually > working at the proxy level. But for the rest the concept is similar: create > a tunnel to reach the action, whenever it is. > > I started to dissect the code, and I noticed you use ngrok for creating a > tunnel. I am trying to understand what it is exactly, but is this? > https://ngrok.com/ > > What is the license state? It looks like to be proprietary code coupled > with a proprietary service that happens to have a free (as a beer) but not > open source version. Is it correct? Is it appropriate/acceptable for an > apache project? > > -- > Michele Sciabarra > mich...@sciabarra.com > > > > - Original message - > From: Alexander Klimetschek > To: "mich...@sciabarra.com" , " > dev@openwhisk.apache.org" > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Wednesday, February 12, 2020 2:06 AM > > > : Standalone OpenWhisk running in a docker container, because the > debugger (and the IDE) runs in another docker container. > > I guess this isn't really a scenario that wskdebug is built for, because > in this case you have full control over what happens in that local > openwhisk and debug ports of action containers can be visible in your host. > IIUC this might be what you are doing already - not sure I fully grasped > that however. > > wskdebug is generally meant for debugging when you are using a remote > Openwhisk (say IBM Cloud or Adobe I/O Runtime) and you have no other > choice. Many/most action developers will not themselves be able to spin up > a local openwhisk, and sometimes you really need to debug in the real > environment, not a local copy. > > But ignoring that, I wonder what exactly is failing when you run wskdebug > inside a container? In theory it should be feasible. Might be something > that can be fixed. > > Cheers, > Alex > > > *From:* Michele Sciabarra > *Sent:* Tuesday, February 4, 2020 08:18 > *To:* dev@openwhisk.apache.org > *Subject:* Re: Preview of a OpenWhisk IDE & Debugger... and an help > request > > The main reason because I tried my own approach instead of using wskdebug, > that I tried, is because I was unable to make it work from within a docker > container. > > My setup is: Standalone OpenWhisk running in a docker container, because > the debugger (and the IDE) runs in another docker container. > > I need this setup because I want to provide a very simple installation, a > wskide command that will setup the development environment. If I run the > debugger from the standalone openwhisk works. But I have problems to add > also the IDE that requires also node. So the prerequisites to run the whole > thing would be a java of a given version, a node of the right version and > docker. > > So I decided to go for a full dockerized solution. I have a launcher, > written in go, that starts standalone openwhisk running in a docker > container, and another container with the debugger and the editor (theia). > In this setup, wskdebug does not work. It tries to do something with docker > and does not work. I was unable to understand what is wrong, I tried to > read the code but I do not follow it. > > For this reason I simply put an action in debug mode (using the runtime) > and then I connected from the ide. It is more straightforward. There are > still some issues to sync. But everything is open for discussion, I am more > than happy if I can re-use wskdebug. > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message - > From: Alexander Klimetschek > To: "dev@openwhisk.apache.org" > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Tuesday, February 04, 2020 5:02 PM > > Hi Michele, > > please note that wskdebug [1] is a debugger for any kind. Nodejs has the > best out of the box support since that’s what we are exclusively using > right now. Other languages can already be supported using the right command > line arguments (ports, docker command etc), which is how Java worked. Given > this new __OW_DEBUG_PORT env variable, it can be set with wskdebug using > —dockerArgs. Contributions are welcome to make this more automatic based on > the kind/image version of the action :-) > > FYI, On the contribution front, I will work on the legal documents this > or next week. > > [1] https://github.com/adobe/wskdebug > > Cheers, > Alex > > Von: Michele Sciabarra > Gesendet: Monday, February 3, 2020 2:27:15 AM > An: dev@openwhisk.apache.org > Betreff: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > > This is basically also what I am trying to do. > > I guess the difference
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Yes I have a big advantage, in the fact I control the proxy. I read your documentation and from what I see it works in a very similar way: you "decorate" the action with your own action, while I am actually working at the proxy level. But for the rest the concept is similar: create a tunnel to reach the action, whenever it is. I started to dissect the code, and I noticed you use ngrok for creating a tunnel. I am trying to understand what it is exactly, but is this? https://ngrok.com/ What is the license state? It looks like to be proprietary code coupled with a proprietary service that happens to have a free (as a beer) but not open source version. Is it correct? Is it appropriate/acceptable for an apache project? -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "mich...@sciabarra.com" , "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Wednesday, February 12, 2020 2:06 AM > : Standalone OpenWhisk running in a docker container, because the debugger > (and the IDE) runs in another docker container. I guess this isn't really a scenario that wskdebug is built for, because in this case you have full control over what happens in that local openwhisk and debug ports of action containers can be visible in your host. IIUC this might be what you are doing already - not sure I fully grasped that however. wskdebug is generally meant for debugging when you are using a remote Openwhisk (say IBM Cloud or Adobe I/O Runtime) and you have no other choice. Many/most action developers will not themselves be able to spin up a local openwhisk, and sometimes you really need to debug in the real environment, not a local copy. But ignoring that, I wonder what exactly is failing when you run wskdebug inside a container? In theory it should be feasible. Might be something that can be fixed. Cheers, Alex *From:* Michele Sciabarra *Sent:* Tuesday, February 4, 2020 08:18 *To:* dev@openwhisk.apache.org *Subject:* Re: Preview of a OpenWhisk IDE & Debugger... and an help request The main reason because I tried my own approach instead of using wskdebug, that I tried, is because I was unable to make it work from within a docker container. My setup is: Standalone OpenWhisk running in a docker container, because the debugger (and the IDE) runs in another docker container. I need this setup because I want to provide a very simple installation, a wskide command that will setup the development environment. If I run the debugger from the standalone openwhisk works. But I have problems to add also the IDE that requires also node. So the prerequisites to run the whole thing would be a java of a given version, a node of the right version and docker. So I decided to go for a full dockerized solution. I have a launcher, written in go, that starts standalone openwhisk running in a docker container, and another container with the debugger and the editor (theia). In this setup, wskdebug does not work. It tries to do something with docker and does not work. I was unable to understand what is wrong, I tried to read the code but I do not follow it. For this reason I simply put an action in debug mode (using the runtime) and then I connected from the ide. It is more straightforward. There are still some issues to sync. But everything is open for discussion, I am more than happy if I can re-use wskdebug. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Tuesday, February 04, 2020 5:02 PM Hi Michele, please note that wskdebug [1] is a debugger for any kind. Nodejs has the best out of the box support since that’s what we are exclusively using right now. Other languages can already be supported using the right command line arguments (ports, docker command etc), which is how Java worked. Given this new __OW_DEBUG_PORT env variable, it can be set with wskdebug using —dockerArgs. Contributions are welcome to make this more automatic based on the kind/image version of the action :-) FYI, On the contribution front, I will work on the legal documents this or next week. [1] https://github.com/adobe/wskdebug Cheers, Alex Von: Michele Sciabarra Gesendet: Monday, February 3, 2020 2:27:15 AM An: dev@openwhisk.apache.org Betreff: Re: Preview of a OpenWhisk IDE & Debugger... and an help request This is basically also what I am trying to do. I guess the difference is that you are doing this using the standard nodejs runtime while I am doing the same using the goproxy. I am sure it is also similar to the adobe/wskdebug that I tried to use, and works but it specific to the node and java runtimes, without actionloop. My goal is to get the debugger for the "other"
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
And regarding actionloop specifically: when I looked at it last year, it seemed that the generic actionloop container would just need a flag (such as an environment variable) to enable debugging, which wskdebug could set automatically if it sees an actionloop based kind. Then each specific actionloop language container would use this to run the language runtime inside the container with debugging enabled and open a debug port, which would also be passed through as env var. Environment variables are good for this, as this makes it impossible to change them in a real production Openwhisk environment (as only the openwhisk invoker can set these, and they would only have an effect on start of the container/app). While wskdebug can easily set these as well. Cheers, Alex From: Alexander Klimetschek Sent: Tuesday, February 11, 2020 17:06 To: mich...@sciabarra.com ; dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > : Standalone OpenWhisk running in a docker container, because the debugger > (and the IDE) runs in another docker container. I guess this isn't really a scenario that wskdebug is built for, because in this case you have full control over what happens in that local openwhisk and debug ports of action containers can be visible in your host. IIUC this might be what you are doing already - not sure I fully grasped that however. wskdebug is generally meant for debugging when you are using a remote Openwhisk (say IBM Cloud or Adobe I/O Runtime) and you have no other choice. Many/most action developers will not themselves be able to spin up a local openwhisk, and sometimes you really need to debug in the real environment, not a local copy. But ignoring that, I wonder what exactly is failing when you run wskdebug inside a container? In theory it should be feasible. Might be something that can be fixed. Cheers, Alex From: Michele Sciabarra Sent: Tuesday, February 4, 2020 08:18 To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request The main reason because I tried my own approach instead of using wskdebug, that I tried, is because I was unable to make it work from within a docker container. My setup is: Standalone OpenWhisk running in a docker container, because the debugger (and the IDE) runs in another docker container. I need this setup because I want to provide a very simple installation, a wskide command that will setup the development environment. If I run the debugger from the standalone openwhisk works. But I have problems to add also the IDE that requires also node. So the prerequisites to run the whole thing would be a java of a given version, a node of the right version and docker. So I decided to go for a full dockerized solution. I have a launcher, written in go, that starts standalone openwhisk running in a docker container, and another container with the debugger and the editor (theia). In this setup, wskdebug does not work. It tries to do something with docker and does not work. I was unable to understand what is wrong, I tried to read the code but I do not follow it. For this reason I simply put an action in debug mode (using the runtime) and then I connected from the ide. It is more straightforward. There are still some issues to sync. But everything is open for discussion, I am more than happy if I can re-use wskdebug. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Tuesday, February 04, 2020 5:02 PM Hi Michele, please note that wskdebug [1] is a debugger for any kind. Nodejs has the best out of the box support since that’s what we are exclusively using right now. Other languages can already be supported using the right command line arguments (ports, docker command etc), which is how Java worked. Given this new __OW_DEBUG_PORT env variable, it can be set with wskdebug using —dockerArgs. Contributions are welcome to make this more automatic based on the kind/image version of the action :-) FYI, On the contribution front, I will work on the legal documents this or next week. [1] https://github.com/adobe/wskdebug Cheers, Alex Von: Michele Sciabarra Gesendet: Monday, February 3, 2020 2:27:15 AM An: dev@openwhisk.apache.org Betreff: Re: Preview of a OpenWhisk IDE & Debugger... and an help request This is basically also what I am trying to do. I guess the difference is that you are doing this using the standard nodejs runtime while I am doing the same using the goproxy. I am sure it is also similar to the adobe/wskdebug that I tried to use, and works but it specific to the node and java runtimes, without actionloop. My goal is to get the debugger for the "other"
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
> : Standalone OpenWhisk running in a docker container, because the debugger > (and the IDE) runs in another docker container. I guess this isn't really a scenario that wskdebug is built for, because in this case you have full control over what happens in that local openwhisk and debug ports of action containers can be visible in your host. IIUC this might be what you are doing already - not sure I fully grasped that however. wskdebug is generally meant for debugging when you are using a remote Openwhisk (say IBM Cloud or Adobe I/O Runtime) and you have no other choice. Many/most action developers will not themselves be able to spin up a local openwhisk, and sometimes you really need to debug in the real environment, not a local copy. But ignoring that, I wonder what exactly is failing when you run wskdebug inside a container? In theory it should be feasible. Might be something that can be fixed. Cheers, Alex From: Michele Sciabarra Sent: Tuesday, February 4, 2020 08:18 To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request The main reason because I tried my own approach instead of using wskdebug, that I tried, is because I was unable to make it work from within a docker container. My setup is: Standalone OpenWhisk running in a docker container, because the debugger (and the IDE) runs in another docker container. I need this setup because I want to provide a very simple installation, a wskide command that will setup the development environment. If I run the debugger from the standalone openwhisk works. But I have problems to add also the IDE that requires also node. So the prerequisites to run the whole thing would be a java of a given version, a node of the right version and docker. So I decided to go for a full dockerized solution. I have a launcher, written in go, that starts standalone openwhisk running in a docker container, and another container with the debugger and the editor (theia). In this setup, wskdebug does not work. It tries to do something with docker and does not work. I was unable to understand what is wrong, I tried to read the code but I do not follow it. For this reason I simply put an action in debug mode (using the runtime) and then I connected from the ide. It is more straightforward. There are still some issues to sync. But everything is open for discussion, I am more than happy if I can re-use wskdebug. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Tuesday, February 04, 2020 5:02 PM Hi Michele, please note that wskdebug [1] is a debugger for any kind. Nodejs has the best out of the box support since that’s what we are exclusively using right now. Other languages can already be supported using the right command line arguments (ports, docker command etc), which is how Java worked. Given this new __OW_DEBUG_PORT env variable, it can be set with wskdebug using —dockerArgs. Contributions are welcome to make this more automatic based on the kind/image version of the action :-) FYI, On the contribution front, I will work on the legal documents this or next week. [1] https://github.com/adobe/wskdebug Cheers, Alex Von: Michele Sciabarra Gesendet: Monday, February 3, 2020 2:27:15 AM An: dev@openwhisk.apache.org Betreff: Re: Preview of a OpenWhisk IDE & Debugger... and an help request This is basically also what I am trying to do. I guess the difference is that you are doing this using the standard nodejs runtime while I am doing the same using the goproxy. I am sure it is also similar to the adobe/wskdebug that I tried to use, and works but it specific to the node and java runtimes, without actionloop. My goal is to get the debugger for the "other" languages, most notabily typescript python and go. Let's discuss on the call to see how we can align efforts. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Dominic Kim To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Monday, February 03, 2020 10:52 AM Thank you for the details. It seems what you are tying now is similar with our approach and can be aligned with ours too as it is generic like you said. We enabled the debugging of Nodejs runtime with chrome DevTools protocol https://chromedevtools.github.io/devtools-protocol/. Our UI communicates with the real remote OW deployment. We implemented one proxy server to correlate a debugging session with a corresponding action container. Since each action container is not exposed to public, we also have a bridge component on each invoker machine for location transparency. If I understood correctly, each container will connect to the IDE in a reverse way in your
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
The main reason because I tried my own approach instead of using wskdebug, that I tried, is because I was unable to make it work from within a docker container. My setup is: Standalone OpenWhisk running in a docker container, because the debugger (and the IDE) runs in another docker container. I need this setup because I want to provide a very simple installation, a wskide command that will setup the development environment. If I run the debugger from the standalone openwhisk works. But I have problems to add also the IDE that requires also node. So the prerequisites to run the whole thing would be a java of a given version, a node of the right version and docker. So I decided to go for a full dockerized solution. I have a launcher, written in go, that starts standalone openwhisk running in a docker container, and another container with the debugger and the editor (theia). In this setup, wskdebug does not work. It tries to do something with docker and does not work. I was unable to understand what is wrong, I tried to read the code but I do not follow it. For this reason I simply put an action in debug mode (using the runtime) and then I connected from the ide. It is more straightforward. There are still some issues to sync. But everything is open for discussion, I am more than happy if I can re-use wskdebug. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Alexander Klimetschek To: "dev@openwhisk.apache.org" Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Tuesday, February 04, 2020 5:02 PM Hi Michele, please note that wskdebug [1] is a debugger for any kind. Nodejs has the best out of the box support since that’s what we are exclusively using right now. Other languages can already be supported using the right command line arguments (ports, docker command etc), which is how Java worked. Given this new __OW_DEBUG_PORT env variable, it can be set with wskdebug using —dockerArgs. Contributions are welcome to make this more automatic based on the kind/image version of the action :-) FYI, On the contribution front, I will work on the legal documents this or next week. [1] https://github.com/adobe/wskdebug Cheers, Alex Von: Michele Sciabarra Gesendet: Monday, February 3, 2020 2:27:15 AM An: dev@openwhisk.apache.org Betreff: Re: Preview of a OpenWhisk IDE & Debugger... and an help request This is basically also what I am trying to do. I guess the difference is that you are doing this using the standard nodejs runtime while I am doing the same using the goproxy. I am sure it is also similar to the adobe/wskdebug that I tried to use, and works but it specific to the node and java runtimes, without actionloop. My goal is to get the debugger for the "other" languages, most notabily typescript python and go. Let's discuss on the call to see how we can align efforts. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Dominic Kim To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Monday, February 03, 2020 10:52 AM Thank you for the details. It seems what you are tying now is similar with our approach and can be aligned with ours too as it is generic like you said. We enabled the debugging of Nodejs runtime with chrome DevTools protocol https://chromedevtools.github.io/devtools-protocol/. Our UI communicates with the real remote OW deployment. We implemented one proxy server to correlate a debugging session with a corresponding action container. Since each action container is not exposed to public, we also have a bridge component on each invoker machine for location transparency. If I understood correctly, each container will connect to the IDE in a reverse way in your version and similarly it connects to the proxy via bridge in our version. SoI think two versions can coexist, if we make the interface extensible. Maybe I can share more details at this interchange call. Thanks Best regards Dominic. 2020년 2월 3일 (월) 오후 4:47, Michele Sciabarra 님이 작성: > Hi Dominic > > the preliminary work I did was already submitted as a PR to build a > standalone docker image (that is critical for my design). > > The rest the work is here: https://github.com/sciabarracom/openwhisk-ide > and uses the (upcoming) typescript runtime here > https://github.com/sciabarracom/openwhisk-runtime-typescript. But do not > use it yet as it is pretty much work in progress, no documentation nor it > is even remotely stable. > > The key idea is to leverage the fact that actionloop launches a process > for each action, and I am simplying putting the process in debug mode. Then > I am using Eclipse Theia, that is vscode in a browser, > https://theia-ide.org/ as an editor and debugger interface. > > The key problem I have is to connect the action running under a debugger > (problem solved) with the debugger
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Hi Michele, please note that wskdebug [1] is a debugger for any kind. Nodejs has the best out of the box support since that’s what we are exclusively using right now. Other languages can already be supported using the right command line arguments (ports, docker command etc), which is how Java worked. Given this new __OW_DEBUG_PORT env variable, it can be set with wskdebug using —dockerArgs. Contributions are welcome to make this more automatic based on the kind/image version of the action :-) FYI, On the contribution front, I will work on the legal documents this or next week. [1] https://github.com/adobe/wskdebug Cheers, Alex Von: Michele Sciabarra Gesendet: Monday, February 3, 2020 2:27:15 AM An: dev@openwhisk.apache.org Betreff: Re: Preview of a OpenWhisk IDE & Debugger... and an help request This is basically also what I am trying to do. I guess the difference is that you are doing this using the standard nodejs runtime while I am doing the same using the goproxy. I am sure it is also similar to the adobe/wskdebug that I tried to use, and works but it specific to the node and java runtimes, without actionloop. My goal is to get the debugger for the "other" languages, most notabily typescript python and go. Let's discuss on the call to see how we can align efforts. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Dominic Kim To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Monday, February 03, 2020 10:52 AM Thank you for the details. It seems what you are tying now is similar with our approach and can be aligned with ours too as it is generic like you said. We enabled the debugging of Nodejs runtime with chrome DevTools protocol https://chromedevtools.github.io/devtools-protocol/. Our UI communicates with the real remote OW deployment. We implemented one proxy server to correlate a debugging session with a corresponding action container. Since each action container is not exposed to public, we also have a bridge component on each invoker machine for location transparency. If I understood correctly, each container will connect to the IDE in a reverse way in your version and similarly it connects to the proxy via bridge in our version. SoI think two versions can coexist, if we make the interface extensible. Maybe I can share more details at this interchange call. Thanks Best regards Dominic. 2020년 2월 3일 (월) 오후 4:47, Michele Sciabarra 님이 작성: > Hi Dominic > > the preliminary work I did was already submitted as a PR to build a > standalone docker image (that is critical for my design). > > The rest the work is here: https://github.com/sciabarracom/openwhisk-ide > and uses the (upcoming) typescript runtime here > https://github.com/sciabarracom/openwhisk-runtime-typescript. But do not > use it yet as it is pretty much work in progress, no documentation nor it > is even remotely stable. > > The key idea is to leverage the fact that actionloop launches a process > for each action, and I am simplying putting the process in debug mode. Then > I am using Eclipse Theia, that is vscode in a browser, > https://theia-ide.org/ as an editor and debugger interface. > > The key problem I have is to connect the action running under a debugger > (problem solved) with the debugger client. So far I am just starting the > action , asking to the action its IP and then connecting to it with the > debugger. Problem is that the action may have a different IP > > I am now in the process of trying a different approach, where I > communicate to the action the IP of the IDE and ask to the action to > connect back, maybe creating a tunnel. In this way it could work in a more > generic way, even with a production whisk, as the only requirement will be > to have the client (that is itself a docker container) reachable by the > action. > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message - > From: Dominic Kim > To: dev@openwhisk.apache.org > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Monday, February 03, 2020 7:07 AM > > Hi Michele. > Thank you for sharing great works. > > We here(Naver) are also using a web based debugging feature and I would > like to align ours with yours. > Is there any reference that I can follow up your works? > Did you open any PR? > > And I want to share our version at this tech interchange call. > > > Best regards > Dominic > > > 2020년 2월 2일 (일) 오전 7:02, Michele Sciabarra 님이 작성: > > > Great suggestion. I know how to pass configuration parameters, what is > the > > configuration to set? > > > > -- > > Michele Sciabarra > > mich...@sciabarra.com > > > > - Original message - > > From: Rodric Rabbah > > To: dev@openwhisk.apache.org > > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > > Date: Saturday, February 01, 2020 8:35 PM > > > > > The
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
This is basically also what I am trying to do. I guess the difference is that you are doing this using the standard nodejs runtime while I am doing the same using the goproxy. I am sure it is also similar to the adobe/wskdebug that I tried to use, and works but it specific to the node and java runtimes, without actionloop. My goal is to get the debugger for the "other" languages, most notabily typescript python and go. Let's discuss on the call to see how we can align efforts. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Dominic Kim To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Monday, February 03, 2020 10:52 AM Thank you for the details. It seems what you are tying now is similar with our approach and can be aligned with ours too as it is generic like you said. We enabled the debugging of Nodejs runtime with chrome DevTools protocol https://chromedevtools.github.io/devtools-protocol/. Our UI communicates with the real remote OW deployment. We implemented one proxy server to correlate a debugging session with a corresponding action container. Since each action container is not exposed to public, we also have a bridge component on each invoker machine for location transparency. If I understood correctly, each container will connect to the IDE in a reverse way in your version and similarly it connects to the proxy via bridge in our version. SoI think two versions can coexist, if we make the interface extensible. Maybe I can share more details at this interchange call. Thanks Best regards Dominic. 2020년 2월 3일 (월) 오후 4:47, Michele Sciabarra 님이 작성: > Hi Dominic > > the preliminary work I did was already submitted as a PR to build a > standalone docker image (that is critical for my design). > > The rest the work is here: https://github.com/sciabarracom/openwhisk-ide > and uses the (upcoming) typescript runtime here > https://github.com/sciabarracom/openwhisk-runtime-typescript. But do not > use it yet as it is pretty much work in progress, no documentation nor it > is even remotely stable. > > The key idea is to leverage the fact that actionloop launches a process > for each action, and I am simplying putting the process in debug mode. Then > I am using Eclipse Theia, that is vscode in a browser, > https://theia-ide.org/ as an editor and debugger interface. > > The key problem I have is to connect the action running under a debugger > (problem solved) with the debugger client. So far I am just starting the > action , asking to the action its IP and then connecting to it with the > debugger. Problem is that the action may have a different IP > > I am now in the process of trying a different approach, where I > communicate to the action the IP of the IDE and ask to the action to > connect back, maybe creating a tunnel. In this way it could work in a more > generic way, even with a production whisk, as the only requirement will be > to have the client (that is itself a docker container) reachable by the > action. > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message - > From: Dominic Kim > To: dev@openwhisk.apache.org > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Monday, February 03, 2020 7:07 AM > > Hi Michele. > Thank you for sharing great works. > > We here(Naver) are also using a web based debugging feature and I would > like to align ours with yours. > Is there any reference that I can follow up your works? > Did you open any PR? > > And I want to share our version at this tech interchange call. > > > Best regards > Dominic > > > 2020년 2월 2일 (일) 오전 7:02, Michele Sciabarra 님이 작성: > > > Great suggestion. I know how to pass configuration parameters, what is > the > > configuration to set? > > > > -- > > Michele Sciabarra > > mich...@sciabarra.com > > > > - Original message - > > From: Rodric Rabbah > > To: dev@openwhisk.apache.org > > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > > Date: Saturday, February 01, 2020 8:35 PM > > > > > The first problem is that I need to invoke an action twice as the first > > time the debugger does not attach. I guess it is because the image is > > paused. > > > > Did you try to change the pause grace configuration to an max int. > > > > -r > > >
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Thank you for the details. It seems what you are tying now is similar with our approach and can be aligned with ours too as it is generic like you said. We enabled the debugging of Nodejs runtime with chrome DevTools protocol https://chromedevtools.github.io/devtools-protocol/. Our UI communicates with the real remote OW deployment. We implemented one proxy server to correlate a debugging session with a corresponding action container. Since each action container is not exposed to public, we also have a bridge component on each invoker machine for location transparency. If I understood correctly, each container will connect to the IDE in a reverse way in your version and similarly it connects to the proxy via bridge in our version. SoI think two versions can coexist, if we make the interface extensible. Maybe I can share more details at this interchange call. Thanks Best regards Dominic. 2020년 2월 3일 (월) 오후 4:47, Michele Sciabarra 님이 작성: > Hi Dominic > > the preliminary work I did was already submitted as a PR to build a > standalone docker image (that is critical for my design). > > The rest the work is here: https://github.com/sciabarracom/openwhisk-ide > and uses the (upcoming) typescript runtime here > https://github.com/sciabarracom/openwhisk-runtime-typescript. But do not > use it yet as it is pretty much work in progress, no documentation nor it > is even remotely stable. > > The key idea is to leverage the fact that actionloop launches a process > for each action, and I am simplying putting the process in debug mode. Then > I am using Eclipse Theia, that is vscode in a browser, > https://theia-ide.org/ as an editor and debugger interface. > > The key problem I have is to connect the action running under a debugger > (problem solved) with the debugger client. So far I am just starting the > action , asking to the action its IP and then connecting to it with the > debugger. Problem is that the action may have a different IP > > I am now in the process of trying a different approach, where I > communicate to the action the IP of the IDE and ask to the action to > connect back, maybe creating a tunnel. In this way it could work in a more > generic way, even with a production whisk, as the only requirement will be > to have the client (that is itself a docker container) reachable by the > action. > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message - > From: Dominic Kim > To: dev@openwhisk.apache.org > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Monday, February 03, 2020 7:07 AM > > Hi Michele. > Thank you for sharing great works. > > We here(Naver) are also using a web based debugging feature and I would > like to align ours with yours. > Is there any reference that I can follow up your works? > Did you open any PR? > > And I want to share our version at this tech interchange call. > > > Best regards > Dominic > > > 2020년 2월 2일 (일) 오전 7:02, Michele Sciabarra 님이 작성: > > > Great suggestion. I know how to pass configuration parameters, what is > the > > configuration to set? > > > > -- > > Michele Sciabarra > > mich...@sciabarra.com > > > > - Original message - > > From: Rodric Rabbah > > To: dev@openwhisk.apache.org > > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > > Date: Saturday, February 01, 2020 8:35 PM > > > > > The first problem is that I need to invoke an action twice as the first > > time the debugger does not attach. I guess it is because the image is > > paused. > > > > Did you try to change the pause grace configuration to an max int. > > > > -r > > >
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Hi Dominic the preliminary work I did was already submitted as a PR to build a standalone docker image (that is critical for my design). The rest the work is here: https://github.com/sciabarracom/openwhisk-ide and uses the (upcoming) typescript runtime here https://github.com/sciabarracom/openwhisk-runtime-typescript. But do not use it yet as it is pretty much work in progress, no documentation nor it is even remotely stable. The key idea is to leverage the fact that actionloop launches a process for each action, and I am simplying putting the process in debug mode. Then I am using Eclipse Theia, that is vscode in a browser, https://theia-ide.org/ as an editor and debugger interface. The key problem I have is to connect the action running under a debugger (problem solved) with the debugger client. So far I am just starting the action , asking to the action its IP and then connecting to it with the debugger. Problem is that the action may have a different IP I am now in the process of trying a different approach, where I communicate to the action the IP of the IDE and ask to the action to connect back, maybe creating a tunnel. In this way it could work in a more generic way, even with a production whisk, as the only requirement will be to have the client (that is itself a docker container) reachable by the action. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Dominic Kim To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Monday, February 03, 2020 7:07 AM Hi Michele. Thank you for sharing great works. We here(Naver) are also using a web based debugging feature and I would like to align ours with yours. Is there any reference that I can follow up your works? Did you open any PR? And I want to share our version at this tech interchange call. Best regards Dominic 2020년 2월 2일 (일) 오전 7:02, Michele Sciabarra 님이 작성: > Great suggestion. I know how to pass configuration parameters, what is the > configuration to set? > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message - > From: Rodric Rabbah > To: dev@openwhisk.apache.org > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Saturday, February 01, 2020 8:35 PM > > > The first problem is that I need to invoke an action twice as the first > time the debugger does not attach. I guess it is because the image is > paused. > > Did you try to change the pause grace configuration to an max int. > > -r >
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Hi Michele. Thank you for sharing great works. We here(Naver) are also using a web based debugging feature and I would like to align ours with yours. Is there any reference that I can follow up your works? Did you open any PR? And I want to share our version at this tech interchange call. Best regards Dominic 2020년 2월 2일 (일) 오전 7:02, Michele Sciabarra 님이 작성: > Great suggestion. I know how to pass configuration parameters, what is the > configuration to set? > > -- > Michele Sciabarra > mich...@sciabarra.com > > - Original message - > From: Rodric Rabbah > To: dev@openwhisk.apache.org > Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request > Date: Saturday, February 01, 2020 8:35 PM > > > The first problem is that I need to invoke an action twice as the first > time the debugger does not attach. I guess it is because the image is > paused. > > Did you try to change the pause grace configuration to an max int. > > -r >
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Great suggestion. I know how to pass configuration parameters, what is the configuration to set? -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Rodric Rabbah To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Saturday, February 01, 2020 8:35 PM > The first problem is that I need to invoke an action twice as the first time the debugger does not attach. I guess it is because the image is paused. Did you try to change the pause grace configuration to an max int. -r
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
> The first problem is that I need to invoke an action twice as the first time the debugger does not attach. I guess it is because the image is paused. Did you try to change the pause grace configuration to an max int. -r
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Then help me guys! I am reading the source of the CommonBalancer to find how to ensure I can always hit the same action and the container is unpaused when I want to debug one. -- Michele Sciabarra mich...@sciabarra.com - Original message - From: Carlos Santana To: dev@openwhisk.apache.org Subject: Re: Preview of a OpenWhisk IDE & Debugger... and an help request Date: Saturday, February 01, 2020 7:54 PM Very cool feature and demo Michele +1 - Carlos Santana @csantanapr > On Jan 31, 2020, at 8:38 AM, Michele Sciabarra wrote: > > Hello Whiskers, > > I am working on an integrated IDE & Debugger for OpenWhisk using the > ActionLoop runtime, the standalone OpenWhisk and Eclipse Theia. This would be > complementary to the existing wskdebug for Javascript and Java, as this works > now for Typescript and I plan to add to other actionloop based runtimes. > > You can see a demo here: https://www.youtube.com/watch?v=FhtGsm4Vnu4 > > I am using the standalone Openwhisk and Eclipse Theia, the in-browser > vscode-like editor that can be deployed as a docker container. > > The mechanic is simple: when I deploy an action I pass an additional > environment variable __OW_DEBUG_PORT > The runtime when it sees this environment variable starts under a debugger. > I can then ask to the runtime the parameters to connect to the debugger and I > use this to connect to the debugger, as you can see in the demo. > > I adapted the upcoming typescript runtime to do this, but I plan to do > similar changes also for other action loop based runtimes, like go and > python. Also I am using a Makefile to start the environment but I am working > on a standalone openwhisk-ide launcher. Unless we add the feature “ide" to > the wsk cli , if you like the idea... > > I have a couple of problems to solve and I am asking for help. The first > problem is that I need to invoke an action twice as the first time the > debugger does not attach. I guess it is because the image is paused. So I > wonder if it is possible to enable an option that does not pause the > container while running using the standalone openwhisk. And the second > problem is that sometimes I get more than one instance of an action. This > happens when I redeploy. I wonder if it is possible to force the Lean > Balancer to use only one instance of an action. > > All of this of course are options only for development purposes but I think > in this way OpenWhisk would be the ONLY serverless to include also an IDE > with debugger ready to go. No more “serverless actions are hard to debug”. > > -- > Michele Sciabarra > mich...@sciabarra.com
Re: Preview of a OpenWhisk IDE & Debugger... and an help request
Very cool feature and demo Michele +1 - Carlos Santana @csantanapr > On Jan 31, 2020, at 8:38 AM, Michele Sciabarra wrote: > > Hello Whiskers, > > I am working on an integrated IDE & Debugger for OpenWhisk using the > ActionLoop runtime, the standalone OpenWhisk and Eclipse Theia. This would be > complementary to the existing wskdebug for Javascript and Java, as this works > now for Typescript and I plan to add to other actionloop based runtimes. > > You can see a demo here: https://www.youtube.com/watch?v=FhtGsm4Vnu4 > > I am using the standalone Openwhisk and Eclipse Theia, the in-browser > vscode-like editor that can be deployed as a docker container. > > The mechanic is simple: when I deploy an action I pass an additional > environment variable __OW_DEBUG_PORT > The runtime when it sees this environment variable starts under a debugger. > I can then ask to the runtime the parameters to connect to the debugger and I > use this to connect to the debugger, as you can see in the demo. > > I adapted the upcoming typescript runtime to do this, but I plan to do > similar changes also for other action loop based runtimes, like go and > python. Also I am using a Makefile to start the environment but I am working > on a standalone openwhisk-ide launcher. Unless we add the feature “ide" to > the wsk cli , if you like the idea... > > I have a couple of problems to solve and I am asking for help. The first > problem is that I need to invoke an action twice as the first time the > debugger does not attach. I guess it is because the image is paused. So I > wonder if it is possible to enable an option that does not pause the > container while running using the standalone openwhisk. And the second > problem is that sometimes I get more than one instance of an action. This > happens when I redeploy. I wonder if it is possible to force the Lean > Balancer to use only one instance of an action. > > All of this of course are options only for development purposes but I think > in this way OpenWhisk would be the ONLY serverless to include also an IDE > with debugger ready to go. No more “serverless actions are hard to debug”. > > -- > Michele Sciabarra > mich...@sciabarra.com
Preview of a OpenWhisk IDE & Debugger... and an help request
Hello Whiskers, I am working on an integrated IDE & Debugger for OpenWhisk using the ActionLoop runtime, the standalone OpenWhisk and Eclipse Theia. This would be complementary to the existing wskdebug for Javascript and Java, as this works now for Typescript and I plan to add to other actionloop based runtimes. You can see a demo here: https://www.youtube.com/watch?v=FhtGsm4Vnu4 I am using the standalone Openwhisk and Eclipse Theia, the in-browser vscode-like editor that can be deployed as a docker container. The mechanic is simple: when I deploy an action I pass an additional environment variable __OW_DEBUG_PORT The runtime when it sees this environment variable starts under a debugger. I can then ask to the runtime the parameters to connect to the debugger and I use this to connect to the debugger, as you can see in the demo. I adapted the upcoming typescript runtime to do this, but I plan to do similar changes also for other action loop based runtimes, like go and python. Also I am using a Makefile to start the environment but I am working on a standalone openwhisk-ide launcher. Unless we add the feature “ide" to the wsk cli , if you like the idea... I have a couple of problems to solve and I am asking for help. The first problem is that I need to invoke an action twice as the first time the debugger does not attach. I guess it is because the image is paused. So I wonder if it is possible to enable an option that does not pause the container while running using the standalone openwhisk. And the second problem is that sometimes I get more than one instance of an action. This happens when I redeploy. I wonder if it is possible to force the Lean Balancer to use only one instance of an action. All of this of course are options only for development purposes but I think in this way OpenWhisk would be the ONLY serverless to include also an IDE with debugger ready to go. No more “serverless actions are hard to debug”. -- Michele Sciabarra mich...@sciabarra.com
