[ 
https://issues.apache.org/jira/browse/DISPATCH-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468587#comment-17468587
 ] 

Jiri Daněk commented on DISPATCH-2281:
--------------------------------------

Viewing this from Linux-only point of view, then this is issue of correct 
escaping in the config file, specifically of documenting how to correctly 
escape. I am not sure if this is written down anywhere. The current config 
format is JSON with (great) many twists (managed by regex transformations).

> Dispatch confg refuses to load Windows paths with backslashes
> -------------------------------------------------------------
>
>                 Key: DISPATCH-2281
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-2281
>             Project: Qpid Dispatch
>          Issue Type: Sub-task
>          Components: Tests
>            Reporter: Jiri Daněk
>            Priority: Major
>
> {noformat}
> 15: 2021-11-06 21:03:49.699705 +0100 AGENT (error) Line 4 |"debugDumpFile": 
> "C:\Users\Vitorio\CLionProjects\qpid-dispatch\cmake-build-debug-visual-studio-clang\tests\system_test.dir\system_tests_link_routes\Dispatch1428\setUpClass\A-qddebug.txt"}],
> [...]
> 15: 2021-11-06 21:03:49.717249 +0100 ERROR (error) Python: Exception: Cannot 
> load configuration file A.conf: Invalid \escape: line 4 column 21 (char 69
> {noformat}
> The config loading procedure first transforms the config with regexes and 
> then reads it as JSON
> {noformat}
> 15:   File 
> "C:\Users\Vitorio\CLionProjects\qpid-dispatch\python\qpid_dispatch_internal\management\config.py",
>  line 198, in _parse
> 15:     sections = json.loads(js_text)
> {noformat}
> The error seems to be the correct behavior. Windows paths will need to be 
> escaped, or written with forward slashes (this works on contemporary Windows 
> versions). The Dispatch tests will need to be fixed.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to