sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: langchain
Issue: TokenTextSplitter not loading up HF tokenizer from `.from_huggingface_tokenizer()`; using `gpt2` instead
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

```python
from langchain_text_splitters import TokenTextSplitter

tts = TokenTextSplitter(chunk_size=256, chunk_overlap=0).from_huggingface_tokenizer(tokenizer)
print(tts._tokenizer)
# output: <Encoding 'gpt2'>

tts = TokenTextSplitter.from_huggingface_tokenizer(tokenizer, chunk_size=256, chunk_overlap=0)
print(tts._tokenizer)
# output: <Encoding 'gpt2'>

tts = tts.from_huggingface_tokenizer(tokenizer)
tts._tokenizer
# output: <Encoding 'gpt2'>
```

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

_No response_

### Description

* It should show Huggingface Tokenizer
* It should use the Huggingface tokenizer, instead of the GPT2 tokenizer

### System Info

System Information
------------------
> OS:  Linux
> OS Version:  #1 SMP PREEMPT_DYNAMIC Thu Jun 27 21:05:47 UTC 2024
> Python Version:  3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0]

Package Information
-------------------
> langchain_core: 0.3.16
> langchain: 0.3.7
> langchain_community: 0.3.6
> langsmith: 0.1.139
> langchain_experimental: 0.3.3
> langchain_huggingface: 0.1.2
> langchain_text_splitters: 0.3.2

Optional packages not installed
-------------------------------
> langgraph
> langserve

Other Dependencies
------------------
> aiohttp: 3.10.10
> async-timeout: 4.0.3
> dataclasses-json: 0.6.7
> httpx: 0.27.2
> httpx-sse: 0.4.0
> huggingface-hub: 0.24.7
> jsonpatch: 1.33
> numpy: 1.26.4
> orjson: 3.10.11
> packaging: 24.1
> pydantic: 2.9.2
> pydantic-settings: 2.6.1
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> sentence-transformers: 3.2.1
> SQLAlchemy: 2.0.35
> tenacity: 8.5.0
> tokenizers: 0.19.1
> transformers: 4.44.2
> typing-extensions: 4.12.2
Repository: ui
Issue: [bug]: Skeleton Animation not working (animate-pulse)
Labels: bug

### Describe the bug

Skeleton is not animated, it is mentioned also in this other [issue](https://github.com/shadcn-ui/ui/issues/758). It shows as pulse keyframes are not defined.  I fixed it by adding the pulse keyframe in `tailwind.config.ts`

```
keyframes: {
      pulse: {
        "50%": {
          opacity: "0.5",
        },
      },
    },
```


### Affected component/components

Skeleton

### How to reproduce

Install and use Skeleton component

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
"next": "15.0.3"
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: TypeScript
Issue: slow paste with spinner
Labels: Needs Investigation

I have default paste settings on in insiders, but see a spinner every once in a while, for particular snippets of code

https://github.com/user-attachments/assets/59d36cd4-4cd8-4a00-9d60-aff32c7d86ac
Repository: ui
Issue: [bug]: cli tries to use yarn when I use pnpm
Labels: bug

### Describe the bug

```
 pnpm dlx shadcn@latest add drawer

✔ Checking registry.
⠋ Installing dependencies.
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Command failed with exit code 1: yarn add vaul @radix-ui/react-dialog
'yarn' is not recognized as an internal or external command,
operable program or batch file.
```

same happened with the init command too.

### Affected component/components

*

### How to reproduce

1. `npx shadcn@latest init -d`


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
i don't have yarn installed.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: PowerToys
Issue: Data folder location
Labels: Needs-Triage

### Description of the new feature / enhancement

Powertoys is a welcome addition. However it adds 2 folders to the \Documents folder, whether we want them there or not. Can you please make it possible for the user to specify where they are located?

### Scenario when this would be used?

It's important to me because of the way I copy stuff to my backups. Also, too many others do the same thing. 

### Supporting information

_No response_
Repository: flutter
Issue: Cupertino dialog horizontal divider is not showing correctly in dark mode
Labels: c: regression,framework,a: fidelity,f: cupertino,P2,team-design,triaged-design,f: theming

Regression introduced by #150410

The horizontal divider that separates the body of the Cupertino dialog from the actions is not correctly picking up the right color in dark mode, so it appears darker than it should. The dividers between different actions are showing up correctly.

As shown here:
![381261821-fb9eecf3-659a-4fdf-974](https://github.com/user-attachments/assets/8edeb79b-3c83-440c-a34a-2c0e104d294e)
The left image is a native dialog, the right is a CupertinoAlertDialog on master.

More details [here](https://github.com/flutter/flutter/pull/157218#issuecomment-2466747739).
Repository: rust
Issue: add hint for E0401 when defining a const inside a func
Labels: A-diagnostics,T-compiler

### Code

```Rust
struct Foo<const N: usize>;

impl<const N: usize> Foo<N> {
    fn get_n_plus_one() -> usize {
        const M: usize = N + 1;
        M
    }
}
```

### Current output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0401]: can't use generic parameters from outer item
 --> src/lib.rs:5:26
  |
3 | impl<const N: usize> Foo<N> {
  |            - const parameter from outer item
4 |     fn get_n_plus_one() -> usize {
5 |         const M: usize = N + 1;
  |                          ^ use of generic parameter from outer item
  |
  = note: a `const` is a separate item from the item that contains it
```

### Desired output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0401]: can't use generic parameters from outer item
 --> src/lib.rs:5:26
  |
3 | impl<const N: usize> Foo<N> {
  |            - const parameter from outer item
4 |     fn get_n_plus_one() -> usize {
5 |         const M: usize = N + 1;
  |                          ^ use of generic parameter from outer item
  |
  = note: a `const` is a separate item from the item that contains it
    help: associated constants and let statements can use const paramaters, consider using one of those.
```

### Rationale and extra context

_No response_

### Other cases

```Rust

```

### Rust Version

```Shell
rustc 1.84.0-nightly (759e07f06 2024-10-30)
binary: rustc
commit-hash: 759e07f063fb8e6306ff1bdaeb70af56a878b415
commit-date: 2024-10-30
host: x86_64-unknown-linux-gnu
release: 1.84.0-nightly
LLVM version: 19.1.1
```

### Anything else?

_No response_
Repository: material-ui
Issue: [TextField] Cursor jumps to beginning when clicking outside the default line-height area
Labels: external dependency,component: text field,browser: Safari

### Steps to reproduce

Link to live example: (required)
Go to the [TextField demo page on MUI’s website](https://mui.com/material-ui/react-text-field/).

Steps:
1. Type some text into any TextField component.
2. Click above the input area, especially outside the text’s line-height area (e.g., towards the top of the field).

https://github.com/user-attachments/assets/b8534f17-d429-49e1-9c82-951db7292223


3 .Observe the cursor behavior—it should ideally position itself where you clicked but instead jumps to the beginning of the text. Unless you click in the small native input line height.


### Current behavior

When using the TextField component, clicking within the input area but outside the default line-height (e.g., in the top half of the input area) causes the cursor to jump to the beginning of the text instead of positioning where the click occurred. This behavior causes the input field to respond in an unexpected and inconsistent way for users.

### Expected behavior

The cursor should appear at the exact location where the user clicks within the input area, aligning with standard input field behavior and enhancing user experience.

### Context

This issue affects the user experience by causing unexpected cursor jumps within the input area. It occurs even with the default TextField styling, making it a general issue in applications that use MUI’s TextField component.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 14.6.1
  Binaries:
    Node: 20.16.0 - /opt/homebrew/opt/node@20/bin/node
    npm: 10.8.1 - /opt/homebrew/opt/node@20/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 130.0.6723.117
    Edge: Not Found
    Safari: 17.6
  npmPackages:
    @emotion/react: ^11.11.3 => 11.11.3 
    @emotion/styled: ^11.11.0 => 11.11.0 
    @mui/base: 5.0.0-beta.61 
    @mui/core-downloads-tracker: 6.1.6 
    @mui/icons-material: ^6.1.6 => 6.1.6 
    @mui/lab: ^6.0.0-beta.14 => 6.0.0-beta.14 
    @mui/material: ^6.1.6 => 6.1.6 
    @mui/private-theming: 6.1.6 
    @mui/styled-engine: 6.1.6 
    @mui/system: ^6.1.6 => 6.1.6 
    @mui/types: 7.2.19 
    @mui/utils: 5.15.9 
    @mui/x-charts: ^6.18.7 => 6.18.7 
    @mui/x-data-grid: ^6.18.4 => 6.18.6 
    @types/react: 18.3.12 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: 4.9.5 
```
</details>


**Search keywords**: TextField cursor placement , TextField line-height issue, TextField cursor misalignment, MUI TextField cursor jump
Repository: react
Issue: Align on HTML attribute/property casing (ie not camelCase)
Labels: Type: Discussion

## Summary

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

I am cross-posting an issue I made with Preact and Voby 
https://github.com/preactjs/preact/issues/4555
https://github.com/vobyjs/voby/issues/45
Repository: deno
Issue: Deno fmt over big files
Labels: deno fmt,needs investigation

eslint.config.mjs  package-lock.json
  ~/papernet    main ?:1 userland@localhost  18:31:47··❯ deno fmt
Error formatting: /home/userland/papernet/views/index.html
   Syntax error (expected close tag) at file:///home/userland/papernet/views/index.html:32:0

/home/userland/papernet/.github/workflows/go.yml
/home/userland/papernet/views/admin.html
/home/userland/papernet/README.md
/home/userland/papernet/public/css/library.css
/home/userland/papernet/public/css/download.css
/home/userland/papernet/public/css/style.css
/home/userland/papernet/eslint.config.mjs
/home/userland/papernet/views/components/header.html
/home/userland/papernet/public/js/blob.js
/home/userland/papernet/views/components/searchResults.html
/home/userland/papernet/views/components/download.html
/home/userland/papernet/views/components/books.html
/home/userland/papernet/views/layouts/mainLayout.html
/home/userland/papernet/public/js/main.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/CSSRulePlugin.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/ScrollToPlugin.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/TextPlugin.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/EaselPlugin.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/PixiPlugin.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/Observer.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/CustomEase.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/Flip.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/MotionPathPlugin.min.js
/home/userland/papernet/public/cdn_modules/htmx@2.0.1/htmx.min.js
/home/userland/papernet/public/lib/htmx.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/Draggable.min.js
/home/userland/papernet/public/cdn_modules/gsap@3.12.5/ScrollTrigger.min.js

============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.

Platform: linux aarch64
Version: 2.0.4
Args: ["deno", "fmt"]

thread 'tokio-runtime-worker' panicked at cli/tools/fmt.rs:792:11:
Formatting not stable. Bailed after 5 tries. This indicates a bug in the formatter where it formats the file (/home/userland/papernet/public/cdn_modules/gsap@3.12.5/gsap.min.js) differently each time. As a temporary workaround you can ignore this file.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  ~/papernet  ✘ 1  4s userland@localhost  18:32:05······❯
Repository: terminal
Issue: Pane focus is lost after pane swap
Labels: Issue-Bug,Area-UserInterface,Product-Terminal

### Windows Terminal version

1.21.2911.0

### Windows build number

10.0.22631.0

### Other Software

_No response_

### Steps to reproduce

Create a split pane, use keybinds to swap between them.

### Expected Behavior

Pane shouldn't lose focus.

### Actual Behavior

Pane loses focus, Terminal doesn't respect any inputs unless the window itself is refocused, here is visual example. I was able to reproduce it with empty $PROFILE (video recording wasn't though):
https://github.com/user-attachments/assets/08cb98dc-72cc-4c23-962e-f909668c184c

Video description:
- I swap panes twice, lose focus each time, click back to regain focus.
- I change my active pane to show it works correctly without losing focus.
- I alt-tab, swap pane again, same behavior.
- I alt-tab immediately after losing focus, now swapping panes suddenly working without losing focus.
- I change my active pane.
- I swap, and now I lose the focus.
- I do showcase that last one with alt-tab multiple times.

So my uneducated guess is there are two different focuses in play there, usual Windows window focus and Terminal's pane focus. So, clicking on terminal or changing panes via keybind affects pane focus state, which sets the state in a way to cause unexpected behavior. But alt-tabbing it after focus is lost sets that state in a different way (or doesn't set it at all), which allows behavior to work as expected until it is re-set back via clicking or pane change.
Repository: go
Issue: proposal: testing/quick: deprecate package
Labels: Proposal

### Proposal Details

testing/quick has been frozen since #15557, [CL 31910](https://go.dev/cl/31910). It has, accordingly, not received much new development (primarily repo-wide updates).

Compared to other frozen packages, there aren't that many users, pkg.go.dev only lists 335 importers https://pkg.go.dev/testing/quick
There's also a clear replacement we can point to, `testing`'s [built in fuzz support](https://pkg.go.dev/testing#hdr-Fuzzing) introduced in Go 1.18.

I propose we mark the package as deprecated, and point users towards fuzzing.
Repository: pytorch
Issue: Let torch.compiler.allow_in_graph work in more situations
Labels: triaged,oncall: pt2,module: dynamo

### 🐛 Describe the bug

@Chillee and I were discussing what it would take to get `allow_in_graph` to work in more situations. Here is an accounting of some situations which we thought of:

* NN module input https://github.com/pytorch/pytorch/issues/138786 
* Local functions that close over local variables
* Methods that take in some object, potentially temporary, as a self argument

In general, there's a hierarchy, where some things are easier to deal with and some are harder to deal with:

* Accesses to global variables are "easy" to deal with, because we can just feed the real global variable directly into the function when we do tracing. The challenge here is entirely around ensuring tensor accesses get appropriately mapped to FX inputs (because parameters get lifted into arguments into the FX graph)
  * Things are a bit trickier if there is a mutation of the global variable. Then if we give the direct global variables they will have the un-mutated version of the variable. We can either just YOLO this situation or try to do something more clever (see below).
* If you have an input that corresponds to some temporary object, life is harder, because we have to somehow reconstruct the object to pass into the function. When the temporary object is disposable (you can just create it on the fly to pass in, as we do for pytree). If the object is not reconstructible, you need to somehow construct a proxy object which emulates the original object as much as possible
* If you have an input which is a *closed over* variable for a temporary closure, you need to somehow create a closure on the fly with the inputs you wanted to stub in. This has to be done recursively for any closures that themselves may be closed over (you can stop this process when you get to globals)



### Versions

master

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: godot
Issue: The Image stored in the emission_point_texture of a ParticleProcessMaterial changes id on save when Creating Emission Points From Node
Labels: bug,topic:editor

### Tested versions

- Reproducible: v4.3.stable.mono.official [77dcf97d8]

### System information

Godot v4.3.stable.mono - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1060 6GB (NVIDIA; 32.0.15.6109) - Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz (4 Threads)

### Issue description

When using a **GPUParticle3D** node and having it's emission points created from another node, the _emission_point_texture_ property inside its **ParticleProcessMaterial** will have a new **ImageTexture** assigned. From that point on, every time the scene is opened and saved, the _image_ property inside that **ImageTexture** will be regenerated with a new id. While this does not lead to any behavior issues, this means that scene will now be dirty and will be marked as an unstaged change on version control systems such as git

![image](https://github.com/user-attachments/assets/ceb80fcf-a5a5-4ad4-b6e2-ab9c8ccb3b18)


### Steps to reproduce

**With MRP**
- On a terminal, run `git status` and verify that there are no unstaged changes
- Open the Minimal Reproduction Project
- Open the scene.tscn
- Hit Ctrl+S
- On a terminal, run `git status`
- Verify that scene.tscn has unstaged changes

**Without MRP**
- Create a new scene
- Create a GPUParticle3D node with an empty **ParticleProcessMaterial** and any mesh for it's _draw_pass_1_
- Create a MeshInstance3D node with any mesh
- Select the GPUParticle3D and, from the menu over the scene preview, select GPUParticle3D > Create Emission Points From Node
- Pick the MeshInstance3D created above
- Save the scene to any new file
- Backup the saved scene or stage the file under a version control system such as git
- Close the scene in Godot
- Reopen the scene
- Hit CTRL+S
- Compare the newly saved scene with the backup from earlier
- Verify that the saved scene has unstaged changes

### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/user-attachments/files/17721657/MRP.zip)
Repository: tauri
Issue: [bug] Logs in the devtools are blocked when application is maximized or set to fullscreen.
Labels: type: bug,status: needs triage

### Describe the bug

I am building a `fullscreen` and `transparent` application with tauri2 and vue3.

when I was debuging, logs in the devtools were blocked like this:

https://github.com/user-attachments/assets/2ea7678a-4bea-4221-b753-76da9d90213d

Sometimes, warnings show up, which may be relevant.

```
[2024-11-12T19:04:36Z WARN  tao::platform_impl::platform::event_loop::runner] NewEvents emitted without explicit RedrawEventsCleared
[2024-11-12T19:04:36Z WARN  tao::platform_impl::platform::event_loop::runner] RedrawEventsCleared emitted without explicit MainEventsCleared
```
If I take devTools to secondary screen, everything's ok.




### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.19045 x86_64 (X64)
    ✔ WebView2: 130.0.2849.80
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.15.0
    - pnpm: 9.12.3
    - npm: 10.8.1

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3   
    - wry 🦀: 0.47.0
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.1.1
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.2     
    - @tauri-apps/plugin-shell : 2.0.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: deno
Issue: `deno install` with incorrect peer dependencies installs incompatible React versions
Labels: bug,install

Version: Deno 2.0.6

So... I am migrating a legacy React Vite project from Node+Yarn to Deno.

When I run `deno install` followed by `deno run -A npm:vite serve`, the page crashes in the browser with a runtime error from React:

```
Error: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
```

I have narrowed this problem down to **multiple incompatible React versions** being installed by `deno install`. It installs 3 different versions of React:

![Screenshot from 2024-11-12 13-15-26](https://github.com/user-attachments/assets/c4086ae2-c3b3-4da4-ba4c-0b26df5ab401)

The problem is actually that I have incorrect peer dependencies in my project. When I run `yarn` normally, it's full of peer dependency warnings. I understand this is a problem with my project, but it's not easy to fix. It's caused by some of my libraries having a peer-dependency on React 16 or 17, while my project has been upgraded to React 18 (which yarn allowed me to do).

![image](https://github.com/user-attachments/assets/dae77c25-67d6-43df-a3b6-6fe177bfe097)

If I use `yarn` to set up node_modules, and then use `deno run -A npm:vite serve`, it all works perfectly. So the problem is related to the behavior of `deno install` and not the Deno runtime itself.

As for the solution, I think Deno should at least warn about peer dependencies. I am not sure if there's a standard expected behavior among package managers about what to do in this scenario, or if there are any workarounds besides replacing these unmaintained packages with forks. (EDIT: I tried specifying [overrides](https://docs.npmjs.com/cli/v10/configuring-npm/package-json?v=true#overrides) to react 18 in package.json and it had no effect.)

For reference, this is the project: https://gitlab.com/soapbox-pub/soapbox

(I feel bad that Deno is burdened by this legacy Node crap, but I thought you would rather know than not know. :smiling_face_with_tear:)