[jira] [Created] (COUCHDB-3243) couchdb v2.0.0 not supported by vendor even wit...

[ASF subversion and git services (JIRA)]

ASF subversion and git services created COUCHDB-3243:


 Summary: couchdb v2.0.0not supported by vendor even wit...
 Key: COUCHDB-3243
 URL: https://issues.apache.org/jira/browse/COUCHDB-3243
 Project: CouchDB
  Issue Type: Bug
Reporter: ASF subversion and git services
 Attachments: Screenshot_17.jpg

couchdb v2.0.0

not supported by vendor even with 86x computer... 

*Reporter*: zonetm
*E-mail*: [mailto:zone.nan...@gmail.com]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (COUCHDB-3242) Make get view group info timeout in couch_indexer configurable

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/COUCHDB-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15692133#comment-15692133
 ] 

ASF GitHub Bot commented on COUCHDB-3242:
-

GitHub user nickva opened a pull request:

https://github.com/apache/couchdb-couch-index/pull/20

Configurable timeout for view group get_info/1

A busy view group server might take longer than 5 seconds to respond, so 
make
the timeout configurable. "infinity" is also a valid configuration value.

Configuration section, key and default value (in milliseconds):

   `query_server_config.group_info_timeout = 5000`

COUCHDB-3242

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudant/couchdb-couch-index 
couchdb-3242-index-group-info-timeout

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-couch-index/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit f0a6854e578469612937a766632fdcdc52ee9c65
Author: Nick Vatamaniuc 
Date:   2016-11-24T04:05:00Z

Configurable timeout for view group get_info/1

A busy view group server might take longer than 5 seconds to respond, so 
make
the timeout configurable. "infinity" is also a valid configuration value.

Configuration section, key and default value (in milliseconds):

   `query_server_config.group_info_timeout = 5000`

COUCHDB-3242




> Make get view group info timeout in couch_indexer configurable
> --
>
> Key: COUCHDB-3242
> URL: https://issues.apache.org/jira/browse/COUCHDB-3242
> Project: CouchDB
>  Issue Type: Bug
>Reporter: Nick Vatamaniuc
>
> Some busy views will take longer than the default 5 seconds to return.
> https://github.com/cloudant/couchdb-couch-index/blob/master/src/couch_index.erl#L57-L58



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] couchdb-couch-index pull request #20: Configurable timeout for view group ge...

[nickva]

GitHub user nickva opened a pull request:

https://github.com/apache/couchdb-couch-index/pull/20

Configurable timeout for view group get_info/1

A busy view group server might take longer than 5 seconds to respond, so 
make
the timeout configurable. "infinity" is also a valid configuration value.

Configuration section, key and default value (in milliseconds):

   `query_server_config.group_info_timeout = 5000`

COUCHDB-3242

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudant/couchdb-couch-index 
couchdb-3242-index-group-info-timeout

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-couch-index/pull/20.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #20


commit f0a6854e578469612937a766632fdcdc52ee9c65
Author: Nick Vatamaniuc 
Date:   2016-11-24T04:05:00Z

Configurable timeout for view group get_info/1

A busy view group server might take longer than 5 seconds to respond, so 
make
the timeout configurable. "infinity" is also a valid configuration value.

Configuration section, key and default value (in milliseconds):

   `query_server_config.group_info_timeout = 5000`

COUCHDB-3242




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (COUCHDB-3242) Make get view group info timeout in couch_indexer configurable

[Nick Vatamaniuc (JIRA)]

Nick Vatamaniuc created COUCHDB-3242:


 Summary: Make get view group info timeout in couch_indexer 
configurable
 Key: COUCHDB-3242
 URL: https://issues.apache.org/jira/browse/COUCHDB-3242
 Project: CouchDB
  Issue Type: Bug
Reporter: Nick Vatamaniuc


Some busy views will take longer than the default 5 seconds to return.

https://github.com/cloudant/couchdb-couch-index/blob/master/src/couch_index.erl#L57-L58



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (COUCHDB-3146) Incorrect URI for DB with slash in name

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/COUCHDB-3146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15691757#comment-15691757
 ] 

ASF GitHub Bot commented on COUCHDB-3146:
-

GitHub user timmak opened a pull request:

https://github.com/apache/couchdb-fauxton/pull/813

encodeding url path for database name with special characters

Should resolve https://issues.apache.org/jira/browse/COUCHDB-3146


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/timmak/couchdb-fauxton COUCHDB-3146

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-fauxton/pull/813.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #813


commit efbd95427581aa5a5102fda6a017f53ad0ddf932
Author: Tim Pinington 
Date:   2016-11-24T00:16:46Z

encodeding url path for database name with special characters




> Incorrect URI for DB with slash in name
> ---
>
> Key: COUCHDB-3146
> URL: https://issues.apache.org/jira/browse/COUCHDB-3146
> Project: CouchDB
>  Issue Type: Bug
>  Components: Fauxton
>Affects Versions: 2.0.0, 1.7.0
>Reporter: Sergey Korobkov
>
> I have DB with name "test/test/test"
> And there is problem after creating/editing documents
> !http://storage8.static.itmages.com/i/16/0914/h_1473842714_1691024_f371ab4dd8.png!
> Link in DB name "test/test/test" is:*database/test/test/test/_all_docs*
> {quote}
>  href="database/test/test/test/_all_docs">test/test/test
> {quote}
> But it should be *database/test%2Ftest%2Ftest/_all_docs*
> The same problem with buttons "Save Changes" and "Cancel". After pushing this 
> button I am didn't return to document list.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] couchdb-fauxton pull request #813: encodeding url path for database name wit...

[timmak]

GitHub user timmak opened a pull request:

https://github.com/apache/couchdb-fauxton/pull/813

encodeding url path for database name with special characters

Should resolve https://issues.apache.org/jira/browse/COUCHDB-3146


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/timmak/couchdb-fauxton COUCHDB-3146

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-fauxton/pull/813.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #813


commit efbd95427581aa5a5102fda6a017f53ad0ddf932
Author: Tim Pinington 
Date:   2016-11-24T00:16:46Z

encodeding url path for database name with special characters




---
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 #214: Handle open_result message that arrives after the ...

[eiri]

Github user eiri commented on the issue:

https://github.com/apache/couchdb-couch/pull/214
  
+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.
---

[jira] [Resolved] (COUCHDB-3241) race condition in couch_server

[Robert Newson (JIRA)]

 [ 
https://issues.apache.org/jira/browse/COUCHDB-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Newson resolved COUCHDB-3241.

   Resolution: Fixed
Fix Version/s: 2.1.0

> race condition in couch_server
> --
>
> Key: COUCHDB-3241
> URL: https://issues.apache.org/jira/browse/COUCHDB-3241
> Project: CouchDB
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Robert Newson
> Fix For: 2.1.0
>
>
> It's possible to crash couch_server if the delete message for a database is 
> received before the asynchronous open_result message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (COUCHDB-3241) race condition in couch_server

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/COUCHDB-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690797#comment-15690797
 ] 

ASF GitHub Bot commented on COUCHDB-3241:
-

Github user asfgit closed the pull request at:

https://github.com/apache/couchdb-couch/pull/214


> race condition in couch_server
> --
>
> Key: COUCHDB-3241
> URL: https://issues.apache.org/jira/browse/COUCHDB-3241
> Project: CouchDB
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Robert Newson
>
> It's possible to crash couch_server if the delete message for a database is 
> received before the asynchronous open_result message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] couchdb-couch pull request #214: Handle open_result message that arrives aft...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/couchdb-couch/pull/214


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (COUCHDB-3241) race condition in couch_server

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/COUCHDB-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15690391#comment-15690391
 ] 

ASF GitHub Bot commented on COUCHDB-3241:
-

GitHub user rnewson opened a pull request:

https://github.com/apache/couchdb-couch/pull/214

Handle open_result message that arrives after the delete

Opening a database is asynchronous, therefore it's possible for the
database to have been deleted before the open is complete. The
open_result code assumes this doesn't happen, so when it does,
couch_server crashes, taking the couch_dbs ETS table with it.

