sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Favor idle GPUs that fit over largest free memory GPUs when scheduling
Labels: feature request

The scheduler today tries to find a single GPU to run a model based on the [largest amount of free VRAM](https://github.com/ollama/ollama/blob/main/server/sched.go#L690-L693), but on multi-GPU setups where one GPU is significantly larger than others, this can lead to smaller models clumping on the largest GPU.  The algorithm should be a bit smarter to try to find an idle GPU first to avoid this clumping behavior.
Repository: react-native
Issue: Android - Composer - Previous text is cut off after creating next line
Labels: Issue: Author Provided Repro,Platform: Android

### Description

When the TextInput component is controlled and the multiline prop is set to true, the text gets cut off after writing some text and adding a new line. However, when a new character is added, the text displays correctly.

### Steps to reproduce

1. Add a TextInput
2. set the value prop and onChangeText
3. set as true the multiline prop
4. Add some text
5. Add a new line, tapping the Enter button on the keyboard
6. The text is cut off 

### React Native Version

0.74.3

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: macOS 13.6.7
  CPU: (10) arm64 Apple M1 Pro
  Memory: 41.83 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.14.0
    path: ~/.nvm/versions/node/v20.14.0/bin/node
  Yarn:
    version: 1.22.22
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.7.0
    path: ~/.nvm/versions/node/v20.14.0/bin/npm
  Watchman:
    version: 2023.11.27.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/eduardograciano/.gem/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.4
      - iOS 16.4
      - macOS 13.3
      - tvOS 16.4
      - watchOS 9.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10671973
  Xcode:
    version: 14.3.1/14E300c
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 2.7.5
    path: /Users/eduardograciano/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: false
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: true
```


### Stacktrace or Logs

```text
-
```


### Reproducer

https://github.com/gedu/android-composer-reproducer

### Screenshots and Videos


https://github.com/user-attachments/assets/67a44e6e-c8bc-470a-b29b-48b7846b1d36

<img width="651" alt="Screenshot 2024-07-18 at 15 56 24" src="https://github.com/user-attachments/assets/c4f1a49c-99b9-4905-85bb-a1c181a6af66">
Repository: pytorch
Issue: Using an empty tensor and `torch.int64` or `torch.bool` for `dtype` of `nanmean()` works while a non-empty tensor doesn't work
Labels: good first issue,module: error checking,triaged,module: boolean tensor

### 🐛 Describe the bug

Using a non-empty tensor and `torch.int64` or `torch.bool` for `dtype` of [nanmean()](https://pytorch.org/docs/stable/generated/torch.nanmean.html) gets the errors as shown below:

```python
import torch

my_tensor = torch.tensor([0., 1., 2.])

torch.nanmean(input=my_tensor, dtype=torch.int64) # Error

torch.nanmean(input=my_tensor, dtype=torch.bool) # Error
```

> RuntimeError: "nansum_cpu" not implemented for 'Long'

> RuntimeError: "nansum_cpu" not implemented for 'Bool'

But, using an empty tensor and `torch.int64` or `torch.bool` for `dtype` of `nanmean()` works even though the results are `tensor(nan)` which are not converted to `torch.int64` or `torch.bool` as shown below:

```python
import torch

my_tensor = torch.tensor([])
my_tensor = torch.tensor([[]])
my_tensor = torch.tensor([[[]]])

torch.nanmean(input=my_tensor, dtype=torch.int64)
torch.nanmean(input=my_tensor, dtype=torch.bool)
# tensor(nan) 
```

### Versions

```python
import torch

torch.__version__ # 2.3.1+cu121
```

cc @malfet
Repository: ollama
Issue: Search/Filter by license
Labels: feature request

First, thanks for all the awesome work ! 

It would be nice to be able to search / filter by license on this page https://ollama.com/library
Repository: rust
Issue: Unconstrained lifetimes in impl headers are usable in assoc consts
Labels: A-const-generics,T-types

#114713

This should be dealt with somehow before allowing associated constants to be used in the type system (e.g. `feature(generic_const_exprs)` or a `min` variation).
Repository: pytorch
Issue: DISABLED test_comprehensive_nn_functional_pad_reflect_cuda_bfloat16 (__main__.TestDecompCUDA)
Labels: triaged,skipped

Platforms: rocm, linux



This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22test_decomp.py%3A%3ATestDecompCUDA%3A%3Atest_comprehensive_nn_functional_pad_reflect_cuda_bfloat16%22%5D)).

cc @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: TypeScript
Issue: Contextual parameters inferred from overloads improvements
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

contextual parameters functions overloads inference TS7006 argument length

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

Currently, inferring a parameter type from a function with overloads is very finicky. Unused generic parameters, constraints, and parameter length all unnecessarily prevent parameter types from being inferred.

A lot of these limitations are mentioned on https://github.com/microsoft/TypeScript/pull/42620, but there's no inherent reason the parameters can't be inferred in many of these cases. This is a suggestion to revisit some of the merge logic to allow a wider variety of cases to be inferred correctly.

### 📃 Motivating Example

Here are some examples I've run into recently that I believe are reasonable inference candidates:

Playground: https://tsplay.dev/N5YkVN

```ts
export type Fn = {
    // t is unused in the first overload
    <t>(s: string): void
    <t>(t: t): void
}

// first: string | t
export const fn: Fn = (first) => {}

export type Fn2 = {
    // remove unused generic param
    (s: string): void
    <t>(t: t): void
}

// Parameter 'first' implicitly has an 'any' type.
export const fn2: Fn2 = (first) => {}

export type Fn3 = {
    <t>(s: string): void
    // add constraint to a parameter
    <t extends number>(t: t): void
}

// Parameter 'first' implicitly has an 'any' type.
export const fn3: Fn3 = (first) => {}


export type Fn4 = {
    (s: string): void
    (n: number, b: boolean): void
}

// Second could safely be inferred as boolean | undefined here

// Type '(first: number, second: boolean) => void' is not assignable to type 'Fn4'.
//   Target signature provides too few arguments. Expected 2 or more, but got 1.(2322)
export const fn4: Fn4 = (first, second) => {}
```

### 💻 Use Cases

1. What do you want to use this for? Parameter inference
2. What shortcomings exist with current approaches? Duplicate definitions and casting
3. What workarounds are you using in the meantime? Forcing the signatures to align with hacks like adding unused generic parameters, manually typing them and/or casting.
Repository: flutter
Issue: [Semantics / Accessibility] TextField is invisible to TalkBack when suffixIcon is a IconButton.
Labels: a: text input,platform-android,framework,a: accessibility,has reproducible steps,P2,team-android,triaged-android,found in release: 3.22,found in release: 3.24

### Steps to reproduce

1. TextField -> decoration: InputDecoration -> suffixIcon: IconButton.
2. Enable TalkBack on your device.
3. Click on the input.

### Expected results

When pressed on the input, it should be announced: : "edit box"

### Actual results

It is not possible to click on TextField.

### Code sample

<details open><summary>Code sample</summary>

```
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  late final TextEditingController searchController = TextEditingController();

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        title: Text(widget.title),
      ),
      body: Center(
        child: TextField(
          decoration: InputDecoration(
            suffixIcon: IconButton(
              onPressed: () {},
              icon: const Text('icon'),
            ),
          ),
        ),
      ),
    );
  }
}

```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>


https://github.com/user-attachments/assets/b8de7cfb-e588-4b43-a7a4-212613e182d9


</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel stable, 3.22.2, on macOS 13.5.1 22G90 darwin-x64, locale en-US)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.90.2)
[✓] Connected device (3 available)
[✓] Network resources
```

</details>
Repository: pytorch
Issue: Shape-aware type hinting
Labels: feature,module: typing,triaged

### 🚀 The feature, motivation and pitch

Instead of the messy code syntax:


`python
if self.buildA_true:
            if idx is None:
                adp: torch.Tensor = self.gc(self.idx)
            else:
                adp: torch.Tensor = self.gc(idx)
        else:
            adp: torch.Tensor = self.predefined_A
`

### Alternatives

Support shape annotated Tensors

`python
if self.buildA_true:
            if idx is None:
                adp: torch.Tensor[207,207] = self.gc(self.idx)
            else:
                adp: torch.Tensor[207,207] = self.gc(idx)
        else:
            adp: torch.Tensor[207,207] = self.predefined_A
`

### Additional context

_No response_

cc @ezyang @malfet @xuzhao9 @gramster
Repository: pytorch
Issue: PT2E XNNPACKQuantizer has unused operator_type_config and set_operator_type
Labels: oncall: quantization

### 🐛 Describe the bug

A setter for `operator_type_config` called `set_operator_type` exists for `XNNPACKQuantizer`, but it is unused.

```sh
$ rg 'operator_type_config'

torch/ao/quantization/quantizer/xnnpack_quantizer.py
277:        self.operator_type_config: Dict[
319:        self.operator_type_config[operator_type] = quantization_config
```

