This is really interesting in the context of partial replications,
which may occur either explicitly or implicitly as result of security
considerations: http://www.usenix.org/event/nsdi06/tech/full_papers/belaramani/belaramani_html
Antony Blakey
-
CTO, Linkuistics Pty Ltd
Ph: 0438
On Fri, Feb 13, 2009 at 4:03 PM, Jan Lehnardt wrote:
>
> On 14 Feb 2009, at 00:55, Antony Blakey wrote:
>
>> We shouldn't have in-browser tests. In-browser tests are about testing the
>> browser, which we shouldn't do in this project. Our tests should be about
>> Couch, on the command-line, build-
On 14/02/2009, at 10:43 AM, Paul Davis wrote:
If the intention of the code is clear then why bother repeating the
intention, why bother repeating the intention when the code is clear?
See, its fucked up.
No, your comment proves nothing.
Anyway, there's a lot of literature on this subject, so
On Fri, Feb 13, 2009 at 6:55 PM, Antony Blakey wrote:
>
> On 14/02/2009, at 10:09 AM, Paul Davis wrote:
>
>> Tests should be identifiable obviously, but if you want literature in
>> your code, go write AppleScript.
>
> Code should prioritize easy comprehensibility, especially given that there's
>
On 14 Feb 2009, at 00:55, Antony Blakey wrote:
We shouldn't have in-browser tests. In-browser tests are about
testing the browser, which we shouldn't do in this project. Our
tests should be about Couch, on the command-line, build-farm-
integratable.
We have both and we can keep both as bo
On 14/02/2009, at 10:09 AM, Paul Davis wrote:
Tests should be identifiable obviously, but if you want literature in
your code, go write AppleScript.
Code should prioritize easy comprehensibility, especially given that
there's no separate documentation. You're obviously not a literate
prog
On Fri, Feb 13, 2009 at 6:23 PM, Antony Blakey wrote:
>
> On 14/02/2009, at 5:00 AM, Paul Davis wrote:
>
>> 1. NO LONG ASS TEST NAMES.
>
> -1
>
> OTOH, I'd like namespaced tests, so each node isn't a paragraph, but the
> fully qualified form is cf. ruby's rspec et al.
>
Tests should be identifiab
On 14/02/2009, at 5:00 AM, Paul Davis wrote:
1. NO LONG ASS TEST NAMES.
-1
OTOH, I'd like namespaced tests, so each node isn't a paragraph, but
the fully qualified form is cf. ruby's rspec et al.
2. I'd still argue that we shouldn't be using a browser as our native
test runner.
+1
Th
[
https://issues.apache.org/jira/browse/COUCHDB-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673389#action_12673389
]
Adam Kocoloski commented on COUCHDB-240:
Hi Maximillian, thanks. I know the attac
[
https://issues.apache.org/jira/browse/COUCHDB-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673385#action_12673385
]
Maximillian Dornseif commented on COUCHDB-240:
--
The error I'm seeing might ac
Non-Unicde characters in an attachment name render a document unreadable.
-
Key: COUCHDB-254
URL: https://issues.apache.org/jira/browse/COUCHDB-254
Project: CouchDB
Issu
On Fri, Feb 13, 2009 at 1:52 PM, Chris Anderson wrote:
> On Fri, Feb 13, 2009 at 10:30 AM, Paul Davis
> wrote:
>>
>> 2. I'd still argue that we shouldn't be using a browser as our native
>> test runner. We'd have to give up the little green check marks that
>> make us all feel warm and fuzzy when
On Fri, Feb 13, 2009 at 3:13 PM, Chris Anderson wrote:
> On Fri, Feb 13, 2009 at 12:07 PM, Zachary Zolton
> wrote:
>> I know John Resig produced some interesting work, WRT unit testing
>> browser-based JavaScript:
>>
>> http://ejohn.org/projects/bringing-the-browser-to-the-server/
>>
>> Something
[
https://issues.apache.org/jira/browse/COUCHDB-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson closed COUCHDB-252.
--
Resolution: Fixed
applied in r744240
> Allow _list functiosn to signal that iteration of the
On Fri, Feb 13, 2009 at 12:07 PM, Zachary Zolton
wrote:
> I know John Resig produced some interesting work, WRT unit testing
> browser-based JavaScript:
>
> http://ejohn.org/projects/bringing-the-browser-to-the-server/
>
> Something like this might suffice for those who would like to run
> CouchDB
I know John Resig produced some interesting work, WRT unit testing
browser-based JavaScript:
http://ejohn.org/projects/bringing-the-browser-to-the-server/
Something like this might suffice for those who would like to run
CouchDB's JavaScript test suite outside of the browser...?
On Fri, Feb 13,
I second what JChris said. I wouldn't have been nervous about making
my first patch — even though involve some Erlang code — if there
wasn't that easy-to-grasp JavaScript test harness.
On Fri, Feb 13, 2009 at 12:52 PM, Chris Anderson wrote:
> On Fri, Feb 13, 2009 at 10:30 AM, Paul Davis
> wrote:
On 13/02/2009 19:52, Chris Anderson wrote:
I know for sure that in-browser tests are a big part of what brought
me to CouchDB. They tell the story of a web-native database in a way
that nothing else can really touch. They also make it *incredibly
easy* for newcomers to contribute.
They also mak
On Fri, Feb 13, 2009 at 10:30 AM, Paul Davis
wrote:
>
> 2. I'd still argue that we shouldn't be using a browser as our native
> test runner. We'd have to give up the little green check marks that
> make us all feel warm and fuzzy when tests pass, but the browser is a
> huge ass confounding variabl
[
https://issues.apache.org/jira/browse/COUCHDB-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson closed COUCHDB-251.
--
Resolution: Fixed
applied in r744210
> Allow _list functions to accept arbitrary GET paramete
On Feb 13, 2009, at 1:09 PM, Chris Anderson wrote:
On Fri, Feb 13, 2009 at 10:02 AM, Damien Katz
wrote:
My other reason to drop couch.js from the test is it risks becoming
the
defacto JS library, and not a very good one. Because we are trying
to keep
it simple for the tests, it doesn't ha
Couple of thoughts:
1. NO LONG ASS TEST NAMES.
2. I'd still argue that we shouldn't be using a browser as our native
test runner. We'd have to give up the little green check marks that
make us all feel warm and fuzzy when tests pass, but the browser is a
huge ass confounding variable. To me, a pr
On Fri, Feb 13, 2009 at 10:02 AM, Damien Katz wrote:
> My other reason to drop couch.js from the test is it risks becoming the
> defacto JS library, and not a very good one. Because we are trying to keep
> it simple for the tests, it doesn't have lots of features that would be more
> useful for re
So there have been some grumbling that the test suite could use some
changes.
A small problem I see is the use of couch.js in the tests. I'd
personally like to remove the Javascript couch.js library usage from
the tests and instead use more naked HTTP calls and simple sub-routines.
My bi
[
https://issues.apache.org/jira/browse/COUCHDB-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Anderson closed COUCHDB-253.
--
Resolution: Fixed
applied in r744193
> Replicator should not use chunked transfer-encoding on
[
https://issues.apache.org/jira/browse/COUCHDB-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noah Slater updated COUCHDB-250:
Fix Version/s: 0.9
Priority: Blocker (was: Minor)
> init script missing check for $COUCH
Replicator should not use chunked transfer-encoding on GET requests
---
Key: COUCHDB-253
URL: https://issues.apache.org/jira/browse/COUCHDB-253
Project: CouchDB
Issue Type: Bug
[
https://issues.apache.org/jira/browse/COUCHDB-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis updated COUCHDB-252:
--
Attachment: COUCHDB-252.patch
Patch for the improvment. This may cause a conflict with
Allow _list functiosn to signal that iteration of the view should cease.
Key: COUCHDB-252
URL: https://issues.apache.org/jira/browse/COUCHDB-252
Project: CouchDB
Issue
[
https://issues.apache.org/jira/browse/COUCHDB-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis updated COUCHDB-251:
--
Attachment: COUCHDB-251.patch
Patch for the improvement.
> Allow _list functions to a
Allow _list functions to accept arbitrary GET parameters.
-
Key: COUCHDB-251
URL: https://issues.apache.org/jira/browse/COUCHDB-251
Project: CouchDB
Issue Type: Improvement
Co
On 13 Feb 2009, at 01:46, Chris Anderson wrote:
Also, hoping to get feedback from the mochiweb team on the mochi parts
of the patch, but their google group seems to be taking a while to
accept new messages...
Your email made it through fine. Groups doesn't send you a copy of your
own mails by
init script missing check for $COUCHDB_PID_FILE
---
Key: COUCHDB-250
URL: https://issues.apache.org/jira/browse/COUCHDB-250
Project: CouchDB
Issue Type: Bug
Components: Build System
A
[
https://issues.apache.org/jira/browse/COUCHDB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viacheslav Seledkin updated COUCHDB-249:
Attachment: couch_view_updater.erl
this is modified couch_view_updater.erl of 7398
34 matches
Mail list logo
