sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `x` dropped because it borrows itself + dropping a reference causes an error
Labels: A-diagnostics,T-compiler

<!--
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.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

This file produces a very strange error message on build: https://github.com/Jakobeha/typed-arena-any-vec/blob/weird-issue/src/test.rs

```
error[E0597]: `arena` does not live long enough
  --> typed-arena-any-vec/src/test.rs:30:24
   |
30 |         let mut node = arena.alloc(Node(None, 1, DropTracker(&drop_counter))).unwrap();
   |                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ borrowed value does not live long enough
...
47 |     }
   |     -
   |     |
   |     `arena` dropped here while still borrowed
   |     borrow might be used here, when `arena` is dropped and runs the destructor for type `Arena<Node<'_, '_>, ArrayVec<Node<'_, '_>, 2_usize>>`
```

additionally when I try to drop a reference I get

```
error[E0505]: cannot move out of `node` because it is borrowed
  --> typed-arena-any-vec/src/test.rs:46:14
   |
38 |         let error = arena.alloc(Node(Some(node), 3, DropTracker(&drop_counter))).unwrap_err();
   |                                           ---- borrow of `*node` occurs here
...
46 |         drop(node);
   |              ^^^^ move out of `node` occurs here
47 |     }
   |     - borrow might be used here, when `arena` is dropped and runs the destructor for type `Arena<Node<'_, '_>, ArrayVec<Node<'_, '_>, 2_usize>>`
```

but I dropped the *reference* to node, IntelliJ even warns on line 46 "Dropping a reference does nothing".

This seems like a rustc bug considering dropping the reference causes an error. Although I don't know if my code has any actual "dropped while borrowed" problem.

The issue came up when I implemented `Drop` on `_ArrayVec` which is stored within `Arena`. Removing the `impl Drop for _ArrayVec` resolves the first compiler error (but leaks memory), however *dropping a reference still causes the second error*. Removing the reference drop causes the code to compile and tests to run normally, there are test failures but no segfaults.

Note that `Arena<Node<...` does *not* have drop code from `DropTracker` because it is wrapped in `ManuallyDrop`. Only when `Drop` is implemented on `_ArrayVec` does it get the drop restriction.

Also note that this was tested on the nightly compiler 1.64.
Repository: vscode
Issue: Git - Support git's --color-moved and --color-moved-ws options in diff viewer
Labels: feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

For large code changes or refactoring it is extremely helpful to be able to see which lines of code have actually changed, been added or been removed and easily differentiate them from lines that have simply been rearranged or changed indentation. The `git diff` command and global git config support options to highlight moved lines differently from changed lines, or event to just grey them out. This includes the ability to ignore lines that moved and only differ in indentation.

I would like to be able to have the same benefit when using the VSCode diff viewer since it's much more convenient than viewing a diff in the terminal. It would also be great if it defaulted to use whatever option is set in the project or global git config based on the values returned by `git config --get diff.colormoved` and `git config --get diff.colormovedws`.
Repository: go
Issue: x/build: linux-amd64-wsl builder runs into "unexpected EOF" errors downloading dependencies
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- builder == "linux-amd64-wsl" && `\.go:\d+:\d+: .*@v\d.*: unexpected EOF`
```

From https://build.golang.org/log/1d606b9af9022065aa9b7b4dd76799415ae5fd0b:

```
[...]
go: downloading github.com/gobwas/pool v0.2.1
go: downloading golang.org/x/text v0.3.6
go: downloading github.com/golang/groupcache v0.0.0-20200121045136-8c9f03a8e57e
go: downloading golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1
../../../../pkg/mod/cloud.google.com/go/datastore@v1.2.0/client.go:25:2: google.golang.org/genproto@v0.0.0-20210726143408-b02e89920bf0: read "https:/goproxy.io/@v/v0.0.0-20210726143408-b02e89920bf0.zip": unexpected EOF
../../../../pkg/mod/cloud.google.com/go@v0.88.0/internal/trace/trace.go:23:2: google.golang.org/genproto@v0.0.0-20210726143408-b02e89920bf0: read "https:/goproxy.io/@v/v0.0.0-20210726143408-b02e89920bf0.zip": unexpected EOF
../../../../pkg/mod/google.golang.org/grpc@v1.39.0/status/status.go:34:2: google.golang.org/genproto@v0.0.0-20210726143408-b02e89920bf0: read "https:/goproxy.io/@v/v0.0.0-20210726143408-b02e89920bf0.zip": unexpected EOF
../../../../pkg/mod/cloud.google.com/go/datastore@v1.2.0/save.go:26:2: google.golang.org/genproto@v0.0.0-20210726143408-b02e89920bf0: read "https:/goproxy.io/@v/v0.0.0-20210726143408-b02e89920bf0.zip": unexpected EOF
../../../../pkg/mod/cloud.google.com/go@v0.88.0/cloudbuild/apiv1/v2/cloud_build_client.go:33:2: google.golang.org/genproto@v0.0.0-20210726143408-b02e89920bf0: read "https:/goproxy.io/@v/v0.0.0-20210726143408-b02e89920bf0.zip": unexpected EOF
../../../../pkg/mod/cloud.google.com/go@v0.88.0/longrunning/autogen/operations_client.go:31:2: google.golang.org/genproto@v0.0.0-20210726143408-b02e89920bf0: read "https:/goproxy.io/@v/v0.0.0-20210726143408-b02e89920bf0.zip": unexpected EOF
../../../../pkg/mod/cloud.google.com/go@v0.88.0/iam/iam.go:30:2: google.golang.org/genproto@v0.0.0-20210726143408-b02e89920bf0: read "https:/goproxy.io/@v/v0.0.0-20210726143408-b02e89920bf0.zip": unexpected EOF
../../../../pkg/mod/cloud.google.com/go/storage@v1.10.0/iam.go:24:2: google.golang.org/genproto@v0.0.0-20210726143408-b02e89920bf0: read "https:/goproxy.io/@v/v0.0.0-20210726143408-b02e89920bf0.zip": unexpected EOF
```

The "https:/goproxy.io" part looks unusual, should that be "https://" instead of "https:/"? CC @mengzhuo.

Possibly related to #52793, #52727, #42971, but they're all closed.
Repository: go
Issue: x/build: instances of all internet-facing tests failing
Labels: Builders,NeedsInvestigation

```
#!watchflakes
post <- repo == "build" && `https:\/\/maintner\.golang\.org\/.+: 502 Bad Gateway`
```

Issue created to collect instances where internet-facing tests fail with errors:

```
[...]
2022/07/28 00:33:59 syncing segment 136 did not succeed on attempt 3, will try again in 9s: https://maintner.golang.org/logs/136: 502 Bad Gateway
2022/07/28 00:34:08 Downloading 15228181 bytes of https://maintner.golang.org/logs/136 ...
2022/07/28 00:34:17 Unknown error type *errors.errorString: &errors.errorString{s:"https://maintner.golang.org/logs/136: 502 Bad Gateway"}
2022/07/28 00:34:17 syncing segment 136 did not succeed on attempt 4, will try again in 16s: https://maintner.golang.org/logs/136: 502 Bad Gateway
2022/07/28 00:34:33 Downloading 15228181 bytes of https://maintner.golang.org/logs/136 ...
2022/07/28 00:34:34 Unknown error type *errors.errorString: &errors.errorString{s:"corrupt download"}
2022/07/28 00:34:34 Corpus GetMutations: corrupt download
--- FAIL: TestCorpusCheck (112.99s)
    godata_test.go:52: getting corpus: corrupt download
2022/07/28 00:34:34 Loading data from log *maintner.netMutSource ...
2022/07/28 00:34:34 Downloading 15186069 bytes of https://maintner.golang.org/logs/136 ...
2022/07/28 00:34:35 wrote /root/.cache/golang-maintner/0136.growing.mutlog
2022/07/28 00:35:16 Reloaded data from log *maintner.netMutSource.
FAIL
FAIL	golang.org/x/build/maintner/godata	156.319s
[...]
--- FAIL: TestFindWork (9.05s)
    coordinator_test.go:309: bad http response: 500 Internal Server Error
2022/07/28 00:33:04 gRPCServer.ClearResults: bad status from dashboard: 400 ("400 Bad Request")
2022/07/28 00:33:04 gRPCServer.ClearResults: bad status from dashboard: 308 ("308 Permanent Redirect")
FAIL
FAIL	golang.org/x/build/cmd/coordinator	9.164s
[...]
```

- [2022-07-28T00:31:10-b32452c-462b78f/linux-amd64-longtest](https://build.golang.org/log/071c7ae0215d17cf40283338c20e641fabea14fe)
- [2022-07-28T00:31:10-b32452c-462b78f/windows-amd64-longtest](https://build.golang.org/log/451d9c4afd3ecaa83a7084cc4da6596a91ec6fc7)
Repository: three.js
Issue: WebGLShaderCache poor performance
Labels: Suggestion

<!-- Ignoring this template may result in your bug report getting deleted -->

**Describe the bug**

The WebGLShaderCache uses full vertex/fragment shader source code as keys in a `Map<string, WebGLShaderStage>` and performs several lookups per frame, causing noticeably poor performance.

**To Reproduce**

1. Create a RawShaderMaterial subclass with a non-trivial vertex and/or fragment shader (a few hundred lines of GLSL)
2. Render 10k object instances using this material
3. Record a performance trace in Chrome dev tools
4. Observe the time spent in `WebGLShaderCache#_getShaderStage()`

**Expected behavior**

* Avoid double-lookups in the common path: instead of `.has()` followed by `.get()`, use a single `.get()` when possible
* Allow materials to specify their own `vertexShaderKey` and `fragmentShaderKey` strings that will be used instead of the full shader source code

