Locker | Locker - the `` me '' platform | Application Framework library

When you constrain both X and Y to any, you lose all interface-implementor relationship. The only thing that is known at compile time is that X and Y are different types, and you can't assign one to the another within the function body.

A way to make it compile is to use an explicit assertion:

OK so a coworker helped me find a solution.

Sources:

• https://nathankleyn.com/2017/12/29/using-transient-and-lazy-vals-to-avoid-spark-serialisation-issues/
• https://www.waitingforcode.com/apache-spark/serialization-issues-part-2/read#serializable_factory_wrapper

Code:

Perhaps something like this?

One way could be to use a second y axis. Although this method is to be used critically, in this situation I think it is appropriate:

From what I understood, when you input as action, you get the list of movies and then a No matches like this:

I encountered same issue and you can use TapGestureHandler from react-native-guesture-handler to make the clicks work.

I think you could unstack + convert MultiIndex to a plain index + transpose:

There are different things to point out:

1. Instead of find_all() that would return a resultset use find(), cause there is only one script tag the would match.

2. Intstead of converting the tag and its content into a str() use .text to extract the content.

3. Main issue is that you have to replace all " in your extracted text, cause per se it is no valid json if you print, it would look like:

   '{"@context":"http://schema.org","@type":"Product","aggregateRating"...'

Fix:

• Unfortunately, as of PowerShell 7.2.1, the automatic $? variable has no meaningful value after calling a written-in-PowerShell function (as opposed to a binary cmdlet) . (More immediately, even inside the function, $? only reflects $false at the very start of the catch block, as Mathias notes).

  • If PowerShell functions had feature parity with binary cmdlets, then emitting at least one (non-script-terminating) error, such as with Write-Error, would set $? in the caller's scope to $false, but that is currently not the case.

  • You can work around this limitation by using $PSCmdlet.WriteError() from an advanced function or script, but that is quite cumbersome. The same applies to $PSCmdlet.ThrowTerminatingError(), which is the only way to create a statement-terminating error from PowerShell code. (By contrast, the throw statement generates a script-terminating error, i.e. terminates the entire script and its callers - unless a try / catch or trap statement catches the error somewhere up the call stack).

  • See this answer for more information and links to relevant GitHub issues.

• As a workaround, I suggest:

  • Make your function an advanced one, so as to enable support for the common -ErrorVariable parameter - it allows you to collect all non-terminating errors emitted by the function in a self-chosen variable.

    • Note: The self-chosen variable name must be passed without the $; e.g., to collection in variable $errs, use -ErrorVariable errs; do NOT use Error / $Error, because $Error is the automatic variable that collects all errors that occur in the entire session.

    • You can combine this with the common -ErrorAction parameter to initially silence the errors (-ErrorAction SilentlyContinue), so you can emit them later on demand. Do NOT use -ErrorAction Stop, because it will render -ErrorVariable useless and instead abort your script as a whole.

  • You can let the errors simply occur - no need for a try / catch statement: since there is no throw statement in your code, your loop will continue to run even if errors occur in a given iteration.

    • Note: While it is possible to trap terminating errors inside the loop with try / catch and then relay them as non-terminating ones with $_ | Write-Error in the catch block, you'll end up with each such error twice in the variable passed to -ErrorVariable. (If you didn't relay, the errors would still be collected, but not print.)

  • After invocation, check if any errors were collected, to determine whether at least one key wasn't backed up successfully.

  • As an aside: Of course, you could alternatively make your function output (return) a Boolean ($true or $false) to indicate whether errors occurred, but that wouldn't be an option for functions designed to output data.

Here's the outline of this approach: