sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Moving a gltf file with separate bin file within the editor doesn't move the bin file
Labels: bug,topic:import

**Godot version:**
3.2.3 stable


**OS/device including version:**
Windows 10


**Issue description:**
I got a gltf file from my artist that had a separate bin file and texture. After importing I decided to move the files to another directory, but the editor doesn't move the bin file with the gtlf file which broke the model.


**Steps to reproduce:**
1. Open the attached project
2. Open suzanne.tscn
3. Note that Suzanne is in the scene
4. Close the scene
5. Use the FileSystem tab to move suzanne.gltf into the empty folder
6. Open suzanne.tscn again
7. Note that Suzanne doesn't show
8. In Windows Explorer you'll see the bin file didn't move with the gltf file, breaking the link between the two


**Minimal reproduction project:**
[Bin file bug.zip](https://github.com/godotengine/godot/files/5431628/Bin.file.bug.zip)
Repository: create-react-app
Issue: [v4] What else has been changed in testing ?
Labels: stale,needs triage

I upgraded `react-scripts` in my project from version `3.4.x` to `4.0.0` and testing isn't like before.

I read the changelog, you said that you've upgraded to Jest 26 and now set `resetMocks` to `true` by default in the Jest config! (hmm, this isn't expected), so, I added:

    "resetMocks": false,

to make my tests work again. I fixed some other new `Eslint` warning (and that's okay)...
**BUT,** Now it **covers only a part of the test suits!**
I have 420 tests (551 suites) in the project,

    "test": "react-scripts test --coverage --watchAll=true",

runs only  118 (25 suites)!

Thanks!
Repository: pytorch
Issue: Clearer error messages for 'different devices' error in the RNN module
Labels: triaged,better-engineering

Hello,
I have been working with PyTorch's RNN module and I came across some vague error messages.

## Problem Description
Here is a snippet of the code I'm working on : 
```python
def forward(self, sent_tuple):
    sent, sent_len = sent_tuple
    sent_packed = nn.utils.rnn.pack_padded_sequence(sent, sent_len)
    sent_output = self.enc_lstm(sent_packed)[0]  # seqlen x batch x 2*nhid
    sent_output = nn.utils.rnn.pad_packed_sequence(sent_output)[0]
```
```python
model.cuda()
tensor = torch.from_numpy(embed).float()
seq_len = torch.from_numpy(np.array([embed.shape[0]])).long()
out_embed = infersent_model((embed, seq_len))
```
An error was produced because the model and the batch data were on different devices (GPU and CPU, respectively). Here is the error trace : 
```bash
Traceback (most recent call last):
  File "test.py", line 140, in <module>
    test(args.text_path, args.model_version, args.model_path, args.w2v_path, args.network_pkl, args.truncation_psi, exp_dir)
  File "test.py", line 110, in test
    out_embed = infersent_model((embed, seq_len))
  File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/graduation-project/personal-work/portrait-synthesis-from-speech/text-to-face-generation/infersent.py", line 33, in forward
    sent_output = self.enc_lstm(sent_packed)[0]  # seqlen x batch x 2*nhid
  File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/module.py", line 722, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/torch/nn/modules/rnn.py", line 580, in forward
    self.num_layers, self.dropout, self.training, self.bidirectional)
RuntimeError: Expected !pre_compute_input to be true, but got false.  (Could this error message be improved?  If so, please report an enhancement request to PyTorch.)
```

## Solution
This was solved by moving the batch data to GPU : 
```python
model.cuda()
tensor = torch.from_numpy(embed).float().cuda()
seq_len = torch.from_numpy(np.array([embed.shape[0]])).long().cuda()
out_embed = model((embed, seq_len))
```

## Improvements
I think this error message is somehow confusing : 
```bash
RuntimeError: Expected !pre_compute_input to be true, but got false.
```
So, 
- First, If the problem is with devices, why is this error message different from others, like `expected device cuda`, for instance?
- Second, If that's the case, I think there might be a more specific error message to the different devices problem in RNN module rather than using a generic message in `TORCH_CHECK_WITH_MSG`.
Repository: rust
Issue: Excessive memory usage building GTK Rust, a problem for entry level devices for newcomers (e.g. Raspberry Pi 3+)
Labels: C-enhancement,T-compiler,I-compilemem

I tried to build this [Rust project, an on-screen keyboard](https://source.puri.sm/Librem5/squeekboard) directly [on-device on a PinePhone](https://www.pine64.org/pinephone/):

```bash
$ git clone https://source.puri.sm/Librem5/squeekboard
$ cd squeekboard
$ mkdir _build
$ meson _build/
$ cd _build
$ ninja
```
*(install of some dependencies will likely be required before it runs through, it tells you which as you go)*

I expected to see this happen: it works

Instead, this happened: it runs out of memory once it builds GTK for Rust:

![oom](https://user-images.githubusercontent.com/64124388/97055244-f0c91900-1575-11eb-8539-b7670b0f8717.png)

This device has 2GB in total in memory as you can see. Now before you point out that may not be the typical developer device, the Raspberry PI also commonly has around that range in memory and is a common entry level device for tinkerers and new want-to-be programmers that try out their first steps. Please also note that some people from less fortunate backgrounds *may not be able to afford a pricier device.* Also, mobile phones used on the run for quick tasks, which might involve rebuilding an app locally as I tried here, are increasingly becoming more common. For all programming languages other than Rust that I've ever tried, this is not an issue: compilation may take long, maybe hours even for larger projects, but at least for regular desktop level applications outside of giants like browsers, or entire compiler toolchains themselves, it usually works, even if only with lots of patience. For Rust however, this doesn't seem to be currently the case.

I reported the issue to GTK for Rust which is the component that makes rustc run out of memory when compiled, where it was pointed out this is likely something that needs to be addressed in the compiler: https://github.com/gtk-rs/gtk/issues/1074

Since this seems like a potentially major accessibility barrier for newcomers and people stuck with less powerful devices to get into the Rust world, I suggest that this situation should be improved.

**Please note I am not objecting to this memory usage in environments where it is available, if that speeds up compilation (for caching etc).** However, it shouldn't be a required amount to be able to build any basic graphical GTK application *at all*.

### Meta
`rustc --version --verbose`:
```
$ rustc --version --verbose
rustc 1.44.0
binary: rustc
commit-hash: unknown
commit-date: unknown
host: aarch64-alpine-linux-musl
release: 1.44.0
LLVM version: 10.0
```
(this is the compiler directly on the 2GB device, a PinePhone.)
Repository: go
Issue: x/build: add builder to test ios/amd64 port
Labels: Builders,NeedsInvestigation,new-builder

If it is possible to create a builder for the ios/amd64 target (iOS Simulator, see #42100) with a reasonable amount of effort, we should create it. This is the tracking issue for any investigation and work that goes into this.

CC @golang/release, @cherrymui, @eliasnaur.
Repository: node
Issue: V8 coverage API next steps
Labels: coverage

Opening an issue to track the work before moving v8.startCoverage() and v8.stopCoverage() out of experiment. This will take some refactoring. See https://github.com/nodejs/node/pull/33807#issuecomment-643314073 and https://github.com/nodejs/node/pull/33807#issuecomment-693162916

> 1. Add a v8.startCoverage() method to reuse the per-env connection, if NODE_V8_COVERAGE is not set (would be useful to restart after v8.stopCoverage())
> 2. It would be good to have an API that (optionally?) returns the coverage result. I think it should be v8.takeCoverage() as the Profiler.stopPreciseCoverage command doesn't return this but the Profiler.takePreciseCoverage does. Also, I realize that this method should be asynchronous as there's no guarantee that we can get the response from inspector synchronously (it just happens to be this way right now), so it should probably return a promise.
> 3. Error reporting can be improved (return a rejection?)

Also https://github.com/nodejs/node/issues/35212
Repository: flutter
Issue: [google_maps_flutter] Bug rendering when not using maps full screen
Labels: a: platform-views,p: maps,package,team-ecosystem,has reproducible steps,P2,found in release: 3.7,found in release: 3.8,triaged-ecosystem

<!-- 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 out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Steps to Reproduce

<!-- You must include full steps to reproduce so that we can reproduce the problem. -->

1. Run `flutter create bug`.
2. Add google_maps_flutter 1.0.3 as a dependency.
3. Show `GoogleMap` widget using part of screen.
4. Show a widget (e.g `Container` with white background above widget.

**Actual results:** <!-- what did you see? -->

This is how I am showing the map:
![IMG_9AA8721E3B3B-1](https://user-images.githubusercontent.com/9013995/97063748-dabc5800-1577-11eb-94e3-f5e1a625da36.jpeg)

This is what happens if a widget is above the map:
![Untitled](https://user-images.githubusercontent.com/9013995/97063859-849be480-1578-11eb-96d4-080927b74aec.png)
(those lines does not appear when taking a screenshot, thus I needed to take a picture of this)


Should I use another way of displaying a static map?

<details>
  <summary>Logs</summary>

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
[✓] Flutter (Channel stable, 1.22.2, on Mac OS X 10.15.7 19H2, locale en-BR)
    • Flutter version 1.22.2 at /Users/marcoskobuchi/flutter
    • Framework revision 84f3d28555 (8 days ago), 2020-10-15 16:26:19 -0700
    • Engine revision b8752bbfff
    • Dart version 2.10.2

 
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/marcoskobuchi/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/marcoskobuchi/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.9.3

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
```

</details>
Repository: react
Issue: Bug: Input leaks fiber nodes in recent versions of chromium
Labels: Type: Needs Investigation

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: ^16.13.1

## Steps To Reproduce

1. Mount an input component
2. Type anything
3. Unmount input component

Small code sample:

```
const InputWrapper = () => {
  const Siblings = React.useMemo(() => new Array(1000).fill(1).map((_,i) => <div key={i}/>), []);
  return (
    <div>
      <input />
      {Siblings}
    </div>
  );
};
export const Demo = () => {
  const [show, setShow] = React.useState(false);

  const handleShow = React.useCallback(() => {
    setShow((prev) => !prev);
  }, []);

  const closeRef = React.useRef<number>(0);
  
  const handleShowMany = React.useCallback(() => {
    closeRef.current = 0;
    const id = setInterval(() => {
      setShow(prev => !prev);
      if (closeRef.current++ > 10000) {
        clearInterval(id);
      }
    }, 1);
  }, [setShow])

  return (
    <div>
      <button onClick={handleShow}>{show ? "hide" : "show"}</button>
      <button onClick={handleShowMany}>{closeRef.current}</button>
      {show && <InputWrapper />}
    </div>
  );
};
``` 

## The current behavior
Currently when mounting the input controller for the first time, a small increase in fiber nodes occurs, and after typing in the input box, seemingly the entire React fiber tree is leaked. When mounting/unmounting the input again, there is no clean up (even after thousands of iterations).

## The expected behavior
The fiber nodes to be cleaned up after unmounting the input element.

Comparison memory+fiber nodes on Chrome 69 vs Chrome 86:

**Chrome 69**:
![image](https://user-images.githubusercontent.com/54151393/97064044-3e368d80-1558-11eb-8676-3ee913542cc5.png)

**Chrome 86**:
![image](https://user-images.githubusercontent.com/54151393/97064051-4db5d680-1558-11eb-834b-04a26f4c507a.png)

**Note the 600kb increase in memory per scenario in Chrome 86, vs the <100KB in Chrome 69, as well as the difference in Fiber nodes**

**The final number of fiber nodes in the Chome 69 snapshot is the same as the initial count of fiber nodes in Chrome 86 after mounting the input element for the first time:**
![image](https://user-images.githubusercontent.com/54151393/97064148-ca48b500-1558-11eb-9b41-ca397b1156a7.png)
Repository: flutter
Issue: `expr: syntax error` on flutter/plugin ci in `incremental_build.sh`
Labels: p: tooling,package,team-ecosystem,P2,triaged-ecosystem

See https://cirrus-ci.com/task/5584991339937792?command=build#L7

For example, in ` build-ipas+drive-examples CHANNEL:master PLUGIN_SHARDING:--shardIndex 0 --shardCount 4`,  Each `incremental_build.sh` command seems to print out an `expr: syntax error` error. It doesn't seem to affect the CI execution for now. It would be nice if we can fix this nonetheless.
Repository: vscode
Issue: Let extensions hook into url opening
Labels: feature-request,api,under-discussion,api-proposal

## Overview
Let extensions hook into url opening. Motivating use case: I click on a link in the integrated terminal and it opens in my [browser preview extension](https://marketplace.visualstudio.com/items?itemName=auchenberg.vscode-browser-preview)

Potential places to handle links:

- Links in the terminal
- Links in documents
- Links from the remote port forwarding views
- Debugger launch?
- Open external?

## Additional requirements

- A url opener should be able to decline opening a link

    Some openers may only support specific types of links, such as `localhost`

- Clicking a link should activate relevant extensions

    We'd need a new activation event  so that extensions can make sure they handle link opening

- Let users fallback to VS Code's default behavior

    This typically is to open using the default browser

- Handle multiple url openers being registered at the same time

    Users should be able to select which opener to use in this case. They should potentially be able to specify a default opener.
Repository: go
Issue: cmd/compile: unneeded panicshift for bounded shift amount
Labels: Performance,NeedsInvestigation,compiler/runtime

Tested on 1.15.3 and tip. 

Foo contains an unnecessary `panicshift` call, whereas Bar does not:

```golang
func Foo(x int) byte {
    if x >= 0 { 
        return byte(1) << (x % 8)
    }
    return 0
}

func Bar(x uint) byte {
    return byte(1) << (x % 8)
}
```

godbolt link: https://godbolt.org/z/qhTqYM
Repository: TypeScript
Issue: watch additional files
Labels: Suggestion,Awaiting More Feedback

## Search Terms

tsc watch yarn.lock

## Suggestion

add the ability to watch files that are not part of the default set

## Use Cases

primary use case for this is to auto restart language server, or a `tsc --watch` if `yarn.lock` changes when using pnp since there is no `node_modules` to watch. currently if a library is removed tsc will actually crash when it goes missing. When a library is added tsc watch needs to be manually restarted.

## Examples

I think these should be additive, not replace the existing paths, however I can see adding a new option for additivity, or requiring this to replace existing options. If it replaces the current watch set then it should be well documented how to specify them. If no arguments are provided the behavior of suggested would be use the defaults.

```tsc --watch yarn.lock```

```
"compilerOptions": {
    "watch": {
      "paths": ["yarn.lock"],
    },
}
```

## 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: flutter
Issue: [flutter_tools] A new flutter update should show version info 
Labels: tool,c: proposal,P3,team-tool,triaged-tool

Continuing from #67532.

## Use case

Running any `flutter` command from a stale install would occasionally display the following message: 
```
  ╔════════════════════════════════════════════════════════════════════════════╗
  ║ A new version of Flutter is available!                                     ║
  ║                                                                            ║
  ║ To update to the latest version, run "flutter upgrade".                    ║
  ╚════════════════════════════════════════════════════════════════════════════╝
```

Since #68866 and #69420 users can check for updates _manually_ by running `flutter upgrade --verify-only`.
<pre>
$ flutter upgrade --verify-only
A new version of Flutter is available on channel &lt;user channel&gt;

<b>The latest revision: &lt;update version&gt;</b>
Your current version: &lt;user installed version&gt;

To upgrade now, run "flutter upgrade".
$
</pre>
Provided that the user is on the `stable` channel, the url for [release notes](https://flutter.dev/docs/development/tools/sdk/release-notes) is also shown.

## Proposal

The freshness check message needs to be updated to include the update version:
<pre>
A new version of Flutter is available!

<b>The latest revision: &lt;update version&gt;</b>
Your current version: &lt;user installed version&gt;

To update to the latest version, run "flutter upgrade".
</pre>

The freshness check uses a cache to [prevent network calls at every flutter command](https://github.com/flutter/flutter/blob/a880c4ed3590477380c975f867406ba336834848/packages/flutter_tools/lib/src/version.dart#L837-L842); in case the tool determines an update from the cache, we can recommend the user to run `flutter upgrade --verify-only` themselves instead of displaying a "stale" latest version from the cache.

<pre>
A new version of Flutter is available!

To update to the latest version, run "flutter upgrade".
To compare versions, run "flutter upgrade --verify-only".
</pre>


cc @christopherfujino
Repository: pytorch
Issue: About 2 minor bug fixes on CUDA macOSX 10.13.6
Labels: module: build,module: cuda,triaged,module: macos,module: nnpack

## 🐛 Bug

During building pytorch 1.7 on macOSX 10.13.6, cuda 10.1(update2), Xcode 10.1(clang 1000.11.45.5), I found the following two bugs and adjusted code accordingly on my local mac. Just update information to you in case that you need to fix as well.

## To Reproduce

Using "MAGMA_HOME="/usr/local/lib/magma-cu101" MACOSX_DEPLOYMENT_TARGET=10.9 CC=clang CXX=clang++ USE_OPENMP=OFF USE_FBGEMM=OFF  python setup.py bdist_wheel" to build pytorch on 1.7 branch

Steps to reproduce the behavior:

1. For issue during building nnpack
```bash
"ModuleNotFoundError: No module named 'peachpy.x86_64.avx’" 
```
1. Error when building ../torch/csrc/jit/codegen/cuda/kernel_cache.cpp

```bash
../torch/csrc/jit/codegen/cuda/kernel_cache.cpp:29:25: error: format specifies type 'long' but the argument has type 'int64_t' (aka 'long long') [-Werror,-Wformat]
        printf("%ld, ", shape_symbol.static_size());
                ~~~     ^~~~~~~~~~~~~~~~~~~~~~~~~~
                %lld
../torch/csrc/jit/codegen/cuda/kernel_cache.cpp:31:28: error: format specifies type 'long' but the argument has type 'int64_t' (aka 'long long') [-Werror,-Wformat]
        printf("s(%ld), ", *reinterpret_cast<const int64_t*>(&shape_symbol));
                  ~~~      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                  %lld
```

## My code changes

1. For issue during building nnpack: have to generate bytecode ahead of time
https://github.com/pytorch/pytorch/blob/master/cmake/External/nnpack.cmake#51, add following codes:
```python
  # Orlando: check if avx bytecode has been generated or not
  if(NOT EXISTS "${CAFFE2_THIRD_PARTY_ROOT}/python-peachpy/peachpy/x86_64/avx.py")
    execute_process(COMMAND python setup.by develop
      WORKING_DIRECTORY "${CAFFE2_THIRD_PARTY_ROOT}/python-peachpy")
  endif()
```

2. Error when building ../torch/csrc/jit/codegen/cuda/kernel_cache.cpp
https://github.com/pytorch/pytorch/blob/master/torch/csrc/jit/codegen/cuda/kernel_cache.cpp#L48
int64_t refers to third_party/eigen/Eigen/src/Core/util/Meta.h

```c
      const auto& shape_symbol = sizes.value()[i];
      if (shape_symbol.is_static()) {
        printf("%lld, ", shape_symbol.static_size());
      } else {
        printf("s(%lld), ", *reinterpret_cast<const int64_t*>(&shape_symbol));
      }
```

## Environment

 - PyTorch Version (e.g., 1.0): 1.7
 - OS (e.g., Linux): macOS 10.13.6
 - How you installed PyTorch (`conda`, `pip`, source): source
 - Build command you used (if compiling from source): MAGMA_HOME="/usr/local/lib/magma-cu101" MACOSX_DEPLOYMENT_TARGET=10.9 CC=clang CXX=clang++ USE_OPENMP=OFF USE_FBGEMM=OFF  python setup.py bdist_wheel
 - Python version: 3.7
 - CUDA/cuDNN version: 10.1update 2, cudnn 7.6.5
 - GPU models and configuration:
 - Any other relevant information:


cc @malfet @seemethere @walterddr @ngimel
Repository: create-react-app
Issue: Expose jest's `slowTestThreshold` option
Labels: issue: proposal,needs triage

Hello CRA, thanks for bringing the new update :)

I often do large integration tests in lieu of unit testing, and as such, test suites that test an entire page often take around 15 seconds.

[Jest 26.2 released a feature](https://github.com/facebook/jest/pull/9366) called `slowTestThreshold` where you could set a threshold for when jest would highlight the run time of your tests as red. [View the docs here](https://jestjs.io/docs/en/configuration#slowtestthreshold-number)

This option is unfortunately not green-lighted by CRA's out of the box jest setup. I would love to have this as an option exposed from CRA's `package.json` 🙏  If this is something that's first-issue-level and I was pointed in the right direction, I could manage making a PR.