sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: Open new terminal tab in same directory as existing tab (OSC 7?)
Labels: Issue-Feature,Product-Powershell,Product-Conpty,Area-VT,Area-Settings,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

Have the option (or default) of a new terminal tab opening in the current directory of the window of which you hit the hotkey to open a new tab. This is the standard way most linux terminals work and is most handy. I often work in a directory where I need to launch multiple seperate processes, its a pain to CD back into the directory each time.

# Proposed technical implementation details (optional)

Hit the new tab hotkey, the new terminal should then be in the same folder as the previouse.


----

_maintainer edit: Before commenting, make sure to check out_

# [Tutorial: Opening a tab or pane in the same directory in Windows Terminal](https://learn.microsoft.com/en-us/windows/terminal/tutorials/new-tab-same-directory)

This is largely something configurable today, this issue is just tracking _another_ way of configuring this
Repository: pytorch
Issue: Version number is still duplicated in a bunch of places
Labels: module: binaries,triaged,better-engineering

Current sites:

https://github.com/pytorch/pytorch/pull/27751
https://github.com/pytorch/pytorch/pull/27374

cc @ezyang @pbelevich @soumith
Repository: TypeScript
Issue: Suggestion: disallow synthetic imports for ES modules
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. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.6.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** allowSyntheticDefaultImports esModuleInterop babel synthetic es modules default exports imports commonjs

**Code**

`allowSyntheticDefaultImports` is great when you're importing a _CommonJS module_, where/when Babel/TS will make sure there is a `default` export/import via their "interop" layers (e.g. `esModuleInterop`).

```ts
// foo.js
exports.foo = () => {}
```

```ts
// foo.d.ts
declare const _default: { foo: () => {} }
export = _default
```

```ts
// main.ts
import Foo from './foo';
Foo.foo(); // all good!
```

However, it's possible to shoot yourself in the foot by trying to import a non-existent `default` from an _ES module_.

```js
// foo.js
export const foo = () => {}
```

```ts
// foo.d.ts
export declare const foo: () => {}
```

```ts
// main.ts
import Foo from './foo'; // no error, but should be `* as Foo`!
// runtime error!!
// TypeError: Cannot read property 'foo' of undefined
Foo.foo();
```

Ideally it would not be possible to use synthetic default imports with an ES module, so runtime errors such as the one above would not happen.
Repository: godot
Issue: url, b, u and i tags in RichTextLabel don´t respect the margin
Labels: bug,topic:gui

**Godot version:** 3.1.1-stable_win32

**OS/device including version:** Windows 7/PC

**Issue description:** When a text marked with a url, u, b or i tag inside a Richtextlabel hits the margin area, it just go over the margin no matter what. The regular text detects the margin and jumps to the next line, but the tags doesn´t and just continue like no margin is in place.

**Steps to reproduce:** 
-Create a Rich text label, set a right margin and disable scroll_active.
-Fill the Richtextlabel with a text so a word marked with a tag reaches the right margin.
-Enjoy the bug!

**Minimal reproduction project:**
See the word "Paleolítico" in the second line of this capture:
![bug](https://user-images.githubusercontent.com/17690275/66674983-a4f64b00-ec64-11e9-8271-5cf228739ec1.png)
Repository: pytorch
Issue: Test `make html-stable` target in CI
Labels: triaged,module: doc infra

Right now, in the CI, we build master docs on all PRs. Every time a release comes around I am nervous if the stable docs (built with `make html-stable`) are buildable or not. We should also build stable docs on all PRs.

cc @ezyang @zou3519
Repository: flutter
Issue: Report more detail about hot reload/restart failures to analytics
Labels: tool,t: hot reload,from: study,a: quality,a: annoyance,P2,team-tool,triaged-tool

The tool sometimes fails to send analytics when there is an exception during hot reload, like here:

https://github.com/flutter/flutter/blob/e76160703f0a027c90d2c71ebfcb829306edccd2/packages/flutter_tools/lib/src/run_hot.dart#L774

Also, the tool could send more information on a rejection notice from the VM. Currently these messages are dropped here:

https://github.com/flutter/flutter/blob/e76160703f0a027c90d2c71ebfcb829306edccd2/packages/flutter_tools/lib/src/run_hot.dart#L507

These messages come from a few different places in the VM, and a rejection notice could in theory contain several messages, so a component of this issue may be asking for a summary message from the VM, or reporting only the first message in the notice to analytics.

Search term in the VM code: 'ReasonForCancelling' like

https://github.com/dart-lang/sdk/blob/90ff37e0115c301cb742f894f64f4e3c78879df7/runtime/vm/isolate_reload.cc#L266 

and

https://github.com/dart-lang/sdk/blob/90ff37e0115c301cb742f894f64f4e3c78879df7/runtime/vm/object_reload.cc#L562
Repository: pytorch
Issue: torch.cuda.default_generators documentation referenced but don't exist.
Labels: high priority,module: docs,module: cuda,triaged

https://github.com/pytorch/pytorch/blob/master/docs/source/torch.rst (scroll down to default_generators)

cc @ezyang @gchanan @zou3519 @jerryzh168
Repository: godot
Issue: Parser Error: Identifier '_some_singleton' not declared in the current scope.
Labels: bug,topic:gdscript,confirmed

**Godot version:**
3.1.1

**OS/device including version:**
Win 10

**Issue description:**
When pressing F6 to play a scene, the parser error in the title is thrown referring to a AutoLoad singleton. This happens only sometimes - reopening Godot and the project makes the problem rarer in my case. This doesn't happen on a simple (minimal) project. Only seems to happen when there are more singletons / more stuff in them (one of them is a simple scene). The order of singletons doesn't seem to matter: it's either all loaded or none.

I've found same / similar issue here: #3156 but since asked in the discussion, here is a new bug report.

**Update:**
My last uneducated guesses are that it has something to do with script errors that might be elsewhere. Seems to happen more frequently, when you change a script and save it but do not yet re-save other scripts that extend on it. (Doing this, in any case, causes often problems: from minor problems with refreshing export variables in the inspector to crashing the whole engine.) Just don't understand why it happens only sometimes (as if by a coin toss).
Repository: pytorch
Issue: docs for torch.cuda.reset_max_memory_reserved don't exist
Labels: module: docs,module: cuda,triaged

The documentation has an[entry for it](https://github.com/pytorch/pytorch/blob/master/docs/source/cuda.rst), but the documentation website [doesn't have it](https://pytorch.org/docs/master/cuda.html).
Repository: go
Issue: x/website: link to /dl from project and release history pages
Labels: Documentation,NeedsInvestigation,website

It'd be nice to get the download page linked from more places like The Project, Release History, and the release pages. 

I always end up on the releases pages first and then don't see a link to find the sha256s and URLs to grab them. It'd be nice to just have link to the downloads page on those
Repository: TypeScript
Issue: Expose `resolvedModules` property of `SourceFile`
Labels: Suggestion,API,Awaiting More Feedback

**TypeScript Version:**  3.6.4

**Code**

```ts
import * as ts from 'typescript'

function createCompilerHost(): ts.CompilerHost {
  function fileExists(fileName: string): boolean {
    return ts.sys.fileExists(fileName)
  }

  function readFile(fileName: string): string | undefined {
    return ts.sys.readFile(fileName)
  }

  function getSourceFile(
    fileName: string,
    languageVersion: ts.ScriptTarget,
  ) {
    const sourceText = ts.sys.readFile(fileName)
    return sourceText !== undefined
      ? ts.createSourceFile(fileName, sourceText, languageVersion)
      : undefined
  }

  function resolveModuleNames(moduleNames) {
    return moduleNames.map(() => undefined)
  }

  return {
    getSourceFile,
    getDefaultLibFileName: () => 'lib.d.ts',
    writeFile: (fileName, content) => ts.sys.writeFile(fileName, content),
    getCurrentDirectory: () => ts.sys.getCurrentDirectory(),
    getDirectories: path => ts.sys.getDirectories(path),
    getCanonicalFileName: fileName =>
      ts.sys.useCaseSensitiveFileNames ? fileName : fileName.toLowerCase(),
    getNewLine: () => ts.sys.newLine,
    useCaseSensitiveFileNames: () => ts.sys.useCaseSensitiveFileNames,
    fileExists,
    readFile,
    resolveModuleNames,
  }

}

const options = {
  module: ts.ModuleKind.ES2015,
  target: ts.ScriptTarget.ES5,
}
const host = createCompilerHost()
const sourceFiles = ts.createProgram(['./test.ts'], options, host).getSourceFiles()
const matchsFile = sourceFiles
  .filter(s => {
    return s.resolvedModules.has('typescript')
  })

```

**Expected behavior:**
Property 'resolvedModules' should exist on type 'SourceFile'

**Actual behavior:**
![image](https://user-images.githubusercontent.com/28128450/66694140-170d7500-ece3-11e9-98c3-4f77ffa64722.png)
Repository: godot
Issue: _init() not work in visual script
Labels: bug,confirmed,topic:visualscript

**Godot version:**  Godot 3.2 alpha2

**OS/device including version:** Ubuntu 18.04 LTS x86_64

**Issue description:** _init() not work in visual script

**Steps to reproduce:**
Create a simple visual script like:
![init_bug_screenshot](https://user-images.githubusercontent.com/5593546/66697043-7b8cfc00-ed04-11e9-9f73-55258f2c3742.png)

Nothing was printed in the output tab when running.

I also tried to assign a value to a member variable in _init(). But I found its value was not changed when I printed in _ready() function.

**Minimal reproduction project:**
Repository: vscode
Issue: Support for RHEL 8 in FIPS mode
Labels: help wanted,feature-request,install-update,linux

<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.39.1
- OS Version: RHEL 8 (Red Hat Enterprise Linux 8)

Steps to Reproduce:

1. Enable FIPS in RHEL 8
2. Attempt to install VS Code

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: n/a


Most likely causes:
* VS Code may not officially support RHEL 8
* VS Code's RPM uses a non-FIPS algorithm for the per-file digest and other cryptographic operations, most likely MD5.


```
[root@rhel8 ~]# dnf install code
Updating Subscription Management repositories.
Dependencies resolved.
==========================================================================================================================================================================
 Package                             Arch                                  Version                                              Repository                           Size
==========================================================================================================================================================================
Installing:
 code                                x86_64                                1.39.1-1570750844.el7                                code                                 77 M

Transaction Summary
==========================================================================================================================================================================
Install  1 Package

Total download size: 77 M
Installed size: 77 M
Is this ok [y/N]: y
Downloading Packages:
code-1.39.1-1570750844.el7.x86_64.rpm                                                                                                     5.6 MB/s |  77 MB     00:13    
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                                                                     5.6 MB/s |  77 MB     00:13     
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
  package code-1.39.1-1570750844.el7.x86_64 does not verify: no digest

Error Summary
-------------
```

Workaround (with RPM in current directory):
```
[root@rhel8 ~]# rpm --nofiledigest --nodigest --install code-1.39.1-1570750844.el7.x86_64.rpm
```
Repository: terminal
Issue: cursorWidth for vertical bar
Labels: Help Wanted,Area-Settings,Product-Terminal,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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

My preferred cursor shape is "bar", and thus I'm happy to see that this is WT's default.

(My reason is that this is what every modern application does, carrying the semantics that the cursor is between two characters rather than over one. I found that in the terminal-based apps I'm using it becomes more obvious to know e.g. the boundaries of a piece of text as I'm selecting it, without potential off-by-ones – especially when the application uses inverse colors for the selected text, and so does the terminal for its solid rectangle cursor.)

There's one big disadvantage though: It's hard to locate if your eyes don't know where to look for it.

So I propose a config option to make the bar wider, analogously to the already existing "cursorHeight" for "vintage".

(On a side note, I'm wondering why "cursorHeight" doesn't apply to "underscore" too; in fact, why these are two different cursor shapes rather than one with a different height...)

# Proposed technical implementation details

A new option "cursorWidth" for the "bar" shape, or perhaps "cursorHeight" and "cursorWidth" merged into a common option.

I don't have a firm opinion whether the width should grow only to the right, or evenly to both sides. I'd probably only increase it from 1px to 2px for myself, so it doesn't really matter to me. I'd leave it to you to make a choice. In VTE it only grows to the right, mostly because we only have a 1px padding by default as opposed to your 8px, and we wouldn't want to chop it off when it's at the beginning of a line.
Repository: TypeScript
Issue: Improve Intellisense for String Enums
Labels: Bug

<!-- 🚨 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

-->

## Suggestion

String Enums should get a dropdown intellisense when `=== ""` is typed.
![paqLP9oYjv](https://user-images.githubusercontent.com/15217173/66704126-022ee280-ecdf-11e9-95b5-4fe734d356e5.gif)

Note that TS properly knows that `x === ""` is always false in both cases, since it knows `x` is `"A" | "B" | "C" | "D" | "E"`.

Interestingly, intellisense properly displays all the string methods when `x.` is typed.

![image](https://user-images.githubusercontent.com/15217173/66704147-28548280-ecdf-11e9-8c32-131c4bc78348.png)

<!-- A summary of what you'd like to see added or changed -->

## Use Cases

This feature would make it easier to use string enums defined by libraries, especially in the case of same-name index-value pairs like `A = "A"`.

That way, one could do:
```ts
x === "A"
```
Instead of:
```ts
x === Enum.A
```
<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

## 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).

**Related:** https://github.com/microsoft/TypeScript/issues/2151
**Search Terms:** string enum intellisense
<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
Repository: flutter
Issue: SliverAppBar not tappable while scrolling up when snap=true
Labels: framework,f: material design,f: scrolling,customer: quill (g3),has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-design,triaged-design

Internal: b/142343241

Steps to reproduce:
1. Create a simple sliver with a SliverAppBar with snap=true and SliverList.
2. Scroll down.
3. Scroll up.
4. While the scroll up is still in progress, tap the SliverAppBar.

Expected behaviour:
* SliverAppBar should remain, and the tap should be recognized and handled by widgets (eg. tab bar) on the app bar.

Actual behaviour:
* SliverAppBar disappears, due to an ScrollPosition.isScrollingNotifier handled, that calls maybeStartSnapAnimation when scrolling stops.
Repository: flutter
Issue: [url_launcher] Status bar color is not set
Labels: platform-ios,p: url_launcher,package,P3,team-ios,triaged-ios

Internal: b/140725708

url_launcher Flutter plugin doesn't update the status bar color when the Safari view controller is pushed. If the background color of the app is black (and/or app sets the status bar to white), the url_launcher will happily launch safari with the same configuration causing the status bar to disappear.
Repository: godot
Issue: If a `preload` is highlighted by wrong file name, renaming the file does not update the script editor
Labels: bug,topic:editor,confirmed,usability

Godot 3.2 alpha2

Say you have this in your script:
```gdscript
const MyShader = preload("./../my_shader.shader")
```
If the file name is actually `the_shader.shader`, it will cause the line to be highlighted red and produce an error.

Now if you rename your file to be `my_shader.shader`, it should match the script. However, the script editor still shows the error and only updates if you do an edit.

It probably also happens in the opposite case, where a path is initially correct but a rename makes it wrong.
Repository: TypeScript
Issue: Sorting an array removes type inference
Labels: Bug

**TypeScript Version:**  3.7.0-dev.20191011

**Search Terms:** type inference

**Code**

```ts
function getAllValuesUnsorted(m: ReadonlyArray<ReadonlyArray<string>>): ReadonlyArray<string> {
	// OK
	return Array.from(flatten(m.values()))
}

function getAllValuesSorted(m: ReadonlyArray<ReadonlyArray<string>>): ReadonlyArray<string> {
	// Type 'unknown[]' is not assignable to type 'readonly string[]'.
	return Array.from(flatten(m.values())).sort()
}

function* flatten<T>(a: Iterable<Iterable<T>>): Iterable<T> {
	for (const xs of a)
		for (const x of xs)
			yield x
}
```

**Expected behavior:**

No error.

**Actual behavior:**

```
a.ts:6:2 - error TS2322: Type 'unknown[]' is not assignable to type 'readonly string[]'.
  Type 'unknown' is not assignable to type 'string'.
```
Repository: go
Issue: x/website/internal/dl: document /dl/?mode=json API more prominently
Labels: Documentation,NeedsFix

It would be nice for the JSON mode of golang.org/dl to be documented somewhere (https://golang.org/dl/?mode=json). I wasn't able to find it until after I built a project to recreate the same functionality and someone pointed it out. 
Having a JSON API for Go releases is great and I think some folks would build more tools using it if we had it documented.
Repository: rust
Issue: Improve pretty printing of const raw pointers
Labels: C-enhancement,A-diagnostics,T-compiler,A-const-generics

#64986 changed the pretty-printing of const raw pointers to `{pointer}`. This can cause confusing diagnostics due to the lack of detail the printing of raw pointers provides, like the following:
```
error[E0308]: mismatched types
  --> $DIR/raw-ptr-const-param.rs:7:38
   |
LL |     let _: Const<{15 as *const _}> = Const::<{10 as *const _}>;
   |                                      ^^^^^^^^^^^^^^^^^^^^^^^^^ expected `{pointer}`, found `{pointer}`
   |
   = note: expected type `Const<{pointer}>`
              found type `Const<{pointer}>`
```