Skip to content

Error parsing rez-search --before/--after with relative time in bash #2086

@hww-nikhilshankarnoble

Description

@hww-nikhilshankarnoble

Attempting to use the --before/--after command-line flags for rez-search is giving me CLI parsing errors when specifying a relative time instead of an epoch timestamp, when using Bash on Linux (I don't currently have access to a Windows box to test on, apologies).

Environment

  • OS: Tested across Ubuntu 22.04 and Rocky Linux 9.7
  • Shell: bash
  • Rez version: Reproducible with 3.1.1 and 3.3.0
  • Rez python version: 3.10.12 (Ubuntu) and 3.9.25 (Rocky)

To Reproduce

Run the following command in a Bash shell, attempting to search for any packages released in the last day:

$ rez-search "*" --after '-1d'
rez search: error: argument --after: expected one argument  

This behaviour is the same when quoting with double quotes or trying to escape the minus:

 $ rez-search "*" --after "-1d"
rez search: error: argument --after: expected one argument  
 $ rez-search "*" --after \-1d
rez search: error: argument --after: expected one argument  

Using the epoch timestamp instead of a relative time works as expected:

 $ rez-search "*" --after 1773852883
fastapi
numpy

Expected behavior
The packages before/after the relative time being listed.

Actual behavior
A CLI argument parsing error (listed above)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions