MobilityData / gbfs-validator

The canonical GBFS validator. Maintained by the GBFS community, facilitated by MobilityData.
https://gbfs-validator.mobilitydata.org/
Apache License 2.0
18 stars 12 forks source link

Response code 500 on the LINK Knoxville feed #130

Closed richfab closed 1 year ago

richfab commented 1 year ago

What is the issue and why is it an issue?

When using the validator on a random feed (LINK Knoxville from systems.csv#L686), I realized that it returns "Sorry, this version is not yet implemented or not detectable !". However, the filegbfs.json is conform to v2.2 when testing it against the JSON Schema.

It could be a problem for other feeds too.

gbfs.json Output
image image

Please describe some potential solutions you have considered (even if they aren’t related to GBFS).

I don't have a solution but I did some debugging, if it helps.

The checkAutodiscovery() method in gbfs.js catches this error:

HTTPError: Response code 500 (Internal Server Error)
    at Request.<anonymous> (/Users/fabien/GitHub/MobilityData/gbfs-validator/gbfs-validator/node_modules/got/dist/source/as-promise/index.js:118:42)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {name: 'HTTPError', code: 'ERR_NON_2XX_3XX_RESPONSE', timings: {…}, stack: 'HTTPError: Response code 500 (Internal Server…ions (node:internal/process/task_queues:95:5)', message: 'Response code 500 (Internal Server Error)', …}

But the feed loads correctly in the browser 🤔

richfab commented 1 year ago

Duplicate of https://github.com/MobilityData/gbfs-validator/issues/90