If it is not supported for this quantizer, then an assertion, warning message, or comment should be added.

It seems that it was copied from the x86 inductor quantizer, which renamed the config to `operator_type_qconfig` and appears to use this to allow filtering out specific ATen operator types.

### Versions

At commit c015e5b of `pytorch/pytorch`

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @msaroufim
Repository: PowerToys
Issue: Show CPU, disk, network, GPU, and memory usage on PowerToys Run
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

### Description of the new feature / enhancement

Like Task Manager, when we click the Performance tab, we can monitor the percentage of CPU and GPU. Also, we can see how much memory it's being used by other apps that are running in foreground or background. With PowerToys Run, we want to monitor the usage of CPU, disk, network, GPU, and memory instead of opening Task Manager and clicking the Performance tab.

### Scenario when this would be used?

Press the PowerToys Run hotkey, and type **cpu** for CPU usage, **memory** for RAM usage, **disk** for disk usage (such as internal or external or removable drives), **network** for network usage, and **gpu** for GPU usage.

### Supporting information

Users can type in **cpu**, **memory**, **disk**, **network**, and/or **gpu** globally in PowerToys Run if global results are enabled without having to input the direct activation command before typing in first.
Repository: PowerToys
Issue: Let users switch between users from PowerToys Run
Labels: Idea-Enhancement,Help Wanted,Product-PowerToys Run,Run-Plugin

### Description of the new feature / enhancement

Usually, the methods of switching between users are:

1. Clicking Start>the user profile picture icon>another username.
2. Pressing CTRL+ALT+DELETE and clicking Switch user.

The coolest thing to do in PowerToys Run is by using it, we can switch between users.

### Scenario when this would be used?

Press the hotkey for PowerToys Run, type **switch user** and click "Switch between users." This will return to the sign-in screen without signing out of the current user account where another user can sign into his/her user account.

### Supporting information

Regardless of whether there is more than one user account is available on a PC or not, a user can still press the hotkey for PowerToys Run, type **switch user**, and then click "Switch between users."
Repository: flutter
Issue: Promote camera plugin to 1.0
Labels: p: camera,package,team-ecosystem,P2,triaged-ecosystem

