You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
airflow info --file-io fails: file.io no longer accepts anonymous POST uploads, and the failure crashes instead of raising a friendly error #73045
Running airflow info --file-io crashes instead of uploading the report and printing a shareable link.
1. file.io's anonymous upload endpoint no longer works. This is reproducible with a plain curl:
$ curl -sD - -o /dev/null -X POST -d test https://file.io
HTTP/2 301
location: https://www.file.io/
server: cloudflare
$ curl -sD - -o /dev/null -X POST -d test https://www.file.io/
HTTP/2 405
allow: GET, HEAD, OPTIONS
Even following file.io's own developer docs exactly — POST https://file.io/ as multipart/form-data with a file field, rather than a raw-body POST — the
same redirect happens:
https://www.file.io/ is now served as a static site (S3 behind Cloudflare) that only answers GET/HEAD/OPTIONS — POST is rejected outright, regardless of body format.
2. Airflow's own error handling for this case is broken, independent of (1). In _upload_text_to_fileio (airflow-core/src/airflow/cli/commands/info_command.py):
def_upload_text_to_fileio(content):
"""Upload text file to File.io service and return link."""resp=httpx.post("https://file.io", content=content)
ifresp.status_codenotin [200, 201]:
print(resp.json())
raiseFileIoException("Failed to send report to file.io service.")
...
Because a redirect/error response has an HTML body (not JSON), resp.json() raises json.JSONDecodeError (a ValueError) — and that call isn't wrapped in a try/except. So the
intended raise FileIoException(...) on the next line is never reached; an unhandled ValueError
propagates out of the function instead.
The tenacity.retry decorator on this function only retries FileIoException
(retry=tenacity.retry_if_exception_type(FileIoException)), so this ValueError isn't retried —
it's re-raised on the very first attempt. _send_report_to_fileio's except FileIoException as ex:
doesn't catch a plain ValueError either, so it propagates all the way up and crashes airflow info --file-io with an unhandled traceback, instead of the intended, friendly "Failed to send report to file.io service." message.
What you think should happen instead?
airflow info --file-io should either:
upload successfully to a working anonymous file-sharing backend, or
fail with the clear, intended FileIoException message — not an unhandled ValueError/ json.JSONDecodeError traceback — when the backend is unavailable.
changed the title [-]airflow info --file-io does not work[/-][+]airflow info --file-io fails: file.io no longer accepts anonymous POST uploads, and the failure crashes instead of raising a friendly error[/+]on Sep 12, 2026
I dug a little further into this, and it looks like file.io's anonymous upload backend is no longer available. The current file.io site appears to be static, while its upload functionality is backed by LimeWire and requires authentication.
So there doesn't seem to be a drop-in replacement for the current --file-io behavior.
Would it make more sense to deprecate --file-io rather than only fix the error handling? I'm happy to work on it if this direction makes sense.
@rjgoyln Thank you for the quick reply! I agree on the deprecation since file.io's anonymous upload path is genuinely gone.
In my opinion, deprecation is the right call here also because it seems to have been failing for a long time already without anyone complaining much, which suggests the feature isn't seeing much real usage anyway?
Activity
[-]airflow info --file-io does not work[/-][+]airflow info --file-io fails: file.io no longer accepts anonymous POST uploads, and the failure crashes instead of raising a friendly error[/+]rjgoyln commentedon Sep 12, 2026
I dug a little further into this, and it looks like file.io's anonymous upload backend is no longer available. The current file.io site appears to be static, while its upload functionality is backed by LimeWire and requires authentication.
So there doesn't seem to be a drop-in replacement for the current
--file-iobehavior.Would it make more sense to deprecate
--file-iorather than only fix the error handling? I'm happy to work on it if this direction makes sense.roykoand commentedon Sep 12, 2026
@rjgoyln Thank you for the quick reply! I agree on the deprecation since file.io's anonymous upload path is genuinely gone.
In my opinion, deprecation is the right call here also because it seems to have been failing for a long time already without anyone complaining much, which suggests the feature isn't seeing much real usage anyway?
kaxil commentedon Sep 13, 2026
PR: #73054
Remove airflow info `--file-io` as `file.io` dropped anonymous uploads (
Remove airflow info `--file-io` as `file.io` dropped anonymous uploads (