sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: [json] allow $ref in confiuguration schemas
Labels: feature-request,json

Issue Type: <b>Bug</b>

Steps to Reproduce:

1. Create a ["definitions"](https://json-schema.org/understanding-json-schema/structuring.html) member for a JSON schema, and put a subschema there.
2. Attempt to refer to this subschema in `settings.json`.

***

I'm in a folder called "json" with a subfolder called "schemas" with the schemas, and a subfolder called ".vscode" for the `settings.json`.

Here is the definitions schema I am using:
```
{
  "$schema": "https://json-schema.org/draft/2019-09/schema",
  "type": "object",
  "definitions": {
    "items": {
      "type": "array",
      "items": {
        "$ref": "items.json#"
      },
      "minItems": 1
    }
  }
}
```

If I just make `items.json` into an array and use `"url": "./schemas/items.json"` works fine, but that isn't very conducive to my current work case. 

&nbsp;

So I tried using this:
```
"schema": {
	"type": "array",
	"items": {
	  "$ref": "./schemas/items.json"
	}
  }
```

Got this error: "Problems loading reference 'vscode://schemas/custom/schemas/items.json': Request vscode/content failed with message: cannot open vscode://schemas/custom/schemas/items.json. Detail: resource is not available".

&nbsp;

Tried using this:
`"url": "file:///C:/Users/BLATANT-DOXX-RISK/Source/Repos/json/schemas/types.json#/definitions/items"`

And it just used `types.json`, ignored the definitions part, and looked for nothing but a blank object.

&nbsp;

Finally, I tried using this: `"url": "./schemas/types.json#/definitions/items"`.

Got this error: "File not found (c:\Users\BLATANT-DOXX-RISK\Source\Repos\json\schemas\types.json#\definitions\items))".

&nbsp;

@aeschli came up a *lot* when looking through Github issues.

***

VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:35:15.005Z)
OS version: Windows_NT x64 10.0.18362

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: disabled_software<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_deferred_display_list: disabled_off<br>skia_renderer: disabled_off<br>surface_synchronization: enabled_on<br>video_decode: enabled<br>viz_display_compositor: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.80GB (7.40GB free)|
|Process Argv|C:\Users\ZACH-GAMING\Source\Repos\Cataclysm-DDA-Testing\data\json|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
Repository: flutter
Issue: Implement PlatformView support on macOS
Labels: c: new feature,platform-mac,a: platform-views,a: desktop,P2,team-macos,triaged-macos

We'll want to support embedding native views in a Flutter view, as is currently supported on mobile.

Remaining tasks:
* [X] Gesture support
* [ ] Focus traversal
* [ ] Accessibility tree merging
Repository: flutter
Issue: Implement PlatformView support on Linux
Labels: c: new feature,customer: crowd,platform-linux,a: desktop,P2,team-linux,triaged-linux

We'll want to support embedding native views in a Flutter view, as is currently supported on mobile.

~This is of course blocked on #30729 since until we have a view-based toolkit implementation for Linux, there's no concept of a "view" to embed.~
Repository: pytorch
Issue: Stop binding in-place methods to `torch.*`
Labels: triaged,module: ux

## 🐛 Bug

`torch.abs_` should not exist, but it does:
```
In [1]: import torch

In [2]: torch.abs_
Out[2]: <function _VariableFunctions.abs_>
```
Repository: flutter
Issue: [webview_flutter] Add Linux support
Labels: c: new feature,p: webview,platform-linux,package,a: desktop,P2,team-linux,triaged-linux

Once we definitively pick a toolkit, we'll need to evaluate web view options for that toolkit.

Blocked on #41724
Repository: terminal
Issue: Alt-Gr issue (global one also affecting conhost, not just Windows Terminal)
Labels: Product-Conhost,Help Wanted,Area-Input,Issue-Bug

# Environment

