Unknown file: hapi-fhir-cli....zip when uploading terminology

[MacL3an]

Trying to follow the instructions on how to load a CodingSystem into HAPI FHIR. Running HAPI using docker compose and MySQL. I then run:

hapi-fhir-cli upload-terminology -d Loinc_2.72.zip -v r4 -t https://localhost:8080/fhir -u https://loinc.org

Which gives me the following errors in the logs:

2022-02-22 10:08:21.112 [http-nio-8080-exec-9] INFO  c.u.f.j.p.TerminologyUploaderProvider [TerminologyUploaderProvider.java:378] Reading in local file: /var/folders/c7/908fsfh92msc5bx31kx8x57r0000gn/T/hapi-fhir-cli4557113645459213.zip
2022-02-22 10:08:21.114 [http-nio-8080-exec-9] WARN  c.u.f.r.s.i.ExceptionHandlingInterceptor [ExceptionHandlingInterceptor.java:148] Failure during REST processing: ca.uhn.fhir.rest.server.exceptions.InvalidRequestException: HAPI-1141: Unknown file: hapi-fhir-cli4557113645459213.zip
2022-02-22 10:08:21.117 [http-nio-8080-exec-9] INFO  fhirtest.access [LoggingInterceptor.java:160] ERROR - POST https://localhost:8080/fhir/CodeSystem/$upload-external-code-system

When I try doing the same against a servert started using hapi-fhir-cli run-server -v r4 it works fine, but this the drawback then is that it's using a local DB and I would like to use an external DB like MySQL. So it seems there is something in the interaction with the CLI that is not working?

[MacL3an]

Ah, noticed this might be a duplicate of this one.

[joeflack4]

This issue is also mirrored here, where I provide much more detail, including the cause in my case, being Docker issues. More info: hapifhir/hapi-fhir#3276

Related; this is also about LOINC, but a different error: hapifhir/hapi-fhir#1629

[github-actions]

This issue is stale because it has been open 730 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[joeflack4]

Read down from here: hapifhir/hapi-fhir#3276 (comment)
In this other thread, the problem is described as seeming to have to do with a fixed file size limit, and someone suggests how to override that limit to fix the issue.

So I guess the issue is fixable, but at the very least, there should be a better error message for when this happens.