sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: FancyZones does not place window in zone unless you drag a mouse
Labels: Issue-Bug,FancyZones-Layouts,Priority-3

### Microsoft PowerToys version

0.66.0

### Installation method

PowerToys auto-update, Microsoft Store

### Running as admin

No

### Area(s) with issue?

FancyZones

### Steps to reproduce

1. Have FancyZone
2. Setup zones
3. Place any window inside any zone
4. Hold the window by mouse
5. Press Shift key
6. Nothing happens

But if you drag window by at least one pixel - window snaps correctly

https://user-images.githubusercontent.com/12271104/212610152-e326b997-e0cf-4664-a4ff-218ba267a357.mp4

### ✔️ Expected Behavior

Window snaps to zone correctly

### ❌ Actual Behavior

Window does not snap unless you drag it

### Other Software

Windows 11 latest stable.

The bug happens in all windows of apps of all types (UWP, Win32, WinUI 2/3).
Repository: flutter
Issue: [desktop] Chinese characters cannot be input when TextField is surrounded by ToolTip
Labels: a: text input,engine,platform-mac,platform-windows,a: desktop,has reproducible steps,P2,found in release: 3.7,team-text-input,triaged-text-input

During development, we found that when "TextField" was wrapped by "ToolTip" chinese input could not be performed normally.

The code is simple：
```
Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Tooltip(child: TextField(),message: "1",),
            Tooltip(child: TextField(),message: "2",),
            Tooltip(child: TextField(),message: "3",),
            Tooltip(child: TextField(),message: "4",),
          ],
        )
```

The result is：

https://user-images.githubusercontent.com/4360198/212610715-7e82a2cd-f8b9-4472-b69f-4eee9ff27b1d.mp4

After testing, it was found that，there are problems in version 3.3.10 and version 3.3.9, but there are no problems in version 3.3.8
Repository: create-react-app
Issue: It does not run on DigitalOcean Droplet
Labels: needs triage,issue: bug report

When I try to execute `create-react-app` on my DigitalOcean Droplet with 512 MB RAM, it keeps aborting when installing `react-scripts`. Maybe there should be a flag to specify the maximum memory usage when executing the command. 

See [this question on SO](https://stackoverflow.com/questions/75130574/is-my-server-too-weak-for-create-react-app)
Repository: material-ui
Issue: [Switch] onBlur not working for mobile devices
Labels: component: switch,browser: Safari

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/s/elated-sanderson-frv36i?file=/src/App.tsx

Steps:

1. Open link on any Ipad or Iphone
2. Open console in codesandbox
3. Tap Switch

### Current behavior 😯

There should be log in console "onBlur fired" but there isn't one. 

### Expected behavior 🤔

You should see logged text in console

### Context 🔦

Usually throughout our app we use onChange for handling local state and onBlur for calling api for saving data.
My question is it a bug or it is expected behavior and we need to find another workaround for handling saving data 

### Your environment 🌎

_No response_
Repository: tensorflow
Issue: Generate flatbuffer files during build
Labels: type:feature,TF 2.11

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Feature Request

### Have you reproduced the bug with TF nightly?

Yes

### Source

source

### Tensorflow Version

any

### Custom Code

No

### OS Platform and Distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

```shell
Currently the output of the flatbuffer schema files are committed to the sources. This makes PRs updating the flatbuffer version and schema changes very big (see e.g. https://github.com/tensorflow/tensorflow/commit/bf0901b663e87f081c7a317fe1ac705ab1a2df8b) and also requires users to build against the exact same flatbuffer version. This may be an issue when an another version already exists which then fails the build. Even flatbuffers 2.0.6 vs 2.0.7 is so different they are not compatible.

If the flatbuffer C++files/headers etc. were generated during the build process this would be much easier and even avoids trouble when it was forgotten to update the generated files on schema changes.
```


### Standalone code to reproduce the issue

```shell
Build
```


### Relevant log output

_No response_</details>
Repository: godot
Issue: Godot 4 Beta 12: 3d camera attributes do not work in viewport with a transparent background. 
Labels: bug,topic:rendering,topic:3d

### Godot version

4.0 Beta 12

### System information

Win 10, RTX 2070 mobile

### Issue description

in a 3d scene, when I insert a viewport node with a viewport camera, and add camera attributes (like DoF) to that viewport camera I will see the effects in the editor but when I run the game, the viewport shows nothing. Otherwise when the attributes are cleared the viewport works fine.

### Steps to reproduce

start a 3d scene
create a 3d cam
add a viewport container node
add a subviewport node as a child of it
in the subviewport node, check Transparent BG
add another 3d camera as a child of the viewport
add a mesh object in front of the viewport camera
add camera attributes to the viewport camera, enable Near DoF and see the effects of the DoF in the editor
Run the game - the mesh is not visible

### Minimal reproduction project

[viewport_issue.zip](https://github.com/godotengine/godot/files/10424683/viewport_issue.zip)
Repository: godot
Issue: Localized `application/config/name_<lang>` project setting doesn't respect platform-specific feature overrides for the _target_ platform
Labels: bug,platform:ios,platform:android,platform:macos,topic:export

### Godot version

3.5.1

### System information

macOS 

### Issue description

override the name in project settings for different platforms doesn't work.

### Steps to reproduce

set the project name 
application/config/name to game

set
application/config/name_zh to game_zh 

set 
application/config/name_zh.Android to game_zh_android

the app name run on Android device is game_zh not game_zh_android


### Minimal reproduction project

N/A
Repository: next.js
Issue: Invariant: attempted to hard navigate to the same URL
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information


node > 14

NextJS 13.1.1

### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/floral-glitter-3mp1x0?file=%2Fnext.config.js&selection=%5B%7B%22endColumn%22%3A1%2C%22endLineNumber%22%3A11%2C%22startColumn%22%3A1%2C%22startLineNumber%22%3A11%7D%5D

CodeSandbox example here


just try to visit any 404 URL like /en/reset-password

and invariant will trigger

### Describe the Bug

Am trying to use a middleware to redirect users using localization middleware

Everything works fine until I implement a 404.tsx page
which results in showing  
```
Invariant: attempted to hard navigate to the same URL
```

for the 404 pages ( only when using 404.tsx )

### Expected Behavior

To show 404 without any error similar

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: angular
Issue: [platform-server]: support shadow DOM and custom elements
Labels: feature,area: server,feature: under consideration

# 🚀 Feature request


#### What modules are relevant for this feature request?
<!-- ✍️edit: -->
- [ ] aspnetcore-engine
- [ ] builders
- [x] common
- [ ] express-engine
- [ ] hapi-engine
- [ ] module-map-ngfactory-loader

### Description
<!-- ✍️--> A clear and concise description of the problem or missing capability...
Angular Universal should be able to handle shadow DOM v1 and custom elements as part of it's SSR capabilities. This is probably going to be related to [domino angular/universal#160](https://github.com/fgnass/domino/issues/160), shouldn't necessarily be. 

### Describe the solution you'd like
<!-- ✍️--> If you have a solution in mind, please describe it.
Either Angular Universal works with [domino](https://github.com/fgnass/domino) to support this use case or an avenue is created to use something like [@skate/ssr](https://github.com/skatejs/skatejs) or [jsdom](https://github.com/jsdom/jsdom) both of which support SSR on custom elements and shadow DOM v1. 

This should work out of the box as `ViewEncapsulation.ShadowDOM` is a built-in feature of Angular and this package cannot be said to be complete without supporting that.

### Describe alternatives you've considered
<!-- ✍️--> Have you considered any alternative solutions or workarounds?
The only other option is to abandon Angular Universal as a solution in this problem space.
Repository: storybook
Issue: [Bug]: Unable to access context in docs.container
Labels: bug,addon: docs

### Describe the bug

Hi,

We were running v7 beta 13 and just tried updating to beta 28. We use the `docs.container` to wrap-up a repeated documentation introduction. We are now unable to read from `context.storyById()`, where we get the following error:

```
Error: No primary story defined for docs entry. Did you forget to use `<Meta>`
```

This is despite our `*.mdx` file containing `<Meta of={Stories} />` line.

### To Reproduce

```shell
Reproduction:

https://github.com/will-stone/storybook-docs-container-bug

The offending line: https://github.com/will-stone/storybook-docs-container-bug/blob/main/.storybook/preview.jsx#L4

The MDX file with the `Meta` component: https://github.com/will-stone/storybook-docs-container-bug/blob/main/src/stories/Button.mdx?plain=1#L5
```


### System

```shell
System:
    OS: macOS 12.6.2
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 18.12.1 - ~/.local/share/nvm/v18.12.1/bin/node
    npm: 8.19.2 - ~/.local/share/nvm/v18.12.1/bin/npm
  Browsers:
    Chrome: 108.0.5359.124
    Firefox: 108.0.2
    Safari: 16.2
  npmPackages:
    @storybook/addon-essentials: ^7.0.0-beta.28 => 7.0.0-beta.28
    @storybook/addon-interactions: ^7.0.0-beta.28 => 7.0.0-beta.28
    @storybook/addon-links: ^7.0.0-beta.28 => 7.0.0-beta.28
    @storybook/blocks: ^7.0.0-beta.28 => 7.0.0-beta.28
    @storybook/react: ^7.0.0-beta.28 => 7.0.0-beta.28
    @storybook/react-vite: ^7.0.0-beta.28 => 7.0.0-beta.28
    @storybook/testing-library: ^0.0.13 => 0.0.13
```


### Additional context

Being able to access context in the `docs.container` is incredibly useful, as it means we can have story-aware conditional logic in there.
Repository: stable-diffusion-webui
Issue: [Bug]: ImportError: DLL load failed while importing _ufuncs: %1 is not a valid Win32
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

Launched WebUI-User with "git pull" to update
Received ImportError: DLL load failed while importing _ufuncs: %1 is not a valid Win32 application and immediately closed

### Steps to reproduce the problem

1. Go to folder with Stable Diffusion
2. Run WebUI-User.bat
3. Error happens

### What should have happened?

WebUI should run in the console

### Commit where the problem happens

d073637e104fa7256e0b0c546b5b83a16b881b8a

### What platforms do you use to access UI ?

Windows

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

```Shell
--xformers --deepdanbooru --listen --theme dark --no-half-vae
```


### Additional information, context and logs

![BorkedAgain](https://user-images.githubusercontent.com/110208021/212692622-743525eb-a8f4-40f5-b5b2-edbddcc20937.jpg)
Repository: pytorch
Issue: test_qnnpack_add fails
Labels: oncall: mobile,module: xnnpack

### 🐛 Describe the bug

The test fails with this:
```
test_qnnpack_add (quantization.core.test_quantized_op.TestQNNPackOps) ... Falsifying example: test_qnnpack_add(
    A=(array([1.], dtype=float32), (1.0, 0, torch.qint8)),
    zero_point=127,
    scale_A=0.057,
    scale_B=0.008,
    scale_C=0.003,
    self=<quantization.core.test_quantized_op.TestQNNPackOps testMethod=test_qnnpack_add>,
)
FAIL
```

The test_qnnpack_add_broadcast fails due to similar reasons.

With a bit of code reading I found this:
- `qA.dequantize()` and `qB.dequantize()` are zero due to the scaling and a zero_point of 127
- Hence the [groundtruth C](https://github.com/pytorch/pytorch/blob/76c88364ed6ffcef41743c8370d6ff1306e0100d/test/quantization/core/test_quantized_op.py#L5914) is also zero which is passed to `_quantize` yielding `qC = [0]`
- But the `qC_qnnp.int_repr = [127]`

More intermediates:
```
qA = tensor([0.], size=(1,), dtype=torch.qint8,
       quantization_scheme=torch.per_tensor_affine, scale=0.057, zero_point=127)
qB = tensor([0.], size=(1,), dtype=torch.qint8,
       quantization_scheme=torch.per_tensor_affine, scale=0.008, zero_point=127)
qA/qB.dequantize() = tensor([0.])
qC_qnnp = tensor([0.3810], size=(1,), dtype=torch.qint8,
       quantization_scheme=torch.per_tensor_affine, scale=0.003, zero_point=0)
qC_qnnp.int_repr() = tensor([127], dtype=torch.int8)
qC_qnnp.dequantize() = tensor([0.3810])
```


### Versions

PyTorch 1.12.1

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: terminal
Issue: wt new-tab open near current tab
Labels: Help Wanted,Product-Terminal,Issue-Task,Area-Commandline,good first issue

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

I have a Bash function that opens a tab with PowerShell in the current directory:

```sh
vspwsh ()
{
    wt new-tab --profile "Developer PowerShell for VS 2017" --startingDirectory .
}
```

I'd like this to place the new PowerShell tab next to the Bash tab in which I run the command.  That way, it would be easier for me to keep track of the purpose of each tab, keeping tabs near each other when they are for working on the same directory.

This is somewhat related to <https://github.com/microsoft/terminal/issues/3158> but would not depend on any escape sequences emitted by the shell.

# Proposed technical implementation details (optional)

Add a `--near-current-tab` option to `wt new-tab`. When specified, use the WT_SESSION environment variable to find the session, tab, and window in which the command was run, and place the new tab near that one.

If both `--near-current-tab` and `--window` are specified, then ignore WT_SESSION and instead use the selected tab of the specified window.
Repository: rust
Issue: `unnecessary parentheses around type` in attribute macro
Labels: A-diagnostics,T-compiler,D-papercut,A-proc-macros,L-unused_parens

### Code

Since this is related to proc_macro reproducing is slightly troublesome. The original problem originated here: https://github.com/lesurp/OptionalStruct/blob/master/tests/nested.rs

Simplified call site:
```Rust
struct Foo;
struct Baz;

#[optional_struct]
struct Bar {
    #[optional_rename(Foo)]
    log_config: Baz,
}
```
Note that the macro is **not** a `derive` macro (and the attribute `optional_rename` not a derive macro helper attributes).

### Current output

```Shell
warning: unnecessary parentheses around type
 --> tests/reverse_wrapping.rs:7:22
  |
7 |     #[optional_rename(Foo)]
  |                      ^                 ^
  |
  = note: `#[warn(unused_parens)]` on by default
help: remove these parentheses
  |
7 -     #[optional_rename(Foo)]
7 +     #[optional_renameFoo]
  |
```


### Desired output

```Shell
No warning.
```


### Rationale and extra context

The parentheses are read as part of the type, but they are part of the attribute definition.

### Other cases

_No response_

### Anything else?

_No response_
Repository: flutter
Issue: Document all platform-specific `path_provider` paths
Labels: d: api docs,p: path_provider,package,team-ecosystem,P3,triaged-ecosystem

<!-- 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
-->

## Use case

I'm learning Flutter and I want to write a simple JSON file. https://docs.flutter.dev/cookbook/persistence/reading-writing-files directs me to `path_provider`. I'm learning via MacOS, so I copied the sample code into a new project and ran it and it seemed to work. However, I also want to look at the file generated by my `CounterClass`:

```dart
class CounterStorage {
  Future<String> get _localPath async {
    final directory = await getApplicationDocumentsDirectory();

    return directory.path;
  }

  Future<File> get _localFile async {
    final path = await _localPath;
    return File('$path/counter.txt');
  }
```
I'm not sure where this file ended up on my hard drive and the docs at https://pub.dev/packages/path_provider don't tell me. I tried clicking GitHub links to looks through the source code but `platform_path` seems to delegate to `path_provider_macos` which seems to use `path_provider_platform_interface` which seems to be a base class but also looks like it has an implementation that's calling out to some swift code via some messages.g.dart and that's where I got stuck. I *think* I can add a print statement to my app but I'm still super new to this and not much past copy/paste/try to understand mode and that would would only work for this platform. 

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching something showing what you are imagining:
      * images
      * videos
      * code samples

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->

Please document where files created with this abstraction end up on target platforms, perhaps in https://github.com/flutter/plugins/blob/main/packages/path_provider/path_provider/README.md .
Repository: TypeScript
Issue: Optional properties on function interface breaks inference of type parameters
Labels: Bug,Help Wanted

# Bug Report

### 🔎 Search Terms

function interface optional properties generics type parameters inference

### 🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about type inference.

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.9.4#code/JYOwLgpgTgZghgYwgAgGIFcQIIIB4AqAfMgN4CwAUMsgBRxQDmAXMvgJQsBuA9sACYBuSgF8hFSqEixEKDFgBCBYuSq16zVh2Q9+Y6gA8A-CwDOYKKAZjRlSgm4gzybuinZkAXmQEANIRowmAgscjhKPsjqLOyeyjYU9o5gzq7Q8p7e+H4BQSFBikQRUZqxpPGJTqAg0BkEyBD6kCB8JsgA5HBtyAA+7QBGXb1tCG3+CH0sdIzRbKU6fLMecWKULm40VdARUxodg-1ti3FsYmtpGyDVUNvFez0HR2UnyAD0L-VQUNxQlEA)

### 💻 Code

```ts
interface FuncA<T> {
  (arg: T): void;
};

interface FuncB<T> {
  (arg: T): void;
  x?: string;
};

const outerA = <T,>(func: FuncA<T>, arg: T) => {};
const outerB = <T,>(func: FuncB<T>, arg: T) => {};
const inner = <T extends 'a' | 'b' | 'c'>(cb: (arg: T) => void) => {};

outerA(inner, (arg: 'a' | 'b') => {});
outerB(inner, (arg: 'a' | 'b') => {}); // error
```

### 🙁 Actual behavior

In the call to `outerA()`, the type of the `func` parameter is inferred as `FuncA<(arg: 'a' | 'b') => void>`, as determined by the type of the `arg` parameter.

In the call to `outerB()`, the type of the `func` parameter is inferred instead as `FuncB<(arg: 'a' | 'b' | 'c') => void>`, using the base constraint of `inner`'s `T` parameter rather than the subtype of that constraint used by the `arg` parameter.

### 🙂 Expected behavior

I do not expect the addition of an optional property on `FuncB<T>` to break the type parameter inference. It seems that `inner`'s `T` parameter should be inferred as `'a' | 'b'` in both cases.
Repository: vscode
Issue: Add multi cursor support but with Tab stops-like behavior
Labels: feature-request,editor-multicursor

<!-- ⚠️⚠️ 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. -->
I'm unsure if this is already possible. My apologies if it is as I haven't found a way to achieve this yet.

Let's say I'm working on an HTML document, and have 50 elements already created but realized I should change the class of 8 of them. I would have to manually move the cursor to each tag's class attribute each time I make a change to it. 

What I would like to be able to do is click on each tag's class attribute,  just as if I was adding multiple cursors, but instead of adding a cursor, add a "stop point", so I can then edit the first tag class name, hit tab, and have my cursor move to the next one I want to edit without having to manually move the cursor to it.

If it's already possible, I'd like to know how to do it as I haven't found the right search term to find the answer:)