sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: The order index of new node of Editable-Children-enaled scene is not saved in `.tscn` file sometimes
Labels: bug,topic:editor

### Tested versions

- Reproducible in v4.4.dev4.official [36e6207bb]

### System information

Windows 11 - Godot Engine v4.4.dev4.official.36e6207bb - Vulkan 1.3.280 - Forward+ - Using Device #0: NVIDIA - NVIDIA GeForce RTX 3060 Ti

### Issue description

![Image](https://github.com/user-attachments/assets/9d1d4a9e-1ffc-4d40-8c23-7cef7e38fdaa)
![Image](https://github.com/user-attachments/assets/a743926a-01ec-46d2-a019-dc743db85828)

When I add a new node `Node2D_xxxx` between `Node2D3` and `Node2D4` and save, the order index is not saved in `main.tscn` file so that when I re-open `main.tscn`, the `Node2D_xxxx` came after `Node2D4`.

Meanwhile, the `Node2D_yyyy`'s order is saved correctly. So I guess there is a bug to cause such different behavior.

### Steps to reproduce

1. Open MRP and open `main.tscn`
2. drag `Node2D_xxxx` between `Node2D3` and `Node2D4` and save。
3. re-open `main.tscn` and see the position of `Node2D_xxxx` 

### Minimal reproduction project (MRP)

[test_child_order.zip](https://github.com/user-attachments/files/17823918/test_child_order.zip)
Repository: rust
Issue: Type inference chooses wrong trait impl based on generic parameter
Labels: A-trait-system,C-bug,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
fn foo<T1, T2, E>(a: T1) -> Result<T2, E>
where
    T1: TryInto<usize>,
    T2: TryFrom<T1, Error = E>,
{
    a.try_into()
}

fn bar<T1, T2, E>(a: T1) -> Result<T2, E>
where
    T1: TryInto<usize>,
    T2: TryFrom<T1, Error = E>,
{
    TryInto::<T2>::try_into(a)
}
```

I expected to see this happen: 

Both functions should compile.

Instead, this happened: 

Only `bar` compiles.
`foo` produces the following compiler error:
```
error[E0308]: mismatched types
 --> src/main.rs:9:5
  |
4 | fn foo<T1, T2, E>(a: T1) -> Result<T2, E>
  |            --               ------------- expected `Result<T2, E>` because of return type
  |            |
  |            expected this type parameter
...
9 |     a.try_into()
  |     ^^^^^^^^^^^^ expected `Result<T2, E>`, found `Result<usize, ...>`
  |
  = note: expected enum `Result<T2, E>`
             found enum `Result<usize, <T1 as TryInto<usize>>::Error>`

For more information about this error, try `rustc --explain E0308`.
```

I also tried compiling with the new trait solver (`rustc -Znext-solver src/main.rs`) and get the same error message. I am not 100% sure if that means that I am compiling it the wrong way or if the output is just identical.

### 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.84.0-nightly (5ec7d6eee 2024-11-17)
binary: rustc
commit-hash: 5ec7d6eee7e0f5236ec1559499070eaf836bc608
commit-date: 2024-11-17
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.3
```
Repository: pytorch
Issue: plus prefix-less wheels not being published on https://download.pytorch.org/whl/torch/ for linux x86_64
Labels: module: binaries,triaged

In the process of answering something that @charliermarsh was asking, I noticed that on https://download.pytorch.org/whl/torch/ we aren't publishing Linux x86_64 wheels that don't have `+` prefix, which is awkward.
We should publish the default wheels not just on PyPI's default servers, but also on this index page?

cc: @malfet @seemethere 

cc @seemethere @malfet @osalpekar @atalman
Repository: tensorflow
Issue: Aborted (core dumped) in `tf.raw_ops.MatrixInverse`
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf 2.17

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 22.04.3 LTS (x86_64)

### Mobile device

_No response_

### Python version

3.9.13

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When the shape of the input argument is empty and the gpu is available, tf.raw_ops.MatrixInverse triggers a crash.
It can be reproduced on tf-nightly when the gpu is available.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf
tf.raw_ops.MatrixInverse(input=tf.cast(tf.random.uniform([], dtype=tf.dtypes.float32, maxval=60000), dtype=tf.complex128),adjoint=True)
```


### Relevant log output

```shell
2024-11-20 10:46:15.940818: I tensorflow/core/util/port.cc:153] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-11-20 10:46:16.001155: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:485] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-11-20 10:46:16.076386: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:8454] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-11-20 10:46:16.100080: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1452] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-11-20 10:46:16.154057: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: SSE4.1 SSE4.2 AVX AVX2 AVX512F AVX512_VNNI AVX512_BF16 AVX512_FP16 AVX_VNNI AMX_TILE AMX_INT8 AMX_BF16 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-11-20 10:46:23.889652: I tensorflow/core/common_runtime/gpu/gpu_device.cc:2021] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 21903 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 4090, pci bus id: 0000:1f:00.0, compute capability: 8.9
2024-11-20 10:46:23.891964: I tensorflow/core/common_runtime/gpu/gpu_device.cc:2021] Created device /job:localhost/replica:0/task:0/device:GPU:1 with 71 MB memory:  -> device: 1, name: NVIDIA GeForce RTX 4090, pci bus id: 0000:d4:00.0, compute capability: 8.9
2024-11-20 10:46:24.756574: F tensorflow/core/framework/tensor_shape.cc:356] Check failed: d >= 0 (0 vs. -1)
Aborted (core dumped)
```
Repository: react-native
Issue: Touch events unresponsive for flexible child Views in ScrollView component under React Native new architecture
Labels: Component: ScrollView,Needs: Triage :mag:,Newer Patch Available,Type: New Architecture

### Description

There is an issue with the touch events in a ScrollView when using the new architecture. Specifically, below a ScrollView, there is a View component with a minWidth of 100%. Inside this View, there are three child View components, each set with flexGrow: 1, flexShrink: 1, and flexBasis: "25%". The last two child View component does not respond to the touchstart event under the new architecture, while it works fine in the old architecture.

### Steps to reproduce

1. Create a ScrollView component provided by react-native and set horizontal to true
2. Place a View component below the ScrollView with minWidth: 100%.
3. Inside the View component, add three child View components, each with flexGrow: 1, flexShrink: 1, and flexBasis: "25%".
4. Test the touchstart event on the last two child View component.

Expected Result:
The last two child View components should respond to the touchstart event.

Actual Result:
The last two child View components do not respond to the touchstart event when using the new architecture, while this issue does not occur in the old architecture.

### React Native Version

0.74.3、0.75.2、0.76.2

### Affected Platforms

Runtime - iOS

### Areas

Fabric - The New Renderer

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.2.1
  CPU: (8) x64 Apple M3
  Memory: 180.14 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.1
    path: ~/.nvm/versions/node/v20.11.1/bin/node
  Yarn:
    version: 1.22.22
    path: /usr/local/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.1/bin/npm
  Watchman:
    version: 2024.10.21.00
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.4
      - iOS 17.4
      - macOS 14.4
      - tvOS 17.4
      - visionOS 1.1
      - watchOS 10.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.3 AI-233.14808.21.2331.11709847
  Xcode:
    version: 15.3/15E204a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.11
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.1
    wanted: 15.0.1
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.2
    wanted: 0.76.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true
```


