sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Volume expand controller doesn't have a support for the flexvolume plugin
Labels: kind/bug,sig/storage,lifecycle/frozen,triage/accepted

### What happened?

The flexVolume plugin implements the `ExpandableVolumePlugin` interface, but the expander controller does not add support for it.

- https://github.com/kubernetes/kubernetes/blob/remove-unnecessary-permissions/pkg/controller/volume/expand/expand_controller.go#L118
- https://github.com/kubernetes/kubernetes/blob/remove-unnecessary-permissions/pkg/volume/flexvolume/plugin.go#L59

Is it a bug? the flexVolume plugin has been marked as `deprecated` since v1.23, but it still works.

https://github.com/kubernetes/kubernetes/pull/67851 implemented the Flexvolume resize and said that the flex plugins are not installed on the controller. 

@gnufied said that the flex volume plugin IMO does support allowing expansion from control-plane too. It is just that, most deployments typically don't install the flex volume plugin in the control-plane for various reasons, but if they do and plugin implements expandvolume command, then control-plane expansion will work. 

> if they do and plugin implements expandvolume command, then control-plane expansion will work. 

The prequisite is that the expand controller needs to add support for the flexVolume plugin, but it doesn't now.

What did you expect to happen?



### What did you expect to happen?

One of the following:

- [ ] The expand controller should add support for the flexVolume plugin. (may not be recommended because the flexVolume plugin is deprecated since v1.23. And no users reported this issue in my knowledge)

- [ ] Once the portworx plugin completes csi migration, can we deprecated the expand controller and then remove it in the future. (recommended) but flex plugin also optionally supports attach which can be executed from control-plane. it means that the flex plugin can be installed on the controller.

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

NONE

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
All supported versions
```

</details>


### Cloud provider

<details>
NONE
</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: ollama
Issue: Issue when running smollm:360m and also smollm:135m
Labels: bug

### What is the issue?

I tried running with the 1.7b version, and it ran successfully. 
![image](https://github.com/user-attachments/assets/6074c785-cbb2-43e0-b82d-32fe74184840)
However, when running these two smaller versions, it shows the following error.
![image](https://github.com/user-attachments/assets/419da9f0-0ea2-4795-bdab-78e457dfbd08)


### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.6
Repository: deno
Issue: Suggestion: Add TLS option to `deno serve` command
Labels: feat,serve

The `Deno.serve()` method can enable TLS.
If `deno serve` command also had an option to enable TLS, would be easier to build secure server.

For example, like this:

- `--tls-key <file>` ... Path to private key in PEM format
- `--tls-cert <file>` ... Path to server certificate in PEM format

```sh
deno serve --tls-key ./server.key --tls-cert ./server.crt ./server.ts
```
Repository: vscode
Issue: Already in transaction
Labels: error-telemetry

```javascript
Error: Already in transaction
at s.transact (https:/<REDACTED: user-file-path>:96:986)
at L.Y (https:/<REDACTED: user-file-path>:163:12999)
at L.Y (https:/<REDACTED: user-file-path>:1345:51366)
at L.ib (https:/<REDACTED: user-file-path>:163:18163)
at o.B (https:/<REDACTED: user-file-path>:90:732)
at o.C (https:/<REDACTED: user-file-path>:90:802)
at o.fire (https:/<REDACTED: user-file-path>:90:1018)
at d.value (https:/<REDACTED: user-file-path>:159:20304)
at o.B (https:/<REDACTED: user-file-path>:90:732)
at o.fire (https:/<REDACTED: user-file-path>:90:949)
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=fee1edb8d6d72a0ddff41e5f71a671c23ed924b9&bH=0e38863c-84bd-c37f-c922-9185ab8ab25b)
Repository: vscode
Issue: [1537] potential listener LEAK detected, having 1090 listeners already. MOST frequent listener (1090):
Labels: error-telemetry

```javascript
Error
at c.create in src/vs/base/common/event.ts:921:15
at k.q [as onDidChange] in src/vs/base/common/event.ts:1128:34
at S in src/vs/editor/contrib/semanticTokens/browser/documentSemanticTokens.ts:158:59
at bindDocumentChangeListeners in src/vs/editor/contrib/semanticTokens/browser/documentSemanticTokens.ts:171:4
at o.B in src/vs/base/common/event.ts:1230:13
at o.C in src/vs/base/common/event.ts:1241:9
at o.fire in src/vs/base/common/event.ts:1265:9
at E.register in src/vs/editor/common/languageFeatureRegistry.ts:77:21
at w.$registerDocumentSemanticTokensProvider in src/vs/workbench/api/browser/mainThreadLanguageFeatures.ts:525:96
at S in src/vs/workbench/services/extensions/common/rpcProtocol.ts:458:17
at S.Q in src/vs/workbench/services/extensions/common/rpcProtocol.ts:443:32
at S.M in src/vs/workbench/services/extensions/common/rpcProtocol.ts:373:19
at S.L in src/vs/workbench/services/extensions/common/rpcProtocol.ts:299:10
at u.value in src/vs/workbench/services/extensions/common/rpcProtocol.ts:161:57
at o.B in src/vs/base/common/event.ts:1230:13
at o.fire in src/vs/base/common/event.ts:1261:9
at s.fire in src/vs/base/parts/ipc/common/ipc.net.ts:652:19
at b.A in src/vs/base/parts/ipc/common/ipc.net.ts:1022:23
at u.value in src/vs/base/parts/ipc/common/ipc.net.ts:879:72
at o.B in src/vs/base/common/event.ts:1230:13
at o.fire in src/vs/base/common/event.ts:1261:9
at h.acceptChunk in src/vs/base/parts/ipc/common/ipc.net.ts:394:21
at <anonymous> in src/vs/base/parts/ipc/common/ipc.net.ts:350:51
at listener in src/vs/platform/remote/browser/browserSocketFactory.ts:231:39
at o.B in src/vs/base/common/event.ts:1230:13
at o.fire in src/vs/base/common/event.ts:1261:9
at j.onload in src/vs/platform/remote/browser/browserSocketFactory.ts:92:17
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=fee1edb8d6d72a0ddff41e5f71a671c23ed924b9&bH=1a31847f-6ccb-a4f4-dfd3-ddd2d13b373b)
Repository: rust
Issue: Negative UI test error annotations
Labels: A-testsuite,C-enhancement,T-bootstrap,E-medium,A-compiletest,E-needs-design,E-needs-investigation

I wish there is a negative assertion, saying that here one shall not expect a `HELP` note.

_Originally posted by @dingxiangfei2009 in https://github.com/rust-lang/rust/pull/107251#discussion_r1725678959_

---

Something that might be nice-to-have is *negative* ui test error annotations, i.e. that we explicitly want to make sure some diagnostic is *not* emitted (analogous to FileCheck `check-NOT` annotations).

Obviously, you can rely on checking the blessed stderr, but a negative ui test annotation could help communicate intent in the test itself and is less prone to accidentally letting the blessed stderr though.

Note: we should probably try to make the directive parser more robust and less hacky before attempting to add more syntax.
Repository: neovim
Issue: "nvim --headless --listen ..." does not unlink socket on signal exit/Ctrl-C
Labels: bug,server,complexity:low,startup

### Problem

If Neovim is started with `--headless --listen /some/unix/socket`, and `bind` returns `EADDRINUSE` because the socket file already exists, Neovim does not report any error and just continues running, but will not accept any connections on the socket.

### Steps to reproduce

`nvim --headless --listen ./hello.sock`
(Ctrl-C, check that ./hello.sock exists now)
`nvim --headless --listen ./hello.sock`
(Try to connect via `nvim --remote-ui --server ./hello.sock`)

If needed, use `strace nvim --headless --listen ./hello.sock |& grep hello` to verify that `bind` errors.

### Expected behavior

Neovim should handle this situation gracefully, either by exiting with an error, or trying to determine if the socket is actually used, and unlinking/recreating it if not.

### Neovim version (nvim -v)

NVIM v0.11.0-dev-655+g6af9ca492

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

N/A

### Operating system/version

Arch Linux

### Terminal name/version

wezterm

### $TERM environment variable

xterm-256color

### Installation

`neovim-nightly-bin` AUR package (downloads latest github release)
Repository: rust
Issue: Remove time-boxed `time` inference regression mitigation note
Labels: C-cleanup,A-diagnostics,T-compiler

We should remove the `time` inference regression diagnostics note once sufficient time has passed.

Introduced in #129343 to help guide users to update their `time` version.

See https://github.com/rust-lang/rust/pull/129343#issuecomment-2304993629 for more context.

cc @apiraino as you wanted to make sure it gets removed eventually (thank you!)
Repository: vscode
Issue: Watch expressions should allow LSP or debugger to remove inner whitespaces
Labels: feature-request,debug

Watch expressions should allow LSP or debugger to remove inner whitespace.

In languages like Dart, most of the time (and even more so in the future with the new tall formatter) you can select multiple lines that represent a single expression and add them to the watch list. 

Currently, we end up with lots of whitespaces between every line because of indentation and such. There could be an option for the LSP or debugger to remove inner spaces when that will not interfere with the expression (like spaces inside strings and such should not be removed).

### Edit

This could be expanded to remove trailing `;` and similar as well.
Repository: deno
Issue: Perf: `structuredClone` runs slow compared to `bun` and `node`
Labels: perf,needs investigation

OS: Windows 11
deno version: 1.46.1
bun version: 1.1.25
node version: 21.5.0
Test script:
```js
const testArray = [{
  description: 'Random description.',
  testNumber: 123456789,
  testBoolean: true,
  testObject: {
    testString: 'test string',
    testNumber: 12345
  },
  testArray: [{
    myName: 'test name',
    myNumber: 123245
  }]
},{
  description: 'Random description.',
  testNumber: 123456789,
  testBoolean: true,
  testObject: {
    testString: 'test string',
    testNumber: 12345
  },
  testArray: [{
    myName: 'test name',
    myNumber: 123245
  }]
    }];

