diff --git a/scrape_out/issues/Automattic_wp-calypso_77283.json b/scrape_out/issues/Automattic_wp-calypso_77283.json
new file mode 100644
index 0000000000000000000000000000000000000000..6e7c49b597be04f9bd71c571ffd26e67091923c8
--- /dev/null
+++ b/scrape_out/issues/Automattic_wp-calypso_77283.json
@@ -0,0 +1 @@
+{"number": 77283, "title": "Create wrapper component for Launchpad", "body": "Make a generic \u201cLaunchpad\u201d component that wraps the checklist/checklist item components and utilizes the connection to the API via `useLaunchpad` hook in data-stores.\r\n\r\nRelated to https://github.com/Automattic/wp-calypso/issues/77284 https://github.com/Automattic/wp-calypso/issues/77285", "state": "CLOSED", "created_at": "2023-05-23T20:21:19Z", "closed_at": "2023-06-01T20:12:16Z", "author_login": "nelsonec87", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 77511, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["[Feature] Launchpad", "Launchpad Checklist Refactor"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/Becksteinlab_MDPOW_237.json b/scrape_out/issues/Becksteinlab_MDPOW_237.json
new file mode 100644
index 0000000000000000000000000000000000000000..fb0a5df4daa8603c7f92a896d928f8d810121358
--- /dev/null
+++ b/scrape_out/issues/Becksteinlab_MDPOW_237.json
@@ -0,0 +1 @@
+{"number": 237, "title": "accept dihedrals_kws dictionary as input for use with workflows base and registry", "body": "link PR #229 \r\n\r\n* after merging PR #217 \r\n* modify workflows.dihedral to accept and parse dictionary of kwargs\r\n* add functionality to automated analyses as they are completed", "state": "CLOSED", "created_at": "2023-02-01T02:16:30Z", "closed_at": "2023-04-04T01:59:34Z", "author_login": "cadeduckworth", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 229, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/BrokkAi_brokk_3022.json b/scrape_out/issues/BrokkAi_brokk_3022.json
new file mode 100644
index 0000000000000000000000000000000000000000..9b35b95516c9a5073fde84ead544efb49f6569d6
--- /dev/null
+++ b/scrape_out/issues/BrokkAi_brokk_3022.json
@@ -0,0 +1 @@
+{"number": 3022, "title": "Use primary repo analyzer as basis for worktrees", "body": "We should clone the primary analyzer cache and rebuild any changes necessary for the worktree branch, instead of starting from scratch", "state": "CLOSED", "created_at": "2026-03-06T19:59:09Z", "closed_at": "2026-03-12T09:43:41Z", "author_login": "jbellis", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 3029, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/COVESA_cdsp_88.json b/scrape_out/issues/COVESA_cdsp_88.json
new file mode 100644
index 0000000000000000000000000000000000000000..c486b1c9e32a77e8fc510d13bbe07667cb9c398e
--- /dev/null
+++ b/scrape_out/issues/COVESA_cdsp_88.json
@@ -0,0 +1 @@
+{"number": 88, "title": "Knowledge Layer Server components fails to build: Ubuntu 24.10 not available", "body": "## Summary\nTrying to build the Knowledge Layer Server from either the docker directory or the KL example results in the following build error:\n\n```\n/genivi/cdsp/cdsp/examples/knowledgelayer-hello-world$ docker compose -f docker-compose.yml build knowledge-layer \nCompose can now delegate builds to bake for better performance.\n To do so, set COMPOSE_BAKE=true.\n[+] Building 3.0s (6/18) docker:default\n => [knowledge-layer internal] load build definition from Dockerfile 0.0s\n => => transferring dockerfile: 1.02kB 0.0s\n => [knowledge-layer internal] load metadata for docker.io/library/ubuntu:24.10 0.5s\n => [knowledge-layer internal] load .dockerignore 0.0s\n => => transferring context: 2B 0.0s\n => CACHED [knowledge-layer 1/14] FROM docker.io/library/ubuntu:24.10@sha256:cdf755952ed117f6126ff4e65810bf93767d4c38f5c7185b50e 0.0s\n => [knowledge-layer internal] load build context 0.2s\n => => transferring context: 17.68kB 0.1s\n => ERROR [knowledge-layer 2/14] RUN apt-get -y update && apt-get install -y --no-install-recommends build-essential cmake 2.4s\n------ \n > [knowledge-layer 2/14] RUN apt-get -y update && apt-get install -y --no-install-recommends build-essential cmake g++ ca-certificates git wget: \n1.482 Ign:1 http://security.ubuntu.com/ubuntu oracular-security InRelease \n1.482 Ign:2 http://archive.ubuntu.com/ubuntu oracular InRelease \n1.620 Ign:3 http://archive.ubuntu.com/ubuntu oracular-updates InRelease \n1.621 Err:4 http://security.ubuntu.com/ubuntu oracular-security Release\n1.621 404 Not Found [IP: 91.189.92.22 80]\n1.762 Ign:5 http://archive.ubuntu.com/ubuntu oracular-backports InRelease\n1.905 Err:6 http://archive.ubuntu.com/ubuntu oracular Release\n1.905 404 Not Found [IP: 91.189.92.24 80]\n2.057 Err:7 http://archive.ubuntu.com/ubuntu oracular-updates Release\n2.057 404 Not Found [IP: 91.189.92.24 80]\n2.199 Err:8 http://archive.ubuntu.com/ubuntu oracular-backports Release\n2.199 404 Not Found [IP: 91.189.92.24 80]\n2.220 Reading package lists...\n2.236 E: The repository 'http://security.ubuntu.com/ubuntu oracular-security Release' does not have a Release file.\n2.236 E: The repository 'http://archive.ubuntu.com/ubuntu oracular Release' does not have a Release file.\n2.236 E: The repository 'http://archive.ubuntu.com/ubuntu oracular-updates Release' does not have a Release file.\n2.236 E: The repository 'http://archive.ubuntu.com/ubuntu oracular-backports Release' does not have a Release file.\n------\nfailed to solve: process \"/bin/sh -c apt-get -y update && apt-get install -y --no-install-recommends build-essential cmake g++ ca-certificates git wget\" did not complete successfully: exit code: 100\n```\n\n## Investigation\nThe KL Dockerfile builds using Ubuntu 24.10 as a base, which is an interim rather than Long Term Support (LTS) version. Working assumption is that the release files have been moved to an archive, hence the failure.\n\n### Trying Ubuntu 24.04 LTS\nDropping down to the latest LTS, Ubuntu 24.04 LTS solves the issue, but results in other later build errors related to software versions:\n```\n$ docker compose -f docker-compose-cdsp.yml build knowledge-layer \nCompose can now delegate builds to bake for better performance.\n To do so, set COMPOSE_BAKE=true.\n[+] Building 808.7s (18/18) FINISHED docker:default\n => [knowledge-layer internal] load build definition from Dockerfile 0.0s\n => => transferring dockerfile: 1.02kB 0.0s\n => [knowledge-layer internal] load metadata for docker.io/library/ubuntu:24.04 0.6s\n => [knowledge-layer internal] load .dockerignore 0.0s\n => => transferring context: 2B 0.0s\n => [knowledge-layer 1/14] FROM docker.io/library/ubuntu:24.04@sha256:d1e2e92c075e5ca139d51a140fff46f84315c0fdce203eab2807c7e495 0.0s\n => [knowledge-layer internal] load build context 0.0s\n => => transferring context: 19.16kB 0.0s\n => CACHED [knowledge-layer 2/14] RUN apt-get -y update && apt-get install -y --no-install-recommends build-essential cmake 0.0s\n => CACHED [knowledge-layer 3/14] COPY ZscalerRootCertificate-2048-SHA256.crt /usr/local/share/ca-certificates/ZscalerRootCertif 0.0s\n => [knowledge-layer 4/14] COPY Netskope_rootcaCert.pem /usr/local/share/ca-certificates/Netskope_rootcaCert.crt 0.1s\n => [knowledge-layer 5/14] RUN update-ca-certificates --verbose 2.3s\n => [knowledge-layer 6/14] RUN wget https://archives.boost.io/release/1.87.0/source/boost_1_87_0.tar.gz && tar xzf boost_1_8 765.9s \n => [knowledge-layer 7/14] WORKDIR /src 0.1s \n => [knowledge-layer 8/14] COPY connector connector 0.6s \n => [knowledge-layer 9/14] COPY symbolic-reasoner symbolic-reasoner 0.2s \n => [knowledge-layer 10/14] COPY third_party third_party 0.2s \n => [knowledge-layer 11/14] COPY common-test-resources common-test-resources 0.2s \n => [knowledge-layer 12/14] COPY CMakeLists.txt . 0.1s \n => [knowledge-layer 13/14] WORKDIR /src/build 0.1s\n => ERROR [knowledge-layer 14/14] RUN cmake -DCMAKE_BUILD_TYPE=Release .. && make reasoner_client -j8 37.8s\n------ \n > [knowledge-layer 14/14] RUN cmake -DCMAKE_BUILD_TYPE=Release .. && make reasoner_client -j8: \n1.123 -- The CXX compiler identification is GNU 13.3.0 \n1.180 -- Detecting CXX compiler ABI info \n1.345 -- Detecting CXX compiler ABI info - done \n1.364 -- Check for working CXX compiler: /usr/bin/c++ - skipped \n1.367 -- Detecting CXX compile features\n1.368 -- Detecting CXX compile features - done\n1.370 CMake Error at CMakeLists.txt:11 (cmake_policy):\n1.370 Policy \"CMP0167\" is not known to this version of CMake.\n1.370 \n1.370 \n1.553 -- Found Boost: /usr/local/lib/cmake/Boost-1.87.0/BoostConfig.cmake (found suitable version \"1.87.0\", minimum required is \"1.87\") found components: system filesystem thread \n23.97 -- Using the multi-header code from /src/build/_deps/json-src/include/\n28.55 -- The C compiler identification is GNU 13.3.0\n28.59 -- Detecting C compiler ABI info\n28.73 -- Detecting C compiler ABI info - done\n28.74 -- Check for working C compiler: /usr/bin/cc - skipped\n28.75 -- Detecting C compile features\n28.75 -- Detecting C compile features - done\n37.41 -- Found Threads: TRUE \n37.44 -- Configuring incomplete, errors occurred!\n------\nfailed to solve: process \"/bin/sh -c cmake -DCMAKE_BUILD_TYPE=Release .. && make reasoner_client -j8\" did not complete successfully: exit code: 1\n```\n\nThe problem seems to be CMake version in Ubuntu 24.04 LTS.\n\n### Trying Ubuntu 25.10 Interim\nThere is no LTS version later than 24.04. \nTrying the Ubuntu 25.10 Interim release solves the CMake issue and KL builds. However as an Interim release it will also quickly become unsupported as with 24.10 and the original bug will repeat itself.\n\n### Solutions / workarounds\nSome possible ideas:\n1. Use 24.04 LTS and extend the Dockerfile to individually install the required later CMake\n2. Use 25.10 Interim _but we must watch and update_ to 25 LTS when it is released.\n\n@chrizmc, @claireqiu , @sschleemilch you may have other ideas having a better understanding of the code. I have not simply pushed a fix for 2 because of the open KL PR.", "state": "CLOSED", "created_at": "2026-03-12T17:06:43Z", "closed_at": "2026-03-18T17:41:27Z", "author_login": "slawr", "comment_rounds": [{"comments": [{"id": "IC_kwDOKnhlIs7ybtxM", "body": "Thank you @slawr , we are investigating and provide fix soon", "createdAt": "2026-03-16T12:35:41Z", "updatedAt": "2026-03-16T12:35:54Z", "author": {"login": "claireqiu"}}]}, {"comments": [{"id": "IC_kwDOKnhlIs7zcg0W", "body": "Can confirm this now builds with the update from @claireqiu a couple of days ago. Can close when PR #88 merged", "createdAt": "2026-03-18T17:32:08Z", "updatedAt": "2026-03-18T17:32:50Z", "author": {"login": "slawr"}}]}], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/CRPropa_CRPropa3_6.json b/scrape_out/issues/CRPropa_CRPropa3_6.json
new file mode 100644
index 0000000000000000000000000000000000000000..c7a91aba0ce3df88babc65d3aa441284da616f74
--- /dev/null
+++ b/scrape_out/issues/CRPropa_CRPropa3_6.json
@@ -0,0 +1 @@
+{"number": 6, "title": "", "body": "", "state": "", "created_at": "", "closed_at": null, "author_login": "", "comment_rounds": [{"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDQzNjM4ODMy", "body": "Hi,\n\ncould you please run \n\n/usr/local/bin/python -c \"import sys; from distutils import sysconfig; \nsys.stdout.write(sysconfig.get_python_inc())\"\n\nand report the output? Maybe your homebrew python installation is faulty.\n\nThanks\nGero\n\nAm Dienstag, 20. Mai 2014, 02:34:18 schrieb NiekSchultheiss:\n\n> I had to apply some hacks to get CRPropa running on my system with a\n> Homebrew installed Python.\n> \n> It showed the correct paths to the `/usr/local` version of Python during\n> `cmake ..` However, when doing `ccmake ..` it used the wrong Python\n> Headers:\n> \n> ```\n> PYTHON_EXECUTABLE /usr/local/bin/python\n> PYTHON_H_FOUND /System/Library/Frameworks/Python.framework/Headers\n> ```\n> \n> I had to manually set the Python headers location to the homebrew version:\n> \n> /usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Headers/Python.h\n> \n> Then I proceeded with `make && make test`, which passed 100%, then `make\n> install`. Which also went fine, but importing crpropa resulted in Python\n> crashing. I found wrong links to python:\n> \n> ```\n> otool -L /usr/local/lib/python2.7/site-packages/_crpropa.so\n> ```\n> \n> And had to change it to the correct one:\n> \n> ```\n> install_name_tool -change\n> ```\n> \n> /System/Library/Frameworks/Python.framework/Versions/2.7/Python\n> /usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/Pyt\n> hon /usr/local/lib/python2.7/site-packages/_crpropa.so\n> \n> After which running the example worked.\n> \n> ---\n> \n> Reply to this email directly or view it on GitHub:\n> https://github.com/CRPropa/CRPropa3/issues/6\n\n## \n\nDipl.-Phys. Gero M\u00fcller\nIII. Physikalisches Institut A\nRWTH Aachen University\n+49 (0)241 80 23567\n", "createdAt": "2014-05-20T15:10:00Z", "updatedAt": "2014-05-20T15:10:00Z", "author": {"login": "geromueller"}}]}, {"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDQ0MTczNDAx", "body": "Running:\n\n``` python\n>>> import sys\n>>> from distutils import sysconfig\n>>> sysconfig.get_python_inc()\n'/usr/local/Cellar/python/2.7.6_1/Frameworks/Python.framework/Versions/2.7/include/python2.7'\n```\n\nThanks,\nNiek\n", "createdAt": "2014-05-26T09:40:50Z", "updatedAt": "2014-05-26T09:40:50Z", "author": {"login": "NiekSchultheiss"}}]}, {"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDUxMDA1Mjg1", "body": "Hello!\n\nThere was a recent change in python/Python.cmake that might fix that. Can you try setting these options when running cmake:\n-DPYTHON_EXECUTABLE=/path/to/homebrew/python/python \n-DPYTHON_LIBRARIES=/path/to/homebrew/python/libpython.so (or .dylib)\nBy doing this you will be linking the libraries against your homebrew installed python instead of the standard Apple python framework.\n\nPlease let me know the outcome of this.\n\nRafael\n", "createdAt": "2014-08-03T22:25:02Z", "updatedAt": "2014-08-03T22:28:38Z", "author": {"login": "rafaelab"}}]}, {"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDExNTU2MTQ1Mg==", "body": "assume solved\n", "createdAt": "2015-06-26T07:31:13Z", "updatedAt": "2015-06-26T07:31:13Z", "author": {"login": "DavidWalz"}}]}], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "bare_mention", "will_close": false, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/ChainSafe_gossamer_3760.json b/scrape_out/issues/ChainSafe_gossamer_3760.json
new file mode 100644
index 0000000000000000000000000000000000000000..2fd1d7d1d280e32676b8ebce38ec7846bca1b2b4
--- /dev/null
+++ b/scrape_out/issues/ChainSafe_gossamer_3760.json
@@ -0,0 +1 @@
+{"number": 3760, "title": "(pkg/trie): Create Trie interface and rename our current implementation", "body": "Based on my [latest proposal](https://github.com/ChainSafe/gossamer/discussions/3646#discussioncomment-8465826) I created this issue to address the second part of Phase 0.\n\n> - Move all trie-related code to a single package in /pkg/trie.\n> - Create a Trie interface with the minimum necessary methods for a trie. Such as: get, insert, remove, contains, root\nRename the current Trie struct to InMemoryTrie.\n\nThe goal is to have a Trie interface with the minimum required functions and use them as a way to add polymorphism to our trie. This will helpful later to replace our InMemory trie to a backed db trie", "state": "CLOSED", "created_at": "2024-02-15T16:19:40Z", "closed_at": "2024-03-27T19:56:16Z", "author_login": "dimartiro", "comment_rounds": [{"comments": [{"id": "IC_kwDOCgOTdc53EWZY", "body": "Blocked by #3775 ", "createdAt": "2024-03-14T14:46:15Z", "updatedAt": "2024-03-14T14:46:15Z", "author": {"login": "dimartiro"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 3768, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["T-refactor", "C-simple", "S-trie"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/ChainSafe_gossamer_4464.json b/scrape_out/issues/ChainSafe_gossamer_4464.json
new file mode 100644
index 0000000000000000000000000000000000000000..d6cf3151420c659f85cf8ea82a49c48bac5d3ec1
--- /dev/null
+++ b/scrape_out/issues/ChainSafe_gossamer_4464.json
@@ -0,0 +1 @@
+{"number": 4464, "title": "Introduce interface for `TrieState`, implement `TrieState` with new translation shim type from `Externalities` to `TrieState`.", "body": "## Issue Summary\n\nTaken from design doc:\n\n> The `TrieState()` method defined in `StorageState` is responsible for retrieving the state trie for a given block hash. It retrieves the `Trie` associated to the block hash and returns a `*rtstorage.TrieState`. This method is almost exclusively called before calling `Instance.SetContextStorage` to be able track storage changes by a runtime instance. There are methods in `TrieState` that handle storage changes as well as starting, rolling back, and committing transactions. The changes are handled through [`storageDiff`](https://github.com/ChainSafe/gossamer/blob/2eff00475ac1234ac1701f596808f93b3bf0bd46/lib/runtime/storage/storagediff.go#L24) currently, which keep all the changes in memory before commiting, and applying them to a new in-memory trie to compute the state root. `StoreTrie` is explicitly called to persist the trie in `InmemoryStorageState` to be accessible later.\n \n> Given that storing a block and it's associated storage changes are handled in one `BlockImportOperation`, we should remove the `StoreTrie` method entirely from `StorageState`. Rather `BlockState.AddBlock` should accept an introduced [`OverlayedChanges`](https://github.com/paritytech/polkadot-sdk/blob/ad8620922bd7c0477b25c7dfd6fc233641cb27ae/substrate/primitives/state-machine/src/overlayed_changes/mod.rs#L99) type analagous to the substrate primitive. I propose creating an interface around `TrieState` first. Second, we create a new type that implements `TrieState` which combines the read-only `TrieBackend` of the block hash, as well as the `OverlayedChanges` type that can be extracted before calling `AddBlock`. This new `TrieState` will be passed into the runtime instance. This introduced implementation of `TrieState` is analagous to the substrate primitive [`sp_statemachine::ext::Ext`](https://github.com/paritytech/polkadot-sdk/blob/6c3219ebe9231a0305f53c7b33cb558d46058062/substrate/primitives/state-machine/src/ext.rs#L92) and the analgous trait to the `TrieState` interface is [`sp_externalities::Externalities`](https://github.com/paritytech/polkadot-sdk/blob/ad8620922bd7c0477b25c7dfd6fc233641cb27ae/substrate/primitives/externalities/src/lib.rs#L81). By following this approach, it should limit the amount of changes within the wazero runtime instance code.\n\n## Acceptance Criteria\n- Introduce `TrieState` interface and replace occurrences where [`storage.TrieState`](https://github.com/ChainSafe/gossamer/blob/2eff00475ac1234ac1701f596808f93b3bf0bd46/lib/runtime/storage/trie.go#L25) are used with new interface.\n- Create new `TrieState` implementation using the introduced `Ext` type issue #4462 to track changes\n- Given that all usages of `TrieState.Trie()` are called just to calculate the hash, we should modify any usages of `TrieState.Trie()` to a new method that will return the state root. We already have a method called `DeltaStateRoot` in the codebase to calculate the state root based on overlayed changes and backend.\n- Implement functionality using `Ext` type introduced in #4465.", "state": "CLOSED", "created_at": "2025-01-14T18:43:44Z", "closed_at": "2025-06-12T21:58:37Z", "author_login": "timwu20", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 4726, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/DataMedSci_yagit_58.json b/scrape_out/issues/DataMedSci_yagit_58.json
new file mode 100644
index 0000000000000000000000000000000000000000..dff1daab9d7994fee368b551edb6308dcc97467b
--- /dev/null
+++ b/scrape_out/issues/DataMedSci_yagit_58.json
@@ -0,0 +1 @@
+{"number": 58, "title": "We also need an instruction for developers to get and build the googletest framework locally without doing sudo make install.", "body": " We also need an instruction for developers to get and build the googletest framework locally without doing sudo make install.\r\n\r\n_Originally posted by @grzanka in https://github.com/DataMedSci/yagit/pull/57#discussion_r1292201274_\r\n ", "state": "CLOSED", "created_at": "2023-08-14T16:46:09Z", "closed_at": "2024-04-15T11:05:38Z", "author_login": "grzanka", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 67, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/DaveDuck321_GrapheneLang_47.json b/scrape_out/issues/DaveDuck321_GrapheneLang_47.json
new file mode 100644
index 0000000000000000000000000000000000000000..4857ff183bf90474f83d40b8bc81b8da8edf1b04
--- /dev/null
+++ b/scrape_out/issues/DaveDuck321_GrapheneLang_47.json
@@ -0,0 +1 @@
+{"number": 47, "title": "Arrays cannot be initialized", "body": "```rust\r\nfunction putchar : (char: u8) -> u8 = {\r\n const buffer : u8[1] = { char }; // Error: initializer list cannot be assigned to type 'u8[1]' (expected a struct type similar to '{u8}')\r\n\r\n puts<1>(&buffer);\r\n\r\n return char;\r\n};\r\n```\r\n\r\n\r\nThis doesn't work either\r\n\r\n```rust\r\nfunction putchar : (char: u8) -> u8 = {\r\n let buffer : u8[1];\r\n buffer[0] = char;\r\n\r\n puts<1>(&buffer); // Cannot use uninitialized variable 'buffer'\r\n\r\n return char;\r\n};\r\n```", "state": "CLOSED", "created_at": "2023-04-02T21:39:00Z", "closed_at": "2023-05-11T14:24:03Z", "author_login": "antroseco", "comment_rounds": [{"comments": [{"id": "IC_kwDOIUti0c5ZBDFm", "body": "I've already started looking at the initializer list problem.\r\n\r\nThe uninitialized variable check is defo a bug tho.", "createdAt": "2023-04-02T21:43:44Z", "updatedAt": "2023-04-02T21:43:44Z", "author": {"login": "DaveDuck321"}}]}, {"comments": [{"id": "IC_kwDOIUti0c5Znd6V", "body": "https://github.com/DaveDuck321/GrapheneLang/commit/8066af42d56c4c6b0a197528b1b4b5e2dc81c15f checks if we've written to any element of the array. If we have, the variable is marked as initialized. This is a bit coarse tbh but it allows us to initialize something.", "createdAt": "2023-04-11T14:50:54Z", "updatedAt": "2023-04-11T14:50:54Z", "author": {"login": "DaveDuck321"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 77, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/GCTC-NTGC_gc-digital-talent_16705.json b/scrape_out/issues/GCTC-NTGC_gc-digital-talent_16705.json
new file mode 100644
index 0000000000000000000000000000000000000000..272d5d0d0def4c4bd6931ca3529580de3bdc8553
--- /dev/null
+++ b/scrape_out/issues/GCTC-NTGC_gc-digital-talent_16705.json
@@ -0,0 +1 @@
+{"number": 16705, "title": "\ud83d\udd24 Duplicate values in common files", "body": "### \ud83d\udd24 Copy\n\n\n\n### \ud83d\ude4b\u200d\u2640\ufe0f Proposed Solution\n\n_No response_\n\n### \ud83c\udf0e Localization\n\n_No response_\n\n### \u2705 Acceptance Criteria\n\n- [ ] no duplicate array keys in common.php files", "state": "CLOSED", "created_at": "2026-05-06T15:10:55Z", "closed_at": "2026-05-07T17:33:00Z", "author_login": "mnigh", "comment_rounds": [{"comments": [{"id": "IC_kwDOFbwAwM8AAAABBaIvTA", "body": "This is a problem since only one of the values (the last one in the array overrides any previous ones) is actually being used. Which one should actually be used?\n\n## English\n```\n'bilingual' => 'Bilingual',\n'bilingual' => 'Bilingual positions',\n```\n\n## French\n```\n'bilingual' => 'Bilingue',\n'bilingual' => 'Postes bilingues',\n```", "createdAt": "2026-05-06T15:14:34Z", "updatedAt": "2026-05-06T15:14:34Z", "author": {"login": "mnigh"}}, {"id": "IC_kwDOFbwAwM8AAAABBbyqDA", "body": "> Which one should actually be used?\n\nSeems to me that they should be distinct strings with distinct keys. Hopefully there aren't too many uses of these strings to examine. Hopefully it's clear from the PR that the second one was introduced in what the usage should be. I'll tag an estimate of 2 for the sleuthing that will be needed.", "createdAt": "2026-05-06T19:23:50Z", "updatedAt": "2026-05-06T19:23:50Z", "author": {"login": "petertgiles"}}, {"id": "IC_kwDOFbwAwM8AAAABBbzw_w", "body": "> > Which one should actually be used?\n> \n> Seems to me that they should be distinct strings with distinct keys. Hopefully there aren't too many uses of these strings to examine. Hopefully it's clear from the PR that the second one was introduced in what the usage should be. I'll tag an estimate of 2 for the sleuthing that will be needed.\n\n## Screenshot\n\n", "createdAt": "2026-05-06T19:25:40Z", "updatedAt": "2026-05-06T19:25:40Z", "author": {"login": "mnigh"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 16733, "link_type": "closing_keyword", "will_close": true, "comment_count": 3, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["copy"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/GregTechCEu_GregTech-Modern_4397.json b/scrape_out/issues/GregTechCEu_GregTech-Modern_4397.json
new file mode 100644
index 0000000000000000000000000000000000000000..587cd911d5e688a95467c31109fab055baf0bc7e
--- /dev/null
+++ b/scrape_out/issues/GregTechCEu_GregTech-Modern_4397.json
@@ -0,0 +1 @@
+{"number": 4397, "title": "Unable to convert Copper Ingot into Copper Nuggets when manual compression is reenabled", "body": "### Checked for existing issues\n\n- [x] I have checked for existing issues, and have found none.\n\n### Tested latest version\n\n- [x] I have checked that this occurs on the latest version.\n\n### GregTech CEu Version\n\n7.4.1 SNAPSHOT c1673c9\n\n### Minecraft Version\n\n1.20.1 Forge\n\n### Recipe Viewer Installed\n\nEMI\n\n### Environment\n\nSingleplayer\n\n### Cross-Mod Interaction\n\nNo\n\n### Other Installed Mods\n\nEMI\n\n### Expected Behavior\n\nWhen changing `disableManualCompression` from true to false in the config, there should be a recipe that turns 1 Copper Ingot into 9 Copper Nuggets like with all other ingots\n\n### Actual Behavior\n\nCopper Nuggets can only be obtained using a Fluid Solidifier or an Alloy Smelter with a nugget Casting Mold\n\n### Steps to Reproduce\n\nIn `config/gtceu.yaml`, change the line `disableManualCompression: true` to `disableManualCompression: false`\nLook at the crafting recipe for Copper Nuggets\n\n### Additional Information\n\n_No response_", "state": "CLOSED", "created_at": "2025-12-28T11:16:57Z", "closed_at": "2026-01-05T11:08:43Z", "author_login": "esmenard", "comment_rounds": [{"comments": [{"id": "IC_kwDOJK5Dcs7cOL9A", "body": "https://github.com/GregTechCEu/GregTech-Modern/blob/c1673c9112619205c22fd55e1d50b8dc3861d2be/src/main/java/com/gregtechceu/gtceu/data/recipe/generated/MaterialRecipeHandler.java#L488-L499\n\nThis part creates disassembling recipes for every GregTech ingot, but not for Copper, given that it is a vanilla Minecraft ingot", "createdAt": "2025-12-28T12:21:49Z", "updatedAt": "2025-12-28T12:21:49Z", "author": {"login": "esmenard"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 4399, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["type: bug", "1.20.1"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/Hexastack_Hexabot_242.json b/scrape_out/issues/Hexastack_Hexabot_242.json
new file mode 100644
index 0000000000000000000000000000000000000000..66afd30b59db002eeafb54b0f97e9cfeef96d0e1
--- /dev/null
+++ b/scrape_out/issues/Hexastack_Hexabot_242.json
@@ -0,0 +1 @@
+{"number": 242, "title": "\ud83d\udc1b [BUG] - widget pasting text replace the old text content", "body": "### Description\r\nWe can notice that when we past a text content in the widget text field the old text content is replaced\r\n\r\n### Issue Demonstration\r\n\r\n\r\n### Reproduction steps\r\n\r\n```bash\r\n1. Go to Visual Editor\r\n2. Copy a text\r\n3. Paste the text in the widget\r\n4. Paste other text\r\n5. Notice the paste issue\r\n```\r\n\r\n### Logs\r\n\r\n_No response_\r\n\r\n### Browsers\r\n\r\n_No response_\r\n\r\n### OS\r\n\r\n_No response_", "state": "CLOSED", "created_at": "2024-10-18T16:30:00Z", "closed_at": "2024-11-12T08:56:02Z", "author_login": "yassinedorbozgithub", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 316, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/Jan-IngenHousz-Institute_open-jii_45.json b/scrape_out/issues/Jan-IngenHousz-Institute_open-jii_45.json
new file mode 100644
index 0000000000000000000000000000000000000000..2d178997ddb2f6bb0559c8a2a6a4e96ebe693d9c
--- /dev/null
+++ b/scrape_out/issues/Jan-IngenHousz-Institute_open-jii_45.json
@@ -0,0 +1 @@
+{"number": 45, "title": "Setup PostHog for Feature Flagging & Web Analytics", "body": "## Context\n\nWe need to onboard our web, mobile, and backend applications onto PostHog Cloud. This involves creating the project in the PostHog console, enabling basic analytics, setting up a sample feature flag, and generating the credentials (API key + host URL) so that each team can integrate their codebases.\n\n## Acceptance Criteria\n\n- A PostHog Cloud project exists under our organization\n- Analytics autocapture (pageviews and clicks) is enabled in the project settings\n- A sample feature flag (e.g. beta-ui-banner) is created with at least one rollout rule\n- The project's API key and host URL have been generated and securely stored\n- An internal document has been published that shows where to find the API key, host URL, and sample flag in the PostHog console\n- Each application (Web, Mobile, Backend) has access to the API key, host URL, and documentation\n\n## Additional Context\n\n- We are using PostHog Cloud, so there is no need for any self-hosting or infrastructure changes\n- The single project API key will be used by all front-end (web/mobile) and back-end integrations\n- Subsequent tickets will cover installing the SDKs and writing the actual instrumentation code", "state": "CLOSED", "created_at": "2025-01-07T09:27:10Z", "closed_at": "2025-11-17T11:04:05Z", "author_login": "dominikvrbic", "comment_rounds": [], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["documentation", "ci/cd"], "milestone": "Milestone 5 Beta: 0.1Beta launch", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/MTES-MCT_monitorfish_1957.json b/scrape_out/issues/MTES-MCT_monitorfish_1957.json
new file mode 100644
index 0000000000000000000000000000000000000000..2f30764f8bccc5b04fdbd9329b7a0f33f3b3bf5d
--- /dev/null
+++ b/scrape_out/issues/MTES-MCT_monitorfish_1957.json
@@ -0,0 +1 @@
+{"number": 1957, "title": "[Missions] Ne pas passer le parametre `seaFronts` au backend pour r\u00e9cup\u00e9rer les missions mais filtrer dans le front", "body": "Cela permet d'afficher toutes les missions sur la carto", "state": "CLOSED", "created_at": "2023-05-03T09:39:49Z", "closed_at": "2023-05-04T08:20:03Z", "author_login": "louptheron", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 1963, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["feat. enhancement", "dev"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/MatrixAI_Polykey_520.json b/scrape_out/issues/MatrixAI_Polykey_520.json
new file mode 100644
index 0000000000000000000000000000000000000000..8027e788056a05bda698f9c1d6e5f71ba82fc3ac
--- /dev/null
+++ b/scrape_out/issues/MatrixAI_Polykey_520.json
@@ -0,0 +1 @@
+{"number": 520, "title": "Use default exports for handler classes", "body": "### Specification\r\n\r\nAs a standard we want to use default exports if a file exports a single class. The client handlers used to export the caller and handler definition. Now it's just the handler so it needs to be updated to a default export.\r\n\r\n### Additional context\r\n\r\n* Related #509 \r\n* Related #513 \r\n\r\n### Tasks\r\n\r\n1. update all of the client handlers to use default exports.\r\n\r\n", "state": "CLOSED", "created_at": "2023-04-06T05:02:13Z", "closed_at": "2023-10-12T01:29:55Z", "author_login": "tegefaulkes", "comment_rounds": [{"comments": [{"id": "IC_kwDOCB2rRs5ZUToc", "body": "I accidentally created this to soon. let me edit it.", "createdAt": "2023-04-06T05:02:46Z", "updatedAt": "2023-04-06T05:02:46Z", "author": {"login": "tegefaulkes"}}, {"id": "IC_kwDOCB2rRs5ZUUfE", "body": "Is there any technical reason to use default exports?\r\n\r\nI think named exports are just generally better for maintainability. They prevent renaming things when you import them. Otherwise it's possible for the imported and exported name to become out of sync. ", "createdAt": "2023-04-06T05:08:17Z", "updatedAt": "2023-04-06T05:08:17Z", "author": {"login": "tegefaulkes"}}, {"id": "IC_kwDOCB2rRs5ZY2yN", "body": "It's just convention and consistency. Actually both can be used at the same time. Sometimes I provide a default export and named exports. **But the name of the file should always be the same as the name of the default export**.", "createdAt": "2023-04-06T22:12:40Z", "updatedAt": "2023-04-06T22:12:40Z", "author": {"login": "CMCDragonkai"}}]}, {"comments": [{"id": "IC_kwDOCB2rRs5hBOux", "body": "See if you can do this before we extract out all the CLI to Polykey-CLI.", "createdAt": "2023-07-09T13:11:59Z", "updatedAt": "2023-07-09T13:11:59Z", "author": {"login": "CMCDragonkai"}}]}, {"comments": [{"id": "IC_kwDOCB2rRs5nvg_O", "body": "Doing this now in #552.", "createdAt": "2023-09-29T08:29:09Z", "updatedAt": "2023-09-29T08:29:09Z", "author": {"login": "CMCDragonkai"}}, {"id": "IC_kwDOCB2rRs5nvg_P", "body": "Doing this now in #552.", "createdAt": "2023-09-29T08:29:09Z", "updatedAt": "2023-09-29T08:29:09Z", "author": {"login": "CMCDragonkai"}}, {"id": "IC_kwDOCB2rRs5nvheV", "body": "I think you used suffix naming. `XHandler`. Whereas usually we prefer prefix naming. Like `EventX`, or `ErrorX`, so `HandlerX` should be used instead.\n\nBut since the entire directory is this... it could be shortened to just `X`. In this case instead of `NodesClaimsGetHandler`, it could just be `NodesClaimsGet`. Subject, object verb order.\n\nI'm dropping the `Handler` name then.", "createdAt": "2023-09-29T08:30:52Z", "updatedAt": "2023-09-29T08:30:52Z", "author": {"login": "CMCDragonkai"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 567, "link_type": "closing_keyword", "will_close": true, "comment_count": 7, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["development", "r&d:polykey:core activity 1"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/NilFoundation_nil_52.json b/scrape_out/issues/NilFoundation_nil_52.json
new file mode 100644
index 0000000000000000000000000000000000000000..22055121aab69e82cc7d9d3a0063e0c92bc4ef61
--- /dev/null
+++ b/scrape_out/issues/NilFoundation_nil_52.json
@@ -0,0 +1 @@
+{"number": 52, "title": "Exclude bloom filters from the block / block hash", "body": "We can already verify the correctness of events / logs by checking merkle proof of inclusion to the block.\n\nBut the bloom filter data structure is difficult to prove in context of ZK, so it should be safe to exclude it. ", "state": "CLOSED", "created_at": "2025-01-30T14:15:30Z", "closed_at": "2025-02-07T13:59:26Z", "author_login": "knazarov", "comment_rounds": [{"comments": [{"id": "IC_kwDONucwYM6cjwRw", "body": "Should we also exclude Bloom filter from receipts?\n\nAnd also \"exclude from block\" and \"exclude from hash\" are two different things. E.g. we can store bloom filters as a block metainformation (like a signature) or we can just remove it.", "createdAt": "2025-01-31T08:23:24Z", "updatedAt": "2025-01-31T08:23:24Z", "author": {"login": "olegrok"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 218, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/OpenLiberty_liberty-tools-eclipse_239.json b/scrape_out/issues/OpenLiberty_liberty-tools-eclipse_239.json
new file mode 100644
index 0000000000000000000000000000000000000000..675343bc101b6f8df914184b76493bc0cc8b5ef7
--- /dev/null
+++ b/scrape_out/issues/OpenLiberty_liberty-tools-eclipse_239.json
@@ -0,0 +1 @@
+{"number": 239, "title": "Provide option on Run Config to do a 'clean' before running dev mode", "body": "", "state": "CLOSED", "created_at": "2022-11-14T03:44:05Z", "closed_at": "2025-03-20T14:39:21Z", "author_login": "scottkurz", "comment_rounds": [{"comments": [{"id": "IC_kwDOG7ZroM5gRJVv", "body": "This sounds like a dup of #111. ", "createdAt": "2023-06-30T19:27:36Z", "updatedAt": "2023-06-30T19:27:36Z", "author": {"login": "awisniew90"}}]}, {"comments": [{"id": "IC_kwDOG7ZroM5mTPtg", "body": "As a user, clean support is very useful. I hope it can be done soon. Now I need to clean from outside the IDE.", "createdAt": "2023-09-12T19:47:29Z", "updatedAt": "2023-09-12T19:47:52Z", "author": {"login": "gkwan-ibm"}}, {"id": "IC_kwDOG7ZroM5mTrx9", "body": "@gkwan-ibm - we are working on a prototype that will allow this along with any other \"pre start\" goal. We need to first have a design discussion over how we can keep this consistent over the three IDEs. \r\n", "createdAt": "2023-09-12T21:04:15Z", "updatedAt": "2023-09-12T21:04:15Z", "author": {"login": "awisniew90"}}, {"id": "IC_kwDOG7ZroM5mTtf3", "body": "@scottkurz - maybe we can add this topic to the next design discussion.", "createdAt": "2023-09-12T21:08:24Z", "updatedAt": "2023-09-12T21:08:24Z", "author": {"login": "awisniew90"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 554, "link_type": "closing_keyword", "will_close": true, "comment_count": 4, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "design", "parity"], "milestone": "25.0.6", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/PackageKit_PackageKit_202.json b/scrape_out/issues/PackageKit_PackageKit_202.json
new file mode 100644
index 0000000000000000000000000000000000000000..486b1ba7046e1358b1dc65059665477494f77d31
--- /dev/null
+++ b/scrape_out/issues/PackageKit_PackageKit_202.json
@@ -0,0 +1 @@
+{"number": 202, "title": "Use delta RPMs in DNF backend", "body": "The DNF backend is currently using full-size RPMs rather than delta RPMs. Should use delta RPMs when available.\r\n\r\nNot sure if this belongs in libdnf or PackageKit.", "state": "CLOSED", "created_at": "2017-07-01T00:02:52Z", "closed_at": "2026-01-20T13:11:57Z", "author_login": "da2x", "comment_rounds": [{"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDMxMjczNDkxOA==", "body": "I would imagine the concept of using DeltaRPMs would be mostly invisible to PackageKit. libdnf needs work to add support for DeltaRPMs (this is currently implemented in DNF mostly in [`dnf/drpm.py`](https://github.com/rpm-software-management/dnf/blob/master/dnf/drpm.py) and needs to be migrated into libdnf). ", "createdAt": "2017-07-03T21:15:07Z", "updatedAt": "2017-07-03T21:15:07Z", "author": {"login": "Conan-Kudo"}}]}, {"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDM5NTUyNTg5NA==", "body": "Any news on this one?\r\nIt's a bit annoying the gui can't do what the most commonly used cli tool can achive\r\nIt would be great for the bandwidth (last time i started my notebook it almost killed my vpn on my desktop which shouldn't be)\r\n\r\nOr should i disable packagekit and use dnf instead (that would do for me but not everyone is used to cli e.g. my whole family)\r\n\r\nThis isn't supposed to be a rant about packagekit; it's a good backend for gui updates and it does it's job, but there are some drawbacks like missing delta support or using the whole bandwidth", "createdAt": "2018-06-07T18:49:02Z", "updatedAt": "2018-06-07T18:49:02Z", "author": {"login": "nachfuellbar"}}]}, {"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDUzMTQ5ODUzMA==", "body": "See also issue #338 for starters...", "createdAt": "2019-09-14T17:35:06Z", "updatedAt": "2019-09-14T17:35:06Z", "author": {"login": "nekohayo"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 931, "link_type": "closing_keyword", "will_close": true, "comment_count": 3, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "Backend: dnf (Fedora Linux)"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/PolicyEngine_policyengine-us_6415.json b/scrape_out/issues/PolicyEngine_policyengine-us_6415.json
new file mode 100644
index 0000000000000000000000000000000000000000..d299788b6280a3cb35fc4194e3edb59c1490a21a
--- /dev/null
+++ b/scrape_out/issues/PolicyEngine_policyengine-us_6415.json
@@ -0,0 +1 @@
+{"number": 6415, "title": "Adjust `ssi_income_deemed_from_ineligible_spouse` formula ", "body": "I need to check the formula for `ssi_income_deemed_from_ineligible_spouse`, with that amount of income, both people should have 0 ssi. \r\n\r\n\r\n_Originally posted by @hua7450 in https://github.com/PolicyEngine/policyengine-us/issues/6411#issuecomment-3199205258_\r\n ", "state": "CLOSED", "created_at": "2025-08-19T20:57:55Z", "closed_at": "2025-08-25T13:09:24Z", "author_login": "hua7450", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 6411, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/RuminantFarmSystems_RuFaS_2044.json b/scrape_out/issues/RuminantFarmSystems_RuFaS_2044.json
new file mode 100644
index 0000000000000000000000000000000000000000..549c95934337eccaac64572c09f5add467bde379
--- /dev/null
+++ b/scrape_out/issues/RuminantFarmSystems_RuFaS_2044.json
@@ -0,0 +1 @@
+{"number": 2044, "title": "[Feed Storage] Investigate nutrient losses in Feed Storage E2E testing routine", "body": "\r\nThe nutrient loss routines of the Feed Storage module need to be carefully evaluated and in some cases corrected.\r\n\r\n## Status\r\n\r\nWith the correction of the Feed Storage degradation routines in #2014, the E2E testing results were evaluated and updated to better test the Feed Storage module. But the updates mainly focused on making sure that stored crops lost mass correctly, and not necessarily that they lost nutrients correctly.\r\n\r\n## Intention\r\n\r\nEnsure that nutrients are lost from stored crops as time goes by and they degrade.\r\n\r\n## Request\r\n\r\nEvaluate the nutrient compositions of feeds that are stored as part of the Feed Storage E2E testing routine, and confirm that they are correct and robust by evaluating the actual results of E2E testing with SMEs.\r\n\r\nA particular aspect that needs to be looked into is the loss of crude protein in Unprotected Hay. The crude protein mass goes to zero before the hay is finished losing dry matter, so a number of warnings are generated because the Hay is attempting to lose crude protein even though it has none left. Please determine whether this indicates a bug, or is reasonable behavior based on inputs and routines. If this behavior is found to be reasonable, please consider changing how the warning is raised or removing it entirely, because the current warning is very unspecific and repetitive.\r\n\r\n### Target deadline\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Additional Information\r\n\r\n\r\nThe lead SME who should be worked with for this issue is @KevinP-B \r\n\r\n", "state": "CLOSED", "created_at": "2024-10-24T16:47:58Z", "closed_at": "2025-01-24T20:26:51Z", "author_login": "Isgotkowitz", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 2132, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug", "dev-team", "Feed"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/Rust-GCC_gccrs_2709.json b/scrape_out/issues/Rust-GCC_gccrs_2709.json
new file mode 100644
index 0000000000000000000000000000000000000000..ef2cc67dad55ee12da1edab8f33f630d4c61a0aa
--- /dev/null
+++ b/scrape_out/issues/Rust-GCC_gccrs_2709.json
@@ -0,0 +1 @@
+{"number": 2709, "title": "ICE in impl const items without value", "body": "\r\n```rust\r\nstruct S;\r\n\r\nimpl S {\r\n const D: u8;\r\n}\r\n```\r\n\r\nwhile it should produce a nice error: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=9b8643a863d5350e8b226e8bc9789b88\r\n\r\nthis should be adressed in a later PR however :)\r\n\r\n_Originally posted by @CohenArthur in https://github.com/Rust-GCC/gccrs/pull/2708#discussion_r1368934653_\r\n ", "state": "CLOSED", "created_at": "2023-10-23T22:15:12Z", "closed_at": "2023-11-06T18:06:14Z", "author_login": "CohenArthur", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 2713, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug"], "milestone": "HIR Pipeline for libcore 1.49 Complete", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/SkinsRestorer_SkinsRestorer_1246.json b/scrape_out/issues/SkinsRestorer_SkinsRestorer_1246.json
new file mode 100644
index 0000000000000000000000000000000000000000..66d7bba570c97e7481975dc2d107e270f2912d2e
--- /dev/null
+++ b/scrape_out/issues/SkinsRestorer_SkinsRestorer_1246.json
@@ -0,0 +1 @@
+{"number": 1246, "title": "Error", "body": "### Is there an existing issue for this?\n\n- [X] I have searched the existing issues\n\n### Are you using forge?\n\nNo\n\n### Installed conforming to our guide?\n\n- [X] I have read the installation guide and performed all steps\n\n### Describe your issue\n\nError on console on startup\n\n### How can we reproduce what you got?\n\nStep 1. Put SkinsRestorer in plugin folder\r\nStep 2. Start server\n\n### Server/Error Logs\n\nhttps://mclo.gs/wbEIBAq\n\n### Minecraft implementation\n\n```markdown\n- Proxy: N/A\r\n- Backend: \r\n[09:30:15 INFO]: Checking version, please wait...\r\n[09:30:16 INFO]: This server is running Paper version git-Paper-481 (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: cbcdfd0)\r\nYou are 3 version(s) behind\r\nDownload the new version at: https://papermc.io/downloads\n```\n\n\n### What client are you using?\n\nOriginal Minecraft Launcher\n\n### SkinsRestorer Version\n\nSkinsRestorer version 14.2.9\n\n### List of plugins\n\nJust SkinsRestorer\n\n### Java Version\n\nNo access, I am using a hosting service\n\n### Does your issue require a plugin in order to reproduce?\n\nNone", "state": "CLOSED", "created_at": "2023-04-02T07:37:24Z", "closed_at": "2023-06-14T17:19:42Z", "author_login": "", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 1251, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/Stellarium_stellarium_633.json b/scrape_out/issues/Stellarium_stellarium_633.json
new file mode 100644
index 0000000000000000000000000000000000000000..3e85946e445cbc5d9b0369a553acf5a35471342e
--- /dev/null
+++ b/scrape_out/issues/Stellarium_stellarium_633.json
@@ -0,0 +1 @@
+{"number": 633, "title": "Eta Carinae should be labeled with a name.", "body": "**Is your feature request related to a problem? Please describe.**\r\nEta Carinae is an important star, but it is not labeled with a name.\r\n**Describe the solution you'd like**\r\nEta Carinae should be labeled with a name. It is HR 4210, HD 93308\r\n\r\n\r\n**Additional context**\r\nAdd any other context or screenshots about the feature request here.\r\n\r\n", "state": "CLOSED", "created_at": "2019-02-18T15:40:48Z", "closed_at": "2025-01-13T15:12:14Z", "author_login": "sunshuwei", "comment_rounds": [{"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDQ2NDc4MjA1MA==", "body": "Eta Carinae hasn't HIP designation and we cannot add any labels to any stars without HIP designations currently. ", "createdAt": "2019-02-18T15:45:00Z", "updatedAt": "2019-02-18T15:45:00Z", "author": {"login": "alex-w"}}, {"id": "MDEyOklzc3VlQ29tbWVudDQ2NTEzNDUzMQ==", "body": "I guess the same is true. Why can't use another catalog as an alternatives?", "createdAt": "2019-02-19T13:49:39Z", "updatedAt": "2019-02-19T13:49:39Z", "author": {"login": "sunshuwei"}}, {"id": "MDEyOklzc3VlQ29tbWVudDQ2NTE0NTE2Mg==", "body": "The star catalog and cross-referencing uses Hipparcos as only key reference because HIP was by far the best reference 15 years ago and is (well, almost!) complete with reasonably bright stars. Replacing the star catalog is a major undertaking, which should happen within the next 5 years or so for various reasons. Astrometry has a new gold mine with Gaia data, which however does not contain bright stars. Somebody needs to take the time for developing an efficient data storage format for stars.", "createdAt": "2019-02-19T14:17:57Z", "updatedAt": "2019-02-19T14:17:57Z", "author": {"login": "gzotti"}}]}, {"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDU2MzkwNTY4Ng==", "body": "I think there is another bug. I've noticed that on some occasions, even the brightest stars do not get their name, but only the greek name (\u03b1-boo instead of Arcturus, \u03b1-CMa insteed of Sirius), despite `Name` being set in the Settings>Information>Displayed fields dialog.\r\n\r\nIt's as if something happens in parallel and doesn't complete in time. When I start Stellarium, the first thing I usually do is halt time, and for a while, I had the impression that doing this too quickly contributed to this glitch (although I see no immediate reason for this). I inspected the log but saw no suspect warnings (\"loaded .* star names\"). When this happens, I cannot find the star either, e.g. the Find dialog does not show Sirius.\r\n\r\nThis also resembles #831 ", "createdAt": "2019-12-10T07:35:45Z", "updatedAt": "2019-12-10T07:35:45Z", "author": {"login": "axd1967"}}]}, {"comments": [{"id": "IC_kwDOAR2kcM6To6Fe", "body": "As a temporary solution the designation for \u03b7 Car star has been added via Missing Stars plugin", "createdAt": "2024-11-14T17:08:36Z", "updatedAt": "2024-11-14T17:08:52Z", "author": {"login": "alex-w"}}]}, {"comments": [{"id": "IC_kwDOAR2kcM6T_XOz", "body": "\n\nHello @sunshuwei!\n\nPlease check the fresh version (development snapshot) of Stellarium:\nhttps://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot\n\n\n", "createdAt": "2024-11-18T12:09:11Z", "updatedAt": "2024-11-18T12:09:11Z", "author": {"login": "github-actions"}}]}, {"comments": [{"id": "IC_kwDOAR2kcM6epHNU", "body": "\n\nHello @sunshuwei!\n\nPlease check the fresh version (development snapshot) of Stellarium:\nhttps://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot\n\n\n", "createdAt": "2025-02-16T19:18:07Z", "updatedAt": "2025-02-16T19:18:07Z", "author": {"login": "github-actions"}}]}, {"comments": [{"id": "IC_kwDOAR2kcM6jse16", "body": "\n\nHello @sunshuwei!\n\nPlease check the latest stable version of Stellarium:\nhttps://github.com/Stellarium/stellarium/releases/latest\n\n\n", "createdAt": "2025-03-23T18:08:36Z", "updatedAt": "2025-03-23T18:08:36Z", "author": {"login": "github-actions"}}]}], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 8, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "state: confirmed", "data", "subsystem: catalogs"], "milestone": "25.1", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/ThreeSixtyGiving_datastore_246.json b/scrape_out/issues/ThreeSixtyGiving_datastore_246.json
new file mode 100644
index 0000000000000000000000000000000000000000..a4d10c9ea504f0e6e128e90bac234650bb98178c
--- /dev/null
+++ b/scrape_out/issues/ThreeSixtyGiving_datastore_246.json
@@ -0,0 +1 @@
+{"number": 246, "title": "Quality Dashboard shows > 100% org IDs", "body": "[By grants view](https://qualitydashboard.threesixtygiving.org/alldata#grants) showing 108% Includes at least one charity or company no. I expect this should always add up to < 100%\n\n", "state": "CLOSED", "created_at": "2024-12-13T09:46:26Z", "closed_at": "2024-12-16T14:35:37Z", "author_login": "mariongalley", "comment_rounds": [{"comments": [{"id": "IC_kwDOC9QAvM6XeSqK", "body": "Via David:\r\n> This is probably actually a bug in the datastore, specifically this code which generates the data for the data quality dashboard: https://github.com/ThreeSixtyGiving/datastore/blob/live/datastore/data_quality/quality_data.py", "createdAt": "2024-12-13T10:01:53Z", "updatedAt": "2024-12-13T10:01:53Z", "author": {"login": "mariongalley"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 247, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/UniversityOfSaskatchewanCMPT371_term-project-2024-team-2_22.json b/scrape_out/issues/UniversityOfSaskatchewanCMPT371_term-project-2024-team-2_22.json
new file mode 100644
index 0000000000000000000000000000000000000000..66703ee0b361606b9c96d2691f21a31c3d9bfb72
--- /dev/null
+++ b/scrape_out/issues/UniversityOfSaskatchewanCMPT371_term-project-2024-team-2_22.json
@@ -0,0 +1 @@
+{"number": 22, "title": "Implement backend data exclusion for rows with missing data", "body": "When a row has a piece of data missing from the row, exclude it. This should be relegated to a back-end operation that filters out incomplete rows before sending them to the UI", "state": "CLOSED", "created_at": "2024-01-19T23:47:28Z", "closed_at": "2024-03-02T18:01:25Z", "author_login": "matthew-buglass", "comment_rounds": [], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["High Priority"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/Zettlr_Zettlr_5949.json b/scrape_out/issues/Zettlr_Zettlr_5949.json
new file mode 100644
index 0000000000000000000000000000000000000000..61a0b0e7d5533f5427bf113f982d5d1aa218a8d3
--- /dev/null
+++ b/scrape_out/issues/Zettlr_Zettlr_5949.json
@@ -0,0 +1 @@
+{"number": 5949, "title": "Zettlr Crashes on Start With Symlinks in Directory Tree", "body": "### Description\n\nJust had a bug (on the most recent develop branch) where I added a softlink (`ln -s source target`) into the directory tree for Zettlr, and subsequently I couldn't start Zettlr. The start was aborted with an error that the app couldn't load the main window. This is spurious because it was certainly caused by the symlink (it worked again after removing the symlink), but somehow the actual error got swallowed in the boot process.\n\n### Reproducing\n\nHave a symlink in your loaded workspaces.\n\n### Zettlr version\n\ndevelop\n\n### Installation Method\n\nFrom the Website or GitHub\n\n### Installation Method (Other)\n\n_No response_\n\n### Your Platform\n\n- [ ] Windows\n- [x] macOS\n- [ ] Linux\n\n### Architecture\n\n- [ ] Intel 64bit\n- [x] ARM 64bit (includes Apple Silicon)\n\n### Operating System Version\n\nTahoe\n\n### Additional Information\n\n_No response_", "state": "CLOSED", "created_at": "2025-10-15T17:34:29Z", "closed_at": "2025-12-19T13:51:16Z", "author_login": "nathanlesage", "comment_rounds": [{"comments": [{"id": "IC_kwDOBuGRQc7QBPUo", "body": "Still not fixed with the most recent FSAL rewrite.", "createdAt": "2025-11-05T08:49:57Z", "updatedAt": "2025-11-05T08:49:57Z", "author": {"login": "nathanlesage"}}]}], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/ansible-collections_vmware.vmware_361.json b/scrape_out/issues/ansible-collections_vmware.vmware_361.json
new file mode 100644
index 0000000000000000000000000000000000000000..a6f2bdfaa27a15598082263d4e154a3fbdb8dc5a
--- /dev/null
+++ b/scrape_out/issues/ansible-collections_vmware.vmware_361.json
@@ -0,0 +1 @@
+{"number": 361, "title": "Add adjustable timeout for vm_snapshot module", "body": "\n\n\n##### SUMMARY\n\nCurrently, vmware.vmware.vm_snapshot can delete a snapshot, but after 1 hour it reports a failure, even if vCenter is still deleting the snapshot.\n\n##### ISSUE TYPE\n- Feature Idea\nAdd a parameter to allow for extending this timeout in the Ansible module so it could wait as long as the user defines before marking the task as failed\n\n##### COMPONENT NAME\n\nvmware.vmware.vm_snapshot\n\n##### ADDITIONAL INFORMATION\n\n\n\n```yaml\n - name: Call vCenter API to remove guest snapshot\n vmware.vmware.vm_snapshot:\n hostname: \"{{ vmware_info.vcenter }}\"\n username: \"{{ hostvars[vmware_info.vcenter].vcenter_user }}\"\n password: \"{{ hostvars[vmware_info.vcenter].vcenter_password }}\"\n validate_certs: \"{{ hostvars[vmware_info.vcenter].vmware_validate_certs }}\"\n datacenter: \"{{ vmware_info.datacenter }}\"\n moid: \"{{ vmware_info.vmoid }}\"\n snapshot_name: \"{{ snapshot_name }}\"\n description: \"{{ description | default(omit) }}\"\n state: absent\n delegate_to: localhost\n```\n\nAfter 1 hour, task marked as Failed\n`msg: Timeout waiting for running task to complete in VMWare invocation:`\nSnapshot delete completed in 1 hour and 10 minutes successfully in vCenter\n\n", "state": "CLOSED", "created_at": "2026-05-27T14:39:38Z", "closed_at": "2026-05-28T16:52:07Z", "author_login": "MallocArray", "comment_rounds": [{"comments": [{"id": "IC_kwDOLPpI4c8AAAABD5agiQ", "body": "At first glance, I think it would be fairly simple to add a timeout parameter and use it here:\n\nhttps://github.com/ansible-collections/vmware.vmware/blob/c6f67f2b59a0d89289e4ebd271ad2b2ce13a2ae7/plugins/modules/vm_snapshot.py#L379-L380\n\nIt looks like `wait_for_completion` expects the timeout in seconds and has a default of 3600 / 1 hour:\n\nhttps://github.com/ansible-collections/vmware.vmware/blob/c6f67f2b59a0d89289e4ebd271ad2b2ce13a2ae7/plugins/module_utils/_vsphere_tasks.py#L38\n\nIf we define a default of 3600 for timeout it wouldn't even be breaking, just a new feature. @mikemorency @p3ck What do you think? I could try and knock something up if you want me to. \n\nNote to myself: vm_powerstate", "createdAt": "2026-05-27T16:28:13Z", "updatedAt": "2026-05-27T16:28:13Z", "author": {"login": "mariolenz"}}, {"id": "IC_kwDOLPpI4c8AAAABD6ieTw", "body": "Yea, that seems like a good approach to me. Thanks @mariolenz ", "createdAt": "2026-05-27T18:53:41Z", "updatedAt": "2026-05-27T18:53:41Z", "author": {"login": "mikemorency"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 362, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/apecloud_kubeblocks_6005.json b/scrape_out/issues/apecloud_kubeblocks_6005.json
new file mode 100644
index 0000000000000000000000000000000000000000..b4a9c1d8a13a33cb72abe67c7dfe2f6750eec22a
--- /dev/null
+++ b/scrape_out/issues/apecloud_kubeblocks_6005.json
@@ -0,0 +1 @@
+{"number": 6005, "title": "[Features] support the custom opsrequest for the databases", "body": "**What is the user interaction of your feature**\r\n Some database engines have already encapsulated many operational tasks, making them highly convenient to use. \r\nWhile DBAs may have accumulated operational expertise. \r\n\r\nbut using these operations in Kubeblocks might be more complex.\r\nCould an API be provided to integrate these operational tasks into opsRequest, allowing execution through opsRequest? \r\n\r\n", "state": "CLOSED", "created_at": "2023-12-06T06:34:38Z", "closed_at": "2023-12-08T03:15:23Z", "author_login": "wangyelei", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 5940, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["kind/feature", "area/user-interaction", "feature", "documentation"], "milestone": "Release 0.8.0", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/assume-framework_assume_321.json b/scrape_out/issues/assume-framework_assume_321.json
new file mode 100644
index 0000000000000000000000000000000000000000..32d3d0b23d36baf3dbb08f95a41449c8371db4f4
--- /dev/null
+++ b/scrape_out/issues/assume-framework_assume_321.json
@@ -0,0 +1 @@
+{"number": 321, "title": "Improve performance by switching from pandas to numpy", "body": "During my recent studies I found ASSUME to be very slow when simulating a whole year.\nOne way to improve this is by switching towards daily market clearing instead of hourly, but it still takes a while.\nWhen looking into the code which takes a lot of time I found pandas to often be the case:\n\n## Act 1: Profiling Benchmarks\n\ndue to various reasons, cProfile does not give good timings when running async code.\nMore correct timings can be seen using `yappi` (pip install yappi) - https://github.com/sumerc/yappi\nSo one can run `yappi -o \"out.profile\" assume_cli/cli.py` and then use `tuna` (pip install tuna) to visualize the profiling result:\n`tuna out.profile`.\nThis gives theses visual charts like shown below.\nThe results are therefore equally to running `assume -s example01a -c base`. This run takes 88s on my laptop.\nProbably ~20s are spent organizing asyncio-stuff\n~60s is spent in pandas\n~3s on imports\n~ rest on other stuff\n\ncalculate_bids boils down to take time in pandas\n\n\nhandling market_feedback spends a lot of time in pandas too - nearly all the site-packages stuff is spend in pandas \n\n\nwriting outputs spends most of its time in pandas too\n\n\nThough one can not see that much due to the long lines - I could not find a way to remove the absolute paths from the pictures..\n\n## Act 2: Alternatives\nSo I thought how one can replace pandas.\nOur requirements includes slicing, indexing by datetime and having multiple series.\nAfter experimenting with [modin](https://github.com/modin-project/modin) and [dask](https://github.com/dask/dask)\nI could not use modin as a drop in replacement and dask did not seem like a good solution either, as we spend a lot of time in the initialization of dataframes and not in the heavy lifting.\n\nI came up with good old numpy, which supports slicing. But can only have an array with the same types.\nSo a datetime index is not possible.\n\nI thought about having a convenience wrapper - something like this:\n\n```python\ndef idx_from_date(date):\n return (date-start)//freq\n\ndef numpy_dt_indexer(data, fr, to):\n from_idx = idx_from_date(fr)\n to_idx = idx_from_date(to)\n return data[from_idx:to_idx]\n```\n\nAfter all, it turns out, that switching to numpy is at least 40x faster than pandas.\nI really hope, that this is also the case when switching the main parts of the simulation to it.\n\n## Act 3\n\nImplementation\nTBD", "state": "CLOSED", "created_at": "2024-03-12T15:37:37Z", "closed_at": "2024-11-25T15:44:40Z", "author_login": "maurerle", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 483, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "priority: low"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/assume-framework_assume_678.json b/scrape_out/issues/assume-framework_assume_678.json
new file mode 100644
index 0000000000000000000000000000000000000000..7828e6665a7b71a7de72caf9630ca491cc8a81ab
--- /dev/null
+++ b/scrape_out/issues/assume-framework_assume_678.json
@@ -0,0 +1 @@
+{"number": 678, "title": "Colab Notebooks: conflicting naming of forecasts and forecaster", "body": "Since we introduced per unit forecasters in https://github.com/assume-framework/assume/pull/660 the file assume.common.forecasts was renamed to \"forecaster.py\".\nThis leads to an import error when running Colab Notebooks, where we first do pip install (current version 0.5.5, having \"forecasts.py\" as name of the file) and then git clone our repository (having \"forecaster.py\" as filename).\n\nOne solution woul be to install from the cloned repo instead of pypi:\n```\nif IN_COLAB:\n !git clone --depth=1 https://github.com/assume-framework/assume.git assume-repo\n !pip install -e assume-repo\n```\nBut maybe it makes more sense for users to use the pypi install?\nIt seems quite unintuitive for me to clone a whole repository and then mix it with pip install. But I have no good idea on how to organize this in a way, that helps to avoid such errors. -> discussion needed\n\nError occured in Notebooks: 03, 04a. Potentially affected: all Notebooks", "state": "CLOSED", "created_at": "2025-11-12T14:18:16Z", "closed_at": "2026-03-11T09:04:07Z", "author_login": "gugrimm", "comment_rounds": [{"comments": [{"id": "IC_kwDOJYuvt87SMxA3", "body": "Historically, the fix to such issues is to do a release.\nBut installing the local checked out files would make sense as well and ensure that the correct development state is used, as the ipynb should always work with the source code of the repo.\n@jrasko what do you think?", "createdAt": "2025-11-13T08:56:40Z", "updatedAt": "2025-11-13T08:56:40Z", "author": {"login": "maurerle"}}, {"id": "IC_kwDOJYuvt87SfmCH", "body": "The only reason for this renaming was to prevent conflicts while tinkering locally with both old and new forecasters. Now that we didged the old forecasters, we can easily rename the forcaster back to forecasts.\n\nHowever, simple renamings shouldn't create collisions, therefore I'm also in favour of the local installation of the latest dev state. \n", "createdAt": "2025-11-14T08:13:26Z", "updatedAt": "2025-11-14T08:13:26Z", "author": {"login": "jrasko"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 690, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["priority: medium"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/athanorlabs_atomic-swap_337.json b/scrape_out/issues/athanorlabs_atomic-swap_337.json
new file mode 100644
index 0000000000000000000000000000000000000000..4ebf2b6ed092390d585d178c47d63a0ea1f6fb98
--- /dev/null
+++ b/scrape_out/issues/athanorlabs_atomic-swap_337.json
@@ -0,0 +1 @@
+{"number": 337, "title": "relayer data dir issues", "body": "### How {ENV} for the data-dir is determined (flag vs chain-ID)\r\n\r\nThe relayer's default value for `--data-dir`, as shown in the help, is `{HOME}/.atomicswap/{ENV}`. This left me confused, as I couldn't find the `--env` flag for the relayer. I had to dig through the code to determine that the value of ENV is derived from the chain ID of the ethereum endpoint.\r\n\r\nOptions to make our tools consistent:\r\n(1) Add an `--env` flag to the relayer and validate that the chain ID of the ethereum endpoint matches the environment. (Current behavior of `swapd`.)\r\n(2) Remove the `--env` flag from `swapd` and derive it from the chain ID of the ethereum endpoint. (Current behavior of the `realyer`.)\r\n\r\n### Avoiding `relayer`/`swapd` conflicts\r\n\r\nAfter determining what `{ENV}` was for the `relayer`, I was then confused as to the ETH private key location. The help says it is in `{DATA_DIR}/eth.key`, which converts to `{HOME}/.atomicswap/{ENV}/eth.key` if you didn't pass a `--data-dir` flag. This is the same location as `swapd`'s key, which had me concerned, as swapd and the relayer can't share the same key for nonce synchronization reasons. Digging through the code, I realized that the help lied, and that the default data-dir for the relayer is actually `{HOME}/.atomicswap/{ENV}/relayer` making this another inconsistency between our tools.\r\n\r\nHere are some possible pairs that would make our data-dir locations consistent between programs:\r\n1. `{HOME}/.atomicswap/{ENV}/relayer`\r\n`{HOME}/.atomicswap/{ENV}/swapd`\r\n1. `{HOME}/.atomicswap/relayer/{ENV}`\r\n`{HOME}/.atomicswap/swapd/{ENV}`\r\n1. `{HOME}/.atomic/{ENV}/swapd`\r\n`{HOME}/.atomic/{ENV}/relayer`\r\n1. `{HOME}/.atomic/swapd/{ENV}`\r\n`{HOME}/.atomic/relayer/{ENV}`", "state": "CLOSED", "created_at": "2023-03-02T00:54:52Z", "closed_at": "2023-03-17T19:22:18Z", "author_login": "dimalinux", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 342, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/azerothcore_azerothcore-wotlk_8097.json b/scrape_out/issues/azerothcore_azerothcore-wotlk_8097.json
new file mode 100644
index 0000000000000000000000000000000000000000..6dcc4cfb03ecc54ca961e83f5d64227b2a086758
--- /dev/null
+++ b/scrape_out/issues/azerothcore_azerothcore-wotlk_8097.json
@@ -0,0 +1 @@
+{"number": 8097, "title": "[Warrior] Cleave does not interact with Sweeping Strikes", "body": "### Current Behaviour\n\nCleave is supposed to consume one(extra) Sweeping Strikes, effectively striking the 2 Cleaved targets twice. Currently it behaves like an autoattack/every other ability. It will consume a SS stack and do the Cleave, but the secondary cleaved target will not result in triggering another SS(originated from the secondary target)\n\n### Expected Blizzlike Behaviour\n\nCleave is supposed to consume 2 SS stacks, being treated as 2 attacks(one one the main target, one of the secondary target). Therefore, one attack will trigger SS, that SS damaging the secondary target and, the other attack, on secondary target, will trigger another SS, that SS damaging the Primary target.\n\n### Source\n\n* You can see it here like a ripple effect on the secondary target. There are 2 sources of damage on the main target and no other ability than Cleave being cast https://www.youtube.com/watch?v=JaAR8vkGNeY&t=9s. This is because the secondary target being hit by Cleave will also trigger a SS originating from itself, sweeping back the main target\n* In sims you can see the behaviour more clearly. One Cleave was used during SS(and one on last stack). It shows SS did damage once to Target 1 and once to Target 2:\n\nWhen Cleave was used on last stack, it only procced the said last stack and it only damaged Target 2(Target 1 hit from Cleave procced the SS, but Target 2 hit from Cleave had no SS charge to proc):\n\n* Here he talks about \"4 chances to crit\" refering to the 4 sits of Cleave + SS: https://www.lurkerlounge.com/forums/thread-6241.html \n\n* https://vanilla-wow-archive.fandom.com/wiki/Sweeping_Strikes\n\n\n\n### Steps to reproduce the problem\n\n1. Get Sweeping Strikes\n2. Cleave 2 targets\n\n### Extra Notes\n\nUsing Glyph of Cleave, should result in 3 expanses of SS stacks, equivalent to doing 3 attacks(1st on main, 2nd on secondary, 3rd on tertiary) and each of those will attack nearest target(through SS cleaves), resulting in 6 attacks(3 of cleave + extra SS of the secondary + extra of SS of the tertiary). Note that if any of the secondary or tertiary targets was missed/dodged/parried, it should not expand SS stack and not do damage through it, as it the case with the main target.\n\n\n\n### AC rev. hash/commit\n\nhttps://github.com/chromiecraft/azerothcore-wotlk/commit/a20576dc8c4916791e7830f18ef6c3ca528e29a9\n\n\n### Operating system\n\nUbuntu 22.04\n\n\n### Modules\n\n- [mod-1v1-arena](https://github.com/azerothcore/mod-1v1-arena)\n- [mod-ah-bot](https://github.com/azerothcore/mod-ah-bot)\n- [mod-anticheat](https://github.com/azerothcore/mod-anticheat)\n- [mod-arena-3v3-solo-queue](https://github.com/azerothcore/mod-arena-3v3-solo-queue)\n- [mod-arena-replay](https://github.com/azerothcore/mod-arena-replay)\n- [mod-bg-item-reward](https://github.com/azerothcore/mod-bg-item-reward)\n- [mod-breaking-news-override](https://github.com/azerothcore/mod-breaking-news-override)\n- [mod-cfbg](https://github.com/azerothcore/mod-cfbg)\n- [mod-chat-transmitter](https://github.com/azerothcore/mod-chat-transmitter)\n- [mod-chromie-xp](https://github.com/azerothcore/mod-chromie-xp)\n- [mod-costumes](https://github.com/azerothcore/mod-costumes)\n- [mod-cta-switch](https://github.com/azerothcore/mod-cta-switch)\n- [mod-desertion-warnings](https://github.com/azerothcore/mod-desertion-warnings)\n- [mod-dmf-switch](https://github.com/azerothcore/mod-dmf-switch)\n- [mod-duel-reset](https://github.com/azerothcore/mod-duel-reset)\n- [mod-eluna](https://github.com/azerothcore/mod-eluna)\n- [mod-instanced-worldbosses](https://github.com/nyeriah/mod-instanced-worldbosses)\n- [mod-ip-tracker](https://github.com/azerothcore/mod-ip-tracker)\n- [mod-low-level-arena](https://github.com/azerothcore/mod-low-level-arena)\n- [mod-low-level-rbg](https://github.com/azerothcore/mod-low-level-rbg)\n- [mod-multi-client-check](https://github.com/azerothcore/mod-multi-client-check)\n- [mod-npc-spectator](https://github.com/gozzim/mod-npc-spectator)\n- [mod-progression-system](https://github.com/azerothcore/mod-progression-system)\n- [mod-pvp-titles](https://github.com/azerothcore/mod-pvp-titles)\n- [mod-pvpstats-announcer](https://github.com/azerothcore/mod-pvpstats-announcer)\n- [mod-queue-list-cache](https://github.com/azerothcore/mod-queue-list-cache)\n- [mod-rdf-expansion](https://github.com/azerothcore/mod-rdf-expansion)\n- [mod-transmog](https://github.com/azerothcore/mod-transmog)\n- [mod-weekend-xp](https://github.com/azerothcore/mod-weekend-xp)\n- [mod-zone-difficulty](https://github.com/azerothcore/mod-zone-difficulty)\n- [lua-CarbonCopy](https://github.com/55Honey/Acore_CarbonCopy)\n- [lua-eventScripts](https://github.com/55Honey/Acore_eventScripts)\n- [lua-ExchangeNpc](https://github.com/55Honey/Acore_ExchangeNpc)\n- [lua-LevelUpReward](https://github.com/55Honey/Acore_LevelUpReward)\n- [lua-RecruitAFriend](https://github.com/55Honey/Acore_RecruitAFriend)\n- [lua-SendAndBind](https://github.com/55Honey/Acore_SendAndBind)\n- [lua-TempAnnouncements](https://github.com/55Honey/Acore_TempAnnouncements)\n- [lua-Zonecheck](https://github.com/55Honey/acore_Zonecheck)\n\n\n### Customizations\n\nNone\n\n\n### Server\n\nChromieCraft\n", "state": "CLOSED", "created_at": "2025-06-20T14:22:43Z", "closed_at": "2026-02-18T11:32:09Z", "author_login": "vvranceanu", "comment_rounds": [], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["Confirmed", "ChromieCraft Generic", "Loot"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/buildbot_buildbot_8063.json b/scrape_out/issues/buildbot_buildbot_8063.json
new file mode 100644
index 0000000000000000000000000000000000000000..9bafaa4bdcae160be500a610f34a47b7db8794b8
--- /dev/null
+++ b/scrape_out/issues/buildbot_buildbot_8063.json
@@ -0,0 +1 @@
+{"number": 8063, "title": "No worker Actions buttons in 4.0.3", "body": "As said in https://github.com/buildbot/buildbot/discussions/8010 the worker actions button seems to be missing from the workers page and the specific worker pages; see attached screenshots and configuration.\r\n\r\nTested on:\r\n\r\nUbuntu 22.04 (Python 3.10.12)\r\nbuildbot 4.0.3\r\nVivaldi 6.9.3447.44-1\r\nFirefox 130.0\r\n\r\n[packages.txt](https://github.com/user-attachments/files/17186952/packages.txt)\r\n\r\n\r\n\r\n", "state": "CLOSED", "created_at": "2024-09-30T08:54:26Z", "closed_at": "2024-09-30T19:52:24Z", "author_login": "fraca7", "comment_rounds": [{"comments": [{"id": "IC_kwDOAAuZZc6OAzSr", "body": "Forgot to mention: the buildbot configuration itself is the basic master.cfg.example generated by create-master", "createdAt": "2024-09-30T09:14:37Z", "updatedAt": "2024-09-30T09:14:37Z", "author": {"login": "fraca7"}}, {"id": "IC_kwDOAAuZZc6OBEo0", "body": "https://github.com/buildbot/buildbot/pull/7984 add the Action button to the Workers page.\r\n\r\nStill missing from the specific Worker page.\r\n\r\nIn the mean time, note that the emote in the \"State\" column is clickable and open the dialog that would be open with the Action button.", "createdAt": "2024-09-30T09:47:37Z", "updatedAt": "2024-09-30T09:47:37Z", "author": {"login": "tdesveaux"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 8064, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/canonical_juju-dashboard_1534.json b/scrape_out/issues/canonical_juju-dashboard_1534.json
new file mode 100644
index 0000000000000000000000000000000000000000..956859b548f22a6418c1dd7962ea02ece0368712
--- /dev/null
+++ b/scrape_out/issues/canonical_juju-dashboard_1534.json
@@ -0,0 +1 @@
+{"number": 1534, "title": "Display names of apps when displaying charms in actions panel", "body": "In the applications tab when displaying the list of charms to choose from to perform an action, it would be helpful to list the names of the applications with each radio button option so you can tell which apps the action will be performed on.\r\n\r\n\r\n", "state": "CLOSED", "created_at": "2023-07-17T07:14:22Z", "closed_at": "2023-09-18T09:01:25Z", "author_login": "huwshimi", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 1631, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/cfg-is_cfgms_1771.json b/scrape_out/issues/cfg-is_cfgms_1771.json
new file mode 100644
index 0000000000000000000000000000000000000000..171c00040e8685e8d1f8d8c5b9e6208f45b95ebe
--- /dev/null
+++ b/scrape_out/issues/cfg-is_cfgms_1771.json
@@ -0,0 +1 @@
+{"number": 1771, "title": "security: catch log-injection in flight \u2014 pre-commit lint + dev-agent prompt hardening", "body": "## Goal\nThe dev agent recurrently introduces `Log entries created from user input` CodeQL findings \u2014 most recently 12+ comments on PR #1770. CodeQL only runs in CI, so the agent's local validation (`make test-complete`) never sees them. Catch this class at write time.\n\n## Acceptance Criteria\n- [ ] `scripts/lint-log-injection.sh` exists and flags every PR #1770 finding (`features/controller/api/handlers_registration.go` lines 135, 140, 144, 161, 168, 173, 215, 244, 251)\n- [ ] `make test-commit` runs the new lint and fails on any finding\n- [ ] `scripts/install-git-hooks.sh` installs a pre-commit hook that runs the lint on staged `.go` files only\n- [ ] Dev agent prompt includes a Log Sanitization Checklist that points at `logging.SanitizeLogValue` for HTTP-derived values\n- [ ] Smoke test: running the lint against PR #1770's `handlers_registration.go` returns non-zero with the expected file:line list\n- [ ] `make test` passes on the implementing branch\n\n## Non-Goals\n- Local CodeQL CLI integration (Option C from PO triage) \u2014 out of scope; revisit if grep gate misses real findings\n- Retrofitting existing log calls outside the files lint flags (separate hygiene story)\n\n## Files In Scope\n- `scripts/lint-log-injection.sh`\n- `Makefile`\n- `scripts/install-git-hooks.sh`\n- `.devcontainer/entrypoint.sh`\n\n## Dependencies\nNone.\n\n## PM Notes\nFounder directive 2026-05-22: \"do A&B\" \u2014 A = lint gate, B = agent prompt hardening. Inline implementation on host session.", "state": "CLOSED", "created_at": "2026-05-23T01:06:19Z", "closed_at": "2026-05-24T03:57:39Z", "author_login": "jrdnr", "comment_rounds": [{"comments": [{"id": "IC_kwDONHREOc8AAAABDaHFlw", "body": "Scope expanded mid-implementation: also harden the acceptance reviewer to block on `@github-advanced-security[bot]` findings (CodeQL inline comments, dep alerts, secret scans). Added as Phase 2.1 of `.claude/agents/acceptance-reviewer.md`. Founder directive 2026-05-22.", "createdAt": "2026-05-23T01:16:42Z", "updatedAt": "2026-05-23T01:16:42Z", "author": {"login": "jrdnr"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 1772, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["high-priority", "story"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/destiny-evidence_destiny-repository_718.json b/scrape_out/issues/destiny-evidence_destiny-repository_718.json
new file mode 100644
index 0000000000000000000000000000000000000000..5b3b306c21f5ef71ec5162a91131ac02063dcdd2
--- /dev/null
+++ b/scrape_out/issues/destiny-evidence_destiny-repository_718.json
@@ -0,0 +1 @@
+{"number": 718, "title": "Structured search parameter for country", "body": "## Context \n\nDe-scoped from initial deliverable \n\n## Technical scope \n\ndestiny-repo\n* Add a structured parameter to /references/search to allow searching by country\n * Current scope is that this should only support ISO-2 codes as these are what is projected by our enhancments\n * Use your judgement to decide (a) how to document this limitation, or (b) implement country name conversion for friendlier search requests.\n\nevidence-repo-ui\n* Update the searching to use the structured country filter parameter \n\n", "state": "CLOSED", "created_at": "2026-05-28T01:18:10Z", "closed_at": "2026-05-29T01:40:31Z", "author_login": "jack-o-the-green", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 719, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/dilla-chat_dilla-chat_88.json b/scrape_out/issues/dilla-chat_dilla-chat_88.json
new file mode 100644
index 0000000000000000000000000000000000000000..db0b21fc4f48604060247621c791a9c1db8e1a4c
--- /dev/null
+++ b/scrape_out/issues/dilla-chat_dilla-chat_88.json
@@ -0,0 +1 @@
+{"number": 88, "title": "bug: empty channel list, PMs crash, wide resize handle", "body": "## Bugs found during first-time setup testing\n\n### 1. Channel list empty after bootstrap\nThe bootstrap creates a \"general\" channel (confirmed in DB) but the Kanals tab shows nothing. The client likely doesn't fetch channels after bootstrap or the WebSocket sync:init doesn't fire.\n\n### 2. PMs tab crashes with infinite re-render\nClicking the \"PMs\" tab causes: `Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate.`\n\n### 3. Resize handle between sidebar and main content is too wide\nThe draggable divider (cyan/teal bar) is visually much wider than expected \u2014 should be a thin 4-6px handle, not a full bar.\n\n## Steps to reproduce\n1. Fresh server: `rm -rf data && cargo run -- --insecure`\n2. Create identity at `/create-identity`\n3. Bootstrap at `/setup?token=...`\n4. Observe empty channel list\n5. Click \"PMs\" tab \u2192 crash\n6. Note wide resize handle between sidebar and content area\n\n## Environment\n- macOS, Chrome/Firefox\n- Vite dev server on port 8888, server on port 8080", "state": "CLOSED", "created_at": "2026-03-25T18:20:27Z", "closed_at": "2026-03-28T07:20:10Z", "author_login": "jonasthim", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 89, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/dstackai_dstack_3757.json b/scrape_out/issues/dstackai_dstack_3757.json
new file mode 100644
index 0000000000000000000000000000000000000000..4b1f4264160f55a275d25f0412fd72cbe71e9aa6
--- /dev/null
+++ b/scrape_out/issues/dstackai_dstack_3757.json
@@ -0,0 +1 @@
+{"number": 3757, "title": "[Feature]: Kubernetes: volumes support", "body": "### Problem\n\nWhile Kubernetes supports a wide variety of both local and non-local (network) persistent volumes, `dstacks`'s Kubernetes backend lacks any volume support.\n\n### Solution\n\nhttps://docs.google.com/document/d/1RcY9CdeMjxmSF_w9QtzUGx0hqdFEbTaxKMR9IugasT0\n\n### Workaround\n\n_No response_\n\n### Would you like to help us implement this feature by sending a PR?\n\nYes", "state": "CLOSED", "created_at": "2026-04-09T09:41:18Z", "closed_at": "2026-04-16T08:20:13Z", "author_login": "un-def", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 3781, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["feature", "kubernetes"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/equaltoai_lesser_469.json b/scrape_out/issues/equaltoai_lesser_469.json
new file mode 100644
index 0000000000000000000000000000000000000000..16b1f1df247cb390a5ba20e6eb2bf348738508ad
--- /dev/null
+++ b/scrape_out/issues/equaltoai_lesser_469.json
@@ -0,0 +1 @@
+{"number": 469, "title": "[Account Contract][P1.2] Isolate optional extension state from core account hydration", "body": "## Parent Milestone\n\n[[Account Contract][P1] Harden core account hydration and caller boundaries](https://github.com/equaltoai/lesser/issues/467)\n\n## Step\n\nRefactor account repository hydration so core user/account reads are insulated from optional extension-schema drift and can succeed even when governance or other extension payloads evolve.\n\n## Completion Criteria\n\n- core account hydration no longer fails because optional extension payloads changed shape\n- repository code has an explicit isolation boundary between core fields and extension state\n- repository tests cover the hardened behavior with live-shaped agent rows", "state": "CLOSED", "created_at": "2026-03-27T13:13:58Z", "closed_at": "2026-03-27T18:49:00Z", "author_login": "aron23", "comment_rounds": [{"comments": [{"id": "IC_kwDOO16fiM73AYws", "body": "Completed on `aron/account-contract-p1-467` in `26ba9bb8`.\n\nRubric:\n- refactored core account hydration onto explicit `userCoreProjection` and optional `userMetadataProjection` boundaries\n- `GetUser`/`GetAccount` now keep core reads alive even when optional metadata decode fails or evolves\n- updated repository/API/Graph/accounts test harnesses to support the hardened projection path without regressing caller expectations\n\nVerification:\n- `GOTOOLCHAIN=go1.26.1 go test ./pkg/storage/repositories ./pkg/services/accounts ./cmd/api/handlers ./graph -count=1`", "createdAt": "2026-03-27T17:14:28Z", "updatedAt": "2026-03-27T17:14:28Z", "author": {"login": "aron23"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 474, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/equinor_ert_7518.json b/scrape_out/issues/equinor_ert_7518.json
new file mode 100644
index 0000000000000000000000000000000000000000..db82ffe93c7577a2f2fd81357f58d65f791d9cc4
--- /dev/null
+++ b/scrape_out/issues/equinor_ert_7518.json
@@ -0,0 +1 @@
+{"number": 7518, "title": "Fix ruff preview option PLC0415", "body": "**Describe the bug**\r\nRelated to #7377 \r\n\r\n\r\n`````\r\n(py3.10-venv) x86_64 \u279c ert git:(improve-ruff-coverage2) \u2717 ruff rule PLC0415 \r\n# import-outside-top-level (PLC0415)\r\n\r\nDerived from the **Pylint** linter.\r\n\r\nThis rule is in preview and is not stable. The `--preview` flag is required for use.\r\n\r\n## What it does\r\nChecks for `import` statements outside of a module's top-level scope, such\r\nas within a function or class definition.\r\n\r\n## Why is this bad?\r\n[PEP 8] recommends placing imports not only at the top-level of a module,\r\nbut at the very top of the file, \"just after any module comments and\r\ndocstrings, and before module globals and constants.\"\r\n\r\n`import` statements have effects that are global in scope; defining them at\r\nthe top level has a number of benefits. For example, it makes it easier to\r\nidentify the dependencies of a module, and ensures that any invalid imports\r\nare caught regardless of whether a specific function is called or class is\r\ninstantiated.\r\n\r\nAn import statement would typically be placed within a function only to\r\navoid a circular dependency, to defer a costly module load, or to avoid\r\nloading a dependency altogether in a certain runtime environment.\r\n\r\n## Example\r\n```python\r\ndef print_python_version():\r\n import platform\r\n\r\n print(python.python_version())\r\n```\r\n\r\nUse instead:\r\n```python\r\nimport platform\r\n\r\n\r\ndef print_python_version():\r\n print(python.python_version())\r\n```\r\n\r\n[PEP 8]: https://peps.python.org/pep-0008/#imports\r\n`````\r\n", "state": "CLOSED", "created_at": "2024-03-25T09:37:52Z", "closed_at": "2024-04-02T10:21:51Z", "author_login": "jonathan-eq", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 7519, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["improvement", "release-notes:skip"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/equinor_ert_9182.json b/scrape_out/issues/equinor_ert_9182.json
new file mode 100644
index 0000000000000000000000000000000000000000..a04508f1eb143e8569a2f4a6f46338cec97cb67a
--- /dev/null
+++ b/scrape_out/issues/equinor_ert_9182.json
@@ -0,0 +1 @@
+{"number": 9182, "title": "Limit the use of EverestConfig in the Server related function signatures", "body": "", "state": "CLOSED", "created_at": "2024-11-12T09:18:00Z", "closed_at": "2024-11-18T10:14:18Z", "author_login": "DanSava", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 9181, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/etalab_catalogage-donnees_592.json b/scrape_out/issues/etalab_catalogage-donnees_592.json
new file mode 100644
index 0000000000000000000000000000000000000000..2b885cfcd76556295bb6106142bc3d9bea352273
--- /dev/null
+++ b/scrape_out/issues/etalab_catalogage-donnees_592.json
@@ -0,0 +1 @@
+{"number": 592, "title": "Recherche avanc\u00e9e : Affichage des filtres actifs", "body": "## Description\r\n\r\nLes utilisateurs peuvent faire une recherche avanc\u00e9e en filtrant sur diff\u00e9rents champs.\r\n\r\n\r\n\r\nLe fait qu'un filtre est \"actif\", c'est \u00e0 dire qu'une valeur a \u00e9t\u00e9 s\u00e9lectionn\u00e9e sur ce filtre, n'est pas flagrant (voir exemple ci-dessus avec les filtres des champs \"Couverture g\u00e9o\" et \"Format\" qui sont actifs). Pour aider l'utilisateur \u00e0 comprendre la recherche effectu\u00e9e et ses r\u00e9sultats, il serait utile d'afficher la liste des filtres actifs et la valeur s\u00e9lectionn\u00e9e pour chaque filtre.\r\n\r\nCela sera encore plus utile quand plusieurs valeurs pourront \u00eatre s\u00e9lectionn\u00e9es pour chaque filtre (#591).\r\n\r\n## Impl\u00e9mentation frontend\r\n\r\nLa liste des filtres actifs doit s'afficher au-dessus de l'accord\u00e9on.\r\n\r\nDans l'accord\u00e9on, les filtres actifs doivent \u00eatre surlign\u00e9s de la m\u00eame couleur que dans la liste au-dessus.\r\n\r\n\r\n\r\n[Voir maquette](https://www.figma.com/file/42KOPuvkD1jpubEe2mMtXr/DATALOGUE-maquettes?node-id=2373-38010)", "state": "CLOSED", "created_at": "2023-03-23T11:56:38Z", "closed_at": "2023-05-04T08:35:46Z", "author_login": "johanricher", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 597, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/fiaisis_frontend_323.json b/scrape_out/issues/fiaisis_frontend_323.json
new file mode 100644
index 0000000000000000000000000000000000000000..51ea6f773473f40b0fdf81a26a8116807f474b5f
--- /dev/null
+++ b/scrape_out/issues/fiaisis_frontend_323.json
@@ -0,0 +1 @@
+{"number": 323, "title": "Add a \"Apply settings\" button", "body": "", "state": "CLOSED", "created_at": "2024-10-08T12:16:57Z", "closed_at": "2024-10-24T14:12:16Z", "author_login": "Dagonite", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 303, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": [{"number": 293, "title": "[EPIC] Instrument job config page epic", "state": "CLOSED"}]}
\ No newline at end of file
diff --git a/scrape_out/issues/frankbria_codeframe_330.json b/scrape_out/issues/frankbria_codeframe_330.json
new file mode 100644
index 0000000000000000000000000000000000000000..cd856ba6a353e054bcd6412701d62c2c62840cdc
--- /dev/null
+++ b/scrape_out/issues/frankbria_codeframe_330.json
@@ -0,0 +1 @@
+{"number": 330, "title": "[Phase 3] PRD View - Document Creation & Discovery", "body": "## Overview\nImplement the PRD View for creating, viewing, and iterating on Product Requirements Documents with AI-powered Socratic discovery.\n\n**Reference:** `docs/PHASE_3_UI_ARCHITECTURE.md` Section 1.2, 3.2, 5.1\n\n## Purpose\nCreate, view, and iterate on Product Requirements Documents.\n\n## User Actions\n- Upload/paste PRD markdown\n- Start discovery session (Socratic AI conversation)\n- Edit PRD content\n- Generate tasks from PRD\n\n## Components\n```\nPRDView\n\u251c\u2500\u2500 PRDHeader\n\u2502 \u251c\u2500\u2500 PRDTitle (editable inline)\n\u2502 \u251c\u2500\u2500 PRDActions\n\u2502 \u2502 \u251c\u2500\u2500 UploadPRDButton\n\u2502 \u2502 \u251c\u2500\u2500 StartDiscoveryButton\n\u2502 \u2502 \u2514\u2500\u2500 GenerateTasksButton\n\u2502 \u2514\u2500\u2500 PRDMetadata (version, file path)\n\u251c\u2500\u2500 PRDContent (two-column when discovery active)\n\u2502 \u251c\u2500\u2500 MarkdownEditor (left, or full-width when no discovery)\n\u2502 \u2514\u2500\u2500 DiscoveryPanel (right, collapsible)\n\u2502 \u251c\u2500\u2500 DiscoveryTranscript (chat-style messages)\n\u2502 \u2514\u2500\u2500 DiscoveryInput (text input + send button)\n\u2514\u2500\u2500 AssociatedTasksSummary\n \u2514\u2500\u2500 TaskCountByStatus (compact badges)\n```\n\n## API Endpoints Used\n- `GET /api/v2/prd` - Get current PRD\n- `POST /api/v2/prd` - Create/update PRD\n- `POST /api/v2/discovery/start` - Start discovery session\n- `POST /api/v2/discovery/respond` - Send discovery response\n- `POST /api/v2/tasks/generate` - Generate tasks from PRD\n\n## Acceptance Criteria\n- [ ] Upload PRD via file picker or paste markdown\n- [ ] Markdown editor with live preview\n- [ ] Start discovery session button launches chat panel\n- [ ] Chat-style discovery with AI avatar/branding\n- [ ] Thinking indicator while AI generates responses\n- [ ] Discovery panel slides in from right\n- [ ] \"Skip discovery\" option to write PRD manually\n- [ ] Generate tasks button (enabled when PRD exists)\n- [ ] Shows associated task counts by status\n- [ ] Responsive two-column layout during discovery\n\n## Route\n- `/prd` - PRD editor\n- `/prd/discovery` - Discovery session sub-view\n\n## Real-time Requirements\n- SSE for discovery session responses (streaming AI replies)", "state": "CLOSED", "created_at": "2026-02-03T23:47:16Z", "closed_at": "2026-02-06T00:14:22Z", "author_login": "frankbria", "comment_rounds": [{"comments": [{"id": "IC_kwDOQDW4hc7lJRpU", "body": "\n\n\n\n\n\n\n\n\n\n\n\n# Plan\n\n## Observations\n\nThe codebase has a well-structured Phase 3 architecture with:\n- **Backend APIs**: Complete v2 endpoints for PRD (`file:codeframe/ui/routers/prd_v2.py`), discovery (`file:codeframe/ui/routers/discovery_v2.py`), and tasks (`file:codeframe/ui/routers/tasks_v2.py`)\n- **Frontend Stack**: Next.js 14 with App Router, React 18, Shadcn/UI components, Tailwind CSS, and Hugeicons\n- **Existing Patterns**: Legacy components (`file:legacy/web-ui/src/components/PRDModal.tsx`, `file:legacy/web-ui/src/components/DiscoveryProgress.tsx`) provide reference implementations but need rebuilding per Phase 3 spec\n- **Streaming Infrastructure**: SSE support via `file:codeframe/core/streaming.py` with EventPublisher for real-time updates\n- **Type System**: Comprehensive TypeScript types in `file:legacy/web-ui/src/types/`\n\n## Approach\n\nFollowing the **Phase 3 UI Architecture** (`file:docs/PHASE_3_UI_ARCHITECTURE.md` Section 3.2), implement the PRD View as a standalone route with integrated discovery session support. The approach prioritizes:\n1. **Component-first development**: Build reusable UI components matching the architecture's component hierarchy\n2. **API integration**: Connect to existing v2 endpoints without backend changes\n3. **Real-time streaming**: Implement SSE for discovery chat responses\n4. **Progressive enhancement**: Start with core functionality (upload/edit PRD), then add discovery, then task generation\n\nThis aligns with the \"golden path\" philosophy\u2014building only what's necessary for the core workflow.\n\n## Implementation Steps\n\n### 1. Create Route Structure\n\n**Create PRD route pages:**\n- Create `file:legacy/web-ui/src/app/prd/page.tsx` for main PRD editor view\n- Create `file:legacy/web-ui/src/app/prd/discovery/page.tsx` for discovery session sub-view (optional, can be handled in main view with state)\n\n**Update Navigation:**\n- Modify `file:legacy/web-ui/src/components/Navigation.tsx` to add PRD navigation link (document icon)\n- Add route to sidebar navigation per architecture Section 2\n\n### 2. Define TypeScript Types\n\n**Create PRD-specific types:**\n- Create `file:legacy/web-ui/src/types/prd.ts` with interfaces:\n - `PrdRecord` (id, workspace_id, title, content, metadata, created_at, version, parent_id, change_summary, chain_id)\n - `DiscoverySession` (session_id, state, question, answered_count, is_complete)\n - `DiscoveryMessage` (role: 'user' | 'assistant', content, timestamp)\n - `TaskGenerationResult` (task_count, tasks)\n\n**Update API client:**\n- Extend `file:legacy/web-ui/src/lib/api.ts` with `prdV2Api` object containing:\n - `getLatest()` \u2192 GET `/api/v2/prd/latest`\n - `create(content, title?)` \u2192 POST `/api/v2/prd`\n - `update(prdId, content)` \u2192 POST `/api/v2/prd/{id}/versions`\n - `startDiscovery()` \u2192 POST `/api/v2/discovery/start`\n - `submitAnswer(sessionId, answer)` \u2192 POST `/api/v2/discovery/{session_id}/answer`\n - `generatePrd(sessionId)` \u2192 POST `/api/v2/discovery/{session_id}/generate-prd`\n - `generateTasks(prdId?)` \u2192 POST `/api/v2/discovery/generate-tasks`\n\n### 3. Build Core Components\n\n**Component hierarchy per architecture Section 3.2:**\n\n#### PRDView (Main Container)\n- Create `file:legacy/web-ui/src/components/prd/PRDView.tsx`\n- State management: PRD content, discovery session, task summary\n- Layout: Responsive grid (single column default, two-column when discovery active)\n- Integrate all child components\n\n#### PRDHeader\n- Create `file:legacy/web-ui/src/components/prd/PRDHeader.tsx`\n- Components:\n - **PRDTitle**: Inline editable title (contentEditable or input field)\n - **PRDActions**: Button group with Upload, Start Discovery, Generate Tasks\n - **PRDMetadata**: Display version, file path, timestamps\n- Use Shadcn Button, Input components\n\n#### PRDContent\n- Create `file:legacy/web-ui/src/components/prd/PRDContent.tsx`\n- Two-column layout using CSS Grid or Flexbox\n- Left pane: MarkdownEditor (full-width when discovery inactive)\n- Right pane: DiscoveryPanel (collapsible, slides in from right)\n\n#### MarkdownEditor\n- Create `file:legacy/web-ui/src/components/prd/MarkdownEditor.tsx`\n- Use `react-markdown` (already in dependencies) for live preview\n- Split view: Textarea for editing + rendered preview\n- Debounced auto-save to prevent excessive API calls\n- Syntax highlighting for code blocks via Shiki (mentioned in architecture)\n\n#### DiscoveryPanel\n- Create `file:legacy/web-ui/src/components/prd/DiscoveryPanel.tsx`\n- Collapsible panel with slide-in animation (Tailwind transitions)\n- Contains DiscoveryTranscript and DiscoveryInput\n- Close button to collapse panel\n\n#### DiscoveryTranscript\n- Create `file:legacy/web-ui/src/components/prd/DiscoveryTranscript.tsx`\n- Chat-style message list (similar to `file:legacy/web-ui/src/components/ChatInterface.tsx`)\n- Message bubbles: User (right-aligned, primary color) vs AI (left-aligned, muted)\n- AI avatar/branding icon (use Hugeicons)\n- Auto-scroll to bottom on new messages\n- Thinking indicator: Animated dots while AI generates response\n\n#### DiscoveryInput\n- Create `file:legacy/web-ui/src/components/prd/DiscoveryInput.tsx`\n- Textarea with send button\n- Character count indicator (max 10,000 per API)\n- Keyboard shortcut: Ctrl+Enter to submit\n- Disabled state while waiting for AI response\n\n#### AssociatedTasksSummary\n- Create `file:legacy/web-ui/src/components/prd/AssociatedTasksSummary.tsx`\n- Compact badge display showing task counts by status\n- Use Shadcn Badge component\n- Format: \"READY: 5 | IN_PROGRESS: 2 | DONE: 8\"\n- Click to navigate to `/tasks` view (future enhancement)\n\n### 4. Implement Upload/Paste PRD Flow\n\n**UploadPRDModal:**\n- Create `file:legacy/web-ui/src/components/prd/UploadPRDModal.tsx`\n- Shadcn Dialog component\n- Two tabs: File Upload | Paste Markdown\n- File upload: Accept `.md` files, read content via FileReader API\n- Paste: Textarea for direct markdown input\n- Validation: Check content length, markdown format\n- On submit: Call `prdV2Api.create()`, update PRDView state\n\n### 5. Implement Discovery Session Flow\n\n**State management in PRDView:**\n- Track discovery session state: `idle | discovering | completed`\n- Store session_id, messages array, current question\n- Use SWR for polling discovery status (optional, prefer SSE)\n\n**Start Discovery:**\n- Button click \u2192 Call `prdV2Api.startDiscovery()`\n- Response contains session_id and first question\n- Slide in DiscoveryPanel from right (CSS transform transition)\n- Display first question in DiscoveryTranscript\n\n**Answer Submission:**\n- User types answer \u2192 Click send or Ctrl+Enter\n- Show thinking indicator (animated dots)\n- Call `prdV2Api.submitAnswer(sessionId, answer)`\n- Response contains:\n - `accepted`: boolean (if false, show feedback)\n - `next_question`: Next question or null if complete\n - `is_complete`: boolean\n- Append user message and AI response to transcript\n- If complete, show \"Generate PRD\" button\n\n**SSE Streaming (Optional Enhancement):**\n- For streaming AI responses, implement SSE client\n- Connect to `/api/v2/discovery/{session_id}/stream` (if endpoint exists)\n- Display partial responses as they arrive (typewriter effect)\n\n### 6. Implement PRD Generation from Discovery\n\n**Generate PRD Button:**\n- Enabled when discovery session is complete\n- Click \u2192 Call `prdV2Api.generatePrd(sessionId)`\n- Show loading spinner with progress message\n- Response contains prd_id, title, preview\n- Fetch full PRD via `prdV2Api.getLatest()`\n- Populate MarkdownEditor with generated content\n- Collapse DiscoveryPanel, show success toast\n\n**Skip Discovery Option:**\n- \"Skip Discovery\" button in DiscoveryPanel header\n- Closes panel, allows manual PRD writing\n- User can start discovery later if needed\n\n### 7. Implement Task Generation\n\n**Generate Tasks Button:**\n- Located in PRDHeader actions\n- Enabled when PRD exists (content not empty)\n- Click \u2192 Call `prdV2Api.generateTasks()`\n- Show loading modal with progress indicator\n- Response contains task_count and task list\n- Update AssociatedTasksSummary with counts\n- Show success toast: \"Generated X tasks\"\n- Optionally navigate to `/tasks` view\n\n### 8. Add Real-time Updates\n\n**SSE Integration for Discovery:**\n- Create `file:legacy/web-ui/src/hooks/useDiscoveryStream.ts` custom hook\n- Connect to SSE endpoint when discovery session active\n- Listen for events:\n - `discovery_question_ready`: New question available\n - `discovery_completed`: Session finished\n - `prd_generation_started`: PRD generation began\n - `prd_generation_completed`: PRD ready\n- Update component state based on events\n\n**WebSocket Integration (Alternative):**\n- Reuse existing WebSocket client from `file:legacy/web-ui/src/lib/websocket.ts`\n- Subscribe to discovery events for project\n- Handle same event types as SSE\n\n### 9. Styling and Responsiveness\n\n**Tailwind CSS Classes:**\n- Use existing Shadcn/UI theme variables (bg-card, text-foreground, border-border)\n- Two-column layout: `grid grid-cols-1 lg:grid-cols-2 gap-4`\n- Discovery panel slide-in: `transform transition-transform duration-300 translate-x-0 lg:translate-x-full`\n- Markdown preview: `prose prose-sm max-w-none` (Tailwind Typography)\n\n**Mobile Responsiveness:**\n- Stack columns vertically on mobile\n- Discovery panel becomes full-screen overlay on small screens\n- Collapsible sections for better mobile UX\n\n### 10. Error Handling and Loading States\n\n**Error Boundaries:**\n- Wrap PRDView in ErrorBoundary component\n- Display user-friendly error messages for API failures\n- Retry buttons for transient errors\n\n**Loading States:**\n- Skeleton loaders for PRD content while fetching\n- Spinner for discovery answer submission\n- Progress bar for PRD/task generation\n- Disabled states for buttons during operations\n\n**Validation:**\n- Client-side validation for answer length (1-10,000 chars)\n- Markdown syntax validation (optional, warn on invalid syntax)\n- Prevent duplicate submissions (debounce, disable button)\n\n### 11. Testing Considerations\n\n**Component Tests:**\n- Test PRDView rendering with different states (idle, discovering, completed)\n- Test MarkdownEditor editing and preview\n- Test DiscoveryPanel message display and submission\n- Mock API calls using MSW (already in dependencies)\n\n**Integration Tests:**\n- Test full discovery flow: start \u2192 answer questions \u2192 generate PRD\n- Test upload PRD flow\n- Test task generation from PRD\n\n**E2E Tests (Future):**\n- Full user journey from discovery to task generation\n\n### 12. Documentation\n\n**Update Architecture Docs:**\n- Document component structure in `file:docs/PHASE_3_UI_ARCHITECTURE.md`\n- Add screenshots/wireframes to docs\n\n**Code Comments:**\n- JSDoc comments for all components and functions\n- Inline comments for complex logic (SSE handling, state management)\n\n**README Updates:**\n- Add PRD View to feature list\n- Document discovery workflow for users\n\n---\n\n## Component Dependency Graph\n\n```mermaid\ngraph TD\n A[PRDView] --> B[PRDHeader]\n A --> C[PRDContent]\n A --> D[AssociatedTasksSummary]\n \n B --> E[PRDTitle]\n B --> F[PRDActions]\n B --> G[PRDMetadata]\n \n F --> H[UploadPRDButton]\n F --> I[StartDiscoveryButton]\n F --> J[GenerateTasksButton]\n \n C --> K[MarkdownEditor]\n C --> L[DiscoveryPanel]\n \n L --> M[DiscoveryTranscript]\n L --> N[DiscoveryInput]\n \n H --> O[UploadPRDModal]\n \n style A fill:#e1f5ff\n style C fill:#fff4e1\n style L fill:#ffe1f5\n```\n\n## Discovery Session Flow\n\n```mermaid\nsequenceDiagram\n participant User\n participant PRDView\n participant API\n participant AI\n \n User->>PRDView: Click \"Start Discovery\"\n PRDView->>API: POST /api/v2/discovery/start\n API->>AI: Initialize session\n AI-->>API: First question\n API-->>PRDView: {session_id, question}\n PRDView->>PRDView: Show DiscoveryPanel\n \n loop Answer Questions\n User->>PRDView: Type answer + submit\n PRDView->>API: POST /api/v2/discovery/{id}/answer\n API->>AI: Validate & process answer\n AI-->>API: Next question or completion\n API-->>PRDView: {accepted, next_question, is_complete}\n PRDView->>PRDView: Update transcript\n end\n \n User->>PRDView: Click \"Generate PRD\"\n PRDView->>API: POST /api/v2/discovery/{id}/generate-prd\n API->>AI: Synthesize PRD from answers\n AI-->>API: Generated PRD content\n API-->>PRDView: {prd_id, title, content}\n PRDView->>PRDView: Populate MarkdownEditor\n PRDView->>PRDView: Collapse DiscoveryPanel\n```\n\n## File Structure\n\n```\nlegacy/web-ui/src/\n\u251c\u2500\u2500 app/\n\u2502 \u2514\u2500\u2500 prd/\n\u2502 \u251c\u2500\u2500 page.tsx # Main PRD route\n\u2502 \u2514\u2500\u2500 discovery/\n\u2502 \u2514\u2500\u2500 page.tsx # Discovery sub-route (optional)\n\u251c\u2500\u2500 components/\n\u2502 \u251c\u2500\u2500 Navigation.tsx # Update with PRD link\n\u2502 \u2514\u2500\u2500 prd/\n\u2502 \u251c\u2500\u2500 PRDView.tsx # Main container\n\u2502 \u251c\u2500\u2500 PRDHeader.tsx # Header with actions\n\u2502 \u251c\u2500\u2500 PRDContent.tsx # Two-column layout\n\u2502 \u251c\u2500\u2500 MarkdownEditor.tsx # Editor + preview\n\u2502 \u251c\u2500\u2500 DiscoveryPanel.tsx # Collapsible chat panel\n\u2502 \u251c\u2500\u2500 DiscoveryTranscript.tsx # Message list\n\u2502 \u251c\u2500\u2500 DiscoveryInput.tsx # Answer input\n\u2502 \u251c\u2500\u2500 AssociatedTasksSummary.tsx # Task count badges\n\u2502 \u2514\u2500\u2500 UploadPRDModal.tsx # Upload/paste modal\n\u251c\u2500\u2500 hooks/\n\u2502 \u2514\u2500\u2500 useDiscoveryStream.ts # SSE hook for discovery\n\u251c\u2500\u2500 lib/\n\u2502 \u2514\u2500\u2500 api.ts # Add prdV2Api methods\n\u2514\u2500\u2500 types/\n \u2514\u2500\u2500 prd.ts # PRD-specific types\n```\n## Import In IDE\n
\n\n\n\n\n\ud83e\udd16 Prompt for AI Agents\n\n~~~markdown\n## Observations\n\nThe codebase has a well-structured Phase 3 architecture with:\n- **Backend APIs**: Complete v2 endpoints for PRD (`file:codeframe/ui/routers/prd_v2.py`), discovery (`file:codeframe/ui/routers/discovery_v2.py`), and tasks (`file:codeframe/ui/routers/tasks_v2.py`)\n- **Frontend Stack**: Next.js 14 with App Router, React 18, Shadcn/UI components, Tailwind CSS, and Hugeicons\n- **Existing Patterns**: Legacy components (`file:legacy/web-ui/src/components/PRDModal.tsx`, `file:legacy/web-ui/src/components/DiscoveryProgress.tsx`) provide reference implementations but need rebuilding per Phase 3 spec\n- **Streaming Infrastructure**: SSE support via `file:codeframe/core/streaming.py` with EventPublisher for real-time updates\n- **Type System**: Comprehensive TypeScript types in `file:legacy/web-ui/src/types/`\n\n## Approach\n\nFollowing the **Phase 3 UI Architecture** (`file:docs/PHASE_3_UI_ARCHITECTURE.md` Section 3.2), implement the PRD View as a standalone route with integrated discovery session support. The approach prioritizes:\n1. **Component-first development**: Build reusable UI components matching the architecture's component hierarchy\n2. **API integration**: Connect to existing v2 endpoints without backend changes\n3. **Real-time streaming**: Implement SSE for discovery chat responses\n4. **Progressive enhancement**: Start with core functionality (upload/edit PRD), then add discovery, then task generation\n\nThis aligns with the \"golden path\" philosophy\u2014building only what's necessary for the core workflow.\n\n## Implementation Steps\n\n### 1. Create Route Structure\n\n**Create PRD route pages:**\n- Create `file:legacy/web-ui/src/app/prd/page.tsx` for main PRD editor view\n- Create `file:legacy/web-ui/src/app/prd/discovery/page.tsx` for discovery session sub-view (optional, can be handled in main view with state)\n\n**Update Navigation:**\n- Modify `file:legacy/web-ui/src/components/Navigation.tsx` to add PRD navigation link (document icon)\n- Add route to sidebar navigation per architecture Section 2\n\n### 2. Define TypeScript Types\n\n**Create PRD-specific types:**\n- Create `file:legacy/web-ui/src/types/prd.ts` with interfaces:\n - `PrdRecord` (id, workspace_id, title, content, metadata, created_at, version, parent_id, change_summary, chain_id)\n - `DiscoverySession` (session_id, state, question, answered_count, is_complete)\n - `DiscoveryMessage` (role: 'user' | 'assistant', content, timestamp)\n - `TaskGenerationResult` (task_count, tasks)\n\n**Update API client:**\n- Extend `file:legacy/web-ui/src/lib/api.ts` with `prdV2Api` object containing:\n - `getLatest()` \u2192 GET `/api/v2/prd/latest`\n - `create(content, title?)` \u2192 POST `/api/v2/prd`\n - `update(prdId, content)` \u2192 POST `/api/v2/prd/{id}/versions`\n - `startDiscovery()` \u2192 POST `/api/v2/discovery/start`\n - `submitAnswer(sessionId, answer)` \u2192 POST `/api/v2/discovery/{session_id}/answer`\n - `generatePrd(sessionId)` \u2192 POST `/api/v2/discovery/{session_id}/generate-prd`\n - `generateTasks(prdId?)` \u2192 POST `/api/v2/discovery/generate-tasks`\n\n### 3. Build Core Components\n\n**Component hierarchy per architecture Section 3.2:**\n\n#### PRDView (Main Container)\n- Create `file:legacy/web-ui/src/components/prd/PRDView.tsx`\n- State management: PRD content, discovery session, task summary\n- Layout: Responsive grid (single column default, two-column when discovery active)\n- Integrate all child components\n\n#### PRDHeader\n- Create `file:legacy/web-ui/src/components/prd/PRDHeader.tsx`\n- Components:\n - **PRDTitle**: Inline editable title (contentEditable or input field)\n - **PRDActions**: Button group with Upload, Start Discovery, Generate Tasks\n - **PRDMetadata**: Display version, file path, timestamps\n- Use Shadcn Button, Input components\n\n#### PRDContent\n- Create `file:legacy/web-ui/src/components/prd/PRDContent.tsx`\n- Two-column layout using CSS Grid or Flexbox\n- Left pane: MarkdownEditor (full-width when discovery inactive)\n- Right pane: DiscoveryPanel (collapsible, slides in from right)\n\n#### MarkdownEditor\n- Create `file:legacy/web-ui/src/components/prd/MarkdownEditor.tsx`\n- Use `react-markdown` (already in dependencies) for live preview\n- Split view: Textarea for editing + rendered preview\n- Debounced auto-save to prevent excessive API calls\n- Syntax highlighting for code blocks via Shiki (mentioned in architecture)\n\n#### DiscoveryPanel\n- Create `file:legacy/web-ui/src/components/prd/DiscoveryPanel.tsx`\n- Collapsible panel with slide-in animation (Tailwind transitions)\n- Contains DiscoveryTranscript and DiscoveryInput\n- Close button to collapse panel\n\n#### DiscoveryTranscript\n- Create `file:legacy/web-ui/src/components/prd/DiscoveryTranscript.tsx`\n- Chat-style message list (similar to `file:legacy/web-ui/src/components/ChatInterface.tsx`)\n- Message bubbles: User (right-aligned, primary color) vs AI (left-aligned, muted)\n- AI avatar/branding icon (use Hugeicons)\n- Auto-scroll to bottom on new messages\n- Thinking indicator: Animated dots while AI generates response\n\n#### DiscoveryInput\n- Create `file:legacy/web-ui/src/components/prd/DiscoveryInput.tsx`\n- Textarea with send button\n- Character count indicator (max 10,000 per API)\n- Keyboard shortcut: Ctrl+Enter to submit\n- Disabled state while waiting for AI response\n\n#### AssociatedTasksSummary\n- Create `file:legacy/web-ui/src/components/prd/AssociatedTasksSummary.tsx`\n- Compact badge display showing task counts by status\n- Use Shadcn Badge component\n- Format: \"READY: 5 | IN_PROGRESS: 2 | DONE: 8\"\n- Click to navigate to `/tasks` view (future enhancement)\n\n### 4. Implement Upload/Paste PRD Flow\n\n**UploadPRDModal:**\n- Create `file:legacy/web-ui/src/components/prd/UploadPRDModal.tsx`\n- Shadcn Dialog component\n- Two tabs: File Upload | Paste Markdown\n- File upload: Accept `.md` files, read content via FileReader API\n- Paste: Textarea for direct markdown input\n- Validation: Check content length, markdown format\n- On submit: Call `prdV2Api.create()`, update PRDView state\n\n### 5. Implement Discovery Session Flow\n\n**State management in PRDView:**\n- Track discovery session state: `idle | discovering | completed`\n- Store session_id, messages array, current question\n- Use SWR for polling discovery status (optional, prefer SSE)\n\n**Start Discovery:**\n- Button click \u2192 Call `prdV2Api.startDiscovery()`\n- Response contains session_id and first question\n- Slide in DiscoveryPanel from right (CSS transform transition)\n- Display first question in DiscoveryTranscript\n\n**Answer Submission:**\n- User types answer \u2192 Click send or Ctrl+Enter\n- Show thinking indicator (animated dots)\n- Call `prdV2Api.submitAnswer(sessionId, answer)`\n- Response contains:\n - `accepted`: boolean (if false, show feedback)\n - `next_question`: Next question or null if complete\n - `is_complete`: boolean\n- Append user message and AI response to transcript\n- If complete, show \"Generate PRD\" button\n\n**SSE Streaming (Optional Enhancement):**\n- For streaming AI responses, implement SSE client\n- Connect to `/api/v2/discovery/{session_id}/stream` (if endpoint exists)\n- Display partial responses as they arrive (typewriter effect)\n\n### 6. Implement PRD Generation from Discovery\n\n**Generate PRD Button:**\n- Enabled when discovery session is complete\n- Click \u2192 Call `prdV2Api.generatePrd(sessionId)`\n- Show loading spinner with progress message\n- Response contains prd_id, title, preview\n- Fetch full PRD via `prdV2Api.getLatest()`\n- Populate MarkdownEditor with generated content\n- Collapse DiscoveryPanel, show success toast\n\n**Skip Discovery Option:**\n- \"Skip Discovery\" button in DiscoveryPanel header\n- Closes panel, allows manual PRD writing\n- User can start discovery later if needed\n\n### 7. Implement Task Generation\n\n**Generate Tasks Button:**\n- Located in PRDHeader actions\n- Enabled when PRD exists (content not empty)\n- Click \u2192 Call `prdV2Api.generateTasks()`\n- Show loading modal with progress indicator\n- Response contains task_count and task list\n- Update AssociatedTasksSummary with counts\n- Show success toast: \"Generated X tasks\"\n- Optionally navigate to `/tasks` view\n\n### 8. Add Real-time Updates\n\n**SSE Integration for Discovery:**\n- Create `file:legacy/web-ui/src/hooks/useDiscoveryStream.ts` custom hook\n- Connect to SSE endpoint when discovery session active\n- Listen for events:\n - `discovery_question_ready`: New question available\n - `discovery_completed`: Session finished\n - `prd_generation_started`: PRD generation began\n - `prd_generation_completed`: PRD ready\n- Update component state based on events\n\n**WebSocket Integration (Alternative):**\n- Reuse existing WebSocket client from `file:legacy/web-ui/src/lib/websocket.ts`\n- Subscribe to discovery events for project\n- Handle same event types as SSE\n\n### 9. Styling and Responsiveness\n\n**Tailwind CSS Classes:**\n- Use existing Shadcn/UI theme variables (bg-card, text-foreground, border-border)\n- Two-column layout: `grid grid-cols-1 lg:grid-cols-2 gap-4`\n- Discovery panel slide-in: `transform transition-transform duration-300 translate-x-0 lg:translate-x-full`\n- Markdown preview: `prose prose-sm max-w-none` (Tailwind Typography)\n\n**Mobile Responsiveness:**\n- Stack columns vertically on mobile\n- Discovery panel becomes full-screen overlay on small screens\n- Collapsible sections for better mobile UX\n\n### 10. Error Handling and Loading States\n\n**Error Boundaries:**\n- Wrap PRDView in ErrorBoundary component\n- Display user-friendly error messages for API failures\n- Retry buttons for transient errors\n\n**Loading States:**\n- Skeleton loaders for PRD content while fetching\n- Spinner for discovery answer submission\n- Progress bar for PRD/task generation\n- Disabled states for buttons during operations\n\n**Validation:**\n- Client-side validation for answer length (1-10,000 chars)\n- Markdown syntax validation (optional, warn on invalid syntax)\n- Prevent duplicate submissions (debounce, disable button)\n\n### 11. Testing Considerations\n\n**Component Tests:**\n- Test PRDView rendering with different states (idle, discovering, completed)\n- Test MarkdownEditor editing and preview\n- Test DiscoveryPanel message display and submission\n- Mock API calls using MSW (already in dependencies)\n\n**Integration Tests:**\n- Test full discovery flow: start \u2192 answer questions \u2192 generate PRD\n- Test upload PRD flow\n- Test task generation from PRD\n\n**E2E Tests (Future):**\n- Full user journey from discovery to task generation\n\n### 12. Documentation\n\n**Update Architecture Docs:**\n- Document component structure in `file:docs/PHASE_3_UI_ARCHITECTURE.md`\n- Add screenshots/wireframes to docs\n\n**Code Comments:**\n- JSDoc comments for all components and functions\n- Inline comments for complex logic (SSE handling, state management)\n\n**README Updates:**\n- Add PRD View to feature list\n- Document discovery workflow for users\n\n---\n\n## Component Dependency Graph\n\n```mermaid\ngraph TD\n A[PRDView] --> B[PRDHeader]\n A --> C[PRDContent]\n A --> D[AssociatedTasksSummary]\n \n B --> E[PRDTitle]\n B --> F[PRDActions]\n B --> G[PRDMetadata]\n \n F --> H[UploadPRDButton]\n F --> I[StartDiscoveryButton]\n F --> J[GenerateTasksButton]\n \n C --> K[MarkdownEditor]\n C --> L[DiscoveryPanel]\n \n L --> M[DiscoveryTranscript]\n L --> N[DiscoveryInput]\n \n H --> O[UploadPRDModal]\n \n style A fill:#e1f5ff\n style C fill:#fff4e1\n style L fill:#ffe1f5\n```\n\n## Discovery Session Flow\n\n```mermaid\nsequenceDiagram\n participant User\n participant PRDView\n participant API\n participant AI\n \n User->>PRDView: Click \"Start Discovery\"\n PRDView->>API: POST /api/v2/discovery/start\n API->>AI: Initialize session\n AI-->>API: First question\n API-->>PRDView: {session_id, question}\n PRDView->>PRDView: Show DiscoveryPanel\n \n loop Answer Questions\n User->>PRDView: Type answer + submit\n PRDView->>API: POST /api/v2/discovery/{id}/answer\n API->>AI: Validate & process answer\n AI-->>API: Next question or completion\n API-->>PRDView: {accepted, next_question, is_complete}\n PRDView->>PRDView: Update transcript\n end\n \n User->>PRDView: Click \"Generate PRD\"\n PRDView->>API: POST /api/v2/discovery/{id}/generate-prd\n API->>AI: Synthesize PRD from answers\n AI-->>API: Generated PRD content\n API-->>PRDView: {prd_id, title, content}\n PRDView->>PRDView: Populate MarkdownEditor\n PRDView->>PRDView: Collapse DiscoveryPanel\n```\n\n## File Structure\n\n```\nlegacy/web-ui/src/\n\u251c\u2500\u2500 app/\n\u2502 \u2514\u2500\u2500 prd/\n\u2502 \u251c\u2500\u2500 page.tsx # Main PRD route\n\u2502 \u2514\u2500\u2500 discovery/\n\u2502 \u2514\u2500\u2500 page.tsx # Discovery sub-route (optional)\n\u251c\u2500\u2500 components/\n\u2502 \u251c\u2500\u2500 Navigation.tsx # Update with PRD link\n\u2502 \u2514\u2500\u2500 prd/\n\u2502 \u251c\u2500\u2500 PRDView.tsx # Main container\n\u2502 \u251c\u2500\u2500 PRDHeader.tsx # Header with actions\n\u2502 \u251c\u2500\u2500 PRDContent.tsx # Two-column layout\n\u2502 \u251c\u2500\u2500 MarkdownEditor.tsx # Editor + preview\n\u2502 \u251c\u2500\u2500 DiscoveryPanel.tsx # Collapsible chat panel\n\u2502 \u251c\u2500\u2500 DiscoveryTranscript.tsx # Message list\n\u2502 \u251c\u2500\u2500 DiscoveryInput.tsx # Answer input\n\u2502 \u251c\u2500\u2500 AssociatedTasksSummary.tsx # Task count badges\n\u2502 \u2514\u2500\u2500 UploadPRDModal.tsx # Upload/paste modal\n\u251c\u2500\u2500 hooks/\n\u2502 \u2514\u2500\u2500 useDiscoveryStream.ts # SSE hook for discovery\n\u251c\u2500\u2500 lib/\n\u2502 \u2514\u2500\u2500 api.ts # Add prdV2Api methods\n\u2514\u2500\u2500 types/\n \u2514\u2500\u2500 prd.ts # PRD-specific types\n```\n~~~\n\n\n\n---\n\n\n\nExecution Information\n\n**Branch**: [main](https://github.com/frankbria/codeframe/tree/main)\n**Commit**: b2523613fca58e5aa58b1887037cb5096f932c3a\n\n\n\n---\n\n\n\n:bulb: Tips\n\n\n### Supported Commands (Inside Comments)\n- Use `@traycerai generate` to iterate on the previous version of the implementation plan.\n\n### Supported Commands (Inside Description)\n- Add `@traycerai ignore` anywhere in the ticket description to prevent this ticket from being processed.\n- Add `@traycerai branch:` anywhere in the ticket description to specify the target branch for the implementation plan.\n\n### Community\n\n- Join our [Discord Community](https://traycer.ai/discord) to get help, request features, and share feedback.\n- Follow us on [X/Twitter](https://twitter.com/traycerai) for updates and announcements.\n\n\n\n\n\n\n \n\n\n\n \n\n\n> [!WARNING]\n> Something went wrong while processing your request.\n> \n> Reference ID: `8b875f04-0866-42c0-9bb2-ba9718a7c840`\n> \n> Please try again or [contact support](mailto:support@traycer.ai?subject=%5BTICKET-ASSIST%5D%20Failed%20to%20generate%20a%20response%2C%20ID%3A%208b875f04-0866-42c0-9bb2-ba9718a7c840&body=An%20issue%20occurred%20while%20generating%20a%20response.%0A%0AReference%20ID%3A%208b875f04-0866-42c0-9bb2-ba9718a7c840%0AOwner%3A%20frankbria%0ARepository%3A%20codeframe%0ATicket%20Number%3A%20330) if the issue persists, referencing this ID.\n> \n\n", "createdAt": "2026-02-03T23:47:21Z", "updatedAt": "2026-02-05T21:55:46Z", "author": {"login": "traycerai"}}, {"id": "IC_kwDOQDW4hc7lJS9B", "body": "\n\n\n### \ud83d\udcdd CodeRabbit Plan Mode\nGenerate an implementation plan and prompts that you can use with your favorite coding agent.\n\n- [ ] Create Plan\n\n\nExamples\n\n- [Example 1](https://redirect.github.com/coderabbitai/git-worktree-runner/issues/29#issuecomment-3589134556)\n- [Example 2](https://redirect.github.com/coderabbitai/git-worktree-runner/issues/12#issuecomment-3606665167)\n\n\n\n---\n\n\ud83d\udd17 Related PRs\n\nfrankbria/codeframe#194 - Fix PRD generation progress tracking UI [merged]\nfrankbria/codeframe#196 - fix(discovery): Synchronize PRD buttons and fix state persistence on tab revisit [merged]\nfrankbria/codeframe#213 - feat(planning): Add Generate Task Breakdown button to DiscoveryProgress [merged]\nfrankbria/codeframe#214 - feat(planning): Add TaskReview component for task approval workflow [merged]\nfrankbria/codeframe#317 - feat(cli): add interactive PRD generation via Socratic discovery [merged]\n\n\n\n---\n\n \ud83e\uddea Issue enrichment is currently in open beta.\n\n\nYou can configure auto-planning by selecting labels in the issue_enrichment configuration.\n\nTo disable automatic issue enrichment, add the following to your `.coderabbit.yaml`:\n```yaml\nissue_enrichment:\n auto_enrich:\n enabled: false\n```\n\n\n\ud83d\udcac Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit)!", "createdAt": "2026-02-03T23:48:06Z", "updatedAt": "2026-02-03T23:48:06Z", "author": {"login": "coderabbitai"}}, {"id": "IC_kwDOQDW4hc7l3Gfi", "body": "Revise the implementation plan to not use /legacy/web-ui. All files should be under the /web-ui directory.", "createdAt": "2026-02-05T21:44:09Z", "updatedAt": "2026-02-05T21:44:09Z", "author": {"login": "frankbria"}}, {"id": "IC_kwDOQDW4hc7l3t1U", "body": "## Revised Implementation Plan (corrected file paths)\n\n**All files go under `web-ui/`, NOT `legacy/web-ui/`.** The `legacy/web-ui/` directory contains v1 reference code only.\n\nFull plan document: [`docs/ISSUE_330_PRD_VIEW_PLAN.md`](../docs/ISSUE_330_PRD_VIEW_PLAN.md)\n\n---\n\n### Key Corrections from Previous Plan\n\n1. **Directory**: All paths changed from `legacy/web-ui/src/...` \u2192 `web-ui/src/...`\n2. **Existing patterns**: API client follows the `workspaceApi`/`tasksApi` namespace pattern already in `web-ui/src/lib/api.ts`\n3. **Types**: Extend the existing `web-ui/src/types/index.ts` barrel, add new `web-ui/src/types/prd.ts`\n4. **Icons**: Use `@hugeicons/react` (not lucide-react) per Nova template\n5. **API endpoints**: Verified against actual backend routers (`prd_v2.py`, `discovery_v2.py`)\n\n---\n\n### File Structure\n\n```\nweb-ui/src/\n\u251c\u2500\u2500 app/\n\u2502 \u2514\u2500\u2500 prd/\n\u2502 \u251c\u2500\u2500 page.tsx # Main PRD route\n\u2502 \u2514\u2500\u2500 discovery/\n\u2502 \u2514\u2500\u2500 page.tsx # Discovery sub-route (optional)\n\u251c\u2500\u2500 components/\n\u2502 \u2514\u2500\u2500 prd/\n\u2502 \u251c\u2500\u2500 PRDView.tsx # Main container\n\u2502 \u251c\u2500\u2500 PRDHeader.tsx # Header with actions\n\u2502 \u251c\u2500\u2500 PRDContent.tsx # Two-column layout\n\u2502 \u251c\u2500\u2500 MarkdownEditor.tsx # Editor + preview\n\u2502 \u251c\u2500\u2500 DiscoveryPanel.tsx # Collapsible chat panel\n\u2502 \u251c\u2500\u2500 DiscoveryTranscript.tsx # Message list\n\u2502 \u251c\u2500\u2500 DiscoveryInput.tsx # Answer input\n\u2502 \u251c\u2500\u2500 AssociatedTasksSummary.tsx # Task count badges\n\u2502 \u251c\u2500\u2500 UploadPRDModal.tsx # Upload/paste modal\n\u2502 \u2514\u2500\u2500 index.ts # Barrel export\n\u251c\u2500\u2500 hooks/\n\u2502 \u2514\u2500\u2500 useDiscoveryStream.ts # SSE hook for discovery\n\u251c\u2500\u2500 lib/\n\u2502 \u2514\u2500\u2500 api.ts # Add prdApi + discoveryApi\n\u2514\u2500\u2500 types/\n \u251c\u2500\u2500 index.ts # Re-export prd types\n \u2514\u2500\u2500 prd.ts # PRD-specific types\n```\n\n### API Endpoints (verified)\n\n**PRD** (`/api/v2/prd`):\n| Method | Path | Purpose |\n|--------|------|---------|\n| `GET` | `/api/v2/prd` | List PRDs |\n| `GET` | `/api/v2/prd/latest` | Get latest |\n| `POST` | `/api/v2/prd` | Create PRD |\n| `GET` | `/api/v2/prd/{id}/versions` | Version history |\n| `POST` | `/api/v2/prd/{id}/versions` | New version |\n\n**Discovery** (`/api/v2/discovery`):\n| Method | Path | Purpose |\n|--------|------|---------|\n| `POST` | `/api/v2/discovery/start` | Start session |\n| `GET` | `/api/v2/discovery/status` | Session status |\n| `POST` | `/api/v2/discovery/{session_id}/answer` | Submit answer |\n| `POST` | `/api/v2/discovery/{session_id}/generate-prd` | Generate PRD |\n| `POST` | `/api/v2/discovery/generate-tasks` | Generate tasks |\n\n### Acceptance Criteria Mapping\n\n| Criterion | Component | Step |\n|-----------|-----------|------|\n| Upload PRD via file picker or paste | `UploadPRDModal` | 5 |\n| Markdown editor with live preview | `MarkdownEditor` | 4 |\n| Discovery session launches chat panel | `DiscoveryPanel` | 6 |\n| Chat-style with AI avatar/branding | `DiscoveryTranscript` | 6 |\n| Thinking indicator | `DiscoveryTranscript` | 6 |\n| Discovery panel slides in from right | `DiscoveryPanel` | 6 |\n| \"Skip discovery\" option | `DiscoveryPanel` close button | 6 |\n| Generate tasks button | `PRDHeader` \u2192 `PRDActions` | 7 |\n| Task counts by status | `AssociatedTasksSummary` | 7 |\n| Responsive two-column layout | `PRDContent` | 4 |\n\n### Implementation Order\n\n1. Types + API client (foundation)\n2. PRD route + PRDView shell\n3. PRDHeader + UploadPRDModal\n4. MarkdownEditor\n5. DiscoveryPanel + Transcript + Input\n6. AssociatedTasksSummary + task generation\n7. SSE hook (enhancement)\n8. Navigation sidebar link\n9. Testing", "createdAt": "2026-02-05T22:16:58Z", "updatedAt": "2026-02-05T22:16:58Z", "author": {"login": "frankbria"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 337, "link_type": "closing_keyword", "will_close": true, "comment_count": 4, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["phase-3"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/grafana_grafana_113930.json b/scrape_out/issues/grafana_grafana_113930.json
new file mode 100644
index 0000000000000000000000000000000000000000..d58bc3731230fce4b90def29d03f8310c2cd3794
--- /dev/null
+++ b/scrape_out/issues/grafana_grafana_113930.json
@@ -0,0 +1 @@
+{"number": 113930, "title": "TTRD: Add missing tracking events", "body": "**What would you like to be added**:\n\nThe events that are missing but required for TTRD need to be added. They can be found in the related [design doc](https://docs.google.com/document/d/1dyUi-S_a2PGVz-tPYx_HHEPzmpvSaDubQlFBlrvBftI/edit?tab=t.0#heading=h.frqotpub4g57).", "state": "CLOSED", "created_at": "2025-11-14T13:28:42Z", "closed_at": "2026-03-20T16:09:03Z", "author_login": "L-M-K-B", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 119138, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["area/frontend", "internal"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/grafana_grafana_50665.json b/scrape_out/issues/grafana_grafana_50665.json
new file mode 100644
index 0000000000000000000000000000000000000000..d4afecfdb77e66b2c9223e6dfff2a436b5cbf176
--- /dev/null
+++ b/scrape_out/issues/grafana_grafana_50665.json
@@ -0,0 +1 @@
+{"number": 50665, "title": "LibraryPanels: Change backend permissions to use RBAC", "body": "thought: eventually we'll need to change the implementation here to use something that checks RBAC permissions, similar to `CanCreate` method of dashboard guardian. I feel like it's out of the scope for this PR though, so just sharing my thoughts here.\r\n\r\nCurrently the access checks performed here look at legacy permissions, but from 9.0 role-based access control (RBAC) is enabled by default, so we should check RBAC permissions where possible. \r\n\r\nFrom what I can tell, we haven't decided on what RBAC permissions for library elements will look like. If we're fine reusing dashboard permissions for library elements, the check would look something like this:\r\n\r\n```\r\n\tg := guardian.New(c, cmd.FolderID, signedInUser.OrgId, signedInUser)\r\n\tcanCreate, err := g.CanCreate(cmd.FolderID, false)\r\n\tif err != nil {\r\n\t\treturn err\r\n\t}\r\n\tif !canCreate {\r\n\t\treturn models.ErrFolderAccessDenied\r\n\t}\r\n```\r\n\r\nBut perhaps we want separate actions for library elements \ud83e\udd14 \r\n\r\nSame applies to permission checks carried out from `deleteLibraryElement`, `deleteLibraryElementsInFolderUID` and `handleFolderIDPatches`.\r\n\r\n_Originally posted by @IevaVasiljeva in https://github.com/grafana/grafana/pull/50241#discussion_r895535674_", "state": "CLOSED", "created_at": "2022-06-13T10:12:25Z", "closed_at": "2023-10-11T23:30:52Z", "author_login": "joshhunt", "comment_rounds": [{"comments": [{"id": "IC_kwDOAOaWjc5JZCsh", "body": "\u23f8 On hold: until https://github.com/grafana/grafana/pull/50560", "createdAt": "2022-08-30T08:01:50Z", "updatedAt": "2022-08-30T08:01:50Z", "author": {"login": "axelavargas"}}]}, {"comments": [{"id": "IC_kwDOAOaWjc5OjxsN", "body": "Hi @axelavargas , I can see that #50560 has already been merged, would you happen to have any new updates regarding prioritisation of this issue since you should be unblocked for now? Apologies in advance if my understanding is incorrect. ", "createdAt": "2022-11-17T03:12:48Z", "updatedAt": "2022-11-17T03:12:48Z", "author": {"login": "grafpat"}}]}, {"comments": [{"id": "IC_kwDOAOaWjc5PCagF", "body": "Hi @axelavargas, Just a quick follow-up to see if you have some updates regarding this issue.", "createdAt": "2022-11-24T07:01:07Z", "updatedAt": "2022-11-24T07:01:07Z", "author": {"login": "doanbutar"}}]}, {"comments": [{"id": "IC_kwDOAOaWjc5PNMXD", "body": "Hi @grafpat and @doanbutar \ud83d\udc4b\ud83c\udffe, unfortunately, no update regarding this specific issue, the last thing we did on this domain was this PR:\r\n\r\n- LibraryPanels: Fix issue where viewer with folder edit permissions could not update library panel #58420\r\n\r\nI don't think I can give an ETA for this issue as there are other higher priorities on the team, but as soon as we get it into the near-term planning I'll give you an update.\r\n\r\nThanks for understanding \ud83d\ude4f\ud83c\udffe\r\n\r\ncc, @thanos-karachalios , @natellium ", "createdAt": "2022-11-28T10:35:00Z", "updatedAt": "2022-11-28T10:35:55Z", "author": {"login": "axelavargas"}}]}, {"comments": [{"id": "IC_kwDOAOaWjc5i-U8X", "body": "Here's a question: If a user doesn't have library panel view permissions, but does have permissions to view a dashboard that contains a library panel, what should we do? Maybe just have some sort of information about user permissions where normally the panel contents would be?", "createdAt": "2023-08-01T15:01:48Z", "updatedAt": "2023-08-01T15:01:48Z", "author": {"login": "kaydelaney"}}]}, {"comments": [{"id": "IC_kwDOAOaWjc5lsag7", "body": "@kaydelaney at the moment it shows an error, would make sense to keep it that way I suppose.\r\n\r\n", "createdAt": "2023-09-05T08:07:34Z", "updatedAt": "2023-09-05T08:07:34Z", "author": {"login": "natellium"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 73475, "link_type": "closing_keyword", "will_close": true, "comment_count": 6, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["prio/high", "type/chore", "area/frontend/library-panels", "team/grafana-dashboards", "prio/planned"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/grafana_profiles-drilldown_351.json b/scrape_out/issues/grafana_profiles-drilldown_351.json
new file mode 100644
index 0000000000000000000000000000000000000000..c756a4e5693258724dbe6b71ad73f4bc91af2393
--- /dev/null
+++ b/scrape_out/issues/grafana_profiles-drilldown_351.json
@@ -0,0 +1 @@
+{"number": 351, "title": "[Labels view] Sort label values by their max value", "body": "### Feature description\n\n**Is your feature request related to a problem? Please describe.**\n\nI'm exploring profiles of different pods trying to find examples of goroutine spikes. \n\nThere's no easy way to find them, I just learned that I can click this button _outside_ of the label view:\n\n\n\nBut what I'd really want is to sort the labels by their max value in the presented range.\n\n**Describe the solution you'd like**\n\nIn the label view, i.e. here:\n\n\n\nI would like to be able to sort the values by their max value.\n\n### Alternatives considered\n\n**Describe alternatives you've considered**\n\nLet me run PromQL on that data.\n", "state": "CLOSED", "created_at": "2025-01-24T13:23:35Z", "closed_at": "2025-02-04T10:11:49Z", "author_login": "colega", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 361, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "feature"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/kiwix_kiwix-js_719.json b/scrape_out/issues/kiwix_kiwix-js_719.json
new file mode 100644
index 0000000000000000000000000000000000000000..3e01c6f8103b7c2b21c8b1b71a166746147e9e3e
--- /dev/null
+++ b/scrape_out/issues/kiwix_kiwix-js_719.json
@@ -0,0 +1 @@
+{"number": 719, "title": "Support \"page preview\" feature of Wikipedia and Wikivoyage", "body": "This is a feature that is default for signed-out users of Wikipedia, though signed-in users may need to switch it on. It consists in showing a small preview of the lede, together with an image (if the article has one) when a user hovers over (or long-presses on mobile) an intenal link. It looks like in the screenshot below (the \u00cele-de-France pop-up). It seems to me that this would be quite easy to support in Kiwix JS, especially now that block caching gives us quick lookup capabilities. The equivalent of hovering over a link in mobile is long-press.\r\n\r\nWould this be of interest? An issue might be how to get the target of a hover in SW mode without interfering with the DOM. I think it can be done with a mouseover event listener on the iframe **window** (i.e. above the DOM), from which the target of the event can be retrieved and tested. It would need to run with a suitable timeout delay, so that it is not triggered excessively with each mouse movement, but this is precisely what is required for a hover event. This method would avoid having to attach listeners to each link in the DOM.\r\n\r\n\r\n", "state": "CLOSED", "created_at": "2021-04-10T14:20:12Z", "closed_at": "2024-06-02T14:40:15Z", "author_login": "Jaifroid", "comment_rounds": [{"comments": [{"id": "IC_kwDOAGvj0s468uo5", "body": "Jaifroid, I want to work on this issue. Can you please assign this issue to me", "createdAt": "2021-12-08T17:02:30Z", "updatedAt": "2021-12-08T17:02:30Z", "author": {"login": "Maneet-k"}}, {"id": "IC_kwDOAGvj0s46_ChP", "body": "@Maneet-k Thank you for the offer. However, this issue is a tentative suggestion, and has not been agreed by the active developers on this app. No work should be undertaken until a discussion has been had about the usefulness of the feature and the balance of utility vs the risk of complicating the codebase. This feature, if agreed, is not at all straightforward, and if you are not highly experienced with JavaScript and UI development, then I would suggest you look for a different issue.", "createdAt": "2021-12-09T08:01:47Z", "updatedAt": "2021-12-09T08:01:47Z", "author": {"login": "Jaifroid"}}, {"id": "IC_kwDOAGvj0s46_Dnp", "body": "Ohkayy...... not a problem at all :)\nBut that would be little better if you could give me some suggestion on other issues, if they're open", "createdAt": "2021-12-09T08:08:55Z", "updatedAt": "2021-12-09T08:08:55Z", "author": {"login": "Maneet-k"}}, {"id": "IC_kwDOAGvj0s46_FAz", "body": "Well I don't know your level of experience. If you're prepared to study the source code and look for ways of putting repeated code into a separate function, then #78 might be suitable. But it depends on your interests, knowledge and experience.", "createdAt": "2021-12-09T08:17:18Z", "updatedAt": "2021-12-09T08:17:18Z", "author": {"login": "Jaifroid"}}, {"id": "IC_kwDOAGvj0s46_PuT", "body": "#729 might also be easier than #78 ?", "createdAt": "2021-12-09T09:16:25Z", "updatedAt": "2021-12-09T09:16:25Z", "author": {"login": "mossroy"}}, {"id": "IC_kwDOAGvj0s46_Rig", "body": "That's true. I had assigned that to someone else, but that person has not come back to us and doesn't appear to be working on it.", "createdAt": "2021-12-09T09:25:42Z", "updatedAt": "2021-12-09T09:25:42Z", "author": {"login": "Jaifroid"}}, {"id": "IC_kwDOAGvj0s46_Soc", "body": "Thanks alot @jaifroid and @mossroy for your help. I'll be working on that issue^^", "createdAt": "2021-12-09T09:31:22Z", "updatedAt": "2021-12-09T09:31:22Z", "author": {"login": "Maneet-k"}}, {"id": "IC_kwDOAGvj0s46_Vfe", "body": "Same as https://github.com/kiwix/kiwix-desktop/issues/611 on kiwix-desktop. Really hard ticket, if the \"preview\" is not already pre-computed.", "createdAt": "2021-12-09T09:46:59Z", "updatedAt": "2021-12-09T09:46:59Z", "author": {"login": "kelson42"}}]}, {"comments": [{"id": "IC_kwDOAGvj0s5-UwqT", "body": "This issue has been solved in the PWA, and I have nearly finished backporting the code. Here's what it looks like in KJS browser extension:\r\n\r\n\r\n", "createdAt": "2024-05-19T21:55:52Z", "updatedAt": "2024-05-19T21:55:52Z", "author": {"login": "Jaifroid"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 1252, "link_type": "closing_keyword", "will_close": true, "comment_count": 9, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "user interface"], "milestone": "v4.1", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/lablup_backend.ai-webui_4747.json b/scrape_out/issues/lablup_backend.ai-webui_4747.json
new file mode 100644
index 0000000000000000000000000000000000000000..10b812af018b8124ea6120a089e00ba9f23ec73a
--- /dev/null
+++ b/scrape_out/issues/lablup_backend.ai-webui_4747.json
@@ -0,0 +1 @@
+{"number": 4747, "title": "Remove \"Switch back to the Classic UI\" setting and related Lit components", "body": "## Summary\n\nRemove the \"Switch back to the Classic UI\" setting and related Lit components.\n\n## Context\n\nAfter the removal of the related setting, it is necessary to verify that users who previously switched to the Classic UI are displayed correctly in the NEO UI.\n\n## Acceptance criteria\n\n- The \"Switch back to the Classic UI\" setting must be removed.\n- All related Lit components should be deleted.\n- Verify that users who had previously switched to the Classic UI are now displayed correctly in the NEO UI.\n\n## Other information\n\nN/A\n\n\nJIRA Issue: FR-1757", "state": "CLOSED", "created_at": "2025-12-02T01:25:43Z", "closed_at": "2025-12-16T05:21:46Z", "author_login": "yomybaby", "comment_rounds": [], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/linagora_linid-im-api-community-plugins_32.json b/scrape_out/issues/linagora_linid-im-api-community-plugins_32.json
new file mode 100644
index 0000000000000000000000000000000000000000..da796a185d62816c346b0e64899223f8967b250e
--- /dev/null
+++ b/scrape_out/issues/linagora_linid-im-api-community-plugins_32.json
@@ -0,0 +1 @@
+{"number": 32, "title": "Implement `DatabaseProviderPlugin` (DPB) using jOOQ (PostgreSQL only)", "body": "**Description**\n\nCreate a `DatabaseProviderPlugin` (DPB) responsible for managing relational database access through configurable datasources.\n\nThis plugin must rely on jOOQ for SQL construction and execution.\nAt this stage, only **PostgreSQL** is supported.\n\nThe plugin must integrate with the global YAML configuration model and allow entities to be persisted dynamically based on external configuration, without static entity definitions.\n\nFiltering and pagination logic must not be implemented yet. However, API responses must return structurally valid paginated responses.\n\n---\n\n## Objectives\n\n* Introduce a new provider type: `database`\n* Support PostgreSQL exclusively (initial scope)\n* Use jOOQ for all SQL interactions\n* Allow multiple PostgreSQL providers to be declared\n* Dynamically map entities to tables and attributes to columns\n* Perform basic CRUD operations (initial focus: insert + basic read)\n* Return valid page structures without implementing real pagination\n\n---\n\n## \u26a0\ufe0f Critical Requirement\n\n**A connection pool must be implemented and properly configured.**\n\nThe plugin must not use raw DriverManager connections.\n\nRequirements:\n\n* Use a production-grade connection pool (e.g., HikariCP)\n* One pool per configured provider\n* Proper configuration of:\n\n * maximum pool size\n * idle timeout\n * connection timeout\n * validation query (if needed)\n* Ensure safe lifecycle management (startup / shutdown)\n* Prevent connection leaks\n\nConnection pooling is mandatory for performance, scalability, and resource safety.\n\n---\n\n## Configuration Model\n\nThe plugin must support integration with a global YAML configuration structured as follows:\n\n```yaml\nproviders:\n - name: ExampleDatabase\n type: database\n url: jdbc:postgresql://DATABASE_HOST:DATABASE_PORT/DATABASE_NAME\n username: DATABASE_USER\n password: DATABASE_PASSWORD\n\nentities:\n - name: account\n route: accounts\n provider: ExampleDatabase\n tasks:\n (...)\n access:\n table: ACCOUNT_TABLE_NAME\n attributes:\n - name: id\n type: String\n required: false\n input: Text\n access:\n column: ID_COLUMN_NAME\n```\n\n---\n\n## Technical Requirements\n\n### 1. jOOQ Integration\n\n* Use jOOQ `DSLContext` for all queries\n* Use bind parameters for all values\n* Do not concatenate SQL values directly\n* Use dynamic table and field resolution via `DSL.name(...)`\n* Validate table and column names against configuration before executing queries\n\n---\n\n### 2. PostgreSQL Support (Only)\n\n* The plugin must support PostgreSQL exclusively\n* Use PostgreSQL JDBC driver\n* No abstraction layer for other databases yet\n* Architecture should remain extensible for future RDBMS support\n\n---\n\n### 3. Provider Registration\n\n* Detect providers with `type: database`\n* Initialize a PostgreSQL datasource per provider\n* Attach a dedicated connection pool per provider\n* Support multiple configured PostgreSQL datasources simultaneously\n\n---\n\n### 4. Entity Binding\n\nFor each entity referencing a database provider:\n\n* Resolve target table from `entities[].access.table`\n* Resolve column mappings from `entities[].attributes[].access.column`\n* Allow only declared attributes to be persisted\n* Do not rely on static JPA entities\n* All persistence logic must be dynamic and configuration-driven\n\n---\n\n### 5. Data Operations (Initial Scope)\n\nThe plugin must support:\n\n* Insert operation using dynamic column mapping\n* Basic read operation (select all rows from mapped table)\n\nAll operations must:\n\n* Use jOOQ\n* Use bind parameters\n* Restrict columns to those declared in configuration\n* Avoid runtime SQL injection risks\n\n---\n\n### 6. Pagination Contract (Without Real Pagination)\n\nFiltering and pagination logic must **not** be implemented.\n\nHowever, API responses must return a valid page structure, for example:\n\n```json\n{\n \"content\": [...],\n \"page\": 0,\n \"size\": 20,\n \"totalElements\": X,\n \"totalPages\": 1\n}\n```\n\nFor now:\n\n* `page` defaults to 0\n* `size` defaults to a configured or safe default\n* `totalElements` reflects actual row count\n* `totalPages` may be set to 1\n\nThe response contract must remain forward-compatible with future pagination implementation.\n\n---\n\n## Out of Scope\n\n* Filtering\n* Sorting\n* Real pagination\n* Joins and relationship handling\n* Schema migration management\n* Support for databases other than PostgreSQL\n\n", "state": "CLOSED", "created_at": "2026-03-02T11:21:51Z", "closed_at": "2026-03-26T10:35:28Z", "author_login": "Zorin95670", "comment_rounds": [{"comments": [{"id": "IC_kwDOPKPegs7tdMNF", "body": "### Objective\n\nCreate a **Spring component** (`DslRegistry`) that centrally manages all `DSLContext`s for PostgreSQL providers in the `DatabaseProviderPlugin` (DPB).\nThis component must:\n\n* Provide a **unique `DSLContext` per provider configuration**\n* Manage **connection pools** (`HikariDataSource`) lifecycle\n* Recreate the pool if the provider configuration changes\n* Close all pools cleanly when the Spring application shuts down\n\n---\n\n## 1\ufe0f\u20e3 Core Behavior\n\n* **Class**: `DslRegistry` annotated with `@Component`\n* **Public method**:\n\n```java\n// Store by name the configuration hash\nprivate Map configurations;\n\npublic DSLContext getDsl(ProviderConfiguration config) {\n String key = config.getName();\n String previoushash;\n String currentHash;\n\n synchronized (key.intern()) { // lock by provider name\n DSLContextHolder holder = map.get(key);\n\n if ( previousHash == currentHash) {\n return DSL;\n }\n\n close previous dsl if exists\n recreate pool with HikariDataSource\n return it\n }\n}\n```\n\n* **Internal map**: `Map`\n\n```text\nDSLContextHolder {\n DSLContext dsl;\n HikariDataSource datasource;\n ProviderConfiguration configSnapshot; // used to detect config changes\n}\n```\n\n* The map key = `configuration.getName()` (provider name, considered unique)\n* On each `getDsl` call:\n\n 1. Lock on `key.intern()` \u2192 ensures only **one thread** creates or reloads a DSLContext for the same provider\n 2. Check if DSLContext exists and if the configuration has changed (TODO placeholder)\n 3. If not present or changed \u2192 close old datasource, create new Hikari pool + DSLContext, update map\n 4. Return the DSLContext\n\n---\n\n## 2\ufe0f\u20e3 Pool Management\n\n* Use **HikariCP** for connection pooling\n* Each DSLContext must be tied to its own HikariDataSource\n\nExample creation:\n\n```java\nHikariConfig hikariConfig = new HikariConfig();\nhikariConfig.setJdbcUrl(config.getUrl());\nhikariConfig.setUsername(config.getUsername());\nhikariConfig.setPassword(config.getPassword());\nhikariConfig.setMaximumPoolSize(config.getMaximumPoolSize());\n\nHikariDataSource ds = new HikariDataSource(hikariConfig);\nDSLContext dsl = DSL.using(ds, SQLDialect.POSTGRES);\n```\n\n* Always use **bind parameters** via DSLContext to prevent SQL injection\n\n---\n\n## 3\ufe0f\u20e3 Shutdown Handling\n\n* `DslRegistry` must close all pools on application shutdown\n* Implement Spring `DisposableBean` or annotate a method with `@PreDestroy`:\n\n```java\n@PreDestroy\npublic void shutdown() {\n for (DSLContextHolder holder : map.values()) {\n holder.getDatasource().close();\n }\n}\n```\n\n---\n\n## 4\ufe0f\u20e3 Thread-safety\n\n* Synchronization is per-provider using `key.intern()`\n* Allows concurrent requests for **different providers** without blocking each other\n* Ensures only **one DSLContext** and pool exist per provider at a time\n\n---\n\n## 5\ufe0f\u20e3 Extensibility\n\n* Later, implement the **configuration change check** in the TODO placeholder\n* This pattern can be extended for multiple database types in the future\n* Map of `DSLContextHolder`s allows dynamic reload of pools safely\n\n", "createdAt": "2026-03-02T11:40:09Z", "updatedAt": "2026-03-02T11:51:41Z", "author": {"login": "Zorin95670"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 35, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/loculus-project_loculus_5623.json b/scrape_out/issues/loculus-project_loculus_5623.json
new file mode 100644
index 0000000000000000000000000000000000000000..9e3129f270e55557320f3bc9d64d241d613c7c44
--- /dev/null
+++ b/scrape_out/issues/loculus-project_loculus_5623.json
@@ -0,0 +1 @@
+{"number": 5623, "title": "Multi Segment Submission: Submission of single sequence on edit page without fasta Header uses strange naming", "body": "Discovered here: https://github.com/pathoplexus/pathoplexus/pull/759#issuecomment-3603068608 when testing https://github.com/loculus-project/loculus/pull/5382\n\n\nIf I revise a sequence submission via the edit page and upload a single segment in a file without a header the sequence is initial called `Segment 3` but then after processing is called 6 (it is also downloaded as 6):\n\n", "state": "CLOSED", "created_at": "2025-12-03T16:31:13Z", "closed_at": "2025-12-05T17:35:56Z", "author_login": "anna-parker", "comment_rounds": [{"comments": [{"id": "IC_kwDOJjZkuM7XDih-", "body": "I had noticed this: a) I don't think it's a huge deal b) I'm not sure how easy it would be to fix, I haven't looked at your PR yet but I can imagine a situation where trying to fix this would introduce the possibility of duplicate names in certain circumstances (though that may already be the case). ", "createdAt": "2025-12-03T17:40:06Z", "updatedAt": "2025-12-03T17:40:06Z", "author": {"login": "theosanderson"}}, {"id": "IC_kwDOJjZkuM7XDo6V", "body": "Ah yes thats why I used the key originally - I guess we could call it `Segment key` then - I recall @fengelniederhammer thought we should not just call the files by key as this doesnt look nice", "createdAt": "2025-12-03T17:46:21Z", "updatedAt": "2025-12-04T08:03:47Z", "author": {"login": "anna-parker"}}, {"id": "IC_kwDOJjZkuM7XDqX9", "body": "> (though that may already be the case).\n\nCurrently it isnt possible to have duplicate names as I dont allow for duplicate fastaIds on the edit page\n", "createdAt": "2025-12-03T17:47:45Z", "updatedAt": "2025-12-03T17:47:53Z", "author": {"login": "anna-parker"}}, {"id": "IC_kwDOJjZkuM7XNZHJ", "body": "Yeah I guess I probably think `Unnamed seq a21325f` or something might be the way to go, but we're probs already spending too long on this very niche thing :)", "createdAt": "2025-12-04T07:06:12Z", "updatedAt": "2025-12-04T07:06:12Z", "author": {"login": "theosanderson"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 5632, "link_type": "closing_keyword", "will_close": true, "comment_count": 4, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["multipath"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/logto-io_logto_8190.json b/scrape_out/issues/logto-io_logto_8190.json
new file mode 100644
index 0000000000000000000000000000000000000000..13d8dd0564aa089d481f3239f77e3877a35e6e53
--- /dev/null
+++ b/scrape_out/issues/logto-io_logto_8190.json
@@ -0,0 +1 @@
+{"number": 8190, "title": "feature request: fetch user profile details via WeCom additional APIs", "body": "### What problem did you meet?\n\nWhen using WeCom (\u4f01\u4e1a\u5fae\u4fe1) as a social login provider, the connector only returns basic user identification (userid/openid) but leaves other important profile fields empty:\n- Avatar: empty\n- Email: empty \n- Phone: empty\n- Name: defaults to userid\n\nThis creates a poor user experience because:\n1. Applications cannot display user avatars after WeCom login\n2. User registration forms need manual input for email and phone\n3. Applications lack contact information (email/phone) for communication\n4. User profiles appear incomplete compared to other social connectors\n\nWeCom actually provides additional APIs to fetch this detailed information, but the current connector implementation doesn't utilize them.\n\n### Describe what you'd like Logto to have\n\n would like the WeCom connector to automatically fetch complete user profile data during authentication by:\n\n1. **Calling the user.get API** (`https://qyapi.weixin.qq.com/cgi-bin/user/get`) with the userid to fetch:\n - Name\n - Basic profile information\n\n2. **Calling the auth/getuserdetail API** (`https://qyapi.weixin.qq.com/cgi-bin/auth/getuserdetail`) when user_ticket is available to fetch sensitive data:\n - Email\n - Mobile\n - Avatar\n - Address\n - Gender\n\nThis would make the WeCom connector's behavior consistent with other social connectors and provide complete user profiles out of the box.\n\n**API References:**\n- [Get user basic info](https://developer.work.weixin.qq.com/document/path/90196)\n- [Get user sensitive info](https://developer.work.weixin.qq.com/document/path/95833)\n\n**Note:** I have already implemented and tested this enhancement. Happy to submit a PR once this is confirmed.", "state": "CLOSED", "created_at": "2026-01-09T09:00:15Z", "closed_at": "2026-05-20T03:35:55Z", "author_login": "liyujun-dev", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 8191, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["feature-request"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/mantidproject_mantid_35011.json b/scrape_out/issues/mantidproject_mantid_35011.json
new file mode 100644
index 0000000000000000000000000000000000000000..916a5f6c337e517d56641b2856ee5dd1badc503a
--- /dev/null
+++ b/scrape_out/issues/mantidproject_mantid_35011.json
@@ -0,0 +1 @@
+{"number": 35011, "title": "Minor Sample Transmission Calculator Improvements", "body": "**Describe the bug**\r\n - [ ] A) Missing axes labels on the embedded plot\r\n - [ ] B) Single wavelength: Width is able to be larger than the max\r\n - [ ] C) Multiple wavelength: Only allows odd number of wavelengths without explanation\r\n\r\n**To Reproduce**\r\nA)\r\n1. Open the GUI and check the Axes\r\n\r\nB)\r\n1. Set the min to 1, max to 10, and the width to 12. \r\n2. Enter `H2 O` into the Chemical Formula field\r\n4. Click calculate\r\n5. No points will be present\r\n\r\nC)\r\n1. Select Multiple from the dropdown combobox\r\n2. Enter 1,2,3,4 \r\n3. Click calculate\r\n4. An error will appear\r\n\r\n**Expected behavior**\r\nA) Labels present\r\nB) A warning/error message is shown\r\nC) Explain in the error message why an odd number is required (Needs to be in point, width, point, width, point, etc.)\r\n\r\n**Platform/Version (please complete the following information):**\r\n - OS: All\r\n - Mantid Version : 6.6\r\n", "state": "CLOSED", "created_at": "2023-01-18T16:44:55Z", "closed_at": "2023-08-21T16:37:13Z", "author_login": "cailafinn", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 35930, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["Bug", "Maintenance", "Induction", "ISIS: Core"], "milestone": "Release 6.8", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/martijnversluis_ChordSheetJS_904.json b/scrape_out/issues/martijnversluis_ChordSheetJS_904.json
new file mode 100644
index 0000000000000000000000000000000000000000..65396642aa7d93d68dcf26809dcea85f2df1aa4f
--- /dev/null
+++ b/scrape_out/issues/martijnversluis_ChordSheetJS_904.json
@@ -0,0 +1 @@
+{"number": 904, "title": "Error when serializing chords with comments", "body": "Hello,\r\n\r\nFirst, thanks for this amazing lib, you saved me a lot of time :blush: \r\n\r\nI'm trying to serialize a song (containing comments) that ChordSheetJS has parsed successfully, but I am encountering the following error:\r\n\r\n\r\nHere is the code I'm using:\r\n\r\n```js\r\nconst song = parser.parse(songChordPro);\r\nconst serializedSong = new ChordSheetJS.ChordSheetSerializer().serialize(\r\n song\r\n);\r\n\r\n```\r\nAnd below the content on the file.\r\n\r\n```\r\n# ----------------------------------------------------------------------------\r\n# ANGIE - The Rolling Stones\r\n# ----------------------------------------------------------------------------\r\n{ns}\r\n{define: E7 base-fret 1 frets 0 2 0 1 0 0} \r\n{define: F base-fret 1 frets x x 3 2 1 1} \r\n{t: ANGIE - The Rolling Stones}\r\n{st: (Richards/Jagger)}\r\n{artist: The Rolling Stones}\r\n{composer: Keith Richards; Mick Jagger}\r\n\r\nhttps://www.youtube.com/watch?v=K5_EBAzIPJM (Capo 0)\r\n \r\n\r\n[INTRO:] [Am][,] [E] [E][-][E7][,] [G] [F][;] [F] [C][,] [G] [Am]\r\n\r\nAngie, [E]An [E7]gie, [G]when will those clouds [F]all disappear-[C]er? \r\n[Am]Angie, [E]An [E7]gie, [G]where will it lead [F]us from here-[C]ere?\r\nWith no [G]loving in our souls, and no [Dm]money in our [Am]coats, \r\n[C]You can't [F]say we're satis[G]fied.\r\nBut [Am]Angie, [E]An [E7]gie, [G]you can't [F]say we never tri-[C]ed?\r\n\r\n[Am]Angie, you're [E]beauti[E7]ful, yeah. \r\n[G]But ain't it time we [F]said goodby-[C]eye?\r\n[Am]Angie, I still [E]love [E7]you, \r\n[G]Remember all those [F]nights we cri-[C]ied? \r\n\r\nAll the [G]dreams we held so close, seemed to [Dm]all go up in [Am]smoke. \r\n[C]Let me [F]whisper in your [G]ear: \r\n\"[Am]Angie, [E]Angie, [G]where will it [F]lead us, from here-[C]ere?\"\r\n\r\n[Am] [E] [E7][,] [G] [F] [Dm] [C][;] [Am] [E] [E7][,] [G] [F] [Dm] [C]\r\n\r\nOhhh [G]Angie don't you weep, all your [Dm]kisses still taste [Am]sweet. \r\n[C]I hate that [F]sadness in your [G]eyes. \r\nBut [Am]Angie, [E]An [E7]gie, [G]ain't it [F]time we said goodby-[C]eye?\r\n\r\n[Am] [E] [E7][,] [G] [F] [Dm] [C]\r\n\r\nWith no [G]loving, in our souls, and no [Dm]money in our [Am]coats, \r\n[C]You can't [F]say were satis[G]fied.\r\nBut [Dm]Angie, I still love you [Am]baby. [Dm]Everywhere I look, I see your [Am]eyes.\r\n[Dm]There ain't a woman that comes [Am]close to you. [C]Come on [F]baby dry your [G]eyes.\r\n\r\n[Am]Angie, [E]An [E7]gie, [G]ain't it [F]good to be ali-[C]ive? \r\n \r\n[Am]Angie, [E]An [E7]gie, [G]they can't [F]say we never tri-[C]ied. \r\n\r\n\r\n```\r\n\r\nIf I\u00a0remove the comments\r\n\r\n```\r\n# ----------------------------------------------------------------------------\r\n# ANGIE - The Rolling Stones\r\n# ----------------------------------------------------------------------------\r\n```\r\nEverything works as expected.", "state": "CLOSED", "created_at": "2023-05-27T08:00:16Z", "closed_at": "2023-06-13T09:20:44Z", "author_login": "vjousse", "comment_rounds": [{"comments": [{"id": "IC_kwDOAfAt3M5etPGp", "body": "@vjousse Thanks for reporting this issue \ud83d\udc4d. I just published [`v7.17.1`](https://github.com/martijnversluis/ChordSheetJS/releases/tag/v7.17.1) that addresses this bug.\r\n\r\nPlease let me know if this fixes your issue. ", "createdAt": "2023-06-13T09:34:18Z", "updatedAt": "2023-06-13T09:34:18Z", "author": {"login": "martijnversluis"}}]}, {"comments": [{"id": "IC_kwDOAfAt3M5hMkxF", "body": "Hello @martijnversluis ,\r\nThanks for the fix! Unfortunately, I'm still facing the same issue. Are you sure the `v7.17.1` was correctly published? It seems that it doesn't contain your fix.\r\n\r\nHere is the version I am using from my `yarn.lock` file:\r\n\r\n```\r\nchordsheetjs@^7.17.1:\r\n version \"7.17.1\"\r\n resolved \"https://registry.yarnpkg.com/chordsheetjs/-/chordsheetjs-7.17.1.tgz#7defe9feea0b5b1115d996bed6a1b7a4a8a28f60\"\r\n integrity sha512-K8sBgYNonbaUHs8x7PYhDmkOrg4QS4nr456s8M7KrpBL8iqyzYU0ZZvoANOeAGXdbh95XDEHVs+0BLjxXAT2zA==\r\n dependencies:\r\n lodash.get \"^4.4.2\"\r\n```\r\n\r\nFor example, there is no mention of your new `formatComment` function in the downloaded `.tgz`. Am I missing something?\r\n\r\nHere is my `package.json`:\r\n\r\n```json\r\n{\r\n \"scripts\": {\r\n \"start\": \"parcel html/index.html\",\r\n \"build\": \"parcel build html/index.html\"\r\n },\r\n \"devDependencies\": {\r\n \"@parcel/transformer-elm\": \"2.9.3\",\r\n \"elm\": \"^0.19.1-5\",\r\n \"parcel\": \"^2.9.3\",\r\n \"postcss\": \"^8.4.14\",\r\n \"process\": \"^0.11.10\",\r\n \"tailwindcss\": \"^3.0.24\"\r\n },\r\n \"dependencies\": {\r\n \"chordsheetjs\": \"^7.17.1\"\r\n }\r\n}\r\n```", "createdAt": "2023-07-11T11:53:48Z", "updatedAt": "2023-07-11T11:53:48Z", "author": {"login": "vjousse"}}, {"id": "IC_kwDOAfAt3M5hX6nZ", "body": "Hey @vjousse. You're completely right, for some reason this change did not end up in the release. \r\n\r\nI published `7.17.2` and [tested it using RunKit](https://runkit.com/martijnversluis/chordsheetjs-serialize-comments), so now I know for sure the change is included. \r\n\r\nPlease let me know if it _is_ fixed now \ud83d\ude04 ", "createdAt": "2023-07-13T06:47:53Z", "updatedAt": "2023-07-13T06:47:53Z", "author": {"login": "martijnversluis"}}]}, {"comments": [{"id": "IC_kwDOAfAt3M5hjiDr", "body": "Thanks a lot, it works now! :blush: ", "createdAt": "2023-07-15T08:04:02Z", "updatedAt": "2023-07-15T08:04:02Z", "author": {"login": "vjousse"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 913, "link_type": "closing_keyword", "will_close": true, "comment_count": 4, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/mealie-recipes_mealie_7557.json b/scrape_out/issues/mealie-recipes_mealie_7557.json
new file mode 100644
index 0000000000000000000000000000000000000000..a8b7f7239d2c428d7cd8f091c3b0b386167ffacd
--- /dev/null
+++ b/scrape_out/issues/mealie-recipes_mealie_7557.json
@@ -0,0 +1 @@
+{"number": 7557, "title": "[BUG] - Cannot create new categories/tools/keywords from within a recipe", "body": "### First Check\n\n- [x] This is not a feature request.\n- [x] I added a very descriptive title to this issue (title field is above this).\n- [x] I used the GitHub search to find a similar issue and didn't find it.\n- [x] I searched the Mealie documentation, with the integrated search.\n- [x] I already read the docs and didn't find an answer.\n- [x] This issue can be replicated on the demo site (https://demo.mealie.io/).\n\n### What is the issue you are experiencing?\n\nSo i've updated my docker to the last version of mealie and in the meantime I've migrated from sqlite to postgres (the migration was a bliss). Everything works fine but one part is missing : \n\nWhen I create or edit a recipe, I'm no longer able to add new categories/tool/keyword from the recipe interface (I was able to do that before). I can still add new ingredients or units from the recipe, and i can still add new tools or categories from the dedicated menus.\n\nWhat I expect is what i had before and similar to ingredients, a scrolling menu with a +new/create button : \n\n\n\nWhat I get is a scroll menu without a +new/create button:\n\n\n\n Idk if it's due to my switch to postgres...\n\n\n### Steps to Reproduce\n\nThere is the same issue on the demo site\n\n### Please provide relevant logs\n\nI have no logs\n\n### Mealie Version\n\nVersion: v3.16.0\nBuild: 5fc4851ef5261be3cee131ab17e5532fc4820f14\nApplication mode : production\nDatabase : postgres\nScrapper : 15.11.0\n\n\n### Deployment\n\nOther (please specify below)\n\n### Additional Deployment Details\n\nPodman with quadlet for system-d (essentially docker linux)", "state": "CLOSED", "created_at": "2026-04-28T20:01:51Z", "closed_at": "2026-04-30T15:29:02Z", "author_login": "fritman1", "comment_rounds": [{"comments": [{"id": "IC_kwDOEwYbgs8AAAABAx7R7A", "body": "I'm not sure if this can be called a bug, but it's impractical and illogical.", "createdAt": "2026-04-29T20:32:45Z", "updatedAt": "2026-04-29T20:32:45Z", "author": {"login": "zdenek-stursa"}}, {"id": "IC_kwDOEwYbgs8AAAABAyGSTw", "body": "@zdenek-stursa well before my migration to postgres + update, I'm sure it was possible (like the button existed..., i used it multiple times)... maybe it's a limitation introduced by postgres ? ", "createdAt": "2026-04-29T21:03:40Z", "updatedAt": "2026-04-29T21:04:04Z", "author": {"login": "fritman1"}}, {"id": "IC_kwDOEwYbgs8AAAABAyztNA", "body": "Pretty sure this is a bug, we made some updates to these dropdowns recently", "createdAt": "2026-04-29T23:29:50Z", "updatedAt": "2026-04-29T23:29:50Z", "author": {"login": "michael-genson"}}, {"id": "IC_kwDOEwYbgs8AAAABA0oDEg", "body": "I've prepared PR [#7564](https://github.com/mealie-recipes/mealie/pull/7564)", "createdAt": "2026-04-30T06:22:50Z", "updatedAt": "2026-04-30T06:22:50Z", "author": {"login": "zdenek-stursa"}}, {"id": "IC_kwDOEwYbgs8AAAABA4bXCA", "body": "Thanks a lot !", "createdAt": "2026-04-30T16:12:54Z", "updatedAt": "2026-04-30T16:12:54Z", "author": {"login": "fritman1"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 7564, "link_type": "closing_keyword", "will_close": true, "comment_count": 5, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug", "bug: confirmed"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/msys2_msys2-runtime_24.json b/scrape_out/issues/msys2_msys2-runtime_24.json
new file mode 100644
index 0000000000000000000000000000000000000000..cd22e51504b47120612ca3e425e4997fdd14be2f
--- /dev/null
+++ b/scrape_out/issues/msys2_msys2-runtime_24.json
@@ -0,0 +1 @@
+{"number": 24, "title": "Figure out what to do with msys2-runtime tests in this repo", "body": "It has a copy of the [convert code](https://github.com/msys2/msys2-runtime/blob/msys2-3_3_6-release/winsup/cygwin/msys2_path_conv.cc) and a bunch of [tests](https://github.com/msys2/path_convert/blob/master/src/main.cpp#L169).\r\n\r\nSuggestion:\r\n\r\n* [ ] Make sure the code is in sync with the runtime\r\n* [x] Test against the real runtime somehow, if all fails via a dummy mingw binary that just prints all args and env vars back https://github.com/msys2/msys2-tests/pull/21\r\n* [x] Move the testing code to https://github.com/msys2/msys2-tests, so we run it more often, against staging, and can potentially add more runtime tests https://github.com/msys2/msys2-tests/pull/22\r\n* ~Archive this repo~\r\n", "state": "CLOSED", "created_at": "2022-11-20T18:56:55Z", "closed_at": "2025-04-20T21:54:05Z", "author_login": "lazka", "comment_rounds": [{"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDc1NzY5MzQwMw==", "body": "Sounds like a legit bug. Ideally it should be fixed upstream in cygwin first so I would ask the same question on their mailing list.\r\n\r\nThanks", "createdAt": "2021-01-11T08:14:21Z", "updatedAt": "2021-01-11T08:14:21Z", "author": {"login": "mingwandroid"}}]}], "resolution": "open", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 6, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/netdata_netdata_21373.json b/scrape_out/issues/netdata_netdata_21373.json
new file mode 100644
index 0000000000000000000000000000000000000000..bdb9ed8405fc634c646e0c8de9e1b1f9ef6a51b7
--- /dev/null
+++ b/scrape_out/issues/netdata_netdata_21373.json
@@ -0,0 +1 @@
+{"number": 21373, "title": "[Feat]: add config to set custom telegram api domain", "body": "### Problem\n\npublic telegram api is censored in some countries like mine, adding a custom domain for alerts can help me receive alerts with more trust than using vpn on agents or setting a proxy\n\n### Description\n\nbased on [telegram bot api](https://core.telegram.org/bots/api#using-a-local-bot-api-server) its possible to set another domain for different reasons\nfrom what i see for example in uptime-kuma the reason is telegram is censored in some contries and custom api are the best way to work around it but using proxy and other ways are not always accessible and are problematic\n\n### Importance\n\nreally want\n\n### Value proposition\n\n1. workaround against telegram censorship\n\n### Proposed implementation\n\n_No response_", "state": "CLOSED", "created_at": "2025-12-01T14:10:11Z", "closed_at": "2025-12-01T19:35:09Z", "author_login": "IMIEEET", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 21376, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["feature request", "needs triage"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/nspcc-dev_neofs-node_3968.json b/scrape_out/issues/nspcc-dev_neofs-node_3968.json
new file mode 100644
index 0000000000000000000000000000000000000000..74e963435495faaaff48f61ce89932aad768cadf
--- /dev/null
+++ b/scrape_out/issues/nspcc-dev_neofs-node_3968.json
@@ -0,0 +1 @@
+{"number": 3968, "title": "Panic during searchv2 with one SN down", "body": "```\n2026-04-28T15:44:32.360-0400\tinfo\tcache/clients.go:192\tinitializing connection to the SN...\t{\"scope\": \"read\", \"public key\": \"03fe344aa2409866351c1536cec910528c59f9c2af08f60c62a2e2d22fa7b20c11\", \"address\": \"/dns4/localhost/tcp/53967\"}\npanic: runtime error: invalid memory address or nil pointer dereference\n[signal SIGSEGV: segmentation violation code=0x2 addr=0x18 pc=0x105064a1c]\n\ngoroutine 360 [running]:\ngithub.com/nspcc-dev/neofs-node/pkg/services/object.(*Server).ProcessSearch(0x140002288f0, {0x1056a0130, 0x14000ec8150}, 0x1400076d900)\n\tgithub.com/nspcc-dev/neofs-node/pkg/services/object/server.go:2152 +0xc1c\ngithub.com/nspcc-dev/neofs-node/pkg/services/object.(*Server).processSearchRequest(0x140002288f0, {0x1056a0130, 0x14000ec8150}, 0x1400076d900)\n\tgithub.com/nspcc-dev/neofs-node/pkg/services/object/server.go:2014 +0x52c\ngithub.com/nspcc-dev/neofs-node/pkg/services/object.(*Server).SearchV2(0x140002288f0, {0x1056a0130, 0x14000ec8150}, 0x1400076d900)\n\tgithub.com/nspcc-dev/neofs-node/pkg/services/object/server.go:1951 +0x314\ngithub.com/nspcc-dev/neofs-sdk-go/proto/object._ObjectService_SearchV2_Handler({0x10565b340, 0x140002288f0}, {0x1056a0130, 0x14000ec8150}, 0x14000e80500, 0x0)\n\tgithub.com/nspcc-dev/neofs-sdk-go@v1.0.0-rc.18.0.20260417090255-d6b86c01a5af/proto/object/service_grpc.pb.go:784 +0x1b8\ngoogle.golang.org/grpc.(*Server).processUnaryRPC(0x140000fe248, {0x1056a0130, 0x14000ec80c0}, 0x14000ea8340, 0x1400034e270, 0x1400012ea30, 0x0)\n\tgoogle.golang.org/grpc@v1.79.3/server.go:1429 +0xc94\ngoogle.golang.org/grpc.(*Server).handleStream(0x140000fe248, {0x1056a0ad8, 0x14000313860}, 0x14000ea8340)\n\tgoogle.golang.org/grpc@v1.79.3/server.go:1855 +0x89c\ngoogle.golang.org/grpc.(*Server).serveStreams.func2.1()\n\tgoogle.golang.org/grpc@v1.79.3/server.go:1064 +0x74\ncreated by google.golang.org/grpc.(*Server).serveStreams.func2 in goroutine 372\n\tgoogle.golang.org/grpc@v1.79.3/server.go:1075 +0x120\n```", "state": "CLOSED", "created_at": "2026-04-28T19:45:34Z", "closed_at": "2026-04-29T09:10:35Z", "author_login": "evgeniiz321", "comment_rounds": [{"comments": [{"id": "IC_kwDOEJvkIM8AAAABApn8ow", "body": "can be reproduced by https://github.com/nspcc-dev/neofs-testcases/pull/1356", "createdAt": "2026-04-28T19:57:22Z", "updatedAt": "2026-04-28T19:57:22Z", "author": {"login": "evgeniiz321"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 3970, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug", "neofs-storage", "U1", "S4", "I4"], "milestone": "v0.53.0", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/nu-radio_NuRadioMC_1042.json b/scrape_out/issues/nu-radio_NuRadioMC_1042.json
new file mode 100644
index 0000000000000000000000000000000000000000..a5e19d1990fc261795a50e33eacaccb5bbd34c7c
--- /dev/null
+++ b/scrape_out/issues/nu-radio_NuRadioMC_1042.json
@@ -0,0 +1 @@
+{"number": 1042, "title": "shower_maximum currently not stored in simulated shower", "body": "The parameter `shower_maximum` ([link](https://nu-radio.github.io/NuRadioMC/NuRadioReco/apidoc/NuRadioReco.framework.parameters.html#NuRadioReco.framework.parameters.showerParameters.shower_maximum)) is currently not stored in the simulated shower by default. For neutrino events simulated with ARZ this is relevant in reconstruction, because the viewing angle and travel times are adjusted based on the simulated xmax.\n\nWhile in principle the xmax can be retrieved indirectly via the [charge_excess_profile_id](https://nu-radio.github.io/NuRadioMC/NuRadioReco/apidoc/NuRadioReco.framework.parameters.html#NuRadioReco.framework.parameters.showerParameters.charge_excess_profile_id), this is rather cumbersome and unintuitive. It would be better to just store xmax directly during `simulation.py`.\n\nThis should hopefully be a relatively easy change. We could consider also storing xmax in the HDF5 files.", "state": "CLOSED", "created_at": "2026-02-10T13:02:14Z", "closed_at": "2026-02-26T13:35:10Z", "author_login": "sjoerd-bouma", "comment_rounds": [{"comments": [{"id": "IC_kwDOBxodNM7ptweA", "body": "We could also store it directly into the pickled shower library? (At least we should cache the result during each run to not calculate it over and over for the same profile).", "createdAt": "2026-02-18T14:16:30Z", "updatedAt": "2026-02-18T14:16:30Z", "author": {"login": "fschlueter"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 1048, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["NuRadioMC"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/openSUSE_osc_864.json b/scrape_out/issues/openSUSE_osc_864.json
new file mode 100644
index 0000000000000000000000000000000000000000..ffe25ee0636e518407eadc50966b28adecd9119f
--- /dev/null
+++ b/scrape_out/issues/openSUSE_osc_864.json
@@ -0,0 +1 @@
+{"number": 864, "title": "`osc repo add` or scripted repo addition", "body": "It is good when CLI tools can be used in shell scripts to automate workflows. With `osc` I don't see how to add repository without manually editing XML file with `osc meta prjconf -e`.\r\n\r\nHow about adding a set of `osc repo` commands that will make `osc` interface more or less consistent with what `git remote` provides?\r\n\r\n * `osc repo ls` - list repos configured for the current project\r\n * `osd repo add` - add repo to the project\r\n\r\n", "state": "CLOSED", "created_at": "2020-11-18T12:56:48Z", "closed_at": "2023-07-14T08:57:41Z", "author_login": "abitrolly", "comment_rounds": [{"comments": [{"id": "IC_kwDOACVGhc5XJ41u", "body": "I'm working on something like this right now.\r\nI'm not sure about the `osc repo ls` command, you can always check the meta.\r\nOn the other hand we should also add `osc repo rm`.", "createdAt": "2023-03-09T15:02:35Z", "updatedAt": "2023-03-09T15:02:35Z", "author": {"login": "dmach"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 1324, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/pagefaultgames_pokerogue_2635.json b/scrape_out/issues/pagefaultgames_pokerogue_2635.json
new file mode 100644
index 0000000000000000000000000000000000000000..a5bb9a1a03e780b358fff1e87c748ec57198970e
--- /dev/null
+++ b/scrape_out/issues/pagefaultgames_pokerogue_2635.json
@@ -0,0 +1 @@
+{"number": 2635, "title": "[BUG] Imposters breaks the game", "body": "**Describe the bug**\r\nUpon switching a guzzlord spliced with an imposter ditto, the game locks up. It doesn't freeze per say because the sprites are still moving up and down, but I can't do anything.\r\nHowever, if the switch happens when the promp pops up at the start of a battle, it doesn't freeze. In this case, opening up the summary screen of the transformed species (in this case guzz/ditto transformed into claydol), I have a black screen, the game freezes.\r\n\r\nI don't remember it being an issue with a simple ditto.\r\n", "state": "CLOSED", "created_at": "2024-06-27T01:25:35Z", "closed_at": "2024-11-10T05:39:07Z", "author_login": "kleenxfeu", "comment_rounds": [{"comments": [{"id": "IC_kwDOJPu3QM6GquVV", "body": "Grand Transform Aggregated Issues (Fusion Transform Softlock, Form Not Saved, {Stat changes not copied(imposter), pp not reduced, delayed type change fixed in https://github.com/pagefaultgames/pokerogue/pull/3462})\r\nhttps://discord.com/channels/1125469663833370665/1267976989957029900/1267976989957029900\r\n\r\n\r\nThis one is the same as Issue 2481(Spliced Transform) https://github.com/pagefaultgames/pokerogue/issues/2481\r\nand 2675 (Unable to Catch Imposter Ditto in Spliced mode) https://github.com/pagefaultgames/pokerogue/issues/2675\r\nin that the game crashes at the of a battle with a Transformed Fusion --> Fusion", "createdAt": "2024-07-30T23:06:22Z", "updatedAt": "2024-08-26T08:13:17Z", "author": {"login": "Snailman11"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 4824, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["(Legacy) Bug", "Ability"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/paritytech_substrate-api-sidecar_1153.json b/scrape_out/issues/paritytech_substrate-api-sidecar_1153.json
new file mode 100644
index 0000000000000000000000000000000000000000..37685b8a95e60a272e0935e8c70dde5a14fde924
--- /dev/null
+++ b/scrape_out/issues/paritytech_substrate-api-sidecar_1153.json
@@ -0,0 +1 @@
+{"number": 1153, "title": "[Bug] transaction-pool unwrapping undefined.", "body": "While building out the extended e2e-tests, I was consistently getting this error:\r\n\r\n```\r\n2022-11-28 16:07:30 error: Cannot read properties of undefined (reading 'unwrap') \r\n TypeError: Cannot read properties of undefined (reading 'unwrap')\r\n at NodeTransactionPoolService.computeExtPriority (/Users/tarikgul/Desktop/parity/tools-team/substrate-api-sidecar/build/src/services/node/NodeTransactionPoolService.js:89:80)\r\n at NodeTransactionPoolService.extractExtrinsicInfo (/Users/tarikgul/Desktop/parity/tools-team/substrate-api-sidecar/build/src/services/node/NodeTransactionPoolService.js:61:37)\r\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\r\n at async Promise.all (index 0)\r\n at async NodeTransactionPoolService.fetchTransactionPool (/Users/tarikgul/Desktop/parity/tools-team/substrate-api-sidecar/build/src/services/node/NodeTransactionPoolService.js:35:26)\r\n at async NodeTransactionPoolController.getNodeTransactionPool (/Users/tarikgul/Desktop/parity/tools-team/substrate-api-sidecar/build/src/controllers/node/NodeTransactionPoolController.js:47:62)\r\n at async /Users/tarikgul/Desktop/parity/tools-team/substrate-api-sidecar/build/src/controllers/AbstractController.js:226:9\r\n```\r\n\r\nI was able to reproduce it, and it should be looked into and resolved. \r\n\r\nThis involved the following endpoint `/node/transaction-pool?includeFee=true`\r\n", "state": "CLOSED", "created_at": "2022-11-28T21:09:08Z", "closed_at": "2023-01-09T15:28:59Z", "author_login": "TarikGul", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 1177, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["I2 - Bug \ud83d\udc1c", "C0 - Relay"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/pathpy_pathpyG_91.json b/scrape_out/issues/pathpy_pathpyG_91.json
new file mode 100644
index 0000000000000000000000000000000000000000..34c03c891d52d0b788ef32078171f1a28fd9b234
--- /dev/null
+++ b/scrape_out/issues/pathpy_pathpyG_91.json
@@ -0,0 +1 @@
+{"number": 91, "title": "Add RollingTimeWindow iterator class", "body": "", "state": "CLOSED", "created_at": "2024-01-22T11:26:14Z", "closed_at": "2024-02-21T16:41:40Z", "author_login": "IngoScholtes", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 93, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement"], "milestone": "ML4Nets Course", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/pulp_pulpcore_6274.json b/scrape_out/issues/pulp_pulpcore_6274.json
new file mode 100644
index 0000000000000000000000000000000000000000..8dfc79e69fba9c8c88482e4897151770b0888200
--- /dev/null
+++ b/scrape_out/issues/pulp_pulpcore_6274.json
@@ -0,0 +1 @@
+{"number": 6274, "title": "A deleted-artifact-file cannot be restored by re-uploading.", "body": "**Version**\nmain\n\n**Describe the bug**\nIf a user accidentally deletes a file in /var/lib/pulp/media/artifacts that wasn't sync'd from somewhere, there's no way to re-upload it short of a) deleting all repo-versions that reference the content of that artifact and running orphan-cleanup, or b) messy database surgery.\n\nThe problem is that the upload-process finds the db-entity Artifact, and decides \"the file is already here\" so it doesn't replace it with the incoming one.\n\nThe repair script can fix things when such a mistake happens with files that have a valid RemoteArtifact. \n\n**To Reproduce**\n\n1. Sync https://fixtures.pulpproject.org/rpm-signed/ immediate\n2. Log into the pulp instance and `rm -rf /var/lib/pulp/media/artifacts/b0/`\n3. `wget https://fixtures.pulpproject.org/rpm-signed/bear-4.1-1.noarch.rpm`\n4. `pulp rpm content -t package upload --repository test --file ./bear-4.1-1.noarch.rpm`\n5. Watch failures happen and Be Sad.\n\n**Expected behavior**\nRE-upload should notice that the artifact.file is *actually not there* and restore it from the incoming upload.\n\n**Additional context**\nAdd any other context about the problem here. Please provide links to any previous discussions via Discourse or Bugzilla.\nThis is one of the use-cases mentioned in https://issues.redhat.com/browse/PULP-294", "state": "CLOSED", "created_at": "2025-02-15T17:14:14Z", "closed_at": "2025-02-20T15:15:42Z", "author_login": "ggainey", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 6275, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["Issue"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/rcpch_rcpch-audit-engine_1101.json b/scrape_out/issues/rcpch_rcpch-audit-engine_1101.json
new file mode 100644
index 0000000000000000000000000000000000000000..dc49a823b9f082552b7a9090afe25c12a3cf5385
--- /dev/null
+++ b/scrape_out/issues/rcpch_rcpch-audit-engine_1101.json
@@ -0,0 +1 @@
+{"number": 1101, "title": "Adding Jersey to Organisational Audit", "body": "Related to #1100, Is it possible to add Jersey to the 2024 organisational audit? Can we give them just access to the org audit form, without us needing to have the clinical side worked out? ", "state": "CLOSED", "created_at": "2024-11-13T10:56:06Z", "closed_at": "2025-01-23T20:36:30Z", "author_login": "nikyraja", "comment_rounds": [{"comments": [{"id": "IC_kwDOGMFnNM6VDd8g", "body": "Once https://github.com/rcpch/rcpch-audit-engine/pull/1105 is merged this will work out of the box", "createdAt": "2024-11-26T12:47:25Z", "updatedAt": "2024-11-26T12:47:25Z", "author": {"login": "mbarton"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 1105, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/rizinorg_rizin_3700.json b/scrape_out/issues/rizinorg_rizin_3700.json
new file mode 100644
index 0000000000000000000000000000000000000000..901f37fb1189995e7afc73f3342688057eb49fa0
--- /dev/null
+++ b/scrape_out/issues/rizinorg_rizin_3700.json
@@ -0,0 +1 @@
+{"number": 3700, "title": "Broken test `typedef self-reference`", "body": "Borken and it should not depend on the DWARF information.\r\n\r\n```\r\nNAME=typedef self-reference\r\nBROKEN=1\r\nFILE=bins/elf/analysis/self-ref-typedef\r\nCMDS=< I don't see the use case where one would not want to collect the deb information from a RHEL system. That would be very useful to help support realize there is something very wrong - and suggest what that person should do instead.\r\n> \r\n\r\nAssume we have plugin `foo` that collects a bunch of command output. If I get a support case dealing with `foo`, let's say getting \"bad\" output from some command in production, I'm going to first look for/in `sos_commands/foo` for the output I expect. If that is present, I can assume that `foo` is at least installed properly, since sos activated the plugin.\r\n\r\nOn a RHEL system, if `foo` was installed via a .deb, then this is very wrong and is an improper installation. This data being present actually hinders problem resolution. If `sos_commands/foo` is missing, my first instinct is to check `installed_rpms`, which would not have `foo` in it. Thus, I have to assume that `foo` is either not installed (perhaps the user is running from source for example) or is installed improperly (as defined by the best practices for a RHEL system).\r\n\r\nBy excluding the data collection, a support engineer is clued into the improper installation quicker than they would be while going through what is, effectively in this case, useless clutter in the archive.\r\n\r\n\r\nI wouldn't object to new `packages`-like tuples for snaps and flatpaks for plugin activation beyond the standard package managers, but the use of these package managers should be policy controlled, and not active/enabled across the board.\r\n", "createdAt": "2020-09-18T22:30:34Z", "updatedAt": "2020-09-18T22:30:34Z", "author": {"login": "TurboTurtle"}}]}, {"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDY5NTkyMDcyNw==", "body": "Alright, I'm convinced. I can't figure out a good way to collect the data\nfrom that plugin without making it seem like it ran as expected.\n", "createdAt": "2020-09-21T06:13:56Z", "updatedAt": "2020-09-21T06:13:56Z", "author": {"login": "BryanQuigley"}}]}, {"comments": [{"id": "IC_kwDOAB7_RM43slBr", "body": "I'm just gonna poke this issue with a stick, I have a situation like this:\r\n\r\nSystem: Ubuntu 20.04 running on Google Cloud Platform\r\n\r\nMy GCP plugin I'm working on, wants to collect `gcloud` output. `gcloud` is traditionally provided in a package called `google-cloud-sdk` - however, on this instance this package in installed via `snap` and not `apt`/`dpkg`.\r\n\r\nAs you can see, currently with Ubuntu and their `snap`s, there is no one *right* way of installation. Can I use `SoSPredicate(self, packages=['google-cloud-sdk'])` in a way that would check for `snap` installs too?", "createdAt": "2021-10-05T13:49:14Z", "updatedAt": "2021-10-05T13:49:14Z", "author": {"login": "m-strzelczyk"}}, {"id": "IC_kwDOAB7_RM43ssOL", "body": "> I'm just gonna poke this issue with a stick, I have a situation like this:\r\n> \r\n> System: Ubuntu 20.04 running on Google Cloud Platform\r\n> \r\n> My GCP plugin I'm working on, wants to collect `gcloud` output. `gcloud` is traditionally provided in a package called `google-cloud-sdk` - however, on this instance this package in installed via `snap` and not `apt`/`dpkg`.\r\n> \r\nWhile we are still working on the PackageManager to support FlatPak and SNAP, you could add (PR) the following `commands = ('gcloud',)` inside your plugin. Just make sure the binary is found in the Ubuntu policy defined PATH env: https://github.com/sosreport/sos/blob/main/sos/policies/distros/ubuntu.py#L22-L23 .\r\n\r\nSome plugin such as maas.py does the following:\r\n\r\n```\r\n def _is_snap_installed(self):\r\n return self.exec_cmd('snap list google-cloud-sdk')[\"status\"] == 0\r\n\r\n....\r\nself._is_snap = self._is_snap_installed() \r\nif self._is_snap:\r\n ....\r\n else:\r\n ....\r\n```\r\nhttps://github.com/sosreport/sos/blob/main/sos/report/plugins/maas.py#L59-L60\r\n\r\n> As you can see, currently with Ubuntu and their `snap`s, there is no one _right_ way of installation. Can I use `SoSPredicate(self, packages=['google-cloud-sdk'])` in a way that would check for `snap` installs too?\r\n\r\n", "createdAt": "2021-10-05T14:25:24Z", "updatedAt": "2021-10-05T14:30:33Z", "author": {"login": "slashdd"}}]}, {"comments": [{"id": "IC_kwDOAB7_RM4-iCHW", "body": "@slashdd @BryanQuigley \r\n\r\nLet's cycle around on this. I like the idea of adding `PackageManager()`s for flatpak/snaps. That being said, I'm not very clued into snaps myself. What are the hurdles we need to clear for a snap package manager?\r\n\r\nI also think we can provide multiple package manager support via `Policy()` to those that want it without too much effort.\r\n\r\nOff the top of my head, 2 approaches would be:\r\n\r\n1. Make the `Policy()` methods that call `PackageManager()` loop over some list of valid package managers for the given policy\r\n2. Have all policies use a new \"meta\" package manager that handles ^ internally. Policies would then specify which specific package managers this \"meta\" manager gets initialized with.\r\n", "createdAt": "2022-02-23T18:59:03Z", "updatedAt": "2022-02-23T18:59:03Z", "author": {"login": "TurboTurtle"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 3219, "link_type": "closing_keyword", "will_close": true, "comment_count": 7, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/taskcluster_taskcluster_7443.json b/scrape_out/issues/taskcluster_taskcluster_7443.json
new file mode 100644
index 0000000000000000000000000000000000000000..5b1d9055a3f677ba62c9842fc927c9015bd98a2d
--- /dev/null
+++ b/scrape_out/issues/taskcluster_taskcluster_7443.json
@@ -0,0 +1 @@
+{"number": 7443, "title": "Worker-manager killing workers executing tasks because of queueInactivityTimeout ", "body": "We introduced zombie workers killing in https://github.com/taskcluster/taskcluster/pull/6333 \r\nbut didn't consider the fact that really low `queueInactivityTimeout` values could kill the worker while it is working on a task.\r\n\r\nWorker manager should additionally check if worker has zero active claims at that point. \r\n\r\nAnother option would to always increase this value by a \"default reclaim timeout\", so if tasks are considered claim expired after 20 min, we could always include 20m extra", "state": "CLOSED", "created_at": "2025-01-09T13:46:12Z", "closed_at": "2025-01-13T16:05:59Z", "author_login": "lotas", "comment_rounds": [{"comments": [{"id": "IC_kwDOCaXmMM6Z-W7U", "body": "schema should define minimum value for the `queueInactivityTimeout` to be equal to `DEFAULT_CLAIM_TIMEOUT` (+1?)", "createdAt": "2025-01-10T16:55:25Z", "updatedAt": "2025-01-10T16:55:25Z", "author": {"login": "lotas"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 7452, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug", "worker management"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/tronprotocol_java-tron_5368.json b/scrape_out/issues/tronprotocol_java-tron_5368.json
new file mode 100644
index 0000000000000000000000000000000000000000..c65ed92bf104881a0bfc9800596bc10821d76f05
--- /dev/null
+++ b/scrape_out/issues/tronprotocol_java-tron_5368.json
@@ -0,0 +1 @@
+{"number": 5368, "title": "Acquire Internet IP from Libp2p API", "body": "# Rationale\r\n\r\nAt present, java-tron clients obtain external IPv4 and IPv6 through a method that accesses two certain URLs, it\u2019s the same as libp2p. Java-tron executes this method first, and libp2p executes later when being initialized. This time-consuming method has been executed twice and may delay the startup speed of the java-tron clients.\r\n\r\n# Implementation\r\n\r\n1. When java-tron clients start, it obtains the external IP through Libp2p\u2019s method/api directly.\r\n2. When initializing libp2p, java-tron assigns two IPs to the related fields of P2pConfig, and Libp2p does not need to acquire the external IP again. To meet this requirement we need to add a new constructor method for libp2p.\r\n\r\n# Compatibility\r\n\r\nThere is no backward compatibility concern for this issue.", "state": "CLOSED", "created_at": "2023-07-21T10:44:36Z", "closed_at": "2023-08-30T10:17:10Z", "author_login": "317787106", "comment_rounds": [{"comments": [{"id": "IC_kwDOBuELcs5iLZPc", "body": "What is the purpose of `external IPv4 and IPv6`? What are the effects if they are not acquired ?", "createdAt": "2023-07-24T03:45:35Z", "updatedAt": "2023-07-24T03:45:35Z", "author": {"login": "halibobo1205"}}, {"id": "IC_kwDOBuELcs5iLiC9", "body": "@halibobo1205 The main usage of ip in libp2p is used to construct your homenode, that is part of UDP Ping & Pong message sent to other in p2p node discovering, and you can find third party nodes from neighbours's message that include ip. Usage of ip in java-tron is to build HelloMessage in HandshakeService.", "createdAt": "2023-07-24T04:30:49Z", "updatedAt": "2023-07-24T04:30:49Z", "author": {"login": "317787106"}}, {"id": "IC_kwDOBuELcs5iMNMa", "body": "Why not initial the libp2p module first, and try to get the IPs through the libp2p interface?", "createdAt": "2023-07-24T07:32:20Z", "updatedAt": "2023-07-24T07:32:20Z", "author": {"login": "tomatoishealthy"}}, {"id": "IC_kwDOBuELcs5iMT11", "body": "> Why not initial the libp2p module first, and try to get the IPs through the libp2p interface?\r\n\r\nagree with @guoquanwu , if java-tron's use libp2p module as a dependency, it is better to query the needed config directly from the dependency instead of constructing it itself.", "createdAt": "2023-07-24T07:50:25Z", "updatedAt": "2023-07-24T07:50:25Z", "author": {"login": "eodiandie"}}, {"id": "IC_kwDOBuELcs5iMV3Q", "body": "> Why not initial the libp2p module first, and try to get the IPs through the libp2p interface?\r\n\r\nsame viewpoint with this. Using Libp2p\u2019s method/api directly to get the external IP and then reusing the IP to initial libp2p may be unreasonable.\r\n\r\n", "createdAt": "2023-07-24T07:56:15Z", "updatedAt": "2023-07-24T07:56:26Z", "author": {"login": "kuny0707"}}, {"id": "IC_kwDOBuELcs5iMZva", "body": "@guoquanwu @xq-lu @yuekun0707 Good suggestion! I accept this idea. There will be more places to modify, but that is another matter.", "createdAt": "2023-07-24T08:07:08Z", "updatedAt": "2023-07-24T08:07:08Z", "author": {"login": "317787106"}}, {"id": "IC_kwDOBuELcs5iMfS4", "body": "> @halibobo1205 The main usage of ip in libp2p is used to construct your homenode, that is part of UDP Ping & Pong message sent to other in p2p node discovering, and you can find third party nodes from neighbours's message that include ip. Usage of ip in java-tron is to build HelloMessage in HandshakeService.\r\n\r\n BTW, what are the effects if they are acquired failed?", "createdAt": "2023-07-24T08:22:12Z", "updatedAt": "2023-07-24T08:45:25Z", "author": {"login": "halibobo1205"}}, {"id": "IC_kwDOBuELcs5iMu3a", "body": "@halibobo1205 If java-tron fails to get the external IP, it use 127.0.0.1 as default, it records HelloMessage in log. When some exception happens, developer can backtrack the whole process easily. But this will become harder if ip is missing or use default ip in HelloMessage. Node in HelloMessage includes IPv4 and IPv6, so it has more information than the socket's address.", "createdAt": "2023-07-24T09:01:05Z", "updatedAt": "2023-07-24T09:04:20Z", "author": {"login": "317787106"}}]}, {"comments": [{"id": "IC_kwDOBuELcs5kQRTc", "body": "What if the ip changed after you acquired it ? How much time does it cost to obtain external IPv4 and IPv6? As I know, it should be very fast to obtain external IPv4 and IPv6", "createdAt": "2023-08-17T09:52:49Z", "updatedAt": "2023-08-17T09:55:23Z", "author": {"login": "lurais"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 5407, "link_type": "closing_keyword", "will_close": true, "comment_count": 9, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["type:feature"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/tutao_tutanota_6326.json b/scrape_out/issues/tutao_tutanota_6326.json
new file mode 100644
index 0000000000000000000000000000000000000000..13b96e2fecc603767ae62a52f0e866a0ae9b2d14
--- /dev/null
+++ b/scrape_out/issues/tutao_tutanota_6326.json
@@ -0,0 +1 @@
+{"number": 6326, "title": "Agenda Items do not scroll in desktop mode", "body": "Repro:\r\n- Have enough events in a day that there are more than fit onto the screen.\r\n- You are not able to scroll to see the ones below.\r\n\r\nExpected:\r\n- Can scroll to see all events\r\n\r\nWe aren't using our own List component to display these, maybe use that here too?\r\n\r\n## Test Notes\r\n- [x] Event view popup is styled correctly\r\n - [x] Description icon & body are aligned\r\n - [x] Participants icon & body are aligned\r\n - [x] Invitation buttons look correct\r\n - [x] Stays correct at various view-port sizes\r\n- [x] Event list in the agenda view scrolls\r\n- [x] Details in the agenda view scrolls ", "state": "CLOSED", "created_at": "2023-12-21T16:07:31Z", "closed_at": "2024-01-19T14:31:10Z", "author_login": "wrdhub", "comment_rounds": [{"comments": [{"id": "IC_kwDOAVT0qs5w_zhv", "body": "This works, but there is also now a horizontal scrollbar if the window is not wide enough.\r\n\r\n\r\n", "createdAt": "2024-01-17T13:06:05Z", "updatedAt": "2024-01-17T13:06:05Z", "author": {"login": "paw-hub"}}, {"id": "IC_kwDOAVT0qs5xPzSn", "body": "The scroll works on three columns layout but not on one/two columns layout.\r\nAlso, not working on mobile devices.\r\n\r\nAnd the invitation button seems to be without hover effect, that isn't a big problem and shouldn't hold the release\r\n\r\n\r\n\r\n", "createdAt": "2024-01-19T08:28:09Z", "updatedAt": "2024-01-19T08:28:09Z", "author": {"login": "murilopereirame"}}, {"id": "IC_kwDOAVT0qs5xQm-T", "body": "Invitation button was like that, it's fixed in #6334", "createdAt": "2024-01-19T10:50:51Z", "updatedAt": "2024-01-19T10:50:51Z", "author": {"login": "charlag"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 6345, "link_type": "closing_keyword", "will_close": true, "comment_count": 3, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug", "state:tested", "desktop", "state:done", "topic: calendar"], "milestone": "3.121.0", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/vegaprotocol_vega_9078.json b/scrape_out/issues/vegaprotocol_vega_9078.json
new file mode 100644
index 0000000000000000000000000000000000000000..d7def397f8ca1c7085db93641889ac9a41ab1128
--- /dev/null
+++ b/scrape_out/issues/vegaprotocol_vega_9078.json
@@ -0,0 +1 @@
+{"number": 9078, "title": "[Referral]: Add API for the activity streak", "body": "- activity streak \r\n\r\n- [ ] Vesting\r\n - [ ] reward_distribution_bonus_multiplier\r\n\r\n\r\n- [ ] Activity streak info\r\n\r\n - [ ] Inactivity_streak (ie. N epochs)\r\n - [ ] Activity_streak (ie. N epochs)\r\n - [ ] Reward_distribution_activity_multiplier\r\n - [ ] Reward_vesting_activity_multiplier", "state": "CLOSED", "created_at": "2023-08-15T12:22:31Z", "closed_at": "2023-09-07T15:11:55Z", "author_login": "gordsport", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 9309, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["api", "referral"], "milestone": "\u2604\ufe0f Cosmic Elevator", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/woocommerce_google-listings-and-ads_2933.json b/scrape_out/issues/woocommerce_google-listings-and-ads_2933.json
new file mode 100644
index 0000000000000000000000000000000000000000..f5247fe3983d017ef9026c91c00d7caae77b6ff9
--- /dev/null
+++ b/scrape_out/issues/woocommerce_google-listings-and-ads_2933.json
@@ -0,0 +1 @@
+{"number": 2933, "title": "Update sorting and filtering in Price Suggestions", "body": "## User Story\nAs an engineer, I want to avoid loading large datasets on the frontend by querying the API on demand with pagination, sorting, and search parameters, so that only a small, relevant subset of data is fetched and cached per request.\n\n## Acceptance Criteria\n* DataViews interactions are driven by server responses instead of frontend filtering.\n* Sorting, searching, and pagination should result in a new request to the REST API.\n* The total number of pages should update if the total possible results change (e.g., search results will return fewer price benchmark objects than the default view.\n* By default, the price benchmarks suggestions should be ordered by effectiveness (High to Low)\n* If the same search or sort is made without refreshing the page, it should NOT result in another REST request.\n\n## Implementation Brief\n* Update the `fetchPriceBenchmarkSuggestions` action to accept an `args` parameter which is an object containing the following properties:\n\t* page\n\t* per_page\n\t* search\n\t* order\n\t* orderby\n* The `args` should be added to the `price-benchmarks` endpoint using `addQueryArgs`.\n* Update the `getPriceBenchmarkSuggestions` selector/resolver to include the `args` parameter.\n\t* Update the `usePriceBenchmarkSuggestions` hook as well.\n* Update `js/src/data/reducer.js` to change `price_benchmark.suggestions` from an array to an object with the following properties.\n\t* items: Contains product info keyed by the product ID.\n\t* queries: Contains query results keyed in by a slug generated from the `args` passed to `fetchPriceBenchmarkSuggestions`. The query results should be stored in the `items` property and pagination data in the `meta` property.\n\t\t* The items should contains product IDs only, referencing products in the parent `items` property.\n\t\t\t* Before adding the data in the store, some data manipulation needs to occur to upsert the product info.\n* Update `PriceBenchmarkSuggestions` to:\n\t* include the `args` parameter to `usePriceBenchmarkSuggestions` with the `DataViews` `view` property mapped to the properties in the first bullet point.\n\t\t* `view.perPage` -> `per_page`\n\t\t* `view.search` -> `search`\n\t\t* `view.page` -> `page`\n\t\t* `view.sort.direction` -> `order`\n\t\t* `view.sort.field` -> `orderby`\n\t* remove usage of the `filterSortAndPaginate` function to instead manually handle the pagination via the `paginationInfo` prop of `DataViews`.\n\t\t* Sorting will be handled automatically when the query will be returned from the API.\n\t* Use the `isLoading` prop of `DataViews` to indicate if there's any query in progress instead of rendering `TablePlaceholder`\n\t* The `EmptyMetricsNotice` component should be rendered only when there's no data on the initial query (default query).\n\t* Add necessary function to format the data to be stored/retrieved from the store.\n\n## Test coverage\n* Update mock data to make sure existing tests pass.", "state": "CLOSED", "created_at": "2025-05-23T15:54:57Z", "closed_at": "2025-06-11T16:11:14Z", "author_login": "asvinb", "comment_rounds": [{"comments": [{"id": "IC_kwDOEjsCO86tJkGo", "body": "@asvinb This looks good to me. Let's add a little more specifics to the AC:\n\n* Sorting, searching, and pagination should result in a new request to the REST API.\n* The total number of pages should update if the total possible results change (e.g., search results will return fewer price benchmark objects than the default view.\n* By default, the price benchmarks suggestions should be ordered by `effectiveness` (High to Low)\n* If the same search or sort is made without refreshing the page, it should NOT result in another REST request.", "createdAt": "2025-05-23T16:06:14Z", "updatedAt": "2025-05-23T16:06:14Z", "author": {"login": "joemcgill"}}, {"id": "IC_kwDOEjsCO86tMBgI", "body": "These changes are dependent on the BE changes being worked on for #2911. Until those are ready, this will need to be tested using mocked REST responses.", "createdAt": "2025-05-23T19:40:15Z", "updatedAt": "2025-05-23T19:40:15Z", "author": {"login": "joemcgill"}}]}], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["Bug Bash Item"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/zerothi_sisl_538.json b/scrape_out/issues/zerothi_sisl_538.json
new file mode 100644
index 0000000000000000000000000000000000000000..550099902b4250b180cedcaac896da51df09ecbd
--- /dev/null
+++ b/scrape_out/issues/zerothi_sisl_538.json
@@ -0,0 +1 @@
+{"number": 538, "title": "sisl.nodes and automatic_recalc", "body": "**Describe the feature**\r\n\r\nInstead of passing the automatic_recalc as a function argument, wouldn't it be more explicit to use a separate method for the class?\r\n\r\nI.e. a user might find it weird that an _extra_ argument to the function call will change the behaviour.\r\nSince the `update_inputs` is already documented, it shouldn't be too much of a hazzle to make a `Node.set_autocalc(True|False)` or similar? Or perhaps, since the documentation emphasises `lazy` behaviour, we might name it `Node.set_lazy(True|False)`?\r\n\r\nIs there a special point on adding extra arguments to the function?\r\n\r\n@pfebrer\r\n", "state": "CLOSED", "created_at": "2023-02-09T18:17:59Z", "closed_at": "2023-03-08T11:38:51Z", "author_login": "zerothi", "comment_rounds": [{"comments": [{"id": "IC_kwDOAkih_85U6ndz", "body": "I agree the current approach doesn't make much sense.\r\n\r\nLet's call this extra arguments that define the behavior of the node \"meta-arguments\".\r\n\r\nIn the tutorial I show how one can overwrite a meta-argument default in the function signature:\r\n\r\n```python\r\n@Node.from_func\r\ndef myalert(val=val, automatic_recalc=True):\r\n ...\r\n```\r\n\r\nThe function itself doesn't use `automatic_recalc`, so indeed it is very strange that it has this extra argument. It makes even less sense if the function is defined separately, and you create a node like:\r\n\r\n```python\r\ndef myalert(val=val, automatic_recalc=True):\r\n ...\r\n\r\nalert_node = Node.from_func(myalert)\r\n```\r\n\r\nSo for this case, I would propose:\r\n```python\r\n@Node.from_func(automatic_recalc=True)\r\ndef myalert(val=val):\r\n ...\r\n\r\n#or\r\n\r\ndef myalert(val=val):\r\n ...\r\n\r\nNode.from_func(myalert, automatic_recalc=True)\r\n```\r\n\r\nTo overwrite meta-argument defaults.\r\n\r\nThen `lazy` could also be a meta-argument.\r\n\r\nI also agree 100% that the `update_inputs` should be left only for function arguments as well. I like your idea of `set_*` methods, but perhaps to make it more general for any number of meta-arguments there could be a special method to update them (`update_metainputs` or whatever, I don't know what the right name would be to make it understandable).\r\n\r\nSo, in summary, you made me realise that we should have this distinction between `arguments` and `meta-arguments` and treat them separately, do you agree?\r\n", "createdAt": "2023-02-09T18:40:04Z", "updatedAt": "2023-02-09T18:40:04Z", "author": {"login": "pfebrer"}}, {"id": "IC_kwDOAkih_85U6oD5", "body": "Another meta-argument that I already thought we should introduce is `cached=True|False`. Because you might want a lazy node but still not cache its result.", "createdAt": "2023-02-09T18:42:18Z", "updatedAt": "2023-02-09T18:42:18Z", "author": {"login": "pfebrer"}}, {"id": "IC_kwDOAkih_85U6quW", "body": "I forgot you also made the point that calling the node with this extra arguments is strange. I also agree. How about:\r\n\r\n```python\r\nwith node_arguments(lazy=True, automatic_recalc=True):\r\n node = node_cls(argument1=\"something\")\r\n\r\n#or\r\n\r\nnode_cls.with(lazy=True, automatic_recalc=True)(argument1=\"something\")\r\n```\r\n", "createdAt": "2023-02-09T18:52:40Z", "updatedAt": "2023-02-09T18:52:40Z", "author": {"login": "pfebrer"}}]}, {"comments": [{"id": "IC_kwDOAkih_85VMZaG", "body": "Yeah, the `node_cls.with` seems like a good idea... Then everything can be packed into that one.\r\n\r\n```python\r\ndef = sisl.node.context(**default args)\r\ndef2 = sisl.node.context(**default args2)\r\nnode.with(context=def)(...)\r\nnode(...)\r\n```\r\nor something similar?", "createdAt": "2023-02-14T08:21:09Z", "updatedAt": "2023-02-14T08:21:09Z", "author": {"login": "zerothi"}}, {"id": "IC_kwDOAkih_85VMm9Y", "body": "Do you think the `with` needs to accept everything packed into the `context` argument? Why not pass the arguments directly? Do you expect `with` to have other arguments?\r\n\r\nThe way you did it is interesting though. Do you expect these settings to be put in a context and then nodes have to check the context that they are attached to before actually doing things? As opposed to the settings being the state of each node individually. If you did that you could share the context between nodes, which could be nice to switch on and off some features for multiple nodes at the same time. And by default nodes would point to the main general context.\r\n\r\nThe only problem that I see is that perhaps I want some extra context setting that only applies to a certain class of Node. But then these contexts could be made of partial contexts that are chained in something like a chainmap:\r\n\r\n```python\r\n# All the settings of the main sisl context\r\nsisl_main_context = sisl.nodes.context( ... )\r\n\r\n# Special context that I define for event listeners\r\nlisten_context = sisl.nodes.context(automatic_recalc=True}\r\n\r\n# Use the sisl main context except for the settings that are explicitly overwritten by listen_context \r\ncontext = Chainmap(sisl_main_context, listen_context)\r\n\r\nnode.with(context)()\r\n```\r\n\r\nThen any update to the main context of `sisl` would still be applied to the node.\r\n\r\nI really like the idea that with one switch in this case for example you could turn off all event listeners. And since we are trying to be functional it seems like having contexts that are consumed by nodes is better than having a node state.\r\n\r\nFollowing the same mindset, input management could also be something detached from nodes themselves, but that is for another discussion :sweat_smile: ", "createdAt": "2023-02-14T09:06:22Z", "updatedAt": "2023-02-14T09:06:58Z", "author": {"login": "pfebrer"}}, {"id": "IC_kwDOAkih_85VMz5d", "body": "My main motivation for having a context argument is that context managers would have problems if one of the nodes in the context do not want to use the context. That would mean an irregular workflow...\r\n\r\nThat is why the argument based contexts seemed a bit more natural to me. But you could do both, a global *state context*, and then local contexts which are chain-mapped internally for their use. A context should then also be able to revert to default arguments.", "createdAt": "2023-02-14T09:40:18Z", "updatedAt": "2023-02-14T09:40:18Z", "author": {"login": "zerothi"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 547, "link_type": "closing_keyword", "will_close": true, "comment_count": 6, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file
diff --git a/scrape_out/issues/zowe_zowe-explorer-vscode_3824.json b/scrape_out/issues/zowe_zowe-explorer-vscode_3824.json
new file mode 100644
index 0000000000000000000000000000000000000000..dd7672831fe3fd9f4c7148b73048bc136dfdfaae
--- /dev/null
+++ b/scrape_out/issues/zowe_zowe-explorer-vscode_3824.json
@@ -0,0 +1 @@
+{"number": 3824, "title": "Right click action of delete on VSAM datasets in ZE view", "body": "**Is your feature request related to a problem? Please describe.**\n\nRight now we do not have any choice to delete the created VSAM datasets from the Zowe Explorer view. The only option we have is through the CLI command\n\n**Describe the solution you'd like**\n\nShould we bring the right click option of Delete on VSAM datasets in ZE and through that option it can be deleted.\n", "state": "CLOSED", "created_at": "2025-08-25T06:47:06Z", "closed_at": "2025-09-10T21:32:38Z", "author_login": "likhithanimma1", "comment_rounds": [{"comments": [{"id": "IC_kwDOCPJY786_3qsk", "body": "Thank you for raising this enhancement request.\nThe community has 90 days to vote on it.\nIf the enhancement receives at least 10 upvotes, it is added to our development backlog.\nIf it receives fewer votes, the issue is closed.", "createdAt": "2025-08-25T06:47:15Z", "updatedAt": "2025-08-25T06:47:15Z", "author": {"login": "github-actions"}}]}, {"comments": [{"id": "IC_kwDOCPJY787Ch-Ws", "body": "PR: https://github.com/zowe/zowe-explorer-vscode/pull/3845", "createdAt": "2025-09-07T10:49:46Z", "updatedAt": "2025-09-07T10:49:46Z", "author": {"login": "likhithanimma1"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 3845, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "priority-medium"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}
\ No newline at end of file