sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Remove redundant codecs on iOS.
Labels: c: proposal,P2,team-engine,triaged-engine,slimpeller

The Flutter Engine ships codecs for commonly supported formats. When the application requests image decoding from a file, these built-in codecs are queried. If these codecs are unable to decompress the image, the engine asks the platform codecs to try. In this way, the application gets a base set of codecs they can depend on while also getting support for newer codecs available on the platform.

However, the [codecs supported on the platform](https://gist.github.com/chinmaygarde/ae5aa5eb591d1b6fa91b2d3c718dc190) are usually a superset of those [supported by the Flutter Engine](https://gist.github.com/chinmaygarde/7b02ce99e6243f8c378468515e4f2482).

Removing all built-in codecs from the Flutter Engine is possible with minimal impact to end users. However, codecs like WebP were added to iOS in iOS 14 while Flutter supports versions as old as iOS 12. Other codecs like PNG and JPEG have always been available on iOS but there might be differences in the way the engine codecs and the platform codecs work.

We should consider removing these codecs to save on binary size.
Repository: flutter
Issue: Remove the --enable-impeller run flag and FLTEnableImpeller plist key on iOS.
Labels: P2,team-engine,triaged-engine,slimpeller

Impeller has been the default on iOS since 3.13. As we prep to remove the fallback, we should [remove the flag and plist entries](https://docs.flutter.dev/perf/impeller#ios) and/or warn about their pending removal.
Repository: flutter
Issue: Find and list the implicit uses of the Skia software renderer in the Flutter Engine.
Labels: P2,team-engine,triaged-engine,slimpeller
Repository: node
Issue: Proposal: Alternative to enabling Corepack by default
Labels: feature request,experimental

This is a sketch of a proposal, so please don’t pepper me with questions about how it would work; I don’t know. It’s an early idea that I want to suggest to see if there’s interest.

So today, when you run `corepack enable`, a file named `yarn` is written to a path like `/usr/local/bin/yarn`. This is a `#!/usr/bin/env node` script that tells Corepack to run Yarn. Presumably https://github.com/nodejs/node/pull/51886 will cause this file to exist upon Node installation, without the need to run `corepack enable` to create it. All well and good.

What if instead, we create a new `#!/usr/bin/env node` script that lives at the same path `/usr/local/bin/yarn`. This file would exist upon Node installation, and in this Node installation there’s no bundled Corepack (bear with me). When run, this new `yarn` script would do the following:

1. Prompt the user “Do you want to download and install Yarn?” and if yes:
2. `npm install --global corepack`
3. `corepack enable yarn`
4. Runs Yarn with the arguments originally passed to the script

From the user’s perspective, this is the same DX as if https://github.com/nodejs/node/pull/51886 lands; though it takes slightly longer, because instead of downloading and installing just Yarn it’s downloading and installing both Corepack and Yarn.

Besides shrinking the Node bundle size slightly, the benefit of doing this is to get the Node project off the hook for the maintenance burden and security burden of Corepack. We would be responsible for this handful-of-lines download-and-install script, but that’s it. Corepack could be gifted to the Yarn org and they could become responsible for it.

This also becomes a pattern that we could use for any other CLI tools we may want to provide easy access to, but not bundle, in the future—even npm (downloaded and installed directly, not via Corepack). I don’t know what we might consider for such treatment other than Yarn and pnpm, but the capability would be there.

@nodejs/tsc @nodejs/corepack @nodejs/npm @nodejs/package-maintenance
Repository: flutter
Issue: Allow visualizing Flutter Engine binary sizes on iOS.
Labels: P2,team-engine,triaged-engine,slimpeller

There needs to be a way to attribute binary size contributions of various translation units and folders.

[go/flutter-engine-size-viz](https://goto.google.com/flutter-engine-size-viz) has some prior art on using Bloaty and other tools.
Repository: flutter
Issue: Generate Flutter engine binary size visualizations for iOS on CI.
Labels: P2,team-engine,triaged-engine,slimpeller

Depends on https://github.com/flutter/flutter/issues/144441.

This is similar to the binary size visualizations for Android which [are available here](https://storage.googleapis.com/flutter_infra_release/flutter/12def739b1f63ccaf5b859714d9f552e9e6fe348/android-arm64-release/sizes/index.html).
Repository: rust
Issue: Compiler indefinitely takes resources when HRTB is used in conjunction with lifetime in GAT
Labels: A-lifetimes,A-trait-system,T-compiler,I-compilemem,C-bug,I-hang,fixed-by-next-solver,A-GATs,A-higher-ranked

<!--
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
pub trait A {
    type Item<'a>
    where
        Self: 'a;

    fn run(&mut self) -> Self::Item<'_>;
}

#[derive(Debug)]
pub struct S<F>(F);

impl<F> A for S<F>
where
    for<'a> F: FnMut(&Self::Item<'a>),
{
    type Item<'a> = i32
    where
        Self: 'a;

    fn run(&mut self) -> Self::Item<'_> {
        todo!()
    }
}

```

I expected to see this happen: the code should compile or return a compilation error in a short time.

Instead, this happened: the compiler start working and taking resources, apparently indefinitely.

Notice that removing the bound for `F` stops the issue to occur.

---

EDIT: the code triggers infinite recursion, the bound should be `FnMut(&I::Item<'a>)`. As suggested by others, the issue of infinite recursion is managed by the next solver (using `-Znext-solver`), and thanks to that is also easy to spot the problem in the code.

### 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`:
Stable:
```
rustc 1.76.0 (07dca489a 2024-02-04)
binary: rustc
commit-hash: 07dca489ac2d933c78d3c5158e3f43beefeb02ce
commit-date: 2024-02-04
host: x86_64-unknown-linux-gnu
release: 1.76.0
LLVM version: 17.0.6
```

Nightly:
```
rustc 1.78.0-nightly (c475e2303 2024-02-28)
binary: rustc
commit-hash: c475e2303b551d726307c646181e0677af1e0069
commit-date: 2024-02-28
host: x86_64-unknown-linux-gnu
release: 1.78.0-nightly
LLVM version: 18.1.0
```

The issue occurs both on stable and nightly.
Repository: pytorch
Issue: DISABLED test_subgraphs_with_parameters_device_cuda_dynamic_True (__main__.CondTests)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22inductor%2Ftest_control_flow.py%3A%3ACondTests%3A%3Atest_subgraphs_with_parameters_device_cuda_dynamic_True%22%5D)).


Newly added test fails on rocm:
https://github.com/pytorch/pytorch/pull/120777#issuecomment-1972125294

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: kubernetes
Issue: Pod Crashloop backoff requeue issues
Labels: kind/bug,sig/node,priority/important-longterm,triage/accepted

When stepping through the pod crashloop backoff implementation, I noticed a few issues:

1. Backoff errors are unsuccessfully suppressed:
  - This code is non-functional, since there will always be a non-error result present (`ConfigPodSandbox`) with a nil error: https://github.com/kubernetes/kubernetes/blob/5cf4fbe524ca1479607a4880949a032064556f76/pkg/kubelet/kubelet.go#L1964-L1971
2. The propogated backoff error means that the pod worker always immediately requeues the pod: https://github.com/kubernetes/kubernetes/blob/5cf4fbe524ca1479607a4880949a032064556f76/pkg/kubelet/pod_workers.go#L1495-L1497
  - If the backoff error were suppressed, then the default 1m sync frequency would be used, which would cause very long initial backoffs.

The result of these issues are:
1. Log spam: `E0301 01:06:01.286649    1869 pod_workers.go:1294] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"alpine\" with CrashLoopBackOff: \"back-off 5m0s restarting failed container=alpine pod=restarting-pod_default(ca0d5836-1435-497e-9a41-547fbcc10484)\"" pod="default/restarting-pod" podUID=ca0d5836-1435-497e-9a41-547fbcc10484` get's logged in a frequent loop
2. Kubelet does unnecessary work to reexamine pods and containers in backoff
3. (minor) the error retry period is 10s, which adds up to 10s to the backoff time

I think the ideal fix is to propagate the backoff retry time up from SyncPod [1] to the pod worker [2], so that the pod can be requeued with the exact (jittered) right amount of retry time. One option is to use a custom error type to encapsulate the backoff time, which I started working on here: https://github.com/tallclair/kubernetes/commit/5d89eb2538cc8929540476f436d4a1b92c9babee

Of course, there is very little test coverage across these code paths too.

[1]: https://github.com/kubernetes/kubernetes/blob/5cf4fbe524ca1479607a4880949a032064556f76/pkg/kubelet/kuberuntime/kuberuntime_manager.go#L1325
[2]: https://github.com/kubernetes/kubernetes/blob/5cf4fbe524ca1479607a4880949a032064556f76/pkg/kubelet/pod_workers.go#L1484

/sig node
/kind bug
Repository: vscode
Issue: Allow changing the font color of an editor widget
Labels: feature-request,editor-theming

In a few places, we use a CSS rule like this where we want to set the text color of a CodeEditorWidget, e.g. to follow `input.foreground` instead of `editor.foreground`. I added another one in https://github.com/microsoft/vscode/pull/206564. This is a hack, it would be nice to have a better way to do this.

https://github.com/microsoft/vscode/blob/23888827cc3047a9a9ecd8608b3a04accaa3aca6/src/vs/workbench/contrib/codeEditor/browser/suggestEnabledInput/suggestEnabledInput.css#L13-L15
Repository: rust
Issue: error[E0308]: mismatched types `expected fn pointer, found fn item`
Labels: P-medium,T-compiler,regression-from-stable-to-stable,C-bug,T-types

### Code

I tried this code:

```rust
pub fn foo(_: &i32, _: &i32) {}
pub const _: [for<'r> fn(&'r i32, &'r i32); 2] = [foo, foo];
```

I expected to see this happen: *compile successfully*

Instead, this happened:

```sh
error[E0308]: mismatched types
 --> src/lib.rs:3:56
  |
3 | pub const _: [for<'r> fn(&'r i32, &'r i32); 2] = [foo, foo];
  |                                                        ^^^ expected fn pointer, found fn item
  |
  = note: expected fn pointer `for<'r> fn(&'r _, &'r _)`
                found fn item `for<'a, 'b> fn(&'a _, &'b _) {foo}`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `fnitem` (lib) due to 1 previous error
```

### Version it worked on

It most recently worked on: `nightly-2024-02-29`

### Version with regression

searched nightlies: from nightly-2024-02-28 to nightly-2024-03-01
regressed nightly: nightly-2024-03-01
searched commit range: https://github.com/rust-lang/rust/compare/c475e2303b551d726307c646181e0677af1e0069...878c8a2a62d49ca5c454547ad67290a1df746cb5
regressed commit: https://github.com/rust-lang/rust/commit/878c8a2a62d49ca5c454547ad67290a1df746cb5 cc @spastorino

<details>
<summary>bisected with <a href='https://github.com/rust-lang/cargo-bisect-rustc'>cargo-bisect-rustc</a> v0.6.8</summary>

Host triple: x86_64-unknown-linux-gnu
Reproduce with:
```bash
cargo bisect-rustc --start=2024-02-28 --end=2024-03-01
```
</details>

@rustbot modify labels: +regression-from-stable-to-nightly  -regression-untriaged
Repository: vscode
Issue: API to show a learnMore button for `forceNewSession`
Labels: feature-request,api,authentication

```
	export interface AuthenticationForceNewSessionOptions {
		learnMore?: Uri;
	}
```

So it can show up in the auth prompt.
Repository: vscode
Issue: Git - activeRepositoryBranchName in window.title is not refreshed consistently
Labels: bug,git

<!-- ⚠️⚠️ 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
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.87.0
- OS Version: Windows 11 Pro 23H2 22631.3155
- Git version: 2.44.0.windows.1

My window.title is `${dirty}${activeEditorShort}${separator}${rootName}${separator}${profileName}${separator}${activeRepositoryName}/${activeRepositoryBranchName}`

Steps to Reproduce:

1. Open a file that is source controlled
2. In the integrated terminal, execute `git switch <branch1>`
3. In the integrated terminal, execute `git switch <branch2>`
4. Repeat 2 and 3 until the problem manifests (resizing/maximizing/restoring the window and then switching may be related?)

![image](https://github.com/microsoft/vscode/assets/519875/4e492fe0-4bca-4d89-9155-3cc442527bd3)
Repository: flutter
Issue: [Web][CanvasKit] Web font rendering appears semi transparent, resulting in blurry text
Labels: engine,a: typography,platform-web,e: web_canvaskit,has reproducible steps,P2,team-web,triaged-web,found in release: 3.19,found in release: 3.20

### Steps to reproduce

Use last flutter sdk create web app and use chinese or open web site "https://flutter-gallery-archive.web.app/#/demo/2d-transformations" 
![微信截图_20240301132714](https://github.com/flutter/flutter/assets/5417624/7c6e7d3f-2112-4c43-95fc-64f93661e4ac)
![微信截图_20240301132829](https://github.com/flutter/flutter/assets/5417624/4fe684de-71f9-4ff7-a3fd-223e1215bb0f)


### Expected results

![image](https://github.com/flutter/flutter/assets/5417624/c449cd04-4bba-408c-b14f-3d499b4b3073)


### Actual results

![image](https://github.com/flutter/flutter/assets/5417624/aa1c926e-2c07-49a6-b6e6-370dfcdc6cfe)


### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.19.2, on Microsoft Windows [版本 10.0.22631.3155], locale zh-CN)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.8.3)
[√] Android Studio (version 2021.1)
[√] VS Code (version 1.87.0)
[√] Connected device (3 available)
[√] Network resources
Repository: ollama
Issue: Starting Ollama a second time on Windows 11 creates another instance
Labels: bug,windows

![image](https://github.com/ollama/ollama/assets/251292/f39e33c2-2789-4cf8-97b0-7cc5a0eb7420)
Repository: transformers
Issue: MPNet doesn't have an implemented LMHead subclass
Labels: Feature request

### Feature request

The code of mpnet needs a proper implementation of LMHead class to adapt to Language Generation Tasks

### Motivation

We want to perform some experiments on the MPNet style inference on language generation tasks. On going through the codebase, there is a standby class inherited from `torch.nn.module`, which means there is no proper implementation of LMHead on this model

### Your contribution

I'm eager to contribute to this issue by submitting a PR. This work would be super relevant for us to extend our experiments to MPNet as well for our research projects.
Repository: pytorch
Issue: TORCH_CHECK level changes in flatten
Labels: module: error checking,triaged,module: viewing and reshaping

### 🚀 The feature, motivation and pitch

Per discussion https://github.com/pytorch/pytorch/pull/120894,
It's good to change the TORCH_CHECK level (IndexError or ValueError) consistently for flatten APIs.

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet
Repository: tauri
Issue: IOS DEV: Error from getpwuid_r: 0 [bug] 
Labels: type: bug,status: needs triage,platform: iOS

### Describe the bug

When I run pnpm tauri ios dev I get an error:
```bash
Deploying app to device...
com.kitty.kitty: 79519
        Info Watching /Users/hezhaozhao/myself/kitty/src-tauri for changes...
Error from getpwuid_r: 0 (Undefined error: 0)
Filtering the log data using "subsystem == "com.kitty.kitty""
```

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.3.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 18.14.0
    - pnpm: 8.12.0
    - npm: 9.3.1

[-] Packages
    - tauri [RUST]: 2.0.0-beta.6
    - tauri-build [RUST]: 2.0.0-beta.4
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.0
    - @tauri-apps/api [NPM]: 2.0.0-beta.0
    - @tauri-apps/cli [NPM]: 2.0.0-beta.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite

[-] iOS
    - Developer Teams: None
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: deno
Issue: make the lsp report `deno doc --lint` errors
Labels: suggestion,lsp

That would make it easier for the user to notice missing docs
Repository: vscode
Issue: Outline view: Auto collapse previous method tree when 'Follow Cursor' is checked.
Labels: feature-request,outline

<!-- ⚠️⚠️ 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. -->

Regarding 'Outline view' When `Follow Cursor` and `alwaysCollapse` are checked. I'd like only the active method tree to be expanded where my cursor is. In the video below, it expands the methods where I put the cursor but do not close the previous one. This becomes messy as you can see. There can be a new setting called: `expandActive`

![screenshot 2024-03-01 at 13 53 26@2x](https://github.com/microsoft/vscode/assets/7106086/db400cc4-f376-4321-98ee-9a4005904034)

![screenshot 2024-03-01 at 13 53 49@2x](https://github.com/microsoft/vscode/assets/7106086/f5d659f5-b876-40b1-b56e-c3947155760b)




https://github.com/microsoft/vscode/assets/7106086/c3279590-0f59-43ab-b25a-ec6ecfbadfa0
Repository: PowerToys
Issue: Switching windows in the same zone doens't work anymore 
Labels: Issue-Bug,Product-FancyZones,Needs-Repro,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Snap multiple windows to the same zone.
Try to switch them with {win}+{PgUp/Down} keys

### ✔️ Expected Behavior

Windows are switching

### ❌ Actual Behavior

Nothing happens (reassigning switching shortcut to other key combination won't help)

### Other Software

Windows 11
Version 22H2 22621.3155
Repository: opencv
Issue: telecentric calibration
Labels: feature,category: calib3d

### Describe the feature and motivation

dear all
please correct me if I am wrong: a telecentric lens model seems not to be covered in opencv calibration (as it is in Halcon mvTech for instance). I think it would be beneficial to implement it and add it. 


### Additional context

Please an opinion about it: in the meantime while it is not available, do you think it would be appropriate to get a telecentric model as a limit ( f-> infinite) just applying the projective lens pin hole model with a fixed "very high" focal (not recalculated) and then obtain the telecentric magnification m=f/z ? where z would be calculated by the calibration as a hopefully relatively high value as well? so basically the telecentric lens would be somehow simulated as a telephoto ? thank you very much in advance for your feedback
Repository: rust
Issue: Improve MSVC debug info for f16 and f128
Labels: A-debuginfo,E-hard,T-compiler,O-windows-msvc,WG-debugging,F-f16_and_f128,E-needs-investigation

The code at https://github.com/rust-lang/rust/blob/6cbf0926d54c80ea6d15df333be9281f65bbeb36/compiler/rustc_codegen_llvm/src/debuginfo/metadata.rs#L696-L707 produces a debug representation for MSVC, which could be improved. Quoting from @MaulingMonkey in https://github.com/rust-lang/rust/pull/114607/files#r1454683264:

> Not sure if proper support is possible here without bugging Microsoft. Even if it is possible, Microsoft hasn't bothered for their own SDK types (e.g. `_FLOAT128` can be found in the windows SDK, but it's just a struct around a couple of u64s and has no useful debug visualizers.)
> 
> If it _were_ possible:
> 
>     * Emit debug info for a `u16`/`u128`-wrapping structure (I'm fuzzy on the details here, I've only wrapped existing emitted types rather than emitting my own.  Merely defining an unused std type might not be enough as such types will get culled IME?)
> 
>     * Write/extend a `*.natvis` file (probably [rust/src/etc/natvis/intrinsics.natvis](https://github.com/rust-lang/rust/blob/6bf600bc98879bf1bf2ab0f3b3b37c965f5bdff6/src/etc/natvis/intrinsic.natvis)?) that unpacks the bits and reconstitutes them as an approximate double or float in it's `<DisplayString>`.
>       
>       * How do you transmute/type-pun from `u64` → `f64` in the subset of C++ allowed by the debugger (no pointer-to-temporary shenannigans)?  _Maybe_ abuse a union somehow...?
>       * See [`natvis-pdbs` Recommended Reading](https://crates.io/crates/natvis-pdbs#recommended-reading)
>       * If you added a new `*.nativs` file for some reason, make sure it's referenced properly (see e.g. [rust/src/bootstrap/src/core/build_steps/dist.rs](https://github.com/rust-lang/rust/blob/master/src/bootstrap/src/core/build_steps/dist.rs#L535-L538)
>       * Consider unit tests like [tests/debuginfo/pretty-std-collections-hash.rs](https://github.com/rust-lang/rust/blob/6bf600bc98879bf1bf2ab0f3b3b37c965f5bdff6/tests/debuginfo/pretty-std-collections-hash.rs#L1)
>
> (It's [possible to call `_CrtCheckMemory()` from a watch window](https://ofekshilon.com/2016/11/01/checking-memory-corruption-from-the-debugger-in-2016/). I forget if this works in a `*.natvis` visualizer. If so, you could theoretically author `F128toApproxF64(high: u64, low: u64)` and stuff it in a DLL? Or better yet, let someone more foolish take the time to go down _that_ rabbit hole and shave that yak...)

@rustbot label +F-f16_and_f128