You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MobilityData Validation Result can run into CSV parsing issues when validating the MBTA's GTFS feed. Running the same feed with the MobilityData Validator locally does not produce the same result.
Expected behavior
Validator should not produce the parsing issue.
Steps to reproduce the problem
Validate MBTA's latest GTFS feed. Observe the following errors:
Any special notes on configuration used
None
Version of datatools-server and datatools-ui if applicable (exact commit hash or branch name)
Latest validator branch, dev server.
The text was updated successfully, but these errors were encountered:
I think we can probably get around this by increasing the timeout between report generation time and report collection time but should we maybe consider making the time dynamic based on file size? What do you think @philip-cline
I think we should make it dynamic based on file size personally. Wouldn't want to wait the time it takes to validate MBTA for the results to come back for a tiny feed like Golden Gate
Observed behavior
MobilityData Validation Result can run into CSV parsing issues when validating the MBTA's GTFS feed. Running the same feed with the MobilityData Validator locally does not produce the same result.
Expected behavior
Validator should not produce the parsing issue.
Steps to reproduce the problem
Validate MBTA's latest GTFS feed. Observe the following errors:
Any special notes on configuration used
None
Version of datatools-server and datatools-ui if applicable (exact commit hash or branch name)
Latest validator branch, dev server.
The text was updated successfully, but these errors were encountered: