sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: libtorch 1.5 crashes when used on macs when using torch::max without AVX support
Labels: module: crash,module: cpu,triaged,module: macos

## 🐛 Bug

When using libtorch 1.5 with the torch:max function on macs without AVX support, it crashes the application using it.
Other functions such as conv1d, conv2d, ReLU seems to work fine without AVX.

## Crash Report

Here's the stack from the crash report:

Crashed Thread:                0    Dispatch queue: com.apple.main-thread

Exception Type:                EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:              0x0000000000000001, 0x0000000000000000
Exception Note:                EXC_CORPSE_NOTIFY

Termination Signal:        Illegal instruction: 4
Termination Reason:        Namespace SIGNAL, Code 0x4
Terminating Process:      exc handler [591]

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0      libtorch_cpu.dylib                        	0x000000011cd81a84 at::Tensor& c10::Dispatcher::callUnboxed<at::Tensor&, at::Tensor&, c10::Scalar>(c10::OperatorHandle const&, at::Tensor&, c10::Scalar) const + 116
1      libtorch_cpu.dylib                        	0x000000011d456d65 at::native::(anonymous namespace)::max_all_kernel_impl(at::Tensor&, at::Tensor const&) + 9893
2      libtorch_cpu.dylib                        	0x000000011c5ab66c at::native::max(at::Tensor const&) + 332
3      libtorch_cpu.dylib                        	0x000000011c90faf6 at::CPUType::max(at::Tensor const&) + 102
4      libtorch_cpu.dylib                        	0x000000011c956e82 c10::detail::wrap_kernel_functor_unboxed_<c10::detail::WrapRuntimeKernelFunctor_<at::Tensor (*)(at::Tensor const&), at::Tensor, c10::guts::typelist::typelist<at::Tensor const&> >, at::Tensor (at::Tensor const&)>::call(c10::OperatorKernel*, at::Tensor const&) + 18
5      libtorch_cpu.dylib                        	0x000000011c276701 at::Tensor c10::OperatorHandle::callUnboxed<at::Tensor, at::Tensor const&>(at::Tensor const&) const + 241
6      libtorch_cpu.dylib                        	0x000000011e8390a5 torch::autograd::VariableType::max(at::Tensor const&) + 1349
7      libtorch_cpu.dylib                        	0x000000011c956e82 c10::detail::wrap_kernel_functor_unboxed_<c10::detail::WrapRuntimeKernelFunctor_<at::Tensor (*)(at::Tensor const&), at::Tensor, c10::guts::typelist::typelist<at::Tensor const&> >, at::Tensor (at::Tensor const&)>::call(c10::OperatorKernel*, at::Tensor const&) + 18

## Environment

Official libtorch 1.5 binaries.
macOS High Sierra, macOS Mojave
CPU without AVX instructions (for instance, mac pro 2010).

cc @VitalyFedyunin
Repository: storybook
Issue: CLI: Typings for parameters
Labels: feature request,api: addons,cli,typescript

Typings for addon-specific parameters:
- [ ] Define extensibility structure (e.g. `.storybook/typings.d.ts`)
- [ ] Define how addons modify this structure (e.g. codemod from `sb add`, manual config)
- [ ] Typings for essential addons:
  - [ ] actions
  - [ ] backgrounds
  - [ ] controls
  - [ ] docs
  - [ ] viewport
- [ ] Add to CLI templates
Repository: storybook
Issue: CLI: Typings for frameworks
Labels: feature request,cli,typescript

