Helicone Users user details null error

On users page click on user causes client side error
https://www.helicone.ai/users/32423562352365realUserID

Plain Text

TypeError: Cannot read properties of null (reading 'toString')
    at l (1980-3e81a5f0b132355c.js:1:23266)
    at N ([id]-d691b8924030ce85.js:1:3180)
    at ak (framework-314c182fa7e2bf37.js:9:60903)
    at up (framework-314c182fa7e2bf37.js:9:72785)
    at i (framework-314c182fa7e2bf37.js:9:120317)
    at oD (framework-314c182fa7e2bf37.js:9:99073)
    at framework-314c182fa7e2bf37.js:9:98940
    at oO (framework-314c182fa7e2bf37.js:9:98947)
    at oE (framework-314c182fa7e2bf37.js:9:95699)
    at oP (framework-314c182fa7e2bf37.js:9:96088)

Attachment

14 comments

aayoKho

hey ! glad you're using Helicone.

do you mind DM'ing me some more details? Or potentially adding me to your org so I can take a look?

scott@helicone.ai

aayoKho

would love to know the user's id

UUmut (Hope) YILDIRIM

Hey added you

aayoKho

hey - just got a fix in. will merge it in once it finishes building

UUmut (Hope) YILDIRIM

thanks scott btw does gateway.hconeai.com save responses

aayoKho

yeah it does

UUmut (Hope) YILDIRIM

I cant see them on my requests page and when i enable dedicated domains on gateway fallback, CF return error 522
This one works;

Plain Text

  headers.set(
    "Helicone-Fallbacks",
    JSON.stringify([
      {
        "target-url": "https://api.openai.com",
        headers: {
          Authorization:
            "Bearer sk-asd",
        },
        onCodes: [{ from: 400, to: 500 }],
      },
      {
        "target-url": "https://api.together.xyz",
        headers: {
          Authorization:
            "Bearer asd",
          "Content-Type": "application/json",
        },
        onCodes: [401, 403],
        bodyKeyOverride: {
          model: "mistralai/Mixtral-8x22B-Instruct-v0.1",
        },
      },
    ])

Not this one;

Plain Text

  headers.set(
    "Helicone-Fallbacks",
    JSON.stringify([
      {
        "target-url": "https://oai.hconeai.com",
        headers: {
          Authorization:
            "Bearer sk-asd",
        },
        onCodes: [{ from: 400, to: 500 }],
      },
      {
        "target-url": "https://together.hconeai.com",
        headers: {
          Authorization:
            "Bearer asd",
          "Content-Type": "application/json",
        },
        onCodes: [401, 403],
        bodyKeyOverride: {
          model: "mistralai/Mixtral-8x22B-Instruct-v0.1",
        },
      },
    ])
  );

Return is error code: 522

UUmut (Hope) YILDIRIM

Could you let me know if this is a problem on my end? I would be happy to hop on a call.

UUmut (Hope) YILDIRIM

Attachment

Screenshot_2024-04-17_at_11.23.44_PM.png

UUmut (Hope) YILDIRIM

Attachment

Screenshot_2024-04-18_at_12.18.49_AM.png

CCole

Hi , hope you're doing well 🙂

So, in the example you gave that returned a 522, the target-urls are the helicone cloudflare workers. This will lead to a 522 as the cloudflare workers are not able to call other cloudflare workers.

UUmut (Hope) YILDIRIM

I though custom domains were fine?
https://community.cloudflare.com/t/is-a-worker-allowed-to-make-requests-to-another-worker/194733/7

UUmut (Hope) YILDIRIM

Doing well btw 😄

CCole

interesting, I did not know that. It seems the problem would be that the domain is the same then. Any reason why the fallback url is helicone? Wouldn't the fallback be another provider?

Add a reply

Helicone Community Page

Helicone Users user details null error