sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: AltGr keypress makes me press Home twice in Terminal for effect.
Labels: bug,help wanted,terminal-input

Issue Type: <b>Bug</b>

You will need a Norwegian or other keyboard with AltGr to reproduce this.

1. Open a terminal (cmd or wsl or SSH remote)
2. Press AltGr + [ to make a [ character. Or anything that involved AltGr key.
3. Press Home
 Expected result: 
The cursor moves to start of line.
 Actual result:
Nothing happens
4. Press Home again. Now the cursor move.

The same happens for End or Arrow keys also. 

VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:40:02.816Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 x 4008)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: enabled_on<br>video_decode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|31.96GB (18.90GB free)|
|Process Argv|--disable-extensions --crash-reporter-id 0dd2b7f7-0733-4fbe-918d-575797b6cab6|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30425749
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
vscoreces:30384385
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30424896
pythonvs932:30410667
wslgetstartedc:30426334
vscop804:30404766
vscop940:30404999
vsrem710cf:30416617
vsbas813:30426126

```

</details>

Screenshot with log:
https://user-images.githubusercontent.com/1906913/151179623-611f342c-bf4e-4537-aa7e-3cd700bd6802.png

<!-- generated by issue reporter -->
Repository: PowerToys
Issue: FancyZone Window Switching for any window on top of another
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

I enjoy the use of Window Switching functionality, but I don't like the restriction that the windows need first to be placed into the exact same zone for them to work. This is especially evident with multiple maximized windows on top of each other on the same monitor, they don't work with window switching shortcuts. To make them work, I need to put them in a fancyzone that is a false "maximize" size, but then they take up the whole screen but are still in the "restored state", showing the titlebar.

If the logic could include any window that is layered on top of another, I think this window switching shortcut functionality would become a lot more useful and flexible. 

### Scenario when this would be used?

It would help me immediately switch to applications hidden below another window, regardless if I manually assigned them to a fancy zone or not, and would enable the use of Window Switching when windows are Maximized.

### Supporting information

_No response_
Repository: rust
Issue: Tracking Issue for asm_unwind
Labels: A-inline-assembly,B-unstable,C-tracking-issue,F-asm

The feature gate for the issue is `#![feature(asm_unwind)]`.

### Summary

This feature adds a `may_unwind` option to `asm!` which allows an `asm` block to unwind stack and be part of the stack unwinding process. This option is only supported by the LLVM backend right now.

### Status

Blocked on the stabilization of `extern "C-unwind"` (#74990).

Also it is uncertain whether this can be supported directly by non-LLVM backends. It is possible to support by outlining the assembly code to a separate function and calling it.
Repository: rust
Issue: Tracking Issue for asm_experimental_arch
Labels: A-inline-assembly,B-unstable,C-tracking-issue,F-asm

The feature gate for the issue is `#![feature(asm_experimental_arch)]`.

### Summary

This feature tracks `asm!` and `global_asm!` support for the following architectures:
- Arm64ec: https://github.com/rust-lang/rust/pull/131781
- NVPTX
- PowerPC
- Hexagon
- MIPS32r2 and MIPS64r2
- wasm32
- BPF
- SPIR-V
- AVR
- MSP430
- s390x: https://github.com/rust-lang/rust/pull/131258

### Status

Each architecture needs to be reviewed before stabilization:
- It must have `clobber_abi`.
- It must be possible to clobber every register that is normally clobbered by a function call.
- Generally review that the exposed register classes make sense.
Repository: flutter
Issue: [Web][HTML]: Line drawing with PointMode.polygon has rendering errors
Labels: engine,e: web_html,has reproducible steps,P3,found in release: 2.8,found in release: 2.9,team-engine,triaged-engine

## Steps to Reproduce

When using canvas.drawPoints(PointMode.polygon, ...) or the same lines with canvas.drawRawPoints(PointMode.polygon, ...), the polygon line renderer has two defects:

1. The strokeJoin paint parameter does nothing.  The renderer draws each line segment as a flat-ended rectangle and doesn't create a bevel, mitre or rounded join.
2. If the opacity is less than 255, so the lines are partially translucent, it can be seen that the rectangles overdraw each other and instead of the adjacent rectangles being uniformly opaque, the overlapping part is less translucent than the non-overlapping parts.

I have set up a simple example: https://dartpad.dev/?id=d6ea4d4b5a6a2bf5d0881ee4cbdc7451

DartPad says it has Flutter 2.8.1 and Dart SDK 2.15.1.

Changing the other paint parameters, isAntiAlias, strokeWidth, style etc. doesn't seem to fundamentally alter the output and the defects show up regardless.

Thanks
Paul.
Repository: storybook
Issue: [addon-docs] transformSource parameters should include Story control values/args or storyFn
Labels: feature request,needs triage

**Is your feature request related to a problem? Please describe**
In Storybook 6.3 we used to be able to call the `storyFn` parameter from inside of `transformSource`, now we only get `src` and `storyContext` with Storybook 6.4.

**Describe the solution you'd like**
Ideally we would be able to retrieve the Story `args` or `storyFn` to render out the HTML based on Controls that are set within the Story. Currently with `storyContext` you only get access to `originalStoryFn` and this is without the current `args`. You can use `initialArgs` but this does not help us when we want rendered HTML after we change Control values for any given Story.

**Describe alternatives you've considered**
One alternative was to use the `@whitespace/storybook-addon-html` addon, but with our layouts in Storybook this introduces major performance issues because the addon has to re-render the HTML output inside the panel every time a control changes. With `transformSource` we would be able to fetch the HTML only when inside the Docs panel.

**Are you able to assist to bring the feature to reality?**
No

**Additional context**
REF: https://github.com/storybookjs/storybook/issues/14489#issuecomment-1018802909
Repository: flutter
Issue: [web] support scaling page content using two-finger pinch gesture
Labels: c: new feature,framework,a: accessibility,platform-web,has reproducible steps,P3,found in release: 2.8,found in release: 2.10,team-web,triaged-web

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Steps to Reproduce

<!-- Please include full steps to reproduce so that we can reproduce the problem. -->

1. Execute `flutter run release --web-renderer html -d web-server --web-port 8080 --web-hostname 10.0.0.209` on any Flutter Web project.
2. Navigate to the hostname and port on any web browser to access the Flutter Web app
3. Open the developer tools and navigate to the source code.

**Expected results:**
With the HTML tag `<meta name="viewport" content="width=device-width, initial-scale=.0, maximum-scale=2.0, user-scalable=yes">` in the index.html, I expect the tag to remain there for accessibility checkers.

**Actual results:**
This meta tag:
`<meta flt-viewport="" name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">`
is generated by Flutter, overriding any attempts to set the maximum-scale or user-scalable properties. Even attempts to update this meta tag at runtime are thwarted by Flutter. 

This is an issue as it prevents the Flutter web app from passing accessibility checkers even if user scalability is implemented in-app via Flutter. Any help or workarounds would be greatly appreciated as Flutter is only viable for this project as the client relies on passing accessibility checkers and security scans for their institution's cyber-sec insurance, and funding.
Repository: flutter
Issue: [dropdown]: Multi-Select Dropdown
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

## Use case

After trying to use some packages on pub.dev, I encountered, that most of them can just handle Strings and are not type-aware and not usable as good as the Material Dropdown like implemented in the Flutter Framework.

But in several projects and especially customer projects in my actual company, we couldn't implement Multi-Select Dropdown Menu's or Multi-Select Dropdown-FormFields.

For example: You got a business in your DB and that business can have multiple deals to select from another collection. These deals should be selected in multiple for that business.

Actually it is not possible with Flutter like DropdownButton/DropdownButtonFormField.

## Proposal

Either extend actual dropdown.dart with multi-select dropdown widgets, or integrate it's functionality into existing DropdownButton/DropdownButtonFormField

@HansMuller
Repository: pytorch
Issue: Clarify the behavior of DataLoader sampler and batch_sampler parameters
Labels: module: docs,module: dataloader,triaged

### 📚 The doc issue

Documentation to be updated: https://pytorch.org/docs/stable/data.html

Problem: Looking at https://discuss.pytorch.org/t/force-dataloader-to-fetch-batched-index-from-custom-batch-sampler/86656/3 some users (myself included) find the documentation to be confusing.

The documentation implies that `sampler` is expected to return one index at a time while `batch_sampler` is meant to return a batch of indices at a time. It therefore seems intuitive to pass a `BatchSampler` into `batch_sampler` since the former does what `batch_sampler` seems to be designed for.

It isn't clear that it is perfectly legal (and sometimes desirable) to pass a `BatchSampler` into `sampler`, nor that passing a `BatchSampler` into `batch_sampler` will result in the indices getting broken down and passed individually into `__getitem__`.

### Suggest a potential alternative/fix

The existing behavior is okay. I just think that the documentation should be augmented to mention two things:

1. Users who want to load batches of data at a time should pass a `BatchSampler` into `sampler` (not `batch_sampler`)
2. If you pass a `BatchSampler` into `batch_sampler` it'll break down the indexes and pass them individually into `__getitem__`

cc @brianjo @mruberry @SsnL @VitalyFedyunin @ejguan @NivekT
Repository: pytorch
Issue: Add `output_size` argument to `Upsample` forward method (just like for `ConvTranspose` Modules)
Labels: module: nn,triaged,enhancement

### 🚀 The feature, motivation and pitch

Motivated by the same reasons ConvTranspose modules have an `output_size` argument.

The problem is that multiple tensor sizes will downsample to the same size
For example:
```python
>>> import torch
>>> import torch.nn.functional as F
>>> F.interpolate(torch.rand(1, 1, 10, 10), scale_factor=.5).shape
torch.size([1, 1, 5, 5])
```
```python
>>> F.interpolate(torch.rand(1, 1, 11, 11), scale_factor=.5).shape
torch.size([1, 1, 5, 5])
```

When reversing this operation with an upsampling interpolation operation, an `output_size` argument is required to reconstruct the original input size. The desired functionality is as follows -- to reconstruct the original size of [1, 1, 11, 11], we would do:

```python
nn.Upsample(scale_factor=2)(torch.rand(1, 1, 5, 5), output_size=[1, 1, 11, 11])
```

**Implementation:**
`_ConvTransposeNd` already has a utility method [`_output_padding`](https://github.com/pytorch/pytorch/blob/master/torch/nn/modules/conv.py#L611-L649) for calculating the padding of the output tensor when the `output_size` argument is provided. While `Upsample` doesn't require most of the arguments (e.g. padding, dilation, kernel_size ...) It seems like a reasonable solution would be to extract the `_output_padding` method into a separate utility function to use with the `Upsample` module as well.

I'm happy to create a pull request if this is a desired feature.

### Alternatives

_No response_

### Additional context

The motivation for this feature request is to get Unet models (specifically [segmentation_models_pytorch](https://github.com/qubvel/segmentation_models.pytorch.git) Unet model) to work with arbitrarily sized input images. Currently these models throw errors at the upsampling op for certain input images sizes -- due to the round-off problem mentioned above. However this feature is useful for any model that include downsampling + upsampling interpolation layers.

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345
Repository: TypeScript
Issue: Conditional types documentation missing information crucial for their usage.
Labels: Docs

# Bug Report
Documentation for conditional types  is missing very important information about limitations. If someone wishes to use them frustration ensues because it is not working as one would expect. Documentation uses throw "unimplemented"; and gives no warnings about issues you could run into when actually making an implementation.

After several hours of trying and searching and already strongly believing it is a bug, I found that it is Design limitation - https://github.com/microsoft/TypeScript/issues/22735

### 🔎 Search Terms

conditional types not working, TS2322, conditional types, broken conditional types

### Problematic code

- Taken straight from documentation with simple implementation added + with workaround.
- the same on codesandbox: https://codesandbox.io/s/si8kv
```

interface IdLabel {
  id: number /* some fields */;
}
interface NameLabel {
  name: string /* other fields */;
}
type NameOrId<T extends number | string> = T extends number
  ? IdLabel
  : NameLabel;
function createLabelBad<T extends number | string>(idOrName: T): NameOrId<T> {
  if (typeof idOrName === 'string') {
      return {name: idOrName}; // TS2322
  }
  return {id: idOrName}; // TS2322
}
function createLabelGood<T extends number | string>(idOrName: T): NameOrId<T> {
  if (typeof idOrName === 'string') {
      const nameLabel: NameLabel = {name: idOrName};
      return nameLabel as any;
  }
  const idLabel: IdLabel = {id: idOrName};
  return idLabel as any;
}
```

### 🙁 Actual behavior

Very important information is omitted from documentation. This causes unnecessary frustration and headaches and lost time.

### 🙂 Expected behavior

Very important information about limitations of conditional types is mentioned possibly with some workarounds presented instead of throw "unimplemented";
Repository: go
Issue: runtime: TestCgoCrashHandler failure on windows-amd64-2008 with "runtime: failed to create new OS thread"
Labels: OS-Windows,NeedsInvestigation,compiler/runtime

```
--- FAIL: TestCgoCrashHandler (0.02s)
    crash_test.go:160: output:
        main: recovered done
        new-thread: recovered done
        second-new-thread: recovered done
        main-again: recovered done
        
        This application has requested the Runtime to terminate it in an unusual way.
        Please contact the application's support team for more information.
        runtime: failed to create new OS thread (13)
        
        
        wanted:
        main: recovered done
        new-thread: recovered done
        second-new-thread: recovered done
        main-again: recovered done
FAIL
FAIL	runtime	44.919s
```

`greplogs --dashboard -md -l -e 'FAIL: TestCgoCrashHandler .*(?:\n    .*)*runtime: failed to create new OS thread'`

[2022-01-24T16:55:59-f9df4ea/windows-amd64-2008](https://build.golang.org/log/ef6042fc121ad714c6ed9bc83257798d458a6a31)

(CC @alexbrainman)
Since we've only seen one of these in the logs, I'll leave it in the backlog to gather more data about the failure rate.
Repository: godot
Issue: Project white screens and hangs indefinitely when run from Editor
Labels: bug,topic:rendering,topic:editor,crash

### Godot version

v3.4.2.stable.official [45eaa2daf]

### System information

Edition	Windows 10 Home Version	21H1 Installed on	‎8/‎4/‎2021 OS build	19043.1466 Experience	Windows Feature Experience Pack 120.2212.3920.0

### Issue description

I have a small networked project setup with one project being the server and the other being a client.

When I attempt to run the client project from the editor after a fresh computer restart, the project works as expected. However, after a few run attempts, the project window will open up an all white window, and hang indefinitely with no debug output.

If I fully restart my computer, I can get a few runs in successfully before the issue crops back up.

If I export the client project and run the exported executable, it runs as expected as many times as I like.

### Steps to reproduce

I've attached my client project, the server project should not be needed for reproducing this bug.

Run the project from the Godot editor. Note that on expected boot, there should be debug logs and a gray game scene. It may crash or error out without the server project running on localhost but that's fine.

Close the project debug run. Try to run it again. The error behavior should resume and show a white screen and hang indefinitely.

The project attached isn't necessarily "minimal" but it is what I've got at the moment.

### Minimal reproduction project

[pixctf.zip](https://github.com/godotengine/godot/files/7945336/pixctf.zip)
Repository: rust
Issue: Tracking Issue for panic_backtrace_config
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(panic_backtrace_config)]`

This is a tracking issue for configuring the capture and display of backtraces in the default panic hook, as well as exposing that configuration to third-party libraries for usage.

### Public API

```rust
mod panic {
    #[derive(Copy, Clone, Debug, PartialEq, Eq)]
    #[non_exhaustive]
    pub enum BacktraceStyle {
        Short,
        Full,
        Off,
    }
    fn set_backtrace_style(BacktraceStyle);
    fn get_backtrace_style() -> Option<BacktraceStyle>;
}
```

This API is intended to form part of the strategy for addressing the unsoundness of the `std::env::set_var` API on some platforms (mostly non-Windows). See https://github.com/rust-lang/rust/pull/92431#issuecomment-1014945627 for a summary.

### Steps / History

- [x] Implementation: #93101
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

* Do we need to move to a thread-local or otherwise more customizable strategy for whether to capture backtraces? See [this comment](https://github.com/rust-lang/rust/pull/79085#issuecomment-727845826) for some potential use cases for this.
   * Proposed answer: no, leave this for third-party hooks.
* Bikeshed on naming of all the options, as usual.
* Should BacktraceStyle be moved into `std::backtrace`?
   * It's already somewhat annoying to import and/or re-type the `std::panic::` prefix necessary to use these APIs, probably adding a second module to the mix isn't worth it.
* Should `get_backtrace_style` be exposed?
   *  The `Option<BacktraceStyle>` return type looks a little weird, and may not mean the intuitive thing -- `None` represents `Unsupported`, not "not set" or "don't print backtraces", as might be initially assumed.
   * We may want a `std::panic::report_backtrace(&mut dyn Write)` instead which internally knows how to format things.
Repository: create-react-app
Issue: Registering Service Worker causes `NO INTERNET` chrome page on default install
Labels: needs triage,issue: bug report

### Describe the bug

Run a brand new create react app project and register a service worker. Build your app using `yarn build` and serve it using `serve -s build`. Open a new chrome tab in incognito mode. While the page will serve normally for the first 10 seconds, when the service worker activates, the page suddenly breaks with an appear offline message.

### Did you try recovering your dependencies?

This can be reproduced using a brand new project.

### Which terms did you search for in User Guide?

None of the troubleshooting tips in https://create-react-app.dev/docs/troubleshooting/ are helpful.

### Environment

```
node -v
v16.11.1
npx -v
6.14.8
```

### Steps to reproduce

First install a fresh project

```bash
npx create-react-app@v5.0.0 my-app --template cra-template-pwa-typescript
cd my-app
yarn install
```

then apply this patch

```git
diff --git a/src/index.tsx b/src/index.tsx
index e459b13..4a7b0ba 100644
--- a/src/index.tsx
+++ b/src/index.tsx
@@ -15,7 +15,7 @@ ReactDOM.render(
 // If you want your app to work offline and load faster, you can change
 // unregister() to register() below. Note this comes with some pitfalls.
 // Learn more about service workers: https://cra.link/PWA
-serviceWorkerRegistration.unregister();
+serviceWorkerRegistration.register();

 // If you want to start measuring performance in your app, pass a function
 // to log results (for example: reportWebVitals(console.log))
```

And finally build and serve

```
yarn build
serve -s build
```


### Actual behavior

Try to open an incognito page on Google Chrome (v97 or above). The page will load for a few seconds. If you refresh the page and show the inspector and go to the `Application` tab, it displays the dinosaur.

<img width="1213" alt="Screenshot 2022-01-26 at 23 19 26" src="https://user-images.githubusercontent.com/2795594/151257315-c01becb6-b418-4f1e-98e9-568435424a5a.png">

### Expected behavior

It should display the create react app homepage

<img width="1286" alt="Screenshot 2022-01-26 at 23 25 37" src="https://user-images.githubusercontent.com/2795594/151257436-03912606-dfb6-47a8-b5ce-2b9fcc7358d7.png">


### Reproducible demo

See steps to reproduce.
Repository: PowerToys
Issue: Snap applications to specified monitor
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

Some applications just don't want to remember the last position where they were at. A feature that could force applications to snap back to the monitor of choice would be a big help. I used to have DisplayFusion installed that could handle something like that, but something using less resources would be preferred.

### Scenario when this would be used?

With my dual monitor setup it's preferred that some apps just open on the secondary monitor, without having to move it every time you launch the app. Could be nice for gamers as well. some games don't add the option to specify a preferred monitor, and force the primary one.

### Supporting information

_No response_