sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: follow-up(scheduler): some plugins missing in the filter and score part in the integration test
Labels: sig/scheduling,needs-triage

Check the [filter](https://github.com/kubernetes/kubernetes/tree/master/test/integration/scheduler/filters) [score](https://github.com/kubernetes/kubernetes/tree/master/test/integration/scheduler/scoring) part of the scheduler integration test. We found that some plugins' filter and score are not implemented. I will increase the test coverage to make the plugin test complete. 

filter part: 
- [ ] NodePorts @googs1025 
- [ ] NodResources @googs1025 
- [ ] NodeAffinity @googs1025 
- [ ] DynamicResources @googs1025 
- [ ] TaintToleration @googs1025 

score part: 
- [ ] ~DynamicResources~
- [ ] TaintToleration
Repository: react
Issue: Bug: suspected React 19 issue in React Documentation interactive app
Labels: Status: Unconfirmed

I suspect an issue with React v19, or if not a React v19 issue, an issue with the code in the React Documentation

React version: v19

## Steps To Reproduce

1. go to https://react.dev/learn/render-and-commit
2. scroll down to the first interactive app, see screenshot.
3. Delete line 5 in the code.
4. hit the reset button in the upper right corner, then hit on ok.
5. instead of seeing the image rendered on the right, it is empty.
6. click a random line in the code (of course without changing something), hit the ENTER key, and the image is rendered.

<img width="891" alt="Image" src="https://github.com/user-attachments/assets/26cb147c-f52e-4f53-9d34-595028dd0e81" />

.


Link to code example:

https://react.dev/learn/render-and-commit

## The current behavior

When you remove the code in line 5, then click on reset and click on ok, no image is rendered, unless you click the code and hit the ENTER key.

## The expected behavior

When you remove the code in line 5, then click on reset and click on ok, an image should be rendered without having to click the code and hit the ENTER key.

PS: I have experienced random clicking issues with the interactive examples in the React Documentation.
Repository: angular
Issue: Provide multiple classes / tokens with single definition
Labels: feature,area: core,core: di

### Which @angular/* package(s) are relevant/related to the feature request?

_No response_

### Description

Right now, if I want to register multiple types to DI, I need to repeat my definition, e.g.

```
{
    provide: SETTINGS_PAGE_DEFINITION,
    useClass: DashboardSettingsPageDefinition,
    multi: true
},
{
    provide: SETTINGS_PAGE_DEFINITION,
    useClass: TerminplanerSettingsPageDefinition,
    multi: true
},
{
    provide: SETTINGS_PAGE_DEFINITION,
    useClass: GoogleSyncSettingsPageDefinition,
    multi: true
},
{
    provide: SETTINGS_PAGE_DEFINITION,
    useClass: LeistungserfassungSettingsPageDefinition,
    multi: true
},
```

Same for use `useExisting`. `useValue` or `useFactory` allows me to return an array but the token than sure contains an array of array. You can work around it but its not typed correct etc..

Wouldn't it be nice to be able to register multiple tokens / classes etc. at once?

### Proposed solution

```
{
    provide: SETTINGS_PAGE_DEFINITION,
    useClass(es?): [DashboardSettingsPageDefinition, TerminplanerSettingsPageDefinition, GoogleSyncSettingsPageDefinition, LeistungserfassungSettingsPageDefinition]
    multi: true
}
```

### Alternatives considered

Using a factory, returning an array. Works but a bit quirky.
Repository: transformers
Issue: Llama3.2: Allow batch to have
Labels: Feature request,VLM

### Feature request

Currently, llama3.2 requires either no images per batch or each example have at least one image. Is there some easy workaround (apart from feeding dummy images which is computationally expensive) to allow some examples to have images and other examples to have no images?

Current error message:
`"If a batch of text is provided, there should be either no images or at least one image per sample"`

from https://github.com/huggingface/transformers/blob/3f860dba553d09a8eb96fded8d940c98a9a86854/src/transformers/models/mllama/processing_mllama.py#L303

### Motivation

Not all examples may have images, but some do.

### Your contribution

Could possibly submit a PR
Repository: ollama
Issue: Ollama is not installing on Termux
Labels: feature request

~ $ curl -fsSL https://ollama.com/install.sh | sh
```
>>> Installing ollama to /usr
No superuser binary detected.
Are you rooted?
```
Repository: ollama
Issue: Use of System Ram over RDMA in GPU to allow for GPU acceleration on lower VRAM hardware.
Labels: feature request

Hi all!

I'm a GPU dev who has been messing around with Ollama for some self hosting. I was wondering if there is any reason Ollama has not been able to take advantage of GPU acceleration while using system RAM through RDMA(reBar). I have done system ram access through RDMA on GPU for real time processing and have had better results than CPU side tasks despite the increase in data latency when going over PCIE.

I look forward to hearing from you!
Repository: ollama
Issue: Upload compressed package file, unable to decompress and error reported
Labels: bug

### What is the issue?

Thanks for this great program, I love it! However, I uploaded a compressed package containing the project source code in the dialog interface, and an error occurred when the program was run. Can this problem be solved?

![Image](https://github.com/user-attachments/assets/2c6d9c78-5512-4b4e-a60e-04b98efb60ea)

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: vscode
Issue: Extensions - publisher trust dialog shown while creating a profile
Labels: bug,extensions,user-profiles

Steps to Reproduce:

1. Install the latest VS Code Insiders release
2. Create a new profile from the Python template
3. During profile creation the "publisher trust" dialog is shown multiple times
Repository: awesome-mac
Issue: 🐝 Feature request: add a icon for unmaintained apps and/or move them to a seperate list
Labels: help wanted

### Is your feature request related to a problem? Please describe.

I am frustrated when I click into one link only to find out that an app is not maintained and the last update was like 5 years ago.

### Describe the solution you'd like

add a icon for unmaintained apps and/or move them to a seperate list

### Describe alternatives you've considered

_No response_

### 📖 Additional contex

_No response_

### 🧨 Issue Checklist

- [ ] I have checked for other similar issues
- [ ] I have explained why this change is important
- [ ] I have added necessary documentation (if appropriate)
Repository: ollama
Issue: can't install deepseek 1.7b on windows
Labels: bug,networking

### What is the issue?


while trying to run ollama run deepseek-r1:7b it repeatedly fails at about 6%.everytime i try to run deepseek
 i get an error saying error max retries exceeded: EOF



### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

latest
Repository: PowerToys
Issue: Ability to Center Active Window on Nearest Monitor
Labels: Needs-Triage

### Description of the new feature / enhancement

When working with various tools, theres a chance a window "gets lost". Even more so, when it is a child window. This utility, https://github.com/Devail1/window-center-resize, helps with it.

### Scenario when this would be used?

When a child window is lost and other means of moving it are not working

### Supporting information

This tool is working for me at the moment:
https://github.com/Devail1/window-center-resize
Repository: electron
Issue: TLS with Ed25519 based certificates failing
Labels: platform/windows,bug :beetle:,has-repro-repo,34-x-y

### Preflight Checklist

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

### Electron Version

34.0.1

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

Windows

### Operating System Version

Windows 11 Pro 24H2 (26100.3025)

### What arch are you using?

x64

### Last Known Working Electron version

_Probably none_

### Expected Behavior

Electron is able to deal with connections where client and/or server using certificates with Ed25519 based certificates. The testcase (see below) should generate the same output as running this with plain Node.js, like:
```text
TLS 32144: client _init handle? true
TLS 32144: client initRead handle? true buffered? false
TLS 32144: client _start handle? true connecting? false requestOCSP? false
TLS 32144: client onhandshakedone
TLS 32144: client _finishInit handle? true alpn false servername localhost
TLS 32144: client emit secureConnect. authorized: true
TLS 32144: client emit session
TLS 32144: client emit session
statusCode: 200
headers: {
  date: 'Tue, 28 Jan 2025 14:14:16 GMT',
  connection: 'keep-alive',
  'keep-alive': 'timeout=5',
  'transfer-encoding': 'chunked'
}
```

### Actual Behavior

But it produced:
```
TLS 41608: client _init handle? true
TLS 41608: client initRead handle? true buffered? false
TLS 41608: client _start handle? true connecting? false requestOCSP? false
Error: write EPROTO 1009216:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:..\..\third_party\boringssl\src\ssl\tls_record.cc:579:SSL alert number 40

    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:95:16) {
  errno: -4046,
  code: 'EPROTO',
  syscall: 'write'
}
TLS 41608: client onerror [Error: 1009216:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:..\..\third_party\boringssl\src\ssl\tls_record.cc:579:SSL alert number 40
] {
  library: 'SSL routines',
  function: 'OPENSSL_internal',
  reason: 'SSLV3_ALERT_HANDSHAKE_FAILURE',
  code: 'ERR_SSL_SSLV3_ALERT_HANDSHAKE_FAILURE'
} had? true
```

The server side (if in debug mode) reports `ERR_SSL_NO_SUITABLE_SIGNATURE_ALGORITHM`.

### Testcase Gist URL

https://github.com/blaubaer/electron-tls-ed25519-bug-testcase

### Additional Information

The same testcase works perfectly with Node.js directly, but once Electron is involved (regardless if main thread or not) it fails.

If the same server (as in the testcase) is used, connecting with the certificates and keys was also successfully tested with Golang `1.23` and Java `21`.

Electron also works with RSA 4096.
Repository: angular
Issue: Unused imports diagnostics for modules
Labels: area: compiler,compiler: extended diagnostics

### Command

build

### Description

Recently the new flag "unusedStandaloneImports" was added that detects unused standalone imports in the given standalone components. 

It works just fine, however there're quite a lot of use cases where modules are applicable even along with standalone components, e.g. complex UI packages like `@angular/material/tabs`, thus having the diagnostics to check whether such modules are used is also highly valuable.

I understand that resolving all dependencies of a module is much more computationally heavy operation in comparison with standalone components, but I can still see it being useful as an optional flag that can be enabled only on CI or to cleanup such imports manually from time to time.

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_
Repository: ui
Issue: [bug]: not able to locate the components route when running the repo locally
Labels: bug

### Describe the bug

I have cloned down this repo, every another route is working fine, this error is mainly coming when I am clicking on the components from the top navbar,
I am on Windows 10,
I tried running `$ pnpm --filter=www dev`, `$ pnpm dev`, `$ pnpm www:dev`, all are giving me the same error



![Image](https://github.com/user-attachments/assets/acca961b-8b7b-4ad2-aaa5-2c6a8e1fa4c5)
![Image](https://github.com/user-attachments/assets/75978729-965e-4bef-bbc4-64e91683621f)

### Affected component/components

components

### How to reproduce

try clicking the components in the local running repo

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
Windows 10, Chromium
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: ollama
Issue: Add install location variable to linux
Labels: feature request

I would like to specify install location either with a parameter --install-dir or with a variable $OLLAMA_INSTALL_DIR or both

the variable already exists in installer script, so it should be enough to allow overwriting it with custom value. something like:


```
export OLLAMA_INSTALL_DIR="/home/user/ollamainst"
curl -fsSL https://ollama.com/install.sh | sh

```
Repository: kubernetes
Issue: Clarify When to Set the timestamp and containersStatuses Fields in PodSandboxStatusResponse
Labels: kind/documentation,sig/node,needs-triage

When the evented PLEG is enabled, the kubelet determines whether to retrieve container statuses from the `PodSandboxStatusResponse` by checking if its `timestamp` field is empty.
Ref: https://github.com/kubernetes/kubernetes/blob/7140b4910c6c1179c9778a7f3bb8037356febd58/pkg/kubelet/kuberuntime/kuberuntime_manager.go#L1634-L1656

However, in containerd/containerd#10740, the `timestamp` field of `PodSandboxStatusResponse` was populated, while the `containersStatuses` field was not. This clearly breaks the evented PLEG functionality.

The maintainers of containerd were unaware of how the kubelet uses the timestamp field, and there are no existing comments documenting when these fields should be populated.

To address this, I propose clarifying in the comments of `PodSandboxStatusResponse` the conditions under which the `timestamp` and `containersStatuses` fields should be set.

While this is a minor clarification, it has already caused misunderstandings and impacted real-world functionality. For this reason, I am opening an issue to discuss and formally document the expectations around these fields.

relate: #129818
Repository: PowerToys
Issue: Feature Request: add color contrast calculator (WCAG) to the color picker
Labels: Needs-Triage

### Description of the new feature / enhancement

It would be great if the color picker could calculate color contrast according to the WCAG requirements against #fff / #000 or a custom color chosen by the user. Initially, it would calculate the contrast for both #fff and #000 and indicate the contrast ration and maybe additionally a "pass" or "fail" for WCAG AA. Then the user could be able to change the background colors to any custom color he chooses.

### Scenario when this would be used?

Digital Designers have to incorporate digital accessibility guidelines in their designs. 
This would help immensely with finding accessibility problems!

### Supporting information

Similar to: https://colorcontrast.app/ or https://www.aremycolorsaccessible.com/
Repository: material-ui
Issue: [docs] Using Joy UI and Material UI together
Labels: status: waiting for maintainer,support: docs-feedback

### Related page

https://mui.com/joy-ui/integrations/material-ui/#set-up-the-providers , https://mui.com/material-ui/integrations/theme-scoping/

### Kind of issue

Unclear explanations

### Issue description

I'm using Joy UI with Material UI.  However, I dont understand which document is right.  

[This correct](https://mui.com/material-ui/integrations/theme-scoping/) ;

```
import { ThemeProvider, THEME_ID, createTheme } from '@mui/material/styles';
import { AnotherThemeProvider } from 'another-ui-library';

const materialTheme = createTheme(/* your theme */);

function App() {
  return (
    <AnotherThemeProvider>
      <ThemeProvider theme={{ [THEME_ID]: materialTheme }}>
        {/* components from another library and Material UI */}
      </ThemeProvider>
    </AnotherThemeProvider>
  );
}
```

[or this](https://mui.com/joy-ui/integrations/material-ui/#set-up-the-providers) ; 

```
import {
  extendTheme as materialExtendTheme,
  CssVarsProvider as MaterialCssVarsProvider,
  THEME_ID as MATERIAL_THEME_ID,
} from '@mui/material/styles';
import { CssVarsProvider as JoyCssVarsProvider } from '@mui/joy/styles';
import CssBaseline from '@mui/material/CssBaseline';

const materialTheme = materialExtendTheme();

export default function App() {
  return (
    <MaterialCssVarsProvider theme={{ [MATERIAL_THEME_ID]: materialTheme }}>
      <JoyCssVarsProvider>
        <CssBaseline enableColorScheme />
        ...Material UI and Joy UI components
      </JoyCssVarsProvider>
    </MaterialCssVarsProvider>
  );
}
```


### Context

_No response_

**Search keywords**: using-joy-with-mui
Repository: neovim
Issue: `on_detach` on `nvim_buf_attach` is not triggered with returning truthy value
Labels: api

### Problem

It appears that `on_detach` on `nvim_buf_attach` is not triggered when buffer is detached by `on_bytes` returning a truthy value.

### Steps to reproduce

It appears that `on_detach` on `nvim_buf_attach` is not triggered when buffer is detached by `on_bytes` returning a truthy value.
(Detached by `:bwipe` did work as expected.)

1. Prepare the minimal lua script (issue-on_detach.lua):

   ```lua
   local count = 0
   vim.api.nvim_buf_attach(0, false, {
     on_bytes = function()
       vim.notify("count = " .. count)
       count = count + 1
       if count > 2 then
         vim.notify("detaching")
         -- Return truthy to detach,
         return vim.print(true)
       end
     end,
     on_detach = function()
       -- but `on_detach` is not triggered.
       vim.notify("detached")
     end,
   })
   vim.notify("loaded")
   ```

2. Start nvim with the lua script:

   ```sh
   nvim --clean -u NONE -S issue-on_detach.lua
   ```

   NOTE: Loading by `-u` did not work.

   ```sh
   nvim --clean -u issue-on_detach.lua
   ```

3. Input some texts like "foobar" in the empty buffer.

4. Run `:messages`, but no "detached" in the output.

   ```log
   loaded
   count = 0
   count = 1
   count = 2
   detaching
   true
   ```


### Expected behavior

```
loaded
count = 0
count = 1
count = 2
detaching
true
detached
```

### Nvim version (nvim -v)

NVIM v0.11.0-dev-c4749679

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

no

### Operating system/version

NixOS 24.11

### Terminal name/version

alacritty 0.14.0

### $TERM environment variable

tmux-256color

### Installation

bob or nix
Repository: flutter
Issue: Remove direct usages of python3 and replace with vpython3
Labels: team-infra,fyi-engine

Email to Luci announce https://groups.google.com/a/google.com/g/flutter-team/c/_kU2X6e0aF8/m/BOtIA4tREgAJ?utm_medium=email&utm_source=footer 


luci is moving from python 3.8 to 3.11 (https://chrome-internal-review.googlesource.com/c/infradata/config/+/7983127,) 
If you are using vpython3, this change will not affect you - vpython3 allows you to specify the version of python in your .vpython3 spec. This will only affect processes which run `python3` directly. Recipes are an example of this - they have been using 3.11 for [about a year](https://chromium.googlesource.com/infra/luci/recipes-py/+/bc823506675bfff173e2af808db497d7c11a484c) a this point.


There are places in ourcodebase where we call python3 directly. 

[General search](https://github.com/search?q=repo%3Aflutter%2Fflutter%20python3&type=code)

Specific examples: 
* https://github.com/flutter/flutter/blob/9e273d5e6e2e75336f26951a09aba0f5656a7e77/dev/bots/prepare_package/archive_publisher.dart#L180 
* https://github.com/flutter/flutter/blob/9e273d5e6e2e75336f26951a09aba0f5656a7e77/engine/src/flutter/tools/gn#L833
* https://github.com/flutter/flutter/blob/9e273d5e6e2e75336f26951a09aba0f5656a7e77/dev/bots/test/prepare_package_test.dart#L495 
* https://github.com/flutter/flutter/blob/9e273d5e6e2e75336f26951a09aba0f5656a7e77/engine/src/flutter/ci/impeller_cmake_build_test.py#L74 
* 

Lots of places where we use `!/usr/bin/env python3` [example](https://github.com/flutter/flutter/blob/9e273d5e6e2e75336f26951a09aba0f5656a7e77/engine/src/flutter/tools/fuchsia/depfile_path_to_relative.py#L1) at the top of a file instead of `#!/usr/bin/env vpython3` [vpython example](https://github.com/flutter/flutter/blob/9e273d5e6e2e75336f26951a09aba0f5656a7e77/engine/src/flutter/tools/githooks/pre-push#L1)
Repository: vscode
Issue: `registerDocumentPasteEditProvider` misses the blurb about multiple provider case
Labels: bug

Testing #238916

With `registerXYZ`-functions we usually document what happens when multiple providers are selected, like [here](https://github.com/microsoft/vscode/blob/7a3d738bbb52a0222cbd97277b07d93113b79139/src/vscode-dts/vscode.d.ts#L14859-L14861). This is missing for the paste-provider
Repository: angular
Issue: Angular 19 - Signal Inputs and Web Components routed vs page load
Labels: area: elements

### Which @angular/* package(s) are the source of the bug?

elements

### Is this a regression?

Yes

### Description

We are experiencing an issue with input signals in a web component. When navigating to a page containing the web component via routing, the input signals are set correctly. However, if the page is reloaded directly (e.g., by refreshing the browser), the input signals are not initialized as expected.

Switching from input() to @Input resolves the issue. Below is a reproduction of the problem:

Steps to Reproduce:
Run the app and web component server as outlined in the README.
Navigate to http://localhost:5500/.
Click on "Go to Counter".
Observe that the initial values are correctly set to 5 and 10.
Refresh the browser.
Notice that the initial values revert to 0.
This behavior occurs for various input types, including booleans, objects, and numbers.

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/~/github.com/vickieallen-certua/angular-input-signals-web-components

### Please provide the exception or error you saw

```true

```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 19.1.4
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 19.1.3
... animations, common, compiler, compiler-cli, core, elements
... forms, platform-browser, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1901.4
@angular-devkit/build-angular   19.1.4
@angular-devkit/core            19.1.4
@angular-devkit/schematics      19.1.4
@angular/cli                    19.1.4
@schematics/angular             19.1.4
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.15.0
```

### Anything else?

_No response_