sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Minor text cropping issue on Ultrawide monitors, in FancyZones layout editor
Labels: Issue-Bug,FancyZones-Editor,Area-User Interface,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.60.0

### Running as admin

- [X] Yes

### Area(s) with issue?

FancyZones Editor

### Steps to reproduce

Requires an ultra widescreen monitor (32:9) running at resolution of 5120 x 1440.

Repro:
- Select FancyZones
- Click 'Launch layout editor'
- Note that the text in the screen & resolution display image has a tiny text cropping error. (See attached image which shows the issues clearly).
- 
![image001](https://user-images.githubusercontent.com/4445791/178572793-6d250960-fdae-4eeb-b0a1-30f6704f8772.png)



### ✔️ Expected Behavior

No text cropping in UI elements.

### ❌ Actual Behavior

Text cropping occurred as per screenshot.

### Other Software

_No response_
Repository: flutter
Issue: flutter build dashboard header bar has alignment issues
Labels: team-infra,P3,triaged-infra

The branch drop down is extremely long, because of one very long branch name, which makes it look not correct. We should try to make the drop down in the header be a fixed width to the size of the title text, and expand once it is opened.

See:

![image](https://user-images.githubusercontent.com/91688203/178577857-37c47053-8973-4fd0-8c31-9e77176dacc2.png)

![image](https://user-images.githubusercontent.com/91688203/178577727-c196a04b-c7b2-41b7-a583-b22284f776d7.png)
Repository: vscode
Issue: API request - Support interactive window natively
Labels: feature-request,api-proposal,interactive-window

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
As described in https://github.com/microsoft/vscode/issues/151994 extensions have to have special knowledge about the interactive window URI in order to handle things like inserting new cells and intellisense.

This issue is to:
- Eliminate URI parsing in extensions and language servers
- Eliminate the usage of a command to create an interactive window
- Propose an API for creating interactive windows (based on the 'interactive.open' command used now)
- Propose an API for adding new cells into the history
- Change the current notebook API to include the special 'input' cell as part of the interactive notebook.

```typescript
  // Under vscode.workspace namespace
		/**
		 * Creates a new interactive window
		 * @param resource interactive resource uri 
		 * @param title title of the editor
		 * @param initialController controller to start with
		 * @param options options for viewing
		 */
		export function openInteractiveWindow(resource?: Uri, title?: string, initialController?: NotebookController, options?: { viewColumn?: ViewColumn; preserveFocus?: boolean }): Thenable<NotebookDocument>;

// Under vscode.NotebookEdit class

		/**
		 * Utility to create an edit that adds to an interactive window
		 * @param newCells the new cells
		 */
		static addInteractiveCells(newCells: NotebookCellData[]): NotebookEdit;

```


Additionally the notebook API for the interactive window should include the input box in its list of cells.
Repository: vscode
Issue: List widget - add api for a list item to specify not to receive focus
Labels: feature-request,list-widget

At the moment there is code that disables a list item receiving focus and instead focuses a particular element within the list item. It would be great if the list widget would have the capability for a list item to specify that it should never receive focus. This would be useful in the Source Control view for both the list item containing the commit input field, and the action button.
Repository: go
Issue: runtime: convert atomic values to runtime/internal/atomic types
Labels: compiler/runtime

`runtime/internal/atomic` added Int32, etc types a while ago, which are slowing getting used on new code. We should also go through existing code and convert bare atomic values to use the atomic types.
Repository: deno
Issue: Resolving promises in the `beforeunload` event can lead to event loop errors
Labels: bug,deno_core

```js
await new Promise(resolve => {
  window.onbeforeunload = resolve;
});
```

```
error: Module evaluation is still pending but there are no pending ops or dynamic imports. This situation is often caused by unresolved promises.
```

This can also happen with `deno test`:

```js
Deno.test("resolve on beforeunload", async () => {
  await new Promise(resolve => {
    window.onbeforeunload = resolve;
  });
});
```

```
running 1 test from ./a.test.js
resolve on beforeunload ...
FAILED | 0 passed | 0 failed (20ms)

error: Promise resolution is still pending but the event loop has already resolved.
```

These errors show up because Deno's event loop assumes that a promise that's holding up a module's top-level await (or in the case of `deno test`, a call to `JsRuntime::poll_value`) will resolve within the event loop, and so if there are no ref'd async ops that can cause some more code to run, the promise won't ever resolve. But the `beforeunload` event is fired from the CLI crate and the event loop doesn't know about it.

This is not specific to the `beforeunload` event, since it can also happen with promises that resolve on the `unload` event. The difference is that nothing other than microtasks will run after the `unload` event, whereas the event loop might keep running after `beforeunload`.
Repository: vscode
Issue: Feature Request: `editor.autoCloseBlockComment` setting
Labels: feature-request,editor-autoclosing

In `language-configuration.json`, block comment start and end positions can be defined.  For example, for cpp, or typescript-basics:

```
"blockComment":["/*","*/"]
```

typescript-basics also has an AutoClosingPair defined for block comments (requiring an additional asterisk, though I'm not aware of the origin of that convention) :

```
		{
			"open": "/**",
			"close": " */",
			"notIn": [
				"string"
			]
		}
```

There are currently two settings, which make it possible to disable the auto-closing, for brackets and quotes: `editor.autoClosingBrackets` and `editor.autoClosingQuotes`.

It looks like `editor.autoClosingBrackets` also controls whether comments are auto-closed.  Since there are fields in `language-configuration.json` to identify brackets and blockComments, it seems enabling/disabling of block comments could be done using a separate setting, rather than being lumped in with brackets.

There is not currently an `autoClosingPair` in `cpp`.  I'd also like to suggest adding that, provided there is a way to disable it without disabling auto closing of brackets.

Alternatively, if there is a recommended way of implementing auto-closing of block comments that could be implemented by an extension, perhaps we could do that in the C/C++ extension and provide our own setting for it.

Ideally, C++ block comment closing would not require the second asterisks (required in typescript* and the closing `*/` could be typed over.  (see: https://github.com/microsoft/vscode/issues/54499 ).

https://github.com/microsoft/vscode/issues/1966 is related.
Repository: rust
Issue: `overflowing_literals` should have an option for "ignore signed overflows"
Labels: A-diagnostics,T-lang,T-compiler

I have recently been working with code where using the two's complement form of signed literals is useful, but this doesn't mesh very well with the `overflowing_literals` lint.

Here's a simplified example:

```rust
let good_signed = 0b_1111_1111i8;
let bad_signed = 0b_111_111_111i8;
let good_unsigned = 0b_1111_1111u8;
let bad_unsigned = 0b_111_111_111u8;
```

Right now, with the `overflowing_literals` lint, `good_signed`, `bad_signed`, and `bad_unsigned` will all be marked as overflowing. To avoid `good_signed` being marked as invalid, I had code that I blanket marked as `#[allow(overflowing_literals)]`, but this caused me to miss literals like `bad_signed` and `bad_unsigned`, which overflow regardless of their sign.

I'm not sure what the best strategy here is. I see two possible solutions:

1. The `overflowing_literals` lint is split into a separate lint alongside `overflowing_literals` lint, where this new lint warns on integer literals that would not overflow if they were unsigned, but do overflow because they're signed. This can be selectively allowed in code while still being able to keep the `overflowing_literals` lint on.
2. Instead of splitting the lint, no lint is thrown at all in the case where a signed integer overflows to a negative number because it's written in two's complement form. Or, alternatively, the lint is only triggered if the integer is written in base-10, but not if it's written in hexadecimal, octal, or binary.

Either way, the current configuration of the lint seems overly restrictive.

After searching, I decided to file a separate issue instead of including this analysis in #53628. If this is seen as too similar to the existing ticket, I'm fine with also closing this in favour of that one.
Repository: pytorch
Issue: quantization: QConfigMapping should be easy to print
Labels: oncall: quantization,triaged

### 🐛 Describe the bug

Currently printing out the contents of a `QConfigMapping` object does not make it easy to see the contents:

```
import torch
qconfig_mapping = torch.ao.quantization.get_default_qconfig_mapping()
print(qconfig_mapping)

> <torch.ao.quantization.qconfig_mapping.QConfigMapping object at 0x7f29785c45e0>
```

Ideally printing this object would display the contents, so users can inspect the configs they are passing in to the quantization APIs.

### Versions

master

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @jgong5 @Xia-Weiwen @leslie-fang-intel @vkuzo
Repository: go
Issue: runtime: use epoll_pwait2 where available for sub-millisecond timeout precision on Linux
Labels: Performance,help wanted,NeedsFix,compiler/runtime

Linux kernel 5.11 (February, 2021) added the `epoll_pwait2` system call.  It is exactly like `epoll_pwait` except that the timeout argument is a `struct timespec`.  This permits specifying a timeout with nanosecond precision, where `epoll_pwait` and `epoll_wait` only permit millisecond precision.  We should change runtime/netpoll_epoll.go to use `epoll_pwait2` when available to get higher precision delays.

CC @golang/runtime
Repository: vscode
Issue: Inactive nested breakpoint indicators jump horizontally
Labels: bug,debug

Hi there,
There is a report for a breakpoints  rendering issue.

Type: <b>Bug</b>

1. Set a line breakpoint
1. Turn off the breakpoint
1. Turn on the breakpoint

Actual behaviour: Inactive nested breakpoint indicators jump horizontally on turn off/turn on actions.

Expected behaviour: Inactive nested breakpoint indicators do not change their position on turn off/turn on actions.

https://user-images.githubusercontent.com/3923527/178627791-ab268492-16b2-4842-95c4-73f3eaf17576.mov

VS Code version: Code - Insiders 1.70.0-insider (f3528d481b366b24321c382d5e5849f4c7d65248, 2022-07-12T09:33:59.420Z)
OS version: Darwin x64 21.5.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|3, 2, 2|
|Memory (System)|64.00GB (4.65GB free)|
|Process Argv|--crash-reporter-id dae9747d-a608-49fb-967b-b0bdd43dcc8f|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30404738
wslgetstarted:30449409
vscscmwlcmt:30465136
cppdebug:30492333
pylanb8912:30522163
vsclangdf:30492506

```

</details>

<!-- generated by issue reporter -->
Repository: transformers
Issue: Model parallelism for m2m100
Labels: New model

### Model description

The translation model m2m100 proposed by Facebook is too huge to train using DDP, is there any open solution for model parallelism of m2m100, just like GPT2? Thank you.

### Open source status

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

### Provide useful links for the implementation

_No response_
Repository: pytorch
Issue: Investigate ncclRedOpCreatePreMulSum operator for gradient reduction
Labels: oncall: distributed

### 🚀 The feature, motivation and pitch

Per @kwen2501's comment here: https://github.com/pytorch/pytorch/issues/78774#issuecomment-1148272714, we should investigate this operator and see whether it is more efficient than gradient pre/post divide in DDP / FSDP.

### Alternatives

_No response_

### Additional context

_No response_

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @kwen2501
Repository: pytorch
Issue: "Attempted to resize a view tensor to a larger size. This is not allowed in the functionalization pass" reported on non view tensor
Labels: triaged,module: functionalization

### 🐛 Describe the bug

Repro test:

```
    def test_resize_intermediate(self):
        def f(x):
            y = x.clone()
            z = y.view(0)
            y.resize_(20)
            return y

        self.assert_functionalization(f, torch.ones(0))
```

this raises

```
======================================================================
ERROR: test_resize_intermediate (__main__.TestFunctionalization)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/test_functionalization.py", line 120, in test_resize_intermediate
    self.assert_functionalization(f, torch.ones(0))
  File "test/test_functionalization.py", line 93, in assert_functionalization
    out_functional = func(input_functional)
  File "test/test_functionalization.py", line 117, in f
    y.resize_(20)
RuntimeError: Attempted to resize a view tensor to a larger size. This is not allowed in the functionalization pass
```

However, y is not a view.

This variant of the program does work:

```
        def f(x):
            y = x.clone()
            y.resize_(20)
            return y
```

cc @bdhirsh @ezyang this is low priority

### Versions

master
Repository: angular
Issue: Add a ghost property to `InjectionToken` for generic type parameter type safety
Labels: feature,area: core,state: has PR,core: di,cross-cutting: types,feature: in backlog

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

Currently `InjectionToken` doesn't use the type parameter and thus typescript does not type check it (it is marked as unused).
```ts
// Simplified version
class InjectionToken<T> {
  constructor(protected name: string) {}
}

interface Person {
  name: string;
}

interface Car {
  numOfWheels: number;
}

const a = new InjectionToken<Person>('test');
const b = new InjectionToken<Car>('test');

// No error :(
const c: InjectionToken<Person> = b;
```

### Proposed solution

As the generic type is not used anyway - an unused property can be added to `InjectionToken` just for this type check ability with the type `T`
```ts
// Simplified version
class InjectionToken<T> {
  typeCheck!: T;
  // #typeCheck!: T; // Option 2
  // protected typeCheck!: T; // Option 3

  constructor(protected name: string) {}
}

interface Person {
  name: string;
}

interface Car {
  numOfWheels: number;
}

const a = new InjectionToken<Person>('test');
const b = new InjectionToken<Car>('test');

// Error :)
const c: InjectionToken<Person> = b;
``` 

### Alternatives considered

1. Wrap `InjectionToken` with a custom class that does it (possible? recommended?)
2. Ignore the missing type check :(
Repository: opencv
Issue: Memory Leaks on Windows
Labels: duplicate,question (invalid tracker)

##### System information (version)
- OpenCV => 4.6
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2019

##### Detailed description
When linking against the pre-built OpenCV world DLL, there are many memory leaks on Windows with a simple test program.

##### Steps to reproduce
1. Create a new test console project in Visual Studio
2. Replace the contents of the generated .cpp with the following code:

```
#define _CRTDBG_MAP_ALLOC

#include <stdlib.h>
#include <crtdbg.h>

#include <opencv2/core.hpp>

int main()
{        
    cv::Mat myMatrix;

    _CrtDumpMemoryLeaks();
}
```

4. Open project settings and add the path to the downloaded OpenCV headers, and link against the OpenCV world DLL .lib file
5. Copy the OpenCV world DLL to the same directory as the .exe
6. Run the program and observe the memory leaks (my output Debug log attached below)

Am I doing something wrong? Is there a way to fix these leaks? Perhaps an issue with the initialization of OpenCV?

[DebugLog.txt](https://github.com/opencv/opencv/files/9100532/DebugLog.txt)
Repository: rust
Issue: assoc type impl mismatch with trait assoc type doesnt mention where clauses
Labels: A-diagnostics,T-compiler,A-GATs

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

```rust
#![feature(generic_associated_types)]

trait Trait {
    type Assoc<'a>;
}

impl<'b> Trait for &'b () {
    type Assoc<'a>
    = &'a &'b ()
    where
        Self: 'a;
}
```

The current output is:

```
error: `impl` associated type signature for `Assoc` doesn't match `trait` associated type signature
 --> src/lib.rs:8:5
  |
4 |     type Assoc<'a>;
  |     -------------- expected
...
8 |     type Assoc<'a>
  |     ^^^^^^^^^^^^^^ found
```

Ideally the output should look like:

```
error: `impl` associated type signature for `Assoc` doesn't match `trait` associated type signature
 --> src/lib.rs:8:5
  |
4 |     type Assoc<'a>;
  |     -------------- expected no where clause
...
8 |     type Assoc<'a>
  |     ...
  |     where
  |         Self: 'a;
  |         ^^^^^^^^ found where clause not present on trait definition
note: consider adding where clause to trait definition
  |
4 |    type Assoc<'a>
  |    where
  |        Self: 'a;
  |    +++++++++++++
```
Repository: deno
Issue: Deno cannot fully cache Skypack with the `?dts` query param
Labels: bug,cli

For example, when I run `deno cache` twice (so it should have been cached):

```
deno cache "https://cdn.skypack.dev/swagger-client?dts"
```

It still downloads the index.d.ts file from Skypack, the output is:

```
Download https://cdn.skypack.dev/-/swagger-client@v3.18.5-Nt8AmAsJyCx6gdL9U9cP/dist=es2019,mode=types/index.d.ts
```

If I remove the `?dts` query param, all files from Skypack can be properly cached.
Repository: flutter
Issue: [proposal] Provide a way to retrieve the data of all textfields within a `Form` widget
Labels: a: text input,c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

## Use case

the Flutter `Form` widget can be extremely powerful and has a lot of potential to simplify form implementations. Sadly I'm finding myself having to create my own Form widgets because there is not simple build-in way to aggregate all the form data in one place. Just like the form can interact with all its `FormField` children through validation, saving, ... it should also have an option to submit it's childrens data. Similar to how HTML handles form submission.

## Proposal

since the `FormState` already has all its `FormFieldState` children registered it would be trivial to collect all their values. the implementation difficulties come from returning the form data in a manageable way.

I would propose adding a `submissionKey` string to the `FormField<T>` base class. this allows us to aggregate all the `FormField` data under a `Map<String, dynamic>` where the entries would be shaped as: `submissionKey:  value`. 

this would require all `FormField` to have a non-null submissionKey. This can be hande by either throwing an exception when calling a form submit on a null submissionKey, or not adding `FormField` values to the end `Form` submit data if the submissionKey is null.

This would be a minor addition to the framework with no breaking or changing code, that would still have enormous benefits.

comparing the current closest implementation of this:
```dart
Form(
  child: Column(
    children: [
      TextField( 
        onSave: (value) {
          data['name'] = value;
        },
      ),
      TextField(
        onSave: (value) {
          data['email'] = value;
        },
      ),
      TextField(
         onSave: (value) {
          data['message'] = value;
        },
      ),
      MaterialButton(
        child: Text('submit'),
        onPressed: () {
          final form = Form.of(context);
          if(!form.validate()) return;

          form.save();
          /// handle data in stateful widget...
        }
      ),
    ],
  ),    
);
```



would be turned into something like this: 
```dart
Form(
  child: Column(
    children: [
      TextField(
        submissionKey: 'name',
        ...
      ),
      TextField(
        submissionKey: 'email',
        ...
      ),
      TextField(
        submissionKey: 'message',
        ...
      ),
      MaterialButton(
        child: Text('submit'),
        onPressed: () {
          final form = Form.of(context);
          if(!form.validate()) return;
          
          final data = form.submit();
          // final object = FormObject.fromJson(data); ...
        }
      );
    ],
  ),    
);

```
Repository: next.js
Issue: incorrect params in custom express server
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:22 PDT 2022; root:xnu-8020.121.3~4/RELEASE_X86_64
    Binaries:
      Node: 16.13.2
      npm: 8.1.2
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.2.2
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

we are using custom express server for server side routing, and using the same for dynamic routes. The problem arises in the passing of query params from the server to the context of data fetching functions.

we have a file pages/news/[news].js and in the file we use getServerSideProps. the context of the function returns `context.params  = {news: '[news]'}`

### Expected Behavior

it is supposed the return the dyanmic url param
for http://localhost:3000/news/23572

`context.params  = {news: '23572'}`

### Link to reproduction

-

### To Reproduce

create next app

create custom server

copy the example express server server.js and add

`  server.get('/news/:news', (req, res) => {
    const queryParams = { news: req.params.news };
    const pagePath = '/news/[news]';
    return app.render(req, res, pagePath, queryParams);
  });`

in pages/news/[news].js

`export const getServerSideProps = async (ctx) => {
  console.log({ query: ctx.query, params: ctx.params });
  return {props: {}};
 }`