Learn more about these different git repos.
Other Git URLs
Currently message queue is implemented via context, so each thread has its own queue. As queue needn't to be consumed before the EOL of httpd thread, messages can be silently dropped. Maybe separate db table should be used for this (maybe temporary one, but that is questionable).
PR #2441
Metadata Update from @tkopecek: - Custom field Size adjusted to None
As queue needn't to be consumed before the EOL of httpd thread
The context ThreadLocal object is cleared before and after each call. This was never a queue that persisted across calls. The context.protonmsg_msgs field was merely intended to buffer the messages during a single call so that they could be sent during the postCommit callback.
context
context.protonmsg_msgs
postCommit
In the postCommit handler, the plugin will try to send all messages from context.protonmsg_msgs. The only reason that these messages would not be consumed are:
Metadata Update from @tkopecek: - Issue tagged with: testing-ready
Commit 729f847 fixes this issue
Commit 8c25339 fixes this issue
Commit 30e8734 fixes this issue
Commit 5167fee relates to this ticket
Metadata Update from @jcupova: - Issue tagged with: testing-done
Login to comment on this ticket.