sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Figure out how to reconcile `@types/node`'s `AbortSignal` and `AbortController` with Deno's
Labels: bug,tsc

The following code errors:

```ts
import { writeFile } from "node:fs";

const controller = new AbortController();
const signal = controller.signal;

// error here about duplicate AbortSignal types (`AbortSignal` is not assignable to type `AbortSignal`)
writeFile("file.txt", "content", { signal }, (err) => {
});
```

This is because we explicitly keep `AbortSignal` and `AbortController` over in the Node globalThis symbol:

https://github.com/denoland/deno/blob/0733943fe7de30fa54d6cd8ee34f7393e8bb7482/cli/tsc/99_main_compiler.js#L1290-L1291

That's because when attempting to share these globals, the errors are the following:

```
> ../deno/target/debug/deno check --all a.ts
Check file:///V:/scratch/a.ts
error: TS2300 [ERROR]: Duplicate identifier 'AbortController'.
declare class AbortController {
              ~~~~~~~~~~~~~~~
    at asset:///lib.deno.web.d.ts:295:15

    'AbortController' was also declared here.
    interface AbortController {
              ~~~~~~~~~~~~~~~
        at file:///C:/Users/david/AppData/Local/deno/npm/registry.npmjs.org/@types/node/18.11.18/globals.d.ts:47:11    and here.
    declare var AbortController: typeof globalThis extends {onmessage: any; AbortController: infer T}
                ~~~~~~~~~~~~~~~
        at file:///C:/Users/david/AppData/Local/deno/npm/registry.npmjs.org/@types/node/18.11.18/globals.d.ts:67:13

TS2320 [ERROR]: Interface 'AbortSignal' cannot simultaneously extend types 'EventTarget' and 'EventTarget'.
  Named property 'dispatchEvent' of types 'EventTarget' and 'EventTarget' are not identical.
interface AbortSignal extends EventTarget {
          ~~~~~~~~~~~
    at asset:///lib.deno.web.d.ts:313:11

TS2300 [ERROR]: Duplicate identifier 'AbortController'.
interface AbortController {
          ~~~~~~~~~~~~~~~
    at file:///C:/Users/david/AppData/Local/deno/npm/registry.npmjs.org/@types/node/18.11.18/globals.d.ts:47:11

    'AbortController' was also declared here.
    declare class AbortController {
                  ~~~~~~~~~~~~~~~
        at asset:///lib.deno.web.d.ts:295:15

TS2300 [ERROR]: Duplicate identifier 'AbortController'.
declare var AbortController: typeof globalThis extends {onmessage: any; AbortController: infer T}
            ~~~~~~~~~~~~~~~
    at file:///C:/Users/david/AppData/Local/deno/npm/registry.npmjs.org/@types/node/18.11.18/globals.d.ts:67:13

    'AbortController' was also declared here.
    declare class AbortController {
                  ~~~~~~~~~~~~~~~
        at asset:///lib.deno.web.d.ts:295:15

Found 4 errors.
```
Repository: electron
Issue: [Bug]: onBeforeRequest url does not include port when used with a custom scheme
Labels: bug :beetle:,platform/all,25-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

25.1.1

### What operating system are you using?

Ubuntu

### Operating System Version

18.04

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

The following minimal example:

```
const {app, BrowserWindow, protocol, session} = require('electron');

protocol.registerSchemesAsPrivileged([{
  scheme: 'yolo',
  privileges: {
    standard: true,
    secure: true,
    bypassCSP: true,
    supportFetchAPI: true
  }
}]);

app.whenReady().then(async () => {
  protocol.registerFileProtocol('yolo', (request, callback) => {
    console.log('FILE CALLBACK');
    console.log(request.url);
    callback({url: request.url});
  });
  let win = new BrowserWindow({
    webPreferences: {
      nodeIntegration: true,
      nodeIntegrationInSubFrames: false,
      contextIsolation: false,
    },
  });

  session.defaultSession.webRequest.onBeforeRequest((details, callback) => {
    console.log('BEFORE REQUEST');
    console.log(details.url);
    callback({});
  });

  win.loadURL('yolo://localhost:8000/asdf.html');
});
```
is expected to print:

```
BEFORE REQUEST
yolo://localhost:8000/asdf.html
FILE CALLBACK
yolo://localhost:8000/asdf.html
```

### Actual Behavior

Instead, it prints

```
BEFORE REQUEST
yolo://localhost/asdf.html
FILE CALLBACK
yolo://localhost/asdf.html
```

(the port is stripped)

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: react-native
Issue: [iOS] Ellipsis carries background from trimmed text
Labels: Platform: iOS,Issue: Author Provided Repro,Resolution: Fixed,Component: Text,Newer Patch Available

### Description

This issue happens on iOS only:

I tried to use nested text which has background, and could be wrapped with an ellipsis. Even the nested text doesn't show, the ellipsis has the background of nested text.

```
<Text numberOfLines={1} ellipsizeMode={'tail'}>Long text <Text style={{backgroundColor: 'red'}}>Nested text</Text></Text>
```



### React Native Version

0.70.6

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

System:
    OS: macOS 12.5.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 548.38 MB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    Yarn: 1.19.2 - ~/.nix-profile/bin/yarn
    npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
    Watchman: 4.9.0 - /Users/shidong.lin/.nix-profile/bin/watchman
  Managers:
    CocoaPods: 1.11.0 - /Users/shidong.lin/.nix-profile/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK:
      API Levels: 30, 31, 32
      Build Tools: 30.0.3
      System Images: android-31 | Google Play ARM 64 v8a, android-32 | Google Play ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 2022.2 AI-222.4459.24.2221.9862592
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.11 - /Users/shidong.lin/.nix-profile/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0
    react-native: https://github.com/react-native/archive/f56cf181afcd364122f94ac8609f9b3c7b0b1afb.tar.gz => 0.70.6
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

### Steps to reproduce

```
<Text numberOfLines={1}>Long text <Text style={{backgroundColor: 'red'}}>Nested text</Text></Text>
```
Just create a long text with colored nested text, check the behavior of ellipsis.

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

```
<Text numberOfLines={1} ellipsizeMode={'tail'}>Long text <Text style={{backgroundColor: 'red'}}>Nested text</Text></Text>
```
Repository: PowerToys
Issue: Context menu to mirror Images
Labels: Idea-New PowerToy,Product-File Actions Menu

### Description of the new feature / enhancement

Given these days a lot of pictures are selfies, they get downloaded laterally flipped. It would be nice to have a lateral flip power toy to mirror-image a picture on demand.

### Scenario when this would be used?

People will need this feature because there is no Windows-native image-flip operation that simply flips a picture. 

There are native operations to left-rotate and right-rotate an image, but not one to laterally flip one. 

A lot of phone pictures are saved as mirror images (especially selfies) and require flipping to show the traditional perspective.

For example
![image](https://github.com/microsoft/PowerToys/assets/830311/ddc5348a-d7c6-46fb-abdb-7f7f2f34cc6f)


### Supporting information

"Mirror selfies" are the common default on Android phones. I do believe that Apple phones have the sensible default of flipping the image before saving it.

https://www.techadvisor.com/article/734420/how-to-flip-a-selfie-photo-in-android.html
Repository: opencv
Issue: 'pyrDown_'
Labels: incomplete

### System Information

opencv 4.5.4-dev
ubuntu20.04
rk3588
arm_release_ver of this libmali is 'g2p0-01eac0', rk_so_ver is '4'.
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.5.4-dev) /home/firefly/cross_pro/opencv-master/modules/imgproc/src/pyramids.cpp:749: error: (-215:Assertion failed) !_src.empty() in function 'pyrDown_'

### Detailed description

