couchdb-ci git commit: Fix ansible yum Centos package group install
Repository: couchdb-ci
Updated Branches:
refs/heads/master 69285ff19 -> 30055eb24
Fix ansible yum Centos package group install
Project: http://git-wip-us.apache.org/repos/asf/couchdb-ci/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-ci/commit/30055eb2
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-ci/tree/30055eb2
Diff: http://git-wip-us.apache.org/repos/asf/couchdb-ci/diff/30055eb2
Branch: refs/heads/master
Commit: 30055eb24384baac7d11993421cd3d7d3b150268
Parents: 69285ff
Author: Joan Touzet
Authored: Thu Mar 16 00:18:21 2017 -0700
Committer: Joan Touzet
Committed: Thu Mar 16 00:18:21 2017 -0700
--
ansible/roles/dependencies-centos/tasks/main.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/30055eb2/ansible/roles/dependencies-centos/tasks/main.yml
--
diff --git a/ansible/roles/dependencies-centos/tasks/main.yml
b/ansible/roles/dependencies-centos/tasks/main.yml
index 71a29d3..02ad98b 100644
--- a/ansible/roles/dependencies-centos/tasks/main.yml
+++ b/ansible/roles/dependencies-centos/tasks/main.yml
@@ -18,7 +18,7 @@
- name: install auxiliary packages
yum: name={{item}} state=present update_cache=yes
with_items:
- - '"@Development tools"'
+ - "@Development tools"
- git
- wget
- which
[jira] [Commented] (COUCHDB-2386) Cant undelete documents in master while passing _rev
[ https://issues.apache.org/jira/browse/COUCHDB-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927870#comment-15927870 ] Will Holley commented on COUCHDB-2386: -- I think this means there is no way to update a deleted document in 2.x except to undelete it. > Cant undelete documents in master while passing _rev > > > Key: COUCHDB-2386 > URL: https://issues.apache.org/jira/browse/COUCHDB-2386 > Project: CouchDB > Issue Type: Bug > Components: Database Core >Reporter: Dale Harvey > > Basic commands to reproduce > https://gist.github.com/daleharvey/cd5f058b20e92b52d80c > There was a bug tracking this fix in previous versions of Couch, was > reintroduced with the cluster merge > https://issues.apache.org/jira/browse/COUCHDB-292 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3224) Fauxton not correctly display database with "-" and "/" symbol in name
[ https://issues.apache.org/jira/browse/COUCHDB-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927946#comment-15927946 ] ASF GitHub Bot commented on COUCHDB-3224: - Github user garrensmith commented on the issue: https://github.com/apache/couchdb-fauxton/pull/802 @sergey-safarov seems it was a travis issue. Could you fix the lint issues and try again. > Fauxton not correctly display database with "-" and "/" symbol in name > -- > > Key: COUCHDB-3224 > URL: https://issues.apache.org/jira/browse/COUCHDB-3224 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Sergey Safarov > > Fauxton cannot display database with "-" symbol in name and cannot display > view with "/" simbol in database name. > Tu reproduce execute "curl -X PUT > http://127.0.0.1:5984/mytest%2Fdata%2Fbase-201609"; ant try open this database > via fauxton. > Also if you create view for this database then this view wont work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3224) Fauxton not correctly display database with "-" and "/" symbol in name
[
https://issues.apache.org/jira/browse/COUCHDB-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927953#comment-15927953
]
ASF GitHub Bot commented on COUCHDB-3224:
-
Github user garrensmith commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/802#discussion_r106408073
--- Diff: app/addons/databases/actions.js ---
@@ -176,7 +176,7 @@ export default {
databaseName = databaseName.trim();
-const url = FauxtonAPI.urls('allDocs', 'app',
app.utils.safeURLName(databaseName), '');
+const url = FauxtonAPI.urls('allDocs', 'app',
encodeURIComponent(databaseName), '');
--- End diff --
Same as aboce it seems its better to use `allDocsSantized` then you don't
need to encodeURIComponent
> Fauxton not correctly display database with "-" and "/" symbol in name
> --
>
> Key: COUCHDB-3224
> URL: https://issues.apache.org/jira/browse/COUCHDB-3224
> Project: CouchDB
> Issue Type: Bug
> Components: Fauxton
>Reporter: Sergey Safarov
>
> Fauxton cannot display database with "-" symbol in name and cannot display
> view with "/" simbol in database name.
> Tu reproduce execute "curl -X PUT
> http://127.0.0.1:5984/mytest%2Fdata%2Fbase-201609"; ant try open this database
> via fauxton.
> Also if you create view for this database then this view wont work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-3224) Fauxton not correctly display database with "-" and "/" symbol in name
[
https://issues.apache.org/jira/browse/COUCHDB-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927954#comment-15927954
]
ASF GitHub Bot commented on COUCHDB-3224:
-
Github user garrensmith commented on a diff in the pull request:
https://github.com/apache/couchdb-fauxton/pull/802#discussion_r106408017
--- Diff: app/addons/databases/actions.js ---
@@ -155,7 +155,7 @@ export default {
type: 'success',
clear: true
});
-var route = FauxtonAPI.urls('allDocs', 'app',
app.utils.safeURLName(databaseName), '?limit=' + Resources.DocLimit);
+var route = FauxtonAPI.urls('allDocs', 'app',
encodeURIComponent(databaseName), '?limit=' + Resources.DocLimit);
--- End diff --
Could you rather use this function
https://github.com/apache/couchdb-fauxton/blob/master/app/addons/documents/base.js#L40
and then you don't need to encodeURIComponent
> Fauxton not correctly display database with "-" and "/" symbol in name
> --
>
> Key: COUCHDB-3224
> URL: https://issues.apache.org/jira/browse/COUCHDB-3224
> Project: CouchDB
> Issue Type: Bug
> Components: Fauxton
>Reporter: Sergey Safarov
>
> Fauxton cannot display database with "-" symbol in name and cannot display
> view with "/" simbol in database name.
> Tu reproduce execute "curl -X PUT
> http://127.0.0.1:5984/mytest%2Fdata%2Fbase-201609"; ant try open this database
> via fauxton.
> Also if you create view for this database then this view wont work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (COUCHDB-2799) Feedback/Idea: User experience improvement if Docs opened inside Fauxton iFrame
[ https://issues.apache.org/jira/browse/COUCHDB-2799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2799. - Resolution: Won't Fix I don't see how this could be useful. > Feedback/Idea: User experience improvement if Docs opened inside Fauxton > iFrame > > > Key: COUCHDB-2799 > URL: https://issues.apache.org/jira/browse/COUCHDB-2799 > Project: CouchDB > Issue Type: Wish > Components: Fauxton >Reporter: Tony OHagan > > IMHO ... I think the user experience would be improved if selecting Documents > opened the http://localhost:8000/_utils/docs/intro/api.html as part of the > same interface (inside the iFrame) rather than starting a new browser TAB as > you're now forced to navigate back to the original Fauxton TAB. > A Documents expandable submenu in the Fauxton could also link to the major > document headings. > Pros: > - Faster and less disruptive UX / Navigation > Cons: > - User needs a wide screen to view the docs as they are now pushed further > to the right. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-2108) Group databases with / char
[ https://issues.apache.org/jira/browse/COUCHDB-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927984#comment-15927984 ] ASF GitHub Bot commented on COUCHDB-2108: - GitHub user garrensmith opened an issue: https://github.com/apache/couchdb-fauxton/issues/869 Group databases with / char Currently databases with / char in name showed as flat list. While it's ok, but the main trick of having this char in db name is to group the databases on filesystem. It would be awesome if Fauxton will also group them in UI, providing fold/unfold buttons. Taken from https://issues.apache.org/jira/browse/COUCHDB-2108 > Group databases with / char > --- > > Key: COUCHDB-2108 > URL: https://issues.apache.org/jira/browse/COUCHDB-2108 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: Alexander Shorin > Labels: advanced > > Currently databases with / char in name showed as flat list. While it's ok, > but the main trick of having this char in db name is to group the databases > on filesystem. It would be awesome if Fauxton will also group them in UI, > providing fold/unfold buttons. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2108) Group databases with / char
[ https://issues.apache.org/jira/browse/COUCHDB-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2108. - Resolution: Duplicate Moved to here https://github.com/apache/couchdb-fauxton/issues/869 > Group databases with / char > --- > > Key: COUCHDB-2108 > URL: https://issues.apache.org/jira/browse/COUCHDB-2108 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: Alexander Shorin > Labels: advanced > > Currently databases with / char in name showed as flat list. While it's ok, > but the main trick of having this char in db name is to group the databases > on filesystem. It would be awesome if Fauxton will also group them in UI, > providing fold/unfold buttons. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-2586) Problem scrolling to end of a long line in Ace editor
[ https://issues.apache.org/jira/browse/COUCHDB-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927988#comment-15927988 ] ASF GitHub Bot commented on COUCHDB-2586: - GitHub user garrensmith opened an issue: https://github.com/apache/couchdb-fauxton/issues/870 Problem scrolling to end of a long line in Ace editor There's a bug with the Ace editor configuration (full page + elsewhere) where if you have a single very long line of text - long enough to make the horizontal scrollbar appear, you can't scroll to the very end of the line. This occurs in all browsers. It looks like the editor is failing to take into account the width of the vertical scrollbar, so the final 1 or 2 characters get hidden. I spent some time investigating this thinking it was our bug, but it turns out to be a bug with Ace itself. I've opened a ticket here: https://github.com/ajaxorg/ace/issues/2360 Taken from https://issues.apache.org/jira/browse/COUCHDB-2586 > Problem scrolling to end of a long line in Ace editor > - > > Key: COUCHDB-2586 > URL: https://issues.apache.org/jira/browse/COUCHDB-2586 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Ben Keen >Assignee: Ben Keen > > There's a bug with the Ace editor configuration (full page + elsewhere) where > if you have a single very long line of text - long enough to make the > horizontal scrollbar appear, you can't scroll to the very end of the line. > This occurs in all browsers. It looks like the editor is failing to take into > account the width of the vertical scrollbar, so the final 1 or 2 characters > get hidden. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2392) afterRender is called twice
[ https://issues.apache.org/jira/browse/COUCHDB-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2392. - Resolution: Fixed > afterRender is called twice > --- > > Key: COUCHDB-2392 > URL: https://issues.apache.org/jira/browse/COUCHDB-2392 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Robert Kowalski >Assignee: Ben Keen > > afterRender is called twice - I thought Garren fixed it some time ago, but it > seems to happen again. > see: > https://github.com/apache/couchdb-fauxton/commit/332c7b5350a928e35006e821f1f8bf9b6b748c12#diff-4a170929e0ed75614fc691eaa2dac8b9R37 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2586) Problem scrolling to end of a long line in Ace editor
[ https://issues.apache.org/jira/browse/COUCHDB-2586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2586. - Resolution: Fixed Moved to https://github.com/apache/couchdb-fauxton/issues/870 > Problem scrolling to end of a long line in Ace editor > - > > Key: COUCHDB-2586 > URL: https://issues.apache.org/jira/browse/COUCHDB-2586 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Ben Keen >Assignee: Ben Keen > > There's a bug with the Ace editor configuration (full page + elsewhere) where > if you have a single very long line of text - long enough to make the > horizontal scrollbar appear, you can't scroll to the very end of the line. > This occurs in all browsers. It looks like the editor is failing to take into > account the width of the vertical scrollbar, so the final 1 or 2 characters > get hidden. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2711) Add View -> Back btn bug
[ https://issues.apache.org/jira/browse/COUCHDB-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2711. - Resolution: Fixed I can't reproduce this anymore. > Add View -> Back btn bug > > > Key: COUCHDB-2711 > URL: https://issues.apache.org/jira/browse/COUCHDB-2711 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Ben Keen > > - Create a new View & click save > - Click back. It takes you to the Create View page again. > - Click back again. It should take you to where you came from, not the edit > view page. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-2757) Copied & pasted string with newlines should show JSON syntax error in Ace editors
[ https://issues.apache.org/jira/browse/COUCHDB-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928056#comment-15928056 ] ASF GitHub Bot commented on COUCHDB-2757: - GitHub user garrensmith opened an issue: https://github.com/apache/couchdb-fauxton/issues/871 Copied & pasted string with newlines should show JSON syntax error in Ace editors Copying & pasting in text with newlines into a string in the full page doc editor (and probably any Ace editor field) should show an error icon in the gutter, but it doesn't. Taken from https://issues.apache.org/jira/browse/COUCHDB-2757 > Copied & pasted string with newlines should show JSON syntax error in Ace > editors > - > > Key: COUCHDB-2757 > URL: https://issues.apache.org/jira/browse/COUCHDB-2757 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Ben Keen >Assignee: Ben Keen > > Copying & pasting in text with newlines into a string in the full page doc > editor (and probably any Ace editor field) should show an error icon in the > gutter, but it doesn't. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2977) JavaScript and CSS files for fauxton can not be found
[ https://issues.apache.org/jira/browse/COUCHDB-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2977. - Resolution: Cannot Reproduce > JavaScript and CSS files for fauxton can not be found > - > > Key: COUCHDB-2977 > URL: https://issues.apache.org/jira/browse/COUCHDB-2977 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Patrick Palacin >Assignee: Garren Smith > > Hi folks, > i followed these guide: > https://docs.google.com/document/d/1BtndYr-0KDQTqBSLVdJoR_8C5ObYjT1RBo_Qyh5ykdQ/edit# > installing as single node setup on latest alpha (15.3) . When i try now to > open _utils I get a blank page. Firefox devtools are showing: > "NetworkError: 404 Object Not Found - > http://159.122.91.165:5984/_utils/dashboard.assets/js/require-c9def4126d9d299af5b771713151534f.js"; > require...534f.js > "NetworkError: 404 Object Not Found - > http://159.122.91.165:5984/_utils/dashboard.assets/css/index-6772bc2fbb800cb971b29ad7f561.css"; > I am running on Ubuntu 16.04 LTS and installed all dependencies from the > standard repository. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (COUCHDB-2109) Show amount of wasted space in db list
[
https://issues.apache.org/jira/browse/COUCHDB-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith resolved COUCHDB-2109.
---
Resolution: Fixed
This is fixed
> Show amount of wasted space in db list
> --
>
> Key: COUCHDB-2109
> URL: https://issues.apache.org/jira/browse/COUCHDB-2109
> Project: CouchDB
> Issue Type: Improvement
> Components: Fauxton
>Reporter: Alexander Shorin
> Labels: intermediate
>
> Currently Fauxton, as like as Futon, shows only {{data_size}} value. This
> value could stay roughly the same forever, while {{disk_size}} will grow
> bigger. If Fauxton will provide amount of space that could be recovered by
> compaction operation - that would be extremely helpful for db administrations
> (and those people who didn't setup any monitoring around).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-2120) Navigate to the user's document
[ https://issues.apache.org/jira/browse/COUCHDB-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928071#comment-15928071 ] ASF GitHub Bot commented on COUCHDB-2120: - GitHub user garrensmith opened an issue: https://github.com/apache/couchdb-fauxton/issues/873 Navigate to the user's document Futon doesn't allows this, but this would be extremely useful if by clicking on username on sidebar while user is logged in to quickly navigate to the document in auth db that belongs to that user. Some kind of profile feature. Taken from https://issues.apache.org/jira/browse/COUCHDB-2120 > Navigate to the user's document > --- > > Key: COUCHDB-2120 > URL: https://issues.apache.org/jira/browse/COUCHDB-2120 > Project: CouchDB > Issue Type: New Feature > Components: Fauxton >Reporter: Alexander Shorin > > Futon doesn't allows this, but this would be extremely useful if by clicking > on username on sidebar while user is logged in to quickly navigate to the > document in auth db that belongs to that user. Some kind of profile feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2120) Navigate to the user's document
[ https://issues.apache.org/jira/browse/COUCHDB-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2120. - Resolution: Fixed https://github.com/apache/couchdb-fauxton/issues/873 > Navigate to the user's document > --- > > Key: COUCHDB-2120 > URL: https://issues.apache.org/jira/browse/COUCHDB-2120 > Project: CouchDB > Issue Type: New Feature > Components: Fauxton >Reporter: Alexander Shorin > > Futon doesn't allows this, but this would be extremely useful if by clicking > on username on sidebar while user is logged in to quickly navigate to the > document in auth db that belongs to that user. Some kind of profile feature. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2757) Copied & pasted string with newlines should show JSON syntax error in Ace editors
[ https://issues.apache.org/jira/browse/COUCHDB-2757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2757. - Resolution: Fixed moved to https://github.com/apache/couchdb-fauxton/issues/871 > Copied & pasted string with newlines should show JSON syntax error in Ace > editors > - > > Key: COUCHDB-2757 > URL: https://issues.apache.org/jira/browse/COUCHDB-2757 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Ben Keen >Assignee: Ben Keen > > Copying & pasting in text with newlines into a string in the full page doc > editor (and probably any Ace editor field) should show an error icon in the > gutter, but it doesn't. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2272) Reorginize docs sidebar items
[ https://issues.apache.org/jira/browse/COUCHDB-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2272. - Resolution: Fixed This will be fixed with the new UX design. We are planning to move away from the sidebar > Reorginize docs sidebar items > - > > Key: COUCHDB-2272 > URL: https://issues.apache.org/jira/browse/COUCHDB-2272 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: Alexander Shorin > > The "Create New Doc" and "Create New Index" are more common operations, but > it doesn't oblivious to figure out where they are on the new sidebar. In the > same time the rare operations like Compaction and Permissions are on top > while you wouldn't use them too much. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (COUCHDB-2144) Improve checkboxes on Replication page
[ https://issues.apache.org/jira/browse/COUCHDB-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2144. --- Resolution: Fixed New replication section fixes this > Improve checkboxes on Replication page > -- > > Key: COUCHDB-2144 > URL: https://issues.apache.org/jira/browse/COUCHDB-2144 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: Alexander Shorin > > They are really looks awkward and alien for the rest design. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3139) Single Node Setup on Fauxton forces non-127.0.0.1 IP
[ https://issues.apache.org/jira/browse/COUCHDB-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928084#comment-15928084 ] ASF GitHub Bot commented on COUCHDB-3139: - GitHub user garrensmith opened an issue: https://github.com/apache/couchdb-fauxton/issues/874 Single Node Setup on Fauxton forces non-127.0.0.1 IP Single node setups might just want to bind to 127.0.0.1, this could be fore security on the db server, or on a dev machine. Currently, the setup wizard for the single-node case forces an ip address other than 127.0.0.1, we should not do that Taken from https://issues.apache.org/jira/browse/COUCHDB-3139 > Single Node Setup on Fauxton forces non-127.0.0.1 IP > > > Key: COUCHDB-3139 > URL: https://issues.apache.org/jira/browse/COUCHDB-3139 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Jan Lehnardt > > Single node setups might just want to bind to 127.0.0.1, this could be fore > security on the db server, or on a dev machine. > Currently, the setup wizard for the single-node case forces an ip address > other than 127.0.0.1, we should not do that :) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-3139) Single Node Setup on Fauxton forces non-127.0.0.1 IP
[ https://issues.apache.org/jira/browse/COUCHDB-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-3139. - Resolution: Fixed Moved to https://github.com/apache/couchdb-fauxton/issues/874 > Single Node Setup on Fauxton forces non-127.0.0.1 IP > > > Key: COUCHDB-3139 > URL: https://issues.apache.org/jira/browse/COUCHDB-3139 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Jan Lehnardt > > Single node setups might just want to bind to 127.0.0.1, this could be fore > security on the db server, or on a dev machine. > Currently, the setup wizard for the single-node case forces an ip address > other than 127.0.0.1, we should not do that :) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2276) All Docs & index UX & design improvements
[ https://issues.apache.org/jira/browse/COUCHDB-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2276. - Resolution: Fixed > All Docs & index UX & design improvements > - > > Key: COUCHDB-2276 > URL: https://issues.apache.org/jira/browse/COUCHDB-2276 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: Sue Lockwood >Assignee: Jenn Schiffer > > We are improving the UX for indexes and the all docs section and it involves > a lot of css clean up. > I'm making this ticket so we can keep track of PRs made for these updates > that may not deserve their own ticket. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2786) Invalid map/reduce functions do not show an error to the user
[
https://issues.apache.org/jira/browse/COUCHDB-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith closed COUCHDB-2786.
-
Resolution: Fixed
moved to https://github.com/apache/couchdb-fauxton/issues/872
> Invalid map/reduce functions do not show an error to the user
> -
>
> Key: COUCHDB-2786
> URL: https://issues.apache.org/jira/browse/COUCHDB-2786
> Project: CouchDB
> Issue Type: Bug
> Components: Fauxton
>Reporter: Robert Kowalski
>
> Click: "Create view"
> as the map function put in valid javascript, but without the "function
> wrapper" from CouchDB:
> eg.
> if (doc.latin_name) {
> emit(doc.latin_name, doc.latin_name.length);
> }
> Couch returns
> {"error":"compilation_error","reason":"Compilation of the map function in the
> 'latin_name_jssum' view failed: Expression does not eval to a function. (\n
> if(doc.latin_name){\nemit(doc.latin_name, doc.latin_name.length);\n
> }\n)"}
> but Fauxton does not show an error and the button is not pressable any more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (COUCHDB-2909) cannot read property 'contents' of udnefined, while compiling Couch 2.0
[
https://issues.apache.org/jira/browse/COUCHDB-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Garren Smith closed COUCHDB-2909.
-
Resolution: Fixed
> cannot read property 'contents' of udnefined, while compiling Couch 2.0
>
>
> Key: COUCHDB-2909
> URL: https://issues.apache.org/jira/browse/COUCHDB-2909
> Project: CouchDB
> Issue Type: Bug
> Components: Fauxton
>Reporter: Billy Earney
>
> I'm trying to compile couchdb 2.0 on ubuntu 14.04.
> I have cloned the couchdb 2.0 git repo, and have installed the required libs,
> and tried compiling couchdb and get the following error after some time
> compiling:
> .
> .
> built Module("verifyinstall/components.react")
> built Module("verifyinstall/tests/componentsSpec.react")
> ["activetasks/components.react","activetasks/tests/activetasks.componentsSpec.react","auth/components.react","auth/test/auth.componentsSpec.react","cluster/cluster.react","cluster/tests/clusterSpec.react","compaction/components.react","compaction/tests/componentsSpec.react","components/react-components.react","components/tests/beautifySpec.react","components/tests/codeEditorPanelSpec.react","components/tests/codeEditorSpec.react","components/tests/confirmButtonSpec.react","components/tests/docSpec.react","components/tests/headerTogglebuttonSpec.react","components/tests/paddedBorderedBoxSpec.react","components/tests/stringEditModalSpec.react","components/tests/styledSelectSpec.react","components/tests/zenModeSpec.react","cors/components.react","cors/tests/componentsSpec.react","databases/components.react","databases/tests/componentsSpec.react","documents/changes/components.react","documents/changes/tests/changes.componentsSpec.react","documents/designdocinfo/components.react","documents/doc-editor/components.react","documents/doc-editor/tests/doc-editor.componentsSpec.react","documents/header/header.react","documents/header/tests/headerSpec.react","documents/index-editor/components.react","documents/index-editor/tests/viewIndex.componentsSpec.react","documents/index-results/index-results.components.react","documents/index-results/tests/index-results.componentsSpec.react","documents/mango/mango.components.react","documents/mango/tests/mango.componentsSpec.react","documents/pagination/pagination.react","documents/pagination/tests/pagination.componentSpec.react","documents/queryoptions/queryoptions.react","documents/queryoptions/tests/queryoptions.componentsSpec.react","documents/sidebar/sidebar.react","fauxton/components.react","fauxton/navigation/components.react","fauxton/navigation/tests/componentsSpec.react","fauxton/tests/componentsSpec.react","permissions/components.react","permissions/tests/componentsSpec.react","verifyinstall/components.react","verifyinstall/tests/componentsSpec.react"]
> Running "less:compile" (less) task
> Warning: Cannot read property 'contents' of undefined Use --force to continue.
> Aborted due to warnings.
> npm ERR! weird error 3
> npm WARN This failure might be due to the use of legacy binary "node"
> npm WARN For further explanations, please read
> /usr/share/doc/nodejs/README.Debian
>
> npm ERR! not ok code 0
> make: *** [share/www] Error 1
> Any ideas why I maybe getting this error?
> Thanks!
> billy
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-3045) replace safeURLName in code
[ https://issues.apache.org/jira/browse/COUCHDB-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928091#comment-15928091 ] ASF GitHub Bot commented on COUCHDB-3045: - GitHub user garrensmith opened an issue: https://github.com/apache/couchdb-fauxton/issues/875 replace safeURLName in code We have a still some usages of safeURLName where we manually slice of the _design prefix for design docs. Later we glue the prefix on again. We have a helper function that handles that already, which is also available in the utils.js file. Task: find appearances of safeURLName with code search, understand how it is used, remove custom safeURLName shenanigans with their design doc handling and replace it with other helper function. Good beginner task to get your toes wet with our codebase. Taken from https://issues.apache.org/jira/browse/COUCHDB-3045 > replace safeURLName in code > --- > > Key: COUCHDB-3045 > URL: https://issues.apache.org/jira/browse/COUCHDB-3045 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Robert Kowalski >Assignee: Ryan Millay > Labels: beginner > > We have a still some usages of safeURLName where we manually slice of the > _design prefix for design docs. Later we glue the prefix on again. We have a > helper function that handles that already, which is also available in the > utils.js file. > Task: find appearances of safeURLName with code search, understand how it is > used, remove custom safeURLName shenanigans with their design doc handling > and replace it with other helper function. > Good beginner task to get your toes wet with our codebase. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-3045) replace safeURLName in code
[ https://issues.apache.org/jira/browse/COUCHDB-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-3045. - Resolution: Fixed Moved to https://github.com/apache/couchdb-fauxton/issues/875 > replace safeURLName in code > --- > > Key: COUCHDB-3045 > URL: https://issues.apache.org/jira/browse/COUCHDB-3045 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Robert Kowalski >Assignee: Ryan Millay > Labels: beginner > > We have a still some usages of safeURLName where we manually slice of the > _design prefix for design docs. Later we glue the prefix on again. We have a > helper function that handles that already, which is also available in the > utils.js file. > Task: find appearances of safeURLName with code search, understand how it is > used, remove custom safeURLName shenanigans with their design doc handling > and replace it with other helper function. > Good beginner task to get your toes wet with our codebase. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-3192) Remove ZeroClipboard and replace it with pure JS
[ https://issues.apache.org/jira/browse/COUCHDB-3192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-3192. - Resolution: Fixed > Remove ZeroClipboard and replace it with pure JS > > > Key: COUCHDB-3192 > URL: https://issues.apache.org/jira/browse/COUCHDB-3192 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Robert Kowalski >Assignee: Ryan Millay > > As Safari now supports accessing the clipboard using JS we can throw out the > old Flash based zeroclipboard. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-2565) Responsive Fauxton
[ https://issues.apache.org/jira/browse/COUCHDB-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-2565. - Resolution: Fixed Moved to https://github.com/apache/couchdb-fauxton/issues/876 > Responsive Fauxton > -- > > Key: COUCHDB-2565 > URL: https://issues.apache.org/jira/browse/COUCHDB-2565 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: Robert Kowalski > Attachments: after.png, before.png > > > For a full responsive Fauxton I think we would need: > - throw out the current not maintained Bootstrap 2 which is mainly just used > for button styling at the moment > - make use of an actively maintained bootstrap and use it's helper to create > responsive grids > Some good points from [~michellep]: > Suggestions: > 1. We could collapse the left most nav when the screen is below a certain > width. > 2. Also maybe when the width gets really small, collapse the api url/ add new > database/ search buttons down to icon-only (like in buttons the code editor). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (COUCHDB-3056) Added Fauxton noscript element
[ https://issues.apache.org/jira/browse/COUCHDB-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith closed COUCHDB-3056. - Resolution: Fixed > Added Fauxton noscript element > -- > > Key: COUCHDB-3056 > URL: https://issues.apache.org/jira/browse/COUCHDB-3056 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: ali norouzi >Priority: Trivial > Labels: ui > > Fauxton need to a `noscript` warning. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-2565) Responsive Fauxton
[ https://issues.apache.org/jira/browse/COUCHDB-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928127#comment-15928127 ] ASF GitHub Bot commented on COUCHDB-2565: - GitHub user garrensmith opened an issue: https://github.com/apache/couchdb-fauxton/issues/876 More responsive Fauxton For a full responsive Fauxton I think we would need: throw out the current not maintained Bootstrap 2 which is mainly just used for button styling at the moment make use of an actively maintained bootstrap and use it's helper to create responsive grids Some good points from @michellephung Suggestions: 1. We could collapse the left most nav when the screen is below a certain width. 2. Also maybe when the width gets really small, collapse the api url/ add new database/ search buttons down to icon-only (like in buttons the code editor). Taken from https://issues.apache.org/jira/browse/COUCHDB-2565 > Responsive Fauxton > -- > > Key: COUCHDB-2565 > URL: https://issues.apache.org/jira/browse/COUCHDB-2565 > Project: CouchDB > Issue Type: Improvement > Components: Fauxton >Reporter: Robert Kowalski > Attachments: after.png, before.png > > > For a full responsive Fauxton I think we would need: > - throw out the current not maintained Bootstrap 2 which is mainly just used > for button styling at the moment > - make use of an actively maintained bootstrap and use it's helper to create > responsive grids > Some good points from [~michellep]: > Suggestions: > 1. We could collapse the left most nav when the screen is below a certain > width. > 2. Also maybe when the width gets really small, collapse the api url/ add new > database/ search buttons down to icon-only (like in buttons the code editor). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3224) Fauxton not correctly display database with "-" and "/" symbol in name
[ https://issues.apache.org/jira/browse/COUCHDB-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928146#comment-15928146 ] ASF GitHub Bot commented on COUCHDB-3224: - Github user sergey-safarov commented on the issue: https://github.com/apache/couchdb-fauxton/pull/802 @garrensmith I updated PR but exist two issues: 1) tests is looped 2) two tests is failed. I can revert back last changes. > Fauxton not correctly display database with "-" and "/" symbol in name > -- > > Key: COUCHDB-3224 > URL: https://issues.apache.org/jira/browse/COUCHDB-3224 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Sergey Safarov > > Fauxton cannot display database with "-" symbol in name and cannot display > view with "/" simbol in database name. > Tu reproduce execute "curl -X PUT > http://127.0.0.1:5984/mytest%2Fdata%2Fbase-201609"; ant try open this database > via fauxton. > Also if you create view for this database then this view wont work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3224) Fauxton not correctly display database with "-" and "/" symbol in name
[ https://issues.apache.org/jira/browse/COUCHDB-3224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928151#comment-15928151 ] ASF GitHub Bot commented on COUCHDB-3224: - Github user garrensmith commented on the issue: https://github.com/apache/couchdb-fauxton/pull/802 @sergey-safarov I will take a look next week. The PR has quite wide reaching effects. So I need to take a look at it. Leave it as is for now. > Fauxton not correctly display database with "-" and "/" symbol in name > -- > > Key: COUCHDB-3224 > URL: https://issues.apache.org/jira/browse/COUCHDB-3224 > Project: CouchDB > Issue Type: Bug > Components: Fauxton >Reporter: Sergey Safarov > > Fauxton cannot display database with "-" symbol in name and cannot display > view with "/" simbol in database name. > Tu reproduce execute "curl -X PUT > http://127.0.0.1:5984/mytest%2Fdata%2Fbase-201609"; ant try open this database > via fauxton. > Also if you create view for this database then this view wont work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (COUCHDB-3314) Add an option in doc creation APIs to specify a random value for an initial doc revision
[
https://issues.apache.org/jira/browse/COUCHDB-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928227#comment-15928227
]
Jan Lehnardt commented on COUCHDB-3314:
---
This is cool stuff. My comment applies to both this and COUCHDB-3315.
1. the use-case we are trying to preserve here (create doc X on db A and db B
and not have a conflict when A and B replicate.) is _very_ rare. Deterministic
revisions are mostly relevant on later revs (especially on mobile/PouchDB sync).
2. I’m totally comfortable with billing 3.0 features as: we are trading
permanent deletes and cluster purge for the rare use-case of deterministic
initial revisions.
3. I’m less confident with adding a switch that will force users into trouble
past the point where they can do anything about it (e.g. you can’t purge
because you didn’t 0-…-create a year ago).
4. it’d be nice if we can keep an escape hatch open that would be in line with
existing semantics, I’m imagining a 2-ABC… _rev with new_edits=false, that
could create an initial doc rev with a deterministic revision. ([~rnewson]
tells me this is currently broken, but would be worth a fix in this context)
5. I don’t think we should introduce the 0- hack.
> Add an option in doc creation APIs to specify a random value for an initial
> doc revision
>
>
> Key: COUCHDB-3314
> URL: https://issues.apache.org/jira/browse/COUCHDB-3314
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, HTTP Interface
>Reporter: Mayya Sharipova
>
> Currently the initial revision of a document is deterministic. For instance,
> anyone that has created an empty document probably recognizes the revision
> starting with "1-967a00dff...". In order to account for situations when a
> document is continually purged and recreated we're going to add randomness to
> this initial revision by specifying a 0-$rev in the request coordinator. We
> will then include this in the revision generation but drop the 0-$rev entry
> from the revision's path.
> Thus, the new API will look like this:
> acurl -X PUT
> https://http://adm:pass@127.0.0.1:5984/test-db/newdoc1?rev=0-adfdafa123 -d
> '{}'
> And similarly for _bulk_docs
> For a user who wants to create a doc, then purge it, and then re-create, it
> is recommended to recreate it with another random revision.
> It is important to note that the 0-$rev only affects document creation. Once
> a document exists, updates to the document will continue to update their hash
> in the same deterministic fashion. Ie, once a document exists, identical
> updates will result in identical revisions.
> _
> The following changes need to be made in the code:
> 1. API changes to allow to specify random rev in doc PUT requests, _bulk_docs
> 2. Internals:
> 2.1 Use a new revision here:
> https://github.com/apache/couchdb-couch/blob/master/src/couch_db.erl#L886
> 2.2 Don't include provided 0-$rev entry to the revision's path (find wherever
> new_revid is called from; could be 2-3 places)
> 2.3 Reject a 0-$rev during replication
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-3314) Add an option in doc creation APIs to specify a random value for an initial doc revision
[
https://issues.apache.org/jira/browse/COUCHDB-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928293#comment-15928293
]
Paul Joseph Davis commented on COUCHDB-3314:
Couple points for clarification:
The random initial revision isn't *required* for clustered purge or permanent
deletes. Its merely to try and avoid some *possible* odd behavior if a user has
a specific pattern around "create doc, completely purge doc" in that if they
cycle quickly enough they may get into a state where things get a bit wonky
until they create a second revision. And that's not even known. This just makes
things a lot more sane by not having the same revisions floating around in a
given document's revision tree.
That said, the other reason this was optional was so that we could split it
between the 2.x/3.0 branch. One was to make it possible (either via API or
config) and then the second ticket was to swap the default on 3.0 release.
[~rnewson] I'd say that's only part of the swap and as [~janl] says a rare part
of the reasoning. Its after a doc is created in a db that deterministic
revisions are mostly important.
[~janl] Responding point by point:
1. That's my assumption but I haven't got any hard data either way.
2. Cool
3. This is unrelated. Purge will work the same regardless of how the doc is
created.
4/5. The escape hatch I came up with was the 0- hack. Your suggestion to
specify a revision with new_edits=false seems better on the face of it cause
that kind of even somehow matches the semantics better I think. Creating the
same doc in two different databases is almost like a "pre-creation replication"
type of operation if that makes sense.
> Add an option in doc creation APIs to specify a random value for an initial
> doc revision
>
>
> Key: COUCHDB-3314
> URL: https://issues.apache.org/jira/browse/COUCHDB-3314
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, HTTP Interface
>Reporter: Mayya Sharipova
>
> Currently the initial revision of a document is deterministic. For instance,
> anyone that has created an empty document probably recognizes the revision
> starting with "1-967a00dff...". In order to account for situations when a
> document is continually purged and recreated we're going to add randomness to
> this initial revision by specifying a 0-$rev in the request coordinator. We
> will then include this in the revision generation but drop the 0-$rev entry
> from the revision's path.
> Thus, the new API will look like this:
> acurl -X PUT
> https://http://adm:pass@127.0.0.1:5984/test-db/newdoc1?rev=0-adfdafa123 -d
> '{}'
> And similarly for _bulk_docs
> For a user who wants to create a doc, then purge it, and then re-create, it
> is recommended to recreate it with another random revision.
> It is important to note that the 0-$rev only affects document creation. Once
> a document exists, updates to the document will continue to update their hash
> in the same deterministic fashion. Ie, once a document exists, identical
> updates will result in identical revisions.
> _
> The following changes need to be made in the code:
> 1. API changes to allow to specify random rev in doc PUT requests, _bulk_docs
> 2. Internals:
> 2.1 Use a new revision here:
> https://github.com/apache/couchdb-couch/blob/master/src/couch_db.erl#L886
> 2.2 Don't include provided 0-$rev entry to the revision's path (find wherever
> new_revid is called from; could be 2-3 places)
> 2.3 Reject a 0-$rev during replication
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-3314) Add an option in doc creation APIs to specify a random value for an initial doc revision
[
https://issues.apache.org/jira/browse/COUCHDB-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928298#comment-15928298
]
Paul Joseph Davis commented on COUCHDB-3314:
To clarify on the create/purge cycle behavior. My worry there is that users
would end up seeing either purges that don't seem to take effect and/or creates
that don't seem to take effect. As this would be racing with internal
replication and read-repair the eventual consistency aspects of the system
would I think produce "interesting" results that the random initial revision
would solve.
> Add an option in doc creation APIs to specify a random value for an initial
> doc revision
>
>
> Key: COUCHDB-3314
> URL: https://issues.apache.org/jira/browse/COUCHDB-3314
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, HTTP Interface
>Reporter: Mayya Sharipova
>
> Currently the initial revision of a document is deterministic. For instance,
> anyone that has created an empty document probably recognizes the revision
> starting with "1-967a00dff...". In order to account for situations when a
> document is continually purged and recreated we're going to add randomness to
> this initial revision by specifying a 0-$rev in the request coordinator. We
> will then include this in the revision generation but drop the 0-$rev entry
> from the revision's path.
> Thus, the new API will look like this:
> acurl -X PUT
> https://http://adm:pass@127.0.0.1:5984/test-db/newdoc1?rev=0-adfdafa123 -d
> '{}'
> And similarly for _bulk_docs
> For a user who wants to create a doc, then purge it, and then re-create, it
> is recommended to recreate it with another random revision.
> It is important to note that the 0-$rev only affects document creation. Once
> a document exists, updates to the document will continue to update their hash
> in the same deterministic fashion. Ie, once a document exists, identical
> updates will result in identical revisions.
> _
> The following changes need to be made in the code:
> 1. API changes to allow to specify random rev in doc PUT requests, _bulk_docs
> 2. Internals:
> 2.1 Use a new revision here:
> https://github.com/apache/couchdb-couch/blob/master/src/couch_db.erl#L886
> 2.2 Don't include provided 0-$rev entry to the revision's path (find wherever
> new_revid is called from; could be 2-3 places)
> 2.3 Reject a 0-$rev during replication
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-3326) Implement clustered purge API: _purge
[
https://issues.apache.org/jira/browse/COUCHDB-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928310#comment-15928310
]
ASF subversion and git services commented on COUCHDB-3326:
--
Commit a6572cfb4bedcb77484536587ae938176b224dc4 in couchdb-chttpd's branch
refs/heads/COUCHDB-3326-clustered-purge from [~mayyas]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-chttpd.git;h=a6572cf ]
Implement clustered purge HTTP endpoint
COUCHDB-3326
> Implement clustered purge API: _purge
> -
>
> Key: COUCHDB-3326
> URL: https://issues.apache.org/jira/browse/COUCHDB-3326
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, Documentation, HTTP Interface
>Reporter: Mayya Sharipova
>
> This implements the clustered purge API:
> {code:}
> curl -H 'Content-Type: application/json' -X POST
> "http://adm:pass@127.0.0.1:5984/test1/_purge"; -d
> '{"d1":["3-410e46c04b51b4c3304ed232790a49da",
> "3-420e46c04b51b4c3304ed232790a35db"],"d2":["2-a39d6d63f29a956ae39930f84dd71ec3"],
> "d3":["1-bdca7a3ac9503bf6e46d7d7a782e8f03"]}'
> {code}
> Response: status_code 201 or 202
> {code:javascript}
> {
> "purged": [
> {
> "ok": true, //Quorum was reached, at least W nodes
> successfully purged doc
> "id": "d1",
> "revs": [
> "3-410e46c04b51b4c3304ed232790a49da",
>"3-420e46c04b51b4c3304ed232790a35db"
> ]
> },
> {
> "accepted": true, //Quorum was NOT reached, but request was
> accepted
> "id": "d2",
> "revs": [
> "2-a39d6d63f29a956ae39930f84dd71ec3"
> ]
> },
> {
> "ok": true,
> "id": "d3",
> "revs": []//(DocId or Revs missing) OR (Revs are not leaf
> revisions)
> } ],
> "purge_seq":
> "6-g1BMeJzLYWBgYMpgTmHgz8tPSTV2MDQy1zMAQsMckEQiQ5L8sxKZ4UoMcSrJAgC9PRRl"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-3314) Add an option in doc creation APIs to specify a random value for an initial doc revision
[
https://issues.apache.org/jira/browse/COUCHDB-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928388#comment-15928388
]
Robert Newson commented on COUCHDB-3314:
Jan and I discussed this on IRC and agreed to make the change in COUCHDB-3315
straight off.
Specifically, we accept that the 'same doc creation at two disconnected sites
get the same _rev' is something we're willing to sacrifice to gain clustered
purge (and "hard delete" later on).
So, we'll change behaviour unilaterally, no opt-in or opt-in (no clever "0-"
revision).
The initial revision of a document will be random, but deterministic revision
calculation applies for all updates (so that the N copies within the cluster
are the same rev).
> Add an option in doc creation APIs to specify a random value for an initial
> doc revision
>
>
> Key: COUCHDB-3314
> URL: https://issues.apache.org/jira/browse/COUCHDB-3314
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, HTTP Interface
>Reporter: Mayya Sharipova
>
> Currently the initial revision of a document is deterministic. For instance,
> anyone that has created an empty document probably recognizes the revision
> starting with "1-967a00dff...". In order to account for situations when a
> document is continually purged and recreated we're going to add randomness to
> this initial revision by specifying a 0-$rev in the request coordinator. We
> will then include this in the revision generation but drop the 0-$rev entry
> from the revision's path.
> Thus, the new API will look like this:
> acurl -X PUT
> https://http://adm:pass@127.0.0.1:5984/test-db/newdoc1?rev=0-adfdafa123 -d
> '{}'
> And similarly for _bulk_docs
> For a user who wants to create a doc, then purge it, and then re-create, it
> is recommended to recreate it with another random revision.
> It is important to note that the 0-$rev only affects document creation. Once
> a document exists, updates to the document will continue to update their hash
> in the same deterministic fashion. Ie, once a document exists, identical
> updates will result in identical revisions.
> _
> The following changes need to be made in the code:
> 1. API changes to allow to specify random rev in doc PUT requests, _bulk_docs
> 2. Internals:
> 2.1 Use a new revision here:
> https://github.com/apache/couchdb-couch/blob/master/src/couch_db.erl#L886
> 2.2 Don't include provided 0-$rev entry to the revision's path (find wherever
> new_revid is called from; could be 2-3 places)
> 2.3 Reject a 0-$rev during replication
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-3314) Add an option in doc creation APIs to specify a random value for an initial doc revision
[
https://issues.apache.org/jira/browse/COUCHDB-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928433#comment-15928433
]
Joan Touzet commented on COUCHDB-3314:
--
Further to the IRC discussion with [~janl], [~rnewson] and [~paul.joseph.davis]
I raised the concern that this could frustrate users who independently
calculate document checksums and are unable to predict the {{_rev}} value.
However, the ability to *specify your own {{\_rev}} value* should avoid this
problem. It should also allow the 'same doc creation at two disconnected sites
get the same {{\_rev}}' scenario to work, assuming the client code at both
sites _also_ includes the precalculated {{\_rev}}.
Or, as [~rnewson] put it:
{quote}
10:53 <+rnewson> so, the semantic is this. on doc creation (brand new id or old
id to deleted doc) gets a random _rev _unless_ a rev is specified (if it is, we
use it, and I think bump it)
{quote}
If the above is true I'm +1, with the usual caveats of "document this very
clearly."
> Add an option in doc creation APIs to specify a random value for an initial
> doc revision
>
>
> Key: COUCHDB-3314
> URL: https://issues.apache.org/jira/browse/COUCHDB-3314
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core, HTTP Interface
>Reporter: Mayya Sharipova
>
> Currently the initial revision of a document is deterministic. For instance,
> anyone that has created an empty document probably recognizes the revision
> starting with "1-967a00dff...". In order to account for situations when a
> document is continually purged and recreated we're going to add randomness to
> this initial revision by specifying a 0-$rev in the request coordinator. We
> will then include this in the revision generation but drop the 0-$rev entry
> from the revision's path.
> Thus, the new API will look like this:
> acurl -X PUT
> https://http://adm:pass@127.0.0.1:5984/test-db/newdoc1?rev=0-adfdafa123 -d
> '{}'
> And similarly for _bulk_docs
> For a user who wants to create a doc, then purge it, and then re-create, it
> is recommended to recreate it with another random revision.
> It is important to note that the 0-$rev only affects document creation. Once
> a document exists, updates to the document will continue to update their hash
> in the same deterministic fashion. Ie, once a document exists, identical
> updates will result in identical revisions.
> _
> The following changes need to be made in the code:
> 1. API changes to allow to specify random rev in doc PUT requests, _bulk_docs
> 2. Internals:
> 2.1 Use a new revision here:
> https://github.com/apache/couchdb-couch/blob/master/src/couch_db.erl#L886
> 2.2 Don't include provided 0-$rev entry to the revision's path (find wherever
> new_revid is called from; could be 2-3 places)
> 2.3 Reject a 0-$rev during replication
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (COUCHDB-3315) Introduce randomness to initial revisions of docs
[
https://issues.apache.org/jira/browse/COUCHDB-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928437#comment-15928437
]
Joan Touzet commented on COUCHDB-3315:
--
If you're coming to this ticket without context, you probably want to read the
comment thread on COUCHDB-3314 as well.
> Introduce randomness to initial revisions of docs
> -
>
> Key: COUCHDB-3315
> URL: https://issues.apache.org/jira/browse/COUCHDB-3315
> Project: CouchDB
> Issue Type: Improvement
> Components: Database Core
>Reporter: Mayya Sharipova
> Fix For: 3.0.0
>
>
> This ticket is for couch 3.0 to add randomness to the initial revision of any
> doc with an option to specify that random value in the API by a user.
> While a goal for COUCHDB-3314 is to allow a user to supply a random initial
> revision for a doc through API when desired and if not supplied a
> deterministic {0, <<>>} will be used for all docs; the goal of this ticket
> is to make initial revisions of all docs to be random. This is done to
> account for situations when a document is continually purged and recreated.
> This change does affect one specific behavior. Any user that currently sends
> identical writes to two independent databases and then replicates between
> those databases would see conflicts whenever they create a new database. The
> downside of this change is that there's a use case where someone may make the
> same exact writes to two or more databases and expect there to be no
> conflicts due to replication.
> It is important to note that the 0-$rev only affects document creation. Once
> a document exists, updates to the document will continue to update their hash
> in the same deterministic fashion. Ie, once a document exists, identical
> updates will result in identical revisions.
>
> Changes to code:
> Swap the logic in new_revid to produce random revisions for the initial
> creation
> {0, <<>>} which it is now, we'll replace it with randomness the <<>> binary
> bit
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[GitHub] couchdb-couch-mrview pull request #70: Fix undef error on empty list functio...
Github user asfgit closed the pull request at: https://github.com/apache/couchdb-couch-mrview/pull/70 --- 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 #239: An ETS based couch_lru
Github user sagelywizard commented on the issue: https://github.com/apache/couchdb-couch/pull/239 :+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. ---
[2/3] couchdb-ci git commit: Shorten Docker image names now that we have couchdbdev org
Shorten Docker image names now that we have couchdbdev org Project: http://git-wip-us.apache.org/repos/asf/couchdb-ci/repo Commit: http://git-wip-us.apache.org/repos/asf/couchdb-ci/commit/51f2988d Tree: http://git-wip-us.apache.org/repos/asf/couchdb-ci/tree/51f2988d Diff: http://git-wip-us.apache.org/repos/asf/couchdb-ci/diff/51f2988d Branch: refs/heads/master Commit: 51f2988d334f2ff7f1f37935117468c9fcb5491f Parents: 3df0edf Author: Joan Touzet Authored: Thu Mar 16 14:10:30 2017 -0700 Committer: Joan Touzet Committed: Thu Mar 16 14:10:30 2017 -0700 -- bin/centos-7-base/create-container.sh| 2 +- bin/centos-7-base/enter-container.sh | 2 +- bin/centos-7-base/publish-container.sh | 2 +- bin/centos-7-erlang-18/create-container.sh | 2 +- bin/centos-7-erlang-18/enter-container.sh| 2 +- bin/centos-7-erlang-18/publish-container.sh | 2 +- bin/centos-7-erlang-default/create-container.sh | 2 +- bin/centos-7-erlang-default/enter-container.sh | 2 +- bin/centos-7-erlang-default/publish-container.sh | 2 +- bin/debian-8-base/create-container.sh| 2 +- bin/debian-8-base/enter-container.sh | 2 +- bin/debian-8-base/publish-container.sh | 2 +- bin/debian-8-erlang-18/create-container.sh | 2 +- bin/debian-8-erlang-18/enter-container.sh| 2 +- bin/debian-8-erlang-18/publish-container.sh | 2 +- bin/debian-8-erlang-default/create-container.sh | 2 +- bin/debian-8-erlang-default/enter-container.sh | 2 +- bin/debian-8-erlang-default/publish-container.sh | 2 +- bin/ubuntu-14.04-base/create-container.sh| 2 +- bin/ubuntu-14.04-base/enter-container.sh | 2 +- bin/ubuntu-14.04-base/publish-container.sh | 2 +- bin/ubuntu-14.04-erlang-18/create-container.sh | 2 +- bin/ubuntu-14.04-erlang-18/enter-container.sh| 2 +- bin/ubuntu-14.04-erlang-18/publish-container.sh | 2 +- bin/ubuntu-14.04-erlang-default/create-container.sh | 2 +- bin/ubuntu-14.04-erlang-default/enter-container.sh | 2 +- bin/ubuntu-14.04-erlang-default/publish-container.sh | 2 +- dockerfiles/centos-7-erlang-18 | 2 +- dockerfiles/centos-7-erlang-default | 2 +- dockerfiles/debian-8-erlang-18 | 2 +- dockerfiles/debian-8-erlang-default | 2 +- dockerfiles/ubuntu-14.04-erlang-18 | 2 +- dockerfiles/ubuntu-14.04-erlang-default | 2 +- jenkins/build.sh | 2 +- 34 files changed, 34 insertions(+), 34 deletions(-) -- http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/51f2988d/bin/centos-7-base/create-container.sh -- diff --git a/bin/centos-7-base/create-container.sh b/bin/centos-7-base/create-container.sh index c31a01a..9c5f068 100755 --- a/bin/centos-7-base/create-container.sh +++ b/bin/centos-7-base/create-container.sh @@ -23,6 +23,6 @@ set -e # build context (because they need the Ansible files). pushd `dirname $0`/../.. > /dev/null -docker build -f dockerfiles/centos-7-base -t couchdbdev/couchdb-build-centos-7-base . +docker build -f dockerfiles/centos-7-base -t couchdbdev/centos-7-base . popd > /dev/null http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/51f2988d/bin/centos-7-base/enter-container.sh -- diff --git a/bin/centos-7-base/enter-container.sh b/bin/centos-7-base/enter-container.sh index e7c88ae..253b54b 100755 --- a/bin/centos-7-base/enter-container.sh +++ b/bin/centos-7-base/enter-container.sh @@ -17,4 +17,4 @@ # specific language governing permissions and limitations # under the License. -docker run -it couchdbdev/couchdb-build-centos-7-base bash +docker run -it couchdbdev/centos-7-base bash http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/51f2988d/bin/centos-7-base/publish-container.sh -- diff --git a/bin/centos-7-base/publish-container.sh b/bin/centos-7-base/publish-container.sh index 86869ae..874c3d8 100755 --- a/bin/centos-7-base/publish-container.sh +++ b/bin/centos-7-base/publish-container.sh @@ -17,4 +17,4 @@ # specific language governing permissions and limitations # under the License. -docker push couchdbdev/couchdb-build-centos-7-base +docker push couchdbdev/centos-7-base http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/51f2988d/bin/centos-7-erlang-18/create-container.sh -- diff --git a/bin/centos-7-erlang-18/create-container.sh b/bin/centos-7-erlang-18/create-container.sh index 3ef2548..7f20ac9 1007
[1/3] couchdb-ci git commit: Fix CentOS LaTeX build
Repository: couchdb-ci
Updated Branches:
refs/heads/master 30055eb24 -> 7fa91caea
Fix CentOS LaTeX build
Project: http://git-wip-us.apache.org/repos/asf/couchdb-ci/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-ci/commit/3df0edf8
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-ci/tree/3df0edf8
Diff: http://git-wip-us.apache.org/repos/asf/couchdb-ci/diff/3df0edf8
Branch: refs/heads/master
Commit: 3df0edf8dc41185df0ca1f5471e128020f23b504
Parents: 30055eb
Author: Joan Touzet
Authored: Thu Mar 16 13:36:06 2017 -0700
Committer: Joan Touzet
Committed: Thu Mar 16 13:36:06 2017 -0700
--
.../roles/dependencies-centos/tasks/latex.yml | 23 ++--
1 file changed, 16 insertions(+), 7 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/3df0edf8/ansible/roles/dependencies-centos/tasks/latex.yml
--
diff --git a/ansible/roles/dependencies-centos/tasks/latex.yml
b/ansible/roles/dependencies-centos/tasks/latex.yml
index ca0ba59..b2a01b4 100644
--- a/ansible/roles/dependencies-centos/tasks/latex.yml
+++ b/ansible/roles/dependencies-centos/tasks/latex.yml
@@ -15,9 +15,9 @@
# specific language governing permissions and limitations
# under the License.
-- name: copy TeX Live installer
- copy:
-src: install-tl-unx.tar.gz
+- name: download TeX Live installer
+ get_url:
+url: http://mirror.ctan.org/systems/texlive/tlnet/install-tl-unx.tar.gz
dest: /tmp/install-tl-unx.tar.gz
- name: copy TeX Live installer profile
copy:
@@ -28,16 +28,25 @@
src: /tmp/install-tl-unx.tar.gz
dest: /tmp
copy: no
+- name: remove TeX Live installer
+ file:
+path: /tmp/install-tl-unx.tar.gz
+state: absent
+- name: determine extracted installer path
+ shell: ls -d /tmp/install-tl-*
+ register: dir_name
- name: install TeX Live via net installer
- command: /tmp/install-tl-20160206/install-tl --profile=/tmp/texlive.profile
- args:
-chdir: /tmp/install-tl-20160206
+ command: "{{ item }}/install-tl --profile=/tmp/texlive.profile chdir={{ item
}}"
+ with_items: "{{ dir_name.stdout_lines }}"
- name: install additional TeX packages
command: tlmgr install capt-of framed multirow needspace threeparttable
titlesec upquote wrapfig
# remove docs dir - this has no benefit for our use case and makes the
# container 500 MB bigger
+- name: find LaTeX docs dir
+ shell: ls -d /usr/local/texlive/*
+ register: docdir_name
- name: delete LaTeX docs
file:
-path: /usr/local/texlive/2015/texmf-dist/doc
+path: "{{docdir_name}}/texmf-dist/doc"
state: absent
[3/3] couchdb-ci git commit: Add docker cleanup script
Add docker cleanup script Project: http://git-wip-us.apache.org/repos/asf/couchdb-ci/repo Commit: http://git-wip-us.apache.org/repos/asf/couchdb-ci/commit/7fa91cae Tree: http://git-wip-us.apache.org/repos/asf/couchdb-ci/tree/7fa91cae Diff: http://git-wip-us.apache.org/repos/asf/couchdb-ci/diff/7fa91cae Branch: refs/heads/master Commit: 7fa91caead0481b5a2dc916f52a1ff0c7a0c7309 Parents: 51f2988 Author: Joan Touzet Authored: Thu Mar 16 14:44:55 2017 -0700 Committer: Joan Touzet Committed: Thu Mar 16 14:44:55 2017 -0700 -- bin/cleanup-docker.sh | 32 1 file changed, 32 insertions(+) -- http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/7fa91cae/bin/cleanup-docker.sh -- diff --git a/bin/cleanup-docker.sh b/bin/cleanup-docker.sh new file mode 100755 index 000..dc114ac --- /dev/null +++ b/bin/cleanup-docker.sh @@ -0,0 +1,32 @@ +#!/usr/bin/env bash + +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +echo WARNING! This script will delete all stopped containers! +read -n1 -r -p "Press any key to continue..." key +echo + +# Delete all stopped containers +docker rm $(docker ps -aq --filter status=exited) 2&>/dev/null + +# Delete all untagged or dangling images +docker rmi $(docker images -q -f dangling=true) 2&>/dev/null + +# Clean up dangling volumes, if any +docker volume rm $(docker volume ls -qf dangling=true) 2&>/dev/null +
[1/2] couchdb-ci git commit: Erlang 18->18.2; copy ansible into every image
Repository: couchdb-ci Updated Branches: refs/heads/master 7fa91caea -> 396f77a46 Erlang 18->18.2; copy ansible into every image Previously, the Dockerfile only copied the ansible/ directory into the -base images. This means that if you want to add a new version of Erlang (for instance), you have to rebuild *all* of the images just to populate the /ansible directory to the child images. So instead we simply re-ADD the /ansible directory into each child image. This allows for generation of new os-erlang-XX.X images (or other things, in the future) without respinning every single image. Project: http://git-wip-us.apache.org/repos/asf/couchdb-ci/repo Commit: http://git-wip-us.apache.org/repos/asf/couchdb-ci/commit/a0ad40dd Tree: http://git-wip-us.apache.org/repos/asf/couchdb-ci/tree/a0ad40dd Diff: http://git-wip-us.apache.org/repos/asf/couchdb-ci/diff/a0ad40dd Branch: refs/heads/master Commit: a0ad40ddf4ecb09c18b437d6c9e8c9b29cf06794 Parents: 7fa91ca Author: Joan Touzet Authored: Thu Mar 16 22:21:43 2017 -0700 Committer: Joan Touzet Committed: Thu Mar 16 22:21:43 2017 -0700 -- ansible/centos-7-erlang-18.2.yml| 21 +++ ansible/centos-7-erlang-18.yml | 21 --- ansible/debian-8-erlang-18.2.yml| 22 +++ ansible/debian-8-erlang-18.yml | 22 --- ansible/roles/erlang-18-centos/tasks/main.yml | 23 --- ansible/roles/erlang-18-debian/tasks/main.yml | 46 -- ansible/roles/erlang-18.2-centos/tasks/main.yml | 23 +++ ansible/roles/erlang-18.2-debian/tasks/main.yml | 66 ansible/run-ansible-local.sh| 2 +- ansible/ubuntu-14.04-erlang-18.2.yml| 22 +++ ansible/ubuntu-14.04-erlang-18.yml | 22 --- bin/centos-7-erlang-18.2/create-container.sh| 28 + bin/centos-7-erlang-18.2/enter-container.sh | 20 ++ bin/centos-7-erlang-18.2/publish-container.sh | 20 ++ .../run-build-in-container.sh | 24 +++ bin/centos-7-erlang-18/create-container.sh | 28 - bin/centos-7-erlang-18/enter-container.sh | 20 -- bin/centos-7-erlang-18/publish-container.sh | 20 -- .../run-build-in-container.sh | 24 --- bin/debian-8-erlang-18.2/create-container.sh| 28 + bin/debian-8-erlang-18.2/enter-container.sh | 20 ++ bin/debian-8-erlang-18.2/publish-container.sh | 20 ++ .../run-build-in-container.sh | 24 +++ bin/debian-8-erlang-18/create-container.sh | 28 - bin/debian-8-erlang-18/enter-container.sh | 20 -- bin/debian-8-erlang-18/publish-container.sh | 20 -- .../run-build-in-container.sh | 24 --- .../create-container.sh | 28 + bin/ubuntu-14.04-erlang-18.2/enter-container.sh | 20 ++ .../publish-container.sh| 20 ++ .../run-build-in-container.sh | 24 +++ bin/ubuntu-14.04-erlang-18/create-container.sh | 28 - bin/ubuntu-14.04-erlang-18/enter-container.sh | 20 -- bin/ubuntu-14.04-erlang-18/publish-container.sh | 20 -- .../run-build-in-container.sh | 24 --- dockerfiles/centos-7-erlang-18 | 29 - dockerfiles/centos-7-erlang-18.2| 34 ++ dockerfiles/centos-7-erlang-default | 5 ++ dockerfiles/debian-8-erlang-18 | 29 - dockerfiles/debian-8-erlang-18.2| 34 ++ dockerfiles/debian-8-erlang-default | 5 ++ dockerfiles/ubuntu-14.04-erlang-18 | 29 - dockerfiles/ubuntu-14.04-erlang-18.2| 34 ++ dockerfiles/ubuntu-14.04-erlang-default | 5 ++ 44 files changed, 548 insertions(+), 498 deletions(-) -- http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/a0ad40dd/ansible/centos-7-erlang-18.2.yml -- diff --git a/ansible/centos-7-erlang-18.2.yml b/ansible/centos-7-erlang-18.2.yml new file mode 100644 index 000..492f252 --- /dev/null +++ b/ansible/centos-7-erlang-18.2.yml @@ -0,0 +1,21 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distrib
[2/2] couchdb-ci git commit: Fix comment in jenkins/build.sh
Fix comment in jenkins/build.sh Project: http://git-wip-us.apache.org/repos/asf/couchdb-ci/repo Commit: http://git-wip-us.apache.org/repos/asf/couchdb-ci/commit/396f77a4 Tree: http://git-wip-us.apache.org/repos/asf/couchdb-ci/tree/396f77a4 Diff: http://git-wip-us.apache.org/repos/asf/couchdb-ci/diff/396f77a4 Branch: refs/heads/master Commit: 396f77a46f4b699c810f82cde8a1698e771da4b5 Parents: a0ad40d Author: Joan Touzet Authored: Thu Mar 16 22:57:32 2017 -0700 Committer: Joan Touzet Committed: Thu Mar 16 22:57:32 2017 -0700 -- jenkins/build.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/couchdb-ci/blob/396f77a4/jenkins/build.sh -- diff --git a/jenkins/build.sh b/jenkins/build.sh index 63e77d1..623b6b3 100755 --- a/jenkins/build.sh +++ b/jenkins/build.sh @@ -59,7 +59,7 @@ esac case $ERLANG in default*) -echo "Using Erlang 18.2" +echo "Using OS default Erlang" DOCKER_IMAGE=$DOCKER_IMAGE"erlang-default" ;; 18.2*)