### Stacktrace or Logs

```text
No logs
```


### Reproducer

https://github.com/yandadaFreedom/rn-original-scrollview

### Screenshots and Videos

_No response_
Repository: PowerToys
Issue: PowerToys Ruler: Protractor for Measuring Angles
Labels: Needs-Triage

### Description of the new feature / enhancement

Add a protractor tool to PowerToys Ruler for precise angle measurement on screen. This feature would allow users to easily measure angles directly on images, diagrams, or plots displayed on their monitors. It can be integrated into the existing PowerToys Ruler tool, enabling the user to overlay a protractor on the screen and measure angles with high accuracy.

### Scenario when this would be used?

As a scientist or professional working with visual data, such as images, graphs, or plots, users often need to measure angles to confirm the accuracy of their analysis. For example, when reviewing scientific plots in Matplotlib or analyzing images that require precise angle measurements, this tool would provide a quick and easy way to verify the angles without manually using a physical protractor. This feature would be particularly useful for verifying geometric relationships, angles in graphs, or alignment in visual data.

### Supporting information

Here:
Ruler and Protractor
https://apps.microsoft.com/detail/9pcx0wjj9g5h?launch=true&mode=full&hl=en-us&gl=us&ocid=bingwebsearch
Repository: angular
Issue: docs: Unable to Connect to Port - Components in Angular Tutorial
Labels: area: docs-infra

### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

All of the other tutorials load the preview, but the first one - Components in Angular Tutorial, continues to throw unable to connect to port error. I tested this on a different machine and continued to get the same error.

### Please provide a link to a minimal reproduction of the bug

https://angular.dev/tutorials/learn-angular/1-components-in-angular

### Please provide the exception or error you saw

```true
Unable to connect to port 4200
No server listening on port 4200.
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

```

### Anything else?

_No response_
Repository: deno
Issue: Add support for `--permit-no-files` in `deno bench`
Labels: suggestion,help wanted

For parity with `deno test`.

It's useful for workspaces when creating a deno task bench alias but a given packages has no bench files
Repository: ollama
Issue: Memory usage higher than LM Studio for similar model
Labels: bug

### What is the issue?

Memory usage is different for two services but both services use `llama.cpp` under the hood (not sure, but i think it is). I am not using MLX backend as it's slower on my machine.


### lm-studio (GGUF model)


https://github.com/user-attachments/assets/f283a317-c65d-44f9-ba43-37d49f0cb5ec



### ollama


https://github.com/user-attachments/assets/81fa67f7-19ae-46dc-aec9-2ed5a3d59b2f

#### Env

```bash
OLLAMA_NOHISTORY=1
OLLAMA_FLASH_ATTENTION=1
OLLAMA_KEEP_ALIVE=5m
OLLAMA_MAX_QUEUE=512
OLLAMA_MAX_LOADED_MODELS=1
OLLAMA_HOST=127.0.0.1
OLLAMA_NUM_PARALLEL=1
```



### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

0.4.x
Repository: rust
Issue: Terse parse error on `&raw expr`
Labels: A-diagnostics,A-parser,T-compiler,F-raw_ref_op,D-terse,A-raw-pointers

<!--
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
mod foo {
    pub static A: i32 = 0;
    pub static B: i32 = 0;
    pub static C: i32 = 0;
}


fn main() {
    let _arr = [ &raw foo::A, &raw foo::B, &raw foo::C ];
}
```

I expected to see this happen: Code compiles normally

Instead, this happened: A parser error.

```
error: expected one of `!`, `,`, `.`, `::`, `;`, `?`, `]`, `{`, or an operator, found `foo`
 --> src/main.rs:9:23
  |
9 |     let _arr = [ &raw foo::A, &raw foo::B, &raw foo::C ];
  |                       ^^^ expected one of 9 possible tokens
```

### 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.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 19.1.1
```
Repository: PowerToys
Issue: Default save path for New+ templates should not be dependent by language setting
Labels: Issue-Bug,Area-Localization,Needs-Triage,Issue-Translation

### Microsoft PowerToys version

0.85.1

### Utility with translation issue

New+

### 🌐 Language affected

Japanese

### ❌ Actual phrase(s)

`%localappdata%\Microsoft\PowerToys\NewPlus\テンプレート`

