Robert Sachunsky

Results 944 comments of Robert Sachunsky

It's clear the reason for this is that [ResourceManager.list_available only returns database results](https://github.com/OCR-D/core/blob/b7130307ce68c5f074c1ceea24b66ae9ee9ef289/ocrd/ocrd/resource_manager.py#L102-L109) – it does **not** look up all `ocrd-` executables in PATH. (For comparison, [ResourceManager.list_installed returns database results...

Speaking of short-circuiting with `ocrd-all-tool.json`: we do not have a dedicated issue for that, but since it's probably tied to the solution here, anyway: The idea would be to have...

> Implementing [this](https://github.com/OCR-D/pull/974) in bashlib processors will be very difficult. This is absolutely not about (re-)implementing the Processing Server. It's merely about **delegating** to the `ocrd processing-worker` subcommand, implemented as...

> I'm wondering whether we want to / can continue to support bashlib fully or whether it wouldn't be easier to convert ocrd_olena, ocrd_fileformat etc. to python. I've said this...

> But you could easily reimplement bashlib procesors in python by just delegating the calls of the actual tools to `subprocess.run` and have the full expressivity and OCR-D/core support of...

The original issue was resolved via #1024. So do we want to repurpose (and rename) this for your new idea of providing a Python-only general purpose wrapper doing preconfigured shell...

Discussion continued as follows: - @kba suggested using the static [ocrd-all-tool.json](https://ocr-d.de/js/ocrd-all-tool.json) files as a stop-gap. - @MehmedGIT added #1028 to utilise that in the Processing Server - @bertsky provided https://github.com/OCR-D/ocrd_all/pull/362...

BTW I believe for the full Web API including `/discovery`, we would need central worker registration anyway.

> > BTW I believe for the full Web API including /discovery, we would need central worker registration anyway. > > True. We still need to think about how exactly...

The discussion then continued to details of alternative solutions: - @bertsky proposed an [alternative mechanism](https://github.com/OCR-D/core/pull/974#discussion_r1121549686) for native processor sessions which would require keeping the SSH connection open but kill it...