[jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350232#comment-14350232
]
Sergey Kozlov commented on IGNITE-185:
--
Please merge in sprint-2
> Batch mode for Visorcmd
> ---
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: sprint-2
>
> Attachments: runVisorcmdWithFileResults,
> runVisorcmdWithUTF16FileResults, withExit, withExit_akelpad_UTF16,
> withoutExit_UTF16.txt
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350231#comment-14350231
]
Sergey Kozlov commented on IGNITE-185:
--
I think we don't process encoded file unless it's ANSI and UTF-8.
> Batch mode for Visorcmd
> ---
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: sprint-2
>
> Attachments: runVisorcmdWithFileResults,
> runVisorcmdWithUTF16FileResults, withExit, withExit_akelpad_UTF16,
> withoutExit_UTF16.txt
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350200#comment-14350200
]
Vasilisa Sidorova commented on IGNITE-185:
--
Ubuntu 14.04/Windows7 Ignate Fabric Only Build #119 for ignite-185 branch (ver.
1.0.0-RC2-SNAPSHOT#20150305-sha1:d8ee19a5):
Now all works fine: verify for several types of file (created from different
editors with different encodings) except encoding UTF-16.
You can see the results for that files in the attachment
"runVisorcmdWithUTF16FileResults". Input files "withExit_akelpad_UTF16" and
"withoutExit_UTF16.txt" are also attached.
I'm not sure should it be fixed - it seem like very rare user's scenario.
> Batch mode for Visorcmd
> ---
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Assignee: Vasilisa Sidorova
> Fix For: sprint-2
>
> Attachments: runVisorcmdWithFileResults, withExit
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348658#comment-14348658
]
Vasilisa Sidorova commented on IGNITE-185:
--
Ubuntu 14.04, Ignate Fabric Only Build #118 for ignite-185 branch (ver.
1.0.0-RC2-SNAPSHOT#20150305-sha1:0149a0d3):
Now all is works correctly. Thanks.
Windows 7, Ignate Fabric Only Build #114 for ignite-185 branch (ver.
1.0.0-RC2-SNAPSHOT#20150304-sha1:e9356ab0):
1) There is OK for input commands set from command line
2) There is problem with input commands set from file: the numbers and letters
which are answers are read as independent commands. Look at the command's
"ignitevisorcmd.bat -b=withExit" results in the file
"runVisorcmdWithFileResults". Input file "withExit" is also attached
> Batch mode for Visorcmd
> ---
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Assignee: Vasilisa Sidorova
> Fix For: sprint-2
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347246#comment-14347246
]
Sergey Kozlov commented on IGNITE-185:
--
Confirmed for me too
No issues for ignitevisorcmd.bat
> Batch mode for Visorcmd
> ---
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: sprint-2
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345004#comment-14345004
]
Vasilisa Sidorova commented on IGNITE-185:
--
Ubuntu 14.04, Ignate Fabric Only Build #107 (ver.
1.0.1-RC1-SNAPSHOT#20150224-sha1:1ff1c8e6):
Checked for the command set: "open;3;node;0;y;vvm;kill;0;r;y;y;[exit]" from
command line and from file. It's OK except one moment:
If commands set haven't "exit" as last command user stay in the visor session
but couldn't doing something here only close the terminal.
So, expected result is: if last command in commands set isn't "exit" send to
visorcmd forced "exit". Please, implement this.
> Batch mode for Visorcmd
> ---
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Assignee: Vasilisa Sidorova
> Fix For: sprint-2
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327645#comment-14327645
]
Andrey Novikov commented on IGNITE-185:
---
Sergey, please check in branch
-e option:
./bin/ggvisorcmd -e="open;2;kill;y"
-b option:
./bin/ggvisorcmd -b="file path"
with content:
{code}
open
2
kill
y
quit
{code}
> Batch mode for Visorcmd
> ---
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Assignee: Sergey Kozlov
> Fix For: sprint-2
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
[
https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325497#comment-14325497
]
Sergey Kozlov commented on IGNITE-185:
--
The original description is outdated.
It's enough for now to have an option:
./bin/ggvisorcmd -e "command1;command2"
> Batch mode for Visorcmd
> ---
>
> Key: IGNITE-185
> URL: https://issues.apache.org/jira/browse/IGNITE-185
> Project: Ignite
> Issue Type: Task
> Components: UI
>Affects Versions: sprint-1
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: sprint-2
>
>
> Batch mode for visorcmd allow to read commands from test file (one command
> per line), perform them, send output to STDOUT/STDERR and exit if end of text
> file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test
> scripts can compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for
> some commands (e.g. "kill" - confirm to kill, "open" - set number of config
> file). But can be resolved by following ways:
> next line after such command contains text for request, e.g.
> open
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve
> commands like "open"?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