ubuntu20.04
rk3588
arm_release_ver of this libmali is 'g2p0-01eac0', rk_so_ver is '4'.
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.5.4-dev) /home/firefly/cross_pro/opencv-master/modules/imgproc/src/pyramids.cpp:749: error: (-215:Assertion failed) !_src.empty() in function 'pyrDown_'

### Steps to reproduce

ubuntu20.04
rk3588
arm_release_ver of this libmali is 'g2p0-01eac0', rk_so_ver is '4'.
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.5.4-dev) /home/firefly/cross_pro/opencv-master/modules/imgproc/src/pyramids.cpp:749: error: (-215:Assertion failed) !_src.empty() in function 'pyrDown_'

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: PowerToys
Issue: Always on Top and VirtualBox(es)
Labels: Issue-Bug,Product-Always On Top,Needs-Triage

### Microsoft PowerToys version

0.70.1

### Installation method

GitHub, PowerToys auto-update, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

With a VM open, I use Win+Ctrl+t, and no framing indicating it's been "pinned" shows. It doesn't stay on top.

### ✔️ Expected Behavior

The VM to stay on top.

### ❌ Actual Behavior

Sinks typically to the back.

### Other Software

VirtualBox Graphical User Interface
Version 7.0.8 r156879 (Qt5.15.2)
Copyright © 2023 Oracle and/or its affiliates.
Repository: rust
Issue: TAIT: concrete types may differ by normalization
Labels: T-compiler,C-bug,F-type_alias_impl_trait,S-bug-has-test,T-types,fixed-by-next-solver

The following should compile:
```rust
#![feature(type_alias_impl_trait)]

trait Trait {
    type Gat<'lt>;
}

impl Trait for u8 {
    type Gat<'lt> = ();
}

fn dyn_hoops<T: Trait>(_: T) -> *const dyn FnOnce(T::Gat<'_>) {
    loop {}
}

type Opaque = impl Sized;

fn define() -> Opaque {
    dyn_hoops::<_>(0)
    //~^ ERROR concrete type differs from previous defining opaque type use
    // expected `*const (dyn FnOnce(()) + 'static)`,
    // got      `*const dyn for<'a> FnOnce(<u8 as Trait>::Gat<'a>)`
}
```
 
There are multiple places where we compare concrete types for equality. A regression test for this issue should cover them all:
```rust
#![feature(type_alias_impl_trait)]

trait Trait {
    type Gat<'lt>;
}

impl Trait for u8 {
    type Gat<'lt> = ();
}

fn dyn_hoops<T: Trait>(_: T) -> *const dyn FnOnce(T::Gat<'_>) {
    loop {}
}

mod typeof_1 {
    use super::*;
    type Opaque = impl Sized;
    fn define() -> Opaque {
        dyn_hoops::<_>(0)
    }
}

mod typeof_2 {
    use super::*;
    type Opaque = impl Sized;
    fn define_1() -> Opaque { dyn_hoops::<_>(0) }
    fn define_2() -> Opaque { dyn_hoops::<u8>(0) }
}

mod typeck {
    use super::*;
    type Opaque = impl Sized;
    fn define() -> Option<Opaque> {
        let _: Opaque = dyn_hoops::<_>(0);
        let _: Opaque = dyn_hoops::<u8>(0);
        None
    }
}

mod borrowck {
    use super::*;
    type Opaque = impl Sized;
    fn define() -> Option<Opaque> {
        let _: Opaque = dyn_hoops::<_>(0);
        None
    }
}

