RESOLVED FIXED 175723
[Beacon] Improve error reporting
https://bugs.webkit.org/show_bug.cgi?id=175723
Summary [Beacon] Improve error reporting
Chris Dumez
Reported 2017-08-18 10:18:07 PDT
Improve error reporting for beacon loads. Right now we only report synchronous errors, not asynchronous ones.
Attachments
WIP Patch (29.14 KB, patch)
2017-08-18 13:32 PDT, Chris Dumez
no flags
Patch (39.17 KB, patch)
2017-08-18 14:07 PDT, Chris Dumez
no flags
Patch (39.18 KB, patch)
2017-08-18 14:24 PDT, Chris Dumez
no flags
Patch (40.09 KB, patch)
2017-08-18 15:08 PDT, Chris Dumez
no flags
Patch (40.00 KB, patch)
2017-08-18 16:42 PDT, Chris Dumez
no flags
Chris Dumez
Comment 1 2017-08-18 13:32:16 PDT
Created attachment 318535 [details] WIP Patch
Chris Dumez
Comment 2 2017-08-18 14:07:09 PDT
Radar WebKit Bug Importer
Comment 3 2017-08-18 14:07:45 PDT
Chris Dumez
Comment 4 2017-08-18 14:24:51 PDT
Chris Dumez
Comment 5 2017-08-18 15:08:12 PDT
Darin Adler
Comment 6 2017-08-18 15:40:07 PDT
Comment on attachment 318549 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=318549&action=review > Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:49 > + auto inflightBeacons = WTFMove(m_inflightBeacons); > + for (auto& beacon : inflightBeacons) > + beacon->removeClient(*this); Is there really some risk of reentry here? If not, it seems unnecessary to move m_inflightBeacons into a local variable. > Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:54 > + NavigatorBeacon* supplement = static_cast<NavigatorBeacon*>(Supplement<Navigator>::from(navigator, supplementName())); Please consider auto* here. > Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:74 > + bool wasRemoved = m_inflightBeacons.removeFirst(&resource); If the operations we need are append and removeFirst, then normally we would want to use a Deque, not a Vector. > Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:92 > + String description = error.localizedDescription(); Strange to use a "localized" description and then append hard-coded English text to it. > Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:95 > + messageMiddle = ASCIILiteral(" due to access control checks."); Why does this even compile? We are assigning to a const char*. Or we can have the local variable be of type ASCIILiteral, which I think would be better. > Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:100 > + document->addConsoleMessage(MessageSource::Network, MessageLevel::Error, makeString("Beacon API cannot load ", error.failingURL().string(), messageMiddle, description)); We could do ASCIILiteral(messageMiddle) here. > Source/WebCore/Modules/beacon/NavigatorBeacon.h:51 > + static NavigatorBeacon* from(Navigator*); Can this take a reference instead of a pointer? > Source/WebCore/Modules/beacon/NavigatorBeacon.h:56 > + // CachedRawResourceClient > + void notifyFinished(CachedResource&) final; > + void logError(const ResourceError&); Seems unnecessary to comment which class we are overriding here. But especially strange to label this paragraph with the class name, but only one of the two functions here is an override. > Source/WebCore/platform/network/PingHandle.h:48 > + , m_timeoutTimer(*this, &PingHandle::timeoutTimerFired) Consider using the lambda form of Timer instead of this one? I think we should use it in all new code, and only use the pointer-to-member-function one in legacy code.
Chris Dumez
Comment 7 2017-08-18 16:04:09 PDT
Comment on attachment 318549 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=318549&action=review >> Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:49 >> + beacon->removeClient(*this); > > Is there really some risk of reentry here? If not, it seems unnecessary to move m_inflightBeacons into a local variable. I don't think this is an issue currently. I'll get rid of the local. >> Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:54 >> + NavigatorBeacon* supplement = static_cast<NavigatorBeacon*>(Supplement<Navigator>::from(navigator, supplementName())); > > Please consider auto* here. Ok. >> Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:74 >> + bool wasRemoved = m_inflightBeacons.removeFirst(&resource); > > If the operations we need are append and removeFirst, then normally we would want to use a Deque, not a Vector. I think you may be confused by what removeFirst() does here. It removes the first match in the vector, not the first item in the vector. >> Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:95 >> + messageMiddle = ASCIILiteral(" due to access control checks."); > > Why does this even compile? We are assigning to a const char*. Or we can have the local variable be of type ASCIILiteral, which I think would be better. Oops. I guess it works because of the "operator const char*() { return m_characters; }" operator on ASCIILiteral. Will fix. >> Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:100 >> + document->addConsoleMessage(MessageSource::Network, MessageLevel::Error, makeString("Beacon API cannot load ", error.failingURL().string(), messageMiddle, description)); > > We could do ASCIILiteral(messageMiddle) here. Ok. >> Source/WebCore/Modules/beacon/NavigatorBeacon.h:51 >> + static NavigatorBeacon* from(Navigator*); > > Can this take a reference instead of a pointer? Ok. >> Source/WebCore/Modules/beacon/NavigatorBeacon.h:56 >> + void logError(const ResourceError&); > > Seems unnecessary to comment which class we are overriding here. But especially strange to label this paragraph with the class name, but only one of the two functions here is an override. Ok. >> Source/WebCore/platform/network/PingHandle.h:48 >> + , m_timeoutTimer(*this, &PingHandle::timeoutTimerFired) > > Consider using the lambda form of Timer instead of this one? I think we should use it in all new code, and only use the pointer-to-member-function one in legacy code. This is not new code but I can take a look. Do you mean that we now prefer to inline the body of the timeoutTimerFired() method inside the init list?
Chris Dumez
Comment 8 2017-08-18 16:07:35 PDT
Comment on attachment 318549 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=318549&action=review >>> Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:74 >>> + bool wasRemoved = m_inflightBeacons.removeFirst(&resource); >> >> If the operations we need are append and removeFirst, then normally we would want to use a Deque, not a Vector. > > I think you may be confused by what removeFirst() does here. It removes the first match in the vector, not the first item in the vector. Technically, this could be a HashSet. It seemed a little overkill at first but I guess a page could send a lot of beacons. Please let me know if you'd prefer a HashSet.
Chris Dumez
Comment 9 2017-08-18 16:42:01 PDT
Chris Dumez
Comment 10 2017-08-18 16:43:09 PDT
(In reply to Chris Dumez from comment #8) > Comment on attachment 318549 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=318549&action=review > > >>> Source/WebCore/Modules/beacon/NavigatorBeacon.cpp:74 > >>> + bool wasRemoved = m_inflightBeacons.removeFirst(&resource); > >> > >> If the operations we need are append and removeFirst, then normally we would want to use a Deque, not a Vector. > > > > I think you may be confused by what removeFirst() does here. It removes the first match in the vector, not the first item in the vector. > > Technically, this could be a HashSet. It seemed a little overkill at first > but I guess a page could send a lot of beacons. Please let me know if you'd > prefer a HashSet. It seems we don't currently have the right traits to have a HashSet of CachedResourceHandles.
WebKit Commit Bot
Comment 11 2017-08-18 17:28:02 PDT
Comment on attachment 318556 [details] Patch Clearing flags on attachment: 318556 Committed r220946: <http://trac.webkit.org/changeset/220946>
WebKit Commit Bot
Comment 12 2017-08-18 17:28:04 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.