sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Area3D does not reliably detect mouse clicks
Labels: bug,platform:linuxbsd,topic:input

### Godot version

4.1.1, 4.0.3

### System information

Godot v4.1.1.stable - TUXEDO OS 2 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Laptop GPU () - AMD Ryzen 9 5900HX with Radeon Graphics (16 Threads)

### Issue description

I have a Godot 3.5 setup for point&click puzzle games. They use a viewport for the 3d world, and Control nodes for GUI.
There are 2 types of nodes used for hotspots for the mouse : TextureRectangle for navigation (GUI), and Area3D for 3d meshes (viewport). 

In Godot 3.5, everything works fine. In Godot 4.0.3 & 4.1.1, the Area3D nodes have some problems. 
I have encountered 2 scenarios : 1) mouse clicks are detected for a while, and then suddenly stop working, or, they work only now and then, 2) as soon as the mouse clicks outside of the game window (for instance on the desktop, or inside the editor) the Area3D nodes stop working, or, they only work now and then. I have the same problem in a release build. There are no errors in the output window or in the log file.

I have the same minimal project in Godot 3.5 & in Godot 4.1.1.


### Steps to reproduce

Run the project in the editor, click the cube multiple times.
Also try clicking outside the game window, and then repeat clicking on the cube.

### Minimal reproduction project

