sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: KeyboardAvoidingView mistakingly adds white space on screen bottom after being untangled
Labels: Component: KeyboardAvoidingView,API: Keyboard,Needs: Attention

## [Description]
I wrapped a view as a footer inside KeyboardAvoidingView. It works properly before the keyboard has been untoggled. However, after the keyboard is untoggled, it adds a white space on the bottom of the screen. The height of the white space is as big as the keyboardVerticalOffset. This white space shouldn't exist.

## React Native version:
System:
    OS: macOS 10.15.6
    CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
    Memory: 28.43 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.18.1 - /usr/local/bin/node
    Yarn: Not Found
    npm: 6.14.5 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  Languages:
    Java: 14.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: ~16.11.0 => 16.11.0 
    react-native: https://github.com/expo/react-native/archive/sdk-38.0.1.tar.gz => 0.62.2 
  npmGlobalPackages:
    *react-native*: Not Found

## Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
1. Use KeyboardAvoidingView, set  keyboardVerticalOffset to any value
2. Put a view inside KeyboardAvoidingView, set the position as absolute, and set the bottom to 0

## Expected Results
The white space for keyboardVerticalOffset should only exist when the keyboard is toggled.

## Snack, code example, screenshot, or link to a repository:
```
<KeyboardAvoidingView
      behavior={Platform.OS == "ios" ? "padding" : "height"}
      keyboardVerticalOffset={48}
      style={{width: "100%",
                   height: "100%",
                   position: "absolute",
                   zIndex: 1,}}
>
      <View
              style={{width: "100%",
                            position: "absolute",
                            height: 56,
                            bottom: 0,}}
      >
              <SubmitButton/>
       </View>
</KeyboardAvoidingView>

```

