sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: langchain
Issue: ModuleNotFoundError: No module named 'rank_llm.rerank.zephyr_reranker' (update of rank_llm.rerank ->  rank_llm.rerank.listwise.zephyr_reranker)
Labels: 🤖:bug,stale

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code


 `from rank_llm.rerank.listwise.zephyr_reranker import ZephyrReranker`
🧨🧨 `from rank_llm.rerank.zephyr_reranker import ZephyrReranker`


### Error Message and Stack Trace (if applicable)

ModuleNotFoundError: No module named 'rank_llm.rerank.zephyr_reranker'

### Description

I think the `rank_llm` updated version changed the package locations:

worked: `from rank_llm.rerank.listwise.zephyr_reranker import ZephyrReranker`
not worked: `from rank_llm.rerank.zephyr_reranker import ZephyrReranker`


### System Info

up2date langchain
Repository: PowerToys
Issue: Add a Highlight Border When Switching Windows
Labels: Needs-Triage

### Description of the new feature / enhancement

When working on a large monitor with 3+ windows visible at a time, it can often be confusing to know which window is in focus, or which window you've instantly alt + tabbed to.
My suggestion is to add an feature that adds a 1px blue border (or whatever) that fades out over 2 seconds or so, to whichever window becomes activated. This way, you will instantly know which one you've selected.

Additionally - although a bit different/more technical, I think it could also be really useful to be able to proximity-switch to a window based on FancyZones zones. So basically you can "move" the active zone, which would function just like moving the active window around using hotkeys, except instead of moving the window, you're moving the "active zone", and whichever window was last accessed in the zone you land on, becomes active.

### Scenario when this would be used?

This would be especially useful for large monitors where you quickly want to switch between windows. While the alt+tab windows overview is of course very useful, this requires you to "study" the windows for a second in order to choose the right one - meaning, if you simply quick swap with alt + tab, it's usually almost impossible to know which window you've now switched to, if it's one of the windows that are already visible and for instance, in another FancyZones zone.

Additionally, especially with browsers, you'll often have multiple browsers open with very similar content on them, making it hard to distinguish which one you want.

For instance, let's say you have your editor in one zone, and two github repos open in their own windows in other zones. Visually, on your monitor, you know which window you want to tab to, but with alt + tab, the window previews will look very similar, and I often find myself selecting the wrong window, and having to hit some other key to see which one I'm in (eg. up/down arrow key to see which one scrolls).

I think the border glow would help with this, but switching active zones would be even better.

### Supporting information

_No response_
Repository: godot
Issue: NodePath property targeting breaks when the targets script is overridden in an inherited scene.
Labels: bug,topic:editor

### Tested versions

Tested in 4.4-dev2_mono_win64 and 4.3-stable_mono_win64

### System information

Godot v4.4.dev2.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4080 (NVIDIA; 31.0.15.4633) - AMD Ryzen 7 5800X 8-Core Processor (16 Threads)

### Issue description

When the target of an exported NodePath property has its script overridden in an inherited scene, the NodePath breaks and throws a ObjectDisposedException.

### Steps to reproduce

To reproduce this bug, one needs a BaseScene, an InheritedScene (created via "New Inherited Scene" of the BaseScene), a BaseScript, a OtherScript and finally one ScriptWithExport with one export of the type Node.

The BaseScene looks as follows:
BaseScene (BaseScript)
+ScriptWithExport (Exported variable Target targets BaseScene)

The InheritedScene looks like this:
InheritedScene (OtherScript)
+ScriptWithExport (Exported variable Target targets InheritedScene)

Inside the _Ready function of the ScriptWithExport function add one line which prints the Target.

While the BaseScene works as expected, the InheritedScene will throw an ObjectDisposedException. Replacing OtherScript with BaseScript in the Inherited Scene, will result in a working condition again.

The targeted node does not have to be the root node, the same error can be reproduced when any node has its script overridden and is the target of an exported NodePath property.



### Minimal reproduction project (MRP)

