sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking Issue for `pointer::mask`
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(ptr_mask)]`

This is a tracking issue for `<*const T>::mask` and `<*mut T>::mask` methods that allow masking pointers.

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
impl<T: ?Sized> *const T {
    pub fn mask(self, mask: usize) -> *const T;
}

impl<T: ?Sized> *mut T {
    pub fn mask(self, mask: usize) -> *mut T;
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation: #96946
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.
Repository: rust
Issue: Adding an attribute to a `macro_export`ed macro and reexporting it incorrectly triggers the macro_expanded_macro_exports_accessed_by_absolute_paths error
Labels: A-attributes,A-resolve,A-macros,T-compiler,C-bug

I tried this code:

```rust
#[rustfmt::skip]    // <- The code compiles if this attribute is removed
#[macro_export]
macro_rules! _a {
    () => {
        "Hello world"
    };
}

pub use _a as a;

fn main() {
    println!(a!());
}
```

(https://gist.github.com/jakobrs/8bcaf3448431126005e16ac678f769c5)

I expected to see this happen: The code should compile successfully.

Instead, this happened: The `macro_expanded_macro_exports_accessed_by_absolute_paths` error is triggered.


<details>
<summary>Full error message</summary>

```
error: cannot determine resolution for the macro `a`
  --> ./b.rs:12:14
   |
12 |     println!(a!());
   |              ^
   |
   = note: import resolution is stuck, try simplifying macro imports

error: macro-expanded `macro_export` macros from the current crate cannot be referred to by absolute paths
 --> ./b.rs:9:9
  |
9 | pub use _a as a;
  |         ^^^^^^^
  |
  = note: `#[deny(macro_expanded_macro_exports_accessed_by_absolute_paths)]` on by default
  = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
  = note: for more information, see issue #52234 <https://github.com/rust-lang/rust/issues/52234>
note: the macro is defined here
 --> ./b.rs:3:1
  |
3 | / macro_rules! _a {
4 | |     () => {
5 | |         "Hello world"
6 | |     };
7 | | }
  | |_^

error: macro-expanded `macro_export` macros from the current crate cannot be referred to by absolute paths
  --> ./b.rs:12:14
   |
12 |     println!(a!());
   |              ^
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #52234 <https://github.com/rust-lang/rust/issues/52234>
note: the macro is defined here
  --> ./b.rs:3:1
   |
3  | / macro_rules! _a {
4  | |     () => {
5  | |         "Hello world"
6  | |     };
7  | | }
   | |_^

error: aborting due to 3 previous errors
```
</details>

### Meta
This happens with Rust 1.60, 1.61 and nightly (bb8c2f411 2022-06-19)
`rustc --version --verbose`:
```
# Nightly

rustc 1.63.0-nightly (bb8c2f411 2022-06-19)
binary: rustc
commit-hash: bb8c2f41174caceec00c28bc6c5c20ae9f9a175c
commit-date: 2022-06-19
host: x86_64-unknown-linux-gnu
release: 1.63.0-nightly
LLVM version: 14.0.5

# Stable

rustc 1.61.0 (fe5b13d68 2022-05-18)
binary: rustc
commit-hash: fe5b13d681f25ee6474be29d748c65adcd91f69e
commit-date: 2022-05-18
host: x86_64-unknown-linux-gnu
release: 1.61.0
LLVM version: 14.0.0
```

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"bvanjoi"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: vscode
Issue: Renaming a folder that is locked by an application locks up explorer for ~1 minute and eventually fails with EPERM
Labels: bug,file-explorer

![Recording 2022-06-18 at 08 05 02](https://user-images.githubusercontent.com/2193314/174608108-957275c5-bb80-41d8-87f8-d6b6f7199858.gif)

Eventually I see this:

![image](https://user-images.githubusercontent.com/2193314/174608130-09c3c80a-b4f9-4d93-966d-088d4c4582e4.png)

When I do the same in Windows Explorer I see the folder is being used by another application instantly. Reloading the window freed the lock and I could rename. Possibly improvements we could make:

- Detect EPERM and report it instantly
- Free the lock on all files (maybe caused by file watcher?) when renaming so the operation goes through

Version: 1.69.0-insider (user setup)
Commit: fbf1cf3832d43088e27837dbb68d24ab65a098c1
Date: 2022-06-17T05:16:33.731Z
Electron: 18.3.3
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT x64 10.0.22000
Repository: vscode
Issue: Duplicate entries in edit breakpoint and related submenus
Labels: bug,debug

I got in this state after adding a conditional breakpoint, debugging and then right clicking:

![image](https://user-images.githubusercontent.com/2193314/174609920-51452850-d642-4497-ba07-d4943e9f6df9.png)

Version: 1.69.0-insider (user setup)
Commit: fbf1cf3832d43088e27837dbb68d24ab65a098c1
Date: 2022-06-17T05:16:33.731Z
Electron: 18.3.3
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT x64 10.0.22000
Repository: kubernetes
Issue: kubectl.exe not code-signed
Labels: kind/feature,sig/windows,sig/release,lifecycle/frozen,needs-triage

1. Follow [instructions](https://kubernetes.io/docs/tasks/tools/install-kubectl-windows/#install-kubectl-binary-with-curl-on-windows) to download kubectl on Windows
2. Check file properties of `kubectl.exe`

**Expected**: `kubectl.exe` is code-signed (Authenticode)

**Actual**: `kubectl.exe` is not code-signed, lacking any evidence that the file has been built by a trustworthy source
Repository: PowerToys
Issue: Watch folder option for image resizer 
Labels: Idea-Enhancement,Product-Image Resizer,Needs-Triage

### Description of the new feature / enhancement

Auto resize image in real time for said watch folder with the option to save resized image in a different folder. 

### Scenario when this would be used?

When dealing with everyday situation when countless image that need to be resized on the go (one by one) instead of by batch. If it is resized in real time, don't have to use batch mode. Thus, saving time. 

### Supporting information

_No response_
Repository: pytorch
Issue: All {view}_scatter variants should support all (or most) dtypes
Labels: triaged,module: functionalization

We've been using `{view}_scatter` to replace some in-place operations (e.g. x`.diag().copy_(y) -> diagonal_scatter(x, y)`) for the purposes of composite compliance. However, as discovered by @kshitij12345, it turns out that the {view}_scatter operations do not have the same coverage as the original operations (they may not support complex dtype, and they may not support complex autodiff even if they support complex dtype).

We should make sure the {view}_scatter operations have the same coverage (dtype, autograd, etc) as their in-place `{view}.copy_(...)` variants.

cc @bdhirsh
Repository: material-ui
Issue: Use more than `primary` and `secondary` colors when using typescript
Labels: typescript,customization: theme

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

```
    "@material-ui/core": "^4.12.4",
    "@material-ui/icons": "^4.11.3",
    "@material-ui/lab": "^4.0.0-alpha.61",
```

### Summary 💡

https://mui.com/material-ui/customization/theming/
I am creating custom material ui theme as documented above and works correctly for `primary` and `secondary` palette colors.

My issue and therefore this post is because I need more than two colors and I cannot them to the palette. Typescript compilation fails.

See examples section

### Examples 🌈

I want to use for example other color below like `blue` instead of only primary and secondary.
Primary is black secondary green. 

I have a lot of colors for success messages, loading status, errors etc  so two colors are not enough.


The below will fail because typescript requires primary or secondary string
```
<LinearProgress color="blue" />
```

The same with defining the theme, it fails if I try to add extra colors to the palette

The below will not compile as `blue` is not recognised as a key
```
const _default = createTheme({
    palette: {
        blue: '#0231ec'
    },
});

The same problem is everywhere, another example with a "cancel" button that I need it to be red.
![Screenshot 2022-06-20 at 18 21 04](https://user-images.githubusercontent.com/15630854/174644153-4434abde-bc04-4170-b3ed-87fdb6fae1bb.png)

I set it as secondary which is red now. Now I need another color for loading spinner which is not `primary` black or secondary red. What to do in this case?
I cannot choose other values in ts + react mui components ...

```

### Motivation 🔦

Have a colorful website with all needed colors instead of being limited to two colors... primary and secondary
Repository: electron
Issue: [Bug]: Unable to bind to media control events from bluetooth devices on macOS
Labels: platform/macOS,bug :beetle:,status/confirmed,has-repro-gist,25-x-y,26-x-y,27-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

18.2.3

### What operating system are you using?

macOS

### Operating System Version

macOS Monterey 12.4

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

unknown

### Expected Behavior

Media control events from bluetooth devices should be detected like keyboard media control events using globalShortcut.register. 

### Actual Behavior

In the testcase I bound to MediaPlayPause, logs show that keyboard presses are detected and bluetooth media control events are not detected. This results in another application that has bound to bluetooth media controls receiving the command or if one isn't running, the operating system's default behavior of opening Apple Music. 

### Testcase Gist URL

https://gist.github.com/e6f47e61bf3e37ee578352301818b3b7

### Additional Information

_No response_
Repository: go
Issue: cmd/compile: inlining confuses escape analysis with interface{} params
Labels: Performance,NeedsInvestigation,compiler/runtime

Take a look at https://go.dev/play/p/mPqA0RaybuQ.

On `go version devel go1.19-9068c6844d Thu Jun 16 21:58:40 2022 +0000 linux/amd64` I get the following benchmark results:

```
name                        time/op
ConditionalDebugf/false-16  69.4ns ± 3%
ConditionalDebugf/true-16    280ns ± 0%
InlinedDebugf/false-16      0.53ns ± 1%
InlinedDebugf/true-16        281ns ± 4%

name                        alloc/op
ConditionalDebugf/false-16   24.0B ± 0%
ConditionalDebugf/true-16    40.0B ± 0%
InlinedDebugf/false-16       0.00B     
InlinedDebugf/true-16        40.0B ± 0%

name                        allocs/op
ConditionalDebugf/false-16    2.00 ± 0%
ConditionalDebugf/true-16     3.00 ± 0%
InlinedDebugf/false-16        0.00     
InlinedDebugf/true-16         3.00 ± 0%
```

First, note that both debugf functions are inlined:

```
$ go test -gcflags='-m' |& grep Debugf
./go_test.go:12:6: can inline conditionalDebugf
./go_test.go:18:6: can inline inlinedDebugf
./go_test.go:30:22: inlining call to conditionalDebugf
./go_test.go:45:19: inlining call to inlinedDebugf
```

And, in the `true` sub-benchmarks where debug logging is enabled and we actually call `Sprintf`, we can see three allocations - two corresponding to the two `interface{}` parameters, as the `string` and `int` variables escape to the heap via the interface, and one for the actual call to `Sprintf` constructing a string.

So far so good. However, when debug logging is disabled, I want to avoid those allocations, because this debug logging happens in a tight loop that runs millions of times in a program, so I want to avoid millions of allocations made in a very short amount of time.

This works fine for the "manually inlined" case where I wrap the call to Debugf with a conditional. Note the zero allocations on `InlinedDebugf/false`. However, that means that every time I want to use Debugf (a dozen times in said program), I need three lines rather than one, and it's pretty repetitive and verbose.

One good alternative is to move the conditional inside the Debugf function - and since it's still inlined, it should be the same result. However, `ConditionalDebugf/false` allocates twice, presumably because the two arguments do still allocate, as if I was actually calling `Sprintf` when in fact I am not.

It seems to me like the two benchmarks should behave the same; the compiler's escape analysis and inliner should work well enough together to detect this scenario.

Note that my real use case involves `log.Printf`, which is a no-op when one has called `log.SetOutput(io.Discard)`. The benchmark above is a simplification which still reproduces the same problem.
Repository: flutter
Issue: [go_router] state params missing after refresh on web
Labels: package,has reproducible steps,P2,p: go_router,found in release: 3.0,found in release: 3.1,team-go_router,triaged-go_router

I've noticed an issue that when I refresh on web, the `state.params` in `navigatorBuilder` are missing even tho the `location` is set correctly.

Example:

Pattern: `/:page`
Url: `localhost:4444/#/2`

Result:
* `location` = `/2`
* `state.params['page']` = `null`

Expected Result:
* `location` = `/2`
* `state.params['page']` = `2`

<details>
<summary>Code Example</summary>

```dart
import 'package:flutter/material.dart';
import 'package:go_router/go_router.dart';

void main() {
  runApp(MyApp());
}

final routes = [
  GoRoute(
    path: '/',
    builder: (context, state) => const Page(
      number: "1",
    ),
  ),
  GoRoute(
    path: '/:page',
    builder: (context, state) => Page(number: state.params["page"] ?? "1"),
  ),
];

class MyApp extends StatelessWidget {
  final _router = GoRouter(
      routes: routes,
      navigatorBuilder: (
        BuildContext context,
        GoRouterState state,
        Widget child,
      ) {
        print(state.location); // -> /2
        print(state.params); // -> null :( expected: { 'page': '2' }
        return child;
      });

  @override
  Widget build(BuildContext context) {
    return MaterialApp.router(
      routeInformationProvider: _router.routeInformationProvider,
      routeInformationParser: _router.routeInformationParser,
      routerDelegate: _router.routerDelegate,
    );
  }
}

class Page extends StatelessWidget {
  const Page({Key? key, required this.number}) : super(key: key);
  final String number;

  @override
  Widget build(BuildContext context) {
    return Center(
        child: Column(
      mainAxisSize: MainAxisSize.min,
      children: [
        Text("Page $number"),
        ElevatedButton(
            onPressed: () {
              final next = (int.tryParse(number) ?? 1) + 1;
              context.go("/$next");
            },
            child: Text("Next"))
      ],
    ));
  }
}
```
</details>
Repository: godot
Issue: 3D projects crashes on start
Labels: bug,platform:linuxbsd,topic:rendering,topic:editor,needs testing,crash,regression

### Godot version

4.0 alpha 9

### System information

Linux, AMD RX 5500 XT

### Issue description

A couple of 3D projects now crash on start and I get this:
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.0.alpha10.official (4bbe7f0b98de72d6dd77d5ade4b761de375bcf66)
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f4bb27ea210] (??:0)
[2] /home/roger/work/godot4/Godot_v4.0-alpha10_linux.64() [0xde3997] (??:0)
[3] /home/roger/work/godot4/Godot_v4.0-alpha10_linux.64() [0x37c7d80] (??:0)
[4] /home/roger/work/godot4/Godot_v4.0-alpha10_linux.64() [0xdcafef] (??:0)
[5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f4bb27cb0b3] (??:0)
[6] /home/roger/work/godot4/Godot_v4.0-alpha10_linux.64() [0xddfa3e] (??:0)
-- END OF BACKTRACE --