![Artboard](https://user-images.githubusercontent.com/25261744/89864467-008daf80-db7a-11ea-9895-43ee449be351.png)
Repository: flutter
Issue: Simulate invokeMethod in MethodChannel from native to Flutter
Labels: a: tests,framework,c: proposal,P3,a: plugins,team-framework,triaged-framework

I'm developing a native plugin and trying to do unit tests. All unit tests will be done in Dart (No native code).

Flutter has a test example of how you can test call method channel from Dart to native using `setMockMethodCallHandler`.

The problem is I've not found the way to test method channel that calls from native to Dart that uses `setMethodCallHandler` to handle a call from native.

For example,
```
// main.dart

class Plugin {

  static MethodChannel _channel = const MethodChannel('plugin');
 
  Plugin() {
    _channel.setMethodCallHandler((call) async {
      print("called from native: ${call.method}");
    });
  }

}
```

```
// tests/main_test.dart

void main() {
  const MethodChannel _channel = MethodChannel('core.super_router');
  Plugin plugin;

  setUp(() async {
    TestWidgetsFlutterBinding.ensureInitialized();
    plugin = Plugin();
  });

  test("call from native", () async {
    _channel.invokeMethod("something");
    // This call can't reach the handler in the Plugin
  });
}
```

I'm purpose for method like so `_channel.simulateInvokeMethod("something");`
Repository: PowerToys
Issue: Integrate the "The Microsoft Keyboard Layout Creator" into Powertoys
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager

## 📝 Integrate the "The Microsoft Keyboard Layout Creator" into Powertoys

_The Microsoft Keyboard Layout Creator (MSKLC) extends the international functionality of Windows 2000, Windows XP and Windows Server 2003 systems_

_Would be nice to get this Microsoft application integrated into Powertoys, so it's supported in Windows 10.

https://support.microsoft.com/en-ph/help/823010/the-microsoft-keyboard-layout-creator
Repository: node
Issue: stream: remove destroy thenable duplication
Labels: stream

In https://github.com/nodejs/node/pull/34416 we introduced thenable support for some stream methods. However, this has lead to a lot of code duplication which will make it harder to maintain. We should clean it up at some point.

Opening this issue to keep track of this.
Repository: PowerToys
Issue: Run At Startup + Always Run As Administrator does not work if Admin User is different user
Labels: Product-Settings

## ℹ Computer information: Windows 10 1909 Build 18363.959

Following Problem:
I have two users, user1 and user1admin. user1 does not have admin rights on the maschine, user1admin does.

1. I am working as user1 - my windows boots as user1
2. I start Power Toys I can check Run At Startup 
3. But for Always Run as Administrator I have restart - it is greyed out.
4. I click restart and enter the credentials for user1admin.
5. PowerToys restarts now in admin mode (as user1admin process). 
6. I can set AlwysRunAs Administrator to true.
7. I can drag admin windows.

8. I restart the Maschine, now PowerToys has Always run as Administrator false and doesn't run as administrator.

Now why I belive what is the error:
When I check the settings.json:
C:\Users\user1\AppData\Local\Microsoft\PowerToys\settings.json 
"is_admin":false
C:\Users\user1admin\AppData\Local\Microsoft\PowerToys\settings.json 
"is_admin":true

Since I restarted as a differnt user (user1admin) the setting.json was just
updated for user1admin. But when I boot windows I am user1. And user1
has still is_admin: false.

Now my question is can you solve this? Or is there a solution for me?
I wanted to set the startup.exe to always run as user1admin but so far I did not find where 
the autostart is for power toys (registry?), just found this issue.:
https://github.com/microsoft/PowerToys/issues/5810

I would like to set that the autostart of powertoys is always executed as admin1user.
Maybe you can add a paragraph in the adminmode section.

- Windows build number: [run "winver"] Windows 10 1909 Build 18363.959
- PowerToys version:  20.0
- PowerToy module: Fancy Zones

Why is it like that: My company has a serious security concept as it should be. Our normal
users have no admin privileges. If I need admin privileges I need to start the application with my admin account.
Now I am a developer and if I want to debug a webpage I need to run visual studio in admin mode to allow the process
to register an url. This visual studio window then cannot be moved by Fancy Zones since it runs in admin mode.

Thank you very much
Greetings
Michael
Repository: react
Issue: DOM attribute stringification fixes
Labels: Type: Feature Request

This is regarding the discussion in #17773. 

React-DOM currently stringifies DOM attribute values  before passing them to `Element.setAttribute(NS)` functions. This might be unnecessary, as these functions implicitly stringify attribute values on their own (WebIDL attributes typed as `DOMString`). It also makes it difficult to enforce [Trusted Types](https://w3c.github.io/webappsec-trusted-types/dist/spec/) in React applications, as the trusted type objects would be stringified before values reach the DOM sinks.

Currently there is a `enableTrustedTypesIntegration` feature flag to disable stringification, but it seems like this behavior can be safely removed for modern browsers with no backwards-compatibility problems. Let me explain:

Attribute stringification was introduced in https://github.com/facebook/react/commit/b0455f46709fca94da0b6126b719d6dd07605e65, at that time to workaround a [**jsdom**](https://github.com/jsdom/jsdom) limitation (jsdom's DOM emulation didn't stringify on its own). **IE 8/9** [have a similar issue](https://github.com/facebook/react/commit/3b94abcb3b2c05fc38406b02a501427e58377c44). If an object is passed to a DOM attribute, its value becomes `[object]`, ignoring any stringification rules defined in objects' `toString` function.

- Jsdom does not have the issue anymore. Since at least 4.0.0 its `setAttribute` function does stringify the values via its IDL layer ([runkit demo](https://runkit.com/kkotowicz/jsdom-setattribute)).
- React doesn't support IE 8 anymore.
- The issue still exists for IE9 (contrary to https://github.com/facebook/react/issues/11735, my tests confirm that the bug still exists, but one needs to try a standard attribute, like `p.title`, and not one with a custom name).
- All other browsers, even in their old versions (I tested IEs, Firefox, Chrome, Safari, Opera and a few mobile browsers ) correctly stringify.

I propose to remove the stringification (similar to https://github.com/facebook/react/pull/17774) unless a browser bug is detected. 

That way there is no spurious stringification, and the code branches with the workaround can be removed once buggy browsers stop being supported. My testing shows that only IE9 is affected. The change would be backwards-compatible. I'll send a PR with the proposed change.
Repository: rust
Issue: Tracking Issue for pointer methods returning `MaybeUninit<T>`
Labels: C-tracking-issue,S-tracking-design-concerns

This is a tracking issue for methods on pointer types returning `MaybeUninit`: `as_uninit_ref/mut` and `as_uninit_slice(_mut)` on mutable and const raw pointers and `NonNull`.
The feature gate for the issue is `#![feature(ptr_as_uninit)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [ ] Merge Implementation (cc @rust-lang/T-libs, cc @RalfJung)
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions

- Currently, there is no unchecked non-null version for raw pointers without pointer casts. Either we want `as_uninit_ref_unchecked` or `Option::unwrap_unchecked`
- Should these operations on `NonNull` take `self`, `&self`, `&mut self`? Also see the discussion at https://github.com/rust-lang/rust/pull/96100.

### Implementation history

- Initial implementation: #75392
Repository: flutter
Issue: Material German translation of pasteButtonLabel is incorrect
Labels: framework,f: material design,a: internationalization,team-design,triaged-design

Copied from https://github.com/flutter/flutter/pull/63126, thanks for the report by @lazylazyllama:

After #63026 was merged, the German translation of `pasteButtonLabel` was changed from `EINFÜGEN` to `Einsetzen`, but I as a native German speaker can tell you that `Einsetzen` is a very weird translation and not common at all. It really should be `Einfügen`.

Native Android is also calling it `Einfügen`:

![image](https://user-images.githubusercontent.com/10547444/89579024-59d0a880-d833-11ea-9c56-7b27ae18be30.png)

On the other hand, Native iOS uses `Einsetzen` for its paste button label. 

The issue here is that Google's internal translation console treats both paste button labels as the same message, so the translation for both paste labels are identical. The change from EINFÜGEN to Einsetzen was created due to a request to match native iOS for the Cupertino widget, which unfortunately caused the native Android version to no longer match. Thus, the fix involves decoupling these translations so that they are independent of each other.
Repository: PowerToys
Issue: Animated Portable Network Graphics (APNG) Support in File Explorer
Labels: Idea-New PowerToy,Product-File Explorer

## 📝 Animated Portable Network Graphics (APNG) Support in File Explorer

_Expected Behavior:_

File Explorer should display a thumbnail and preview image for all animated PNG (.apng) files in a given directory. While the image is _NOT_ explicitly selected, File Explorer should initially display the .apng file as a static image (though still with full transparency support), just as an ordinary .png image. However, when the user mouses over the image, or selects it, File Explorer should display a short preview of the .apng animation, if any.

> NOTE: Displaying _animation previews_ for .apng images should be fully toggle-able (on|off) in PowerToys settings menu, in the event that they become too "busy" to the user, or they simply want to turn the functionality off.
---
More Info: [Wikipedia: Animated Portable Network Graphics (APNG)](https://en.wikipedia.org/wiki/APNG)

Sample animated PNG attached (*change **'.png'** extension to **'.apng'** to test functionality*) .

![Animated_PNG_example_bouncing_beach_ball](https://user-images.githubusercontent.com/5521397/89909328-f345e480-dbbc-11ea-9559-10757880ec3e.png)
---
If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: scrcpy
Issue: arm64
Labels: snap

I'm using scrcpy 1.12.1, it's on ubuntu arm64 repositorys
in snap it is armhf (32 bits) only.

I think snap could be simplest to add an updated arm64.
Repository: PowerToys
Issue: Add Preview for Adobe Illustrator Files (.ai)
Labels: Idea-New PowerToy,Product-File Explorer

## 📝 Provide a description of the new feature

_What is the expected behavior of the proposed feature?  What is the scenario this would be used?_
In Mac we can preview .ai files without opening Adobe Illustrator. Most of the designers would not have to open the files to see what art is inside the file.
---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
👍
Repository: flutter
Issue: Debugger lost connection soon  after ~35 sec  after iPhone is locked meanwhile xcode doesn't kill even after 2 minutes 
Labels: platform-ios,tool,a: debugging,has reproducible steps,P2,found in release: 3.7,found in release: 3.8,team-ios,triaged-ios

## Steps to Reproduce

1. Run the app on iOS physical device in debug mode using Android Studio (probably starting the app in run mode is the same)
2. Lock iPhone
3. Observe "lost connection" log in Android studio after a minute or sooner

## Comments

It's very hard to develop background processes of the app or test app behaviour when we return from background after some time if we are loosing connection to the device.

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

## Possible Linked issues

https://github.com/flutter/flutter/issues/45470

## Flutter Doctor

```
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.17.5, on Mac OS X 10.15.5 19F101, locale en-GB)
 
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
[✓] Android Studio (version 4.0)
[!] VS Code (version 1.47.3)
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

```

</details>
Repository: vscode
Issue: Add an api to determine runtime host environment (node, webworker)
Labels: feature-request,api,api-proposal,web

As we get closer to support running extensions in a webworker extension host, it would be valuable to have an API that extensions can use to reliably detect the runtime host.

```ts
export enum ExtensionRuntime {
    Node = 1,
    Webworker = 2
}

export interface ExtensionContext {
    readonly extensionRuntime: ExtensionRuntime;
}
```

Alternative naming: `ExtensionHost` or `ExtensionRuntimeHost`

Additionally it might be nice to expose a `when` context variable that would also expose this.
Repository: pytorch
Issue: prelu_backward, hardshrink_backward shouldn't be a method
Labels: triaged,module: dispatch

Currently, we have:

```
- func: prelu_backward(Tensor grad_output, Tensor self, Tensor weight) -> (Tensor, Tensor)
  use_c10_dispatcher: full
  variants: function, method
  dispatch: 
    CPU: prelu_backward_cpu
    CUDA: prelu_backward_cuda
```

This means we generate a `Tensor::prelu_backward` method. There is absolutely no reason we should have this method.
Repository: TypeScript
Issue: Suggestion: perform excess property checks when spreading an inline object literal
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.9.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
declare const someCondition: boolean;

type MyObject = { foo: number; bar?: number };

const a: MyObject = {
  foo: 1,
  bar: 2,
  // ✅ Error because `invalid` is an excess property
  invalid: 3,
};

const b: MyObject = {
  foo: 1,
  ...(someCondition
    ? {
        bar: 2,
        // ❌ `invalid` is an excess property, but we don't get an error here
        invalid: 3,
      }
    : {}),
};
```

In the example above, I only want to include specific properties when a condition is met. That's the only reason I'm using spread here.

I understand that TypeScript only performs excess property checks inside of object literals. Currently this does not include inline object literals which are being spread inside of another object literal.

In my experience this is a very common code pattern so it would be great if TypeScript handled this.

**Expected behavior:**

An error

**Actual behavior:**

No error

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: terminal
Issue: Allow display of HTML output by a console application to enable some nice graphical/interactive features.  
Labels: Area-VT,Area-Extensibility,Product-Terminal,Issue-Scenario

# Description of the new feature/enhancement

Continuing from https://github.com/microsoft/terminal/issues/5746#issuecomment-671601536

It would be fantastic if I could just pipe out HTML5 from my console app and have it display on the terminal.

# Proposed technical implementation details (optional)

I'm imagining some kind of escape sequence that enables/disables HTML chunk output or a file/pipe that could be written to/read from. The escape sequence would determine the dimensions/container types. This sequence could be output by any app even running remote but for I am mainly considering locally running command-line apps. An app could interrogate the environment vars to determine if the HTML rendering option was available. 

HTML output could be rendered within the following container types.

- An inline WebView that is scrolled along and put to sleep off-screen? Gets turned into an image when the parent app closes?  I could imaging starting an app that outputs some HTML/JS that opens a WebSocket back to the parent app with all sorts of possibilities.  Live graphs, buttons etc.   
- A popup window? 
- An underlay that takes up the entire terminal window. such that content is rendered under the terminal text.
- An overlay that takes up the entire terminal window. such that content is rendered over the terminal text?  

These last two could be used for backgrounds, Persistent graphs, VStatus widgets, Controls. etc. 

It would change the terminal into a graphical environment based on HTML/CSS/SVG/JS. I suspect it would have rapid and enthusiastic adoption by developers. Could be awful. Could be amazing.
Repository: pytorch
Issue: TensorOptions extensibility has rusted shut
Labels: triaged,module: codegen

One of the original motivations for introducing TensorOptions was to make it easier to add new parameters to factory functions, should the need arise, without having to modify all function signatures; it'd just be a new field in TensorOptions. Furthermore, as TensorOptions were always kwarg-only arguments on Python side, there wouldn't be any BC implications for changes like this.

With the current status quo of mobile serialization that is position dependent, we no longer can rely on an argument being kwarg-only; position matters, no matter what.  However, this doesn't necessarily imply that we can't add new parameters to TensorOptions; if the newly added parameters are defaulted, the new definitions are "roughly" backwards compatible.

However, we also now have native functions which add new kwargs AFTER the tensor options kwargs:

```
- func: empty.memory_format(int[] size, *, ScalarType? dtype=None, Layout? layout=None, Device? device=None, bool? pin_memory=None, MemoryFormat? memory_format=None) -> Tensor
```

For these functions, TensorOptions extensibility is no longer a thing. TensorOptions parameters should live in a contiguous segment `ScalarType? dtype=None, Layout? layout=None, Device? device=None, bool? pin_memory=None`. But to insert a new parameter between `pin_memory` and `memory_format` is BC-breaking as it changes the positional order of arguments. So we have no way to add new arguments now, at least until we have a solid plan for treating kwargs on mobile as not positional. :(

Note: Can we just add the new argument at the very end of the argument list? Maybe. It would be pretty strange though: when you translate back into the TensorOptions version of the code, arguably you should delete the new argument from the argument list; so now you are in the weird situation where `pin_memory` is not the last argument in schema, but it is the last argument in C++ API.
Repository: flutter
Issue: ide_templates hardcode Android SDK version instead of using `{{androidSdkVersion}}`
Labels: platform-android,tool,P2,team-android,triaged-android

See
https://github.com/flutter/flutter/blob/75b737ff695afba5ec8b4e313c130c520b3651fb/packages/flutter_tools/ide_templates/intellij/examples/platform_channel/android.iml.copy.tmpl#L8
versus
https://github.com/flutter/flutter/blob/ff25edd3ad38d8845df1e3905f193da7d9004d00/packages/flutter_tools/templates/app/android-kotlin.tmpl/projectName_android.iml.tmpl#L24