Explicitly handle the case and keep on keeping on.

COUCHDB-3241

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudant/couchdb-couch 
3241-async-open-sync-delete

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-couch/pull/214.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #214


commit 54890e1b8f1d44225ed559ec53f7bf1f4402435b
Author: Robert Newson 
Date:   2016-11-23T15:20:11Z

Handle open_result message that arrives after the delete

Opening a database is asynchronous, therefore it's possible for the
database to have been deleted before the open is complete. The
open_result code assumes this doesn't happen, so when it does,
couch_server crashes, taking the couch_dbs ETS table with it.

Explicitly handle the case and keep on keeping on.

COUCHDB-3241




> race condition in couch_server
> --
>
> Key: COUCHDB-3241
> URL: https://issues.apache.org/jira/browse/COUCHDB-3241
> Project: CouchDB
>  Issue Type: Bug
>Affects Versions: 2.0.0
>Reporter: Robert Newson
>
> It's possible to crash couch_server if the delete message for a database is 
> received before the asynchronous open_result message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] couchdb-couch pull request #214: Handle open_result message that arrives aft...

[rnewson]

GitHub user rnewson opened a pull request:

https://github.com/apache/couchdb-couch/pull/214

Handle open_result message that arrives after the delete

Opening a database is asynchronous, therefore it's possible for the
database to have been deleted before the open is complete. The
open_result code assumes this doesn't happen, so when it does,
couch_server crashes, taking the couch_dbs ETS table with it.

Explicitly handle the case and keep on keeping on.

COUCHDB-3241

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cloudant/couchdb-couch 
3241-async-open-sync-delete

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-couch/pull/214.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #214


commit 54890e1b8f1d44225ed559ec53f7bf1f4402435b
Author: Robert Newson 
Date:   2016-11-23T15:20:11Z

Handle open_result message that arrives after the delete

Opening a database is asynchronous, therefore it's possible for the
database to have been deleted before the open is complete. The
open_result code assumes this doesn't happen, so when it does,
couch_server crashes, taking the couch_dbs ETS table with it.

Explicitly handle the case and keep on keeping on.

COUCHDB-3241




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (COUCHDB-3241) race condition in couch_server

[Robert Newson (JIRA)]

Robert Newson created COUCHDB-3241:
--

 Summary: race condition in couch_server
 Key: COUCHDB-3241
 URL: https://issues.apache.org/jira/browse/COUCHDB-3241
 Project: CouchDB
  Issue Type: Bug
Reporter: Robert Newson


It's possible to crash couch_server if the delete message for a database is 
received before the asynchronous open_result message.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] couchdb-fauxton pull request #812: remove doc_editor template

[garrensmith]

GitHub user garrensmith opened a pull request:

https://github.com/apache/couchdb-fauxton/pull/812

remove doc_editor template



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/garrensmith/couchdb-fauxton 
remove-doc_editor-template

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-fauxton/pull/812.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #812


commit eaa2286df8060cd03461a9377bf309bd89ac31cf
Author: Garren Smith 
Date:   2016-11-23T09:03:16Z

remove doc_editor template




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fauxton pull request #811: update react and react-bootstrap

[garrensmith]

Github user garrensmith closed the pull request at:

https://github.com/apache/couchdb-fauxton/pull/811


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fauxton issue #811: update react and react-bootstrap

[garrensmith]

Github user garrensmith commented on the issue:

https://github.com/apache/couchdb-fauxton/pull/811
  
Merging because this is green 
https://travis-ci.org/garrensmith/couchdb-fauxton/builds/178215661


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] couchdb-fauxton pull request #811: update react and react-bootstrap

[garrensmith]

GitHub user garrensmith opened a pull request:

https://github.com/apache/couchdb-fauxton/pull/811

update react and react-bootstrap



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/garrensmith/couchdb-fauxton dependency-updates

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/couchdb-fauxton/pull/811.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #811


commit dd5eb49780a032a897ca125d8a7227d6b1ea0b38
Author: Garren Smith 
Date:   2016-11-23T08:09:09Z

update react and react-bootstrap




---
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.
---