`Windows 10 Education, Build 18362.19h1_release_svc_19h2_rel.190621-1123`
Windows Terminal version (if applicable): Latest build from revision 0ce08aff ,
i.e. after commit 33361698 (but it didn't work either before).

Any other software? -> Testing Mathematica 11.3 kernel, but also reproducible
using Wolfram Engine (free DL at official website https://www.wolfram.com/engine/ )

# Steps to reproduce

Just open `math` (or `wolframscript` when using Wolfram Engine) command and try to enter square brackets or other symbols that require **pressing either AltGr or Ctrl-Alt on french keyboard layout**.

# Expected behavior

The square brackets should appear....

# Actual behavior

... but they do not. See the screen-capture. The problem happens when using standard Conhost and also the OpenConsole.exe version.
**On the contrary**, the square brackets are correctly transmitted to the `math` (or `wolframscript`) program **when using MinTTY from Git4Windows**.

![image](https://user-images.githubusercontent.com/1969829/65993323-44f7eb80-e491-11e9-8b16-4f419fa6406d.png)
Repository: TypeScript
Issue: Remove useless `@‍typedef` comments in `declaration`
Labels: Bug,Effort: Difficult,Domain: Comment Emit,Domain: Declaration Emit

JS input

```js
// @ts-check

/**
 * @typedef {number} Foo
 * Docs for `Foo`.
 */

export class Bar {

}
```

```sh
tsc --declaration --allowJs --emitDeclarationOnly foo.js
```

# Current Behavior

```ts
/**
 * @typedef {number} Foo
 * Docs for `Foo`.
 */
export class Bar {
}
/**
 * Docs for `Foo`.
 */
export type Foo = number;
```

# Proposed Behavior

```ts
export class Bar {
}
/**
 * Docs for `Foo`.
 */
export type Foo = number;
```
Repository: flutter
Issue: FLUTTER_BUILD_MODE isn't compatible with plugins on macOS
Labels: tool,platform-mac,a: desktop,P3,team-macos,triaged-macos

Using FLUTTER_BUILD_MODE to override the framework type on macOS works with a trivial project, but the Podfile uses FLUTTER_FRAMEWORK_DIR which isn't affected by it. That means that if any plugins are added, the Podfile logic will add a reference into the build that points unconditionally to the "real" build mode, and once Xcode knows about two different copies of the framework (the Podfile-generated symlink and the copy in Flutter/ephemeral/) it may bundle either one.

There's a note in the xcconfig-generation code about not adding FLUTTER_FRAMEWORK_DIR to module projects, which may be related to this happening on iOS. Assuming we want to support FLUTTER_BUILD_MODE for non-module projects though, this would likely affect iOS as well.

STR:
- Find/create a macOS project
- Add a plugin to it that supports macOS
- Open the project and add `FLUTTER_BUILD_MODE=debug` as a custom project setting
- `flutter build macos && flutter build macos --debug`
- Run `ls -l `find . -name FlutterMacOS`

The expected behavior is that they are all the same, but in practice the version in .../Build/.../Release/ is often actually the release framework. If that happens, the app won't launch because it'll try to load a debug VM snapshot with a release-mode FlutterMacOS.framework, which doesn't support JIT.
Repository: TypeScript
Issue: Language service fails to provide type info
Labels: Bug,Needs Investigation

Looks like recursive type breaks type info on Win10. Ubuntu works fine.

cc @ahejlsberg 

Language service outputs no info. See #33631.

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.4.0-dev.20191001

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

1. use Win10.
1. clone https://github.com/falsandtru/securemark
1. run `npm i`
1. open src/util/toc.ts
1. wait for the language service to be ready
1. look at type info as follows

![image](https://user-images.githubusercontent.com/3143368/65999409-50223a00-e4d8-11e9-9352-eeaa2a3369fa.png)

**Expected behavior:**

Show correct info.

**Actual behavior:**

Show wrong info.

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:**
Repository: storybook
Issue: Deprecation warnings in docs
Labels: feature request,addon: docs

I'm interested in marking components as deprecated to indicate that they should no longer be used, but the `jsdoc` attribute `@deprecated` is not being shown in the docs output in a way that is pronounced enough for readers.

**Describe the solution you'd like**
It would be awesome to have a subset of docs for styling and laying out potential `jsdoc` info

**Describe alternatives you've considered**
I've considered using the subtitle for this purpose, but it's preferable to keep these things in source/`jsdoc`

**Are you able to assist bring the feature to reality?**
Unsure, would need some pointers
Repository: pytorch
Issue: Easier way to create tensors with names
Labels: triaged,enhancement,module: named tensor

## 🚀 Feature

Right now, to create a tensor with names, we do
```
x = torch.randn(3, 3, 3, 3, names=('N', 'C', 'H', 'W'))
```

Typing the ' a lot is an inconvenience. It would be nice to explore one of the following APIs:

1.  `x = torch.randn(N=3, C=3, H=3, W=3)` (Python >= 3.6)
2. `x = torch.randn(torch.dims(N=3, C=3, H=3, W=3))` (Python >= 3.6)
3. `x = torch.randn(3, 3, 3, 3, names='N C H W')`
4. `x = torch.randn(3, 3, 3, 3, names='NCHW')` (number of characters must match number of dims)

## Motivation

Type less, feel happier.
Repository: vscode
Issue: [css] css.lint.hexColorLength seems to be now irrelevant
Labels: bug,css-less-scss

Issue still occurs in Insiders v1.39.0

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.39.0
- OS Version: macOS 10.14.6

Steps to Reproduce:

1. Set css.lint.hexColorLength to error or warning
2. Create a css file with a wrongly formatted color value
```
div {
    color: #ccc0003;
}
```

Expected behavior:
An error or warning as per the `css.lint.hexColorLength` setting.

Actual behavior:
A `css-propertyvaluexpected` error.

The `css.lint.hexColorLength` setting seems to no longer be relevant.

Does this issue occur when all extensions are disabled? Yes
Repository: neovim
Issue: flaky test: wait_spec.lua @ 53: wait() evaluates the condition on given interval
Labels: bug,test

```
[  FAILED  ] test/functional\eval\wait_spec.lua @ 53: wait() evaluates the condition on given interval
test/functional\eval\wait_spec.lua:62: Expected objects to be the same.
Passed in:
(number) 0
Expected:
(number) -1

stack traceback:
	test/functional\eval\wait_spec.lua:62: in function <test/functional\eval\wait_spec.lua:53>

```
https://ci.appveyor.com/project/neovim/neovim/builds/27813594/job/uiksgfa184xoy394#L8340
Repository: flutter
Issue: Automatically migrate app project to use the new Android embedding
Labels: c: new feature,platform-android,tool,a: existing-apps,P3,team-android,triaged-android

If an app is using the old embedding and a plugin is using the new embedding. Then, we could try to migrate the app to the new embedding automatically.
Repository: TypeScript
Issue: Function body is not checked against assertion signature
Labels: Suggestion,Needs Proposal

**TypeScript Version:** 3.7.0-dev.20191002

**Search Terms:** assertion signatures, asserts, not checked, unchecked, unsound

**Code**

```ts
function assertIsString(x: number | string): asserts x is string {
}

function test(x: number | string) {
    assertIsString(x);
    x.toUpperCase();
}

test(4);
```

**Expected behavior:**

This incorrect empty implementation of `assertIsString` should not type check, because there are execution paths through `assertIsString` that don’t narrow the type of `x` to `string` as the type of `assertIsString` should require.

**Actual behavior:**

No TS errors. Compiled JS code fails at runtime: `TypeError: x.toUpperCase is not a function`.

**Playground Link:** Playground nightly isn’t new enough, but maybe it will be by the time you read this: [link](https://www.typescriptlang.org/play/?ts=Nightly#code/GYVwdgxgLglg9mABAQwM6oKYCcoElUDKUWMYA5gBQAeAXImCALYBG2iAPoqsaWQJR00mHKkRVEMUdxLlEAbwBQAXwULQkWAkRQM3anQYs2nabz7yFiKynTY8hHuWp8A3JetUAdFDgBVAA7+2ADCaBgUrsqqOnoALK5AA).

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: TypeScript
Issue: Allow overload signatures when writing class property initializers
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
1) typescript class bound function parameter overload 
2) typescript class bound function overload 
3) typescript class bound method overload 
4) [typescript class bound arrow overload](https://stackoverflow.com/a/56109925) 

## Suggestion

<!-- A summary of what you'd like to see added or changed -->

It would be nice if we could overload bound arrow function methods in a class without the need to specifically declare a constructor and bind methods in it.

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

## Examples

<!-- Show how this would be used and what the behavior would be -->
```typescript
// existing valid implementation
// class `A` has method `a` bound to its instance in the constructor
class A {
  constructor(){
    this.a = this.a.bind(this);
  }

  a(a: string): string;
  a(a: string, b: string): string;
  a(a: string, b?: string): string {
    if(b) return a + b;
    return a;
  }
}

// suggested alternative implementation
// class `B` declares a bound arrow function `a` and its overloads without the need for a ctor
class B {
  a = (a: string): string;
  a = (a: string, b: string): string;
  a = (a: string, b?: string): string => {
    if(b) return a + b;
    return a;
  }
}
```

## 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: bitcoin
Issue: contrib: makeseeds.py improvements
Labels: P2P,Scripts and tools,good first issue

Some suggestions for improvements, or at least for discussion between major releases:


- [x] Read [suspicious hosts](https://github.com/bitcoin/bitcoin/pull/16999#issuecomment-536869449)  from a file (done in #17823, removed completely in #24862)
- [x] [Determinism](https://github.com/bitcoin/bitcoin/pull/16999#issuecomment-537070141) could be improved (this is useful for cross-checking)
    - [x] Read ASNs from a file (Done in #24864)
    - [x] Per-ASN limit [isn't consistently enforced?](https://github.com/bitcoin/bitcoin/pull/16999#issuecomment-537173086)
- [x] [A max of 2 seeds per ASN seems a bit strict](https://github.com/bitcoin/bitcoin/pull/16999#issuecomment-536999544) at lest for IPv6 (done in #24818)
- [x] [Should we bump MIN_BLOCKS?](https://github.com/bitcoin/bitcoin/pull/16999#issuecomment-536999544) (done in #24818)
- [x] Some [typos](https://github.com/bitcoin/bitcoin/pull/16999#pullrequestreview-295794240) in the comments
- [x] Handle and hardcode TorV3 peers (after #19954), see #20239
- [ ] Bring back onion functionality past TorV3 switch
    - [ ] We need a source of non-hardcoded V3 peers, currently the only ones are hardcoded and the seeder hasn't been updated to crawl v3 nodes yet (see sipa/bitcoin-seeder#92)
    - [ ] Consider increasing uptime requirements for Tor nodes from 10% as there [appear to be enough](#issuecomment-718622693)

#7398 was a previous attempt to improve this script, but was abandoned, maybe some changes are useful.
Repository: godot
Issue: Unrecoverable renaming error (without manual file edition)
Labels: bug,topic:editor,confirmed

**Godot version:**
branch master, commit bf8322376c97eee0f2ce25737c959bc33b945e60

**OS/device including version:**
Linux Mint 18.2 cinnamon 64bits

**Issue description:**
After an error of renaming in the editor, scene can not be opened anymore.

**Steps to reproduce:**

- in a scene, append another scene (via the file panel).
- in the file editor, rightclick on the imported scene and rename;
- during renaming, do not respect extension convention;
- confirm, close the main scene (if opened) and try to open it again => editor will refuse to load it and returns a **!sdata.is_valid()** error
- the renamed file also disappears from the file panel

In the main scene .tscn, i found this:

```
[ext_resource path="res://models/chair_tube.-eggtscn" type="PackedScene" id=3]
```
To fix: open the .tscn in a texteditor and make the extension and path right manually, save and re-open in the editor.

suggestions:
- propose a "view all" in the file panel to see hidden file -> also usefull when storing data on drive in custom file format
- in the right-click of the file panel, propose a "edit in text editor", as the editor already integrate a text editor!

It's not a critical issue for me but might be super annoying for noobs or people without programming reflexs.

All the best, godot rocks
Repository: vue
Issue: transitions with appear should be SSR with the "-enter" class
Labels: transition

### Version
2.6.10

### Reproduction link

```sh
mkdir vue-bug-repo
yarn init -y
yarn add vue vue-server-renderer
```


```js
// Step 1: Create a Vue instance
const Vue = require('vue')
const app = new Vue({
  data: () => ({ show: true }),
  template: `<div>
    <transition appear name="fade">
      <p v-if="show">
      Hello World
      </p>
    </transition>
  </div>`
})

// Step 2: Create a renderer
const renderer = require('vue-server-renderer').createRenderer()
renderer.renderToString(app).then(html => {
  console.log(html)
}).catch(err => {
  console.error(err)
})
```





### Steps to reproduce

- `node index.js`

### What is expected?

The server response should contain the `*enter` classes applied to the transitioning element. The `*active` classes should then be applied during the `hydration` so that the transition can appear smoothly.

### What is actually happening?

The element is first displayed, as if there were no transitions. Then then entire animation starts, causing wired animations.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: TypeScript
Issue: If all values used in a template literal have a literal type, then the template should have a literal type
Labels: Suggestion,In Discussion

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

template string, string literal, template string literal, cast template string as literal

## Suggestion

It seems all template strings are widened to type `string`; however, when all the variables used inside a template string have literal types, it would be nice if the resulting string also had a literal type.

## Use Cases

I maintain a library, and I'd like it if templated strings for CSS properties like box shadow would show up for my dev users in intellisense, instead of just "string".

Here's a screenshot showing the current behavior:

![image](https://user-images.githubusercontent.com/45078010/66056784-a9549280-e505-11e9-99cf-686700cb895c.png)

It would be very useful if `readonly boxShadow` and `readonly border` had literal types instead of a generic string type, to inform my devs what value is passed.

## Examples

```javascript

const elementColors = {
  ...
  globalFocus: '#ff0000',
  ...
} as const

const widths = {
  ...
  default: 4,
  ...
} as const

const shadow = {
  default: {
    boxShadow: boxShadow: `${ elementColors.globalFocus } 0 0 0 ${ width.default }px`,
  },
  ...
} as const
```

In the above, `typeof elementColors.globalFocus === '#ff0000'` and `typeof width.default === 4`, but `typeof shadow.default.boxShadow === string`. All of the parts used to create the template have literal types, so why doesn't the resulting string have a literal type? TypeScript should be able to infer that only a single possible value is valid for this. `typeof shadow.default.boxShadow` should equal `'#ff0000 0 0 0 4px'`.

## Checklist

My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
  * could be breaking for people who rely on templates having type string vs a literal type
* [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: rust
Issue: wrap llvm messages
Labels: A-LLVM,C-enhancement,A-diagnostics,T-compiler

When using `-Cpasses=lint`, llvm prints its messages directly into stderr
````
   Compiling smallvec v0.6.10
   Compiling syn v1.0.5
Unusual: unreachable immediately preceded by instruction without side effects
  unreachable, !dbg !113
Unusual: unreachable immediately preceded by instruction without side effects
  unreachable, !dbg !113
Unusual: unreachable immediately preceded by instruction without side effects
  unreachable, !dbg !113
   Compiling bitflags v1.2.0
````

I wonder if we could wrap them so that it is easier to figure out that they are coming from llvm when parsing cargo/rustc output.

`LLVM lint-pass: Unusual: unreachable...`
Repository: scrcpy
Issue: Chrome on Android 10 won't work if screen is off.
Labels: screenoff

I actually imagine this is likely Chrome's fault, from recent updates, but leaving info here in case:

Pixel 2 XL, Android 10.  Chrome and Chrome Beta will not work correctly if using scrcpy 1.10 on Windows 10, and I've turned the phone display off.

Both versions of Chrome will stop rendering tabs usually.  If they do manage to render a tab, it may not scroll properly, or will completely freeze and the app has to be force closed.  If I clear all storage/cache for them, they will usually open correctly again, but only after the first load.

I have observed this behavior both when using CTRL+O to turn the screen off, and when launching scrcpy-noconsole with -S