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

Blueprint registration #1061

Merged
merged 3 commits into from Apr 27, 2015

Conversation

Projects
None yet
4 participants
@llllllllll
Member

llllllllll commented Apr 24, 2015

Looking back at the blueprint change I made; I don't think it made it much easier to actually pull the endpoints into another app because of how I did the data registration. This change makes it so that registering the api blueprint adds both the endpoints and the data itself so that it is a single step. This also updates the docs to show the corrected usage.

This makes it much easier to take these endpoints and put them on an app that you want to feed into gunicorn or something.

@cpcloud cpcloud modified the milestones: 0.9.0, 0.8.1 Apr 24, 2015

@cpcloud cpcloud self-assigned this Apr 24, 2015

@llllllllll

This comment has been minimized.

Member

llllllllll commented Apr 25, 2015

Any idea why that one test died only on py2.7 with spark 1.2? Transient error?

@cpcloud

This comment has been minimized.

Member

cpcloud commented Apr 25, 2015

yep, just rehash and push to restart the build

git commit --amend -C HEAD && git push --force
@mrocklin

This comment has been minimized.

Member

mrocklin commented Apr 25, 2015

travis.ci also has a restart button

On Sat, Apr 25, 2015 at 5:37 AM, Phillip Cloud notifications@github.com
wrote:

yep, just rehash and push to restart the build

git commit --amend -C HEAD && git push --force


Reply to this email directly or view it on GitHub
#1061 (comment).

@llllllllll llllllllll force-pushed the quantopian:blueprint-registration branch from 9aa7faf to 77d657f Apr 26, 2015

@llllllllll

This comment has been minimized.

Member

llllllllll commented Apr 26, 2015

Where is the restart button, or is it only available to repo owners/collaborators?

@cpcloud

This comment has been minimized.

Member

cpcloud commented Apr 26, 2015

There's nothing wrong with rehashing the commit and then force pushing. Additionally, @llllllllll rehashing and pushing doesn't depend on you having access rights to the travis build.

@cowlicks

This comment has been minimized.

Contributor

cowlicks commented Apr 27, 2015

@llllllllll Closing and reopening the PR will also trigger a re-test. In case you don't want to sign in/register with travis-ci.

@llllllllll

This comment has been minimized.

Member

llllllllll commented Apr 27, 2015

Oh, I already have an account with travis; however, idk how to restart a test in their UI.

@cpcloud

This comment has been minimized.

Member

cpcloud commented Apr 27, 2015

looks good to me, merging

cpcloud added a commit that referenced this pull request Apr 27, 2015

@cpcloud cpcloud merged commit 6be1d10 into blaze:master Apr 27, 2015

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@llllllllll

This comment has been minimized.

Member

llllllllll commented Apr 27, 2015

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment