[JENKINS-15526] toJSON broken: [JENKINS-11618] reintroduced a bug fixed by prototypejs 1.7

[timja]

the script:
JSON.stringify(

{"a":[1,2]}

)

delivers the wrong result:

• should: " {"a":[1,2]}

  "

• actual: " {"a":"[1, 2]"}

  "

hint:
This was probably introduced by fix for JENKINS-11618

The problem is that this behaviour breaks e.g. test automation support for SilkTest and WebDriver, and probably some other things too.

---

Originally reported by alienllama, imported from: toJSON broken: [JENKINS-11618] reintroduced a bug fixed by prototypejs 1.7

• status: Open
• priority: Major
• resolution: Unresolved
• imported: 2022/01/10

[timja]

scm_issue_link:

Code changed in jenkins
User: Ulli Hafner
Path:
src/main/java/hudson/plugins/warnings/GroovyParser.java
src/main/java/hudson/plugins/warnings/parser/ParserRegistry.java
http://jenkins-ci.org/commit/warnings-plugin/2987adb60b54e0a0b471ba2c3e14384d680ba930
Log:
Improved fix for JENKINS-15526[FIXED JENKINS-16107].

Compare: https://github.com/jenkinsci/warnings-plugin/compare/d677b1f5d9f1...2987adb60b54

–
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[timja]

evernat:

The comment in this issue seems misleading.
What should be the status of this issue? Should it be fixed?

[timja]

danielbeck:

Is this still a problem in recent Jenkins versions? How can this be reproduced? What is the impact of this issue?

[timja]

[Originally duplicated by: JENKINS-25152]