Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in scan (file = file, ... : line X did not have 6 elements #29

Closed
scossin opened this issue Feb 2, 2021 · 3 comments
Closed

Error in scan (file = file, ... : line X did not have 6 elements #29

scossin opened this issue Feb 2, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@scossin
Copy link

scossin commented Feb 2, 2021

Describe the bug

logs <- read.table(file = file.path(outputFolder, "log_catalogueExport.txt"),

The error occurs if the log file doesn't contain 6 elements.

The log file doesn't contain 6 elements if only one of the queries doesn't work: an error is logged and the line added doesn't contain 6 elements:

ParallelLogger::logError(sprintf("Analysis %d -- ERROR %s", mainSql$analysisId, e))

This error is very annoying because it occurs at the end of all the SQL queries before the CATALOGUE_RESULTS tables are created so it seems difficult to recover from this error.

To Reproduce
Run an analysis with the CatalogueExport::catalogueExport() containing a SQL error in one of the queries, with default parameters and numThreads=1

@scossin scossin added the bug Something isn't working label Feb 2, 2021
@PRijnbeek
Copy link
Contributor

Yes in principle no queries should fail and we may need to stop if they do to avoid these issues. Not sure about the 6 elements will try to reproduce (never happened earlier even when queries did fail for me).

@PRijnbeek
Copy link
Contributor

PRijnbeek commented Mar 7, 2021

I am not able to reproduce this when I simulate an error in the query on the current dev version

it then adds this row:

2021-03-07 17:07:20 [Main thread] ERROR CatalogueExport 3 Analysis 0 -- ERROR Error: Error executing SQL: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'synpuf.personP'. An error report has been created at /Users/Rijnbeek/Documents/Github/EHDEN/CatalogueExport/errorReportSql.txt

Which is read successfully:

image

@PRijnbeek
Copy link
Contributor

Will close it when pulling in dev. Re-open if this still is an issue.

@PRijnbeek PRijnbeek mentioned this issue Mar 7, 2021
PRijnbeek added a commit that referenced this issue Mar 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants