Re: [Factor-talk] [ planet-factor ] site down
The site seems up. We had a regression that made it very unreliable,
crashing every few hours. It should be back to crashing every couple months
now.
If you want to read the docs offline, you can do this (takes several
minutes to run, Factor will hang in the meantime):
USE: help.html generate-help
"docs" cache-directory .
On Mac, that puts the docs in:
"/Users/erg/Library/Caches/org.factorcode.Factor"
Sorry about the stability, the build farm is running again and should catch
serious regressions in the future.
Doug
On Tue, Mar 18, 2014 at 9:41 PM, Davison wrote:
> The site is up for me. I hit docs, planet, and main site (factorcode.org)
> without an issue.
>
>
> On Wed, Mar 19, 2014 at 12:02 AM, Dave Carlton > wrote:
>
>> Still down here :(
>>
>> I can mirror the site once you get it up.
>>
>> On Mar 11, 2014, at 21:01 , John Benediktsson wrote:
>>
>> It looks like we might have tracked down the issue. I have updated
>> factorcode.org and will see if it stays running now.
>>
>> Best,
>> John.
>>
>>
>> On Tue, Mar 11, 2014 at 6:59 AM, John Benediktsson wrote:
>>
>>> There is some specific input that a spammer is making on
>>> paste.factorcode.org that seems to be taking down the server, not sure
>>> if this is a new bug that was introduced or an old one that is being
>>> exposed. It's related to the new-annotation url, but haven't been able to
>>> figure it out yet.
>>>
>>> Thought I had the solution yesterday with
>>> commit 49ce12d00b4c4f882e40d035d193e8f2f5dc64c8, but it appears maybe not.
>>>
>>> [2014-03-07T18:58:00Z] NOTICE handle-client: { T{ duplex-stream f
>>> ~decoder~ ~encoder~ } T{ inet4 f "192.99.0.94" 60549 } T{ inet4 f "0.0.0.0"
>>> 8080 } }
>>> [2014-03-07T18:58:00Z] NOTICE accepted-connection: remote:
>>> 192.99.0.94:60549, local: 0.0.0.0:8080
>>> [2014-03-07T18:58:00Z] NOTICE httpd-hit: { "POST" URL" http://paste.
>>> factorcode.org/new-annotation" }
>>> [2014-03-07T18:58:00Z] NOTICE httpd-header: { "user-agent" "Mozilla/4.0
>>> (compatible; MSIE 6.0; Windows NT 5.1)" }
>>> [2014-03-07T18:58:00Z] NOTICE httpd-header: { "x-forwarded-for" f }
>>> [2014-03-07T18:58:00Z] DEBUG init-user: f
>>> *[2014-03-07T18:58:00Z] ERROR do-request: Memory protection fault at
>>> address 0*
>>> [2014-03-07T18:58:04Z] NOTICE handle-client: { T{ duplex-stream f
>>> ~decoder~ ~encoder~ } T{ inet4 f "187.21.213.198" 46293 } T{ inet4 f
>>> "0.0.0.0" 8080 } }
>>> [2014-03-07T18:58:04Z] NOTICE accepted-connection: remote:
>>> 187.21.213.198:46293, local: 0.0.0.0:8080
>>>
>>> If you want to help troubleshoot, maybe you and I and @erg can talk
>>> offline about approaches?
>>>
>>> Best,
>>> John.
>>>
>>>
>>>
>>> On Tue, Mar 11, 2014 at 4:26 AM, Jon Harper wrote:
>>>
What do we have to do to repair factorcode.org and concatenative.org? I
can spend time on this if needed.
Jon
On Thu, Mar 6, 2014 at 1:17 PM, Dominikus Herzberg <
dominikus.herzb...@gmail.com> wrote:
> The site factorcode.org is still down. I'm missing the online doc
> very much ...
>
> / Dominikus
>
>
> 2014-03-01 20:52 GMT+01:00 mr wzrd :
>
> Cannot connect to planet.factorcode.org today.
>>
>>
>>
>> --
>> Flow-based real-time traffic analytics software. Cisco certified tool.
>> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
>> Customize your own dashboards, set traffic alerts and generate
>> reports.
>> Network behavioral analysis & security monitoring. All-in-one tool.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
>> ___
>> Factor-talk mailing list
>> Factor-talk@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/factor-talk
>>
>
>
>
> --
> Subversion Kills Productivity. Get off Subversion & Make the Move to
> Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually
> works.
> Faster operations. Version large binaries. Built-in WAN optimization
> and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>
> ___
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
>
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download
Re: [Factor-talk] [ planet-factor ] site down
The site is up for me. I hit docs, planet, and main site (factorcode.org)
without an issue.
On Wed, Mar 19, 2014 at 12:02 AM, Dave Carlton
wrote:
> Still down here :(
>
> I can mirror the site once you get it up.
>
> On Mar 11, 2014, at 21:01 , John Benediktsson wrote:
>
> It looks like we might have tracked down the issue. I have updated
> factorcode.org and will see if it stays running now.
>
> Best,
> John.
>
>
> On Tue, Mar 11, 2014 at 6:59 AM, John Benediktsson wrote:
>
>> There is some specific input that a spammer is making on
>> paste.factorcode.org that seems to be taking down the server, not sure
>> if this is a new bug that was introduced or an old one that is being
>> exposed. It's related to the new-annotation url, but haven't been able to
>> figure it out yet.
>>
>> Thought I had the solution yesterday with
>> commit 49ce12d00b4c4f882e40d035d193e8f2f5dc64c8, but it appears maybe not.
>>
>> [2014-03-07T18:58:00Z] NOTICE handle-client: { T{ duplex-stream f
>> ~decoder~ ~encoder~ } T{ inet4 f "192.99.0.94" 60549 } T{ inet4 f "0.0.0.0"
>> 8080 } }
>> [2014-03-07T18:58:00Z] NOTICE accepted-connection: remote:
>> 192.99.0.94:60549, local: 0.0.0.0:8080
>> [2014-03-07T18:58:00Z] NOTICE httpd-hit: { "POST" URL" http://paste.
>> factorcode.org/new-annotation" }
>> [2014-03-07T18:58:00Z] NOTICE httpd-header: { "user-agent" "Mozilla/4.0
>> (compatible; MSIE 6.0; Windows NT 5.1)" }
>> [2014-03-07T18:58:00Z] NOTICE httpd-header: { "x-forwarded-for" f }
>> [2014-03-07T18:58:00Z] DEBUG init-user: f
>> *[2014-03-07T18:58:00Z] ERROR do-request: Memory protection fault at
>> address 0*
>> [2014-03-07T18:58:04Z] NOTICE handle-client: { T{ duplex-stream f
>> ~decoder~ ~encoder~ } T{ inet4 f "187.21.213.198" 46293 } T{ inet4 f
>> "0.0.0.0" 8080 } }
>> [2014-03-07T18:58:04Z] NOTICE accepted-connection: remote:
>> 187.21.213.198:46293, local: 0.0.0.0:8080
>>
>> If you want to help troubleshoot, maybe you and I and @erg can talk
>> offline about approaches?
>>
>> Best,
>> John.
>>
>>
>>
>> On Tue, Mar 11, 2014 at 4:26 AM, Jon Harper wrote:
>>
>>> What do we have to do to repair factorcode.org and concatenative.org ?
>>> I can spend time on this if needed.
>>>
>>> Jon
>>>
>>>
>>> On Thu, Mar 6, 2014 at 1:17 PM, Dominikus Herzberg <
>>> dominikus.herzb...@gmail.com> wrote:
>>>
The site factorcode.org is still down. I'm missing the online doc very
much ...
/ Dominikus
2014-03-01 20:52 GMT+01:00 mr wzrd :
Cannot connect to planet.factorcode.org today.
>
>
>
> --
> Flow-based real-time traffic analytics software. Cisco certified tool.
> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
> Customize your own dashboards, set traffic alerts and generate reports.
> Network behavioral analysis & security monitoring. All-in-one tool.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
> ___
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
--
Subversion Kills Productivity. Get off Subversion & Make the Move to
Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization
and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
___
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
>>>
>>>
>>> --
>>> Learn Graph Databases - Download FREE O'Reilly Book
>>> "Graph Databases" is the definitive new guide to graph databases and
>>> their
>>> applications. Written by three acclaimed leaders in the field,
>>> this first edition is now available. Download your free book today!
>>> http://p.sf.net/sfu/13534_NeoTech
>>>
>>> ___
>>> Factor-talk mailing list
>>> Factor-talk@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/factor-talk
>>>
>>>
>>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
>
> http://p.sf.net/sfu/13534_NeoTech___
> Factor-talk mailing list
>
Re: [Factor-talk] [ planet-factor ] site down
Still down here :(
I can mirror the site once you get it up.
On Mar 11, 2014, at 21:01 , John Benediktsson wrote:
> It looks like we might have tracked down the issue. I have updated
> factorcode.org and will see if it stays running now.
>
> Best,
> John.
>
>
> On Tue, Mar 11, 2014 at 6:59 AM, John Benediktsson wrote:
> There is some specific input that a spammer is making on paste.factorcode.org
> that seems to be taking down the server, not sure if this is a new bug that
> was introduced or an old one that is being exposed. It's related to the
> new-annotation url, but haven't been able to figure it out yet.
>
> Thought I had the solution yesterday with commit
> 49ce12d00b4c4f882e40d035d193e8f2f5dc64c8, but it appears maybe not.
>
> [2014-03-07T18:58:00Z] NOTICE handle-client: { T{ duplex-stream f ~decoder~
> ~encoder~ } T{ inet4 f "192.99.0.94" 60549 } T{ inet4 f "0.0.0.0" 8080 } }
> [2014-03-07T18:58:00Z] NOTICE accepted-connection: remote: 192.99.0.94:60549,
> local: 0.0.0.0:8080
> [2014-03-07T18:58:00Z] NOTICE httpd-hit: { "POST" URL"
> http://paste.factorcode.org/new-annotation"; }
> [2014-03-07T18:58:00Z] NOTICE httpd-header: { "user-agent" "Mozilla/4.0
> (compatible; MSIE 6.0; Windows NT 5.1)" }
> [2014-03-07T18:58:00Z] NOTICE httpd-header: { "x-forwarded-for" f }
> [2014-03-07T18:58:00Z] DEBUG init-user: f
> [2014-03-07T18:58:00Z] ERROR do-request: Memory protection fault at address 0
> [2014-03-07T18:58:04Z] NOTICE handle-client: { T{ duplex-stream f ~decoder~
> ~encoder~ } T{ inet4 f "187.21.213.198" 46293 } T{ inet4 f "0.0.0.0" 8080 } }
> [2014-03-07T18:58:04Z] NOTICE accepted-connection: remote:
> 187.21.213.198:46293, local: 0.0.0.0:8080
>
> If you want to help troubleshoot, maybe you and I and @erg can talk offline
> about approaches?
>
> Best,
> John.
>
>
>
> On Tue, Mar 11, 2014 at 4:26 AM, Jon Harper wrote:
> What do we have to do to repair factorcode.org and concatenative.org ? I can
> spend time on this if needed.
>
> Jon
>
>
> On Thu, Mar 6, 2014 at 1:17 PM, Dominikus Herzberg
> wrote:
> The site factorcode.org is still down. I'm missing the online doc very much
> ...
>
> / Dominikus
>
>
> 2014-03-01 20:52 GMT+01:00 mr wzrd :
>
> Cannot connect to planet.factorcode.org today.
>
>
> --
> Flow-based real-time traffic analytics software. Cisco certified tool.
> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
> Customize your own dashboards, set traffic alerts and generate reports.
> Network behavioral analysis & security monitoring. All-in-one tool.
> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
> ___
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
>
> --
> Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
> With Perforce, you get hassle-free workflows. Merge that actually works.
> Faster operations. Version large binaries. Built-in WAN optimization and the
> freedom to use Git, Perforce or both. Make the move to Perforce.
> http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
>
> ___
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
>
> ___
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
>
>
>
> --
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech___
> Factor-talk mailing list
> Factor-talk@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/factor-talk
--
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your f
Re: [Factor-talk] manual memory management and STRUCT:
2014-03-18 14:12 GMT+01:00 Jon Harper : > In this case, it's more complicated then a single with-destructor scope, > because I use the destructors to call libyaml's destroy function on the > struct, so that the same memory can be reused between the calls to libyaml > for this struct. So I really need to destroy it right away before the next > call the libyaml, hence the nested with-destructors. > > I could allocate new memory for those structs every time and destroy them > only at the end of the parsing. But in most cases, only one struct is needed > at a given time, so I thought reusing them was a good thing. > Jon I think you're falling for the premature optimization trap here. Allocating memory is incredibly cheap so unless your code is memory constrained there is no need to save on it. It's always better to start with the simplest implementation you can get away with and then if you run into performance problems start to optimize it. -- mvh/best regards Björn Lindqvist -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] manual memory management and STRUCT:
In this case, it's more complicated then a single with-destructor scope, because I use the destructors to call libyaml's destroy function on the struct, so that the same memory can be reused between the calls to libyaml for this struct. So I really need to destroy it right away before the next call the libyaml, hence the nested with-destructors. I could allocate new memory for those structs every time and destroy them only at the end of the parsing. But in most cases, only one struct is needed at a given time, so I thought reusing them was a good thing. Jon On Tue, Mar 18, 2014 at 12:21 PM, Björn Lindqvist wrote: > Hi Jon, > > 2014-03-17 21:57 GMT+01:00 Jon Harper : > > Hi list, > > I am working with libyaml, a C library to parse yaml docs. Some libyaml > > functions give string results by malloc'ing memory and giving back > pointers > > to those strings in a struct. They then require the caller to call a > libyaml > > "destroy" function on the struct that frees the strings. > > > > I would like to make a deep copy of the manually managed struct to a > garbage > > collected struct so that I can keep some data after I called the libyaml > > destroy function and not worry about freeing it. Does anyone know how to > do > > this simply ? > > Let me preface this by saying that I'm far from an expert neither on > libyaml or factor... But this is what I think I've figured out about > how alien memory management works. > > What I think you are doing wrong is worrying to much about freeing the > memory you are allocating. The ?scalar-value word is only an > intermediate step in the doc parsing process. Since the yaml> words > body already is wrapped in a with-destructors block, and it is the > main entry point for your parser, you don't need to call > with-destructors anywhere else. > > Just remember to pair every allocation (or resource acquisition) with a > &destructor word (which you already are doing) and factor should work > it out fine. > > > -- > mvh/best regards Björn Lindqvist > > > -- > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > ___ > Factor-talk mailing list > Factor-talk@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/factor-talk > -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
Re: [Factor-talk] manual memory management and STRUCT:
Hi Jon, 2014-03-17 21:57 GMT+01:00 Jon Harper : > Hi list, > I am working with libyaml, a C library to parse yaml docs. Some libyaml > functions give string results by malloc'ing memory and giving back pointers > to those strings in a struct. They then require the caller to call a libyaml > "destroy" function on the struct that frees the strings. > > I would like to make a deep copy of the manually managed struct to a garbage > collected struct so that I can keep some data after I called the libyaml > destroy function and not worry about freeing it. Does anyone know how to do > this simply ? Let me preface this by saying that I'm far from an expert neither on libyaml or factor... But this is what I think I've figured out about how alien memory management works. What I think you are doing wrong is worrying to much about freeing the memory you are allocating. The ?scalar-value word is only an intermediate step in the doc parsing process. Since the yaml> words body already is wrapped in a with-destructors block, and it is the main entry point for your parser, you don't need to call with-destructors anywhere else. Just remember to pair every allocation (or resource acquisition) with a &destructor word (which you already are doing) and factor should work it out fine. -- mvh/best regards Björn Lindqvist -- Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech ___ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
