sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [tool_crash] String: <57 characters>
Labels: c: crash,tool,P2,team-tool,triaged-tool

## Command
```
flutter run --profile
```

## Steps to Reproduce
1. ...
2. ...
3. ...

## Logs
String: <57 characters>
```

```
```
[✓] Flutter (Channel unknown, 3.0.1, on macOS 11.6 20G165 darwin-x64, locale zh-Hans-CN)
    • Flutter version 3.0.1 at /Users/wujie/.rflutter_sdk/rflutter
    • Upstream repository unknown
    • Framework revision fb57da5f94 (3 months ago), 2022-05-19 15:50:29 -0700
    • Engine revision caaafc5604
    • Dart version 2.17.1
    • DevTools version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/wujie/Library/Android/sdk
    • Platform android-32, build-tools 32.0.0
    • Java binary at: /Users/wujie/Downloads/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✗] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once i
Repository: flutter
Issue: Input Decorator overflows the parent widget vertically
Labels: a: text input,framework,f: material design,a: desktop,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-design,triaged-design

## Steps to Reproduce

1. Run https://dartpad.dev/?id=60403a776f027d75ccd29aa2421342b7

**Expected results:**
The InputDecorator in red should be inside the parent widget without any overflow.

**Actual results:**
On web (screenshot) we can see on the top and bottom a small overflow. On android, this is slightly different but still buggy.

![image](https://user-images.githubusercontent.com/18555491/182391056-e103feb2-5a7f-43c3-9ceb-e9b180412fbc.png)

I have not find a workaround yet. Might be a similar issue with another approach https://github.com/flutter/flutter/issues/82709.
Repository: storybook
Issue: Missing description in 'Docs' for Svelte components with top-level {#if}s
Labels: bug,needs triage

**Describe the bug**
The 'docs' addon isn't displaying Svelte components' descriptions in the 'Docs' tab, when that component includes a top-level `{#if ...}`.

Note this only happens for component descriptions in HTML comments ([the recommended approach for component docs](https://svelte.dev/faq#how-do-i-document-my-components)). If the description is in a JSDoc block, the description is displayed correctly in the 'Docs' tab.

**To Reproduce**
Follow the install instructions in [this reproduction repo](https://github.com/egargan/repro-storybook-svelte-no-docs-description).

**System**
```
Environment Info:
  System:
    OS: macOS 11.6.7
    CPU: <removed>
  Binaries:
    Node: 16.9.1 - ~/.nvm/versions/node/v16.9.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v17.9.1/bin/yarn
    npm: 7.21.1 - ~/.nvm/versions/node/v16.9.1/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Firefox: 102.0.1
    Safari: 15.5
  npmPackages:
    @storybook/addon-actions: ^6.5.9 => 6.5.9
    @storybook/addon-essentials: ^6.5.9 => 6.5.9
    @storybook/addon-interactions: ^6.5.9 => 6.5.9
    @storybook/addon-links: ^6.5.9 => 6.5.9
    @storybook/addon-svelte-csf: ^2.0.4 => 2.0.4
    @storybook/svelte: ^6.5.9 => 6.5.9
    @storybook/testing-library: ^0.0.13 => 0.0.13
```
Repository: excalidraw
Issue: escape should deselect elements
Labels: enhancement

To align with other editors.

Might require some rewriting of keyboard handling to ensure that higher-precedence esc handlers (popups, blurring inputs, ...) doesn't deselect.
Repository: go
Issue: go/doc/comment: Inconsistent documentation about comment.Parser.LookupPackage == nil
Labels: Documentation,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19rc2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

```
$ go doc comment.Parser
[...]
        // Setting LookupPackage to nil is equivalent to setting it to
        // a function that always returns "", false.
        LookupPackage func(name string) (importPath string, ok bool)
[...]
```

```
$ go doc comment.DefaultLookupPackage
package comment // import "go/doc/comment"

func DefaultLookupPackage(name string) (importPath string, ok bool)
    DefaultLookupPackage is the default package lookup function, used when
    Parser.LookupPackage is nil. It recognizes names of the packages from the
    standard library with single-element import paths, such as math, which would
    otherwise be impossible to name.
[...]
```

### What did you expect to see?

Consistent documentation.

### What did you see instead?

Contradictory statements in the documentation for `comment.Parser` and `comment.DefaultLookupPackage` regarding the behavior when `comment.Parser.LookupPackage == nil`.
Repository: tensorflow
Issue: MirroredStrategy does not use GPUs simultaneously
Labels: comp:dist-strat,type:performance,TF 2.9

### Issue Type

Performance

### Source

binary

### Tensorflow Version

2.6,2.7,2.8,2.9

### Custom Code

Yes

### OS Platform and Distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.8

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

DGX1 V100 

### Current Behaviour?

Hi,
I have observed some bad performance when trying to run single machine / multi-GPU jobs. I have reported a minimum example below. When looking at the GPU performance (with NVIDIA NSight System), I can see that the GPUs run almost sequentially, i.e., GPU0 will do some work then when it is almost done, GPU1 will start. 

![image](https://user-images.githubusercontent.com/37110816/182431591-47ff8961-9987-4d91-afd1-356881078bd9.png)

I have executed a similar version of the code on PyTorch and it exhibits the expected behaviour, i.e., the GPUs run in parallel.

![image](https://user-images.githubusercontent.com/37110816/182431647-fe5f2162-3045-43e1-a444-238d9d828d7f.png)

This issue on TF dramatically slows down model training. Can someone help me with the issue? Am I not using MirroredStrategy correctly? I used `@tf.function` to disable the eager execution of the graphs. I am posting the code below and to remove any impact of data loading, each GPU creates their own tensor to work on.

Thanks!


### Standalone code to reproduce the issue

```shell
import tensorflow as tf
import numpy as np
import time
from functools import partial

N = 2**20
D = 1

mirrored_strategy = tf.distribute.MirroredStrategy()
N_DEVICES = mirrored_strategy.num_replicas_in_sync

print(f'Found {N_DEVICES} gpus')

def per_replica_grads():
    M = tf.eye(8192)
    M = tf.linalg.inv(M)
    return M[0, :]


@tf.function
def step():
    with mirrored_strategy.scope():
        fn_replica = mirrored_strategy.run(per_replica_grads)
        fn_replica_summed = mirrored_strategy.reduce(tf.distribute.ReduceOp.SUM, fn_replica, axis=None)
    return fn_replica_summed


for it in range(10):
    time.sleep(0.5)
    print(step())
```


### Relevant log output

_No response_
Repository: flutter
Issue: [adaptive_scaffold] Develop An Infrastructure to Support Developing Adaptive Layouts
Labels: package,team-ecosystem,P3,p: flutter_adaptive_scaffold,triaged-ecosystem

Currently building an adaptive app is very “barebones”; There is no one “plug and play” solution for developers
This project will provide developers with an abstracted and more friendly interface to develop adaptive applications.

Described further in the [design doc](https://docs.google.com/document/d/1qhrpTWYs5f67X8v32NCCNTRMIjSrVHuaMEFAul-Q_Ms/edit?usp=sharing)

Will be released as a package in flutter/packages and then reevaluated.

First stage in release: https://github.com/flutter/packages/pull/2406
Repository: pytorch
Issue: in-place variants should get their own OpInfos
Labels: triaged,better-engineering,module: testing

### 🚀 The feature, motivation and pitch

Today, to write an OpInfo test to check that a subsystem (let's say vmap) works on all operations, we write something like the following:
```
@ops(op_db)
def test_vmap(self, device, dtype, op):
  test_op(op)
  if op.inplace_variant:
    test_op(op.inplace_variant)
```
Let's say that we have correct vmap support for torch.add, but incorrect support for `Tensor.add_`. Then there is no way to specify "I want to skip this test for Tensor.add_ but have the test run for torch.add" without adding additional infrastructure.

If we made in-place variants their own OpInfos, we could rewrite the above test as the following. And, since the OpInfo for "add" would be separate from "add_", then we would be able to skip them separately from each other.
```
@ops(op_db)
def test_vmap(self, device, dtype, op):
  test_op(op)
```

### Alternatives

Split test_vmap into the following:
```
@ops(op_db)
def test_vmap(self, device, dtype, op):
  test_op(op)

@ops(op_db)
def test_vmap_inplace(self, device, dtype, op):
  if op.inplace_variant:
    test_op(op.inplace_variant)
 ```
 but keep in mind that everyone who uses OpInfos and cares about out-of-place and in-place operations now needs to write two tests.

### Additional context

cc @mruberry @ngimel what are your thoughts?
Repository: flutter
Issue: Tooltip semantics are being read aloud when tooltip is not visible
Labels: framework,f: material design,a: accessibility,has reproducible steps,found in release: 3.3,found in release: 3.4,team-design,triaged-design

## Steps to Reproduce

1. Add a Tooltip with a message and a Text widget as its child.
2. Turn on Accessibility. 
3. Tap on Text widget
4. Observe the Tooltip message is being read even though the tooltip is not visible. 

Note: The same is true for a tooltip widget that has no child or is not visible.

**Expected results:**

I would expect the semantic labels of the tooltip or the message of the tooltip to not be read aloud unless visible.

**Actual results:**

I am seeing the Tooltip message being read aloud even when the tooltip is not visible. 


The below example illustrates how we are trying to use a Tooltip around a Text widget to display the full amount of text. This is so users will always have access to the full text.

```dart
const Tooltip(
  message: 'Should display full message in tooltip',
 child: Text('Should have some really long text that is cut off from ellipsis', maxLines: 2, overflow: TextOverflow.ellipsis)
)
```
Repository: yt-dlp
Issue: Thumbnail added to FLAC again
Labels: enhancement,core:post-processor

Run this command few times and see how each time file increase in size due to thumbnail embdded again as new another one. This happens because of format - **FLAC**. It doesn't happen for mp3. Disadvantage is more noticeable for songs with heavy thumbnails.
`yt-dlp https://soundcloud.com/uselet/funny-loud-music -x --audio-format flac --embed-thumbnail`

mediainfo says
```
Cover                       : Yes / Yes / Yes / Yes / Yes / Yes / Yes
Cover type                  : Cover (front) / Cover (front) / Cover (front) / Cover (front) / Cover (front) / Cover (front) / Cover (front)
Cover MIME                  : image/jpeg / image/jpeg / image/jpeg / image/jpeg / image/jpeg / image/jpeg / image/jpeg
```
Repository: rust
Issue: Tracking LLVM workarounds
Labels: A-LLVM,metabug,T-compiler,C-tracking-issue

This is a metabug for tracking the compiler's workarounds of LLVM's behavior that have resulted in the compiler implementing what one might refer to as "ugly hacks" to fix the behavior in question on our side. Logically, when the behavior is resolved and appropriate tests if any have been added, the issue can be closed, from Rust's perspective. Worse, leaving "fixed but not ideally" issues open makes it harder to sift through and prioritize problems. However, also logically, we also want to obtain various code improvements in the future, and not tracking them in some way makes it harder for us to find them again. Thus the purpose of this metabug is to allow observing these as a collective.

- [ ] https://github.com/rust-lang/rust/issues/43517 patched by https://github.com/rust-lang/rust/pull/47007
- [ ] https://github.com/rust-lang/rust/issues/98768 patched by https://github.com/rust-lang/rust/pull/98998
Repository: pytorch
Issue: Schema information for torch.* operations
Labels: triaged,module: __torch_function__,module: testing

### 🚀 The feature, motivation and pitch

My main motivation for this is for in-place vmap testing. In order to do vmap in-place testing, we must, given an OpInfo, construct some sample inputs, some of which are batched or not. For example, given `Tensor.add_(x, y)`, we would need to generate x and y.

There is a problem if we generate x to be a regular Tensor and y to be the Tensor being vmapped over, because that errors out. If we knew that the first argument to `Tensor.add_` is the argument that gets mutated, then we can avoid generating the aforementioned case.

I don't know if anything else would find this useful, but just putting it out there.

### Alternatives

- Assume that the first argument of an in-place operation gets mutated :) (this is not always true)
- Try to "guess" what the aten operator that corresponds to a python torch in-place operation is. e.g. Tensor.add_ -> at::add_. This does not always work.

### Additional context

_No response_

cc @hameerabbasi @rgommers @peterbell10 @ezyang
Repository: pytorch
Issue: unittest.subTest and way to selectively mark subTests as expected failures
Labels: triaged,better-engineering,module: testing

### 🚀 The feature, motivation and pitch

When testing if something like vmap works on an operator, we test the following things:
1. if it errors out (it shouldn't)
2. if the output of vmap matches the output of a for loop (it should)
3. if there is a batching rule implemented for the operation. We do this by running the vmap and checking if it raises any "batching rule not implemented" warnings.

We have two separate tests, test_vmap_exhaustive, and test_op_has_batch_rule. The former does (1) and (2), and the latter does (1), (2), (3) (because (1) and (2) are almost required for (3)). We could cut down the test time if we have one test and used something like unittest.subTest in a way so that each test gets 3 subtests.

Furthermore, if a vmap test fails for e.g. torch.searchsorted, we have an expected failure for it. It would be nice to be able to distinguish between if it failed because of (1) or if it failed because of (2); (2) is a silent correctness issue and is much more hi-pri to fix.

### Alternatives

n/a

### Additional context

cc @jbschlosser who has worked on many testing improvements in the past
Repository: godot
Issue: Popup dialog buttons wrong size when popup was previously displayed smaller
Labels: bug,topic:editor,topic:gui

### Godot version

v4.0.alpha13.official [59dcddc45]

### System information

Pop!_OS 22.04 LTS

### Issue description

https://user-images.githubusercontent.com/61291296/182470516-2a1ffe38-7d3b-454c-8a17-784d18d70e4c.mp4

The "save changes to scene before X" popup can display with the rightmost button being too small if the popup was previously displayed with a smaller size. I don't think this occurs with popups more generally - I've also seen the rightmost button of the "Attach Node Script" popup be similarly too small, but I haven't been able to reproduce that (though it did happen quite a few times).

I haven't been able to reproduce this in alpha 12.

### Steps to reproduce

Have a scene with unsaved changes.
Start closing the editor by clicking the X.
Click cancel in the popup.
Start reloading the project with `Project > Reload Current Project`.
Observe the little button.

### Minimal reproduction project

See reproduction steps.
Repository: transformers
Issue: Update no_trainer scripts to include gradient accumulation
Labels: Examples,Good First Issue

### Feature request

🤗 Accelerate has a gradient accumulation wrapper, and the `no_trainer` scripts should be updated to include it! 

An example can be seen [here](https://github.com/huggingface/accelerate/blob/main/examples/by_feature/gradient_accumulation.py), below is an example diff of what the integration would look like:

```diff
-     accelerator = (
-         Accelerator(log_with=args.report_to, logging_dir=args.output_dir) if args.with_tracking else Accelerator()
-     )
+     accelerator = (
+         Accelerator(log_with=args.report_to, logging_dir=args.output_dir, gradient_accumulation_steps=args.gradient_accumulation_steps) if args.with_tracking else Accelerator(gradient_accumulation_steps=args.gradient_accumulation_steps)
+     )
```

As well as:
```diff
-     num_update_steps_per_epoch = math.ceil(len(train_dataloader) / args.gradient_accumulation_steps)
+     num_update_steps_per_epoch = len(train_dataloader)

...


for step, batch in enumerate(train_dataloader):
+     with accelerator.accumulate(model):
```
```diff
-             loss = loss / args.gradient_accumulation_steps
            accelerator.backward(loss)
-             if step % args.gradient_accumulation_steps == 0 or step == len(train_dataloader) - 1:
            optimizer.step()
            lr_scheduler.step()
            optimizer.zero_grad()
                progress_bar.update(1)
                completed_steps += 1
```

The list of available scripts to update include:

- [ ] examples/pytorch/image-classification/run_image_classification_no_trainer.py
- [ ] examples/pytorch/language-modeling/run_clm_no_trainer.py
- [ ] examples/pytorch/language-modeling/run_mlm_no_trainer.py
- [ ] examples/pytorch/multiple-choice/run_swag_no_trainer.py
- [ ] examples/pytorch/question-answering/run_qa_beam_search_no_trainer.py
- [ ] examples/pytorch/question_answering/run_qa_no_trainer.py
- [ ] examples/pytorch/semantic-segmentation/run_semantic_segmentation_no_trainer.py
- [ ] examples/pytorch/speech-pretraining/run_wav2vec2_pretraining_no_trainer.py
- [ ] examples/pytorch/summarization/run_summarization_no_trainer.py

### Motivation

This is a great first issue for someone who wants to learn how to use some of the latest bits in Accelerate and get an easy beginner contribution to the library 🤗 

### Your contribution

If you decide to pick up this issue, feel free to ping myself (@muellerzr), @sgugger, or @pacman100 to review 🤗
Repository: pytorch
Issue: SequentialLR does not work correctly with multiple ConstantLR
Labels: triaged,module: LrScheduler

In combination with multiple ConstantLR schedulers, SequentialLR should use one at a time (depending whether the current epoch and milestones), but it instead applies several at the same time. For the example below:

```
import torch.optim
from torch import nn
from torch.optim.lr_scheduler import ConstantLR
from torch.optim.lr_scheduler import SequentialLR

model = nn.Linear(10, 10)
optimizer = torch.optim.Adam(model.parameters(), lr=1.0)

scheduler1 = ConstantLR(optimizer, factor=0.5, total_iters=3)
scheduler2 = ConstantLR(optimizer, factor=0.3, total_iters=4)
scheduler = SequentialLR(optimizer, schedulers=[scheduler1, scheduler2], milestones=[3])

for step in range(6):
    scheduler.step()
    print(step, scheduler.get_last_lr())
```

The output is:
0 [0.15]
1 [0.15]
2 [0.3]
3 [0.3]
4 [0.3]
5 [0.3]

While the correct output should be:
0 [0.5]
1 [0.5]
2 [0.3]
3 [0.3]
4 [0.3]
5 [0.3]

### Versions

1.12
Repository: go
Issue: x/sys/windows: fix Accept implementation
Labels: NeedsFix

Currently [`windows.Accept`](https://cs.opensource.google/go/x/sys/+/1609e554:windows/syscall_windows.go;l=1254) (like `syscall.Accept` for `GOOS=windows`) contains a stub function which does nothing.

Looks like this function was introduced to mimic `unix.Sockaddr.Accept` method but it's just a useless stub.

I propose to fix it's signature and re-implement it as winsock's [accept](https://docs.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-accept) function.

In the end it will look something like this:

```go
package windows

func Accept(fd windows.Handle, sockaddr, sockaddrLen uintptr)
```

**Winsock accept function signature** (see [MSDN](https://docs.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-accept))

```c
SOCKET WSAAPI accept(
  [in]      SOCKET   s,
  [out]     sockaddr *addr,
  [in, out] int      *addrlen
);
```

Instead of passing sockaddr raw pointer and it's size it's possible to also use `Sockaddr` interface and the same approach like in `windows.Bind` but it will limit method's potential use cases (it can't be used for custom sockets). See #54209.
Repository: pytorch
Issue: Move nested-tensor tutorial from prototype
Labels: triaged,module: nestedtensor

### 📚 The doc issue

Nested-tensor tutorial involves ops that are nightly-only now, so it is put under prototype/ and have _tutorial suffix removed.

### Suggest a potential alternative/fix

Once new PyTorch release comes out, we should move it back to beginner/ and append _tutorial suffix.

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @mikaylagawarecki
Repository: flutter
Issue: [flutter_tools] DartDevelopmentServiceException in DartDevelopmentServiceImpl.startService()
Labels: c: crash,tool,platform-web,P2,team-web,triaged-web

on Beta/3.3.0-0.0.pre

```
DartDevelopmentServiceException: WebSocketChannelException: WebSocketChannelException: WebSocketException: Connection to 'http://127.0.0.1:44456/C8p9ZOEuA0k=/ws#' was not upgraded to websocket
at DartDevelopmentServiceImpl.startService(dds_impl.dart:133)
at <asynchronous gap>(async)
at DartDevelopmentService.startDartDevelopmentService(dds.dart:97)
at <asynchronous gap>(async)
at DebugService.startDartDevelopmentService(debug_service.dart:156)
at <asynchronous gap>(async)
at DevHandler._createAppDebugServices(dev_handler.dart:468)
at <asynchronous gap>(async)
at DevHandler.loadAppServices(dev_handler.dart:244)
at <asynchronous gap>(async)
at Dwds.debugConnection(dwds.dart:91)
at <asynchronous gap>(async)
at WebDevFS.connect.<anonymous closure>(devfs_web.dart:694)
at <asynchronous gap>(async)
```
Repository: godot
Issue: `draw_texture_rect` still doesn't seem to be working as expected
Labels: bug,topic:rendering,topic:2d

### Godot version

v4.0.alpha13.official [82811367c]

### System information

Linux Mint 20.3

### Issue description

The change in implementation between alpha12 and alpha13 resulted in #63775.

| Alpha12 | Alpha13 |
| :-------: | :-------: |
| ![alpha12](https://user-images.githubusercontent.com/30386067/182496496-3474ab73-e766-4120-8c78-6fa2e04fd1a8.png) | ![alpha13](https://user-images.githubusercontent.com/30386067/182496502-4f67f93a-9d6e-46bf-b106-d8e2f168aa78.png) |
| ![alpha12-1](https://user-images.githubusercontent.com/30386067/182496507-f6d74df9-375f-442e-ba0b-15a2d19148c9.png) | ![alpha13-1](https://user-images.githubusercontent.com/30386067/182496498-acaba5e2-1b00-4b3f-825b-a07665e4b756.png) |

It doesn't seem to fit in `rect`, it seems to swap the `x`, `y` of the `rect` as well. I'm not sure if this is as expected. 

### Steps to reproduce



```GDScript
extends Node2D

func _ready():
	$"Icon".tex = $"source".texture

```

```GDScript
extends Sprite2D


var tex : Texture2D

func _draw():
	if tex:
#		draw_texture_rect(tex, Rect2(Vector2(), tex.get_size()), false, Color(1,1,1,1), true)
		draw_texture_rect(tex, Rect2(Vector2(), tex.get_size()/2), false, Color(1,1,1,1), true)

```


### Minimal reproduction project

[draw_texture_rect.zip](https://github.com/godotengine/godot/files/9246809/draw_texture_rect.zip)