client-js | Backbone-based JavaScript client for WP API | Content Management System library

I think you've pretty much figured it out. Ktor freezes itself and all of its configuration in order to ensure that it can be used across threads in Kotlin/Native. Kodein assumes you will only ever touch it from one thread and is not safe to freeze. (Whether that's a limitation, a bug, or a design flaw is maybe up for interpretation.)

To work around these issues, you want to avoid accidentally capturing this references in your HttpClient configuration that refer to Kodein internals. A good way to do this is to grab instances from DI in helper variables outside the HttpClient lambda, as you've discovered.

If I understand the error correctly, your project requests for the debug version of the artifact, while in the build script I see publishLibraryVariants("release"). Try changing the script to follow the code snippet from the documentation.

It is resolved by upgrading ktor version to 1.3.2 or higher

thanks to @jackFeeting comment, I updated lxml and my code worked just fine. pip3 install --upgrade lxml updated from version 4.4.1 to 4.6.2

.icc files do not have a "source code" in the sense in which people normally use the term "source code". You might say, the .icc file is the source code, and it is interpreted by software that does something about images.

So if you have the .icc file, then you have the source code.

You probably have some .icc files on your computer, e.g. (from www.colourmanagement.net):

• ubuntu: /usr/share/color/icc
• windows: \system32\spool\drivers\color
• mac: /Library/ColorSync/Profiles or /Users//Library/ColorSync/Profiles

The ICC file format is ... well, a file format, like JPG or WAV. It's a sequence of bytes. I found the ICC Specification here on the page ICC Specifications.

To load and inspect a .icc file from an own program, I assume there are libraries for some programming languages. It seems that the ICC provides some themselves.

Short answer: no, with RelaySocket the connection is not peer-to-peer.

In UHST 1.x the relay was used for signalling the WebRTC connection (ICE peer exchange), but once WebRTC DataChannel is successfully established, the clients close the relay connection and all data transport is through WebRTC. The host keeps the relay connection open to signal new peers that need ICE exchange.

UHST 2.0 introduced the concept of RelaySocket which is an implementation of the UHST protocol over the relay instead of over WebRTC. WebRTC is still bundled with the JS client and can be enabled. With RelaySocket the relay acts as a man-in-the-middle which forwards messages between the clients and the host.

The main reason for switching to RelaySocket is to enable interoperability with mobile UHST clients (Flutter, iOS, Android) where WebRTC implementations are not readily available or standard. Also, if porting UHST to IoT devices WebRTC may not be available.

From comments: Lambda container will be destroyed after few minutes of inactivity and any changes made to disk or global memory, will not be persisted across invocations after this idle period or even in other threads.

In current example Quickbooks refresh token stored in disk and will not be persisted and refresh token from original lambda zip will be used in subsequent invocations.

Looks like pandas doesn't know how to properly handle character escaping in this instance in json. If you don't need to use pandas you can do something like: