sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Manifest Confusion: @storybook/core NPM Registry data reports different scripts than current package.json
Labels: bug,needs triage

### Describe the bug

I am checking my dependencies for the latest [NPM Manifest Confusion](https://blog.vlt.sh/blog/the-massive-hole-in-the-npm-ecosystem) vulnerability, and @storybook/core keeps getting flagged for what looks like an accidental oversight, and not intentional malicious behavior.

When you view the [registry file](https://registry.npmjs.com/@storybook/core) for this package in NPM, the latest version lists two scripts, "prepare" and "start".

The [package.json](https://www.npmjs.com/package/@storybook/core/file/57b398bee5e3dcee468e1f75f83e04fc875bd8ab182092be11dacacdaf8611af) distributed with the same version only displays one of those scripts, "prepare".

### To Reproduce

There is a [python script](https://github.com/panki27/npm-manifest-check) similar to the one I am using that checks the manifest files for differences with the current files, and should show the issue (I have not tested this script).

To manually check:

1. View the [registry file](https://registry.npmjs.com/@storybook/core).
2. Find the latest version (in 'dist-tags'.latest) (should be 6.5.16 at this time)
3. View the reported scripts for the latest version (in versions["6.5.16"].scripts)
4. View the [index](https://www.npmjs.com/package/@storybook/core/v/6.5.16/index) for the latest version of the package to get the hex sum for the package.json
5. Use that hex sum to fetch the latest version's [package.json](https://www.npmjs.com/package/@storybook/core/file/57b398bee5e3dcee468e1f75f83e04fc875bd8ab182092be11dacacdaf8611af)
6. Compare the scripts in the package.json with what is declared in the manifest. They should match, but do not.

### System

```shell
N/A
```


### Additional context

_No response_
Repository: tauri
Issue: [feat] Expose Tao's raw `DeviceEvent`
Labels: type: feature request

### Describe the problem

I'm attempting to capture a mouse move event from raw device input, similar to [winput](https://docs.rs/winput/latest/winput/message_loop/index.html). However, it conflicts with Tauri's message loop and so cannot be used.

After some research, I discovered that Tao actually provides a [DeviceEvent](https://docs.rs/tao/latest/tao/event/enum.DeviceEvent.html) that exposes raw mouse move events from the OS.

Is there a way to access it?

- Platform: Windows
- Tauri version: 1.4.0

### Describe the solution you'd like

I couldn't find the api that exposes the [DeviceEvent](https://docs.rs/tao/latest/tao/event/enum.DeviceEvent.html) from Tauri directly, let me know if there's already one there or other ways (like accessing via, say, a raw window handle?) are available.

I'd like to have the `DeviceEvent` exposed so that I can utilize it for my usecases that requires getting raw device input.

### Alternatives considered

- [winput](https://docs.rs/winput/latest/winput/) - Conflicts with the Tauri's message loop.
- [multiinput](http://jonesey13.github.io/multiinput-rust/doc/multiinput/index.html) - Not sure what's going on, but it leaks memory.
- ['mousemove'](https://developer.mozilla.org/en-US/docs/Web/API/Element/mousemove_event) event from Web api. (see below)

### Additional context

What I was trying to achieve is that to capture mouse input while locking the cursor in the center of the app window.

I could use ['mousemove'](https://developer.mozilla.org/en-US/docs/Web/API/Element/mousemove_event) event from the Web api, but it eventually fails to get relative position because it retreats back to the center position after move, canceling out the points that moved, thus resulting to zero deltas after all.
Repository: next.js
Issue: When using middleware, responses are sometimes empty object {} header x-middleware-next:1 is present
Labels: bug,Middleware,linear: next

### 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: x64
      Version: Darwin Kernel Version 17.5.0: Mon Mar  5 22:24:32 PST 2018; root:xnu-4570.51.1~1/RELEASE_X86_64
    Binaries:
      Node: 16.20.0
      npm: 8.19.4
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10-canary.2
      eslint-config-next: 13.4.9
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

git@github.com:tombburnell/nextmiddlewarebug.git

### To Reproduce

clone the provided project, Install and build, then run using npm start.

click the links 1,2,3,4,5, etc while looking in inspector. 




### Describe the Bug

Some responses only have {} instead of { pageProps: {data: trackX } }
Those responses also have x-middleware-skip and are missing other headers.

Without middleware, the response is correct every time. Very confusing.

When this runs behind nginx cache, the pages fail to load with middleware enabled.

### Expected Behavior

Response with or without middleware should be the same when nothing explicitly has been done to change the response.

I need to use middleware to set a cookie but it's changing the response as well.

### Which browser are you using? (if relevant)

chrome

### How are you deploying your application? (if relevant)

aws/ec2

<sub>[NEXT-1428](https://linear.app/vercel/issue/NEXT-1428/when-using-middleware-responses-are-sometimes-empty-object-header-x)</sub>
Repository: ant-design
Issue: 使用StyleProvider标签包裹组件，使用form.resetFields()，表单组件样式会丢失
Labels: Inactive,🚌 External Dependency,🧶 Low Priority

### Reproduction link

[https://github.com/linzhaoyang/my-app.git](https://github.com/linzhaoyang/my-app.git)

### Steps to reproduce

参考antd5.x样式兼容方案将StyleProvider包裹在组件外层，调用form.resetFields()。

### What is expected?

form表单的DatePicker、 Input、Select 组件样式不会丢失

### What is actually happening?

form表单的DatePicker、 Input、Select 组件样式丢失

| Environment | Info |
| --- | --- |
| antd | 5.6.4 |
| React | 17.0.2 |
| System | macOS 10.13.6  |
| Browser | 114.0.5735.198（正式版本） (x86_64) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: An adjustable/tunable mouse pointer active zone utility app
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Many many years ago in a far far away galaxy I had a mouse utility that allowed to fine-tune and adjust everything in matters mouse including the pointer active zone area (tip).

For example: the response active area size of the tip of the pointer arrow, 1 or more pixels or even at a different location i.e. in the center of the pointer arrow.

Most importantly, when sizing a window, the pixel range where the mouse pointer switches over to the sizing double arrow over the windows border. For example 2 - 3 pixels or more tolerance and not the current default setting of 1pixel.



### Scenario when this would be used?

Since the geniuses of Windows 10 et al decided that now on the borderless windows you have to be accurate within 1 pixel for that sizing double arrow to show and function, good luck with that if you have a 4K screen resolution. It's very frustrating and nearly impossible to say the least. next to impossible on a touchpad.
As it is right now, I have to be exactly with the pointer [tip] over edge of a window otherwise it will not work and I never get the sizing double arrow.

To be clear I don't mean a mouse pointer design app. 
Rather a utility app that allows to adjust the default active area of the default mouse pointer et al.

### Supporting information

I tried to find such out there but I have not gotten any relevant results.
Repository: material-ui
Issue: [Joy][Stack] `direction` prop as object breaks `spacing` prop
Labels: bug 🐛,package: system,component: Stack

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

https://codesandbox.io/s/exciting-cherry-h3g5mz?file=/demo.tsx

### Current behavior 😯

On small (`sm`) window, the `spacing` prop as string is not applied when using the `direction` prop as object (for breakpoints mapping). It works as expected if both are objects or both are strings.

### Expected behavior 🤔

I expect the props to work in any combination.

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 13.4.1
  Binaries:
    Node: 20.4.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.7.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 114.0.5735.198
    Edge: Not Found
    Safari: 16.5.1
  npmPackages:
    @emotion/react: 11.11.1 => 11.11.1
    @emotion/styled: 11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.6
    @mui/core-downloads-tracker:  5.13.7
    @mui/joy: 5.0.0-alpha.86 => 5.0.0-alpha.86
    @mui/private-theming:  5.13.7
    @mui/styled-engine:  5.13.2
    @mui/system:  5.13.7
    @mui/types:  7.2.4
    @mui/utils:  5.13.7
    @types/react: 18.2.14 => 18.2.14
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 5.1.6 => 5.1.6
```
</details>
Repository: PowerToys
Issue: A new feature to quickly add parentheses into highlighted text
Labels: Needs-Triage

### Description of the new feature / enhancement

Do you know how you can just add parentheses into a piece of text, or the closing parentheses would just be automatically added when you type in an opening one in a code editor like VSCode? Can we make that available everywhere else?

### Scenario when this would be used?

In an Internet post, comment, document editing, or anywhere that the user might want to quickly add a pair of parentheses into an existing piece of text

### Supporting information


https://github.com/microsoft/PowerToys/assets/12825127/1a01c91e-c7d2-4567-b624-8fe915a8443a
Repository: godot
Issue: Sprite scaling snap doesn't work when rotated
Labels: bug,enhancement,topic:editor,topic:2d

### Godot version

4.1.stable

### System information

Godot v4.1.stable - Windows 10.0.22000 - Vulkan (Forward+) - dedicated GeForce MX350 () - Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz (8 Threads)

### Issue description

Whenever you rotate a sprite, the scaling snap stops working entirely, it should probably either snap to the grid or work like a rotated ColorRect, that snaps to the settings rather than the on-screen grid

### Steps to reproduce

1 - Rotate a sprite by any amount of degrees, positive or negative;
2 - Try rescaling the sprite in the 2D tab with select mode.

### Minimal reproduction project

[min reproduction.zip](https://github.com/godotengine/godot/files/12022617/min.reproduction.zip)
Repository: flutter
Issue: Include a flutter preview device with the Flutter SDK that supports hot reload
Labels: tool,P2,team-tool,triaged-tool

### Use case

This would allow new Flutter developers to experience Flutter's hot reload developer experience before installing a native build toolchain (such as Xcode, or Visual Studio).

- [x] introduce a new, hidden `flutter build _preview` sub-command https://github.com/flutter/flutter/pull/135639
- [x] introduce a new, PreviewDevice device available to Windows host users on release channels https://github.com/flutter/flutter/pull/135639
- [x] add error handling for when a user tries to build an app with plugins https://github.com/flutter/flutter/pull/136936
- [x] ensure IDE extensions can detect preview device https://github.com/flutter/flutter/pull/140112
- [ ] Have VSCode list the device as "preview -preview device", not referring to desktop
- [ ] Figure out why the preview device does not show in the "Flutter sidebar" in VSCode
- [ ] distribute the preview device with the Flutter SDK
- [ ] https://github.com/flutter/flutter/issues/139949
Repository: node
Issue: `Crypto` API documentation for `x509.keyUsage` is wrong for all versions
Labels: crypto,doc

### Affected URL(s)

https://nodejs.org/api/crypto.html#x509keyusage

### Description of the problem

The page for  `x509.keyUsage` indicates that it returns `An array detailing the key usages for this certificate.` while in fact it only returns the extended key usage for the certificate. For example:

- `1.3.6.1.5.5.7.3.1` for `TLS Web server`
- or `1.3.6.1.5.5.7.3.2` for `TLS Web client`

Key usages (not extend) are completely different are related to certificate extension under OID `2.5.29.15` to contain value in a bit array format.

Key usage can have for definition: Digital signature, Non-repudiation, Key encipherment, Data encipherment, Key agreement, Certificate signing, CRL signing, Encipher only, Decipher only.

Therefore the API should be `x509.extKeyUsage` and the definition  `An array detailing the key extended usages for this certificate.` to match the reality of the function.
Repository: flutter
Issue: [package tooling] Move dart pub get into fetch deps command
Labels: team,p: tooling,package,team-ecosystem,P2,triaged-ecosystem

Newly created command for fetching/downloading dependencies prior to building named fetch-deps. Add ` dart pub get` utility to the command to fetch dart dependencies.
Repository: rust
Issue: Custom MIR: bad span for assignments
Labels: T-compiler,A-MIR

Consider this code:
```rust
#![feature(custom_mir, core_intrinsics)]
use std::intrinsics::mir::*;

pub struct S(i32);

#[custom_mir(dialect = "runtime", phase = "optimized")]
fn main() {
    mir! {
        let x: i32;
        {
            let _observe = x;
            Return()
        }

    }
}
```
When running it in Miri, I wold expect this to point at the assignment. Instead it points at the entire `mir!` block:
```
error: Undefined Behavior: constructing invalid value: encountered uninitialized memory, but expected an integer
  --> src/main.rs:8:5
   |
8  | /     mir! {
9  | |         let x: i32;
10 | |         {
11 | |             let _observe = x;
...  |
14 | |
15 | |     }
   | |_____^ constructing invalid value: encountered uninitialized memory, but expected an integer
```

I've seen it use proper spans for `Call` terminators inside `mir!` blocks so I hope this is just an oversight and easy to fix. :)

Cc @JakobDegen
Repository: TypeScript
Issue: [FR] `"javascript/typescript.preferences.importModuleSpecifier": "no-relative-parent-imports"`
Labels: Suggestion,Awaiting More Feedback

<!-- ⚠️⚠️ 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. -->

Works like https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-relative-parent-imports.md
The following patterns are considered problems:

```js
/**
 *  in my-project/lib/a.js
 */

import bar from '../main' // Import parent file using a relative path
```

The following patterns are NOT considered problems:

```js
/**
 *  in my-project/main.js
 */

import foo from 'foo' // Import package using module path
import a from './lib/a' // Import child file using relative path

/**
 *  in my-project/lib/a.js
 */

import b from './b' // Import sibling file using relative path
```
Repository: go
Issue: x/pkgsite/internal/xcontext: TestStats failures with MillisToLastByte out of expected range
Labels: NeedsInvestigation,pkgsite

```
#!watchflakes
post <- pkg == "golang.org/x/pkgsite/internal/xcontext" && test == "TestStats" && `MillisToLastByte is \d+, wanted \d+`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/ea02a211b4fec7e757f6edfad44505805e79a457)):

    2023/06/29 00:02:26 Info: caching response of length 25 for /A
    2023/06/29 00:02:26 Debug: serving "/A" from cache
    2023/06/29 00:02:26 Info: caching response of length 25 for /A
    2023/06/29 00:02:26 Debug: serving "/A" from cache
    2023/06/29 00:02:27 Error: middleware.Panic: panic!
    --- FAIL: TestStats (0.59s)
        stats_test.go:72: MillisToLastByte is 587, wanted 500 +/- 50


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/pkgsite/internal/poller: Test failures with `incorrect 'good' value -1`
Labels: Testing,help wanted,NeedsFix,pkgsite

```
#!watchflakes
post <- pkg == "golang.org/x/pkgsite/internal/poller" && test == "Test" && `incorrect 'good' value -1`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/032647fa5d948219a6f5a7ef2d7a47d592d670df)):

    --- FAIL: Test (3.29s)
        poller_test.go:58: incorrect 'good' value -1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/pkgsite/internal/poller: TestCache failures with `CacheResultCount diff`
Labels: NeedsInvestigation,pkgsite

```
#!watchflakes
post <- pkg == "golang.org/x/pkgsite/internal/poller" && test == "TestCache" && `CacheResultCount diff`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/3d728c7cbf0553bd8de6350ccc04e89f288010ee)):

    2023/07/06 21:59:58 Info: caching response of length 25 for /A
    2023/07/06 21:59:58 Debug: serving "/A" from cache
    2023/07/06 21:59:58 Info: caching response of length 25 for /A
    2023/07/06 21:59:58 Info: cache get("/A"): context timed out
    2023/07/06 21:59:58 Info: caching response of length 25 for /A
    --- FAIL: TestCache (0.29s)
        caching_test.go:159: [A is cached again] GET returned body 5, want 4
        caching_test.go:177: [A is cached again] CacheResultCount diff (-want +got):
              map[bool]int{
            - 	false: 3,
            + 	false: 4,
            - 	true:  2,
            + 	true:  1,
              }
        caching_test.go:177: [bypassing the cache] CacheResultCount diff (-want +got):
              map[bool]int{
            - 	false: 3,
            + 	false: 4,
            - 	true:  2,
            + 	true:  1,
              }
    2023/07/06 21:59:59 Error: middleware.Panic: panic!


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/pkgsite/internal/poller: TestStats failures with MillisToLastByte out of expected range
Labels: Testing,NeedsInvestigation,pkgsite

```
#!watchflakes
post <- pkg == "golang.org/x/pkgsite/internal/poller" && test == "TestStats" && `MillisToLastByte is \d+, wanted \d+`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/3d728c7cbf0553bd8de6350ccc04e89f288010ee)):

    --- FAIL: TestStats (0.69s)
        stats_test.go:72: MillisToLastByte is 689, wanted 500 +/- 50


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: next.js
Issue: Duplicate js datasource created on html source
Labels: bug,linear: next

### 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: 19.6.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10-canary.2
      eslint-config-next: 13.4.9
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


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

Data fetching (gS(S)P, getInitialProps), Script optimization (next/script), SWC minifier (swcMinify: true), SWC transpilation, Turbopack (--turbo)

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

https://github.com/mehmet-z-sonmez/reproduction-app

### To Reproduce

If this component, creating 100 array of items to be rendered,  is called from layout, the Javascript item_list is duplicated in html source.

```
export default async function ItemListComponent() {


    const item_list = await createItems()


    return (
        <>
            <h1>Item List Component</h1>
            <ul>
                {item_list.map((item, index) => {
                    return <li key={index}>{item}</li>
                })}
            </ul>
        </>
    )

}

const createItems = async () => {
    let item_list = []

    for (let i = 1; i <= 100; i++) {
        item_list.push("Item" + i)
    }

    return item_list

}
```

```
import ItemListComponent from '../components/itemListComponent'

export default function RootLayout({ children }) {
  return (
    <html>
      <head />
      <body>
        {/* @ts-expect-error Server Component */}
        <ItemListComponent />
        <div>{children}</div>
      </body>
    </html>
  )
}
```

![duplicate_list](https://github.com/vercel/next.js/assets/109310774/526d22e6-2c11-4ffe-9804-dc574bb6c52c)


### Describe the Bug

Javascript datasources are duplicated in app html source, if they are used in layout, or components that layouts consumes.
The duplication do not occurs, if the lists are created in pages.
As most time layout hold menus, and this menus can be created by a datasource, such as lists, or fetch, it is not efficient to have same list twice in the final app source.

### Expected Behavior

Expected result is like the image to be a single source( single 100 items). This result can be retrieved if the listing component is consumed by page, not layout.

![expected_result](https://github.com/vercel/next.js/assets/109310774/a5dfbdfb-8831-4968-9152-8bd05513ec19)


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

114.0.5735.199

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

npm run dev

<sub>[NEXT-1427](https://linear.app/vercel/issue/NEXT-1427/duplicate-js-datasource-created-on-html-source)</sub>
Repository: pytorch
Issue: torch.jit.frontend.NotSupportedError: keyword-arg expansion is not supported: for dgl.nn.HeteroGraphConv()
Labels: oncall: jit

### 🚀 The feature, motivation and pitch

Hello,

I get this error once I call the following line after my model is trained.

```
model_scripted = torch.jit.script(model) # Export to TorchScript
model_scripted.save('model_scripted.pt') # Save

```

my model has a HeteroGraphConv layer that uses dictionary-based arguments (two node types). However, TorchScript has limitations compared to dynamic Python execution, and keyword argument expansion is one of the features not supported in TorchScript. 

Not sure if it's a bug or a feature to be developed, but NotSupportedError made me think it's a feature request.

Thanks!

### Alternatives

_No response_

### Additional context

```
torch.jit.frontend.NotSupportedError: keyword-arg expansion is not supported:
  File "../opt/anaconda3/lib/python3.9/site-packages/dgl/nn/pytorch/hetero.py", line 178
                    (src_inputs[stype], dst_inputs[dtype]),
                    *mod_args.get(etype, ()),
                    **mod_kwargs.get(etype, {}))
                      ~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
                outputs[dtype].append(dstdata)
        else:
```

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel