sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: DevTools can't load Components tree in Components Tab
Labels: Type: Bug,Type: Discussion,Component: Developer Tools

## Summary

There's a mix of several different issues that result in the Components tree not being able to load, which happens inconsistently. 

In some cases, after trying out a different build of DevTools with a potential fix, the issue seems to fully resolve itself, even after going back to using the "bad" build where the issue originally occurred. However, that doesn't mean the issue is fixed by that build, since other reports keep occurring.

This issue is a master task tracking all of the issues we've seen so far from user reports:

- `Cannot add node "x" because a node with that id is already in the store`, reported in #21636 before we shipped v4.20.0.
- `No location name for view with id <id_of_components _tab>`, reported in the console inspecting DevTools itself.
![image](https://user-images.githubusercontent.com/1271509/139111165-e5717518-f1fa-4579-80a9-5f8a0b80bf90.png)
- `Invalid renderer id "1"`, logged in the console of the main page
![image](https://user-images.githubusercontent.com/1271509/139113532-ceff5ac1-ab50-42ef-a432-153ea63733fa.png)
- `Unable to find React on the page.`, which suggests that the extension failed to load entirely as that's just placeholder text from before the extension panels are created with Chrome.
![image](https://user-images.githubusercontent.com/1271509/139111465-21759a3c-6455-49df-acfc-e7c56e430cb5.png)
- `Uncaught error: Extension Context Invalidated`, reported in #22577.
https://user-images.githubusercontent.com/7581546/137986963-f55b9fc2-745d-4aeb-8b8b-49645197c163.png
- Navigating to a new tab doesn't load Components tree (even after v4.21.0 w duplicate extension logic reverted). See https://github.com/facebook/react/issues/22663 for details

![image](https://user-images.githubusercontent.com/1271509/139601873-7e923b1d-6831-4994-ac17-d94ba58cf409.png)

- No error being shown at all, as also reported in #22577.


---------

## Root Cause and Fixes

- The suspected root cause is the changes shipped in v4.20.0 for detecting duplicate installations of DevTools. 
- A fix was attempted with v.4.20.2, based on reports from users in #22636 confirming that our changes in #22597 fixed the issue
- The logic is now being fully reverted in https://github.com/facebook/react/pull/22638
Repository: electron
Issue: [Feature Request]: Drag / Resize API for BrowserView within Parent Window
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

While one can resize BrowserViews via the .setBounds API, an often desired feature would be a BrowserView that can be dragged and resized similar to a BrowserWindow (BrowserWindow on the Desktop, BrowserView within the BrowserWindow).

While trying the implement this using a mousemove event listener on a "drag" region I realised that it is non-trivial, since reading ev.clientX relative to the dragged BrowserView leads to errors, since the BrowserView get incrementally repositions and hence the coordinates aren't relative anymore to the old coordinate.

### Proposed Solution

Have ability to define draggable region, similar to BrowserWindow and maybe pass on resize options into BrowserView constructor so it can be automatically resized like the BrowserWindow.

### Alternatives Considered

I think I will implement it, that on drag / resize start I create a topLevel invisible BrowserView that handles the mouseMove event and routes them to main, but this may be non-trivial, especially for beginner Coders.

### Additional Information

_No response_
Repository: neovim
Issue: Unable to open swap file when full filepath is too long
Labels: bug,platform:windows

On windows if the full filepath of a file is too long, then the message will display when opening the file in Neovim:

E303: Unable to open swap file for "very\long\filepath", recovery impossible

My tests indicate that 197 characters is the limit, with 198 character filepaths causing the error.
This may be an issue for people with deeply nested file structures or long file or directory names.

I imagine this is caused by the way swapfile names are generated in neovim, and the inbuilt filename limits in windows, but I haven't explored it.

Will happily delete this thread if this is a known issue.

Thanks, Tom
Repository: vscode
Issue: The call hierarchy UI should have the ability to filter calls, or apply name filter patterns
Labels: feature-request,callhierarchy

<!-- ⚠️⚠️ 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. -->
**Note**: This came from VS Code Java extension, referencing the issue here: https://github.com/redhat-developer/vscode-java/issues/2179

When I use **Show Call Hierarchy** on a property in a Java class object that is frequently used in both the main source code, as well as in the unit tests, the Call Hierarchy list would display a bunch of results. Because, the results include both the main source code and unit tests references, there isn't a way to automatically exclude certain folder directories or paths out from unwanted invocations.

I would like to request for a UI improvement in Visual Studio Code, to allow users apply any one of the following options:

- Filter test codes based on folder directory. (e.g., Filtering Java unit test codes or Java source code documents residing under `src/test/java` when specified)
- Apply name filter patterns. (e.g., Filtering reference names that matches the given filter patterns in the reference class names.)
- Limit the call depth of a given number. (e.g., Only goes down in depth up to the given number, inclusive.)

This feature is similar to Eclipse IDE's "Filter Calls" dialog:

![image](https://user-images.githubusercontent.com/6444116/138523340-7b14bfe2-5463-4fa7-adf3-92118ecde522.png)

This is accessed by invoking "Show Call Hierarchy" on a class member, then opening "Filters" in the "More Options" menu in Eclipse IDE.

Currently, we don't have anything similar to this in Visual Studio Code in general (regardless of what language support), where the call hierarchy UI allows the user to filter out what references to look for / ignore.

##### Environment
- Operating System: Ubuntu 20.04.2 LTS
- JDK version: AdoptOpenJDK 11  (jdk-11.0.11+9)
- Visual Studio Code version:  1.61.2

##### Current Result

The "Show Call Hierarchy" looks something like this, whenever we attempt to invoke call hierarchy. I'm using Java language support as an example.

![image](https://user-images.githubusercontent.com/6444116/138524191-a7c98040-2fdb-4ad3-aa27-11a118db7a4b.png)

##### Expected Result

Call hierarchy UI with filter options would automatically filter out either all test codes, or applying a name filter pattern to exclude any references containing "test". A mock example should look something like this immediately upon invoking the call hierarchy:

![image](https://user-images.githubusercontent.com/6444116/138524377-a1d0f202-1fef-4e42-a683-9dffc20c3104.png)
Repository: go
Issue: proposal: context: add generic Key type
Labels: Proposal,Proposal-Hold,generics

The `Context` API suffers from the lack of type safety since keys and values are both `interface{}`.

With generics coming in Go 1.18, I propose the addition of:
```go
package context

// Key is a generic key type associated with a specific value type.
type Key[Value any] struct{ name *string }

// NewKey constructs a new context key with an associated value.
// Every key is unique, even if provided the same name.
func NewKey[Value any](name string) Key[Value] {
	return Key[Value]{&name}
}

// WithValue returns a copy of parent in which the value associated with key is val.
//
// It is a type-safe equivalent of WithValue.
func (key Key[Value]) WithValue(parent context.Context, val Value) context.Context {
	return context.WithValue(ctx, key, val)
}

// Value returns the value associated with this context for key,
// additionally reporting whether the value was found.
//
// It is a type-safe equivalent of Context.Value.
func (key Key[Value]) Value(ctx context.Context) (Value, bool) {
	v, ok := ctx.Value(key).(Value)
	return v, ok
}

// String returns the name of the key.
func (key Key[Value]) String() string {
	return *key.name
}
```
For type safety, the value type is associated with the key type, and type safe variants of `Context.Value` and `WithValue` are hung off of `Key` as methods.

[Example usage](https://go2goplay.golang.org/p/Z1y6AK6h9eq):
```go
k1 := NewKey[error]("error")
k2 := NewKey[error]("error")
fmt.Println(k1 == k2) // expect false since each key is unique

ctx := context.Background()
ctx = k1.WithValue(ctx, io.EOF)

fmt.Println(k1.Value(ctx)) // EOF true
fmt.Println(k2.Value(ctx)) // <nil> false
```

\cc @josharian
Repository: pytorch
Issue: [FX] autowrap_functions doesn't work for module-scoped functions
Labels: triaged,module: fx

Repro:

```
import torch
import torch.fx

def hi(a, b):
    return torch.zeros(a, b)

tracer = torch.fx.Tracer(autowrap_functions=(torch.zeros,))

tracer.trace(hi)

"""
TypeError: zeros() received an invalid combination of arguments - got (Proxy, Proxy), but expected one of:
 * (tuple of ints size, *, tuple of names names, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
 * (tuple of ints size, *, Tensor out, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
"""
```

I believe the issue here is that the implementation of `autowrap_functions` dumps all of the function IDs into the `_autowrap_function_ids` set:

https://github.com/pytorch/pytorch/blob/7c48b9ee25b1d9c7ba7adf91f3808c7426a046e1/torch/fx/_symbolic_trace.py#L242

which is then picked up by `_autowrap_check`:

https://github.com/pytorch/pytorch/blob/7c48b9ee25b1d9c7ba7adf91f3808c7426a046e1/torch/fx/_symbolic_trace.py#L615

which then only looks into the passed-in `frame_dict`:

https://github.com/pytorch/pytorch/blob/7c48b9ee25b1d9c7ba7adf91f3808c7426a046e1/torch/fx/_symbolic_trace.py#L796

which at that callsite is the globals dict of the traced function:

https://github.com/pytorch/pytorch/blob/7c48b9ee25b1d9c7ba7adf91f3808c7426a046e1/torch/fx/_symbolic_trace.py#L588

This means that, since `torch.zeros` does not directly appear in the globals of the traced function, it is not patched. We should do a few things:

1) Add a set that confirms that all of `_autowrap_function_ids` is patched and throws a warning if any remain that are not patched
2) Build out the infrastructure to be able to patch module-scoped functions passed in as `autowrap_functions`. This might require patching the recursive modules in the traced function's globals

cc @ezyang @SherlockNoMad
Repository: godot
Issue: Animation editor allows dragging keyframes to negative time values
Labels: discussion,topic:editor,topic:animation

### Godot version

4.0.dev (5ff0624a0), 3.3.4.stable

### System information

Fedora 34, GeForce GTX 1080 (NVIDIA 470.74)

### Issue description

Using the mouse, it's possible to drag keyframes into negative time values:

https://user-images.githubusercontent.com/180032/139137667-1743c502-f286-4ad9-a1b3-f225ffb85c8e.mp4

Is this a bug or intended behavior?


### Steps to reproduce

- Create an AnimationPlayer node.
- Create an animation property track.
- Create at least one keyframe, and move the first one to the left (beyond the `0` time marker).

### Minimal reproduction project

N/A
Repository: flutter
Issue: Override the shader compilation error handler to avoid crashes
Labels: engine,P3,team-engine,triaged-engine

Skia has an SkDEBUGFAIL here: https://github.com/google/skia/blob/13fd52e587d22a2f2f2119a4172c3d71a7164ad4/src/gpu/GrShaderUtils.cpp#L219

This should only actually crash if `SK_DEBUG`, which should only be set if`!NDEBUG`, which means it should only affect `unopt` builds of the engine. We should still probably avoid it for local developers.
Repository: flutter
Issue: [video_player] WEB: Ability to use VideoPlayerController.file for cached files
Labels: c: new feature,platform-web,p: video_player,package,c: proposal,P3,team-web,triaged-web

 We are working on a video intensive web app and we want to preload the next couple of videos in the feed. We can do the downloading using `flutter_cache_manager`. However we can not use `.file` factory of video player controller. What is the reason for this exactly?

In the documentation it states that:

> The Web platform does not suppport dart:io, so avoid using the VideoPlayerController.file constructor for the plugin. Using the constructor attempts to create a VideoPlayerController.file that will throw an UnimplementedError.

But in the [discussion made here](https://github.com/Baseflow/flutter_cache_manager/issues/339#issuecomment-950109846), they offered using `MemoryFileSystem` for web.

> An implementation of FileSystem that exists entirely in memory with an internal representation loosely based on the Filesystem Hierarchy Standard.
> This implementation of the FileSystem interface does not directly use any dart:io APIs; it merely uses the library's enum values and interfaces. As such, it is suitable for use in the browser.

[Flutter API Docs - MemoryFileSystem](https://api.flutter.dev/flutter/package-file_memory/MemoryFileSystem-class.html)

So I was wondering if we can use this as an alternative to `VideoPlayerController.file()`? maybe add something new like `VideoPlayerController.memory()` just for the Web?
Repository: vscode
Issue: VScode copy to Onenote missing blank line
Labels: bug,macos,editor-clipboard

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:1.61.2 (Universal)
- OS Version:MacOS 11.5.2 (20G95)

Steps to Reproduce:

1.in vscode use `Markdown` format like this

```
testblank1
testblank2

testblank3
testblank4
```

2.copy to onenote

```
testblank1
testblank2
testblank3
testblank4
```
blank row will be missing

3. macos editor、sublime...etc. it dont have this issues
Repository: rust
Issue: Missing add #![feature(const_trait_impl)] help message
Labels: A-diagnostics,T-compiler

This code compiles without errors with the last Nightly:

```rust
#![feature(const_num_from_num, const_trait_impl)]
#![allow(incomplete_features, dead_code)]
fn main() {
    const X: u64 = u64::from(10_u32);
}
```

While the following two versions:

```rust
#![feature(const_num_from_num)]
#![allow(incomplete_features, dead_code)]
fn main() {
    const X: u64 = u64::from(10_u32);
}
```

```rust
#![allow(incomplete_features, dead_code)]
fn main() {
    const X: u64 = u64::from(10_u32);
}
```

They don't compile and rustc doesn't give a help message like this that helps how to fix the code:

```
  = help: add `#![feature(const_trait_impl)]` to the crate attributes to enable
```
Using:
```
rustc 1.58.0-nightly (e269e6bf4 2021-10-26)
binary: rustc
commit-hash: e269e6bf47f40c9046cd44ab787881d700099252
commit-date: 2021-10-26
host: x86_64-pc-windows-gnu
release: 1.58.0-nightly
LLVM version: 13.0.0
```
Repository: pytorch
Issue: [FX] FX torchvision tests fail with torchvision 0.10
Labels: triaged,module: fx

User reported that these two tests fail with torchvision `0.10.0a0+e828eef`:

```
test_torchvision_models_detection_ssd300_vgg16
test_torchvision_models_detection_ssdlite320_mobilenet_v3_large
```

This pointed out the fact that PT mainline CI uses an old (0.9) version of torchvision: https://github.com/pytorch/pytorch/blob/9ba39d2008113747d1c69d13c749b31ea06bec17/.jenkins/pytorch/common_utils.sh#L85

We should update torchvision in CI and fix the FX issues

cc @ezyang @SherlockNoMad @fmassa
Repository: vscode
Issue: Make breadcrumbs always visible when showTabs is disabled
Labels: feature-request,breadcrumbs

<!-- ⚠️⚠️ 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. -->
When `workbench.editor.showTabs` is disabled, the breadcrumbs UI is only visible when the editor is focused. For me it would be nice if I could configure VSCode so the breadcrumbs were always visible.

I think this is the relevant line where we'd want to conditionally hide the breadcrumbs UI depending on a new configuration setting:

https://github.com/microsoft/vscode/blob/92646227bc0030ae07fc20be0f57b7809bcb4c74/src/vs/workbench/browser/parts/editor/noTabsTitleControl.ts#L255
Repository: pytorch
Issue: [LTC] Replace mv with addmv in ts_native_functions.yaml
Labels: triaged

Replace mv with addmv in ts_native_functions.yaml since mv is decomposed into addmv.
Repository: pytorch
Issue: Missing doc for torch.autograd functions
Labels: module: docs,module: autograd,triaged

The following functions and classes are not documented correctly: they are part of the public API but do not show up on the [docs website](https://pytorch.org/docs/master/)
This means that we want to do either:
- Add a docstring and make sure it is properly added to a .rst file so that it appears on the docs website
- Make it private by prepending a `_` to the function name

torch.autograd
--------------
Functions:
 * register_py_tensor_class_for_device
 * variable

cc @brianjo @mruberry @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: pytorch
Issue: Missing doc for torch.cuda functions
Labels: module: docs,module: cuda,triaged

The following functions and classes are not documented correctly: they are part of the public API but do not show up on the [docs website](https://pytorch.org/docs/master/)
This means that we want to do either:
- Add a docstring and make sure it is properly added to a .rst file so that it appears on the docs website
- Make it private by prepending a `_` to the function name
- Remove it from the public API by deleting it from your `__init__.py` file (like [here](https://github.com/pytorch/pytorch/blob/708f7b120957f47f22752f49d52c08d5a0ca7fc0/torch/__init__.py#L696))

torch.cuda
----------
Functions:
 * check_error
 * cudart
 * is_bf16_supported

Classes:
 * BFloat16Storage
 * BFloat16Tensor
 * BoolStorage
 * BoolTensor
 * ByteStorage
 * ByteTensor
 * CharStorage
 * CharTensor
 * ComplexDoubleStorage
 * ComplexFloatStorage
 * CudaError
 * DeferredCudaCallError
 * DoubleStorage
 * DoubleTensor
 * FloatStorage
 * FloatTensor
 * HalfStorage
 * HalfTensor
 * IntStorage
 * IntTensor
 * LongStorage
 * LongTensor
 * ShortStorage
 * ShortTensor
 * UntypedStorage
 * cudaStatus

cc @brianjo @mruberry @ngimel
Repository: pytorch
Issue: Missing doc for torch.distributed functions
Labels: high priority,triage review,oncall: distributed,module: docs,better-engineering

The following functions and classes are not documented correctly: they are part of the public API but do not show up on the [docs website](https://pytorch.org/docs/master/)
This means that we want to do either:
- Add a docstring and make sure it is properly added to a .rst file so that it appears on the docs website
- Make it private by prepending a `_` to the function name
- Remove it from the public API by deleting it from your `__init__.py` file (like [here](https://github.com/pytorch/pytorch/blob/708f7b120957f47f22752f49d52c08d5a0ca7fc0/torch/__init__.py#L696))


torch.distributed.autograd
--------------------------
Functions:
 * is_available

torch.distributed.elastic.events
--------------------------------
Functions:
 * construct_and_record_rdzv_event
 * record_rdzv_event

torch.distributed.elastic.metrics
---------------------------------
Functions:
 * initialize_metrics

torch.distributed.elastic.multiprocessing.errors
------------------------------------------------
Classes:
 * ChildFailedError -- missing methods:

   - format_msg
   - get_first_failure
 * ProcessFailure -- missing methods:

   - signal_name
   - timestamp_isoformat

torch.distributed.elastic.rendezvous.registry
---------------------------------------------
Functions:
 * get_rendezvous_handler

torch.distributed.launch
------------------------
Functions:
 * launch
 * main
 * parse_args

torch.distributed.rpc
---------------------
Functions:
 * is_available

torch.distributed.run
---------------------
Functions:
 * config_from_args
 * determine_local_world_size
 * get_args_parser
 * get_rdzv_endpoint
 * get_use_env
 * main
 * parse_args
 * parse_min_max_nnodes
 * run
 * run_script_path

cc @ezyang @gchanan @zou3519 @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @brianjo @mruberry