unshiftio / recovery Goto Github PK

View Code? Open in Web Editor NEW

19.0 19.0 1.0 45 KB

Recover from a network failure using randomized exponential backoff.

Home Page: http://unshift.io

License: MIT License

JavaScript 100.00%

recovery's People

Contributors

Stargazers

Watchers

Forkers

ishan-marikar

recovery's Issues

Update docs

just a note :)

An in-range update of eventemitter3 is breaking the build 🚨

The dependency eventemitter3 was updated from `3.1.0` to `3.1.1`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eventemitter3 is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 18 commits.

5294132 [dist] 3.1.1
48ef1d6 [ts] Improve ListenerFn interface (#193)
bb9242b chore(package): update nyc to version 14.0.0 (#191)
a1a67ed chore(package): update mocha to version 6.1.0 (#190)
434f324 chore(package): update uglify-js to version 3.5.0 (#189)
ea0f703 chore(package): update assume to version 2.2.0 (#188)
5489d30 chore(package): update mocha to version 6.0.0 (#187)
7b2bbbb chore(package): update nyc to version 13.3.0 (#186)
639fc40 chore(package): update nyc to version 13.2.0 (#184)
991b945 chore(package): update sauce-browsers to version 2.0.0 (#177)
4591868 [test] Remove Opera from the list of browsers to test
0797470 [doc] Fix typo (#175)
e228f13 chore(package): update nyc to version 12.0.1 (#172)
64d4ef1 [test] Add deviceName field for Android
05ba925 [travis] Add node 10 and remove node 4

There are 18 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of inherits is breaking the build 🚨

The dependency inherits was updated from `2.0.3` to `2.0.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

inherits is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 6 commits.

9a2c294 2.0.4
48c7e72 .gitignore
018f73a package-lock.json
41dab1f update test to provide 100% coverage
dbade4c handle missing superCtor
f721d6b neveragain.tech pledge request

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of pre-commit is breaking the build 🚨

Version 1.2.1 of pre-commit just got published.

Branch	Build failing 🚨
Dependency	pre-commit
Current Version	1.2.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As pre-commit is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ coverage/coveralls Coverage pending from Coveralls.io Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 commits .

7d6feb1 [dist] 1.2.1
3ecafe0 [fix] chmod 0777 the newly created file; Fixes #88

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Using recovery guidlines on README may be incorrect

Code on README:

recovery = new Recovery();

recovery.on('reconnect', function (opts) {
  console.log(opts.attempt);

  reconnectmyconnection(function (err) {
    if (err) return reconnect.reconnected(err);
    reconnect.reconnected();
  });
});

recovery.reconnect();

I suppose the calls on object reconnect are meant to be recovery. Is that correct?

I would be glad to send a pull request if that is the case.

unshiftio / recovery Goto Github PK

recovery's People

Contributors

Stargazers

Watchers

Forkers

recovery's Issues

Update docs

An in-range update of eventemitter3 is breaking the build 🚨

The dependency eventemitter3 was updated from `3.1.0` to `3.1.1`.

An in-range update of inherits is breaking the build 🚨

The dependency inherits was updated from `2.0.3` to `2.0.4`.

An in-range update of pre-commit is breaking the build 🚨

Version 1.2.1 of pre-commit just got published.

Using recovery guidlines on README may be incorrect

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

Jobs

unshiftio / recovery Goto Github PK

recovery's People

Contributors

Stargazers

Watchers

Forkers

recovery's Issues

The dependency eventemitter3 was updated from 3.1.0 to 3.1.1.

The dependency inherits was updated from 2.0.3 to 2.0.4.

Version 1.2.1 of pre-commit just got published.

Recommend Projects

Recommend Topics

Recommend Org

Jobs

The dependency eventemitter3 was updated from `3.1.0` to `3.1.1`.

The dependency inherits was updated from `2.0.3` to `2.0.4`.