sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Target debug_universal_framework failed: Exception: Unsupported iOS arch name "i386" build failed
Labels: platform-ios,tool,P3,team-ios,triaged-ios

I tried running on a iPhone 5 iOS 10.3 simulator in Xcode, and `debug_universal_framework` fails.

Note the `-dIosArchs=i386`:
```
Showing Recent Messages
...

Showing Recent Messages
♦ /Users/m/Projects/flutter/bin/flutter --verbose assemble --output=/Users/m/Projects/test_create/ios/Flutter/ -dTargetPlatform=ios -dTargetFile=/Users/m/Projects/test_create/lib/main.dart -dBuildMode=debug -dIosArchs=i386 -dSplitDebugInfo= -dTreeShakeIcons=false -dTrackWidgetCreation=true -dDartObfuscation=false -dEnableBitcode= -dDartDefines= -dExtraFrontEndOptions= debug_ios_bundle_flutter_assets


[+1570 ms] debug_universal_framework: Starting due to {InvalidatedReason.inputChanged}
...
[   +6 ms] Target debug_universal_framework failed: Exception: Unsupported iOS arch name "i386"
build failed.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      AssembleCommand.runCommand (package:flutter_tools/src/commands/assemble.dart:197:7)
```
```
$ flutter doctor -v
[✓] Flutter (Channel unknown, v1.18.1-pre.14, on Mac OS X 10.15.4 19E266, locale en-US)
    • Flutter version 1.18.1-pre.14 at /Users/m/Projects/flutter
    • Framework revision 0a8b590943 (18 minutes ago), 2020-04-06 14:54:52 -0700
    • Engine revision 9b8dcc7ecf
    • Dart version 2.8.0 (build 2.8.0-dev.20.0 05103dfe5a)

 
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/m/Library/Android/sdk
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
    • Xcode at /Users/m/Applications/Xcode-11-4.app/Contents/Developer
    • Xcode 11.4, Build version 11E146
    • CocoaPods version 1.9.0

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 44.0.2
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] IntelliJ IDEA Community Edition (version 2019.2.4)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 41.1.3
    • Dart plugin version 192.7402

[✓] VS Code (version 1.43.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.6.0

[✓] Connected device (2 available)
    • iPhone 8 Plus • D919CFD4-7DB9-4CE3-B3A1-8A56B33E9901 • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-4 (simulator)
    • iPhone 5 10_3 • C9076A75-FF73-408F-850B-8034CB75CA03 • ios • com.apple.CoreSimulator.SimRuntime.iOS-10-3 (simulator)
```
Repository: godot
Issue: Consider always saving the rendering API name
Labels: enhancement,discussion,topic:editor

If you set a project to use GLES 2, this is saved in the `project.godot` file:

```
[rendering]

quality/driver/driver_name="GLES2"
```

However, this string is not saved with a GLES 3 project in Godot 3.2, or in a Vulkan project in the current master. I think it would make sense for this string to always be saved.

This would help with #31171, since we could use this information to show warnings in the project manager if the project is using an unsupported API, such as if the list of rendering APIs in Godot changes in the future (ex: Opening a 3.2 GLES 3 project in Godot 4.0), or if compiling for a platform without specific APIs (ex: We'd want to show warnings for Vulkan projects if you tried to open them on a possible future ~~Raspberry Pi~~ *uh, non-Vulkan* version of Godot).
Repository: pytorch
Issue: Allow grid_sample to accept pixel units (absolute coordinates)
Labels: proposal accepted,module: nn,triaged,module: vision

_This issue is expanded from #24870 for reference and for additional discussions on implementation details. See that issue for context._

Add an option for the grid/flow input to `grid_sample` to be expressed in pixel units (absolute coordinates). This is much more natural for some applications, including image registration, where the grid-like input is actually a displacement field, and this eliminates the need for the user to convert to normalized [-1,1] coordinates, which is prone to user error, (especially when users don’t know which setting of `align_corners` to target).

This, along with #36108, would help simplify the implementation of convolutional networks to do Optical Flow Estimation and Image Registration tasks.

cc @fmassa
Repository: pytorch
Issue: Add a flow_sample function to sample optical flows and displacement fields
Labels: module: nn,triaged,enhancement

