ASSIGNED 175854
Platform code should be able to safely log in release builds
https://bugs.webkit.org/show_bug.cgi?id=175854
Summary Platform code should be able to safely log in release builds
Eric Carlson
Reported 2017-08-22 15:22:00 PDT
Release logging should not happen in private browsing mode. Page.usesEphemeralSession() is used to check for private browsing mode, but Page isn't accessible from inside of Platform/. Instead of passing "private browsing mode" state to every Platform object that needs to do release logging, create a Logger class that Page can allocate and configure and which can be used inside of Platform/.
Attachments
Proposed patch. (10.34 KB, patch)
2017-08-22 15:34 PDT, Eric Carlson
no flags
Proposed patch. (10.38 KB, patch)
2017-08-22 15:45 PDT, Eric Carlson
jer.noble: review+
Patch for landing. (10.42 KB, patch)
2017-08-23 10:58 PDT, Eric Carlson
commit-queue: commit-queue-
Patch for landing. (10.42 KB, patch)
2017-08-23 12:20 PDT, Eric Carlson
no flags
Radar WebKit Bug Importer
Comment 1 2017-08-22 15:25:37 PDT
Eric Carlson
Comment 2 2017-08-22 15:34:00 PDT
Created attachment 318812 [details] Proposed patch.
Eric Carlson
Comment 3 2017-08-22 15:45:48 PDT
Created attachment 318814 [details] Proposed patch.
Jer Noble
Comment 4 2017-08-22 16:14:36 PDT
Comment on attachment 318814 [details] Proposed patch. View in context: https://bugs.webkit.org/attachment.cgi?id=318814&action=review r=me with maybe a nit, maybe not a nit. > Source/WebCore/PAL/pal/Logger.h:94 > + bool enabled() const { return m_enabled; } nit: I don't know where we (as a project) come down on "bool enabled()" v. "bool isEnabled()". I could go either way.
Eric Carlson
Comment 5 2017-08-23 10:58:31 PDT
Created attachment 318888 [details] Patch for landing.
Eric Carlson
Comment 6 2017-08-23 11:00:10 PDT
(In reply to Jer Noble from comment #4) > Comment on attachment 318814 [details] > Proposed patch. > > View in context: > https://bugs.webkit.org/attachment.cgi?id=318814&action=review > > r=me with maybe a nit, maybe not a nit. > > > Source/WebCore/PAL/pal/Logger.h:94 > > + bool enabled() const { return m_enabled; } > > nit: I don't know where we (as a project) come down on "bool enabled()" v. > "bool isEnabled()". I could go either way. It looks like we don't have consensus, there are about twice as many "bool enabled()" as "bool isEnabled()".
Build Bot
Comment 7 2017-08-23 11:04:12 PDT
Attachment 318888 [details] did not pass style-queue: ERROR: Source/WebCore/PAL/pal/Logger.h:105: The parameter name "channel" adds no information, so it should be removed. [readability/parameter_name] [5] Total errors found: 1 in 5 files If any of these errors are false positives, please file a bug against check-webkit-style.
WebKit Commit Bot
Comment 8 2017-08-23 11:16:07 PDT
Comment on attachment 318888 [details] Patch for landing. Rejecting attachment 318888 [details] from commit-queue. Failed to run "['/Volumes/Data/EWS/WebKit/Tools/Scripts/webkit-patch', '--status-host=webkit-queues.webkit.org', '--bot-id=webkit-cq-03', 'build', '--no-clean', '--no-update', '--build-style=release', '--port=mac']" exit_code: 2 cwd: /Volumes/Data/EWS/WebKit Last 500 characters of output: bKit/Tools/TestWebKitAPI/Tests/WebCore/cocoa/WebCoreNSURLSession.mm -o /Volumes/Data/EWS/WebKit/WebKitBuild/TestWebKitAPI.build/Release/TestWebKitAPILibrary.build/Objects-normal/x86_64/WebCoreNSURLSession.o ** BUILD FAILED ** The following build commands failed: CompileC /Volumes/Data/EWS/WebKit/WebKitBuild/TestWebKitAPI.build/Release/TestWebKitAPILibrary.build/Objects-normal/x86_64/Logging.o Tests/WebCore/Logging.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (1 failure) Full output: http://webkit-queues.webkit.org/results/4369505
Eric Carlson
Comment 9 2017-08-23 12:20:34 PDT
Created attachment 318899 [details] Patch for landing.
WebKit Commit Bot
Comment 10 2017-08-23 13:02:02 PDT
Comment on attachment 318899 [details] Patch for landing. Clearing flags on attachment: 318899 Committed r221095: <http://trac.webkit.org/changeset/221095>
Note You need to log in before you can comment on or make changes to this bug.