sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: Please report XTVERSION in response to CSI > 0 q or set TERM to something other than xterm (or both)
Labels: Issue-Feature,Needs-Triage,Needs-Tag-Fix

### Description of the new feature

Ideally I think Windows Terminal would set the environment variable `TERM` to a unique value and also update the existing terminfo databases. However, I understand that the intermediate state that creates where many programs don't recognize the new terminal type is undesirable.

So in the meantime, can Windows Terminal report XTVERSION? From [ctlseqs](https://invisible-island.net/xterm/ctlseqs/ctlseqs.html):
```
CSI > Ps q
            Ps = 0  ⇒  Report xterm name and version (XTVERSION).
          The response is a DSR sequence identifying the version:
            DCS > | text ST
```

This escape sequence is pretty widely supported to send a unique string that identifies the name and version of a terminal. Off the top of my head, VTE-based terminals (such as GNOME Terminal), Konsole, iTerm2, WezTerm, Contour, and kitty all support this escape sequence.

Context: I am currently drafting up a patch to Emacs that will rely either `TERM` or XTVERSION to determine if xterm-mouse-mode is safe to be enabled by default. Emacs wants to see support fo OSC52 copy, bracketed paste, DECSET1000, and DECSET1003 at a minimum and checking XTVERSION or `TERM` is the only way I have to identify if these escape sequences are supported. Also see [Emacs discussion thread](https://debbugs.gnu.org/cgi/bugreport.cgi?bug=74833).

### Proposed technical implementation details

_No response_
Repository: godot
Issue: Cannot declare virtual method with enum from own class
Labels: bug,topic:core,usability

### Tested versions

v4.4.dev7
v4.3.stable
v4.2.2.stable
v4.1.stable


### System information

Windows 11 24H2

### Issue description

Attempting to setup a class which defines a virtual method for an enum setup in that class. That is, before `VARIANT_ENUM_CAST` gets setup. Because the logic in the virtual method is declared immediately, any generic calls are established before this crucial step. In this case, it's `PtrToArg` that's setup too early.


### Steps to reproduce

Script excerpt:
```cpp
class Logger : public RefCounted {
	GDCLASS(Logger, RefCounted);

protected:
	static void _bind_methods();

public:
	enum class LogLevel {
		DEBUG,
		INFO,
		WARN,
		ERROR,
		FATAL,
		MAX,
	};

	virtual void log(const String &p_content, LogLevel p_level, const TypedDictionary<String, Variant> &p_context = {}) = 0;

#define _COMMA ,
	GDVIRTUAL3(_log, String, LogLevel, TypedDictionary<String _COMMA Variant>);
#undef _COMMA
};

VARIANT_ENUM_CAST(Logger::LogLevel);
```

Error output:
```
Use of undeclared identifier 'argval2'; did you mean 'argval1'? clang(undeclared_var_use_suggest)
Expected ';' after expression clang(expected_semi_after_expr)
No member named 'EncodeT' in 'PtrToArg<Logger::LogLevel>' clang(no_member)
Use of undeclared identifier 'argval2' clang(undeclared_var_use)
Implicit instantiation of undefined template 'GetTypeInfo<Logger::LogLevel>' clang(template_instantiate_undefined)
type_info.h(62, 8): Template is declared here
```

### Minimal reproduction project (MRP)

N/A
Repository: pytorch
Issue: cuDNN version is not detected correctly in PyTorch
Labels: module: cudnn,module: cuda,triaged

### 🐛 Describe the bug

I am experiencing issues with PyTorch not detecting the correct version of cuDNN. Here’s the setup:

I installed Nightly PyTorch 2.6 using the following command:

```python 
pip3 install --pre torch --index-url https://download.pytorch.org/whl/nightly/cu118
```
I installed also the latest supported version of cuDNN for CUDA 11.8, which is cuDNN 9.6. see: https://docs.nvidia.com/deeplearning/cudnn/latest/reference/support-matrix.html

When running the following code to check the cuDNN version:
```python
import torch
print(f"CUDNN version: {torch.backends.cudnn.version()}")
```
the returned version is 90100 (cuDNN 9.1), but it should be 90600 (cuDNN 9.6).

### Versions

PyTorch version: 2.6.0.dev20241231+cu118
Is debug build: False
CUDA used to build PyTorch: 11.8
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 11 Home (10.0.22631 64 bits)
GCC version: Could not collect
Clang version: Could not collect
CMake version: Could not collect
Libc version: N/A

Python version: 3.12.8 | packaged by conda-forge | (main, Dec  5 2024, 14:06:27) [MSC v.1942 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-11-10.0.22631-SP0
Is CUDA available: True
CUDA runtime version: 11.8.89

CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce GTX 1650 Ti
Nvidia driver version: 566.36
cuDNN version: C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.8\bin\cudnn_ops64_9.dll
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Name: AMD Ryzen 7 4800H with Radeon Graphics         
Manufacturer: AuthenticAMD
Family: 107
Architecture: 9
ProcessorType: 3
DeviceID: CPU0
CurrentClockSpeed: 2900
MaxClockSpeed: 2900
L2CacheSize: 4096
L2CacheSpeed: None
Revision: 24577

Versions of relevant libraries:
[pip3] flake8==7.1.1
[pip3] mypy==1.14.0
[pip3] mypy_extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] numpydoc==1.8.0
[pip3] torch==2.6.0.dev20241231+cu118
[pip3] torchvision==0.22.0.dev20241230+cu118
[conda] _anaconda_depends         2024.10             py312_mkl_0  
[conda] blas                      1.0                         mkl  
[conda] mkl                       2023.2.0         h6a75c08_49573    conda-forge
[conda] mkl-service               2.4.1           py312h0ad82dd_1    conda-forge
[conda] mkl_fft                   1.3.10          py312h98b3aff_1    conda-forge
[conda] mkl_random                1.2.8           py312hb562361_0    conda-forge
[conda] numpy                     1.26.4          py312hfd52020_0  
[conda] numpy-base                1.26.4          py312h4dde369_0  
[conda] numpydoc                  1.8.0              pyhd8ed1ab_1    conda-forge
[conda] torch                     2.6.0.dev20241231+cu118          pypi_0    pypi
[conda] torchvision               0.22.0.dev20241230+cu118          pypi_0    pypi

cc @csarofeen @ptrblck @xwang233 @eqy @msaroufim
Repository: go
Issue: go/packages: line directives not treatead properly in the exported file
Labels: NeedsInvestigation

Reproducer (using the `x/tools/go/packages` testing API):

```go
func TestReproducer(t *testing.T) {
	exported := packagestest.Export(t, packagestest.Modules, []packagestest.Module{
		{
			Name: "test",
			Files: map[string]any{
				"test.go": `package test; import "test/other"; var _ = other.Test;`,
				"other/file.go": `package other

//line other.go:1:1
var Test int
`,
			},
		},
	})
	t.Cleanup(exported.Cleanup)

	exported.Config.Mode = packages.LoadSyntax
	exported.Config.Fset = token.NewFileSet()
	pkgs, err := packages.Load(exported.Config, "test")
	if err != nil {
		t.Fatal(err)
	}
	packages.PrintErrors(pkgs)

	p := pkgs[0].Imports["test/other"]
	pos := p.Types.Scope().Lookup("Test").Pos()
	t.Log(exported.Config.Fset.Position(pos)) // other.go:4:1
}

```

The `Mode` is set to `packages.LoadSyntax`, thus `go/packages` is going to load `test/other` from the `ExportFile`.

```bash
$ go test ./go/packages/ -run TestReproducer -v
=== RUN   TestReproducer
    (....)
    packages_test.go:3455: other.go:4:1
--- PASS: TestReproducer (0.15s)
```

The file name (`other.go`) comes from the line directive, but the line/col (`4:1`) information does not.

I think that the issue is somewhere in `cmd/go`, while debugging, i saw the same values here (i.e. other.go:4:1):

https://github.com/golang/tools/blob/4f820dbaf9859eaafa01a17d133583f4d8c5a73c/internal/gcimporter/ureader_yes.go#L201-L205
Repository: PowerToys
Issue: Bluetooth widget/floating window that shows battery information
Labels: Needs-Triage

### Description of the new feature / enhancement

A floating window/widget for viewing Bluetooth devices battery percentage.

Windows currently doesn't have the option to open a floating Always-On-Top small window for viewing information about Bluetooth info.
A small floating window could be very nice (and easy) thing to have.
Plus it can notify you when the battery is at a low percentage :)

This is a very basic thing and its sad that windows does not have this already...

### Scenario when this would be used?

Showing the battery info for a Bluetooth headset for example. This could be helpful to know when to plug in the headset and not run out of battery.

### Supporting information

_No response_
Repository: godot
Issue: Android export from android will not update main scene layout unless .godot/exported/... is deleted
Labels: bug,platform:android,topic:editor,topic:export

<!-- Failed to upload "repro-godotatoaexportedcache2.zip" -->
### Tested versions

- Reproducible on:
    - Godot v4.4-dev7 - Android -> Android
    - Godot master 0c45ace151f25de2ca54fe7a46b6f077be32ba6f - Android -> Android
    - Godot master 2582793d408ade0b6ed42f913ae33e7da5fb9184 - Android -> Android
-  Not Reproducible on:
    - Godot 4.4-dev7 - Linux -> Android
    - Godot 4.3-stable - Linux -> Android
    - Godot master 2582793d408ade0b6ed42f913ae33e7da5fb9184 - Linux -> Android
    - Godot 4.3-stable - Linux -> Linux
    - Godot 4.4-dev7 - Linux -> Linux
    - Godot 4.3-stable - Android -> Android (not implemented yet: https://github.com/godotengine/godot/commit/a5897d579bb0af496a18f7430345a67fe27ff0df)



### System information

Godot v4.4.dev7 - Android - Single-window, 1 monitor - Vulkan (Mobile) - integrated Mali-G715 -  (9 threads)
(Google Pixel 8)

### Issue description

It looks like the scene is cached in `.godot/exported/<id>/file_cache` on the first export, which is not updated in subsequent exports....

~~It appears that the desktop editor does not create `.godot/exported/<id>/file_cache` when exporting!?~~

### Steps to reproduce

Create a simple app on the editor in android. Export the app and install (all on the same device 😙🤌) then adjust the main scene layout to something different.. and re-export.

In the MRP you can hide/show the TextRect named `HideMeThenReExport`

It seems like the scripts get updated but the scene contents don't change on the exported app.

Delete `.godot/exported/<id>/file_cache` and then re-export and the scene updates to the new layout.

### Minimal reproduction project (MRP)
[repro-godotatoaexportedcache2.zip](https://github.com/user-attachments/files/18286768/repro-godotatoaexportedcache2.zip)

---
**Bugsquad Edit:** Adding info from #99023

When I export an APK file, it always exports the first exported version.When I delete a folder called exported in the file manager, I can export the new version of the file again. It's just me. My friend is totally fine.And it seems that only the scene files and resource files will not be updated, the script will be updated. Not only did I save it several times, but I even deleted GODOT and tried again, with the same result.
Repository: rust
Issue: RPIT associated type lifetime bound is ignored
Labels: A-lifetimes,A-associated-items,A-impl-trait,C-bug,S-has-mcve,T-types

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
trait Foo<'x> {
    type Out;
    fn foo(self) -> Self::Out;
}

struct Bar;

impl<'x> Foo<'x> for Bar {
    type Out = ();
    fn foo(self) -> Self::Out {
        todo!()
    }
}

fn make_static_foo<'x>(_: &'x ()) -> impl Foo<'x, Out: 'static> {
    Bar
}

fn assert_static<T: 'static>(_: T) {}

fn test() {
    let local = ();
    assert_static(make_static_foo(&local).foo());
}
```

I expect it to compile, but instead it gives the following error:
```
error[E0597]: `local` does not live long enough
  --> src/lib.rs:23:35
   |
22 |     let local = ();
   |         ----- binding `local` declared here
23 |     assert_static(make_static_foo(&local).foo());
   |                   ----------------^^^^^^-
   |                   |               |
   |                   |               borrowed value does not live long enough
   |                   argument requires that `local` is borrowed for `'static`
24 | }
   | - `local` dropped here while still borrowed
