char0n / django-gearman-proxy

Proxy backends/workers for asynchronous email and sms sending using gearman as message queue.

Hi 👋

Vladimír Gorej is a Prague-based software engineer passionate about software/code quality, Functional and Reactive programming. Vladimír is formerly Technical Team Lead of Oracle, Principal Software Engineer at Apiary and held other senior engineering and leading roles in international companies like Ubiquiti Networks or SecurityScorecard. He's been active in the Open Source community for the last ten years and currently utilizes his experience in this field as an Open Source Software Engineer at SmartBear. Vladimír holds all OpenSource Best Practices certifications awarded by The Linux Foundation and is a member of the GitHub Stars program. His favorite programming languages include JavaScript, Python, and Elixir.

❤️ Sponsor me through GitHub

Latest Blog Posts

Advanced memoization for JavaScript functions with lodash.memoize

Sat Feb 05 2022

---

How to handle errors in SwaggerUI

Mon Jan 24 2022

---

How to migrate from querystring to URLSearchParams in Node.js

Thu Oct 14 2021

---

How to apply the Apache 2.0 License to your Open Source software project

Sat Oct 02 2021

---

Things I have learned while maintaining JavaScript monorepo with Lerna

Tue Sep 07 2021

---

➡️ More blog posts

GitHub Stats

django-gearman-proxy's Issues

Cannot handle attachments

msg = EmailMessage('message', 'body', '[email protected]', ['[email protected]',])
msg.attach('contract.pdf', contract, 'application/pdf')
msg.send()

Will break the serialization process:

File "/home/rsmol/.virtualenvs/aukcejinak-website/lib/python2.7/site-packages/django_gearman_proxy/serializers/mail/json.py", line 25, in serialize
    'connection': django_gearman_proxy.settings.GEARMAN_EMAIL_BACKEND
  File "/usr/lib64/python2.7/json/__init__.py", line 243, in dumps
    return _default_encoder.encode(obj)

Cyclic recursion

When using email backend, and no valid gearman connection is found during submitting gearman job to send new email and you are also using django.utils.log.AdminEmailHandler logging handler, new email is geneated and applicated try to notifiy admins about this error thru AdminEmailHandler. This will trigger submittion of another gearman job to send new email, that will trigger another error. This way errors are triggered in never ending loop, that will eventualy consume system and disk resources on machine that django-gearman-proxy is used.

Project requirements

Add python-gearman library as requirement to README. Also running gearman server is required.