[GitHub] couchdb-fauxton pull request #865: Permanent Notification Banner Plugin
GitHub user millayr opened a pull request: https://github.com/apache/couchdb-fauxton/pull/865 Permanent Notification Banner Plugin This PR gives us the option to dynamically set a notification banner across the top of fauxton. For example:  You can merge this pull request into a Git repository by running: $ git pull https://github.com/millayr/couchdb-fauxton perma-warning-header Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb-fauxton/pull/865.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #865 commit 7902254be9b4891682a5da4b20ef102a6b3eab4a Author: Ryan Millay Date: 2017-03-03T18:53:42Z initialize perma warning progress commit 0494e23060ce5e186b2f91f222a2b8396460b879 Author: Ryan Millay Date: 2017-03-03T20:28:50Z tweaking styling and layout commit 93119de9f3e20acee584b1a275132e8badb809db Author: Ryan Millay Date: 2017-03-03T20:46:18Z adding permanent notification test commit 9c61fda0b7e258b06b32c295ffa2596f08a64fd7 Author: Ryan Millay Date: 2017-03-03T20:47:56Z adding new line chars commit 273e85ce07b00e86e767b4130885d491dee59a2a Author: Ryan Millay Date: 2017-03-03T20:50:04Z cleaning test commit 84931845c98f5bebe927646dc72b2b5bfe4099c9 Author: Ryan Millay Date: 2017-03-03T20:51:20Z fixing identation to spaces --- 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 not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-fauxton pull request #859: fix replication source/target url
Github user nolanlawson closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/859 --- 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 not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3316) Log replicator db name not just doc ids
[ https://issues.apache.org/jira/browse/COUCHDB-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894624#comment-15894624 ] ASF subversion and git services commented on COUCHDB-3316: -- Commit 7ac71bf2a02323e07c5196428feecb18bbf774c5 in couchdb's branch refs/heads/master from [~vatamane] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=7ac71bf ] Bump replicator dependency: handle db deletion and improve logging. COUCHDB-3316 > Log replicator db name not just doc ids > --- > > Key: COUCHDB-3316 > URL: https://issues.apache.org/jira/browse/COUCHDB-3316 > Project: CouchDB > Issue Type: Improvement >Reporter: Nick Vatamaniuc > > Currently replicator logs only doc_id. However in 2.0 there could be more > than one _replicator db. So for logs to be useful it would be nice to log the > db as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3316) Log replicator db name not just doc ids
[ https://issues.apache.org/jira/browse/COUCHDB-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894599#comment-15894599 ] ASF GitHub Bot commented on COUCHDB-3316: - Github user asfgit closed the pull request at: https://github.com/apache/couchdb-couch-replicator/pull/59 > Log replicator db name not just doc ids > --- > > Key: COUCHDB-3316 > URL: https://issues.apache.org/jira/browse/COUCHDB-3316 > Project: CouchDB > Issue Type: Improvement >Reporter: Nick Vatamaniuc > > Currently replicator logs only doc_id. However in 2.0 there could be more > than one _replicator db. So for logs to be useful it would be nice to log the > db as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3316) Log replicator db name not just doc ids
[ https://issues.apache.org/jira/browse/COUCHDB-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894598#comment-15894598 ] ASF subversion and git services commented on COUCHDB-3316: -- Commit 50dcd7d7c5f7ce003e8e2fc84646c1aa9931ebaa in couchdb-couch-replicator's branch refs/heads/master from [~vatamane] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-couch-replicator.git;h=50dcd7d ] Make sure to log db as well as doc in replicator logs. COUCHDB-3316 > Log replicator db name not just doc ids > --- > > Key: COUCHDB-3316 > URL: https://issues.apache.org/jira/browse/COUCHDB-3316 > Project: CouchDB > Issue Type: Improvement >Reporter: Nick Vatamaniuc > > Currently replicator logs only doc_id. However in 2.0 there could be more > than one _replicator db. So for logs to be useful it would be nice to log the > db as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] couchdb-couch-replicator pull request #59: Make sure to log db as well as do...
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-couch-replicator/pull/59 --- 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 not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3316) Log replicator db name not just doc ids
[ https://issues.apache.org/jira/browse/COUCHDB-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894587#comment-15894587 ] ASF subversion and git services commented on COUCHDB-3316: -- Commit f0c612fd921dc22264872664940578d8f09baf68 in couchdb's branch refs/heads/master from [~vatamane] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=f0c612f ] Bump couch dependency. Fixes badarith error in get_db_info COUCHDB-3316 > Log replicator db name not just doc ids > --- > > Key: COUCHDB-3316 > URL: https://issues.apache.org/jira/browse/COUCHDB-3316 > Project: CouchDB > Issue Type: Improvement >Reporter: Nick Vatamaniuc > > Currently replicator logs only doc_id. However in 2.0 there could be more > than one _replicator db. So for logs to be useful it would be nice to log the > db as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] couchdb-couch pull request #231: Fix `badarith` error in couch_db:get_db_inf...
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-couch/pull/231 --- 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 not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-3316) Log replicator db name not just doc ids
[ https://issues.apache.org/jira/browse/COUCHDB-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894582#comment-15894582 ] ASF subversion and git services commented on COUCHDB-3316: -- Commit 63ef337475a266379c7208f52f827980e69d1d1b in couchdb-couch's branch refs/heads/master from [~vatamane] [ https://git-wip-us.apache.org/repos/asf?p=couchdb-couch.git;h=63ef337 ] Fix `badarith` error in couch_db:get_db_info call When folding we account for a previous `null`, `undefined`, or a number. However btree:size/1 returns 0, `nil` or a number. Switched `undefined` to `nil`. Couldn't find where btree:size would ever return `undefined`, it seems we meant to use `nil` instead. COUCHDB-3316 > Log replicator db name not just doc ids > --- > > Key: COUCHDB-3316 > URL: https://issues.apache.org/jira/browse/COUCHDB-3316 > Project: CouchDB > Issue Type: Improvement >Reporter: Nick Vatamaniuc > > Currently replicator logs only doc_id. However in 2.0 there could be more > than one _replicator db. So for logs to be useful it would be nice to log the > db as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3316) Log replicator db name not just doc ids
[ https://issues.apache.org/jira/browse/COUCHDB-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894583#comment-15894583 ] ASF GitHub Bot commented on COUCHDB-3316: - Github user asfgit closed the pull request at: https://github.com/apache/couchdb-couch/pull/231 > Log replicator db name not just doc ids > --- > > Key: COUCHDB-3316 > URL: https://issues.apache.org/jira/browse/COUCHDB-3316 > Project: CouchDB > Issue Type: Improvement >Reporter: Nick Vatamaniuc > > Currently replicator logs only doc_id. However in 2.0 there could be more > than one _replicator db. So for logs to be useful it would be nice to log the > db as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[GitHub] couchdb-couch-replicator issue #59: Make sure to log db as well as doc in re...
Github user davisp commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/59 +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 not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-couch issue #231: Fix `badarith` error in couch_db:get_db_info call
Github user davisp commented on the issue: https://github.com/apache/couchdb-couch/pull/231 +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 not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb-couch issue #231: Fix `badarith` error in couch_db:get_db_info call
Github user rnewson commented on the issue: https://github.com/apache/couchdb-couch/pull/231 +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 not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
