Shout | SSH made easy in Swift | SSH Utils library

Change from ${files} to ${file}. You just want the one file that .map() is currently iterating for that specific iteration, not the whole array:

Alright so I managed to make it work (repository has been updated accordingly).

All I needed was to actually inline the css and js, in order to achieve that I leveraged this bit here: https://www.npmjs.com/package/vite-plugin-singlefile.

I created another config dedicated to the inlined stuffery:

vite.config.inlined.ts:

The problem is that the subquery and the surrounding query share the same snapshot, that is, they see the same state of the database. Hence the outer query cannot see the rows inserted by the inner query.

See the documentation (which explains that in the context of WITH, although it also applies here):

The sub-statements in WITH are executed concurrently with each other and with the main query. Therefore, when using data-modifying statements in WITH, the order in which the specified updates actually happen is unpredictable. All the statements are executed with the same snapshot (see Chapter 13), so they cannot “see” one another's effects on the target tables.

In addition, there is a second problem with your approach: if you run EXPLAIN (ANALYZE) on your statement, you will find that the subquery is not executed at all! Since the table is empty, there is no id, and running the subquery is not necessary to calculate the (empty) result.

You will have to run that in two different statements. Or, better, do it in a different fashion: updating a row that you just inserted is unnecessarily wasteful.

try wrap these lines inside a setState:

• The automatic $args variable is only available in simple (non-advanced) functions / scripts. A script automatically becomes an advanced one by using the [CmdletBinding()] attribute and/or at least one per-parameter [Parameter()] attribute.

  • Using $args allows a function/script to accept an open-ended number of positional arguments, usually instead of, but also in addition to using explicitly declared parameters.

  • But it doesn't allow passing named arguments (arguments prefixed by a predeclared target parameter name, e.g., -Title)

• For robustness, using an advanced (cmdlet-like) function or script is preferable; such functions / scripts:

  • They require declaring parameters explicitly.
  • They accept no arguments other than ones that bind to declared parameters.
    • However, you can define a single catch-all parameter that collects all positional arguments that don't bind to any of the other predeclared parameters, using [Parameter(ValueFromRemainingArguments)].

• Explicitly defined parameters are positional by default, in the order in which they are declared inside the param(...) block.

  • You can turn off this default with [CmdletBinding(PositionalBinding=$false)],
  • which then allows you to selectively enable positional binding, using the Position property of the individual [Parameter()] attributes.

• When you call a PowerShell script via the PowerShell's CLI's -File parameter, the invocation syntax is fundamentally the same as when calling script from inside PowerShell; that is, you can pass named arguments and/or - if supported - positional arguments.

  • Constraints:
    • The arguments are treated as literals.
    • Passing array arguments (,-separated elements) is not supported.
  • If you do need your arguments to be interpreted as they would be from inside PowerShell, use the -Command / -c CLI parameter instead
  • See this answer for guidance on when to use -File vs. `-Command.

To put it all together:

ToastNotificationMix.ps1:

Specifying the full path of the command worked:

Short ansewer

The code works fine, i'll leave it here just in case somebody needs it in the future. Bug wasn't in the code, it was in the data that i was provided with.

Detailed Explanation

The code works fine. The data that i was provided with was manipulated for some reasons by my client so that each variable product wasn't a real variable product but at the same time the labels were typed in as variable products (yea i know it's confusing and not a standard practice), that's why whenever i tried to add them to cart, it would give the error saying {your-attribute} is a required field.

So we deleted each product data and add it back as a real and true variable product, then the code worked without us changing anything in it.

Take-away
So remember, whenever developing your app, there are always two sides to this coin! One side is your code and the other side is the data you're working on.

So, always always always, make sure the data you're working with is the way/format it's supposed to be. Also if you can't find any bug in your code, remember to check/debug the other side which is the data.
If you don't check the data first or at any debugging stage, then it'll be hard to track down the issue down the road!

This bug created a long delay in the project (about 2 weeks until we tracked down the bug in the data). So make sure to always check the both sides of the coin:

• First, the data you're working with
• Second, the code you wrote.

You need to add the Space between UserHome.

Looking at the setup.py, it looks like the package just doesn't support Windows. All those os.system() calls are POSIX-only.