sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: gclient sync of the engine cannot pull flutter/java/openjdk/linux-aarch64
Labels: engine,platform-linux,P3,platform-host-arm,platform-target-arm,e: local-engine-development,team-engine,triaged-engine

I get an error saying gclient cannot find `flutter/java/openjdk/linux-aarc64` on aarch64 Linux. Looks like it doesn't exist? https://chrome-infra-packages.appspot.com/p/flutter/java/openjdk

```
> ________ running 'cipd ensure -log-level error -root /nix/store/q0pwqcvz1il5b0b38h6r8agnifx8v2cr-flutter-engine-source-af0f0d559c8a87d912a20971bbd84afc80a54b0f-x86_64-linux-x86_64-linux -ensure-file /build/tmpzwogih2k.ensure' in '.'
> Errors:
>   failed to resolve flutter/java/openjdk/linux-arm64@version:17 (line 23): no such package: flutter/java/openjdk/linux-arm64
> Error: Command 'cipd ensure -log-level error -root /nix/store/q0pwqcvz1il5b0b38h6r8agnifx8v2cr-flutter-engine-source-af0f0d559c8a87d912a20971bbd84afc80a54b0f-x86_64-linux-x86_64-linux -ensure-file /build/tmpzwogih2k.ensure' returned non-zero exit status 1
> Errors:
>   failed to resolve flutter/java/openjdk/linux-arm64@version:17 (line 23): no such package: flutter/java/openjdk/linux-arm64
```
Repository: next.js
Issue: Error next js 15 image component
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/Farruh-JS/next15_image_issue/master

### To Reproduce

Codesandbox link: https://codesandbox.io/p/github/Farruh-JS/next15_image_issue/master 
Github link: https://github.com/Farruh-JS/next15_image_issue

I don't know why, but on Codesandbox everything worked fine for me, you should run this locally.

