You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by glynnbird <gi...@git.apache.org> on 2016/10/26 13:22:23 UTC
[GitHub] couchdb-nano pull request #1: Dependencies update
GitHub user glynnbird opened a pull request:
https://github.com/apache/couchdb-nano/pull/1
Dependencies update
- updated dependencies to latest versions as this hadn't been done in a while
- tweaked the tests to ensure that they worked with the latest dependencies, chiefly expecting 'null' not 'undefined' from a call to the async library
- tweaked the tests so that they run against CouchDB 2.0 mainly avoiding change sequence number arithmetic
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/glynnbird/couchdb-nano dependencies
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-nano/pull/1.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 #1
----
commit 04386c17cdf66233b2c50b42e0bef1f59485d400
Author: Glynn Bird <gl...@gmail.com>
Date: 2016-10-26T09:51:56Z
version bump for dependencies
commit d1c7554c0a9ecbab2c7c4ad3616195d3da9bbbfc
Author: Glynn Bird <gl...@gmail.com>
Date: 2016-10-26T10:54:56Z
fix mocked tests
commit 45d58bfeb8b59ee97d1821ed9006c735fc65f4e4
Author: Glynn Bird <gl...@gmail.com>
Date: 2016-10-26T13:19:25Z
modified tests to work with latest dependencies and CouchDB 2.0
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-nano pull request #1: Dependencies update
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-nano/pull/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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-nano issue #1: Dependencies update
Posted by garrensmith <gi...@git.apache.org>.
Github user garrensmith commented on the issue:
https://github.com/apache/couchdb-nano/pull/1
ping @jhs and @jo. Is nano fully part of CouchDB now?
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-nano issue #1: Dependencies update
Posted by garrensmith <gi...@git.apache.org>.
Github user garrensmith commented on the issue:
https://github.com/apache/couchdb-nano/pull/1
@glynnbird this is how we test against couchdb 2.0 for Fauxton https://github.com/apache/couchdb-fauxton/blob/master/.travis.yml#L11-L16
It might be helpful for you
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-nano issue #1: Dependencies update
Posted by glynnbird <gi...@git.apache.org>.
Github user glynnbird commented on the issue:
https://github.com/apache/couchdb-nano/pull/1
^ the tests fail because they will be being performed against CouchDB 1.0. I'm working on that.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---