Skip to content

Some contents causes a fatal error when importing databases into PostgreSQL  #224

@dpordomingo

Description

@dpordomingo

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions