re-judge 4 ERROR rows

judge/review_200.jsonl

@@ -67,7 +67,7 @@
 {"id": 1452, "text": "DNN: need support of the GreaterOrEqual operator from ONNX\n\n### Descripe the feature and motivation\n\nThere is a contributor trying to contribute a model to opencv zoo. Link to the pull request: https://github.com/opencv/opencv_zoo/pull/82. And this model requires the support of GreaterOrEqual operator from ONNX.\n\n### Additional context\n\nThere might be other operators that are not supported in the current version of OpenCV. Need to generate a list of operators to check whether there are other unsupported operators.", "maintainer_label": "feature", "repo": "opencv/opencv", "judge_label": "feature", "judge_confidence": 0.97, "judge_rationale": "User asks for addition of GreaterOrEqual ONNX operator support, a request for new functionality."}
 {"id": 130, "text": "React.lazy does not allow retrying a rejected promise\n\n**Do you want to request a *feature* or report a *bug*?**\n\nIt can be seen as a feature or a bug, depending on angle. Let's say it's an enhancement to how `lazy` works.\n\n**What is the current behavior?**\n\nWhen using `React.lazy`, if the given promise rejects while trying to asynchronously load a component, it's no longer possible to retry loading the component chunk because `lazy` internally caches the promise rejection.\n\n**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:**\n\nThis does not seem to work great in CodeSandbox because it's using service workers, which get in the way when simulating offline mode, yet this small app illustrates the issue: https://codesandbox.io/s/v8921j642l\n\n**What is the expected behavior?**\n\nA promise rejection should not be cached by `lazy` and another attempt to render the component should call the function again, giving it the chance to return a new promise.\n\n**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**\n\nAFAIK all version of React that include `lazy`.", "maintainer_label": "feature", "repo": "facebook/react", "judge_label": "feature", "judge_confidence": 0.93, "judge_rationale": "User requests change to React.lazy behavior (no retry on rejection), not reporting incorrect operation; they seek new capability, fitting a feature request."}
 {"id": 437, "text": "TF Lite enable Flex delegate C++ API (with CMake of Bazel)\n\n**System information**\n- Linux Ubuntu 18.04):\n- TensorFlow installed from source:\n- TensorFlow version commit 47e07ba0d68c55dba62bff5b8486291086840097:\n\nHi, I want to run simple conv2d layer training using C++ API of TF Lite. I\u2019ve used examples/minimal project as reference. Calling trainer->invoke() leads to next error:\n\n`ERROR: TensorFlow Lite Error: Select TensorFlow op(s), included in the given model is(are) not supported by this interpreter. Make sure you apply/link Flex delegate before inference. For the Android, it can be resolved by adding \u201corg.tensorflow:tensorflow-lite-select-tf-ops\u201d dependency\u2026`\n`ERROR: Node number 48 (FlexConv2DBackpropFilter) failed to prepare.`\n\nI didn\u2019t find any good tutorial on Flex delegate. Please, tell me, how to build TF Lite with Flex using CMake and how to make this interpreter use Flex\u2019s implementation of this node. Thanks", "maintainer_label": "feature", "repo": "tensorflow/tensorflow", "judge_label": "support", "judge_confidence": 0.98, "judge_rationale": "User asks how to build TF Lite with Flex delegate and use it, requiring guidance/configuration help, not reporting a defect."}
-{"id": 1487, "text": "Error while loading yolor_p6.onnx: expand op doesn't support multiple axes for constant input\n\nI'm trying to load yolor after i converted it from pytorch to onnx. buti get this error:\n\nNode [Expand@ai.onnx]:(815) parse error: OpenCV(4.5.5) /io/opencv/modules/dnn/src/onnx/onnx_importer.cpp:2389: error: (-213:The function/feature is not implemented) Expand op doesn't support multiple axes for constant input in function 'parseExpand'\n\nmy code :\n`import cv2`\n`onnx_model = cv2.dnn.readNetFromONNX('yolor_p6.onnx')`", "maintainer_label": "feature", "repo": "opencv/opencv", "judge_label": "ERROR", "judge_confidence": 0.0, "judge_rationale": "Expecting value: line 1 column 1 (char 0)"}
+{"id": 1487, "text": "Error while loading yolor_p6.onnx: expand op doesn't support multiple axes for constant input\n\nI'm trying to load yolor after i converted it from pytorch to onnx. buti get this error:\n\nNode [Expand@ai.onnx]:(815) parse error: OpenCV(4.5.5) /io/opencv/modules/dnn/src/onnx/onnx_importer.cpp:2389: error: (-213:The function/feature is not implemented) Expand op doesn't support multiple axes for constant input in function 'parseExpand'\n\nmy code :\n`import cv2`\n`onnx_model = cv2.dnn.readNetFromONNX('yolor_p6.onnx')`", "maintainer_label": "feature", "repo": "opencv/opencv", "judge_label": "bug", "judge_confidence": 0.9, "judge_rationale": "Correct usage crashes due to unimplemented Expand op handling in OpenCV's ONNX importer, indicating a library defect."}
 {"id": 766, "text": "Pick up TS 5.1.6\n\nTrack picking up https://github.com/microsoft/typescript/issues?q=is%3Aissue+milestone%3A%22TypeScript+5.1.6%22+is%3Aclosed", "maintainer_label": "feature", "repo": "microsoft/vscode", "judge_label": "feature", "judge_confidence": 0.85, "judge_rationale": "User asks to upgrade the project to TypeScript 5.1.6, a request for new version support rather than bug or question."}
 {"id": 789, "text": "Peek Call/Type Hierarchy not in command palette\n\nTesting #186213\n\n<img width=\"497\" alt=\"image\" src=\"https://github.com/microsoft/vscode/assets/323878/ba07c303-4a1a-460f-9da5-d582c3b43d85\">\n\n<img width=\"667\" alt=\"image\" src=\"https://github.com/microsoft/vscode/assets/323878/436aab1c-305a-4b2d-aab2-a32c9d9f6d6b\">", "maintainer_label": "feature", "repo": "microsoft/vscode", "judge_label": "bug", "judge_confidence": 0.96, "judge_rationale": "User reports an expected command is absent from the command palette, indicating incorrect behavior of the existing feature."}
 {"id": 1491, "text": "Add resize layer compatible with ONNX opset13 version\n\n**Merge with extra**: https://github.com/opencv/opencv_extra/pull/954\n\nOpset13 has changed resize layer mapping. \nAnd there may the empty input in the resize node.\nHappened when exporting the ONNX model with the 1.9 or later version of pytorch with opset 13, for example the \"Resize\" in [ AnimeGANv2 model](https://github.com/Kazuhito00/AnimeGANv2-ONNX-Sample/tree/main/model).\nMore details can be found in the [Test data](https://github.com/opencv/opencv_extra/pull/954).\n\n### Pull Request Readiness Checklist\n\nSee details at https://github.com/opencv/opencv/wiki/How_to_contribute#making-a-good-pull-request\n\n- [x] I agree to contribute to the project under Apache 2 License.\n- [x] To the best of my knowledge, the proposed patch is not based on a code under GPL or another license that is incompatible with OpenCV\n- [x] The PR is proposed to the proper branch\n- [ ] There is a reference to the original bug report and related work\n- [ ] There is accuracy test, performance test and test data in opencv_extra repository, if applicable\n Patch to opencv_extra has the same branch name.\n- [ ] The feature is well documented and sample code can be built with the project CMake\n\n```\nopencv_extra=resize_onnx_opset13\n```", "maintainer_label": "feature", "repo": "opencv/opencv", "judge_label": "feature", "judge_confidence": 0.97, "judge_rationale": "User requests adding a new resize layer to support ONNX opset13, which is a request for new functionality."}
@@ -93,7 +93,7 @@
 {"id": 133, "text": "More helpful interaction for \"React does not recognize the 'propName' prop on a DOM Element\"\n\n**Do you want to request a *feature* or report a *bug*?**\n\nFeature\n\n**What is the current behavior?**\n\nWhen you pass a unknown prop to a DOM element - common when you pass `{...props}` to something that turns out to be a div/span/any other DOM element rather than a composite component - you get a warning like so:\n\n```Warning: React does not recognize the `propName` prop on a DOM element. ....```\n\nIf the tree is pretty complicated, especially if you're using HOCs, it can be very hard to find where this prop has been passed and to which DOM element. \n\n**What is the expected behavior?**\n\nWe had a quick muck around with react-dom and logging the DOM element that triggers this warning allows you to see the element in the DOM and makes it much easier to work out where the prop is being accidentally passed. You can even use the react dev tools to work out exactly which line the component is defined in the code.\n\nSimply logging the element is obviously not the most elegant way of showing the user where the mistake is, but would it be possible to do _something_ in order to make it quicker to fix mistaken prop passing like this?\n\n**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**\n\nAll.", "maintainer_label": "feature", "repo": "facebook/react", "judge_label": "feature", "judge_confidence": 0.97, "judge_rationale": "User requests enhanced warning behavior to aid debugging, a new capability rather than reporting incorrect behavior."}
 {"id": 916, "text": "Keep seed phrase/mnemonic on cold encrypted\n\n**Is your feature request related to a problem? Please describe.**\n<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->\nIt is not safe to keep the seed phrase or private keys on the computer or smartphones. \n\n**Describe the solution you'd like**\n<!-- A clear and concise description of what you want to happen. -->\nNeed to have an option to user save the seed phrase or private keys encripted on NFC Card or USB device, like a cold wallet integrated with Bitcoin core.\n\nSo every time user wants to withdraw Bitcoin, need to have the USB \"pendrive\" connected on PC or tap the NFC Card.\n\n**Describe alternatives you've considered**\n<!-- A clear and concise description of any alternative solutions or features you've considered. -->\nI have checked and there is another wallets using this solution.\n\n**Additional context**\n<!-- Add any other context or screenshots about the feature request here. -->\nI already have this working without integration with Bitcoin Core.", "maintainer_label": "feature", "repo": "bitcoin/bitcoin", "judge_label": "feature", "judge_confidence": 0.97, "judge_rationale": "User requests new capability to store seed phrase on encrypted NFC/USB, which is a feature enhancement."}
 {"id": 100, "text": "[DevTools] Manifest version 2 is deprecated\n\n### Website or app\n\nhttps://developer.chrome.com/blog/mv2-transition/\n\n### Repro steps\n\nUse latest React DevTools with Electron (Chromium) (18.2.0 / Chromium 100)\n\n```\n (node:80082) ExtensionLoadWarning: Warnings loading extension at ./node_modules/electron-devtools-vendor/extensions/react-developer-tools:\n Manifest version 2 is deprecated, and support will be removed in 2023. See https://developer.chrome.com/blog/mv2-transition/ for more details.\n```\n\n### How often does this bug happen?\n\nEvery time\n\n### DevTools package (automated)\n\n_No response_\n\n### DevTools version (automated)\n\n_No response_\n\n### Error message (automated)\n\n_No response_\n\n### Error call stack (automated)\n\n_No response_\n\n### Error component stack (automated)\n\n_No response_\n\n### GitHub query string (automated)\n\n_No response_", "maintainer_label": "feature", "repo": "facebook/react", "judge_label": "support", "judge_confidence": 0.92, "judge_rationale": "User reports a deprecation warning and seeks guidance; behavior is expected, not a defect in the library."}
-{"id": 111, "text": "Devtools: Impossible to debug firefox webextension moz-extension: pages due to strict CSP\n\n<!--\n Note: if the issue is about documentation or the website, please file it at:\n https://github.com/reactjs/reactjs.org/issues/new\n-->\n\n**Do you want to request a *feature* or report a *bug*?**\n\n* feature request\n* Original issue is: https://github.com/facebook/react-devtools/issues/922\n * There are more details.\n* Mozilla's Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1573027\n\n**What is the current behavior?**\n\nThe react-devtools toolbar button does not light up and clicking on it says \"This page does not appear to be using react\". This is probably since extensions are not allowed to inject scripts into other extensions' pages.\n\n**What is the expected behavior?**\n\nThe react-devtools toolbar button should light up and the addon should be able to debug the page\n\n**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**\n\nThis is still reproducible\n\n* Firefox v68~\n* react devtools v4.0.5\n* react v16.9", "maintainer_label": "feature", "repo": "facebook/react", "judge_label": "ERROR", "judge_confidence": 0.0, "judge_rationale": "Expecting value: line 1 column 1 (char 0)"}
+{"id": 111, "text": "Devtools: Impossible to debug firefox webextension moz-extension: pages due to strict CSP\n\n<!--\n Note: if the issue is about documentation or the website, please file it at:\n https://github.com/reactjs/reactjs.org/issues/new\n-->\n\n**Do you want to request a *feature* or report a *bug*?**\n\n* feature request\n* Original issue is: https://github.com/facebook/react-devtools/issues/922\n * There are more details.\n* Mozilla's Bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1573027\n\n**What is the current behavior?**\n\nThe react-devtools toolbar button does not light up and clicking on it says \"This page does not appear to be using react\". This is probably since extensions are not allowed to inject scripts into other extensions' pages.\n\n**What is the expected behavior?**\n\nThe react-devtools toolbar button should light up and the addon should be able to debug the page\n\n**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**\n\nThis is still reproducible\n\n* Firefox v68~\n* react devtools v4.0.5\n* react v16.9", "maintainer_label": "feature", "repo": "facebook/react", "judge_label": "bug", "judge_confidence": 0.97, "judge_rationale": "User reports devtools failing to work due to CSP, a defect in the tool's ability to debug extensions, needing code change."}
 {"id": 933, "text": "doc: add a brief description to each namespace\n\n**Is your feature request related to a problem? Please describe.**\n\nMany namespaces are as yet un-annotated with a brief description, as used by Doxygen to generate developer documentation, locally or at https://doxygen.bitcoincore.org/namespaces.html.\n\n<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->\n\nIncomplete developer documentation may affect developer onboarding time, and this seems like low-hanging fruit.\n\n**Describe the solution you'd like**\n<!-- A clear and concise description of what you want to happen. -->\n\nTo add annotations to each of these namespaces. There may be existing descriptions elsewhere, if not I or someone else could attempt to describe each namespace, and reviewers could suggest improvements or alternatives.\n\n**Describe alternatives you've considered**\n<!-- A clear and concise description of any alternative solutions or features you've considered. -->\n\nIdeally each description would be committed by its author, so perhaps handling this with one PR that is then squashed isn't the best solution.\n\nOn the other hand, if this would ease developer onboarding perhaps that's more important.\n\n**Additional context**\n\nDocumentation at time of opening 14/12/2022:\n\n![doxygen-namespaces-20211214](https://user-images.githubusercontent.com/97605837/149532363-fc8e7c16-a253-417b-92bd-5a3b8419a2af.png)", "maintainer_label": "feature", "repo": "bitcoin/bitcoin", "judge_label": "feature", "judge_confidence": 0.99, "judge_rationale": "User requests adding namespace descriptions to documentation, an enhancement to improve developer onboarding, not a defect or support query."}
 {"id": 473, "text": "Adding Select Tf Ops to Cmake\n\n**System information**\n- TensorFlow version (you are using): any\n- Are you willing to contribute it (Yes/No): no\n\n**Describe the feature and the current behavior/state.** \nCurrently one has to decide between using Select TF ops with bazel or GPU support with CMake.\nIt would be nice if either bazel has an option to support GPU on any OpenCL system or CMake can build with TF Ops.\n\n**Will this change the current api? How?**\nNo\n\n**Who will benefit with this feature?**\nEverybody who wants to use GPU acceleration and TF Ops.", "maintainer_label": "feature", "repo": "tensorflow/tensorflow", "judge_label": "feature", "judge_confidence": 0.98, "judge_rationale": "User requests new capability: CMake support for Select TF ops / GPU on OpenCL, which is an enhancement, not a bug or support question."}
 {"id": 184, "text": "Feature Request: Support auxclick event (onAuxClick)\n\nVersion 15.4.1\n\nAs starting Chrome 55, there is a new event `auxclick` to handle middle click, and `click` doesn't trigger by middle click anymore\nhttps://developers.google.com/web/updates/2016/10/auxclick", "maintainer_label": "feature", "repo": "facebook/react", "judge_label": "feature", "judge_confidence": 0.99, "judge_rationale": "User requests adding support for the auxclick event, a new capability, indicating a feature request."}