The projects were working until alpha 8. Other, simpler projects, still work, also, if I use Windows, all the projects run fine.

### Steps to reproduce

I havent been able to reproduce the problem. I created a new project, and added more and more elements (larger scenes, animated models, navigation regions) but it runs fine. 

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: test_meta_vstack_cuda_int16 (__main__.TestMetaCUDA) Fails with DEBUG=1
Labels: module: autograd,triaged,needs research

### 🐛 Describe the bug

`python test/test_meta.py -k test_meta_vstack_cuda_int16`

> ERROR: test_meta_vstack_cuda_int16 (__main__.TestMetaCUDA) 
Traceback (most recent call last):
  File "/scratch/eellison/pytorch/test/test_meta.py", line 325, in run_meta_crossref
    meta_rs = func(*meta_args, **meta_kwargs)
  File "/private/home/eellison/anaconda3/lib/python3.8/site-packages/torch/overrides.py", line 1768, in wrapped
    return f(self, *args, **kwargs)
  File "/private/home/eellison/anaconda3/lib/python3.8/site-packages/torch/overrides.py", line 1873, in __torch_function__
    return func(*args, **kwargs)
RuntimeError: self__storage_saved.value().is_alias_of(result.storage()) INTERNAL ASSERT FAILED at "/raid/eellison/pytorch/torch/csrc/autograd/generated/VariableType_4.cpp":13537, please report a bug to PyTorch. 

