sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Floating window causing errors when running with --headless
Labels: bug,topic:editor,needs testing

### Tested versions

Reproducible in 4.3.stable

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated AMD Radeon RX 7900 XT (Advanced Micro Devices, Inc.; 32.0.11037.4004) - AMD Ryzen Threadripper 7970X 32-Cores (64 Threads)

### Issue description

Exporting with --headless when your cached editor layout has a floating window will cause an error:
`ERROR: Condition "!is_window_available()" is true.`

This error is pretty much benign except being a red herring when generating builds. This error is pretty much benign except being a red herring when generating builds. It smells similar to [this issue](https://github.com/godotengine/godot/issues/86806), which I'm also hitting. I'm sure both issues can be fixed by just adding a headless check somewhere, but I'm not sure where.

### Steps to reproduce

Run command and view error in output:
```
Godot_v4.3-stable_win64_console.exe --export-debug --headless Web-Debug "output\out.html"
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org

savepack: begin: Packing steps: 102
        savepack: step 2: Storing File: res://.godot/imported/out.apple-touch-icon.png-a0cd21a521c42b6c1e93d3f601d82855x
        savepack: step 2: Storing File: res://output/out.apple-touch-icon.png.import
        savepack: step 22: Storing File: res://.godot/imported/out.icon.png-333c99a988fc5e116d9b8646f4d13f35.ctex
        savepack: step 22: Storing File: res://output/out.icon.png.import
        savepack: step 42: Storing File: res://.godot/imported/out.png-aef36046165722104faf40ac0d340d9c.ctex
        savepack: step 42: Storing File: res://output/out.png.import
        savepack: step 62: Storing File: res://.godot/imported/icon.svg-218a8f2b3041327d8a5756f3a245f83b.ctex
        savepack: step 62: Storing File: res://icon.svg.import
        savepack: step 82: Storing File: res://.godot/exported/133200997/export-14584830dbc22d3f76a596eed5f4948e-node_3n
        savepack: step 82: Storing File: res://node_3d.tscn.remap
        savepack: step 82: Storing File: res://.godot/global_script_class_cache.cfg
        savepack: step 82: Storing File: res://icon.svg
        savepack: step 82: Storing File: res://.godot/uid_cache.bin
        savepack: step 82: Storing File: res://project.binary
savepack: end
ERROR: Condition "!is_window_available()" is true.
   at: restore_window_from_saved_position (editor/window_wrapper.cpp:222)
```

### Minimal reproduction project (MRP)

To make the minimal build, all I did was create and set a root scene node for startup, create a default web5 export (I'd assume it's an issue with out exports), made the Node window be floating, and close the editor. I then ran the command and triggered the error.

[MinimumTest.zip](https://github.com/user-attachments/files/18512057/MinimumTest.zip)

Note: Anybody who downloads this will have to make the Node window floating, otherwise they won't get the error.
Repository: rust
Issue: Missing safety blocks in solid/io.rs
Labels: C-cleanup,T-libs

### Location

- Second impl block for `BorrowedFd<'_>`, safety is in the first one: https://github.com/rust-lang/rust/blob/dee7d0e730a3a3ed98c89dd33c4ac16edc82de8a/library/std/src/os/solid/io.rs#L125-L126
- Near impl safety block of `OwnedFd`: https://github.com/rust-lang/rust/blob/dee7d0e730a3a3ed98c89dd33c4ac16edc82de8a/library/std/src/os/solid/io.rs#L170-L171

### Summary

This is my first issue so maybe there is no issue.
I'm checking some unsafe blocks just in case something is missing and there are those without safety blocks.

Since I saw a different file with a safety block in the `drop` function (see: https://github.com/rust-lang/rust/blob/dee7d0e730a3a3ed98c89dd33c4ac16edc82de8a/library/core/src/cell/lazy.rs#L150-L152) I thought it may be missing here.

What guide could I check to make sure?
Thanks in advance.
Repository: next.js
Issue: Turbopack Error: "Next.js package not found" during pnpm dev
Labels: Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/mjeanbosco19/events-mis

### To Reproduce

To Reproduce
1. Clone the Repository: https://github.com/mjeanbosco19/events-mis
2. Use pnpm to install all project dependencies
3. Run the development server using Turbopack: pnpm dev
4. Observe the Error

![Image](https://github.com/user-attachments/assets/7370f179-1338-4275-ac64-e4419680a73a)

### Current vs. Expected behavior

Current Behavior when running the development server with pnpm dev, the process fails, and the following error message is displayed in the terminal:

FATAL: An unexpected Turbopack error occurred.  
Error [TurbopackInternalError]: Next.js package not found  

Debug info:  
- Execution of get_entrypoints_with_issues failed  
- Execution of Project::entrypoints failed  
- Execution of AppProject::routes failed  
- Execution of directory_tree_to_entrypoints_internal failed  
- Execution of directory_tree_to_loader_tree failed  
- Execution of *FileSystemPath::join failed  
- Execution of get_next_package failed  
- Next.js package not found  
No additional logs are generated in the provided log file path:
C:\Users\pc\AppData\Local\Temp\next-panic-4bc82ebe23177e94ca24c26cf186725.log.

This prevents the development server from starting and halts all development work.

Expected Behavior the development server should start successfully using Turbopack when running the pnpm dev command. Expected output in the terminal should look like:

▲ Next.js 15.1.4 (Turbopack)  
- Local:        http://localhost:3000  
- Network:      http://192.168.1.81:3000  
- Environments: .env  

✓ Starting...  
The application should be accessible at the specified local and network URLs without errors.



### Provide environment information

```bash
$ npx --no-install next info
'yarn' is not recognized as an internal or external command,
operable program or batch file.

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 12013
  Available CPU cores: 8
Binaries:
  Node: 22.13.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: 9.15.4
Relevant Packages:
  next: 15.2.0-canary.20 // Latest available version is detected (15.2.0-canary.20).
  eslint-config-next: 15.1.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

Turbopack

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

next dev (local)

### Additional context

The issue occurs locally while running the development server using pnpm dev. No deployment platform is involved; this error arises during local development.
Repository: excalidraw
Issue: Remote element drag updates are slow
Labels: bug,performance ⚡️

**Reproduction**
1. Connect two excalidraw clients (A and B) through a shared scene 
1. Create freedraw element on client A
1. Drag the freedraw element on client A
1. Observe the updates being reflected in slow-mo speeds on client B

**Technical details**

The issue seems to lie in shape cache misses, likely due to remote elements being always new instances and hence always missing the cache & re-generating from scratch.

**Notes**
- Probably does not affect just freedraw, though the difference there might be the most noticable.
- See the related screenshots, capturing the bottleneck (freedraw shape re-generation) which repeats on every single remote update.

![Image](https://github.com/user-attachments/assets/e173ec79-82e6-4467-94b1-3a970d3a8e06)
![Image](https://github.com/user-attachments/assets/318a7006-3b0e-45fb-a59c-30296c26fe99)
Repository: PowerToys
Issue: error
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce



Version: 0.87.1.0
OS Version: Microsoft Windows NT 10.0.22631.0
IntPtr Length: 8
x64: True
Date: 2025/01/23 7:34:19
Exception:
System.Runtime.InteropServices.COMException (0x80263001): {デスクトップ構成が無効化されています} デスクトップ構成が無効化されているために、操作を完了できませんでした。 (0x80263001)
   at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
   at System.Windows.Appearance.WindowBackdropManager.UpdateGlassFrame(IntPtr hwnd, WindowBackdropType backdropType)
   at System.Windows.Appearance.WindowBackdropManager.ApplyBackdrop(IntPtr hwnd, WindowBackdropType backdropType)
   at System.Windows.Appearance.WindowBackdropManager.SetBackdrop(Window window, WindowBackdropType backdropType)
   at System.Windows.ThemeManager.ApplyStyleOnWindow(Window window, Boolean useLightColors)
   at System.Windows.ThemeManager.ApplyFluentOnWindow(Window window)
   at System.Windows.ThemeManager.OnWindowThemeChanged(Window window, ThemeMode oldThemeMode, ThemeMode newThemeMode)
   at System.Windows.Window.CreateSourceWindow(Boolean duringShow)
   at System.Windows.Window.ShowHelper(Object booleanBox)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)



### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: godot
Issue: Error spam "target doesn't match" with OpenGL and global uniform of type `sampler2DArray` with no value
Labels: bug,topic:rendering

### Tested versions

- Reproducible in v4.4.beta1.official [d33da79d3]

### System information

Godot v4.4.beta1 - Pop!_OS 22.04 LTS on X11 - X11 display driver, Single-window, 3 monitors - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 4070 Ti - AMD Ryzen 9 7950X 16-Core Processor (32 threads)

### Issue description

With the compatibility (OpenGL) renderer, if you add a global uniform of type `sampler2DArray` (with no value) and make a scene with a shader that uses that global uniform, the following message will be spammed to the console every frame:

```
ERROR: GL ERROR: Source: OpenGL Type: Error     ID: 1282        Severity: High  Message: GL_INVALID_OPERATION error generated. Target doesn't match the texture's target.
   at: _gl_debug_print (drivers/gles3/rasterizer_gles3.cpp:189)
```

In fact, this will happen for any texture type other than `sampler2D` (including `sampler3D` and `samplerCube`).

What I suspect is happening, is that it's using the wrong default texture, but the correct target type. If I assign a value to the global uniform then the error stops.

The MRP below will start spamming the message just on opening the project.

### Steps to reproduce

Using the MRP is easiest - just open it!

However, if you want to set it up manually:
 
- In **Project Settings** add a shader global of type `sampler2DArray` - I'm going to use the name "my_test_global" here. Don't assign a value to it (the issue won't show if it has a value, which is why I think this is about using the wrong default texture)
- Create a scene with a **MeshInstance3D** with a **BoxMesh**
- Create a new shader material in the surface material override, for example:
  ```
  shader_type spatial;
  
  global uniform sampler2DArray my_test_global;
  
  void fragment() {
  	ALBEDO = vec3(1.0, 0.0, 0.0) * texture(my_test_global, vec3(UV, 0.0)).r;
  }
  ```
- Enjoy the error spam!

### Minimal reproduction project (MRP)

[opengl-global-uniform-sampler2darray.zip](https://github.com/user-attachments/files/18512431/opengl-global-uniform-sampler2darray.zip)
Repository: PowerToys
Issue: Color Picker
Labels: Needs-Triage

### Description of the new feature / enhancement

Is it possible to get a history feature/option for the Color Picker function?

### Scenario when this would be used?

IT would be nice to go back and look at the colors captured over a period of time.

### Supporting information

Nothing to add here.
Repository: vscode
Issue: c# dev kit is downloading dotnet 8.0 version and failing to open the solutino.
Labels: triage-needed

<!-- ⚠️⚠️ 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/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.96.4 
- OS Version:  MAC Darwin x64 24.2.0
- 
Steps to Reproduce:

1.  .Net Install tool in output : ms-dotnettools.csdevkit requested to download the .NET ASP.NET Runtime.
Downloading .NET version(s) 8.0.12~x64~aspnetcore ........... Done!
.NET 8.0.12~x64~aspnetcore executable path: /Users/mpadmaos10/Library/Application Support/Code/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/8.0.12~x64~aspnetcore/dotnet

2. While building the solution, it is throwing the below error.
Activating the "Microsoft.VisualStudio.CpsProjectIconSourceService (0.1)" service failed.
Repository: vscode
Issue: Updating issue
Labels: info-needed

The following message keeps popping up even after restarting it "Restart Visual Studio Code to apply the latest update"
Repository: pytorch
Issue: aot inductor intermediate tensor debug printing (setting 2) not working
Labels: triaged,oncall: pt2

### 🐛 Describe the bug

Code:
```python
from torch._inductor.fuzzer import ConfigFuzzer, visualize_results #, create_simple_test_model_gpu
import torch

def create_simple_test_model_gpu():
    """Create a simple test model function for demonstration."""

    batch_size = 32
    seq_length = 50
    hidden_size = 768

    def test_fn():
        inp = torch.randn(batch_size, seq_length, hidden_size, device="cuda")
        weight = torch.randn(hidden_size, hidden_size, device="cuda")
        matmul_output = inp @ weight
        final_output = torch.nn.LayerNorm(hidden_size, device="cuda")(matmul_output)
        return True

    return test_fn
tf = create_simple_test_model_gpu()

comp = torch.compile(options={"aot_inductor.debug_intermediate_value_printer": "2"})(tf)
comp()


```
Error msg:
```
Traceback (most recent call last):
  File "/home/gabeferns/org/debug/fuzzer-0/bug.py", line 23, in <module>
    comp()
  File "/home/gabeferns/pt-envs/fuzzer/torch/_dynamo/eval_frame.py", line 566, in _fn
    return fn(*args, **kwargs)
  File "/home/gabeferns/org/debug/fuzzer-0/bug.py", line 11, in test_fn
    def test_fn():
  File "/home/gabeferns/pt-envs/fuzzer/torch/_dynamo/eval_frame.py", line 745, in _fn
    return fn(*args, **kwargs)
  File "/home/gabeferns/pt-envs/fuzzer/torch/_functorch/aot_autograd.py", line 1199, in forward
    return compiled_fn(full_args)
  File "/home/gabeferns/pt-envs/fuzzer/torch/_functorch/_aot_autograd/runtime_wrappers.py", line 326, in runtime_wrapper
    all_outs = call_func_at_runtime_with_args(
  File "/home/gabeferns/pt-envs/fuzzer/torch/_functorch/_aot_autograd/utils.py", line 126, in call_func_at_runtime_with_args
    out = normalize_as_list(f(args))
  File "/home/gabeferns/pt-envs/fuzzer/torch/_functorch/_aot_autograd/runtime_wrappers.py", line 687, in inner_fn
    outs = compiled_fn(args)
  File "/home/gabeferns/pt-envs/fuzzer/torch/_functorch/_aot_autograd/runtime_wrappers.py", line 493, in wrapper
    return compiled_fn(runtime_args)
  File "/home/gabeferns/pt-envs/fuzzer/torch/_inductor/output_code.py", line 457, in __call__
    return self.current_callable(inputs)
  File "/tmp/torchinductor_gabeferns/us/cusdgx2jfgdi7skkxb27i4l7xuwe2afa2blsn3kgbqsuldogqqin.py", line 133, in call
    _print_debugging_tensor_value_info("inductor: before_launch - triton_poi_fused_randn_0 - 0", 0)
  File "/home/gabeferns/pt-envs/fuzzer/torch/_inductor/codegen/debug_utils.py", line 26, in _print_debugging_tensor_value_info
    numel = arg.float().numel()
AttributeError: 'int' object has no attribute 'float'
```
I have a fix incoming.

### Versions

git hash: 40e27fbcf2b

cc @chauhang @penguinwu
Repository: node
Issue: Add Option to Skip Initial Run in Watch Mode
Labels: feature request

### What is the problem this feature will solve?

Currently, when running a Node.js application in `--watch` mode, the application executes immediately upon startup. While this is useful in many scenarios, there are cases where skipping the initial run would be beneficial, such as:  

- When setting up for long-running tasks that do not need immediate execution.  
- When using watch mode solely for monitoring changes without requiring an initial execution.  
- To avoid redundant initialization when the program has already been run before starting the watch mode.  


### What is the feature you are proposing to solve the problem?

Introduce a new flag, such as `--skip-initial-run`, to the `--watch` mode. When this flag is enabled:  
1. The application does not execute immediately upon startup.  
2. The watcher waits for the first file change to trigger an execution.  

### Example Usage  
```bash  
node --watch --skip-initial-run app.js  
```  

### Benefits  
- Provides greater flexibility in watch mode usage.  
- Avoids unnecessary initialization or resource usage when immediate execution is not needed.  

### Alternatives  
- Users can implement workarounds in their code (e.g., using a custom flag in the application), but this increases complexity and is not a clean solution.  

### Additional Context  
This feature would align with similar functionality in other tools like nodemon, which supports skipping the initial run using a configuration option.  

Would this be a feasible addition? Happy to discuss and contribute!  

Thank you for considering this feature request!

### What alternatives have you considered?

_No response_
Repository: ollama
Issue: Ollama does not perform structured output correctly.
Labels: bug

### What is the issue?

request:
`{
            "model":"llama3.2",
            "messages":datas+[
                {
                    "role":"user",
                    "content":input_data,
                    "images":[screenshot_base64]
                }
            ],
            "stream":False,
            "format":{
                "type":"object",
                "reply":{"type":"string"},
                "properties":{
                    "operations":{"type":"array",
                                  "instruct":{
                                      "type":"object",
                                      "functions":{"type":"object",
                                                   "function_name":{
                                                       "type":"string"},
                                                       "parameter":{"type":"array","items":{"type":"string"}}
                                                       }
                                                       }
                }
            }
        },
        "required":["reply"]
        }`
reply:
`{"operations": []}`
Ollama did not reply with the required "reply".

### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.5.7
Repository: ui
Issue: [chore]: Upgrade to TailwindCSS v4
Labels: area: request,tailwind

### Feature description

Request to upgrade the project dependency to TailwindCSS v4 to ensure compatibility, leverage new features, and improve performance.

Follow the [TailwindCSS Upgrade Guide](https://tailwindcss.com/docs/upgrade-guide#using-the-upgrade-tool) to streamline the update process.

### Affected component/components

_No response_

### Additional Context

Additional details here...

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues and PRs
Repository: pytorch
Issue: [dynamo] `random.Random` gives wrong result on second call
Labels: triaged,oncall: pt2,module: dynamo

`random.Random` calls are not correct on the second call onward. This is because Dynamo generates RNG on `random.Random` objects by creating a new object and applying the RNG state at the time of tracing, which is not correct in general.

Example failing test:
```python
    def test_random_object_repeat(self):
        def fn(x, rng):
            return x + rng.randint(1, 100)

        inp = torch.randn(3, 3)
        opt_fn = torch.compile(fn, backend="eager", fullgraph=True)
        rng1 = random.Random(0)
        rng2 = random.Random(0)

        self.assertEqual(fn(inp, rng1), opt_fn(inp, rng2))
        with torch.compiler.set_stance("fail_on_recompile"):
            self.assertEqual(fn(inp, rng1), opt_fn(inp, rng2))
            self.assertEqual(fn(inp, rng1), opt_fn(inp, rng2))

        self.assertEqual(rng1.getstate(), rng2.getstate())
```

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: pytorch
Issue: [dynamo] fix graph break on random.random
Labels: triaged,module: regression,oncall: pt2,module: dynamo

We used to not graph break on `random.random`, but we do now.

```python
import random

import torch


@torch.compile(backend="eager", fullgraph=True)
def fn(x):
    return x + random.random()


fn(torch.ones(5, 5))
```

This does not happen to other supported random functions - `randint`, `randrange`, `uniform`, listed in https://github.com/pytorch/pytorch/blob/d95a6babcc581ff06d1b914ee9f92c81b2e850e2/torch/_dynamo/variables/user_defined.py#L743.

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: react
Issue: [DevTools Bug]: react-devtools not start up
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

sorrry I don't know how to reproduce this.

### Repro steps

npm install -g react-devtools

react-devtools

react-devtools not start up on ubuntu24 ,  nothing happen , no error message at all




### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

```text

```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text

```
Repository: ui
Issue: [feat]: Switch to radix-ui mono package
Labels: area: request

### Feature description

Radix-ui has release a [new package](https://www.npmjs.com/package/radix-ui) which exposes the latest version of all Radix Primitives from a single place. Using it would avoid conflicting or duplicate dependencies.

### Affected component/components

All components

### Additional Context

Additional details here...

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues and PRs