sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: In devicelab, periodically delete Xcode AppInstallationBinaryDeltas
Labels: team-infra,P2,infra: device lab,triaged-infra

On the devicelab the app installation deltas directory seems to grow and grow, eventually leading to low disk space:
```
~/Library/Containers/com.apple.CoreDevice.CoreDeviceService/Data/Library/Caches/AppInstallationBinaryDeltas
```
```
1.9G io.flutter.platformview.PlatformViewUITests.xctrunner
3.7G com.yourcompany.flutterView
4.2G io.flutter.examples.fullPlatformView
5.8G io.flutter.demo.gallery
8.1G com.yourcompany.microbenchmarks
8.2G com.example.platformChannelsBenchmarks
11M dev.flutter.infra-dialogUITests.xctrunner
12G com.yourcompany.platformViewsLayout
15G com.yourcompany.platforminteraction
15G io.flutter.externalUi
16G com.example.PlatformChannel
16G com.example.PlatformChannelSwift
16G com.example.spellCheck
16G com.yourcompany.flavors.paid
17G com.example.channels
17G com.example.wideGamutTest
19G io.flutter.platformview.platformviewTests
20G com.yourcompany.complexLayout
22G com.example.packageWithNativeAssets
25G io.flutter.examples.gallery
38G com.example.newGallery
110G io.flutter.e2e
242G com.example.macrobenchmarks
```
https://github.com/flutter/flutter/issues/148684#issuecomment-2123558467

Set up something (user agent?) in the devicelab to periodically remove everything in this directory.  The app deltas in this directory keep subsequent installations incremental, so we probably shouldn't delete it on every run, or it will slow down the tests and unnecessarily increase the bits we're writing to the device.
Repository: go
Issue: cmd/cgo/internal/testcarchive: TestManyCalls failures
Labels: NeedsInvestigation,compiler/runtime

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

Issue created automatically to collect these failures.

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

    === RUN   TestManyCalls
    === PAUSE TestManyCalls
    === CONT  TestManyCalls
        carchive_test.go:1209: [go build -buildmode=c-archive -o libgo7.a ./libgo7]
        carchive_test.go:1221: [gcc -fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/home/swarming/.swarming/w/ir/x/t/go-build2815952951=/tmp/go-build -gno-record-gcc-switches -I /home/swarming/.swarming/w/ir/x/t/carchive_test2671988462/pkg/linux_amd64_shared/testcarchive -o testp7 main7.c libgo7.a]
        carchive_test.go:1237: test program timed out
        carchive_test.go:1244: [./testp7]
        carchive_test.go:1246: signal: killed
    --- FAIL: TestManyCalls (63.87s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: workbench.explorer.fileView.toggleVisibility does not work
Labels: bug,file-explorer,confirmation-pending

Type: <b>Bug</b>

I think the file list view on the sidebar is called fileView in command names, because workbench.explorer.fileView.focus opens and focuses that view.

So, workbench.explorer.fileView.toggleVisibility should toggle fileView, but this does nothing.

VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:16:23.416Z)
OS version: Linux x64 6.5.0-35-generic
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 x 4600)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<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: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|1, 0, 0|
|Memory (System)|31.25GB (26.11GB free)|
|Process Argv|--crash-reporter-id 38674377-bc44-42f3-8275-501299517ac6|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|ubuntu|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu|
|XDG_SESSION_TYPE|x11|
</details><details><summary>Extensions (12)</summary>

Extension|Author (truncated)|Version
---|---|---
ruff|cha|2024.20.0
vscode-quick-select|dba|0.2.9
githistory|don|0.6.20
vscode-autohotkey-plus-plus|mar|5.0.3
debugpy|ms-|2024.6.0
python|ms-|2024.6.0
vscode-pylance|ms-|2024.5.1
remote-containers|ms-|0.362.0
cpptools|ms-|1.20.5
autodocstring|njp|0.6.1
vscode-fileutils|sle|3.10.3
gitblame|wad|11.0.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes516:30244333
vscorecescf:30445987
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
showvideot:31016892
chatpanelt:31048053
dsvsc021:30996838
0ee40948:31013168
pythoncenvptcf:31049071
fchga941:31046352
pythonprt:31047983
dwnewjupyter:31046869
26j00206:31048877

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: [dynamo] Check for invalid random_ arguments while tracing
Labels: triaged,oncall: pt2,module: dynamo

Discovered with https://github.com/pytorch/pytorch/pull/126341.

Original repro command: `PYTORCH_TEST_WITH_DYNAMO=1 python -m pytest test/test_tensor_creation_ops.py::TestTensorCreationCPU::test_random_from_to_bool_cpu`

Repro:
```python
import torch

def f():
    try:
        x = torch.empty((3, 3), dtype=torch.bool)
        x.random_(-1, 1)
    except:
        x = x + 1
    return x

opt_f = torch.compile(f, backend="eager")
opt_f()
```