![image](https://github.com/user-attachments/assets/f361d134-f70a-47ae-aa85-c23937f77b1c)

### Current vs. Expected behavior

If you use the Next Image component, some random images will return a 500 error. However, if you render the same image with an img tag, it will work fine.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
Binaries:
  Node: 20.11.1
  npm: 10.5.0
Relevant Packages:
  next: 15.0.1
  eslint-config-next: 15.0.0-canary.148
  react: 19.0.0-rc-69d4b800-20241021
  react-dom: 19.0.0-rc-69d4b800-20241021
  typescript: 5
Next.js Config:
 images: {
		remotePatterns: [
			{ protocol: 'https', hostname: 'ik.imagekit.io' },
			{
				protocol: 'https',
				hostname: 'storage.googleapis.com',
				port: '',
				pathname: '/polebor/site/media/original/**',
			},
			{ protocol: 'https', hostname: 'mp.softly.uz' },
		],
	},
```


### Which area(s) are affected? (Select all that apply)

Image (next/image)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

I tested my reproduction against different canary releases including latest 15.0.2-canary.6 version, and the first one that introduced the bug was &quot;15.0.0&quot;, since reverting to &quot;14.2.14&quot; works.
Also i have tried on my windows machine, got the same problem
Repository: godot
Issue: GraphEdit in the editor scales GraphNodes according to editor scale but not positions, leading to broken display at scales different than the design scale
Labels: bug,topic:editor,confirmed,topic:visualscript,topic:shaders

### Tested versions

Godot 4.3 Stable

### System information

Windows 10 64, Godot 4.3 Stable, Forward+

### Issue description

Godot Engine does not respect the grid of visual nodes (in shaders or other graphs) if the UI scale has changed. It is crucial for public projects or games developed by multiple people on different screens. Or even if a single person tries to work on a desktop (100% scale) and laptop (150-200% scale).

### You made a node graph, when your system is at 100% scale, it looks clean:
![Godot_Visual_Shaders_Bug](https://github.com/user-attachments/assets/dfd5555c-0217-48e9-aa3e-b8b0ee076238)

### With 150% scale, nodes are mashed together:
![Godot_Visual_Shaders_Bug2](https://github.com/user-attachments/assets/e068ead6-c6cf-42b6-9f17-f985f5b920ba)

### With 200% scale, it gets even worse:
![Godot_Visual_Shaders_Bug3](https://github.com/user-attachments/assets/78da3312-59b0-4cc4-835c-93de1459e808)

The solution is not just change sizes of nodes themselves, but also make them respect the grid (and reorganize accordingly).

### Steps to reproduce

1. Use system scale of 100% (and/or editor scale of 100%)
2. Make a visual shader with several nodes aligned in a grid, save it
3. Change UI scale (in the system or in the Godot Editor), relaunch
4. Grid is now messed up completely

### Minimal reproduction project (MRP)

You can try my graph from here: https://github.com/ArseniyMirniy/Godot-4-Free-Color-Correction-and-Screen-Effects-Visual-Shader
Repository: godot
Issue: When system scale changes and Godot 4 is running, it tries to adjust and usually crashes
Labels: bug,platform:windows,topic:porting,needs testing,crash

### Tested versions

Godot 4.3 Stable

### System information

Windows 10 and 11, Godot 4.3

### Issue description

Godot 4 is always following system scale, and there are many issues with that. It ignores the defined scale in the editor settings (if they are changed in system, it changes them again), it breaks UI elements, and finally, it tries to adjust on runtime.

If Godot 4.3 editor is running, and the user tries to change the scale in Windows OS settings, the app starting to consume 100% of CPU for a certain amount of time and tries to rescale everything on runtime. Very often it does not succeed and crashes. Sometimes it changes the scale, and it works (in my test, 4/10 rescales worked, and 6 crashed).

### Steps to reproduce

1. Launch Godot 4.3
2. Open Windows 10 OS settings
3. Change scale and apply
4. Godot either freezes for 10-15 seconds and changes scale or crashes.

### Minimal reproduction project (MRP)

Does not require a project.
Repository: go
Issue: govulncheck-action: Warning: Both go-version and go-version-file inputs are specified, only go-version will be used while only 'go-version-file: go.mod' is specified
Labels: NeedsInvestigation,vulncheck or vulndb

### govulncheck version

golang/govulncheck-action@v1.0.4

### Does this issue reproduce at the latest version of golang.org/x/vuln?

- Yes.

### Output of `go env` in your module/workspace:

```shell
-
```


### What did you do?

```
- uses: golang/govulncheck-action@v1.0.4
  with:
    go-version-file: go.mod
    go-package: ./...
```

### What did you see happen?

Warning: Both go-version and go-version-file inputs are specified, only go-version will be used

### What did you expect to see?

No warning as `go-version-file: go.mod` has been defined. If this is the case, then the code should omit go-version and only use the version that is defined in the go.mod file. Now it is using another Golang version, while another version is defined in the go.mod file.
Repository: kubernetes
Issue: CRD Mutation handler with leases
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

We have a leases feature in Kubernetes,  If we have an api server is deployed with v1 we can create another v10 version of api server. When deploying CRDs we can use the apiversion v10 to deploy on a newly leased for 10 hours. So that we can test it in 10 hours and move it to v1 CRD upgrade.

### Why is this needed?

This is to have a closest env with the production cluster where we can test with the real time env with automation. This is not only for CRD it can be applied for every resources that's been there in the K8s. But we can start with CRDs and cluster based resources.
Repository: pytorch
Issue: Runtime error: retains_grad_hooks not implemented for compiled autograd
Labels: triaged,oncall: pt2,module: compiled autograd

### 🚀 The feature, motivation and pitch

When we use compiled autograd to compile the backward graph and get the gradient of some activation, pytorch throws the error "retains_grad_hooks not implemented for compiled autograd". Will pytorch support compiled autograd with retain_grad_hooks?

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @chauhang @penguinwu @xmfan @yf225 @albanD @gqchen @pearu @nikitaved @soulitzer @Varal7
Repository: rust
Issue: abi_unsupported_vector_types lint is optimization-dependent
Labels: A-lints,T-lang,T-compiler,C-discussion,A-ABI,E-needs-design,L-abi_unsupported_vector_types

The lint guarding against https://github.com/rust-lang/rust/issues/116558 is intended to eventually become a hard error to fix this ABI issue. However, right now the lint is optimization-dependent: it runs during monomorphization to be able to figure out the actual argument types that will be passed at all call sites, and reject them if they need a missing target feature. If a call gets optimized away (e.g. in dead code), the lint will not fire.

I don't know any good way to prevent this, since we need the monomorphization-time information to check whether any of the arguments is a too-large SIMD vector. So this issue mostly serves to let @rust-lang/lang know that this is a thing, and as a place to track any ideas we might have about fixing this, or concerns about making this into an optimization-dependent hard error.
Repository: ollama
Issue: Does ollama have other model support plans?Such as TTS, graphics, video, etc
Labels: model request

We deeply appreciate the convenience, speed, and power of Olama. In order to meet more application scenarios, we hope that Olama can increase support for other model categories, such as text generated speech, text generated images, text generated videos, etc. With the rapid development of AI, the demand for AI will also increase. I hope you can carefully consider it.
Repository: flutter
Issue: Safari/Firefox browser: keyboard not working for TextFields within SelectionArea + Dialog
Labels: a: text input,framework,platform-web,has reproducible steps,browser: safari-macos,browser: firefox,P2,f: selection,team-web,triaged-web,found in release: 3.24,found in release: 3.27

### Steps to reproduce

- Run the given code with Flutter Web in the Safari or Firefox browser
- Open the dialog
- Try to write some text in each field

### Expected results

The keyboard should work correctly

### Actual results

Half of the time the keyboard doesn't work. If you focus an other field, sometime it works and sometime it just doesn't.
It works for the Chrome browser but not for Firefox or Safari (on macOS)

### Code sample

<details open><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() => runApp(App());

class App extends StatelessWidget {
  const App({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: SelectionArea(
        child: Scaffold(
          body: Builder(
            builder: (context) {
              return Center(
                child: FilledButton(
                  onPressed: () {
                    showDialog(
                        context: context, builder: (context) => EditDialog());
                  },
                  child: Text('Open dialog'),
                ),
              );
            },
          ),
        ),
      ),
    );
  }
}

class EditDialog extends StatelessWidget {
  const EditDialog({super.key});

  @override
  Widget build(BuildContext context) {
    return AlertDialog(
      scrollable: true,
      title: Text('Dialog'),
      content: Column(
        mainAxisSize: MainAxisSize.min,
        children: [
          for (var i = 0; i < 8; i++)
            TextField(
              decoration: InputDecoration(labelText: 'Enter text'),
            ),
        ],
      ),
      actions: [
        FilledButton(
          onPressed: () {
            Navigator.pop(context);
          },
          child: Text('OK'),
        )
      ],
    );
  }
}
```

</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 (Channel beta, 3.27.0-0.1.pre, on macOS 14.5 23F79 darwin-arm64, locale en-BE)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2024.2.3)
[✓] VS Code (version 1.93.0)
```

</details>
Repository: langchain
Issue: DOC: data parsing error handling (if retry and data fixing does not work)
Labels: 🤖:docs,stale

### URL

https://python.langchain.com/docs/how_to/output_parser_fixing/

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

I'm looking for ways to handle data parsing errors with 100% guarantee. 

Current documentation considers attempts to fix the errors by prompting LLM to fix it or with retry. The enhancement might work, but without any guarantee.

To be 100% sure, it would be helpful to explain how to handle parsing errors in the worst case, when the above attempts fail. 



### Idea or request for content:

One idea is to extend the output parser class to handle the parsing errors
Repository: vscode
Issue: Suggest (workspace-)recommended extensions if they are disabled
Labels: feature-request,extensions


Type: <b>Feature Request</b>

Actual:
Extensions added as workspace recommendations are suggested if they are not installed.

Expected:
Extensions added as workspace recommendations are suggested if they are not installed or not enabled.


The reason behind my suggestion is that users might have a number of extensions installed on their vscode, but they are disabled by default and enabled only based on the workspace.

When opening a workspace the application checks the recommended extensions from the workspace, but it does not suggest them to the user if the extension is installed but disabled. I believe it should suggest the extension based on its enabled state rather than its installed state.


Version: 1.94.2 (user setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

VS Code version: Code 1.94.2 (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Windows_NT x64 10.0.22631
Modes:


<!-- generated by issue reporter -->
Repository: vscode
Issue: Views drag and drop: allow to drop into the entire bar instead of splitting
Labels: feature-request,under-discussion,workbench-dnd,layout,workbench-views,workbench-auxsidebar

Right now for me to drag and drop a view in the secondary sidebar I have to drop it in the small title area of the secondary sidebar.
If I drop it in the large view area, it basically splits the view container.

I know this logically makes sense, but makes the whole DnD experience unusable.

Could DnD see if I am dragging the only view in the container, and if yes always drop it as a separate container?
I am constantly being bitten by this (even with previous DnD scenarios).
Repository: rust
Issue: no-op remap_path_prefix change invalidates incremental cache
Labels: A-debuginfo,T-compiler,A-incr-comp,C-feature-request,WG-incr-comp,A-path-remapping

<!--
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'm building rust code in a CI environment, setting -Cincremental to a shared location. CI allocates a new working directory for each build. To prevent leaking that info to the debug info, we set `--remap_path_prefix=${PWD}=` to eliminate the unwanted prefix from the debug info.


```sh
rustc src/lib.rs \
  --crate-name=xxx \
  --crate-type=rlib \
  --error-format=human \
  --out-dir=${OUTDIR} \
  --remap-path-prefix=${PWD}= \
  --emit=dep-info,link \
  -Ccodegen-units=256 \
  -Zincremental_info \
  -Cincremental=${CACHEDIR}
