René's URL Explorer Experiment


Title: Nested CDATA section causes invalid XML message by ut_realtime_reporter · Issue #1073 · utPLSQL/utPLSQL · GitHub

Open Graph Title: Nested CDATA section causes invalid XML message by ut_realtime_reporter · Issue #1073 · utPLSQL/utPLSQL

X Title: Nested CDATA section causes invalid XML message by ut_realtime_reporter · Issue #1073 · utPLSQL/utPLSQL

Description: Describe the bug When an utPLSQL output contains a CDATA section, then the ut_realtime_reporter produces an invalid XML message. Such a message cannot be processed by consumers such as the SQL Developer extension. This is related to utPL...

Open Graph Description: Describe the bug When an utPLSQL output contains a CDATA section, then the ut_realtime_reporter produces an invalid XML message. Such a message cannot be processed by consumers such as the SQL Deve...

X Description: Describe the bug When an utPLSQL output contains a CDATA section, then the ut_realtime_reporter produces an invalid XML message. Such a message cannot be processed by consumers such as the SQL Deve...

Opengraph URL: https://github.com/utPLSQL/utPLSQL/issues/1073

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Nested CDATA section causes invalid XML message by ut_realtime_reporter","articleBody":"## Describe the bug\r\nWhen an utPLSQL output contains a CDATA section, then the `ut_realtime_reporter` produces an invalid XML message. Such a message cannot be processed by consumers such as the SQL Developer extension. \r\n\r\nThis is related to utPLSQL/utPLSQL-SQLDeveloper#107.\r\n\r\n## Provide version info\r\n```\r\n19.0.0.0.0\r\n19.0.0\r\n\r\n\r\nPL/SQL procedure successfully completed.\r\n\r\n\r\nUT_VERSION                                                  \r\n------------------------------------------------------------\r\nv3.1.11.3380-develop\r\n\r\n\r\nBANNER                                                                           BANNER_FULL                                                                                                                                                      BANNER_LEGACY                                                                        CON_ID\r\n-------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----------\r\nOracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production           Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production                                                                                           Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production                    0\r\n                                                                                 Version 19.7.0.0.0                                                                                                                                                                                                                                          \r\n\r\n\r\n\r\nPARAMETER                      VALUE                                                           \r\n------------------------------ ----------------------------------------------------------------\r\nNLS_LANGUAGE                   AMERICAN                                                        \r\nNLS_TERRITORY                  SWITZERLAND                                                     \r\nNLS_CURRENCY                   SFr.                                                            \r\nNLS_ISO_CURRENCY               SWITZERLAND                                                     \r\nNLS_NUMERIC_CHARACTERS         .,                                                              \r\nNLS_CALENDAR                   GREGORIAN                                                       \r\nNLS_DATE_FORMAT                DD.MM.YYYY HH24:MI:SS                                           \r\nNLS_DATE_LANGUAGE              AMERICAN                                                        \r\nNLS_SORT                       BINARY                                                          \r\nNLS_TIME_FORMAT                HH24:MI:SSXFF                                                   \r\nNLS_TIMESTAMP_FORMAT           DD.MM.RR HH24:MI:SSXFF                                          \r\n\r\nPARAMETER                      VALUE                                                           \r\n------------------------------ ----------------------------------------------------------------\r\nNLS_TIME_TZ_FORMAT             HH24:MI:SSXFF TZR                                               \r\nNLS_TIMESTAMP_TZ_FORMAT        DD.MM.RR HH24:MI:SSXFF TZR                                      \r\nNLS_DUAL_CURRENCY              SF                                                              \r\nNLS_COMP                       BINARY                                                          \r\nNLS_LENGTH_SEMANTICS           BYTE                                                            \r\nNLS_NCHAR_CONV_EXCP            FALSE                                                           \r\n\r\n17 rows selected. \r\n\r\n\r\nPORT_STRING                                                 \r\n------------------------------------------------------------\r\nx86_64/Linux 2.4.xx\r\n```\r\n\r\n## To Reproduce\r\n\r\n### 1. Create Test Package\r\n\r\n```sql\r\nCREATE OR REPLACE PACKAGE junit_utplsql_test2_pkg is\r\n   --%suite(JUnit testing)\r\n   --%suitepath(b)\\n\r\n\r\n   --%test(test XML with nested CDATA)\r\n   PROCEDURE test_nested_cdata;\r\nEND;\r\n/\r\n\r\nCREATE OR REPLACE PACKAGE BODY junit_utplsql_test2_pkg IS\r\n   PROCEDURE test_nested_cdata IS\r\n   BEGIN\r\n      dbms_output.put_line('nested cdata block: \u003c![CDATA[...]]\u003e, to be handled.');\r\n      ut.expect(1).to_equal(1);\r\n   END;\r\nEND;\r\n/\r\n```\r\n\r\n### 2. Run Test\r\n\r\n```sql\r\nDECLARE\r\n   l_reporter ut_realtime_reporter := ut_realtime_reporter();\r\nBEGIN\r\n   l_reporter.set_reporter_id('12345');\r\n   l_reporter.output_buffer.init();\r\n   sys.dbms_output.enable(NULL);\r\n   ut_runner.run(\r\n      a_paths     =\u003e ut_varchar2_list('junit_utplsql_test2_pkg'),\r\n      a_reporters =\u003e ut_reporters(l_reporter)\r\n   );\r\n   sys.dbms_output.disable;\r\nEND;\r\n/\r\n```\r\n\r\n### 3. Consume wrong XML message\r\n\r\n```sql\r\nWITH\r\n   FUNCTION reporter return ut_realtime_reporter IS\r\n      l_reporter ut_realtime_reporter := ut_realtime_reporter();\r\n   BEGIN\r\n      l_reporter.set_reporter_id('12345');\r\n      RETURN l_reporter;\r\n   END;\r\nSELECT text \r\n  FROM TABLE(reporter().get_lines())\r\n WHERE item_type = 'post-test'\r\n/\r\n```\r\n\r\nThis produces the following output:\r\n\r\n```xml\r\n\u003c?xml version=\"1.0\"?\u003e\r\n\u003cevent type=\"post-test\"\u003e\r\n  \u003ctest id=\"junit_utplsql_test2_pkg.test_nested_cdata\"\u003e\r\n    \u003ctestNumber\u003e1\u003c/testNumber\u003e\r\n    \u003ctotalNumberOfTests\u003e1\u003c/totalNumberOfTests\u003e\r\n    \u003cstartTime\u003e2020-06-04T10:47:00.245501\u003c/startTime\u003e\r\n    \u003cendTime\u003e2020-06-04T10:47:00.250778\u003c/endTime\u003e\r\n    \u003cexecutionTime\u003e.005277\u003c/executionTime\u003e\r\n    \u003ccounter\u003e\r\n      \u003cdisabled\u003e0\u003c/disabled\u003e\r\n      \u003csuccess\u003e1\u003c/success\u003e\r\n      \u003cfailure\u003e0\u003c/failure\u003e\r\n      \u003cerror\u003e0\u003c/error\u003e\r\n      \u003cwarning\u003e0\u003c/warning\u003e\r\n    \u003c/counter\u003e\r\n    \u003cserverOutput\u003e\u003c![CDATA[nested cdata block: \u003c![CDATA[...]]\u003e, to be handled.\r\n]]\u003e\u003c/serverOutput\u003e\r\n  \u003c/test\u003e\r\n\u003c/event\u003e\r\n```\r\n\r\nThis is not a valid XML document. You can go to https://www.xmlvalidation.com/ and paste the result there for details. The reason is the nested CDATA section.\r\n\r\n## Expected behavior\r\nProduce a valid XML document. Always.\r\n\r\n","author":{"url":"https://github.com/PhilippSalvisberg","@type":"Person","name":"PhilippSalvisberg"},"datePublished":"2020-06-04T08:54:17.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1073/utPLSQL/issues/1073"}

