sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Settings editor doesn't support settings with very long descriptions well like terminal.integrated.commandsToSkipShell
Labels: feature-request,settings-editor

This setting takes the cake for longest description at ~7000 characters. It is too long to fit in the settings UI and seems to be mostly listing defaults? Is there a reason those defaults aren't just actual defaults for the setting? For me to read the whole setting description I must click the "open default settings" link in the description and then scroll to find this setting in the list. 


cc @rzhao271 for how settings UI handles descriptions which are too long.
Repository: godot
Issue: Jumping height is inaccurate when pushing against a wall while "block on wall" is disabled for CharacterBody3D
Labels: bug,topic:physics,topic:3d

### Godot version

4.0

### System information

windows 10

### Issue description

When real_velocity is used, the jump height of a CharacterBody3D is drastically different while pushing against a wall if the "block on wall" setting is disabled.
![jumpbug](https://user-images.githubusercontent.com/10412778/223482354-d9879ede-79e9-4b25-8699-61c828c36dd9.gif)


### Steps to reproduce

run the example project. Try jumping with and without pushing against the wall. Notice the height differences.

### Minimal reproduction project

[realVelocityJumpBug.zip](https://github.com/godotengine/godot/files/10911545/realVelocityJumpBug.zip)
Repository: rust
Issue: Tracking Issue for Rustdoc Askama Migration
Labels: T-rustdoc,E-mentor,E-help-wanted,E-medium,C-tracking-issue,A-rustdoc-ui

# Tracking Issue for Rustdoc Askama Migration

[Zulip Discussion](https://rust-lang.zulipchat.com/#narrow/stream/266220-rustdoc/topic/rustdoc.20allocations.20are.20slow)

This issue is to track the progress of migrating rustdoc's HTML rendering to Askama.

## Suggested Workflow
If you'd like to work on a component, please leave a comment claiming it so that work doesn't conflict.
Work on translating the current series of `format!()` and string building calls into an HTML template. Where possible, try to keep as much logic as possible on the Rust side. Make sure to refer to [`STYLE.md`](https://github.com/rust-lang/rust/blob/master/src/librustdoc/html/templates/STYLE.md) for templating style, especially using comment blocks to minimize whitespace.

A specific example of a migration (and some style considerations) is [here](https://github.com/rust-lang/rust/pull/108784#pullrequestreview-1325314611).

## Components to Migrate

- [x] Sidebar (#108784)
- [ ] Content
    - [x] Stability/Portability/Deprecation (#108757)
    - [ ] Item (`print_item.rs`)
        - [x] Item Header
        - [ ] Doc Block
        - [ ] Modules
        - [ ] Functions
        - [ ] Traits
        - [ ] Structs
        - [x] Unions (#109925)
        - [ ] Enums
        - [ ] Typedefs
        - [ ] Macros
        - [X] ProcMacros (#112031)
        - [X] Primitives (#112032)
        - [X] Statics (#11927)
        - [ ] Constants
        - [X] Foreign Types (#112005)
        - [~~Keywords~~](https://github.com/rust-lang/rust/pull/111314#issuecomment-1537413925) 
        - [X] Opaque Types (#112034)
        - [X] Trait Aliases (#112030)
     - [ ] Scraped examples
- [ ] Source View
  - [x] Line Numbers (#109187)
  - [ ] Code Highlighting

## Implementation History

- https://github.com/rust-lang/rust/pull/86157
- https://github.com/rust-lang/rust/pull/89695
- https://github.com/rust-lang/rust/pull/92526

@rustbot label +T-rustdoc +A-rustdoc-ui
Repository: storybook
Issue: [Feature Request]: Disable Controls while Persisting Arg Values
Labels: feature request,has workaround,addon: controls

### Is your feature request related to a problem? Please describe

Hi,

My problem is that I have a modal that has a header and body text that should be updatable. However, when the modal is visible, it traps the focus, so I'm unable to type into the Storybook controls. I tried using the conditional controls, but when I do that the header and body text are removed completely, leaving my modal empty.

Here's a Loom of my scenario: https://www.loom.com/share/02ec2fec9a3f4800b80a1c5744b3ea0f

### Describe the solution you'd like

I would like to be able to either regain access to the inputs so that I can update them within the modal OR I would like the controls to be deactivated but present when the modal is visible. Conditionally rendering the controls does work, but I still need access to the arg values.

### Describe alternatives you've considered

The may be a way only to trap focus when the canvas is selected, but that's janky and would require me to hack my component in ways I probably should. I also though about persisting the previous values of the args, but that seems like an effortful work around that a feature could resolve.thought

### Are you able to assist to bring the feature to reality?

yes, I can

### Additional context

Here's the loom: https://www.loom.com/share/02ec2fec9a3f4800b80a1c5744b3ea0f
Repository: transformers
Issue: Add X-Decoder Model 
Labels: New model

### Model description

X-Decoder is a generalized decoding pipeline that can predict pixel-level segmentation and language tokens seamlessly. X-Decoder is the first work that provides a unified way to support all types of image segmentation and a variety of vision-language (VL) tasks. 

The model exhibits strong transferability to a wide range of downstream tasks in both zero-shot and fine-tuning settings, achieving state-of-the-art open-vocabulary segmentation and referring segmentation on 10 settings of 7 datasets and should be a valuable addition to transformers library

### Open source status

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

### Provide useful links for the implementation

Paper: https://arxiv.org/pdf/2212.11270.pdf
Code: https://github.com/microsoft/X-Decoder
Weights: https://huggingface.co/spaces/xdecoder/Demo/blob/main/xdecoder_focalt_last.pt

Author: @eltociear 
Cc: @NielsRogge @alaradirik
Repository: go
Issue: proposal: x/tools/.../shadow: specific cases that are unlikely to have false positives
Labels: Proposal,Analysis

I propose discussing more specific cases of variable shadowing, to allow making [`shadow`](https://cs.opensource.google/go/x/tools/+/refs/tags/v0.6.0:go/analysis/passes/shadow/) an analyzer that can be enabled by default.

## Background

I did the common thing of refactoring this code:

```go
someSlice := sliceAPizza()
// ...
eat(someSlice)
```

into

```go
var someSlice []int
if party {
  someSlice := make([]int, 0, 42)
  someSlice = append(someSlice, sliceAPizza()...)
} else {
  someSlice = sliceACucumber()
}
// ...
eat(someSlice)
```

The problem here being that `:=` and `=` are somewhat difficult to tell apart. This is a clear case of unintended shadowing. I ran the shadow analyzer, and it came up with lots of false positives for `err`, as one would expect. So enabling that is out of the question for me.

## Proposal

This made me wonder if this pattern of

```go
var a int  // A variable declaration right before a block.
for {
  // Probably means to assign to a at some point.
}
```

is something a shadow analyzer could flag without the risk of false positives.

* If there are false positives (the outer-`a`  not being used in `for`, but an inner-`a` is,) moving the outer declaration to after the block probably improves readability.
* If a mix of outer and inner `a` are used, that could be detected by checking if outer-`a` is being used at all in the block, before flagging the shadowing.

Are there other situations where shadowing is more clear than the general case currently implemented in the analyzer?
Repository: PowerToys
Issue: [Mouse Jump | idea] Hold for jump
Labels: Idea-Enhancement,Product-Mouse Utilities

### Description of the new feature / enhancement

That idea directed for better and faster using Mouse Jump in user environment, when user tired clicking, or user often using that utility.

### Scenario when this would be used?

Checkbox in mouse jump partition, below activation shortcut, unchecked by default.
You're hold activation shortcut and release for jump around screen(-s) instead clicking if that checkbox is checked.

### Supporting information

_No response_
Repository: next.js
Issue: [AppDir] Page navigation with start transition is waiting for Suspended components
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home Single Language
    Binaries:
      Node: 18.5.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.2.4-canary.5
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://github.com/vercel/next.js/files/10912131/poc-rsc.zip)

### To Reproduce

- Click the 'click me' button in the example.
- 'Please wait' text will appear
- Eventually redirection/DOM update will happen and Both time stamps on the page will update

### Describe the Bug

The page has dynamic content simulated via a 5 sec Promise.
When navigating via router/navigation APIs, and using startTransition to show user progress of the nav the behavior is as follows:
- Start Transition enables the loading state
- Transition completes only when the Suspended component that renders after async Promise is complete

This is contrary to the browser page loading behavior where the async component is under suspense and page is shown quickly. The same behavior should be available when navigating using router and transitions.

POC
[poc-rsc.zip](https://github.com/vercel/next.js/files/10912131/poc-rsc.zip)


### Expected Behavior

The expected behavior is as follows:
- Start Transition enables the loading state
- Transition should complete when the page is available to render, excluding the async/Suspended components that are under suspense
- If the async components are having a suspense boundary, the fallback should be visible
- Once the suspended components are available to render, those should be updated.

Expected behavior sample:
![image](https://user-images.githubusercontent.com/3159347/223498826-88b99413-5316-48b2-a812-716670e719bf.png)


For this example, 
- the page should not wait for 'Delayed content' completion. 
- the transition should complete with static content shown and the delayed content replaced by its suspense fallback 'loading' text.


### Which browser are you using? (if relevant)

Latest

### How are you deploying your application? (if relevant)

next dev
Repository: PowerToys
Issue: Caps & Num Lock reset
Labels: Needs-Triage

### Description of the new feature / enhancement

Set timeout to turn off caps lock and turn on num lock.

### Scenario when this would be used?

Sometimes a user will engage the Caps Lock or Num Lock, and forget that it state.  When the next go to type; either they are YELLING in all caps, or the screen goes nuts as they are trying to enter numbers.

### Supporting information

_No response_
Repository: kubernetes
Issue: Deprecated annotation `volume.beta.kubernetes.io/storage-class` still honored
Labels: kind/bug,sig/storage,lifecycle/frozen,needs-triage

### Overview

The annotation `volume.beta.kubernetes.io/storage-class`  is long deprecated, but still honored.

We should eventually stop honoring it. The annotation was never treated as stable.
### Anything else we need to know?

It's nice to emit warnings when these things are used, and then later stop honoring them (perhaps with a different warning).
Repository: pytorch
Issue: [Dynamo] HuggingFace transformers configuration_utils graph break workaround
Labels: needs reproduction,triaged,oncall: pt2,module: dynamo,dynamo-dataclasses

### 🐛 Describe the bug

HF worked around dynamo problem here https://github.com/huggingface/transformers/pull/21648/files#r1107482201

This should not be necessary, we should fix our code.

### Versions

master

cc @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @aakhundov @wconstab @ngimel @Xia-Weiwen @soumith
Repository: PowerToys
Issue: PT Run - Specify Additional Search Folders
Labels: Needs-Triage

### Description of the new feature / enhancement

I am requesting the addition of a feature that will allow users to add a collection of folders that PT Run will search/index for the types of files that it normally returns from the usual locations. This could be most easily implemented as a config file addition. A simple GUI could be used as well, perhaps as a phase 2 release.

Thank you for your consideration.

### Scenario when this would be used?

Every use of PT Run will provide all applications that are installed/located in non-C-Drive folders.

### Supporting information

I, like many I know, do not dump everything into my C drive. Thus pretty much every installation I do (that actually allows me to specify the install folder) gets put on my D drive. This is done into a Program Files and Program Files x86 folder pair. These two directories actually get flagged by Windows as "special" - having restricted access. This leads me to create an "unblocked" apps folder on the D drive as well, so that applications placed there won't break or constantly complain about not having write permissions.
Repository: excalidraw
Issue: Shadow text when editing text containers without keyboard on iOS
Labels: bug,mobile,Text containers

I recorded this issue using the #6328 PR
This effected all the browsers I tested on my iPad Pro 11 15.6.1: Safari, Edge, Chrome, Firefox; but strangely it did not effect Obsidian.md

![5FD11EF9-72C0-46CB-BCDF-9846AEEFA6D4](https://user-images.githubusercontent.com/14358394/223512288-77bd0cc3-98a5-46da-9061-17e614be99ce.png)


https://user-images.githubusercontent.com/14358394/223512094-b4bbdd8a-3605-428e-ab25-42dc016c4e1f.MOV
Repository: flutter
Issue: Add Windows 11 AMD64 machines to the Devicelab
Labels: team-infra,P2,triaged-infra

We should run framework-side Devicelab and host tests on both Windows 10 and Windows 11. This is only needed for testing; for building, Windows 10 alone is enough.

Windows 10 and 11 both have significant market share. However, Windows 11 is currently a ["best effort" platform](https://docs.flutter.dev/development/tools/sdk/release-notes/supported-platforms#best-effort-platforms) as we don't run our tests on Windows 11.
Repository: vscode
Issue: Remove the strict bounds on "Jump to line" and allow overflow to jump to the end of a file.
Labels: feature-request,quick-open

<!-- ⚠️⚠️ 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. -->

**Feature Request:** Jumping to a line (`Ctrl+G`) should not be bounded by the size of the file.

For example, jumping to line 1234 in a 1000 line file should jump to the last line rather than doing nothing, and jumping to line 0 should be the same thing as jumping to line 1.

This makes it easier to jump to the beginning and end of a file. Sometimes you don't care how large a file is and want to jump "somewhere near the end." I know that `Ctrl+Home` and `Ctrl+End` already achieve this goal, but having that functionality in a single shortcut is more ergonomic. This is also how it's done by Sublime Text, so there's admittedly some muscle memory there.
Repository: flutter
Issue: Tasks are marked as `In Progress` though no builds are scheduled
Labels: team-infra,P2,triaged-infra

Example from current TOT:

Builder `Linux web_tests_3` is marked as `In Progress` (yellow) for commit https://github.com/flutter/flutter/commit/80be2bfc9f8cc39d197f616b8ce809217908a5f8
<img width="479" alt="Screenshot 2023-03-07 at 10 30 32 AM" src="https://user-images.githubusercontent.com/54558023/223516821-6c886f1e-eeec-4501-b87e-468eef743cee.png">

However, there is no build scheduled per milo page:
<img width="1047" alt="Screenshot 2023-03-07 at 10 30 45 AM" src="https://user-images.githubusercontent.com/54558023/223516937-9457fbf4-8d3e-4ee7-a6fc-83d075201aa2.png">

This happens on random number of tasks intermittently on random commit rows. Should be a bug in the scheduler.

See original findings of this issue: https://github.com/flutter/flutter/issues/120395#issuecomment-1444810718 /cc @ricardoamador
Repository: stable-diffusion-webui
Issue: [Bug]: SwinIR upscaler producing black bars
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?

![image](https://user-images.githubusercontent.com/13378059/223522493-206e3006-cbb1-448c-bc21-9a12bde4a192.png)
specs: AMD RX 6600 XT

### Steps to reproduce the problem

Extras -> Upscaler 1 -> SwinIR 4x


### What should have happened?

full image

### Commit where the problem happens

https://github.com/lshqqytiger/stable-diffusion-webui-directml

### What platforms do you use to access the UI ?

_No response_

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
--no-half --precision full --no-half-vae --opt-sub-quad-attention --opt-split-attention-v1 --medvram --autolaunch
```


### List of extensions

<html>
<body>
<!--StartFragment-->

ultimate-upscale-for-automatic1111 | https://github.com/Coyote-A/ultimate-upscale-for-automatic1111.git | 0a3d03a4 (Tue Feb 7 06:07:23 2023) | unknown
-- | -- | -- | --
LDSR | built-in |   |  
Lora | built-in |   |  
ScuNET | built-in |   |  
SwinIR | built-in |   |  
prompt-bracket-checker

<!--EndFragment-->
</body>
</html>ultimate-upscale-for-automatic1111	https://github.com/Coyote-A/ultimate-upscale-for-automatic1111.git	0a3d03a4 (Tue Feb 7 06:07:23 2023)	unknown
LDSR	[built-in](http://127.0.0.1:7860/)		
Lora	[built-in](http://127.0.0.1:7860/)		
ScuNET	[built-in](http://127.0.0.1:7860/)		
SwinIR	[built-in](http://127.0.0.1:7860/)		
prompt-bracket-checker

### Console logs

```Shell
venv "D:\AI_ART\stable-diffusion-webui-directml\venv\Scripts\Python.exe"
Python 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:20:36) [MSC v.1929 64 bit (AMD64)]
Commit hash: ff558348682fea569785dcfae1f1282cfbefda6b
Installing requirements for Web UI
Launching Web UI with arguments: --no-half --precision full --no-half-vae --opt-sub-quad-attention --opt-split-attention-v1 --medvram --autolaunch
Interrogations are fallen back to cpu. This doesn't affect on image generation. But if you want to use interrogate (CLIP or DeepBooru), check out this issue: https://github.com/lshqqytiger/stable-diffusion-webui-directml/issues/10
Warning: caught exception 'Torch not compiled with CUDA enabled', memory monitor disabled
No module 'xformers'. Proceeding without it.
Loading weights [e03274b1e7] from D:\AI_ART\stable-diffusion-webui-directml\models\Stable-diffusion\meinamix_meinaV7.safetensors
Creating model from config: D:\AI_ART\stable-diffusion-webui-directml\configs\v1-inference.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Applying sub-quadratic cross attention optimization.
Textual inversion embeddings loaded(0):
Model loaded in 5.0s (load weights from disk: 0.1s, create model: 0.5s, apply weights to model: 4.3s).
Running on local URL:  http://127.0.0.1:7860
```


### Additional information

_No response_
Repository: electron
Issue: [Bug]: Desktop Capturer not consistently using PipeWire on Wayland
Labels: platform/linux,bug :beetle:,status/confirmed,has-repro-gist,23-x-y,24-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

23.0.0

### What operating system are you using?

Other Linux

### Operating System Version

Ubuntu 22.04, Fedora 35

### What arch are you using?

x64

### Last Known Working Electron version

22.3.2

### Expected Behavior

Desktop capturer should consistently return capturer sources. If on Wayland, the desktop capturer should use PipeWire. If on X11, the desktop capturer should use the X11 capturer.

### Actual Behavior

WebRTC's desktop capturer API falls back to the X11 capturer even when using Wayland. PipeWire itself will occassionally segfault when trying to return sources.

### Testcase Gist URL

https://gist.github.com/5c9df25094b029595e7e4fc2256568ef

### Additional Information

Following up on a conversation in this PR (#37511), which prevents a hard crash from occurring when trying to use the desktop capturer API, but doesn't resolve the underlying Wayland problem. We should default to the PipeWire capturer if we are using Wayland.
Repository: PowerToys
Issue: [Quick Accent] Relative Positioning
Labels: Idea-Enhancement,Needs-Triage,Product-Quick Accent

### Description of the new feature / enhancement

The available toolbar positions let the user set on the toolbar on a fix position. But the problem with the available positions was as mentioned, it is in a fix position. This kind of problem is much more visible when the user has a large monitor.

What I propose is relative positioning of the toolbar.

![image](https://user-images.githubusercontent.com/104838593/223542468-8a9cdcca-ae3b-455e-b883-e5288069e55d.png)


### Scenario when this would be used?

With relative positioning. when the user activates the quick accent, the position of the toolbar is either above or below the letter of what the user wants to modify. it helps the user easily see the toolbar and what they want to select. 

### Supporting information

_No response_
Repository: flutter
Issue: Lighthouse accessibility doesn't like our viewport meta tag
Labels: a: accessibility,platform-web,P2,team-web,triaged-web

```html
<meta flt-viewport="" name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
```

![image](https://user-images.githubusercontent.com/17034/223543616-b72cb2a9-d9f4-4c26-ad91-82012da3ee25.png)