The dataset viewer is not available for this subset.
Exception: SplitsNotFoundError
Message: The split names could not be parsed from the dataset config.
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 286, in get_dataset_config_info
for split_generator in builder._split_generators(
~~~~~~~~~~~~~~~~~~~~~~~~~^
StreamingDownloadManager(base_path=builder.base_path, download_config=download_config)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/src/libs/libcommon/src/libcommon/packaged_modules.py", line 18, in _refuse_lance
raise NotImplementedError(LANCE_DISABLED_MESSAGE)
NotImplementedError: The Lance format is not supported.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/split_names.py", line 68, in compute_split_names_from_streaming_response
for split in get_dataset_split_names(
~~~~~~~~~~~~~~~~~~~~~~~^
path=dataset,
^^^^^^^^^^^^^
config_name=config,
^^^^^^^^^^^^^^^^^^^
token=hf_token,
^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 340, in get_dataset_split_names
info = get_dataset_config_info(
path,
...<6 lines>...
**config_kwargs,
)
File "/usr/local/lib/python3.14/site-packages/datasets/inspect.py", line 291, in get_dataset_config_info
raise SplitsNotFoundError("The split names could not be parsed from the dataset config.") from err
datasets.inspect.SplitsNotFoundError: The split names could not be parsed from the dataset config.Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
huggingface/transformers issues and pull requests, as a funes memory
Every issue and pull request of huggingface/transformers with activity since 2024-01-01 — opening bodies, comments, reviews, inline review comments and PR diffs — chunked, embedded and written to a Lance table by funes, so the tracker can be searched by meaning and read back thread by thread. Kept fresh every few minutes by the funes-github Space.
Use it
Set funes up for your agent the usual way, once — funes add claude or funes add codex — and keep
your own sessions as its default memory. Then tell the agent this memory exists, either way:
A skill, loaded when the topic comes up:
hf download dacorvo/transformers-gh-memory --repo-type dataset --include 'skills/*' --local-dir ~/.claude # Claude Code hf download dacorvo/transformers-gh-memory --repo-type dataset --include 'skills/*' --local-dir ~/.codex # CodexA paragraph in
CLAUDE.mdorAGENTS.md:dacorvo/transformers-gh-memoryis a funes memory of huggingface/transformers issues and PRs. For questions about transformers issues, PRs, reviews or who said what, pass it as thememoryargument of the funes tools (recall,get,sessions). One session is one thread,gh/huggingface/transformers#<number>.
Then ask in plain words:
- why are the experts sharded on the TP mesh for masked expert parallelism?
- what was decided about byte fallback when loading the SentencePiece backend tokenizer?
- read me the review of PR #48857
(funes itself: curl -fsSL https://huggingface.co/buckets/huggingface/funes/resolve/install.sh | sh)
What is in a thread
One thread is one funes session, gh/huggingface/transformers#<number>. Its turns, in order:
| turn | text | role |
|---|---|---|
| opening | **@login** opened issue/PR #n: title, labels, body |
the author's author_association, lowercased |
| comment | **@login** wrote: body |
idem |
| review | **@login** approved / requested changes / reviewed: body |
idem |
| inline review comment | **@login** commented on \path line n`:` the last 8 lines of the hunk, body |
idem |
| PR diff | gh pr diff n → the diff, capped at 200 KB |
the PR author's |
role is GitHub's relationship to the project — member, collaborator, contributor,
first_time_contributor, none — or bot for automation (github-actions, the Copilot reviewer,
the docs builder). The login stays in the text, so "what did ArthurZucker say about …" works.
harness is github; the repo facet is huggingface/transformers.
What to expect
- Append-only. funes never rewrites. An edited body is a new turn stamped with its edit time; the
earlier text stays and recency ranks the newer one. Deleted comments stay. A lone comment edit does
not move a thread's
updated_at, so it lands at the thread's next activity. - Freshness. A thread updated on GitHub is here within about five minutes of its next activity.
- Diffs are indexed in funes's deferred tier: recall over the discussion is unaffected; they answer "which PR touched this file".
- Secrets. Text is redacted at index time and a fail-closed scanner holds back anything that slips through before it is published.
Provenance
Built by gh_to_funes.py
from the GitHub REST and GraphQL APIs, into funes's
turns-file format, then
funes index and funes push. Embeddings: BAAI/bge-small-en-v1.5. The texts are their authors'
words as published on GitHub, redistributed here for search; the diffs are code from
huggingface/transformers (Apache-2.0). Fork the Space to build the same memory for another project.
| Chunks | 610,247 |
| Embedding model | BAAI/bge-small-en-v1.5 |
| Updated | 2026-09-21 |
- Downloads last month
- 9