data/queries/dev.jsonl

{"query_id":"cross_issue_0003","query":"[Epic] Horizontally scalable request layer (e.g. `pgwired`)?","query_context":"At the moment, all communication from clients goes through `environmentd`, which maintains the catalog, performs optimization, sends requests to `clusterd`, and passes results back to the client. Both data and control are multiplexed on the same connection.\n\nThe result of this multiplexing is\n* increased effort for `environmentd` to provide data to clients,\n* inability to restart independently of client connections, and\n* risk of exhausting resources within `environmentd`.\n\nEdit: Renamed the new component to `pgwired` based on feedback.\n\n## Goals\n\nSplit the control and data plane into separate entities. This could be achieved using the following approach:\n* Introduce an `pgwired` that accepts client connections, forwards requests to `environmentd`, and collects results from `environmentd` or `computed` directly.\n* `environmentd` maintains its current responsibility but does not transfer data from `computed` to clients because that data is exchanged directly.\n* `computed` hands the result of inserts directly to `persist` instead of passing data through `environmentd`\n* `pgwired` needs to be stateless to avoid conflicts with `environmentd`'s state.\n* The rollout needs to happen in a backwards-compatible fashion.\n\n## Non-goals\n\n* Move more processing, such as optimization, out of `environmentd`.\n\n## Tasks\n\n* Design the structure of `pgwired`\n * Derive a minimal protocol that allows `pgwired` to discover which services it needs to talk to.\n* Implement the protocol between `pgwired` and `computed`, while preserving the existing communication channel.\n\n## Alternatives\n\n* Use Persist to move data between components of the system.","reference_answer":"from @ georgewfraser (thanks!), lightly edited and shared with permission:\n\nYou can get most of Fivetran's commands if you set up postgres as a source (henceforth, \"upstreamdb\") and set up a new postgres database as a destination (henceforth, \"downstreamdb\"). Instrument downstreamdb with statement level logging and do the following operations:\n\nCreate a few tables in upstreamdb, add some data, and connect it to fivetran. Fivetran should do an initial load of all the data (into fivetran's internal representation).\n\n* Sync a table to downstreamdb.\n * On the first sync Fivetran should copy straight into the table (this is DWH dependent, so lets see what happens).\n* Run some inserts in upstreamdb, then sync again.\n * You should see Fivetran create a separate staging table and then move the data from there.\n* Run some updates in upstreamdb and then sync again. \n * Be sure to update multiple columns, and try a few variations.\n * You'll see us do some funky update queries that do a \"patch\" operation. They're long but they follow a simple template.\n* Sync some DELETES.\n * You'll see some slightly different update queries.\n* Add a column.\n * We'll add the column in the destination.\n* Change the type of a column.\n * We'll migrate the data in-place in the destination.\n* Click resync in the Fivetran UI.\n * We'll do a \"mass update\" where we flag any rows that didn't get resynced as deleted.\n* All of these queries will be slightly different in \"history mode\" vs \"live mode\" (ed: i don't know what this means, perhaps it is obvious from Fivetran UI). \n * History mode isn't widely available yet though, and it's probably best to just start with live mode.","answer_document_id":"gh_comment_755764601","silver_evidence_path":["gh_comment_1242851542","gh_issue_778157642","gh_comment_755764601"],"known_context_document_ids":["gh_issue_1358985263"],"evidence_issue_ids":[1358985263,778157642],"source_repo_name":"MaterializeInc/materialize","source_issue_id":1358985263,"source_issue_url":"https://github.com/MaterializeInc/materialize/issues/14568","target_repo_name":"MaterializeInc/materialize","target_issue_id":778157642,"target_issue_url":"https://github.com/MaterializeInc/materialize/issues/5188","split":"dev","quality_score":94.15,"annotation_level":"silver"}
{"query_id":"cross_issue_0020","query":"External hostname is not updated if an ingress is added *after* relating a charm to Prometheus?","query_context":"### Bug Description\n\nSee title. If you first relate to Prometheus and then to Traefik, it all works as expected. The other way around, no cigar.\n\n### To Reproduce\n\n-\n\n### Environment\n\n-\n\n### Relevant log output\n\nshell\n-\n\n### Additional context\n\nWe could have used the ingress established/revoked events, but these are unfortunately fired prematurely","reference_answer":"So basically, what I think would make sense here:\n\nAn optional argument, per consumer, to turn path-prefix-stripping on and off. It should take whatever path prefix it is using for that route and add it to the middleware's list of path's to strip. As an example:\n\n- Jon is instantiating the traefik consumer in his `zinc-k8s` charm.\n- Jon is, either implicitly or explicitly, setting the `strip_path_prefix` argument to `True`.\n- Traefik adds a route, with the path prefix `/jons-cool-model-zinc-k8s`, resulting in the full routable URL ` URL \n- Traefik also adds a strip path prefix middleware for `/jons-cool-model-zinc-k8s`.\n- The workload app will no longer have to know that it is being reverse proxied and will continue to work, as long as all of the links it renders are relative.","answer_document_id":"gh_comment_1265451573","silver_evidence_path":["gh_comment_1277474331","gh_issue_1207565669","gh_comment_1265451573"],"known_context_document_ids":["gh_issue_1381005452"],"evidence_issue_ids":[1381005452,1207565669],"source_repo_name":"canonical/prometheus-k8s-operator","source_issue_id":1381005452,"source_issue_url":"https://github.com/canonical/prometheus-k8s-operator/issues/368","target_repo_name":"canonical/traefik-k8s-operator","target_issue_id":1207565669,"target_issue_url":"https://github.com/canonical/traefik-k8s-operator/issues/45","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0027","query":"[Question] longhorn-conversion-webhook container not starting error, failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: eaccess /usr/local/sbin/longhorn-manager: permission denied: unknown?","query_context":"**Question:**\n\nI am open this as Question, because this is my first Longhorn storage installation on Kubernetes cluster (Multi Master HA setup), Feels like issue with some container permission while accessing /usr/local/sbin/longhorn-manager while provisioning container.\nafter applying the longhorn.yaml version v1.3.2, non of pods are getting started throwing error \"CrashLoopBackOff\" for longhorn-manager and convention-webhook pods. Looking at Kubernetes pod logs, in longhorn-conventional-webhook container its showing with the message: \" unable to start container process: eaccess /usr/local/sbin/longhorn-manager: permission denied: unknown\"\n\nWhat more can I look at to diagnose this issue? Is my volume configured incorrectly somehow? Did I miss a setup step somewhere?\n\nEnvironment Setup\nLonghorn version: v1.3.2\nKubernetes version: v1.24.0\nNode config\nOS type and version: Rhel 8\nCPU per node: 4\nMemory per node: 8gb & 16gb\nDisk type: XFS\nNetwork bandwidth and latency between the nodes: I don't have numbers, but they are all running on the same physical server\nUnderlying Infrastructure (e.g VMWare/KVM, Baremetal): KVM\n\n**Additional context**\nMy basic setup is that I have multiple K8s nodes running inside KVM virtual machines provisioned with libvirt. The K8S nodes are running rhel8. I have ensured that nfs-common and open-iscsi are both installed. Everything is running the latest version give or take a week. Each K8S VM has a 300gb XFS volume mounted at /var/lib/longhorn.","reference_answer":"You can manually hide the private information, or you can send the support bundle to longhorn-support-bundle@suse.com which is only accessible by Longhorn members.","answer_document_id":"gh_comment_2176532828","silver_evidence_path":["gh_comment_2176162185","gh_issue_2359706899","gh_comment_2176532828"],"known_context_document_ids":["gh_issue_1749022121"],"evidence_issue_ids":[1749022121,2359706899],"source_repo_name":"longhorn/longhorn","source_issue_id":1749022121,"source_issue_url":"https://github.com/longhorn/longhorn/issues/6090","target_repo_name":"longhorn/longhorn","target_issue_id":2359706899,"target_issue_url":"https://github.com/longhorn/longhorn/issues/8780","split":"dev","quality_score":94.85,"annotation_level":"silver"}
{"query_id":"cross_issue_0036","query":"error message using this step?","query_context":"Hi,\nI set this first step in our workflow:\n\n - name: Cancel Previous Runs\n uses: styfle/cancel-workflow-action@0.11.0\n\nI did 2 pushes (first, and second) one after another to check how it works.\nI see this message in the logs:\n`Error while canceling workflow_id 5888667: Resource not accessible by integration`\n\nWhy did it happen?","reference_answer":"Makes sense, as long as we can provide examples for each of the `Advanced:` use cases in the readme.\n\nWould you like to submit a PR?","answer_document_id":"gh_comment_1316300915","silver_evidence_path":["gh_comment_1379695924","gh_issue_1448551601","gh_comment_1316300915"],"known_context_document_ids":["gh_issue_1528923107"],"evidence_issue_ids":[1528923107,1448551601],"source_repo_name":"styfle/cancel-workflow-action","source_issue_id":1528923107,"source_issue_url":"https://github.com/styfle/cancel-workflow-action/issues/200","target_repo_name":"styfle/cancel-workflow-action","target_issue_id":1448551601,"target_issue_url":"https://github.com/styfle/cancel-workflow-action/issues/191","split":"dev","quality_score":82.09,"annotation_level":"silver"}
{"query_id":"cross_issue_0042","query":"[image_picker] image_picker: ^1.0.7 image revert issue in IOS?","query_context":"### Steps to reproduce\n\n1. get the image from library/gallery or capture it from camera(only front camera)\n2. select and show it\n3. all images are inverted like a mirror in IOS devices only are inverted\n\n### Expected results\n\nThe image must be the same as placed in the gallery or captured by camera using the front camera.\n\n### Actual results\n\nImages are inverted in IOS when choosing from library/gallery using ImagePicker().pickImage(ImageSource.gallery) or captured by camera using ImagePicker().pickImage(ImageSource.camera).\n\n### Code sample\n\nImagePicker().pickImage(source:text == StringConstants.loadFromLibrary ? ImageSource.gallery : ImageSource.camera).then((value) async {\nif (value != null) {\nList imageBytes = File(value.path).readAsBytesSync();\nString _base64Image = base64Encode(imageBytes);\n}\n}).onError((err, stackTrace) {\ndebugPrint(err.toString());\n});\n\n### Screenshots or Video\n\n \n Screenshots / Video demonstration \n\n[Upload media here]\n\n \n\n### Logs\n\n Logs \n\nconsole\n[Paste your logs here]\n\n \n\n### Flutter Doctor output\n\nFlutter (Channel stable, 3.16.7, on Microsoft Windows [Version 10.0.19044.3086], locale en-US)\n• Flutter version 3.16.7 on channel stable at D:\\dev\\projects\\flutter\n• Upstream repository URL \n• Framework revision URL (3 months ago), 2024-01-11 15:19:26 -0600\n• Engine revision 4a585b7929\n• Dart version 3.2.4\n• DevTools version 2.28.5\n\nNote: the bug is only generating in case of front camera images that are placed in gallery or captured from camera.","reference_answer":"When taking selfie in native camera at on Android devices, they are correcting the mirror effect, this is a useful feature to be baked into the `camera` package instead of modifing the image using `Transform` widget\nThanks for the issue!","answer_document_id":"gh_comment_789551119","silver_evidence_path":["gh_comment_2063059413","gh_issue_407865675","gh_comment_789551119"],"known_context_document_ids":["gh_issue_2242954070"],"evidence_issue_ids":[2242954070,407865675],"source_repo_name":"flutter/flutter","source_issue_id":2242954070,"source_issue_url":"https://github.com/flutter/flutter/issues/146751","target_repo_name":"flutter/flutter","target_issue_id":407865675,"target_issue_url":"https://github.com/flutter/flutter/issues/27650","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0045","query":"residual and capacity do not have the value returned by the API?","query_context":"### Mark\n\nPeugeot\n\n### Model\n\ne208\n\n### Year\n\n2020\n\n### Engine\n\nElectric\n\n### Remote service\n\nE-remote control\n\n### HomeAssistant version\n\nlast\n\n### Integration version\n\nlast\n\n### What happened?\n\nHi, I think there is a problem with the display of battery capacity and remaining values.\nthe percentage does not correspond to the displayed values either\n\nAPI log : \n'preconditioning': {'airConditioning': {'createdAt': '2025-08-19T06:47:53Z', 'updatedAt': '2025-08-19T06:47:53Z', 'status': 'Disabled'}}, 'energies': [{'createdAt': '2025-08-10T02:12:28Z', 'type': 'Electric', 'subType': 'ElectricEnergy', 'level': 41.0, 'autonomy': 160, 'extension': {'electric': {'battery': {'load': {'createdAt': '2025-08-10T02:12:28Z', **'capacity': 46176, 'residual': 18688}},** 'charging': {'plugged': False, 'status': 'Disconnected', 'chargingRate': 0, 'chargingMode': 'No', 'nextDelayedTime': 'PT22H5M', 'schedule': []}}}}], 'preconditionning': {'airConditioning': {'createdAt': '2025-08-19T06:47:53Z', 'updatedAt': '2025-08-19T06:47:53Z', 'status': 'Disabled'}}, 'energy': [{'createdAt': '2025-08-10T02:12:28Z', 'updatedAt': '2025-08-19T06:47:53Z', 'type': 'Electric', 'level': 41.0, 'autonomy': 160, 'charging': {'plugged': False, 'status': 'Disconnected', 'chargingRate': 0, 'chargingMode': 'No', 'nextDelayedTime': 'PT22H5M'}}]}\n\nintegration value in yellow :\n\n \n\n \n\n### Log output\n\nshell","reference_answer":"Unfortunally stellantis dont provide the specific type of hybrid.\nThe only way is to remove capacity and residual for all hybrids on next release.","answer_document_id":"gh_comment_3012288415","silver_evidence_path":["gh_comment_3207555401","gh_issue_3171387380","gh_comment_3012288415"],"known_context_document_ids":["gh_issue_3333286707"],"evidence_issue_ids":[3333286707,3171387380],"source_repo_name":"andreadegiovine/homeassistant-stellantis-vehicles","source_issue_id":3333286707,"source_issue_url":"https://github.com/andreadegiovine/homeassistant-stellantis-vehicles/issues/264","target_repo_name":"andreadegiovine/homeassistant-stellantis-vehicles","target_issue_id":3171387380,"target_issue_url":"https://github.com/andreadegiovine/homeassistant-stellantis-vehicles/issues/208","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0048","query":"Receive from dashboard?","query_context":"As a fast-follow for send, we need to design a way to handle \"Send\" & \"Receive\" as global action.\nThis issue is about the Receive part that is delivered separately.\n\nAC:\n- User is able to trigger receive from homepage \n- User is able to choose or create new account for receiving \n\nDesigns: URL","reference_answer":"Missing Cardano Send feature is something that has to be handled here. And even if we unblock the ADA send and implemented, it will probably be available only on 2.8.7 FW and not older (since the ADA send flow has been changed in that version). URL","answer_document_id":"gh_comment_2603965598","silver_evidence_path":["gh_comment_2603958190","gh_issue_2801051938","gh_comment_2603965598"],"known_context_document_ids":["gh_issue_2770798238"],"evidence_issue_ids":[2770798238,2801051938],"source_repo_name":"trezor/trezor-suite","source_issue_id":2770798238,"source_issue_url":"https://github.com/trezor/trezor-suite/issues/16204","target_repo_name":"trezor/trezor-suite","target_issue_id":2801051938,"target_issue_url":"https://github.com/trezor/trezor-suite/issues/16484","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0063","query":"None or multiple MFA types potentially break login flow?","query_context":"This needs investigation to replicate, but there is a possiblity that if:\n\nA user has no MFA setup on their amazon account, they will be prompted to set it up after a successful login. Which breaks the flow.\n\nA user has multiple forms of MFA setup on their amazon account, they might be presented with a different version of the MFA form. Which breaks the login flow.","reference_answer":"@mmstano when you say you cleared cookies and history - I meant the ones the server application (the add-on) stores, not your browsers. Perhaps a misunderstanding there because I said cookies, because that's what I called one of the files it generates haha. Probably a poor choice of words on my part.\n\nI'm not sure if Home Assistant will remove an add-ons persisted data when the add-on is removed tbf. But worth checking just incase. It might keep the data around so it's all still there should you decide to activate the add-on again.\n\nBut yea, the server add-on tells HA to store some files it needs for future reference. One of them is a config.json file and the other is a cookies.json file. The former stores server settings, the latter stores your authenticated browser session with amazon.\n\nProbably a red herring, but something to check out in the mean time until I get chance to try and replicate this.\n\nThose errors look chromium related, and not our errors, just output logs from chromium itself. That \"not authenticated\" error is likely referring to something else.\n\nI will try and replicate later, but I don't have windows I'm afraid 😅 .\n\nIf I really can't replicate it, the nuclear option would be to get together on discord or something and do a screenshare, fiddle with some code and see if we can discover what the hell is going on.","answer_document_id":"gh_comment_2587420635","silver_evidence_path":["gh_comment_2585955674","gh_issue_2769203934","gh_comment_2587420635"],"known_context_document_ids":["gh_issue_2769061212"],"evidence_issue_ids":[2769061212,2769203934],"source_repo_name":"madmachinations/home-assistant-alexa-shopping-list","source_issue_id":2769061212,"source_issue_url":"https://github.com/madmachinations/home-assistant-alexa-shopping-list/issues/37","target_repo_name":"madmachinations/home-assistant-alexa-shopping-list","target_issue_id":2769203934,"target_issue_url":"https://github.com/madmachinations/home-assistant-alexa-shopping-list/issues/39","split":"dev","quality_score":82.86,"annotation_level":"silver"}
{"query_id":"cross_issue_0066","query":"Canonical URL not added with default configuration?","query_context":"With a new install of the Metatag 1.22.5 and default settings...\n\nUnder \"Advanced Tags\" for \"Global\" and \"Content\", the following token is set for \"Canonical URL\":\n\n`[current-page:url:absolute]`\n\nSince a token is is provided for the canonical url field by default, I would expect to see\n\n` `\n\nIn the head of all pages. However, no rel canonical tag is inserted.\n\nNote that if \"Always output canonical, shortlink, and generator meta tags\" is enabled in Metatag master settings, a canonical tag _is_ inserted.\n\nReproducible with Backdrop 1.24.1 and Metatag 1.22.5.\n\nPerhaps I am misunderstanding expected behavior?","reference_answer":"I checked metatag's handling of `#attached` and it looks like it already works correctly. There was a separate issue with Canonical not working #109, but with that issue fixed I have confirmed that the HTTP `Link` header already works properly. The `X-Generator` header is another example of a metatag that exists both in HTML and in the HTTP header. I added test coverage for both in a PR at URL \n\nSo in summary to fix this issue, I think we need to do both of these things:\n\n1. Merge URL to make `schema_metatag` act like other metatags.\n2. Merge URL which includes @dgbruns's fix and test coverage.","answer_document_id":"gh_comment_1773517917","silver_evidence_path":["gh_comment_1749924386","gh_issue_1929309320","gh_comment_1773517917"],"known_context_document_ids":["gh_issue_1631050458"],"evidence_issue_ids":[1631050458,1929309320],"source_repo_name":"backdrop-contrib/metatag","source_issue_id":1631050458,"source_issue_url":"https://github.com/backdrop-contrib/metatag/issues/109","target_repo_name":"backdrop-contrib/metatag","target_issue_id":1929309320,"target_issue_url":"https://github.com/backdrop-contrib/metatag/issues/110","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0068","query":"SchemaOf returns undefined-able type for a required array?","query_context":"I need to verify that my schema match array of strings, so I use [`yup.SchemaOf `]( URL but when I try to validate using this schema or InferType from it, it returns me `string[] | undefined`. I can't understand where this `undefined` comes from:\n\njs\nconst schema: yup.SchemaOf = yup.array().of(yup.string().required()).required();\ntype MyType = yup.InferType ;\n\nExpected result: `type MyType = string[]`\nActual result: `type MyType = string[] | undefined`\n\nI provided this simplified example, but this happens not only with array of strings, but with any arrays, including arrays in object attributes.\n\nNote: if I don't use SchemaOf annotation, it works as expected:\n\njs\nconst schema = yup.array().of(yup.string().required()).required();\ntype MyType = yup.InferType ; // type MyType = string[]\n\n(but that way I can't guarantee that validation schema produce objects that match types defined in my application)\n\nYup version: 0.32.11\nNodeJS version: 16.15.0\nTypeScript version: 4.6.4\n\nIt became pretty annoying so I appreciate any feedback. Thank you!","reference_answer":"Yes, strict nulls is a required typescript setting for types to work, as mentioned in the docs","answer_document_id":"gh_comment_1704320561","silver_evidence_path":["gh_comment_1419298740","gh_issue_916934899","gh_comment_1704320561"],"known_context_document_ids":["gh_issue_1486753151"],"evidence_issue_ids":[1486753151,916934899],"source_repo_name":"jquense/yup","source_issue_id":1486753151,"source_issue_url":"https://github.com/jquense/yup/issues/1853","target_repo_name":"jquense/yup","target_issue_id":916934899,"target_issue_url":"https://github.com/jquense/yup/issues/1389","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0073","query":"[google_maps_flutter] Google maps overlay?","query_context":"I would like to display an image in overlay at given lat-log positions on Google map using Flutter. I am using flutter package google_maps_flutter: ^2.2.1, at present the package does not provide to implement the feature .","reference_answer":"@UDAYBIDKAR did some great work on this in URL but unfortunately isn't available to finish the work. If anyone would like to build on their great contribution and take it to the finish line, that would be great — there's just some review comments to address (see the PR for details).","answer_document_id":"gh_comment_1149260271","silver_evidence_path":["gh_comment_1272788855","gh_issue_398605825","gh_comment_1149260271"],"known_context_document_ids":["gh_issue_1400904897"],"evidence_issue_ids":[1400904897,398605825],"source_repo_name":"flutter/flutter","source_issue_id":1400904897,"source_issue_url":"https://github.com/flutter/flutter/issues/113093","target_repo_name":"flutter/flutter","target_issue_id":398605825,"target_issue_url":"https://github.com/flutter/flutter/issues/26479","split":"dev","quality_score":79.76,"annotation_level":"silver"}
{"query_id":"cross_issue_0074","query":"left right assertion failures on intel/nvidia hybrid gpu laptop.","query_context":"Hi! I tried running wl-screenrec on my hardware but I consistently get the following errors on both my NVIDIA card and my integrated intel gpu:\n\nbash\n❯ ./wl-screenrec --dri-device /dev/dri/renderD129 -v\nUsing output eDP-1\n[file @ 0x564a68e9ce00] Setting default whitelist 'file,crypto,data'\n[AVHWDeviceContext @ 0x564a68e9d340] libva: VA-API version 1.18.0\n[AVHWDeviceContext @ 0x564a68e9d340] libva: Trying to open /usr/lib/dri/iHD_drv_video.so\n[AVHWDeviceContext @ 0x564a68e9d340] libva: va_openDriver() returns -1\n[AVHWDeviceContext @ 0x564a68e9d340] libva: Trying to open /usr/lib/dri/i965_drv_video.so\n[AVHWDeviceContext @ 0x564a68e9d340] libva: va_openDriver() returns -1\n[AVHWDeviceContext @ 0x564a68e9d340] Failed to initialise VAAPI connection: -1 (unknown libva error).\nthread 'main' panicked at 'assertion failed: `(left == right)`\n left: `-5`,\n right: `0`', src/avhw.rs:34:13\nnote: run with `RUST_BACKTRACE=1` environment variable to display a backtrace\n[AVIOContext @ 0x564a68e9d180] Statistics: 0 bytes written, 0 seeks, 0 writeouts\n\nIf anyone can provide some context as to why this is occurring, I'd love to dig in deeper and provide more information.","reference_answer":"Fixed the timing issues, which includes mp4 timing, so it should work without jank. \n\nI'm going to close this issue, if you still see the frame corruption issues open a new issue. Thanks for all the help guys!","answer_document_id":"gh_comment_1383295409","silver_evidence_path":["gh_comment_1618898421","gh_issue_1533767150","gh_comment_1383295409"],"known_context_document_ids":["gh_issue_1784075121"],"evidence_issue_ids":[1784075121,1533767150],"source_repo_name":"russelltg/wl-screenrec","source_issue_id":1784075121,"source_issue_url":"https://github.com/russelltg/wl-screenrec/issues/13","target_repo_name":"russelltg/wl-screenrec","target_issue_id":1533767150,"target_issue_url":"https://github.com/russelltg/wl-screenrec/issues/1","split":"dev","quality_score":90.95,"annotation_level":"silver"}
{"query_id":"cross_issue_0077","query":"🚀 Feature: publish: :push action?","query_context":"### 🔖 Feature description\n\nadd publish:\\ :push to the list of built-in action\n\n### 🎤 Context\n\nAs a user who adding API (or any other component) to my service catalogue - I want to have the option to do this via UI.\nCreating a new git repository for each new entity seems wasteful, so I want to have a single repository for all configs. \nCreating yaml files manually and registering them via a direct link is tiring.\nI want to push a new yaml file directly to the branch and be able to register entity in catalog immediately after creation.\n\ntemplate example:\n\n steps:\n - id: fetch-base\n name: Fetch Base\n action: fetch:template\n input:\n url: ./content\n values:\n name: ${{ parameters.name }}\n\n - id: publish\n name: Publish\n action: publish:github:push\n input:\n branch: master\n targetPath: some/path\n repoUrl: ${{ parameters.repoUrl }}\n\n - id: register\n name: Register\n action: catalog:register\n input:\n repoContentsUrl: ${{ steps['publish'].output.repoContentsUrl }}\n catalogInfoPath: 'some/path/catalog-info.yaml'\n\n### ✌️ Possible Implementation\n\n_No response_\n\n### 👀 Have you spent some time to check if this feature request has been raised before?\n\n- [X] I checked and didn't find similar issue\n\n### 🏢 Have you read the Code of Conduct?\n\n- [X] I have read the Code of Conduct\n\n### Are you willing to submit PR?\n\nNone","reference_answer":"That's right.\n \n\nYep, spread them out to where they belong, and leave their management up to their respective owners.\n \n\nI am again a bit confused by the wording \"catalog repo\". :) There should be no catalog repo. You should have catalog-info files spread out all across your version control system, and the catalog (the catalog SERVICE, running in your infrastructure) holds a list of URLs pointing to those files. It updates its internal state all the time, in the background, based on the contents of those files.\n\nIf an end user changes a catalog-info file in their own repo, that's already registered in the catalog backend, there's no more action to take. You don't re-register. A short while later, the updated info will just automatically be reflected in the catalog.","answer_document_id":"gh_comment_1700502364","silver_evidence_path":["gh_comment_1420485882","gh_issue_1568411360","gh_comment_1700502364"],"known_context_document_ids":["gh_issue_1568395314"],"evidence_issue_ids":[1568395314,1568411360],"source_repo_name":"backstage/backstage","source_issue_id":1568395314,"source_issue_url":"https://github.com/backstage/backstage/issues/16153","target_repo_name":"backstage/backstage","target_issue_id":1568411360,"target_issue_url":"https://github.com/backstage/backstage/issues/16155","split":"dev","quality_score":95.31,"annotation_level":"silver"}
{"query_id":"cross_issue_0084","query":"Correção de Estilização na Página de Horóscopo?","query_context":"Descrição: Esta tarefa foca na construção e implementação do conteúdo da tela do horoscopo do site, utilizando o design já estabelecido como referência. \n\nfigma: URL \ndocumento: heavenly.pdf","reference_answer":"Correção de estilo concluída e integrada à branch develop. \nfeature da tarefa: Feature/correcao estilo","answer_document_id":"gh_comment_2263587636","silver_evidence_path":["gh_comment_2263562908","gh_issue_2438482435","gh_comment_2263587636"],"known_context_document_ids":["gh_issue_2433955804"],"evidence_issue_ids":[2433955804,2438482435],"source_repo_name":"victo-dev-qriarlabs/heavenly","source_issue_id":2433955804,"source_issue_url":"https://github.com/victo-dev-qriarlabs/heavenly/issues/27","target_repo_name":"victo-dev-qriarlabs/heavenly","target_issue_id":2438482435,"target_issue_url":"https://github.com/victo-dev-qriarlabs/heavenly/issues/32","split":"dev","quality_score":83.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0095","query":"Tighten the definition of \"column\"?","query_context":"The source map spec doesn't describe the units for columns -- just that they are zero-based. It turns out that Gecko uses UTF-16 code points, and that seems to be a common, but not universal, choice. It would improve the spec if it were explicit about the units.","reference_answer":"I left a comment now on the tc39 proposal. I hope for now that Firefox reverts this behavior but the issue is known from our side. Since not all Firefox versions agree on the offset it's unfortunately a pretty frustrating situation right now that we do not want to try to make too many guesses about.","answer_document_id":"gh_comment_1134703895","silver_evidence_path":["gh_comment_1499111388","gh_issue_1094187909","gh_comment_1134703895"],"known_context_document_ids":["gh_issue_255951179"],"evidence_issue_ids":[255951179,1094187909],"source_repo_name":"tc39/source-map-rfc","source_issue_id":255951179,"source_issue_url":"https://github.com/tc39/source-map-rfc/issues/5","target_repo_name":"getsentry/rust-sourcemap","target_issue_id":1094187909,"target_issue_url":"https://github.com/getsentry/rust-sourcemap/issues/37","split":"dev","quality_score":86.33,"annotation_level":"silver"}
{"query_id":"cross_issue_0096","query":"Create a preprocessing step to use defaults, validate input data, and calculate flow partitions?","query_context":"### Description\n\nAs in the Tulipa-OBZ-CaseStudy, we start with the bare minimum input data and then move on to the tables we need to create the model. Having these steps inside Tulipa will help improve the users' experience and avoid data that generates incorrect constraints (e.g., the flow partitions must be inferred from the asset partitions).\n\n### Sub issues\n\n- [ ] Create the minimum input data (mandatory) files/tables an user must provide\n- [ ] Create a validation function to check #461 \n- [x] #1129\n- [ ] #1052","reference_answer":"Here's a version of the 1st one, the user workflow. It includes functions that don't exist, and I haven't followed the current situation of the workflow, but it should be enough to evaluate the solution.\nTulipa User Workflow-2.pdf","answer_document_id":"gh_comment_2734444189","silver_evidence_path":["gh_comment_2740565600","gh_issue_2086214232","gh_comment_2734444189"],"known_context_document_ids":["gh_issue_2909350286"],"evidence_issue_ids":[2909350286,2086214232],"source_repo_name":"TulipaEnergy/TulipaEnergyModel.jl","source_issue_id":2909350286,"source_issue_url":"https://github.com/TulipaEnergy/TulipaEnergyModel.jl/issues/1081","target_repo_name":"TulipaEnergy/TulipaEnergyModel.jl","target_issue_id":2086214232,"target_issue_url":"https://github.com/TulipaEnergy/TulipaEnergyModel.jl/issues/415","split":"dev","quality_score":93.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0104","query":"Unify tagging for mirroring and release stages?","query_context":"Related to URL \n\nCurrently both mirroring and release stage are tagging the same build commit with the same tag and pushing it to a remote (mirroring to `dotnet-security-partners/dotnet`, release to the public `VMR`). They are also using two different scripts to achieve this.\n\nWe should unify this step under one logic to guarantee that we don't accidently change only one of them in the future, resulting in a miss-match between what we published publicly versus what we handed off to partners.\n\nWe could utilize the Release CLI for this by just adding a single command and using it in both stages.","reference_answer":"[Triage] Closing as a duplicate of URL Even though this issue was logged first, URL has more detail.","answer_document_id":"gh_comment_2127600905","silver_evidence_path":["gh_comment_2037259445","gh_issue_2134531067","gh_comment_2127600905"],"known_context_document_ids":["gh_issue_1994455778"],"evidence_issue_ids":[1994455778,2134531067],"source_repo_name":"dotnet/source-build","source_issue_id":1994455778,"source_issue_url":"https://github.com/dotnet/source-build/issues/3736","target_repo_name":"dotnet/source-build","target_issue_id":2134531067,"target_issue_url":"https://github.com/dotnet/source-build/issues/4131","split":"dev","quality_score":91.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0112","query":"Bug with Window Covers in Matter/SmartThings/Google Home Integration?","query_context":"Here is how you can explain your issue on GitHub in English:\n\nI have an issue with my window covers. These covers do not support percentage-based positioning; they only have commands for \"up,\" \"down,\" and \"stop.\" To manage their state, I added a sensor that indicates whether they are open or closed.\n\nI created a YAML configuration for these covers using the cover component with the generic platform.\n\nOn Homebridge and Home Assistant, everything works fine.\n\nOn Matter, SmartThings, or Google Home, the integration does not work properly.\n\nHowever, when I use Google Home via the cloud, it works as expected.\n\nIt seems like the problem is specifically related to how the configuration or functionality is handled in Matter/SmartThings/Google Home locally.\n\nvolet_louis:\n friendly_name: \"Volet Louis 2\"\n position_template: \"{{ (states('binary_sensor.lumi_lumi_sensor_magnet_aq2_opening_25') == 'off')|int * 100 }}\"\n open_cover:\n service: cover.open_cover\n data:\n entity_id: cover.volet_louis\n close_cover:\n service: cover.close_cover\n data:\n entity_id: cover.volet_louis\n stop_cover:\n service: cover.stop_cover\n data:\n entity_id: cover.volet_louis","reference_answer":"🤦 \n \n\nCan you confirm that google home is always in sync with \"target position\" instead of \"current position\" ?\nWe don't have target position in home assistant, right? At least I don't have it. So i could sync target position with current position, but doesn't really make sense...\n \n\nFor ALL covers? As I mentioned earlier: \nMatter open = 0% and close = 100%\nHA open = 100% and close = 0%\n\nTherefore I am inverting. Can you test using \"open cover\" command (without percentage) to verify that it's REALLY inverted?\n \n\nYes, but users could be confused by it, when trying to set the position to 30% in GH 😀 \n \n \n\nBut isn't that a problem of the integration. If the cover supports it, shouldn't it be part of the cover entity?\nAnyway I am already using/used it for covers. I just need to re-add it for non-position-aware covers.\n\nTo make it clear:\nI don't have a problem with device based bridge, it's just a matter of effort vs. available time at the moment 😀","answer_document_id":"gh_comment_2495465968","silver_evidence_path":["gh_comment_2509725262","gh_issue_2663138981","gh_comment_2495465968"],"known_context_document_ids":["gh_issue_2666439047"],"evidence_issue_ids":[2666439047,2663138981],"source_repo_name":"t0bst4r/home-assistant-matter-hub","source_issue_id":2666439047,"source_issue_url":"https://github.com/t0bst4r/home-assistant-matter-hub/issues/164","target_repo_name":"t0bst4r/home-assistant-matter-hub","target_issue_id":2663138981,"target_issue_url":"https://github.com/t0bst4r/home-assistant-matter-hub/issues/144","split":"dev","quality_score":87.09,"annotation_level":"silver"}
{"query_id":"cross_issue_0113","query":"Brisanje nepremičnine?","query_context":"Potrebovale bi pomoč pri brisanju nepremičnine. Kljub temu, da smo uredile, da ko izbrišemo nepremičnino, da se izbriše tudi komitent, nam še vedno javlja napako, da izbris ni mogoč, ker se v komitentu sklicujemo na nepremičnino, ki bi jo rade izbrisale.\nŽe v naprej hvala za pomoč!","reference_answer":"Hvala za opombe, `requests` smo odstranili url-je smo pa naredili tako kot smo se menili na vajah.\nImamo še eno vprašanje glede `binder`-ja, ali moramo spremeniti oz. dodati še kaj za delovanje le-tega \n(poleg povezave z _javnost_ na bazo).","answer_document_id":"gh_comment_1133666159","silver_evidence_path":["gh_comment_1162024452","gh_issue_1235096216","gh_comment_1133666159"],"known_context_document_ids":["gh_issue_1277475311"],"evidence_issue_ids":[1277475311,1235096216],"source_repo_name":"nezakrzan/Nepremicninske-agencije","source_issue_id":1277475311,"source_issue_url":"https://github.com/nezakrzan/Nepremicninske-agencije/issues/5","target_repo_name":"MatejRojec/Gamma","target_issue_id":1235096216,"target_issue_url":"https://github.com/MatejRojec/Gamma/issues/1","split":"dev","quality_score":82.67,"annotation_level":"silver"}
{"query_id":"cross_issue_0114","query":"Change Some expression that not contribute with inclusive language or antiracist language?","query_context":"### Summary\n\nHi community!\n\nIn the view Spam Filter when you are editing a domain.\n\nchange words \nWhite List for Enabled\nBlack List for Disabled\n\nIn Spanish \nLista Blanca: Habilitada\nLista Negra: Deshabilitada\n\nCaptura de pantalla de 2022-03-25 20-23-59\n\nCaptura de pantalla de 2022-03-25 20-22-02\n\n### Motivation\n\ncontribute to a non-racist language\n\n### Additional context\n\n_No response_","reference_answer":"I don't think Mailcow is the right place for political discussions like this. While the intent may be laudable, it comes at a price in terms of clarity, brevity and unambiguity.\n\nFor example, replacing \"whitelist\" with \"allow list\" is ambiguous and unclear (you don't need to be on that list to be allowed to send mail) and \"spam filter bypass list\" is lengthy and not completely clear either.\n\nThere do not appear to be alternative terms in widespread use (Exchange has \"safe senders\", Gmail doesn't even have that feature), and as a small mail server platform, we are not in the position to define new terms. We need to make it as easy as possible for people migrating from other platforms. Once Exchange, Yahoo, Gmail, etc. converge on a new name, we will happily adopt it.","answer_document_id":"gh_comment_558603194","silver_evidence_path":["gh_comment_1079667256","gh_issue_524674898","gh_comment_558603194"],"known_context_document_ids":["gh_issue_1181473654"],"evidence_issue_ids":[1181473654,524674898],"source_repo_name":"mailcow/mailcow-dockerized","source_issue_id":1181473654,"source_issue_url":"https://github.com/mailcow/mailcow-dockerized/issues/4524","target_repo_name":"mailcow/mailcow-dockerized","target_issue_id":524674898,"target_issue_url":"https://github.com/mailcow/mailcow-dockerized/issues/3155","split":"dev","quality_score":83.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0115","query":"Better integration with UI library: ...register() to pass e.g. error, helperText?","query_context":"**Is your feature request related to a problem? Please describe.**\nPardon me if I'm missing something, but it seems like a massive wasted opportunity not to let the register() function pass some additional props to the input component, such as in the case of MUI TextField `error` and `helperText`. Since it's already being spread anyway, it can just pass arbitrary props. Let me give an example. Currently our code looks like this:\n\njsx\n \n\nThat's a lot of boilerplate for every single input field, and our forms contain a lot of input fields. Given that DX is one of the goals of this project, I felt like this would be a great addition!\n\n**Describe the solution you'd like**\nInstead, the `register()` function passes `error` and `helperText` props to the component automatically. It already know we're dealing with the `first_name` here (because we pass that to `register()`) so it can use that to extract `error.first_name` and `errors.first_name.message`.\n\njsx\n \n\nOf course, different UI libraries use different props for `error` and `helperText`. There would need to be some way to tell react-hook-form what UI library the project is using so it can figure out which props to pass. Ideas? Also the `register()` function would need to be nicely typed so that you can spread it to your input component without unknown props errors.\n\n**Describe alternatives you've considered**\nThe alternative is to pass those props manually, which is error-prone, increases the SLOC of your component and thus decreases readability, and is just a waste of time for the developer.","reference_answer":"<img width=\"613\" alt=\"image\" src=\" URL \n\nIt's working because there is no type check.","answer_document_id":"gh_comment_1174448809","silver_evidence_path":["gh_comment_1426504627","gh_issue_1291947895","gh_comment_1174448809"],"known_context_document_ids":["gh_issue_1566221915"],"evidence_issue_ids":[1566221915,1291947895],"source_repo_name":"react-hook-form/react-hook-form","source_issue_id":1566221915,"source_issue_url":"https://github.com/react-hook-form/react-hook-form/issues/9851","target_repo_name":"react-hook-form/react-hook-form","target_issue_id":1291947895,"target_issue_url":"https://github.com/react-hook-form/react-hook-form/issues/8619","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0117","query":"Column access to tables?","query_context":"With #17 we have defined a simple table structure, but we have no simple way to get a numpy array of the columns, for instance, we might hope to be able to get\n\npython\nchild_left = TableCollection.intervals.child_left\n\nOr even set a whole column:\n\npython\nTableCollection.intervals.child_left = child_left +1\n\n(we can't even do the latter in tskit, though)","reference_answer":"The two example tests in test_tables.py should show you (a) how to use fixtures (e.g. if you want to import a standard GIG for testing in multiple tests) and (b) how to use `@pytest.mark.parametrize` to test a range of parameter values. Both of these are useful idioms.","answer_document_id":"gh_comment_1744739365","silver_evidence_path":["gh_comment_1742788938","gh_issue_1919841089","gh_comment_1744739365"],"known_context_document_ids":["gh_issue_1919641073"],"evidence_issue_ids":[1919641073,1919841089],"source_repo_name":"hyanwong/GeneticInheritanceGraph","source_issue_id":1919641073,"source_issue_url":"https://github.com/hyanwong/GeneticInheritanceGraph/issues/19","target_repo_name":"hyanwong/GeneticInheritanceGraph","target_issue_id":1919841089,"target_issue_url":"https://github.com/hyanwong/GeneticInheritanceGraph/issues/20","split":"dev","quality_score":84.34,"annotation_level":"silver"}
{"query_id":"cross_issue_0120","query":"Password presence validation bizarre behaviour?","query_context":"User model\n\nruby\nclass User true\n\nfound_user = User.last\nfound_user.update!(name: \"Other\", password: \"\")\n# => Validation failed: Password can't be blank (ActiveRecord::RecordInvalid)\n\nMore info on:\nWhy would `has_secure_password` suppress password validation on update, but only if the object is newly created?\n\nMay I ask this behaviour is intended or it's a bug?","reference_answer":"I don't think the problem is on those conditionals. `''` is empty so the password_digest would not be updated. The validation doesn't fail because the digest is still the same as before and no changes to the database will be made.\n\nWe have a test for it\n URL So an empty password doesn't change the current password so it is still valid.\n\nIf I remember correctly we tried to fix this before and I'm almost sure there is a reason for this behavior. But please investigate.","answer_document_id":"gh_comment_434361126","silver_evidence_path":["gh_comment_2207625700","gh_issue_375450743","gh_comment_434361126"],"known_context_document_ids":["gh_issue_2388408787"],"evidence_issue_ids":[2388408787,375450743],"source_repo_name":"rails/rails","source_issue_id":2388408787,"source_issue_url":"https://github.com/rails/rails/issues/52264","target_repo_name":"rails/rails","target_issue_id":375450743,"target_issue_url":"https://github.com/rails/rails/issues/34348","split":"dev","quality_score":93.71,"annotation_level":"silver"}
{"query_id":"cross_issue_0121","query":"Support for setting an alternate subscriptionId as a resource parameter?","query_context":"### Is there an existing issue for this?\n\n- [X] I have searched the existing issues\n\n### Community Note\n\n \n\n* Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request\n* Please do not leave \"+1\" or \"me too\" comments, they generate extra noise for issue followers and do not help prioritize the request\n* If you are interested in working on this issue or have submitted a pull request, please leave a comment\n\n \n\n### Description\n\nCurrently in order to support multiple subscriptions, one needs to specify multiple aliases as different providers, since currently the azurerm provider has a 1-to-1 relationship between the authentication credentials and subscriptions.\n\nHowever, from an Azure API perspective, the relationship between authentication credentials and subscriptions is actually a 1-to-N.\n\nThe main drawback of the current method used by azurerm is that the subscriptionIds must be known beforehand (to be declared); therefore it's not possible to work with multiple dynamic subscriptions, at least not without the usage of an external helper to declare them as provider aliases directly in the TF files.\n\nMy proposal is to allow any resource to specify an alternative subscriptionId (different from the one specified within the provider block) as part of the resource parameters.\n\nThis way, subscriptions can be created/updated/destroyed dynamically, and their values could be reused to populate such this resource parameter.\n\n### New or Affected Resource(s)/Data Source(s)\n\nazurerm_*\n\n### Potential Terraform Configuration\n\nhcl\nprovider \"azurerm\" {\n client_id = \"nono\"\n client_secret = \"nono\"\n subscription_id = \"XXX\" \n tenant_id = \"nono\"\n}\n\n# Sample resource using the default subscription (coming from provider block)\nresource \"azurerm_private_dns_zone\" \"zoneXXX\" {\n name = \"XXX.domain\"\n resource_group_name = azurerm_resource_group.xxx.name\n}\n\n# Sample resource using the custom subscription \nresource \"azurerm_private_dns_zone\" \"zoneYYY\" {\n name = \"YYY.domain\"\n subscription_id = \"YYY\"\n resource_group_name = azurerm_resource_group.yyy.name\n}\n\n### References\n\n_No response_","reference_answer":"@bhupinder-azenix Can you use the provider alias of `subscriptionA` to create this resource and assign whatever you have in `${data.azurerm_client_config.this.subscription_id}` as `subscription_id`? That should be equivalent to above azapi config.","answer_document_id":"gh_comment_1336817682","silver_evidence_path":["gh_comment_1336790016","gh_issue_1470899703","gh_comment_1336817682"],"known_context_document_ids":["gh_issue_1473255289"],"evidence_issue_ids":[1473255289,1470899703],"source_repo_name":"hashicorp/terraform-provider-azurerm","source_issue_id":1473255289,"source_issue_url":"https://github.com/hashicorp/terraform-provider-azurerm/issues/19539","target_repo_name":"hashicorp/terraform-provider-azurerm","target_issue_id":1470899703,"target_issue_url":"https://github.com/hashicorp/terraform-provider-azurerm/issues/19520","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0129","query":"Can we disable the Outlook warning when add-in closes the message from ItemSent event?","query_context":"Last week when using our add-in we started seeing this warning when our add-in tries to close a message being composed:\n\nImage\n\nOur add-in retrieves all the information of a message to later send it using the Graph API. Before it was seamless for the users, but now we are getting a lot of confusion from our users since they don't know if they should close the message or cancel. Also if they cancel our service will still send the message, but the draft isn't deleted and that creates even more confusion.\n\nWe were wondering if there was a way to disable this feature in the user's mailbox or disable the feature entirely in our add-in ?\n\nPlease take note that this warning was not there earlier last week and that it only happens when the `Office.context.mailbox.item.close()` line is executed from the `ItemSent` event. The mailbox item is closed without warning if called from a side panel.\n\nHere is a code example:\n\nXML:\n\n...\n \n \n \n...\n\nOnSendHandler function:\n\nfunction onSendHandler(event){\n //Process de data in the body\n ...\n \n //Close mailbox item to later be sent\n Office.context.mailbox.item.close() //Warning is triggered since the event based activation was from ItemSent\n}\n\n**Edit**\n\nI tried the `closeAsync` function with `discardItem: true`:\n\nmailboxItem?.closeAsync({ discardItem: true }, result => {\n console.log(result);\n});\n\nI don't get the previous close warning and the mailbox item is getting closed successfully, but now I get a new warning:\n\nImage\n\nI think again this message is linked to the `ItemSent` event and just to add, it says that the `email was moved to the Drafts folder`, but no drafts are present for the message that was closed.\n\nIs there a way to disable this new warning with the `ItemSent` event ?","reference_answer":"Hi @victorcalarasu \n\nThank you for providing the logs. \nI can see repeated POST requests to \" URL \n\".\nThis endpoint if for Telemetry collection.\nNO_AUTH also suggests that requests are unauthenticated. \nIs the add-in explicitly sending excessive analytics data using Office.js APIs? You may re-try disabling them.","answer_document_id":"gh_comment_2643736897","silver_evidence_path":["gh_comment_2663148565","gh_issue_2825795142","gh_comment_2643736897"],"known_context_document_ids":["gh_issue_2845562803"],"evidence_issue_ids":[2845562803,2825795142],"source_repo_name":"OfficeDev/office-js","source_issue_id":2845562803,"source_issue_url":"https://github.com/OfficeDev/office-js/issues/5378","target_repo_name":"OfficeDev/office-js","target_issue_id":2825795142,"target_issue_url":"https://github.com/OfficeDev/office-js/issues/5345","split":"dev","quality_score":84.92,"annotation_level":"silver"}
{"query_id":"cross_issue_0133","query":"Is there any way to bypass CSP?","query_context":"Related to URL \nIs there any way to bypass cross-origin objects?\nBecause this code\n\njs\ndocument.querySelector('iframe[title=\"Основное содержание испытания hCaptcha\"]').contentWindow.document \n\nreturns `Uncaught DOMException: Permission denied to access property \"document\" on cross-origin object`.\nSame in playwright:\n\npython\ncaptcha = await page.wait_for_selector('iframe[title=\"Основное содержание испытания hCaptcha\"]')\nframe = await captcha.content_frame()\n\nException:\n\njs\nElementHandle.content_frame: Protocol error (Page.describeNode): error in channel \"content::9/13/2\": exception while running method \"describeNode\" in namespace \"page\": Permission denied to access property \"docShell\" on cross-origin object _describeNode@chrome://juggler/content/content/PageAgent.js:417:62\n_onMessageInternal@chrome://juggler/content/SimpleChannel.js:237:37\n_onMessage@chrome://juggler/content/SimpleChannel.js:194:12\nbindToActor/actor.receiveMessage@chrome://juggler/content/SimpleChannel.js:39:44\nplaywright._impl._errors.Error: Protocol error (Page.describeNode): error in channel \"content::9/13/2\": exception while running method \"describeNode\" in namespace \"page\": Permission denied to access property \"docShell\" on cross-origin object _describeNode@chrome://juggler/content/content/PageAgent.js:417:62\n_onMessageInternal@chrome://juggler/content/SimpleChannel.js:237:37\n_onMessage@chrome://juggler/content/SimpleChannel.js:194:12\nbindToActor/actor.receiveMessage@chrome://juggler/content/SimpleChannel.js:39:44\n\nMethods like `bounding_box()` work and return everything correctly, but `page.mouse.click(x, y)` on iframe coordinates also doesn't work","reference_answer":"Hello,\n\nI figured out that reason this issue doesn't happen when using the route solution is because headers aren't being passed to `route.fulfill`.\n\npython\nasync def handle_route(route):\n response = await route.fetch()\n await route.fulfill(\n body=await response.body(),\n headers=response.headers,\n status=response.status\n )\n\nSpecifically, the reason Turnstile passes is due because the `Cross-Origin-Opener-Policy` (or COOP) header is being removed. Seems like Playwright's click function does not support the latest security changes in FF133+.\n\nA workaround for this could be to use this preference which disables COOP from being handled:\n\npython\nfirefox_user_prefs={\n 'browser.tabs.remote.useCrossOriginOpenerPolicy': False,\n}\n\nHowever, this could potentially be detected by anti-bots, though I haven't seen this used in a production environment (all of the Camoufox testing sites still pass). I will consider adding a COOP toggle in the Python library until Playwright bumps to FF133+ 👍","answer_document_id":"gh_comment_2614137611","silver_evidence_path":["gh_comment_2575137583","gh_issue_2763156165","gh_comment_2614137611"],"known_context_document_ids":["gh_issue_2748192207"],"evidence_issue_ids":[2748192207,2763156165],"source_repo_name":"daijro/camoufox","source_issue_id":2748192207,"source_issue_url":"https://github.com/daijro/camoufox/issues/144","target_repo_name":"daijro/camoufox","target_issue_id":2763156165,"target_issue_url":"https://github.com/daijro/camoufox/issues/150","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0134","query":"NuGet publishing?","query_context":"Publish our OSS packages to NuGet. Individual issues for the same: URL URL URL \n\nFirst steps:\n\n- Set up the NuGet publishing with GitHub Actions of URL and URL These will then at a later point serve as models for the rest.\n- These two projects are special, and thus cover all important use cases, because Helpful Extensions depends on Helpful Libraries, and Helpful Libraries contains three csprojs that all need to be published (either as separate packages or one; perhaps the former because other projects may not depend on all of them).\n- We're developing such OSS projects as part of this OSOCE solution. In other projects of ours we use them as submodules too, so consuming and improving them is easier. We'll keep this, thus we need some way for this to not clash with NuGet references.\n\nSome criteria to keep in mind:\n\n- We can handle the whole thing from a build in OSOCE too somehow, it needn't be for each project, if it makes things easier.\n- Currently, we have about 30 projects that we'd like to publish to NuGet. This already necessitates the ability to manage NuGet publishing somehow centrally in a DRY manner (apart from credentials that can be stored in GitHub secrets) but we'll likely have many more. So, a solution where we need to maintain a pipeline in each of these repositories would be an issue","reference_answer":"@scleaver @deanmarcussen it might be interesting for you what we've progressed with Node.js Extensions here. While we don't have the full functionality of Gulp Extensions yet, we actually have an NPM script-containing NuGet package working!","answer_document_id":"gh_comment_1109736143","silver_evidence_path":["gh_comment_1040840795","gh_issue_1130673631","gh_comment_1109736143"],"known_context_document_ids":["gh_issue_1069925276"],"evidence_issue_ids":[1069925276,1130673631],"source_repo_name":"Lombiq/Open-Source-Orchard-Core-Extensions","source_issue_id":1069925276,"source_issue_url":"https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/issues/23","target_repo_name":"Lombiq/Open-Source-Orchard-Core-Extensions","target_issue_id":1130673631,"target_issue_url":"https://github.com/Lombiq/Open-Source-Orchard-Core-Extensions/issues/48","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0135","query":"[LLD] symbol not found with PROVIDE script?","query_context":"I tried the following code. I expect lld to link successful while also removing unused symbols, but it reports `symbol not found: bar`.\n\na.s:\n\nasm\n.global _start\n_start:\n nop\n.section .text.foo,\"ax\",@progbits\n.global foo\nfoo:\n nop\n.section .text.bar,\"ax\",@progbits\n.global bar\nbar:\n nop\n\nscript.t:\n\nPROVIDE(foo = bar);\n\ncommands:\n\nbash\nllvm-mc -filetype=obj -triple=x86_64 a.s -o a.o\nld.lld -o a_gc a.o --gc-sections -T script.t\n\noutput:\n\nld.lld: error: script.t:1: symbol not found: bar\nld.lld: error: script.t:1: symbol not found: bar\nld.lld: error: script.t:1: symbol not found: bar\n\ncc @MaskRay ebb326a51fec37b5a47e5702e8ea157cd4f835cd","reference_answer":"I have read the related code, maybe we need to add this symbol to the symbol table. Or change the code like this:\n\ndiff\ndiff --git a/lld/ELF/ScriptParser.cpp b/lld/ELF/ScriptParser.cpp\nindex 3febcfb87da4..44185c282ad7 100644\n--- a/lld/ELF/ScriptParser.cpp\n+++ b/lld/ELF/ScriptParser.cpp\n@@ -1660,10 +1660,11 @@ Expr ScriptParser::readPrimary() {\n tok = unquote(tok);\n else if (!isValidSymbolName(tok))\n setError(\"malformed number: \" + tok);\n- if (activeProvideSym)\n+ if (activeProvideSym) {\n ctx.script->provideMap[*activeProvideSym].push_back(tok);\n- else\n- ctx.script->referencedSymbols.push_back(tok);\n+ return [] { return 0; };\n+ }\n+ ctx.script->referencedSymbols.push_back(tok);\n return [=, s = ctx.script] { return s->getSymbolValue(tok, location); };\n }\n\nHowever, I'm not familiar with this part of the code. \n \n \n \n\nIn any case, I believe the upstream backport is likely to miss our backport process. I'm reverting this commit to our fork LLVM.","answer_document_id":"gh_comment_2399624148","silver_evidence_path":["gh_comment_2406615664","gh_issue_2562252541","gh_comment_2399624148"],"known_context_document_ids":["gh_issue_2572023365"],"evidence_issue_ids":[2572023365,2562252541],"source_repo_name":"llvm/llvm-project","source_issue_id":2572023365,"source_issue_url":"https://github.com/llvm/llvm-project/issues/111478","target_repo_name":"rust-lang/rust","target_issue_id":2562252541,"target_issue_url":"https://github.com/rust-lang/rust/issues/131164","split":"dev","quality_score":92.44,"annotation_level":"silver"}
{"query_id":"cross_issue_0140","query":"[Impeller] Flaky impeller golden test in the engine?","query_context":"After URL there appears to be a flaky golden file test in the engine that is blocking other PRs from landing (example: URL \n\nScreenshot 2023-04-05 at 4 48 25 PM\n\nThe individual dots to the right show different colors, meaning a unique image was generated for each commit.\nThis is with the fuzzy matching algorithm set for this test:\n\nScreenshot 2023-04-05 at 4 51 07 PM\n\nAlso, it looks like this image is even flaking in post submit, because the same test is listed as untriaged on the main branch: URL \n\nIn the framework we have the tree go red if an unapproved image shows up in post submit, maybe the engine implementation should do the same.\n\ncc @mdebbar @dnfield @chinmaygarde @gaaclarke","reference_answer":"The main problem with the configuration file updates is there are a lot of places that end up needing this, and some of those places don't allow comments, and no one seems to have a good way to make sure we're covering all of them short of watching for a new failure to pop up.","answer_document_id":"gh_comment_1509220947","silver_evidence_path":["gh_comment_1515095567","gh_issue_1668699070","gh_comment_1509220947"],"known_context_document_ids":["gh_issue_1656350220"],"evidence_issue_ids":[1656350220,1668699070],"source_repo_name":"flutter/flutter","source_issue_id":1656350220,"source_issue_url":"https://github.com/flutter/flutter/issues/124277","target_repo_name":"flutter/flutter","target_issue_id":1668699070,"target_issue_url":"https://github.com/flutter/flutter/issues/124877","split":"dev","quality_score":75.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0141","query":"Migrating/Integrating WebCrypto (possibly WASM) instead of Node Forge Crypto?","query_context":"### Specification\n\nThe work in #155 involving nativescript meant that we are starting to consider alternatives to Node forge crypto in order to standardise our crypto API and future proof to future JS-based platforms. There are number of reasons to look into webcrypto:\n\n* WebCrypto is a standard across ES platforms, thus enabling more potential native-implementations which can improve performance and security (prevent timing attacks)\n* WebCrypto API focuses on using ES-compliant buffers like `Uint8Array` and `ArrayBuffer` which can help us standardise our buffer usage across js-db, js-id, js-workers and more, especially as workers require `ArrayBuffer` to do zero-copy\n* There is existing work with WebCrypto API involving WASM to plug in functionality that isn't supported by the standard, such as providing ed25519 keys, and this will help us resolve the usage of ed25519 #168 \n* The `node-forge` source code isn't well maintained and doesn't have as many eyes watching and evaluating its security\n\nNow for some background:\n\nThis comment URL explains how we came to be using `node-forge` as opposed to other cryptographic libraries.\n\nI know that when Polykey project first started, we initially were thinking of using PGP and thus the kbpgp.js library ( URL We ended up going away from PGP due to its limited usage in a number of scenarios that we want PK to deal with. Namely end to end encrypted network communication which is a TLS issue, that makes use of X.509 certificates rather than PGP certificates. Furthermore we also had symmetric encryption/decryption scenarios like js-encryptedfs that again would not make use of PGP standards. Therefore it just lacked interoperability with many other cryptographic scenarios, it seemed like its own island of standards, the library can still be brought back in in the future if we find usecases for PK using PGP.\n\nHowever in choosing node-forge, we came across a few other problems. Mainly overall-cross platform compatibility planning for mobile devices. This is not just a problem with crypto, but also other libraries that are used in our `networking` domain such as utp-native.\n\nHere are something I found that may be relevant to us proceeding here:\n\n* The webcrypto standard ( URL is now the official standard for cryptographic operations in browser environments. It is now being supported by all major browsers and electron\n* This webcrypto standard is now taking over other deployment platforms such as in Nodejs: URL & URL \n* As a standardised API, switching over to this API gives us more cross-platform opportunity as the rest of the world's development ecosystem catches up and migrates over to webcrypto standard.\n* In particular are nativescript and react-native ecosystems. Currently none of them have official crypto APIs, they expect the developer to use underlying native iOS or Android crypto APIs.\n* However I found out that the GUN project URL claims to be able to use webcrypto on react-native and other platforms.\n* It does this through a \"webview\" trick. Basically this hooks into the browser runtimes that are on iOS and Android to perform the actual crypto and then return the results back to the main application. I have no idea about the performance characteristics of this trick. This trick is described here: URL and URL \n* The usage of webcrypto libraries is pioneered by \"PeculiarVentures\" which has these main libraries:\n - URL - this could be an alternative to node-forge for all of our PKI/X.509 and TLS related functionality (previously it was claimed this was overly complex compared to `node-forge`)\n - URL - this is a generic polyfill for webcrypto, not entirely sure how it wraps the native webcrypto inside nodejs or if smooths over the differences, there is a discussion about this library in relation to other webcrypto polyfills targeting nodejs URL because this is also mentioned with respect to the webview trick, there may also be a relationship between the webview trick and this polyfill\n - They have many other crypto related libraries that we should investigate\n\nAll of this will mean that we either replace node-forge, or end up creating a adapter pattern where we plugin different crypto implementions depending on our environment. At this point in time, the `keys` domain abstracts over most(all?) crypto operations for all other domains. Except in the case of EFS which is currently pinned to `node-forge` (it may be a good idea to abstract that and expect an interface of functions for EFS).\n\nCross platform compatibility here isn't just about the fundamental crypto library. It's also about other parts of PK. One closely related situation is the JOSE libraries. As they involve cryptographic operations, they currently seem to \"fix\" their underlying crypto library as well. It would be ideal that if we standardise on a crypto library for cross-platform deployment, that we can also ensure that our JOSE library is using the same crypto library to reduce our crypto attack surface. We are currently using URL which uses native crypto depending on the platform including webcrypto. Contenders include URL (which fixes on node-forge) and URL \n\n### Additional context\n\n* URL - js-id also should be using WebCrypto\n* #155 - will impact NativeScript deployment\n* URL - can help make use of the migration to `ArrayBuffer` and typed arrays\n* WebAssembly resources\n - There are 2 well supported runtimes for WASM:\n * wasm3 - supports interpretation\n * wasmer - supports JIT and AOT compilation\n - URL \n - URL \n - URL \n - URL - This describes how to use webcrypto together with webassembly when you need a custom crytographic functionality not supported inside webcrypto.\n - URL \n - URL and URL \n\nWasmer can compile WASM code to native code. But wasm3 is for interpretation. Why use interpetation?\n\nIt appears that in some cases interpretation can be more widely deployed. There are examples of iOS apps using wasm3. URL \n\nIt's becoming fast a standard target for many languages. Even TypeScript when ported to AssemblyScript can be compiled to WASM.\n\nOnce it is WASM, the only thing missing is broad adoption of WASI. If WASI is broadly adopted like it is in nodejs ( URL then pretty much we have a universal portable binary capable of doing relevant system operations. WASI is like a universal standard of system calls. Like a whole new POSIX standard.\n\nThen one would just use WASM and WASI for all platforms.\n\n### Tasks\n \n1. ...\n2. ...\n3. ...","reference_answer":"We decided not to bother with preventing resource starvation, however an idea is like this.\n\n1. Take advantage of DB's natural key ordering.\n2. Create a bimap index of Priority/Timestamp -> Task Id AND Timestamp/Priority -> Task Id\n3. Now we can iterate task ids based on 2 compound indexes: highest priority + earliest timestamp AND earliest timestamp + highest priority\n4. Use dynamic programming/kinetic priority function that iterates through both sublevels (indexes) simultaneously to fill up a fixed concurrency pool (if unlimited, this policy is unnecessary, just iterate through as fast as posssible)\n\nSimultaneous iteration that uses the timestamp to weight the priority, where the timestamp delta starts from 0 and goes towards infinity. Once could say that this multiples the priority based on a \"rate\". A delta of 0 multiplies by 1. A delta of infinity multiplies by infinity. Therefore the rate produces a multiplier between 1 to infinity.","answer_document_id":"gh_comment_1223590432","silver_evidence_path":["gh_comment_1207685560","gh_issue_1128062883","gh_comment_1223590432"],"known_context_document_ids":["gh_issue_1036078659"],"evidence_issue_ids":[1036078659,1128062883],"source_repo_name":"MatrixAI/Polykey","source_issue_id":1036078659,"source_issue_url":"https://github.com/MatrixAI/Polykey/issues/270","target_repo_name":"MatrixAI/Polykey","target_issue_id":1128062883,"target_issue_url":"https://github.com/MatrixAI/Polykey/issues/329","split":"dev","quality_score":94.08,"annotation_level":"silver"}
{"query_id":"cross_issue_0143","query":"spire-agent gets OOMKilled after pod restart?","query_context":"* **Version**: up to 1.8.6\n* **Platform**: Linux 6.5.0-26-generic 26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 GNU/Linux\n* **Subsystem**: agent\n\nWhen I delete a spire-agent pod in the cluster, it becomes unstable, the container gets `OOMKilled` a couple of times before becoming stable.\n\nThese are the resource settings currently:\n\n Limits:\n cpu: 1\n memory: 570Mi\n Requests:\n cpu: 800m\n memory: 512Mi\n\nThere is only a warning about a container ID that is not found at attestation then the agent exits with reason `OOMKilled`.\n\ntime=\"2024-04-11T13:40:53Z\" level=warning msg=\"Current umask 0022 is too permissive; setting umask 0027\"\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Starting agent with data directory: \"/run/spire/temp\"\"\ntime=\"2024-04-11T13:40:53Z\" level=warning msg=\"Agent is now configured to accept remote network connections for Prometheus stats collection. Please ensure access to this port is tightly controlled\" subsystem_name=telemetry\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Plugin loaded\" external=false plugin_name=k8s_psat plugin_type=NodeAttestor subsystem_name=catalog\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Plugin loaded\" external=false plugin_name=memory plugin_type=KeyManager subsystem_name=catalog\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Plugin loaded\" external=false plugin_name=k8s plugin_type=WorkloadAttestor subsystem_name=catalog\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Bundle loaded\" subsystem_name=attestor trust_domain_id=\"spiffe://infra\"\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"SVID is not found. Starting node attestation\" subsystem_name=attestor trust_domain_id=\"spiffe://infra\"\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Node attestation was successful\" rettestable=true spiffe_id=\"spiffe://infra/spire/agent/k8s_psat/infra-cluster/890be4ad-1618-4379-9bc9-c54bb55223d5\" subsystem_name=attestor trust_domain_id=\"spiffe://infra\"\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Renewing X509-SVID\" entry_id=28908b2f-d02b-4269-8ecf-de78d350bf5d spiffe_id=\"spiffe://infra/ns/infra/pod/nsmgr-72bjt\" subsystem_name=manager\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Renewing X509-SVID\" entry_id=deaeb5c6-ab93-4851-88c5-e13497486f09 spiffe_id=\"spiffe://infra/ns/infra/pod/forwarder-vpp-xgbgq\" subsystem_name=manager\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Renewing X509-SVID\" entry_id=610ecd0f-e2c9-4e38-922d-9e325a3dd6cb spiffe_id=\"spiffe://infra/ns/cndsc3/pod/proxy-vpn1-6vkn4\" subsystem_name=manager\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Renewing X509-SVID\" entry_id=0415f6a1-240c-49b3-8215-7e337bcead79 spiffe_id=\"spiffe://infra/ns/cndsc3/pod/proxy-vpn2-pvb7p\" subsystem_name=manager\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Renewing X509-SVID\" entry_id=0d2837cb-9aa8-4189-b2d7-c3ddeb4ee587 spiffe_id=\"spiffe://infra/ns/cndsc3/pod/stateless-lb-frontend-attr-vpn2-5444c987npdbt\" subsystem_name=manager\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Renewing X509-SVID\" entry_id=cfdb2a8a-e340-4cef-8d3f-8944af4e4758 spiffe_id=\"spiffe://infra/ns/cndsc3/pod/fdr-fdcb9f8f6-tqqcj\" subsystem_name=manager\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Renewing X509-SVID\" entry_id=14d49a0a-2b58-4a7c-a0de-551df85d2fc1 spiffe_id=\"spiffe://infra/ns/infra/pod/registry-k8s-5cc46b8bbf-bk6wc\" subsystem_name=manager\ntime=\"2024-04-11T13:40:53Z\" level=info msg=\"Starting Workload and SDS APIs\" address=/run/spire/sockets/agent.sock network=unix subsystem_name=endpoints\ntime=\"2024-04-11T13:40:53Z\" level=warning msg=\"Container id not found\" attempt=1 container_id=0c2c4b591c6e68635a6cfff55c91a90244bfb85c2091d0f43874785ff39789a7 external=false plugin_name=k8s plugin_type=WorkloadAttestor pod_uid=1f39d257-6173-4a4e-ac25-3706dd13db63 retry_interval=500ms subsystem_name=catalog\n2024-04-11T13:40:58.743 Agent exit code: 137\n\nAs it can be seen on this graph, the average memory consumption is always below 200Mi but after restart there is a spike that causes the container restart:\nspire-agent-oomkilled\n\nCan you please help to understand if this behavior is normal? Is there any other way than further increasing the memory resource limit to make it stable?","reference_answer":"Yes, @Rishikesh01. That is the correct package for the Kubernetes workload attestor code.","answer_document_id":"gh_comment_2111010080","silver_evidence_path":["gh_comment_2087237867","gh_issue_2272424957","gh_comment_2111010080"],"known_context_document_ids":["gh_issue_2243116749"],"evidence_issue_ids":[2243116749,2272424957],"source_repo_name":"spiffe/spire","source_issue_id":2243116749,"source_issue_url":"https://github.com/spiffe/spire/issues/5067","target_repo_name":"spiffe/spire","target_issue_id":2272424957,"target_issue_url":"https://github.com/spiffe/spire/issues/5111","split":"dev","quality_score":80.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0145","query":"Sokol-shdc segfaults with glsl:100 because of variable shadowing?","query_context":"The shader:\n\nglsl\n@module threedee\n\n@vs vs\nin vec3 pos_in;\nin vec2 uv_in;\n\nout vec3 pos;\nout vec2 uv;\nout vec4 light_space_fragment_position;\n\nuniform vs_params {\n mat4 model;\n mat4 view;\n mat4 projection;\n mat4 directional_light_space_matrix; \n};\n\nvoid main() {\n pos = pos_in;\n uv = uv_in;\n\n vec4 frag_pos = view * model * vec4(pos_in, 1.0);\n gl_Position = projection * frag_pos;\n\n light_space_fragment_position = directional_light_space_matrix * frag_pos;\n}\n@end\n\n@fs fs\nuniform sampler2D tex;\nuniform sampler2D shadow_map;\n\nin vec3 pos;\nin vec2 uv;\nin vec4 light_space_fragment_position;\n\nout vec4 frag_color;\n\nfloat decodeDepth(vec4 rgba) {\n return dot(rgba, vec4(1.0, 1.0/255.0, 1.0/65025.0, 1.0/16581375.0));\n}\n\nfloat calculate_shadow_factor(sampler2D shadowMap, vec4 light_space_fragment_position) {\n float shadow = 1.0;\n\n vec3 projected_coords = light_space_fragment_position.xyz / light_space_fragment_position.w;\n\n if(projected_coords.z > 1.0)\n return shadow;\n\n projected_coords = projected_coords * 0.5f + 0.5f;\n\n float current_depth = projected_coords.z;\n\n vec2 shadow_map_size = textureSize(shadow_map, 0);\n vec2 uv = projected_coords.xy * shadow_map_size;\n\n shadow = decodeDepth(texture(shadowMap, uv));\n\n return shadow;\n}\n\nvoid main() {\n vec4 col = texture(tex, uv);\n if(col.a < 0.5)\n {\n discard;\n }\n else\n {\n vec3 light_dir = normalize(vec3(1, -1, 0));\n\n float shadow_factor = 1.0;//In percentage of light remaining, i.e. 1.0 full-bright, 0.0 fully shadowed\n shadow_factor = calculate_shadow_factor(shadow_map, light_space_fragment_position);\n\n frag_color = vec4(col.rgb*shadow_factor, 1.0);\n }\n}\n@end\n\n@program program vs fs","reference_answer":"I just implemented a fix to communicate the SPIRVCross error message instead of just crashing in branch `storage-buffer`. In case of your example shader the error message isn't very helpful, but better than nothing I guess:\n\n/Users/floh/projects/sokol-tools/test/issue_86.glsl:0:0: error: SPIRVCross exception: Access chains that result in an array can not be flattened\n\nUnfortunately I don't get line information back from SPIRVCross, only an error message. Closing this ticket (even though the fix isn't in the master branch yet).","answer_document_id":"gh_comment_2037763439","silver_evidence_path":["gh_comment_1620549656","gh_issue_1664663651","gh_comment_2037763439"],"known_context_document_ids":["gh_issue_1787072909"],"evidence_issue_ids":[1787072909,1664663651],"source_repo_name":"floooh/sokol-tools","source_issue_id":1787072909,"source_issue_url":"https://github.com/floooh/sokol-tools/issues/95","target_repo_name":"floooh/sokol-tools","target_issue_id":1664663651,"target_issue_url":"https://github.com/floooh/sokol-tools/issues/86","split":"dev","quality_score":86.41,"annotation_level":"silver"}
{"query_id":"cross_issue_0147","query":"[iOS] \"Original error: Command '/usr/bin/python' not found\" appear when use setLocation of a iOS Emulator on MAC Apple Silicon (M1)?","query_context":"## The problem\n\nWhen I call setLocation function appium return error \"Original error: Command '/usr/bin/python' not found\" and break test.\n<img width=\"820\" alt=\"Screen Shot 2022-08-08 at 23 10 18\" src=\" URL \n\n## Environment\n\n* Appium version (or git revision) that exhibits the issue: **Appium 1.22.3**\n* Last Appium version that did not exhibit the issue (if applicable): **N/A**\n* Desktop OS/version used to run Appium: **macOS Monterey 12.5 - M1Pro**\n* Node.js version (unless using Appium.app|exe): **v18.7.0**\n* Npm or Yarn package manager: **npm**\n* Mobile platform/version under test: iOS 15.5\n* Real device or emulator/simulator: XCode Emulator\n* Appium CLI or Appium.app|exe: Appium.app\n\n## Details\nThe error appear when I hit command: \n`driver.setLocation(new Location(0,0,0));`\n\n## Link to Appium logs\nGist\n\n## Code To Reproduce Issue [ Good To Have ]\n`driver.setLocation(new Location(0,0,0));`","reference_answer":"Newer versions are available via appium 2. You can get it via npm as `appium@next`.","answer_document_id":"gh_comment_1145633607","silver_evidence_path":["gh_comment_1208354224","gh_issue_1258187940","gh_comment_1145633607"],"known_context_document_ids":["gh_issue_1332101175"],"evidence_issue_ids":[1332101175,1258187940],"source_repo_name":"appium/appium","source_issue_id":1332101175,"source_issue_url":"https://github.com/appium/appium/issues/17334","target_repo_name":"appium/appium","target_issue_id":1258187940,"target_issue_url":"https://github.com/appium/appium/issues/17031","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0150","query":"Compressed, chunked response inhibits connection reuse?","query_context":"rust\nenv_logger::init();\nlet agent: Agent = ureq::AgentBuilder::new().build();\nfor _ in 0..2 {\n let resp = agent.get(\" URL \n println!(\"Connection: {}\", resp.header(\"connection\").unwrap());\n std::io::copy(&mut resp.into_reader(), &mut io::sink()).unwrap();\n}\n\nresults in (RUST_LOG=trace)\n\n[2022-10-17T01:02:37Z DEBUG ureq::stream] connecting to www.jammersreviews.com:443 at 172.67.140.111:443\n[2022-10-17T01:02:37Z DEBUG rustls::client::hs] No cached session for DnsName(DnsName(DnsName(\"www.jammersreviews.com\")))\n[...]\n[2022-10-17T01:02:37Z DEBUG ureq::stream] created stream: Stream(RustlsStream)\n[2022-10-17T01:02:37Z DEBUG ureq::unit] sending request GET URL \n[2022-10-17T01:02:37Z DEBUG ureq::unit] writing prelude: GET /st-tos/s1/dagger.php HTTP/1.1\n Host: www.jammersreviews.com\n User-Agent: ureq/2.5.0\n Accept: */*\n accept-encoding: gzip\n[2022-10-17T01:02:37Z DEBUG rustls::client::tls13] Ticket saved\n[2022-10-17T01:02:37Z DEBUG rustls::client::tls13] Ticket saved\n[2022-10-17T01:02:37Z DEBUG ureq::response] Chunked body in response\n[2022-10-17T01:02:37Z DEBUG ureq::unit] response 200 to GET URL \nConnection: keep-alive\n[2022-10-17T01:02:37Z DEBUG ureq::stream] dropping stream: Stream(RustlsStream)\n[2022-10-17T01:02:37Z DEBUG ureq::stream] connecting to www.jammersreviews.com:443 at 172.67.140.111:443\n[2022-10-17T01:02:37Z DEBUG rustls::client::hs] Resuming session\n[...]\n[2022-10-17T01:02:37Z DEBUG ureq::stream] created stream: Stream(RustlsStream)\n[2022-10-17T01:02:37Z DEBUG ureq::unit] sending request GET URL \n[2022-10-17T01:02:37Z DEBUG ureq::unit] writing prelude: GET /st-tos/s1/dagger.php HTTP/1.1\n Host: www.jammersreviews.com\n User-Agent: ureq/2.5.0\n Accept: */*\n accept-encoding: gzip\n[2022-10-17T01:02:37Z DEBUG rustls::client::tls13] Ticket saved\n[2022-10-17T01:02:37Z DEBUG rustls::client::tls13] Ticket saved\n[2022-10-17T01:02:37Z DEBUG ureq::response] Chunked body in response\n[2022-10-17T01:02:37Z DEBUG ureq::unit] response 200 to GET URL \nConnection: keep-alive\n[2022-10-17T01:02:37Z DEBUG ureq::stream] dropping stream: Stream(RustlsStream)\n\nAs can be seen, though TLS does session resumption, the TCP stream gets closed and reopened between requests. I believe this is caused by the fact that the `GzDecoder` knows when to expect the end of the gzip stream, never tries to read beyond it, and therefore never makes the read that causes the `ChunkDecoder` to give it Ok(0), which is what the `PoolReturnRead` looks for to know when to return the `Stream` to its pool. I was able to get it to work properly by using a `MultiGzDecoder` instead of a plain `GzDecoder`, at least in my private, heavily-modified version of ureq. But I don't think any such thing is available for Brotli.","reference_answer":"When we return the Stream to the pool, we can check that the `inner` `BufReader`'s buffer is empty.","answer_document_id":"gh_comment_1328015846","silver_evidence_path":["gh_comment_1340380401","gh_issue_1465065439","gh_comment_1328015846"],"known_context_document_ids":["gh_issue_1410754066"],"evidence_issue_ids":[1410754066,1465065439],"source_repo_name":"algesten/ureq","source_issue_id":1410754066,"source_issue_url":"https://github.com/algesten/ureq/issues/549","target_repo_name":"algesten/ureq","target_issue_id":1465065439,"target_issue_url":"https://github.com/algesten/ureq/issues/559","split":"dev","quality_score":85.67,"annotation_level":"silver"}
{"query_id":"cross_issue_0159","query":"Signal UI does not show on Debian Forky unless run with \"--disable-gpu\"?","query_context":"### Using a supported version?\n\n- [x] I have searched searched open and closed issues for duplicates.\n- [x] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.\n\n### Overall summary\n\nFollowing me updating all my packages in apt yesterday, Signal's UI stopped working, the app would appear in my panel, and I'd get notifications, but no UI would show. Running signal-desktop with the --disable-gpu flag allows it to launch and work again. When running signal-desktop from the terminal, I can see a bunch of GPU errors. Since I can't get a debug log from the app directly due to it not launching, I've attached that terminal log to the debug log section\n\n### Steps to reproduce\n\n1. Run Debian Forky (with Wayland)\n2. Install signal-desktop from Signal's official apt repo\n3. Launch signal-desktop\n4. UI fails to load\n\n### Expected result\n\nExpected result is for the UI to show.\n\n### Actual result\n\nCurrent result is the UI does not show at all.\n\n### Screenshots\n\n_No response_\n\n### Signal version\n\n7.78.0\n\n### Operating system\n\nDebian Forky with KDE Plasma 6.5.1 (Wayland)\n\n### Version of Signal on your phone\n\n_No response_\n\n### Link to debug log\n\nNODE_ENV production\nNODE_CONFIG_DIR /opt/Signal/resources/app.asar/config\nNODE_CONFIG {}\nALLOW_CONFIG_MUTATIONS undefined\nHOSTNAME debian\nNODE_APP_INSTANCE undefined\nSUPPRESS_NO_CONFIG_WARNING undefined\nSIGNAL_ENABLE_HTTP undefined\nuserData: /home/ivy/.config/Signal\n(node:16128) [DEP0180] DeprecationWarning: fs.Stats constructor is deprecated.\n(Use `signal-desktop --trace-deprecation ...` to show where the warning was created)\n[16403:1107/160301.991707:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16403:1107/160301.991816:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16403:1107/160301.991866:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16403:1107/160301.991926:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16403:1107/160301.991968:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16403:1107/160301.992016:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16403:1107/160301.992077:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16403:1107/160301.992125:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16403:1107/160301.992203:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16403:1107/160301.992308:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.\n[16403:1107/160301.992388:ERROR:components/viz/service/gl/exit_code.cc:13] Restarting GPU process due to unrecoverable error. Context was lost.\n[16128:1107/160301.999767:ERROR:content/browser/gpu/gpu_process_host.cc:964] GPU process exited unexpectedly: exit_code=8704\n[16460:1107/160302.077249:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16460:1107/160302.077328:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16460:1107/160302.077377:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16460:1107/160302.077417:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16460:1107/160302.077453:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16460:1107/160302.077485:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16460:1107/160302.077530:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16460:1107/160302.077563:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16460:1107/160302.077593:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16460:1107/160302.077638:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.\n[16460:1107/160302.077689:ERROR:components/viz/service/gl/exit_code.cc:13] Restarting GPU process due to unrecoverable error. Context was lost.\n[16128:1107/160302.084797:ERROR:content/browser/gpu/gpu_process_host.cc:964] GPU process exited unexpectedly: exit_code=8704\n[16505:1107/160302.166760:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16505:1107/160302.166840:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16505:1107/160302.166882:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16505:1107/160302.166925:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16505:1107/160302.166963:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16505:1107/160302.167005:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16505:1107/160302.167047:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=SCANOUT\n[16505:1107/160302.167084:ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:82] Cannot create bo with format= RGBA_8888 and usage=GPU_READ\n[16505:1107/160302.167118:ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:931] CreateSharedImage: could not create backing.\n[16505:1107/160302.167180:ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.\n[16505:1107/160302.167243:ERROR:components/viz/service/gl/exit_code.cc:13] Restarting GPU process due to unrecoverable error. Context was lost.\n[16128:1107/160302.176041:ERROR:content/browser/gpu/gpu_process_host.cc:964] GPU process exited unexpectedly: exit_code=8704","reference_answer":"Since this issue was opened, we started using `curve25519-n`, a native module. This should improve the performance of our curve25519 code by a lot.\n\nGiven that (and the fact that this issue has been inactive for over 3 years), I'm going to close. Happy to reopen if that's wrong.","answer_document_id":"gh_comment_689879564","silver_evidence_path":["gh_comment_3506753136","gh_issue_48250344","gh_comment_689879564"],"known_context_document_ids":["gh_issue_3601735997"],"evidence_issue_ids":[3601735997,48250344],"source_repo_name":"signalapp/Signal-Desktop","source_issue_id":3601735997,"source_issue_url":"https://github.com/signalapp/Signal-Desktop/issues/7586","target_repo_name":"signalapp/Signal-Desktop","target_issue_id":48250344,"target_issue_url":"https://github.com/signalapp/Signal-Desktop/issues/88","split":"dev","quality_score":81.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0162","query":"Some `cupyx.scipy.signal` APIs fall back to NumPy?","query_context":"Some `scipy.signal` APIs depend on `numpy.eigvals`, which computes the eigenvalues of a general matrix. However, cuSolver only provides the eigenvalue solver of a symmetric (Hermitian) matrix but does not the one of a general matrix. Therefore, the `cupyx.scipy.signal` counterparts of such APIs are currently implemented by falling back to `numpy.eigvals` or `numpy.roots`, which calls `numpy.eigvals`.\n\nSuch APIs include:\n- `cupyx.scipy.signal.findfreqs` #7641\n- `cupyx.scipy.signal.tf2zpk` #7652\n- `cupyx.scipy.signal.ss2tf` #7652\n\nSee:\n- URL \n- URL","reference_answer":"Yes! The new routine was meant for CuPy and other projects to implement `eig` and `eigvals`.","answer_document_id":"gh_comment_2468209117","silver_evidence_path":["gh_comment_1664905336","gh_issue_1110834324","gh_comment_2468209117"],"known_context_document_ids":["gh_issue_1823849646"],"evidence_issue_ids":[1823849646,1110834324],"source_repo_name":"cupy/cupy","source_issue_id":1823849646,"source_issue_url":"https://github.com/cupy/cupy/issues/7761","target_repo_name":"cupy/cupy","target_issue_id":1110834324,"target_issue_url":"https://github.com/cupy/cupy/issues/6359","split":"dev","quality_score":83.8,"annotation_level":"silver"}
{"query_id":"cross_issue_0163","query":"Inquiry Regarding LED Screen Procurement?","query_context":"(Please excuse my limited English proficiency; this message was translated with AI assistance.)\n\nDear Author,\n\nI am a DIY creator from China. While attempting to replicate your project, I encountered challenges in procuring the specific LED screen used. I would like to clarify the details of the LED panel you employed.\n\nFrom your referenced project link (about driving an LED screen with a Raspberry Pi 4), it seems you used a screen with a P1.875 pixel pitch, a 128x64 array, and FM6126 driver chips. ​Is this accurate?​​ (Note: This information might differ from your actual setup.)\n\nIf correct, manufacturers in China have informed me that FM6126-driven screens are discontinued. Could you provide guidance on driver alternatives? If your screen uses a different driver chip (which we sincerely hope is the case), please specify the chip model so we can source compatible panels from other suppliers.\n\nAdditionally, you shared a product link that directs to a flexible LED screen with a soft rubber base (now discontinued). However, your YouTube video appears to show a rigid screen. ​Did you actually use a flexible screen in your project?​​\n\nYour assistance would be immensely valuable. Thank you very much!","reference_answer":"I think you should step back and start again from an unmodified repo. If you daisy chain two 64x64 panels together, they should work as a single 128x64 panel. Both variants (vortex and rotovox) use two 128x64 panels, so we know that part works. If the image is the wrong way up, it's because the panels are the wrong way up.\nYou can't adjust the rotation of the image in the software. The orientation of the scan lines, and the order they're addressed, is fundamental to how the device works. It times its output to where the current scanline is physically located in space.\n\nVortex assumes two 128x64 panels arranged with horizontal scanlines, placed back to back. In this configuration, both panels have line 0 at the top, and line 63 at the bottom.\n\nRotovox assumes two 128x64 panels arranged vertically (with their scanlines vertical), and both facing the same way. One of the panels is upside down compared with the other. The point of this arrangement is to ensure that each corresponding scanline is at the same radius. Line 0 of both panels is closest to the axis, line 63 is furthest from the axis.\n\nIf you want to replicate one of these setups using four 64x64 panels, arrange them in two chains of 2, with each chain arranged so that their horizontal scanlines are aligned. Check that this works using `rpi-rgb-led` with no display transforms applied. The panels have to be side by side, the same way up, with scanline 0 extending across the top of both panels.\n(If that doesn't work, check whether `--led-rows=64 --led-cols=64 --led-chain=2` behaves the same way as `--led-rows=64 --led-cols=128 --led-chain=1` - the assumption I'm making is that they're equivalent, but I've never tested that.)\n\nIf none of that helps, it may still be possible to use make a smaller display using the 64x64 panels without chaining.","answer_document_id":"gh_comment_2829013265","silver_evidence_path":["gh_comment_2822974454","gh_issue_3012583703","gh_comment_2829013265"],"known_context_document_ids":["gh_issue_2995475862"],"evidence_issue_ids":[2995475862,3012583703],"source_repo_name":"AncientJames/VortexParts","source_issue_id":2995475862,"source_issue_url":"https://github.com/AncientJames/VortexParts/issues/5","target_repo_name":"AncientJames/multivox","target_issue_id":3012583703,"target_issue_url":"https://github.com/AncientJames/multivox/issues/5","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0169","query":"Add MiroTalk?","query_context":"_Best of JS_ is for the most popular open-source projects related to the web platform and Node.js.\n \nWhat is the URL of the project you'd like to add to _Best of JS_? \n\nGitHub: URL \nDemo: URL \n\nBefore submitting the request to add a new project, please check the following points:\n\n- ✅ The project is related to the web platform or Node.js\n- ✅ The project has more than 100 stars on GitHub\n- ✅ The project has thorough documentation in English\n- ✅ The project is not deprecated and actively maintained\n\nHow would this project be tagged? (Pick one or several existing tags from this list: URL \n\nWebRTC, Websocket, Real-Time\n \nAlso you can suggest new tags to add if you think _Best of JS_ is missing useful tags. \n\nself-hosted, sfu, p2p, web-app, video-conferencing, video-call, voip, streaming, file-sharing, screen-sharing, whiteboard","reference_answer":"Hello @nitad54448, \nWhat do you mean by `I get a certificate error` ? \nIf you using the MiroTalk SSL default certificates on: URL \nAt most the browser could tell you that it is an unknown certificate, you accept it and you can use Mirotalk in HTTPS.\nI haven't tried caddy, I usually use Let's Encrypt for trusted certificates.\nRegards","answer_document_id":"gh_comment_1065859831","silver_evidence_path":["gh_comment_1007905910","gh_issue_1013759860","gh_comment_1065859831"],"known_context_document_ids":["gh_issue_1096698404"],"evidence_issue_ids":[1096698404,1013759860],"source_repo_name":"michaelrambeau/bestofjs","source_issue_id":1096698404,"source_issue_url":"https://github.com/michaelrambeau/bestofjs/issues/448","target_repo_name":"miroslavpejic85/mirotalksfu","target_issue_id":1013759860,"target_issue_url":"https://github.com/miroslavpejic85/mirotalksfu/issues/14","split":"dev","quality_score":93.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0192","query":"Usage of NonBondedForce.setIncludeDirectSpace(False)?","query_context":"Hi,\n\nI've created a very simple test case where I have 3 Coulomb forces:\n\n1) NonBondedForce with PME\n2) CustomNonbondedForce of a Coulomb potential with PeriodicCutoff\n3) NonBondedForce.setIncludeDirectSpace(False) with PME\n\nSo if I'm not mistaklen, Force1 should be the sum of Force2 and Force3\n\nForce1 and Force2 has values that I would except. Force3 seems completely off though.\n\nIs this a bug? or am I missing something?\n\nThanks!\n\ntest_includedirectspace.zip","reference_answer":"Not exactly like that, but what you can do is have the NonbondedForce compute only the reciprocal space term. Do that by calling `setIncludeDirectSpace(False)`. Then you can use a CustomNonbondedForce to compute the direct space part, both Coulomb and LJ, in whatever way you want.","answer_document_id":"gh_comment_1850886150","silver_evidence_path":["gh_comment_1887762028","gh_issue_2036469035","gh_comment_1850886150"],"known_context_document_ids":["gh_issue_2073429889"],"evidence_issue_ids":[2073429889,2036469035],"source_repo_name":"openmm/openmm","source_issue_id":2073429889,"source_issue_url":"https://github.com/openmm/openmm/issues/4387","target_repo_name":"openmm/openmm","target_issue_id":2036469035,"target_issue_url":"https://github.com/openmm/openmm/issues/4349","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0196","query":"[CoE Starter Kit - BUG] Audit Component Issue?","query_context":"### Does this bug already exist in our backlog?\n\n- [X] I have checked and confirm this is a new bug.\n\n### Describe the issue\n\nHI,\n\nwe are facing an issue in Audit component and would like to reinstall only audit component , can you please help me on this \n\n### Expected Behavior\n\nPost upgrade also , Flow is still show the old connectors in the flow\n\nThe flow is not upgraded and didn't change the connectors\n\n### What solution are you experiencing the issue with?\n\nAudit Log\n\n### What solution version are you using?\n\n3.3\n\n### What app or flow are you having the issue with?\n\nAdmin | Sync Audit Logs\n\n### What method are you using to get inventory and telemetry?\n\nCloud flows\n\n### Steps To Reproduce\n\nPost upgrade also , Flow is still show the old connectors in the flow\n\nThe flow is not upgraded and didn't change the connectors\n\n### Anything else?\n\nPost upgrade also , Flow is still show the old connectors in the flow\n\nThe flow is not upgraded and didn't change the connectors","reference_answer":"You will need to hire someone that can sit with you to fix your situation then. Your environment is not in a state that I can assist in debugging remotely. \n\nThere are partners that specialize specifically in CoE Starter Kit, so you could reach out to them for assistance. You can find some via you can find them via AppSource\n\nAs a reminder, although the underlying features and components used to build the kit (such as Dataverse, admin APIs, and connectors) are fully supported, the kit itself represents sample implementations of these features. While we do our best to help people use them as is, they are not a supported feature.","answer_document_id":"gh_comment_1501903104","silver_evidence_path":["gh_comment_1512858519","gh_issue_1654114193","gh_comment_1501903104"],"known_context_document_ids":["gh_issue_1672394617"],"evidence_issue_ids":[1672394617,1654114193],"source_repo_name":"microsoft/coe-starter-kit","source_issue_id":1672394617,"source_issue_url":"https://github.com/microsoft/coe-starter-kit/issues/5314","target_repo_name":"microsoft/coe-starter-kit","target_issue_id":1654114193,"target_issue_url":"https://github.com/microsoft/coe-starter-kit/issues/5191","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0198","query":"JXL->JXL processing (to remove alpha channel) drops color profile?","query_context":"### ImageMagick version\n\n7.1.1-44\n\n### Operating system\n\nLinux\n\n### Operating system, version and so on\n\nFedora 41 x86_64\n\n### Description\n\nThe Fedora 42 background images are going to be distributed in JXL format instead of the traditional PNG. Due to the limitations of the GNOME background system's timed-transition image blending, it's necessary that background images be stripped of their alpha channel before installation. We've been accomplishing that with a `magick -alpha off` command, which works fine on PNG images.\n\nIt works fairly well on JXL images as well (with an added `-quality 100`), but the output image no longer carries the same color profile as the input image.\n\n### Steps to Reproduce\n\n## 1. Unzip and examine the original file:\n\nbash\n$ unzip f42-01-day.zip\nArchive: f42-01-day.zip\n inflating: f42-01-day.jxl \n\n$ identify -verbose f42-01-day.jxl\nImage:\n Filename: f42-01-day.jxl\n Permissions: rw-r--r--\n Format: JXL (JPEG XL (ISO/IEC 18181))\n Mime type: image/jxl\n Class: DirectClass\n Geometry: 4032x3024+0+0\n Units: Undefined\n Colorspace: sRGB\n Type: TrueColorAlpha\n Base type: Undefined\n Endianness: Undefined\n Depth: 8-bit\n Channels: 4.0\n Channel depth:\n Red: 8-bit\n Green: 8-bit\n Blue: 8-bit\n Alpha: 1-bit\n Channel statistics:\n Pixels: 12192768\n Red:\n min: 12 (0.0470588)\n max: 214 (0.839216)\n mean: 126.731 (0.496982)\n median: 133 (0.521569)\n standard deviation: 43.3644 (0.170056)\n kurtosis: -0.324868\n skewness: 0.0404497\n entropy: 0.749915\n Green:\n min: 5 (0.0196078)\n max: 224 (0.878431)\n mean: 137.296 (0.538416)\n median: 142 (0.556863)\n standard deviation: 47.5222 (0.186362)\n kurtosis: -0.608794\n skewness: -0.11526\n entropy: 0.76154\n Blue:\n min: 5 (0.0196078)\n max: 221 (0.866667)\n mean: 105.595 (0.414096)\n median: 90 (0.352941)\n standard deviation: 54.5139 (0.21378)\n kurtosis: -0.439243\n skewness: 0.766023\n entropy: 0.752578\n Alpha:\n min: 255 (1)\n max: 255 (1)\n mean: 255 (1)\n median: 255 (1)\n standard deviation: 0 (0)\n kurtosis: 0\n skewness: 0\n entropy: 0\n Image statistics:\n Overall:\n min: 5 (0.0196078)\n max: 255 (1)\n mean: 156.155 (0.612374)\n median: 155 (0.607843)\n standard deviation: 36.3501 (0.14255)\n kurtosis: -0.343226\n skewness: 0.172803\n entropy: 0.566008\n Rendering intent: Perceptual\n Gamma: 0.454545\n Chromaticity:\n red primary: (0.64,0.33,0.03)\n green primary: (0.3,0.6,0.1)\n blue primary: (0.15,0.06,0.79)\n white point: (0.3127,0.329,0.3583)\n Matte color: grey74\n Background color: white\n Border color: srgb(223,223,223)\n Transparent color: black\n Interlace: None\n Intensity: Undefined\n Compose: Over\n Page geometry: 4032x3024+0+0\n Dispose: Undefined\n Iterations: 0\n Compression: Undefined\n Orientation: TopLeft\n Profiles:\n Profile-icc: 9080 bytes\n Properties:\n date:create: 2025-03-11T23:48:07+00:00\n date:modify: 2025-03-11T08:05:06+00:00\n date:timestamp: 2025-03-11T23:48:55+00:00\n icc:copyright: Copyright 2015, Elle Stone (website: URL email: ellestone@ninedegreesbelow.com). This ICC profile is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License ( URL \n icc:description: sRGB-elle-V2-srgbtrc.icc\n mime:type: image/jxl\n signature: 6a090391cc3d126be6a5807503aeef4cfddce0c527120cbf76252cdaa7e4ddbd\n Artifacts:\n verbose: true\n Tainted: False\n Filesize: 1.93684MiB\n Number pixels: 12.1928M\n Pixel cache type: Memory\n Pixels per second: 13.1612MP\n User time: 2.440u\n Elapsed time: 0:01.926\n Version: ImageMagick 7.1.1-44 Q16-HDRI x86_64 22688 URL \n\nThe original image contains a 9k color profile, `sRGB-elle-V2-srgbtrc.icc`.\n\n## 2. Process the image using ImageMagick to remove alpha channel\n\nbash\n$ magick f42-01-day.jxl -quality 100 -alpha off f42-01-day_noalpha.jxl\n\n## 3. Examine the output file\n\nbash\n$ identify -verbose f42-01-day_noalpha.jxl\nImage:\n Filename: f42-01-day_noalpha.jxl\n Permissions: rw-r--r--\n Format: JXL (JPEG XL (ISO/IEC 18181))\n Mime type: image/jxl\n Class: DirectClass\n Geometry: 4032x3024+0+0\n Units: Undefined\n Colorspace: sRGB\n Type: TrueColor\n Base type: Undefined\n Endianness: Undefined\n Depth: 8-bit\n Channels: 3.0\n Channel depth:\n Red: 8-bit\n Green: 8-bit\n Blue: 8-bit\n Channel statistics:\n Pixels: 12192768\n Red:\n min: 12 (0.0470588)\n max: 214 (0.839216)\n mean: 126.731 (0.496982)\n median: 133 (0.521569)\n standard deviation: 43.3644 (0.170056)\n kurtosis: -0.324868\n skewness: 0.0404497\n entropy: 0.749915\n Green:\n min: 5 (0.0196078)\n max: 224 (0.878431)\n mean: 137.296 (0.538416)\n median: 142 (0.556863)\n standard deviation: 47.5222 (0.186362)\n kurtosis: -0.608794\n skewness: -0.11526\n entropy: 0.76154\n Blue:\n min: 5 (0.0196078)\n max: 221 (0.866667)\n mean: 105.595 (0.414096)\n median: 90 (0.352941)\n standard deviation: 54.5139 (0.21378)\n kurtosis: -0.439243\n skewness: 0.766023\n entropy: 0.752578\n Image statistics:\n Overall:\n min: 5 (0.0196078)\n max: 224 (0.878431)\n mean: 123.207 (0.483165)\n median: 121.667 (0.477124)\n standard deviation: 48.4668 (0.190066)\n kurtosis: -0.457635\n skewness: 0.230404\n entropy: 0.754678\n Rendering intent: Relative\n Gamma: 0.454545\n Chromaticity:\n red primary: (0.64,0.33,0.03)\n green primary: (0.3,0.6,0.1)\n blue primary: (0.15,0.06,0.79)\n white point: (0.3127,0.329,0.3583)\n Matte color: grey74\n Background color: white\n Border color: srgb(223,223,223)\n Transparent color: black\n Interlace: None\n Intensity: Undefined\n Compose: Over\n Page geometry: 4032x3024+0+0\n Dispose: Undefined\n Iterations: 0\n Compression: Undefined\n Orientation: TopLeft\n Profiles:\n Profile-icc: 536 bytes\n Properties:\n date:create: 2025-03-11T23:50:54+00:00\n date:modify: 2025-03-11T23:50:54+00:00\n date:timestamp: 2025-03-11T23:51:34+00:00\n icc:copyright: CC0\n icc:description: RGB_D65_SRG_Rel_SRG\n mime:type: image/jxl\n signature: bb19320a637ffbb342d9fcf381ea825659dbf8c10ac02fd768311252f2a68c33\n Artifacts:\n verbose: true\n Tainted: False\n Filesize: 1.9296MiB\n Number pixels: 12.1928M\n Pixel cache type: Memory\n Pixels per second: 14.5702MP\n User time: 2.270u\n Elapsed time: 0:01.836\n Version: ImageMagick 7.1.1-44 Q16-HDRI x86_64 22688 URL \n\nThe image no longer has an alpha channel (that's good!), but has lost the ICC profile and other metadata.\n\n## Delegate information:\n\nbash\n$ magick -list format|grep jxl\n JXL* JXL rw+ JPEG XL (ISO/IEC 18181) (libjxl 0.10.4)\n\n### Images\n\nHere's the first of the upcoming Fedora 42 background images, in source JXL format (with color profile): \n\nf42-01-day.zip","reference_answer":"The `-x` flag in cjxl is only used for inputs that can't have color profiles embedded (PPM, ect), otherwise it's taken from the original file. \nJPEG XL can use Color Enums instead of ICC profiles for common color spaces (sRGB, P3, Rec2020, ect). Usually this is only used for lossy, but it seems ImageMagick is incorrectly using Enums for lossless too. This has little to no impact visually, but it does remove the original ICC profile.\n\nUsing cjxl to recompress the source file retains the ICC in Lossless, and uses the sRGB Enum when set to lossy, confirming it as an ImageMagick bug. @sboukortt might know what area needs to be fixed though, likely just a missing flag.","answer_document_id":"gh_comment_2760646384","silver_evidence_path":["gh_comment_2759932405","gh_issue_2954682159","gh_comment_2760646384"],"known_context_document_ids":["gh_issue_2912159490"],"evidence_issue_ids":[2912159490,2954682159],"source_repo_name":"ImageMagick/ImageMagick","source_issue_id":2912159490,"source_issue_url":"https://github.com/ImageMagick/ImageMagick/issues/8022","target_repo_name":"libjxl/libjxl","target_issue_id":2954682159,"target_issue_url":"https://github.com/libjxl/libjxl/issues/4164","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0199","query":"`__vite_ssr_import_meta__.glob is not a function` Error During SSR?","query_context":"### Related plugins\n\n- [x] plugin-vue\n\n- [ ] plugin-vue-jsx\n\n### Describe the bug\n\nThis bug is a very strange one. When using SSR, I cannot use dynamic imports more than once in my Vue SFC if I add `class=\"whatever\"` to the root element. Please see the minimal reproduction, but here is a brief rundown:\n\n1. I'd like to do some ``import(`./dynamicA/${name}.json`)`` and some ``import(`./dynamicB/${name}.json`)`` in my Vue SFC... in other words, I'd like to using dynamic importing multiple times.\n2. When I do, the second dynamic import fails if I add `class=\"whatever\"` to the root element of my SFC.\n3. This is very surprising outcome, because as a developer I wouldn't expect my `class` attribute and dynamic imports to have anything to do with each other.\n\n### Reproduction\n\n URL \n\n### Steps to reproduce\n\nPlease see the minimal reproduction `README.md` for reproduction steps.\n\n### System Info\n\nshell\nSystem:\n OS: macOS 12.5\n CPU: (10) arm64 Apple M1 Pro\n Memory: 99.11 MB / 16.00 GB\n Shell: 5.8.1 - /bin/zsh\n Binaries:\n Node: 16.19.0 - ~/.volta/tools/image/node/16.19.0/bin/node\n npm: 8.19.3 - ~/.volta/tools/image/node/16.19.0/bin/npm\n Browsers:\n Chrome: 109.0.5414.119\n Safari: 15.6\n npmPackages:\n @vitejs/plugin-vue: ^4.0.0 => 4.0.0 \n vite: ^4.0.4 => 4.0.4\n\n### Used Package Manager\n\nnpm\n\n### Logs\n\n \n Click to expand! \n\nshell\n/entrypoints/App.vue:8\n console.log(\"[dynamicB/test.json#message]\", (await __vite_ssr_import_0__.default((__vite_ssr_import_meta__.glob(\"./dynamicB/*.json\")), `./dynamicB/${name}.json`)).default.message);\n ^\n\nTypeError: __vite_ssr_import_meta__.glob is not a function\n at asyncWrapper (/entrypoints/App.vue:8:110)\n\n \n\n### Validations\n\n- [X] Follow our Code of Conduct\n- [X] Read the Contributing Guidelines.\n- [X] Read the docs.\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.\n- [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.\n- [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.\n- [X] The provided reproduction is a minimal reproducible example of the bug.","reference_answer":"When ran without the parser, the tokenizer _will_ fail to distinguish regexps from division operators in some cases (because JavaScript cannot be tokenized without parsing). This is a known limitation, and not something that's fixable.","answer_document_id":"gh_comment_1413454994","silver_evidence_path":["gh_comment_1413986695","gh_issue_1563228395","gh_comment_1413454994"],"known_context_document_ids":["gh_issue_1562914587"],"evidence_issue_ids":[1562914587,1563228395],"source_repo_name":"vitejs/vite-plugin-vue","source_issue_id":1562914587,"source_issue_url":"https://github.com/vitejs/vite-plugin-vue/issues/96","target_repo_name":"acornjs/acorn","target_issue_id":1563228395,"target_issue_url":"https://github.com/acornjs/acorn/issues/1191","split":"dev","quality_score":83.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0202","query":"Stack custom items even if NBT data order is different?","query_context":"### Terms\n\n- [x] I'm using the very latest version of ItemsAdder and its dependencies.\n- [x] I am sure this is a bug and it is not caused by a misconfiguration or by another plugin.\n- [x] I've looked for already existing issues on the Issue Tracker and haven't found any.\n- [x] I already searched on the plugin wiki to know if a solution is already known.\n- [x] I searched the `#itemsadder-forum` channel on Discord for similar issues.\n- [x] I tested that this issue persists on a **bare-minimum Server** as described in #4187.\n\n### Discord Username (optional)\n\n_No response_\n\n### What happened?\n\nAfter the plugin update, many things broke. 1st problem is, that order of nbt tags has been randomly changed, so now the old items cannot stack with a new one.\n\nImage\n\ncauses issues like this (the purple item)\n\nImage\n\ngg\n\n### Steps to reproduce the issue\n\nIdk updete the plugin from 4.0.7 to 4.0.9\n\n### Server version\n\nPaper 1.21.1 v132\n\n### ItemsAdder Version\n\n4.0.9\n\n### ProtocolLib Version\n\nProtocolLib version 5.4.0-SNAPSHOT-741\n\n### LoneLibs Version\n\nLoneLibs version 1.0.65\n\n### Full Server Log\n\n URL \n\n### Error (optional)\n\nshell\n\n### Problematic items yml configuration file (optional)\n\nyaml\n\n### Other files, you can drag and drop them here to upload. (optional)\n\n_No response_\n\n### Screenshots/Videos (you can drag and drop files or paste links)\n\n_No response_","reference_answer":"This seems to be a MMOitems bug not ItemsAdder bug.\nAs I said:\n \n\nThis is not an ItemsAdder bug.","answer_document_id":"gh_comment_1496225278","silver_evidence_path":["gh_comment_2730318151","gh_issue_1646868078","gh_comment_1496225278"],"known_context_document_ids":["gh_issue_2900044991"],"evidence_issue_ids":[2900044991,1646868078],"source_repo_name":"PluginBugs/Issues-ItemsAdder","source_issue_id":2900044991,"source_issue_url":"https://github.com/PluginBugs/Issues-ItemsAdder/issues/4497","target_repo_name":"PluginBugs/Issues-ItemsAdder","target_issue_id":1646868078,"target_issue_url":"https://github.com/PluginBugs/Issues-ItemsAdder/issues/2473","split":"dev","quality_score":83.5,"annotation_level":"silver"}
{"query_id":"cross_issue_0207","query":"MCAD Multi-Cluster + KubeStellar Integration (Stage-1)?","query_context":"### Feature Description\n\nMCAD as one of the options for the job queuing and scheduling interface for KubeStellar.\n\n### Proposed Solution\n\nStage-1: MCAD dispatcher deploys appWrappers to MCAD agent clusters and collects AppWrapper status via KubeStellar\nStage-2: new MCAD observability paths (e.g., metrics collection: Prometheus, Thanos, Observatorium, etc.) enable by KubeStellar\n\n### Want to contribute?\n\n- [ ] I would like to work on this issue.\n\n### Additional Context\n\nThe gaps identified for stage-1 are the following:\n\ni) MCAD dispatcher needs to create a KubeStellar EdgePlacement objects. The EdgePlacement object is used to select a target cluster to deploy a workload (e.g., AppWrapper)\n\nii) MCAD dispatcher needs to deploy AppWrappers and EdgePlacement objects to KubeStellar Workload Management Workspaces (WMW)\n\niii) MCAD dispatcher needs to use an informer library to collect appWrapper status from KubeStellar","reference_answer":"Thanks @dumb000!, \n\n@asm582 , I tagged this one as well with multi-cluster label.","answer_document_id":"gh_comment_1656249359","silver_evidence_path":["gh_comment_1656299812","gh_issue_1827007119","gh_comment_1656249359"],"known_context_document_ids":["gh_issue_1826714794"],"evidence_issue_ids":[1826714794,1827007119],"source_repo_name":"project-codeflare/multi-cluster-app-dispatcher","source_issue_id":1826714794,"source_issue_url":"https://github.com/project-codeflare/multi-cluster-app-dispatcher/issues/521","target_repo_name":"project-codeflare/multi-cluster-app-dispatcher","target_issue_id":1827007119,"target_issue_url":"https://github.com/project-codeflare/multi-cluster-app-dispatcher/issues/524","split":"dev","quality_score":85.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0210","query":"Show percentage?","query_context":"While using the app, I found that sometimes I need to finish pomodoro timer early. In that case, I want to record how much did I spend - 70%, 50% for example. Let's make this option\n\nThis is adding new column named percentage","reference_answer":"Hello, @TheRustyPickle. I'm sorry that I'm so busy (😢) that I have not researched about this issue.\nSo correct me if I'm wrong. \nAs I commented above, I found clap supports `clap_complete`. Could you take a look and see if it solves this issue?","answer_document_id":"gh_comment_1445140347","silver_evidence_path":["gh_comment_1444761047","gh_issue_1236602971","gh_comment_1445140347"],"known_context_document_ids":["gh_issue_1452514134"],"evidence_issue_ids":[1452514134,1236602971],"source_repo_name":"24seconds/rust-cli-pomodoro","source_issue_id":1452514134,"source_issue_url":"https://github.com/24seconds/rust-cli-pomodoro/issues/126","target_repo_name":"24seconds/rust-cli-pomodoro","target_issue_id":1236602971,"target_issue_url":"https://github.com/24seconds/rust-cli-pomodoro/issues/63","split":"dev","quality_score":77.63,"annotation_level":"silver"}
{"query_id":"cross_issue_0216","query":"Could not open '/lib64/ld-linux-x86-64.so.2' during devcontainer build?","query_context":"I'm trying to create a small dev container via VS Code's \"Add Dev Container Configuration Files\" option. I have selected only a couple other features (\"docker-in-docker\", \"go\", \"python\", and \"pre-commit\"). \n\nEvery time I select the pre-commit feature (also happens when manually adding the `\"ghcr.io/devcontainers-contrib/features/pre-commit:2\": {}` feature to the devcontainer.json) I see the following error when trying to build the devcontainer:\n\n[2022-12-29T16:13:59.722Z] ------\n \n#0 0.134 ===========================================================================\n#0 0.134 Feature : Pre-Commit (via pipx)\n#0 0.134 Description : Pre-Commit is a framework for managing and maintaining multi-language pre-commit hooks.\n#0 0.134 Id : ghcr.io/devcontainers-contrib/features/pre-commit\n#0 0.134 Version : 2.0.0\n#0 0.134 Documentation : URL \n#0 0.134 Options :\n#0 0.134 VERSION=\"latest\"\n#0 0.134 ===========================================================================\n#0 0.792 featmake: OK\n#0 0.808 qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory\n[2022-12-29T16:13:59.722Z] #0 0.810 ERROR: Feature \"Pre-Commit (via pipx)\" (ghcr.io/devcontainers-contrib/features/pre-commit) failed to install! Look at the documentation at URL for help troubleshooting this error.\n------\n[2022-12-29T16:13:59.722Z] ERROR: failed to solve: executor failed running [/bin/sh -c cd /tmp/build-features/pre-commit_4 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh]: exit code: 255\n\nFor reference I'm running this on a 2021 16-inch MacBookPro with Apple M1 Pro processor (could the error be related to running this on an ARM processor?). Might I be missing something? The devcontainer works fine when removing the pre-commit feature and installing pre-commit manually (using pip3, for example).","reference_answer":"from version 0.0.16 and up featmake is now not a binary but a raw shell script, you can open it with any text editor","answer_document_id":"gh_comment_1399239126","silver_evidence_path":["gh_comment_1382044337","gh_issue_1515951110","gh_comment_1399239126"],"known_context_document_ids":["gh_issue_1514016009"],"evidence_issue_ids":[1514016009,1515951110],"source_repo_name":"devcontainers-contrib/features","source_issue_id":1514016009,"source_issue_url":"https://github.com/devcontainers-contrib/features/issues/223","target_repo_name":"devcontainers-contrib/features","target_issue_id":1515951110,"target_issue_url":"https://github.com/devcontainers-contrib/features/issues/246","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0218","query":"Reference id not matching with documentElement id?","query_context":"**To Reproduce**\n\nReceiving this response from Azure AD:\n\nxml\n \n STRIPPED \n \n \n \n \n STRIPPED \n \n \n \n \n STRIPPED \n \n \n STRIPPED \n \n \n STRIPPED \n \n \n \n \n STRIPPED \n \n \n \n \n \n STRIPPED \n \n \n \n STRIPPED \n \n STRIPPED \n \n STRIPPED \n \n STRIPPED \n \n urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport \n URL \n \n STRIPPED \n STRIPPED \n STRIPPED \n \n STRIPPED \n \n STRIPPED \n \n STRIPPED \n \n STRIPPED \n \n \n \n \n urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport \n \n \n \n \n\nWhen validating the signature, the documentElement of the SAML response is used and the reference id tries to match with the id of it. But they don't match, instead the reference id matches with the ` `-Element id, thus successfully validating the signature is not possible.\n\n**Expected behavior**\nSignature should validate successfully.\n\n**Environment**\n\n- Node.js version: 16.14.0\n- `passport-saml` version: 4.0.4","reference_answer":"The change was intended as it is in harmony with the secure-by-default philosophy that we have here. Please feel free to put up a PR to help us with our README.","answer_document_id":"gh_comment_1828405987","silver_evidence_path":["gh_comment_1572152351","gh_issue_1677161072","gh_comment_1828405987"],"known_context_document_ids":["gh_issue_1736068303"],"evidence_issue_ids":[1736068303,1677161072],"source_repo_name":"node-saml/passport-saml","source_issue_id":1736068303,"source_issue_url":"https://github.com/node-saml/passport-saml/issues/863","target_repo_name":"node-saml/passport-saml","target_issue_id":1677161072,"target_issue_url":"https://github.com/node-saml/passport-saml/issues/859","split":"dev","quality_score":85.4,"annotation_level":"silver"}
{"query_id":"cross_issue_0227","query":"FS22 Lumberjack nopt working in multiplayer/dedicated server?","query_context":"I noticed that deleting trees by using the chainsaw red ring no longer works in multiplayer. When the tree or stump is supposed to disappear the chainsaw snaps back a bit but just continues to saw and spew sahavings. Nothing else happens. In career mode it still works like a charm :)\n\nDo we know why this is?","reference_answer":"Please let me know if this version has resolved the issue: URL \n\nI guess it will not do anything to your terrain issue caused by previously removed trees, but hopefully should prevent the problem occuring again.","answer_document_id":"gh_comment_1122211678","silver_evidence_path":["gh_comment_1164919482","gh_issue_1222204688","gh_comment_1122211678"],"known_context_document_ids":["gh_issue_1282979174"],"evidence_issue_ids":[1282979174,1222204688],"source_repo_name":"loki79uk/FS22_LumberJack","source_issue_id":1282979174,"source_issue_url":"https://github.com/loki79uk/FS22_LumberJack/issues/5","target_repo_name":"loki79uk/FS22_LumberJack","target_issue_id":1222204688,"target_issue_url":"https://github.com/loki79uk/FS22_LumberJack/issues/4","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0232","query":"Icecast only loading or no sound on iOS in Angular?","query_context":"Hello Ethan,\n\nfirst of all thank you for your hard work. I really like it and it works perfectly on Android. Unfortunately I can't get it to work on iOS. I am using Ionic and Angular. The stream is loading (network tab of developer console), but I can't hear anything. The event listener gives success on play, no error. The stream keeps on loading.\n\nIf I use a standard html5 audio without your script the stream plays fine. I really look forward to use your icecast-metadata-player.\n\nDo you have any idea?","reference_answer":"After you've cloned the repo, and checked out the PR, you can point directly to the `icecast-metadata-player` folder in your `package.json`. Example: `\"icecast-metadata-player:\" \"file:path-to-icecast-metadata-js-clone/src/icecast-metadata-player\"`. I use this method every time I am testing with the demo page.","answer_document_id":"gh_comment_1073268546","silver_evidence_path":["gh_comment_1132359999","gh_issue_1154526730","gh_comment_1073268546"],"known_context_document_ids":["gh_issue_1203245435"],"evidence_issue_ids":[1203245435,1154526730],"source_repo_name":"eshaz/icecast-metadata-js","source_issue_id":1203245435,"source_issue_url":"https://github.com/eshaz/icecast-metadata-js/issues/119","target_repo_name":"eshaz/icecast-metadata-js","target_issue_id":1154526730,"target_issue_url":"https://github.com/eshaz/icecast-metadata-js/issues/107","split":"dev","quality_score":91.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0244","query":"Double free() in global object destruction in 7.10.1 (regression from 7.10.0)?","query_context":"I'm getting double free() error of memory block allocated by **pqxx::internal::demangle_type_name**.\n\nSystem: Arch Linux\nlibpqxx version: 7.10.1\nUsed compiler: clang++ 20.1.6\n\nValgrind output:\n`[pavenis@ap test]$ valgrind ./CellTest \n==1688117== Memcheck, a memory error detector\n==1688117== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.\n==1688117== Using Valgrind-3.25.1 and LibVEX; rerun with -h for copyright info\n==1688117== Command: ./CellTest\n==1688117== \n\nCell tests\n==========\nRunning 2 test cases...\n+ [is_saddle(Cell)]\n+ [minmax(Cell)]\n\n*** No errors detected\n==1688117== Invalid free() / delete / delete[] / realloc()\n==1688117== at 0x496D8DD: operator delete(void*, unsigned long) (vg_replace_malloc.c:1181)\n==1688117== by 0x672C05F: __cxa_finalize (cxa_finalize.c:97)\n==1688117== by 0x9033B97: ??? (in /usr/lib/libpqxx-7.10.so)\n==1688117== by 0x4125FD1: _dl_call_fini (dl-call_fini.c:43)\n==1688117== by 0x41291B1: _dl_fini (dl-fini.c:120)\n==1688117== by 0x672C5E0: __run_exit_handlers (exit.c:118)\n==1688117== by 0x672C6BD: exit (exit.c:148)\n==1688117== by 0x67136BB: (below main) (libc_start_call_main.h:74)\n==1688117== Address 0xbd623c0 is 0 bytes inside a block of size 129 free'd\n==1688117== at 0x496D8DD: operator delete(void*, unsigned long) (vg_replace_malloc.c:1181)\n==1688117== by 0x4062D64: std::__new_allocator ::deallocate(char*, unsigned long) (new_allocator.h:172)\n==1688117== by 0x4062CCF: deallocate (allocator.h:215)\n==1688117== by 0x4062CCF: deallocate (alloc_traits.h:649)\n==1688117== by 0x4062CCF: std::__cxx11::basic_string , std::allocator >::_M_destroy(unsigned long) (basic_string.h:305)\n==1688117== by 0x4062BD9: std::__cxx11::basic_string , std::allocator >::_M_dispose() (basic_string.h:299)\n==1688117== by 0x404CB48: std::__cxx11::basic_string , std::allocator >::~basic_string() (basic_string.h:896)\n==1688117== by 0x672C05F: __cxa_finalize (cxa_finalize.c:97)\n==1688117== by 0x69B55E7: ??? (in /usr/lib/libsmartmet-macgyver.so)\n==1688117== by 0x4125FD1: _dl_call_fini (dl-call_fini.c:43)\n==1688117== by 0x41291B1: _dl_fini (dl-fini.c:120)\n==1688117== by 0x672C5E0: __run_exit_handlers (exit.c:118)\n==1688117== by 0x672C6BD: exit (exit.c:148)\n==1688117== by 0x67136BB: (below main) (libc_start_call_main.h:74)\n==1688117== Block was alloc'd at\n==1688117== at 0x4969F93: operator new(unsigned long) (vg_replace_malloc.c:487)\n==1688117== by 0x904ABC5: UnknownInlinedFun (new_allocator.h:151)\n==1688117== by 0x904ABC5: UnknownInlinedFun (alloc_traits.h:614)\n==1688117== by 0x904ABC5: UnknownInlinedFun (basic_string.h:142)\n==1688117== by 0x904ABC5: UnknownInlinedFun (basic_string.tcc:164)\n==1688117== by 0x904ABC5: UnknownInlinedFun (basic_string.tcc:235)\n==1688117== by 0x904ABC5: UnknownInlinedFun (basic_string.h:692)\n==1688117== by 0x904ABC5: pqxx::internal::demangle_type_nameabi:cxx11 (strconv.cxx:245)\n==1688117== by 0x69B47CB: __cxx_global_var_init.33 (strconv.hxx:80)\n==1688117== by 0x41292F6: call_init (dl-init.c:74)\n==1688117== by 0x41292F6: call_init (dl-init.c:26)\n==1688117== by 0x41293CC: _dl_init (dl-init.c:121)\n==1688117== by 0x414161F: ??? (in /usr/lib/ld-linux-x86-64.so.2)\n==1688117== \n==1688117== \n==1688117== HEAP SUMMARY:\n==1688117== in use at exit: 330 bytes in 5 blocks\n==1688117== total heap usage: 7,058 allocs, 7,054 frees, 1,461,985 bytes allocated\n==1688117== \n==1688117== LEAK SUMMARY:\n==1688117== definitely lost: 129 bytes in 1 blocks\n==1688117== indirectly lost: 0 bytes in 0 blocks\n==1688117== possibly lost: 0 bytes in 0 blocks\n==1688117== still reachable: 201 bytes in 4 blocks\n==1688117== suppressed: 0 bytes in 0 blocks\n==1688117== Rerun with --leak-check=full to see details of leaked memory\n==1688117== \n==1688117== For lists of detected and suppressed errors, rerun with: -s\n==1688117== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)\n`\n\nProgram was a one of the test of URL","reference_answer":"No need to change compilers for this... Don't get me wrong, clang is an excellent compiler. But one of those tricks to producing top-quality code is to run it through as many compilers as you can, and pay attention to the errors or warnings they produce.\n\nSo... do both. :-)","answer_document_id":"gh_comment_1536803949","silver_evidence_path":["gh_comment_3027685448","gh_issue_1693971058","gh_comment_1536803949"],"known_context_document_ids":["gh_issue_3192217050"],"evidence_issue_ids":[3192217050,1693971058],"source_repo_name":"jtv/libpqxx","source_issue_id":3192217050,"source_issue_url":"https://github.com/jtv/libpqxx/issues/1007","target_repo_name":"jtv/libpqxx","target_issue_id":1693971058,"target_issue_url":"https://github.com/jtv/libpqxx/issues/681","split":"dev","quality_score":93.08,"annotation_level":"silver"}
{"query_id":"cross_issue_0246","query":"[Bug]: storage stopped working in termux:api 0.51.0?","query_context":"### Problem description\n\nStorage stopped working when updating Termux:API to 0.51.0\n\nDon't know what the old version was, it was probably like 3 months old but I'm not sure. \n`cd storage` works, but I cannot navigate to anything inside storage.\nQuote\n\nu0_a318@localhost:~$ cd storage/movies\nbash: cd: storage/movies: Permission denied\nu0_a318@localhost:~$ namei -l storage/movies\nf: storage/movies\ndrwx------ u0_a318 u0_a318 storage\nlrwxrwxrwx u0_a318 u0_a318 movies -> /storage/emulated/0/Movies\ndrwxr-xr-x root root /\ndrwx--x--x shell everybody storage\ndrwxrwx--- media_rw media_rw emulated\ndrwxrws--- media_rw media_rw 0\ndrwxrws--- u0_a309 media_rw Movies\nu0_a318@localhost:~$ id\nuid=10318(u0_a318) gid=10318(u0_a318) groups=10318(u0_a318),3003(inet),9997(everybody),20318(u0_a318_cache),50318(all_a318) context=u:r:untrusted_app_27:s0:c62,c257,c512,c768\n\nIt was working perfectly before the Termux:API update.\n\nSource: F-droid\nTermux 0.118.2\nTermux:API 0.51.0\nPhone: Samsung Galaxy S24 Ultra \nAndroid 14 \n\nStorage was working perfectly before the Termux:API update.\n\n### Steps to reproduce the behavior.\n\n- Update to Termux:API 0.51.0\n- cd storage/movies\nbash: cd: storage/movies: Permission denied\n\n### What is the expected behavior?\n\nNo error.\n\n### System information\n\n* Termux application version: 0.118.2\n* Android OS version: 14\n* Device model: Samsung Galaxy S24 Ultra","reference_answer":"Seems like firmware related bug. Usually OS does not automatically revoke permissions day after user grants it.","answer_document_id":"gh_comment_2815556706","silver_evidence_path":["gh_comment_2816773924","gh_issue_2980104140","gh_comment_2815556706"],"known_context_document_ids":["gh_issue_3006374922"],"evidence_issue_ids":[3006374922,2980104140],"source_repo_name":"termux/termux-app","source_issue_id":3006374922,"source_issue_url":"https://github.com/termux/termux-app/issues/4506","target_repo_name":"termux/termux-app","target_issue_id":2980104140,"target_issue_url":"https://github.com/termux/termux-app/issues/4486","split":"dev","quality_score":86.57,"annotation_level":"silver"}
{"query_id":"cross_issue_0257","query":"[flang][LoongArch] Runtime error in spec2017 527.cam4_r with size=ref and optimization levels \"-O3\"/\"-Ofast\"?","query_context":"Tested OS: Debian sid/experimental loong64 installed with llvm 20.1.3\n\nOptimization setting:\n\n`COPTIMIZE = -g -Ofast -march=la464 -flto=auto`\n`FOPTIMIZE = -g -Ofast -march=la464 -flto=auto`\n\nWhen I test spec2017 527.cam4_r with above optimization setting and ref size, I met the following error:\n\nrun_base_refrate_mytest_llvm_20d1d3-m64.0000 -f compare.cmd -E -e compare.err -o compare.stdout'; no non-empty output files exist\n Command returned exit code 1\n****************************************\nContents of cam4_r_base.mytest_llvm_20d1d3-m64.err\n****************************************\nFortran STOP\nIEEE arithmetic exceptions signaled: DIVBYZERO INEXACT INVALID OVERFLOW UNDERFLOW\n\n****************************************\n*** Miscompare of cam4_validate.txt\n\nThe content in miscomparison file is:\n\n0001: PASS: 4 points. \n PASS: 0 points. \n ^\n\nThe above error still appears when I change the optimization level of Fortran part to `-O3`. If the optimization level of Fortran part is `-O2` or lower, the program can run smoothly.\n\nThe above error only appears with ref size, with test/train sizes the program can run smoothly at optimization level of Fortran part `-Ofast`.","reference_answer":"@llvm/issue-subscribers-backend-loongarch\n\nAuthor: None (azuresky01)\n\n \nTested OS: Debian sid/experimental loong64 installed with llvm 20.1.3\n\nOptimization setting:\n\nCOPTIMIZE = -Ofast -march=la464 -flto=auto -fno-strict-aliasing\nFOPTIMIZE = -Ofast -march=la464 -flto=auto\n\nWhen I test spec2006 416.gamess with above optimization setting and ref size, I met the following error:\n\nrun_base_ref_llvm-64bit-test.0000 -c 1 -e compare.err -o compare.stdout -f compare.cmd\n\n****************************************\nContents of triazolium.err\n****************************************\nFortran STOP: IN ABRT\nIEEE arithmetic exceptions signaled: INEXACT INVALID\n\n****************************************\n\n****************************************\nContents of h2ocu2+.gradient.err\n****************************************\nFortran STOP\nIEEE arithmetic exceptions signaled: INEXACT INVALID UNDERFLOW\n\n****************************************\n\n****************************************\nContents of cytosine.2.err\n****************************************\nFortran STOP\nIEEE arithmetic exceptions signaled: INEXACT INVALID\n\n****************************************\n\n*** Miscompare of triazolium.out\n\nthe content of triazolium.out.mis in this example:\n\n0654: ----- FROZEN CORE ENERGY = -1092.06138801\n ----- FROZEN CORE ENERGY = -1089.34489867\n ^\n0679: STATE 1 ENERGY= -585.3957141489 S= 0.00 SZ= 0.00 SPACE SYM=A' \n STATE 1 ENERGY= -582.6821224495 S= 0.00 SZ= 0.00 SPACE SYM=A' \n ^\n0685: 0.9779593\n 0.9781004\n ^\n0686: -0.0838917\n -0.0834754\n ^\n0687: -0.0700851\n -0.0703953\n ^\n0688: -0.0681958\n -0.0681070\n ^\n0689: 0.0622926\n 0.0622399\n ^\n0690: 0.0622926\n 0.0622399\n ^\n0691: -0.0566227\n -0.0564314\n ^\n0703: STATE= 1 ENERGY= -585.3957141489 WEIGHT= 1.00000 S= 0.00\n STATE= 1 ENERGY= -582.6821224495 WEIGHT= 1.00000 S= 0.00\n\nThe above error still appears when I change the optimization level of Fortran part to `-O3` or `-O2`. If the optimization level of Fortran part is `-O1` or lower, the program can run smoothly.\n\nThe above error only appears with ref size, with test/train sizes the program can run smoothly at optimization level of Fortran part `-Ofast`.","answer_document_id":"gh_comment_2829288017","silver_evidence_path":["gh_comment_2832880508","gh_issue_3014357058","gh_comment_2829288017"],"known_context_document_ids":["gh_issue_3014322436"],"evidence_issue_ids":[3014322436,3014357058],"source_repo_name":"llvm/llvm-project","source_issue_id":3014322436,"source_issue_url":"https://github.com/llvm/llvm-project/issues/136971","target_repo_name":"llvm/llvm-project","target_issue_id":3014357058,"target_issue_url":"https://github.com/llvm/llvm-project/issues/137000","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0258","query":"Topcoder Archive issue?","query_context":"This is not actually issue, it is actually a suggestion that TopCoder single round matches(SRM) archive has a lot of good quality questions as it is now shutdown, we are unable to submit the solutions and judge the code.\nThe archive now is available with a questions and all the testcases. It is difficult to manually check all the testcases if we could make something for it which is similar to that we have for codeforces and atcoder it would be good.","reference_answer":"I understand your use case of having quick access to a local file in an environment that's all set to get going, but it's not what this extension is built for, and easily something that external tools can provide on their own.\n \n\nI don't agree. I'm not willing to drop the aforementioned consistency for the sake of adding partial parsers that are (in my opinion) out-of-scope for this extension.","answer_document_id":"gh_comment_1157063428","silver_evidence_path":["gh_comment_3366108544","gh_issue_1244089211","gh_comment_1157063428"],"known_context_document_ids":["gh_issue_3409553686"],"evidence_issue_ids":[3409553686,1244089211],"source_repo_name":"jmerle/competitive-companion","source_issue_id":3409553686,"source_issue_url":"https://github.com/jmerle/competitive-companion/issues/636","target_repo_name":"jmerle/competitive-companion","target_issue_id":1244089211,"target_issue_url":"https://github.com/jmerle/competitive-companion/issues/245","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0266","query":"Search broken in docs?","query_context":"# Bug report\n\n## Describe the bug\n\nLooks like searching documentation is broken!\n\n## To Reproduce\n\nSteps to reproduce the behavior, please provide code snippets or a repository:\n1. Go to URL \n2. Click on the Search box\n3. Type anything in the search box\n\n## Expected behavior\nResults\n\n## Actual behavior\nThe UI says I'm offline, the console is full of net::ERR_NAME_NOT_RESOLVED\n\n## Screenshots\nScreen Shot 2022-03-22 at 11 04 08 AM\n\n## System information\nMac, Chrome","reference_answer":"You're welcome to help here @Hallidayo - I don't know what the `appId` should be in this case - perhaps just `supabase`?","answer_document_id":"gh_comment_1073799317","silver_evidence_path":["gh_comment_1075699912","gh_issue_1157355690","gh_comment_1073799317"],"known_context_document_ids":["gh_issue_1177126839"],"evidence_issue_ids":[1177126839,1157355690],"source_repo_name":"supabase/supabase","source_issue_id":1177126839,"source_issue_url":"https://github.com/supabase/supabase/issues/6007","target_repo_name":"supabase/supabase","target_issue_id":1157355690,"target_issue_url":"https://github.com/supabase/supabase/issues/5762","split":"dev","quality_score":86.15,"annotation_level":"silver"}
{"query_id":"cross_issue_0267","query":"Firefox browser extention does not automatically or manually lock anymore?","query_context":"### Steps To Reproduce\n\n1. Restart Firefox\n2. Unlock Bitwarden\n3. Use the browser a bit\n4. Try to lock Bitwarden\n\n### Expected Result\n\nExpected the extention to lock and require password/PIN.\n\n### Actual Result\n\nDoes not do anything.\n\n### Screenshots or Videos\n\n_No response_\n\n### Additional Context\n\nWhen I try to to it manually in the Settings in the extension it also does nothing.\n\n### Operating System\n\nmacOS\n\n### Operating System Version\n\n12.5.1\n\n### Web Browser\n\nFirefox\n\n### Browser Version\n\n104.0.2\n\n### Build Version\n\n2022.8.0","reference_answer":"Since this issue has been open for quite some time without recent activity, I'm curious if anyone is still experiencing this problem. If the issue persists, please share any updated details. Thanks, everyone, for your contributions and feedback!","answer_document_id":"gh_comment_2309979711","silver_evidence_path":["gh_comment_1257027550","gh_issue_1334980463","gh_comment_2309979711"],"known_context_document_ids":["gh_issue_1379995556"],"evidence_issue_ids":[1379995556,1334980463],"source_repo_name":"bitwarden/clients","source_issue_id":1379995556,"source_issue_url":"https://github.com/bitwarden/clients/issues/3570","target_repo_name":"bitwarden/clients","target_issue_id":1334980463,"target_issue_url":"https://github.com/bitwarden/clients/issues/3274","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0275","query":"CONAN_BASE_PROFILE_BUILD is not correctly passed to Docker?","query_context":"### Description of Problem, Request, or Question\n\nConanMultiPackager(use_docker=True) doesn't correctly handle build profile settings. If I set `CONAN_BASE_PROFILE_BUILD=my_build_profile`, CPT adds\n\n-e CPT_PROFILE_BUILD=\"@@include(my_build_profile)@@@@[settings]@@@@[options]@@@@[env]@@@@[build_requires]@@@@\"\n\nto Docker command line, but the build fails inside Docker because `my_build_profile` does not exist there:\n\n File \"c:\\python39\\lib\\site-packages\\conans\\client\\profile_loader.py\", line 132, in read_profile\n return _load_profile(text, profile_path, default_folder)\n File \"c:\\python39\\lib\\site-packages\\conans\\client\\profile_loader.py\", line 151, in _load_profile\n profile, included_vars = read_profile(include, cwd, default_folder)\n File \"c:\\python39\\lib\\site-packages\\conans\\client\\profile_loader.py\", line 119, in read_profile\n profile_path = get_profile_path(profile_name, default_folder, cwd)\n File \"c:\\python39\\lib\\site-packages\\conans\\client\\profile_loader.py\", line 107, in get_profile_path\n raise ConanException(\"Profile not found: %s\" % profile_name)\nconans.errors.ConanException: Profile not found: my_build_profile\n\nAnother problem is that in the absence of CONAN_BASE_PROFILE_BUILD CPT passes empty settings for the build profile:\n\n-e CPT_PROFILE=\"@@include(default)@@@@[settings]@@arch=x86_64@@build_type=Release@@compiler=Visual Studio@@compiler.runtime=MD@@compiler.version=15@@os=Windows@@[options]@@@@[env]@@@@[build_requires]@@@@\"\n-e CPT_PROFILE_BUILD=\"@@include(default)@@@@[settings]@@@@[options]@@@@[env]@@@@[build_requires]@@@@\"\n\nThat breaks my build that worked before with CPT 0.35.0. Why not pass the same settings in CPT_PROFILE_BUILD as in CPT_PROFILE if CONAN_BASE_PROFILE_BUILD is not set?\n\n### Environment Details\n* Conan Package Tools Version: **0.37.0**\n* Conan version: **conan 1.43.0**","reference_answer":"@jmarrec have you already tried asking in m4 mail list, as it was discussed in #7369? it seems like there is no configure option to bypass the check, and proper fix may require to patch m4 sources.","answer_document_id":"gh_comment_1016462518","silver_evidence_path":["gh_comment_1015389623","gh_issue_1103697906","gh_comment_1016462518"],"known_context_document_ids":["gh_issue_1082247057"],"evidence_issue_ids":[1082247057,1103697906],"source_repo_name":"conan-io/conan-package-tools","source_issue_id":1082247057,"source_issue_url":"https://github.com/conan-io/conan-package-tools/issues/595","target_repo_name":"conan-io/conan-center-index","target_issue_id":1103697906,"target_issue_url":"https://github.com/conan-io/conan-center-index/issues/8920","split":"dev","quality_score":85.78,"annotation_level":"silver"}
{"query_id":"cross_issue_0277","query":"[DOC] Provide guideline to setup an 'air-gapped' repository and how to enable Harvester UI extension in Rancher v2.10.x?","query_context":"**Is your doc request related to a problem? Please describe or add the related issue ID.**\nStarting from Rancher v2.10.0, we introduce the Harvester UI extension on Rancher.\n\n* Currently we provide the automatic install UI extension under regular network environment. \n\n* It extremely important we need to consider the use case of `air-gapped` environment since still many user and customer required this feature.\n\n* Thus we need to provide the guideline steps for how to properly setup an `air-gapped` local repository for user in their own environment. \n\n**Describe the solution you'd like**\n \n\nThe document could include these content\n\n1. Steps for to setup an air-ggaped repository \n2. Steps to add airgapped UI extension repository in Rancher\n3. Whether it support automatic install or always require to manually install the extension\n4. Anything we need to consider when upgrade Rancher from v2.10.x before. \n\n**Additional context**\n \n* For the air-ggaped repository setup, we can refer and extend from the test issue.\n - URL","reference_answer":"Now I'm using vagrant to setup rancher, and follow the steps in URL to install harvester-ui-extenstion, but I'm still encountering the same installation failed issue, though I can use the workaround mentioned in URL to mitigate the installation failed issue. I'm wondering is this expected? Or should we consider it as a bug? c.c @khushboo-rancher, @noahgildersleeve.\n\nNote: the endpoint in harvester UIPlugin seems wrong, and should be ` URL instead.","answer_document_id":"gh_comment_2739170632","silver_evidence_path":["gh_comment_2585377698","gh_issue_2782073730","gh_comment_2739170632"],"known_context_document_ids":["gh_issue_2759216263"],"evidence_issue_ids":[2759216263,2782073730],"source_repo_name":"harvester/harvester","source_issue_id":2759216263,"source_issue_url":"https://github.com/harvester/harvester/issues/7258","target_repo_name":"harvester/harvester","target_issue_id":2782073730,"target_issue_url":"https://github.com/harvester/harvester/issues/7353","split":"dev","quality_score":92.79,"annotation_level":"silver"}
{"query_id":"cross_issue_0283","query":"When attempting to set a wallpaper i recieve a segmentation fault. run with sudo the same.","query_context":"[luke@fedora build]$ ./wallengine /home/luke/.local/share/Steam/steamapps/workshop/content/431960/2677437153/\nDetected scene.pkg file at /home/luke/.local/share/Steam/steamapps/workshop/content/431960/2677437153/scene.pkg. Adding to list of searchable paths\nFound wallpaper engine's assets at /home/luke/.local/share/Steam/steamapps/common/wallpaper_engine/assets\nSegmentation fault (core dumped)\n[luke@fedora build]$ \n\nfixed location of program and retested still having the issue.","reference_answer":"wp::video::node is the base class for all the different types of nodes the scene can have. right now only the materials are implemented, so if your scene uses models, web-browser or video the content won't be displayed (in fact you should be seeing an error in the log).\n\nAs I haven't implemented the Wallpaper engine texture format yet only PNG/JPG textures are supported. #1 \nRight now this is as far as you can get with any background: URL \nThis is the background I'm loading in that picture: URL \n\nYou'll notice that for every material, there is a png or jpg file with the actual texture.\n\nShaders support is implemented but they aren't loaded yet from the project.json file as I still have to implement the parser for them.","answer_document_id":"gh_comment_475576330","silver_evidence_path":["gh_comment_1120475633","gh_issue_424094176","gh_comment_475576330"],"known_context_document_ids":["gh_issue_1216605480"],"evidence_issue_ids":[1216605480,424094176],"source_repo_name":"Almamu/linux-wallpaperengine","source_issue_id":1216605480,"source_issue_url":"https://github.com/Almamu/linux-wallpaperengine/issues/89","target_repo_name":"Almamu/linux-wallpaperengine","target_issue_id":424094176,"target_issue_url":"https://github.com/Almamu/linux-wallpaperengine/issues/2","split":"dev","quality_score":94.83,"annotation_level":"silver"}
{"query_id":"cross_issue_0286","query":"Update release GitHub workflows?","query_context":"I think the release workflows could be simplified.\n\n* Use a single machine to publish everything - `macos-latest` can build all Kotlin targets.\n* Just trigger `./gradlew publish` instead of listing all of the publish tasks separately. \n\nIn URL I introduced a BuildService with limited concurrency to try to avoid issues with Maven Central and parallel uploads. If it doesn't work, then the quickest and easiest fix is to add the flags `--no-configuration-cache org.gradle.parallel=false -Dorg.gradle.workers.max=1`.\n\nWe could also look into creating a staging repository before releasing - then Maven Central won't get confused about parallel uploads.","reference_answer":"`maven-publish` itself supports cc since 7.6 and the `signing` plugin will in Gradle 8.1. However there is one big open blocker when publishing to maven central URL When configuration cache is enabled the repository url will be evaluated eagerly and not when the publishing tasks are executed. Since we are computing that url based on the output of the task that creates the staging repo the build will fail with this:\n\nConfiguration cache state could not be cached: field `repository` of `org.gradle.api.publish.maven.tasks.PublishToMavenRepository$PublishSpec` bean found in field `value` of `org.gradle.internal.Try$Success` bean found in field `result` of `org.gradle.internal.serialization.Cached$Fixed` bean found in field `spec` of task `:nexus:publishMavenPublicationToMavenCentralRepository` of type `org.gradle.api.publish.maven.tasks.PublishToMavenRepository`: error writing value of type 'org.gradle.api.publish.maven.tasks.PublishToMavenRepository$RepositorySpec$Configured'\n \n The value of this provider is derived from:\n - task ':nexus:createStagingRepository' property 'stagingRepositoryId'\n\nSo current status: \n- Gradle 7.6: publishing to local or non maven central remote repositories works with cc when signing is disabled\n- Gradle 8.1: publishing to local or non maven central remote repositories works with cc with signing enabled\n- TBD: publishing to maven central works with cc","answer_document_id":"gh_comment_1367968935","silver_evidence_path":["gh_comment_2152038495","gh_issue_897637877","gh_comment_1367968935"],"known_context_document_ids":["gh_issue_2337738681"],"evidence_issue_ids":[2337738681,897637877],"source_repo_name":"kotest/kotest","source_issue_id":2337738681,"source_issue_url":"https://github.com/kotest/kotest/issues/4067","target_repo_name":"vanniktech/gradle-maven-publish-plugin","target_issue_id":897637877,"target_issue_url":"https://github.com/vanniktech/gradle-maven-publish-plugin/issues/259","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0316","query":"Step not saved (clash with precision?) (was: Add step editing (was: Slider min/max/step editing))?","query_context":"This is step 2 from URL \n\nAdd the ability to edit the start/stop/round attributes of a slider (triple-click or shift-click, probably, popping up a dialog). This will be saved to a shared table, with options:\n\n- just apply to this slider\n- apply to all [cfg] sliders on [KSampler] nodes\n- apply to all [cfg] sliders on any node\n\nAt this point the old mechanism will be retired (maybe auto converted, maybe not!)","reference_answer":"Yup. There is a weird interplay between precision, round, and step. I think I've got it working...","answer_document_id":"gh_comment_2430431842","silver_evidence_path":["gh_comment_2430463263","gh_issue_2603989066","gh_comment_2430431842"],"known_context_document_ids":["gh_issue_2574697599"],"evidence_issue_ids":[2574697599,2603989066],"source_repo_name":"chrisgoringe/cg-controller","source_issue_id":2574697599,"source_issue_url":"https://github.com/chrisgoringe/cg-controller/issues/61","target_repo_name":"chrisgoringe/cg-controller","target_issue_id":2603989066,"target_issue_url":"https://github.com/chrisgoringe/cg-controller/issues/181","split":"dev","quality_score":83.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0321","query":"Syntax issue using PREFERRED PARAMETER?","query_context":"Hello,\n\nI have syntax errors in my abaplint result set, that a importing parameter IV_STRING is not given into the method.\nSyntax_error_prefered_parameter_1\n\nThe importing parameter IV_STRING is definied as prefered parameter.\nSyntax_error_prefered_parameter_3\n\nAccording to SAP help this option \"prefered parameter\" says, that parameter is implicitly set to optional.\nSyntax_error_prefered_parameter_2\n\nTherefore abaplint should not return an error in that case. SAP himself is not raising issues.\n\nThanks.\n\nBest regards,\nDominik","reference_answer":"if you change the code to use functional writing, I think it should work, as a workaround.... URL","answer_document_id":"gh_comment_1385631950","silver_evidence_path":["gh_comment_1379348978","gh_issue_1519036695","gh_comment_1385631950"],"known_context_document_ids":["gh_issue_1528811973"],"evidence_issue_ids":[1528811973,1519036695],"source_repo_name":"abaplint/abaplint","source_issue_id":1528811973,"source_issue_url":"https://github.com/abaplint/abaplint/issues/2841","target_repo_name":"abaplint/abaplint","target_issue_id":1519036695,"target_issue_url":"https://github.com/abaplint/abaplint/issues/2826","split":"dev","quality_score":91.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0323","query":"App not opening on Windows 11?","query_context":"I downloaded the app from both the Microsoft store, as well as the manual .zip installation. It is not opening from either place. My cursor shows the blue circle loading icon for about half a second and then nothing happens. I am not able to replicate this issue on any Windows 10 machines.","reference_answer":"So assuming that's fixed, I believe the original issue this thread is based on is a problem with the 2022 version that is not present in the main branch. Here's a pre-release build of the main branch for anyone else finding this issue later: \npathplanner-windows.zip\n\nI'll close this after the 2023 version is released.","answer_document_id":"gh_comment_1283239772","silver_evidence_path":["gh_comment_1301466008","gh_issue_1392899383","gh_comment_1283239772"],"known_context_document_ids":["gh_issue_1433886944"],"evidence_issue_ids":[1433886944,1392899383],"source_repo_name":"mjansen4857/pathplanner","source_issue_id":1433886944,"source_issue_url":"https://github.com/mjansen4857/pathplanner/issues/141","target_repo_name":"mjansen4857/pathplanner","target_issue_id":1392899383,"target_issue_url":"https://github.com/mjansen4857/pathplanner/issues/117","split":"dev","quality_score":87.35,"annotation_level":"silver"}
{"query_id":"cross_issue_0328","query":"Access to AWS to test gdalcubes in large collections?","query_context":"Dear Marius:\n\nDo you have access to AWS to test gdalcubes? We had problems when regularizing large image collections. The problems are not simple to reproduce, because they occur when trying to run `gdalcubes` on big data.","reference_answer":"This might be caused by the GDAL error handler defined by the `sf` package. The GDAL error handler (set with \n`CPLSetErrorHandler`) might be called from threads created by gdalcubes but the error handler calls `Rf_warning()` (see URL which is not thread-safe. However, a single-thread test, where all computations run in the main thread should clarify further.","answer_document_id":"gh_comment_1030926650","silver_evidence_path":["gh_comment_1049101611","gh_issue_1042460965","gh_comment_1030926650"],"known_context_document_ids":["gh_issue_1148414934"],"evidence_issue_ids":[1148414934,1042460965],"source_repo_name":"appelmar/gdalcubes_R","source_issue_id":1148414934,"source_issue_url":"https://github.com/appelmar/gdalcubes_R/issues/55","target_repo_name":"appelmar/gdalcubes_R","target_issue_id":1042460965,"target_issue_url":"https://github.com/appelmar/gdalcubes_R/issues/48","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0331","query":"Consider pushing out a new release?","query_context":"### Steps to reproduce\n\n \n\n \n\nrails new demo\ncd demo\nDOCKER_BUILDKIT=1 docker build .\n\n### Expected behavior\n\nBuild succeeds.\n\n### Actual behavior\n\nFails with Ruby 3.4.2 (obtained via brew)\n\n10.42 Gem::Ext::BuildError: ERROR: Failed to build gem native extension.\n10.42 \n10.42 current directory: /usr/local/bundle/ruby/3.4.0/gems/psych-5.2.3/ext/psych\n10.42 /usr/local/bin/ruby extconf.rb\n10.42 checking for pkg-config for yaml-0.1... not found\n10.42 checking for yaml.h... no\n10.42 yaml.h not found\n10.42 *** extconf.rb failed ***\n\n### System configuration\n\n**Rails version**: `Rails 8.0.1`\n\n**Ruby version**: `ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [arm64-darwin24]`\n\n### See also\n\n URL","reference_answer":"Similar report just came in #435, too.\n\nI believe something changed in the alpine image, since we test alpine in the CI pipeline and it passed last week, but started failing yesterday with the new image\n\n- pass URL \n- fail URL \n\nWill investigate. In the meantime, a workaround is to use `ruby:3-alpine3.18`","answer_document_id":"gh_comment_1852044793","silver_evidence_path":["gh_comment_2751441316","gh_issue_2037156404","gh_comment_1852044793"],"known_context_document_ids":["gh_issue_2869092863"],"evidence_issue_ids":[2869092863,2037156404],"source_repo_name":"rails/rails","source_issue_id":2869092863,"source_issue_url":"https://github.com/rails/rails/issues/54588","target_repo_name":"sparklemotion/sqlite3-ruby","target_issue_id":2037156404,"target_issue_url":"https://github.com/sparklemotion/sqlite3-ruby/issues/434","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0334","query":"'quarto publish gh-pages' does not respect output-dir?","query_context":"### Bug description\n\nQuarto docs specify to set `output-dir: docs` for gh-pages: URL -- and set `docs/` as the target directory in the Github Pages config.\n\nHowever, running `quarto publish gh-pages` appears to ignore the `output-dir` setting.\n- input: URL \n- `gh-pages` after running `quarto publish gh-pages` locally (successfully): URL \n\nThis means I need to set the Github Pages config to use ` ` instead of `docs/`.\n\nRunning `quarto render` locally puts the output in `docs/` as expected.\n\n---\n\n- macOS 12.4\n\n- quarto version:\n\nbase ❯ quarto check\n\n \n\n[✓] Checking Quarto installation......OK\n Version: 0.9.629\n Path: /Applications/quarto/bin\n\n[✓] Checking basic markdown render....OK\n\n[✓] Checking Python 3 installation....OK\n Version: 3.9.13 (Conda)\n Path: /Users/inorton/opt/conda/bin/python\n Jupyter: (None)\n\n Jupyter is not available in this Python installation.\n Install with conda install jupyter\n\n[✓] Checking R installation...........OK\n Version: 4.1.0\n Path: /Library/Frameworks/R.framework/Resources\n LibPaths:\n - /Users/inorton/Library/R/x86_64/4.1/library\n - /Library/Frameworks/R.framework/Versions/4.1/Resources/library\n rmarkdown: 2.9\n\n[✓] Checking Knitr engine render......OK\n\n \n\n### Checklist\n\n- [X] formatted your issue so it is easier for us to read?\n- [X] included a minimal, self-contained, and reproducible example?\n- [X] documented the quarto version you're running, by providing the output produced by `quarto check` in a terminal in your issue?\n- [ ] documented the RStudio IDE version you're running (if applicable), by providing the value displayed in the \"About RStudio\" main menu dialog?\n- [X] documented which operating system you're running? If on Linux, please provide the specific distribution as well.\n- [ ] upgraded to the latest version, including your versions of R, the RStudio IDE, and relevant R packages?","reference_answer":"@tg-x Please open a new thread ( URL with sufficient details for your request after double checking it's not something already possible, if there are alternatives. Thank you!\nNote that `quarto publish` is not intended to cover all possible use cases, *i.e.*, you can can use `quarto render` and then take control of the publishing part to do whatever you need to do.\nGitHub Pages does not care about branches other than `gh-pages`, so adding a parameter to publish to GitHub Pages on another branch does not make sense.","answer_document_id":"gh_comment_1965479875","silver_evidence_path":["gh_comment_1965481746","gh_issue_1325867468","gh_comment_1965479875"],"known_context_document_ids":["gh_issue_1288930178"],"evidence_issue_ids":[1288930178,1325867468],"source_repo_name":"quarto-dev/quarto-cli","source_issue_id":1288930178,"source_issue_url":"https://github.com/quarto-dev/quarto-cli/issues/1246","target_repo_name":"quarto-dev/quarto-cli","target_issue_id":1325867468,"target_issue_url":"https://github.com/quarto-dev/quarto-cli/issues/1640","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0335","query":"[2.5] Audio delay on fresh install when running three parallel Kurento media servers?","query_context":"I was installing BBB 2.5 on a new server and dealing with high audio delay (**audio and video where totally out of sync**).\nI had copied `/etc/bigbluebutton/bbb-conf/apply-config.sh` file from the old server to the new one, without much changing it. There was called the function `enableMultipleKurentos` in it, based on here to run three parallel KMS. \n\nI reinstalled it again and noticed that using `enableMultipleKurentos` function in `apply-config.sh` file may be causing this problem. \nadding `disableMultipleKurentos` didn't solve the problem. So I ended up removing all files and installing again, without adding that function into apply-config fie. And it's solved now. \n\nP.S. I'm not sure if it's been cause of the problem! I just decided to report it here, for more investigations. \nSince I'm not currently able to reproduce it on another server.\n \n**To Reproduce**\nSteps to reproduce the behavior:\n1. fresh installation of BBB 2.5\n2. add `enableMultipleKurentos` to file `/etc/bigbluebutton/bbb-conf/apply-config.sh`\n3. Run `sudo bbb-conf --restart`\n4. Turn on audio and camera\n5. Check on another device to see if it has any delay or not\n\nVersion: **BigBlueButton Server 2.5.1 (3020)**","reference_answer":"@mokazemi Would you be able to do some more testing on your end to see if the audio is out of sync before you make either of those two changes (server time or `60:120:20`, then make one of the changes, and test again. \n\nWe would be very interested if you can do a specific before/after comparison of making only those these changes.","answer_document_id":"gh_comment_1251430382","silver_evidence_path":["gh_comment_1254180701","gh_issue_1362382618","gh_comment_1251430382"],"known_context_document_ids":["gh_issue_1269320628"],"evidence_issue_ids":[1269320628,1362382618],"source_repo_name":"bigbluebutton/bigbluebutton","source_issue_id":1269320628,"source_issue_url":"https://github.com/bigbluebutton/bigbluebutton/issues/15172","target_repo_name":"bigbluebutton/bigbluebutton","target_issue_id":1362382618,"target_issue_url":"https://github.com/bigbluebutton/bigbluebutton/issues/15644","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0336","query":"[Bug/Support]: \"End of file during parsing\" error: how to see whole log, including commands?","query_context":"### Confirmation\n\n- [X] I have checked the documentation (README, Wiki, docstrings, etc)\n- [ ] I am checking these without reading them.\n- [X] I have searched previous issues to see if my question is a duplicate.\n\n### Elpaca Version\n\nElpaca 43ec2d8 grafted, HEAD -> master, origin/master, origin/HEAD\ninstaller: 0.7\nemacs-version: GNU Emacs 30.0.50 (build 1, x86_64-w64-mingw32)\n of 2024-04-08\ngit --version: git version 2.44.0.windows.1\n\n### Operating System\n\nWindows 11\n\n### Description\n\nI'm getting errors building a few packages. Not sure how to track them down because the log doesn't have the actual subprocess command executed to build:\n\nvertico [MELPA|GNU-devel ELPA]\nVERTical Interactive COmpletion\n\nsource: MELPA\nurl: URL \nmenu item recipe:\n( :package \"vertico\"\n :repo \"minad/vertico\"\n :files (:defaults \"extensions/vertico-*.el\")\n :fetcher github\n :source \"MELPA\")\nfull recipe:\n( :package \"vertico\" \n ;; Inherited from declaration.\n :files (:defaults \"extensions/*\")\n ;; Inherited from elpaca-order-functions.\n :depth 1\n :inherit t\n :protocol https\n ;; Inherited from elpaca-menu-item.\n :source \"MELPA\"\n :fetcher github\n :repo \"minad/vertico\")\ndependencies: \n emacs >= 27.1\n compat >= 29.1.4.4\ndependents: nil\ninstalled version: 1.8 1def56a\nstatuses:\n (failed autoloads linking unblocked ref-checked-out unthrottled blocked queue-throttled unthrottled blocked queue-throttled queued)\nfiles:\n $REPOS/vertico/extensions/vertico-buffer.el → $BUILDS/vertico/vertico-buffer.el\n $REPOS/vertico/extensions/vertico-directory.el → $BUILDS/vertico/vertico-directory.el\n $REPOS/vertico/extensions/vertico-flat.el → $BUILDS/vertico/vertico-flat.el\n $REPOS/vertico/extensions/vertico-grid.el → $BUILDS/vertico/vertico-grid.el\n $REPOS/vertico/extensions/vertico-indexed.el → $BUILDS/vertico/vertico-indexed.el\n $REPOS/vertico/extensions/vertico-mouse.el → $BUILDS/vertico/vertico-mouse.el\n $REPOS/vertico/extensions/vertico-multiform.el → $BUILDS/vertico/vertico-multiform.el\n $REPOS/vertico/extensions/vertico-quick.el → $BUILDS/vertico/vertico-quick.el\n $REPOS/vertico/extensions/vertico-repeat.el → $BUILDS/vertico/vertico-repeat.el\n $REPOS/vertico/extensions/vertico-reverse.el → $BUILDS/vertico/vertico-reverse.el\n $REPOS/vertico/extensions/vertico-suspend.el → $BUILDS/vertico/vertico-suspend.el\n $REPOS/vertico/extensions/vertico-unobtrusive.el → $BUILDS/vertico/vertico-unobtrusive.el\n $REPOS/vertico/vertico.el → $BUILDS/vertico/vertico.el\nlog:\n [2024-05-02 09:33:03] Package queued\n [2024-05-02 09:33:03] Continued by: elpaca--process\n [2024-05-02 09:33:03] elpaca-queue-limit exceeded\n [2024-05-02 09:33:03] Continued by: elpaca--finalize\n [2024-05-02 09:33:03] elpaca-queue-limit exceeded\n [2024-05-02 09:33:04] Continued by: elpaca--finalize\n [2024-05-02 09:33:04] Continued by: elpaca--configure-remotes\n [2024-05-02 09:33:04] Continued by: elpaca--checkout-ref\n [2024-05-02 09:33:04] Continued by: elpaca--dispatch-build-commands\n [2024-05-02 09:33:04] Continued by: elpaca--queue-dependencies\n [2024-05-02 09:33:04] No external dependencies\n [2024-05-02 09:33:04] Checking dependency versions\n [2024-05-02 09:33:04] Continued by: elpaca--check-version\n [2024-05-02 09:33:04] Linking build files\n [2024-05-02 09:33:04] Continued by: elpaca--link-build-files\n [2024-05-02 09:33:04] Build files linked\n [2024-05-02 09:33:04] Generating autoloads: c:/Users/garyo/AppData/Roaming/.config/emacs/elpaca/builds/vertico\n [2024-05-02 09:33:04] End of file during parsing\n [2024-05-02 09:33:04] Subprocess error (see previous log entries)\n\nI set `elpaca-verbosity` to 100 but don't see anything more in that log.","reference_answer":"Thanks for taking the time to fill out a support ticket. \n \n \n \n \n \n \n \n \n \n \n\nYes. That does look like a circular dependency.\nI've squashed that bug several times, so perhaps there's a case I missed.\n \n \n\nMaybe they're related.\nYou can prevent the \"too many open file\" error by setting the `elpaca-queue-limit` option prior to processing any queues. e.g.\n\n emacs-lisp\n(setq elpaca-queue-limit 30)\n\nIf you search the issue tracker there are other Windows users who have hit this limit.\nI don't recall exactly where they ended up with that value, but I think it was closer to 12-20. Allegedly there are ways to allow more open file handles at the OS level, but I don't use Windows enough to give any advice on how to do it.\n\nI would try:\n\n1. saving `(setq elpaca-queue-limit 12)` in you init file just after the elpaca installer.\n2. `M-x restart-emacs`\n\nThen, in a fresh Emacs session, try another `elpaca-update-all` and see if the issue persists.","answer_document_id":"gh_comment_2090642074","silver_evidence_path":["gh_comment_2100897793","gh_issue_2275508432","gh_comment_2090642074"],"known_context_document_ids":["gh_issue_2275583763"],"evidence_issue_ids":[2275583763,2275508432],"source_repo_name":"progfolio/elpaca","source_issue_id":2275583763,"source_issue_url":"https://github.com/progfolio/elpaca/issues/303","target_repo_name":"progfolio/elpaca","target_issue_id":2275508432,"target_issue_url":"https://github.com/progfolio/elpaca/issues/302","split":"dev","quality_score":89.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0338","query":"Evaluate data quality when saving and loading feather and parquet files?","query_context":"Evaluate add difference in resulting loaded dataframe when using to read_csv and to_csv versus comparable feather and parquet functions:\n\n- URL \n- URL \n- URL \n- URL \n\nThis can be tested with these CSV files: \n\n- URL \n- URL \n- URL \n-","reference_answer":"#332 was accepted and closed with a caveat. Please see final comment with implementation notes and testing instructions.","answer_document_id":"gh_comment_2905988271","silver_evidence_path":["gh_comment_2905987388","gh_issue_3054482249","gh_comment_2905988271"],"known_context_document_ids":["gh_issue_3054485107"],"evidence_issue_ids":[3054485107,3054482249],"source_repo_name":"openpolicedata/openpolicedata","source_issue_id":3054485107,"source_issue_url":"https://github.com/openpolicedata/openpolicedata/issues/332","target_repo_name":"openpolicedata/openpolicedata","target_issue_id":3054482249,"target_issue_url":"https://github.com/openpolicedata/openpolicedata/issues/330","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0341","query":"dart_plugin_registrant.dart + AOT + --obfuscation?","query_context":"### Is there an existing issue for this?\n\n- [X] I have searched the existing issues\n- [X] I have read the guide to filing a bug\n\n### Steps to reproduce\n\nManually build AOT components where you can control use of the --obfuscate flag.\n\nBuild sequences:\n URL \n URL \n\n### Expected results\n\ncorrectly register plugins regardless of obfuscate flag\n\n### Actual results\n\nwithout passing --obfuscate to `gen_snapshot`:\n* Flutter Package examples - correctly register plugins\n* Gallery - does not register plugins\n* Wonderous - does not register plugins\n\npassing --obfuscate to `gen_snapshot`:\n* Flutter Package examples - correctly register plugins\n* Gallery - correctly register plugins\n* Wonderous - correctly register plugins\n\nDumping symbols from AOT in both cases using readelf, the expected entry points are present:\n\nworking\n\n 11673: 000000000059914c 116 FUNC LOCAL DEFAULT 7 _PluginRegistrant.register\n 11674: 00000000005991c0 44 FUNC LOCAL DEFAULT 7 _PluginRegistrant.register\n 11675: 00000000005991ec 8 FUNC LOCAL DEFAULT 7 dartPluginRegistrantLibrary\n 11676: 00000000005991f4 8 FUNC LOCAL DEFAULT 7 dartPluginRegistrantLibrary\n 11677: 00000000005991fc 48 FUNC LOCAL DEFAULT 7 main\n\nnot working\n\n131825: 0000000001e991e0 8 FUNC LOCAL DEFAULT 7 dartPluginRegistrantLibrary\n131826: 0000000001e991e8 8 FUNC LOCAL DEFAULT 7 dartPluginRegistrantLibrary\n131827: 0000000001e991f0 320 FUNC LOCAL DEFAULT 7 _PluginRegistrant.register\n131828: 0000000001e99330 44 FUNC LOCAL DEFAULT 7 _PluginRegistrant.register\n131829: 0000000001e9935c 96 FUNC LOCAL DEFAULT 7 main\n131830: 0000000001e993bc 44 FUNC LOCAL DEFAULT 7 main\n\n### Code sample\n\nNA\n\n### Screenshots or Video\n\nNA\n\n### Logs\n\nNA\n\n### Flutter Doctor output\n\n Doctor output \n\nconsole\n[!] Flutter (Channel [user-branch], 3.13.9, on Fedora Linux 38 (Workstation Edition) 6.5.8-200.fc38.x86_64, locale en_US.UTF-8)\n ! Flutter version 3.13.9 on channel [user-branch] at /mnt/raid10/workspace-automation/flutter\n Currently on an unknown channel. Run `flutter channel` to switch to an official channel.\n If that doesn't fix the issue, reinstall Flutter by following instructions at URL \n ! Upstream repository unknown source is not a standard remote.\n Set environment variable \"FLUTTER_GIT_URL\" to unknown source to dismiss this error.\n • Framework revision d211f42860 (12 days ago), 2023-10-25 13:42:25 -0700\n • Engine revision 0545f8705d\n • Dart version 3.1.5\n • DevTools version 2.25.0\n • If those were intentional, you can disregard the above warnings; however it is recommended to use \"git\" directly to perform update checks and upgrades.\n\n[✓] Linux toolchain - develop for Linux desktop\n • clang version 16.0.6 (Fedora 16.0.6-3.fc38)\n • cmake version 3.27.7\n • ninja version 1.11.1\n • pkg-config version 1.8.0\n\n[✓] VS Code (version 1.84.1)\n • VS Code at /usr/share/code\n • Flutter extension version 3.76.0\n\n[✓] Connected device (2 available)\n • Linux (desktop) • linux • linux-x64 • Fedora Linux 38 (Workstation Edition) 6.5.8-200.fc38.x86_64\n • Toyota homescreen (mobile) • desktop-homescreen • linux-x64 • homescreen x86_64\n\n[✓] Network resources\n • All expected network resources are available.\n\n! Doctor found issues in 1 category.\nList of custom devices in \"/mnt/raid10/workspace-automation/.config/flutter/custom_devices.json\":\n id: desktop-homescreen, label: Toyota homescreen, enabled: true\n[joel@air workspace-automation]$ flutter doctor\nDoctor summary (to see all details, run flutter doctor -v):\n[!] Flutter (Channel [user-branch], 3.13.9, on Fedora Linux 38 (Workstation Edition) 6.5.8-200.fc38.x86_64, locale en_US.UTF-8)\n ! Flutter version 3.13.9 on channel [user-branch] at /mnt/raid10/workspace-automation/flutter\n Currently on an unknown channel. Run `flutter channel` to switch to an official channel.\n If that doesn't fix the issue, reinstall Flutter by following instructions at URL \n ! Upstream repository unknown source is not a standard remote.\n Set environment variable \"FLUTTER_GIT_URL\" to unknown source to dismiss this error.\n[✓] Linux toolchain - develop for Linux desktop\n[✓] VS Code (version 1.84.1)\n[✓] Connected device (2 available)\n[✓] Network resources\n\n! Doctor found issues in 1 category.","reference_answer":"@jwinarske Thanks for filing the bug. For the record, @stuartmorgan is the TL for this area of the code so he's the one who should make the final call on this.\n\nIt sounds like there's an ambiguity in your request. We support several Linux-based platforms, for example Android and GTK. Plugins for different platforms are quite different (for example, plugins on Android are typically in Java, whereas on GTK they are in C!).\n\nThe core problem, I think, is that we don't yet have extensible logic in the tool so that you can easily add new platforms. We should definitely work on that. URL is where we're tracking that issue. You can discuss this in #hackers-tool on our Discord. As a heavy user of a custom embedding, you may be interested in getting involved in this work; we haven't really started on it in earnest yet but it is an area we are very interested in.","answer_document_id":"gh_comment_1189394597","silver_evidence_path":["gh_comment_1809369517","gh_issue_1306642461","gh_comment_1189394597"],"known_context_document_ids":["gh_issue_1980262763"],"evidence_issue_ids":[1980262763,1306642461],"source_repo_name":"flutter/flutter","source_issue_id":1980262763,"source_issue_url":"https://github.com/flutter/flutter/issues/137972","target_repo_name":"flutter/flutter","target_issue_id":1306642461,"target_issue_url":"https://github.com/flutter/flutter/issues/107762","split":"dev","quality_score":95.17,"annotation_level":"silver"}
{"query_id":"cross_issue_0345","query":"General questions?","query_context":"Hi Soroosh, \n\nSorry I've got some more general questions about OCSmesh and didn't know the best way to contact you. I hope this is okay.\n\nIs there any functionality in OCSmesh to allow a review of the CFL number, to ensure the grid won't create numerical diffusion?\n\nCheers,\n\nTom","reference_answer":"@TPCollings, I was wondering if you had the chance to test the updates? If not, I can merge them to the `main` branch and you can just test it there whenever you get the chance to.","answer_document_id":"gh_comment_1265671004","silver_evidence_path":["gh_comment_1252918981","gh_issue_1366594020","gh_comment_1265671004"],"known_context_document_ids":["gh_issue_1364463217"],"evidence_issue_ids":[1364463217,1366594020],"source_repo_name":"noaa-ocs-modeling/OCSMesh","source_issue_id":1364463217,"source_issue_url":"https://github.com/noaa-ocs-modeling/OCSMesh/issues/24","target_repo_name":"noaa-ocs-modeling/OCSMesh","target_issue_id":1366594020,"target_issue_url":"https://github.com/noaa-ocs-modeling/OCSMesh/issues/25","split":"dev","quality_score":83.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0347","query":"[Critical] Attackers may craft invalid domain bundle/execution receipt with excessive fraud proof size, making it impossible to submit a fraud proof on consensus chain?","query_context":"# Issue description\n\nWhen a bundle/execution receipt with an invalid execution result is constructed, someone will have to generate a fraud proof for it and submit it by dispatching a `submit_fraud_proof` call on the consensus chain. For the case of an invalid extrinsic execution result, the fraud proof will be of type `InvalidStateTransitionProof` and this fraud proof will contain one or two storage proofs (`InvalidStateTransitionProof.proof` and `InvalidStateTransitionProof.execution_phase.ApplyExtrinsic.extrinsic_proof`).\n\nIf the failing extrinsic is doing a lot of storage access, this will lead to large storage proofs, possibly to an extent where the fraud proof exceeds the consensus chain `MAX_BLOCK_LENGTH = 5 MiB`. If this is the case, honest domain operators may know that the block is invalid but they can never successfully dispatch a `submit_fraud_proof` for it.\n\nIn order to limit the amount of storage changes, the 2D weight system should be used with an appropriate limit for the `proof_size` weight in order to ensure that it is always possible to submit a fraud proof when needed. As of now the `MAXIMUM_BLOCK_WEIGHT` is configured to `Weight::from_parts(u64::MAX, u64::MAX)`, so there is effectively no limit at all.\n\n# Risk\n\nIf an invalid bundle/execution receipt cannot be discarded via a fraud proof due to this, it will eventually be considered final. If the storage root after executing the invalid bundle contains outgoing transfer messages minting SSC out of thin air, these transfers will be accepted by the consensus chain or sibling domains, effectively allowing an attacker to mint arbitrary amounts of SSC.\n\n# Mitigation suggestion\n\nUse an appropriate limit for the `proof_size` weight (with some safety margin to the consensus chain block length) to ensure that it is always possible to submit a fraud proof for an invalid bundle. Extra care needs to be taken to ensure that no calls can lead to a proof size larger than the predicted value from the weight calculation since this may directly lead to a situation where an invalid execution receipt is accepted since nobody can submit a fraud proof for it.","reference_answer":"There's also #2365. Can we have bundle limit in domain config instead of block limit? Especially since domain block limit is not enforced.\nSo in domain config we would have `target_bundles_per_slot` (1 or less, or more) and `max_bundle_weight`. Then the average domain block weight would be `target_bundles_per_slot * max_bundle_weight/SLOT_PROBABILITY` and each domain should have hardware requirements to be able to achieve that.","answer_document_id":"gh_comment_2023964506","silver_evidence_path":["gh_comment_2135123497","gh_issue_2065778987","gh_comment_2023964506"],"known_context_document_ids":["gh_issue_2088725488"],"evidence_issue_ids":[2088725488,2065778987],"source_repo_name":"autonomys/subspace","source_issue_id":2088725488,"source_issue_url":"https://github.com/autonomys/subspace/issues/2425","target_repo_name":"subspace/subspace","target_issue_id":2065778987,"target_issue_url":"https://github.com/subspace/subspace/issues/2387","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0356","query":"some warnning happened when i run manipulation.ipynb?","query_context":"/home/ubuntu/miniconda3/envs/mujoco_playground/lib/python3.10/site-packages/jax/_src/interpreters/xla.py:132: RuntimeWarning: overflow encountered in cast\n return np.asarray(x, dtypes.canonicalize_dtype(x.dtype))\n/home/ubuntu/miniconda3/envs/mujoco_playground/lib/python3.10/site-packages/jax/_src/interpreters/xla.py:132: RuntimeWarning: overflow encountered in cast\n return np.asarray(x, dtypes.canonicalize_dtype(x.dtype))\n/home/ubuntu/miniconda3/envs/mujoco_playground/lib/python3.10/site-packages/jax/_src/interpreters/xla.py:132: RuntimeWarning: overflow encountered in cast\n return np.asarray(x, dtypes.canonicalize_dtype(x.dtype))\n2025-01-16 18:44:38.791223: E external/xla/xla/service/slow_operation_alarm.cc:73] \n********************************\n[Compiling module jit_generate_eval_unroll] Very slow compile? If you want to file a bug, run with envvar XLA_FLAGS=--xla_dump_to=/tmp/foo and attach the results.","reference_answer":"Closing, as it looks like this issue has been resolved. Please re-open if this is not the case. Thanks!","answer_document_id":"gh_comment_2784628622","silver_evidence_path":["gh_comment_2787856493","gh_issue_2816754787","gh_comment_2784628622"],"known_context_document_ids":["gh_issue_2792373426"],"evidence_issue_ids":[2792373426,2816754787],"source_repo_name":"google-deepmind/mujoco_playground","source_issue_id":2792373426,"source_issue_url":"https://github.com/google-deepmind/mujoco_playground/issues/11","target_repo_name":"jax-ml/jax","target_issue_id":2816754787,"target_issue_url":"https://github.com/jax-ml/jax/issues/26162","split":"dev","quality_score":91.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0359","query":"Name of project/tool?","query_context":"- [x] 1. Name the service as SyBValS (**Sy**stems **B**iology **Val**idation **S**ervice) everywhere in the sample application, including the About dialog\n- [x] 2. Name this repository as \"sybvals\"\n- [x] 3. Write a README introducing the service (use a format similar to this)","reference_answer":"@ugurdogrusoz item 6 ( test.sbgn) is now working. Reason of error is that test.sbgn does not include mapProperties, so there is undefined errors in code, it is fixed by adding if else statement.","answer_document_id":"gh_comment_2202800112","silver_evidence_path":["gh_comment_2192924373","gh_issue_2281602434","gh_comment_2202800112"],"known_context_document_ids":["gh_issue_2207975296"],"evidence_issue_ids":[2207975296,2281602434],"source_repo_name":"iVis-at-Bilkent/sybvals","source_issue_id":2207975296,"source_issue_url":"https://github.com/iVis-at-Bilkent/sybvals/issues/1","target_repo_name":"iVis-at-Bilkent/sybvals","target_issue_id":2281602434,"target_issue_url":"https://github.com/iVis-at-Bilkent/sybvals/issues/8","split":"dev","quality_score":91.81,"annotation_level":"silver"}
{"query_id":"cross_issue_0360","query":"Version 1.10+ no longer finds checkpoints in custom install folder.","query_context":"Error: _The checkpoint used by this style is not installed_.\n\nMy ComfyUI install is a Windows portable version with custom .yaml paths. It had been working flawlessly with the plugin until 1.10/11.\nUpdating caused missing Python errors likely caused by ComfyUI's portable version Python folder being called _python embeded_, while the Krita plugin searches for _python_ instead. Although this had been working and is unrelated.\n\nNow it can only detect SDXL models and no 1.5 models. If I remove the custom checkpoint path from the .yaml file it no longer detects any checkpoints at all. Every other folder path in the .yaml (LoRAs, etc.) is detected except for checkpoints. ComfyUI itself can read the checkpoint folder.","reference_answer":"Okay, but the issue is that SD1.5 checkpoints are detected as \"stab\" for some reason.\nYou said you updated ComfyUI and custom nodes, but what are the exact versions of ComfyUI and comfyui-tooling-nodes you are using? \nI have both on latest (Comfy: a252963f956a7d76344e3f0ce24b1047480a25af, comfyui-tooling-nodes: b2496a3f132f8c3f7d452a0960c422f55c33d128) and can't reproduce this...","answer_document_id":"gh_comment_1868480483","silver_evidence_path":["gh_comment_1869147495","gh_issue_2054835489","gh_comment_1868480483"],"known_context_document_ids":["gh_issue_2055809104"],"evidence_issue_ids":[2055809104,2054835489],"source_repo_name":"Acly/krita-ai-diffusion","source_issue_id":2055809104,"source_issue_url":"https://github.com/Acly/krita-ai-diffusion/issues/276","target_repo_name":"Acly/krita-ai-diffusion","target_issue_id":2054835489,"target_issue_url":"https://github.com/Acly/krita-ai-diffusion/issues/267","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0367","query":"Improve gas estimation for create transactions?","query_context":"### Component\n\nForge\n\n### Describe the feature you would like\n\nfollowup for URL \n\n- [ ] estimate gas for `executor.deploy`\n\n### Additional context\n\n_No response_","reference_answer":"Hi all,\n\nI've tried reproducing this on Optimism, Optimism Sepolia, Arbitrum and Arbitrum Sepolia on both Anvil forks and actual deployments and am unable to reproduce it.\n\nOn Arbitrum and Arbitrum Sepolia (live) we flag it as an exception, estimate via RPC and trigger slow mode.\n\nSee: URL \n\nGiven that the issue does not occur anymore or cannot be reproduced reliably I'm marking this as `resolved`.\n\nThe existing workaround of `--with-gas-multiplier` exists if one happens to run into this issue.","answer_document_id":"gh_comment_2507303056","silver_evidence_path":["gh_comment_1504187325","gh_issue_1273968058","gh_comment_2507303056"],"known_context_document_ids":["gh_issue_1334947793"],"evidence_issue_ids":[1334947793,1273968058],"source_repo_name":"foundry-rs/foundry","source_issue_id":1334947793,"source_issue_url":"https://github.com/foundry-rs/foundry/issues/2700","target_repo_name":"foundry-rs/foundry","target_issue_id":1273968058,"target_issue_url":"https://github.com/foundry-rs/foundry/issues/2002","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0374","query":"Resetting Rewards doesn't reset Ads count?","query_context":"### Description\n\nWhile verifying the CR 134 manual pass, noticed resetting rewards doesn't reset ad count. Except for Ads data, other data is reset/wiped out. Tried few times and was able to reproduce every time. However, I could not reproduce in 1.75.x. Reproduced in 1.76.63. \n\n### Steps to reproduce\n\n1. Install 1.77.52\n2. launch Brave\n3. enabled Rewards\n4. connected uphold\n5. contributed BAT via rewards panel\n6. waited for few ads\n7. opened brave://rewards\n8. clicked ... menu\n9. clicked `Disable and reset Rewards`\n10. Rejoined Rewards\n\n### Actual result\n\nThe ads count still shown \n\n URL \n\n### Expected result\n\nAd count from before resetting rewards should not be shown\n\n### Reproduces how often\n\nEasily reproduced\n\n### Brave version (brave://version info)\n\nBrave | 1.77.52 Chromium: 134.0.6998.15 (Official Build) nightly (64-bit)\n-- | --\nRevision | d2b1e97cd8ae806f9aa05a0204a9b953536c5bce\nOS | Windows 11 Version 24H2 (Build 26100.2894)\n\n### Channel information\n\n- [ ] release (stable)\n- [x] beta\n- [x] nightly\n\n### Reproducibility\n\n- [ ] with Brave Shields disabled\n- [ ] with Brave Rewards disabled\n- [ ] in the latest version of Chrome\n\n### Miscellaneous information\n\n@Miyayes @zenparsing \ncc: @brave/qa-team","reference_answer":"Verification in progress with\n\nBrave | 1.76.74 Chromium: 134.0.6998.89 (Official Build) (x86_64)\n-- | --\nRevision | f529926c39ddc08b1e0873f4b8befdca4984b492\nOS | macOS Version 14.7.4 (Build 23H420)","answer_document_id":"gh_comment_2713949764","silver_evidence_path":["gh_comment_2713370313","gh_issue_2851121226","gh_comment_2713949764"],"known_context_document_ids":["gh_issue_2867354832"],"evidence_issue_ids":[2867354832,2851121226],"source_repo_name":"brave/brave-browser","source_issue_id":2867354832,"source_issue_url":"https://github.com/brave/brave-browser/issues/44138","target_repo_name":"brave/brave-browser","target_issue_id":2851121226,"target_issue_url":"https://github.com/brave/brave-browser/issues/43946","split":"dev","quality_score":83.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0376","query":"Question: How many threads can there be by default?","query_context":"Hi\nDoes RestAssured have a limit on the number of threads?\nIf so, how is it installed and what is the default?\n\nAlso a question about the maximum waiting time for a request to be completed.\nWhat is it like? How can I set a different value?","reference_answer":"I'm closing this for now, I've done a bit of research and running the tests and monitoring using `netstat -a` didn't show any obvious problems here.\n\nWill reopen when new information emerges or when a problem is reported by a user.","answer_document_id":"gh_comment_1882711458","silver_evidence_path":["gh_comment_1728944839","gh_issue_1872902001","gh_comment_1882711458"],"known_context_document_ids":["gh_issue_1904922028"],"evidence_issue_ids":[1904922028,1872902001],"source_repo_name":"basdijkstra/rest-assured-net","source_issue_id":1904922028,"source_issue_url":"https://github.com/basdijkstra/rest-assured-net/issues/108","target_repo_name":"basdijkstra/rest-assured-net","target_issue_id":1872902001,"target_issue_url":"https://github.com/basdijkstra/rest-assured-net/issues/107","split":"dev","quality_score":91.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0386","query":"Deploying from `x86_64-linux` to `aarch64-linux`?","query_context":"Hello,\n\nI would like to deploy updates to my Raspberry router using Deploy-rs. A work-in-progress commit has been made in my config, you can find it here.\n\nWhen I run the command: `deploy .#router` (_`router` is my raspberry machine_), it downloaded ~1.2Gb and then, I got this issue.\n\n$ deploy .#router\n🚀 ℹ [deploy] [INFO] Running checks for flake in .\nwarning: unknown flake output 'deploy'\n🚀 ℹ [deploy] [INFO] Evaluating flake in .\n🚀 ℹ [deploy] [INFO] The following profiles are going to be deployed:\n[router.system]\nuser = \"root\"\nssh_user = \"pol\"\npath = \"/nix/store/xlz3rd2dfkya33rjr1q6l1j849mh4lyw-activatable-nixos-system-router-23.11.20230607.381e92a\"\nhostname = \"router\"\nssh_opts = []\n\n🚀 ℹ [deploy] [INFO] Building profile `system` for node `router`\nerror: a 'aarch64-linux' with features {} is required to build '/nix/store/c6mljancr1wmnc0vqgwwwi8ic86krix4-builder.pl.drv', but I am a 'x86_64-linux' with features {benchmark, big-parallel, kvm, nixos-test}\n🚀 ❌ [deploy] [ERROR] Failed to push profile: Nix build command resulted in a bad exit code: Some(1)\n\nCould you please help me by telling me if the `deploy-rs` has been correctly done (based on the commit) and if you have a solution on the issue I currently have ?\n\nThanks in advance.","reference_answer":"Oh, AFAICS, build failure happens during checks build, which indeed needs target system capability for building the profile locally as a part of the check. A solution to this is to provide `--skip-checks` option","answer_document_id":"gh_comment_1590761310","silver_evidence_path":["gh_comment_1589022531","gh_issue_1669828363","gh_comment_1590761310"],"known_context_document_ids":["gh_issue_1749447893"],"evidence_issue_ids":[1749447893,1669828363],"source_repo_name":"serokell/deploy-rs","source_issue_id":1749447893,"source_issue_url":"https://github.com/serokell/deploy-rs/issues/219","target_repo_name":"serokell/deploy-rs","target_issue_id":1669828363,"target_issue_url":"https://github.com/serokell/deploy-rs/issues/200","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0402","query":"Vite CJS build warning caused by import of `unoCSSConfig` from `@tutorialkit/astro`?","query_context":"### Describe the bug\n\nWhen TutorialKit is started in development or build mode, Vite's CJS build entrypoint error is shown:\n\n$ pnpm dev\n...\nThe CJS build of Vite's Node API is deprecated. See URL for more details.\n\n### Steps to reproduce\n\nsh\n$ pnpm create tutorial\n\n$ pnpm dev\n...\nThe CJS build of Vite's Node API is deprecated. See URL for more details.\n\ndiff\n$ code uno.config.ts\n\n- import { unoCSSConfig } from '@tutorialkit/astro';\n\nexport default defineConfig({\n- ...unoCSSConfig,\n\nsh\n$ pnpm dev\n\n# No warnings\n\n### Expected behavior\n\nNo warning should be shown\n\n### Platform\n\n- TutorialKit version: 0.1.4","reference_answer":"@Barbapapazes Thanks for the pointer! This `mergeConfigs` function from `unocss` seems to be what we're looking for 👀","answer_document_id":"gh_comment_2273794340","silver_evidence_path":["gh_comment_2288811681","gh_issue_2411671343","gh_comment_2273794340"],"known_context_document_ids":["gh_issue_2465458144"],"evidence_issue_ids":[2465458144,2411671343],"source_repo_name":"stackblitz/tutorialkit","source_issue_id":2465458144,"source_issue_url":"https://github.com/stackblitz/tutorialkit/issues/244","target_repo_name":"stackblitz/tutorialkit","target_issue_id":2411671343,"target_issue_url":"https://github.com/stackblitz/tutorialkit/issues/144","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0405","query":"Update GOVERNANCE to include sub project voting?","query_context":"Outside of it being easier to find the governance of the project (e.g., I usually look for a GOVERNANCE.md file or a community repo), I'd like to ensure the voting is done in a transparent way.\n\nAs I understand it, all the governance is currently here: URL \n\nI see that it is being followed by adding maintainers, e.g., URL \n\nThere's been confusion in public how certain decisions have been made in the project which is an opportunity for clarity and growth imho: URL \n\nFor tetragon, do you have an example of where the vote happened for this? I recall that when the project was being moved to CNCF, some of the votes were happening in the Cilium Slack which isn't a best practice and we recommended recording everything on github and/or mailing list. If a vote can't be dug up, the CNCF requests that you correct things to reflect what is stated in your governance. If you need help on how to do this, look at other CNCF projects e.g., URL \n\nIf you want to use a tool that helps, we have URL in CNCF that can help with voting.","reference_answer":"Something else that I think would help with this discussion is: What do we need beyond just having a maintainer create the repo? What expectations or obligations are there that we need to satisfy for any new repo (whether freshly created due to contributions within the Cilium organization, or as a fork from an external repo for Cilium organization usage).","answer_document_id":"gh_comment_1910942150","silver_evidence_path":["gh_comment_1912274548","gh_issue_1715466325","gh_comment_1910942150"],"known_context_document_ids":["gh_issue_2102398540"],"evidence_issue_ids":[2102398540,1715466325],"source_repo_name":"cilium/community","source_issue_id":2102398540,"source_issue_url":"https://github.com/cilium/community/issues/82","target_repo_name":"cilium/community","target_issue_id":1715466325,"target_issue_url":"https://github.com/cilium/community/issues/27","split":"dev","quality_score":80.17,"annotation_level":"silver"}
{"query_id":"cross_issue_0407","query":"provide one method or api so that the upper layer can know the backup progress?","query_context":"## Is your feature request related to a problem? Please describe.\n\nCurrently myapp.exe will call rdiff-backup.exe, but did not know the progress on the backup\n\n## Describe the solution you'd like\nsimple solution is: rdiff-backup.exe write the progress info to one log file \nmyapp.exe can read the real time log from that file.\n\n## Describe alternatives you've considered\n\n## Additional context","reference_answer":"The issue is that rdiff-backup expects the target directory to it alone. A system directory like this `.WD...` directory can only create issues. Either remove it or backup to some sub- directory of W:.\n\nAt this stage, I don't see any other short term solution. Longer term would be the implementation of #790 or a new enhancement to simply ignore certain files.","answer_document_id":"gh_comment_1442394257","silver_evidence_path":["gh_comment_1442874492","gh_issue_1596171988","gh_comment_1442394257"],"known_context_document_ids":["gh_issue_1597754342"],"evidence_issue_ids":[1597754342,1596171988],"source_repo_name":"rdiff-backup/rdiff-backup","source_issue_id":1597754342,"source_issue_url":"https://github.com/rdiff-backup/rdiff-backup/issues/856","target_repo_name":"rdiff-backup/rdiff-backup","target_issue_id":1596171988,"target_issue_url":"https://github.com/rdiff-backup/rdiff-backup/issues/855","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0409","query":"[webView_flutter] screen blank on some Huawei devices with Flutter 3.29?","query_context":"### Steps to reproduce\n\n1.Create a new Flutter project with WebView:\nflutter create webview_test\ncd webview_test\nflutter pub add webview_flutter\n\n2.Edit main.dart to include a simple WebView\n\ndart\nimport 'package:flutter/material.dart';\nimport 'package:webview_flutter/webview_flutter.dart';\n\nvoid main() {\n runApp(MyApp());\n}\n\nclass MyApp extends StatefulWidget {\n @override\n _MyAppState createState() => _MyAppState();\n}\n\nclass _MyAppState extends State {\n late final WebViewController _controller;\n\n @override\n void initState() {\n super.initState();\n _controller = WebViewController()\n ..loadRequest(Uri.parse(' URL \n }\n\n @override\n Widget build(BuildContext context) {\n return MaterialApp(\n home: Scaffold(\n appBar: AppBar(title: Text(\"WebView Test\")),\n body: WebViewWidget(controller: _controller),\n ),\n );\n }\n}\n\n3.Execute flutter run\n\n### Expected results\n\nThe web page ( URL should display correctly in the WebView.\nThe user must be able to interact with the page (scroll, clicks, etc.).\n\n### Actual results\n\nOn some Huawei devices ( y8p, y9s, p30 pro, p40 pro ..) :\n\n-The WebView screen stay blank.\n-Sometimes the application crashes immediately when opening the WebView.\n\n### Code sample\n\n(The code provided in the \"Steps to reproduce\" section can be used as a minimal, reproducible example.)\n\n### Screenshots or Video\n\n \n Screenshots / Video demonstration \n\n[Upload media here]\n\n \n\n### Logs\n\n Logs \n\nconsole\n[Paste your logs here]\n\n \n\n### Flutter Doctor output\n\nDoctor summary (to see all details, run flutter doctor -v):\n[✓] Flutter (Channel stable, 3.27.3, on Microsoft Windows [version 10.0.26100.3194], locale fr-FR)\n[✓] Windows Version (Installed version of Windows is version 10 or higher)\n[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)\n[✓] Chrome - develop for the web\n[✗] Visual Studio - develop Windows apps\n ✗ Visual Studio not installed; this is necessary to develop Windows apps.\n Download at URL \n Please install the \"Desktop development with C++\" workload, including all of its default components\n[✓] Android Studio (version 2022.3)\n[!] Android Studio (version 2024.2)\n ✗ Unable to determine bundled Java version.\n[✓] Connected device (3 available)\n[✓] Network resources","reference_answer":"I've landed some changes to master that changes how we do selection of platform views and rendering backend choice on mediatek devices that I believe should fix these issues.","answer_document_id":"gh_comment_2691019245","silver_evidence_path":["gh_comment_2712092908","gh_issue_2852148373","gh_comment_2691019245"],"known_context_document_ids":["gh_issue_2906724872"],"evidence_issue_ids":[2906724872,2852148373],"source_repo_name":"flutter/flutter","source_issue_id":2906724872,"source_issue_url":"https://github.com/flutter/flutter/issues/164897","target_repo_name":"flutter/flutter","target_issue_id":2852148373,"target_issue_url":"https://github.com/flutter/flutter/issues/163262","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0419","query":"commit `Implement Quick Dungeons Select` seems to have broken the desktop version of `additionalvisualsettings`?","query_context":"ended up leaving a comment on the commit, but thought I should throw up an issue about it as well. Upon updating scripts, the latest version of `additionalvisualsettings` seems to be broken and no longer loading in the desktop version of the game.\n\nIf I go and put it in the `scripts` folder and change it back to the older version it seems to work again, but obviously I end up missing the reason for the update.\n\nI'm just wondering if you are just no longer supporting the desktop version? as there are a couple scripts as of recent that just don't work in the desktop version at all.\n\nScript that don't show up in desktop version are as followed:\nadditionalvisualsettings (broken within recent commit)\ncatchfilterfantasia\nperkypokeruspandemic","reference_answer":"The scripts should update automatically and should also support new scripts, at least this is the design of it and how I made the client edit initially work, but then again ever since catchfilterfantasia got introduced, that has also been causing problems.\n\nIt's likely that the custom edit needs to be updated and needs to be looked at, but then again I haven't touched this or have been wanting to maintain this since January.","answer_document_id":"gh_comment_1167823338","silver_evidence_path":["gh_comment_1170663574","gh_issue_1285789701","gh_comment_1167823338"],"known_context_document_ids":["gh_issue_1289442289"],"evidence_issue_ids":[1289442289,1285789701],"source_repo_name":"Ephenia/Pokeclicker-Scripts","source_issue_id":1289442289,"source_issue_url":"https://github.com/Ephenia/Pokeclicker-Scripts/issues/163","target_repo_name":"Ephenia/Pokeclicker-Scripts","target_issue_id":1285789701,"target_issue_url":"https://github.com/Ephenia/Pokeclicker-Scripts/issues/158","split":"dev","quality_score":87.36,"annotation_level":"silver"}
{"query_id":"cross_issue_0431","query":"Multiple Formbuilder Forms on a single page not working properly.","query_context":"### Description: Two Formbuilder forms on a single page not working properly when clicking on the save button.\n\n### Environment Details: I am working on a staging environment having PHP on the stack side\n\n - formBuilder Version: Latest one\n - Browser: Chrome\n - OS: Windows\n\n### Expected Behavior: No matter how many formbuilder forms we use on a single page if the ids of that formbuilder form are different. Each action should work with respect to individual forms. \n\n### Actual Behavior: Right now once I click on the save button of the first formbuilder form it throws some error \"Uncaught TypeError: formBuilder.actions.getData is not a function\"\n\n### Steps to Reproduce: Below is complete code which I am working on:\n**JS** \n\njQuery(function($) {\n var fbTemplate = document.getElementById('fb-editor');\n var options = {\n disabledActionButtons: ['data','clear','save']\n };\n var formBuilder = $(fbTemplate).formBuilder(options);\n document.getElementById('getJSON').addEventListener('click', function() {\n alert(formBuilder.actions.getData('json'));\n });\n var fbTemplate1 = document.getElementById('fb-editor1');\n var options1 = {\n disabledActionButtons: ['data','clear','save']\n };\n var formBuilder2 = $(fbTemplate1).formBuilder(options1);\n document.getElementById('getJSON1').addEventListener('click', function() {\n alert(formBuilder2.actions.getData('json'));\n });\n});\n\n**HTML**\n\n \n Get JSON Data \n \n Get JSON Data","reference_answer":"formRender does not have the promise interface, only multiple formBuilder instances need to be created via awaiting the promise interface.","answer_document_id":"gh_comment_1689106147","silver_evidence_path":["gh_comment_1654833720","gh_issue_638416841","gh_comment_1689106147"],"known_context_document_ids":["gh_issue_1427498041"],"evidence_issue_ids":[1427498041,638416841],"source_repo_name":"kevinchappell/formBuilder","source_issue_id":1427498041,"source_issue_url":"https://github.com/kevinchappell/formBuilder/issues/1340","target_repo_name":"kevinchappell/formBuilder","target_issue_id":638416841,"target_issue_url":"https://github.com/kevinchappell/formBuilder/issues/1087","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0434","query":"waardelijst soortblusinstallaties, niet compleet?","query_context":"Onderstaand de huidige inhoud van de waardelijst soortblusinstallaties V1.0.\nDaaronder de lijst zoals in BKL, bijlage VII tabel B.3.\nVraagt dat om een uitbreiding van de waarden in de IMEV lijst?\n\nimage\n\n \nInformatie over blusinstallaties uit BKL VII tabel B.3\n\n**Beschermingsniveau volgens PGS 15, blussysteem en stikstofgehalte** \n\n**Beschermingsniveau 1** \n(Semi-)automatische monitorinstallatie \nAutomatische deluge installatie \nAutomatische hi-ex outside-air installatie, stikstofgehalte 10% \nBedrijfsbrandweer met ter plaatse blussen, stikstofgehalte 10% \n\n**Beschermingsniveau 2a, stikstofgehalte 10 %**\nADR-klasse 3 in kunststof \nADR-klasse 3 niet in kunststof \nGeen ADR-klasse 3 \n\n**Beschermingsniveau 3**\nStikstofgehalte 10%\n\n**Alle beschermingsniveaus** \n Gasflessen","reference_answer":"Gesloten, omdat het verwerkt is in versie 1.2 en omdat die versie goedgekeurd is.","answer_document_id":"gh_comment_1155304054","silver_evidence_path":["gh_comment_1029849854","gh_issue_889781390","gh_comment_1155304054"],"known_context_document_ids":["gh_issue_1084691551"],"evidence_issue_ids":[1084691551,889781390],"source_repo_name":"Geonovum/imev-werkomgeving","source_issue_id":1084691551,"source_issue_url":"https://github.com/Geonovum/imev-werkomgeving/issues/37","target_repo_name":"Geonovum/imev-werkomgeving","target_issue_id":889781390,"target_issue_url":"https://github.com/Geonovum/imev-werkomgeving/issues/18","split":"dev","quality_score":83.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0436","query":"Scala 3 generated @main function is generated in package scope?","query_context":"## Compiler version\n\nScala 3\n\n## Minimized code\n\nSuppose you are converting a Scala 2 application that has 2 main methods in the same package. This is not that uncommon as you may put applications in a `app` package. Here is the code, put in the same file for simplicity for the issue.\n\nscala\npackage app\n\nobject Foo {\n def main(args: Array[String]): Unit = println(\"Foo\")\n}\n\nobject Bar {\n def main(args: Array[String]): Unit = println(\"Bar\")\n}\n\nNow you are converting this Scala 3 or just happen to want to add another application and you like the name `main` for your entry point as you are used to that convention. You convert the `args` using the documentation as you would get an conversion error **No given instance ...** if you left it as an `Array[String]`.\n\nscala\npackage app\n\nobject Foo {\n @main def main(args: String*): Unit = println(\"Foo\")\n}\n\nobject Bar {\n @main def main(args: String*): Unit = println(\"Bar\")\n}\n\n## Output\n\nNow this second example doesn't compile with a **main is already defined as main ...** error pointing to one or the other application that was compiled first.\n\n## Expectation\n\nGenerated or synthetic code should be scoped to the scope it is found in. It seems weird that code found in `object` scope is generated in package scope. This may be a more advanced way of thinking about this. The overall point is this is really surprising and bound to catch people because of the overall ergonomics.\n\nThere is also an additional surprise as follows:\n\nscala\npackage baz\n\nobject Bar {\n @main def main(): Unit = println(\"main Bar\")\n @main def bar(): Unit = println(\"bar Bar\")\n}\n\nResults in a warning (maybe for case insensitive file systems or something).\n\nscala\nwarn] 9 |object Bar {\n[warn] | ^\n[warn] |Not generating the static forwarders of Top(baz.Bar) because its name differs only in case from the name of another class or trait in this compilation unit.\n\nNote that main functions are not really special in Java except for the signature. They can be called by other code like a normal function. \n\nI know the intent was to try and make entry points easier, nicer, and more flexible with less boiler plate. These sort of \"edge\" cases or just stuff people may try to do will be very unexpected.\n\nThanks.","reference_answer":"@EugeneFlesselle @jan-pieter @nmcb we will use the following Zoom link for today:\n URL","answer_document_id":"gh_comment_2286483270","silver_evidence_path":["gh_comment_2283672714","gh_issue_2460683482","gh_comment_2286483270"],"known_context_document_ids":["gh_issue_2453969514"],"evidence_issue_ids":[2453969514,2460683482],"source_repo_name":"scala/scala3","source_issue_id":2453969514,"source_issue_url":"https://github.com/scala/scala3/issues/21348","target_repo_name":"scala/scala3","target_issue_id":2460683482,"target_issue_url":"https://github.com/scala/scala3/issues/21365","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0443","query":"Adding UNITASK_DOTWEEN_SUPPORT scripting define results in a ton of warnings about not awaiting a tween/sequence?","query_context":"I'm using DOTween for tweens and UniTask for async. I didn't realize for a while that DOTween was supported directly but a script define had to be added. So I went to add it today and it results in a ton of warnings on my tweens/sequences saying \"Because this call is not awaited, execution of the current method continues before the call is completed. Consider applying the 'await' operator to the result of the call.\". Some examples of code:\n\nSequence s = DOTween.Sequence();\n// every line after this shows the warning\ns.Append(container.DOFade(1, 0.75f));\ns.AppendInterval(this.mediaDuration);\ns.Append(container.DOFade(0, 0.75f));\ns.SetId(this.GetInstanceID());\n\nTween t = container.DOFade(0, 0.25f);\nbool wasKilled = false;\n// the following line shows the warning\nt.OnKill(() => wasKilled = true);\n\n// all regular tweens show it too\nthis.rightQuestion.DOFade(1, 1);\n\nAny way to make these warnings go away? I think the issue is that Tweens are directly awaitable (`await this.rightQuestion.DOFade(1, 1)`). I wonder if it would make more sense to require calling a function on the tween/sequence in order to await the tween. For example, without the script define, you have to do `this.rightQuestion.DOFade(1, 1).AsyncWaitForCompletion()` in order to await the tween. For UnityWebRequests, you have to call `SendWebRequest` in order to await it. Seems like it would be more consistent with other objects if you had to call a function and it would remove all the warnings.","reference_answer":"Ah yeah. I don't think that's too bad.\n\nHowever, isn't it a bit confusing that the presence or absence of `using UniTask` changes whether or not a discard is required?","answer_document_id":"gh_comment_1909423767","silver_evidence_path":["gh_comment_1718674004","gh_issue_1641551589","gh_comment_1909423767"],"known_context_document_ids":["gh_issue_1888875846"],"evidence_issue_ids":[1888875846,1641551589],"source_repo_name":"Cysharp/UniTask","source_issue_id":1888875846,"source_issue_url":"https://github.com/Cysharp/UniTask/issues/502","target_repo_name":"Cysharp/UniTask","target_issue_id":1641551589,"target_issue_url":"https://github.com/Cysharp/UniTask/issues/452","split":"dev","quality_score":86.12,"annotation_level":"silver"}
{"query_id":"cross_issue_0448","query":"Carthage Xcode >=12 compatibility?","query_context":"Generate xcframework for the next version in order to avoid using carthage workaround\n\n URL \n\n@cbaker6","reference_answer":"@mman I've been bashing my head against against something for a minute now... I've got my branch rebased with mainline, but it seems like no matter what I do, I can't get the tests to see the main source files. You're doing it with cSettings I gather, but when I do similar, they seem to be ignored.\n\nDo you know of any reason why this might be? The only differences I can see are that I use the path and publicHeadersPath attributes.","answer_document_id":"gh_comment_1027982635","silver_evidence_path":["gh_comment_1017476827","gh_issue_496619883","gh_comment_1027982635"],"known_context_document_ids":["gh_issue_780775604"],"evidence_issue_ids":[780775604,496619883],"source_repo_name":"parse-community/Parse-SDK-iOS-OSX","source_issue_id":780775604,"source_issue_url":"https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/1591","target_repo_name":"parse-community/Parse-SDK-iOS-OSX","target_issue_id":496619883,"target_issue_url":"https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/1453","split":"dev","quality_score":92.56,"annotation_level":"silver"}
{"query_id":"cross_issue_0451","query":"Support Root-Relative Links (Absolute Links)?","query_context":"Hi @wooorm ! 👋\n\n### Subject of the feature\n\nWhat do you think about supporting root-relative links such as in the example below?\n\nmd\nabc\nabc\n\nI suppose this could be configured with a configuration option, maybe named like `basedir`.\n\n### Problem\n\nOn large sites with a lot of moving files or large directory structures, updating relative links can be a pain.\n\nRoot relative links can also avoid any ambiguity that can be caused by using the same path ending and file name between multiple files.\n\n### Expected behaviour\n\nIt would be nice for these links to also be checked.\n\n### Alternatives\n\ngatsby-remark-check-links, but:\n\n1. It's Gatsby-specific\n2. It runs as a Gatsby plugin and only warns in the console :(\n\ngh-action-check-broken-links, but:\n\n1. It's wrapped in a GitHub Action\n2. It assumes everything is in a `pages` directory","reference_answer":"I recommend adding an option to `urlConfig`, similar to `lines: boolean`, which is then checked for here. Something along the lines of: `resolveAbsolutePathsInRepo: boolean`? That way, folks can configure whether their hosted git supports this or not.\n\nFurthermore, you are now creating a *path* inside `value`, in your `if` branch.\nBut the value we are making is a (serialized) *URL*.\n`path.resolve` and `config.root` are all about paths. (note: see my last paragraph of this comment later touches on this again)\n\nFor reference, I checked the following in a private repo (`wooorm/private`) on GitHub:\n\n`readme.md`\n\nmarkdown\nalpha\nbravo\ncharlie\ndelta\necho\nfoxtrot\n\n`x/y/z.md` (empty)\n\nmarkdown\n\nGithub generates the following HTML for the readme:\n\nhtml\n alpha \n bravo \n charlie \n delta \n echo \n foxtrot \n\nThat is to say, all absolute paths are prefixed with `/wooorm/private/blob/main`.\nso `!config.urlConfig.prefix.startsWith(value)` and the current handling are not needed.\nThe information needed to construct `/wooorm/private/blob/main`, other than the branch,\nis in `urlConfig.prefix`.\nMissing a branch is fine, we don’t use it yet: URL \n\nSo, I personally would do something like the following pseudocode:\n\njs\n // Absolute paths: `/path/to/file.md`.\n if (value.charAt(0) === slash) {\n if (!config.urlConfig.hostname) {\n return\n }\n\n // Create a URL.\n const pathname = config.urlConfig.resolveAbsolutePathsInRepo && config.urlConfig.prefix\n ? config.urlConfig.prefix + 'unknown' + value\n : value.slice(1)\n value = https + slashes + config.urlConfig.hostname + pathname\n }\n\n…where `unknown` is a temporary value for a branch name, which is dropped later!\n\nFinally, the function as I look at it now is a bit of a mix between path and URL handling.\nThat’s ambiguous and probably points to some bugs.\nIt’s probably better to investigate all that and look at it some more some other time though!","answer_document_id":"gh_comment_1508684337","silver_evidence_path":["gh_comment_2450152500","gh_issue_1660806613","gh_comment_1508684337"],"known_context_document_ids":["gh_issue_678998792"],"evidence_issue_ids":[678998792,1660806613],"source_repo_name":"remarkjs/remark-validate-links","source_issue_id":678998792,"source_issue_url":"https://github.com/remarkjs/remark-validate-links/issues/57","target_repo_name":"remarkjs/remark-validate-links","target_issue_id":1660806613,"target_issue_url":"https://github.com/remarkjs/remark-validate-links/issues/75","split":"dev","quality_score":87.29,"annotation_level":"silver"}
{"query_id":"cross_issue_0454","query":"throughput of the stream is too low?","query_context":"Hello, I'm testing the throughput of the quic stream on the localhost.\n \nIn my test, I can only obtain a throughput of approximately 5MBps. \n\nTest environments:\n quic-go version: 0.51.0, 0.48.0, and the perf tool\n OS: window11 or ubuntu2204\n go version: go1.23\n\nThe results of throughput tests obtained on these platforms are roughly the same, all very low. I want to know what might be the reason for this? \n\nThank you!\n\nThe following is my test code:\n\n \n// client\ndata := make([]byte, 8192)\nfor i := 0; i < 8192; i++ {\n data[i] = byte(i)\n}\ncnt := 100000\n\nstream, err := conn.OpenStreamSync(context.Background())\nif err != nil {\n return err\n}\ndefer stream.Close()\n\nfor i := 0; i < cnt; i++ {\n _, err = stream.Write(data)\n if err != nil {\n return err\n }\n}\n\n \n// server\nconn, err := listener.Accept(context.Background())\nif err != nil {\n return err\n}\n\nvar totalBytes int64\nvar started bool\nvar startTime time.Time\n\nstream, err := conn.AcceptStream(context.Background())\nif err != nil {\n log.Printf(\"AcceptStream error: %v\", err)\n}\ndefer stream.Close()\n\nbuf := make([]byte, 8192)\nfor {\n n, err := stream.Read(buf)\n if err != nil {\n if err != io.EOF {\n log.Printf(\"Stream %d error: %v\", stream.StreamID(), err)\n }\n break\n }\n if !started {\n started = true\n startTime = time.Now()\n }\n totalBytes += int64(n)\n elapsed := time.Since(startTime).Seconds()\n currentBandwidth := float64(totalBytes) / (elapsed * 1e6)\n fmt.Printf(\"\\rCurrent throughput: %.2f MBps\", currentBandwidth)\n}\nreturn nil\n\nI also conducted tests on up to 32 streams, and the obtained throughput was approximately the same.","reference_answer":"We're currently not using batched writes, so it's not unexpected that you can't fill a 10 Gbit link.\n\nThere's been work on using the `sendmmsg` API in URL which surfaced that we were allocating like crazy, which was killing performance due to GC constantly kicking in. In the mean time, we've done a lot of work to reduce allocs, and we'll be done >80% once we merge all the outstanding PRs linked in URL \nThere's also some subtle issues with how Go delivers packets from the kernel to the QUIC layer, which affect how timely we can acknowledge incoming packets, which has complicated implications on the congestion controller.\n\nOther than that, there's a new Go API in the works to allow batched writes in a more efficient way: URL I expect huge performance improvements from this, but obviously we'll have to wait for this API to actually be implemented before we can put numbers on this.","answer_document_id":"gh_comment_1374622785","silver_evidence_path":["gh_comment_2837326551","gh_issue_1522202081","gh_comment_1374622785"],"known_context_document_ids":["gh_issue_3026831815"],"evidence_issue_ids":[3026831815,1522202081],"source_repo_name":"quic-go/quic-go","source_issue_id":3026831815,"source_issue_url":"https://github.com/quic-go/quic-go/issues/5091","target_repo_name":"quic-go/quic-go","target_issue_id":1522202081,"target_issue_url":"https://github.com/quic-go/quic-go/issues/3670","split":"dev","quality_score":94.26,"annotation_level":"silver"}
{"query_id":"cross_issue_0461","query":"Parsing error: Cannot use keyword 'await' outside an async function?","query_context":"**What version of this package are you using?**\n\n14.3.4\n\n**What operating system, Node.js, and npm version?**\n\nNode: 14.13.0\nnpm: 6.14.8\nOS: macOS Catalina 10.15.5\n\n**What happened?**\n\nGiven code:\n\njs\nimport { fileURLToPath } from 'url'\nimport fs from 'fs'\nconst file = await fs.promise.readFile(fileURLToPath(import.meta.url))\nconsole.log(file.toString())\n\nOutput is:\n\nstandard: Use JavaScript Standard Style ( URL \n example.mjs:3:14: Parsing error: Cannot use keyword 'await' outside an async function\n\n**What did you expect to happen?**\n\n`Top-level await` is a stage 3 proposal (see URL but is enabled by default in from Node 14.8.0 (see URL \n\nThis is going to mean that linting with apps written for Node 14+ will be problematic, as top-level await is bound to be used. \n\nSince Node 14 is becoming Active LTS in a few weeks I think TLA should pass linting\n\n**Are you willing to submit a pull request to fix this bug?**\n\nyes","reference_answer":"I can try to roll one later, but if there’s no _need_ for you to run with a newer version of `eslint-plugin-n` then you can simply downgrade it to the version that `standard` expects.","answer_document_id":"gh_comment_1062025961","silver_evidence_path":["gh_comment_1014753723","gh_issue_1096525083","gh_comment_1062025961"],"known_context_document_ids":["gh_issue_716873209"],"evidence_issue_ids":[716873209,1096525083],"source_repo_name":"standard/standard","source_issue_id":716873209,"source_issue_url":"https://github.com/standard/standard/issues/1548","target_repo_name":"standard/eslint-config-standard","target_issue_id":1096525083,"target_issue_url":"https://github.com/standard/eslint-config-standard/issues/208","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0462","query":"[Issue]: The provided authorization code or refresh token is revoked.","query_context":"I installed v4 yesterday (upgrade from v3 via delete v3 -> install v4) and it seemd to work fine, but this morning it is not working anymore with the following error:\n \n\nDeleting the configuration incl. credentials and re-adding them to re-do the OAuth-flow solved the problem.\nI'll update this issue if it happens again, but maybe an option to manually re-do OAuth without deleting would be good?\n\nThanks for your work and regards,\nChristoph","reference_answer":"Maybe Daikin changed something for the old API, you are using that. Btw, change your daikin password, this was listed plain text in your json (which I just removed)","answer_document_id":"gh_comment_2004315404","silver_evidence_path":["gh_comment_1972620054","gh_issue_2139900425","gh_comment_2004315404"],"known_context_document_ids":["gh_issue_2162721039"],"evidence_issue_ids":[2162721039,2139900425],"source_repo_name":"jwillemsen/daikin_onecta","source_issue_id":2162721039,"source_issue_url":"https://github.com/jwillemsen/daikin_onecta/issues/62","target_repo_name":"jwillemsen/daikin_onecta","target_issue_id":2139900425,"target_issue_url":"https://github.com/jwillemsen/daikin_onecta/issues/41","split":"dev","quality_score":91.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0463","query":"Introduce flow control between partitions?","query_context":"**Description**\n\nPartitions send commands between each for the following cases:\n\n- Message correlation (including correlation)\n- Deployment distribution\n\nIn both cases, since communication is assumed to be unreliable, we have built-in retry mechanisms. In the event of a failure in these, or a bug on either side, it can happen that the sender overloads the receiver. Or it can be that the receiver is generally overloaded and the sender shouldn't send anything until the situation resolves itself.\n\nThere's no way for the receiver to notify the sender at the moment that it should slow down. We saw this in one incident, where the deployment distributor kept retrying deployments at a faster rate than the receiving partition could process, resulting in the build up of an incredibly large log and that partition being effectively unavailable from a user point of view.\n\nIdeally, we should see a solution which satisfies the following:\n\n- [ ] Commands from other partitions can be rejected based on the current load, sharing the same rate limiter as external commands\n- [ ] Certain commands may need to be whitelisted (e.g. backup/checkpoint related commands)\n- [ ] The receiving partition can provide information about when to retry\n- [ ] The sending partition does not buffer commands for retry in an unbounded way\n\nThe last point is to ensure we don't run out of memory by buffering commands to be sent to a given partition which is unable to process any commands for a longer period of time.","reference_answer":"We're working on another solution for that in parallel. URL \n\nI know the issue specifies IPC, but the proposed solution will enforce rate limits between the different categories, user submitted commands, internal/scheduled commands, and remote ones.","answer_document_id":"gh_comment_1806797939","silver_evidence_path":["gh_comment_1802371153","gh_issue_1846746772","gh_comment_1806797939"],"known_context_document_ids":["gh_issue_1341358608"],"evidence_issue_ids":[1341358608,1846746772],"source_repo_name":"camunda/camunda","source_issue_id":1341358608,"source_issue_url":"https://github.com/camunda/camunda/issues/10087","target_repo_name":"camunda/zeebe","target_issue_id":1846746772,"target_issue_url":"https://github.com/camunda/zeebe/issues/13870","split":"dev","quality_score":96.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0474","query":"Graceful shutdown consistently takes 90 seconds?","query_context":"Jan 13 02:50:04 azalea systemd[1]: Reached target System Power Off.\n░░ Subject: A start job for unit poweroff.target has finished successfully\n░░ Defined-By: systemd\n░░ Support: URL \n░░\n░░ A start job for unit poweroff.target has finished successfully.\n░░\n░░ The job identifier is 6768.\nJan 13 02:50:04 azalea systemd[1]: Shutting down.\nJan 13 02:50:04 azalea systemd-shutdown[1]: Syncing filesystems and block devices.\nJan 13 02:50:04 azalea systemd-shutdown[1]: Sending SIGTERM to remaining processes...\nJan 13 02:50:04 azalea systemd-journald[662]: Received SIGTERM from PID 1 (systemd-shutdow).\nJan 13 02:50:04 azalea systemd-journald[662]: Journal stopped\n░░ Subject: The journal has been stopped\n░░ Defined-By: systemd\n░░ Support: URL \n░░\n░░ The system journal process has shut down and closed all currently\n░░ active journal files.\n░░ The unit UNIT completed and consumed the indicated resources.\nJan 13 02:48:47 azalea kernel: ucsi_acpi USBC000:00: unknown error 256\nJan 13 02:48:47 azalea kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)\nJan 13 02:50:03 azalea systemd[1]: session-3.scope: Stopping timed out. Killing.\nJan 13 02:50:03 azalea systemd[1]: session-3.scope: Killing process 1879 (cosmic-settings) with signal SIGKILL.\nJan 13 02:50:03 azalea systemd[1]: session-3.scope: Killing process 1882 (ctrl-c) with signal SIGKILL.\nJan 13 02:50:03 azalea systemd[1]: session-3.scope: Failed with result 'timeout'.\n░░ Subject: Unit failed\n░░ Defined-By: systemd\n░░ Support: URL \n░░\n░░ The unit session-3.scope has entered the 'failed' state with result 'timeout'.\nJan 13 02:50:03 azalea systemd[1]: Stopped Session 3 of User sebastian.\n░░ Subject: A stop job for unit session-3.scope has finished\n░░ Defined-By: systemd\n░░ Support: URL \n░░\n░░ A stop job for unit session-3.scope has finished.\n░░\n░░ The job identifier is 6778 and the job result is done.\n\nI'm not entirely sure if this is something related to my hardware or with this flake. Has anybody else been able to reproduce?","reference_answer":"Should be fixed now on main branch, please update this flake and remove any workarounds you might have had. Feel free to reopen if you're still having issues!","answer_document_id":"gh_comment_2565662751","silver_evidence_path":["gh_comment_2586604430","gh_issue_2707381654","gh_comment_2565662751"],"known_context_document_ids":["gh_issue_2783393923"],"evidence_issue_ids":[2783393923,2707381654],"source_repo_name":"lilyinstarlight/nixos-cosmic","source_issue_id":2783393923,"source_issue_url":"https://github.com/lilyinstarlight/nixos-cosmic/issues/588","target_repo_name":"lilyinstarlight/nixos-cosmic","target_issue_id":2707381654,"target_issue_url":"https://github.com/lilyinstarlight/nixos-cosmic/issues/498","split":"dev","quality_score":92.58,"annotation_level":"silver"}
{"query_id":"cross_issue_0486","query":"Confusing which Xcode I'm using with a nightly toolchain?","query_context":"Now that Xcode 16 Beta is out I have two Xcodes installed on my machine. I have also downloaded the nightly build of the 6.0 Swift toolchain. Sometimes I want to use it with Xcode 15, sometimes with Xcode 16 Beta. When I use the command to select a Swift toolchain it's confusing which Xcode it's actually using. It would be nice if I could select that separately from the toolchain selection. At the end of they day, they are different environment variables on Mac, DEVELOPER_DIR and TOOLCHAINS.","reference_answer":"There's also the option of just adding to the terminal environment directly using the `ExtensionContext`:\n\ntypescript\ncontext.environmentVariableCollection.clear();\ncontext.environmentVariableCollection.prepend(\n \"PATH\",\n \"/path/to/usr/bin:\",\n { applyAtShellIntegration: true }\n);\nfor (const variable in configuration.swiftEnvironmentVariables) {\n context.environmentVariableCollection.replace(\n variable,\n configuration.swiftEnvironmentVariables[variable],\n { applyAtShellIntegration: true }\n );\n}\n\nUsing this approach the user will have the environment automatically populated in their VS Code terminal without having to launch a special profile. The only minor annoyance being that modifying certain variables (e.g. `PATH`) triggers a warning before the terminal will be updated:\n\n<img width=\"522\" alt=\"Screenshot 2024-06-27 at 2 30 02 PM\" src=\" URL","answer_document_id":"gh_comment_2195430213","silver_evidence_path":["gh_comment_2179046624","gh_issue_2362568103","gh_comment_2195430213"],"known_context_document_ids":["gh_issue_2360603876"],"evidence_issue_ids":[2360603876,2362568103],"source_repo_name":"swiftlang/vscode-swift","source_issue_id":2360603876,"source_issue_url":"https://github.com/swiftlang/vscode-swift/issues/911","target_repo_name":"swiftlang/vscode-swift","target_issue_id":2362568103,"target_issue_url":"https://github.com/swiftlang/vscode-swift/issues/914","split":"dev","quality_score":87.65,"annotation_level":"silver"}
{"query_id":"cross_issue_0487","query":"Better ways to introspect? --> JSON representation of HDC-API?","query_context":"Currently it's a cumbersome mixture of very specific Commands and Properties, which don't scale nicely.\nIt also feels as if it weren't tailored to its use-cases.\n\nDiscarded as bad Idea: A single command with multiple arguments: \n - GetIntrospection(item_type=command, item_id=0xF0, aspect_id=0xF0)\n - That's cumbersome, too, because we need to introduce new tables for item_types and aspect_ids\n - Command returns var data-type\n\nPotentially better idea: A single command without any arguments, which returns a machine-parseable syntax detailing all details about a whole feature. What could such a simple enough syntax be, which …\n - … a microcontroller can generate on the fly, by composing it directly into the TX buffer.\n - … a tool can translate into source-code for proxy-stubs or for descriptors for devices implemented in other languages, i.e. a \"digital twin\" implemented in Python.\n - … a host can use to dynamically create proxy objects.\n - … is human readable.\n\n How about JSON?\nFind out by implementing a proof-of-concept firmware that generates it on-the-fly from descriptor data.","reference_answer":"Thanks to the improvements obtained in #21, we should certainly allow this.\nThe reason being, that custom feature states are much more valuable if their meaning is documented. \n(Lesson learned from the \"Architecting a Bridge\" manifesto: Automate documentation!)\n\nNote how there's no need to make this mandatory. Firmware developers who do not need this feature can just omit it.","answer_document_id":"gh_comment_1312065329","silver_evidence_path":["gh_comment_1304905800","gh_issue_1436967946","gh_comment_1312065329"],"known_context_document_ids":["gh_issue_1437547785"],"evidence_issue_ids":[1437547785,1436967946],"source_repo_name":"kiksotik/hdc","source_issue_id":1437547785,"source_issue_url":"https://github.com/kiksotik/hdc/issues/21","target_repo_name":"kiksotik/hdc","target_issue_id":1436967946,"target_issue_url":"https://github.com/kiksotik/hdc/issues/18","split":"dev","quality_score":85.33,"annotation_level":"silver"}
{"query_id":"cross_issue_0491","query":"úložiště - zobrazení struktury ve stromu?","query_context":"V úložišti v panelu se zobrazením Tabulka a Mřížka by se hodila i možnost zobrazení ve stromu, aby se nemuselo postupně proklikávat po úrovních.","reference_answer":"No ona to nebyla vteřina, bez refreshe nám to nešlo. Ale dneska už je to OK, tak nevím, jestli už jsi s tím něco dělal, nebo se ProArc jen potřeboval prospat.","answer_document_id":"gh_comment_1558566604","silver_evidence_path":["gh_comment_1486767192","gh_issue_1509052415","gh_comment_1558566604"],"known_context_document_ids":["gh_issue_1434530878"],"evidence_issue_ids":[1434530878,1509052415],"source_repo_name":"proarc/proarc-client","source_issue_id":1434530878,"source_issue_url":"https://github.com/proarc/proarc-client/issues/258","target_repo_name":"proarc/proarc-client","target_issue_id":1509052415,"target_issue_url":"https://github.com/proarc/proarc-client/issues/282","split":"dev","quality_score":75.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0493","query":"Support arrays in generated equals function?","query_context":"`toString` and `hashCode` already support this. `data class`es do not, and have an IDE warning about it.\n\nIt should be fairly trivial to add support, I'm just not sure if it's a good idea to. It may be unexpected behavior?","reference_answer":"Or if not, we could make it `compileOnly` for non-native targets only, I imagine.\n\nAnnoying that end-consumers will have to download the Poko deps for no reason, but I agree it's not a deal-breaker and can be a future optimization. Closing!","answer_document_id":"gh_comment_1668408861","silver_evidence_path":["gh_comment_1563359450","gh_issue_1726316390","gh_comment_1668408861"],"known_context_document_ids":["gh_issue_577568685"],"evidence_issue_ids":[577568685,1726316390],"source_repo_name":"drewhamilton/Poko","source_issue_id":577568685,"source_issue_url":"https://github.com/drewhamilton/Poko/issues/1","target_repo_name":"drewhamilton/Poko","target_issue_id":1726316390,"target_issue_url":"https://github.com/drewhamilton/Poko/issues/142","split":"dev","quality_score":88.0,"annotation_level":"silver"}
{"query_id":"cross_issue_0498","query":"ParseOptions: Add `read_tags`?","query_context":"### Summary\n\nUnexpectedly, many projects pull in Lofty *solely* for its property reading. Each time it is used for this purpose, however, all of the tags are still being parsed unnecessarily.\n\nJust as one can skip property reading with `ParseOptions::read_properties(false)`, it may be worth adding `ParseOptions::read_tags()`.\n\n### API design\n\nrust\nimpl ParseOptions {\n pub fn read_tags(&mut self, read_tags: bool) -> Self;\n}","reference_answer":"Kid3 puts markers to show that you can add another tag to the file, not necessarily that it's present, BTW.\n \n\nYeah, I haven't actually seen anyone make use of TagLib's `StringHandler`. I imagine in most cases no errors are noticed since Picard (and likely other tools) add an ID3v2 tag for compatibility. The real issue here is that in Lofty it's a hard error, rather than a discard & warn.","answer_document_id":"gh_comment_2466916028","silver_evidence_path":["gh_comment_2156182298","gh_issue_2235598020","gh_comment_2466916028"],"known_context_document_ids":["gh_issue_1893302202"],"evidence_issue_ids":[1893302202,2235598020],"source_repo_name":"Serial-ATA/lofty-rs","source_issue_id":1893302202,"source_issue_url":"https://github.com/Serial-ATA/lofty-rs/issues/251","target_repo_name":"Serial-ATA/lofty-rs","target_issue_id":2235598020,"target_issue_url":"https://github.com/Serial-ATA/lofty-rs/issues/373","split":"dev","quality_score":94.15,"annotation_level":"silver"}
{"query_id":"cross_issue_0500","query":"Container crashing when trying to retrieve VPN configs?","query_context":"### Is there a pinned issue for this?\n\n- [X] I have read the pinned issues\n\n### Is there an existing or similar issue for this?\n\n- [X] I have searched the existing issues\n\n### Is there any comment in the documentation for this?\n\n- [X] I have read the documentation, especially the FAQ and Troubleshooting parts\n\n### Is this related to the container/transmission?\n\n- [X] I have checked the container repo for issues\n\n### Are you using the latest release?\n\n- [X] I am using the latest release\n\n### Have you tried using the dev branch latest?\n\n- [X] I have tried using dev branch\n\n### Config used\n\nyaml\nversion: '3.8'\nservices:\n transmission-openvpn:\n container_name: 'haugene'\n cap_add:\n - NET_ADMIN\n devices:\n - '/dev/net/tun'\n volumes:\n - /volume1/data/transmission-data/:/data\n - /volume1/data/haugene/resolv.conf:/etc/resolv.conf\n - /volume1/data/haugene/:/config\n environment:\n - OPENVPN_PROVIDER=PROTONVPN\n - OPENVPN_CONFIG=dk.protonvpn.net.udp\n - OPENVPN_USERNAME=**None**\n - OPENVPN_PASSWORD=**None**\n - LOCAL_NETWORK=192.168.1.0/24\n - OVERRIDE_DNS_1=94.140.14.14\n - OVERRIDE_DNS_2=149.112.112.112\n - OPENVPN_OPTS=--inactive 3600 --ping 10 --ping-exit 60\n #- TRANSMISSION_RATIO_LIMIT=3\n #- TRANSMISSION_RATIO_LIMIT_ENABLED=true\n - TRANSMISSION_SPEED_LIMIT_UP_ENABLED=true\n - TRANSMISSION_SPEED_LIMIT_UP=1000\n logging:\n driver: json-file\n options:\n max-size: 10m\n sysctls:\n - net.ipv6.conf.all.disable_ipv6=0\n ports:\n - '9091:9091'\n image: haugene/transmission-openvpn:dev\n\nnetworks:\n default:\n external:\n name: mybridge\n\n### Current Behavior\n\nContainer crashes at start with this error:\n \n \n \n\nThe issue started somewhere in the last 8 days, it was working fine 8 days ago and as far as I can tell ourobouros did not upgrade this container in the last 8 days.\n\n### Expected Behavior\n\ncontainer starting normally\n\n### How have you tried to solve the problem?\n\n1. tried the dev channel\n2. DNS seems to work because I can see this in the logs:\n \n \n\n### Log output\n\nStarting container with revision: 52d432ddca774080040627e3b6ec61fc9e6b0ac7\nTRANSMISSION_HOME is currently set to: /config/transmission-home\nOne or more OVERRIDE_DNS addresses found. Will use them to overwrite /etc/resolv.conf\nCreating TUN device /dev/net/tun\nUsing OpenVPN provider: PROTONVPN\nRunning with VPN_CONFIG_SOURCE auto\nNo bundled config script found for PROTONVPN. Defaulting to external config\nWill get configs from URL \nRepository is already cloned, checking for update\nerror: Your local changes to the following files would be overwritten by merge:\n openvpn/privado/updateConfigs.sh\nPlease commit your changes or stash them before you merge.\nAborting\nUpdating 45cc9b305..35ec20293\n\n### Environment\n\nmarkdown\n- OS: DSM 7.2\n- Docker: 20.10.23\n\n### Anything else?\n\n_No response_","reference_answer":"Exactly, the clones repo is stored in config so check that the git clone\ndeleted\n\nOn Wed, 27 Sep 2023 at 07:10, Niels Morf ***@***.***> wrote:","answer_document_id":"gh_comment_1736374402","silver_evidence_path":["gh_comment_1738938132","gh_issue_1913323259","gh_comment_1736374402"],"known_context_document_ids":["gh_issue_1916921713"],"evidence_issue_ids":[1916921713,1913323259],"source_repo_name":"haugene/vpn-configs-contrib","source_issue_id":1916921713,"source_issue_url":"https://github.com/haugene/vpn-configs-contrib/issues/241","target_repo_name":"haugene/docker-transmission-openvpn","target_issue_id":1913323259,"target_issue_url":"https://github.com/haugene/docker-transmission-openvpn/issues/2727","split":"dev","quality_score":88.0,"annotation_level":"silver"}