sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: The SU (scroll up) sequence should pan the viewport down
Labels: Product-Conhost,Help Wanted,Area-VT,Issue-Bug,Priority-2

### Windows Terminal version (or Windows build number)

10.0.18363.1500, 1.10.1933.0

### Other Software

_No response_

### Steps to reproduce

1. Open a bash shell in conhost or Windows Terminal.
2. Set the window height to something smallish like 24 rows.
3. Execute the following commands: `for i in {1..100}; do echo $i; done; tput indn 10`
4. Scroll back to view the lines that have been moved off screen.

### Expected Behavior

There should be no gap in the sequence of numbers.

### Actual Behavior

There are numbers missing from the sequence at the point where they've scrolled off screen.

![image](https://user-images.githubusercontent.com/4181424/131259764-30dafeb4-327a-4fae-90df-3646a13f39cd.png)

The problem here is that there are two ways in which the `SU` escape sequence is typically implemented in Linux terminals. Most terminals, including XTerm, will pan the viewport down, as if you'd executed a linefeed at the bottom of the window. Lines at the top of the window will be moved into the scrollback buffer, and nothing is lost.

On VTE-based terminals, and Konsole, the `SU` escape sequence will just scroll the buffer contents up, constrained within the visible area. This is equivalent of deleting lines from the top of the window, so anything that scrolls off screen is lost. And that's the behavior that we're currently matching.

From a DEC VT-compatibility point of view, I don't think either interpretation is correct, so that's not a deciding factor. But the reason I think we should be matching XTerm, is because the `indn` terminfo capability is defined as `SU`, and the `ind` capability is defined as a linefeed control, so I think there is an expectation that `indn` should produce the equivalent of multiple linefeeds.

If we aren't going to do that, then we probably shouldn't be using _xterm-256color_ for our `TERM` value.
Repository: pytorch
Issue: AttributeError: module 'torchvision.models' has no attribute 'load_model'
Labels: needs reproduction,module: serialization,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->
AttributeError: module 'torchvision.models' has no attribute 'load_model'

## To Reproduce

Trying to load custom model which is saved in .h5 file. Model can be loaded via Jupyter notebook successfully and whereas getting issue if model being loaded with python file. Environment remain the same for both. 
Descriptive: Saved the code in jupyter anf python file now running both the files. Jupyter run perfectly fine where Python file gives the error.

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->
# Error:

Using TensorFlow backend.
Loading SKU predictor
Traceback (most recent call last):
  File "SKU_detect_crop.py", line 42, in <module>
    model_sku = models.load_model(model_path, backbone_name='resnet50',convert=True)
AttributeError: module 'torchvision.models' has no attribute 'load_model'


<!-- A clear and concise description of what you expected to happen. -->

## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

 PyTorch version: 1.9.0+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.10

Python version: 3.7.3 (default, Mar 27 2019, 22:11:17)  [GCC 7.3.0] (64-bit runtime)
Python platform: Linux-5.10.16.3-microsoft-standard-WSL2-x86_64-with-debian-bullseye-sid
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.18.5
[pip3] torch==1.9.0+cpu
[pip3] torchaudio==0.9.0
[pip3] torchvision==0.10.0+cpu
[conda] numpy                     1.18.5                   pypi_0    pypi
[conda] torch                     1.9.0+cpu                pypi_0    pypi
[conda] torchaudio                0.9.0                    pypi_0    pypi
[conda] torchvision               0.10.0+cpu               pypi_0    pypi

## Additional context

<!-- Add any other context about the problem here. -->


cc @mruberry
Repository: pytorch
Issue: F.conv2d: confusing error message when using uint8 input instead of float32
Labels: module: error checking,module: convolution,triaged,enhancement

`RuntimeError: expected scalar type Byte but found Float`: why does it complain about scalar type? and it should complain about Byte instead of Float, not the other way around. Also "scalar type" wording is a bit confusing, it makes me think there is some scalar and that the message talks about its type. But in fact I think it refers to a dtype of a tensor's element and refers to this element as scalar.

Also string dtype names Byte / Float are very obsolete, torch.uint8 / torch.float32 or uint8 / float32 should be the modern ones. I suggest error messages use modern dtype identifiers throughout all PyTorch.

```python
import torch
import torchvision

model = torchvision.models.resnet18(pretrained = False)

x = torch.zeros(4, 3, 128, 128, dtype = torch.uint8)

model(x)
```
```
Traceback (most recent call last):
  File "/home/.../lab/vadim/mask2cad_pytorch/bug.py", line 8, in <module>
    model(x)
  File "/home/.../lab/vadim/prefix/miniconda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/.../lab/vadim/prefix/miniconda/lib/python3.9/site-packages/torchvision/models/resnet.py", line 249, in forward
    return self._forward_impl(x)
  File "/home/.../lab/vadim/prefix/miniconda/lib/python3.9/site-packages/torchvision/models/resnet.py", line 232, in _forward_impl
    x = self.conv1(x)
  File "/home/.../lab/vadim/prefix/miniconda/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/.../lab/vadim/prefix/miniconda/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 443, in forward
    return self._conv_forward(input, self.weight, self.bias)
  File "/home/.../lab/vadim/prefix/miniconda/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 439, in _conv_forward
    return F.conv2d(input, weight, bias, self.stride,
RuntimeError: expected scalar type Byte but found Float
```
Repository: material-ui
Issue: [Stack] Set useFlexGap as default
Labels: new feature,breaking change,component: Stack

## Current Behavior 😯

When the Stack items overflow the container, they don't wrap.

## Expected Behavior 🤔

When the Stack items overflow the container, they should wrap.

## Steps to Reproduce 🕹

Steps:

1. https://codesandbox.io/s/wispy-leaf-krlx2p?file=/demo.tsx

<img width="279" alt="Screenshot 2021-08-29 at 23 09 32" src="https://user-images.githubusercontent.com/3165635/131265400-753d3275-f7a4-47e8-8f18-79d253d1d8d8.png">

## Context 🔦

Most of the Stack components that we benchmarked against in https://github.com/mui-org/material-ui/issues/18158 don't flex wrap. My assumption is that they don't because the gap is usually implemented with a margin-left but this assumption might not be accurate.

We noticed a regression linked to this behavior in https://github.com/mui-org/material-ui/issues/27973#issuecomment-907163786. It's also why there are still locations in the demos where we use `<Box sx={{ '& > :not(style)': { m: 1 } }}>` over the simpler `<Stack>` component.

On Chakra-UI's side, they solved this problem by introducing an extra [`Wrap`](https://chakra-ui.com/docs/layout/wrap) component.

For the solution of this issue, I would propose we update the Stack's implementation to wrap by default, and to use the negative margin strategy of the `Grid` to implement the gap. It seems to have been working well so far.

Would wrapping be the right thing to do by default? Figma's Stack doesn't wrap: https://www.figma.com/file/UW7KPuo4XXBsoqztC8iupE/Stack-wrap?node-id=0%3A1, so maybe this behavior should be optional. It's unclear to me. At the very least, the support for a `flexWrap="nowrap"` prop seems required.

## Your Environment 🌎

v5.0.0-beta.5
Repository: godot
Issue: Can't delete files in Web Editor
Labels: bug,platform:web,topic:editor,topic:porting,confirmed

### Godot version

3.3.3.stable

### System information

Windows 10, Google Chrome Browser

### Issue description

If I try to delete an item in a web editor project, it gives the following error.
![image](https://user-images.githubusercontent.com/34734122/131267883-e5d6fe60-3cb1-431f-8b80-533c1a676318.png)
Also, no relevant errors seem to show up in the browser console when I attempt this operation.

### Steps to reproduce

Make a new project, and watch what happens when you try to delete any of the file it comes with (icon.png, default_env.tres).

### Minimal reproduction project

_No response_
Repository: TypeScript
Issue: Only number index type is inferred from `any` computed property key
Labels: Bug,Fix Available

# Bug Report

### 🔎 Search Terms

* Computed properties
* Indexers
* Index signatures

### 🕗 Version & Regression Information

- This is the behavior in every version I tried.

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.5.0-dev.20210826#code/CYUwxgNghgTiAEEQBd5QFxoHYE8DcAUAWAPZYDOqJARgFbwC88A3gfPANpQC6mAROT4AaAgF888APSSWnAB6YsAVwC21EDF7xKMAJZYA5vFFEatDnyjUwfbniA)

### 💻 Code


```ts
declare let a: any;

const obj = {
  [a]: "s",
}; // { [x: number]: string }

obj["abc"]; // error
```

### 🙁 Actual behavior

A numeric indexer is inferred. String index access marked as invalid.

### 🙂 Expected behavior

A string indexer is expected. No error for string access.

```ts
declare let a: any;

const obj = {
  [a]: "s",
}; // { [x: number]: string }

obj["abc"]; // no error
```

I created a small PR that addresses the issue as an example but I'm still not sure if the current behavior is intentional or not.

EDIT: I'm still not sure if the inferred indexer should have a String type, perhaps a union of the allowed primitive types fits better, e.g.:
```ts
declare let a: any;

const obj = {
  [a]: "s",
}; // { [x: string | number | symbol]: string }
```
Repository: terminal
Issue: Settings that are floats like acrylicOpacity don't round trip correctly
Labels: Issue-Bug,Area-Settings,Product-Terminal,Priority-3

### Windows Terminal version (or Windows build number)

1.11.2372.0

### Other Software

Just a terminal bug, nothing else

### Steps to reproduce

Edit settings.json manually and set "acrylicOpacity": 0.7 while Terminal is running. 

Now go to the Terminal Settings UI and change something else. Note that acrylicOpacity is now 0.69999999999999996

![image](https://user-images.githubusercontent.com/2892/131270280-0fc272f5-dafa-4106-aec7-f646a9564e06.png)


### Expected Behavior

I expected floats to roundtrip with JSON numbers

### Actual Behavior

0.7 turned into "acrylicOpacity": 0.69999999999999996,
Repository: flutter
Issue: onPanUpdate doesn't trigger if map placeholder is placed inside a Stack.
Labels: framework,f: scrolling,f: gestures,P2,team-framework,triaged-framework

```dart
  Widget result = _ScrollableScope(
      scrollable: this,
      position: position,
      // TODO(ianh): Having all these global keys is sad.
      child: Listener(
        onPointerSignal: _receivedPointerSignal,
        child: RawGestureDetector(
          key: _gestureDetectorKey,
          gestures: _gestureRecognizers,
          **behavior: HitTestBehavior.opaque,**
          excludeFromSemantics: widget.excludeFromSemantics,
          child: Semantics(
            explicitChildNodes: !widget.excludeFromSemantics,
            child: IgnorePointer(
              key: _ignorePointerKey,
              ignoring: _shouldIgnorePointer,
              ignoringSemantics: false,
              child: widget.viewportBuilder(context, position),
            ),
          ),
        ),
      ),
    );
```
Repository: yt-dlp
Issue: [Feature Request] Add `--embed-auto-subs`
Labels: enhancement

## Checklist

- [x] I'm reporting a feature request
- [x] I've verified that I'm running yt-dlp version **2021.08.10**
- [x] I've searched the bugtracker for similar feature requests including closed ones

## Description

Per the discussions at #630, we need a new option so both normal subtitles and auto-generated subtitles and be embedded and deleted. I propose we add a new option `--embed-auto-subs` to download auto subtitles, embed them, and delete the files.
Repository: pytorch
Issue: Get zero when using torch.matmul and torch.dot with 1-D tensor in torch-1.9.0-cp39-none-macosx_11_0_arm64.whl
Labels: needs reproduction,triaged,module: correctness (silent),module: arm

## 🐛 Bug

When using torch.matmul and torch.dot with 1-D tensor

## To Reproduce

Steps to reproduce the behavior:
On my MacBook M1 with torch --version==1.9.0
>>> import torch
>>> x=torch.tensor([2.,2.])
>>> torch.matmul(x,x)
returns tensor(0.)

On Google Colab
import torch
x=torch.tensor([2.,2.])
torch.matmul(x,x)
returns  tensor(8.)

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

<!-- A clear and concise description of what you expected to happen. -->

## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

PyTorch version: 1.9.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 11.4 (arm64)
GCC version: Could not collect
Clang version: 12.0.5 (clang-1205.0.22.11)
CMake version: version 3.20.4
Libc version: N/A

Python version: 3.9 (64-bit runtime)
Python platform: macOS-11.4-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip] numpy==1.21.2
[pip] torch==1.9.0
[pip] torchaudio==0.9.0
[pip] torchvision==0.10.0
[conda] numpy                     1.21.2           py39h1f3b974_0    conda-forge
[conda] pytorch                   1.8.0           cpu_py39hc766e51_1    conda-forge

## Additional context

<!-- Add any other context about the problem here. -->


cc @malfet
Repository: godot
Issue: `OS.execute()` does not work with `xcopy` on Windows (release exports only)
Labels: bug,platform:windows,topic:porting,confirmed

### Godot version

3.3.3 stable

### System information

windows 10

### Issue description

I can run `OS.execute("xcopy", ["/i", "/d", "/y", source_file_path, dest_folder])` without a issue in DEBUG mode.

But it won't work in Release mode.

In release mode, the return value of the execute function is still `0`, but nothing really happens. 

### Steps to reproduce

`OS.execute("xcopy", ["/i", "/d", "/y", source_file_path, dest_folder])`

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: [feature request] torch.Generator constructor to accept seed directly
Labels: triaged,module: random

```python
# currently
rng = torch.Generator()
rng.manual_seed(seed)
perm_nd = torch.rand(shape0, shape1, generator = rng).argsort(dim = -1)

# proposed
perm_nd = torch.rand(shape0, shape1, generator = torch.Generator(seed)).argsort(dim = -1)
```

cc @pbelevich @heitorschueroff
Repository: rust
Issue: Run tests with compilter_builtins
Labels: C-enhancement

Rust CI is currently not gated on running the std tests on any targets that rely on compiler_builtins/libm. See e.g. this test failure https://github.com/rust-lang/rust/pull/85925#discussion_r654904770. This makes some sense, since none of these targets are tier 1. However, these components are used in many tier 2/tier 3 targets. This issue is to somehow run the Rust test suite with compiler_builtins in CI.

Additional background: LLVM will insert calls to various functions as part of code generation. On e.g. Linux these functions are fulfilled by linking libc, libm, libgcc, etc. For platforms that don't have these functions natively (bare metal etc.), the Rust project has developed the compiler_builtins and libm crates.

This work has been sort of approved by the infra and libs-impl teams:
* https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/meeting.202021-06-21/near/243413445
* https://rust-lang.zulipchat.com/#narrow/stream/219381-t-libs/topic/compiler-builtins.20gating
Repository: flutter
Issue: [flutter_markdown] Feature Request: Custom Widget for h1, h2 etc.
Labels: package,c: proposal,team-ecosystem,P3,p: flutter_markdown,triaged-ecosystem

I just started to look into this package and wanted to implement a custom styling (Padding and underline that requires a stack) of h1 - h6. After briefly trying out to pass a custom MarkdownBuilder to the builder function of `MarkdownBody` like this `{'h1': _H1Builder(),` I realized that I'm not able to do this because h1 - h6 are defined in `_kBlockTags`. So I can't use a custom builder here.

Is there a way how I can achieve this behavior with the current implementation?

## Proposal

My proposal would be to check if the tag is inside the builder map. If yes use the provided builder, if not use the default one for builder tags e.g.
Repository: go
Issue: runtime: hangs on windows with golang >= 1.14
Labels: OS-Windows,NeedsInvestigation,compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### Does this issue reproduce with the latest release?
Yes.
Works with v <1.14. Last working version is 1.13.15


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\IDE\Programme\go\cache
set GOENV=C:\IDE\Programme\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\IDE\Programme\go\path
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\IDE\Programme\go\go114
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\IDE\Programme\go\go114\pkg\tool\windows_amd64
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\IDE\Projects_Git\playground\go\examples\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=C:\IDE\Programme\go\tmp\go-build087442934=/tmp/go-build -gno-record-gcc-switches

</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

create a simple hello world program
hello
  - main
     -  main.go

**go run main.go** runs every time  as expected (  with go **v 1.13.15**)

But with go **v > 1.14** it runs rarely. That means 99% of the cases it hangs. 
After the hanging I can't interrupt the cmd window with Ctrl+C. So I must kill the cmd process. over the task manager. 

I had an eye to the MCAfee Scanner. I let it deinstall from our IT-Department for testing. But the result was the same. Nothing changed. 

Windows defender is disabled. 

That's my output with the -x flag

<details><summary><code>go run -x main.go </code> Output</summary><br><pre>

C:\IDE\Projects_Git\playground\go\hello\main>go run -x main.go
WORK=C:\IDE\Programme\go\tmp\go-build432668794

</pre></details>

After this output the run command hangs

### What I have testet?

1. Deinstall MCAfee 
2. Run command as Administrator
3. Set all path variables to C:\IDE\...  ( this area is not touched from MCAfee )
4. Testest not working versions 1.14 - 1.17
Repository: flutter
Issue: [web] Mouse scrolling doesn't work on iPads properly 
Labels: c: new feature,framework,engine,a: tablet,f: scrolling,platform-web,a: mouse,has reproducible steps,P3,found in release: 2.5,found in release: 2.6,browser: safari-ios,team-web,triaged-web

## Use case

iPad mouse support has come to flutter apps, but when scrolling through the same app on web, the scroll doesn’t work.

## Proposal

Add support for iPad Mouse scrolling so users can scroll through web pages without needing to use their fingers to swipe down.
Repository: godot
Issue: .tscn files blowing in size up due to multimesh data-arrays being saved when dynamically generated by a tool script
Labels: discussion,topic:editor

### Godot version

3.3.3 stable

### System information

arch linux

### Issue description

I have made myself a grass system using multimesh instancing. This means there is a multimesh instance with a few million grass blades in my scene.

No big issue, right? I mean it is dynamically generated after all ... well yes, but I do it as a tool in editor so I can get a proper preview of what I am doing when building my level.

That means all the grass positions and their properties get stored into my .tscn file.

This makes saving slow, causes regular crashes for my git gui, artificially blows up my repo size and is generally just not useful, since I just want to dynamically generate the array anyway.

I am aware, that this is kind of expected behavior, but I would still consider it to be somewhat of an unintentional side-product. A proposed solution would be to mark some values as "dynamic" so they won't get saved statically. I can imagine users being asked about this when attempting to save a unusually large entity.

### Steps to reproduce

1. Start with a blank project
2. Set up a multimesh Instance as a tool (you can follow this [grass tutorial on YouTube](https://www.youtube.com/watch?v=usdwhhZWIJ4))
3. sace the scene
4. it is now multiple megabytes, if you've spawned enough grass blades

### Minimal reproduction project
[The main scene of this tutorial project on github](https://github.com/lonegamedev/godot_botw_grass/blob/main/Scene.tscn) demonstrates the unwanted behavior. It is so large it cannot be rendered by the github webgui.