Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-5· anthropicHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION [Filters] Backend do not accept conditional groups Describe the issue…

  1. User

    ISSUE DESCRIPTION

    [Filters] Backend do not accept conditional groups

    Describe the issue

    HTTP 400 is returned at a simple conditional group filter query.

    Reproduction

    1. Navigate to the Executions view
    2. Add a new conditional group to the default set of filters
    3. Keep the OR operator
    4. Add a new filer - e.g. labels foo:bar
    5. HTTP 400 response with:

    Invalid query filters: Provided query filters are invalid: Field TIME_RANGE is not supported for resource EXECUTION. Supported fields are QUERY, SCOPE, FLOW_ID, START_DATE, END_DATE, STATE, LABELS, TRIGGER_EXECUTION_ID, CHILD_FILTER, NAMESPACE, KIND, PARENT_ID

    Environment

    • Kestra Version: develop

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /kestra, current file: none) bash-$

  2. Claude Assistant

    Now let me implement the fix in QueryFilterUtils.

  3. Claude Assistant

    Now update rewriteTriggerDateFilters to be recursive:

  4. Claude Assistant

    Now make TimeLineSearch.parseDuration accessible:

  5. Claude Assistant

    Now update the three call sites of mapLeaves:

  6. Claude Assistant

    All changes are complete. Let me do a final verification of the repository state:

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.