[GitHub] wohali commented on issue #1611: Bad Security Object Error After Moving Shards
wohali commented on issue #1611: Bad Security Object Error After Moving Shards URL: https://github.com/apache/couchdb/issues/1611#issuecomment-422994860 @arifcse019 Can you provide a minimal example for us with a script that uses cURL? I've personally performed the steps you mention above (1-4) many times and have never run across this. What technique are you using to move the shards? There is newly updated documentation on the approved approach online, can you follow that? http://docs.couchdb.org/en/stable/cluster/sharding.html This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] arifcse019 opened a new issue #1611: Bad Security Object Error After Moving Shards
arifcse019 opened a new issue #1611: Bad Security Object Error After Moving
Shards
URL: https://github.com/apache/couchdb/issues/1611
Security objects for some databases fail to sync properly in a new node
after all shards are moved from an old node.
## Expected Behavior
Security objects for all databases should sync when shards are moved to a
new node
## Current Behavior
Security objects for some databases fail to sync properly in a new node
after all shards are moved from an old node. The log says things like:
" [error] 2018-09-19T17:24:05.388202Z couchdb@first.couchcluster.internal
<0.19944.2> Bad security object in <<"db-name">>:
[{{[{<<"_id">>,<<"_security">>},{<<"admins">>,{[{<<"names">>,[]},{<<"roles">>,[]}]}},{<<"members">>,{[{<<"names">>,[<<"user-name">>]},{<<"roles">>,[]}]}}]},13},{{[]},7}]
"
## Steps to Reproduce (for bugs)
1. Add a new node to the cluster
2. Move All Shards from an old node to this new one
3. Shut down and delete the old node
4. Verify Security Objects on all databases
## Context
We are trying to replace couch cluster instances with new instances as part
of preparing for a scenario where one instance can go away abruptly
## Your Environment
* Version used: Couch 2.1.2, 3 node cluster
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] nickva opened a new pull request #1613: Ignore local nodes in read repair filtering
nickva opened a new pull request #1613: Ignore local nodes in read repair
filtering
URL: https://github.com/apache/couchdb/pull/1613
Previosly local node revisions were causing `badmatch` failures in read
repair
filter. Node sequences already filtered out local nodes while NodeRevs
didn't, so
during matching `{Node, NodeSeq} = lists:keyfind(Node, 1, NodeSeqs)` Node
would
not be found in the list and crash.
Example of crash:
```
fabric_rpc:update_docs/3 error:{badmatch,false}
[{fabric_rpc,'-read_repair_filter/3-fun-1-',4,[{file,"src/fabric_rpc.erl"},{line,360}]},
```
## Checklist
- [x] Code is written and works correctly;
- [x] Changes are covered by tests;
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] ermouth opened a new issue #1612: JS-rewritten post/put hangs or returns bad_request
ermouth opened a new issue #1612: JS-rewritten post/put hangs or returns
bad_request
URL: https://github.com/apache/couchdb/issues/1612
## Expected Behavior
JS rewrite, returning `{path:'whatever', method:'PUT', body:'body'} should
send body to the rewritten endpoint.
## Current Behavior
The `body` field of rewrite fn returned obj is in some cases dropped. If
source request was POST/PUT, the rewritten requests hangs, or, if source
request was GET-like, `bad_request` error is sent as response.
## Steps to Reproduce
1. Create empty bucket named, say, `zz`
2. Put design doc with `rewrites` into the bucket. Below ddoc is intended to
create new random doc on each request to `_design/n/_rewrite` endpoint:
{
"_id": "_design/n",
"rewrites": "function (r) {\n\tvar id =
'x'+(Date.now()+'').substr(-8);\n\treturn
{\n\t\tpath:'../../'+id,\n\t\tmethod:'PUT',\n\t\theaders:{'content-type':'application/json',Accept:'application/json'},\n\t\tbody:JSON.stringify({_id:id,type:'test',val:Date.now().toString(36)})\n\t}\n}"
}
3. Call `http://couchdb_ip/zz/_design/n/_rewrite`.
## Solution
The issue is caused by cleaning-up rewritten request prematurely here:
https://github.com/apache/couchdb/blob/master/src/chttpd/src/chttpd_rewrite.erl#L67.
It should only be cleaned if we have no body to send.
That line (L67) should be replaced with this code:
Body = case couch_util:get_value(<<"body">>, Props) of
undefined -> erlang:get(mochiweb_request_body);
B -> B
end,
case Body of
undefined -> MochiReq:cleanup();
_ -> erlang:put(mochiweb_request_body, Body)
end,
It fixes issue completely.
## Your Environment
* Version used: 2.1.2, 2.2.0
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] nickva closed pull request #1613: Ignore local nodes in read repair filtering
nickva closed pull request #1613: Ignore local nodes in read repair filtering
URL: https://github.com/apache/couchdb/pull/1613
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/src/fabric/src/fabric_rpc.erl b/src/fabric/src/fabric_rpc.erl
index c684229690..11e6754646 100644
--- a/src/fabric/src/fabric_rpc.erl
+++ b/src/fabric/src/fabric_rpc.erl
@@ -347,7 +347,8 @@ read_repair_filter(DbName, Docs, NodeRevs, Options) ->
% as the read_repair option to update_docs.
read_repair_filter(Db, Docs, NodeRevs) ->
[#doc{id = DocId} | _] = Docs,
-Nodes = lists:usort([Node || {Node, _} <- NodeRevs, Node /= node()]),
+NonLocalNodeRevs = [NR || {N, _} = NR <- NodeRevs, N /= node()],
+Nodes = lists:usort([Node || {Node, _} <- NonLocalNodeRevs]),
NodeSeqs = get_node_seqs(Db, Nodes),
DbPSeq = couch_db:get_purge_seq(Db),
@@ -360,7 +361,7 @@ read_repair_filter(Db, Docs, NodeRevs) ->
{Node, NodeSeq} = lists:keyfind(Node, 1, NodeSeqs),
NodeSeq >= DbPSeq - Lag
end,
-RecentNodeRevs = lists:filter(NodeFiltFun, NodeRevs),
+RecentNodeRevs = lists:filter(NodeFiltFun, NonLocalNodeRevs),
% For each node we scan the purge infos to filter out any
% revisions that have been locally purged since we last
diff --git a/src/fabric/test/fabric_rpc_purge_tests.erl
b/src/fabric/test/fabric_rpc_purge_tests.erl
index 26507cf0bb..4eafb2bc46 100644
--- a/src/fabric/test/fabric_rpc_purge_tests.erl
+++ b/src/fabric/test/fabric_rpc_purge_tests.erl
@@ -46,6 +46,7 @@ main_test_() ->
lists:map(fun wrap/1, [
?TDEF(t_filter),
?TDEF(t_filter_unknown_node),
+?TDEF(t_filter_local_node),
?TDEF(t_no_filter_old_node),
?TDEF(t_no_filter_different_node),
?TDEF(t_no_filter_after_repl)
@@ -58,6 +59,7 @@ main_test_() ->
lists:map(fun wrap/1, [
?TDEF(t_filter),
?TDEF(t_filter_unknown_node),
+?TDEF(t_filter_local_node),
?TDEF(t_no_filter_old_node),
?TDEF(t_no_filter_different_node),
?TDEF(t_no_filter_after_repl)
@@ -172,6 +174,26 @@ t_no_filter_different_node({DbName, DocId, OldDoc, PSeq})
->
?assertEqual({ok, OldDoc}, open_doc(DbName, DocId)).
+t_filter_local_node({DbName, DocId, OldDoc, PSeq}) ->
+?assertEqual({not_found, missing}, open_doc(DbName, DocId)),
+create_purge_checkpoint(DbName, PSeq),
+
+% Create a valid purge for a different node
+TgtNode = list_to_binary(atom_to_list('notfoo@127.0.0.1')),
+create_purge_checkpoint(DbName, 0, TgtNode),
+
+% Add a local node rev to the list of node revs. It should
+% be filtered out
+{Pos, [Rev | _]} = OldDoc#doc.revs,
+RROpts = [{read_repair, [
+{tgt_node(), [{Pos, Rev}]},
+{node(), [{1, <<"123">>}]}
+]}],
+rpc_update_doc(DbName, OldDoc, RROpts),
+
+?assertEqual({ok, OldDoc}, open_doc(DbName, DocId)).
+
+
t_no_filter_after_repl({DbName, DocId, OldDoc, PSeq}) ->
?assertEqual({not_found, missing}, open_doc(DbName, DocId)),
create_purge_checkpoint(DbName, PSeq),
@@ -282,4 +304,4 @@ tgt_node() ->
tgt_node_bin() ->
-iolist_to_binary(atom_to_list(tgt_node())).
\ No newline at end of file
+iolist_to_binary(atom_to_list(tgt_node())).
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] kmoe opened a new issue #1610: Set-Cookie Expires field date format
kmoe opened a new issue #1610: Set-Cookie Expires field date format URL: https://github.com/apache/couchdb/issues/1610 This is either a spec issue or a documentation issue. ## Steps to reproduce 1. Set the config value `couch_httpd_auth.allow_persistent_cookies` to `true` 2. `POST` username and password to `/_session` as described in [docs](http://docs.couchdb.org/en/stable/api/server/authn.html?highlight=set-cookie#post--_session) ## Results The response contains a header of this form: ``` Set-Cookie: AuthSession=cm9vdDo1MEJCRkYwMjq0LO0ylOIwShrgt8y-UkhI-c6BGw; Version=1; Expires=Thu, 20-Sep-2018 11:24:18 GMT; Max-Age=86400; Path=/; HttpOnly; Secure ``` ## Issue We are concerned with the `Expires` value: ``` Expires=Thu, 20-Sep-2018 11:24:18 GMT ``` Does this date format implement any known RFC? [RFC6265](https://tools.ietf.org/html/rfc6265#section-4.1.1) defines the `Set-Cookie` field, and specifies that the `Expires` date is defined in [RFC2616, Section 3.3.1](https://tools.ietf.org/html/rfc2616#section-3.3.1). This section cites three date formats: ``` Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123 Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format ``` The CouchDB `Expires` format satisfies none of these. Is the CouchDB `Expires` date format specified somewhere, either in CouchDB documentation or some other RFC? ## Context I am writing a proxy server which needs to parse the `Expires` value. I couldn't find the place in the CouchDB codebase where it is set. If there is an Erlang/Elixir library that parses this format, that would also be welcome. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] wohali commented on issue #1551: Fix session based replicator auth when endpoints with require_valid_user
wohali commented on issue #1551: Fix session based replicator auth when endpoints with require_valid_user URL: https://github.com/apache/couchdb/pull/1551#issuecomment-422843552 2.3.0 is being planned for release now. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (COUCHDB-3226) Build under snap container is denied access to /bindf
[ https://issues.apache.org/jira/browse/COUCHDB-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620619#comment-16620619 ] ASF subversion and git services commented on COUCHDB-3226: -- Commit c4faf706a9bba87d89d3e056d7402878aa5d6341 in couchdb's branch refs/heads/COUCHDB-3226-pre-clustered-purge from jiangph [ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=c4faf70 ] Add downgrade_purge_info function to downgrade database COUCHDB-3226 > Build under snap container is denied access to /bindf > - > > Key: COUCHDB-3226 > URL: https://issues.apache.org/jira/browse/COUCHDB-3226 > Project: CouchDB > Issue Type: Bug > Components: Build System >Reporter: Simon C Klassen >Priority: Major > > dmesg is logging "audit: type=1400 audit(1478517224.548:198): > apparmor="DENIED" operation="exec" profile="snap.couchdb.couchdb" > name="/bin/df" pid=16227 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 > ouid=0" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] garrensmith opened a new pull request #1609: Mango match doc on co-ordinating node
garrensmith opened a new pull request #1609: Mango match doc on co-ordinating node URL: https://github.com/apache/couchdb/pull/1609 ## Overview This fixes an issue when doing a rolling upgrade of a CouchDB cluster and adding commit a6bc72e the nodes that were not upgraded yet would send through all the docs in the index and those would be passed through to the user because the co-oridnator would assume it was matched at the node level. This adds in a check to see if it has been matched at the node level or not. And then performs a match if required. ## Testing recommendations This is tricky to test. If you have nodes running an older version of CouchDB, this should stop unmatched docs from being returned to the user. ## Checklist - [x] Code is written and works correctly; - [ ] Changes are covered by tests; - [ ] Documentation reflects the changes; This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] davisp commented on a change in pull request #1602: Remove runtime configurability of core system components
davisp commented on a change in pull request #1602: Remove runtime
configurability of core system components
URL: https://github.com/apache/couchdb/pull/1602#discussion_r218835624
##
File path: src/couch/src/couch_secondary_sup.erl
##
@@ -26,6 +26,16 @@ init([]) ->
worker,
dynamic}
],
+Daemons = [
+{"index_server", "{couch_index_server, start_link, []}"},
Review comment:
It seems a bit silly to keep these as strings just to convert all of the
terms in the following list comprehension. I'd at least like to remove that bit
of silly for this supervisor. I'd also suggest that we just write out the child
specs directly in the SecondarySupervisors list above given that's the more
traditional way of doing things (or at least using a helper that gets mapped
over the name/mfa pairs.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] abbyad opened a new pull request #1608: Fix link in contributing doc
abbyad opened a new pull request #1608: Fix link in contributing doc URL: https://github.com/apache/couchdb/pull/1608 ## Overview The URL for Hoodie was displayed instead of being a hyperlink. Displaying the full link may have been intentional, but perhaps not. If so, please disregard this PR. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] janl closed issue #1453: Cut 2.2.0 release
janl closed issue #1453: Cut 2.2.0 release URL: https://github.com/apache/couchdb/issues/1453 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] glynnbird commented on issue #1254: Add aggregation functions to Mango
glynnbird commented on issue #1254: Add aggregation functions to Mango
URL: https://github.com/apache/couchdb/issues/1254#issuecomment-422799520
I was asked by @willholley to contribute this Markdown which describes a
possible `aggregator` syntax for supporting aggregations in Mango.
# What would Mango aggregation look like?
At the moment, the Mango query language only performs data selection - a
portion of a larger data set can be returned by providing a JSON query. If my
data looks like this:
```js
{
_id: "someid",
date: "2018-08-24",
status: "provisional",
invoiceAddress: {
street: "10 Front Street",
city: "Dallas",
state: "Texas"
},
amount: 7.99,
tax: 0,
totalAmount: 7.99,
customerId: "A65522",
lineItems: [
{
productId: "P1",
name: "fish",
cost: 6.0
},
{
productId: "P2",
name: "chips",
cost: 1.99
}
]
}
```
and I want only the "complete" orders from a database I could perform a
query.
```js
{
selector: {
status : "complete"
},
fields: ["totalAmount", "date"]
}
```
which would give a paged result set in blocks of 200 records:
```js
{
"docs": [
{
"totalAmount": 7.99,
"date": "2018-08-24"
},
{
"totalAmount": 4.50,
"date": "2018-08-24"
},
...
],
"bookmark":
"g1A6eJzLYWBgYMpgSmHgKy5JLCrJTq2MT8lPzkzJBYqzVqUmFSWCJDlgkgjhLADXERDn",
"execution_stats": {
"total_keys_examined": 0,
"total_docs_examined": 10,
"total_quorum_docs_examined": 0,
"results_returned": 8,
"execution_time_ms": 2.75
},
"warning": "no matching index found, create an index to optimize query
time"
}
```
But what I really want is a grand total of the `totalAmount` fields, grouped
by `date` but Mango only supports *selection* not *aggregation*. I would have
to page through all the results and perform the aggregation in my code.
This document imagines that Mango magically *does* support aggregation.
Everything that follows is fictional syntax in my imaginary world.
--- start of imaginary world ---
## My first Mango aggregation
I can use the new "aggregator" object in a Mango query. My query still has a
selector, because I don't want to aggregate ALL the documents, only the
"complete" orders as before:
```js
{
selector: {
status : "complete"
},
aggregator: {
operation: "sum",
of: ["totalAmount"]
}
}
```
Note:
- I no longer need to supply a `fields` object at the top level. Mango knows
the fields it needs from those specified in the aggregator object.
- the `aggregator.operation` field can be one of `sum`, `count` or `stats`.
- `aggregator.of` is an array - we'll see how this works later.
If I'm using the `count` aggregation, I needn't supplied an `aggregation.of`
array:
```js
{
selector: {
status : "complete"
},
aggregator: {
operation: "count"
}
}
```
## A grand total example
Using an `aggreator.operation` of `sum` allows me to get a grand total of a
field:
```
{
selector: {
status : "complete"
},
aggregator: {
operation: "sum",
of: ["totalAmount"]
}
}
```
or fields:
```
{
selector: {
status : "complete"
},
aggregator: {
operation: "sum",
of: ["totalAmount", "tax"]
}
}
```
or by emptying the "selector", all documents are aggregated:
```
{
selector: { },
aggregator: {
operation: "sum",
of: ["totalAmount", "tax"]
}
}
```
## Grouping
In this example I am performing a more complex selector and introduce
grouping:
```
{
selector: {
"$or": {
status : "complete",
status: "refunded"
}
},
aggregator: {
operation: "sum",
of: ["totalAmount", "tax"],
group: ["date"]
}
}
```
Any valid Mango selector is allowed in the "selector" object. The "selector"
is evaluated at index time and decides which portion of the data makes it to
the index. If the selector is changed, a new index is required to calculate the
result.
The optional "aggregator.group" is an array of keys by which the sum is
grouped in the result set. It is an array, so I can have multi-dimensional
grouping:
```
{
selector: {
"$or": {
status : "complete",
status: "refunded"
}
},
aggregator: {
operation: "sum",
of: ["totalAmount",
[GitHub] Antonio-Maranhao opened a new pull request #1125: [partitioned-dbs] Support create and list databases
Antonio-Maranhao opened a new pull request #1125: [partitioned-dbs] Support create and list databases URL: https://github.com/apache/couchdb-fauxton/pull/1125 ## Overview First in a series of PRs that will be submitted in support of the new user-defined partitioned databases feature (https://github.com/apache/couchdb/pull/1605). To provide backwards compatibility, Fauxton will detect if the feature is enabled on the server and only display the new GUI elements based on this check. Summary: - Detect and enable support if the feature is available on the server - Add 'Partitioned' checkbox when creating a new database - Show 'Partitioned' column in the database list ## Testing recommendations - Create a new database and check the 'Partitioned' checkbox - Verify the new database is listed and its 'Partitioned' column reads 'Yes' ## Related Pull Requests https://github.com/apache/couchdb/pull/1605 ## Checklist - [x] Code is written and works correctly; - [x] Changes are covered by tests; - [ ] Documentation reflects the changes; - [ ] Update [rebar.config.script](https://github.com/apache/couchdb/blob/master/rebar.config.script) with the correct tag once a new Fauxton release is made This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] jaydoane commented on issue #1605: Feature/user partitioned databases
jaydoane commented on issue #1605: Feature/user partitioned databases URL: https://github.com/apache/couchdb/pull/1605#issuecomment-423034534 @garrensmith I notice that the tests in https://github.com/cloudant/partition_tests/tree/master/test don't have a common prefix, which although fine for now, I think will become less cohesive once they are merged with the main elixir suite. Would you consider renaming them so they all start with `partition_`? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] Richard-O-Wood commented on issue #718: SSL / HTTPS settings lead to shards being shown, instead of databases.
Richard-O-Wood commented on issue #718: SSL / HTTPS settings lead to shards being shown, instead of databases. URL: https://github.com/apache/couchdb/issues/718#issuecomment-422922449 I was having a very similar problem until earlier this morning. I am running V2.1.0 on Windows Server 2012 R2 I am using a WSSO_Proxy server for authentication. However, I do have an OpenSSL certificate and CA installed and referenced in my local.ini My Fauxton Databases page was working fine on HTTP (port 5984) but on HTTPS (port 6984) I was getting shards instead of my databases. I read through the explanations from @wohali above, and tried a number of different combinations. Finally got a local.ini file that would work. I thought I would share my file for reference. I changed a few things in the attached file for obfuscation purposes like the IP address company name in the URL and some characters in the hash values. Hopefully this will help someone else. Also, if anyone spots something "wrong" in my local.ini, please let me know. [local.ini](https://github.com/apache/couchdb/files/2398383/local_ini.txt) This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] H--o-l commented on issue #1551: Fix session based replicator auth when endpoints with require_valid_user
H--o-l commented on issue #1551: Fix session based replicator auth when endpoints with require_valid_user URL: https://github.com/apache/couchdb/pull/1551#issuecomment-422725500 Hi ! Same remark as @adrienverge , we are stuck in version 2.1.2 due to issue #1550. We would love to update but we need this fix in order to. Do you know when a version 2.2.1 could be expected ? Thanks in advance ! This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (COUCHDB-3226) Build under snap container is denied access to /bindf
[ https://issues.apache.org/jira/browse/COUCHDB-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620374#comment-16620374 ] ASF subversion and git services commented on COUCHDB-3226: -- Commit 67a65fd586657547aa01b468232338af246e428d in couchdb's branch refs/heads/COUCHDB-3226-pre-clustered-purge from jiangph [ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=67a65fd ] Add downgrade_purge_info function to downgrade database COUCHDB-3226 > Build under snap container is denied access to /bindf > - > > Key: COUCHDB-3226 > URL: https://issues.apache.org/jira/browse/COUCHDB-3226 > Project: CouchDB > Issue Type: Bug > Components: Build System >Reporter: Simon C Klassen >Priority: Major > > dmesg is logging "audit: type=1400 audit(1478517224.548:198): > apparmor="DENIED" operation="exec" profile="snap.couchdb.couchdb" > name="/bin/df" pid=16227 comm="sh" requested_mask="x" denied_mask="x" fsuid=0 > ouid=0" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
