got my first xet error , and it leaks a token (i think?)

#2
by Tonic - opened

image.png

just having fun doing silly things to test it out, let me know if that's a real token btw, probably i should check that out if i'm responsible :-)

Xet Team org

Thanks for reporting the issue! But it's definitely not a token, it's a commit Oid of your repo: https://huggingface.co/datasets/Tonic/Health-Bench-Eval-OSS-2025-07/commit/21e0c0262b362d69cb0e8eb3a54ffe820ac77eae

We'll investigate what happened to your dataset viewer!

изображение.png

I had a similar problem with https://huggingface.co/datasets/nyuuzyou/hailuoai but in my case it was HTTP 401, fixed by switching the dataset between private/public a few hours later

Xet Team org

Thanks for the additional report @nyuuzyou we'll review this as well and follow up here.

Xet Team org

Hey @Tonic and @nyuuzyou we have recently done some updates here, but it was done in an effort to avoid issues between Xet-enabled repos and the dataset viewer, so I'm wondering if we can get a few additional details to investigate. Specifically:

  • When did you encounter the issue?
  • What was the specific URL where you encountered the issue?
  • If you're still seeing this (mostly for @Tonic , I suppose) does the issue go away if you look at this in an incognito browser or do a hard refresh?
  • What browser are you using when you see this?

Thanks again!

@Tonic @nyuuzyou hey there! Just wondering if this is still an issue for y'all - if it is, just see my note above requesting a few more details.

Hi, I haven't encountered this problem anymore. The only thing I can add is that it was a server side issue - the same error on the dataset page was displayed to all users

Sign up or log in to comment