Closed joaopaulosm closed 1 year ago
Michael, any guidance on how I can be helpful is appreciated.
As it happens, I may have fixed this last week with 92fb0a4afa5054b6cc3e8eb395facaa337d1c454. Are you able to test with the master branch?
I was hoping to go to sleep and wake up with the fix ready, but this time you surpassed all expectations by fixing it BEFORE the issue was reported =D
Jokes aside, yes, I did test with the master branch and it fixed the issue completely. Thanks again, Michael!
Ok :) I still might wish to have noticed this issue a few hours before making the 1.1.3 release, instead it was a few hours afterwards. A 1.1.4 with this fix will likely happen within the next few days.
Included in 1.1.4
.
I was going to report this issue now and found out that I just missed the last update... Thanks!
I have a test program (IOC) that monitors a set of NT PVs which are made of many structures and a "value" field that is set to "any" (the PVs were created using QSRV info tags). I noticed that when moving from PVXS 1.0.1 to 1.1.3 the monitor event crashed, yielding the following stack trace in the IOC console:
I tested again with PVXS 1.0.1 and everything was OK. Then I started testing with
pvxmonitor
from PVXS >= 1.0.1 and managed to reproduce the same problem.To Reproduce Steps to reproduce the behavior:
Create a simple IOC with a "group" PV, something like the database below:
record(calc, "$(P)$(R)$(NAME)B") { field(CALC, "A+1") field(INPA, "$(P)$(R)$(NAME)B") field(SCAN, "1 second")
}
FOO:BAR:PVNAME Connected to 192.168.0.1:PORTNUM FOO:BAR:PVNAME struct record struct record._options struct record._options.queueSize uint32_t = 0 record._options.atomic bool = false A any A-> double = [some number] B any B-> double = [some number]
CRIT pvxs.tcp.io Server Error while processing cmd 0x0d: No such field