sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [RFC] Intel GPU ATen Operations Upstreaming Options
Labels: triaged,intel

### 🚀 The feature, motivation and pitch

This RFC is a consequence of #114835 in terms of XPU ATen operation upstreaming options.

To support the Inductor benchmarks, the Inductor needs to fall 91 operations back to ATen

- 9 ATen operations utilize libraries(OneDNN & OneMKL)
- 46 ATen operations are device-agnostic
- 36 ATen operations need SYCL code

Regarding the library-related and device-agnostic operations, they are straightforward to be upstreamed as in-tree directly.

In terms of the 36 ATen operations that need SYCL implementation, the line of code is about **16, 000**. And we have different upstreaming options.

- Option 1: Start from out-of-tree as a **git submodule** and move in-tree eventually
- Option 2: Start from out-of-tree as a separate branch and move in-tree eventually
- Option 3: Upstream in-tree directly

All three options follow the same implementation method; the primary difference lies in the code location.

To minimize community overhead before XPU gains wider adoption and to enable agile XPU development, we will start with an out-of-tree approach. Thus, at this moment, **Option 1** and **Option 2** are preferred.

However, hosting the 36 operations with 16,000 lines of code in a separate branch is burdensome:

- The synchronization/rebase effort for a separate branch is greater than that for a git submodule.
- A separate branch would introduce additional overhead in the release process and cadence compared to the git submodule option.
- Hosting XPU ATen operations in a separate branch could confuse PyTorch users, especially if the runtime and some ATen operations are upstreamed, while others are in a separate branch.

Considering these factors, we strongly recommend adopting the **git submodule(Option 1)** approach to host XPU ATen operations.

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet @seemethere @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @atalman @albanD
Repository: TypeScript
Issue: Support labels in template string
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

template string label
template string name
interpolation label

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

The idea is to allow the addition of labels into a template literal.
This has no effect on the type itself in any way, the sole purpose is to give a better DX.

These labels would be shown by IntelliSense in order to provide the same experience as labels for the tuple labels.

### 📃 Motivating Example

```ts
// Template literal today
type Options = {
   name: `${string}/${string}`;
}

// With labels
type Options = {
   name: `${scope: string}/${baseName: string}`;
}
```

### 💻 Use Cases

This would offer a slightly better DX. 
Right now you can document the parts of the template in a JSDoc comment, but the JSDoc is not preserve by IntelliSense in some cases.
Repository: godot
Issue:  Array.all() only runs only for the first array entry if the passed callable has no return value
Labels: enhancement,discussion,topic:gdscript

### Tested versions

v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1050 (NVIDIA; 30.0.14.7111) - Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 Threads)

### Issue description

The function Array.all() only runs only for the first array entry if the passed callable has no return value.
This is very error-prone.

It should run for all values. (So undefined return value means "true" and not "false")
Or at least a warning should be displayed in the editor that the return value is undefined. 

You can certainly argue about whether it is a bug or rather a suggestion. But I think that evil behavior is more on the bug-ish side.

### Steps to reproduce

        @tool
        extends EditorScript
        
        func _run() -> void:
	        var array_: Array[int] = [1,2,3,4]
	        # prints 1
	        array_.all(func(a): print(a))
        
	        # prints 1 2 3 4
	        array_.all(func(a): print(a); return true)


### Minimal reproduction project (MRP)

n/a
Repository: opencv
Issue: Big OpenCV Cleanup
Labels: feature,cleanup

### Describe the feature and motivation

