Saving blob is not user friendly: ends up in random location, file has random name. We should wait for FileSaver API to land and use it. Until then, I am suggesting to copy to clipboard instead.
Created attachment 80490 [details] Patch
Committed r77128: <http://trac.webkit.org/changeset/77128>
One of the commit-queue nodes seems to be hung in a loop trying to land this. Trying to figure out why now.
http://queues.webkit.org/queue-status/commit-queue/bots/eseidel-cq-sf was the bot which got stuck for the record. Retry webkitpy.common.net.statusserver: [INFO] Releasing work item 80490 from commit-queue Unable to process work item. Fetching: https://bugs.webkit.org/attachment.cgi?id=80490&action=edit Fetching: https://bugs.webkit.org/show_bug.cgi?id=53328&ctype=xml Processing patch Adding [] to the CC list for bug 53328 Fetching: https://bugs.webkit.org/attachment.cgi?id=80490&action=edit Fetching: https://bugs.webkit.org/show_bug.cgi?id=53328&ctype=xml Retry webkitpy.common.net.statusserver: [INFO] Releasing work item 80490 from commit-queue Unable to process work item. Fetching: https://bugs.webkit.org/attachment.cgi?id=80490&action=edit Fetching: https://bugs.webkit.org/show_bug.cgi?id=53328&ctype=xml Processing patch Adding [] to the CC list for bug 53328 Fetching: https://bugs.webkit.org/attachment.cgi?id=80490&action=edit Fetching: https://bugs.webkit.org/show_bug.cgi?id=53328&ctype=xml Retry webkitpy.common.net.statusserver: [INFO] Releasing work item 80490 from commit-queue Unable to process work item. Was the retry loop. Investigating.
Yeah, the commit-queue seems to have no way of clearing out patches from its queue. Interesting. We have other scripts for this, but they're not currently run automatically.
Running webkit-patch clean-pending-commit manually to clean out this (and possibly other) patches which got stuck in the queue.
Actually, the feeder queue should be removing this automatically once it's closed. I suspect the feeder queue may be down. The style-queue went down 12 hours ago. :(
Yes, the feeder queue must have been down. I started one locally and this bug was (correctly) removed from the queue.