sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: TypeError: importers[path] is not a function occurred in monorepo after migrating to v7
Labels: bug,monorepos,pnpm

### Describe the bug

When using Storybook version 6.5.15 in **monorepo** with `vite`, there were no issues. But after migrating to version 7, an error occurred.


![image](https://user-images.githubusercontent.com/76927618/231944612-2295656a-8215-4916-9623-fe7ec289851b.png)
```
TypeError: importers[path] is not a function
    at StoryStore.importFn (http://localhost:6007/virtual:/@storybook/builder-vite/storybook-stories.js:6:31)
    at StoryStore.loadCSFFileByStoryId (http://localhost:6007/sb-preview/runtime.mjs:40:8376)
    at StoryStore.loadStory (http://localhost:6007/sb-preview/runtime.mjs:40:9563)
    at async http://localhost:6007/sb-preview/runtime.mjs:74:9003
    at async StoryRender.runPhase (http://localhost:6007/sb-preview/runtime.mjs:74:8764)
    at async StoryRender.prepare (http://localhost:6007/sb-preview/runtime.mjs:74:8922)
    at async PreviewWeb.renderSelection (http://localhost:6007/sb-preview/runtime.mjs:94:3120)
    at async PreviewWeb.selectSpecifiedStory (http://localhost:6007/sb-preview/runtime.mjs:94:247)
```

### To Reproduce

clone https://github.com/emewjin/sb-bug-reproduce-project and following [README](https://github.com/emewjin/sb-bug-reproduce-project#readme) steps

### System

```shell
Environment Info:

  System:
    OS: macOS 13.2.1
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 16.19.1 - ~/.nvm/versions/node/v16.19.1/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v16.19.1/bin/npm
  Browsers:
    Chrome: 112.0.5615.49
    Firefox: 107.0
    Safari: 16.3
  npmPackages:
    @storybook/addon-actions: ^7.0.4 => 7.0.4 
    @storybook/addon-backgrounds: ^7.0.4 => 7.0.4 
    @storybook/addon-controls: ^7.0.4 => 7.0.4 
    @storybook/addon-docs: ^7.0.4 => 7.0.4 
    @storybook/addon-interactions: ^7.0.4 => 7.0.4 
    @storybook/addon-links: ^7.0.4 => 7.0.4 
    @storybook/addon-mdx-gfm: ^7.0.4 => 7.0.4 
    @storybook/addon-measure: ^7.0.4 => 7.0.4 
    @storybook/addon-outline: ^7.0.4 => 7.0.4 
    @storybook/addon-toolbars: ^7.0.4 => 7.0.4 
    @storybook/addon-viewport: ^7.0.4 => 7.0.4 
    @storybook/mdx2-csf: ^1.0.0 => 1.0.0 
    @storybook/react: ^7.0.4 => 7.0.4 
    @storybook/react-vite: ^7.0.4 => 7.0.4 
    @storybook/testing-library: ^0.1.0 => 0.1.0 
    @storybook/theming: ^7.0.4 => 7.0.4
```


### Additional context

_No response_
Repository: puppeteer
Issue: [Bug]: PDF Header and Footer not working correctly
Labels: bug,upstream,confirmed

### Bug expectation

I expected the header and footer to be generated with the correct content and in the correct places.

Instead I got one of three problems (depending on the setup):

1. If a header template is defined but no footer, then the text `about:blank` and the Page number is being displayed at the *bottom* of the page (remember: this should be the header, but it seems to be placed at the footer's position). The content (`about:blank` and the page number) will be displayed regardless of what I actually put into the header template. ![image](https://user-images.githubusercontent.com/24976550/231948044-724644c7-8f5b-4d13-95ec-5dfd6483f350.png)
2. If a footer template is defined but no header, then the current date and time will be displayed at the top left of the page, which, again, is the both wrong place and also independent from the content that is actually in the footer.  ![image](https://user-images.githubusercontent.com/24976550/231948700-ef4c8398-3b22-4e67-9b4c-583d589921da.png)
3. If both a header and a footer is defined, then neither will be displayed (as if neither was defined).

The main content of the page seems to get generated properly in all cases.


Also some additial notes are: `browser.version()` returns `HeadlessChrome/112.0.5614.0`. And while I say below that I am on Linux, this is only partially true. I am inside a (Ubuntu)-WSL.

EDIT: Updated from puppeteer version `19.8.5` to `19.9.0`. The described errors remain identical.


### Bug behavior

- [ ] Flaky
- [X] PDF

### Minimal, reproducible example

```TypeScript
const { writeFile } = require('fs/promises');
const { launch } = require('puppeteer');

const puppeteerOptions = {
    margin: { top: 100, bottom: 100, left: 100, right: 100 },
    format: 'a4',
    displayHeaderFooter: true,
    // comment these two in and out for the described behaviour
    headerTemplate: '<div class="pageNumber"></div>',
    footerTemplate: '<div class="pageNumber"></div>',
};

async function main() {
    const browser = await launch({
        args: ['--no-sandbox', '--disable-dev-shm-usage'],
        headless: true,
    });

    const page = await browser.newPage();
    await page.setContent('<div>Hello, World!</div>', { waitUntil: 'networkidle0' });

    const pdf = await page.pdf(puppeteerOptions);

    await browser.close();

    writeFile('./output.pdf', pdf);
}

main();
```


### Error string

no error

### Puppeteer configuration

_No response_

### Puppeteer version

19.9.0

### Node version

16.15.1

### Package manager

npm

### Package manager version

8.11.0

### Operating system

Linux
Repository: opencv
Issue: Raise error instead of crashing if chosen output type too small (connectedComponentsWithStats)
Labels: category: imgproc,incomplete

### Descripe the feature and motivation

When running `connectedComponentsWithStats` on an array with more than 2^16 objects using `ltype=CV_16U`, the application crashes instead of raising some sort of exception in Python:

```
free(): corrupted unsorted chunks
Aborted (core dumped)
```

```
corrupted size vs. prev_size 
Aborted (core dumped)
```

To debug and get a stack trace, the Python `faulthandler` has to be enabled.

Raising/throwing an exception about the too-small type would simplify debugging.

### Additional context

Use this code to reproduce:

```py
import cv2
import numpy as np

tile = np.array([[1,0],[0,0]], dtype="uint8")
im = np.tile(tile, (1024,1024))
cv2.connectedComponentsWithStats(
    im, connectivity=8, ltype=cv2.CV_16U
)
```
Repository: deno
Issue: Support file: specifiers in package.json dependencies
Labels: node compat

In `package.json` we can specify file packages in folders by using [`file:` specifiers](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#local-paths):

```json
{
   "dependencies": {
       "@jamesernator/logger": "file:packages/logger"
   }
}
```

However currently Deno hasn't implemented them and instead just errors when trying to execute a file where such a package.json exists:

```
Not implemented scheme 'file'
    at file:///home/jamesernator/scripts/scripts/backup.general.ts:1:18
```

This issue is a request to implement `file:` specifiers in `package.json` with suitable behaviour.
Repository: PowerToys
Issue: FancyZones - automatic snapping when changing width of one window
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

Hi,
Im new here.
I use often FancyZones and I can't find missing function for me.
I need function, when the width of one window changes, then other windows will automatically snap to the new dimensions of that window.
This function works at build in Windows snapping, but i need more than 2 zones on screen.

It is possible to add this function?
Regards,
Krzysztof
Repository: neovim
Issue: inccommand (:command-preview): restore buffers/windows after preview
Labels: enhancement,inccommand

### Problem

Currently if `vim.api.nvim_win_set_buf` is called from a user command-preview function it is not reset when the user leaves the commandline. This would be useful for global search or goto style commands.

For example `GotoDefinition` could peek the location of the definition. Or even simpler a `SwitchBuffer/SwitchFile` command that shows the buffer in the current window while choosing the buffer from the popupmenu. 

Additionally there are some commands where showing some preview in a split/floating window makes a lot of sense even if `inccommand=nosplit`, I think allowing plugins to simply create windows (that are automatically destroyed when you leave the cmdline) could be useful. This could also be closely approximated by allowing the inccomand to be specified per command or even per invocation, if full window layout saving/restoring is too flexible/complex

### Expected behavior

Expanding the set of information/context that is saved before and restored after a command preview to include, in order of how useful I think this is

- shown buffer in each window
- existing windows and their configs

Another possibility that may allow more fine grained and efficient context saving and restoration is to add `before_preview`,  and `after_preview` callbacks where the plugin/user can save and restore whatever state it wants, including neovim editor state as well as its own. The downside of this is that a poorly implemented `after_preview` plugin could mess up the editor state. However it actually has another advantage besides being the most flexible: some expensive one-time computations can be done in the `before_preview` callback, such as treesitter queries, lsp requests, etc.
Repository: PowerToys
Issue: Precision touchpad tuning
Labels: Needs-Triage

### Description of the new feature / enhancement

Looking at documentation on [Precision Touchpad registry tweaks](https://learn.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchpad-tuning-guidelines) I found some very helpful ones, like tuning sensitivity zones. I did not find any software that does allow to configure them in a user-friendly way.
I would like to open a discussion if this is a good candidate for a PowerToys feature. Can be also united in one feature with #22864  if implemented.

Suggested design is:
- have a visual representation of a touchpad as a rectangular, and inside of it, a representation of margins for two sensitivity zones (Curtain and SuperCurtain)
- letting user to move margins of both zones (Left, Right, Top, Bottom separately), but SuperCurtain should stay less or equal to Curtain
- additionally have two separate sliders for "Horizontal Offset" and "Spacebar Offset" (but I'm not sure if the last is not the same as CurtainTop) 

### Scenario when this would be used?

A lot of mac users are delighted with mac touchpads' accuracy and performance and it's one of them key features that keep their productivity at max. While Microsoft did a lot with implementing Precision Touchpad drivers, there's more can be done in userland space. A power user can benefit of tuning those parameters to more comfortable levels and reach top productivity on their machine.

### Supporting information

https://learn.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchpad-tuning-guidelines is the main source of knowledge on this. Otherwise only reddit/superuser posts mentioning manual registry tweaks. No special software has been found personally by me.
Probably was intended for OEMs to set. But not every OEM will do it (if any). Also OEM tweaks can be lost with OS reinstall.
Repository: create-react-app
Issue: when there is a file with wrong syntax under src and it is not referenced, a compilation error will occur
Labels: needs triage,issue: bug report

There may be some undeveloped temporary files under `src`, which have not been introduced into the actual application, but it seems that they will be compiled and then an error will be reported

![image](https://user-images.githubusercontent.com/31298600/231967802-d1119e7c-1030-4057-9fba-2dff210ecb6d.png)
Repository: PowerToys
Issue: Change colour of update reminder
Labels: Issue-Bug,Area-Flyout

### Description of the new feature / enhancement

When a new update is available, the General settings page shows a reminder; but it's misleading and looks like PowerToys is up-to-date, even when there is an update available. Change the green colour to yellow when there is an update.
![image](https://user-images.githubusercontent.com/130738065/231971615-ce186899-8353-49dc-98bc-d61c39fd70f2.png)

### Scenario when this would be used?

to easily check whether there's an update available using colour cues.

### Supporting information

_No response_
Repository: TypeScript
Issue: Accessors are always reduced to properties in object literal declarations
Labels: Bug,Help Wanted,Domain: Declaration Emit

# Bug Report

Currently, accessors in object literals are condensed in plain properties - this an issue when get/set use different types. 
The workaround is to explicitly specify the type (see playground).
Ideally, accessor should be preserved in declaration files, when possible.

### 🔎 Search Terms

accessors, object literal

### 🕗 Version & Regression Information

/

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=5.0.4#code/KYDwDg9gTgLgBAYwgOwM7wGIQgBjgXjgG8BYAKDkrgHNh4AjAQygAoBKALjmQFcBbesCjE4UOjyjI4OANxwAvgBpyVOKjpwmrAG6MANj2BdeAoXAA+amFACWyamxHzy8meXKhIsRCnRwsEACMXKQUVLQMzOzG-IJQKlTqkTr6hjGmwpbotvZsLgT+2LJwAPQlcABKwDzqhbhwAGbQPsgINurIwKio7mRAA)

### 💻 Code

```ts
export const Foo = {
    get bar(): number { /* ... */ },
    set bar(value: number | string) { /* ... */ }
};
```

### 🙁 Actual behavior

```ts
export declare const Foo: {
    bar: number;
};
```

### 🙂 Expected behavior
```ts
export declare const Foo: {
    get bar(): number;
    set bar(value: number | string);
};
```
Repository: create-react-app
Issue: React Tutorial #0.4 onAfterSetupMiddleware is Deprecated | onBeforeSetupMiddleware is Deprecated
Labels: needs triage,issue: bug report

<!--
hi, solve to problem npm -  onAfterSetupMiddleware is Deprecated | onBeforeSetupMiddleware is Deprecated

link:

https://www.youtube.com/watch?v=ifSTp9WEHpo

-->
Repository: next.js
Issue: next/font refactor seems to brake builds when deployed
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: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.12.1
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.6
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


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

Font optimization (next/font)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/bold-kalam-ztju0q?file=%2Fpages%2Findex.tsx&selection=%5B%7B%22endColumn%22%3A12%2C%22endLineNumber%22%3A14%2C%22startColumn%22%3A12%2C%22startLineNumber%22%3A14%7D%5D

### To Reproduce

1. Import a font from `next/font/google` like:
```js
import { Jost } from 'next/font/google'
```

2. Use it in some of the [documented ways](https://nextjs.org/docs/basic-features/font-optimization#google-fonts)
3. Deploy the code to Vercel

### Describe the Bug

Seems that the [last refactor](https://github.com/vercel/next.js/pull/46731/files#diff-1a962444b9309d7fdb380f39786872f78c7b7456bad5b34dee72db0282356b63) of next/font/google published in [v13.2.4](https://github.com/vercel/next.js/releases/tag/v13.2.4) broke the builds [when deploying to Vercel](https://github.com/vercel/next.js/discussions/48371). 

This doesn't happen when downgrading to `v13.2.3`.

### Expected Behavior

Not to broke build in production.

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

_No response_

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

Vercel
Repository: puppeteer
Issue: [Bug]: Extension option page is automatically opened when puppeteer launch
Labels: feature,confirmed

### Bug expectation

What actually happened instead?:
I followed this guide to load Metamask extension successfully: https://pptr.dev/guides/chrome-extensions. After that, everytime I launch the puppeteer again, the Metamask option page is automatically opened

Expected: 
The extension option page need to be not opened

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Minimal, reproducible example

```TypeScript
const puppeteer = require("puppeteer");

(async () => {
  const browser = await puppeteer.launch({
    headless: false,
    args: [
      "--user-data-dir=data-dir",
      "--disable-extensions-except=path-to-ext",
      "--load-extension=path-to-ext",
    ],
    ignoreDefaultArgs: ["--disable-extensions"],
  });
})();
```


### Error string

no error

### Puppeteer configuration

_No response_

### Puppeteer version

lastest

### Node version

16.19.1

### Package manager

yarn

### Package manager version

1.22.19

### Operating system

macOS
Repository: pytorch
Issue: torch.cuda.is_available() return False
Labels: module: docs,module: cuda,triaged

### 🐛 Describe the bug

![image](https://user-images.githubusercontent.com/61486634/232003058-5027d8b5-1d6f-4fdb-8011-2dbce5d9bc8b.png)


### Versions

![image](https://user-images.githubusercontent.com/61486634/232003083-a96d97bd-22d1-43f2-9422-e9b6a392cdcf.png)
GPU 0: Quadro K620 (UUID: GPU-56622fc6-a9b3-5594-4c6d-b0b231be656a)
python version：3.8.16
cuda version：cuda10.2
cudnn version:8.7.0
![image](https://user-images.githubusercontent.com/61486634/232003168-4aa58152-4b30-436b-949e-ff6a3fd5e84e.png)
torch version：
![image](https://user-images.githubusercontent.com/61486634/232003276-c15165e5-c9e9-4978-9b56-1be6b97e5965.png)


cc @svekars @carljparker @ngimel
Repository: tensorflow
Issue: ImportError: libtensorflow_cc.so.2: cannot open shared object file: No such file or directory
Labels: stat:awaiting tensorflower,type:bug,type:build/install,subtype: ubuntu/linux,TF 2.13

<details><summary>Click to expand!</summary> 
 
 ### Issue Type

Bug

### Have you reproduced the bug with TF nightly?

No

### Source

source

### Tensorflow Version

tf 2.13.0

### Custom Code

Yes

### OS Platform and Distribution

Linux

### Mobile device

_No response_

### Python version

3.9

### Bazel version

6.1.1

### GCC/Compiler version

9.5.0

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current Behaviour?

I build the lastest TensorFlow code from source successfully with
`bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package`

Then I generate a TensorFlow whl successfully with
`./bazel-bin/tensorflow/tools/pip_package/build_pip_package /tmp/tensorflow_pkg`

But when I pip install this whl, import tensorflow got "ImportError: libtensorflow_cc.so.2: cannot open shared object file: No such file or directory". 

I found the whl file generated is only 80.64M. But I think it should be about 200M.

But there has libtensorflow_cc.so.2 file under path tensorflow/bazel-bin/tensorflow. I don't know why it wasn't packed into the whl file.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf
```


### Relevant log output

```shell
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/data1/envs/xtc3.9/lib/python3.9/site-packages/tensorflow/__init__.py", line 38, in <module>
    from tensorflow.python.tools import module_util as _module_util
  File "/data1/envs/xtc3.9/lib/python3.9/site-packages/tensorflow/python/__init__.py", line 36, in <module>
    from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow
  File "/data1/envs/xtc3.9/lib/python3.9/site-packages/tensorflow/python/pywrap_tensorflow.py", line 26, in <module>
    self_check.preload_check()
  File "/data1/envs/xtc3.9/lib/python3.9/site-packages/tensorflow/python/platform/self_check.py", line 63, in preload_check
    from tensorflow.python.platform import _pywrap_cpu_feature_guard
ImportError: libtensorflow_cc.so.2: cannot open shared object file: No such file or directory
```
</details>
Repository: storybook
Issue: [Bug]: Docs with react-vite doesn't work on 7.0.4 - Cannot read properties of undefined (reading 'fonts')
Labels: bug,has workaround,mdx,builder-vite

### Describe the bug

Storybook render this error on docs page on a new storybook

Cannot read properties of undefined (reading 'fonts')

![image](https://user-images.githubusercontent.com/1044182/232009700-b923dca5-63e8-494d-8234-dcde51b4f284.png)

If I downgrade to 7.0.3, docs page working

### To Reproduce

yarn dlx storybook@latest init --builder=vite --type=react
yarn storybook

or
yarn dlx storybook@next sandbox
choose React Vite (TS)
yarn install
yarn storybook

### System

```shell
Environment Info:

  System:
    OS: Linux 6.1 Manjaro Linux
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
  Binaries:
    Node: 19.8.1 - /tmp/xfs-72c84e66/node
    Yarn: 3.2.0 - /tmp/xfs-72c84e66/yarn
    npm: 8.19.2 - /usr/bin/npm
  Browsers:
    Firefox: 111.0.1
```


### Additional context

The problem is only on 7.0.4

7.0.3 => OK
7.1.0-apha.3 => OK
Repository: deno
Issue: Deno build on riscv64
Labels: build

I've successfully built Deno (1.32.3, 1.32.4 in progress) in qemu-user and run on HiFive Unmatched on [Arch Linux riscv64](https://archlinux.felixc.at).

Some tweaks I did:

- Use system `clang`, `lld`, `gn` and `ninja` to manually build V8.
- Apply https://github.com/denoland/rusty_v8/pull/1209 to allow passing extra GN args when building V8. The following steps will contain newly added environment variables from that PR.
- `NO_PRINT_GN_ARGS=1`. GN somehow segfaults when printing arguments, but it is trivial for now and doesn't affect generating build files.
- Enable `v8_enable_shared_ro_heap`. This is intentially [disabled](https://github.com/denoland/rusty_v8/blob/5dce1eaeef6457b7571b12c9c6170a362a62bb38/.gn#L52), but we need to wait for pointer compression to meet rusty_v8's [requirement](https://github.com/denoland/rusty_v8/blob/5dce1eaeef6457b7571b12c9c6170a362a62bb38/src/binding.cc#L2907) and disable it.
- Replace `ring` with [felixonmars/ring](https://github.com/felixonmars/ring) to provide C fallback for platforms without assembly crypto implementation.

Environment variables exported:
```sh
local _extra_gn_args=(
  'custom_toolchain="//build/toolchain/linux/unbundle:default"'
  'host_toolchain="//build/toolchain/linux/unbundle:default"'
  'v8_enable_shared_ro_heap=true'
)

export CC=clang CXX=clang++ AR=ar NM=nm
export CFLAGS="${CFLAGS//-fstack-clash-protection/}" CXXFLAGS="${CXXFLAGS//-fstack-clash-protection/}"
export V8_FROM_SOURCE=1
export CLANG_BASE_PATH=/usr
export GN=/usr/bin/gn NINJA=/usr/bin/ninja
export EXTRA_GN_ARGS="${_extra_gn_args[@]}"
export NO_PRINT_GN_ARGS=1
```

Build script for Arch Linux can be found in https://github.com/felixonmars/archriscv-packages/pull/2510. Patch Arch Linux's official PKGBUILD and build it:

```sh
pacman -S asp
asp checkout deno
cd deno/repos/community-x86_64
curl -L https://github.com/felixonmars/archriscv-packages/pull/2510.patch | git apply
makepkg -s
```

## Caveats

Note that current build runs TypeScript scripts normally, but in REPL errors will appear (while not affecting basic auto completion functionality):

```
ERROR TSLS = Error: Could not find source file: 'file://<working_dir>/$deno$repl.ts'.
    at getValidSourceFile (ext:deno_tsc/00_typescript.js:133358:23)
    at Object.getSemanticDiagnostics (ext:deno_tsc/00_typescript.js:133600:32)
    at serverRequest (ext:deno_tsc/99_main_compiler.js:1059:34)
    at [ext:cli/lsp/tsc.rs:3496:26]:1:12
```

This is triggered only by TypeScript LSP's `getDiagnostics` request. Other LSP requests with specifiers containing `$deno$repl.ts` seem to not fail. I'm yet to find out why.