Re: [webkit-dev] Scheduled downtime - svn.webkit.org and git.webkit.org 5.30 - 6.30pm PDT Monday 3/27/2017

2017-03-28 Thread Ling Ho
Thanks for your mail. For some reason, the post-commit to push git got stuck after r214463. It is now updated and I will watch for the next commit to make sure it's fine. ... ling On 3/28/17 2:04 AM, z...@falconsigh.net wrote: On Tue, Mar 28, 2017, at 10:01 AM, Ling Ho wrote: Hi Zan, I

Re: [webkit-dev] Scheduled downtime - svn.webkit.org and git.webkit.org 5.30 - 6.30pm PDT Monday 3/27/2017

2017-03-28 Thread Ling Ho
Hi Zan, I have tested a git clone earlier and it should be working for you too. We have also taken care notification emails issue to webkit-changes list. Thanks, ... ling On 3/28/17 12:04 AM, z...@falconsigh.net wrote: On Tue, Mar 28, 2017, at 08:45 AM, Lucas Forschler wrote: Quick update:

Re: [webkit-dev] Scheduled downtime - svn.webkit.org and git.webkit.org 5.30 - 6.30pm PDT Monday 3/27/2017

2017-03-28 Thread zan
On Tue, Mar 28, 2017, at 08:45 AM, Lucas Forschler wrote: > Quick update: > > We are currently tracking issues with our EWS bots, as well as not > sending change notification emails to webkit-chan...@lists.webkit.org. > > If you notice anything awry, please let us know so we can investigate.

Re: [webkit-dev] Scheduled downtime - svn.webkit.org and git.webkit.org 5.30 - 6.30pm PDT Monday 3/27/2017

2017-03-28 Thread Lucas Forschler
Quick update: We are currently tracking issues with our EWS bots, as well as not sending change notification emails to webkit-chan...@lists.webkit.org . If you notice anything awry, please let us know so we can investigate. Thanks, Lucas > On Mar 27,

Re: [webkit-dev] Scheduled downtime - svn.webkit.org and git.webkit.org 5.30 - 6.30pm PDT Monday 3/27/2017

2017-03-28 Thread zan
On Tue, Mar 28, 2017, at 10:01 AM, Ling Ho wrote: > Hi Zan, > > I have tested a git clone earlier and it should be working for you > too. We have also taken care notification emails issue to webkit- > changes list. > > Thanks, > ... > ling > Hi, the Git mirror is working now,

Re: [webkit-dev] Proposal to limit the size of the captured exception stack

2017-03-28 Thread Mark Lam
To follow up, I’ve implemented the change in r214289: .org/r214289>. Error.stackTraceLimit is now 100. I also implemented a separate exceptionStackTraceLimit for stack traces captured at the time of throwing a value (not to be confused with Error.stack

Re: [webkit-dev] Proposal to limit the size of the captured exception stack

2017-03-28 Thread Geoffrey Garen
Does the separate exceptionStackTraceLimit mean that if a developer gets a truncated stack trace in the Web Inspector, there’s no way for the developer to remedy that? Is that what other browsers’ developer tools do? Geoff > On Mar 28, 2017, at 4:09 PM, Mark Lam wrote: >

Re: [webkit-dev] Proposal to limit the size of the captured exception stack

2017-03-28 Thread Mark Lam
Matt, I tested this on Firefox and Chrome and saw that Chrome captures up to 200 frames. I don’t see Firefox capturing frames at all when not throwing an Error. Were you looking at Error.stack for Firefox when you came up with the 128 frames number? Maybe there’s a Firebug option I’m not

Re: [webkit-dev] Proposal to limit the size of the captured exception stack

2017-03-28 Thread Matt Baker
> On Mar 28, 2017, at 4:23 PM, Geoffrey Garen wrote: > > Does the separate exceptionStackTraceLimit mean that if a developer gets a > truncated stack trace in the Web Inspector, there’s no way for the developer > to remedy that? Is that what other browsers’ developer tools

Re: [webkit-dev] Proposal to limit the size of the captured exception stack

2017-03-28 Thread Mark Lam
Currently, there’s no way for the developer to change this. We can certainly make it an option that the Inspector can change if desired. Mark > On Mar 28, 2017, at 7:35 PM, Matt Baker wrote: > >> On Mar 28, 2017, at 4:23 PM, Geoffrey Garen >