-
Notifications
You must be signed in to change notification settings - Fork 22
Open
Description
- I triggered the yc-360 script with the [On-demand] Execution mode, along with "cmdTimeout" argument as follows:
./yc -c yc-agent.yaml -p 960300 -a "yCrash" -tags "cmdTimeout: 80s"
My Config File:
version: '1'
options:
j: D:\SoftwareSetup\jdk8\jdk1.8.0_60
k: ycrash@0fa10568-2ddf-****-****-************
s: http://localhost:8080
edScript: D:\files\ExtendedData\script\user.bat
edDataFolder: D:\files\ExtendedData\
cmdTimeout: "2"
a: ycrash
appLogs:
- D:\tier1app-workstation\AppLog-TestData-20241008T105854Z-001\AppLog-TestData\yc-0.log
- When I execute the yc-360 script, it displays the validation message as follows:
2025/08/21 19:41:00 decode config file path D:\ConfigFiles\yc-config.yaml failed: yaml: unmarshal errors:
line 10: cannot unmarshal !!str `2` into time.Duration
- Message is not clear
EXPECTED RESULT: We should print user friendly message like "Invalid value "2" for flag -cmdTimeout. The value should include a time unit. Supported formats are: 2s, 2m, 2ms, 2ns, 2us."
NOTE: It needs to be fixed when we pass the cmdTimeout in config file and also in yc-360 Script.
Metadata
Metadata
Assignees
Labels
No labels