sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: [4.4] Godot 4.4 Beta 1 uses ~32% more VRAM when activating viewports compared to 4.3 Stable
Labels: bug,topic:core,topic:rendering,regression

### Tested versions

- Reproducible in Godot 4.4 Dev 1, Godot 4.4 Beta 1 (haven't tested versions in between)
- Not reproducible in Godot 4.3 Stable

### System information

Godot v4.4.beta1 - Windows 10 (build 19045) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated AMD Radeon R9 M200X Series (Advanced Micro Devices, Inc.; 27.20.20913.2000) - Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz (8 threads)

### Issue description

While testing the [Godot Benchmarks](https://github.com/godotengine/godot-benchmarks) project using Godot 4.4 Beta 1 on some older computer setups, I found that the benchmark would always crash at the "Viewport > Activation > Activate 1024 Viewports" part on a system with only 1 GB of VRAM. When the console is open, the output reads:

```
Running benchmark 1 of 1: viewport/activation/activate_1024_viewports
ERROR: Can't allocate memory for image, error: -2.
   at: (drivers/vulkan/rendering_device_driver_vulkan.cpp:1812)
ERROR: Condition "!texture.driver_id" is true. Returning: RID()
   at: texture_create (servers/rendering/rendering_device.cpp:1020)
ERROR: Condition "texture.rd_texture.is_null()" is true.
   at: texture_2d_initialize (servers/rendering/renderer_rd/storage_rd/texture_storage.cpp:820)
ERROR: Attempting to use an uninitialized RID
   at: (./core/templates/rid_owner.h:259)
```

This same issue occurs on both Windows 10 and Ubuntu 22.04 LTS, and none of the other tests fail, only Activate 1024 Viewports. When converting the benchmark project to 4.3 Stable, the test is able to run successfully.

I tried reproducing the issue on a separate computer with 2 GB of VRAM, and while the issue didn't occur, I found in Task Manager that the Activate 1024 Viewports test would use around 0.75 GB of VRAM in 4.3 Stable, but around 1.1 GB in 4.4 Dev 1 and 4.4 Beta 1 (I haven't tested any of the versions in between yet). In the images below, the green line represents the test being run in 4.3 Stable, and the red line represents the same test being run in 4.4 Beta 1.

![Image](https://github.com/user-attachments/assets/b9744ad3-3bf6-41e1-8600-6460ee29b14c)

![Image](https://github.com/user-attachments/assets/09c6bffb-2791-49d2-b341-ca1d1d0b1f61)


(I understand that old hardware can't be supported forever, so if this issue is a side effect of a new feature that will benefit most users then that's okay. I just wanted to bring attention to it in case it's not a known or intended change.)

### Steps to reproduce

Run the [Godot Benchmarks](https://github.com/godotengine/godot-benchmarks) project in Godot 4.4 Beta 1, select and run only the following tests and note how much VRAM was used:

- Activate 1024 Viewports
- Activate 256 Viewports
- Activate 64 Viewports

Then, repeat the same process using Godot 4.3 Stable and compare the VRAM usage to 4.4 Beta 1.

### Minimal reproduction project (MRP)

https://github.com/godotengine/godot-benchmarks
Repository: tensorflow
Issue: How to enable compiler flags for avx2 avx512f fma
Labels: stat:awaiting response

I've compiled Tensorflow on Debian 12 successfully but when use jupyter I get this message
**To enable the following instructions: AVX2 AVX512F FMA, in other operations, rebuild Tensorflow with the appropriate compiler flags.**

```
the compilation is like this:
$ python ./configure.py

Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is -Wno-sign-compare]: -Wno-sign-compare -march=native -mavx2 -mavx512f -mfma -msse4.1 -msse4.2

$ bazelisk build //tensorflow/tools/pip_package:wheel --repo_env=WHEEL_NAME=tensorflow_cpu --local_ram_resources=2048 --config=monolithic --verbose_failures -c opt --config=opt --copt=-Wno-gnu-offsetof-extensions --copt=-march=native --copt=-mavx --copt=-mavx2 --copt=-mfma --copt=-msse4.1 --copt=-msse4.2
```

How to correctly compile tensorflow with AVX2 AVX512F FMA flags
Repository: rust
Issue: Tracking issue for release notes of #134633: Stabilize `get_many_mut` as `get_disjoint_mut`
Labels: relnotes,T-libs,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #134633.

### 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
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Stabilize `get_many_mut` as `get_disjoint_mut`](https://github.com/rust-lang/rust/pull/134633)
````

> [!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 @GrigorenkoPV, @joshtriplett -- origin issue/PR authors and assignees for starting to draft text
Repository: node
Issue: fs: can't require non-ASCII file paths in Shift-JIS filesystem
Labels: fs,windows

### Version

v22.13.0, v23.6.0

### Platform

```text
Microsoft Windows NT 10.0.26100.0 x64
```

### Subsystem

fs

### What steps will reproduce the bug?

1. Use Japanese Windows with `Shift-JIS` (aka `CP932`)
2. Load a non-ASCII file path with `require` such as `ヘルプ.js`

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

Always reproduceable under a Shift-JIS filesystem.

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

The file is loaded correctly.

### What do you see instead?

"Process exited with code 3221225477"

### Additional information

- May be similar to https://github.com/nodejs/node/issues/56049, although it's an issue for a different method and doesn't mention the Shift-JIS requirement.
- The issue was found in https://github.com/sapphiredev/pieces/issues/460 for reference, which used `require` in the user's case, the aforementioned issue also links a [reproducible example repository](https://github.com/c7e715d1b04b17683718fb1e8944cc28/my-sapphire-bot), although not a minimal one for testing purposes, the issue has been reproduced with a simple `require` in REPL as well.
- The same code works fine:
  - If the filesystem isn't Shift-JIS (UNIX, non-Japanese Windows).
  - ASCII names are used instead.
  - When run with an alternative runtime such as Deno.
Repository: rust
Issue: Basic wrapping arithmetic on pointers is pessimized compared to integers
Labels: A-LLVM,I-slow,T-compiler,C-optimization

Consider these two very simple functions:

```rust
pub fn foo_int(x: usize, y: usize, z: isize) -> (usize, usize) {
    let mask = (z.wrapping_sub(15) >> (isize::BITS - 1)) as usize;
    (x.wrapping_sub(mask), y ^ mask)
}

pub fn foo_ptr(x: *const u8, y: usize, z: isize) -> (*const u8, usize) {
    let mask = (z.wrapping_sub(15) >> (isize::BITS - 1)) as usize;
    (x.wrapping_sub(mask), y ^ mask)
}
```

I would expect these to generate identical codegen. Here we are treating a pointer as an ordinary number, with `wrapping_sub`. But we actually see a pessimization in the codegen for the pointer version:

```asm
foo_int:
        mov     rax, rdi
        add     rdx, -15
        sar     rdx, 63
        sub     rax, rdx
        xor     rdx, rsi
        ret

foo_ptr:
        add     rdx, -15
        mov     rax, rdx
        shr     rax, 63
        sar     rdx, 63
        add     rax, rdi
        xor     rdx, rsi
        ret
```

I think this has something to do with provenance. Consider the following two modified examples:

```rust
pub fn foo_expose_ptr(x: *const u8, y: usize, z: isize) -> (*const u8, usize) {
    let mask = (z.wrapping_sub(15) >> (isize::BITS - 1)) as usize;
    let u = x.expose_provenance().wrapping_sub(mask);
    (std::ptr::with_exposed_provenance(u), y ^ mask)
}

pub fn foo_map_addr_ptr(x: *const u8, y: usize, z: isize) -> (*const u8, usize) {
    let mask = (z.wrapping_sub(15) >> (isize::BITS - 1)) as usize;
    (x.map_addr(|a| a.wrapping_sub(mask)), y ^ mask)
}
```

`foo_expose_ptr` is efficient like `foo_int`, but `foo_map_addr_ptr` is pessimized like `foo_ptr`. I think this is a bug, provenance should not pessimize basic wrapping integer arithmetic, even if it occurs on pointers.
Repository: flutter
Issue: [Impller] The laptop freezes when running the project on the emulator. After deactivating Impller, it returned to work normally without any problems.
Labels: waiting for customer response,in triage

### Steps to reproduce

[Impller] The laptop freezes when running the project on the emulator. After deactivating Impller, it returned to work normally without any problems. 

### Expected results

[Impller] The laptop freezes when running the project on the emulator. After deactivating Impller, it returned to work normally without any problems. 

### Actual results

[Impller] The laptop freezes when running the project on the emulator. After deactivating Impller, it returned to work normally without any problems. 

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[Paste your output here]
```

</details>
Repository: godot
Issue: SpotLight3D shadow has significant peter-panning with default settings (4.4-dev7 and 4.4-beta1)
Labels: bug,topic:rendering,confirmed,regression,topic:3d

### Tested versions

Reproducible in: 4.4-dev7 and 4.4-beta1
Not reproducible in: 4.4-dev6 and before

### System information

Godot v4.4.dev7 - Windows 11 (build 22631) - Single-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 (NVIDIA; 32.0.15.6603) - 13th Gen Intel(R) Core(TM) i7-13700K (24 threads)

### Issue description

Shadow casting SpotLight3D has noticeable peter-panning effect with default bias value. Example below:

![Image](https://github.com/user-attachments/assets/501f57ff-6c38-477d-aa8e-0e2e695ab5ba)

### Steps to reproduce

Create a new 3D scene
Add floor into the scene and add mesh on the floor
Add SpotLight3D and enable shadows
Point the spotlight towards mesh and observe shadow it casts

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: minor editing issue in atomic.rs makes it harder to understand
Labels: A-docs,T-libs

### Location

Here is a minor editing change to the documentation of `fence()` that makes the example easier to understand. Just read the example with and without this change to understand why this is better:

```
diff --git a/library/core/src/sync/atomic.rs b/library/core/src/sync/atomic.rs
index fda26a67299..8edf0d9e48d 100644
--- a/library/core/src/sync/atomic.rs
+++ b/library/core/src/sync/atomic.rs
@@ -3608,24 +3608,24 @@ unsafe fn atomic_umin<T: Copy>(dst: *mut T, val: T, order: Ordering) -> T {
 ///
 /// A fence 'A' which has (at least) [`Release`] ordering semantics, synchronizes
 /// with a fence 'B' with (at least) [`Acquire`] semantics, if and only if there
-/// exist operations X and Y, both operating on some atomic object 'M' such
+/// exist operations X and Y, both operating on some atomic object 'm' such
 /// that A is sequenced before X, Y is sequenced before B and Y observes
-/// the change to M. This provides a happens-before dependence between A and B.
+/// the change to m. This provides a happens-before dependence between A and B.
 ///
 /// ```text
 ///     Thread 1                                          Thread 2
 ///
 /// fence(Release);      A --------------
-/// x.store(3, Relaxed); X ---------    |
+/// m.store(3, Relaxed); X ---------    |
 ///                                |    |
 ///                                |    |
-///                                -------------> Y  if x.load(Relaxed) == 3 {
+///                                -------------> Y  if m.load(Relaxed) == 3 {
 ///                                     |-------> B      fence(Acquire);
 ///                                                      ...
 ///                                                  }
 /// ```
 ///
-/// Note that in the example above, it is crucial that the accesses to `x` are atomic. Fences cannot
+/// Note that in the example above, it is crucial that the accesses to `m` are atomic. Fences cannot
 /// be used to establish synchronization among non-atomic accesses in different threads. However,
 /// thanks to the happens-before relationship between A and B, any non-atomic accesses that
 /// happen-before A are now also properly synchronized with any non-atomic accesses that

```

### Summary

Small improvement to docs to clarify example.
Repository: vscode
Issue: SCM Graph - Add support for graph for remote repositories
Labels: feature-request,github


Type: <b>Bug</b>

"connect to" -> "open remote repository" -> "Open repository from GitHub" -> "repo-name"
the source control graph is empty and does not show commits

VS Code version: Code 1.96.3 (91fbdddc47bc9c09064bf7acf133d22631cbf083, 2025-01-09T18:14:09.060Z)
OS version: Windows_NT x64 10.0.26100
Modes:

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

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)|
|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)|31.73GB (5.77GB free)|
|Process Argv|--crash-reporter-id 6d6f1ec5-eef8-4c70-aa02-95843cfea593|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (13)</summary>

Extension|Author (truncated)|Version
---|---|---
dart-code|Dar|3.102.0
flutter|Dar|3.102.0
remotehub|Git|0.64.0
vscode-pull-request-github|Git|0.102.0
vscode-autohotkey-plus-plus|mar|6.4.3
vscode-http-client|mkl|0.34.0
vscode-apache|mrm|1.2.0
debugpy|ms-|2024.14.0
python|ms-|2024.22.2
vscode-pylance|ms-|2024.12.1
azure-repos|ms-|0.40.0
remote-repositories|ms-|0.42.0
vscode-gradle|vsc|3.16.4


</details><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
vscrpc:30673769
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
2j25a237:31215806
6074i472:31201624
dwoutputs:31217127
9064b325:31222308

```

</details>

<!-- generated by issue reporter -->
Repository: langchain
Issue: deepseek-r1 not working with Ollama format correctly
Labels: 🤖:bug

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

No Code needed

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

There is no exception

### Description

I was trying deepseek-r1:14b today with ollama format:Json schema

looks like the integration need to be update as this kind of model when you ask question it start with thinking section before it start answering

so I was getting wrong output mainly the output was part of the thinking process

same code works with Phi4 and llamaa 3.2


### System Info

I'm using the js version of langchain
Repository: godot
Issue: Memory starvation while (re)importing assets
Labels: bug,topic:import

### Tested versions

- Reproducible in Godot 4.3 stable and 4.4 beta 01

### System information

Godot v4.4.beta1 - macOS Sequoia (15.2.0) - Multi-window, 1 monitor - Metal (Mobile) - integrated Apple M1 Pro (Apple7) - Apple M1 Pro (8 threads)

### Issue description

I have a few asset packs on my Godot project, which is fine. Re-scanning is not really a problem as it is usually pretty fast.
But after deleting all *.import files on my asset folder (I was trying to force a re-import) I can't open my project anymore, as it keeps reimporting assets until there is no RAM available anymore. I wonder if this is expected behavior of if there might be a memory leak somewhere.

![Image](https://github.com/user-attachments/assets/a7b2a2bc-a36c-4229-b323-8296b585b3cd)

![Image](https://github.com/user-attachments/assets/ee650261-c37a-49d0-83b2-2b8f94989125)

My assets are mostly .fbx files and a few .jpg for textures, as these are paid assets I can't share an MRP unfortunately.

### Steps to reproduce

- Have a bunch of files on a 'assets' folder
- Open the project
- Bam!

### Minimal reproduction project (MRP)

I've been using a few of the packs from this [bundle](https://justcreate3d.itch.io/low-poly-mega-bundle).
As they're paid, I can't share them unfortunately.
Repository: flutter
Issue: SegmentedButton keyboard navigation incorrectly moves focus on click with multi selection enabled. 
Labels: a: text input,framework,f: material design,f: focus,has reproducible steps,P2,team-design,triaged-design,found in release: 3.27,found in release: 3.28

### Steps to reproduce

1. Navigate to the first SegmentedButton doc example: https://api.flutter.dev/flutter/material/SegmentedButton-class.html.
2. Focus one of "Multiple choice" buttons.
3. Click to interact with the button.
4. Observe that focus is moved to another button, instead of staying on the interacted button.

### Expected results

The focus should remain on the current button when clicked.

### Actual results

The focus moves when button is clicked.

### Code sample

See SegmentedButton doc example: https://api.flutter.dev/flutter/material/SegmentedButton-class.html.

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

https://github.com/user-attachments/assets/ca1a8629-a30c-4fde-b89f-774558a5d8a3

</details>


### Logs

_No response_

### Flutter Doctor output

<details open><summary>Doctor output</summary>
N/A
</details>
Repository: PowerToys
Issue: Atalho para o powertoys run não está funcionando
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Ao pressionar o atalho para a função do powertoys run, nada ocorre, depois da última atualização nenhum problema foi identificado, contudo ao reiniciar o notebook, esta função para de ser ativada, preciso desinstalar e reinstalar novamente para poder voltar a funcionar, porém ao reiniciar o dispositivo o erro persiste.

When pressing the shortcut for the powertoys run function, nothing happens, after the last update no problem was identified, however when restarting the notebook, this function stops being activated, I need to uninstall and reinstall again to be able to work again, however when restarting the device the error persists.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

O comportamento esperado era que ao iniciar o micro a função estivesse disponível, mesmo que reiniciasse varias vezes, porém, não é isso que ocorre.

The expected behavior was that when starting the computer the function would be available, even if it restarted several times, however, this is not what happens.

### Other Software

_No response_
Repository: pytorch
Issue: Flaky Dynamo test: TestAutograd.test_gradcheck_nondeterministic
Labels: module: autograd,triaged,module: testing,oncall: pt2

### 🐛 Describe the bug

Reproduce command:
```
PYTORCH_TEST_WITH_DYNAMO=1 python test/test_autograd.py TestAutograd.test_gradcheck_nondeterministic
```
This issue was discovered while I was working on #142830. The core problem is that this unit test produces different results on CI compared to running it locally. The test passes in the main branch, but if I remove the `assertRaisesRegex` assertion (#145205), the test still passes locally but fails on CI. I suspect that even though it currently passes on CI, it’s likely coincidental.

After making changes in #142830, this test began failing. However, I’ve been unable to reproduce the failure locally.

There is a similar flaky test marked at #127115.

### Versions

main

cc @ezyang @albanD @gqchen @pearu @nikitaved @soulitzer @Varal7 @xmfan @chauhang @penguinwu