You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes + minor formatting adjustments for MTA RNs (#302)
* Fixes + minor formatting adjustments
* Update docs/topics/release-notes-topics/ref_new-features-and-enhancements-8-0.adoc
Co-authored-by: Andy Arnold <anarnold@redhat.com>
* Update docs/topics/release-notes-topics/ref_fixed-issues-8-0.adoc
Co-authored-by: Andy Arnold <anarnold@redhat.com>
---------
Co-authored-by: Andy Arnold <anarnold@redhat.com>
Copy file name to clipboardExpand all lines: docs/topics/release-notes-topics/ref_fixed-issues-8-0-1.adoc
+1-28Lines changed: 1 addition & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,99 +12,72 @@ In {ProductShortName} 8.0.1 the performance of Java binary analysis has signific
12
12
Before this change, when you analyzed Java binary applications, {ProductShortName} incorrectly classified some open-source dependencies as internal dependencies, it was then decompiled and analyzed, that caused the analysis to take longer to complete. Now, the location of the Maven index file is passed to the Java provider to determine if an embedded dependency is open-source or internal. This fix resolved the two following issues:
13
13
14
14
Binary application analysis latency is reduced in {ProductShortName}::
15
-
16
15
When you analyzed a binary, the performance degraded because {ProductShortName} relied on Maven search. With this release, this issue is fixed by introducing the pre-generated Maven index that does not require connecting to an external index.
Analysis of binary applications classify open source dependencies accurately::
22
-
23
-
When you analyzed Java binary applications, {ProductShortName} incorrectly classified some open-source dependencies as internal dependencies. With this version, this issue if fixed. This leads to {ProductShortName} classifying embedded open source dependencies correctly after a source+dependency binary analysis.
20
+
When you analyzed Java binary applications, {ProductShortName} incorrectly classified some open-source dependencies as internal dependencies. With this version, this issue is fixed. This leads to {ProductShortName} classifying embedded open source dependencies correctly after a source+dependency binary analysis.
{ProductShortName} enables you to target an organization when importing applications from Cloud Foundry::
29
-
30
25
When you imported applications from Cloud Foundry (CF), {ProductShortName} did not have a provision for you to mention the CF organizations. With this release, this issue is fixed. You can configure one or more organizations, spaces, and applications for the discovery process. The spaces can belong to different organizations and the applications can belong to different spaces. You must specify at least one organization for application discovery.
{ProductShortName} {CLIName} correctly processes Cloud Foundry applications with service binding::
36
-
37
30
The discovery process of Cloud Foundry (CF) applications with service bindings by using live connection failed in {ProductShortName} {CLIName}. The {ProductShortName} {CLIName} did not parse the `VCAP_SERVICES` environment variables correctly to handle service binding information for an array of services. For example, `cf bind-service _<application_name>_ postgres01`. With this version, this issue is fixed. As a result, {ProductShortName} {CLIName} successfully completes the discovery of CF applications with service bindings.
Cloud Foundry applications imported in {ProductShortName} are tagged automatically::
43
-
44
35
When you imported applications in {ProductShortName} from a Cloud Foundry (CF) instance, the applications did not contain the `Cloud Foundry` tag. The tag links an application to an archetype. The archetype has a generator that produces the deployment assets for a migration path. With this release, this issue is fixed. You no longer have to manually add the `Cloud Foundry` tag in the imported application.
You can import Cloud Foundry applications from the application inventory in the {ProductShortName} web console::
50
40
51
41
Before this update, an {ProductShortName} Architect could not discover or import applications from the Cloud Foundry (CF) source platform on the application inventory page. As a result, only an {ProductShortName} Administrator could import the applications on the *Source platforms* page in the Administrator mode. With this release, this issue is fixed. Architects can now import CF applications in the *Application Inventory*.
Concurrent usage of {mta-dl-plugin} for code resolution at scale no longer causes race conditions::
57
-
58
46
Concurrent usage of the Solution Server through the {mta-dl-plugin} Visual Studio (VS) Code plugin for code resolution at scale caused race conditions for duplicate incidents. With this release, this issue is fixed. The plugin generates resolutions for the incidents identified when many users use it concurrently.
{ProductShortName} rules for Java use FQN to match annotations in source code::
64
-
65
51
Before this update, the annotation rules for Java applications did not use Fully Qualified Names (FQNs) to match with the annotation location in rules. As a result, the rule triggered incorrect matches or false positives for issues. For example, a rule that looked for the `javax.enterprise.inject.Produces` incorrectly matched with occurrences of `javax.ws.rs.Produces`. With this release, this issue is fixed.
{ProductShortName} triggers rules to match import statements with wildcard in Java applications analysis::
71
-
72
56
{ProductShortName} did not trigger rule to match import statements that contain a wildcard when analyzing a Java application. Consequently, specific incidents were not detected in the report after the analysis. With this release, this issue is fixed.
{ProductShortName} {WebName} enables you to edit secure SVN application without an error::
78
-
79
61
When you disabled the `Allow insecure connection` for an application stored in the SVN repository and edited the application, the {WebName} displayed a blank page some times with the `TypeError` `cannot read properties of undefined (reading 'kind')`. With this version, this issue is fixed. You can edit secure SVN applications in the {ProductShortName} {WebName}.
{ProductShortName} no longer fails language and tech discovery for Java application in SVN repositories::
85
-
86
66
Before this update, for a Java application source code stored in an SVN repository, {ProductShortName} produced an error when trying to checkout the repository by using the SVN credential. As a result, the language and tech discovery of the application failed. With this release, this issue is fixed. You can now analyze an application stored in SVN repository without any error.
{ProductShortName} displays source repository URL when you skip configuring the repository type field::
92
-
93
71
{ProductShortName} did not show the source repository URL in the application details view if you did not select between the `Git` or `Subversion` repository type. As a result, you could not run an analysis on the application source code. With this release, this issue is fixed. You can now use {ProductShortName} to run an analysis on the source code even if you do not configure the repository type field.
You can complete an assessment by using a custom questionnaire in the {ProductShortName} {WebName}::
99
-
100
76
Before this update, you could not proceed to the final step after filling in the responses to the custom questionnaire because the *Next* button was disabled in the web console. With this release, this issue is fixed.
{ProductShortName} web console detects custom rules when many are uploaded at a time::
106
-
107
81
When you uploaded more than one custom rule at a time in the {ProductShortName} web console, the rules were not detected. With this version, this issue is fixed. You can upload one or more custom rules at once.
Copy file name to clipboardExpand all lines: docs/topics/release-notes-topics/ref_fixed-issues-8-0.adoc
+2-10Lines changed: 2 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,33 +9,25 @@
9
9
{ProductFirstRef} ({ProductShortName}) version 8.0.0 provides the following fixed issues and other problems that have a significant impact.
10
10
11
11
The default `values.yaml` file is merged with the discover `values.yaml` file when generating a deployment manifest::
12
-
13
12
Before this update, when you generated a deployment manifest by using the Helm template, the default values in the`values.yaml` file, packaged with the Helm chart, were ignored. Consequently, only the values from the `values.yaml` file created after running the `mta-cli discover` command were used. With this update, the default `values.yaml` file is merged with the discover `values.yaml` file.
{ProductShortName} CLI no longer fails to detect dependencies for Gradle projects::
20
-
21
18
Before this update, when you ran an application analysis for Gradle projects in containerless mode, {ProductFullName} command-line interface (CLI) did not detect Gradle dependencies. As a consequence, the analysis report did not list the dependencies and displayed an error message in the analysis logs instead. With this update, the issue is fixed. As a result, {ProductShortName} CLI detects Gradle dependencies after the analysis is complete.
{ProductShortName} UI no longer fails to analyze projects built with Gradle version 7 and later::
28
-
29
-
Before this update, when you analyzed an application built with Gradle in `Source code + dependencies` mode in the {ProductFullName} user interface (UI), the analysis failed if you had Gradle version 7 or later installed* With this update, the issue is fixed*
24
+
Before this update, when you analyzed an application built with Gradle in `Source code + dependencies` mode in the {ProductFullName} user interface (UI), the analysis failed if you had Gradle version 7 or later installed. With this update, the issue is fixed.
The discovery manifest lists all defined web processes in the application::
36
-
37
30
Before this update, the `mta-cli discover` command only moved an application-level process with the process type explicitly defined to the `processes` block in the discovery manifest. Consequently, the discovery manifest did not list implicit application-level processes in the `processes` block. This resulted in the violation of the recommended clarity and proper configuration practices, especially if multiple process types were planned. With this update, `mta-cli discover` moves both implicit and explicit application-level process types to the `processes` block in the discovery manifest.
Copy file name to clipboardExpand all lines: docs/topics/release-notes-topics/ref_known-issues-8-0-1.adoc
+2-13Lines changed: 2 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,40 +10,33 @@
10
10
11
11
12
12
{ProductShortName} assessment form malfunctions when you use it with a custom questionnaire::
13
-
14
13
In the {ProductShortName} {WebName}, selecting an answer to a question in the assessment form generated from a custom questionnaire causes the form to select an option available for another question.
15
14
+
16
15
To work around this problem, ensure that one or more `order` keys listed in a section, for example `answers`, have a unique order number.
{ProductShortName} UI does not trigger a violation for open source dependencies in Gradle applications::
21
-
22
20
{ProductShortName} UI does not trigger a violation for open source libraries when you run a `source+dependency` analysis of a Gradle application. As a result, the analysis report does not list incidents for open source dependencies.
23
21
+
24
-
25
22
To work around this problem, analyze Gradle applications by using the {ProductShortName} command-line interface (CLI).
{ProductShortName} UI fails to process applications with service bindings::
31
-
32
28
When you use the {ProductFullName} user interface (UI) to run an application discovery for a deployed Cloud Foundry (CF) application with a service binding, {ProductShortName} UI does not parse the `VCAP_SERVICES` environment variables correctly to handle service binding information. Consequently, the discovery fails.
33
29
+
34
-
35
30
To work around this problem, run the application discovery by using the {ProductShortName} command-line interface (CLI).
Rules with `METHOD_CALL` or `CONSTRUCTOR_CALL` do not match expected locations when specifying parameters::
41
-
42
36
Search patterns in Java rules that have the `METHOD_CALL` and `CONSTRUCTOR_CALL` locations do not match the expected methods and constructors in the application source code.
{ProductShortName} analysis result does not change if you add or remove a custom rule::
33
-
34
31
When you use Developer Lightspeed for {ProductShortName}, the analysis results do not change if you include or remove a custom rule but do not restart the analyzer process.
35
32
+
36
-
37
33
To work around this problem, restart the analyzer process by clicking the *Start/Stop* button after making a configuration change.
`ANNOTATION` location rules do not match on FQNs::
44
-
45
39
The `ANNOTATION` search location does not properly use Fully Qualified Names (FQNs) to match annotations. This leads to incorrect matches and false positives in analysis issues. For example, a rule that searches for annotations using the `javax.enterprise.inject.Produces` pattern might incorrectly match the occurrences of the `javax.ws.rs.Produces` annotation in the source code.
Developer Lightspeed for {ProductShortName} database throws a connection error::
55
-
56
47
The Solution Server throws a connection error when concurrent connections increase in a short span of time. To work around this problem, enter the following command to allow the Developer Lightspeed for {ProductShortName} database to expire idle connections:
57
48
+
58
49
----
59
50
oc -n openshift-mta exec deploy/kai-db – psql -U postgres -d postgres -c "ALTER ROLE kai SET idle_session_timeout = '1min'; ALTER ROLE kai SET idle_in_transaction_session_timeout = '1min';"
0 commit comments