@@ -129,7 +129,7 @@
 {"id": 277, "text": "Limitations of React.createContext\n\n**Do you want to request a *feature* or report a *bug*?**\n\nfeature\n\n**What is the current behavior?**\n\nThe current behavior requires end users to use `createContext` in the module scope. To my understanding, it's not currently possible to use a default value derived from the state of a component (a stateful Provider in my case).\n\nThis [StackOverflow post](https://stackoverflow.com/questions/51448291/how-to-create-a-generic-react-component-with-a-typed-context-provider) hits the issue right on IMO.\n\nI feel like this is the classic use case for replacing Redux, and it doesn't work out of the box with static types.\n\nI think it's quite telling that `react-redux` is doing something similar [here](https://github.com/reduxjs/react-redux/pull/995/files#diff-0d7275a0771455b7118505dedef42772R3) in their PR to move to React 16 context. I would expect the default value to be `this.state` of the Provider component instead of `null`.\n\nMy knowledge of React internals is naive, but I didn't see anyone else bringing up this issue.\n\n**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:**\n\n**What is the desired behavior?**\n\nMaybe a JSX API for context creation? I imagine it's not quite that simple.\n\n**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**\n\n16.3+", "maintainer_label": "question", "repo": "facebook/react", "judge_label": "feature", "judge_confidence": 0.99, "judge_rationale": "User requests new capability: allowing default context value derived from a Provider's state, which is not currently supported."}
 {"id": 268, "text": "react-cache alphas don't work with 16.8+\n\n> `react-cache` was not published with 16.8.1 like the rest of the react packages.\nThis means that the platform's Suspense stuff will not work.\n\n_Originally posted by @jaredpalmer in https://github.com/palmerhq/the-platform/pull/70#issuecomment-461170282_", "maintainer_label": "question", "repo": "facebook/react", "judge_label": "bug", "judge_confidence": 0.95, "judge_rationale": "User reports missing react-cache release for 16.8+, breaking Suspense features\u2014a defect in the library distribution."}
 {"id": 1340, "text": "Import module error !!!\n\nI am using Anaconda to install opencv. \nAfter success of installation in the Anaconda I go to the jupyter notebook in venv created in the Anaconda.\nIn the Anaconda terminal the importing is successful but in the jupyter notebook it is not successful. \nPlease se the image attached for more information.\n![image](https://user-images.githubusercontent.com/40560482/196770745-639a6589-2313-4f72-ac1c-9028e0694ba6.png)", "maintainer_label": "question", "repo": "opencv/opencv", "judge_label": "support", "judge_confidence": 0.96, "judge_rationale": "User cannot import OpenCV in Jupyter despite successful install; likely due to environment/path configuration, requiring guidance rather than a library defect."}
