klass | a utility for creating expressive classes in JavaScript | Translation library

You haven't mentioned this, but I assume you're using the nightly builds published in npm as typescript@next. If so, you are likely seeing a preview of a new feature for TypeScript 4.4, "strict optional properties", as implemented in microsoft/TypeScript#43947. (UPDATE 2021-06-10) This functionality was originally going to be enabled via a new --strictOptionalProperties compiler flag, which would have been included in the --strict suite of compiler options. However, according to this comment, the flag will be renamed and removed from --strict, so anyone who wants to see this behavior in TypeScript 4.4 and above will need to manually enable it, via some compiler flag whose name has not yet been decided.

Strict optional properties will prevent you from assigning undefined to an optional property, while still allowing you to read undefined from such a property. This is more in keeping with how people have wanted optional properties to be for a long time, as evidenced by the (now finally closed) issue microsoft/TypeScript#13195.

Anyway, this means it is no longer safe to assign a value read from an optional parameter into an optional property of the same type, without first checking if it is undefined:

The error is telling you: django.db.utils.IntegrityError: UNIQUE constraint failed: libman_klass.school_id, libman_klass.name. This means that the unique_together on your models is throwing an error as you are trying to save a school and name which already exists in the database.

For example the code below, a Klass with the school=request.user.school and name=2 already exists but you have a unique together constraint to prevent this.

brew install ./cmake.rb will try to install a bottle, which obviously doesn't exist anymore. Try installing from source with brew install -s ./cmake.rb.

Apache Arrow utilizes a pretty similar idea of Java off-heap storage as Apache Ignite does. For Apache Arrow it means that objects like IntVector don't actually store data in their on-heap layout. They just store a reference to a buffer containing an off-heap address of a physical representation. Technically it's a long offset pointing to a chunk of memory within JVM address space.

When you restart your JVM, address space changes. But in your Apache Ignite native persistence there's a record holding an old pointer. It leads to a SIGSEGV because it's not in the JVM address anymore (in fact it doesn't even exist after a restart).

You could use Apache Arrow serialization machinery to store data permanently in Apache Ignite or even somewhere else. But in fact after that you're going to lose Apache Arrow preciousness as a fast in-memory columnar store. It was initially designed to share off-heap data across multiple data-processing solutions.

Therefore I believe that technically it could be possible to leverage Apache Ignite binary storage format. In that case a custom BinarySerializer should be implemented. After that it would be possible to use it with the Apache Arrow vector classes.

I can confirm my theory stated in Edit 3:

The mono runtime doesn't quite support virtual methods in generic Interfaces! (Or at least not retrieving stack frame information of them).

Therefore changing the interface declaration of IGenericCell from

One option via merge:

The error is not saying your driver doesn't exist, it's saying the Connector doesn't. Scan over your error for each PluginDesc{klass=class and you'll notice the connector.class you're trying to use isn't there

The latest Kafka Connect images from Confluent include no connectors, outside of those pre-bundled with Kafka (and some ones from Control Center, which aren't really useful), so you must install others on your own - described here

If you want to follow the 5.0 documentation, use the appropriate tagged docker image rather than latest (the old images do have the connectors installed)

Also, you would need to place the jdbc driver directly into the jdbc connector folder for it to properly be detected on the classpath; it is not a "plugin" in Connect terminology. The above link also shows an example of this

This is more of a workaround than addressing the root cause.

The issue is due to na values in some of the columns. You can get around this by using keep_default_na=False in read_csv to get empty strings instead of na values in the Info column:

Before you draw new information to the screen you want to clear it.

to do this you want to do