When i try to install run-cli i have this error:

error[E0061]: this function takes 2 arguments but 1 argument was supplied
   --> src/sub_commands/test.rs:228:9
    |
228 |         match run_single_test(&args.value_of("number").unwrap().to_string()) {
    |               ^^^^^^^^^^^^^^^----------------------------------------------- an argument of type `bool` is missing
    |
note: function defined here
   --> src/sub_commands/test.rs:95:8
    |
95  | pub fn run_single_test(test_case_name: &String, verbose: bool)
    |        ^^^^^^^^^^^^^^^ -----------------------  -------------
help: provide the argument
    |
228 |         match run_single_test(&args.value_of("number").unwrap().to_string(), /* bool */) {
    |               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For more information about this error, try `rustc --explain E0061`.
error: could not compile `run-cli` due to previous error
error: failed to compile `run-cli v0.9.1 (/home/grillo/repos/bleh/run-cli)`, intermediate artifacts can be found at `/home/grillo/repos/bleh/run-cli/target`

Add support for --number and --verbose arguments to the test subcommand.

Known Issues: the arguments for --number are not necessarily numeric and can be greater than the number of tests. First, it is needed to save the number of tests in a structure and then implement this limit.

I am personally struggling to create a github actions workflow for run-cli because the program is built around user input via stdin. I would like to see more scripting support (passing all inputs needed via command line, environment variables or other methods) in the program to help setup CI applications.

As the title suggests, after running run-cli credentials, the user email and password is stored in plain text at ~/.config/.run-cli/run-cli-credentials.toml, giving attackers potential control over the whole user account.

I suggest either adding a token-based authentication system in the run.codes site (ideally limiting access the same way github or AWS tokens), adding password storing in the same way as in docker login, or support a --credentials option that let users secure their passwords in other places and pass it via command line when needed (of course, ideally in an environment variable, because of commands history file).

[WARNINGS] Solve warnings that appears during compilation

The Warnings

During compilation process, rust compiler generated 2 warnings as follows:

warning: unused variable: `res`
   --> src/run_codes/mod.rs:102:6
    |
102 |     let res = client
    |         ^^^ help: if this is intentional, prefix it with an underscore: `_res`
    |
    = note: `#[warn(unused_variables)]` on by default

warning: associated function `read_credentials_locally` is never used
  --> src/utils/mod.rs:85:9
   |
85 |     pub fn read_credentials_locally(project: Project) -> Option<UserCredentials> {
   |            ^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(dead_code)]` on by default

warning: `run-cli` (bin "run-cli") generated 2 warnings

Sugestion

Erase line 102

let res = client

Add macro to ignore unused function

pub fn read_credentials_locally(project: Project) -> Option<UserCredentials>

[DOCS] Add distribution dependencies to the README.md

The Error

On Fedora 36 (Thirty Six) package openssl-devel is required to compile run-cli from source.

Without it i got the following error:

error: failed to run custom build command for `openssl-sys v0.9.77`

Caused by:
  process didn't exit successfully: `/home/coveiro/Repos/run-cli/target/release/build/openssl-sys-856093e4cb4b382b/build-script-main` (exit status: 101)
  --- stdout
  cargo:rustc-cfg=const_fn
  cargo:rustc-cfg=openssl
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_LIB_DIR
  X86_64_UNKNOWN_LINUX_GNU_OPENSSL_LIB_DIR unset
  ...
  Make sure you also have the development packages of openssl installed.
  For example, `libssl-dev` on Ubuntu or `openssl-devel` on Fedora.
  ...
error: failed to compile `run-cli v0.9.1 (/home/coveiro/Repos/run-cli)`, intermediate artifacts can be found at `/home/coveiro/Repos/run-cli/target`

Suggestion

Add openssl-devel or libssl-dev (openssl developer package) as a dependency on the README.md, warning future users of the requirement.