jobmanager | Android library for executing tasks | Job Scheduling library

There are two major reasons for this cause.

1. Setting enableDangerousExperimentalLeanBuils to true.
2. Missing expo-splash-screen package.

The error is because it's(Gradle build) looking for expo-modules-splashscreen package, which is supposedly moved out of expo's main module in SDK 41, hence needs to be separately installed. In order to fix this, there are two workarounds:

1. Remove enableDangerousExperimentalLeanBuilds property. (Not tested)
2. Install expo-splash-screen using npm install expo-splash-screen.(Tested and working)

To use SendFileAsync, you need to have the file locally. If you want to send a URL without downloading, just use SendMessageAsync. Discord will preview the image from the URL (unless the user disabled that manually).

Otherwise, this would help:

The RocksDB state backend does keep its working state on each task manager's local disk, while checkpoints are normally stored in a distributed filesystem.

If you have checkpointing enabled, then the spare task manager is able to recover the state from the latest checkpoint and resume processing.

You could disable the chaining via (disableChaining()) and start a new chain to isolate it from others via (startNewChain()). You can play with Flink Plan Visualizer to see if your plan has isolated operators. These modifiers applied affter the operator. Example:

I have no clue why, but skipping SocketChannel and IMessageChannel declarations worked:

If you annotate a method with @Activate it will be called when the component starts.

@Activate public void startScheduledJob()

I guess you want your job to run on startup. Another option would be to let MyJobService be a servlet and call it from outside.

So the problem in this case is that Applications in close vicinity import each other, but not in the way it would make sense.

There was a second application without the exclude, and so Spring figured it could just add the excluded class anyways. I wanted to have feature / package based Spring test application, this seems not to be possible. I merged them into one big application and now exclusion works normally.

If you look at the documentation, set_handler requires a 'static callback, meaning the callback must be able to live forever.

Here your callback includes a reference to self, meaning it can't outlive self ('a), which is definitely not 'static.

The simplest way to fix this issue is to pass only "owned" data to the callback, e.g.

The way Flink works internally is that the Dispatcher creates for every submitted job a dedicated JobMaster component. This component needs a leader election and for this purpose it creates a k8s-ha-app1--jobmanager config map. This is the reason why you see multiple xyz-jobmanager ConfigMaps being created.

The reason why these ConfigMaps are not cleaned up is that this currently happens only when the whole cluster is shut down. This is a limitation and the Flink community has created FLINK-20695 in order to fix it. The idea is that the JobMaster related ConfigMaps can be deleted after the job has reached a terminal state.

A bit related is another limitation which hampers the proper clean up in case of a session cluster. If the cluster is shut down with a SIGTERM signal then it is currently not guaranteed that all resources are cleaned up. See FLINK-21008 for more information.