We need to clean [OpenCV 5.0](https://github.com/orgs/opencv/projects/1) codebase, especially the main repository, in order to create room for new functionality and reduce maintenance effort.

This is the master ticket that refers to several child topics:

- [ ] (???) [Use standard C++ types in API](https://github.com/opencv/opencv/issues/24994)
- [ ] (WIP, multiple PRs) [Clean Core module](https://github.com/opencv/opencv/issues/25002)
- [ ] (WIP, multiple PRs) [Clean Imgproc module](https://github.com/opencv/opencv/issues/25001)
- [ ] (WIP, #25292) [Clean Features2D, rename it to Features](https://github.com/opencv/opencv/issues/24999)
- [ ] (WIP, #25708) [Replace FLANN with new smaller and better implementation](https://github.com/opencv/opencv/issues/24998)
- [x] [Clean Objdetect module](https://github.com/opencv/opencv/issues/25004)
- [x] [Move ML module to opencv_contrib](https://github.com/opencv/opencv/issues/24997)
- [x] [Remove OpenVX](https://github.com/opencv/opencv/issues/24995)
- [ ] (???) [Move IPP to opencv/3rdparty](https://github.com/opencv/opencv/issues/24996)
- [ ] [Move G-API to opencv_contrib or to the separate opencv/G-API repository](https://github.com/opencv/opencv/issues/25000)
- [x] [Clean Samples](https://github.com/opencv/opencv/issues/25006)

### Additional context

_No response_
Repository: vscode
Issue: Workspace Trust - Security restrictions per folder per extension
Labels: feature-request,workspace-trust

<!-- ⚠️⚠️ 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. -->
Use case:
Having both open source & closed source inside the same workspace, and while using extensions like co-pilot or codiumAI, I want to restrict specific extensions to prevent them from reading the closed source (to ensure it never leaves my local machine).

Trusting the vscode IDE does not mean I trust all plugins, and trusting a plugin with open source code does not mean I trust it with closed source code, which can be in the same workspace together (in different folders).

Feature request:
Restrict/Allow access per folder per extension in a single workspace.

Notes:
Running untrusted code in a container and mounting only the open source folders would be an obvious solution, however: the plugin setting this up should be under the same security constraints. A plugin with integration with vscode from a trusted publisher that could set this containerization up for any/all plugins in a generic way would satisfy this feature request.
Repository: go
Issue: proposal: flag: add All, AllSet iterators
Labels: Proposal

### Proposal Details

The flag package currently has Visit and VisitAll iterators, but unfortunately, the iterators don't return bool, so they aren't compatible with the range func experiment. I propose to add `All() iter.Seq[*Flag]`, `AllSet() iter.Seq[*Flag]`, and methods on FlagSet. The name "AllSet" isn't ideal, and I'm open to suggestions for better names.
Repository: storybook
Issue: [Bug]: @storybook/blocks - Check the render method of `ArgsTable`.
Labels: bug,sev:S3,upgrade:7.6

### Describe the bug

I'm trying to upgrade my storybook and to have from 7.4.1 to 7.6.14 and to have a clean install I also removed my yarn.lock file. Everything works as expected however the storybook/block fails when I use ArgTypes with the following error: Check the render method of `ArgsTable`.
A simple example of it is:

```jsx
import { Meta, Canvas, ArgTypes } from '@storybook/blocks';
import * as ButtonStories from './UnStyled.stories';

<Meta title="DCXLibrary/Form/Button/Documentation" />

Below a list of all the available properties:
<ArgTypes of={ButtonStories} />
```

### To Reproduce

here the repository with the relative file:

- https://github.com/Capgemini/dcx-react-library/blob/release/1.0.0/stories/Button/Documentation.mdx
- https://github.com/Capgemini/dcx-react-library/blob/release/1.0.0/stories/Button/UnStyled.stories.js


### System

```bash
danielezurico@Danieles-MacBook-Pro dcx-react-library % npx storybook@latest info

Storybook Environment Info:

  System:
    OS: macOS 14.2.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.14.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn <----- active
    npm: 9.3.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 121.0.6167.160
    Safari: 17.2.1
  npmPackages:
    @storybook/addon-a11y: ^7.6.14 => 7.6.14 
    @storybook/addon-actions: ^7.6.14 => 7.6.14 
    @storybook/addon-controls: ^7.6.14 => 7.6.14 
    @storybook/addon-docs: ^7.6.14 => 7.6.14 
    @storybook/addon-essentials: ^7.6.14 => 7.6.14 
    @storybook/addon-links: ^7.6.14 => 7.6.14 
    @storybook/addon-mdx-gfm: ^7.6.14 => 7.6.14 
    @storybook/addons: ^7.6.14 => 7.6.14 
    @storybook/blocks: ^7.6.14 => 7.6.14 
    @storybook/preset-typescript: 3.0.0 => 3.0.0 
    @storybook/react: ^7.6.14 => 7.6.14 
    @storybook/react-webpack5: ^7.6.14 => 7.6.14 
    @storybook/theming: ^7.6.14 => 7.6.14 
    chromatic: 6.24.1 => 6.24.1 
    eslint-plugin-storybook: 0.6.13 => 0.6.13 
    storybook: ^7.6.14 => 7.6.14 
    storybook-css-modules-preset: 1.1.1 => 1.1.1 
    storybook-design-token: 2.10.0 => 2.10.0
```

Here the branch where I was trying the upgrade: https://github.com/Capgemini/dcx-react-library/tree/feature/example-vite


```[tasklist]
### Tasks
```
Repository: PowerToys
Issue: Change FileLocksmith activation bahaviour
Labels: Idea-Enhancement,Status-In progress,Product-File Locksmith

### Description of the new feature / enhancement

Currently the selected files are written into a file and then read via the UI thread. We should use pipes like PowerRename does, as this is way more performant

### Scenario when this would be used?

Performance gains

### Supporting information

_No response_
Repository: PowerToys
Issue: full-width Japanese characters 
Labels: Product-Text Extractor

### Description of the new feature / enhancement

・！や？を全角で読み取るか、半角で読み取るか選択したい。
・読み取りたくない記号を設定したい　「」 ← 例

### Scenario when this would be used?

動画作成時の音声出力で読み上げさせる際

### Supporting information

_No response_
Repository: vscode
Issue: VSCode terminal seems to construct environment in a strange way
Labels: bug,workbench-os-integration,WSL,remote,web

<!-- ⚠️⚠️ 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.86.1 (commit 31c37ee8f63491495ac49e43b8544550fbae4533)
- OS Version: WSL2 (issue seems to reproduce on linux as well)

I initially posted this on [stackoverflow](https://stackoverflow.com/q/77978975/8278183) but after some more observations, it looks like a bug to me. First, here is the basic issue. I am starting vscode using the cli web server as `code serve-web`. I am using the following in `settings.json`:
```
{
    "terminal.integrated.profiles.linux": {
        "my-bash": {
            "path": "/usr/bin/bash",
            "args": ["--noprofile", "--norc"]
        },
    },
    "terminal.integrated.defaultProfile.linux": "my-bash"
}
```

To replicate my issue, put `export TMP_VARIABLE=10` in `/etc/profile.d/xxxx.sh` and run the following commands (on WSL/linux, not the vscode terminal).
```
$ export TMP_VARIABLE=3
$ export NEW_TMP_VARIABLE=100
$ code serve-web
```
In the vscode terminal, the newly created variable `NEW_TMP_VARIABLE` appears and is set to `100` (which is what I want). But for some reason, `TMP_VARIABLE` is still equal to `10`. Why is this happening?

How do I get vscode web server's terminal to use the variables in my current environment? And why does the `--noprofile` option not have the desired effect?

---

**Further observations**

If I add `echo 'profile.d is being read!!'` to `/etc/profile.d/xxxx.sh`, this statement is output each time I open a new terminal on WSL/linux. In vscode, if I change the shell args to `["--login"]`, I can see it output in the vscode terminal as well. But with args set to `["--noprofile", "--norc"]`, I don't see this echo. However, the value of `TMP_VARIABLE` is still set according to what's in `/etc/profile.d/xxxx.sh`, not according to the local environment. This makes me think vscode is starting a new login shell somewhere and copying its environment over in some strange way. I'm not sure, but seems to me like there is some bug here.
Repository: PowerToys
Issue: Bring Microsoft Management Console functionality into PowerToys
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Functionality that is currently contained within the MMC, like the event viewer, policy editor or device management should have some complementary equivalents in PowerToys, that simplify usage of said functionality.

For reference, similarly to how Registry Preview aims to be a simpler-to-use and more streamlined version of regedit, or Environment Variables being a much faster (and much better looking) way to access and modify environment variables compared to the native Windows dialogue, it'd be nice to see this philosophy be extended to MMC utilities such as the Event Viewer, the Scheduler or the Device Manager.

### Scenario when this would be used?

Many MMC applets, like the Scheduler or the Event Viewer, which can greatly help with automating tasks and efficiently diagnosing computer errors respectively, are an integral part of some power users' workflow. On their current state however, they are rather "hidden away"/burried and the outdated MMC UI tends to make navigation through the applets sluggish and a bit more difficult than it should be. Thus, creating a no-nonsense, modernized and simplified version of those applets can, in my opinion, greatly boost productivity to the afore mentioned power users, or even make the applets much more accessible to other users, helping them use Windows much more efficiently.
Repository: next.js
Issue: Type constraint error in useParams hook
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/page-params-constraint-hnx3fy

### To Reproduce

1. Open CodeSandbox and go to "/components/client.tsx".
2. The error should be visible in: useParams<PageParams>() (hover over "PageParams") .

### Current vs. Expected behavior

Whenever I try and add an interface to the useParams generic parameter like so:
```
export interface PageParams {
  storefront: string;
  product: string;
}

export function ClientComponent() {
  const params = useParams<PageParams>();
  return <div>{JSON.stringify(params, null, 4)}</div>;
}
```
 It displays the following error:
``Type 'PageParams' does not satisfy the constraint 'Params'. Index signature for type 'string' is missing in type 'PageParams'.typescript(2344)``
However, if we just change the interface into a "type" the error disappears and everything works fine:
````
export type PageParams = {
  storefront: string;
  product: string;
};

export function ClientComponent() {
  const params = useParams<PageParams>();
  return <div>{JSON.stringify(params, null, 4)}</div>;
}
````
I belive this to be a bug because since we use the file-system based routing in the app router, we shouldn't have to extend the generic "Params" that the useParams has by default right?
 Btw, for anyone facing the same issue this is the only way I found of fixing it while still using an interface:
````
interface Params {
  [key: string]: string | string[];
}

export interface PageParams extends Params {
  storefront: string;
  product: string;
}
````

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: pytorch
Issue: [56+] Graph-break if we try to Fakeify an "unknown" Tensor with no data_ptr.
Labels: low priority,triaged,small,oncall: pt2,module: dynamo

(56, 'Cannot access storage of BatchedTensorImpl', 'PYTORCH_TEST_WITH_DYNAMO=1 pytest test_legacy_vmap.py -v -k test_accepts_nested_inputs')

This will fix 56+ tests, including the ones in test_legacy_vmap.py.


cc @ezyang @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @msaroufim @bdhirsh @aakhundov
Repository: flutter
Issue: Dropdown menus should support animated open/close transitions
Labels: c: new feature,framework,f: material design,c: proposal,P2,team-design,triaged-design,:hourglass_flowing_sand:

The animated open and close transitions are covered here: https://m3.material.io/components/menus/guidelines#691d98ba-0375-4681-8c47-a5c3e7b58798

To avoid creating a backwards incompatibility, we could add an `AnimationStyle` parameter to DropdownMenu and MenuStyle whose (computed) default was `AnimationStyle.noAnimation`. If the backwards incompatibility isn't problematic, then it would make more sense for the animation to be enabled by default on mobile, but not on desktop.

See also (internal Google link): https://yaqs.corp.google.com/eng/q/676407458779889664
Repository: vscode
Issue: Debt: Find Safer way to parse settings from notebook settings within nb.cellEditorCustomizations
Labels: debt,notebook-cell-editor

Re: https://github.com/microsoft/vscode/pull/204783

see: https://github.com/microsoft/vscode/pull/204783/files#diff-4677a47fd6ba528332f9c7620a387a37bc7092af04591fdcb1a16701f8fe5951R97
Repository: go
Issue: proposal: time: Add functions for finding greatest or least time.Time supplied
Labels: Proposal

### Proposal Details

While attempting to port over from Ruby code to Go, I ran into an issue where I needed to set a variable of type `time.Time` to the maximum of three different times. The maximum here would apply to the farthest in the future time. In Ruby this involves putting the three times in an array and calling the max method on the array.  
```ruby
my_time = [someTime, someTime2, DateTime.now].max
```
This doesn't work in Go currently because the `slices.Max` method only works on slices where of type `cmp.Ordered` which `time.Time` is not. 
All `time.Time`'s can be converted to an int64 Unix representation which would satisfy the cmp.Ordered requirement for using `slices.Max` and `slices.Min`. However, this wouldn't work for times before 0 Unix time. 

I'd instead purpose adding `Min` and `Max` functions for the `time` package. They'd work by just using the `Before` and `After` methods that already exist in the package

```golang
func Max(x Time, y ...Time) Time {
	maxTime := x
	for _, val := range y {
		if val.After(maxTime) {
			maxTime = val
		}
	}
	return maxTime
}

func Min(x Time, y ...Time) Time {
	minTime := x
	for _, val := range y {
		if val.Before(minTime) {
			minTime = val
		}
	}
	return minTime
}
```

```golang
// Usage
thatTime := time.Max(someTime, someTime2, time.Now())
```

The function signature is just like the min and max built-in functions where at least one parameter is required, that way we can just return that value if no others are passed in. The first parameter would also just get used as our base for finding the min or max of the times. This also prevents us from unintentionally returning the time.Time zero value in the Min function
Repository: rust
Issue: Unexpected partial move in async move block for Copy field
Labels: A-lints,T-compiler,C-bug,D-edition,A-edition-2021

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

It is possible to write code which _looks_ like it should not compile and does not function as expected when trying to mutate Copy fields on a struct in an async move block.

I tried this code:

```rust
use futures::StreamExt;

#[derive(Debug)]
struct Foo { a: i32, b: i32 }

async fn work() -> Foo {
    let mut foo = Foo { a: 0, b: 0};
    let mut futs = futures::stream::FuturesUnordered::new();
    
    for i in 0..100 {
        foo.a += 1;
        
        futs.push(tokio::spawn(async move {
            foo.b += 1;
        }));
    }
    
    for i in 0..100 {
        futs.next().await;
    }
    
    foo
}

#[tokio::main]
async fn main() {
    println!("{:?}", work().await);
}
```

I expected to see this happen: Foo should have value 100 for both a and b

Instead, this happened: Foo.b is zero.

This behavior is so surprising that it should at least be a warning from rustc. The outcome is clearly not the intent of the code, but it looks like it should work as expected.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.76.0 (07dca489a 2024-02-04)
```

This is possibly a dupe of #108808