After rev 891077 (ticket 558, md5 integrity check) I need to update that
patch for storing gzip compressed attachments.
The md5 calculated by couch_stream corresponds to the md5 of the gzipped
content, therefore not matching the attachment content sent by the client
for those attachments having a m
[
https://issues.apache.org/jira/browse/COUCHDB-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792717#action_12792717
]
Paul Joseph Davis commented on COUCHDB-597:
---
No idea. I'll try and reproduce whe
[
https://issues.apache.org/jira/browse/COUCHDB-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792710#action_12792710
]
Robert Newson commented on COUCHDB-597:
---
well, on my production class server, the sa
[
https://issues.apache.org/jira/browse/COUCHDB-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792709#action_12792709
]
Robert Newson commented on COUCHDB-597:
---
It doesn't seem to, no.
> Replication tas
[
https://issues.apache.org/jira/browse/COUCHDB-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792705#action_12792705
]
Paul Joseph Davis commented on COUCHDB-597:
---
Does this produce the {#Ref<...>, 3
[
https://issues.apache.org/jira/browse/COUCHDB-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792702#action_12792702
]
Robert Newson commented on COUCHDB-597:
---
fy: current trunk fails with;
{"error":"er
[
https://issues.apache.org/jira/browse/COUCHDB-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792700#action_12792700
]
Robert Newson commented on COUCHDB-597:
---
I can reproduce at least one problem with r
[
https://issues.apache.org/jira/browse/COUCHDB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792655#action_12792655
]
Benoit Chesneau commented on COUCHDB-595:
-
answering myself, using recv(0) allow u
[
https://issues.apache.org/jira/browse/COUCHDB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-595:
Attachment: couchdb_att_100_continue2.patch
chunked send use stream_body which already sen
[
https://issues.apache.org/jira/browse/COUCHDB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Chesneau updated COUCHDB-595:
Attachment: couchdb_att_100_continue.patch
Patch that seem to fix the issue. To put attach
[
https://issues.apache.org/jira/browse/COUCHDB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792639#action_12792639
]
Benoit Chesneau commented on COUCHDB-595:
-
Closer look on it using raw socket call
[
https://issues.apache.org/jira/browse/COUCHDB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson reopened COUCHDB-595:
---
Below is a script to reproduce the problem.
Curl sends this;
> PUT /db1/doc1/att HTTP/1.1
> U
FYI, I haven't looked at this patch's code, but I like it's concepts and I hope
of the other committers will have a chance to look at it soon and work out any
issues to get it checked into trunk. If not I eventually will get around to it,
but I can't promise when.
-Damien
On Dec 9, 2009, at 8
Apologies for not replying, I have a lot of stuff going on right.
For 1.0 features, I only want a few more enhancements to continuous replication
(they might already be there) and full windows support.
I think we should set a hard date of Feb 1. for feature freeze, 0.11.0 is the
last new featur
Testing new settings as my previous messages haven't gotten through.
-Damien
On 18 Dec 2009, at 17:37, Robert Newson wrote:
> Jira does build a roadmap for you, but it depends on you filing
> bugs/tasks and assigning them as "fix for ". I'm not sure we
> all can add new versions (that should be locked down if it's not
> already), but that's how roadmaps are handled in jir
Jira does build a roadmap for you, but it depends on you filing
bugs/tasks and assigning them as "fix for ". I'm not sure we
all can add new versions (that should be locked down if it's not
already), but that's how roadmaps are handled in jira.
B.
On Fri, Dec 18, 2009 at 5:10 PM, Paul Davis wrot
Link might be handy:
http://forrest.apache.org/forrest-issues.html
On Fri, Dec 18, 2009 at 12:09 PM, Paul Davis
wrote:
> On Fri, Dec 18, 2009 at 12:05 PM, Noah Slater wrote:
>> Hey,
>>
>> Does JIRA have a page what we could use as the roadmap?
>>
>> That would have the added advantage of updati
On Fri, Dec 18, 2009 at 12:05 PM, Noah Slater wrote:
> Hey,
>
> Does JIRA have a page what we could use as the roadmap?
>
> That would have the added advantage of updating itself automatically as we
> edited tickets.
>
> I found the roadmap tab from the main CouchDB page, but it doesn't have any
init script needlessly 'su's, and non-superuser use fails
-
Key: COUCHDB-603
URL: https://issues.apache.org/jira/browse/COUCHDB-603
Project: CouchDB
Issue Type: Improvement
Co
Hey,
Does JIRA have a page what we could use as the roadmap?
That would have the added advantage of updating itself automatically as we
edited tickets.
I found the roadmap tab from the main CouchDB page, but it doesn't have any
tickets for post 0.10 on it.
Thoughts?
Thanks,
Noah
On 18 Dec 2009, at 16:45, Dirkjan Ochtman wrote:
> That said, it's perfectly alright if there's no roadmap at all, I'm
> just surprised by the lack of thoughts from the core developers (who
> are usually the ones to have these ideas) in this thread.
Three of the core developers have been busy at
On Fri, Dec 18, 2009 at 17:02, Paul Davis wrote:
> I'm not really a fan of roadmaps. We get new features when people
> write them. Everyone has the ability to write code, submit it and get
> a new feature. I can't tell you what feature you're going to write, so
> why would I tell everyone else tha
On Fri, Dec 18, 2009 at 2:39 AM, Dirkjan Ochtman wrote:
> It seems weird that none of the core developers have bothered to write
> up some of their ideas here, for ten days running now. I understand
> you're all busy with Relaxed, but it doesn't have to take so long,
> does it? IMO it would be nic
On Tue, Dec 15, 2009 at 11:11:52AM +0100, Kosta Welke wrote: To insert in a
> list, insert in the middle of the existing 'boundaries'. For inserting
> items at the beginning or end, the boundaries are "a".charCodeAt(0)-1
> (which is "`") and "z".CharCodeAt(0)+1 (which is "{"). If you want, you
> ca
I sort of agree with you, but in all fairness some of the core programmers have
weighed in.
To repeat my earlier post, I think it's a good time to put some stakes in the
ground with respect to direction. I'm sure there are a number of parties
interested in extending and making use of the intern
[
https://issues.apache.org/jira/browse/COUCHDB-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Davies resolved COUCHDB-598.
--
Resolution: Won't Fix
> _show without docid returns 500 instead of 404
> -
27 matches
Mail list logo
