sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Missing `has` method on the `access` object in Decorator Contexts
Labels: bug,upstream,swc

Version: Deno v1.40.3+0bfa0cc

After submitting issue #22253, which is also related to something missing in decorator context objects, I noticed that **none** of the context objects from the reproduction run seemed to have a `has` method in their `access` objects. 

According to [the proposal specification](https://arai-a.github.io/ecma262-compare/?pr=2417&id=sec-createdecoratoraccessobject), only the `get` and `set` property should vary in their presence depending on the type of target being decorated. The `has` method is supposed to be present in the context of every decorator type (other than `"class"`, obviously).

Here's a quick reproduction:

```ts
const example = (target, context) => {
  const { name, kind } = context;
  console.log(
    `name: "${name.toString()}"\nkind: ${
      context.kind
    }\n"access" in context => ${
      ("access" in context)
    }\n"has" in context.access => ${
      ("has" in context.access)
    }\n"get" in context.access => ${
      ("get" in context.access)
    }\n"set" in context.access => ${
      ("set" in context.access)
    }\n`,
  );
};

// quick, non-exhaustive demo with various target types
class Foo {
  @example someMethod() {/* ignore */}

  @example get someGetter() {
    return true;
  }

  @example set someSetter(_) {/* ignore */}

  @example accessor foobar = "bazbuzz";

  @example fieldOfBrokenDreams = "change me";
}
```

And the output of the above code is:

```ts

name: "someMethod"
kind: method
"access" in context => true
"has" in context.access => false
"get" in context.access => true
"set" in context.access => false

name: "someGetter"
kind: getter
"access" in context => true
"has" in context.access => false
"get" in context.access => true
"set" in context.access => false

name: "someSetter"
kind: setter
"access" in context => true
"has" in context.access => false
"get" in context.access => false
"set" in context.access => true

name: "foobar"
kind: accessor
"access" in context => true
"has" in context.access => false
"get" in context.access => true
"set" in context.access => true

name: "fieldOfBrokenDreams"
kind: field
"access" in context => true
"has" in context.access => false
"get" in context.access => true
"set" in context.access => true
```

Notice that `"has" in context.access` always results in `false`.
Repository: node
Issue: `parallel/test-http-correct-hostname` fails on "node-test-commit-loongarch64/nodes=clfs23-64"
Labels: flaky-test

### Test

test-http-correct-hostname

### Platform

Other

### Console output

```console
not ok 3701 parallel/test-http-correct-hostname
  ---
  duration_ms: 120017.77300
  severity: fail
  exitcode: -15
  stack: |-
    timeout
  ...
```


### Build links

```
https://ci.nodejs.org/job/node-test-commit-loongarch64/nodes=clfs23-64/75/console
```

### Additional information

Hi,

log: https://ci.nodejs.org/job/node-test-commit-loongarch64/nodes=clfs23-64/75/console

In common user machines, the test case can pass normally. I guess it is the machine local area network problem of "node-test-commit-loongarch64/nodes=clfs23-64". It is recommended to skip this test item for the time being.

Best regards
Repository: pytorch
Issue: Incorrect Results from cdist_backward Operator with Input Dimensions Exceeding int32_max
Labels: needs reproduction,triaged,module: 64-bit,module: edge cases

### 🐛 Describe the bug

## Issue Description
I've encountered an issue where the `cdist_backward` operator produces incorrect results when either of its input dimensions `r1 * M` or `r2 * M` exceed the maximum value for `int32` (2,147,483,647). This seems to suggest that there might be an integer overflow happening internally when computing large tensors.

### To Reproduce
Steps to reproduce the behavior:
1. Use `cdist_backward` operator with inputs that result in dimensions `r1 * M` or `r2 * M` exceeding `int32_max`.
2. Observe incorrect computation results.

```python
# Sample code to reproduce the issue
import torch

# Example tensor dimensions that cause the issue
# Please replace this with the specific dimensions you used
tensor1 = torch.randn([1,1024,1024 * 2050])
tensor2 = torch.randn([1,1024,1024 * 2050])

# Code to demonstrate the issue
result = torch.cdist_backward(tensor1, tensor2, p=2)
print(result)
```
### Possible Cause and My Understanding
Based on my observations and tests, I suspect that the issue might be related to integer overflow within the `cdist_backward` operator's internal computation. This is because the problem occurs when the input dimensions, when multiplied (`r1 * M` or `r2 * M`), exceed the maximum value that an `int32` can represent (2,147,483,647). 
This overflow could potentially cause the internal index calculations or memory allocations to

located the overflow : https://github.com/pytorch/pytorch/blob/7bcf7da3a268b435777fe87c7794c382f444e86d/aten/src/ATen/native/cuda/DistanceKernel.cu#L133
```c++
const int l = y / r_size;
const int k = y % r_size;
const int stride = blockDim.x * gridDim.x;
const int l_size = r_size * m;
```

### Versions

 torch2.1/torch1.13/torch1.9
Repository: kubernetes
Issue: GetDeviceBindMountRefs not effective
Labels: kind/bug,sig/storage,lifecycle/rotten,needs-triage

### What happened?

Even if multiple block device files exist in `/var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/<pv-name>/dev/`, `GetDeviceBindMountRefs` returns nil.

### What did you expect to happen?

It returns what are present in that directory

### How can we reproduce it (as minimally and precisely as possible)?

Hard to reproduce. But with a simple Go program, we can see the error:
```go
func main() {
	entries, err := os.ReadDir(os.Args[1])
	if err != nil {
		panic(err)
	}
	for _, entry := range entries {
		println(entry.Name(), entry.Type())
	}
}
```
Run this with `./main /var/lib/kubelet/plugins/kubernetes.io/csi/volumeDevices/*/dev/`. It outputs:
```
364c407c-5603-4338-9e86-fc8e5a3c5153 0
ceebc348-9906-4d2c-a730-07d56f6105c5 0
```

### Anything else we need to know?

`os.ReadDir` reads the directory in the system filesystem (maybe ext4), which does not know the mounted block device file (in devtmpfs) over it. So, it always returns the information about the hidden regular file.

However, I suspect we may have possible leakage here. We may need to check carefully for leakage before fixing this. Or we will break existing setup. Specifically, we write 5 global states when a CSI volumeDevice is in use.

1. `/plugins/kubernetes.io/csi/volumeDevices/staging/<pv>/<pv>`
2. `/plugins/kubernetes.io/csi/volumeDevices/publish/<pv>/<pod uid>`
3. `/plugins/kubernetes.io/csi/volumeDevices/<pv>/dev/<pod uid>`
4. `/pods/<pod uid>/volumeDevices/kubernetes.io~csi/<pv>`    symlink to 2
5. loop device

`GetDeviceBindMountRefs` checks for 3, volume reconstruction after kubelet restart checks for 4. Then 1-3 may leak and `GetDeviceBindMountRefs` may fail if 1-3 success but 4 does not.


### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.29.0
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.3-aliyun.1
```

</details>


### Cloud provider

<details>
Alibaba Cloud
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
NAME="Alibaba Cloud Linux"
VERSION="3 (Soaring Falcon)"
ID="alinux"
ID_LIKE="rhel fedora centos anolis"
VERSION_ID="3"
UPDATE_ID="9"
PLATFORM_ID="platform:al8"
PRETTY_NAME="Alibaba Cloud Linux 3 (Soaring Falcon)"
ANSI_COLOR="0;31"
HOME_URL="https://www.aliyun.com/"

$ uname -a
Linux iZ2zeecp36u39wxvdec6i8Z 5.10.134-16.1.al8.x86_64 #1 SMP Thu Dec 7 14:11:24 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: storybook
Issue: [Bug]: Ember App not re-loading
Labels: bug,help wanted,ember

### Describe the bug

The way to use ember with storybook is starting the ember app, which starts its own server and serves its `dist` folder. That ember server also has its livereload to push changes. Using the `dist` actually makes use of that livereload mechanics.

However, with storybook's config, you use the `staticDirs`:

```ts
import type { StorybookConfig } from '@storybook/ember';

const config: StorybookConfig = {
  // ...
  staticDirs: ['../dist'],
};
export default config;
```

It looks like, this is **very** _static_ - I currently receive no auto updates.

I consider this to be a more tracking issue, to share this in the ember discord, when things pop up and to gain knowledge within this ticket. 

### To Reproduce

Setup:

```
ember new
npx storybook@next init
```

1. Create a component + story
2. Start the ember server
3. Start storybook
4. Navigate to the story
5. Change the component

Expected Behavior: See the change in storybook


### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.1
    CPU: (11) arm64 Apple M3 Pro
    Shell: 3.6.4 - /opt/homebrew/bin/fish
  Binaries:
    Node: 20.11.0 - ~/.volta/tools/image/node/20.11.0/bin/node
    Yarn: 1.22.21 - ~/.volta/tools/image/yarn/1.22.21/bin/yarn
    npm: 10.2.4 - ~/.volta/tools/image/node/20.11.0/bin/npm
    pnpm: 8.14.3 - ~/.volta/tools/image/pnpm/8.14.3/bin/pnpm <----- active
  Browsers:
    Chrome: 121.0.6167.139
    Edge: 120.0.2210.144
    Safari: 17.1
  npmPackages:
    @storybook/addon-essentials: 8.0.0-beta.0 => 8.0.0-beta.0
    @storybook/addon-links: 8.0.0-beta.0 => 8.0.0-beta.0
    @storybook/blocks: 8.0.0-beta.0 => 8.0.0-beta.0
    @storybook/ember: 8.0.0-beta.0 => 8.0.0-beta.0
    @storybook/ember-cli-storybook: ^0.6.1 => 0.6.1
    @storybook/test: 8.0.0-beta.0 => 8.0.0-beta.0
    eslint-plugin-storybook: ^0.6.15 => 0.6.15
    storybook: 8.0.0-beta.0 => 8.0.0-beta.0
```

### Additional context

_No response_
Repository: godot
Issue: Debug session over wifi have not started with android device
Labels: bug,platform:android,topic:editor,topic:export

### Tested versions

- Reproduces in godot: 4.2 stable .net. 
- Phone: Pixel 4a, android 13
- Tablet: Redmi Pad SE, android 13

### System information

Windows 10, Godot 4.2 stable .net

### Issue description

Debug session over wifi have not started with android device. Application builds, deploys and runs on android device but programm execution is not paused on break points. GD.Print() messages don't appear in debug output window.

### Steps to reproduce

1) create godot project
2) set node 2d scene
3) add script for node from step 2
4) in process method in script from strp 3 add print function with some text
5) Install export template
6) Install android build template
7) Set checkbox: deploy with Remote debug
8) Configure android SDK and debug keys in Editor->Editor settings->Export->Android
9) Set checkbox Import ETC2 ASTC in project settings
10) Add export presets for android
11) connect phone/tablet with adb to computer
12) Press remote debug button-> your device name