fn main() {}
```
Repository: godot
Issue: Theme regression in godot 4
Labels: bug,topic:editor,regression

### Godot version

4.0+

### System information

Godot v4.0+

### Issue description

The light themes in godot 4 have regressed from godot 3. I expect the theme 'Solarized Light' in godot 4 to look exactly the way it looked in godot 3.

### Steps to reproduce

Open godot, go to the Editor -> Editor Settings -> Interface -> Theme, and change the theme to one of the light themes, either 'Light' or 'Solarized Light'.

### Minimal reproduction project

Create a brand new empty project in godot and see the solarized light theme in godot 3:

![image](https://github.com/godotengine/godot/assets/20380758/020b7480-d526-4daf-a58c-a8e169dbac9f)

Compare it to godot 4, where the colors are overblown and the minimap has no highlight:

![image](https://github.com/godotengine/godot/assets/20380758/e03f5dc7-6fa6-45d9-b637-c0d3d10320f0)

I opened PR #78297 to attempt fixing the overblown colors (by simply reducing the negative contrast) until I realized that the minimap hightlight was also missing.
Repository: storybook
Issue: [Bug]: Storybook NextJS and react- i18next trigger an issue with the use of serverSideTranslations
Labels: bug,nextjs

### Describe the bug

When trying to build `storybook build` we got `ModuleNotFoundError: Module not found: Error: Package path ./serverSideTranslations is not exported from package service\node_modules\react-
i18next (see exports field in node_modules\react-i18next\package.json)`

All the react-i18next features work weel outside of storybook.

### To Reproduce

Setup main.js:
```
import type { StorybookConfig } from "@storybook/nextjs";

const config: StorybookConfig = {
  stories: ["../stories/**/*.mdx", "../stories/**/*.stories.@(js|jsx|ts|tsx)"],
  addons: [
    "@storybook/addon-links",
    "@storybook/addon-essentials",
    "@storybook/addon-interactions",
    "storybook-addon-next",
  ],
  framework: {
    name: "@storybook/nextjs",
    options: {},
  },
  docs: {
    autodocs: "tag",
  },
  core: {
    builder: "@storybook/builder-webpack5",
  },
  webpackFinal: async (config, { configType }) => {
    config.resolve.alias = {
      ...config.resolve.alias,
      "next-i18next": "react-i18next",
    };
    return config;
  },
};
export default config;
```
```
preview.tsx:

import { Suspense } from "react";
import { I18nextProvider } from "react-i18next";
import i18n from "./i18n";

// Wrap your stories in the I18nextProvider component
const withI18next = (Story) => {
  return (
    <Suspense fallback={<div>loading translations...</div>}>
      <I18nextProvider i18n={i18n}>
        <Story />
      </I18nextProvider>
    </Suspense>
  );
};
export const decorators = [withI18next];

export const globalTypes = {
  locale: {
    name: "Locale",
    description: "Internationalization locale",
    toolbar: {
      icon: "globe",
      items: [
        { value: "en", title: "English" },
        { value: "de", title: "Deutsch" },
      ],
      showName: true,
    },
  },
};
```
run `storybook build` 

### System

```shell
System:
    OS: Windows 10 10.0.19044
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz
  Binaries:
    Node: 18.0.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.6.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (112.0.1722.68)
  npmPackages:
    @storybook/addon-actions: ^7.0.8 => 7.0.8
    @storybook/addon-essentials: ^7.0.8 => 7.0.8
    @storybook/addon-interactions: ^7.0.8 => 7.0.8
    @storybook/addon-links: ^7.0.8 => 7.0.8
    @storybook/addon-mdx-gfm: 7.0.8 => 7.0.8
    @storybook/blocks: 7.0.8 => 7.0.8
    @storybook/nextjs: 7.0.8 => 7.0.8
    @storybook/react: ^7.0.8 => 7.0.8
    @storybook/testing-library: ^0.0.14-next.2 => 0.0.14-next.2
