sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking issue for release notes of #133073: `--nocapture` doesn't follow common CLI conventions, making it a stumbling block to people debugging failures
Labels: relnotes,A-libtest,T-testing-devex,relnotes-tracking-issue


This issue tracks the release notes text for #133073.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] 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
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [`--nocapture` doesn't follow common CLI conventions, making it a stumbling block to people debugging failures](https://github.com/rust-lang/rust/issues/133073)
````

> [!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 -- origin issue/PR authors and assignees for starting to draft text
Repository: go
Issue: cmd/cgo/internal/testplugin: TestMethod2 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/cgo/internal/testplugin" && test == "TestMethod2"
```

Issue created automatically to collect these failures.

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

    === RUN   TestMethod2
    ( GOPATH=$TMPDIR PWD=$TMPDIR/src/testplugin LD_LIBRARY_PATH=$TMPDIR/src/testplugin /Users/swarming/.swarming/w/ir/x/w/goroot/bin/go build -gcflags '' -buildmode=plugin -o method2.so ./method2/plugin.go )
        plugin_test.go:332: /Users/swarming/.swarming/w/ir/x/w/goroot/bin/go build -gcflags  -buildmode=plugin -o method2.so ./method2/plugin.go: exit status 1
            # command-line-arguments
            ../../../../w/goroot/pkg/tool/darwin_amd64/link: running clang failed: exit status 1
            /usr/bin/clang -arch x86_64 -m64 -Wl,-headerpad,1144 -Wl,-flat_namespace -Wl,-bind_at_load -dynamiclib -o a.out.so -Qunused-arguments ../../../go-link-3320883559/go.o ../../../go-link-3320883559/000000.o ../../../go-link-3320883559/000001.o ../../../go-link-3320883559/000002.o ../../../go-link-3320883559/000003.o ../../../go-link-3320883559/000004.o ../../../go-link-3320883559/000005.o ../../../go-link-3320883559/000006.o ../../../go-link-3320883559/000007.o ../../../go-link-3320883559/000008.o ../../../go-link-3320883559/000009.o -O2 -g -lpthread
            ld: warning: -bind_at_load is deprecated on macOS
            0  0x1001acc3b  __assert_rtn + 64
            1  0x1000f146c  ld::AliasAtom::targetOfAliasAtom() const + 236
            2  0x1000cb07f  ld::setAtomDebugFileInfo(ld::Atom const*, mach_o::DebugNoteFileInfo const*) + 79
            3  0x1000aa6ff  ld::AtomPlacement::forEachAtom(void (ld::Atom const*, bool&) block_pointer) const + 287
            4  0x1000c75ef  ld::InputFiles::SliceParser::parseObjectFile(mach_o::Header const*) const + 27951
            5  0x1000d6c91  ld::InputFiles::parseAllFiles(void (ld::AtomFile const*) block_pointer)::$_7::operator()(unsigned long, ld::FileInfo const&) const + 657
            6  0x7ff8047d1066  _dispatch_client_callout2 + 8
            7  0x7ff8047e418f  _dispatch_apply_invoke_and_wait + 213
            8  0x7ff8047e3692  _dispatch_apply_with_attr_f + 1207
            9  0x7ff8047e3847  dispatch_apply + 45
            10  0x1001736b2  ld::AtomFileConsolidator::parseFiles(bool) + 370
            11  0x1000f8597  main + 12471
            ld: Assertion failed: (targetIndex < atoms.size()), function directTargetNoFollow, file Fixup.cpp, line 374.
            clang: error: linker command failed with exit code 1 (use -v to see invocation)
            
    --- FAIL: TestMethod2 (1.10s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: `dev/bots/analyze_snippet_code.dart` does not allow engine to override `analysis_options.yaml`
Labels: engine,team-infra,P2,c: tech-debt,monorepo

See https://github.com/flutter/flutter/blob/29d04353558aca228c52c0b692bf25a8020c0934/dev/bots/analyze_snippet_code.dart#L998-L1001

In https://github.com/flutter/engine/pull/53223, we made an intentional decision to no longer require `always_specify_types`, and indeed that change is still in effect in the [merged monorepo](https://github.com/flutter/flutter/blob/29d04353558aca228c52c0b692bf25a8020c0934/engine/src/flutter/analysis_options.yaml#L36). However, there are scripts that assume certain properties that live outside the engine.

I had to undo style suggestions recommended by @jtmcdole (https://github.com/flutter/flutter/pull/160798#discussion_r1896860808) as a result.
Repository: yt-dlp
Issue: [bandcamp] Support user-purchased Bandcamp albums
Labels: account-needed,site-enhancement

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a site-specific feature
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [ ] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required

### Region

USA

### Example URLs

N/A

### Provide a description that is worded well enough to be understood

Currently yt-dlp only supports downloading MP3 of albums which are not free, even if the album has been purchased by the user and the login cookies are supplied (see examples below). It would be nice to support lossless downloading of purchased albums.

Side note: its seems like yt-dlp prefers to download the 128 kbps mp3 stream over the v0 stream (which ends up being about twice the filesize), which I believe is a separate bug.

### Provide verbose output that clearly demonstrates the problem

- [X] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [X] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [X] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell
yt-dlp https://cadeparker.bandcamp.com/track/ghettotech-forever -F                                   
[Bandcamp] Extracting URL: https://cadeparker.bandcamp.com/track/ghettotech-forever
[Bandcamp] ghettotech-forever: Downloading webpage
[info] Available formats for 1180292997:
ID      EXT RESOLUTION │  FILESIZE  TBR PROTO │ VCODEC     ACODEC  ABR
──────────────────────────────────────────────────────────────────────
mp3-128 mp3 audio only │ ≈12.00MiB 128k https │ audio only mp3    128k


yt-dlp https://cadeparker.bandcamp.com/track/ghettotech-forever -F --cookies-from-browser firefox
[Bandcamp] Extracting URL: https://cadeparker.bandcamp.com/track/ghettotech-forever
[Bandcamp] ghettotech-forever: Downloading webpage
Extracting cookies from firefox
Extracted ____ cookies from firefox
[info] Available formats for 1180292997:
ID      EXT RESOLUTION │  FILESIZE  TBR PROTO │ VCODEC     ACODEC  ABR
──────────────────────────────────────────────────────────────────────
mp3-v0  mp3 audio only │                https │ audio only mp3
mp3-128 mp3 audio only │ ≈12.00MiB 128k https │ audio only mp3    128k
```
Repository: rust
Issue: strange borrowing suggestion
Labels: A-diagnostics,A-borrow-checker,T-compiler

Rustc suggests borrowing of a function's return type when there is a trait not implemented error for the function's parameters.

Not only does the borrow not help, a dereferencing is required instead, but it is suggested for the return type, which is not where the problem is at all.

Consider the following program:

```Rust
#[derive(Clone, Copy)]
struct Hello;

trait Tr: Clone + Copy {}
impl Tr for Hello {}

fn foo<T: Tr>(_v: T, _w: T) {}

fn main() {
    let hellos = [Hello; 3];
    for hi in hellos.iter() {
        foo(hi, hi);
    }
}
```

On latest nightly `1.85.0-nightly (2024-12-25 7c002ff9a70cb84fd1a9)` (same as on stable and beta):

```
error[E0277]: the trait bound `&Hello: Tr` is not satisfied
  --> src/main.rs:14:9
   |
14 |         foo(hi, hi);
   |         ^^^ the trait `Tr` is not implemented for `&Hello`
   |
note: required by a bound in `foo`
  --> src/main.rs:7:11
   |
7  | fn foo<T: Tr>(_v: T, _w: T) {}
   |           ^^ required by this bound in `foo`
help: consider borrowing here
   |
14 |         &foo(hi, hi);
   |         +

error[E0277]: the trait bound `&Hello: Tr` is not satisfied
  --> src/main.rs:15:13
   |
15 |         bar(hi);
   |         --- ^^ the trait `Tr` is not implemented for `&Hello`
   |         |
   |         required by a bound introduced by this call
   |
   = help: the trait `Tr` is implemented for `Hello`
note: required by a bound in `bar`
  --> src/main.rs:9:11
   |
9  | fn bar<T: Tr>(_v: T) {}
   |           ^^ required by this bound in `bar`
```

The example shows that if there is one parameter, a borrow is not suggested. It happens only if there is two parameters.

Related (but not the same): #132041
Repository: flutter
Issue: SearchAnchor.bar listener does not fire open/close events
Labels: framework,f: material design,has reproducible steps,P2,team-design,triaged-design,found in release: 3.27,found in release: 3.28

### Steps to reproduce

1- Create a SearchAnchor.bar() widget
2- Add a listener to the `SearchController`
```dart
_searchController.addListener(() {
  if (_searchController.isOpen) {
    debugPrint('SearchAnchor.bar() is open.');
  } else {
    debugPrint('SearchAnchor.bar() is closed.');
  }
});
```
3-It wont report correctly if the widget is open or not 



### Expected results

Know if the widget is open

### Actual results

The result is uncertain. It will only change to open if you type something on the bar.

### Code sample

[SearchError.zip](https://github.com/user-attachments/files/18255911/SearchError.zip)


### 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

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, 3.28.0-2.0.pre.38578, on Microsoft Windows [versao 10.0.26100.2605], locale pt-BR)
[√] Windows Version (11 Home 64-bit, 24H2, 2009)
[√] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[√] Chrome - develop for the web
[X] Visual Studio - develop Windows apps
    X Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2024.1)
[√] VS Code (version 1.96.2)
[√] Connected device (3 available)
[√] Network resources

! Doctor found issues in 1 category.
```

</details>
Repository: flutter
Issue: camera_android_camerax and flutter_plugin_android_lifecycle require higher NDK version that Flutter master `flutter.ndkVersion`
Labels: platform-android,tool,a: first hour,P1,team-android,triaged-android

On Flutter master channel I added the camera plugin to a fresh app, and on Android build I got a scary-looking red "Your project is configured with Android NDK 26.3.11579264, but the following plugin(s) depend on a different Android NDK version:" error:

```
$ flutter create flutter_camera_test_app
$ cd flutter_camera_test_app
$ flutter pub add camera
$ flutter build apk
...
Your project is configured with Android NDK 26.3.11579264, but the following plugin(s) depend on a different Android NDK version:
- camera_android_camerax requires Android NDK 27.0.12077973
- flutter_plugin_android_lifecycle requires Android NDK 27.0.12077973
Fix this issue by using the highest Android NDK version (they are backward compatible).
Add the following to /Users/m/Projects/github-repro/flutter_camera_test_app/android/app/build.gradle.kts:

    android {
        ndkVersion = "27.0.12077973"
        ...
    }
...
```
The app actually builds fine.

The `flutter create` template is `ndkVersion = flutter.ndkVersion`

```
$ flutter doctor -v
[!] Flutter (Channel main, 3.28.0-2.0.pre.38578, on macOS 15.1.1 24B91 darwin-arm64, locale en-US)
    • Flutter version 3.28.0-2.0.pre.38578 on channel main at /Users/m/Projects/flutter
...
    • Framework revision 29d0435355 (5 hours ago), 2024-12-26 18:40:29 +0100
```


Tool:
1. As a developer what am I supposed to do about this error, actually follow the instructions to hardcode `ndkVersion`?  Why do we have `flutter.ndkVersion` if we immediately recommend the developer overwrite it?  I know this error was just greatly improved with https://github.com/flutter/flutter/pull/147809.
2. The app successfully built.  What are the consequences of not updating the NDK version as suggested?  Can the tool just silently do the work of swapping in the higher version, if it always "just works"? Will devs be doomed to constantly chase this hardcoded value?

Package:
1. Why is `camera_android_camerax` and `flutter_plugin_android_lifecycle` requiring higher NDK versions than what's in Flutter master? Should that be allowed? Should the package repo have lints to prevent this? Where is this version number exactly coming from, since it's not actually specified in the package (that I can see)?
Repository: PowerToys
Issue: Always On Top - Reading its config file (settings.json) way too often
Labels: Issue-Bug,Product-FancyZones,Resolution-Fix Committed,Product-Always On Top

### Microsoft PowerToys version

0.87.1

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

Always on Top

### Steps to reproduce

Enable the Always On Top feature. Monitor its activity using Process Monitor or a similar tool.

### ✔️ Expected Behavior

The tool should load its settings file once and keep its config in memory (it's tiny).

If any other PowerToy tools exhibit the same behaviour then they could also benefit from such a change.

### ❌ Actual Behavior

The program reads its `settings.json` file *every single time* window focus changes, which is very inefficient.

![Image](https://github.com/user-attachments/assets/8b19caa0-d1a1-4406-9b2b-e15476dca3d6)

In the interests of improving SSD performance and longevity, I'll be disabling this feature for now, just like I disable the Indexing service.

### Other Software

_No response_
Repository: rust
Issue: Warn on Fullwidth Exclamation Mark (U+FF01) in comment
Labels: T-rustdoc,A-lints,A-Unicode,T-compiler,C-feature-request

```rust
//! A
//！B
//! C
```

For the above Rust source code, rustdoc produces documentation containing only "A C". The line containing "B" is only a comment. The comment starts with https://www.compart.com/en/unicode/U+FF01.

I caught this in a real-world documentation PR from a Chinese contributor. See https://github.com/rust-lang/rust/pull/134241#pullrequestreview-2523541705.

In GitHub, the distinction is practically invisible.

<p align="center"><img src="https://github.com/user-attachments/assets/fefc1fb0-a20a-4bf5-afdf-72a9041a5426" width="700"></p>

In my text editor, it is more obvious.

<p align="center"><img src="https://github.com/user-attachments/assets/37c64868-9d99-42d6-b16d-cd57b8a0ffed" width="700"></p>

Would it be reasonable for rustc and/or rustdoc to have reported a lint on such code?
Repository: pytorch
Issue: [RFC] Identifying dynamic int8 symmetric vs asymmetric quantization of activation/input in Inductor-CPU
Labels: oncall: pt2,oncall: cpu inductor

### 🚀 The feature, motivation and pitch

## Problem statement

If int8 asymmetric quantization is used, at Inductor compile time, the input used while invoking `torch.compile` might be such that the zero-points of activation for some quantized linear may _coincidentally_ be zero (per-tensor quantization) or all zeros (per-token quantization). In such a case, we might mistake this case to pertain to symmetric quantization.

Please suggest some solutions to this problem besides these two.

## Potential solution 1

One solution is to make zero-point optional for dequantizing an int8 tensor.

In torchao, it is possible to make some changes to ensure that int8 symmetric quantization would not have zero-points, so they wouldn’t be present in the Inductor graph. But similar changes would have to be made for PT2E quantization as well.

Nevertheless, if this change is made only in torchao, then we could still leverage this change with Inductor patterns corresponding to int8 symmetrically quantized activations that don't use zero-points for dequantization, but users who don't use torchao wouldn't benefit.

cc @chauhang @penguinwu @leslie-fang-intel @Xia-Weiwen 

# Alternatives

## Potential solution 2

For per-tensor quantization, we could add a runtime check in Inductor codegened code that'd detect as to whether the int8 quantization-type of an activation is symmetric or asymmetric (by checking if zp is 0).
But this approach may not be as performant for per-channel quantization (would need to check if any zp value is non-zero). 

#### This approach needs some new infra in Inductor-CPU codegen -

Support of two variants of epilogues, both of which are compiled, but only one of which is used at runtime depending upon some check. In this case, one variant would only applies activation & weight scales, while the second one would also compute compensation) – the decision to use one of them is to be made at runtime for the whole quantized linear.

### Additional context

We can compute int8 quantized linear with int8xint8 -> int32 GEMMs, so long as weights are not asymmetrically quantized.
If activations are asymmetrically quantized, we can apply compensation pertaining to zero-points of activation, after applying activation & weight scales.
If activations are symmetrically quantized, the computation is straightforward, and after int8 x int8 -> int32 GEMMs, we only need to apply pointwise activation & weight scales (which can happen at the block-level if we apply epilogues at micro-kernel level).
Repository: transformers
Issue: `model.config.to_diff_dict()` delivers different result to `model.save_pretrained()`
Labels: Core: Modeling,bug

### System Info

- `transformers` version: 4.48.0.dev0
- Platform: Linux-5.15.167.4-microsoft-standard-WSL2-x86_64-with-glibc2.35
- Python version: 3.12.5
- Huggingface_hub version: 0.25.1
- Safetensors version: 0.4.5
- Accelerate version: 0.34.2
- Accelerate config:    not found
- PyTorch version (GPU?): 2.5.1+cu124 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed
- Using distributed or parallel set-up in script?: <fill in>
- Using GPU in script?: <fill in>
- GPU type: NVIDIA GeForce RTX 4090

### Who can help?

@ArthurZuc

### Information

- [ ] The official example scripts
- [X] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [X] My own task or dataset (give details below)

### Reproduction

I have a use case that requires that model weights always be encrypted when in local storage and only be decrypted in memory. As a result, it is not an option to use `model.from_pretrained(dir)`.

Instead, my workaround has been to do:
```python
import msgspec
from pyfakefs.fake_filesystem_unittest import Patcher as ffspatcher
from transformers import AutoConfig, AutoModelForSequenceClassification, PreTrainedModel

weights = {...} # Deserialized to `dict` from an encrypted file elsewhere.
config = {...} # Deserialized to `dict` from an encrypted file elsewhere.

json_encoder = msgspec.json.encode

with ffspatcher() as patcher:
    fakepath = f'FAKE_FILE_SYSTEM://config.json'
    patcher.fs.create_file(fakepath, contents = json_encoder(config))
    config = AutoConfig.from_pretrained(fakepath)

model: PreTrainedModel = AutoModelForSequenceClassification.from_config(config)
model.load_state_dict(weights)
```

The problem I've noticed, however, is that when I serialize my config like so:
```python
config = model.config.to_diff_dict()
```

The resulting config includes the key `_attn_implementation_autoset` set to `True` whereas the actual config of the model does not include that key and as a result when I try loading the config with `AutoConfig.from_pretrained()`, it ends up not using the default attention implementation for my model, SDPA, delivering effectively a different model with different logits.

My current hotfix is to just delete the key `_attn_implementation_autoset` from all of my configs. But is it really necessary to add that key to `to_diff_dict()` when it is not added when you do `save_pretrained()`?

### Expected behavior

I get the same model in a reproduciable way as when I save the config with `to_diff_dict()` vs `save_pretrained()`.
Repository: flutter
Issue: [Proposal] Add a onClose callback to SearchAnchor to intercept suggestion close events
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

I need to call a function after SearchAnchor View closes

### Proposal

Add an "onClose" function to the widget