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
When a database that is being imported into a PostgreSQL internal database contains weird content, the whole import process fails.
This database error-weird-content.db.zip contains a FilePair that cannot be imported to a PostgreSQL database.
INFO[2018-03-22 17:04:55] request started http_method=POST http_proto=HTTP/1.1 http_scheme=http remote_addr="127.0.0.1:53496" uri="http://cat.sourced.tech:8080/api/experiments/1/file-pairs" user_agent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36"
INFO[2018-03-22 17:04:55] Failed to insert row
error: pq: invalid byte sequence for encoding "UTF8": 0xce 0xc4
http_method=POST http_proto=HTTP/1.1 http_scheme=http remote_addr="127.0.0.1:53496" uri="http://cat.sourced.tech:8080/api/experiments/1/file-pairs" user_agent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36"
ERRO[2018-03-22 17:04:55] pq: Could not complete operation in a failed transaction http_method=POST http_proto=HTTP/1.1 http_scheme=http remote_addr="127.0.0.1:53496" uri="http://cat.sourced.tech:8080/api/experiments/1/file-pairs" user_agent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36"
That FilePair was found inside the 2000 FilePairs database provided by ML, and it was properly imported into the internal SQlite database on Staging as id#1635
The text was updated successfully, but these errors were encountered:
Interesting, did you have a chance to look a bit deeper into this?
I.e does this mean that some content in SQLite we have is already not UTF-8 encoded, or does it gets messed up on the application side?
I didn't spend more time digging into this problem.
I only tried to find the way to reproduce it and confirm which FilePair could serve us as an example.
In this case, the file in the zip can be seen in Staging if you go to the pair with id#1635
Should I try to confirm if the content in SQLite is the same as the provided by ML, or if was it ruined when imported also in the internal SQLite DB?
Uh oh!
There was an error while loading. Please reload this page.
When a database that is being imported into a PostgreSQL internal database contains weird content, the whole import process fails.
This database error-weird-content.db.zip contains a FilePair that cannot be imported to a PostgreSQL database.
That FilePair was found inside the 2000 FilePairs database provided by ML, and it was properly imported into the internal SQlite database on Staging as
id#1635
The text was updated successfully, but these errors were encountered: