sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: False positive warnings about not animatable properties
Labels: area: animations,P3

### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

No

### Description

There was already a fix for this warnings on #46666 but it didn't fix all the false positives.

For example with this code I get warnings.

```
export const collapse: AnimationTriggerMetadata = trigger('collapseAnimation', [
  state('expanded', style({ height: '*', visibility: 'visible' })),
  state('hidden', style({ height: 0, overflow: 'hidden', borderTopWidth: '0', visibility: 'hidden' })),
  transition('expanded => hidden', animate(`150ms ${AnimationCurves.EASE_IN_OUT}`)),
  transition('hidden => expanded', animate(`150ms ${AnimationCurves.EASE_IN_OUT}`)),
]);
```

```
<div class="collapse-content"
     [class.collapse-content-active]="active"
     [@collapseAnimation]="active ? 'expanded' : 'hidden'">
  <div class="collapse-content-box">
    <ng-content></ng-content>
  </div>
</div>
```

For me to remove the overflow hidden, I would have to set the style manually with the same delay as the animation.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
Warning: The animation trigger "collapseAnimation" is attempting to animate the following not animatable properties: overflow
(to check the list of all animatable properties visit https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_animated_properties)
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 14.0.4
Node: 16.15.1
Package Manager: npm 8.13.2
OS: win32 x64

Angular: 14.0.4
... cdk, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1400.4
@angular-devkit/build-angular   14.0.4
@angular-devkit/core            14.0.4
@angular-devkit/schematics      14.0.4
@angular/animations             14.0.6
@schematics/angular             14.0.4
ng-packagr                      14.0.3
rxjs                            7.5.5
typescript                      4.7.4
```


### Anything else?

_No response_
Repository: flutter
Issue: [Proposal] Select only month and year in showDatePicker or in alternative function 
Labels: c: new feature,framework,f: material design,f: date/time picker,c: proposal,P3,team-design,triaged-design

## Use case

In showDatePicker function there is no parameter to only select month and year in the dialog.

A [package](https://pub.dev/packages/month_year_picker) already exists but missing some popularity and seems not ready for production (getting few bugs, missing maintenance...).

## Proposal

Could be great to have a new parameter in showDatePicker function to be able to only select month and year or to have a new one (showMonthYearPicker ?)

Could also be nice, to have this feature fore dateRange selection
Repository: bitcoin
Issue: `externalip=...onion` ignored when onion/prox not set
Labels: Bug

My bitcoin.conf says `externalip=....onion` (among a few other IPs) but `localaddresses` in `getnetworkinfo` only lists the non-onion IPs. I assume this may (or may not) have to do with the fact that no `onion`/`proxy` is configured - the node doesn't have the ability to make outbound tor connections, but that doesn't mean anything for inbound onion connections.
Repository: godot
Issue: [3.x] Built-in toon diffuse mode too bright
Labels: bug,topic:rendering,topic:3d

### Godot version

v3.4.4.stable.fedora [419e713a2]

### System information

Fedora Linux 36 (Workstation Edition), GLES 3

### Issue description

When you set a material's diffuse mode to toon and have a light source(only tested with directional light), the lit part of the material becomes significantly brighter than normal materials of the same albedo with Burly(ddefault) diffuse mode.

This is more noticeable with the Glow effect enabled(screen mode) and shadow disabled(a separate issue of toon shader being dependent on shadowmap instead of dot product?).

Testing condition:
- Directional light energy at 1
- default skybox

## With shadows
### Without glow
![image](https://user-images.githubusercontent.com/25323231/180297817-d4738a07-6f5d-47a2-aa65-ec13b669d0dd.png)

### With glow
![image](https://user-images.githubusercontent.com/25323231/180297838-b74b6af7-d4d2-413d-9764-53be90c26c60.png)

## Without shadows
### Without glow
![image](https://user-images.githubusercontent.com/25323231/180297907-e1277355-edbe-49aa-80bb-9f5947aee383.png)

### With glow
![image](https://user-images.githubusercontent.com/25323231/180297942-04b8c5f9-ed9d-45b7-a183-968be96de37c.png)


### Steps to reproduce

1. New scene
2. Add directional light
3. Add mesh with toon material
4. Burn your retinas

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: Unknown builtin op: aten::broadcast_shapes
Labels: oncall: jit

### 🚀 The feature, motivation and pitch

`torch.broadcast_shapes` doesn't work with torch.jit.script：
```
@torch.jit.script
def broadcast_common_batch_shape(x, x_data, y_data):
    common_shape = torch.broadcast_shapes(x.size()[:-1], x_data.size()[:-1], y_data.size()[:-1])
    return (torch.broadcast_to(x, common_shape + x.size()[-1:]).contiguous(),
                torch.broadcast_to(x_data, common_shape + x_data.size()[-1:]).contiguous(),
                torch.broadcast_to(y_data, common_shape + y_data.size()[-1:]).contiguous())
````
It would be pleased to have this feature.

### Alternatives

_No response_

### Additional context

_No response_
Repository: transformers
Issue: Onnx Runtime Errors With LongT5
Labels: Good Second Issue,bug,ONNX

### System Info

- `optimum` version: 1.2.3 (installed via Github installation)
- `transformers` version: 4.20.1
- Platform: Linux-5.4.188+-x86_64-with-Ubuntu-18.04-bionic
- Python version: 3.7.13
- Huggingface_hub version: 0.8.1
- PyTorch version (GPU?): 1.11.0+cu113 (False)
- Tensorflow version (GPU?): 2.8.2 (False)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed
- Using GPU in script?: no
- Using distributed or parallel set-up in script?: no

### Who can help?

@stancld @echarlaix @LysandreJik

### Information

- [ ] The official example scripts
- [X] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [x] My own task or dataset (give details below)

### Reproduction

LongT5 with TGlobal Attention isn't able to run sequences longer than **global_block_size * 2**. This is because during the model tracing [num_globals > 0](https://github.com/huggingface/transformers/blob/main/src/transformers/models/longt5/modeling_longt5.py#L191) is being converted to False. I originally posted the error in Optimum (https://github.com/huggingface/optimum/issues/285) but @echarlaix asked me to open an issue here because this error concerns the ONNX export.

Code to reproduce is below:

```
!pip install transformers
!pip install transformers[onnx]
!python -m pip install git+https://github.com/huggingface/optimum.git
!python -m pip install git+[https://github.com/huggingface/optimum.git#egg=optimum[onnxruntime]](https://github.com/huggingface/optimum.git#egg=optimum%5Bonnxruntime%5D)
!pip install datasets
```

```py
from optimum.onnxruntime import ORTModelForSeq2SeqLM

model = ORTModelForSeq2SeqLM.from_pretrained("longt5-tglobal-base", from_transformers=True)
from transformers import AutoTokenizer, pipeline

tokenizer = AutoTokenizer.from_pretrained('google/long-t5-tglobal-base')

onnx_summarization = pipeline("summarization", model=model, tokenizer=tokenizer)

text = # Something longer than 32 tokens if I don't change the number of global blocks
pred = onnx_summarization(text)`
```
```
RuntimeException: [ONNXRuntimeError] : 6 : RUNTIME_EXCEPTION : Non-zero status code returned while running LessOrEqual node. Name:'LessOrEqual_648' Status Message: /onnxruntime_src/onnxruntime/core/providers/cpu/math/element_wise_ops.h:603 onnxruntime::Broadcaster::Broadcaster(gsl::span, gsl::span) largest <= 1 was false. Can broadcast 0 by 0 or 1. 16 is invalid.
```
### Expected behavior

Should work for very large seq lens on default global block size without error
Repository: pytorch
Issue: Make sure we always redispatch through a dispatcher for all SymInt ops
Labels: triaged
Repository: pytorch
Issue: Devirtualize sym_sizes, virtualize sym_sizes_custom
Labels: triaged
Repository: pytorch
Issue: Investigate if it's okay to throw a RuntimeError instead of TypeError here : https://github.com/pytorch/pytorch/pull/79560/files#diff-415017bcad4fa6cd6d3dfe5f6ea1caffcd7122b46b8c1e4825f7d889efc80a62R1816
Labels: triaged
Repository: pytorch
Issue: Investigate adding Dockerfile linter hadolint to CI
Labels: module: ci,triaged

https://github.com/hadolint/hadolint

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: Investigate adding shell linter/checker to CI
Labels: module: ci,triaged

I randomly ran https://github.com/koalaman/shellcheck and already found one legitimate bug: https://github.com/pytorch/pytorch/pull/81954

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: Overloading multiple signatures for a single ref
Labels: triaged,module: primTorch

Consider an op like `arange` which is able to support the following two signatures using python arg parser

https://github.com/pytorch/pytorch/blob/8d0cbce0696e76c9e4c929c24c0331df25125b40/torch/csrc/autograd/python_torch_functions_manual.cpp#L87-L90

It seems tricky to add an op like this since Python does not support overloads and arguments with defaults must come after arguments that don't have defaults.  

but one solution could be to accept a more general signature and parse it yourself (similar to what python arg parser does):
  - in the below example, we have `arange(arg1: optional[Number], arg2: optional[Number], step=1, *, ...)`  add in the function body, have checks to route the call to the correct prim, which itself does not take any optional arguments
  - registering stubs with `@overload` decorator from the `typing` module seems to help with static checking tools 

https://github.com/pytorch/pytorch/blob/d1a9372e611b6e833f83fab57816819b7732e1cc/torch/_refs/__init__.py#L2989-L3055

Curious if others think this is a good general solution

cc @ezyang @mruberry @ngimel
Repository: vscode
Issue: Git - diff compare views don't update view when click + and switch to next conflicting file
Labels: feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.69.1
- OS Version: mac

Steps to Reproduce:

1. merging branch 
2. fix conflicts for one file 
3. click +
4. it will automatically switch to next file 
5. but diff compare are not loaded out
Repository: rust
Issue: Compiler suggestions give invalid syntax when trying to constraint associated type with a trait that has the same name as a derive macro
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics,D-papercut,D-invalid-suggestion

Sorry if this is duplicated, I think it's well known that problems with derive macros and their correspondent traits are quite a pain to handle, but I couldn't find this reported yet.

Given the following code: [play](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=2318f3f870cbcd28950dc28e2d0bfe6c)

```rust
struct Foo;
struct Bar;

