Closed hassanakbar4 closed 3 years ago
resolution_overtaken by events type_defect | by julian.reschke@gmx.de
resolution_overtaken by events
type_defect
The new code (#6) that processes for IRTF stream RFCs behaves weirdly when the workgroup element contains XML-special characters, such as "<" or ">".
Example:
<workgroup><insert_name></workgroup>
The code does something like
set workgroupname "" if {([string compare \ [set workgroup [lindex [find_element workgroup \ $attrs(.CHILDREN)] 0]] ""])} { array set wv $elem($workgroup) # jre: this escapes angle brackets; why? set workgroupname [string trim $wv(.CTEXT)] }
For some strange reason that gets evaluated as
<insert_name>
instead of
<insert_name>
which of course leads to funny results when the code later does
regsub -all -- %WORKGROUPNAME% $status "$workgroupname" status
because "&" is special in regexp processing.
Issue migrated from trac:17 at 2021-10-20 19:47:16 +0500
resolution_overtaken by eventstype_defect| by julian.reschke@gmx.deThe new code (#6) that processes for IRTF stream RFCs behaves weirdly when the workgroup element contains XML-special characters, such as "<" or ">".
Example:
The code does something like
For some strange reason that gets evaluated as
instead of
which of course leads to funny results when the code later does
because "&" is special in regexp processing.
Issue migrated from trac:17 at 2021-10-20 19:47:16 +0500