-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ 2375002 ] Inconsistent error message (installation path) #191
Comments
The same with other keys.
causes a wrong version (the one from testsuites management) used for version check:
|
@namsonx : What is the status of this issue? |
Hello @ngoan1608, can you update the status of this ticket? |
solved and already merged with #220 |
Retest result: Every invalid key causes a corresponding error message now. OK. But missing keys are not considered. Usecase:
In my opinion the file package_context.json should also be checked for completeness. |
The behavior changed (probably caused by 0.13.1 changes). In case of an invalid
And the debug log file is mostly empty:
See also: #302 |
Hi @namsonx , |
#191 (comment) solved in between. No, I have to correct myself: not solved. By mistake I tested with standard JSONP configuration file. But this issue is about the package_context.json file. Now I faced: The behavior of this file completely different. Test ongoing. |
Restest with package_context.json / extended version / level INFO
Console:
Debug log file: completely empty
Console:
Debug log file: completely empty
Is ignored (maybe because of this information is not used because the version check is passed). Test is passed.
The provided installer location is wrong (belongs to component, but not to bundle). Therefore It's better to check package_context.json for completeness at first.
Same issue as in item before:
Bundle name does not fit to installer path. |
In package_context.json I made a key invalid:
Outcome is an inconsistent error message:
The content of package_context.json should be checked more strict.
The text was updated successfully, but these errors were encountered: