Closed enoriega closed 3 years ago
@kwalcock: can you please take a look at this asap? Not sure what is causing this: an incorrect json4s library version?
Adding @myedibleenso, in case he knows what this is. Thank you both!
Not sure what might happening here. There are tests in place for json serialization. This only happens for some papers?
I would take a look at the history for any changes to json serialization and the json4s
dependency. You might also need to look at changes to the json serialization code in processors
.
I'm looking at the history and testing, but it looks like this isn't the first time the problem has been encountered. @zhengzhongliang has code in one of his branches in which
val json4sV = "3.6.9"
has been changed to
val json4sV = "3.5.1" //Change this to 3.5.1 for annotation on server
Perhaps he can comment on what happened.
@enoriega or others, where might I find a file very much like PMC6600461(.nxml?)?
@kwalcock I'll find a couple files that trigger this and come back with them
I found a file that fails. The best solution IMO is to stick with the json4s that processors uses. Mixing and matching them seems to lead to problems. The change has been made in the PR, #719.
Ok. Same as with issue #718, this error hasn't happened while running branch kwalcock-fixes
, so I think this is safe to close too.
I have experienced the following error repeatedly. This goes unhandled and error crashes
ReachCLI
instead of logging and recovering gracefully.I'm not sure which file is the culprit of triggering it, but the last PMCID shown before crashing is
PMC6600461
.I attach reach's log to this ticket.
json_error.log