EPICS Home

Experimental Physics and Industrial Control System


 
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  2025  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  2025 
<== Date ==> <== Thread ==>

Subject: [Bug 2029482] [NEW] pvget json error
From: Matt Clarke via Core-talk <core-talk at aps.anl.gov>
To: core-talk at aps.anl.gov
Date: Thu, 03 Aug 2023 12:22:36 -0000
Public bug reported:

I’ve been using `pvget -M json` and have noticed a problem with it when
the PV has the alarm fields set like so:

double lowAlarmLimit nan
double lowWarningLimit nan
double highWarningLimit nan
double highAlarmLimit nan

When I run pvget I get the following:

> pvget -M json IOC:m1.RBV
IOC:m1.RBV {"value":88.129999999999995,"alarm":{"severity":0,"status":0,"message":"NO_ALARM"},"timeStamp":{"secondsPastEpoch":1691063460,"nanoseconds":182366000,"userTag":0},"display":{"limitLow":-100.0,"limitHigh":100.0,"description":"motor 1","units":"degrees","precision":5,"form":{"index":0,"choices":["Default","String","Binary","Decimal","Hex","Exponential","Engineering"]}},"control":{"limitLow":-100.0,"limitHigh":100.0,"minStep":0.0},"valueAlarm":{"active":false,"lowAlarmLimit"Error in monitor handler : yajl_gen_invalid_number

It looks like YAJL doesn’t like the nan values. If I set them to non-nan
values then the error goes away.

This is with base 7.0.7.

** Affects: epics-base
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/2029482

Title:
  pvget json error

Status in EPICS Base:
  New

Bug description:
  I’ve been using `pvget -M json` and have noticed a problem with it
  when the PV has the alarm fields set like so:

  double lowAlarmLimit nan
  double lowWarningLimit nan
  double highWarningLimit nan
  double highAlarmLimit nan

  When I run pvget I get the following:

  > pvget -M json IOC:m1.RBV
  IOC:m1.RBV {"value":88.129999999999995,"alarm":{"severity":0,"status":0,"message":"NO_ALARM"},"timeStamp":{"secondsPastEpoch":1691063460,"nanoseconds":182366000,"userTag":0},"display":{"limitLow":-100.0,"limitHigh":100.0,"description":"motor 1","units":"degrees","precision":5,"form":{"index":0,"choices":["Default","String","Binary","Decimal","Hex","Exponential","Engineering"]}},"control":{"limitLow":-100.0,"limitHigh":100.0,"minStep":0.0},"valueAlarm":{"active":false,"lowAlarmLimit"Error in monitor handler : yajl_gen_invalid_number

  It looks like YAJL doesn’t like the nan values. If I set them to non-
  nan values then the error goes away.

  This is with base 7.0.7.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/2029482/+subscriptions


Replies:
[Bug 2029482] Re: pvget json error Andrew Johnson via Core-talk
[Bug 2029482] Re: pvget json error Matt Clarke via Core-talk
[Bug 2029482] Re: pvget json error Andrew Johnson via Core-talk
[Bug 2029482] Re: pvget json error Matt Clarke via Core-talk
[Bug 2029482] Re: pvget json error Andrew Johnson via Core-talk
[Bug 2029482] Re: pvget json error Matt Clarke via Core-talk

Navigate by Date:
Prev: Re: What is the next step for RTEMS and EPICS? Does a small (virtual) workshop make sense? Chris Johns via Core-talk
Next: Re: What is the next step for RTEMS and EPICS? Does a small (virtual) workshop make sense? Andrew Johnson via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  2025 
Navigate by Thread:
Prev: Build failed: EPICS Base 7 base-7.0-981 AppVeyor via Core-talk
Next: [Bug 2029482] Re: pvget json error Andrew Johnson via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  2025