sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [List] Sticky subheader overlaps scrollbar on iOS (all major browsers)
Labels: component: list,package: material-ui,ready to take

### Steps to reproduce

Steps:
On any iOS 18.0.1+ browser
1. Open this link to live example: [(official List demo page)](https://mui.com/material-ui/react-list/#sticky-subheader)
2.Scroll  the sticky sub-header list
3.Notice the list sub-headers overlapping the scrollbar

![Screenshot 2024-11-27 at 09 45 11](https://github.com/user-attachments/assets/c35820a5-4599-4da2-b5f7-23c395dce27c)



### Current behavior

List sub-headers are overlapping the list scrollbar (overlay)

### Expected behavior

List scrollbar stays "above" list content

### Context

_No response_

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: ListSubheader iOS scrollbar
Repository: vscode
Issue: Turn on EditContext by default for non-screen reader users and off for screen reader users
Labels: feature-request,editor-edit-context

Turn on EditContext by default for non-screen reader users and off for screen reader users
Repository: flutter
Issue: Mac_benchmark flutter_view_macos__start_up is 2.00% flaky
Labels: platform-mac,P2,c: flake,team-macos,triaged-macos

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Mac_benchmark flutter_view_macos__start_up"
}
-->

The post-submit test builder `Mac_benchmark flutter_view_macos__start_up` had a flaky ratio 2.00% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_benchmark%20flutter_view_macos__start_up/10531
Commit: https://github.com/flutter/flutter/commit/d39c3532578a05d208e16d080a234a5f2c40e4ba

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_benchmark%20flutter_view_macos__start_up/10531
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_benchmark%20flutter_view_macos__start_up/10459

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_benchmark%20flutter_view_macos__start_up

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: langchain
Issue: Indexing API not reducing the ingestion time significantly with OpenSearch, even with exactly the same input file
Labels: Ɑ: vector store

### 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
INDEX_NAME="test-vector-index-5"
VECTOR_FIELD='vector_field'

CONNECTION_STRING = "postgresql+psycopg://admin:admin@10.177.245.11:5433/vectordb"
COLLECTION_NAME = "vectordb"
namespace = f"aoss/{COLLECTION_NAME}"

# Setting up record manager on PostgreSQL
record_manager = SQLRecordManager(namespace, db_url=CONNECTION_STRING)
record_manager.create_schema()

# Initializing OpenSearch LangChain client
osvectorsearch = OpenSearchVectorSearch(
  embedding_function = embeddings,
  index_name = INDEX_NAME,
  http_auth = awsauth,
  use_ssl = True,
  verify_certs = True,
  http_compress = True, # enables gzip compression for request bodies
  connection_class = RequestsHttpConnection,
  opensearch_url="https://" + OPENSEARCH_ENDPOINT
)

cleanup = "incremental"

result = index(
    documents,
    record_manager,
    osvectorsearch,
    cleanup=cleanup.value,
    source_id_key="source",
    batch_size=10
)
```

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

_No response_

### Description

I've used the same code for LangChain's Indexing API with Weaviate and PGVector where the feature works as expected. For example, for 2185 documents to be ingested on the first go with cleanup='full', it would take about 10 minutes to do so. I'd modify a single character, and reingestion using cleanup=incremental would take a few seconds.

I'd tried the same with OpenSearch, where the first ingestion took around 700 seconds, and re-ingesting exactly the same data took about 590 seconds. Is there any reason why this might be happening?

### System Info

LangChain package versions:

```
langchain                0.3.3
langchain-community      0.3.2
langchain-core           0.3.10
langchain-openai         0.2.2
langchain-text-splitters 0.3.0
```

Platform: Windows
Python Version: 3.12.4
Repository: vscode
Issue: Win11 How to solve the problem of misplaced vscode pasting comments
Labels: feature-request,editor-autoindent

<!-- ⚠️⚠️ 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

<!-- 🪓 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:  latest
- OS Version: win11

Steps to Reproduce:


![Image](https://github.com/user-attachments/assets/600f5070-74e4-41fb-834e-1d7e61d73aa6)
Repository: godot
Issue: `WebSocketPeer.put_packet()` fails with no error printed when the socket is disconnected
Labels: needs testing,topic:network

### Tested versions

Reproducible in the 4.3-stable.

### System information

Ubuntu 22.04, 4.3-stable

### Issue description

WebSocketPeer.get_ready_state returns 1 when the socket is actually disconnected.
WebSocketPeer.put_packet puts packets into the void with no indication that something went wrong.

IIRC, this is not how websockets are supposed to work.

### Steps to reproduce

```gdscript
var socket = WebSocketPeer.new()
socket.connect_to_url(secure_url)
... wait for it to connect, then pull the cable
socket.poll()
socket.get_ready_state()  # this returns 1
socket.put_packet(packet)  # this doesn't report anything either
```

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Instanced scenes gets overwritten to null randomly on open scene tabs
Labels: bug,topic:editor,needs testing

### Tested versions

4.3.stable Mono

### System information

MacOS - M1 Pro - 4.3.stable - Mono (C#) - Vulkan (Forward+)

### Issue description

Everyday, my opened scene in the editor are randomly overwrited - all their exported properties - with null. All connected signals are removed. Thankfully I have Git to catch these, but this is very concerning as any opened level or prefabs become completely broken.

Here's some of my git diff so you can see what's hapenning:
![Image](https://github.com/user-attachments/assets/f5f51885-ec96-4f83-ae07-7ff6cb36dc9a)
![Image](https://github.com/user-attachments/assets/b83de6b5-3f81-4e70-b318-f53ad572ca17)

Any workarounds or ideas why this might happen is welcome - I'm desperate.

### Steps to reproduce

Unfortunately, I have no idea how to reproduce it, I'm sorry. 

This issue wasn’t happening a few weeks ago. The project got bigger, so it could be either a scale issue, or related to a tool script I added that instantiate scene along a Path3D. Aside from that, nothing has changed.

### Minimal reproduction project (MRP)

Sorry, I can't reproduce.
Repository: ui
Issue: [bug]: request Support for CSP/nonce, Such as sidebar
Labels: bug

### Describe the bug

Env: 
I used the nextjs + shadcn-ui for my ai peoject。After I set the nextjs csp setting，the shadcn parts work not well.

### Affected component/components

Sidebar, Toast, Sonner, Tabs, Dialog, Sheet, Command

### How to reproduce

When my first layer is initialized loaded the page, the page is rendered normally, and the pages are also rendered normally. But when I refresh the page, some styles and functions are no longer normal.

for example The width variables of the sidebar are acting in style, and it is undefined and will not take effect after CSP setting. I think the problem is caused by shadcn self.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
nextjs + shadcn-ui
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ollama
Issue: Can you make the normalize optional for embeddings?
Labels: bug

### What is the issue?

https://ollama.com/library/nomic-embed-text:v1.5

```shell
curl http://localhost:11434/api/embeddings -d '{
  "model": "nomic-embed-text",
  "prompt": "The sky is blue because of Rayleigh scattering"
}'
```

access "http://127.0.0.1:%d/embedding" is ok, [ollama_llama_server](https://github.com/ollama/ollama/blob/main/llm/server.go#L894) returns the right embedding, while the `/api/embed` returns a different embedding, can you make the `normalize` optional?

### OS

Linux

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: pytorch
Issue: [Inductor] `score_fusion_memory` will always run the code optimized for small sets
Labels: triaged,oncall: pt2

### 🐛 Describe the bug

It seems the condition below is always True:
https://github.com/pytorch/pytorch/blob/4ae1c4cbb59deeae2aabc61ea1e02cf1d5992812/torch/_inductor/scheduler.py#L3266-L3270

Both `node1_dep_len` and `node2_dep_len` are unsigned integers. The larger of the two, when multiplied by 4, is definitely greater than the smaller one. 

### Versions

You can see that in latest commit in main branch.

cc @chauhang @penguinwu
Repository: deno
Issue: fmt: keep newlines in class constructors
Labels: suggestion,deno fmt

Version: Deno 2.1.1
## Current behaviour
Deno's `fmt` CLI tool removes newlines between `constructor`'s arguments. This makes classes harder to read if class members are being defined with before mentioned `constructor`
## Expected behaviour
Don't remove newlines between constructor's arguments, like Prettier does.
## Demonstration
https://github.com/user-attachments/assets/921244cf-518c-4ebe-b93f-92f3a4f8d1e6
Repository: ollama
Issue: Support AMD 780m
Labels: feature request

Please consider to add better AMD support (e.g. 7840u with 780m)
Repository: next.js
Issue: VS Code cannot bind breakpoints in a Turborepo Next.js project
Labels: bug,Turbopack

### Link to the code that reproduces this issue

https://github.com/michaelschufi/turbo-debug-nextjs-repro

### To Reproduce

1. Using VS Code, open either 
   the file `turbo-debug-nextjs-repro.code-workspace`:
   ```
   code turbo-debug-nextjs-repro.code-workspace
   ```
   
   or the folder `apps/docs/`:
   ```
   code apps/docs
   ```
2. Open the file `app/page.tsx` inside the folder `apps/docs/`.
3. Set a breakpoint on the same line as the `console.log`.
4. Start the debugger and open the page in a browser.


### Current vs. Expected behavior

Observe
- the debugger NOT stopping at the breakpoint
   - the debugger stopping at the debugger statement
   - the debugger opening a second VS Code file tab
   - the paths of the two tabs not matching when hovering over the tab labels (see screenshot below)  

-> As can be seen: The debugger kind of adds the relative path to the workspace folder to the path of the file it is debugging - resulting in doubling the path segments.

```diff
- ~/repos/turbo-debug-nextjs-repro/apps/docs/app/page.tsx
+ ~/repos/turbo-debug-nextjs-repro/apps/docs/apps/docs/app/page.tsx
```

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
  Available memory (MB): 15853
  Available CPU cores: 16
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.0.0
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: N/A
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

I think, this might also be related to the Next.js dev error window's path not matching the editor's CWD - instead it also outputs the path from the monorepo-root instead of the CWD where `next dev` was called.

Note: I don't know if this is a Next.js, Turborepo, Turbopack, or a VS Code issue - probably a bit of all of them 😅
Repository: PowerToys
Issue: Folder Size
Labels: Idea-Enhancement,Product-File Explorer,Needs-Triage

### Description of the new feature / enhancement

An option to show the sizes of folders within Windows Explorer. 

### Scenario when this would be used?

For example finding out where space is disappearing to on a system or running out of space on one drive / google drive / dropbox.

### Supporting information

I know 3rd party tools exist for this, but maybe one of the free ones could be incorporated or would be open to collaboration? Its great not to have to download and install many different tools when migrating to a new machine.
Repository: tensorflow
Issue: Some operators give different results on CPU and GPU when dealing with complex numbers that include `inf`.
Labels: type:bug,comp:ops,2.17

### Issue type

Bug

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

No

### Source

source

### TensorFlow version

2.17.1

### Custom code

Yes

### OS platform and distribution

Ubuntu 22.04.3

### Mobile device

_No response_

### Python version

3.11

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

The outputs of TensorFlow mathematical APIs (`sin, cos, tan, sinh, cosh, exp, and reduce_mean`) are inconsistent between the CPU and GPU when applied to complex inputs containing `inf`. 

### Standalone code to reproduce the issue

```shell
python
import tensorflow as tf

