sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: `LogOutputChannel` LogLevel property race condition if Global Log Level and Output Panel Log Level are not the same
Labels: bug,log

<!-- ⚠️⚠️ 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-insiders
- OS Version: Windows/Linux (Tested locally and in Codespaces)

## Reproduction
1. Start this branch in Codespaces and use Launch task Run Extension [Isolated Profile]
https://github.com/JustinGrote/vscode-extension-issues/tree/issue/logOutputWindowTraceChange
1. Change log level to something other than info
1. Choose "Restart Extension Host"

Relevant Code:
https://github.com/JustinGrote/vscode-extension-issues/blob/issue/logOutputWindowTraceChange/src/extension.ts

## Expected
A `LogOutputChannel` starts with the `logLevel` that the user preference has specified

## Actual
Always starts at `Info` and gets set sometime later, however logs seem to filter normally. 

EDIT: This only happens if the default log level and the output pane log level are not the same, and "Set as Default" has not been used to modify the `argv.json`. If default log level and output pane log level are the same, the ondidChange does not fire later and the startup log level is correct.

https://github.com/user-attachments/assets/f7e53748-d024-40cf-a8cb-b47eb7418a0d

## Relevance
I have a custom logger that relies on checking the logLevel and do a noop if it does not meet the required level.



## Potential Fixes
- Update the property before processing any further log calls
- Provide a promise that can be awaited for when the LogOutputChannel is ready to receive logs at the user preferenced log level.
- I considered waiting for an onDidChangeLogLevel but this does not trigger if the user preference specified `info`, so a spurious onDidChangeLogLevel for info as well would also suffice.
Repository: godot
Issue: Zooming with scroll is broken with the Game view camera override
Labels: bug,topic:editor

### Tested versions

v4.4.dev.custom_build [c6c464cf9]

### System information

Godot v4.4.dev (c6c464cf9) - macOS 14.5.0 - Multi-window, 1 monitor - Metal (Forward+) - integrated Apple M1 Max (Apple7) - Apple M1 Max (10 threads)

### Issue description

It's a bit hard to explain or even understand what exactly is going on but a single mousewheel tick can throw the camera away several hundred meters away. It's not just hyper-sensitive it also appears to be inverted and wrapped around some distance range, so when light scrolling the camera is jittering around uncontrollably

https://github.com/user-attachments/assets/0536362a-4449-4e32-8a6d-3413a686a31f



### Steps to reproduce

1. Run the project
2. Switch to the Game mode
3. Click 3D
4. Click on the camera override button
5. Scroll in game

### Minimal reproduction project (MRP)

I just made a new empty project so I don't think it's needed to debug but here it is just in case:
[new-game-project.zip](https://github.com/user-attachments/files/17603658/new-game-project.zip)
Repository: PowerToys
Issue: Ver 0.85.1: PowerRename no longer appears in Windows Explorer context menus
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

GitHub, PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerRename

### Steps to reproduce

Right-click (or shift-right-click) on one or more files or folders in Windows Explorer.

### ✔️ Expected Behavior

Previously, there was a "PowerRename" entry in the context menu.

### ❌ Actual Behavior

"PowerRename" no longer appears in the context menu.

### Other Software

Windows 11, version 23H2 (OS build 22631.4391)
Repository: deno
Issue: Could not resolve 'npm:@ibm-cloud/platform-services@0.67.0'
Labels: needs investigation,node resolution,bundler-resolution

```ts
import * as ibm from "npm:@ibm-cloud/platform-services/iam-identity/v1";
```

```log
error: Unable to load /home/nicolas/.cache/deno/npm/registry.npmjs.org/@ibm-cloud/platform-services/0.67.0/iam-identity/v1 imported from file:///home/user/Programming/deno_test/ibm.ts

Caused by:
    No such file or directory (os error 2)
```

Version: Deno 2.0.4

UPDATE: Wrong code snippet
Repository: vscode
Issue: Multiple `LogOutputChannel` with same name race condition
Labels: bug,output

<!-- ⚠️⚠️ 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-insiders
- OS Version: Windows/Linux (Tested locally and in Codespaces)

## Reproduction
Start codespace on https://github.com/JustinGrote/vscode-extension-issues/tree/issue/logAppendOrder and `Run Extension [Isolated Profile]`
[Relevant Code](https://github.com/JustinGrote/vscode-extension-issues/blob/issue/logAppendOrder/src/extension.ts)

## Expected
Logs appear in the order they are sent
```
Log1
Log2
Log1
```

## Actual
Second Log1 appears before log2, presumably because it is "warmed up"
![Image](https://github.com/user-attachments/assets/96ed403e-7947-4bab-a59b-92431a425702)


## Notes
If this is expected behavior, it should be documented in `vscode.d.ts` because it can lead to out-of-order logs. 

Further, if multiple instances of an output channel of the same name is unsupported, it should also be documented as such or better, provide an exception on creation.
Repository: pytorch
Issue: OpOverloads are slow?
Labels: triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher

This came up when I was investigating https://github.com/pytorch/pytorch/issues/139500 (and in parallel @ezyang hypothesized about boxing vs unboxing performance).

Experiment: calling torch.stack on 5 tensors. We can vary the number of tensors, but in general the torch.* variant is faster than the torch.ops.* variant.

```py
import torch
from triton.testing import do_bench

num_tensors = 5
args = [torch.randn([]) for _ in range(num_tensors)]

def run_stack():
    for _ in range(1000):
        torch.stack(args)

def run_stack_op():
    for _ in range(1000):
        torch.ops.aten.stack.default(args)

mode = "mean"
print("num_tensors", num_tensors)
print(do_bench(run_stack, return_mode=mode))
print(do_bench(run_stack_op, return_mode=mode))
```
Output:
```
num_tensors 5
5.3403449058532715
8.467509269714355
num_tensors 1
3.627135753631592
6.683566570281982
```
Units are in ms.

I also benchmarked torch.sin vs torch.ops.aten.sin.default, and the results were similar:
```
2.5906755924224854 (torch.sin)
4.57119083404541 (torch.ops.aten.sin.default)
```

Since we make heavy use of OpOverload during PT2 tracing, and because metas *should be* inexpensive (I'm not sure if this is true), compilation time could probably benefit from a faster OpOverload interface





cc @ezyang @chauhang @penguinwu @bdhirsh @yf225
Repository: pytorch
Issue: inductor/test_move_constructors_to_cuda.py::TestMoveConstructorsToCuda::test_multi_gpu unit test failure
Labels: triaged

### 🐛 Describe the bug

inductor/test_move_constructors_to_cuda.py::TestMoveConstructorsToCuda::test_multi_gpu FAILED [1.4059s] [ 14%]
==================================== RERUNS ====================================
__________________ TestMoveConstructorsToCuda.test_multi_gpu ___________________
Traceback (most recent call last):
  File "/usr/lib/python3.12/unittest/case.py", line 58, in testPartExecutor
    yield
  File "/usr/lib/python3.12/unittest/case.py", line 634, in run
    self._callTestMethod(testMethod)
  File "/usr/lib/python3.12/unittest/case.py", line 589, in _callTestMethod
    if method() is not None:
       ^^^^^^^^
  File "/usr/local/lib/python3.12/dist-packages/torch/testing/_internal/common_utils.py", line 2983, in wrapper
    method(*args, **kwargs)
  File "/opt/pytorch/pytorch/test/inductor/test_move_constructors_to_cuda.py", line 103, in test_multi_gpu
    self._check_fn(foo, True, inp)
  File "/opt/pytorch/pytorch/test/inductor/test_move_constructors_to_cuda.py", line 31, in _check_fn
    FileCheck().check("cpp_fused").run(code[0])
RuntimeError: Expected to find "cpp_fused" but did not find it
Searched string:
# AOT ID: ['0_inference']
~~~~~~~~~ <--- HERE
from ctypes import c_void_p, c_long, c_int
import torch
From CHECK: cpp_fused
To execute this test, run the following from the base repo dir:
    python test/inductor/test_move_constructors_to_cuda.py TestMoveConstructorsToCuda.test_multi_gpu


tested on A100x2 systems 

### Versions

nightly versions
Repository: pytorch
Issue: boxing-unboxing overhead seems significant
Labels: triaged,module: dispatch

https://gist.github.com/zou3519/b987e00a82c7e184b8896a5df7b0bfa9

Benchmarking two cases:
1. torch.ops.mylib.foo operator that has an Autograd key that takes unboxed inputs but a CPU key that boxes (via return to Python)
2. torch.ops.mylib.foo_cpp operator that has an Autograd key and CPU key (in cpp) that take unboxed inputs
```
num_tensors 5
2.7380013465881348  # clone
13.052228927612305  # foo
8.257509231567383  # foo_cpp
```

NB: We have an Autograd key that accepts unboxed inputs to emulate how built-in PyTorch operators work. If I delete the autograd registration for both operators, then it becomes a boxed fallback, which brings the numbers a lot closer together (both at around 8). It looks like one unboxing isn't bad, but a boxing is bad.
Repository: langchain
Issue: Tool use for fireworks.ai seem to be broken
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

```
import os
from pathlib import Path

from dotenv import load_dotenv
from langchain_community.tools import WikipediaQueryRun
from langchain_community.utilities import WikipediaAPIWrapper
from langchain_core.messages import HumanMessage
from langchain_fireworks import ChatFireworks

load_dotenv(dotenv_path=Path(__file__).parents[1] / ".env")

LLM_API_KEY = os.environ.get("LLM_API_KEY") # Put api key here if no .env exists


wikipedia = WikipediaQueryRun(api_wrapper=WikipediaAPIWrapper())

tools = [wikipedia]


client_medium = ChatFireworks(
    api_key=LLM_API_KEY,
    model="accounts/fireworks/models/llama-v3p1-8b-instruct",
    temperature=0,
)

llm_with_tools = client_medium.bind_tools(tools, tool_choice="wikipedia") # or tool_choice="any"
result = llm_with_tools.invoke([HumanMessage(content="What is stable diffusion")])

print(result.tool_calls) # returns [] 
```

### Error Message and Stack Trace (if applicable)

_No response_

### Description

I am working with the fireworks.ai client and I noticed that Llama 8B never uses a tool even when tool_choice is equal to the tool name or to "any" to force a tool use. This contradicts the documentation for this parameter (https://python.langchain.com/docs/how_to/tool_choice/ ) but I am not sure why it is happening.

Thanks ! 

### System Info


System Information
------------------
> OS:  Linux
> OS Version:  #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Oct  2 16:16:55 UTC 2
> Python Version:  3.11.10 (main, Oct  3 2024, 07:29:13) [GCC 11.2.0]

Package Information
-------------------
> langchain_core: 0.3.15
> langchain: 0.3.6
> langchain_community: 0.3.4
> langsmith: 0.1.139
> langchain_fireworks: 0.2.5
> langchain_openai: 0.2.5
> langchain_text_splitters: 0.3.1
> langgraph: 0.2.39

Optional packages not installed
-------------------------------
> langserve

Other Dependencies
------------------
> aiohttp: 3.10.10
> async-timeout: Installed. No version info available.
> dataclasses-json: 0.6.7
> fireworks-ai: 0.15.7
> httpx: 0.27.2
> httpx-sse: 0.4.0
> jsonpatch: 1.33
> langgraph-checkpoint: 2.0.2
> langgraph-sdk: 0.1.35
> numpy: 1.26.4
> openai: 1.53.0
> orjson: 3.10.10
> packaging: 24.1
> pydantic: 2.8.2
> pydantic-settings: 2.6.1
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> SQLAlchemy: 2.0.36
> tenacity: 9.0.0
> tiktoken: 0.8.0
> typing-extensions: 4.12.2
Repository: next.js
Issue: Getting Turbopack fatal error  while trying to start and run.
Labels: bug,Turbopack

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/withered-https-go8s7s

### To Reproduce

---------------------------
Panic: panicked at turbopack/crates/turbo-tasks-fs/src/glob.rs:179:25:
not yet implemented: glob char sequences are not implemented yet
Backtrace:    0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: <unknown>
  26: <unknown>
  27: <unknown>
  28: <unknown>
  29: <unknown>
  30: <unknown>
  31: <unknown>
  32: <unknown>
  33: <unknown>
  34: start_thread
  35: clone



### Current vs. Expected behavior

While i am trying to start next typescript project i am getting fatal turbopack error, FATAL: An unexpected Turbopack error occurred. Please report the content of log.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Debian 5.10.149-1 (2022-10-17)
  Available memory (MB): 24048
  Available CPU cores: 10
Binaries:
  Node: 18.20.4
  npm: 10.9.0
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.2 // Latest available version is detected (15.0.2).
  eslint-config-next: 15.0.2
  react: 19.0.0-rc-02c0e824-20241028
  react-dom: 19.0.0-rc-02c0e824-20241028
  typescript: 5.6.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

_No response_
Repository: deno
Issue: Wrong Deno Version reported on Windows Registry/Control Panel when upgrade via `deno upgrade`.
Labels: windows,needs info

Version: Deno 2.0.4

![image](https://github.com/user-attachments/assets/9b5b8de2-e3f4-419e-96e7-010720bd5186)

**Windows Registry/Control Panel reported version:** 2.0.2
**Actual version:** 2.0.4 (upgraded via deno upgrade)

This also becomes a problem when you check Deno version in winget which will be same Windows registry/Control Panel.
Repository: godot
Issue: CollisionShape2D with top_level has inconsistent position for physics
Labels: bug,topic:physics,topic:2d

### Tested versions

- Reproductible in 4.4 dev3 and 4.3 stable

### System information

Godot v4.4.dev3 - Windows 10 - Vulkan (Forward+) - NVIDIA 3060 Ti

### Issue description

When dynamically adding a collision shape with `top_level` set and then placing it through its `global_position`, the effective position (used in the physics server) seems to differ, thus giving incorrect collisions.

### Steps to reproduce

There are 2 scenes, in the project, for each. In the first one, there are 2 areas overlapping through 2 circle collision shapes. In the second scene one of the areas is left untuched, but the other one is created and placed dynamically at the exam same position as it was in the first node. Important: Note that it is added as a child of an "strangely" offset node.

You can run both scenes with "Visible Collision Shapes", in both case you should see the shapes overlap.
When the scenes are running you can left click to see the overlapping areas in the output console, in the first scene you should see something, while the second one should return an empty array.

### Minimal reproduction project (MRP)

[mrp-toplevelcollisionshape2d.zip](https://github.com/user-attachments/files/17604790/mrp-toplevelcollisionshape2d.zip)
Repository: godot
Issue: Drag and Drop doesn't work when using the pen (works with trackpad)
Labels: bug,topic:input

### Tested versions

v4.3.stable.official [77dcf97d8]

### System information

Newest macOS / Mac mini M1

### Issue description

I use a trackpad (don't have a mouse connected) and never had any problems with Godot on that front.
A few days ago I bought a graphic tablet and it works as expected with all the apps I use. But in Godot, drag and dropping fails to activate.

For example, if I try to drag and drop a Texture (from File panel) to a TextureRect, when I use my trackpad it works no problem, but using the pen it just doesn't happen.

### Steps to reproduce

Using the pen:
Point to a (for example) bitmap file.
Press the pen, hold it and start dragging the file towards the destination (at this point, the bitmap file should get glued to the cursor, but it doesn't happen).
Release the pen at the point where the file is meant to be dropped…
…there will be no result.


### Minimal reproduction project (MRP)

https://github.com/user-attachments/assets/f7216794-6186-4f4b-bb39-8bb1b5092e36

In the video, I first drag and drop an image to the TextureRec (the circle around the mouse pointer indicates the button is held down). Then I try to do the same thing with a pen (again, the circle around the mouse, which is drawn by the OS, indicates that the pressing is registered as expected)…
…but when I let go of the pen, nothing happens.
I noticed that the blue highlight stays in the File panel for the whole time if that matters.
Repository: svelte
Issue: Deprecate `{@debug }`...?
Labels: breaking change,needs discussion

### Describe the problem

Svelte 5 introduced the [`$inspect`](https://svelte.dev/docs/svelte/$inspect) rune, which has very similar functionality to the debug tag. This makes me question the necessity of the [`{@debug }`](https://svelte.dev/docs/svelte/@debug) tag. 

### Describe the proposed solution

I feel like the debug tag _probably_ isn't needed, but the only thing that `{@debug }` has that `$inspect` doesn't is the ability to log on every state change. I think the best way to replace this would be to just make calling `$inspect` without any arguments have the same behavior. 
The only issue I see with doing this is that Svelte 5 has already released and this could upset some people. 

### Importance

nice to have
Repository: electron
Issue: zoom level is reset on location.hash change
Labels: platform/macOS,bug :beetle:,has-repro-gist,33-x-y

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

33.0.2

### What operating system(s) are you using?

macOS

### Operating System Version

macOS 15.1 (24B83)

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

Pressing cmd +/- to change the zoom level should always work regardless of `window.location.hash` changing.

### Actual Behavior

The internal zoom level is reset when changing `window.location.hash`, but the apparent zoom level is not. When the user next presses cmd +/-, the zoom level snaps back to 100% rather than adjusting incrementally.

For example, in this demo I am pressing **only** `cmd +` to increase the zoom level. I am not pressing `cmd -`, but the zoom decreases on its own.

https://github.com/user-attachments/assets/4bc4316b-dc63-4619-8a6d-9676a92821cb


### Testcase Gist URL

https://gist.github.com/jtbandes/15c1565745f0dcf61e1923bd9225379b

### Additional Information

This is a re-submission of https://github.com/electron/electron/issues/42333 with a testcase gist.

This is related to https://github.com/electron/electron/issues/40354 which was fixed in https://github.com/electron/electron/pull/40650
Repository: neovim
Issue: in gui, startup messages don't show up in command-line
Labels: bug,startup,messages

### Problem

Noticed this because `W325: Ignoring swapfile from Nvim...` didn't show up. You can see it if you manually do `:mesages` after startup.

Issue #24705 is probably related. Using the test below, you can see

- `TUI`, `AFTER UIEnter` shows up in the command-line at startup.
- `goneovim` a defer of around 50ms is needed.
- `neovide` a defer of around 150ms is needed.


### Steps to reproduce

Put the following somewhere in initialization, and notice if you see the `AFTER UIEnter` message.

```lua
vim.api.nvim_create_autocmd("UIEnter", {
    callback = function(ev)
        vim.print("AFTER UIEnter")
        return true
    end
})
```

### Expected behavior

The message should show up in any `gui` on the initial screen.

### Nvim version (nvim -v)

https://github.com/neovim/neovim/commit/b34e137e43d359c8db4fb76028dea3b410842aff

### Vim (not Nvim) behaves the same?

NA

### Operating system/version

ubuntu

### Terminal name/version

gnome-termincal

### $TERM environment variable

xterm-256color

### Installation

make install