Robert Sachunsky

@MehmedGIT can you please help? The [CI fails for py310 ubuntu:22](https://github.com/OCR-D/core/actions/runs/9659280016/job/26642275100?pr=1239) only. The only context is ``` Network ocrd_network_test Creating Network ocrd_network_test Created Container ocrd_network_mongo_db Creating Container ocrd_network_rabbit_mq Creating Container...

So the last commit ensured that Github will show our pytest and flake8 results directly. However, IMO we should modify our Makefile to make sure that `PYTEST_ARGS` is used in...

Also, does anybody know what's wrong with the Scrutinizer setup?

also #877 and #740

Admitted, this would be a rather severe (and therefore risky) change. We should wait until we have robust real-life real-data regression testing (again). To elaborate, I believe the following would...

As the error message already states: with TF >= 2.11, you have to wrap an `tf.keras.optimizers.legacy.Optimizer` rather than `tf.keras.optimizers.Optimizer` (because the latter is now what used to be `tf.keras.optimizers.experimental.Optimizer`).

A couple of points worth discussing: - In contrast to the formulation in #322, there is no single `process_page` now. We have too many cases to consider of what processors...

BTW, I consider it bad practice that we always load the ocrd-tool.json in the inheriting constructor. It should really be a class attribute. And assuming it is always placed in...

> BTW, I consider it bad practice that we always load the ocrd-tool.json in the inheriting constructor. > > It should really be a class attribute. And assuming it is...

Notice how `Processor.setup` currently only gets called if one is using `run_processor` (via `get_processor` actually). So it's not enough anymore to just instantiate a processor and call `process` or `process_workspace`...