sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Godot does not correctly collapse methods under X conditions
Labels: bug,topic:editor,needs testing

### Godot version

v3.5.beta1.official [b9b23d222]

### System information

w10 64

### Issue description

When reloading or loading a project, godot has not properly collapsed the methods.
In this video you can see how I have the method collapsed, then I reload the project and you can see that the method is not properly collapsed.
It also happens with the lower method but I will only focus on the "_mueve_personaje" method

I have not been able to reproduce the problem but I can send the project privately.

Video:

https://user-images.githubusercontent.com/19652075/151537618-7df5c881-4c42-46b4-9148-b1b124c9467c.mp4






### Steps to reproduce

...

### Minimal reproduction project

I have not been able to reproduce the problem but I can send the project privately.
Repository: flutter
Issue: [video_player] Buffering works only from current position. Proposal to seek backward through buffer by default.
Labels: c: new feature,p: video_player,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

## Use case

When I turn off wifi I can only seek forward through buffer but if I try seek backward it stalls.

## Proposal

I think video_player should provide possibility to seek backward through buffer by default.
Repository: transformers
Issue: Evidentiality-guided Generator - Retrieval model
Labels: New model

# 🌟 New model addition

## Model description

In this paper, we introduce Evidentiality-guided GGenerator, which incorporates evidentiality of passages---whether a passage contains correct evidence to support the output---into training the generator via multi-task learning of answer generation and evidentiality prediction for retrieval-augmented generation. Experimental results show large improvements across three knowledge intensive tasks: open question answering, fact verification and knowledge-enhanced dialogue.

## Open source status

* [x] the model implementation is available: https://github.com/AkariAsai/evidentiality_qa/tree/main/evi_gen
* [x] the model weights are available: https://github.com/AkariAsai/evidentiality_qa#fine-tuned-models
* [x] who are the authors: @AkariAsai

Happy to guide anyone who is interested through adding this model! Seems like it gives some nice improvements over RAG!

@qqaatw - maybe interesting for you ;-)
Repository: PowerToys
Issue: Allow more combinations / keys to change language layout
Labels: Idea-New PowerToy,Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

In linux, for example, there are many alternative combinations for changing keyboard layout, even with one key, would be nice to have similar on windows.
![Снимок экрана 2022-01-28 142915](https://user-images.githubusercontent.com/5204968/151547144-de974ba5-66ce-4585-b701-b495eea6f551.png)
![Снимок экрана 2022-01-28 142935](https://user-images.githubusercontent.com/5204968/151547146-87790829-643b-4bff-8f0d-548503bc3a29.png)


### Scenario when this would be used?

Since moving from linux i really miss native way to change keyboard layout with one key (right ctrl), there is a way to do this with [lswitch ](https://haali.net/winutils/) program, but it's not ideal, switching keyboard layout with right ctrl does not work in some explorer windows, and it lswitch stops working rarely, so i want this functionality in powertoys.

### Supporting information

_No response_
Repository: godot
Issue: _unhandled_input is not called when start dragging within UI element into outside
Labels: bug,topic:input

### Godot version

3.4.2.stable

### System information

Windows 10, GTX 1070Ti

### Issue description

So I want to have a generic `is_over_ui` boolean to find out if my mouse is over UI or not.
So I have tried to implement it like this:

```
func _input(event):
	if event is InputEventMouse || event is InputEventMouseMotion:
		is_over_ui = true

func _unhandled_input(event):
	if event is InputEventMouse || event is InputEventMouseMotion:
		is_over_ui = false
```

It works when moving between UI and no UI areas. But when I try to press in UI area and drag from there to the area with no UI, `_unhandle_input` is not called at all until I release the mouse left click button. I want to know if it is something in purpose or a bug. And if it is in purpose, why ? 

### Steps to reproduce

1. Create UI element on the screen
2. Write this code in a script: `func _unhandled_input(event): print("Unhandle Input")`
3. Start dragging within UI area into outside

### Minimal reproduction project

[UnhandleInputTest.zip](https://github.com/godotengine/godot/files/7958653/UnhandleInputTest.zip)
Repository: godot
Issue: Animation names must be called [animation name]-loop in order to loop when using a AnimationTreeBlendSpace1D
Labels: bug,topic:animation

### Godot version

3.4.stable.official.206ba70f4

### System information

windows 10 openGL ES 3.0. intel core i5-8365u with intel UHD graphics (intergrated)

### Issue description

When creating a blendspace1D in the animation tree, the animations will not loop when running the game unless the animations are named [animation name]-loop (eg: walk_anim-loop).

They will however, loop in the scene view regardless of weather it has the -loop at the end of the animations name, just not while running the game. I could find nothing in the documentation about this and stumbled on the solution by accident.


### Steps to reproduce

Create an object with some animations you want to loop with an animation player
create an animation tree.
In the animation tree create a blend tree 1D and add your animations.
Watch as they loop in the scene view, but dont loop in the actual game.
Change the names of the animations to have '-loop' at the end and watch as they now loop in the game as well.

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: multiple PRs on pytorch are closed by push to unrelated branches such as pytorch-canary
Labels: triaged,module: third_party

### 🐛 Describe the bug

Reported via Pytorch OSS CI/ Tree Huggers Oncall
There are occurrences of multiple PRs on pytorch are closed by push to unrelated branches such as pytorch-canary.

Examples: 
PR: https://github.com/pytorch/pytorch/issues/69432
Closed by: https://github.com/atalman/pytorch-canary/commit/852df1765869d6f4de4ae496fb12495bd99e17ba

PR: https://github.com/pytorch/pytorch/pull/71611
Closed by this commit: https://github.com/pytorch/pytorch-canary/commit/76952f86276f6d99853fcb45de384361a78f3830

Following is PR related to commit however closed by Michael Suo. Normally we expect all PR  to be closed by pytorchmergebot
PR: https://github.com/pytorch/pytorch/pull/71944
Closed by this commit: https://github.com/pytorch/pytorch/commit/5bd19ba8460aa174133f74b389861f54106a3086

We want to investigate this and implement a fix to prevent these issues.



### Versions

github issue
Repository: storybook
Issue: Numerous issues with Angular Compodoc since v6.4.0-alpha.34
Labels: bug,angular,argtypes

I'm experiencing numerous issues with Angular in newer versions of Storybook. It seems they are all related to Compodoc. These issues include:
* Arrays are interpreted as strings
* Enums are not correctly interpreted
* EventEmitters throw errors

 I tracked down the version when this started happening and I found out that these issues started to occur in [v6.4.0-alpha.34](https://github.com/storybookjs/storybook/releases/tag/v6.4.0-alpha.34) (in **v6.4.0-alpha.33** everything is fine). I assume it is related to this pull request:  #15744

Note: These issues are also still present in latest **6.5.0-alpha.26**

### Reproduce:
Clone this repository: https://github.com/decline/storybook-angular-issues

There are 3 stories that describe what is going wrong.

#### See errors in v6.4.0-alpha.34:

```sh
yarn && yarn storybook
```

#### See it working in v6.4.0-alpha.33:

```sh
git checkout 6.4.0-alpha.33
yarn && yarn storybook
```

As soon as you remove the `setCompodocJson(docJson);` line in `.storybook/preview.js` it will also work in v6.4.0-alpha.34, but then you will also lose Compodoc support 😕

I also recorded a video that shows the comparison between the two versions:


https://user-images.githubusercontent.com/5609744/151581283-fa3f5def-5371-47e7-8054-311fef8703a0.mov

### Environment Info:
```
  System:
    OS: macOS 11.6.3
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
  Binaries:
    Node: 14.17.5 - ~/.nvm/versions/node/v14.17.5/bin/node
    Yarn: 3.1.1 - /usr/local/bin/yarn
    npm: 6.14.14 - ~/.nvm/versions/node/v14.17.5/bin/npm
  Browsers:
    Chrome: 97.0.4692.99
    Firefox: 96.0.2
    Safari: 15.3
  npmPackages:
    @storybook/addon-actions: 6.4.0-alpha.34 => 6.4.0-alpha.34 
    @storybook/addon-docs: 6.4.0-alpha.34 => 6.4.0-alpha.34 
    @storybook/addon-essentials: 6.4.0-alpha.34 => 6.4.0-alpha.34 
    @storybook/addon-links: 6.4.0-alpha.34 => 6.4.0-alpha.34 
    @storybook/angular: 6.4.0-alpha.34 => 6.4.0-alpha.34 
    @storybook/builder-webpack5: 6.4.0-alpha.34 => 6.4.0-alpha.34 
    @storybook/manager-webpack5: 6.4.0-alpha.34 => 6.4.0-alpha.34 

```

### Additional context:
Issue https://github.com/storybookjs/storybook/issues/17302 is related to this one, I will close that issue in favour of this new one here.
Repository: go
Issue: cmd/asm: amd64 MOVBQZX instructions referring to upper-byte registers are not rejected
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.3 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Haven't checked

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/wojtek/.cache/go-build"
GOENV="/home/wojtek/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/wojtek/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/wojtek/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.17"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.17/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.3"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2132970980=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Consider this simple program

`main.go`

```
package main

// go:noescape
func asmfun()
func main() { asmfun() }
```

and the asm implementation --- `asmfun_amd64.s`

```
#include "textflag.h"

TEXT ·asmfun(SB), NOSPLIT, $0
    // wrong code
    MOVBQZX AH, AX
    MOVBQZX BH, AX
    MOVBQZX CH, AX
    MOVBQZX DH, AX
    RET   
```

### What did you expect to see?

I'd expect the assembler to reject invalid code, as referencing the upper-byte
registers is impossible.

### What did you see instead?

```
$ go build
$ go tool objdump -s asmfun main
TEXT main.asmfun.abi0(SB) /home/wojtek/t/bug/asmfun_amd64.s
  asmfun_amd64.s:5  0x455420        480fb6c4        MOVZX SP, AX        
  asmfun_amd64.s:6  0x455424        480fb6c7        MOVZX DI, AX        
  asmfun_amd64.s:7  0x455428        480fb6c5        MOVZX BP, AX        
  asmfun_amd64.s:8  0x45542c        480fb6c6        MOVZX SI, AX        
  asmfun_amd64.s:9  0x455430        c3              RET         
```
Repository: TypeScript
Issue: `@deprecated` incorrectly marks the wrong type as deprecated when used in JavaScript.
Labels: Bug,Help Wanted,Domain: JSDoc

# Bug Report

### 🔎 Search Terms

deprecated jsdoc js 

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `deprecated`

### ⏯ 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.
-->
[Playground](https://www.typescriptlang.org/play?ts=4.5.4&ssl=2&ssc=5&pln=2&pc=15&filetype=js#code/PQKhCgAIUgBATApgBwE6IMYEMAuj5Qyw4Cey+iAZpAN4B2ArgLYBGiqkAPpAM46oBLOgHMAvpACyJACplEhYOHAYANlh49IAMQD2O2lEhHQEI2aLIsqLE1pTZ5cQA9D5xWciU9ACicBKA1dIUXAQ5R06PkgnSABeSDpEAHdtHz8AbnAnADovHW8AVgygA) (JavaScript)
[Playground](https://www.typescriptlang.org/play?ts=4.5.4#code/PQKhCgAIUgBATApgBwE6IMYEMAuj5QjDg4CeyikAsqQCrmUC8kAdgK4C2ARoqpAD6QAzjlQBLFgHMA3OHAYANliFDIAMQD2GyAG8okAwDMtACgAeALmp0GASl1yDBgL7hX8jSxGQzkZi0QAd3VTW1kzADpjDRMAVjCgA) (TypeScript)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
/**
 * @deprecated
 * @typedef {number | string} MyType
 */

class Foo {
    /**
     * @param {MyType} x
     *         ^^^^^^-- Not marked as deprecated
     */
    foo(x) {

    }
}

const x = new Foo();
//            ^^^--- Marked as deprecated
x.foo(5);
```

### 🙁 Actual behavior

The class `Foo` is marked as deprecated.

### 🙂 Expected behavior

The type `MyType` of parameter `x` of `Foo.foo()` should be marked as deprecated and the class `Foo` should not. Just like how it works in the TypeScript equivalent of this code.
Repository: material-ui
Issue: [Tooltip] Change `disableInteractive` default value
Labels: accessibility,discussion,breaking change,waiting for 👍,component: tooltip

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

After a tooltip is shown, moving the mouse cursor over the tooltip keeps it open indefinitely. It is hidden only when the mouse cursor is moved outside it.

![msedge_2022-01-28_12-39-44](https://user-images.githubusercontent.com/7026091/151576376-4990c5ba-0926-467b-a43b-6b9b0994526b.gif)

### Expected behavior 🤔

The tooltip should close as soon as the mouse moves outside the main element. This is illustrated in the [Material Design guidelines](https://material.io/components/tooltips#behavior): Also, the statement _"Continuously display the tooltip as long as the user long-presses or hovers over the element."_ implies that when this is no longer the case the tooltip should disappear.

See other Material Design implementations for comparison, e.g. [Vue/Quasar](https://quasar.dev/vue-components/tooltip)), does it correctly:

![msedge_2022-01-28_12-41-54](https://user-images.githubusercontent.com/7026091/151576808-a3223a4d-8a06-4110-bb62-49c534d609f9.gif)


### Steps to reproduce 🕹

To reproduce:

1. Go to the [built-in example](https://mui.com/components/tooltips/#basic-tooltip)).
2. Move the mouse cursor over the IconButton: The tooltip is shown.
3. Move the mouse cursor outside the IconButton and over the tooltip. The tooltip is still shown. It is hidden only when the mouse cursor is moved outside it.


### Context 🔦

Any context / all uses.

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>
```
  Browser: MS Edge v. 97.0.1072.69, 64 bits
    System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 14.15.0 - C:\Program Files\nodejs\node.EXE 
    Yarn: Not Found
    npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD    
  Browsers:
    Chrome: 97.0.4692.99
    Edge: Spartan (44.19041.1266.0), Chromium (97.0.1072.69)
  npmPackages:
    @emotion/react: ^11.7.1 => 11.7.1 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/base:  5.0.0-alpha.66 
    @mui/material: ^5.3.1 => 5.3.1 
    @mui/private-theming:  5.3.0 
    @mui/styled-engine:  5.3.0 
    @mui/system:  5.3.0 
    @mui/types:  7.1.0 
    @mui/utils:  5.3.0 
    @types/react: ^17.0.38 => 17.0.38 
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 ```
</details>
Repository: neovim
Issue: UI: misplaced cursor on frequent resizes
Labels: bug,ui

### Neovim version (nvim -v)

NVIM v0.7.0-dev+950-gdcd346d09

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

linux

### Terminal name/version

kitty

### $TERM environment variable

xterm-kitty

### Installation

appimage

### How to reproduce the issue

Create an init.vim:
```vim
set nu
set laststatus=0
call append(0, repeat("aaaaa ", 30))
delete
set lines=5
normal $
for i in range(12,20)
  call execute("set columns=" . (12+(20-i)))
endfor
for i in range(12,20)
  call execute("set columns=" . i)
endfor
```
And then run `nvim -u init.vim`.

### Expected behavior

Cursor is on the last character of the line, inserting characters inserts characters before the cursor.

### Actual behavior

Cursor is below the last line, inserting characters does not match cursor position.

Originally reported in https://github.com/glacambre/firenvim/issues/1289 .
Repository: transformers
Issue: [activations] pytorch-1.11+ Tanh Gelu Approximation 
Labels: Performance,WIP

# 🚀 Feature request

As kindly flagged by @vadimkantorov pt-1.11 will have a fast Tanh Gelu Approximation as implemented here https://github.com/pytorch/pytorch/pull/61439 so we could replace our manual implementation with the fast one when pt>=1.11 is detected.

for additional context please see this thread: https://github.com/pytorch/pytorch/issues/39853
Repository: go
Issue: time: Document time.Parse leap second behavior
Labels: Documentation,help wanted,NeedsInvestigation

`go version`: `go version go1.17.5 linux/amd64`

[RFC3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) documents that leap seconds will be denoted as `YYYY-MM-DDT23:59:60Z`. Attempting to parse such a value using `time.Parse` returns the following error:

```
parsing time "2022-12-31T23:59:60Z": second out of range
```
https://go.dev/play/p/es_oGD37vZl

This behavior seems perfectly reasonable, given the fact that Go's time keeping does not account for the leap second and instead uses the Unix style of time. However, while I notice that the documentation for package `time` mentions that `calendrical calculations always assume a Gregorian calendar, with no leap seconds`, it doesn't seem to indicate the parser behavior. 

I see that issues have been opened in the past to change the behavior, https://github.com/golang/go/issues/8728. This issue is just a request that the behavior be documented as part of the time package.

Happy to provide any other information needed.
Repository: flutter
Issue: [Hero] Offstage heroes should not interfere with onstage heroes
Labels: framework,a: animation,c: proposal,P3,team-framework,triaged-framework

When using something like `IndexedStack`, hero widgets that are `Offstage` are interfering with the widgets that are onstage.

This is non-intuitive, as widgets that are not currently being rendered are ineligible for hero transition from a visual perspective, why would the code be looking for them?

To reproduce, run this snippet, and observe as the heroes to not work, and throw this error:
```
There are multiple heroes that share the same tag within a subtree.

Within each subtree for which heroes are to be animated (i.e. a PageRoute subtree), each Hero must have a unique non-null tag.
In this case, multiple heroes had the following tag: logo
Here is the subtree for one of the offending heroes: Hero
```
```dart
class HeroBugTest extends StatelessWidget {
  @override
  Widget build(BuildContext context) => MaterialApp(home: MainView());
}

class MainView extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Column(children: [
      Expanded(
          child: IndexedStack(
        index: 0,
        children: [
          Hero(tag: 'logo', child: Center(child: FlutterLogo(size: 100))),
          Hero(tag: 'logo', child: Center(child: FlutterLogo(size: 100))),
        ],
      )),
      OutlinedButton(
        onPressed: () => Navigator.of(context).push(
          MaterialPageRoute(
            builder: (_) => const Hero(
              tag: 'logo',
              child: FlutterLogo(size: 400),
            ),
          ),
        ),
        child: const Text('Push Route'),
      ),
    ]);
  }
}
```

# Use Case
I have an app that uses tabs, each tab show products in different ways (favorites, search, etc), all products push a fullscreen product view when tapped.  The hero tag for every product should always be `productId`. I enforce the conditions that only one tab is visible at a time and no product can be repeated inside of a tab, so this simple approach should work nicely.

# Expected Behavior
Offstage heroes should **not** interfere with onstage heroes.

# Actual Behavior
Offstage heroes **are** interfering with the onstage heroes.
Repository: material-ui
Issue: [Container] - property `disableGutters` doesn't work if theme `styleOverrides` have been applied
Labels: support: question

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When the `Container` padding style is overridden, the `disableGutters` property stops working.

### Expected behavior 🤔

The `disableGutters` property should work even with the style override.

### Steps to reproduce 🕹

If the container style have been overridden, the `disableGutters` property won't work.

```typescript
// theme.tsx
    ...
    components: {
      MuiContainer: {
        styleOverrides: {
          root: {
            [customBreakpoints.between('xs', 'sm')]: {
              padding: '0 20px',
            },
            [customBreakpoints.up('md')]: {
              padding: '0 90px',
            },
          },
        },
      },
    },
    ...
```

```typescript
      <Container disableGutters> // won't remove gutters from 'xs' to 'sm' and above 'md'
```