SIP2 failures with certain kinds of user standing penalties
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned |
Bug Description
Affects 2.10, master:
The new feature introduced in bug 1499123 enables Standing Penalties to have an Ignore Proximity.
Some of the SIP2 changes for this feature cause failures when a patron has certain kinds of standing penalties.
If you attempt to retrieve a patron that has a blocking standing penalty applied whose corresponding config.
Depending on your SIPServer personality, you'll either notice a failure to respond to patron info messages, or you may get an immediate disconnect.
When running SIPServer in non-daemon mode, you'll see something like this:
Can't locate object method "standing_penalty" via package "1" (perhaps you forgot to load "1"?) at /usr/local/
"1" will be the id of a standing penalty.
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Working branch with fix at user/jeff/ lp1592891- sip2-failures- with-standing- penalties
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ jeff/lp1592891- sip2-failures- with-standing- penalties