nestor

You need to configure your ssh target node and set up correctly on the Rundeck's node source, your node definition needs more attributes, I leave these steps to configure from scratch:

1. Make sure that your target ssh config admits password login (enable PasswordAuthentication yes on the /etc/ssh/sshd_config config file and restart the sshd service: systemctl restart sshd).

2. On the Rundeck side create a password key to reference it later in the resources.xml file (ssh-password-storage-path attribute).

3. On Rundeck side, make sure that you're using a well-configured node definition. I used the following resources.xml content example:

apply blow logic

You are getting an error message : "ReferenceError: orderNum is not define).

This is because your Logger statement is not part of a function.

Logger is a feature of Google scripts and Logger.log is well documented.

In the following example, I have included three versions of a Logger statement.

• Logger.log("the order number is "+orderNum);: in this case the description text is in quotes, followed by the "+" operator and the variable name.
• Logger.log('var %s', orderNum);: the suggestion made by @Tanaike. In the case, '%s' acts as a placeholder doc ref.
• Logger.log('var ', orderNum);: this is your logger statement, but this time it is included within the function.

These statements return these results:

• the order number is 1001
• var 1001.0
• var 1001.0

You are right, this is because SSR - there is no window during build. One way is to use tags in your template and make all this things in mounted() in export.

In this particular case you are lucky: there's a plugin for your component. Gridsome plugin library contains many wrappers for vue components, so you can use them easier.

The array contains references to the objects.when you bind the array item to value value="{{ reply.text }}" the references of currentResponse.replies is attached to this.so when you update the value of input box it automatically update the array.

I must confess I haven't fully read your question as its huge but I kinda have an idea on what you're after. Is not the solution to separate the sending part from the SQL part? So create a new table called queue and insert all actions into a new table. You then run a separate cron/task which sends the emails as long as a particular user hasn't been contacted in the last X minutes. That way you can preserve a sense of uniqueness.

Use recipient NOT IN (SELECT ...) and author NOT IN (SELECT ...) to exclude the participants that match your conditions 1 and 2.

It depends on your use case.

Most of the time you can get away with a shallow copy.

But if for some reason, the props (or state) you are passing needs deep comparison, then you will have to resort to libraries like react-fast-compare.

Using a shallow copy won't introduce any bugs, at worst some of your components will not re-render properly.

You might want to read these :

https://daveceddia.com/react-redux-immutability-guide/

https://github.com/FormidableLabs/react-fast-compare

In case any one wants to do the same task using SparkSession, below is the code: