-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Error codes #201
Comments
This is a great idea. We'll be sure to add this to the design for v2.0. |
This error type will be used for all internal errors, and will rely on numeric error codes which can be easily checked by the application. This also changes PSSH parsing to throw on errors instead of retaining partial data. Issue #201 b/25306826 Change-Id: I19d23d99d4ee72cb31fe5f233bac57a3a9cfc283
Finished in 6231488. All reported errors in v2.0 are shaka.util.Error type. They have a category (network, media, drm, etc.) and a specific error code, both of which are numerical and fully-documented. |
This great. The hard work is much appreciated. |
Now that I'm looking at this more closely I do have a quick question. You mention a DRM category in your comment but there isn't a DRM category in the |
The new DrmEngine is still a work-in-progress and hang been published yet. But we will have a DRM error category and specific codes for various errors. There are not standard error codes for CDMs in the EME spec, but we will try to divine as much as we can when we can. For the rest, we will include error strings from the CDM. Hopefully, we can get the important stuff. What situations are important to you? |
Okay, great. The lack of standard error codes is something we have been trying to determine how to handle. We are interested in stuff like:
But I'm not even sure if these are all possible to recognize or if error messages are the best we will get. Do you have an idea about what the cross browser support will be for these? Is it possible to determine these things consistently across browsers? |
|
Yeah, basically, you get something back from the license server but it's rejected by the CDM. |
That should be trivial and cross-platform. The Promise returned by update() would be rejected in that case. |
Can we add error codes to the major Shaka errors so that they are easy to map? We are in a position where we want to funnel Shaka errors through our own application error pipeline so that we can have a consistent error interface. But it's difficult to map to our own error codes because the errors only contain messages which might change.
The text was updated successfully, but these errors were encountered: