echidna Failure messages could be improved

Tried to publish, but I initially got failure:The error I got back from submitting is:

    {
      "time": "2015-03-17T18:10:45.112Z",
      "fact": "You are not authorized to publish"
    },

Would be good if the service would tell you what you need to do to get authorization? @plehegar fixed it for me, but not sure what he did to get it to work.

Mar 17 '15 18:03 marcoscaceres

@marcoscaceres, yes, I intend to provide better error report. That's the cost of an early release version :-) I leave this open until you feel feedback is up to your expectations.

Mar 18 '15 01:03 astorije

Thanks @astorije! Happy to review messages, etc. Here is another example from today where it's not clear how to proceed: https://lists.w3.org/Archives/Public/public-tr-notifications/2015Mar/0011.html

Mar 18 '15 17:03 marcoscaceres

@marcoscaceres, I agree it must seem very cryptic indeed.

In this case, one of our dependencies (the spec generator has crashed, ouch...

Mar 18 '15 20:03 astorije

Yeah, it might be useful to have a way to also check Echidna's status... I've been periodically sending publication requests through out the day hoping that it would start working again. You can see all my fails:

https://lists.w3.org/Archives/Public/public-tr-notifications/2015Mar/

Mar 18 '15 22:03 marcoscaceres

Got another strange one: latest-is-not-previous

https://lists.w3.org/Archives/Public/public-tr-notifications/2015May/0011.html

May 13 '15 21:05 marcoscaceres

@marcoscaceres: yes, definitely it's bad UI now… We shall make it more legible very soon. Thank you for keeping track here.

In the meantime, when you see error keys specifically from Specberus, like this one, you can run your doc through Specberus to (sometimes) get a better error message. (In fact, for now I suggest that you always do that manually until Specberus returns zero errors, before submitting to Echidna.) In this case, I see one error, but a different one, in Specberus right now… (The key latest-is-not-previous in Specberus would return the message “retrieved ‘previous’ and ‘latest’ documents, but their contents don't match”.)

May 14 '15 06:05 tripu