sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Different Result with Different GPUs (A6000, A40)
Labels: needs reproduction,module: cuda,triaged,module: determinism

### 🐛 Describe the bug

I set most of parameters right but get different result with different GPUs.



### Versions

```
def set_deterministic_pytorch(seed: int):
    # Set CUBLAS workspace config
    cublas_workspace_config = os.environ.get("CUBLAS_WORKSPACE_CONFIG")
    if cublas_workspace_config is None:
        os.environ["CUBLAS_WORKSPACE_CONFIG"] = ":4096:8"

    # Set PyTorch deterministic settings
    os.environ['PYTHONHASHSEED'] = str(seed)

    torch.manual_seed(seed)
    torch.use_deterministic_algorithms(True, warn_only=True) # alternative : torch.use_deterministic_algorithms(True)
    torch.backends.cudnn.deterministic = True
    torch.backends.cudnn.benchmark = False

    torch.utils.deterministic.fill_uninitialized_memory = True

    # Disable TensorFloat32 for consistent precision
    torch.backends.cuda.matmul.allow_tf32 = False
    torch.backends.cudnn.allow_tf32 = False

    # If using CUDA
    if torch.cuda.is_available():
        torch.cuda.manual_seed(seed)
        torch.cuda.manual_seed_all(seed)  # If using multi-GPU
```

cc @ptrblck @msaroufim @eqy @mruberry @kurtamohler
Repository: PowerToys
Issue: Right click menu leftovers after uninstall - "Loading..."
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

File Locksmith

### Steps to reproduce

Install Powertoys.
Uninstall Powertoys.
Right click on any file in the File Explorer.
Several lines with "Loading..." shows on the context menu briefly and then goes away.

![Image](https://github.com/user-attachments/assets/72a8561e-1521-40de-8b48-ede8a5e3ff14)


### ✔️ Expected Behavior

After uninstalling Powertoys, my right click menu should go back to normal behavior.


### ❌ Actual Behavior

Several lines with "Loading..." show on the menu.

### Other Software

_No response_
Repository: PowerToys
Issue: [Settings] ImageResizer preset descriptions do not show units
Labels: Issue-Bug,Product-Settings,Resolution-Fix Committed,Product-Image Resizer

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Settings

### Steps to reproduce

Open the ImageResizer section of the Settings application and observe the **Image sizes** section of the page.

### ✔️ Expected Behavior

The unit should be present after the dimensions, i.e.:

![Image](https://github.com/user-attachments/assets/38733f47-7cb8-4ea1-9485-8e54415951a9)

### ❌ Actual Behavior

The presets each lack the unit designation after the size/percentage text:

![Image](https://github.com/user-attachments/assets/1c36f34c-00f8-42c0-b038-2345b53ad226)

### Other Software

_No response_
Repository: vscode
Issue: Ctrl-click links don't make browser active window
Labels: info-needed


Type: <b>Bug</b>

When clicking 'Follow link' on link hover it does activate browser window, instead they should either both do or don't (preferably do because I had no ideas browser tabs were even opening resulting in a mess of tabs which is bad UX)

![Image](https://github.com/user-attachments/assets/6c070e6f-89a2-4591-b706-355140af06e5)

VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.89GB (0.48GB free)|
|Process Argv|--crash-reporter-id b90a84ae-89ed-45c8-9adb-9989df75643b|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (7)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-eslint|dba|3.0.10
copilot|Git|1.256.0
copilot-chat|Git|0.23.2
vscode-codeql|Git|1.17.0
debugpy|ms-|2024.14.0
python|ms-|2024.22.2
errorlens|use|3.22.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
cf1a2727:31215809
6074i472:31201624

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: Unified Pytorch for Nvidia (CUDA), Intel (XPU), AMD (ROCm)
Labels: module: build,feature,module: rocm,triaged

### 🚀 The feature, motivation and pitch

Allow a single pytorch binary/pkg to support all major gpu platforms. One pytorch env that can execute code on `cpu`, `mps`, `cuda`, `xpu`, and `rocm`. Not 3 torch virtual envs where they can't talk to each other. 

Reasons why we need this:
* It is only the natural solution for end-users
* Pre-built consumer multiple device machines already exist: Arc iGPU (XPU) + Nvidia (CUDA) (LAPTOPS).
* Custom-builds: XPU + CUDA + ROCm in one machine.  No one says you can only have a single device class in a system. 
* LLM models can run optimally using mixed gpus in a more performant way and/or cost effective way. 
* There is no technical reason I can think that shouldn't allow this natural state of multi-device torch env. 
* Developers on multi-device envs are forced to use vritual envs where one device can't talk via pytorch api to another without some shm or rpc magic. 

End-User Problems:
* Driver dependencies. Nvidia drivers are the easiest to use/install with ROCm and Intel/XPU less friendly in that order. 
* Drivers have complex depends and single pkg for all platforms is hard for end-users and they have to do all the prep work

Current state:
* CUDA pytorch can't access XPU or ROCm. 
* Intel XPU enabled Pytorch can't access CUDA or ROCm.
* Amd ROCm pytorch can't access CUDA, or XPU. 


The current state of affairs is bad for pytorch and bad for developers.

Ask yourself this one question:

Why can't Pytorch natively transfer `tensors` from [`cpu`, `mps`, `cuda`, `xpu`, `rocm`] to/from [`cpu`, `mps`, `cuda`, `xpu`, `rocm`] in one environment?



### Alternatives

None. We don't want 3 separate environments. End-users should have the option to have a unified env for all devices. Not all users want this but many will, given the choice is there. Currently there is no choice. 

### Additional context

_No response_

cc @malfet @seemethere @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd
Repository: godot
Issue: Posix formatting strings visible in Visual Studio output on building
Labels: platform:windows,topic:buildsystem,needs testing,regression

### Tested versions

4.4 Master

### System information

Windows 10 - Visual Studio 2022

### Issue description

I have noticed recently that the way the compilation status is displayed in the output has become not very readable, for example we can see text like `[34mCompiling [1mmodules\godot_physics_3d\godot_step_3d.cpp [22;23;24;29m ...[0m.`

For example `1m` and `modules` are written together, is that how it should be?

![Image](https://github.com/user-attachments/assets/6d54091c-170e-4e7d-a851-7db3f8a12b78)

I also see extra symbols (for example `...<-[0m`) what is the point of them?

### Steps to reproduce

Start building the engine on VS 2022

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: Next build fails only in Github Action
Labels: Output (export/standalone)

### Link to the code that reproduces this issue

https://github.com/jpaise/search-frontend

### To Reproduce

```
 - name: Setup pnpm
        uses: pnpm/action-setup@v4
        with:
          version: 10

      - name: Set up Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '18'

      - name: Install dependencies
        run: pnpm install

      - name: Build and Export project
        run: pnpm build
```

this would result 
```
   ▲ Next.js 15.2.0-canary.4

   Creating an optimized production build ...
 ✓ Compiled successfully
   Linting and checking validity of types ...
 ELIFECYCLE  Command failed with exit code 1.
 ``` 
 
 in github action with no clear error message. I've tried `npm`, `yarn` and `pnpm`, all same results. Earlier Nextjs version, same result, if I disable linting, then the error will display in the next step. So pretty much all the possible combinations has been tried. 
 
 next.config.js
 ```
 /** @type {import('next').NextConfig} */
const nextConfig = {
  output: 'export',
  images: {
    unoptimized: true,
    domains: [], // Add any image domains you're using
  },
  trailingSlash: true,
  assetPrefix: process.env.NODE_ENV === 'production' ? './' : '',
  reactStrictMode: true,
}

module.exports = nextConfig
```



### Current vs. Expected behavior

Everything works fine in local (ubuntu) environment, but it just somehow stuck on github action build. All the local env matches cloud ones. 

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #83~20.04.1-Ubuntu SMP Fri Oct 4 21:49:59 UTC 2024
  Available memory (MB): 15992
  Available CPU cores: 4
Binaries:
  Node: 18.20.5
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 10.0.0
Relevant Packages:
  next: 15.2.0-canary.4 // Latest available version is detected (15.2.0-canary.4).
  eslint-config-next: 15.1.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: export
```


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

Output (export/standalone)

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

next build (local), Other (Deployed)

### Additional context

_No response_
Repository: next.js
Issue: Passing data to both client & server component result in always async server tree
Labels: create-next-app,Webpack,Turbopack

### Link to the code that reproduces this issue

https://stackblitz.com/edit/stackblitz-starters-ex8vzvqf?file=app%2Fpage.tsx

### To Reproduce

1. Start the application in development
2. Observe the code inside `page.tsx`, `components/client.tsx` and `components/server.tsx`.
3. Note what the children's type of the `InternalClientComponent` component

### Current vs. Expected behavior

- The children of the `InternalClientComponent` should be of type: `Symbol(React.element)` (or `Symbol(React.transitional.element)` in react-19)
- However, they are of type `Symbol(React.lazy)` indicating that they are suspending or awaiting smth, but they are not, they are a simple `<button>` element.

IMPORTANT NOTES:
- Not passing the `data` property to either the `ClientComponent` or `ServerComponent` resolves the issue, pointing me that this is mostly related to the data reference, not the components themselves.
- It is working with [next@14](https://stackblitz.com/edit/stackblitz-starters-vwuub5bs?description=The%20React%20framework%20for%20production&file=app%2Fpage.tsx,app%2Flayout.tsx,package.json,app%2Fcomponents%2Fclient.tsx&title=Next.js%20Starter)
- If the `data` is of primitive type, it's also working
- Not happening during `build`

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: Ubuntu 20.04.0 LTS Sat Jan 11 2025 21:19:29 GMT+0200 (Eastern European Standard Time)
  Available memory (MB): NaN
  Available CPU cores: 8
Binaries:
  Node: 18.20.3
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 15.2.0-canary.4 // Latest available version is detected (15.2.0-canary.4).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

create-next-app, Turbopack, Webpack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

I tested a different combinations of next 14/15 & react 18/19 as well as `dev` & `build` commands and with `--turbo` flag and webpack respectively - the issue is consistently reproducable since next@15.0.0

I suspect that passing once a reference to a variable get's passed to a client component it gets turned to a promise so it can travel through the network, however there are also server component that are incorrectly reading the promise (instead of the original variable) which turns them into an async tree -> thus subsequent client components are receiving `async` server components regardless if they are suspending or not.
Repository: ui
Issue: [bug]: Responsive Breadcrumb Example Doesn't Work
Labels: bug

### Describe the bug

Looking at the responsive example for the [breadcrumb](https://ui.shadcn.com/docs/components/breadcrumb) component and resizing my browser or opening on my phone doesn't ever seem to trigger the drawer behavior. Is the `useMediaQuery()` hook bugged? 

### Affected component/components

Breadcrumb

### How to reproduce

Look at the docs.

### Codesandbox/StackBlitz link

https://github.com/shadcn-ui/ui/blob/1081536246b44b6664f4c99bc3f1b3614e632841/apps/www/public/r/styles/new-york/breadcrumb-responsive.json#L10

### Logs

```bash
n/a
```


### System Info

```bash
n/a
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: rust
Issue: Status of the riscv32im-risc0-zkvm-elf target
Labels: T-compiler,O-risc0

We currently have a target called `riscv32im-risc0-zkvm-elf`, which targets the [RISC Zero Zero Knowledge VM](https://risczero.com/). This target is maintained by @SchmErik, @jbruestle, @flaub #134721 has revealed some issues in this target.

The biggest issue is that the target sets `target_os = "zkvm"`. A "Zero Knowledge VM" is a generic concept and not an operating system. The correct `target_os` would be `risc0`.

But there is another question, whether this target should exist in the first place. The alternative to this target would be using the existing `riscv32im-unknown-none-elf` target with a RISC0-provided crate for the system calls.

The thing that is currently gained from having this target is that it can have `std`, where the very few syscalls that exist are used to implement some standard library interfaces.
Concretely, the following functionality is provided:
- program arguments
- environment variables (read-only)
- stdio
- the system global allocator
- and of course HashMap
- (no_threads) std::sync

other features like `std::fs`, `std::io`, `std::process`, `std::thread`, `std::time`, `std::net` are not supported.

@SchmErik, who is a maintainer of the target, highlights how the `std` support is useful in https://github.com/rust-lang/rust/pull/134721#issuecomment-2578851596:
> Having std support is important to us because it allows developers to use crates outside of no_std. This has enabled many others to use our target much more easily with existing crates

Additionally, they mentioned how having the target allows them to add cfgs to forked ecosystem crates to make them use more of RISC Zero's APIs (though this could also be implemented without a target and a normal custom cfg).

It is always unsatisfactory to have targets with such incomplete standard libraries (at least it's not as bad as `wasm32-unknown-unknown` in this case). On the other hand, (just like the wasm target) the APIs that are implemented are likely useful.

This issue is about figuring out what to do with this target, whether to keep it (renamed) or remove it alltogether.
Repository: vscode
Issue: Open Recent doesn't include project if closed in 2nd app instance
Labels: feature-request,workbench-history


Type: <b>Bug</b>

Currently the list just builds as projects are opened but if 2 VSCodes are open and more than 10 projects opened in 2nd instance, closing open project in 1st instance will not include in list, even though it was factually among the 2 most recently open ones thus still very relevant/useful to this menu since user will expect it to be there for easy re-access so to fix, project closes must also trigger addition to list (if not already in it, if so a re-bump is even warranted since it was more recently open than the other 9 closed ones that newly buried it and is at risk of losing recency status with only 1 new open)

VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz (4 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.89GB (0.38GB free)|
|Process Argv|--crash-reporter-id b90a84ae-89ed-45c8-9adb-9989df75643b|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (7)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-eslint|dba|3.0.10
copilot|Git|1.256.0
copilot-chat|Git|0.23.2
vscode-codeql|Git|1.17.0
debugpy|ms-|2024.14.0
python|ms-|2024.22.2
errorlens|use|3.22.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
cf1a2727:31215809
6074i472:31201624

```

</details>

<!-- generated by issue reporter -->
Repository: langchain
Issue: [Bug] Arg Returns in docstring not found in function signature even when it is provided
Labels: 🤖:bug,Ɑ:  core

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


## Steps to Reproduce:

Create a Python function with type hints in the signature.
Add a detailed docstring that includes type information in the "Args" and "Returns" sections.
Try to run the function and observe the failure.
Example Code:

Below is a self-contained, minimal, reproducible example demonstrating the issue:

from typing import Optional, List, Tuple

def read_orders(customer: Optional[str] = None) -> List[Tuple[int, str, str, int, str]]:
    """
    Reads orders from the orders table. If a customer name is provided, it retrieves orders for that customer.

    Args:
    - customer (str, optional): Name of the customer to filter orders by. If None, all orders are retrieved.

    Returns:
    - List[Tuple[int, str, str, int, str]]: A list of orders where each order is represented as a tuple containing:
        - order_id (int)
        - customer_name (str)
        - product_name (str)
        - quantity (int)
        - order_date (str)
    """
    
## How I fix it 
By delling the args and returns 
    
    
    

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


 130 if docstring_arg not in annotations:
    131     msg = f"Arg {docstring_arg} in docstring not found in function signature."
--> 132     raise ValueError(msg)

ValueError: Arg - customer (str, optional) in docstring not found in function signature.


### Description

## Description:
I am encountering an issue when using type declarations in both function signatures and docstrings in Python. The problem arises when I add type information in the docstring along with the type hints in the function signature. The function fails to execute correctly if both have type declarations.


### System Info

System Information
------------------
> OS:  Darwin
> OS Version:  Darwin Kernel Version 23.6.0: Thu Sep 12 23:36:12 PDT 2024; root:xnu-10063.141.1.701.1~1/RELEASE_ARM64_T6020
> Python Version:  3.10.0 (default, Mar  3 2022, 03:54:28) [Clang 12.0.0 ]

Package Information
-------------------
> langchain_core: 0.3.29
> langchain: 0.3.13
> langchain_community: 0.3.13
> langsmith: 0.2.7
> langchain_openai: 0.3.0
> langchain_text_splitters: 0.3.4
> langgraph_cli: 0.1.65
> langgraph_sdk: 0.1.48
Repository: ui
Issue: CanvasRevealEffect does not work on react 19 bc cant import * as THREE from "three";
Labels: area: request

### Feature description

CanvasRevealEffect does not work on react 19 bc cant import * as THREE from "three";

even if you npm install --force framer-motion clsx tailwind-merge three @react-three/fiber
it wont work 


<img width="409" alt="Screenshot 2025-01-11 at 3 16 34 PM" src="https://github.com/user-attachments/assets/5f836d16-c795-4b17-bdd2-94064b4b4b7d" />


### Affected component/components

component/ui/canvas-reveal-effect

### Additional Context

even if you npm install --force framer-motion clsx tailwind-merge three @react-three/fiber
it wont work 


next.js 15 and react 19 I'm on

### Before submitting

- [X] I've searched for existing issues and PRs
- [X] I've made research efforts and searched the documentation
Repository: PowerToys
Issue: MacOS / Linux like screenshot feature
Labels: Needs-Triage

### Description of the new feature / enhancement

Provide MacOS-like screenshot utility that could take screenshot and save the place of screenshot for another one (like CMD+SHIFT+5)

### Scenario when this would be used?

Power user is taking a lot of screenshots to document his job. The feature would help to remain professional and standarize the screenshot size.

### Supporting information

_No response_