sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Mouse Utilities: mouse cursor to reflect current keyboard layout / input method
Labels: Needs-Triage

### Description of the new feature / enhancement

Windows support multiple keyboard layouts / input methods. Users can cycle through them by **Windows logo key + Space bar**. Current keybaord layout status is shown on the Taskbar. Sometimes taskbar will be hidden or the status is hardly noticable. This feature would greatly improve working efficiency: users don't have to check the current input method every time before they input any text.

Mouse Utilities could change the cursor color or its appearance to reflect the current keyboard layout / input method. And some input method also could be switched off, like Chinese input method, by **Ctrl + Space bar**. That makes the Chinese input method output English (the current status is still Chinese input method). In this case, Mouse Utilities should also reflect this Chinese input method off status.

### Scenario when this would be used?

Every day, every time, whenever users want to input any a bit text. Users won't have to check the current input method / keyboard layout status before they want to input text.

### Supporting information

[Change your keyboard layout - Microsoft Support](https://support.microsoft.com/en-us/windows/change-your-keyboard-layout-245c49b8-f856-7fd7-2cf5-41e54c66f5b3)
[Keyboard shortcuts in Windows - Microsoft Support](https://support.microsoft.com/en-us/windows/keyboard-shortcuts-in-windows-dcc61a57-8ff0-cffe-9796-cb9706c75eec)

**Ctrl + Spacebar** Turn the Chinese input method editor (IME) on or off.
**Windows logo key + Shift + Spacebar** Cycle backwards through language and keyboard layout.
**Windows logo key + Spacebar** Switch input language and keyboard layout.
Repository: node
Issue: Multiple require and clear-module module files lead to memory explosion
Labels: memory

### Version

v18.12.0

### Platform

23; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000 arm64

### Subsystem

_No response_

### What steps will reproduce the bug?

Multiple require and clear-module module files lead to memory explosion and eventually lead to OOM


### How often does it reproduce? Is there a required condition?

test file：https://cdnjs.cloudflare.com/ajax/libs/three.js/0.155.0/three.js
need Three-party module： clear-module

### What is the expected behavior? Why is that the expected behavior?

Memory does not show a large increase

### What do you see instead?

code：

```js
const https = require('https');
const fs = require('fs');
const path = require('path');
const { getHeapStatistics } = require('node:v8');
const clearModule = require('clear-module');

const assetsUrl = 'https://cdnjs.cloudflare.com/ajax/libs/three.js/0.155.0/three.js'; // 196k

function requireAndClear(filepath) {
  console.log('start===', getHeapStatistics());
  for (let i = 0; i < 100; i++) {
    const module = require(filepath);
    clearModule(filepath);
  }
  console.log('end===', getHeapStatistics());
}
function download(url) {
  const filepath = path.join(__dirname, 'three.js');
  https.get(url, function (res) {
    const writeStream = fs.createWriteStream(filepath);
    res.pipe(writeStream);
    writeStream.on('finish', function () {
      writeStream.close();
      requireAndClear(filepath);
      console.log('download finished');
    });
  });
}
download(assetsUrl);
```

result after run：**total_heap_size increased by 345M**。filesize[196kB]，require and clear 100times，**3.45M growth each time on average.**

```
start=== {
  total_heap_size: 7897088,
  total_heap_size_executable: 524288,
  total_physical_size: 8093696,
  total_available_size: 4338774048,
  used_heap_size: 6256552,
  heap_size_limit: 4345298944,
  malloced_memory: 254128,
  peak_malloced_memory: 699824,
  does_zap_garbage: 0,
  number_of_native_contexts: 1,
  number_of_detached_contexts: 0,
  total_global_handles_size: 8192,
  used_global_handles_size: 3424,
  external_memory: 3104637
}
end=== {
  total_heap_size: 370114560,
  total_heap_size_executable: 3407872,
  total_physical_size: 353484800,
  total_available_size: 4014804888,
  used_heap_size: 317174112,
  heap_size_limit: 4345298944,
  malloced_memory: 270440,
  peak_malloced_memory: 3199416,
  does_zap_garbage: 0,
  number_of_native_contexts: 1,
  number_of_detached_contexts: 0,
  total_global_handles_size: 16384,
  used_global_handles_size: 9824,
  external_memory: 7083505
}
```

### Additional information

How to completely clear after nodejs dynamic require module.
Repository: pytorch
Issue: Branch name in double quotes ""
Labels: module: ci,triaged

### 🐛 Describe the bug

TBD

### Versions

It is not a bug per say, but a issue we are facing. We see that a new branch has been added with double quotes in it name: "serialize".
We have forked the pytorch repository and our internal automation of fetching the latest code is broken due to branch name in quotes. 
Just curious, if there any guidelines about branch name?

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: stable-diffusion-webui
Issue: [Bug]: 
Labels: asking-for-help-with-local-system-issues

After generating several consecutive images, the Linux server crashes directly and cannot access it, requiring a reboot
Repository: storybook
Issue: [Bug]: use of isomorphic-unfetch breaks storybook-next build
Labels: bug,needs triage

### Describe the bug

When importing `isomorphic-unfetch@5.0.0` (latest) into a Component that is to be displayed in a Story in `storybook`, the `storybook` build breaks with:

```
Module not found: Error: Can't resolve 'unfetch' in '/Users/martaver/Projects/repro/node_modules/isomorphic-unfetch'
```
and several:
```
odule build failed: UnhandledSchemeError: Reading from "node:buffer" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
```
of varying imports.

This might be simply a problem with `isomorphic-unfetch`, e.g. I know there is a problem with exports in `unfetch`:
https://github.com/developit/unfetch/issues/162
https://github.com/developit/unfetch/pull/164

However, since the same build error does NOT occur in `next`'s build, I thought I'd flag this for the `storybook` team, since this suggests that `storybook` is doing something different in its build to `next` and I was under the impression that `storybook` should be utilising the same build configuration as `next`.

### To Reproduce

https://github.com/cleric-sh/repro/tree/next-storybook-isomorphic-unfetch

Note the `repro` is in branch `next-storybook-isomorphic-unfetch`!

Run `npm run storybook` and check out the `Button` component. It imports `isomorphic-unfetch` without using it, which causes the aforementioned build errors.

### System

```shell
Environment Info:

  System:
    OS: macOS 12.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 16.20.1 - ~/.config/nvm/versions/node/v16.20.1/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.19.4 - ~/.config/nvm/versions/node/v16.20.1/bin/npm
  Browsers:
    Chrome: 115.0.5790.114
    Safari: 15.5
  npmPackages:
    @storybook/addon-essentials: 7.1.1 => 7.1.1 
    @storybook/addon-interactions: 7.1.1 => 7.1.1 
    @storybook/addon-links: 7.1.1 => 7.1.1 
    @storybook/addon-onboarding: ^1.0.8 => 1.0.8 
    @storybook/blocks: 7.1.1 => 7.1.1 
    @storybook/nextjs: 7.1.1 => 7.1.1 
    @storybook/react: 7.1.1 => 7.1.1 
    @storybook/testing-library: ^0.2.0 => 0.2.0
```


### Additional context

_No response_
Repository: flutter
Issue: [Impeller] Degraded performance when using Impeller on Intel MacBook Pro 2015
Labels: engine,a: animation,c: performance,platform-mac,a: desktop,perf: memory,has reproducible steps,P2,e: impeller,team-engine,triaged-engine,found in release: 3.13

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

1. This is tested on my old Intel MacBook Pro 2015
  ```
  MacBook Pro (Retina, 15-inch, Mid 2015)
2,2 GHz Quad-Core Intel Core i7
16 GB 1600 MHz DDR3
Intel Iris Pro 1536 MB
```
3. Run simple Flutter with some kind of animation and Impeller enabled (see code sample)

### Expected results

App without Impeller enabled works pretty smooth and keeps fairly low memory usage (see screen recording `skia.mov`)

### Actual results

High memory usage (up to 1.2GB in this example) and overall stutter of the whole desktop, it's most noticeable when app window is maximized (see screen recording `impeller.mov`), also Flutter dev tools report no issues with the frame rate

### Code sample

<details><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: Column(
            mainAxisAlignment: MainAxisAlignment.center,
            children: <Widget>[
              Transform.scale(
                scale: 10.0,
                child: const CircularProgressIndicator(),
              ),
            ],
          ),
        ),
      ),
    );
  }
}
```

</details>


### Screenshots or Video

<details>
<summary>Screenshots / Video demonstration</summary>

https://github.com/flutter/flutter/assets/3144291/d506cd1b-22fc-45e5-9064-b95ed8c921a3


https://github.com/flutter/flutter/assets/3144291/09f5e303-27c9-4b75-aa36-b132426668a8


</details>






### Logs

_No response_

### Flutter Doctor output

<details><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 3.13.0-16.0.pre.42, on macOS 12.6.8 21G725 darwin-x64, locale en-PL)
[✗] Android toolchain - develop for Android devices
    ✗ ANDROID_HOME = /Users/piotrek/Library/Android/sdk
      but Android SDK not found at this location.
[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] VS Code (version 1.80.2)
[✓] Connected device (2 available)
[✓] Network resources
```

