sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: `node --v8-options`  says that you can use a space between the flag name and value, but it's not true
Labels: cli

### Version

v22.5.1

### Platform

```text
Linux nic-desktop 6.9.3-76060903-generic #202405300957~1718348209~22.04~7817b67 SMP PREEMPT_DYNAMIC Mon J x86_64 x86_64 x86_64 GNU/Linux
```


### Subsystem

cli

### What steps will reproduce the bug?

`node --v8-options` prints:

```
The following syntax for options is accepted (both '-' and '--' are ok):
  --flag        (bool flags only)
  --no-flag     (bool flags only)
  --flag=value  (non-bool flags only, no spaces around '=')
  --flag value  (non-bool flags only)
  --            (captures all remaining args in JavaScript)
```

### How often does it reproduce? Is there a required condition?

/

### What is the expected behavior? Why is that the expected behavior?

The help output should match the implementation

### What do you see instead?

It's not true that I can use `--flag value`. If I try running `node --arm-arch armv8 foo.js` it parses `armv8` as the script name, rather than as if it was `node --arm-arch=armv8 foo.js`

### Additional information

_No response_
Repository: pytorch
Issue: torch.nn.Bilinear weights initialization reason
Labels: module: nn,triaged,topic: docs

### 📚 The doc issue

`torch.nn.Bilinear` initializes weights uniformly in +-1/sqrt(in-1-features)(https://github.com/pytorch/pytorch/blob/main/torch/nn/modules/linear.py#L219) , and this fact is included in the documentation.

Is there a justification for this weights initialization? A one-line code comment would help. Intuitively, would expect instead that given a bilinear form `x^TAy` where both `x` and `y` are considered inputs, weights initialization would be symmetric under `x <-> y`. 





### Suggest a potential alternative/fix

```
    def reset_parameters(self) -> None:
        # FIXME: weights are initialized to blah blah because of blah blah
        bound = 1 / math.sqrt(self.weight.size(1))
        init.uniform_(self.weight, -bound, bound)
        if self.bias is not None:
            init.uniform_(self.bias, -bound, bound)
```

Other options could be to point the user to define their own bilinear layer using the `einsum` operation, if the provided Bilinear API may not generalize to all applications.

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: three.js
Issue: BatchedMesh without a transform array
Labels: Suggestion

### Description

As mentioned previously, we are using BatchedMesh extensively. However, we don't actually use the transform arrays. I would like to make that optional. For our use cases, it keeps the code simpler, it uses less VRAM, and it has a (small) effect on rasterization performance.

### Solution

Something like:

```
			batchingMatrix: IS_BATCHEDMESH && object._matricesTexture !== null,
			batchingColor: IS_BATCHEDMESH && object._colorsTexture !== null,
```

and

```
				p_uniforms.setOptional( _gl, object, 'batchingTexture' );
				if ( objects._matricesTexture !== null ) {

					p_uniforms.setValue( _gl, 'batchingTexture', object._matricesTexture, textures );

				}

				p_uniforms.setOptional( _gl, object, 'batchingIdTexture' );
				if ( object._indirectTexture !== null ) {

					p_uniforms.setValue( _gl, 'batchingIdTexture', object._indirectTexture, textures );

				}
```

### Alternatives

I'm not sure

### Additional context

_No response_
Repository: deno
Issue: WebGPU spec validation not met with `beginRenderPass`
Labels: bug,web,upstream,webgpu

Hi! I've been using the most recent commit of Deno compiled from source (1faac2dce380afa387f08780ae1a79d087b3acf0) and I think there might be an issue with some of the validation for `beginRenderPass`. But I'm not sure if it might be an upstream `wgpu` issue. 

Based on the most recent spec (https://www.w3.org/TR/webgpu/#abstract-opdef-gpurenderpassdescriptor-valid-usage), if `this.occlusionQuerySet` is not null, it must be 'valid to use'. This mean that `object.[[[device]]`  must equal `targetObject.[[[device]]]` (https://www.w3.org/TR/webgpu/#abstract-opdef-valid-to-use-with). 

I expected the following program to emit an error because the `querySet` that is used belongs to a different device:
```js
async function main() {
    const adapter = await navigator.gpu.requestAdapter();
    const device = await adapter.requestDevice();
    const encoder = device.createCommandEncoder();
    const texture = device.createTexture({
        dimension: "2d",
        sampleCount: 1,
        format: "bgra8unorm",
        label: "GPUTexture2",
        size: {
            width: 30,
            height: 30,
            depthOrArrayLayers: 2
        },
        mipLevelCount: 1,
        usage: GPUTextureUsage.RENDER_ATTACHMENT | GPUTextureUsage.TEXTURE_BINDING | GPUTextureUsage.COPY_SRC,
        viewFormats: ["bgra8unorm-srgb"]
    });
    const textureView = texture.createView({
        aspect: "all",
        dimension: "2d-array",
        arrayLayerCount: 1,
        baseArrayLayer: 0,
        mipLevelCount: 1,
        baseMipLevel: 0,
        format: "bgra8unorm",
        label: "GPUTextureView2"
    });

    const adapter2 = await navigator.gpu.requestAdapter();
    const device2 = await adapter2.requestDevice()
    const querySetFromDevice2 = device2.createQuerySet({
        count: 1162,
        label: "GPUQuerySet0",
        type: "occlusion"
    })

    const renderPassEncoder = encoder.beginRenderPass({
        colorAttachments: [{
            clearValue: {
                r: 0,
                g: 0,
                b: 0,
                a: 0
            },
            loadOp: "load",
            storeOp: "discard",
            view: textureView
        }],
        label: "GPURenderPassEncoder0",
        maxDrawCount: 439496549,
        occlusionQuerySet: querySetFromDevice2 // Should throw an error 
    });



}
main().catch(console.error);
```

This type of error is caught when `textureView` is from a different `device` instance, but not for `occlusionQuerySet`.
Repository: godot
Issue: Node3D: `Transform` inspector CTRL and SHIFT has no effect to the slider
Labels: discussion,topic:editor,usability

### Tested versions

v4.3.rc1.mono.official [e343dbbcc]

### System information

Windows 11

### Issue description

I encountered this problem because I would use the 'Page' argument for 'HSlider' but it has no effect.
Then I checked on the Godot `Node3D` inspector `Transform` to use the CTRL or SHIFT as the tooltips says.
![image](https://github.com/user-attachments/assets/6d8cf44e-73f3-434d-a796-6dd6aa190046)

But pressing CTRL or SHIFT does not work inside the inspector.
When I use the gizmo in 3D view, it rotates 15° when I press CTRL and 5° when I press SHIFT.




### Steps to reproduce

- Create a 3D Scene and add a Node3D with a mesh.
- switch to the inspector and try to use CRTL or SHIFT during using the slider (no effect)
- verify it by using the gizmo inside the 3d view (it works)

### Minimal reproduction project (MRP)

n/a
Repository: flutter
Issue: Possible unnecessary files in debug build
Labels: tool,P2,team-tool,triaged-tool

In 
https://github.com/flutter/flutter/blob/99e201e2ef3f8e996c9320feffa513007b67a4d8/packages/flutter_tools/lib/src/build_system/targets/ios.dart#L467
 and 
https://github.com/flutter/flutter/blob/99e201e2ef3f8e996c9320feffa513007b67a4d8/packages/flutter_tools/lib/src/build_system/targets/android.dart#L56
, the build system copies `Artifact.vmSnapshotData` and `Artifact.isolateSnapshotData` from the host artifacts to the assets during the debug build mode. However, in [dart_snapshot.cc](https://github.com/flutter/engine/blob/3b31b21599d1968c4f8b1c0a4e77562105bf5e55/runtime/dart_snapshot.cc#L104), it shows that these files are [not used under the Android platform](https://github.com/flutter/engine/blob/3b31b21599d1968c4f8b1c0a4e77562105bf5e55/runtime/dart_snapshot.cc#L28), while they are used under the iOS platform.

This copying action appears to be redundant for Android, as the files are not used. On the other hand, for iOS, the build system relies on the snapshot build for the host platform.

A potential problem arises if iOS enables the compressed pointers feature in the future. The host snapshot may become incompatible with the snapshot generated for iOS, potentially causing offset errors or other issues.

Edit: The snapshot files can be removed for iOS too, they can be found by symbol mapping, and the version in symbol are compiled for target platform.
Repository: ui
Issue: [bug]: cli defaulting to TypeScript but then defaults to tailwind.config.js
Labels: bug

### Describe the bug

_I'm using Remix in this example, but I suspect this causes issues with other frameworks too_

When running `npx shadcn-ui@latest init`, it takes you through the CLI setup process, defaults to using TypeScript, but then for tailwind, it defaults to tailwind.config.js rather than a .ts file.  

I suspect this is the cause for issue [2704](https://github.com/shadcn-ui/ui/issues/2704)

![image](https://github.com/user-attachments/assets/35ca1432-eb4a-4159-8c81-ebd43b7ddb36)


### Affected component/components

All

### How to reproduce


Follow the docs here: https://ui.shadcn.com/docs/installation/remix

After step 3, you will have a `tailwind.config.js` and a `tailwind.config.ts` file which conflict

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
n/A
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: neovim
Issue: Duplicate diagnostics for LSP implementing both push and pull
Labels: bug,lsp,diagnostic

### Problem

Since 0.10.0 neovim supports LSP pull diagnostics, a specific LSP 'Verible' has both push and pull diagnostics (added 2 years ago in https://github.com/chipsalliance/verible/pull/1268 ).

Now all warnings/errors appear twice:

![tvnviewer_MzoLWoqsLp](https://github.com/user-attachments/assets/50da093c-d904-4fe3-aba5-1bb31fb834ae)

- Both vscode and helix seem to handle this without issues.
- In nvim 0.9 there were no LSP pull diagnostics so this issue did not appear (no duplicate warnings/errors).
- Using nvim 0.10.0 an ancient version of the LSP without pull diagnostics (the version right before the pull request linked) also works as expected.




### Steps to reproduce using "nvim -u minimal_init.lua"

To reproduce simply use the Verible lsp with any systemverilog (.sv) file that contains any warning/error.

```
--- CHANGE THESE
local pattern = 'systemverilog'
local cmd = {'verible-verilog-ls'}
local root_markers = {'.git', '.editorconfig'}
local settings = vim.empty_dict()

-- unchanged below :)
vim.api.nvim_create_autocmd('FileType', {
  pattern = pattern,
  callback = function(args)
    local match = vim.fs.find(root_markers, { path = args.file, upward = true })[1]
    local root_dir = match and vim.fn.fnamemodify(match, ':p:h') or nil
    vim.lsp.start({
      name = 'bugged-ls',
      cmd = cmd,
      root_dir = root_dir,
      settings = settings
    })
  end
})
```

Example invalid file _test.sv_, which produces: _syntax error, rejected "--"_"
```
module test(--)
endmodule
```

### Expected behavior

I would expect warnings to appear only once.

I don't know the LSP standards too well, but perhaps when both push and pull are supported by a LSP only one of the two should be used? I could probably work around this issue by disabling the pull capabilities for this LSP, but I feel like it would be cleaner to fix this in nvim directly.

### Neovim version (nvim -v)

0.10.0

### Language server name/version

verible-v0.0-2023-gbda7f9a8 and later

### Operating system/version

N/A

### Log file

https://gist.github.com/henrykvdb/bf47ad22a44380426625d686543670e9
Repository: vscode
Issue: Cannot interact with environment variable hover for terminals
Labels: under-discussion,workbench-hover

The hover is shown like this, and mousing over it to dismisses the hover before my mouse gets there if I want to interact with any of the actions

![image](https://github.com/user-attachments/assets/1e3dd698-fb78-4233-a8aa-32a8e9c2f745)


@benibenj maybe we should have "[safe triangles](https://github.com/microsoft/vscode/blob/main/src/vs/base/browser/dom.ts#L2523)" for hovers out of the box, I've hit this kind of thing in many editor areas
Repository: godot
Issue: `Texture2D`'s `get_size()` returns a Vector2 (while `Image`'s returns a Vector2i)
Labels: discussion,topic:core,usability

### Tested versions

- 4.2.stable
- 4.3-rc1

### System information

doesn't matter

### Issue description

not sure if it can be classified as a bug, but I think `Texture2D.get_size()` should return a Vector2i because right now you cannot compare the two without first casting one into the other (can't directly compare Vector2i and Vector2)

### Steps to reproduce

see Docs

### Minimal reproduction project (MRP)

see Docs
Repository: vscode
Issue: Cloud (☁️) emoji not rendering in terminal or editor on macOS Monterey 12.3.1
Labels: bug,terminal-rendering

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.91.1
- OS Version: macOS Sonoma 14.6

Steps to Reproduce:

1. Copy to either the terminal or editor: \"☁️\".
2. It won't render correctly:
    <img width="24" alt="image" src="https://user-images.githubusercontent.com/24731903/161929771-0f53f291-7000-457b-a988-25cfd063c120.png">

Reopening #146893, this happens with the default fonts, and also with 'Meslo LG M for Powerline' and 'MesloLGM Nerd Font', this doesn't happen in other apps that use this same font, e.g. iTerm2, and doesn't happen only in the SV Code terminal, it also happens in the editor itself. Something is wrong here... It's not right to just blame the font...

This happens with both `editor.fontFamily` set to the default and with `"editor.fontFamily": "'Meslo LG M for Powerline', Menlo, Monaco, 'Courier New', monospace"`. 

![6bkl4h](https://user-images.githubusercontent.com/24731903/161930706-1bdd64bf-cb85-4cd7-b94a-8d0d3cc1b9df.jpg)
Repository: opencv
Issue: calibrate.py parameters bug
Labels: question (invalid tracker),wontfix

### System Information

OpenCV version: 4.8.0
Operating System / Platform: Ubuntu 20.04
Compiler & compiler version: GCC 9.3.0

### Detailed description

while running calibrate.py sample code, if you pass a parameter for the location of the images the code fails to use this information.
"img_mask" variable is only filled if no data_path is provided

![image](https://github.com/user-attachments/assets/7490829a-cc7a-4354-a5ed-89bca07a7416)


### Steps to reproduce

call the script from terminal with any path as parameter, the path is the only relevant parameter 
py calibrate.py -w 13 -h 9 -t charucoboard --square_size=1 --marker_size=0.8 --aruco_dict=DICT_4X4_250  --threads=4  \\any_path\\*.png

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] 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: pytorch
Issue: Can we avoid RecordStream for P2P ops?
Labels: oncall: distributed,triaged

**Background: RecordStream is a safety/convenience feature that sacrifices some performance**

RecordStream is a feature that automates safety of cuda-allocator reuse/free when tensors are used across multiple nccl streams.  TLDR; If the tensor is used on a separate stream from which it's allocated, the allocator could attempt to free it too early, and recordStream implements a cuda-event-based callback system to ensure the remote stream work compeltes before allocator reuse/free can occur.  Why is this bad?  It can lead to non-determinism of memory reuse, that can lead to significant performance variations in distributed programs.  Often times, we'd rather be explicit about freeing, so that we know when it will happen and it happens at the same time on all ranks.

**Disabling RecordStream**
Today there exists a flag (`TORCH_NCCL_AVOID_RECORD_STREAMS`) for disabling recordStream in much of the ProcessGroupNCCL code, but P2P ops are excepted from this for the following reason: [ProcessGroupNCCL::pointToPoint()](https://github.com/pytorch/pytorch/blob/main/torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp#L2910)

> "for isend, I don't think the API requires the user to wait() on the returned handle, so ProcessGroupNCCL can't know when it's safe to release the input"

To be clear, the isend API returns a work object, created inside the pointToPoint function, which holds a reference to the input tensor.  Holding this reference should keep the tensor alive until the work object is out of scope.

For recv operations, users are required to call work.wait() before using the tensor, but for send operations they may not be in this habit and they may be relying on the recordStream functionality for safety.

However, it's simple enough to fix the safety issue with send operations, by holding onto the work object until the appropriate time to call .wait().

**Proposal**

When `TORCH_NCCL_AVOID_RECORD_STREAMS=1`, we change the behavior of P2P ops including isend, in an unsafe way.  We issue a warning about this.  This is a new explicit requirement which we should document. 
* isend is only safe if users hold onto the work object for long enough to ensure the send is completed.  Generally, this means holding onto it until calling .wait() and then discarding it.  We explain that the memory for the send buffer is held until the work is waited() and deleted.
* We issue a warn_once to explain this when users call isend with `TORCH_NCCL_AVOID_RECORD_STREAMS=1`

Users could face silent correctness bugs if they don't heed the warning.

If in the future we want to enable TORCH_NCCL_AVOID_RECORD_STREAMS by default, we face additional safety risks to doing so.

Alternatives?

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @d4l3k @c-p-i-o
Repository: vscode
Issue: Allow coloring individual files in the explorer view using the context menu
Labels: feature-request,file-explorer

<!-- ⚠️⚠️ 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. -->

https://github.com/user-attachments/assets/5ba79f23-25ea-418b-8822-9e1017b4f9c2

Select individual files with the context menu and set a background color on them. The background colors / list can be saved to the `.vscode` folder so they're persistent in the project and can be shared with others.
Repository: next.js
Issue: Issue with loading `AKAMAI` images in `dev` mod
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/funny-glitter-28gnx5

### To Reproduce

Issue in this line: https://github.com/vercel/next.js/blob/canary/packages/next/src/shared/lib/image-loader.ts#L32

I am using AKAMAI Image manager for serving the images in all environments. Image config used in **`next.config.js`** provided in [CodeSandbox](https://codesandbox.io/p/devbox/funny-glitter-28gnx5):

While debugging, I got following image configuration:

```ts
{
  config: {
    deviceSizes: [ 180, 264, 396, 564, 657 ],
    imageSizes: [
      16,  32,  48,  64,
      96, 128, 256, 384
    ],
    path: 'https://{akamaiDomainDev}/',
    loader: 'akamai',
    loaderFile: '',
    domains: [
       akamaiDomainDev,
       akamaiDomainProd,
    ],
    disableStaticImages: false,
    minimumCacheTTL: 60,
    formats: [ 'image/webp' ],
    dangerouslyAllowSVG: false,
    contentSecurityPolicy: "script-src 'none'; frame-src 'none'; sandbox;",
    contentDispositionType: 'inline',
    remotePatterns: [],
    unoptimized: false,
    allSizes: [
       16,  32,  48,  64,  96,
      128, 180, 256, 264, 384,
      396, 564, 657
    ]
  },
  src: 'assets/1234.jpg',
  quality: undefined,
  width: 16
}
```

- Run: `yarn dev`

### Current vs. Expected behavior

### Current

- Different behavior in **dev** and **prod** mode. Can we have a consistent behavior?
- If the leading **`/`** is **not provided** in the image **src** in **prod** build then there is **no issue**
- Running the app in **dev** mode **requires** leading **`/`** in image src if domains array is specified in image config
- Otherwise, following error is being shown:
  <img width="497" alt="image" src="https://github.com/user-attachments/assets/d7ff900b-da00-4577-9a5e-f2ebaea9bf5f">

### Expected

- No errors
- Image loaded on the page
- Consistent behavior for AKAMAI images in dev and prod mode

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:13:18 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6030
  Available memory (MB): 18432
  Available CPU cores: 12
Binaries:
  Node: 20.15.1
  npm: 10.7.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 14.2.5 // Latest available version is detected (14.2.5).
  eslint-config-next: 14.2.5
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A
```

### Which area(s) are affected? (Select all that apply)

Image (next/image)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

The easiest fix could be adding leading `/` to image **`src`** but the question is why we have inconsistency between different environments? Is it expected behavior?
Repository: PowerToys
Issue: PowerToys App triggering error.
Labels: Issue-Bug,Product-Settings,Needs-Triage,Status-No recent activity,Needs-Team-Response

### Microsoft PowerToys version

0.82.1.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

Initial install works and features are working fine.  When I shut down the computer the app gets the pop up "Contact your system administrator for more info."  I have contacted our local networ engineering team and the don't block this specific app.  Had the same issue with bing wallpaper app with similar response that app is not blocked.  Now the bing wallpaper app is working fine.  

### ✔️ Expected Behavior

App should launch and remain functional after Shut Down and Restarts.  After Restart the app does not open.

### ❌ Actual Behavior

App launches with restart but is not functional.  Power Toys apps don't work.

### Other Software

Not sure what to put here.