Rectify | sample Android application that performs perspective | Learning library

your then method always return a value, even if your future is void, so you need to change your code to:

Try this:

The problem is completely unrelated to any r libraries. The reason why you only see it if you fix the r errors is that then your document is more than one page long and you actually get to see your fancy headers (the first page uses a different pagestyle, thus no error with only one page).

As the error messages says, the actual problem is that \theauthor is not defined. You manually define it for the title, you must also define it for the author.

i also had this issue, using the same tutorial

reading the docs on request body searches, i found it states the following:

Note The _search API accepts HTTP GET and POST for request body searches, but not all HTTP clients support adding a request body to a GET request. POST is the more universal choice.

changing my method to POST solved the issue for me

You're missing an 's', the parameter is called "algorithms" in the decode function:

My Gradle couldn't find the redacted-gradle-plugin but both of your classes compiles with this minimalistic build.gradle.kts:

See this Swift bug for an explanation and workaround from the Swift compiler team.

This is intentional. The ABI of enum cases with payloads that are potentially unavailable is not well-defined. That this worked in the past was by coincidence of your application not requiring the (potentially unavailable) type metadata for the payload. Please either increase your deployment target or mark Foo itself as available as the least-available case. https://github.com/apple/swift/pull/36327

So you either need to mark the whole enum as @available(iOS 13.0, *) or need to increase your deployment target to iOS 13.0.

The DST root formerly used and by default still bridged by LetsEncrypt just expired.

(note edits 10/05)

nodejs should successfully connect to a server using a LetsEncrypt cert with the 'compatibility' chain (i.e. still using the bridge to DST, even though it's expired, for old Android) IF

1. it has the ISRG root cert in its truststore aka root list. By default nodejs uses a compiled-in root list and v8.0.0 up contains the ISRG root. However application code like axios can replace or extend the compiled-in list, in which case it's the version/contents used by the application that matter.

2. AND nodejs uses OpenSSL 1.1.0 up (my previous belief that 1.1.1 was needed proved wrong on more thorough testing) OR the DST root is removed from the truststore (you can't remove it from the compiled-in list, but if you use a replacement list, you can omit/remove it from that).

   On Linux, at least a Linux distro with a package manager, nodejs is probably built to use the system-supplied OpenSSL; check what the package manager shows for dependencies, or whether ldd $(which node) lists some version of libssl and libcrypto (noting that different systems/packagers sometimes use version numbers for these library files that are related to, but NOT the same as, the OpenSSL version they contain!).

   On Windows, OpenSSL is usually not installed, and when it is, not necessarily in a fixed place, so nodejs is normally built to use its own (static-linked) OpenSSL. In this case the version of nodejs must be new enough, and I don't know what the mapping is, but it appears yours is sufficient.

EDIT: The better way is to use f2py is "the smart way"

just doing this works well