sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Suggestion: making exports visible only to the same directory with JSDoc @package tag
Labels: Suggestion,Awaiting More Feedback

## Search Terms

JSDoc package directory package-private

## Suggestion

If an export is annotated with `@package`, that export is visible only to files in the same directory.

I can think of two levels of `@package` support: a soft one would remove these exports from auto completion if not visible. A hard one would also emit a compile error.

See also: [Use JSDoc: @package](https://jsdoc.app/tags-package.html)


## Use Cases

We organize source code using directory structure. We often make exports that are meant to be referenced only by sibling modules. However, JavaScript/TypeScript has no idea of scoping based on file system, so we are free to import such "local" exports everywhere. TypeScript could help us do file system-based scoping.

## Examples

```ts
// ----- src/foo/bar.ts
/**
 * @package
 */
export fooBar = "fooBar";

// ----- src/foo/index.ts
// Can import fooBar from "./bar"
import { fooBar } from "./bar";

// ----- index.ts
// CANNOT import fooBar from "./foo/bar"
import { fooBar } from "./foo/bar";
```


## 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: node
Issue: The rss memory not recall after a lot of file writing
Labels: memory

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**: 14.15.0
* **Platform**: Linux   3.10.0-693.2.2.el7.x86_64 #1 SMP Tue Sep 12 22:26:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
* **Subsystem**:

### What steps will reproduce the bug?

<!--
Enter details about your bug, preferably a simple code snippet that can be
run using `node` directly without installing third-party dependencies.
-->
```javascript
const fs = require('fs');
const path = require('path');
const MAX_SIZE = 1000 * 1000;
console.time('write');
let count = 0;
console.log('pid', process.pid);
function write(stream, i) {
    stream.end(JSON.stringify({index:i}), function(err) {
        stream.destroy();
        if (err) {
            console.error('write error', err);
        }
        count++;
        if (count === MAX_SIZE) {
            console.timeEnd('write');//write: 498283.611ms
        }
    });
}
for(var i=0; i< MAX_SIZE;i++) {
    const filename = path.join(__dirname, 'files/' + i + '.json');
    const stream = fs.createWriteStream(filename);
    write(stream, i);
}
setInterval(function() {}, 1000);
```
After run this code, the node occupy about 800MB memory, most of that is outside the heap. I had tried the version of `12.18.4`, it has the same problem. I wonder how to recall the memory.
Repository: rust
Issue: Intra-doc links do not resolve associated items for blanket impls
Labels: T-rustdoc,A-trait-system,C-bug,A-intra-doc-links

<!--
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.
-->

I tried this code:

```rust
pub trait Trait {
    fn f();
}
impl<T> Trait for T {
    fn f() {}
}

pub mod inner {
    use crate::Trait;
    /// Link to [S::f]
    pub struct S;
}
```

I expected to see this happen: The link resolves to `<S as Trait>::f`

Instead, this happened: rustdoc can't resolve the link:

```
warning: unresolved link to `S::f`
  --> blanket.rs:10:18
   |
10 |     /// Link to [S::f]
   |                  ^^^^ the struct `S` has no field or associated item named `f`
   |
   = note: `#[warn(broken_intra_doc_links)]` on by default
```

### Meta
<!--
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.
-->

`rustdoc +nightly --version`: `rustdoc 1.49.0-nightly (ffa2e7ae8 2020-10-24)`

cc @seeplusplus

After seeing https://github.com/rust-lang/rust/issues/78761 I'm strongly considering getting rid of blanket impls altogether, clearly no one has been using them or they would have opened an issue. @Manishearth what do you think?

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":null}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: create-react-app
Issue: fast refresh not working when using some babel macro
Labels: stale,needs triage,issue: bug report

### Describe the bug

I'm using `autobg.macro` in my project, which works fine in `react-scripts@3`, but when using it with v4, the fast refresh feature does not work. I have to reload my page every time to get the update.

`src/App.js`

```js
import styled from 'styled-components/macro';
import autobg from 'autobg.macro';

const Map = styled.div`
  ${autobg('./assets/map.jpg')}
`;

function App() {
  return <Map />;
}

export default App;
```

`autobg.macro` doc link: https://github.com/littlee/autobg.macro

### Did you try recovering your dependencies?

yes

### Which terms did you search for in User Guide?

did not find anything helpful

### Environment

```
Environment Info:

  current version of create-react-app: 4.0.0
  running from /Users/lixiaokai/.npm/_npx/37617/lib/node_modules/create-react-app

  System:
    OS: macOS 10.15.7
    CPU: (4) x64 Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz
  Binaries:
    Node: 14.15.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.8 - /usr/local/bin/npm
  Browsers:
    Chrome: 86.0.4240.183
    Edge: Not Found
    Firefox: Not Found
    Safari: 14.0
  npmPackages:
    react: ^17.0.1 => 17.0.1
    react-dom: ^17.0.1 => 17.0.1
    react-scripts: 4.0.0 => 4.0.0
  npmGlobalPackages:
    create-react-app: Not Found
```

### Steps to reproduce

1. edit `src/App.js` to

```js
import styled from 'styled-components/macro';
import autobg from 'autobg.macro';

const Map = styled.div`
  ${autobg('./assets/map.jpg')}
`;

function App() {
  return <Map />;
}

export default App;
```

2. edit `src/App.js`, add some `<h1 />` or anything

3. switch to the browser, wait for the update


### Expected behavior

the browser should update the page without a full reload


### Actual behavior

the browser does not update the page until a manually full reload
Repository: vscode
Issue: Implement Debugger Modules View
Labels: feature-request,debug

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

Like in VS:
[![VS Modules View](https://docs.microsoft.com/en-us/visualstudio/debugger/media/dbg-tips-modules-window.png)](https://docs.microsoft.com/en-us/visualstudio/debugger/debugger-tips-and-tricks?view=vs-2019#modules_window)
As part of the official DAP: https://microsoft.github.io/debug-adapter-protocol/specification#Requests_Modules

Can be done with a simple TreeDataProvider like in: https://github.com/vadimcn/vscode-lldb/blob/master/extension/modulesView.ts

The debug adapter part has been [merged](https://github.com/microsoft/MIEngine/pull/1040#issuecomment-710353360) recently for the cpp extension and finally released: https://github.com/microsoft/vscode-cpptools/releases/tag/1.1.0
Repository: excalidraw
Issue: Significant frame rate drops in dark mode
Labels: performance ⚡️

Has anyone else experienced any significant drops in frame rate while performing actions in dark mode?

I really noticed this when dragging selections on a blank canvas.

in light mode:
![image](https://user-images.githubusercontent.com/34794189/98356016-de8db700-201a-11eb-95bf-82ff1191abc0.png)

in dark mode:
![image](https://user-images.githubusercontent.com/34794189/98356068-f402e100-201a-11eb-91e6-5025fe0c43f6.png)

Those dips on the graph is when i'm doing any kind of dragging/selecting.

Browser:
Firefox 82.0.2

OS: Pop!_OS
Repository: three.js
Issue: controls end event broken for mousewheel
Labels: Enhancement

**Describe the bug**

Currently mousewheel is treated like this in controls:

```jsx
function onMouseWheel(event) {
  if ( scope.enabled === false || scope.enableZoom === false || ( state !== STATE.NONE && state !== STATE.ROTATE ) ) return
  event.preventDefault()
  event.stopPropagation()
  scope.dispatchEvent(startEvent)
  handleMouseWheel(event)
  scope.dispatchEvent(endEvent)
}
```

That means that `start` and `stop` for zoom cannot be relied upon as it behaves differently from all other gestures, pan and rotate for instance. This makes it hard to detect when the control has stopped on the parental level.

We started to notice this because we render on demand. Controls tell the state model that the scene is moving or not. Zoom caused issues when the canvas flips on-demand-rendering on and off.

**To Reproduce**

https://codesandbox.io/s/r3f-basic-demo-forked-omcxr

Open the dev console and pan, you will see 1 start, 1 stop. Zoom and it will spit out hundreds of start/stops.

**Expected behavior**

`start` and `stop` should not leak internals, they should tell the user when controls are active and when not. As long as controls are dollying, either because mousewheel is firing in sequence or because damping is enabled, `stop` should not be called. In this case it has to anticipate browser behaviour and debounce the tail call. It could do the same to `start` with a leading call but it's not as important imo.

```jsx
import debounce from "lodash-es/debounce"

const debouncedEnd = debounce(() => scope.dispatchEvent(endEvent), 100)

function onMouseWheel(event) {
  if ( scope.enabled === false || scope.enableZoom === false || ( state !== STATE.NONE && state !== STATE.ROTATE ) ) return
  event.preventDefault()
  event.stopPropagation()
  scope.dispatchEvent(startEvent)
  handleMouseWheel(event)
  debouncedEnd()
}
```
Repository: vscode
Issue: Suggestion details shown on the left of suggestion list hide text and cursor
Labels: suggest,under-discussion

Issue Type: <b>Bug</b>

Trigger suggestion on a small enough VS Code window, and it renders suggestion details on the left of suggestion list, completely hiding code snippet and cursor. Suggestion details can be resized, but since its bottom right corner is glued to the suggestion list, it still hides the input unless you resize it to be so small that it's useless.

<img width="1024" alt="Screen Shot 2020-11-06 at 13 51 02" src="https://user-images.githubusercontent.com/68182/98358049-2cb0b380-2037-11eb-9d3e-294e420df720.png">

<img width="1024" alt="Screen Shot 2020-11-06 at 13 51 10" src="https://user-images.githubusercontent.com/68182/98358069-32a69480-2037-11eb-95ba-934f02fef301.png">


VS Code version: Code 1.51.0 (fcac248b077b55bae4ba5bab613fd6e9156c2f0c, 2020-11-05T18:14:40.758Z)
OS version: Darwin x64 19.6.0

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-1030NG7 CPU @ 1.10GHz (8 x 1100)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (0.32GB free)|
|Process Argv|-psn_0_2912967|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (6)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-markdownlint|Dav|0.37.2
vscode-pull-request-github|Git|0.21.0
go|gol|0.18.1
remote-ssh|ms-|0.55.0
remote-ssh-edit|ms-|0.55.0
rewrap|stk|1.13.0

(1 theme extensions excluded)

</details>
<!-- generated by issue reporter -->
Repository: create-react-app
Issue: Improve Documentation on adding-images-fonts-and-files.md 
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

When looking at the documentation here: https://create-react-app.dev/docs/adding-images-fonts-and-files/
It talks about adding in images, fonts and files.
However all examples/info is about Images and SVGs.



### Describe the solution you'd like

I'd like to see more examples of using fonts here as that is part of what the page talks about.
Repository: flutter
Issue: [doc] Explain how hot-restart works and  why deactivate (dispose) not called on hot restart 
Labels: tool,t: hot reload,d: api docs,P3,team-tool,triaged-tool

In my flutter web app I use websocket which is connects when user is logged in. Websocket is connecting in `initState` of Home widget and disconnects in `dispose`:

`main.dart`:
```dart
...
MaterialApp(
  home: isLoggedIn ? Home() : Login(),
),
```
`home.dart`:
```dart
@override
void dispose() {
  super.dispose();
  // disconnect from websocket - NEVER called
}

@override
void initState() {
  super.initState();
  // connect to websocket - called always
}
```

All works fine until I did modifications in my code and click save. Yes, I know that flutter web does not supports hot reload (to catch it) and hot restart just re-create app but why deactivate and dispose methods not called? This cause that I reach maximum websocket connections during development and I need to restart debug session. 

Is it possible to fix this?
Repository: terminal
Issue: Local Echo: Predict the display of remote characters
Labels: Issue-Feature,Area-Output,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
Predict characters that will be displayed in the terminal without having to wait for the shell. This is done in the 1.51 release of Visual Studio Code and is explained in detail on its release notes: [https://code.visualstudio.com/updates/v1_51\#_local-echo](https://code.visualstudio.com/updates/v1_51\#_local-echo)

As explained in the Visual Studio Code release notes, this will be particularly useful when working over an ssh connection.
<!-- 
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)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: rust
Issue: Error on deriving PartialEq on Foo and then implementing it for dyn Foo
Labels: A-macros,T-compiler,A-MIR,C-bug

I tried this code:

```rust
trait Foo {}

impl PartialEq for dyn Foo {
    fn eq (self: &'_ Self, _: &'_ Self) -> bool { false }
}

#[derive(PartialEq)]
struct Bar {
    __: ::std::rc::Rc<dyn Foo>,
}
fn main () {}
```

I expected to see this happen:

A working `PartialEq` derived implementation for `Bar`.

Instead, this happened:
An error was thrown:

```rust
error[E0507]: cannot move out of `*__self_1_0` which is behind a shared reference
 --> src/main.rs:9:5
  |
9 |     __: ::std::rc::Rc<dyn Foo>,
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^ move occurs because `*__self_1_0` has type `Rc<dyn Foo>`, which does not implement the `Copy` trait
  |
  = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error

For more information about this error, try `rustc --explain E0507`.
error: could not compile `playground`

To learn more, run the command again with --verbose.
```

### Meta
The bug is present on nightly and stable in the two versions I tried:
`rustc --version --verbose`:
```
rustc 1.49.0-nightly (ffa2e7ae8 2020-10-24)
binary: rustc
commit-hash: ffa2e7ae8fbf9badc035740db949b9dae271c29f
commit-date: 2020-10-24
host: x86_64-pc-windows-msvc
release: 1.49.0-nightly
LLVM version: 11.0
```

`rustc --version --verbose`:
```
rustc 1.46.0 (04488afe3 2020-08-24)
binary: rustc
commit-hash: 04488afe34512aa4c33566eb16d8c912a3ae04f9
commit-date: 2020-08-24
host: x86_64-pc-windows-msvc
release: 1.46.0
LLVM version: 10.0
```

Backtrace doesn't show anything different than the error.
Here is the reproducable code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=a4d7bd689ed0687e24533f956f7a5971
@danielhenrymantilla seemed interested in the issue.
Repository: PowerToys
Issue: Unzip multiple compressed files at once
Labels: Idea-New PowerToy

## Add the ability to extract the contents of multiple zip files at the same time and into the same location

_What is the expected behavior of the proposed feature?  What is the scenario this would be used?_

Consider downloading multiple zip files. To get at the contents of all of them, each must be individually opened and the contents extracted to the desired location. It would be great if there was a way (power toy) that would let me select multiple zip files at once and then allow me to specify a single directory where the contents of all the zip files would be extracted to.

An option to maintain (or not) the directory structure within the compressed files would be nice.

An option to automatically handle multiple files with the same names (collisions) would be a nice to have.

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: pytorch
Issue: Hackable python-only autograd engine
Labels: module: autograd,triaged

## 🚀 Feature
Create an autograd engine from scratch only in pytorch for easy experimentation and interoperability with other python-only features. It should follow the current design very closely to simplify implementation.
It requires:
- An execution engine to run a given graph
- A basic Tensor sub-classing to create the backward graph based on `__torch_function__`
- A simple API to create these Tensors and call into the engine
- Use the codegen and derivatives.yaml to generate the backward formulas for most of our functions

## Motivation
This came up when discussing how to interface Tensor subclasses built in python with `__torch_function__` and the autograd that lives only in c++. We would need a simple and hackable testbed for such features before investing in expensive modifications of the lowlevel engine we have.

Another motivation for such system is that it would be very easy for researcher to modify and experiment with.
In particular, projects like [backpack](https://github.com/f-dangel/backpack) could move away from the intensive hook usage and be more efficient.
It would also serve as an example on how to easily create backward-like passes on top of pytorch.

## Open questions
Does this need to live in core or should we have a side repo for it?

Do we want to support view/inplace in the first version?
Do we want to simplify "saving for backward" by just cloning in the first version?



cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved
Repository: PowerToys
Issue: Define keyboard shortcut to foreground a window running in a zone.
Labels: Idea-Enhancement,FancyZones-Editor,Product-FancyZones

My use case is that I have several programs running and assigned one per FancyZone. I want to assign keyboard shortcuts to FancyZones, that when pressed, bring the window running in that zone to the foreground to receive input. This allows much faster swapping between programs without removing my hands from the keyboard.

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: godot
Issue: Unable to load plugin when using minifyEnabled
Labels: bug,platform:android,topic:buildsystem,topic:plugin

**Godot version:**
3.2.3-stable-mono

**Issue description:**
Godot Google Play Billing plugin not loaded when using minifyEnabled in build.gradle


**Steps to reproduce:**
1. Install Android build template for "Dodge the Creeps"
2. Edit build.gradle file like so:

`    buildTypes.all { buildType ->
        buildType.zipAlignEnabled false
        buildType.signingConfig null
        minifyEnabled true
    }`

3. Run it on real device

**Minimal reproduction project:**
APK: https://www.file-upload.com/ru11gs0rsalp


@m4gr3d
Repository: flutter
Issue: [ios] Ownership of FlutterPlatformViewsController is not very clear
Labels: team,platform-ios,engine,P3,c: tech-debt,team-ios,triaged-ios

On initial glance it seems to be owned by the engine but the shared refs are passed around a bunch. We should refactor to remove the shared_ptr usage of the FlutterPlatformViewsController.

Right now its shared between:
1. Engine
2. PlatformViewsIOS
3. A11y bridge
4. Gesture recognizers
5. IOSExternalViewEmbedder

cc: @gaaclarke
Repository: tensorflow
Issue: tf.linalg.pinv also for complex matrices
Labels: stat:awaiting tensorflower,type:feature,comp:ops

<em>Please make sure that this is a feature request. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template</em>


**System information**
- TensorFlow version (you are using): 2.3
- Are you willing to contribute it (Yes/No): Yes



**Describe the feature and the current behavior/state.**

Right now, as stated in [the docs](https://www.tensorflow.org/api_docs/python/tf/linalg/pinv#args), the `pinv` operator accepts only float-like matrices.
It would be nice to have it accept complex matrices as well, like `numpy` does.

**Will this change the current api? How?**

No

**Who will benefit with this feature?**

People working with complex matrices.
I typically work with MRI data which is naturally complex, but I guess this can be applied to other domains.

**Any Other info.**

I checked in the latest [`tf.experimental.numpy`](https://www.tensorflow.org/api_docs/python/tf/experimental/numpy), and it's absent. But maybe the complex-supported `pinv` should be better there, I don't know.