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
The error "IMEX failed to complete: could not export database: [...] Error code 1: SQL error or missing database" should list the actual errno or the actual SQL error message in full
#6551
I've seen a user, who apparently tried to export a backup in delta chat desktop, come to me with the following error: IMEX failed to complete: could not export database: failed to export attached backup data base: disk I/O error: Error code 1: SQL error or missing database In the log file, there doesn't seem to be anything more specific either than this vague error message.
If I'm reading this error correctly, it might include 1. any errno like EIO with an actual disk error indicating a hardware problem, 2. or any errno like EPERM indicating a permission problem, 3. or any errno like ENOENT indicating the database was moved around or the path somehow assembled wrongly indicating an install problem, 4. or any SQL error indicating any sort of schema problem with the underlying database.
This seems like too many potential error sources mapped to a single error message. I suggest that the error message should include either the actual system errno on Linux, or the actual SQL error in case of a schema issue.
Operating System (Linux/Mac/Windows/iOS/Android): Linux
Expected behavior: The error message gives either the exact system errno on Linux, or the SQL error message in full, or at least logs this information to the log file.
Actual behavior: Neither the error message nor the log file seem to include the detailed underlying error.
Steps to reproduce the problem: 1. Not sure how exactly users commonly run into this error
Screenshots:
Logs:
The text was updated successfully, but these errors were encountered:
I've seen a user, who apparently tried to export a backup in delta chat desktop, come to me with the following error:
IMEX failed to complete: could not export database: failed to export attached backup data base: disk I/O error: Error code 1: SQL error or missing database
In the log file, there doesn't seem to be anything more specific either than this vague error message.If I'm reading this error correctly, it might include 1. any errno like EIO with an actual disk error indicating a hardware problem, 2. or any errno like EPERM indicating a permission problem, 3. or any errno like ENOENT indicating the database was moved around or the path somehow assembled wrongly indicating an install problem, 4. or any SQL error indicating any sort of schema problem with the underlying database.
This seems like too many potential error sources mapped to a single error message. I suggest that the error message should include either the actual system errno on Linux, or the actual SQL error in case of a schema issue.
The text was updated successfully, but these errors were encountered: