sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: remap-path-prefix from 1.47.0 results in weird prefixes in backtraces
Labels: P-medium,T-compiler,regression-from-stable-to-stable,C-bug,A-reproducibility

I tried this code:

```rust
#![feature(backtrace)]

fn main() {
    futures::executor::block_on(async move {
        println!("{}", std::backtrace::Backtrace::capture());
        panic!()
    });
}
```

with the environment variables:

```sh
RUSTFLAGS='--remap-path-prefix=/home/nemo157/.cargo/registry/src/github.com-1ecc6299db9ec823=crates.io'
RUST_BACKTRACE=1
RUSTC_BOOTSTRAP=1
```

On 1.46 (and earlier) this results in backtraces looking as expected (for both the `Backtrace::capture` and `begin_panic`):

```
   5: std::thread::local::LocalKey<T>::with
             at /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libstd/thread/local.rs:239
   6: futures_executor::local_pool::run_executor
             at crates.io/futures-executor-0.3.7/src/local_pool.rs:83
   7: futures_executor::local_pool::block_on
             at crates.io/futures-executor-0.3.7/src/local_pool.rs:317
   8: foo::main
             at src/main.rs:4
```

but on 1.47 and later there is a spurious `./` prefixed onto the remapped paths:

```
   6: std::thread::local::LocalKey<T>::with
             at /rustc/18bf6b4f01a6feaf7259ba7cdae58031af1b7b39/library/std/src/thread/local.rs:241
   7: futures_executor::local_pool::run_executor
             at ./crates.io/futures-executor-0.3.7/src/local_pool.rs:83
   8: futures_executor::local_pool::block_on
             at ./crates.io/futures-executor-0.3.7/src/local_pool.rs:317
   9: foo::main
             at ./src/main.rs:4
```

If there are remapped frames on top of each other this seems to become even more complex, in another project using this set of flags:

```toml
rustflags = [
  "--remap-path-prefix=/home/nemo157=~",
  "--remap-path-prefix=/home/nemo157/.cargo=cargo",
  "--remap-path-prefix=/home/nemo157/.cargo/registry/src/github.com-1ecc6299db9ec823=crates.io",
  "--remap-path-prefix=/home/nemo157/.rustup=rustup",
]
```

I got a backtrace like this:

```
   8: clap::app::App::get_matches_from
             at crates.io/clap-2.33.3/crates.io/clap-2.33.3/src/app/mod.rs:1519:9
   9: clap::app::App::get_matches
             at crates.io/clap-2.33.3/crates.io/clap-2.33.3/src/app/mod.rs:1460:9
  10: structopt::StructOpt::from_args
             at ~/sources/bs58-rs/crates.io/structopt-0.3.18/src/lib.rs:1089:26
  11: <bs58::Args as paw_raw::ParseArgs>::parse_args
             at ~/sources/bs58-rs/cli/src/main.rs:69:17
  12: bs58::main
             at ~/sources/bs58-rs/cli/src/main.rs:83:1
```

Frames 8 and 9 include duplicate `crates.io/clap-2.33.3` prefixes, and frame 10 randomly has a `~/sources/bs58-rs` prefix
Repository: ant-design
Issue: mentions 使用onchange的情况下输入 @ 符号在删除之前的@符号会弹出无数据 
Labels: 🐛 Bug,help wanted,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[https://codepen.io/mraiguo/pen/NWrXmRj?editors=0010](https://codepen.io/mraiguo/pen/NWrXmRj?editors=0010)

### Steps to reproduce
输入@符号在退格键删除@符号
[![B3oPSg.png](https://s1.ax1x.com/2020/10/28/B3oPSg.png)](https://imgchr.com/i/B3oPSg)

### What is expected?
不出现 no data 框

### What is actually happening?
出现 no data 框

| Environment | Info |
|---|---|
| antd | undefined |
| React | react16 |
| System | win10 |
| Browser | chrome |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: svelte
Issue: Handling of @html in textarea tags
Labels: stale-bot,temp-stale

**Describe the bug**
Svelte compiler fails to handle {@html} inside `<textarea>` tags

**Logs**
No output in browser console. Compiler throws error `Unexpected character '@' (7:11)`

**To Reproduce**
https://svelte.dev/repl/001f72ee82ac4115920eaf086d785584

**Expected behavior**
The compiler compiles the code successfully, the output `<textarea>` contains the child HTML elements in the string.

**Stacktraces**
N/A

**Information about your Svelte project:**
- Your browser and the version: Firefox 82, Chrome 86 (doesn't matter)

- Your operating system: Windows 10 (doesn't matter)

- Svelte version: 3.29.4

- Whether your project uses Webpack or Rollup: None, as I used Snowpack in dev mode.

**Severity**
Low. I was able to use `<div>` instead for my use case.

**Additional context**
I was trying to integrate TinyMCE editor into my Svelte app. On the surface, TinyMCE uses <textarea> and the content to be edited must be children of that `<textarea>`. But upon reading through their docs (it's a bit unclear) turns out `<div>` can be used too, so that's my solution for the time being.
Repository: node
Issue: Link modules with paths in module.link(linker)
Labels: esm

https://nodejs.org/api/vm.html#vm_module_link_linker

Now we can only link "standard" modules with functions combined with SyntheticModules, like this:

```
await module.link( function( spec ) {
	
    return new Promise( async function( resolve, reject ) {
	
	const mod = await import( spec );
        resolve( new vm.SyntheticModule( [ 'default' ], function() {

            this.setExport( 'default', mod.default );
        }, { context } ) );
    } )
} );
```
Repository: node
Issue: fs.stat() and fs.lstat() cannot read the stats of a file with denied permissions on Windows
Labels: fs,windows

<!--
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.5.0
* **Platform**: Win10 x64
* **Subsystem**: fs

### What is the expected behavior?

A similar issue https://github.com/nodejs/node/issues/22577 has been closed 2 years ago, but the issue hasn't been fixed.

Node.js cannot read the `stats` of immutable files (files with all permissions denied) on Windows. I'm not talking about the contents, just the stats. 

Example:

After you deny all permissions to a file (to protect it from being deleted or modified), the default Windows File Explorer can still read the file's stats (name, size, etc) but Node.js throws `EPERM: operation not permitted, lstat`:
```
> icacls E:\test.txt /deny *S-1-1-0:(F)
```
This command effectively denies all modification permissions (delete, rename, write) for Everyone (`*S-1-1-0`).

### What do you see instead?

#### Windows 10:

```
> icacls E:\test.txt /deny *S-1-1-0:(D)
> node
> fs.lstatSync('E:\\test.txt')
Uncaught Error: EPERM: operation not permitted, lstat 'E:/test.txt'
    at Object.lstatSync (fs.js:1033:3) {
  errno: -4048,
  syscall: 'lstat',
  code: 'EPERM',
  path: 'E:/test.txt'
}
```

#### Linux ubuntu 20.01:

```
> sudo chattr +i /home/user/Desktop/test.txt
> node
> fs.lstatSync('/home/user/Desktop/test.txt')
Stats {
  dev: 2053,
  mode: 33206,
  nlink: 1,
  uid: 1000,
  gid: 1000,
  rdev: 0,
  blksize: 4096,
  ino: 263860,
  size: 39881,
  blocks: 80,
  atimeMs: 1603884853571.3228,
  mtimeMs: 1602542159686.156,
  ctimeMs: 1603894615058.1975,
  birthtimeMs: 1603842167648.6978,
  atime: 2020-10-28T11:34:13.571Z,
  mtime: 2020-10-12T22:35:59.686Z,
  ctime: 2020-10-28T14:16:55.058Z,
  birthtime: 2020-10-27T23:42:47.649Z 
}
```

#### MacOS:

Haven't tested
Repository: PowerToys
Issue: [Run] Have search ignore file types
Labels: Idea-Enhancement,Help Wanted,Product-PowerToys Run

## 📝 Provide a description of the new feature

_What is the expected behavior of the proposed feature?  What is the scenario this would be used?_

Option to ignore files using a file called `.ptrunignore` (in the user directory) that works just like `.gitignore` and `.dockerignore` (supports Regular Expression) but it works systemwide

## Why?

I (and many others ) would like to have these kinds of results not show up in PT Run:

![PT Run search results that displays useless binaries](https://user-images.githubusercontent.com/67918878/97451250-948d3d00-1959-11eb-855b-e8084e527a90.png)

If this feature gets implemented, I could add `*.pyc` to `.ptrunignore` and results with the `.pyc` extension would not show up in PT run search results.

<hr>
If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: go
Issue: x/tools/gopls: use a per-process shared temp directory
Labels: gopls,Tools

gopls can generate a fairly wide-range of temp files and directories (logs, heap dumps, temp modfiles, gc details data, and now temp workspace directories).

We should consolidate these into a top-level temp directory for the gopls process, both so that they are co-located, and so that we can have a catch-all clean up pass when the gopls process exits.
Repository: create-react-app
Issue: Proposal: Revert override of jest default `resetMocks`
Labels: issue: proposal,needs triage

## About

Hey what's up!

I found myself trying to work out why all my tests broke when upgrading react-scripts and then realized it's because of the change to enabling `resetMocks` by default.

I wanted to challenge this decision because, especially when react-scripts is targeted at newer users looking to use react, this causes [fundamental jest examples online](https://jestjs.io/docs/en/jest-object#jestcreatemockfrommodulemodulename) to break.

## App-wide mocks

It also means app-wide mocks such as these don't work.

```js
// some-mocked-module.js
export const useSomeHook = jest.fn(() => true);
```

```js
// setupTests.js
jest.mock('some-mocked-module', () => ({
  useSomeHook: jest.fn(() => true)
}))
```

For new users, I can see why it would be very confusing.
Repository: rust
Issue: cannot use #![deny(missing_docs)] with external derive macro
Labels: A-lints,T-compiler,C-bug

<!--
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 ([graphql_client v0.9](https://docs.rs/graphql_client/0.9.0/src/graphql_client/lib.rs.html#67-75))

```rust
use graphql_client::*;

#[derive(GraphQLQuery)]
#[graphql(
    query_path = "src/query/schema/get.graphql",
    schema_path = "schema.graphql",
    response_derives = "PartialEq, Debug, Serialize, Deserialize",
    deprecated = "warn"
)]
/// Documentation for this struct
pub struct GetSchemaQuery;
```

I expected to see a successful build.

Instead, the build failed and complained about missing docs for a struct that originated in a derive macro.

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Full build output</summary>
<p>

```console
$ RUST_BACKTRACE=1 cargo build --package rover-client
   Compiling rover-client v0.0.0 (/home/avery/Documents/work/rover/crates/rover-client)
error: missing documentation for a module
 --> crates/rover-client/src/query/schema/get.rs:9:10
  |
9 | #[derive(GraphQLQuery)]
  |          ^^^^^^^^^^^^
  |
note: the lint level is defined here
 --> crates/rover-client/src/lib.rs:1:9
  |
1 | #![deny(missing_docs)]
  |         ^^^^^^^^^^^^
  = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: missing documentation for a constant
 --> crates/rover-client/src/query/schema/get.rs:9:10
  |
9 | #[derive(GraphQLQuery)]
  |          ^^^^^^^^^^^^
  |
  = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: missing documentation for a struct
 --> crates/rover-client/src/query/schema/get.rs:9:10
  |
9 | #[derive(GraphQLQuery)]
  |          ^^^^^^^^^^^^
  |
  = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: missing documentation for a struct field
 --> crates/rover-client/src/query/schema/get.rs:9:10
  |
9 | #[derive(GraphQLQuery)]
  |          ^^^^^^^^^^^^
  |
  = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 4 previous errors

error: could not compile `rover-client`.

To learn more, run the command again with --verbose.
```

</p>
</details>
Repository: create-react-app
Issue: public directory css url
Labels: needs triage,issue: bug report

### Describe the bug

When trying to import a image using the url method in a css/sass file the path no longer resolves to include the public directory using the prefix `/`

### Did you try recovering your dependencies?

Yes

### Which terms did you search for in User Guide?

### Environment

```
  current version of create-react-app: 4.0.0
  running from /Users/jfay/.npm/_npx/12069/lib/node_modules/create-react-app

  System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 12.18.3 - /usr/local/bin/node
    Yarn: 1.21.1 - /usr/local/bin/yarn
    npm: 6.14.6 - /usr/local/bin/npm
  Browsers:
    Chrome: 86.0.4240.75
    Edge: Not Found
    Firefox: 80.0
    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. Start with a generic cra w/ react-scripts@4.0.0 
2. Open App.css
3. Set the background to use an image resolved to the public url

```css
.App {
  text-align: center;
  background-image: url("/logo192.png");
}
```

### Expected behavior

Prior to upgrading to react-scripts@latest version 3.4.3 resolved images referenced in css files to include the public directory. 

### Actual behavior

<img width="731" alt="Screen Shot 2020-10-28 at 12 33 07 PM" src="https://user-images.githubusercontent.com/46365891/97466660-bcf54700-1919-11eb-934a-700d21263860.png">
Repository: pytorch
Issue: max_pool2d always fails on native Android app
Labels: oncall: mobile

## 🐛 Bug

The C++ TorchScript always crashes on Android when trying to execute `torch.max_poo2d`. This was found using the operation as part of a bigger model, but also the error was reproduced with and simple model containing the operation only.

Simple model to reproduce the error:

```
class DummyMaxpooler(nn.Module):
    def __init__(self):
        super(DummyMaxpooler, self).__init__()

    def forward(self, x: Tensor, k: int, s: int):
        return torch.max_pool2d(x, kernel_size=k, padding=k // 2, stride=s)
```

Input creation on C++:

```
    torch::Tensor tensor_example = torch::rand({1, 320, 320});
    std::vector<torch::jit::IValue> inputs;
    inputs.emplace_back(tensor_example);
    inputs.emplace_back(2);
    inputs.emplace_back(3);
    auto result = m_module.forward(inputs);
```

Error traceback:

```
libc++abi: terminating with uncaught exception of type std::runtime_error: The following operation failed in the TorchScript interpreter.
    Traceback of TorchScript, serialized code (most recent call last):
      File "code/__torch__.py", line 10, in forward
        s: int) -> Tensor:
        _0 = torch.floordiv(k, 2)
        _1 = torch.max_pool2d(x, [k, k], [s, s], [_0, _0], [1, 1], False)
             ~~~~~~~~~~~~~~~~ <--- HERE
        return _1
    
    Traceback of TorchScript, original code (most recent call last):
      File "/.../dummy_maxpooler.py", line 13, in forward
        def forward(self, x: Tensor, k: int, s: int):
            return torch.max_pool2d(x, kernel_size=k, padding=k // 2, stride=s)
                   ~~~~~~~~~~~~~~~~ <--- HERE
    RuntimeError: Dimension out of range (expected to be in range of [-3, 2], but got 3)
```

## Environment

 - PyTorch Version: 1.6.0
 - OS: Android
 - How you installed PyTorch: dependency pulled from 'org.pytorch:pytorch_android:1.6.0-SNAPSHOT', as detailed in: https://pytorch.org/tutorials/recipes/android_native_app_with_custom_op.html#making-android-application
 - Any other relevant information:  libtorch 1.6.0 was also build from source using the script `scripts/build_pytorch_android.sh` with the exact same result
Repository: create-react-app
Issue: fixed start bug
Labels: stale,needs triage,issue: bug report

![image](https://user-images.githubusercontent.com/53595007/97471485-be5b5980-1983-11eb-9a36-0c66a11f78a0.png)

npx create-react-app my-app
cd my-app
npm start
this about error show！
**change node_nodules/react-refresh/cjs/react-refresh-runtime.development.js line465 "renderers" to "_listeners.renderer",then the error fixed!******
Repository: pytorch
Issue: torch.sum(tensor(2.), dim=0) (and probably other reduction functions) doesn't make sense
Labels: module: docs,triaged,module: reductions

## 🐛 Bug

torch.sum allows passing in a scalar tensor with dim=0. However, the scalar tensor has no dimensions, so asking to reduce over dimension 0 doesn't make sense.

## To Reproduce

Steps to reproduce the behavior:

```
>>> torch.sum(torch.tensor(2.), dim=0)
tensor(2.)
```
This also happens for F.softmax and probably other reduction functions.

## Expected behavior

This should probably error out or we should update our documentation

## Environment
master

cc @jlin27 @mruberry
Repository: flutter
Issue: Add support for host architecture detection of arm64 on Windows desktop
Labels: c: new feature,tool,platform-windows,a: desktop,P3,team-windows,triaged-windows

This is currently support on macOS via OperatingSystemUtils, a similar addition to the HostArchitecture enum and implementations for Linux and windows.

API: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/base/os.dart#L123

Example macOS implementation: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/base/os.dart#L302
Repository: electron
Issue: [macOS] application menu items are not localized on non-English macOS 
Labels: platform/macOS,bug :beetle:,status/confirmed,10-x-y

<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:**
  * <!-- (output of `node_modules/.bin/electron --version`) e.g. 4.0.3 --> 10.1.5
* **Operating System:**
  * <!-- (Platform and Version) e.g. macOS 10.13.6 / Windows 10 (1803) / Ubuntu 18.04 x64 --> macOS Catalina 10.15.7
* **Last Known Working Electron version:**
  * <!-- (if applicable) e.g. 3.1.0 --> Not sure

### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
All the application menu labels should match the language of the OS

### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
Some of the labels are in English and some of them match the OS language

### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide an example.
-->

<!--
For bugs that can be encapsulated in a small experiment, you can use Electron Fiddle (https://github.com/electron/fiddle) to publish your example to a GitHub Gist and link it your bug report.
-->

<!--
If Fiddle is insufficient to produce an example, please provide an example REPOSITORY that can be cloned and run. You can fork electron-quick-start (https://github.com/electron/electron-quick-start) and include a link to the branch with your changes.
-->

* Set the primary language of the OS to a non-English language (I used French)

```sh
$ git clone https://github.com/electron/electron-quick-start
$ npm install
$ npm start || electron .
```
* Look at the application menu

### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
<img width="1020" alt="locale1" src="https://user-images.githubusercontent.com/42934634/97473083-3cebd300-1953-11eb-8c37-9624c148112a.png">
<img width="1020" alt="locale2" src="https://user-images.githubusercontent.com/42934634/97473090-3fe6c380-1953-11eb-8ccc-22aec3afc73c.png">

### Additional Information
<!-- Add any other context about the problem here. -->
Google Chrome's menu is properly localized
Repository: flutter
Issue: Update Windows build rules to consider the arm64 target platform
Labels: c: new feature,tool,platform-windows,a: desktop,P3,team-windows,triaged-windows

Currently these build rules hard-code an x64 target platform, but they should be configured to both provide and accept this target platform and use it to select the correct compilation artifacts. Even without uploaded artifacts, this should be sufficient to build with a local engine.

macOS build rules will be different and do not need to be adjusted.

- [x] linux
- [ ] windows
Repository: flutter
Issue: Add target platform and sysroot flags to flutter build linux, windows
Labels: c: new feature,tool,a: desktop,P3,team-tool,triaged-tool

This would simply pass through the target platform configuration once the rules support it.

By default, this should select the architecture of the current host platform, and if a different platform is provided should complain if there is also no sysroot.

This can be supported before artifacts are uploaded via loca-engine builds.
Repository: flutter
Issue: Update cache.dart to download prebuilt windows binaries when available for ARM64
Labels: c: new feature,tool,platform-windows,a: desktop,P3,team-windows,triaged-windows

This would allow flutter build linux/windows to work without a local engine