sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: devtools injector tree tab doesn't show a provider from root injector
Labels: area: devtools

### Which @angular/* package(s) are the source of the bug?

devtools

### Is this a regression?

Yes

### Description

**A provider within the root injector should be shown, but it's not.** The injectable to be found within devtools tab is called `SignalStore` (created by `@ngrx/signals` package).

REPRO steps:
- run the app
- click to the "EMPLOYEES" link (to enable routing and display components)

SETUP
- the SignalStore is injected in only 1 place:
  - employee-listing component
- the SignalStore is provided in 4 places:
  1. employee-listing component
  2. employee-page component (parent)
  3. route (app.routes.ts)
  4. in root injector

While browsing through "injector tree" tab I can see all of them WITHOUT the root one:

(1)

https://github.com/ducin/angular-bug-repros/blob/devtools_injector_tree_provider_missing_in_root_injector/src/app/employees/employee-listing.component.ts#L24

![image](https://github.com/user-attachments/assets/ddbdaf97-cb50-4d5b-9e23-e7f10619b230)

(2)

https://github.com/ducin/angular-bug-repros/blob/devtools_injector_tree_provider_missing_in_root_injector/src/app/employees/employee-page.component.ts#L21

![image](https://github.com/user-attachments/assets/56b1543c-24b2-47ae-9d41-047eb2b065f1)

(3)
https://github.com/ducin/angular-bug-repros/blob/devtools_injector_tree_provider_missing_in_root_injector/src/app/app.routes.ts#L17

![image](https://github.com/user-attachments/assets/ecce3785-ca53-41df-84e7-d9aff30d4a78)

BUT for the root injector (4) it's not there:

https://github.com/ducin/angular-bug-repros/blob/devtools_injector_tree_provider_missing_in_root_injector/src/app/employees/employee-store.ts#L35

![image](https://github.com/user-attachments/assets/8d4b054d-1dbb-400b-abf0-dd4165a8304b)
 


### Please provide a link to a minimal reproduction of the bug

https://github.com/ducin/angular-bug-repros/tree/devtools_injector_tree_provider_missing_in_root_injector

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
angular v18.1.3, devtools: 1.0.17
node: v20.13.1
npm: 10.5.2
os: macos sonoma v14.5
```


### Anything else?

There is a slight possibility that this is related to ngrx/signals itself, but, basing on the code below, I don't think so...

https://github.com/ngrx/platform/blob/main/modules/signals/src/signal-store.ts#L1344C9-L1350

CC @markostanimirovic 

Also, when all providers are removed (1-component, 2 - parent component, 3 - route) and only `"providedIn": root` is left, then the SignalStore provider is visible

![image](https://github.com/user-attachments/assets/eb452a81-81b7-4294-bca8-0581b61d72af)

**however, this is NOT expected behavior**
Repository: vscode
Issue: Error in "diffEditor.revert" command when invoked though keybinding
Labels: bug,diff-editor

Type: <b>Bug</b>

Tried this on stable and insider version of vscode with disabled extensions.
Open some dir, with two files, open first file to edit select 'compare with ...' command, diff editor opened, cursor to any difference, see right arrow icon between splitted panes, right click on it and assign keybinding, go back to splitted pane, pass assigned key, see errror: "Cannot read properties of undefined (reading 'originalUri')"

VS Code version: Code - Insiders 1.93.0-insider (b45f04309feede3182ac4a7b945df1e64663a222, 2024-08-14T05:03:36.595Z)
OS version: Linux x64 6.8.0-40-generic
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 4600H with Radeon Graphics (12 x 3977)|
|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)|2, 1, 1|
|Memory (System)|15.00GB (2.87GB free)|
|Process Argv|--disable-extensions --user-data-dir /tmp/vscode-ins --crash-reporter-id 9e3e11ab-a688-49f4-a1e5-3de3e12bca29|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|ubuntu-xorg|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu-xorg|
|XDG_SESSION_TYPE|x11|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
vsaa593:30376534
py29gd2263:31024238
c4g48928:30535728
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonnoceb:30776497
asynctok:30898717
dsvsc014:30777825
dsvsc015:30821418
pythonregdiag2:30926734
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
g316j359:31013175
a69g1124:31018687
dvdeprecation:31040973
dwnewjupyter:31046869
legacy_priority:31057981
nativerepl1:31104042
refactort:31084545
pythonrstrctxt:31093868
flighttreat:31105043
wkspc-onlycs-c:31111717
nativeloc1:31111755
wkspc-ranged-t:31111713
cf971741:31111988
jh802675:31111929

```

</details>

<!-- generated by issue reporter -->

![image](https://github.com/user-attachments/assets/f65498e1-e322-4322-a6a1-d274f81cc01c)
Repository: react
Issue: [React 19] No re-render after 'useActionState' action queue finishes
Labels: Type: Bug,React 19

## Summary

When multiple client side actions are scheduled via `useActionState`, the "Action queue" promises are processed sequentially as expected. However after the last action promise resolves, the component is not re-rendered. This means, the component is stuck in "loading" without access to "data".

### Steps to reproduce

1. Open the demo here: https://codesandbox.io/p/sandbox/use-action-state-stuck-xl72xk?file=%2Fsrc%2FApp.js
2. Click the "Send request" button two times.
3. After 10 seconds (each request is 5 seconds and processed sequentially), the component still shows "Loading..." and not the dummy data (as I would expect).


#### Notes
* When only one "action" is scheduled (button clicked once), the component re-renders when the action is done, as expected.
* The promise "delay" seems to have an effect. When `REQUEST_DELAY` is set lower i.e. 1000ms, this "issue" is not present.
* Possibly related: https://github.com/facebook/react/issues/27630

Is this behavior intentional?
Repository: stable-diffusion-webui
Issue: [Bug]: Runtime error , torch is not able to use GPU
Labels: bug-report

### Checklist

- [ ] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [ ] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

I'm sorry, I'm a french man and totally newbie here.
I'd like to install stable diffusion just to create AI image for fun :)
I try my best to follow this tutorial https://www.youtube.com/watch?v=onmqbI5XPH8&t=4s...

I've been trying for 3 days now to install,unistall it and run into a lot of different problem (python localisation, web.user bat...)
Today I followed up this video below. It was fine until to the point it saying that 
![Capture d’écran 2024-08-14 140328](https://github.com/user-attachments/assets/9f6e1414-5886-4322-a3cf-ff81819121dd)

As someone suggested I try to add a line oneweb-user.bat file to skip the conda check-up and even uninstall the VERV file in order to create another one. I updated pip files etc... It's really infuriating as every time I'm about to manage to install it, there's always an error somewhere... The installation is clean...

### Steps to reproduce the problem

As the Youtube video says...

### What should have happened?

I should the installation done and got an URL adress on the cmd to use it to have stable diffusion...

### What browsers do you use to access the UI ?

Google Chrome

### Sysinfo

?

### Console logs

```Shell
?
```


### Additional information

I'm sorry, i'm unable to replies to the above questions because I'm totally new to it and didn't find the console log or the sysinfo...
Repository: rust
Issue: Tracking Issue for box_as_ptr
Labels: C-tracking-issue,T-libs,A-box

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(box_as_ptr)]`

This is a tracking issue for `Box::as_ptr` and `Box::as_mut_ptr`.

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
impl<T: ?Sized, A: Allocator> Box<T, A> {
    pub fn as_mut_ptr(b: &mut Self) -> *mut T;
    pub fn as_ptr(b: &Self) -> *const T;
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] ACP: https://github.com/rust-lang/libs-team/issues/355
- [ ] Implementation: https://github.com/rust-lang/rust/pull/129091
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: vscode
Issue: `Load More Stack Frames` renders poorly when horizontalScrolling enabled
Labels: bug,debug

<!-- ⚠️⚠️ 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?: N/A (need *some* debugger extension to test)

<!-- 🪓 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.92.1
- OS Version: Arch LInux x64 6.6.44-3-lts

Steps to Reproduce:

1. Open the debugger for any language.
2. Pause on a breakpoint. Either with a deep enough stack so that it doesn't load fully and shows `Show N More Stack Frames` message. OR some debugger extensions apparently don't load the stack at all by default, and display `Load More Stack Frames` after the first entry.
3. Make sure the stack frames already shown have very long names.
4. Observe that the `Load More Stack Frames` (or `Show N More Stack Frames`) is centered relative to the longest frame name, making it completely invisible if frame names are long and the panel is narrow. See picture:

Completely invisible on small panel widths:
![pic](https://github.com/user-attachments/assets/c57c1294-8211-4514-b1af-8ba057f56b8a)

Only starts appearing on large panel widths:
![pic](https://github.com/user-attachments/assets/49bec37b-1ab3-4976-9bae-1dc9e4f9c180)

I suggest that this text should be centered based on the physical panel width (ignoring the scroll).
Repository: vscode
Issue: Drag sideways on minimap to pan?
Labels: feature-request,editor-minimap

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Drag sideways on minimap code/outline to scroll sideways.

Possibly hold down `Ctrl` key or similar to enable this behaviour to prevent unintentional sideways scrolling.

I think it would be 🌈**amazing**🌈 for wide documents :D ❤️
Repository: godot
Issue: C# Compute Shaders run significantly slower than GDScript compute shaders. (Godot 4.3 RC3)
Labels: bug,topic:rendering,topic:dotnet,performance

### Tested versions

- Reproducible in Godot 4.3 RC3

### System information

EndeavorOS Linux (Arch based). CPU - Intel i7-1165G7 (iGPU). Drivers - vulkan-intel/mesa

### Issue description

Project using a GPU Poisson Disk Sampling shader. When running via c# version of rd.Submit(), shader takes upwards of 300-500ms each to run. 
When calling from a GDScript version though, (even from inside a C# program) each shader runs in < 5ms. 

Huge discrepancy, and not entirely sure if this is a bug, or just a current limitation of the C# implementation. 

### Steps to reproduce

Load up MRP, in Main, toggle "Gd Script Shader" export variable on and off. Time Elapsed in ms is posted to Output terminal. GDScript version of Shader Code runs in < 150ms total whereas the C# version of the Shader code takes almost 3.5s. 

Both use the same glsl file. 

### Minimal reproduction project (MRP)

[Archive.zip](https://github.com/user-attachments/files/16613598/Archive.zip)
Repository: pytorch
Issue: [BE] Deduplicate auto_functionalized and triton_kernel_wrapper_functional
Labels: triaged,oncall: pt2,module: pt2-dispatcher,module: user triton

These do the same thing - they're a functional wrapper around something that is mutable.

cc @ezyang @chauhang @penguinwu @bdhirsh @oulgen @aakhundov
Repository: angular
Issue: Duplicate trusted type policy error when using an angular app with a  webcomponent that embeds an angular app
Labels: area: elements

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

- We have an angular application that uses an angular webcomponent. 
- We do not allow duplicates in the CSP header ( and we would like to avoid it )
- This causes an issue, because angular cannot create its trusted policy on the webcomponent ( they are already created by the main app ), and the webcomponent cannot work properly

- Is there a workaround ( apart from allowind duplicates ) ?
- Is there a way to rename the policy that angular create ( so we can avoid creating duplicate policy ) ?

This affect every angular app that 
- embeds an angular element
- has trusted type enabled and do not allow duplicate

### Please provide a link to a minimal reproduction of the bug


### Please provide the exception or error you saw

```true
TypeError: Failed to execute 'createPolicy' on 'TrustedTypePolicyFactory': Policy with name "angular" already exists.
```


### Please provide the environment you discovered this bug in (run `ng version`)

_No response_

### Anything else?

_No response_
Repository: pytorch
Issue: Collect tensor shapes only when using record_shapes in profiler
Labels: oncall: profiler

### 🚀 The feature, motivation and pitch

Currently, the record_shapes option in the PyTorch Profiler holds references to tensors until profiling is completed. This behavior can lead to increased memory usage and potential memory leaks, especially when profiling large-scale models or long-running tasks. Instead of keeping references to tensors, the profiler could capture the shapes of the tensors at the moment they are encountered during profiling. 




### Alternatives

_No response_

### Additional context

The tensors are held inside TorchOpStorage::torch_ops_::_input_outputs_

cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise
Repository: go
Issue: proposal: golang.org/x/net/html: Add Tokenizer as Option to html.ParseWithOptions()
Labels: Proposal

### Proposal Details

### **Issue**

I was working with parsing HTML data, and I ran into an issue. When something like
`<![CDATA[ .... ]]>`
came up, the default html.Parse() method will parse that as an html comment. Calling html.Render() yields:
`<!--[CDATA[ .... ]]-->`
creating a comment that isn't useful.
String manipulation can be used to get around this, but I know that under the hood the html.Tokenizer has the method:
`func (z *Tokenizer) AllowCDATA(allowCDATA bool)`
which sets the tokenizer to process this properly.

### **Proposed Solution**
I propose that the user be allowed to set the html.Tokenizer used by the html.Parse()/html.ParseWithOptions() methods. Under the hood, ParseWithOptions() creates a new html.Tokenizer based on the io.Reader passed to it. If the user was also allowed to pass the Tokenizer used by the parser, the user could then set those options as appropriate/necessary, avoiding the above problem.

This could be solved by adding an html.ParseOption. Namely:
```
func ParseOptionWithTokenizer(tokenizer *Tokenizer) ParseOption {
	return func(p *parser) {
		p.tokenizer = tokenizer
	}
}
```

and this would be called like:
```
tokenizer := html.NewTokenizer(myReader)
tokenizer.AllowCDATA(true)

html.ParseWithOptions(myReader, html.ParseOptionWithTokenizer(tokenizer))
```

The name of the method can be changed as well to whatever makes more sense.
Repository: vscode
Issue: Add quick fix for npm vulnerabilities
Labels: feature-request,npm

Suggestion from Brigit that we cover this type of output with a quick fix:

![image](https://github.com/user-attachments/assets/5eb638db-f782-4a1a-b7d7-eb74475d73d4)

Currently npm quick fixes:

https://github.com/microsoft/vscode/blob/45feb8c9e43964dd9f16c40745c0d990e707ca55/extensions/npm/src/npmMain.ts#L74-L96
Repository: pytorch
Issue: [randperm] Add argument to disallow identiy mappings
Labels: triaged,module: random

### 🚀 The feature, motivation and pitch

The `randperm` function is very useful, but in some scenarios I would like to disallow identity mappings; i.e. for a tensor with indices `i` and 'values' `v`, the output of `randperm` should guarentee that  `i != v`. 

The new definition of randperm, would then look something like
```
torch.randperm(n, *, generator=None, out=None, dtype=torch.int64, layout=torch.strided, device=None, requires_grad=False, pin_memory=False, allow_identity_mapping=True) or 
torch.randperm(n, *, generator=None, out=None, dtype=torch.int64, layout=torch.strided, device=None, requires_grad=False, pin_memory=False, disallow_identity_mapping=False)
```

### Alternatives

_No response_

### Additional context

I have a simple implementation in python that does exactly this. It could serve as a wrapper around the internal `randperm` functions, by simply mutating the output of the underlying C/Cuda/.... If this, however, will not do, I am willing to attempt a foray into the depths of `ATen`.

---
Tagging you since you seem to be involved in the development of this part of the code base (based on previous issues).
@angelayi @SherlockNoMad 

cc @pbelevich
Repository: kubernetes
Issue: Emulation version: Remove hard coded DefaultKubeBinaryVersion value.
Labels: sig/api-machinery,triage/accepted

Let's find a way to replace this hard coded version number with something we don't need to manually update each version:

https://github.com/kubernetes/kubernetes/blob/b6b7abc871a55ce26bc62c0d5452b73077364395/staging/src/k8s.io/component-base/version/base.go#L69

xref:

https://github.com/kubernetes/kubernetes/pull/126604/files#r1715877080
Repository: ollama
Issue: Honor/use amdgpu.gttsize Kernel parameter to use all unified memory for AMD APU
Labels: feature request

Hi,

I do have a feature request.

**System**
- Ollama v0.3.6
- Fedora 40 (Kernel 6.10.3)
- AMD APU Ryzen 7840u / 780m
- 64 GB RAM
- ROCM 6.1.1

**Info**
Kernel 6.10.3 supports setting amdgpu.gttsize to values like 32768 which I think works around the issue many have with an AMD APU. They can only set a few values for GPU memory in their BIOS mostly not more than 8 GB. Since the memory is always the same pool, it would be nice if Ollama offloaded compute to the GPU in such cases as well.

**Example:**
Bios GPU memory allocation set to auto
amdgpu.gttsize=32768

--> ollama run gemma2:27b "Tell me a joke"

This runs at 100% on the CPU as the model is 16GB

On the other hand, running (./llama-bench) an even bigger model directly with llama.cpp on the GPU works:

> | model                                         |            size |     params | backend    | ngl |             test |                     t/s |
> | llama 8x7B Q4_K - Medium       |  48.25 GiB |    91.80 B  | ROCm      |  99 |         pp512 |     81.32 ± 0.36 |


**Conclusion**
Please support the unified memory. I do know that the speed will be in numerous instances not good, but it beats pure CPU compute in performance and thermal output. I do this as a hobby, so tinkering is part of the game. If I recall correctly before using all memory + GPU did only work with the llama.cpp Vulcan backend but as they now support it for the GPU as well (at least that is my perception) would be nice to have it in Ollama as well. Please also correct me if I am wrong - maybe this is already possible, then please point me in the right direction.
Repository: godot
Issue: 3D Omni Lights cut in half after exporting to Web
Labels: bug,platform:web,topic:rendering,needs testing,topic:3d

### Tested versions

v4.2.2

### System information

Windows 10

### Issue description

The Omni Lights get cut in half and the directional light also acts weird, I’m assuming It's because the browser renderer is different.
How can I fix this?

### Steps to reproduce

In editor, lights work fine, export to web, and lights are weird

### Minimal reproduction project (MRP)

![Captura de ecrã 2024-08-13 112956](https://github.com/user-attachments/assets/97cf80dd-dc9f-4a66-b8f6-5a010af13b75)