On Sep 26, 2015 09:33, "Eric Rescorla" wrote:
>
> On Fri, Sep 25, 2015 at 3:20 PM, wrote:
>
> > On Saturday, September 19, 2015 at 8:15:50 PM UTC+2, Eric Rescorla
wrote:
> > > On Sat, Sep 19, 2015 at 11:09 AM, Oliver Lietz
wrote:
> > >
> > > > Hi,
> > > > our nanoStream plugin supports live enco
On Fri, Sep 25, 2015 at 3:20 PM, wrote:
> On Saturday, September 19, 2015 at 8:15:50 PM UTC+2, Eric Rescorla wrote:
> > On Sat, Sep 19, 2015 at 11:09 AM, Oliver Lietz wrote:
> >
> > > Hi,
> > > our nanoStream plugin supports live encoding and streaming with
> > > h264/aac/rtmp from live camera s
On Sat, Sep 26, 2015 at 7:34 AM, Ehsan Akhgari
wrote:
> On 2015-09-25 12:01 PM, Justin Dolske wrote:
>
>> At Mozilla, it seems like previous discussions on this kind of thing
>> (style and warnings come to mind) have dealt with this at a
>> file/directory/module level... Someone fixes up a thing
On Sat, Sep 26, 2015 at 10:20 AM, wrote:
> MSE is playback only, so no option for live broadcast.
>
What do you mean? There doesn't seem to be any reason why MSE can't do live
broadcast.
If you're using HLS, you can use MSE.
https://github.com/dailymotion/hls.js
> WebRTC is VP9 and a peer pro
On Fri, Sep 25, 2015 at 11:46 PM, Ehsan Akhgari wrote:
>
> Our static analysis builds can be easily triggered from the try server
> (although I have been unable to get anyone interested to fix bug 1116518 to
> make those builds happen on the try server by default, which makes it all
> too easy for
On Saturday, September 19, 2015 at 8:15:50 PM UTC+2, Eric Rescorla wrote:
> On Sat, Sep 19, 2015 at 11:09 AM, Oliver Lietz wrote:
>
> > Hi,
> > our nanoStream plugin supports live encoding and streaming with
> > h264/aac/rtmp from live camera sources and capture devices.
> > We needed to replace
On 2015-09-25 12:01 PM, Justin Dolske wrote:
On 9/25/15 7:06 AM, Robert O'Callahan wrote:
[...]I'm not quite sure
what it would take to get those build failures to appear in MozReview
but
it should be possible.
The tricky bit is to determine which failures were introduced by the
patch,
and j
I have now updated the git-bz-moz and moz-git-tools repositories with my
REST API rewrite. Let me know if you have any problems or feedback (I'm
mccr8 on IRC). Thanks to everybody who gave me feedback, and to froydnj who
looked over the many patches.
Andrew
On Wed, Sep 23, 2015 at 1:49 PM, Andrew
On 9/25/15 7:06 AM, Robert O'Callahan wrote:
[...]I'm not quite sure
what it would take to get those build failures to appear in MozReview but
it should be possible.
The tricky bit is to determine which failures were introduced by the patch,
and just display those, and display them in the con
On Fri, Sep 25, 2015 at 10:46 AM, Josh Matthews
wrote:
> On 2015-09-25 10:06 AM, Robert O'Callahan wrote:
>
>> On Sat, Sep 26, 2015 at 1:46 AM, Ehsan Akhgari
>> wrote:
>>
>> Our static analysis builds can be easily triggered from the try server
>>> (although I have been unable to get anyone inte
On Fri, Sep 25, 2015 at 10:06 AM, Robert O'Callahan
wrote:
> On Sat, Sep 26, 2015 at 1:46 AM, Ehsan Akhgari
> wrote:
>
> Our static analysis builds can be easily triggered from the try server
>> (although I have been unable to get anyone interested to fix bug 1116518 to
>> make those builds happ
On 2015-09-25 10:06 AM, Robert O'Callahan wrote:
On Sat, Sep 26, 2015 at 1:46 AM, Ehsan Akhgari
wrote:
Our static analysis builds can be easily triggered from the try server
(although I have been unable to get anyone interested to fix bug 1116518 to
make those builds happen on the try server b
On Fri, Sep 25, 2015 at 12:19 AM, Robert O'Callahan
wrote:
> On Fri, Sep 25, 2015 at 5:41 AM, Sylvestre Ledru
> wrote:
>
> > Any questions, comments?
> >
>
> This whitepaper on Infer is an interesting read:
>
> https://fbcdn-dragon-a.akamaihd.net/hphotos-ak-xap1/t39.2365-6/10935986_9852840081636
On Sat, Sep 26, 2015 at 1:46 AM, Ehsan Akhgari
wrote:
> Our static analysis builds can be easily triggered from the try server
> (although I have been unable to get anyone interested to fix bug 1116518 to
> make those builds happen on the try server by default, which makes it all
> too easy for p
On 2015-09-24 10:55 PM, Justin Dolske wrote:
On 9/24/15 6:55 PM, Robert O'Callahan wrote:
FWIW I agree that Talos results for Linux32 are unimportant. Even if
there
was a Linux-32-only regression, I don't think it'd be worth our
developers
spending time on it.
I agree. Kill them.
+1.
_
On 2015-09-25 12:19 AM, Robert O'Callahan wrote:
On Fri, Sep 25, 2015 at 5:41 AM, Sylvestre Ledru
wrote:
Any questions, comments?
This whitepaper on Infer is an interesting read:
https://fbcdn-dragon-a.akamaihd.net/hphotos-ak-xap1/t39.2365-6/10935986_985284008163608_74391_n/Moving_Fast_
On 2015-09-25 5:35 AM, Sylvestre Ledru wrote:
Le 24/09/2015 23:29, Ehsan Akhgari a écrit :
On 2015-09-24 1:41 PM, Sylvestre Ledru wrote:
= Static analyzers =
For now, we are running:
* Coverity, a proprietary tool with a great (but slow) web interface. As
Firefox is Free software, the service i
Le 25/09/2015 01:05, Robert O'Callahan a écrit :
> Why not make scan-builds and infer results public? Those are public tools so
> we should assume black-hats already have the resutls.
>
>
When I presented these results on the sec ml a while back, I have been asked to
hide them because
they show p
Le 24/09/2015 23:29, Ehsan Akhgari a écrit :
> On 2015-09-24 1:41 PM, Sylvestre Ledru wrote:
>> = Static analyzers =
>> For now, we are running:
>> * Coverity, a proprietary tool with a great (but slow) web interface. As
>> Firefox is Free software, the service is provided for free
>> but with a re
19 matches
Mail list logo