-{"id": 276, "text": "SetStateAction returned from useState hook dose not accept a second callback argument\n\n<!--\n Note: if the issue is about documentation or the website, please file it at:\n https://github.com/reactjs/reactjs.org/issues/new\n-->\n\n**Do you want to request a *feature* or report a *bug*?**\nQuestion\n\n**What is the current behavior?**\nThe SetStateAction returned from useState hook dose not accept a second callback argument. It cannot works like Class Componet's 'setState' method, which receives a callback param, and can perform the callback after this setState action updates;\n\n**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:**\nhttps://codesandbox.io/s/93mkr1ywpr\n\n**What is the expected behavior?**\nHopes the SetStateAction function can receive a second callback argument, and can used like 'setState' method callback. \n\nI have read the official note: \n\n> // this technically does accept a second argument, but it's already under a deprecation warning\n> // and it's not even released so probably better to not define it.\n\nIf instead it's working as intended, how can I perform special action after this SetStateAction called ? \n\n**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**\n16.7.0-alpha.0", "maintainer_label": "question", "repo": "facebook/react", "judge_label": "ERROR", "judge_confidence": 0.0, "judge_rationale": "Expecting value: line 1 column 1 (char 0)"}
+{"id": 276, "text": "SetStateAction returned from useState hook dose not accept a second callback argument\n\n<!--\n Note: if the issue is about documentation or the website, please file it at:\n https://github.com/reactjs/reactjs.org/issues/new\n-->\n\n**Do you want to request a *feature* or report a *bug*?**\nQuestion\n\n**What is the current behavior?**\nThe SetStateAction returned from useState hook dose not accept a second callback argument. It cannot works like Class Componet's 'setState' method, which receives a callback param, and can perform the callback after this setState action updates;\n\n**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:**\nhttps://codesandbox.io/s/93mkr1ywpr\n\n**What is the expected behavior?**\nHopes the SetStateAction function can receive a second callback argument, and can used like 'setState' method callback. \n\nI have read the official note: \n\n> // this technically does accept a second argument, but it's already under a deprecation warning\n> // and it's not even released so probably better to not define it.\n\nIf instead it's working as intended, how can I perform special action after this SetStateAction called ? \n\n**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**\n16.7.0-alpha.0", "maintainer_label": "question", "repo": "facebook/react", "judge_label": "question", "judge_confidence": 0.96, "judge_rationale": "User seeks guidance on performing post\u2011state\u2011update actions, not reporting a defect or requesting new functionality."}
 {"id": 340, "text": "How to solve the backpropagation problem of tf.signal.rfft?\n\n<details><summary>Click to expand!</summary> \n \n ### Issue Type\n\nFeature Request\n\n### Have you reproduced the bug with TF nightly?\n\nNo\n\n### Source\n\nsource\n\n### Tensorflow Version\n\ntf 2.11\n\n### Custom Code\n\nYes\n\n### OS Platform and Distribution\n\nWindows 10\n\n### Mobile device\n\n_No response_\n\n### Python version\n\n3.9\n\n### Bazel version\n\n_No response_\n\n### GCC/Compiler version\n\n_No response_\n\n### CUDA/cuDNN version\n\n_No response_\n\n### GPU model and memory\n\n_No response_\n\n### Current Behaviour?\n\n```shell\nI x wanted to implement the Hilbert transform in the model built by tensorflowd, but I found no callable API. so I implemented it myself using tf.signal.rfft and tf.signal.ifft. However, when I was training, I found the following error reported:\nLookupError: gradient registry has no entry for: RFFT3D\nI think it may be that tensorflow has not defined the corresponding backpropagation method for rfft3d yet. I want to provide my code train.py & model.py\n```\n\n### Standalone code to reproduce the issue\n\n```\ndef hilbert_transform(x, N=None, axis=-1):\n if x.dtype == tf.complex64 or x.dtype == tf.complex128:\n raise ValueError(\"x must be real.\")\n if N is None:\n N = x.shape[axis]\n if N <= 0:\n raise ValueError(\"N must be positive.\")\n x_br = tf.signal.rfft3d(x[:, :, :1])\n x_bi = tf.signal.rfft3d(x[:, :, 1:])\n x_complex = concatenate([x_br, x_bi], axis=-1)\n\n h = np.zeros(N)\n if N % 2 == 0:\n h[0] = h[N // 2] = 1\n h[1:N // 2] = 2\n else:\n h[0] = 1\n h[1:(N + 1) // 2] = 2\n if x.shape.ndims > 1:\n ind = [tf.newaxis] * x.shape.ndims\n ind[axis] = slice(None)\n h = h[tuple(ind)]\n x_complex_h = x_complex * h\n x_bj = tf.signal.ifft3d(x_complex_h[:, :, :1])\n x_bk = tf.signal.ifft3d(x_complex_h[:, :, 1:])\n x_hilbert = concatenate([tf.math.imag(x_bj), tf.math.imag(x_bk)], axis=-1)\n return x_hilbert\n```\n\n### Relevant log output\n\n_No response_</details>", "maintainer_label": "question", "repo": "tensorflow/tensorflow", "judge_label": "bug", "judge_confidence": 0.94, "judge_rationale": "TensorFlow lacks a gradient implementation for RFFT3D, causing runtime error; requires library change, not user misconfiguration."}
 {"id": 202, "text": "React 18 : useState 'sharing' state value between components of the same type\n\n<!--\n Ask a question or share feedback about the React 18 release here.\n-->\n\nI created a custom table component that has pagination, search bar and export to excel button. The main usage of the component is as follows:\n\n```jsx\n<ClientsTable\n dataset={sellsInfo}\n Headers={sellsInfoHeaders}\n downloadFileName={`OrdenesCliente-${clientId}`}\n pageSize={2}\n identifier={'id'}\n/> \n```\n\nTo enable pagination, global filter and dataset download, I used state variables using `useState` hook, as follows. \n\n```jsx\nconst ClientsTable = (props) => {\n let { dataset, Headers, pageSize, actions, identifier, downloadFileName } = props;\n \n const [ displayDataset, setDisplayDataset ] = useState(dataset);\n const [ pageIndex, setPageIndex ] = useState(0);\n const numPages = Math.ceil(displayDataset.length / pageSize);\n const [ canNextPage, setCanNextPage ] = useState(true);\n const [ canPrevPage, setCanPrevPage ] = useState(false);\n const [ sortSmallToLarge, setSortSmallToLarge ] = useState(true);\n const [ sortingField, setSortingField ] = useState(null);\n\n // some logic for filtering, pagination and rendering\n}\n```\n\nRendering only one table component in an app view works just fine. However, rendering two or more implies that React uses the same state variables for all table components in the view. This is unintended behavior for me. In particular, I created a custom tab component that renders two different tables on tab selection. The two tables have the same state variables, different pros though, which causes conflicts in the view.\n\nHow can I render multiple table components in my app without having this behavior?\n\nThanks in advance.", "maintainer_label": "question", "repo": "facebook/react", "judge_label": "question", "judge_confidence": 0.98, "judge_rationale": "User asks how to avoid shared state across component instances; seeks guidance, not reporting a defect."}
 {"id": 1030, "text": "IBD stalls permanently with Bitcoin core v23 after \"ignoring getheaders from peer=0 because node is in initial block download\"\n\nWith Bitcoin core v23 (Qt versin on Windows, or with the daemon from commandline), the IBD process can stall indefinitely after receiving a large block:\n```\n2022-08-07T13:24:50Z [net.cpp:3043] [CNode] Added connection to 104.248.143.83:8333 peer=0\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending version (102 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:1146] [PushNodeVersion] send version message: version 70016, blocks=239242, them=104.248.143.83:8333, txrelay=1, peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: version (102 bytes) peer=0\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending verack (0 bytes) peer=0\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending getaddr (0 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2754] [ProcessMessage] receive version message: /Satoshi:0.20.1/: version 70015, blocks=748403, us=104.248.143.83:8333, txrelay=1, peer=0, peeraddr=104.248.143.83:8333\n2022-08-07T13:24:50Z [timedata.cpp:57] [AddTimeData] added time data, samples 2, offset -1 (+0 minutes)\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: verack (0 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2797] [ProcessMessage] New outbound peer connected: version: 70015, blocks=748403, peer=0, peeraddr=104.248.143.83:8333 (manual)\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending sendheaders (0 bytes) peer=0\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending sendcmpct (9 bytes) peer=0\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending sendcmpct (9 bytes) peer=0\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending ping (8 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:4650] [SendMessages] initial getheaders (319216) to peer=0 (startheight:748403)\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending getheaders (997 bytes) peer=0\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending feefilter (8 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: sendheaders (0 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: sendcmpct (9 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: sendcmpct (9 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: ping (8 bytes) peer=0\n2022-08-07T13:24:50Z [net.cpp:3060] [PushMessage] sending pong (8 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: getheaders (1029 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:3223] [ProcessMessage] Ignoring getheaders from peer=0 because node is in initial block download\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: feefilter (8 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:4051] [ProcessMessage] received: feefilter of 0.00001000 BTC/kvB from peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: pong (8 bytes) peer=0\n2022-08-07T13:24:50Z [net_processing.cpp:2558] [ProcessMessage] received: headers (162003 bytes) peer=0\n```\nThen any other attemps to connect to other peers (or accept incoming connections) stalls permanently (we can waitfior hours: no network activity, no disk activity, but some thread uses 100% of a CPU core, probably in a tight loop generated by a deadlock and infinite attemps to recover from it).\n\nIf we try to shutdown, al most all databases thread are closed, the RPC services are closed, But the conenction manager remains locked for about ~15 minutes, not doing anything.\n\nIn fact the received headers are not even starting to be parse until AFTER these ~15 minutes. At which time we see that in logs:\n(note: I've enabled ```logtimestamps=1```, ```logsourcelocations=1``` and ```logthreadnames=1``` in bitcoin.conf to have more traceable traces; and ", "maintainer_label": "question", "repo": "bitcoin/bitcoin", "judge_label": "bug", "judge_confidence": 0.97, "judge_rationale": "User reports deterministic stall during IBD, indicating incorrect behavior that requires code change, not user misconfiguration."}