</details>
Repository: pytorch
Issue: `softmax` to handle dimensions comprised of `-inf`
Labels: module: nn,triaged

### 🚀 The feature, motivation and pitch

Currently `softmax` handles `-inf` in most of the cases, for example:

```python
>>> x = torch.tensor([-float('inf'), 1])
>>> x.softmax(-1)
tensor([0., 1.])
>>> x.cuda().softmax(-1)
tensor([0., 1.], device='cuda:0')
```

However, once the normalized dimension is comprised of solely `-inf`, there is an issue:
```python
>>> x = torch.tensor([-float('inf')] * 2)
>>> x.softmax(-1)
tensor([nan, nan])
>>> x.cuda().softmax(-1)
tensor([nan, nan], device='cuda:0')
```

I understand we get it because `inf - inf = nan`, but why not assume that `softmax` is computed in the limit?
In such a case `softmax` should return a uniform distribution. This case is quite easy to detect since `max == -inf` will imply a uniform distribution.

Issues for more context:
https://github.com/pytorch/pytorch/issues/25110
https://github.com/pytorch/pytorch/issues/103749
https://github.com/pytorch/pytorch/issues/103963


cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: neovim
Issue: Cannot abort file writing using Lua autocommands
Labels: needs:discussion,lua,events

### Problem