[Testing_mouse_area3d_Go411.zip](https://github.com/godotengine/godot/files/12174433/Testing_mouse_area3d_Go411.zip)
[Testing_mouse_aread_Go352.zip](https://github.com/godotengine/godot/files/12174443/Testing_mouse_aread_Go352.zip)
Repository: terminal
Issue: Add cursorTextColor attribute to colour schemes
Labels: Issue-Feature,Area-Rendering,Area-Settings,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

Colour schemes allow setting the cursor colour (`cursorColor`), however, they don't allow setting the text colour of the character under the cursor. The character under the cursor just keeps its native colour. This is a problem for the _Filled Box_ cursor type because the character under the cursor may become very illegible if the cursor colour and character colour don't happen to naturally contrast.

This problem is exacerbated in applications like Vim where the text that the cursor moves over comes in many different colours. Thus, the problem can't be generally solved by changing the cursor colour because there might always be some combination of cursor and text colour that remain illegible.

The best solution to this problem would be to always change the colour of the character under the cursor to a colour that contrasts well with the cursor colour. In this way, it's guaranteed that the character under the cursor is always legible.

This could be implemented by adding a cursor text colour attribute to the colour scheme (e.g. `cursorTextColor` attribute), so that colour scheme designers can choose a good combination.

That's also exactly how it is done in iTerm2:

![unnamed](https://github.com/microsoft/terminal/assets/2396208/d7a9741c-efe1-43b5-90d7-ba8da960b078)

Considerations:

- This applies only to the _Filled Box_ cursor type. For the other cursor types, it's not necessary to change the colour of the character under the cursor.
- Thus, the attribute could maybe be named `cursorFilledBoxTextColor` to make this clear.

Related:

- #1203 addressed a similar issue, however, it only solved printing the character on top of the cursor instead of below it. It does not change the colour of the character, and thus the problem of illegible colour combinations remains.
Repository: flutter
Issue: Think about stress test multi-view scenarios
Labels: a: desktop,P3,a: multi window,team-framework,triaged-framework
Repository: vscode
Issue: "Turn on Cloud Changes" in vscode.dev does nothing once user signs in
Labels: bug,github-repositories

- Open a remote repo in vscode.dev
- Open terminal
- Click link to turn on cloud changes, sign in successfully
- 🐛 When I click the link again, nothing happens. I'd expect if I'm signed in, the link points to docs, or it goes away if there's no action left to take

![image](https://github.com/microsoft/vscode/assets/25310137/1bbcb1b4-50d2-4b84-aec9-3d5788f3c367)
Repository: transformers
Issue: Add Vocos model
Labels: New model

### Model description

Vocos is a Fourier-based neural vocoder for audio synthesis.

According to its [paper](https://arxiv.org/pdf/2306.00814.pdf), Vocos constantly outperforms [HifiGan](https://huggingface.co/docs/transformers/main/en/model_doc/speecht5#transformers.SpeechT5HifiGan), has 13.5M params and is significantly faster than any competing vocoders!

Moreover, it is also compatible with Bark, and significantly improve audio quality as showed [here](https://charactr-platform.github.io/vocos/#audio-reconstruction-from-bark-tokens).

Vocos is composed of a backbone (ConvNeXt) and an inverse fourier transform head (either STFT or MDCT).  


### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Vocos code is available [here](https://github.com/charactr-platform/vocos/tree/main) and was mainly contributed by @hubertsiuzdak.

Its weights are available on HF hub [here](https://huggingface.co/charactr/vocos-mel-24khz) and [here](https://huggingface.co/charactr/vocos-encodec-24khz).
Repository: godot
Issue: Image::compress / compress_with_channels unreliable, not exportable
Labels: documentation,topic:export

### Godot version

Godot 4.1.1-stable

### System information

Windows 11/64, RTX 3070, Vulkan

### Issue description

I'm building Terrain3D and ran into problems with `Image::compress()` and `Image::compress_from_channels()` which don't work on export and are unreliable in the editor.

```
#define COLOR_RB Color(1.0f, 0.0f, 1.0f, 1.0f)
#define COLOR_NORMAL Color(0.5f, 0.5f, 1.0f, 1.0f)

Ref<Image> Terrain3DStorage::get_filled_image(Vector2i p_size, Color p_color, bool p_create_mipmaps, Image::Format p_format) {
	Ref<Image> img = Image::create(p_size.x, p_size.y, p_create_mipmaps, p_format);
	img->fill(p_color);
	if (p_create_mipmaps) {
		img->generate_mipmaps();
	}
	return img;
}

img = get_filled_image(albedo_size, COLOR_RB, true, Image::FORMAT_RGBA8);
img->compress(Image::COMPRESS_S3TC, Image::COMPRESS_SOURCE_SRGB);
// img->get_format() 
// In editor: returns 19 FORMAT_DXT5, expected
// On export: returns 5 FORMAT_RGBA8, not expected **

img = get_filled_image(normal_size, COLOR_NORMAL, true, Image::FORMAT_RGBA8);
img->compress(Image::COMPRESS_S3TC, Image::COMPRESS_SOURCE_SRGB);
// img->get_format()
// In editor: returns 17 FORMAT_DXT1, not expected **
// On export: returns 5 FORMAT_RGBA8, not expected **
```

We transitioned to
```
img->compress_from_channels(Image::COMPRESS_S3TC, Image::USED_CHANNELS_RGBA);
// In editor: 19 FORMAT_DXT5, expected
// On export: returns 5 FORMAT_RGBA8, not expected **

img->compress_from_channels(Image::COMPRESS_S3TC, Image::USED_CHANNELS_RGBA);
// In editor: 19 FORMAT_DXT5, expected
// On export: returns 5 FORMAT_RGBA8, not expected **
```

With either function, debug exports give this error message:
```
ERROR: Condition "!_image_compress_bc_func" is true. Returning: ERR_UNAVAILABLE
   at: compress_from_channels (core/io/image.cpp:2637)
```

I'm using the default export options:
![image](https://github.com/godotengine/godot/assets/632766/6db1211d-9b60-467c-a7ab-895955ba0e6b)



Godot 4.1.1-stable
Terrain3D 0.8.1+ a69eff


### Steps to reproduce

See above

### Minimal reproduction project

n/a
Repository: go
Issue: proposal: x/oauth2: support Refresh Token Request with Custom Parameters
Labels: Proposal

Migrated from https://github.com/golang/oauth2/issues/521, refs https://github.com/golang/go/issues/56402#issuecomment-1639698959

We'd like to be able to add custom parameters to the Refresh Token Request provided by the [configuration client](https://pkg.go.dev/golang.org/x/oauth2#Config.Client).

**Proposed solution:**

Add optional parameters to `oauth2.Config.TokenSource()` similar to `SetAuthURLParam`. This pattern could later be extended for headers if necessary.

**Proposed API:**

```go
type TokenSourceOption func(*reuseTokenSource)
func (c *Config) TokenSource(ctx context.Context, t *Token, opts ...TokenSourceOption) TokenSource
```

Would be happy to try a CL.

**Consequence of not implementing:**

Custom unmarshaling of `oauth2.Token` (see https://github.com/golang/go/issues/61417) or custom token refreshers (see https://github.com/evcc-io/evcc/blob/master/util/oauth/tokensource.go#L12)

**Alternatives:**

To some extend https://github.com/golang/go/issues/61417 but still at cost of additional code.
Repository: go
Issue: os/signal: TestTerminalSignal failures with `subprogram failed: exit status 1` after `Waiting for exit...`
Labels: OS-Darwin,NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "os/signal" && test == "TestTerminalSignal" && `Waiting for exit` && `subprogram failed: exit status 1`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/33e2497909ced352ea7f049fb63ee05f671ebf70)):

    error running second subprocess: <nil>
    --- FAIL: TestTerminalSignal (90.76s)
        signal_cgo_test.go:186: Sending ^Z...
        signal_cgo_test.go:198: Sending SIGCONT...
        signal_cgo_test.go:211: Waiting for exit...
        signal_cgo_test.go:214: subprogram failed: exit status 1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: Web-Dev-For-Beginners
Issue: Can't access web-dev-beginer
Labels: no-issue-activity

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.
Repository: Web-Dev-For-Beginners
Issue: Bug Web-Dev-For-Beginners
Labels: no-issue-activity

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - Browser [e.g. stock browser, safari]
 - Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Latent cache
Labels: enhancement

### 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 ?

when choose VAE as x/y/z variable and "keep seeds -1" is disabled, webui could generate only one latent and use different VAEs to decode this image, instead of simply generating images for each VAE, wasting lots of time generating same latent.

### Proposed workflow

The process below is just an example:
1. Go to scripts and choose xyz plot
2. set x type 'VAE' and provide with 3 different values, and keep y and z 'none'
3. click 'generate'
4. what webui does now: generate 3 images (maybe use 60 steps in default setting) using a seed.
5. what expect to do: generate only one latent (maybe only need 20 steps in default setting), and use 3 VAEs to decode this latent. We can also get 3 images which are the same except for VAE but the time cost decrease to about only 1/3.

### Additional information

_No response_
Repository: go
Issue: x/vulndb: create tool to display # importers of a module's packages to support vuln triage
Labels: vulncheck or vulndb

Create a CLI tool (or similar) which can determine the number of importers of a Go module's importable packages. (E.g., as a start, display the package with the most importers).
Repository: next.js
Issue: Font Source_Sans_Pro not supported on version 13.4.12, but supported on 13.4.2
Labels: bug,Font (next/font),linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Next versions 13.4.2 and 13.4.12
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Font optimization (next/font)

### Link to the code that reproduces this issue or a replay of the bug

doesn't apply

### To Reproduce

This is the path of the file that contains the font export`/node_modules/next/dist/compiled/@next/font/dist/google/index`

### Describe the Bug

The named export Source_Sans_Pro doesn't exist anymore on version 13.4.12

I use next@13.4.2. Since I use the font Source_Sans_Pro, the update to 13.4.12 implies a breaking change for me. Shouldn't the last digit of the versioning mean non-breaking changes?


### Expected Behavior

`/node_modules/next/dist/compiled/@next/font/dist/google/index` Shouldn't stop having the font on a non-breaking version change

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

<sub>[NEXT-1480](https://linear.app/vercel/issue/NEXT-1480/font-source-sans-pro-not-supported-on-version-13412-but-supported-on)</sub>
Repository: deno
Issue: Support deno run resolving bare specifiers with import map
Labels: suggestion

### Proposal

Support `deno run` resolving bare specifiers with the import map.

For example:

If the `deno.json` file contains an import map that maps `lume/` to `https://deno.land/x/lume@v1.18.1/`:

```json
{
  "imports": {
    "lume/": "https://deno.land/x/lume@v1.18.1/"
  }
}
```

It be possible to reference the bare specifier with deno run:

```
deno run lume/cli.ts
```

Instead of:

```
deno run https://deno.land/x/lume@v1.18.1/cli.ts
```

### Why

Today bare specifiers are interpreted inconsistently by `deno run` and an `import`. `import`s with bare specifiers interpret them using an import map and relative paths must be prefixed with `./`. `deno run` however treats a bare specifier as a relative path.

This prevents developers from conveniently referencing versions in an import map in deno run commands, or in deno tasks. It is easy to accidentally use the wrong version when running a tool with deno run when the project is configured for a different version.

It is possible to work around this by piping an import to the deno run command, but this is not intuitive. For example:

```
echo "import 'lume/cli.ts'" | deno run -
```
Repository: flutter
Issue: Tickers, Timers, Tests, and FPS
Labels: a: tests,framework,P2,team-framework,triaged-framework

In Flutter widgets, `Timer`s are a problem because they aren't controlled by Flutter's test runner. Instead, Flutter provides `Ticker`s, which hook into the Flutter pipeline, and therefore they can be controlled in tests. Generally speaking, any `Timer` behavior will produce unpredictable test results and therefore shouldn't be used in widgets. 

However, there seems to be an issue with relying on `Ticker`s for time tracking, too. Namely, `Ticker`s seem to continuously schedule new frames, and force Flutter into a full FPS execution, which, at best, is a big waste of device energy.

Here's a real-world example. In Super Editor, we flash a text caret on and off every 0.5 seconds. To do this, we could use a `Timer`, but as mentioned above, `Timer`s don't play well with tests. Therefore, we register a `Ticker` and observe the passage of time. When we see 0.5 seconds pass, we show or hide the caret.

```dart
void _onTick(Duration elapsedTime) {
    if (elapsedTime - _lastBlinkTime >= _flashPeriod) {
      _blink();
      _lastBlinkTime = elapsedTime;
    }
  }
```

Apparently, by using a `Ticker`, Flutter constantly schedules frames, yielding 58 unnecessary frames per second. Moreover, this constant frame scheduling prevents mobile devices from entering low-frame-rate mode.

Is there a canonical solution to this `Ticker` problem? If not, I think Flutter needs a way to handle the passage of time, which integrates with tests, and also doesn't schedule unnecessary frames.
Repository: pytorch
Issue: Potential lack of CI testing on older NVIDIA GPU
Labels: module: ci,triaged

## Issue description

Recently, we observe flaky issue with AWS G3 runner using Tesla M60 GPU https://github.com/pytorch/pytorch/issues/105721#event-9928505839.  The issue was mitigated by moving the job to the newer G5 runner using A10G.  Because the actual root cause is unclear, running on G5 could hide actual issues if it turns out to be something on PyTorch.  So this issue is here to track any future investigations on this area.

Here is an example failure where `nvidia-smi` hangs:

* [linux-bionic-cuda11.8-py3.9-gcc7 / test (multigpu, 1, 1, linux.16xlarge.nvidia.gpu)](https://hud.pytorch.org/pytorch/pytorch/commit/33b855e9069ddc98399c0dfd362f18df9503b66f)

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: vscode
Issue: Accessible diff viewer close button is not vertically centered
Labels: feature-request,polish,diff-editor

1. Open a diff editor 
2. Shift+F7 or use Open Accessible Diff Viewer from the editor title overflow menu 
<img width="269" alt="image" src="https://github.com/microsoft/vscode/assets/30305945/540948f4-9c12-4604-9d71-2efd3cf69198">

3. :bug: the x to close is not vertically centered 
![image](https://github.com/microsoft/vscode/assets/30305945/033e52ec-e16a-449c-870e-9a5bab5c95a5)
Repository: vscode
Issue: Navigation in notebook output matches always move the viewport
Labels: bug,papercut :drop_of_blood:,notebook-find


Type: <b>Bug</b>

* Open endgame.github-issues notebook
* Run all
* Now search for a keyword that has multiple matches in outputs
* Press enter to navigate
* Instead of revealing the match into view only when necessary, it moves the match to the center of the view every time, it's very annoying compared to how editor handles matches navigation

VS Code version: Code - Insiders 1.81.0-insider (Universal) (862fa13002d8018c328931ee1edccfd4ca76447d, 2023-07-26T05:36:43.574Z)
OS version: Darwin x64 22.5.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|3, 3, 3|
|Memory (System)|32.00GB (0.45GB free)|
|Process Argv|--enable-proposed-api ms-vscode.vscode-notebook-history --enable-proposed-api vscode.notebook-editing --enable-proposed-api vscode.vscode-test-resolver --enable-proposed-api donjayamanne.kusto --enable-proposed-api donjayamanne.jupyterpowertools --enable-proposed-api rebornix.better-jupyter-errors --enable-proposed-api rchiodo.jupyter-tools --crash-reporter-id 1a907bbd-fa02-4595-81e0-63e1648afb31|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: vscode
Issue: [themes] mark favorites themes
Labels: feature-request,themes

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
There is only three classes of color themes, dark, light and high contrast. It would be great to have an option to create a custom class such as "Favorites" with ones we choose, showing on top or in the order we set.
For example, a custom class with 
Dark Modern, 
Community Material Theme Darker High Contrast, 
Material Theme Darker High Contrast
under the name of "Dark Themes" would be great. 
settings.json config parameters can be set as follows:
"""
colorTheme.customClasses = [
    {"Dark Themes": [
        "Dark Modern",
        "Community Material Theme Darker High Contrast",
        "Material Theme Darker High Contrast",
    ]
]
"""
Thanks for your time and patience to read through this request.