_This issue is expanded from #24870 for reference and for additional discussions on implementation details. See that issue for context._

Add a function `flow_sample` to `torch.nn.functional` which mimicks `grid_sample`, but for sampling using only the residual displacement/flow. 
This eliminates the need to constantly add an identity grid to the flow/displacement field, which is imprecise, slow, and very [prone to user error](https://discuss.pytorch.org/t/warp-video-frame-from-optical-flow/6013).

The function signatures for both `flow_sample` and `grid_sample` will be nearly identical, and both will dispatch to the same underlying kernel (the existing `grid_sample` kernel).

This, along with #36107, would help simplify the implementation of convolutional networks to do Optical Flow Estimation and Image Registration tasks.
Repository: kubernetes
Issue: default storage class for RWO vs RWM
Labels: sig/storage,kind/feature,needs-triage

We have multiple storage classes and its always unclear what to set as default, as there can be one best default for ReadWriteOnce vs ReadWriteMany.

I'd like the option to mark one storage class that is ReadWriteOnce as storageclass.kubernetes.io/is-default-class and one that is ReadWriteMany as storageclass.kubernetes.io/is-default-class and have Kubernetes pick the right default based on the users ReadWriteX request in the pvc.
Repository: rust
Issue: When supressing possibly-uninitialized errors, prefer showing the textually earlier error
Labels: A-diagnostics,T-compiler,C-bug,D-papercut

<!--
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.
-->

I tried [this code](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=308dcd45b3f1758d4924113403202780):

```rust
pub fn transliterate(mut origin: String) -> String {
    let counter: usize = origin.chars().count();
    let mut j: usize = 0;
    let mut i: usize = 0;
    let origin_vec: Vec<char> = origin.chars().collect();
    let mut origin_mutated: Vec<char>;
    if j <= counter {
        while j <= counter {
            match origin_vec[j] {
                'А' => {
                    origin_mutated[i] = 'A';
                    i += 1;
                    j += 1;
                }
                // snip
                'Я' => {
                    origin_mutated[i] = 'Y';
                    i += 1;
                    j += 1;
                    origin_mutated[i] = 'a';
                    i += 1;
                }
                _ => {
                    j += 1;
                }
            }
        }
    } else if j > counter {
        origin_mutated[i] = '\n';
    } else {
        origin = origin_mutated.into_iter().collect();
    }
    //origin = origin_mutated.into_iter().collect();
    (origin)
}

```

I expected to see this happen: the possibly-uninitialized error would report the textually first usage of `origin_mutated`

```
error[E0381]: borrow of possibly-uninitialized variable: `origin_mutated`
  --> src/lib.rs:11:21
   |
11 |                     origin_mutated[i] = 'A';
   |                     ^^^^^^^^^^^^^^ use of possibly-uninitialized `origin_mutated`
```



Instead, this happened: the possibly-uninitialized error reports the textually last usage of `origin_mutated`

```
error[E0381]: borrow of possibly-uninitialized variable: `origin_mutated`
   --> src/lib.rs:188:21
    |
188 |                     origin_mutated[i] = 'Y';
    |                     ^^^^^^^^^^^^^^ use of possibly-uninitialized `origin_mutated`
```

Originally reported by [L0uisc on irlo](https://internals.rust-lang.org/t/unexpected-location-for-compiler-error-reported/12100/2).

@rustbot modify labels: +A-diagnostics, +D-papercut
Repository: godot
Issue: `Directory` dir_exists` fails on exported projects on subpaths & paths with more than 2 slashes in `res`
Labels: bug,topic:core,confirmed

**Godot version:**
3.2.1

**OS/device including version:**
Arch Linux, up to date as of April 6th, 2020

**Issue description:**
`Directory`, and `File` classes fail to find directories, or files, using `dir_exists`, `file_exists` on exported projects.

**Steps to reproduce:**

Create Directory object, and attempt to check whether directory/file exists, note that it shows the file/directory exists when the project is run from the editor, but shows that the file/directory does not export when project is exported, and the resulting binary is run.

Note: `dir.open` does work with the same path, so it seems to be exclusive to how `dir_exists` work.

**Minimal reproduction project:**

[Sorry for the OneDrive link](https://1drv.ms/u/s!AlyWBEjLKwQ5hElu-2_zveAEJjdf?e=9W59nT)
There are similar issues (including [26009](https://github.com/godotengine/godot/issues/26009)), but was directed to create my own, so here it is.
Repository: pytorch
Issue: build Pytorch-1.5.0-rc1 from source fail
Labels: module: build,triaged

I am trying to build pytorch 1.5.0-rc1 from source and i am seeing this error.

Linking    libnccl.so.2.4.8                    > /sources/pytorch/build/nccl/lib/libnccl.so.2.4.8
Generating nccl.pc.in                          > /sources/pytorch/build/nccl/lib/pkgconfig/nccl.pc
Archiving  libnccl_static.a                    > /sources/pytorch/build/nccl/lib/libnccl_static.a
/sources/pytorch/third_party/nccl/nccl/src
[ 27%] No install step for 'nccl_external'
[ 27%] Completed 'nccl_external'
[ 27%] Built target nccl_external
gmake: *** [all] Error 2
Building wheel torch-1.5.0a0+bcd3f6d
-- Building version 1.5.0a0+bcd3f6d
cmake -DBUILD_PYTHON=True -DBUILD_TEST=True -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/sources/pytorch/torch -DCMAKE_PREFIX_PATH=/usr/local/conda/bin/../ -DNUMPY_INCLUDE_DIR=/usr/local/conda/lib/python3.6/site-packages/numpy/core/include -DPYTHON_EXECUTABLE=/usr/local/conda/bin/python -DPYTHON_INCLUDE_DIR=/usr/local/conda/include/python3.6m -DPYTHON_LIBRARY=/usr/local/conda/lib/libpython3.6m.so.1.0 -DTORCH_BUILD_VERSION=1.5.0a0+bcd3f6d -DUSE_NUMPY=True -DUSE_SYSTEM_NCCL=0 /sources/pytorch
cmake --build . --target install --config Release -- -j 48
Traceback (most recent call last):
  File "setup.py", line 745, in <module>
    build_deps()
  File "setup.py", line 316, in build_deps
    cmake=cmake)
  File "/sources/pytorch/tools/build_pytorch_libs.py", line 62, in build_caffe2
    cmake.build(my_env)
  File "/sources/pytorch/tools/setup_helpers/cmake.py", line 339, in build
    self.run(build_args, my_env)
  File "/sources/pytorch/tools/setup_helpers/cmake.py", line 141, in run
    check_call(command, cwd=self.build_dir, env=env)
  File "/usr/local/conda/lib/python3.6/subprocess.py", line 311, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'install', '--config', 'Release', '--', '-j', '48']' returned non-zero exit status 2.
The command '/bin/sh -c cd /sources && git clone --recursive --branch v1.5.0-rc1 --single-branch --depth 1 https://github.com/pytorch/pytorch.git && cd pytorch &&     source scl_source enable devtoolset-4 &&     export TORCH_CUDA_ARCH_LIST="3.5 5.2 6.0 6.1 7.0+PTX" &&     export CMAKE_PREFIX_PATH=${CONDA_PREFIX:-"$(dirname $(which conda))/../"} &&     USE_SYSTEM_NCCL=0 /usr/local/conda/bin/python setup.py bdist_wheel -d /tmp/pytorch_pkg &&     pip3 install -i https://pypi.sankuai.com/simple  /tmp/pytorch_pkg/*.whl     &&     rm -rf /sources/pytorch &&     rm -rf /tmp/pytorch_pkg && rm -rf /root/.cache/pip' returned a non-zero code: 1

The full log is in this link:
https://gist.github.com/522730312/1976c4793b83446f60a14eb9960cd7ac
Repository: TypeScript
Issue: tsserver protocol is missing notification message type. (maybe?)
Labels: Needs Investigation

While implementing a tsserver client, I found out not all request messages will reply with a response.
For example, the open request extends the `Request` interface. But it really notifies (as the documentation implies).
This was a bit confusing for me, because I understood that if I send an open request, I must wait for the response... but it never came.
https://github.com/microsoft/TypeScript/blob/a2609b1f1b58f9b6ef62cb3b6ff47efb35059eee/lib/protocol.d.ts#L1113-L1124

I understand that the interface documentation says the server will not send a response. I didn't read the full command documentation until now.
But maybe the documentation could be a bit more explicit about a kind of message where a response is not expected, for certain commands (maybe notify?).
Repository: go
Issue: os: permit Rename to read-only file on Windows
Labels: OS-Windows,NeedsInvestigation

On Windows 10, in Go 1.13, it used to be possible to rename over a read only file (like it is in Unix). In Go 1.14 it is not. I'm not seeing anything specific about this in the release notes, was this an intentional change?

```
func TestRenameRO(t *testing.T) {
	os.Remove("a")
	os.Remove("b")
	defer os.Remove("a")
	defer os.Remove("b")

	if err := ioutil.WriteFile("a", []byte("some data"), 0644); err != nil { // rw
		t.Fatal(err)
	}
	if err := ioutil.WriteFile("b", []byte("some data"), 0444); err != nil { // ro
		t.Fatal(err)
	}
	if err := os.Rename("a", "b"); err != nil {
		t.Error(err)
	}
}
```

```
PS C:\Users\JakobBorg\dev\test> go1.13.9 test
PASS
ok      _/C_/Users/JakobBorg/dev/test   0.048s
PS C:\Users\JakobBorg\dev\test> go1.14.1 test
--- FAIL: TestRenameRO (0.01s)
    rename_test.go:22: rename a b: Access is denied.
FAIL
exit status 1
FAIL    _/C_/Users/JakobBorg/dev/test   0.046s
PS C:\Users\JakobBorg\dev\test> 
```
Repository: opencv
Issue: Crash due to negative focal length in bundle adjustment
Labels: bug,category: stitching,needs investigation

##### System information (version)
- OpenCV => 4.2

##### Detailed description
I'm working with the stitching pipeline and sometimes happen that it crashes during the bundle adjustment process.
I found out that is an [old issue](https://github.com/opencv/opencv/issues/4322) but no one is assigned to resolve it.  
In the `BundleAdjusterRay::calcError(Mat &err)` function sometimes the focal lengths `f1` or `f2` become negative so `mult = sqrt(f1 * f2)` is `NaN` and it makes the program crash in a further call of SVD to a `NaN` matrix.
https://github.com/opencv/opencv/blob/cf2a3c8e7430cc92569dd7f114609f9377b12d9e/modules/stitching/src/motion_estimators.cpp#L553-L563

##### Steps to reproduce
I managed to reproduce this bug with the [stitching_detailed sample](https://github.com/opencv/opencv/blob/master/samples/cpp/stitching_detailed.cpp ) with the attached images.
Negative focal length occurs when the `edge` processed has fields `first = 0` and `second = 2`.


 
[crash.zip](https://github.com/opencv/opencv/files/4442933/crash.zip)


##### Issue submission checklist

 - [x] I report the issue, it's not a question
   <!--
   OpenCV team works with answers.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with question without real issue statement will be
   closed.
   -->
 - [x] I checked the problem with documentation, FAQ, open issues,
       answers.opencv.org, Stack Overflow, etc and have not found solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://answers.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [x] I updated to latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only latest release for each branch.
   The ticket is closed, if the problem is not reproduced with modern version.
   -->
 - [x] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as archite to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->
Repository: material-ui
Issue: [core] The hidden prop does not always visually hide elements
Labels: bug 🐛

Im using the `hidden` prop of `Container` to show only the current Tab and to hide the rest (copied from the Tabs example)
was working fine until i upgraded to version 4.9.9 from version 4.9.1 (could be higher version but i think 4.9.1)

- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Current Behavior 😯

<!-- Describe what happens instead of the expected behavior. -->
`<Container hidden={tabIndex != 1}> </Container>`

The Container is not hidden even though tabIndex = 1

## Expected Behavior 🤔
Container should not be visible

## Steps to Reproduce 🕹
`<Container hidden={tabIndex != 1}>sdfsdfsdfds</Container>`


https://codesandbox.io/s/empty-browser-n8fwh?fontsize=14&hidenavigation=1&theme=dark

* Works on 4.9.1 *

Steps:

1. upgrade to version 4.9.9
2. use a Container with hidden prop as True

| Tech        | Version |
| ----------- | ------- |
| Material-UI | v4.9.9  |
| React       | v16.12.0  |
| Chrome     |        |
Repository: godot
Issue: 2D CanvasModulate happens before light is applied, making light reset modulation
Labels: bug,topic:rendering,confirmed,topic:2d

Godot version: 3.2.1 stable

Issue description: When Canvas Modulate is applied to scene, but Light2D is also used in scene in "Mask" mode (To apply transparency to show player when he's behind some objects), modulation of sprite is reset when it  gets in Light texture range.

Minimal reproduction project:
[CanvasModulateBug.zip](https://github.com/godotengine/godot/files/4443722/CanvasModulateBug.zip)
Repository: TypeScript
Issue: Cannot assign to ... because it is a read-only property when using type guard in ctor
Labels: Bug,Help Wanted,PursuitFellowship

A common pattern is declaring narrower types for members in derived classes. However, when combined with type guards, assignement to readonly members fails with an unexpected "Cannot assign to ... because it is a read-only property" error. 

**TypeScript Version:**  3.7.2

**Search Terms:**
class member read-only property type narrowing covariant type guard

**Code**

```ts
class Foo {
    public readonly x: string | number;

    constructor() {
        if (isBar(this))
            // error TS2540: Cannot assign to 'x' because it is a read-only property.
            this.x = 'string';
        else
            // no error here
            this.x = 123;
    }
}

class Bar extends Foo {
    // Declare narrower type for member in derived class
    public readonly x: string;
}

function isBar(foo: Foo): foo is Bar {
    return foo instanceof Bar;
}
```

**Expected behavior:**

Assignment to this.x should be allowed with or without type guard in the constructor

**Actual behavior:**

error TS2540: Cannot assign to 'x' because it is a read-only property.
 
**Playground Link:** 

https://www.typescriptlang.org/play/?ssl=2&ssc=1&pln=22&pc=1#code/FAYwNghgzlAEBiB7RsDexadgBwK4CMwBLEWAJwFMIATRAOzAE9YAPALligBcyi6BzWAB9YdXAFt8FMgG5gGLCHrcyuEF0RkAFAEo0CrFiIAzWFqJQAQhG1cAFhZ06Dh1wHo3saWU2wAKgDKAEwArAAsAAwcAMIQdHSIXLDQUET8dLAasADkLNmwUiAQuFAUsERJFsnkVNQAtPRMOD7Y0lyMAHQurlj2Fh0ssAC8sACMQQDMcj2YFGCl3TMeoijevnbSFIs9fVADw2OT01gAvsBnoJAwsNZkXixcFHTUcEgo6IZ4hCQ1NI3M7E4PD4-DkF2MuDo6iI9HKVhsWmMyA4bx0HCRKCqt30hkoXFwZAyGPKdG4cRAFEQpluYOAQA

**Related Issues:**

It is as if the type guard creates an invisible alias (cf https://github.com/microsoft/TypeScript/issues/14241), and asignment inside the type guard fails.
Repository: vscode
Issue: Scrollbar doens't respond to touch screen dragging
Labels: feature-request,windows,editor-scrollbar

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version:
Version: 1.43.2 (system setup)
Commit: 0ba0ca52957102ca3527cf479571617f0de6ed50
Date: 2020-03-24T07:36:51.261Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT ia32 10.0.18363

Steps to Reproduce:

1. Touch and drag the scrollbar in the code editor
2. Nothing happens

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: pytorch
Issue: Inconsistent ProcessGroupMPI work data structure for send/recv and collectives
Labels: module: performance,oncall: distributed,triaged,better-engineering

In the current `ProcessGroupMPI` implementation, `send`/`recv`/`recvAnySource` returns a `shared_ptr` of `AsyncWork` to the application, which is the only reference to the `AsyncWork` data object. Hence, its lifetime of the `AsyncWork` item is dictated by the application. However, the `AsyncWork` contains the input tensor of the operation. If not deleted in time, it would unnecessarily consume memory even after the communication is done. This behavior is different from other collective communication APIs where a different `WorkEntry` object is added into a queue, and there is a separate thread processing works from the queue, meaning that the lifetime of the input tensors are controlled by ProcessGroupMPI itself. If there is no reason to keep these two implementations inconsistent, it would be better to consolidate them to have the same behavior. 

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar @VitalyFedyunin @ngimel