bitfab-cli 0.2.489 → 0.2.491
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +3 -3
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -29561,7 +29561,7 @@ var getExperiment = {
|
|
|
29561
29561
|
var getGraderVerdicts = {
|
|
29562
29562
|
name: "get_grader_verdicts",
|
|
29563
29563
|
title: "Get Grader Verdicts",
|
|
29564
|
-
description: `Read the INDIVIDUAL verdicts each grader recorded, one row per grader per trace, with the grader's reason, its failure diagnostic, the confidence, and whether the verdict came from a person, a grader Bitfab ran, or an external grader whose verdict was posted from outside Bitfab with save_grader_verdicts. This is the per-grader breakdown that get_trace_verdicts does not show: that tool returns one grader-agnostic verdict per trace, so use it for a dataset's overall pass/fail and use this one to see WHICH check failed and why. Pass traceIds to see every grader's verdict on those traces, graderId to see that grader's most recent verdicts across traces (newest first, use it to diagnose a grader that is misfiring), or both to narrow to one grader on specific traces. Call list_graders first if you need grader ids.`,
|
|
29564
|
+
description: `Read the INDIVIDUAL verdicts each grader recorded, one row per grader per trace, with the grader's reason, its failure diagnostic, the confidence, and whether the verdict came from a person, a grader Bitfab ran, or an external grader whose verdict was posted from outside Bitfab with save_grader_verdicts. A person's verdict for a grader is given in the dashboard, only on a trace that grader has not judged, so it never replaces a grader's own verdict. This is the per-grader breakdown that get_trace_verdicts does not show: that tool returns one grader-agnostic verdict per trace, so use it for a dataset's overall pass/fail and use this one to see WHICH check failed and why. Pass traceIds to see every grader's verdict on those traces, graderId to see that grader's most recent verdicts across traces (newest first, use it to diagnose a grader that is misfiring), or both to narrow to one grader on specific traces. Call list_graders first if you need grader ids.`,
|
|
29565
29565
|
inputSchema: {
|
|
29566
29566
|
traceIds: external_exports.preprocess(parseJsonString, external_exports.array(external_exports.uuid()).min(1).max(GET_GRADER_VERDICTS_MAX_IDS)).optional().describe(`Trace IDs to read grader verdicts for (1-${GET_GRADER_VERDICTS_MAX_IDS}). Omit to read by grader instead.`),
|
|
29567
29567
|
graderId: external_exports.uuid().optional().describe("Restrict to one grader (from list_graders). On its own, returns that grader's most recent verdicts across all traces."),
|
|
@@ -31140,8 +31140,8 @@ var semver2 = __toESM(require_semver2(), 1);
|
|
|
31140
31140
|
// ../bitfab-plugin-lib/dist/bakedSdkVersions.js
|
|
31141
31141
|
var BAKED_SDK_VERSIONS = {
|
|
31142
31142
|
typescript: "0.68.9",
|
|
31143
|
-
python: "0.68.
|
|
31144
|
-
ruby: "0.67.
|
|
31143
|
+
python: "0.68.9",
|
|
31144
|
+
ruby: "0.67.4",
|
|
31145
31145
|
go: "0.67.4"
|
|
31146
31146
|
};
|
|
31147
31147
|
|
package/package.json
CHANGED