I have made both of these changes in a patched version of three.js we use in Foxglove Studio (see https://github.com/foxglove/studio/blob/main/patches/three.patch). I'd be happy to turn this into a PR for three.js if this seems like the right approach.

**Platform:**

 - Device: All
 - OS: All
 - Browser: All
 - Three.js version: dev
Repository: svelte
Issue: Binding to store on select element doesn't work with on:input event.
Labels: browser specific

### Describe the bug

In the event listener of input event of select which bind to store value, if the value of the same store but different property was changed, the bind itself doesn't work at all.

1. Create a store with object: i.e. `const s = writable({a:0, b: 0})`
2. Create a `<select>` element with `bind:value={$s.a}` and `on:input={()=>$s.b++}`.
3. Change select element's value. It won't change the `$s.a`

### Reproduction

https://svelte.dev/repl/6520010283474705a76372d5a2569e16?version=3.49.0

### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 12.5
    CPU: (20) arm64 Apple M1 Ultra
    Memory: 46.50 GB / 128.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v16.14.2/bin/yarn
    npm: 8.9.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Safari: 15.6
```


### Severity

annoyance
Repository: godot
Issue: Mipmaps Limit import setting is not respected
Labels: bug,topic:editor,confirmed,topic:import

### Godot version

v4.0.alpha13.official [59dcddc45]

### System information

Windows 10, Vulkan Mobile, NVIDA 980 Ti

### Issue description

The Mipmaps Limit setting in the Texture2D import settings is not respected.

![mipmaps-limit-bug](https://user-images.githubusercontent.com/17506573/182982305-61d01c76-5282-4b77-bbe5-eed93453cf69.png)

(In the above screenshot, note that the Limit is set to 5, but there are 13 mipmaps for this Texture2D resource.)

### Steps to reproduce

1. Add a new Texture2D resource to the FileSystem.
2. Select the new texture resource and view the Import panel
3. Turn on Generate under Mipmaps
4. Click "Reimport" button
5. Set the Limit to something other than -1
6. Click the "Reimport" button again
7. Select the Texture2D resource in the FileSystem to view it in the Inspector panel
8. Note that the inspector shows that there are more mipmaps in the Texture2D resource than in the Limit setting

### Minimal reproduction project

[MipmapsLimitBug.zip](https://github.com/godotengine/godot/files/9264492/MipmapsLimitBug.zip)
Repository: godot
Issue: class callable format is not same as godot-headers and godot-cpp
Labels: bug,topic:gdextension

### Godot version

4.0 alpha13

### System information

windows 10

### Issue description

**I wan't compile gdnative with c++** 

**error:**
error LNK2019 : unresolved external symbol call_deferred

**Point**
I find gen/include/godot_cpp/variant/callable.hpp has   _void call_deferred(const Args&... args) const;_

but godot engine's callable in 4.0alpha13 is _void Callable::call_deferred(const Variant **p_arguments, int p_argcount) const_



### Steps to reproduce

**mycode:**

```
void Example::AddRouteOnMessage(const Variant **args, GDNativeInt arg_count, GDNativeCallError &error) {
	if (arg_count != 2) {
		error.error = GDNATIVE_CALL_ERROR_TOO_FEW_ARGUMENTS;
		error.expected = 2;
	}
	String route = args[0]->operator String();
	Callable funcall = args[1]->operator Callable();
	pitayaClient.AddRouteOnMessage(route.ascii().get_data(),
			[this, &funcall](const uint8_t* data, size_t length) {
				PackedByteArray tmpVar;
				tmpVar.resize(length);
				memcpy(tmpVar.ptrw(), data, length);
				funcall.call_deferred(tmpVar);
			});
} 
```

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Poor sort order for 'go to symbol'
Labels: feature-request,quick-open

Type: <b>Bug</b>

1. In VS Code workspace
1. Open `vscode.d.ts`
1. Use go to symbol and type `tab`

**bug**
The `Tab` interface is low down in the list while fuzzy matches are sorted higher:

![Screen Shot 2022-08-04 at 7 14 14 PM](https://user-images.githubusercontent.com/12821956/182987441-9ef1e48e-7ab6-4005-a7b6-2abfccc961ca.png)


VS Code version: Code - Insiders 1.70.0-insider (Universal) (da76f93349a72022ca4670c1b84860304616aaa2, 2022-08-03T05:55:27.651Z)
OS version: Darwin x64 21.5.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 3, 4|
|Memory (System)|32.00GB (0.03GB free)|
|Process Argv|--crash-reporter-id 48781ca2-1705-4f64-9bab-325055aab55d|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: godot
Issue: Can't edit atlas texture in exported array variable
Labels: bug,topic:editor

### Godot version

v3.5.rc8.official [516d6b6ba]

### System information

Ubuntu 20.04.3 LTS, GLES3

### Issue description

When I export an array variable with a `Texture` type, I can't edit any atlas textures with the editor on the bottom panel.

My current workaround is to export a regular texture and then copy/paste it into the array, making each texture unique after pasting.

### Steps to reproduce

1. Create a script with `export(Array, Texture) var textures`
2. Give the array a non-zero size and create a new `AtlasTexture` in one of the spots
3. You can't open the resource to set an `Atlas` variable :/

### Minimal reproduction project

[no-edit-atlas-arrays.zip](https://github.com/godotengine/godot/files/9265399/no-edit-atlas-arrays.zip)
Repository: pytorch
Issue: GPU arch 8.6 is not covered by the `TORCH_CUDA_ARCH_LIST = All` option 
Labels: module: build,module: cuda,triaged

### 🐛 Describe the bug

Since `TORCH_CUDA_ARCH_LIST = Common` covers 8.6, it's probably a bug that 8.6 is not included in `TORCH_CUDA_ARCH_LIST = All`.

`TORCH_CUDA_ARCH_LIST = All` will use  `CUDA_KNOWN_GPU_ARCHITECTURES`,
https://github.com/pytorch/pytorch/blob/bfebf254dd92f3ed35154597166e7e71fb04f31b/cmake/Modules_CUDA_fix/upstream/FindCUDA/select_compute_arch.cmake#L192-L193
whose latest arch is `"Ampere"`,
https://github.com/pytorch/pytorch/blob/bfebf254dd92f3ed35154597166e7e71fb04f31b/cmake/Modules_CUDA_fix/upstream/FindCUDA/select_compute_arch.cmake#L86
and `"Ampere"` adds 80 to bin/ptx only.
https://github.com/pytorch/pytorch/blob/bfebf254dd92f3ed35154597166e7e71fb04f31b/cmake/Modules_CUDA_fix/upstream/FindCUDA/select_compute_arch.cmake#L237-L239

### Versions

TOT

cc @malfet @seemethere @ngimel
Repository: pytorch
Issue: Unknown builtin op: torchvision::deform_conv2d
Labels: oncall: jit

### 🐛 Describe the bug

I have a model, in this model i have used torchvision.ops.DeformConv2D
then i traced this model with out any error.
but when i want to load this jit model in c++ liobtorch

"torch::jit::load();"

i got an error about Unknown builtin op: torchvision::deform_conv2d
my Version:
python3.8 :  torch 1.11.0-cpu
                   torchvision 0.12.0-cpu
c++ : libtorch 1.11.0-cpu


"
Unknown builtin op: torchvision::deform_conv2d.
Could not find any similar ops to torchvision::deform_conv2d. This op may not exist or may not be currently supported in TorchScript.
.......
Serialized   File "code/__torch__/torchvision/ops/deform_conv.py", line 14
    bias = self.bias
    weight = self.weight
    input = ops.torchvision.deform_conv2d(argument_1, weight, offset, mask, bias, 1, 1, 1, 1, 1, 1, 1, 1, True)
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
    return input
"

### Versions

my Version:
python3.8 :  torch 1.11.0-cpu
                   torchvision 0.12.0-cpu
c++ : libtorch 1.11.0-cpu
Repository: next.js
Issue: Wrong file path generated when using new URL with import.meta.url as the base.
Labels: Upstream,bug,linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.4.0: Fri Mar 18 00:47:26 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T8101
    Binaries:
      Node: 16.15.1
      npm: 8.11.0
      Yarn: 1.22.17
      pnpm: N/A
    Relevant packages:
      next: 12.2.4-canary.12
      eslint-config-next: 12.2.4
      react: 18.2.0
      react-dom: 18.2.0

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

When trying to create a url to a file using `new URL(<path_to_file>, import.meta.url)` the second argument seems to be ignored. I'm getting `/_next/static/media/file.js` whereas, according to webpack [docs](https://webpack.js.org/guides/asset-modules/#url-assets) It should be prefixed with the `document.baseURI`.

I've tried to reproduce it in a vanilla webpack project as well with CRA with no luck, so I assume it's somehow related to next's webpack config.

I first encountered this when trying to use a Stencil generated component library in a next app. The library used web workers and they'd throw `Uncaught DOMException: Failed to execute 'importScripts' on 'WorkerGlobalScope': The URL '/_next/static/media/file.js' is invalid.` in Chrome (and similar errors in Firefox and Safari). However if I tried to open the file, it was there.

This issue affects [Stencil](https://stenciljs.com/) due to how they implement their [web workers transform](https://stenciljs.com/docs/web-workers). When building for a component library what they do is generate the url to the file (using `new URL` with `import.meta.url` as the base), then create a `Blob` with `importScripts('<url.href>')` and then use that blob as the `scriptURL` for the worker. Since `importScripts` needs the full file url, not just an absolute path, it fails.

### Expected Behavior

A proper file url is generated, so that it can be consumed inside workers.

### Link to reproduction

https://stackblitz.com/edit/vercel-next-js-zvgw7e?file=pages/index.tsx

### To Reproduce

Open the minimal reproduction & check the console output.
Repository: PowerToys
Issue: keyboard layout dependent key overrides
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager

### Description of the new feature / enhancement

When using different keyboard layouts it would be useful to override a key on a specific layout. 

### Scenario when this would be used?

I use "US International" and "German" keyboard-layout it would be useful to remap in "German" z to y and y to z, because they are flipped to the "US International" layout. When typing I often switch the layout on the fly and have always the problem that I don't know it y types y or z. When typing German I need access to äöü as well as ß, but when programming I find it more useful to have the braces in their position, when typing one of these wrong it is not so annoying as typing y or z wrong. To think about the key assignment of y and z is annoying in my use case, so I would love to see a layout specific override.

### Supporting information

_No response_
Repository: PowerToys
Issue: x + C -> ctrl + C , x + v -> crtl + V
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager

### Description of the new feature / enhancement

I would like to be able to replace the existing shortcut by pressing two English keys.

When inputting text, it should be entered normally.

### Scenario when this would be used?

x + C -> ctrl + C , x + v -> crtl + V

### Supporting information

_No response_