Project

General

Profile

Bug #4521

KNB data error checking is overly aggressive

Added by Oliver Soong about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
data access
Target version:
Start date:
11/03/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4521

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"

History

#1 Updated by Chad Berkley about 10 years ago

I think this is my fault. I'm trying to track it down now.

#2 Updated by Chad Berkley about 10 years ago

This is a problem with some configuration values. I'll get this fixed tomorrow.

#3 Updated by Chad Berkley about 10 years ago

Error in my configuration manager conversion code in DelimiterResolver. Fixed.

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 4521

Also available in: Atom PDF