sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: When an intent is received by the app, AppState receive a background state then an active state just after
Labels: Platform: Linux,API: AppState,Needs: Triage :mag:

### Description

When the app receive an Intent the AppState quickly change to background before come back to active instead of staying in "active" state.

Relevant sources in react native: 

- https://github.com/facebook/react-native/blob/8bd3edec88148d0ab1f225d2119435681fbbba33/ReactAndroid/src/main/java/com/facebook/react/modules/appstate/AppStateModule.java#L65-L81
- https://github.com/facebook/react-native/blob/8bd3edec88148d0ab1f225d2119435681fbbba33/ReactAndroid/src/main/java/com/facebook/react/bridge/LifecycleEventListener.java#L32-L49
- https://github.com/facebook/react-native/blob/8bd3edec88148d0ab1f225d2119435681fbbba33/ReactAndroid/src/test/java/com/facebook/react/modules/timing/TimingModuleTest.java

### Version

0.70

### Output of `npx react-native info`
```
info Fetching system and libraries information...
System:
    OS: Linux 5.19 Arch Linux
    CPU: (6) x64 Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
    Memory: 10.91 GB / 15.43 GB
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 18.8.0 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 8.19.1 - /usr/bin/npm
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 30, 31, 33
      Build Tools: 29.0.0, 29.0.2, 30.0.3, 31.0.0, 33.0.0
      System Images: android-30 | Android TV Intel x86 Atom, android-30 | Intel x86 Atom_64, android-30 | Google TV Intel x86 Atom
      Android NDK: 25.1.8937393
  IDEs:
    Android Studio: AI-212.5712.43.2112.8815526
  Languages:
    Java: 1.8.0_345 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.1.0 => 18.1.0 
    react-native: 0.70.0 => 0.70.0 
  npmGlobalPackages:
    *react-native*: Not Found
```

### Steps to reproduce

### Steps

