i tried to post this comment:
This was fixed by @gauravano and is now live!
On this page: https://publiclab.org/questions/stevie/08-14-2018/what-are-ways-to-monitor-algae-blooms#c20404
And got a 500 error. Not sure why -- need to pull the logs! If anyone can reproduce this locally we could probably fix quickly. Thanks for any help!
GET https://publiclab.org/comment/answer_create/1129?body=This+was+fixed+by+%40gauravano+and+is+now+live!&_=1535553099274 500 (Internal Server Error)
@jywarren!
I just went over to the question pointed by you - https://publiclab.org/questions/stevie/08-14-2018/what-are-ways-to-monitor-algae-blooms#c20404
The error shown is due to some interruption in completing the request but comments are created there if you visit the page, you will notice

I also tested by commenting here - https://publiclab.org/notes/gauravano/08-12-2018/gsoc-2018-final-work-product-of-draft-feature-and-email-integration-project#c20509 and its working for now.
This behavior was seen some days ago too by @ebarry too, she notified in the chatroom. At that time, Email service was down so the comment was created but also thrown 500 due to the interruption in the request(email sending failure). Also, when you tagged us all here - https://publiclab.org/notes/warren/08-21-2018/congratulations-on-a-great-2018-summer-of-code#c20445 . The Email service was down and so no email was sent to anyone mentioned. Did you experience this error at that time?
@jywarren
aha, so you think it's the email service being down that causes this? Yes,
that moment tagging you all sounds very similar. I did see a problem at
that time too.
On Wed, Aug 29, 2018 at 2:37 PM Gaurav Sachdeva notifications@github.com
wrote:
I also tested by commenting here -
https://publiclab.org/notes/gauravano/08-12-2018/gsoc-2018-final-work-product-of-draft-feature-and-email-integration-project#c20509
and its working for now.This behavior was seen some days ago too by @ebarry
https://github.com/ebarry too, she notified in the chatroom. At that
time, Email service was down so the comment was created but also thrown 500
due to the interruption in the request(email sending failure). Also, when
you tagged us all here -
https://publiclab.org/notes/warren/08-21-2018/congratulations-on-a-great-2018-summer-of-code#c20445
. The Email service was down and so no email was sent to anyone mentioned.
Did you experience this error at that time?@jywarren https://github.com/jywarren
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/3273#issuecomment-417059927,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABfJxqdmvXnXuiOv87UQE0mL67l8xY3ks5uVt85gaJpZM4WRrkX
.
yes, email service being down seems to be one of the reason.
Do you think we can use Redis to solve this, we can enqueue our emails using redis, this will also decrease the page loading time after signup or after every operation where response waits for email to be sent. We should only use this solution if Redis is working stable at all times.
Has Redis been quite stable, or at least more stable than mailman? @icarito
?
On Wed, Aug 29, 2018 at 3:32 PM Gaurav Sachdeva notifications@github.com
wrote:
yes, email service being down seems to be one of the reason.
Do you think we can use Redis to solve this, we can enqueue our emails
using redis, this will also decrease the page loading time after signup or
after every operation where response waits for email to be sent. We should
only use this solution if Redis is working stable at all times.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/3273#issuecomment-417076731,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABfJ-PSCWuewS4UKOkCPA6q_1fPwDFcks5uVuwQgaJpZM4WRrkX
.
I haven't seen this happen recently...
OK noting that this mailman monitoring project is ongoing here: https://github.com/publiclab/plots2/issues/3208
Sorry, i meant #3040
Closing in favor of that issue!