```


### Additional context

Here is a simple repro repo https://github.com/couz74/storybook-i18-nextjs
Repository: deno
Issue: npm:undici not working (Connect Timeout Error)
Labels: bug,windows,node compat,node API,node:http

It appears to have been resolved as a result of the following issue, but it still does not work in my environment.
https://github.com/denoland/deno/issues/16710

```js
PS D:\Desktop\Projects\Discord\Deno> node index.mjs
{
  data: {
    t: 'READY',
    s: 1,
    op: 0,
    d: {
      v: 10,
      user_settings: {},
      user: [Object],
      shard: [Array],
      session_type: 'normal',
      session_id: '329437320dbddd3c074ac6ca6815161e',
      resume_gateway_url: 'wss://gateway-us-east1-b.discord.gg',
      relationships: [],
      private_channels: [],
      presences: [],
      guilds: [Array],
      guild_join_requests: [],
      geo_ordered_rtc_regions: [Array],
      application: [Object],
      _trace: [Array]
    }
  },
  shardId: 0
}
PS D:\Desktop\Projects\Discord\Deno> deno run --allow-all index.ts
error: Uncaught (in promise) ConnectTimeoutError: Connect Timeout Error
    at onConnectTimeout (file:///D:/Desktop/Projects/Discord/Deno/node_modules/.deno/undici@5.22.1/node_modules/undici/lib/core/connect.js:182:24)
    at file:///D:/Desktop/Projects/Discord/Deno/node_modules/.deno/undici@5.22.1/node_modules/undici/lib/core/connect.js:129:46
    at file:///D:/Desktop/Projects/Discord/Deno/node_modules/.deno/undici@5.22.1/node_modules/undici/lib/core/connect.js:168:33
    at Object.action (ext:deno_web/02_timers.js:153:11)
    at handleTimerMacrotask (ext:deno_web/02_timers.js:67:10)
    at eventLoopTick (ext:core/01_core.js:189:21)
 ```

I used @discordjs/rest to test the behavior, but only undici actually causes errors.
```ts
import { request } from "npm:undici"
await request("https://jsonplaceholder.typicode.com/todos/1")
```

My enviroments:
deno 1.34.3 (release, x86_64-pc-windows-msvc)
v8 11.5.150.2
typescript 5.0.4
Repository: youtube-dl
Issue: Global cycling network (gcn)
Labels: request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [ ] I've verified that I'm running youtube-dl version **2021.12.17**
- [ ] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

I would love it if you could some way to support GCN. 

It's not a massive site but has done really good videos for the cycling and mountain bike community. Being able to have those videos offline would be awesome. 

Thanks for all the work you do.
Repository: next.js
Issue: not-found.js not work when use static HTML export
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.15.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.7-canary.0
      eslint-config-next: 13.4.5
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Static HTML Export (output: "export")

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/mwkldeveloper/not-found

### To Reproduce

1. npx create-next-app@latest
2. use default setting
3. add simple not-found.tsx to app folder:
```
export default function NotFound() {
  return (
    <div>
      <h2>Not Found</h2>
      <p>Could not find requested resource</p>
    </div>
  )
}
```
4. add  `output: 'export'`  in next.config.js
5. npm run build
6. copy all files under folder "out" to any static http file server
7. browser some page not exist e.g https://localhost:3000/pagenotfound


### Describe the Bug

not-found.tsx  works under `npm run dev` mode, it can be correct displayed but
 After static HTML export,  run as SPA seems cannot route to the custom not-found.tsx. just redirct to default page/Home page 

### Expected Behavior

when browser some page not exist, should render the not-found.tsx in static HTML export mode , the same as behavior on dev or SSR mode.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

static  file export and copy to server
Repository: vscode
Issue: Command Center customization
Labels: feature-request,menus

<!-- ⚠️⚠️ 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. -->

I want to have ability to add/edit action/tools/buttons(with icons) on the Command Center, near by navigation buttons
<img width="1080" alt="Screenshot 2023-06-16 at 11 18 37" src="https://github.com/microsoft/vscode/assets/47519614/2f2a6d1d-f8de-4ae8-a031-871e0b9bb218">
Repository: PowerToys
Issue: touchpad absolute  position mode
Labels: Idea-New PowerToy,Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

touchpad absolute  position mode

### Scenario when this would be used?

touchpad absolute  position mode

### Supporting information

_No response_