```

I expected this will reuse the incremental build cache, but it's not:

```
[incremental] session directory: 259 files hard-linked
[incremental] session directory: 0 files copied
[incremental] completely ignoring cache because of differing commandline arguments
```

Further inspection of how the hash being generated, I found:

https://github.com/rust-lang/rust/blob/017ae1b21f7be6dcdcfc95631e54bde806653a8a/compiler/rustc_session/src/options.rs#L195-L222

for our case, `working_dir` always uses remapped_path `""`, which is stable over build. but the `remap_path_prefix` is different everytime. and the logic for populating `working_dir` is at:

https://github.com/rust-lang/rust/blob/017ae1b21f7be6dcdcfc95631e54bde806653a8a/compiler/rustc_session/src/config.rs#L2690-L2695

So to get correct remapped `working_dir`, I must set `--remap-path-prefix`, but setting it will change `remap_path_prefix` and causing hash mismatch:

https://github.com/rust-lang/rust/blob/017ae1b21f7be6dcdcfc95631e54bde806653a8a/compiler/rustc_incremental/src/persist/load.rs#L159-L164

### 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-nightly (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: aarch64-apple-darwin
release: 1.82.0-nightly
LLVM version: 19.1.1
```
Repository: tensorflow
Issue: Does TFLite dequantize opertor support constant buffer input
Labels: stat:awaiting tensorflower,type:bug,comp:lite,ModelOptimizationToolkit,2.17

