2009/3/16 Matt Goodall <[email protected]>: > 2009/3/16 Chris Anderson <[email protected]>: >> On Mon, Mar 16, 2009 at 6:07 AM, Jan Lehnardt <[email protected]> wrote: >>> >>> On 15 Mar 2009, at 21:58, Chris Anderson wrote: >>> >>>> We are within striking distance of 0.9 >>>> >>>> 12 Outstanding issues: >>>> >>>> >>>> https://issues.apache.org:443/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310780&priority=1&status=1&status=4&fixfor=12313208&sorter/field=issuekey&sorter/order=DESC >>>> >>>> I think it'd be very cool if we could release in time for ApacheCon EU >>>> - starts on March 23rd. I think this is feasible but it will require >>>> some doing. >>>> >>>> Some of these tickets may be as simple as documentation or exploration >>>> to see if the issue is resolved by the new replication security patch. >>>> None of them look very challenging. >>> >>> >>> I see the replication test failing in Firefox and Safari 3.0 (but not Safari >>> 4 beta) >>> >>> The test fails with >>> >>> {"error":"normal","reason":"{gen_server,call,[<0.29400.0>,get_result,infinity]} >>> >>> which comes as >>> >>> [info] [<0.29281.0>] 127.0.0.1 - - 'GET' >>> /test_suite_db_a/_local%2Fb1fc9bd58a179f7aeb55e42d710fdceb 200 >>> [info] [<0.29359.0>] starting replication "b1fc9bd58a179f7aeb55e42d710fdceb" >>> at <0.29400.0> >>> [info] [<0.29400.0>] recording a checkpoint at source update_seq 20 >>> [error] [<0.29359.0>] Uncaught error in HTTP request: {exit, >>> {normal, >>> {gen_server,call, >>> [<0.29400.0>,get_result,infinity]}}} >>> >>> in the CouchDB log >>> >> >> I get this intermittently on my FF also. Running it a few times makes >> it pass. I think this is more a problem with the test suite than with >> replication. Can you make this a ticket? I think it'll be a fair >> amount of work. > > I've seen the same, or very similar, error when triggering a > replication using curl and Futon's replication page. I don't have any > logs right now though. > > - Matt >
I've also had problems saving and deleting a document in Futon. The few times I've had it has been after the document is in conflict after replication. Again, no logs at the moment; I'll see if I can repeat it. - Matt