[The camera package](https://pub.dev/packages/camera) is currently at 0.11.0+1.  It seems pretty mature at this point.  Can it be promoted to 1.0?

cc @stuartmorgan
Repository: godot
Issue: Dead keys trigger two times every other press when used as input on Windows
Labels: bug,platform:windows,needs testing,topic:input

### Tested versions

Godot v4.3.beta3

### System information

Godot v4.3.beta3 - Windows 10.0.19045

### Issue description

When using a keyboard layout with dead keys (like United States-International) and you use it as input it trigger the action two times every other press. This would cause problems if say you have set an input to a physical key that corresponds to a dead key on the users keyboard layout. Or if a user want to use a key that happens to be a dead key, for what ever reason that could be.

This is also true when used for shortcuts in the editor

Tested this in some other programs, and Inkscape had same behavior as Godot. Gimp was one of the programs that worked. This problem doesn't seem to happen on a Debian system I tested on.

### Steps to reproduce

Set an input action to physical key QuoteLeft on a US keyboard layout
Add a function that prints or rotate something when this input is pressed
Switch to United States-International layout

or in the editor

Set "zoom in" to physical key QuoteLeft 
set zoom to 25%
With the US layout it will go 35.4% > 50%
set it to 25% again
Switch to United States-International layout
Now it goes 35.4% > 70.7%

### Minimal reproduction project (MRP)

[deadkeys.zip](https://github.com/user-attachments/files/16288361/deadkeys.zip)
Repository: flutter
Issue: [rfw] Goldens tests disabled due to blocking flutter->packages roll
Labels: package,team-ecosystem,P2,c: tech-debt,c: disabled test,p: rfw,triaged-ecosystem

The following goldens tests are failing in rfw, thus blocking the Flutter -> packages roll 
In argument_decoders_test:
[golden checks](https://github.com/flutter/packages/blob/ef80c44a134981fd3a615507f59d5cdb6f07e979/packages/rfw/test/argument_decoders_test.dart#L234)
In material_widgets_test:
[Material widgets](https://github.com/flutter/packages/blob/ef80c44a134981fd3a615507f59d5cdb6f07e979/packages/rfw/test/material_widgets_test.dart#L25)
[Implement Material properties ](https://github.com/flutter/packages/blob/ef80c44a134981fd3a615507f59d5cdb6f07e979/packages/rfw/test/material_widgets_test.dart#L521)
[Implement OverflowBar properties ](https://github.com/flutter/packages/blob/ef80c44a134981fd3a615507f59d5cdb6f07e979/packages/rfw/test/material_widgets_test.dart#L368)
[OverflowBar configured to resemble ButtonBar](https://github.com/flutter/packages/blob/ef80c44a134981fd3a615507f59d5cdb6f07e979/packages/rfw/test/material_widgets_test.dart#L307)
[Implement ButtonBar properties](https://github.com/flutter/packages/blob/ef80c44a134981fd3a615507f59d5cdb6f07e979/packages/rfw/test/material_widgets_test.dart#L231)

See also https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8742051507903378097/+/u/Run_package_tests/Dart_unit_tests/stdout
Repository: pytorch
Issue: Add some more testing around checkpoint over compile
Labels: module: checkpoint,triaged

### 🚀 The feature, motivation and pitch

^

It seems to ... work?

But it does it work in all cases? with cudagraphs? etc. Need to add some tests at least...

cc: @zou3519 @soulitzer 

```
import torch.nn as nn
import copy
import torch
torch.set_default_device('cuda')

def f(x):
    x = torch.mm(x, x).cos()
    x = torch.mm(x, x).cos()
    return x

cf = torch.compile(f)

def g(x, f):
    return torch.utils.checkpoint.checkpoint(f, x, use_reentrant=False)

inp = torch.randn(16, 16, requires_grad=True) 
g(inp, f).sum().backward()
out1 = inp.grad
inp.grad = None
g(inp, cf).sum().backward()
out2 = inp.grad
print((out1 - out2))
```

### Alternatives

_No response_

### Additional context

_No response_

cc @soulitzer
Repository: rust
Issue: Remove `binary_asm_labels` once the LLVM issue is fixed
Labels: C-cleanup,A-LLVM,A-inline-assembly,T-compiler,L-binary_asm_labels

This issue is just to track https://github.com/llvm/llvm-project/issues/99547. After that is fixed, we can remove `binary_asm_labels` and allow using `0:` and `1:` on x86.

Relevant issues:

- https://github.com/llvm/llvm-project/issues/99547
- https://github.com/rust-lang/rust/issues/94426

Relevant PRs:

- https://github.com/rust-lang/rust/pull/126922
- https://github.com/rust-lang/rust/pull/127935
Repository: godot
Issue: `EditorNode3DGizmo::add_collision_triangles` replaces previous meshes instead of adding
Labels: bug,topic:editor,topic:3d

### Tested versions

Reproducible in: 4.3.beta [0918fd2], 4.2.2.stable, 4.1.4.stable

### System information

Windows 10 - Godot v4.2.2.stable

### Issue description

I'm playing around with the plugin system, and I wanted to add a gizmo that has collision triangles. A gizmo that needs to add collision triangles will not work correctly if it's working with multiple `TriangleMesh`es: only the last one added is checked for collision.

The implementation of `EditorNode3DGizmo::add_collision_triangles` seems to be the culprit:
https://github.com/godotengine/godot/blob/ff8a2780ee777c2456ce42368e1065774c7c4c3f/editor/plugins/node_3d_editor_gizmos.cpp#L361-L363

I consider this a bug because it is inconsistent with the way other functions, like `add_mesh` and `add_collision_segment`, work.

### Steps to reproduce

- Download the MRP included in this issue
- Open Scene.tscn
- Select the pyramid
- Click on the bottom triangle of the pyramid. Observe that it will not be deselected.
- Click on other triangles of the pyramid. This time, the pyramid will incorrectly be deselected.

### Minimal reproduction project (MRP)

[Editor3DNodeGizmo AddCollisionTriangles MRP.zip](https://github.com/user-attachments/files/16289318/Editor3DNodeGizmo.AddCollisionTriangles.MRP.zip)
Repository: rust
Issue: `asm!` lints based on `cfg` rather than target
Labels: C-enhancement,A-lints,A-inline-assembly,T-compiler

For example:

```rust
#[cfg(target_arch = "x86")]
fn foo() {
    unsafe { asm!("0: jmp 0b") };
}
```

This currently raises `binary_asm_labels` only if targeting x86. Ideally we would be able to raise the lint regardless of what the current target is.

Requested in https://github.com/rust-lang/rust/issues/127821 and https://github.com/rust-lang/rust/pull/127935