sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Inconsistent string auto-complete when inside/outside string
Labels: Bug

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

inconsistent string auto complete intellisense suggestions tuple position

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->

This is the behavior in every version I tried, and I reviewed the FAQ for entries about auto-complete / suggestions.

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/CYUwxgNghgTiAEAzArgOzAFwJYHtVJxwAoAPALngG0AiEqagGnloCNHmSxqBdASgoBuOLMACwAKESEileHwkB6BfBUA9eJhgQA1AGcADlDAJdACxwB3XR3pNW7WlwlTiNHr0XKV8dZp0GjE3MrG2oJIA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
declare function foo(x: ["xa", "xb", "xc"]): void
foo([ ])
//   ^ ctrl+space shows "xa", "xb", "xc"
foo([""])
//    ^ ctrl+space shows "xa"
```

### 🙁 Actual behavior

The suggestion list outside of the string ignores the tuple position and suggests all members, while the suggestion list inside of a string suggests only the string for that position.

### 🙂 Expected behavior

Both suggestion lists would show `"xa"` but not `"xb"` or `"xc"`.
Repository: animate.css
Issue: Improve Animations
Labels: improvement,v5

## Back Entrances and Exits

We could make them smoother and improve its final steps. They look a bit stiff and shy at the moment.

## Jack in the Box

It could be a bit more "exaggerated".

## Zoom outs

Could be a bit clearer and be more "exaggerated" too.

## Slide Entrances and Exits

Could use more of the Squash and stretch principle.

It would be good to review all the animations, code and animation wise as there's room for improvement.
Repository: animate.css
Issue: Create an easy to use and share playground
Labels: improvement,help wanted,v5

Right now it's a bit of an effort to test out all of the animations and work on them. It's 2022, we have better options, let's improve this and make our lives and collaboration easier.

A few things to keep in mind:
- It should be easy to use
- It should have a few different "shapes" for testing out the animations. Right now our playground/website only shows a title with the animations which doesn't help us to detect a few weird things that can happen with different shapes.
- It should be easy to "fork"
- It should be online
Repository: material-ui
Issue: [Table] Low performance when rendering modest size Table
Labels: performance,component: table

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

I'm writing a component which is basically a selectable grid, implemented using `Table`. User can select the cells in a row by pressing and dragging the mouse over them. [Example code here](https://codesandbox.io/s/mui-table-styled-v336gu?file=/src/MyTable.js)

When the number of rows is greater than 5, the selection is very slow to response. Profiling results show that the renders of `MyTable` component may take around half second or more, when the table size increases.
![image](https://user-images.githubusercontent.com/511857/166474847-2ddb89b7-8dea-4408-9a8d-c70c4490be23.png)
The re-render seems to be initiated due to a change in `ownerState` props, as shown below:
![image](https://user-images.githubusercontent.com/511857/166475084-7e1ad6cd-8ee9-491c-b130-f1740e1e517a.png)
In this capture, there's also a change in `sx` due to the styling applied to the cells which are selected, but I have run another tests removing the selection styling updates, and the `ownerState` change is always there.



### Expected behavior 🤔

I have implemented the same component but using plain HTML tables, and the performance is as expected. [Example code here](https://codesandbox.io/s/mui-table-unstyled-tyw5jz?file=/src/MyTable.js)

### Steps to reproduce 🕹

Steps:

1. Run implementation with `Table`: [sample code](https://codesandbox.io/s/mui-table-styled-v336gu?file=/src/MyTable.js)
2. Run implementation with `<table>` to compare: [sample code](https://codesandbox.io/s/mui-table-unstyled-tyw5jz?file=/src/MyTable.js)



### Context 🔦

I'm new to React and MUI, so it may be that I'm doing something blatantly wrong (although I took precautions and investigated before opening this issue 😄). But overall it seems to me that there's some undesired change triggering unnecessary renders.


### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
System:
    OS: Windows 10 10.0.19043
  Binaries:
    Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 8.5.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 100.0.4896.127
    Edge: Spartan (44.19041.1266.0), Chromium (101.0.1210.32)
  npmPackages:
    @emotion/react: ^11.9.0 => 11.9.0
    @emotion/styled: ^11.8.1 => 11.8.1
    @mui/base:  5.0.0-alpha.78
    @mui/icons-material: ^5.6.2 => 5.6.2
    @mui/material: ^5.6.3 => 5.6.3
    @mui/private-theming:  5.6.2
    @mui/styled-engine:  5.6.1
    @mui/system:  5.6.3
    @mui/types:  7.1.3
    @mui/utils:  5.6.1
    @types/react:  18.0.8
    react: ^18.1.0 => 18.1.0
    react-dom: ^18.1.0 => 18.1.0
    typescript:  4.6.4
```
</details>
Repository: go
Issue: runtime: check use of osyield in signal handlers
Labels: NeedsInvestigation,compiler/runtime

The SIGPROF handler uses `runtime.osyield` to spin while waiting for exclusive access to the profiling buffer. In the discussion of https://go.dev/cl/400795, @mknyszek questioned whether that was safe. I'm not sure that it is.

I see that on many OSes (Linux, FreeBSD, NetBSD, OpenBSD, Solaris, Dragonfly) that function does a `sched_yield(2)` syscall, which is not one of the syscalls listed in signal-safety(7) as being required by POSIX to be safe to call from signal handlers.

On top of that, the change in Go 1.18 to use `timer_create(2)` on Linux for CPU profiling means that many SIGPROF deliveries are now thread-targeted (versus `setitimer(2)`'s process-targeted signals), which may have opened the possibility of a process handling multiple overlapping SIGPROF deliveries (on separate threads).

Let's make sure the `runtime.osyield` calls are safe in that context, and write down why.

Here's some of the code in question: https://github.com/golang/go/blob/go1.18.1/src/runtime/cpuprof.go#L123-L129
Repository: vscode
Issue: Cmd + K, Cmd + I should ideally trigger all hovers
Labels: feature-request,accessibility,workbench-hover

`Cmd + K, Cmd + I` already triggers the editor hover.
For consistency it should also trigger the custom hover in the workbench. This command should also pass the focus to the custom hover for accessibility reasons.
Repository: go
Issue: runtime: improve the "best effort" of the execution tracer's CPU sample delivery
Labels: NeedsInvestigation,compiler/runtime

The work in https://go.dev/cl/400795 (proposed for the Go 1.19 cycle) to add CPU profile samples to the execution tracer's output relies on the process generating at least a modest stream of other traceable events. If the process's goroutines as a group use more than 19 thread-seconds of CPU time before any individual P flushes a traceBuf (or before tracing ends), the profiling buffer will overflow and (silently) drop records before the goroutine calling `runtime.ReadTrace` wakes up to drain it.

There may be a better way to move profile samples from the profBuf into traceBufs (such as launching a goroutine to drain the profBuf).
Repository: go
Issue: net/http: TestRequestLimit_h2 failure with `didn't expect to get request in Handler`
Labels: NeedsInvestigation

```
--- FAIL: TestRequestLimit_h2 (0.48s)
    serve_test.go:2969: didn't expect to get request in Handler
FAIL
FAIL	net/http	11.329s
```

`greplogs -l -e 'didn'\''t expect to get request in Handler'`
[2022-05-02T14:54:05-349cc83/solaris-amd64-oraclerel](https://build.golang.org/log/9ef0677aafd851270d0fa41479b1d3b110b5a561)

Leaving in the backlog because this has only been observed once, although since that builder is very slow (CC @rorth) I suspect that the failure mode is timing-sensitive and platform-independent.

(CC @neild)
Repository: excalidraw
Issue: Disable updating locked elements
Labels: discussion,element locking

When an element is locked, I think we should disable any kind of update (eg changing background, stroke, etc). Right now we disable interaction (eg moving, resizing) but we should also disable any kind of properties update as the element is locked.

Figjam, Miro, whimisical as well don't allow updating elements unless unlocked.

As a user, I think locking means "Disable any kind of updates related to element" and not just updates related to element dimensions/position
Repository: go
Issue: x/build: OOM while compiling on solaris-amd64-oraclerel
Labels: OS-Solaris,Builders,NeedsInvestigation

`greplogs --dashboard -md -l -e '\Asolaris-amd64(.*\n)*# .*\nfatal error: .*(?:out of memory|cannot allocate memory)' --since=2022-01-01`
[2022-05-02T20:18:15-8375b54/solaris-amd64-oraclerel](https://build.golang.org/log/c669d551ce9f1bbb0b6d4b9b36742610e88930e3)
```
# net/http_test [net/http.test]
fatal error: runtime: cannot allocate memory
…
FAIL	net/http [build failed]
```

Given the various other resource-exhaustion issues with this builder (such as #51443), I suspect that this is a builder issue (#52433 notwithstanding). (attn: @rorth)
Repository: excalidraw
Issue: Enable selection of single elements  to unlock when locked for better UX
Labels: discussion,element locking

As per UX, I feel it's not intuitive to disable selection and I am not sure why we are disabling selection, even when you right-click the element it gets selected.
As per the flow, I select an element -> right-click, -> lock, hence I am expecting then when I click on an element again it will select it, and then I can either use the context menu/shortcut to unlock it.
Miro, Figjam , whimisical  allow the selection of lock elements and show a visual indicator to unlock as well which makes it more intuitive.
Hence I would suggest we allow selection and show some indicator (eg lock icon) that makes it clear that the element is locked so the user needs to unlock it(clicking on lock icon will unlock the element).

And this is most helpful during collaboration where users don't know which elements are locked and which aren't
And one more thing, disabling selection+ not showing indicator might look like a bug when someone tries to interact with the elements (eg move, resize) unless the user is aware of the lock functionality in Excalidraw

In case we want to disable selection then I suggest showing some indicator that makes it more clear how to unlock and why the selection is disabled but to align with other tools I think we should allow selection + some indicator to unlock when selected as well.
Repository: go
Issue: runtime,cmd/compile: SIGSEGV on netbsd-arm64-bsiegert during bootstrapping
Labels: OS-NetBSD,NeedsInvestigation,arch-arm64,compiler/runtime

`greplogs -l -e '/compile: signal: segmentation fault' --since=2022-01-01`
[2022-05-02T16:21:47-eb4f295-0fdca72/netbsd-arm64-bsiegert](https://build.golang.org/log/268ae7a471439bc52564bd984de09f68154aa178)
[2022-01-06T19:06:36-5b0dc2d-378766a/netbsd-arm64-bsiegert](https://build.golang.org/log/002bd6993330c869cdbcbe5424561d135aa9cb47)

(CC @golang/netbsd, @golang/arm; attn @bsiegert)
Repository: pytorch
Issue: Supporting torch.tensor.apply_ over GPU
Labels: module: cuda,triaged

### 🚀 The feature, motivation and pitch

I came across a problem in my project where I needed that `apply_` function. It is interesting to see that it isn't supported over GPU. 

I was wondering if it is possible to extend it to GPU, perhaps for pure lambdas to begin with. 

If there are no known issues directly stopping this from happening, I would like to work on this. 

I feel that extending it to GPU for pure lambda callbacks is a good starting point. 

PS: Any pointers on the issue will be appreciated as my experience with Pytorch has been strictly with its application interface as of now :D 

### Alternatives

_No response_

### Additional context

_No response_

cc @ngimel
Repository: pytorch
Issue: [checkpoint] Handle overlapping storage during save and load
Labels: oncall: distributed,triaged,sharded_tensor

### 🚀 The feature, motivation and pitch

When loading a checkpoint, we should check whether any of the tensors have overlapping storage and, if so, we're loading data from different storage_keys. We should eliminate the superfluous load is such cases.

A similar check should be performed when saving a checkpoint and use that to reduce the amount of IO done.

 

### Alternatives

_No response_

### Additional context

_No response_

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: pytorch
Issue: [checkpoint] Stable file format for checkpoints
Labels: oncall: distributed,triaged,sharded_tensor

### 🚀 The feature, motivation and pitch

We need to provide a stable file format at some level for checkpoints so users can, at the very least, query which PyTorch version is necessary to correctly load it.



### Alternatives

_No response_

### Additional context

_No response_

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: pytorch
Issue: Bug in dataloader iterator found by mypy
Labels: module: dataloader,triaged

While upgrading mypy, found a call to `_BaseDataLoaderIter.reset()` that appears to trivially fail ([link](https://github.com/pytorch/pytorch/blob/543eaac415bfba59e648a3da8be5c4f964f9bc6e/torch/utils/data/dataloader.py#L557)), as it does not provide a required positional argument.

cc @SsnL @VitalyFedyunin @ejguan @NivekT
Repository: pytorch
Issue: Default repr of __get__ methods in __torch_function__ is bad
Labels: triaged,module: __torch_function__

### 🐛 Describe the bug

I got a function in `__torch_function__` that I couldn't handle. I wanted to print it out to see what was up:

```
>>> repr(func)
"<method-wrapper '__get__' of getset_descriptor object at 0x7f1208602a40>"
```

Completely useless. In this case, I needed to call `repr(func.__self__)` to get useful information about getset_descriptor.

This is actually sort of the inverse problem as https://github.com/pytorch/pytorch/issues/76534 where for a more useful bound method print, we want CPython to produce the repr of the self object cc @hameerabbasi @rgommers @peterbell10 @pmeier 

### Versions

master
Repository: PowerToys
Issue: Instant translator
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Given that when selecting any text anywhere, web, desktop, work, excel at the end of the selection then translate to a configured language of PowerToys.

### Scenario when this would be used?

Any location whether on the web or desktop application when text is selected.

### Supporting information

_No response_
Repository: pytorch
Issue: Quantization in Libtorch
Labels: oncall: quantization,low priority,triaged

### 🚀 The feature, motivation and pitch

I am working on a Libtorch program that is heavily performance constrained, and I was hoping to run inference using quantization to speed up the model and reduce memory usage. I would like for Libtorch to support static and dynamic quantization just like Pytorch, both for creating quantized models and using quantized torchscript models.

### Alternatives

I tried quantizing the model in Python and then using that exported torchscript .pt file in Libtorch, but that gave a `RuntimeError: Didn't find engine for operation quantized::conv2d_prepack NoQEngine` (I get the same error trying to import that model in Pytorch). I am using Windows 10.

### Additional context

_No response_

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: flutter
Issue: Deprecate and remove synthetic `package:flutter_gen`
Labels: c: new feature,tool,a: internationalization,P1,team-tool,triaged-tool

Currently, `flutter_gen` is a virtual package we generate to provide certain functionality (e.g. [internationalisation](https://docs.flutter.dev/development/accessibility-and-localization/internationalization#adding-your-own-localized-messages)). Developers have to import that package into their app. The package itself is not listed in their app's `pubspec.yaml`, though. Instead, the `flutter_gen` package is made available by a rewrite of the package config file itself.

This "hack" has caused issues with multiple tools in the past, e.g.:

* build_runner (https://github.com/dart-lang/build/issues/2835)
* linter (specifically, the `depend_on_referenced_packages ` lint, https://github.com/dart-lang/sdk/issues/58690)
* Dart Code (https://github.com/Dart-Code/Dart-Code/issues/3948)
* pub (mentioned in https://github.com/dart-lang/sdk/issues/58690)

It's expensive for tooling to have to handle package:flutter_gen as a special case and it's easy to overlook that special support for it is needed resulting in a sub-par user experience.

We should rethink whether there are better ways to support the functionality that `flutter_gen` is currently providing that's more aligned with the dart ecosystem and its tooling. Maybe the upcoming support for [macros](https://github.com/dart-lang/language/blob/master/working/macros/feature-specification.md) in Dart can help with that).
Repository: electron
Issue: [Feature Request]: Window always-on-bottom (inverse of top-most)
Labels: enhancement :sparkles:,component/BrowserWindow

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Hello everyone,
I would like to ask you if there is any way to set the window to be "**always-on-bottom**" (inverse of top-most).
And if not, would it be possible to implement this feature?



### Proposed Solution

I am creating a system monitor application for which I would like it to work as a widget. 
![Screenshot from 2022-05-03 20-02-41](https://user-images.githubusercontent.com/46067689/166515740-3b243b7b-c414-4e68-9686-2a85c678f9e4.png)




### Alternatives Considered

I tried to follow these solutions:
1) https://stackoverflow.com/questions/39435066/change-system-z-order-of-browserwindow-in-electron-possible
2) this module https://github.com/armaldio/electron-bottom-most

### Additional Information

_No response_
Repository: pytorch
Issue: hanging process with init_process_group(backend='mpi') cannot be killed 
Labels: oncall: distributed

## Issue description

Running mpirun with torch.distributed hangs. When parts of ranks raised error intentionally and the others are doing allgather, those who raised error cannot be killed and were waiting for all other processes to exit. On the other hand, the process that is doing allgather seems to be waiting for other processes too. This leads to all process hanging eventually.

## Code example

```
import torch.distributed as dist
import torch
import time
import sys
import os

dist.init_process_group(backend='mpi')
rank = dist.get_rank()
size = dist.get_world_size()
pid = os.getpid()

tensor_list = [torch.zeros(1, dtype=torch.int64) for _ in range(size)]
tensor = torch.arange(1, dtype=torch.int64) + rank

if rank == 0:
    print(f"Allgather: PID[{pid}]")
    dist.all_gather(tensor_list, tensor)
else:
    # to kill a process
    print(f"Runtime Error: PID[{pid}]")
    raise RuntimeError
    # sys.exit(-1)
    # dist.destroy_process_group() 
```

Error msg:
```
Runtime Error: PID[16955]
Runtime Error: PID[16956]
Runtime Error: PID[16957]
Traceback (most recent call last):
  File "torch_init.py", line 21, in <module>
    raise RuntimeError
RuntimeError
Traceback (most recent call last):
  File "torch_init.py", line 21, in <module>
    raise RuntimeError
RuntimeError
Traceback (most recent call last):
  File "torch_init.py", line 21, in <module>
    raise RuntimeError
RuntimeError
```
and hangs afterwards. (verified by checking 'top' cmd)

tried to use async allgather with timeout, and the wait() was able to terminate but still cannot exit afterwards.

- PyTorch or Caffe2:
- How you installed PyTorch (conda, pip, source): pip
- Build command you used (if compiling from source):
- OS: Ubuntu18
- PyTorch version: 1.8.1+cpu
- Python version: python3.7


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang