-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure service lookup works well with versions #47
Labels
Comments
SlavoKrupa
added a commit
to SlavoKrupa/SilverWare
that referenced
this issue
Nov 5, 2016
SlavoKrupa
added a commit
to SlavoKrupa/SilverWare
that referenced
this issue
Nov 6, 2016
SlavoKrupa
added a commit
to SlavoKrupa/SilverWare
that referenced
this issue
Nov 6, 2016
SlavoKrupa
added a commit
to SlavoKrupa/SilverWare
that referenced
this issue
Nov 6, 2016
SlavoKrupa
added a commit
to SlavoKrupa/SilverWare
that referenced
this issue
Nov 6, 2016
…cluster lookup - Versioning uses semver4j from https://github.com/vdurmont/semver4j in npm mode. It allows wider range of queries to be executed and rules for the version format is not so strict. i.e - major and patch versions are not required. see - https://github.com/npm/node-semver for more information. Process of resolving versions is described in VersionResolver. - Fix for cluster when main node of the cluster fails. - Cluster lookup now provides more clear information about a result of a lookup.
SlavoKrupa
added a commit
to SlavoKrupa/SilverWare
that referenced
this issue
Nov 6, 2016
…cluster lookup - Versioning uses semver4j from https://github.com/vdurmont/semver4j in npm mode. It allows wider range of queries to be executed and rules for the version format is not so strict. i.e - major and patch versions are not required. see - https://github.com/npm/node-semver for more information. Process of resolving versions is described in VersionResolver. - Fix for cluster when main node of the cluster fails. - Cluster lookup now provides more clear information about a result of a lookup.
marvec
pushed a commit
that referenced
this issue
Nov 8, 2016
- Versioning uses semver4j from https://github.com/vdurmont/semver4j in npm mode. It allows wider range of queries to be executed and rules for the version format is not so strict. i.e - major and patch versions are not required. see - https://github.com/npm/node-semver for more information. Process of resolving versions is described in VersionResolver. - Fix for cluster when main node of the cluster fails. - Cluster lookup now provides more clear information about a result of a lookup.
RadekKoubsky
pushed a commit
to RadekKoubsky/SilverWare
that referenced
this issue
Nov 12, 2016
…cluster lookup - Versioning uses semver4j from https://github.com/vdurmont/semver4j in npm mode. It allows wider range of queries to be executed and rules for the version format is not so strict. i.e - major and patch versions are not required. see - https://github.com/npm/node-semver for more information. Process of resolving versions is described in VersionResolver. - Fix for cluster when main node of the cluster fails. - Cluster lookup now provides more clear information about a result of a lookup.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently version numbers in the service lookup queries are ignored. Implement this and test it thoroughly.
The text was updated successfully, but these errors were encountered: