Skip to content
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

Nits in server config to get rosetta-cli started #5799

Merged
merged 2 commits into from
Aug 28, 2020

Conversation

bkase
Copy link
Member

@bkase bkase commented Aug 28, 2020

  • Version number bumped
  • Server more robust to disconnecting clients
  • Errors has consistent schema for languages lacking sum types
  • Adds rosetta.conf

From the CodaProtocol/rosetta-cli fork:

rosetta-cli --configuration-file rosetta.conf check:data
deterministically fails after having made it through some initial validation

* Version number bumped
* Server more robust to disconnecting clients
* Errors has consistent schema for languages lacking sum types
* Adds rosetta.conf

From the CodaProtocol/rosetta-cli fork:

`rosetta-cli --configuration-file rosetta.conf check:data`
deterministically fails after having made it through some initial validation
@bkase bkase requested a review from a team as a code owner August 28, 2020 17:11
Base automatically changed from rosetta/delegation-in-test-agent to develop August 28, 2020 20:03
@bkase bkase added ci-build-me Add this label to trigger a circle+buildkite build for this branch ready-to-merge Adding this label will trigger mergify and trigger CI to run and merge the PR labels Aug 28, 2020
@bkase bkase merged commit 0f589cf into develop Aug 28, 2020
@bkase bkase deleted the rosetta/nits-in-server-config branch August 28, 2020 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-build-me Add this label to trigger a circle+buildkite build for this branch ready-to-merge Adding this label will trigger mergify and trigger CI to run and merge the PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants