No early-exit when target file exists during `osmium cat`

[tobschli]

What version of osmium-tool are you using?

osmium version 1.19.0
libosmium version 2.23.0
Supported PBF compression types: none zlib lz4

What operating system version are you using?

Linux: 6.18.18-1-MANJARO

Tell us something about your system

Probably not relevant in this case

What did you do exactly?

1. I have a valid planet.osm.pbf file (Region US from geofabrik):

➜ ls
planet.osm.pbf

2. I convert it to another format (e.g. .osm.bz2):

➜ osmium cat -o planet.osm.bz2 planet.osm.pbf --progress
[>                                                                       0%

3. I cancel this operation with ^C
4. The target file was created (although not complete, as I aborted the conversion):

➜ ls
planet.osm.bz2  planet.osm.pbf

6. When restarting this process, the tool seems to be stuck, as no progress is reported:

➜ osmium cat -o planet.osm.bz2 planet.osm.pbf --progress

---

The same behavior also appears when the source (or target) file are not readable / writable from the executing user.

What did you expect to happen?

I expected an error that it is not supported to overwrite files.
In the latter case, I expect an error that the file is not readable / writable.

What did happen instead?

osmium hangs until the process is destroyed by the user.

What did you do to try analyzing the problem?

I could confirm that conversion progress works as expected, when the target file was not present beforehand.

[lonvia]

I can confirm that the same behviour exists with osmium version 1.15.0 from an older Debian Bookworm.

[yuiseki]

I tried to reproduce this on current master (osmium-tool 1.19.1, libosmium 2.23.1, Ubuntu 24.04, gcc 13) and could not.

Tested conditions:

• Output file does not exist → works correctly
• Output file exists (empty) → exits immediately with File exists. Try using --overwrite
• Output file is a partial result left by a previous interrupted run → same error, clean exit
• Output file has no read/write permissions → same error, clean exit

In all cases the process exited with code 1 rather than hanging. It is possible the underlying issue was fixed somewhere between v1.19.0 and v1.19.1, or between libosmium v2.23.0 and v2.23.1. If you can still reproduce on a recent build it would help to narrow down which version introduced the fix.

[tobschli]

Ah! Actually nice to hear that!
I will try the patch versions later (today hopefully). If I can confirm that the issue is resolved, I will close the issue here.

[joto]

I have tested this also and do see the problem with a variety of libosmium/osmium-tool versions. But I am pretty sure this worked before. @yuiseki is not seeing this problem, so maybe it is related to some kernel or cpp std lib version or so. Could it be that the scheduler is deciding differently which threads to run?