[
https://issues.apache.org/jira/browse/COUCHDB-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625892#comment-14625892
]
ASF GitHub Bot commented on COUCHDB-2750:
-
GitHub user davisp opened a pull requ
Paul Joseph Davis created COUCHDB-2750:
--
Summary: Update khash to not use un-exported functions for Windows
support
Key: COUCHDB-2750
URL: https://issues.apache.org/jira/browse/COUCHDB-2750
Proje
Github user jaydoane commented on the pull request:
https://github.com/apache/couchdb-couch-replicator/pull/12#issuecomment-121134650
The follow-up PR: https://github.com/cloudant/chttpd-local/pull/15
---
If your project is set up for it, you can reply to this email and have your
rep
Github user davisp commented on the pull request:
https://github.com/apache/couchdb-couch/pull/71#issuecomment-121134365
I'm working on getting the actual dataset used and benchmark code. The
general outline of the test though is that they loaded something like 35K
records into a Q=12
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-couch/pull/71#issuecomment-121092448
@davisp wowow! how are the numbers for a micro-benchmark that uses of one
of our api-endpoints compared to an unpatched version?
I usually run somet
[
https://issues.apache.org/jira/browse/COUCHDB-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625297#comment-14625297
]
ASF GitHub Bot commented on COUCHDB-2740:
-
Github user rnewson closed the pull r
Github user rnewson commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/41#issuecomment-121051190
not sure this is the way to go.
---
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 do
[
https://issues.apache.org/jira/browse/COUCHDB-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625298#comment-14625298
]
ASF GitHub Bot commented on COUCHDB-2740:
-
Github user rnewson closed the pull r
Github user rnewson closed the pull request at:
https://github.com/apache/couchdb-couch/pull/65
---
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
enabled and wishes so, or if the feature
Github user rnewson closed the pull request at:
https://github.com/apache/couchdb-chttpd/pull/41
---
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
enabled and wishes so, or if the feature
Github user rnewson commented on the pull request:
https://github.com/apache/couchdb-couch/pull/65#issuecomment-121051056
not sure this is the way to go.
---
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 doe
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-couch/pull/71#issuecomment-121048266
+1
Not sure how to test performance part for now. @robertkowalski do you have
anything to fire here?
---
If your project is set up for it, you can reply to th
[
https://issues.apache.org/jira/browse/COUCHDB-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625280#comment-14625280
]
ASF subversion and git services commented on COUCHDB-2749:
--
Com
Github user rnewson commented on the pull request:
https://github.com/apache/couchdb-couch/pull/70#issuecomment-121046243
moving the timestamp logic to mochiweb makes sense and you can therefore
legitimately use mochiglobal to store the state ;)
---
If your project is set up for it,
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-couch/pull/72#issuecomment-121038136
@rnewson can you add some context to the commit message so you don't have
to search the issue in jira to understand the issue when reading the git log?
Github user robertkowalski commented on the pull request:
https://github.com/apache/couchdb-couch/pull/72#issuecomment-121038289
it will also help us creating the next release log for 2.0 :)
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user wohali commented on a diff in the pull request:
https://github.com/apache/couchdb-couch/pull/69#discussion_r34503056
--- Diff: rebar.config.script ---
@@ -76,6 +77,9 @@ IcuDarwinEnv = [{"CFLAGS", "-DXP_UNIX
-I/usr/local/opt/icu4c/include"},
{"LDFLAG
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-couch/pull/72#issuecomment-121022690
+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 opened a pull request:
https://github.com/apache/couchdb-jiffy/pull/2
Sync with upstream
@davisp @rnewson
P.S. .travis needs in modification, but also in INFRA activation request. I
want first to collect all the other repos where travis may be used as we
Github user kxepal closed the pull request at:
https://github.com/apache/couchdb-jiffy/pull/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
enabled and wishes so, or if the feature is
[
https://issues.apache.org/jira/browse/COUCHDB-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625127#comment-14625127
]
ASF subversion and git services commented on COUCHDB-2749:
--
Com
[
https://issues.apache.org/jira/browse/COUCHDB-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625109#comment-14625109
]
ASF GitHub Bot commented on COUCHDB-2749:
-
GitHub user rnewson opened a pull req
GitHub user rnewson opened a pull request:
https://github.com/apache/couchdb-couch/pull/72
Erase async_open entry in failure case
COUCHDB-2749
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloudant/couchdb-couch 2749-couch_serve
Robert Newson created COUCHDB-2749:
--
Summary: keep couch_server process dictionary clean
Key: COUCHDB-2749
URL: https://issues.apache.org/jira/browse/COUCHDB-2749
Project: CouchDB
Issue Type
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-couch/pull/70#issuecomment-121000875
@janl Good point, agree with this. Would be also good if this improvement
will land into upstream.
---
If your project is set up for it, you can reply to this emai
[
https://issues.apache.org/jira/browse/COUCHDB-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624974#comment-14624974
]
ASF GitHub Bot commented on COUCHDB-2732:
-
GitHub user davisp opened a pull requ
GitHub user davisp opened a pull request:
https://github.com/apache/couchdb-couch/pull/71
Optimize couch_ejson_compare NIF
The old nif was allocating a set of collators that were reserved and
released by each scheduler thread. This coordination and the
accompanying mutex turn
[
https://issues.apache.org/jira/browse/COUCHDB-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624988#comment-14624988
]
Paul Joseph Davis commented on COUCHDB-2732:
When we saw this in testing my
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/70#issuecomment-120988170
Iâm in favour of this, but I think this should live in mochiweb, not
CouchDB.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user janl commented on the pull request:
https://github.com/apache/couchdb-mochiweb/pull/1#issuecomment-120987809
Are you planning to propose the change to mochiweb upstream as well?
(obviously not the same patch, but the same idea :)
---
If your project is set up for it, you
Robert Kowalski created COUCHDB-2748:
Summary: encoding problems with reserved chars
Key: COUCHDB-2748
URL: https://issues.apache.org/jira/browse/COUCHDB-2748
Project: CouchDB
Issue Type:
[
https://issues.apache.org/jira/browse/COUCHDB-2601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624714#comment-14624714
]
ASF GitHub Bot commented on COUCHDB-2601:
-
Github user robertkowalski closed the
Github user robertkowalski closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/474
---
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
enabled and wishes so, or if th
Github user rnewson commented on the pull request:
https://github.com/apache/couchdb-couch/pull/70#issuecomment-120935258
I'm still against adding this complexity for a 2% difference, I don't think
our attitude should be that we make things more complex than they already are
for very
Repository: couchdb-nmo
Updated Tags: refs/tags/1.0.0 [created] ce0ece724
Repository: couchdb-nano
Updated Tags: refs/tags/0.0.2 [created] 393a7bfd0
refs/tags/0.0.3 [created] 497ce5c5f
refs/tags/0.1.0 [created] a925f90d0
refs/tags/0.1.5 [created] 9fc57cc64
refs/tags/0.1.6 [created] 17d7f401b
refs/tags/0.1.7 [created] fce6eabda
refs/tags/0.1.8 [created] 8ef5f
36 matches
Mail list logo
