sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Image cache should have a notion of when the last time an image was rendered, and be able to evict based on that
Labels: c: new feature,framework,engine,c: performance,a: images,perf: memory,P2,team-engine,triaged-engine

Currently, if you cache an image, it will only get evicted if you manually do so (`evict` or `clear`), or if enough new images are added so (either total images or total bytes) to evict the LRU.

It would be nice to allow automated eviction of images that have not been used in a specified number of frames or seconds, perhaps only after they have been rendered once.

To do this, I think we need the following:

- Expose something on `ui.Image` about a timestamp (or frame number?) when it was last actually used in a `Scene` (or otherwise when it was last actually drawn).
- Use that information in the `ImageCache` to evict images that have not been drawn in N seconds (or frames?). We'd need some way to call this periodically. I suspect calling it every frame would be overkill, but maybe the image cache has a periodic timer or something to call it every N seconds.
Repository: terminal
Issue: Starting Directory redesign proposal
Labels: Product-Terminal,Issue-Task,Area-SettingsUI

Got some feedback on this design:
> Default option is not the first thing you see

This one can probably be ignored. The parent process option is not the default option.

> The heading for the whole block is disabled

This one is annoying. I have a feeling that a11y will not like that the header is disabled. We should make the header its own text block to avoid this.

![Starting Directory SUI](https://user-images.githubusercontent.com/11050425/105884061-681aa880-5fbc-11eb-860b-61703572901c.png)

The user also proposed a new design for this setting:
![Starting Directory Proposal](https://user-images.githubusercontent.com/11050425/105884109-79fc4b80-5fbc-11eb-81bb-ed2eb4f5c59a.png)

@cinnamon-msft Thoughts?

Somewhat related to #8805 (to track a wholistic discussion of this setting)
Repository: vscode
Issue: Tab wrap - implement different presentation so that tabs don't jump around (editor actions, decorations, dirty state)
Labels: feature-request,workbench-tabs

Testing #114827

![tab-jumping](https://user-images.githubusercontent.com/641685/105896635-0fabd100-5fe5-11eb-9743-d38f7f3f8585.gif)
Repository: vscode
Issue: workbench.externalUriOpeners protocol glob patterns don't work
Labels: feature-request,api

Testing #114962

- Have `"workbench.externalUriOpeners": { "https:*": "cool-opener" }`
- Click on a link `// https://peet.io`
- The URL is not opened with that opener
Repository: go
Issue: x/net/webdav: microsoft miniredirector fails setting properties of directories
Labels: NeedsDecision

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/kyle/.cache/go-build"
GOENV="/home/kyle/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/kyle/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/kyle/"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build009155035=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

Ran a simple wrapper around x/net/webdav. Pointed the windows mini redirector (from windows 10) at it, then tried to clone golang/net: `git clone https://github.com/golang/net.git`


### What did you expect to see?
The git clone succeed.


### What did you see instead?

```
Z:\>git clone https://github.com/golang/net.git
Cloning into 'net'...
//files.kyle-shares.agilicus.cloud@SSL/DavWWWRoot/agent/net/.git: Input/output error
```

Digging in, it's clear that the issue is due to windows trying to set properties directories such as `./.git`. 

I added some logging to the proppatch handler and found it doing these operations:

```
2021/01/26 12:16:21 Patching /net {urn:schemas-microsoft-com: Win32CreationTime}
2021/01/26 12:16:21 Patching /net {urn:schemas-microsoft-com: Win32LastAccessTime}
2021/01/26 12:16:21 Patching /net {urn:schemas-microsoft-com: Win32LastModifiedTime}
2021/01/26 12:16:21 Patching /net {urn:schemas-microsoft-com: Win32FileAttributes}
2021/01/26 12:16:21 Fail on patch: open /home/kyle/shared/net: is a directory

```
Repository: pytorch
Issue: segmentation fault in torch.nn.ReplicationPad3d/2d when padding is large
Labels: module: crash,module: nn,triaged,module: padding

## 🐛 Bug

segmentation fault in `torch.nn.ReplicationPad3d` and `torch.nn.ReplicationPad2d` when `padding` is large

## To Reproduce
~~~python
import torch
layer = torch.nn.ReplicationPad3d(padding=498444555)
model_input = torch.ones([1, 1, 1, 1, 1])
layer(model_input)
~~~

~~~python
import torch
layer = torch.nn.ReplicationPad2d(padding=1012756988)
model_input = torch.ones([2,2,2,2])
layer(model_input)
~~~

Output:
~~~python
Segmentation fault (core dumped)
~~~

## Expected behavior

expect exception message instead of crash.

## 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.8.0.dev20210126+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.4 LTS (x86_64)
GCC version: Could not collect
Clang version: Could not collect
CMake version: Could not collect

Python version: 3.7 (64-bit runtime)
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


Relevant: #50961

cc @albanD @mruberry @jbschlosser
Repository: vscode
Issue: Adjust cell diff editor height based on viewport size
Labels: freeze-slow-crash-leak,debt,diff-editor,notebook-perf

Testing #114969

Notice how the icon is blurry when clicking, that's how long it remains slow. Selection/editing in the diff editor is really slow as well, I believe this is because monaco is so large so it's creating so many dom elements.

![recording (52)](https://user-images.githubusercontent.com/2193314/105900237-9d30f600-5fd0-11eb-8915-1b1311d797cf.gif)
Repository: pytorch
Issue: [TorchScript Usability] error message when invoking __init__ of module types inside TorchScript
Labels: oncall: jit

## Problem description

Since subclasses of `torch.nn.Module` are treated as `TSInstanceClassType`, the `__init__()` method of such types is not considered TorchScript methods and thus they are not supposed to be invoked inside TorchScript. 

The error-message we issue now is counter-intuitive to users.

Test case: [test-module.py](https://github.com/penguinwu/hodgepodge/blob/master/TorchScriptStudy/bad-examples/test-module.py)

```
python test-module.py 
Eager:  5
Traceback (most recent call last):
  File "test-module.bad.py", line 23, in <module>
    m = torch.jit.script(MyModel(2))
  File "/data/users/pengwu/pytorch/torch/jit/_script.py", line 901, in script
    qualified_name = _qualified_name(obj)
  File "/data/users/pengwu/pytorch/torch/_jit_internal.py", line 870, in _qualified_name
    raise RuntimeError("Could not get name of python class object")
RuntimeError: Could not get name of python class object
```

## Desired behavior

The error message of "Could not get name of python class object" is really confusing. Can we say something like "cannot invoke __init__() method of subclasses of `torch.nn.Module` classes"?

Related to #50444

cc @gmagogsfm
Repository: pytorch
Issue: [TorchScript Usability] Earlier type checking needed for interface type
Labels: oncall: jit

## Problem description

Interface types  do not allow to define constructors, but the error message complains about return type of `__init__` not annotated

Test case: [test-interface.py](https://github.com/penguinwu/hodgepodge/blob/master/TorchScriptStudy/bad-examples/test-interface.py)
```
> python test-interface.py 
Traceback (most recent call last):
  File "test-interface.py", line 4, in <module>
    class TestInterface(torch.nn.Module):
  File "/data/users/pengwu/pytorch/torch/jit/_script.py", line 1043, in interface
    torch._C._jit_script_interface_compile(
RuntimeError: 
interface declarations must have a return type annotated.:
  File "test-interface.py", line 7
    def __init__(self):
    ~~~~~~~~~~~~~~~~~~~
        pass
        ~~~~ <--- HERE
```

## Desired behavior

The error message should simply say that interface types cannot define `__init__` methods

Related to #50444 

cc @gmagogsfm
Repository: go
Issue: Go compiler and runtime meeting notes
Labels: NeedsInvestigation,umbrella

Google's Go compiler and runtime team meets periodically (roughly weekly) to discuss ongoing development of the compiler and runtime. While not open to the public, there's been [desire by the community](https://groups.google.com/g/golang-dev/c/vQ8NDOra_CM/m/5zZKdh4kCgAJ) to learn what the compiler and runtime team is working on. While we learn what is a good format, and what works and doesn't, we will start publishing meeting minutes here.

These compiler and runtime meeting minutes are under development. We welcome feedback on content, format, level of detail, timeliness, and so on. If the minutes are helpful, please let us know. If they are less than helpful, we welcome constructive comments on how to improve them.

Notes on agenda items that address Google specific needs are elided.

**This meta-issue records minutes of Google's Go compiler and runtime meetings as issue comments, so that they can be cross-linked easily with the relevant issues. This meta-issue is for minutes only; comments that are not meeting minutes will be deleted.**
Repository: pytorch
Issue: [TorchScript Usability] tensor printout format differs from eager mode
Labels: oncall: jit,good first issue,OSS contribution wanted,TSUsability,TSRootCause:PyTorchParityGap


Test case:  [test-tensor-printout-differ.py](https://github.com/penguinwu/hodgepodge/blob/master/TorchScriptStudy/bad-examples/test-tensor-printout-differ.py)
```
> python test-tensor-printout-differ.py 
tensor([1., 1., 1., 1., 1., 1.])
Eager: True
 1
 1
 1
 1
 1
 1
[ CPUFloatType{6} ]
TorchScript: True
```

The TorchScript prints out 1-D tensors vertically instead of horizontally as in eager. Also elements of float tensor should be in float format (i.e., `1.` instead of `1`).

Please also check if multi-dimensional tensors are printed out in the right format.

Related to #50444

cc @gmagogsfm
Repository: pytorch
Issue: [TorchScript Usability] Non-intuitive error messages for user errors 
Labels: oncall: jit

Test case 1: [test-enum-mystic-error-message.py](https://github.com/penguinwu/hodgepodge/blob/master/TorchScriptStudy/bad-examples/test-enum-mystic-error-message.py) 

The test failed because `em_fn` was annotated as `@torch.script.jit`, but also supplied as input to `torch.script.jit(em_fn)`. The error message is not helpful to users. Instead, JIT should just tolerate `@torch.script.jit` instead of issuing errors. Similarly for modules that are annotated as `@torch.script.jit`but is also supplied as input to `torch.jit.trace(...)`
```
> python test-enum-mystic-error-message.py 
Traceback (most recent call last):
  File "test-enum-mystic-error-message.py", line 18, in <module>
    m = torch.jit.script(enum_fn)
  File "/home/pengwu/local/miniconda3/envs/pytorch/lib/python3.8/site-packages/torch/jit/_script.py", line 936, in script
    ast = get_jit_def(obj, obj.__name__)
AttributeError: 'torch._C.ScriptFunction' object has no attribute '__name__'
```

Test case 2: [test-enum-annotated.py](https://github.com/penguinwu/hodgepodge/blob/master/TorchScriptStudy/bad-examples/test-enum-annotated.py)

The test failed because `enum` class is annotated as `@torch.jit.script` and is treated as a custom class
```
> python test-enum-annotated.py Traceback (most recent call last):
  File "test-enum-annotated.py", line 7, in <module>
    class Color(Enum):
  File "/home/pengwu/local/miniconda3/envs/pytorch/lib/python3.8/site-packages/torch/jit/_script.py", line 913, in script
    raise RuntimeError(
RuntimeError: TorchScript classes must be new-style classes. Please inherit from 'object'.
```

Test case 3: [test-tuple.py](https://github.com/penguinwu/hodgepodge/blob/master/TorchScriptStudy/bad-examples/test-tuple.py)

Not exactly sure what is wrong with the example, perhaps it is related to decorators or passing a non-module object to `trace.jit.script()`?

```
> python test-tuple.py 
Traceback (most recent call last):
  File "test-tuple.py", line 14, in <module>
    m = torch.jit.script(MyClass(2, (1,2)))
  File "/home/pengwu/local/miniconda3/envs/pytorch/lib/python3.8/site-packages/torch/jit/_script.py", line 901, in script
    qualified_name = _qualified_name(obj)
  File "/home/pengwu/local/miniconda3/envs/pytorch/lib/python3.8/site-packages/torch/_jit_internal.py", line 793, in _qualified_name
    raise RuntimeError("Could not get name of python class object")
RuntimeError: Could not get name of python class object
```

Related to #50444

cc @gmagogsfm
Repository: vscode
Issue: Modify issue reporter description text when signed in
Labels: bug,issue-reporter

I see `Create on GitHub` while the text above still reads "You will be able to edit your issue and add screenshots when we preview it on GitHub."? Maybe should be like "you can edit the created issue to add screenshots" or something similar.

Or make this textarea a rich text editor so we can upload images here directly.

_Originally posted by @yume-chan in https://github.com/microsoft/vscode/issues/114963#issuecomment-767224246_
Repository: PowerToys
Issue: action different on two screens
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Planning-Consideration,Status-Reproducible

<!--
**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.
-->

## ℹ Computer information

- PowerToys version: v0.29.3
- PowerToy Utility: Keyboard Manager
- Running PowerToys as Admin: yes
- Windows build number: [run "winver"] 18363.1316

## 📝 Provide detailed reproduction steps (if any)

1. …Powertoys Remap shortcuts
2. …Set ctrl + # to Alt + print screen [ie print current window]
3. …Press ctrl+# with focus window on left hand (primary) screen -> works OK, focus window copied to clipboard
4. Press ctrl+# with focus window on right hand (secondary) screen -> error, both screens are copied to clipboard

### ✔️ Expected result

_What is the expected result of the above steps?_
see above
### ❌ Actual result

_What is the actual result of the above steps?_
see above
## 📷 Screenshots

_Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form_
No - description should be adequate. Behaviour is repeatable consistently
Repository: next.js
Issue: redirects don't work properly with i18n and basepath
Labels: bug,Internationalization (i18n)

**What version of Next.js are you using?**

10.0.5

**What version of Node.js are you using?**

12.16.1

**What browser are you using?**

Chrome

**What operating system are you using?**

Windows

**How are you deploying your application?**

docker / k8s

**Describe the Bug**

I'm developing a `nextjs` app that should be deployed at `/my-base-path`.  I wanted to redirect `/` to `/my-base-path`, and I setup `next.config.js` accordingly:

```js
const basePath = '/my-base-path';

const nextConfig = {
    basePath,
    env: {
        BASE_PATH: basePath,
    },
    redirects: async () => ([
        {
            source: '/',
            destination: basePath,
            permanent: false,
            basePath: false,
        },
    ])
};
module.exports = nextConfig;
```

Everything works as expected: `/` redirects to `/my-base-path`.

Once I add an `i18n` config to `nextConfig`, redirects don't function as I expect:

```js
const basePath = '/my-base-path';

const nextConfig = {
    basePath,
    env: {
        BASE_PATH: basePath,
    },
    i18n: {
        defaultLocale: 'en',
        locales: ['en', 'es'],
    },
    redirects: async () => ([
        {
            source: '/',
            destination: basePath,
            permanent: false,
            basePath: false,
        },
    ])
};
module.exports = nextConfig;
```

**Expected Behavior**

- `/` should redirect to `/my-base-path`, but `/` just returns a 404.
- `/en` redirects to `/en/my-base-path`, and `/en/my-base-path` returns a 404.
- `/my-base-path/en` renders the welcome page, but I would expect it to redirect to `/my-base-path`.
- `/my-base-path` renders the welcome page as expected. 👍 


**To Reproduce**

A repo demonstrating this behavior exists at https://github.com/ckeeney/nextjs-redirect-i18n-basepath

It's unclear to me whether the correct path structure is `/{locale}/{basePath}/{page}` or `/{basePath}/{locale}/{page}`. 

I think the former would make a more consistent URL pattern across multiple zones, but I'm a bit nervous about how complicated that would make the routing rules for the reverse proxy.  For the latter option we can simply route all traffic for each base path to it's designated nextjs app, matching on basePath as you would expect.  The former requires that the load balancer have some way of handling the locales, and I'm not sure the more predictable locale URLs are worth that trouble.
Repository: flutter
Issue: flutter test doesn't handle running out of file handles gracefully
Labels: a: tests,team,c: crash,tool,framework,engine,dependency: dart,P2,c: tech-debt,team-engine,triaged-engine

When I run the framework tests on my machine (20 cores) with `-j 80` (or some other high value), I get failures like this after a few thousand tests have run:
```
01:35 +5710 ~14 -1: loading /home/ianh/dev/flutter/packages/flutter/test/widgets/build_scope_test.dart [E]                                                                                             
  Failed to load "/home/ianh/dev/flutter/packages/flutter/test/widgets/build_scope_test.dart":
  OS error message was a not a utf8 string.
    Command: /home/ianh/dev/flutter/bin/cache/artifacts/engine/linux-x64/flutter_tester --disable-observatory --enable-checked-mode --verify-entry-points --enable-software-rendering --skia-deterministic-rendering --enable-dart-profiling --non-interactive --use-test-fonts --packages=/home/ianh/dev/flutter/packages/flutter/.dart_tool/package_config.json /tmp/flutter_tools.VCUVNK/flutter_test_listener.SXABFX/listener.dart.dill
01:36 +5714 ~14 -2: loading /home/ianh/dev/flutter/packages/flutter/test/widgets/fractionally_sized_box_test.dart [E]                                                                                  
  Failed to load "/home/ianh/dev/flutter/packages/flutter/test/widgets/fractionally_sized_box_test.dart":
  OS error message was a not a utf8 string.
    Command: /home/ianh/dev/flutter/bin/cache/artifacts/engine/linux-x64/flutter_tester --disable-observatory --enable-checked-mode --verify-entry-points --enable-software-rendering --skia-deterministic-rendering --enable-dart-profiling --non-interactive --use-test-fonts --packages=/home/ianh/dev/flutter/packages/flutter/.dart_tool/package_config.json /tmp/flutter_tools.VCUVNK/flutter_test_listener.SXKQVH/listener.dart.dill
01:36 +5715 ~14 -3: loading /home/ianh/dev/flutter/packages/flutter/test/widgets/set_state_2_test.dart [E]                                                                                             
  Failed to load "/home/ianh/dev/flutter/packages/flutter/test/widgets/set_state_2_test.dart":
  OS error message was a not a utf8 string.
    Command: /home/ianh/dev/flutter/bin/cache/artifacts/engine/linux-x64/flutter_tester --disable-observatory --enable-checked-mode --verify-entry-points --enable-software-rendering --skia-deterministic-rendering --enable-dart-profiling --non-interactive --use-test-fonts --packages=/home/ianh/dev/flutter/packages/flutter/.dart_tool/package_config.json /tmp/flutter_tools.VCUVNK/flutter_test_listener.EHVQRZ/listener.dart.dill
```

Seems like we're either running out of resources, or generally corrupting something, or maybe there's some sort of race condition? Not clear.
Repository: pytorch
Issue: -fno-omit-frame-pointer by default in our builds
Labels: module: build,triaged,enhancement

Omitting frame pointer is worth a few percent in general purpose workloads, but (1) PyTorch is not general purpose workloads and (2) it makes tools like perf not work. I suggest we should turn on frame pointer by default on our OSS builds.

cc @malfet @seemethere @walterddr
Repository: pytorch
Issue: Make it clearer when a tensor was quantized symmetrically
Labels: oncall: quantization,low priority,triaged

## 🐛 Bug

Symmetric quantization scheme is a special case of an affine quantization scheme.  Currently, the information on whether the tensor was quantized with a symmetric scheme or not is not stored on the quantized Tensor.  This is numerically correct but confusing.

## To Reproduce

1. quantize a tensor (there is no way to specify a qscheme here)
2. verify that printed qscheme on the tensor is affine, even if the intent was to use symmetric
```
>>> import torch                                                               
>>> x = torch.randn(2, 2)                                                      
>>> xq = torch.quantize_per_tensor(x, 0.1, 0, torch.qint8)                     
>>> xq                                                                         
tensor([[-0.3000, -0.4000],                                                    
        [-0.3000,  1.0000]], size=(2, 2), dtype=torch.qint8,                   
       quantization_scheme=torch.per_tensor_affine, scale=0.1, zero_point=0)   
```

At the very least, we should document this behavior.  It would be even better to store qscheme on the tensor.

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @jgong5 @Xia-Weiwen @leslie-fang-intel @dzhulgakov @vkuzo