kevinkelin opened a new issue, #15136:
URL: https://github.com/apache/dolphinscheduler/issues/15136

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   In python task , if a variable has "\n", then use setValue to make a 
Parameter for next node,  the variable will not work well 
   
   node_one 
   ```python
   s = "hello \n world"
   print("${setValue(message=%s)}"%s)
   ```
   
   node_two
   ```shell
   echo "${message}"
   
   echo "hi"
   ```
   
   check runtime log 
   
   node_one 
   ```
   [INFO] 2023-11-08 10:51:02.588 +0800 - process start, process id is: 10376
   [INFO] 2023-11-08 10:51:03.588 +0800 -  -> 
         world)}
   [INFO] 2023-11-08 10:51:03.590 +0800 - process has exited. execute 
   ```
   
   node_two
   ```
   [INFO] 2023-11-08 10:51:04.374 +0800 - process start, process id is: 30190
   [INFO] 2023-11-08 10:51:05.374 +0800 -  -> 
        
        hi
   [INFO] 2023-11-08 10:51:05.375 +0800 - process has exited. execute
   ```
   
   
   
   ### What you expected to happen
   
   In node_two, when `echo "${message}"`  will show the  Parameter set in pre 
task,  in this case, want show “hello \n world"
   
   ### How to reproduce
   
   create a workflow, the first task use python task, make a variable include 
"\n", then use setValue to make a  Parameter
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.2.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to