Certain holds cannot be manually retargeted (reset)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Triaged
|
Undecided
|
Unassigned |
Bug Description
EG 2.1
PostgreSQL 9.0.4
I've come across a couple instances where manually retargeting a hold seems to do nothing. I've further found that the prev_check_time does not change.
I believe it's related to a logged error noting:
Processing of hold failed: Can't call method "count" without a package or object reference at /usr/local/
That piece of code deals with part holds, and the count is from: $_->part_
I haven't been able to track down any pattern to the problem, and have not been able to reproduce it on demand. It's only when staff discover a hold that "won't capture", that I find one. Manually removing the prev_check_time seems to resolve the individual problem.
Changed in evergreen: | |
status: | New → Incomplete |
Changed in evergreen: | |
status: | Incomplete → Triaged |
tags: | added: holds |
tags: |
added: circ-holds removed: holds |
I'm cautiously marking this one Incomplete since we have not seen it happen in our consortium and there has been no additional confirmation.