sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: DevTools: Component bookmarks
Labels: Type: Enhancement,Type: Discussion,Component: Developer Tools,React Core Team

Product developers sometimes find it useful to jump back and forth between a few components in a tree. Currently this requires scrolling or using the selection tool. Maybe we could allow you to temporarily bookmark one or more components somehow? Then the existing Search interface could maybe be repurposed to let you step between bookmarked components (when there's no search text).

These bookmarks would probably not need to be persisted between reloads, so they could be associated with the specific in-memory element<sup>1</sup>.

<sup>1</sup> Although this association would be lost with a filter change.

---
Originally reported via https://github.com/bvaughn/react-devtools-experimental/issues/305
Repository: react
Issue: DevTools: Fix disabled hooks lint rule
Labels: Component: Developer Tools,React Core Team

Disabled via 00f6466

More context at https://github.com/bvaughn/react-devtools-experimental/pull/154#discussion_r275134664

---
Originally reported via https://github.com/bvaughn/react-devtools-experimental/issues/156
Repository: react
Issue: DevTools: Collect more info when profiling
Labels: Type: Enhancement,Component: Developer Tools,React Core Team

Some feedback I've heard from a DevTools user (roughly transcribed by me):

> I'm trying to pinpoint those renders...with hooks, it's sometimes more unclear to me why something is rendering...I generally don't use devtools much anywhere. I use console.log. But Redux devtools worked really well for me because I could see when things were changing and what exactly changed.

Maybe we could add an opt-in mode (in Settings > Profiler) to collect more data when profiling about _why_ a component rendered. For example, if `props` or `state` changed, we could show which keys changed (just their name, not their values). Maybe we could do something similar for context and for hooks?

Then we could add this information to the right side panel for the selected fiber in the Profiler UI.

---
Originally reported via https://github.com/bvaughn/react-devtools-experimental/issues/98
Repository: react
Issue: DevTools: Should Profiler surface the base duration?
Labels: Type: Enhancement,Component: Developer Tools,React Core Team

Benoit shared feedback that it would be helpful to show the base duration for the tree (and/or selected element) to get a sense of the total cost over time. (Not sure yet what we'd call this.)

---
Originally reported via https://github.com/bvaughn/react-devtools-experimental/issues/55
Repository: react
Issue: DevTools: Better linking between browser Performance tab and DevTools Profiler
Labels: Type: Enhancement,Component: Developer Tools,React Core Team

Notes from a chat with Benoit:

It would be nice if starting profiling (or reload and profiling) in the browser auto-started profiling in DevTools.

It would also be nice if viewing a range of time in the Performance tab narrowed down the commits within the Profiler. At least starting the profilers at the same time would enable a manual match-up.

To my knowledge, none of the currently available APIs (including experimental) would enable us to support this level of integration.

---
If we were to make use of the DevTools protocol, we could [`Profiler.start`](https://vanilla.aslushnikov.com/?Profiler.start) and [`Profiler.stop`](https://vanilla.aslushnikov.com/?Profiler.stop) the built-in profiler in sync with React's own profiler. Chrome's profiler also dispatches [`Profiler.consoleProfileStarted`](https://vanilla.aslushnikov.com/?Profiler.consoleProfileStarted) and [`Profiler.consoleProfileFinished`](https://vanilla.aslushnikov.com/?Profiler.consoleProfileFinished) events which we _could_ use to follow the browser's profiler if we wanted to.

There do not appear to be any APIs/events for syncing the zoomed-in range.

---
Originally reported via https://github.com/bvaughn/react-devtools-experimental/issues/37
Repository: create-react-app
Issue: [Option] Disable automatic dependency installation
Labels: issue: proposal

### Is your proposal related to a problem?
No

### Describe the solution you'd like
It would be nice to be able to use create-react-app to create a new project without automatically installing all of the dependencies. Something like ```create-react-app app-name --skipInstall``` similar to how the [@angular/cli](https://angular.io/cli/new) works.

### Describe alternatives you've considered

It doesn't appear that there are any options for configuring create-react-app other than additional logging. Manually creating a React project from scratch would be counterproductive.

### Additional context
I find myself generating a lot of template/placeholder projects with create-react-app, without the need to run them right away. It would greatly speed up the process if I could optionally omit the dependency installation step.
Repository: rust
Issue: Cannot use `use Self::*;` inside a method
Labels: C-enhancement,A-diagnostics,A-resolve,T-lang,T-compiler,D-confusing

```rust
enum A {}

impl A {
    fn foo() {
        use Self::*; // error: unresolved import `Self`
    }
}
```
It's counterintuitive that this fails. At the very least (if it's not possible to fix this), we should special case the error message to explain the problem.
https://github.com/rust-lang/rust/issues/49683#issuecomment-458886172 may be related.
Repository: react
Issue: DevTools: Crashes and warnings when quickly collapsing
Labels: Type: Bug,Component: Developer Tools,React Core Team

This is weird. Happens if I select a node deeply and then long-press "left" arrow.

```
Invalid index 154 specified; store contains 154 items.

Uncaught Invariant Violation: Expected to find a host parent. This error is likely caused by a bug in React. Please file an issue.
    at ReactError (file:///Users/gaearon/p/react-devtools-experimental/shells/dev/build/devtools.js:8529:40)
```

It starts with "invalid index" and then gives me different React invariants or warnings depending on how lucky I am.

![Screen Recording 2019-04-25 at 05 58 PM](https://user-images.githubusercontent.com/810438/56754075-fcbafb80-6783-11e9-8fe6-84aa29d1c120.gif)

---
More weird symptoms:

<img width="889" alt="Screen Shot 2019-04-25 at 6 38 22 PM" src="https://user-images.githubusercontent.com/810438/56756281-5671f480-6789-11e9-8d0b-631a5217e63b.png">

---
<img width="832" alt="Screen Shot 2019-04-25 at 6 41 37 PM" src="https://user-images.githubusercontent.com/810438/56756492-c7191100-6789-11e9-8814-cb849590ee01.png">

---
This "fixes" it:

```diff
       runWithPriority(UserBlockingPriority, () => dispatch(action));
-      next(() => dispatch({ type: 'UPDATE_INSPECTED_ELEMENT_ID' }));
+      runWithPriority(UserBlockingPriority, () => dispatch({ type: 'UPDATE_INSPECTED_ELEMENT_ID' }));
     },
```

So I suspect it's a bug with `Scheduler.next()`.

---
This also looks funky. Note how somewhere in the middle right pane gets "stuck" showing the same cycle of values:

![Screen Recording 2019-04-25 at 07 36 PM](https://user-images.githubusercontent.com/810438/56759733-8b824500-6791-11e9-95ba-d4d3630a4c5e.gif)

---
React bug: https://github.com/facebook/react/issues/15512

---
Originally reported by @gaearon via https://github.com/bvaughn/react-devtools-experimental/issues/228
Repository: react
Issue: DevTools: Re-enable postMessage transferable for faster ArrayBuffer transfers
Labels: Type: Bug,Component: Developer Tools,React Core Team

I got this on FB.com sandbox:

<img width="815" alt="screen shot 2019-03-01 at 1 15 24 pm" src="https://user-images.githubusercontent.com/810438/53640457-26dcbb00-3c24-11e9-828f-a987ffeec4da.png">


---
Originally reported by @gaearon via https://github.com/bvaughn/react-devtools-experimental/issues/25
Repository: react
Issue: DevTools: Check if accessibility regressions exist compared to old DevTools
Labels: Component: Developer Tools,React Core Team

Before this becomes stable, we need to check if we are regressing accessibility on any important existing interactions.

At least, we should probably make the tree view focusable.

---
Originally reported by @gaearon via https://github.com/bvaughn/react-devtools-experimental/issues/52
Repository: react
Issue: DevTools: Audit places where we change tags or disconnect alternates in React
Labels: Component: Developer Tools,React Core Team

Cases like https://github.com/bvaughn/react-devtools-experimental/issues/197 (where a dehydrated Suspense node turns into a regular one) produce confusing failures because we expect Fiber alternates to be "for life", whereas in practice they can actually get disconnected by React in some cases. (Search for "Disconnect" in ReactFiberBeginWork.)

Additionally, I think changing `tag` can also produce confusing failures if it changes from a value that was filtered out, to a value that is not filtered out.

We need to be more proactive about handling these cases when we make such changes to React, and we need to look at existing cases where this happens and whether we can handle them.

---
Originally reported by @gaearon via https://github.com/bvaughn/react-devtools-experimental/issues/198
Repository: react
Issue: DevTools: Components tree is sometimes unexpectedly empty after navigation
Labels: Type: Bug,Component: Developer Tools,React Core Team

1. Open FB page
2. Open Components tab
3. Change address bar to `https://reactjs.org` and press Enter

Expected: Components tab gets populated.
Actual:

<img width="783" alt="Screen Shot 2019-04-23 at 7 27 37 PM" src="https://user-images.githubusercontent.com/810438/56606380-00247a80-65fe-11e9-988c-2ad3e69eb579.png">

~~If I **inspect background page**, I see this:~~ (fixed by #229)

<img width="652" alt="Screen Shot 2019-04-23 at 7 27 12 PM" src="https://user-images.githubusercontent.com/810438/56606408-0b77a600-65fe-11e9-9f65-5502401b7e4a.png">

---
Originally reported by @gaearon via https://github.com/bvaughn/react-devtools-experimental/issues/217
Repository: react
Issue: DevTools: Write tests for preserving selection
Labels: Component: Developer Tools,React Core Team

See https://github.com/bvaughn/react-devtools-experimental/pull/215. It would be nice to have test coverage for it.

---
I got stuck here:

```js
    const Component = () => <div>Hi</div>;

    act(() =>
      ReactDOM.render(<Component />, document.createElement('div'))
    );
    const id = store.getElementIDAtIndex(0);
    const rendererID = store.getRendererIDForElement(id);

    act(() => {
      global.bridge.send('selectElement', { id, rendererID });
    })
```

This test fails on master because bridge object is shared between agent and store. Separating it and emulating having two bridges didn't work because of some regression in the Suspense test. I haven't dug into why because the stack trace display is obscured and points to the wrong line in the test. The stack trace display points to the wrong line likely because of regenerator code. The regenerator code is likely coming from `babel-preset-env` thinking we need to polyfill async/await. I don't know why `babel-preset-env` doesn't realize my Node already has async/await. At that point I punted on this.

---
Originally reported by @gaearon via https://github.com/bvaughn/react-devtools-experimental/issues/219
Repository: flutter
Issue: [flutter_tool] Add support for unknown/unsupported platforms for the plugin tools templates
Labels: c: new feature,tool,P3,team-tool,triaged-tool
Repository: flutter
Issue: -[FlutterEngine maybeSetupPlatformViewChannels] is not thread-safe.
Labels: c: crash,platform-ios,engine,P2,team-ios,triaged-ios

The platform view may have been collected in [the method call handler](https://github.com/flutter/engine/blob/99ee3c2b0df7911baa390fa897cefc836605d154/shell/platform/darwin/ios/framework/Source/FlutterEngine.mm#L305) which will cause the dereference of a collected value.
Repository: react
Issue: Chrome's Custom Formatters
Labels: Type: Discussion,Component: Developer Tools

**Do you want to request a *feature* or report a *bug*?**
Feature

_Transferring feature request from the old repo https://github.com/facebook/react-devtools/issues/989_

Hi! Is there any plans on supporting [Chrome's custom formatters](https://docs.google.com/document/d/1FTascZXT9cxfetuPRT2eXPQKXui4nWFivUnS_335T3U/preview) to display custom data structures in readable format in React dev tools?

For example when debugging ClojureScript's immutable data structures we have a custom formatter that outputs data into the console in readable and inspectable format.

Here how it looks like
![screen shot 2018-02-19 at 3 02 32 pm](https://user-images.githubusercontent.com/1355501/36379156-39e8a882-1586-11e8-8973-7e6d3772cb4e.png)

And here's how data looks like in React Dev Tools inspector (basically underlying implementation of a data structure as seen in plain JS)
![screen shot 2018-02-19 at 2 59 04 pm](https://user-images.githubusercontent.com/1355501/36379177-4b280d90-1586-11e8-808d-ea7f2cebb274.png)

I think this can be done for React Dev Tools since once Custom Formatters are defined they are applied everywhere in Chrome's Dev Tools where it's possible to inspect data.
Repository: TypeScript
Issue: TSServer: Find all reference for per overloaded function type
Labels: Suggestion,Awaiting More Feedback,Domain: Refactorings



## Search Terms
Find references, overload, function, overloaded function

## Suggestion

Provide a mechanism to search references of a function with particular overloaded type

## Use Cases
In current implementation find all references for overloaded function shows all references for every overload
Some times we need to find references of particular overload only (i.e. a overload is deprecated and we want to update all use cases)

## Examples

```ts
/**
 * @deprecated
 **/
declare function fn():void; // overload 1
declare function fn(param:string):number; // overload  2

fn(); // use 1

const x = fn('a'); // use 2
const y = fn('b'); // use 3

```

Finding references for `overload 1` should list `use 1`.
Finding references for `overload 2` should list `use 2` and `use 3`.

## 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: create-react-app
Issue: disable TS check on start script
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

Yep. My project has some interface exportation files just for IDE type definition (nothing imported on the project), but, when I try to `npm start`, the script tells me to install (unnecessarily) typescript and creates a `tsconfig.json` file in project's root dir. This is annoying.

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

Add some way (maybe a flag?) to disable this check.

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

(Write your answer here.)

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here if you haven't already.
-->

The project's team does not have TypeScript fluency, but we're applying it in some cases that involve sensitive data, but just to get the IDE code time report (`/** @type...`). There are no reasons to install whole ts lib just for this.
Repository: flutter
Issue: Expose Skia Paint.getTextPath
Labels: c: new feature,engine,dependency: skia,P3,team-engine,triaged-engine

Flutter fails to expose https://skia.org/user/api/SkPaint_Reference#SkPaint_getTextPath

## Use case

Numerous. Using the text as clipping path, or using it as a base for more complex painting operations.
Repository: pytorch
Issue: tensorboard add_graph error
Labels: triaged,module: tensorboard

I update torch to `1.2.0` and use `torch.utils.tensorboard import SummaryWriter` save the graph, report error:
```
Only tensors or tuples of tensors can be output from traced functions(getOutput at /pytorch/torch/csrc/jit/tracer.cpp:208)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x33 (0x7f67d5059273 in /opt/anaconda3/lib/python3.7/site-packages/lib/libc10.so)
...
```
When I use torch 1.1.0 + cuda9.0  don't report error.
Repository: opencv
Issue: OpenCV VideoCapture::read reads an empty matrix mid video
Labels: bug,category: videoio,RFC,future,confirmed


##### System information
- OpenCV => 4.1
- Operating System / Platform => x86_64 GNU/Linux (Debian-based)
- Compiler => g++ (8.3.0)

##### Detailed description

OpenCV VideoCapture::read fails to read certain video file formats until the end. 
Three test videos were tested (videos provided below):
rottest.avi (fps: 24; total frames: 337, reads 107 frames - 108th was unsuccessful) 
rottest.mp4 (fps: 24; total frames: 337, reads 337 frames - 338th was unsuccessful; as expected)
rottest.webm (fps: 30; total frames: 423, reads 107 frames - 108th was unsuccessful)

All videos have the same content, only underwent format conversion. 
The expected behavior is for rottest.webm to successfully read 423 frames and fail on 424th,
while for rottest.avi is should read 337 frames successfully and fail on the 338th frame.

To be more specific, in all instances I have checked manually and the call `cap.read(curr_img);` returns false on the unsuccessful frame numbers given above. 

I did not try to visualize the images using cv::imshow but can do that as well if someone considers it necessary.

##### Steps to reproduce

testvideoin.cpp

```
#include <opencv2/videoio.hpp>
#include <opencv2/highgui/highgui.hpp>
#include <opencv2/imgproc/imgproc.hpp>
#include <iostream>
#include <string>

int main(int argc, char const *argv[])
{
	if (argc<2)
		return 0;
	std::string path(argv[1]);
	cv::VideoCapture cap(path);
	cv::Mat curr_img;
	unsigned frame_no=1;
	bool success=false;
	std::cout << "Video total frame number: " << static_cast<int>(cap.get(cv::CAP_PROP_FRAME_COUNT)) << std::endl;

	success=cap.read(curr_img);
	while (!curr_img.empty())
	{
		std::cout << "Frame no: " << frame_no <<"; SUCCESS: "<< success << std::endl;
		success=cap.read(curr_img);
		if (!success)
			curr_img=cv::Mat();
		frame_no++;
	}

	std::cout <<"Frame no: " << frame_no << "; Image empty: " << curr_img.empty() << std::endl;
	return 0;
}
```

Compilation: 
g++ -std=c++14 -Wall -Wextra -g -O0 -I/usr/local/include/opencv4 -L/usr/local/lib -o testvideoin -lopencv_core -lopencv_videoio -lopencv_imgproc -lopencv_imgcodecs testvideoin.cpp

Test set: https://drive.google.com/open?id=1FdyrYWi7qNGB3KSaELLQDZ2ugAnxp2OL
(rottest.webm, rottest.avi, rottest.mp4)
Repository: go
Issue: cmd/gc: go:nointerface pragma is undocumented
Labels: Documentation,help wanted,NeedsInvestigation

The Go compiler has a pragma

    //go:nointerface

As far as I can tell, it prevents a method from being used to satisfy an interface. However, I cannot find any (public) documentation on it.

Even https://golang.org/src/cmd/compile/internal/gc/lex.go, which has comments for the other pragmas, does not describe this one.
Repository: go
Issue: doc: do not embed style in release-note HTML files
Labels: Documentation,NeedsFix

When styles are embedded in release note html files, it may also require you to do the same thing in the previous ones to keep the same style across all versions.

[The embedded style](https://github.com/golang/go/blob/d6ffc1d8394d6f6420bb92d79d320da88720fbe0/doc/go1.6.html#L12) in go1.6 html seems to cause #33718.

I think that it is better to try not to embed style in release note html files, and write it in stylesheet instead.
Repository: vue
Issue: Scoped CSS attribute is reused or discarded when switching between components with scoped CSS
Labels: bug,contribution welcome

### Version
2.6.10

### Reproduction link

- Functional components: [https://github.com/sin1ght/test](https://github.com/sin1ght/test)
- Regular components and slots: https://codesandbox.io/embed/vue-template-3pnsx







### Steps to reproduce
After npm run serve, click the toggle button and find that child has no style.

Child and child2 components are reused, child's data-v-* disappears, causing the style to disappear

### What is expected?

Child should have a black background scope style

### What is actually happening?

Child without style

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: flutter
Issue: Disable crash reporting if the flutter_tool checkout is dirty
Labels: c: new feature,team,tool,P2,team-tool,triaged-tool

This can be the source of confusing crash reports that are not possible to debug.
Repository: flutter
Issue: Add any experimental flags enabled to crash reports
Labels: c: new feature,team,tool,P3,team-tool,triaged-tool

This will help with narrowing down the cause of tool crashes, reproducing and fixing them.