On Thu, Oct 31, 2019, 06:02 Jason Orendorff wrote:
> Ignoring the awaited value here is like using `catch {}` to squelch all
> exceptions, or ignoring the return value of an async function or method, or
> any other expression that produces a Promise. Do we have lints for those
> pitfalls? I'm
On 11/1/19 4:03 PM, Andrew Sutherland wrote:
On 11/1/19 4:39 PM, Kim Moir wrote:
On Nov 14, 2019, we intend to change the permissions associated with
Level
3 access to revoke direct push access to hg.mozilla.org on
mozilla-inbound,
mozilla-central, mozilla-beta, mozilla-release and esr repos.
On 11/1/19 4:39 PM, Kim Moir wrote:
On Nov 14, 2019, we intend to change the permissions associated with Level
3 access to revoke direct push access to hg.mozilla.org on mozilla-inbound,
mozilla-central, mozilla-beta, mozilla-release and esr repos.
For mozilla-beta, mozilla-release, and esr...
Officially decommissioning m-i will take place after we change the
permissions. It will remain a read-only repo for historical purposes. No I
don't see a need to run things in CI on m-i beyond that date.
deprecate mozilla-inbound after Lando is used for most mozilla-central
landing
The Engineering Workflow team enabled a hook in July which asked people to
provide a reason for directly pushing to hg.mozilla.org. Since it was
enabled, we have seen the number of direct pushes decrease to a few per
week.
Enabling developers to use standard tools to land reviewed code through a
On 10/31/19 7:31 PM, Junior Hsu wrote:
However, it doesn't not align the spec
Is that covered by https://github.com/whatwg/fetch/issues/274 or is
there a new spec issue needed?
-Boris
___
dev-platform mailing list
dev-platform@lists.mozilla.org
Just a quick reminder that the deadline for Fx72 Pi Requests is *today*.
Please submit your requests as soon as possible.
On Tue, Oct 29, 2019 at 11:20 PM Tom Grabowski
wrote:
> PI team has made the criteria for feature inclusion in release scope
>
Hi there!
Release Engineering has improved how Firefox Preview and other Android
Projects are published with Taskcluster, thanks to Taskgraph. What is
Taskgraph? Why does Taskcluster work better with it? Check out this
3-minute-video:
[image: image.png]
In Firefox 72, we'll ship the Nullish Coalescing Operator, allowing
developers to easily test for values that may be falsy, but are not null or
undefined. It will be available in the next Nightly. The proposal is in
stage 3, and has been added to the agenda for December 2019 to go to stage
4.
To be more specific, the title should be "Add image/webp to default Accept
navigation header"
That is, include image/webp when content policy is DOCUMENT/SUB_DOCUMENT.
fetch()/"Save as" is with `Accept: */*" as is.
Thanks for any feedback.
Junior
On Thu, Oct 31, 2019 at 4:31 PM Junior Hsu
Would this fix https://bugzilla.mozilla.org/show_bug.cgi?id=1526731#c15
? (That is, would we now send image/webp as part of the accept header
for the fetch() / nsIWebBrowserPersist requests?)
~ Gijs
On 31/10/2019 23:31, Junior Hsu wrote:
Summary:
I'd like to increase the visibility for this
On 11/1/19 6:08 AM, Paolo Amadini wrote:
On 10/31/2019 1:57 PM, Jan-Ivar Bruaroey wrote:
The context here is the same as Promise.allSettled: we explicitly *do*
want to ignore errors, right?
In general, in mozilla-central we want to at least log those errors, at
which point they are already
12 matches
Mail list logo