`test_meta_unsqueeze_cuda_int8` also fails


### Versions

master

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: next.js
Issue: Link AsPath with optional catch-all parameter produces weird behaviour. 
Labels: bug,Navigation,linear: next

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Enterprise
    Binaries:
      Node: 16.14.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.1.7-canary.42
      react: 17.0.2
      react-dom: 17.0.2

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

Vercel

### Describe the Bug

I'm using routes with a custom "as" parameter. So users see a url that is different from the internal NextJS one. This approach works fine in most cases but problems emerge on optional catch-all routes like `[[...params]]`

Here is a simple deployed app: https://nextjs-dynamic-routing-eta.vercel.app/
It has two routes: `index.js` (to show hello world) and `/post/[[...params]].js`. Header has several links.

The first block has 3 links without `as`. They point to `/post`, `/post/1` and `/post/1/2` respectively. 

The second block has the same 3 links, but with the `as` parameter passed. 
The third one (`/post/1/2`) works perfectly.
The second one (`/post/1`) passes string instead of array in the `params` route parameter. 
The first one (`/post`) throws an error https://nextjs.org/docs/messages/incompatible-href-as. 

### Expected Behavior

All three links in the 2nd block must work in the same way as links in the 1st block, but the browser must show a `/human-readable` url. 



### Link to reproduction

https://github.com/k0ka/nextjs-dynamic-routing/

### To Reproduce

Clicking on the "as human-readable" links must show the same result in html as the corresponding link in the "without as" block, but the url should be changed to "/human-readable". 

More specifically:
1) clicking on the "As human-readable" => "No parameters" link must show on the bottom of the page text
```
Params is an array. Length 0
```
 and the url must be `https://nextjs-dynamic-routing-eta.vercel.app/human-readable`

2) clicking on the "As human-readable" => "One parameter" link must show on the bottom of the page text
``` 
Params is an array. Length 1
* 1
```
and the url must be `https://nextjs-dynamic-routing-eta.vercel.app/human-readable`
Repository: flutter
Issue: [A11y][iOS]: Voice Control with overlay cannot dismiss an opened dialog with "show number" or "go back"
Labels: platform-ios,framework,a: accessibility,customer: money (g3),has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-ios,triaged-ios

Internal: b/228415209

## Steps to Reproduce

1. Enable Voice Control with Overlay in iOS settings.
2. Trigger a Flutter dialog.
3. Attempt to dismiss the dialog using voice controls.

Expected: Voice commands exist that can dismiss the Flutter dialog.
Actual: Seems to be no way to dismiss the dialog using voice controls.

```dart
OutlinedButton(
          onPressed: () {
            showGeneralDialog<void>(
              context: context,
              barrierColor: Colors.transparent,
              barrierDismissible: true,
              barrierLabel:
                  MaterialLocalizations.of(context).modalBarrierDismissLabel,
              pageBuilder: (_, __, ___) =>
                  const AlertDialog(title: Text('Alert!')),
            );
          },
          child: const Text('Open Dialog'),
        ),
```

ATTACHED VIDEO BELOW:
In the video, observe that the dialog cannot be closed.

The number 1 that appears after the command show numbers is to stop the recording, it's not actually there without the video recording. There is no number on the screen when "show numbers" is issued.

Works in Android, and works in VoiceOver. In VoiceOver, the focus can go to the back (I'm guessing there's a ModalBarrier at the back?) and it's announced as "dismiss".

https://user-images.githubusercontent.com/37954976/174659422-049a364e-f91f-4b1d-87fe-53b018a2732d.MP4