-
Notifications
You must be signed in to change notification settings - Fork 714
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
Docker build was fixed in PR #430, but versions >5.2.1 haven't been uploaded #544
Comments
Thanks @gabrielkrell! On the backlog ;) Happy New Year! |
Same to you! |
Hi @gabrielkrell, I hope all is well! It's been a while. I merged in #430 and it looks like there is still some issue with the Docker build. If you have a moment, I'd appreciate your insight. Thanks! With Best Regards, Elmer |
Hey @thinkingserious, I've been fine! Same to you; hope all are happy at Sendgrid :). I'll take a look, but it may be some time until I get to it - lots on the backlog right now. - Gabe |
Thanks! I hope a full backlog means that you are having a great time :) |
Any one working on this ? @gabrielkrell can you just guide me how to fix this ? |
I am about to look into this one, but before I do, are you already working on this @Warlord77? |
Closing this out as the root-level Dockerfile is now functioning properly. |
I seem to be having issues - I think this line requires a folder that's not in the repo. Line 6 in 50d50d2
I can't find a guide to using Docker on the repo either - all the links seem to be broken. |
@jonodrew This should help: https://github.com/sendgrid/sendgrid-python/blob/master/CONTRIBUTING.md#testing Which links are broken? |
In https://github.com/sendgrid/sendgrid-python/blob/master/FIRST_TIMERS.md#setting-up-the-development-environment, the link to USAGE.md is broken. With that being said, I then looked at that file and it seemed to be a guide to the API rather than how to set up the container? With that being said, once I'd run |
Looks like the language there was copied from the old CONTRIBUTING.md (and would have been referencing the old Docker usage file). The |
Old links have now been removed. |
Issue Summary
A weird bug was discovered in #426 and fixed in #430, but in the meantime builds for 4.2.1 and 4.3.0 failed. Is it possible to backport #430 to the old tags and then re-upload to Docker Hub?
Steps to Reproduce
(See the builds page.)
Technical details:
The rest of the builds were fine, but Docker was broken in builds 4.2.1 and 4.3.0. To get them up, you could:
Nontechnical details:
Happy New Year!
The text was updated successfully, but these errors were encountered: