| AppUpdater.sys.mjs |
`AbortablePromise`s automatically add themselves to this set on construction
and remove themselves when they settle.
|
30848 |
- |
| background_task_metrics.yaml |
|
15387 |
- |
| BackgroundTask_backgroundupdate.sys.mjs |
Verify that pre-conditions to update this installation (both persistent and
transient) are fulfilled, and if they are all fulfilled, pump the update
loop.
This means checking for, downloading, and potentially applying updates.
@param {object} Optional parameters
{boolean} checkOnly
If specified as `true`, checks for updates but does not download them
unless a flag from Balrog specifically overrides this behavior.
@returns {any} - Returns AppUpdater status upon update loop exit.
|
24235 |
- |
| BackgroundUpdate.sys.mjs |
-*- js-indent-level: 2; indent-tabs-mode: nil -*- |
43764 |
- |
| common |
|
|
- |
| components.conf |
|
1477 |
- |
| content |
|
|
- |
| docs |
|
|
- |
| jar.mn |
|
611 |
- |
| metrics.yaml |
|
59966 |
- |
| moz.build |
|
1437 |
- |
| nsIUpdateService.idl |
An interface that describes an object representing a patch file that can
be downloaded and applied to a version of this application so that it
can be updated.
|
39822 |
- |
| nsUpdateService.manifest |
|
143 |
- |
| pings.yaml |
|
1591 |
- |
| shared_metrics.yaml |
|
5367 |
- |
| shared_pings.yaml |
|
2779 |
- |
| tests |
|
|
- |
| UpdateListener.sys.mjs |
|
18223 |
- |
| UpdateLog.sys.mjs |
Update logging lives in its own module for several reasons. First, it avoids
having some very similar logging code duplicated in several places. And
second, we only want to open the update messages file once. Opening it
multiple times from multiple files does not result in all those messages
ending up in the same log file.
Note that simply importing this module can cause the value of the
`app.update.log.file` pref to change. This may seem a bit weird, but we are
going to consider it to be acceptable because any other module that wants to
interact with that pref really ought to be doing it by interacting with this
module instead, making the pref more of an internal implementation detail.
This option was chosen over doing this work more lazily (say, on a log
message) because this initialization step has user-visible consequences
(the log file moves) and we'd prefer that those happen close to startup so
that the user doesn't observe it happening at a seemingly random time.
|
6680 |
- |
| updater |
|
|
- |
| UpdateService.sys.mjs |
|
254921 |
- |
| UpdateServiceStub.sys.mjs |
-*- indent-tabs-mode: nil; js-indent-level: 2 -*- |
16172 |
- |
| UpdateTelemetry.sys.mjs |
Values for the Glean.update.checkCodeNotify and
Glean.update.checkCodeExternal custom_distribution metrics.
|
21280 |
- |