garrensmith closed issue #973: Order changes in replication view, if you click
on an action
URL: https://github.com/apache/couchdb-fauxton/issues/973
This is an automated message from the Apache Git Service.
To respond to
harald-d commented on issue #978: Creating a 2-node cluster with couchdb 2.1
never works
URL: https://github.com/apache/couchdb/issues/978#issuecomment-343833024
Hello Joan,
I can't thank you enough - changing the name in vm.args did the trick, now
the cluster seems to work.
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/138/
Yay, we passed. https://builds.apache.org/job/CouchDB/job/2.1.x/11/
wohali closed pull request #987: Revert to ubuntu Jenkins label, uids now
standardised
URL: https://github.com/apache/couchdb/pull/987
This is an automated message from the Apache Git Service.
To respond to the message,
Boo, we failed. https://builds.apache.org/job/CouchDB/job/master/137/
wohali opened a new pull request #987: Revert to ubuntu Jenkins label, uids now
standardised
URL: https://github.com/apache/couchdb/pull/987
See https://github.com/apache/couchdb/pull/986
This is an automated message
wohali closed pull request #986: Revert to ubuntu Jenkins label, uids now
standardised
URL: https://github.com/apache/couchdb/pull/986
This is an automated message from the Apache Git Service.
To respond to the message,
wohali commented on issue #986: Revert to ubuntu Jenkins label, uids now
standardised
URL: https://github.com/apache/couchdb/pull/986#issuecomment-343771782
```
17:01 <+jan_> Wohali: I think you?re the only one who can reasonably
review
this, feel free to
Yay, we passed. https://builds.apache.org/job/CouchDB/job/jenkins-new-label/2/
janl commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343766547
@ondra-novak Vice President of Apache CouchDB here. Formal notice to check
your attitude and wording. I?m not seeing a language
ondra-novak commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343764159
Thank you very much. If you need help, testing, investigating etc, please
let me know.
rnewson commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343763630
It's probably a bug, yes. we'll look into it. (there's no such as bugfree
code, and couchdb has been production 'ready' for many
wohali commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343763659
Locking this ticket to public updates.
This is an automated
wohali commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343763659
Locking this ticket to updates.
This is an automated message from
ondra-novak commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343763553
I feel that you only just trivialize the bug, or trying to play a game "the
bug is on your side"
no, you have a bug in
wohali commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343762498
Thank you @rnewson.
@ondra-novak Insulting the project you're asking for help from isn't going
to get this resolved any
wohali commented on issue #914: Blacklist some config sections from HTTP
PUT/DELETE operations
URL: https://github.com/apache/couchdb/pull/914#issuecomment-343762644
We know this change is frustrating for your specific use case, but there is
a good reason for this change.
Again,
wohali commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343762498
Thank you @rnewson.
@ondra-novak Insulting the project you're asking for help from isn't going
to get this resolved any
rnewson commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343760312
I can't immediately think why the seq wouldn't be preserved across view
compaction. I'm testing locally now.
ondra-novak commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343759935
> Also for reference, please see
https://issues.apache.org/jira/browse/COUCHDB-2849 which discusses why this is
a problematic
ondra-novak commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343758719
What is purpose of update_seq for the view? Has it some meaningful use?
Till 1.6. it was good reference to find offset
ondra-novak commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343758719
What is purpose of update_seq for the view? Has it some meaningful use?
Till 1.6. it was good reference to find offset
ondra-novak commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343758719
What is purpose of update_seq for the view? Has it some meaningful use?
Until 1.6. it was good reference to find offset
ondra-novak commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343758135
I don't understand, my english is not good.
Is this really WAI?
$ curl -s
wohali commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343758010
Also for reference, please see
https://issues.apache.org/jira/browse/COUCHDB-2849 which discusses why this is
a problematic
wohali commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343757731
Paraphrasing a response that has been given before:
The update sequence values in CouchDB are opaque. In CouchDB 1.x, they
wohali commented on issue #984: update_seq of a view is set to zero after
compaction
URL: https://github.com/apache/couchdb/issues/984#issuecomment-343757399
Functionality was added back into 2.x with this commit:
wohali commented on issue #981: Feature; is it possible to have collection
level above document?
URL: https://github.com/apache/couchdb/issues/981#issuecomment-343755239
This has been requested in the past and is not possible to implement the way
you are requesting.
A better option
mohshraim commented on issue #981: Feature; is it possible to have collection
level above document?
URL: https://github.com/apache/couchdb/issues/981#issuecomment-343752488
@wohali
Thanks for your reply and links..
I have already read the whole documentation a hundred times last
popojargo commented on issue #973: Order changes in replication view, if you
click on an action
URL: https://github.com/apache/couchdb-fauxton/issues/973#issuecomment-343752560
@garrensmith Fixed with #1019
This is an
mohshraim commented on issue #981: Feature; is it possible to have collection
level above document?
URL: https://github.com/apache/couchdb/issues/981#issuecomment-343752488
Thanks for your reply and links..
I have already read the whole documentation a hundred times last month,
ondra-novak opened a new issue #985: _changes since=now doesn't send response
headers till the first output
URL: https://github.com/apache/couchdb/issues/985
I found this after migration from 1.6. Now to request _changes on the
database **since=now** no response headers are returned till
ondra-novak opened a new issue #984: Blocker old bug: update_seq of the view is
set to zero after compaction
URL: https://github.com/apache/couchdb/issues/984
After compaction of the view (not _info), update seq is reset to zero.
## Expected Behavior
Update_seq ought to
ondra-novak commented on issue #914: Blacklist some config sections from HTTP
PUT/DELETE operations
URL: https://github.com/apache/couchdb/pull/914#issuecomment-343728084
OK, so I will need to put some http server there
```
oh boy, please make things more complicated next
ondra-novak commented on issue #914: Blacklist some config sections from HTTP
PUT/DELETE operations
URL: https://github.com/apache/couchdb/pull/914#issuecomment-343728084
OK, so I will need to put some http server there
```
oh boy, please make things more complicated later
kxepal commented on issue #914: Blacklist some config sections from HTTP
PUT/DELETE operations
URL: https://github.com/apache/couchdb/pull/914#issuecomment-343727727
@ondra-novak
Suddenly, no - it's a security measurement. However, for 2.x you still can
manage os_daemons in runtime by
kxepal commented on issue #914: Blacklist some config sections from HTTP
PUT/DELETE operations
URL: https://github.com/apache/couchdb/pull/914#issuecomment-343727727
@ondra-novak
Suddenly, no - it's a security measurement. However, for 2.x you still can
manage os_daemons in runtime by
ondra-novak commented on issue #914: Blacklist some config sections from HTTP
PUT/DELETE operations
URL: https://github.com/apache/couchdb/pull/914#issuecomment-343726379
Is there some way to remove blacklist? I am heavily using os_daemons to
start/stop daemons by http
39 matches
Mail list logo
