- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 2 Sep 2016 16:24:16 -0700
- To: "Hodges, Jeff" <jeff.hodges@paypal.com>
- Cc: "spec-prod@w3.org" <spec-prod@w3.org>
On Wed, Aug 17, 2016 at 5:10 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Wed, Aug 17, 2016 at 3:49 PM, Hodges, Jeff <jeff.hodges@paypal.com> wrote: >> somewhat all of a sudden, the cloud-hosted bikeshed claims: Unknown >> Status 'ED' used >> >> here's the details.. >> >>> curl https://api.csswg.org/bikeshed/ -F file=@index.bs -F force=1 -F >>>output=err > errors.txt ; ls -l errors* >> % Total % Received % Xferd Average Speed Time Time Time >> Current >> Dload Upload Total Spent Left >> Speed >> 100 116k 0 162 100 116k 222 160k --:--:-- --:--:-- --:--:-- >> 160k >> -rw-r--r-- 1 jehodges 110028724 162 Aug 17 15:22 errors.txt >> >> >>> cat errors.txt >> Error running preprocessor, returned code: 1. >> \033[1;31mFATAL ERROR:\033[0m Unknown Status 'ED' used. >> \033[7;31m ✘ \033[0m Did not generate, due to fatal errors >> >> The metadata section in this index.bs begins with.. >> >> <pre class='metadata'> >> Title: Web Authentication: An API for accessing Scoped Credentials >> Status: ED >> TR: http://www.w3.org/TR/webauthn/ >> ED: http://w3c.github.io/webauthn/ >> Shortname: webauthn >> ... >> </pre> >> >> >> >> This is a bug, yes? > > Kinda sorta, but mostly WAI. I've begun namespacing the statuses > based on "supergroup" - W3C groups have access to the W3C document > statuses, ISO groups have access to the ISO statuses, etc. This > avoids collisions between independent groups. > > Unfortunately, I haven't yet added a good way to let Bikeshed know > that you're a W3C group, besides me adding your group to the list > manually. Happy to do so - what's your Group? All of this is thoroughly fixed now! First, Bikeshed emits a useful error message actually telling you what's wrong, and suggests a fix. Second, it now allows you to tell it that you're a W3C group, even if your group isn't on Bikeshed's list yet. Third, the docs now list all the statuses (didn't realize you were allowed to use <details> in GitHub Markdown; that's what I was waiting for). ~TJ
Received on Friday, 2 September 2016 23:25:04 UTC