sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking issue for release notes of #134283: fix(libtest): Deprecate '--logfile'
Labels: T-libs-api,relnotes,A-libtest,I-release-nominated,relnotes-tracking-issue


This issue tracks the release notes text for #134283.

### Steps

- [x] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [x] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Libraries
- [Deprecate libtest's '--logfile' option](https://github.com/rust-lang/rust/pull/134283)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @epage, @Amanieu -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Port tests to use the intrinsic macro
Labels: C-cleanup

> `tests/ui/simd` has a bunch of test cases that need porting, I would suggest those be ported in a separate PR before we do the final big PR that removes support for this ABI from the compiler entirely. 

 _Originally posted by @RalfJung in [#132735](https://github.com/rust-lang/rust/issues/132735#issuecomment-2609964087)_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"vayunbiyani"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: go
Issue: cmd/link/internal: panic in loader.(*SymbolBuilder).SetBytesAt
Labels: NeedsInvestigation,Tools,compiler/runtime

```
#!watchflakes
default <- pkg == "golang.org/x/tools/gopls/internal/test/integration/template" && test == ""
```

Issue created automatically to collect these failures.

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

    FAIL	golang.org/x/tools/gopls/internal/test/integration/template [build failed]


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: [Impeller] entitypass clip stack should pop the appropriate number of clips on restore.
Labels: P3,e: impeller,team-engine,triaged-engine

Currently when we pop a save stack, we only remove a single clip from the clip record-replay system. This was the cause of the issue worked around in https://github.com/flutter/flutter/pull/162113 .

We should already be tracking clip depth with enough granularity to know how many entries to pop. Low priority as the workaround is fairly straightforward.
Repository: flutter
Issue: Screen flickering on iOS and iPhone
Labels: platform-ios,engine,customer: vroom,c: rendering,a: production,P1,e: impeller,team-engine,triaged-engine

### Steps to reproduce

This is reported from a priority partner.

As described by the partner: "Since end of last year, the number of occurrences of a “screen flickering” issue of our iOS testers increased significantly. This problem is not reliably reproducible"

We have seen this issue on Flutter 3.19.5 and 3.22.3.

Devices that reported the mentioned issues:

iPhone 15 Pro, iOS 18.2.1
iPhone 14 Pro Max, iOS 17.4
iPhone 13 mini, iOS 18.2
iPhone 13, iOS 18.2.1

This issue seems to be independent of the configuration of our app (brand, environment) but as far as we know only happens in Release builds (as mentioned in the linked GH issues)

This problem also happens with the official AppStore releases.

Even our testers are not able to reliably reproduce the issue.


Potential related issues: 

https://github.com/flutter/flutter/issues/159184
https://github.com/flutter/flutter/issues/159061




### Expected results

No screen flickering.

### Actual results

Flickering. We have received videos of the behavior, which are shared internally.

### Code sample

N/A

### Screenshots or Video

Videos have been shared privately internally.

### Logs

N/A

### Flutter Doctor output

Will ask the partner.
Repository: vscode
Issue: Support setting user.name/user.email in the config for the built-in git extension, per user-profile
Labels: feature-request,git

<!-- ⚠️⚠️ 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. -->
Like many of us, I commit to both personal repositories and to work repositories.  However, these are in two different "personas", which need two different names/email addresses.  Currently, I've set up profiles in VSCode to reflect this, but I haven't found a way to change the settings in git to reflect this.

 - It _can_ be manually configured for each repository via `git config user.email ....`.  Unfortunately, these are all in devcontainers, so not only does it have to be done for each one, but it has to be re-done each time the container is rebuilt.
 - There are ways to conditionally configure git... unfortunately this has to be handled through separate config files, which the devcontainer extension doesn't copy (although I've submitted an issue with them)
 - It can be configured with environment variables; `GIT_AUTHOR_EMAIL`/`GIT_COMMITTER_EMAIL`/etc.  Unfortunately, the only way I've found to do this per-profile so far is the `terminal.integrated.env.<os>`/`terminal.integrated.profiles.<os>.<shell>.env` settings, which the built-in git extension (of course?) ignores.
   - Currently if I try to use this it means that commits between the UI and the CLI have mismatching authors/emails!  Fun times.
   - Setting this as an environment variable on the devcontainer isn't an option, for obvious reasons. 

So, I'd prefer some way to be able to set this per-profile to support working in different personas this way.
Repository: terminal
Issue: After trying out Quake mode, running `wt -w 0 sp -s 0.4 pwsh` from any non-quake mode WT terminal always opens a new terminal window
Labels: Issue-Bug,Needs-Tag-Fix

### Windows Terminal version

1.22.3232.0

### Windows build number

10.0.26100.0

### Other Software

_No response_

### Steps to reproduce

1. Run `wt --window _quake` to try out the Quake mode
2. Close all Quake mode window, then open a new regular WT window, run `wt -w 0 sp -s 0.4 pwsh` within it

### Expected Behavior

The command `wt -w 0 sp -s 0.4 pwsh` should split the current window and run PowerShell in the new pane

### Actual Behavior

After trying out the Quake mode, running `wt -w 0 sp -s 0.4 pwsh` from WT (regular window, non-Quake mode) will always start a new window and split it over there, instead of splitting the current window.
Repository: pytorch
Issue: Enable `sm_89` support for relevant ops in PyTorch
Labels: module: build,module: cuda,triaged,module: m1

Please add sm_89 to the list of target architectures for the stable, nightly, and Docker images. While I’ve seen references indicating that sm_89 might not need explicit builds due to binary compatibility with sm_86 and sm_80, that compatibility does not hold for FP8-related features on sm_89.

For more details, see this comment: https://github.com/pytorch/ao/issues/1057#issuecomment-2613095265.

Thanks in advance!

cc: @alexsamardzic 

cc @malfet @seemethere @ptrblck @msaroufim @eqy
Repository: vscode
Issue: PreparedToolInvocation.pasteTenseMessage should take a callback
Labels: chat-tools

A find text tool should be able to say "Found 123 results" or something like that as the complete tool message
Repository: flutter
Issue: [skwasm] RuntimeError: illegal cast in `layers.dart`
Labels: waiting for customer response,in triage

### Steps to reproduce

I've recently switched to the wasm-build of DevTools and am occasionally encountering an issue where it fails to render (I need to reload the page to get it to render). I see an error in the Chrome console which looks like it's an issue in the engine, but the stacktrace locations don't correspond to the current engine locations  (attached is screenshot).

![Image](https://github.com/user-attachments/assets/baf811ee-3ffe-4af2-84c1-bfc990e9a711)

For reference, my Flutter version:

```
Flutter 3.29.0-1.0.pre.2 • channel [user-branch] • unknown source
Framework • revision 5517cc9b3b (9 days ago) • 2025-01-15 22:17:29 +0100
Engine • revision 5517cc9b3b
Tools • Dart 3.7.0 (build 3.7.0-323.0.dev) • DevTools 2.42.0
```

### Expected results

DevTools should render with wasm build

### Actual results

DevTools occasionally fails to render

### Code sample

No reliable repro


### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

[!] Flutter (Channel [user-branch], 3.29.0-1.0.pre.2, on macOS 15.2 24C101 darwin-arm64, locale en) [190ms]
    ! Flutter version 3.29.0-1.0.pre.2 on channel [user-branch] at /Users/elliottbrooks/dev/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
    ! Unknown upstream repository.
      Reinstall Flutter by following instructions at https://flutter.dev/setup.
    • Framework revision 5517cc9b3b (9 days ago), 2025-01-15 22:17:29 +0100
    • Engine revision 5517cc9b3b
    • Dart version 3.7.0 (build 3.7.0-323.0.dev)
    • DevTools version 2.42.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update
      checks and upgrades.
Repository: kubernetes
Issue: CPU starvation on worker nodes caused by the Kubelet not setting cpu.cfs_quota_us in the kubepods.slice cgroup.
Labels: sig/node,needs-triage

Any idea why the kubelet isn't setting a value for cpu.cfs_quota_us for the parent cgroup "kubepods.slice", and instead defaults to -1? This is leading to CPU starvation on the node, as burstable pods end up consuming 100% of the CPU, despite CPU reservations being configured in the kubelet’s kubeReserved and systemReserved as shown below. These reservations aren’t being enforced because the parent cgroup doesn't have CPU quota set. This is resulting in pods consuming 100% of the CPU and nothing being reserved for system processes or kubelet.

**################
Kubelet Config:
################**
kubeReserved:
  cpu: "2000m"
systemReserved:
  cpu: "2000m"

**################
CGroup "kubepods.slice" setting for cpu quota:
################**

$ cat /sys/fs/cgroup/cpu/kubepods.slice/cpu.cfs_quota_us
-1
Repository: storybook
Issue: [Bug]: runtime and iframe 404 on first load
Labels: bug,needs triage

### Describe the bug

I am trying to upgrade from storybook 8.3.5 to 8.5.1. When I upgrade and run storybook, it opens the browser and stays on the loading spinner with the errors shown in the screenshot. It corrects itself on refresh. I have tried some other suggestions from past issues like vite --force, tracking down caches and removing, and others but those do not remove the issues. This issue occurs for all versions higher than 8.3.5 for me.

<img width="1269" alt="Image" src="https://github.com/user-attachments/assets/53df2de7-f1bb-4160-99f8-97081808ac08" />

### Reproduction link

no

### Reproduction steps

1. upgrade to any storybook version higher than 8.3.5
2. run storybook dev
3. see no other errors except those shown in the console and loading spinner.

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.7
    CPU: (12) arm64 Apple M3 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 23.5.0 - /opt/homebrew/bin/node
    npm: 10.9.2 - /opt/homebrew/bin/npm <----- active
    pnpm: 9.12.1 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 129.0.6668.90
    Safari: 17.6
  npmPackages:
    @storybook/addon-a11y: 8.4.7 => 8.4.7 
    @storybook/addon-essentials: 8.4.7 => 8.4.7 
    @storybook/addon-interactions: 8.4.7 => 8.4.7 
    @storybook/addon-links: 8.4.7 => 8.4.7 
    @storybook/addon-onboarding: 8.4.7 => 8.4.7 
    @storybook/blocks: 8.4.7 => 8.4.7 
    @storybook/builder-vite: 8.4.7 => 8.4.7 
    @storybook/react: 8.4.7 => 8.4.7 
    @storybook/react-vite: 8.4.7 => 8.4.7 
    @storybook/test: 8.4.7 => 8.4.7 
    @storybook/test-runner: 0.19.1 => 0.19.1 
    chromatic: 11.10.4 => 11.10.4 
    storybook: 8.4.7 => 8.4.7 
    storybook-addon-tailwind-autodocs: 1.0.8 => 1.0.8 
    storybook-react-i18next: 3.1.7 => 3.1.7 
```

### Additional context

_No response_
Repository: node
Issue: A way to forget a variable in Node.js REPL?
Labels: feature request

### What is the problem this feature will solve?

It's just a tiny improvement for the REPL.

Take the following sample of REPL usage when a typo happened.

```sh
> const { DatabaseSync } = require('node:sqliite');
Uncaught Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:sqliite
    at Function._load (node:internal/modules/cjs/loader:1068:13)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
    at Module.require (node:internal/modules/cjs/loader:1340:12)
    at require (node:internal/modules/helpers:141:16) {
  code: 'ERR_UNKNOWN_BUILTIN_MODULE'
}
> const { DatabaseSync } = require('node:sqlite');
Uncaught SyntaxError: Identifier 'DatabaseSync' has already been declared
```

Note that due to a typo, I can't use require again to import `DatabaseSync`. Instead, I usually close and open the reply.

### What is the feature you are proposing to solve the problem?

Implementing a way to forget a variable would solve it.

The Erlang programming language doesn't allow reassignment, so a situation like the one described above might occur. To solve this, they have a utility function for forgetting a variable.

In the example below we can reuse `Message` after calling `f(Message)`.

![Image](https://github.com/user-attachments/assets/5965da19-4ea9-485d-982c-5ab6fac18e16)

NOTE: That would be good. However, I don't know of a way to do this in the current REPL. Please let me know if there's one.

### What alternatives have you considered?

Using `let` when importing in REPL :)
Repository: puppeteer
Issue: [Bug]: remove deprecated clickCount attribute
Labels: bug,confirmed,P3

### Minimal, reproducible example

```TypeScript
import puppeteer from 'puppeteer';

const puppeteerOptions = {
  headless: false,
  protocol: 'webDriverBiDi',
}

const browser = await puppeteer.launch(puppeteerOptions);

const page = await browser.newPage();

await page.goto('data:text/html,<label id=lbl ondblclick="output.innerText += \'dblclick\'">click me</label><div id="output"></div>')

await page.click('#lbl',  { clickCount: 2 });

console.log(await page.evaluate(() => output.innerText));

await browser.close();
```

### Background

I've been trying to get vue's tests running using WebDriver BiDi

### Expectation

The code above should print "dblclick" 

### Reality

It prints nothing but does print "dblclick" if I'm not using  `protocol: 'webDriverBiDi',`

### Puppeteer configuration file (if used)

```TypeScript

```

### Puppeteer version

24.1.1

### Node version

23.5.0

### Package manager

yarn

### Package manager version

1.22.22

### Operating system

macOS
Repository: vscode
Issue: Paste is extremely laggy
Labels: info-needed


Type: <b>Bug</b>

Paste is extremely laggy. Fix it.
Add a test please, is like one of the most used operation 

VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Xeon(R) W-2133 CPU @ 3.60GHz (12 x 3600)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|63.59GB (36.26GB free)|
|Process Argv|--crash-reporter-id c7111d2b-8353-4f60-bf14-9bf1bbea5cf8|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (16)</summary>

Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|13.5.0
markdown-mermaid|bie|1.27.0
vscode-eslint|dba|3.0.10
vscode-playwright-test-snippets|dee|0.0.3
xml|Dot|2.5.1
gitlens|eam|16.2.1
code-runner|for|0.12.2
copilot|Git|1.259.0
copilot-chat|Git|0.23.2
prettify-json|moh|0.0.3
powershell|ms-|2025.0.0
vsliveshare|ms-|1.0.5948
vscode-yaml|red|1.15.0
vscode-playwright-test-runner|sak|1.4.1
code-spell-checker|str|4.0.34
markdown-all-in-one|yzh|3.6.2


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->
Repository: neovim
Issue: Allow non-ASCII `iskeyword` values
Labels: needs:vim-patch

### Problem

The `iskeyword` option currently accepts only ASCII characters. But languages like Agda, Pie use non-ASCII characters in identifier names.

### Expected behavior

Allow non-ASCII `iskeyword` values.
Repository: godot
Issue: Unable to reload project with save after changing resource script
Labels: bug,topic:editor

### Tested versions

4.3 stable, 4.4 beta1

### System information

Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility) - Radeon RX 560 Series (Advanced Micro Devices, Inc.; 31.0.14001.45012) - Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 Threads)

### Issue description

After changing the custom resource script, it is impossible to reload the project, saving it, the pop-up selection window appears even after selection.

https://github.com/user-attachments/assets/5c17a701-a523-4b5a-9619-1874d1f71f2b

### Steps to reproduce

1. Open MRP
2. Open the resource `new_resource.tres` and open its script
3. Edit the resource script
4. Reload the project using `Project->Reload Current Project`
5. The pop-up window will appear again.

### Minimal reproduction project (MRP)

[bug.zip](https://github.com/user-attachments/files/18540803/bug.zip)
Repository: PowerToys
Issue: Power Toys conficts with PowerPoint or Adobe Creative Cloud in Win11?
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

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

### ✔️ Expected Behavior

I was using ordinary apps in Windows and didn't anticipate the glitch or conflict with Power Toys.

### ❌ Actual Behavior

Displays blacked out and flickered before restoring without the previous monitor settings. PowerToys advised me to upload the log. There was also an error message from Adobe Cloud. 

### Other Software

I was using PowerPoint. I previously had Adobe Illustrator open but had closed it. I was creating an image.
Repository: transformers
Issue: Request to add Co-DETR
Labels: New model

### Model description

> A collaborative hybrid assignments training scheme, namely **Co-DETR**, learns more efficient and effective DETR-based detectors from versatile label assignment manners. This new training scheme can easily enhance the encoder’s learning ability in end-to-end detectors by training the multiple parallel auxiliary heads supervised by one-to-many label assignments such as ATSS and Faster RCNN. In addition, we conduct extra customized positive queries by extracting the positive coordinates from these auxiliary heads to improve the training efficiency of positive samples in the decoder. In inference, these auxiliary heads are discarded and thus our method introduces no additional parameters and computational cost to the original detector while requiring no hand-crafted non-maximum suppression (NMS).

Quote from their paper: https://arxiv.org/pdf/2211.12860

SotA on **Object Detection on COCO test-dev**: https://paperswithcode.com/sota/object-detection-on-coco

### Open source status

- [x] The model implementation is available
- [x] The model weights are available

### Provide useful links for the implementation

Repository & Weight Links: https://github.com/Sense-X/Co-DETR
MMDet Implementation: https://github.com/open-mmlab/mmdetection/tree/main/projects/CO-DETR

Author: Zhuofan Zong https://github.com/TempleX98
Repository: flutter
Issue: Android tests failing to build because ninja cannot be found
Labels: P2,team: presubmit flakes,c: flake,team-android,triaged-android,fyi-infra


Linux_android_emu flutter_driver_android_test
```
Execution failed for task ':app:configureCMakeDebug[arm64-v8a]'.
> [CXX1416] Could not find Ninja on PATH or in SDK CMake bin folders.
```

Examples: 
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android_emu%20flutter_driver_android_test/2724/overview
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android_emu%20flutter_driver_android_test/2734/overview
Repository: flutter
Issue: Investigate spotlight running on chromium macOS VMs
Labels: team-infra

This may be causing https://github.com/flutter/flutter/issues/157636
Repository: kubernetes
Issue: [CLE] Randomize lease candidate ping order and parallelize
Labels: sig/api-machinery,triage/accepted

In the leader election controller: https://github.com/kubernetes/kubernetes/blob/master/pkg/controlplane/controller/leaderelection/leaderelection_controller.go#L267-L293, candidates are iterated through sequentially and `LeaseCandidates.Update()` is a blocking operation that is also called sequentially. This can lead to cases where certain candidates do not have enough time to respond. We should parallelize this entire operation and iterate through the list in a random order to ensure every candidate has a fair chance of responding.

/cc @Henrywu573
/triage accepted
/sig api-machinery