sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: [fz] override list to allow quirky programs to resize
Labels: Idea-Enhancement,Product-FancyZones

### Description of the new feature / enhancement

I really love PowerToys and the Fancy Zones are definitely a must and I still wonder why it's not included in the main operating system by default.

Anyways, it would be nice if the fancy zones worked with older applications (like EZVIZ program, for example, that looks like something from the times of Windows Vista 😝) and fixed size windows (even if it only moves to the nearest corner of a chosen zone or to its center, depending on the location of the mouse pointer).



### Scenario when this would be used?

To move/resize windows that aren't actually manipulatable using Fancy Zones

### Supporting information

EZVIZ has an application that looks like it comes from Windows Vista and is one example.

TD Ameritrade's "Think or Swim" also isn't resizable/movable using Fancy Zones, as well other similar applications.

Windows with fixed sizes like dialogs could benefit from the possibility of moving them to the nearest corner or center of a zone.
Repository: PowerToys
Issue: [AlwaysOnTop][Settings] Border preview
Labels: Product-Settings,Product-Always On Top

Add a border preview in the settings (as for FancyZones).
Repository: PowerToys
Issue: [AlwaysOnTop][Settings] Sound settings
Labels: Idea-Enhancement,Product-Settings,Product-Always On Top

Allow selecting different sounds for pinning.
Repository: ant-design
Issue: textarea在safari中，showcount更新不及时
Labels: help wanted,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/qian-tao-jie-gou-yu-xiao-yan-xin-xi-antd-4-18-2-forked-injit)

### Steps to reproduce
打开链接，在textarea中快速输入，计数会一直为0，页面有刷新的时候正常。如果正常，可以多次尝试。

### What is expected?
正常计数

### What is actually happening?
多数情况下计数一直为0，目前统计，10次有5次是有问题的

| Environment | Info |
|---|---|
| antd | 4.18.2 |
| React | 18 |
| System | macos |
| Browser | safari |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Emitted `memset` and `memcpy` are really slow on WASM
Labels: O-wasm,C-bug,C-optimization

While both functions do the "usual" double-loop pattern, with one loop processing 4 or 8 bytes at a time, and the other one doing the remaining few, sadly, the former one also only does 1-byte wide loads and stores, just has more of them per iteration in series.
This does not look right, it could very well operate on single 32bit or 64bit wide primitives per iteration.

This is what `rustc` emits in `--release` mode:
[memset](https://gist.github.com/torokati44/aaf63ed379879fc0c7bef0efcc94ad9e)
[memcpy](https://gist.github.com/torokati44/2c61a72f388a53a19095feb3dabaedd4)

Running them through `wasm-opt -O` doesn't do much, only reorders some locals, and changes an "add -1" to a "sub 1" for some reason:
[memset after wasm-opt](https://gist.github.com/torokati44/336465bc52dd8756a036d1311ee391f1)
[memcpy after wasm-opt](https://gist.github.com/torokati44/6f3242e19565430eb54795068e978ab4)
(I have also extended these sources to be complete modules for experimentation purposes.)

These functions constitute a double-digit percentage of total runtime in some cases, see: https://github.com/WebAssembly/binaryen/issues/4403#issuecomment-998326902
Repository: svelte
Issue: Pure CSS Transition
Labels: transition/animation

### Describe the problem

Hi,
is there any built-in way to use pure CSS transition in Svelte?

### Describe the proposed solution

Solution in Vue.js: https://v3.vuejs.org/guide/transitions-enterleave.html#transitioning-single-elements-components

```
<transition name="sidebar">
    <p>hello</p>
</transition>

<style>
.sidebar-enter-active,
.sidebar-leave-active {
    @apply transition duration-300
}

.sidebar-enter-from,
.sidebar-leave-to {
    @apply opacity-0 translate-x-36
}
</style>
```
_TailwindCSS_ is used in example.

### Alternatives considered

-

### Importance

would make my life easier
Repository: godot
Issue: Attempted to convert Variant to a managed array of unmarshallable element type (ArrayMesh)
Labels: bug,topic:dotnet

### Godot version

3.4.2.stable.mono.official

### System information

Manjaro Linux 5.10, GLES3, NVIDIA RTX 3070 (495.44)

### Issue description

When trying to add a Surface to an ArrayMesh in C# I get the following error:
> Attempted to convert Variant to a managed array of unmarshallable element type


### Steps to reproduce

The following code (namely, the line that starts with "mesh.AddSurfaceFromArrays") causes the error message to appear:

```csharp
private void BuildMesh() {
        var arrays = new Godot.Collections.Array();
        arrays.Resize((int)Mesh.ArrayType.Max);

        Vector3[] verts = new Vector3[4];
        Vector2[] uvs = new Vector2[4];
        Vector3[] normals = new Vector3[4];
        int[] indices = new int[6];
        
        Vector3 normal = new Vector3(0,1,0);

        verts[0] = new Vector3(0,0,0);
        uvs[0] = new Vector2(0,0);
        normals[0] = normal;
        verts[1] = new Vector3(this.SizeX,0,0);
        uvs[1] = new Vector2(this.CellsX,0);
        normals[1] = normal;
        verts[2] = new Vector3(this.SizeX,0,this.SizeY);
        uvs[2] = new Vector2(this.CellsX,this.CellsY);
        normals[2] = normal;
        verts[3] = new Vector3(0,0,this.SizeY);
        uvs[3] = new Vector2(0,this.CellsY);
        normals[3] = normal;

        indices[0] = 0; indices[1] = 1; indices[2] = 2;
        indices[3] = 2; indices[4] = 3; indices[5] = 0;

        arrays[(int)Mesh.ArrayType.Vertex] = verts;
        arrays[(int)Mesh.ArrayType.TexUv] = uvs;
        arrays[(int)Mesh.ArrayType.Normal] = normal;
        arrays[(int)Mesh.ArrayType.Index] = indices;

        ArrayMesh mesh = new ArrayMesh();
        mesh.AddSurfaceFromArrays(Mesh.PrimitiveType.Triangles, arrays);

        this.meshInstance = new MeshInstance();
        this.meshInstance.Mesh = mesh;

        AddChild(this.meshInstance);
}
```

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: BatchNorm on variable-length sequences or batches
Labels: feature,triaged

### 🚀 The feature, motivation and pitch

BatchNorm1d is often used on variable-length sequences. As I understand, that would be always incorrect currently, as it ignores the sequence lengths and thus also includes the padded values for the statistics.

To fix this, there should be an additional argument like `seq_lengths` or `batch_sizes` or so, and it should calculate the statistics only over the valid values.

(Similarly also for 2D and 3D batch norm.)


### Alternatives

The alternative is the current way to just ignore this.

I wonder a bit that this is not discussed or even mentioned at all in the documentation.


### Additional context

I don't really know the influence of this. It probably depends. I see Batch Norm also being used for sequence tasks like speech recognition, machine translation, text-to-speech and others, where the usage is almost always "wrong". I assume not many people have really investigated the effect of this.

If the effect is minor, then ignoring is maybe fine. But I would expect some discussion, and a reference to some study on this.

If the effect is big, then this is a serious problem. Then this is not really just a feature request but a serious issue.

If the effect is unknown, then I'm not sure if just ignoring it is such a good idea.

I have tried to search a bit for any references, discussions, study, or just mentions on this but I failed to find much.

#25910
https://discuss.pytorch.org/t/padding-for-variable-length-sequences-and-batch-norm-layer/21985
https://discuss.pytorch.org/t/batchnorm-for-different-sized-samples-in-batch/44251
https://discuss.pytorch.org/t/masked-batch-normalization/57813
https://discuss.pytorch.org/t/masked-batchnorm-for-variable-length-input/107286
https://github.com/cooijmanstim/recurrent-batch-normalization/issues/2
https://github.com/SeanNaren/deepspeech.pytorch/issues/312
https://yangkky.github.io/2020/03/16/masked-batch-norm.html

Also, TensorFlow seems to ignore it as well. Although there is some discussion and there was some PR (unmerged):

https://github.com/tensorflow/tensorflow/issues/30021
https://github.com/tensorflow/tensorflow/issues/30161
https://github.com/tensorflow/tensorflow/pull/30298
Repository: vscode
Issue: Add arguments property to npm tasks
Labels: feature-request,tasks

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->

Does this issue occur when all extensions are disabled?: Yes

- VS Code Version: 1.63.2
- OS Version: Windows 11 (10.0.22000.376)

This has been reported before (#128569), but that issue is locked as "not reproducible". The default Office.js add-ins created using Yeoman generator create several launch configurations. The one for Microsoft Word looks like this:

```
{
  "name": "Word Desktop (Edge Chromium)",
  "type": "pwa-msedge",
  "request": "attach",
  "useWebView": true,
  "port": 9229,
  "timeout": 600000,
  "webRoot": "${workspaceRoot}",
  "preLaunchTask": "Debug: Word Desktop",
  "postDebugTask": "Stop Debug"
},

```

`preLaunchTask` refers to an entry in `tasks.json` that is defined like this:

```
{
  "label": "Debug: Word Desktop",
  "type": "npm",
  "script": "start:desktop -- --app word",
  "presentation": {
    "clear": true,
    "panel": "dedicated",
  },
  "problemMatcher": []
},

```
`start:desktop` is defined in `package.json`:

`"start:desktop": "office-addin-debugging start manifest.xml desktop",`

Trying to launch this configuration, I see the following error:

```
> Executing task: npm run "start:desktop -- -- app word" <

npm ERR! Missing script: "start:desktop -- -- app word"
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR!   npm run
```

It is basically the `npm run` tasks with command-line argument, which fails saying that it can't locate the script. Interestingly, running the task directly from the terminal launches it successfully:

```
$ npm run start:desktop -- --app word

> office-addin-taskpane@0.0.1 start:desktop
> office-addin-debugging start manifest.xml desktop "--app" "word"

Debugging is being started...
App type: desktop
Enabled debugging for add-in 216e8727-a1f1-4fad-9421-a768af6ab77c.
Starting the dev server... (webpack serve --mode development)
The dev server is running on port 3000. Process id: 19976
Sideloading the Office Add-in...
Debugging started.

```

From this, I conclude that this has got something to do with how arguments are being handled/passed by the task.

Steps to Reproduce:

1. Install yeoman and office-generator (`npm install -g yo generator-office`)
2. Run `yo office` in an empty folder. Choose Typescript, Word and Task Pane Project options.
3. Select `Word Desktop (Edge Chromium)` debug configuration and start debugging. There you go!
Repository: godot
Issue: godot crashes without warning when importing an mp3 file
Labels: bug,confirmed,topic:import,crash

### Godot version

Godot Engine v3.4.2.stable.official.45eaa2daf

### System information

Windows 10 GLES3 AMD Radeon (TM) R5 M330

### Issue description

godot crashes after importing an mp3 file sized 160 mb. i have checked with audacity and the file seems to be not corrupted so this must be an issue with godot

### Steps to reproduce

i am attaching an example project for reproducing this bug, its just the default project with the said mp3 file added


### Minimal reproduction project

https://drive.google.com/file/d/1iB6s-Qm_IEvCchya8H4LJVjqpPGFxDTn/view?usp=sharing
Repository: PowerToys
Issue: Have AppLocale like solution again for char encoding issues for languages like Chinese
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Oh, I know that character encoding errors are getting less and less, but there are still some applications that have errors. Can you add "Use ...encoding to open the application"?function--Google Translate

### Scenario when this would be used?

Character encoding error

### Supporting information

_No response_
Repository: vscode
Issue: Filtering snippets in IntelliSense
Labels: snippets,under-discussion

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: <b>Bug</b>

Filtering snippets in Python (.py) and notebook (.ipynb) editors with the IntelliSense popup has become over-sensitive to the '.' (dot) character in snippet prefixes. Typing a '.' appears to break the snippet navigation and hides the IntelliSense popup, although it is possible to get it back by typing Ctrl+Space. 

I believe this is due to a change in snippet filtering behaviour starting from version 1.63(?)

In my snippet extension (analytic-signal.snippets-plotly) I use '.' to organize a hierarchy of snippets. This was working very smoothly - typing prefix elements separated by '.' allowed you to progressively navigate a snippet hierarchy and simultaneously see the filtered results in the IntelliSense popup.

Note that snippet filtering with the Insert Snippet command still works as expected.

VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:37:28.172Z)
OS version: Darwin x64 21.1.0
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2900)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|1, 2, 2|
|Memory (System)|32.00GB (8.42GB free)|
|Process Argv|--crash-reporter-id a9c98a1c-f474-4ebb-9a4d-d2a82c17d6b6|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (22)</summary>

Extension|Author (truncated)|Version
---|---|---
essential-data-science-pack|ana|1.0.2
preview-html|ana|1.0.0
preview-jp2|ana|0.0.4
preview-mp4|ana|0.0.1
preview-pdf|ana|1.0.0
preview-tiff|ana|1.0.1
snippets-geojson|ana|1.0.0
snippets-plotly|ana|1.0.3
vscode-azureresourcegroups|ms-|0.4.0
vscode-azurestorage|ms-|0.12.1
vscode-azurevirtualmachines|ms-|0.4.1
vscode-dotnet-runtime|ms-|1.5.0
python|ms-|2021.12.1559732655
vscode-pylance|ms-|2021.12.2
jupyter|ms-|2021.11.1001550889
jupyter-keymap|ms-|1.0.0
jupyter-renderers|ms-|1.0.4
remote-ssh|ms-|0.70.0
remote-ssh-edit|ms-|0.70.0
azure-account|ms-|0.9.11
azurerm-vscode-tools|msa|0.15.5
vscode-sanddance|msr|3.3.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vscop804cf:30404767
vs360:30404995
vsrem710cf:30416617
py55gd98cf:30411515
vscexrecpromp3c:30407761

```

</details>

<!-- generated by issue reporter -->
Repository: flutter
Issue: [Proposal]Tapping a virtual keyboard's next-button, when in a text-field should not switch focus to other widgets apart from TextField
Labels: a: text input,platform-android,platform-ios,framework,c: proposal,f: focus,P3,team-framework,triaged-framework

If a `TextField` has `textInputAction: TextInputAction.next`, a right-arrow will be displayed in the virtual keyboard in the Android phone.

If next to that `TextField` there is another `TextField`, pressing that right-arrow will move focus to that other `TextField`, which is the correct expected behavior.

However, if next to that `TextField` there is, say, a button; then pressing that right-arrow will move focus to that button, which makes no sense in a phone.

I don't understand why, in phones (Android and iOS), widgets other than textfields can have focus. There's nothing we can do with that focus.

It makes perfect sense in the desktop or web, of course.

So my questions are:

1) Does it make sense that widgets other than textfields can have focus, in phones?

2) Without having to manually add `ExcludeFocus` everywhere, how do I prevent focus of non-textfields in phones, so that pressing the abovementioned right-arrow will move focus to the next text-field? 

This issue is to suggest that non-textfield widgets should detect the platform, and accept focus only for desktop/web.
Repository: pytorch
Issue: JIT / TorchScript should support for sum(List[torch.Tensor]) like non-JIT PyTorch already does
Labels: oncall: jit,Stale

### 🚀 The feature, motivation and pitch

The following code currently fails due to JIT not supporting the summarization of tensor lists:

```
from typing import List
import torch

def test_func(x: List[torch.Tensor]) -> torch.Tensor:
    return sum(x)

test_input = [torch.randn(1,2,4,4) for i in range(5)]

out_test = test_func(test_input) # Works

jit_test = torch.jit.script(test_func) # Fails

out_jit = jit_test(test_input)
```

It would be nice if JIT would work here for use cases like these.

### Alternatives

_No response_

### Additional context

This feature already works in normal PyTorch and it's simple enough that many would probably expect it to work in JIT.
Repository: godot
Issue: Visual Particle Shader overrides Transform in Process
Labels: bug,topic:shaders,topic:particles

### Godot version

4.0.dev.custom_build [9f058674a]

### System information

Windows 10, Ryzen 5 2600, GTX 1060, Vulkan

### Issue description

The visual shader editor for particles resets the particle transform to the generated matrix in the process function. I'd expect it to work like the start function where it generates a transform and multiplies it by the original transform. 

This is code generated for rotation and scale respectively in the start function
`TRANSFORM *= __build_rotation_mat4(vec3(0, 1, 0), n_out4p0);`
`TRANSFORM *= mat4(vec4(n_out5p0, 0, 0, 0), vec4(0, n_out5p0, 0, 0), vec4(0, 0, n_out5p0, 0), vec4(0, 0, 0, 1));`

This is a generated scale operation in the process function
`TRANSFORM = mat4(vec4(n_out2p0, 0, 0, 0), vec4(0, n_out2p0, 0, 0), vec4(0, 0, n_out2p0, 0), vec4(0, 0, 0, 1));`

### Steps to reproduce

If you plug any values into the scale or rotation inputs in the visual shader editor's process function in particle mode the transform will be reset. 

### Minimal reproduction project

[reproduction_project.zip](https://github.com/godotengine/godot/files/7794794/reproduction_project.zip)
Repository: rust
Issue: confusing warnings when the arguments to matches!() are backwards
Labels: A-diagnostics,T-compiler

Here's a minimized example of a mistake I made today ([playgrond link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=74953874e096705cd0213487de68b86c)):

```rust
fn main() {
    let x = Some(false);
    let y = matches!(Some(true), x);
    dbg!(y);
}
```

The intent there is for the match to fail, so `y` should be false. However, `y` is true! The issue is that I've screwed up the argument order for `matches!()`; it's supposed to be expression+pattern, and I've written pattern+expression. Unfortunately, my pattern is a valid expression, and my expression is a valid pattern (a trivial pattern that matches anything).

Here are the warnings rustc 1.57.0 emits for this code:

```
warning: unused variable: `x`
 --> src/main.rs:2:9
  |
2 |     let x = Some(false);
  |         ^ help: if this is intentional, prefix it with an underscore: `_x`
  |
  = note: `#[warn(unused_variables)]` on by default

warning: unused variable: `x`
 --> src/main.rs:3:34
  |
3 |     let y = matches!(Some(true), x);
  |                                  ^ help: if this is intentional, prefix it with an underscore: `_x`
```

That's pretty confusing, because it sure _looks_ like `x` is being used. Maybe this would be a good candidate for a special case warning, sort of like the special case "pattern binding ___ is named the same as one of the variants of the type ___" warning that was recently added for the common "forgot to scope my enum variants" mistake in `match` statements. In this case with `matches!`, we might want a warning anytime a binding is created without an attached `if` clause? And maybe similarly a warning anytime the pattern is trivial?
Repository: flutter
Issue: [Proposal] Multiline TextField should support both submit and enter a newline
Labels: a: text input,c: new feature,platform-android,platform-ios,framework,c: proposal,P3,team-framework,triaged-framework

Related but closed: https://github.com/flutter/flutter/issues/18439

The keyboard opened from this has a done button (on _most_ devices...), and visually has multiple lines. It however has no newline key anymore, so you can't manually enter newlines. See https://github.com/flutter/flutter/issues/18439#issuecomment-762781393.

```
TextField(
  maxLines: 5,
  keyboardType: TextInputType.text,
  textInputAction: TextInputAction.done,
),
```

The keyboard opened from this has a newline button, but cannot be submitted. Not only that, on iOS, you have no native back button and cannot close the keyboard as the user unless there is a another widget which requests focus which is on screen you can tap. On Android, the native back button will NOT fire `onSubmitted` or `onEditingComplete`, so while you can close the keyboard. Similarly, unless there is another way to change the focus, every time you do anything the keyboard will re-open with this TextField focused. See https://github.com/flutter/flutter/issues/18439#issue-331833498

```
TextField(
  maxLines: 5,
  onEditingComplete: () {
    print("As far as I can tell, this cannot fire. There is no done or submit button");
  },
  onSubmitted: (s) {
     print("As far as I can tell, this cannot fire. There is no done or submit button");
  },
),
```
Repository: go
Issue: proposal: strings: add new functions to deprecate strings.{Trim/TrimRight/TrimLeft} to avoid mistakes
Labels: Proposal,Proposal-Hold

Hi, could we add new methods to solve the problem of `cutset` type in Strings.{Trim/TrimRight/TrimLeft}.


Apparently, many gohpers misunderstood the this `cutset` type, and it cauese some bugs. And, there're several proposals for solving the `cutset` type problem:
- https://github.com/golang/go/issues/46533
- https://github.com/golang/go/issues/47822

I read through this proposals and see the conclusion is no change will be made.

This `cutset` problem affects many developers:
- if we have known the problem already, we may not make the same mistake again. 
- but if we doesn't know it in advance, we may likely make the mistake.

In python, `str.{strip/rstrip/lstrip}('cutset')` method works the same as in go `strings.{Trim/TrimRight/TrimLeft}(s, "cutset")`. Maybe this signature is ok.

If we:
- add new methods strings.{TrimCutset\TrimRightCutset\TrimLeftCutset}, and add `//Deprecated` and `go:linkname` on strings.{Trim/TrimRight/TrimLeft}, we may make this clearer
- or add new methods strings.{TrimCutset\TrimRightCutset\TrimLeftCutset}, and declare the `cutset` as []rune, and use this methods to reimplement strings.{Trim/TrimRight/TrimLeft}