Bad Gateway?
Closed this issue · 9 comments
works and returns a generated document, but
... doesn't work and returns a Bad Gateway.
The second is the one that should work since it's using the correct shortName.
It seems that the system doesn't recognize the shortname but it does exist: http://www.w3.org/TR/appmanifest/ .
What's wrong there?
On 19/03/2015 21:17 , Philippe Le Hegaret wrote:
The second is the one that should work since it's using the correct
shortName.
It seems that the system doesn't recognize the shortname but it does
exist: http://www.w3.org/TR/appmanifest/ .What's wrong there?
I can't find the string "appmanifest" appearing anywhere in
http://www.w3.org/2002/01/tr-automation/tr.rdf. That's likely to be the
source of the problem: the spec-generator can't find the previous version.
Robin Berjon - http://berjon.com/ - @robinberjon
@tripu This should fix the problem encountered on Wednesday (well, tr.rdf will need to be fixed as well now)
Thanks, @plehegar. I'll let @darobin or @dontcallmedom merge your fix. We will update the instance of spec-generator in labs.w3.org together with the other tools next time.
The metadata extraction part is @dontcallmedom's code, I defer to him on this. A quick look LGTM.
@tripu once merged, it would be good to deploy it sooner rather than later otherwise we'll keep messing tr.rdf ...
Speaking of deployment, have there been discussions of continuous deployment?
no continuous deployment yet but a 2/3 weeks release cycle. Critical bug fix get deployed sooner.