1. Start the demo app (https://github.com/gritwyplay/ExempleAppState)
2. Send an intent ( `adb shell am start -a "android.intent.action.VIEW" -d test://test`)
3. Observe current app state in the app ("Current state is: xxxxxx")

### Expected

1. The App start
2. The intent is fired
3. The current state stay active

### Actual

1. As Expected
2. As Expected
3. The current state quickly change to "background" before come back to "active"




### Snack, code example, screenshot, or link to a repository

Demo app : https://github.com/gritwyplay/ExempleAppState
Repository: tensorflow
Issue: GPU memory usage depends on data size
Labels: stat:awaiting tensorflower,type:bug,comp:gpu,TF 2.9

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Bug

### Source

binary

### Tensorflow Version

2.6-2.10

### Custom Code

Yes

### OS Platform and Distribution

Linux Fedora 36

### Mobile device

_No response_

### Python version

3.9

### Bazel version

_No response_

### GCC/Compiler version

_No response_

### CUDA/cuDNN version

11.7

### GPU model and memory

RTX 2070, 8GiB

### Current Behaviour?


Training a small model on small batches runs out of GPU memory if the total amount of data is large.

The same code works fine on TF 2.5, but fails on 2.6, 2.7, 2.8, and 2.9.



### Standalone code to reproduce the issue


Here is a handy script: https://gist.github.com/Dapid/3f58697edf91c6610ed5e7b681db440f

In short, a tiny model is trained on a fixed array of data. If the total amount of data is small, it runs; otherwise, it crashes.

Running `python benchmark.py` works, but `python benchmark.py --big` doesn't. Using the `tf.data` API doesn't make a difference.



### Relevant log output

```shell
-09-06 10:52:22.131172: W tensorflow/core/common_runtime/bfc_allocator.cc:462] Allocator (GPU_0_bfc) ran out of memory trying to allocate 15.26GiB (rounded to 16384000000)requested by op _EagerConst
```

Defining `TF_GPU_ALLOCATOR=cuda_malloc_async`:

```shell
2022-09-06 10:58:16.939018: W tensorflow/core/framework/cpu_allocator_impl.cc:82] Allocation of 16384000000 exceeds 10% of free system memory.
2022-09-06 10:58:23.313713: E tensorflow/core/common_runtime/gpu/gpu_cudamallocasync_allocator.cc:288] gpu_async_0 cuMemAllocAsync failed to allocate 16384000000 bytes: CUDA error: out of memory (CUDA_ERROR_OUT_OF_MEMORY)
 Reported by CUDA: Free memory/Total memory: 1111293952/8369799168
2022-09-06 10:58:23.313737: E tensorflow/core/common_runtime/gpu/gpu_cudamallocasync_allocator.cc:293] Stats: Limit:                      6184304640
InUse:                        67126312
MaxInUse:                    201327628
NumAllocs:                          13
MaxAllocSize:                 67108864
Reserved:                            0
PeakReserved:                        0
LargestFreeBlock:                    0

2022-09-06 10:58:23.313745: E tensorflow/core/common_runtime/gpu/gpu_cudamallocasync_allocator.cc:56] Histogram of current allocation: (allocation_size_in_bytes, nb_allocation_of_that_sizes), ...;
2022-09-06 10:58:23.313749: E tensorflow/core/common_runtime/gpu/gpu_cudamallocasync_allocator.cc:59] 4, 5
2022-09-06 10:58:23.313753: E tensorflow/core/common_runtime/gpu/gpu_cudamallocasync_allocator.cc:59] 8, 2
2022-09-06 10:58:23.313755: E tensorflow/core/common_runtime/gpu/gpu_cudamallocasync_allocator.cc:59] 1028, 1
2022-09-06 10:58:23.313758: E tensorflow/core/common_runtime/gpu/gpu_cudamallocasync_allocator.cc:59] 16384, 1
2022-09-06 10:58:23.313761: E tensorflow/core/common_runtime/gpu/gpu_cudamallocasync_allocator.cc:59] 67108864, 1
```

</details>
Repository: material-ui
Issue: [Rating] Unable to properly navigate using Arrow keys in Safari browser
Labels: bug 🐛,component: rating,browser: Safari

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Only for Keyboard Users, I am trying to access the rating component on the safari browser with arrow keys but I cannot properly navigate between stars similar to the chrome browser. 
![safari](https://user-images.githubusercontent.com/53289809/188597592-b136ca6b-c6ca-4a6f-a74c-0f3836cb27b4.png)



### Expected behavior 🤔

This navigation should work normally in the Chrome browser. So it should have similar behaviour in the safari browser.
![chrome](https://user-images.githubusercontent.com/53289809/188597698-a4173f86-c0e0-4860-bf7d-7da7f493df81.png)


### Steps to reproduce 🕹

Steps:

1. Open Rating component on Mac OS + Safari browser
2. Press the Tab key until reached the Rating component
3. Press down/right arrow key to select stars
4. Navigation between stars did not start with the right arrow key and did not behave similarly like chrome


### Context 🔦

I was using this component and this issue comes into the picture while accessibility testing.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
     System:
    OS: macOS 12.5.1
  Binaries:
    Node: 16.17.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 8.18.0 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 104.0.5112.101
    Edge: Not Found
    Firefox: Not Found
    Safari: 15.6.1
  npmPackages:
    @types/react: 16.9.15 => 16.9.15 
    react: 16.12.0 => 16.12.0 
    react-dom: 16.12.0 => 16.12.0 
    typescript: 4.2 => 4.2.4 

```
</details>
Repository: vscode
Issue: explicit save in the results view should trigger "accept merge" action
Labels: under-discussion,merge-editor

<!-- ⚠️⚠️ 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. -->

With the new "Resolve Conflicts" visualization mode, the previous capability of marking a file with conflicts as an "accepted merge" using an "explicit save" command (i.e. CMD + S on Mac OS) seems to have been lost. It makes the process more complex and slower because you need to click the "Merge" button continuously on the UI.
Repository: node
Issue: Publish `exports` and `imports` implementations as separate module(s)
Labels: module,feature request,esm,never-stale

### What is the problem this feature will solve?

Projects implementing support for module resolution have to add support for the quite advanced `exports` and `imports` fields in package.json.

https://nodejs.org/api/packages.html#exports
https://nodejs.org/api/packages.html#imports

Examples of projects that have done this are Webpack, TypeScript, Jest (only `exports`, not `imports`), Yarn and probably more. AFAIK neither Rollup, Parcel or Metro (to name some bundlers) have support.

### What is the feature you are proposing to solve the problem?

If the algorithm Node uses internally was published as a separate module, I hope (and believe) more projects would be able to add support more readily, and that ecosystem compatibility would improve as a result.

I think part of the reason is the complexity in supporting the algorithm needed, particularly with subpath exports, wildcards and conditionals. E.g. https://github.com/browserify/resolve/issues/222 is stuck, and https://github.com/facebook/jest/issues/9771 took a _long_ time.

Prior art for externalizing parts of Node publishing [`cjs-module-lexer`](https://github.com/nodejs/cjs-module-lexer) separately, which means Jest could implement the same feature as node itself when importing CJS from ESM (via `vm` API).

---

Note that this is _not_ a request for the full `require` or ESM resolution algorithm. This is solely a request for "given this `exports`/`imports`, this specifier and these conditions, what path does it map to" - no FS access/lookups at all. API similar to https://github.com/lukeed/resolve.exports makes sense to me.

### What alternatives have you considered?

Jest (and Yarn) currently use https://github.com/lukeed/resolve.exports to avoid having to implement all the resolution. It currently does not support `imports` (https://github.com/lukeed/resolve.exports/issues/14).
Repository: go
Issue: x/net/ipv{4,6}: adopt net/netip address types
Labels: Proposal,Proposal-Accepted

The `x/net/ipv{4,6}` packages currently use `net.IP` and `net.Addr` types everywhere, with all the performance issues that the new types in the `net/netip` package were designed to resolve. In particular, the performance sensitive function `ReadBatch` must allocate the returned source addresses on every call (see related #26838).

In order to introduce this without breaking changes, parts of the API needs to be duplicated, analogous to, for example,  `net.ReadFromUDPAddrPort` added in go-1.18.
To avoid too much API bloat, it might be sufficient to implement this for performance sensitive functions like `Read/WriteBatch`.

Losely related to proposal #45886; when a fast `net.Read/WriteUDPMsgs` functionality is available, we may simply no longer need `x/net.Read/WriteBatch` for some use cases.
Repository: PowerToys
Issue: 希望在键盘管理器中加一个屏幕键盘，能在屏幕上实时显示我按了哪个键
Labels: Idea-Enhancement,Idea-New PowerToy,Product-Keyboard Shortcut Manager

### Description of the new feature / enhancement

不同于Windows自带的屏幕键盘，我想要的功能是当我按下键盘某个键，在屏幕中心就能显示这个按键

### Scenario when this would be used?

当我分享屏幕时，当我给别人演示讲解某个软件。我按下某个操作按键，我希望观看我屏幕的人知道我按下了哪个按键操作

### Supporting information

_No response_
Repository: flutter
Issue: Nested Navigator does not allow swipe to exit when using `CupertinoPageRoute`
Labels: framework,f: cupertino,f: routes,has reproducible steps,P2,found in release: 3.3,found in release: 3.4,team-design,triaged-design

Github demo: https://github.com/suesitran/flutter_navigation_demo

1. Execute `flutter run` on the code above 
2. In first page, click on 'Go to multitab page'
3. In Page 1, click on 'Go to sub page'
4. In sub-page, swipe from left to right to return to Page 1

**Expected results:** 
App returns to Page 1

**Actual results:**
- in iOS devices, the app returns to the first Single page
- in Android device, unable to swipe to return to previous page
Repository: vscode
Issue: Slightly de-clutter the merge editor UI
Labels: polish,under-discussion,merge-editor

There has been user feedback to de-clutter the merge editor UI. For example https://twitter.com/shamssahal/status/1567094628515737601 
And I agree. Though I am not sure what can we remove.

One thing that comes to mind - why don't we hide the editor area where folding is? In the Incoming and Current view, we already do not support folding and with removing this we would save on screen real estate.

Just to be clear, the area between line numbers and where the text / conflict starts

![Screenshot 2022-09-06 at 14 55 36](https://user-images.githubusercontent.com/1926584/188640803-cc72d79e-6f37-48e2-88e4-938ea0706c56.png)

Another thing - auto resolved conflicts are too strong. Can we make those checkboxes and the border around those conflicts  more subtle? 

Other ideas welcome

fyi @daviddossett 

![Screenshot 2022-09-06 at 14 56 46](https://user-images.githubusercontent.com/1926584/188641006-9094b580-ab63-4e65-8fc1-5f13d5d06830.png)
Repository: TypeScript
Issue: Type narrowing of generic types in control flow analysis
Labels: Needs Investigation

# Bug Report

Hello,

### 🔎 Search Terms

type narrowing, generic types, control flow analysis

### 🕗 Version & Regression Information

(see Playground) When trying to narrow generic types (unions), the control flow analysis is not aware of the narrowing. I also see that this PR: https://github.com/microsoft/TypeScript/pull/43183 was supposed to address this.

Please keep and fill in the line that best applies:
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about type narrowing

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/MYewdgzgLgBAkgOTgFTgQQDIH0DKy3ICiMAvDAN4BQMMAjAFwwDkUAptLUwDTUwBMjFuyh9ulAL4BuSlACeAB1YwcUAIZtSMOYpAAzeElSZc+ItMqhIsaOtYAlVgBMArsFYAnTQB5kCpawAPNjBHCBgAa1ZZPWU1NgA+AApeGzZGFVseGlVgKABLcEZyLT9GX0VJGAA3VQAbZ1ZGaHc8sABzGHEYAB8KEsVBYFrWVXcmSpr6xpgwZwBbACMPTp4ASlJ4il48-USc-PAAOm0lEjPmIZGx9aoaGgB6e5h9grBDyYaYPLCAImbWjq9WaLDw-LgwBbOawACxAzlqjghSh+wKW7h+vBo7lYUGc7jAz1yr3edQa0ho4kovGxuPxWzuMEOTNSrCydwA2i8jicALqMLlvD6s3hSCTmFkOFxudyJRAodDYPAEQjg4onQbDUbcaqk6YABk6q0kQA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
const INITIAL_STATE = {
  1: 'test1',
  2: 'test2',
};
type State = typeof INITIAL_STATE;

const stateReducer = <Type extends keyof State>(
  state: State,
  action: { type: Type; value: string } | { type: 'clear'; value: number },
) => {
  if (action.type === 'clear') {
    // action.value is "string | number", but should be "number"
    return action.value;
  }

  return {
    ...state,
    [action.type]: action.value,
  };
};

stateReducer(INITIAL_STATE, { type: 'clear', value: 0 });
```

### 🙁 Actual behavior

`action.value is "string | number"`

### 🙂 Expected behavior

but should be "number"

Thanks in advance!
Repository: pytorch
Issue: Tensor Subclass that doesn't require grad may wrap a Tensor subclass that requires grad
Labels: triaged,tensor subclass

From a practical perspective, this only happens today in functorch. 

## The Problem

We have some composite operations that check if a Tensor requires grad. If it does, then it goes down one path; if it doesn't, then it goes down a "non-differentiable" path.

In functorch, we can have Tensor subclasses that do not require grad that wrap Tensors that do require grad. Unfortunately, the composite operations check if a Tensor requires grad and return false on the Tensor subclass, causing it to go down a non-differentiable path.

See https://github.com/pytorch/pytorch/pull/84137 for example. This problem is related to composite compliance: https://github.com/pytorch/pytorch/issues/69991

cc @ezyang
Repository: godot
Issue: CRASH no errors
Labels: bug,topic:core,needs testing,crash

### Godot version

4.0alpha15

### System information

Windows 10, RX 550, Vulkan api 1-2-0

### Issue description

Godot Engine v4.0.alpha15.official.432b25d36 - https://godotengine.org
Vulkan API 1.2.0 - Using Vulkan Device #0: AMD - Radeon RX550/550 Series

if size > Vector2i(170, 170):
 Crash();


### Steps to reproduce

--• Download my script
----• <b>Change .txt to .gd </b>
------• Add script to Node2D

### Minimal reproduction project

![2022-09-06_18-58-15](https://user-images.githubusercontent.com/88548189/188654855-27dd2685-9415-47ff-949d-1308441d14ef.png)

Download: [generator-alpha-1.1 (1).txt](https://github.com/godotengine/godot/files/9508135/generator-alpha-1.1.1.txt)
Repository: angular
Issue: Angular Dev Tools - Can't use when 3rd party adds empty div to DOM
Labels: state: has PR,P4,area: devtools

### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

No

### Description

We rely on several third party tools in our app for our marketing team and help desk, etc.  

App Cues, Segment, Intercom, and more.

At some point, one of them adds a couple of empty divs to the dom and this crashes/prevents Angular Dev Tools from working.

Here is a link to the open issue from the old repo.  Our entire dev team would love to use these dev tools, but it's not possible.

https://github.com/rangle/angular-devtools/issues/910




### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
polyfills.js:22576 Uncaught Error: ASSERTION ERROR: The provided value must be an instance of a DOM Node but got [object HTMLScriptElement]
    at throwError (vendor.js:215325:9)
    at assertDomNode (vendor.js:215331:5)
    at getLContext (vendor.js:224057:18)
    at getDirectives (vendor.js:240462:19)
    at kt (render-tree.ts:15:26)
    at render-tree.ts:52:23
    at NodeList.forEach (<anonymous>)
    at kt (render-tree.ts:51:28)
    at render-tree.ts:52:23
    at NodeList.forEach (<anonymous>)
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 14.2.1
Node: 16.14.2
Package Manager: npm 8.5.0 
OS: darwin arm64

Angular: 14.2.0
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, material, material-moment-adapter
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1402.1
@angular-devkit/build-angular   14.2.1
@angular-devkit/core            14.2.1
@angular-devkit/schematics      12.2.18
@angular/cli                    14.2.1
@angular/flex-layout            14.0.0-beta.40
@schematics/angular             14.2.1
rxjs                            7.5.6
typescript                      4.8.2
webpack                         5.74.0
```


### Anything else?

_No response_
Repository: storybook
Issue: Extending dev server still possible? How? Documentation missing / Zombie code?
Labels: bug,needs triage

**Describe the bug**

At one point in Storybook's development, there appeared to be an opportunity to customize or extend the web server. In our case it is about the extension with two HTTP proxy entries:

`main.ts`: 

```ts
const { createProxyMiddleware } = require('http-proxy-middleware');

...

"extendServer": (app) => {
  let target = 'https://epxportalassetsdev.blob.core.windows.net/sw-demo/';

  app.use(
    '/assets',
    createProxyMiddleware({
      target: target,
      changeOrigin: true,
      pathRewrite: { '^/assets/': '/' },
    })
  );
},

...
```

In the code there is an option "extendServer" (`storybookDevServer()`), which can still be found partially online. However, it is not present in the official documentation. An entry of this function in `main.js` seems to be ignored according to my analysis. Typical top-level configurations that are observed seem to be `smokeTest`, `configDir`, `ignorePreview`, etc. These are all outside of the storybook configuration through `main.js` and seem to be made configurable exclusively through the CLI.

Extending the server via a CLI option makes little sense in my opinion. After all, a few lines of real code are needed here. 

Is this code a leftover? Then it should be removed, right? Otherwise it would be really helpful if this would be implemented. I could provide a PR for this, just want to ask first if I understood everything correctly and how the solution should look like.

Current code: (`core/lib/core-server/src/dev-server.ts`, line ~106)

```ts
if (typeof options.extendServer === 'function') {
  options.extendServer(server);
}
```

Suggested code:

```ts
if (typeof core.extendServer === 'function') {
  core.extendServer(app);
}
```

In the suggested code I changed `options` => `core` to access the core configuration from `main.js`. Furthermore, I used the variable `app` instead of `server` to really get to the original web server configuration.


**To Reproduce**

Not feasible in this case.

**System**

Environment Info:

  System:
    OS: macOS 12.5.1
    CPU: (20) arm64 Apple M1 Ultra
  Binaries:
    Node: 16.16.0 - /opt/homebrew/opt/node@16/bin/node
    Yarn: 1.22.15 - /opt/homebrew/opt/node@16/bin/yarn
    npm: 8.11.0 - /opt/homebrew/opt/node@16/bin/npm
  Browsers:
    Chrome: 104.0.5112.101
    Firefox: 98.0.2
    Safari: 15.6.1
Repository: vscode
Issue: Comments: Go to Next Comment Thread *in Files*
Labels: feature-request,comments

The design of `Go To Next Comment Thread` was discussed in https://github.com/microsoft/vscode/issues/110408. The command jumps to the next comment in the same file. Quite often, code review comments are spread among multiple files. It would be useful to be able to jump to the next comment, even when it's in a different file.

I notice there are two commands for the problems:
* `Go to Next Problem in Files (Error, Warning, Info)`
* `Go to Next Problem (Error, Warning, Info)`

So we could go for a similar approach. As mentioned in https://github.com/microsoft/vscode/issues/127473, being able to jump to the next **unresolved** comment would be very nice.

I'm not sure how many commands we should add, but what I'd find the most useful is "Go to Next Unresolved Comment Thread in Files". The workflow would be just like F8: jump to the next unresolved comment, resolve it, and iterate until every is resolved.
Repository: flutter
Issue: Specify `fontFamily` and/or `fontFamilyFallback` for 2021 text styles
Labels: framework,f: material design,a: typography,team-design,triaged-design

Per the [Material spec](https://m3.material.io/styles/typography/type-scale-tokens), we should investigate specifying `fontFamily` and/or `fontFamilyFallback` for 2021 text styles. We should also consider using Noto, which "is used as a “fallback” font, when a language is unsupported." ([Noto guidance](https://material.io/design/typography/language-support.html#noto-guidance))

Tokens are available for the text styles

cc @darrenaustin