let testCopy = null;

testCopy = structuredClone(testArray);
```
Result:
```bash
hyperfine -N --warmup=100 "node test.js" "bun run test.js" "deno run test.js"

Benchmark 1: node test.js
  Time (mean ± σ):      34.6 ms ±   0.8 ms    [User: 18.9 ms, System: 14.4 ms]
  Range (min … max):    33.4 ms …  37.4 ms    87 runs

Benchmark 2: bun run test.js
  Time (mean ± σ):      43.5 ms ±   1.4 ms    [User: 18.4 ms, System: 26.3 ms]
  Range (min … max):    41.6 ms …  48.0 ms    63 runs

Benchmark 3: deno run test.js
  Time (mean ± σ):      93.5 ms ±   1.4 ms    [User: 21.7 ms, System: 18.1 ms]
  Range (min … max):    90.4 ms …  96.1 ms    31 runs

Summary
  node test.js ran
    1.26 ± 0.05 times faster than bun run test.js
    2.70 ± 0.08 times faster than deno run test.js
```

It seems that other 2 runtime implements it in native.
Repository: PowerToys
Issue: Advanced Paste clipboard concatenation
Labels: Idea-Enhancement,Needs-Triage,Product-Advanced Paste

### Description of the new feature / enhancement

Similar to how copy and paste works with Alfred on Mac, pressing Ctrl+C twice in quick succession would add the current clipboard selection to the previous one.

### Scenario when this would be used?

When copying large pieces of text across multiple documents, cross-referencing from multiple sources, etc.

### Supporting information

_No response_
Repository: TypeScript
Issue: Optimal TS monorepos: how to handle project references when projects opt out of composite within dependency chain
Labels: Needs Investigation

### 🔎 Search Terms

project references
no output

### 🕗 Version & Regression Information

N/A

### ⏯ Playground Link

N/A

### 💻 Code

```ts
// Your code here
```


### 🙁 Actual behavior

Please see full description, repro and video walkthrough

### 🙂 Expected behavior

Please see full description, repro and video walkthrough

### Additional information about the issue

I am reporting this as an issue because @jakebailey advised me that that would make sense for any time a Debug Error is reached in TS, but also to get formal guidance from the TS Team on finalizing our new TypeScript plugin for Nx.

As discussed in our sync between our teams a couple of months ago, we are building a new mechanism to sync Nx project graph (derived from package.json files and import and export statements) automatically to configuration files on disk. This is a generic mechanism, but in the context of TS, this applies to syncing project references in tsconfig.json files.

This should allow us to keep Nx out of the way of `tsc` where appropriate (`tsc` will be directly executed by Nx behind the scenes when using `nx typecheck my-ts-proj` or `nx build my-ts-proj` for example) and still allow users to run raw `tsc` if they wish because all the relevant config will live on disk and be up to date thanks to Nx.

The syncing mechanism is working really well already for repo's which can fully stick to `composite: true` throughout the codebase, but we have already run into one case on the https://github.com/typescript-eslint/typescript-eslint (where @jakebailey and @sheetalkamat kindly help out) where a couple of projects needed to opt out of `composite: true` and not emit declaration files at all.

As explained in detail in attached loom covering the reproduction repo, we would like some advice on how we should attempt to handle cases like this in our syncing logic.

The super brief summary of the issue causing it to hit the Debug Failure is:
- Projects: A -> B -> C
- B is opting out of composite
- The root solution file can happily reference all 3 projects as hoped, despite the composite opt out of B
- We want to be able to typecheck A, B and C
- `tsc -b --emitDeclarationOnly` is used for typechecking (intentionally kept distinct from _building_ with `tsc`, producing JS artifacts)
- When typechecking the whole repo, or typechecking just A, we hit the Debug failure because of B not having any outputs before proceeding onto A

**🎥 Context and issue reproduction:** https://www.loom.com/share/84a7098b3d1e4a819bd598ad7fc3ae7f

**🔗 Reproduction repo:** https://github.com/JamesHenry/tsc-composite-false-repro
Repository: ui
Issue: [bug]: 404 This page could not be found in nextjs production
Labels: bug

### Describe the bug

404
This page could not be found.

### Affected component/components

build issue

### How to reproduce

module.exports = {
  output: "standalone",
  images: {
    domains: ["meethour.s3.amazonaws.com"],
    unoptimized: true,
  },
};

  "scripts": {
    "dev": "node app.js",
    "build": "next build",
    "start": "export NODE_ENV=production && node app.js",
    "release": "sh release.sh",
    "lint": "npm run pretty && next lint",
    "lint-fix": "next lint --fix",
    "sass": "node-sass --watch public/scss/main.scss public/css/style.css --source-map public/css/style.css.map",
    "pretty": "prettier --write \"./**/*.{js,jsx,mjs,cjs,ts,tsx,json}\""
  },
  "dependencies": {
    "@fortawesome/fontawesome-svg-core": "^6.6.0",
    "@fortawesome/free-solid-svg-icons": "^6.6.0",
    "@fortawesome/react-fontawesome": "^0.2.2",
    "@reduxjs/toolkit": "^1.9.7",
    "axios": "^1.6.7",
    "bootstrap": "^5.3.0",
    "dompurify": "^3.1.4",
    "express": "^4.19.2",
    "fs": "^0.0.1-security",
    "html-react-parser": "^5.1.10",
    "js-sha256": "^0.11.0",
    "mdb-react-ui-kit": "^6.2.0",
    "metismenujs": "^1.4.0",
    "moment": "^2.30.1",
    "next": "^14.2.4",
    "next-unused": "^0.0.6",
    "node-sass": "^9.0.0",
    "path": "^0.12.7",
    "react": "^18.3.1",
    "react-bootstrap": "^2.7.4",
    "react-countup": "^6.4.2",
    "react-dom": "^18.3.1",
    "react-google-recaptcha": "^3.1.0",
    "react-helmet": "^6.1.0",
    "react-hook-form": "^7.51.1",
    "react-loading-skeleton": "^3.4.0",
    "react-player": "^2.13.0",
    "react-redux": "^8.1.3",
    "react-search-autocomplete": "^8.5.2",
    "react-share": "^5.1.0",
    "react-slick": "^0.29.0",
    "react-visibility-sensor": "^5.1.1",
    "redux": "^4.2.1",
    "sharp": "^0.32.1",
    "slick-carousel": "^1.8.1",
    "video-react": "^0.16.0",
    "wowjs": "^1.1.3"
  },
  
  release.sh
  #!/bin/bash

NODE_ENV=production
rm -r out out.zip
npm run build && mkdir out
cd ./.next/standalone
cd ../..
cp -r ./.next/standalone/* ./.next/standalone/.next ./public ./slices ./utils ./out
cp -r ./.next/static ./out/.next/static
mv ./out/server.js ./out/app.js
cp ./app.js ./out/app.js
rm -fr ./out/node_modules
cp -r node_modules ./out/node_modules 
cp package.json ./out/package.json
zip -r out.zip ./out
rm -fr ./out && rm -fr ./.next
  


### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
404
This page could not be found.
```


