Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-couch/pull/69#issuecomment-120673998
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enable
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-couch/pull/69#discussion_r34417481
--- Diff: rebar.config.script ---
@@ -76,6 +77,9 @@ IcuDarwinEnv = [{"CFLAGS", "-DXP_UNIX
-I/usr/local/opt/icu4c/include"},
{"LDFLAG
Github user wohali commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/474#issuecomment-120673880
I simply meant that we need someone to *manually* run a test case where we
validate that the configuration process works when setup against not just 3
localhost
Github user wohali commented on a diff in the pull request:
https://github.com/apache/couchdb-couch/pull/69#discussion_r34417453
--- Diff: rebar.config.script ---
@@ -76,6 +77,9 @@ IcuDarwinEnv = [{"CFLAGS", "-DXP_UNIX
-I/usr/local/opt/icu4c/include"},
{"LDFLAG
Github user jaydoane commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/42#issuecomment-120673633
FWIW, this does seem to fix the problem for me locally.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-couch/pull/69#discussion_r34417395
--- Diff: rebar.config.script ---
@@ -76,6 +77,9 @@ IcuDarwinEnv = [{"CFLAGS", "-DXP_UNIX
-I/usr/local/opt/icu4c/include"},
{"LDFLAG
GitHub user wohali opened a pull request:
https://github.com/apache/couchdb-couch/pull/69
Support Windows build target
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/wohali/couchdb-couch windows_support
Alternatively you can re
Github user jaydoane commented on the pull request:
https://github.com/apache/couchdb-couch/pull/68#issuecomment-120666964
I did test, but not this particular case, unfortunately. I agree that it's
broken because of that patch. Going to poke around a bit to see if it can be
repaired.
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-couch/pull/68#issuecomment-120665267
@jaydoane Did you test your patch with local interface? I think, it broke
something useful:
```
$ curl -v -XPOST http://localhost:59860/db/_changes?filt
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/42#issuecomment-120665181
Ok. I also not sure if this one is correct, but I took
[`handle_view_list_req/3`](https://github.com/apache/couchdb-chttpd/blob/master/src/chttpd_show.erl#L170-L172
Github user rnewson commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/42#issuecomment-120661779
Hrm. Will look in the week. Not sure this is the right fix
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/42#issuecomment-120654381
cc @rnewson
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this fea
GitHub user kxepal opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/42
Read request body on POST to changes feed
Prevents to return https://github.com/apache/couchdb-couch/pull/68 error
for every POST request.
You can merge this pull request into a Git repositor
[
https://issues.apache.org/jira/browse/COUCHDB-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623515#comment-14623515
]
Adam Kocoloski commented on COUCHDB-2735:
-
I can confirm that if group_alike_doc
14 matches
Mail list logo
