Action trigger fails if granularity is removed
Bug #2026206 reported by
Terran McCanna
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned | ||
3.12 |
Fix Released
|
High
|
Unassigned |
Bug Description
Evergreen 3.10-ish
If an action trigger is saved with a granularity setting and then the granularity is removed, it saves it as an empty string instead of NULL, but the query generated by action_
SELECT "atev".id FROM action_
This results in events being created but getting stuck in Pending status and never completing.
Changed in evergreen: | |
assignee: | nobody → Mike Rylander (mrylander) |
Changed in evergreen: | |
status: | New → Confirmed |
tags: | added: pullrequest |
Changed in evergreen: | |
milestone: | 3.13.1 → 3.13.2 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've pushed a branch to working that addresses the "was NULL, now blank or all WS" granularity values by having the "get me events to work on" code understand that case in the one code path where we're looking for explicitly (and only) NULL granularity. See the top commit of:
https:/ /git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ miker/lp- 2026206- empty-granulari ty