Output:
```
$ TORCH_LOGS="graph_code" python playground3.py 
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code] TRACED GRAPH
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]  ===== __compiled_fn_1 =====
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]  /data/users/williamwen/pytorch2/torch/fx/_lazy_graph_module.py class GraphModule(torch.nn.Module):
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]     def forward(self):
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]         # File: /data/users/williamwen/pytorch2/playground3.py:5 in f, code: x = torch.empty((3, 3), dtype=torch.bool)
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]         x: "b8[3, 3]" = torch.empty((3, 3), dtype = torch.bool)
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]         
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]         # File: /data/users/williamwen/pytorch2/playground3.py:6 in f, code: x.random_(-1, 1)
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]         random_: "b8[3, 3]" = x.random_(-1, 1)
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]         return (x,)
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code]         
V0521 17:33:16.624000 139979020912448 torch/_dynamo/output_graph.py:1277] [0/0] [__graph_code] 
Traceback (most recent call last):
  File "/data/users/williamwen/pytorch2/playground3.py", line 12, in <module>
    opt_f()
  File "/data/users/williamwen/pytorch2/torch/_dynamo/eval_frame.py", line 414, in _fn
    return fn(*args, **kwargs)
  File "/data/users/williamwen/pytorch2/playground3.py", line 3, in f
    def f():
  File "/data/users/williamwen/pytorch2/torch/_dynamo/eval_frame.py", line 548, in _fn
    return fn(*args, **kwargs)
  File "<eval_with_key>.1", line 6, in forward
RuntimeError: from is out of bounds for bool
```

Also happens with `uniform_`.

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng
Repository: rust
Issue: Should have a stack-probe test that doesn't need std's overflow handler
Labels: A-testsuite,C-enhancement,E-needs-test,T-libs

Many platforms need to ignore `stack-probes.rs` simply because they cannot emit the right lines of text. I think testing std's stack overflow handler and its messaging should be distinguished from the possibly more critical question of "well, do we have stack probes or not?"

See:
- https://github.com/rust-lang/rust/issues/25872
- https://github.com/rust-lang/rust/issues/124823
- https://github.com/rust-lang/rust/pull/125226
Repository: vscode
Issue: Custom labels: support full file name variable
Labels: feature-request,workbench-custom-labels

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
Awesome feature! I've been using the following config:
**: [${dirname}] ${filename}.${extname}

However, there's a slight problem with dot files. (e.g. `.zshrc`)
The above config renders it as `[prevDirectory] .zshrc.`, but I want it without the ending dot. Is that possible with the current levers?
Repository: puppeteer
Issue: [Bug]: setcontent uses document.write triggering chrome console error
Labels: bug,confirmed,P3

### Minimal, reproducible example

```TypeScript
const puppeteer = require("puppeteer");

async function screenshot() {
  const browser = await puppeteer.launch({
    headless: 'shell',
    ignoreHTTPSErrors: true,
  });
  const page = await browser.newPage();
  page.on("console", msg => console.error(msg.text()));
  const html = '<html><head></head><body><script type="text/javascript" src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.js"></script></body></html>';
  await page.setContent(html, {waitUntil: 'networkidle0'});
  await browser.close();
}

process.exitCode = 1;
screenshot();
```


### Error string

A parser-blocking, cross site (i.e. different eTLD+1) script, https://cdnjs.cloudflare.com/ajax/libs/jquery/3.7.1/jquery.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message. See https://www.chromestatus.com/feature/5718547946799104 for more details.

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

_No response_

### Expectation

I expected setcontent to use non-deprecated browser features.

### Reality

It errors.

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.9.0

### Node version

18.20.2

### Package manager

yarn

### Package manager version

1.22.22

### Operating system

Linux
Repository: material-ui
Issue: [icons] Material Icons do not support Joy UI's "danger" color prop
Labels: on hold,package: icons,package: joy-ui

### Steps to reproduce

Link to live example: 

Steps:
1. Import any Icon from "@mui/icons-material"
2. Import Button from "@mui/joy"
3. Set the color prop on any Icon to "danger"


### Current behavior

Type '"danger"' is not assignable to type '"primary" | "success" | "warning" | "disabled" | "action" | "inherit" | "secondary" | "error" | "info" | undefined'.

### Expected behavior

Expected behavior is for the icon to inherit the red "danger" color, as is the case with all Joy components.

### Context

I'm trying to use it to create simple label strings (in <FormHelperText>)

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: Icons, Icons-Material, Joy UI, Danger
Repository: ollama
Issue: ollama and the inference results are inconsistent with the inference results of Transformers (HF)
Labels: bug

### What is the issue?

This is the evaluation result of using our own benchmark on ollama and transformers, and the gap is huge.