When saving a file, the function called in BufWritePre on lua throws an error, but the file is still saved.
For example

`hoge.lua`
```lua:hoge.lua
vim.api.nvim_create_autocmd('BufWritePre', {
  callback = function()
    error('hoge')
  end
})
```
This function throws an error, but the buffer is written to the file.

also the below codes acts the same
```lua:hoge.lua
vim.cmd([[
	au BufWritePre * throw 'hoge' 
]])
```

```lua:hoge.lua
vim.api.nvim_create_autocmd('BufWritePre', {
     command = "throw 'error'"
})
```

However, when we use vimscript, the thrown error prevents the buffer written to the file
Ex. `hoge.vim`
```vim
au BufWritePre * throw 'hoge'
```

### Steps to reproduce

1. Define the functions I wrote above
2. save some buffers to the file

### Expected behavior

When the au functions throw errors, the buffers won't be written to the file

### Neovim version (nvim -v)

NVIM v0.10.0-dev-753+g4a06de40e

### Vim (not Nvim) behaves the same?

not at 9.0.1650

### Operating system/version

macOS 13.14.1

### Terminal name/version

wezterm

### $TERM environment variable

xterm-256color

### Installation

brew
Repository: next.js
Issue: Incorrect metadata fetching from Google Fonts causes some fonts do not have expected subsets
Labels: bug,Font (next/font)

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PREEMPT_DYNAMIC Thu, 27 Jul 2023 22:02:18 +0000
    Binaries:
      Node: 20.4.0
      npm: 9.8.1
      Yarn: 1.22.19
      pnpm: 8.6.11
    Relevant Packages:
      next: 13.4.13-canary.12
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Font optimization (next/font)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/myl7/next-missing-font-subsets-mre

### To Reproduce