### System Info

```bash
module.exports = {
  output: "standalone",
  images: {
    domains: ["meethour.s3.amazonaws.com"],
    unoptimized: true,
  },
};
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: TypeScript
Issue: The order of values ​​in a union affects the correct type inference
Labels: Help Wanted,Possible Improvement,Union Order Dependence

### 🔎 Search Terms

union order type infer 

### 🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about `union` / `order`

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.5.4#code/C4TwDgpgBAshDO8CGBzaBeKBvKB7MwAlrgHbwD8AXFAEoQDGuATgCYA88wThJKANFACuJANYlcAdxIA+KAF8A3ACgloSFAASSEiwA2EJmwAqszAAoAtgmRpqRgJRR0sgG65CLZUpYNdSJtAAZsL0RKRQ8IIARvD03FEQxlAQAB7AEDrwsNaoENJmSlBFUGBIILq4SCyUhcVFAD7YUFaIuXbyUABkTQAW2noG1Fo6+oYm8rV1jTgtNhDUZo7OUEYd3Th9I4Oa-aPGsnK19tRuHl6RMXGECWZYtbNtUItOsrd4BMRk1DP+IhDA1AA5BZfv9AR05PY+LVNgMmAscPgwmR5EtZHc6pjigB6bFQAB65FqcmhkOUQA

### 💻 Code

```ts
type Message = { options?: Record<string, unknown> };