My benchmark is a set similar to function call, which is more difficult than QA questions such as summary. It requires the model to have certain instruction following ability and logical reasoning ability. The evaluation shows that the same model llama3-8B-int4 has completely different results on the two frameworks.

<img width="916" alt="image" src="https://github.com/ollama/ollama/assets/22168174/2ab36ef7-d0c7-4d4f-8a72-e9b7e3c50008">



### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.1.37
Repository: PowerToys
Issue: [Advanced Paste > Paste with AI] Custom Model / Endpoint Selection
Labels: Idea-Enhancement,Tracker,Product-Advanced Paste

### Description of the new feature / enhancement

It should be possible to configure the model used (currently fixed as `gpt3.5-turbo`) and endpoint (currently fixed as OpenAI's) to arbitrary values

### Scenario when this would be used?

Sending requests to an alternative AI endpoint (eg a local model, internal company hosted models, alternative ai providers), or ensuring higher-quality conversions (eg by pointing requests at gpt-4o)

### Supporting information

[Microsoft's documentation](https://learn.microsoft.com/en-us/dotnet/api/overview/azure/ai.openai-readme?view=azure-dotnet-preview) appears to suggest that the underlying library used for AI completions supports other libraries, it just needs to be provided with an endpoint.

The currently used model is a hardcoded string in this repository
Repository: PowerToys
Issue: Re-submit UI bug
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.81.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

![2024-05-22 09 32 46](https://github.com/microsoft/PowerToys/assets/8612989/16d6790f-d9c4-4e92-8450-0070913f2fd8)
Already submitted once, but still the same

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: terminal
Issue: Windows Terminal Window Does Not Send `EVENT_OBJECT_DESTROY` On Close
Labels: Issue-Bug,Needs-Triage,Needs-Attention

### Windows Terminal version

1.19.11213.0

### Windows build number

10.0.22631.0

### Other Software

_No response_

### Steps to reproduce

Open a single instance of Windows terminal on the desktop. Close that instance of Windows Terminal. `EVENT_OBJECT_DESTROY` is not emitted.

### Expected Behavior

`EVENT_OBJECT_DESTROY` should be emitted when the Windows Terminal window is closed by the window handle that the user has just interacted with.

### Actual Behavior

`EVENT_OBJECT_DESTROY` is not emitted for the Windows Terminal window that was closed.

When opening Windows Terminal, `EVENT_SYSTEM_FOREGROUND` is emitted, and the window handle of the actual window that I as the user interact with is the log example below is `658858`:
```
2024-05-22T01:39:16.367526Z  INFO process_event{event=FocusChange(SystemForeground, Window { hwnd: 658858 })}: komorebi::process_event: processed: (hwnd: 658858, title: PowerShell, exe: WindowsTerminal.exe, class: CASCADIA_HOSTING_WINDOW_CLASS)
```

When I close the window, _sometimes_ an `EVENT_OBJECT_HIDE` is emitted, but it is emitted for a completely separate window handle (`920252`):

```
2024-05-22T01:39:18.051931Z DEBUG process_event{event=Hide(ObjectHide, Window { hwnd: 920252 })}:should_manage{self=Window { hwnd: 920252 } event=Some(Hide(ObjectHide, Window { hwnd: 920252 }))}: komorebi::window: ignoring (exe: WindowsTerminal.exe, title: DesktopWindowXamlSource, event: Hide (WinEvent: ObjectHide, Window: (hwnd: 920252)))
```
Repository: PowerToys
Issue: File Locksmith doesn't detect locked folders
Labels: Issue-Bug,Needs-Triage,Product-File Locksmith

### Microsoft PowerToys version

0.81.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

File Locksmith

### Steps to reproduce

Tried to rename a folder (probably similar if trying to delete a folder)
Windows advised it couldn't because it was being used by another process
In File Explorer right-clicked the folder and selected Unlock with File Locksmith


### ✔️ Expected Behavior

Locksmith should be able to identify the process holding the lock on the folder for the user (and offer to terminate or locate the process).

### ❌ Actual Behavior

File Locksmith failed to find any processes using the folder!

Instead, I installed and ran alternative software Lock Hunter, which found the offending process; was able to terminate it; and I was able to remove the original folder.

### Other Software

_No response_
Repository: transformers
Issue: [LLaMA3] 'add_bos_token=True, add_eos_token=True' seems not taking effect
Labels: Core: Tokenization,Feature request

### System Info

Platform = Windows
PyTorch = 2.3.0
Transformers = 4.41.0

### Who can help?

_No response_

### 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

```
import torch
from transformers import AutoTokenizer

LLaMAPath = '/path/to/llama3-8b'

# The following two yields the same results, all of them contains BOS token and no EOS token
tokenizer = AutoTokenizer.from_pretrained(LLaMAPath, add_bos_token=True, add_eos_token=True)
# tokenizer = AutoTokenizer.from_pretrained(LLaMAPath, add_bos_token=False, add_eos_token=False)

tokenizer.add_special_tokens({"pad_token": "
"}) 
inputs = tokenizer(['hi, how are you today?'], padding=True, return_tensors='pt')
print(inputs)
```

All of the statements above produce `[128000,   6151,     11,   1268,    527,    499,   3432,     30]`

### Expected behavior

I think when using `tokenizer = AutoTokenizer.from_pretrained(LLaMAPath, add_bos_token=True, add_eos_token=True)`, we get `[128000,   6151,     11,   1268,    527,    499,   3432,     30,  128001]`,

when using `tokenizer = AutoTokenizer.from_pretrained(LLaMAPath, add_bos_token=False, add_eos_token=False)`, we get `[6151,     11,   1268,    527,    499,   3432,     30]`,
Repository: pytorch
Issue: [dynamo][flaky-test] test skipping after polluting global state
Labels: triaged,oncall: pt2,module: dynamo

### 🐛 Describe the bug

Continuation of: https://github.com/pytorch/pytorch/issues/126178, which we need closed for CI test to be re-enabled.

Repro
1. revert https://github.com/pytorch/pytorch/pull/126790
2. `PYTORCH_TEST_WITH_DYNAMO=1 python test/test_nn.py -k test_swap_module_params_fails_after_forward` is marked as skip after executing its first line outside the try-finally block: 
https://github.com/pytorch/pytorch/blob/d54c28e7fcb6377aa007c0d3e53837683420af4b/test/test_nn.py#L1597-L1599 This pollutes global state, and the second test fails 

After fix, this should pass: `PYTORCH_TEST_WITH_DYNAMO=1 pytest test/test_nn.py::TestNN::test_swap_module_params_fails_after_forward test/test_nn.py::TestNNDeviceTypeCPU::test_conv_empty_input_cpu_float64`

### Versions

main

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng
Repository: deno
Issue: suggestion: expand the functionality of `deno doc --lint`
Labels: cli,suggestion

Such as:
1. Ensure all type parameters are documented with a `@typeParam` or `@template` tag.
2. Ensure all parameters are documented with a [`@param`](https://jsdoc.app/tags-param), `@arg`, or `@argument` tag.
3. Ensure all functions and methods are documented with a [`@returns`](https://jsdoc.app/tags-returns) tag.
4. Ensure all symbols have at least one [`@example`](https://jsdoc.app/tags-example) tag.

This would significantly improve the quality of package documentation. We currently compensate for this missing functionality in the Standard Library by implementing our own [doc checker](https://github.com/denoland/deno_std/blob/main/_tools/check_docs.ts).

If approved, I'd happily help with these efforts.

CC @dsherret
Repository: pytorch
Issue: propagate_real_tensors can cause deadlocks for programs with collectives
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

Hat tip @flaviotruzzi for pointing this out.

Propagate real tensors will run real tensor compute during compilation. That includes collective calls. But collective calls will deadlock if not all ranks are doing the same thing. So if you have a program where one rank is recompiling but another is not, boom, instant deadlock. This potentially is workaroundable by forcing recompilation on all ranks.

But wait, it gets worse. Suppose that in one rank you compile a collective call, and in another rank you don't compile the collective call because of some rank specific graph break. Then the compile-time collective just doesn't have any paired collective at all, and once again you're toast. But now the non-compiled rank doesn't even know that it's supposed to emit extra collectives.

For more cancer: fake tensor propagation can happen multiple times, e.g., when we repropagate information. It happens at least four times, once in Dynamo, twice in AOTAutograd, once in Inductor. Each time we repropagate a collective, we will trigger the collective again. If you have something like a graph break induced restart in Dynamo, that will also generate a repropagate in Dynamo.

We can't put garbage data in the collective calls, because the collectives are often communicating things like tensor splits which must have real data or you will IMA.

In all likelihood, the only reasonable thing to do is to save the results of collective calls the first time they occur, and then ensure we consistently reuse that result on subsequent calls. This is reminiscent of the unbacked SymInt reallocation problem. I'm not sure I actually want to spend effort actually implementing this though.

### Versions

main

cc @msaroufim @bdhirsh @anijain2305 @chauhang
Repository: storybook
Issue: Theming 2.0
Labels: feature request

RFC: https://github.com/storybookjs/storybook/discussions/24344
Repository: PowerToys
Issue: File Locksmith do not include service that locked a folder or file
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.81.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

File Locksmith

### Steps to reproduce

Have a service that locked a folder or file then try to do anything with said folder or file. 

### ✔️ Expected Behavior

File locksmith should be able to find any process or services that lock folder or file from modify. 

### ❌ Actual Behavior

File locksmith does not show services that locked a folder or file, displaying no results even with administrator privilege. 

### Other Software

_No response_