eec946b5936068af4034b536735710e6f15d2e2a: Bug 1412090 - patch 3 - Check the sandbox policy to verify font files will be readable by the content process before including them in the system font list. r=gps
Jonathan Kew <jkew@mozilla.com> - Thu, 09 Nov 2017 16:54:30 +0000 - rev 695873
Push 88577 by mozilla@noorenberghe.ca at Thu, 09 Nov 2017 23:43:51 +0000
Bug 1412090 - patch 3 - Check the sandbox policy to verify font files will be readable by the content process before including them in the system font list. r=gps
72a6f5f3512c49acc3e3735dbadd1007f9ddc54c: Bug 1412090 - patch 2 - Rework the fontconfig-based platform font list implementation to pass the list of available font patterns from chrome to content, instead of letting the content process get it directly from fontconfig. r=lsalzman
Jonathan Kew <jkew@mozilla.com> - Thu, 02 Nov 2017 20:29:33 +0000 - rev 695872
Push 88577 by mozilla@noorenberghe.ca at Thu, 09 Nov 2017 23:43:51 +0000
Bug 1412090 - patch 2 - Rework the fontconfig-based platform font list implementation to pass the list of available font patterns from chrome to content, instead of letting the content process get it directly from fontconfig. r=lsalzman
ea8ee40ed426ff032fb9ba0345cc45bf6097bd23: Bug 1412090 - patch 1 - Wrap the font family record used to pass font info from chrome to content on macOS in a union, in preparation for using the same mechanism with a different type of font record on Linux. (No functional change here, just the added union type and some renamings from 'font family list' to 'font list' to be more generic.) r=lsalzman
Jonathan Kew <jkew@mozilla.com> - Thu, 02 Nov 2017 17:23:16 +0000 - rev 695871
Push 88577 by mozilla@noorenberghe.ca at Thu, 09 Nov 2017 23:43:51 +0000
Bug 1412090 - patch 1 - Wrap the font family record used to pass font info from chrome to content on macOS in a union, in preparation for using the same mechanism with a different type of font record on Linux. (No functional change here, just the added union type and some renamings from 'font family list' to 'font list' to be more generic.) r=lsalzman
a48c10a1e0644ae267d26c9d5d4a7c358852ed13: Bug 1415880 - Remove the obsolete mIsValid flag from gfxFontEntry, as nothing depends on it any more. r=jrmuizel
Jonathan Kew <jkew@mozilla.com> - Thu, 09 Nov 2017 16:54:02 +0000 - rev 695870
Push 88577 by mozilla@noorenberghe.ca at Thu, 09 Nov 2017 23:43:51 +0000
Bug 1415880 - Remove the obsolete mIsValid flag from gfxFontEntry, as nothing depends on it any more. r=jrmuizel
4fe9a9993e1b70550410cd6b79729535160bebe5: bug 1368868 - give up on ocsp stapling strictness because we can't have nice things r?jcj draft
David Keeler <dkeeler@mozilla.com> - Wed, 08 Nov 2017 15:50:26 -0800 - rev 695869
Push 88576 by bmo:dkeeler@mozilla.com at Thu, 09 Nov 2017 23:30:52 +0000
bug 1368868 - give up on ocsp stapling strictness because we can't have nice things r?jcj MozReview-Commit-ID: nbX0c251oC
a817458ef58c10b3f32872cfd75601859630913e: Bug 1415747 - Remove nsIDOMHTMLScriptElement draft
Kyle Machulis <kyle@nonpolynomial.com> - Wed, 08 Nov 2017 19:02:14 -0800 - rev 695868
Push 88575 by bmo:kyle@nonpolynomial.com at Thu, 09 Nov 2017 23:28:09 +0000
Bug 1415747 - Remove nsIDOMHTMLScriptElement MozReview-Commit-ID: 3I7qVTsKFJC
20faca1cbc25bef14313322bcecad14e73ecd4e8: Bug 1415747 - Remove nsIDOMHTMLScriptElement draft
Kyle Machulis <kyle@nonpolynomial.com> - Wed, 08 Nov 2017 19:02:14 -0800 - rev 695867
Push 88574 by bmo:kyle@nonpolynomial.com at Thu, 09 Nov 2017 23:25:39 +0000
Bug 1415747 - Remove nsIDOMHTMLScriptElement MozReview-Commit-ID: 3I7qVTsKFJC
72a6a4bce04adc7bead1215593ccbcb59f20ec03: Bug 1415747 - Remove nsIDOMHTMLScriptElement draft
Kyle Machulis <kyle@nonpolynomial.com> - Wed, 08 Nov 2017 19:02:14 -0800 - rev 695866
Push 88573 by bmo:kyle@nonpolynomial.com at Thu, 09 Nov 2017 23:20:48 +0000
Bug 1415747 - Remove nsIDOMHTMLScriptElement MozReview-Commit-ID: 3I7qVTsKFJC
3527e326e2ec7995cdefc9f7fd6ac1cab317de59: Add the add-on name and icon in in a very not wonderful fashion draft
Mark Striemer <mstriemer@mozilla.com> - Thu, 09 Nov 2017 17:18:36 -0600 - rev 695865
Push 88572 by bmo:mstriemer@mozilla.com at Thu, 09 Nov 2017 23:18:59 +0000
Add the add-on name and icon in in a very not wonderful fashion MozReview-Commit-ID: 53ojMfuTbmZ
67d23593752babf9a4063ef5b5c45b93c24a1890: Bug 1411646 prevent oauth redirect requests from happening, r?rpl draft
Shane Caraveo <scaraveo@mozilla.com> - Thu, 09 Nov 2017 15:11:13 -0800 - rev 695864
Push 88571 by mixedpuppy@gmail.com at Thu, 09 Nov 2017 23:12:51 +0000
Bug 1411646 prevent oauth redirect requests from happening, r?rpl MozReview-Commit-ID: L8ekyXDeCbp
2c3ee273d2491ad8e895ea1ef12b46158449283c: Bug 1415614 - Move configure invocation out of mach_commands.py; r=nalexander draft
Gregory Szorc <gps@mozilla.com> - Thu, 09 Nov 2017 12:19:16 -0800 - rev 695863
Push 88570 by bmo:gps@mozilla.com at Thu, 09 Nov 2017 23:11:44 +0000
Bug 1415614 - Move configure invocation out of mach_commands.py; r=nalexander While we're here, also move the low-level code to invoke configure to a proper Python module. MozReview-Commit-ID: 4rlCxOwcVu1
ecf6c5a2a561cad81fc5a61704a711c14e27306b: Bug 1415614 - Move code for invoking build system out of mach_commands.py; r=nalexander draft
Gregory Szorc <gps@mozilla.com> - Wed, 08 Nov 2017 15:52:17 -0800 - rev 695862
Push 88570 by bmo:gps@mozilla.com at Thu, 09 Nov 2017 23:11:44 +0000
Bug 1415614 - Move code for invoking build system out of mach_commands.py; r=nalexander The goal is to move this lower-level code somewhere where it can be reused. The only meaningful code change as part of the move was handling of the mach context. Before, we could access self._mach_context. After, we need to pass it as an argument. This also uncovered a bug where "telemetry_handler" could be None but we called it unconditionally. We now guard this call with an "if." MozReview-Commit-ID: FWw4l6H1ayS
ac1ce7a17b7be9027b05901c7d4fa79c0cfa3674: Bug 1415614 - Move build output processing code out of mach_commands.py; r=nalexander draft
Gregory Szorc <gps@mozilla.com> - Wed, 08 Nov 2017 14:45:07 -0800 - rev 695861
Push 88570 by bmo:gps@mozilla.com at Thu, 09 Nov 2017 23:11:44 +0000
Bug 1415614 - Move build output processing code out of mach_commands.py; r=nalexander In general, we shouldn't have so much business logic in mach_commands.py files. I'd like to move more of the low-level "perform a build" logic out of mach_commands.py to facilitate some future work. That code makes use of this output processing code. So as the first step in moving the build code, we move its dependencies. As part of this, I also cleaned up some random unused imports around lines that were touched. No meaningful code changes were performed as part of the code move. MozReview-Commit-ID: 96mGWUJ7oLb
f50dbbe024e50dfc2d3ea4a46c328ef753e6bab6: Bug 1415614 - Add an API to log all structured messages; r?build draft
Gregory Szorc <gps@mozilla.com> - Thu, 09 Nov 2017 15:09:52 -0800 - rev 695860
Push 88570 by bmo:gps@mozilla.com at Thu, 09 Nov 2017 23:11:44 +0000
Bug 1415614 - Add an API to log all structured messages; r?build Currently, marking a logger as a structured logger will require a subsequent function call in order for the logger to be hooked up to active handlers. This behavior is not intuitive and makes it easy to not have handlers for newly-registered loggers. This means messages may not be logged anywhere. In addition, we have to manually specify which named loggers to enable structured logging for. This can be annoying. We change the behavior of register_structured_logger() to automatically add existing terminal and json handlers to the logger being marked as structured. We also introduce an API to enable structured logging for all loggers. Existing consumers of registered_structured_logger() in mozbuild have been updated to use this API. A new consumer has been added for the `mach configure` command because it should have been there before. We stop short of making enable_all_structured_loggers() the default. This is because various commands interact with the log manager in ways that will result in duplicate logging of messages and dropping of structured messages. There is a bit of a rabbit hole here and addressing it can be done as a follow-up. MozReview-Commit-ID: 1aU6eJvTSMP
1ca1aadf88fd5e88b0e9951582d1559e7b73fce5: Bug 1416029: Pass empty TRY_COMMIT_MESSAGE to mozharness on windows. draft
Tom Prince <mozilla@hocat.ca> - Tue, 24 Oct 2017 15:12:36 -0600 - rev 695859
Push 88569 by bmo:mozilla@hocat.ca at Thu, 09 Nov 2017 23:07:31 +0000
Bug 1416029: Pass empty TRY_COMMIT_MESSAGE to mozharness on windows. Apparently the window's generic-worker uses batch files for running setting environment variables. In windows batch files, setting an environment variable to empty actually unsets. So, in order to avoid mozharness trying to determine the commit message itself, pass an empty TRY_COMMIT_MESSAGE as a space instead. MozReview-Commit-ID: 2nJfJE0EaF0
6dafd7a79e36882afb3bb6b9e1a44159b3f6b1d4: Bug 1416034 - Refuse to run client.mk unless using mach; r?ted draft
Gregory Szorc <gps@mozilla.com> - Thu, 09 Nov 2017 15:03:57 -0800 - rev 695858
Push 88568 by bmo:gps@mozilla.com at Thu, 09 Nov 2017 23:05:47 +0000
Bug 1416034 - Refuse to run client.mk unless using mach; r?ted We will soon begin the process of moving logic from client.mk into mach. Once we start this process, it won't be possible to invoke client.mk in isolation. This commit introduces a check in client.mk that will error unless client.mk is executed from mach. This should help more easily identify users of client.mk during the transition period - before client.mk is removed and callers start getting missing file errors. Obviously the check can be bypassed easily. If someone does this, upcoming changes will quickly break that workflow. So this isn't a big deal. MozReview-Commit-ID: JB7hXlvTKWe
341a29e79d2e43967d70b25f3164248668532cde: Bug 1416020 - Remove echo-variable-% target from client.mk; r?build draft
Gregory Szorc <gps@mozilla.com> - Thu, 09 Nov 2017 14:26:55 -0800 - rev 695857
Push 88568 by bmo:gps@mozilla.com at Thu, 09 Nov 2017 23:05:47 +0000
Bug 1416020 - Remove echo-variable-% target from client.mk; r?build AFAICT this is unused. There are some mozharness consumers that evaluate an echo-variable-* target. However, I believe they are hitting the target from debugmake.mk and not going through client.mk. MozReview-Commit-ID: 9XjykFMRpsT
39194dda0c3ca860e76119588c5e31efae0e6dd5: Bug 1416020 - Remove unused variables from client.mk; r?build draft
Gregory Szorc <gps@mozilla.com> - Thu, 09 Nov 2017 14:19:41 -0800 - rev 695856
Push 88568 by bmo:gps@mozilla.com at Thu, 09 Nov 2017 23:05:47 +0000
Bug 1416020 - Remove unused variables from client.mk; r?build The last use of PERL was removed recently. The last use of comma was removed by c8276e89a513 in 2008. The last use of SH was... never AFAICT. The variable was defined but unused in the initial import of client.mk from CVS in 1998. MozReview-Commit-ID: LFqcVRf36wf
eec433485cdf3e732300a52705f2d49c7fc6709a: Bug 1416029: Pass empty TRY_COMMIT_MESSAGE to mozharness on windows. draft
Tom Prince <mozilla@hocat.ca> - Tue, 24 Oct 2017 15:12:36 -0600 - rev 695855
Push 88567 by bmo:mozilla@hocat.ca at Thu, 09 Nov 2017 23:03:25 +0000
Bug 1416029: Pass empty TRY_COMMIT_MESSAGE to mozharness on windows. Apparently the window's generic-worker uses batch files for running setting environment variables. In windows batch files, setting an environment variable to empty actually unsets. So, in order to avoid mozharness trying to determine the commit message itself, pass an empty TRY_COMMIT_MESSAGE as a space instead. MozReview-Commit-ID: 2nJfJE0EaF0
0ee10fac1c16f6fae14d265a0458c58e59b6c660: Bug 1410737: Log repositories checked out. draft
Tom Prince <mozilla@hocat.ca> - Thu, 26 Oct 2017 11:54:55 -0600 - rev 695854
Push 88567 by bmo:mozilla@hocat.ca at Thu, 09 Nov 2017 23:03:25 +0000
Bug 1410737: Log repositories checked out. MozReview-Commit-ID: 7D7i8CMXjMY
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip