sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: [React 19] Reintroduce debugSource in some kind of opt-in way
Labels: React 19

## Summary

`__debugSource` was removed in #28265 to solve problems that do not apply to us and without including any 1:1 replacement that we could make work for our case. We are currently looking for ways to re-implement it for React 19 but all approaches seem quite hacky or fragile without any additional support from React.

We use `__debugSource` to create a mapping between a DOM element (fiber node in practice) to the source location where the JSX element was created. We use this information to be able to implement an in-browser, in-app editor for JSX, e.g. we can find a fiber node from a DOM element and then find the exact source location where the element was created, parse the file and modify the JSX node. Naturally, this is only ever available in dev mode.

We control the main configuration for how TSX/JSX is transformed into JS so getting accurate source information has never been a problem. However, all approaches using stack traces and similar will not work as they only contain the line number and not exact location in the source file. Take for instance the JSX code
```jsx
function MyView() {
  return <><span>Hello</span><span>Hello</span><span>Hello</span></>;
}
```
and it is quite difficult to know which element a `<span>` from the DOM maps to, even if the line number is available.

We have prototyped some workarounds like using our own jsx dev transform and placing the source info manually somewhere but these approaches also have issues:
1. If placing on the `ReactElement`, we have to abuse an existing property as only those are copied to the fiber nodes when rendering. The closest one would be `_debugInfo` but that will probably be overwritten in some cases
2. Placing the mapping in a global variable would work but as only the `ReactElement` instance is available at that point, and that instance is not referenced from a fiber node, there does not seem to be anything sensible available to use as a key for the map

We could rewrite part of the React code but that would seem even more fragile.

Good ideas are welcome
Repository: PowerToys
Issue: Add circle to search
Labels: Needs-Triage

### Description of the new feature / enhancement

Circle to search is currently a flagship feature that allows one to encircle a portion of the screen while running image recognition and open a tab with the output as the query to the search engine.

### Scenario when this would be used?

We mostly do research on laptops compared to smartphones, so it would be a smart choice to implement the same on desktops, too.

### Supporting information

It should support non-touch screens too with the use of graphics tablets.
Repository: PowerToys
Issue: Restoring from hibernation in Win11
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Hibernated Windows11 through PowerToys Run by typing: "Hibernate". When next time turned the computer on, a message window appeared.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

System.Runtime.InteropServices.COMException (0x80070006): A leíró érvénytelen. (0x80070006 (E_HANDLE))
   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.OnSystemThemeChanged()
   at System.Windows.SystemResources.SystemThemeFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   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)



### Other Software

_No response_
Repository: react-native
Issue: [IOS] No/disappearing Conversion Line when Typing CJK (Chinese, Japanese, Korean) Characters into TextInput (0.76.5)
Labels: Platform: iOS,Issue: Author Provided Repro,Component: TextInput

### Description

When typing CJK characters into TextInput, the conversion line (the line under the group of pre-formatted characters) disappears after typing the first character or doesn't appear at all.

https://github.com/user-attachments/assets/6afb4b71-cb77-406b-a768-8b5fbd775cf7



### Steps to reproduce

1. `npx create-expo-app@latest`
2. In the home screen, add 
```
import { useState } from 'react';
import { TextInput } from 'react-native';
...
  const [text, setText] = useState('')
  ...
    <TextInput value={text} onChangeText={setText} style={{ height: 50, width: '100%' }} />
```
3. Run the project with `npm run ios`
4. Type Japanese, Chinese, or Korean

### React Native Version

0.76.5

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 15.1.1
  CPU: (8) arm64 Apple M2
  Memory: 164.45 MB / 8.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 22.5.1
    path: ~/.nvm/versions/node/v22.5.1/bin/node
  Yarn:
    version: 1.22.19
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.8.2
    path: ~/.nvm/versions/node/v22.5.1/bin/npm
  Watchman:
    version: 2024.12.02.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.2
      - iOS 18.2
      - macOS 15.2
      - tvOS 18.2
      - visionOS 2.2
      - watchOS 11.2
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10671973
  Xcode:
    version: 16.2/16C5032a
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 20.0.2
    path: /Users/personal/.jenv/shims/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react: Not Found
  react-native: Not Found
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

https://github.com/haruki-m/react-native-text-input-issue

### Screenshots and Videos

_No response_
Repository: vscode
Issue: Bad hover handling (unjustifiable blockage)
Labels: workbench-hover

    In particular for touch input. (that may have atypical ["mouseleave"](https://developer.mozilla.org/en-US/docs/Web/API/Element/mouseleave_event) handling)
<img src="https://github.com/MasterInQuestion/attach/raw/main/microsoft/vscode/237285/hover.webp" alt="    https://github.com/MasterInQuestion/attach/raw/main/microsoft/vscode/237285/hover.webp" />

    Similar:
    [ https://github.com/microsoft/vscode/issues/237273](https://github.com/microsoft/vscode/issues/237273)
    [ https://github.com/microsoft/vscode/issues/235979](https://github.com/microsoft/vscode/issues/235979)
Repository: langchain
Issue: ChatPromptTemplate.format_messages does not handle f-strings inherited from BaseMessage, such as SystemMessage, etc
Labels: 🤖:bug,investigate

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

from langchain_core.messages import HumanMessage, SystemMessage, AIMessage
from langchain_core.prompts import ChatPromptTemplate, MessagesPlaceholder

ChatPromptTemplate.from_messages([
    SystemMessage("You are a helpful assistant. Answer all questions to the best of your ability in {language}"),
    MessagesPlaceholder(variable_name="messages")
]).invoke({"language": "English", "messages": [HumanMessage("hello")]})

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

Unexpected results

### Description

result，language Not replaced:
ChatPromptValue(messages=[SystemMessage(content='You are a helpful assistant. Answer all questions to the best of your ability in {language}', additional_kwargs={}, response_metadata={}), HumanMessage(content='hello', additional_kwargs={}, response_metadata={})])

because，No processing of objects integrated from BaseMessage

class ChatPromptTemplate(ChatPromptTemplate):
    def format_messages(self, **kwargs: Any) -> list[BaseMessage]:
        kwargs = self._merge_partial_and_user_variables(**kwargs)
        result = []
        for message_template in self.messages:
            if isinstance(message_template, BaseMessage):
                # No processing of objects integrated from BaseMessage
                result.extend([message_template])
            elif isinstance(
                    message_template, (BaseMessagePromptTemplate, BaseChatPromptTemplate)
            ):
                message = message_template.format_messages(**kwargs)
                result.extend(message)
            else:
                msg = f"Unexpected input: {message_template}"
                raise ValueError(msg)
        return result

### System Info

python==3.12.7
langchain==0.3.14
Repository: ollama
Issue: llama3.2-vision doesn't utilize my GPU.
Labels: bug

### What is the issue?

I bought a new pc with 4070 Super to do some AI tasks using Ollama, but when I tried to run llama3.2-vision it just didn't utilize my GPU and only utilize my CPU, llama3.2 does utilize my GPU, so why is that? thank you.

### OS

Windows

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.5.4
Repository: TypeScript
Issue: Unary minus on 'any' should infer type to 'number | bigint', not just 'number'
Labels: Suggestion,In Discussion

### 🔎 Search Terms

"unary minus", "negate bigint"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about bigint


### ⏯ Playground Link

https://www.typescriptlang.org/play/?target=99&ts=5.7.2#code/MYewdgzgLgBARjAvDAtACgIxgJQG4BQA9ITKTAHoD8+okscATEqnAcWRdTeNDGM+gx4iJMlW50+TZCjBtRpcRN4BDAFwwVYAJ7NWIjuNq8AHgJXzDXY7FoA3Zmjsat27EgB8qO5bHUbMABOzPZocMLsfsq24HbSME4aYACuALZwAKbBAD7wAJYA5nlgUO6IXig+BlEBgfH2DGERCpz4QA

### 💻 Code

```ts
const b = -(1n);
//    ^?
const b2 = -b;
//    ^?

const n = -(1);
//    ^?
const n2 = -n;
//    ^?

const a: any = b;
//    ^?
const x = -a;
//    ^?

const conv = (v: any) => -v;
//    ^?
const r = conv(b);
//    ^?
const conv2 = (v: number | bigint) => -v;
//    ^?
const r2 = conv2(b);
//    ^?
```


### 🙁 Actual behavior

Applying an unary minus on an `any` variable infers the type to `number` (as can be seen in the "hat-question mark" comments or the .D.TS tab for `x`, `conv`, and `r`). The inferred type for the constants `x` and `r` is thus wrong (they actually contain a BigInt value).

Unary minus on a `number` correctly infers `number`, and (more importantly) unary minus on a `bigint` correctly infers `bigint`. Same for unary minus on a `number | bigint` which infers `number | bigint`.

### 🙂 Expected behavior

Applying an unary minus on an `any` variable should infer the type to `number | bigint`.

ECMAScript specifies (https://tc39.es/ecma262/multipage/ecmascript-language-expressions.html#sec-unary-minus-operator) unary minus as doing a `ToNumeric` (which returns either a Number of a BigInt) and then applying the appropriate `unaryMinus` abstract operation depending on the type of the value. The result is thus either a Number or a BigInt.

(the unary plus operator however converts to Number values only)

### Additional information about the issue

_No response_
Repository: excalidraw
Issue: Rendering Problem on Linux(Debian)
Labels: bug,Linux

![Image](https://github.com/user-attachments/assets/d38f6664-9537-4ba2-ac49-bb91b722f7e4)

Excalidraw website is having issues with rendering bigger size of the objects, which is visible in the above picture. Is this a problem on my end?? I have used Excalidraw on windows and it works flawlessly.

How can I resolve this issue I am facing??
Repository: tensorflow
Issue: How can I use local CUDA instead of hermetic CUDA to build? 
Labels: type:build/install,subtype: ubuntu/linux,TF 2.18

### Issue type

Build/Install

### Have you reproduced the bug with TensorFlow Nightly?

No

### Source

source

### TensorFlow version

2.18

### Custom code

No

### OS platform and distribution

Ubuntu 24.04

### Mobile device

_No response_

### Python version

3.12

### Bazel version

6.5.0

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Configures about hermetic CUDA are confusing. It seems to bring extra dependencies into the output binary. I want to build a tf-lib depends on local CUDA libs.

### Standalone code to reproduce the issue

```shell
-
```


### Relevant log output

_No response_
Repository: tensorflow
Issue: Broken compatibility with tensorflow-metal in 2.18
Labels: type:bug,comp:gpu,TF 2.18

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

2.18

### Custom code

Yes

### OS platform and distribution

MacOS 15.2

### Mobile device

_No response_

### Python version

3.11.11

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

Apple M2 Max GPU 38-cores

### Current behavior?

Apple silicone GPU with tensorflow-metal==1.1.0  and python 3.11 works fine with tensorboard==2.17.0

This is normal output:
```
/Users/mspanchenko/anaconda3/envs/cryptoNN_ml_core/bin/python /Users/mspanchenko/VSCode/cryptoNN/ml/core_second_window/test_tensorflow_gpus.py 
[PhysicalDevice(name='/physical_device:GPU:0', device_type='GPU')]

Process finished with exit code 0
```

But if I upgrade tensorflow to 2.18 I'll have error, attached in "Relevant log output" issue section

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

if __name__ == '__main__':
    gpus = tf.config.experimental.list_physical_devices('GPU')
    print(gpus)
```


### Relevant log output

```shell
/Users/mspanchenko/anaconda3/envs/cryptoNN_ml_core/bin/python /Users/mspanchenko/VSCode/cryptoNN/ml/core_second_window/test_tensorflow_gpus.py 
Traceback (most recent call last):
  File "/Users/mspanchenko/VSCode/cryptoNN/ml/core_second_window/test_tensorflow_gpus.py", line 1, in <module>
    import tensorflow as tf
  File "/Users/mspanchenko/anaconda3/envs/cryptoNN_ml_core/lib/python3.11/site-packages/tensorflow/__init__.py", line 437, in <module>
    _ll.load_library(_plugin_dir)
  File "/Users/mspanchenko/anaconda3/envs/cryptoNN_ml_core/lib/python3.11/site-packages/tensorflow/python/framework/load_library.py", line 151, in load_library
    py_tf.TF_LoadLibrary(lib)
tensorflow.python.framework.errors_impl.NotFoundError: dlopen(/Users/mspanchenko/anaconda3/envs/cryptoNN_ml_core/lib/python3.11/site-packages/tensorflow-plugins/libmetal_plugin.dylib, 0x0006): Symbol not found: __ZN3tsl8internal10LogMessageC1EPKcii
  Referenced from: <D2EF42E3-3A7F-39DD-9982-FB6BCDC2853C> /Users/mspanchenko/anaconda3/envs/cryptoNN_ml_core/lib/python3.11/site-packages/tensorflow-plugins/libmetal_plugin.dylib
  Expected in:     <2814A58E-D752-317B-8040-131217E2F9AA> /Users/mspanchenko/anaconda3/envs/cryptoNN_ml_core/lib/python3.11/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so

Process finished with exit code 1
```
Repository: deno
Issue: Vite's development server misbehaves when run under Deno version 2.1.2 and later
Labels: bug,node compat

Version: Deno 2.1.2, 2.1.3, 2.1.4
OS: Arch Linux

When Vite's development server is running under Deno and a file it is tracking is modified by Neovim, a change is registered in every file that Vite is tracking and all are reloaded.

Because of this HMR is unusable.  Vite will inevitably detect too many changes and overwhelm the refresh system leading to either a crash and relaunch or at best a total source reload.

This only happens under Deno after version 2.1.2, earlier versions do not exhibit this issue.

Some editors other than Neovim also do not trigger this issue (for instance a filesave in VSCode does not cause this to happen).  There seems to be something specific about the way Neovim saves a file that confuses Vite's file watcher when run under Deno 2.1.2 and later.

I have tested many versions of Neovim (v9.x, v10.x, nightly) with and without plugins enabled, and all trigger this issue.  Many versions of Vite (v4.x, v5.x, v6.x) as well, and all trigger this issue.

The problem has specifically been observed in Neovim (any version), Vite (any version), and Deno (`2.1.2`, `2.1.3`, and `2.1.4`)

Here is a simple reproduction of the issue https://github.com/GunnerGuyven/deno-issue-example-1

Downgrading Deno using `sudo deno upgrade 2.1.1` also avoids this issue.
Repository: flutter
Issue: Firebase Flutter tutorial includes incorrect statement statement to define GuestBookState
Labels: team-codelabs

In [this codelabs firebase tutorial](https://firebase.google.com/codelabs/firebase-get-to-know-flutter#6), it shows below line of code which complains about invalid use of private type in public API...


```dart
@override
  _GuestBookState createState() => _GuestBookState();
```


...but the sample source uses this line which gives no error...

`State<GuestBook> createState() => _GuestBookState();`

https://github.com/flutter/codelabs/blob/7e69ced1af6a90e3c0ebaf2e6a1720ff34e7461e/firebase-get-to-know-flutter/step_09/lib/guest_book.dart#L23
Repository: pytorch
Issue: PyTorch Enum PYI stubs are invalid. Fix typing of PYI stubs
Labels: module: typing,module: lint,triaged

### 🐛 Describe the bug

Updating mypy reveals that the way we have defined enums in our PYI stub is not valid. Specifically, we are not suppose to annotate the type of any values per https://typing.readthedocs.io/en/latest/spec/enums.html#defining-members . Therefore, we need to fix the typing and update it to a more modern typing system. See #143837 for some example errors.

### Versions

master as of today

cc @ezyang @malfet @xuzhao9 @gramster
Repository: go
Issue: text/scanner: SkipComments is ignored without ScanComments
Labels: Documentation,NeedsInvestigation,BugReport

### Go version

go1.23.4

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/carlo/.cache/go-build'
GOENV='/home/carlo/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/carlo/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/carlo/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/lib/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.4'
GODEBUG=''
GOTELEMETRY='off'
GOTELEMETRYDIR='/home/carlo/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v3'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/carlo/src/go-scanner-bug/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build186288891=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

The `text/scanner` [docs](https://pkg.go.dev/text/scanner#pkg-constants) say:

> Predefined mode bits to control recognition of tokens. For instance, to configure a [Scanner](https://pkg.go.dev/text/scanner#Scanner) such that it only recognizes (Go) identifiers, integers, and skips comments, set the Scanner's Mode field to:
>
> `ScanIdents | ScanInts | SkipComments`
>
> With the exceptions of comments, which are skipped if SkipComments is set, unrecognized tokens are not ignored.

However, it seems that `SkipComments` only works as advertised when combined with `ScanComments`, despite the example clearly implying otherwise.

The following code demonstrates (see [go.dev.play link](https://go.dev/play/p/37ddUf4EPvV)):

```go
package main

import (
	"fmt"
	"strings"
	"text/scanner"
)

func main() {
	testScanner(scanner.ScanIdents|scanner.ScanInts|scanner.SkipComments, "// comment")
	testScanner(scanner.ScanIdents|scanner.ScanInts|scanner.ScanComments|scanner.SkipComments, "// comment")
}

func testScanner(mode uint, input string) {
	var sc scanner.Scanner
	sc.Init(strings.NewReader(input))
	sc.Mode = mode
	for sc.Peek() != scanner.EOF {
		tok := sc.Scan()
		fmt.Printf("[%s:'%s'] ", scanner.TokenString(tok), sc.TokenText())
	}
	fmt.Println()
}
```

### What did you see happen?

The output is:

```
["/":'/'] ["/":'/'] [Ident:'comment'] 
[EOF:''] 
```

### What did you expect to see?

I would expect the output to be:

```
[EOF:''] 
[EOF:''] 
```
Repository: ui
Issue: [bug]: Area Chart - Interactive
Labels: bug

### Describe the bug

when using Area Chart - Interactive with the cart type set to basis the dot isn't on the right place

### Affected component/components

Area Chart

### How to reproduce

make a chart and set the type to basis

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrome, Windows 11
```


### Before submitting

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