diff --git a/README.md b/README.md index c75a7bedece9a45625ad713ee652684e96722692..fdf8018ac85bb74dae6eeaa1690c7d744a82967a 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ viewer: false # MiMo-V2.6-RL Code (Harbor) -**Fix a real issue in a real repository.** 2,698 Harbor tasks from the Code domain of Xiaomi's +**Fix a real issue in a real repository.** 2,602 Harbor tasks from the Code domain of Xiaomi's [MiMo-V2.6-RL-oss](https://huggingface.co/datasets/XiaomiMiMo/MiMo-V2.6-RL-oss), the RL environments MiMo-V2.6 was trained on, converted so every one runs as a standard Harbor task. @@ -34,7 +34,7 @@ The agent gets an issue and the repository at its base commit. After it finishes | | | |---|---| -| Tasks | 2,698 | +| Tasks | 2,602 | | Graded by | hidden tests (deterministic) | | Reference step limit | 500 | | Source | [`XiaomiMiMo/MiMo-V2.6-RL-oss`](https://huggingface.co/datasets/XiaomiMiMo/MiMo-V2.6-RL-oss) at `639865fd3374` | diff --git a/data/tasks.jsonl b/data/tasks.jsonl index 81b37b52e5129c8a74dfc662bd08686f4ed12842..a45358d48d58bdcc5034ee4189a7f5badc269ca7 100644 --- a/data/tasks.jsonl +++ b/data/tasks.jsonl @@ -6,7 +6,6 @@ {"task_id": "format-code-task-000008", "source_id": "format-code-task-000008", "domain": "code", "task_path": "tasks/format-code-task-000008", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ad2b230a1c2d0686e12bd1fe3e722a68c66e92309fa8951adeed18c13ce75d87", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the `manimgl` and `manim-render` commands to support opening or revealing rendered output files directly from the CLI. When I run `manimgl path/to/scene.py SceneName --open` or `manimgl path/to/scene.py SceneName -o`, the command should render the scene to a media file just like `--write_file`, and after the movie or final-frame image has been saved it should launch that saved file with the platform's default opener. Passing `--open` by itself should imply file writing; users should not also have to pass `--write_file`.\n\nI also want `manimgl path/to/scene.py SceneName --finder` to imply file writing and then reveal the saved output in the operating system's file browser when rendering completes. If the run saves only the final frame with `--skip_animations`, the image file should be opened or revealed; otherwise the movie file should be opened or revealed. These flags should appear in `manimgl --help` with `-o, --open` described as automatically opening the saved file and `--finder` described as showing the output file in Finder/file browser. A successful render that opens or reveals the output should still exit with code 0."} {"task_id": "format-code-task-000011", "source_id": "format-code-task-000011", "domain": "code", "task_path": "tasks/format-code-task-000011", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c573f9ab59e0f4be186fc0d7cba1d0ad92dfa8e3f49abec863c2562f71286767", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## 1277 and 338 directories are placeholders — please fill them in\n\nI was browsing this repo looking for the Go solutions to a couple of LeetCode problems and noticed that **1277. Count Square Submatrices with All Ones** and **338. Counting Bits** both appear to be unfinished placeholders.\n\nIn `leetcode/1201-1300/1277.Count-Square-Submatrices-with-All-Ones/` and `leetcode/301-400/0338.Counting-Bits/`, the contents look like this:\n\n- `README.md` has the `> [!WARNING|style:flat]` banner saying *\"This question is temporarily unanswered if you have good ideas. Welcome to Create Pull Request PR\"*.\n- The `## Description` section is mostly empty, and the only example given is:\n ```\n Input: a = \"11\", b = \"1\"\n Output: \"100\"\n ```\n which clearly belongs to some other problem (looks like a string-addition / add-binary kind of question), not to 1277 or 338.\n- `Solution.go` only contains the dummy stub:\n ```go\n package Solution\n\n func Solution(x bool) bool {\n return x\n }\n ```\n The `bool` signature obviously doesn't match either problem — 1277 takes a 2D matrix and returns a count, 338 takes an integer `n` and returns a slice.\n\nCould someone fill these two in properly? Specifically, for each of the two problems:\n\n- update `README.md` so the description and example(s) actually match what LeetCode is asking for,\n- and replace the stub `Solution.go` with a real implementation using a function signature that fits the problem's input/output.\n\nHappy to review if someone picks them up. Thanks!"} {"task_id": "format-code-task-000013", "source_id": "format-code-task-000013", "domain": "code", "task_path": "tasks/format-code-task-000013", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:30dfff7f5ffeaab1b72d1b5e38a530cb30f216690d67945084c809e26518d49d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nThe small `lib/lru` package is now being used by callers that need to inspect and manage a cache without reaching into its implementation. Extend its public API while fixing the byte-accounting bug when an existing key is updated.\n\nAdd these methods to `*Cache`: `Bytes() int64`, `Peek(key string) (Value, bool)`, `Keys() []string`, `Remove(key string) (Value, bool)`, `Clear()`, `Resize(maxBytes int64)`, `Stats()` returning a struct value with exported `Hits` and `Misses` fields of type `uint64`, and `ResetStats()`.\n\nThe observable contract is:\n\n- An entry consumes `len(key) + value.Len()` bytes. `Bytes` reports the sum for entries currently retained. Replacing an existing key must account for both larger and smaller values, make that key most recently used, and must not itself invoke `OnEvicted`.\n- A positive byte limit is enforced after every add or replacement by evicting least-recently-used entries until the cache fits. If one entry is larger than the limit, it is added and then evicted through the normal callback path. A limit of zero continues to mean unlimited capacity.\n- `Get` keeps its current lookup and recency behavior and increments exactly one counter: `Hits` for a found key or `Misses` for an absent key. `Peek` returns the same value/found pair without changing recency or either counter. `Keys` returns the current keys from most to least recently used and does not change recency or counters. `ResetStats` zeros both counters without changing entries.\n- `Remove` returns the removed value and `true`, updates byte usage, and invokes `OnEvicted` once when the key exists. For a missing key it returns the zero `Value` and `false` without a callback.\n- `Clear` removes every entry, leaves both `Len()` and `Bytes()` at zero, and invokes `OnEvicted` once per entry in least-to-most-recently-used order.\n- `Resize` changes the byte limit immediately. A positive limit evicts least-recently-used entries, using `OnEvicted`, until the cache fits; resizing to zero disables the limit without discarding retained entries.\n\nKeep the existing `New`, `Add`, `Get`, `RemoveOldest`, `Len`, `Value`, and `OnEvicted` surfaces compatible. In particular, `Get` and replacement still promote an entry, `RemoveOldest` removes the least-recently-used entry and invokes the callback, and existing zero-limit callers remain unlimited. The cache may remain documented as unsafe for concurrent access."} -{"task_id": "format-code-task-000014", "source_id": "format-code-task-000014", "domain": "code", "task_path": "tasks/format-code-task-000014", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2c7c021648118dd49b4be28cd89fd85d6e510e31a6a95588847e3959b64fe03f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the `github.com/8treenet/freedom/infra/kafka` package to provide a stateful Kafka producer API for Freedom applications. The entry point should be `kafka.GetProducer() kafka.Producer`, where `Producer` exposes `Start(addrs []string, config *sarama.Config)`, `NewMsg(topic string, content []byte) *kafka.Msg`, and `Restart() error`; the concrete `*kafka.ProducerImpl` should also support `Close() error` for lifecycle cleanup.\n\nCalling `Start([]string{\"127.0.0.1:9092\"}, cfg)` should remember the broker addresses and Sarama config for the producer lifecycle, and it should force `cfg.Producer.Return.Errors` and `cfg.Producer.Return.Successes` to `true` so synchronous sends can report their result. After the Freedom application boots with configured broker addresses, publishing `kafka.GetProducer().NewMsg(\"orders\", []byte(\"paid\")).SetMessageKey(\"order-1\").SetHeader(map[string]interface{}{\"x-request-id\":\"r1\", \"attempt\": 2}).Publish()` should send one Sarama producer message to topic `orders`, with value `paid`, key `order-1`, and headers `x-request-id: r1` and `attempt: 2`. If no message key is set, `Publish` should generate a non-empty uppercase UUID-style key with dashes removed before sending.\n\n`Msg.SetHeader` should be chainable and should merge additional header maps into any existing headers. `Msg.GetHeader`, `Msg.SetMessageKey`, and `Msg.GetMessageKey` should expose the current message headers and key consistently before publish. If `Publish` is called before the producer has an initialized Sarama sync producer, it should return an error equivalent to `producer is not initialized` instead of panicking.\n\nI also need producer middleware support through `kafka.InstallMiddleware(...kafka.ProducerHandler)`, where `ProducerHandler` is `func(*kafka.Msg)`. Installed handlers should run in order when `Msg.Publish` calls `Msg.Next`; a handler can call `Next` to continue, call `Stop` to prevent the send, and inspect `IsStopped` or `GetExecution` for message state. `Restart()` should close the current producer connection and then dial again using the stored addresses and config, and `Close()` should be a no-op when no producer connection is active."} {"task_id": "format-code-task-000016", "source_id": "format-code-task-000016", "domain": "code", "task_path": "tasks/format-code-task-000016", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:727b2208406052c4c5d86492acdaed7d5540b90633f2e22197e509c5b07ccac5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Sync IDA Pro type definitions across collaborating analysts\n\nWe're using Polichombr to collaborate on reversing a sample with two\nother analysts. The current server-side IDA actions cover most of what\nwe need — global names, comments, and structs all sync between our IDA\ninstances through the API — but there's one IDA action that doesn't get\nshared: **type definitions** (the ones you set by hitting `Y` on a\nvariable, function, or address in IDA Pro).\n\n### What we'd like to do\n\nIn IDA, I'll often refine a function prototype on a `sub_xxxxxx`, e.g.\nturn the default `int __cdecl sub_401000(int, int)` into something\nmeaningful like `BOOL __stdcall ParseConfigBlob(char *blob, size_t\nlen)`. Then I want my teammates to pick that up automatically the next\ntime their plugin pulls from the server, the same way they pick up the\nnames and comments I made.\n\nRight now, there's no way to do this through Polichombr. Names get\npushed and pulled fine, structs get pushed and pulled fine, but the\ntype info I set with `Y` just stays local in my `.idb` and the rest of\nthe team has to re-discover it independently. For functions with\nnon-trivial prototypes (lots of pointers, callbacks, custom typedefs)\nthis ends up being a real source of duplicated work.\n\n### What we'd expect\n\nIdeally the server should treat applied type definitions as just\nanother kind of IDA action, alongside names / comments / structs:\n\n- the plugin should be able to push a type definition for a given\n sample at a given address,\n- and a teammate's plugin should be able to query, for a given sample,\n the type definitions that have been recorded — with the same kind of\n filtering you already support for names and comments (by address, or\n only the ones added after a given timestamp, so we don't keep\n re-pulling the whole history on every sync).\n\nWould it be possible to add this? Happy to test against any branch.\n\n(For API shape, mirroring the existing `/samples//names/` style would make sense — e.g. a `types`-flavored endpoint that accepts an `address` + `typedef` payload on push and returns the recorded `typedefs` on pull.)"} {"task_id": "format-code-task-000018", "source_id": "format-code-task-000018", "domain": "code", "task_path": "tasks/format-code-task-000018", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:647de7572a687a0cf76e10a411fba517b6e3f0f75850ad1c1989a0df08658531", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Persist sublattice metadata atomically and track the root dispatch\n\nWhen the dispatcher runs a workflow that contains sublattices, each sublattice is\nitself dispatched and gets its own lattice record in the results database. Two\nthings are currently awkward about how those records are created.\n\nFirst, the database column that links a sublattice's lattice record back to the\nparent electron that spawned it (`electron_id`) is only filled in *after* the\nsublattice has already been written to the database. There is a window during\nwhich a sublattice record exists with no link to its parent, so an interruption\ncan leave it orphaned. We want the parent electron id to be written in the *same*\ninsertion that creates the lattice record, not in a later update.\n\nSecond, we are about to need a way to identify, for any (sub)lattice in a\nhierarchy, the dispatch id of the top-level (\"root\") workflow that ultimately\nkicked everything off. A nested sublattice three levels deep should still be able\nto report the dispatch id of the original top-level dispatch.\n\nPlease make the following behavior available.\n\n## `root_dispatch_id` on the result object\n\nThe result object should expose a read-only `root_dispatch_id`. For a result\nobject that represents a top-level dispatch, this equals its own dispatch id. A\nresult object constructed for a given dispatch id reports that same id as its\nroot dispatch id until it is told otherwise (see the factory below).\n\n## Persisting a parent electron id atomically\n\nPersisting a result object should optionally accept the database id of the parent\nelectron that spawned this workflow. When provided, that id must be stored on the\nlattice record in the very same transaction that first creates the lattice\nrecord — not written by a subsequent update. When it is not provided, the\nlattice record's `electron_id` stays null. Persisting a top-level workflow must\ncontinue to behave exactly as before (its `electron_id` is null).\n\n## A factory for building a result object from a serialized lattice\n\nAdd a convenience factory, importable as\n`covalent._results_manager.result.initialize_result_object`, that constructs and\npersists a result object from a JSON-serialized lattice. It takes the JSON\nlattice and, optionally, a parent result object and a parent electron id:\n\n```\ninitialize_result_object(json_lattice, parent_result_object=None, parent_electron_id=None)\n```\n\nIt must:\n\n- deserialize the lattice and assign the new result object a freshly generated,\n unique dispatch id (two calls never collide);\n- initialize the result object's nodes and persist it before returning, passing\n along the parent electron id so it lands atomically on the lattice record as\n described above;\n- when a parent result object is supplied (i.e. this lattice is a sublattice),\n make the new result object inherit the parent's `root_dispatch_id` rather than\n using its own dispatch id;\n- return the fully constructed result object.\n\nThe returned result object's own dispatch id must still be distinct from its\nparent's.\n"} {"task_id": "format-code-task-000019", "source_id": "format-code-task-000019", "domain": "code", "task_path": "tasks/format-code-task-000019", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ca7ef5eafe3ec58c8a5287ac4a3b92a297f3dae36a0c0bd615df3f4e7d357b35", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Bulk-delete dispatches by status filter\n\nRight now the dispatch-management backend can only soft-delete dispatches one at\na time, by passing an explicit list of dispatch ids. The UI needs a \"delete all\"\ncapability so users can clear out every dispatch that matches whatever they are\ncurrently looking at — i.e. the active status filter plus the search box — in a\nsingle request.\n\nAdd a bulk deletion operation to the dispatch summary data-access layer (the\nsame component that already handles per-id deletion and the dispatch listing).\nIt should accept a request object `DeleteAllDispatchesRequest` with two optional\nfields:\n\n- `status_filter`: a dispatch status enum value, defaulting to a new `ALL`\n selector that means \"every status\".\n- `search_string`: a string, defaulting to `\"\"`.\n\nExpose the behavior as a `delete_all_dispatches` method that takes such a request\nand returns the same response shape used by the existing per-id delete\n(`success_items`, `failure_items`, `message`).\n\nBehavior:\n\n- Selection. Only currently-active dispatches are eligible. A dispatch is\n selected when its status matches the filter **and** the search string is a\n case-insensitive substring of either its name or its dispatch id. An empty\n search string matches everything.\n- Status filter semantics:\n - `ALL` selects dispatches in any status.\n - `COMPLETED` is a group selector: it selects dispatches that are `COMPLETED`\n as well as those in the post-processing states `POSTPROCESSING`,\n `POSTPROCESSING_FAILED`, and `PENDING_POSTPROCESSING`.\n - Any other status value selects only dispatches in exactly that status.\n- Deletion is a soft delete, consistent with the existing per-id delete: each\n selected dispatch and its electrons are marked inactive. Dispatches that are\n already inactive are never re-selected or reported.\n- Response. `success_items` contains the dispatch ids (as UUIDs) that were\n deleted; order is not significant. When at least one dispatch was deleted the\n `message` is `\"Dispatch(es) have been deleted successfully!\"`. When nothing\n matched, `success_items` is empty and the `message` is\n `\"No dispatches were deleted\"`.\n\nThe existing per-id delete operation must keep working unchanged.\n"} @@ -85,7 +84,6 @@ {"task_id": "format-code-task-000102", "source_id": "format-code-task-000102", "domain": "code", "task_path": "tasks/format-code-task-000102", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:aa9c965030b8c71db6722d38668ecf48e6f58b73da71e771595087bb89df5977", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nValidate email address format when using automatic IAM authentication\nWhen adding IAM database users to either MySQL or Postgres the user or service account username is formatted in a certain way that differs across database engine types.\n\nThis is not necessarily trivial to users when using the connectors, we should try validating and formatting the IAM database usernames within the connectors to remove this burden on users.\n\n**Postgres**: Removes `.gserviceaccount.com` domain suffix if it exists.\n**MySQL**: Removes everything after and including the `@` sign. (`test-user@gmail.com` -> `test-user`)\n\nShould already have `databaseVersion` from the API request to https://cloud.google.com/sql/docs/mysql/admin-api/rest/v1beta4/connect/get"} {"task_id": "format-code-task-000103", "source_id": "format-code-task-000103", "domain": "code", "task_path": "tasks/format-code-task-000103", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3cf0610cd970e677b62836aa3112c1b21b2f66d50d2d7eb8ee7e99a1945afd44", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `FetchServiceImageMetaData` on `ConfigAgent` is a pure passthrough — remove it and call dbdaemon directly\n\nLooking at how `isImageSeeded` (in the instance controller) gets the service image metadata today, it goes through `ConfigAgent`:\n\n```\nisImageSeeded\n -> ConfigAgent client.FetchServiceImageMetaData\n -> dbdaemon client.FetchServiceImageMetaData // actually does the work\n```\n\nBut if you check the `ConfigAgent` server implementation of `FetchServiceImageMetaData`, it doesn't do anything meaningful: it just dials dbdaemon, forwards the request, and repacks the response field-for-field into the equivalent `ConfigAgent` proto. No additional logic, no enrichment, no decision-making — purely a wrapper.\n\nThis forces us to maintain a redundant set of `FetchServiceImageMetaDataRequest` / `FetchServiceImageMetaDataResponse` messages on the `ConfigAgent` proto that mirror the dbdaemon ones one-to-one, plus an extra network hop and an extra RPC surface to keep in sync. The `ConfigAgent` is supposed to host orchestration / business logic that sits above raw dbdaemon calls; a thin forwarder like this doesn't belong there.\n\n`isImageSeeded` is currently the only caller of the `ConfigAgent` version, and the instance controller already has a `DatabaseClientFactory` available for talking to dbdaemon directly. So the `ConfigAgent` layer here isn't even buying us a stable abstraction for multiple callers — it's dead weight on a single call site.\n\nI'd like to remove `FetchServiceImageMetaData` from the `ConfigAgent` surface entirely and have `isImageSeeded` talk to dbdaemon directly via the database client. The behavior observed by the controller should be identical (same metadata, same `SeededImage` interpretation), it's just one less hop and one less proto pair to maintain."} {"task_id": "format-code-task-000104", "source_id": "format-code-task-000104", "domain": "code", "task_path": "tasks/format-code-task-000104", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3d21b6c02d2419d16a46ca08411ad2ebe4645e4e07e1d1f8093dc12590b71ba8", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Object properties (Content-Type, Cache-Control, custom metadata, ...) are lost after editing a file through gcsfuse\n\nI've been using gcsfuse to mount a bucket where the objects already have meaningful properties set on them — things like `Content-Type`, `Cache-Control`, `Content-Encoding`, plus a few custom metadata entries we use for tracking.\n\n### What I'm seeing\n\n1. Upload an object to the bucket with properties set (via the console / gsutil / API). For example a `.html` file with `Content-Type: text/html`, `Cache-Control: public, max-age=3600`, and a custom metadata pair like `owner=alice`.\n2. Mount the bucket with gcsfuse and edit that file through the mountpoint (any modification — append, rewrite, whatever ends up syncing a new generation).\n3. Go look at the object again in the GCS console.\n\nAfter step 3, the only metadata still present is the `gcsfuse_mtime` key that gcsfuse itself writes. `Content-Type` has reverted to the default, `Cache-Control` is gone, and my custom metadata entries are gone too.\n\n### What I expected\n\nEditing a file through the mount shouldn't silently wipe out the object's existing properties. The new generation should carry over whatever was set on the previous generation; gcsfuse is the one writing the new version, so it owns preserving that state. Only the mtime is something gcsfuse legitimately needs to update on its own.\n\nThis affects both flows that produce a new generation — full rewrites of small/changed files, and the compose-based \"append\" optimization for larger files. In both cases the resulting object comes back stripped.\n\nCould the syncer be fixed so that the properties on the source object are retained on the new generation it writes?"} -{"task_id": "format-code-task-000105", "source_id": "format-code-task-000105", "domain": "code", "task_path": "tasks/format-code-task-000105", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:13a78ffaf2a5084faeac5b58b0c54823c7f97427724b7b44f73a00b2c5f3937a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nCopying symlink from previous stage fails instead of overwriting\n**Actual behavior**\n`COPY --from=0 X Y` where X is a symlink from stage 0 and Y is an pre-existing symlink in the current stage fails with \"file exists\".\n\n**Expected behavior**\n`COPY --from=0 X Y` where X is a symlink from stage 0 and Y is a pre-existing symlink in the current stage should overwrite Y with X as it would if neither were symlinks.\n\n**To Reproduce**\n\n```bash\ndocker run --rm -v $PWD:/workspace:ro gcr.io/kaniko-project/executor:v0.6.0 --no-push\n```\nwith the following Dockerfile:\n```dockerfile\nFROM python:slim\n\nFROM python:slim\nCOPY --from=0 /usr/local/lib/libpython3.7m.so /usr/local/lib/libpython3.7m.so\n```\n\nAlthough this is a bit contrived, we had a Dockerfile which was building into /usr/local/lib and then copying that into the final stage which seems like a legitimate use-case."} {"task_id": "format-code-task-000106", "source_id": "format-code-task-000106", "domain": "code", "task_path": "tasks/format-code-task-000106", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:424a976430b4f9d39e3b298e967a7d45728ebecefb9feda4df5d392c9b0ec6d5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI have a custom artifact where the files Skaffold should watch come from our own build tooling, so keeping `dependencies.paths` updated by hand doesn’t really work. Could Skaffold run a script/command for that artifact and use the file list it returns as the dependencies for watching and rebuilds? Ideally it would give a clear error if the command fails or prints something Skaffold can’t understand.\n\nExpected outcomes:\n- Custom artifact configuration supports `dependencies.command`, exposed through `CustomDependencies.Command`, as an alternative dependency source for determining the files used by watching and rebuild decisions.\n- When `dependencies.command` is configured, Skaffold runs that command during custom artifact dependency resolution and uses its output as the dependency list.\n- The command output must be a valid JSON array of strings; invalid JSON or JSON with a different shape should fail dependency resolution with a clear error.\n- If the dependency command exits unsuccessfully, dependency resolution should fail with an error that makes the failing command context clear.\n- `dependencies.ignore` remains valid with `dependencies.paths`, but is invalid when combined with `dependencies.command`.\n- The public schema and custom builder documentation describe the new `dependencies.command` option and its JSON-array output contract.\n\nImplementation notes:\n- The exact execution helper, parsing location, validation organization, and internal data flow are up to the implementer.\n- Preserve existing dependency behavior for path-based and Dockerfile-based custom artifacts.\n- Error text does not need to match any particular sentence exactly, but it should be actionable enough to distinguish command execution failures from malformed command output."} {"task_id": "format-code-task-000107", "source_id": "format-code-task-000107", "domain": "code", "task_path": "tasks/format-code-task-000107", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:76b0561c369f9d422e64f811221b5c0629a315a19cbe0c7fade9d24f76b43ad7", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n[Custom builder] $IMAGES is always a single image\nWe currently pass the build script the `IMAGES` env variable. This variable contains the list of images to build. However, this variable always contains a single tag.\n\nI think we should deprecate this value and use `IMAGE` instead."} {"task_id": "format-code-task-000108", "source_id": "format-code-task-000108", "domain": "code", "task_path": "tasks/format-code-task-000108", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:dbc61e843ff7991f9ad1d6d413302321c316ccf058eb2f2606201856592b5bf7", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nHandle minikube exit code 89\nMinikube has well-defined exit codes, and Skaffold has special handling for turning minikube exit codes into actionable errors. This code needs to be updated as it's not handling minikube exit code 89:\n\n```\ninvalid skaffold config: getting minikube env: running [/Users/bdealwis/installs/google-cloud-sdk/bin/minikube docker-env --shell none -p minikube --user=skaffold]\n - stdout: \"false exit code 89\\n\"\n - stderr: \"\"\n - cause: exit status 89\n```\n\nBasically minikube is stopped.\n\n- platform: macOS 12.3.1 on arm64\n- `skaffold version`: v1.37.1 (installed via gcloud)\n- `minikube version`: v1.25.2 (installed via gcloud)"} @@ -100,13 +98,11 @@ {"task_id": "format-code-task-000117", "source_id": "format-code-task-000117", "domain": "code", "task_path": "tasks/format-code-task-000117", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d6a7ba84dd446af3fd649ac0c18a22042e5588e44e847d32062c5211cecd3cb7", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Manage custom nameservers for a registered DNS domain\n\nOur users register DNS domains through IBM Cloud (SoftLayer) and frequently need to point a\nregistered domain at a custom set of nameservers from Terraform. Today the provider has no way to\ndiscover a domain registration or to manage its nameservers. Add that capability.\n\n## Data source: `ibm_dns_domain_registration`\n\nLooks up a domain registration by its name.\n\n- Input argument `name` (string, **required**): the registered domain name to look up.\n- Exported attribute `name_servers` (**computed**): the list of nameserver hostnames currently\n configured on the registration, as strings.\n\n## Resource: `ibm_dns_domain_registration_nameservers`\n\nManages the custom nameservers of an existing domain registration.\n\n- Argument `dns_registration_id` (string, **required**): the identifier of the domain registration\n to manage.\n- Argument `name_servers` (**required**): the desired collection of nameserver hostnames (strings)\n the registration should use.\n- Exported attribute `original_name_servers` (**computed**): the nameservers that were present\n before this resource took over management, so they can be restored later.\n\n## Nameserver validation\n\nEvery value supplied in `name_servers` must be a syntactically valid DNS hostname. Validation must\nhappen during configuration validation (i.e. before any API call is made), so that an invalid\nvalue causes a validation error rather than being sent to the backend. A value is valid only if all\nof the following hold:\n\n- it is non-empty and at most 253 characters long;\n- it consists of dot-separated labels and contains at least one dot (at least two labels);\n- every label is between 1 and 63 characters long;\n- every label contains only ASCII letters, digits, and hyphens; and\n- no label begins or ends with a hyphen.\n\nAny value that violates one or more of these rules must produce a validation error for the\n`name_servers` argument; values that satisfy all of them must validate cleanly.\n\nThe provider must continue to pass its internal schema validation with these additions in place.\n"} {"task_id": "format-code-task-000118", "source_id": "format-code-task-000118", "domain": "code", "task_path": "tasks/format-code-task-000118", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:075454795230273f1e5ded54cc2f12c32373e2ca661001466624171472cb2a33", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nIs there a way to assign IAM policy templates to target accounts using the IBM provider? I've got policy templates set up and I need to roll them out to specific accounts via Terraform, but I can't find a resource for it. Ideally I'd be able to specify which template version goes to which account and then reference back the assignment details (like the account ID, when it was created, and the status of what got created) in my outputs. It'd also be nice if I could point acceptance tests at a target account through an env var.\n\n# Expected outcomes\n\n- Terraform resource support:\n - Terraform configurations can declare an `ibm_iam_policy_assignment` managed resource without the provider rejecting the resource type as unsupported.\n - The resource lets users assign an IAM policy template/version to a target account using Terraform configuration.\n\n- Resource input validation:\n - `version` is a required string input.\n - `target` is a required map input for the assignment target.\n - `templates` is required and accepts exactly one item; that item requires `id` and `version`.\n - `options` is required and accepts exactly one item; its nested `root` block is required and includes a required `requester_id`.\n - Missing required inputs, empty required blocks, or more than one `templates`/`options` item are rejected during Terraform validation or planning.\n - `accept_language` is optional and defaults to `default` when omitted.\n\n- Resource state and outputs:\n - After a successful apply/read, `ibm_iam_policy_assignment` exposes assignment metadata that can be referenced in Terraform outputs, including `account_id`, `href`, `created_at`, `created_by_id`, `last_modified_at`, and `last_modified_by_id`.\n - The resource also exposes a computed `resources` list describing created assignment resources, including each item’s `target` and nested policy result information such as the created policy ID, status, and any error message details.\n\n- Acceptance-test configuration:\n - Acceptance-test setup can read a target account from the `IBM_POLICY_ASSIGNMENT_TARGET_ACCOUNT_ID` environment variable.\n - When that environment variable is not set, the acceptance-test setup emits an informational message telling users to set it for `ibm_iam_policy_assignment` tests.\n\n# Implementation notes\n\n- Follow the provider’s existing conventions for Terraform managed resources, schema validation, state population, import/read/delete behavior, diagnostics, and acceptance-test configuration.\n- The concrete internal structure, helper functions, mapping code, and validation placement are up to the implementation as long as the externally observable Terraform behavior above is satisfied.\n- Tests should validate behavior through Terraform configuration/schema outcomes, resource state, diagnostics, and acceptance-test setup behavior rather than relying on private helper names or internal call paths."} {"task_id": "format-code-task-000119", "source_id": "format-code-task-000119", "domain": "code", "task_path": "tasks/format-code-task-000119", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:961be4ce2148b11411002c0386ab3679bcbdeba8126f6f5b7d63d79ae77f4713", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Missing wrapper for `TNoOp` in `lale.lib.autoai_libs`\n\nI'm building pipelines that use the schema-enhanced wrappers under `lale.lib.autoai_libs`. The module already exposes wrappers for the whole family of feature-transform / feature-selection operators that live in `autoai_libs.cognito.transforms.transform_utils` — `TA1`, `TA2`, `TB1`, `TB2`, `TAM`, `TGen`, `FS1`, `FS2` are all there.\n\nHowever, the `TNoOp` operator from that same module isn't exposed:\n\n```python\nfrom lale.lib.autoai_libs import TA1, TA2, TNoOp # TNoOp import fails\n```\n\nThe upstream `autoai_libs.cognito.transforms.transform_utils.TNoOp` is a transformer that passes data through unchanged, which is genuinely useful when composing pipelines (e.g. as a placeholder branch, or as a baseline to compare other feature-transform branches against). Today the only way to use it from a Lale pipeline is to grab the raw `autoai_libs` class, which means I lose the schema-validation / hyperparameter-search story that every other wrapper in this module gives me.\n\nCould you add a Lale-wrapped `TNoOp` alongside its siblings so it can be imported from `lale.lib.autoai_libs` and dropped into a pipeline the same way the other `T*` / `FS*` wrappers can?"} -{"task_id": "format-code-task-000121", "source_id": "format-code-task-000121", "domain": "code", "task_path": "tasks/format-code-task-000121", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:85e99dbe4a8e4136fd93050e6c3a18b1decd7806bf1c55bec1d73152919e5ea8", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI'm seeing a weird imbalance with Sarama's round-robin consumer group balancing: if I have several topics with only one or a few partitions each, and the same consumers subscribe to all of them, the first partitions keep landing on the same consumer while others sit idle. Is the round-robin strategy supposed to spread partitions across topics too? It would be great if those topic partitions were distributed more evenly across the group instead of restarting the rotation for each topic.\n\n# Expected outcomes\n\n- Round-robin planning through `BalanceStrategyRoundRobin.Plan(...)` should distribute partitions across topics as part of one continuous round-robin assignment, rather than starting the member rotation over independently for each topic.\n- When multiple members subscribe to the same small-partition topics, partitions from different topics should be spread across the eligible members as evenly as the round-robin sequence allows.\n- When members have different topic subscriptions, `BalanceStrategyRoundRobin.Plan(...)` should still keep the round-robin progression across topic partitions and assign each partition to an eligible subscribed member, skipping members that are not subscribed to that partition’s topic.\n\n# Implementation notes\n\n- Preserve the existing public strategy surface and observable behavior outside the round-robin assignment semantics described above.\n- The concrete data structures, helper functions, and exact location of the assignment logic are implementation choices, as long as the public round-robin plan results match the expected behavior."} {"task_id": "format-code-task-000122", "source_id": "format-code-task-000122", "domain": "code", "task_path": "tasks/format-code-task-000122", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2393a19996106f2a17fb6507e47bfcf3964e79ee275bc2bdf4333628c3e57799", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI'm hitting a circular import the moment I try to use anything from `idaes.core.components` on its own — importing a Component should not require the generic property package dependency chain to be pulled in first. I shouldn't have to drag in the whole generic property package just to define a component. It would be great if `idaes.core.components` could stand on its own while still supporting parameter values populated from component configuration data.\n\n# Expected outcomes\n\n- `idaes.core.components` can be imported and used independently without depending on the generic property-package utility path that participated in the circular import.\n- A core-level public utility is available as `idaes.core.util.misc.set_param_from_config(block, parameter_name, config=None, index=None)` for setting a parameter-like Pyomo object on a block from parameter data stored on a configuration block.\n- The parameter-population behavior preserves the existing user-facing semantics for scalar parameter data, unit-aware tuple data, explicit versus default configuration blocks, indexed parameter entries, and clear errors for common misuse such as missing configuration, invalid configuration objects, missing target parameters, or missing parameter-data entries.\n\n# Implementation notes\n\n- Keep the dependency direction such that core component definitions do not need to import generic property-model modules.\n- The exact internal organization, helper boundaries, and validation placement are up to the implementer, as long as the public behavior above is preserved.\n- Prefer behavior-preserving changes over broad rewrites of property models or component APIs."} {"task_id": "format-code-task-000123", "source_id": "format-code-task-000123", "domain": "code", "task_path": "tasks/format-code-task-000123", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:9ae0bb5555a3067599469c375a6bccbb8820c2c2e709b99af118ad56c4e7177f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Updating a formatted field — the new value can't be found by `filterByText` over all fields\n\nI have an `igDataSource` (used by igGrid) where one of the schema fields has a `formatter` function set up — in my case it's a number column that gets formatted into a currency string for display.\n\nRoughly the setup looks like this:\n\n```js\nvar ds = new $.ig.DataSource({\n dataSource: products,\n schema: {\n fields: [\n { name: \"ProductID\", type: \"number\" },\n { name: \"Name\", type: \"string\" },\n {\n name: \"Price\",\n type: \"number\",\n formatter: function (val) { return \"$\" + val.toFixed(2); }\n }\n ]\n }\n});\nds.dataBind();\n```\n\nWhen the data is first loaded, `filterByText` over all fields works as expected — searching for the formatted string of the `Price` column (e.g. `\"$19.99\"`) matches the row that has `Price: 19.99`.\n\nThe problem shows up after I edit a formatted field. If I call `updateRow` to change `Price` on some row from `19.99` to `42.50` and commit the transaction, then call `filterByText(\"$42.50\")` over all fields, **the updated row is not returned**. The old value still matches (until I commit), and the new formatted value matches nothing — even though the underlying data has clearly been updated (I can see the new value in the grid, and filtering on the raw `Price` field directly works fine).\n\nSo `filterByText` across all fields seems to be searching against a stale formatted representation of the rows for any field that has a `formatter` — initial bind is fine, but after a commit on an updated row the formatted view for that row is out of sync with the actual data.\n\nCould `filterByText` over all fields stay consistent with the current state of the data source after edits on formatted columns? Right now the only workaround I have is to re-bind the data source after every commit, which obviously defeats the point of transactions."} {"task_id": "format-code-task-000124", "source_id": "format-code-task-000124", "domain": "code", "task_path": "tasks/format-code-task-000124", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:188e08d96d5749b4e92d163a266b0ab5726284b799c750bf250c303aa0f4e557", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Add a read API for model stages\n\nOur backend already persists **model stages** — each one is a named checkpoint that\nbelongs to a model (the stage carries a `name`, a `timestamp`, an optional `map`\nscore, and the id of the model it belongs to). The database table and ORM model are\nalready in place, but there is currently no HTTP API to look a stage up, and nothing\nguards against stages whose names are malformed. We need to expose model stages over\nthe same versioned REST API the rest of the app uses (`/api/v1`).\n\nPlease add a read API for model stages, mounted under `/api/v1/model_stages`, with the\nfollowing behaviour. Like the other resource endpoints, these require an authenticated\nactive user.\n\n## Fetch a single stage\n\n`GET /api/v1/model_stages/{stage_id}` returns the stage wrapped in the usual envelope:\n\n```json\n{\"result\": { ...stage fields... }}\n```\n\nThe returned stage must expose at least its `id`, `name`, `map`, and `model_id`, plus a\nnested `model` object exposing the owning model's `id` and `hash`.\n\n- If no stage has that id, the request fails as *not found* (HTTP 404) and the response\n body carries the error code **112001**.\n\n## Validate stage names on lookup\n\nA stage name is only considered valid when it is a non-empty string that forms a valid\nidentifier: it starts with a letter or an underscore and contains only letters, digits,\nand underscores (e.g. `best`, `stage_1`, `_tmp` are valid; `\"\"`, `1stage`, `with space`,\n`a-b` are not).\n\nWhen a single stage is fetched by id and its stored name is not valid, the request must\nfail with the error code **112002** (a distinct outcome from the not-found case above),\nrather than returning the stage.\n\n## Fetch several stages at once\n\n`GET /api/v1/model_stages/batch?ids=1,2,3` returns\n\n```json\n{\"result\": [ ...stages... ]}\n```\n\ncontaining exactly the stages whose ids exist, in any order; ids that match no stage are\nsimply omitted (an all-missing request yields an empty list). This batch endpoint returns\nthe matching stages without rejecting the request.\n"} {"task_id": "format-code-task-000125", "source_id": "format-code-task-000125", "domain": "code", "task_path": "tasks/format-code-task-000125", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:fcc9ac977a0a4e9bc3f22b9fac90b4c73b418a9ebd2e24caab3351590b527e82", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `parse_module` chokes on f-strings containing a generator expression\n\nI'm using LibCST to walk through a bunch of existing Python source files (building a small refactoring tool). On one of the files the parse just blows up, but the file itself is valid Python — `python -c` runs it fine and `ast.parse` is happy with it.\n\nI narrowed it down to f-strings that contain a generator expression inside the `{...}` part. Minimal repro:\n\n```python\nimport libcst as cst\n\nsource = 'x = f\"{sum(i for i in range(10))}\"'\ncst.parse_module(source)\n```\n\nThe same string parses fine with the stdlib:\n\n```python\nimport ast\nast.parse('x = f\"{sum(i for i in range(10))}\"') # OK\ncompile('x = f\"{sum(i for i in range(10))}\"', \"\", \"exec\") # OK\n```\n\nA bare generator expression wrapped in its own parens inside the f-string hits the same problem:\n\n```python\ncst.parse_module('x = f\"{(i*2 for i in range(3))}\"')\n```\n\nBoth of these are accepted by CPython itself, so I'd expect LibCST to handle them too. Right now anything with a `for ... in ...` clause inside an f-string expression slot seems to be rejected at parse time, which means I can't run my tool over files that happen to use this pattern.\n\nCould the f-string expression parser be updated to accept the same expression forms that CPython does here?"} {"task_id": "format-code-task-000126", "source_id": "format-code-task-000126", "domain": "code", "task_path": "tasks/format-code-task-000126", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2af7fa5e20499570618db65cf54766f9f0a07521ba1686c5e745dcd6d696ed6b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI'm trying to train the conf_branch method with a resnet18 backbone on CIFAR and it blows up with a shape mismatch as soon as it hits the forward pass. The configs/train_conf_branch.yml as-is doesn't seem to work for anything other than whatever tiny backbone it was originally written against. Also while poking around I noticed `postprocessor.name: opengan` just throws a KeyError saying it's not registered, and `trainer.name: opengan` only works if I spell it `openGan` which is weird. Can you take a look at the conf_branch + opengan pipelines end to end?\n\n# Expected outcomes\n\n- The conf_branch network wrapper should run a forward pass successfully with compatible CIFAR-style ResNet backbones and other compatible backbones with nontrivial feature/output dimensions.\n- `ConfBranchNet.forward(x)` should produce class predictions with shape `(batch_size, num_classes)`.\n- `ConfBranchNet.forward(x, return_confidence=True)` should return both class predictions and confidence scores, with confidence shaped `(batch_size, 1)`.\n- The conf_branch training configuration should use a recorder that is available through the normal configuration-driven recorder construction path so that the training pipeline can be constructed from the provided config.\n- `get_postprocessor` should accept `config.postprocessor.name: opengan` and construct the OpenGAN postprocessor.\n- `get_trainer` should accept `config.trainer.name: opengan` using the same lowercase spelling used in OpenGAN configs.\n- Conf_branch training epoch metrics should include the training loss in addition to accuracy and epoch index.\n\n# Implementation notes\n\n- The exact internal wiring, helper structure, and validation locations are up to the implementer.\n- Prefer behavior-compatible fixes that preserve existing public APIs and configuration-driven construction patterns.\n- Do not special-case a single backbone or dataset; the conf_branch path should work for compatible backbones that expose the representation needed by the wrapper."} -{"task_id": "format-code-task-000127", "source_id": "format-code-task-000127", "domain": "code", "task_path": "tasks/format-code-task-000127", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c880bca682f9acb39abc0c86edce758978214cb874c21a323e68f592a4e540d4", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `make_grid` 的 `normalize=True` 对单张图不生效\n\n我在用 jittor 训一个生成模型,每隔若干步把当前生成出来的图存盘看一下效果。生成出来的张量数值范围不是 [0, 1](大致在 [-1, 1] 左右),所以我用 `make_grid` / `save_image` 时传了 `normalize=True`,希望它在保存前把数值缩放到 [0, 1]。\n\nbatch 内有多张图时一切正常,存出来的拼图颜色看上去是对的。\n\n但是当我只想看单张图的时候(比如只生成一个样本,或者 debug 阶段只 forward 一张),保存出来的图整张要么全黑要么全白,完全没有被归一化。我换了几种 shape 试了一下:\n\n```python\nimport jittor as jt\nfrom jittor.misc import make_grid\n\n# 一个 batch=1 的图像,数值范围不在 [0,1]\nx = jt.randn(1, 3, 64, 64) * 5.0\n\nout = make_grid(x, normalize=True)\nprint(out.min(), out.max()) # 我期望接近 0 和 1,但实际还是原始范围\n```\n\n而把 batch 改成 ≥2 之后,`out` 的数值范围就被正常归一到 [0, 1] 了。所以 `normalize=True` 这个参数在单图场景下相当于没生效,结果跟我不传 `normalize` 一样。\n\n希望 `normalize=True` 不论输入是单张还是多张都能生效。"} {"task_id": "format-code-task-000128", "source_id": "format-code-task-000128", "domain": "code", "task_path": "tasks/format-code-task-000128", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:535af3b70c76953af7d20e53a7bebfad39cc63a32b005a508ce7b4b97058124a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n🐛 Bug: .allcontributorsrc is conflicting with formatting again\n### Bug Report Checklist\n\n- [x] I have tried restarting my IDE and the issue persists.\n- [x] I have pulled the latest `main` branch of the repository.\n- [x] I have [searched for related issues](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aissue) and found none that matched my issue.\n\n### Expected\n\nPRs generated by the `@allcontributors` bot shouldn't mangle formatting. The file should be formatted with tabs per the Prettier config.\n\n### Actual\n\nhttps://github.com/JoshuaKGoldberg/create-typescript-app/pull/1974 is replacing tabs with spaces.\n\nhttps://github.com/JoshuaKGoldberg/all-contributors-for-repository/pull/773 is an example in a downstream repo.\n\n### Additional Info\n\n_Sigh_. I've seen this before. Similar past issue: #837\n\n🎁"} {"task_id": "format-code-task-000130", "source_id": "format-code-task-000130", "domain": "code", "task_path": "tasks/format-code-task-000130", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:f0e3228519256c9143cd20e504a622c76560289db873abf9d998da015aa60dda", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI'm working with `Hyperplane` and `Line2D` in LazySets, and I want to be able to generate random points that actually lie on the hyperplane/line. Right now if I just call `sample` on a `Hyperplane`, the points I get aren't on it. It'd also be handy to have a way to project an arbitrary point onto a hyperplane or line. Ideally sampling a hyperplane would just give me points on it by default, but I'd still like to control the underlying distribution if I want to.\n\n# Expected outcomes\n\n- Projection onto hyperplane-like sets:\n - `project(x, hp::Hyperplane)` should accept an arbitrary point and return its orthogonal projection onto the given hyperplane.\n - The returned point should lie on the target hyperplane, and points that are already on the hyperplane should be unchanged up to the numeric precision of the element type.\n- Projection onto two-dimensional lines:\n - `project(x, L::Line2D)` should accept an arbitrary two-dimensional point and return its orthogonal projection onto the given line.\n - The returned point should lie on the target line, and points that are already on the line should be unchanged up to the numeric precision of the element type.\n- Sampling from hyperplanes and lines:\n - Calling `sample` on a `Hyperplane` without specifying a sampler should produce points that lie on that hyperplane.\n - Calling `sample` on a `Line2D` without specifying a sampler should produce points that lie on that line.\n - `HyperplaneSampler` should be available as a sampler for both `Hyperplane` and `Line2D`, and samples produced with it should lie on the requested set.\n - `HyperplaneSampler` should work with its default configuration and should also allow callers to control the sampling distribution through its public API.\n\n# Implementation notes\n\n- Preserve the existing public sampling API style and numeric-type flexibility used elsewhere in LazySets.\n- The concrete implementation strategy, helper organization, and validation location are up to the implementer, as long as the externally observable projection and sampling behavior above is satisfied.\n- Tests should tolerate ordinary floating-point roundoff for inexact numeric types."} {"task_id": "format-code-task-000131", "source_id": "format-code-task-000131", "domain": "code", "task_path": "tasks/format-code-task-000131", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a8257fe0cc824d6d9eb456fe2e1ee83c4b624e666ef108e35c5921b8fa2e116f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## SLES hosts aren't being recognized as a known OS\n\nWe have a mixed Linux fleet managed through Katello — RHEL, CentOS, Fedora, and a chunk of SUSE Linux Enterprise Server boxes. The Red Hat / CentOS / Fedora ones get their OS picked up correctly, but for the SLES hosts the OS comes back as nothing — Katello doesn't seem to map the distribution name reported by the subscription consumer to anything at all, so they end up without a proper OS assignment.\n\nExpected: SLES (and SUSE Linux Enterprise in general, since the distribution name reported can vary a bit) should be a recognized OS just like RHEL / CentOS / Fedora are. Could support for it be added?"} @@ -156,7 +152,6 @@ {"task_id": "format-code-task-000179", "source_id": "format-code-task-000179", "domain": "code", "task_path": "tasks/format-code-task-000179", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:e380a39b3b2b9fd26df9706e9d332829494fbe8c2709b78cd5d149229a0c6fad", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI’d like our sales quotations to pick a shipping method as soon as they’re created, instead of waiting until the order is confirmed or making the salesperson choose it manually. Ideally I could turn that on in Sales settings, and if the customer or delivery address changes on the quote, the carrier would refresh to match the new address.\n\n# Expected outcomes\n\n- A company-level Sales setting is available to enable or disable automatic carrier selection for newly created quotations. The setting is exposed through `res.config.settings.carrier_on_create` and stored on `res.company.carrier_on_create`.\n- The new quotation-time setting is independent from the existing confirmation-time automatic carrier assignment setting: enabling or disabling one must not silently change the behavior controlled by the other.\n- When quotation-time carrier selection is enabled and a new draft quotation is created without an already selected carrier, the quotation should automatically receive the carrier that matches the current customer or delivery address according to the existing delivery carrier rules.\n- If a carrier has already been explicitly set on a newly created quotation, automatic quotation-time selection should not replace that existing carrier.\n- When quotation-time carrier selection is disabled, creating a quotation should continue to leave carrier selection to the existing manual or confirmation-time flows.\n- When the customer or delivery address is changed on a quotation while quotation-time carrier selection is enabled, the quotation’s selected carrier should refresh to match the new address.\n- Confirming a sales order should continue to be governed by the existing confirmation-time automatic carrier assignment setting, independently of whether quotation-time carrier selection is enabled.\n\n# Implementation notes\n\n- Use the existing Odoo sales, delivery carrier, and configuration mechanisms where appropriate.\n- The exact internal helper structure, validation location, and data flow are up to the implementer, provided the observable quotation creation, address-change, configuration, and confirmation behaviors above are satisfied.\n- Keep compatibility with existing carrier assignment behavior outside the new quotation-time opt-in flow."} {"task_id": "format-code-task-000181", "source_id": "format-code-task-000181", "domain": "code", "task_path": "tasks/format-code-task-000181", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b8d835b2819c00e7b5f6cfc74f4c897a00c042e047dd8ff47604ffa32c00f07f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Improve how linestrings are assigned to their covering polygon\n\nWhen OSMNames builds the place hierarchy, every feature is assigned a `parent_id`\npointing at the single polygon that \"covers\" it (the most specific administrative\narea it sits in). For polygons, points and housenumbers this works well, but for\n**linestrings** (streets, rivers, …) the current rule is too strict and leaves many\nof them without a parent.\n\nToday a linestring only receives a parent when a polygon **fully contains the entire\nlinestring**, and only when that polygon is fine-grained enough (its `place_rank` is\nat or above a fixed threshold). In practice streets routinely run right up to — or\nacross — an administrative boundary, or poke slightly outside the area they belong to,\nso full containment almost never holds and the linestring is left unparented. The\n`place_rank` gate makes this worse by ignoring coarser polygons entirely.\n\nChange the way the single-covering-polygon assignment decides whether a linestring\nbelongs to a polygon so it is based on the linestring's **center point** — the point\nlocated halfway along the linestring — rather than on the whole geometry:\n\n- A linestring is assigned to a polygon when that linestring's center point lies\n inside the polygon, **even if the polygon does not contain the rest of the\n linestring** (e.g. the linestring extends beyond the polygon's boundary).\n- This must work **regardless of the polygon's `place_rank`** — the previous\n `place_rank` restriction for linestrings is removed; a coarse polygon may become a\n linestring's parent if it contains the center point.\n- A linestring whose center point is **not** inside a polygon must **not** be parented\n to it, even if one of its endpoints touches or lies within the polygon.\n- When more than one candidate polygon contains the center point, the linestring is\n assigned to the most specific one (the smallest, highest-`place_rank` polygon),\n exactly as a single covering polygon is chosen for any other feature.\n\nThis change applies to linestrings only. Polygons, points and housenumbers must keep\nbeing assigned to the polygon that fully contains them, exactly as before.\n"} {"task_id": "format-code-task-000182", "source_id": "format-code-task-000182", "domain": "code", "task_path": "tasks/format-code-task-000182", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:59dc1f354d243d39d7cabfaa479c32215529865417bd0a79f8d6164e8076fa49", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Housenumbers near administrative boundaries don't get a street_id\n\nWhen I import an OSM extract that spans several adjoining administrative\nareas, a lot of housenumbers end up with `street_id IS NULL` after the\nimport finishes — even though the corresponding street is clearly there in\n`osm_linestring`.\n\nLooking at the cases that fail, they all seem to sit close to the boundary\nbetween two parents: the housenumber is tagged into one admin area and the\nstreet geometry it actually belongs to is in the neighbouring one. So the\n`parent_id` on the housenumber and on the street differ, and the name-based\nmatching step (full match / levenshtein / substring) skips them entirely.\n\nConcretely, if I pick one such housenumber and check the linestring with\nthe matching `normalized_name` a few hundred meters away, it's obviously\nthe right street — same name, runs right past the address — but they have\ndifferent parents, so nothing gets linked. The result is a noticeable gap\nin `street_id` coverage along every admin border in the dataset.\n\nI'd expect the name-based street matching to also pick up streets that are\ngeographically close to the housenumber, not only ones that happen to share\nthe exact same `parent_id`. Streets near boundaries shouldn't fall through\nthe cracks just because OSM put them on the \"other side\" of an admin\npolygon."} -{"task_id": "format-code-task-000183", "source_id": "format-code-task-000183", "domain": "code", "task_path": "tasks/format-code-task-000183", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d7ea0fc34ba500b014555ac1295a15a67bd62827971ca15656a2d7d8d8bf4d72", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nWhen I want to add a custom variable to a particle in Parcels, right now I have to subclass `JITParticle` just to attach one extra `Variable`. It feels heavy when I only want one or two extra fields tracked per particle. Could the particle classes offer a class-level helper, in the requested `add_variable` style, that gives me back a pclass I can hand straight to `ParticleSet`? Would make my scripts so much cleaner.\n\n## Expected outcomes\n\n- Single custom variable: public particle classes such as `JITParticle` and `ScipyParticle` support `add_variable(...)` as a class-level API that returns a new particle class usable as `pclass` in `ParticleSet`.\n- Variable configuration: the single-variable API supports adding a variable from either a variable name plus existing `Variable` configuration options, or an existing `Variable` definition, while preserving normal `Variable` semantics.\n- Multiple custom variables: particle classes support adding more than one `Variable` definition in one class-level call, while preserving each variable's own name, initial value, dtype, and other supported configuration.\n- ParticleSet integration: a `ParticleSet` constructed with a class returned by the new API can read and write the added variables during kernels in both JIT and Scipy particle modes where those modes are supported.\n- Backward compatibility: the existing pattern of declaring custom `Variable`s in a particle subclass class body continues to work and remains behaviorally equivalent for the same variables.\n\n## Implementation notes\n\n- The public API shape is part of the requested behavior: `add_variable(...)` is the single-variable entry point, and a plural class-level entry point is expected for multiple variables.\n- The concrete class-construction mechanism, internal registration strategy, generated class naming, validation location, and storage layout are implementation details.\n- The new API should preserve existing `Variable` semantics rather than introducing a separate variable model.\n- Keep existing subclass-based particle definitions compatible while adding the lighter-weight class-level entry points."} {"task_id": "format-code-task-000185", "source_id": "format-code-task-000185", "domain": "code", "task_path": "tasks/format-code-task-000185", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1e9d92c3306cbb5f6117dc8074970b0868b9e898e7c177f99cf09ab58760a0ba", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Validator registrations never reach my external block builder\n\nI'm running a Prysm beacon node together with an external block builder service (MEV-Boost style setup). My validator client is configured to send validator registrations through the beacon node, and the calls all come back successful — but on the builder side, nothing ever shows up. The builder keeps reporting that it has zero registered validators, and as a result it never produces any blocks for me, so I'm always falling back to local block production.\n\nFrom the validator's point of view this looks like a complete success: the registration RPC against the beacon node returns OK every time. But the builder behind it is clearly never being told about any of these validators, so the whole external-builder pipeline is effectively a no-op for me even though I've wired everything up.\n\nWhat I'd expect: when a block builder is configured on the beacon node, validator registrations that come in over `SubmitValidatorRegistration` should actually be delivered to that builder so it can start producing blocks for those validators. If something goes wrong on the builder side while accepting the registration, I'd want that surfaced back to the caller as an error rather than silently swallowed.\n\nOne thing to keep in mind: not every node operator runs a builder. For nodes that don't have one configured, this RPC should still respond normally so that validator clients which always send registrations don't start erroring out against builder-less setups."} {"task_id": "format-code-task-000186", "source_id": "format-code-task-000186", "domain": "code", "task_path": "tasks/format-code-task-000186", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1a57816f127e15deb088a03eb9917b6c6012e6f0b1dbe2e82d93dba8c90e1d52", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nWhen I run `validator accounts import --keys-dir=... --holesky` and there's no wallet yet, it asks me \"Enter a wallet directory\" twice — and whatever I type the first time gets thrown away, only the second answer counts. I've also got my keystore JSON files sorted into subfolders under my keys dir, and the import doesn't seem to pick those up at all, only the ones sitting at the top level.\n\n# Expected outcomes\n\n- Wallet setup during `validator accounts import` should prompt for the wallet directory exactly once when no wallet exists yet, and the directory entered at that prompt should be the directory used for the wallet.\n- Importing through `validator accounts import --keys-dir ` should discover keystore JSON files in the keys directory and in nested subdirectories up to a maximum scan depth of 2 nested directory levels below the keys directory.\n- Keystore files located deeper than that maximum scan depth should not be imported, and the command should emit an informational message indicating that the maximum keystore-folder scan depth of 2 was reached.\n- The import operation should emit an informational message when validator keystore importing begins.\n- If directory processing fails during import, the command should report the failure as an inability to process the directory and import keys.\n\n# Implementation notes\n\nThe exact internal structure, helper boundaries, traversal mechanism, and validation location are up to the implementer. Preserve existing command-line behavior aside from the observable import-flow changes described above, and avoid making tests or behavior depend on private implementation details."} {"task_id": "format-code-task-000187", "source_id": "format-code-task-000187", "domain": "code", "task_path": "tasks/format-code-task-000187", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6df5c3ac3de21b62a38e60b0b602d472ee0a3b13ff8dd0ffff6f30e16f283711", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Support next-epoch crosslink committees with a registry-change option\n\nOur beacon-chain core exposes a function that returns the crosslink committees\n(each a set of validator indices together with the shard it is assigned to) for\na given slot. Today it only knows how to answer for slots that belong to the\n**previous** or **current** epoch — asking for a slot in the **next** epoch is\nrejected as out of bounds. We need it to answer for next-epoch slots too, since\nproposers and attesters have to look one epoch ahead.\n\nPlease extend the existing \"crosslink committees at slot\" lookup so that:\n\n- Slots whose epoch equals the next epoch are now valid and return the\n committees for that epoch instead of an error. The accepted range becomes\n `previousEpoch <= epoch(slot) <= nextEpoch`; a slot whose epoch is earlier\n than the previous epoch or later than the next epoch must still return an\n error.\n\n- Callers can optionally request a *registry change*. There are two valid\n shufflings for the next epoch — one that assumes the validator registry was\n rotated and one that assumes it was not — and the caller chooses between them.\n This option only affects next-epoch slots; for previous- and current-epoch\n slots the result must be exactly the same regardless of what is requested.\n\n- For a next-epoch slot, the default (no registry change) keeps the committees\n starting at the current epoch's start shard. When a registry change is\n requested, the committees are rotated forward: their start shard is advanced\n by the number of committees in the current epoch (taken modulo the configured\n shard count).\n\nExisting callers that only ask for previous/current-epoch committees and do not\ncare about a registry change must keep working without changes, and their\nresults must be unchanged.\n"} @@ -206,13 +201,11 @@ {"task_id": "format-code-task-000235", "source_id": "format-code-task-000235", "domain": "code", "task_path": "tasks/format-code-task-000235", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:38e51dd9aaff6026c754c3a0649da292a58bb82583b33a61a52a7dab7b726ac5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n \n\n**Rasa NLU version**: 0.13.4\n\n**Operating system** (windows, osx, ...): Windows\n\n**Content of model configuration file**:\n```yml\nlanguage: \"en\"\n\npipeline: \"spacy_sklearn\"\n```\n\n**Issue**:\nThe endpoint /evaluate of Rasa NLU HTTP server (server.py) is not up-to-date compared to the evaluate.py script of Rasa NLU. In particular it does not evaluate entities (only intents) and encounters some bugs that the script does not have.\n\nThus it would be great if Rasa NLU HTTP server could be inline with the latest evaluate.py script or maybe directly call it internally. Thanks!"} {"task_id": "format-code-task-000236", "source_id": "format-code-task-000236", "domain": "code", "task_path": "tasks/format-code-task-000236", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:0b8b463e022ec77b317a921bd586948de4752b49ff594c96e4fa0a62953a2287", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nThe remove-x-internal decorator doesn't remove references to x-internal components\nLet's say we're referencing two parameter components, one internal:\n```\n parameters:\n - $ref: '#/components/parameters/ProductID'\n - $ref: '#/components/parameters/Vendor'\n```\n```\n parameters:\n ProductID:\n in: path\n name: product_id\n description: The ID of the product.\n required: true\n schema:\n type: string\n format: uuid\n Vendor:\n in: header\n name: X-Vendor\n description: The vendor.\n schema:\n type: string\n x-internal: true\n```\n\nOnce we run the remove-x-internal decorator, the Vendor component will be removed, but the reference to it will remain. Perhaps because the order of the removals is wrong (we remove the component then check the reference?)\n\nFull repro: https://github.com/bojanz/openapi-cli-bug/tree/builtin-decorator"} {"task_id": "format-code-task-000237", "source_id": "format-code-task-000237", "domain": "code", "task_path": "tasks/format-code-task-000237", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:582e3ddc40d269a61ac6cdce28e739bc750081d86118defa9ed6cdc0c3cf1d90", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Callable objects (instances with `__call__`) rejected as a `typing.Callable` argument\n\nI'm using `runtime_validation` to type-check a function whose parameter is annotated as `typing.Callable[[int], str]`. Plain functions work fine, but if I try to pass an instance of a class that implements `__call__`, validation rejects it.\n\nMinimal repro:\n\n```python\nimport typing\nfrom enforce import runtime_validation\n\nclass Multiplier:\n def __call__(self, a: int) -> str:\n return str(2 * a)\n\n@runtime_validation\ndef run(f: typing.Callable[[int], str], b: int) -> str:\n return f(b)\n\n# works:\ndef bar(a: int) -> str:\n return str(2 * a)\nrun(bar, 5)\n\n# rejected:\nrun(Multiplier(), 5)\n```\n\nIn normal Python an object that defines `__call__` *is* callable — `Multiplier()(5)` works exactly like calling a function — so it feels surprising that `runtime_validation` only accepts plain functions here. Ideally, an object implementing `__call__` should be usable anywhere a regular function is expected, including when the parameter is typed as `typing.Callable[...]`, and its signature should still be validated against the declared `Callable[...]` argument/return types."} -{"task_id": "format-code-task-000238", "source_id": "format-code-task-000238", "domain": "code", "task_path": "tasks/format-code-task-000238", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:029305ec1673a697ddfa326c6fe8bb5ff9e749cd94e311fe75e79a164978db82", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `math.exp` returns `inf` instead of raising `OverflowError`\n\nI'm porting some code from CPython to RustPython and noticed that\n`math.exp` doesn't behave the same way for large arguments.\n\nIn CPython:\n\n```python\n>>> import math\n>>> math.exp(1e6)\nTraceback (most recent call last):\n File \"\", line 1, in \nOverflowError: math range error\n```\n\nIn RustPython:\n\n```python\n>>> import math\n>>> math.exp(1e6)\ninf\n```\n\nThis breaks code that wraps `math.exp` in `try/except OverflowError` —\nthe exception never fires on RustPython, and `inf` silently propagates\nthrough downstream calculations instead.\n\nI'd expect `math.exp` (and the other `math` functions in the same boat)\nto match CPython here: when the input is a finite number but the result\nwould overflow to infinity, raise `OverflowError` rather than returning\n`inf`.\n\nIn particular, `math.ldexp` has the same issue (e.g. `math.ldexp(1.0, 10000)`\nreturns `inf` instead of raising) — and while you're at it, please make sure\nthat special inputs to `ldexp` (NaN, ±inf, 0) are still returned unchanged\nrather than getting converted into an `OverflowError`."} {"task_id": "format-code-task-000239", "source_id": "format-code-task-000239", "domain": "code", "task_path": "tasks/format-code-task-000239", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3548fccfa3af16fdb79414c0a119701af2b827c7e2bee13d55fa43885db1ad84", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nfast method has bug when compute S1_conf/ST_conf\nthis is my setting:\n\n```python\nparam_values = fast_sampler.sample(problem, N=4935, seed=100) # N=4935\n```\nwhen the code do fast analyze as following sentence:\n```python\nSi = fast.analyze(problem, Y, print_to_console=True)\n# len(Y) = 34545, because len(Y)= N*D (D is number of parameters, there D=7, I have 7 parameters to analysis)\n```\n\n**The bug is comming**:\n\n```bash\n File \"C:\\ProgramData\\Anaconda3\\envs\\geo_env\\lib\\site-packages\\SALib\\analyze\\fast.py\", line 83, in analyze\n S1_d_conf, ST_d_conf = bootstrap(Y_l, N, M, omega_0, num_resamples, conf_level)\n\n File \"C:\\ProgramData\\Anaconda3\\envs\\geo_env\\lib\\site-packages\\SALib\\analyze\\fast.py\", line 116, in bootstrap\n S1, ST = compute_orders(Y_rs, N, M, omega_0)\n\n File \"C:\\ProgramData\\Anaconda3\\envs\\geo_env\\lib\\site-packages\\SALib\\analyze\\fast.py\", line 95, in compute_orders\n Sp = np.power(np.absolute(f[np.arange(1, int((N + 1) / 2))]) / N, 2)\n\n**IndexError: index 2467 is out of bounds for axis 0 with size 2467**\n```\n\nIn my opinion:\nIt is `np.arange(1, int((N + 1) / 2))` cause the bug, `np.arange` return is `[1,2,.....2467]`, however the lenth of f is 2467, the max index is 2466, So, I think maybe File \"C:\\ProgramData\\Anaconda3\\envs\\geo_env\\lib\\site-packages\\SALib\\analyze\\fast.py\", line 95, should change to `Sp = np.power(np.absolute(f[np.arange(0, int((N + 1) / 2)-1)]) / N, 2)`. Do you think so?\n\nSorry, my English is poor, my code is also poor. I wish l describe the problem clearly."} {"task_id": "format-code-task-000240", "source_id": "format-code-task-000240", "domain": "code", "task_path": "tasks/format-code-task-000240", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a5adce23cf67b83bc201947a6de1c2986d43f97316c6f12c9c460c7984af19ac", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nAdd an option to use encrypted connection\nCurrently to use an encrypted connection the client needs to pass some certificates.\nhttps://github.com/SAP/node-hdb#encrypted-network-communication\nIf HANA server is using a certificate signed by a public CA like VeriSign, there is no need to pass custom certificates as most public certificates are builtin in node.js. See `ca` optin in [tls.createSecureContext](https://nodejs.org/docs/latest/api/tls.html#tls_tls_createsecurecontext_options).\nFor such cases it would be useful to have a separate option to enable encryption, e.g.\n```js\nvar client = hdb.createClient({\n host : 'hostname',\n port : 30015,\n ssl: true,\n ...\n});\n```\nProbably a better name should be used as node actually uses TLS.\nAs a workaround you can pass `ca: undefined`\n```js\nvar client = hdb.createClient({\n host : 'hostname',\n port : 30015,\n ca: undefined,\n ...\n});\n```"} {"task_id": "format-code-task-000241", "source_id": "format-code-task-000241", "domain": "code", "task_path": "tasks/format-code-task-000241", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d1124feea675a7da84b08cfa52d3eb4757a07ea50f0ec7498f7f6d21386e9648", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Convenient access to the variance gradient at a single point in kriging surrogates\n\nI'm using `KRG` (and the MFK variants) for some Bayesian-optimization-flavoured work where, at a candidate point `x*`, I need the gradient of the predicted variance — i.e. the partial derivatives of the variance with respect to *all* input dimensions, evaluated at that one point.\n\nLooking at the public API of `SurrogateModel` / kriging-based models, the only thing I can find for variance derivatives is `predict_variance_derivatives(x, kx)`, which gives the derivative with respect to a single input component `kx`. So if my problem has `nx` inputs and I want the gradient at a point, I end up doing something like:\n\n```python\ngrad = np.array([\n sm.predict_variance_derivatives(x_star, kx).ravel()\n for kx in range(x_star.shape[1])\n])\n```\n\nThis works but feels off:\n\n* It's `nx` separate predict calls for what is conceptually one quantity at one point.\n* Every caller that wants \"variance gradient at a point\" has to re-implement the same loop + stacking + shape massaging, and it's easy to get the orientation of the resulting array wrong.\n* For acquisition functions / optimizers that ask the surrogate for a gradient at the current iterate, this is the natural thing to want directly from the model.\n\nIt would be great if kriging-based surrogates exposed a first-class way to ask, in one call, for the gradient of the variance at a given point — taking an `x` of shape `(1, nx)` (and ideally accepting a plain `(nx,)` vector for convenience) and returning the full vector of partials at that point.\n\nFor context, `predict_variance_derivatives(x, kx)` already covers the \"set of points, one component\" case and should keep working as it does today; what's missing is the dual \"one point, all components\" case. The two together would cover the typical use cases nicely.\n\nA natural name for the new entry point would be something like `predict_variance_gradient(x)`."} {"task_id": "format-code-task-000242", "source_id": "format-code-task-000242", "domain": "code", "task_path": "tasks/format-code-task-000242", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b6baf166493ce17466aacf6f623d06b08233d5fb214198da501736212ff69e94", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nDrawing of certain paths breaks in `cartopy` 0.25.0\nHello! I’m a developer of [mosaic](https://github.com/e3SM-Project/mosaic), a python package for unstructured mesh visualization which is heavily reliant on cartopy.\n\nWe’ve noticed an issue drawing certain paths when switching from cartopy `0.24.0` to `0.25.0`. See [E3SM-Project/mosaic/#42](https://github.com/E3SM-Project/mosaic/issues/42) for the original issue where this was brought to our attention. Here’s a minimum working example:\n```python\nimport cartopy\nimport cartopy.crs as ccrs\nimport numpy as np\nimport matplotlib.pyplot as plt\n\nfrom matplotlib.collections import PolyCollection\n\n# https://wktmap.com/?fae129b6\npatch = np.array([[\n [-180.00020734, -63.5383884 ],\n [-179.93611911, -63.61745971],\n [-179.77001049, -63.62512738],\n [-179.67109735, -63.55616224],\n [-179.74190981, -63.49385818],\n [-179.91362571, -63.48807984],\n [-180.00020734, -63.5383884 ],\n [-180.00020734, -63.5383884 ],\n]])\n\nfig, ax = plt.subplots(\n constrained_layout=True, subplot_kw={\"projection\": ccrs.PlateCarree()}\n)\n\ncollection = PolyCollection(patch, array=[1.], ec='k', alpha=0.5)\n\ncollection.set_transform(ccrs.PlateCarree())\n\nax.add_collection(collection)\nax.autoscale_view()\n\nax.set_title(f\"cartopy v{cartopy.__version__}\")\nax.gridlines(draw_labels=True)\n\nplt.show() \n```\nHere's what the patch looks like in cartopy `0.24.0`:\n```\nconda create -n cartopy_0.24.0 python=3.13 cartopy=0.24.0\n```\n\"Image\"\n\nAnd, here's what the patch looks like in cartopy `0.25.0`:\n```\nconda create -n cartopy_0.25.0 python=3.13 cartopy=0.25.0\n```\n\"Image\"\n\n----\n\nMy hunch is that the issue arises because the first/last index lies outside of the projection boundary (i.e. -180 deg). But, I haven't had time to through and test that hunch. \n\nFor some context, in `mosaic` we repeat the first index as the last to ensure the polygons are closed. Because we have variable resolution meshes, the polygons can have variable number of sides. To support ragged array likes this, we further repeat the first/last index as many times as needed to fill in up to the max number of sides.\n\n**cc'ing** @xylar @cbegeman"} {"task_id": "format-code-task-000243", "source_id": "format-code-task-000243", "domain": "code", "task_path": "tasks/format-code-task-000243", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b863f7e45366a2fca725f4e99c3b7f6fe8417ac4211cf7c9a1e80e8b9632572d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Old model versions are not cleaned up after a rolling update\n\nI'm running Seldon Core v2 and trying out rolling updates on a model. My setup is roughly:\n\n1. Apply a `Model` (e.g. `iris`) pointing at storage URI `.../iris/v1`.\n2. Wait for it to become ready.\n3. Re-apply the same `Model` with a new storage URI `.../iris/v2` to roll it forward.\n\nThe new version comes up fine and starts serving traffic, but the **old version never goes away**. If I keep rolling the model forward (v2 → v3 → v4 …) the previous versions just accumulate in the scheduler — version cleanup never seems to fire for them. I'd expect that once the new version is fully available and serving, the older one(s) should be cleaned up automatically the way the docs imply.\n\nI can reproduce this with a plain sklearn iris model — nothing fancy in the spec, just `requirements: [sklearn]` and a storage URI pointing at a rolling sample bucket.\n\n---\n\nWhile poking at this I also noticed something that looks related (same \"stale state hangs around\" flavour, but on the experiment side):\n\nIf I update an existing `Experiment` (change weights, change candidates, etc.), the new config takes effect but it doesn't feel like the previous routing for that experiment is being reset first — re-applying the same experiment a couple of times produces routing behaviour that doesn't match what I'd get from creating it fresh. Creating it fresh from a clean state works as expected.\n\nBoth symptoms feel like envoy-side state from the previous version of the object isn't being released before the new state is applied. Could the incremental processor be made to behave correctly across repeated model rollouts and experiment updates?"} -{"task_id": "format-code-task-000244", "source_id": "format-code-task-000244", "domain": "code", "task_path": "tasks/format-code-task-000244", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:554678bc02f1a5af7688f76031f2ff250132ac7c540940926b135395a397118e", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Missing `cm3` and `mm3` volume units\n\n`Measured::Volume` already supports `m3`, `in3`, `ft3`, liters and the various SI liter prefixes, but there's no support for cubic centimeters or cubic millimeters.\n\nThese come up all the time for small-volume measurements (think component packaging, lab/medical work, 3D-printing material usage, etc.), and right now I can't express them without converting by hand:\n\n```ruby\nMeasured::Volume.new(5, :cm3)\n# => Measured::UnitError: Unit 'cm3' does not exist\n```\n\nIt would be great if `cm3` and `mm3` were first-class units in `Measured::Volume`, so they can be constructed directly and converted to/from any of the existing volume units (liters, m3, in3, gallons, …) like the other units do."} {"task_id": "format-code-task-000245", "source_id": "format-code-task-000245", "domain": "code", "task_path": "tasks/format-code-task-000245", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1b003fa83015b358eb8534ea24dd552ef767044bf1e1f7df67a8a44b31d46338", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `IndexFilters` keyboard shortcut can't be turned off, and its tooltip always advertises it\n\nI'm embedding the `IndexFilters` component in a page that has its own keyboard handling. I noticed that whenever the user presses `F` anywhere on the page (outside of an input), `IndexFilters` grabs focus and switches into search/filter mode. This conflicts with shortcuts I want to handle myself, and in some contexts I simply don't want a global single-letter shortcut hijacking keystrokes at all.\n\nLooking at `IndexFiltersProps`, I don't see any prop to opt out of this behavior. The keydown handler inside `IndexFilters` always runs.\n\nThere's a related problem with the tooltip on the search/filter toggle button. The default tooltip text is something like:\n\n> Search and filter (F)\n\nThe `(F)` is hard-coded into the localized strings (across all of the `locales/*.json` files) because it's part of the same single translation key used for the tooltip. So even in cases where pressing `F` shouldn't do anything, the tooltip still tells users it will — which is wrong / misleading.\n\nI can override the tooltip via `filteringAccessibilityTooltip`, but that only patches the symptom on a single instance; the shortcut itself still fires, and every consumer that wants the same behavior has to know to override the string in every supported language.\n\n### What I'd like\n\nA way for the consumer of `IndexFilters` to disable the built-in keyboard shortcut behavior. When it's disabled:\n\n- pressing `F` outside of inputs should no longer cause `IndexFilters` to enter search/filter mode,\n- the default tooltip on the search/filter toggle button should stop advertising the `(F)` shortcut (and this should apply automatically across all supported locales, without each app having to ship its own override string).\n\nThe current behavior (shortcut on, tooltip mentions `(F)`) should remain the default so existing usages aren't affected.\n\nI'd expect this to be exposed as a new boolean prop on `IndexFilters`, something like `disableKeyboardShortcuts`."} {"task_id": "format-code-task-000246", "source_id": "format-code-task-000246", "domain": "code", "task_path": "tasks/format-code-task-000246", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:e9c8684023a5a4c7ae2ffb395ac4bf3e7f0d16c5805622ddc4b341575b41132a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Code actions feel stale after I move the cursor, and RuboCop seems to run on every keystroke\n\nI've been using ruby-lsp in VS Code on a moderately sized Ruby file that has several RuboCop offenses spread across the file (say, an indentation issue near the top, a string-quote issue further down, etc.).\n\n### What I'm seeing\n\nWhen I put my cursor on the first offense and open the lightbulb / quick fix menu, I get the expected fix for that offense. So far so good.\n\nThen I scroll down and click on a *different* offense in another part of the file. I expect the quick fix menu to show me an action for *this* offense. Instead I keep getting the same code action I got the first time, as if the editor is still showing me suggestions for the previous cursor location. If I keep moving around, the suggestions don't seem to track where I actually am in the file — they look frozen on whatever range was used the first time `textDocument/codeAction` fired for this file.\n\n### And separately (but I suspect related)\n\nWhile poking at this, I noticed the editor stalls noticeably every time code actions get requested, even when I haven't edited the file at all between requests — just moved the cursor. Watching activity, it looks like RuboCop is being re-run from scratch over and over for the same unchanged file contents. For a file that hasn't changed, re-analyzing it every time the cursor moves feels wrong and is making the experience pretty laggy.\n\n### What I'd expect\n\n- Code actions should reflect the current selection / visible range. Moving my cursor to a different offense should give me the fix for *that* offense, not a cached one from earlier.\n- Re-analyzing the file with RuboCop when nothing about the file has changed seems wasteful — that part I'd expect to be reused across requests on the same unchanged document.\n\nRight now it feels like the two are inverted: the thing that depends on where I'm looking is sticky, and the thing that doesn't depend on where I'm looking is being recomputed every time."} {"task_id": "format-code-task-000247", "source_id": "format-code-task-000247", "domain": "code", "task_path": "tasks/format-code-task-000247", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d58d8a32d17a0e389e55cd58cccc251b457368b8987ee8e33c5783673b181a45", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Add configurable \"toxics\" to proxies\n\nRight now a proxy is a dumb pipe: whatever a client sends is forwarded verbatim to the\nupstream and back. We want to be able to deliberately degrade a proxied connection so we can\ntest how applications behave against a flaky network. The first degradation we need is\n**latency**.\n\nIntroduce the notion of a *toxic* that can be attached to a proxy, independently for each of\nthe two traffic directions:\n\n- **upstream** — data travelling from the client toward the upstream server.\n- **downstream** — data travelling from the upstream server back to the client.\n\n## HTTP API\n\nAdd these endpoints to the existing API server (the one that already serves `/proxies`):\n\n- `GET /proxies/{proxy}/upstream/toxics`\n- `GET /proxies/{proxy}/downstream/toxics`\n\n Returns a JSON object that maps each available toxic's name to its current state. A freshly\n created proxy must already list a toxic named `latency` in **both** directions, and that\n toxic must start **disabled**. The latency toxic's state is a JSON object with these fields:\n `enabled` (bool), `latency` (number, milliseconds) and `jitter` (number, milliseconds). On a\n new proxy it reads `{\"enabled\": false, \"latency\": 0, \"jitter\": 0}`.\n\n- `POST /proxies/{proxy}/upstream/toxics/{name}`\n- `POST /proxies/{proxy}/downstream/toxics/{name}`\n\n Sets the complete desired state of the named toxic for that direction from the JSON request\n body and responds with the resulting toxic state as JSON. The body fully specifies the new\n state: any field that is omitted is reset to its zero value (so `enabled` defaults to\n `false`, and `latency`/`jitter` default to `0`). The change must persist — a subsequent\n `GET` reflects it — and must affect **only** the direction it was posted to; the same toxic\n in the other direction is left untouched.\n\n### Errors\n\n- A request for a proxy that does not exist responds with HTTP `404`.\n- A `POST` to a toxic name that does not exist responds with HTTP `404`.\n\n## Behavior\n\nThe latency toxic must actually slow traffic down, not just record settings. When the\n`latency` toxic is enabled with a latency of *L* milliseconds (and `jitter` 0) on a direction,\ndata flowing in that direction is delayed by approximately *L* milliseconds before it reaches\nthe other side. A direction whose latency toxic is disabled forwards data with no added delay,\nexactly as before.\n\nConfiguration applied before a client connects takes effect for that connection.\n"} @@ -265,14 +258,12 @@ {"task_id": "format-code-task-000303", "source_id": "format-code-task-000303", "domain": "code", "task_path": "tasks/format-code-task-000303", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:5ccd510cd931c4cec671e62e9bd5b616cf288e9c4715de6b87c326e77bce172d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want Scoary to install a `vcf2scoary` command for converting haploid VCF files into the Roary/Scoary-style presence/absence CSV that the main `scoary` command accepts. The command should run as `vcf2scoary [--out PATH] [--types LIST] [--force] `, defaulting the output path to `./mutations_presence_absence.csv`, refusing to overwrite an existing output file unless `--force` is supplied, and exiting non-zero with `Outfile already exists. Change name of outfile or run with --force` or `Unable to locate input file ` for those error cases.\n\nFor a VCF whose metadata includes `##fileformat=VCFv4.1` and `##FORMAT=`, the command should print `VCF version 4.1 detected` while processing and `Reached the end of the file` before exiting 0. It should write a quoted comma-separated CSV whose header is the VCF header with a `DUMMY` column inserted between `FORMAT` and the sample columns. For example, a record `NC_000962 4013 0 T C 9999 0 TYPE=snp GT 0 1 1 1` should become a CSV row with the original first nine fields, `False` in the `DUMMY` column, and only the genotype values `0,1,1,1` in the sample columns even if genotype cells contain colon-separated subfields.\n\nThe `--types` option should accept a comma-separated list such as `--types snp,ins,del`; when it is not `ALL`, only VCF records whose INFO column contains a matching `TYPE=` should be emitted. Multiallelic ALT values should be split into separate binary reference-versus-alternate rows: for `ALT=C,A` with sample genotypes `0,0,1,2`, the output should contain one row for `C` with `DUMMY` set to `True` and sample values `0,0,1,0`, and another row for `A` with sample values `0,0,0,1`; missing genotype `.` should be treated as `0`. If the VCF metadata says the GT format has `Number` other than `1`, the command should exit non-zero with `ERROR: Expected a single allele per genotype. Scoary only works for haploid organisms.`"} {"task_id": "format-code-task-000305", "source_id": "format-code-task-000305", "domain": "code", "task_path": "tasks/format-code-task-000305", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:eeb24ca7ef539ab28b329011fc1f923390f3096a6be7c3e9cceb852ac7d08d8b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nHey, I'm hitting a weird thing with `mockQuery` — if my query params include an array (like `{tags: ['a','b']}`), the mock never matches the request, even though I'm passing what looks like the exact same array on the other side. Plain string/number params work fine, it's specifically the array-valued ones that break. Would be great if `mockQuery` just matched when the arrays have the same items in the same order.\n\n# Expected outcomes\n\n- `mockQuery` should match requests whose query parameters include array values when the expected and actual arrays contain equivalent items in the same order.\n- Array-valued query parameters should remain order-sensitive: the same items in a different order, or arrays of different lengths, should not be treated as equivalent.\n- Equivalent array handling should work when array values appear inside ordinary query parameter objects, including nested values that are compared as part of deciding whether the query parameters match.\n- Existing query parameter comparison behavior for plain string, number, boolean, and object values should be preserved, including not matching values that differ in kind or differ in any supplied object property.\n- Any existing public equivalence helper used by this matching path should reflect the same observable matching semantics.\n\n# Implementation notes\n\n- The specific data structures, helper decomposition, type-checking approach, and validation locations are up to the implementer.\n- Preserve the existing public API shape while adding correct handling for array-valued parameters."} {"task_id": "format-code-task-000306", "source_id": "format-code-task-000306", "domain": "code", "task_path": "tasks/format-code-task-000306", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:44a5671a700b360b8ab9b69620d4818189f7c23f46d2e7333d50224ea784f117", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Make the Keras wrappers behave like real scikit-learn estimators\n\nThe `KerasClassifier` and `KerasRegressor` wrappers in this package are supposed to let a\ncompiled Keras model be used anywhere a scikit-learn estimator is expected, but right now they\ndon't actually work — they lean on Keras methods that no longer exist and they don't follow\nscikit-learn's estimator conventions. Please bring them up to a fully working, scikit-learn\ncompatible state.\n\nBoth estimators are constructed with a `build_fn` plus any number of extra keyword arguments,\ne.g. `KerasClassifier(build_fn=my_build_fn, hidden_dim=10)`. `build_fn` is a callable that\nreturns a **compiled** Keras model. The following three ways of supplying it must all work:\n\n1. a plain function,\n2. an instance of a class that implements `__call__`,\n3. `None`, in which case the wrapper is being subclassed and the subclass itself implements\n `__call__`.\n\nThe extra keyword arguments are model/fit parameters; any of them whose names match an argument\nof `build_fn` are forwarded to it when the model is built.\n\n## scikit-learn parameter API\n\n* `get_params()` returns a dict containing `build_fn` together with every extra keyword argument\n passed to the constructor, mapped to its current value. It accepts the usual optional `deep`\n argument.\n* `set_params(**params)` updates the given parameters in place and returns the estimator itself;\n a subsequent `get_params()` reflects the new values.\n* `sklearn.base.clone(estimator)` must succeed and return a new, **unfitted** estimator that\n carries the same constructor parameters.\n\n## KerasClassifier\n\n* `fit(X, y)` builds and trains the model and returns the estimator itself. Extra keyword\n arguments (e.g. `epochs`, `batch_size`) are forwarded to the underlying Keras `fit`. After\n fitting, `classes_` holds the sorted unique labels seen in `y` and `n_classes_` holds their\n count. The original label values must be preserved even when they are not a contiguous\n `0..k-1` range.\n* `predict(X)` returns a 1-D array of shape `(n_samples,)` whose entries are drawn from\n `classes_` (i.e. the original label values, not internal indices).\n* `predict_proba(X)` returns an array of shape `(n_samples, n_classes_)` whose rows sum to 1.\n For a binary problem whose network has a single output unit it must still return two columns.\n* `score(X, y)` returns the mean classification accuracy as a float in `[0, 1]`.\n\n## KerasRegressor\n\n* `fit(X, y)` builds and trains the model and returns the estimator itself, forwarding extra\n keyword arguments to the underlying Keras `fit`.\n* `predict(X)` returns a 1-D array of shape `(n_samples,)` for a single-output model.\n* `score(X, y)` returns the coefficient of determination R² (as scikit-learn defines it).\n\n## Serialization\n\nA fitted estimator must survive a `pickle` round-trip: after unpickling it produces the same\npredictions as the original.\n"} -{"task_id": "format-code-task-000308", "source_id": "format-code-task-000308", "domain": "code", "task_path": "tasks/format-code-task-000308", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a019aa67ecfd985b52db20ea60b739d775746c9e4d9eae82c3aee79ed2c80bfb", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the Go client to support multi-key existence checks from an existing connected client with `func (clnt *Client) BatchExists(policy *BatchPolicy, keys []*Key) ([]bool, Error)`.\n\nWhen I call `exists, err := client.BatchExists(nil, []*Key{keyA, keyB, keyC})` and `keyA` and `keyC` exist while `keyB` does not, I should get `[]bool{true, false, true}` with a nil error. When I call it with two missing keys, I should get `[]bool{false, false}` with a nil error; a missing key is a per-key false result, not a failed batch call. The returned slice must always be in the same positional order as the input keys, and a nil policy must use the client's default batch policy.\n\nThe method should perform the existence check as a batch operation that requests no bin data. It should honor batch read filtering by leaving filtered-out positions false and returning an error chain that includes `types.FILTERED_OUT`. If the server returns an unexpected per-key error, or returns bin data for an existence-only response, the method should return a non-nil `Error` instead of silently marking that key true."} {"task_id": "format-code-task-000309", "source_id": "format-code-task-000309", "domain": "code", "task_path": "tasks/format-code-task-000309", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b9d36d4ecd13ae72f8f22620a56261d149f3e2de7e54989ea9f1fa709a8a4d51", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the Go client to expose expression operation builders so an expression can be used as an Aerospike `*Operation` in `Client.Operate`, query execute operations, and other operation lists. The public API should include `ExpReadOp(name string, exp *Expression, flags ExpReadFlags) *Operation` and `ExpWriteOp(binName string, exp *Expression, flags ExpWriteFlags) *Operation`.\n\n`ExpReadOp` should create a read operation whose result bin name is `name` and whose payload is the supplied expression plus the supplied read flags. For example, `ExpReadOp(\"sum\", ExpNumAdd(ExpIntBin(\"a\"), ExpIntVal(5)), ExpReadFlagDefault)` should be sendable as an operation and should return the server-evaluated value under result name `sum`. `ExpReadFlagDefault` should be `0`, and `ExpReadFlagEvalNoFail` should be `1 << 4` so unknown or non-bin expression evaluation failures can be ignored.\n\n`ExpWriteOp` should create a write operation whose target bin is `binName` and whose payload is the supplied expression plus the supplied write flags. For example, `ExpWriteOp(\"total\", ExpNumAdd(ExpIntBin(\"a\"), ExpIntBin(\"b\")), ExpWriteFlagDefault)` should be sendable as an operation and should write the server-evaluated expression result into bin `total`. The write flags should include `ExpWriteFlagDefault == 0`, `ExpWriteFlagCreateOnly == 1 << 0`, `ExpWriteFlagUpdateOnly == 1 << 1`, `ExpWriteFlagAllowDelete == 1 << 2`, `ExpWriteFlagPolicyNoFail == 1 << 3`, and `ExpWriteFlagEvalNoFail == 1 << 4`.\n\nBoth builders should serialize the expression operation payload as an array containing the packed expression and the integer flags, then store that payload as the operation value. Calling either builder with the same expression, name, and flags should produce an equivalent `*Operation` and should not touch the filesystem, network, or global state. If the supplied expression cannot be packed, the builder should panic instead of returning a partial operation."} {"task_id": "format-code-task-000310", "source_id": "format-code-task-000310", "domain": "code", "task_path": "tasks/format-code-task-000310", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d493268674fdd2df767904f5c162a9b170364b119798be86d943d28666864b2d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nInconsistency in numba mode when passing scalar to function\nIn numba mode:\n```python\nimport aesara\naesara.config.mode = \"NUMBA\"\nimport aesara.tensor as at\n\nx = at.scalar(name=\"x\")\nf = aesara.function([x], 2*x)\nprint(repr(f(10))) # prints 20.0\n```\n\nIn c mode:\n\n```python\nimport aesara\nimport aesara.tensor as at\n\nx = at.scalar(name=\"x\")\nf = aesara.function([x], 2*x)\nprint(repr(f(10))) # prints array(20.)\n```\n\nThis came up in https://github.com/pymc-devs/pymc/issues/5937. Found by [bherwerth](https://github.com/bherwerth)."} {"task_id": "format-code-task-000311", "source_id": "format-code-task-000311", "domain": "code", "task_path": "tasks/format-code-task-000311", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:5ac6ca3ca6da73f740bc45fa868644d55e09f6890e325e26a55a531774c2cb94", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nAutofix(): Indexing error\nThe autofix function produces the following error: \n> IndexError: boolean index did not match indexed array along dimension 0; dimension is 138 but corresponding boolean dimension is 2\n\nCode to reproduce the error: \n```python\ndef test_autofix():\n x = load_sample()\n s = bct.autofix(bct.binarize(bct.threshold_proportional(x, .41)))\n assert np.allclose(np.sum(s), 7752)\n```\n\nThis is due to the following line: \nhttps://github.com/aestrivex/bctpy/blob/c8cfdeeca7d2437b93754ea3237f3e44b9c22957/bct/utils/other.py#L272\n\nProposed substituition:\n\n```python\nW[np.where(np.isinf(W))] = 0\nW[np.where(np.isnan(W))] = 0\n```"} {"task_id": "format-code-task-000312", "source_id": "format-code-task-000312", "domain": "code", "task_path": "tasks/format-code-task-000312", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b44e02b76460bd43394f8fdc5726935a3910408cca54d571f3139ec21e27e9c0", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n我给 dynamic preferences 的 Section 配了 verbose_name(比如 General settings),但在 Django admin 的偏好列表、右侧 section 过滤器和编辑页里看到的还是 general,Python 里 str(section) 打出来也是 general。我一开始还以为是 verbose_name 没生效,或者我配置写错了。\n\nExpected outcomes:\n- `Section.__str__()` should use a configured human-readable section name when one is provided.\n- Sections without a configured human-readable name should continue to display their original section name, and an empty section should still stringify to an empty string.\n- In the Django admin preference changelist, each preference’s section display should prefer the human-readable section name and fall back to the original section name when the section cannot be resolved.\n- In the Django admin section filter, filter option labels should prefer the human-readable section name and fall back to the original section name when the section cannot be resolved.\n- In the Django admin preference edit page, the read-only section display should prefer the human-readable section name and fall back to the original section name when the section cannot be resolved.\n\nImplementation notes:\n- Keep existing preference registration, lookup, filtering, and editing behavior intact; this change is only about the externally visible section label shown to users.\n- The exact data flow, helper structure, and admin customization approach are up to the implementation, as long as the observable API and admin behavior above are satisfied."} {"task_id": "format-code-task-000313", "source_id": "format-code-task-000313", "domain": "code", "task_path": "tasks/format-code-task-000313", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:dfd3be8722147c02ba9d7832e4886df7dec3d81c716623e3e27772a85280627c", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want Torus' `Configuration` class to support executable Python configuration files through a stateful API: `c = Configuration()`, `c.load(fname)`, and later `c.reload()`. `load(fname)` should accept a filesystem path string, execute that Python file as a module, remember the path for future reloads, and expose the file's public configuration globals through the existing configuration accessors. For example, if the file defines `SCHEMAS = {'main': {'match': 'app.*', 'intervals': {}}}`, then after `c.load(path)`, `c.schema('main')` should return that loaded schema and `c.schemas('app.hit')` should include it. If the file defines `AGGREGATES = [('app.total', 'app.*')]`, those aggregate rules should be available through `c.aggregates()` and should participate when `c.process(stat, value, timestamp)` expands matching stats.\n\nThe same load call should register `TRANSFORMS` and `MACROS` dictionaries by name, so `c.transform('name')` returns the callable supplied by the config file and `c.macro('name')` returns the macro mapping supplied by the config file. If the file defines `DEBUG`, `c.debug` should reflect that value after loading. Config-defined schema functions should be able to refer to Torus' `long_or_float` helper from the loaded module namespace.\n\nLifecycle hooks should run when present: a callable `on_load` in a config file is called during `load(fname)`, and a callable `on_reload` is called during `reload()`. `reload()` should clear the currently loaded debug value, schemas, aggregate rules, transforms, and macros, then re-execute every path already loaded on that `Configuration` instance. If a config file changes between `load()` and `reload()`, the accessors should reflect the new file contents after reload, and entries that only existed before reload should no longer be present. Calling `Configuration().reload()` before any files are loaded should succeed and leave the configuration empty. Passing a missing or unreadable path to `load(fname)` should raise the underlying `IOError` to the caller."} {"task_id": "format-code-task-000315", "source_id": "format-code-task-000315", "domain": "code", "task_path": "tasks/format-code-task-000315", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:386821f391aa66442a5866bd2931d6b3960820ca4a33d9ee76d4ccc7f06c019a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the scheduler objects to offer a direct run-and-wait convenience API for one-off jobs, in addition to the lower-level queue/result APIs. For asynchronous use, `AsyncScheduler.run_job(func_or_task_id: str | Callable[..., Any], *, args: Iterable[Any] | None = None, kwargs: Mapping[str, Any] | None = None, job_executor: str | UnsetValue = unset, metadata: MetadataType | UnsetValue = unset) -> Any` should be awaitable after the scheduler has been initialized and started. For synchronous use, `Scheduler.run_job(...) -> Any` should expose the same arguments and block through the scheduler's background event loop.\n\nWhen I call `await scheduler.run_job(add, args=[2, 3])`, it should enqueue exactly one job, wait until that job is released, fetch its result, and return `5`. When I call `await scheduler.run_job(greet, kwargs={\"name\": \"Ada\"})`, it should pass the keyword arguments to the task and return that task's return value. The `job_executor` argument should select the named executor for this one job, so `job_executor=\"threadpool\"` or `job_executor=\"processpool\"` runs the callable through that executor instead of the task default.\n\nIf the task raises an exception, `run_job()` should raise that same exception to the caller instead of returning a `JobResult`. If the recorded job outcome is a missed start deadline, it should raise `JobDeadlineMissed`; if the job is cancelled, it should raise `JobCancelled`. If the scheduler has not been initialized yet, calling `run_job()` should fail the same way as the scheduler's other initialized-only methods."} -{"task_id": "format-code-task-000316", "source_id": "format-code-task-000316", "domain": "code", "task_path": "tasks/format-code-task-000316", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:0da66b0a6a6ee964c90c4ecb11e4d292407e2c77204dcceb975fda09b3ce77cf", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the Go LINQ `Query` type to support lazy ordering and sorting methods. The public API should include `func (q Query) OrderBy(selector func(any) any) OrderedQuery`, `func (q Query) OrderByT(selectorFn any) OrderedQuery`, `func (q Query) OrderByDescending(selector func(any) any) OrderedQuery`, `func (q Query) OrderByDescendingT(selectorFn any) OrderedQuery`, `func (oq OrderedQuery) ThenBy(selector func(any) any) OrderedQuery`, `func (oq OrderedQuery) ThenByT(selectorFn any) OrderedQuery`, `func (oq OrderedQuery) ThenByDescending(selector func(any) any) OrderedQuery`, `func (oq OrderedQuery) ThenByDescendingT(selectorFn any) OrderedQuery`, `func (q Query) Sort(less func(i, j any) bool) Query`, and `func (q Query) SortT(lessFn any) Query`.\n\nFor `From([]int{3, 1, 2}).OrderBy(func(v any) any { return v.(int) })`, iterating the returned query should yield `1, 2, 3`. For `From([]string{\"aa\", \"b\", \"cc\"}).OrderByDescending(func(v any) any { return len(v.(string)) })`, iterating should yield the length-2 strings before `\"b\"`. Chained ordering should support multiple keys: given records with fields `{group, name}`, `OrderBy(group).ThenByDescending(name)` should sort by `group` ascending and, within equal groups, by `name` descending. `Sort` should let callers provide the direct less-than comparison; for `From([]int{3, 1, 2}).Sort(func(i, j any) bool { return i.(int) < j.(int) })`, iteration should yield `1, 2, 3`.\n\nThe typed variants should accept strongly typed functions through `any` and behave the same as the untyped variants, such as `OrderByT(func(v int) int { return v })` and `SortT(func(i, j int) bool { return i < j })`. Invalid typed function signatures should panic with the existing signature-validation errors, for example `OrderByT(func(i, j int) int { return i })` should panic with `OrderByT: parameter [selectorFn] has a invalid function signature. Expected: 'func(T)T', actual: 'func(int,int)int'`, and `SortT(func(i, j int) string { return \"\" })` should panic with `SortT: parameter [lessFn] has a invalid function signature. Expected: 'func(T,T)bool', actual: 'func(int,int)string'`.\n\nThese methods should be referentially transparent query transformations: creating the ordered query should not mutate the input slice or consume the source immediately, and iterating the same returned query with the same source values should produce the same ordered results each time. Empty inputs should iterate as empty results, and iteration should respect an early `yield` return of `false` without requiring callers to consume the entire sorted output."} {"task_id": "format-code-task-000317", "source_id": "format-code-task-000317", "domain": "code", "task_path": "tasks/format-code-task-000317", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:5e4a76b932d816c066a72dc1ed643f45b60f7b4779cb0a34456ce286ffa66c02", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n我想在 v2 的 `.ahoy.yml` 里给命令写更详细的 `description`,不然现在 `ahoy --help` / `ahoy --help` 只看得到 usage,长说明写了也像没生效一样。顺手也想把 v2 这些开发命令整理一下:build 相关走 goreleaser,加个 release 命令,旧的 godep 别名就不用留了。\n\nExpected outcomes:\n- Command descriptions: a command-level `description:` in a v2 `.ahoy.yml` command is treated as user-visible help text, including descriptions written as YAML multiline block strings.\n- Per-command help: `ahoy --help` shows the command’s `description:` content when it is configured, while commands without a description continue to work normally.\n- Global help: `ahoy --help` shows configured descriptions in the `COMMANDS:` section in addition to each command’s `usage:` summary; multiline descriptions remain readable as multiple lines, and commands without descriptions still show only their normal summary.\n- v2 development commands: in the repository’s v2 `.ahoy.yml`, `build` uses `goreleaser build --config ../.goreleaser.yml --snapshot --clean --single-target`, and `build-all` uses `goreleaser build --config ../.goreleaser.yml --snapshot --clean`.\n- v2 release command: the repository’s v2 `.ahoy.yml` defines a `release` command that runs `goreleaser release --config ../.goreleaser.yml --clean`.\n- v2 dependency command cleanup: the repository’s v2 `.ahoy.yml` no longer defines the old `godep` alias command.\n\nImplementation notes:\n- Preserve existing v2 command behavior except where the configured help text or the listed development commands are intentionally changed.\n- The data flow, formatting mechanism, and validation location for command descriptions are implementation choices, as long as the observable help output and command configuration behavior match the outcomes above.\n- Keep the help output readable for both single-line and multiline descriptions without requiring callers to use a different command-line entry point."} {"task_id": "format-code-task-000318", "source_id": "format-code-task-000318", "domain": "code", "task_path": "tasks/format-code-task-000318", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c9a6c16f49ded7d04f85e86b29d49536a6f81b92759faf455eaf701b1ba1982a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want Gnomix's command-line inference run to support an optional BED segment export controlled by the YAML config key `inference.bed_file_output`. When I run `python3 gnomix.py ` with `bed_file_output: True` in `config.yaml`, or run the training-mode command with a config file that sets that key to true, inference should use the generated `query_results.msp` file to create `/query_results_bed` if that directory does not already exist.\n\nFor each haplotype column in the MSP output, the command should write one tab-separated BED-style file under `query_results_bed`, naming files by replacing dots in the haplotype name with underscores and appending `.bed` (for example `NA001.0` becomes `NA001_0.bed`). Each file should have the columns `chm`, `spos`, `epos`, `ancestry`, `sgpos`, and `egpos` and no row index column. Consecutive MSP windows with the same ancestry call for that haplotype should be collapsed into a single segment: the segment starts at the first window's physical and genetic start positions, ends at the last consecutive window's physical and genetic end positions, and a new row begins only when the ancestry call changes. The `ancestry` column should contain the reference population names in the model's population order, not just numeric labels. On a successful BED export, the command should exit with status 0; if the BED output directory cannot be created or a BED file cannot be written, the command should fail non-zero instead of silently skipping those files."} {"task_id": "format-code-task-000319", "source_id": "format-code-task-000319", "domain": "code", "task_path": "tasks/format-code-task-000319", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4b65b6cbb100be4f28faeb14f36250a2c544c05e9c285890561946c318a26871", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Allow customizing the `.webp` filename rule\n\nMost WebP converters I've used (the ones that batch-convert `.jpg` / `.png` to `.webp`) keep the original extension and just append `.webp`. So `logo.png` becomes `logo.png.webp` on disk, not `logo.webp`. This is actually the default in a lot of tools.\n\nWith the current plugin I can't make the generated CSS line up with that. For example I have:\n\n```css\n.logo {\n background: url(/logo.png);\n}\n```\n\nand my actual file on disk is `/logo.png.webp`. But the plugin always rewrites the url to `/logo.webp`, which 404s.\n\nLooking at the existing options (`modules`, `webpClass`, `noWebpClass`) there's nothing that controls how the filename is rewritten — the `.png` → `.webp` substitution is hardcoded.\n\nCould we get an option to control how the new filename is derived from the old one? That way users whose webp files sit next to the originals as `name.png.webp` (or any other naming convention) can configure it without forking the plugin.\n\nI'd expect the new option to be something like `rename`.\n\nThanks!"} @@ -289,7 +280,6 @@ {"task_id": "format-code-task-000331", "source_id": "format-code-task-000331", "domain": "code", "task_path": "tasks/format-code-task-000331", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:290e9064ff9085de67279c0898bc75818d9119a7e916e83ef60982bcf21ce0fa", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## No way to disable response gzip compression in `HttpServer`\n\nLooking at `HttpServer`, when the servlet context is built it always installs a `GzipHandler` for response compression:\n\n```java\n// -- gzip handler\ncontext.insertHandler(new GzipHandler());\n```\n\nThere's no corresponding switch on `HttpServerConfig` — every service that uses airlift's http-server gets gzipped responses whether it wants them or not.\n\nThis is a problem in a few setups we have:\n\n- Services sit behind a reverse proxy / CDN that already handles content negotiation and compression. Doing gzip a second time at the origin is just wasted CPU.\n- Some downstream consumers want to look at raw response bodies (debugging, capturing traffic, simple clients that don't speak `Accept-Encoding`) and the automatic gzip layer gets in the way.\n- For some endpoints the payloads are already compressed (images, pre-gzipped blobs) and re-running them through `GzipHandler` is pointless.\n\nI'd like to be able to turn the response compression off via configuration, the same way other server features are toggled in `HttpServerConfig` (e.g. the `http-server.log.compression.enabled` flag for request log compression). The default should remain \"compression on\" so existing deployments don't change behavior — this is purely an opt-out for the cases above.\n\nThe new property would be something like `http-server.compression.enabled` on `HttpServerConfig`."} {"task_id": "format-code-task-000332", "source_id": "format-code-task-000332", "domain": "code", "task_path": "tasks/format-code-task-000332", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c127626b702e3ec7e9423b9eb41f91053582e614e11755eb49b503dddbcfa410", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want PeekingDuck's dabble pipeline nodes to support zone occupancy counting from object detections through two node objects: `dabble.bbox_to_btm_midpoint.Node(config: Dict[str, Any] = None, **kwargs: Any)` with `run(inputs: Dict[str, Any]) -> Dict[str, Any]`, and `dabble.zone_count.Node(config: Dict[str, Any] = None, **kwargs: Any)` with `run(inputs: Dict[str, Any]) -> Dict[str, Any]`.\n\nThe `bbox_to_btm_midpoint` node should read normalized bounding boxes from `inputs[\"bboxes\"]` and the image array from `inputs[\"img\"]`, then return `{\"btm_midpoint\": [...]}` where each point is the integer bottom midpoint in image pixels. For an image with shape `(400, 600, 3)` and one bbox `[0.1, 0.2, 0.3, 0.4]`, `run()` should return `{\"btm_midpoint\": [(120, 160)]}`. For the same image with no boxes, it should return `{\"btm_midpoint\": []}`, and it should not mutate the input image or bbox list.\n\nThe `zone_count` node should accept a config containing `input`, `output`, `resolution`, and `zones`, prepare the configured polygons at construction time, and count incoming `inputs[\"btm_midpoint\"]` points on each call to `run()`. Zone coordinates may be all non-negative integer pixel coordinates, or all fractions between 0 and 1 that are resolved against `resolution`; for `resolution: [1280, 720]`, the fractional zone `[[0.5, 0], [1, 0], [1, 1], [0.5, 1]]` should resolve to `[(640, 0), (1280, 0), (1280, 720), (640, 720)]` in the returned `\"zones\"` list. With zones `[[[0, 0], [640, 0], [640, 720], [0, 720]], [[0.5, 0], [1, 0], [1, 1], [0.5, 1]]]` and points `[(2, 2), (3, 3), (720, 700), (650, 50)]`, `run()` should return `\"zone_count\": [2, 2]`; with no points it should return counts `[0, 0]` and the same resolved zones. If a single configured zone mixes pixel coordinates and fractional coordinates, constructing the node should raise `ValueError` explaining that the zone must be all pixel-wise points or all fractions of the frame between 0 and 1."} {"task_id": "format-code-task-000333", "source_id": "format-code-task-000333", "domain": "code", "task_path": "tasks/format-code-task-000333", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c4797144ea39df7932efca2ecb3baee341e780bbce4d214d0c58d951afaaec44", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n我现在用 `darker` 的时候想临时按项目外的 Black 设置来跑,比如这次要换个 line length,或者保留字符串引号别被规范化,但好像只能靠 Black 配置文件控制。能不能让 `darker` 命令行里也能直接传这些 Black 格式化选项,而且我手动传的时候就按我这次传的来?\n\nExpected outcomes:\n- CLI line length: `darker` accepts `-l LINE_LENGTH` and `--line-length LINE_LENGTH`, and formatting uses the provided maximum line length for the current run.\n- CLI string normalization: `darker` accepts `-S` and `--skip-string-normalization`, and formatting preserves string quotes and prefixes instead of normalizing them for the current run.\n- CLI precedence over config: when `-c/--config` is used together with an explicit CLI line-length or skip-string-normalization option, the explicit CLI value takes precedence over the corresponding Black config setting for that run.\n- Config compatibility: when a Black configuration read through `-c/--config` requests skipped string normalization, `darker` formats consistently with that configuration.\n- User-facing help and documentation: `darker --help` and the README document the supported Black-related command-line options, including `-l/--line-length` and `-S/--skip-string-normalization`.\n\nImplementation notes:\n- Keep the behavior compatible with existing `darker` workflows, including formatting only the relevant changed portions.\n- The internal representation of option values, where configuration is merged, and how formatting options are passed through are implementation details.\n- Preserve existing command-line behavior for users who do not pass the new options."} -{"task_id": "format-code-task-000334", "source_id": "format-code-task-000334", "domain": "code", "task_path": "tasks/format-code-task-000334", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:f4697c5861852f80910a01d27bb2503078f1d4bc51be451a763a13e5394d15be", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\npypa/pip#10909 is so far the \"highest profile\" discussion I've found on this topic.\n\nIt seems that [pip](https://github.com/pypa/pip) and [colorama](https://github.com/tartley/colorama) are going to support only `FORCE_COLOR=` and `NO_COLOR=`, but not `PY_COLORS`.\n\nOn the other hand, Pytest does support `PY_COLORS={1|0}` and `NO_COLOR=` (with `PY_COLORS` taking precedence).\n\nSo in the end it may be best to do the same as Pytest:\n- `PY_COLORS={1|0}` (taking precedence over other options)\n- `NO_COLOR=`\n- and possibly `FORCE_COLOR=` (similar to [pip](https://github.com/pypa/pip) and [colorama](https://github.com/tartley/colorama))\n\nAs for the `true`/`false` discussion, I'm going to make the call to only support `PY_COLORS={0|1}` for now. Thanks @MatthijsBurgh for initiating the discussion and motivating me to look further into the topic!\n\n_Originally posted by @akaihola in https://github.com/akaihola/darker/pull/353#discussion_r846752942_"} {"task_id": "format-code-task-000335", "source_id": "format-code-task-000335", "domain": "code", "task_path": "tasks/format-code-task-000335", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:02f0c45a26481cf1e7b4a3b669d04ac7e1c459084286c8ac7fafbd6449cec851", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Make the filter for the homepage graph configurable\n\nThe big graph at the top of the console home page (the one showing Gbps over time) only shows flows where the input interface boundary is `external`. That criterion is baked into the query and I can't find any way to change it from the configuration.\n\nThis is awkward in a couple of deployments I'm running:\n\n- One instance is on a network where I haven't bothered classifying interfaces as external/internal — everything stays `undefined`. The homepage graph is just flat at zero even though the per-source-AS / per-country widgets right below it clearly show traffic going through. New users land on the page and assume Akvorado isn't actually receiving anything.\n- Another instance is used purely for internal observability inside a single AS. There's no \"edge\" in any meaningful sense and I'd much rather have that graph show the sum of *all* captured flows than nothing at all.\n- And in general, \"edge ingress\" isn't always the most useful default — depending on the deployment I might want to filter on a different boundary, a specific exporter group, etc.\n\nIt would be great if this could be exposed in the console configuration alongside the existing keys like `homepage-top-widgets`, `dimensions-limit` and `cache-ttl`, so each operator can pick whatever criterion makes sense for their setup — including no extra filter at all (i.e. just sum everything). The current behaviour should remain the default so existing deployments don't suddenly start showing different numbers.\n\nA natural name for the new console config key would be something like `homepage-graph-filter`."} {"task_id": "format-code-task-000336", "source_id": "format-code-task-000336", "domain": "code", "task_path": "tasks/format-code-task-000336", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:37517e4a7e2c426cb1c461e95ed3a3234868ebbc386b5b7f10f5cba4763539c6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Front seat \"Auto\" heating triggers the wrong seat\n\nI'm using the tesla_custom integration in Home Assistant. My car has the auto seat climate feature on the front seats, so the heated seat selects for `left` and `right` show an `Auto` option in addition to Off/Low/Medium/High.\n\nWhen I pick any of Off/Low/Medium/High the seat heater behaves correctly — the left select controls the driver's seat, the right select controls the passenger's seat.\n\nBut as soon as I pick `Auto` from either of the front seat selects, the wrong seat reacts (or nothing visible happens on the seat I actually selected). Switching back to Low/Medium/High on that same select then works fine again, so the select itself is wired up to the right seat — it's specifically the `Auto` path that ends up targeting a different seat than the one I clicked.\n\nSame thing happens in reverse: if `Auto` is currently active and I switch the select to one of the manual levels, the integration first tries to turn auto climate off, and that \"off\" call also seems to land on the wrong seat.\n\nIt looks like the regular seat heater command and the auto seat climate command don't agree on which seat index means \"driver\" vs \"passenger\", and the integration is feeding the same index to both. Could the Auto branch be fixed so that picking Auto on the left select actually turns on auto climate for the driver's seat (and right → passenger)?"} {"task_id": "format-code-task-000337", "source_id": "format-code-task-000337", "domain": "code", "task_path": "tasks/format-code-task-000337", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a6eac4fef2ef84134d37d247fe05a04347b3f7af2fc5e4e700407d79565ea4c3", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n[BUG] Resize with 2D masks crashes\nAdditional target in Resize fails.\n\n```python\nimport numpy as np\nimport albumentations as A\n\nimage = np.zeros((256, 256, 3), dtype=np.uint8)\nmask = np.ones((256, 256), dtype=np.uint8) # 2D mask\n\ntransform = A.Compose(\n [\n A.Resize(height=512, width=512), # Resize image + mask\n ],\n additional_targets={\"semantic_mask\": \"mask\"},\n)\n\naugmented = transform(image=image, semantic_mask=mask)\nprint(augmented[\"semantic_mask\"].shape)\n```\n\ngenerates error:\n```\n File \"C:\\Users\\aselimc\\micromamba\\envs\\dinov3\\Lib\\site-packages\\albumentations\\augmentations\\geometric\\resize.py\", line 833, in apply_to_mask\n return fgeometric.resize(mask, (self.height, self.width), interpolation=interpolation)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"C:\\Users\\aselimc\\micromamba\\envs\\dinov3\\Lib\\site-packages\\albucore\\decorators.py\", line 42, in wrapped_function\n result = func(img, *args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"C:\\Users\\aselimc\\micromamba\\envs\\dinov3\\Lib\\site-packages\\albumentations\\augmentations\\geometric\\functional.py\", line 261, in resize\n return resize_cv2(img, target_shape, interpolation)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"C:\\Users\\aselimc\\micromamba\\envs\\dinov3\\Lib\\site-packages\\albumentations\\augmentations\\geometric\\functional.py\", line 352, in resize_cv2\n return resize_fn(img)\n ^^^^^^^^^^^^^^\n File \"C:\\Users\\aselimc\\micromamba\\envs\\dinov3\\Lib\\site-packages\\albucore\\utils.py\", line 92, in __process_fn\n chunk = img[:, :, index : index + 4]\n ~~~^^^^^^^^^^^^^^^^^^^^^^^^^\nIndexError: too many indices for array: array is 2-dimensional, but 3 were indexed\n```\n\nbut error does not occur if I just pass it as \n```python\naugmented = transform(image=image, mask=mask)\n```\n\nalbumentationsx 2.0.10\nalbucore 0.0.33"} @@ -303,7 +293,6 @@ {"task_id": "format-code-task-000346", "source_id": "format-code-task-000346", "domain": "code", "task_path": "tasks/format-code-task-000346", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c23f59b07647d59ea2f7ab0091fe909474cd5366338223084d8b954c6a885b36", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Missing ZMSCORE support\n\nI'm using miniredis to unit-test a service that talks to Redis through go-redis. The service has a hot path where it needs to look up scores for a batch of members in a sorted set (a leaderboard), so instead of firing off N round-trips of ZSCORE it uses ZMSCORE to get them all in one call.\n\nWhen I point the same code at miniredis in tests, the ZMSCORE call doesn't go through — miniredis doesn't seem to know about that command. ZSCORE works fine, so it looks like ZMSCORE just hasn't been wired up yet.\n\nCould ZMSCORE be added? It's been a standard Redis sorted-set command for a while now and it'd be nice to be able to cover code paths that use it without having to rewrite them to loop over ZSCORE just for tests.\n\nIt would also be useful to have a matching Go helper on `Miniredis` / `RedisDB` alongside the existing `ZScore(...)`, so test setup/assertions can query multiple members at once directly without going through the protocol."} {"task_id": "format-code-task-000347", "source_id": "format-code-task-000347", "domain": "code", "task_path": "tasks/format-code-task-000347", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2a0f8c3207a91fac28a29412985b1b5760850cdfe34ff99c64104269ca051d47", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI'm trying to pull a list of all the chart repositories under one of my Container Registry instances so I can iterate over them in Terraform, but the alicloud provider doesn't seem to expose a data source for that — I can list image repos but not chart ones. Could you add something on the alicloud provider side so I can query chart repos under a given CR instance? Ideally I'd also be able to filter by name or by a set of ids, and dump the result to a file if I want.\n\nExpected outcomes:\n- Data source availability: Terraform configurations can use `data \"alicloud_cr_chart_repositories\"` to read chart repositories for a Container Registry instance.\n- Required input: `alicloud_cr_chart_repositories.instance_id` is required, so validation or planning reports a missing required argument when it is omitted.\n- Repository results: `alicloud_cr_chart_repositories.repositories` returns the matching chart repositories, with each item exposing `chart_repository_id`, `create_time`, `instance_id`, `id`, `repo_name`, `repo_namespace_name`, `repo_type`, and `summary`.\n- Stable identifiers: each repository `id`, and each value in the top-level `ids` output, identifies a chart repository using its instance, namespace, and repository name; the top-level `names` output contains the repository names.\n- Filtering: `alicloud_cr_chart_repositories.name_regex` limits results to repository names matching the regular expression, and invalid regular expressions are rejected during configuration validation.\n- Filtering by identifiers: `alicloud_cr_chart_repositories.ids` can be supplied to return only repositories whose identifiers are in the supplied set.\n- Optional file output: when `alicloud_cr_chart_repositories.output_file` is set, the data source writes the returned repository list to that path.\n\nImplementation notes:\n- Follow the provider’s existing conventions for Terraform data sources, schema validation, state shape, pagination, retries, and optional file output.\n- The specific helper functions, internal data structures, request construction, and filtering location are implementation details, as long as the public Terraform behavior above is satisfied.\n- Do not require users to manage chart repositories with a new resource in order to use this data source; it should work for existing chart repositories in the target instance."} {"task_id": "format-code-task-000348", "source_id": "format-code-task-000348", "domain": "code", "task_path": "tasks/format-code-task-000348", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:31c78e4cce4a54124d7a9da9b14f48aa2d1be2f7e75fdde382d3c5b8d743e81d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Bring the EMR (v2) cluster resource up to date with newer service capabilities\n\nThe `alicloud_emrv2_cluster` resource is missing a few configuration options that the\nunderlying EMR service now supports. Please extend the resource so users can express them\nin their Terraform configurations.\n\n## System disk encryption\n\nToday the node-attributes block of a cluster only lets users turn on encryption for *data*\ndisks (`data_disk_encrypted` / `data_disk_kms_key_id`). Add the equivalent options for the\n**system** disk:\n\n- `system_disk_encrypted` — a boolean toggle for whether the node's system disk is encrypted.\n Optional.\n- `system_disk_kms_key_id` — the KMS key id used to encrypt the system disk. Optional, and a\n string. An empty value is not a meaningful key id and must be rejected during validation\n (i.e. configuring it as `\"\"` should produce a validation error); any non-empty value is\n accepted.\n\nBoth options describe how a node is provisioned at creation time, so — like the existing\nnode-attribute fields — they are immutable: changing either of them must force the cluster to\nbe recreated rather than updated in place.\n\n## Newer enumerated values\n\nTwo existing fields reject values that the service now accepts. Widen their accepted sets\n(without dropping any value already accepted today, and while still rejecting anything outside\nthe set):\n\n- The node group type now also supports `MASTER-EXTEND`, in addition to the existing\n `MASTER`, `CORE`, `TASK`, and `GATEWAY`.\n- A bootstrap script's execution moment now also supports `BEFORE_START`, in addition to the\n existing `BEFORE_INSTALL` and `AFTER_STARTED`.\n\nThese should behave like the other validated string fields: a configuration using one of the\naccepted values plans cleanly, and a value outside the accepted set is reported as invalid.\n"} -{"task_id": "format-code-task-000349", "source_id": "format-code-task-000349", "domain": "code", "task_path": "tasks/format-code-task-000349", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c4c8a1de5ee7c32269af98da665324349deb312af84e72f9d3a6a2e962c2734d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the `image-syncer` root command to load synchronization inputs from user-supplied configuration files before it starts copying registry images.\n\nThe CLI should support `image-syncer --images ` with an optional `--auth `, and it should also support the deprecated combined form `image-syncer --config `. These files may be JSON, YAML, or YML; paths with any other extension should fail during startup before any registry transfer begins. For example, running `image-syncer --images rules.txt` should exit non-zero and report an initialization error that includes `decode image file rules.txt error: only one of yaml/yml/json format is supported`.\n\nIf neither `--config` nor `--images` is provided, startup should fail non-zero with an initialization error that includes `neither config.json nor images.json is provided`. If `--images` is provided without `--auth`, startup should continue and log a warning that no authentication information was found because neither `config.json` nor `auth.json` was provided.\n\nFor separate auth files, each auth entry should load `username`, `password`, and `insecure`, and environment variables in usernames and passwords should be expanded. When building transfer tasks, source and destination repositories should receive the auth entry whose configured repository key matches the repository path on a slash boundary; if no auth entry matches, the command should log that access for that repository will be anonymous.\n\nThe image rules file should map each source image to either one destination string or a list of destination strings. Environment variables in destination strings should be expanded, duplicate destinations in a list should be collapsed, and each source/destination pair should become a sync task. Empty destination strings, empty destination lists, and destination lists containing non-string values should fail during startup; for an empty destination, the error should include `empty destination is not supported for source: `.\n\nThe command should also accept repeatable `--os ` and `--arch ` filters, ignore empty filter values, and pass the remaining filters into the generated sync tasks. `image-syncer --help` should list `--config`, `--auth`, `--images`, `--os`, and `--arch` alongside the other root command flags and exit 0."} {"task_id": "format-code-task-000350", "source_id": "format-code-task-000350", "domain": "code", "task_path": "tasks/format-code-task-000350", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:273eb4bbeaa57797a12df29ea02de287471707e1e97ffad7f3581f1a417984ea", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the Go utility package to expose `GenerateRepoURLs(url string, externalTagsOrDigest func(string, string) ([]string, error)) ([]*RepoURL, error)` as a one-shot parser and expander for Docker image references. When I call it with `\"nginx:v1\"` and a tag provider that would return `[]string{\"latest\"}`, it should return one `RepoURL` whose `String()` is `docker.io/library/nginx:v1`, `GetRegistry()` is `docker.io`, `GetRepo()` is `library/nginx`, and `GetTagOrDigest()` is `v1`; the provider should not be consulted for this concrete tag. When I call it with `\"127.0.0.1:300/library/nginx:v1,v2\"`, it should return two entries for the same registry and repository, preserving the tag order `v1`, then `v2`.\n\nIf the URL has no tag or digest, such as `\"registry.hub.docker.io/library/nginx\"`, the function should call the supplied tag provider with registry `registry.hub.docker.io` and repository `library/nginx`, then return one `RepoURL` per provided tag using those tags in provider order. If the URL uses a tag regex like `\"test-regex/test:/b+/\"`, it should fetch all tags through the provider, compile the regex between the slashes, and return only matching tags; for provider output `[]string{\"aaa\", \"bbb\"}`, the result should contain only tag `bbb`. If the URL uses a digest like `\"registry.cn-beijing.aliyuncs.com/hhyasdf/hybridnet@sha256:df2ef9e979fc063645dcbed51374233c6bcf4ab49308c0478702565e96b9bc9e\"`, the returned `RepoURL` should preserve that digest, use `@` in `GetRepoWithTagOrDigest()`, and report repository `hhyasdf/hybridnet`.\n\nInvalid input should return a non-nil error instead of partial results: a regex tag must have both leading and trailing `/`, an invalid regex should report a regex error, an invalid repository reference should report a parse error, and an error returned by the tag provider should be propagated with context. For the same input and a deterministic tag provider, repeated calls should produce equal ordered results. The function should not write files, perform network access directly, or keep hidden global state; all external tag lookup must happen through the supplied callback."} {"task_id": "format-code-task-000352", "source_id": "format-code-task-000352", "domain": "code", "task_path": "tasks/format-code-task-000352", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3fa6514d743c42dc40ddc3724bb24049abeb0b0e42e557f8bd64aef87eab75d3", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nWhen I move a chassis to a different rack in Ralph, the blades under it still show the old rack afterward, which makes the location data inconsistent. Could you make the directly attached child assets follow the parent’s rack when I save that change?\n\n## Expected outcomes\n\n- When an existing parent data center asset is saved after its rack changes, each directly attached child data center asset reflects the parent’s new rack.\n- Child assets that are not directly attached to the moved parent are outside the required synchronization scope.\n- Saving a parent without changing its rack should not introduce unrelated location changes.\n\n## Implementation notes\n\n- The specific place where the synchronization is performed is up to the implementation, as long as the externally observable saved asset state is consistent afterward.\n- Preserve existing validation and save behavior for data center assets while adding the rack synchronization behavior."} {"task_id": "format-code-task-000354", "source_id": "format-code-task-000354", "domain": "code", "task_path": "tasks/format-code-task-000354", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4fb69ee10d4f5db63d0ec8f84d1d7c2517842fd9afdae0f1bcee81430b800134", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### SecurityScan piling up multiple records per host\n\nWe push scan results into ralph from an external vulnerability scanner. The integration runs on a schedule and `POST`s the latest scan for each host to `/api/security-scans/` (using `host_ip` to identify the target).\n\nAfter running this for a while I noticed that ralph keeps **every** scan we've ever submitted for a given host. So for a single machine I end up with dozens of `SecurityScan` rows, all pointing at the same `base_object`, and the API/admin happily lets them accumulate forever.\n\nConceptually that doesn't make sense for our use case — there is only ever one \"current\" scan result for a host. The previous one is stale the moment a new scan finishes; we don't want history, we want the latest state. The Security Info tab in the admin already kind of acknowledges this (it only shows one entry per host anyway), so the underlying data model storing N of them feels wrong.\n\nWhat I'd expect:\n\n- Re-`POST`ing a scan for a host that already has one should replace the previous one rather than add another row.\n- Each host should only ever have one `SecurityScan` associated with it.\n\nIt would also be nice if existing databases (ours has been running for a while and already has the duplicates) got cleaned up to the \"one per host\" state when this is fixed — otherwise we'd have to write our own cleanup script before the new behaviour can be enforced.\n\nIs there a reason scans were modelled as \"many per host\" originally? If not, can we move to a one-scan-per-host model?"} @@ -318,7 +307,6 @@ {"task_id": "format-code-task-000366", "source_id": "format-code-task-000366", "domain": "code", "task_path": "tasks/format-code-task-000366", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:51f4bd2495b3122889b2bf4bb252301cb62f5ad23f87d25298272fd6b5e5f785", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Flesh out order management on the Trading API client\n\nRight now `TradingClient` can only submit a new order (`submit_order`). That's not\nenough to actually manage orders against the Alpaca trading API — there's no way to\nlist existing orders, look one up, change one, or cancel them. Please round out the\nclient so it covers the rest of the `/v2/orders` routes.\n\nAdd the following methods to `TradingClient`:\n\n- **`get_orders(filter=None)`** — returns a `list` of `Order` objects by issuing a\n `GET` to `/v2/orders`. The optional `filter` is a `GetOrdersRequest` describing the\n standard query parameters: order `status`, `limit`, `after`/`until` timestamps, sort\n `direction`, `nested`, `side`, and a list of `symbols`. Every field is optional and\n only the ones that are set should be sent. When the filter supplies a list of\n symbols, they must be transmitted as a single comma-separated `symbols` query\n parameter (e.g. `symbols=SPY,AAPL`), not as repeated parameters. Calling it with no\n filter must still work and simply send no query parameters.\n\n- **`get_order_by_id(order_id, filter=None)`** — returns the `Order` retrieved from\n `GET /v2/orders/{order_id}`. The optional `filter` is a `GetOrderByIdRequest`\n carrying the `nested` flag.\n\n- **`replace_order(order_id, order_data=None)`** — updates an existing order via\n `PATCH /v2/orders/{order_id}` and returns the resulting `Order`. The optional\n `order_data` is a `ReplaceOrderRequest` describing the fields that may be changed\n (`qty`, `time_in_force`, `limit_price`, `stop_price`, `trail`, `client_order_id`);\n again, only fields that are set should be sent.\n\n- **`cancel_orders()`** — issues a `DELETE` to `/v2/orders` and returns a `list`\n describing the cancellation outcome of each order. The API responds with an array of\n objects each carrying the order `id` and an integer HTTP `status`; surface each as a\n `CancelOrderResponse` exposing `id` (a `UUID`) and `status` (an `int`).\n\nWherever a method takes an order id, accept either a `UUID` instance or a UUID-formatted\nstring. If the value is neither (for example an arbitrary non-UUID string), raise a\n`ValueError` before any request is made.\n\nThe new request objects (`GetOrdersRequest`, `GetOrderByIdRequest`,\n`ReplaceOrderRequest`) and the `CancelOrderResponse` model should be importable from the\nsame place as the existing order request models (e.g. `MarketOrderRequest`), and the\nrequest objects should follow the existing convention of omitting unset fields when\nserialized.\n\nOne more thing: an `Order`'s `client_order_id` is a user-supplied identifier that is not\nnecessarily a UUID, so make sure an `Order` whose `client_order_id` is an arbitrary\nstring parses correctly.\n"} {"task_id": "format-code-task-000367", "source_id": "format-code-task-000367", "domain": "code", "task_path": "tasks/format-code-task-000367", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:7412629e5ffe26738c8b3156745a3060e3274df6c3f0ea6c5d9860724357ff0c", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the package entry point to expose a NestJS dynamic module registration API through `UnleashClientModule`. The class should provide `static forRoot(config: { config: UnleashConfig; isGlobal: boolean }): DynamicModule`: when called with `{ config: { url: 'http://unleash.test/api/', appName: 'api' }, isGlobal: true }`, it returns module metadata whose `module` is `UnleashClientModule`, `global` is `true`, `exports` includes `UnleashClientProvider`, `UNLEASH_CLIENT_CONFIG`, and `Reflector`, and `providers` includes a value provider for `UNLEASH_CLIENT_CONFIG` with the same object, a factory provider that creates `UnleashClientProvider` from the nested `config`, `Reflector`, and `UnleashGuard`. Calling `forRoot` with the same config and `isGlobal: false` should return equivalent metadata with `global` set to `false`, and the supplied config object must not be mutated.\n\nI also want `static forRootAsync(options: { imports?: ModuleMetadata['imports']; useFactory?: (...args: any[]) => Promise<{ config: UnleashConfig }> | { config: UnleashConfig }; inject?: any[]; isGlobal?: boolean }): DynamicModule`. When called with an imports array, an inject array, a factory function, and `isGlobal: true`, it should preserve the imports on the returned module metadata, set `global` to `true`, export `UnleashClientProvider`, `UNLEASH_CLIENT_CONFIG`, and `Reflector`, register `UNLEASH_CLIENT_MODULE_OPTIONS` with the supplied factory and inject list, register `UNLEASH_CLIENT_CONFIG` as the resolved module options, and register a factory provider that creates `UnleashClientProvider` from the resolved nested `config`. When called as `forRootAsync({ isGlobal: false })`, it should return `imports: []`, `global: false`, no `UNLEASH_CLIENT_MODULE_OPTIONS` factory provider, and still include the client provider, config token provider, `Reflector`, and `UnleashGuard`. These registration calls should only construct Nest module metadata; repeated calls with the same input should return equivalent results and should not open network connections, write files, or mutate global state."} {"task_id": "format-code-task-000368", "source_id": "format-code-task-000368", "domain": "code", "task_path": "tasks/format-code-task-000368", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4fc89374e37dc61d69b5bbf1fd4707284f9e0ea8ca6982500386d70b39691f6e", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want to import `UnleashClientProvider` from `@alpha018/nestjs-unleash-client` and use it as a Nest injectable, stateful facade over the Node Unleash SDK. The class should be constructible as `new UnleashClientProvider(config: UnleashConfig)`, expose `onModuleInit(): void`, `onModuleDestroy(): void`, a readonly `unleashClient: Unleash` getter, `isEnabled(name: string, context?: Context): boolean`, and `getFeatureToggleDefinition(toggleName: string): FeatureInterface | undefined`.\n\nWhen `onModuleInit()` is called with a config such as `{ url: 'http://localhost:4242/api', instanceId: 'test-instance', appName: 'test-app' }`, it should create one `Unleash` SDK client with that config and make it available through `unleashClient`. During initialization it should register SDK `error` and `warn` listeners; an error event should be logged through Nest's `Logger.error` with the error message and stack, and a warning event should be logged through `Logger.warn` with the warning message.\n\nAfter initialization, `provider.isEnabled('checkout', { userId: '42' })` should return the boolean produced by the SDK client's `isEnabled('checkout', { userId: '42' })`; for example it returns `true` when the SDK returns `true`, and `false` when the SDK returns `false`. `provider.getFeatureToggleDefinition('checkout')` should return the SDK client's feature toggle definition object for that name, and should return `undefined` when the SDK has no definition for that name. When `onModuleDestroy()` is called, the provider should destroy the retained SDK client by calling its `destroy()` method."} -{"task_id": "format-code-task-000369", "source_id": "format-code-task-000369", "domain": "code", "task_path": "tasks/format-code-task-000369", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:f4d3998ac4e14715f8c93f75d77824c3d26ba3c89f4c500fa818c4e254b5390d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI need the existing SSHClient object to expose `ExecuteCommand(cmd string) (string, error)` for running dashboard metric collection commands over its already-open SSH connection. Each call should trim surrounding whitespace only for allowlist checking, accept only commands whose trimmed text starts with one of these prefixes: `lscpu `, `top -`, `which `, `nvidia-smi `, `amd-smi `, `rocm-smi `, `free -`, or `df -`; any other command, such as `uname -a`, must return an empty string and an error whose message is `command not in allowed list: `, without opening an SSH session or sending the command to the remote host.\n\nFor an allowed command, `ExecuteCommand` should open a fresh SSH session on that client, run the command with combined stdout/stderr capture, close the session before returning, and return the captured text as a Go string. If the remote command exits successfully, the error return is nil; for example, if the remote server responds to `free -m | grep Mem:` with `Mem: 1000 400 600\\n`, the method returns that exact string and nil. If the remote command writes `warn\\n` and exits non-zero for an allowed command such as `df -h | grep -E '^/dev/'`, the method still returns `warn\\n` together with the SSH command error. If creating the session fails, return an empty string and the session creation error."} {"task_id": "format-code-task-000370", "source_id": "format-code-task-000370", "domain": "code", "task_path": "tasks/format-code-task-000370", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:987d25dad6f3b5c821f6ef768d78b0660998b6892feb8115b88af520771b5c92", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nI'm passing `cutoff_time` into `Entity.head()` / `EntitySet.head()`, but the rows I get back still include records after that timestamp. I also hit weird behavior with `Variable.head(cutoff_time=...)`: sometimes it looks like the cutoff is ignored, and in one case it errored instead of returning the expected variable values.\n\n## Expected Outcomes\n\n- `Entity.head(n=..., cutoff_time=...)` and `EntitySet.head(entity_id, n=..., cutoff_time=...)` should apply the cutoff to the returned data before limiting to the requested number of rows.\n- Timestamp-style cutoffs should exclude rows at or after the cutoff time.\n- Tabular cutoffs supplied as a two-column pandas `DataFrame` should constrain results using the provided instance identifiers and their associated cutoff times.\n- `Variable.head(n=..., cutoff_time=...)` should return the requested variable as a single-column `DataFrame` while honoring the same cutoff behavior.\n- Invalid `cutoff_time` inputs should fail clearly with `ValueError` and the message `cutoff_time must be None, a Datetime, a pd.Timestamp, or a pd.DataFrame`.\n\n## Implementation Notes\n\nThe filtering location, helper structure, and internal data flow are implementation details. Preserve the existing public API shape for `Entity.head`, `EntitySet.head`, and `Variable.head`, and make the externally visible returned data and errors match the behaviors above."} {"task_id": "format-code-task-000371", "source_id": "format-code-task-000371", "domain": "code", "task_path": "tasks/format-code-task-000371", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3f21f9e3d5ce26351c80f2447dcfb831b0e29079db6d7f47070d77da01f725ef", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nCannot initialize a ColumnSchema without initialized Ordinal logical type\nPR #870 made a change which allowed users to initialize a column schema object with an ordinal logical type, without first instantiating the ordinal logical type, as long as the column schema was not tied to data. This seems to have been broken with the 0.4.0 release of woodwork, and it is no longer possible to do this.\n\nThe ability to use a non-instantiated Ordinal logical type is needed/preferred for the Featuretools integration.\n\n#### Code Sample - Woodwork 0.3.1\n\n```python\n>>> from woodwork.column_schema import ColumnSchema\n>>> from woodwork.logical_types import Ordinal\n>>> ColumnSchema(logical_type=Ordinal)\n\n\n```\n\n#### Code Sample - Woodwork 0.4.0\n\n```python\n>>> from woodwork.column_schema import ColumnSchema\n>>> from woodwork.logical_types import Ordinal\n>>> ColumnSchema(logical_type=Ordinal)\nTraceback (most recent call last):\n File \"\", line 1, in \n File \"/Users/nate.parsons/dev/tmp/ordinal-test/env/lib/python3.8/site-packages/woodwork/column_schema.py\", line 35, in __init__\n logical_type = logical_type()\n File \"/Users/nate.parsons/dev/tmp/ordinal-test/env/lib/python3.8/site-packages/woodwork/logical_types.py\", line 369, in __init__\n raise TypeError(\"Must use an Ordinal instance with order values defined\")\nTypeError: Must use an Ordinal instance with order values defined\n\n```"} {"task_id": "format-code-task-000372", "source_id": "format-code-task-000372", "domain": "code", "task_path": "tasks/format-code-task-000372", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:099f26ba892c0485ec81ac4854f42b3bea820de7f54d85d8b5a6dbe99a06437f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n```\n>>> a = Const(1) - Const(2) \n>>> a.shape()\nunsigned(3)\n```\n\nThe correct result here (`-1`) is obviously not representable in an unsigned shape."} @@ -397,9 +385,6 @@ {"task_id": "format-code-task-000459", "source_id": "format-code-task-000459", "domain": "code", "task_path": "tasks/format-code-task-000459", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:79489c38b18f078c8535fe0274077da68d9fddb09b52ed01992b994b03e80009", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI need the public page lifecycle methods for an existing `Jbig2Ctx`: `int jbig2_complete_page(Jbig2Ctx *ctx)`, `Jbig2Image *jbig2_page_out(Jbig2Ctx *ctx)`, and `void jbig2_release_page(Jbig2Ctx *ctx, Jbig2Image *image)`. After I create a decoder context and feed enough JBIG2 data for a page, `jbig2_complete_page(ctx)` should mark the current decoded page as available and return 0. If the current page has no image buffer, `jbig2_complete_page(ctx)` should report a fatal error through the configured error callback and return -1. For streams whose final pending segment declares an unknown data length of `0xffffffff`, `jbig2_complete_page(ctx)` should warn, use the bytes already buffered as that segment body, parse it, advance the segment state, and return -1 with a warning if that parse fails.\n\nOnce a page is complete, `jbig2_page_out(ctx)` should return a referenced `Jbig2Image *` for the first available completed page, with the page pixel data, width, height, and stride preserved for the caller. If no completed page is available, `jbig2_page_out(ctx)` should return `NULL`. Calling `jbig2_page_out(ctx)` twice in a row should not return the same page twice unless another page has completed in between, because the first call hands that page to the caller. When I am done with a returned image, `jbig2_release_page(ctx, image)` should release the library's reference and mark that page as no longer held by the caller. Calling `jbig2_release_page(ctx, NULL)` should be a no-op, and passing an image pointer that did not come from that context's `jbig2_page_out` should report a warning through the error callback without crashing."} {"task_id": "format-code-task-000460", "source_id": "format-code-task-000460", "domain": "code", "task_path": "tasks/format-code-task-000460", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d15f2b579dca6fc525a85fbb08b133551ae4ed66bab3c89bb0b64ecdfa4d0316", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### Works tab is empty for artists that only have collections (no artist series)\n\nOn the artist page, the **Works** tab currently renders the artist series rail beneath the top works rail. For artists who don't have any artist series associated with them but who *do* belong to one or more collections, this section just shows up empty — the collections never appear on the Works tab at all.\n\nFor comparison, the **Overview** tab shows the collections rail correctly for these same artists. So the data is clearly available; it's just that the Works tab seems to assume every artist will have at least one artist series.\n\n#### Steps to reproduce\n1. Find an artist who is featured in at least one collection but has no artist series (we have a few of these in production).\n2. Navigate to `/artist//works`.\n3. Notice that nothing related to series or collections renders in that area — just the top works rail and the artwork filter below.\n4. Now navigate to `/artist/` (Overview). The collections show up fine.\n\n#### Expected\nOn the Works tab, when an artist has no artist series, we should fall back to showing their collections so the slot isn't wasted (and so users can still discover the artist via collections from this tab). When the artist *does* have artist series, behavior should stay as it is today — show the artist series rail.\n\nThe Overview tab should continue to behave as it currently does (collections only — no change there)."} {"task_id": "format-code-task-000461", "source_id": "format-code-task-000461", "domain": "code", "task_path": "tasks/format-code-task-000461", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2ba8c9e9fa131b12c46283e79de7dc104de020427039859e7ff43613714ee36d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want server-side `Meteor.SmartCollection` live queries to honor the `fields` option when a cursor is observed or published. The API shape is `var coll = new Meteor.SmartCollection(name, options); var cursor = coll.find(selector, {fields: projection}); cursor.observeChanges(callbacks);`, and the same projected output should flow through a cursor returned from `Meteor.publish`.\n\nFor an inclusion projection such as `{aa: 1, \"bb.c\": 1}`, when a matching document is `{_id: \"aa\", aa: 10, bb: {c: 10, k: 12}, cc: 20}`, the `added` callback should receive id `\"aa\"` and document `{_id: \"aa\", aa: 10, bb: {c: 10}}`. `_id` should be included by default for inclusion projections, but `{aa: 1, _id: 0}` should omit `_id` from the delivered document fields.\n\nFor an exclusion projection such as `{aa: 0, \"bb.c\": 0}`, when a matching document is `{_id: \"aa\", aa: 50, bb: {c: 45, k: 12}, cc: 20}`, the delivered document should be `{_id: \"aa\", bb: {k: 12}, cc: 20}`. The same projection rules should apply to later `changed` field maps, so with `{aa: 1}` a change map `{aa: 50, bb: 30}` should notify observers only with `{aa: 50}` and update the live-query cache only for that projected field.\n\nThe projection validator should reject unsupported field specs by throwing `Error`: field names containing `$` or values that are not numeric `0` or `1` are invalid, and mixing inclusion and exclusion in the same projection is invalid except for excluding `_id` alongside included fields."} -{"task_id": "format-code-task-000462", "source_id": "format-code-task-000462", "domain": "code", "task_path": "tasks/format-code-task-000462", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:81d00cf1b9eb1eb16b3b59c5f7b05514cb6cc62b1ac9a8635ca7431dbd9c9369", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the `asdf uninstall ` command to remove an installed runtime version for a plugin. When I run `asdf uninstall dummy 1.0.0` and that version is installed, the command should run any configured `pre_asdf_uninstall_dummy` hook with `1.0.0`, run the plugin's optional `uninstall` callback, delete that version's install directory, run any configured `post_asdf_uninstall_dummy` hook with `1.0.0`, then refresh shims so executables from the removed version are no longer advertised. The uninstall callback should receive `ASDF_INSTALL_TYPE`, `ASDF_INSTALL_VERSION`, and `ASDF_INSTALL_PATH`, and hook or callback stdout/stderr should pass through to the command output. For example, with uninstall hooks and a callback that prints `custom uninstall`, stdout should contain `pre_asdf_uninstall_dummy 1.0.0`, then `custom uninstall`, then `post_asdf_uninstall_dummy 1.0.0`, and the command should exit 0.\n\nIf either `` or `` is missing, `asdf uninstall` should print `No plugin given` on stderr and exit non-zero. If the requested version is `latest`, it should print `'latest' is a special version value that cannot be used for uninstall command` on stderr and exit non-zero. If the version is not installed, it should print `No such version` on stderr and exit non-zero. If config loading, a hook, the plugin callback, install-directory removal, or shim refresh fails, the command should print the underlying error to stderr and exit non-zero."} -{"task_id": "format-code-task-000463", "source_id": "format-code-task-000463", "domain": "code", "task_path": "tasks/format-code-task-000463", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:332021f84f2f999c3acd182ac371153e50cc38fe4df83d3b6a5e4a351f50598c", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `asdf shimversions ` to show which installed plugin versions provide a shimmed command. When I install versions such as `dummy 3.0` and `dummy 1.0`, run `asdf reshim dummy`, and then run `asdf shimversions dummy`, stdout should contain one provider line per recorded version in the format ` `, for example `dummy 3.0` and `dummy 1.0`, and the command should exit 0.\n\nIf I run `asdf shimversions` without a command name, it should print `usage: asdf shimversions ` to stderr and exit nonzero. If the asdf config cannot be loaded, it should report `error loading config: ` to stderr and fail nonzero. If the shim metadata for the requested command cannot be read, the command should fail nonzero without printing made-up provider lines."} -{"task_id": "format-code-task-000464", "source_id": "format-code-task-000464", "domain": "code", "task_path": "tasks/format-code-task-000464", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ebcbde0d4f0c8dc030eb41d89c6981e55364dc163859e0c5de9af82e626d987b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the `asdf set` command to update the version selection file used by future asdf resolution. The command should be invoked as `asdf set [ ...]`, should print nothing on stdout on success, and should exit with status 0 after writing the requested tool and versions.\n\nBy default, running `asdf set lua 5.2.3` in a directory with no version file should create `.tool-versions` in the current directory containing `lua 5.2.3` followed by a newline. If that file already contains `lua 1.1.1`, the command should replace that line with `lua 5.2.3`; if the file contains other tools, it should preserve those lines and append `lua 5.2.3` at the end. Inline comments on the replaced tool line and comment-only lines for unrelated content should be preserved, and multiple requested versions such as `asdf set python 3.12.1 3.11.8` should be written on one line after the tool name.\n\nThe command should support `--home`/`-u` to write the user home `.tool-versions` file instead of the current directory file, and `--parent`/`-p` to find and update the closest existing `.tool-versions` file in a parent directory. If both `--home` and `--parent` are supplied, it should fail with a non-zero exit and print `home and parent flags cannot both be specified; must be one location or the other` to stderr. If no arguments are supplied, it should fail non-zero and print `tool and version must be provided as arguments`; if only a tool is supplied, it should fail non-zero and print `version must be provided as an argument`. If `--parent` is supplied and no parent version file exists, it should fail non-zero and print `No .tool-versions version file found in parent directory` to stderr.\n\nVersion arguments may be literal versions, `ref:...`, `path:...`, `system`, `latest`, or `latest:`. For `latest` selectors, `asdf set` should resolve the selector for the named plugin first and write the resolved concrete version string to the version file; if the selector cannot be resolved, the command should fail non-zero instead of writing a `latest` token."} {"task_id": "format-code-task-000466", "source_id": "format-code-task-000466", "domain": "code", "task_path": "tasks/format-code-task-000466", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ebeef74b10197181a06e33111dd7176bb1d925e4a3a27d65f63c45cc8e2a8784", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nRewriting TypedDict can lead to SyntaxError\npyupgrade checks if the keys of a TypedDict are strings, but not if they are valid for usage in class syntax.\n\nHere's a minimal input:\n\n```python\nfrom typing_extensions import TypedDict\n\nMyDict = TypedDict(\"MyDict\", {\"my-key\": str, \"another key\": int})\n```\n\n\nThis is the rewrite produced by `pyupgrade --py36-plus minimal.py`:\n\n```python\nfrom typing_extensions import TypedDict\n\nclass MyDict(TypedDict):\n my-key: str\n another key: int\n```\n\nThe `-` and the space in the keys are invalid syntax."} {"task_id": "format-code-task-000467", "source_id": "format-code-task-000467", "domain": "code", "task_path": "tasks/format-code-task-000467", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:11f500124b54861d671d09a44e09c7bac172a608e18bc9190beaf26f49865779", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nFailing test case using pyupgrade 2.25.0:\n\n```\n$ echo 'a=b=c=None; print(\"Query:%8s %s %s\" % (a, b, c))' > test.py ; pyupgrade --py36-plus test.py ; cat test.py\nRewriting test.py\na=b=c=None; print(f\"Query:{a:>8} {b} {c}\")\n```\n\n```pycon\n>>> a=b=c=None; print(\"Query:%8s %s %s\" % (a, b, c))\nQuery: None None None\n>>> a=b=c=None; print(f\"Query:{a:>8} {b} {c}\")\nTraceback (most recent call last):\n File \"\", line 1, in \nTypeError: unsupported format string passed to NoneType.__format__\n```\n\nThe problem is while ``f\"{None}\"`` works, advanced string format arguments do not:\n\n```pycon\n>>> \"%8s\" % None\n' None'\n```\n\n```pycon\n>>> f\"{None:>8}\"\nTraceback (most recent call last):\n File \"\", line 1, in \nTypeError: unsupported format string passed to NoneType.__format__\n```\n\nPossible workaround:\n\n```python\n>>> a=b=c=None; print(f\"Query:{str(a):>8} {b} {c}\")\nQuery: None None None\n```\n\nThis issue was found in https://github.com/biopython/biopython/pull/3724"} {"task_id": "format-code-task-000468", "source_id": "format-code-task-000468", "domain": "code", "task_path": "tasks/format-code-task-000468", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a4edb3e7d4c93e07ef916cab41b38e29d5f3bd95061403e94a05003bdc2fe05f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `git-deps` to report dependency analysis results directly in the terminal when I run it with commit-ish arguments and no `--serve` or `--json` mode. For a single target commit such as `git-deps 4f27a1e^!`, stdout should contain one dependency SHA per line, without repeating the same dependency more than once for that target; in the git-deps repository this includes lines like `3374b8419a45d91d3c0631be11c8cf893b272217`, `3a1dd42fd6114a634ba7cf037ce61e2aee76db73`, and `b1967573e81a8100a4cc778936de0ba0a8a8f5cb`. If the target is the root commit, for example `git-deps b196757^!`, the command should exit successfully and produce no dependency lines. When I ask for multiple targets, either by passing multiple commit-ish arguments or by using a revision range that expands to more than one revision, each dependency line should be an edge formatted as ` `. The same edge format should be used with recursive reporting, so `git-deps -r 4f27a1e^!` should include lines such as `4f27a1ee2b5fd63a58311a20e2aed0a24eda8da2 3374b8419a45d91d3c0631be11c8cf893b272217` and recursive downstream edges like `3374b8419a45d91d3c0631be11c8cf893b272217 b1967573e81a8100a4cc778936de0ba0a8a8f5cb`. With `--log`, terminal reporting should print each newly discovered dependency as a `git log -n1` block using color-enabled git output; in multi-commit mode it should prefix each dependency with ` depends on:` and, if a dependency commit has already been shown, print `commit (already shown above)` instead of showing the full log block again. The happy path should exit 0 after all selected revisions are analyzed and their terminal output is written as discoveries are emitted."} @@ -410,13 +395,11 @@ {"task_id": "format-code-task-000475", "source_id": "format-code-task-000475", "domain": "code", "task_path": "tasks/format-code-task-000475", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2920f48ab8af81e1f84e8b339b3307087b66ff1b8db48d60e638366c865a28a1", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nWay to reset data-react-beautiful-dnd-draggable for server side rendering\n## Bug or feature request?\nBug\n\n### Expected behavior\n`data-react-beautiful-dnd-draggable` shouldn't increment based on how many times it was run on the server but start fresh for each request.\n\n### Actual behavior\nEach time the server render is hit `data-react-beautiful-dnd-draggable` is incremented by 1.\ni.e. after 6 reloads console throws:\n```\nWarning: Prop `data-react-beautiful-dnd-draggable` did not match. Server: \"6\" Client: \"0\"\n```\n\n### Steps to reproduce\nServer side render and reload couple times, each reload the `data-react-beautiful-dnd-draggable` gets incremented by 1.\n\n### Browser version\nChrome\n\nhttps://github.com/atlassian/react-beautiful-dnd/blob/master/src/view/style-marshal/style-marshal.js#L11\n\nPossible solution to this would be to expose a function that resets the counter that one could call during a server side render like so:\n```\nexport function resetCounter() {\n count = 0;\n}\n```"} {"task_id": "format-code-task-000476", "source_id": "format-code-task-000476", "domain": "code", "task_path": "tasks/format-code-task-000476", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:59ed31161ac1cadf700fa3e01d8bd2cfabe4c2da4634b6e81ace121472db4639", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `gosaic index [PATHS...]` with no `--clean`, `--list`, or `--rm` flag to populate the local image index from one or more file or directory paths. When I run `gosaic --dsn sqlite3:///tmp/gosaic.sqlite3 index ./tiles`, it should recursively discover regular `.jpg`, `.jpeg`, and `.png` files under `./tiles`, convert stored paths to absolute paths, print a line containing `Indexing N images...` where `N` is the number of discovered usable image paths, and exit with code 0 after inserting the records.\n\nEach indexed image should store the absolute path, MD5 content hash, width, height, EXIF orientation, and a reusable aspect-ratio record. JPEG EXIF orientation values 5 through 8 should swap the stored width and height, and missing or zero orientation should be treated as orientation 1. If two discovered files have the same MD5 hash, only the first should be inserted so later `gosaic index --list` output contains one path for that image content.\n\nRunning `gosaic index` without any paths and without stdin paths should fail with exit code 1 and print `Must specify paths to index`. If a supplied path cannot be walked or an individual image cannot be hashed, opened, or inspected, the command should print an error message naming that path and continue indexing the remaining discovered images when possible."} {"task_id": "format-code-task-000477", "source_id": "format-code-task-000477", "domain": "code", "task_path": "tasks/format-code-task-000477", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:8d45b77feb0a469c3eba227ac247353b8ec85a1821b2453f2cb1623a321659d6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Add support for `proof_of_possession` on resource servers\n\nI'm using auth0-deploy-cli to manage my tenant configuration as code. One of my APIs needs proof-of-possession (DPoP) enabled on the access tokens it issues — Auth0's Management API exposes a `proof_of_possession` setting on resource servers for exactly this.\n\nWhen I add `proof_of_possession` to the resource server entry in my YAML config and run an import, the deploy CLI doesn't recognize the field — the resource server schema only covers things like `enforce_policies`, `token_dialect`, scopes, etc.\n\nCould the resource server schema be extended so that `proof_of_possession` is a recognized, validated field? I'd like to manage this setting through the CLI alongside the other resource server properties instead of having to configure it out-of-band."} -{"task_id": "format-code-task-000478", "source_id": "format-code-task-000478", "domain": "code", "task_path": "tasks/format-code-task-000478", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6a8fdfa3bc606efb72eed8c5619dd37faaaefeef046bf27979b4d136aabab630", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI’m using the Java SDK’s ManagementAPI and I need to trigger Auth0’s verification email job from there, but right now I don’t see any Jobs API support so I have to hand-roll the HTTP call. It would be great if the SDK let me send a verification email for a user and get back a typed job response I can inspect, like the job id/status/type and creation time.\n\nExpected outcomes:\n- Management API callers can access Jobs support through `ManagementAPI.jobs()`, receiving a `JobsEntity` that exposes Jobs-related operations.\n- `JobsEntity.sendVerificationEmail(String userId, String clientId)` returns a `Request` for sending a verification email job for the given user.\n- Executing the verification email request sends a POST request to Auth0’s verification email job endpoint, includes the required `user_id` in the JSON request body, and includes `client_id` only when a non-empty client id is provided.\n- Calling the verification email operation without a user id is rejected by the SDK before sending a request.\n- The SDK provides `com.auth0.json.mgmt.jobs.Job` for the Jobs API response, with readable `getId()`, `getStatus()`, `getType()`, and `getCreatedAt()` values from the response JSON.\n- `Job` JSON handling ignores unknown response fields and does not serialize null fields.\n\nImplementation notes:\n- Follow the existing Management API entity and request patterns in the SDK.\n- The internal data structures, validation location, and JSON binding details are up to the implementation as long as the public SDK behavior above is satisfied.\n\n## Required output literals (exact-match contract)\n\nWhen executing Jobs Management API requests, the implementation MUST authenticate the HTTP request using the configured API token:\n\n- HTTP header name: `Authorization` - exact wire-level header required by the existing Management API request pattern.\n- HTTP header value: `Bearer ` followed by the configured API token - exact bearer-token prefix required for Auth0 Management API authentication.\n"} {"task_id": "format-code-task-000479", "source_id": "format-code-task-000479", "domain": "code", "task_path": "tasks/format-code-task-000479", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:16b1881b0ff31ee3fbdea57681e9ba3d023269259fc0cb5b619d1b589398efc4", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nTerms and Privacy checkbox not available with Passwordless mode of Lock\n**Issue:**\n\nCurrently when using passwordless signup we aren't able to get a checkbox with the `signUpTerms` text and the `mustAcceptTerms` keys set.\n\nThis is limited only to the `Auth0LockPasswordless` where as it seems to be working fine when using the database with username-password version of the lock.\n\nWe would like to be able to ensure this checkbox/notice display to be in compliance with GDPR and other privacy standards.\n\n- [x] Code snippet or sample project that reproduces the bug\n\n```js\n var clientID = \"XXXXXXXXXXXXXXXXXXXX\";\n var domain = \"freecodecamp.auth0.com\";\n\n var options = {\n languageDictionary: {\n title : \"freeCodeCamp.org\",\n signUpTerms: \"By choosing to continue you confirm that you have read and agreed to...\"\n },\n mustAcceptTerms: true,\n theme: {\n ...\n },\n ...\n socialBigButtons : true,\n passwordlessMethod: 'link',\n auth: {\n redirectUrl: 'http://localhost:3000/',\n responseType: 'token id_token',\n params: {\n scope: 'openid profile email'\n }\n },\n allowedConnections: [\n \"email\", \"google-oauth2\", \"facebook\", \"github\"\n ],\n };\n\n var lock = new Auth0LockPasswordless(clientID, domain, options);\n lock.show();\n```\n\n- [x] Screenshots when appropriate\n\n![image](https://user-images.githubusercontent.com/1884376/41974178-d7c3b1ce-7a34-11e8-8904-6b4496721a0a.png)\n\n\n- [x] Lock version\n\n```\n11.7.2\n```\n\n- [x] Browser & OS\n\n```\nNot relevant\n```\n\nMake sure to include **as much information as possible** for us to understand and reproduce the bug, that way we can fix it as quickly as possible."} {"task_id": "format-code-task-000480", "source_id": "format-code-task-000480", "domain": "code", "task_path": "tasks/format-code-task-000480", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:8a457012ce66ff7e1b5c5f8df943476ceac28ab249eab51be46754482878fb19", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### Version\n\n\nv4.38.2\n\n### Deployment Method\n\n\nDocker\n\n### Reverse Proxy\n\n\nTraefik\n\n### Reverse Proxy Version\n\n\n2.11.0\n\n### Description\n\n\nIn upgrading to 4.38 I changed my Traefik middleware to use the (default provided) `/api/authz/forward-auth` route. Then, I noticed requests to Home Assistant's `/api` were getting a 401 response, despite having valid (for Home Assistant) `Authorization` headers. The error comes from Authelia, even though the request should be bypassed.\n\n### Reproduction\n\n\nThis can be reproduced using something simple like `traefik/whoami`\n\nAn example docker-compose.yml:\n\n```yml\nservices:\n whoami:\n image: traefik/whoami\n labels:\n - traefik.enable=true\n - traefik.http.routers.${COMPOSE_PROJECT_NAME}-whoami.rule=Host(`whoami.${HOMELAB_BASE_DOMAIN}`)\n - traefik.http.routers.${COMPOSE_PROJECT_NAME}-whoami.entrypoints=web,websecure\n - traefik.http.routers.${COMPOSE_PROJECT_NAME}-whoami.middlewares=auth@file\n```\n\nwhere `auth@file` is this Traefik middleware:\n\n```yml\nhttp:\n middlewares:\n auth:\n forwardAuth:\n # Using the internal container + port\n address: http://authelia:9091/api/authz/forward-auth\n trustForwardHeader: true\n authResponseHeaders:\n - Authorization\n - Proxy-Authorization\n - Remote-User\n - Remote-Groups\n - Remote-Email\n - Remote-Name\n```\n\nand the `access_control` which should bypass Authelia:\n\n```yml\naccess_control:\n default_policy: one_factor\n\n rules:\n - domain: whoami.${HOMELAB_BASE_DOMAIN}\n policy: bypass\n```\n\nWith Authelia + Traefik + whoami running, now you can try curl:\n\n```sh\n# This works:\ncurl -L https://whoami.${HOMELAB_BASE_DOMAIN}/\n\n# This gets a 401 from Authelia:\ncurl -L -H 'Authorization: Bearer test' https://whoami.${HOMELAB_BASE_DOMAIN}/\n```\n\n### Expectations\n\n\nIdeally Authelia wouldn't be doing much when the requested route is bypassed.\n\n### Configuration (Authelia)\n\n\n```yaml\ntheme: auto\n\ntotp:\n issuer: auth.${HOMELAB_BASE_DOMAIN}\n\nauthentication_backend:\n password_reset:\n disable: true\n\n file:\n path: /config/users.yml\n\naccess_control:\n default_policy: one_factor\n #default_policy: two_factor\n\n rules:\n - domain: whoami.${HOMELAB_BASE_DOMAIN}\n policy: bypass\n\nsession:\n inactivity: '5m'\n expiration: '1h'\n remember_me: '1M'\n\n redis:\n host: redis\n\n cookies:\n - domain: ${HOMELAB_BASE_DOMAIN}\n authelia_url: https://auth.${HOMELAB_BASE_DOMAIN}\n default_redirection_url: https://dashboard.${HOMELAB_BASE_DOMAIN}\n\nstorage:\n local:\n path: /output/db.sqlite3\n\nnotifier:\n filesystem:\n filename: /output/notifications\n```\n\n\n### Build Information\n\n\n```shell\nLast Tag: v4.38.2\nState: tagged clean\nBranch: v4.38.2\nCommit: 573e79c8d34e118195731424df15d3e2c989495e\nBuild Number: 27687\nBuild OS: linux\nBuild Arch: amd64\nBuild Compiler: gc\nBuild Date: Sat, 16 Mar 2024 02:33:12 +1100\nExtra:\n\nGo:\n Version: go1.22.1\n Module Path: github.com/authelia/authelia/v4\n Executable Path: github.com/authelia/authelia/v4/cmd/authelia\n Settings:\n -buildmode: pie\n -compiler: gc\n -trimpath: true\n DefaultGODEBUG: httplaxcontentlength=1,httpmuxgo121=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1\n CGO_ENABLED: 1\n GOARCH: amd64\n GOOS: linux\n GOAMD64: v1\n vcs: git\n vcs.revision: 573e79c8d34e118195731424df15d3e2c989495e\n vcs.time: 2024-03-15T15:24:32Z\n vcs.modified: true\n Dependencies:\n authelia.com/provider/oauth2@v0.1.1 (h1:JHMWB8aieYW++7a+t3RIB0fkxcLMHyT7NUKPEAl6cls=)\n filippo.io/edwards25519@v1.1.0 (h1:FNf4tywRC1HmFuKW5xopWpigGjJKiJSV0Cqo0cJWDaA=)\n github.com/Azure/go-ntlmssp@v0.0.0-20221128193559-754e69321358 (h1:mFRzDkZVAjdal+s7s0MwaRv9igoPqLRdzOLzw/8Xvq8=)\n github.com/Gurpartap/logrus-stack@v0.0.0-20170710170904-89c00d8a28f4 (h1:vdT7QwBhJJEVNFMBNhRSFDRCB6O16T28VhvqRgqFyn8=)\n github.com/andybalholm/brotl"} {"task_id": "format-code-task-000481", "source_id": "format-code-task-000481", "domain": "code", "task_path": "tasks/format-code-task-000481", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:63da82f03953656b081811b19c1f942fe65bd6f2d20f4bf0f2fe301fbe43b248", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the `` element instance to expose an async `setAuthenticationConfiguration(securitySchemeId, { token, clientId, clientSecret, redirectUri })` method so host applications can configure credentials after a spec is loaded. The method should look up the loaded OpenAPI security scheme by `securitySchemeId` and reject by throwing `Error('SecuritySchemeNotFound')` when no matching scheme exists.\n\nWhen I call `await explorer.setAuthenticationConfiguration('bearerAuth', { token: 'abc123' })` for an HTTP bearer scheme, the matching scheme should store `Bearer abc123` as the applied credential, and a token that already starts with `Bearer ` should not get a duplicate prefix. When I call `await explorer.setAuthenticationConfiguration('basicAuth', { token: 'user:password' })` for an HTTP basic scheme, it should apply an `Authorization` value of `Basic ${btoa('user:password')}`.\n\nThe method should trim and save OAuth client configuration from the options object: `clientId`, `clientSecret`, and `redirectUri`. `redirectUri` should be resolved with `new URL(..., window.location.href).toString()`, so relative redirect paths become absolute URLs. After updating the scheme, the element should check the current page URL for an OAuth response, request a render update, and later executable requests for operations that require that security scheme should receive the applied credential through the existing request flow."} {"task_id": "format-code-task-000482", "source_id": "format-code-task-000482", "domain": "code", "task_path": "tasks/format-code-task-000482", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:8beb90f665967eca05459f8fd25efd258ce4f329b4ca36fc5faf7a9f8f7a5266", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Watch API on Postgres occasionally reports namespace modifications as deletions, corrupting the schema cache\n\nWe're running SpiceDB in production with Postgres as the datastore, and we have the experimental schema cache enabled (the one that's driven by the Watch API). After running for a while, we start seeing requests fail with errors like:\n\n```\nunknown namespace \"document\"\n```\n\n…even though the namespace is clearly still defined — `zed schema read` against the same cluster shows it's there. Restarting SpiceDB clears the cache and the errors go away, but they come back after some more schema activity.\n\nWhile digging into this we started subscribing to the Watch API directly to see what events were actually being emitted when our team edits the schema. What we observed is that **a plain modification to a namespace** (e.g. adding a new relation to an existing `document` namespace and writing the updated schema) sometimes shows up on the Watch stream as a **deletion event for that namespace**, instead of as a \"definition changed\" event. It's not consistent — the same kind of edit will sometimes correctly come through as \"changed\" and sometimes incorrectly come through as \"deleted\". We haven't been able to find a reliable repro on demand; it feels like a race / ordering thing inside SpiceDB.\n\nThis obviously breaks the schema cache: it sees the spurious deletion event, drops the namespace from its cache, and then subsequent permission checks against that namespace fail with \"unknown namespace\" until something else forces a refresh.\n\nA few extra data points:\n\n- We **only** see this on clusters using Postgres as the datastore. We have another cluster on CockroachDB and have never reproduced it there — Watch events for schema edits on CRDB always look correct.\n- The user never actually deleted the namespace. There is no `DeleteNamespace` / `WriteSchema`-with-namespace-removed in the audit log around the time of the bad event. The schema modification was a pure edit.\n- Because the cache is wrong, end users hit the failure even though the schema in the datastore is fine, which makes this pretty painful to operate around.\n\nExpected behavior: when a namespace (or caveat) is modified in a single transaction, the Watch API should consistently emit it as a definition change, regardless of which datastore backend is in use. It shouldn't sometimes look like a delete just because of how the underlying datastore happens to surface the update."} {"task_id": "format-code-task-000483", "source_id": "format-code-task-000483", "domain": "code", "task_path": "tasks/format-code-task-000483", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2cdd790eb163f5f2b4e2370a0e7bf601704fcfa1083f59e559e38edd2d8a4d3b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Remove the required column list from `Automerge.Table`\n\nWhen you create a table, you currently have to pass in a list of column names:\n\n```js\ndoc.authors = new Automerge.Table(['surname', 'forename'])\ndoc.publications = new Automerge.Table(['type', 'authors', 'title', 'publisher', 'edition', 'year'])\n```\n\nBut as far as I can tell, this list of columns isn't actually used for anything meaningful anymore. Since #236, you can no longer add a row by passing an array of values that gets mapped to column names — rows must already be objects with named properties. So the column list doesn't enforce a schema, doesn't validate row shapes, doesn't affect storage, and rows are free to omit some of the \"columns\" or include extra properties not in the list.\n\nIn other words, requiring this argument forces every user to write something that looks meaningful but isn't. It's confusing — new users reasonably assume the column list does something (enforces required fields, fixes a row shape, etc.) and then are surprised when it doesn't.\n\nI think we should just drop the column list from the `Table` API. Creating a table should look like:\n\n```js\ndoc.authors = new Automerge.Table()\ndoc.publications = new Automerge.Table()\n```\n\nRows continue to be plain objects, and by convention users should give rows in the same table the same set of properties, but Automerge doesn't (and currently can't) enforce that. The docs should be updated to reflect this — and to mention that not enforcing a schema is actually somewhat intentional, since different clients in a collaborative app may be running different versions and using slightly different property sets.\n\nIf/when proper schema support is added later, that can be designed properly. The current half-feature isn't getting us closer to that and just adds noise to the API.\n\nThoughts?"} -{"task_id": "format-code-task-000484", "source_id": "format-code-task-000484", "domain": "code", "task_path": "tasks/format-code-task-000484", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:fb821ab827128b73c0a1d9eca3bdba5d4a97a8e8e626b5e0ffb3ef7433ac1487", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## PI and LogEI acquisition functions crash when called\n\nI'm using RoBO for some Bayesian optimization experiments. The default `EI`\nacquisition function works fine, so I wanted to compare against `PI` and\n`LogEI` on the same problem.\n\nI set them up the same way I set up `EI` (same model, same `X_lower` /\n`X_upper`, same `compute_incumbent` for `LogEI`). The moment I evaluate\neither of them on a candidate point, it blows up somewhere inside the call —\nit never gets to return an acquisition value.\n\nRough sketch of what I'm doing:\n\n```python\n# this works fine\nei = EI(model, X_lower, X_upper, compute_incumbent)\nval = ei(X_test)\n\n# this dies\npi = PI(model, X_lower, X_upper)\nval_p = pi(X_test, incumbent)\n\n# this also dies\nlogei = LogEI(model, X_lower, X_upper, compute_incumbent)\nval_l = logei(X_test)\n```\n\nSince `EI` works on exactly the same model/bounds, I'd expect `PI` and\n`LogEI` to be usable as drop-in alternatives. Right now they aren't — only\n`EI` is actually callable.\n\nCould `PI` and `LogEI` be fixed so they also return a value the way `EI`\ndoes?"} {"task_id": "format-code-task-000485", "source_id": "format-code-task-000485", "domain": "code", "task_path": "tasks/format-code-task-000485", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:764601861619a8469d21a8c01e31beeaa87f54d651573173743fb496e519c836", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `autopkg run` and `autopkg install` to support a check-only mode with `-c` or `--check`, as in `autopkg run --check Firefox.download.recipe` or `autopkg install -c Firefox`. In this mode, after the recipe is found and composed, AutoPkg should shorten that recipe's processor list so execution stops at the final `EndOfCheckPhase` processor and does not run processors that appear after it. A successful check run should then continue through the normal recipe processing path for the remaining steps, print the usual `Processing ...` progress line, and complete with the normal successful exit status when no recipe fails.\n\nIf a recipe passed to `autopkg run --check` or `autopkg install --check` does not contain an `EndOfCheckPhase` processor, AutoPkg should not process that recipe. It should write `Recipe at is missing EndOfCheckPhase Processor, not possible to perform check.` to stderr, count that recipe as failed, continue with any remaining recipes, and exit with the recipe-failure status when the run finishes. The short `-c` flag and long `--check` flag should be accepted anywhere the run/install option parser accepts other options, and command help for run/install should list the option as only checking for new or changed downloads."} {"task_id": "format-code-task-000486", "source_id": "format-code-task-000486", "domain": "code", "task_path": "tasks/format-code-task-000486", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3f322a5265875bf313513285e08c8974b0e26eedb4d8906352a2616715468212", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the `autopkg` CLI to provide a recipe repository listing command. When I run `autopkg repo-list`, it should read the configured `RECIPE_REPOS` preference and print each installed repository as one line in the format ` ()`, sorted by repository path, followed by a blank line. The alias `autopkg list-repos` should behave the same way.\n\nFor example, if `RECIPE_REPOS` contains `/Users/me/Library/AutoPkg/RecipeRepos/com.github.autopkg.recipes` with URL `https://github.com/autopkg/recipes` and `/tmp/custom-recipes` with URL `https://github.com/example/custom-recipes`, stdout should list `/tmp/custom-recipes (https://github.com/example/custom-recipes)` before `/Users/me/Library/AutoPkg/RecipeRepos/com.github.autopkg.recipes (https://github.com/autopkg/recipes)` and then emit the trailing blank line. If there are no configured recipe repositories, stdout should be exactly `No recipe repos.` followed by a newline. The command should accept the common `--prefs ` option so I can point it at a specific preferences file before listing repositories. `autopkg repo-list --help` should show `Usage: autopkg repo-list` and describe that it lists all installed recipe repos, exiting successfully. Top-level `autopkg help` should include both `repo-list` with help text `List installed recipe repos` and `list-repos` with help text `see repo-list`."} {"task_id": "format-code-task-000487", "source_id": "format-code-task-000487", "domain": "code", "task_path": "tasks/format-code-task-000487", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c3b36138a90bcc9264d7b82014818f9cc3b59faf05b9319f17a76c63f19ae651", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `ToIPDesc` can't parse IPv6 addresses\n\nI'm trying to use `utils.ToIPDesc` with IPv6 peer addresses and it doesn't work. For example:\n\n```go\ndesc, err := utils.ToIPDesc(\"::1:9651\")\n// err != nil -> \"bad ip format\"\n```\n\nAny IPv6 address goes through this path because `ToIPDesc` looks like it just splits the input on `:` and expects exactly two parts, which is fine for `127.0.0.1:9651` but obviously falls apart the moment the host itself contains colons.\n\nThe reverse direction has the same problem. If I build an `IPDesc` with an IPv6 `net.IP` and call `String()` on it, I get something like\n\n```\n::1:9651\n```\n\nwhich is ambiguous — you can't tell where the address ends and the port begins, and feeding it back into `ToIPDesc` won't round-trip.\n\nIPv4 still needs to keep working as before (`127.0.0.1:9651` etc.), but `ToIPDesc` / `IPDesc.String()` should handle IPv6 in an unambiguous way so nodes can actually be addressed over v6."} @@ -440,7 +423,6 @@ {"task_id": "format-code-task-000506", "source_id": "format-code-task-000506", "domain": "code", "task_path": "tasks/format-code-task-000506", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:57dd433c8733ea9c329ccde22313cb078692f624015fdb2c7cf746fff68aa7a3", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### s3manager.Upload API shape — align with upcoming Download manager\n\nI'm working on adding a download manager to `s3manager` (counterpart to the existing upload manager). While sketching the API I realized the two are going to look inconsistent if I leave Upload as-is.\n\nToday, uploading looks like this:\n\n```go\nsvc := s3.New(nil)\nresp, err := s3manager.Upload(svc, &s3manager.UploadInput{...}, nil)\n```\n\ni.e. `Upload` is a package-level function that takes the `*s3.S3` client, the input, and an options struct as positional arguments. The download manager I'm building really wants to be a reusable object — you configure it once (concurrency, part size, which S3 client to use) and then call it many times against different inputs. Forcing the same shape on Upload would mean every call site has to re-pass the client and the opts, and the two managers would read very differently side by side even though they're conceptually symmetric.\n\nI'd like to reshape Upload along the same lines: configure once, then call `Upload` on the configured object as many times as you want, ideally safe to share across goroutines. The S3 client should be part of that one-time configuration rather than a required positional argument on every call — and it'd be nice if it were optional, so simple use cases (`just upload this file with defaults`) don't have to construct an `s3.S3` themselves.\n\nI'm fine with this being a breaking change for Upload callers — better to do it now, before the download manager ships and locks in the asymmetry, than to introduce two differently-shaped APIs and try to reconcile them later.\n\nThe existing knobs in `UploadOptions` (PartSize, Concurrency, LeavePartsOnError) and the zero-value-means-default behavior should keep working the way they do now; this is purely about the call shape, not about changing what the upload itself does.\n\nNaming-wise I'd expect something like `s3manager.NewUploader(opts)` returning the reusable object, with the S3 client living on `UploadOptions` (e.g. an `S3` field)."} {"task_id": "format-code-task-000507", "source_id": "format-code-task-000507", "domain": "code", "task_path": "tasks/format-code-task-000507", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b7f81f544c89ba5534fd89fe768a0fb2ce3ce4e75ab51a6c2ec9880f3c1aaf21", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nCloudFront Sign creates invalid signature if URL contains &\nConfirm by changing [ ] to [x] below to ensure that it's a bug:\n- [x] I've gone though the [API reference](https://docs.aws.amazon.com/sdk-for-go/v2/api/)\n- [x] I've checked [AWS Forums](https://forums.aws.amazon.com) and [StackOverflow](https://stackoverflow.com/questions/tagged/aws-sdk-go) for answers\n- [x] I've searched for [previous similar issues](https://github.com/aws/aws-sdk-go-v2/issues) and didn't find any solution\n \n**Describe the bug**\nAfter switching from the V1 SDK to the V2 SDK, signing a URL with more than 2 query parameters results in an invalid signature and cloudfront will return a 403. For a url with 1 or less query parameters, the V1 SDK and V2 SDK signatures are identical. But if you have a URL with more than 2 query parameters, the V2 SDK will return a different signature than the V1 SDK. This looks like a regression from the v1 SDK - an issue was raised and fixed in V1 but it looks like the fix is not included in the v2 SDK https://github.com/aws/aws-sdk-go/issues/2163\n\n**Version of AWS SDK for Go?**\n1.40.18\n\n**Version of Go (`go version`)?**\ngo1.16.4 darwin/amd64\n\n**To Reproduce (observed behavior)**\nCode example copied from this issue: https://github.com/aws/aws-sdk-go/issues/2163\n```\nsigner := sign.NewURLSigner(keyID, privKey)\nsignedURL, _ := signer.Sign(\"https://myuploaddomain.com/\", time.Now().Add(1*time.Hour))\n// signedURL VALID\nsignedURL, _ := signer.Sign(\"https://myuploaddomain.com?key=one\", time.Now().Add(1*time.Hour))\n// signedURL VALID\nsignedURL, _ := signer.Sign(\"https://myuploaddomain.com?key=one&value=two\", time.Now().Add(1*time.Hour))\n// signedURL INVALID returns AccessDenied when uploading\n\n```\n\n**Expected behavior**\nSigning a URL containing two query string parameters should result in the same signature as the V1 SDK."} {"task_id": "format-code-task-000508", "source_id": "format-code-task-000508", "domain": "code", "task_path": "tasks/format-code-task-000508", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d9c24cfff152526a0afe208aac603afbc4354e6599a6b9482ecec536170951b0", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `pipeline init` defaults the CodeCommit branch to `master`, but new CodeCommit repos use `main`\n\nI'm trying to set up a Copilot pipeline that's triggered from an AWS CodeCommit repository. My repo is fairly new — when I created it in CodeCommit, the default branch was `main` (which I believe is the current default for new CodeCommit repos).\n\nI ran `copilot pipeline init` from my workspace, picked my CodeCommit repo URL when prompted, and accepted the default branch (i.e. I didn't pass `--git-branch`). When I looked at the generated pipeline manifest, the source branch was set to `master`. After deploying the pipeline, the Source stage points at a branch that doesn't exist in my repo, so the pipeline can't actually pull anything or get triggered by pushes.\n\nIf I explicitly pass the branch name it works fine, so this is just about what the default should be when CodeCommit is the source.\n\nLooking at the docs page for the pipeline manifest, it also says:\n\n> The name of the branch in your repository that triggers the pipeline. The default for GitHub is `main`; the default for Bitbucket and CodeCommit is `master`.\n\nSo at least for the CodeCommit half of that sentence, the documented default doesn't match what new CodeCommit repos actually use. It would be great if the CodeCommit default in `pipeline init` (and the corresponding docs) were updated to match what users actually get out of CodeCommit today, so things \"just work\" without having to override the branch every time."} -{"task_id": "format-code-task-000509", "source_id": "format-code-task-000509", "domain": "code", "task_path": "tasks/format-code-task-000509", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:52260dbf6f30f2882c284d45ce43b058dce076a8981232866c0347d04306bcaa", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want a manifest interpolation API in the Go `manifest` package that can be used as `manifest.NewInterpolator(appName string, envName string).Interpolate(input string) (string, error)`. The interpolator should parse the input as YAML, substitute `${VAR}` placeholders only in YAML string values, and return the resulting YAML text with normal YAML formatting.\n\n`COPILOT_APPLICATION_NAME` and `COPILOT_ENVIRONMENT_NAME` should be predefined from the constructor arguments. For example, with `manifest.NewInterpolator(\"myApp\", \"test\")`, interpolating `image: repo/${COPILOT_ENVIRONMENT_NAME}:${TAG}` with OS environment variable `TAG=latest` should return YAML containing `image: repo/test:latest`. With `SECURITY_GROUPS=[\"sg-1\",\"sg-2\"]`, interpolating `network:\\n vpc:\\n security_groups: ${SECURITY_GROUPS}` should turn that string value into a YAML sequence containing `sg-1` and `sg-2` rather than leaving it as a JSON-looking string.\n\nEscaped placeholders should remain literal after removing the escape slash: interpolating `command: echo \\\\${NAME}` should produce YAML containing `command: echo ${NAME}` and should not require `NAME` to be set. If a placeholder refers to an unset OS environment variable, `Interpolate` should return an error like `environment variable \"NAME\" is not defined`. If the OS environment tries to override a predefined Copilot variable with a different value, such as setting `COPILOT_ENVIRONMENT_NAME=prod` while the interpolator was created with env name `test`, `Interpolate` should return an error saying that predefined variable cannot be overridden.\n\nCalling `Interpolate` multiple times with the same constructor arguments, input YAML, and OS environment should produce the same output and should not mutate the input string or write to the filesystem or network."} {"task_id": "format-code-task-000510", "source_id": "format-code-task-000510", "domain": "code", "task_path": "tasks/format-code-task-000510", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:089291d614c7fd8e0f366fdd263de251f451b4837542ae2e973903ce6ec62c76", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nOption to apply user classnames\nIt would be a very nice feature to allow us to set our own class names on the resulting iframe. Right now it is hardcoded to a static value:\nhttps://github.com/awslabs/amazon-quicksight-embedding-sdk/blob/79bdce13d916ed906d22c198720ca13a42fdb0bd/src/EmbeddableDashboard.js#L139\n\nMaybe something like this?\n```js\n QuickSightEmbedding.embedDashboard({\n url,\n container,\n scrolling: 'no',\n height: 'AutoFit',\n loadingHeight: '400px',\n className: 'my-apps-classname', // <-----\n }).on('error', this.handleError);\n```\n\nFor example, this could be used to apply bootstrap class names to the iframe itself to change the border or shadow, without having to duplicate framework features in custom css."} {"task_id": "format-code-task-000511", "source_id": "format-code-task-000511", "domain": "code", "task_path": "tasks/format-code-task-000511", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:5e230782492aaf01ebdc2ea329d75fef97f12150f69fc84d75919a632d0828d6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI'm looking for an ability to disable the metric extraction and ingestion into CloudWatch Metrics, while still logging them to CloudWatch Logs.\n\nThat ability is important for me as I want to be able to disable ingestion into CloudWatch Metrics on demand for cost saving purposes while still receiving the data in CloudWatch Logs enabling me to analytics with CloudWatch Insights, even though they aren't ingested into CloudWatch Metrics.\n\nFrom reading through the EMF specification (https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Embedded_Metric_Format_Specification.html) I didn't notice any flag to indicate if metrics should be ingested into CloudWatch Metrics or not. \n\nIs there an option to choose whether such metrics should get ingested by CloudWatch Metrics or not? If not it'd be great to have such an option.\n\nI'd expect this to be exposed as a config option, something like `Config.disable_metric_extraction` (with a matching `AWS_EMF_DISABLE_METRIC_EXTRACTION` environment variable)."} {"task_id": "format-code-task-000512", "source_id": "format-code-task-000512", "domain": "code", "task_path": "tasks/format-code-task-000512", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:8195534dfe750a0bcf79a00a0aeb5a5a1d3eeefd6718acac14cdfcd9e23bac76", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want an `ExpectedNumInstanceSampler` available from `gluonts.transform` for training pipelines that need roughly a target number of split points per time series. I should be able to construct it with keyword fields `num_instances: float`, `min_instances: int = 0`, `axis: int = -1`, `min_past: int = 0`, and `min_future: int = 0`, then call it as `sampler(ts: np.ndarray) -> np.ndarray` to get integer split indices.\n\nFor each successful call, it should compute the inclusive valid split interval from `min_past` through `ts.shape[axis] - min_future`; if that interval is empty, it returns an empty integer array and does not advance its running counters. Otherwise, the sampler should keep state across calls by incrementing `n` and adding the current valid window size to `total_length`, then use `num_instances / (total_length / n)` as the per-index sampling probability.\n\nFor a concrete deterministic case, with `sampler = ExpectedNumInstanceSampler(num_instances=2, min_past=1, min_future=1)`, `ts = np.zeros(5)`, and `np.random.random_sample(4)` producing `[0.9, 0.2, 0.8, 0.1]`, calling `sampler(ts)` should return `np.array([2, 4])`, because the valid split indices are `[1, 2, 3, 4]` and the probability is `2 / 4`. With `sampler = ExpectedNumInstanceSampler(num_instances=1, min_instances=2)`, `ts = np.zeros(3)`, `np.random.random_sample(4)` producing values above the sampling probability for every position, and `np.random.randint(0, 4, size=2)` producing `[3, 1]`, the call should return `np.array([3, 1])` so that the requested minimum number of instances is still met. With `ExpectedNumInstanceSampler(num_instances=4, min_past=3, min_future=2)(np.zeros(4))`, the result should be an empty integer array because there is no valid split interval."} @@ -469,7 +451,6 @@ {"task_id": "format-code-task-000537", "source_id": "format-code-task-000537", "domain": "code", "task_path": "tasks/format-code-task-000537", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:cd3f666bd2a0b07e613a9c17cc1f867367b82d325b46e3280c861f0b709c5373", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want an installed command named `ntsynt_merge_collinear.py` for post-processing an existing ntSynt synteny block TSV. It should be invoked as `ntsynt_merge_collinear.py --tsv blocks.tsv [--indel N] [--merge N]`, with `--indel` defaulting to 50000 bp and `--merge` defaulting to 1000000 bp. The input is tab-separated rows with at least these columns: block ID, assembly, contig, start, end, strand; extra columns such as minimizer count and prior break reason may be present but should not control the merge.\n\nThe command should group rows by block ID, use the first assembly encountered in the file as the reference assembly, sort blocks by that reference assembly's contig and start coordinate, and then compare each adjacent block pair across every assembly. Adjacent blocks should merge only when every assembly stays on the same contig, every assembly keeps the same strand, all orientation-aware gaps are non-negative, the spread between the largest and smallest gap is at most `--indel`, and the largest gap is less than `--merge`. For `+` strand blocks the gap is `next.start - current.end` and merging extends the current end to the next end; for `-` strand blocks the gap is `current.start - next.end` and merging extends the current start to the next start.\n\nFor example, given `--indel 10 --merge 100` and an input file containing `0\tasmA\tchr1\t100\t200\t+\t7\tNone`, `0\tasmB\tchr7\t500\t600\t+\t7\tNone`, `1\tasmA\tchr1\t220\t300\t+\t4\tNone`, and `1\tasmB\tchr7\t625\t705\t+\t4\tNone`, stdout should be exactly two rows: `0\tasmA\tchr1\t100\t300\t+\t0\tNone` and `0\tasmB\tchr7\t500\t705\t+\t0\tNone`, with exit code 0. Output block IDs should be renumbered from 0, the minimizer-count column should be `0`, and the final column should be `None` for the first output block or the recomputed discontinuity reason for later blocks. When a pair does not merge, the next block's reason should be `id_change`, `ori_change`, `inconsistent_order`, `indel`, or `merge`, chosen in that priority order.\n\nIf an input row has fewer than six tab-separated columns, the command should fail with a non-zero exit and report an error mentioning the expected minimum column count. If `--tsv` is omitted, argparse-style usage should be written to stderr and the exit code should be 2. `--help` should print usage to stdout, include `--tsv`, `--indel`, and `--merge`, and exit 0."} {"task_id": "format-code-task-000538", "source_id": "format-code-task-000538", "domain": "code", "task_path": "tasks/format-code-task-000538", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ad76cffccf21f602b2b335d164fd2bfcb9418c1521853b7ec08bb6571a373d71", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nIs a template is must in v1.6?\n\nI use c.Ctx.Output.Body() direct write reponse , it works in beego v1.5 . \n\n```\nc.Ctx.Output.Header(\"Content-Type\", \"application/xml; charset=utf-8\")\nc.Ctx.Output.Body(response)\n```\n\nBut wrong in beego v1.6\n\n```\n2016/02/09 21:50:55 [router.go:854][C] Handler crashed with error can't find templatefile in the path:maincontroller/get.tpl \n2016/02/09 21:50:55 [router.go:860][C] /usr/local/go/src/runtime/asm_amd64.s:437 \n2016/02/09 21:50:55 [router.go:860][C] /usr/local/go/src/runtime/panic.go:423 \n2016/02/09 21:50:55 [router.go:860][C] /Users/brian/dev/go/src/github.com/astaxie/beego/controller.go:262 \n2016/02/09 21:50:55 [router.go:860][C] /Users/brian/dev/go/src/github.com/astaxie/beego/controller.go:183 \n2016/02/09 21:50:55 [router.go:860][C] /Users/brian/dev/go/src/github.com/astaxie/beego/router.go:784 \n2016/02/09 21:50:55 [router.go:860][C] /usr/local/go/src/net/http/server.go:1862 \n2016/02/09 21:50:55 [router.go:860][C] /usr/local/go/src/net/http/server.go:1361 \n2016/02/09 21:50:55 [router.go:860][C] /usr/local/go/src/runtime/asm_amd64.s:1721 \n```"} {"task_id": "format-code-task-000539", "source_id": "format-code-task-000539", "domain": "code", "task_path": "tasks/format-code-task-000539", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:0ccb2c50bd474a5b0155b55d488c2d50d788e4358badad438f12eae3a8c164cf", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want Beego sessions to support reading the session ID from the request URL query string when I explicitly enable that behavior. The public option should be `session.CfgEnableSidInURLQuery(enable bool) session.ManagerConfigOpt`, and `session.ManagerConfig` should also expose an `EnableSidInURLQuery bool` JSON-configurable field so callers can configure it directly.\n\nFor a concrete flow, I should be able to create a manager with `cfg := session.NewManagerConfig(session.CfgCookieName(\"sid\"), session.CfgEnableSidInURLQuery(true))`, then `mgr, err := session.NewManager(\"memory\", cfg)`. If I already have a memory session with ID `abc123` containing `\"user\" = \"alice\"`, then calling `mgr.SessionStart(w, r)` for a request with no session cookie and URL `/?sid=abc123` should return that same store, so `store.SessionID(ctx)` is `\"abc123\"` and `store.Get(ctx, \"user\")` is `\"alice\"`. If there is no matching existing session for the query value, `SessionStart` should create a fresh session ID through the configured provider instead of treating the query value as valid.\n\nWhen URL-query lookup is enabled and parsing the request form fails, `SessionStart` should return that parse error and no session store. When URL-query lookup is disabled, a `?sid=...` value should be ignored and the normal cookie/header/new-session behavior should apply. Beego's web session configuration should also have `SessionEnableSidInURLQuery bool`; when automatic session registration builds the session manager from `BConfig.WebConfig.Session`, that setting should populate the manager's URL-query lookup option."} -{"task_id": "format-code-task-000540", "source_id": "format-code-task-000540", "domain": "code", "task_path": "tasks/format-code-task-000540", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3ab03632ea65de70a9a92e5f6f39960236b13618214d320664244b7d833d87cf", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## NoneType binary/comparison ops don't match CPython behavior\n\nI've been running some Python snippets through Batavia and noticed a bunch of operations involving `None` behave differently from CPython 3.\n\n### Comparisons\n\nIn CPython 3, ordering comparisons against `None` raise `TypeError`:\n\n```python\n>>> None < 1\nTypeError: unorderable types: NoneType() < int()\n>>> None <= 1\nTypeError: ...\n>>> None > 1\nTypeError: ...\n>>> None >= 1\nTypeError: ...\n```\n\nIn Batavia, these just return `False` silently, so code that's supposed to blow up keeps running and produces wrong results downstream. Only `==` / `!=` should work against `None` (and they do — that part's fine).\n\n### Bitwise operators\n\n```python\n>>> None & 1\n>>> None ^ 1\n>>> None | 1\n```\n\nIn CPython these raise `TypeError` (\"unsupported operand type(s) for ...\") like the other unsupported binary ops on `None`. In Batavia I get a `NotImplementedError` saying the dunder hasn't been implemented yet, which makes it look like Batavia is incomplete rather than the user's code being wrong.\n\n### Subscripting\n\n```python\n>>> None[0]\n```\n\nCPython says `'NoneType' object is not subscriptable`. Batavia phrases this as if it were a binary operand mismatch (\"unsupported operand type(s) for []: ...\"), which doesn't match and is misleading — subscripting isn't a binary op.\n\n### `pow` / `**`\n\n```python\n>>> None ** 2\n```\n\nCPython's message mentions both `**` and `pow()` in the unsupported-operand text. Batavia's message only mentions `pow`, so anyone using the `**` operator and grepping for it in the error won't find anything.\n\nCould the `None` dunder methods be aligned with CPython here? The other binary ops on `None` (`+`, `-`, `*`, `/`, `//`, `%`, `<<`, `>>`) already raise `TypeError` with CPython-shaped messages, so this is just filling in the remaining cases consistently."} {"task_id": "format-code-task-000541", "source_id": "format-code-task-000541", "domain": "code", "task_path": "tasks/format-code-task-000541", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:bc5b384a50ec344f05aaf1041ada4e26de55975a8f09d9fcd05baf963ef21cf7", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Add lifecycle event handlers to `toga.Window`\n\nRight now a `Window` only lets you respond to one lifecycle event, `on_close`.\nApplications frequently need to react to a window changing its focus or\nvisibility — for example, pausing background work when a window is hidden, or\nrefreshing data when it comes back to the foreground.\n\nAdd four new optional event handlers to `toga.Window`:\n\n- `on_gain_focus` — the window became the application's current (focused) window.\n- `on_lose_focus` — the window stopped being the application's current window.\n- `on_show` — the window became visible.\n- `on_hide` — the window stopped being visible.\n\n## Expected behavior\n\n- Each handler must be available **both** as a keyword argument to the `Window`\n constructor **and** as a readable/writable property, in exactly the same way\n the existing `on_close` handler works. Assigning a new callable to the\n property replaces the handler.\n- When a handler has not been provided, reading the property must still return a\n callable (a no-op), consistent with how an unset `on_close` behaves.\n- Whenever a handler fires, it is invoked with the window instance it belongs\n to.\n\nThe handlers fire in response to the following observable state changes:\n\n- **Visibility.** When a window transitions from not-visible to visible, its\n `on_show` handler fires; when it transitions from visible to not-visible, its\n `on_hide` handler fires. This applies whether visibility is changed through\n `show()`/`hide()` or through the `visible` property. A request that does not\n actually change the visibility (e.g. showing an already-visible window) must\n not fire either handler.\n- **Minimize / restore.** Moving a visible window into the minimized state fires\n its `on_hide` handler; restoring it from the minimized state back to a visible\n state fires its `on_show` handler. Switching between other window states does\n not fire these handlers, and a state request that leaves the state unchanged\n fires nothing.\n- **Focus.** When the application's current window changes from one window to a\n different window, the window that was current has its `on_lose_focus` handler\n fired, and the window that becomes current has its `on_gain_focus` handler\n fired. Setting the current window to the window that is already current fires\n neither handler.\n\nAdding these handlers should not disturb the existing `on_close` behavior.\n"} {"task_id": "format-code-task-000542", "source_id": "format-code-task-000542", "domain": "code", "task_path": "tasks/format-code-task-000542", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:145bb5aa75f56562829a474f0659f8eabd8da08da72a17bf784435baf31b0a06", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Make `tuple` support the standard operators\n\nRight now Python tuples that get transpiled to the JVM can be created, indexed,\nsliced and iterated, but almost every operator on them is dead — using one\ncurrently blows up with a \"not implemented\" error instead of behaving like\nCPython. Please make tuples support the usual operator protocol so that\ntranspiled code behaves exactly the way it does under CPython 3.5.\n\nConcretely, a tuple should support:\n\n* **Rich comparisons** (`<`, `<=`, `>`, `>=`, `==`, `!=`) against another\n tuple, using Python's lexicographic ordering: compare element by element, and\n at the first position where the two tuples differ the result is decided by\n comparing those two elements; if one tuple is a prefix of the other, the\n shorter one is the smaller. Equality is element-wise and length-sensitive.\n * `==` and `!=` must also work when the other operand is **not** a tuple:\n a tuple is never equal to a non-tuple, so `==` is `False` and `!=` is\n `True` (no error).\n * The ordering comparisons (`<`, `<=`, `>`, `>=`) against a non-tuple operand\n must raise `TypeError`, matching CPython's message for unorderable types.\n\n* **Concatenation** with `+`: `tuple + tuple` produces a new tuple with the\n elements of the left followed by the elements of the right. Adding anything\n that is not a tuple raises `TypeError` with CPython's message.\n\n* **Repetition** with `*`: `tuple * n` for an integer `n` produces a new tuple\n with the elements repeated `n` times (`n` of zero or less yields an empty\n tuple); a boolean counts as `0`/`1`. Multiplying by something that is not an\n integer raises `TypeError` with CPython's message.\n\n* **Truthiness**: an empty tuple is falsy and a non-empty tuple is truthy, so it\n behaves correctly in boolean contexts (`if`, `while`, `not ...`).\n\n* **Unary operators**: `+`, `-` and `~` are not valid on tuples and must raise\n `TypeError` with CPython's message for a bad unary operand.\n\nThe observable contract is simply that each of these operations produces output\n(including raised exceptions and their messages) identical to CPython 3.5 for\nthe same source. Existing tuple behaviour (creation, `repr`, indexing, slicing,\niteration) must keep working.\n"} {"task_id": "format-code-task-000543", "source_id": "format-code-task-000543", "domain": "code", "task_path": "tasks/format-code-task-000543", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1c4104700166d460756bfa58aa7d1bb56eb8446f34f6426140795c1ea6610f66", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Floor division and modulo for floats\n\nVOC transpiles Python to Java by providing a runtime implementation of Python's\nbuilt-in types. Right now the `float` type is missing two arithmetic operators:\nfloor division (`//`) and modulo (`%`). Any program that uses them on a float\ncurrently blows up instead of computing a result.\n\nPlease implement both operators on `float` so they behave exactly like CPython.\n\nThe left operand is a `float`; the right operand may be an `int`, a `float`, or a\n`bool`. Concretely:\n\n- `a // b` returns a `float` equal to the floor of the true division `a / b`\n (e.g. `9.9 // 2.0` is `4.0`, `-9.9 // 2.0` is `-5.0`).\n- `a % b` returns a `float`. The result follows Python's convention that the\n modulo takes the **sign of the divisor**: `5.5 % -2` is `-0.5`, `-5.5 % 2` is\n `0.5`. When the remainder is exactly zero, the result is a signed zero whose\n sign matches the divisor, so `-7.0 % 7.0` is `0.0` while `7.0 % -7.0` and\n `0.0 % -3` are `-0.0`.\n- A `bool` right operand acts like the integer `1` (`True`) or `0` (`False`).\n\nEdge cases that must match CPython:\n\n- Dividing or taking the modulo by a zero divisor (whether `0`, `0.0`, or\n `False`) raises `ZeroDivisionError`. Floor division by zero reports\n `float divmod()`; modulo by zero reports `float modulo`.\n- Applying either operator with an unsupported right-hand type raises\n `TypeError` with the message\n `unsupported operand type(s) for //: 'float' and ''` (and the\n analogous message with `%` for modulo), where `` is the offending\n operand's type name.\n\nBoth the global scope and inside-a-function scope must produce identical results,\nmatching what CPython prints for the same source.\n"} @@ -525,13 +506,11 @@ {"task_id": "format-code-task-000598", "source_id": "format-code-task-000598", "domain": "code", "task_path": "tasks/format-code-task-000598", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ba5bae953b729cd03c67afcc83a9e25f6eb3940b0e2ab9f09cc2d0f89359be9d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### Custom notify / sessions endpoints set via environment variables are ignored\n\nI'm running bugsnag-go against our self-hosted (on-premise) Bugsnag deployment and configuring everything through environment variables (we don't want internal URLs baked into the Go binary). My env looks like:\n\n```\nBUGSNAG_API_KEY=...\nBUGSNAG_NOTIFY_ENDPOINT=https://errors.bugsnag.internal.example\nBUGSNAG_SESSIONS_ENDPOINT=https://sessions.bugsnag.internal.example\n```\n\nand in code I just do:\n\n```go\nbugsnag.Configure(bugsnag.Configuration{\n ReleaseStage: \"production\",\n AppVersion: buildVersion,\n // intentionally NOT setting Endpoints in code -\n // I want them to come from the env vars above\n})\n```\n\nI'd expect error reports and session data to be POSTed to my internal hosts. Instead, nothing shows up on our internal Bugsnag dashboard. When I look at outbound traffic from the app, the notifier is actually calling the public SaaS endpoints (`notify.bugsnag.com` / `sessions.bugsnag.com`) — my env-var values appear to have no effect at all.\n\nAs a workaround, if I read the env vars myself and stuff them onto the `Endpoints` field of `Configuration`:\n\n```go\nbugsnag.Configure(bugsnag.Configuration{\n Endpoints: bugsnag.Endpoints{\n Notify: os.Getenv(\"BUGSNAG_NOTIFY_ENDPOINT\"),\n Sessions: os.Getenv(\"BUGSNAG_SESSIONS_ENDPOINT\"),\n },\n ReleaseStage: \"production\",\n AppVersion: buildVersion,\n})\n```\n\nthen everything works correctly — events arrive at the right place. So configuring via the `Configuration` struct directly is fine; it's specifically the \"endpoints configured *only* through environment variables\" path that doesn't take effect.\n\nSince `BUGSNAG_NOTIFY_ENDPOINT` / `BUGSNAG_SESSIONS_ENDPOINT` are documented as a supported configuration channel, I'd expect setting them in the env to behave the same as setting `Endpoints` in code — including in the common case where the app only calls `Configure` with non-endpoint options (release stage, app version, etc.) and leaves the `Endpoints` field zero-valued."} {"task_id": "format-code-task-000599", "source_id": "format-code-task-000599", "domain": "code", "task_path": "tasks/format-code-task-000599", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:660fbccbb3e98f75f3344d0b948fdf263e278d2d49e468ede8f117d3c1ca747a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Allow hooks to skip checkout by clearing `BUILDKITE_REPO`\n\n### Use case\n\nWe have a few buildkite pipelines that don't actually need source code—things like deployment jobs, maintenance tasks that hit external APIs, jobs that just orchestrate other jobs, etc. For those, doing a full git clone is pointless and just slows things down.\n\nWhat I'd like to do is decide in a hook (typically `environment`) whether the job needs source for this particular run, and if not, skip checkout entirely. The most natural way to express that is from the hook itself, e.g. something like:\n\n```bash\n# .buildkite/hooks/environment\nif [[ \"$BUILDKITE_PIPELINE_SLUG\" == \"deploy-prod\" ]]; then\n export BUILDKITE_REPO=\"\"\nfi\n```\n\n### What actually happens\n\nClearing or unsetting `BUILDKITE_REPO` from a hook doesn't skip checkout—the agent still goes into the checkout phase and tries to clone, which then fails (since there's no repo URL to clone from) and the whole job errors out before the command phase ever runs.\n\n### What I'd expect\n\nIf `BUILDKITE_REPO` ends up empty by the time the checkout phase starts, the agent should just skip checkout and continue on to run the command. The command still needs somewhere reasonable to execute from, so the working directory should be set up sensibly even when nothing was checked out (and ideally cleaned up afterwards so we don't leak directories on the agent host across many such jobs).\n\nThis would let people opt individual jobs out of checkout from a hook, without having to maintain a separate agent / queue / pipeline config for \"no-checkout\" jobs."} {"task_id": "format-code-task-000600", "source_id": "format-code-task-000600", "domain": "code", "task_path": "tasks/format-code-task-000600", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:9f81f9cabab7980e142b54d32a7f915ccf200e2f4528f366bd0b3afec02d999d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nI switch between a few different builders depending on the project I'm working on, and right now there's no easy way to manage my default builder from the `pack config` command. I'd love to be able to check what my current default builder is, set a new one, and clear it out when I don't want a default anymore — all through `pack config`. Ideally when I set one it'd make sure the builder actually exists first so I don't end up with a bogus default. Also, I keep typo-ing `pack config trusted-builders` as `trust-builder`, so it'd be nice if those just worked too.\n\n## Expected Outcomes\n\n- `pack config default-builder` reports the saved default builder when one exists, and reports that none is set with guidance toward suggested builders when it does not.\n- `pack config default-builder ` only saves a builder after confirming it can be found; if it cannot be found, the command fails clearly and leaves the previous default unchanged.\n- `pack config default-builder --unset` and `pack config default-builder -u` clear a saved default builder, or report that there was nothing to clear.\n- `pack config trust-builder` and `pack config trust-builders` behave as aliases for the existing `pack config trusted-builders` command, including its subcommands.\n\n## Implementation Notes\n\nKeep the behavior observable through the CLI and persisted pack configuration. Preserve existing `pack config` behavior while adding the new default-builder management flow and trusted-builder aliases; command wiring, validation placement, helper names, and internal data organization are up to the implementation."} -{"task_id": "format-code-task-000601", "source_id": "format-code-task-000601", "domain": "code", "task_path": "tasks/format-code-task-000601", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:82addb509c36014eb750472393765187bfb4b28b3929912f0608495e1f4f5864", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI'm using react-window with React.memo to wrap my row component, but my items are re-rendering on every scroll even when their data hasn't changed. Could you provide a built-in comparison helper I can drop into React.memo, and ideally something equivalent for class-based item components too, so my memoized rows actually skip these pointless re-renders?\n\n# Expected outcomes\n\n- Functional item renderers can import a top-level `areEqual` helper from `react-window` and use it as a `React.memo` comparison function.\n- The functional helper skips updates when item renderer props are unchanged in shallow terms, including the rendered positioning/style values, even if wrapper objects are recreated between renders.\n- The functional helper allows updates when any shallow style/positioning value or any other shallow prop value actually changes.\n- Class-based item renderers can import a top-level `shouldComponentUpdate` helper from `react-window` and use it as an instance update check.\n- The class helper skips updates when props are unchanged by the helper’s item-prop comparison and state is shallowly unchanged.\n- The class helper allows updates when item props differ or when state shallowly differs.\n\n# Implementation notes\n\n- The helpers should be optional utilities and should not change the default rendering behavior of existing list or grid components.\n- The exact internal organization, helper functions, file layout, and reuse between helpers are up to the implementation.\n- Comparisons should remain shallow; deep equality is not required."} {"task_id": "format-code-task-000602", "source_id": "format-code-task-000602", "domain": "code", "task_path": "tasks/format-code-task-000602", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4895c1afebc31cc609e368e1108d09f5d23006505ca6b58f2d73e2fe39200a1d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Feature request: per-call field overrides for `FakeData`\n\nI'm using `faker` to populate structs in unit tests. Most of the time the default tag-based generation is exactly what I want, but I keep running into two cases where I need finer control on a **per-call** basis:\n\n1. **Some fields shouldn't be randomized at all.** Typical example is a primary-key-ish field that I want to leave at its zero value (or set myself afterwards), or a field whose zero value carries semantic meaning for the test. Today `FakeData` fills every exported field, so I end up zeroing them out again right after the call, which is noisy.\n\n2. **A specific field needs a value from a constrained set.** For example a `Status` field that must be one of a handful of valid enum strings, or an `Age` that must satisfy some test-specific invariant. The `oneof` tag covers some of this, but I don't want to bake test-only constraints into the struct tags of my production types. I'd like to supply a generator function for that one field, just for this call.\n\nWhat I'd like is something roughly like:\n\n```go\ntype User struct {\n ID int64\n Name string\n Status string\n}\n\nvar u User\nerr := faker.FakeData(&u, /* tell faker to skip ID and to use my fn for Status */)\n```\n\n…where the \"skip these fields\" list and the \"use this function for that field\" mapping are passed in at the call site, so they don't leak into the struct definition and don't affect other tests / other calls to `FakeData`.\n\n### Why not the existing extension points?\n\n- `AddProvider` / `RemoveProvider` register a provider against a **tag name**, globally. That means I'd have to (a) put a custom tag on my struct field and (b) mutate global state in tests, which is ugly and racy when tests run in parallel.\n- Struct tags like `faker:\"-\"` work, but again they live on the type, not on the call. I don't always want that field skipped — only in this particular test.\n\n### Expected behavior\n\n- A way to pass, at call time, a set of field names that `FakeData` should leave alone (no randomization, original/zero value preserved).\n- A way to pass, at call time, a mapping from field name to a user-supplied function that produces the value for that field. If the function returns an error, `FakeData` should surface it rather than silently swallowing it.\n- Existing call sites (`faker.FakeData(&x)` with no extra arguments) should keep working unchanged.\n\nHappy to help review if someone picks this up.\n\nThe shape I have in mind is something like `faker.FakeData(&u, faker.WithFieldsToIgnore(\"ID\"), faker.WithCustomFieldProvider(\"Status\", myStatusFn))`."} {"task_id": "format-code-task-000603", "source_id": "format-code-task-000603", "domain": "code", "task_path": "tasks/format-code-task-000603", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d5940439fc5b60e87c95b029b6db8f869543a416dfdcf1ab9721be1a8427946c", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the zkSync and Scroll chain adapters to each expose `getTransactions(address: string): Promise` so wallet analysis can fetch a complete transaction-history array for a single address in one async call.\n\nFor zkSync, `getTransactions('0xabc')` should call `https://block-explorer-api.mainnet.zksync.io/api` with account `txlist` requests using `address: '0xabc'`, `startblock` beginning at `0`, `endblock: 99999999999999`, `sort: 'asc'`, and `offset: 1000`. If the first mocked explorer response has `status: 200`, `data.status: '1'`, and `data.result` containing one transaction object `txA`, the promise should resolve to `[txA]`. If a page contains exactly 1000 transactions, the next request should use the last transaction's `blockNumber` as the new `startblock`, and the resolved array should concatenate the pages in fetch order until a page shorter than 1000 is returned.\n\nFor Scroll, `getTransactions('0xdef')` should first page through `https://api.scrollscan.com/api` account `txlist` responses with the same `startblock`, `endblock`, `sort`, and `offset` behavior. After the normal transaction pages finish, it should also page through account `txlistinternal` responses for the same address. If the normal result is `[normalTx]` and the internal result contains one transaction with the same `hash`, the resolved array should remain `[normalTx]`. If the internal result contains a different `hash`, the resolved array should append a transaction-shaped object copied from the internal transaction for `contractAddress`, `from`, `gas`, `gasUsed`, `hash`, `input`, `isError`, `timeStamp`, `to`, `value`, and `blockNumber`, while filling unsupported normal-transaction fields with zero, empty string, or an empty `transfers` array.\n\nWhen an explorer response has `data.status: '0'`, the function should log `Error occurred while retrieving transactions:` with the explorer message and resolve with the transactions accumulated so far. When an HTTP request throws, it should log `Error occurred while making the request:` with the thrown error, stop paging, and resolve with the transactions accumulated so far."} {"task_id": "format-code-task-000604", "source_id": "format-code-task-000604", "domain": "code", "task_path": "tasks/format-code-task-000604", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:7fe528cadca74b2509795b9743a1ab7daa563f17e290975e8bb080f6a8929e17", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nI'm running into a weird issue with `useModel`: when I do `setState((state) => { state.count += 1 })`, the model state ends up as `undefined`, and when I do `setState({ count: 5 })` my other fields like `name` disappear. I also noticed an action middleware that calls `action()` around this setter seems to trigger my updater logic more than once. I'm hitting this while moving code from `4.0.x` to `4.1.x`, and the README doesn't really show how the old `Model`/registry/`useStore` setup maps to the new `createStore` style.\n\n## Expected Outcomes\n\n- `useModel` setters created inside `createStore` should support function updaters that mutate the provided state object without returning a value; the mutation should be reflected in the store and the state should not become `undefined`.\n- When the current model state is an object and the setter receives an object, the update should behave like a shallow partial update: changed keys are updated and unrelated existing keys remain available.\n- Action middleware that invokes the setter action should observe the completed setter result for function updaters without causing the updater callback to execute more than once for a single setter call.\n- The README FAQ should include a migration guide for moving from `4.0.x` to `4.1.x`, covering the shift from the old `Model`/registry/`useStore` pattern to the `createStore`-based pattern.\n\n## Implementation Notes\n\n- Preserve the existing public `createStore`, `useModel`, middleware, and store usage style while adjusting the observable setter behavior.\n- The exact internal state-update mechanism, validation location, and documentation wording are up to the implementation as long as the public behavior and migration guidance are clear."} {"task_id": "format-code-task-000605", "source_id": "format-code-task-000605", "domain": "code", "task_path": "tasks/format-code-task-000605", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:fed618bbd6f26aed02080a0a085b1d5c741cc41cd4f0f6734120a48ac4c6c5c5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Add a filesystem-backed metadata key/value store\n\nOur data-join components persist their metadata through a small key/value\ninterface (the existing etcd and MySQL clients in `fedlearner.common` are\nexamples). We now need to be able to keep that metadata on a distributed\nfilesystem (HDFS or an NFS mount) instead of a database, so deployments that\nalready have shared storage don't have to stand up a separate KV service.\n\nAdd a new client, importable as\n\n```python\nfrom fedlearner.common.dfs_client import DFSClient\n```\n\n`DFSClient(base_dir)` is constructed with a base directory under which all\nmetadata lives, and it must expose the same key/value surface the other\nclients already provide:\n\n- `set_data(key, data)` — store `data` (`bytes` or `str`) under `key`,\n creating any intermediate directories as needed. Returns a truthy value on\n success. Storing an existing key overwrites its value.\n- `get_data(key)` — return the stored value **as `bytes`**, or `None` if the\n key was never set (values stored as `str` come back as `bytes`).\n- `delete(key)` — remove the value stored at `key`. Afterwards `get_data(key)`\n is `None`.\n- `delete_prefix(key)` — recursively remove everything stored at or below\n `key`. Returns a truthy value when something was removed and a falsy value\n when there was nothing to delete.\n- `cas(key, old_data, new_data)` — atomic compare-and-swap. Compare the\n currently stored value against `old_data` **by textual content** (so a\n value previously stored as `b'x'` matches an expected `'x'` and vice\n versa); if they match, write `new_data` and return a truthy value, otherwise\n leave the value untouched and return a falsy value. Comparing against a key\n that has never been set succeeds only when `old_data` is `None`, in which\n case the key is created.\n- `get_prefix_kvs(prefix, ignore_prefix=False)` — return a list of\n `(key, value)` pairs, both `bytes`, for every key stored at or below\n `prefix`, sorted in ascending key order. The returned keys are relative to\n the client's base directory. When `ignore_prefix` is `True`, the pair for\n the exact `prefix` key itself is excluded. An unknown prefix yields an empty\n list.\n\nKeys use `/` as a separator and form a hierarchy: the **same** key may both\nhold a value and serve as the prefix of other, nested keys (e.g. `foo` can\nhold a value while `foo/a` and `foo/b` hold their own values), and\n`get_prefix_kvs('foo')` then returns the value at `foo` followed by the values\nat `foo/a` and `foo/b`.\n\nBecause the data lives on a shared filesystem under the base directory, the\nstore is not in-process state: a freshly constructed `DFSClient` pointed at the\nsame base directory must observe everything a previous client wrote there.\n\n"} {"task_id": "format-code-task-000606", "source_id": "format-code-task-000606", "domain": "code", "task_path": "tasks/format-code-task-000606", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:45e2be47f8bd4a9400a29e1e12344ac920dc9038397650b8fbbc62cda92416a4", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Some paragraphs fail to render with \"unexpected type of element while serializing a paragraph\"\n\nI'm using libasciidoc to render some `.adoc` files to HTML. On certain documents (regular-looking paragraphs, nothing fancy), the conversion bails out instead of producing output. The error I get bubbles up from the substitution stage:\n\n```\nunexpected type of element while serializing a paragraph: '[]interface {}'\n```\n\nSo the serializer for a paragraph is rejecting a line because it's not a `RawLine`, but apparently the lines that make it down to `serializeParagraph` aren't always raw — sometimes a line shows up as `[]interface{}` (presumably a line that already went through some other processing step / contains nested elements). When that happens, the whole paragraph never gets reparsed, and the document errors out.\n\nThis should just work — a paragraph whose lines have been turned into nested element slices is still a valid paragraph, and the serializer should be able to flatten it back to its textual form so the normal-paragraph substitution can reparse it like any other paragraph. It shouldn't be an error condition.\n\nCould the paragraph serialization be made to handle that case (and ideally any reasonable nesting of raw lines inside it) instead of refusing?"} -{"task_id": "format-code-task-000607", "source_id": "format-code-task-000607", "domain": "code", "task_path": "tasks/format-code-task-000607", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4f33d287c6284088c946f79499d022fdf89ed4ab3c583fdcfede9bc213781a36", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `devcockpit cleanup list` to be a direct CLI command that reports how much space is used by common developer cache directories under my home directory, without launching the interactive TUI. When I run `devcockpit cleanup list`, it should exit 0 on a successful scan and print a cache-size table to stdout headed `Dev Cockpit — Cache Sizes`, with `CACHE` and `SIZE` columns, one row per existing cache location, a separator line, and a final `Total` row that sums the listed sizes.\n\nOn Linux, the command should check these home-relative locations: `.cache`, `.npm/_cacache`, `.cache/yarn`, `go/pkg/mod/cache`, `.cache/pip`, `.gradle/caches`, `.m2/repository`, and `.docker`, using labels like `User Cache`, `npm Cache`, `Yarn Cache`, `Go Module Cache`, `pip Cache`, `Gradle Cache`, `Maven Cache`, and `Docker Data`. On macOS, it should check `Library/Caches/Homebrew`, `.npm/_cacache`, `Library/Caches/Yarn`, `go/pkg/mod/cache`, `Library/Caches/pip`, `Library/Caches/CocoaPods`, `Library/Developer/Xcode/DerivedData`, `.gradle/caches`, `.m2/repository`, and `Library/Containers/com.docker.docker/Data`, using labels like `Homebrew Cache`, `npm Cache`, `Yarn Cache`, `Go Module Cache`, `pip Cache`, `CocoaPods Cache`, `Xcode DerivedData`, `Gradle Cache`, `Maven Cache`, and `Docker Temp`.\n\nDirectories that do not exist should be skipped rather than printed as errors. Existing directories should be measured with `du -sk` using a short timeout; if measuring a directory fails, that row should still be included with a zero size instead of failing the whole command. Sizes should be human readable as `B`, `KB`, `MB`, or `GB` with one decimal for KB and above, and rows over 1 GB should be visually warned while rows over 5 GB should be visually critical in the terminal styling.\n\nIf the home directory cannot be determined, the command should print `Error: Cannot determine home directory` to stderr and exit 1. The global `devcockpit --help` output should list `devcockpit cleanup list` as the cache-size command and include it in the examples, and disk/storage diagnostics should suggest `devcockpit cleanup list` when low disk space or large caches are detected."} {"task_id": "format-code-task-000609", "source_id": "format-code-task-000609", "domain": "code", "task_path": "tasks/format-code-task-000609", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4304d919d7761a95524bf4cbffbbb999878c4527a767707c7872709ea798233c", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### What can be improved?\n\nBeing able to load tabular data is a wonderful new feature.\nBut it is currently limited by forcing the data to 'match' calliope's dimension names in certain cases. Enforcing strict naming by default makes a lot of sense: you avoid ambiguity and you also avoid the risks of relying on column position.\n\nHowever, it will often be too inflexible.\n\n## Reasoning\n\nSome of our names might lead to files being less human readable, or finicky: \n- if a model is national resolution, `nodes` is less informative than `country`\n- people will often go for `technology` or `tech` instead of `techs`, since it can be intuitive to name columns in singular\n- people might prefer `time` or `utc_timestamp`, over `timesteps`...\n\nThis will lead to a lot of 'boilerplate' code that just shapes the data to fit Calliope's naming. See the following 3 examples for different names used for timeseries in Euro Calliope with v6.10:\n\n![image](https://github.com/user-attachments/assets/d3e2f638-3a36-4005-81da-781653cd9f7e)\n![image](https://github.com/user-attachments/assets/73b95df4-59f0-42a3-b9b8-c9e8c4c64833)\n![image](https://github.com/user-attachments/assets/fed11440-0a8b-425b-88a0-345ba2a49edc)\n\nAll 3 are equally 'human' readable, but since they do not specify `timesteps`, they won't load into Calliope.\n\n# Proposal\n\nAn option to use mappings would solve this issue.\nFor example, you could load one of the timeseries above this way:\n\n```\ndata_sources:\n demand_elec_timeseries:\n source: timeseries/demand/electricity.csv\n columns: nodes\n rows: {timesteps: time}\n add_dims:\n techs: demand_elec\n parameters: sink_use_equals\n```\n\nThis is still strict, but more flexible.\n\n### Version\n\nv0.7.0.dev3\n\n---\n\nA new top-level data-source option (something like `rename_dims`) that takes a `{old_name: new_name}` mapping would be a natural fit here."} {"task_id": "format-code-task-000610", "source_id": "format-code-task-000610", "domain": "code", "task_path": "tasks/format-code-task-000610", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:5267bf1468d6b32827664c1bd28290d4715d3f111ee5f83f641f1fb8ce7386d6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `fontVariant` style on `TextInput` is ignored\n\nI'm using `TextInput` from react-native-paper and trying to apply a `fontVariant` (e.g. `small-caps` for a username field, or `tabular-nums` for an amount field). It works fine on a plain RN `` but has no visible effect when I apply it through paper's `TextInput`.\n\n```tsx\nimport { TextInput } from 'react-native-paper';\n\n\n```\n\nThe text inside the input renders with the default glyphs as if `fontVariant` wasn't set at all. Other text style props on the same `style` object (like `fontSize` and `fontWeight`) do come through correctly, so it seems specific to `fontVariant`.\n\nThis happens with both `mode=\"flat\"` and `mode=\"outlined\"`, on both iOS and Android.\n\nIt would be great if `TextInput` respected `fontVariant` from `style` the same way it already respects the other font-related text styles."} {"task_id": "format-code-task-000611", "source_id": "format-code-task-000611", "domain": "code", "task_path": "tasks/format-code-task-000611", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d30b21ec218a00710f664265f264373473536fd7e4dcf32327d8deeb9721a661", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## README map-reduce example doesn't run\n\nJust trying communist out for the first time — looks great for what I want to do (crunch some numbers across a few workers). I copy-pasted the map-reduce example straight from the README:\n\n```js\nvar worker = communist(4);\n//pass it the number of map workers\nworker.data([1,2,3]);\nworker.map(function(x){return x*x;});\nworker.reduce(function(a,b){return a+b;});\nworker.data([4,5,6]);\nworker.fetch().then(function(a){console.log(a)});\n// README says this should print 91\nworker.data([6,7,8]).fetch().then(function(a){console.log(a)});\n// and this should print 240\nworker.close().then(function(a){console.log(a)});\n// and this should print 389\n```\n\nWhen I run this, it blows up on the `worker.fetch()` line — the object I get back from `communist(4)` doesn't seem to have a `fetch` (or a `close`). I only get `.data`, `.map`, `.reduce` on it. So none of the lines after the initial three setup calls actually work.\n\nIs the README out of date, or is `communist(N)` supposed to give back the object the README describes (the one with `data` / `map` / `reduce` / `fetch` / `close`, where you can keep feeding it data and ask for results whenever)? That's the workflow I'm after — incrementally pushing chunks in, occasionally fetching the running result, and closing manually when I'm done."} @@ -569,7 +548,6 @@ {"task_id": "format-code-task-000651", "source_id": "format-code-task-000651", "domain": "code", "task_path": "tasks/format-code-task-000651", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4a68d1fa88e76f6c13b79d282666a416956456bc52c41c5dbf11d6d0cf5f6384", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n`Variable.__repr__` raises error when underlying data is not initialized\nIn v2, the following code raises an error.\n\n```\nIn [1]: import chainer\nIn [2]: a = chainer.Variable()\nIn [4]: a.data is None\nOut[4]: True\nIn [5]: repr(a)\n---------------------------------------------------------------------------\nAttributeError Traceback (most recent call last)\n in ()\n----> 1 repr(a)\n\n/Users/oonokenta/dev/chainer/chainer/variable.py in __repr__(self)\n 305 \n 306 def __repr__(self):\n--> 307 return variable_repr(self)\n 308 \n 309 def __str__(self):\n\n/Users/oonokenta/dev/chainer/chainer/variable.py in variable_repr(var)\n 75 prefix = 'variable'\n 76 \n---> 77 if arr.size > 0 or arr.shape == (0,):\n 78 lst = numpy.array2string(arr, None, None, None, ', ', prefix + '(')\n 79 else: # show zero-length shape unless it is (0,)\n\nAttributeError: 'NoneType' object has no attribute 'size'\n```\n\nIt is because `variable_repr(var)` assumes that `var.data` is not `None`."} {"task_id": "format-code-task-000652", "source_id": "format-code-task-000652", "domain": "code", "task_path": "tasks/format-code-task-000652", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:690c88cdc41331417fdd3af8778ea3618ee66dd9b9cc86a7a0bab06966c966a0", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nZeroDivisionError in softmax_cross_entropy when I pass masked array\n- Chainer version: `origin/master`\n - CuPy version: `2.0.0b1`\n - OS/Platform: `Ubuntu 14.04`\n - CUDA/cuDNN version: `CUDA-8.0.61-1/cudnn5.1.5-1`\n\n## Problem\n\nWhen I mask two arrays and calculate `softmax_cross_entroy`, `ZeroDivisionError` occurs when masked array's data is `[]`\nI thought it should be checked in ndim and shape check at the beginning of the function, but the array's shape was something like `(0, 2, 2)`\n\n## Reproduction\n\n```python\nimport chainer\nimport cupy\nimport numpy as np\n\n\ndata = np.random.random((10, 2, 2))\nt = cupy.ones((data.shape[0], data.shape[2]), dtype=cupy.int32)\nx = chainer.Variable(data)\nx.to_gpu()\nmask = t[:, 0] == 0\nx_masked = x[mask]\nprint('=================')\nprint('x_masked')\nprint(' data: {}'.format(x_masked.data))\nprint(' shape: {}'.format(x_masked.shape))\nprint('=================')\nt_masked = t[mask]\nprint('=================')\nprint('t_masked')\nprint(' data: {}'.format(t_masked))\nprint(' shape: {}'.format(t_masked.shape))\nprint('=================')\nchainer.functions.softmax_cross_entropy(x_masked, t_masked)\n```\n* Shape\n```\n=================\nx_masked\n data: []\n shape: (0, 2, 2)\n=================\n=================\nt_masked\n data: []\n shape: (0, 2)\n=================\n```\n* Error\n```bash\nTraceback (most recent call last):\n File \"spam.py\", line 25, in \n chainer.functions.softmax_cross_entropy(x_masked, t_masked)\n File \"/home/shingo/chainer/chainer/functions/loss/softmax_cross_entropy.py\", line 275, in softmax_cross_entropy\n normalize, cache_score, class_weight, ignore_label, reduce)(x, t)\n File \"/home/shingo/chainer/chainer/function.py\", line 212, in __call__\n ret = node.apply(inputs)\n File \"/home/shingo/chainer/chainer/function_node.py\", line 219, in apply\n outputs = self.forward(in_data)\n File \"/home/shingo/chainer/chainer/function.py\", line 117, in forward\n return self._function.forward(inputs)\n File \"/home/shingo/chainer/chainer/function.py\", line 319, in forward\n return self.forward_gpu(inputs)\n File \"/home/shingo/chainer/chainer/functions/loss/softmax_cross_entropy.py\", line 102, in forward_gpu\n log_y = log_softmax._log_softmax(x)\n File \"/home/shingo/chainer/chainer/functions/activation/log_softmax.py\", line 36, in _log_softmax\n x.reshape(x.shape[:2] + (-1, 1)))\n File \"cupy/core/core.pyx\", line 461, in cupy.core.core.ndarray.reshape (cupy/core/core.cpp:11315)\n File \"cupy/core/core.pyx\", line 434, in cupy.core.core.ndarray._reshape (cupy/core/core.cpp:10994)\n File \"cupy/core/internal.pyx\", line 139, in cupy.core.internal.infer_unknown_dimension (cupy/core/internal.cpp:3060)\nZeroDivisionError: integer division or modulo by zero\n```"} {"task_id": "format-code-task-000654", "source_id": "format-code-task-000654", "domain": "code", "task_path": "tasks/format-code-task-000654", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:fc6c1564e982587a5bbfb8380b42711764b6152d924a8af2e53602e7574c1b3f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nI'm hitting an issue with `chainercv.transforms.resize` on CHW grayscale images: when I pass a NumPy array shaped like `(1, H, W)`, the result seems to get squeezed into 2D or sometimes errors out. In my no-`cv2` setup I also noticed non-RGB inputs behave oddly, like a 1-channel image failing and extra channels disappearing.\n\n## Expected outcomes\n\n- Grayscale CHW inputs passed to `chainercv.transforms.resize` should resize successfully and preserve their single channel dimension, returning an array shaped `(1, new_H, new_W)`.\n- When `chainercv.transforms.resize` runs without `cv2` available, non-RGB CHW inputs should resize according to their actual number of channels rather than assuming exactly three channels.\n- The resized output should preserve the input channel count for both fewer-than-three-channel and more-than-three-channel inputs in the no-`cv2` fallback path.\n- Resizing should operate on the image data in the preserved channels rather than replacing valid non-constant input with a constant placeholder.\n- Existing RGB CHW resize behavior should continue to return the expected channel-first shape.\n\n## Implementation notes\n\n- The implementation may choose any appropriate internal handling for channel order, backend-specific image resizing behavior, and per-channel processing, as long as the public resize behavior above is satisfied.\n- Keep the public API behavior centered on `chainercv.transforms.resize`; no particular private helper structure or internal code organization is required."} -{"task_id": "format-code-task-000655", "source_id": "format-code-task-000655", "domain": "code", "task_path": "tasks/format-code-task-000655", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:73f5c9fc3bf815afa9a8c353a73eae8c62a3c9224bcab3e5d5076348df65c369", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nI'm seeing weird samples when I train DQN/DDPG with batched environments and replay: n-step sequences and episodic replay entries sometimes contain transitions from different parallel envs stitched together. It also looks like when one batch item hits done/reset, the replay state for the other still-running envs gets disturbed. This shows up with interleaved env steps where sampled trajectories have state/action markers from multiple envs.\n\n## Expected outcomes\n\n- Sampled n-step replay sequences never combine transitions from different parallel environment sources, including when environment steps are interleaved.\n- Calling `stop_current_episode(env_id=...)` ends only the replay trajectory for that environment and does not flush, clear, or mix trajectories from other environments.\n- Stored and sampled episodic replay entries never combine transitions from different parallel environment sources, including when episodes are completed or interrupted in a different order than their steps were observed.\n- In DQN/DDPG batch training with replay, each batch position is handled as a distinct replay environment identity, and a done/reset flag for one batch position does not disturb the replay trajectory for other batch positions.\n- `ReplayBuffer.append` accepts additional keyword fields and preserves them in stored experiences so they can be observed after sampling.\n\n## Implementation notes\n\nThe exact internal data structures, storage layout, and validation locations are up to the implementation. Preserve existing single-environment behavior by treating omitted environment identity as the default environment.\n\n## Required public API surface (mechanical binding)\n\nThe following names / signatures MUST be implemented exactly as listed; downstream test harness mechanically binds these:\n\n- `ReplayBuffer.append(..., env_id=..., **kwargs)` and equivalent concrete replay-buffer append methods - tests must pass a named public environment identity to create multiple replay streams through the buffer API, while still verifying arbitrary extra keyword fields are stored.\n"} {"task_id": "format-code-task-000656", "source_id": "format-code-task-000656", "domain": "code", "task_path": "tasks/format-code-task-000656", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:066fa78ba127ff32a728747cb732d960ad1226fc2394e83176f0b438a5475099", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `HanziWriter` instances to support `updateDimensions(options: Partial<{ width: number; height: number; padding: number }>): void` after creation. In a session like `const writer = HanziWriter.create('target', '人', { width: 200, height: 200, padding: 10, charDataLoader }); await writer.setCharacter('人'); writer.updateDimensions({ width: 300, height: 350, padding: 20 });`, the rendered SVG target should have `width=\"300\"` and `height=\"350\"`, and the currently displayed character should stay visible using the new size and padding rather than resetting to an unloaded state. The same method should work for canvas-backed writers: after `HanziWriter.create('target', '人', { renderer: 'canvas', width: 200, height: 200, padding: 10, charDataLoader }).updateDimensions({ width: 300, height: 350, padding: 20 })`, the canvas element should expose `width=\"300\"` and `height=\"350\"`.\n\nThe options object is partial: omitted `width`, `height`, or `padding` values should keep their current values while provided values take effect. If a quiz is active, calling `updateDimensions` should keep the quiz active and align subsequent pointer input with the resized character, so strokes are graded in the same character coordinate space after the resize. Updating dimensions for an already-rendered character should apply the new geometry without discarding what is currently visible."} {"task_id": "format-code-task-000657", "source_id": "format-code-task-000657", "domain": "code", "task_path": "tasks/format-code-task-000657", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:807ec4d49598763b60b8d2c18b5d793470a4ba2b1c09458fb77756458e4f4951", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nCurrently `opnieuw` will only raise the last caught exception. This creates two issues:\n1. We lose any exceptions that were previously raised. This is especially problematic when the first caught exception is different from the second caught exception.\n2. It is hard to tell whether `opnieuw` actually retried in a Sentry stack trace as the retrying isn't explicitly in the trace.\n\n```python\nfrom opnieuw import retry\n\ncounter = 0\n\n\n@retry(\n retry_on_exceptions=(TypeError, ValueError),\n max_calls_total=3,\n retry_window_after_first_call_in_seconds=1,\n)\ndef raise_depending_on_counter() -> None:\n global counter\n counter += 1\n if counter == 1:\n raise TypeError\n elif counter == 2:\n raise ValueError\n else:\n raise IndexError\n\n\nraise_depending_on_counter()\n```\n\nThis currently raises:\n```console\n❯ python test.py\nTraceback (most recent call last):\n File \"/home/daniel/channable/requestmachine/test.py\", line 22, in \n raise_depending_on_counter()\n File \"/nix/store/mzflaklx9497sffvm5k28cf6m0zdi0yd-python3-3.11.4-env/lib/python3.11/site-packages/opnieuw/retries.py\", line 240, in wrapper\n return f(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^\n File \"/home/daniel/channable/requestmachine/test.py\", line 19, in raise_depending_on_counter\n raise IndexError\nIndexError\n```\n\nIdeally it would be something like:\n```console\n❯ python test.py\nTraceback (most recent call last):\n File \"/nix/store/mzflaklx9497sffvm5k28cf6m0zdi0yd-python3-3.11.4-env/lib/python3.11/site-packages/opnieuw/retries.py\", line 241, in wrapper\n return f(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^\n File \"/home/daniel/channable/requestmachine/test.py\", line 15, in raise_depending_on_counter\n raise TypeError\nTypeError\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n File \"/nix/store/mzflaklx9497sffvm5k28cf6m0zdi0yd-python3-3.11.4-env/lib/python3.11/site-packages/opnieuw/retries.py\", line 241, in wrapper\n return f(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^\n File \"/home/daniel/channable/requestmachine/test.py\", line 17, in raise_depending_on_counter\n raise ValueError\nValueError\n\nThe above exception was the direct cause of the following exception:\n\nTraceback (most recent call last):\n File \"/home/daniel/channable/requestmachine/test.py\", line 22, in \n raise_depending_on_counter()\n File \"/nix/store/mzflaklx9497sffvm5k28cf6m0zdi0yd-python3-3.11.4-env/lib/python3.11/site-packages/opnieuw/retries.py\", line 265, in wrapper\n raise last_exception\n File \"/nix/store/mzflaklx9497sffvm5k28cf6m0zdi0yd-python3-3.11.4-env/lib/python3.11/site-packages/opnieuw/retries.py\", line 241, in wrapper\n return f(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^\n File \"/home/daniel/channable/requestmachine/test.py\", line 19, in raise_depending_on_counter\n raise IndexError\nIndexError\n```\n\nA draft PR is here: https://github.com/channable/opnieuw/pull/21."} {"task_id": "format-code-task-000658", "source_id": "format-code-task-000658", "domain": "code", "task_path": "tasks/format-code-task-000658", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a230cf3b8d3f5c8743532ccb41b038317ef08a687ddfaa235153900d9564f51f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nI'm still using `docker: true` in some fogg configs, and right now `fogg plan` / `fogg apply` don't give me any heads-up that Docker support is going away. Can we have those commands show a non-fatal deprecation warning when Docker is enabled, and have config validation surface that kind of warning instead of only fatal errors?\n\n## Expected outcomes\n\n- **Docker-enabled CLI runs**\n - When a configuration enables Docker with `docker: true`, both `fogg plan` and `fogg apply` should emit the warning `Docker support is deprecated and will be removed in a future version of fogg.`\n - That warning is non-fatal: it should not by itself cause `fogg plan` or `fogg apply` to fail.\n\n- **Docker-disabled CLI runs**\n - When Docker is not enabled in the configuration, `fogg plan` and `fogg apply` should not emit the Docker deprecation warning.\n\n- **Configuration validation warnings**\n - `config/v2.Config.Validate` should surface non-fatal validation warnings as well as fatal validation errors.\n - Calling `Validate` on a config whose `Docker` setting is true should return a warning containing `Docker support is deprecated and will be removed in a future version of fogg.`\n - Fatal validation failures should still be reported as errors; non-fatal warnings should remain inspectable even when fatal validation errors are also present.\n\n## Implementation notes\n\nThe exact mechanism for collecting, propagating, and displaying warnings is up to the implementation. Keep existing fatal validation behavior intact while adding a way for callers and CLI commands to observe non-fatal warnings."} @@ -590,7 +568,6 @@ {"task_id": "format-code-task-000678", "source_id": "format-code-task-000678", "domain": "code", "task_path": "tasks/format-code-task-000678", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:194d062bf587e2bcf5fae7a88603390cfa68d77a41f9a3f24ae5b1a27e2ca71f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### Describe the bug\n\nUsing `gh` to `browse` a file with given line number does not work with Markdown files. The URL the user is taken to is the rendered Markdown view without line numbers on the left-hand side.\n\n### Steps to reproduce the behavior\n\n```\n$ gh browse README.md:3\nnow opening https://github.com/cli/cli/tree/trunk/README.md#L3 in browser\n$ gh --version\ngh version 2.0.0 (2021-08-24)\nhttps://github.com/cli/cli/releases/tag/v2.0.0\n```\n\n### Expected vs actual behavior\n\nLooks like a `?plain=1` parameter was [added to GitHub Web UI](https://github.blog/changelog/2021-06-30-parameter-to-disable-markdown-rendering/) to specifically help navigate to Markdown lines.\n\nSo, instead of:\n* https://github.com/cli/cli/tree/trunk/README.md#L3\n\nI'd expect the user to be taken to:\n* https://github.com/cli/cli/blob/trunk/README.md?plain=1#L3\n\n_note: the new URL has `blob` in the path because `?plain=1` does not work with `tree` in the path_\n\n### Logs\n\nN/A"} {"task_id": "format-code-task-000679", "source_id": "format-code-task-000679", "domain": "code", "task_path": "tasks/format-code-task-000679", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:12d5aff3d3367d0ab747abf6c2f8bc0359a5cd6aacd1b2bb7384ff6ecd90b891", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n`gh release create`: \"Write using git tag message as template\" option is hidden sometimes even when annotations exist\n### Describe the bug\n\n`gh --version`:\ngh version 2.4.0 (2021-12-21)\nhttps://github.com/cli/cli/releases/tag/v2.4.0\n\nIn earlier versions, I would *always* see the option to create release notes from a tag message if the tag was annotated. Currently, that option is hidden when I own the repository.\n\n### Steps to reproduce the behavior\n\n```shell\ngh repo clone me/my-repo\ncd my-repo\ngit tag -am \"foo\" bar\ngh release create bar # don't see option\n```\n```shell\ngh repo clone another-user/repo-i-do-no-maintain\ncd repo-i-do-not-maintain\ngit tag -am \"foo\" bar\ngh release create bar # see tag message option\n```\n\n### Expected vs actual behavior\n\nI expect the \"Write using git tag message as template\" option to *always* appear, assuming the annotated tag is available.\n\n### Extra Info\n\nI think these lines are doing it. It looks like, as long as `generatedNotes != nil`, `tagDescription` is not set, so it equals `\"\"`.\nhttps://github.com/cli/cli/blob/ad8d7bb02e36e66e28c78837f5392afd1a5187a3/pkg/cmd/release/create/create.go#L237-L239\nhttps://github.com/cli/cli/blob/ad8d7bb02e36e66e28c78837f5392afd1a5187a3/pkg/cmd/release/create/create.go#L261-L263"} {"task_id": "format-code-task-000680", "source_id": "format-code-task-000680", "domain": "code", "task_path": "tasks/format-code-task-000680", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:30f7fc0408ef4c6c93e4f5a3b20978a546361bdfd33843459c3cdded172240e3", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `auto_ml.Predictor` to support regression uncertainty prediction as part of the normal object lifecycle. A user should be able to construct `Predictor(type_of_estimator='regressor', column_descriptions=...)`, call `train(...)` with the opt-in keyword arguments `train_uncertainty_model=True`, `uncertainty_data=...`, `uncertainty_delta=None`, `uncertainty_delta_units=None`, `uncertainty_delta_direction=None`, `calibrate_uncertainty=False`, `uncertainty_calibration_settings=None`, and `uncertainty_calibration_data=None`, and then call `predict_uncertainty(prediction_data)` or `score_uncertainty(X, y, advanced_scoring=True, verbose=2)` on the same instance.\n\nWhen `train_uncertainty_model=True` is used for a regressor, training should clean and transform `uncertainty_data`, append the base regression prediction as an additional feature, label each row as certain or uncertain from the observed prediction error, and train a classifier that predicts the probability that a future regression prediction will be uncertain. If no `uncertainty_delta` is supplied, the threshold should default to one half of the standard deviation of the original regression training targets, measured in absolute units. If `uncertainty_delta_units='absolute'`, compare either `abs(prediction - actual)` for `uncertainty_delta_direction='both'` or the signed delta for `uncertainty_delta_direction='directional'`; if `uncertainty_delta_units='percentage'`, make the same comparisons after dividing the delta by the actual value.\n\n`predict_uncertainty(prediction_data)` should return the base regression prediction together with the uncertainty probability. For batch prediction input, it should return a pandas `DataFrame` with at least `base_prediction` and `uncertainty_prediction` columns, where `uncertainty_prediction` is the probability of the uncertain class. For a single row dict, it should return a dict with the same fields. `score_uncertainty(X, y, advanced_scoring=True, verbose=2)` should call `predict_uncertainty`, derive the true uncertain labels from `y` using the configured threshold rules, print the normal classifier probability diagnostics, and return the Brier score.\n\nIf `calibrate_uncertainty=True`, training should use `uncertainty_calibration_data` plus `uncertainty_calibration_settings` to bucket uncertainty probabilities and attach calibration details to later batch `predict_uncertainty` results. The default calibration settings should be `{'num_buckets': 10, 'percentiles': [25, 50, 75]}`. With custom settings like `{'num_buckets': 3, 'percentiles': [25, 50, 75]}`, batch uncertainty predictions should include `bucket_num`, `percentile_25_delta`, `percentile_50_delta`, and `percentile_75_delta` columns.\n\nInvalid training configurations should fail early with `ValueError`: `train_uncertainty_model=True` on a classifier, `train_uncertainty_model=True` without `uncertainty_data`, an `uncertainty_delta` without `uncertainty_delta_units`, or an `uncertainty_delta_direction` other than `both` or `directional`."} -{"task_id": "format-code-task-000681", "source_id": "format-code-task-000681", "domain": "code", "task_path": "tasks/format-code-task-000681", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:fa7998e14b2b38495e9e7b32a86b955c0d642cbe38dfda63f0b27a3726a204bf", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## CI `wasm_bindings` job is broken and `cargo test --all` blows up in `crates/testing`\n\nI was trying to put up a PR and noticed the `wasm_bindings` job on GitHub Actions fails right away. The \"Build rust-wasm-test\" step is invoking\n\n```\ncargo run -p spacetimedb-cli -- build crates/modules/rust-wasm-test\n```\n\nbut there is no `crates/modules/` directory anymore — the modules live under the top-level `modules/` directory now (`modules/rust-wasm-test`, `modules/benchmarks`, `modules/spacetimedb_quickstart`, all listed as workspace members in the root `Cargo.toml`). So the CLI bails out because it can't find the manifest. Looks like the CI workflow was just never updated when modules were moved.\n\nI tried reproducing locally with `cargo test --all` and ran into a separate but related mess: the integration tests in `crates/testing` (`with_module` / `with_module_async` → `load_module`) panic when they try to read the compiled wasm. From poking at it, it seems the test harness is still resolving module paths and wasm artifact paths as if modules were under `crates/modules/`, so it ends up pointing at a file that doesn't exist and `std::fs::read(...).unwrap()` blows up.\n\nA second thing I noticed while looking at this: the harness assumes every module's wasm artifact has the same fixed filename. But each module is its own crate with its own name, and `cargo build --target=wasm32-unknown-unknown --release` produces a wasm whose name comes from the crate name — so different modules produce differently-named `.wasm` files. As soon as you point it at, say, `benchmarks` instead of `rust-wasm-test`, the hardcoded filename won't match.\n\nAlso minor, but `modules/spacetimedb_quickstart` uses `snake_case` while the other entries under `modules/` are `kebab-case` — would be nice to make that consistent while we're cleaning this up.\n\nIt would be great to get CI green again and have the testing crate actually able to load module wasm from wherever the modules currently live."} {"task_id": "format-code-task-000682", "source_id": "format-code-task-000682", "domain": "code", "task_path": "tasks/format-code-task-000682", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:36e649e9fb82b0a31751c70a8e92223f70c13287f6c30ac596f20ef1e35a9ab0", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Feature request: KMS encryption filter and action for SNS topics\n\nSNS now supports server-side encryption with KMS, and I'd like to manage it with Cloud Custodian, but the SNS resource doesn't seem to expose anything for it.\n\nMy use cases:\n\n1. **Audit which SNS topics are encrypted and with which key.** I want to write a policy that selects SNS topics whose KMS master key is (or isn't) one of our approved CMKs — same kind of filtering that other resources support against a KMS key (matching by id / arn / alias). Right now I can only get at it by writing a raw `value` filter against `KmsMasterKeyId`, which doesn't help me match against alias names or filter through KMS key attributes.\n\n2. **Remediate unencrypted topics.** Once I've found topics that aren't encrypted (or are encrypted with the wrong key), I want an action that flips encryption on for them, ideally letting me pick the KMS key. I'd also like to be able to turn encryption back off on a topic if needed.\n\nA rough example of the kind of policy I'd like to be able to write:\n\n```yaml\npolicies:\n - name: sns-encrypt-with-approved-cmk\n resource: sns\n filters:\n - \n actions:\n - \n```\n\nWould it be possible to add KMS-aware filtering and an encryption-management action to the `sns` resource?"} {"task_id": "format-code-task-000683", "source_id": "format-code-task-000683", "domain": "code", "task_path": "tasks/format-code-task-000683", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:bbecd1a438230867a44d24f7f33c63f5e9bdae8898f63995dd271d32765928f9", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## iam-role resource has no way to delete roles via a policy\n\nI'm trying to write a Custodian policy that cleans up IAM roles that haven't been used in a long time. The `usage` filter on `iam-role` works well for finding them — e.g.:\n\n```yaml\npolicies:\n - name: iam-delete-unused-role\n resource: iam-role\n filters:\n - type: usage\n match-operator: all\n LastAuthenticated: null\n actions:\n - delete\n```\n\n…but when I run this Custodian rejects the policy because `iam-role` doesn't actually have a `delete` action registered. Other IAM resources have actionable lifecycle support, so it's surprising that role deletion isn't there.\n\nCould `iam-role` get a `delete` action so unused/stale roles can be cleaned up directly from a policy?\n\nA couple of things I'd want the action to handle gracefully, since they come up routinely when sweeping a large account:\n\n- Some roles will still be attached to an instance profile and AWS refuses to delete them in that state. The action shouldn't silently pretend it worked, but it also shouldn't be the kind of thing where one stuck role aborts the whole sweep before the other deletable roles are processed.\n- When iterating over a batch, individual roles may have already been removed (e.g. by another process between list and delete) — that case should just be skipped rather than treated as a failure."} {"task_id": "format-code-task-000684", "source_id": "format-code-task-000684", "domain": "code", "task_path": "tasks/format-code-task-000684", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:5b0309cd8842e0fac00c108c6d4c00f98a9070b773865d768a4e39981acee9ca", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nThe S3 `data-events` filter is used to find buckets whose object-level activity is covered by CloudTrail, but its selector parsing is too literal for the shapes returned by the CloudTrail API. A selector may identify an S3 bucket with the canonical bucket ARN (`arn:aws:s3:::bucket`) or with the object resource form (`arn:aws:s3:::bucket/*`), and a wildcard bucket resource must mean every bucket in the policy input. The filter also needs to remain safe when a trail contains management-event selectors or data resources for another AWS service.\n\nUpdate the filter's observable behavior without changing its policy-facing shape: `state: present` must return each input bucket covered by at least one S3 object data resource from any of the discovered trails, while `state: absent` must return exactly the complementary input buckets. Coverage from trails in different home regions must be combined; each trail's event selectors must be read from its own `HomeRegion`, so a trail in one region cannot hide or replace selectors from another. Preserve the input bucket order. Existing policy configurations and the `state` values remain unchanged."} @@ -614,7 +591,6 @@ {"task_id": "format-code-task-000707", "source_id": "format-code-task-000707", "domain": "code", "task_path": "tasks/format-code-task-000707", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1953dc4cbb7a7a7ca7c1792af3415a6904ea53c3402e4a5a658e175ddf2a701b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nOut of memory crash when objects have a large length field unrelated to array size\nWhile writing tests for [GraphBrainz](https://github.com/exogen/graphbrainz) I noticed that my latest test was consistently crashing AVA. Running the single test alone was enough to cause an OOM error, always in `concordance.serialize`, and the object I was snapshotting was not large by any means.\n\nI narrowed it down to the `length` field on my objects. This field has nothing to do with array lengths, rather the meaning in this context is a recording length in milliseconds.\n\n```js\n[\n {\n title: \"Airbag\",\n length: 284400\n },\n {\n title: \"Paranoid Android\",\n length: 383493\n },\n // …more…\n]\n```\n\nConcordance seems to be assigning some special meaning to these `length` fields and allocating memory based on them.\n\nTry this and you'll notice it takes quite a long time and uses a lot of memory:\n\n```\n> concordance = require('concordance');\n> concordance.serialize(concordance.describe({ length: 12345678 }));\n```\n\nIt's possible this could be the cause of several of the OOM bug reports opened for AVA.\n\n
\nStack trace\n\n```\n==== JS stack trace =========================================\n\n 0: ExitFrame [pc: 0x3241121dc01d]\nSecurity context: 0x3f5ee919e681 \n 1: encode [0x3f5ecb13e4a1] [/Users/brianbeck/Projects/graphbrainz/node_modules/concordance/lib/encoder.js:~177] [pc=0x3241125889c2](this=0x3f5ecfec66f9 ,serializerVersion=2,rootRecord=0x3f5ecb13e771 ,usedPlugins=0x3f5ecb145bf9 )\n 2: serialize [0x3f5ecb102e21] [/Users/b...\n\nFATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory\n 1: 0x100039dbf node::Abort() [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n 2: 0x100039fc9 node::OnFatalError(char const*, char const*) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n 3: 0x1001d1375 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n 4: 0x10059c572 v8::internal::Heap::FatalProcessOutOfMemory(char const*) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n 5: 0x10059f045 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n 6: 0x10059aeef v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n 7: 0x1005990c4 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n 8: 0x1005995c5 v8::internal::Heap::CollectAllAvailableGarbage(v8::internal::GarbageCollectionReason) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n 9: 0x1005a5a21 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n10: 0x100574da6 v8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Heap::RootListIndex, int, v8::internal::Object*, v8::internal::PretenureFlag) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n11: 0x10051c2de v8::internal::(anonymous namespace)::ElementsAccessorBase >::GrowCapacity(v8::internal::Handle, unsigned int) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n12: 0x1007b6f9f v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/brianbeck/.nvm/versions/node/v10.10.0/bin/node]\n13: 0x3241121dc01d\nAbort trap: 6\n```\n\n"} {"task_id": "format-code-task-000708", "source_id": "format-code-task-000708", "domain": "code", "task_path": "tasks/format-code-task-000708", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:593991a595e1e19d554009e1ab76027edc1cd9a7e24fa31652751af11928ca54", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI'm hitting a bare `AssertionError` (no message at all) when conda tries to install into my env — the traceback just ends in `PrefixData.insert` with an empty assert, so I have no idea which package is the problem. It seems to happen after the solver finishes, during the actual write-out step. I dug a bit and it looks like the same package name shows up twice in what the solver decided to install, but I can't tell from the error which one it is. Could you take a look?\n\nExpected outcomes:\n- When conda computes the final set of package records for an environment operation, the result should not contain more than one record for the same package name.\n- If insertion of a package record still encounters a duplicate package name, the raised `AssertionError` should include enough context to identify the conflicting package name and make the failure actionable instead of appearing as an empty assertion.\n\nImplementation notes:\n- The specific data structures, filtering location, and validation mechanism are up to the implementer.\n- Preserve the existing solver and prefix write-out semantics except for eliminating duplicate-name records and improving the duplicate insertion failure message."} {"task_id": "format-code-task-000710", "source_id": "format-code-task-000710", "domain": "code", "task_path": "tasks/format-code-task-000710", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4dcf91b93d0f83d1d5458906cf6e1e36c66da77aad744bc61adf17c4e49184d4", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Hooks directory monitor gets out of sync with the filesystem\n\nI'm using podman's hook directory monitoring (dropping `*.json` files into a hooks.d directory and letting podman pick them up at runtime). I've run into a few situations where what podman thinks is in the directory doesn't match what's actually there.\n\n### 1. One bad hook file hides the other valid hooks\n\nIf I drop two hook files into the directory and one of them is malformed (bad JSON / fails validation), the valid one next to it doesn't get picked up either. I'd expect podman to log/report the error for the bad file but still register the good one — instead the good hook is silently missing.\n\nThis shows up both at startup and while the monitor is running: as soon as something invalid is in the directory, working hooks alongside it stop being honored.\n\n### 2. `mv`-ing a hook file out of the directory leaves it active\n\nIf I `mv somehook.json /tmp/` (instead of `rm`-ing it), podman keeps acting like `somehook.json` is still installed and keeps running it on container start. The file is no longer in the hooks directory, so it shouldn't be applied anymore.\n\n`rm` works correctly; `mv` out of the directory does not.\n\n### 3. Renaming a hook file makes it run twice\n\nIf I rename a hook file in place — e.g. `mv myhook.json myhook-renamed.json` within the hooks directory — podman ends up running the hook twice on the next container: once under the old name (which it never dropped) and once under the new name. Only the renamed file actually exists on disk, so it should run once.\n\n### 4. `chmod` on a hook file isn't reflected\n\nChanging permissions on a hook file (e.g. so it becomes unreadable, or fixing it back) doesn't seem to cause the monitor to re-evaluate the directory — the in-memory state just stays whatever it was.\n\n---\n\nIn all of these cases, what I'd like is simple: the set of active hooks should match the set of valid `*.json` files currently in the configured hook directories. Errors on individual files should be reported but shouldn't prevent the rest from loading, and filesystem operations like rename/move/chmod should be reflected the same way create/delete already (mostly) are."} -{"task_id": "format-code-task-000712", "source_id": "format-code-task-000712", "domain": "code", "task_path": "tasks/format-code-task-000712", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:47b3532699382de8ea4583a2f5fe1856a03ed60a13c8a63c4e61ef1a27004d87", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `netassert run --input-file tests.yaml --kubeconfig kubeconfig` to support Kubernetes workload references in each test's `src.k8sResource` and, when present, `dst.k8sResource`. A `k8sResource` with `kind: pod`, `name`, and `namespace` should resolve to that exact Pod only when it exists, is in the Running phase, and has a non-empty Pod IP; otherwise the test should fail before any scanner or sniffer container is launched, with a reason that says the Pod is missing, not running, or has no IP.\n\nFor `kind: deployment`, NetAssert should find the named Deployment in the requested namespace, choose a ReplicaSet owned by that Deployment with at least one replica, then choose one running owned Pod whose labels match the ReplicaSet selector and whose Pod IP is set. If no such ReplicaSet or Pod exists, the test should fail with a reason tied to the named Deployment and namespace.\n\nFor `kind: statefulset`, NetAssert should find the named StatefulSet, reject StatefulSets scaled to zero, then choose one running owned Pod matching the StatefulSet selector with a Pod IP. For `kind: daemonset`, NetAssert should find the named DaemonSet, reject DaemonSets with zero available Pods, then choose one running owned Pod matching the DaemonSet selector with a Pod IP.\n\nIn a TCP test where the source is a Deployment and the destination is a Pod, the scanner should be launched in the resolved source Pod and should target the resolved destination Pod IP. In a UDP test where both source and destination are Kubernetes resources, the sniffer should be launched in the resolved destination Pod and the scanner should be launched in the resolved source Pod, using the destination Pod IP as the scanner target."} {"task_id": "format-code-task-000714", "source_id": "format-code-task-000714", "domain": "code", "task_path": "tasks/format-code-task-000714", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2edd5889601c89a47dd63dc85ae2c630f9c64f88fddde5bcf8d7a7620892d138", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nThe JSON request-body processor currently flattens some object-shaped payloads into ARGS, but JSON variables are not actually inspectable by rules and array-shaped documents can be rejected even though JSON arrays are part of the supported body shape. Make JSON body inspection consistent and useful to WAF policies.\n\nWhen a body is processed as JSON, recursively flatten both object and array containers into the established dotted keys (for example, `json.user.name`, `json.items.0`, and deeper nested indexes). Every array element must be addressable, including string, number, boolean, null, object, and nested-array elements. Convert scalar values to their textual form (`null` becomes an empty string) without dropping them. The resulting flattened values must remain available through both `ARGS_POST` and the combined `ARGS` collection using those keys.\n\nThe public `BodyProcessor` lookup path used by `SecRule JSON:` must resolve existing nested object and array paths to their scalar value. A path that is absent must produce no match rather than matching another field or the whole document. Malformed JSON and valid JSON documents whose root is a scalar (rather than an object or array) must be reported as processing errors. Keep the existing object flattening behavior and normal request-body error propagation intact."} {"task_id": "format-code-task-000715", "source_id": "format-code-task-000715", "domain": "code", "task_path": "tasks/format-code-task-000715", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:0c90f18ab8b297fbac0c5dd1f4fd6f694af590e4812db96d6a9b32f2edbed001", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Client doesn't retry other machines when a request to one machine fails at the network layer\n\nI'm using go-etcd against a multi-node etcd cluster and relying on the\nclient's built-in retry/fail-over to keep things working when one node\nbecomes unavailable (machine down, connection refused, transient network\nhiccup, etc.).\n\nWhat I expected: if the client can't even get a response back from one\nof the machines in the cluster, it should move on and try another one,\nup to the usual retry limit.\n\nWhat actually happens: the very first network-level failure bubbles\nstraight back out of `SendRequest` to my code. The other machines in\nthe cluster are never tried, even though they're healthy and listed in\n`cluster.Machines`. Effectively a single bad node takes the whole call\ndown instead of being failed over.\n\nMinimal repro: point a `Client` at a cluster where the first machine in\nthe list is unreachable (e.g. nothing listening on that port, or pull\nits network), and do any normal `Get`/`Set`. The call returns the\nunderlying dial/connection error immediately instead of retrying the\nother members.\n\nThe HTTP-status retry path (e.g. 500 from the server) seems to behave\ncorrectly — only the \"no response at all\" path is broken. Since this is\nexactly the case where retrying matters most, I'd expect the default\nretry policy to keep going here rather than surface the error on the\nfirst attempt."} {"task_id": "format-code-task-000716", "source_id": "format-code-task-000716", "domain": "code", "task_path": "tasks/format-code-task-000716", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b0adf886b6815f78cd303fb2ca30e16cb8df0b0ce5172805c40a0f9a15c09e77", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI've got a bunch of Ignition configs floating around that still declare `\"ignition\": { \"version\": \"2.0.0\" }`, and when I feed them through `config.Parse` they blow up because it tries to read them as the latest schema. I don't really want to hand-rewrite them all to the newest version — can the parser just recognize 2.0.0 configs and handle them properly, ideally giving me back the same internal config type so the rest of my code doesn't care which version the input was?\n\n# Expected outcomes\n\n- `config.Parse` should accept valid Ignition configs that declare version `2.0.0`.\n- Parsing a valid `2.0.0` config should return the repository’s current `types.Config` representation, so callers can consume it like configs parsed from newer supported versions.\n- Supported user-visible configuration data from valid `2.0.0` configs should be preserved in the current config representation.\n- Invalid `2.0.0` configs should still fail with an error and validation report rather than being silently accepted.\n- Existing behavior for other supported versions should continue to work.\n\n# Implementation notes\n\n- Do not require callers of `config.Parse` to know whether the input was originally version `2.0.0` or a newer supported version.\n- Prefer behavior-compatible integration with the existing config parsing and validation conventions.\n- The exact parsing organization and compatibility implementation are up to the implementer."} @@ -628,7 +604,6 @@ {"task_id": "format-code-task-000724", "source_id": "format-code-task-000724", "domain": "code", "task_path": "tasks/format-code-task-000724", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:5c384b024f9da9fc1749593b8cb85609a22cbf25544f070b22ab95dccc89dfd2", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\n我想通过 REST API 动态改某个 db 的 audit 配置,按理说 PUT/POST `/{db}/_config/audit` 应该能做这事吧?但我试了下,不管发什么请求体过去,配置都没变,GET 回来还是原样,感觉这俩接口压根没接上。能不能让 PUT 整体替换、POST 增量改 audit events 真正生效?另外 GET 现在直接返回一坨 events map,我想顺便知道 audit 整体是不是开着的,最好能把全局 enabled 也带出来。\n\n# Expected outcomes\n\n- `GET /{db}/_config/audit` returns a JSON object that includes both the database audit enabled state and the audit event configuration, rather than returning the event map as the top-level response.\n- The audit enabled state and event enabled states returned by `GET /{db}/_config/audit` reflect the current persisted database configuration after defaults/runtime configuration are applied, including changes made through the configuration API without requiring a database restart.\n- `GET /{db}/_config/audit` includes an ETag corresponding to the current database configuration version when the audit configuration is available.\n- If database audit configuration cannot be read because the server is running without persistent configuration support, `GET /{db}/_config/audit` returns a `503 Service Unavailable` response with an audit-configuration-unavailable error.\n- `PUT /{db}/_config/audit` treats the request body as a full replacement of the database audit configuration: the global audit enabled value is replaced from the request body, and the enabled event set is rebuilt from the events explicitly enabled in the request.\n- `POST /{db}/_config/audit` treats the request body as an incremental update: explicitly supplied global audit enabled values are updated, events set to enabled are added, events set to disabled are removed, and omitted fields/events are left unchanged.\n- `PUT /{db}/_config/audit` and `POST /{db}/_config/audit` reject malformed or unknown audit event IDs in the submitted events object with a `400 Bad Request` response that identifies the audit configuration update failure and distinguishes invalid event ID syntax from unknown event IDs.\n- When `GET /{db}/_config/audit` is requested in verbose form, each event entry includes the available event metadata and enabled/filterable state using the documented event object fields, while omitting unavailable metadata fields from the JSON response.\n\n# Implementation notes\n\nThe implementation may choose where to perform parsing, validation, persistence updates, and response construction, as long as the externally observable REST API behavior above is satisfied. Keep the behavior compatible with existing audit event identifiers and existing admin API conventions for JSON responses, errors, and configuration versioning."} {"task_id": "format-code-task-000725", "source_id": "format-code-task-000725", "domain": "code", "task_path": "tasks/format-code-task-000725", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:772444e9f959d5f0ebf06d72fbb844a8038c6a10a1c47da77dd9ef3efddec9e0", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\n我在用 ALL 的 SAC 跑连续控制时发现,只把环境 action space 从 `[-1, 1]` 线性放大到比如 `[-2, 2]`,`SoftDeterministicPolicy` 返回的 `log_prob`、entropy 和 policy loss 就会明显跟着尺度变,训练表现也飘得很厉害。另外我开了 `clip_grad` 后,有次梯度范数已经是 NaN/Inf,`step()` 还是继续往下跑了;我这边环境用的是 torch 1.9,但包依赖看起来还卡在 1.8。\n\n## Expected outcomes\n\n- `SoftDeterministicPolicy` 在连续动作空间边界不是 `[-1, 1]` 时,返回的 `log_prob` 应与缩放后的动作分布一致;只线性放大同一任务的动作范围时,`log_prob` 只应体现动作尺度带来的常数偏移,不应出现逐维概率量级被错误放大的现象。\n- 基于该 `log_prob` 的 entropy 与 SAC policy loss 不应因为动作空间做等价线性缩放而产生额外的异常尺度变化。\n- `Approximation.step()` 在启用非零 `clip_grad` 时,如果待裁剪的梯度范数为 NaN 或 Inf,应抛出 `RuntimeError` 并阻止优化步骤静默继续。\n- 包元数据版本应更新为 `0.7.2`,文档配置中的 release 也应更新为 `0.7.2`。\n- 安装依赖应面向 torch 1.9,声明为 `torch~=1.9.0`;项目 CI 中固定安装的 CPU 版 torch 也应更新到 `torch==1.9.0+cpu`。\n\n## Implementation notes\n\n具体校正位置、辅助函数组织方式、内部命名和测试覆盖方式由实现者决定;只要公开行为、错误处理语义、版本元数据与依赖声明满足上述结果即可。"} {"task_id": "format-code-task-000726", "source_id": "format-code-task-000726", "domain": "code", "task_path": "tasks/format-code-task-000726", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:77e829c9926a80502c549e3dc3d5dfb2caa8dfc8841774efcb8b727e349fa198", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Fix double-backprop through shared feature networks\n\nIn our actor-critic setup, a single `FeatureNetwork` produces a feature\nrepresentation that is shared by several downstream heads (e.g. a value\nfunction and a policy). Each head computes its own loss and calls\n`.backward()`. Today, because the features the network hands out are still\nwired into the feature model's computation graph, every head's backward pass\nruns all the way back through the shared feature model. With two heads that\nmeans we backpropagate through the shared model twice per update even though we\nonly take one optimizer step — wasteful, and it forces callers to juggle\n`retain_graph=True` to avoid \"backward through the graph a second time\" errors.\n\nRework `FeatureNetwork` so the shared model is only backpropagated through\nonce per training step, while keeping its existing public surface\n(`__call__`, `eval`, `reinforce`).\n\nRequired observable behavior:\n\n- Calling the network on a state returns a `State` whose mask and info are\n carried over from the input, and whose feature tensor holds the model's\n output for that state. That feature tensor must be a gradient-tracking leaf\n that is **disconnected** from the feature model's graph: any number of\n downstream computations may derive a loss from it and call `.backward()`\n independently, in sequence, without passing `retain_graph` and without\n raising. The gradient each head produces accumulates on this returned\n feature tensor.\n\n- `reinforce()` takes no loss of its own — the training signal is exactly the\n gradient that downstream heads have accumulated on the feature tensors handed\n out since the last `reinforce()`. It pushes that accumulated gradient back\n through the shared model in a single backward pass, honoring the optional\n gradient clipping, then performs one optimizer step and clears the gradients.\n\n- The network may be called multiple times before a single `reinforce()`; all\n of those forward passes contribute their accumulated gradients to that one\n optimizer step. After `reinforce()` returns, the pending state is cleared:\n the next forward/reinforce cycle is independent and must not re-apply\n gradients from a previous cycle.\n\n- `eval(state)` returns a `State` (mask/info preserved) whose features are the\n model output computed without building a graph (no gradient tracking), and\n it must not disturb the model's training mode.\n\nThe net effect: for a set of downstream losses, the optimizer step applied to\nthe shared model is exactly the single SGD-equivalent step you would get by\nbackpropagating the summed downstream gradient through the model once.\n"} -{"task_id": "format-code-task-000727", "source_id": "format-code-task-000727", "domain": "code", "task_path": "tasks/format-code-task-000727", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:18e9bfe40fa52adb11f38f307a785b06057c4b1b9db827bb718a774bf3939170", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Feature request: drop-in configuration files\n\nI'm packaging CRI-O for our distribution and want to ship sensible defaults in `/etc/crio/crio.conf` while letting users (and our config management) layer in machine-specific tweaks — custom registries, an extra runtime entry, a different cgroup manager — without ever touching that base file.\n\nToday the only knob we have is `--config, -c` pointing at one TOML file, which forces us into two awkward options:\n\n- Have users edit `/etc/crio/crio.conf` directly: conflicts on every package update, painful for config management to template.\n- Have users replace it with their own copy: they lose any new defaults we ship in future releases.\n\nMost other system daemons (systemd, networkd, sshd, …) solve this with a \"drop-in\" directory pattern: a directory of partial config files that are merged on top of the base config in a predictable order. I'd like CRI-O to support the same idea — a directory of partial TOML configs that get layered on top of the main `crio.conf` at startup, with ordering determined by filename so admins can pick priority via prefixes like `00-…`, `10-…`, `99-…`.\n\nWhat matters for this to be useful:\n\n- The base config file is applied first, then each fragment is layered on top in deterministic name order. Each fragment is just a partial TOML — only the keys it sets should take effect, the rest fall through to the lower-priority layers.\n- Command-line flags passed to `crio` continue to have the highest priority, same as today, so a CLI override always beats both the base config and any fragments.\n- If the drop-in directory doesn't exist, startup should not fail — that's the expected state for users who don't use drop-ins at all.\n\nThis would let distros and config-management tools layer overrides cleanly without ever rewriting `crio.conf`.\n\nA natural shape would be a new CLI flag like `--config-dir` (short `-d`) on `crio` to point at the directory, plus a corresponding method on the `Config` type (something like `UpdateFromPath`) that walks the directory and layers each file on top via the existing per-file update path."} {"task_id": "format-code-task-000728", "source_id": "format-code-task-000728", "domain": "code", "task_path": "tasks/format-code-task-000728", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a25a1d4e5116c9c643fb9f967c01407c49b7db600d308bab4d0516cad1184e54", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Closing a WAMP session raises errors when a pending call's awaiting task was cancelled (asyncio)\n\nI'm using autobahn-python over asyncio. In my app I make WAMP calls\nfrom inside tasks and put timeouts on them with `asyncio.wait_for`, so\nsome calls end up with their awaiter cancelled before `session.call(...)`\nhas actually returned. Roughly:\n\n```python\nasync def fetch():\n return await session.call(u'com.example.fetch')\n\ntry:\n result = await asyncio.wait_for(fetch(), timeout=2.0)\nexcept asyncio.TimeoutError:\n pass # give up and move on\n```\n\nAfter running like this for a while I eventually shut the session down —\neither explicitly via `leave()`, or because the underlying transport\ndrops. When that happens and there are still-pending requests whose\nawaiting task had previously been cancelled / timed out, autobahn itself\nerrors out during the teardown of the session.\n\nI'd expect closing a session to be a clean operation: even if some of\nthe still-outstanding request futures have already been abandoned or\ncancelled by their callers, shutting the session down shouldn't blow up."} {"task_id": "format-code-task-000729", "source_id": "format-code-task-000729", "domain": "code", "task_path": "tasks/format-code-task-000729", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:152a01891517bc39fb879be1baf17144a7b67108665c40e596fa41a62905ecc2", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\n我用 terrajet 把资源导出成 tfstate 之后,发现 refresh 阶段完全不理会我在 main.tf 里配的 operation timeouts,每次还是按默认超时走。我特地配了 read/create 这些超时,apply 的时候看着是生效的,但 refresh 还是该慢慢慢、该卡卡,感觉像是 refresh 根本没拿到我配的超时值。这是不是 tfstate 里少存了点什么?\n\n## Expected outcomes\n\n- `WriteTFState` should preserve configured non-zero operation timeout settings in the generated tfstate using a Terraform-compatible state representation observable by refresh.\n- `WriteTFState` should omit timeout state metadata when no operation timeout is configured, and should not disturb any existing state metadata in that case.\n- When existing state metadata is present, `WriteTFState` should preserve unrelated existing metadata while adding or updating the configured timeout information.\n- `WriteMainTF` should keep its existing behavior for operation timeouts: configured non-zero timeout settings are emitted through the existing `timeouts` parameter in main.tf, and no `timeouts` parameter is emitted when all operation timeouts are unset.\n\n## Implementation notes\n\nThe exact structure of helper code, data types, and validation placement is up to the implementer. The important requirement is that the generated tfstate and main.tf remain compatible with Terraform’s observable behavior for operation timeouts and preserve unrelated existing metadata.\n\n## Required output literals (exact-match contract)\n\nWhen `WriteTFState` emits configured operation timeouts into Terraform state private metadata, the decoded private metadata MUST contain Terraform's resource timeout metadata key exactly:\n\n- State private metadata key: `e2bfb730-ecaa-11e6-8f88-34363bc7c4c0` — this is Terraform's resource timeout private-state compatibility key consumed by refresh.\n\nWithin that metadata object, configured operations MUST use Terraform's operation names exactly: `read`, `create`, `update`, and `delete`. Values MUST be Terraform-compatible duration nanosecond values."} {"task_id": "format-code-task-000730", "source_id": "format-code-task-000730", "domain": "code", "task_path": "tasks/format-code-task-000730", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a5e2f843526274c12bb4f91301746ef3b9f9c5a6653d110102c9db394e713629", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Open a memiavl database at a historical version\n\nThe embedded `memiavl` database (the `memiavl` Go module in this repository) can\ncurrently only be opened at its latest committed version: loading the database\nreplays the entire write-ahead log, so you always end up at the tip.\n\nWe need to be able to open the database **at a specific earlier committed\nversion**, so that callers can reconstruct the exact state of a past version\n(for serving versioned queries, state-sync, etc.) without having to mutate or\nroll back the database.\n\nAdd a load option that selects the version to open. The observable contract:\n\n- The load options gain a way to request a target version, expressed as an\n unsigned integer.\n- When the target version is left at its zero value (the default), loading\n behaves exactly as it does today and opens the latest committed version.\n- When a positive target version `v` that exists in the database's committed\n history is requested, the loaded database must reflect exactly the committed\n state as of version `v`: the version it reports is `v`, and its commit hash\n (and therefore its per-store contents) is identical to what it was right after\n version `v` was committed — as if the commits made after `v` had never been\n applied.\n- Opening at a target version must be non-destructive: it must not delete or\n rewrite the existing on-disk history, so the same database can afterwards be\n reopened at any other version, including the latest.\n\nThe existing latest-version load path and all other database behavior must be\nunaffected.\n"} @@ -638,7 +613,6 @@ {"task_id": "format-code-task-000735", "source_id": "format-code-task-000735", "domain": "code", "task_path": "tasks/format-code-task-000735", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:857e9fbf15bf721e9d87a3e40679800c9c0ec3d57c5ce734d0351210276bb054", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the TM1py cells service to support an async DataFrame cube write method on an existing service object: `tm1.cells.write_dataframe_async(cube_name: str, data: pandas.DataFrame, slice_size_of_dataframe: int = 250_000, max_workers: int = 8, dimensions: Iterable[str] = None, increment: bool = True, sandbox_name: str = None, deactivate_transaction_log: bool = False, reactivate_transaction_log: bool = False, **kwargs)`.\n\nFor a session like `tm1 = TM1Service(...)`, calling `tm1.cells.write_dataframe_async(\"Sales\", df, dimensions=[\"Version\", \"Month\", \"Measure\"], slice_size_of_dataframe=2, max_workers=4, increment=False, sandbox_name=\"Plan\")` should split the DataFrame into row chunks of that size and write each chunk through the existing DataFrame write path using blob mode, preserving the cube name, dimension order, increment flag, sandbox name, and any extra keyword arguments. If `dimensions` is not provided, the method should infer the cube dimension order before validating or writing. A valid DataFrame must have exactly one value column in addition to the cube dimension columns; otherwise it should raise `ValueError(\"Number of columns in 'data' DataFrame must be number of dimensions in cube + 1\")`. Passing a non-DataFrame as `data` should raise `ValueError(\"argument 'data' must of type DataFrame\")`.\n\nWhen `increment=True`, numeric duplicate intersections in the DataFrame should be aggregated before the chunks are submitted, so duplicate rows increment the cube once with their summed value. If every chunk write succeeds, the method should return `None`. If one or more chunk writes fail with `TM1pyWriteFailureException` or `TM1pyWritePartialFailureException`, the method should raise one `TM1pyWritePartialFailureException` whose statuses and error log filenames are flattened from all failed chunks and whose attempt count sums each partial failure's attempts, counting a total failure without an attempts attribute as one attempt. The transaction-log deactivate/reactivate options should apply around the overall async DataFrame write call in the same way as other cell write methods."} {"task_id": "format-code-task-000736", "source_id": "format-code-task-000736", "domain": "code", "task_path": "tasks/format-code-task-000736", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:e2e732b1cab2fbeb38617ca4d2c86b36a51f424ce990552b63cf58aebccc528b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nPlease answer these questions before submitting a bug report.\n\n### What version of godog are you using?\nGodog version is: v0.10.0\n\n### What version of Go are you using?\ngo version go1.14.7 linux/amd64\n\n### What did you do?\nIf possible, provide a recipe for reproducing the error.\nI added a new features/foo.feature to my project and ran `godog .` for the first time in that project.\n\n### What did you expect to see?\ngodog suggesting the new framework functions listed at `// godog v0.10.0 (latest)` in the README.md with the correct regex for the steps. I just defined.\n```\nYou can implement step definitions for undefined steps with these snippets:\n[...]\n\nfunc InitializeTestSuite(ctx *godog.TestSuiteContext) {\n\tctx.BeforeSuite(func() { \n\t\t// clean state for the first rune\n\t})\n}\n\nfunc InitializeScenario(ctx *godog.ScenarioContext) {\n\tctx.BeforeScenario(func(*godog.Scenario) {\n\t\t// clean the state before every scenario\n\t})\n\n\tctx.Step(`regex`, stepcall)\n}\n```\n### What did you see instead?\nexample code for the deprecated calls\n```\nYou can implement step definitions for undefined steps with these snippets:\n[...]\n\nfunc FeatureContext(s *godog.Suite) {\n\ts.Step(`regex`, stepcall)\n}\n```\n\n### Additional context\nI use a project with Go modules.\nfeature file at features/happydogs.feature\n```gherkin\nFeature: Happy dogs\n As a dog owner\n I want my dogs to be happy\n So that it will make me happy as well\n\n Scenario: Initially the dog is sad\n Given 2 dogs\n When they play with no balls\n Then they are still sad\n\n Scenario: If they have at least one ball they are happy\n Given there are 2 dogs\n When they play with 1 ball\n Then then all dogs will be happy\n```\nFull output of godog .\n```plain\n$ godog .\nFeature: Happy dogs\n As a dog owner\n I want my dogs to be happy\n So that it will make me happy as well\n\n Scenario: Initially the dog is sad # features/happydogs.feature:6\n Given 2 dogs\n When they play with no balls\n Then they are still sad\n\n Scenario: If they have at least one ball they are happy # features/happydogs.feature:11\n Given there are 2 dogs\n When they play with 1 ball\n Then then all dogs will be happy\n\n2 scenarios (2 undefined)\n6 steps (6 undefined)\n246.175µs\n\nYou can implement step definitions for undefined steps with these snippets:\n\nfunc dogs(arg1 int) error {\n\treturn godog.ErrPending\n}\n\nfunc thenAllDogsWillBeHappy() error {\n\treturn godog.ErrPending\n}\n\nfunc thereAreDogs(arg1 int) error {\n\treturn godog.ErrPending\n}\n\nfunc theyAreStillSad() error {\n\treturn godog.ErrPending\n}\n\nfunc theyPlayWithBall(arg1 int) error {\n\treturn godog.ErrPending\n}\n\nfunc theyPlayWithNoBalls() error {\n\treturn godog.ErrPending\n}\n\nfunc FeatureContext(s *godog.Suite) {\n\ts.Step(`^(\\d+) dogs$`, dogs)\n\ts.Step(`^then all dogs will be happy$`, thenAllDogsWillBeHappy)\n\ts.Step(`^there are (\\d+) dogs$`, thereAreDogs)\n\ts.Step(`^they are still sad$`, theyAreStillSad)\n\ts.Step(`^they play with (\\d+) ball$`, theyPlayWithBall)\n\ts.Step(`^they play with no balls$`, theyPlayWithNoBalls)\n}\n```"} {"task_id": "format-code-task-000737", "source_id": "format-code-task-000737", "domain": "code", "task_path": "tasks/format-code-task-000737", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a0a77f5fac3a4ca3bb6b0246954e7e3061eea3a55c0fc2ea8115f937c8de5876", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n**Problem Statement**\n\nI’m trying to use CuPy sparse matrices the same way I use SciPy, where I can create an empty CSR or CSC matrix just by passing a shape, but `cupy.sparse.csr_matrix((m, n))` and `csc_matrix((m, n))` don’t seem to accept that. It would be really helpful if those constructors could handle a shape-only empty matrix, including when I pass a dtype.\n\n**Expected Outcomes**\n- `cupy.sparse.csr_matrix((M, N))` accepts a two-dimensional shape tuple and creates an empty CSR matrix with shape `(M, N)`.\n- `cupy.sparse.csc_matrix((M, N))` accepts a two-dimensional shape tuple and creates an empty CSC matrix with shape `(M, N)`.\n- When no `dtype` is supplied for this shape-only form, the resulting empty CSR or CSC matrix defaults to `float64`.\n- When a `dtype` is supplied for this shape-only form, the resulting empty CSR or CSC matrix preserves that dtype.\n- The documented constructor forms for these APIs include shape-only empty-matrix construction, including `csr_matrix((M, N), [dtype])` and `csc_matrix((M, N), [dtype])`.\n\n**Implementation Notes**\n\nAny implementation that preserves the current sparse matrix API and makes the public constructor behavior match these outcomes is acceptable. The exact validation flow, helper structure, and internal sparse-storage construction strategy are left to the implementer."} -{"task_id": "format-code-task-000738", "source_id": "format-code-task-000738", "domain": "code", "task_path": "tasks/format-code-task-000738", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a2c225360a82d3b9e82c3bd5efe509a9e997e26e5a5665f8f1d98e700e00b57f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nNo validation for kernel name\nAlthough `ElementwiseKernel`'s `name` argument is directly used as a function name in generated CUDA code, there are no validation process to raise an exception when invalid characters are used in `name`.\nThat causes CUDA compile error, which is a bit difficult to debug."} {"task_id": "format-code-task-000739", "source_id": "format-code-task-000739", "domain": "code", "task_path": "tasks/format-code-task-000739", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b7e4c697507d3f0e0c0d8993721b64bc14c30b86fd628f1d82c8da928232b39d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want an exported pure TypeScript function `insertVariableToCurl({ curl, index, variableName }: { curl: string; index: number; variableName: string }) => string` that inserts a shell variable reference into cURL command text at a cursor offset. For `insertVariableToCurl({ curl: \"\", index: 0, variableName: \"TOKEN\" })`, it should return `$TOKEN`. For `insertVariableToCurl({ curl: \"curl example.com\", index: 16, variableName: \"TOKEN\" })`, it should append at the end and return `curl example.com$TOKEN`. When insertion occurs inside an unquoted word character, it should use brace syntax so the variable name is not merged with surrounding text: `insertVariableToCurl({ curl: \"curl example.com\", index: 6, variableName: \"HOST\" })` should return `curl e${HOST}xample.com`. In double-quoted values, inserting before a word character should also use braces, while inserting before punctuation or whitespace should use `$NAME` directly; for example `insertVariableToCurl({ curl: \"curl \\\"hello world\\\"\", index: 12, variableName: \"NAME\" })` should return `curl \\\"hello ${NAME}world\\\"`. In single-quoted values, inserting inside the quoted text should close the quote, insert `$NAME`, and reopen the quote so shell expansion can occur, such as returning `curl 'hello'$NAME' world'` for `insertVariableToCurl({ curl: \"curl 'hello world'\", index: 11, variableName: \"NAME\" })`. Inserting into whitespace or a newline should place `$NAME` at the cursor while preserving the surrounding characters. If the cursor points inside a cURL option token such as `-H`, the function should throw an `Error` with message `Cannot insert variable to option`. Calling it multiple times with the same arguments should produce the same string, and it should not mutate the argument object, touch the filesystem, use the network, or depend on hidden global state."} {"task_id": "format-code-task-000740", "source_id": "format-code-task-000740", "domain": "code", "task_path": "tasks/format-code-task-000740", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1154537c03ee513d71558f3373bc4a7ca9864f3d5483542908f4b3f28ebe846a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nInheritance works with task parameters e.g:\n\n```ini\n[runtime]\n [[FAM]]\n [[task]]\n inherit = FAM\n```\n\nHowever, when mixing parameters across inheritance it only partially works.\n\n```ini\n[runtime]\n [[FAM]]\n [[task]]\n inherit = FAM\n```\n\n### Example\n\n```ini\n[task parameters]\n a = 1..2\n b = 1..2\n\n[scheduling]\n [[graph]]\n R1 = \"\"\"\n \n \"\"\"\n\n[runtime]\n [[]]\n inherit = \n script = test $b -eq 1\n\n [[]]\n [[[environment]]]\n b = %(b)d\n```\n\nThe inheritance does indeed work as shown by the output of `cylc config`:\n\n```console\n$ cylc config --sparse param-test \n[task parameters]\n a = 1, 2\n b = 1, 2\n[scheduling]\n cycling mode = integer\n initial cycle point = 1\n final cycle point = 1\n [[graph]]\n R1 = \n[runtime]\n [[root]]\n [[_a1]]\n inherit = _b1\n script = test $b -eq 1\n [[[environment]]]\n b = %(b)d\n [[_a2]]\n inherit = _b1\n script = test $b -eq 1\n [[[environment]]]\n b = %(b)d\n [[_b1]]\n [[[environment]]]\n b = %(b)d\n [[_b2]]\n [[[environment]]]\n b = %(b)d\n[visualization]\n [[node attributes]]\n```\n\nHowever, the parameter in the environment variable is not expanded in the job script:\n\n```bash\n# job\n\ncylc__job__inst__user_env() {\n # TASK RUNTIME ENVIRONMENT:\n export b\n b=\"%(b)d\"\n}\n```\n\n### Use Case\n\nExample use case which involves mapping one parameter onto another:\n\n```ini\n[runtime]\n # define environments\n [[environment]]\n\n # map models onto environments\n [[model]]\n inherit = environment<1>\n [[model]]\n inherit = environment<2>\n [[model]]\n inherit = environment<1>\n```"} {"task_id": "format-code-task-000741", "source_id": "format-code-task-000741", "domain": "code", "task_path": "tasks/format-code-task-000741", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:0c98e4bd100d00f3907ef687bd495a79f2dbdf88a58693c6e5ab82fa58f90990", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI’m using Cython with C++20/23 code and keep having to write little wrappers because `libcpp` doesn’t expose things like `std::gcd`/`std::lcm`, container `.contains()`, or `std::string` helpers like `starts_with`, `ends_with`, and `contains`. It would be really nice if I could just cimport/use these standard library APIs directly from Cython.\n\n# Expected outcomes\n\n- Cython C++ code can cimport and call modern numeric helpers from `libcpp.numeric`, including `gcd`, `lcm`, and `midpoint`, with the corresponding standard-library behavior.\n- The standard ordered and unordered associative containers exposed by `libcpp` support their C++ membership query through `.contains(...)`, returning whether the requested key or value is present.\n- `libcpp.string.string` supports the standard prefix, suffix, and substring-style helpers `starts_with(...)`, `ends_with(...)`, and `contains(...)` for normal Cython byte/character string inputs, returning the corresponding boolean result.\n\n# Notes\n\nThese APIs should be available through normal Cython `cimport` usage in C++ mode and should work under the appropriate C++ standard level for the underlying standard-library feature."} @@ -669,11 +643,9 @@ {"task_id": "format-code-task-000771", "source_id": "format-code-task-000771", "domain": "code", "task_path": "tasks/format-code-task-000771", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6ebbd0a3c16a151219811185328cdef7d502b11af7ab1e059ac980704b7d43d6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `dcos-launch` library API is awkward to use — every launcher method demands the config/info dict be passed in again\n\nI'm trying to use `dcos-launch` as a library (not just through the CLI) to spin up a cluster, wait for it, run some checks, and tear it down. The current launcher API feels really clunky:\n\n```python\nimport launch, launch.config\n\nconfig = launch.config.get_validated_config(config_path)\nlauncher = launch.get_launcher(config)\ninfo = launcher.create(config)\nlauncher.wait(info)\nlauncher.describe(info)\nlauncher.test(info, 'py.test')\nlauncher.delete(info)\n```\n\nA couple of things bother me here:\n\n1. I already handed `config` to `get_launcher(...)` so it could build the right `BotoWrapper` / `AzureWrapper`. Then I have to hand the same `config` to `create(...)` again. Why does the launcher need it twice?\n\n2. After `create`, every subsequent call (`wait`, `describe`, `test`, `delete`) needs me to thread the `info` dict back in as the first argument. The launcher object itself knows which deployment it's responsible for — at least it should — so making me carry `info` around on every call feels redundant. If I forget and call `launcher.wait()` I get a `TypeError`; if I accidentally pass a stale dict I get really confusing behavior.\n\nThe natural way to use a launcher feels like:\n\n```python\nlauncher = launch.get_launcher(config_or_info)\nlauncher.create()\nlauncher.wait()\nlauncher.describe()\nlauncher.test('py.test')\nlauncher.delete()\n```\n\ni.e. the launcher should own the configuration / deployment state it needs, and each method just acts on that state. `create()` still returns the info dict so I can persist it to disk for a later process to pick back up via `get_launcher(info)`.\n\nCould the AWS and Azure launchers (and the CLI that drives them) be refactored so callers don't have to keep feeding the same dict back in on every method call?"} {"task_id": "format-code-task-000772", "source_id": "format-code-task-000772", "domain": "code", "task_path": "tasks/format-code-task-000772", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:31fe0dd1c938c3a4820171182b8e82fc156a6540df1701a95527e2588748b9e4", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI'm writing a plugin and want my own store that just lets consumers subscribe via addChangeListener, but the only BaseStore I can see in the codebase comes bundled with this get/set thing that auto-dispatches APP_STORE_CHANGE through PluginSDK — which I really don't want my plugin store doing.\n\nCould we expose a lean BaseStore through PluginSDK that's basically just the change-listener part, and keep the get/set+dispatch behavior as a separate thing for stores that actually need it?\n\nWould make it way easier to build plugin-side stores without inheriting the whole app-store machinery."} {"task_id": "format-code-task-000773", "source_id": "format-code-task-000773", "domain": "code", "task_path": "tasks/format-code-task-000773", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:de65abd3c8960ba51196b633e94ce2a22f2552c2c43c63367b51a42cb1bc70a4", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want a `RandomForest` model class for NumPy arrays that I can use as `RandomForest(n_trees, max_depth, n_feats, classifier=True, criterion=\"entropy\")`, followed by `fit(X, Y)` and then `predict(X)`. Calling `fit` should build `n_trees` independent decision trees, each trained on a bootstrap sample of the training rows drawn with replacement, while passing through `max_depth`, `n_feats`, `criterion`, and `classifier` to each tree.\n\nAfter fitting, `predict(X)` should return a one-dimensional NumPy array with one prediction for each input row. In classification mode, it should aggregate the trees by majority vote over integer class labels, choosing the smallest class label when vote counts tie. For example, after `np.random.seed(0)`, fitting `RandomForest(n_trees=3, max_depth=2, n_feats=1, classifier=True, criterion=\"entropy\")` on `X=np.array([[0.0], [1.0], [2.0]])` and `Y=np.array([1, 1, 1])` should make `predict(np.array([[10.0], [-5.0]]))` return `np.array([1, 1])`.\n\nIn regression mode, the same class should be usable with `classifier=False` and `criterion=\"mse\"`, and `predict` should average the numeric predictions from all trees. For example, after fitting `RandomForest(n_trees=4, max_depth=2, n_feats=1, classifier=False, criterion=\"mse\")` on `X=np.array([[0.0], [1.0], [2.0]])` and `Y=np.array([2.5, 2.5, 2.5])`, `predict(np.array([[10.0], [-5.0]]))` should return `np.array([2.5, 2.5])`."} -{"task_id": "format-code-task-000775", "source_id": "format-code-task-000775", "domain": "code", "task_path": "tasks/format-code-task-000775", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4fde5d5ac1e4781d3b5521659679f624a299fa0aa35563a9af9ad37c049563cb", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want a stateful Go API facade for managing iCode deployment and execution. The package should expose an ICodeApi type and NewICodeApi(containerService ivm.ContainerService, gitService ivm.GitService, eventService common.EventService) ICodeApi so callers can wire their container, Git, and event implementations once and then use the same API value across deploy, execute, list, and undeploy calls.\n\nICodeApi needs Deploy(baseSaveUrl string, gitUrl string, sshPath string, password string) (ivm.ICode, error) and DeployFromRawSsh(baseSaveUrl string, gitUrl string, rawSsh []byte, password string) (ivm.ICode, error). Deploy should call the Git service clone path with those arguments, start the container for the returned ivm.ICode, publish an icode.created event containing the iCode ID, path, version, commit hash, Git URL, and repository name, then return that same ivm.ICode with a nil error. DeployFromRawSsh should do the same flow but use the raw SSH clone path and preserve the raw key bytes and password when it calls the Git service. If cloning fails, either deploy method should return the zero ivm.ICode and that error without starting a container or publishing an event; if container start fails, it should return the zero ivm.ICode and that error without publishing an event; if publishing icode.created fails after the container starts, it should return the zero ivm.ICode with a nil error.\n\nICodeApi also needs UnDeploy(id ivm.ID) error. It should stop the matching container first; if stop fails, return that error and do not publish anything. When stop succeeds, publish the iCode removal event carrying the iCode ID and return the publish result.\n\nFor execution, ICodeApi needs ExecuteRequest(request ivm.Request) (ivm.Result, error), which directly forwards the request to the configured container service, and ExecuteRequestList(requestList []ivm.Request) []ivm.Result, which processes requests in order and returns one result per input request. If an individual request fails, the list result for that position should be ivm.Result{Err: err.Error()} and later requests should still run. Finally, GetRunningICodeList() []ivm.ICode should return the running iCodes reported by the configured container service, so a session can deploy an iCode, observe it in the running list, execute requests against it, undeploy it, and observe that it is no longer running."} {"task_id": "format-code-task-000776", "source_id": "format-code-task-000776", "domain": "code", "task_path": "tasks/format-code-task-000776", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:982e60f4a277ebd0417cabb3d10341dd9b019c4744b2bf2f47c67102f19f12f2", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Feature request: fallback / conditional transforms for summary string templates\n\nI'm using summary string templates with filter syntax to format entry summaries. Right now I can use `upper`, `lower` and `date('')`, which is great, but I keep running into two cases that aren't covered.\n\n### 1. Fallback when a field is empty\n\nSome entries in my collection don't have every field filled in. For example, I have an optional `subtitle` field, and when it's missing my summary ends up with a dangling separator or an empty section:\n\n```yaml\ncollections:\n - name: 'posts'\n label: 'Posts'\n folder: '_posts'\n summary: \"{{title}} — {{subtitle}}\"\n fields:\n - { label: 'Title', name: 'title', widget: 'string' }\n - { label: 'Subtitle', name: 'subtitle', widget: 'string', required: false }\n```\n\nI'd like a way, from within the template syntax, to say \"if this field is empty, use this literal string instead\" — so I can write something like `{{subtitle | }}` and get `Untitled` when the field is blank, without having to write a custom preview/summary component just for that.\n\n### 2. Pick one of two values based on whether a field is set\n\nRelated, but slightly different: sometimes I don't want to print the field's value at all, I just want to branch on whether it's truthy and emit one string or another. E.g. a `featured` boolean controlling whether the summary shows `★` or nothing, or a `draft` flag controlling whether to show `(draft)` or `(published)`.\n\nToday the only way I can do this is by post-processing the summary outside of the CMS config, which defeats the point of having the filter syntax.\n\nCould the template filter pipeline be extended to cover these two cases? They feel like a natural extension of the existing `upper` / `lower` / `date(...)` filters and would remove a lot of awkwardness around optional / boolean fields in summary strings.\n\nNaming-wise I'd expect something like `default('...')` for case 1 and `ternary('...', '...')` for case 2, to match the existing filter call style."} {"task_id": "format-code-task-000777", "source_id": "format-code-task-000777", "domain": "code", "task_path": "tasks/format-code-task-000777", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6756afa426495a254bb2cfed85d9d5db7586aabc48b6febbb969f273d8c3625a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Cannot extend the new role-based model with custom manage roles\n\nWe're rolling out the new aggregation-based role model from `user-authz` to our org and we'd like to compose our own scopes / capabilities on top of it. Two concrete cases:\n\n**Case 1 — a custom scope.** The built-in scopes (`deckhouse`, `kubernetes`, `networking`, ...) don't match how we slice responsibilities internally. I'd like a single \"scope\" that bundles the admin level of the `deckhouse` scope, the admin level of the `kubernetes` scope, and everything from the `user-authn` module.\n\nSo I created a `ClusterRole`, marked it as a manage role, and used a plain Kubernetes `aggregationRule` whose selectors point at the labels of the existing built-in roles, e.g.:\n\n```yaml\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRole\nmetadata:\n name: custom:manage:mycustomscope:admin\n labels:\n rbac.deckhouse.io/kind: manage\n rbac.deckhouse.io/level: scope\n rbac.deckhouse.io/scope: custom\naggregationRule:\n clusterRoleSelectors:\n - matchLabels:\n rbac.deckhouse.io/kind: manage\n rbac.deckhouse.io/aggregate-to-deckhouse-as: admin\n - matchLabels:\n rbac.deckhouse.io/kind: manage\n rbac.deckhouse.io/aggregate-to-kubernetes-as: admin\n - matchLabels:\n rbac.deckhouse.io/kind: manage\n module: user-authn\nrules: []\n```\n\nAggregation itself works (the role ends up with the union of rules as expected). But when I create a `ClusterRoleBinding` against it for a user, **no namespaced `RoleBinding`s show up** — whereas if I bind the same user directly to `d8:manage:deckhouse:admin`, the use-role bindings appear in the deckhouse-managed namespaces as expected. So my custom scope role is effectively ignored by the machinery that materialises the namespaced bindings.\n\n**Case 2 — extending an existing scope with a new capability.** A separate operator team installed a new cluster-scoped CRD (`MySuperResource`). I want users who hold `d8:manage:deckhouse:admin` to also get get/list/watch on this resource. The natural thing is to add a small `ClusterRole` carrying the rules and a label that says \"aggregate me into the deckhouse manage scope\":\n\n```yaml\napiVersion: rbac.authorization.k8s.io/v1\nkind: ClusterRole\nmetadata:\n name: custom:manage:capability:mycustommodule:superresource:view\n labels:\n rbac.deckhouse.io/kind: manage\n rbac.deckhouse.io/aggregate-to-deckhouse-as: admin\nrules:\n - apiGroups: [mygroup.io]\n resources: [mysuperresources]\n verbs: [get, list, watch]\n```\n\nThe rules do get aggregated into `d8:manage:deckhouse:admin`, but if this capability lives in its own namespace and I want a corresponding namespaced use-role binding produced there, I have no way to express that — and nothing happens automatically.\n\n**What I'd expect:**\n- Custom `ClusterRole`s that mark themselves as `rbac.deckhouse.io/kind: manage` and use a standard `aggregationRule` should be first-class citizens of the new role model — they shouldn't need to look like internal Deckhouse roles to be recognised.\n- Binding a subject to such a custom manage role via `ClusterRoleBinding` should automatically produce the same kind of namespaced `RoleBinding`s that binding to a built-in `d8:manage:*` role produces, covering the namespaces of all the roles it (transitively) aggregates.\n- There should be documentation in the user-authz FAQ explaining the contract: which labels a custom role must carry, how to bolt a new capability onto an existing scope, how to introduce a brand-new scope, and how to make the hook create use-role bindings in a namespace that a new capability lives in. Right now operators have to read the hook source to guess at the rules."} {"task_id": "format-code-task-000778", "source_id": "format-code-task-000778", "domain": "code", "task_path": "tasks/format-code-task-000778", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:dd3aff081df374291e73af387ed179817d272183fd779ad5ccdb471b551f0465", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## After upgrading to 1.55, the `deckhouse` Service still has stale EndpointSlices and `cm/deckhouse` checks get stuck\n\nAfter updating Deckhouse to 1.55 I noticed something odd on the `deckhouse` Service in `d8-system`:\n\n```\n$ kubectl -n d8-system get endpointslices -l kubernetes.io/service-name=deckhouse\nNAME ADDRESSTYPE PORTS AGE\ndeckhouse IPv4 9650,9651,9652 5m\ndeckhouse-abcde IPv4 9650,9651,9652 30m\n```\n\nThere are **two** EndpointSlices for the same Service:\n\n- `deckhouse` — the one Deckhouse itself manages now (this is the new behavior in 1.55, fine)\n- `deckhouse-` — the old one the built-in endpointslice-controller generated from the Service's selector, left over from before the upgrade\n\nAs a result `cm/deckhouse` checks stay stuck and webhook traffic ends up hitting the wrong endpoint occasionally (the manually-managed slice points at the real deckhouse pod, the controller-managed one points at whatever the selector matches at the moment, and they disagree during rollout).\n\nLooking at the release notes / changelog it seems the intent in 1.55 was that Deckhouse takes over endpoint management itself and the old controller-generated slice gets cleaned up on startup. From the outside it does not look like that cleanup actually happens — I waited a long while, restarted the deckhouse pod, the `deckhouse-` slice keeps coming back / never goes away. Deleting it by hand with `kubectl delete endpointslice` works for a few seconds, then a new `deckhouse-` slice shows up again, presumably re-created by the endpointslice-controller because the Service still has its selector.\n\nExpected: after upgrading, the `deckhouse` Service in `d8-system` should end up with exactly one EndpointSlice — the one Deckhouse manages itself — and the stale controller-generated slice(s) should be gone for good (not re-created on the next reconcile)."} -{"task_id": "format-code-task-000779", "source_id": "format-code-task-000779", "domain": "code", "task_path": "tasks/format-code-task-000779", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4615245ec58fb8aa03b553d6d0b3107234ad18704cdbf7e9301b5ebdafc5747a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the cloud-provider validation library to expose `ValidateInstanceClassesEtcdDisk(state *State) Result` as a pure one-shot validator for provider InstanceClass `spec.etcdDisk` placement. The function should read `state.InstanceClassKind`, `state.NodeGroups`, and `state.InstanceClasses`, return a `Result`, and leave the supplied `State` and contained resources unchanged.\n\nWhen `state` is nil, it should return a blocking validation result with code `internal_state_nil`. When an InstanceClass has an empty kind or a kind equal to `state.InstanceClassKind`, and the NodeGroup named exactly `master` references it through `spec.cloudInstances.classReference.kind/name`, that InstanceClass must define `spec.etcdDisk`; otherwise the result should contain an error at `/.spec.etcdDisk` with code `master_etcd_disk_required`. For example, a `State` with `InstanceClassKind: \"DVPInstanceClass\"`, a `master` NodeGroup referencing `master-dvp`, and a `DVPInstanceClass` named `master-dvp` without `spec.etcdDisk` should return that error.\n\nWhen any non-`master` NodeGroup references an InstanceClass through a matching classReference kind and name, that InstanceClass must not define `spec.etcdDisk`; otherwise the result should contain an error at `/.spec.etcdDisk` with code `etcd_disk_forbidden_for_non_master` and the rejected `etcdDisk` value. For example, a `worker` NodeGroup referencing `worker-dvp` and a `DVPInstanceClass` named `worker-dvp` with `spec.etcdDisk: {}` should return this error. The validator should ignore NodeGroups without `cloudInstances.classReference`, references with a different kind or an empty name, and InstanceClasses whose non-empty kind differs from `state.InstanceClassKind`; unattached InstanceClasses may define `spec.etcdDisk` without an error. Calling it repeatedly with equivalent input should produce equivalent validation results and should not perform filesystem, network, or global-state side effects."} {"task_id": "format-code-task-000780", "source_id": "format-code-task-000780", "domain": "code", "task_path": "tasks/format-code-task-000780", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:dd9d201bd771cb450ca7b857531f76322da8b2aa5d8bd5ca6cde4fbaf98796b3", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## mempool: remove dead `isTreasuryEnabled` / `isAutoRevocationsEnabled` parameters\n\nA bunch of methods on `mempool.TxPool` currently require callers to pass\n`isTreasuryEnabled` and `isAutoRevocationsEnabled` flags, but the methods\nthemselves don't actually do anything with those flags — they're just\nthreaded through to the next call, which also doesn't use them.\n\nFor example, in `server.go` every time we want to evict something from the\npool we end up with code like this:\n\n```go\ntipHash := &s.chain.BestSnapshot().Hash\nisTreasuryEnabled, err := s.chain.IsTreasuryAgendaActive(tipHash)\nif err != nil {\n srvrLog.Errorf(\"Could not obtain treasury agenda status: %v\", err)\n}\n\nisAutoRevocationsEnabled, err :=\n s.chain.IsAutoRevocationsAgendaActive(tipHash)\nif err != nil {\n srvrLog.Errorf(\"Could not obtain automatic ticket revocations agenda \"+\n \"status: %v\", err)\n}\n\nnumEvicted := s.txMemPool.RemoveOrphansByTag(mempool.Tag(sp.ID()),\n isTreasuryEnabled, isAutoRevocationsEnabled)\n```\n\n…just to call into `RemoveOrphansByTag`, which forwards the two booleans to\n`removeOrphan`, which… also doesn't read them. The same pattern shows up\naround `RemoveTransaction`, `RemoveDoubleSpends`, `RemoveOrphan`, and friends\non the public surface of `TxPool`, and across a number of the internal\nhelpers that back them.\n\nThese parameters are effectively dead weight on the API: callers have to go\nfetch agenda state from the chain solely to satisfy a signature, the values\nthen get tunneled through several layers of mempool internals, and nothing\never actually consumes them.\n\nIt would be nice to clean this up — drop the unused agenda flag parameters\nfrom the affected `TxPool` methods and simplify the call sites accordingly,\nso callers no longer have to query agenda status just to feed parameters\nthat don't do anything."} {"task_id": "format-code-task-000781", "source_id": "format-code-task-000781", "domain": "code", "task_path": "tasks/format-code-task-000781", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2135753b7dc42e8824a1ce0aa1dc9e38254bf57b6abf612cef05c569c7c71729", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nThe CoSi package is used at a network boundary: callers receive a public-key roster, a message, a participation policy, and signature bytes that may be truncated, oversized, or deliberately malformed. Harden this public surface so malformed inputs are ordinary verification failures, never process panics, while keeping the existing wire format and valid-signature behavior intact. Verify must require a signature containing exactly one encoded commitment, one encoded response, and the roster-sized participation mask; reject masks with bits set beyond the roster; and reject empty, nil-entry, or duplicate-key rosters before attempting cryptographic verification. The default policy remains the complete-roster policy, while a valid threshold policy continues to authorize a signature when enough listed participants contributed. Threshold values that cannot describe a non-empty roster must never authorize a mask. The Mask API must likewise be total over caller-provided indices: negative or out-of-range indices return errors, and rejected SetMask calls (wrong length or out-of-range bits) leave both the mask and aggregate public key unchanged. Existing successful complete and threshold signatures must continue to verify, and all of these failures must be reported through returned errors rather than panics."} {"task_id": "format-code-task-000783", "source_id": "format-code-task-000783", "domain": "code", "task_path": "tasks/format-code-task-000783", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:e07e4bc66d9c2557408aa5d03370a43a3c02a1cddfa109f51db271280bd85a82", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want a public `process_context_with_edu_rerank(processor: EduRerankProcessor, context: str, query: str, temp_dir: str = \"temp\", top_k_per_level: int = 3) -> tuple[str, dict]` helper for one-shot LongBench context compression. It should take raw context text, write it to a temporary `.txt` file under `temp_dir`, call `processor.parse_file()` on that file, delete the temporary file afterward, then call `processor.semantic_filter(parsed_data, query, top_k_per_level=top_k_per_level)` and return the filtered text plus stats.\n\nThe stats dict should always use the keys `orig_tokens`, `new_tokens`, and `ratio`. Token counts should use `tiktoken`'s `cl100k_base` encoding when available, with special tokens disallowed, and otherwise fall back to `len(text) // 4`; successful compression should report `ratio` as `new_tokens / orig_tokens` rounded to 4 decimal places. For an empty context, return `(\"\", {\"orig_tokens\": 0, \"new_tokens\": 0, \"ratio\": 0.0})` without calling the processor. If writing the temp file fails, parsing returns no data, or semantic filtering returns an empty string, return the original context with `new_tokens == orig_tokens` and `ratio == 1.0`.\n\nFor example, with a processor whose `parse_file()` returns parsed data and whose `semantic_filter()` returns `\"Chapter 2: Methods\"`, calling the helper with a non-empty context and query should return `\"Chapter 2: Methods\"` and stats computed from the original and filtered text. With a processor whose `parse_file()` returns `None`, the same non-empty input should return the original context unchanged and a ratio of `1.0`. Running the module directly should also act as a small demonstration: create an `EduRerankProcessor`, process a sample context and query, and print the original token count, filtered token count, compression ratio, and filtered text."} @@ -688,8 +660,6 @@ {"task_id": "format-code-task-000794", "source_id": "format-code-task-000794", "domain": "code", "task_path": "tasks/format-code-task-000794", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:e7ec160c032646ee9b580ea9c465f515acbeab98177ead492508b35dcbea7ed6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the stateful EVM library to support nested contract-call execution when bytecode run through `FakeBlockchain` and `chain.vm.runCode(environment)` reaches the `CALL` (`0xf1`), `CALLCODE` (`0xf2`), or `DELEGATECALL` (`0xf4`) opcodes.\n\nFor `CALL`, the opcode should pop gas, target address, value, input memory offset, input size, return memory offset, and return size from the stack; read the requested input bytes from caller memory; execute the target account's code in a nested frame whose account is the target, whose caller is the current account, whose value is the popped value, and whose depth is one greater than the caller. For `CALLCODE`, it should execute the target account's code while keeping the current account as the execution account and using the current account as caller. For `DELEGATECALL`, it should execute the target account's code while keeping the current execution account and current caller, and with zero call value.\n\nEach nested call should run inside a checkpointed blockchain layer. If the nested frame stops without reverting, commit that layer, push `1` to the caller stack, copy up to the requested return size into caller memory at the requested return offset with zero padding, store the full nested return bytes as the caller's last return data, and advance the caller program counter past the call opcode. If the nested frame reverts or otherwise does not finish cleanly, roll back the layer, push `0` to the caller stack, clear the caller's last return data, leave return memory uncopied, and still advance past the call opcode.\n\nA concrete session should work like this: create `const chain = new FakeBlockchain()`, install an account at address `\"2\"` whose code stores `0x2a` in memory and returns 32 bytes, then run caller bytecode that pushes return size `32`, return offset `0`, zero input size and offset, zero value, address `2`, gas, and executes `CALL`. The resulting `state.stack` should contain a success flag of `1`, `state.memory` should contain the 32 returned bytes at offset `0`, and `state.lastReturned` should equal those 32 bytes. If the target account instead writes storage and then executes `REVERT`, the caller should receive stack flag `0`, the target storage write should not be visible through the blockchain after the call, and `state.lastReturned` should be an empty array."} {"task_id": "format-code-task-000795", "source_id": "format-code-task-000795", "domain": "code", "task_path": "tasks/format-code-task-000795", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d8911905f04bda308fe8633678ad42b6dd30ffc120c2d87c86ac2633f30a2b6a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n'path can't be empty'\nWhen mounting only a router created with `MosaicTilerFactory` without any prefix, FastAPI will error with `\"Exception: Prefix and path cannot be both empty (path operation: read)\"`\n\nhttps://github.com/developmentseed/titiler/blob/f2821b9421ecad0e1a79356fc82c3f6ee39833f5/titiler/endpoints/factory.py#L720-L725\n\nThis will be a **breaking change** for the application that are already build on top of titiler\n\nIn order to make a smooth transition we could maybe do \n```python\n@self.router.get(\n \"\",\n response_model=MosaicJSON,\n response_model_exclude_none=True,\n responses={200: {\"description\": \"Return MosaicJSON definition\"}},\n deprecated=True,\n)\n@self.router.get(\n \"/\",\n response_model=MosaicJSON,\n response_model_exclude_none=True,\n responses={200: {\"description\": \"Return MosaicJSON definition\"}},\n)\n```"} {"task_id": "format-code-task-000796", "source_id": "format-code-task-000796", "domain": "code", "task_path": "tasks/format-code-task-000796", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:356694eb7c8ac00faace33c93fa27b5d2890b240a87813daf647ed6cb0aed844", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### Cannot create multiple `JsonApi` clients in the same app\n\nI'm using `devour-api-client` in a project that talks to two different JSON-API backends — our main app API and a separate analytics API. They live on different hosts and need different headers, so I want one Devour client per backend.\n\nThe current bootstrap is:\n\n```js\nimport JsonApi from 'devour-api-client'\n\nlet mainApi = JsonApi.getInstance()\nmainApi.setup('http://main.example.com')\nmainApi.headers['x-auth'] = 'token-for-main'\n\nlet analyticsApi = JsonApi.getInstance()\nanalyticsApi.setup('http://analytics.example.com')\nanalyticsApi.headers['x-auth'] = 'token-for-analytics'\n```\n\nAfter this runs, `mainApi` and `analyticsApi` are the same object. The second `setup(...)` call overwrites the `apiUrl` and headers of the first one, and any models I defined on `mainApi` show up on `analyticsApi` too. I end up with one shared client instead of two.\n\nLooking at the README, `JsonApi.getInstance()` seems to be the only documented way to obtain a client, and it always hands back the same instance. That makes it impossible to use the library against more than one API at a time, or to have isolated clients in tests.\n\nCould the API be changed so I can create independent `JsonApi` clients? Something where each client has its own `apiUrl`, headers, middleware stack and registered models, and configuring one doesn't leak into another. Happy to update the README example to match."} -{"task_id": "format-code-task-000797", "source_id": "format-code-task-000797", "domain": "code", "task_path": "tasks/format-code-task-000797", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:80137d00cad32b8421c2a23fe661b4733c887550d2653d235ef605b582389cef", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Add subnet-level metrics for canister snapshot usage\n\nWe're operating an IC subnet and starting to see real use of the canister snapshot feature. From the operator side, snapshots are a resource users can create that consumes subnet memory, with per-canister limits — basically the same shape as wasm memory, stable memory, queue memory, cycles balance, etc.\n\nThe problem is that snapshots are basically invisible from the subnet's `/metrics` output. We can scrape things like:\n\n- `scheduler_canister_balance_cycles_total`\n- `replicated_state_registered_canisters{status=...}`\n- canister wasm / stable memory histograms\n- queue memory / response bytes\n\n…but there is no aggregate signal for snapshots. We can't answer two pretty basic capacity questions from Prometheus:\n\n1. How many canister snapshots currently exist on this subnet?\n2. How much memory are they using in total?\n\nBoth questions matter for capacity planning and for alerting (e.g. notice when snapshot memory grows unexpectedly, or when adoption ramps up after a release). Right now the only way to get either number is to walk the replicated state out-of-band, which doesn't help us when we're staring at a Grafana dashboard.\n\nCould the scheduler expose these as subnet-wide gauges, refreshed each round, alongside the other per-round scheduler metrics? That way they show up in the existing scrape and we can graph / alert on them like everything else. To fit our existing dashboards, please expose them under the names `scheduler_canister_snapshots_memory_usage_bytes` (total snapshot memory in bytes) and `scheduler_num_canister_snapshots` (snapshot count)."} -{"task_id": "format-code-task-000798", "source_id": "format-code-task-000798", "domain": "code", "task_path": "tasks/format-code-task-000798", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b3546b05738281528e8b62c58599b9aa937ffa4f3b81e4137d9f867836489120", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## NNS init CSV parser no longer accepts `dissolve_delay_s` / `maturity_e8s_equivalent`\n\nI'm using `add_all_neurons_from_csv_file` to bootstrap NNS governance with a set of initial neurons (similar to `rs/nns/integration_tests/src/neurons.csv`). I want each neuron in that CSV to have a configurable dissolve delay and an initial maturity.\n\nWhen I add `dissolve_delay_s` and `maturity_e8s_equivalent` columns to the CSV header, init blows up on the header check — the parser only accepts the fixed 6-column schema (`neuron_id;owner_id;created_ts_ns;staked_icpt;follows;not_for_profit`) and rejects anything else.\n\nIf I drop those columns and stick to the 6-column schema, init succeeds, but then every neuron ends up with a dissolve delay of 1 second regardless of what I wanted, and maturity is always 0. So there's currently no way to configure these two per-neuron values from the CSV at all.\n\nThis used to be supported (or at least the field names suggest it was intended to be), so it feels like a regression. Could the CSV format be updated so that `dissolve_delay_s` and `maturity_e8s_equivalent` are recognized again and actually flow into the resulting `Neuron`? The committed `neurons.csv` test fixture should also be updated to match."} {"task_id": "format-code-task-000799", "source_id": "format-code-task-000799", "domain": "code", "task_path": "tasks/format-code-task-000799", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:9ca0198f4cf70025e5d24e42380f926e3c3b556f04e6c4d0594c366d0f3bbcb0", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want this JWT library to provide verified parsing as a direct library API. The public API should include `type Keyfunc func(*Token) (interface{}, error)`, `func Parse(tokenString string, keyFunc Keyfunc) (*Token, error)`, `func ParseWithClaims(tokenString string, claims Claims, keyFunc Keyfunc) (*Token, error)`, `func (p *Parser) Parse(tokenString string, keyFunc Keyfunc) (*Token, error)`, and `func (p *Parser) ParseWithClaims(tokenString string, claims Claims, keyFunc Keyfunc) (*Token, error)`.\n\nFor a valid compact JWT signed with HS256 using the key `[]byte(\"AllYourBase\")`, calling `Parse` with a key callback that returns that key should return a `*Token` with decoded header and map claims, the third segment copied into `Token.Signature`, `Token.Valid == true`, and a nil error. For a token containing custom claims, calling `ParseWithClaims(tokenString, &MyClaims{}, keyFunc)` should decode the payload into the supplied claims type and return it on `token.Claims` when the signature and registered claims are valid.\n\nValidation failures should return a `*ValidationError` instead of a valid token. A missing key callback should set `ValidationErrorUnverifiable`; a key callback error should be wrapped as unverifiable; an expired or not-yet-valid claim should set the corresponding registered-claim validation bit; and a bad signature should set `ValidationErrorSignatureInvalid`. If `Parser.ValidMethods` is set, parsing should reject tokens whose header `alg` is not in that list with a signature-invalid validation error. If `Parser.SkipClaimsValidation` is true, parsing should still verify the signature but should not fail only because `exp`, `iat`, or `nbf` claims are outside the current time."} {"task_id": "format-code-task-000800", "source_id": "format-code-task-000800", "domain": "code", "task_path": "tasks/format-code-task-000800", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:67488ab2322f5073873c6bb163729a50240a18f9350ce60c61b9fab67e21d712", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want a `request` package for parsing JWTs directly from `*http.Request` values without hand-extracting the token string first. It should expose `ParseFromRequest(req *http.Request, extractor Extractor, keyFunc jwt.Keyfunc, options ...ParseFromRequestOption) (*jwt.Token, error)`, where the extractor finds the raw token, the default claims type is `jwt.MapClaims`, the default parser is `&jwt.Parser{}`, extractor errors are returned unchanged, and successful extraction is parsed with `ParseWithClaims` and the supplied key callback. It should also expose `ParseFromRequestWithClaims(req *http.Request, extractor Extractor, claims jwt.Claims, keyFunc jwt.Keyfunc) (*jwt.Token, error)` as the custom-claims convenience form, plus `WithClaims(claims jwt.Claims)` and `WithParser(parser *jwt.Parser)` options.\n\nI need an `Extractor` interface with `ExtractToken(*http.Request) (string, error)` and a shared `ErrNoTokenInRequest` error for the no-token case. `HeaderExtractor{\"X-Token\"}` should return the first non-empty matching header value, so a request with `X-Token: abc.def.ghi` returns `\"abc.def.ghi\", nil`; with none of the configured headers present it returns `\"\", ErrNoTokenInRequest`. `ArgumentExtractor{\"token\"}` should read query or parsed form arguments, so a request for `/?token=abc.def.ghi` returns that value, and a request with no matching argument returns `ErrNoTokenInRequest`.\n\nI also need composition helpers: `MultiExtractor{HeaderExtractor{\"X-Token\"}, ArgumentExtractor{\"token\"}}` should try each extractor in order, return the first token it finds, skip `ErrNoTokenInRequest`, return the first other error immediately, and return `ErrNoTokenInRequest` if every extractor misses. `PostExtractionFilter` should wrap another extractor and transform a found token with a `func(string) (string, error)`, returning the filter's token or error; if the wrapped extractor misses or errors, that result should pass through.\n\nFor OAuth-style requests, `AuthorizationHeaderExtractor` should read the `Authorization` header and strip a leading `Bearer ` prefix case-insensitively, so `Authorization: Bearer abc.def.ghi` and `Authorization: bearer abc.def.ghi` both extract `abc.def.ghi`, while a non-bearer header value is returned unchanged. `OAuth2Extractor` should first use that authorization-header behavior and then fall back to the `access_token` request argument; for example, if both an Authorization bearer token and `?access_token=other` are present, the header token wins, and if only `?access_token=abc.def.ghi` is present, that argument is used. Calling `ParseFromRequest` with `OAuth2Extractor` and a valid signed JWT from either location should return a parsed token with the expected claims; calling it on a request where the extractor finds nothing should return `ErrNoTokenInRequest` and no token."} {"task_id": "format-code-task-000802", "source_id": "format-code-task-000802", "domain": "code", "task_path": "tasks/format-code-task-000802", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ec29ba56fbeecaa9a155f66b087ace9aa03907c4186e86f7610bbf9d543d4482", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nWhen using Dragonfly `IntegerRef` \"extras\" with the engine language set to German, numbers can't be spoken naturally as whole words. Instead, they must be spoken separately with short pauses. For example, one would have to say \"ein und dreissig\" instead of \"einunddreissig\" to match 31.\n\nIt should be possible to change Dragonfly's German number implementation ([number.py](https://github.com/dictation-toolbox/dragonfly/blob/master/dragonfly/language/de/number.py)) to accept either way of pronouncing German numbers.\n\nThanks @tripfish for reporting this on Gitter last month. I should have opened this issue back then, sorry."} @@ -716,7 +686,6 @@ {"task_id": "format-code-task-000827", "source_id": "format-code-task-000827", "domain": "code", "task_path": "tasks/format-code-task-000827", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ba7b1d3705768ef363d0656cc594e33dd853cb0653de1f737fd61f6b103e6490", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Persist an old → new commit-hash mapping during migration\n\nWhen a repository is migrated to the new storage format, every commit is\nrewritten and gets a brand-new commit hash. Today there is no way to find out\nwhich migrated commit a given pre-migration hash turned into, which makes it\nhard for tooling and users to correlate references, scripts, or external\nrecords against the migrated history.\n\nExtend the migration so that, once it finishes, the migrated database records\nthe full correspondence between the old and new commit hashes.\n\nThe mapping must be discoverable through normal SQL:\n\n- The migrated database has a branch named `dolt_migrated_commits`.\n- On that branch there is a table named `dolt_commit_mapping` with two\n `varchar` columns:\n - `old_commit_hash` — the commit's hash before migration; this is the\n primary key and is never null.\n - `new_commit_hash` — the corresponding commit's hash after migration.\n- The table contains exactly one row per migrated commit: every commit in the\n migrated history is represented, and `old_commit_hash` values are unique.\n- Every `new_commit_hash` is a real commit in the migrated history (i.e. it\n appears in `dolt_log`), and every migrated commit is the target of some row.\n- `old_commit_hash` holds the *pre-migration* hash, which is distinct from any\n post-migration commit hash.\n\nA typical way to read the mapping back is a revision-qualified query such as:\n\n```sql\nSELECT old_commit_hash, new_commit_hash\nFROM `dolt/dolt_migrated_commits`.dolt_commit_mapping;\n```\n\nAll existing migration behavior — commit-graph traversal, working-set\nmigration, tag migration, and branch head mapping — must continue to work\nunchanged alongside this new persisted artifact.\n"} {"task_id": "format-code-task-000828", "source_id": "format-code-task-000828", "domain": "code", "task_path": "tasks/format-code-task-000828", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:9f5405d1d919d3443e0a9d264599b8a4eee3ebc1631da2d55106477fccfe89f7", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want react-image-crop to expose pure TypeScript helper functions for preparing an initial aspect-ratio crop before passing it to the React component.\n\n`makeAspectCrop(crop: Pick & Partial>, aspect: number, containerWidth: number, containerHeight: number): PercentCrop` and `makeAspectCrop(crop: Pick & Partial>, aspect: number, containerWidth: number, containerHeight: number): PixelCrop` should take a partial crop and fill in the missing width or height so the result matches the requested aspect ratio while preserving the input unit. For example, `makeAspectCrop({ unit: '%', width: 50 }, 16 / 9, 400, 300)` should return `{ unit: '%', x: 0, y: 0, width: 50, height: 37.5 }`. If the requested aspect crop would overflow the container, it should shrink the overflowing dimension to fit; for example, `makeAspectCrop({ unit: 'px', x: 300, y: 0, width: 200 }, 1, 400, 300)` should return `{ unit: 'px', x: 300, y: 0, width: 100, height: 100 }`.\n\n`centerCrop(crop: Pick & Partial>, containerWidth: number, containerHeight: number): PercentCrop` and `centerCrop(crop: Pick & Partial>, containerWidth: number, containerHeight: number): PixelCrop` should center a partial crop within the container and preserve the input unit. For example, `centerCrop({ unit: 'px', width: 100, height: 50 }, 400, 300)` should return `{ unit: 'px', x: 150, y: 125, width: 100, height: 50 }`, and `centerCrop({ unit: '%', width: 50, height: 25 }, 400, 200)` should return `{ unit: '%', x: 25, y: 37.5, width: 50, height: 25 }`.\n\nBoth helpers should be deterministic, should not mutate the crop object passed in, and should not perform filesystem, network, or global-state side effects."} {"task_id": "format-code-task-000829", "source_id": "format-code-task-000829", "domain": "code", "task_path": "tasks/format-code-task-000829", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:234b888b4a3c97dbfb11d9046628b3d145a0a986df1da4a25c58bd843200d7cf", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `doorstop` with no subcommand to act as the project validation command. When I run it from a Doorstop working copy, it should load the tree, print a progress line like `validating items...`, and report traceability, review, outline, link, and external-reference problems with info, warning, or error severity.\n\nI also want the top-level validation flags `--no-reformat`, `--reorder`, `--no-level-check`, `--no-ref-check`, `--no-child-check`, `--strict-child-check`, `--no-suspect-check`, `--no-review-check`, `--skip`, `--warn-all`, and `--error-all` to control which checks run and how issues are treated.\n\nOn success, if the tree has more than one document, it should print the drawn tree before exiting 0. If validation finds error-level problems, or the tree cannot be loaded, it should exit nonzero."} -{"task_id": "format-code-task-000830", "source_id": "format-code-task-000830", "domain": "code", "task_path": "tasks/format-code-task-000830", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d78047b140049a239b769749b633da6191abd1fbd63a65358b9e9dd497f09f68", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want Goja's JavaScript Runtime to support the BigInt-oriented DataView methods on existing DataView instances: DataView.prototype.getBigInt64(byteOffset, littleEndian), DataView.prototype.getBigUint64(byteOffset, littleEndian), DataView.prototype.setBigInt64(byteOffset, value, littleEndian), and DataView.prototype.setBigUint64(byteOffset, value, littleEndian).\n\nGiven `const dv = new DataView(new ArrayBuffer(8))`, calling `dv.setBigInt64(0, -2n, false)` should return `undefined` and a later `dv.getBigInt64(0, false)` should return `-2n`. With the same buffer, `dv.setBigUint64(0, 0x0102030405060708n, true)` should store the value in little-endian byte order, and `dv.getBigUint64(0, true)` should return `0x0102030405060708n` while `dv.getBigUint64(0, false)` observes the bytes as the opposite-endian value.\n\nThe methods should validate their receiver as a DataView and throw TypeError when called with an incompatible `this`. They should also respect the DataView byte offset, byte length, and detached-buffer checks: reading or writing eight bytes past the view bounds should throw RangeError, and using a detached ArrayBuffer should throw TypeError. The setters should require BigInt-compatible values and write exactly eight bytes into the underlying ArrayBuffer without changing the DataView's length or offset."} {"task_id": "format-code-task-000831", "source_id": "format-code-task-000831", "domain": "code", "task_path": "tasks/format-code-task-000831", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:882a64632bf07b902a785be6025b2599f3fed6a1eeb089f773d3de3c71b5da22", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `AfcService.rename(source: str, target: str) -> None` to move or rename a file or directory on the connected device media filesystem.\n\nIn a normal session, after `await afc.set_file_contents(\"source.txt\", b\"data\")`, calling `await afc.rename(\"source.txt\", \"dest.txt\")` should return `None`, `await afc.get_file_contents(\"dest.txt\")` should return `b\"data\"`, and trying to read `\"source.txt\"` should raise `AfcFileNotFoundError`. It should also support moving paths between existing folders, such as renaming `\"dir_a/dir_b/source.txt\"` to `\"dir_a/dest.txt\"` while preserving the file bytes. Renaming a path to itself should be a successful no-op that leaves the contents intact.\n\nIf the source path does not exist, `await afc.rename(\"missing.txt\", \"dest.txt\")` should raise `AfcFileNotFoundError`. If the source exists but the device rejects the target path or reports another AFC failure, that AFC error should be surfaced rather than being converted into a missing-source error. The method should accept the same path-like values as other `AfcService` path methods and convert them before sending the device request."} {"task_id": "format-code-task-000832", "source_id": "format-code-task-000832", "domain": "code", "task_path": "tasks/format-code-task-000832", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:94fc024a89543ea50babc995bc8407aef0b2f20c1840345c7814a255878c6287", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n[BUG] Async example wrong\nSeems like session for validator creates only on `__aenter__`\n\n```\nFile \"inapppy/asyncio/appstore.py\", line 47, in validate\n api_response = await self.post_json(receipt_json)\n File \"inapppy/asyncio/appstore.py\", line 30, in post_json\n async with self._session.post(\nAttributeError: 'NoneType' object has no attribute 'post'\n```\n\n**Working example for me**\n```python\nasync with validator:\n validation_result = await validator.validate(...)\n```"} {"task_id": "format-code-task-000833", "source_id": "format-code-task-000833", "domain": "code", "task_path": "tasks/format-code-task-000833", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2acab12e5d86fa76887cd2f903aee715dd8c0a8ff3e8c55f2088b686ee300c84", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want to use `SQLAInterface(model_class, session=None)` as a stateful data-access object for SQLAlchemy model mutations. It should provide `add(item: Model, commit: bool = True) -> None`, `edit(item: Model, commit: bool = True) -> None`, `delete(item: Model, commit: bool = True) -> None`, and `delete_all(items: list[Model]) -> None`.\n\nFor a normal session, `interface.add(book)` should add the model instance and commit immediately, so a later query in the same database can find the new row. If I call `interface.add(book, commit=False)`, the item should be added to the session without committing, so I can commit the transaction myself later. `interface.edit(book)` should merge the changed model instance and commit immediately, while `interface.edit(book, commit=False)` should merge without committing.\n\n`interface.delete(book)` should remove that model instance from the session and commit immediately, and `interface.delete(book, commit=False)` should delete without committing. When the model has file or image columns with stored filenames, deleting one item should also delete those managed files before removing the row. `interface.delete_all([book1, book2])` should delete every provided item, delete any managed files or images for each one, and commit once after the loop.\n\nIf SQLAlchemy raises an error during `add`, the interface should roll back the session and re-raise the original SQLAlchemy exception. If SQLAlchemy raises during `edit`, `delete`, or `delete_all`, the interface should roll back and raise `DatabaseException` with the original SQLAlchemy exception available as the cause."} @@ -743,11 +712,9 @@ {"task_id": "format-code-task-000857", "source_id": "format-code-task-000857", "domain": "code", "task_path": "tasks/format-code-task-000857", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2b2778e2d14d7b20e0a3063af6bb3b316f54887bba40c1e9d23337d0775f8fef", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Feature request: support spot allocation strategy in `instancesDistribution`\n\nI'm setting up spot nodegroups in eksctl using the `instancesDistribution` block on a NodeGroup. Today I can specify `instanceTypes`, `maxPrice`, `onDemandBaseCapacity`, `onDemandPercentageAboveBaseCapacity`, and `spotInstancePools`, but I don't see a way to control which spot allocation strategy the underlying Auto Scaling Group / MixedInstancesPolicy will use.\n\nThe ASG MixedInstancesPolicy supports two allocation strategies for spot:\n\n- `lowest-price` (what you effectively get today, since AWS defaults to it)\n- `capacity-optimized` — ASG picks instances from the deepest Spot capacity pools across the configured instance types\n\nThe capacity-optimized strategy is what I actually want for production workloads: I give it a broad list of instance types and let ASG pick from the pools least likely to be interrupted. Right now I can't express this through an eksctl config file — I have to drop down to raw CloudFormation or post-hoc edit the ASG, which defeats the point of declaring the nodegroup in eksctl.\n\nCould `instancesDistribution` grow a knob for this? My yaml would look roughly like:\n\n```yaml\nnodeGroups:\n - name: ng-capacity-optimized\n minSize: 2\n maxSize: 5\n instancesDistribution:\n instanceTypes: [\"t3.small\", \"t3.medium\"]\n maxPrice: 0.017\n onDemandBaseCapacity: 0\n onDemandPercentageAboveBaseCapacity: 50\n # something here to pick capacity-optimized vs lowest-price\n```\n\nBehavior I'd expect:\n\n- If I don't set it, nothing changes — eksctl produces the same template as today, and AWS' default kicks in.\n- If I do set it, the value flows through to the generated `MixedInstancesPolicy.InstancesDistribution` on the ASG.\n- Only the strategies that AWS actually supports should be accepted; anything else should fail validation up front rather than after CloudFormation rejects the stack.\n- The strategy and `spotInstancePools` interact in a not-entirely-obvious way at the AWS layer — eksctl should make that interaction sane (e.g. not silently produce a config the AWS API will refuse).\n\nDocs under `usage/spot-instances` and the config schema should mention the new field so people can discover it."} {"task_id": "format-code-task-000858", "source_id": "format-code-task-000858", "domain": "code", "task_path": "tasks/format-code-task-000858", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1699310e821314c103cbb0cf94c0f7593c976f98b1c8533c7971fcb5dc66d0b6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nNode kubectl unable to start due to incorrect Taints Argument\n\n\n\n\n**What were you trying to accomplish?**\n\n\nWe tried to create a new nodegroup that was supposed to be added to the cluster.\n\nThe nodegroup had the config:\n\n``` \ntaints:\n controller: \"true:NoSchedule\"\n```\n\n**What happened?**\n\n\nThe new nodegroup was created but failed to connect to the k8s cluster due to an invalid argument. An invalid `:` is at the beginning of the `--register-with-taints` argument.\n\n**How to reproduce it?**\n\nCreate a nodegroup with the following taints config using kubectl v0.47.0. (Tested on kubernetes 1.19)\n\n``` \ntaints:\n controller: \"true:NoSchedule\"\n```\n\n**Logs**\n\n\n```\nF0502 21:07:37.221415 8139 server.go:156] invalid argument \"controllers=:true:NoSchedule\" for \"--register-with-taints\" flag: invalid taint spec: controllers=:true:NoSchedule\n\n``` \n\n**Anything else we need to know?**\n\n\nThe problem is only observed on v0.47.0. It works with eksctl v0.46.0.\n\nThis behavior is tested in: https://github.com/weaveworks/eksctl/blob/fc1f3b4b5ed6364777ad9d8160af9be241dd2319/pkg/nodebootstrap/ubuntu_test.go#L120\n\nThe case of `{\"foo\": \"bar\"}` is covered, but `{\"foo\": \"true:bar\"}` is not tested.\n\n\n**Versions**\n\n```\n$ eksctl version\n0.47.0\n\n```\n@Legion2"} {"task_id": "format-code-task-000859", "source_id": "format-code-task-000859", "domain": "code", "task_path": "tasks/format-code-task-000859", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:74ebba0513416d56330d1b6696485d835f94a5799aafded73375a9ea33df2f5f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nPossibility to set preBootstrapCommands when using custom ami with managed nodegroups\n\n\n**What feature/behavior/change do you want?**\n\nWhen pinning AMI for a managed nodegroup, currently eksctl ignores preBootstrapCommands. It would nice to have preBoostrapCommands.\n\nAWS [blog](https://aws.amazon.com/blogs/containers/introducing-launch-template-and-custom-ami-support-in-amazon-eks-managed-node-groups/) talks about the workflow with eksctl, but eksctl does not respect preBootstrapCommands when using custom AMI.\n\n![image](https://user-images.githubusercontent.com/1823272/127633255-bc580729-da78-4214-adb4-3c7c2399889e.png)\n\n**Why do you want this feature?**\n\nThis will allow us to do additional configuration before bootstrapping."} -{"task_id": "format-code-task-000860", "source_id": "format-code-task-000860", "domain": "code", "task_path": "tasks/format-code-task-000860", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2859a11508554d8ea815c2af88eba9b0944cf29de42fb39eb76dd865101fefd5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nEnsure ES index names are lowercase\nWith https://github.com/elastic/beats/pull/18854 libbeat changed the default behavior for not not lowercasing all outputs by default, but instead setting index and pipeline names to lowercase in the standard idxmgmt implementation. \nAPM Server diverges from beats idxmgmt implementation, therefore APM Server would have needed to also update to this behavior. By not applying any change in APM Server but ugrading to libbeat changes, we introduced a regression where customized index names are no longer guaranteed to be lower case. \n\nIssue was reported in https://discuss.elastic.co/t/index-name-must-be-lowercase-after-upgrade-to-7-9-2/251433/7"} {"task_id": "format-code-task-000861", "source_id": "format-code-task-000861", "domain": "code", "task_path": "tasks/format-code-task-000861", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a11b2af550aec9217be9aecaf24d23d2577dc1485a01a34e54091700fe9cabd1", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Migrate `uwsgi/status` MetricSet to ReporterV2\n\nTracking issue: #10774\n\nThe `uwsgi/status` metricset under `metricbeat/module/uwsgi/status` is still using the legacy `Fetch()` interface that returns `([]common.MapStr, error)`. As part of the broader effort tracked in #10774, it should be moved over to the `ReporterV2` interface so that it's consistent with the other metricsets that have already been migrated.\n\nHeads-up: this one is a bit more involved than some of the other modules — it has more tests than usual and the module setup deviates from the typical pattern in a few places, so the migration is not a pure mechanical rename."} {"task_id": "format-code-task-000862", "source_id": "format-code-task-000862", "domain": "code", "task_path": "tasks/format-code-task-000862", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a04281312a6a05d8d422b34523c5df5fe019b9cb5123a26d38aa0e797789c73f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n[Metricbeat] Migrate `mysql/status` metricset to ReporterV2\n\nTracking the broader ReporterV2 migration in #10774. While going through the remaining metricsets that still implement the old `Fetch()` interface, `mysql/status` is one of the ones that hasn't been migrated yet.\n\nWe should update it to use `ReporterV2`, in line with the other metricsets that have already been converted."} {"task_id": "format-code-task-000863", "source_id": "format-code-task-000863", "domain": "code", "task_path": "tasks/format-code-task-000863", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b9e0491b10234cc91d9b8ee23611429701661dc59aee64612bebdd6613994efd", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nHi,I have met a problem as follows:\n\ni have use metricbeat to collect docker memory, but found that the data of memory (suce as memory usage) was different from the \"docker stats\", is it right ?\nmetricbeat: 7.6.0\n\n![image](https://user-images.githubusercontent.com/74529952/124690502-e59ff880-df0c-11eb-8866-29618c92c37e.png)\n\n![image](https://user-images.githubusercontent.com/74529952/124690523-edf83380-df0c-11eb-8758-28635bf6d11a.png)"} -{"task_id": "format-code-task-000864", "source_id": "format-code-task-000864", "domain": "code", "task_path": "tasks/format-code-task-000864", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:991cb92d1e6ea3eb4b494353f5c3ecb418b8e0e963c3a8ae00c53fc91b4a534b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nAPM Pod fails to start when using a keystore\nWhen using a keystore the APM Pod fails to start:\n\n```\n+ echo 'Initializing keystore.'\n+ /usr/share/apm-server/apm-server keystore create --force\nInitializing keystore.\nCreated apm-server keystore\n+ for filename in '/mnt/elastic-internal/secure-settings/*'\n+ [[ -e /mnt/elastic-internal/secure-settings/logging.verbose ]]\n++ basename /mnt/elastic-internal/secure-settings/logging.verbose\n+ key=logging.verbose\n+ echo 'Adding logging.verbose to the keystore.'\nAdding logging.verbose to the keystore.\n+ /usr/share/apm-server/apm-server keystore add logging.verbose /mnt/elastic-internal/secure-settings/logging.verbose\ncould not create secret for: [logging.verbose /mnt/elastic-internal/secure-settings/logging.verbose], you can only provide one key per invocation\n```\n\nSeems related to https://github.com/elastic/cloud-on-k8s/pull/1377/files#diff-a45727bb5c0ed9ac8b2a53155dfb83b8L100"} {"task_id": "format-code-task-000865", "source_id": "format-code-task-000865", "domain": "code", "task_path": "tasks/format-code-task-000865", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6fa30ad01e0717fa7db200e46749945239a65f27899ddd218e24892f273c4e59", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n[logstash] Reload k8s pod if the k8s secrets changed\n**Describe the feature:**\nRestart k8s pod when secrets changed\nShould to add `secretsechecksum` to the statefulset annotation. \n\n**Describe a specific use case for the feature:**\nWe updated secrets which mounted to the statefulset, but pod know about the only old secrets, pod should be restarted as in the case of `logstash-config` changed.\n\nI can prepare the **PR**."} {"task_id": "format-code-task-000866", "source_id": "format-code-task-000866", "domain": "code", "task_path": "tasks/format-code-task-000866", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:794361aff81f605be669b452eb5e35ee3d1f0d6ddfdf571136a196fbdd5fa403", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nKeep track of ingest_took statistic in bulk operation type.\nI'm currently writing a track that benchmarks an ingest processor and in order to see the impact of this ingest processor isolated from indexing itself, `ingest_took` field from bulk response should be examined.\n\nCurrently I check the service time (~~which I think is `took` field from bulk response~~), but that includes also the time it took the index the documents."} {"task_id": "format-code-task-000867", "source_id": "format-code-task-000867", "domain": "code", "task_path": "tasks/format-code-task-000867", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:e9068de1fe32a08502d944e9630a2c0b6da60a6f07221624bf9201a484988775", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nComponents disappear in certain cases.\nIn the `Sorting.js` container, we have the following code:\n\n```\nif (!searchTerm && results.length === 0) return null;\n```\n\nThe intent of this code was to hide the Component on the initial load of the Search UI experience, and not show it until it is needed.\n\nThere are few issues with this.\n\n1. Individual UI components should not be responsible for this. This is something that should happen at a top level IF it is needed. Not every user of the API will need this. Some users will not have an initial empty state.\n\n2. The check itself is not actually successfully checking for the initial empty state of the UI. It is possible to get back into this case where you have 0 results with no search term by some creative use of filters."} @@ -774,13 +741,11 @@ {"task_id": "format-code-task-000890", "source_id": "format-code-task-000890", "domain": "code", "task_path": "tasks/format-code-task-000890", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:34b33e7409c27cf9ac43c4144c4dbbe5a19b2e22c7be2cda104f487a4f1a6a1f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nAdd `allowFinally` flag to `catch-or-return`\n### Description\n\nI would like the option to allow a `finally()` method to follow a `catch()` and still result in a passing `catch-or-return` rule.\n\nThis is not a duplicate of #29 and #32 because what I am after is subtly different. Adding `finally` to `terminationMethod` will allow you to finish a promise with `finally()` _in place_ of a `catch()`, but I would like to allow the use of `finally()` _in addition_ to `catch()`.\n\ne.g. I still want to enforce that Promises are \"caught\", but allow for a `finally()` callback after it has been caught. There is currently no way to do this.\n\n### Example\n\n```javascript\n// valid when allowFinally: true\nshowSpinner = true;\nservice.doSomethingAsync()\n .then(response => {\n console.log('success!', response);\n })\n .catch(err => {\n console.log('error!', err);\n })\n .finally(() => {\n showSpinner = false;\n });\n\n// invalid when allowFinally: true\nshowSpinner = true;\nservice.doSomethingAsync()\n .then(response => {\n console.log('success!', response);\n })\n .finally(() => {\n showSpinner = false;\n });\n\n```"} {"task_id": "format-code-task-000891", "source_id": "format-code-task-000891", "domain": "code", "task_path": "tasks/format-code-task-000891", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:15c2acfa71019a865489e8bf45212d724f5270342d2a0b51490c314f669debb1", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n5.1.0 - Each then() should return a value or throw\nUpdated deps this morning. In particular, eslint-plugin-promise from v4.3.1 to v5.1.0 (did you forget to make a tag for this release?) and getting the following error:\n\n```\nerror Each then() should return a value or throw promise/always-return\n```\n\nThe code in question looks like this:\n\n```js\nexport const fetchAbout = async function ({ commit, state, getters, rootState }) {\n return axios.get(state.baseUrl)\n .then((results) => {\n if (results.status === 200) { // OK\n commit('setAbout', results.data.payload)\n return results\n }\n else {\n throw new Error(results.data.error || results.data)\n }\n })\n .catch(function (error) {\n console.error('fetch about', error)\n throw error\n })\n}\n```\n\nI am not seeing the issue here. There is both a `return` and a `throw` involved.\n**Expected behavior:** No error here\n\n**Actual behavior:** issues an error\n\n### Versions\n\n- Node version: v12.18.4\n- ESLint version: v7.23.0\n- eslint-plugin-promise version: v5.1.0"} {"task_id": "format-code-task-000892", "source_id": "format-code-task-000892", "domain": "code", "task_path": "tasks/format-code-task-000892", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6e09696c238e5522a2e8701df578df70efb301736f82b230ac9d7ebea0d40a90", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nRule Change: Improve no-html rule's location reporting for HTML tags\n### What rule do you want to change?\n\nno-html\n\n### What change do you want to make?\n\nOther\n\n### How do you think the change should be implemented?\n\nOther\n\n### Example code\n\n```markdown\n
Some content
\n```\n\n### What does the rule currently do for this code?\n\nCurrently, the rule calculates the end of the reported location for an HTML tag using `start.column + match[0].length + 1`. This typically reports only the tag name itself and an extra character, missing any attributes or trailing spaces within the opening tag. For `
`, it reports `
`, it will report the full `
`.\n- For ``, it will report only `/svd/.svd`, choose svd2rust's RISC-V output when the chip's configured build target contains `riscv` and Xtensa LX output otherwise, and generate with the repository policy: debug impls behind `impl-register-debug`, defmt support behind `defmt`, interrupt link section `.rwtext.interrupt`, legacy identifier formatting with constant-case enum type/read names and PascalCase enum values, maximum cluster sizing, and no top-level peripherals struct except for `esp32s2-ulp`, `esp32s3-ulp`, and `esp32c6-lp`.\n\nThe command should write the rendered Rust crate into the chip package, include the repository HTML logo attribute in the crate docs, translate generated `doc_auto_cfg` attributes to `doc_cfg`, write `device.x`, and write the svd2rust `build.rs` for the same configuration. It should then split the generated Rust into the package `src/` directory with `form`, remove the temporary `lib.rs`, and run `cargo fmt` in that chip package, retrying transient formatter failures a few times. A successful generation run exits 0 after all requested chips finish; if SVD patching, SVD reading, rendering, writing generated files, splitting the source tree, or formatting fails for any requested chip, `generate` exits non-zero instead of reporting success. The generated files are the observable output, so normal successful runs do not need to print a data stream to stdout."} {"task_id": "format-code-task-000896", "source_id": "format-code-task-000896", "domain": "code", "task_path": "tasks/format-code-task-000896", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:f9af6eb698b24fd5834f9cab94de9c47e531239a23800ad5ce9f418ca250ac46", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## etcd panics on startup when recovering v3 backend from a snapshot\n\nI run a small etcd cluster in production. Recently one of the members fell behind far enough that the leader had to send it a full snapshot to catch up. After the snapshot was transferred, when that member restarted to apply it, etcd panicked during startup and the node never came back online.\n\nWhat I see in the logs:\n\n- Normal bootstrap progress, including a line about recovering the v3 backend from a snapshot.\n- Right after that, the process panics with what looks like an `assertion failed: tx closed` from the underlying bolt store, and exits.\n- The member never finishes bootstrap, so it can't rejoin the cluster.\n\nThe data directory does have the `snap.db` from the snapshot transfer present at the time of the crash — the panic seems to happen while etcd is trying to load that snapshot into its v3 backend during bootstrap, not later during normal operation.\n\nThe only \"workaround\" I've found is to wipe the member's data directory entirely and have it rejoin as if it were a fresh node. That's obviously not something we want to do every time a member happens to need a snapshot to catch up — it defeats the point of the snapshot recovery path.\n\nSo as far as I can tell, today any member that has to receive a full snapshot from the leader becomes unrecoverable on the next restart without manual intervention. Could someone take a look at the snapshot-recovery path in bootstrap?"} {"task_id": "format-code-task-000897", "source_id": "format-code-task-000897", "domain": "code", "task_path": "tasks/format-code-task-000897", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:7669521ea7fafed56f8456e0050651c9e0b35aee6045a34d69c42e1bd677770e", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n`etcdctl lease keep-alive` has no way to renew just once and exit\n\nRight now `etcdctl lease keep-alive ` keeps the stream open and\nkeeps refreshing the lease until I kill it. That's fine for long-running\nprocesses, but I'm calling etcdctl from a shell script where I just want\nto bump a lease's TTL back to its full value at a specific point in time\nand then let the script move on to the next step.\n\nWhat I'd like to do roughly:\n\n```\n# ... do some work ...\netcdctl lease keep-alive # I want this to renew once and return\n# ... do more work ...\n```\n\nWith the current behavior the command never returns, so I have to background\nit and kill it, which is awkward and racy. The underlying clientv3 API\nalready supports a single-shot keep-alive, so it would be nice to expose\nthat through etcdctl as well — i.e. have a way to ask `lease keep-alive`\nto reset the TTL one time and exit immediately.\n\nA natural shape would be something like a `--once` flag on `lease keep-alive`."} {"task_id": "format-code-task-000898", "source_id": "format-code-task-000898", "domain": "code", "task_path": "tasks/format-code-task-000898", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4d5d5324cdf5d917119afaba1b68ac08848d19cf66b297e3a8ce8ab3e5861241", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Add permutation and factorial helpers to the base utilities\n\nThe inference code is about to grow support for exploring label assignments over\nsmall groups of variables, and for that it needs a couple of reusable\ncombinatorics helpers. Please add them to the project's **base** utility library\nas free functions, exposed from a new header **`permutationsutil.h`**. Including\nthat header should be all a caller needs in order to use the functions — in\nparticular the `std::unordered_set>` type they operate on must\nbe usable as-is straight after the include.\n\nImplement exactly these three functions:\n\n### `void ComputeAllPermutations(std::vector v, std::unordered_set>* permutations, size_t beam_size)`\n\n- Enumerates permutations of `v` and adds them into `*permutations`. Because the\n destination is a set of vectors, only **distinct** arrangements are stored — if\n `v` contains repeated values, the arrangements that coincide collapse into one\n entry.\n- When `beam_size` is large enough to hold them all, the set ends up containing\n **every** distinct permutation of `v` — that is `n!` arrangements when all\n values are distinct, and correspondingly fewer when some values repeat — and\n this includes `v`'s original arrangement.\n- `beam_size` caps the work: generation halts as soon as the number of stored\n permutations exceeds `beam_size`, so the result never holds more than\n `beam_size + 1` entries. When `v` has at least `beam_size` distinct\n permutations, the set is filled up to the beam. Whatever entries were already\n present in `*permutations` on entry are preserved.\n\n### `void ComputeRandomPermutations(std::vector v, std::unordered_set>* permutations, size_t beam_size, size_t max_num_duplicates)`\n\n- Repeatedly draws random permutations of `v` and inserts the distinct ones into\n `*permutations`, stopping when either `beam_size` distinct permutations have\n been collected, or `max_num_duplicates` already-seen permutations have been\n drawn. The duplicate limit is a termination guard: it ensures the call returns\n even when `v` has fewer than `beam_size` distinct permutations.\n- The result holds at most `beam_size` entries, every one a permutation of `v`.\n When `beam_size` is at least the number of distinct permutations of `v`, the\n set ends up containing all of them.\n\n### `uint64 CalculateFactorial(int n)`\n\n- Returns `n!`. If the true value would not fit in a `uint64`, it returns\n `(uint64)-1` as an overflow sentinel instead of a wrapped-around result.\n (`uint64` is the project's unsigned 64-bit integer type.)\n"} {"task_id": "format-code-task-000899", "source_id": "format-code-task-000899", "domain": "code", "task_path": "tasks/format-code-task-000899", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:f4756a60cf86deed28559db6ce40cb2c4952cd778558952f17ddf702addeb37a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Logs disappear silently when using `AddTestScope`\n\nI'm writing a devstack test and using `devtest.AddTestScope(ctx, \"...\")` to tag log lines with a test scope. After adding the scope, log calls that go through the resulting context simply produce no output — the lines I'd expect to see in the test output are just missing. There's no panic, no error printed, nothing in stderr, the test just runs and the log calls behave as if they were no-ops.\n\nRough shape of what I'm doing:\n\n```go\nctx := devtest.AddTestScope(t.Ctx(), \"my-subtest\")\nlogger := /* the op-service logger configured with the context handler */\nlogger.InfoContext(ctx, \"starting step\", \"foo\", \"bar\") // <- never appears\n```\n\nIf I skip `AddTestScope` entirely the same log line shows up fine, so something about the scope-tagged context is making the log get dropped on the floor.\n\nThis is pretty painful to debug because there's zero signal that anything went wrong — you just stare at empty output and wonder whether the log call ran at all. Two things I'd like to see fixed:\n\n1. `AddTestScope` should work — adding a test scope to the context shouldn't cause subsequent log calls on that context to vanish.\n2. More generally, if something is wrong with the values that the context handler is trying to attach to a log record, that shouldn't silently drop the entire log line. A developer should at least get *some* visible indication that things aren't working, instead of having logs disappear without a trace."} {"task_id": "format-code-task-000900", "source_id": "format-code-task-000900", "domain": "code", "task_path": "tasks/format-code-task-000900", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:f5d913904e0a6b9636db85e6a4685665b8c5cd095d537a77db1672f4c28d52b7", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI'm running a backend group with `consensus_aware = true` and three upstreams, and even when all three are healthy and in agreement, almost all RPC traffic lands on the first backend in the config. If I mark that first one unhealthy, I still see requests hit it and fail before falling through, and a degraded backend near the top of the list also gets picked before the other healthy nodes. I'm not sure if my config is wrong, but consensus-aware routing looks like it's just following the config order instead of the current backend state.\n\nExpected outcomes:\n- For a backend group configured with `consensus_aware = true`, RPC forwarding should use the currently agreed consensus set rather than simply walking the original configured backend order.\n- When multiple healthy, non-degraded upstreams are in the current consensus set, repeated stable traffic should be observable across more than one of those upstreams instead of consistently concentrating on the first configured backend.\n- Upstreams that are currently unhealthy should not be selected for normal forwarding in a consensus-aware backend group; if other healthy consensus members are available, requests should go to those members without first failing against the unhealthy one.\n- Healthy but degraded upstreams may still be used as fallback candidates, but healthy non-degraded upstreams should be preferred ahead of degraded ones.\n\nImplementation notes:\n- The routing mechanism, data structures, and exact place where candidates are selected are up to the implementation.\n- Preserve existing consensus-aware semantics outside of backend candidate selection, including normal request handling and fallback behavior when no suitable backend is available."} -{"task_id": "format-code-task-000901", "source_id": "format-code-task-000901", "domain": "code", "task_path": "tasks/format-code-task-000901", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:9574be02c274993016ac43818f84975ceaa69f20a99d65852a698479538ba18e", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Add an OP-Stack `ProtocolVersion` type\n\nWe're introducing the concept of a Superchain \"Protocol Version\" — a Semver-compatible\nidentifier that lets nodes reason about which protocol features they support and signal\nrecommended/required upgrades to each other. As a first step we need a self-contained value\ntype for it in the shared eth types package (`op-service/eth`), exported as\n`eth.ProtocolVersion`, so the rest of the stack can encode, compare, log and transport it.\n\n## Encoding\n\nA `ProtocolVersion` is a single fixed 32-byte value. The first byte is a `version-type`\ndiscriminator (a `uint8`) and the remaining 31 bytes are the typed payload, so the format can be\nextended in the future.\n\nFor `version-type` `0`, the 32 bytes are laid out as:\n\n```\n\n```\n\nwhere `major`, `minor`, `patch` and `pre-release` are big-endian `uint32` values in that order,\nand `build` is 8 raw bytes.\n\nProvide a builder for version-type 0 values, `eth.ProtocolVersionV0`, with fields\n`Build [8]byte` and `Major`, `Minor`, `Patch`, `PreRelease` (all `uint32`), and an `Encode()`\nmethod that packs them into a `ProtocolVersion` with exactly the layout above. The 7 reserved\nbytes must be zero.\n\n## Human-readable form\n\n`String()` renders a version-type 0 value as a Semver-style string:\n\n- The base is `vMAJOR.MINOR.PATCH` using the decimal values (no zero-padding), e.g. `v1.2.3`.\n- If `pre-release` is non-zero, append `-PRERELEASE`, e.g. `v1.2.3-4`. A zero pre-release is omitted.\n- If the build field is not all zero, append a `+` build suffix:\n - If, after trimming trailing zero bytes, every remaining build byte is in the Semver build\n character set (`0-9`, `a-z`, `A-Z`, `-`, `.`), present it directly as that string,\n e.g. build bytes `\"OPstack\\x00\"` render as `+OPstack`.\n - Otherwise present all 8 build bytes as a `0x`-prefixed lowercase hex string,\n e.g. `+0xff00010203040506`.\n - An all-zero build adds no suffix.\n\n## Comparison\n\nAdd a `Compare(other ProtocolVersion) ProtocolVersionComparison` method and an exported\n`ProtocolVersionComparison` result type with named values:\n`AheadMajor`, `OutdatedMajor`, `AheadMinor`, `OutdatedMinor`, `AheadPatch`, `OutdatedPatch`,\n`AheadPrerelease`, `OutdatedPrerelease`, `Matching`, `DiffVersionType`, `DiffBuild`,\n`EmptyVersion`, `InvalidVersion`.\n\nComparison semantics (receiver compared against `other`):\n\n- If either operand is the zero value (all 32 bytes zero) → `EmptyVersion`.\n- Otherwise if the two `version-type` bytes differ → `DiffVersionType`.\n- Otherwise if the version type is non-zero (unrecognized) → `InvalidVersion`.\n- Otherwise (both version-type 0): if the two `build` fields differ → `DiffBuild`\n (different builds are not comparable, regardless of the version numbers).\n- Otherwise compare `major`, then `minor`, then `patch`, then `pre-release`, in that precedence\n order. The first field that differs decides the result: if the receiver's field is greater it is\n \"ahead\" (`AheadMajor`/`AheadMinor`/`AheadPatch`/`AheadPrerelease`), if smaller it is \"outdated\"\n (`OutdatedMajor`/…). If all four are equal → `Matching`.\n\n## Serialization\n\nA `ProtocolVersion` must encode in JSON (and via text marshaling) as a single `0x`-prefixed\n32-byte hex string, and decode back from that same representation. Decoding input of the wrong\nlength must return an error.\n"} {"task_id": "format-code-task-000902", "source_id": "format-code-task-000902", "domain": "code", "task_path": "tasks/format-code-task-000902", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:f395ec30956da3ea52e5512536e4c1a28a969dbf3d7af5f3136f49c22b8afae5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n\"ethclient.Client\" doesn't support setting http header.\nWhile i use infura jsonapi with \"ethclient.Client\", for security considerations, i gonna set \"User-Agent\", \"Origin\" by HTTP Headers.\nBut i can't find a way to do so.\nDo i miss something ?\n\n#### System information\n\nGeth version: `v1.9.5`\nOS & Version: ubuntu 18.04.01 \n\n#### Expected behaviour\n\n\n#### Actual behaviour\n\n\n#### Steps to reproduce the behaviour\n\n\n#### Backtrace\n\n````\n[backtrace]\n````\n\nIt would be nice if the underlying rpc client exposed something like `SetHeader(key, value)` for this."} {"task_id": "format-code-task-000903", "source_id": "format-code-task-000903", "domain": "code", "task_path": "tasks/format-code-task-000903", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:00ccbfa9cdb5ef77c6c7b021a3e5a956d8de38fb4e09a85cafd3297095097f45", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### `AncientRange` returns only one item when `maxBytes` is 0\n\nI'm building a small tool that pulls items in bulk out of the freezer through the `ethdb.AncientReaderOp.AncientRange(kind, start, count, maxBytes)` API. In some code paths I genuinely don't care about a byte budget — I just want exactly `count` items if they're present in the freezer. The natural way to express \"no byte limit\" felt like passing `maxBytes = 0`, so I tried:\n\n```go\nitems, err := db.AncientRange(\"bodies\", start, 100, 0)\nif err != nil {\n log.Fatal(err)\n}\nfmt.Println(len(items)) // expected: 100 (or however many are available)\n```\n\nWhat I actually get back is a slice of length 1. Asking for 50, 100 or 1000 items all behave the same — only the first one comes back. So in practice I have to call `AncientRange` in a loop one item at a time, which kind of defeats the point of having a range API.\n\nThe obvious workaround is to pass a huge number like `math.MaxUint64` for `maxBytes`, but that's awkward — it reads like \"I'm fine allocating 16 EiB up front\" rather than \"I genuinely don't want a byte cap\", and it also relies on the implementation not actually trying to honor that as a buffer size.\n\nThe current doc on `AncientRange` says it will return \"at most `count` items, at least 1 item (even if exceeding maxBytes), but will otherwise return as many items as fit into maxBytes.\" That's a reasonable contract when the caller does specify a byte budget, but there's no documented way to say \"no budget, just give me `count` items\". It would be really useful if `maxBytes = 0` meant exactly that — return up to `count` items, ignoring any byte-size cap — while a nonzero `maxBytes` keeps behaving the way it does today.\n\nThis should apply both at the top-level `Freezer.AncientRange` and at the underlying `freezerTable.RetrieveItems`, since both take the same `maxBytes` parameter."} {"task_id": "format-code-task-000904", "source_id": "format-code-task-000904", "domain": "code", "task_path": "tasks/format-code-task-000904", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:80e8d7a7d26548f5ef476c5fa3047cb89ab436e2ac351c09d580d39a5a32e258", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nWhen I call `GET /stamps`, I’m getting back old stamp entries whose batches don’t exist anymore, so the list is cluttered with unusable stuff. I’d rather have the normal response show only stamps that are still backed by an existing batch, and maybe have some explicit way to include the stale ones when I’m debugging.\n\n# Expected outcomes\n\n- Default stamp listing:\n - A `GET /stamps` response should include only stamps whose underlying batch still exists.\n - Stale stamp entries whose batch no longer exists should be omitted from the normal `stamps` array response.\n\n- Explicit inclusion of stale entries:\n - `GET /stamps?all=true` should return all locally tracked stamps, including stale entries whose batch no longer exists.\n - Stale entries returned through the explicit “all” mode should still be represented as unavailable/non-existing in the existing response fields, such as `exists: false` and `usable: false`.\n\n- Query parameter handling:\n - Only an `all` query value that is equal to `true` using case-insensitive comparison should enable the all-stamps response.\n - Missing `all`, `all=false`, or any other non-true value should use the default filtered behavior.\n\n- API documentation:\n - The OpenAPI documentation for `GET /stamps` should document the optional `all` query parameter.\n - The route documentation should describe the endpoint as listing stamps without implying that the default response returns every tracked or every available batch.\n\n# Implementation notes\n\n- The exact data structures, helper functions, and validation location are implementation details.\n- The behavior should be observable through the existing HTTP API and its documented response shape.\n- Existing response fields for stamp availability should remain compatible with callers."} @@ -814,7 +779,6 @@ {"task_id": "format-code-task-000934", "source_id": "format-code-task-000934", "domain": "code", "task_path": "tasks/format-code-task-000934", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:453b7b2bc6b0514e8701aa4de321327b2c548e552bad066eb8c754d6b2a87e28", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nschema.response without a status code throws a cryptic error message\n### Prerequisites\n\n- [X] I have written a descriptive issue title\n- [X] I have searched existing issues to ensure the bug has not already been reported\n\n\n### Fastify version\n\n3.29\n\n### Plugin version\n\n_No response_\n\n### Node.js version\n\n16.x\n\n### Operating system\n\nmacOS\n\n### Operating system version (i.e. 20.04, 11.3, 10)\n\n12.3.1\n\n### Description\n\nThe current response schema definition is:\n\n```\nschema: {\n response: {\n $STATUS_CODE: your_schema_here\n }\n}\n```\n\nI accidentally typed the following:\n\n```\nschema: {\n response: your_schema_here\n}\n```\n\nThis results in an error that is a little cryptic, in my opinion:\n\n```\nFastifyError [Error]: Failed building the serialization schema for GET: /meters, due to error schema is invalid: data.properties should be object\n```\n\nIt seems like this mistake could be captured by fastify, and a better error message could be returned to the user? Obviously the best solution is to RTFM correctly, so I understand if this is deemed not worthwhile :)\n\n### Steps to Reproduce\n\nPass a schema directly to response, without specifying a status code:\n\n```\napp.route({\n url: '/',\n method: 'GET',\n schema: {\n response: {\n type: 'array'\n }\n },\n handler: (req, reply) => {\n reply.send([])\n }\n})\n```\n\n### Expected Behavior\n\nAn error message stating \"response schemas should be nested under a response code, e.g { 200: { type: 'object' } }\" or similar."} {"task_id": "format-code-task-000935", "source_id": "format-code-task-000935", "domain": "code", "task_path": "tasks/format-code-task-000935", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c0709bdede29fc4fd557ea74dfd933f5ea489dd2738a79f4ae813e16fa263839", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nCertain errors result in request being null\nIf an error occurs before the Validation part of the lifecycle, `request` is `null` in:\n\n+ The `onSend` hook\n\n ```js\nfastify.addHook('onSend', function(request, reply, payload, next) {\n console.log(request) // null\n})\n```\n\n+ Any custom error handler\n\n```js\nfastify.setErrorHandler(function(err, reply) {\n console.log(reply.request) // null\n})\n```\n\nThis is very much unexpected in the `onSend` hook and this also makes it more difficult to access the `req` object in the error handler.\n\nSee PR #551 for a potential fix."} {"task_id": "format-code-task-000936", "source_id": "format-code-task-000936", "domain": "code", "task_path": "tasks/format-code-task-000936", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3174e365b68357282b238a361057c960fa0f8eb9611060c60fbfdab9dea4251d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nGenerate-plugin template uses incorrect Fastify version\n### Prerequisites\n\n- [x] I have written a descriptive issue title\n- [x] I have searched existing issues to ensure the bug has not already been reported\n\n\n### Fastify version\n\n5.0.0\n\n### Plugin version\n\n5.0.0\n\n### Node.js version\n\n22.12.0\n\n### Operating system\n\nLinux\n\n### Operating system version (i.e. 20.04, 11.3, 10)\n\nUbuntu 24.04\n\n### Description\n\nWhen launch generate-plugin create a nwe plugin it force the fastify version to ^4.0.0 while the fastfy version used is ^5.0.0\n\n### Link to code that reproduces the bug\n\nhttps://github.com/gafreax/fastify-cli-incorrect-plugin-fastify-version\n\n### Expected Behavior\n\nWhen using the `fastify generate-plugin` command, the generated plugin\n template specifies a dependency on Fastify version `^4.0.0`. However, my\n project uses Fastify `^5.0.0` (or higher). This version mismatch leads to\n errors during plugin installation and prevents the generated plugin from\n working correctly with my existing application.\n\n To reproduce:\n\n 1. Run `fastify generate-plugin `\n 2. Observe the `package.json` file of the newly generated plugin. It will\n contain `fastify@^4.0.0` as a dependency.\n\nThe error is:\n\n```\n> fastify start -w -l info -P app.js\n\nFastifyError [Error]: fastify-plugin: index-auto-0 - expected '^4.x' fastify version, '5.2.1' is installed\n at Object.checkVersion (/home/gafz/Workspace/ex/node_modules/fastify/lib/pluginUtils.js:125:11)\n at Object.registerPlugin (/home/gafz/Workspace/ex/node_modules/fastify/lib/pluginUtils.js:148:16)\n at Boot.override (/home/gafz/Workspace/ex/node_modules/fastify/lib/pluginOverride.js:28:57)\n at Boot._loadPlugin (/home/gafz/Workspace/ex/node_modules/avvio/boot.js:425:25)\n at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {\n code: 'FST_ERR_PLUGIN_VERSION_MISMATCH',\n statusCode: 500\n}\n```"} -{"task_id": "format-code-task-000937", "source_id": "format-code-task-000937", "domain": "code", "task_path": "tasks/format-code-task-000937", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:039ce3f73170937717f5816948eb8ef151b85a1bd9f8a4a11b0cf61973b0a8a6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nBug: Quality value syntax not supported\nIt seems like fastify-compress does not support [Quality Value](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding#Syntax) syntax in the `Accepts-Encoding` header. This values for example causes a `406 Unsupported Encoding` HTTP error to be returned. \n\nLooking int the source of [`index.js:128`](https://github.com/fastify/fastify-compress/blob/master/index.js#L126) in `onSend` the `encoding` variable is indeed `null`. This error goes away once removing the `q` directives from the header value.\n\nExample `Accepts-Encoding` header value that we fail to parse:\n`gzip;q=1.0,deflate;q=0.6,identity;q=0.3`\n\nQuickly looking at the source, we will likely need to update`getEncodingHeader` to support this."} {"task_id": "format-code-task-000938", "source_id": "format-code-task-000938", "domain": "code", "task_path": "tasks/format-code-task-000938", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:944954ba7cda6877ed944767a47a94965d870dfc627b41cade69b24df0e4b6cd", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### New Issue Checklist\n\n- [x] Updated fastlane to the latest version\n- [x] I read the [Contribution Guidelines](https://github.com/fastlane/fastlane/blob/master/CONTRIBUTING.md)\n\n### Issue Description\n\nThe Apple Vision Pro launches this Friday and I'm trying to ship our visionOS app to TestFlight, but `fastlane pilot upload` rejects `xros` as a platform.\n\nWhen I run something like:\n\n```\nbundle exec fastlane pilot upload \\\n --api-key-path \\\n --team_id \\\n --app_platform xros \\\n --ipa ./MyVisionApp.ipa\n```\n\npilot bails out complaining that the platform can only be `ios`, `appletvos`, or `osx`. If I leave `--app_platform` off, it eventually prompts me for the platform and only offers those same three values, so there's no way to tell pilot the build is for visionOS.\n\nThe ipa itself is a perfectly valid visionOS build — App Store Connect accepts it when uploaded via Xcode / Transporter directly — pilot is the only thing in my pipeline that refuses it.\n\nCould `xros` be added as a recognized platform for pilot alongside `ios`, `appletvos`, and `osx`? Right now Vision Pro releases through fastlane are fully blocked on this.\n\n### Environment\n\n- fastlane pilot\n- target platform: visionOS (xros)"} {"task_id": "format-code-task-000939", "source_id": "format-code-task-000939", "domain": "code", "task_path": "tasks/format-code-task-000939", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:60e33860bd3117eb0ac0209945dec775da0987ca7fa29117355e5da72d2aa971", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI'm trying to use `Predictor.predict` with a sequence labeling model and it keeps failing with a TypeError about unexpected keyword arguments. The model follows the framework's sequence-labeling forward interface, but Predictor does not appear to be respecting the task I set when it forwards prepared inputs to the model. Can it call the network in a way that matches the task I'm doing? And if I pass some task name it doesn't know about, I'd rather get a clear error up front than a confusing crash deep inside the model.\n\n# Expected outcomes\n\n- Sequence labeling prediction:\n - The forwarding step used by `Predictor.predict` should work for `task=\"seq_label\"` with a sequence-labeling model that only accepts the task-appropriate model inputs, even when the prepared batch/input contains additional fields.\n - Sequence-labeling prediction should still return the normal predicted-label output for that task rather than exposing raw intermediate model output.\n\n- Text classification prediction:\n - The forwarding step used by `Predictor.predict` should continue to support `task=\"text_classify\"` with the task-appropriate model input expected by text classification models.\n - Text classification prediction should not require sequence-labeling-specific post-processing behavior from the model.\n\n- Unknown task handling:\n - If `Predictor` is used with an unsupported task name, prediction should fail early with a clear `NotImplementedError`.\n - The error message should make it clear that the task is unknown or unsupported.\n\n# Implementation notes\n\n- The exact dispatch structure and where validation is performed are up to the implementer.\n- Keep the behavior aligned with the existing `Predictor` data preparation and batching flow.\n- Avoid requiring models for one supported task to accept inputs that belong only to another task."} {"task_id": "format-code-task-000940", "source_id": "format-code-task-000940", "domain": "code", "task_path": "tasks/format-code-task-000940", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1fd9f6cfa0977ba50367a27e331a14cbe21683f78cd0d7cd4906ad078b2a4aef", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want Skunk to add derived metric methods to RubyCritic analysed file and collection objects so library and report code can ask those objects directly for SkunkScore data.\n\nFor a RubyCritic::AnalysedModule, provide public zero-argument methods skunk_score, penalty_factor, churn_times_cost, and to_hash. skunk_score should return the file cost rounded to 2 decimals when coverage is exactly 100; with cost 100 and coverage 100 it returns 100, with cost 100 and coverage 0 it returns 10000, and with cost 100 and coverage 75 it returns 2500. penalty_factor should be 100 minus integer coverage, so coverage 75 gives 25. churn_times_cost should multiply cost by churn and round to 2 decimals, treating zero or negative churn as 1; for cost 2.34 and churn 3 it returns 7.02, and for cost 2.34 and churn 0 it returns 2.34. to_hash should return a hash with file as the pathname string plus skunk_score, churn_times_cost, churn, cost rounded to 2 decimals, and coverage rounded to 2 decimals.\n\nFor a RubyCritic::AnalysedModulesCollection, provide public zero-argument methods analysed_modules_count, skunk_score_total, skunk_score_average, total_churn_times_cost, worst_module, sorted_modules, non_test_modules, files_as_hash, and to_hash. The collection metrics should ignore test files: paths under directories beginning or ending with test or spec, and filenames ending in _test.rb or _spec.rb, are excluded from counts, totals, rankings, and exported file lists. Given production modules lib/a.rb with skunk_score 10 and churn_times_cost 5, lib/b.rb with skunk_score 20 and churn_times_cost 7, and test/a_test.rb with skunk_score 999, analysed_modules_count returns 2, skunk_score_total returns 30, skunk_score_average returns 15.0, total_churn_times_cost returns 12, sorted_modules returns lib/b.rb before lib/a.rb, and worst_module returns lib/b.rb. For an empty collection, skunk_score_average returns 0.0 and worst_module returns nil. Collection to_hash should include analysed_modules_count, skunk_score_total, skunk_score_average, total_churn_times_cost, worst_pathname, worst_score, and files, where files is the sorted list of per-file hashes."} @@ -1065,7 +1029,6 @@ {"task_id": "format-code-task-001192", "source_id": "format-code-task-001192", "domain": "code", "task_path": "tasks/format-code-task-001192", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ab7fc2a0bca857603405207ca16f70acd58f3bdd72dd8aeb48ff9db096617a36", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### Missing type definition for `Observable.combineAll` in rxjs v5 libdef\n\nThe flow-typed definitions for `rxjs` v5 (`definitions/npm/rxjs_v5.0.x/...`) don't seem to include the `combineAll` operator. It's a standard rxjs 5 operator (see http://reactivex.io/rxjs/class/es6/Observable.js~Observable.html#instance-method-combineAll) and works fine at runtime, but Flow complains it's not on `Observable`.\n\nRepro — something like:\n\n```js\nimport { Observable } from 'rxjs';\n\nconst higherOrder: Observable> = Observable.of(\n Observable.of(1, 2, 3),\n Observable.of(4, 5, 6),\n);\n\nconst combined = higherOrder.combineAll();\ncombined.subscribe(arr => console.log(arr));\n```\n\nFlow errors out on `.combineAll()` because the method isn't declared on `rxjs$Observable`. Other \"join\" operators on higher-order observables like `concatAll` and `mergeAll` are already in the libdef, so it'd be nice to have `combineAll` covered as well (in both the `flow_v0.25.0-v0.33.x` and `flow_v0.34.x-` variants).\n\nIt should also support the optional projection function form (`combineAll(project)`) that rxjs allows."} {"task_id": "format-code-task-001193", "source_id": "format-code-task-001193", "domain": "code", "task_path": "tasks/format-code-task-001193", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:cf9a6a69a2f556c2e9d57e55daf55fa201990423e4a9e5eac46e00426fc647a5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `history.push` / `history.replace` 类型不接受 location 对象\n\nhistory v4 的 API 允许我用两种方式调用 `push` 和 `replace`:传一个 path 字符串(加可选 state),或者直接传一个 location 对象,例如:\n\n```js\nimport createBrowserHistory from 'history/createBrowserHistory';\n\nconst history = createBrowserHistory();\n\n// 形式 1:path + state(这种 flow 不报错)\nhistory.push('/foo', { from: 'bar' });\n\n// 形式 2:location 对象(这种 flow 报错)\nhistory.push({\n pathname: '/foo',\n search: '?x=1',\n hash: '#section',\n});\n```\n\n第二种调用是 history 库官方文档里推荐的用法(在需要同时指定 pathname/search/hash 时很常见,react-router 内部也是这么用的),运行时完全正常,但当前 flow-typed 里 `BrowserHistory` / `MemoryHistory` / `HashHistory` 的 `push` 和 `replace` 签名只覆盖了 `(path: string, state?)`,所以传 location 对象时 flow 直接报类型错误。\n\n`replace` 也有同样的问题。\n\n另外顺带:`BrowserLocation` 和 `MemoryLocation` 里 `state` 的类型是 `string`,但实际上 state 是用户自己塞进去的任意对象(react-router 文档里的例子也是对象),写成 string 太窄了,传 `{ from: '/login' }` 这种就过不了类型检查。\n\n希望这些类型能同时支持 path-字符串和 location-对象两种调用形式。"} {"task_id": "format-code-task-001194", "source_id": "format-code-task-001194", "domain": "code", "task_path": "tasks/format-code-task-001194", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:5d64cd17ad5efac8d45ea5f8342f3661462b87ba07b70c6071e18642d01757d1", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nFound in https://github.com/flutter/flutter/pull/129381\n\nThe flutter gold check only runs on PRs that are running golden file tests - or so we thought. 🕵️ \n\nThe way the check determines this is by checking the already running checks on a PR. If the framework test shards or web test shards are running, flutter gold adds itself to the queue:\n\nhttps://github.com/flutter/cocoon/blob/26515729f2afdf0a77b03c9bdcd06824cc4b0436/app_dart/lib/src/request_handlers/push_gold_status_to_github.dart#L122\n\nIn https://github.com/flutter/flutter/pull/129381, we found that the API docs are not accounted for by this. The API docs tests run on a different shard (I think misc?) and so flutter gold was not triggered.\n\nThis would have broken the tree if @HansMuller had not known a golden file change was expected. The PR could have landed, the new image would have shown up in post submit as untriaged, and the tree would go red."} -{"task_id": "format-code-task-001195", "source_id": "format-code-task-001195", "domain": "code", "task_path": "tasks/format-code-task-001195", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:903c2b51269769d15c620d5f27511370903d4ef7ec62c987d64730291dc0d30a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `flux plugin install` to support pinned SHA-256 digest references in addition to plain plugin names and versions. The invocation should be `flux plugin install @sha256:`, for example `flux plugin install operator@sha256:06e0a38db4fa6bc9f705a577c7e58dc020bfe2618e45488599e5ef7bb62e3a8a`.\n\nWhen the part after `@` starts with `sha256:`, the command should treat it as a digest rather than as a version string. It should resolve that digest against the plugin's catalog manifest by scanning versions in order and selecting the first platform entry whose checksum exactly matches the digest and whose OS and architecture match the current machine. It should then install the resolved version/platform and exit 0 on success, reporting the installed plugin name and version the same way as other successful plugin installs.\n\nIf the manifest has no versions, the command should fail with a non-zero exit and an error like `plugin \"operator\" has no versions`. If the digest is absent for the current OS/architecture, including when the same digest exists only for another platform, the command should fail with a non-zero exit and an error like `digest \"sha256:...\" not found for plugin \"operator\" on linux/amd64`. `flux plugin install --help` should advertise the digest form in the usage string and include an example for installing pinned to a digest."} {"task_id": "format-code-task-001196", "source_id": "format-code-task-001196", "domain": "code", "task_path": "tasks/format-code-task-001196", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:bd989230bd6424d203d75a9b57ee46f8de8147fd8a7d11da0de10f8853af38a5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Strict isinstance check rejects values that the transformer could actually convert\n\nI have a task that takes a `FlyteFile` input:\n\n```python\nfrom flytekit import task, workflow\nfrom flytekit.types.file import FlyteFile\n\n@task\ndef process(f: FlyteFile) -> int:\n with open(f, \"r\") as fp:\n return len(fp.read())\n\n@workflow\ndef wf(path: str) -> int:\n # I'd also like to be able to just hand a path string in directly\n # when driving things programmatically / locally\n return process(f=path)\n```\n\nWhen I try to drive this with a plain string path as the value for the `FlyteFile` input, flytekit blows up with a `FlyteTypeException` complaining that `str` is not an instance of `FlyteFile`. The conversion never gets a chance to run, even though the registered transformer for `FlyteFile` is perfectly capable of turning a path string into the right literal.\n\nI'd expect the type engine to attempt the conversion through the registered transformer and only raise `FlyteTypeException` if the transformer itself can't handle the value. Right now anything that isn't already an `isinstance` of the declared type is rejected up front, which makes it impossible to leverage transformers that do legitimate type coercion (path-like → file, etc.).\n\nCould the type engine be a bit less eager about the up-front isinstance check, and let the transformer have a say in whether the value is acceptable?"} {"task_id": "format-code-task-001197", "source_id": "format-code-task-001197", "domain": "code", "task_path": "tasks/format-code-task-001197", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:eb778154370aa13ee73db5b98842120f63647ed4bcb6bcc7bb84fcf68f81f19b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the NES library to support iNES mapper 7 / AOROM cartridges when I create an emulator with `nes.NewConsole(path string) (*nes.Console, error)`. If the `.nes` header declares mapper ID 7 and the ROM data is otherwise valid, `NewConsole` should return a usable console instead of an unsupported-mapper error.\n\nFor mapper 7 cartridges, CPU reads from `$8000-$FFFF` should come from one 32 KB PRG-ROM bank, initially bank 0. CPU writes at `$8000-$FFFF` should select the active 32 KB PRG bank from the low three bits of the written value, so a later read from the same CPU address range reflects the selected bank. The same write should set single-screen nametable mirroring from bit 4: clear selects the first single-screen page and set selects the second single-screen page.\n\nThe mapper should make cartridge CHR memory available to the PPU at `$0000-$1FFF`, with PPU writes in that range updating CHR RAM when the cartridge uses writable CHR storage. CPU reads and writes at `$6000-$7FFF` should access cartridge SRAM at the matching offset. Console save/load state should preserve the mapper 7 selected PRG bank, so after loading a saved state, subsequent CPU reads continue from the same mapped bank."} {"task_id": "format-code-task-001198", "source_id": "format-code-task-001198", "domain": "code", "task_path": "tasks/format-code-task-001198", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:66991318c652275f2d21805e10ef3f4f2e38525aa675b32bbc3fab7e1cb4974e", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nCustom profiles routinely build on several other profiles, but today `include_profiles` behaves like a check-list copy rather than true profile composition: inherited configuration defaults and status policies disappear, duplicate checks can run more than once when they came from different sections, and a bad include graph ends in an opaque recursion failure. Please make compiled profiles compose all of this policy predictably.\n\nProcess included profiles depth-first in the order listed, followed by the including profile's own declarations. Configuration defaults must be inherited transitively and merged at the check-ID and variable-name levels, so an override of one variable does not discard sibling variables. For conflicts, a later included profile wins over an earlier one, and the including profile wins over every include. When a user supplies a check-specific configuration namespace at runtime, merge it over the compiled profile defaults by variable name as well; omitted variables keep their defaults, while explicitly supplied falsy values such as `0` remain real overrides. Other top-level runtime configuration and the existing explicit/excluded-check selection behavior must continue to work.\n\nStatus overrides must compose transitively too. Merge rules by check ID and message code: preserve rules for unmentioned codes, replace an earlier rule when a later include defines the same code, and give the including profile final precedence. An included profile may contribute defaults or an override for a check that is supplied by another profile; policy metadata is not conditional on that included profile placing the check in one of its own sections. The resulting policies must be the ones observed when the check actually runs.\n\nA compiled profile must contain each check ID at most once, even if separate includes or the local profile list it under different section names. Keep the first occurrence and its section position according to the depth-first traversal above; later duplicates must not execute again. Reject direct or indirect include cycles with `ValueError` before recursion overflows, and include the profile-name chain in the error so the cycle can be diagnosed.\n\nFinally, treat compilation as a snapshot. Nested configuration-default and override structures in a returned profile must not alias the source module's `PROFILE` data or another compilation result: changes on either side after compilation must not leak across that boundary. Preserve the existing public usage in which a custom module is passed to `profile_factory`, bundled profiles are referenced by short name, and profile/runtime exclusion and explicit-selection filters remain supported."} @@ -1092,9 +1055,7 @@ {"task_id": "format-code-task-001222", "source_id": "format-code-task-001222", "domain": "code", "task_path": "tasks/format-code-task-001222", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d73e3dca0d19ec8e6b2aaf495d694b87a21dffd762bed85d7b1594a0f9a03f44", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Non-HTTP socket traffic blows up when HTTPretty is enabled\n\nI'm using HTTPretty to mock HTTP responses in my tests, but the code under\ntest also opens a regular TCP connection to a non-HTTP service (in my case\nRedis, but it would happen with anything that's not on ports 80/443). As\nsoon as that code path calls `send()` or `recv()` on its socket, the test\nexplodes with:\n\n```\nRuntimeError:\nHTTPretty intercepted and unexpected socket method call.\nPlease open an issue at 'https://github.com/gabrielfalcao/HTTPretty/issues'\nAnd paste the following traceback:\n...\n```\n\nRoughly what I'm doing:\n\n```python\n@httprettified\ndef test_something():\n httpretty.register_uri(httpretty.GET, \"http://example.com/api\", body=\"ok\")\n\n # this part of the code talks HTTP — fine, gets mocked\n do_http_call()\n\n # this part talks to e.g. redis on a non-HTTP port — boom\n do_non_http_call()\n```\n\nThe HTTP mocking itself works as expected. The problem is that *every*\nsocket created while HTTPretty is enabled has its `send` / `sendto` /\n`recv` / `recvfrom` / `recv_into` / `recvfrom_into` replaced with a stub\nthat always raises, regardless of whether the socket is actually talking\nto something HTTPretty cares about.\n\nI'd expect HTTPretty to only intercept sockets that are actually being\nused for HTTP traffic, and to leave other sockets alone so they behave\nlike normal sockets. Otherwise it's pretty much impossible to use\nHTTPretty in any test where the code under test also touches a non-HTTP\nservice."} {"task_id": "format-code-task-001223", "source_id": "format-code-task-001223", "domain": "code", "task_path": "tasks/format-code-task-001223", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:1ee39008c1bffea9e5fe3e661d3a9eb934ec3ea9382cb8866037151e26ba2c74", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `solana.Transaction` to provide a stateful signing and signature verification API. On a `*Transaction`, `PartialSign(func(solana.PublicKey) *solana.PrivateKey) ([]solana.Signature, error)` should serialize the transaction message, use the message's required signer public keys in order, allocate `tx.Signatures` to that signer count when it is empty, and write signatures only for keys whose callback returns a non-nil private key; nil keys should leave existing or zero signature slots untouched so repeated partial signing calls can fill signer slots in any order.\n\nFor a transaction with three required signers A, B, and C and an empty `Signatures` slice, calling `PartialSign` with only B's key should return a 3-element slice, set `Signatures[1]` to B's signature, leave `Signatures[0]` and `Signatures[2]` as zero signatures, and a later call with A and C should fill slots 0 and 2 without moving B. If `tx.Signatures` already has a nonzero length different from the required signer count, `PartialSign` should return an error like `invalid signatures length, expected 3, actual 1` and should not resize it.\n\n`Sign(func(solana.PublicKey) *solana.PrivateKey) ([]solana.Signature, error)` should require every signer key before signing. For a transaction with signers A and B, if the callback returns A's key but nil for B, `Sign` should return a non-nil error mentioning B and should not silently produce a partially signed transaction; when the callback returns both keys, it should fill `tx.Signatures` in signer order and return that same slice.\n\n`VerifySignatures() error` should serialize `tx.Message`, require `len(tx.Signatures) == len(tx.Message.Signers())`, and verify each signature against the public key at the same signer index. After `Sign` succeeds, `VerifySignatures` should return nil. If a transaction has two required signers but only one stored signature, `VerifySignatures` should return an error like `got 2 signers, but 1 signatures`; if a signature slot contains a signature made by the wrong key or over different message bytes, it should return an error identifying the invalid signer."} {"task_id": "format-code-task-001224", "source_id": "format-code-task-001224", "domain": "code", "task_path": "tasks/format-code-task-001224", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b2ea6ed1be207ce38a3caa1df07b355422934062b8f1d5e2c88dec8c267e7de7", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nProblem Statement: I noticed `jsdoc/valid-types` catches bad JSDoc types, but it seems to let completely empty inline tags like `{@link}` or `{@tutorial}` slip through, even inside a `@param` description. Could it report those as missing content instead of treating them as valid?\n\nExpected outcomes:\n- The `jsdoc/valid-types` rule should report `Inline tag \"\" missing content` when a link-style or tutorial inline tag has no content.\n- This should hold both in the main JSDoc description and inside other tag descriptions such as `@param`.\n- Inline tags with content should remain valid, and unrelated inline tags should not be treated as missing content.\n\nImplementation notes:\n- Only the externally visible lint result matters; traversal strategy, helper structure, and internal data organization are not part of the required contract."} -{"task_id": "format-code-task-001225", "source_id": "format-code-task-001225", "domain": "code", "task_path": "tasks/format-code-task-001225", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:101f2e6df72026b064e196c30dacaf1a1f4ad05fd8efc923b5686a6ecb417abe", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n\"require-returns\" requires useless return statements for return type \"undefined\"\nSubject says it. If the return type is undefined I don't need a return statement in the code.\n\nThis plugin should concern itself with JSDoc — not with the code style! The return type when there is no `return` statement is `undefined`, so describing such a function as having `@returns {undefined}` is 100% correct. I should not get\n\n Present JSDoc @returns declaration but not available return expression in function jsdoc/require-returns"} {"task_id": "format-code-task-001226", "source_id": "format-code-task-001226", "domain": "code", "task_path": "tasks/format-code-task-001226", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:90ae6c6e47d15e900c43971032f778d3970ab2427fe08328496d1afb782c2093", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Warn users when picking a non-perceptually-uniform 2D colormap\n\nWe ship a bunch of 2D colormaps in the `colormaps` directory that get used by `Volume2D` / `Vertex2D` via the `cmap` argument. Several of the older ones aren't perceptually uniform (the steps in the colormap don't correspond to equal perceptual changes), which can be misleading when interpreting brain maps — small differences in the data look bigger or smaller than they actually are depending on where they fall in the colormap.\n\nThe good news is that for most of these older colormaps we now also ship a perceptually-uniform counterpart in the same directory (you can see this by listing the `.png` files under the colormaps dir — there are clear pairs of \"old\" vs \"PU_*\" / \"*_alpha\" versions covering essentially the same color scheme).\n\nThe problem is that nothing in pycortex tells the user about this. If someone writes e.g.\n\n```python\nimport cortex\nv = cortex.Volume2D(data1, data2, subject, xfmname, cmap=\"RdBu_covar\", ...)\ncortex.quickshow(v)\n```\n\nit just renders silently with the non-uniform colormap, and unless the user happens to know that a better drop-in replacement exists in the colormaps folder, they'll keep using the worse one. New users especially have no way of knowing which of the bundled 2D colormaps are the \"good\" ones.\n\nIt would be nice if pycortex nudged the user in this case — when a 2D view is being colormapped with one of the known non-perceptually-uniform colormaps that has a direct perceptually-uniform replacement available, surface a message at render/colormapping time pointing them at the better option. For 2D colormaps that don't have a clear PU equivalent we shouldn't say anything, and the call should otherwise behave exactly as before (no error, no change in output)."} -{"task_id": "format-code-task-001227", "source_id": "format-code-task-001227", "domain": "code", "task_path": "tasks/format-code-task-001227", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:4ed35ad9c41db2112b782b277438535d59dced22d5491f41ca222d1da1e43e37", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want SanitizeEmail to provide stateful activation controls for deciding whether an outgoing Mail message is sanitized. The public API should include `SanitizeEmail.force_sanitize` and `SanitizeEmail.force_sanitize=(value)` where `value` may be `true`, `false`, or `nil`; a non-`nil` value takes precedence over configured activation for later deliveries. `SanitizeEmail::Config.configure` should support `config[:engage] = true`, `false`, or `nil`: `true` engages sanitization, `false` leaves messages unchanged, and `nil` falls through to `config[:activation_proc]`. `config[:activation_proc]` should be a callable that receives the Mail message and whose truthy or falsey return value decides whether that message is sanitized when `force_sanitize` and `engage` are both `nil`; by default the gem should be inert and leave messages unchanged.\n\nFor a concrete session, after configuring `sanitized_to: \"safe@example.test\"` and `engage: true`, delivering a message addressed to `real@example.test` should run the normal sanitizing flow so the delivered message is addressed to `safe@example.test` and records the original recipient header. With the same safe recipient config but `engage: false`, delivering the same message should keep `real@example.test` and should not add original-recipient sanitization headers. If `force_sanitize` is set to `false`, it should keep the original recipient even when `activation_proc` returns true; if `force_sanitize` is set to `true`, it should sanitize even when configured activation would otherwise deny it. Messages with `perform_deliveries` false should never be sanitized.\n\nI also need scoped overrides: `SanitizeEmail.sanitary(config_options = {}) { ... }` should require a block, temporarily merge the provided config options for deliveries inside the block, force sanitization by default, and put the prior config and force state back after the block exits even if the block raises. If `sanitary` receives `engage:` or `activation_proc:` in its options, those options should decide activation instead of the default force-on behavior. `SanitizeEmail.unsanitary { ... }` should require a block, force deliveries inside the block to remain unsanitized, and put the prior force state back afterward. Calling either scoped method without a block should raise `SanitizeEmail::MissingBlockParameter` with a message naming the method that needs a block.\n\nFor compatibility, `config[:local_environments]` in Rails should map to an activation proc that engages only when `Rails.env` is included in that list, and configuring deprecated `config[:force_sanitize]` should warn and copy that value into `SanitizeEmail.force_sanitize`."} {"task_id": "format-code-task-001228", "source_id": "format-code-task-001228", "domain": "code", "task_path": "tasks/format-code-task-001228", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:7078e28bd86a1b64fc8111bc1368f97f2d5ba004fa8ee9a0cbd70f7f207c9913", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Rename `CountsPredictor` and modernize its API for consistency with `MapEvaluator`\n\nRight now we have two classes that essentially do the same job — compute predicted counts (`npred`) from a model and a set of IRFs — but they're inconsistent:\n\n- In the `map` package we have `MapEvaluator`, which exposes a single method that returns the predicted counts directly.\n- In the `spectrum` package we have `CountsPredictor`, with a clunky two-step usage pattern:\n\n```python\npredictor = CountsPredictor(model=model, aeff=aeff, edisp=edisp, livetime=livetime)\npredictor.run()\nresult = predictor.npred\n```\n\nYou have to remember to call `run()` first, and the result lives on a `.npred` attribute rather than being returned. That's awkward, and the name `CountsPredictor` doesn't line up with the `*Evaluator` naming used on the map side.\n\n### Proposal\n\nBring the spectrum-side class in line with `MapEvaluator`:\n\n1. Rename the class so its name matches the `*Evaluator` style used elsewhere for the equivalent map-side functionality.\n2. Replace the `run()` + `.npred` attribute pattern with a single method call that computes and **returns** the predicted `CountsSpectrum` directly, so callers can write something like:\n\n ```python\n result = evaluator.(...)\n ```\n\n instead of needing two separate steps.\n\nAll the existing constructor arguments (`model`, `aeff`, `edisp`, `livetime`, `e_true`) should keep working the same way; only the class name and the way you trigger the computation / get the result need to change.\n\n### Callers to update\n\nThere are several places inside gammapy that currently use `CountsPredictor` via the old two-step pattern and need to be migrated to the new API:\n\n- `gammapy/spectrum/fit.py` (used inside `SpectrumDataset` and `SpectrumFit._predict_counts_helper`)\n- `gammapy/spectrum/observation.py` (`SpectrumObservation.predicted_counts`)\n- `gammapy/spectrum/simulation.py` (`SpectrumSimulation.npred_source` / `npred_background`)\n- `gammapy/spectrum/sensitivity.py` (`SensitivityEstimator.run`)\n- `gammapy/time/lightcurve.py` (`LightCurveEstimator.compute_flux_point`)\n\nAnd of course `__all__` / docstrings / the example in the class docstring should be updated to reflect the new name and usage.\n\nThis is the implementation of the proposed change PR 12 from PIG 7."} {"task_id": "format-code-task-001229", "source_id": "format-code-task-001229", "domain": "code", "task_path": "tasks/format-code-task-001229", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:358429649225eab6357ea1036be96277593262bb1551f3a7a42be3669f470334", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n`Dataset.npred_signal()` should take model name\n`Dataset.npred_signal()` takes a model as argument, whereas in most other places (eg:`FluxPointEstimator` we access models by their names. This create some confusion.\n\n@adonath shall I put in a PR to change this?"} {"task_id": "format-code-task-001231", "source_id": "format-code-task-001231", "domain": "code", "task_path": "tasks/format-code-task-001231", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a1065510fdfa9e5f9c443984d588a62fa1cbfefb53de126d69957f1a8e6e2551", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n**Is your feature request related to a problem? Please describe.**\nUsing the websocket server with web browsers causes inconsistent behavior with using tracking cookies because of the attributes (or lack of) for the cookie. \n\n**Describe the solution you'd like**\nI would like the ability to modify the http.Cookie attributes presented by the websocket server when tracking cookies are enabled. Specifically the ability to set `Secure: true` and `SameSite: http.SameSiteNoneMode`\n\n**Describe alternatives you've considered**\nFor now, we are cloning the project, hard coding the http.Cookie settings in `func (s *WebsocketServer) ServeHTTP(w http.ResponseWriter, r *http.Request)` and redirecting in go.mod.\n\n**Additional context**\nI'd expect the configuration to live as new fields on `WebsocketServer`, named something like `TrackingCookieSecureAttribute` and `TrackingCookieSameSiteAttribute`."} @@ -1104,7 +1065,6 @@ {"task_id": "format-code-task-001235", "source_id": "format-code-task-001235", "domain": "code", "task_path": "tasks/format-code-task-001235", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d20e0367c8d0c546bbca0d4e80d037b2fd3ecd3d5010fb5f79f1bb3f1a6e345a", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nRight now when a Shoot fails to reconcile because of bad cloud credentials, everything seems to get bucketed into `ERR_INFRA_UNAUTHORIZED` — so I can't tell from the status whether the credentials were straight-up rejected (wrong access key, auth failed) versus the credentials being valid but lacking the right permissions on the provider side. Those are two totally different things I'd handle differently (rotate the key vs. fix the IAM policy), but the error code doesn't distinguish them. Could there be a separate code specifically for the \"credentials didn't authenticate\" case so I can route alerting on it? Also `ERR_INFRA_INSUFFICIENT_PRIVILEGES` shows up too and it's never been clear how it relates to the unauthorized one — would be nice if the docs made the relationship and meaning clearer.\n\n# Expected outcomes\n\n- Authentication vs. authorization:\n - Infrastructure errors caused by credentials that fail authentication, such as invalid access keys or authentication failures, should be classified with a distinct exported error code, `ERR_INFRA_UNAUTHENTICATED`.\n - Infrastructure errors caused by authenticated requests that are not authorized, such as access-denied or forbidden-style provider responses, should continue to be classified as `ERR_INFRA_UNAUTHORIZED`.\n - `DetermineErrorCodes` should distinguish these two categories so callers can route alerts differently for authentication failures versus authorization failures.\n\n- Public error-code surface:\n - The public API should expose an `ErrorInfraUnauthenticated` error code whose string value is `ERR_INFRA_UNAUTHENTICATED`.\n - The new unauthenticated infrastructure code should be treated consistently with the existing non-retryable infrastructure credential/permission error codes.\n - `ERR_INFRA_INSUFFICIENT_PRIVILEGES` should remain understandable as a legacy/deprecated code whose meaning is covered by `ERR_INFRA_UNAUTHORIZED`.\n\n- Documentation:\n - The Shoot status documentation should list `ERR_INFRA_UNAUTHENTICATED` and describe it as the code for missing or invalid authentication credentials.\n - The documentation for `ERR_INFRA_UNAUTHORIZED` should describe authorization refusal rather than invalid credentials.\n - The documentation for `ERR_INFRA_INSUFFICIENT_PRIVILEGES` should make clear that it is deprecated in favor of `ERR_INFRA_UNAUTHORIZED`.\n\n# Implementation notes\n\nThe concrete implementation approach is up to the implementer. Choose whatever data structures, matching rules, and integration points fit the existing codebase, as long as the externally visible error-code classification, public constants, non-retryable handling, and documentation behavior match the outcomes above."} {"task_id": "format-code-task-001236", "source_id": "format-code-task-001236", "domain": "code", "task_path": "tasks/format-code-task-001236", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:03237f1268797defb438e6a63db6b11a989ca0939ec08c597b84eb9c62280e1d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Shoot deletion blocks on `List`-ing resources whose API endpoint is already gone\n\nWe're hitting an issue during shoot deletion where the generic resource cleanup in `pkg/utils/kubernetes/client` refuses to make progress.\n\nScenario: by the time the cleanup pass runs, some of the aggregated/extension API endpoints on the cluster are already torn down. When the cleanup tries to `List` resources of those kinds, the apiserver returns a 404 for the whole collection — i.e. there's literally no such API serving anymore, so semantically there is nothing left to clean up.\n\nThe cleanup helpers, however, propagate that 404 as a fatal error. So `Clean` / `EnsureGone` for those object lists never succeed, and shoot deletion stalls on resources that are already, by any reasonable definition, gone.\n\nThe closely related case where the kind isn't registered at the apiserver at all (no matching REST mapping) is already handled — those errors are swallowed and the cleanup correctly treats the collection as empty. It seems inconsistent that \"kind not known to discovery\" is treated as \"nothing to do\" while \"kind's API endpoint no longer there\" is treated as a hard failure: from the operator's point of view both mean the same thing (the resources can't possibly still exist).\n\nExpectation: when the cleanup / ensure-gone helpers encounter that situation while listing or fetching the target object(s), they should consider the work done and let deletion proceed, the same way they already do for unknown kinds. The same reasoning applies to the single-object `Get` paths used by the per-object cleanup action."} {"task_id": "format-code-task-001237", "source_id": "format-code-task-001237", "domain": "code", "task_path": "tasks/format-code-task-001237", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:290857b3d717fa3a212e94ec8d48c4de6a5c496200dd3a1f5e78025c5101b69f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nShoot conditions are not getting populated on first reconciliation\n**How to categorize this issue?**\n\n/area control-plane\n/kind bug\n\n**What happened**:\nWhen shoot is created its conditions such as `APISERVER`, `Control Plane` etc are not getting populated correctly in the shoot `status` on the first reconciliation of shoot. Though with the next reconciliation, these conditions are getting populated in shoot status correctly.\n\n**What you expected to happen**:\nWhen shoot is created it should set `APISERVER`, `Control Plane` etc other conditions properly in shoot status on the first reconciliation only.\n\n**How to reproduce it (as minimally and precisely as possible)**:\nCreate a shoot with 629e94d066f09d0af2888e2511c19b6189b845e2 `Gardener` version and check the following:\n```\n$ kubectl get shoot -A -o wide \n\nNAMESPACE NAME CLOUDPROFILE PROVIDER REGION SEED K8S VERSION HIBERNATION LAST OPERATION STATUS PURPOSE GARDENER VERSION APISERVER CONTROL NODES SYSTEM AGE\ngarden-local local local local local local 1.25.4 Awake Create Processing (10%) healthy evaluation v1.63.0-dev 10m\n```\n\nInstead of condition to be `` it should have been set to `Progressing` or `Unknown` as per shoot healthiness as follows:\n\n```\nNAMESPACE NAME CLOUDPROFILE PROVIDER REGION SEED K8S VERSION HIBERNATION LAST OPERATION STATUS PURPOSE GARDENER VERSION APISERVER CONTROL NODES SYSTEM AGE\ngarden-local local local local local local 1.25.4 Awake Create Processing (81%) healthy evaluation v1.63.0-dev True Progressing Progressing Progressing 3m5s\n```\n\n**Anything else we need to know?**:\nIt happens if shoot has no seed name in spec during creation.\nIt works with commit 73059233c0214553fa3ce79b21cbc777ff563ac7. So probably this issue is introduced with #7206.\n\n**Environment**: provider-local\n\n- Gardener version: 629e94d066f09d0af2888e2511c19b6189b845e2\n- Kubernetes version (use `kubectl version`):\n- Cloud provider or hardware configuration:\n- Others:"} -{"task_id": "format-code-task-001238", "source_id": "format-code-task-001238", "domain": "code", "task_path": "tasks/format-code-task-001238", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:3bba56698d7259805d1125c29106d47bbbee0632bf7c5fe520e655675713abb7", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the Go media title translator to expose `Translate(name string) string` so release-style media filenames can be turned into clean display titles. For `Translate(\"Godzilla.2014.720p.BluRay.x264-LEONARDO_[scarabey.org].mkv\")`, it should return `\"Godzilla\"`. For `Translate(\"Godzilla 2014\")`, it should return `\"Godzilla\"`. For names without a year or season/episode marker, it should still replace dots with spaces, remove bracketed release-group text, remove the tokens `720p`, `1080p`, `x264`, `BluRay`, `mkv`, `avi`, `mp4`, `(`, and `)`, trim surrounding whitespace, and return the cleaned string; for example `Translate(\"[Group]Plain.Title.1080p.mkv\")` should return `\"Plain Title\"`. It should also stop the title at a four-digit year or an `SxxExx` episode marker, so `Translate(\"Example.Show.S02E03.1080p.mkv\")` returns `\"Example Show\"`. The function should accept any string input, including an empty string, without returning an error or panicking; `Translate(\"\")` should return `\"\"`. Calling it multiple times with the same input should produce the same output and should not perform filesystem, network, or other external side effects."} {"task_id": "format-code-task-001239", "source_id": "format-code-task-001239", "domain": "code", "task_path": "tasks/format-code-task-001239", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:bd864005d68f51b1f7cd64b948bfe558dc52fe8569cd2d1a1f3b43c4ea589a59", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n[gatsby-remark-images]: bug: uses filename as alt text when showCaptions is true\n## Description\n\nSince https://github.com/gatsbyjs/gatsby/pull/13489, when using `showCaptions:true` `gatsby-remark-images` inserts the file name, when using the standard img snippet:\n\n```\n![](./img.jpg)\n```\n\n### Steps to reproduce\n1. Enable showCaptions:true with latest version of plugin\n2. Add `![](./img.jpg)` to a markdown\n\n### Expected result\nShouldn't be any caption shown\n\n### Actual result\nThe file name is inserted as caption\n\n### Temporary workaround\nYou can insert a space between [ ], and then a space is shown instead, at least not visible.\n\n\n### Environment\n\n```\n\n System:\n OS: macOS 10.14.4\n CPU: (8) x64 Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz\n Shell: 3.2.57 - /bin/bash\n Binaries:\n Node: 8.15.1 - ~/n/bin/node\n Yarn: 1.15.2 - /usr/local/bin/yarn\n npm: 6.4.1 - ~/n/bin/npm\n Languages:\n Python: 2.7.16 - /usr/local/bin/python\n Browsers:\n Chrome: 74.0.3729.157\n Firefox: 66.0.5\n Safari: 12.1\n npmPackages:\n gatsby: 2.5.x => 2.5.6 \n gatsby-image: ^2.1.0 => 2.1.0 \n gatsby-plugin-react-helmet: ^3.0.12 => 3.0.12 \n gatsby-plugin-sass: ^2.0.11 => 2.0.11 \n gatsby-plugin-sharp: ^2.0.37 => 2.0.37 \n gatsby-remark-copy-linked-files: ^2.0.12 => 2.0.12 \n gatsby-remark-images: 3.x => 3.0.11 \n gatsby-remark-prismjs: ^3.2.9 => 3.2.9 \n gatsby-remark-responsive-iframe: ^2.1.1 => 2.1.1 \n gatsby-remark-smartypants: ^2.0.9 => 2.0.9 \n gatsby-source-filesystem: ^2.0.36 => 2.0.36 \n gatsby-transformer-remark: ^2.3.12 => 2.3.12 \n gatsby-transformer-sharp: ^2.1.19 => 2.1.19 \n npmGlobalPackages:\n gatsby-cli: 2.5.15\n```"} {"task_id": "format-code-task-001240", "source_id": "format-code-task-001240", "domain": "code", "task_path": "tasks/format-code-task-001240", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:639079f77a8f5c150f3d99e6a9e694b662e378f91db681777fabb5a2d3cb9d02", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want `gz::sim::SdfEntityCreator` to support creating ECS entities from SDF projectors. Given an existing `SdfEntityCreator`, calling `Entity CreateEntities(const sdf::Projector *)` with a projector named `projector`, a raw pose of `(1, 2, 3, 0, 0, 0)`, near clip `2.0`, far clip `7.0`, horizontal FOV `0.5`, texture `path/to/dummy_image.png`, and visibility flags `0x01` should allocate one entity and return its ID. That entity should have a `components::Projector` component containing the same `sdf::Projector` data, a `components::Pose` component resolved from the projector semantic pose, and a `components::Name` component with `projector`. If I call `CreateEntities(const sdf::Link *)` on a link that contains that projector, the creator should also create the projector entity, set its parent to the returned link entity, and preserve the projector's name, pose, clip distances, FOV, texture, and visibility flags in the ECS components. A link with multiple SDF projectors should create one child projector entity for each projector."} {"task_id": "format-code-task-001241", "source_id": "format-code-task-001241", "domain": "code", "task_path": "tasks/format-code-task-001241", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:f12f88875c2dbcb5728380a78351990ff966560c31574c6e31834c8d2b37ed4f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want stateful data-series resampling APIs in `pyalgotrade.dataseries.resampled`: `ResampledBarDataSeries(dataSeries, frequency, maxLen=None)` for OHLCV bars and `ResampledDataSeries(dataSeries, frequency, aggfun, maxLen=None)` for generic values. Each object subscribes to the source data series' new-value event, keeps the current time bucket open, and appends one grouped value to itself when a later source value crosses into the next bucket. `pushLast()` should flush the currently open bucket, and `checkNow(dateTime)` should flush it when `dateTime` no longer belongs to that bucket.\n\nFor `ResampledBarDataSeries`, the input must be a `pyalgotrade.dataseries.bards.BarDataSeries`; passing a different data series raises `Exception(\"dataSeries must be a dataseries.bards.BarDataSeries instance\")`. Given second bars at `2011-01-01 01:01:01` with open `2.1`, high `3`, low `1`, close `2`, volume `10`, adjusted close `1`; `2011-01-01 01:01:02` with open `2`, high `3`, low `1`, close `2.3`, volume `10`, adjusted close `2`; and `2011-01-01 01:02:01` with open `2`, high `3`, low `1`, close `2`, volume `10`, adjusted close `2`, a one-minute `ResampledBarDataSeries` should have one completed bar after the third append. That completed bar should be dated `2011-01-01 01:01:00`, use the first open `2.1`, max high `3`, min low `1`, last close `2.3`, summed volume `20`, last adjusted close `2`, and the requested output frequency. After `pushLast()`, it should append the second minute's bar dated `2011-01-01 01:02:00`.\n\nFor `ResampledDataSeries`, the `aggfun` receives the list of values collected in a bucket and its return value is appended with the bucket's beginning datetime. For example, wrapping the close-price series from the same three bars with `ResampledDataSeries(closeSeries, bar.Frequency.MINUTE, sum)` should append `4.3` for the first minute after the third source bar arrives, and after `pushLast()` it should append `2` for the second minute. Unsupported resampling frequencies should raise `Exception(\"Unsupported frequency\")` during construction."} @@ -1120,7 +1080,6 @@ {"task_id": "format-code-task-001252", "source_id": "format-code-task-001252", "domain": "code", "task_path": "tasks/format-code-task-001252", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:144fd0cdafb90caac8a00b2857839fbf8e4fb8693860eec30de6d028d9230185", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nThe text, below element, should not be capitalized as it changes meaning completely\n### Expected behavior\nWhen Taiko executes the text should display\n```\nWrote BR3 4AS into the textBox below element with text Postcode\n```\n\n### Actual behavior\n1. When Taiko executes the text should display\n```\nWrote BR3 4AS into the textBox Below Element with text Postcode\n```\n2. The text **below element** should not be capitalized as it changes meaning completely.\n\n### Steps to reproduce\n1. Execute the script [Taiko-BT-Headless.js](https://github.com/amitsarkar007/Taiko-Scripts/blob/master/Taiko-BT-Headless.js)\n2. Check the terminal for the output\n```\ntaiko .\\Taiko-BT-Headless.js\n[PASS] Browser opened\n[PASS] Navigated to URL http://bt.com\n[PASS] Clicked element matching text \"OK\" 1 times\n[PASS] Clicked element matching text \"Broadband\" 1 times\n[PASS] Clicked element matching text \"Fibre broadband\" 1 times\n[PASS] Clicked element matching text \"See broadband deals\" 1 times\n[PASS] Clicked element matching text \"Add and continue\" 1 times\n[PASS] Wrote BR3 4AS into the textBox Below Element with text Postcode \n[PASS] Clicked element matching text \"Check availability\" 1 times\n[PASS] Clicked button with label 55 Eden Road 1 times\n[PASS] Clicked element matching text \"Confirm address\" 1 times\n[PASS] Browser closed\n```\n\n### Versions\n```\ntaiko --version\nVersion: 1.0.16 (Chromium: 85.0.4168.0) RELEASE\n\nnode --version\nv12.18.3\n```"} {"task_id": "format-code-task-001253", "source_id": "format-code-task-001253", "domain": "code", "task_path": "tasks/format-code-task-001253", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c9359fd322a64548b7b1c3448554dc112139ad4eee29b9e701beca2451b0c4cf", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## External `$ref` resolution breaks when the base spec is loaded over HTTP\n\nI'm using `kin-openapi` to load an OpenAPI 3 spec that's hosted on an HTTP server. The spec is split across multiple files — the root document references other schema files via `$ref`, e.g.:\n\n```yaml\n# served at http://example.com/schemas/openapi.yaml\ncomponents:\n schemas:\n Pet:\n $ref: './pet.yaml'\n```\n\nwith `pet.yaml` sitting next to it on the same server.\n\nI load it like this:\n\n```go\nloader := openapi3.NewSwaggerLoader()\nloader.IsExternalRefsAllowed = true\n\nu, _ := url.Parse(\"http://example.com/schemas/openapi.yaml\")\nswagger, err := loader.LoadSwaggerFromURI(u)\n```\n\nThe external `$ref` to `pet.yaml` doesn't get resolved correctly — the loader ends up trying to fetch from a URL that doesn't actually exist on the server, so I either get a fetch error or an unresolved-ref error coming back from `LoadSwaggerFromURI`.\n\nThe same exact spec layout works fine when I load it from local disk (using a filesystem path as the base) — refs to sibling files resolve and the spec loads cleanly. It only goes wrong when the base location is an `http://` URL.\n\nI'd expect external `$ref`s to work the same way regardless of whether the base spec was loaded from a local file or from an HTTP URL — sibling refs in the same directory should resolve in both cases."} {"task_id": "format-code-task-001254", "source_id": "format-code-task-001254", "domain": "code", "task_path": "tasks/format-code-task-001254", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:c767b59621383e2bca4737c3a566522cbd27dd70a06cd19e92ad19ae0571b94e", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\n我这边用 openapi3filter 校验一个 `Content-Type: application/zip` 的接口时,现在还得自己额外注册 body decoder,不然直接卡在不支持这个 media type 上。能不能让 `application/zip` 默认就能被识别并解出来,后面照常走 schema 校验?\n\n# Expected outcomes\n\n- `openapi3filter` 在默认配置下应支持 `application/zip` 请求体的 body decoding;调用方不需要额外注册 decoder,也不应再因为该 media type 缺少内置 decoder 而在解码阶段失败。\n- 当 `Content-Type` 为 `application/zip` 且 body 是有效 zip archive 时,验证流程应将 zip 中的文件内容解码为可用于后续 schema 校验的字符串值。\n- `openapi3filter.ZipFileBodyDecoder` 应作为可复用的公开 body decoder 提供,并能从 zip archive 中读取文件内容,以 `string` 形式返回;如果读取 body 或解析 zip archive 失败,应返回错误。\n- 当 `Content-Type` 为 `application/zip` 但 body 不是合法 zip archive 时,失败应来自 zip 解码/解析过程,而不是缺少或不支持 `application/zip` decoder。\n\n# Implementation notes\n\n- 具体的读取方式、缓冲策略、错误包装方式以及 decoder 注册位置由实现者决定。\n- 只要外部行为满足上述结果,可以复用现有 body decoder 机制或以等价方式接入验证流程。"} -{"task_id": "format-code-task-001255", "source_id": "format-code-task-001255", "domain": "code", "task_path": "tasks/format-code-task-001255", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:0eb1fff1ee121e4e478d90be6bc48f6be54ed1c462a36e585d9f03d31f4b89a5", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the Go library to expose response validation for a route-matched OpenAPI operation with `ValidateResponse(ctx context.Context, input *ResponseValidationInput) error`. `ResponseValidationInput` should carry the already-built `*RequestValidationInput`, response `Status int`, response `Header http.Header`, response `Body io.ReadCloser`, and optional `*Options`, and `SetBodyBytes(value []byte) *ResponseValidationInput` should replace the response body with a rereadable body containing those bytes.\n\nFor a request whose method is `HEAD`, `ValidateResponse` should return nil without validating the response body. For response statuses such as 304, 301, 307, and 308, it should also return nil without further validation. For a normal documented response, such as a 200 response with `Content-Type: application/json`, body `{\"id\":123}`, and an OpenAPI schema requiring numeric `id`, it should return nil and leave `input.Body` readable again with the same bytes after validation. If the operation defines a default response and the concrete status has no response entry, the default response should be used.\n\nWhen `Options.IncludeResponseStatus` is false, an undocumented response status with no default response should be accepted; when it is true, the same input should return a `*ResponseError` whose message is `status is not supported`. Required response headers should be decoded according to their OpenAPI serialization style and validated against their schemas; if a required header such as `X-Trace` is missing, return a `*ResponseError` with message `response header \"X-Trace\" missing`, and if a present header fails its schema, return a `*ResponseError` saying that header does not match the schema. If `Options.ExcludeResponseBody` is true, header and status validation should still run, but body content and schema validation should be skipped.\n\nFor body validation, the function should select the response media type from the `Content-Type` header, decode the body using registered body decoders, and validate it as a response schema, including write-only restrictions unless `Options.ExcludeWriteOnlyValidations` is true. A response with `Content-Type: text/plain` when only `application/json` is documented should return a `*ResponseError` whose message is `response header Content-Type has unexpected value: \"text/plain\"`. A JSON response body that decodes successfully but violates the schema should return a `*ResponseError` whose message starts with `response body doesn't match schema`, and `ResponseError.Unwrap()` should expose the underlying decode, read, or schema error when one exists."} {"task_id": "format-code-task-001256", "source_id": "format-code-task-001256", "domain": "code", "task_path": "tasks/format-code-task-001256", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:339fd45bd663465fe5ccb55466af884c59e6057870605275f8d2ebe83a49f658", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## S3 object tagging is not supported by the mock\n\nI'm using `moto` to mock S3 in my test suite. Part of the code under test attaches tags to objects (we use them for downstream lifecycle/cost-allocation logic) and later reads them back. Against real S3 this works fine via boto3's `put_object_tagging` / `get_object_tagging`, but under `@mock_s3` it doesn't behave correctly — there's no working round-trip for object tags.\n\nMinimal repro:\n\n```python\nimport boto3\nfrom moto import mock_s3\n\n@mock_s3\ndef test_object_tags():\n client = boto3.client(\"s3\", region_name=\"us-east-1\")\n client.create_bucket(Bucket=\"mybucket\")\n client.put_object(Bucket=\"mybucket\", Key=\"myfile\", Body=b\"hello\")\n\n client.put_object_tagging(\n Bucket=\"mybucket\",\n Key=\"myfile\",\n Tagging={\"TagSet\": [\n {\"Key\": \"environment\", \"Value\": \"staging\"},\n {\"Key\": \"team\", \"Value\": \"data\"},\n ]},\n )\n\n resp = client.get_object_tagging(Bucket=\"mybucket\", Key=\"myfile\")\n print(resp[\"TagSet\"]) # expected: the two tags I just put\n```\n\nI'd also expect the same to work when tags are supplied inline at upload time via the `Tagging` parameter on `put_object` (i.e. the `x-amz-tagging` header form, like `environment=staging&team=data`), and then retrieved with `get_object_tagging`.\n\nCould object tagging support be added so `put_object_tagging` / `get_object_tagging` (and the inline `Tagging=` on `put_object`) round-trip correctly under `mock_s3`?"} {"task_id": "format-code-task-001257", "source_id": "format-code-task-001257", "domain": "code", "task_path": "tasks/format-code-task-001257", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:26a664003d7830da9c072ee03f6cd4a55aa1a0f381d8b1bd232836782f59d252", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\nI'm using moto's CloudFormation mocking, and my template has an `AWS::EC2::VPCGatewayAttachment` that attaches a VPN gateway via `VpnGatewayId`. When I call `create_stack`, it blows up with `KeyError: 'InternetGatewayId'`. On top of that, I'm also declaring an `AWS::EC2::VPNGateway` resource in the same template, and that doesn't seem to be recognized by moto's CloudFormation at all.\n\n## Expected outcomes\n\n- CloudFormation stack creation should support an `AWS::EC2::VPCGatewayAttachment` whose properties attach a VPN gateway by `VpnGatewayId`; creating such a stack should not fail because an internet gateway property is absent.\n- The resulting mocked EC2 state should show the VPN gateway attached to the intended VPC after the stack is created.\n- Existing CloudFormation support for `AWS::EC2::VPCGatewayAttachment` with `InternetGatewayId` should continue to create an internet gateway attachment successfully.\n- CloudFormation should recognize and create `AWS::EC2::VPNGateway` resources with the standard required gateway type property and the optional Amazon-side ASN property.\n- A CloudFormation-created `AWS::EC2::VPNGateway` should have a usable physical resource id so that other resources in the same template can reference it with `Ref`.\n\n## Implementation notes\n\n- Match moto’s existing CloudFormation resource modeling conventions and EC2 backend behavior.\n- The exact internal structure, helper methods, and validation location are up to the implementer, as long as the externally observable CloudFormation and EC2 behavior above is satisfied."} {"task_id": "format-code-task-001258", "source_id": "format-code-task-001258", "domain": "code", "task_path": "tasks/format-code-task-001258", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:50c49ffee82e9a7fc7b6eff410f73cb9552fc67b6b28ec09baea944d2d2bd8a2", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nMoto's dynamodb2 currently doesn't throw an error for this situation, where as the real dynamodb does.\n\nFor a query like so:\n\n```python\ntable.update_item(\n Key={...},\n UpdateExpression='ADD x :one SET a = :a ADD y :one',\n ExpressionAttributeValues={':one': 1, ':a': 'lore ipsum'},\n)\n```\n\nthe real dynamo will return the error:\n\n```txt\nAn error occurred (ValidationException) when calling the UpdateItem operation: Invalid UpdateExpression: The \"ADD\" section can only be used once in an update expression;\n```\n\nWhereas moto will happily process the query."} @@ -1160,8 +1119,6 @@ {"task_id": "format-code-task-001302", "source_id": "format-code-task-001302", "domain": "code", "task_path": "tasks/format-code-task-001302", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6cf1fc0dfbb67a190a69348a159a8ecfaf39455f753ddbe8b9445d717c48f3d1", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\n我这边用 `database.NewPaginator` 分页一个带 `Preload` 关联的 GORM 查询时,列表数据本身能查出来,但分页的 total/page 会不对,有时候还会报错。能不能让这种带 `Preload` 的分页也正常算总数?\n\n## Expected Outcomes\n\n- 使用 `database.NewPaginator` 对已配置 GORM `Preload` 的查询分页时,分页器应能按原查询条件正确计算总记录数与最大页数。\n- 带 `Preload` 的分页查询不应因为关联预加载而在分页统计阶段失败。\n- 修复不应破坏实际列表查询:原查询请求预加载的关联数据仍应随分页结果正常加载。\n\n## Implementation Notes\n\n请保持现有公开 API 与调用方式兼容,避免要求调用者为带关联预加载的分页场景额外改写查询。"} {"task_id": "format-code-task-001303", "source_id": "format-code-task-001303", "domain": "code", "task_path": "tasks/format-code-task-001303", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:9db089af4e00830fb84207d610df947952f78a8bbebd47773a82cb6827e6a08f", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the `sd/lb` package to provide retrying endpoint wrappers for load-balanced clients. The public API should include `func Retry(max int, timeout time.Duration, b Balancer) endpoint.Endpoint`, `type Callback func(n int, received error) (keepTrying bool, replacement error)`, and `func RetryWithCallback(timeout time.Duration, b Balancer, cb Callback) endpoint.Endpoint`.\n\nWhen I create `retry := Retry(3, time.Second, balancer)` and call `retry(ctx, request)`, each failed attempt should ask `balancer.Endpoint()` for an endpoint, invoke that endpoint with the same request under the retry timeout, and continue until an endpoint returns a successful response, the attempt limit is reached, or the timeout expires. For example, with a round-robin balancer over endpoints that return `error one`, then `error two`, then `\"ok\"`, `Retry(3, time.Second, balancer)(ctx, req)` should return `\"ok\", nil`; with `Retry(2, time.Second, balancer)` over the same endpoints it should return an error after the second failed endpoint.\n\nIf the balancer has no endpoints, the returned endpoint should surface that failure through the retry path. If the timeout expires before an attempt returns, the returned endpoint should return the context deadline error. Passing a nil `Balancer` to `RetryWithCallback` should panic with `nil Balancer`.\n\n`RetryWithCallback` should call the callback after each failed attempt with the 1-based attempt number and the exact error received from the balancer or endpoint. If the callback returns `false`, retries should stop immediately; if it also returns a replacement error, that replacement should become the final error. A nil callback should mean retry indefinitely until success or timeout.\n\nRetry failures should be returned as a public `RetryError` value with `RawErrors []error`, `Final error`, and an `Error() string` method. The final error string should be the final error message, and when multiple failures occurred it should append the earlier errors in the form `final error (previously: first error; second error)`."} {"task_id": "format-code-task-001304", "source_id": "format-code-task-001304", "domain": "code", "task_path": "tasks/format-code-task-001304", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:004346aa2191258d8642620f175fbe57966024df9ecd68c6ad4df4b1c8783811", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the AMQP transport package to provide a client-side request/response publisher API for invoking remote Go kit endpoints over AMQP. The public constructor should be `NewPublisher(ch Channel, q *amqp.Queue, enc EncodeRequestFunc, dec DecodeResponseFunc, options ...PublisherOption) *Publisher`, where `EncodeRequestFunc` writes the domain request into an `amqp.Publishing` and `DecodeResponseFunc` converts the matching AMQP reply delivery back into a domain response. After construction, `Publisher.Endpoint() endpoint.Endpoint` should return an endpoint function that encodes the request, publishes it, waits for a reply with the same correlation ID, decodes that reply, and returns the decoded response.\n\nFor example, with a mock channel whose reply queue contains a delivery with correlation ID `correlation` and JSON body `{\"s\":437,\"n\":\"husky\"}`, a publisher configured with `PublisherBefore(SetCorrelationID(\"correlation\"))` and JSON encoders/decoders should publish the encoded request and return a response object with squadron `437` and name `husky`. If the request encoder returns `errors.New(\"err!\")`, the endpoint call should return that error without producing a decoded response; if the response decoder returns `errors.New(\"err!\")`, the endpoint call should return that decode error. `PublisherTimeout(d)` should bound the whole request/reply wait: if no matching reply arrives before the timeout, the endpoint should return the context deadline error.\n\nI also need publisher options for `PublisherBefore`, `PublisherAfter`, `PublisherDeliverer`, and `PublisherTimeout`. The default deliverer should publish with the exchange and routing key from the request context, consume from the configured reply queue, ignore deliveries whose correlation ID does not match, Ack the matching reply when consume auto-ack is false, and pass AMQP consume arguments from `SetConsumeArgs`; `SetConsumeAutoAck` should control the consume auto-ack flag. A `SendAndForgetDeliverer` option should publish the request and return immediately without waiting for a reply, so callers can use no-op or nil-tolerant response hooks/decoders for fire-and-forget calls."} -{"task_id": "format-code-task-001305", "source_id": "format-code-task-001305", "domain": "code", "task_path": "tasks/format-code-task-001305", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b31dd36f91dc46c80ce832c1ba34dbd631215406f215687b553387bb0b847f49", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the original `lark` package's `*Bot` to support heartbeat-based tenant access token renewal for chat bots. For a bot created with `lark.NewChatBot(appID, appSecret)`, calling `bot.StartHeartbeat() error` should synchronously request a tenant access token with the app credentials, store the returned token on the bot so `bot.TenantAccessToken()` and authenticated SDK calls can use it, and then start a background renewal loop. The public stop method should be `bot.StopHeartbeat()`, and calling it should stop that renewal loop so it does not keep fetching new tenant access tokens.\n\nThe first `StartHeartbeat` fetch is part of the method's observable behavior: if the Feishu/Lark auth request succeeds, `StartHeartbeat` returns nil and the bot has a non-empty tenant access token; if that initial auth request fails, `StartHeartbeat` returns the error and does not silently continue. `StartHeartbeat` should only be valid for chat bots; calling it on a notification bot created with `lark.NewNotificationBot(...)` should return `lark.ErrBotTypeError` and should not start any background renewal work. After the loop is running, each successful renewal should update the bot's stored tenant access token. The renewal interval should default to 10 seconds, but when the auth response includes an `expire` value greater than 20 seconds, the next renewal should wait `expire - 20` seconds. Later renewal errors should be logged and should not crash the caller's process."} -{"task_id": "format-code-task-001306", "source_id": "format-code-task-001306", "domain": "code", "task_path": "tasks/format-code-task-001306", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6c772f118e832add98fb916519907a0d061abebad84904263851ef439bed6db8", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want the Go SDK's chat bot upload APIs so a configured `Bot` can upload images and files to Feishu/Lark and return the platform keys needed for later messages.\n\nIn the root `lark` package, expose `func (bot Bot) UploadImage(string) (*UploadImageResponse, error)`, `func (bot Bot) UploadImageObject(image.Image) (*UploadImageResponse, error)`, and `func (bot Bot) UploadFile(UploadFileRequest) (*UploadFileResponse, error)`. In the `lark/v2` package, expose the context-aware forms `func (bot *Bot) UploadImage(context.Context, string) (*UploadImageResponse, error)`, `func (bot *Bot) UploadImageObject(context.Context, image.Image) (*UploadImageResponse, error)`, and `func (bot *Bot) UploadFile(context.Context, UploadFileRequest) (*UploadFileResponse, error)`.\n\n`UploadImage` should open the supplied local path, build a multipart POST to `/open-apis/im/v1/images` with `image_type=message` and a file part named `image`, set the multipart `Content-Type`, use the SDK's authenticated request flow, decode the JSON response, and return an `UploadImageResponse` whose `Data.ImageKey` contains the returned `image_key`. `UploadImageObject` should accept an `image.Image`, encode it as JPEG into the multipart `image` part using a stable form filename such as `temp_image`, post to the same image endpoint, and return the same response type.\n\n`UploadFileRequest` should provide `FileType string`, `FileName string`, `Duration int`, `Path string`, and `Reader io.Reader`. `UploadFile` should POST multipart data to `/open-apis/im/v1/files` with `file_type`, `file_name`, and a file part named `file`; when `Reader` is nil it should read bytes from `Path`, and when `Reader` is provided it should stream from that reader while using `FileName` as the form filename. For an mp4 upload with a positive `Duration`, include a `duration` form field formatted as decimal seconds; for other file types or non-positive durations, omit that field. It should decode the response into `UploadFileResponse` with `Data.FileKey` populated from `file_key`.\n\nA concrete session should work like: create/configure a chat `Bot`, call `UploadImage(\"./fixtures/test.jpg\")`, observe no Go error and a non-empty `resp.Data.ImageKey`; then call `UploadFile(UploadFileRequest{FileType: \"pdf\", FileName: \"hello.pdf\", Path: \"./fixtures/test.pdf\"})` and observe no Go error and a non-empty `resp.Data.FileKey`. Another session should call `UploadFile(UploadFileRequest{FileType: \"stream\", FileName: \"test-data.csv\", Reader: strings.NewReader(\"Name,Age\\nFoo,25\\n\")})` and upload those reader bytes without needing a filesystem path.\n\nIf opening the local path fails, multipart file creation fails, copying or JPEG encoding fails, closing the multipart writer fails, the authenticated request fails, or response decoding fails, the method should return `nil` for the response and the encountered error. The v2 methods must honor the supplied `context.Context` through the request path, including cancellation or timeout errors from the HTTP layer."} {"task_id": "format-code-task-001307", "source_id": "format-code-task-001307", "domain": "code", "task_path": "tasks/format-code-task-001307", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:2a3fdf6101a8769ad135377bc22b3d2df7ac785f1d981e58f13bb61fa2198064", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nThis isn't an issue with `go-logr` but it may be worth identifying as a potential trap for the unwary; I *will* update my blog [post](https://pretired.dazwilkin.com/posts/211018/).\n\nMy naive implementation of `RenderValuesHook` was:\n\n```golang\nrenderLabels := func(kvList []interface{}) []interface{} {\n // loggingLabels becomes the only label key\n return []interface{}{\n loggingLabels,\n funcr.PseudoStruct(kvList),\n }\n}\n```\n\nThis worked fine if `WithValues` is only called once per Logger. If `WithValues` is called again, the existing labels are nested within the new set, i.e.:\n\n```JSON\n{\n \"jsonPayload\": {\n \"logging.googleapis.com/labels\": {\n \"logging.googleapis.com/labels\": { <--- INCORRECT\n \"foo\": \"X\"\n },\n \"bar\": \"Y\"\n }\n }\n \"labels\": {\n \"instanceId\": \"00bf4bf0...\"\n }\n}\n``` \n\n> **NOTE** In my case, Google Cloud Logging no longer recognized the borked `logging.googleapis.com/labels` as special values and does not merge them with the `labels` field.\n\nUsing [`NewStdoutLogger`](https://github.com/go-logr/logr/blob/8d00e357f1cbbb9246ed8bbf03f2c8fe242d2ae9/example_test.go#L27), the issue does not occur:\n\n```Golang\n\tl := NewStdoutLogger()\n\tl.Info(\"info\")\n\n\tl = l.WithValues(\"foo\", \"X\")\n\tl.Info(\"info\")\n\n\tl = l.WithValues(\"bar\", \"Y\")\n\tl.Info(\"info\")\n```\nOutputs:\n\n```console\n\"level\"=0 \"msg\"=\"info\"\n\"level\"=0 \"msg\"=\"info\" \"foo\"=\"X\"\n\"level\"=0 \"msg\"=\"info\" \"foo\"=\"X\" \"bar\"=\"Y\"\n```\n\nSo, it's an issue with my implementation.\n\nI revised the implementation (improvements welcome):\n\n```golang\nrenderLabels := func(kvList []interface{}) []interface{} {\n // If loggingLabels is present, it will be the first label key\n k, _ := kvList[0].(string)\n if k == loggingLabels && len(kvList) > 2 {\n // The label values should be a PseudoStruct\n v, _ := kvList[1].(funcr.PseudoStruct)\n // Append additional ([2:]) label keys|values to the existing loggingLabels\n // loggingLabels becomes the only label key\n return []interface{}{\n loggingLabels,\n append(v, funcr.PseudoStruct(kvList[2:])...),\n }\n }\n\n // loggingLabels becomes the only label key\n return []interface{}{\n loggingLabels,\n funcr.PseudoStruct(kvList),\n }\n}\n```\n\nAnd, replacing `NewStdoutLogger` with `NewStructuredLogger`, I get:\n\n```console\n{\"level\":0,\"msg\":\"info\"}\n{\"level\":0,\"msg\":\"info\",\"logging.googleapis.com/labels\":{\"foo\":\"X\"}}\n{\"level\":0,\"msg\":\"info\",\"logging.googleapis.com/labels\":{\"foo\":\"X\",\"bar\":\"Y\"}}\n```"} {"task_id": "format-code-task-001308", "source_id": "format-code-task-001308", "domain": "code", "task_path": "tasks/format-code-task-001308", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:265382a8b03463e43cb84e928ac0849cbf9fa3d94623f9ff6a382630cae01548", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\n我在用 go-ole 调 COM 的时候,很多 GUID 都是文档里直接给的 `{...}` 字符串,现在还得自己拆开填 GUID 结构体,挺容易写错;而且 fmt 打印出来也是结构体 dump,不方便对照。能不能让库直接从 GUID 字符串生成 GUID,并且打印时就是常见的 GUID 文本格式?\n\n# Expected outcomes\n\n- GUID parsing: `NewGUID(guid string) *GUID` should construct a `*GUID` from valid GUID text in any of these common forms: 32 contiguous hexadecimal characters, 36 characters with hyphens, or 38 characters with braces and hyphens.\n- GUID parsing should be case-insensitive for hexadecimal characters and should preserve the represented GUID value.\n- Invalid GUID text should fail clearly by returning `nil`, including malformed lengths, missing required braces or hyphens for formatted inputs, or non-hexadecimal characters.\n- GUID formatting: `(*GUID).String() string` should return the common brace-wrapped, hyphenated GUID text format using uppercase hexadecimal characters.\n- `fmt` formatting of a non-nil `*GUID` should use the same common GUID text representation rather than a Go struct dump.\n- Calling `String()` on a nil `*GUID` should return the empty GUID text `{00000000-0000-0000-0000-000000000000}`.\n\n# Implementation notes\n\n- Keep the behavior available through the public `ole` package API; the internal parsing and formatting approach is up to the implementer.\n- The implementation should remain pure Go and should not require callers to manually split GUID strings into struct fields.\n- Preserve existing GUID equality and COM interop behavior for GUID values constructed by other means."} {"task_id": "format-code-task-001309", "source_id": "format-code-task-001309", "domain": "code", "task_path": "tasks/format-code-task-001309", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:03ea79cf5abfec82eea6cb528c17fe4f46fb4b263ae4583717a4dff91099dc80", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want LARS request contexts to provide a body decoding helper with the method signature `Decode(includeFormQueryParams bool, maxMemory int64, v interface{}) (err error)` on `lars.Context` and `*lars.Ctx`. A handler should be able to receive its current request context, pass a pointer to an application struct, and have the helper choose a decoder from the request `Content-Type`, ignoring any `; charset=...` suffix.\n\nFor `Content-Type: application/json`, `Decode` should read at most `maxMemory` bytes from the request body and JSON-decode into `v`; for example a body `{\"Name\":\"Ana\"}` should populate `struct { Name string }{Name:\"Ana\"}` and return nil, while malformed JSON should return the JSON decoder error. For `Content-Type: application/xml`, it should likewise read at most `maxMemory` bytes and XML-decode into `v`, so `Ana` can populate a struct with a `Name` field.\n\nFor `Content-Type: application/x-www-form-urlencoded`, `Decode` should parse the submitted form and use form tags to fill struct fields. In a route like `/user/:id`, posting body `Name=Joey` to `/user/13` with `includeFormQueryParams=true` should populate `ID == 13` for `ID int `form:\"id\"`` and `Name == \"Joey\"`; with `includeFormQueryParams=false`, the same request should leave `ID == 0` while still setting `Name == \"Joey\"`. For `Content-Type: multipart/form-data`, the same include flag should control whether route/query values are included along with multipart value fields, and `maxMemory` should be passed to multipart parsing.\n\nIf form parsing or multipart parsing fails, `Decode` should return that parse error and not hide it. If the content type is unsupported or empty, `Decode` should return nil without decoding into the target. I also need `(*lars.LARS).BuiltInFormDecoder() *form.Decoder` to return a non-nil built-in form decoder so applications can register custom form decoding behavior before `Decode` handles URL-encoded or multipart form requests."} @@ -1233,7 +1190,6 @@ {"task_id": "format-code-task-001388", "source_id": "format-code-task-001388", "domain": "code", "task_path": "tasks/format-code-task-001388", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:d090c83877ad8b67e86f24c6de6b0c3979adbee315c99f0d6b84f95d6cc4d661", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nAzureMonitor: configuration editor should be disabled for readonly datasource\n**What would you like to be added**:\n\nWhen opening configuration editor for provisioned read-only Azure Monitor datasource, the controls are still editable.\n`DataSourceJsonData` has `readOnly` property which needs to be respected.\n\nAlso, because all controls are editable, it's possible to save the read-only datasource by clicking on **Load Subscriptions**."} {"task_id": "format-code-task-001389", "source_id": "format-code-task-001389", "domain": "code", "task_path": "tasks/format-code-task-001389", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:dd6c5768fafad2fe765f2c252dfb17cf83f7dca45a3b45f6dffcdb611a062dc8", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Configurable gRPC message size limits\n\nThe gRPC client module (`k6/net/grpc`) currently relies on the gRPC library's\nbuilt-in defaults for the maximum size of messages it will send and receive on a\nconnection. Some users load-test services that exchange large messages and need\nto raise that ceiling; others want to cap it deliberately. Today there's no way\nto control either limit from a script.\n\nAdd two optional parameters to the client's `connect(address, params)` call:\n\n- `maxReceiveSize` — the largest message, in bytes, the client will accept in a\n response on this connection.\n- `maxSendSize` — the largest message, in bytes, the client will send in a\n request on this connection.\n\nBehavior:\n\n- Both are optional. When a parameter is omitted (or left at its default), the\n connection keeps the current behavior and uses the gRPC library defaults — a\n script that never sets them must work exactly as before.\n- Each value must be an integer. A non-integer value (e.g. a string or boolean)\n must make `connect` fail with an error reading\n `invalid maxReceiveSize value: '', it needs to be an integer`\n (and the analogous message for `maxSendSize`).\n- A negative integer must make `connect` fail with an error reading\n `invalid maxReceiveSize value: '', it needs to be a positive integer`\n (and the analogous message for `maxSendSize`).\n- When `maxReceiveSize` is set to a positive value and the server returns a\n message larger than it, the RPC fails: the response's status is the\n resource-exhausted status code.\n- When `maxSendSize` is set to a positive value and the script tries to send a\n request larger than it, the RPC fails the same way.\n\nThe existing connect parameters and their validation (`plaintext`, `timeout`,\n`reflect`, and the rejection of unknown parameters) must keep working unchanged.\n"} {"task_id": "format-code-task-001390", "source_id": "format-code-task-001390", "domain": "code", "task_path": "tasks/format-code-task-001390", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b869f3dbe1717cc46afd9543e03110872337571ca3eeb4d3199e0c38fc90b872", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nPreventing storing environment variables' values in archive\n# What?\n\nAdd a new flag to a `k6 archive` that will prevent storing environment variables (passed with the `--env`) in the archive's `metadata.json`.\n\n# Why?\n\nSometimes scripts can use the environment variables in the init context and it's not possible to produce an archive without passing them, however storing the actual values of the environment variables can be harmful from the security perspective."} -{"task_id": "format-code-task-001391", "source_id": "format-code-task-001391", "domain": "code", "task_path": "tasks/format-code-task-001391", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:986369efa046d8837a4a235b57a243691fa44b0b567777b3c54e500bbd42cc8d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nQuery range step does not support duration string.\nFrom slack:\n\n> prometheus seems to accept a \"step\" parameter as either a duration string or float, but loki seems to >only accept integers representing seconds - are there plans for loki's API to be brought more in line with >Prometheus' API in this respect?\n\n\nEasy change to support and we should be as close as possible to Prometheus.\n\nPlease also update the doc."} {"task_id": "format-code-task-001392", "source_id": "format-code-task-001392", "domain": "code", "task_path": "tasks/format-code-task-001392", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:6500cd47bbd3a3ee6bab008c2413682f8b2b3d00c473a99fd9cb30a550f0854c", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nCanary 2.7.0 Push Mode Always Uses HTTP\n\n\n**Describe the bug**\nCanary push mode uses HTTP even if `-tls=true` is set.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n1. Configure Loki with a HTTPS frontend (we use AWS ALB).\n2. Start canary with the following configuration:\n\n`[\n \"-addr=loki-internal.alb:443\",\n \"-interval=10s\",\n \"-labelname=canary-id\",\n \"-labelvalue=canary-1234\",\n \"-push\",\n \"-tls=true\",\n \"-streamname=source\",\n \"-streamvalue=stdout\",\n \"-user=\",\n \"-pass=\"\n]`\n\n**Expected behavior**\nWhen `-tls=true` is set I'd expect Canary to use HTTPS when pushing.\n\n**Environment:**\n - Infrastructure: AWS ECS\n - Deployment tool: Terraform\n\n**Screenshots, Promtail config, or terminal output**\nWith above configuration, we get the following logs from ALB:\n\n`https 2022-11-15T00:34:21.063192Z app/loki-internal-alb/ghasjhya :56178 - -1 -1 -1 400 - 256 370 \"POST http://loki-internal.alb:443/loki/api/v1/push HTTP/1.1\" \"canary-push/2.7.0\" - - - \"-\" \"-\" \"-\" - 2022-11-15T00:34:21.062000Z \"-\" \"-\" \"-\" \"-\" \"-\" \"-\" \"-\"`"} {"task_id": "format-code-task-001393", "source_id": "format-code-task-001393", "domain": "code", "task_path": "tasks/format-code-task-001393", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:be8b3f4ad4978a9df511375cfb8090ea482cb20f1bb005ba7d891bcb517918b2", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nAdd ability to create outgoing webhook w/ PATCH HTTP Method via the UI\n### What would you like to see!\n\nadd the PATCH option to the list op http methods\n[\"GET\", \"POST\", \"PUT\", \"DELETE\", \"OPTIONS\"]\n\n### Product Area\n\nOther\n\n### Anything else to add?\n\n_No response_"} {"task_id": "format-code-task-001394", "source_id": "format-code-task-001394", "domain": "code", "task_path": "tasks/format-code-task-001394", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:ffdd1fe4a59e9353e41502424fbfedc2a14dee35dc85c7294a789d5c7d44bace", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n/escalate Slack Dropdown Duplicates Teams for Each Route in Direct Paging\n### What went wrong?\n\n**What happened**:\n- Teams with more than 1 Route defined in Direct Paging are being duplicated in the Create Escalation menu from the /escalate command. e.g. a Direct Paging Integration with 3 routes will be shown 3 times in the \"Team to notify\" menu (pictured below). It seems to stop incrementing at 3 (e.g. making 5 routes doesn't create 5 entries in the dropdown) but I don't know what to make of why that is.\n\n**What did you expect to happen**:\n- Expected that each Team would only appear once in the \"Team to notify\" dropdown menu.\n\n\n\"Screenshot\n\n![Screenshot 2023-11-20 110758](https://github.com/grafana/oncall/assets/80909828/97d5ca27-4d91-4a42-821d-a2d75d420e78)\n\n\n\n### How do we reproduce it?\n\n1. Create a Direct Paging Integration for a team.\n2. Create 2 or more Routes for that team's Direct Paging.\n3. Run the /escalate command in Slack, then select \"Team to notify\" -- in screenshots pictured above there are duplicate entries for this team displayed.\n\n\n### Grafana OnCall Version\n\nv1.3.59\n\n### Product Area\n\nChatops\n\n### Grafana OnCall Platform?\n\nKubernetes\n\n### User's Browser?\n\nSlack Production 4.35.126\n\n### Anything else to add?\n\n_No response_"} @@ -1280,7 +1236,6 @@ {"task_id": "format-code-task-001442", "source_id": "format-code-task-001442", "domain": "code", "task_path": "tasks/format-code-task-001442", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:9e0b474da7909369556d28a24032b69c38f5f675838fd85e08d8da1ccbdc9166", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## `hclwrite.TokensForValue` produces awkward single-line output for objects/maps\n\nI'm using `hclwrite` in a small Go tool that generates `.hcl` files\nprogrammatically — I build up a `cty.Value` (typically an object with a\nhandful of attributes, sometimes nested) and pass it through\n`TokensForValue` so I can write it out as HCL source for humans to read\nand edit.\n\nFor lists and tuples the output looks reasonable, but for objects and\nmaps everything gets crammed onto one line, separated by commas:\n\n```hcl\nconfig = { bar = 5, baz = true, foo = \"foo\" }\n```\n\nThis is pretty far from how the same value would normally be written by\nhand or by `terraform fmt`, where you get one attribute per line and no\ncommas:\n\n```hcl\nconfig = {\n bar = 5\n baz = true\n foo = \"foo\"\n}\n```\n\nIt's especially noticeable once the values get nested or the number of\nattributes grows past two or three — the single-line format becomes\ngenuinely hard to read, and diffs of the generated files are basically\nunreadable since any change to a single attribute rewrites the entire\nline.\n\nCould `TokensForValue` emit objects and maps in the conventional\nmulti-line style instead, so the generated output looks like the HCL\npeople actually write?"} {"task_id": "format-code-task-001444", "source_id": "format-code-task-001444", "domain": "code", "task_path": "tasks/format-code-task-001444", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a54fcfa670984bf04394db4693b6a480026765cbf1d6c1969a851b38b5adbcb8", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n### Job summary counters drift from the real allocation states\n\nI'm running a few jobs on a small Nomad cluster and using `nomad status ` to keep an eye on what's going on. After allocations cycle through their normal lifecycle (pending → running, completes, restarts, gets marked lost when I take a node down, etc.), the **Summary** block in `nomad status` stops matching reality.\n\nFor example, after running a job for a while and bouncing a client node, I'll see something like:\n\n- The allocation list shows N allocations actually running on the remaining nodes,\n- but the job summary reports a different number for `Running` / `Starting` / `Lost` / `Complete`.\n\nSometimes the running count is too high (looks like a previous state never got decremented when the alloc transitioned), sometimes a \"lost\" count never shows up after I stop a node even though the per-alloc client status correctly flips to lost. Restarting the server doesn't fix it — the summary stays wrong until I redeploy the job.\n\nI can reproduce this most reliably by:\n\n1. Submitting a job with a few task groups / a few instances each.\n2. Letting allocs come up so they're all in `running`.\n3. Either (a) shutting down a node that is hosting some of those allocs so they get marked lost, or (b) just letting the client report status updates back over a few cycles.\n4. Comparing `nomad status ` summary counts against the actual allocation list.\n\nThe per-allocation `ClientStatus` values look correct in the alloc listing — it's just the aggregated summary on the job that drifts. Once the summary is wrong it stays wrong, which makes the `nomad status` output unreliable for monitoring and for any automation we build on top of it.\n\nThe summary should always reflect the current states of the allocations that belong to the job."} {"task_id": "format-code-task-001445", "source_id": "format-code-task-001445", "domain": "code", "task_path": "tasks/format-code-task-001445", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:9596e71756e0d08d47bd807ec32ce0850723998bb3a4a6860db350bd7fe703c4", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Nomad client crashes during Consul fingerprinting when the agent's self response is incomplete\n\nI'm running a Nomad client alongside a Consul agent. In some of my environments\n(older Consul versions, plus a couple where ACLs restrict what the agent's\n`/v1/agent/self` endpoint returns), the Nomad client process dies shortly after\nstartup with a panic that comes out of the Consul fingerprinter — i.e. it\nblows up while populating the `consul.*` node attributes from whatever the\nConsul agent returned.\n\nIn environments where the Consul agent returns the \"full\" self info, everything\nis fine and I can see `consul.server`, `consul.version`, `consul.datacenter`,\netc. show up on the node. But as soon as I point the same Nomad client at one\nof the funkier Consul setups, the whole client process goes down — not just the\nConsul fingerprint, the entire client. That seems wrong: even if Consul info is\npartially missing or shaped slightly differently than expected, I'd expect Nomad\nto log something and move on, not crash.\n\nA few things I'd like out of the fingerprinter:\n\n- It should be defensive about whatever the Consul agent hands back. If a\n particular piece of info isn't there (or isn't the shape Nomad expected), the\n fingerprinter should skip just that piece rather than take the client down.\n- I'd still like *some* signal in the Nomad logs when this happens, so I can\n tell which Consul environments are returning incomplete data — silent skipping\n would make this very hard to debug.\n- Whatever info *is* available should still be recorded on the node, so the\n client is at least partially usable against a Consul agent that doesn't\n expose everything.\n\nHappy to test a fix against the Consul setups where I'm currently seeing the\ncrash."} -{"task_id": "format-code-task-001446", "source_id": "format-code-task-001446", "domain": "code", "task_path": "tasks/format-code-task-001446", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a37d844f899cfb2ea51a3288b67a62d43a2a026fcd169bd392181ca4f983c4a6", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nACL CLI does not validate policy rules when creating a new policy\n### Nomad version\nNomad v0.7.0-dev \n\n### Issue\nA policy of the following syntax: \n\n```\n{ \n \"Name\": \"my-policy\", \n \"Description\": \"This is a great policy\", \n \"Rules\": \"anything\" \n} \n```\nCan be successfully created via the `nomad acl policy apply` command."} {"task_id": "format-code-task-001447", "source_id": "format-code-task-001447", "domain": "code", "task_path": "tasks/format-code-task-001447", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:7dcb4867390a3ec65e23ccd410e7077bf69d6e1cb046a2ae8055372ae349dc03", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Problem Statement\n\n我的 job 里加了个 poststop task 做清理,结果 deploy 一直卡在 running,最后超时变成 unhealthy / failed。但主 task 早就起来了,Consul health check 也是好的。\n\n感觉是那个 poststop task 一直 pending 把整个 deployment 拖住了?它本来就要等主 task 退出才会跑啊,这样我永远没法 deploy 成功。\n\n是我哪里配错了吗,还是说带 poststop 的 job 就没法正常 promote?\n\n## Expected outcomes\n\n- Deployment health with poststop cleanup tasks:\n - A deployment/allocation that includes a `poststop` lifecycle task should be able to become healthy once the normal workload tasks are running and their health checks are passing.\n - A `poststop` lifecycle task that is still pending because the main workload has not exited yet must not by itself keep the deployment in running/pending health until it times out as unhealthy or failed.\n\n- Health semantics for other task outcomes:\n - A task failure should still make the allocation unhealthy.\n - A non-`poststop` task that has already finished when it is expected to participate in allocation health should still make the allocation unhealthy; the poststop cleanup case should not accidentally exempt other lifecycle or normal tasks from health evaluation.\n - A normal or otherwise health-participating task that has not started yet should still prevent the allocation from being reported healthy.\n\n## Implementation notes\n\n- Preserve the existing deployment and allocation health semantics except for the special lifecycle behavior described above.\n- The exact internal data structures, helper boundaries, and validation location are up to the implementation, as long as externally observable deployment/allocation health behavior matches the expected outcomes."} {"task_id": "format-code-task-001448", "source_id": "format-code-task-001448", "domain": "code", "task_path": "tasks/format-code-task-001448", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:bfedc4acc60f8555c95f67501b8e94fc095184075582849d6cbfa03f7b8b3d46", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want Nomad's job-file commands to accept Nomad API JSON job specifications with a `-json` flag. The supported invocations should be `nomad job run -json `, `nomad job plan -json `, and `nomad job validate -json `; the existing `nomad run`, `nomad plan`, and `nomad validate` aliases should accept the same flag.\n\nWhen the flag is present, the command should decode the input as JSON instead of HCL2. It should accept both a bare JSON job object and an object with a top-level `Job` field, such as output from `nomad job inspect -json` or `nomad job run -output`. For example, `nomad job run -json -output ./job.json` where `job.json` contains `{ \"Job\": { \"ID\": \"example\", \"Name\": \"example\", \"Type\": \"service\", \"Datacenters\": [\"dc1\"], \"TaskGroups\": [] } }` should exit 0 and write the decoded API job JSON to stdout, including the `ID`, `Name`, `Type`, `Datacenters`, and `TaskGroups` from the nested `Job` value. The same file without the outer `Job` wrapper should decode to the same job.\n\nFor `nomad job run -json ` submissions, the job submission metadata should preserve the exact JSON source and mark the submission format as `json`, so later source inspection can distinguish JSON submissions from HCL2 submissions. `nomad job validate -json ` should validate the decoded API job, and `nomad job plan -json ` should plan the decoded API job.\n\nInvalid JSON should fail before any HCL2 parsing is attempted: `nomad job validate -json bad.json` should exit 1 and print an error containing `Error getting job struct: Failed to parse JSON job`, while `nomad job plan -json bad.json` should exit 255 with the same parse-error text. Because HCL variables are not meaningful for API JSON input, combining `-json` with `-var` or `-var-file` should fail before parsing; `job run` and `job validate` should exit 1, `job plan` should exit 255, and stderr should include `Invalid job options: cannot use variables with JSON files.` The help output for `nomad job run -help`, `nomad job plan -help`, and `nomad job validate -help` should list `-json` and explain that it parses the job file as JSON and uses a top-level `Job` value when present."} {"task_id": "format-code-task-001449", "source_id": "format-code-task-001449", "domain": "code", "task_path": "tasks/format-code-task-001449", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:e835172459bb2c46d0c5d2e81ab2b74ca15499881bf1216ef277951822525d1d", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Support Managed Identity auth for the azure-arm builder\n\nI'd like to run Packer with the `azure-arm` builder from inside an Azure VM that has a system-assigned managed identity, and have Packer use that identity to talk to Azure — without me having to hand it a service principal.\n\n### What I'm trying to do\n\nI provisioned a small Azure VM to run my Packer builds on. The VM has managed identity enabled and the identity has been granted the right roles on my subscription. Tools like `az` already pick this up automatically on that VM — I never have to put credentials in any config.\n\nI'd like Packer to do the same thing. My intent is to leave `client_id`, `client_secret` (and ideally `subscription_id`) out of my packer template entirely, since the VM Packer is running on already has an identity that can do the work. That way I don't have to create a separate service principal just for Packer, and I don't have to ship a `client_secret` around in my templates / repos.\n\n### What actually happens\n\nIf I drop those fields from the azure-arm builder config, the build never even starts — config validation rejects the template up front because `client_id`, `client_secret` and `subscription_id` are treated as unconditionally required.\n\nSo today there's basically no way to use the azure-arm builder without supplying a full service-principal-style credential set, even when Packer is running somewhere that already has an Azure identity attached to it.\n\n### What I'd like\n\nWhen Packer is running on an Azure VM that has a managed identity, the azure-arm builder should be able to use that identity to authenticate to Azure ARM instead of requiring a service principal in the template. Concretely, it should be possible to leave the SPN-style fields out of the builder config and have the build still run (using the host VM's identity), the same way the device-login path today doesn't require `client_id`/`client_secret`.\n\nThis would make Packer much nicer to use as part of an Azure-native CI/CD setup."} @@ -1299,7 +1254,6 @@ {"task_id": "format-code-task-001463", "source_id": "format-code-task-001463", "domain": "code", "task_path": "tasks/format-code-task-001463", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:b4a6ee11c9b8587ffdda29e65a8e86f6ab7b641ebb5416f9e9a65719385b72c9", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Device removal aborts when a brick on the device has no path, leaving the device stuck\n\nI'm trying to decommission a disk from one of my nodes using the normal flow — set the device offline and then transition it to the failed state so heketi will move the bricks off it automatically.\n\nOn most devices this works fine. But I have one device where the operation stops partway through with an error, and after that:\n\n- the device is still in the offline state (it didn't transition to failed),\n- only some of the bricks on it got migrated; the rest are still associated with the device,\n- so I can't actually retire the disk.\n\nWhen I look at the device info via the API, I notice that a few of the bricks on this device have an empty `path` field. As far as I can tell these are leftovers from an earlier operation that didn't complete cleanly — the brick entries exist in heketi's DB but there's nothing real backing them on the host (no LV, nothing under `/var/lib/heketi/mounts/...`). The bricks that do have a proper path migrate just fine; it's the empty-path ones that seem to trip up the whole remove.\n\nThe only way I've found to get unstuck is to manually edit the heketi DB to drop those phantom brick entries and then re-run the remove, which is not something I want to be doing on a production cluster.\n\nIt would be much better if `Remove` on a device just skipped bricks that obviously can't be migrated (no path = nothing to move anyway) and kept going with the rest, so the device can actually reach the failed state. A warning in the log naming which brick got skipped would be enough for me to follow up on the stale entries afterwards."} {"task_id": "format-code-task-001464", "source_id": "format-code-task-001464", "domain": "code", "task_path": "tasks/format-code-task-001464", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:bdc4237a7e20ee9eb10491df7778b911abc058a77ed4cf3c6c27425d3f94577c", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want a pure `pairAnchorsAndFootnotes(timeline: Array) -> Object` utility that turns a chronological stream of inline footnote events into a lookup table keyed by marker code and anchor index. The input timeline contains events with `type: \"anchor\"` or `type: \"footnote\"`; anchor events include `markerCode` and `index`, and footnote events include `markerCode` and `content`.\n\nFor example, calling `pairAnchorsAndFootnotes([{type:\"anchor\", markerCode:\"9312\", index:0}, {type:\"footnote\", markerCode:\"9312\", content:\"first note\"}])` should return an object where `result[\"9312\"][0] === \"first note\"`. If repeated markers appear, pairing should follow reading order: `[{type:\"anchor\", markerCode:\"9312\", index:0}, {type:\"anchor\", markerCode:\"9312\", index:1}, {type:\"footnote\", markerCode:\"9312\", content:\"first\"}, {type:\"footnote\", markerCode:\"9312\", content:\"second\"}]` should produce `result[\"9312\"][0] === \"first\"` and `result[\"9312\"][1] === \"second\"`.\n\nIf an anchor cannot be matched to a later footnote before the group changes or before the timeline ends, its lookup entry should be the configured not-found footnote placeholder. Footnote events with no queued matching anchor can be ignored. Passing a non-array input should return an empty object. The function must be deterministic, must not mutate the input timeline, and must not read or write the filesystem, network, DOM, or hidden global state beyond using the configured footnote constants."} {"task_id": "format-code-task-001465", "source_id": "format-code-task-001465", "domain": "code", "task_path": "tasks/format-code-task-001465", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:a6a28751343a581a802ded93ca900312c3be06553ef7f971c9925b08052702c1", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Per-location traffic pricing isn't exposed on `ServerType` / `LoadBalancerType`\n\nHetzner announced that the traffic pricing model is changing on **2024-08-05**: included traffic and traffic overage prices are no longer global, they're per server type / load balancer type and per location. The pricing API has already been updated to return this — each entry under `server_types[].prices[]` and `load_balancer_types[].prices[]` now includes:\n\n```json\n{\n \"location\": \"fsn1\",\n \"price_hourly\": { ... },\n \"price_monthly\": { ... },\n \"included_traffic\": 21990232555520,\n \"price_per_tb_traffic\": { \"net\": \"...\", \"gross\": \"...\" }\n}\n```\n\nThe problem is that `hcloud-go` silently drops these two fields. If I do something like:\n\n```go\npricing, _, _ := client.Pricing.Get(ctx)\nfor _, st := range pricing.ServerTypes {\n for _, p := range st.Pricings {\n fmt.Println(p.Location.Name, p.Hourly, p.Monthly)\n // no way to see included traffic or per-TB overage here\n }\n}\n```\n\n…there's nowhere on `ServerTypeLocationPricing` (or `LoadBalancerTypeLocationPricing`) to read the per-location included traffic or the per-TB traffic price. The same goes for the schema struct used for JSON decoding — it doesn't carry those fields, so even if I unmarshalled the response myself through the schema package I'd lose them.\n\nAfter 2024-08-05 the existing top-level `Pricing.Traffic.PerTB` and `ServerType.IncludedTraffic` will start reporting 0, so anyone relying on those values today will silently get wrong pricing data unless the SDK exposes the new per-location fields and clearly signals that the old ones are going away.\n\nIt would be great if `hcloud-go` could:\n\n1. Surface the new per-location included traffic + per-TB traffic price coming from the API so callers can actually use the new pricing model, and\n2. Make it obvious (via the type system / godoc) that the old global traffic fields are on their way out, so users can migrate before they start returning zeros.\n\nThe fields I'd expect on the location-pricing structs are something like `IncludedTraffic` and `PerTBTraffic`."} -{"task_id": "format-code-task-001466", "source_id": "format-code-task-001466", "domain": "code", "task_path": "tasks/format-code-task-001466", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:79ac1bdac0d80064e305cb6ef77118ca80badd22df7dc03fe972130d78da7f05", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\nI want autogold to support raw text snapshots for golden-file assertions. The public API should include `type Raw string`, and when I call `autogold.ExpectFile(t, autogold.Raw(contents))`, autogold should compare and update the `.golden` file using `contents` exactly as provided instead of formatting it as a Go literal.\n\nFor example, `autogold.ExpectFile(t, autogold.Raw(\"{\\\"ok\\\":true}\\n\"))` should expect the golden file to contain `{\"ok\":true}\\n` directly, with no surrounding quotes, escaping, Go type wrapper, or automatically added newline. Likewise, `autogold.ExpectFile(t, autogold.Raw(\"line 1\\nline 2\"))` should use exactly those two raw lines as the snapshot text. When cleanup mode is active, an empty raw snapshot such as `autogold.ExpectFile(t, autogold.Raw(\"\"))` should remove the corresponding `.golden` file rather than preserving an empty file."} {"task_id": "format-code-task-001467", "source_id": "format-code-task-001467", "domain": "code", "task_path": "tasks/format-code-task-001467", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:8dd7478030f8cc8c236f7a30e155c9d85cf19ab8e5b8c588cd999da14cb3cc86", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Problem Statement\n\nI’m building a Dashboard with the built-in HTML component and I already have the content as an HTML string. Right now it feels like I have to turn that into the elements structure or make a custom component just to render it. Could the HTML component accept a plain HTML string directly so I can drop in markup like a heading without that extra conversion?\n\n# Expected outcomes\n\n- Built-in Dashboard HTML components configured with `type: 'HTML'` should accept an `html` property whose value is a plain HTML string.\n- When an HTML component is configured with `html`, the component should render the corresponding markup into its dashboard cell, including ordinary element structure, text, and attributes from the string.\n- Existing HTML component configurations that use the `elements` array should continue to render as before.\n- Dashboard documentation for the built-in HTML component should describe `html` as a supported way to define component content.\n- Dashboard documentation and examples for custom HTML components should no longer imply that a custom component is required just to render an HTML string in a built-in HTML component.\n\n# Implementation notes\n\nThe exact parsing path, data structures, and internal placement of the conversion logic are left to the implementer. Preserve the existing public Dashboard configuration style and compatibility with current HTML component usage while adding support for the new string-based content option."} {"task_id": "format-code-task-001468", "source_id": "format-code-task-001468", "domain": "code", "task_path": "tasks/format-code-task-001468", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:36e12b1c4544823fb4afbe928e5bc31d73dbae6c30d458d34d1a9bf87da3c38b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n## Common shell commands aren't highlighted as built-ins in `bash`\n\nI'm using highlight.js on my docs site to render shell snippets, and the most-used commands look completely unstyled while rare shell internals show up colored. Take a typical snippet:\n\n```bash\nmkdir -p /tmp/build\ncp src/* /tmp/build/\nls -la /tmp/build\nchmod +x /tmp/build/run.sh\nmv /tmp/build/output.log /var/log/\ncat /var/log/syslog | head -n 50 | sort | wc -l\necho \"done\"\n```\n\nWhen this is rendered as `language-bash`, `echo` (and things like `printf`, `pwd`, `set`) get the built-in styling, but `mkdir`, `cp`, `ls`, `chmod`, `mv`, `cat`, `head`, `sort`, `wc` are all rendered as plain text — same color as filenames and arguments. The visual outcome is that the everyday GNU core utilities — which is basically what people actually write in shell scripts 99% of the time — look unrecognized, while the obscure shell-internal stuff stands out. Side-by-side it looks really inconsistent.\n\nIt would be great if the standard GNU core utilities were treated as built-ins by the bash grammar too, so a normal shell snippet looks uniformly highlighted."} {"task_id": "format-code-task-001469", "source_id": "format-code-task-001469", "domain": "code", "task_path": "tasks/format-code-task-001469", "docker_image": "docker.io/xiaomimimo/mimo-v2.6-rl-oss@sha256:0322b6efb0b596a9bbf261fe9ab06523837aa84e674e944c4508e8e5ff7d960b", "step_limit": 500, "agent_timeout_sec": 3600.0, "verifier_timeout_sec": 2100.0, "instruction": "Fix the following issue:\n\n# Flatten the message action-row component builders\n\nBuilding a message action row today is clumsy: to add a button or select menu you\nget back a *separate* sub-builder and then have to remember to call a finalising\nmethod on it to actually attach the component to the row. This breaks call chaining\nand is easy to get wrong.\n\nMake the message action-row builder able to add components **directly**, in a single\ncall, returning the row itself so calls can be chained. The standard\n`MessageActionRowBuilder` implementation (the one exported from the public builder\nimplementation module) should grow the following methods.\n\n## Buttons\n\n- `add_interactive_button(style, custom_id, /, *, emoji=UNDEFINED, label=UNDEFINED, is_disabled=False)`\n appends an interactive (non-link) button and returns the action row.\n- `add_link_button(url, /, *, emoji=UNDEFINED, label=UNDEFINED, is_disabled=False)`\n appends a link-style button and returns the action row.\n\n`emoji` accepts a custom-emoji object/ID or a unicode emoji/string; `label` is the\nbutton's text; `is_disabled` marks it disabled.\n\n## Select menus\n\n- `add_select_menu(type_, custom_id, /, *, placeholder=UNDEFINED, min_values=0, max_values=1, is_disabled=False)`\n appends a select menu of the given type and returns the action row. This is the\n method for the user / role / mentionable select-menu types; channel and text\n select menus have their own dedicated methods (below). Passing a value that is not\n a valid select-menu component type must raise `ValueError`.\n- `add_channel_menu(custom_id, /, *, channel_types=(), placeholder=UNDEFINED, min_values=0, max_values=1, is_disabled=False)`\n appends a channel select menu and returns the action row. `channel_types`\n restricts which channel types may be picked (empty means no restriction).\n- `add_text_menu(custom_id, /, *, placeholder=UNDEFINED, min_values=0, max_values=1, is_disabled=False)`\n appends a text select menu and, because such a menu needs its options filled in,\n returns the *text-select-menu builder* (not the row).\n\nThe returned text-select-menu builder must expose:\n\n- a `parent` property that returns the action row the menu was added to, so callers\n can hop back and continue building the row; and\n- `add_option(label, value, /, *, description=UNDEFINED, emoji=UNDEFINED, is_default=False)`\n which appends an option to that menu and returns the menu builder (so options can\n be chained). `emoji` follows the same custom/unicode handling as buttons.\n\nThe menu must already be attached to the row as soon as `add_text_menu` returns\n(before any options are added).\n\n## Single component type per row\n\nAn action row may only hold one kind of component. Adding a component whose type\ndiffers from what the row already contains must raise `ValueError`.\n\n## Serialized output\n\nWhen the action row is built, each added component must appear inside the row's\n`\"components\"` list serialized to the Discord payload shape:\n\n- Buttons → `{\"type\": 2, \"style\":