- Change the line [`subsets: ['latin']`](https://github.com/myl7/next-missing-font-subsets-mre/blob/f8b395881b67921e6f47e724d1cadf833e39a932/app/layout.tsx#L7) to `subsets: ['chinese-simplified']`
- Run `npm run build`, which will fail

### Describe the Bug

`@next/font/google` fetches from Google Fonts to get the font metadata (in advance and included in the distribution) so that it can download needed fonts when building to serve them locally after deployed (correct me if wrong).

But to decide which subsets should be loaded, `@next/font/google` get the information that which subset is the WOFF file for [from the comments](https://github.com/vercel/next.js/blob/3c84b3ac99e143cec08181616ec89d393e8dbf41/packages/font/src/google/find-font-files-in-css.ts#L16) in the Google Fonts CSS.
It is only true for some fonts like [Noto Sans Osage](https://fonts.googleapis.com/css2?family=Noto+Sans+Osage&display=swap) but not for others like [Noto Serif SC](https://fonts.googleapis.com/css2?family=Noto+Serif+SC&display=swap).
For the latter one, the comments in the Google Fonts CSS are in the form like `[4]`, `[5]` to indicate the Unicode range, other than a subset name.
That causes [the generated metadata file](https://github.com/vercel/next.js/blob/3c84b3ac99e143cec08181616ec89d393e8dbf41/packages/font/src/google/font-data.json#L9157) to contain fonts with incorrect subsets, mostly `["latin"]` which I think is the default value.

It does not seem to avoid loading the font completely, but instead seems to load all subsets of the fonts (not so sure). However, while still working, the name of "latin" should still be confusing.

### Expected Behavior

Perfect solution: Get the correct subset information from somewhere as the metadata file included in the package.
But other than the comments, I have not found it anywhere that contains the information.

Alternatively, an additional default value can be added to indicate that the font can only be fully loaded, other than the current "latin".

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

Mozilla Firefox 115.0.3

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

Vercel
Repository: excalidraw
Issue: align action removes elements from containing frame
Labels: bug,frames

On align action, elements that end up being moved are removed from the containing frame.

via @wietsevenema

![align_out_of_frame](https://github.com/excalidraw/excalidraw/assets/5153846/dc66ce8d-7640-41de-adcf-2d7f45419073)
Repository: angular
Issue: Allow to fallback to default ngSrcset in NgOptimizedImage when binded to falsy value (and combine other props) 
Labels: area: common,common: image directive

### Which @angular/* package(s) are relevant/related to the feature request?

common

### Description

## Conditional ngSrcset
Currently it's impossible to implement conditional behavior of **ngSrcset** (and probably other props as well).
Consider following example:
```
<img [ngSrc]="path" [height]="height" [width]="width"
        [ngSrcset]="!crop ? '16w, 48w, 96w, 128w, 384w, 640w, 750w, 828w, 1080w, 1200w, 1920w' : ''" [loaderParams]="{crop, width, height}">
```
We want to apply srcset only when ```crop``` is not ```true``` otherwise we want the default behavior of NgOptimizedImage like no ngSrcset was stated, from docs: 
```
A srcset can be generated automatically from the image's width and height attributes with no further input required.

Example srcset generated: <[img](https://angular.io/api/common/NgOptimizedImage) ... srcset="image-400w.jpg 1x, image-800w.jpg 2x">
```

Currently this fails with an following error:
```
ERROR Error: NG02952: The NgOptimizedImage directive (activated on an <img> element with the `ngSrc="..."`) has detected that `ngSrcset` has an invalid value (``). To fix this, change the value to a non-empty string.
```

## Combination of other properties
The problem is not exclusive to ngSrcset property of NgOptimizedImage as for example following is not possible neither due combination of properties ```priority``` and ```loading``` even when priority is falsey:
This throws error even when should be theoretically possible:
```
<img [priority]="false" [loading]="loading" [ngSrc]="path" [height]="height" [width]="width">
```
In the end to combine dynamic resolution of ```priority``` and ```loading``` and ```ngSrcSet``` you have to write complex multiconditionals (when you consider these two usecases then you need 4 img elements).

### Proposed solution

- Allow ```ngSrcset``` to take some or at least one "falsey" value ("", null, undefined) that would result in default behavior as stated in the docs - that is srcset for different densities ```srcset="image-400w.jpg 1x, image-800w.jpg 2x"```
- Allow ```priority``` input be set together with ```loading``` and if ```priority``` is an empty string ```<img priority>``` or true ```<img [priority]="true">``` ignore user-defined ```loading``` parameter. If ```<img [priority]="false" loading="lazy">``` then ```loading``` parameter should take effect.
- Allow ```loading``` input to take falsy value and in that case fallback to default behavior ("lazy" when priority=false and "eager" when priority=true)

### Alternatives considered

Currently needed behavior is possible only by explicitly writing redundant ```img``` elements:
```
      <img *ngIf="crop" [ngSrc]="path" [height]="height" [width]="width"  [loaderParams]="loaderParams">
      <img *ngIf="!crop " [ngSrc]="path" [height]="height" [width]="width" [loading]="loading" ngSrcset="16w, 48w, 96w, 128w, 384w, 640w, 750w, 828w, 1080w, 1200w, 1920w"  [loaderParams]="loaderParams">
```
Repository: rust
Issue: strip = "symbols" doesn't work when cross-compiling from linux to macOS
Labels: A-linkage,O-macos,A-cross,T-compiler,C-bug

Currently, when compiling for macOS with `-C strip=symbols`, rustc will try to invoke `strip` on the output binary to remove its symbols. This, unfortunately, fails when cross-compiling from linux, as the `strip` binary on linux only understands ELF files and will choke on the mach-o. This results in the following warnings in the build logs, and an unstripped binary output:

```
warning: stripping debug info with `strip` failed: exit status: 1
  |
  = note: /usr/bin/strip: /home/roblabla/repro/target/x86_64-apple-darwin/release/deps/repro-19371802bd981e48: file format not recognized
```

Ideally, rustc should either:

1. Use a cross-target stripper, such as `llvm-strip` (which is currently packaged in rustup as part of llvm-tools-preview, CC #85658)
2. Allow the user to configure which strip utility it will use (which could then end up in .cargo/config) to use one provided by osxcross or llvm.

Reproduction steps:

```bash
cargo new testing
cd testing
curl -L https://github.com/roblabla/MacOSX-SDKs/releases/download/13.3/MacOSX13.3.sdk.tar.xz | tar xJ
echo '[profile.release]' >> Cargo.toml
echo 'strip = "symbols"' >> Cargo.toml
SDKROOT=$PWD/MacOSX13.3.sdk CARGO_TARGET_X86_64_APPLE_DARWIN_LINKER=rust-lld cargo build --target=x86_64-apple-darwin --release
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.71.0 (8ede3aae2 2023-07-12)
binary: rustc
commit-hash: 8ede3aae28fe6e4d52b38157d7bfe0d3bceef225
commit-date: 2023-07-12
host: aarch64-apple-darwin
release: 1.71.0
LLVM version: 16.0.5
```
Repository: Web-Dev-For-Beginners
Issue: issue#1
Labels: no-issue-activity

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
 - OS: [e.g. iOS]
 - Browser [e.g. chrome, safari]
 - Version [e.g. 22]

**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - Browser [e.g. stock browser, safari]
 - Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
Repository: stable-diffusion-webui
Issue: [Feature Request]: refresh xyz list without reload ui
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

refresh xyz list without reload ui

### Proposed workflow

1. open xyz
2. select checkpoint or vae
3. upload or rename checkpoint or vae in disk
4. <=== should has a button for allow refresh list


### Additional information

_No response_
Repository: react-native
Issue: Codegen chokes on imported types
Labels: Tech: Codegen,Needs: React Native Team Attention,Type: New Architecture,Never gets stale

### Description

It seems codegen currently chokes on types imported from a different module, _i.e._ consider this example:
```ts
// types.ts
export type MyType = {
  field: string;
};

// NativeReactNativeMyModule.ts
import type { TurboModule } from 'react-native';
import { TurboModuleRegistry } from 'react-native';

import { type MyType } from './types';

export interface Spec extends TurboModule {
  myMethod(arg: MyType): void;
}

export default TurboModuleRegistry.getEnforcing<Spec>('ReactNativeMyModule');
```

When running the build (for Android on Ubuntu system) the codegen chokes on the method definition saying `UnsupportedGenericParserError: Module NativeReactNativeMyModule: Unrecognized generic type 'MyType' in NativeModule spec.`

This equivalent code works fine though:
```ts
import type { TurboModule } from 'react-native';
import { TurboModuleRegistry } from 'react-native';

export type MyType = {
  field: string;
};

export interface Spec extends TurboModule {
  myMethod(arg: MyType): void;
}

export default TurboModuleRegistry.getEnforcing<Spec>('ReactNativeMyModule');
```

### React Native Version

v0.72.3

### Output of `npx react-native info`

N/A

### Steps to reproduce

N/A

### Snack, code example, screenshot, or link to a repository

N/A