@@ -189,7 +189,7 @@
 {"id": 1706, "text": "Support \"jump to\" for literal record keys\n\n# Suggestion\n\n<!--\n Please fill in each section completely. Thank you!\n-->\n\n## \ud83d\udd0d Search Terms\n\n<!--\n \ud83d\udca1 Did you know? TypeScript has over 2,000 open suggestions!\n \ud83d\udd0e Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.\n The \"Common Feature Requests\" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests\n\n Replace the text below:\n-->\n\n- jump to record key\n\n## \u2705 Viability Checklist\n\n<!--\n Suggestions that don't meet all these criteria are very, very unlikely to be accepted.\n We always recommend reviewing the TypeScript design goals before investing time writing\n a proposal for ideas outside the scope of the project.\n-->\nMy suggestion meets these guidelines:\n\n* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code\n* [x] This wouldn't change the runtime behavior of existing JavaScript code\n* [x] This could be implemented without emitting different JS based on the types of the expressions\n* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)\n* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).\n\n## \u2b50 Suggestion\n\n<!-- A summary of what you'd like to see added or changed -->\n\nRecord keys should support \"Jump to definition\" actions.\n\n## \ud83d\udcc3 Motivating Example\n\n<!--\n If you were announcing this feature in a blog post, what's a short explanation that shows\n a developer why this feature improves the language?\n-->\n\n```ts\ntype Something = { field: string };\n\ntype Somethings<Keys extends string> = Record<Keys, Something>;\n\ntype ContainerOfSomethings = Somethings<'a' | 'b'>;\n\nconst container: ContainerOfSomethings = {\n a: { field: 'a' },\n b: { field: 'b' }\n};\n\nconsole.log(container.a);\n // ^---- \"Jump to\" should bring me to line 5 where 'a' is listed\n```\n\n[Playground Example](https://www.typescriptlang.org/play?ts=5.2.0-beta#code/C4TwDgpgBAyg9gWwsAFgSwHYHMoF4oDeUAZmhADYAmAXFAM7ABOmOAvgNwBQnoksiydNjoAeANIQQdKBAAewCBkrSGzbAD48UAEoQAxnEaVxkugBp+SVC3Vce4aAGE4GYAENMERgHli8K0JY0vj+giyiAORuEVAAPlARAEYRttwGGAxQ6e6ejLTOrh4YXr6h1sJaBJxQNVButESkFDQJ0VCsZtW1iQ0kZFS0STGsnBxpLnRw5BAAdORwWAAU2UVeM24AlFy1O7t7tQD0B1AAegC0F2dQAEQAUgCuCGBQwHDX9Chw91RQiWo4SBecCg5E8UAArFAAO4oLzQKIxNDSUEMCCUIA)\n\n## \ud83d\udcbb Use Cases\n\n<!--\n What do you want to use this for?\n What shortcomings exist with current approaches?\n What workarounds are you using in the meantime?\n-->\n\nEnhance Developer Experience.", "maintainer_label": "support", "repo": "TypeScript", "judge_label": "feature", "judge_confidence": 0.99, "judge_rationale": "User requests new IDE navigation support for record keys, which is a request for additional functionality."}
 {"id": 1560, "text": "Autocomplete breaks after one property for an array generic\n\n### \ud83d\udd0e Search Terms\n\narray generic \n\n### \ud83d\udd57 Version & Regression Information\n\n- This is the behavior in every version I tried, and I reviewed the FAQ for entries about generics\n\n### \u23ef Playground Link\n\nhttps://www.typescriptlang.org/play?ts=5.4.2#code/C4TwDgpgBAsg9gEwgGwMLIIYFcDOEA8AKgHxQC8UA3gFBR1QDyASgPwBcsiK62eRxAbQC6Ablr0AggDkAIu05I0mXARLCxAXygAyKAAUMAJ2ABLDMn5jqoSFABCGPAEUsEQyCJQIAD2AQAdgg4UDjAhib+AOYANFAAql6+AUFQcABGAFYQAMbApBQ09FAAtlzIHIRiRQCOru7y8Io8KvhxxJpWNtBxeIYubiDk9o4Q-e74AEQ9bhOxlFD+GMUQHKHhUSJQGJErC1jFaW5QGu3W4NB6cKE4Y4MUDs51HhOX17NUUKbAyLtrEZGbbJwfx+EGrML-Y6nM62W5DaZ9J5QAA++iuwBuTysADMsP5ciZgZ8IKF-p4fKCUrdiAAKWoDCrCACUVHEdCB-hwcB+ADpkHBInSnkzNNRqLj8aYiX5SVEAEzkpKBYK3YS0+nuCoswr0Dlc3n8wUakAi6gaMUy0xRGkCNmsopFUqKDhTXqzO01J4cHUOh2LZYuy3u32+gD0oaghHAkO20AAFm5oAB3EzIZBbLDAOBA4pgH5+D0h2McACMAAZC3QNNE7dXqEJTdYSVbInKbXafQ6nSgXQjgyHjd7K36lrsJkGayGHeHI+5PtGolsdlAE4YILETMAoEngQByLfYLM5vMQAtTutFOsNsRAA\n\n### \ud83d\udcbb Code\n\n```ts\ntype ModelClause<T> = {\n OR?: ModelClause<T>[];\n AND?: ModelClause<T>[];\n} & Partial<T>;\n\ntype BaseQuery<T extends string, U extends object> = {\n model: T;\n query?: ModelClause<U>;\n};\n\ntype UserQuery = BaseQuery<\"User\", { name: string; age: number }>;\ntype PostsQuery = BaseQuery<\"Posts\", { title: string; content: string }>;\n\ntype Query = UserQuery | PostsQuery;\n\nfunction testing<T extends Query>(query: T[]) {\n console.log(query);\n}\n\nfunction testing2<T extends Query[]>(query: T) {\n console.log(query);\n}\n\ntesting([\n {\n model: \"User\",\n query: {\n name: \"test\",\n // Typing age here will autocomplete\n age: 10\n },\n },\n]);\n\ntesting2([\n {\n model: \"User\",\n query: {\n name: \"test\",\n // Try typing age here, it won't autocomplete\n },\n },\n]);\n\n```\n\n### \ud83d\ude41 Actual behavior\n\nFor the `testing` function, you correctly get suggested fields when filling in the `query` property.\n\n![CleanShot 2024-03-21 at 11 57 26](https://github.com/microsoft/TypeScript/assets/11869830/4f65c296-1e14-49ec-a65a-1a397d7c1e23)\n\n![CleanShot 2024-03-21 at 11 57 41](https://github.com/microsoft/TypeScript/assets/11869830/5378bbb7-b651-4585-939d-542671f0d560)\n\nHowever, for `testing2`, the suggestion works for your first property, whichever one you try.\n\n![CleanShot 2024-03-21 at 11 57 57](https://github.com/microsoft/TypeScript/assets/11869830/94a530c0-d39f-4b61-adf5-ab20d078c0db)\n\n![CleanShot 2024-03-21 at 11 58 25](https://github.com/microsoft/TypeScript/assets/11869830/2a3acfdb-bb26-4ff6-b29a-e9f36c71cd18)\n\nHowever, once the first one is provided, it will stop autocompleting.\n\n![CleanShot 2024-03-21 at 11 58 56](https://github.com/microsoft/TypeScript/assets/11869830/c70261ec-4a88-4174-9fe6-867acf3a633c)\n\nOnce one has been provided, you can also list any key, regardless of if it's part of the model.\n\n![CleanShot 2024-03-21 at 12 00 27](https://github.com/microsoft/TypeScript/assets/11869830/2f35780d-2466-4b05-a9fc-fe75c29700dc)\n\n![CleanShot 2024-03-21 at 12 00 45](https://github.com/microsoft/TypeScript/assets/11869830/02b0401e-a9b2-4868-8d29-64d009cdc0c4)\n\n### \ud83d\ude42 Expected behavior\n\nIt should correctly suggest all properties and typecheck additional properties and not stop working after the first one.\n\n### Additional information about the issue\n\nSome extra context why I'm using the `testing2` approach, here's a [playground link](https://www.typescriptlang.org/play?ts=5.4.2#code/C4TwDgpgBAsg9gEwgGwMLIIYFcDOEA8AKgHxQC8UA3gFBR1QDyASgPwBcsiK62eRxAbQC6Ablr0AggDkAIu05I0mXARLCxAXygAyKAAUMAJ2ABLDMn5jqoSFABCGPAEUsEQyCJQIAD2AQAdgg4UDjAhib+AOYANFAAql6+AUFQcABGAFYQAMbApBQ09FAAtlzIHIRiRQCOru7y8Io8KvhxxJpWNtBxeIaNKORUUP4YxRAcoeFRIlAYkePDWMVpblAaYl3xvS5uIIMOznUeAEQ9bsexZ31l7dbg0Hpwof3Ig5RQpsDIC5MRkTPZOD+PzAiZhP5rDb3fRPYA4HbufaOCAIk6PUI4C4w543TrQ1GDK4EgA+2LhqLxtlRhDgL34g0IiRBKSJR3EdBYWzcL3ZUAqTOSwXR5LZRU5wp5RQ4-ggADc3JToDAMGBqXAmBAcFhkMBPD5mcFDBAMAggcg9qjhPkqLyBABpKARKAAawgIDgADMoIQhBw1XTCPahLd1tRqB6sP5ciYgR9NaYogAmPVJQLBS3BgAUtTcJk1FQAlBxlaqjjSNVqdfTCvRAf4cHBvgA6ZBwSLZup5nAFqxFI3ALCGfxQYSzYIltUV7W6kiaMN10IjlS", "maintainer_label": "support", "repo": "TypeScript", "judge_label": "bug", "judge_confidence": 0.96, "judge_rationale": "User reports incorrect autocomplete/type inference behavior in TypeScript, indicating a defect needing a library change."}
 {"id": 1881, "text": "Data URI scheme support for images in settings.json\n\n# Description of the new feature/enhancement\n\nIt would be great to be able to set image files (like `icon` or `backgroundImage`) in settings.json using data URI scheme. This could be useful when making backups or clones of Windows terminal settings, when syncing them with other devices, etc., especially when our custom profiles are concerned.\n\n# Proposed technical implementation details\n\nAn example fragment from settings.json for a custom `icon`:\n\n```\n{\n \"guid\": \"{7895828e-1e14-4068-89b4-582567b7495e}\",\n \"name\": \"MySQL\",\n \"commandline\": \"wsl.exe mysql -u username -p\",\n \"hidden\": false,\n \"icon\": \"data:image/png;base64,iVBORw0KG..............goAJRU5ErkJggg==\"\n}\n```", "maintainer_label": "support", "repo": "terminal", "judge_label": "feature", "judge_confidence": 0.99, "judge_rationale": "User is requesting a new capability (data URI support) in settings.json, indicating a feature enhancement."}
