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

Internal Server Error will occur if I add type annotation to the route functions #1049

Closed
studio3104 opened this issue Jan 15, 2019 · 3 comments

Comments

@studio3104
Copy link
Contributor

studio3104 commented Jan 15, 2019

When I deployed after giving type annotation to my existing implementation as below, Internal Server Error occurred at all endpoints.

@app.route('/')
def index() -> Dict[str, str]:
    return {'hello': 'world'}

My deployment is done via a pipeline based on the definition generated by chalice generate-pipeline command.

Though I created a new environment to try to reproduce my issue, I could not make it reproduced. (I mean I could access to my API normally even if the method has type annotation.)

If I re-deploy the code that was deleted the type annotation via the existing pipeline, I can access normally without facing an Internal Server Error.

Submitting a reproduction code is difficult for me, but is there anything I can confirm else?

@studio3104
Copy link
Contributor Author

My local environment

$ chalice --version
chalice 1.6.2, python 3.7.1, darwin 17.7.0

@studio3104
Copy link
Contributor Author

I'm really sorry for making organizers bothering, but I got succeeded with 3.6.
Originally, 3.7 shouldn't have been supported for now, I tried with my custom code at the time...

@studio3104
Copy link
Contributor Author

Custom code is this #1045
Probably I need to close this PR as well...?

jamesls added a commit to jamesls/chalice that referenced this issue Jan 28, 2019
jamesls added a commit to jamesls/chalice that referenced this issue Jan 28, 2019
jamesls added a commit that referenced this issue Jan 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant