Currently, cicp_inserter relies on the input file being valid.
Most files are valid so this isn't awful. But it means cicp_inserter can generate something problematic if the file is not valid.
cicp_inserter should at least notice an invalid file and warn the user. Perhaps adding a --quiet to silence warnings.
cicp_inserter should perhaps also fix invalid files that appear fixable. This might be trickier though because perhaps one program ignores the invalid piece of the file, showing an apparently-valid file to the user. "Fixing" it might change what the user sees. From the user's perspective, it was working and has become broken.
Currently, cicp_inserter relies on the input file being valid.
Most files are valid so this isn't awful. But it means cicp_inserter can generate something problematic if the file is not valid.
cicp_inserter should at least notice an invalid file and warn the user. Perhaps adding a --quiet to silence warnings.
cicp_inserter should perhaps also fix invalid files that appear fixable. This might be trickier though because perhaps one program ignores the invalid piece of the file, showing an apparently-valid file to the user. "Fixing" it might change what the user sees. From the user's perspective, it was working and has become broken.