test_inputs = [
    tf.constant([complex(float('inf'), 0), complex(0, float('inf')), complex(float('inf'), float('inf'))], dtype=tf.complex128),
]

test_apis = [
    tf.math.sin, tf.math.cos, tf.math.tan,
    tf.math.sinh, tf.math.cosh, tf.math.exp, tf.math.reduce_mean
]

for api in test_apis:
    print(f"Testing {api.__name__}")
    for x in test_inputs:
        try:
            with tf.device('/CPU'):
              cpu_out = api(x)
              print(f"CPU Output: {cpu_out}")
            with tf.device('/GPU:0'):
              gpu_out = api(x)
              print(f"GPU Output: {gpu_out}")
        except Exception as e:
            print(f"Error in {api.__name__}: {e}")
```


### Relevant log output

```shell
Testing sin
CPU Output: [nan +0.j  0.+infj nan+infj]
GPU Output: [nan+nanj nan+infj nan+nanj]
Testing cos
CPU Output: [nan +0.j inf -0.j inf+nanj]
GPU Output: [nan+nanj inf+nanj nan+nanj]
Testing tan
CPU Output: [nan+0.j  0.+1.j  0.+1.j]
GPU Output: [nan+nanj  0. +1.j  0. +1.j]
Testing sinh
CPU Output: [inf +0.j  0.+nanj inf+nanj]
GPU Output: [inf+nanj nan+nanj nan+nanj]
Testing cosh
CPU Output: [inf +0.j nan +0.j inf+nanj]
GPU Output: [inf+nanj nan+nanj nan+nanj]
Testing exp
CPU Output: [inf +0.j nan+nanj inf+nanj]
GPU Output: [inf+nanj nan+nanj nan+nanj]
Testing reduce_mean
CPU Output: (inf+infj)
GPU Output: (nan+nanj)
```
Repository: godot
Issue: `Input.is_action_pressed()` does not report the correct action when releasing a modifier key
Labels: bug,topic:input

### Tested versions

- Reproducible in 4.3.stable.official

### System information

Godot v4.3.stable - Ubuntu 24.04.1 LTS 24.04 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (nvidia; 535.183.01) - Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 Threads)

### Issue description

In the `_process` or `_physics_process` functions, actions are not being properly recognized by `Input.is_action_pressed` when a modifier key is released, even when `exact_match` is true.

Consider two keyboard actions, "walk" and "run", which are both bound to the right arrow, but the latter of which uses the Shift key as a modifier. Pressing shift-right will be recognized as "run," but upon releasing the modifier key, the action continues to be recognized as "run" rather than being interpreted as "walk". 

That is, given code like this:
```
func _process(_delta: float) -> void:
	if Input.is_action_pressed("run", true):
		_process_label.text = "Run"
	elif Input.is_action_pressed("walk", true):
		_process_label.text = "Walk"
	else:
		_process_label.text = "Idle"
```
if I give the "run" input, then release the shift key, it continues to report the "run" action as matching even though it should instead be the "walk" action.


Strangely, this happens only if the modified action is tested first. The following code works as expected, where "walk" is the unmodified action and "run" is the modified one:
```
func _process(_delta: float) -> void:
	if Input.is_action_pressed("walk", true):
		_process_label.text = "Walk"
	elif Input.is_action_pressed("run", true):
		_process_label.text = "Run"
	else:
		_process_label.text = "Idle"
```

One would expect these two functions to have the same behavior, but they don't.

Note that the `_input` function and its `InputEvent.is_action` work as expected, correctly distinguishing between the two states. That is, when running, if releasing the shift key, the input is then recognized as "walk".

### Steps to reproduce

- Create two keyboard input actions that are different only in that one takes a modifier key (e.g. shift)
- In the `_process` function, use `Input.is_action_pressed` to monitor the state of the input. 
- See that the unmodified action is recognized, then pressing the modifier makes the modified action recognized, but releasing the modifier does not revert back to recognizing the unmodified action

### Minimal reproduction project (MRP)

When running the example, 
- press right to recognize the "walk" action
- then press shift also to recognize the "run" action
- then release shift, keeping right held down, and see that it stays "run" rather than reverting to "walk"

The example also illustrates how this behavior is different from the `_input` function, which correctly distinguishes between "run" and "walk" using the `is_action` function.

[example.zip](https://github.com/user-attachments/files/17935125/example.zip)
Repository: electron
Issue: WebContentView container priority is too high
Labels: enhancement :sparkles:

### 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 feature request that matches the one I want to file, without success.

### Problem Description

Adding WebContentView to BrowseWindow will obscure the render thread UI elements, and positioning cannot solve this problem

### Proposed Solution

Refer to the comparison with webview, you can control the hierarchical relationship by yourself, or provide an api for control

### Alternatives Considered

none

### Additional Information

Demo: https://gist.github.com/7779d612dd7cdf8482f91dbfee266767
Repository: pytorch
Issue: [PT2] Fine-grained custom triton kernels support
Labels: triaged,oncall: pt2,module: user triton

### 🚀 The feature, motivation and pitch

Currently, only limited set of triton features supported for `torch.compile`: autotune's `configs` and `keys` fields only, and heuristics before autotune. This significantly limits possible use-cases.

Heuristics before of autotune disallow to create computed properties that depend on tuned parameters (aka is time dimension is divisible by block). That removes the possibility of some optimizations, and makes code messy.

Also, autotune additional fields like configs pruning are also disallowed, even though they allow to speed up tuning process.

### Alternatives

_No response_

### Additional context

_No response_

cc @chauhang @penguinwu @oulgen @aakhundov @davidberard98
Repository: vscode
Issue: Empty code coverage (vscode development)
Labels: bug,engineering

I was trying to understand VSCode code structure and testing philosophy, and tried to get code coverage on Linux according to the instructions:

https://github.com/microsoft/vscode/blob/main/test/unit/README.md#os-x-and-linux

I got here by following the links in Wiki:

[Writing Tests](https://github.com/microsoft/vscode/wiki/Writing-Tests) -> [Unit Tests](https://github.com/microsoft/vscode/blob/main/test/unit/README.md#L1) (in the sentence "Tests can be run manually on the command line, see the instructions here.")

However I got empty coverage result. It seems that `test.sh` does not have any logic around handling the `--coverage` flag.

My guess is that the instructions are outdated, and manual coverage collection requires a different process?

<!-- ⚠️⚠️ 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?: N/A

<!-- 🪓 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: N/A, git commit at `67a68e1`
- OS Version: Debian 12

Steps to Reproduce:

1. run `./scripts/test.sh --coverage`
2. examine `./build/coverage/index.html`
Repository: vscode
Issue: Right-clicking injected text caused funny selection
Labels: bug,file-decorations

* don't use edit context
* have injected text like ghost text or inlay hint
* right click on them
* the element gets weirdly selected (not the editor selection but like a native dom selection)

https://github.com/user-attachments/assets/85f2396b-97c3-48ba-8e82-b9e6eb866f21