-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOMHighResTimeStamp link missing now #1646
Comments
It looks like DOMHighResTimeStamp is linking again? Must have been an intermittent data error, since I also see it in the database. The argumentdef failures are indeed new, and debugging is turning out to be interesting. More updates as I figure this out. |
Pretty sure it's a bug in my webidl parser, plinss/widlparser#56 is tracking it. |
Updated bikeshed this morning. Still get this error:
Could be that I didn't update correctly or I'm running the wrong version. (Had some troubles installing the new version but pip install is working fine.) Thanks for looking in to this. |
Tried bikeshed again today. It looks much better and most of the issues are gone. Except I'm now getting
I think this make all the links to bibliographic data broken. |
????? A "500 internal server error"? That sounds like something has corrupted the file? |
Here's the log from running
and many more lines about not finding stuff in the biblio data. |
|
Specifically the error is:
... with tons of spewed data following |
All right, while this is fixed in the live data, there was a period of time where the manifest was being generated wrong and put its entire contents on one line accidentally. Looks like my code wasn't robust to the possiblity of the manifest being totally borked, so if you happened to grab the data while it was wrong, it's just straight failing. And I guess the data is wrong in the current version uploaded to PyPi. ^_^ I've fixed it locally; as soon as this update finishes, I'll push the fixed version to PyPi and you can update things. ( |
And done. Once you upgrade, you should be at version 1.1.0 (check it with |
Thanks @tabatkins! This looks great and the number of errors in the WebAudio spec has been reduced. However, |
Then you're not on the latest version, since I just added it as part of the 1.1.0 release. ^_^ |
My copy (via |
...weird, https://github.com/tabatkins/bikeshed/blob/master/MANIFEST.in specifies that it should include that file. |
The WebAudio spec references
DomHighResTimeStamp
inSection 1.2.5. AudioTimeStamp. This used to link to https://www.w3.org/TR/hr-time-2/#dom-domhighrestimestamp, but after updating bikeshed, this no longer works.
There are also lots of new additional errors when building the WebAudio spec. For example, we get
This error didn't use to occur. The former is a bug in bikeshed. The latter could very well be a bug in the WebAudio spec which is now incorrect because bikeshed tightened up something.
The text was updated successfully, but these errors were encountered: