chore(deps): Bump datasets from 2.21.0 to 5.0.0 in /services - #126
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [datasets](https://github.com/huggingface/datasets) from 2.21.0 to 5.0.0. - [Release notes](https://github.com/huggingface/datasets/releases) - [Commits](huggingface/datasets@2.21.0...5.0.0) --- updated-dependencies: - dependency-name: datasets dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Owner
|
🔒 Held — not declining. datasets is used only by Revisit when: the anchor_runner DocRED source is reworked to a non-script dataset — bump then. |
letuhao
added a commit
that referenced
this pull request
Aug 11, 2026
…s undo hint is #122's counterexample First invocation ever; no code change needed. Both directions proven, database restored to false. kg_exclude=true -> {chapter_id, kg_exclude: true}, undo_hint carries false kg_exclude=false -> {chapter_id, kg_exclude: false}, undo_hint carries true The undo hint's args are {book_id, chapter_id, kg_exclude} — exactly this tool's own arguments, carrying the PREVIOUS value. Replayable verbatim, which is what undoResult's "argument template" contract actually means. Three data points now: correct here and in #105, broken in #122 and fixed there. My first two calls used `excluded`; the field is `kg_exclude`. Reading the schema first is the stated method for this phase and I guessed anyway — the fifth time in this loop that a guessed argument name cost a call. Not exercised: the retraction half. The description says kg_exclude=true RETRACTS already-extracted facts and passages, and the throwaway chapter has never been extracted, so the flag flipped but nothing was retracted. Said plainly rather than implied by a green result. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Superseded by #200. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps datasets from 2.21.0 to 5.0.0.
Release notes
Sourced from datasets's releases.
... (truncated)
Commits
68ac1a9Release: 5.0.0 (#8239)cfe4492Support composed splits in streaming datasets (#8220)fd67320Keep None as a real null in Json() columns instead of the string "null" (#8231)10cdc81Fix iterable skip over full Arrow blocks (#8236)b7c064dParse agent traces messages for SFT usingteich(#8232)31e92f1fix: embed_external_files=True for mesh support (#8224)d168d5ffeat: add TsFile (Apache IoTDB) packaged builder with per-device wide format ...992f3cffix(map): fix progress bar exceeding total when load_from_cache_file=False (#...8474a91Fix single lance file form pylance 7.0 (#8225)d4284e9feat: add 3D mesh support and MeshFolder builder (#8055)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)