sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking issue for release notes of #119286: show linker output even if the linker succeeds
Labels: A-linkage,T-compiler,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #119286.

### Steps

- [ ] 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
# Compiler
- [Stop silencing linker warnings](https://github.com/rust-lang/rust/pull/119286)
````

> [!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
````

cc @jyn514, @bjorn3 -- origin issue/PR authors and assignees for starting to draft text
Repository: godot
Issue: set_content_scale_size doesn't stretch correctly
Labels: topic:rendering,documentation

### Tested versions

4.4.dev7

### System information

Windows 10, Godot 4.4.dev7

### Issue description

Using `set_content_scale_size` to set a new scale for the viewport results in the window being cropped and unusually scaled. Here's how it appears before using content scale:
![Image](https://github.com/user-attachments/assets/1b2e37ab-101e-49c3-a560-3bb0e899c6ff)

The viewport size is 160x200 and I'm attempting to use `get_tree().get_root().set_content_scale_size(Vector2i(320,200))` to create a double-width pixel ratio:
![Image](https://github.com/user-attachments/assets/ca456297-4386-4e1f-93d8-65a06cde0a07)

This is how it appears:
![Image](https://github.com/user-attachments/assets/c25d198b-fec2-4126-8491-f647a21175f5)

The top is cropped and the width is not really much wider. Here's how it is meant to look:
![Image](https://github.com/user-attachments/assets/2f3d93c1-4493-4d7b-b7d0-8a0820eb9193)


### Steps to reproduce

Enable the line `get_tree().get_root().set_content_scale_size(Vector2i(320,200))` in the example project.

### Minimal reproduction project (MRP)

[teststretch.zip](https://github.com/user-attachments/files/18308037/teststretch.zip)
Repository: godot
Issue: Double Precision MultiMeshInstance3D does not Scale Properly
Labels: bug,topic:rendering,topic:3d

### Tested versions

- Reproducible in: 4.4.dev.double [bdf625b], 4.1.dev.double [dbcc7f3]. (I didn't personally check but @Zylann said it was also reproducible on a double precision build of Godot 4.3.)
- Not reproducible on single precision builds. 



### System information

Godot v4.4.dev.mono (e369ef6e1 (Really bdf625b)) - Windows 11 (build 22631) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 (NVIDIA; 32.0.15.6590) - AMD Ryzen 7 3700X 8-Core Processor (16 threads)

### Issue description

Expected:

https://github.com/user-attachments/assets/8a2641ba-21b1-4ba5-816b-46dace461759

Actual:

https://github.com/user-attachments/assets/50a6479c-7245-4820-8acd-9c8a354469f5

In double precision builds of godot it seems like the scale isn't being applied properly across the individual mesh instances within a MultiMeshInstance3D. The scale gets applied but the positions/origins of the instances aren't affected at all. 

### Steps to reproduce

Included is a MRP. In the MRP just open the one scene and attempt to scale the MultiMeshInstance3D or it's parent cube. The parent is unneeded but it helps illustrate what it should look like since when scaling it the cubes should stick to the surface of the parent cube. 

In general the steps to reproduce are:
1.) Run a double precision version of godot.
2.) Create a new scene and populate it with a MultiMeshInstance3D.
3.) Populate the MultiMeshInstance3D where each instance has some offset.
4.) Attempt to scale the MultiMeshInstance3D and observe each instance's position not change. 

### Minimal reproduction project (MRP)

[multimeshweirdness.zip](https://github.com/user-attachments/files/18308308/multimeshweirdness.zip)
Repository: storybook
Issue: [Bug]: `storybook dev` is watching ignored files
Labels: bug,core

### Describe the bug

when running `test-storybook --coverage`, `storybook dev` output follows
```bash
5:24:26 AM [vite] (client) page reload coverage/storybook/lcov-report/index.html
5:24:26 AM [vite] (ssr) page reload coverage/storybook/lcov-report/index.html (x2)
5:24:26 AM [vite] (client) page reload coverage/storybook/lcov-report/components/index.html
5:24:26 AM [vite] (ssr) page reload coverage/storybook/lcov-report/components/index.html (x2)
5:24:26 AM [vite] (client) page reload coverage/storybook/lcov-report/components/Button.tsx.html
5:24:26 AM [vite] (ssr) page reload coverage/storybook/lcov-report/components/Button.tsx.html (x2)
5:24:26 AM [vite] (client) page reload coverage/storybook/lcov-report/components/Header.tsx.html
5:24:26 AM [vite] (ssr) page reload coverage/storybook/lcov-report/components/Header.tsx.html (x2)
5:24:26 AM [vite] (client) page reload coverage/storybook/lcov-report/components/Page.tsx.html
5:24:26 AM [vite] (ssr) page reload coverage/storybook/lcov-report/components/Page.tsx.html (x2)
5:24:26 AM [vite] (client) page reload coverage/storybook/lcov-report/components/LoginForm/index.html
5:24:26 AM [vite] (ssr) page reload coverage/storybook/lcov-report/components/LoginForm/index.html (x2)
5:24:26 AM [vite] (client) page reload coverage/storybook/lcov-report/components/LoginForm/LoginForm.tsx.html
5:24:26 AM [vite] (ssr) page reload coverage/storybook/lcov-report/components/LoginForm/LoginForm.tsx.html (x2)
```

### Reproduction link

https://github.com/ianzone/react-storybook/tree/main

### Reproduction steps

1. clone https://github.com/ianzone/react-storybook/tree/main
2. pnpm i
3. pnpm run dev
4. pnpm run test:story

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-13800H
    Shell: 5.9 - /home/linuxbrew/.linuxbrew/bin/zsh
  Binaries:
    Node: 22.12.0 - /home/linuxbrew/.linuxbrew/opt/node@22/bin/node
    npm: 10.9.0 - /home/linuxbrew/.linuxbrew/opt/node@22/bin/npm
    pnpm: 9.15.2 - /home/linuxbrew/.linuxbrew/bin/pnpm <----- active
  npmPackages:
    @storybook/addon-a11y: ^8.4.7 => 8.4.7
    @storybook/addon-coverage: ^1.0.5 => 1.0.5
    @storybook/addon-essentials: ^8.4.7 => 8.4.7
    @storybook/addon-interactions: ^8.4.7 => 8.4.7
    @storybook/addon-links: ^8.4.7 => 8.4.7
    @storybook/blocks: ^8.4.7 => 8.4.7
    @storybook/react: ^8.4.7 => 8.4.7
    @storybook/react-vite: ^8.4.7 => 8.4.7
    @storybook/test: ^8.4.7 => 8.4.7
    @storybook/test-runner: ^0.21.0 => 0.21.0
    chromatic: ^11.22.0 => 11.22.0
    storybook: ^8.4.7 => 8.4.7
```

### Additional context

_No response_
Repository: PowerToys
Issue: Keyboard Manager mapping of keys causes wacom device express keys to not function properly.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

being a long time mac user, and using a mac keyboard with my windows 11 computer, i remapped the keyboards control/command key with the windows key. ![Image](https://github.com/user-attachments/assets/4fac10e8-ca69-41d1-881e-f41a8b7915b0)

I was setting up my wacom tablet intuos pro (pth-451)  some of the express key options would not work.  specifically any that used the control key, such as undo and redo, it would act as if i had pressed windows-z instead of control-z for undo.  



### ✔️ Expected Behavior

expecting the keyboard remapping to be system wide (all devices such as a tablet) and not just for a keyboard.

When i turn off keyboard manager the wacom tablet works as expected.  

### ❌ Actual Behavior

when using the express key set up to use control-z it would do windows z instead.  

### Other Software

Was using wacoms setting software to set up express keys to keyboard short cuts and for using adobe illustrator 29.1
Repository: deno
Issue: Cannot read properties of undefined (reading 'variables') => process.config 
Labels: bug,node compat,quick fix

I updated to Deno 2.X few months ago, and I had an issue when using Neo4j package from NPM (even with the latest Deno version. 2.1.4):

```ts
import neo4j from "npm:neo4j-driver@5.27.0";

const driver = neo4j.driver("bolt://localhost:7687", neo4j.auth.basic("neo4j", "0000"));
```

I got the following error:

```
error: Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'variables')
    at getSystemInfo (file:///Users/heziode/Library/Caches/deno/npm/registry.npmjs.org/neo4j-driver-core/5.27.0/lib/internal/bolt-agent/node/bolt-agent.js:30:34)
    at Object.fromVersion (file:///Users/heziode/Library/Caches/deno/npm/registry.npmjs.org/neo4j-driver-core/5.27.0/lib/internal/bolt-agent/node/bolt-agent.js:40:22)
    at Object.driver (file:///Users/heziode/Library/Caches/deno/npm/registry.npmjs.org/neo4j-driver/5.27.0/lib/index.js:205:63)
    at file:///Path/To/Project/script.ts:3:22
```

The line in `bolt-agent.js`:

```js
        hostArch: process.config.variables.host_arch,
```

Version: Deno 2.1.4
OS: macOS (but I can reprooduce on Debian)

---

The script works with Deno 1.46.3
Repository: ant-design
Issue: Form.Item broken when rendered in Column
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/3vmg28?file=%2Fsrc%2FApp.js%3A14%2C1-15%2C1)

### Steps to reproduce

    <Form>
      <Row>
        <Col>
          <Form.Item
            layout="vertical"
            name="input1"
            label="Input 1"
            help="What do I do"
          >
            <Input />
          </Form.Item>
          <Form.Item layout="vertical" name="input1" label="Input 1">
            <Input />
          </Form.Item>
        </Col>
      </Row>
    </Form>

### What is expected?

Form Item render on top of each other.

### What is actually happening?

The form items overlap because of flex-col added in 5.18. 

| Environment | Info |
| --- | --- |
| antd | 5.18.0 |
| React | Any |
| System | Windows |
| Browser | Edge |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Loading indicators when pasting
Labels: editor-clipboard

this is crazy yall, it's been like 6 months of this weird "loading" paste feature

gets faster the less you're running, but even on a new m4 this keeps happening

![Image](https://github.com/user-attachments/assets/5966903a-d845-44f2-9e7d-1af77006f82b)

- VS Code Version: 1.96.0
- OS Version: Mac 15.1

Steps to Reproduce:

1. Do any amount of heavy work
2. Copy and paste

It seems that it for TypeScript Intellisense to finish before pasting, which it did not last year. It barely functions as an editor now.

https://www.loom.com/share/187d5a342f044a1793b0e607fd415b3c
Repository: node
Issue: Readable.fromWeb doesn't end on empty string
Labels: stream,web streams

### Version

v23.5.0

### Platform

```text
Linux xiaomi-mi-pro-gtx 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec  5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```

### Subsystem

_No response_

### What steps will reproduce the bug?

```js
import { Readable } from "node:stream";

const response = new Response({
  async *[Symbol.asyncIterator]() {
    yield '' // works only with non-empty string
  }
})

const stream = Readable.fromWeb(response.body);
// const stream = Readable.from('') // works as expected

stream.on('data', chunk => {
  console.log(`data: ${chunk}`)
})

stream.on('end', () => {
  console.log('ended')
});
```

### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior? Why is that the expected behavior?

Similar to the `Readable.from` stream, the `Readable.fromWeb` stream should trigger both 'data' & 'end' events. 

### What do you see instead?

`data` & `end` events are only triggered, when the response string is not empty.

### Additional information

_No response_
Repository: PowerToys
Issue: Power Toys - Image Resizer - 2 things
Labels: Needs-Triage

### Description of the new feature / enhancement

1) Almost what I need. The matching of the smallest dimension when resizing is what messes me up. What I want is to resize a directory full of images such that none of them are larger than, say, 1000 px in the **largest** direction, regardless of the orientation as long as it maintains the length/width ratio. For example: something that is 2100x3000 ends up 700x1000, while something 2000x1600 ends up 1000x800.

2) Renaming needs more work. I can tell it to rename the images to **%1 (%2)** as the docs show, but I want some custom text in the new name too. I'd like the new name spec to allow **%1 V2** or something like that which just appends some text on the filename. If I then leave the resized files in the source directory they will sort right behind the originals and I can see the effects of my resizing more easily.

If there are ways to accomplish these things with the Resizer "as is", then I apologize for not figuring it out and I'd appreciate some guidance to make it work the way I want it.

### Scenario when this would be used?

See above, it's all there.

### Supporting information

_No response_
Repository: neovim
Issue: Nvim can be a Lua host; Lua plugins can define RPC method/request handlers
Labels: enhancement,plugin,channels-rpc,lua,remote-plugin

### Problem

Although https://github.com/neovim/neovim/issues/11474 is closed, Nvim still has [test/client/](https://github.com/neovim/neovim/tree/64b0e6582ae8c273efbe39109bcb261079c2bcd4/test/client) because Nvim itself cannot yet easily perform as a RPC host which can *receive* requests/notifications. This is because:

- no way to define a RPC method/notification handler in a Nvim Lua plugin

### Expected behavior

Eliminate `test/client/`. Nvim Lua plugins can easily:

- define a RPC method handler, so a client can make a RPC request to `foo` and the method handler can handle it and return a result. Just like node-client, pynvim, etc., already can.
    - design: implement as `RpcRequest` event (autocmd)?
        - ⚠  need ability for autocmds to (1) receive parameters and (2) return results.
            - allows [vim.on_func()](https://github.com/neovim/neovim/pull/22598) to fully use the event subsystem, and avoid reinventing its own event subsystem
Repository: rust
Issue: rustc fails to build trivial hello world program; cargo build always fails : exit code: 0xc0000005, STATUS_ACCESS_VIOLATION
Labels: O-windows,T-compiler,C-discussion

### Verification

- [x] I searched for recent similar issues at https://github.com/rust-lang/rustup/issues?q=is%3Aissue+is%3Aopen%2Cclosed and found no duplicates.
- [x] I am on the latest version of Rustup according to https://github.com/rust-lang/rustup/tags and am still able to reproduce my issue.

### Problem

Hi,

I have installed latest `rustup-init.exe`.  Always i am getting build issue as below `exit code: 0xc0000005, STATUS_ACCESS_VIOLATION`. I have tried to reinstall couple of times still did not workout. 



```
PS D:\rust-example> cargo new ex03
    Creating binary (application) `ex03` package
note: see more `Cargo.toml` keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
PS D:\rust-example> cd .\ex03\

PS D:\rust-example\ex03> cargo --version
cargo 1.83.0 (5ffbef321 2024-10-29)

PS D:\rust-example\ex03> rustc --version
rustc 1.83.0 (90b35a623 2024-11-26)

PS D:\rust-example\ex03> cargo build
   Compiling ex03 v0.1.0 (D:\rust-example\ex03)
error: could not compile `ex03` (bin "ex03")

Caused by:
  process didn't exit successfully: `C:\Users\LENOVO\.rustup\toolchains\stable-x86_64-pc-windows-msvc\bin\rustc.exe --crate-name ex03 --edition=2021 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=237 --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --check-cfg cfg(docsrs) --check-cfg "cfg(feature, values())" -C metadata=3c538b4ef1d2d27e --out-dir D:\rust-example\ex03\target\debug\deps -C incremental=D:\rust-example\ex03\target\debug\incremental -L dependency=D:\rust-example\ex03\target\debug\deps` (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION)
PS D:\rust-example\ex03> 
```

Could you please help?


### Steps

1. Download  and install _rustup-init.exe_ from [install exe from here](https://www.rust-lang.org/tools/install)
2. Create a sample project `cargo new ex03`
3. Perform `cargo build`

Issue: It never build success. Always getting error as `exit code: 0xc0000005, STATUS_ACCESS_VIOLATION`.

### Possible Solution(s)

_No response_

### Notes

I have tried to install `stable-x86_64-pc-windows-gnu` and checked however still did not worked out.


Windows Version:
![Image](https://github.com/user-attachments/assets/39580038-c436-4029-a8f5-9ad03beeb968)
![Image](https://github.com/user-attachments/assets/7dc575f2-8b20-4bac-b683-f2de44495a54)


### Rustup version

```console
cargo 1.83.0 (5ffbef321 2024-10-29)
```

### Installed toolchains

```console
Default host: x86_64-pc-windows-msvc
rustup home:  C:\Users\LENOVO\.rustup

stable-x86_64-pc-windows-msvc (default)
rustc 1.83.0 (90b35a623 2024-11-26)
```

### OS version

```console
Windows 11 Pro OS,  Version 24H2 (OS Build 26100.2605)

C:\Windows\System32>wmic os get osarchitecture
OSArchitecture
64-bit
```
Repository: TypeScript
Issue: `./*.d.ts` required in `exports` to avoid `Cannot be named without a reference to... not portable...`
Labels: Needs More Info

### 🔎 Search Terms

The inferred type of '...' cannot be named without a reference to... This is likely not portable. A type annotation is necessary.

### 🕗 Version & Regression Information

Between 5.3 to 5.7 (latest)


### ⏯ Playground Link

_No response_

### 💻 Code


### TSconfig of importing project
```ts
{
  "compilerOptions": {
    "outDir": "./lib",
    "rootDir": "./src",
    "tsBuildInfoFile": "./lib/.tsbuildinfo",

    "target": "ESNext",
    "module":"ESNext",
    "moduleResolution":"bundler",

    "composite": true,
    "declarationMap": true,
    "sourceMap": true,
    "strict": true,
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "noErrorTruncation": true,
    "verbatimModuleSyntax": true,

    "emitDeclarationOnly": true,
    "skipLibCheck": true,

    "allowJs": true,

    
  },
  "include": ["src/**/*"]
}
```

### Package.json of project BEING IMPORTED
```json
{

  "type": "module",
  "files": [
    "lib/**/*",
    "src/**/*"
  ],
  "exports": {
    "./lib/*.d.ts": "./lib/*.d.ts",
    ".": {
      "types":"./lib/index.d.ts",
      "import":"./lib/index.js"
    }
  },
}

```



### 🙁 Actual behavior

If you do not include `"./lib/*.d.ts": "./lib/*.d.ts"` in the package.json of the imported project, you will receive the `...likely not portable...` error.

However, in none of the documentations and searches I've seen was this written as a requirement. As a result, I assume it's a bug.

The problem with the above solution is that it exposes the `.d.ts` files, which causes intellisense import suggestions to suggest two imports (one from the proper path, and one from the .d.ts path).

Note:
1. The import is a **direct dependency**, not a transitive dependency.
2. Using `main:./lib/index.js` instead of `exports:...` also removes the error.



### 🙂 Expected behavior

Should not need to explicitly export all types

### Additional information about the issue

_No response_
Repository: langchain
Issue: langchain_ollama 0.2.2 completely broke tool usage
Labels: 🤖:bug,investigate

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

The following code (copied 99% from an example of tool usage in the documentation), run with langchain_ollama==0.2.2
```from langchain_core.tools import tool
from langchain_ollama.chat_models import ChatOllama

@tool
def get_weather(city: str):
    """Give me name of city, I return current weather"""
    return "19 degree and foggy"

llm = ChatOllama(model="llama3.1").bind_tools(tools=[get_weather])
res = llm.invoke("what is the weather in London?")
print(res.tool_calls[0])
```

fails with `IndexError: list index out of range`

`pip install -U langchain-ollama==0.2.1` and run the same code again and it works as expected, i.e., the output is `{'name': 'get_weather', 'args': {'city': 'London'}, 'id': '252c5e30-8332-4354-9986-f75d705a4bff', 'type': 'tool_call'}`

### Error Message and Stack Trace (if applicable)

```
Traceback (most recent call last):
  File "test_ollama_tools.py", line 11, in <module>
    print(res.tool_calls[0])
          ~~~~~~~~~~~~~~^^^
IndexError: list index out of range
```

### Description

Langchain ollama should support tool calls, and have supported in the past, but even simple examples are not identified as tool calls.

### System Info

System Information
------------------
> OS:  Windows
> OS Version:  10.0.22631
> Python Version:  3.12.8 (tags/v3.12.8:2dc476b, Dec  3 2024, 19:30:04) [MSC v.1942 64 bit (AMD64)]

Package Information
-------------------
> langchain_core: 0.3.28
> langchain: 0.3.13
> langchain_community: 0.3.13
> langsmith: 0.2.6
> langchain_ollama: 0.2.2
> langchain_openai: 0.2.14
> langchain_postgres: 0.0.12
> langchain_text_splitters: 0.3.4
> langgraph_sdk: 0.1.48

Optional packages not installed
-------------------------------
> langserve

Other Dependencies
------------------
> aiohttp: 3.11.11
> async-timeout: Installed. No version info available.
> dataclasses-json: 0.6.7
> httpx: 0.27.2
> httpx-sse: 0.4.0
> jsonpatch: 1.33
> langsmith-pyo3: Installed. No version info available.
> numpy: 1.26.4
> ollama: 0.4.4
> openai: 1.59.3
> orjson: 3.10.12
> packaging: 24.2
> pgvector: 0.2.5
> psycopg: 3.2.3
> psycopg-pool: 3.2.4
> pydantic: 2.10.4
> pydantic-settings: 2.7.0
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> SQLAlchemy: 2.0.36
> sqlalchemy: 2.0.36
> tenacity: 9.0.0
> tiktoken: 0.8.0
> typing-extensions: 4.12.2
> zstandard: Installed. No version info available.
Repository: PowerToys
Issue: I found myself using the dashboard a lot. I would love to see ways to customize it or pin the favourite modules on top.
Labels: Needs-Triage

### Description of the new feature / enhancement

Dashboard

### Scenario when this would be used?

Pin or customize dashboard so you don't need to look for it again when you want to turn it on.

### Supporting information

I found myself using the dashboard a lot. I would love to see ways to customize it or pin the favourite modules on top.