jid | json incremental digger | JSON Processing library

I know almost nothing about kubernetes and node.js, but I have experience in ejabberd and docker, so maybe I can give some useful hint:

Looking at the configuration you showed, and assuming you use the default ejabberd config from https://github.com/processone/docker-ejabberd/blob/master/ecs/conf/ejabberd.yml#L38

In that configuration file it says that:

• port 5222 is used for XMPP C2S connections
• 5280 for HTTP connections
• and 5443 is used for HTTPS, including WebSocket, BOSH, web admin...

service: "wss://ejabberd-srv:5222/xmpp-websocket",

In your case, if your client uses WebSocket to connect to ejabberd, you should open the 5443 port in kubernetes and tell your client to use an URL like "wss://ejabberd-srv:5443/ws",

I'm not sure what you're using to code, but in order to set it in Android Studio, open the manifest of your project and under the "activity" section, put android:exported="true"(or false if that is what you prefer). I have attached an example.

my application hosting on IIS (Windows Server 2012)

I want to run my application endlessly.

A BackgroundService hosted in ASP.NET in IIS will run as long as your ASP.NET application runs. That's it. Since ASP.NET/IIS will restart periodically, your BackgroundService will be periodically shut down (and restarted). Neither ASP.NET nor IIS were designed for long-lived background processes; they were designed for HTTP services. In the general case (i.e., cloud providers), your app may actually be shut down until the next HTTP request comes in.

If this is not acceptable, then ASP.NET/IIS is not the correct host for your needs. You can use a Win32 Service host instead of ASP.NET/IIS by creating a new project with the Worker Service template, adding a Win32 Service lifetime, and hosting the same BackgroundService in that application instead of in your ASP.NET app.

This can't work - functions defined inside another function ("inner functions") only "exist" as variables inside the outer function's local scope. They're not accessible to any other code. ​The unittest discovery won't find them, and couldn't call them even if it knew about them.

You get an undefined error for your job id because:

1. You use poll: X on your initial task, so ansible connects every X seconds to check if the task is finished
2. When ansible exists that task and enters your next async_status task, the job is done. And since you used a non-zero value to poll the async status cache is automatically cleared.
3. since the cache was cleared, the job id does not exist anymore.

Your above scenario is meant to be used to avoid timeouts with your target on long running tasks, not to run tasks concurrently and have a later checkpoint on their status. For this second requirement, you need to run the async task with poll: 0 and clean-up the cache by yourself

See the documentation for more explanation on the above concepts:

• ansible async guide
• ansible async_status module

I made an example with your above task and fixed it to use the dedicated module apt (note that you could add a name option to the module with one or a list of packages and ansible would do both the cache update and install in a single step). Also, retries * delay on the async_status task should be equal or greater than async on the initial task if you want to make sure that you won't miss the end.

Q: "The module shell shows changed every time I run it"

A: In async mode the task can't be skipped immediately. First, the module shell must find out whether the file /opt/assure1/logs/SetupWizard.log exists at the remote host or not. Then, if the file exists the module will decide to skip the execution of the command. But, you run the task asynchronously. In this case, Ansible starts the module and returns without waiting for the module to complete. That's what the registered variable Assure1InstallWait says. The task started but didn't finish yet.

You need wait_for instead of wait_for_connection. It is run locally:

You will have to do it like this:

You cannot get the phone number from the QR since the value after ../qr/ is decoded by WhatsApp.
If you only want to open the WhatsApp application (that will later ask you to add the contact), once you have the qr code link https://wa.me/qr/YOUR_CODE you can just open the url using a normal intent. The code below should do the work and you will see a dialog prompting to chose between a browser or Whatsapp if it is installed: