Helicone Community Page

Updated last year

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

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"
      }
    }
  ]
h
p
J
6 comments
Okay, so pat has already reported the issue and @Justin & other are working on that fix πŸ˜‰ https://discord.com/channels/1020597994703310878/1121932317347295372/1163386744817864755
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 ... 😦
@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
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 ... πŸ™‚
@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
Sign up and join the conversation on Discord