-
Notifications
You must be signed in to change notification settings - Fork 71
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
Refactor to use aiobotocore, python3 and tornado 7 #147
Conversation
the build is failing because the thumbor-dev docker image used for building and testing is using python2 instead of python3. the docker image is built using https://github.com/Bladrak/docker-thumbor-dev/blob/master/Dockerfile. can we move over the project under thumbor-community as well? i can help set it up with python3 in that case so we can move this pr forward. |
Hi @bagipriyank sorry for the delay, I I'll take a look at this docker image issue. |
You should be able to switch to https://hub.docker.com/r/bladrak/thumbor-dev-py3 (which is essentially the same image as before, but for python 3 :) ) |
Done. |
@bagipriyank feel free to work on top of this PR. |
BC Breaks should be documented (for instance the removal of the presigning loader) |
stupid question, how do i push changes to this pull request? |
I don't think you can unless you are maintainer of this repository. You can open a parallel pull request I suppose. |
It's possible if you give @bagipriyank write access to your forked repo @amanagr :) |
another option is to close this pr, push @amanagr's changes to a branch |
@bagipriyank sounds good to me. |
@bagipriyank any update on this? |
Any news on reviewing and integrating this? |
Needed here too. Any news ? |
Also looking for this. Is it possible to get a release here before thumbor 7.0 is stable? |
FYI -- when running this code I see this error for each request
|
Would it be possible to publish a prerelease with these changes? Initial testing looks good, but before I promote this to our staging environment it would be nice to be able to at least refer to a tag or branch in this repository instead of the fork. |
Not sure I can since the branch is not on this repo. |
@Bladrak Do you not have the correct permissions to merge this PR or? If you're maintainer you should be able to merge a PR afaik. |
@peterrus the MR is still a WIP, as it's not passing the tests and there are some feedbacks to take into account. So I can't merge it until it's stable (or I risk having a master branch unstable). |
@Bladrak of course, I understand, apologies. I did not see the feedback in #142. I gave this branch a try in a test environment and saw no regression in functionality except the issues regarding unclosed connections that @jimas14 has fixed in amanagr#1. Running from that branch solved that as well. Just some feedback (: Furthermore it seems this branch has locked |
Thanks for the feedback @peterrus :-) Would you be able to submit a new PR with the fixes you've mentioned? As soon as this is passing and the feedbacks are documented, I'm willing to merge :) |
Hi @Bladrak I did not do any fixes except for installing some packages through pip. I am just using I am not sure if I feel confident enough in fixing the issues from the feedback of #142 as I have never worked on either Thumbor's or this plugins sources before unfortunately. |
If we get the two referenced PR's ⬆️ merged we should have working unit tests both locally and on CircleCI again. |
I switched the base branch of this from master to py3 so we can pre-release it, merging it as is, considering py3 is an unstable branch |
Seems that not all relevant commits have been merged:
error message disappear if i use direclty: |
You are right @mello7tre. Seems amanagr#1 was not merged into |
Thanks. |
Yes indeed, if someone can open a PR on this repo for amanagr#1 into the |
Thanks, merged! |
This is #142 without the last commit which tries to use aiobotocore's context manager approach and this PR uses aiobotocore v0.12.
Testing on s3 worked fine for me.