type Handler<T> = (message: T) => void;

declare function subscribe<T extends Message>(
    payload:
      | { message: T } & { handler: Handler<T> }
      | { message: () => T } & { handler: Handler<T> }
  ): void;

subscribe({
  message: () => ({ options: { market: 'market' } }),
  handler: ({ options }) => {
                  // ^? Record<string, unknown>
  },
});
```


### 🙁 Actual behavior

`options` type is `Record<string, unknown>`

### 🙂 Expected behavior

`options` type should be inferred as `{ market: string }`

### Additional information about the issue

if you reverse the order of values in the union:

```ts
declare function subscribe<T extends Message>(
    payload:
      | { message: () => T } & { handler: Handler<T> }
      | { message: T } & { handler: Handler<T> }
  ): void;
```

then the type will be inferred correctly
Repository: deno
Issue: Feat: Add a way to detect if a file is run by `deno serve` or `deno run`
Labels: cli,suggestion

**Add a way to detect if a file is run by `deno serve` or `deno run`.** 

Maybe add a variable like `Deno.subcommand` which has the type

```typescript
declare namespace Deno {
  export const subcommand: "run" | "serve" | "task" | "test" | "bench" | "jupyter" | "repl" | "eval" | "install" | "uninstall" | "add" | "remove";
}
```

In production I want to use `deno serve --parallel` but locally I want to to use `Deno.serve()`. The reason is a bit complicated but basically my default export takes 5-10 seconds before it's exported which delays `deno serve` starting the server by over 5 seconds, however using `Deno.serve()` allows me to start the server almost instantly. In production I don't have the delay.

(N.B. I can't switch to `deno serve` at all because of this blocker #24099 but I want to!.)
Repository: ollama
Issue: Phi3.5 broken behaviour 
Labels: bug

### What is the issue?

As mentioned by a few others in https://github.com/ollama/ollama/issues/6449 the phi3.5 models never stop responding and quickly become nonsensical

example:
![image](https://github.com/user-attachments/assets/15ad7703-6380-4d33-a8f8-1cd121575231)


### OS

WSL2

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.3.6
Repository: TypeScript
Issue: Inlay variance hints
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

inlay hints, variance annotations

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Display missing variance annotations for type parameters as inlay hints.

Examples:

```ts
type Ex1<T> = {}

type Ex2</* out */ T> = () => T

type Ex3</* in */ T> = (in: T) => void

type Ex4</* in out */ T> = (in: T) => T
```

### 📃 Motivating Example

It is convenient to know variance of specific type parameters when you're trying to understand how a type works/should be used.

### 💻 Use Cases

Examining complex 3rd party types.
Repository: ant-design
Issue: Range slider works incorrectly
Labels: help wanted,Inactive

### Reproduction link

[https://gyazo.com/e194a7d02a4faf0855993efa444d5c2a](https://gyazo.com/e194a7d02a4faf0855993efa444d5c2a)

### Steps to reproduce

1. hold down the mouse left button
2. select text through the slider https://gyazo.com/9dc434831e262ac8d091139f60b8f9cd
3. release the mouse button

### What is expected?

The slider does not move with the mouse

### What is actually happening?

the slider moves behind the mouse

| Environment | Info |
| --- | --- |
| antd | 5.20.2 |
| React | - |
| System | Mac OS |
| Browser | Chrome 127 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->