sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: Use react-scripts outside of a CRA project
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

My team developer a couple of CRA applications from a Lerna monorepo. And to make life easier, we don't install Jest, Webpack, etc. so we don't upset `CRA` with having different versions or use the `SKIP_PREFLIGHT_CHECK` flag .

 So for our non-CRA packages in the monorepo, we use run tests with `react-script test` in non-CRA packages. 

The issue is that the function [verifyTypeScriptSetup.js](https://github.com/facebook/create-react-app/blob/30fc0bf5ed566d9b42194d56541d278013d7928c/packages/react-scripts/scripts/utils/verifyTypeScriptSetup.js) forces an override our `tsconfig.json`, and is invoked every time the test script is running [scripts/test.js#L31](https://github.com/facebook/create-react-app/blob/30fc0bf5ed566d9b42194d56541d278013d7928c/packages/react-scripts/scripts/test.js#L31). In our case, adding `"noEmit": true`.

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

Similar to `verifyPackageTree()`, have a environment variable to skip this step
```javascript
if (process.env.SKIP_TYPESCRIPT_SETUP_CHECK !== 'true') {
  verifyTypeScriptSetup();
}
```

We need it for `react-scripts test`, but it is the same issue in all the other scripts

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

We currently have a `posttest` npm script invoking a node script to revert the change. Not scalable when we have N amount of new packages. 

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

I will love get feedback on this and to add this piece of code! 
Thank you CRA team for all your great work!
Repository: terminal
Issue: conhost: evaluate continued collection of connected process stats
Labels: Product-Conhost,Issue-Task,Area-CodeHealth,Priority-2

Are we still using the list of connected processes and their VT statistics? If not, we can declutter our lives and remove a potential source of community consternation.

https://github.com/microsoft/terminal/blob/master/src/host/telemetry.cpp#L287
Repository: flutter
Issue: hot_mode_dev_cycle__benchmark needs a more capable benchmark/regression tracking
Labels: c: new feature,team,tool,c: performance,P2,team-tool,triaged-tool

The hot reload/restart cycle is critical to the Flutter developer workflow, but our benchmarks that measure it don't tell the whole story. Unfortunately, when one of these benchmarks regresses it is extremely difficult to pinpoint the cause via bisecting due to:

1. The benchmark performs a large number of operations, making the possible candidate range quite large. That is, it could be a change to the tool, to the framework, to the gallery, to skia, to Dart...

2. The benchmark has a high variance on the device lab machines. This may be due to fundamental hardware constraints inherent in our benchmark setup. This also makes it difficult to reproduce locally.

These both lead to:

3. bisecting will not yield clear candidates, since the tests _must_ be repeated n times to gain an accurate measurement of the mean. But the number of test runs needed depends on the variance of the benchmark itself.

Now, we cannot simply _give up_ on these benchmarks, or accept arbitrary regressions. But if we're having trouble pinpointing the regression clearly some work needs to be done. Based on my experience bisecting  https://github.com/flutter/flutter/issues/57323 I believe the following needs to be done:


1. Create several smaller reference benchmarks for each large scale smoke test. In the case of hot reload/restart it would be something like measuring the execution time N times for:

   * hot reload, no invalidation.
   * hot reload, 1 invalidated file.
   * hot restart
   * runFromSource time (hot restart vm service request)

These numbers will provide guidance to the engineer bisecting. If the benchmark regresses and compile time does not, then we can rule out CFE/compiler changes. If runFromSource time regresses, it could be a VM issue. If none of them regress, it might be delay in render or it might be a hardware defect.

Most importantly, each of these operations is small enough that they could be run N times automatically, making the bisection process if they regress easier.

2. We need a framework for measuring the "Certainty" of our benchmark values that can allow us to auto-bisect.

Bisecting a change is fairly straightforward when its pass/fail. For benchmark regressions with variance it isn't so clear. While running each of the microbenchmarks above N times will help, in the case where the overall benchmark regresses we need tool assistance to find the culprit.

This could be done by evaluation of the hypothesis with N % (likely 95%) certainty, are the measurements at these two commits different. I'm not quite sure on the correct model here, we might need a non-parametric process but maybe something like a chi-squared test would be good enough.
Repository: terminal
Issue: Scenario: TerminalControl Interactivity Improvements
Labels: Area-Input,Area-TerminalControl,Product-Terminal,Issue-Scenario

This is a comprehensive list of improvements to our interactivity model for v2. This is not finalized and may be updated as new issues come in or we make cuts for v2.

## (Hidden) Refactors
- [ ] #5099: mouse selection should begin/end at nearest cell boundary (and be inclusive start exclusive end like accessibility!)
- [x] #5814: Use `til::point`
- [x] #3538: GenRTF() and GenHTML() should use shared components
- [ ] #4423: Refactor Word Expansion (shared between accessibility/selection)
- [x] #6842: Interactivity layer

## Selection

### Features
- [x] #4557: Shift+Multi-Click selection expansion
- [ ] #3884: persistent selection on copy
- [ ] Word Selection Improvements
   - [ ] #3077: Unicode character categories
   - [ ] #3077: regex support
   - [ ] #6178: double-click should line wrap if the word was broken across lines
- [ ] #4993: Scenario: Keyboard Selection
   - refer to the GitHub issue above for more details
- [x] Copy Formatted Text
   - #4191: add array support
   - #5262: add keybinding arg

### Bugs
- [x] #5626: start selection from padding
- [x] #5766: Shift+Click initial click doesn't work
- [ ] #11751



## Touch Interactions

### Features
- [ ] #3149: Touch Zoom
- [ ] #3109: Inertial Scrolling
- [ ] #5159: Touch Selection

## Miscellaneous Major Features
- [ ] SnapOnOutput:
   - [x] #980: pause scrolling when a selection exists
   - [x] #3863: pause scrolling when not at bottom
      - [ ] also add a keybinding for that (ScrollLock)
- [ ] #1553: Pointer Bindings

## Clipboard

- [ ] #6134 strip tabs when pasting, perhaps
Repository: three.js
Issue: Gamepad Support
Labels: Enhancement,Design

Is it possible to add Gamepad support for controllers.
It is well documented and I guess quite useful to get interaction for all buttons, touch pad, thumbstick on controllers.
https://immersive-web.github.io/webxr-gamepads-module/

PS: It looks like I don't have permission to add label Enhancement
Repository: three.js
Issue: SkinnedMesh.clone doesn't work properly, results in undefined skeleton property
Labels: Bug

When cloning `SkinnedMesh`, the resulting `SkinnedMesh` instance doesn't have `skeleton` property defined.

I'm not sure if this is also a bug, but having a `SkinnedMesh` with undefined `skeleton` crashes the renderer with:
```
 Uncaught TypeError: Cannot read property 'frame' of undefined
```

at

https://github.com/mrdoob/three.js/blob/f177bce88ea3ff48818a30ff09d871133fcd245b/src/renderers/WebGLRenderer.js#L1343

##### Example
https://jsfiddle.net/pwonz6gd/

##### Three.js version

- [x] dev
- [x] r115

##### Browser

- [x] All of them

##### OS

- [x] All of them


#### Solution?
EDIT: _(removed my horrible solution)_

As mentioned, one is supposed to use [SkeletonUtils.clone](https://threejs.org/docs/index.html#examples/en/utils/SkeletonUtils.clone). I'd still expect some kind of warning about this, instead of the whole renderer crashing.
Repository: deno
Issue: Installed scripts can't know their own name
Labels: cli,suggestion

There's no way for a `deno install`ed script to know its own name.

```
$ deno install -n cmdname https://url.to/script.ts
                  ^^^^^^^
```
This has a significant impact on CLI modules, that may need it for various reasons such as showing help messages and usage examples, registering shell completions etc.

Are there any plans to introduce this functionality somehow?
Repository: flutter
Issue: Remove all "await Future.delayed" logic from tests
Labels: a: tests,team,framework,P2,c: flake,team-framework,triaged-framework

Having a test just wait a few seconds is a race condition waiting to happen.

We should remove all occurrences of `Future<void>.delayed` in our tests.

For example:
https://github.com/flutter/flutter/blob/master/dev/integration_tests/ui/test_driver/keyboard_resize_test.dart#L36
Repository: go
Issue: runtime: move tests for runtime-gdb.py to a separate package and do not run them during all.bash
Labels: Testing,NeedsDecision,Debugging,compiler/runtime

The tests in `runtime-gdb_test.go`, for the GDB bindings in `runtime-gdb.py`, have historically been very flaky. They are currently skipped on a large fraction of platforms due to:
* #15603
* #17366
* #18784
* #20821
* #21380 / #22021 / #22687
* #22893
* #25939
* #28558
* #29508
* #35710
* and what appears to be an untracked issue for 'darwin': a skip was added in [CL 20193](https://golang.org/cl/20193), but neither the code itself nor any of the commentary I could find on the code review explains why `gdb` does or did not work on that platform.

If we had an incoming change to add a test with this many skips today, I suspect that we would turn it down: it tests what is supposed to be cross-platform code, but only checks the actual behavior of that code for a narrow subset of users — _because_ that behavior does not work reliably across platforms.

But it doesn't work reliably on the remaining tested platforms either: despite all of those skips, the tests are still flaky today:
* #24616 
   * Possibly fixed in [CL 233942](https://golang.org/cl/233942), which notes:
     > This part of the test has been flaky despite repeated attempts to fix it,
     > and it is unclear what exactly it is testing. Remove it.
* #25697
* #35743
* #37366
* #37405
* #37794
* #39021
* #39025
* #39228
* #43068
* #43825
* #48874
* #53431
* #58698
* #58932
* #61487
* #63728
* #64752
* #65176

#39021 in particular describes a regression during the 1.15 cycle that is interfering with the SlowBots and TryBots on pending CLs, will likely interfere with release testing as well, and so far has resisted attempts at bisection because the test (and its failure mode) is highly nondeterministic.

If we consider the runtime “incorrect” if it does not work with `gdb`, then we should take the time to fix and maintain the Go bindings properly and portably  — **not** just `Skip` their tests! — in the same way that we fix and maintain other features of the runtime across platforms. Otherwise, it is not appropriate to run the tests for those bindings as part of the tests for the `runtime` package, which is a dependency of most Go binaries (and is therefore likely to have its tests run in users' CI systems).

Most of the other Go project tests for integration with third-party tools are in the `misc` subdirectory. I propose that we move the `gdb` integration tests there.

I further propose that we should not run these tests as part of `all.bash`, `run.bash`, or on the Go project builders until such time as they can be made reliable, with only one `Skip` based on a check for a `gdb` executable at a sufficiently recent version.
Repository: godot
Issue: Listener3D will override hearing location even if not current
Labels: discussion,topic:core

**Godot version:**
3.2.1

**Issue description:**
So docs say that Listener
```
Once added to the scene tree and enabled using [method make_current], this node will override the location sounds are heard from.
```
However this is not true. You don't need to make it current, it will automatically become current if it's the first listener in the SceneTree.

Just check the code
https://github.com/godotengine/godot/blob/9239412027b6c25009efab69dc39650e0d76c56d/scene/3d/listener_3d.cpp#L82-L87

Either it should not behave like that or the documentation should be updated. Also this overrides Camera hearing even if it's added after it.
Repository: PowerToys
Issue: [Run] Allow open of bitlocker encrypted drives like windows search does
Labels: Idea-Enhancement,Product-PowerToys Run

On the windows search (start menu) I can enter the drive letter of an encrypted drive and after press enter I will be asked for the password.
In launcher this won't work.

Please add this functionality to launcher.

**Note:**
In start menu this command is marked as type "command".
Repository: terminal
Issue: Add a explorer context menu entry to let the user pick the profile they want to "open here"
Labels: Product-Terminal,Issue-Task,Area-ShellExtension

Follow up from #6100

We should add another entry to the explorer context menu to let the user select which profile.

This is the _only_ other option I'm considering at this time, I don't want to clutter that UI too badly.

#### notes:
* We could maybe allow arbitrary customization akin to what we're planning for #1571.
* #9749, #11348: people want to use `startupActions` in the specified directory
* #9991 maybe also relevant
Repository: terminal
Issue: The explorer context menu should only appear on shift+click
Labels: Help Wanted,Product-Terminal,Issue-Task,Area-ShellExtension

Follow-up from #6100. 

The Explorer context menu is notoriously cluttered. We shouldn't add to that clutter if we can avoid it. This issue represents me taking the time to investigate how exactly to make the menu only appear on shift+right click, not _just_ right click.
Repository: rust
Issue: Make core::panic::Location available from another module?
Labels: C-enhancement,T-libs-api,F-track_caller

I scanned the history but didn't see this question mentioned. Has there been any discussion about moving the Location type out of the std::panic module, or even just re-exporting under a different name if it needs to stay there for backwards compatibility?

I'm really looking forward to track_caller, but almost none of my use cases are panic related and panic is a pretty eye-catching word in code that causes me to do a double-take every time I encounter it. It seems like a superficial thing to discuss compared with all the implementation details, but I just wanted to provide my experience in case that aspect has been overlooked.

_Originally posted by @ggriffiniii in https://github.com/rust-lang/rust/issues/47809#issuecomment-618955432_

---

@anp's thoughts: I also have non-panicking uses in mind for `Location::caller` and have thought a couple of times about proposing an alias like `core::source::Location` or similar.
Repository: node
Issue: errorMonitor be emitted consistently
Labels: events

<!--
Thank you for suggesting an idea to make Node.js better.

Please fill in as much of the template below as you're able.
-->

**Is your feature request related to a problem? Please describe.**
No

In an event callback, the current way to capture an error in an `async` function is to have the `captureRejectionSymbol` defined. If that is not available, the `error` callback is executed. (Given `captureRejections` is true)


If we also place an `EventEmitter.errorMonitor`, then the `errorMonitor` is emitted when `captureRejectionSymbol` is not defined and the `error` is set. However, if the `captureRejectionSymbol` is available, then the `errorMonitor` is not invoked and only the `captureRejectionsSymbol` method is executed.

Here's a demo:-
```js
class MyEmitter extends EventEmitter {
  constructor() {
    super({ captureRejections: true });
  }
}

const myEmitter = new MyEmitter();

myEmitter.on(EventEmitter.errorMonitor, (err) => {
  console.log('Error monitor');
});

myEmitter.on('data', async () => {
  throw new Error();
})

myEmitter.on('error', (err) => {
  console.log('error handler');
})

myEmitter.emit('data');

//=> Error monitor
//=> error handler
```

**Describe the solution you'd like**
I was thinking that, for consistency, the `errorMonitor` event be emitted even when a `captureRejectionSymbol` method is available, just like `error`. The reason being that `captureRejectionSymbol` can be considered an alternative way of setting an `error`.

```js
class MyEmitter extends EventEmitter {
  constructor() {
    super({ captureRejections: true });
  }
  [captureRejectionSymbol]() {
    console.log('rejection');
  }
}

const myEmitter = new MyEmitter();

myEmitter.on(EventEmitter.errorMonitor, (err) => {
  console.log('Error monitor');
});

myEmitter.on('data', async () => {
  throw new Error();
})

myEmitter.on('error', (err) => {
  console.log('error handler');
})

myEmitter.emit('data');

//=> rejection 
```
but the proposed output should be
```js
//=> Error monitor
//=> rejection 
```
I tested the code on Node v14.2.0 (macOS).
I am not sure whether this is already implemented in some PR. I was not able to find one. I am also not sure of any backward compatibility that might be broken. So would like feedback on this. :)
Repository: PowerToys
Issue: [KBM] Allow users to map only modifier key shortcuts
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager

# Summary of the new feature/enhancement
Right now, if we try to set either the original shortcut or the new shortcut to finish on a modifier key (<kbd>Ctrl</kbd>, <kbd>Shift</kbd>, <kbd>Alt</kbd>, <kbd>Win</kbd>), the error message "Some of the keys could not be remapped. Do you want to continue anyway?" appears. Allowing users to remap shortcuts that end with a modifier key would allow users to have a bigger pool of shortcuts to modify (e.g. changing input keyboard layouts and input languages).

<!-- 
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: flutter
Issue: [Feature request] control padding on a ThemeData level
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

I was just looking for a padding property for CardTheme, but there was none. I would like a uniform padding across all my cards in the app...
<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: PowerToys
Issue: [Run] Apps don't launch proper folder (link target)
Labels: Idea-Enhancement,Help Wanted,Product-PowerToys Run

From #3422, a user requested copy file path, we have open containing folder however.

When trying out "word", this actually opens up the LNK folder, not the exe folder.

Example: I search for word and i get C:\ProgramData\Microsoft\Windows\Start Menu\Programs

In reality it should be: "C:\Program Files\Microsoft Office\root\Office16\"
Repository: pytorch
Issue: Memory Leak with Docker GPU
Labels: high priority,module: cudnn,module: cuda,module: memory usage,triaged,module: regression

## 🐛 Bug

I built a custom image based on `pytorch/pytorch:1.5-cuda10.1-cudnn7-runtime`, but it has memory leak once ran using docker with gpus. As an example, this ran (https://app.wandb.ai/cleanrl/cleanRL/runs/1giu2q8i?workspace=user-costa-huang) has its memory risen from 9% to 80% of 64 GB memory in minutes. In comparison, I rolled back to build the custom image based on `pytorch/pytorch:1.4-cuda10.1-cudnn7-runtime` and there is no such issues.

![image](https://user-images.githubusercontent.com/5555347/82630987-680f1100-9bc2-11ea-8ef2-cedbe0452310.png)


## To Reproduce

Steps to reproduce the behavior:

Obtain a wandb key from https://www.wandb.com/ and run the following

```
docker run --gpus all -d --cpuset-cpus="0" -e WANDB={YOUR_WANDB_KEY} vwxyzjn/cleanrl:1.5-cuda10.1-cudnn7-runtime-cleanrl-0.2.1 python dqn_atari_visual.py --gym-id BreakoutNoFrameskip-v4 --total-timesteps 10000000 --wandb-project-name cleanrl.benchmark  --prod-mode --capture-video --seed 2
```
Should reproduce the results where the memory blows up about 10 mins in. While the following script that uses the previous docker image of pytorch 1.4 should not have its memory blow up
```
docker run --gpus all -d --cpuset-cpus="0" -e WANDB={YOUR_WANDB_KEY} vwxyzjn/cleanrl:1.4-cuda10.1-cudnn7-runtime-cleanrl-0.2.1 python dqn_atari_visual.py --gym-id BreakoutNoFrameskip-v4 --total-timesteps 10000000 --wandb-project-name cleanrl.benchmark --prod-mode --capture-video --seed 2
```

And this is the Dockerfile

```
FROM pytorch/pytorch:1.5-cuda10.1-cudnn7-runtime

RUN apt-get update && \
    apt-get -y install xvfb ffmpeg git build-essential
RUN pip install gym[box2d,atari] pybullet==2.7.9
RUN git clone https://github.com/vwxyzjn/cleanrl && \
    cd cleanrl && pip install -e .
RUN apt-get -y install python-opengl
RUN pip install opencv-python
RUN pip install seaborn pandas

WORKDIR /workspace/cleanrl/cleanrl

COPY entrypoint.sh /usr/local/bin/
RUN chmod 777 /usr/local/bin/entrypoint.sh
ENTRYPOINT ["/usr/local/bin/entrypoint.sh"]
CMD python ppo2_continuous_action.py --capture-video --total-timesteps 200
```


<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

The following image is the expected behavior, which is produced by the previous pytorch 1.4 docker image(https://app.wandb.ai/cleanrl/cleanrl/runs/3az3ndy1?workspace=)
![image](https://user-images.githubusercontent.com/5555347/82631048-8ecd4780-9bc2-11ea-84bc-fc51dbded0fb.png)

In particular, the memory didn't blow up.



<!-- A clear and concise description of what you expected to happen. -->

## Environment

The experiments are ran using AWS batch at a GPU instance, and the docker image is based on `pytorch/pytorch:1.5-cuda10.1-cudnn7-runtime` that produces the memory explosion.


cc @ezyang @gchanan @zou3519 @ngimel @csarofeen @ptrblck