sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Layer normalization for Nested Tensors does not return the correct tensor types
Labels: triaged,module: nestedtensor

### 🐛 Describe the bug

Layer normalization on `NestedTensor` returns the result of layer normalization, mean, and standard deviation. It should return 3 NTs if not reducing on the ragged dimension, and 3 dense tensors otherwise.

e.g.
```Python
import torch

size = 1024

lengths = torch.randint(10000, 16000, (size,), device="cpu")
offsets = torch.zeros((size + 1,), device="cpu", dtype=torch.int32)
torch.cumsum(lengths, dim=0, out=offsets[1:])

values = torch.randn(
    (offsets[-1].item(), size), device="cpu", requires_grad=True
)

nt = NestedTensor(values, offsets)

out = torch.nn.functional.layer_norm(nt, nt.shape[1:])
```

### Versions

fbcode H100 8/9/24

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ
Repository: ollama
Issue: AirLLM integration?
Labels: feature request

I'd love to see the addition/support of [AirLLM](https://github.com/lyogavin/airllm) in ollama, as it can massively decrease the needed amount of vram to run large models.
Repository: kubernetes
Issue: Memory EmptyDir tmpfs size capped at 100% of node RAM size, not SizeLimit as specified
Labels: sig/node,kind/feature,triage/accepted

### What happened?

I have a bit of an odd use case -- running a Kubernetes 1.29 cluster with NodeSwap enabled on AWS. The EC2 nodes have swap memory enabled on attached SSDs, and have successfully been able to utilize the swap (allocate/use more memory than RAM) when running pods in production. 

On Linux, tmpfs I believe is typically able to be allocated to sizes larger than RAM, and in the cases where swap is present the files in tmpfs will be swapped out. 

When configuring an EmptyDir backed by memory, I set a limit equal to the node's RAM + swap for a pod (say, 150GB). Upon exec'ing into the pod, I noticed that the size of the tmpfs corresponding to the EmptyDir was capped at the node's RAM size (say, 50GB). There does not seem to be a way to enable EmptyDir sizes greater than node RAM sizes, which is limiting for some of our applications which choose to use RAM via writing to tmpfs. It would be preferable to have no limit on EmptyDir memory size, and allow the pod to be evicted/killed if RAM + swap (or just RAM) is exhausted. 



### What did you expect to happen?

The size of the EmptyDir would be equal to the specified size in the configuration file, as opposed to being capped to the amount of physical RAM on the node. 

### How can we reproduce it (as minimally and precisely as possible)?

1. Spin up a cluster with NodeSwap Enabled
2. Enable some amount of swap on a node (say, 10GB)
3. Create a pod with a memory-backed EmptyDir with SizeLimit == Node's RAM + 10GB (swap size). Configure no RAM limit on the pod. 
4. Verify that EmptyDir presents in pod as tmpfs capped at Node's RAM size, not RAM + Swap size. 

### Anything else we need to know?

Thank you for taking a look!

### Kubernetes version

Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.6", GitCommit:"ad3338546da947756e8a88aa6822e9c11e7eac22", GitTreeState:"clean", BuildDate:"2022-04-14T08:49:13Z", GoVersion:"go1.17.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"29+", GitVersion:"v1.29.6-eks-db838b0", GitCommit:"c978c80de3b482f1f425d408772311592917aa4e", GitTreeState:"clean", BuildDate:"2024-06-27T19:09:52Z", GoVersion:"go1.21.11", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.23) and server (1.29) exceeds the supported minor version skew of +/-1



### Cloud provider

AWS EKS

### OS version

Nodes running recent version of Amazon Linux

### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: stable-diffusion-webui
Issue: [Bug]: extensions 與 extranetworks 總是無法載入列表
Labels: bug-report

### Checklist

- [ ] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [ ] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

