helicone/web/services/lib/filters/filter...

At a glance

A community member is facing an issue with the "Invalid operatorundefined" error when using a filter in GraphQL. The error occurs at a specific line of code in the Helicone project. Other community members have reported the issue, and the Helicone team, including Justin, is working on a fix. The community members cannot find a workaround for the bug as they rely on property filtering, and downgrading to an older version is difficult for a managed Helicone setup. One community member suggests exporting the entire dataset and filtering it locally if the dataset is small. Eventually, the Helicone team finds and fixes the bug, and they thank the community members for their patience.

Useful resources

hharryTheharry

Has anyone faced an issue with "Invalid operatorundefined" ?

For example, we use filter in GraphQL:

Plain Text

{
  "limit": 10,
  "offset": 0,
  "filters": [
    {
      "property": {
        "name": "app",
        "value": {
          "equals": "test"
        }
      }
    }
  ]
}

But this returns an error like at the line https://github.com/Helicone/helicone/blob/main/web/services/lib/filters/filters.ts#L31:

Plain Text

  "errors": [
    {
      "message": "Invalid operatorundefined",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "heliconeRequest"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      }
    }
  ]

6 comments

hharryTheharry

This happened since 10th Oct so I guess you might break a backward-compatibility ... https://github.com/Helicone/helicone/commit/9abf1981a8fdddd3c34a55b6b45d7843c70c515c#diff-fffd1f3c8e47da240410b86c661f2f873225040b2ddf9dfef311318ba4d87c58R199

hharryTheharry

Okay, so pat has already reported the issue and @Justin & other are working on that fix 😉 https://discord.com/channels/1020597994703310878/1121932317347295372/1163386744817864755

hharryTheharry

We unfortunatelty cannot do a workaround for this bug as we reply on filtering by property ... is there any way to bypass the current issue? One way is to downgrade to an older version but it's difficult for a managed helicone ... 😦

ppat

@harryTheharry I was also reliant on property filtering, but if your dataset is small, perhaps you can export the entire thing and do the property filtering after the fact. That's essentially what I did

hharryTheharry

thanks for ur feedback @pat , our dataset is not small and we pull all every 30 mins by filtering a property .... I probably need to export all the items then filter by createdAt as justin suggested ... 🙂

JJustin

@harryTheharry and @pat just found the bug! It was a tiny fix, but def was a head scratcher! thanks for your patience while we fixed this issue
https://github.com/Helicone/helicone/pull/949

Add a reply

Helicone Community Page

helicone/web/services/lib/filters/filter...