sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: Bug: Form reset lost checkbox onChange event
Labels: Type: Bug,Component: DOM

Hi, I use checkbox uncontrolled mode, onChange in form reset after, lose onChange.
```js
<input type="checkbox" onChange={onChange} />
```

but use add ref.addEventListener('change', onChange) is ok
```js
const checkRef = useRef<HTMLInputElement>();
useEffect(() => {
        if (checkboxRef) {
            checkboxRef.current.addEventListener('change', onChange);
        }
    }, []);

<input type="checkbox" ref="checkboxRef" onChange={onChange} />
```


React version: 16.13 and old 

## Steps To Reproduce

1. checkbox => checked
2. form reset
3. checked  => checked

Link to code example:
[not react is ok](https://codepen.io/imagine10255/pen/ExPaLOJ?editors=1111)
[reset is lose target onChange](https://codesandbox.io/s/affectionate-brook-96dw9?file=/src/App.js)

## The current behavior
1. checkbox => checked (target onChange)
2. form reset
3. checked  => checked (lose target onChange)

## The expected behavior
1. checkbox => checked (target onChange)
2. form reset
3. checked  => checked (target onChange)
Repository: flutter
Issue: Reference material spec for text scaling when available in AppBar
Labels: framework,f: material design,a: typography,team-design,triaged-design

Follow up from https://github.com/flutter/flutter/issues/58093

When the material spec for accessibility text scaling is available add reference to it in docs, to educate and explain the text scale factor cap of `1.34` for titles.
Repository: pytorch
Issue: [JIT] OrderedDict doesn't support custom objects
Labels: triage review,oncall: jit

There seems to be an inconsistency with how  `OrderedDict` is handled by torchscript compared to `dict`. 

Minimal example illustrating that `OrderedDict` doesn't seem to support custom objects, while dict do.
```python
import torch; from typing import Dict; from collections import OrderedDict

class C:
    def __init__(self, x):
        self.x = x

def f(x):
    # this fails with the below error
    d : Dict[str, C] = OrderedDict()
    # this works
    # d : Dict[str, C] = {}

    d['a'] = C(x)
    d['b'] = C(2 * x)
    return d

ff = torch.jit.script(f)
```

with the error message

```python
Traceback (most recent call last):
  File "tst.py", line 17, in <module>
    ff = torch.jit.script(f)
  File "/Users/fmassa/anaconda3/lib/python3.6/site-packages/torch/jit/__init__.py", line 1369, in script
    fn = torch._C._jit_script_compile(qualified_name, ast, _rcb, get_default_args(obj))
RuntimeError:
Variable 'd' is annotated with type Dict[str, __torch__.C] but is being assigned to a value of type Dict[str, Tensor]:
  File "tst.py", line 9
def f(x):
    d : Dict[str, C] = OrderedDict()
    ~ <--- HERE
    d['a'] = C(x)
    d['b'] = C(2 * x)
```

cc @suo
Repository: react-native
Issue: TextInput with TextAlign on iOS does not add ellipsis instead wraps
Labels: Platform: iOS,Component: TextInput,Needs: Environment Info,Needs: Attention

```
import React, { PureComponent } from 'react';
import {Text, TextInput, View} from 'react-native';

const App = () => {
  return (
    <View style={{flex: 1, justifyContent: 'center'}}>
      <View>
        <Text>Text Input without alignment</Text>
        <TextInput style={{padding: 10, margin: 20, borderColor: 'grey', borderWidth: 1}}/>
        <Text>Text Input with right alignment</Text>
        <TextInput textAlign={'right'} style={{padding: 10, margin: 20, borderColor:  'grey', borderWidth: 1}}/>
      </View>
      <TextInput/>
    </View>);
};

export default App;
```

Write some long text into the first field with spaces.
![image](https://user-images.githubusercontent.com/56955855/83871769-1f229500-a74a-11ea-9672-e6f92f28f274.png)

Write similar text into the second field.
![image](https://user-images.githubusercontent.com/56955855/83871839-3bbecd00-a74a-11ea-9f64-898de3a8a1e5.png)


Unfocus second input
Expected: both fields will have ellipsis at the end
Actual: second input with textAlign doesn't have ellipsis.

Android app works in a different way:
It never shows ellipsis but if you type a long string it always shows the end of it and never beginning. I guess it should move to begin when unfocused.

react: 16.11.0 => 16.11.0 
react-native: 0.62.1 => 0.62.1
Repository: terminal
Issue: Option to create desktop shortcuts to profiles
Labels: Issue-Feature,Help Wanted,Area-UserInterface,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

As a user, I'd like to be able to easily create desktop shortcuts that open a specific profile. This could be done e.g. via right clicking a profile in the profile dropdown and selecting an action "Create desktop shortcut".

For context, I use a Powershell Core profile to do software updates and a WSL shell to do some dev work and I currently cannot find a way to quickly run one of those; I always start the default Powershell profile and then manually open WSL and close Powershell which seems cumbersome.
<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: flutter
Issue: Google Maps Flutter Navigation Toolbar
Labels: c: new feature,p: maps,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

I can see that we have the ability to enable/disable the navigation toolbar (mapToolbarEnabled) on the map but even when enabled, the toolbar only appears when the red pin is clicked on. 

Can we have an option to force the navigation toolbar to always be showing when enabled, as it may not be obvious to the end user that they need to click on the red pin to navigate to Maps directly from there for directions?
Repository: node
Issue: Async Hooks and Streams
Labels: stream,async_hooks

Continuing a little bit from https://github.com/nodejs/node/issues/33723.

Do we need closer integration between async hooks and streams? In particular since `Stream.destroy` can be invoked from basically anywhere the `'close'` event can be emitted in a for user unexpected async scope (not sure yet about the correct terminology in async hooks context).

What currently seems to be the way to approach this is to monkey patch `destroy` after creating a stream, e.g.

```js
const stream = new Duplex(...)
stream.destroy = asyncResource.runInAsyncScope.bind(asyncResource, stream.destroy, stream)
```

Maybe would make sense to be able to provide a `asyncId` or `asyncTriggerId` (not sure of the difference yet) as a constructor argument?
Repository: flutter
Issue: Overscroll behavior should default to off for touch on ChromeOS
Labels: framework,f: scrolling,platform-chromebook,platform-web,P3,team-web,triaged-web

Go to gallery.flutter.dev on a ChromeOS machine.

If you scroll using the trackpad (2 finger scroll) no overscroll behavior is present.

However if you scroll using the touchscreen, you get the Android-style overscroll glow.

Everywhere else I can find in ChromeOS (web pages in Chrome, the application launcher, settings dialog) do not exhibit the overscroll glow behavior.

I expect if I tried an Android app on Chrome OS it would show overscroll however?

This is a tiny issue, just putting it on file.
Repository: go
Issue: runtime: read-only accessor for gcpercent
Labels: NeedsInvestigation,FeatureRequest,compiler/runtime

I would like to programmatically access the current value of `GOGC` in my program (for logging it, with various runtime stats).

For `GOMAXPROCS`, I can call `runtime.GOMAXPROCS(0)` to get the current value without changing it. However, for `GOGC`, I see no way of reading the value without writing. I could do a two-step call like

```
percent := debug.SetGCPercent(100)
debug.SetGCPercent(percent)
```

but I am worried about the disruption that this may cause in a program that is under load and that has a non-standard `GOGC` value in the first place.

The documentation for SetGCPercent says that a negative value will disable GC, however there is no documented effect for calling it with 0. Maybe this could be defined to just return the current value, like in GOMAXPROCS? This would just be a matter of making `runtime.setGCPercent` return early in this case.
Repository: go
Issue: net/http/cookiejar: strips additional information
Labels: NeedsInvestigation

https://github.com/golang/go/blob/50bd1c4d4eb4fac8ddeb5f063c099daccfb71b26/src/net/http/cookiejar/jar.go#L219

Is there a purpose to leave out everything apart from the name and value here?
I'd like to know how long time a cookie has left to live..
Repository: svelte
Issue: Error in bidi transitions when returning a function
Labels: awaiting submitter,stale-bot,temp-stale

https://svelte.dev/repl/283d750225684048b26cf6880dfcea2d?version=3.23.0
`Cannot read property 'r' of undefined`

https://github.com/sveltejs/svelte/blob/dba6e5efadb8aaf86ca25022cd3279bb4ea42434/src/runtime/internal/transitions.ts#L337-L342

`wait.then` resolves after `check_outros` meaning that `outros` will be the reassigned to its parent group, which is `undefined` in this case
Repository: terminal
Issue: Notification after a long running command finishes
Labels: Issue-Feature,Area-Extensibility,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

It would be awesome to add an option for a notification bubble or sound after a long running command. Long running command can be configurable but a sane default could be 10 seconds. 

The scenario for this would to switch users from a pull to push model. Without notifications, a user would have to constantly "pull" their terminal to see if their command is done. Switching to push removes the cognitive overhead of having to constantly pull and instead be pushed only once the command is done running.

# Current workarounds

* Run a script that creates a notification after the command is done: `long_command; notification.py`

## Extra asks

Beyond allowing for notifications, it would also be helpful if users were provided a hook. Here are some scenarios the hook can cover:

* Hitting an API to report the run length of the command (Useful for engineering systems)
* Changing the color of your smart LEDs (Think of all the things Makers could do!)
* Context aware notifications (If the script name contains 'foo' then do then, otherwise do that

# Other Terminal support

* iTerm has this as a feature: https://www.iterm2.com/documentation-shell-integration.html#:~:text=Alert%20on%20next%20mark,in%20another%20window%20or%20tab.

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: TypeScript
Issue: [javascript] Find all references when for module.exports = { foo: foo }
Labels: Bug


*TS Template added by @mjbvz*

**TypeScript Version**: 4.0.0-dev.20200605

**Search Terms**
- JavaScript
- find all references (f12)

---

Code

// main.ts
```
import { foo } from './lib.js';

foo();
```
// lib.js
```
function foo() {
	console.log("hello world")
}

module.exports = { foo: foo }
```
Run find all references on **foo()** in **main.js**

**Expected behavior:**
foo references in both files are returned.

**Actual behavior:**
Only references in main are returned

Also I created **jsconfig.json** on root project but still not work.

```
{
    "compilerOptions": {
        "target": "ES6"
    },
    "exclude": [
        "node_modules",
        "**/node_modules/*"
    ]
}
```

And many other examples:

```
{
    "compilerOptions": {
        "target": "esnext",
        "baseUrl": "./",
        "jsx": "react",
    },
    "include": [
        "./src/js/**/*"
    ],
}
```

I use react and javascript in actual project
Repository: flutter
Issue: MediaQueryData.viewInsets might not be the right thing to use on iOS keyboard
Labels: platform-ios,framework,f: material design,a: fidelity,f: cupertino,team-design,triaged-design

The default behavior for iOS keyboards might be closer to media query padding rather than a view inset. 

In an iOS app, such as iMessage, open the keyboard and scroll. The content will scroll behind the translucent keyboard. This doesn't happen by default in Flutter since our Scaffold and CupertinoScafford default to resizeToAvoidBottomInset=true. This makes it unlikely for any content to be behind the keyboard which loses the "frosted glass look and feel".
Repository: TypeScript
Issue: Add auto-completion results to CSSStyleDeclaration.{setProperty,removeProperty}
Labels: Suggestion,Awaiting More Feedback

## Search Terms

setProperty

## Suggestion

[`CSSStyleDeclaration.setProperty(propertyName, value, priority);`](https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleDeclaration/setProperty) is currently typed as `setProperty(property: string, value: string | null, priority?: string | undefined): void`. 
There is a specific set of defined properties in CSS: https://www.w3.org/TR/CSS/#properties It would be great if this specific list of properties could be added to the definition, such that auto-completion would show the allowed values.

(The same is true for https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleDeclaration/removeProperty so this feature request applies to that method as well)

For backwards compatible reasons (and to be spec-compliant), a `string` overload would remain. That's because the following is legal, albeit a noop:

```js
element.style.setProperty('non-existent', 'something');
```

## Use Cases

Improved editor experience for style APIs.

## Examples

With my cursor at `|`, ask for the auto-completions. The expected behavior would be to show the list of accepted properties, similar to how `document.createElement` works.
```
element.style.setProperty('|
```

## 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: pytorch
Issue: friend constexpr in templated struct loses constexpr-ness in nvcc
Labels: triaged

This fails to compile in nvcc:

```
template <typename T>
struct A {
  constexpr A(T x) : x_(x) {}
  constexpr bool equals(const A& other) { return x_ == other.x_; }
  friend constexpr bool func_equals(const A& self, const A& other) { return self.x_ == other.x_; }
  T x_;
};

constexpr bool ok(int a, int b) {
  return A<int>(a).equals(b);
}

constexpr bool bad(int a, int b) {
  return func_equals(A<int>(a), A<int>(b));
}
```

This results in the error:

```
test.cu: In function ‘constexpr bool bad(int, int)’:
test.cu:14:19: error: call to non-constexpr function ‘bool func_equals(const A<int>&, const A<int>&)’
   return func_equals(A<int>(a), A<int>(b));
        ~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~         
```

If you run with `--verbose --keep` and look at the cudafe, you can see that the constexpr is dropped

```
# 1 "test.cu"
template< class T>·
# 2
struct A {·
# 3
constexpr A(T x) : x_(x) { }·
# 4
constexpr bool equals(const A &other) { return (x_) == (other.x_); }·
# 5
friend inline bool func_equals(const A &self, const A &other) { return (self.x_) == (other.x_); }·
# 6
T x_;·
```

I've filed this as nvbug https://developer.nvidia.com/nvidia_bug/3010385

In the meantime, we MUST NOT define constexpr friend functions. It is usually simple enough to work around it some other way (define it as a method or a free function). An example of some constexpr friend functions that are affected by this are `c10::string_view` `operator==`.
Repository: flutter
Issue: in_app_purchase - cancel subscription and restore cancelled subscription
Labels: c: new feature,p: in_app_purchase,package,team-ecosystem,P3,triaged-ecosystem

Would it be possible to add to the in_app_purchase plugin the following functionalities?

- Cancel Subscription
- Restore Cancelled Subscription (When cancelled but not yet expired)

At the moment the user has to do those actions via the App Store / Google Play.
Repository: PowerToys
Issue: [Run][Calculator Plugin] Calculator Expansion
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

# Summary of the new feature/enhancement

Expand the calculator by implementing bit shifting, modulus operations, and bitwise operators like on macOS' Spotlight, as well as allowing an implicit multiplication when a number is next to a parenthesized number.

# Proposed technical implementation details (optional)

Examples:
- 5 << 4 * 2 = **1280**
- (24 >> 2) - 1 = **6**
- 5 % 3 = **2**
- 15 & 3 = **3**
- 26 | 5 = **31**
- 2(40) = **80**
Repository: PowerToys
Issue: [PowerRename] Add an option to reverse the order of files
Labels: Idea-Enhancement,Product-PowerRename

I need to be able to reverse filenames for automatic import into a program. My files are named as 3a, 3b, 3c, etc. as I don't know how many I am going to have to create, I need it to delete the letters (can be done with regex `[a-zA-Z]`) and then enumerate the items in reverse order, so 3c comes out as "3 (1)", 3b comes out as "3 (2)", etc. This would be really helpful and make my use case and anyone else who needs to do something like this so much faster.
Repository: godot
Issue: get_cell_autotile_coord gives the same information if the tile is at the position 0, 0 in the tileset or the cell doesn't have autotilling
Labels: enhancement,topic:core

**Godot version:**
3.2.1.stable.official

**OS/device including version:**
Windows10

**Issue description:**
The GDscript function get_cell_autotile_coord() returns a zero vector when the cell doesn't have autotilling. See documentation: https://docs.godotengine.org/en/stable/classes/class_tilemap.html#class-tilemap-method-get-cell-autotile-coord
What the function returns is a vector2 containing the coordinates of the tile in the tileset. But the first tile in the tileset is at the position (0, 0). So it's exactly the same as if the cell doesn't have autotilling.
So the function can return misleading information.

**Steps to reproduce:**
Execute the minimal project linked. You'll see that the cell at the coordinates (0, 0) get the same result with the get_cell_autotile_coord function as the cell (4, 0) even if it's an empty cell - so obviously no autotiling.

**Minimal reproduction project:**
[Issue_TileMap.zip](https://github.com/godotengine/godot/files/4739241/Issue_TileMap.zip)

I took the liberty to check the tile_map.cpp - if I may add a small contribution to the project.
Maybe the constant INVALID_CELL could be returned is both coordinates of the vector2 to handle this case:
![image](https://user-images.githubusercontent.com/48227025/83934358-73e00300-a77e-11ea-93cf-109bb76b5aa0.png)
Repository: pytorch
Issue: Switching from CPU build to CUDA build in conda environments is a bit tricky
Labels: module: docs,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->
Currently, it is a bit tricky to switch from CPU build to CUDA build. Users will sometimes forget to specify the cudatoolkit requirement and find out that they installed the CPU build. Then they will attempt to follow the steps on pytorch.org, that is `conda install -c pytorch cudatoolkit=x.x pytorch`. But actually that is not enough because `cpuonly` is still there.

## To Reproduce

Steps to reproduce the behavior:

1. `conda install -c pytorch cpuonly pytorch`
2. `conda install -c pytorch cudatoolkit=x.x pytorch`

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

Better user message. 

<!-- A clear and concise description of what you expected to happen. -->


cc @jlin27