![image](https://github.com/user-attachments/assets/b8678efc-6431-4d87-bca7-137d6583a02e)

![image](https://github.com/user-attachments/assets/7c953f4d-3b8b-47a1-a106-094a54a1397d)


### Steps to reproduce the problem

.

### What should have happened?

.

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

Google Chrome

### Sysinfo

.

### Console logs

```Shell
.
```


### Additional information

_No response_
Repository: rust
Issue: `tests/run-make/dump-ice-to-disk` is flakey on i686-mingw
Labels: A-testsuite,A-diagnostics,T-compiler,O-windows-gnu,C-bug,D-diagnostic-infra,A-run-make

I've seen multiple instances of dump-ice-to-disk failing on completely unrelated PRs, but it's completely non-obvious to me how it can fail non-deterministically.

- https://github.com/rust-lang/rust/pull/125642#issuecomment-2278407758
    - `i686-mingw`: assertion `left == right` failed (left: 59, right: 60)
    - https://github.com/rust-lang/rust/blob/730d5d4095a264ef5f7c0a0781eea68c15431d45/tests/run-make/dump-ice-to-disk/rmake.rs#L32
- https://github.com/rust-lang/rust/pull/128293#issuecomment-2254336988
    - `i686-mingw`: assertion `left == right` failed (left: 61, right: 62)
    - https://github.com/rust-lang/rust/blob/2b78d920964e1d70927bcd208529bda0e11120d0/tests/run-make/dump-ice-to-disk/rmake.rs#L55
- https://github.com/rust-lang/rust/pull/122362#issuecomment-2281276239 failed **twice**
    - `i686-mingw`: assertion `left == right` failed (left: 60, right: 59)
    - https://github.com/rust-lang/rust/blob/730d5d4095a264ef5f7c0a0781eea68c15431d45/tests/run-make/dump-ice-to-disk/rmake.rs#L76
    - `i686-mingw`: assertion `left == right` failed (left: 60, right: 59)
	- https://github.com/rust-lang/rust/blob/c9bd03cb724e13cca96ad320733046cbdb16fbbe/tests/run-make/dump-ice-to-disk/rmake.rs#L63

---

<details>
	<summary>Past investigations</summary>

Update: see https://rust-lang.zulipchat.com/#narrow/stream/182449-t-compiler.2Fhelp/topic/getting.20.60Box.3Cdyn.20Any.3E.60.20as.20ICE.20message posted by @camelid:

> I'm getting the following ICE message during development of a PR:
>
> ```
> thread 'rustc' panicked at compiler/rustc_middle/src/ty/context.rs:3013:21:
> Box<dyn Any>
> stack backtrace:
> ```
>
> this line in my PR is
>
> ```
> bug!("No bound vars found for {}", self.hir().node_to_string(id))
> ```
>
> it turns out it displays the message correctly to stderr but not to the rustc-ice file

Is it possible that the test isn't flakey, but that our ICE dump actually regressed? cc @estebank and @nnethercote for diagnostic and ICE dumping in case you guys have any ideas.

Update 2: #128956 has the `Box<dyn Any>` symptom as well, it might not be limited to ICE dumps to files but also to stderr? Unclear at this moment.

```
thread 'rustc' panicked at compiler\rustc_codegen_llvm\src\context.rs:1138:21:
Box<dyn Any>
stack backtrace:
   0:     0x7fffe0c051b0 - std::backtrace_rs::backtrace::dbghelp64::trace::h0891390128512157
```

Update 3: `Box<dyn Any>` seems to be a separate thing.
</details>
Repository: godot
Issue: Invalid case for `PlaceHolder` & `UserData` in GDExtension function pointers
Labels: bug,topic:gdextension

### Tested versions

Godot 4.2 to master

### System information

all platforms

### Issue description

https://github.com/godotengine/godot/blob/88f3b5f9d52f740b24fabfb8bc01b8b7026ba279/core/extension/gdextension_interface.h#L2606-L2621

In `gdextension_interface.h`, functions `placeholder_script_instance_create` & `placeholder_script_instance_update` are incorrectly capitalized in their corresponding function pointer signatures (`GDExtensionInterfacePlaceHolderScriptInstanceCreate` & `GDExtensionInterfacePlaceHolderScriptInstanceUpdate`)

So `placeholder` in snake case becomes `PlaceHolder` in camelcase.

This is an issue when using automated tools that convert back the camelcase into snakecase (resulting in `place_holder_script_instance_create`, [for instance in Godot-Python](https://github.com/touilleMan/godot-python/blob/449c827ad6822fb00f586cab914d69ac316d9de9/src/godot/hazmat/gdnative_ptrs.pxd.j2#L139-L140))

Fortunately Godot displays a warning when `pythonscript_gdextension_get_proc_address` is used on an unknown function  (`ERROR: Attempt to get non-existent interface function: place_holder_script_instance_create.`). But this is nevertheless an anoying footgun...


The fix would simply be to rename `PlaceHolder` -> `Placeholder`. This would obviously breaks any code using those methods (though fixing is trivial), I'm not aware of the policy concerning GDExtension compat but I guess this kind of break is only allowed when bumping minor version (so 4.3, or even 4.4 given 4.3 is right around the corner ^^).

### Steps to reproduce

n/a

### Minimal reproduction project (MRP)

n/a
Repository: rust
Issue: macro_rules: Fragment `vis` somehow matches token `[` despite no visibility modifier starting with/having such token
Labels: A-macros,T-compiler,C-bug

I tried this code:

```rust
macro_rules! makro {
    (
        $(  
            [ $( $fn_type: ident )* ] 
        )?
        
        $fn_vis: vis
    ) => { };
}

makro! { [unsafe] pub }
```

I expected to see this happen: It compiles

Instead, this happened: 
```
   Compiling playground v0.0.1 (/playground)
error: local ambiguity when calling macro `makro`: multiple parsing options: built-in NTs vis ('fn_vis') or 1 other option.
  --> src/lib.rs:13:10
   |
13 | makro! { [unsafe] pub }
   |          ^

error: could not compile `playground` (lib) due to 1 previous error
```

`rustc --version --verbose`:
```
rustc 1.82.0-nightly (cefe1dcef 2024-07-22)
binary: rustc
commit-hash: cefe1dcef0e21f4d0c8ea856ad61c1936dfb7913
commit-date: 2024-07-22
host: x86_64-pc-windows-msvc
release: 1.82.0-nightly
LLVM version: 18.1.7
```

This also happens in stable Rust, playground link: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=b75389208cdb78680bab4ba33bb90efb
Repository: godot
Issue: Animation Freezes When Played for First Time & AnimationTree Transition Does Not Work When Animation is Looping
Labels: topic:animation

### Tested versions

Tested in Godot 4.2 stable and v4.3.rc3.mono.official [03afb92ef]

### System information

Windows 11, Gpu RX 6600, Cpu 10400, Godot v4.3.rc3.mono.official [03afb92ef]

### Issue description

- Animations do not play if looping is enabled for the rest animations
- There is a freeze that occurs just after playing the reload animation for the first time (more info on this below)

https://github.com/user-attachments/assets/d6ce6856-dd4c-42ce-80bd-30f96c16e4b7

### Steps to reproduce

1. Open up the attached MRP.

There will be 2 AnimationPlayer nodes. Currently the "arms_rest" and "assault_rifle_rest" are not set to be looping. We will get back to this later.

2. Play the game with F5.

Immediately press R to play the reload animation. Part of the animation will freeze for the first time playing but will not freeze after that. You should see the reload animation play on repeat.

Some observations about the freeze.
- Only the weapon animation freezes, the entire game did not freeze
- If you wait 10 seconds before playing the weapon reload animation then there will be no freezing to begin with
- The freeze happens every time the game starts up

This warning will appear in the console.
```
W 0:00:04:0825   _transition_to_next_recursive: AnimationNodeStateMachinePlayback: parameters/playback aborts the transition by detecting one or more looped transitions in the same frame to prevent to infinity loop. You may need to check the transition settings.
  <C++ Source>   scene/animation/animation_node_state_machine.cpp:918 @ _transition_to_next_recursive()
```

3. Close the game and set the "arms_rest" and "assault_rifle_rest" animations to be looping by clicking the looping icon in each AnimationPlayer node.

![Untitled](https://github.com/user-attachments/assets/2e4afadc-5618-4100-85a0-391ac0b458bd)

4. Play the game again with F5

Press R to play the reload animation and notice how the animations will not play at all. The same warning that appeared in console will appear again.

### Minimal reproduction project (MRP)

MRP is 27 mb and GitHub upload limit is 25 mb so MRP was uploaded to MediaFire.

https://www.mediafire.com/file/3e7p575esehewe1/MRP_AnimationTest.zip/file
Repository: PowerToys
Issue: Unable to type when using non-host trackpad to select textbox on the non-host device
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.83.0

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

1. Connect a device (laptop in my case) to a host (desktop).
2. Using the laptop's trackpad select a textbox on the host device.
3. using the laptop's trackpad select a textbox on the laptop.
4. Attempt to type using the host device's keyboard.

### ✔️ Expected Behavior

No matter which devices pointer device is selected, ideally any keyboard should be able to type in the last selected textbox.

### ❌ Actual Behavior

Will not type until the host's pointer device is used to select the textbox on the client device.

### Other Software

_No response_
Repository: opencv
Issue: Exceptions when not named parameters
Labels: question (invalid tracker)

### System Information

Python version: 3.8.18
OpenCV python version: 4.10.0
Operating System / Platform: Windows-10-10.0.19045-SP0

### Detailed description

```
cv2.error: OpenCV(4.10.0) D:\a\opencv-python\opencv-python\opencv\modules\imgproc\src\deriv.cpp:104: error: (-211:One of the arguments' values is out of range) The kernel size must be odd and not larger than 31 in function 'cv::getSobelKernels'
```

### Steps to reproduce

```
import numpy as np
 import cv2
  src = (np.random.rand(10, 10, 1) * 256).astype(np.uint8)  
blockSize = 3  
kSize = 3  
borderType = cv2.BORDER_DEFAULT
  output = cv2.cornerMinEigenVal(src, blockSize, kSize, borderType)
```
In this case, it would be throw the exception.

but if use
```
output = cv2.cornerMinEigenVal(src=src, blockSize=blockSize, ksize=kSize, borderType=borderType)
```
it can be correct.
I think it is a bug or error.

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: flutter
Issue: [version 3.24] ThemeData's hintColor not working in TextField, which was working in version 3.22.x
Labels: a: text input,c: regression,framework,f: material design,has reproducible steps,P2,team-text-input,triaged-text-input,found in release: 3.24

### Steps to reproduce

ThemeData(
      hintColor: Colors.red,

### Expected results

TextField's hint text color is read, as in previous version

### Actual results

TextField's hint text color seems white

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.24.0, on Microsoft Windows [Version 10.0.22631.3880], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[√] Chrome - develop for the web
[X] Visual Studio - develop Windows apps
    X Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2024.1)
[√] IntelliJ IDEA Community Edition (version 2024.2)
[√] VS Code, 64-bit edition (version 1.91.1)
[√] Connected device (4 available)
[√] Network resources
```

</details>
Repository: node
Issue: sqlite async API
Labels: sqlite

Provide an async API to our sqlite bindings. In order to avoid blocking the event loop on lookups that require IO.
Repository: godot
Issue: Translations GetText - Inherited scenes (control derived) won't have their text property string added to POT file
Labels: bug,topic:gui

### Tested versions

Godot Engine v4.2.2.stable.official.15073afe3

### System information

Godot v4.2.2.stable - Linux Mint 21.3 (Virginia) - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 1060 6GB (nvidia; 545.29.06) - 12th Gen Intel(R) Core(TM) i5-12600K (16 Threads)

### Issue description

First of all, I'm talking about a case where no scripts is attached to any node.

A node which is not saved as a scene or a node saved as a scene without inheriting another scene do have their translations strings generated by the POT generator.
But a scene which inherits a saved scene won't have any strings generated.

As such, in the latter case there are scenes which can't be translated.

### Steps to reproduce

Create a VboxContainer named Main, save it as main.tscn, set it as the main scene to run.
Add its children:
- A button. Set its text property to: Normal Button
- A button saved as a scene named ButtonBase saved as button_base.tscn. Set its text property to: Button Base Scene
- A scene inherited from ButtonExtended saved as button_extended.tscn. Set its text property to: Button Extended from Button Base scene

Project Settings -> Localization -> POT Generation -> Add...
- main.tscn
- button_base.tscn
- button_extended.tscn

Generate POT file -> "translations.pot"

Open translations.pot with a text editor.



### Minimal reproduction project (MRP)

[get-text-inherited-scene.zip](https://github.com/user-attachments/files/16569075/get-text-inherited-scene.zip)
Repository: ui
Issue: [bug]: Development mode warnings
Labels: bug

### Describe the bug

There are some warnings which occurred during developing the application. 

![warnings](https://github.com/user-attachments/assets/411e5eb3-77e8-4480-bf70-6272b8f30c4d)

### Affected component/components

N/A

### How to reproduce

1. Go to root directory
2. Run `pnpm dev`


### Codesandbox/StackBlitz link

https://github.com/shadcn-ui/ui

### Logs

```bash
www:dev:  └── 14 documents contain field data which didn't match the structure defined in the document type definition. (Skipping documents)
www:dev:
www:dev:      • "docs/changelog.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • toc: "false\r"
www:dev:      • "docs/components/alert.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/badge.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/button.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/card.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/chart.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/combobox.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/date-picker.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/input.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/pagination.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/skeleton.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/table.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/textarea.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
www:dev:      • "docs/components/typography.mdx" of type "Doc" has the following incompatible fields:
www:dev:        • component: "true\r"
```


### System Info

```bash
Win 10
Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ollama
Issue: Install Ollama with Winget on Windows
Labels: feature request,windows

Installing Ollama with winget is working perfectly, however not documented in the README.md

![image](https://github.com/user-attachments/assets/99ee03e2-b2e4-47f2-91e0-d12f048592cb)
Repository: godot
Issue: SpinBox not setting the visibility layer of its inner line edit
Labels: enhancement,discussion,topic:gui

### Tested versions

- Reproducible in v4.2.1.stable.mono.official [b09f793f5]

### System information

Windows 10 - Godot v4.2.1.stable.mono.official [b09f793f5]

### Issue description

A SpinBox's `visibility_layer` does not get copied to the inner LineEdit, so changing the viewport's canvas cull mask to not have the default layer bit set hides the line edit.

I found a workaround where I attach a script to the node with the following code:
```gdscript
extends SpinBox

func _ready():
    get_line_edit().visibillity_layer = visibility_layer
```

### Steps to reproduce

- Create a new SpinBox scene
- Edit the SpinBox's visibility layer to have bits 1 and 2 set
- Change the root viewport's canvas cull mask to have only bit 2 set

### Minimal reproduction project (MRP)

[spinbox-visibility-layer-bug.zip](https://github.com/user-attachments/files/16569104/spinbox-visibility-layer-bug.zip)

Starting the project and pressing the enter key toggles the root viewport's canvas cull mask between having only layer 1 and having only layer 2 visible.