route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:d02b5e74-eb1a-a8ca-f1a7-bfc53a36caba
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idBBE4:222302:838C96:8773BC:6A6382B7
html-safe-nonce85ac641fa50476e3a5a3302d055d0fd97381ab12a6bd28c821437542ca6f6232
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCQkU0OjIyMjMwMjo4MzhDOTY6ODc3M0JDOjZBNjM4MkI3IiwidmlzaXRvcl9pZCI6IjIzMDEwNDk2MDQxNTc5NjQ5ODMiLCJyZWdpb25fZWRnZSI6InNlYSIsInJlZ2lvbl9yZW5kZXIiOiJzZWEifQ==
visitor-hmac77b8a9dcd5b79bfb14360c8f07e4119d7d88d4cbba6eed940ee0314342689720
hovercard-subject-tagissue:630638348
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/utPLSQL/utPLSQL/1073/issue_layout
twitter:imagehttps://opengraph.githubassets.com/3b556593123e88892ba8207930806f57c4739406be90f81d822aafc45bfbf632/utPLSQL/utPLSQL/issues/1073
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/3b556593123e88892ba8207930806f57c4739406be90f81d822aafc45bfbf632/utPLSQL/utPLSQL/issues/1073
og:image:altDescribe the bug When an utPLSQL output contains a CDATA section, then the ut_realtime_reporter produces an invalid XML message. Such a message cannot be processed by consumers such as the SQL Deve...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamePhilippSalvisberg
hostnamegithub.com
expected-hostnamegithub.com
Nonee4fb64aef87da454ec25b158147f7f5f14aef29216e5ca1612c2e48faa599d1f
turbo-cache-controlno-preview
go-importgithub.com/utPLSQL/utPLSQL git https://github.com/utPLSQL/utPLSQL.git
octolytics-dimension-user_id15661281
octolytics-dimension-user_loginutPLSQL
octolytics-dimension-repository_id50728220
octolytics-dimension-repository_nwoutPLSQL/utPLSQL
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id50728220
octolytics-dimension-repository_network_root_nwoutPLSQL/utPLSQL
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
releasee839936ba5faffb9c836dda1cf4729d50c88a32e
ui-targetfull
theme-color#1e2327
color-schemelight dark

