timber | Create WordPress themes with beautiful OOP code | Content Management System library

produce the message through a command ... I surprisingly receive it in the consumer terminal T7

No surprise here since you've not called producer.flush() or producer.close() in your Python producer app after starting the consumer loop.

The console producer blocks on every record by calling get() on the future - source, effectively flushing its buffer

Alternatively, you are missing the matching option for --from-beginning in the Python consumer if you wanted to see the previously sent records

Ultimately, testing a local client/server within the same network adapter/subnet isn't going to help resolve an external network connection

Change

For the First question the param of createQueryBuilder which is user in your case, it's the alias you use in your query:

SELECT user., photo. FROM users user INNER JOIN photos photo ON photo.user = user.id AND photo.isRemoved = FALSE WHERE user.name = 'Timber'

const user = await createQueryBuilder("user") .innerJoinAndSelect("user.photos", "photo", "photo.isRemoved = :isRemoved", { isRemoved: false }) .where("user.name = :name", { name: "Timber" }) .getOne();

The second question:The first argument is the relation you want to load, the second argument is an alias you assign to this relation's table and the third one is optional for any condition you'd add

the forth question, you should use getMany() instead of getOne();

I didn't understand the third question.

Try to use PublishSubject, seems like it was created for cases like yours.

LiveData is a state holder and it's designed to serve this purpose. So it guarantees that all active (whose state is at least STARTED) observers will eventually receive the latest value of this LiveData, but all intermediate values can be conflated. If you need all the posted values to be delivered without conflation, you should use another abstraction - e.g kotlin channel.

I missed to add Hilt plugin and dependencies in build.gradle.kts for feature module :

If your viewModel.emailCheck flow is a hot flow, then you need to manage its life cycle by yourself. If it is not a hot Flow, then you need to use LiveData to control the interface instead of simply collecting Flow. You should convert the flow to LiveData, and add the Observer to LiveData at the corresponding location.

There is no API related to the interface life cycle in Cold Flow, but the life cycle is already managed in LiveData.

It is preferable to use WorkManager if your min sdk is 14+. It will save you from a lot of hassles of using and managing a foreground service.

https://developer.android.com/topic/libraries/architecture/workmanager

Sending location updates is one of the best use case of WorkManager.

I had the same issue and turned out that the buildToolsVersion "30.0.3" used is not installed, so I switched to the installed buildToolsVersion "29.0.3" (in my case) and the warning disappeared.