-
Notifications
You must be signed in to change notification settings - Fork 3
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
Specify summarization, destruction, and options #18
Conversation
This is most of the remaining normative text for the summarizer API.
<th>{{DOMException}} [=DOMException/name=] | ||
<th>Scenarios | ||
<tbody> | ||
<tr> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Chromium is currently reporting InvalidStateError if the backend session is destroyed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can the backend session be destroyed? Is it via the destroy() method or the AbortSignal? Then it should be an AbortError. Or is there some other possibility?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is caused by the backend aborting itself. Maybe we'd like to have another error type for backend failures or simply use UnknownError
instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know why the backend would abort itself? Like, how would I trigger that as a user or developer?
But yes, I think UnknownError might be best for such cases.
This is most of the remaining normative text for the summarizer API.
Preview | Diff