sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Don't copy whole response during response marshalling 
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

When experimenting with measuring memory usage for large LIST requests I noticed one thing that surprised me. It's expected that apiserver requires a lot of memory when listing from etcd. It needs to fetch the data, decode etcd, however what about listing from cache? 

I was surprised when listing from cache still required gigabytes of data (10 concurrent list of 1.5GB data increased memory usage by 22GB). Why? apiserver has all the data it needs, we copy structure of data (e.g. converting between types), but data for that should be miniscule. Most data is stored should come from strings, which are immutable. This lead me to revisit old discussion I had with @mborsz and his experimental work on streaming lists from etcd https://github.com/kubernetes/kubernetes/compare/master...mborsz:kubernetes:streaming, he proposed to implement custom streaming encoder. I looked at current implementation of encoding:

* https://github.com/kubernetes/kubernetes/blob/29101e9774e318f502cbdf68080bafe7c5794124/staging/src/k8s.io/apimachinery/pkg/runtime/serializer/json/json.go#L245-L246 
* https://github.com/golang/go/blob/4f0561f9d354233787de7aa9eff8119a2d4cd5c6/src/encoding/json/stream.go#L223-L233

Built In json library encoder still marshalls whole value and writes it at once. While this is ok for single objects that weight 2MB, it's bad for LIST responses which can be up to 2GB. 

I did a PoC that confirmed my suspicions. https://github.com/kubernetes/kubernetes/compare/master...serathius:kubernetes:streaming-encoder-list Simple hack over encoder reduced memory needed from 26GB to 4 GB.

Proposal:
* Validate different options for streaming JSON and Proto encoder for LIST responses and enable it.

Options:
* Custom encoder for List objects based on reflections https://github.com/kubernetes/kubernetes/compare/master...serathius:kubernetes:streaming-encoder-list
* Define a interface to streaming encoding and generate code for all implementations
* Pick some of available streaming encoding libraries.

Other thoughts:
* Can be also expanded to client decoders
* Similar to https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/3157-watch-list/README.md

### Why is this needed?

For LISTs served from watch cache it prevents allocating data proportional to size of response. This makes memory usage more proportional to CPU usage improving cost estimations of APF which cares only about memory.

For LISTs served from etcd there is a ongoing proposal to serve them from cache.
Repository: ui
Issue: [bug]: Combobox selected style is incorrect
Labels: bug

### Describe the bug

![image](https://github.com/user-attachments/assets/11c0b001-eef2-4878-97ce-bf2f35ba1aed)

When I selected Astro and reopened popover, Astro was not selected as the background color, but was displayed on Next.js

### Affected component/components

Combobox

### How to reproduce

1.select Astro
2.reopen popover

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
macos 15.1
chrome 131.0.6778.140
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: next.js
Issue: `next lint` creates .eslintrc.json instead of eslint.config.mjs after deleting initial ESLint config
Labels: create-next-app,Linting

### Link to the code that reproduces this issue

https://github.com/uwoobeat/nextjs-eslint-config-bug

### To Reproduce

1. Clone the repository (created via `npx create-next-app@canary`)
2. Install dependencies: `npm install`
3. Delete `eslint.config.mjs`
4. Run `npm run lint` (or `pnpm lint`)
5. Observe that `.eslintrc.json` is created instead of regenerating `eslint.config.mjs`

### Current vs. Expected behavior

Current behavior:
- After deleting eslint.config.mjs, running `next lint` creates a new .eslintrc.json file with legacy ESLint configuration format, even though the project was initially set up with ESLint v9's config

Expected behavior:
- When running `next lint` after deleting the config file, it should regenerate the same type of configuration file that was initially created (eslint.config.mjs), maintaining consistency with the project's initial ESLint setup

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 18:40:14 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T8103
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 23.4.0
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.1-canary.13 // Latest available version is detected (15.1.1-canary.13).
  eslint-config-next: 15.1.1-canary.13
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

create-next-app, Linting

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

While #71218 added support for ESLint v9, examining `runLintCheck` and `writeDefaultConfig` shows that Next.js still creates .eslintrc.json when regenerating config files. It's unclear whether this is intentional or if the flat config support was meant to be implemented for config regeneration as well.

I noticed that while Next.js detects and properly uses flat config files (eslint.config.*) during linting process, the default config generation still creates legacy format files. Would like to know if this behavior is intended or if it needs to be updated to maintain consistency with the initial flat config setup from create-next-app.
Repository: rust
Issue: No way to get mutable reference to Vec member without expressing uniqueness over the full Vec
Labels: A-collections,T-libs-api,C-feature-request,needs-acp

I've ran into the following standard library defect. There appears to be no possible sound way to go from a `Vec<T>` to a `&mut T` without expressing uniqueness over the full `Vec`. `Vec::as_mut_ptr` does not suffice because it takes a `&mut self` which expresses unique access over the full vec. A function which goes from `*mut Vec<T> -> *mut T` is necessary, but missing. The same is true for `*mut [T] -> *mut T`.

---

Consider the following example, where I have a `v: Vec<Vec<u32>>` where `m.len() == n` and `m[i].len() == t` for all `i`. I have `t` threads and I now want to process this array mutably in parallel, transposed. For example suppose I want to do the following in-place cumulative sum:

```rust
(0..t).into_par_iter().map(|thread_idx| {
    let mut cumsum = 0;
    for i in 0..n {
        // This obviously doesn't work, but you can't write this soundly with pointers either.
        let x: &mut u32 = &mut v[i][thread_idx];
        cumsum += *x;
        *x = cumsum;
    }
})
```

As far as I can tell, there is no way to write this soundly without introducing (potentially significant) overhead **at all**. The only way to write this soundly is to first create a temporary array of pointers and to modify the inner loop to use those pointers:

```rust
let ptrs: Vec<*mut u32> = v.iter_mut().map(|vi| vi.as_mut_ptr()).collect();
    // ...
        let x: &mut u32 = unsafe { &mut *ptrs[i].add(thread_idx) };
}
```

I really think the standard library should offer some kind of way to write this loop soundly without the unnecessary overhead of creating a pointer array. The simplest solution I think is to add functions which go from `*mut Vec<T> -> *mut T` and `*mut [T] -> *mut T` without creating an intermediate unique reference to the entire `Vec` or slice.
Repository: next.js
Issue: adjustFontFallback is not working with Google Fonts in Next.js 15
Labels: Font (next/font)

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/sweet-moon-yzv9yt

### To Reproduce

1. Import any font from fonts/google
2. Set adjustFontFallback to false
3. Apply className of font to body
4. Check if font fallback is applied in the inspector

### Current vs. Expected behavior

**Current behavior:** font fallback is always provided regardless of the adjustFontFallback value
**Expected behavior:** font fallback should only be applied when adjustFontFallback is true. When it's false it should not be applied

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 16272
  Available CPU cores: 12
Binaries:
  Node: 20.17.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.1.1-canary.1 // Latest available version is detected (15.1.1-canary.1).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Font (next/font)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

adjustFontFallback is working correctly in Next.js 14. However, after updating and not touching the font import and config code, it's not working.
Repository: vscode
Issue: Make editor dimming a core workbench feature
Labels: feature-request,workbench-dim-unfocused

The dim unfocused feature is currently built using some CSS overrides to accomplish the majority of what users wanted without much work. For example:

https://github.com/microsoft/vscode/blob/35be9bf683eace09796e59d54f1f225bbc3a7866/src/vs/workbench/contrib/accessibility/browser/unfocusedViewDimmingContribution.ts#L38-L62

Since this relies upon internal CSS classes it's prone to break though. When this feature went through the test phase there were a collection of problems reported, mostly around certain edge cases not working. I'm merging all those issues into this one to track any further development on the feature if we choose to do so:

- #190102
- #191608
- #191615
- #191616
- #191671
- #191714
- #191743
- #191744
- #191757
- #191775
Repository: rust
Issue: `Don't know how to soften fpowi to fpow` on x86 uefi targets
Labels: A-LLVM,T-compiler,O-UEFI,C-external-bug

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
#[no_mangle]
fn f(x: f32, n: i32) -> f32 {
    x.powi(n)
}
```

```
cargo build --target x86_64-unknown-uefi
```

I expected to see this happen: *it compiles*

Instead, this happened:

```
error: Don't know how to soften fpowi to fpow
```

Same error on `i686-unknown-uefi`, but not on `aarch64-unknown-uefi`.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: x86_64-unknown-linux-gnu
release: 1.83.0
LLVM version: 19.1.1
```
Repository: vscode
Issue: Unable to uninstall vscode: Windows cannot find unins000.exe
Labels: bug,install-update

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

<!-- 🪓 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: 1.96.1
- OS Version: 23H2

Steps to Reproduce:

1. I was programming Agda using agda-mode extension. Then I couldn't compile my code anymore using Ctrl+C Ctrl+L.
2. Then I closed the vscode to open it again, but it didn't open.
3. Then I restarted my computer . after that I couldn't open vscode.
4. Then I tried to uninstall the vscode to install it again, now I cannot uninstall vscode
5. ![Image](https://github.com/user-attachments/assets/62b11826-9530-4072-8f1e-d5323349e7d3)
Repository: next.js
Issue: `next.config.ts` breaks when using import aliases
Labels: TypeScript

### Link to the code that reproduces this issue

https://github.com/Larsv94/tsconfig-alias-import-repro

### To Reproduce

1. Start the application in development (`next dev`) or build the application (`next build`)


### Current vs. Expected behavior

When building or starting the application with `next dev` the commands fail with "Error: Cannot find module './src/config/utils/someUtils'" because of `someConfig.ts` import `someUtils.ts` via an import alias.

It does work when `someConfig.ts` uses a relative import (included in example)

Expect import aliases to work as well

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32476
  Available CPU cores: 28
Binaries:
  Node: 20.18.1
  npm: 10.8.2
  Yarn: 4.5.3
  pnpm: N/A
Relevant Packages:
  next: 15.1.2 // Latest available version is detected (15.1.2).
  eslint-config-next: 15.1.2
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, TypeScript

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

### Additional context

_No response_
Repository: rust
Issue: compiletest: FileCheck-based tests conflate FileCheck prefixes with compiletest revisions
Labels: C-cleanup,A-testsuite,E-hard,T-compiler,T-bootstrap,A-compiletest,E-tedious

> Auto-registering revision names as check prefix is a bit sketchy, and that having to pass `--allow-unused-prefix` is an unfortunate side-effect of not knowing whether the test author actually wanted revision-specific check prefixes or not.
>
> -- https://github.com/rust-lang/rust/pull/134463#discussion_r1890184927

With the current scheme where compiletest `//@ revisions` imply FileCheck prefixes of the same names, we can't distinguish between whether the author wanted to:

1. Use compiletest revisions but ONLY for compiletest directive purposes.
2. Use compiletest revisions but ONLY for filecheck prefix purposes.
3. Use compiletest revisions for BOTH purposes.

We might want to investigate splitting these orthogonal concepts and have something like `//@ filecheck-prefixes: XXX` register FileCheck prefixes separately.

Marked as E-hard as this will take quite a bit of investigation/design, and E-tedious as this  probably involves updating a whole bunch of tests, and I don't have the bandwidth to mentor.
Repository: TypeScript
Issue: Computed property invalid in type declaration emitted in d.ts file
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

computed property unique symbols declaration emit

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.2#code/MYGwhgzhAEAq0G8BQ1XQgFzBglsaATgKZgAmA9gHYgCe0A2gEQaMC6AXNAK6U4COXIuhoBbAEbkQAbiQBfJCCIZoAD07I0DWExasO0Sl3FECM2TMXK6AXkQo09bczb6AjHKRA

### 💻 Code

```ts
class T {
    static readonly ["t"]: unique symbol;
}
let x: {
    [T["t"]]: number;
};
let y = {
    [T["t"]]: 1
}

```


### 🙁 Actual behavior

The type of `x` has an error saying: `A computed property name in a type literal must refer to an expression whose type is a literal type or a 'unique symbol' `

The type of `y` is emitted in declaration files just like the type of `x` and causes an error in the d.ts file

### 🙂 Expected behavior

The type of `x` should be valid. If we use a non-computed property name, the type would be valid (`let x: { [T.t]: number; }`,  [Playground Link](https://www.typescriptlang.org/play/?ts=5.7.2#code/MYGwhgzhAEAq0G8BQ1XQgFzBglsaATgKZgAmA9gHYgCe0A2gEQaMC6AXNAK6U4COXIuhoBbAEbkQAbiQBfJCCIZoAD07I0DWADoMHaJS7iiBGbKlA)). Declaration emit should not emit invalid code.

### Additional information about the issue

Probably fixed by #60052 since the limitation on computed property names in types goes away.
Repository: vscode
Issue: NodeJS code has a strange problem when debugging with the npm run dev command! And there is also a strange phenomenon in Remote SSH!
Labels: info-needed

<!-- ⚠️⚠️ 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: 
版本: 1.96.1 (system setup)
提交: 42b266171e51a016313f47d0c48aca9295b9cbb2
日期: 2024-12-17T17:50:05.206Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
- OS Version: 
OS: Windows_NT x64 10.0.17763
Version: Windows Server 2019 Datacenter
Version number: 1809
Installation Date: 11/7/2024
OS Build : 17763.6532

- File structure and all code
![Image](https://github.com/user-attachments/assets/000fca4d-dc9b-4c2f-ab00-d76977b824ce)







Steps to Reproduce:

1. I don't have any third-party plugins installed, except for the Chinese language pack.
2. In the above configuration, press F5 to debug.
3. The "terminal" prints out npm run dev and waits for about 15 seconds before continuing to print the result (123).
4. And there is no output in the debug console, and the breakpoint is invalid, and the code cannot be debugged.
5. After pressing Shift+F5 to stop debugging, manually enter "npm run dev" in the terminal, press the enter key, basically no waiting, and the content will be output soon.
6. Manually enter "node index.js" in the terminal, press the enter key, and "123" will be output instantly.
7. The same code and vscode will work fine on another Windows 11.
8. I use vscode's remote ssh plugin from local Windows 11 to remote this test project, and the same problem occurs. But it's fine to run local code, and it's okay to run other servers remotely.
9. There is also a phenomenon that when I remotely this server from a local computer, I have to add VSCode's remote. SSH.useExecServer setting is turned off in order to link the remote normally, otherwise it will never be able to connect, but it does not need to be turned off when connecting to other servers.![Image](https://github.com/user-attachments/assets/1d5effa8-0577-40bb-b515-48ecb64a4bdd)

I really don't know what went wrong. Please help take a look, thank you!
Repository: langchain
Issue: sql_agent demo Action and Final Answer appear together to cause an exception
Labels: 🤖:bug,investigate

### 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
# llm = ChatOpenAI()

db = SQLDatabase.from_uri("sqlite:///../somedb/db.sqlite")

agent_executor = create_sql_agent(
    llm=llm,
    db=db,
    verbose=True,
)
agent_executor.handle_parsing_errors=True

resp = agent_executor.invoke("查询三分球命中率最高的球员")
print(resp)

```

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

langsmith:

https://smith.langchain.com/public/e8196299-7b02-4314-a38e-bbae8f2f857e/r

### Description

I am using sql_agent at an example time, when the agent is currently running, it is not possible to run the program.

My current LLM analysis calculation time is likely to be a hit. `includes_answer = FINAL_ANSWER_ACTION in text` Use `includes_answer == True` ,then the result is `FINAL_ANSWER_AND_PARSABLE_ACTION_ERROR_MESSAGE`

### System Info

look  langsmith
Repository: tauri
Issue: [feat] Support for native webview clipboard methods without security prompt
Labels: type: feature request

### Describe the problem

The webview has native clipboard methods like `navigator.clipboard.read`, `navigator.clipboard.write` and `navigator.clipboard.readText`, `navigator.clipboard.writeText` but accessing these triggers a security prompt in the webview with an ugly dialog.
Using the clipboard-manager plugin to read an UHD image from the clipboard takes several seconds, because the clipboard content is transferred as an uncompressed 100MB+ bitmap to the webview. 
This the native `navigator.clipboard.read` the JavaScript app can read the clipboard content as image/png and the image is available instantly.

### Describe the solution you'd like

Tauri should support using these native webview clipboard methods without showing the ugly security prompt (alternatively configure permissions in tauri config instead). (like Socket Runtime does: https://github.com/socketsupply/socket)

### Alternatives considered

The "clipboard-manager" plugin allows limited access to the clipboard but has currently many drawbacks:
- images are always uncompressed bitmaps and reading/writing these to the clipboard is slow and inefficient
- not all formats like html are fully supported

### Additional context

The native clipboard APIs have more features and are already available in the native webviews. If technically possible Tauri should support webstandard APIs. This makes porting apps to Tauri easier and more accessible.
Repository: rust
Issue: Rustdoc failure in `armv7` targets with `-neon` with `target_feature(enable = "neon")`
Labels: T-rustdoc,O-Arm,C-bug,A-target-feature

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
#![feature(arm_target_feature)]

#[target_feature(enable = "neon")]
unsafe fn foo() {}
```
This always compiles, but in `armv7` targets that have `-neon` target-feature, running `rustdoc` on it produces the error

```
error: target feature `neon` cannot be toggled with `#[target_feature]`: unsound on hard-float targets because it changes float ABI
 --> bug.rs:3:18
  |
5 | #[target_feature(enable = "neon")]
  |
```
even if the target has `+soft-float` (e.g `armv7-unknown-linux-gnueabi`).

`rustc --version --verbose`:
```
rustc 1.85.0-nightly (9e136a30a 2024-12-19)
binary: rustc
commit-hash: 9e136a30a965bf4e63f03095c57df7257bf96fd6
commit-date: 2024-12-19
host: x86_64-unknown-linux-gnu
release: 1.85.0-nightly
LLVM version: 19.1.6
```

Related: #133417