-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix trust_remote_code=True for longbench #3361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
99e2780 to
24b19a1
Compare
|
Hi! Thanks for the PR! Just to confirm, the two datasets are equivalent? |
|
They should be equivalent; the number of samples in the |
|
Results from
|
|
Great! which one should i merge before, do you want me to merge #3359 or this one first? |
|
merge this first I think, because this changes the dataset and formatting etc. and #3359 creates groups and increments the version number? Could also merge this one and then I'll pull it into the other PR |
Current longbench dataset (
THUDM/LongBench) needs explicittrust_remote_code=Trueto run, which is no longer supported indatasets>=4.0. Changed dataset toXnhyacinth/LongBench, which has the dataset saved in*.parquet. Part of fixing issue #3171Maybe should also increment version numbers? Keeping this separate from PR #3359 because this is a different feature.