Merge ~epics-core/epics-base/+git/ralph:fix-1770292 into ~epics-core/epics-base/+git/epics-base:3.14
Proposed by
Ralph Lange
Status: | Merged |
---|---|
Approved by: | Ralph Lange |
Approved revision: | 2d9c5e99a191f15ca7d20a8546be922057eb9598 |
Merge reported by: | Ralph Lange |
Merged at revision: | 2d9c5e99a191f15ca7d20a8546be922057eb9598 |
Proposed branch: | ~epics-core/epics-base/+git/ralph:fix-1770292 |
Merge into: | ~epics-core/epics-base/+git/epics-base:3.14 |
Diff against target: |
57 lines (+12/-12) 3 files modified
src/db/dbAccess.c (+4/-4) src/rec/longinRecord.c (+4/-4) src/rec/longoutRecord.c (+4/-4) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Andrew Johnson | Approve | ||
Ralph Lange | Needs Resubmitting | ||
Review via email: mp+345368@code.launchpad.net |
Commit message
Fix for LaunchPad Bugs #1770292 and #1771298
Description of the change
Make get_alarm_double() for longin and longout records work the same as all other record types that implement level alarms.
To post a comment you must log in.
The change only affects integer type records.
Clients that use DBR_GR_<NATIVE> to get at the metadata will see no change on records that do not configure level alarms (as NaN will be converted to 0).
Clients that always use DBR_GR_DOUBLE metadata (like PyEpics) will see consistent behavior between double and integer type records with unconfigured value alarms.