Links:

Skip to contenthttps://github.com/utPLSQL/utPLSQL/issues/1073#start-of-content
https://github.com/
Sign in https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2FutPLSQL%2FutPLSQL%2Fissues%2F1073
GitHub CopilotWrite better code with AIhttps://github.com/features/copilot
GitHub Copilot appDirect agents from issue to mergehttps://github.com/features/ai/github-app
MCP RegistryNewIntegrate external toolshttps://github.com/mcp
ActionsAutomate any workflowhttps://github.com/features/actions
CodespacesInstant dev environmentshttps://github.com/features/codespaces
IssuesPlan and track workhttps://github.com/features/issues
Code ReviewManage code changeshttps://github.com/features/code-review
Code QualityEnforce quality at mergehttps://github.com/features/code-quality
GitHub Advanced SecurityFind and fix vulnerabilitieshttps://github.com/security/advanced-security
Code securitySecure your code as you buildhttps://github.com/security/advanced-security/code-security
Secret protectionStop leaks before they starthttps://github.com/security/advanced-security/secret-protection
Why GitHubhttps://github.com/why-github
Documentationhttps://docs.github.com
Bloghttps://github.blog
Changeloghttps://github.blog/changelog
Marketplacehttps://github.com/marketplace
View all featureshttps://github.com/features
Enterpriseshttps://github.com/enterprise
Small and medium teamshttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
App Modernizationhttps://github.com/solutions/use-case/app-modernization
DevSecOpshttps://github.com/solutions/use-case/devsecops
DevOpshttps://github.com/solutions/use-case/devops
CI/CDhttps://github.com/solutions/use-case/ci-cd
View all use caseshttps://github.com/solutions/use-case
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
View all industrieshttps://github.com/solutions/industry
View all solutionshttps://github.com/solutions
AIhttps://github.com/resources/articles?topic=ai
Software Developmenthttps://github.com/resources/articles?topic=software-development
DevOpshttps://github.com/resources/articles?topic=devops
Securityhttps://github.com/resources/articles?topic=security
View all topicshttps://github.com/resources/articles
Customer storieshttps://github.com/customer-stories
Events & webinarshttps://github.com/resources/events
Ebooks & reportshttps://github.com/resources/whitepapers
Business insightshttps://github.com/solutions/executive-insights
GitHub Skillshttps://skills.github.com
Documentationhttps://docs.github.com
Customer supporthttps://support.github.com
Community forumhttps://github.com/orgs/community/discussions
Trust centerhttps://github.com/trust-center
Partnershttps://github.com/partners
View all resourceshttps://github.com/resources
GitHub SponsorsFund open source developershttps://github.com/open-source/sponsors
Security Labhttps://securitylab.github.com
Maintainer Communityhttps://maintainers.github.com
Acceleratorhttps://github.com/open-source/accelerator
GitHub Starshttps://stars.github.com
Archive Programhttps://archiveprogram.github.com
Topicshttps://github.com/topics
Trendinghttps://github.com/trending
Collectionshttps://github.com/collections
Enterprise platformAI-powered developer platformhttps://github.com/enterprise
GitHub Advanced SecurityEnterprise-grade security featureshttps://github.com/security/advanced-security
Copilot for BusinessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Pricinghttps://github.com/pricing
Search syntax tipshttps://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax
documentationhttps://docs.github.com/search-github/github-code-search/understanding-github-code-search-syntax
Sign in https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2FutPLSQL%2FutPLSQL%2Fissues%2F1073
Sign up https://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=utPLSQL%2FutPLSQL
Reloadhttps://github.com/utPLSQL/utPLSQL/issues/1073
Reloadhttps://github.com/utPLSQL/utPLSQL/issues/1073
Reloadhttps://github.com/utPLSQL/utPLSQL/issues/1073
Please reload this pagehttps://github.com/utPLSQL/utPLSQL/issues/1073
utPLSQL https://github.com/utPLSQL
utPLSQLhttps://github.com/utPLSQL/utPLSQL
Notifications https://github.com/login?return_to=%2FutPLSQL%2FutPLSQL
Fork 188 https://github.com/login?return_to=%2FutPLSQL%2FutPLSQL
Star 619 https://github.com/login?return_to=%2FutPLSQL%2FutPLSQL
Code https://github.com/utPLSQL/utPLSQL
Issues 12 https://github.com/utPLSQL/utPLSQL/issues
Pull requests 0 https://github.com/utPLSQL/utPLSQL/pulls
Discussions https://github.com/utPLSQL/utPLSQL/discussions
Actions https://github.com/utPLSQL/utPLSQL/actions
Projects https://github.com/utPLSQL/utPLSQL/projects
Security and quality 0 https://github.com/utPLSQL/utPLSQL/security
Insights https://github.com/utPLSQL/utPLSQL/pulse
Code https://github.com/utPLSQL/utPLSQL
Issues https://github.com/utPLSQL/utPLSQL/issues
Pull requests https://github.com/utPLSQL/utPLSQL/pulls
Discussions https://github.com/utPLSQL/utPLSQL/discussions
Actions https://github.com/utPLSQL/utPLSQL/actions
Projects https://github.com/utPLSQL/utPLSQL/projects
Security and quality https://github.com/utPLSQL/utPLSQL/security
Insights https://github.com/utPLSQL/utPLSQL/pulse
#1075https://github.com/utPLSQL/utPLSQL/pull/1075
Nested CDATA section causes invalid XML message by ut_realtime_reporterhttps://github.com/utPLSQL/utPLSQL/issues/1073#top
#1075https://github.com/utPLSQL/utPLSQL/pull/1075
https://github.com/PhilippSalvisberg
bughttps://github.com/utPLSQL/utPLSQL/issues?q=state%3Aopen%20label%3A%22bug%22
https://github.com/PhilippSalvisberg
PhilippSalvisberghttps://github.com/PhilippSalvisberg
on Jun 4, 2020https://github.com/utPLSQL/utPLSQL/issues/1073#issue-630638348
utPLSQL/utPLSQL-SQLDeveloper#107https://github.com/utPLSQL/utPLSQL-SQLDeveloper/issues/107
https://www.xmlvalidation.com/https://www.xmlvalidation.com/
PhilippSalvisberghttps://github.com/PhilippSalvisberg
bughttps://github.com/utPLSQL/utPLSQL/issues?q=state%3Aopen%20label%3A%22bug%22
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.