Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ci: add Scylla test.py driver subset #943
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
ci: add Scylla test.py driver subset #943
Changes from 1 commit
7c3723429ec16b8ec3ee4File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🌐 Web query:
scylladb-actions get-version v0.4.3 CLI filters flag syntax documentation💡 Result:
The scylladb-actions/get-version tool, including version v0.4.3, utilizes a filter syntax that supports pattern matching and global position selection to filter software versions [1]. Filter Syntax Overview The tool's filter system allows for combining different types of filters using 'and' / 'or' operators [1]. 1. Pattern Filters (Component-Level): These match specific semantic version components (e.g., Major.Minor.Patch) [1]. Regular expressions are commonly used here to match version segments, such as "^[0-9]{4}$.^[0-9]+$.^[0-9]+$" [2][3][4]. 2. Global Position Filters (List-Level): These allow selection of versions based on their position in the sorted list, such as using 'LAST' to get the newest version, or 'LAST-1' to get the second-newest [1][2][3]. CLI Usage The syntax for applying filters in the CLI is:./get-version --source --repo --filters "" [1] Example usage frequently seen in ScyllaDB repositories involves concatenating pattern and position filters:./get-version --source dockerhub-imagetag --repo scylladb/scylla -filters "^[0-9]{4}$.^[0-9]+$.^[0-9]+$ and LAST.1.LAST" [2][3][4] In this example, the filter matches a specific version pattern and selects a version based on its positional index (LAST, 1, LAST) [1][2]. Note that in some implementation contexts, users pipe the output to tr -d '"' to strip quotation marks [2][3][4].
Citations:
🌐 Web query:
GitHub scylladb-actions get-version v0.4.3 command line options single dash filters💡 Result:
In the scylladb-actions/get-version tool, command-line arguments are typically specified using double dashes (e.g., --filters, --source, --repo) [1]. While some real-world usage examples in CI workflows have occasionally used a single dash for the filters flag (e.g., -filters) [2][3][4][5][6], this is a deviation from standard CLI conventions rather than a supported feature for "single dash filters." The official documentation and repository usage demonstrate the use of double dashes for flags [1]. The filters option accepts a specific syntax for semantic version filtering, which can include pattern matching and positional keywords like LAST [1]. If you encounter documentation or scripts referencing -filters, it should be interpreted as the --filters option [1][2]. It is recommended to use the standard double-dash syntax (--filters) to ensure compatibility and adhere to the tool's intended interface [1].
Citations:
🌐 Web query:
site:github.com/scylladb-actions/get-version v0.4.3 "long-flags" "short-flags" "-filter"💡 Result:
There is no widely recognized software documentation or standard library for v0.4.3 that explicitly defines the terms long-flags and short-flags as formal nomenclature in the context of a -filter argument [1]. The terms long flags and short flags are common industry vernacular used to describe command-line interface arguments, where short flags are typically single characters preceded by a single dash (e.g., -f) and long flags are descriptive names preceded by double dashes (e.g., --filter) [1]. The provided search results indicate that the scylladb-actions/get-version tool uses a --filters argument to support complex version matching, but it does not use the specific phrasing long-flags or short-flags in its documentation [1]. If you are encountering these terms in a specific software package or library, it is likely that the author is using these descriptive names to distinguish between flag formats rather than referencing a version-specific feature of v0.4.3.
Citations:
🌐 Web query:
scylladb csharp-driver .github get-version -filters "and LAST"💡 Result:
The latest release version of the ScyllaDB C# Driver as of July 27, 2026, is v3.22.0.2, which was released on December 1, 2025 [1]. You can find this package on NuGet under the name ScyllaDBCSharpDriver [1][2]. To get the version of the driver in your own project, you can typically inspect the assembly version or the package version defined in your project file (e.g.,.csproj) [2]. For further details: - GitHub Repository: https://github.com/scylladb/csharp-driver [1] - Official Documentation: https://csharp-driver.docs.scylladb.com/ [3] - NuGet Gallery: https://www.nuget.org/packages/ScyllaDBCSharpDriver [2]
Citations:
🌐 Web query:
scylladb driver tests get-version -filters LAST.scylla-"💡 Result:
The syntax LAST.scylla-" or more commonly LAST.LAST.LAST-X is used within ScyllaDB's CI/CD automation and helper scripts to dynamically resolve and fetch specific versions of ScyllaDB from container registries (such as Docker Hub) [1][2]. These strings are arguments passed to a utility tool typically called get-version (or a similar version-fetching script like version_fetch.py) [1][2][3]. This tool parses version tags from a repository (e.g., scylladb/scylla) based on defined filters to automate the testing of drivers against various ScyllaDB releases [1][2]. The components of these strings generally follow a pattern based on MAJOR.MINOR.PATCH semantic versioning [4]: 1. LAST.LAST.LAST-X: This refers to the most recent release, where X is an offset to select previous patch or minor versions (e.g., LAST.LAST.LAST-1 selects the prior patch version) [1][2]. 2. LAST.1.LAST or LAST-1.1.LAST: These variations are often used to identify specific Long-Term Support (LTS) release streams by targeting the appropriate MAJOR.MINOR segments [1][2]. These mechanisms ensure that integration tests for ScyllaDB drivers (such as the C#, Go, and C++ drivers) can be automatically configured to run against the latest supported or prior versions without manual hardcoding [1][2][3].
Citations:
🏁 Script executed:
Repository: scylladb/python-driver
Length of output: 3029
🏁 Script executed:
Repository: scylladb/python-driver
Length of output: 1913
🏁 Script executed:
Repository: scylladb/python-driver
Length of output: 1140
Use the documented
get-versionoption spellings.-filtersis not the standard long flag for this CLI; use--filtersconsistently with--source,--repo,--prefix, and--out-no-prefixso DockerHub tag resolution doesn’t fail parsing the command-line contract.🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Second
find_scylla_executablecall can abort before the intended error message.After
pull_scylla_with_ccm,scylla_exe="$(find_scylla_executable "$version")"(line 160) is a plain assignment, not inside a conditional. Underset -e, iffind_scylla_executablestill can't find the binary (returns 1), the script exits immediately here rather than reaching the descriptive"Scylla executable is not available or executable"message on lines 163-166, making CI failures harder to diagnose.🐛 Proposed fix
if ! scylla_exe="$(find_scylla_executable "$version")"; then pull_scylla_with_ccm "$version" - scylla_exe="$(find_scylla_executable "$version")" + scylla_exe="$(find_scylla_executable "$version")" || true fi📝 Committable suggestion
🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.