sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: FancyZone Can't Tell Difference Between Chrome Shortcuts
Labels: Idea-Enhancement,Product-FancyZones

I use multiple Chrome Shortcuts configured to Open as a Window.  This results in multiple Chrome windows that are used for a specific site/purpose.  Gmail, Messages, IRC, Photos, etc.  FancyZones isn't able to distinguish between those windows and drops them all into the same zone. 

Example of how to create the shortcut:  https://brianhaines.com/2019/06/23/google-chrome-add-application-shortcut/
Repository: excalidraw
Issue: add test helpers for element manipulation
Labels: test

Current issues for clicking (but applies in general):

1. clicking elements is currently too low-level (`mouse.down(coords); mouse.up(coords)`)
2. More importantly, it's not obvious such action actually clicked on the element because it may be covered by a menu. In that case, the test may not be written in a way that would discover that (e.g. testing whether an already selected element was selected by the click won't help). We should maybe set up hooks in the application that will help us in this.
Repository: excalidraw
Issue: write more regression tests
Labels: test

There's still many parts of the application we have zero tests for. Please add anything to the list below that comes to mind.

- [ ] updating scene properties
- [ ] element property updating (via menu)
- [ ] contextMenu
- [ ] dialogs
- [x] comprehensive history tests
- [ ] collaborative mode
Repository: excalidraw
Issue: fix test cases leaks/race conditions
Labels: bug,test

I'm not quite sure what's going on, but several times I've written a test case, it behaves differently when running it in isolation (`it.only`) as opposed to running all tests in file (`regressionTests.test.tsx`).

I'm not talking about snapshots. When the test was run in isolation, all passed, but when run with other tests, some DOM events started failing (or vice versa). 100% reproducible.

Will update this issue when I have time to investigate.
Repository: rust
Issue: "Unnecessary" braces have an influence
Labels: C-enhancement,A-diagnostics,T-compiler

On `1.45.0-nightly (2020-05-29 4bd32c98047a809ba5fd)`
```rust
fn f() -> usize {
    {1usize} - 1usize
}
```
Intuitively, I would expect these braces to be redundant **and also have no influence**, but they do. The compiler expects a `()` type and then considers the minus sign a unary operator.
```
warning: unnecessary braces around block return value
 --> src/lib.rs:6:5
  |
6 |     {1usize} - 1usize
  |     ^^^^^^^^ help: remove these braces
  |
  = note: `#[warn(unused_braces)]` on by default

error[E0308]: mismatched types
 --> src/lib.rs:6:6
  |
6 |     {1usize} - 1usize
  |      ^^^^^^ expected `()`, found `usize`

error[E0600]: cannot apply unary operator `-` to type `usize`
 --> src/lib.rs:6:14
  |
6 |     {1usize} - 1usize
  |              ^^^^^^^^ cannot apply unary operator `-`
  |
  = note: unsigned values cannot be negated
```

It seems to me that either the error message about the braces being redundant is incorrect or misleading, or something more nefarious seems to be going on with scopes, expressions, etc.
Repository: material-ui
Issue: [Tabs] Improve tab panels mounting behavior
Labels: new feature,component: tabs

Based on #21241, we might have an opportunity to improve the `TabPanel` mounting behavior. We can potentially fix these problems:

- Lost states between different panels (by keeping the panels mounted)
- Improve the performance of panel transitions (by mounting the panels ahead of time)
- Improve the SEO support (by rendering all the panels' content)

I have used the following benchmark list https://trello.com/c/JM6Zh3YW/2642-tabs to look at what the others are doing

1. hidden prop with full rendering and no option to disable it https://github.com/reach/reach-ui/blob/115eb680bae13e7e097c9a6cd3047c06530ee880/packages/tabs/src/index.tsx#L643
  - Reach UI 
  - Reakit
  - Garden
  - Chakra
  - React Bootstrap
2. lazy render the content of the tab panels, keep them mounted when moving to a different tab 
  - Antd (plus a `forceRender` prop to render all the panels)
3. only render the active tab panel
  - Base Web (plus a `renderAll` prop to render all the panels)
  - Material-UI
  - JetBrains
  - Semantic UI
  - AltasKit
  - Polaris
4. render in two passes, first the active panel, then all the panels
  - react-swipeable-views

In the future, React mentions maybe solving this in the framework: https://github.com/oliviertassinari/react-swipeable-views/issues/453#issuecomment-417939459, by providing better support for offscreen rendering.

What do you guys think about these different tradeoffs? It seems that we need, at least, a way to enable the mounting of all the panels.
Repository: PowerToys
Issue: New PowerToy: Alt + Tab menu customisations 
Labels: Idea-New PowerToy,Product-Tweak UI Design,Product-Virtual Desktop

# Summary of the new feature/enhancement

New Power Toy: Ability to control the size of the Alt+Tab menu and disable previews
It would be helpful if we could control the size of the Alt+Tab menu (having it not correspond with the screen resolution) and disable the previews as a method of saving space, much like how it was done on Windows 7 when Classic Windows Shell was enabled, instead of Win 7 Basic or Win 7 Aero Glass.

This would impact the user in a positive way because it would allow for the user to have a cleaner representation of their open applications, when using the Alt + Tab menu.

# Proposed technical implementation details (optional)

User to have a configuration menu allowing them to make the following changes to the Alt + Tab menu: 

- Ability to remove previews from each window, and see just a list of open Applications.
- Group applications by their application name
- Ability to rearrange the applications in the Alt+Tab menu.
Repository: PowerToys
Issue: Preview of HTML file that includes pictures
Labels: Idea-Enhancement,Product-File Explorer

# Environment

```
Windows build number: Microsoft Windows [Version 10.0.19041.264]
PowerToys version:  v0.18.1
PowerToy module for which you are reporting the bug (if applicable): File Explorer Preview
```

# Steps to reproduce
1. Create image foo.png (I used MSPaint and screenshot)
2. Create html file: ```<html><body><img src="foo.png"/></body></html>```
3. Select file in Windows Explorer > preview page shows error icon

# Expected behavior
Not show this broken icon.

## Ultimate experience
See screenshots bellow.
The preview pane offers a user selectable, multiple viewing mode, easy to switch ex: tab, buttons
  - Source view: shows the raw html content, no formatting
  - Markup view: shows the html in markup, auto-formatted with indent and color, etc. (like browser's code behind view)
  - Render view: render the html

![image](https://user-images.githubusercontent.com/1571612/83337899-33b7e680-a28d-11ea-88ea-10d68aa3baa2.png)
![image](https://user-images.githubusercontent.com/1571612/83337954-95785080-a28d-11ea-88ce-f1ce84b101a1.png)
![image](https://user-images.githubusercontent.com/1571612/83337916-4a5e3d80-a28d-11ea-95bb-21f3dd9fa508.png)


## Good
Show the html with preview

## Acceptable
Show the html in markup, auto-formatted with indent and color, etc. (like browser's code behind view)

## Options:
I guess there are different "levels" of security with respect to html based on its content.
- javascript location: 
  - no javascript
  - inline-markup javascript: (<script />)
  - relative javascript file <script src="./" />
  - external javascript <script src="http://" />
- what the javascript code is doing
    - not referencing external content
    - referencing relative content (./)
    - referencing external resources (http://)
- css location:
  - no css
  - inline-markup css <style />
  - relative css file <link href="./" />
  - external css <link href="http://" />
- css and location of resources: (images)
  - no external
  - relative resources: ,/
  - external resources: http://

The Preview Pane should choose to display or not the preview based on the different levels of security.
1. html no javascript, no external.  This the safest and should be rendered.
2. html, everything is relative (./): Quite safe, and should be rendered
3. html with external content. (http;//).  Ask the user: do you trust this html.  if the answer is yes, render html.  if not, render the markup.

# Actual behavior
The preview pane shows a [x] icon with tooltip: "Some pictures have been blocked to help prevent the sender from identifying your computer. Open this item to view the pictures."

# Screenshots
Problem reported
![image](https://user-images.githubusercontent.com/1571612/83336878-fb140f00-a284-11ea-8453-b103510de942.png)
Repository: terminal
Issue: Avoid closing window when close last tab.
Labels: Issue-Feature,Area-UserInterface,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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

Avoid closing window when close last tab.

<!-- 
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).
-->

# Proposed technical implementation details (optional)

Keep terminal window when 0 tabs exist, not be concern about the last tab how to be closed.

Features/News/Terminal list, are good contents in the empty window view.

Like Firefox/Chrome/ConEmu which is popular tab manager does.

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: pytorch
Issue: Compilation errors
Labels: module: build,triaged,module: mkldnn

Hello,
i am building Pytorch on Ubuntu 18.04 for the Titan- Black Card (Compute-Capability = 3.5).
I get the following error while compiling:
/home/csverma/Disk/Software/MLearn/Pytorch/pytorch/bld/lib/libtorch_cpu.so: undefined reference to `dnnl::impl::bfloat16_t::operator float() const'
/home/csverma/Disk/Software/MLearn/Pytorch/pytorch/bld/lib/libtorch_cpu.so: undefined reference to `dnnl::impl::cpu::simple_barrier::generate(dnnl::impl::cpu::jit_generator&, Xbyak::Reg64, Xbyak::Reg64)'
/home/csverma/Disk/Software/MLearn/Pytorch/pytorch/bld/lib/libtorch_cpu.so: undefined reference to `dnnl::impl::bfloat16_t::operator=(float)'
/home/csverma/Disk/Software/MLearn/Pytorch/pytorch/bld/lib/libtorch_cpu.so: undefined reference to `dnnl::impl::cpu::simple_barrier::barrier(dnnl::impl::cpu::simple_barrier::ctx_t*, int)'
/home/csverma/Disk/Software/MLearn/Pytorch/pytorch/bld/lib/libtorch_cpu.so: undefined reference to `dnnl::impl::add_floats_and_cvt_to_bfloat16(dnnl::impl::bfloat16_t*, float const*, float const*, unsigned long)'
/home/csverma/Disk/Software/MLearn/Pytorch/pytorch/bld/lib/libtorch_cpu.so: undefined reference to `dnnl::impl::cvt_bfloat16_to_float(float*, dnnl::impl::bfloat16_t const*, unsigned long)'
/home/csverma/Disk/Software/MLearn/Pytorch/pytorch/bld/lib/libtorch_cpu.so: undefined reference to `dnnl::impl::cvt_float_to_bfloat16(dnnl::impl::bfloat16_t*, float const*, unsigned long)'
collect2: error: ld returned 1 exit status
caffe2/lib_c10d/example/CMakeFiles/allreduce.dir/build.make:126: recipe for target 'bin/allreduce' failed
make[2]: *** [bin/allreduce] Error 1
CMakeFiles/Makefile2:5469: recipe for target 'caffe2/lib_c10d/example/CMakeFiles/allreduce.dir/all' failed
make[1]: *** [caffe2/lib_c10d/example/CMakeFiles/allreduce.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2


Any help?



cc @malfet @gujinghui @PenghuiCheng @XiaobingSuper @jianyuh @VitalyFedyunin
Repository: godot
Issue: Instance binding data on GDNativeLibrary objects never gets freed
Labels: bug,topic:gdextension

Godot 3.2.2 beta3
Windows 10 64 bits

`Object` instances can hold GDNative instance binding data (for example, that data can correspond to class wrappers inside of NativeScript libraries). This data is normally freed in the destructor of `Object`... unless `ScriptServer::finish_languages();` is called before. In such case the data will leak. 

Turns out that's the case I found.
In C++ bindings, we access our own `GDNativeLibrary` here: https://github.com/GodotNativeTools/godot-cpp/blob/e97e86648355cbe61c6249483c6f2a5d1b41714f/include/core/Godot.hpp#L43

This leads to instance binding data being attached (only the first time) to the object.
Unfortunately, it never gets freed, because on quit, things happen in this order:

- `ScriptServer::finish_languages();`
- Our GDNative library gets terminated
- Godot deletes the `GDNativeLibrary`

By extension, it also means if a library wants to hold a Godot object as internal singleton (like it happens sometimes in modules), the instance binding data of such objects will always leak, even if the object is freed in the terminate callback.

Eventually there should be an error printed when stuff like that happens, because currently it's completely silent and I had to investigate for a while.

In the C++ bindings we might be able to workaround this by avoiding the use of instance binding data (so, using the C API directly without any helper). Wether this should be allowed or not I don't know, but it looks like a bug from Godot.
Repository: flutter
Issue: Compiler errors are really ugly
Labels: tool,t: gradle,a: quality,P2,team-tool,triaged-tool

At some point in the last few months we ended up making compiler errors much more ugly:

```
$ flutter create dummy_compiler_error
...
$ cd dummy_compiler_error
$ sed -i '$d' lib/main.dart
$ flutter run
Launching lib/main.dart on Lenovo TB 8504F in debug mode...
Running Gradle task 'assembleDebug'...                          

Compiler message:

lib/main.dart:52:50: Error: Can't find '}' to match '{'.

class _MyHomePageState extends State<MyHomePage> {

                                                 ^



Compiler message:

lib/main.dart:52:50: Error: Can't find '}' to match '{'.

class _MyHomePageState extends State<MyHomePage> {

                                                 ^

Target kernel_snapshot failed: Exception: Errors during snapshot creation: null

build failed.



FAILURE: Build failed with an exception.



* Where:

Script '/home/ianh/dev/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 896



* What went wrong:

Execution failed for task ':app:compileFlutterBuildDebug'.

> Process 'command '/home/ianh/dev/flutter/bin/flutter'' finished with non-zero exit value 1



* Try:

Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.



* Get more help at https://help.gradle.org



BUILD FAILED in 7s
Running Gradle task 'assembleDebug'...                              8.4s
Exception: Gradle task assembleDebug failed with exit code 1
```

The very first error message happens very quickly. We should abort there. Instead we seem to try to compile again, and then try to do something else in gradle, not sure what.

cc @jonahwilliams
Repository: rust
Issue: stdio handles (stdin, stdout, stderr) should be `Seek` at least on Unix
Labels: C-enhancement,T-libs-api

Currently, `std::io::Stdin` et al do not implement `Seek`.

It is true that a Unix program is not guaranteed that its stdin/stdout/stderr will be seekable. Often they won't be.  But, they may be.  If stdin is redirected from a file, for example, `lseek` (the system call) will work fine.

The `Seek` trait does not promise that `seek` actually works.  `seek` returns `io::Result` (quite properly).  Indeed a `std::io::File` object can easily refer to a non-seekable object, depending what path was passed.

Conversely, not implementing `Seek` makes it impossible to perform this operation in safe Rust.  There are perhaps some workarounds like asking to open `/dev/stdin`, but they are non-portable and often quite horrible.  Using `unsafe { libc::lseek(...) }` is quite straightforward (apart, perhaps, from a question about whether `lseek64` should be used instead) but we shouldn't expect our users to do that when we could have provided a safe way.

There are file data integrity and synchronisation issues with `Seek`.  But these are not significantly worse for stdin/out/err than for `std::fs::File`.  They are not a memory safety issue and we have already  chosen to address this in the documentation rather than through the type system.

I come from a Unix background.  I don't know what the situation is on Windows.  But, the fact that in Standard C, it is legal to call `fseek` on `stdin` (for example) suggests that the correct answer for Rust is to permit the user to try to call `seek` on all platforms.
Repository: deno
Issue: Caching and loading non-importable resources
Labels: cli,suggestion

## Problem

I often find myself needing to load non-JavaScript non-TypeScript assets, and various problems arise:
* Local module (in git repo) has to use `fs` but remote module has to use `fetch`.
* The assets cannot be cached.
* The assets cannot be bundled.

## Suggestion

Add some way to annotate assets using comments, and `fetch` should support those assets. For example:

```typescript
// @deno-asset './assets/foo.wasm'
// @deno-asset './assets/bar.png'
await fetch(new URL('./assets/foo.wasm', import.meta.url))
await fetch(new URL('./assets/bar.png', import.meta.url))
// --allow-net is not required since it reads from cache
```

## Alternatives

~~There is [asset reference proposal](https://github.com/tc39/proposal-asset-references) that is likely not going to get to stage 3 anytime soon.~~

[import assertion proposal](https://github.com/tc39/proposal-import-assertions) had reached stage 3.

Import types `text` and `bytes` are being discussed in https://github.com/whatwg/html/issues/9444
Repository: youtube-dl
Issue: Possible to get the file paths of all files related to a video downloaded with youtube-dl
Labels: question

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [ x] I'm asking a question
- [ x] I've looked through the README and FAQ for similar questions
- [ x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

I'm writing a script that passes metadata and file locations for videos, thumbnails, subtitles, etc. downloaded by youtube-dl into a database. The script is run by the `--exec` option in youtube-dl and gets passed the name of the video downloaded as an argument. The video name is then used to find other files related to the video (for example, removing the video file extension and replacing it with `.info.json` to find the file created by `--write-info-json`).

However, I'm running into trouble when it comes to indexing thumbnails and subtitles. For example, thumbnails across many different extractors don't have predictable file extensions or names (if there are multiple thumbnails) making it difficult to identify which files are what type and go in what order.

In the case of my script I believe it may be possible to guess the thumbnail name with a high degree of accuracy (using information from `.info.json` check `"thumbnails"` for the thumbnail ext in the `"url"`, checking the `"url"` response header for ext, if there are more then one thumbnails add the `"id"` to the guessed file name, etc.) however this could be prone to sometimes being wrong and I hope there is a better way to do this.

I'm curious to see if there is another way of getting all of the files related to the video downloaded by youtube-dl and to tell what type of files they are (thumbnails, subtitles, metadata, etc.). I did not see a way to do this in the README or FAQ.

If there is no way of doing this a possible solution could be adding a parameter like `--write-files-list` which would write the all files downloaded by youtube-dl when downloading the video to `videoname.files.json`.
```json
"video": "path"
"thumbnails": [
    "path",
    "path"
]
"subtitles": [
...
```
Repository: TypeScript
Issue: Allow type-only named re-exports along with assigned export in the same file
Labels: Suggestion,In Discussion

## Search Terms

allow export types assigned =

## Suggestion

The suggestion is to allow compilation of files that do both `export =` and `export type {}`.

## Use Cases

For modules that target both TypeScript and CommonJS usage it would allow consolidating all exports for both module systems in one file (albeit with the requirement of `esModuleInterop` being `true`).

Currently, in order to do that I would have to utilize @ts-ignore (see parzh/xrange#69 for details).

## Examples

_/person.ts_:

```ts
import personValue from "./person-value";

export = personValue;

export type { default as PersonType } from "./person-type";
```

_/person-type.ts_:

```ts
export default interface Person { name: string; }
```

_/person-value.ts_:

```ts
export default { name: "John Doe" } as import("./person-type").default;
```

#### Usage:

_/usage.ts_:

```js
import personValue from "./person";
import personValue, { PersonType } from "./person";
import type { PersonType } from "./person";
import personValue = require("./person");
```

_/usage.js_:

```js
const personValue = require("./person");
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: godot
Issue: Quick Open Script search should show exact matches on top
Labels: topic:editor

**Godot version:**
3.2.1-stable_win64


**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Windows 10 64 

**Issue description:**
Searching in the Quick Open Script window is not sorting the scripts properly. It should prioritize exact (and complete) match of script names before not exact matches.

**Steps to reproduce:**
use the search option in the Quick Open Script window

![image](https://user-images.githubusercontent.com/16180873/83350795-a9af6280-a30c-11ea-8399-1dbdd5100b34.png)