sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: cuda stream issue when using NVCUVID
Labels: bug,category: gpu/cuda (contrib),platform: win32,needs reproducer

### System Information

OpenCV version: 4.8.0
Operating System / Platform: Windows 10
Compiler & compiler version: Visual Studio 2017 

More information: I compiled OpenCV using the Visual Studio generator, not Ninja, and I didn't enable the opencv_world option. I'm not facing this problem with CUVID streaming in all tries, but I occasionally encounter this issue(for example after 30min that 7 rtsp working, this happen)

### Detailed description

I'm facing an issue when I initiate multiple threads, each using it's own `cv::Ptr<cv::cudacodec::VideoReader>` object, to read from an RTSP camera. I don't utilize the stream object in the function `nextFrame`:

    CV_WRAP virtual bool nextFrame(CV_OUT GpuMat& frame, Stream &stream = Stream::Null()) = 0;
 
which I assume should allow CPU-side synchronization. The idea is to read a `GpuMat` from this function, store it in a `std::dequeue`, and then retrieve a frame from the `std::dequeue` when needed(for processing)

However, problems arise when the `GpuMat` undergoes processing, such as car detection in a deep learning model in a optimized `TensorRT` model which the decoding part I wrote in `CUDA`. I encounter errors indicating `operation not permitted when stream is capturing`. I believe I should be able to fetch frames and process them asynchronously without such issues.

      c:\sources\opencv_4.8.0\opencv_contrib\modules\cudev\include\opencv2\cudev\grid\detail/transform.hpp:267: error: (-217:Gpu API call) operation not permitted when stream is capturing in function 'cv::cudev::grid_transform_detail::TransformDispatcher<false, Policy>::call

### Steps to reproduce

It's challenging to provide sample code, but I'll do my best to deliver and maybe that is some mistakes in my code.

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: PowerToys
Issue: Find only folders in Powertoys Run
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

Hi, when searching the right folder by pressing alt + space, i would like to find only folders and nothing else. i have tried to disconnect every other option but it still shows documents, PDF and other documents i am not interested in. I don't know whether it is a bug or a wrong setting or enhancement request.
can you please help on this one please.
BR,
Matt

### Scenario when this would be used?

help go faster

### Supporting information

_No response_
Repository: svelte
Issue: context api not working with custom-elements
Labels: feature request,custom element,documentation

### Describe the bug

i tried to implement https://svelte.dev/docs/svelte#getcontext with custom elements after the svelte 4 release.
i thought it was fixed in #3422 and #8457 but it looks like its still doesnt work.

if i can help in any way let me know, because this currently blocks my implementation

if this cant be fixed it might be an idea to update https://svelte.dev/docs/custom-elements-api#caveats-and-limitations until it is fixed 

### Reproduction

reproduction of the actual code using svelte 4.0.5 https://stackblitz.com/edit/vitejs-vite-gk4rsr
in uc-button-group.svelte i commented out these lines
<!-- <UcButton value="1" operator="decrement">Button value </UcButton> -->
<!-- <UcButton value="2" operator="increment">Button value </UcButton> -->
they use the svelte component directly and work without any problem :)

i made the reproduction on stackblitz because some issues with the repl i already reported in discord :)

### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 13.3.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 1.39 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Chrome Canary: 117.0.5895.0
    Safari: 16.4
```


### Severity

blocking all usage of svelte
Repository: svelte
Issue: de-bloating custom-elements by using Constructable Stylesheets
Labels: custom element

### Describe the problem

Every time a custom element with styling is created it creates a <style> tag what also adds a dom element.
Custom elements already adds more dom elements so allowing to remove one  that is mostly there always would realy make a big difference in dom node creation and also performance.

if any more information needed i can help :)

### Describe the proposed solution

Solution is like LIT implementing usage of Constructable Stylesheets.
Constructable Stylesheets are implementend now in every browser.
svelte beeing all about performance this would be a great step in the right direction for custom element creation with svelte

preventing an excessive DOM size: https://developer.chrome.com/docs/lighthouse/performance/dom-size/
Information on Constructable Stylesheets: https://web.dev/constructable-stylesheets/ and https://github.com/WICG/construct-stylesheets/blob/main/explainer.md

### Alternatives considered

not really 

### Importance

would make my life easier
Repository: material-ui
Issue: `<a>` doesn't have proper color in dark mode
Labels: package: system,component: CssBaseline,customization: theme

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

Steps:

1. Set theme palette mode to dark.
2. Add CssBaseline
3. Add a `<a>` element


### Current behavior 😯

![image](https://github.com/guoyunhe/yara/assets/5836790/3dfc456f-4a27-4e34-a00d-1c4cf219a4a8)

### Expected behavior 🤔

Link color should be more friendly for eyes.

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: rust
Issue: Unconsistent dwarf information between 1.70 and 1.71
Labels: P-medium,regression-from-stable-to-stable,C-bug,A-mir-opt

<!--
Thank you for filing a regression report! 🐛 A regression is something that changed between versions of Rust but was not supposed to.

Please provide a short summary of the regression, along with any information you feel is relevant to replicate it.
-->

### Code

I tried this code:

```rust
fn main() {
    let var_a = 1;
    let var_b = 2; // <- stop here
    let var_c = 3;
}
```

Then run this with rust-gdb:
```
> b test.rs:3
> r
> info locals
```

for rust 1.70 output is correct:
```
var_a = 1
```

for rust 1.71 output contains uninitialized variable:
```
var_b = 0
var_a = 1
```

Lets see whats changed in dwarf, i dump'd 1.70 and 1.71 versions and check difference.

First for 1.70, lexical block of var_b:
```
< 4><0x00000063>          DW_TAG_lexical_block
                            DW_AT_low_pc                0x00071010
                            DW_AT_high_pc               <offset-from-lowpc> 8 <highpc: 0x00071018>
```

And line number info for line 3:
```
0x00071008  [   3,17] NS
```

So it's ok, pc of lexical block for var_b greater then pc of line 3 start, and debugger doesnt show var_b.

Now for 1.71. Lexical block of var_b:
```
< 4><0x00000063>          DW_TAG_lexical_block
                            DW_AT_low_pc                0x0006dd28
                            DW_AT_high_pc               <offset-from-lowpc> 16 <highpc: 0x0006dd38>
```

And line number info for line 3:
```
0x0006dd28  [   3, 9] NS
```

In dwarf generated by rustc 1.71 pc of var_b lexical block are equal to pc of line 3, that's why we see an uninitialized variable.

### Version it worked on

Rust 1.70

### Version with regression

rustc 1.71.0 (8ede3aae2 2023-07-12)
binary: rustc
commit-hash: 8ede3aae28fe6e4d52b38157d7bfe0d3bceef225
commit-date: 2023-07-12
host: x86_64-unknown-linux-gnu
release: 1.71.0
LLVM version: 16.0.5

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"khuey"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: pytorch
Issue: Top level Glossary for users (not contributers)
Labels: module: docs,triaged

### 📚 The doc issue

Related to [https://github.com/pytorch/pytorch/issues/104623](https://github.com/pytorch/pytorch/issues/104623) i propose a new top level glassy that defines concepts that a PyTorch developer is interested in - the rest of the documentation could then link to the standard definitions of words. It should start with definitions of :
-PyTorch
- the associated various repos
- the various packages  
For example as a newby. I would have liked clear definitions of :
- frontend/ backend
- device
- tables of capabilities for different backends 
- what is pickleable an what is not.

I am happy to start this off with a starter set for people to review , then add to.

I know we have GLOSSARY.md - but this seems to be contributor focused, I am not sure if users would need to know about the dispatcher, but may be I am wrong. 



### Suggest a potential alternative/fix

_No response_

cc @svekars @carljparker
Repository: axios
Issue: Not all error / success interceptors is called if success / error interceptor has inappropriate result
Labels: priority::medium

### Describe the bug

If I added interceptor in order:
- a response `errorInterceptor0`
- a response `successInterceptor`
- a response `errorInterceptor1`

and `successInterceptor` throws an error, it will be caught by `errorInterceptor1` only

I checked it only for responses, but I guess it is actual for request interceptors too

### To Reproduce

https://codesandbox.io/p/sandbox/solitary-tdd-39zzzg - with exceptions
https://codesandbox.io/p/sandbox/cocky-lalande-2y4qmv - with results



### Code snippet

```js
import axios from "axios";

axios.interceptors.response.use(() => {
  console.log("success 0");
});
axios.interceptors.response.use(undefined, (error) => {
  console.log("error 0");
  return "success from error";
});
axios.interceptors.response.use(() => {
  console.log("success 1");
});

try {
  const { data } = await axios.get("http://dsfsdfsdfsdf.com");
} catch (e) {}
console.log("done");
```


### Expected behavior

If some success interceptor throws an exception, all appropriate (request or response) error interceptors should be called in the order they was added.
And if some error interceptor returns a value, all success appropriate (request or response) success interceptors should be called.

### Axios Version

1.4.0

### Adapter Version

_No response_

### Browser

_No response_

### Browser Version

_No response_

### Node.js Version

_No response_

### OS

_No response_

### Additional Library Versions

_No response_

### Additional context/Screenshots

_No response_
Repository: PowerToys
Issue: fancyZones Screen Expands/ Maximize
Labels: Needs-Triage

### Description of the new feature / enhancement

When we use power toys fancy zones screens spits into multiple zones but when we use any app in that particular screen size and we want to maximize that particular app in that particular screen it wont happened rather it completely maximize that .

I would suggest to give a additional feature of force lock button that if i want to maximize that particular app in that open fancy zones screen or complete monitor.


This feature is very essential for productivity.
I request the power toys team to implement it as soon as possible.

### Scenario when this would be used?

It would be use in all use cases .

if specific when we use edge browser and install partiular webapp. for trading purpose for coding and etc.





whe we use multiple screens it will be helpfull.
![Add a heading](https://github.com/microsoft/PowerToys/assets/67833258/76e02b6e-128a-4220-a003-ce67a2594d72)


### Supporting information

_No response_
Repository: bitcoin
Issue: guix: re-enable exported symbol checking for RISC-V
Labels: Build system

This is currently disabled, when it can likely be fixed and re-enabled:
https://github.com/bitcoin/bitcoin/blob/673acab223c0f896767b1ae784659df9f95452ae/contrib/devtools/symbol-check.py#L210

A Guix build with the exception dropped shows there are symbols being exported in the RISC-V bins:
```bash
/opt/homebrew/opt/binutils/bin/objdump -T bitcoind

0000000000080500  w   DF .text	00000000000000a6  Base        _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC1IS3_EEPKcRKS3_
000000000007f6a0  w   DF .text	0000000000000064  Base        _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev
000000000007e9da  w   DF .text	0000000000000024  Base        _ZNKSt5ctypeIcE8do_widenEc

std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<std::allocator<char> >(char const*, std::allocator<char> const&)
std::__cxx11::basic_stringbuf<char, std::char_traits<char>, std::allocator<char> >::~basic_stringbuf()
std::ctype<char>::do_widen(char) const
```
Repository: godot
Issue: Overwriting a scene doesn't update all instances of that scene until I reload the main scene
Labels: bug,topic:editor

### Godot version

v4.1.stable.mono.official [970459615]

### System information

Godot v4.1.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; 31.0.15.3179) - AMD Ryzen 5 5600 6-Core Processor (12 Threads)

### Issue description

Overwriting a scene doesn't update all instances of that scene. Restarting Godot or simply closing and reopening the root scene fixes the issue.

### Steps to reproduce

Create a new project and a 3D scene and save it
Add a CanvasLayer
Add a Control as a child to the CanvasLayer
Add a Button to the Control and resize it
Set the Button's text to "A"
Save the Control as control.tscn
Add a second instance of control.tscn (node named Control2) to the CanvasLayer and move it to a different location (so it doesn't cover the first one)
Select the first Control and "make local".
Select the Button on it and resize it, so that it is now smaller than the second one
Change the text on this button to "B"
Now you see two buttons: a small button that says "B" and a big button that says "A"
Save the Control and overwrite control.tscn
Expected result: both controls should have small buttons that say "B"
Actual result: the first control is a small button with B on it, and the second one is a large button with A on it
Save the root scene and close it
open the root scene again
Now both controls have small buttons that say "B"

### Minimal reproduction project

[bugtest3.zip](https://github.com/godotengine/godot/files/12079294/bugtest3.zip)
(here the root scene is node_3d.tscn)
Repository: bitcoin
Issue: 32-bit Linux: build flags lost with depends & overriden CC(X)
Labels: Build system

Building depends for 32-bit Linux (i686-pc-linux-gnu) but setting `CC`/`CXX`, causes us to loose build flags, and ultimately build a 64-bit executable:
```bash
# make -C depends/ HOST=i686-pc-linux-gnu -j9 NO_QT=1 NO_WALLET=1 NO_ZMQ=1 NO_UPNP=1 NO_USDT=1 NO_NATPMP=1 CC=clang CXX=clang++
...
copying packages: boost libevent
to: /home/ubuntu/bitcoin/depends/i686-pc-linux-gnu

./autogen.sh
CONFIG_SITE=/home/ubuntu/bitcoin/depends/i686-pc-linux-gnu/share/config.site ./configure
make -9
....
# file src/bitcoind
src/bitcoind: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=737f136c656f8dd3f5510e0d4d74b20880231066, for GNU/Linux 3.2.0, not stripped
```

We currently work around something similar in our oss-fuzz builds, i.e https://github.com/google/oss-fuzz/pull/10562.
Repository: next.js
Issue: Building with the `app` router + `generateBuildId` causes certain chunks to not be hashed properly
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
    Binaries:
      Node: 16.19.0
      npm: 8.19.3
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10-canary.8
      eslint-config-next: 13.4.10
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/Bakon/nextjs-generateBuildId-issue

### To Reproduce

> npm i

> npm run build (or `next build`)

Inspect / make a screenshot of all the chunks inside `.next/static/chunks`

> npm run build (or `next build`)

Inspect all the chunks inside `.next/static/chunks` again. 
Now you should be able to see that the chunks differ when building again.

![Screenshot 2023-07-18 at 13 35 21](https://github.com/vercel/next.js/assets/13487081/ddaa6866-0972-4142-8c78-ca68866c31de)

### Describe the Bug

When building the application using the `App` Router in combination with `generateBuildId` (next.config.js), _**some**_ chunks are non deterministic.

### Expected Behavior

When building the application using the `App` Router and `generateBuildId` (next.config.js), all the chunks should be deterministic.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: ant-design
Issue: Custom paddings in Collapse aren't clickable
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-vg8yv2?file=/index.js)

### Steps to reproduce

```js