In late 6.0 we defined a type structure for [React](https://github.com/storybookjs/storybook/pull/11811) and [Angular](https://github.com/storybookjs/storybook/pull/11825). Apply to the remaining templates and update as needed:

### Core
- [x] [react](https://github.com/storybookjs/storybook/pull/11811)
- [x] [angular](https://github.com/storybookjs/storybook/pull/11825)
- [x] [vue](https://github.com/storybookjs/storybook/pull/12037)
- [x] [web-components](https://github.com/storybookjs/storybook/pull/12026)

### Other
- [ ] aurelia
- [ ] ember
- [ ] html
- [ ] marionette
- [ ] marko
- [ ] mithril
- [x] preact
- [ ] rax
- [ ] riot
- [ ] svelte
Repository: scrcpy
Issue: Power button stopped working until adb reboot
Labels: screenoff

 - [✔️] I have read the [FAQ](https://github.com/Genymobile/scrcpy/blob/master/FAQ.md).
 - [✔️] I have searched in existing [issues](https://github.com/Genymobile/scrcpy/issues).

**Environment**
 - OS: Windows 10 Home Version 1909
 - scrcpy version: e.g. 1.15.1
 - installation method: Windows release
 - device model: LG G6
 - Android version: 8.0.0

**Describe the bug**
This was really scary and I can't figure out how to reproduce it, but basically, after tinkering around with tapping as well as holding Ctrl+P and Alt+P (I am that right-alt guy who is using `--shortcut-mod=lalt,ralt`), the power button stopped recognizing ALL input, whether through scrcpy or through physical pressing.

It stopped working while the device was being used by scrcpy via USB. And then when I disconnected the phone, even the physical power button did nothing, for the first time ever in my over-2-years with this phone. I even thought it had somehow gotten damaged, but running `adb reboot` got it back up as usual now. I don't know what happened.

Unfortunately I used no-console and also since closed and reopened scrcpy and don't know how to retrieve the record of activity... I will recomment if I'm somehow able to duplicate this issue.
Repository: rust
Issue: `TypeId` and Polymorphization
Labels: -Zpolymorphize

When polymorphization is enabled (`-Zpolymorphization=on`), then this can currently be observed by `TypeId`. For example, the following code when built with a polymorphization-enabled compiler will fail the asserts (and succeeds normally; [playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=0fc2372645557cbbdc60f2d8d0e5be80)):

```rust
fn nop<T>() {}

fn test_the_waters<A: 'static, B: 'static>(a: A, _: B) {
    let any: Box<dyn std::any::Any> = Box::new(a);
    assert!(any.downcast_ref::<A>().is_some());
    assert!(any.downcast_ref::<B>().is_none());
    assert!(any.downcast_ref::<fn()>().is_none());
}

fn main() {
    test_the_waters(nop::<u32>, nop::<u64>);
}
```

This issue was discovered while investigating an earlier regression. After #74538 landed, the example shown below, where a polymorphized closure is indirectly passed to `TypeId`, would result in an ICE ([discussion from that investigation](https://rust-lang.zulipchat.com/#narrow/stream/216091-t-compiler.2Fwg-polymorphization/topic/tokio.20regression.20%28.2374614%29/near/204662905)):

```rust
use std::any::TypeId;

pub fn foo<T: 'static>(_: T) -> TypeId {
    TypeId::of::<T>()
}

fn outer<T: 'static>() -> TypeId {
    foo(|| ())
}

fn main() {
    assert!(outer::<u8>() != outer::<u16>());
}
```

In #74717, the check introduced in #74538 was modified so that this case (and another unrelated case) would no longer ICE for polymorphized functions ([discussion regarding that PR](https://rust-lang.zulipchat.com/#narrow/stream/216091-t-compiler.2Fwg-polymorphization/topic/tokio.20regression.20%28.2374614%29/near/205592381)). There have been [more recent discussion regarding this](https://rust-lang.zulipchat.com/#narrow/stream/216091-t-compiler.2Fwg-polymorphization/topic/TypeId.20guarantees/near/206287053) in a dedicated Zulip topic.

**Unresolved questions:**

- [ ] What is the appropriate behaviour here w/r/t polymorphization?
    - Current consensus appears to be that functions involving reflection cannot be polymorphized.
- [ ] How do we fix this?
    - Without triggering cycle errors, detecting when polymorphization is not appropriate due to later use of `TypeId` seems very challenging.
Repository: rust
Issue: Remove `ParamEnv::reveal_all` from codegen
Labels: C-enhancement,A-codegen,T-compiler,-Zpolymorphize

Instead of using `ParamEnv::reveal_all`, the `ParamEnv` should be tracked in the mono item - this is necessary to enable more complex forms of polymorphization in future. 

> something simple like trying `layout_of(ty)` on various types in the MIR body and ignoring generics in `ty` if it succeeds, should work, but the lack of a correct `ParamEnv` would make it fail later (especially if e.g. it's something like `&T` which only has a constant layout if `T: Sized`)

(source: [eddyb in Zulip](https://rust-lang.zulipchat.com/#narrow/stream/216091-t-compiler.2Fwg-polymorphization/topic/next.20steps/near/204597203))
Repository: rust
Issue: Macro expansion moves comments around.
Labels: A-pretty

```rust

pub fn bar() {
    println!("Hello, World!");
}


// hello...

pub fn foo() {
    /*
    some
    comment
    */
}

// ...world!
```

([Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=9be4f9ada5f085e66bd203de17d6bc99))

Macro Expansion:

```
#![feature(prelude_import)]
#[prelude_import]
use std::prelude::v1::*;
#[macro_use]
extern crate std;
pub fn bar() {


    // hello...

    /*
    some
    comment
    */

    // ...world!
    {
        ::std::io::_print(::core::fmt::Arguments::new_v1(&["Hello, World!\n"],
                                                         &match () {
                                                              () => [],
                                                          }));
    };
}
pub fn foo() { }
```
Repository: rust
Issue: Rustdoc wrapper doesn't support --on-fail=print-env
Labels: T-bootstrap,C-bug

This makes it impossible to e.g. run gdb on rustdoc for a failure that only happens when documenting the standard library.
Repository: rust
Issue: Investigate speeding up `x86_64-apple` jobs
Labels: O-macos,I-compiletime,T-infra

Looking at some most recent builds, it looks like the `x86_64-apple` family of jobs are usually the last to finish, and take significantly longer (over an hour) than certain other jobs. Speeding up these jobs could give us a nice win in build times.

I don't know how much of the build time is under our control (e.g. running more work on these jobs vs other jobs), and how much is related to the Github Actions OS X builders being slower.
Repository: flutter
Issue: Toast as material design element
Labels: framework,f: material design,c: proposal,team-design,triaged-design


### The feature:
Toasts/Snackbars are a core and one of the widely used components which is essential in responding to any event in the app.Ranging from user interactions to network errors and more.

### Alternatives:
There are a lot of alternatives on [pub.dev](https://pub.dev/packages?q=toast)

### Why not use Alternatives?
There are a ton of options available and those might be overwhelming to the new devs who are coming from other languages and don't know where to start. Having options is a great thing which is necessary until it causes something like "Analysis Paralysis". Having such a common feature out of the box could turn out to be helpful to a lot of people.
Repository: flutter
Issue: Support for range value to be from anywhere in the Slider widget, separate from min/max value
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
HI
I want minimum value Slider widget. It seems that the Slider Widget doesn't support it now.
I tried to rotate it but it gets weird when showing the label.

<img width="208" alt="z" src="https://user-images.githubusercontent.com/31924892/89734475-3dcd4100-da97-11ea-883c-9aa16c82c819.png">


<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->

It would be nice if the slider widget has a reverse property so I can specify a minimum value!
Repository: excalidraw
Issue: decouple hit tests from the bindable concept
Labels: refactor

I think it's just a temporary coincidence that non-linear elements are bindable at the same time (in the future we may wanna make filled linear shapes bindable too).

Either way, I'd rename `distanceToBindableElement` since it couples unrelated code to the binding concept, but want to run it through @xixixao first.

Also, `distanceToRectangle()` name isn't correct either as it tests against text elements, too (→ not a rectangle).
Repository: godot
Issue: Error reporting when using for loop with local variable
Labels: topic:gdscript

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
Godot 3.2.2.stable.official

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Windows 10 Pro 1903

**Issue description:**
<!-- What happened, and what was expected. -->
Parser error "variable already defined with the scope" when trying to use an already defined variable in for loop.
Error not occurring when loop is using a global variable.

**Steps to reproduce:**
Declare a local variable of any type, define for loop using this variable

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[TEST_variables.zip](https://github.com/godotengine/godot/files/5047970/TEST_variables.zip)
Repository: flutter
Issue: Choose priority order for DeviceOrientation in setPreferredOrientations when rotating device 
Labels: c: new feature,platform-android,platform-ios,framework,engine,c: proposal,a: layout,P3,team-engine,triaged-engine

Hi everyone!

I'm doing following call at one of my pages:
```
  @override
  void initState() {
    SystemChrome.setPreferredOrientations([
      DeviceOrientation.landscapeRight,
      DeviceOrientation.landscapeLeft,
    ]);
```
The rotation is always going right, even if I change the order.
Is there some way to set which landscape orientation you would prefer?
Repository: rust
Issue: Invalid help message when traits in #[derive()] miss type annotation
Labels: T-compiler,C-bug,A-suggestion-diagnostics,D-invalid-suggestion


```rust

#[derive(Serialize, Deserialize)]
struct Container<T: Serialize + Deserialize> {
	data: T
}

```

Which gives me this error message:

```
error[E0283]: type annotations needed
  --> src/main.rs:33:21
   |
33 | #[derive(Serialize, Deserialize)]
   |                     ^^^^^^^^^^^ cannot infer type for type parameter `T`
34 | struct Container<T: Serialize + Deserialize> {
   |                                 ----------- required by this bound in `Container`
   |
   = note: cannot satisfy `T: _::_serde::Deserialize<'static>`
   = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider specifying the type argument in the function call
   |
33 | #[derive(Serialize, Deserialize::<T>)]
```

Which suggests invalid modification.

`rustc --version --verbose`:
```
rustc 1.47.0-nightly (09f4c9f50 2020-08-07)
binary: rustc
commit-hash: 09f4c9f5082f78b0adcee83d3ab4337e000cd28e
commit-date: 2020-08-07
host: x86_64-unknown-linux-gnu
release: 1.47.0-nightly
LLVM version: 10.0
```
Repository: godot
Issue: AnimationPlayer Easing negative values
Labels: bug,topic:animation

**Godot version:**

v3.2.2

**OS/device including version:**
Win10 1909

**Issue description:**

In a frame seting an AnimationPlayers frame Easing to -1 the curve visualy changes in the editor but in reality it is the same as seting it to 1

**Steps to reproduce:**

1. add AnimationPlayer.
2. Add an animation 
3. Add a keyframe 
4. Set Easing not with puling but by dubbel clicking and typing -1 
5. The curve now [looks like this](https://upload.wikimedia.org/wikipedia/commons/c/ca/Normal_Distribution_CDF.svg)

**Minimal reproduction project:**

[bug report.zip](https://github.com/godotengine/godot/files/5048378/bug.report.zip)
Repository: godot
Issue: SDFGI: Massive slowdown when the camera speed is too fast (even on empty scenes)
Labels: discussion,topic:rendering,confirmed,documentation,topic:3d,performance

**Godot version:**
no commit hash, as it was compiled by hand, but it's probably the one starting from here
https://github.com/godotengine/godot/commit/f2149fe763a5678237b417fb9fefec5a5c74ae9d

**OS/device including version:**
windows 10 1709 16299.431
vulkan
r9 380 4 gb ggdr 5 1425 mhz

AMD stuff
2020.0729.1547.28422
20.20.01.13-200729a-357776E-RadeonSoftwareAdrenalin2020

**Issue description:**
if you increase your camera speed, to a very high value, the framerate drops into the 20s

this is bad if you were to make, a space game with a space ship, which needs to fly VERY FAST
this makes using the editor impossible, the framerate is too low and it's barely usable at all times

**Steps to reproduce:**
1. select the file system menu
2. double click on default_env.res
3. in the inspector menu, enable sdfgi
4. select the view port
5. move the camera around and increase the camera's movement speed until it starts to stutter (scroll wheel up)
6. your framerate is destroyed
![](https://i.imgur.com/bzcUBVp.png)

**Minimal reproduction project:**
even an empty project will do

if you move slowly, the framerate is fine
if you move quickly, it all goes to hell

disabling SDFGI fixes the framerate
Repository: godot
Issue: Raycast can collide with area even if monitorable property is set to false
Labels: discussion,topic:physics

**Godot version:**
Godot 3.2.3 RC 3

**OS/device including version:**
Windows 10

**Issue description:**
When monitorable property of an area is set to false, other area can't detect it as the documention explains it.
But raycasts can still collide with this area.

I know that there is an input_ray_pickable property but it seems very strange that unmonitorable area are not so unmonitorable.

So bug or feature ?
Thanks.


**Steps to reproduce:**
Set up a raycast and an area with monitorable set to false.
Raycast can still detect aera.
Repository: pytorch
Issue: distributed training with c10d does not work with layerdrop in pytorch > 1.4
Labels: high priority,oncall: distributed,triaged

training any model that uses layerdrop (probabilistically skip transformer layers during training) works poorly with c10d distributed training backend (using fairseq). in pytorch 1.4 training would freeze, but if you specified --find-unused-parameters, then it would work. in pytorch 1.5 and above, the training always crashes with an error about inconsistent gradients.

to repro try any transformer based model in fairseq with the c10d backend and layerdrop > 0

for example, for wav2vec 2.0 (from the readme):

python train.py --distributed-world-size 64 --distributed-port $PORT /manifest/path \
--save-dir /model/path fp16 --num-workers 6 --task audio_pretraining --criterion wav2vec --arch wav2vec2 \
--log-keys '["prob_perplexity","code_perplexity","temp"]' --quantize-targets --extractor-mode default \
--conv-feature-layers '[(512, 10, 5)] + [(512, 3, 2)] * 4 + [(512,2,2)] * 2' --final-dim 256 --latent-vars 320 \
--latent-groups 2 --latent-temp '(2,0.5,0.999995)' --infonce --optimizer adam \
--adam-betas '(0.9,0.98)' --adam-eps 1e-06 --lr-scheduler polynomial_decay --total-num-update 400000 \
--lr 0.0005 --warmup-updates 32000 --mask-length 10 --mask-prob 0.65 --mask-selection static --mask-other 0 \
--encoder-layerdrop 0.05 --dropout-input 0.1 --dropout-features 0.1 --feature-grad-mult 0.1 \
--loss-weights '[0.1, 10]' --conv-pos 128 --conv-pos-groups 16 --num-negatives 100 --cross-sample-negatives 0 \
--max-sample-size 250000 --min-sample-size 32000 --dropout 0.1 --attention-dropout 0.1 --weight-decay 0.01 \
--max-tokens 1400000 --max-update 400000 --skip-invalid-size-inputs-valid-test

try with: --find-unused-parameters with pytorch 1.4, or --backend no_c10d (pytorch 1.5+) to get this to actually work

cc @ezyang @gchanan @zou3519 @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar @jiayisuse @agolynski
Repository: go
Issue: x/tools/gopls: consider auto-detecting the module to provide -local without a config
Labels: help wanted,FeatureRequest,gopls,Tools,gopls/imports

See the conversation on https://github.com/golang/go/issues/31999 and https://github.com/golang/go/issues/32049.
Could we add some special value of the setting and have it automatically infer the name of the current module? For use cases where `-local` is not necessarily the path of current module, we could still allow a configuration as before.

/cc @heschik
Repository: flutter
Issue: How to change CameraController.value.aspectRatio 16:9 to 4:3
Labels: d: api docs,p: camera,package,team-ecosystem,P3,triaged-ecosystem

<!-- Thank you for using Flutter!

     Please check out our documentation first:
      * https://flutter.dev/
      * https://api.flutter.dev/

     If you can't find the answer there, please consider asking a question on
     the Stack Overflow Web site:
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     Please don't file a GitHub issue for support requests. GitHub issues are
     for tracking defects in the product. If you file a bug asking for help, we
     will consider this a request for a documentation update.

-->

My phone is Pixel 3.
I make 4 : 3 aspectRatio Camera App.
but defalut is 16 : 9

`AspectRatio(
                aspectRatio: 1,
                child: ClipRect(
                  child: Transform.scale(
                    scale: 1 / 0.75,
                    child: Center(
                      child: AspectRatio(
                        aspectRatio: 0.75,
                        child: CameraPreview(_cameraController),
                      ),
                    ),
                  ),
                ),
              ),`

this code is CameraPreview has 3 : 4 aspectRatio.
Repository: pytorch
Issue: Unbuffered operation
Labels: triaged,enhancement,module: numpy,function request

## 🚀 Feature

Add unbuffered operations to pytorch (e.g. `np.add.at`, see [ufuncs.at docs](https://numpy.org/doc/stable/reference/generated/numpy.ufunc.at.html#numpy.ufunc.at)), which handles repeated indices correctly

```python
import torch
a = torch.zeros(4)
torch.add_unbuffered(a, [1,1,2,3], 1)
# instead of a[[1,1,2,3]] += 1

# should get [0,2,1,1] instead of [0,1,1,1]
```

## Motivation

`numpy` have unbuffered operations (e.g. `np.add.at`) which allows repeated indices in a vectorized operation to work correctly. This is handy when doing counting and probability stuff.

```python
a = np.random.randint(0, 256, 10000)
count = np.zeros(256, int)
np.add.at(count, a, 1)
# instead of count[a] += 1
```

## Alternatives

Alternatively, the whole `ufunc` design from numpy can be taken, which adds generic functionality like `reduce`, `accumulate`, `add` to all kinds of operations.



cc @mruberry @rgommers