-{"id": 1590, "text": "Tooltip component accessibility is lacking\n\n### Reproduction link\n\n[https://antd-reproduce-5x-yvsnjz.stackblitz.io](https://antd-reproduce-5x-yvsnjz.stackblitz.io)\n\n### Steps to reproduce\n\n1. Turn on any screen reader\n2. Use keyboard Tab key to move focus to the link that triggers the tooltip\n\n### What is expected?\n\n- Screen reader should announce tooltip content with the trigger content\n- Moving keyboard focus to the tooltip trigger should display tooltip content for keyboard users\n\n### What is actually happening?\n\n- Moving keyboard focus to tooltip trigger does not display the tooltip content (there is also no easy way to make this happen from a dev perspective)\n- Screen reader does not announce tooltip content when trigger is focused\n\n| Environment | Info |\n| --- | --- |\n| antd | 5.19.2 |\n| React | 18.3.1 |\n| System | Sonoma 14.5 |\n| Browser | Chrome Version 126.0.6478.127 (arm64) |\n\n---\nThe tooltip content should be related to the tooltip trigger accessibly. This is done by adding the aria-describedby attribute to the tooltip's trigger element, and providing the tooltip content's id value to aria-describedby as its attribute value.\nDevelopers should have an easy way to indicate that tooltip content should show up on hover and on focus. This allows keyboard only users to access the tooltip content. Providing an optional prop for displaying the tooltip on focus would be appropriate. But this also requires that the tooltip trigger be focusable, which is not something the AntD Tooltip component currently checks.\n\n<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->", "maintainer_label": "support", "repo": "ant-design", "judge_label": "ERROR", "judge_confidence": 0.0, "judge_rationale": "Expecting value: line 1 column 1 (char 0)"}
+{"id": 1590, "text": "Tooltip component accessibility is lacking\n\n### Reproduction link\n\n[https://antd-reproduce-5x-yvsnjz.stackblitz.io](https://antd-reproduce-5x-yvsnjz.stackblitz.io)\n\n### Steps to reproduce\n\n1. Turn on any screen reader\n2. Use keyboard Tab key to move focus to the link that triggers the tooltip\n\n### What is expected?\n\n- Screen reader should announce tooltip content with the trigger content\n- Moving keyboard focus to the tooltip trigger should display tooltip content for keyboard users\n\n### What is actually happening?\n\n- Moving keyboard focus to tooltip trigger does not display the tooltip content (there is also no easy way to make this happen from a dev perspective)\n- Screen reader does not announce tooltip content when trigger is focused\n\n| Environment | Info |\n| --- | --- |\n| antd | 5.19.2 |\n| React | 18.3.1 |\n| System | Sonoma 14.5 |\n| Browser | Chrome Version 126.0.6478.127 (arm64) |\n\n---\nThe tooltip content should be related to the tooltip trigger accessibly. This is done by adding the aria-describedby attribute to the tooltip's trigger element, and providing the tooltip content's id value to aria-describedby as its attribute value.\nDevelopers should have an easy way to indicate that tooltip content should show up on hover and on focus. This allows keyboard only users to access the tooltip content. Providing an optional prop for displaying the tooltip on focus would be appropriate. But this also requires that the tooltip trigger be focusable, which is not something the AntD Tooltip component currently checks.\n\n<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->", "maintainer_label": "support", "repo": "ant-design", "judge_label": "bug", "judge_confidence": 0.93, "judge_rationale": "The component fails to meet expected accessible behavior (no focus handling), indicating a defect in the library rather than user error or a simple usage question."}
 {"id": 1982, "text": "tour: explain the semantics of the main goroutine\n\nContext: http://127.0.0.1:3999/concurrency/1\n\nIn concurrency/1 (Goroutines), commenting out line 17 say(\"hello\") also stops the go say(\"world\") from doing anything. The program exits before any worlds are said, yet without commenting out line 17 it seems to wait for all goroutines to finish before exiting.", "maintainer_label": "support", "repo": "go", "judge_label": "question", "judge_confidence": 0.96, "judge_rationale": "User asks for explanation of Go's main goroutine semantics; no defect reported, just seeking understanding."}
 {"id": 1682, "text": "JS/TS Better inlay hint positioning in multiline rest parameters\n\n<!-- \u26a0\ufe0f\u26a0\ufe0f Do Not Delete This! feature_request_template \u26a0\ufe0f\u26a0\ufe0f -->\n<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->\n<!-- Please search existing issues to avoid creating duplicates. -->\n\n<!-- Describe the feature you'd like. -->\nThe inlay hint positioning in multiline rest parameters is odd.\n\nConsidering this function\n```js\nconst setTags = (...tags) => { /* ... */ }\n```\n\nHow the hint is positioned:\n![image](https://user-images.githubusercontent.com/2738812/159556543-0c01ff15-d8ff-4851-b670-5f4520a7e8df.png)\n\nWhat I expected it to be:\n![image](https://user-images.githubusercontent.com/2738812/159556678-e719991e-ce0a-46de-95e7-c6c113cee8ae.png)", "maintainer_label": "support", "repo": "TypeScript", "judge_label": "feature", "judge_confidence": 0.97, "judge_rationale": "User requests a change in inlay hint positioning, i.e., an enhancement to existing behavior, not a bug or support question."}
 {"id": 1530, "text": "Add title to split window\n\n# Description of the new feature/enhancement\n\nWhen doing split windows in a tab, there's no header per window, rather the last command given is used int he TAB header. See attached example\n![WindowsTerminal](https://user-images.githubusercontent.com/61461157/75248606-c18abe00-57d4-11ea-96f1-9c19bdccbd85.png)\nCan you provide per split window a header with the command?\n\nThis is when using alt-shift-+ to open e.g. multiple Command prompts to perform pings.\n<!-- \nA clear and concise description of what the problem is that the new feature would solve.\nDescribe why and how a user would use this new functionality (if applicable).\n-->\n\n# Proposed technical implementation details (optional)\nAdd a header to split windows with the command given\n\n<!-- \nA clear and concise description of what you want to happen.\n-->", "maintainer_label": "support", "repo": "terminal", "judge_label": "feature", "judge_confidence": 0.97, "judge_rationale": "User requests new UI behavior (per split window header) \u2013 a product enhancement, not a bug or support query."}