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

Use public interface to get signing seed length #35

Closed
wants to merge 1 commit into from

Conversation

@dchest
Copy link
Contributor

dchest commented Jan 14, 2017

No description provided.

@ayumi
Copy link
Contributor

ayumi commented Jan 14, 2017

Thank you for the patch :)
I saw the tests failed in Travis, so I ran them locally and they passed.

@diracdeltas could you have a look?

@ayumi ayumi requested a review from diracdeltas Jan 14, 2017
@diracdeltas
Copy link
Member

diracdeltas commented Jan 15, 2017

@diracdeltas
Copy link
Member

diracdeltas commented Jan 15, 2017

i've restarted the Travis build 3 times and each time it failed with:

# client RequestUtil
# constructor
Connecting to http://localhost:4000
not ok 30 Error: Credential server response 500
  ---
    operator: error
    expected: |-
      undefined
    actual: |-
      [Error: Credential server response 500]
    at: Test.assert [as _assert] (http://localhost:40495/bundle.js:47:28326)
    stack: |-
      Error: Credential server response 500
          at window.fetch.then.response (http://localhost:40495/bundle.js:52:20779)
  ...

so it doesn't seem to be an intermittent fail. i have no idea how this change could lead to that error. :/

diracdeltas added a commit that referenced this pull request Jan 15, 2017
Same as #35
@diracdeltas
Copy link
Member

diracdeltas commented Jan 15, 2017

Somehow, #36 passes even though it is the exact same change :/. I am going to close this PR in favor of that. 🔮 👻

@ayumi
Copy link
Contributor

ayumi commented Jan 15, 2017

@diracdeltas We use travis encrypted env vars to do the AWS tests, which for security only work when collaborators initiate the build.

@diracdeltas
Copy link
Member

diracdeltas commented Jan 15, 2017

@ayumi o i c

i assume the merged branches will pass Travis since merge commits are done by collaborators, but is there a way to fix it so that outside contributor PR's don't always show up as failing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.