| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
insert a new reason was in place, but didn't let the new reason get used. Code to do this was already in place, just not utilized.
|
|
|
|
|
|
|
|
wasn't loading), causing the _X methods to fail on ->part_event. Only noticed when you retried events that had previously failed.
|
|
|
|
|
|
|
|
added on migrations (also: fixed implicit conditions like this which only apply to a subset of eventtables)
|
|
|
|
condition edit page renders again
|
|
|
|
|
|
condition check
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sure hope so
|
|
|
|
|
|
(closes 1863)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
this patch, also revert gratuitous whitespace changes
|
|
|
|
|
|
table option in access_user::agentnums_sql so this is easy to fix for other reports too)
|
|
therefore selecting all retryable events, and having to filter later. On a system with a running history, this caused bad O() types of situations for performance, especially bad when this was called by something that a user would be awaiting feedback from
|