**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 24.04
- TensorFlow installed from (source or binary): source 
- TensorFlow version (or github SHA if from source): the latest version

**Standalone code to reproduce the issue** 
<img width="724" alt="image" src="https://github.com/user-attachments/assets/849a0952-90ce-42c4-b2dc-9a9e7333fb0b">
The [tflite model for user input](https://github.com/fujunwei/tensorflow/blob/tflite_label_image/tensorflow/lite/examples/python/dequantize_input.tflite) can work as expected

<img width="713" alt="image" src="https://github.com/user-attachments/assets/43cafc84-0ea6-4a06-84b4-4772c6cea8e8">

The [tflite model with constant buffer](https://github.com/fujunwei/tensorflow/blob/tflite_label_image/tensorflow/lite/examples/python/dequantize_constant.tflite) can't compute, so does [dequantize](https://www.tensorflow.org/mlir/tfl_ops#tfldequantize_tfldequantizeop) support constant input?

**Any other info / logs**

You can also modify [dequantize_tester in the Repo](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/delegates/xnnpack/dequantize_tester.cc#L110) to reproduce this issue like below code:

1, Create a constant buffer
```
  const auto buffer_data = builder.CreateVector( reinterpret_cast<const uint8_t*>(constant_buffer.data()),
                                                                              constant_buffer.size());
  const auto buffer_index = base::checked_cast<uint32_t>(buffers.size());
  buffers.emplace_back(::tflite::CreateBuffer(builder, buffer_data));
```

2, Use the `buffer_index ` when creating tensor:
```
const std::array<flatbuffers::Offset<::tflite::Tensor>, 2> tensors{{
      ::tflite::CreateTensor(
          builder,
          builder.CreateVector<int32_t>(Shape().data(), Shape().size()),
          Unsigned() ? ::tflite::TensorType_UINT8 : ::tflite::TensorType_INT8,
          /*buffer=*/buffer_index , /*name=*/0,
          ::tflite::CreateQuantizationParameters(
              builder, /*min=*/0, /*max=*/0,
              builder.CreateVector<float>({InputScale()}),
              builder.CreateVector<int64_t>({InputZeroPoint()}))),
      ::tflite::CreateTensor(
          builder,
          builder.CreateVector<int32_t>(Shape().data(), Shape().size()),
          ::tflite::TensorType_FLOAT32,
          /*buffer=*/0, /*name=*/builder.CreateString("dequantizeLinearOutput")),
  }};

```
Repository: rust
Issue: Code Fails to Compile with Unnecessary `use std::borrow::Borrow;`
Labels: A-diagnostics,T-compiler,D-confusing

<!--
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
use std::borrow::Borrow;

struct Node<T> {
    elem: T,
}

fn main() {
    let a = Some(Rc::new(RefCell::new(Node { elem: 1 })));
    let b = a
        .as_ref()
        .map(|node| Ref::map(node.borrow(), |node| &node.elem));
    print!("{:?}", b);
}
```

I expected to see this happen: The code should compile successfully and print the value of elem.

Instead, this happened: The code fails to compile with an error indicating that Borrow is not resolved, leading to compilation failure. If I comment out the seemingly unnecessary `use std::borrow::Borrow;`, the code can compile.

### 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.81.0 (eeb90cda1 2024-09-04)
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
error[E0282]: type annotations needed for `&_`
  --> src/main.rs:39:46
   |
39 |         .map(|node| Ref::map(node.borrow(), |node| &node.elem));
   |                                              ^^^^   --------- type must be known at this point
   |
help: consider giving this closure parameter an explicit type, where the type for type parameter `T` is specified
   |
39 |         .map(|node| Ref::map(node.borrow(), |node: &T| &node.elem));
   |                                                  ++++

error[E0609]: no field `elem` on type `&_`
  --> src/main.rs:39:58
   |
39 |         .map(|node| Ref::map(node.borrow(), |node| &node.elem));
   |                                                          ^^^^ unknown field
```

</p>
</details>
Repository: excalidraw
Issue: Prevent unintentional element movement at selection
Labels: enhancement

I have been using exalidraw the last few days and there is one little thing that bothers me, if you click on an element and your mouse is not completely still the element will end up moving a little bit with the mouse.

Theoretically this is working correctly but the amount of times I have double clicked on an element and in the process the mouse has moved a pixel and therefore the element has also moved with it is quite high.

A possible solution would be to add a small timeout from the click on the element until it starts processing the mouse movement. 
Maybe 0.3 seconds or so.


Just in case, Im using Firefox 128.3.1esr