Github user iilyak commented on the issue:
https://github.com/apache/couchdb-couch/pull/198
@davisp: I did fix `_replicator` part of a PR.
> Isn't that obviously broken then? How would you ever match something with
'/' in it to filename:basename(Anything)?
basename is
[
https://issues.apache.org/jira/browse/COUCHDB-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491590#comment-15491590
]
Joan Touzet commented on COUCHDB-3147:
--
We should validate that we do the right thing here for
Joan Touzet created COUCHDB-3147:
Summary: uuid missing in clustered welcome response (GET /)
Key: COUCHDB-3147
URL: https://issues.apache.org/jira/browse/COUCHDB-3147
Project: CouchDB
Issue
Github user iilyak commented on the issue:
https://github.com/apache/couchdb-couch/pull/198
No it is not going to work because we set different set of callbacks for
_users and _replicator.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user davisp commented on the issue:
https://github.com/apache/couchdb-couch/pull/198
Also it occurs to me that the check for the replicator here is broken since
we hardcode that in couch_replicator_manager. We could be adding sys_db hooks
to something the manager isn't looking
Github user davisp commented on the issue:
https://github.com/apache/couchdb-couch/pull/198
Isn't that obviously broken then? How would you ever match something with
'/' in it to filename:basename(Anything)?
Is there an intent to make this different than _replicator databases
Github user iilyak commented on the issue:
https://github.com/apache/couchdb-couch/pull/198
`chttpd_auth.autentication_db = "/users"`
`couch_httpd_auth.authentication_db = "users"`
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user davisp commented on the issue:
https://github.com/apache/couchdb-couch/pull/198
Erm, what do we call it other than _users? And if we do, why do we do that?
---
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 iilyak commented on the issue:
https://github.com/apache/couchdb-couch/pull/198
> @davisp: who would want to have two different names for local vs
clustered?
Cloudant!
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user robertkowalski closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/773
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-fauxton/pull/774
---
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
Github user robertkowalski commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/774
+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,
Github user garrensmith commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/773
+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
Github user garrensmith commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/772
+1 once tests pass
---
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 garrensmith opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/774
remove sourcemaps in webpack
We don't use this functionality so its just creating an unnecessary request.
You can merge this pull request into a Git repository by running:
$ git
[
https://issues.apache.org/jira/browse/COUCHDB-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15490339#comment-15490339
]
Robert Kowalski commented on COUCHDB-3050:
--
also applies to the docker image we use now:
[ * ]
GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/773
backbone: delete dead code
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robertkowalski/couchdb-fauxton dead-modal-code
Github user robertkowalski commented on the issue:
https://github.com/apache/couchdb-fauxton/pull/772
i think we can remove the spinner. most pages are react now and for the
rest it doesn't matter much. also it removes some superfluous spinners
---
If your project is set up for it,
GitHub user robertkowalski opened a pull request:
https://github.com/apache/couchdb-fauxton/pull/772
remove spinner
all views except replication are react based now
yay! ð
You can merge this pull request into a Git repository by running:
$ git pull
Sergey Korobkov created COUCHDB-3146:
Summary: Incorrect URI for DB with slash in name
Key: COUCHDB-3146
URL: https://issues.apache.org/jira/browse/COUCHDB-3146
Project: CouchDB
Issue
20 matches
Mail list logo