const items: Items = [
    {
        key: '1',
        label: '...',
        children: '...',
        style: {
             padding: 30
        }
    },
}
```

### What is expected?

The paddings are part of the clickable area and  the styles are aplied to `ant-collapse-header-text`


### What is actually happening?

The paddings are not part of the clickable area, because the styles are applied to the `ant-collapse-header` element.


<img width="451" alt="Screenshot 2023-07-18 at 20 01 18" src="https://github.com/ant-design/ant-design/assets/803674/b5b5eb4f-c1d4-458f-9189-07270e9bff19">

<br/>
<br/>


| Environment | Info |
| --- | --- |
| antd | 5.7.0 |
| React | 18 |
| System | macOS |
| Browser | All |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: [ColorPicker]Make the edit color feature more obvious
Labels: Idea-Enhancement,Area-User Interface,Product-Color Picker

### Description of the new feature / enhancement

In the Color Picker Editor, being able to provide a set of values to preview a color.

I was recently creating some CSS with a :hover action and I wanted to create a slightly darker variation of the background color for a button. I would of been convenient to copy/paste my color, and adjust the values to see a real-time preview of the changes.

Any of the supported color options would be useful, what I had in mind was HEX or RGB.

### Scenario when this would be used?

Anytime color previewing, color creation, and/or when the color picker would be useful.

### Supporting information

_No response_
Repository: react
Issue: [DevTools Bug] Cannot add node "1" because a node with that id is already in the Store.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

react-devtools with expo

### Repro steps

Once react-devtools run this happen there 

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-core

### DevTools version (automated)

4.13.5-0ae5290b54

### Error message (automated)

Cannot add node "1" because a node with that id is already in the Store.

### Error call stack (automated)

```text
at /Users/amr/.config/yarn/global/node_modules/react-devtools-core/dist/standalone.js:48:139060
    at c.emit (/Users/amr/.config/yarn/global/node_modules/react-devtools-core/dist/standalone.js:48:88052)
    at /Users/amr/.config/yarn/global/node_modules/react-devtools-core/dist/standalone.js:48:89523
    at /Users/amr/.config/yarn/global/node_modules/react-devtools-core/dist/standalone.js:48:341120
    at Array.forEach (<anonymous>)
    at S.Vc.e.onmessage (/Users/amr/.config/yarn/global/node_modules/react-devtools-core/dist/standalone.js:48:341104)
    at S.n (/Users/amr/.config/yarn/global/node_modules/react-devtools-core/dist/standalone.js:40:2971)
    at S.emit (events.js:315:20)
    at e.exports.P (/Users/amr/.config/yarn/global/node_modules/react-devtools-core/dist/standalone.js:8:9318)
    at e.exports.emit (events.js:315:20)
```


### Error component stack (automated)

_No response_

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add node  because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: pytorch
Issue: Specify version
Labels: module: docs,triaged

### 📚 The doc issue

In many cases, I know that some functionality was only introduced in a recent PyTorch version. E.g. the use of `torch.device` as a context manager, or the function `torch.set_default_device`. I would expect that the documentation mentions in what version this was introduced, but this information is lacking.

### Suggest a potential alternative/fix

For every function, specify since what version it is available.

Also, similarly, if new arguments are added to a function, you could specify since what version the argument is available.

cc @svekars @carljparker
Repository: rust
Issue: "wrong" fixable suggestion with unused import when import is only used in cfg
Labels: T-compiler,A-suggestion-diagnostics,D-invalid-suggestion

In my codebase cargo fix removes a used import later telling me it couldn't find this Enum and suggesting I import it.
I couldn't see the issue in the list of known issues so I'm adding it here.
It's a proprietary code base so I can't share the full example I can try building a smaller reproducible version as this issue happens within the same crate.
Repository: PowerToys
Issue: Resize in Right Click Drag context menu for PSD files
Labels: Issue-Bug,Product-Image Resizer,Priority-2

### Microsoft PowerToys version

0.71.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Image Resizer

### Steps to reproduce

Right-click drag any PSD file and you get "Resize Pictures Here" context menu, and when proceeding to resize it shows error "Can't resize the following pictures"

### ✔️ Expected Behavior

It shouldn't show the resize context menu as for all other non image files 

### ❌ Actual Behavior

It shows resize here context menu 

### Other Software

_No response_