feedback-to-code/mozzarella huggingface dataset:
Repository: provectus/kafka-ui
Issue: Modify a release flow to publish serde-spi jar to maven central
Labels: status/accepted
scope/infrastructure


Issue comments:

Pull request review comments:

Patch that resolved the issue:
diff --git a/.github/workflows/release-serde-api.yaml b/.github/workflows/release-serde-api.yaml
new file mode 100644
index 00000000000..e13fa7a23a0
--- /dev/null
+++ b/.github/workflows/release-serde-api.yaml
@@ -0,0 +1,33 @@
+name: Release-serde-api
+on: workflow_dispatch
+
+jobs:
+  release-serde-api:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+
+      - run: |
+          git config user.name github-actions
+          git config user.email github-actions@github.com
+
+      - name: Set up JDK
+        uses: actions/setup-java@v3
+        with:
+          java-version: "17"
+          distribution: "zulu"
+          cache: "maven"
+
+      - id: install-secret-key
+        name: Install GPG secret key
+        run: |
+          cat <(echo -e "${{ secrets.GPG_PRIVATE_KEY }}") | gpg --batch --import
+
+      - name: Publish to Maven Central
+        run: |
+          MVN_VERSION=$(curl -s https://search.maven.org/solrsearch/select?q=g:"com.provectus"+AND+a:"kafka-ui-serde-api" | grep -o '"latestVersion": *"[^"]*"' | grep -o '"[^"]*"$' | sed 's/"//g')
+          MVN_VERSION=$(echo "$MVN_VERSION" | awk 'BEGIN{FS=OFS="."} {$2+=1} 1')
+          mvn -B -ntp versions:set -DnewVersion=$MVN_VERSION -pl kafka-ui-serde-api
+          mvn source:jar  javadoc:jar  package  gpg:sign -Dgpg.passphrase=${{ secrets.GPG_PASSPHRASE }} -Dserver.username=${{ secrets.NEXUS_USERNAME }} -Dserver.password=${{ secrets.NEXUS_PASSWORD }} nexus-staging:deploy   -pl kafka-ui-serde-api  -s settings.xml


Test patch:
Repository: provectus/kafka-ui
Issue: Increment serde api version manually
Labels: scope/infrastructure


Issue comments:

Pull request review comments:

Patch that resolved the issue:
diff --git a/.github/workflows/release-serde-api.yaml b/.github/workflows/release-serde-api.yaml
index e13fa7a23a0..227dbcec24c 100644
--- a/.github/workflows/release-serde-api.yaml
+++ b/.github/workflows/release-serde-api.yaml
@@ -27,7 +27,4 @@ jobs:
 
       - name: Publish to Maven Central
         run: |
-          MVN_VERSION=$(curl -s https://search.maven.org/solrsearch/select?q=g:"com.provectus"+AND+a:"kafka-ui-serde-api" | grep -o '"latestVersion": *"[^"]*"' | grep -o '"[^"]*"$' | sed 's/"//g')
-          MVN_VERSION=$(echo "$MVN_VERSION" | awk 'BEGIN{FS=OFS="."} {$2+=1} 1')
-          mvn -B -ntp versions:set -DnewVersion=$MVN_VERSION -pl kafka-ui-serde-api
           mvn source:jar  javadoc:jar  package  gpg:sign -Dgpg.passphrase=${{ secrets.GPG_PASSPHRASE }} -Dserver.username=${{ secrets.NEXUS_USERNAME }} -Dserver.password=${{ secrets.NEXUS_PASSWORD }} nexus-staging:deploy   -pl kafka-ui-serde-api  -s settings.xml


Test patch:
Repository: provectus/kafka-ui
Issue: Google provider w/ OAuth2 w/ RBAC: Invalid client registration id
Labels: type/bug
scope/backend
status/accepted
status/confirmed
area/rbac


Issue comments:

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-api/src/main/java/com/provectus/kafka/ui/config/auth/OAuthPropertiesConverter.java b/kafka-ui-api/src/main/java/com/provectus/kafka/ui/config/auth/OAuthPropertiesConverter.java
index 8fffbfb6997..c3d20664914 100644
--- a/kafka-ui-api/src/main/java/com/provectus/kafka/ui/config/auth/OAuthPropertiesConverter.java
+++ b/kafka-ui-api/src/main/java/com/provectus/kafka/ui/config/auth/OAuthPropertiesConverter.java
@@ -8,12 +8,14 @@
 import lombok.NoArgsConstructor;
 import org.apache.commons.lang3.StringUtils;
 import org.springframework.boot.autoconfigure.security.oauth2.client.OAuth2ClientProperties;
+import org.springframework.security.config.oauth2.client.CommonOAuth2Provider;
 
 @NoArgsConstructor(access = AccessLevel.PRIVATE)
 public final class OAuthPropertiesConverter {
 
   private static final String TYPE = "type";
   private static final String GOOGLE = "google";
+  public static final String DUMMY = "dummy";
 
   public static OAuth2ClientProperties convertProperties(final OAuthProperties properties) {
     final var result = new OAuth2ClientProperties();
@@ -57,7 +59,14 @@ private static void applyGoogleTransformations(OAuth2Provider provider) {
       return;
     }
 
-    final String newUri = provider.getAuthorizationUri() + "?hd=" + allowedDomain;
+    String authorizationUri = CommonOAuth2Provider.GOOGLE
+        .getBuilder(DUMMY)
+        .clientId(DUMMY)
+        .build()
+        .getProviderDetails()
+        .getAuthorizationUri();
+
+    final String newUri = authorizationUri + "?hd=" + allowedDomain;
     provider.setAuthorizationUri(newUri);
   }
 


Test patch:
Repository: provectus/kafka-ui
Issue: "Saved filters" invalid font
Labels: good first issue
scope/frontend
status/accepted
type/chore

<img width="576" alt="image" src="https://user-images.githubusercontent.com/1494347/220509484-46e27477-5fd2-4a27-a69c-998436eac7f9.png">

https://www.figma.com/file/ZkvysdRUmt9p2PDNU3a9WU/Kafka-UI?node-id=2536%3A10370&t=WBEoXbSrlD54Pnqw-4

Issue comments:
Hi, @Haarolean  I would like to work on this issue. Can you please assign it to me?
@vict-o-ria hey Victoria, sure thing :)

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Topics/Topic/Messages/Filters/Filters.styled.ts b/kafka-ui-react-app/src/components/Topics/Topic/Messages/Filters/Filters.styled.ts
index d1230febf94..6e1d50b3bf6 100644
--- a/kafka-ui-react-app/src/components/Topics/Topic/Messages/Filters/Filters.styled.ts
+++ b/kafka-ui-react-app/src/components/Topics/Topic/Messages/Filters/Filters.styled.ts
@@ -184,6 +184,7 @@ export const CreatedFilter = styled.p`
   margin: 25px 0 10px;
   font-size: 14px;
   line-height: 20px;
+  color: ${({ theme }) => theme.list.meta.color};
 `;
 
 export const SavedFiltersContainer = styled.div`


Test patch:
Repository: provectus/kafka-ui
Issue: Request for a `global.imageRegistry` parameter
Labels: status/accepted
scope/k8s

**Describe the bug**
This allows anyone that uses Bitnami helm charts to have this chart as a subchart without explicitly specifying `image.registry`.

**Set up**
I have a helm chart with 5 subcharts:
- service A (respects `global.imageRegistry`)
- service B (respects `global.imageRegistry`)
- service C (respects `global.imageRegistry`)
- kafka from Bitnami (respects `global.imageRegistry`)
- kafka-ui (I have to manually set `kafka-ui.image.registry` to match `global.imageRegistry`)


**Steps to Reproduce**
Setup a helm-chart with kafka-ui as a subchart.

**Expected behavior**
In my ideal setup my `values.yaml` looks like:
```yaml
global:
  imageRegistry: container-registry.my-domain.com
```

But because of the way things are now, I have to write it like this:
```yaml
global:
  imageRegistry: container-registry.my-domain.com

kafka-ui:
  image:
    registry: container-registry.my-domain.com
```

I'm willing to contribute the code to make this happen if the idea is accepted.

Issue comments:
Hello there yardenshoham! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀
I want to claim this issue

Pull request review comments:

Patch that resolved the issue:
diff --git a/charts/kafka-ui/Chart.yaml b/charts/kafka-ui/Chart.yaml
index 6e5f0ee2d5b..4f36aa7f0b1 100644
--- a/charts/kafka-ui/Chart.yaml
+++ b/charts/kafka-ui/Chart.yaml
@@ -2,6 +2,6 @@ apiVersion: v2
 name: kafka-ui
 description: A Helm chart for kafka-UI
 type: application
-version: 0.5.3
+version: 0.5.4
 appVersion: v0.5.0
 icon: https://github.com/provectus/kafka-ui/raw/master/documentation/images/kafka-ui-logo.png
diff --git a/charts/kafka-ui/templates/_helpers.tpl b/charts/kafka-ui/templates/_helpers.tpl
index 510452d4cf3..7155681a44b 100644
--- a/charts/kafka-ui/templates/_helpers.tpl
+++ b/charts/kafka-ui/templates/_helpers.tpl
@@ -68,6 +68,11 @@ This allows us to check if the registry of the image is specified or not.
 */}}
 {{- define "kafka-ui.imageName" -}}
 {{- $registryName := .Values.image.registry -}}
+{{- if .Values.global }}
+    {{- if .Values.global.imageRegistry }}
+     {{- $registryName = .Values.global.imageRegistry -}}
+    {{- end -}}
+{{- end -}}
 {{- $repository := .Values.image.repository -}}
 {{- $tag := .Values.image.tag | default .Chart.AppVersion -}}
 {{- if $registryName }}


Test patch:
Repository: provectus/kafka-ui
Issue: [UI] Schema paths are displayed differently for compare versions and edit
Labels: good first issue
scope/frontend
status/accepted
type/chore

**Describe the bug**
Schema name displayed in a path for Compare versions

**Set up**
https://www.kafka-ui.provectus.io/


**Steps to Reproduce**

1. Navigate to Schema registry
2. Select any schema
3. Press Compare versions
4. Check the path to be [Schema name/Compare versions]
5. Turn back to Schema profile
6. Press Edit
7. Check the path

 **Actual behavior:** Only Edit exists in a path without Schema name

**Expected behavior**
Would be better to keep consistency, remove or keep schema name for both

**Screenshots**

https://user-images.githubusercontent.com/104780608/206220499-9626fe94-1ff9-4dfc-8ea4-69f377fc2ade.mov




**Additional context**

**Priority:** low


Issue comments:

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Schemas/Edit/Form.tsx b/kafka-ui-react-app/src/components/Schemas/Edit/Form.tsx
index ea414ab4b4d..9ce7f280f43 100644
--- a/kafka-ui-react-app/src/components/Schemas/Edit/Form.tsx
+++ b/kafka-ui-react-app/src/components/Schemas/Edit/Form.tsx
@@ -110,7 +110,7 @@ const Form: React.FC = () => {
   return (
     <FormProvider {...methods}>
       <PageHeading
-        text="Edit"
+        text={`${subject} Edit`}
         backText="Schema Registry"
         backTo={clusterSchemasPath(clusterName)}
       />


Test patch:
Repository: provectus/kafka-ui
Issue: Topics: Messages filtering by seek type is broken within Topic profile
Labels: type/bug
scope/frontend
status/accepted
status/confirmed
type/regression
severity/high


**Describe the bug** (Actual behavior)
Messages filtering by seek type (Offset, Timestamp) is broken within Topic profile

**Expected behavior**
Should be possible to filter messages by Offset/Timestamp

**Set up**

https://www.kafka-ui.provectus.io/

**Steps to Reproduce**
<!-- We'd like you to provide an example setup (via docker-compose, helm, etc.) 
to reproduce the problem, especially with a complex setups. -->

1. Login to kafka-ui
2. Navigate to Topics
3. Select the Topic
4. Turn to Messages tab
5. Add new messages
6. Select seek type (Offset/Timestamp)
7. Press Submit

**Screenshots**

https://user-images.githubusercontent.com/104780608/217451012-2888e38d-0346-49fc-82cc-b89d43ed12cb.mov





Issue comments:
Filtering by offset still unavailable


https://user-images.githubusercontent.com/104780608/228433188-be5f19f6-9057-42a1-a84a-0c594c0f1f73.mov



Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Topics/Topic/Messages/Filters/Filters.tsx b/kafka-ui-react-app/src/components/Topics/Topic/Messages/Filters/Filters.tsx
index c3871432e70..ec62f266ed4 100644
--- a/kafka-ui-react-app/src/components/Topics/Topic/Messages/Filters/Filters.tsx
+++ b/kafka-ui-react-app/src/components/Topics/Topic/Messages/Filters/Filters.tsx
@@ -231,7 +231,10 @@ const Filters: React.FC<FiltersProps> = ({
         props.seekType = SeekType.TIMESTAMP;
       }
 
-      if (selectedPartitions.length !== partitions.length) {
+      if (
+        selectedPartitions.length !== partitions.length ||
+        currentSeekType === SeekType.TIMESTAMP
+      ) {
         // not everything in the partition is selected
         props.seekTo = selectedPartitions.map(({ value }) => {
           const offsetProperty =


Test patch:
Repository: provectus/kafka-ui
Issue: Dark theme: 404: Text is black
Labels: good first issue
scope/frontend
status/accepted
type/chore

with a dark theme, the text on the 404 page (page not found) is black. Please adapt.

Issue comments:
Could you assign this to me? I finished it rn, just need to find how to make a pr that satisfied the rules
Great! I've already published a pr, however, I can not add labels and assign myself to the pr or add reviewers to the pr as the contributing documentation says. Could you help me with that?

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/ErrorPage/ErrorPage.styled.ts b/kafka-ui-react-app/src/components/ErrorPage/ErrorPage.styled.ts
index fc6e0332db2..b24d6de564e 100644
--- a/kafka-ui-react-app/src/components/ErrorPage/ErrorPage.styled.ts
+++ b/kafka-ui-react-app/src/components/ErrorPage/ErrorPage.styled.ts
@@ -17,4 +17,5 @@ export const Number = styled.div`
 
 export const Text = styled.div`
   font-size: 20px;
+  color: ${({ theme }) => theme.default.color.normal};
 `;


Test patch:
Repository: provectus/kafka-ui
Issue: FE: Topics: Remove a success message upon creating a topic
Labels: good first issue
scope/frontend
status/accepted
type/chore


**Describe the bug** (Actual behavior)
The success message appears on topic profile after create topic 

**Expected behavior**
In case system redirects to new created Topic profile, no need to have a success message

**Set up**
https://www.kafka-ui.provectus.io/


**Steps to Reproduce**
<!-- We'd like you to provide an example setup (via docker-compose, helm, etc.) 
to reproduce the problem, especially with a complex setups. -->

1. Navigate to Topics
2. Add a new topic
3. Fill the required fields
4. Press Save

**Screenshots**

https://user-images.githubusercontent.com/104780608/221803973-bbe5697d-9120-4432-951a-62e37e5c6c9d.mov






Issue comments:

Pull request review comments:
`client.invalidateQueries(topicKeys.all(clusterName));`
this has to be left intact I suppose
Also, please remove the code instead of commenting it

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/lib/hooks/api/topics.ts b/kafka-ui-react-app/src/lib/hooks/api/topics.ts
index f71299f19bb..a87673368dd 100644
--- a/kafka-ui-react-app/src/lib/hooks/api/topics.ts
+++ b/kafka-ui-react-app/src/lib/hooks/api/topics.ts
@@ -122,9 +122,6 @@ export function useCreateTopicMutation(clusterName: ClusterName) {
       }),
     {
       onSuccess: () => {
-        showSuccessAlert({
-          message: `Topic successfully created.`,
-        });
         client.invalidateQueries(topicKeys.all(clusterName));
       },
     }


Test patch:
diff --git a/kafka-ui-e2e-checks/src/test/java/com/provectus/kafka/ui/smokesuite/topics/TopicsTest.java b/kafka-ui-e2e-checks/src/test/java/com/provectus/kafka/ui/smokesuite/topics/TopicsTest.java
index ad20f595a4f..bad6a9fcde0 100644
--- a/kafka-ui-e2e-checks/src/test/java/com/provectus/kafka/ui/smokesuite/topics/TopicsTest.java
+++ b/kafka-ui-e2e-checks/src/test/java/com/provectus/kafka/ui/smokesuite/topics/TopicsTest.java
@@ -486,11 +486,7 @@ public void checkCopyTopicPossibility() {
     topicDetails
         .waitUntilScreenReady();
     TOPIC_LIST.add(topicToCopy);
-    SoftAssert softly = new SoftAssert();
-    softly.assertTrue(topicDetails.isAlertWithMessageVisible(SUCCESS, "Topic successfully created."),
-        "isAlertWithMessageVisible()");
-    softly.assertTrue(topicDetails.isTopicHeaderVisible(topicToCopy.getName()), "isTopicHeaderVisible()");
-    softly.assertAll();
+    Assert.assertTrue(topicDetails.isTopicHeaderVisible(topicToCopy.getName()), "isTopicHeaderVisible()");
   }
 
   @AfterClass(alwaysRun = true)
Repository: provectus/kafka-ui
Issue: [Topics]  All topics are unchecking with Toggling off Show Internal Topics
Labels: type/bug
good first issue
scope/frontend
status/accepted
status/confirmed



**Describe the bug** (Actual behavior)
All topics checking (unchecking) with toggling off(on) the Show internal Topics

**Expected behavior**
In case of toggling the Show internal Topics, the Topics should not becomes checked(unchecked) as the Internal topics are not checkable in any cases

**Set up**

https://www.kafka-ui.provectus.io/


**Steps to Reproduce**
<!-- We'd like you to provide an example setup (via docker-compose, helm, etc.) 
to reproduce the problem, especially with a complex setups. -->

1. Login to Kafka-ui
2. Navigate to Topics
3. Make sure Show Internal Topics is toggled on
4. Check all topics with on top checkbox
5. Toggle off the Show Internal Topics



https://user-images.githubusercontent.com/104780608/214019758-7d8d3fa9-d8c3-4df6-adf6-34bc4f5193a7.mov






Issue comments:

Pull request review comments:
Do we need the to put it in a string quotation string  literals here for the `${originalRow.name}`?
I think not, it is obviously a string value)
Isn't it already a string?
Yes, it's a string, so we do not need quotation marks - update in a moment

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/common/NewTable/Table.tsx b/kafka-ui-react-app/src/components/common/NewTable/Table.tsx
index 1cdc67001d7..55652df082d 100644
--- a/kafka-ui-react-app/src/components/common/NewTable/Table.tsx
+++ b/kafka-ui-react-app/src/components/common/NewTable/Table.tsx
@@ -142,15 +142,12 @@ const Table: React.FC<TableProps<any>> = ({
     (updater: UpdaterFn<PaginationState>) => {
       const newState = updatePaginationState(updater, searchParams);
       setSearchParams(searchParams);
+      setRowSelection({});
       return newState;
     },
     [searchParams]
   );
 
-  React.useEffect(() => {
-    setRowSelection({});
-  }, [searchParams]);
-
   const table = useReactTable({
     data,
     pageCount,
@@ -160,6 +157,9 @@ const Table: React.FC<TableProps<any>> = ({
       pagination: getPaginationFromSearchParams(searchParams),
       rowSelection,
     },
+    getRowId: (originalRow, index) => {
+      return originalRow.name ? originalRow.name : `${index}`;
+    },
     onSortingChange: onSortingChange as OnChangeFn<SortingState>,
     onPaginationChange: onPaginationChange as OnChangeFn<PaginationState>,
     onRowSelectionChange: setRowSelection,


Test patch:
Repository: provectus/kafka-ui
Issue: Topics: Messages: 404 with schema created by .NET containing guid
Labels: type/bug
scope/frontend
status/accepted
type/regression

**Describe the bug** (Actual behavior)
When viewing the list of messages for a topic, if the schema has been created from .NET with a GUID field, Kafka UI returns a 404 due to it only accepting the format to be UUID. When we do a string replace to change guid to uuid, the messages show correctly provided the latest version of the schema has "uuid" for the format.

**Expected behavior**
Kafka UI should be allowing guids to be displayed and in an earlier version this worked correctly. It only seems to have started since moving to version 0.6.0.

**Set up**
Commit: https://github.com/provectus/kafka-ui/commit/e72f6d6
Version: v0.6.0
Environment: AWS ECS

**Steps to Reproduce**
In .NET create a class that contains a guid property and then use Confluent.SchemaRegistry.Serdes.Json.JsonSerializer for the value/key Serializer to generate the schema that is sent to the schema registry.

**Screenshots**
![image](https://user-images.githubusercontent.com/36782274/227066995-b477a385-040f-48e3-9f3b-ec3273f06010.png)


**Additional context**
An alternative is to do a string replace and disable the AutoRegisterSchema option in the configuration settings of the JsonSerializer. However, the AutoRegisterSchema option would need to be disabled for any connections otherwise the "guid" format value will reappear as the latest version of the schema and break the display again.


Issue comments:
Hello there AaronCoad! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀
Checked BE - all endpoints work as expected (json-schema schemas are not processed on BE at all).  I guess UI library that parses serde's schemas might fail on frontend. 

@Haarolean , please reassign to someone from FE team

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Topics/Topic/SendMessage/utils.ts b/kafka-ui-react-app/src/components/Topics/Topic/SendMessage/utils.ts
index 8a368036c06..6f98c5916d3 100644
--- a/kafka-ui-react-app/src/components/Topics/Topic/SendMessage/utils.ts
+++ b/kafka-ui-react-app/src/components/Topics/Topic/SendMessage/utils.ts
@@ -11,6 +11,7 @@ import upperFirst from 'lodash/upperFirst';
 
 jsf.option('fillProperties', false);
 jsf.option('alwaysFakeOptionals', true);
+jsf.option('failOnInvalidFormat', false);
 
 const generateValueFromSchema = (preffered?: SerdeDescription) => {
   if (!preffered?.schema) {


Test patch:
Repository: provectus/kafka-ui
Issue: Edit config: Selected text background color is transparent
Labels: good first issue
scope/frontend
status/triage
type/chore

1. create connector
2. select some text within config field
3. the selection is not visible

Issue comments:

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/common/Editor/Editor.tsx b/kafka-ui-react-app/src/components/common/Editor/Editor.tsx
index b8744762c96..05c91e3557b 100644
--- a/kafka-ui-react-app/src/components/common/Editor/Editor.tsx
+++ b/kafka-ui-react-app/src/components/common/Editor/Editor.tsx
@@ -50,8 +50,10 @@ export default styled(Editor)`
         theme.ksqlDb.query.editor.cell.backgroundColor};
       color: ${({ theme }) => theme.default.color.normal};
     }
-    .ace_line {
+    .ace_scroller {
       background-color: ${({ theme }) => theme.default.backgroundColor};
+    }
+    .ace_line {
       color: ${({ theme }) => theme.default.color.normal};
     }
     .ace_cursor {
diff --git a/kafka-ui-react-app/src/components/common/EditorViewer/EditorViewer.styled.ts b/kafka-ui-react-app/src/components/common/EditorViewer/EditorViewer.styled.ts
index d60603f635c..a135f4dfcc2 100644
--- a/kafka-ui-react-app/src/components/common/EditorViewer/EditorViewer.styled.ts
+++ b/kafka-ui-react-app/src/components/common/EditorViewer/EditorViewer.styled.ts
@@ -5,7 +5,7 @@ export const Wrapper = styled.div`
   padding: 8px 16px;
   .ace_active-line {
     background-color: ${({ theme }) =>
-      theme.viewer.wrapper.backgroundColor} !important;
+      theme.default.backgroundColor} !important;
   }
   .ace_line {
     color: ${({ theme }) => theme.viewer.wrapper.color} !important;


Test patch:
Repository: provectus/kafka-ui
Issue: Get rid of "Topic analysis successfully started" message
Labels: good first issue
scope/frontend
status/accepted
type/chore

It makes no sense considering the page contents changes

Issue comments:
can you assign me this issue

@Karthik-PM sure :)
@Karthik-PM any luck?
sorry can i get some more time?  i have been facing a lot of build errors

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/lib/hooks/api/topics.ts b/kafka-ui-react-app/src/lib/hooks/api/topics.ts
index 23e6d65ce37..f71299f19bb 100644
--- a/kafka-ui-react-app/src/lib/hooks/api/topics.ts
+++ b/kafka-ui-react-app/src/lib/hooks/api/topics.ts
@@ -314,9 +314,6 @@ export function useAnalyzeTopic(props: GetTopicDetailsRequest) {
   const client = useQueryClient();
   return useMutation(() => api.analyzeTopic(props), {
     onSuccess: () => {
-      showSuccessAlert({
-        message: `Topic analysis successfully started`,
-      });
       client.invalidateQueries(topicKeys.statistics(props));
     },
   });


Test patch: