sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: Add functionality to settings `Open JSON file` entry to open the settings.json parent folder in Explorer
Labels: Help Wanted,Product-Terminal,Issue-Task,good first issue,Area-SettingsUI

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

*(this is a follow up to this issue #1460)*

I have Windows Terminal latest stable, v1.12.10334.0 , on win11.

Currently, in the dropdown menu | 'Settings', there's an `Open JSON file` entry, clicking which opens the settings.json file only if the user has associated the .json file type with an installed editor, otherwise it shows the "Do you want to open this file?" windows dialog .
<details>
<summary>screen capture: </summary>

![](https://user-images.githubusercontent.com/723651/152614540-bc2294dc-597e-4f37-a8a9-c0a9589e5197.gif)
</details>

If you close the dialog, in order to manage to open the settings.json file manually, you'll have to look in the project [wiki FAQ](https://github.com/microsoft/terminal/wiki/Frequently-Asked-Questions-(FAQ)#where-can-i-find-the-settings-file) to find its location/path - there's no related info shown inside the app.  

So, my suggestion is add functionality to "Open JSON file" settings entry to open the settings.json parent folder in Explorer.

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->

In details, my suggestion is, when clicking the `Open JSON file` entry, instead of attempting to open settings.json with the associated editor, to display a menu with two entries:
- `Open settings.json with associated editor`
- `Open parent folder of settings.json in Explorer` (in order to be able to open it manually).

&nbsp;
Or, alternatively/more simply, keep the current behavior (=attempt to open the file with the associated editor when leftclicking the "Open JSON file" entry), but when *rightclicking* it, to open its parent folder in file explorer (and update the entry `tooltip` respectively).
Repository: vscode
Issue: Multi-line Highlight
Labels: feature-request,editor-rendering

Issue Type: <b>Bug</b>

Good evening, 

Since the latest VS Code update (1.64, Jan. 2022), when I add multiple cursors to different lines, the editor highlights every line having a cursor on it. The highlighting on these extra lines is too obtrusive and makes it harder to see other cursors and the code on the highlighted lines, especially since the highlight borders overlap each other on adjacent lines. I would like to have the old behavior back (i.e., only the initial line containing a cursor is highlighted and any other lines with extra cursors are not highlighted).

The old behavior: 

![image](https://user-images.githubusercontent.com/60623875/152619525-8e89364d-cba6-4e75-8a40-7c34a5b8e550.png)

The new behavior: 

![image](https://user-images.githubusercontent.com/60623875/152619086-3019586e-45f3-4e37-94a2-039d22091212.png)

Thank-you for your time!

VS Code version: Code 1.64.0 (5554b12acf27056905806867f251c859323ff7e9, 2022-02-03T04:22:20.678Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No


<!-- generated by issue reporter -->
Repository: flutter
Issue: Missing integration tests for Flutter on Android
Labels: a: tests,platform-android,engine,P2,team-android,triaged-android

There are a few scenarios that don't have integration tests. 
Due to the lack of tests, customers get bugs that are fatal in many cases. e.g. application crash.

We just had one of these issues recently.

Some scenarios:

- [ ]  **Flutter Surface destroyed**.  Recent issues: http://b/216410309 `Shell::OnPlatformViewDestroyed` followed by `Shell::OnPlatformViewCreated`. 
 This can happen when the app is sent to the background or the app switch is toggled, then the app is brought to the foreground.
- [ ] **Flutter Activity lifecycle events**: pause, stop, destroy, restart, etc.. All these things aren't tested to my knowledge.
- [ ]  **Flutter Fragment**. This is mostly used in add-to-app scenarios. The fragment is added to an activity that isn't Flutter Activity in the host app.
- [ ]  **Cached/Shared engines**. This is mostly used in add-to-app scenarios. A single FlutterEngine instance is shared across multiple FlutterActivity or FlutterView instances.
- [ ]  **Texture layers**. For example: a video like the video_player plugin.
- [ ]  **Platform views interleaved with each of the above scenarios**. For example, an app that has multiple Activities. One might be FlutterActivities, while others aren't. We should be testing switching between activities.
- [ ]   **StrictMode** e.g. `detectLeakedClosableObjects()`, maybe others too.
- [ ]   **Status bar**. Recent issues: http://b/223628114, https://github.com/flutter/flutter/issues/100027
- [ ]   **Platform view that renders a SurfaceView**,  Recent issues: http://b/226467394, https://github.com/flutter/flutter/issues/100669

To begin, these scenarios should leverage Android emulators, so they can run on presubmit checks. They should also run as part of the *engine* presubmit checks.

cc @GaryQian 

cc @godofredoc @keyonghan  I believe there was a plan to run some frameworks tests in the engine. Could we run these in the engine once added?
Repository: kubernetes
Issue: APF does not resize final work when not queuing
Labels: kind/bug,sig/api-machinery,priority/important-longterm,lifecycle/frozen,triage/accepted

### What happened?

While reviewing the code in queueset.go, I noticed that the block of code that resizes the final work if it is too wide (`if oldestReqFromMinQueue.workEstimate.FinalSeats > uint(qs.dCfg.ConcurrencyLimit) ...`) appears only in `findDispatchQueueLocked` --- not also in the no-queuing code path (`dispatchSansQueueLocked`).

### What did you expect to happen?

Since the resizing is about the execution phase rather than the queuing phase, I expected it to apply regardless of whether there is queuing.

### How can we reproduce it (as minimally and precisely as possible)?

Read the code.

### Anything else we need to know?

/sig api-machinery
@wojtek-t 
@tkashem 
@deads2k 
@lavalamp 

### Kubernetes version

<details>
current
</details>


### Cloud provider

<details>
N/A
</details>


### OS version

<details>
N/A
</details>


### Install tools

<details>
N/A
</details>


### Container runtime (CRI) and and version (if applicable)

<details>
N/A
</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>
N/A
</details>
Repository: pytorch
Issue: ArgMax for Multi Dimensional Tensor
Labels: feature,triaged,module: ux,module: reductions

### 🚀 The feature, motivation and pitch

argmax() function reshapes a multi-dimensional tensor to find the maximum location. Instead, there can be requirement to get max value in given form like: 
'''
>>>print(A.shape)
torch.Size([2, 2, 2, 2,2 ,2])
>>>print(A.argmax())
tensor(7)
>>>print(A.argmax_multi()) #Proposed
tensor([1, 0, 0, 1,0 ,1])
'''


### Alternatives

_No response_

### Additional context

_No response_
Repository: flutter
Issue: Android embedding migration docs not up to date with splash screen config
Labels: platform-android,engine,d: wiki,P2,team-android,triaged-android

I just got this documentation linked by the CLI that I apparently had to migrate the embedder:
https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects

However in step 4 of the wiki link above it seems to use pre-2.5 splash screen configuration. See this doc on splash screen migration in 2.5:
https://docs.flutter.dev/development/ui/advanced/splash-screen#migrating-from-manifest--activity-defined-custom-splash-screens

I understand the reason as the embedder doc is older than 2.5, but I got it shown first when I upgraded to 2.10.
Repository: godot
Issue: Cannot get region of a spritesheet for a frame when using SpriteFrames
Labels: bug,topic:core,needs testing

### Godot version

3.4.2

### System information

PopOS

### Issue description

1. You create a large sprite sheet
2. You create an AnimatedSprite then create the SpriteFrame and 'add frames from a region'
3. You select your sheet and create your animation

In code you want to grab a texture of the current frame, or even just the first frame, e.g.

```gdscript
var tex=$AnimatedSprite.frames.get_frame("normal",0)
var size=tex.get_size()
```

size is correct and holds the size, e.g. 64x64

However, unless I'm missing something, tex contains the entire sprite sheet and there is no data holding the rect/region where the sprite is. 

```gdscript
var img_tex = ImageTexture.new();
img_tex.create_from_image(tex.get_data().get_rect(?????????),0);
```

The only place I can find it is inside the scene file, e.g.

```gdscript
[ext_resource path="res://assets/graphics/sheet_sprites.sprites/turrets_original.tres" type="Texture" id=5]
[sub_resource type="AtlasTexture" id=11]
atlas = ExtResource( 5 )
region = Rect2( 256, 1092, 64, 64 )
```

But this is not referenced in the animated sprite or the sprite frame.

Note, I am using .tres files to represent individual regions within the sprite sheet so my 'add frame from region' points to my .tres file not the whole sprite sheet, but texture still returns the whole sprite sheet, so the same problem occurs.

### Steps to reproduce

As description

### Minimal reproduction project

_No response_
Repository: tensorflow
Issue: Extremely slow grads computation in dilatied convlution with a large dilation rate
Labels: type:performance,comp:core,TF 2.9

<em>Please make sure that this is a bug. As per our
[GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md),
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template</em>

**System information**
- Have I written custom code (as opposed to using a stock example script provided in TensorFlow):Yes
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04):Linux & Windows & colab
- TensorFlow installed from (source or binary):pip
- TensorFlow version (use command below): 2.7, 2.8rc, 2.8
- Python version: 3.8
- GPU model and memory: Titan RTX

https://colab.research.google.com/drive/1-64VeSW-3SB3rS4mrzUzU1FnubX5TvnD?usp=sharing

Suggest to try both CPU and GPU.

In CPU mode, large dilation rate can run 100x slower than smaller rate.
Repository: flutter
Issue: [Windows] Proposal to add missing TextField behaviours related to mouse clicks, autoscroll using mouse and with keyboard and combination keys.
Labels: a: text input,c: new feature,framework,engine,platform-windows,c: proposal,a: desktop,a: mouse,P3,team-windows,triaged-windows

### Consecutive mouse clicks for selection
- [working] - Double click to select the word
- [missing] - Triple click to select the paragraph
- [missing] - Four click to select the whole TextField

### Autoscroll while selection with mouse
- [missing] - While selecting and dragging the mouse, whenever mouse pointer goes beyond the lower boundary or upper boundary, TextField should autoscroll and selection should proceed further in respective direction. At present it is not possible to select the text with mouse which is beyond visible limit.

### Autoscroll while selection with keyboard
- [missing] - While selecting and proceeding further with Shift key + Arrow keys, if selection goes beyond visible limit TextField should scroll. At present textselection is proceeding but TextField does not scrolling in respective direction.

### Combination keys
**- [working] - Home key -**  to put cursor to line start
**- [missing] - Control key + Home key -** to put cursor to start of the TextField and scroll to it
**- [working] - End key -** to go to line end
**- [missing] - Control key + End key -** to put cursor to end of the TextField and scroll to it
**- [working] - Shift key + Home key -** to select Text between cursor and line start
**- [missing] - Control key + Shift key + Home key -** to select text between cursor and TextField start and scroll to start offset
**- [working] - Shift key + Home key -** to select Text between cursor and line start
**- [missing] - Control key + Shift key + End key -** to select text between cursor and TextField end and scroll to bottom offset


### Tested on
Platform - Windows
Flutter - 2.8.1, channel - stable

Regards,
Sagar
Repository: opencv
Issue: OpenCV2 and iOS - Cannot build 
Labels: category: build/install,platform: ios/osx

I am having this error while building:
`building for ios simulator, but the linked and embedded framework "opencv2.framework" was built for ios.` 

- Xcode 13.2.1 

I downloaded opencv2 version 4.5.5 and executed:
`python opencv/platforms/ios/build_framework.py ios`
Imported the output framework to Xcode but getting this error:

<img width="425" alt="image" src="https://user-images.githubusercontent.com/6886116/152645858-e9bfa45e-51d4-460c-bdad-90dba680b727.png">
Repository: excalidraw
Issue: Color gradient feature (if possible)
Labels: enhancement

A great idea will be the option to fill the background with a linear or radius gradient. It will be great!
Repository: electron
Issue: [Bug]: GetVSyncParametersIfAvailable() failed for 1 times!
Labels: platform/linux,bug :beetle:,bug/regression :leftwards_arrow_with_hook:,blocked/upstream ❌,status/confirmed,has-repro-gist,17-x-y,18-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

17.0.0

### What operating system are you using?

Other Linux

### Operating System Version

Debian GNU/Linux 11 (bullseye)

### What arch are you using?

x64

### Last Known Working Electron version

16.0.8

### Expected Behavior

The command `npm start` runs electron smoothly without any errors.

### Actual Behavior

The command logs out this:

```
> dinobrowse@1.0.0 start
> electron .

[20676:0204/182046.077429:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[20676:0204/182047.144782:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[20676:0204/182047.158435:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
```

### Testcase Gist URL

https://gist.github.com/1787a7f55987914d30b12cc0e4956b7b

### Additional Information

_No response_
Repository: terminal
Issue: Update Actions, Color Schemes pages in SUI to match Controlsv2 style
Labels: Issue-Feature,Product-Terminal,Priority-1,Area-SettingsUI

### Windows Terminal version

1.13.10336.0

### Windows build number

10.0.19044.0

### Other Software

_No response_

### Steps to reproduce

- open SUI and maximize terminal or `Close Navigation` (maximized is move visible)
- go to `Defaults` or `Rendering`

### Expected Behavior

- text aligns with other SUI elements

### Actual Behavior

![wt_sui_align](https://user-images.githubusercontent.com/3933920/152649836-fe5dbad2-09e5-4d3a-a582-f63fed82b038.png)
Repository: transformers
Issue: Porting Compressive Transformer to Huggingface
Labels: New model

# 🌟 New model addition

As part of my Master-Thesis I will implement or adapt different transformer architecture for LM that are specifically designed for long-context situation. As part of this I started with porting the Compressive Transformer to the huggingface interface. And will probably do the same for other architectures in the future. Let me know if you're interested for a pull-request.

## Model description
[Paper](https://arxiv.org/pdf/1911.05507.pdf)

The Compressive Transformer is an extension of the Transformer-XL architecture with an additional compressed memory. Memories that would get discarded in the Transformer-XL get compressed and added to the compressed memory. 
The compression function can take different forms but the best performance on word-level LM is a Conv1d compression. 
Training of the C-Transformer happens the same way to how the Transformer-XL architecture is trained. But additional to that there is an "attention-reconstruction-loss" which compares the attention that we get from using the memory with the attention we get from its compressed counter-part. Using the MSE-loss we can perform gradient updates on the compression function


## Open source status

* [x] the model implementation is available: 
https://nn.labml.ai/transformers/compressive/index.html Is an open source implemention under the MIT license
https://github.com/deepmind/pg19 The data-set used in parts of the experiment by the Authors
https://github.com/vilmarzti/long_context_transformers/blob/main/longcontext/transformers/compressive_transformer.py My humble start of porting the architecture to the huggingface-format.
* [x] the model weights are available: 
None that I could find.
Weights (for wikitext-2 and 103) might become available as my thesis progresses and I start training
* [x] who are the authors: 
Jack W. Rae (https://github.com/dm-jrae)
Anna Potapenko (https://github.com/AnyaP)
Siddhant M. Jayakumar (github-profile not found)
Chloe Hillier (github profile not found)
Timothy P. Lillicrap (github profile not found)
Repository: godot
Issue: `Camera2D` bug when zooming to minus value with `Rotating` on.
Labels: bug,topic:core,topic:2d

### Godot version

3.4.3rc1, 4.0.alpha

### System information

Win10

### Issue description

When enable `Rotating` and zoom x to a minus value, Camera2D will get a strange view rectangle:
![camera2d](https://user-images.githubusercontent.com/12966814/152650540-5fc38421-0bd1-4bf5-894c-2c79a75bc51b.gif)



### Steps to reproduce

Create a Camera2D, enable `Rotating` and drag `zoom-x`  to a minus value.

(If I zoom to `-1,-1`, the view should be flipped relative to `1,1` no matter it is rotating)

### Minimal reproduction project

_No response_
Repository: material-ui
Issue: [TextField] defaultProps seems to be ignored when React.hydrate is used in SSR setup with Remix
Labels: bug 🐛,component: text field

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

I used [Remix + MUI example](https://github.com/mui-org/material-ui/tree/master/examples/remix-with-typescript) as my base and the only change I did is in the `theme` part, like this:
```ts
import { createTheme } from '@mui/material';

const theme = createTheme({
    MuiInputLabel: {
      defaultProps: {
        shrink: true,
      },
    },
    MuiTextField: {
      defaultProps: {
        InputLabelProps: {
          shrink: true,
        }
      }
    }
  },
});

export default theme;
```

In my app I then have login form which uses `TextField` component. When I disable javascript, the form looks correct, the labels are shrunk by default. When I enable javascript and reload the page, the labels are shrunk but when I focus & blur the field(s), it seems that they use the default behavior.

Also there is the following warning in the console:
```
Warning: Prop `className` did not match. Server: "MuiInputLabel-root MuiInputLabel-formControl MuiInputLabel-animated MuiInputLabel-shrink MuiInputLabel-outlined MuiFormLabel-root MuiFormLabel-colorPrimary Mui-required css-1sumxir-MuiFormLabel-root-MuiInputLabel-root" Client: "MuiInputLabel-root MuiInputLabel-formControl MuiInputLabel-animated MuiInputLabel-outlined MuiFormLabel-root MuiFormLabel-colorPrimary Mui-required css-14s5rfu-MuiFormLabel-root-MuiInputLabel-root"
```

### Expected behavior 🤔

I would expect that `defaultProps` are correctly hydrated in SSR setup.

### Steps to reproduce 🕹

Steps:

1. clone MUI repo and go to https://github.com/mui-org/material-ui/tree/master/examples/remix-with-typescript
2. change `theme` to have the changes from "Current behavior" section, add a login form to the `index` route
3. start the project with `npm run dev`, load the page and check the console

### Context 🔦

https://github.com/mui-org/material-ui/tree/master/examples/remix-with-typescript

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  System:
    OS: Linux 5.16 Arch Linux
  Binaries:
    Node: 14.18.0 - ~/.volta/tools/image/node/14.18.0/bin/node
    Yarn: 1.22.17 - ~/.volta/tools/image/yarn/1.22.17/bin/yarn
    npm: 6.14.15 - ~/.volta/tools/image/node/14.18.0/bin/npm
  Browsers:
    Chromium: 98.0.4758.80 (Official Build) Arch Linux (64-bit)
    Firefox: 96.0.3
  npmPackages:
    @emotion/react: ^11.7.1 => 11.7.1 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/base:  5.0.0-alpha.67 
    @mui/icons-material: ^5.3.1 => 5.3.1 
    @mui/lab: ^5.0.0-alpha.66 => 5.0.0-alpha.67 
    @mui/material: ^5.3.1 => 5.4.0 
    @mui/private-theming:  5.3.0 
    @mui/styled-engine:  5.3.0 
    @mui/system:  5.4.0 
    @mui/types:  7.1.0 
    @mui/utils:  5.3.0 
    @types/react: ^17.0.24 => 17.0.39 
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 
    typescript: ^4.1.2 => 4.5.5 
```
</details>
Repository: rust
Issue: `x.py bench` should consider warning/informing the user if they have a configuration that may produce slower/inaccurate benchmakrs
Labels: T-bootstrap,A-contributor-roadblock

Should `x.py bench` emit a message if settings that are bad for performance are enabled? I think my configuration was confusing me quite a bit in https://github.com/rust-lang/rust/pull/90414 -- specifically `rust.debug-info-std` (which IIUC impacts which variables get spilled to the stack) and `rust.incremental` (which impacts codegen units). There are definitely others relevant here.

Note that I do think there are reasons that you may want to have these on when running the benchmark, so it should be an unobtrusive warning or message. Alternatively, it could be configured in some way automatically, if not overridden, similar to `[proflie.bench]` in cargo.

Discussion carried over from that PR.