sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Seemingly equivalent GAT trait implementations behave differently
Labels: GATs-triaged,A-GATs

<!--
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.
-->

The following code fails to compile:

```rust
#![feature(generic_associated_types)]

use std::ops::Deref;

trait GetOutput {
    type Output<'a>
    where
        Self: 'a;

    fn output<'a>(&'a self) -> Self::Output<'a>;
}

impl<T, D> GetOutput for T
where
    T: Deref<Target = D>,
    D: GetOutput,
{
    type Output<'a>
    where
        Self: 'a,
        D: 'a,
    = D::Output<'a>;

    fn output<'a>(&'a self) -> Self::Output<'a> {
        self.deref().output()
    }
}
```

But this equivalent (I think) code compiles just fine:

```rust
#![feature(generic_associated_types)]

use std::ops::Deref;

trait GetOutput {
    type Output<'a>
    where
        Self: 'a;

    fn output<'a>(&'a self) -> Self::Output<'a>;
}

impl<T> GetOutput for T
where
    T: Deref,
    T::Target: GetOutput,
{
    type Output<'a>
    where
        Self: 'a,
        <Self as Deref>::Target: 'a,
    = <<Self as Deref>::Target as GetOutput>::Output<'a>;

    fn output<'a>(&'a self) -> Self::Output<'a> {
        self.deref().output()
    }
}
```

There might be a subtle difference between the two implementation but I can't see any. This is a simplified example from this question in the Rust subreddit: https://www.reddit.com/r/rust/comments/qp8dwl/hey_rustaceans_got_an_easy_question_ask_here/hjsfjgs/
Repository: terminal
Issue: Windows Terminal Azure cloud shell error: IXMLHttpRequest2Callback::OnError: -2146697205: The operation was timed out.  [process exited with code 1]
Labels: Help Wanted,Issue-Bug,Product-Terminal,Area-AzureShell,Priority-2

I have suddenly started receiving this error: 
"IXMLHttpRequest2Callback::OnError: -2146697205: The operation was timed out.

[process exited with code 1]"

When signing into the Azure Cloud Shell in Windows Terminal. Eventually it can be possible to get in but I am informed my session is ephemeral. 

I am using: Windows Terminal
Version: 1.11.2921.0

Please advise! Thanks.
Repository: flutter
Issue: Cursor flickering at the edge of `TextField`
Labels: a: text input,framework,f: material design,a: fidelity,has reproducible steps,found in release: 1.26,found in release: 2.5,team-design,triaged-design

The cursor starts flickering when it reaches the edge of a single-line `TextField`. Looking the native apps, it should always remain steady during typing/deleting and blink only when it's idle. While I think this issue isn't the worst, it still needs to be fixed to feel more native.


- This happens on both iOS and Android.
- Flutter version is `2.5.3` and channel is `stable`.

## Steps to Reproduce

1. Execute `flutter run` on the code sample
2. Type until the cursor reaches the edge of the `TextField`
3. Keep typing to see the cursor flickering

**Expected results:**

https://user-images.githubusercontent.com/12843244/140827149-f9abfd95-816d-4e0c-9a8e-59c13ee271e4.mp4

**Actual results:**

https://user-images.githubusercontent.com/12843244/140827167-565f66e3-7311-462a-9647-4c2eea6521fd.mp4

<details>
<summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() => runApp(const App());

class App extends StatelessWidget {
  const App({Key? key}) : super(key: key);

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      title: _title,
      home: HomePage(),
    );
  }
}

class HomePage extends StatelessWidget {
  const HomePage({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return const Scaffold(
      body: Center(
        child: Padding(
          padding: EdgeInsets.symmetric(horizontal: 30.0),
          child: TextField(
            decoration: InputDecoration(
              hintText: "Type something long",
            ),
          ),
        ),
      ),
    );
  }
}
```

</details>
Repository: TypeScript
Issue: Support class member snippet completions in JS files
Labels: Suggestion,Domain: Completion Lists

# Suggestion

Support class member snippet completions in JS files

## 🔍 Search Terms

class member completion

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [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 feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

We should have [class member snippet completions](https://github.com/microsoft/TypeScript/pull/46370) work in JS files. Currently they only work in TS files.

## 📃 Motivating Example


```js
class Base {
    /**
     * @param {number} a
     * @param {number} b
     */
    foo(a, b) {
        return a + b;
    }
}

class Sub extends Base {
    | // Suggest `foo(a, b) { }` here, like we do in TS files
}
```

## Considerations

To properly support JS, we would have to consider the many ways in which properties can be added to a class in JS. We also should make sure the completion suggestion has JSDoc when possible.
Repository: go
Issue: x/build/cmd/gerritbot: posts duplicate messages whenever Gerrit message IDs change
Labels: Builders,NeedsInvestigation

Starting at about 08 Nov 2021 02:47:26 -0800 GerritBot sent a large number of duplicate comments.  These were comments made in Gerrit on CLs imported into GitHub.  Those comments has already been echoed back to the original GitHub pull requests.  They were then duplicated on November 8.  This affected more than 50 pull requests.

Some Sample GitHub pull requests showing the duplicate comments:

https://github.com/golang/debug/pull/7 (the first one I found)
https://github.com/golang/sys/pull/114
https://github.com/golang/go/pull/44998
https://github.com/golang/go/pull/29726
https://github.com/golang/go/pull/44535 (the last one I found)

CC @golang/osp-team
Repository: flutter
Issue: `flutter test --platform=chrome` doesn't match `flutter_tester`'s window.locales test value
Labels: a: tests,a: fidelity,platform-web,P2,team-web,triaged-web

window.locales should be [en-US, zh-CN] when debugEmulateFlutterTesterEnvironment is true.

See `locale_json` in https://github.com/flutter/engine/blob/master/shell/testing/tester_main.cc
Repository: godot
Issue: RigidBody2D: `MODE_STATIC` prevents `body_entered` signal
Labels: discussion,topic:physics

### Godot version

v3.4.stable.official [206ba70f4]

### System information

Arch Linux (I don’t now how to give a version for this)

### Issue description

![Two balls fall on two bricks. One of the bricks is labeled “Static”. The other is labeled “Kinematic”. When one of the balls hits the “Static” brick, nothing happens. When the other ball his the “Kinematic” brick, the brick disappears.](https://user-images.githubusercontent.com/5579359/140838856-01561905-1fc5-4114-8d9f-e0ea918187a8.gif)

If a RigidBody2D’s mode is set to static, it doesn’t emit `body_entered` signals. If its mode is anything other than static, then it emits `body_entered` signals. I would expect RigidBody2Ds to emit the `body_entered` signal regardless of what mode they’re in. If static RigidBody2Ds aren’t supposed to emit the `body_entered` signal, then I would expect that to be mentioned in the documentation for `body_entered`.

### Steps to reproduce

1. Create a RigidBody2D and give it a collision shape.
2. Set the following properties for it:
    - `mode = MODE_STATIC`
    - `contacts_reported = 1` (or more)
    - `contact_monitor = true`
3. Attach a script to it.
4. Connect its `body_entered` signal to a function in its script. Make it a function that does something noticeable. In the minimal reproduction project, I had that function call `queue_free()`.
5. Create a second RigidBody2D and give it a collision shape.
6. Position the bodies so that the second one will collide with the first one.
7. Run the scene.

### Minimal reproduction project

[rigid_body_2d_mode_static_prevents_body_entered_signal.zip](https://github.com/godotengine/godot/files/7501123/rigid_body_2d_mode_static_prevents_body_entered_signal.zip)

### Workaround

Set the RigidBody2D’s mode to kinematic instead of static.
Repository: TypeScript
Issue: `importModuleSpecifierEnding: 'js'` not honored when path aliases are used
Labels: Bug,Help Wanted,Effort: Moderate

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

- importModuleSpecifierEnding
- paths
- js es modules

### 🕗 Version & Regression Information

reproduced with TypeScript 4.4.4 as well as 4.6.0-dev.20211108 (i.e. `npm install typescript@next` at the time of writing).

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- ~This is a crash~
- ~This changed between versions ______ and _______~
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about __ Modules __
- ~I was unable to test this on prior versions because _______~

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->

I could not figure out how to configure the Bug Workbench to contain multiple files, so I created an example git repository instead:

https://github.com/orzechowskid/ts-example-repo

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
// ./tsconfig.json

{
  "compilerOptions": {
    "allowJs": true,
    "baseUrl": ".",
    "checkJs": true,
    "paths": {
      "~/*": [ "./src/*" ]
    },
    "strict": true
  },
  "include": [
    "./src/**/*"
  ]
}

// ./src/utils/foo/bar/baz.js

export const baz = (a, b) => a + b;

// ./src/components/foo/Bar.js

import * from '~/utils/foo/bar/b
                                ^- wait for auto-suggest
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->
`baz` suggested as autocomplete text

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
`baz.js` suggested as autocomplete text, since it's referring to a module import and I've set `importModuleSpecifierEnding: 'js'` in my preferences.  (FWIW the file extension is appended if I write a relative path, e.g. `'import * from '../../utils/foo/bar/baz.js`).
Repository: go
Issue: runtime: use MiniDumpWriteDump for GOTRACEBACK=crash on Windows
Labels: Proposal,Proposal-Accepted,compiler/runtime

CL 307372 was committed, which contained a nice change to produce crashdumps under certain circumstances. However, several questions were proposed about when those crashdumps would be automatically uploaded to Microsoft in the context of using Insider Builds. In the absence of good answers to that, the otherwise okay CL was reverted (by me) with CL 362454. This proposal is essentially about reverting the revert, and having an extended discussion about under which circumstances these should be enabled and whether we need a new flag for it, as suggested by @bufflig.

Before this proposal moves to an "under consideration" step, we should get a clearer idea about what we're proposing. I'll defer to @zhizheng052 and @bhiggins on this, as they wrote the original CL.

CC @zhizheng052 @bhiggins @bufflig @ianlancetaylor @alexbrainman @aarzilli @aclements
Repository: pytorch
Issue: register_ Hook causes the CUDA out of memory, and remove() is useless
Labels: module: autograd,triaged


register_ Hook causes the CUDA out of memory, and remove() is useless

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: pytorch
Issue: Request to revise the Pytorch tutorial.
Labels: oncall: jit,module: docs,module: cpp

## 📚 Documentation

Hello

I am an university student from South Korea and interested in AI open source.

After looking at the tutorial [LOADING A TORCHSCRIPT MODEL IN C++] ( https://pytorch.org/tutorials/advanced/cpp_export.html ), I found out that the command was wrong while running it on Linux.

I could see through the search that many users already knew it, so I thought this was a problem that had to be corrected.

I think, the instructions(in the step 3 part) must be modified as follows to be executed properly.
(It failed when entered according to the instruction written in the tutorial, but succeeded when executed with the changed instruction as follows.)

previous:  cmake -DCMAKE_PREFIX_PATH=/path/to/libtorch ..
changed:  cmake -S ~/example-app -DCMAKE_PREFIX_PATH=/path/to/libtorch ..

Please review if my opinion is correct.

Thank you for your attention to this matter.
Have a nice day.


Yours faithfully, Minjung Cho.



cc @brianjo @mruberry @jbschlosser
Repository: rust
Issue: Can I create and use a `*mut` to an uninitialized local?
Labels: A-raw-pointers

[The following code](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=af091e6631ed79d5b4dadfb9c7569ba9) does not compile on current nightly or stable (1.56.1).

```rust
fn main() {
    let mut x: i32;
    println!("{:p}", std::ptr::addr_of_mut!(x));
}
```

```
error[E0381]: borrow of possibly-uninitialized variable: `x`
 --> src/main.rs:3:22
  |
3 |     println!("{:p}", std::ptr::addr_of_mut!(x));
  |                      ^^^^^^^^^^^^^^^^^^^^^^^^^ use of possibly-uninitialized `x`
  |
  = note: this error originates in the macro `std::ptr::addr_of_mut` (in Nightly builds, run with -Z macro-backtrace for more info)
```

I would expect this to work, since part of the rationale for the `addr_of` macro and raw reference operator (#64490) was to allow creation of pointers to uninitialized memory. On the other hand, I don't think the behavior of locals that are only assigned/accessed indirectly is fully specified (though I don't think my example is UB). Such locals will never be dropped, which might be surprising, and they cannot be used directly, even after being written via the pointer, without encountering the same error.

`MaybeUninit` is basically always a better choice for these kinds of things, so it shouldn't be of much importance to users. However, we should avoid depending on the illegality of such code inside the compiler–a more complex example arose while discussing region inference–unless we have made a conscious decision to forbid it. Alternatively, if interacting with uninitialized locals is well-defined, we should probably make `addr_of` work on them.
Repository: react
Issue: [DevTools Bug]: Chrome extension's settings reset after every reload
Labels: Type: Bug,Status: Unconfirmed,Resolution: Needs More Information,Component: Developer Tools

### Website or app

Chrome 95.0.4638.69 (Official Build) (64-bit), DevTools version 4.21.0-2f8f60ca8

### Repro steps

1. Open Chrome dev tools
2. Switch to Components or Profiler tab 
3. Select settings and change for example "Highlight updates when components render."
4. Reload window
5. Get back to settings - checbox is not checked.

Expected behavior is to preserve settings forever (local storage?) or at least between reloads.

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: vscode
Issue: Reviving a terminal converts a symlink cwd to its realpath
Labels: help wanted,feature-request,terminal-persistence

Issue Type: <b>Bug</b>

Preferred development environment for various workspaces is under a symlink to a common folder.

Example working directory: ~/src/project
where ~/src -> /x/y/z
When shutting down and restarting vscode, this results in the prompt being changed from ~/src/project to /x/y/z/project

VS Code version: Code 1.62.0 (b3318bc0524af3d74034b8bb8a64df0ccf35549a, 2021-11-03T15:23:01.379Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
Remote OS version: Linux x64 4.4.0-53-generic


<!-- generated by issue reporter -->
Repository: create-react-app
Issue: "jest-circus" is a dependency of react-scripts, but unable to find it under react-scripts.Is there anything I am missing?
Labels: stale,needs triage

There is vulnerability found in 26.6.2 version of "expect" . It depends on "jest-circus".I thought of updating the jest-circus and thinking that its child dependency ie. "expect" would also get updated its latest version.Parent of "jest-circus" is "react-scripts".I tried searching "jest-circus" under "react-scripts" but could not find it.
Is there any other way I can update the "jest-circus" to its latest dependency.?
or If someone can guide how to update the "expect" to its latest version, it would be of great help.
Repository: vscode
Issue: Get rid of before/after css rules in foldingDecorations
Labels: debt,editor-core

[foldingDecorations.ts#L22](https://github.com/microsoft/vscode/blob/f411e1cffbdc3a2d18a4e998ec602521607ed674/src/vs/editor/contrib/folding/foldingDecorations.ts#L22) and [foldingDecorations.ts#L30](https://github.com/microsoft/vscode/blob/f411e1cffbdc3a2d18a4e998ec602521607ed674/src/vs/editor/contrib/folding/foldingDecorations.ts#L30)
* reason: renders ⋯ at end of folded lines
Repository: pytorch
Issue: Release official Python 3.9 images
Labels: module: binaries,triaged

## 🚀 Feature
Support Pytorch CUDA docker images with Python 3.9

## Motivation
Python 3.7 is in the security fixes only stage, and moving forward we're going to use Python 3.9/3.10.

## Pitch
As Python 3.7 is now in security fixes stage only, with no more binaries released, we have started our move to Python 3.9.
The latest official docker images come shipped with Python 3.8, while older ones that we still use come shipped with Python 3.7.
We want to move forward to Python 3.9 with pytorch as well but at the moment there are no docker images that support Python 3.9.
What we need is official images that come shipped with Python 3.9.

## Alternatives
Building and maintaining the images ourselves using the `PYTHON_VERSION` makefile command (was not tested)


cc @ezyang @seemethere @malfet
Repository: vscode
Issue: option for bracket pair vertical line depending on indentation
Labels: feature-request,bracket-pair-guides

<!-- ⚠️⚠️ 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. -->
The new Bracket Pairs Horizontal settings came together with the vertical line depending on the indentation. I would like this dependency to be an option, because I do not like it. My `#if` and `#endif` are situated at the start of the line, rendering all the vertical lines useless:
![image](https://user-images.githubusercontent.com/51912545/140924645-8700087c-94ae-45f7-9112-185373f6ca16.png)
Repository: excalidraw
Issue: Unable to auth with Notion
Labels: Excalidraw+

Hello!

I just signed up for a pro account so we can start embedding Excalidraw images in Notion. 

Here is the sequence of steps to reproduce my error:
1. Paste a private Excalidraw URL into Notion
2. Notion displays an embedded Excalidraw "Click on the Button to Log In" frame
3. I click on Google
4. I select the Google account I used with Excalidraw
5. The auth screen shows white and hangs forever
6. If I refresh the page, I see `Unable to process request due to missing initial state. This may happen if browser sessionStorage is inaccessible or accidentally cleared.`

As a result I can't embed images.

As an alternative, I tried enabling link-sharing, but then the embedded image shows up with lots of additional UI elements (displayed within notion) inviting me to sign up for Excalidraw.
Repository: pytorch
Issue: Some lr-schedulers docs seems to have typos/missing information
Labels: module: docs,module: optimizer,triaged,module: LrScheduler

## 📚 Documentation

According to [ConstantLR](https://pytorch.org/docs/stable/generated/torch.optim.lr_scheduler.ConstantLR.html#torch.optim.lr_scheduler.ConstantLR) "*Decays the learning rate of each parameter group by a small constant factor until the number of epoch reaches a pre-defined milestone: total_iters*"  i.e with `factor=0.5`, `lr=0.05`  and `total_iters=4` I would assume

```
#lr = 0.025 
#lr = 0.0125
#lr = 0.00625
#lr = 0.003125
#lr = 0.5  #Back to initial
```
i.e

```
lr[i+1] = lr[0]*start_factor**i
```
where the docs writes 

```
 # Assuming optimizer uses lr = 0.05 for all groups
# lr = 0.025   if epoch == 0
# lr = 0.025   if epoch == 1
# lr = 0.025   if epoch == 2
# lr = 0.025   if epoch == 3
# lr = 0.05    if epoch >= 4
```

In the  [LinearLR](https://pytorch.org/docs/stable/generated/torch.optim.lr_scheduler.LinearLR.html) the learning-rate examples

```
# Assuming optimizer uses lr = 0.05 for all groups
# lr = 0.025    if epoch == 0
# lr = 0.03125  if epoch == 1
# lr = 0.0375   if epoch == 2
# lr = 0.04375  if epoch == 3
# lr = 0.005    if epoch >= 4
 scheduler = LinearLR(self.opt, start_factor=0.5, total_iters=4)
```

increases after epoch 0 until epoch 4 where it drops again (why?). As far as I understand LinearLR we get the learning-rate in each step by

```
lr[i+1] = lr[i]*start_factor**(i)
```


Generally it would be great, if you provided a (short) formular of how you calculate each learning rate in the schedulers since the wording can be interpreted differently by different persons but formulars (often) does not.






cc @brianjo @mruberry @vincentqb @jbschlosser @albanD