![Image](https://github.com/user-attachments/assets/76b0a800-3187-4898-a080-a157c72af61c)

### ✔️ Expected phrase(s)

`%localappdata%\Microsoft\PowerToys\NewPlus\Templates`

### ℹ Why is the current translation wrong

This issue may not be exactly a translation issue, but forgive me for reporting it as a translation issue because I wasn't sure where it would fall!


Main Issue.
--

New+ template directory names are affected by language settings


This may not be much of a problem for most languages, but Japanese uses double-byte characters and
Japanese uses double-byte characters, which can cause all sorts of bugs if included in the path.

Also, the PowerToys configuration folder is located in `%localappdata%MicrosoftPowerToys`, but the New+ Template folder is the only localized folder, including subdirectories.

There is also a problem with the Japanese documentation. The documentation lists the non-localized folders as template folders.
Here is a link to the documentation and a screenshot of the relevant section.

* [Windows 用 PowerToysNew+ | Microsoft Learn](https://learn.microsoft.com/ja-jp/windows/powertoys/newplus#templates-location)

![Image](https://github.com/user-attachments/assets/4789fd1f-aa02-4b46-bfd3-fbfc7c9189c2)


I find the existence of this directory confusing to both developers and the target users of PowerToys (at least it confused me)

Is this specification (bug?) is intended?
Repository: material-ui
Issue: [docs] [joyui] Container Component Missing in Documentation
Labels: docs,on hold,package: joy-ui,support: docs-feedback

### Related page

https://mui.com/joy-ui/getting-started/
### Kind of issue

Missing information

### Issue description

The Container component is not documented in the "Layout" section of the JoyUI documentation. Despite its absence from the documentation, [the component is present in the library and functional.](https://github.com/mui/material-ui/blob/9c98e3fb475d989ad676672a9dedd3ddbea5258e/packages/mui-joy/src/Container/index.ts)



### Context

Add the Container component to the documentation under the "Layout"  section, If all that is needed is to adapt content from the mui/material docs, I am happy to help with this task. You may assign it to me.

**Search keywords**: JoyUI, Container component, Component API, Documentation missing
Repository: tauri
Issue: [bug] In dev,node_modules 500
Labels: type: bug,status: needs triage

### Describe the bug


![image](https://github.com/user-attachments/assets/fed9c618-bace-4f15-ab71-25998c7bc94f)
![77202562b27ddf5c344b3240e89284e0](https://github.com/user-attachments/assets/dbbe788e-951f-4073-a429-072792cd9b26)
In Windows, everything is normal. When running on Android, the development environment dependency reports a 500 error that cannot be loaded, but it can be accessed via localhost:1420, and it can be accessed after packaging into an APK


### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
- OS: Windows 10.0.22631 x86_64 (X64)
✔ WebView2: 127.0.2651.105
✔ MSVC: Visual Studio Community 2022
✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
- node: 22.2.0
- npm: 10.7.0
- bun: 1.1.30

[-] Packages
- tauri 🦀: 2.1.1
- tauri-build 🦀: 2.0.3
- wry 🦀: 0.47.0
- tao 🦀: 0.30.8
- @tauri-apps/api : 2.1.1
- @tauri-apps/cli : 2.1.0

[-] Plugins
- tauri-plugin-http 🦀: 2.0.3
- @tauri-apps/plugin-http : 2.0.1
- tauri-plugin-fs 🦀: 2.0.3
- @tauri-apps/plugin-fs : not installed!
- tauri-plugin-os 🦀: 2.0.1
- @tauri-apps/plugin-os : 2.0.0
- tauri-plugin-shell 🦀: 2.0.2
- @tauri-apps/plugin-shell : 2.0.1

[-] App
- build-type: bundle
- CSP: unset
- frontendDist: ../dist
- devUrl: http://localhost:1420/
- framework: Vue.js
- bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: godot
Issue: Encoding empty string to base64 reports an error `Condition "ret.is_empty()" is true. Returning: ret`, but should not
Labels: bug,topic:core,usability

### Tested versions

- Reproducible in v4.4.dev2.mono.official [97ef3c837] and v4.3.stable.mono.official [77dcf97d8]

### System information

Godot v4.4.dev2.mono - Windows 10.0.22631 - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 4070 Ti SUPER (NVIDIA; 32.0.15.6109) - AMD Ryzen 7 7800X3D 8-Core Processor (16 Threads)

### Issue description

When encoding the empty string as base64, the resulting base64 string is empty, as is appropriate per [RFC4648](https://www.rfc-editor.org/rfc/rfc4648#section-10). However, an error is reported: ```Condition "ret.is_empty()" is true. Returning: ret```. 

An error should not be reported, because an empty return value is appropriate in this case. 

Possible location of issue: https://github.com/godotengine/godot/blob/a0cd8f187a43935d756e49bf3778f39f0964f0ac/core/core_bind.cpp#L1234-L1238

### Steps to reproduce

1. Use the MRP below or add the following line to any method (such as a `_ready()` method)

```gdscript
	Marshalls.utf8_to_base64("")
```

2. Run the project.
3. Check the godot debugger > errors tab to see the incorrectly reported error.

### Minimal reproduction project (MRP)

[ret_project.zip](https://github.com/user-attachments/files/17825851/ret_project.zip)
Repository: flutter
Issue: fllutter create should initialize analytics_options.yaml with stricter settings
Labels: c: new feature,package,c: proposal,p: flutter_lints

### Use case

When creating a new flutter project with `fluter create` the generated `analysis_options.yaml` does only contain 
`flutter_lints`



### Proposal

It should at least set 

```yaml
analyzer:
  language:
    strict-casts: true
    strict-inference: true
    strict-raw-types: true	
```

also some lints should be set to level `errror` see

https://github.com/dart-lang/sdk/issues/57098#issuecomment-2485661859
Repository: storybook
Issue: Luminosity contrast ratio of keyboard focus indicator with the grey background on the left navigation panel is less than minimum required ratio of 3:1.
Labels: bug,accessibility

### Describe the bug

Luminosity contrast ratio of keyboard focus indicator with the grey background on the left navigation panel is less than minimum required ratio of 3:1

**Observation:**
Same issue is repro'ing on both Mac and Windows.

**User Impact:** 
Visual impaired users and low vision users will be impacted if Luminosity contrast ratio of keyboard focus indicator is less than the required ratio due to which they will not be able to identify their focus properly and will not be able to complete their task easily.

Actual Result: 
Luminosity contrast ratio of keyboard focus indicator with the grey background for 'Content' Control in the left navigation panel is 1.2:1 which is less than minimum required ratio of 3:1. 

Refer Attachment: Luminosity contrast ratio of keyboard focus indicator with the grey background is less than minimum required.
![Image](https://github.com/user-attachments/assets/4f0121e6-b7d3-417f-bfaf-980b1b10f885)

Expected Result: 
Luminosity contrast ratio of keyboard focus indicator with the grey background for all the controls in the left navigation panel should be greater than minimum required ratio of 3:1. 


### Reproduction link

About / Introduction - Page ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net)

### Reproduction steps

1. Open URL: [About / Introduction - Page ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net)](https://ambitious-cliff-0c8148010.2.azurestaticapps.net/?path=/story/about-introduction--page) in latest edge browser.
2. Press tab key to reach to the controls in the left pane.
3. Press tab key and reach to the 'Content' control.
4. Open Color contrast analyzer and select foreground and background for the focus indicator using color picker. 
5. Verify whether on pressing tab keys to reach to the 'Contents' control present in the left navigation panel, luminosity contrast ratio of keyboard focus indicator with the grey background is greater than minimum required or 3:1 or not.

### System

```bash
Test Environment: 
OS: Windows 11 Version 24H2 OS build 26100.1742
Browser: Microsoft New Edge Version129.0.2792.52(Official build) (64-bit)
URL: About / Introduction - Page ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net)
Tool Used: Color Contrast Analyzer

Mac Test Environment:
OS: macOS Sequoia 15.0.1
Browser: Microsoft New Edge Version130.0.2849.56 (Official build) (64-bit)
RL: About / Introduction - Page ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net)
Tool Used: Color Contrast Analyzer
```

### Additional context

_No response_