sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Add support for function call (response back) (message.role=tool)
Labels: feature request,api

# Add support for function call (response back)

1. Currently there's no support for sending back the function call result to the model using the `role=tool` messages.
2. Using the native API (not openai), function tool calls don't have an identifier associated `tool_call_id`, this is present in the `openai` API, and is important to be available on both APIs. 

> [!IMPORTANT] 
> This ID is very when providing the result back to the model (in a chat history where the same function was invoked multiple times in a chat history with different results) for the model to reason about.

![image](https://private-user-images.githubusercontent.com/175953664/375331649-63b89254-3e2a-41e4-89dc-1b0fa5a675bf.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzA4MTI3ODIsIm5iZiI6MTczMDgxMjQ4MiwicGF0aCI6Ii8xNzU5NTM2NjQvMzc1MzMxNjQ5LTYzYjg5MjU0LTNlMmEtNDFlNC04OWRjLTFiMGZhNWE2NzViZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMTA1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTEwNVQxMzE0NDJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01YWVhMmY4YTQ3MjJjNjZiYTAzMmJiNGM0ZDNhMWNkNmMzZGYzNWE4M2RlZTBlYjBjYmJiMDBkZDY0NmZiYTRjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.l4MCxuSbdUftdj4wx5hWLP63e16PNn6zNb9fZaFsoIQ)
Repository: vscode
Issue: Normal quick fix suggestions are not provided on new file, only AI ones
Labels: bug,editor-code-actions

Steps to Reproduce:

1. I'm doing this in `vscode-copilot`
2. Create a new file
3. See it complains about the header
4. `CMD + .` only AI suggestions
5. Press space
6. `CMD + .` now you get non AI fixes 


![Image](https://github.com/user-attachments/assets/53ce7f52-728f-45c6-b391-9133a19717d0)

![Image](https://github.com/user-attachments/assets/00f3d05c-3ae4-4ea6-a853-4aff207ad0f3)
Repository: godot
Issue: Window decorations don't load until interacted with sometimes.
Labels: bug,platform:linuxbsd,topic:gui

### Tested versions

first seen in Godot 4.3.1: Godot 4.3.1.rc.custom_build[6699ae789]

### System information

Godot v4.3.1.rc (6699ae789) - Fedora Linux 41 (KDE Plasma) - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7900 XT (RADV NAVI31) - AMD Ryzen 9 7950X 16-Core Processor (32 Threads)

### Issue description

when compiling the editor with x11="no" upon loading a project the window decorations don't load until directly interacted with, and even then this appears to be random when they'll load or not.

### Steps to reproduce

Compile a custom editor with X11 removed with the specified commit, load a project and try to look for the window control buttons (like minimize and whatnot). 

### Minimal reproduction project (MRP)

N/A
Repository: deno
Issue: NODE_MODULES not created in sub projects
Labels: needs investigation,install

Version: Deno 2.0.4

When creating a Mono repo (with ` "nodeModulesDir": "auto"` set in the `deno.json`), the `deno install` command doesn't create `node_modules` in the sub projects. There is only a single `NODE_MODULES` at the root. After a few discussions on Discord, this seems to be a bug.

I've created a basic mono repo [1] that follows the layout described in [2]. 

[1] https://github.com/irbull/deno_mono_repo
[2] https://docs.deno.com/runtime/fundamentals/workspaces/

Steps to reproduce:
1. Clone this repo (https://github.com/irbull/deno_mono_repo)
2. type `deno install`
3. Notice there is only a `NODE_MODULES` directory at the root (not in any of the sub projects)
Repository: PowerToys
Issue: Expose Workspaces to PowerToys Run
Labels: Needs-Triage,Product-Workspaces

### Description of the new feature / enhancement

PowerToys Run displays Workspaces with names matching the search query. The default selection behavior would be to launch the Workspace.

### Scenario when this would be used?

Launching Workspaces would be faster versus launching the Workspaces Editor and clicking "Launch" each time. This is especially useful with multiple desktops and Workspaces for each desktop.

### Supporting information

_No response_
Repository: PowerToys
Issue: CTRL(left) key hijack
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I have set and used some Keyboard Remap Shortcuts long time ago. I used them constantly before with no issues.

After last update, my left CTRL key constantly stops working! This happens after some use (or after StandBy). The left CTRL is no longer functional, and this hijack happens to my laptops and external keyboard. 
The hijack is released, if the Keyboard Manager is disabled and re-enabled again. The CTRL key then starts to work, but soon is hijacked again. 
The right CTRL key works all the time.

BR, David

[PowerToysReport_2024-11-05-15-37-06.zip]
(https://github.com/user-attachments/files/17634587/PowerToysReport_2024-11-05-15-37-06.zip)


### ✔️ Expected Behavior

Normal use of left CTRL. With or without Keyboard Manager enabled.

### ❌ Actual Behavior

Left CTRL stops working, and starts again, if Keyboard manager is disabled/re-enabled.

### Other Software

_No response_
Repository: go
Issue: x/tools/gopls: pull diagnostic support, continued
Labels: gopls,Tools

Following up on #53275, there are a few more improvements I'd like to make to pull diagnostics so that they are comparable in performance to push diagnostics, at which point we can enable them by default:

- Rewrite the bottom-up graph traversal of analysis nodes: in the common case, all dependency information will be a cache hit (including memoized keys and encoded summaries in the file cache). Therefore, the bottom-up traversal of the full graph is a significant overhead when repeatedly querying diagnostics.
- Rewrite the bottom-up graph traversal to build package handles, for similar reasons.
- Refactor the fact decoder to operate on shallow fact encoding, so that facts in transitive dependencies can be retrieved (and decoded) on demand. (This could have a huge impact on performance).
- Add support for go.mod and go.work diagnostics (requires refactoring the way we diagnose the workspace).

CC @adonovan
Repository: PowerToys
Issue: [PowerToys Run] - VSCode Plugin - Add Extra Buttons
Labels: Idea-Enhancement,Resolution-Fix Committed,Run-Plugin

### Description of the new feature / enhancement

like other items

![Image](https://github.com/user-attachments/assets/9d0d8242-1a3f-4ca5-b04d-f712c3a4bcf1)


### Scenario when this would be used?

to open vscode projects
**Buttons for**

- Open in File-Explorer
- Open in Terminal


### Supporting information

_No response_
Repository: three.js
Issue: TSL: Avoid naming collision when using `label()` or `toVar()`.
Labels: TSL

### Description

When using `label()` or `toVar()` to give variables a name, collisions can occur when the name is already reserved for internal entities like uniforms or varyings.

If you now redefine a variable on app level, a shader error occurs. In WGSL for example:

> Error while parsing WGSL: :40:2 error: redefinition of 'cameraNear'

### Solution

It would be nice if the node material could automatically detect such name collisions and modify the custom names e.g. with a suffix.

### Alternatives

Leave it as it is and ask developers to pick unique names.

### Additional context

#29810
Repository: rust
Issue: LUB coercions works for a function but fails for a closure
Labels: A-diagnostics,A-closures,T-compiler,C-bug,A-coercions,D-confusing

I tried the following code ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=97bdc0c0bce43681addb09a41b9fa6ce)), following the [examples](https://doc.rust-lang.org/reference/type-coercions.html#examples) for LUB coercion in the Reference, chapter 10.7.

The closure does not compile
```rust
    let clo = || {
        if true {
            let x: *mut i32 = &mut 1;
            x
        } else if false {
            let x: &i32 = &1;
            x
        } else {
            let x: &mut i32 = &mut 1;
            x
        }
    };
    let _: *const i32 = clo();
```
with the error:
```
error[E0308]: `if` and `else` have incompatible types
```

A similar function does compile:

```rust
fn f() -> *const i32 {
    if true {
        let x: *mut i32 = &mut 1;
        x
    } else if false {
        let x: &i32 = &1;
        x
    } else {
        let x: &mut i32 = &mut 1;
        x
    }
}
```

According to the Reference, I expected that either both the closure and the function compiles or neither of them.
Repository: rust
Issue: compiletest seems to be generating its own macro backtrace diagnostics?
Labels: T-bootstrap,C-bug,A-compiletest,E-needs-investigation

What on earth is going on here

https://github.com/rust-lang/rust/blob/096277e989d6de11c3077472fc05778e261e7b8e/src/tools/compiletest/src/json.rs#L305-L321

@BoxyUwU found out that compiletest seemingly emits diagnostics that are not in rustc's diagnostics. Like

```
error[E0425]: cannot find value `ident` in this scope
  --> $DIR/const_arg_trivial_macro_expansion-1.rs:11:9
   |
LL |         ident
   |         ^^^^^ not found in this scope
...
LL |     fn array_0() -> [(); unbraced_unbraced_ident!()] { loop {} }
   |                          -------------------------- in this macro invocation
   |
   = note: this error originates in the macro `unbraced_ident` which comes from the expansion of the macro `unbraced_unbraced_ident` (in Nightly builds, run with -Z macro-backtrace for more info)
```

![Image](https://github.com/user-attachments/assets/f2d9208d-6518-438a-9698-ac071c67d411)

like, compiletest is generating its own macro backtrace diagnostics or something funny like that?
Repository: pytorch
Issue: [RFC] PyTorch - PyPi PEP-759 proposal (wheel-next)
Labels: module: binaries,triaged

### 🚀 The feature, motivation and pitch

I would like to call for feedback about the PyPi PEP-759 proposal. This PEP proposes a unique approach to safely hosting external wheels, while keeping PyPI as the source of truth for project and release metadata. The PEP proposes a new uploadable file format, easily derived from .whl files, which includes only metadata to point to an external wheel hosting service, tied to organizational accounts (download.pytorch.org in our case). We are considering participating in this PEP initiative, and would like to get feedback from PyTorch Developers. 

Potentially this PEP can solve some of the issues we are having during PyTorch releases :
- PyTorch PyPI channel size is constantly growing due to the large wheel size of PyTorch binary. Currently around ~900MB for 2.5 release. Implementing this approach will allow us to better control our channel size.
- Allow us to build a better test/staging PyPI channel to test binaries before publishing to PyPI. Currently we use [download.pytorch.org/whl/test](http://download.pytorch.org/whl/test) to test our wheels.
- Potentially give us the ability to host binaries with different CUDA versions on PyPI (Currently we only host CUDA 12.4 for Linux).
- Provide better user experience by eliminating need for specifying the index-url during install ``--index-url https://download.pytorch.org/whl/cpu``

Some possible concerns of this PEP:
- More CDN traffic on download.pytorch.org, hence higher cost
- Will this work well with other tools like Poetry ?
- Any potential security risks ?

Link to PEP-0759: https://peps.python.org/pep-0759/
Discuss Thread: https://discuss.python.org/t/pep-759-external-wheel-hosting/66458

cc @seemethere @malfet @osalpekar @albanD @ptrblck @ezyang @aterrel @warsawnv @DEKHTIARJonathan @gottbrath @rgommers
Repository: tensorflow
Issue: Cannot Convert 51 to a shape - Movenet pose classification tutorial
Labels: stat:awaiting tensorflower,type:support,comp:lite,2.17

### Issue type

Support

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

Yes

### Source

source

### TensorFlow version

2.17.0

### Custom code

No

### OS platform and distribution

Win11, colab notebook

### Mobile device

_No response_

### Python version

3.10.12

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

the notebook pose_classification.ipynb tutorial works fine until the following cell: 

`# Define the model
inputs = tf.keras.Input(shape=(51))
embedding = landmarks_to_embedding(inputs)

layer = keras.layers.Dense(128, activation=tf.nn.relu6)(embedding)
layer = keras.layers.Dropout(0.5)(layer)
layer = keras.layers.Dense(64, activation=tf.nn.relu6)(layer)
layer = keras.layers.Dropout(0.5)(layer)
outputs = keras.layers.Dense(len(class_names), activation="softmax")(layer)

model = keras.Model(inputs, outputs)
model.summary()`

I've run this both locally and within colab and get the same results. Any advice or insight would be helpful. 

### Standalone code to reproduce the issue

```shell
https://colab.research.google.com/github/tensorflow/tensorflow/blob/master/tensorflow/lite/g3doc/tutorials/pose_classification.ipynb#scrollTo=1Pte6b1bgWKv
```


### Relevant log output

```shell
ValueError                                Traceback (most recent call last)

<ipython-input-28-f905a19927b3> in <cell line: 2>()
      1 # Define the model
----> 2 inputs = tf.keras.Input(shape=(51))
      3 embedding = landmarks_to_embedding(inputs)
      4 
      5 layer = keras.layers.Dense(128, activation=tf.nn.relu6)(embedding)

2 frames

/usr/local/lib/python3.10/dist-packages/keras/src/backend/common/variables.py in standardize_shape(shape)
    528             raise ValueError("Undefined shapes are not supported.")
    529         if not hasattr(shape, "__iter__"):
--> 530             raise ValueError(f"Cannot convert '{shape}' to a shape.")
    531         if config.backend() == "tensorflow":
    532             if isinstance(shape, tf.TensorShape):

ValueError: Cannot convert '51' to a shape.
```
Repository: vscode
Issue: API for native window handle
Labels: feature-request,api,on-testplan,api-proposal,microsoft-authentication

For Broker support in Microsoft Authentication (https://github.com/microsoft/vscode/issues/229431) we need the window handle for this API:
https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-node/docs/brokering.md#window-parenting

So, I need to be able to access the window handle from Main alllll the way in an extension.

Here's the proposal:
```ts
	export namespace env {
		/**
		 * Retrieves the native window handle of the current window.
		 *
		 * @returns A promise that resolves to a Buffer containing the native window handle.
		 */
		export function getNativeWindowHandle(): Thenable<Buffer | undefined>;
	}
```
Repository: node
Issue: Missing documentation for process.emit
Labels: question,doc,process

### Affected URL(s)

https://nodejs.org/api/process.html

### Description of the problem

inside process page there is the docs for `process.emitWarning()` but is missing for the function `process.emit()` with following signatures:

```javascript
emit(event: "beforeExit", code: number): boolean;
emit(event: "disconnect"): boolean;
emit(event: "exit", code: number): boolean;
emit(event: "rejectionHandled", promise: Promise<unknown>): boolean;
emit(event: "uncaughtException", error: Error): boolean;
emit(event: "uncaughtExceptionMonitor", error: Error): boolean;
emit(event: "unhandledRejection", reason: unknown, promise: Promise<unknown>): boolean;
emit(event: "warning", warning: Error): boolean;
emit(event: "message", message: unknown, sendHandle: unknown): this;
emit(event: Signals, signal?: Signals): boolean;
emit(
    event: "multipleResolves",
    type: MultipleResolveType,
    promise: Promise<unknown>,
    value: unknown,
): this;
emit(event: "worker", listener: WorkerListener): this;
```

is that correct?
Repository: tensorflow
Issue: [TFLite/LiteRT] Conv3D does not support acceleration
Labels: stat:awaiting tensorflower,type:feature,comp:lite,2.17

**System information**
- TensorFlow Python version: 2.17.
- TensorFlow Android versions:
```
    implementation 'org.tensorflow:tensorflow-lite:2.16.1'
    implementation 'org.tensorflow:tensorflow-lite-select-tf-ops:2.16.1'
    implementation 'org.tensorflow:tensorflow-lite-gpu:2.16.1'
    implementation 'org.tensorflow:tensorflow-lite-gpu-api:2.16.1'
```

**Summary**

I am trying to speed up a model which is mostly made up of `Conv3D` operators on Android (for video classification). As far as I understand, neither the GPU delegate nor the quantization mechanism support `Conv3D`, so I am stuck with just running the full-precision model on CPU.

Am I missing some other ways I could use to accelerate this? If not, could this be a feature request for supporting a way?

Some performance numbers from my tests (one model pass):
* LiteRT, CPU-only, Android (Galaxy S10+): ~1400ms
* LiteRT, CPU-only, iOS (iPhone 13 Pro): ~700ms
* CoreML, accelerated, iOS, `float32` (same phone): ~160ms
* CoreML, accelerated, iOS, `float16`) (same phone): ~15ms
Repository: rust
Issue: Add a `dont-check-error-annotations` to compiletest
Labels: T-bootstrap,C-feature-request,A-compiletest

cc @jieyouxu 

It would be nice if compiletest could support a `//@ dont-check-error-annotations` annotation that would not require you to annotate your file with `//~^ ERROR:` anywhere. This would be useful for cases where I only care that the test doesn't start ICEing. Ideally we'd never need this but sometimes I wind up with hundreds of errors with useless spans and it's just not realistic (or helpful) to annotate it all. See for example [this test](https://gist.github.com/BoxyUwU/fcb293a503e1b577a0c05d4094093de2), all the error annotations are in the wrong place as macro diagnostics emit the error on the *macro definition* not the *caller*. This means that we'd wind up with ~100 error annotations on the insides of the macros which is not a helpful assertion whatsoever.
Repository: kubernetes
Issue: :elephant: Switch away from obsolete package `github.com/grpc-ecosystem/go-grpc-prometheus` 
Labels: sig/instrumentation,area/code-organization,needs-triage

See note on the package

```
⚠️ This project is depreacted and archived as the functionality moved to [go-grpc-middleware](https://github.com/grpc-ecosystem/go-grpc-middleware) repo 
since [provider/prometheus@v1.0.0-rc.0](https://github.com/grpc-ecosystem/go-grpc-middleware/releases/tag/providers%2Fprometheus%2Fv1.0.0-rc.0) release. 
You can pull it using go get github.com/grpc-ecosystem/go-grpc-middleware/providers/prometheus. The API is simplified and morernized, yet functionality 
is similar to what v1.2.0 offered. All questions and issues you can submit [here](https://github.com/grpc-ecosystem/go-grpc-middleware/issues).
```

/sig instrumentation
Repository: rust
Issue: Tracking issue for release notes of #132515: Fix and undeprecate home_dir()
Labels: O-windows,T-libs-api,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #132515.

### Steps

- [x] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Libraries
- [Fix and undeprecate home_dir()](https://github.com/rust-lang/rust/pull/132515)

# Compatibility Notes
- `std::env::home_dir()` has been deprecated for years, because it can give surprising results in some Windows configurations if the `HOME` environment variable is set (which is not the normal configuration on Windows). We had previously changed its behavior, out of concern for compatibility with code depending on this non-standard configuration. Given how long this function has been deprecated, we're now fixing its behavior as a bugfix, and the next version will undeprecate it. (We deferred undeprecating it on nightly until today's stable release, to avoid potential confusion between the fixed version on nightly and the previously unfixed version on stable.)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
`std::env::home_dir()` has been deprecated for years, because it can give surprising results in some Windows configurations if the `HOME` environment variable is set (which is not the normal configuration on Windows). We had previously changed its behavior, out of concern for compatibility with code depending on this non-standard configuration. Given how long this function has been deprecated, we're now fixing its behavior as a bugfix, and the next version will undeprecate it. (We deferred undeprecating it on nightly until today's stable release, to avoid potential confusion between the fixed version on nightly and the previously unfixed version on stable.)
````

cc @kornelski, @jhpratt -- origin issue/PR authors and assignees for starting to draft text
Repository: godot
Issue: Auto insert keys loses node focus after rotation via handle
Labels: bug,topic:animation

### Tested versions

- Reproducible in v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - GLES3 (Compatibility) - NVIDIA GeForce GTX 860M (nvidia; 535.183.01) - Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (8 Threads)

### Issue description

When recording an animation uses auto insert key (red "rec" button active), and registering rotation changes (diamond "rot" button active), every time user rotates a node using the Rotate handle (E), user loses focus of the nodes, and need to click again on the node for further operations. This prevents repeatedly changing rotation to see what the animation will look like.

### Steps to reproduce

- Create an Animation Player with some dummy nodes to rotate
- Create a dummy animation
- Enable auto insert key (red rec button) and rotation mask (diamond rot button)
- Select a node and enter Rotate mode (E)
- Drag mouse to rotate the node

Expected: user keeps focus of node
Actual: user loses focus of node, clicking once more on the scene view will not rotate node and will drag select a rectangle instead

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: CI has misconfigured Android emulators
Labels: P3,team-android,triaged-android

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8733083598586544001/+/u/start_avd/Start_Android_emulator__android_35_google_apis_x64.textpb_/raw_io.output_text

```
I1025 11:14:42.233939   48863 IniFile.cpp:450] Malformed int value 96M for key hw.ramSize
I1025 11:14:42.234009   48863 IniFile.cpp:450] Malformed int value 32M for key vm.heapSize
```

That's bad for 2 reasons.

First, the ramSize and heapSize should be Integer, and size in MegaBytes. Putting "96M" will not be correct, hence the error message.

Second, 96MB of Ram and 32MB of Vm Heap will be very low.

On the other hand, because of this misconfiguration, the system will use default values. We can see later in the log

```
I1025 11:14:42.243638   48863 main-common.c:1280] Increasing RAM size to 2048MB
D1025 11:14:42.243644   48863 main-common.c:1312] VM heap size 0MB is below hardware specified minimum of 512MB,setting it to that value
```

hence having those wrong values shouldn't be a problem.

In this log sent, did the emulator crashed ?