Robert Kowalski (JIRA | 24 Oct 22:56 2014
Picon

[jira] [Assigned] (COUCHDB-708) Newlines in document locations break header parsing


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

Robert Kowalski reassigned COUCHDB-708:
---------------------------------------

    Assignee: Robert Kowalski

> Newlines in document locations break header parsing
> ---------------------------------------------------
>
>                 Key: COUCHDB-708
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-708
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.10.1
>         Environment: ubuntu
>            Reporter: Tim
>            Assignee: Robert Kowalski
>            Priority: Critical
>         Attachments: couchdb-urlencode-location.patch
>
>
> Newlines in document locations break header parsing. Potential header injection issues?
> $ curl -X DELETE http://localhost:5984/testdb
> {"ok":true}
> $ curl -X PUT http://localhost:5984/testdb
> {"ok":true}
(Continue reading)

Joan Touzet (JIRA | 24 Oct 22:30 2014
Picon

[jira] [Created] (COUCHDB-2405) Improve _active_tasks endpoint with filter query string parameters

Joan Touzet created COUCHDB-2405:
------------------------------------

             Summary: Improve _active_tasks endpoint with filter query string parameters
                 Key: COUCHDB-2405
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2405
             Project: CouchDB
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: HTTP Interface
            Reporter: Joan Touzet

As an Fauxton developer, I'd like to specify type, node and range filters on /_active_tasks to be able to
improve Dashboard support for visualising long-running CouchDB cluster tasks.

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

Ben Keen (JIRA | 24 Oct 21:37 2014
Picon

[jira] [Created] (COUCHDB-2404) Make second nav column consistently appear for all Database pages

Ben Keen created COUCHDB-2404:
---------------------------------

             Summary: Make second nav column consistently appear for all Database pages
                 Key: COUCHDB-2404
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2404
             Project: CouchDB
          Issue Type: Improvement
      Security Level: public (Regular issues)
          Components: Fauxton
            Reporter: Ben Keen

Right now when you select a DB and click on the various sub-pages that appear in the second column, sometimes
the column stays there, sometimes it disappears (Permissions, Compact & Clean). Change this so that the
second column always shows up for all subpages.

This is an interesting one, architecture-wise. Those 2 pages - Permissions, Compact & Clean - are separate
components, and the sidebar content is found in the Documents addon. Suggestions on how to tackle this
very welcome!

btw, I spoke to Sean Barclay about this and got his thumbs up. 

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

Ben Keen (JIRA | 24 Oct 21:37 2014
Picon

[jira] [Updated] (COUCHDB-2404) Make second nav column consistently appear for all Database pages


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

Ben Keen updated COUCHDB-2404:
------------------------------
    Priority: Minor  (was: Major)

> Make second nav column consistently appear for all Database pages
> -----------------------------------------------------------------
>
>                 Key: COUCHDB-2404
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2404
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Ben Keen
>            Assignee: Ben Keen
>            Priority: Minor
>
> Right now when you select a DB and click on the various sub-pages that appear in the second column,
sometimes the column stays there, sometimes it disappears (Permissions, Compact & Clean). Change this
so that the second column always shows up for all subpages.
> This is an interesting one, architecture-wise. Those 2 pages - Permissions, Compact & Clean - are
separate components, and the sidebar content is found in the Documents addon. Suggestions on how to
tackle this very welcome!
> btw, I spoke to Sean Barclay about this and got his thumbs up. 

--
(Continue reading)

Ben Keen (JIRA | 24 Oct 21:37 2014
Picon

[jira] [Assigned] (COUCHDB-2404) Make second nav column consistently appear for all Database pages


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

Ben Keen reassigned COUCHDB-2404:
---------------------------------

    Assignee: Ben Keen

> Make second nav column consistently appear for all Database pages
> -----------------------------------------------------------------
>
>                 Key: COUCHDB-2404
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2404
>             Project: CouchDB
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Ben Keen
>            Assignee: Ben Keen
>
> Right now when you select a DB and click on the various sub-pages that appear in the second column,
sometimes the column stays there, sometimes it disappears (Permissions, Compact & Clean). Change this
so that the second column always shows up for all subpages.
> This is an interesting one, architecture-wise. Those 2 pages - Permissions, Compact & Clean - are
separate components, and the sidebar content is found in the Documents addon. Suggestions on how to
tackle this very welcome!
> btw, I spoke to Sean Barclay about this and got his thumbs up. 

--
(Continue reading)

Ben Keen (JIRA | 24 Oct 21:28 2014
Picon

[jira] [Updated] (COUCHDB-2400) Add constants.js file to Fauxton core


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

Ben Keen updated COUCHDB-2400:
------------------------------
    Priority: Minor  (was: Major)

> Add constants.js file to Fauxton core
> -------------------------------------
>
>                 Key: COUCHDB-2400
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2400
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Ben Keen
>            Assignee: Ben Keen
>            Priority: Minor
>
> We hardcode things like JS fade in/out speeds in a lot of places. Add a constants.js file to the core and
expose it via FauxtonAPI (or maybe app...). That can contain app-wide constants like these.

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

Robert Kowalski (JIRA | 24 Oct 18:15 2014
Picon

[jira] [Commented] (COUCHDB-2357) Logout link disappears from sidebar on browser reload


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

Robert Kowalski commented on COUCHDB-2357:
------------------------------------------

it is 2.0 - we decided that the current Fauxton breaks backward compability to CouchDB 1.x to focus on the 2.0
release: http://markmail.org/search/?q=Fauxton%20compatibility%20with%20CouchDB%201.x#query:Fauxton%20compatibility%20with%20CouchDB%201.x%20list%3Aorg.apache.couchdb.dev+page:1+mid:psrn2zdaiyuvebc4+state:results

> Logout link disappears from sidebar on browser reload
> -----------------------------------------------------
>
>                 Key: COUCHDB-2357
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2357
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Javier Candeira
>
> The Logout link disappears from the Fauxton sidebar on reloading the current URL in the browser.
> It reappears if the user logs out manually (by adding the edited fragment `#logout` by hand on the address
bar and hitting <Enter>) and logs in again.
> This has been observed in the following branches:
> master
> sidebar-fixes
> Update-Sidebar

(Continue reading)

Michael Cole (JIRA | 24 Oct 16:54 2014
Picon

[jira] [Commented] (COUCHDB-2403) Build Fauxton for a different url paths?


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

Michael Cole commented on COUCHDB-2403:
---------------------------------------

Hi [~garren], thanks for the help :-)

Fauxton build with relative paths would be awesome!

See this issue for more context on how we'd use it:  https://github.com/pouchdb/express-pouchdb/issues/116

Thanks!

> Build Fauxton for a different url paths?
> ----------------------------------------
>
>                 Key: COUCHDB-2403
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2403
>             Project: CouchDB
>          Issue Type: Question
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Michael Cole
>
> Hey, I'm trying to use Fauxton in another project:  express-pouchdb
> We'd like Fauxton to not know it's URL, until it's being served.  So someone could configure a PouchDB
server in Express at their [own
(Continue reading)

Garren Smith (JIRA | 24 Oct 16:32 2014
Picon

[jira] [Commented] (COUCHDB-2403) Build Fauxton for a different url paths?


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

Garren Smith commented on COUCHDB-2403:
---------------------------------------

Hi  <at> michaelcole, The correct way to do this is by setting the settings.json file. That is what it is there
for. You can edit the app.root and app.host parameters to fit your needs. It only works once you rebuild
fauxton though.

It that doesn't quite fit your needs we might have to look at making the url a little more generic but thats a
little tricky for how Fauxton works.

> Build Fauxton for a different url paths?
> ----------------------------------------
>
>                 Key: COUCHDB-2403
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2403
>             Project: CouchDB
>          Issue Type: Question
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Michael Cole
>
> Hey, I'm trying to use Fauxton in another project:  express-pouchdb
> We'd like Fauxton to not know it's URL, until it's being served.  So someone could configure a PouchDB
server in Express at their [own
URL](https://github.com/MichaelJCole/express-pouchdb#example-usage) like this:
(Continue reading)

Alexander Shorin (JIRA | 24 Oct 16:19 2014
Picon

[jira] [Updated] (COUCHDB-2403) Build Fauxton for a different url paths?


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

Alexander Shorin updated COUCHDB-2403:
--------------------------------------
    Issue Type: Question  (was: Bug)

> Build Fauxton for a different url paths?
> ----------------------------------------
>
>                 Key: COUCHDB-2403
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2403
>             Project: CouchDB
>          Issue Type: Question
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Michael Cole
>
> Hey, I'm trying to use Fauxton in another project:  express-pouchdb
> We'd like Fauxton to not know it's URL, until it's being served.  So someone could configure a PouchDB
server in Express at their [own
URL](https://github.com/MichaelJCole/express-pouchdb#example-usage) like this:
> /mydb/  <-- PouchDB server
> /mydb/_utils  <-- Fauxton
> The best I could figure out to do was hard-
> code the URL in settings.json and use `grunt release` to build Fauxton for that specific URL.
> Is there a better way?
> Thanks!
> Mike
(Continue reading)

Jan Lehnardt (JIRA | 24 Oct 16:16 2014
Picon

[jira] [Commented] (COUCHDB-2403) Build Fauxton for a different url paths?


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

Jan Lehnardt commented on COUCHDB-2403:
---------------------------------------

[~kxepal] JIRA is fine for asking dev related questions.

[~michaelcole] at this point I’m not aware of any other solution, maybe some of the Fauxton devs have more
insight (I’m only looking at Fauxton from a packaging perspective and I have had to change the URL too :)
CC [~garren] [~deathbear] [~robertkowalski]

> Build Fauxton for a different url paths?
> ----------------------------------------
>
>                 Key: COUCHDB-2403
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2403
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Michael Cole
>
> Hey, I'm trying to use Fauxton in another project:  express-pouchdb
> We'd like Fauxton to not know it's URL, until it's being served.  So someone could configure a PouchDB
server in Express at their [own
URL](https://github.com/MichaelJCole/express-pouchdb#example-usage) like this:
> /mydb/  <-- PouchDB server
(Continue reading)


Gmane