sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/compile: slowdown in location list generation, possible remedies
Labels: ToolSpeed,NeedsDecision,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel go1.19-2a6e13843d Mon May 16 09:35:17 2022 +0000 darwin/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
GOARCH="amd64"
GOOS="darwin" and also "linux"
</pre></details>

[CL 397318](https://go-review.googlesource.com/c/go/+/397318) fixed a quadratic space consumption problem in location list generation (#51543) with a fancy data structure that shares storage for small changes to sets (and produced a 95% reduction in heap size for the problem case).  Unfortunately, [it's slower](https://perf.golang.org/search?q=upload:20220411.12), overall adding about 2% to build user time, but for the worst case, 35%.

So that's "the bug", here's discussion of causes and possible remedies.

The root cause is that the location list generation algorithm is currently performing a quadratic amount of work.  For each block, set operations linear in the number of live slots (intersection, difference) are performed.  In some cases the number of live slots is linear in program size, the number of blocks is linear in program size, and we get quadratic time.  (A "slot" is a variable or a piece of an aggregate-typed variable).

This is not necessarily required; clever preprocessing might allow us to notice that a block B's flow predecessors P and Q were both descendants of a common block R, therefore their intersection might be computed more efficiently by only considering flow from R to P and R to Q, which might be smaller.  This is handwavy, potentially complicated, and likely also involves operations with a noticeable constant factor, so pursuing this route would take a little work, and might not pay off.

A more certain plan for improving performance, though not the asymptotic cost, is to reduce the number of conversions between set representations.  The clever structures are currently used to record long-lived set data, the slots live at entrance and exit from each block.  The operations with a block are applied to a simple set representation, which is created and consumed each time a block's effects on live slots are modeled.  This is slightly trickier than just "skip the data conversions and use the shared sets everywhere" because the live data comes in two parts, one mapping slots to where they are found, and the other mapping registers to the slots that are currently bound to that register (this is necessary to know what associations are undone by assignment to a register).
Repository: go
Issue: x/crypto/ocsp: Response.ProducedAt field not honored in CreateResponse func
Labels: 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.18.2 darwin/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="auto"
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/benburkert/Library/Caches/go-build"
GOENV="/Users/benburkert/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/benburkert/pkg/mod"
GONOPROXY="github.com/benburkert/*"
GONOSUMDB="github.com/benburkert/*"
GOOS="darwin"
GOPATH="/Users/benburkert"
GOPRIVATE="github.com/benburkert/*"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.18.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.18.2/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.18.2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/3q/b_j95bxn6_n4z99hyl_8r41r0000gn/T/go-build384942112=/tmp/go-build -gno-record-gcc-switches -fno-common"
GOROOT/bin/go version: go version go1.18.2 darwin/amd64
GOROOT/bin/go tool compile -V: compile version go1.18.2
uname -v: Darwin Kernel Version 20.6.0: Tue Feb 22 21:10:41 PST 2022; root:xnu-7195.141.26~1/RELEASE_X86_64
ProductName:	macOS
ProductVersion:	11.6.5
BuildVersion:	20G527
lldb --version: lldb-1300.0.42.3
Swift version 5.5.2-dev
</pre></details>

### What did you do?

https://go.dev/play/p/lP9QCQ6Pg1a

### What did you expect to see?

exit 0

### What did you see instead?

`2009/11/10 23:00:00 resp.ProducedAt: got 2009-11-10 23:00:00 +0000 UTC, want 2009-11-10 22:50:00 +0000 UTC`
Repository: deno
Issue: Deno test panicked when use Deno.run on windows
Labels: bug,testing

I use Windows 10 in zh-CN locale. Under this circumstance, the `ping` command will output text in GBK encoding. (When I switch code page to 65001, the problem disappeared. (ping command will output in English))
Use `deno run` is ok.
Code:
```typescript
Deno.test('a', async ()=>{
        await Deno.run({cmd: ['ping', '8.8.8.8']}).status();
})
```
Error:
```
Platform: windows x86_64
Version: 1.22.0
Args: ["C:\\Users\\***\\scoop\\apps\\deno\\current\\deno.exe", "test", "--allow-all", ".\\tt.ts"]

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: InvalidData, message: "Windows stdio in console mode does not support writing non-UTF-8 byte sequences" }', cli\tools\test.rs:383:41
stack backtrace:
   0:     0x7ff644c1b085 - <unknown>
   1:     0x7ff644184c4a - <unknown>
   2:     0x7ff644c0e9d9 - <unknown>
   3:     0x7ff644c1ee42 - <unknown>
   4:     0x7ff644c1ea46 - <unknown>
   5:     0x7ff64410cc1a - <unknown>
   6:     0x7ff644c1f886 - <unknown>
   7:     0x7ff644c1f5f3 - <unknown>
   8:     0x7ff644c1f559 - <unknown>
   9:     0x7ff644c1f514 - <unknown>
  10:     0x7ff645d07a05 - CrashForExceptionInNonABICompliantCodeRange
  11:     0x7ff645d07d93 - CrashForExceptionInNonABICompliantCodeRange
  12:     0x7ff643cc39e2 - <unknown>
  13:     0x7ff643fea94a - <unknown>
  14:     0x7ff643fe9b64 - <unknown>
  15:     0x7ff643d454c6 - <unknown>
  16:     0x7ff643fe983b - <unknown>
  17:     0x7ff643fea3c0 - <unknown>
  18:     0x7ff643cc26e8 - <unknown>
  19:     0x7ff643cc16a1 - <unknown>
  20:     0x7ff643cc1191 - <unknown>
  21:     0x7ff643cc12a4 - <unknown>
  22:     0x7ff645cb934c - CrashForExceptionInNonABICompliantCodeRange
  23:     0x7ffc3f177034 - BaseThreadInitThunk
  24:     0x7ffc40542651 - RtlUserThreadStart
```
Repository: pytorch
Issue: General MPS op coverage tracking issue
Labels: feature,triaged,tracker,module: mps

### This issue is to have a centralized place to list and track work on adding support to new ops for the MPS backend.

[**PyTorch MPS Ops Project**](https://github.com/users/kulinseth/projects/1/views/1) : Project to track all the ops for MPS backend. There are a very large number of operators in pytorch and so they are not all yet implemented. We will be prioritizing adding new operators based on user feedback. If possible, please also provide link to the network or use-case where this op is getting used.

As Ops are requested we will add " *To Triage*" pool. If we have 3+ requests for an operation and given its complexity/need the operation will be moved "*To be implemented*" pool. If you want to work on adding support for such op, feel free to comment below to get assigned one. Please avoid pickup up an op that is already being worked on tracked in "*In progress*" pool. 

[Link to the wiki for details](https://github.com/pytorch/pytorch/wiki/MPS-Backend) on how to add these ops and example PRs.

[**MPS operators coverage matrix**](https://qqaatw.github.io/pytorch-mps-ops-coverage/) - The matrix covers most of the supported operators but is not exhaustive. **Please look at the `In vx.x.x` column, if the box is green, it means that the op implementation is included in the latest release; on the other hand, if the box is yellow, it means the op implementation is in the nightly and has not yet included in the latest release.** Before you comment below, please take a look at this matrix to make sure the operator you're requesting has not been implemented in nightly.  More details can be found on the [readme](https://github.com/qqaatw/pytorch-mps-ops-coverage).

cc @kulinseth @malfet @DenisVieriu97 @jhavukainen
Repository: vscode
Issue: Scrollbar Minimap and visible code are out of sync when CodeLens is used
Labels: bug,editor-minimap

Issue Type: <b>Bug</b>

The scroll position and highlighted part of the minimap get out of sync with the visible editor code when CodeLens lines are present in the file and "editor.minimap.size" is set to "fit" or "fill.

Steps to reproduce:

Set "editor.minimap.size" to "fit" or "fill".

Open a file with many CodeLens lines in one part and few in the remaining part. E.g. a class with many attributes and then a long method.
Notice how the highlighted part of the minimap does not match the visible portion of code in the editor.

Remarks:

To observe the effect better, set the "editor.codeLensFontSize": 72 to a very large font size to increase the discrepancy.

It can then be seen that the CodeLens lines are omitted from the minimap, which creates a discrepancy between what is rendered in the minimap and the code editor.
So maybe instead of trying to fix the scrollbars (like in 53eac52308c4611000a171cc7bf1214293473c78) it would be better to include the CodeLens lines in the minimap. A blank line with the correct height would be my suggestion.

When "editor.minimap.size" is set to "proportional" the highlighted part of the minimap matches the visible code, but the switching size creates jitter upon scrolling.

This issue was already reported in #111499 , but only the "proportional" mode seems to be fixed (and got jitter upon scroll instead).

VS Code version: Code 1.67.2 (c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5, 2022-05-17T18:15:52.058Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

Extensions: none
<!-- generated by issue reporter -->
Repository: flutter
Issue: [google_maps_flutter_web] Add missing MapOptions parameters
Labels: c: new feature,p: maps,platform-web,package,c: proposal,P3,c: parity,has partial patch,team-web,triaged-web

## Use case

On Flutter WEB, I would like to be able to enable/disable (via GoogleMap constructor params or whatever) those MapOptions parameters:
mapTypeControl
fullscreenControl
streetViewControl

that display additional buttons onto the Map.
![image](https://user-images.githubusercontent.com/1877340/169121734-c7a6422e-a11f-4f44-8904-fcd9d274aa2a.png)

## Proposal

In the code of the package  it is written (more than 15 months ago):
```
  // These don't have any rawOptions entry, but they seem to be off in the native maps.
  options.mapTypeControl = false;
  options.fullscreenControl = false;
  options.streetViewControl = false;
```

I have switched them all to "true" and it is working fine (= enables all the buttons and gives the previous screenshot). I tried each button and everything is working fine. So, it seems that the comment in the code is not true anymore.

Thanks!
Repository: flutter
Issue: [Web]`AssetImage` opacity doesn't work on the web with HTML renderer
Labels: framework,platform-web,a: images,e: web_html,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-web,triaged-web

Sample code to reproduce

```dart
import 'package:flutter/material.dart';

class Test extends StatelessWidget {
  const Test({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Container(
      decoration: const BoxDecoration(
        image: DecorationImage(image: AssetImage(sampleImage), opacity: 0.5),
      ),
    );
  }
}
```

This widget renders correctly on IOS app, Android App, web browser on computer.
This widget renders with opacity 1 on web browser on Android or IOS devices
Repository: flutter
Issue: Provide a way for iOS plugins to know what window/view to interact with
Labels: c: new feature,platform-ios,engine,P2,a: plugins,team-ios,triaged-ios

Several of our 1P plugins present view controllers over the Flutter view; `GIDSignIn` needs this information, for example. Currently, we do this using `UIApplication.sharedApplication.keyWindow`, but in iOS 13 `keyWindow` is deprecated because of the introduction of scenes on iPads.

To make Flutter scene-friendly, we should provide an alternate way of getting that information. On the macOS embedding, for instance, I added a way to get the `NSView` of the Flutter content via the plugin registrar, which allows plugins to get the window they are part of for things like showing sheets. (I keep finding 3P plugins that ignore that and use the key window instead, but 🤷🏻 ). We should consider doing the same for iOS, or providing some alternate solution.

/cc @jmagman
Repository: transformers
Issue: Google's Trillson Audio Classification
Labels: New model,Good Second Issue

### Model description

The TRILLsson models are described in the publication TRILLsson: Distilling Universal Paralingistic Speech Representations. From audio, they generate generally-useful paralinguistic speech representations (paralinguistics are aspects of speech other than text, such as emotion, language identification, synthetic or real, etc). These representations are smaller, faster, and publicly available versions of the state-of-the-art CAP12 embeddings, which are described in [Universal Paralinguistic Speech Representations Using Self-Supervised Conformers](https://arxiv.org/abs/2110.04621) (ICASSP 2022).

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Google recently has done some very nice work on better audio / speech representations and distilled audio / speech representations. See:
- https://arxiv.org/abs/2110.04621
- https://arxiv.org/abs/2203.00236

Some of the distilled models are open-sourced and could be made more available via an integration to HuggingFace's Transformer library.

E.g. the following notebook shows how the weights can be loaded and run with publicly accessible model code:
https://colab.research.google.com/drive/1-D6pyxFyquIO8pss_lngL_mncHa3kAAT?usp=sharing

The relevent models to add are:
- https://tfhub.dev/google/nonsemantic-speech-benchmark/trillsson3/1 and
- https://tfhub.dev/google/nonsemantic-speech-benchmark/trillsson2/1

and the relevant code is publicly available: https://github.com/google-research/google-research/tree/master/non_semantic_speech_benchmark

The google colab shows exacty how the model can be run and debugged in TF.
Repository: godot
Issue: Vulkan: Visual artifacts/glitching on splash screen if a singleton has a parser error [AMD on Linux]
Labels: bug,platform:linuxbsd,topic:rendering,topic:porting,regression

### Godot version

v4.0.alpha.custom_build [838cb598e]

### System information

Arch on 5.15.40-1-lts

### Issue description

System Information:
```
OS: Arch Linux x86_64
Kernel: 5.15.40-1-lts
CPU: AMD Ryzen 9 5950X
GPU: AMD ATI Radeon RX 6800 XT
Display Server: Reproducible on both Wayland and X11
```

https://user-images.githubusercontent.com/14253836/169154621-77f9ac58-2880-47d8-b1e4-bc479629c87d.mp4

Painfully cool examples:

![image](https://user-images.githubusercontent.com/14253836/169154707-6d8c96e5-897e-49bf-81a5-57b678be1386.png)
![image](https://user-images.githubusercontent.com/14253836/169154723-ab93a06f-5b15-45cf-bf2c-e5fddcf05c94.png)


### Steps to reproduce

1) Add a script as an AutoLoad.
2) Manipulate the script such that it throws a parser error (e.g. `1/0`).
3) Run the project in the editor


### Minimal reproduction project

[test2.zip](https://github.com/godotengine/godot/files/8720885/test2.zip)
Repository: flutter
Issue: [google_maps_flutter] ios, avoid sending message to self in init
Labels: platform-ios,p: maps,package,P2,team-ios,triaged-ios

The `FLTGoogleMapController`'s init method has several places sending message to `self` in the middle of the init method.
See :https://github.com/flutter/plugins/blob/main/packages/google_maps_flutter/google_maps_flutter/ios/Classes/GoogleMapController.m#L70-L132

We should refactor and avoid sending messages to self in the middle of the init methods.
Repository: pytorch
Issue: `torch.utils.benchmark.examples.blas_compare` can not be parsed by Python-3.7 runtime
Labels: triaged,module: benchmark

### 🐛 Describe the bug

Attempt to `python3 -c "import torch.utils.benchmark.examples.blas_compare"` fails with
```
File "/opt/conda/lib/python3.7/site-packages/torch/utils/benchmark/examples/blas_compare.py", line 35, in <module>
     _WORKER_POOL: queue.Queue[Tuple[str, str, int]] = queue.Queue()
 TypeError: 'type' object is not subscriptable
```
See [this](https://github.com/pytorch/pytorch/runs/6493890839?check_suite_focus=true) for example

### Versions

nightly
Repository: deno
Issue: REPL evaluation returning a lone surrogate results in an "Unterminated string literal" error
Labels: bug,repl

```
❯❯❯ deno
Deno 1.21.3+037466e
exit using ctrl+d or close()
> "\uDE00"
Uncaught "Unterminated string literal"
> 
```

This is distinct from the panic in #12226, and is much harder to fix. It is currently blocked on https://github.com/serde-rs/json/issues/890.
Repository: PowerToys
Issue: Ability to drag Custom Layouts around in the Fancy Zones Editor and/or Grouping of Layouts with a user-defined Header
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

1. Ability to drag custom layouts around to change their order in the Fancy Zones Editor
2. would be nice to be able to group them as well (and be able to drag within and between them)

### Scenario when this would be used?

It is common to make variations on a theme .. like "wide left" (2 pane) and another layout "wider left".. maybe you made this second one much later, so it is many custom layouts away from the one it was duplicated from. It would be nice to move them next to each other.

Similarly, it would be nice to group related layouts together.. for example... you have a few layouts related to researching.. a few related to coding.. a few related to managing your music collection.. chances are you didn't create all related ones at the same time, so it would be nice to group them together.

OR

why not just allow for selecting related layouts and then right click, create a new group (i.e. row) with a name that you give them? and be able to drag layouts around within groups or between them?

### Supporting information

_No response_
Repository: pytorch
Issue: `Could not start gRPC server` flakiness in XLA tests
Labels: triaged,module: xla

For some examples, see [here](https://hud.pytorch.org/failure/RuntimeError%3A%20tensorflow%2Fcompiler%2Fxla%2Fxla_client%2Fxrt_local_service.cc%3A56%20%3A%20Check%20failed%3A%20tensorflow%3A%3ANewServer(server_def%2C%20%26server_)%20%3D%3D%20%3A%3Atensorflow%3A%3AStatus%3A%3AOK()%20(UNKNOWN%3A%20Could%20not%20start%20gRPC%20server%20vs.%20OK)). 

Can we add some retries or something to this test?

cc @bdhirsh
Repository: godot
Issue: Camera3D project_* methods not accounting for frustum offset
Labels: bug,topic:core,confirmed,topic:3d

### Godot version

4.0.dev

### System information

Arch Linux 5.16.14

### Issue description

When using a `Camera3D`'s `project_ray_origin`, `project_ray_normal`, `project_position` and `unproject_position` to translate between world and screen coordinates, if the camera is set to frustum projection, the projected position does not match the screen position.
In this example I set up two viewports, one with a frustum camera and an one with an overview perspective camera for debugging. I had a simple script converting positions from `InputEventMouseButton`s into ray origin and normal, then using a `RayCast3D` to intersect with the scene (the three prisms have static bodies)
![1652918820](https://user-images.githubusercontent.com/8162008/169178751-a3d30a61-eaf3-49c6-af17-11d027eb55f8.png)
The expected result (and the one I got with perspective projection, orthographic projection and frustum projection with no offset) is that the green cylinder (that indicates the world position gotten from the conversion) should point to the box in the back, but instead it points at the wall.

Looking into the source, the error is obvious. None of the methods handles frustum projections, there's just a 
```c++
if (mode == PROJECTION_PERSPECTIVE) {
    // stuff for perspective
} else {
    // stuff for orthographic (and implicitly frustum)
}
```
or
```c++
if (mode == PROJECTION_ORTHOGRAPHIC) {
    // stuff for orthographic
} else {
    // stuff for perspective (and implicitly frustum)
}
```

### Steps to reproduce

Set up a 3D scene with a frustum camera with a non-zero offset. Set up a script that uses a world-space position generated from to screen positions using one of the aforementioned methods. I recommend moving a 3D object to the position gotten from a click, as it's the easiest way to see the difference.

### Minimal reproduction project

Sorry for the messy layout. It's the same project as the screenshot.
Change the settings of the `Camera3D` in `Node3D.tscn` to test that indeed it does work on

[debug_program.zip](https://github.com/godotengine/godot/files/8721829/debug_program.zip)
Repository: pytorch
Issue: `addmv, mv` will trigger INTERNAL ASSERT FAILED when input requiring grad
Labels: module: autograd,triaged,actionable

### 🐛 Describe the bug

`addmv` will trigger INTERNAL ASSERT FAILED when input requiring grad

```python
import torch

def addmv(input):
    mat = torch.randint(-1, 1, [2, 3], dtype=torch.int8)
    vec = torch.randint(-1, 1, [3], dtype=torch.int8)
    return torch.addmv(input, mat, vec)

input_normal = torch.rand([2], dtype=torch.float32)
addmv(input_normal)
print('normal pass')
# normal pass

input_with_grad = input_normal.clone().requires_grad_()
addmv(input_with_grad)
# RuntimeError: isDifferentiableType(variable.scalar_type())INTERNAL ASSERT FAILED at "/Users/distiller/project/pytorch/torch/csrc/autograd/functions/utils.h":65, please report a bug to PyTorch. 
```

`mv` will trigger INTERNAL ASSERT FAILED when input requiring grad

```python
import torch

vec = torch.randint(0, 8, [10], dtype=torch.uint8)
tensor = torch.rand([0, 10], dtype=torch.complex64, requires_grad=True)
torch.mv(tensor, vec)
# RuntimeError: isDifferentiableType(variable.scalar_type()) INTERNAL ASSERT FAILED at "/opt/conda/conda-bld/pytorch_1654585902583/work/torch/csrc/autograd/functions/utils.h":65, please report a bug to PyTorch.
```

### Versions

pytorch: 1.11.0

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7