sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Reference of literal is not optimized out
Labels: T-compiler,C-optimization

https://godbolt.org/z/W1Gbnfjz9
Consider code like this, the codegen includes unnecessary reference of literal :
```rust
const T: [u8; 512] = ...;
pub fn f(a: usize) -> u8 {
    *T.get(a).unwrap_or(&1)
}
```
Repository: flutter
Issue: Ios18.2 freezes when selecting pictures
Labels: waiting for customer response,in triage

### Steps to reproduce

Ios18.2 freezes when selecting pictures

### Expected results

Ios18.2 freezes when selecting pictures

### Actual results

Ios18.2 freezes when selecting pictures

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[Paste your output here]
```

</details>
Repository: vscode
Issue: Edit context adds a tabstop between chat input and buttons
Labels: bug,editor-edit-context

- Focus the chat input
- press tab
- Focus goes to `.native-edit-context-textarea`
- Press tab again
- Now it's where I expect, on the next toolbar
Repository: ollama
Issue: [Feature] Support Intel GPUs
Labels: feature request

Ollama had supported by the PR https://github.com/ollama/ollama/pull/2458 merged to support Intel GPU.
But the function disappears now.

I see there are several issues and opened PRs for Intel GPU. But they are too old.

I want to draft PRs to support Intel GPU: dGPU & iGPU (since 11th Core) by including llama.cpp SYCL backend.
This issue is created to trace the development work and reduce the duplicated work in the future.
Repository: PowerToys
Issue: The pop-up fast exception detection fails and the exception stalls
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Installer

### Steps to reproduce

If my system has the latest version installed , the pop-up fast exception detection fails and the exception stalls,but if i use version 0.86 it is normal,if you want a image to debugger,please post email to 2298192210@qq.com,then i will send the picture to you by email

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: PowerToys
Issue: Add Window Snapping with Temporary Screen Boundaries in 'Mouse Without Borders'
Labels: Needs-Triage

### Description of the new feature / enhancement


Currently, 'Mouse Without Borders' allows seamless cursor movement across multiple computers, but dragging windows lacks the ability to snap them to specific areas like halves or quarters of the screen.

The proposed feature would temporarily enable screen boundaries when a window is being dragged, allowing it to snap to predefined areas. This improvement would make managing and arranging windows across multiple monitors more convenient and efficient.

### Scenario when this would be used?

- When using multiple computers connected with 'Mouse Without Borders.'
- Dragging windows between monitors.
- Arranging windows to snap to specific areas, such as halves or quarters of the screen.

### Supporting information

_No response_
Repository: kubernetes
Issue: Long Lived TCP Connections Fail When Downscaling Kube Proxy (ExternalTrafficPolicy Cluster)
Labels: kind/bug,sig/network,sig/autoscaling,sig/cloud-provider,needs-triage

### What happened?

Some external cloud providers such as Azure use a pass-through(direct server return) load balancer. This means that TCP connections are not terminated on the loadbalancer, but instead downstream in the kubernetes cluster.

ExternalTrafficPolicy Cluster configures load balancers to send traffic to any node in the cluster, even if the node is not running a pod that the traffic is destined to. From there kube-proxy routes the request to the pod (which could either be on the same or different node). 

In our case, when client sets up a long living TCP connection and that traffic path hits kube-proxy on a node that downscales sometime during the duration of the TCP connection, we observe 520 errors from the server. 

### What did you expect to happen?

Kubernetes nodes that act as a intermediate hop between the loadbalancer and the node/pod that the traffic is destined to should gracefully allow all existing TCP connections to finish before the node/processes are terminated. 

This is important because some loadbalancers like Azure continue to send traffic to existing TCP even though the target node has been marked unheathly.  

### How can we reproduce it (as minimally and precisely as possible)?

1) Setup any service (e.g., nginx ingress), tolerated/tainted to node group A. Use loadbalancer with external traffic policy: cluster. 
2) Scale node pool B. 
3) Simulate many http requests, targetting loadbalancer endpoint of service created in step 1
4) Scale down node pool B.
5) Observe errors on requests that proxied through scaled down node in node pool B. 

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

1.30

</details>


### Cloud provider

<details>
Azure
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: material-ui
Issue: [docs] Documentation error: integration with tailwindcss step 3
Labels: ready to take,support: docs-feedback

### Related page

https://mui.com/material-ui/integrations/interoperability/#tailwind-css

### Kind of issue

Broken demo

### Issue description

After creating a new nextjs project with the default options, if you want to be able to use both MUI and tailwindcss, you need to follow: https://mui.com/material-ui/integrations/nextjs/   and then to follow: https://mui.com/material-ui/integrations/interoperability/#tailwind-css

But at step 3 without adding `important`, it already works fine at this point. If you add the `important` it doesn't work.

### Context

_No response_

**Search keywords**: tailwindcss nextjs
Repository: ui
Issue: [feat]: remove/rm/delete components using CLI
Labels: area: request

### Feature description

As we have npx shadcn@latest add <component>, why not have a npx shadcn@latest remove/rm/delete <component> using the cli.

Here is how this feature would work:
1. User hits the npx shadcn@latest remove/rm/delete <component>.
2. Search if the component exists in the user's directory.
3. Only remove the component if it exists inside the UI folder
4. If it does not exist in the UI folder, throw error stating the component does not exist -> Add it using npx shadcn@latest add <component>.

### Affected component/components

None

### Additional Context

@shadcn Please check this out!

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: PowerToys
Issue: Invalid Esperanto character
Labels: Issue-Bug,Area-Localization,Needs-Triage,Issue-Translation

### Microsoft PowerToys version

0.87.1

### Utility with translation issue

Quick Accent

### 🌐 Language affected

Esperanto

### ❌ Actual phrase(s)

Ǔ (U+01D3)
ǔ (U+01D4)

### ✔️ Expected phrase(s)

Ŭ (U+016C)
ŭ (U+016D)

### ℹ Why is the current translation wrong

Esperanto uses a different diacritic mark.
Repository: langchain
Issue: DOC: <A long term memory agent 'DOC: ' prefix>
Labels: 🤖:docs

### URL

https://python.langchain.com/docs/versions/migrating_memory/long_term_memory_agent/

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

Something is wrong with this example, when I run exactly same as in the documentation I keep get 429 error. Although I have a commercial license of OpenAI and there is enough dollars left. comes load_memories, not sure what is wrong

error --
   raise self._make_status_error_from_response(err.response) from None
openai.RateLimitError: Error code: 429 - {'error': {'message': 'You exceeded your current quota, please check your plan and billing details. For more information on this error, read the docs: https://platform.openai.com/docs/guides/error-codes/api-errors.', 'type': 'insufficient_quota', 'param': None, 'code': 'insufficient_quota'}}
During task with name 'load_memories' and id '0852441c-bcd1-ee97-f431-c3b9d0a980f2'

### Idea or request for content:

kindly correct the doc
Repository: vscode
Issue: Inline Jupyter Interactive for python files
Labels: feature-request,interactive-window

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. --> 

I want inline jupyter interactive windows/boxes for .py files!

print("#Hello! Make inline interactive a thing!") 
... #Hello! Make inline interactive a thing!
Repository: ollama
Issue: Running OLLAMA_FLASH_ATTENTION=true with LoRA Models Returns: flash_attn is not compatible with LoRA
Labels: bug

### What is the issue?

Hello, I use fine tuned LLMs that use LoRA, when activating OLLAMA_FLASH_ATTENTION=true ollama serve the fine tuned models do not work, the error received is:

```
llama_lora_adapter_set: flash_attn is not compatible with LoRA
panic: error applying lora from file
```

This error stops the model from running until you flag it false. Then it runs correctly when its turned to false.

I have found on the llama.cpp git that they edited and removed part of their code last week to fix this. Here was the same issue: https://github.com/ggerganov/llama.cpp/discussions/11097

Here is the fix that was added to llama.cpp:

https://github.com/ggerganov/llama.cpp/pull/11104/files

I'm not sure what I've done is correct in providing the above information (first ever report), but I found that Ollama uses Llama.cpp so I thought I'd find the solution directly.

### OS

macOS

### GPU

_No response_

### CPU

_No response_

### Ollama version

0.5.5
Repository: ant-design
Issue: 取消表格border，并设置固定列和指定滚动区域高度后，在未达到滚动高度时，仍然会出现一个可滚动1px的滚动条
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/gu-ding-lie-antd-5-23-1-forked-fd5kzv?workspaceId=ws_2SpvwKdLHLzTaCpuAok1Y4)

### Steps to reproduce

1、设置某一列固定
2、设置scroll.y
3、隐藏border，设置 .ant-table-cell {
    border-bottom: none !important;
  }

### What is expected?

未达到滚动高度时不出现滚动条

### What is actually happening?

未达到滚动高度时会出现滚动条

| Environment | Info |
| --- | --- |
| antd | 5.23.1 |
| React | 18.0.0 |
| System | Windows |
| Browser | chrome 131.0.6778.265 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: neovim
Issue: nonblocking :global cmd
Labels: enhancement,complexity:high,multiproc,async

### Problem
Situation, 2 vertical splits with each buffer containing 200K lines of code and diff mode activated by running `:windo diffthis` .

When doing a global command like `:g/^\[/normal! da[` in a 200K line with, the editor freezes until done which could be 3 seconds for the edit operation and then ~20 seconds for the diff calculation.

How feasible is it to do this in a nonbocking mode (separate thread?) to allow user to interact with other buffers?

### Expected behavior
User should still be able to move to another windows and edit that while a long running command is executing in a different window/buffer.
Repository: transformers
Issue: Some weights of the model checkpoint at /models/DeepSeek-V3_bf16 were not used when initializing DeepseekV3ForCausalLM
Labels: bug

### System Info

I use  AutoModelForCausalLM.from_pretrained to load DeepSeek_V3, it raises below warning:

![Image](https://github.com/user-attachments/assets/19b42d79-ed03-4f56-8b8b-765c8d96d32e)
then I print the model state keys, it only has 60 layers, however, the deepseek v3 weight actual has 61 layers, the last layer is missing.

![Image](https://github.com/user-attachments/assets/0400c975-5dfc-4cd2-b4d2-213ee7980b3e)

How to fix it? Thank you~



### Who can help?

_No response_

### Information

- [ ] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

model = AutoModelForCausalLM.from_pretrained(
    "path/to/deepseek_v3_bf16,
    device_map="cpu",
    torch_dtype="auto",
    trust_remote_code=True,
)
print(model.state_dict().keys())

### Expected behavior

 AutoModelForCausalLM.from_pretrained could load deepseek v3 correctly.
Repository: PowerToys
Issue: Unknown Exception happened (System.Reflection.TargetInvocationException)
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Last evening I had my laptop abnormally eating CPU with process "SYSTEM" that cannot be terminated. During the night hours the laptop was left unattended.

This morning I saw that there had been a lot of "rundll" warning windows, and the one big error window from PowerToys.
I've been using PT for many years, but such kind of error I saw for the 1st time ever.

Attached are the details:

- **PowerToys issue window.png** = the screenshot from PT with the Exception details.
- **2025-01-14.txt** = the PT log file (taken from path "C:\Users\User\AppData\Local\Microsoft\PowerToys\PowerToys Run\Logs\0.87.1.0\2025-01-14.txt")
- **error_from_PT_Exception_Window.txt** = the text content copy-pasted from the PowerToys Exception Window, in which it suggests to file a bug on GitHub (what I'm hereby doing). 

Please fix the underlying bug and explain in simple terms why had this bug appear.

### ✔️ Expected Behavior

When the laptop where PT is launched is left unattended through the night, no error must happen, no warning raised, and "system" process must not eat a lot of CPU.

### ❌ Actual Behavior

SYSTEM eats CPU, errors and warning when unattended for hours.

### Other Software

![Image](https://github.com/user-attachments/assets/f1ad57f8-5f3a-404a-adaa-7cc85970e22c)

[2025-01-14.txt](https://github.com/user-attachments/files/18407483/2025-01-14.txt)

[error_from_PT_Exception_Window.txt](https://github.com/user-attachments/files/18407494/error_from_PT_Exception_Window.txt)
Repository: godot
Issue: Error when creating a new project with specific steps (Create Folder manipulation)
Labels: bug,topic:editor,usability

### Tested versions

- Reproducible in: v4.3.stable.official [77dcf97d8], v4.4.dev7.official [46c8f8c5c]

### System information

Godot v4.3.stable - Windows 10.0.26100 - Vulkan (Forward+) - dedicated Radeon (TM) RX 480 Graphics - AMD Ryzen 7 2700 Eight-Core Processor (16 Threads)

### Issue description

When trying to create a new project in Godot, if I leave the "Project Name" field empty and uncheck the "Create Folder" option, then check it again and attempt to enter a project name, I encounter the following errors:
- "You cannot save a project at the selected path." (if saving in Documents)
- "The selected path is not empty." (if saving in any other folder)


### Steps to reproduce

1. Open Godot.
2. Click on "Create"
3. Leave the "Project Name" field empty.
4. Uncheck the "Create Folder" option.
5. Check the "Create Folder" option again.
6. Enter a project name.


### Minimal reproduction project (MRP)

N/A
Repository: go
Issue: cmd/relnote: unrecognized failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/relnote" && test == ""
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8726172893393941921)):

    FAIL	cmd/relnote [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: langchain
Issue: Hangs getting of distinct list of edge labels
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

SELECT * 
FROM cypher('graph', $$
MATCH ()-[e]**->**() RETURN collect(distinct label(e)) as labels
$$) as (e agtype);

### Error Message and Stack Trace (if applicable)

_No response_

### Description

https://github.com/langchain-ai/langchain/blob/master/libs/community/langchain_community/graphs/age_graph.py
Line 158 contains wrong MATCH statement definition.
It should be with a right arrow:
MATCH ()-[e]**->**() RETURN collect(distinct label(e)) as labels

### System Info

A Docker container with the latest version of langchain.
Repository: next.js
Issue: Memory spike issue with Next.js 15.1.4 on Azure
Labels: linear: next

### Verify canary release

- [ ] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 18:51:28 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T8112
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.13.1
  npm: 10.8.1
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.1.4 // Latest available version is detected (15.1.4).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: standalone
```

### Which example does this report relate to?

This issue is not related to any specific example in the examples folder. The problem occurs in a general Next.js application deployed on Azure.

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

We are experiencing a significant memory spike and auto-scaling issues when using Next.js 15.1 in our Azure deployments. Memory usage increases unpredictably under typical traffic conditions, leading to higher resource utilization and triggering unnecessary auto-scaling.

When downgrading to Next.js 14.2, these issues are resolved, and memory usage returns to stable levels. This suggests a regression introduced in version 15.1.

Graphs comparing memory usage for versions 15.1 and 14.2 are attached below for reference.

![Image](https://github.com/user-attachments/assets/9b4fa01f-c9e5-44ab-9aee-ecb7e332cba8)

![Image](https://github.com/user-attachments/assets/7e14e615-4366-4dbe-8d55-e4cbf43bb15b)

### Expected Behavior

Memory usage should remain stable and consistent under typical traffic conditions when using Next.js 15.1, similar to the behavior observed in Next.js 14.2.

### To Reproduce

Deploy a Next.js 15.1 application on Azure with typical production traffic patterns.
Monitor the memory usage and auto-scaling behavior using Azure's monitoring tools.
Observe that memory usage increases significantly and unpredictably, causing auto-scaling to trigger even under normal load.
Downgrade the application to Next.js 14.2.
Re-monitor the application, noticing that memory usage stabilizes and auto-scaling behaves as expected.

![Image](https://github.com/user-attachments/assets/ffeb6497-bd6e-4a31-8525-87d66f6a3546)

![Image](https://github.com/user-attachments/assets/c7063e2d-f1c4-4dd9-8d06-67a2570f55ea)
Repository: PowerToys
Issue: Keep Awake does not work without screen on on some devices
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Awake

### Steps to reproduce

I have two devices: an Intel gen13 laptop and an Intel gen7 desktop with Powertoys installed on both.
I use Keep Awake on both of them, but it behaves differently.
On my desktop, if I choose Keep awake indefinitely, it indeed keeps it awake, but on my laptop it does not have any effect, the laptop goes to sleep as normal.
But if I choose Keep screen on, now the laptop never goes to sleep.

Is there any option to keep the laptop awake without keeping the screen on as well? Why is it different from the Desktop PC?

Steps: Activate Keep Awake indefinitely without any other option.

### ✔️ Expected Behavior

The Laptop should not go to sleep

### ❌ Actual Behavior

The laptop enters sleep mode as normal.

### Other Software

_No response_
Repository: PowerToys
Issue: Session Saving and Restoration Feature for Seamless Workflow Continuity
Labels: Needs-Triage

### Description of the new feature / enhancement

I propose a feature for PowerToys that allows users to save all currently open programs, files, and folders in a workspace. This saved session could be manually activated through a shortcut or similar action. After a system restart, it should also be possible to restore the session through a deliberate action, such as a shortcut. This would enable users to seamlessly continue their work without the need to manually reopen each item.

### Scenario when this would be used?

A typical scenario would be when someone is working on a complex task requiring multiple open files and Explorer windows. Instead of manually restoring everything after a system restart, the user could consciously save all open programs and files with a simple shortcut. After restarting the PC, the saved session could be reopened through a shortcut or similar action, ensuring the workflow remains uninterrupted. This would be particularly beneficial for users working on complex projects, offering significant time savings and convenience.

### Supporting information

_No response_
Repository: deno
Issue: missing Node FS APIs
Labels: node compat

These APIs are missing in `node:fs` module:

- [ ] fchown
- [ ] fchownSync
- [ ] fchmod
- [ ] fchmodSync
- [ ] glob
- [ ] globSync
- [ ] lchmod
- [ ] lchmodSync
- [ ] openAsBlob

Note: This only lists top level APIs in `node:fs` module. The missing `FileHandle` methods are tracked in #25554