Github user janl closed the issue at:
https://github.com/apache/couchdb/issues/464
---
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 enabled
Github user janl commented on the issue:
https://github.com/apache/couchdb/issues/464
See http://docs.couchdb.org/en/2.0.0/maintenance/compaction.html for details
---
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
Github user janl commented on the issue:
https://github.com/apache/couchdb/pull/453
> It's both, but it seems the preferred way is to use the github repo's and
use gitbox as a fallback
There is no preferred way. Individual developers can pick either route.
Github user janl closed the pull request at:
https://github.com/apache/couchdb/pull/38
---
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
Github user janl closed the pull request at:
https://github.com/apache/couchdb/pull/376
---
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
Github user janl closed the pull request at:
https://github.com/apache/couchdb/pull/387
---
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
Github user janl closed the pull request at:
https://github.com/apache/couchdb/pull/406
---
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
Github user janl closed the issue at:
https://github.com/apache/couchdb/issues/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 enabled but
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/57#issuecomment-108573545
@robertkowalski keep this open please :)
---
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
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/57#issuecomment-108402056
Iâm sure we can find a way that adds flexibility (maybe just hand the
atoms/binaries to lager) and let it do all the formatting, while retaining the
speedup
Github user janl commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/33#issuecomment-106022822
@kxepal what @nolanlawson explained here:
https://github.com/apache/couchdb-chttpd/pull/33#issuecomment-98407533
---
If your project is set up for it, you can
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/52#issuecomment-105649460
merged, thank you! :)
---
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
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/52#issuecomment-105478189
There is no harm in explicitly adding the search path, Iâll get this
committed in a bit!
---
If your project is set up for it, you can reply to this email and
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/52#issuecomment-105253339
I donât see this breaking without this patch.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user janl commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/33#issuecomment-105253198
This seems to have to do with the *eventual* nature of a cluster :)
Now this is failing, a little later than the previous one
Github user janl commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/33#issuecomment-105252240
The referenced PR that broke PouchDB tests against CouchDB master have been
merged.
Running the PouchDB tests with the linked repos as @nolanlawson
Github user janl commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/33#issuecomment-95649095
In addition, I think once this lands and alleviate the most egregious
replication performance issues, we should all look at figuring out a completely
new endpoint
Github user janl commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92795169
@kxepal all I meant: I donât think these are blockers. We can always fix
them before, too. Sorry for being unclear :)
---
If your project is set up for it
Github user janl commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/32#issuecomment-92763845
FINALLY \o/
---
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
Github user janl commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92763742
Great work @mar-ia! Letâs get this merged and file issues for the
line-comments to fix soon after.
---
If your project is set up for it, you can reply to
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-91920174
@micah good findings, I keep chipping away at them. The extra `make`
leftovers should be gone with the latest commit.
Could you post the `install.mk` in the top
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-90247231
- Added `-l` (lowercase L) option to `./configure` to specify log dir.
- Cleaned up some internal stuff
- make `make install` and `make uninstall` work
---
If your
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-89735795
1. switched to puhsing commits for progress instead of rebasing into single
commit
2. added `version.mk` that includes version info variables
3. added `-` suffix if
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-89325135
@micah on `make uninstall` what is expected to happen with user-data that
was created by the package? Like databases that might still have important
data, are they
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-89320619
As for Autotools: weâve spent quite some time trying to get rid of them
as much as possible. I agree that the packaging bits are neat, but they also
are not trivial to
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-89315774
@micah new version, should do the right thing vis-a-vis `./configure &&
make distclean` and `make && make clean`.
To test this, I added:
-
ht
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/312#issuecomment-89296287
Iâd still be fine with getting rid of the THANKS file :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb-chttpd/pull/28#discussion_r26791206
--- Diff: src/chttpd_db.erl ---
@@ -93,7 +93,7 @@ handle_changes_req1(#httpd{}=Req, Db) ->
couch_stats:decrement_counter([couchdb, ht
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb-chttpd/pull/28#discussion_r26746285
--- Diff: src/chttpd_db.erl ---
@@ -93,7 +93,7 @@ handle_changes_req1(#httpd{}=Req, Db) ->
couch_stats:decrement_counter([couchdb, ht
Github user janl commented on the pull request:
https://github.com/apache/couchdb-snappy/pull/2#issuecomment-81632205
merged!
---
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
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/309#discussion_r26223044
--- Diff: rel/overlay/etc/default.ini ---
@@ -23,6 +23,7 @@ file_compression = snappy
; and/or more OS page cache hits, but they can also increase overall
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/309#discussion_r26203891
--- Diff: rel/overlay/etc/default.ini ---
@@ -23,6 +23,7 @@ file_compression = snappy
; and/or more OS page cache hits, but they can also increase overall
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/308#issuecomment-77425413
@robertkowalski feel free to commit these straight, no need for a PR :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user janl commented on the pull request:
https://github.com/apache/couchdb-fabric/pull/17#issuecomment-76628895
+1
can we check all other repos, too?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/38#issuecomment-76043327
@iilyak why would you need a different set of db names? what are you trying
to do there?
---
If your project is set up for it, you can reply to this email and have
Github user janl commented on the pull request:
https://github.com/apache/couchdb-admin/pull/2#issuecomment-76028018
yeah, feel free to just commit those
---
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
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/38#issuecomment-76022970
@iilyak for what reason? :) (sorry for being dense)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/38#issuecomment-76021117
I found the related ticket:
https://issues.apache.org/jira/browse/COUCHDB-2625 â It doesnât answer my
question though
---
If your project is set up for it, you
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/38#issuecomment-76020612
Iâd like to understand the underlying issue this is trying to solve,
first :)
---
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-couch/pull/37#issuecomment-76020970
Ah, found it, https://issues.apache.org/jira/browse/COUCHDB-2625 was
probably meant as a reference.
---
If your project is set up for it, you can reply to this email
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/37#issuecomment-76019963
how is this related to https://issues.apache.org/jira/browse/COUCHDB-2585?
---
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-couch/pull/38#issuecomment-76019644
Iâm with @kxepal: sceptical about the usefulness of letting the end user
define how to validate database names.
Iâm not sure what problem this solves. The
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-75797142
@micah good catch, this is an artefact of us using the same `Makefile` in
the git checkout and the release dir / tarball.
A few options:
- hack the current
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/305#discussion_r25244181
--- Diff: Dockerfile ---
@@ -18,6 +18,10 @@ RUN apt-get --no-install-recommends -y install \
libmozjs185-dev \
python
+# Install
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/305#discussion_r25244080
--- Diff: Dockerfile ---
@@ -18,6 +18,10 @@ RUN apt-get --no-install-recommends -y install \
libmozjs185-dev \
python
+# Install
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/305#discussion_r25243636
--- Diff: Dockerfile ---
@@ -18,6 +18,10 @@ RUN apt-get --no-install-recommends -y install \
libmozjs185-dev \
python
+# Install
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/305#discussion_r25176762
--- Diff: Dockerfile ---
@@ -18,6 +18,10 @@ RUN apt-get --no-install-recommends -y install \
libmozjs185-dev \
python
+# Install
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-75148247
Latest version builds THANKS file like we did in 1.x.x (itâs not quite
correct, but eh)
---
If your project is set up for it, you can reply to this email and have your
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-75145474
@sebastianrothbucher good catch, got that included now.
@micah The latest push here supports `make clean` before `./configure`,
this is more to unblock you and not
Github user janl commented on the pull request:
https://github.com/apache/couchdb-chttpd/pull/25#issuecomment-75138237
+1
---
If your project
Github user janl commented on the pull request:
https://github.com/apache/couchdb-snappy/pull/2#issuecomment-75084052
@bryanpkc I donât think Travis is gonna help with running anything but
their stock environment, but we have a Jenkins setup that we can use.
---
If your project is
Github user janl commented on the pull request:
https://github.com/apache/couchdb-snappy/pull/2#issuecomment-74919967
just a note that I think the CI test discussion here is **not** blocking
merging this in
---
If your project is set up for it, you can reply to this email and have
Github user janl commented on the pull request:
https://github.com/apache/couchdb-snappy/pull/2#issuecomment-74892552
we have some CI hardware, would qemu running there would help?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user janl commented on the pull request:
https://github.com/apache/couchdb-snappy/pull/2#issuecomment-74886312
@bryanpkc ongoing: whenever we make a release, run `make test` and report
here or on the dev@couchdb.apache.org mailing list :)
Ideally weâd have a big
Github user janl commented on the pull request:
https://github.com/apache/couchdb-snappy/pull/2#issuecomment-74883487
@kxepal yeah I imagine, and we probably donât want to re-shuffle the code
so you can inject endianness from the tests. Maybe we can have a test that only
runs on BE
Github user janl commented on the pull request:
https://github.com/apache/couchdb-snappy/pull/2#issuecomment-74868043
@bryanpkc nice one! Is there a way to add a test case for this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/302#issuecomment-73986953
I also have this patch for couchdb-couch/rebar.config.script so it runs
correctly in a non-git environment, but as far as I can tell right now, it is
not really needed. It
GitHub user janl opened a pull request:
https://github.com/apache/couchdb/pull/302
Add first stab at a release build script.
Creates a release directory `apache-couchdb` that we can wrap in a tarball.
This is a quick hack to discuss whether this direction is anything weâd like
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/301#issuecomment-73974932
+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
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/31#issuecomment-70517554
just a note that âthe operatorsâ, at least in the beginning, are
end-users as well, so we want to make this as friendly as possible.
---
If your project is set
Github user janl commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/126#issuecomment-66101782
@garrensmith as far as I can tell I have that covered:
https://github.com/apache/couchdb-fauxton/pull/126/files#diff-35b4a816e0441e6a375cd925af50752cR332
---
If
Github user janl commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/126#discussion_r21446085
--- Diff: Gruntfile.js ---
@@ -319,11 +319,11 @@ module.exports = function(grunt) {
couchdb: {
files: [
// this
Github user janl commented on the pull request:
https://github.com/apache/couchdb-fauxton/pull/126#issuecomment-66100567
@robertkowalski Where are the other occurrences of the old path?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/277#issuecomment-63142109
How reliable are travis build errors? 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
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/277#issuecomment-63099209
pushed a rebase to asf.
---
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
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/15#issuecomment-62447266
>> Maybe also send an x-couch-deprecation-notice header with an URL to the
docs where it is explained.
> We'd already discussed this moment: no
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch/pull/15#issuecomment-62443798
Can we please stop the meme of âwe are bumping the major version so
letâs break everything.â?
We should be **very** deliberate with what we break and
GitHub user janl opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/126
Goodbye Futon
Needs to be merged together with https://github.com/apache/couchdb/pull/277
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
GitHub user janl opened a pull request:
https://github.com/apache/couchdb/pull/277
Goodbye Futon
Needs to be merged with https://github.com/apache/couchdb-fauxton/pull/126
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch-log/pull/1#issuecomment-58817401
Closing this PR.
---
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
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch-log/pull/1#issuecomment-58817392
@rnewson thanks, I think these are enough pointers to work with! I want
this for myself and I hope it can be useful for others :)
---
If your project is set up
Github user janl closed the pull request at:
https://github.com/apache/couchdb-couch-log/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
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch-log/pull/1#issuecomment-58814450
@rnewson brilliant, you have clearly thought about this a lot more than I
have :)
On the `.gitconfig` thing, it would be a permanent local setup, right
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch-log/pull/1#issuecomment-58814096
@kxepal sure, but I donât know how to do this yet, so I donât want to
great all the PRs. Discussion first :)
---
If your project is set up for it, you can
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch-log/pull/1#issuecomment-58814080
@kx
---
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
GitHub user janl opened a pull request:
https://github.com/apache/couchdb-couch-log/pull/1
Make git clone base URL configurable to enable full offline builds.
This is a first stab. I tried using Rebar's deps_dir as per
https://github.com/rebar/rebar/wiki/Dynamic-configur
Github user janl commented on the pull request:
https://github.com/apache/couchdb-couch-dbupdates/pull/1#issuecomment-5868
That would be perfect :)
> On 10.10.2014, at 19:16, Alexander Shorin
wrote:
>
> Ok. Like "There is no actually handle_re
Github user janl commented on the pull request:
https://github.com/apache/couchdb/pull/30#issuecomment-35501641
should be trivial to find out whether this was merged.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. To do
Github user janl closed the pull request at:
https://github.com/apache/couchdb/pull/40
GitHub user janl opened a pull request:
https://github.com/apache/couchdb/pull/40
document number encoding
wrapping recent user@ discussion into the docs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/janl/couchdb document
80 matches
Mail list logo