Expected result: 
- application should be uploaded to device and started
- debug session should start in godot editor

Actual result
- application  is uploaded to device and started
- debug session DOES NOT start in godot editor


### Minimal reproduction project (MRP)

[GodotEmpty.zip](https://github.com/godotengine/godot/files/14156805/GodotEmpty.zip)
Repository: godot
Issue: False positive unsafe_call_argument with variant
Labels: discussion,topic:gdscript,confirmed,documentation

### Tested versions

4.2.1.stable.arch_linux
 

### System information

Linux 6.7.2-arch1-1

### Issue description

```
func foo(_a):
	pass

func bar():
	var x = []
	foo(x)
```

The last line shows the warning:

```
(UNSAFE_CALL_ARGUMENT): The argument 1 of the function "foo()" requires the subtype "Variant" but the supertype "Variant" was provided.
```

It should be safe to pass a variant to a function with no type annotation. The error message seems to contradict itself anyhow.

### Steps to reproduce

1. Enable `unsafe_call_argument` warning
2. Write the code in the issue description

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: create "dir"-lists with a right mouse button
Labels: Product-File Explorer,Needs-Triage

### Description of the new feature / enhancement

To create cover letters, lists, etc., I often use a batch script with which I can write the contents of folders to a TXT file. I then use the list of the TXT file to document the contents of the folders, in the letters, lists, etc.
It would be very helpful if the cmd commands, among others, could be accessed via a power toy via an additional entry in the Explorer's context menu.

### Scenario when this would be used?

- I comment with the lists of the TXT file
in cover letters, which documents accompany a letter
- The function is helpful for creating tables of contents
- When passing on links to directories in MS SharePoint, I include the lists in order to document which files can be found under the link. Especially if the link is distributed to third parties outside of my organization.
- In Windows 10 it was possible to insert a shortcut to the batch script into the context menu via the "SendTo" directory. With Windows 11 this no longer seems to be possible, so you can only have the selected directory displayed in a corresponding list by dragging and dropping it onto the batch file. This is very cumbersome compared to an entry in the Explorer context menu

### Supporting information

Here is the content of my batch file, which documents the functions most easily

dir %1\*.* /B /ON > d:\pdf-files\dirlist.txt
tree %1 /F /A > d:\pdf-files\dirtree.txt
d:\notepad++\notepad++.exe d:\pdf-files\dirlist.txt d:\pdf-files\dirtree.txt
Repository: PowerToys
Issue: Power Rename - Context Menu
Labels: Issue-Bug,Product-PowerRename,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerRename

### Steps to reproduce

The context menu for the right click now has the full text of "Rename with PowerRename", which in turn causes Windows 11 to set at 125% scaling and 1440p resolution causing a problem where the context menu stretches too much which was not a problem the earlier version.
![1](https://github.com/microsoft/PowerToys/assets/72495317/63f37c91-d684-49f9-855d-577f02738c37)
![2](https://github.com/microsoft/PowerToys/assets/72495317/c72c8ee8-9f33-41a2-a3bc-14341b6398bd)



### ✔️ Expected Behavior

The context menu had the entry as just "PowerRename" and worked perfectly and fit nicely.

### ❌ Actual Behavior

Stretches the context menu which causes glitches and a weird look.

### Other Software

_No response_
Repository: godot
Issue: EditorExportPlatformAndroid object doesn't contain expected properties at export time
Labels: documentation,topic:plugin,topic:export

### Tested versions

- Reproducible in Godot 4.2.1.stable

### System information

Windows 11 - Android 13 export

### Issue description

I have an Android export plugin where I am overriding `_get_android_manifest_application_element_contents()` and trying to get the `package/unique_name` property from the `EditorExportPlatformAndroid` object as follows:

```
class AndroidExportPlugin extends EditorExportPlugin:
	...
	func _get_android_manifest_application_element_contents(platform: EditorExportPlatform, debug: bool) -> String:
		...
		if platform is EditorExportPlatformAndroid:
			var __unique_name = platform.get("package/unique_name")
```

However, the `package/unique_name` property is not set in the `platform` argument object.

`platform.get("package/unique_name")` returns `null`.

### Steps to reproduce

- Open MRP in Godot Editor
- Install Android build template
- Debug MRP on an Android device
- Check console output

### Minimal reproduction project (MRP)

[editor-export-platform.zip](https://github.com/godotengine/godot/files/14157093/editor-export-platform.zip)
Repository: godot
Issue: Apply_floor_snap() method of CharacterBody3D does not update the velocities after the snapping.
Labels: enhancement,documentation,topic:physics

### Tested versions

4.2.1 stable. reproducible since the method was introduced.


### System information

Fedora workstation

### Issue description

When the discussions about the new `CharacterBody3D` were taking place, the necessity to snap the character regardless of the up velocity resulted in the `apply_floor_snap() `method by fabriceci (https://github.com/godotengine/godot/pull/73749). Now that we are working on a full refractioning of our game Liblast, i had the time to test it's functionality.

After quite a lot of head scratching, I think I isolated the problem. 

The method is meant to force an snapping of the body to the floor even if there is vertical velocity applied. The body snaps correctly, but it's velocity never takes that into account. As a result the body will remain snapped, but it's vertical velocity will continue increasing as if the snapping never happened. This leads to an accumulation of vertical velocity on the body, making it jump when the delta velocity on the vertical axis scape from the snapping vector.


### Steps to reproduce

I made my best to reproduce the issue in the following MPR.  The character body starts above the floor and falls down due to gravity until it reaches the floor. Once we have reached the floor, an small vertical force is applied. The character remains still until it scape and jump after around 4 seconds.

### Minimal reproduction project (MRP)

[Apply_floor_snap bug.zip](https://github.com/godotengine/godot/files/14157203/Apply_floor_snap.bug.zip)
Repository: PowerToys
Issue: sarting ALL last open programms, tabs and so on after reboot (without activated hibernating)
Labels: Needs-Triage

### Description of the new feature / enhancement

title says all ;)

### Scenario when this would be used?

after every boot/logon

### Supporting information

_No response_
Repository: Web-Dev-For-Beginners
Issue: Incorrect link text
Labels: no-issue-activity

**Describe the bug**
[1-getting-started-lessons/1-intro-to-programming-languages/README.md under the heading "Popular Editors and Web Development Extensions"](https://github.com/microsoft/Web-Dev-For-Beginners/tree/main/1-getting-started-lessons/1-intro-to-programming-languages#popular-editors-and-web-development-extensions)
- The link text for Sublime Text says "www.sublimetext"
- Nowhere on the page does it say that Atom has been deprecated

**To Reproduce**
Steps to reproduce the behavior:
1. Go to [the file previously mentioned](https://github.com/microsoft/Web-Dev-For-Beginners/tree/main/1-getting-started-lessons/1-intro-to-programming-languages#popular-editors-and-web-development-extensions)
2. Look at the link text for Atom and the link text for Sublime Text
3. See error

**Expected behavior**
- The link text for Sublime Text is correct
- The page mentions at least somewhere that Atom has been deprecated

**Screenshots**
If applicable, add screenshots to help explain your problem.
![image](https://github.com/microsoft/Web-Dev-For-Beginners/assets/150592702/6cec5ab0-f895-4946-b236-90f48c837b55)


**Desktop (please complete the following information):**
 - OS: Does not matter
 - Browser Does not matter
 - Version Does not matter

**Smartphone (please complete the following information):**
 - Device: Does not matter
 - OS: Does not matter
 - Browser Does not matter
 - Version Does not matter

**Additional context**
Add any other context about the problem here.
Repository: angular
Issue: feat: sec for security type
Labels: area: dev-infra

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

core

### Description

When contributors are making changes, I want them to easily prefix their commits using Conventional Commits, so they distinguish the type of the commit, including security type changes.

When I'm reading through commits, I want an easy way to quickly distinguish them, so their purpose is clear including security updates.

Contributors can select types:
```
feat:
fix:
build:
chore:
ci:
docs:
perf:
refactor:
revert:
style:
test:
```

### Proposed solution

Contributors would be able to select `sec:` for a security type changes.

### Alternatives considered

n/a
Repository: next.js
Issue: Rewrite to page that redirects (301, 302, etc) results in internal URL change
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/silent-brook-qh9zv9?file=%2Fmiddleware.ts%3A16%2C5&workspaceId=eaa85a37-24ba-4d57-a316-bcdf1a6ac9c8

### To Reproduce

**TLDR;**

1. Navigate to codesandbox reproduction
2. Inside of Codesandbox preview, navigate to `/assets/image/location/310/310/ADA.webp`
3. Pathname will be changed to `/static/cities/310x310/2690.webp`

**More detailed description of what's going on:**

I have the following code in my NextJS middleware to handle images fetching
```ts
  if (LOCATION_IMAGE_REGEX.test(request.nextUrl.pathname)) {
    const matches = request.nextUrl.pathname.match(LOCATION_IMAGE_REGEX);
    const width = matches.at(1);
    const height = matches.at(2);
    const code = matches.at(3);
    const extension = matches.at(5);

    return NextResponse.rewrite(`https://photo.hotellook.com/static/cities/${width}x${height}/${code}.${extension}`);
  }
```
This code is supposed to take pathname `/assets/image/location/310/310/ACI.webp` and rewrite it to `https://photo.hotellook.com/static/cities/310x310/ACI.webp`. It worked just fine until `https://photo.hotellook.com/static/cities/310x310/ACI.webp` started redirecting to `https://photo.hotellook.com/static/cities/310x310/30295.webp`. So now URLs in my own app is changing from `assets/image/location/310/310/ACI.webp` to `/static/cities/310x310/30295.webp` and image obviously cannot be found

### Current vs. Expected behavior

Current behavior: rewrite URL can be affected by third party resources.
Expected behavior: rewrite should follow redirects

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023
Binaries:
  Node: 18.14.0
  npm: 9.3.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.5.6
  eslint-config-next: 13.1.1
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.4
Next.js Config:
  output: standalone
```


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

Middleware / Edge (API routes, runtime)

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

next start (local)

### Additional context

Issue is present in both canary (as of 04.02.2024) and 13.5.6 (currently in production)