sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Abstracted  window.getSelection()  for all platforms
Labels: framework,c: proposal,P3,f: selection,team-framework,triaged-framework

## Description 

When creating a custom textSelectionControl using a SelectionArea, the web and macos versions do not have feature parity. 
https://github.com/flutter/flutter/issues/116607 . The work in https://github.com/flutter/flutter/pull/107193 looks like it will resolve the context menu, but does not address retrieval of selected text. 

## Use case
A cross platform context menu or other widget may require retrieving selected text. Context menus typically include a copy function, but there are other widgets that require retrieving selected text.  

## Proposal
Create a simplified abstraction of getting selected text (not needing the system clipboard) that works on mobile and also web, likely with `window.getSelection()`. I am unclear if this selection feature is only to retrieve text or other content such as images.
Repository: pytorch
Issue: [RFC] Add torch.backends.tbb.is_available()
Labels: triaged,enhancement,module: tbb

### 🚀 The feature, motivation and pitch

Add a similar API to `torch.backends.openmp.is_available()` for TBB, `torch.backends.tbb.is_available()`. 

### Usage
The expected usage of `torch.backends.tbb.is_available()` is of similar to that of `torch.backends.openmp.is_available()`. I assume users use `torch.backends.openmp.is_available()` to verify their pytorch config, and `torch.backends.tbb.is_available()` can be of similar usage to that - users can verify whether TBB is enabled on their PyTorch or not with this API rather than using `TBB_VERSION=1`, `MKL_VERBOSE=1`, etc. 

```python
import torch
torch.backends.tbb.is_available() # True if TBB enabled, False otherwise
```

### Alternatives

_No response_

### Additional context

_No response_
Repository: flutter
Issue: Add a property to text rendering widgets that allows for adding a tooltip when the text is overflowed
Labels: a: text input,c: new feature,framework,f: material design,a: typography,c: proposal,team-design,triaged-design

In many cases for text widgets, we do not want to show a redundant tooltip (e.g. "This is my text widget with words" with a tooltip of "This is my text widget with words". But it would be useful to show a tooltip with the full content when the text is ellipsized (e.g "This is my text widg..." with a tooltip "This is my text widget with words". It would be useful if there was a `tooltipOnOverflow` property on `Text`(and likely on other text widgets with the `overflow` field).
Repository: pytorch
Issue: [discussion, idea] Batched, vectorized base64 decoding / encoding + maybe RLE decoding / encoding
Labels: feature,triaged,module: vision,module: nestedtensor

### 🚀 The feature, motivation and pitch

Discussed in context of scriptable base64 decoding here: https://github.com/pytorch/vision/issues/6878#issuecomment-1343439120, http://www.alfredklomp.com/programming/sse-base64/, https://r-libre.teluq.ca/1362/1/base64.pdf 

But then I thought that base64 can be implemented in a vectorized way - and probably some design could probably do batching/parallelization (especially if inputs/outputs of same/padded size or nestedtensor/tensorlist)

The usecases are probably limited but could include some visualization utils that need to encode many images / audio files to base64 for further burning into html as data-uris for self-containedness

### Alternatives

_No response_

### Additional context

_No response_

cc @datumbox @vfdev-5 @pmeier @cpuhrsch @jbschlosser @bhosmer @drisspg @mikaylagawarecki
Repository: flutter
Issue: font icon tree-shaking will erroneously remove code points generated by tear-off constructor
Labels: tool,P2,team-tool,triaged-tool

In https://github.com/flutter/engine/pull/38131, I added a const_finder test in which a non-const instance of the `Target` class is created and used. This should show up in the `nonConstantLocations` field of the output JSON generated by `const_finder`. However, it is not.

Because of this, a flutter app could use code points from a font via a constructor tear-off of the `IconData` class, which would result in non-const instances. In this case, the correct thing to do, when producing a release build with the `--tree-shake-icon` flag (the default) would be for the build to fail with the error message that tree-shaking cannot be done on applications with non-constant instances of `IconData`. However, because const_finder does not detect these as non-const locations, they will be tree-shaken out.
Repository: neovim
Issue: vim.diagnostic.setqflist's namespace argument should accept a table of namespaces
Labels: enhancement,diagnostic

### Feature already in Vim?

_No response_

### Feature description

Similar to functions that take vim.diagnostic.severity as an optional parameter, the namespace parameter could either be a single namespace (number) or a table of namespaces (numbers).

This table can be the result of `vim.tbl_map(vim.lsp.diagnostic.get_namespace, vim.tbl_map(function(i) return i.id end, vim.lsp.get_active_clients()))`.
Repository: rust
Issue: Confusing `E0284` "type annotations needed" when trait method bound trait bound conflict in associated type.
Labels: A-diagnostics,A-trait-system,A-associated-items,T-compiler,D-confusing,D-terse

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code ([playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=ce91872c380cbf9bb89b910c8bff1b92)):

```rust
pub trait Extension: IntoIterator<Item = u32> + Sized {
    fn test(self) -> Vec<u64>
    where
        Self: IntoIterator<Item = u64>,
    {
        self.into_iter().collect()
    }
}
```

(i.e. the bound on `fn test` conflicts with the bound of its trait by way of associated types)

The current output is:

```
error[E0284]: type annotations needed: cannot satisfy `<Self as IntoIterator>::Item == u32`
  |
note: required by a bound in `Extension`
 --> src/lib.rs:1:35
  |
1 | pub trait Extension: IntoIterator<Item = u32> + Sized {
  |                                   ^^^^^^^^^^ required by this bound in `Extension`

For more information about this error, try `rustc --explain E0284`.
error: could not compile `playground` due to previous error
```

<!-- The following is not always necessary. -->
Ideally the output should look like: something mentioning the conflicting bounds. (Or under `#![feature(trivial_bounds)]`, maybe it could just be a trivially false bound?).

```
error[E0000]: conflicting bounds: cannot satisfy both `<Self as IntoIterator>::Item == u32` and `<Self as IntoIterator>::Item == u64`
  |
note: bounds in `Extension` and `fn test`
 --> src/lib.rs:1:35
  |
1 | pub trait Extension: IntoIterator<Item = u32> + Sized {
  |                                   ^^^^^^^^^^ required by this bound in `Extension`
4 |         Self: IntoIterator<Item = u64>,
  |                            ^^^^^^^^^^ required by this bound in `fn test`

error: could not compile `playground` due to previous error
```

<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions. The output might also be
different depending on the Edition.
-->

Same result on stable, beta, and nightly.

Related: #103292, (can't find the issue at the moment, but `impl<T: Trait<Assoc = u32>> SecondTrait for T` conflicting with `impl<T: Trait<Assoc = u64>> SecondTrait for T` when it shouldn't is related).

@rustbot modify labels +A-traits +D-confusing +A-associated-items
Repository: pytorch
Issue: Bfloat16 tensor .numpy() support 
Labels: triaged,module: numpy,module: bfloat16,onnx-needs-info

### 🚀 The feature, motivation and pitch

Numpy doesn't support bfloat16, and doesn't plan to do so. The effect of this is that code that makes any `tensor.numpy()` call breaks when you make it use bfloat16. I was thinking that bfloat16 getting outputted to `np.float32` would make sense, as it just keeps the exponent and ads a few mantissa bits. This must be very quick. This would make all code that is supported with float32 or float16 be compatible with bfloat16 out of the box, and feels like reasonable behavior to me.

### Additional context

The `to_numpy` function seems to be here https://github.com/pytorch/pytorch/blob/master/torch/csrc/utils/tensor_numpy.cpp#L159

and the function that decides the output `np.dtype` seems to be here:
https://github.com/pytorch/pytorch/blob/master/torch/csrc/utils/tensor_numpy.cpp#L267


cc @mruberry @rgommers
Repository: pytorch
Issue: Multiprocessing "Error Propagation" doesn't work for FullyShardedDataParallelism.
Labels: oncall: distributed,module: fsdp

https://github.com/pytorch/pytorch/blob/b7dfbf876f640591c399de2c92f523432b3455a1/torch/multiprocessing/spawn.py#L131

The multiprocessing spawn error propagation relies on sending a "process.terminate" call to request that each process should stop executing. Terminate sends a _request_ that should be honored by the receiving process - but in FSDP, that request is not honored. If one process OOMs, but the others do not, that process will die and the terminate call will be sent out while the others simply end up waiting indefinitely. Due to how FSDP works, I'm assuming they're hanging waiting for the weight all-gather phase, and aren't willing to accept the terminate signal. This is a serious blocking point for FSDP users, since the typical setting (large-model training) will often lead to CUDA OOMs that cannot be handled or propagated correctly.

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: PowerToys
Issue: Snap windows to edges of screens, regions, and other windows
Labels: Needs-Triage

### Description of the new feature / enhancement

When moving or resizing a window, I would like it to "snap" to the edges of the screen, of regions, and of other windows. I can best describe this feature by directing you to a demo of it in action on the MaxTo* tutorial: https://docs.maxto.net/tutorial/snap

* MaxTo is a third-party product that offers functionality similar to FancyZones, but it's paid, has more features, and is very buggy and unreliable (in my experience). It regularly needs to be restarted, and even then isn't reliable. But, it does have some great features! If the snapping feature could be added in to FancyZones, that would address my last big item that I miss from MaxTo.

### Scenario when this would be used?

- Any time you're trying to align two windows
- When you want to "vertically maximize" a window (drag it up to the top and/or bottom edge of the screen)
- When you want to optimize your window layout by making sure a window is all the way to an edge or corner or a screen or region

### Supporting information

The MaxTo documentation has a bit more detail about how their snapping setting works: https://docs.maxto.net/reference/settings/behavior#toc-3
Repository: vscode
Issue: Explore UI density modes
Labels: feature-request,ux,layout

We hear quite a lot of feedback from the community on how they would like VS Code to look and feel. One theme that often comes up is related to UI density. 

This feedback spans specific usability concerns like the [activity bar being hard to understand without labels](https://github.com/microsoft/vscode/issues/130051) as well as broad feedback like the UI feeling overall cramped and harder to interact with given the close proximity of buttons and other elements.

On the other side, many seek a more compact and space-efficient UI. Using the activity bar example, some users would prefer a [hyper-compact version](https://github.com/microsoft/vscode/issues/118692) that doesn't take up any horizontal space. Or perhaps they'd like the [titlebar to use as little space as possible](https://github.com/microsoft/vscode/issues/12377).

Density modes could apply to everything from low-level font/icon sizes to widgets like toolbars and lists. At a high level, they could impact larger UI parts like the status bar, title bar, and more.

This issue will explore what it could look like to feature UI density modes in VS Code.

## Rough Sketch

Here's an idea of what this could look like to get the ball rolling. Not intended to capture every detail:

https://user-images.githubusercontent.com/25163139/206812861-0312f871-84b4-477b-bed1-b49e336d43c5.mp4
Repository: go
Issue: x/vuln/vulncheck: support for generics
Labels: vulncheck or vulndb

vulncheck currently supports generics by instantiating them using `ssa.InstantiateGenerics.` But what happens for entry points that are generics functions: they themselves are not instantiated. They should in principle be supported just as functions accepting interfaces arguments, but it could be that the underlying vta callgraph is not handling them properly.

Investigate and make a long-term decision.
Repository: vscode
Issue: Debugging untitled file in IW shows unbound breakpoints
Labels: bug,debug,notebook-debugging

Breakpoints are not considered verified if the ITextFileService says the file that they're in is dirty. https://github.com/microsoft/vscode/blob/e00b25cc55a1150d86fa54f9b997d97daf530379/src/vs/workbench/contrib/debug/common/debugModel.ts#L887

We should have a way for the debug adapter to signal that it supports debugging dirty/unsaved files. Should this be another flag in `DebugSessionOptions` for `startDebugging`, or a flag on the adapter in package.json?

Interestingly, this currently works on notebooks by accident. @rebornix, if I wanted to make the above check correct for notebook editors, is there a different service that I need to ask whether a notebook editor is dirty?
Repository: vscode
Issue: Extension commands do not show any status indicator while waiting for activation
Labels: feature-request,extensions,extension-activation

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Technically no

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.75.0-insider
- OS Version: Windows

---

When an extension command is triggered, and that command activates the extension, there is no status displayed to indicate that the extension is being activated / waiting for activation to start. If there are many extensions to load, it could take a long time just to get around to activating the relevant extension.

This may leave the user wondering what is happening, and give the impression that the slowdown comes from the extension (rather than VS Code / the presence of many other extensions).

Some past issues have seen improvements in specific cases like tree views (see #59645), but other entry points (in my case, editor title / context menu items) are still impacted.

It would be good to have some sort of indicator (perhaps a notification or status bar item) to communicate to the user that extensions are still loading and the command will be executed when done.
Repository: vscode
Issue: Scroll position changes randomly on Release Notes page when switching tabs
Labels: bug,release-notes

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.74 as well as previous versions
- OS Version: any of Windows, Macos

Steps to Reproduce:

1. Open Release Notes and some other windows (e.g. Get Started) 
2. Scroll Release Notes to some position and remember it
3. Switch to the other tab and then return back several times to see how scroll pos changes

Scroll position may change arbitrarily several lines up or down
Repository: vscode
Issue: Settings editor dropdown is still visible after closing editor
Labels: bug,settings-editor,confirmed

- Open settings editor
- Expand dropdown
- cmd+w to close settings editor
- The dropdown is still there

![Recording 2022-12-09 at 17 41 35 (1)](https://user-images.githubusercontent.com/323878/206812729-8e5edc17-70c6-460d-b31a-8a391fa15ca7.gif)
Repository: PowerToys
Issue: █ Screen ruler ➜ Choose from 4 different functions to start from the beginning
Labels: Idea-Enhancement,Needs-Triage,Product-Screen Ruler

### Description of the new feature / enhancement

● When the shortcut key starts, you can choose the function to start from the very beginning.
The moment you activate the shortcut key, you can activate one of the four tools ( 囗 ＋ ー l　) that exist at the moment.


### Scenario when this would be used?

This allows you to more quickly use the tools you use most from the moment you start them up.

※This is in reference to the properties of ShareX and various screenshot tools. 
※Sorry if this is existing content.

### Supporting information

https://getsharex.com/
Repository: rust
Issue: Use protected visibility by default on ELF platforms
Labels: A-linkage,T-compiler

I noticed that the .so files built by x.py contain a lot of "unnecessary" PLT entries. The compiler should be using protected visibility on ELF platforms by default.

I was thinking we should be able to tie it to `#[no_mangle]` but on Zulip @bjorn3 proposed tying it to the SymbolExportLevel (Rust for mangled and unmangled but not exported from cdylib `#[rustc_std_internal_symbol]` symbols and C for `#[no_mangle]` symbols).
Repository: rust
Issue: bad diagnostic suggestion for self access in a format string
Labels: A-diagnostics,A-resolve,A-macros,T-compiler,A-suggestion-diagnostics,D-invalid-suggestion,A-fmt

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

```rust
struct Foo {
    value: i32
}

impl Foo {
    fn f(&self) -> String {
        format!("{value}")
    }
}
```

The current output is:

```
error[E0425]: cannot find value `value` in this scope
 --> src/lib.rs:7:19
  |
7 |         format!("{value}")
  |                   ^^^^^ help: you might have meant to use the available field: `self.value`
```

Applying the suggestion doesn't work since format strings don't allow non-identifier expressions. Fortunately applying the suggestion and compiling again will lead to another suggestion with the correct syntax. Ideally the original diagnostic should provide the correct syntax of `format!("{}", self.value)`
Repository: stable-diffusion-webui
Issue: [Bug]: Checkpoint not found 
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?

Hey, i'm trying to load the nai model's and I have the api setup on a discord bot to input and produce the images into chat. But whenever I try to use nai.ckpt or other similar files like waifu-diffusion I would get the error and it would load onto a fallback of a generic model.


### Steps to reproduce the problem

Model's such as Waifu-diffusion, Novel AI and a handful of others on use or switching models would force loading fallback,

### What should have happened?

Model of choice should load instead of not finding checkpoint and loading fallback instead.

### Commit where the problem happens

44c46f0ed395967cd3830dd481a2db759fda5b3b

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

Windows, Linux

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

Google Chrome

### Command Line Arguments

```Shell
--listen --api
```


### Additional information, context and logs

Python 3.8.10 (default, Mar 15 2022, 12:22:08)
[GCC 9.4.0]
Commit hash: 44c46f0ed395967cd3830dd481a2db759fda5b3b
Installing requirements for Web UI
Launching Web UI with arguments: --listen --api
No module 'xformers'. Proceeding without it.
Checkpoint nai.ckpt not found; loading fallback nai.ckpt [925997e9]
Loading config from: /home/shieri/stable-diffusion-webui/models/Stable-diffusion/nai.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Loading weights [925997e9] from /home/shieri/stable-diffusion-webui/models/Stable-diffusion/nai.ckpt
Using VAE found similar to selected model: /home/shieri/stable-diffusion-webui/models/Stable-diffusion/nai.vae.pt
Loading VAE weights from: /home/shieri/stable-diffusion-webui/models/Stable-diffusion/nai.vae.pt
Applying cross attention optimization (Doggettx).
Model loaded.
Checkpoint nai.ckpt not found; loading fallback nai.ckpt [925997e9]
Loaded a total of 0 textual inversion embeddings.