couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-2321) It's possible to delete config section while it still has some options (UI bug)
Date Sat, 06 Sep 2014 11:17:29 GMT


ASF subversion and git services commented on COUCHDB-2321:

Commit db58e794f937a52b6b61c964942e56afa7d03d8b in couchdb-couch's branch refs/heads/master
from [~paul.joseph.davis]
[;h=db58e79 ]

Fix bugs with couch_proc_manager limits

This fixes the couch_proc_manager limit counting by rearranging the increment and decrements
when processes are created and destroyed. It ensures that each time we remove a process from
the ets table that we decrement appropriately.

For incrementing, things are a bit more complicated in that we need to increment before inserting
to the table. This is so that our hard limit applies even if one of our asynchronous spawn
calls is opening a new process. This is accomplished by incrementing the counter and storing
the async open call information in a new ets table. If the open is successful the counter
is left untouched. If the open fails then we need to decrement the counter.

This also simplifies starting waiting clients when a processes is either returned, exits,
or fails to start by isolating the logic and calling it in each place as necessary.

Closes COUCHDB-2321

> It's possible to delete config section while it still has some options (UI bug)
> -------------------------------------------------------------------------------
>                 Key: COUCHDB-2321
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Alexander Shorin
>            Assignee: Robert Kowalski
> 1. Create a new section abc with option bar = baz
> 2. Add another option to section abc like boo = foo
> 3. Delete option bar. You'll see the following picture:

This message was sent by Atlassian JIRA

View raw message