impl TryInto<Foo> for Bar {
    type Error = ();
    fn try_into(self) -> Result<Foo, Self::Error> {
        Ok(Foo)
    }
}

fn baz(foo: impl TryInto<Foo>) {
    foo.try_into().unwrap();
}
```

The current output correctly tells me that I need to constrain the `TryInto::Error` with `Debug`:

```rust
error[E0277]: `<impl TryInto<Foo> as TryInto<Foo>>::Error` doesn't implement `Debug`
    --> src/main.rs:14:20
     |
14   |     foo.try_into().unwrap();
     |                    ^^^^^^ `<impl TryInto<Foo> as TryInto<Foo>>::Error` cannot be formatted using `{:?}` because it doesn't implement `Debug`
     |
     = help: the trait `Debug` is not implemented for `<impl TryInto<Foo> as TryInto<Foo>>::Error`
note: required by a bound in `Result::<T, E>::unwrap`
    --> /.../.rustup/toolchains/stable-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/result.rs:1074:12
     |
1074 |         E: fmt::Debug,
     |            ^^^^^^^^^^ required by this bound in `Result::<T, E>::unwrap`
help: introduce a type parameter with a trait bound instead of using `impl Trait`
     |
11   | fn baz<T: TryInto<Foo>>(foo: T) where <T as TryInto<Foo>>::Error: Debug {
     |       +++++++++++++++++      ~  +++++++++++++++++++++++++++++++++++++++

```

But if I just copy and paste the suggestion, without having the `Debug` trait in the scope, the compiler will correctly fail to compile, and even instruct me to bring the correct trait into scope, but also suggests an invalid syntax in the `where` clause:

```rust
error[E0404]: expected trait, found derive macro `Debug`
  --> src/main.rs:12:71
   |
12 |     fn baz<T: TryInto<Foo>>(foo: T) where <T as TryInto<Foo>>::Error: Debug {
   |                                                                       ^^^^^ not a trait
   |
help: constrain the associated type to `Debug`
   |
12 |     fn baz<T: TryInto<Foo>>(foo: T) where T: TryInto<Foo><Error = Debug> {
   |                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
help: consider importing one of these items instead
   |
1  | use core::fmt::Debug;
   |
1  | use std::fmt::Debug;
```

Ideally, the compiler would instruct me to import the correct trait in the first error, giving no chance to output `TryInto<Foo><Error = Debug>`
Repository: neovim
Issue: Set winbar throws not enough space error even when there's space.
Labels: bug,floatwin,statusline,options

### Neovim version (nvim -v)

0.8.0 commit 1f1863ed5

### Vim (not Nvim) behaves the same?

no

### Operating system/version

Arch linux

### Terminal name/version

Kitty terminal

### $TERM environment variable

screen-256color

### Installation

build from repo

### How to reproduce the issue

### Reproduction steps
```lua
-- file: minimal_reproduce.lua
local win = vim.api.nvim_get_current_win()
vim.wo[win].winbar = '%f'

local grp = vim.api.nvim_create_augroup('asdf', {clear=true})
vim.api.nvim_create_autocmd('WinEnter', {
  group = grp,
  pattern = '*',
  desc = 'winbar crash?',
  callback = function ()
    vim.wo[win].winbar = '%f'
  end
})

local buf = vim.api.nvim_create_buf(false, true)
vim.api.nvim_open_win(buf, true, {
  relative = "win",
  win = win,
  border = 'single',
  col = 1,
  row = 1,
  height = 1,
  width = 40,
})
```

```sh
nvim --clean minimal_reproduce.lua
:lua require('minimal_reproduce')
```

### Things to note
- A winbar on current win is already set.
- We are trying to set winbar of previous win while entering the float of height 1 in auto command context.

### Expected behavior

No error should be thrown as the original window has enough space in it to draw winbar.

### Actual behavior

It throws following error
```
Error detected while processing WinEnter Autocommands for "*":
Error executing lua callback: ./minimal_reproduce.lua:10: Vim:E36: Not enough room
stack traceback:
        [C]: in function '__newindex'
        ./minimal_reproduce.lua:10: in function <./minimal_reproduce.lua:9>
        [C]: in function 'nvim_open_win'
        ./minimal_reproduce.lua:15: in main chunk
        [C]: in function 'require'
        [string ":lua"]:1: in main chunk
```

### Speculations 
It seems nvim is trying to draw winbar on the float even though winbar option in that window is empty . This can actually be seen if you open the float with height 2 the float buffer starts after an empty line.


@famiu  any clue ?
Repository: pytorch
Issue: Tensor.backward type hints clarification
Labels: module: docs,module: autograd,module: typing,triaged,actionable

### 📚 The doc issue

The signature of `Tensor.backward` looks like this:
https://github.com/pytorch/pytorch/blob/c52ee6dc0a00dd46f9424424b59dd8714496e9a1/torch/_tensor.py#L425-L427

And in the docstring it defines the args like this:
https://github.com/pytorch/pytorch/blob/c52ee6dc0a00dd46f9424424b59dd8714496e9a1/torch/_tensor.py#L454-L472

I'd like to clarify a few things about the types here. I have numbered them to allow for easier discussion.
* gradient (Tensor or None): 
1. It seems that the type here is clearly `Optional[torch.Tensor]`
2. I find the sentence "If a None value would be acceptable then this argument is optional." a bit odd - should we remove it? 

* retain_graph (bool, optional):
3. Why does this default to `None` rather than `False`?
       
* inputs (sequence of Tensor): 
4. It seems that the type is `Optional[Sequence[torch.Tensor]]` - should we update the docstring to say it is optional like the others?


### Suggest a potential alternative/fix

Should we add type hints?

cc @svekars @holly1238 @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @malfet @rgommers @xuzhao9 @gramster
Repository: next.js
Issue: Regression in 12.2.0: BrowserslistError during build
Labels: bug

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.14.0
      npm: 8.3.1
      Yarn: 1.22.17
      pnpm: N/A
    Relevant packages:
      next: 12.2.3
      eslint-config-next: N/A
      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)

_No response_

### Describe the Bug

When the `.browserslistrc` file contains a line `current node`, the next build fails with this error:
```
BrowserslistError: Unknown version 16.15.1 of Node.js
```

### Expected Behavior

It used to work in next.js < 12.2.0.

`current node` can be a nice safety net to compile down js features that are available in all targeted browsers but not in the used node version. Unlikely but possible.

### Link to reproduction

https://stackblitz.com/edit/vercel-next-js-ry78bk

### To Reproduce

Open the reproduction example and run `npm run build` in the terminal.
Repository: storybook
Issue: Support for ReScript in source-loader
Labels: feature request,needs triage

**Is your feature request related to a problem? Please describe**
Currently source-loader supports JavaScript, TypeScript and Flow. From what I understand the source-loader powers things like code-snippets as well as documentation provided from JSDoc annotations.

In my project I'm using ReScript which compiles to JavaScript. However, this causes source-loader to look at the compiled JavaScript which loses a lot of documentation and causes incorrect snippets.

**Describe the solution you'd like**
Ideally I'd like source-loader to support ReScript natively, but I can understand if the current ReScript community is deemed to be too small to have first-party support and maintenance.

I'd be happy to instead be able to swap in a different source loader but from what I understand there's currently no way to change that, so that may need to be built to support the use case.

**Describe alternatives you've considered**
I've not come up with any other ways to provide Storybook with the required information for correct snippets and component docblocks but I'd be happy if an existing way to do this in userland already exists.

**Are you able to assist to bring the feature to reality?**
Yes, I'd be happy to help implement this but the way data flows through Storybook from source-code to display in the various plugin is not clear enough for me to know where to start. I'd be looking for pointers on what parts of Storybook to modify.
Repository: storybook
Issue: addon-a11y: let us choose to set wcag21aaa as our standard
Labels: feature request,has workaround,addon: a11y

**Is your feature request related to a problem? Please describe**
We want to aim for AAA accessibility, but the A11y addon uses AA as the threshold for passes and doesn't show AAA violations.

**Describe the solution you'd like**
There should be a config setting for specifying the standard you'd like A11y to use as your target.

**Describe alternatives you've considered**
We're also looking at how to specify this in jest-axe tests, but having it displayed in the Storybook UI would be a good reassurance for people who browse Storybook but don't run tests (e.g. stakeholders)

**Are you able to assist to bring the feature to reality?**
I wish, but no! I'm not skilled enough.

**Additional context**
We know this component fails AAA colour contrast check, but because it passes AA Storybook is marking it as a pass.
![image](https://user-images.githubusercontent.com/2109807/180404729-c6c289c0-d01c-479a-acab-b07fb8e1c4d4.png)