```

It looks like the `Out: 'static` bound on `make_static_foo` is just ignored.

The issue sounds similar to #106684, but it is actually the opposite:
In this issue the bound is in the RPIT instead of in the trait definition.


### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.85.0-nightly (7f75bfa1a 2024-12-30)
binary: rustc
commit-hash: 7f75bfa1ad4e9a9d33a179a90603001515e91991
commit-date: 2024-12-30
host: x86_64-unknown-linux-gnu
release: 1.85.0-nightly
LLVM version: 19.1.6
```
Same happens on stable
Repository: godot
Issue: [Godot4.3][iOS Plugin][xcode 16.2] Could not build module 'Foundation' and standard cpp errors for iOS plugin
Labels: platform:ios,topic:plugin,needs testing

### Tested versions

-Reproducible in the 4.3 branch.

### System information

Mac M4 - godot 4.3 - XCode 16.2

### Issue description

I'm trying to build a custom iOS plugin following [the steps here](https://docs.godotengine.org/en/stable/tutorials/platform/ios/ios_plugin.html#creating-an-ios-plugin) using XCode 16.2 and godot 4.3 (branch).

It fails to build the 'Foundation' module as well as the standard cpp classes. See screenshot below.

 <img width="1624" alt="Image" src="https://github.com/user-attachments/assets/2c3542e7-77ae-4222-b762-d46909b56f6f" />


### Steps to reproduce

1. Have XCode 16.2
2. Checkout the [default iOS plugin template](https://github.com/naithar/godot_ios_plugin).
3. Switch godot sub-module to branch `4.3`.
4. build `godot` with `scons platform=ios target=template_debug generate_bundle=yes ios_simulator=yes`
5. Open plugin project
6. Update `Search Header Paths` to new paths (the default ones are outdated).
7. Build the library


### Minimal reproduction project (MRP)

Follow the [official steps](https://docs.godotengine.org/en/stable/tutorials/platform/ios/ios_plugin.html#creating-an-ios-plugin) for creating a plugin using the [default template](https://github.com/naithar/godot_ios_plugin). Only difference is using Godot 4.3 and XCode 16.
Repository: vscode
Issue: VSCode Windows Do Not Restore to Their Original Ubuntu Workspaces After Reboot
Labels: feature-request,linux,workbench-window

When using Ubuntu OS with multiple workspaces (e.g., 4 fixed screens that can be navigated to using the Windows key), applications like Brave Browser restore their windows to the exact workspace they were in before a system shutdown or unexpected closure.  

However, VSCode does not behave the same way. If multiple VSCode windows are open across different Ubuntu workspaces and the system is restarted, all the VSCode windows are restored to the first workspace, instead of returning to their original workspaces.  

This disrupts workflow organization and creates additional overhead for users to manually reassign VSCode windows to the appropriate workspaces.  

### Requested Feature:  
Implement a feature similar to Brave Browser that enables VSCode to remember and restore its windows to the same Ubuntu workspaces they were in before a shutdown or restart.  

### Steps to Reproduce:  
1. Open multiple VSCode windows and place each in a different Ubuntu workspace.  
2. Restart or shut down the system.  
3. After the system restarts, note that all restored VSCode windows appear in the first workspace instead of their original ones.  

### Expected Behavior:  
VSCode windows should restore to the same Ubuntu workspaces they were in before the restart or shutdown.
Repository: terminal
Issue: Implement kitty keyboard protocol
Labels: Needs-Triage,Needs-Tag-Fix

Spec: https://sw.kovidgoyal.net/kitty/keyboard-protocol/

Dup #11509

I just wanted to draw your attention to two new facts:

1) Since the Kitty protocol has [started being supported in iTerm2](https://gitlab.com/gnachman/iterm2/-/issues/10017), we can say that its independent implementation exists on all platforms except Windows. It seems to be gradually becoming a de facto technological standard.

2) A [patch with support for win32-input-mode](https://gitlab.gnome.org/GNOME/vte/-/issues/2601#note_2287197) has been written for the GNOME terminal. If you, like me, are interested in the development of the console applications ecosystem and improving their UX across all platforms, please express your support for its adoption.
Repository: neovim
Issue: presentation mode
Labels: enhancement,plugin,runtime,display,gsoc,options,editor

# Problem

Various filetypes like markdown, latex, and other formats, have a "rendered" form which has a different layout or conceals parts of the text. Currently, this limits how fancy we can render these filetypes; we have to choose between optimizing for editing instead of viewing.

# Expected behavior

Introduce the concept of "presentation mode". This could be a simple flag or variable, which triggers filetype-specific handling.

- Can be easily toggled. Suggested mapping: `z<tab>`, or `<backspace>`, or ...?
    - Disable when entering insert-mode?
- Filetype-specific handling:
    - `text`: "flow" layout (soft-wrap)
    - `markdown`: prettify headings/URLs/lists, "flow" layout (soft-wrap)
    - `help` (vimdoc): prettify headings, "flow" layout (soft-wrap)
- Plugins are also encouraged to handle this mode. E.g. slides
- Set 'conceallevel' ?
- Vim has a `'readonly'` flag and related `:view` command. We could use this to signal "presentation mode"?
    - Problem: 'readonly' is buffer-local, whereas presentation mode is presumably window-local...
Repository: flutter
Issue: Remove or Continuously Update Flutter's GitHub Releases to Avoid Unnecessary Public Misunderstanding
Labels: c: proposal,team-release

### Use case


![2025-01-02 085406](https://github.com/user-attachments/assets/226481b8-84cf-4b87-a714-55ad0e21efce)
The latest version is still showing as 2023, which creates a false impression that 'Flutter is dead' for those who only take a quick glance. Through a snowball effect, this misconception spreads to more people, and I have indeed seen quite a few people who hold this belief

### Proposal

Remove or Continuously Update Releases to Avoid Unnecessary Public Misconceptions
Repository: PowerToys
Issue: Keyboard Manager not allowing to SELECT combination of keys
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

When Remapping a key, the **Select** button, to define the remap, will only accept one key at a time.  You cannot press two keys ( **Alt (Right)** + **X**) to then define the remapping.
1. Open Remap keys
2. Click on **Add key remapping**
3. Click on **Select** OR 3.a. Use drop-down list and choose **Alt (Right)**
4. Select keys on the keyboard, i.e. **Alt (Right)** and **X**  OR 4.a. No other drop-down list field is shown to define a key combination



### ✔️ Expected Behavior

Users should be able to click **Select** and tap on the keys they want to combine to set up the remapping.  

### ❌ Actual Behavior

Only one key will be selected when the user presses **Alt (Right)** and **X** keys to define the **Select** keys.  
I also tried this by pressing the two keys separately and simultaneously with no success.

In contrast, the Select on the To Send column works as expected (i.e. can select multiple keys to define a combination)

### Other Software

_No response_
Repository: kubernetes
Issue: async API call for NominatedNodeName and pod condition
Labels: sig/scheduling,kind/feature,needs-triage

Follow up: https://github.com/kubernetes/kubernetes/issues/126858#issuecomment-2344284869
/cc @JasonChen57 @kubernetes/sig-scheduling-leads @macsko @dom4ha 
/assign
/kind feature
/sig scheduling

The scope of [KEP-4832](https://github.com/kubernetes/enhancements/issues/4832) is currently only the API calls made within the preemption plugin, which is for victim Pod deletion.
But, there's another API call involved to patch the unscheduled pod with nominated node name, status etc, which we may also want to do asynchronously.
https://github.com/kubernetes/kubernetes/blob/c3ebd95c837a21c0c79ab64721c28bba44331bf9/pkg/scheduler/schedule_one.go#L1100-L1107

We can see a potential perf improvement with scheduler-perf with a simple PoC, and decide whether we really want to do it or not. 

Also, it has a broader blast radius since it impacts _all_ unschedulable pods, and hence may not be allowed to just add into the scope of KEP-4832...? I'm not sure.
Repository: transformers
Issue: Request for a Vision Transformer Model for Digital Image Segmentation
Labels: New model

### Model description

I would like to request the addition of a Vision Transformer (ViT) model specifically fine-tuned for digital image segmentation tasks. The model should leverage transformer-based architecture to effectively capture spatial relationships within images, improving performance in tasks such as medical image analysis, satellite image segmentation, or autonomous driving.

The Vision Transformer architecture has proven to be highly effective for various vision tasks by using self-attention mechanisms to capture long-range dependencies in images. This model would be particularly valuable for tasks requiring pixel-level classification, where traditional convolutional neural networks (CNNs) often struggle to capture global features effectively.

The ViT model should include the following key features:

- Pretrained on a large, diverse image segmentation dataset.
- Fine-tuned for pixel-level classification tasks such as medical image segmentation or semantic segmentation of everyday objects.
- Support for standard ViT variants such as ViT-B (Base), ViT-L (Large), and ViT-H (Huge) depending on the task's computational budget.
- Open-source weights and implementation.

### Open source status

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

### Provide useful links for the implementation

@amyeroberts, @qubvel
Repository: svelte
Issue: window onload does not fire up in chrome
Labels: needs discussion

### Describe the bug

When i use `<svelte:window onload={onLoad}>` it does not work in chrome (And also not in svelte.dev environments), but it does work in Firefox.

After talking with chatgpt the fix was:

```

onMount(() => {
    if (document.readyState === 'complete') {
        onLoad();
    } else {
        // Otherwise, wait for the load event
        window.addEventListener('load', onLoad, { once: true });
    }
});

function onLoad(_event) {
    console.debug('loaded window.');
    isAppLoaded = true;
}


```
According to chatgpt onload event may fire before the sveltecode which attaches the eventhandler executes.

I am not a big expert in WebDev, but if I understand this correctly, it is not only a svelt issue. It would be nice if the <svelte window:onload> had already the fix above implmeneted, if that is even the correct way to handle that.

### Reproduction

https://svelte.dev/playground/0f493cd43f36479fb6c907fa08d16ed3?version=5.16.0

Currently, it is successfully reproduces in the online environemnt of svelte.dev, but due to the nature of the issue (race condition), there might be a chance it won't reproduce in the future.

### Logs

_No response_

### System Info

```shell
Independant Scripts:
  Chromium (131.0.2903.99)    

Internet Explorer: 11.0.26100.1882
  npmPackages:
    svelte: ^5.0.0 => 5.16.0
```


### Severity

annoyance