It's been clear from user feedback that people don't realize that `mach
mercurial-setup` doesn't make any changes unless they tell it to.
Reinforce this message in the prompts printed by mach_boostrap.py.
~/.hgrc files are likely created with the user's default umask, which
commonly gives default permissions of 644. If the hgrc config contains
sensitive information (such as Bugzilla credentials), these file
permissions could result in others stealing sensitive data.
Detect when the group and other file mode bits are set and prompt to
remove these permissions.
Bugzilla credentials are optional. Make this more obvious by adding
"optional" to the prompt.
Bugzilla credentials are stored in plain text. Explicitly call this out
in the help text so users can make informed decisions about whether to
capture the credentials.
Developer Tools: Inspector -- screenshot command takes a CSS Selector as the target
object to be captured, but CSS Selectors can contain whitespace. Added quotes
to make sure CSS Selector is treated as a single argument to the screenshot command.
========
https://hg.mozilla.org/integration/gaia-central/rev/494ef969c9dd
Author: Gabriele Svelto <gsvelto@mozilla.com>
Desc: Merge pull request #31005 from gabrielesvelto/bug-1147237-do-not-listen-to-mozl10n-ready
Bug 1147237 - Do not wait for the mozL10n.ready event and clean up the tests so that they are fully stateless r=kgrandon
========
https://hg.mozilla.org/integration/gaia-central/rev/183076fdd54a
Author: Gabriele Svelto <gsvelto@mozilla.com>
Desc: Bug 1147237 - Do not wait for the mozL10n.ready event and clean up the tests so that they are fully stateless r=kgrandon
This patch finally breaks up forwarding received RIL messages to the
main thread before they go to the RIL worker. Any RIL message that is
received on th I/O thread is forwarded directly to the RIL worker
thread and handed over to the RIL worker JS code.
The patch includes a number of changes. They all depend on each other,
so there's no good way of landing them one-by-one.
* |RilConsumer| now runs on the RIL worker thread.
* |RilWorker| uses tasks to register/unregister |RilConsumer| in the worker.
* |RilConsumer| uses |RilSocket| instead of |StreamSocket|.
* With |RilSocket|, received RIL messages do not go through main. They are
forwared to the RIL worker and handed over to JS immediately.
This patch separates the current interface of |RilConsumer| into
two distinct classes. |RilWorker| provides the public interface
and |RilConsumer| provides the internal implementation. Running
|RilConsumer| on a worker thread will be easier this way.
With this patch, |RilSocket| and it's helpers forward received data
via a WCTD. This will hand over the worker's JS context to the RIL
consumer.
In a later patch, the RIL consumer will be moved onto the RIL worker
thread and call the JS ril-worker code directly.
|RilSocket| and |RilSocketConsumer| are copies of the respective stream-
socket classes. Improvements to the RIL I/O code will be implemented on
top of the new classes.
