sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [CupertinoContextMenu] Potential unremoved overlay entry
Labels: framework,f: cupertino,has reproducible steps,P3,found in release: 3.10,team-design,triaged-design,found in release: 3.13

## Details
According to  https://github.com/flutter/flutter/blob/0ff68b8c610d54dd88585d0f97531208988f80b3/packages/flutter/lib/src/cupertino/context_menu.dart#L560C1-L583C1

`_lastOverlayEntry` is only removed when animation is dismissed or completed. 

What if  the overlayEntry is inserted, and then the `CupertinoContextMenu` is disposed and removed from widgets tree? So the entry will never be removed.

Temporary solution is add `_lastOverlayEntry?.remove()` to

https://github.com/flutter/flutter/blob/0ff68b8c610d54dd88585d0f97531208988f80b3/packages/flutter/lib/src/cupertino/context_menu.dart#L683C1-L687C4

But this is not enough, because there will be no animation, and it will be abrupt for it to suddenly disappear.

## Steps to reproduce

1. Add a `CupertinoContextMenu` to any visible widget.
2. Press it to insert the overlayEntry (the `_DecoyChild`) , while remove the `CupertinoContextMenu` from the widgets tree.
3. The entry never dismissed.
Repository: bitcoin
Issue: test: 999 of 999 multisig
Labels: Tests,good first issue

### Motivation

