Add files using upload-large-folder tool

scrape_out/issues/1QB-Information-Technologies_ccvm_151.json

@@ -0,0 +1 @@
+{"number": 151, "title": "Use variables names to replace hard-coding value in clamp function", "body": "This issue comes from one [PR comment](https://github.com/1QB-Information-Technologies/ccvm/pull/141#discussion_r1448027749).\r\n\r\n- The values `0` and `1` in the clamp function should be general values named `lower_clamp` and `upper_clamp`, which receive their values at the input with the default values set to `lower_clamp=0.0` and `upper_clamp=1.0`.\r\n\r\n- This also applies to all post processors.\r\n\r\n", "state": "CLOSED", "created_at": "2024-01-24T01:02:08Z", "closed_at": "2024-01-30T23:30:05Z", "author_login": "Estella-Wang-1qbit", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 152, "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": []}

scrape_out/issues/3drepo_3drepo.io_4705.json

@@ -0,0 +1 @@
+{"number": 4705, "title": "", "body": "", "state": "", "created_at": "", "closed_at": null, "author_login": "", "comment_rounds": [], "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": ["In Staging", "Maintenance"], "milestone": "5.7.0", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/3drepo_3drepo.io_4790.json

@@ -0,0 +1 @@
+{"number": 4790, "title": "", "body": "", "state": "", "created_at": "", "closed_at": null, "author_login": "", "comment_rounds": [{"comments": [{"id": "IC_kwDOAWcnlc50ZoMk", "body": "@AsiteZane  we've seen this before on Mia's laptop, but could not reproduce on anyone elses'....\r\n\r\nIt's a bit difficult for @sebjf  to look into the reason why when we don't have a reliable way to reproduce... unless @sebjf have any further ideas", "createdAt": "2024-02-19T16:54:35Z", "updatedAt": "2024-02-19T16:54:35Z", "author": {"login": "carmenfan"}}, {"id": "IC_kwDOAWcnlc50Zo1-", "body": "> @AsiteZane we've seen this before on Mia's laptop, but could not reproduce on anyone elses'....\r\n> \r\n> It's a bit difficult for @sebjf to look into the reason why when we don't have a reliable way to reproduce... unless @sebjf have any further ideas\r\n\r\n@sebjf  could it be to do with pause rendering being a be unpredictable? sound we be turning it off when we're in an action like this?", "createdAt": "2024-02-19T16:56:21Z", "updatedAt": "2024-02-19T16:56:21Z", "author": {"login": "carmenfan"}}, {"id": "IC_kwDOAWcnlc50aX9f", "body": "I am wondering if it's the same as this issue: https://github.com/3drepo/3drepounity/issues/495\r\n\r\nIs it possible to check the model of GPU(s) on the problem machine, and possibly [switch the high performance one](https://github.com/3drepo/3drepounity/issues/495#issuecomment-1845114139) on or off?", "createdAt": "2024-02-19T19:41:46Z", "updatedAt": "2024-02-19T19:41:46Z", "author": {"login": "sebjf"}}]}, {"comments": [{"id": "IC_kwDOAWcnlc51R8Dl", "body": "@sebjf / @carmenfan  I hopefully have a call with him tomorrow to see if the GPU(s) are causing the issue and then hopefully resolve the matter. I'll let you know how it goes.", "createdAt": "2024-02-27T21:34:17Z", "updatedAt": "2024-02-27T21:34:35Z", "author": {"login": "zaneulhaq"}}, {"id": "IC_kwDOAWcnlc51V6-g", "body": "@sebjf / @carmenfan So, sad news, he only has one GPU and it's the onboard Iris GPU which I was having issues with - no other GPU to flick over to. I'll get him to send the about GPU report and Console log so we can dig a bit deeper. I wouldn't be surprised if this happens to other customers. We seem to have an issue with these onboard graphics GPUs. He's always in the office so if you wanted to triage aggressively in-person Sebastian, that's always an option.", "createdAt": "2024-02-28T10:27:51Z", "updatedAt": "2024-02-28T10:28:12Z", "author": {"login": "zaneulhaq"}}]}, {"comments": [{"id": "IC_kwDOAWcnlc51n9bC", "body": "@sebjf / @carmenfan - info below whenever you think it is appropriate to look at it.\r\n\r\n[www.3drepo.io-1709306894780.log](https://github.com/3drepo/3drepo.io/files/14463010/www.3drepo.io-1709306894780.log)\r\n![webGL report](https://github.com/3drepo/3drepo.io/assets/148439628/d67ca890-ded1-4903-88ff-2b348f57e562)\r\n[about-gpu-2024-03-01T15-25-50-425Z.txt](https://github.com/3drepo/3drepo.io/files/14463013/about-gpu-2024-03-01T15-25-50-425Z.txt)\r\n", "createdAt": "2024-03-01T15:40:41Z", "updatedAt": "2024-03-01T15:40:41Z", "author": {"login": "zaneulhaq"}}, {"id": "IC_kwDOAWcnlc51n_R_", "body": "@sebjf  if you can quickly sanity check to see anything obvious?\r\n\r\nBeyond that I think we'd need a laptop that can reproduce this to thoroughly investigate", "createdAt": "2024-03-01T15:44:54Z", "updatedAt": "2024-03-01T15:44:54Z", "author": {"login": "carmenfan"}}, {"id": "IC_kwDOAWcnlc51oD9B", "body": "Hi @carmenfan @AsiteZane yes this confirms the GPU is the same as the model we've had previous issues with. There isn't any indication of why changing RTs (if that is the problem) fails. (The screenshot is of the WebGL 1.0 info but I am guessing Web GL 2.0 is substantially similar, since the viewer shouldn't load without 2.0 support nowadays.)\r\n\r\nIf the issue is as expected, turning off Pause Rendering should be a workaround. That's not exposed in the Viewer Settings, but we could make a staging deployment to test it on?", "createdAt": "2024-03-01T15:54:54Z", "updatedAt": "2024-03-01T15:58:04Z", "author": {"login": "sebjf"}}, {"id": "IC_kwDOAWcnlc51owlX", "body": "@sebjf we had the pause/resume rendering functions exposed in UnityUtils ages ago for debugging purpose https://github.com/3drepo/3drepo.io/blob/master/frontend/src/globals/unity-util.ts#L1548\r\n\r\nDo they still work? perhaps we can use it as a quick test", "createdAt": "2024-03-01T17:43:54Z", "updatedAt": "2024-03-01T17:43:54Z", "author": {"login": "carmenfan"}}, {"id": "IC_kwDOAWcnlc51o7nP", "body": "> Do they still work? perhaps we can use it as a quick test\r\n\r\nUnfortunately not - it just forces pausing on regardless of input, so the opposite of what we need!", "createdAt": "2024-03-01T18:07:42Z", "updatedAt": "2024-03-01T18:07:42Z", "author": {"login": "sebjf"}}]}, {"comments": [{"id": "IC_kwDOAWcnlc53Dfkz", "body": "Hi @carmenfan @AsiteZane, I was about to add the new API when I found we *do* have one, its just both @carmenfan and I were looking at the wrong one!\r\n\r\nThe unfortunately-named-in-retrospect `UnityUtil.toggleCameraPause()` can be used to toggle the render pause/caching on and off.\r\n\r\n(This is still not exposed via the settings dialog, but Kieran can use this in the Console to see if it is a viable workaround.)", "createdAt": "2024-03-14T12:59:05Z", "updatedAt": "2024-03-14T12:59:05Z", "author": {"login": "sebjf"}}, {"id": "IC_kwDOAWcnlc53HlxN", "body": "> Hi @carmenfan @AsiteZane, I was about to add the new API when I found we _do_ have one, its just both @carmenfan and I were looking at the wrong one!\r\n> \r\n> The unfortunately-named-in-retrospect `UnityUtil.toggleCameraPause()` can be used to toggle the render pause/caching on and off.\r\n> \r\n> (This is still not exposed via the settings dialog, but Kieran can use this in the Console to see if it is a viable workaround.)\r\n\r\n@sebjf , thank you. How would you do that via the console? I've tried looking around with limited success sorry.\r\nScreen shot below - i was trying to create a live expression but that doesn't seem to work... keeps looping between false and true\r\n![image](https://github.com/3drepo/3drepo.io/assets/148439628/355c5aff-f0ad-4950-a003-6d3e92129431)\r\n", "createdAt": "2024-03-14T21:02:22Z", "updatedAt": "2024-03-14T21:05:09Z", "author": {"login": "zaneulhaq"}}, {"id": "IC_kwDOAWcnlc53LVfe", "body": "Hi @AsiteZane, thats correct - unless you mean you give the command and then it responds twice?\r\n\r\nWhat you should see is that calling it changes the reported value:\r\n\r\n![image](https://github.com/3drepo/3drepo.io/assets/5058369/fa9be485-1edc-43c3-ad97-4eb86676a0ea)\r\n\r\nThe default is On, which means the render caching is enabled. Calling it once should turn it off. On larger models you should see a drop in FPS when it's Off.\r\n", "createdAt": "2024-03-15T11:27:48Z", "updatedAt": "2024-03-15T11:27:48Z", "author": {"login": "sebjf"}}, {"id": "IC_kwDOAWcnlc53L4Kv", "body": "Hi @sebjf , what I mean is it keeps turning it on and off without stopping...", "createdAt": "2024-03-15T12:51:57Z", "updatedAt": "2024-03-15T12:51:57Z", "author": {"login": "zaneulhaq"}}, {"id": "IC_kwDOAWcnlc53MF55", "body": "> > Hi @carmenfan @AsiteZane, I was about to add the new API when I found we _do_ have one, its just both @carmenfan and I were looking at the wrong one!\r\n> > The unfortunately-named-in-retrospect `UnityUtil.toggleCameraPause()` can be used to toggle the render pause/caching on and off.\r\n> > (This is still not exposed via the settings dialog, but Kieran can use this in the Console to see if it is a viable workaround.)\r\n> \r\n> @sebjf , thank you. How would you do that via the console? I've tried looking around with limited success sorry. Screen shot below - i was trying to create a live expression but that doesn't seem to work... keeps looping between false and true ![image](https://private-user-images.githubusercontent.com/148439628/312995332-355c5aff-f0ad-4950-a003-6d3e92129431.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTA1MDkyNDQsIm5iZiI6MTcxMDUwODk0NCwicGF0aCI6Ii8xNDg0Mzk2MjgvMzEyOTk1MzMyLTM1NWM1YWZmLWYwYWQtNDk1MC1hMDAzLTZkM2U5MjEyOTQzMS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMzE1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDMxNVQxMzIyMjRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1iNDYyMzBjOWRhYTk1ZDk2Y2U5MjhlYjk5MDFiNzhkMDdiNWMyOTQ1Yzg1ODZiNGVkZDc1OGY0ZTg4ODJlMGExJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.aH641dlN-S6oGPnofa80G8CkXPj4ATxcom434tNzrtQ)\r\n\r\n@AsiteZane  don't create a live expression \ud83d\ude48 \r\n\r\njust go onto the console and type it in once.\r\n\r\nBy doing a live expression you're basically calling the function over and over again \ud83d\ude06 ", "createdAt": "2024-03-15T13:24:28Z", "updatedAt": "2024-03-15T13:24:28Z", "author": {"login": "carmenfan"}}, {"id": "IC_kwDOAWcnlc53Ntpi", "body": "@sebjf / @carmenfan  Whoopsie... went for the most complicated way to address a simple problem \ud83d\ude13 \r\n\r\nNews back from the naughty laptop and their user - great success! UnityUtil.toggleCameraPause() works a treat, is there any way to force it off client-slide when loading a 3DR session so they don't have to do it for each session?", "createdAt": "2024-03-15T17:04:03Z", "updatedAt": "2024-03-15T17:04:03Z", "author": {"login": "zaneulhaq"}}, {"id": "IC_kwDOAWcnlc53N1WX", "body": "We could map it into the viewer settings, but that would refer a bit of front end effort.\r\n\r\n@sebjf probably a better judge of this, but I don't think we want to permanently turn it off? we probably want to only turn it off when we're rendering an animation and during measurements... Otherwise there's going to be massive lag just operating the viewer when you're loading large models.", "createdAt": "2024-03-15T17:23:00Z", "updatedAt": "2024-03-15T17:23:17Z", "author": {"login": "carmenfan"}}, {"id": "IC_kwDOAWcnlc53N2K2", "body": "Thanks @carmenfan  - i just meant for this particular user. Wouldn't want them doing this in front of customers during a demo", "createdAt": "2024-03-15T17:25:00Z", "updatedAt": "2024-03-15T17:25:00Z", "author": {"login": "zaneulhaq"}}, {"id": "IC_kwDOAWcnlc53N39C", "body": "@AsiteZane aside from opening a session in advance put in the function call, there isn't much way around this without sneaking it into viewer settings.\r\n\r\nThere might be some browser extensions he can utilise to do it automatically https://stackoverflow.com/questions/22707808/automatically-run-javascript-code-upon-loading-a-specific-website#:~:text=You%20can%20use%20dotjs.,%2F%20%2C%20dotjs%20will%20execute%20~%2F.", "createdAt": "2024-03-15T17:29:48Z", "updatedAt": "2024-03-15T17:29:48Z", "author": {"login": "carmenfan"}}, {"id": "IC_kwDOAWcnlc53N4kl", "body": "@AsiteZane  but I do mean for this specific user, if he's demoing with it disabled, make sure he thoroughly check with models he intend to demo with that he's not experiencing lag due to turning this feature off. In the past it has become quite a problem in chunky models!", "createdAt": "2024-03-15T17:31:21Z", "updatedAt": "2024-03-15T17:31:39Z", "author": {"login": "carmenfan"}}]}, {"comments": [{"id": "IC_kwDOAWcnlc57hQSK", "body": "As discussed in the meeting...\r\n\r\nWe have confirmed that a number of issues of this type can be solved by turning the Pause Rendering feature off, though the problem with doing this is that the viewer will take a performance hit, which will be especially noticeable during things like mark-up.\r\n\r\nThere are a number of possible next steps:\r\n\r\n1. We have an IRIS XE laptop, so we could try and rework the rendering code around the actual bug in a general way. This is likely to take a long time and not guaranteed to work, though it fixes the issue for good.\r\n\r\n2. The simplest workaround is for the sales team to [turn off Pause Rendering](https://github.com/3drepo/3drepo.io/issues/4790#issuecomment-1997404467) on demand. Possibly expressing this in the Visual Settings dialog. \r\n\r\n3. A middle approach is to build a compatibility shim into the viewer logic. When a flag is set, when any tool or feature that might be vulnerable to the bug is active, pause rendering is automatically disabled.\r\n\r\nThe value proposition for (3) is a little low at the moment, because no customers are reporting the issue, and there is no way to detect the GPU. We would not want to turn the shim on by default, and if no customers are reporting the issue for us to tell them to turn it on manually, the only beneficiaries of that development work are the Sales/CS team, whose problem could also be solved by using a different laptop. \r\n\r\n", "createdAt": "2024-04-23T13:23:21Z", "updatedAt": "2024-04-23T13:23:21Z", "author": {"login": "sebjf"}}]}, {"comments": [{"id": "IC_kwDOAWcnlc58xnzJ", "body": "Some further investigation into this...\r\n\r\nTests with an Iris Xe confirm that the issue is that the main camera ends up drawing into the Scene Camera's Render Texture (RT) - not that, for example, the Front Buffer is not being cleared properly.\r\n\r\nWe can observe the behaviour of this by placing a RawImage Component on the Screen Canvas and setting its image to the Scene Camera's RT. This should give us a picture-in-picture of only what the Scene Camera's RT contains.\r\n\r\nThere are a few interesting things to note about this.\r\n\r\n1. While all mesh objects, such as our lines and Pins, 'overdraw' this way, anything on the `UGUI.RenderingRenderOverlays` pass does not.\r\n2. There is a temporal aspect, which is that after the Scene Camera draws to the buffer, it takes a frame or two for the 'main' camera to draw over it.\r\n3. It is definitely that the main camera is drawing - not simply being cleared. As we can see the Main Camera's Skybox draw.\r\n\r\nVarious parts of the pipeline have been toggled, around the CameraRenderTextureChain CommandBuffers, and the RenderTextureManager on the Scene camera, but the behaviour doesn't change.\r\n\r\nHowever, if we create a RenderTexture *asset*, and assign it to the Scene Camera & RawImage Component at design time, then the RT does not appear to be overridden and we get the expected picture-in-picture effect, with no overdraw of our UI elements.\r\n\r\n![image](https://github.com/3drepo/3drepo.io/assets/5058369/f3d78056-4c0d-43e7-93e3-51c2d33c44e8)\r\n\r\nUsing this same RenderTexture in the previous graphics pipeline (with the Command Buffer Blit) also works. Assigning the RT *asset* dynamically in Start() and via the callbacks as before also works.\r\n\r\nIt appears then that the dynamically created RTs differ from the assets in some way the Iris XE is sensitive to...\r\n\r\n(PS. this investigation has also stumbled upon [this](https://github.com/3drepo/3drepounity/issues/519), though there doesn't appear to be any relation yet.)", "createdAt": "2024-05-03T16:45:59Z", "updatedAt": "2024-05-03T16:45:59Z", "author": {"login": "sebjf"}}, {"id": "IC_kwDOAWcnlc58yA7i", "body": "Further testing shows its the size of the RT that causes the issue - the static RT has a different size than the front buffer. If a RT is created from the assets descriptor, then the bug does not show, but if the size of the asset's descriptor is updated beforehand, then the bug reveals itself. Even if a difference of one pixel will stop the bug from manifesting, but introduces sampling artefacts...\r\n\r\nThis may have something to do with some sort of caching the driver is doing.", "createdAt": "2024-05-03T17:44:10Z", "updatedAt": "2024-05-03T17:49:41Z", "author": {"login": "sebjf"}}]}, {"comments": [{"id": "IC_kwDOAWcnlc59C4kz", "body": "Attempting to create an MWE in a new Unity project shows that it is possible to render to a texture like we intend on the Xe. Comparing the two projects reveals the issue is in the msaa settings of the RenderTexture. With msaa not set in the RenderTextureDescriptor, the bug does not manifest on the Iris Xe.\r\n\r\nLooking further at this, it seems that the camera controls the MSAA and this no longer needs to be set on the RT for MSAA to work - the Scene Camera takes the setting from the Quality settings.\r\n\r\nA Unity issue to make this change permanently has been created [here](https://github.com/3drepo/3drepounity/issues/520).\r\n\r\n", "createdAt": "2024-05-07T09:54:01Z", "updatedAt": "2024-05-07T09:54:01Z", "author": {"login": "sebjf"}}, {"id": "IC_kwDOAWcnlc59Gq0L", "body": "@AsiteZane, this branch (https://issue-4790.dev.3drepo.io/v5/login) is ready for Ciaran to test when he has a sec!", "createdAt": "2024-05-07T16:54:41Z", "updatedAt": "2024-05-07T16:54:41Z", "author": {"login": "sebjf"}}]}], "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": ["bug", "In Staging"], "milestone": "5.9.0", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/3drepo_3drepobouncer_745.json

@@ -0,0 +1 @@
+{"number": 745, "title": "generateWebViewBuffers should stream", "body": "<!-- FEATURE TEMPLATE (delete as appropriate) -->\n<!-- Remember to tag this issue as a feature! -->\n### Description\nProduct issue: https://github.com/3drepo/3D-Repo-Product-Team/issues/683\n<!-- What is the feature, is it associated with any other issues? (list here) -->\nThe web buffer (i.e. stash graph & RepoBundles) construction should be modified so that the entire scene - original or baked - no longer has to be held in memory at once.\n\n### Goals\n<!-- Acceptance criteria : What journeys should the user be able to complete to consider your feature done -->\n<!-- Be as specific as you can, check them off once they work. Add more if you find more requirements during development. Issue should only be considered done after all of them are checked -->\n- [ ] The memory highwater mark is much lower than it is right now\n- [ ] The memory highwater mark increases only trivially with geometry\n<!-- etc etc.. -->\n\n### Tasks\n<!-- base on the goals, deduce the tasks required. check them off once they're done -->\n- [ ] TBD\n<!-- etc etc.. -->\n\n### Related Resources\n<!-- any images/gifs, mockups/wireframes that would aid the development should be listed here -->\nMockUp : `link to mockup`\nCoda doc: `link to coda`\n<!-- END OF FEATURE TEMPLATE -->\n", "state": "CLOSED", "created_at": "2025-03-03T12:24:18Z", "closed_at": "2025-07-08T17:34:01Z", "author_login": "carmenfan", "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": ["In Staging"], "milestone": "5.17.2", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/ACCIDDA_flepimop2_4.json

@@ -0,0 +1 @@
+{"number": 4, "title": "Top Level Pipeline Configuration Specification", "body": "Need a parent `pydantic.BaseModel` object to serve as the root of the configuration specification in a new `flepimop2.configuration` submodule/package. Can be light on implementation for now, largely a container.", "state": "CLOSED", "created_at": "2025-10-13T14:20:30Z", "closed_at": "2025-10-20T18:56:13Z", "author_login": "TimothyWillard", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 7, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["configuration"], "milestone": "Pipeline MVP simulate action", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/AFM-SPM_TopoStats_451.json

@@ -0,0 +1 @@
+{"number": 451, "title": "Remove unnecessary images from tests", "body": "Tests take ages to run, I introduced comparing Matplotlib generated images to many of the unittests but I think there are too many in there now.\r\n\r\nWe should leave those in for explicit testing of `plottingfuncs` and `plotting` (work in progress!) but all the other arrays are checked by their sums and so the graphs themselves are a bit unnecessary.\r\n\r\nThis would also reduce the size of the repository to download (although I fear they will remain buried in the Git history unless I undertake some attach to remove them, not sure I could do that without breaking things).", "state": "CLOSED", "created_at": "2023-02-02T15:13:40Z", "closed_at": "2023-02-10T17:32:56Z", "author_login": "ns-rse", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 455, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": "M4 : On-going Refactoring", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Aam-Digital_ndb-core_2195.json

@@ -0,0 +1 @@
+{"number": 2195, "title": "Wrong entities are added to tables", "body": "**Describe the bug**\r\nThrough the \"listen-to-update logic\" we apply updates to tables once they were initially rendered. This for example adds entities to a table that are synchronized while a table is open. This is also used to remove entities from a table when they are deleted.\r\nAt the moment we are always (?) adding every entity of the given type to the currently open table. \r\nThis can sometimes be wrong when for example the notes for a specific child are shown but a new note for a different child is added. This note will still be added to the table and shown until the view is reloaded.\r\n\r\n**To Reproduce**\r\nThis is only one example, others might work very differently (e.g. through sync)\r\n\r\nSteps to reproduce the behavior:\r\n1. Go to 'Child Details'\r\n2. Click on 'Notes & Tasks'\r\n3. Click on the primary action button\r\n4. Add a subject and save (without adding the child on whose details page we currently are)\r\n5. The note will be shown in the notes table\r\n6. After leaving and re-visiting the the details page the note is not visible any more.\r\n\r\n**Expected behavior**\r\nThe note should never be shown.\r\n\r\n**Additional context**\r\nMost table components use the `RelatedEntitiesComponent` which has logic to listen and apply entity updates of the provided entity type. Currently it adds **all** new entities of that type even if they might not fit the table that is actually shown.\r\n\r\nWe could fix this by providing a filter for the entities which are shown based on the logic of the table. As this logic is very straight forward (show the entities that are linked e.g. to this child) it could be quite easy to even infer this based on the provided property.\r\nActually, even the property can be inferred based on the schema information that is available.", "state": "CLOSED", "created_at": "2024-01-23T18:11:11Z", "closed_at": "2024-02-05T08:58:08Z", "author_login": "TheSlimvReal", "comment_rounds": [{"comments": [{"id": "IC_kwDOA0GdQM5y1BSP", "body": ":tada: This issue has been resolved in version 3.31.1-master.6 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.31.1-master.6)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2024-02-05T08:59:16Z", "updatedAt": "2024-02-05T08:59:16Z", "author": {"login": "aam-digital-ci"}}, {"id": "IC_kwDOA0GdQM5y1iCk", "body": ":tada: This issue has been resolved in version 3.31.1 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.31.1)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2024-02-05T10:13:16Z", "updatedAt": "2024-02-05T10:13:16Z", "author": {"login": "aam-digital-ci"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 2196, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["released on @master", "released"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Aam-Digital_ndb-core_2198.json

@@ -0,0 +1 @@
+{"number": 2198, "title": "EntityCount Dashboard should display human-readable categories when disaggregating by a referenced entity", "body": "![image](https://github.com/Aam-Digital/ndb-core/assets/1682541/b936c5ed-6d21-47a5-97a1-c57a78d2b744)\r\n\r\nThe grouping by a property in the EntityCountDashboard currently displays either .label or the string of the groupBy property. This means grouping by an entity reference (which is a string uuid on the entities) is not displayed well.\r\n\r\n--> use toString or EntityBlockComponent", "state": "CLOSED", "created_at": "2024-01-25T08:37:41Z", "closed_at": "2024-01-29T14:05:58Z", "author_login": "sleidig", "comment_rounds": [{"comments": [{"id": "IC_kwDOA0GdQM5yIPui", "body": "duplicate of #2002 ", "createdAt": "2024-01-29T14:05:59Z", "updatedAt": "2024-01-29T14:05:59Z", "author": {"login": "sleidig"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM5yj-dd", "body": ":tada: This issue has been resolved in version 3.31.1-master.2 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.31.1-master.2)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2024-02-01T19:06:33Z", "updatedAt": "2024-02-01T19:06:33Z", "author": {"login": "aam-digital-ci"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM5y1iEF", "body": ":tada: This issue has been resolved in version 3.31.1 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.31.1)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2024-02-05T10:13:19Z", "updatedAt": "2024-02-05T10:13:19Z", "author": {"login": "aam-digital-ci"}}]}], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 3, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["released on @master", "released"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Aam-Digital_ndb-core_2615.json

@@ -0,0 +1 @@
+{"number": 2615, "title": "", "body": "", "state": "", "created_at": "", "closed_at": null, "author_login": "", "comment_rounds": [{"comments": [{"id": "IC_kwDOA0GdQM6RRtr_", "body": "When opening Add Note Dialog, this error is logged to console: \n\n![Image](https://github.com/user-attachments/assets/a37218cc-428c-47e5-b9a4-b55a3d339301)\n", "createdAt": "2024-10-25T09:37:51Z", "updatedAt": "2024-10-25T09:37:51Z", "author": {"login": "tomwwinter"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM6SAKa1", "body": ":tada: This issue has been resolved in version 3.42.3-master.1 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.42.3-master.1)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2024-10-31T10:23:18Z", "updatedAt": "2024-10-31T10:23:18Z", "author": {"login": "aam-digital-ci"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM6U7ImX", "body": ":tada: This issue has been resolved in version 3.43.0 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.43.0)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2024-11-25T16:47:04Z", "updatedAt": "2024-11-25T16:47:04Z", "author": {"login": "aam-digital-ci"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 2641, "link_type": "closing_text", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["released on @master", "released"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Aam-Digital_ndb-core_2638.json

@@ -0,0 +1 @@
+{"number": 2638, "title": "", "body": "", "state": "", "created_at": "", "closed_at": null, "author_login": "", "comment_rounds": [{"comments": [{"id": "IC_kwDOA0GdQM6SAKcK", "body": ":tada: This issue has been resolved in version 3.42.3-master.1 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.42.3-master.1)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2024-10-31T10:23:21Z", "updatedAt": "2024-10-31T10:23:21Z", "author": {"login": "aam-digital-ci"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM6U7IoU", "body": ":tada: This issue has been resolved in version 3.43.0 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.43.0)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2024-11-25T16:47:07Z", "updatedAt": "2024-11-25T16:47:07Z", "author": {"login": "aam-digital-ci"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 2643, "link_type": "closing_text", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["Type: UX", "released on @master", "released"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Aam-Digital_ndb-core_2858.json

@@ -0,0 +1 @@
+{"number": 2858, "title": "Merge: Other entities linking to either one of the two merged records", "body": "When two records are merged, the details captured in other entities should not be lost or deleted; they should be available in the merged record. \n\nOther entities linking to either one of the two merged records (e.g., Notes related to two records of a Child that are getting merged) must be updated to link to the single merged record. \nDetails captured in other entities (all the records listed within the details tabs captured) should be available in a list in the merged record to ensure no data loss. \n\n**Scenario ** : Child Record A has four linked Notes. Child record B has five notes that are linked. \nIn the merged record, nine notes should be listed to ensure no data loss. \n\nIn scenarios where two-child records are merged for the other entity-related tabs(Education, Notes & tasks, Educational Materials, Observations) to ensure no data loss, all the details captured for both records are available in a list in the current design.\n", "state": "CLOSED", "created_at": "2025-02-14T14:31:37Z", "closed_at": "2025-03-24T08:08:10Z", "author_login": "george-neha", "comment_rounds": [{"comments": [{"id": "IC_kwDOA0GdQM6g9JJt", "body": "Edge case: What if record A + B are both linked, so that after merging them the same record would be linked twice (e.g. twice on the attendance list of an event)?\n\n- ID of the removed merged record gets replaced by the ID of the remaining record\n- if in array fields the same ID is included twice now, then we remove the second, duplicate ID\n- in case this has a different attendance status, we still delete that second entry and log a warning\n   - --> 2nd version: proper UI for asking user about such cases", "createdAt": "2025-03-05T09:41:50Z", "updatedAt": "2025-03-05T09:41:50Z", "author": {"login": "sleidig"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM6h7-ua", "body": "After reviewing both recommended methods, I found the following:  \n\n1. **`findFieldsReferencingEntityType`** provides details about related entity types, such as:  \n\n   ```\n   Aser: { additional: \"Child\", dataType: \"entity\", entityReferenceRole: \"composite\", id: \"child\" }  \n   EducationalMaterial: { additional: \"Child\", dataType: \"entity\", entityReferenceRole: \"composite\", id: \"child\" }  \n   ChildSchoolRelation: [{\u2026}]\n   ```  \n   However, it does not return the related entity IDs or other necessary details.  \n\n2. **`CascadingActionResult`** (from `entityActionService`) provides the information we need\u2014a list of related entities for the selected rows. For example:  \n\n   ```\n   Note {  \n     _id: 'Note:35e63d4b-d0bd-45f7-8c8f-07d9292d9991',  \n     children: ['Child:1'],  \n     childrenAttendance: EventAttendanceMap(0),  \n     authors: ['User:Devak'],  \n     relatedEntities: []  \n   }\n   ```  \n   Since this approach includes entity IDs, it is more suitable for our use case.  \n\n### Proposed Approach:  \n1. Add a new method in `BulkMergeService` to retrieve related entities for the second record.  \n2. And then, update all references to use the first record\u2019s ID.  \n3. Write test cases to verify that after merging, the related entities of Record B are added to the related entities of Record A.  \nLet me know if this approach looks good or if you have any other suggestions.", "createdAt": "2025-03-12T07:21:11Z", "updatedAt": "2025-03-12T08:49:00Z", "author": {"login": "Abhinegi2"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM6jeLnc", "body": "@george-neha, could you test the items mentioned above on the https://pr-2904.aam-digital.net/?", "createdAt": "2025-03-21T07:50:42Z", "updatedAt": "2025-03-21T07:50:42Z", "author": {"login": "Abhinegi2"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM6jx8nS", "body": ":tada: This issue has been resolved in version 3.49.0-master.9 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.49.0-master.9)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2025-03-24T11:19:24Z", "updatedAt": "2025-03-24T11:19:24Z", "author": {"login": "aam-digital-ci"}}, {"id": "IC_kwDOA0GdQM6jzi9I", "body": ":tada: This issue has been resolved in version 3.49.0 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.49.0)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2025-03-24T13:49:14Z", "updatedAt": "2025-03-24T13:49:14Z", "author": {"login": "aam-digital-ci"}}]}], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 5, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["released on @master", "released"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Aam-Digital_ndb-core_3118.json

@@ -0,0 +1 @@
+{"number": 3118, "title": "when creating a new entity type in Admin UI, also add menu item", "body": "We already allow to create a new entity type in the Admin UI through the `AdminEntityTypesComponent`. While the UI is not very polished yet, it serves as a useful tool for internal use and advanced users. When creating a new type, we currently add config for views and the entity config.\n\nAlso create a new menu item `{ \"entityType\": \"MY_NEW_TYPE\" }` (using the EntityMenuItem format) there to automate a very common step that admins need to take.", "state": "CLOSED", "created_at": "2025-07-02T08:50:48Z", "closed_at": "2025-07-02T14:43:47Z", "author_login": "sleidig", "comment_rounds": [{"comments": [{"id": "IC_kwDOA0GdQM60fiR0", "body": ":tada: This issue has been resolved in version 3.57.1-master.7 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.57.1-master.7)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2025-07-02T14:48:28Z", "updatedAt": "2025-07-02T14:48:28Z", "author": {"login": "aam-digital-ci"}}]}, {"comments": [{"id": "IC_kwDOA0GdQM61gPQR", "body": ":tada: This issue has been resolved in version 3.57.1 :tada:\n\nThe release is available on [GitHub release](https://github.com/Aam-Digital/ndb-core/releases/tag/3.57.1)\n\nYour **[semantic-release](https://github.com/semantic-release/semantic-release)** bot :package::rocket:", "createdAt": "2025-07-07T13:24:29Z", "updatedAt": "2025-07-07T13:24:29Z", "author": {"login": "aam-digital-ci"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 3125, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["released on @master", "released", "Client: by X"], "milestone": "Setup Wizard", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Actual-Chat_actual-chat_1081.json

@@ -0,0 +1 @@
+{"number": 1081, "title": "ios maui - share files/docs via app", "body": "", "state": "CLOSED", "created_at": "2023-03-22T10:19:35Z", "closed_at": "2025-12-31T09:51:22Z", "author_login": "frolyo", "comment_rounds": [{"comments": [{"id": "IC_kwDOFyLfoM5bCODb", "body": "Later?", "createdAt": "2023-04-28T10:01:08Z", "updatedAt": "2023-04-28T10:01:08Z", "author": {"login": "alexyakunin"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 3416, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": "iOS", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Adamant-im_adamant_170.json

@@ -0,0 +1 @@
+{"number": 170, "title": "[Enhancement] Add includeDirectTransfers parameter to /api/chats/get", "body": "### Summary\n\nAdd a positive `includeDirectTransfers` query parameter to `/api/chats/get`, keep backward compatibility with the deprecated `withoutDirectTransfers` parameter, and align the endpoint behavior with the existing chat filtering model.\n\n### Motivation\n\nThe existing `withoutDirectTransfers` filter is hard to reason about because it uses a double negative. A positive parameter name is clearer for API consumers, reduces integration mistakes, and makes `/api/chats/get` consistent with related chat endpoints and query-language documentation.\n\n### Detailed description\n\nThis issue is created as the tracking issue for work that was implemented in [PR #91](https://github.com/Adamant-im/adamant/pull/91), which was merged on February 25, 2025.\n\nScope implemented in that PR:\n\n- add `includeDirectTransfers` support for `/api/chats/get`\n- preserve backward compatibility by continuing to accept deprecated `withoutDirectTransfers`\n- keep `withoutDirectTransfers` as the higher-priority option when both parameters are provided\n- cover the behavior with API tests for default behavior and explicit parameter values\n\nRelevant node changes:\n\n- `modules/chats.js`\n- `test/api/chats.js`\n\nCompanion artifacts are already aligned at the time of issue creation:\n\n- `Adamant-im/adamant-schema` documents `includeDirectTransfers` and marks `withoutDirectTransfers` as deprecated\n- `Adamant-im/docs` documents `includeDirectTransfers` for `/api/chats/get` and related chat endpoints\n\n### Screenshots or videos\n\nN/A\n\n### Alternatives\n\nKeep only `withoutDirectTransfers` and document the double negative more clearly. This would preserve compatibility but would keep the API harder to use and less consistent.\n\nAnother alternative would be a breaking rename that removes `withoutDirectTransfers` immediately, but that would create avoidable integration risk for existing clients.\n\n### Proposed technical implementation\n\n- add `includeDirectTransfers` parsing in `/api/chats/get`\n- keep backward-compatible handling of `withoutDirectTransfers`\n- prefer `withoutDirectTransfers` when both filters are present\n- verify behavior with API tests\n- keep schema/docs synchronized with the node implementation\n", "state": "CLOSED", "created_at": "2026-04-21T12:23:07Z", "closed_at": "2026-04-21T12:23:18Z", "author_login": "adamantmm", "comment_rounds": [{"comments": [{"id": "IC_kwDOBjfSW87_nSTe", "body": "Implemented in PR #91, merged on February 25, 2025.", "createdAt": "2026-04-21T12:23:17Z", "updatedAt": "2026-04-21T12:23:17Z", "author": {"login": "adamantmm"}}]}], "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": ["APIs", "enhancement", "Nodes"], "milestone": "v0.10.0", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Aharoni-Lab_cala_53.json

@@ -0,0 +1 @@
+{"number": 53, "title": "Interface Between Data Structure and Transformers", "body": "rn the transformers are dealing with the data structure by getting completely coupled.\n\nneed to build an interface that separates the two.\n\nproposed changes in #52 ", "state": "CLOSED", "created_at": "2025-03-01T00:17:26Z", "closed_at": "2025-03-07T19:38:10Z", "author_login": "raymondwjang", "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": []}

scrape_out/issues/AletheiaFact_aletheia_2028.json

@@ -0,0 +1 @@
+{"number": 2028, "title": "[BE] Create missing steps on state-machine of VR", "body": "### Background Information\n\nDuring the implementation of the state machine for triage, we only implemented the embedding step using an AI task. To follow the implementation, we need to add the missing steps documented on [NOTION](https://www.notion.so/aletheiafact/Triage-5fc9e271e24c4df2a3bfe1662a70ff12?source=copy_link)\n\n### Expected Behavior\n\n- [ ] When creating a verification request, the steps of the TRIAGE should be triggered\n- [ ] Save steps triggered on the database\n- [ ] Pass a verification request from pre-triage to triage", "state": "CLOSED", "created_at": "2025-10-06T12:36:41Z", "closed_at": "2025-11-18T18:43:32Z", "author_login": "snowmous3", "comment_rounds": [{"comments": [{"id": "IC_kwDOCOSaMM7SBA1x", "body": "@snowmous3 \nIn this case, I just need to create a verification request, and what would be my confirmation to validate this issue?", "createdAt": "2025-11-12T19:05:00Z", "updatedAt": "2025-11-12T19:05:00Z", "author": {"login": "Keikonichi"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 2042, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["tech"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/AllayMC_Allay_618.json

@@ -0,0 +1 @@
+{"number": 618, "title": "bug: sky light calculation is wrong", "body": "```\nx\nA\nx\nx\nx\nxxxxx\n```\n\nExpected sky light value of A: 14\nActual value: 11", "state": "CLOSED", "created_at": "2025-03-28T05:46:28Z", "closed_at": "2025-04-18T04:31:51Z", "author_login": "smartcmd", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 622, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": "0.4.0 (API 0.7.0) Release", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/AprilSylph_XKit-Rewritten_1970.json

@@ -0,0 +1 @@
+{"number": 1970, "title": "Tweak to hide the floating \u201cNew posts\u201d indicator button was removed", "body": "### Platform\n\nany\n\n### Browser\n\nany\n\n### Addon version\n\nv1.1.1\n\n### Details\n\nWe removed the tweak that hides the floating \u201cNew posts\u201d indicator button on the dashboard, but it turns out that button still exists!\n\nThis has been remedied in #1942, and so the option will be back in the next XKit Rewritten version! I'm just retroactively making this issue so that I can pin it until that version comes out.", "state": "CLOSED", "created_at": "2025-11-06T11:35:19Z", "closed_at": "2025-11-06T11:35:36Z", "author_login": "marcustyphoon", "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": ["bug"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/ArduPilot_ardupilot_32491.json

@@ -0,0 +1 @@
+{"number": 32491, "title": "Copter: switch OFF does not abort an ongoing Flip", "body": "# Bug Report\n\n\n## Issue details\n\nI found a possible inconsistency between the documented/manual-exit rule for Copter Flip mode and the actual runtime behavior in SITL.\n\nThe rule exists in both:\n1. the official Flip mode documentation\n2. the `mode_flip.cpp` comment\n\nThe relevant rule is:\n\n> Pilot may manually exit flip by switching off ch7/ch8 or by moving roll stick to >40deg left or right\n\nIn my SITL experiments, the **roll-stick abort works**, but **switching the flip AUX switch OFF does not reliably abort an already-triggered Flip**.\n\nWhat I observed is:\n\n1. If I trigger Flip via `RC7_OPTION = 2` and then turn the switch OFF very early, Flip often does **not** start at all.\n2. If I keep the switch ON slightly longer so that Flip is actually triggered, then turning the switch OFF does **not** stop the maneuver; Flip continues and completes normally.\n3. By contrast, a near-full roll-stick input can abort Flip when applied with correct timing.\n\nSo the current behavior appears to be:\n\n- switch OFF affects whether Flip is successfully triggered/latches\n- but switch OFF does **not** seem to abort an ongoing Flip\n- roll-stick abort does work\n\nMy question is:\n- Is the statement \"switching off ch7/ch8 exits Flip\" outdated (documentation/comment only)?\n- Or is switch-OFF abort intended, but currently not implemented in the runtime logic?\n\n## Reproduction summary\n\nI tested in Copter SITL with:\n- `RC7_OPTION = 2`\n- hover in `ALT_HOLD`\n- trigger Flip by setting `CH7` HIGH\n- then switch `CH7` LOW at different delays\n\nRepresentative results:\n- `OFF_DELAY_S = 0.30`: Flip often does not trigger\n- `OFF_DELAY_S = 0.35`: Flip triggers and completes normally (~1.3 s), not aborted by switch OFF\n\nThis suggests that switch OFF affects the trigger/latch boundary, but not the abort of an already-started Flip.\n\n## Evidence / logs\n\n**Screenshot**\n\n<img width=\"1804\" height=\"998\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/d4e0ffb1-2fda-46a6-bf53-d435ed3dce2a\" />\n\n**BIN logs**\nhttps://github.com/jinmussj/SITL-problems/blob/main/2026-03-19%2020-52-20%EF%BC%88Closing%20_the_channel_7_will_not_exit_Flip%EF%BC%89.bin\n\n**Version**\nArduPilot Copter SITL (4.7.0)\n\n**Platform**\n[  ] All\n[  ] AntennaTracker\n[\u00d7] Copter\n[  ] Plane\n[  ] Rover\n[  ] Submarine\n\n**Airframe type**\nQuadcopter\n\n**Hardware type**\nSITL\n\n**Logs**\nSee links above.", "state": "CLOSED", "created_at": "2026-03-19T13:47:15Z", "closed_at": "2026-05-20T23:40:46Z", "author_login": "jinmussj", "comment_rounds": [{"comments": [{"id": "IC_kwDOAHKhpM70BLuh", "body": "I'm a mechanical engineering student, and I've been looking into flight dynamics. I'd like to investigate why the switch-OFF isn't aborting the Flip maneuver in SITL. Mind if I take a look at the logic in `mode_flip.cpp`?", "createdAt": "2026-03-19T23:07:29Z", "updatedAt": "2026-03-19T23:07:29Z", "author": {"login": "Atishyy27"}}, {"id": "IC_kwDOAHKhpM70Dk22", "body": "Hi @jinmussj,\n\nThanks very much for the report.  The comments are correct so this seems like a bug to me.  I've added it to the [4.7 issues list](https://github.com/ArduPilot/ardupilot/issues/32385) although I'm sure it exists in older versions of AP as well.\n\nThe fix is:\n\n1. add a new \"abandon()\" method to ModeFlip ([code here](https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/mode.h#L965)) that sets the _state to FlipState::Abandon\n2. enhance the [RC_Channel_Copter::do_aux_function() ](https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/RC_Channel_Copter.cpp#L186)method so that the new abandon method is called if the switch position is changed to Low or Middle.\n\nI'd like to get @peterbarker's opinion on whether we need to put a semaphore around the Flip mode's _state variable to ensure the rc switch change doesn't affect the state half way through the run function (e.g. is the aux function processing in the same thread as the run function?)\n\nAnyone is welcome to submit a PR to fix this, there's no need to ask for permission. In general the first correct PR is merged, thanks!", "createdAt": "2026-03-20T00:25:11Z", "updatedAt": "2026-03-20T00:26:44Z", "author": {"login": "rmackay9"}}, {"id": "IC_kwDOAHKhpM70FW1J", "body": "> I'm a mechanical engineering student, and I've been looking into flight dynamics. I'd like to investigate why the switch-OFF isn't aborting the Flip maneuver in SITL. Mind if I take a look at the logic in `mode_flip.cpp`?\n\nHi, thanks for your interest.\n\nOf course \u2014 please feel free to take a look at the logic in mode_flip.cpp:\nhttps://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/mode_flip.cpp\n\nAny thoughts are very welcome.", "createdAt": "2026-03-20T02:41:47Z", "updatedAt": "2026-03-20T02:41:47Z", "author": {"login": "jinmussj"}}, {"id": "IC_kwDOAHKhpM70FaN4", "body": "> Hi [@jinmussj](https://github.com/jinmussj),\n> \n> Thanks very much for the report. The comments are correct so this seems like a bug to me. I've added it to the [4.7 issues list](https://github.com/ArduPilot/ardupilot/issues/32385) although I'm sure it exists in older versions of AP as well.\n> \n> The fix is:\n> \n> 1. add a new \"abandon()\" method to ModeFlip ([code here](https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/mode.h#L965)) that sets the _state to FlipState::Abandon\n> 2. enhance the [RC_Channel_Copter::do_aux_function() ](https://github.com/ArduPilot/ardupilot/blob/master/ArduCopter/RC_Channel_Copter.cpp#L186)method so that the new abandon method is called if the switch position is changed to Low or Middle.\n> \n> I'd like to get [@peterbarker](https://github.com/peterbarker)'s opinion on whether we need to put a semaphore around the Flip mode's _state variable to ensure the rc switch change doesn't affect the state half way through the run function (e.g. is the aux function processing in the same thread as the run function?)\n> \n> Anyone is welcome to submit a PR to fix this, there's no need to ask for permission. In general the first correct PR is merged, thanks!\n\nHi @rmackay9,\n\nThank you very much for confirming this and for outlining the possible fix.\n\nThanks as well for the implementation guidance regarding a new abandon() method in ModeFlip and the corresponding change in RC_Channel_Copter::do_aux_function().", "createdAt": "2026-03-20T02:45:55Z", "updatedAt": "2026-03-20T02:45:55Z", "author": {"login": "jinmussj"}}]}, {"comments": [{"id": "IC_kwDOAHKhpM8AAAABAL-gWA", "body": "I found the comment cited in `flip_mode.cpp`. \ud83d\udc4d Next @jinmussj says:\n> The rule exists in [...] the official Flip mode documentation\n\nI'm looking [here](https://ardupilot.org/copter/docs/flip-mode.html#flip-mode) and not finding it. Can someone point me to it?\n\nI also searched git's history ~8 years and can't see that this functionality ever existed.\n\nI agree this is the key question:\n> My question is:\n> - Is the statement \"switching off ch7/ch8 exits Flip\" outdated (documentation/comment only)?\n> - Or is switch-OFF abort intended, but currently not implemented in the runtime logic?\n\n@rmackay9 before I go further, would you please confirm that using an AUX RC switch to abort the flip **should be added as a new feature**? (And correspondingly added to the wiki documentation.) Your describing the solution details seems like 'yes'... but this being currently a 'bug report' suggests no.\n\nThe trivial alternative, as proposed by @jinmussj , is simply removing that false claim from the `.cpp` file comments.", "createdAt": "2026-04-23T20:00:54Z", "updatedAt": "2026-04-23T22:23:51Z", "author": {"login": "hunt0r"}}, {"id": "IC_kwDOAHKhpM8AAAABANJ7UQ", "body": "Hi @hunt0r,\n\nMentioned separately but I think cancelling from the switch is a natural way for the pilot to do it.  We probably need a new cancel accessor added and then trigger it from RC_Channels aux switch handler.", "createdAt": "2026-04-23T22:40:03Z", "updatedAt": "2026-04-23T22:40:03Z", "author": {"login": "rmackay9"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 33005, "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": []}

scrape_out/issues/AtlasDevHQ_atlas_1237.json

@@ -0,0 +1 @@
+{"number": 1237, "title": "test: add test coverage for ee/src/backups/ and ee/src/sla/ modules", "body": "## Context\n\nPR #1236 converted all 18 EE modules from async/Promise to native Effect. The backup modules (`engine.ts`, `restore.ts`, `scheduler.ts`, `verify.ts`) and SLA modules (`alerting.ts`, `metrics.ts`) have **zero test coverage** \u2014 both before and after the conversion.\n\nThese modules had ~900 lines of code changed during the Effect migration with no tests to verify behavioral equivalence.\n\n## What needs testing\n\n### Backups (`ee/src/backups/`)\n- `createBackup` \u2014 pg_dump + gzip pipeline, status tracking, failure recovery\n- `verifyBackup` \u2014 header validation, status updates\n- `purgeExpiredBackups` \u2014 file deletion + DB cleanup, ENOENT handling\n- `listStorageFiles` \u2014 directory listing, ENOENT fallback\n- `executeRestore` \u2014 psql pipeline, pre-restore backup, confirmation tokens\n- `runScheduledBackup` \u2014 cron evaluation, config loading\n\n### SLA (`ee/src/sla/`)\n- `recordQueryMetric` \u2014 fire-and-forget recording\n- `getSlaSummary` \u2014 p50/p95/p99 aggregation\n- `evaluateAlertConditions` \u2014 threshold checks\n- `processAlerts` \u2014 alert routing\n\n## Notes\n- These modules use `Effect.tryPromise` for all DB/filesystem operations after PR #1236 fixes\n- Tests should use `createEEMock()` from `ee/src/__mocks__/internal.ts`\n- Consider mocking `child_process.spawn` for pg_dump/psql tests", "state": "CLOSED", "created_at": "2026-04-04T14:04:20Z", "closed_at": "2026-04-04T15:08:14Z", "author_login": "msywulak", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 1238, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["chore", "area: testing"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Automattic_wp-calypso_89760.json

@@ -0,0 +1 @@
+{"number": 89760, "title": "Remove processing step: Create a new instructions step", "body": "# Goal\r\nShow the pre-migration steps progress directly on the site migration instructions.\r\n\r\nThe overall idea is to show a list of processes we are running as part of the site instructions, and only make the site migration key available when all of them are done.\r\n\r\n## Context\r\nAfter we launched the new site migration flow, we noticed users were dropping off the flow, on loading screens before seeing the instructions page. We want to remove the loading steps and show them directly on the instruction page the -pre-migration progress. \r\n\r\nMore details on paYKcK-4qU-p2\r\nThe initial idea is to have something like this, but it is still totally open to other suggestions.\r\n\r\n![image](https://github.com/Automattic/wp-calypso/assets/38718/8b3b54ed-6f65-44b9-bc02-a6307458d9c4)\r\n\r\n```[tasklist]\r\n### Tasks\r\n- [ ] https://github.com/Automattic/wp-calypso/pull/90086\r\n- [ ] https://github.com/Automattic/wp-calypso/pull/90092\r\n- [ ] https://github.com/Automattic/wp-calypso/pull/90097\r\n- [x] Implement hook to manage the plugin installation, site transfer\r\n- [x] #90143\r\n```\r\n", "state": "CLOSED", "created_at": "2024-04-22T16:20:54Z", "closed_at": "2024-05-03T08:59:25Z", "author_login": "andres-blanco", "comment_rounds": [{"comments": [{"id": "IC_kwDOArzw_857qjBt", "body": "**Support References**\n\n*This comment is automatically generated. Please do not edit it.*\n\n\n- [ ] paYKcK-4qU-p2#comment-3305\n", "createdAt": "2024-04-24T11:43:45Z", "updatedAt": "2024-04-24T11:43:45Z", "author": {"login": "github-actions"}}, {"id": "IC_kwDOArzw_857sRFD", "body": "Here's a proposal for the step based on the wireframe above:\r\n\r\n\r\nhttps://github.com/Automattic/wp-calypso/assets/4933/da0c3d6d-60e8-4b45-b6ce-96387aff5ffb\r\n\r\n\r\nFigma file: 5yhaC6umexdQLlLpCrCyEe-fi-2982_3021", "createdAt": "2024-04-24T15:20:14Z", "updatedAt": "2024-04-24T15:20:14Z", "author": {"login": "javierarce"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 90143, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["Enhancement", "Customer report [LEGACY]", "[Feature] Site Migration"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Automattic_wp-calypso_93302.json

@@ -0,0 +1 @@
+{"number": 93302, "title": "Step: How would you like to migrate?", "body": "### Details\r\n\r\nIntegrate the \"How would you like to migrate?\" step into the flow. It will use the existing step from other flows.\r\n\r\n![Screenshot 2024-08-06 at 19 15 24](https://github.com/user-attachments/assets/443a2c2e-17a7-4f0a-9826-ac362f7e76a8)\r\n\r\nThis step will always be displayed after the checkout.\r\n\r\n### Checklist\r\n\r\n- [ ] The new step is integrated into the flow.\r\n\r\n### Related\r\n\r\nhttps://github.com/Automattic/wp-calypso/issues/93258", "state": "CLOSED", "created_at": "2024-08-06T22:04:51Z", "closed_at": "2024-08-14T17:12:30Z", "author_login": "renatho", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 93465, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["Task"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Automattic_wp-calypso_94670.json

@@ -0,0 +1 @@
+{"number": 94670, "title": "Hosting Overview: 'Need more storage?' is not a hyperlink", "body": "### Quick summary\n\nUnlike all the other blue hyperlinks on the Hosting Overview page, the `Need more storage?` is not a working link.\r\n\r\n![Screenshot on 2024-09-18 at 15:16:58](https://github.com/user-attachments/assets/7d55c245-4072-4340-95be-9a895299aaa9)\r\n\r\nWhen I look at the code responsible for `Need more storage?` at https://github.com/Automattic/wp-calypso/blob/9db92b03c1ef48744601224b37f5cc61e0a77d4d/client/hosting/overview/components/plan-card.tsx#L307-L311 I can see there is a `<span>` and there is no `<a>` with a `href=`.\r\n\n\n### Steps to reproduce\n\n1. Navigate to `https://wordpress.com/overview/SITE_URL` on any of Atomic sites\r\n2. Hover over or click `Need more storage?`\n\n### What you expected to happen\n\nBe able to click and navigate to `https://wordpress.com/add-ons/SITE_URL`\n\n### What actually happened\n\nNothing. \n\n### Impact\n\nMost (> 50%)\n\n### Available workarounds?\n\nNo but the platform is still usable\n\n### If the above answer is \"Yes...\", outline the workaround.\n\n_No response_\n\n### Platform (Simple and/or Atomic)\n\nAtomic\n\n### Logs or notes\n\nFYI: I know @Automattic/letero has recently worked on Hosting Overview refinements pcYYuD-1Pw-p2", "state": "CLOSED", "created_at": "2024-09-18T13:24:27Z", "closed_at": "2024-09-19T14:50:25Z", "author_login": "zdenys", "comment_rounds": [{"comments": [{"id": "IC_kwDOArzw_86Mk49R", "body": "This is a regression caused by https://github.com/Automattic/wp-calypso/pull/94144\r\n\r\nGrabbing this for Letero's board", "createdAt": "2024-09-18T13:30:39Z", "updatedAt": "2024-09-18T13:30:39Z", "author": {"login": "fredrikekelund"}}, {"id": "IC_kwDOArzw_86MlYXw", "body": "\ud83d\udccc REPRODUCTION RESULTS\r\n- Tested on Simple \u2013 Could Not Replicate\r\n- Tested on Atomic \u2013 Replicated\r\n\r\n\ud83d\udccc FINDINGS/SCREENSHOTS/VIDEO\r\nOn Simple sites, the link is linking to the plans page https://wordpress.com/plans/{site_url}\r\n\r\n\ud83d\udccc ACTIONS\r\n- Triaged", "createdAt": "2024-09-18T14:19:03Z", "updatedAt": "2024-09-18T14:19:03Z", "author": {"login": "jartes"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 94702, "link_type": "closing_keyword", "will_close": true, "comment_count": 2, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["Bug", "[Pri] High", "[Feature] Calypso & wp-admin Navigation", "Triaged", "[Platform] Atomic", "[Status] Priority Review Triggered", "[Product] WordPress.com", "[Feature Group] Other Infrastructure"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Automattic_wp-calypso_94782.json

@@ -0,0 +1 @@
+{"number": 94782, "title": "Feature Request - More Urgent Warning of Irreversible Data Loss When Resetting a Site", "body": "### What\n\nIn General Site Settings, there is a link for the user to reset the site. This leads to https://wordpress.com/settings/start-over/{defaultURL}\r\n\r\nThe user is required to enter their site URL to confirm that content will be removed, but I feel that warning of irreversible data loss is not urgent enough for Simple sites.\r\n\r\nI suggest adding a message in red text above or below where the user would enter their site URL to remind them that this process is irreversible, to accompany the message that is already displayed, prompting them to export a backup:\r\n\r\n>To keep a copy of your current site, head to the Export page before starting the reset.\n\n### Why\n\nDue to the risk of irreversible data loss, I think it bears giving a more urgent reminder that the reset cannot be reversed.\n\n### How\n\n_No response_", "state": "CLOSED", "created_at": "2024-09-20T17:03:17Z", "closed_at": "2025-04-09T00:48:21Z", "author_login": "masperber", "comment_rounds": [{"comments": [{"id": "IC_kwDOArzw_86WQ31k", "body": "\ud83d\udccc ACTIONS\n- Triaged\n- Requested author feedback\n- Feature request kept\n\n\n\ud83d\udccc Message to Author\n@masperber I'm not sure people will read warnings at all even if they are in red, but perhaps an \"Export Content\" button could help! Keeping this request.", "createdAt": "2024-12-05T17:29:15Z", "updatedAt": "2024-12-05T17:29:15Z", "author": {"login": "supernovia"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 101763, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["[Feature] Site Settings", "Feature Request", "[Product] WordPress.com", "[Feature Group] Site Settings & Tools"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/BBMRI-ERIC_negotiator_1027.json

@@ -0,0 +1 @@
+{"number": 1027, "title": "[FEATURE] Add webhook event triggers for negotiation lifecycle", "body": "**Brief description.**\nCurrently, webhooks are only delivered via manual API calls. Implement automatic webhook dispatch on negotiation domain events.\n\n**Desired functionality acceptance criteria**\n- Define and create domain events for negotiation lifecycle\n- Implement webhook event listeners that trigger webhooks\n- Webhooks are dispatched to all **active** webhooks\n- Integration tests verify webhooks are triggered on domain events", "state": "CLOSED", "created_at": "2026-02-09T17:09:02Z", "closed_at": "2026-02-26T11:59:44Z", "author_login": "stetsche", "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": []}

scrape_out/issues/BHoM_Robot_Toolkit_507.json

@@ -0,0 +1 @@
+{"number": 507, "title": "Handle tags as groups in Robot", "body": "<!-- PLEASE ENSURE YOU REVIEW THE CONTENT OF EACH ISSUE CAREFULLY, INCLUDING SUBSEQUENT COMMENTS BY YOURSELF OR OTHERS. -->\r\n<!-- IN PARTICULAR PLEASE ENSURE THAT SENSITIVE OR INAPPROPRIATE INFORMATION IS NOT UPLOADED -->\r\n\r\n#### Description:\r\n<!-- Describe your idea. Including details of the intended functionality, expected behaviour and desired inputs and outputs -->\r\n\r\nTo give better usage of the Tags on the BHoMObjects, especially for the elements (Nodes, Bars, Panels and FEMeshes) they should be corresponding to the groups in Robot.\r\n\r\nAdding this feature will enable easier pulling and pushing of groups into robot, and enable greater use of the FIlterRequest, with specifying the tag making it so that the particular group is pulled.\r\n\r\n", "state": "CLOSED", "created_at": "2023-02-03T10:19:18Z", "closed_at": "2023-02-22T11:10:52Z", "author_login": "IsakNaslundBh", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 508, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "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": []}

scrape_out/issues/BU-ISCIII_iskylims_198.json

@@ -0,0 +1 @@
+{"number": 198, "title": "Tables format in wetlab", "body": "### Description of feature\n\n- [ ] Remove pagination and add scroll bar to jexcel tables which are forms. Pe, in assign library protocol there should not be a pagination, but a scroll bar that allows to select all samples at once.\r\n![image](https://github.com/BU-ISCIII/iskylims/assets/3480206/f3f30c97-cf50-45d2-9e76-9efdbc4057a1)\r\n\r\n- [ ] Add pagination and proper search to dataTables after completion forms. Pe the one in the following image:\r\n![image](https://github.com/BU-ISCIII/iskylims/assets/3480206/830b8d8b-42fa-4c9b-8d4a-7548d6d5f8db)\r\n", "state": "OPEN", "created_at": "2023-07-25T15:03:45Z", "closed_at": null, "author_login": "saramonzon", "comment_rounds": [], "resolution": "open", "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": ["enhancement"], "milestone": "Release v3.2.0", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/BastiDood_drap_151.json

@@ -0,0 +1 @@
+{"number": 151, "title": "Remove confusing \"Concluded Quota\" statistic in favor of stats cards", "body": "At the end of a lab draft, a \"concluded quota\" statistic is shown. This is computed by adding the \"initial\" and \"lottery\" quotas of a lab for the draft. The issue is that this statistic is rather confusingly defined and does not seem to be particularly useful. Thus, it would be best if we remove this in favor of more understandable statistics.", "state": "CLOSED", "created_at": "2026-02-21T15:08:34Z", "closed_at": "2026-03-30T00:58:38Z", "author_login": "ehrelevant", "comment_rounds": [{"comments": [{"id": "IC_kwDOLJpaxc7y3gPm", "body": "allo", "createdAt": "2026-03-17T12:34:47Z", "updatedAt": "2026-03-17T12:34:47Z", "author": {"login": "ervnmrcdo"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 211, "link_type": "closing_keyword", "will_close": true, "comment_count": 1, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug", "ui", "api"], "milestone": "Draft 2026 Overhaul", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Blobscan_blobscan_418.json

@@ -0,0 +1 @@
+{"number": 418, "title": "More accurate formatting TTL function", "body": "The current Swarm blob data expiry indicator in the header is not accurate.\r\n\r\n![image](https://github.com/user-attachments/assets/f4dc723f-993d-4aa7-b6dd-d9f0a6de9c56)\r\n\r\nHere it is displayed \"a month\" although we know it is \"5 weeks\" at the moment of writing this from the swarm dashboard.\r\n\r\nMigrate from current `formatTtl()` to [secondsToTimeString](https://github.com/ethersphere/bee-dashboard/blob/master/src/utils/index.ts#L175) from bee-dashboard", "state": "CLOSED", "created_at": "2024-06-20T09:31:05Z", "closed_at": "2024-09-02T21:49:32Z", "author_login": "PabloCastellano", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 503, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["\ud83d\ude4b\u200d\u2640\ufe0f good first issue", "web"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Blobscan_blobscan_686.json

@@ -0,0 +1 @@
+{"number": 686, "title": "Prepare for Pectra fork", "body": "Pectra upgrade will increase the number of blobs to 6/9.\n\n**Pectra Schedule**\n\n* Holesky will fork at slot 3710976 (Mon, Feb 24 at 21:55:12 UTC)\n* Sepolia will fork at slot 7118848 (Wed, Mar 5 at 07:29:36 UTC)\n* Ethereum mainnet: March 2025 (TBD on March 6th)\n\nMake sure Blobscan is ready for this change. We might need to update some constants and logic in apps/web/src/utils/ethereum.ts:\n\nhttps://github.com/Blobscan/blobscan/blob/31be3e00c12370483aed67eaf51bc3ea8be57dbd/apps/web/src/utils/ethereum.ts#L3-L8\n\nTODO:\n\n* [ ] use a switch to use gas target depending on block number \n* [ ] api indexer endpoint: update calculus to determine base fee\n* [ ] ui: update gas target component\n", "state": "CLOSED", "created_at": "2025-01-21T10:58:11Z", "closed_at": "2025-02-24T16:44:45Z", "author_login": "PabloCastellano", "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": []}

scrape_out/issues/BrokkAi_brokk_1720.json

@@ -0,0 +1 @@
+{"number": 1720, "title": "expand diff under x lines in the output", "body": "- we can make this configurable but I would be fine with hard coding something like 50 lines\n- keep collapsed by default\n- expand when done\n", "state": "CLOSED", "created_at": "2025-11-06T15:27:04Z", "closed_at": "2025-11-07T17:55:49Z", "author_login": "foundev", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 1730, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["ui"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/BrokkAi_brokk_2442.json

@@ -0,0 +1 @@
+{"number": 2442, "title": "[Bug]: Session upload exceeding size limit is retried on every sync", "body": "### Brokk Version\n\nmaster\n\n### Operating System\n\nLinux\n\n### What happened?\n\nIf session upload is rejected by server due to size limitation, we keep retrying on every sync attempt:\n```\n2026-01-21 10:15:39,429 [pool-7-thread-1] WARN  SessionSynchronizer$SyncExecutor.execute:216 - Action UPLOAD failed for session 02a2e036-023f-4049-86e7-61d4080530ab: writeRemoteSession failed: 413 - {\"detail\":\"Session content exceeds size limit of 10485760 bytes.\"}\n```\n\n### Relevant log output\n\n```shell\n\n```", "state": "CLOSED", "created_at": "2026-01-21T16:43:47Z", "closed_at": "2026-01-23T08:11:09Z", "author_login": "bdragan", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 2445, "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": []}

scrape_out/issues/BrokkAi_brokk_2510.json

@@ -0,0 +1 @@
+{"number": 2510, "title": "[Bug]: False Positive in Field Usage Detection", "body": "### Describe the feature request.\n\n## The Problem\n\nThe usage search for `org.apache.commons.crypto.stream.output.ChannelOutput.channel` is incorrectly matching a **method parameter** named `channel` in `CtrCryptoInputStream`'s constructor, treating it as if it were a field access expression.\n\nLooking at the code:\n```java\nprotected CtrCryptoInputStream(final ReadableByteChannel channel, final CryptoCipher cipher,\n        final int bufferSize, final byte[] key, final byte[] iv) throws IOException {\n    this(channel, cipher, bufferSize, key, iv, 0);\n}\n```\n\nHere, `channel` is clearly a **parameter** being passed to a delegating constructor call \u2014 not a field load of `this.channel`.\n\n## Root Cause\n\nThe current `IAnalyzer.isAccessExpression` API (with default implementation returning `false`) is meant to filter out false positives, but it lacks the ability to perform **lexical scope analysis** to determine whether an identifier refers to:\n\n1. A **local variable** or **parameter** (should be excluded from field usage results)\n2. An **implicit `this.field`** access (legitimate usage)\n3. An **explicit member access** like `obj.field` (legitimate usage)\n\nWithout backwards analysis to find the nearest declaration, the system cannot distinguish between these cases when it encounters a bare identifier like `channel`.\n\n## Proposed Solution\n\n### New API: Nearest Declaration Lookup\n\nAdd a new method to `IAnalyzer` (or a capability interface) that performs backwards lexical scope analysis:\n\n```java\n/**\n * Finds the nearest lexically-enclosing declaration for an identifier at the given position.\n * \n * @param file the source file\n * @param identifierStartByte the start byte of the identifier\n * @param identifierEndByte the end byte of the identifier\n * @param identifierName the name of the identifier to resolve\n * @return information about the nearest declaration, or empty if not found\n */\nOptional<DeclarationInfo> findNearestDeclaration(\n    ProjectFile file, \n    int startByte, \n    int endByte, \n    String identifierName\n);\n```\n\nWhere `DeclarationInfo` might be:\n```java\nrecord DeclarationInfo(\n    DeclarationKind kind,  // PARAMETER, LOCAL_VARIABLE, FIELD, etc.\n    String name,\n    @Nullable CodeUnit enclosingUnit\n) {}\n\nenum DeclarationKind {\n    PARAMETER,\n    LOCAL_VARIABLE, \n    FIELD,\n    CATCH_PARAMETER,\n    FOR_LOOP_VARIABLE,\n    PATTERN_VARIABLE,  // Java 16+ pattern matching\n    UNKNOWN\n}\n```\n\n### Integration with `isAccessExpression`\n\nThe `isAccessExpression` implementation would then:\n\n1. Call `findNearestDeclaration` for the identifier\n2. If the result is `PARAMETER` or `LOCAL_VARIABLE` (or other non-field kinds), return `false` \u2014 this is **not** a field access\n3. If the result is `FIELD` or unknown, continue with existing logic\n\n### Implementation Approach in TreeSitterAnalyzer\n\nThe backwards analysis would need to:\n\n1. **Parse/retrieve the AST** for the file (via `treeOf(file)`)\n2. **Walk upward** from the identifier's position through enclosing scopes\n3. **Check each scope** for parameter lists, variable declarations, catch clauses, etc.\n4. **Return the first match** where the declaration name equals the identifier name\n\nFor Java specifically, this means checking:\n- Method/constructor **parameter lists** (formal_parameters)\n- **Local variable declarations** (local_variable_declaration)\n- **Enhanced for loops** (enhanced_for_statement)\n- **Try-with-resources** (resource_specification)\n- **Catch clauses** (catch_formal_parameter)\n- **Lambda parameters** (lambda_expression \u2192 parameters)\n- **Pattern variables** (pattern in instanceof/switch)\n\n## Issue Summary\n\n**Title:** Add lexical scope analysis to exclude local variables/parameters from field usage detection\n\n**Description:**\nField usage search incorrectly reports method parameters and local variables as potential field accesses when they share the same name as the target field. \n\n**Example false positive:**\nSearching for usages of `ChannelOutput.channel` field matches a constructor parameter named `channel`:\n```java\nprotected CtrCryptoInputStream(final ReadableByteChannel channel, ...)\n```\n\n**Proposed fix:**\n1. Add `findNearestDeclaration(file, startByte, endByte, name)` API to perform backwards lexical scope analysis\n2. Modify `isAccessExpression` to return `false` when the identifier resolves to a local variable or parameter\n3. Implement the scope walker in `TreeSitterAnalyzer` to check enclosing scopes for shadowing declarations\n\n**Affected languages:** Primarily Java, but the pattern applies to any language with lexical scoping (TypeScript, Python, Go, etc.)\n\n\n### Additional context\n\n_No response_", "state": "CLOSED", "created_at": "2026-01-29T11:34:41Z", "closed_at": "2026-01-30T08:01:03Z", "author_login": "DavidBakerEffendi", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 2516, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "code analysis"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/CAFECA-IO_iSunFA_603.json

@@ -0,0 +1 @@
+{"number": 603, "title": "\u8abf\u6574\u7a0b\u5f0f\u78bc(mock api and test)-2: status, error code and message / api response", "body": "\u7528\u5206\u652f fix/status_error_code \r\n\r\nE010001 - GET /company/:companyId/employee - ISFMK00041\r\nE010002 - GET /company/:companyId/employee/:employeeId - ISFMK00041\r\nE010003 - POST /company/:companyId/employee - ISFMK00041\r\nE010004 - DELETE /company/:companyId/employee/:employeeId - ISFMK00041\r\nE010005 - PUT /company/:companyId/employee/:employeeId - ISFMK00041\r\nR011001 - GET /company/:companyId/report_financial - ISFMK00029\r\nS020001 - GET /company/:companyId/salary - ISFMK00023\r\nS020002 - POST /company/:companyId/salary/:employeeId - ISFMK00023\r\n\r\n\u5f85\u78ba\u8a8d\r\nS030001 - POST /sign-in - ISFMK00001\r\nS040001 - POST /sign-up - ISFMK00001\r\nS050001 - POST /sign-out\r\nR012001 - POST /company/:companyId/report_analysis - ISFMK00037", "state": "CLOSED", "created_at": "2024-05-10T01:40:07Z", "closed_at": "2024-05-16T09:03:50Z", "author_login": "gibbs-shih", "comment_rounds": [{"comments": [{"id": "IC_kwDOLD3MM85-BFM5", "body": "\u7528\u65b0\u5206\u652f feature/status_error_message, \u4fee\u6539 status code, error_message, api response\r\nmock api and test\r\n- [x] E010001 - GET /company/:companyId/employee - ISFMK00041\r\n- [x] E010002 - GET /company/:companyId/employee/:employeeId - ISFMK00041\r\n- [x] E010003 - POST /company/:companyId/employee - ISFMK00041\r\n- [x] E010004 - DELETE /company/:companyId/employee/:employeeId - ISFMK00041\r\n- [x] E010005 - PUT /company/:companyId/employee/:employeeId - ISFMK00041\r\n- [x] R011001 - GET /company/:companyId/report_financial - ISFMK00029\r\n- [x] S020001 - GET /company/:companyId/salary - ISFMK00023\r\n- [x] S020002 - POST /company/:companyId/salary/:employeeId - ISFMK00023\r\n\r\n\u5f85\u78ba\u8a8d\r\n- [x] S030001 - POST /sign-in - ISFMK00001\r\n- [x] S040001 - POST /sign-up - ISFMK00001\r\n- [x] S050001 - POST /sign-out\r\n- [x] R012001 - POST /company/:companyId/report_analysis - ISFMK00037", "createdAt": "2024-05-16T07:02:31Z", "updatedAt": "2024-05-16T09:03:18Z", "author": {"login": "gibbs-shih"}}, {"id": "IC_kwDOLD3MM85-ClFm", "body": "take 6-7 hr", "createdAt": "2024-05-16T09:03:50Z", "updatedAt": "2024-05-16T09:03:50Z", "author": {"login": "gibbs-shih"}}]}], "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": ["enhancement", "8"], "milestone": "v0.8.0 Alpha Release", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/CAIIVS_raitap_197.json

@@ -0,0 +1 @@
+{"number": 197, "title": "Detection: data loader forces dense NCHW, cannot batch variable-size images", "body": "## Summary\n\nThe data loader forces every batch into a single dense `NCHW` tensor. Object-detection inputs are variable-size, so they cannot be stacked, and running `examples/udacity-fasterrcnn` through the CLI fails:\n\n```\nValueError: Images have inconsistent shapes after preprocessing:\n{(3, 451, 800), (3, 533, 800), (3, 440, 780)}.\n```\n\nThe three sample frames have different sizes. For detection, the bundled preset is intentionally a no-op (detection models resize internally), so no common-size resize runs before stacking.\n\n## Why the e2e test passes but the example does not\n\n`test_e2e_detection.py` uses `data.source = \"UdacitySelfDriving\"`, whose `_load_sample` resizes images to a common shape so they stack. The example instead points `data.source` at a directory of raw images \u2192 generic dir-loader \u2192 `np.stack` (`src/raitap/data/data.py:573`, via `_load_data` line 134-138) \u2192 fails. The native-resolution detection path was never exercised through the CLI.\n\n## Root cause\n\n`Data.tensor` is a single dense `NCHW` `torch.Tensor`; ~6 consumers assume it (`.shape`/`.shape[0]`):\n\n- `pipeline/orchestrator.py:138` \u2014 `forward_pass(..., data.tensor)`\n- `pipeline/orchestrator.py:189` \u2014 `data.tensor.shape[0]` (batch size)\n- `pipeline/phases/assess_transparency.py:104,193` \u2014 `inputs=data.tensor`\n- `pipeline/phases/assess_robustness.py:98` \u2014 FGSM input\n- `data/data.py:187,256,336,342` \u2014 shape-based validation + metadata\n\nThis dense-tensor contract contradicts the detection input contract: torchvision and detectron2 take a `List[Tensor]`, one `(C,H,W)` per image at native resolution; the padded common-canvas tensor is an internal model detail (`GeneralizedRCNNTransform` / `ImageList`), not the user input.\n\n## Why resize / pad are not acceptable fixes\n\n- **Resize to common size:** changes the pixel grid, requires rescaling annotation boxes, and diverges from the direct-library fidelity reference (which sees native resolution) \u2014 breaks the use case's fidelity check.\n- **Zero-pad to a common canvas:** the padded border becomes attributed input; IG's zero baseline coincides with the padding (degenerate border); the model's internal transform then re-pads the already-padded canvas (double transform, coords no longer map to pixels, spurious border attribution). Compounds the known preprocessing/graph issue (Captum #901).\n\n## Proposed solution\n\nRepresent a detection batch as a ragged `List[Tensor]` (native-resolution per-image), gated by detection task-kind so classification keeps its dense `NCHW` path. The ~6 consumers branch on task-kind and iterate per image for detection (forward, IG/LayerGradCam, FGSM, metrics already operate per-image / per-box; `forward_batch_size: 1` is already set in the example). This matches torchvision's input contract, Captum's per-sample attribution semantics, preserves annotation coordinates for mAP, and keeps the fidelity reference identical to the direct library call.\n\n## Sources\n\n- torchvision `GeneralizedRCNNTransform` / `ImageList`: https://github.com/pytorch/vision/blob/main/torchvision/models/detection/transform.py , https://github.com/pytorch/vision/blob/main/torchvision/models/detection/image_list.py\n- PyTorch forum, varying-size detection inputs: https://discuss.pytorch.org/t/can-i-use-torchvision-detection-models-on-batches-of-images-with-varying-sizes/133863\n- Captum #708 (scalar wrapper / per-box target), #901 (preprocessing breaks input attribution), #488 (backbone-only CAM): https://github.com/meta-pytorch/captum/issues/708 , https://github.com/meta-pytorch/captum/issues/901 , https://github.com/meta-pytorch/captum/issues/488\n- detectron2 `ImageList.from_tensors`: https://detectron2.readthedocs.io/en/v0.4.1/_modules/detectron2/modeling/meta_arch/rcnn.html\n\n## Related\n\n- Blocks the same example as #196 (preprocessing arch-resolution gap), which is the first failure on this path.\n", "state": "CLOSED", "created_at": "2026-05-24T09:54:10Z", "closed_at": "2026-05-24T21:38:35Z", "author_login": "pizzajojo", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 202, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": [], "milestone": "Phase 3", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/CARTAvis_carta-backend_1420.json

@@ -0,0 +1 @@
+{"number": 1420, "title": "Add unit tests and documentation for Image, String, File, Casacore files in the Util subfolder", "body": "Add test coverage and documentation to the Image, String, File, and Casacore files in the Util sub-folder.\nClosed with PR #1413 ", "state": "CLOSED", "created_at": "2025-03-20T11:20:07Z", "closed_at": "2025-04-29T08:22:04Z", "author_login": "Michaelazzz", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 1413, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["test implementation", "code maintenance"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/CARTAvis_carta-frontend_2396.json

@@ -0,0 +1 @@
+{"number": 2396, "title": "[enhancement] support setting a new RESTFRQ for moment image generation", "body": "This is a feature request from multiple users. \r\n\r\nCurrently we can set a new RESTFRQ in the image list widget so that the spectral axis in the spectral profiler widget can be recalculated to match spectral features in the velocity space. However, when this is applied and user selected a range of velocity to make a moment image (esp. moment 1), the resulting velocity values in the moment 1 image are not calculated using the newly defined RESTFRQ. This is currently a design defect.\r\n\r\nThe proposed changes are:\r\n1) (FROTNEND) add a new input field as \"Rest frequency\" in the moment generator dialog. Its value is sync'ed with the value in the settings dialog of the image list widget. \r\n2) (FRONTEND, BACKEND, PROTOBUF) modify protobuf message to include \"rest frequency\"\r\n3) (BACKEND) using the new \"rest frequency\" to compute moment images.   ", "state": "CLOSED", "created_at": "2024-07-15T02:28:30Z", "closed_at": "2024-09-09T12:20:28Z", "author_login": "kswang1029", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 2404, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["enhancement", "requiring backend"], "milestone": "v5.0-beta", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/CE-Programming_toolchain_646.json

@@ -0,0 +1 @@
+{"number": 646, "title": "Ti's strspn strcspn and strpbrk are broken", "body": "```c\n    char const * str = \"abcdef\";\n    char const * empty = \"\";\n\n    assert(strspn(str, empty) == 0);\n    assert(strpbrk(str, empty) == NULL);\n    assert(strcspn(str, empty) == 6);\n\n    assert(strcspn(str, \"cba\") == 0);\n    assert(strcspn(str, \"fed\") == 3);\n    assert(strcspn(str, \"eebbeb\") == 1);\n    assert(strcspn(str, \"ffaafa\") == 0);\n    assert(strcspn(empty, str) == 0);\n    assert(strcspn(empty, empty) == 0);\n```\nThe following cases fail for Ti's implementation of `strspn`, `strcspn`, and `strpbrk`. These routines will need to be replaced.\n", "state": "CLOSED", "created_at": "2025-10-03T00:38:06Z", "closed_at": "2025-10-13T00:30:16Z", "author_login": "ZERICO2005", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 650, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["bug", "libc"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/CERNDocumentServer_cds-videos_1951.json

@@ -0,0 +1 @@
+{"number": 1951, "title": "CDS Videos: search in deposit form results to search error", "body": "Here is the relevant Sentry exception: https://cds-sentry.web.cern.ch/sentry/cds-videos/issues/33973/?environment=production&referrer=alert_email", "state": "CLOSED", "created_at": "2024-09-20T08:53:46Z", "closed_at": "2025-11-11T14:40:00Z", "author_login": "zzacharo", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 2139, "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": "Video platform enhancements", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/CERNDocumentServer_cds-videos_2030.json

@@ -0,0 +1 @@
+{"number": 2030, "title": "Implement Collaboration", "body": "https://github.com/CERNDocumentServer/cds-videos/blob/main/rfcs/0001/Analysis-to-map-MarcXML-fields-to-CDSVideos.md#collaboration\n\nRole `ResearchGroup`, `Other` added to schema \nhttps://github.com/CERNDocumentServer/cds-videos/pull/2027\n\n- `710__a` corporate name translated as contributor with role `Other` if different than `CERN. Geneva`\n- `710__g` collaboration  translated as contributor with role `ResearchGroup` \n- `710__5` department translated as `_curation.department`", "state": "CLOSED", "created_at": "2025-05-15T10:00:34Z", "closed_at": "2025-05-21T08:40:22Z", "author_login": "zubeydecivelek", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 254, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["migration"], "milestone": "Weblectures migration", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/CMU-313_spring23-nodebb-green_39.json

@@ -0,0 +1 @@
+{"number": 39, "title": "Add tests for issue #2", "body": "Add automated tests for the feature added in  [issue #2](https://github.com/CMU-313/spring23-nodebb-green/issues/2)", "state": "CLOSED", "created_at": "2023-02-20T18:12:18Z", "closed_at": "2023-02-26T18:06:33Z", "author_login": "apoznanski", "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": "[Sprint 2] Testing", "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/COVESA_vss-tools_345.json

@@ -0,0 +1 @@
+{"number": 345, "title": "Add version printout", "body": "We should better add a version printout when running the tool, saying for example \"vss-tools 4.1.1\"", "state": "CLOSED", "created_at": "2024-04-05T09:02:58Z", "closed_at": "2024-07-22T10:37:23Z", "author_login": "erikbosch", "comment_rounds": [{"comments": [{"id": "IC_kwDODm87YM55k8kp", "body": "Indeed. Good plan.", "createdAt": "2024-04-05T12:51:51Z", "updatedAt": "2024-04-05T12:51:51Z", "author": {"login": "ppb2020"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 378, "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": []}

scrape_out/issues/CRPropa_CRPropa3_9.json

@@ -0,0 +1 @@
+{"number": 9, "title": "", "body": "", "state": "", "created_at": "", "closed_at": null, "author_login": "", "comment_rounds": [{"comments": [{"id": "MDEyOklzc3VlQ29tbWVudDQ0NjM0Mjcz", "body": "You need to call the constructor of the super class:\n\ndef **init** (self):\n  Module.**init**(self)\n\nAm Donnerstag, 29. Mai 2014, 23:54:34 schrieb DavidWalz:\n\n> ``` python\n> from crpropa import *\n> class Test(Module):\n>    def __init__ (self):\n>       pass\n> \n> m = ModuleList()\n> m.add(Test())\n> ```\n> \n> TypeError: in method 'ModuleList_add', argument 2 of type 'crpropa::Module\n> *'\n> \n> ---\n> \n> Reply to this email directly or view it on GitHub:\n> https://github.com/CRPropa/CRPropa3/issues/9\n", "createdAt": "2014-05-30T09:51:49Z", "updatedAt": "2014-05-30T09:51:49Z", "author": {"login": "geromueller"}}, {"id": "MDEyOklzc3VlQ29tbWVudDQ0NjQ3NTU4", "body": "Right. I'll add it to the wiki.\n\n``` python\nfrom crpropa import *\nclass Test(Module):\n   def __init__ (self):\n      Module.__init__(self)\n\nm = ModuleList()\nm.add(Test())\n```\n", "createdAt": "2014-05-30T12:59:27Z", "updatedAt": "2014-05-30T12:59:27Z", "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": []}

scrape_out/issues/Card-Forge_forge_10214.json

@@ -0,0 +1 @@
+{"number": 10214, "title": "Realm of Legends: Remove Chaos Option", "body": "Currently, the 'chaos' deck option is broken on realm of legends since it requires 60 card decks. I only left it in because it currently can't be removed, but users are picking it and complaining the game is broken.\n\nIf someone could figure out how to remove it as an option for Realm of Legends, that'd be great.\n", "state": "CLOSED", "created_at": "2026-03-29T16:26:36Z", "closed_at": "2026-04-02T10:00:51Z", "author_login": "VigilantSera", "comment_rounds": [{"comments": [{"id": "IC_kwDOHJqLYM7340Ya", "body": "If someone ever does get around to working on/implementing this you have my blessing to just go ahead and implement it in realm of legends; not that you really need my permission.", "createdAt": "2026-03-30T23:51:45Z", "updatedAt": "2026-03-30T23:52:05Z", "author": {"login": "VigilantSera"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 10224, "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": []}

scrape_out/issues/Card-Forge_forge_3156.json

@@ -0,0 +1 @@
+{"number": 3156, "title": "Feature Request: Remove Ashnod's Altar/Phyrexian Altar from autotapper", "body": "**Is your feature request related to a problem? Please describe.**\r\nMost of the time, since I'm aware of the issue, I try to manually tap for mana when I have either Ashnod's Altar or Phyrexian Altar out, but sometimes (often) you just forget... The sac'ing of creatures when other options are *always* better is really bad, like: \"I have to exit the game bad, 'cause Forge just ended my board.\" \r\n\r\nThe most egregious just happened a few days ago, which is what prompted me to try to ask for this in the first place. I had a very strong board and six treasures ready to be tapped, plus Phyrexian Altar. I, thinking that surely Forge would be smart enough to tap and sac the obvious SIX treasures for mana when I cast a 6CMC card, didn't even think about being warry of the autotapper... The game sac'd all six of my creatures to Phyrexian Altar instead of using the six treasures. I had to quit.\r\n\r\n**Describe the solution you'd like**\r\nJust completely remove Ashnod's Altar and Phyrexian Altar from any kind of autotapping solution. Just don't allow it. If you don't allow it, then Forge can't kill your creatures due to a user's innocent \"error\" when other much better options are present. \r\n\r\nI know I can't be the only person who has had this issue, so why not just resolve this once and for all? I don't know how hard it would be, maybe very hard, but leaving an obvious problem in and just saying \"it's your fault for not tapping manually\" is kinda not cool.\r\n\r\nAnywho, I really, really do love Forge and I use it a lot. I understand that this is all volunteer and no one gets paid for this project of love, but it *is* a project of love, so maybe show a little bit more love and fix this frustration/rage inducing interaction?\r\n", "state": "CLOSED", "created_at": "2023-05-25T21:38:01Z", "closed_at": "2023-08-20T22:39:06Z", "author_login": "TheLastNarwhal", "comment_rounds": [{"comments": [{"id": "IC_kwDOHJqLYM5dN-2j", "body": "imo the Autotapper should prefer to sacrifice (non-creature) treasure token before trying to sacrifice creatures", "createdAt": "2023-05-26T07:38:58Z", "updatedAt": "2023-05-26T07:38:58Z", "author": {"login": "Hanmac"}}, {"id": "IC_kwDOHJqLYM5dRcMY", "body": "Agreed. I also want to say that I've had the autotapper sacrifice creatures instead of tapping pain lands like Mana Confluence. This is another instance where sometimes you just have to quit, because, in my case, it sac'd the creature I was trying to combo with. All in all, if possible, these two cards should really be taken off the menu for the autotapper.", "createdAt": "2023-05-26T19:47:37Z", "updatedAt": "2023-05-26T19:47:37Z", "author": {"login": "TheLastNarwhal"}}]}, {"comments": [{"id": "IC_kwDOHJqLYM5fygMg", "body": "This issue has not been updated in a while and has now been marked as stale. Stale messages will be auto closed.", "createdAt": "2023-06-26T09:29:37Z", "updatedAt": "2023-06-26T09:29:37Z", "author": {"login": "github-actions"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 3657, "link_type": "closing_keyword", "will_close": true, "comment_count": 3, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["AI", "keep"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Card-Forge_forge_4693.json

@@ -0,0 +1 @@
+{"number": 4693, "title": "AI makes illegal choices when triggering Volo's Journal", "body": "Windows, current snapshot.\r\n\r\nThe AI had `Volo, Itinerant Scholar` [CLB], and his journal. It cast `Shimmering Efreet` [VIS] which has the creature type Efreet, triggering journal, and chose Sliver. There's no effect making that a valid choice. I tested it myself and was correctly limited to choosing types that the spell actually had, so I guess it's just that the AI choice isn't made from the restricted set.", "state": "CLOSED", "created_at": "2024-02-15T11:54:14Z", "closed_at": "2024-12-06T14:13:24Z", "author_login": "Samthere", "comment_rounds": [{"comments": [{"id": "IC_kwDOHJqLYM5z_gBP", "body": "It continues to pick Sliver on subsequent casts, which also shouldn't be possible:\r\n\r\n![image](https://github.com/Card-Forge/forge/assets/29505281/fa190636-d75d-40ec-abb6-bf37f6c33833)\r\n\r\nIt wasn't activating the ability, so I took over its turn, and it drew a card for each individual instance of \"Sliver\". This is probably correct, it just shouldn't be possible to note the same creature type multiple times without some other effect. I cast some more creatures while in control of the AI and the ability triggered normally. I checked that \"Sliver\" wasn't just the word showing incorrectly, but it let me choose Efreet as well.\r\n\r\nHowever, it correctly didn't get another creature type noted when it cast a morph creature.\r\n", "createdAt": "2024-02-15T12:43:32Z", "updatedAt": "2024-02-15T12:43:32Z", "author": {"login": "Samthere"}}]}, {"comments": [{"id": "IC_kwDOHJqLYM53WdzA", "body": "This issue has not been updated in a while and has now been marked as stale. Stale messages will be auto closed.", "createdAt": "2024-03-17T09:26:31Z", "updatedAt": "2024-03-17T09:26:31Z", "author": {"login": "github-actions"}}]}, {"comments": [{"id": "IC_kwDOHJqLYM54Fa_X", "body": "This issue was closed because it has been stalled for 5 days with no activity.", "createdAt": "2024-03-22T09:26:39Z", "updatedAt": "2024-03-22T09:26:39Z", "author": {"login": "github-actions"}}]}], "resolution": "closed_manually", "closed_by_pr": null, "link_type": "closing_keyword", "will_close": true, "comment_count": 3, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["BUG", "keep"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/Card-Forge_forge_9654.json

@@ -0,0 +1 @@
+{"number": 9654, "title": "Portrait mode UI not working in most recent nightly snapshots (2.0.10) desktop version.", "body": "\nAfter downloading the most recent snapshot 2.0.10, the Portrait UI is no longer functional, it uses a stretched landscape mode in both adventure and classic modes through the adventure exe. confirmed portrait mode was working in 2.0.08 & 2.0.09\n\n**To Reproduce**\nSteps to reproduce the behavior:\n1. Go to forge-adventure.exe on a portrait monitor\n2. Click on either adventure or classic \n3. See error\n\n**Expected behavior**\nUse the proper Portrait UI that existed in in previous version when detected a monitor that is taller than it is wider\n\n**Screenshots**\n\n<img width=\"2045\" height=\"2729\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/03c4e0b4-0adf-4840-9a24-074eeef8cba9\" />\n<img width=\"2028\" height=\"2705\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/eae71655-ce75-4efc-85d7-bed8f761266c\" />\n<img width=\"2038\" height=\"2722\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/593ca600-251f-4ec5-b778-0afc23795bab\" />\n\n**Desktop (please complete the following information):**\n - OS: Windows 11\n\n\n**Additional context**\ni have tried on a normal monitor in portrait mode + a tablet in portrait mode using a virtual display and the bug exists on both\n", "state": "CLOSED", "created_at": "2026-02-02T10:02:44Z", "closed_at": "2026-03-04T17:18:59Z", "author_login": "Lunar-Rivers", "comment_rounds": [{"comments": [{"id": "IC_kwDOHJqLYM7kiiyX", "body": "Likely #9394 broke something?\n\n@krafczyk \nplease look into it", "createdAt": "2026-02-02T10:26:31Z", "updatedAt": "2026-02-02T10:26:31Z", "author": {"login": "tool4ever"}}, {"id": "IC_kwDOHJqLYM7kt5Uu", "body": "I believe I've got a fix, but I need to test it.", "createdAt": "2026-02-02T19:48:22Z", "updatedAt": "2026-02-02T19:48:22Z", "author": {"login": "krafczyk"}}, {"id": "IC_kwDOHJqLYM7lJ012", "body": "@Lunar-Rivers while I'm fixing this bug properly, you should be able to add the option `portrait` after `-jar <jarname>` in your `forge-adventure.cmd` launcher command to get the portrait GUI back.", "createdAt": "2026-02-04T00:28:05Z", "updatedAt": "2026-02-04T00:28:05Z", "author": {"login": "krafczyk"}}]}, {"comments": [{"id": "IC_kwDOHJqLYM7l96rv", "body": "@tool4ever, I've done all the testing I can on #9676, This bug should be solved with that PR.", "createdAt": "2026-02-06T06:06:03Z", "updatedAt": "2026-02-06T06:06:03Z", "author": {"login": "krafczyk"}}]}], "resolution": "closed_by_pr", "closed_by_pr": 9676, "link_type": "closing_keyword", "will_close": true, "comment_count": 4, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["GUI", "Mobile"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/ChainSafe_gossamer_4000.json

@@ -0,0 +1 @@
+{"number": 4000, "title": "(pkg/trie): Merkle proof generation", "body": "Similar [what we have with in-memory tries](https://github.com/ChainSafe/gossamer/blob/development/pkg/trie/inmemory/proof/generate.go), we need to implement a similar merkle proof generation using our new TrieDB structure.", "state": "CLOSED", "created_at": "2024-06-03T14:36:38Z", "closed_at": "2024-07-19T16:51:12Z", "author_login": "dimartiro", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 4082, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["C-complex", "T-feat", "S-trie"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}

scrape_out/issues/ChainSafe_gossamer_4112.json

@@ -0,0 +1 @@
+{"number": 4112, "title": "Refactor sync package to use the strategy approach", "body": "## Issue summary\r\n<!-- A clear and concise description of what the task is. -->\r\n- Currently, Gossamer sync package is full writing for full sync method, so everything in the sync package is a lot coupled and there is no room to expand or introduce a new sync strategy, such as Warp Sync, without a huge code change.\r\n\r\n- What I am proposing here is to change the sync package a single `SyncService` and this service contains a strategy that can be `FullSyncStrategy` or `WarpSyncStrategy` both implementing the interface `Strategy` and all that the `SyncService` knows is that it has a property `strategy` of type `Strategy`.\r\n\r\n- The `SyncService` works in a loop that execs the following actions:\r\n\r\n1. Acquire the `strategy.NextActions()`\r\n2. Execute the next actions\r\n3. Pass the results to `strategy.IsFinished()`\r\n4. Check if the strategy is done, if so move to the default strategy, otherwise go to step 1\r\n\r\n- The implementation of the `Strategy` interface does not need to have any knowledge about network or workers, it should only know about its current state like: forks, fragments, blocks announced\r\n\r\nThe approach is explained in this PDF\r\n[WARP Sync slides (1).pdf](https://github.com/user-attachments/files/16443419/WARP.Sync.slides.1.pdf)\r\n", "state": "CLOSED", "created_at": "2024-07-31T14:43:47Z", "closed_at": "2024-09-30T15:31:09Z", "author_login": "EclesioMeloJunior", "comment_rounds": [], "resolution": "closed_by_pr", "closed_by_pr": 4114, "link_type": "closing_keyword", "will_close": true, "comment_count": 0, "issue_age_at_pr_days": null, "issue_was_open_at_pr": null, "labels": ["S-network", "C-complex", "T-enhancement", "P-high"], "milestone": null, "sub_issues": [], "sub_issue_count": 0, "parent_issues": []}