GitHub user KlausTrainer opened a pull request:

    https://github.com/apache/couchdb-chttpd/pull/94

    Fix return types of responses to view requests

    This fixes an issue that was introduced with 72258e2 and e5b1aee.
    
    Background:
    
    Although all things still seemed to work, each request to a view
    generated an exception with the following stack trace:
    
    ```
    exception error: undefined function vacc:get/2
      in function  chttpd:result/2 (src/chttpd.erl, line 297)
      in call from chttpd:handle_request_int/1 (src/chttpd.erl, line 276)
      in call from mochiweb_http:headers/6 (src/mochiweb_http.erl, line 122)
    ```

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

    $ git pull https://github.com/KlausTrainer/couchdb-chttpd 
fix-exception-error-on-view-requests

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

    https://github.com/apache/couchdb-chttpd/pull/94.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 #94
    
----
commit a57e86994f6f5610edc3dca31ca373db92306d8b
Author: Klaus Trainer <[email protected]>
Date:   2015-11-02T22:12:04Z

    Fix return types of responses to view requests
    
    This fixes an issue that was introduced with 72258e2 and e5b1aee.
    
    Background:
    
    Although all things still seemed to work, each request to a view
    generated an exception with the following stack trace:
    
    ```
    exception error: undefined function vacc:get/2
      in function  chttpd:result/2 (src/chttpd.erl, line 297)
      in call from chttpd:handle_request_int/1 (src/chttpd.erl, line 276)
      in call from mochiweb_http:headers/6 (src/mochiweb_http.erl, line 122)
    ```

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to