Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Minor |
| Complexity | Unknown |
| Component | App - FluidShell |
| Version | 11.0 |
Command line usage info is not expected to be displayed when actually its parameters are provided as required, but the script content is wrong.
e.g.
Create an input script that contains just "\list".
Output result will be
Missing operand
Usage: RunFluidShell[.bat | .sh] "-cCONNECTION" "-fFILENAME" "-oOUTPUT_FILE" "-uUSERNAME" "-pPASSWORD" "-iINPUT_ENCODING" "-eOUTPUT_ENCODING"
CONNECTION [-c] - [optional] Identifies the connection name.
FILENAME [-f] - [required] File name of the script to execute.
OUTPUT_FILE [-o] - [optional] File name for the text output. Standard out is used if not defined. (NONE for no output)
USERNAME [-u] - [optional] Username to use for login. If not indicated, then the saved username will be used.
PASSWORD [-p] - [optional] Password to use for login. If not indicated, then the saved password will be used.
INPUT_ENCODING [-i] - [optional] Character encoding for the input file.
OUTPUT_ENCODING [-e] - [optional] Character encoding for the output file.
Also, a reference indicating the failing command line # would help here (e.g. if the input script is too long to find the erroneou line directly etc).
I am not sure what is the correct message that RunFluidShell supposes to generate; per issue #6468, the generated message seems to be correct. Reassigned to Andy to take a look.
https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/6468
1. Displaying the Usage of RunFluidShell is actually a feature, because the user is in the command prompt and we are displaying the usage to make it easier for the user.
2. For the error message in the script - Missing Operand is displayed for \list which is also correct.
These 2 was logged as a separate issue and was fixed.
3. Andy, is it possible to display the line number of the script which has the error ?
1. Displaying the Usage of RunFluidShell is actually a feature, because the user is in the command prompt and we are displaying the usage to make it easier for the user.
2. For the error message in the script - Missing Operand is displayed for \list which is also correct.
These 2 was logged as a separate issue and was fixed.
3. Andy, is it possible to display the line number of the script which has the error ?
The first part of my request was misunderstood. I meant that in this particular case, the usage info message misleads the user: it makes him think that maybe some parameters (the context of the script call) are missing or wrong; but actually there is a problem in the script content.
In order to avoid such confusion, it would be better to display the usage info message only if runfluidscript was invoked with inadequate parameters (e.g. "-cConnectionName" is missing).
If the error is in the script content itself, it would be better to display just the failure message (e.g. "Missing operand" in the scenario above) together with a line # reference. The usage info should not be displayed in this case.
The first part of my request was misunderstood. I meant that in this particular case, the usage info message misleads the user: it makes him think that maybe some parameters (the context of the script call) are missing or wrong; but actually there is a problem in the script content.
In order to avoid such confusion, it would be better to display the usage info message only if runfluidscript was invoked with inadequate parameters (e.g. "-cConnectionName" is missing).
If the error is in the script content itself, it would be better to display just the failure message (e.g. "Missing operand" in the scenario above) together with a line # reference. The usage info should not be displayed in this case.
ah, sorry, I misunderstood you. my fault.
fixed.
ah, sorry, I misunderstood you. my fault.
fixed.
Verified with version 11.0.0-beta15 .
Verified with version 11.0.0-beta15 .
Issue #6504 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
I am not sure what is the correct message that RunFluidShell supposes to generate; per issue #6468, the generated message seems to be correct. Reassigned to Andy to take a look.
https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/6468