Filter by reset
- Everywhere
192 - Issues
50 - Pull Requests
43 - Comments
99
Introduce sparse checkout instead of using FULL repo for users
Replace inline git reset logic with ensureRepositoryCheckout helper Add sparse checkout config option in .env.example for selective paths Simplify branch checkout and stash handling via unified function Prepare groundwork for sparse checkout to optimize …
Update Semantic Search index automatically
CLT UI cosmetic touches and issues
There are several issues that are not very critical but are great to address when we can: When we land with branch=.. we should reset the query string, because the branch has already switched, and reloading the page will reswitch it again. The "Create PR" …
Update Semantic Search index automatically
subj.
CLT UI cosmetic touches and issues
Improve CLT output with user command
We should improve our CLI action and provide users with a given command that they can run to validate the test locally. In the same output, we should dump information about the script and real command execution.
CLT UI cosmetic touches and issues
Proxy checkers dir inside container
CLT UI cosmetic touches and issues
…"git operation failed": The button becomes invisible when I hover over it: Too much empty space here which makes the prompt's font too small: "your command or question" is confusing. It makes users wonder things like: "Is there a list of supported …
CLT UI cosmetic touches and issues
Refactor: use start-test/poll-test and banch of improvements and fixes
CLT UI cosmetic touches and issues
I've got this test /home/box/clt/ui/workdir/sanikolaev/test/clt-tests/core/search-stats-global-vs-table-consistency.rec on the server and I can't run it via UI. It says "Running test" and never returns any status. Here's what it looks like after running …
CLT UI cosmetic touches and issues
CLT UI cosmetic touches and issues
When an actual output changes after changing the command the expected output becomes empty:
CLT UI cosmetic touches and issues
CLT UI cosmetic touches and issues
Add possibility to pass the directory required to run tests from outside
CLT UI cosmetic touches and issues
CLT UI cosmetic touches and issues
CI: Display CLT Test EDIT link with a given domain as a parameter in action
Now with our UI, we can not just post error tests to comments in pull requests but also provide a link to edit it in the UI. The link looks like this: {UI_HOST}/?test_path=core%2Ftest-auto-schema.rec&branch=master&failed_tests[]=core%2Ftest-auto-schema. …
CLT UI cosmetic touches and issues
Currently, we keep Rust binaries in a repository that is not very efficient. We should think about introducing a CI pipeline that will build it, and as per CLT tool usage, we can just automatically download it when required to the local system and keep …
Do not post any info in case tests passed
Block inside reusable block compilation
Skip adding succeed tests to summary
We should add to summary only those tests that failed same we do in comments
Closer integration with GitHub, so all changes are saved right away in a GitHub repo Support for Docker checkpoints Show progress while a test is running Syntax highlighting Add Docker image name as a comment (like metadata) Editable code blocks …
Description: HTTP requests sent through Buddy without ; echo at the end cause the request to hang indefinitely, and the test does not complete. The query works correctly when executed via MySQL CLI (mysql -h0 -P9306 -e "show version;"). The issue occurs …
bug