feedback-to-code/mozzarella huggingface dataset:
Repository: provectus/kafka-ui
Issue: Add "Total size" of Partition within Topic's statistics
Labels: good first issue
scope/frontend
status/accepted
type/chore
hacktoberfest



**Describe the bug**
Add "Total size" of Partition within Topic's statistics

**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. -->
Steps to reproduce the behavior:

1. Navigate to Topics
2. Open the Topic
3. Turn to Statistics tab
4. Open the Partition

**Expected behavior**
Total size should be displayed

**Screenshots**
<img width="1717" alt="total size" src="https://user-images.githubusercontent.com/104780608/188836260-3d02590b-23b2-4b89-b440-4d0c29e3e87e.png">






Issue comments:

Pull request review comments:
pls use BytesFormatted here
done

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Topics/Topic/Statistics/PartitionInfoRow.tsx b/kafka-ui-react-app/src/components/Topics/Topic/Statistics/PartitionInfoRow.tsx
index 546f3e619d6..698019f2c44 100644
--- a/kafka-ui-react-app/src/components/Topics/Topic/Statistics/PartitionInfoRow.tsx
+++ b/kafka-ui-react-app/src/components/Topics/Topic/Statistics/PartitionInfoRow.tsx
@@ -27,7 +27,6 @@ const PartitionInfoRow: React.FC<{ row: Row<TopicAnalysisStats> }> = ({
     keySize,
     valueSize,
   } = row.original;
-
   return (
     <S.PartitionInfo>
       <div>
@@ -35,6 +34,8 @@ const PartitionInfoRow: React.FC<{ row: Row<TopicAnalysisStats> }> = ({
         <List>
           <Label>Total message</Label>
           <span>{totalMsgs}</span>
+          <Label>Total size</Label>
+          <BytesFormatted value={(keySize?.sum || 0) + (valueSize?.sum || 0)} />
           <Label>Min. timestamp</Label>
           <span>{formatTimestamp(minTimestamp)}</span>
           <Label>Max. timestamp</Label>


Test patch:
Repository: provectus/kafka-ui
Issue: Add warning message for Danger zone in case of editing the Topic
Labels: good first issue
scope/frontend
status/accepted
type/chore
hacktoberfest

Warning message should be displayed for Danger zone with editing the Topic

**Describe the bug**

Warning message should be displayed for Danger zone with editing the Topic


**Set up**
https://www.kafka-ui.provectus.io/


**Steps to Reproduce**

1. Navigate to Topics
2. Open any Topic
3. Edit settings
4. Check Danger zone


**Expected behavior**
Should be displayed warning message:"Change these parameters only if you are absolutely sure that you are doing."

**Screenshots**
<img width="1717" alt="warning message edit" src="https://user-images.githubusercontent.com/104780608/188640196-220b54ee-1c43-47fc-bc82-a7532f584e3d.png">





Issue comments:

Pull request review comments:
pls use existing palete
done
```suggestion
        Change these parameters only if you are absolutely sure what you are
```

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Topics/Topic/Edit/DangerZone/DangerZone.styled.tsx b/kafka-ui-react-app/src/components/Topics/Topic/Edit/DangerZone/DangerZone.styled.tsx
index b9ad51a669e..b5741c67e19 100644
--- a/kafka-ui-react-app/src/components/Topics/Topic/Edit/DangerZone/DangerZone.styled.tsx
+++ b/kafka-ui-react-app/src/components/Topics/Topic/Edit/DangerZone/DangerZone.styled.tsx
@@ -15,11 +15,15 @@ export const Wrapper = styled.div`
 `;
 
 export const Title = styled.h1`
-  color: ${({ theme }) => theme.dangerZone.color};
+  color: ${({ theme }) => theme.dangerZone.color.title};
   font-size: 20px;
   padding-bottom: 16px;
 `;
-
+export const Warning = styled.div`
+  color: ${({ theme }) => theme.dangerZone.color.warningMessage};
+  font-size: 12px;
+  padding-bottom: 16px;
+`;
 export const Form = styled.form`
   display: flex;
   align-items: flex-end;
diff --git a/kafka-ui-react-app/src/components/Topics/Topic/Edit/DangerZone/DangerZone.tsx b/kafka-ui-react-app/src/components/Topics/Topic/Edit/DangerZone/DangerZone.tsx
index 49f1d3574a4..59016d1d7a4 100644
--- a/kafka-ui-react-app/src/components/Topics/Topic/Edit/DangerZone/DangerZone.tsx
+++ b/kafka-ui-react-app/src/components/Topics/Topic/Edit/DangerZone/DangerZone.tsx
@@ -81,6 +81,10 @@ const DangerZone: React.FC<DangerZoneProps> = ({
   return (
     <S.Wrapper>
       <S.Title>Danger Zone</S.Title>
+      <S.Warning>
+        Change these parameters only if you are absolutely sure what you are
+        doing.
+      </S.Warning>
       <div>
         <FormProvider {...partitionsMethods}>
           <S.Form
diff --git a/kafka-ui-react-app/src/theme/theme.ts b/kafka-ui-react-app/src/theme/theme.ts
index d05ad54cb94..19c082c2840 100644
--- a/kafka-ui-react-app/src/theme/theme.ts
+++ b/kafka-ui-react-app/src/theme/theme.ts
@@ -518,7 +518,10 @@ const theme = {
   },
   dangerZone: {
     borderColor: Colors.neutral[10],
-    color: Colors.red[50],
+    color: {
+      title: Colors.red[50],
+      warningMessage: Colors.neutral[50],
+    },
   },
   configList: {
     color: Colors.neutral[30],


Test patch:
Repository: provectus/kafka-ui
Issue: Topic list: Rename "total partitions" to "partitions"
Labels: good first issue
scope/frontend
status/accepted
type/chore
hacktoberfest

<img width="299" alt="image" src="https://user-images.githubusercontent.com/1494347/193238757-d6f3d11f-05dd-4d77-bd02-972ed95cfb3a.png">


Issue comments:

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Topics/List/TopicTable.tsx b/kafka-ui-react-app/src/components/Topics/List/TopicTable.tsx
index a855435c876..dcafa61b915 100644
--- a/kafka-ui-react-app/src/components/Topics/List/TopicTable.tsx
+++ b/kafka-ui-react-app/src/components/Topics/List/TopicTable.tsx
@@ -42,7 +42,7 @@ const TopicTable: React.FC = () => {
       },
       {
         id: TopicColumnsToSort.TOTAL_PARTITIONS,
-        header: 'Total Partitions',
+        header: 'Partitions',
         accessorKey: 'partitionCount',
       },
       {


Test patch:
Repository: provectus/kafka-ui
Issue: No custom `annotations` on the level of the `Deployment` metadata
Labels: type/enhancement
good first issue
status/accepted
scope/k8s

<!--

Don't forget to check for existing issues/discussions regarding your proposal. We might already have it.
https://github.com/provectus/kafka-ui/issues
https://github.com/provectus/kafka-ui/discussions

-->

**Describe the bug**
<!--(A clear and concise description of what the bug is.)-->
Not really a bug, however, a missing small feature. Deployment object `annotations` should be given as a configuration parameter to the users of the Helm Charts.

A PR can follow to work on that.

**Set up**
<!--
How do you run the app? Please provide as much info as possible:
1. App version (docker image version or check commit hash in the top left corner in UI)
2. Helm chart version, if you use one
3. Any IAAC configs

We might close the issue without further explanation if you don't provide such information.
-->
Using Helm


**Steps to Reproduce**
Steps to reproduce the behavior:

**Expected behavior**
<!--
(A clear and concise description of what you expected to happen)
-->

**Screenshots**
<!--
(If applicable, add screenshots to help explain your problem)
-->


**Additional context**
<!--
(Add any other context about the problem here)
-->


Issue comments:
Hey, thanks for reaching out.

We'll be glad to see a PR addressing this issue.
Hello there sherifkayad! 👋

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. 👀
@Haarolean PR added to this issue ;) Looking forward.

Pull request review comments:

Patch that resolved the issue:
diff --git a/charts/kafka-ui/Chart.yaml b/charts/kafka-ui/Chart.yaml
index 1ecf0eeecea..2ae296b4ee6 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.4.5
+version: 0.4.6
 appVersion: v0.4.0
 icon: https://github.com/provectus/kafka-ui/raw/master/documentation/images/kafka-ui-logo.png
diff --git a/charts/kafka-ui/templates/deployment.yaml b/charts/kafka-ui/templates/deployment.yaml
index 51703c7ed30..a253fc6df51 100644
--- a/charts/kafka-ui/templates/deployment.yaml
+++ b/charts/kafka-ui/templates/deployment.yaml
@@ -4,6 +4,10 @@ metadata:
   name: {{ include "kafka-ui.fullname" . }}
   labels:
     {{- include "kafka-ui.labels" . | nindent 4 }}
+  {{- with .Values.annotations }}
+  annotations:
+    {{- toYaml . | nindent 4 }}
+  {{- end }}
 spec:
 {{- if not .Values.autoscaling.enabled }}
   replicas: {{ .Values.replicaCount }}
diff --git a/charts/kafka-ui/values.yaml b/charts/kafka-ui/values.yaml
index 93d08100d97..35e3ad3dd59 100644
--- a/charts/kafka-ui/values.yaml
+++ b/charts/kafka-ui/values.yaml
@@ -69,6 +69,10 @@ networkPolicy:
 podAnnotations: {}
 podLabels: {}
 
+## Annotations to be added to kafka-ui Deployment
+##
+annotations: {}
+
 podSecurityContext:
   {}
   # fsGroup: 2000


Test patch:
Repository: provectus/kafka-ui
Issue: Make it possible to update helm chart without an actual app release
Labels: type/enhancement
good first issue
status/accepted
hacktoberfest
scope/infrastructure
scope/k8s


Issue comments:
#2632

Pull request review comments:

Patch that resolved the issue:
diff --git a/.github/workflows/helm.yaml b/.github/workflows/helm.yaml
index 255f92260f9..d8c2875aed7 100644
--- a/.github/workflows/helm.yaml
+++ b/.github/workflows/helm.yaml
@@ -15,6 +15,18 @@ jobs:
         uses: Azure/setup-helm@v1
       - name: Setup Kubeval
         uses: lra/setup-kubeval@v1.0.1
+      #check, was helm version increased in Chart.yaml?
+      - name: Check version
+        shell: bash
+        run: |
+          git fetch
+          git checkout master
+          helm_version_old=$(cat charts/kafka-ui/Chart.yaml  | grep version | awk  '{print $2}')
+          git checkout $GITHUB_HEAD_REF
+          helm_version_new=$(cat charts/kafka-ui/Chart.yaml  | grep version | awk  '{print $2}')
+          echo $helm_version_old
+          echo $helm_version_new
+          if [[ "$helm_version_new" > "$helm_version_old" ]]; then exit 0 ; else exit 1 ; fi
       - name: Run kubeval
         shell: bash
         run: |


Test patch:
Repository: provectus/kafka-ui
Issue: [UI] Topic search not working properly with pagination 
Labels: type/bug
good first issue
scope/frontend
status/accepted
status/confirmed
hacktoberfest

**Setup:**
version in c961344
 
**Description:**
1. Go to Topics page
2. move to page 2
3. enter something into topic search field
-> request sent with `page=2` parameter which will force BE to search **on the second page**, which will lead to wrong results 

<img width="904" alt="Screenshot 2022-10-06 at 10 59 46" src="https://user-images.githubusercontent.com/702205/194235461-dbd248e0-ef72-4079-9b6f-96ae37d54224.png">


**Expected behaviour:**
When something new was entered into search field pagination should be reset

---

**Note:** such behaviour should be fixed in all places where pagination is used: SchemaRegistry, Consumers

Issue comments:

Pull request review comments:
what if there is no page property?

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/common/Search/Search.tsx b/kafka-ui-react-app/src/components/common/Search/Search.tsx
index 9baf1ed3b2e..66c0e95030b 100644
--- a/kafka-ui-react-app/src/components/common/Search/Search.tsx
+++ b/kafka-ui-react-app/src/components/common/Search/Search.tsx
@@ -22,6 +22,9 @@ const Search: React.FC<SearchProps> = ({
       onChange(e.target.value);
     } else {
       searchParams.set('q', e.target.value);
+      if (searchParams.get('page')) {
+        searchParams.set('page', '1');
+      }
       setSearchParams(searchParams);
     }
   }, 500);


Test patch:
Repository: provectus/kafka-ui
Issue: Unable to update topic config in case of retain time has been changed
Labels: type/bug
good first issue
scope/frontend
status/accepted
status/confirmed
hacktoberfest

1. Edit any topic
2. Change "time to retain data" via **selectors**
3. "Update topic" button is still disabled

Issue comments:

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Topics/shared/Form/TimeToRetainBtn.tsx b/kafka-ui-react-app/src/components/Topics/shared/Form/TimeToRetainBtn.tsx
index 2364d90516a..8746eef7929 100644
--- a/kafka-ui-react-app/src/components/Topics/shared/Form/TimeToRetainBtn.tsx
+++ b/kafka-ui-react-app/src/components/Topics/shared/Form/TimeToRetainBtn.tsx
@@ -18,7 +18,11 @@ const TimeToRetainBtn: React.FC<Props> = ({ inputName, text, value }) => {
     <S.Button
       isActive={parseFloat(watchedValue) === value}
       type="button"
-      onClick={() => setValue(inputName, value)}
+      onClick={() =>
+        setValue(inputName, value, {
+          shouldDirty: true,
+        })
+      }
     >
       {text}
     </S.Button>


Test patch:
Repository: provectus/kafka-ui
Issue: Wrong actuator path with custom SERVER_SERVLET_CONTEXT_PATH
Labels: type/bug
good first issue
scope/frontend
status/accepted
hacktoberfest
type/regression

**Describe the bug**

When settings SERVER_SERVLET_CONTEXT_PATH to /kafka-ui, actuator is deployed 
with /kafka-ui/actuator/info, but application asks for /actuator/info.

This is a regression from v0.4.0 (which we used before) - it works fine on v0.4.0 (maybe because v0.4.0 does not seem to be asking for /actuator/info endpoint).

**Set up**
Install latest version (c22b6b468c61da1d1a647352405f63cd0670e493335743de6c7f24a519264b35) with
SERVER_SERVLET_CONTEXT_PATH: /kafka-ui

**Steps to Reproduce**

1. go to the landing page

**Expected behavior**
Landing page works and asks for acutator in correct path (/kafka-ui/actuator/info).

**Screenshots**
Not working (c22b6b468c61da1d1a647352405f63cd0670e493335743de6c7f24a519264b35) :
![image](https://user-images.githubusercontent.com/23450695/196111995-150274fa-9415-483e-a28d-78447b8943e7.png)



Issue comments:
Hello there vliska! 👋

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. 👀
Hey, thanks for reaching out. We'll take a look

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/lib/hooks/api/actuatorInfo.ts b/kafka-ui-react-app/src/lib/hooks/api/actuatorInfo.ts
index 8373bf53d38..7e1835d9079 100644
--- a/kafka-ui-react-app/src/lib/hooks/api/actuatorInfo.ts
+++ b/kafka-ui-react-app/src/lib/hooks/api/actuatorInfo.ts
@@ -2,9 +2,10 @@ import { useQuery } from '@tanstack/react-query';
 import { BASE_PARAMS, QUERY_REFETCH_OFF_OPTIONS } from 'lib/constants';
 
 const fetchActuatorInfo = async () => {
-  const data = await fetch('/actuator/info', BASE_PARAMS).then((res) =>
-    res.json()
-  );
+  const data = await fetch(
+    `${BASE_PARAMS.basePath}/actuator/info`,
+    BASE_PARAMS
+  ).then((res) => res.json());
 
   return data;
 };


Test patch:
Repository: provectus/kafka-ui
Issue: KSQL: "Execute KSQL Request" Stream properties overlayed by KSQL query window
Labels: type/bug
good first issue
scope/frontend
status/accepted
status/confirmed
hacktoberfest


**Describe the bug**
Layout of the KSQL query window is broken and Stream properties input left border is way under the KSQL query window.

**Set up**
[0939d61](https://github.com/provectus/kafka-ui/commit/0939d61)

**Steps to Reproduce**
1. Open the KSQL tab.
2. Push the "Execute KSQL Request" button
**Actual behavior**
All the stream properties edit fields are under the query window (all the additional ones are as well)
https://user-images.githubusercontent.com/112083452/195013920-933b7580-5f80-4d2c-afab-84ae089d6324.mov


**Expected behavior**
Normal window layout for every field. Including all the additional stream properties.

**Additional context**
Additional stream properties are also under the query window.

Issue comments:
I'd like to give it a try! Could I get assigned to this task please?
Sure, please. On 22 Oct 2022, at 08:59, Artem Tanyhin ***@***.***> wrote:﻿
I'd like to give it a try! Could I get assigned to this task please?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/KsqlDb/Query/QueryForm/QueryForm.styled.ts b/kafka-ui-react-app/src/components/KsqlDb/Query/QueryForm/QueryForm.styled.ts
index a8fa1cf7afa..3fc59fcecf4 100644
--- a/kafka-ui-react-app/src/components/KsqlDb/Query/QueryForm/QueryForm.styled.ts
+++ b/kafka-ui-react-app/src/components/KsqlDb/Query/QueryForm/QueryForm.styled.ts
@@ -34,17 +34,22 @@ export const StreamPropertiesContainer = styled.label`
 `;
 
 export const InputsContainer = styled.div`
+  overflow: hidden;
+  width: 100%;
   display: flex;
   justify-content: center;
   gap: 10px;
 `;
 
 export const StreamPropertiesInputWrapper = styled.div`
+  & {
+    width: 100%;
+  }
   & > input {
+    width: 100%;
     height: 40px;
     border: 1px solid grey;
     border-radius: 4px;
-    min-width: 300px;
     font-size: 16px;
     padding-left: 15px;
   }


Test patch:
Repository: provectus/kafka-ui
Issue: [UI] Do not cache `serdes` endpoint results on frontend
Labels: type/bug
good first issue
scope/frontend
status/accepted

**Description**

`serdes` endpoint responses should not be cached on frontend, because its responses relates to schema-registry state, which can be changed any time. Also, endpoint should work fast, so, there should be no performance impart on calling it .

Issue comments:
Hi I would like to work on this.Would you assign  me please ?
Hey, sure. 

> On 4 Oct 2022, at 00:02, fMurugi ***@***.***> wrote:
> 
> ﻿
> Hi I would like to work on this.Would you assign me please ?
> 
> —
> Reply to this email directly, view it on GitHub, or unsubscribe.
> You are receiving this because you are subscribed to this thread.

i have a question, how are you caching these results.I cant figure out.

@iliax ?
@fMurugi 
I don't know where exact FE code in placed, but if you first go to some topic page FE will call `serdes` endpoints. After that if go back to Topics list page and go to same topic again - FE wont do any `serdes` calls anymore. (hard-refresh fixing this situation Ctr - shift - R) 

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/lib/hooks/api/topicMessages.tsx b/kafka-ui-react-app/src/lib/hooks/api/topicMessages.tsx
index 941841f11ba..1357a15ea32 100644
--- a/kafka-ui-react-app/src/lib/hooks/api/topicMessages.tsx
+++ b/kafka-ui-react-app/src/lib/hooks/api/topicMessages.tsx
@@ -183,11 +183,11 @@ export const useTopicMessages = ({
 
 export function useSerdes(props: GetSerdesRequest) {
   const { clusterName, topicName, use } = props;
+
   return useQuery(
     ['clusters', clusterName, 'topics', topicName, 'serdes', use],
     () => messagesApiClient.getSerdes(props),
     {
-      refetchOnMount: false,
       refetchOnWindowFocus: false,
       refetchOnReconnect: false,
       refetchInterval: false,


Test patch:
Repository: provectus/kafka-ui
Issue: Topic creation: lock page until creation request finished
Labels: type/bug
good first issue
scope/frontend
status/accepted

**Steps to reproduce:**
1. Go to topic creation page
2. click create topic 
-> page is not locked, and if topic creation is slow than it is possible to click create multiple time. 

**How to fix:**
Lock page and show progress bar while waiting for server response

cc @armenuikafka 


https://user-images.githubusercontent.com/702205/196905138-a9dfd03b-7a07-44c6-a261-b003f8e9016c.mov



Issue comments:

Pull request review comments:
can we use id submitting property of TopicForm component?

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/src/components/Topics/New/New.tsx b/kafka-ui-react-app/src/components/Topics/New/New.tsx
index cf992789362..1fbd59090d2 100644
--- a/kafka-ui-react-app/src/components/Topics/New/New.tsx
+++ b/kafka-ui-react-app/src/components/Topics/New/New.tsx
@@ -57,7 +57,7 @@ const New: React.FC = () => {
           partitionCount={Number(partitionCount)}
           replicationFactor={Number(replicationFactor)}
           inSyncReplicas={Number(inSyncReplicas)}
-          isSubmitting={false}
+          isSubmitting={createTopic.isLoading}
           onSubmit={methods.handleSubmit(onSubmit)}
         />
       </FormProvider>


Test patch:
Repository: provectus/kafka-ui
Issue: 0.4.0 Image Tag Does Not Match
Labels: status/accepted
scope/k8s

**Steps to Reproduce**
Steps to reproduce the behavior:

1. Deploy current main helm chart

**Expected behavior**
The chart defaults that if no tag is defined, the chart app version is used.  

Published Docker Tag: `v0.4.0`

Helm Helper:
```
{{- $tag := .Values.image.tag | default .Chart.AppVersion -}}
```

Chart Value:
```
appVersion: 0.4.0
```

**Screenshots**
Docker:
![image](https://user-images.githubusercontent.com/3513589/198065920-feb93aef-254c-49d4-851d-e2c800a0a4a0.png)

Deployed Tag:
<img width="356" alt="image" src="https://user-images.githubusercontent.com/3513589/198065992-6d6370ce-f14b-43a3-bd25-cfb68280f858.png">


**Additional context**
Not sure if you'd rather update the appVersion in chart to be `"v0.4.0"` or publish a new tag to Docker.


Issue comments:
Hello there treyhendon! 👋

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. 👀
Done in #2842, thank you

Pull request review comments:

Patch that resolved the issue:
diff --git a/charts/kafka-ui/Chart.yaml b/charts/kafka-ui/Chart.yaml
index 89982674019..2da8388a44a 100644
--- a/charts/kafka-ui/Chart.yaml
+++ b/charts/kafka-ui/Chart.yaml
@@ -3,5 +3,5 @@ name: kafka-ui
 description: A Helm chart for kafka-UI
 type: application
 version: 0.4.4
-appVersion: 0.4.0
+appVersion: v0.4.0
 icon: https://github.com/provectus/kafka-ui/raw/master/documentation/images/kafka-ui-logo.png


Test patch:
Repository: provectus/kafka-ui
Issue: React Documentation Readme Includes a Link to create-react-app
Labels: type/documentation
scope/frontend

I don't think create react app link is relevant in the documentation , since nowadays the app uses Vite as a module bundler , where create-react-app uses Webpack and we don't rely on react-script to build the application, we should replace it with Vite source code link.

<img width="1712" alt="image" src="https://user-images.githubusercontent.com/46796009/198550641-1b383bbd-dda5-4927-bd8f-e1979529a160.png">


Issue comments:

Pull request review comments:

Patch that resolved the issue:
diff --git a/kafka-ui-react-app/README.md b/kafka-ui-react-app/README.md
index 8e5ea6ebf3b..8ab814cd1d5 100644
--- a/kafka-ui-react-app/README.md
+++ b/kafka-ui-react-app/README.md
@@ -66,4 +66,4 @@ pnpm start
 ```
 ## Links
 
-* [Create React App](https://github.com/facebook/create-react-app)
+* [Vite](https://github.com/vitejs/vite)


Test patch: