EPICS Controls Argonne National Laboratory

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  <20212022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: [Bug 1935037] Re: Invalid charactor in field name
From: mdavidsaver via Core-talk <core-talk at aps.anl.gov>
To: core-talk at aps.anl.gov
Date: Fri, 27 Aug 2021 15:06:55 -0000
> Provided that the questions of compatibility are answered positively
...

For PVXS, field name conformance is only enforced for locally defined
types.  I've added a test to check that an "in-valid" field name can be
decoded, and re-encoded (eg. by a PVA gateway).  Some non-conformant
names won't be accessible locally though.

https://github.com/mdavidsaver/pvxs/commit/2ab0d662bf3f74f32915d0e07383d8c30217fdd5

I don't have time at present to do this testing for pvDataCPP/AccessCPP,
pvDataJava/AccessJava, or Kay's new PVA.

-- 
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/1935037

Title:
  Invalid charactor in field name

Status in EPICS Base:
  New

Bug description:
  When creating a group in QSRV, the allowed characters are too
  restrictive

  error:
  Error Group not created: Invalid charactor '-' (45) in field name "BI02-TimeRise" must be A-Z, a-z, 0-9, or '_'

  expected behaviour:
  pva structures should allow for a more liberal set of characters that just what is covered by \w regex metacharacter.

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


References:
[Bug 1935037] [NEW] Invalid charactor in field name Niko Kivel via Core-talk

Navigate by Date:
Prev: [Bug 1935037] Re: Invalid charactor in field name mdavidsaver via Core-talk
Next: [Bug 1941875] Re: Buggy warning message "Record/Alias name '...' should not contain non-printable ... mdavidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: [Bug 1935037] Re: Invalid charactor in field name mdavidsaver via Core-talk
Next: [Bug 1935037] Re: Invalid charactor in field name mdavidsaver via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
ANJ, 27 Aug 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·