sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Add `hidden` and `internal` task options
Labels: suggestion,task runner

The recent "Task dependencies" feature is great task composition method but I think there is 2 missing options.
- `hidden`: that allow to hide a task from tasks list but kept callable (eg: when it is only used as dependency or for legacy purposes, ...)
- `iternal`: that allow to hide a task from tasks list and not callable (eg: task used as dependency only, part of a command that was split, framework required logic, ...)

```json
{
  "tasks": {
    "build:css_legacy": {
      "command": "...",
      "hidden": true
    },
    "build:css": {
      "command": "...",
      "hidden": true
    },
    "build:assets": {
      "command": "...",
      "hidden": true
    },,
    "framework_build_config": {
      "command": "...",
      "internal": true
    },
    "build": {
      "command": "...",
      "dependencies": ["framework_build_config", "build:css", "build:html"]
    },
    "long_command": {
      "command": "...",
      "dependencies": ["long_command_part:a", "long_command_part:b", "long_command_part:c"]
    },
    "long_command_part:a": {
      "command": "...",
      "internal": true
    },
    "long_command_part:b": {
      "command": "...",
      "internal": true
    },
    "long_command_part:c": {
      "command": "...",
      "internal": true
    },
  }
}
```

Give the following output:

```sh
deno task

- build
    ...
- long_command
    ...
```

And the following behaviour:

```sh
deno task build:css
# ok

deno task framework_build_config
> Task not found: framework_build_config
# //or more specific message like
> Task is internal: framework_build_config
```
Repository: rust
Issue: std assumes that accessing an already-initialized TLS variable is async-signal-safe
Labels: A-runtime,A-thread-locals,C-bug,T-libs

TLS accesses are not documented to be async-signal-safe, but they mostly are – except for the first access to a variable. We rely on that: we install signal handlers that access thread-local variables, but we ensure they have been accessed before setting up the signal handler. This would be a good thing to discuss with the runtimes we depend on, since hopefully they can provide this as an actual guarantee, or else we'll learn that we can't rely on it.

@joboet @the8472  in terms of interaction with POSIX, what exactly are we relying on here? Or are the kind of TLS variables we are using not part of POSIX? Is it a libc thing, a linker thing, or something else?
Repository: opencv
Issue: discrepancy in constants defined between the core modules and the Objective-C (objc) bindings in OpenCV 5.x
Labels: bug,platform: ios/osx,category: swift/objc bindings

### System Information

OpenCV version: 5.x
Operating System / Platform: Ubuntu 22.04
Compiler & compiler version: GCC 11.3.0

OpenCV Python version: 5.x
Operating System / Platform: Windows 11
Python version: 3.11.4

OpenCV version: 5.x
Operating System / Platform: macOS 13 Ventura
Development Environment: Xcode 14.0, Swift 5.7


### Detailed description

Description of the Bug
When using OpenCV 5.x Objective-C bindings, the matrix operations fail due to mismatched constant definitions in CvTypeExt.swift and the core OpenCV module. The Objective-C binding uses CV_CN_SHIFT = 3, but the core module defines CV_CN_SHIFT = 5. This causes incorrect matrix depth calculations.


Observed Behavior
The code crashes or produces an incorrect matrix with fewer channels than expected.

Expected Behavior
The matrix should be created with a depth supporting 128 channels, as defined by the core module constants.

Error Log
''' [ERROR]: Assertion failed in core.cpp, line 123: invalid depth for 128-channel matrix '''

This issue seems to be caused by outdated constants in CvTypeExt.swift. The constants CV_CN_SHIFT and CV_DEPTH_MAX in the Objective-C bindings need to match those in the core module.

### Steps to reproduce

Setup Environment:

OpenCV version: 5.x
Platform: macOS 13 Ventura
Compiler: Xcode 14.0, Swift 5.7

Code to Reproduce:
'''
#import <opencv2/opencv.hpp>
#import <iostream>

using namespace cv;

int main() {
    // Attempt to create a matrix with 128 channels
    try {
        Mat matrix = Mat::zeros(3, 3, CV_8UC128); // This will fail due to mismatched constants
        std::cout << "Matrix created successfully!" << std::endl;
        std::cout << "Matrix depth: " << matrix.depth() << std::endl;
        std::cout << "Matrix type: " << matrix.type() << std::endl;
    } catch (const cv::Exception& e) {
        std::cerr << "OpenCV Exception: " << e.what() << std::endl;
    }
    return 0;
}

'''

