sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: runtime: go runs into a deadlock where a panicing application never acquires the debuglock due to non-atomic unlock  
Labels: NeedsInvestigation,compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.17.6
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
Linux 4.14.35-2047.514.5.el7uek.x86_64 #2 SMP Mon Jun 13 21:57:28 PDT 2022 x86_64 x86_64 x86_64 GNU/Linux
</pre></details>

### What did you do?
An application (gobgpd) encountered a panic and in the process of dumping stack traces go runtime tried to acquire a printLock which never became available preventing the application from a restart and causing application redundancy to fail.
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->



### What did you expect to see?

A panic should've completed in about a minute or so and application should've restarted.

### What did you see instead?

The panic took six hours.

The runtime printlock function has an additional mp.locks increment/decrement operation to make the operation atomic but no such provision exists during printunlock. If the scheduler pre-empts the printunlock after decrementing printlock but before actually unlocking, this could cause this issue.  

Here is the snippet:

```
func printlock() {
    mp := getg().m
    mp.locks++ // do not reschedule between printlock++ and lock(&debuglock).
    mp.printlock++
    if mp.printlock == 1 {
        lock(&debuglock)
    }
    mp.locks-- // now we know debuglock is held and holding up mp.locks for us.
}

func printunlock() {
    mp := getg().m
    mp.printlock--
    if mp.printlock == 0 {
        unlock(&debuglock)
    }
}
```
Repository: puppeteer
Issue: CDP "Network.setUserAgentOverride" not work in ServiceWorker
Labels: bug,upstream,confirmed,P3

### Bug description

CDP "Network.setUserAgentOverride" not work in ServiceWorker.

Steps to reproduce the problem:
```const puppeteer = require('puppeteer');
(async () => {
  const browser = await puppeteer.launch({
    args: ["--enable-experimental-web-platform-features"],
    headless: false,
  });
  browser.on("targetcreated", async (target) => {
    if (target.type() === "service_worker") {
      const client = await target.createCDPSession();
      if (!client) return;
      console.log("service worker set useragent");
      await client.send("Network.setUserAgentOverride", {
        "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36",
        "platform": "MacIntel",
        "userAgentMetadata": {
          "brands": [
            {
              "brand": "Chromium",
              "version": "100"
            },
            {
              "brand": "Google Chrome",
              "version": "100"
            },
            {
              "brand": ";Not A Brand",
              "version": "96"
            }
          ],
          "fullVersion": "100.0.4896.127",
          "platform": "Mac OS X",
          "platformVersion": "10_15_7",
          "architecture": "x86",
          "model": "",
          "mobile": false
        }
      });
      const worker = await target.worker();
      if (!worker) return;
      const data = await worker.evaluate(() => {
        if ('userAgentData' in navigator) {
          return navigator.userAgentData.brands;
        }
        return undefined;
      }).catch(e => {
        console.log(e.message);
        return undefined;
      });
      console.log("userAgentData: " + JSON.stringify(data));
    }
  });
  const page = await browser.newPage();
  await page.goto('https://abrahamjuliot.github.io/creepjs/');
  // await browser.close();
})();
```
I expect to get log:
`userAgentData: [{ "brand": "Chromium", "version": "100" }, { "brand": "Google Chrome", "version": "100" }, { "brand": ";Not A Brand", "version": "96" }]`

but i get result log:
`userAgentData: [{"brand":"Chromium","version":"105"},{"brand":"Not)A;Brand","version":"8"}]`

userAgent have the same results.



### Puppeteer version

v17.0.0

### Node.js version

v14.20.0

### npm version

v6.14.15

### What operating system are you seeing the problem on?

macOS

### Relevant log output

_No response_
Repository: ant-design
Issue: Bug：React 18环境下，当鼠标hover Panelbody时input值频繁闪烁
Labels: help wanted,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/status-antd-4-22-8-forked-o1z6o6?file=/index.js)

### Steps to reproduce

打开CodeSendbox重现链接
**react 18** 环境下，**single picker** 未选中值或值为空时，鼠标hover Panelbody 时input值频繁闪烁复现：
1、safari 15版本，可直接重现；
2、window和mac环境，chrome *打开开发者工具后*，hover时会闪烁，关闭后则不会。

看了下 rc-picker 的源码，有个立即更新的问题：
PanelBody.tsx
106行应当为 onDateMouseLeave(false)，非立即更新，可解决闪烁问题。

### What is expected?

修复闪烁问题

### What is actually happening?

频繁闪烁、体验不佳

| Environment | Info |
| --- | --- |
| antd | 4.22.8 |
| React | react 18.x |
| System | windows、mac |
| Browser | chrome104、safari 15.x |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: electron
Issue: Feature: scheduling API for main process
Labels: enhancement :sparkles:

Similar to the renderer variant https://chromestatus.com/feature/6031161734201344 using the browser UI thread scheduler.

Need arised from https://github.com/microsoft/vscode/issues/159650
Repository: TypeScript
Issue: Request: Treat generic mapped types with some intersection constraints as homomorphic
Labels: Suggestion,Awaiting More Feedback

# Suggestion

## 🔍 Search Terms

keyof, intersection, mapped type, constraint, homomorphic

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [ ] 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, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

## ⭐ Suggestion

I would like this mapped type to be homomorphic:
```ts
type Remap<T> = {
  [K in keyof T & string]: string
}
```

## 📃 Motivating Example

It's possible to achieve homomorphism for this type with:
```ts
type Remap<T> = {
  [K in keyof T as K & string]: string
}
```

So it's not like my feature request would bring anything new to the table. However, I find the DX of the proposal to be better than this, and perhaps it could be considered.

## 💻 Use Cases

I'm mainly interested in the improved DX because TS already provides the means to achieve this. I will totally understand if this gets just closed as something that won't be done. I couldn't find an issue about this, so I've figured out that it's still worth reporting this even if only for this request to exist in the issue tracker for the people to come.

I've even prototyped~ some of the changes required to make this happen [here](https://github.com/Andarist/TypeScript/commit/121685136badef878c734403512f6423ca9488ac). This code needs cleanup and perhaps it needs to be more strict about those intersections etc, I could refine it further.

