As part of #1837, there are 13 feeds that appeared in the acceptance test report as corrupted. This can happen when a validation report is not generated due to multiple causes. One of the causes is a runtime exception triggered by the validator. After conducting further investigation, I tested the feed mdb-392 against production web deployment and staging.
In case of production, the report was generated with few visible empty spaces in the feed information section, report.
In case of staging, the report was not generated and an error was visible in the logs:
java.lang.NullPointerException: Cannot invoke "org.mobilitydata.gtfsvalidator.table.GtfsFeedInfo.feedStartDate()" because "info" is null
Steps/Code to Reproduce
Execute the GTFS validator against the 13 feeds listed as corrupted
Corrupted marked feeds:
Describe the bug
As part of #1837, there are 13 feeds that appeared in the acceptance test report as
corrupted
. This can happen when a validation report is not generated due to multiple causes. One of the causes is a runtime exception triggered by the validator. After conducting further investigation, I tested the feed mdb-392 against production web deployment and staging.Steps/Code to Reproduce
Execute the GTFS validator against the 13 feeds listed as corrupted Corrupted marked feeds:
Expected Results
All reports are generated and the extraction of the feed information should not block the generation of the HTML and JSON reports.
Actual Results
Validation reports are not generated due to feed information logic.
Screenshots
Files used
No response
Validator version
5.0.1
Operating system
Web
Java version
No response
Additional notes
No response