The stack size limit of 1000 [confuses even those who designed it](https://bitcoin.stackexchange.com/questions/117317/how-can-i-create-a-multi-sign-for-a-large-number-of-users/117320?noredirect=1#comment134168_117320).

It would be useful to have a test to demonstrate that a 999 of 999 Taproot multisig is possible: `multi_a(999, P1, …, P999)`. Especially to make sure our wallet can spend from it and doesn't allow a bigger one (no 999 of 1000 and no 1 of 1000).

### Possible solution

Either expand the descriptors unit test and/or one of the wallet functional tests.

### Useful Skills

Python and a basic understanding of [output descriptors](https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md). Understanding (Mini)script (interpreter) is not necessary unless you actually want to understand why the limit is there.

### Guidance for new contributors

Want to work on this issue?

For guidance on contributing, please read [CONTRIBUTING.md](https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md) before opening your pull request.
Repository: vscode
Issue: [Debt]: Add telemetry data for sticky scroll (+ color picker?)
Labels: debt,telemetry,editor-sticky-scroll
Repository: vscode
Issue: [scss] Cannot open `.scss` files using `@use` import syntax
Labels: bug,help wanted,css-less-scss

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: `YES`

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.80.2 (user setup)
- OS Version: Windows 10 x64

Steps to Reproduce:

1. Create 2 PascalCase folders
2. In folder 1 create file _style1.scss
3. In folder 2 create file _style2.scss
4. In file _style2.scss import _style1.scss with @use syntax (eg: @use "FolderOne/_style1.scss" as *)
5. In _style2.scss do CTRL + Left Click to navigate to _style1.scss

Actual Result:
- Visual studio opens a popup with content: `Error: Unable to open "_style1.scss"`

Expected Result:
- User is able to navigate to _style1.scss

Note:
- The issue occurs with `@import` syntax too.
- The issue only occurs when using `relative path`.
Repository: create-react-app
Issue: react-scripts doesn't check for errors from webpack dev server startCallback()
Labels: needs triage,issue: bug report

### Describe the bug

react-scripts can fail to start the development server, without showing any error information to the user.

From some digging I think the issue is in react-scripts/scripts/start.js, line 125. So far as I can see, when the webpack dev server fails to start then it passes an error to the callback. I hacked it locally to console.log the error and it helped me work out what was wrong with my config, but it's not ideal that react-scripts was silent about the issue.

Something like this might fix it:

    // Launch WebpackDevServer.
    devServer.startCallback(err => {
      if(err) {
        console.log("webpack dev server failed to start");
        console.log(err);
        process.exit();
      }
      if (isInteractive) {
        clearConsole();
      }


### Did you try recovering your dependencies?

Yes, not the problem

### Which terms did you search for in User Guide?

I checked the troubleshooting section, and didn't find anything relevant

### Environment

Environment Info:

  current version of create-react-app: 5.0.1
  running from /Users/mlovett/.npm/_npx/50624/lib/node_modules/create-react-app

  System:
    OS: macOS 13.5
    CPU: (10) x64 Apple M1 Pro
  Binaries:
    Node: 14.20.1 - ~/.nvm/versions/node/v14.20.1/bin/node
    Yarn: Not Found
    npm: 6.14.17 - ~/.nvm/versions/node/v14.20.1/bin/npm
  Browsers:
    Chrome: 115.0.5790.114
    Edge: 115.0.1901.183
    Safari: 16.6
  npmPackages:
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    react-scripts: 5.0.1 => 5.0.1 
  npmGlobalPackages:
    create-react-app: Not Found



### Steps to reproduce

1. Setup a new, clean project:
npx create-react-app my-app
cd my-app
npm start

All ok so far

2. Create a deliberately broken src/setupProxy.js

I used this example file:
module.exports = function() {
  throw new Error("deliberate failure");
};

3. Start the dev server again

### Expected behavior

react-scripts should report the error

### Actual behavior

Console shows:
Compiled successfully!

You can now view my-app in the browser.

  Local:            http://localhost:3000
  On Your Network:  http://192.168.1.193:3000

Note that the development build is not optimized.
To create a production build, use npm run build.

webpack compiled successfully

But... nothing is listening on port 3000

curl -v http://localhost:3000
*   Trying 127.0.0.1:3000...
* connect to 127.0.0.1 port 3000 failed: Connection refused
Repository: angular
Issue: Expose XSRF configuration injection tokens
Labels: feature,area: common/http,feature: insufficient votes

### Which @angular/* package(s) are relevant/related to the feature request?

common

### Description

Currently when setting up XSRF protection in Angular, you can specify custom cookie and header names:
```ts
imports: [
  HttpClientModule,
  HttpClientXsrfModule.withOptions({
    cookieName: 'My-Xsrf-Cookie',
    headerName: 'My-Xsrf-Header',
  }),
],
```
but there is no way of getting/reading those configured values later on for usage within your own service/interceptor/component.

I can see that there are injection tokens defined for XSRF_COOKIE_NAME and XSRF_HEADER_NAME in Angular sources at https://github.com/angular/angular/blob/main/packages/common/http/src/xsrf.ts#L27C14-L27C31, but they dont seem to be exposed, because injecting them does not work:
```ts
import { XSRF_HEADER_NAME } from '@angular/common/http'; // ERROR: Module "@angular/common/http" has no exported member 'XSRF_HEADER_NAME'.ts(2305)
import { Inject, Injectable } from '@angular/core';

@Injectable()
export class MyService {
  public constructor(
    @Inject(XSRF_HEADER_NAME) private readonly _xsrfHeaderName: string,
  ) {}
}
```

### Proposed solution

Exppose `XSRF_COOKIE_NAME`  and `XSRF_HEADER_NAME` injection tokens, so they can be injected into service/interceptor/component.

### Alternatives considered

Its possible to create you own token and use that where needed, but it seems redundant, when XSRF cookie and header names are already set in Angular.
Also if you want to use default Angular cookie/header name there is currently no way to get it programatically, you have to copy them from documentation. It would be handy if Angular somehow exposed its effective XSRF settings.
Repository: next.js
Issue: Parallel routes are rendered unnecessarily
Labels: bug,Navigation

### 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: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.16.0
      npm: 9.8.1
      Yarn: 1.22.19
      pnpm: 8.6.10
    Relevant Packages:
      next: 13.4.13-canary.5
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


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

Routing (next/router, next/navigation, next/link)

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

https://github.com/slvstr-dev/test-parallel

### To Reproduce

- Install project
- Run project locally
- Check console for logs of both routes

### Describe the Bug

In `layout.tsx` I want to render conditionally render a parallel route, f.e. if a user is logged in or not. Currently it runs code from both routes. Console.log's of both `page.tsx` in root and `page.tsx` in `@auth` are being run.

### Expected Behavior

Based on the condition I only expect the console.log from the returned page to run.

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

_No response_

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

_No response_
Repository: go
Issue: x/mobile: iOS framework build with GO randomly hang on iOS
Labels: NeedsInvestigation,mobile

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.19.4
</pre>

### Does this issue reproduce with the latest release?
At the moment is not possible to verify with the latest version of GO.


### What operating system and processor architecture are you using (`go env`)?
The problem appear randomly on ios (GOOS=ios GOARCH=arm64)

### What did you do?
We recived a crash report about a thread having a EXC_BAD_ACCESS on iOS, we are not able to reproduce the crash on our laboratory but after several test we think this behaviour is not cause by the frameworks itself rather than some other problem inside the GO stack that we are not able to figure out. The stacktrace report the following information:

```
Exception Type:  EXC_BAD_ACCESS (SIGABRT)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000038
Exception Codes: 0x0000000000000001, 0x0000000000000038
VM Region Info: 0x38 is not in any region.  Bytes before following region: 68719476680
      REGION TYPE                 START - END      [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      commpage (reserved)     1000000000-7000000000 [384.0G] ---/--- SM=NUL  ...(unallocated)
Triggered by Thread:  2

Thread 2 Crashed:
0   libsystem_kernel.dylib        	0x00000001c95c2558 __pthread_kill + 8 (:-1)
1   libsystem_pthread.dylib       	0x00000001ea403118 pthread_kill + 268 (pthread.c:1670)
2   libsystem_c.dylib             	0x0000000191ba754c raise + 32 (raise.c:30)
3   libname                  	        0x00000001064b44c4 _cgo_topofstack + 5092
4   libname                  	        0x00000001064b2fd8 CMAC_resume + 501884
```

All our stacktrace are identical to this one, all try to access to 0x0000000000000038 and all have the same instruction on the thread. The same device does not always have the crash, make it even harder to track. 

### What did you expect to see?
No crash or some information related to our library


### What did you see instead?
Randomly application crash on our userbase
Repository: vscode
Issue: Opening the quick pick with a <path>@<symbol> pattern does not enter the symbol navigation mode
Labels: bug,quick-open

When opened via terminal:

![image](https://github.com/microsoft/vscode/assets/2193314/8f73cef3-63a8-4bee-9041-f1db52f9a080)

When typed manually:

![image](https://github.com/microsoft/vscode/assets/2193314/9cb8cd50-6135-4f77-84b5-4398505ec996)

We may be using this format for python tests in the future so it would be awesome if it went directly into symbol search

cc @eleanorjboyd
Repository: vscode
Issue: When a document contains many invisible characters, it is unclear what to do to fix that
Labels: feature-request,unicode-highlight

When a document contains many invisible characters, it is unclear what to do to fix that.
Currently, we just show a blue banner saying that the document contains many invisible characters.

It could be useful to have a button in that banner to highlight all occurences instead.
Repository: stable-diffusion-webui
Issue: [Bug]: Bugs in using the SDXL1.0 model  switching models through the '/sdAPI/v1/options' interface, there may be drawing crashes
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

After switching models through the '/sdAPI/v1/options' interface, there may be drawing crashes
Ckpt: dreamshaperXL10_ Alpha2Xl10. safetensors [0f1b80cfe8]
Selecting any model of CKPT and switching the model to SDXL1.0 through the '/sdAPI/v1/options' API interface will result in this bug, which cannot be restored until SD restarts


Picture parameters：
cat
Steps: 20, Sampler: Euler a, CFG scale: 7, Seed: 1393549275, Size: 512x512, Model hash: 0f1b80cfe8, Model: dreamshaperXL10_alpha2Xl10, Clip skip: 2, ENSD: 31337, Version: v1.5.1

Time taken: 1.6 sec.

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/128731958/73f2ac03-d669-4d5b-9000-905e8bcde718)





通过 '/sdapi/v1/options' 接口切换模型以后会出现画崩的情况

ckpt：dreamshaperXL10_alpha2Xl10.safetensors [0f1b80cfe8]

随便选择一个模型，然后通过options接口切换模型到SDXL1.0就会出现这个bug，直到sd重启以后才能恢复



### Steps to reproduce the problem

1. Select any model of ckpt
2. Then switch the model to SDXL1.0 through the '/sdAPI/v1/options' API interface
3. Painting again will reproduce
4. 
![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/128731958/4c6b6a05-94f6-4b8e-b201-030e2c54867f)




1、选择任意型号的ckpt
2、然后通过 '/sdapi/v1/options' api接口切换模型到SDXL1.0
3、再次进行绘画，就会复现

### What should have happened?

![image](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/128731958/62da6100-ebaa-4a91-9390-ad27e041abe0)


### Version or Commit where the problem happens

https://gitcode.net/overbill1683/stable-diffusion-webui/commit/68f336bd994bed5442ad95bad6b6ad5564a5409a

### What Python version are you running on ?

Python 3.10.x

### What platforms do you use to access the UI ?

Windows

### What device are you running WebUI on?

_No response_

### Cross attention optimization

Automatic

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
No
```


### List of extensions

No

### Console logs

```Shell
No exception logs
```


### Additional information

_No response_
Repository: godot
Issue: Crash on lower end hardware when resizing window with mouse
Labels: bug,platform:windows,topic:rendering,topic:porting

### Godot version

4.1.1 stable

### System information

Win 10, latest updates, dedicated Nvidea 765M (2GB VRAM), dedicated Nvidea 1070 (8GB VRAM) both Forward+ renderer

### Issue description

On the 765M Laptop Godot 4.1.1 window **crashes** as soon as I try to resize the Window.
On the 1070 card Godot 4.1.1 drops from ~2100 fps to ~60 fps (vsync disabled) while I try to resize the Window. No crash.

The minimal reproduction scene I tested this has a

Meshinstance3D, (Cube Primitive Mesh)
Camera3D
AnimationPlayer to rotate the cube
WorldEnvironment and DirectionalLight3D to see anything
Label to print the FPS

I have tested this with just the MeshInstance3D and Camera3D with the same result.
Except for disabling vsync, everything else is default. I have also tested this without disabling vsync and the crash on lower spec hardware is the same.

Possibly related: https://github.com/godotengine/godot/issues/79446




### Steps to reproduce

1. Run the MRP, 
2. resize window with mouse

### Minimal reproduction project

[G411_resize_bug.zip](https://github.com/godotengine/godot/files/12195261/G411_resize_bug.zip)
Repository: go
Issue: proposal: database/sql: add methods to scan an entire row into one value
Labels: Proposal

Edited: struct field names are matched to columns case-sensitively.
Edited: untouched storage is ignored rather than zeroed.

---------------

I propose adding the method
```
ScanRow(dest any) error
```
to the `Row` and `Rows` types. `ScanRow` attempts to populate `dest` with all the columns of the current row. `dest` can be a pointer to an array, slice, map or struct. 

## Motivation

`ScanRow` makes it more convenient to populate a row from a struct. Evidence that this is a desirable feature comes from the [github.com/jmoiron/sqlx](https://pkg.go.dev/github.com/jmoiron/sqlx) package, which has 9,800 importers, about 1,000 forks and about 14,000 GitHub stars. (To be fair, `sqlx` provides several other enhancements to `database/sql` as well.) The `ScanRow` method brings `database/sql` closer to parity with `encoding/json`, whose ability to unmarshal into structs and other data types is widely used.

Another motivation comes from the likely addition of [iterators](https://go.dev/issue/61405) to the language. Without something like `ScanRow`, an iterator over a DB query would have to return a `Row` or `Rows`, since the `Scan` method is variadic. An iterator like that still improves on using a `Rows` directly because it makes error-handling more explicit and always calls `Close`. But we could do better with `ScanRow`, because the iterator could deliver a single value holding the entire row:
```
type Product struct {
    Name string
    Quantity int
 }

func processProducts() {
    for p, err := range sql.Query[Product](ctx, db, "SELECT * FROM products") {
       if err != nil {...}
       // use p
    }
}
```
This proposal doesn't include that iterator; I show it merely for motivation.

## Details

`ScanRow` acts as if each part of its argument were passed to `Scan`.

If the value is an array pointer, successive array elements are scanned from the corresponding columns. Excess columns are dropped. Excess array elements are left untouched.

If the value is a slice pointer, the slice is resized to the number of columns and slice elements are scanned from the corresponding columns.

If the value is a map pointer, the underlying key type must be `string`. For each column, a map entry is created whose key is the column name and whose value is scanned from the column. Unnamed columns are assigned unique keys of the form `_%d` for integers 0, 1, .... Other entries in the map are left untouched.

If the value is a struct pointer, its exported visible fields are matched by name to the column names and the field values are scanned from the corresponding columns.  The name matching is done as follows:

1. If the field has a struct tag with key "sql", its value is the column name.
2. Otherwise, the column name is matched to the field name case-sensitively.

Unassigned columns are dropped. Unassigned fields are left untouched.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Allow explicit use of SDXL two different text encoders
Labels: enhancement,sdxl,extension-request

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Looks like SDXL "uses two different text encoders that make sense of the written prompt, helping to pinpoint associated imagery encoded in the model weights. Users can provide a different prompt to each encoder, resulting in novel, high-quality concept combinations."

Cite: https://arstechnica.com/information-technology/2023/07/stable-diffusion-xl-puts-ai-generated-visual-worlds-at-your-gpus-command/

"On Twitter, Xander Steenbrugge showed an example of a combined elephant and an octopus using this technique."

https://twitter.com/xsteenbrugge/status/1684152417087102978?s=20

Is this something that we can do in Auto1111?

### Proposed workflow

1. Allow two different text fields?


### Additional information

_No response_
Repository: pytorch
Issue: Build failure due to C++ version mismatch
Labels: module: build,triaged

### 🐛 Describe the bug

I'm building with GCC 12.2 and "system"/preinstalled protobuf.

The build fails on `caffe2.pb.cc` which includes protobuf which includes abseil which tries to use `std::string_view`.

Abseil was build without specific C++-standard flags so it uses the compilers default, which is C++17. However PyTorchs C++ standard (used to) be C++14: https://github.com/pytorch/pytorch/blob/dff70a5e1a6e7a184a2e75c1b22a8e0ce0944b41/CMakeLists.txt#L40

Both Abseil and Protobuf correctly export (via INTERFACE properties) their required C++ standard but PyTorchs doesn't consistently use the CMake target `protobuf::libprotobuf`

The 2 affected locations are:

- https://github.com/pytorch/pytorch/blob/dffa4e14b912914d461c1af5cea632460ca545aa/caffe2/proto/CMakeLists.txt#L9 which adds an (object-)library containing (generated) protobuf C++ files but that doesn't link against  `protobuf::libprotobuf` and hence doesn't know about it's C++ standard
- https://github.com/pytorch/pytorch/blob/dffa4e14b912914d461c1af5cea632460ca545aa/cmake/ProtoBuf.cmake#L120-L122 which hides the issue by adding the protobuf include path (read from the target) globally (which is discouraged CMake practice)

I was able to resolve this by adding `target_link_libraries(Caffe2_PROTO PUBLIC protobuf::libprotobuf)` and removing https://github.com/pytorch/pytorch/blob/dffa4e14b912914d461c1af5cea632460ca545aa/cmake/ProtoBuf.cmake#L120-L122 

However I'm wondering why the object-library is necessary at all (the objects are used once to create `caffe2_protos`)

Although this (currently) might not be an issue anymore after 36ac095ff8918bf7c208029bf6ad28418f1620c1 raised the standard to C++17 I still think it is wrong to just ignore the C++ standard of (in this case) libprotobuf and any other INTERFACE options it might have set and which may be required to successfully compile it on all systems.

### Versions

1.13.1 - master

cc @malfet @seemethere