[minimal-repro-inheritance.zip](https://github.com/user-attachments/files/17188270/minimal-repro-inheritance.zip)
Repository: PowerToys
Issue: Different Results in OpenAI Playground vs requests sent to API from Advanced Paste
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Advanced Paste

### Steps to reproduce

Adding a custom action with very specific prompt gives a wrong result, where trying the same prompt in Playground gives the correct result. Using gpt-3.5-turbo in Playground so it is the same as Advanced paste.
Example prompt:
"0099-0ac8-0084"
Strip dividers ":", "-", ".". Strip "0099". Divide to 4 octets with dots. Convert octets to dec.

### ✔️ Expected Behavior

10.200.0.132


### ❌ Actual Behavior

172.200.0.132

### Other Software

_No response_
Repository: svelte
Issue: Own TS types for types of input elements
Labels: types / typescript

### Describe the problem

Now there is only a single type [HTMLInputAttributes](https://github.com/sveltejs/svelte/blob/svelte%405.0.0-next.260/packages/svelte/elements.d.ts#L1036) for all input elements and there is e.g. the library `flowbite-svelte` which uses this type to [extend](https://github.com/sveltejs/svelte/blob/svelte%405.0.0-next.260/packages/svelte/elements.d.ts#L1036) the props of a component with it. The advantage is that the maintainers don't have to implement each prop themselves but it comes with the disadvantage that the component has more props than it should have.

### Describe the proposed solution

It would be nice to have types like for example `HTMLInputRadioAttributes` which are specific for one type of input element. Then libraries could extend the props of their components with these types.

### Importance

nice to have
Repository: flutter
Issue: [Semantics] Add support for setting the heading level on iOS and macOS
Labels: c: new feature,platform-ios,a: accessibility,platform-mac,c: proposal,P2,team-accessibility,triaged-accessibility

### Use case

This is a follow-up of closed #97894.
iOS and macOS platforms support [AccessibilityHeadingLevel](https://developer.apple.com/documentation/swiftui/accessibilityheadinglevel) which is an equivalent of [ARIA: heading role](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/heading_role) on web.
iOS support was mentioned by both the OP and in the comment: https://github.com/flutter/flutter/issues/97894#issuecomment-2150050231 but the related PR #41435 added the heading level support for the web only.

Different heading levels can speed up the navigation in case of VoiceOver users. They can quickly navigate between subsequent headings (either any or at the same level only) using the keyboard shortcuts: https://support.apple.com/guide/voiceover/search-commands-cpvokys08/mac

### Proposal

Required changes are analogous to those made in https://github.com/flutter/engine/pull/41435 for web.
Here is how to set the heading level: https://developer.apple.com/documentation/swiftui/view/accessibilityheading(_:)

iOS/macOS also have 6 heading levels (from 1 to 6) like web. The value of `0` can probably be mapped to [unspecified](https://developer.apple.com/documentation/swiftui/accessibilityheadinglevel/unspecified).
Repository: pytorch
Issue: Add Mcdropout layer
Labels: module: nn,triaged

### 🚀 The feature, motivation and pitch

I am working with MCDropout, and find the current workflow in pytorch suboptimal and misleading. The current way to enable Dropout at evaluation time to perform MCDropout (https://arxiv.org/pdf/1506.02142) is to set all the Dropout Layers to training mode, which is in my opinion misleading, since you are not training at that point. 
My implementation would be to set a second flag `mcdropout` that enables to use the Layer with dropout always turned on, so that one does not need to loop over the layers, maintaining a clearer and cleaner code structure.

This is my suggestion:
```
class MCDropout(_DropoutNd):
    """
    Implementation of MCDropout to the torch dropout layer.
    This adds a mcdropout flag, which turns dropout always on in training and
    evaluation mode.

    Args:
        p : probability of an element to be zeroed. Default: 0.5
        mcdropout: if True, will always perform dropout
        inplace : if True, will perform dropout in-place
    """
    def __init__(
        self, p: float = 0.5, mcdropout: bool = True, inplace: bool = False
    ) -> None:
        super().__init__(p, inplace)
        self.mcdroput = mcdropout

    def forward(self, input: torch.Tensor) -> torch.Tensor:
        return torch.nn.functional.dropout(
            input, self.p, self.training or self.mcdropout, self.inplace
        )
```

The change adds a parameter `mcdropout` to the Dropout layer, and returns as a condition to use dropout or not `self.training or self.mcdropout`, thus avoiding the need to go over all the layers and turn the training mode on. This also enables to set only some layers to MCDropout layers in an easier way.

### Alternatives

Currently to use mcdropout one has to go over all the modules in the model and set them to training mode.
```def enable_dropout(model):
    """ Function to enable the dropout layers during test-time """
    for m in model.modules():
        if m.__class__.__name__.startswith('Dropout'):
            m.train()
```

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: TypeScript
Issue: A new generic type can be used for file path completion(intellisense)
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

"path intellisense","path completion","asset path completion"

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Add a tool generics so that some function parameters can enable file path type hints

some assets in `../assets`

```ts
function getImageUrl(name:T<"../assets">) {
...
return ...
}

getImageUrl("// intellisense
```

### 📃 Motivating Example

Enable custom file path completion through generics


### 💻 Use Cases

1. What do you want to use this for?

When I used [vite static resource introduction](https://vitejs.dev/guide/assets.html#new-url-url-import-meta-url), I used a function to wrap it, but the function parameters could not achieve type hints like `import`.

the function like:

```ts
function getImageUrl(name:string) { // lost file intellisense
  return new URL(`./dir/${name}.png`, import.meta.url).href
}
```
2. What shortcomings exist with current approaches?

Only `import` statements support path completion and cannot be customized

3. What workarounds are you using in the meantime?

i make a vscode extension
Repository: PowerToys
Issue: Remapped key in client does BOTH actions on the remote
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Just got new Win 11 laptop and found out about Power Toys and it's keyboard remapping feature. I've enabled remapping Caps Lock -> Backspace, Scroll Lock -> Caps Lock and connected to the remote running the windows 10. Tried using remapped key but realised that BOTH original and remap are sent to/executed on remote. Most remote settings on both ends are defaults, I can't remember fiddling with them and the relevant client side settings are as follows: 

<img width="291" alt="image" src="https://github.com/user-attachments/assets/25dae5de-f2a5-4850-b98c-aaa94e73375d">

Remote host has the same remapping but done in the registry.


### ✔️ Expected Behavior

Only remapped key to be send to the remote, or at the very least the original one.

### ❌ Actual Behavior

BOTH original and remapped keys are sent

### Other Software

Remote desktop connection
Repository: vscode
Issue: Terminal seems to flicker more than ever
Labels: bug,terminal-rendering

I feel that the terminal flickers more when I resize it, not sure it ever did flicker so much actually:

![Image](https://github.com/user-attachments/assets/0f934c0c-e1da-4cd8-bf2b-9f31ed541919)

Did something change in the past weeks?

My terminal related settings:

```json
"terminal.integrated.fontFamily": "Menlo",
    "terminal.integrated.fontSize": 13,
    "terminal.integrated.lineHeight": 1.4,
    "terminal.integrated.windowsEnableConpty": false,
    "terminal.integrated.showExitAlert": false,
    "terminal.integrated.tabs.enabled": true,
    "terminal.integrated.shellIntegration.enabled": true,
    "terminal.integrated.stickyScroll.enabled": false,
    "terminal.integrated.commandsToSkipShell": [
        "workbench.action.openPreviousEditorFromHistory",
        "workbench.action.startTerminalSpeechToText",
		"workbench.action.stopTerminalSpeechToText"
    ],
    "terminal.integrated.initialHint": false,
```
Repository: electron
Issue: [Bug]: Unicode console output on Windows is still problematic
Labels: platform/windows,bug :beetle:,has-repro-gist,32-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

32.1.2

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 10 Pro 22H2

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

When logging Unicode strings to the console in an Electron application on Windows, the output should correctly display the Unicode characters.

### Actual Behavior

When running an Electron application on Windows, `console.log` statements containing Unicode strings produce gibberish or unreadable characters in the console output.

To reproduce this issue, you could add the following lines to the beginning of your main process script:

```javascript
console.log('Привет');
console.log('你好');
console.log('こんにちは');
console.log('مرحبا');
console.log('Γειά σου');
```

Instead of displaying the correct Unicode characters, the console output appears as follows:
![image](https://github.com/user-attachments/assets/c4c09678-4e26-48c9-bf80-5ac59c76ea10)


### Testcase Gist URL

_No response_

### Additional Information

This issue is related to the previously closed issue #5761 (https://github.com/electron/electron/issues/5761). Despite the original issue being closed, the problem still persists. The only known workaround is to run `chcp 65001` every time before running an Electron app.
Repository: excalidraw
Issue: Add support of Ukrainian (or Cyrillic in general) language for Lilita One and  Comic Shanns fonts
Labels: font

Please, add Ukrainian language for following fonts:

- Lilita One
- Comic Shanns

<img width="866" alt="image" src="https://github.com/user-attachments/assets/b017e70d-3c35-4565-bfc4-228fc07bf3b7">
<img width="848" alt="image" src="https://github.com/user-attachments/assets/9cc61510-c72c-48b2-b1a3-ccab78869858">
Repository: pytorch
Issue: BCE loss mps device
Labels: triaged,module: correctness (silent),module: mps

### 🐛 Describe the bug

I have a problem training a model with the BCE loss using mps device. The model uses a linear layer to predict a the sign of a real value number (two classes). When I train it in cpu everything is fine, but when i pass to mps the prediction degenerates and predicts always the same "class" for all the training points.

### Versions

Collecting environment information...
PyTorch version: 2.3.0.dev20240229
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.6.1 (arm64)
GCC version: Could not collect
Clang version: Could not collect
CMake version: version 3.29.2
Libc version: N/A

Python version: 3.12.4 | packaged by conda-forge | (main, Jun 17 2024, 10:13:44) [Clang 16.0.6 ] (64-bit runtime)
Python platform: macOS-14.6.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M3 Max

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.3.0.dev20240229
[pip3] torchaudio==2.2.0.dev20240229
[pip3] torchsummary==1.5.1
[pip3] torchvision==0.18.0.dev20240229
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] torch                     2.3.0.dev20240229          pypi_0    pypi
[conda] torchaudio                2.2.0.dev20240229          pypi_0    pypi
[conda] torchsummary              1.5.1                    pypi_0    pypi
[conda] torchvision               0.18.0.dev20240229          pypi_0    pypi

cc @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen
Repository: neovim
Issue: `gq` fails on empty file with `E20: Mark not set`
Labels: bug-vim,marks,normal-mode

### Problem

Formatting with `gq` and `formatprg` fails on empty file (general new buffer) with error `E20: Mark not set`.

### Steps to reproduce

1. nvim --clean foo
2. `:set formatprg=fmt`
3. type `gqG`
4. command fails with `E20: Mark not set`

tested with these `formatprg` values:
- `fmt`
- `jq`
- `prettier --parser json`

> `formatexpr` seems to be fine. tested with `xmlformat#Format()`, `v:lua.vim.lsp.formatexpr()` and `v:lua.require'conform'.formatexpr()`.

> `:%!fmt` is also fine.

### Expected behavior

`gq` command on empty file should not fail
or print more meaningful error message.

### Nvim version (nvim -v)

v0.11.0-dev-862+gdf915f3af

### Vim (not Nvim) behaves the same?

yes, vim 8.2

### Operating system/version

ubuntu 22.04 (aarch64)

### Terminal name/version

blink shell

### $TERM environment variable

xterm-256color

### Installation

build from repo
Repository: vscode
Issue: Inconsistent button order between editor and panel
Labels: workbench-tabs,under-discussion,layout

* open an editor (no tabs)
* open chat view in secondary sidebad
* the overflow (...) and close (X) commands are swapped

IMO the editor does this rignt

<img width="1069" alt="Screenshot 2024-09-30 at 15 56 31" src="https://github.com/user-attachments/assets/40817e6b-e6c5-45d8-b146-d09e2c6c8b7d">
Repository: go
Issue: proposal: cmd/go: `-json` flag for `go version -m`
Labels: Proposal,NeedsInvestigation,FeatureRequest,GoCommand,Proposal-FinalCommentPeriod

```
$ go version -m -json ~/go/bin/gopls
flag provided but not defined: -json
usage: go version [-m] [-v] [file ...]
Run 'go help version' for details.
```

VS Code Go (TS/JS) uses `go version -m` when inspecting the tools versions. 
If `go version -m` can output JSON-encoded `runtime/debug.BuildSetting` format,
it will help simplifying output parsing  a lot.
Repository: vscode
Issue: how to disable Word Wrap globally
Labels: bug

## Environment data

Version: 1.93.1 (system setup)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

## Expected behaviour

Whenver we use the shortcut key "alt + z" it should disable wordwrap on all jupyter Notebook Cells

## Actual behaviour

It is currently running on individual cell level and whenever we reopen the VSCode, it will be wordwrap again, so need to click each cell and click alt + z to remove word wraps

## Steps to reproduce:

1. create multiple notebook input cells with large string data in single line
2. inbetween create input cells with smaller strings
3. and then keep individual input cell unwrapped using alt + z
4. restart the VScode, and you will see all the cell input values are wordwrapped again.
5. even if we save all input cells with unwrapped data ( alt + z ), after vscode restart, it will wrapped again.



Default I have made wordwrap Off everywhere.
In below screenshot it shows "Modified elsewhere" popup, there also I have checked and made settings to Off.
but still issue persists after restarting the VSCode.


![image](https://github.com/user-attachments/assets/29a3bf7a-668c-4bcc-b518-b1484e207a7e)
Repository: flutter
Issue: Create a migrator for android 35/16kb page size cmake flags for plugin_ffi 
Labels: c: new feature,framework,fyi-ecosystem

Follow on work from https://github.com/flutter/flutter/pull/155508 which updates the templates. 

Examples of updating the app cmake file here. 
Impl file: lib/src/migrations/cmake_native_assets_migration.dart
Test dir: test/general.shard/migrations/cmake_project_migration_test.dart

This bug will need a migrator for the plugin cmake file.