Expected Outcome:
The matrix should be created successfully, supporting 128 channels, with the depth consistent with the CV_CN_SHIFT defined in the core module.
Observed Outcome:
The code fails with an assertion error or unexpected behavior due to the mismatch between CV_CN_SHIFT and CV_CN_MAX in the Objective-C bindings and the core module.


No related data files (images, ONNX, etc.) are needed to reproduce this issue. The problem lies in the mismatched constant definitions in the Objective-C bindings, and the provided code snippet is self-contained.





### 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: rust
Issue: Support non-UTF-8 in environment variable dependency tracking
Labels: T-compiler,C-discussion

[`ParseSess::env_depinfo`](https://github.com/rust-lang/rust/blob/6c76ed5503966c39381fac64eb905ac45e346695/compiler/rustc_session/src/parse.rs#L226) stores `Symbol` instead of `OsStr`.

While we're at it, might make sense to actually not store the environment variable value at all, and instead fetch it inside `write_out_deps`? (which assumes that the variable won't change during execution of the compiler, but it probably won't).

See also https://github.com/rust-lang/rust/pull/130883#discussion_r1864384740.
Repository: opencv
Issue: How do I get the address of cv::cuda::GpuMat?
Labels: question (invalid tracker),category: gpu/cuda (contrib)

### System Information

function cudaMemcpyAsync **invalid argument**

### Detailed description

When I use function cudaMemcpyAsync copy memory DeviceToDevice,the second parameters need to pass the **device address of blob_img_GPU**,How should I specify it? In my code, I use blob_img_GPU.ptr(),but it is fault. When I run the code，error with invalid argument.

### Steps to reproduce

```cpp
for (int batch_idx = 0; batch_idx < _batch_size; ++batch_idx)
{
	letterbox(images[batch_idx], blob_imgs_host[batch_idx], size);
	cv::cuda::GpuMat blob_img_GPU;
	blob_img_GPU.upload(blob_imgs_host[batch_idx]);
	cout << "pointer_host:" << blob_imgs_host[batch_idx].ptr<float>() << endl;
	CHECK(cudaMemcpyAsync(
		(char *)_device_ptrs[0] + batch_idx * total_elements * blob_img_GPU.elemSize(),
		blob_img_GPU.ptr<float>(),
		total_elements * blob_img_GPU.elemSize(),
		cudaMemcpyDeviceToDevice,
		_stream));
}
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: kubernetes
Issue: Improper Permissions on ConfigMap and Secret Mounts
Labels: sig/storage,sig/node,kind/feature,sig/security,needs-triage

### What would you like to be added?

Hey, I am opening this issue publicly as it was approved by a member of the Kubernetes staff on HackerOne (#2867563) to be discussed with the larger community. Since addressing it would break existing users, it may require a Kubernetes Enhancement Proposal (KEP). The staff member also agreed that it is a poor default.

# Description
Kubernetes mounts ConfigMaps and Secrets to containers with default permissions -rw-r--r-- (644) also the permission on the ConfigMaps and Secrets directories mounted to the container is set to -rwxrwxrwx (777),
This configuration allows any user in the container, not just the root user, to read these files, exposing sensitive data and violating the principle of least privilege.
In multi-user containers, any non-root user can access these ConfigMaps and Secrets, further increasing the risk of unauthorized data exposure.
To prevent this, users can use the defaultMode parameter to set stricter permissions, such as 600/750, ensuring only the root user has access.
The current default behavior conflicts with the principle of least privilege, making manual adjustment necessary to protect sensitive data.

# Steps To Reproduce:
1. Create a Kubernetes ConfigMap or Secret.
2. Mount the ConfigMap or Secret into a container.
```
apiVersion: v1
kind: Pod
metadata:
  name: secret-mounted-pod
spec:
  containers:
    - name: my-app
      image: nginx:latest
      securityContext:
        runAsUser: 1000
      volumeMounts:
        - name: secret-volume
          mountPath: "/etc/secret"
          readOnly: true
  volumes:
    - name: secret-volume
      secret:
        secretName: my-secret
```
3. Run the container with multiple users, including a non-root user (e.g., user ID 1000).
4. Observe that the default permissions are -rw-r--r-- and that any non-root user can read the mounted data.


### Why is this needed?

To mitigate this risk, we need to ensure that the directory and the mounted files of Configmaps/Secrets have permissions set to 750. This setting allows only the root user and the group owner to read and execute, while preventing access by other users.
his approach limits read access to the root/owner only, thereby following the principle of least privilege and reducing unauthorized exposure of sensitive data.
Repository: godot
Issue: Visual Shaders Texture2DParameter can't be turned into constant (Unlike other Parameter nodes)
Labels: enhancement,topic:editor,topic:shaders

### Tested versions

4.3 Stable

### System information

Windows 10 x64 (But not related to the issue)

### Issue description

![Image](https://github.com/user-attachments/assets/3707bfab-3e93-4f13-83a7-e1b091339875)
![Image](https://github.com/user-attachments/assets/a14f85de-a231-487e-b35b-486be46c9e52)
![Image](https://github.com/user-attachments/assets/dbf4da52-588c-4fbc-ade2-d77d6932a132)

1. Currently, Texture2DParameter is required in Visual Shaders to properly set Filtering, Texture Repeat, and more. There are no ways to convert it into Constant (even if the workflow doesn't require the user to change it later, and it should be permanent for all instances of the shader).
2. Texture node by default Does Not have features to Repeat or Filter the stored texture. It ignores Repeat settings of the node where used.
3. All other Parameter nodes can be converter into their Constant versions.

### Steps to reproduce

Make Texture2DParameter, try to make it a Constant

### Minimal reproduction project (MRP)

N/A
Repository: go
Issue: x/crypto/x509roots: apply constraints with CertPool.AddCertWithConstraint
Labels: Security,NeedsFix

Now that #57178 has landed, we should use CertPool.AddCertWithConstraint to apply nss.Constraint values.

In particular, the Entrust root now has [a Distrust After of November 30, 2024 that we need to apply](https://sslmate.com/blog/post/entrust_distrust_more_disruptive_than_intended).

/cc @golang/security
Repository: tauri
Issue: In the Tauri project development, how to implement the name change of the Tauri menu?
Labels: type: documentation

In the Tauri project development, how to implement the name change of the Tauri menu?

Mainly used in multi-language development, such as English: Copy in Chinese: copy, just change the display name, do not change the shortcut key event operation, thank you.



The current project is using Tauri 1.x
Repository: godot
Issue: Changing scene twice in `_ready` fails to call `_ready` on final scene
Labels: bug,topic:core

### Tested versions

Reproducable in 4.3-stable

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 (NVIDIA; 32.0.15.6094) - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 Threads)

### Issue description

Create a series of 3 scenes with attached scripts. Scene 1 contains a call to change the scene to scene 2 in it's ready method:
```gdscript
func _ready():
	print("First scene")
	get_tree().change_scene_to_file("res://SecondScene.tscn")
```
Scene 2 then does a similar operation in `_ready`, changing the scene to scene 3.
```gdscript
func _ready():
	print("Second scene")
	# await get_tree().create_timer(0.01).timeout
	# Uncommenting this line fixes the issue /\
	get_tree().change_scene_to_file("res://ThirdScene.tscn")
```
This (as far as I am aware) should result in scene 3 being the currently active scene, however, a script attached to scene 3 does not have it's `_ready` method called once these transitions occur. Scene 3's `_init` method is successfully called however.


### Steps to reproduce

Run the attached project, note that the message "Third scene ready" is not printed. However, uncommenting the `await` call in `second_scene.gd` will produce the correct behaviour.

### Minimal reproduction project (MRP)

[scene_change_bug.zip](https://github.com/user-attachments/files/17969295/scene_change_bug.zip)
Repository: PowerToys
Issue: Make a tool to disable/reenable mouse devices on standby/wakeup
Labels: Idea-New PowerToy,Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

a PowerToys that disable mouse devices when a standby is initiated, and reenable them when computer resumes

it would be a good workaround to the issue of Windows 11 and Modern Standby reacting to mouse events.

### Scenario when this would be used?

Since Windows 11 and Modern Standby, there is no way to tell Windows to not wake up the computer on mouse events
(powercfg /DEVICEDISABLEWAKE or checkbox in device manager are ignored)

That's a common annoying problem because the computer often wakes-up immediately after standby (as our hand release the mouse) or may cause laptops to wakeup unexpectedly in bags and overheat.

So unless Windows teams plan to fix that problem very soon, a tool as described above would be nice

### Supporting information

See https://www.reddit.com/r/thinkpad/comments/sbql0n/disable_usb_mouse_from_waking_up_device_from_sleep/
for more discussion on the subject
(in particular, people under W11, like me, saying the trivial solution is not working)
Repository: TypeScript
Issue: Generic function with function as argument autocomplete broken, unless generic argument of the argument function is it's first argument
Labels: Suggestion,Help Wanted,Experience Enhancement

### 🔎 Search Terms

typescript generic function no autocomplete function as argument

### 🕗 Version & Regression Information

Relevant versions are 5.4.5 and above, tested in all versions from 5.4.5 to 5.8.0 (Nightly) inclusive, I was able to reproduce the bug in all versions.

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.2#code/IYZwngdgxgBAZgV2gFwJYHsIwE4FMDmqIyu2ACgDYKEQBCwAJgDwDyADsjLgB4kQMgYAJVxR02ZsWyoI+ADQxgEMAD4VACijAKFAEbAoAawBcMdcDZtTSsAvQcMEEKfbIAlDAC8KmADd0qAx2HM4wAHLoAJIQcKSsHCpupmTY6AC2RLhM-oE+AN4AvgBQRXiExKSU1DL0DOrmlsHIoXkwIOm4yAAWMvimUr0wBR7eMIUKeUUwMAD0MzC6uBToAO6KCMjoYmlsFJ24MEQLqYa4EAq4vmcw3ejUXTddB8hgbAdHbKlv2BRgftqBYAkBhTNodIrDADcJSKc0OEBIeGIvV+CmAGy26V2+xgK3EhkEqDgMAARPY0JgQCTFNh8Ag0mdONtcII4KhsMQFHBxFxuMAdntjEVQJBYIgUI4cAQiIiqjQAOLodDMVy8vgCYSicSSZDSWRo5RqTTaPQGExmcmOUKuNGWazKEY+HJBGDk0IRaKxbDxZCJZKpDIgLLO-LFUrSirkKgKpV1dRu0ytdoM7q9fq6wYFW1WRQOryhiaguGLZZrdGbbbYki4-EgUHJ3AQtyQoA

### 💻 Code

```ts
async function registerPluginBad<Opt extends Record<string, any>>(callback: (app: any, options: Opt) => void, opts: NoInfer<Opt>): Promise<void> {}

registerPluginBad((app, opts: { something: string }) => {}, {
  // below autocomplete is broken, even though the type is properly validated
  some
});


// interestingly, autocomplete works if "options" argument comes first, for example:
async function registerPluginGood<Opt extends Record<string, any>>(callback: (options: Opt, app: any) => void, opts: NoInfer<Opt>): Promise<void> {}

registerPluginGood((opts: { something: string }, app: any) => {}, {
  // below autocomplete works
  some
});
```


### 🙁 Actual behavior

This one has to be tested in the playground:
registerPluginBad - second argument does not autocomplete, however type is properly validated
registerPluginGood - exact same function, except the first argument "callback" arguments have changed the order, which for some reason fixes the autocomplete

### 🙂 Expected behavior

For both functions, autocomplete should work. Argument order should not matter.
Both do not infer from "opts", so any inference should be from "options" argument of the callback.

### Additional information about the issue

_No response_
Repository: go
Issue: proposal: require more information for proposals
Labels: Proposal

### Proposal Details

The current [proposal process](https://github.com/golang/proposal) for non spec changes is fairly lightweight for the proposer: there is a text box labeled "Proposal Details".

This has led to quite a large number of proposals, at the time of filing: [743 open proposals marked incoming](https://github.com/orgs/golang/projects/17), with a total of 636 filed this year so far, averaging 1.89 per day.

A recurring pattern in proposals is that they lack the detail: they'll often just vaguely describe a desired change. This results in some repetitive back and forth as we try to narrow it down to a specific api change that can be evaluated, and surface the motivations for the proposal.

I propose a 3 field proposal form that covers the majority of proposals we see:

* **Proposal summary:** in words, describe the proposal.
* **Motivation:** 
  * Describe why the change should be made
  * If this is already possible in a third party library, why it should be in the standard library
  * If this has previously been proposed and declined, what significant new information justified revisiting the decision.
  * Include references to external specs, code searches for frequent patterns, etc. 
* **Change details:** 
  * For API changes, the desired new api in godoc format, including comments.
  * For behavioural changes, the updated godoc describing the new behaviour.


cc @golang/proposal-review
Repository: pytorch
Issue: StrideAPI caused regression in channels-last logic
Labels: high priority,triaged,module: regression,module: mps

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/pull/128393 caused numerous performance/correctness regressions for the ops that had a special codepath for channels last, see 
- https://github.com/pytorch/pytorch/issues/141471
- https://github.com/pytorch/pytorch/issues/140902
- https://github.com/pytorch/pytorch/issues/137800
- https://github.com/pytorch/pytorch/issues/142344
Would be nice to have a better testing for those cases

### Versions

2.5.0, 2.5.1, nightly

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @kulinseth @albanD @DenisVieriu97 @jhavukainen
Repository: vscode
Issue: Checked Render whitespace is not shown when the Vscode is initialised at start
Labels: bug,editor-render-whitespace

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.82.2 (Universal)
- OS Version: Darwin arm64 23.4.0

Steps to Reproduce:

1. View -> Appearance
2. Validate the Render Whitespace check
3. Validate the whitespace is being shown or not
Repository: deno
Issue: `node:worker_threads` doesn't load passed in text as CommonJS
Labels: bug,node compat

Deno 2.1.2
```ts
const Worker = require("worker_threads");

const w = (new Worker(`const self = require("worker_threads");`, { eval: true }))();
```
```ts
error: Uncaught (in worker "[worker eval]") (in promise) ReferenceError: require is not defined
const self = require("worker_threads");
             ^
    at data:text/javascript,const self = require("worker_threads");:1:14

    info: Deno supports CommonJS modules in .cjs files, or when the closest
          package.json has a "type": "commonjs" option.
    hint: Rewrite this module to ESM,
          or change the file extension to .cjs,
          or add package.json next to the file with "type": "commonjs" option,
          or pass --unstable-detect-cjs flag to detect CommonJS when loading.
    docs: https://docs.deno.com/go/commonjs
```
`--unstable-detect-cjs` doesn't help.

In my original project, the worker is in .cjs (a third-party lib) and I import it from ESM. I guess it would work if everything was CJS.

`import("node:worker_threads")` (with node:) works, while the script that created the worker can use `require("worker_threads")`.
Repository: pytorch
Issue: Invalid `RPATH` for `_C.so` for in tree installation: assuption fail `"$ORIGIN/../.." -> site-packages`
Labels: module: binaries,triaged,topic: build,topic: binaries

### 🐛 Describe the bug

For in-tree installation, there is a `pytorch-xxx.pth` which contains:

https://github.com/pytorch/pytorch/blob/5deca07c0dcf1482eba99bf93b805cf1cc41ad6c/tools/nightly.py#L762-L771

points to the git repository.

The `torch` package is not installed in the `site-packages` directory.

```console
$ make setup-env-cuda PYTHON="/home/linuxbrew/.linuxbrew/bin/python3.12"
$ source venv/bin/activate
$ patchelf --print-rpath torch/_C.*.so | tr ':' '\n'
$ORIGIN/../../nvidia/cublas/lib
$ORIGIN/../../nvidia/cuda_cupti/lib
$ORIGIN/../../nvidia/cuda_nvrtc/lib
$ORIGIN/../../nvidia/cuda_runtime/lib
$ORIGIN/../../nvidia/cudnn/lib
$ORIGIN/../../nvidia/cufft/lib
$ORIGIN/../../nvidia/curand/lib
$ORIGIN/../../nvidia/cusolver/lib
$ORIGIN/../../nvidia/cusparse/lib
$ORIGIN/../../cusparselt/lib
$ORIGIN/../../nvidia/nccl/lib
$ORIGIN/../../nvidia/nvtx/lib
$ORIGIN
$ORIGIN/lib
```

For CUDA builds, the PyPI wheels require the `torch` package to be installed in the `site-packages` directory:

```console
$ python3 -c 'import torch'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/PanXuehai/Projects/pytorch/torch/__init__.py", line 378, in <module>
    from torch._C import *  # noqa: F403
    ^^^^^^^^^^^^^^^^^^^^^^
ImportError: libcudnn.so.9: cannot open shared object file: No such file or directory
```

https://github.com/pytorch/pytorch/blob/5deca07c0dcf1482eba99bf93b805cf1cc41ad6c/.ci/manywheel/build_cuda.sh#L178-L195

https://github.com/pytorch/pytorch/blob/5deca07c0dcf1482eba99bf93b805cf1cc41ad6c/.ci/manywheel/build_xpu.sh#L90-L95

Maybe related:

- #138506

### Versions

nightly

cc @seemethere @malfet @osalpekar @atalman