Bug #4521
closedKNB data error checking is overly aggressive
0%
Description
On r21314, I can no longer access the Kruger data. I believe this is due to some overly aggressive error checking on the data. The data packages (which are not directly under my control) have thrown errors on the console. I think this is due to negative numbers and zeroes in columns that are nominally whole numbers. In the past, there were non-fatal, but this is now major problem.
This change happened somewhere between r21218 and r21310.
The error message is specifically "Unable to parse the MetaData: Error parsing the eml package: Exception in DataTypeResolver"
Updated by Chad Berkley over 14 years ago
I think this is my fault. I'm trying to track it down now.
Updated by Chad Berkley over 14 years ago
This is a problem with some configuration values. I'll get this fixed tomorrow.
Updated by Chad Berkley over 14 years ago
Error in my configuration manager conversion code in DelimiterResolver. Fixed.