tbvdm
Issue with Invalid Arguments and Mentions in JSON Files
I'm encountering multiple instances where the system is returning errors related to invalid arguments while opening JSON files, as well as issues with invalid mentions in messages.
sigtop: open <filename>.json: invalid argument
sigtop: invalid mention (index: X, body: X Y, placeholders: X, mentions: X: Y, Z)
sigtop: message with invalid mention (conversation: "<conversation name>", sent: <timestamp>)
sigtop: message with invalid mention in edit X (conversation: "<conversation name>", sent: <timestamp>)
sigtop: open <filename>.json: invalid argument
What OS? What filesystem? Can you say anything about the filename? Does it contain "special" (i.e. non-ASCII) characters? How many characters does it have?
sigtop: invalid mention (index: X, body: X Y, placeholders: X, mentions: X: Y, Z) sigtop: message with invalid mention (conversation: "<conversation name>", sent: <timestamp>)
sigtop: message with invalid mention in edit X (conversation: "<conversation name>", sent: <timestamp>)
Are you using the latest version of sigtop? If not, can you share the X/Y/Z values?
I am using Ubuntu 24.04 with an ext4 filesystem and the latest version of sigtop. When attempting to export data to an external disk formatted as exFAT, I encounter the following "invalid argument" errors (example with randomized names and dates, but the format remains the same):
sigtop: open PNI:85aeg5d-534v-745f-234f-dsf464t (PNI:PNI:85aeg5d-534v-745f-234f-dsf464t).json: invalid argument
sigtop: open Group Name || SubName❄️ (group).json: invalid argument
?6 (85aeg5d-534v-745f-234f-dsf464t ).json: invalid argument
However, when exporting to an ext4-formatted local disk, I receive these errors only (but they also occour for exFAT):
sigtop: cannot fix edited long message (conversation: "Group Name", sent: 2025-02-20 01:42:31 (174029000345))
sigtop: attachment without path
sigtop: open Channel1 (group).json: file exists
Interestingly, I did not encounter the "invalid argument" errors today for unknown reasons.
I am using Ubuntu 24.04 with an ext4 filesystem and the latest version of sigtop. When attempting to export data to an external disk formatted as exFAT, I encounter the following "invalid argument" errors (example with randomized names and dates, but the format remains the same):
sigtop: open PNI:85aeg5d-534v-745f-234f-dsf464t (PNI:PNI:85aeg5d-534v-745f-234f-dsf464t).json: invalid argument sigtop: open Group Name || SubName❄️ (group).json: invalid argument ?6 (85aeg5d-534v-745f-234f-dsf464t ).json: invalid argument
sigtop cannot create these files because the filenames contain characters that are not permitted on exFAT. sigtop properly sanitises filenames for exFAT on Windows, but not on Unix.
sigtop: cannot fix edited long message (conversation: "Group Name", sent: 2025-02-20 01:42:31 (174029000345))
You can ignore this error. It is a failed attempt to work around a (minor) bug in Signal.
sigtop: attachment without path
This is an as yet unsolved problem that is tracked in #51.
sigtop: open Channel1 (group).json: file exists
This is because you have two groups with the same name. I'll commit a fix for this soon.
Thank you very much for the quick response. I will try to export messages only to my ext4 filesystem for now, but will still need to extract all media files to my exFAT disk.
Some groups is actually named something similar to <-Group------name------US>, which seems like it is not permitted on ext4 either, is there any way these type of names can be defaulted to exported as their group id instead, if this error occurs?
I replied by email but GitHub is unreliable. New attempt:
I'm very busy at the moment. Sorry. I'll get back to you as soon as possible.
Some groups is actually named something similar to
<-Group------name------US>, which seems like it is not permitted on ext4 either
That's not likely given that ext4 disallows only NUL and slash in filenames. What is the exact error you're getting?