sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: After update, app is completely unusable
Labels: bug,gpu

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.95
- OS Version: Ubuntu 22.04.4 LTS

Steps to Reproduce:

1. Open vscode
2. Screen is gray, buttons are unresponsive, even after reboot.
3. ![Image](https://github.com/user-attachments/assets/a022acfc-676d-4b19-b18d-c83428c8b8e7)
Repository: next.js
Issue: Multiple Google fonts not accessible globally, when imported in the root layout page, in the same format as the init. Geist fonts.
Labels: bug,Font (next/font)

### Link to the code that reproduces this issue

https://github.com/winterdelta/font-investigate

### To Reproduce

Init. a new `repo`, e.g. via `bun create next-app`. Import `next/google/fonts`. Add the `fonts` in the root layout component:


```
import { IBM_Plex_Mono, IBM_Plex_Sans } from "next/font/google";

<body className={`${ibm_mono.className} ${ibm_sans.className}`}>
    {children}
</body>
```


Here, if the order of the fonts is:

- mono and sans (in sequence) > mono font will be default, throughout the app.
- sans and mono (in sequence) > sans font will be default, throughout the app.

even if the CSS variable, e.g. `font-family: var(--font-ibm-plex-mono);` declares otherwise.

The second font will not be available, e.g. when declared via CSS variables, possibly, other inconsistent behaviour too.

### Current vs. Expected behavior

On init., 2 Geist fonts are installed via `create next-app` and are declared as a template-literal in the root layout. If the user replaces these local Geist fonts for Google fonts **in the same format**, only the first font will be accessible. Additional / multiple fonts will not be accessible from nested components.

---

Behaviour for Google fonts should match the behaviour of the Geist local fonts. Adding multiple fonts as template literals into the root body tag should allow access through nested components.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Fri Aug 16 19:20:34 PDT 2024; root:xnu-11215.40.42~4/RELEASE_ARM64_T8112
  Available memory (MB): 8192
  Available CPU cores: 8
Binaries:
  Node: 22.2.0
  npm: 10.7.0
  Yarn: 1.22.21
  pnpm: 9.0.6
Relevant Packages:
  next: 15.0.3-canary.1 // Latest available version is detected (15.0.3-canary.1).
  eslint-config-next: 15.0.1
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


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

Font (next/font)

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

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

_No response_
Repository: pytorch
Issue: Draft-mode export: ep.run_decompositions() doesn't run with real tensor prop
Labels: triaged,oncall: pt2,export-triaged,oncall: export

Repro: patch in https://github.com/pytorch/pytorch/pull/139213 (needed for an error to show up), then run the following script:
```py
import torch
import torch._functorch.config

@torch.library.custom_op("export::foo", mutates_args={}) # E: Untyped decorator makes fun
def foo(x: torch.Tensor, y: torch.Tensor) -> torch.Tensor:
    return x * y

class Foo(torch.nn.Module):
    def forward(self, x, y): # E: Function is missing a type annotation  [no-untyped-def]
        return foo(x, y)

model = Foo()
inputs = (torch.randn(1, 3), torch.randn(2, 1))
with torch._functorch.config.patch(fake_tensor_propagate_real_tensors=True):
    ep = torch.export.export_for_training(model, inputs)
    nodes = list(ep.module().graph.nodes)
    ep.run_decompositions({})
```

What's going on is that:
- the included PR allows real_tensor_prop to infer a meta kernel for an operator during export
- the exported program does not include real tensors along with the FakeTensors (should it?)
- run_decompositions does some re-tracing without propagate_real_tensors because there are no real tensors
- run_decompositions errors due to no meta (the inferred meta kernel isn't persistent)

A fix could be that "if you're not decomposing the operator, then run_decompositions uses the existing FakeTensors to infer a meta kernel". But there's a more general question of if there are any more downstream graph passes that will have problems due to not having access to the real tensors.





cc @ezyang @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: pytorch
Issue: test/export/test_retraceability.py fails locally, likely flaky
Labels: triaged,oncall: pt2,export-triaged,oncall: export

test/export/test_retraceability.py fails locally for me, when running head to toe:
```
FAILED [0.2012s] test/export/test_retraceability.py::RetraceExportTestExport::test_slice_with_floordiv_retraceability - AssertionError: RuntimeError not ra...
FAILED [0.1438s] test/export/test_retraceability.py::RetraceExportNonStrictTestExport::test_slice_with_floordiv_retraceability_non_strict - AssertionError:...
```
When running the tests individually, they pass.



cc @ezyang @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: vscode
Issue: still cannot open files or folders in linux 24
Labels: bug,snap,confirmation-pending,native-file-dialog

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.94.x and the new version 1.95
- OS Version: Linux Ubuntu KDE 24.04 

Steps to Reproduce:

1. File -> Open http://shot.screen1.me/dv9qzSzKXyQY8mGqpqpzw4.png
2 - System crashed after open folder or file : http://shot.screen1.me/x8TQFwWmkH5xLhdEuUvMDg.png

I am using version 1.93.1 to continue using the IDE normally.
Repository: react
Issue: [compiler] Support annotating hook factories that produce stable hooks
Labels: Type: Feature Request,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

nope

### Repro steps

The application I'm developing follows a specific pattern for accessing Redux store data based on parameters. Here's an example:

```jsx
const ProductTile = ({ productId }) => {
  const useProductSelector = createUseSelectorWithParam(productId)
  const title = useProductSelector(productStore.selectLabel)
  const value = useProductSelector(productStore.selectValue)
  const brandId = useProductSelector(productStore.selectBrandId)

  const useBrandSelector = createUseSelectorWithParam(brandId)
  const subTitle = useBrandSelector(brandStore.selectLabel)

  return <Tile title={title} value={value} subTitle={subTitle} />
}
```

We currently use this "higher-order function" (HOF) approach in several thousand places across the codebase, with code like the following:

```jsx
export const createUseSelectorWithParam = (param) => {
  const useSelectorWithParam = (selector) =>
    useSelector((state) => selector(state, param))

  return useSelectorWithParam
}
```

This approach reduces code complexity (fewer arrow functions) and enhances team productivity by decreasing informational noise. However, it currently lacks compatibility with the new React Compiler.

**Question**: Is there a way to inform the React Compiler that the result of `createUseSelectorWithParam` should be treated as a stable hook?

We're hesitant to replace thousands of instances across the codebase with arrow functions or to add parameters universally, as it would likely reduce readability (sometimes only one parameter is needed to access Redux store data, but other times two or even three are required). Additionally, with a higher number of parameters, making such extensive changes could lead to more bugs, as manually adjusting parameters in multiple places increases the chance of errors.

### How often does this bug happen?

Every time

### What version of React are you using?

18.2

### What version of React Compiler are you using?

19.0.0-beta-6fc168f-20241025
Repository: langchain
Issue: DOC: DuckDuckGo community tool docs describing an `output_format` option that is not on the published referenced version
Labels: 🤖:docs

### URL

https://python.langchain.com/api_reference/community/tools/langchain_community.tools.ddg_search.tool.DuckDuckGoSearchResults.html#langchain_community.tools.ddg_search.tool.DuckDuckGoSearchResults.output_format

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

The [referenced documentation](https://python.langchain.com/api_reference/community/tools/langchain_community.tools.ddg_search.tool.DuckDuckGoSearchResults.html#langchain_community.tools.ddg_search.tool.DuckDuckGoSearchResults.output_format) shows an `output_format` option, that is only available on the latest `master` code, however, the documentation for version `0.3.3` states that it's available on that version.

The code on the `0.3.3` tag doesn't include this option https://github.com/langchain-ai/langchain/blob/langchain-community%3D%3D0.3.3/libs/community/langchain_community/tools/ddg_search/tool.py#L77.



### Idea or request for content:

It seems like the documentation and published dependency are not in sync; publishing a new version and updating the documentation accordingly should fix the issue.

For a deeper fix, there might be some deployment synchronization that needs to take place to prevent the issue.
Repository: angular
Issue: Trigger computed signals on mutated value using custom equality
Labels: area: core,core: reactivity,cross-cutting: signals

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

core

### Is this a regression?

No

### Description

Hello to the awesome Angular team 😍

Since js still supports mutating arrays with simple means such as push() etc :)... And it's still a common practice in a lot of codebases...

I hoped that pushing a new item to an array inside a signal, would trigger the computed signal.
Obviously I see now that since the reference of the array object stays the same, 
I have to use .slice() or some other means to create a new array instance after every signal.update(...).
While that is a solution, i hoped that using the custom equality option i could equate the actual array content or length before and after the change,
thus making the code cleaner, even though the framework would need to work a little harder to find out if its the same or not...

Problem is, I found out that if I only mutate the array and not create a new instance (ie items.push(...); return items;) ,
the custom equal function gets the same object as as the "a" and "b" parameters... 
Apparently the framework didn't save an old copy of the signal value before the change, and there is no way to know that it's changed.

I realize this could make things more complicated and might not make sense performance-wise, 
but i decided to raise the issue for your consideration, since it could make sense in certain applications, and since Signals are still being in dev preview...

I put up a stackblitz reproducing this issue.

Thanks a lot!!!

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

https://stackblitz.com/edit/stackblitz-starters-ta7t5b?file=src%2Fmain.ts

### Please provide the exception or error you saw

_No response_

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

Angular CLI: 18.2.7
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 18.2.7
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1802.7
@angular-devkit/build-angular   18.2.7
@angular-devkit/core            18.2.7
@angular-devkit/schematics      18.2.7
@schematics/angular             18.2.7
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.14.10

### Anything else?

_No response_
Repository: ollama
Issue: Docs: Add Linux manual instructions that can run without root / sudo
Labels: feature request

## Description

In the [Linux manual install instructions](https://github.com/ollama/ollama/blob/main/docs/linux.md#manual-install), the commands are shown requiring `sudo` access. This is usually fine with personal machines, but often isn't for shared or managed machines. The request here is to add instructions on how to install without `root` access.

## Proposal

I'm happy to contribute the README PR. Here are my suggested changes:

---

## Manual install

### Download and extract the package:

```shell
curl -L https://ollama.com/download/ollama-linux-amd64.tgz -o ollama-linux-amd64.tgz
sudo tar -C /usr -xzf ollama-linux-amd64.tgz
```

### Non-root install

For those installing without root/sudo access, the install can also be done in user space with the appropriate additions to `PATH` and `LD_LIBRARY_PATH`:

```shell
curl -L https://ollama.com/download/ollama-linux-amd64.tgz -o ollama-linux-amd64.tgz
# Substitute any place you have write access for ~/.local
mkdir -p ~/.local
tar -C ~/.local -xzf ollama-linux-amd64.tgz
# Place this in your ~/.bashrc to persist
export PATH=$HOME/.local/bin:$PATH
export LD_LIBRARY_PATH=$HOME/.local/lib/ollama:$LD_LIBRARY_PATH
```

### Start Ollama:

```shell
ollama serve
```

In another terminal, verify that Ollama is running:

```shell
ollama -v
```
Repository: ui
Issue: Using force install or peer deps is unacceptable and will break a lot of production environments in the future
Labels: bug

### Describe the bug

Running force install is a terrible idea, even knowing that this installation works, I'm installing that in production, and you will produce a lot of issues in production environment in future by being lazy. In facts if you deps are outdated you don't support Next 15


https://github.com/shadcn-ui/ui/issues/5637

### Affected component/components

toast,radio-group,pagination,navigation-menu,drowdown-menu,dialog,command

### How to reproduce

https://github.com/shadcn-ui/ui/issues/5637

### Codesandbox/StackBlitz link

https://codesandbox.io/p/devbox/busy-breeze-go8s7s

### Logs

```bash
https://github.com/shadcn-ui/ui/issues/5637
```


### System Info

```bash
https://github.com/shadcn-ui/ui/issues/5637
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Default word wrap setting is no longer applied to open files when VS Code is relaunched
Labels: bug,editor-wrapping


Type: <b>Bug</b>

I am using the default word wrap settings, which wraps the lines of Markdown files when I open them during a session. However if I leave a Markdown file open when I close Code, its lines are no longer wrapped when I relaunch the application. To wrap them, I either have to type `Alt + z` or close and reopen the file.

Steps to reproduce:

1. Open [Jack.md](https://github.com/user-attachments/files/17575457/Jack.md) in Code and observe that the long line is wrapped.
2. Close code and relaunch it. Ensure that the file is automatically reopened -- do not manually reopen it.
3. Observe that the long line is no longer wrapped.

This occurs with all extensions disabled. I tried to reproduce it in the latest Insiders build, but I couldn't work out how to get it to reopen files that were open in the last session.

To be clear, this is not a duplicate of https://github.com/microsoft/vscode/issues/103199 . That issue is a request for the preservation of custom word wrap settings per file, whereas I am pointing out that Code doesn't always honour the default settings.


VS Code version: Code 1.95.0 (912bb683695358a54ae0c670461738984cbb5b95, 2024-10-28T20:16:24.561Z)
OS version: Linux x64 5.15.0-124-generic
Modes:

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

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz (8 x 1219)|
|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: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off<br>webnn: disabled_off|
|Load (avg)|1, 1, 1|
|Memory (System)|7.45GB (4.33GB free)|
|Process Argv|--crash-reporter-id a5f80cc2-1946-4a5a-b5a0-95b3d7c0f4dc|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|unity|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|unity|
|XDG_SESSION_TYPE|x11|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
da93g388:31013173
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
iacca2:31156134
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue:  OptionButton dropdown not properly inheriting scale of parent CanvasLayer in 4.3
Labels: bug,topic:gui

### Tested versions

- Reproducible in: 4.3.stable

### System information

Apple - Apple M1 Pro Godot Engine v4.3.stable.official.77dcf97d8 API 4.1 Metal

### Issue description

This is a duplicate of issue #94247 only that I am able to reproduce the same bug in v4.3

### Steps to reproduce

Increase or reduce the scale of the parent Control node, the OptionButton dropdown won't inherit the scale.

![Screenshot 2024-10-30 at 11 25 03](https://github.com/user-attachments/assets/eaa250cd-11e4-4f72-a0d8-120b75a3a976)
![Screenshot 2024-10-30 at 11 24 43](https://github.com/user-attachments/assets/198c5a15-f48b-496d-968b-3bfd3a69a880)

### Minimal reproduction project (MRP)

[bug-report.zip](https://github.com/user-attachments/files/17575562/bug-report.zip)
Repository: pytorch
Issue: Using xpu module in the cuda version Pytorch
Labels: module: build,module: cuda,triaged,enhancement,module: xpu

### 🚀 The feature, motivation and pitch

I am working on building a demo that using NV GPU as a comparison with intel XPU.
Additionally, I wonder if it's possible to distribute part of the computations in some tasks to the XPU while using NV GPU.
Therefore, I would like to ask if there are plans to merge the intel /test/xpu branch with the cuda branch?

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet @seemethere @ptrblck @msaroufim @gujinghui @EikanWang @fengyuan14 @guangyey
Repository: godot
Issue: Anonymous lambdas can be randomly assigned a new context object if the original context object is missing at the time of invocation
Labels: bug,topic:gdscript

### Tested versions

Reproducible in 4.3.stable

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 SUPER (NVIDIA; 32.0.15.6590) - Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 Threads)

### Issue description

When you make an anonymous lambda that contains a reference to a local variable or function in the current script where the lambda is defined, and then this lambda is later called when the current node is missing, Godot can (unpredictably) bind this lambda to a completely different node.

In the case that the new node does not have the same members, it will throw an error like in the screenshot below, which is super confusing. But an even more dangerous case I have encountered is if the new node *does* share the same members being referenced in the lambda (i.e. `position` or `name`). In this case, the lambda will silently proceed with the wrong target node as though nothing is wrong, leading to a silent bug that can be almost impossible to diagnose.

In the screenshot below, the `story.gd` script attached to the `story` node is where the error occurs. The lambda being constructed contains a call to a function `_perform_place_transition` which is local to `story.gd`. However, at runtime, the lambda construction fails. The error message and the `self` field in the debugger window both say that the error is occuring on a completely different node in the scene - the `tf_mirror` node under the right eye of a penguin.

Godot will randomly re-bind the lambda to one of a few other nodes, or it will not re-bind at all. There appears to be no pattern as to how it chooses how/whether to re-bind.

![38cc0f5f-5187-4ee0-a291-1177b9d19055](https://github.com/user-attachments/assets/38cc0f5f-5187-4ee0-a291-1177b9d19055)

The problem line of code:
```Game.loader.queue_load_op(func(): await _perform_place_transition(place_name, spawn_point_name))```
The rebinding bug *still occurs* if the lambda does not contain an `await`:
```Game.loader.queue_load_op(func(): _perform_place_transition(place_name, spawn_point_name))```
The rebinding bug *does NOT occur* if an anonymous lambda is not used:
```Game.loader.queue_load_op(_perform_place_transition.bind(place_name, spawn_point_name))```

Just to be clear:
It is a user bug to allow an anonymous lambda to be invoked on a no-longer-valid object. The bug being reported here is the random re-binding being done by Godot.

### Steps to reproduce

I can't share my entire commercial project, and I have attempted but not succeeded in making a reduced or fresh repro project.

### Minimal reproduction project (MRP)

N/A