* Fix the Preview Modal , Dom Nesting issue inside a Table
* minor modifications to the PreviewModal and rhe row data to get rid of errorsin the console
* add JSONPATH library to implement the parsing with it instead of loadash get
* Display In Sync Replicas (ISR) by Partition on Topic overview (#2703)
* add unit test
---------
Co-authored-by: Roman Zabaluev <rzabaluev@provectus.com>
* [e2e] Create common method for produce message in TopicMessagesTests
* [e2e]TopicTests.purgeMessagesOfTopics : Purge messages of topics. First fix
* [e2e]TopicTests.purgeMessagesOfTopics : Purge messages of topics. First fix
Co-authored-by: Vlad Senyuta <66071557+VladSenyuta@users.noreply.github.com>
Failover clients for SchemaRegistry, Kafka-connect, KSQL:
1. SchemeRegistry openapi client generation
2. WebClient configuration logic moved to WebClientConfigurator class
3. ReactiveFailover utility implemented
4. Connect, Ksql moved to ReactiveFailover usage
1. Add support for predefined (well-known) protobuf types.
2. `preservingProtoFieldNames` mode is enabled for proto messages formatting to fit proto file's message's field names
3. Invalid oneof-processing logic removed
4. Protobuf -> JsonSchema self-reference issue fixed
5. format added to Timestamp protobuf type
* [e2e] Create common method for produce message in TopicMessagesTests
* [e2e] Create common method for produce message in TopicMessagesTests
* [e2e] Create common method for produce message in TopicMessagesTests
* test commit
* fix BaseTest
* upd global
* upd global
* upd global
* add local browser VM option
* fix TopicsList column header locator
* fix withStartupTimeout()
* Update bug_report.md
Added:
1. Actual result,
2. Suggestions on naming convention
3. CAPSed the system info partially and moved to top. Alternative: use the warning emoji and move outside the commented block
4. Specified few examples of additional context, that might help collecting more info n the bug.
* Update bug_report.md
replaced severity and priority suggestion.
* Update .github/ISSUE_TEMPLATE/bug_report.md
done
Co-authored-by: Roman Zabaluev <rzabaluev@provectus.com>
* Update bug_report.md
- Moved actual and expected result together at the top
- Changed to "Alternative scenarios"
- Changed number 4 in additional context as well
-removed duplication of "Steps to reproduce"
Co-authored-by: Roman Zabaluev <rzabaluev@provectus.com>
* Vite Custom Plugin code initialization , ( not building on js file )
* Fix the lazy loading functionality in vite
* add lazy loading in the Cluster page
* minor comment code cleanup
* Remove un-necessary files for configuration of the vite
* minor naming modifications
* minor code modification to encode a variable in the root
* Upgarde to Vite v4
* Fix warnings
* resolved validateDOMNesting(...) warning also remove act from PreviewModal.spec.tsx
* Revert "resolved validateDOMNesting(...) warning also remove act from PreviewModal.spec.tsx"
This reverts commit f24660918f.
Co-authored-by: davitbejanyan <dbejanyan@provectus.com>
* [e2e] Checking Topics settings to make sure retention.bytes is right according to Max size on disk in GB selected value. Created new class - SettingsPanel and inner class in SettingsPanel. Add new test to Topicstests.
* First Update. Checking Topics settings to make sure retention.bytes is right according to Max size on disk in GB selected value
* Second Update. Checking Topics settings to make sure retention.bytes is right according to Max size on disk in GB selected value
* Second Update. Checking Topics settings to make sure retention.bytes is right according to Max size on disk in GB selected value
* [e2e] Final Fix. add topicSettingsTab.waitUntilScreenReady();
(cherry picked from commit a9d7d6c515)
* [e2e] Update case "Checking the information of used Broker in a cluster"
* [e2e] Update case "Checking the information of used Broker in a cluster"
* [e2e] Update case "Checking the information of used Broker in a cluster"
* [e2e]First Fix Update case "Checking the information of used Broker in a cluster"
* [e2e]Second Fix Update case "Checking the information of used Broker in a cluster"
* [e2e]Third Fix Update case "Checking the information of used Broker in a cluster"
* [e2e]Third Fix Update case "Checking the information of used Broker in a cluster"
Co-authored-by: Vlad Senyuta <66071557+VladSenyuta@users.noreply.github.com>
(cherry picked from commit ca3916aae0)
