sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Inherited scenes don't inherit 'script variables' from the parent scene.
Labels: bug,topic:core

### Godot version

3.3.3-stable_mono

### System information

Linux 5.10.68-1-MANJARO, GT920M (Nvidia-470-PRIME) GLES3

### Issue description

Inherited scenes don't inherit default `script variables` from parent scene on runtime. On the editor, inherited scenes show default value properly. Happens on both GDScript and Mono (C#).
![Screenshot_20211013_192913](https://user-images.githubusercontent.com/17522480/137133375-89d255fd-b1b2-4ea3-b2c3-90bdf91bbd3c.png)
Ps. Strangely, if parent scene has only one `NodePath`, it inherits the `NodePath` properly. Others are still not inherited.
![Screenshot_20211013_192659](https://user-images.githubusercontent.com/17522480/137133434-aa741594-738f-43e2-ba1e-16e53efc8354.png)



### Steps to reproduce

Create a project which has 3 scenes, `one` is main scene for all others, `two` is a parent scene to contain GDScript version of bug reproduce, and `three` is the same as `two`, but in Mono (C#) version. Then inherit both `two` and `three` without any modifications except the root name (even with the root node name unchanged, it still has the same effect) Then run the test project and the bug occurs.

Configuration of `ParentGD`
![Screenshot_20211013_194237](https://user-images.githubusercontent.com/17522480/137135132-6a067312-c22b-4e10-baa5-36db8509ea17.png)

Configuration of `ParentMono` (C#)
![Screenshot_20211013_194445](https://user-images.githubusercontent.com/17522480/137135191-7e24335d-9f66-468f-a180-49c32384d0bf.png)


### Minimal reproduction project

[BugReproduce.zip](https://github.com/godotengine/godot/files/7338152/BugReproduce.zip)
Repository: vscode
Issue: Readonly repositories should make SCM input readonly also
Labels: bug,vscode.dev

Have a readonly repository. Notice the nice message in the SCM input box.
However the input box should also be readonly, so the placeholder text is always visible and that users can not type in it.
Since the input box is just an editor you should be able to easily set that as an editor option.

fyi @joyceerhl 

![Screenshot 2021-10-13 at 15 39 00](https://user-images.githubusercontent.com/1926584/137143978-0960de87-8dc9-4b59-af5a-53d1db74cc72.png)
Repository: PowerToys
Issue: Preview pane for zip files
Labels: Idea-New PowerToy,Product-File Explorer

### Description of the new feature / enhancement

In **PowerToys** File Explorer add-ons add a preview of folders and zip files too. 



### Scenario when this would be used?

It will make it will help to see the folder & zip file contents directly on the preview pane which would make search easy and make it overall better!

### Supporting information

_No response_
Repository: flutter
Issue: Set default keyboard language in textField
Labels: a: text input,c: new feature,platform-android,framework,c: proposal,P3,team-android,triaged-android

Hi I want to open the keyboard for user with default language I prefer.
For example open keyboard with English keyboard. No matter what language user entered before.

According what I searched there is not option like this.
But in Android native EditText[ there is an option like this.](https://developer.android.com/reference/android/widget/TextView#setImeHintLocales(android.os.LocaleList))
It Will be great to add this to Flutter!
Repository: opencv
Issue: Feature request: customizable InputArray
Labels: category: core,RFC

##### Detailed description

It would be nice to be able to use OpenCV with any custom type. Right now, we have to do:
```
MyType image_in(...), image_out(...);
cv::Mat cv_image_in = MyTypeToOpenCV(image_in);
cv::Mat cv_image_out;
cv::my_function(cv_image_in, cv_image_out);
OpenCVToMyType(image_out, cv_image_out);
```
But it would be nice to be able to do:
```
MyType image_in(...), image_out(...);
cv::my_function(image_in, image_out);
```

Here is a transcribed discussion with @vpisarev

Regarding InputArray — I was thinking of adding yet another kind of InputArray, InputArray::CUSTOM, and adding yet another pointer to the abstract class of virtual methods.

Right now, the code is:
```
class InputArray
{
     // various constructors
     InputArray(const Mat& m);
     InputArray(const std::vector<T>& vec);
     ...
     Mat getMat(int idx=-1) const;
     void create(...);
     ...

     int kind; // MAT, UMAT, STD_VECTOR etc.
     int type; 
     void* obj; // object;
     
     Size size;
};
```

It will be something like that:

#### inside OpenCV ####

```
class InputArray
{
      // the only constructor, but the template one and not "explicit"
      template<typename ArrayT> InputArray(const ArrayT& some_array)
      {
           kind = ArrayDescriptor<ArrayT>::kind;
           obj = &some_array;
           customOps = ArrayDescriptor<ArrayT>::getArrayOps();
      }

     int kind;
     void* obj;
     int type;
     Size size;
     ArrayOperations* customOps; // new member
};

// for arbitrary type we don't provide any array information,
// which will make compiler issue an error in the case of completely alien array type.
template<typename T> struct ArrayDescriptor
{
};

// provide instances for popular array types
template<> struct ArrayDescriptor<Mat>
{
     enum { kind = InputArray::MAT };
     static ArrayOperations* getArrayOps() { return 0; }
};

template<typename T> struct ArrayDescriptor<std:vector<Mat> >
{
     enum { kind = InputArray::VECTOR };
     static ArrayOperations* getArrayOps() { return 0; }
};

// the base class for user arrays
class ArrayOperations
{
public:
      virtual ~ArrayOperations() {}
      virtual Mat getMat(void* obj, int idx) = 0;
      virtual Size size(void* obj) = 0;
      ...
};

// somewhere inside OpenCV core
Mat InputArray:getMat(int idx) {
     if (kind == MAT) return *(Mat*)obj;
     if (kind == CUSTOM) { CV_Assert(customOps != 0); return customOps->getMat(obj, idx); }
    ...
}
```

#### outside OpenCV, in user's lib/app ####
```
// ops for your array defined
class CustomArrayOps : public ArrayOperations
{
public:
       .... // implement all the interface methods
       static CustomArrayOps custom_ops; // basically, you need just once instance of this class
};

// and the corresponding traits type
template<> struct ArrayDescriptor<CustomArray>
{
      enum { kind = InputArray::CUSTOM };
      static ArrayOperations* getArrayOps() { return &CustomlArrayOps::custom_ops; } 
};
```
Repository: vscode
Issue: Extensions keeping the extension host busy lead to disconnection
Labels: bug,remote-connection

- VSCode Version: Insiders 2019-07-31
- Local OS Version: Win 7
- Remote OS Version: Ubuntu 18.04 (on VMWare, running locally)
- Remote Extension/Connection Type: SSH

Steps to Reproduce:

1. Connect to a remote host
2. Do some work for a while (or don't!)

This is my variant of microsoft/vscode-remote-release#246.

The remote host in this case is a VM on the same machine, so the network connection is fast and reliable. I frequently get the popup saying remote host has disconnected, reconnecting in 5 seconds. It duly reconnects.

I can dismiss the popup, and carry on working, doing tasks that definitely require talking to the remote host. So it appears that it _thinks_ it's been disconnected, when the connection is still very much alive and well.

It's not consistent, and I haven't worked out a pattern of when it happens. It's definitely bursty though - if I get one disconnection there will often be another a few seconds later.

There are no logs from any source at Trace level that correspond with the "you've been disconnected" popup appearing. There are plenty of logs that appear when it actually establishes a new connection. You can see all the old `sshd` instances still running on the remote host.
Repository: TypeScript
Issue: Add a flag which priorities unknown over any in `any | unknown`
Labels: Suggestion,Awaiting More Feedback

# Suggestion

## 🔍 Search Terms

any vs unknown, any strict, unknown strict, unknown as any, any as unknown in strict

## ✅ Viability 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, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

We have a lot of cases where we'd like to have folks opt-in to `unknown` instead of `any` in the eslib, DOM, DT and modules. We've discussed internally about the idea of a third primitive, but that's tricky because it requires finding a good word to describe that, would break `.d.ts` backwards compatibility and that's quite a fine-grained change.

I propose that we have a flag which lets `unknown` beat `any` in union narrowing, which we class as a part of the stricter than strict category.

Today all the way back to 3.6:

```ts
type A = any | unknown
//   ^? - type A = any
```

A future release
```ts
// @thisCompilerFlag: true

type A = any | unknown
//   ^? - type A = unknown
```

## 📃 Motivating Example

Anywhere where we use `any` but would prefer to offer a way to provide `unknown` instead, for example:

- `JSON.parse`
-  The `fetch` / [`axios`](https://github.com/axios/axios/issues/4141) APIs
- `new Object` / `Object.create`


## 💻 Use Cases

Where the ecosystem breakage for moving from `any` are too big to warrant the move. I think switching out `any | unknown` is a pretty reasonable syntax which doesn't add a new concept to the language. It means anyone can adopt support without having to force updating TypeScript versions.
Repository: pytorch
Issue: Give a better error message when REGISTER_DISPATCH is used in improper context
Labels: module: internals,triaged,module: dispatch

If you accidentally use REGISTER_DISPATCH outside of native/cpu you get this error:

```
bazel-out/k8-fastbuild/bin/aten/src/ATen/UfuncCPUKernel_sub.cpp:192:18: error: expected constructor, destructor, or type conversion before '(' token             
 REGISTER_DISPATCH(sub_stub, &sub_kernel); 
```

This is not very helpful. Would be better to give a better error message in this case.

cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh
Repository: vscode
Issue: Allow option to deprioritize Symbols in Quick Open
Labels: feature-request,quick-open

Issue Type: <b>Feature Request</b>

The fact that Symbols are included in the Quick Open list is cool and I like it a lot, however more often than not, it is not something that I am specifically looking for with Quick Open.

I'd still like Symbols to be listed, but I also want them to be at the bottom of the list. In other words, I'd like to prioritize file names over Symbols.

VS Code version: Code 1.61.0 (ee8c7def80afc00dd6e593ef12f37756d8f504ea, 2021-10-07T18:13:09.652Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No


<!-- generated by issue reporter -->
Repository: pytorch
Issue: tools/amd_build/build_amd.py should fail if any file fails to write
Labels: module: build,module: rocm,triaged

Right now, it seems to suppress the error and keep going. That's bad! If I fail to write out a file, the subsequent build will almost certainly fail.

cc @malfet @seemethere @jeffdaily @sunway513 @jithunnair-amd @ROCmSupport
Repository: node
Issue: Investigate flaky parallel/test-worker-init-failure
Labels: flaky-test,worker

### Version

master

### Platform

osx

### Subsystem

workers

### What steps will reproduce the bug?

https://ci.nodejs.org/job/node-test-commit-osx-arm/nodes=osx11/3107/testReport/junit/(root)/test/parallel_test_worker_init_failure/

### How often does it reproduce? Is there a required condition?

intermittent

### What is the expected behavior?

test passes

### What do you see instead?

test fails

### Additional information

_No response_
Repository: node
Issue: Investigate flaky wpt/test-user-timing test
Labels: flaky-test

### Version

master

### Platform

arm + x64

### Subsystem

wpt

### What steps will reproduce the bug?

Run test wpt/test-user-timing - https://ci.nodejs.org/job/node-test-binary-arm-12+/12718/RUN_SUBSET=2,label=pi2-docker/testReport/(root)/test/wpt_test_user_timing/



### How often does it reproduce? Is there a required condition?

intermittent

### What is the expected behavior?

test passes

### What do you see instead?

test fails

### Additional information

_No response_
Repository: create-react-app
Issue: Docs are outdated about initial App.test.js
Labels: stale,needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

The ["Running Tests" documentation](https://create-react-app.dev/docs/running-tests#testing-components) currently says:

> If you haven’t decided on a testing strategy yet, we recommend that you start with creating basic smoke tests for your components:
> ```
> import React from 'react';
> import ReactDOM from 'react-dom';
> import App from './App';
> 
> it('renders without crashing', () => {
>  const div = document.createElement('div');
>  ReactDOM.render(<App />, div);
> });
> ```
> This test mounts a component and makes sure that it didn’t throw during rendering. Tests like this provide a lot of value with very little effort so they are great as a starting point, and this is the test you will find in src/App.test.js.

This is no longer the case; since https://github.com/facebook/create-react-app/pull/7881 in 2019, the default test is a more comprehensive test that inspects the rendered output:

```
test('renders learn react link', () => {
  render(<App />);
  const linkElement = screen.getByText(/learn react/i);
  expect(linkElement).toBeInTheDocument();
});
```

[I've taken the liberty of removing the rest of the issue template - this is an issue with the docs, so the troubleshooting and reproduction stuff doesn't really apply]
Repository: go
Issue: regexp: support case-insensitive prefix strings
Labels: Performance,NeedsInvestigation

For a pattern like `foo.*bar`, the regexp compiler will extract the string `"foo"` and search for it using `strings.Index` before trying anything else.

I propose that this be extended to the case-insensitive version `(?i)foo.*bar`.

I did a trial implementation just calling `strings.EqualFold` repeatedly, and it is much faster:

```
name                old time/op    new time/op     delta
Match/Easy0i/16-8     2.99ns ± 1%     2.91ns ± 1%    -2.74%  (p=0.008 n=5+5)
Match/Easy0i/32-8      589ns ± 1%       56ns ± 0%   -90.51%  (p=0.008 n=5+5)
Match/Easy0i/1K-8     17.3µs ± 2%      7.5µs ± 5%   -56.52%  (p=0.008 n=5+5)
Match/Easy0i/32K-8     693µs ± 0%      259µs ± 0%   -62.61%  (p=0.008 n=5+5)
Match/Easy0i/1M-8     22.8ms ± 6%      8.4ms ± 1%   -63.28%  (p=0.008 n=5+5)
Match/Easy0i/32M-8     714ms ± 1%      269ms ± 0%   -62.32%  (p=0.008 n=5+5)

name                old speed      new speed       delta
Match/Easy0i/16-8   5.35GB/s ± 1%   5.50GB/s ± 1%    +2.82%  (p=0.008 n=5+5)
Match/Easy0i/32-8   54.3MB/s ± 1%  572.6MB/s ± 0%  +954.04%  (p=0.008 n=5+5)
Match/Easy0i/1K-8   59.1MB/s ± 2%  135.9MB/s ± 5%  +130.11%  (p=0.008 n=5+5)
Match/Easy0i/32K-8  47.3MB/s ± 0%  126.5MB/s ± 0%  +167.44%  (p=0.008 n=5+5)
Match/Easy0i/1M-8   46.0MB/s ± 6%  125.0MB/s ± 1%  +171.98%  (p=0.008 n=5+5)
Match/Easy0i/32M-8  47.0MB/s ± 1%  124.8MB/s ± 0%  +165.39%  (p=0.008 n=5+5)
```
Repository: transformers
Issue: [performance/precision] adding `jit.script` to activation functions
Labels: WIP

# 🚀 Feature request

### Switch our activation functions to use `@torch.jit.script`

Over at BigScience we have been trying to figure out mismatches between Megatron-LM and HF Transformers when it comes to inference under fp16. There are several mismatches, this one discusses activation functions. And proposes to improve HF's models based on that.

So Megatron uses `@torch.jit.script` for its activation functions, which leads to 2 things:

1. faster performance
2. more correct math under fp16 or amp/fp16. Quoting @ngimel:

> ... that’s due to fusion. Fuser does intermediate operations in fp32, and thus produces more accurate results than simple function that truncates each intermediate to half.

(I need to double check on amp/fp16 - I'm making an assumption here)

So perhaps we should switch our activation functions to use `@torch.jit.script` too?

Caveats: 

1. it appears that when using `@torch.jit.script` one may have to write out the `bwd` part explicitly, see:

https://github.com/NVIDIA/Megatron-LM/blob/b31e1296354e979722627a6c4dedafe19b51fa97/megatron/model/fused_bias_gelu.py#L27-L56

2. This will change the results slightly (back-compat OK?) but it should produce more correct results!

You can see how the 2 functions diverge:

```
import torch
import random

seed = 42
random.seed(seed)    # python RNG
torch.manual_seed(seed)          # cpu + cuda
torch.cuda.manual_seed_all(seed) # multi-gpu
torch.backends.cudnn.enabled = True

width = 128
input = torch.rand((1,5,width*4)).cuda().half()

@torch.jit.script
def gelu_megatron_fwd_jit(x):
    return  x * 0.5 * (1.0 + torch.tanh(0.79788456 * x * (1 + 0.044715 * x * x)))

def gelu_megatron_fwd(x):
    return  x * 0.5 * (1.0 + torch.tanh(0.79788456 * x * (1 + 0.044715 * x * x)))
    
output = gelu_megatron_fwd(input)
output_jit = gelu_megatron_fwd_jit(input)
# have to run 2nd time for jit to kick in!
output_jit = gelu_megatron_fwd_jit(input)

torch.testing.assert_equal(output, output_jit, check_stride=False)    
```

gives:

```
AssertionError: Tensors are not equal!

Mismatched elements: 800 / 2560 (31.2%)
Greatest absolute difference: 0.00048828125 at (0, 0, 1)
Greatest relative difference: 0.0009828009828009828 at (0, 0, 2)
```

@patrickvonplaten, @patil-suraj, @sgugger, @LysandreJik
Repository: create-react-app
Issue: eslint-config-react-app is not compatible with ESLint 8
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

```
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/rules/no-unused-expressions' is not defined by "exports" in /xxx/node_modules/eslint/package.json
    at throwExportsNotFound (internal/modules/esm/resolve.js:290:9)
    at packageExportsResolve (internal/modules/esm/resolve.js:513:3)
    at resolveExports (internal/modules/cjs/loader.js:437:36)
    at Function.Module._findPath (internal/modules/cjs/loader.js:477:31)
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:872:27)
    at Function.Module._load (internal/modules/cjs/loader.js:730:27)
    at Module.require (internal/modules/cjs/loader.js:957:19)
    at require (/xxx/node_modules/v8-compile-cache/v8-compile-cache.js:161:20)
    at Object.<anonymous> (/xxx/node_modules/eslint-plugin-flowtype/dist/rules/noUnusedExpressions.js:8:51)
    at Module._compile (/xxx/node_modules/v8-compile-cache/v8-compile-cache.js:194:30)
```

Looks like `eslint-plugin-flowtype/dist/rules/noUnusedExpressions.js` imports file that's not exported explicitly.

### Environment

Eslint 8.0.0
eslint-plugin-flowtype: 6.1.0
eslint-config-react-app: 6.0.0

### Expected behavior

No errors

### Actual behavior

Error from the above

### Reproducible demo

Clone https://github.com/ringcentral/ringcentral-javascript/tree/eslint8 (branch eslint8)

```bash
yarn install
yarn test
```
Repository: flutter
Issue: Make upgrading easier
Labels: c: new feature,tool,c: proposal,P3,team-tool,triaged-tool

When upgrading to a new version of android it can be difficult and complex. Particularly if you are no longer familiar with the project.
The android directory has 45 files and 37 directories. The ios directory has 42 files and 13 directories.

I would typically check these entire directories into git, and then when a new version of android comes out it can get quite difficult.
You can delete those directories and then do <code>flutter create .</code>
But then you have to find and merge the files within those directories which changed. Many of the files will have changed during the version bump and you have to try to figure out which of the few files (probably AndroidManifest.xml) which have changed.

It might be easier if there was a separate (maybe .android & .ios) directory where all of these files are stored. Then the android and ios directories would only contain the specific files you have changed (but in the correct location in the directory tree). Then, during build those changed files could be copied into the .android and .ios directories for building.
That way you can safely check in the android and ios directories and they will be sparse with just a couple of changed files. Then, when a new version of ios or android comes out you could just delete the .android and .ios directories and it should work right away.

The .android / .ios directories could even be uncompressed zip files with the complete version number attached, allowing swapping different versions of android in/out at will.
Repository: neovim
Issue: defaults: less surprising default value for `'comments'`
Labels: enhancement,defaults,needs:discussion

### Feature already in Vim?

No

### Feature description

Nvim has `j` in `'formatoptions'` by default, but has the same default value for `'comments'` as Vim. This leads to surprising default behavior of `J` in files without a filetype, as mentioned in #6085, #8841, #8655, #11599, #16016, #19729, #20802, #25382. A less surprising default value for `'comments'` will avoid this, and many runtime `ftplugin`s already set `'comments'` to a different local value.