sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Open code file using external editor causing speaker make pop noise on Mac (Apple Silicon)
Labels: bug,platform:macos,topic:editor

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

macOS 13.5.1 (22G90) Apple Sillicon

### Issue description

Once set external editor in editor settings, no matter its a valid external editor or not, each time open a `.gd` file in godot editor causing the speaker of computer make a pop noise just like a sound effects has been cut off.

### Steps to reproduce

- Set proper external editor settings (Editor Settings > Text Editor > External)
- Open any `.gd` file

The file will open normally, but making a noise.

### Minimal reproduction project

N/A
Repository: axios
Issue: Cookies are being sent in the response header from server, but not getting set in any browser
Labels: priority::medium

### Section/Content To Improve

app.use((req, res, next) => {
  const allowedOrigins = [
    "https://app1.netlify.app",
    "https://app2.vercel.app",
  ];
  const origin = req.headers.origin;

  if (allowedOrigins.includes(origin)) {
    res.setHeader("Access-Control-Allow-Origin", origin);
  }

  res.setHeader("Access-Control-Allow-Credentials", true);
  res.setHeader(
    "Access-Control-Allow-Methods",
    "GET, POST, PUT, DELETE, OPTIONS"
  );
  res.setHeader(
    "Access-Control-Allow-Headers",
    "X-Requested-With, X-HTTP-Method-Override, Content-Type, Accept,Authorization"
  );
  // res.setHeader("Access-Control-Expose-Headers", "Set-Cookie");

  if (req.method === "OPTIONS") {
    res.sendStatus(200);
  } else {
    next();
  }
});

I tried with withcreddentials:true in the front end also

axios
        .post(url, UserData, {
          headers: {
            "Content-Type": "application/x-www-form-urlencoded",
          },
          withCredentials: true,
        })

### Suggested Improvement

I searched but didn't find why this is happening, 3rd party cookies are also enabled in browser, my client is hosted on .vercel.app and server on .onrender.com
Most importantly it was working locally(client at port 3000 and server at 3001)

### Relevant File(s)

_No response_
Repository: deno
Issue: feat: increase depth limit of `console.log` or add `inspectDeep`
Labels: feat

When debugging Preact apps I usually have to inspect fairly deep tree structures. When printing these out via `console.log()` the depth limit is hit pretty quickly and subtrees are only printed up to that point. So instead I'm using this helper to print trees with a higher depth:

```ts
export function inspectDeep(value: unknown) {
  console.log(
    Deno.inspect(value, {
      colors: true,
      depth: 20, // probably change this
      iterableLimit: 10000, // probably change this
      strAbbreviateSize: 10000000, // probably change this
    })
  );
}
```

This works great! But now I noticed that I'm now on the third project where I'm copying this function into which made me wonder if we should have something for this out of the box.
Repository: storybook
Issue: [Bug]: vite extensions filed 
Labels: bug,needs triage

### Describe the bug

![image](https://github.com/storybookjs/storybook/assets/133855318/bfecb598-8254-4720-9380-709a2a14d75a)

When I add extensions in Vite and try to start Storybook, I encounter an error.

![image](https://github.com/storybookjs/storybook/assets/133855318/d052ebd6-8d2b-4279-9360-88330c86aa8b)


### To Reproduce

_No response_

### System

_No response_

### Additional context

 "@storybook/addon-essentials": "7.4.0",
    "@storybook/addon-interactions": "7.4.0",
    "@storybook/addon-links": "7.4.0",
    "@storybook/blocks": "7.4.0",
    "@storybook/testing-library": "0.2.0",
    "@storybook/vue3": "7.4.0",
    "@storybook/vue3-vite": "7.4.0",
    "@types/node": "^20.5.9",
    "@vitejs/plugin-vue": "^4.3.4",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "storybook": "7.4.0",
    "typescript": "^5.2.2",
    "vite": "^4.4.9",
    "vue-tsc": "^1.8.8"
Repository: vscode
Issue: Ability to disable diagnostics etc. from certain sources
Labels: under-discussion,languages-diagnostics

<!-- ⚠️⚠️ 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 personally have the issue that I have multiple sources point out the same error. A good example is a vue project in which I had 6 sources tell me a similar error.

<img width="1001" alt="image" src="https://github.com/microsoft/vscode/assets/48829979/db58df17-b738-435b-9eac-6bb7bcfb8909">

The feature I'd like to be implemented would allow the user to disable certain sources. Yes some extensions allow to disable their intellisense or other stuff but I don't want to chase after each and every extension and request a feature which could be implemented in vscode itself. It's not only about extensions tho, the ts server built into vscode also reports these and I, like many others, use the Pretty Typescript errors which makes the errors from the language server useless and also annoying if the error is big.
Repository: angular
Issue: Feature Request: Debounce on HostListener
Labels: feature,area: core,feature: insufficient votes

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

It is better to have Debounce/throttle feature for browser events like scroll, resize in HostListener Decorator by. native as we need to break DRY principle between modules while adding our own debounce decorator or util function each and everytime

### Proposed solution

It is better to have options to add Debounce/throttle feature for browser events like scroll, resize in HostListener Decorator by native

### Alternatives considered

It is better to have Debounce/throttle feature for browser events like scroll, resize in HostListener Decorator by native
Repository: bitcoin
Issue: contrib: add symbol-check test for non-existence of `vmova` instructions in Windows build
Labels: Windows

Given we are patching the Windows GCC used for releases, to avoid the use of certain aligned assembly instructions, we should probably add a symbol-check test to ensure the patches are working as intended. 

See https://github.com/bitcoin/bitcoin/issues/24726, https://github.com/bitcoin/bitcoin/pull/24736 and https://github.com/bitcoin/bitcoin/pull/28151 for the background here.
Repository: pytorch
Issue: `bytes(...)` support of torch tensor does not match numpy + it would be nice to support tensor.tobytes() as alias
Labels: feature,triaged,module: numpy,actionable

### 🐛 Describe the bug

```python
import numpy as np
import torch



a = np.arange(3)
print(bytes(a))
# b'\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00'
# ^ correct ^

print(bytes(a.view(np.uint8)))
# b'\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00'
# ^ correct ^

print(a.view('uint8'))
# array([0, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0], dtype=uint8)

print(a.tobytes())
# b'\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00'
# ^ correct ^




b = torch.arange(3)
print(bytes(b))
# b'\x00\x01\x02'
# ^ incorrect ^

print(bytes(b.view(torch.uint8)))
# b'\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\x02\x00\x00\x00\x00\x00\x00\x00'
# ^ correct ^

print(b.view('uint8'))
# TypeError: view() received an invalid combination of arguments - got (str), but expected one of:
# * (torch.dtype dtype)
#      didn't match because some of the arguments have invalid types: (str)
# * (tuple of ints size)
#      didn't match because some of the arguments have invalid types: (str)

print(b.tobytes())
# AttributeError: 'Tensor' object has no attribute 'tobytes'
``` 

Also, if PyTorch supported string representations of dtype as NumPy does, we could write more polymorphic code: `bytes(tensor.view('uint8'))`, currently we need to have to use backend specific `np.uint8` or `torch.uint8`

Maybe related issues:
- https://github.com/pytorch/pytorch/issues/33041
- https://github.com/pytorch/pytorch/issues/43949

### Versions
```python
np.__version__
# '1.24.2'
torch.__version__
# '2.1.0.dev20230802+cpu'
```

cc @mruberry @rgommers
Repository: rust
Issue: Tracking issue: 32bit x86 targets lose float NaN payload in return values
Labels: C-tracking-issue,A-floating-point,A-ABI,O-x86_32

On x86 (32bit) targets,  returning a floating-point number from a "C" ABI function by-value can change the bits of their NaN payloads. (Specifically, the quiet bit gets set.) This is caused by using x87 registers to pass return values, as mandated by the ABI for this target.

This is a known and long-standing problem, and very hard to fix. The purpose of this issue mostly is to document its existence and to give it a URL that can be referenced.

A proper fix would require patching LLVM to use different code to load float return values into an x87 register -- specifically, it has to be done in a way that NaN payloads are fully preserved.

Related issues:
- https://github.com/llvm/llvm-project/issues/66803: the same bug on the LLVM side.
- https://github.com/rust-lang/rust/issues/114479: that's a different problem, also affecting x86-32 but concerning the actual FP computations, not the NaN bits of return values.

Prior issues:
- https://github.com/rust-lang/rust/issues/73288
- https://github.com/rust-lang/rust/issues/46948
Repository: opencv
Issue: BackgroundSubtractorKNN does not respect a zero learning rate (same with GSOC and LSBP)
Labels: bug,category: video

### System Information

OpenCV python version: 4.8.0.76 opencv-contrib-python
Operating System / Platform: Ubuntu 22.04
Python version: 3.10.12

### Detailed description

The `BackgroundSubtractorKNN()` does **not** stop updating the background model regardless of the zero `learningRate` factor when calling the `BackgroundSubtractorKNN.apply(<image>, None, learningRate=0)`.
It works fine when using the `BackgroundSubtractorMOG2`, but the `BackgroundSubtractorKNN` does not respect the learning rate. The background model keeps updating regardless of the _learningRate_ value.

The same issue exists with `BackgroundSubtractorLSBP` and `BackgroundSubtractorGSOC` from the *cv2.bgsegm* package. Although `BackgroundSubtractorMOG` and `BackgroundSubtractorMGM` work fine.

### Steps to reproduce

```python
import cv2


back_sub = cv2.createBackgroundSubtractorKNN()
# back_sub = cv2.bgsegm.createBackgroundSubtractorLSBP()    # Has the same problem
# back_sub = cv2.bgsegm.createBackgroundSubtractorGSOC()    # Has the same problem

cap = cv2.VideoCapture(0)
if not cap.isOpened():
    raise (Exception("Could not open capture"))

learning_rate = 0.1
while True:
    ret, frame = cap.read()
    if not ret:
        break

    fg_mask = back_sub.apply(frame, None, learning_rate)
    print(learning_rate)

    cv2.imshow("frame", frame)
    cv2.imshow("foreground", fg_mask)
    cv2.imshow("background", back_sub.getBackgroundImage())

    k = cv2.waitKey(1)
    if k == ord("q"):
        break
    # Press "d" to switch learning_rate between 0.1 and 0.0
    elif k == ord("d"):
        if not learning_rate:
            learning_rate = 0.1
        else:
            learning_rate = 0.0

cap.release()
cv2.destroyAllWindows()
```

### 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: react
Issue: Bug: eslint-plugin-react-hooks: Incorrect dependency requirement when using `typeof` on nested data structures
Labels: Type: Bug,Component: ESLint Rules

This issue seems related to #18828, but it's not identical. Using `typeof` on a primitive value seems to work as expected, but it fails for nested property access.

Version: `eslint-plugin-react-hooks@4.6.0`


## Steps To Reproduce

```tsx
import { useEffect, useState } from "react";

const Dummy = () => {
    const [foo, setFoo] = useState<{ bar: number }>({ bar: 42 });

    useEffect(() => {
        const square = (x: typeof foo.bar) => x * x;
        setFoo((previous) => ({ ...previous, bar: square(previous.bar) }));
    }, []);
};
```


## The current behavior

This effect clearly doesn't have external (value) dependencies, but I get this:

> ESLint: React Hook useEffect has a missing dependency: 'foo'. Either include it or remove the dependency array. (react-hooks/exhaustive-deps)


## The expected behavior

Using `typeof` never leads to a dependency requirement, just like in this example doesn't:

```tsx
import { useEffect, useState } from "react";

const Dummy = () => {
    const [bar, setBar] = useState<number>(42);

    useEffect(() => {
        const square = (x: typeof bar) => x * x;
        setBar(square);
    }, []);
};
```
Repository: PowerToys
Issue: UWP programs from the store do not run using a command line alias.
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.73.0

### Installation method

PowerToys auto-update, Other (please specify in "Steps to Reproduce")

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Type the name of the alias in the launcher bar. Press Enter.

### ✔️ Expected Behavior

I was expecting to see a program window.

### ❌ Actual Behavior

You will get a browser window with a search page.
Depending on the alias, you may be able to run a completely different program.

### Other Software

_No response_
Repository: PowerToys
Issue: Different sorting options within the menu
Labels: Idea-Enhancement,Product-Settings

### Description of the new feature / enhancement

I believe it would be a huge advantage if one could sort or group the apps based on multiple reviews, for example, sorting by installation date, alphabetical sorting, grouping by installed and not installed.

### Scenario when this would be used?

Alaways if the main menu is visible

### Supporting information

_No response_
Repository: pytorch
Issue: Allow slicing of Nested Tensors along constant dimensions
Labels: triaged,module: nestedtensor

### 🚀 The feature, motivation and pitch

In many cases several of the nested tensor dimensions are constant, and therefore in principle should allow slicing

```
import torch
a = torch.rand(5,5,5)
b = torch.rand(5,5,10)
c =  torch.rand(5,5,15)
d= torch.nested.nested_tensor([a,b,c])
d[:2]
```

Will currently return the following

`NotImplementedError: Could not run 'aten::slice.Tensor' with arguments from the 'NestedTensorCPU' backend. `

May be useful to be able to mark which dims are and will remain constant? 

### Alternatives

_No response_

### Additional context

_No response_

cc @cpuhrsch @jbschlosser @bhosmer @drisspg
Repository: next.js
Issue: Next 13 updating subproject in monorepo causing TypeError
Labels: bug

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

https://codesandbox.io/p/sandbox/fervent-hooks-28vh4m?file=/exaple-project/next.congig.js:17,1

### To Reproduce

In monorepo project (lerna) with main package.json dependencies
    "next": "12.2.5",
    "react": "18.1.0",
    "react-dom": "18.1.0"
 and node version v16.20.2 
 update subproject to next 13 with external next.config configuration:
 
 /** @type {import('next').NextConfig} */
const config = require('fx-config');

const withTM = require('next-transpile-modules')(config.transpiledModules);
const withBundleAnalyzer = require('@next/bundle-analyzer')({
  enabled: process.env.ANALYZE === 'true'
});

const nextConfig = {
  ...config.nextConfig
};

module.exports = withBundleAnalyzer(withTM(nextConfig));

----
the actual error: 

TypeError: Cannot read properties of undefined (reading 'push')
    at writeConfigurationDefaults (/Users/Projects/-ui/packages/fx-app-currencies/node_modules/next/dist/lib/typescript/writeConfigurationDefaults.js:229:30)
    at async verifyTypeScriptSetup (/Users/Projects/-ui/packages/fx-app-currencies/node_modules/next/dist/lib/verifyTypeScriptSetup.js:120:9)
    at async verifyTypeScript (/Users/Projects/-ui/packages/fx-app-currencies/node_modules/next/dist/server/lib/router-utils/setup-dev.js:95:26)
    at async startWatcher (/Users/Projects/-ui/packages/fx-app-currencies/node_modules/next/dist/server/lib/router-utils/setup-dev.js:116:29)
    at async setupDev (/Users/Projects/-ui/packages/fx-app-currencies/node_modules/next/dist/server/lib/router-utils/setup-dev.js:1032:20)
    at async initialize (/Users/Projects/-ui/packages/fx-app-currencies/node_modules/next/dist/server/lib/router-server.js:68:23)
    at async Server.<anonymous> (/Users/Projects/-ui/packages/fx-app-currencies/node_modules/next/dist/server/lib/start-server.js:178:36)
  

### Current vs. Expected behavior

Expecting to upgrade for next 13

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
OS: Mac
Node: v16.20.2 
Next: 12.2.5
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

Tested with different node version and next canaries but it not helped
Repository: deno
Issue: Consider formatting .mdx files with "deno fmt"
Labels: suggestion,deno fmt

We need to research what it entails to format ".mdx" files. Can we somehow our current support for Markdown and JSX/TSX files in a simple way to support MDX.
Repository: pytorch
Issue: Call for a deterministic implementation of scatter_add_cuda_kernel
Labels: triaged,module: scatter & gather ops

### 🚀 The feature, motivation and pitch

I met an error below: 

-----------------------------------------------------------------------------

......
message_agg = scatter(message, index=obj, dim=0, dim_size=n_node, reduce='sum')
  File "/home/gg/anaconda3/envs/KGAT-Pytorch/lib/python3.6/site-packages/torch_scatter/scatter.py", line 155, in scatter
    return scatter_sum(src, index, dim, out, dim_size)
  File "/home/gg/anaconda3/envs/KGAT-Pytorch/lib/python3.6/site-packages/torch_scatter/scatter.py", line 21, in scatter_sum
    return out.scatter_add_(dim, index, src)
RuntimeError: scatter_add_cuda_kernel does not have a deterministic implementation, but you set 'torch.use_deterministic_algorithms(True)'. You can turn off determinism just for this operation if that's acceptable for your application. You can also file an issue at https://github.com/pytorch/pytorch/issues to help us prioritize adding deterministic support for this operation.


### Alternatives

_No response_

### Additional context

_No response_

cc @mikaylagawarecki
Repository: rustdesk
Issue: "waiting for image" issues
Labels: bug

# Unresolved

- [ ] https://github.com/rustdesk/rustdesk/issues/5608
- [ ] https://github.com/rustdesk/rustdesk/issues/2175
- [ ] https://github.com/rustdesk/rustdesk/issues/6419
Repository: godot
Issue: Gravity vector override of Area3D doesn't override fully the project's default gravity vector
Labels: bug,topic:physics,topic:3d

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

Godot v4.1.1.stable - Pop!_OS 22.04 LTS - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 970 (nvidia; 535.98) - Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4 Threads)

### Issue description

When putting a RigidBody3D inside an Area3D set to override (mode = "Replace") the gravity vector to a null vector, we still see the rigid body falling.
The fall speed is slower than the default one, still it's falling.

The fall seems to stop after a little while.
Setting the "can_sleep" property to false seems to extend the fall asymptotically.

Setting the default gravity vector (project settings) to 0 seems to fix this behavior.

### Steps to reproduce

From the minimal reproduction project:
Minimal scene setup  with:

**An Area3D**
- gravity_space_override set to **Replace**
- gravity_direction set to (0,0,0)

**A default RigidBody3D**

Test1:
- Run the scene and observe the capsule falling and stopping few moments later

Test2:
- Set the property "can_sleep" to false on the RigidBody3D
- Run the scene and observe the capsule falling slower and slower

Test3:
- Set the project setting "physics/3d/default_gravity_vector" to (0,0,0)
- Run the scene and observe the capsule falling no more



### Minimal reproduction project

[Area3dOverridePbDemo.zip](https://github.com/godotengine/godot/files/12525539/Area3dOverridePbDemo.zip)
Repository: PowerToys
Issue: FancyZones "favourites"
Labels: Idea-Enhancement,FancyZones-Editor,Needs-Triage

### Description of the new feature / enhancement

When a user creates a new custom FancyZone it should be able to edit their "favourites" FancyZones on the top bar that shows up when draging a window.

### Scenario when this would be used?

When a user creates a new custom FancyZone.

### Supporting information

_No response_
Repository: go
Issue: cmd/go: `wrong signature` error when using a type alias for `*testing.T`
Labels: NeedsInvestigation,GoCommand

Seems you can't alias `testing.T`, it confuses `go test`. Confuses Go Playground too.

<pre>
go version go1.18.1 linux/amd64
</pre>

### What did you do?

https://go.dev/play/p/21W7rITsLUb

### What did you expect to see?

Test results

### What did you see instead?

`wrong signature for TestLastIndex, must be: func TestLastIndex(t *testing.T)`
Repository: deno
Issue: `deno test --filter` takes a long time to find tests to run
Labels: perf,tests,testing

Noticed that the `--filter` option is pretty slow in detecting which tests to run. With 1000 tests files it takes around 10s to find one single test case on my M2 Macbook Pro.

## Steps to reproduce

1. Create a `generate.ts` file with the following content
  ```ts
  import * as path from "https://deno.land/std@0.201.0/path/mod.ts";
  
  const __dirname = new URL(".", import.meta.url).pathname;
  const dir = path.join(__dirname, "tests");
  
  try {
    Deno.removeSync(dir, { recursive: true });
  } catch {}
  try {
    Deno.mkdirSync(dir);
  } catch {}
  
  // Generate a bunch of tests we don't care about
  for (let i = 0; i < 1000; i++) {
    const file = path.join(__dirname, "tests", `test_file_${i}.test.ts`);
    const code = `Deno.test("Test ${i}", () => {});\n`;
    Deno.writeTextFileSync(file, code);
  }
  
  // Generate the test we care about
  const file = path.join(__dirname, "tests", `filter.test.ts`);
  const code = `Deno.test("filter", () => {});\n`;
  Deno.writeTextFileSync(file, code);
  ```
2. Run `deno run -A generate.ts`. This will create a `test/` folder with 1000 tests plus one `filter.test.ts` which is the one we're passing to `--filter`.
3. Run `deno test --filter "filter"` -> Takes more than 10s