[This issue](https://github.com/microsoft/TypeScript/issues/45582) is somewhat related to this one and perhaps it's even an argument why this one here shouldn't be implemented or why objects with index signatures should be exempt from the proposed changes.
Repository: godot
Issue: Pasting multiple nodes and undoing results in "Node not found" errors
Labels: bug,topic:editor

### Godot version

4.0.alpha15

### System information

Windows 10, Vulkan Clustered, RTX 2060

### Issue description

Note: This issue also occurs in 4.0.alpha14, so I don't think it's a regression caused by #59564.

It seems that undo isn't fully rolling back the changes made when pasting multiple nodes in the scene tree dock. "Node not found" errors will appear in the console after undoing a multi-node paste if scene tabs are switched.

https://user-images.githubusercontent.com/18225391/187653171-483c7db2-2827-4661-9486-4eb6c30f7968.mp4



### Steps to reproduce

- Create two scenes
- Add a few nodes to the first scene (doesn't matter what type)
- Copy at least two nodes, and paste them into another node
- Immediately undo the paste that was just done
- Switch to the second scene you made (without closing the first), and switch back

### Minimal reproduction project

_No response_
Repository: PowerToys
Issue: resizing window to fixed presets
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Snap a window to a specific window size. PE resize to presets, 1 to 1 aspect ratio, and/or to custom values. 

Preferably to the size of the content and not pixels used by frame and menu-bar. So, if I size to 1280x720, the window outside size could be 1288x740 (I don't know the size of the frames and menu-bar).

### Scenario when this would be used?

OBS Studio, or windowed games for a 1 to 1 pixel ratio of the content compared to the resolution of the monitor.

### Supporting information

_No response_
Repository: storybook
Issue: Special characters in the bundle makes it hard to deploy to static site hosting
Labels: bug,needs triage

**Describe the bug**
I've tried deploying a simple Storybook setup to following hosting providers and all of them had issues:

* Firebase
* Netlify
* Cloudflare Pages
* Github Pages

The issues were:
* `sb-addons/.storybook/manager.mjs` missing
* extension folders missing (e.g `@storybook/addon-controls/manager.mjs`) 

My guess is that these services filter out certain file patterns. Storybook could have better cleaner & simpler output layout, an option to just produce a simple static bundle would have been perfect. 

**To Reproduce**
Try deploying to one of the hosting providers in the list.

**System**
404 errors usually. The build is compiled successfully without any error.
Repository: excalidraw
Issue: 𝕏 (form twitter) "If you've answered "not using on mobile", is it because:
Labels: mobile

Hello dear developers ! [About Twitter voting ](https://twitter.com/excalidraw/status/1563209735431528448) increasingly reluctant to use the mobile version because of several reasons, below I've ranked them in priority of importance, from most to least, 🐞(bug) 🌟(FR): 

1. 🐞inconvenient to use drawing - it is necessary to change the tool "selection" to navigate and switch back to the drawing tool to continue drawing #5191 -> #5176
2. #5192 - if there are a large number of elements the canvas begins to freeze on the computer, and even more so on the phone. I know you're working on it, but it's also a point.
3. #5642 
4. #5643
5. #5644
6. #5645
7. #5646
8. #5647
9. #5648
10. #5649
11. #5650
12. #5651

If these points are resolved, we will enjoy using the mobile version a lot more.

Thank you so much for your attention !
Repository: react-native
Issue: React Native Android: An absolute positioned element outside of the bounds of its parent not responding to Drag Gestures (i.ex FlatList)
Labels: Platform: Android,Component: FlatList,Needs: Triage :mag:,Never gets stale

### Description

It's really similar to this issue: #27232.
The Tap gestures were fixed in React Native `0.66`, however, the same problem persists with all the other types of gestures, especially dragging/scrolling, which is quite annoying because the flat list cannot be scrolled at all.

This happens only on Android.
Works perfectly fine on IOS and Web.
Expo SDK 46

### Version

0.69.5

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

System:
    OS: macOS 12.0.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 739.58 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.14.0 - ~/.asdf/installs/nodejs/16.14.0/bin/node
    Yarn: 1.22.18 - ~/.asdf/shims/yarn
    npm: 8.3.1 - ~/.asdf/plugins/nodejs/shims/npm
    Watchman: Not Found
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
    Android SDK: Not Found
  IDEs:
    Android Studio: 2020.3 AI-203.7717.56.2031.7935034
    Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
  Languages:
    Java: 17.0.2 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

### Steps to reproduce

1. Create an absolute positioned component outside the bounds of its parent
2. Add `FlatList` inside this component
3. Run on an Android emulator/device, you won't be able to scroll the flat list.

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

https://snack.expo.dev/@jmysliv/bug-reproduction
Repository: pytorch
Issue: Floordiv is deprecated.
Labels: oncall: jit

### 🐛 Describe the bug

In torch/nn/functional.py,  __floordiv__ is used in group_norm function. __floordiv__ is deprecated, and its behavior will change in a future version of pytorch.

```
def group_norm(
    input: Tensor, num_groups: int, weight: Optional[Tensor] = None, bias: Optional[Tensor] = None, eps: float = 1e-5
) -> Tensor:
    r"""Applies Group Normalization for last certain number of dimensions.

    See :class:`~torch.nn.GroupNorm` for details.
    """
    if has_torch_function_variadic(input, weight, bias):
        return handle_torch_function(group_norm, (input, weight, bias,), input, num_groups, weight=weight, bias=bias, eps=eps)
    _verify_batch_size([input.size(0) * input.size(1) // num_groups, num_groups] + list(input.size()[2:]))
    return torch.group_norm(input, num_groups, weight, bias, eps, torch.backends.cudnn.enabled)
```

### Versions

Collecting environment information...
PyTorch version: 1.12.1+cu113
Is debug build: False
CUDA used to build PyTorch: 11.3
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.5 LTS (x86_64)
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Clang version: Could not collect
CMake version: version 3.16.6
Libc version: glibc-2.27

Python version: 3.8.13 (default, Mar 28 2022, 11:38:47)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.4.0-124-generic-x86_64-with-glibc2.17
Is CUDA available: True
CUDA runtime version: 11.1.105
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3090
Nvidia driver version: 465.19.01
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.2.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.2.2
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.2
[pip3] torch==1.12.1+cu113
[pip3] torchaudio==0.12.1+cu113
[pip3] torchvision==0.13.1+cu113
[conda] numpy                     1.23.2                   pypi_0    pypi
[conda] torch                     1.12.1+cu113             pypi_0    pypi
[conda] torchaudio                0.12.1+cu113             pypi_0    pypi
[conda] torchvision               0.13.1+cu113             pypi_0    pypi

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @ezyang @gchanan @zou3519 @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are
Repository: vscode
Issue: Treat any `en-*` dialect as default
Labels: feature-request,l10n-platform,perf,perf-startup

Today we seem to look for a language pack when e.g. `en-GB` is declared. But the fast path is to let it through as our default locale since we have no language pack for it as far we are concerned.

https://github.com/microsoft/vscode/blob/963bd989c442ab6d70b99405b40f7bed1189ef14/src/vs/base/node/languagePacks.js#L126-L130
Repository: pytorch
Issue: fix ATen tests that do not compile
Labels: triaged

### 🐛 Describe the bug

#84345 added a few missing tests to build and execute in CI. It had to exclude a few because they were not compiling successfully.

### Versions

Trunk.
Repository: go
Issue: proposal: mime: Add new function TypeForPath that behaves exactly like TypeByExtension  but matches on the full filename
Labels: Proposal

Related to the [Issue #52609](https://go.dev/issue/52609), the MIME-info database contains the regex that is not expanded by `TypeByExtension`.
Expanding regex is not suitable in all cases, for example `60:application/x-sharedlib:*.so.[0-9]*`.

Instead, a new function can be added to the API that should receive a type based on full filename, instead of expanding every possible filename for that extension.
Repository: pytorch
Issue: Lack of newly raised optimizers
Labels: high priority,feature,module: optimizer,triaged,needs research

### 🚀 The feature, motivation and pitch

I'm working on train Sota DNNs for research purposes. Optimizers like LAMB, Ranger and Lookahead have shown their advantage compared to SGD or AdamW in many tasks, including large batch training. However, Pytorch has stopped adding new optimizers algorithms for a long time. There are some third-party optimizers packages though, but an official implementation will be helpful.

### Alternatives

Using third-party implementations

### Additional context

_No response_

cc @ezyang @gchanan @zou3519 @vincentqb @jbschlosser @albanD @janeyx99
Repository: pytorch
Issue: RuntimeError: "slow_conv2d_cpu" not implemented for 'Half'
Labels: triaged,module: half

### 🚀 The feature, motivation and pitch

Hi, I need this implementation to make a lot of models (resnets, efficientnets, ...) work on float16 inference.

When I run these models on GPU, it works properly.

### Alternatives

_No response_

### Additional context

_No response_
Repository: vue
Issue: [2.7.10] [typescript] Cannot change the typing of $emit since 2.7.5
Labels: 2.7,feat:types

### Version
2.7.10

### Reproduction link
[github.com](https://github.com/vidal7/vue-2-7-issue-typed-emit)







### Steps to reproduce
* Clone the repo
* npm install
* npm run compile

### What is expected?
No typescript compilation errors

### What is actually happening?
There is typescript compilation errors

---
Since 2.7.5 and https://github.com/vuejs/vue/commit/005e52d0b6f1a5bf9679789c5c4b90afd442d86b, $emit cannot be typed with vue-class-component.

If you checkout commit [62000a803bbe4ed1dc9d30c20772a948cab49d16](https://github.com/vidal7/vue-2-7-issue-typed-emit/commit/62000a803bbe4ed1dc9d30c20772a948cab49d16) and doing npm install to go back in vue 2.7.4 and npm run compile, everything is fine.

See file src/ComponentWithTypedEvents.ts to see examples about working typing of events.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: vscode
Issue: Window control overlay does not dim when modal custom dialog shows
Labels: help wanted,windows,under-discussion,workbench-os-integration,titlebar,dialogs

When you open a folder on a fresh user data dir, you see a modal workspace trust custom dialog that dims the background but not the new WCO:

<img width="773" alt="image" src="https://user-images.githubusercontent.com/900690/187691646-b4518f45-76fe-4f92-8151-1b4b82453523.png">
Repository: flutter
Issue: App crashes on latest versions when `AnimatedContainer / Container` height is set to 0 and throws `uncaught exception 'NSInternalInconsistencyException', reason: 'Transformed points can't form a rect'`
Labels: c: regression,platform-ios,engine,a: accessibility,has reproducible steps,P2,c: fatal crash,found in release: 3.3,found in release: 3.4,team-ios,triaged-ios

am getting the issue here with flutter 3.3 stable:

it keeps crashing when the BaseBottomSheet is active if i comment out the hight and width, once in the page if i add static values to the width and hight it works with hot reload. When restarting it , it crashes again.

i also tried:

-  removing the constructors and removing the screen utill.
- using a container insted of sized box.
- removing material and adding a container instead.

```dart
import 'package:flutter/material.dart';
import 'package:flutter_screenutil/flutter_screenutil.dart';

import '../../../../../constants/const.dart';

class BaseBottomSheet extends StatelessWidget {
  final List<Widget> children;
  final double bottomSheetsHeight;
  const BaseBottomSheet(
      {Key? key,
      required this.children,
      this.bottomSheetsHeight = bottomSheetHeight})
      : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Material(
      color: Colors.white,
      elevation: 5,
      child: SizedBox(
        height: bottomSheetsHeight.h,
        width: bottomSheetWidth(context),
        child: SingleChildScrollView(
          child: Column(
            children: children,
          ),
        ),
      ),
    );
  }
}
```
Repository: puppeteer
Issue: [Bug]: browserWSEndpoint with localhost path throws ECONNREFUSED error
Labels: bug,upstream,confirmed,P3

### Bug description

**Steps to reproduce the problem:**

1. Open Chrome with remote debugging enabled:
`"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222`
2. Get `webSocketDebuggerUrl` by opening the following page using **localhost**:
`http://localhost:9222/json/version`
3. Connect to existing Chrome instance using `webSocketDebuggerUrl` value:
  `const browser = await puppeteer.connect({browserWSEndpoint: 'WEBSOCKETVALUE'})`

**Expected behavior:**
Puppeteer connects to existing instance of Chrome.

**Actual behavior:**
Puppeteer throws ECONNREFUSED error (see output below).

**Important Details**

- I am connecting to my installed version of Chrome 105.0.5195.54 (Official Build) (64-bit) on Windows, not Chromium.
- This worked on 16.2.0 and broke with the 17.0.0 update.
- The workaround is to switch the path to `ws://127.0.0.1`, which works as expected. But the `ws://localhost` path has always worked and this change in 17.0.0 broke my existing scripts.





### Puppeteer version

17.0.0

### Node.js version

18.4.0

### npm version

8.12.1

### What operating system are you seeing the problem on?

Windows

### Relevant log output

```shell
ErrorEvent {
  [Symbol(kTarget)]: WebSocket {
    _events: [Object: null prototype] { open: [Function], error: [Function] },
    _eventsCount: 2,
    _maxListeners: undefined,
    _binaryType: 'nodebuffer',
    _closeCode: 1006,
    _closeFrameReceived: false,
    _closeFrameSent: false,
    _closeMessage: <Buffer >,
    _closeTimer: null,
    _extensions: {},
    _paused: false,
    _protocol: '',
    _readyState: 3,
    _receiver: null,
    _sender: null,
    _socket: null,
    _bufferedAmount: 0,
    _isServer: false,
    _redirects: 0,
    _url: 'ws://localhost:9222/devtools/browser/2cdb3a8e-eeb3-421f-92d6-dc4943256db5',
    _originalUnixSocket: false,
    _originalSecure: false,
    _originalHostOrSocketPath: 'localhost:9222',
    _req: null,
    [Symbol(kCapture)]: false
  },
  [Symbol(kType)]: 'error',
  [Symbol(kError)]: Error: connect ECONNREFUSED ::1:9222
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1237:16) {
    errno: -4078,
    code: 'ECONNREFUSED',
    syscall: 'connect',
    address: '::1',
    port: 9222
  },
  [Symbol(kMessage)]: 'connect ECONNREFUSED ::1:9222'
}
```