Closed allaway closed 1 month ago
It should be something doing with this chunk of codes: https://github.com/Sage-Bionetworks/data_curator/blob/fa9386a675007296bb3758dd0c78825d41277381/functions/validationResult.R#L64-L66
I think it is because the types of values are not consistent. If you try to add as.character, like Value = as.character(i[[4]][[1]])
, it might solve the issue. Feel free to create a PR if that works. I can double check and address it in this repo tomorrow as well.
Thanks for reporting @allaway.
Thanks Rong! I will try that!
@rrchai, unfortunately, this doesn't appear to resolve the issue :(
I am transferring this issue to schematic
. It appears to be a problem with list validation, not the DCA.
I did something similar to @rrchai suggestion. The initial error was:
Error in bind_rows: Can't combine ..1$Column<integer> and..2$Column <character>.
So, I wrapped Column in as.character:
Then, when I try to run the same manifest through, I get a different crash+Error:
2022-05-21T18:40:04.373158+00:00 shinyapps[5711947]: Warning: Error in name2int: You specified the columns: 0, but the column names of the data are , Component, Filename, resourceType, progressReportNumber, dataType, assay, platform, individualID, parentSpecimenID, runType, libraryPrep, comments, age, ageUnit, aliquotID, cellType, dataSubtype, diagnosis, dissociationMethod, eTag, fileFormat, fundingAgency, initiative, isCellLine, isPrimaryCell, isStranded, libraryPreparationMethod, modelSystemName, nf1Genotype, nf2Genotype, nucleicAcidSource, organ, readDepth, readLength, readPair, readPairOrientation, readStrandOrigin, sex, species, specimenID, specimenPreparationMethod, studyId, studyName, tissue, tumorType, entityId
After a bit of testing I found out that if I remove the columns with list validation (cellType, modelSystemName), this error goes away.
@allaway is this error resolved by the fix to #710 ?
Describe the bug When I try to validate a manifest (attached here) the DCA app crashes unexpectedly with the error
Error in bind_rows: Can't combine
..1$Column<integer> and
..2$Column<character>.
To Reproduce Steps to reproduce the behavior:
Expected behavior This shouldn't crash the app.
Priority (select one)
Additional context This hasn't happened with other manifests on the same version of the app/schematic, and validation of this manifest appears to work fine in the same branch of schematic CLI.
Therefore, it's something (1) specific to this manifest and (2) probably has to do with how DCA handles the manifest before or after the
schematic
validation.