sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: stable-diffusion-webui
Issue: [Bug]: inpanting model 2.0 add in the end stages latend nothing 
Labels: bug-report

### Is there an existing issue for this?

- [x] I have searched the existing issues and checked the recent builds/commits

### What happened?

os windows 
browser chrome 
runing https://github.com/TheLastBen/fast-stable-diffusion

the new 2.0 model gives in the inpanted areas returns latend nothig with faint image

### Steps to reproduce the problem

1. get inpanting model https://huggingface.co/stabilityai/stable-diffusion-2-inpainting
2. put in the model folder for image generating from text 
3. inpaint a part of a image put a promt 
4. generare


### What should have happened?

the inpainting result should be less like latend nothing

### Commit where the problem happens

https://github.com/TheLastBen/fast-stable-diffusion

### What platforms do you use to access UI ?

Other/Cloud

### What browsers do you use to access the UI ?

Google Chrome

### Command Line Arguments

_No response_

### Additional information, context and logs

![grid-0068](https://user-images.githubusercontent.com/106181044/210623628-e512e94c-f530-449c-b368-82f613023902.png)
![grid-0067](https://user-images.githubusercontent.com/106181044/210623634-e5a03a08-da23-45de-b698-c9619db380af.png)
![grid-0066](https://user-images.githubusercontent.com/106181044/210623641-3b9b8043-7cd6-453f-bc7d-126bd3c35cd4.png)
![grid-0065](https://user-images.githubusercontent.com/106181044/210623647-9f7c11ab-25f0-4c10-877a-cc2811de481d.png)
![00391-2772040429-landscape 8k ,hi resolution ,profesional foto](https://user-images.githubusercontent.com/106181044/210623652-7bddc316-8955-4f57-9fc4-2a6fae1d82c9.png)
![grid-0012 (1)](https://user-images.githubusercontent.com/106181044/210623653-bf55ba10-49a8-488a-8c61-2e63fab858ce.png)
![grid-0001 (1)](https://user-images.githubusercontent.com/106181044/210623657-29fe280b-16eb-43f4-a689-976e6a8c524c.png)
Repository: pytorch
Issue: linspace (and arange) behaves differently on GPU and CPU
Labels: triaged

### 🐛 Describe the bug

There seems to be numerical inconsistencies when `torch.linspace` is run on GPU vs on CPU, especially when the step size isn't an integer. This difference becomes more obvious when other operations are performed downstream, such as sine and cosine.

The following example can also be reproduced on Google Colab's GPU runtime.

```python
import numpy as np
import torch
from matplotlib import pyplot as plt

n = 200
start, end = -100, 100
device = "cuda"
a = torch.linspace(start, end, steps=n).to(device="cuda")
b = torch.linspace(start, end, steps=n, device="cuda")
print(torch.allclose(a, b))                 # this is True, as expected
print(torch.allclose(a.sin(), b.sin()))     # this is False, the error becomes non-negligible

# plot error against array index
plt.scatter(np.arange(n), (a - b).cpu().numpy())
plt.show()
```

The same issue also exists for `torch.arange`:

```python
import numpy as np
import torch
from matplotlib import pyplot as plt

start, end = -100, 100
step_size = np.random.rand() * 10
device = "cuda"

c = torch.arange(start, end, step=step_size).to(device="cuda")
d = torch.arange(start, end, step=step_size, device="cuda")
print(torch.allclose(c, d))                 # this is mostly True, as expected
print(torch.allclose(c.sin(), d.sin()))     # this is False, the error becomes non-negligible

# plot error against array index
plt.scatter(np.arange(len(c)), (c - d).cpu().numpy())
plt.show()
```

### Versions

Collecting environment information...
PyTorch version: 1.13.0+cu116
Is debug build: False
CUDA used to build PyTorch: 11.6
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.6 LTS (x86_64)
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Clang version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
CMake version: version 3.22.6
Libc version: glibc-2.27

Python version: 3.8.16 (default, Dec  7 2022, 01:12:13)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.10.133+-x86_64-with-glibc2.27
Is CUDA available: True
CUDA runtime version: 11.2.152
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: Tesla T4
Nvidia driver version: 460.32.03
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.1.1
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.21.6
[pip3] torch==1.13.0+cu116
[pip3] torchaudio==0.13.0+cu116
[pip3] torchsummary==1.5.1
[pip3] torchtext==0.14.0
[pip3] torchvision==0.14.0+cu116
[conda] Could not collect
Repository: electron
Issue: [Bug]: Serial Port `device` in `setDevicePermissionHandler` Uses Snake Case
Labels: bug :beetle:,status/confirmed,has-repro-gist,main,19-x-y,22-x-y,23-x-y,component/deviceAccess

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

22.0.0

### What operating system are you using?

macOS

### Operating System Version

macOS 12.6.1

### What arch are you using?

x64

### Last Known Working Electron version

Never

### Expected Behavior

Expect `details.device` for `ses.setDevicePermissionHandler` to use key names which match [`SerialPort`](https://www.electronjs.org/docs/latest/api/structures/serial-port) when `details.deviceType === 'serial'`, as documented. They keys should be camelCase.

### Actual Behavior

They keys are snake_case, refs https://github.com/electron/electron/blob/700f43c90c714fbf0b91458288b88bc18eed7cb0/shell/browser/serial/serial_chooser_context.cc#L26-L35

### Testcase Gist URL

https://gist.github.com/7cc6bef84a28426c1134344dcab2cb29

### Additional Information

The testcase will exit with exit code 0 when the keys are camelCase, 1 when the keys are snake_case, 2 if it's neither, and will timeout after 5 seconds and exit with exit code 3 if there are no serial ports present on the machine running the testcase.
Repository: Web-Dev-For-Beginners
Issue: Missing step for initializing a repository
Labels: no-issue-activity

**Describe the bug**
[Lesson 02 - GitHub Basics](https://github.com/microsoft/Web-Dev-For-Beginners/tree/main/1-getting-started-lessons/2-github-basics) does not include initializing main branch with command `git branch -M main`. Gives error on push command because there is no branch to to push to. 

**To Reproduce**
Steps to reproduce the behavior:
1. Go to [GitHub Basics](https://github.com/microsoft/Web-Dev-For-Beginners/tree/main/1-getting-started-lessons/2-github-basics)
2. Follow steps up to number 11 with `git push -u origin main`
3. See error - `error: failed to push some refs to 'https://github.com/organization/example.git'`

**Expected behavior**
Expected to push put to new repository without errors. 

**Screenshots**
![image](https://user-images.githubusercontent.com/52934303/210633949-643241c0-fe99-4339-b26e-6b7a7b95aab6.png)

**Desktop (please complete the following information):**
 - OS: Windows 10
 - Browser: Chrome

**Additional context**
Add any other context about the problem here.
Repository: excalidraw
Issue: export `<LanguageList/>`
Labels: package:excalidraw

At some point we should export our `<LanguageList/>` component, though we need to figure out how to handle state, first.

Perhaps it should be part of a language package, including hooks for retrieving the lang state, and handling automatic language detection.
Repository: godot
Issue: Godot closes after clicking "Windows Show Desktop" Button
Labels: bug,topic:editor,needs testing,crash

### Godot version

3.5.1

### System information

Windows (GLES 2.0)

### Issue description

When I'm working on Godot and wants to click "Show Desktop", the engine just closes itself
![image](https://user-images.githubusercontent.com/103614257/210642975-0b30e3d6-ab47-4189-878a-0625e995c223.png)


### Steps to reproduce

N/A

### Minimal reproduction project

N/A
Repository: godot
Issue: Global shader uniform color not equal to regular uniform color.
Labels: discussion,topic:shaders

### Godot version

4.0.beta10

### System information

Windows 10 Vulkan

### Issue description

![image](https://user-images.githubusercontent.com/33663275/210646946-1662cc3e-9544-4c5a-901f-535d82bdeba3.png)
The shader global color (top left) is the same hex code as the shader uniform (bottom right). But If i create an unshaded sphere, and show the colors next to each other, the shader global color is slightly lighter than the shader uniform color. 

![image](https://user-images.githubusercontent.com/33663275/210647273-12400c5f-42a9-4039-a51b-7a5b8e9e71e6.png)

I thought maybe it's because of my shader code, so I reduced it to as simple as possible.

![image](https://user-images.githubusercontent.com/33663275/210648444-47723539-0689-43a4-9041-7ba1511e93c0.png)
![image](https://user-images.githubusercontent.com/33663275/210648464-c0d1b65d-2590-4fd7-a33e-e8caa32f88e2.png)



### Steps to reproduce

Create an empty project.
Add a new shader global color.

Create a new shader material.
Set rendermode to unshaded.
Set the ALBEDO to the shader global color

Create an exact replica of this shader, but set the albedo to a regular shader uniform color.

Make sure both colors have the exacts same hex code.

### Minimal reproduction project

[test2.zip](https://github.com/godotengine/godot/files/10347429/test2.zip)
Repository: go
Issue: go/printer: TestFiles failures with `running too slowly`
Labels: Testing,NeedsInvestigation

```
#!watchflakes
post <- pkg == "go/printer" && test == "TestFiles" && `running too slowly`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/c8cc040eea80706976967870d22eeda76c3a5e8b)):

    --- FAIL: TestFiles (0.00s)
        --- FAIL: TestFiles/empty.input (10.01s)
            printer_test.go:160: testdata/empty.input: running too slowly


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: net/http: TestServerCancelsReadTimeoutWhenIdle failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net/http" && test == "TestServerCancelsReadTimeoutWhenIdle" && `failed with duration`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/7842a9473ba6191bd921d493c4008b475fac3801)):

    --- FAIL: TestServerCancelsReadTimeoutWhenIdle (0.00s)
        --- FAIL: TestServerCancelsReadTimeoutWhenIdle/h2 (4.61s)
            clientserver_test.go:210: server log: http: TLS handshake error from 127.0.0.1:50635: read tcp 127.0.0.1:50636->127.0.0.1:50635: i/o timeout
            clientserver_test.go:210: server log: http: TLS handshake error from 127.0.0.1:50633: write tcp 127.0.0.1:50634->127.0.0.1:50633: i/o timeout
            clientserver_test.go:210: server log: http: TLS handshake error from 127.0.0.1:50619: write tcp 127.0.0.1:50620->127.0.0.1:50619: i/o timeout
            clientserver_test.go:210: server log: http: TLS handshake error from 127.0.0.1:50617: write tcp 127.0.0.1:50618->127.0.0.1:50617: i/o timeout
            clientserver_test.go:210: server log: http: TLS handshake error from 127.0.0.1:50610: read tcp 127.0.0.1:50611->127.0.0.1:50610: i/o timeout
            serve_test.go:5853: failed with duration 2s: Get: Get "https://127.0.0.1:50611": unexpected EOF


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: net/http: TestContentTypeWithVariousSources failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net/http" && test == "TestContentTypeWithVariousSources" && `timeout waiting for .* frames`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/330e2b93acb579c15dd63634e692f18842e9bb67)):

    --- FAIL: TestContentTypeWithVariousSources (0.00s)
        --- FAIL: TestContentTypeWithVariousSources/h2 (5.52s)
            --- FAIL: TestContentTypeWithVariousSources/h2/write_one_byte_at_a_time (3.25s)
                clientserver_test.go:210: server log: timeout waiting for SETTINGS frames from 127.0.0.1:61917
                sniff_test.go:236: Get: Get "https://127.0.0.1:61916": unexpected EOF


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: internal/types/errors: TestErrorCodeExamples failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "internal/types/errors" && test == "TestErrorCodeExamples"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/4d48930fc298da2b0f4d22f0278cae64ba3ff28e)):

    panic: test timed out after 30m0s
    running tests:
    	TestErrorCodeExamples (30m0s)
    	TestErrorCodeExamples/UnexportedName (29m59s)
    
    runtime.gopark(0x4000166000?, 0x0?, 0xb8?, 0x5c?, 0x1bc9c?)
    	/var/gobuilder/buildlet/go/src/runtime/proc.go:381 +0xe0 fp=0x4000205c30 sp=0x4000205c10 pc=0x457b0
    runtime.chanrecv(0x400015c000, 0x4000205d3f, 0x1)
    	/var/gobuilder/buildlet/go/src/runtime/chan.go:583 +0x468 fp=0x4000205cc0 sp=0x4000205c30 pc=0x153b8
    runtime.chanrecv1(0x401660?, 0x21a380?)
    	/var/gobuilder/buildlet/go/src/runtime/chan.go:442 +0x14 fp=0x4000205cf0 sp=0x4000205cc0 pc=0x14f44
    testing.(*T).Run(0x4000003a00, {0x4000015600?, 0x40000c5de8?}, 0x4000150000)
    	/var/gobuilder/buildlet/go/src/testing/testing.go:1629 +0x384 fp=0x4000205db0 sp=0x4000205cf0 pc=0xd37c4
    internal/types/errors_test.TestErrorCodeExamples.func1({0x4000015600, 0xe}, 0x4a, 0x40000d0d70)
    	/var/gobuilder/buildlet/go/src/internal/types/errors/codes_test.go:26 +0xbc fp=0x4000205df0 sp=0x4000205db0 pc=0x1f07cc
    internal/types/errors_test.walkCodes(0x4000003a00, 0x4000205f48)
    	/var/gobuilder/buildlet/go/src/internal/types/errors/codes_test.go:81 +0x49c fp=0x4000205f30 sp=0x4000205df0 pc=0x1f0f7c
    internal/types/errors_test.TestErrorCodeExamples(0x4000003a00)
    	/var/gobuilder/buildlet/go/src/internal/types/errors/codes_test.go:25 +0x4c fp=0x4000205f60 sp=0x4000205f30 pc=0x1f06ec
    testing.tRunner(0x4000003a00, 0x278428)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: react-native
Issue: iOS Accessibility Value Out of Sync
Labels: Platform: iOS,Needs: Triage :mag:

### Description

On iOS it seems that after an accessibility action is triggered the value of accessibility value is read an arbitrary amount of time later. This can lead to VoiceOver reading the previous value again rather than the new value.

This means that sometimes the value will be read correctly, depending on how quickly react native renders the updated accessibility action.

However in my moderately complex RN project I was unable to reliably get everything rendering quickly enough. Even when Flipper said the component in question was rendering in a few ms the bug would still sometimes occur (about 1 in 20 actions).

Note: On Android, TalkBack waits any length of time before reading the updated value. Even an artificial of delay of 500ms will still be read correctly.

### Version

0.68.5

### Output of `npx react-native info`

System:
    OS: macOS 12.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 37.62 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
    Watchman: 2022.06.06.00 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK:
      API Levels: 30, 31
      Build Tools: 30.0.2, 31.0.0, 33.0.1
      System Images: android-24 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom, android-31 | Google APIs Intel x86 Atom_64, android-31 | Google Play Intel x86 Atom_64
      Android NDK: Not Found
  IDEs:
    Android Studio: 2021.3 AI-213.7172.25.2113.9123335
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 18.0.1 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2 
    react-native: 0.68.5 => 0.68.5 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

### Steps to reproduce

Accessible components with the following properties:

- `accessibleRole`="adjustable"
- `accessibilityActions` for increment and decrement
- `accessibilityValue` with text property set

In an app where the component is not guaranteed to render quickly enough.

Running with VoiceOver on iOS (Reading speed didn't seem to change the issue)

### Snack, code example, screenshot, or link to a repository

https://snack.expo.dev/@scarlin/ios-accessibility-value-bug-demo
Repository: go
Issue: net/http: TestMaxBytesHandler failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net/http" && ((test == "TestMaxBytesHandler" && `expected echo`) || (log ~ `panic: test timed out` && log ~ `TestMaxBytesHandler \(\d+m\d+s\)`))
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/bafa0610f5ad1e352f75b26117f386539351c7ea)):

    2022/12/28 09:45:59 httptest.Server blocked in Close after 5 seconds, waiting for connections:
      *net.TCPConn 0xc000014098 127.0.0.1:50424 in state active
    2022/12/28 09:45:59 httptest.Server blocked in Close after 5 seconds, waiting for connections:
      *net.TCPConn 0xc00054a030 127.0.0.1:50422 in state active
    --- FAIL: TestMaxBytesHandler (3.42s)
        --- FAIL: TestMaxBytesHandler/max_size_100_request_size_1000000 (2.33s)
            serve_test.go:6703: unexpected connection error: Post "http://127.0.0.1:50578": readfrom tcp 127.0.0.1:50579->127.0.0.1:50578: write tcp 127.0.0.1:50579->127.0.0.1:50578: write: connection reset by peer
            serve_test.go:6726: expected echo of size 100; got 0


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: neovim
Issue: editorconfig: insert_final_newline=false actively sets 'fixendofline', 'endofline'
Labels: status:blocked-external,plugin

### Neovim version (nvim -v)

NVIM v0.9.0-dev-613+gef18c9f9b

### Vim (not Nvim) behaves the same?
No it does the opposite. It does not change the last line in the file.
VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Aug 23 2022 20:18:58)

### Operating system/version

Ubuntu 22.10

### Terminal name/version

xfce4

### $TERM environment variable

xterm-256color

### Installation

Appimage

### How to reproduce the issue

Create an `.editorconfig` file with the contents

```bash
[*]
insert_final_newline = false
```

Open a file and save it. I use `vim-gitgutter` that tells me that the last line has been changed when I open the file.


![image](https://user-images.githubusercontent.com/1689020/210649972-2540e401-80d4-49f3-ae38-e34bf26d9067.png)

![image](https://user-images.githubusercontent.com/1689020/210652985-3cf955eb-fa43-4bec-bc23-29e2870721d3.png)


### Expected behavior

Do not change the last line of the file?
It did not change the last line in neovim 0.6

### Actual behavior

It changes the last line of the file, in every file it opens.

In my last neovim version (0.6) this did not happen.
This also does not happen in vim.

If I remove the `.editorconfig` file, the files are not changed.
Repository: node
Issue: Uncaught exception in socket code: "Cannot read properties of null (reading 'finishWrite')"
Labels: tls,http2

### Version

v18.4.0

### Platform

Linux i-00f751a18edbe3eb6.us-west-2.compute.internal 5.15.73-45.135.amzn2022.x86_64 #1 SMP Fri Oct 14 17:47:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

### Subsystem

http2 (maybe actually net or tls)

### What steps will reproduce the bug?

Apologies that I don't have an easy repro case yet. It's one of those "run my server for a while and then it does this." Near as I can tell, it's along these lines:

1. Connection accepted to an `Http2Server` (via TLS socket).
2. Session established.
3. Session remains idle for five minutes. (No requests ever made.)
4. My code notices the idleness and calls `close()` on the session. (Tick/turn concludes.)
5. Boom! Uncaught exception: `TypeError: Cannot read properties of null (reading 'finishWrite')`

When I get a chance (hopefully soon) I will try to distill down a real example. Thanks for any help you can offer in the meantime.

### How often does it reproduce? Is there a required condition?

Unclear. This shows up about once a day on my not-very-active server. It _does_ correspond one-to-one with a call to `session.close()`. That is, every time my server does this right now, this uncaught exception seems to follow.

### What is the expected behavior?

No uncaught exception. That is, either no exception at all, or an exception that can be safely caught and handled without shutting the system down.

### What do you see instead?

This uncaught exception:

```
TypeError: Cannot read properties of null (reading 'finishWrite')
    at JSStreamSocket.finishWrite (node:internal/js_stream_socket:211:12)
    at Immediate.<anonymous> (node:internal/js_stream_socket:196:14)
    at process.processImmediate (node:internal/timers:471:21)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)
```

### Additional information

This is the actual code which sets up the timeout. The timeout time is 5 minutes, and the `logger...` call simply writes a structured log line.

```js
    session.setTimeout(Http2Wrangler.#SESSION_TIMEOUT_MSEC, () => {
      logger?.idleTimeout();
      session.close();
    });
```

`Http2Session.close()` _does_ accept an optional callback, which is documented as being bound to the `close` event. However, this code _already_ binds a handler to `close` (which does not seem to be getting called before the uncaught exception is generated).
Repository: vscode
Issue: Live Share notebook serializer not being called when opening a notebook file on guest
Labels: under-discussion,notebook,notebook-liveshare

- VS Code Version: 1.74.2
- OS Version: Windows 11

Steps to Reproduce:

1. Open a folder with .ipynb file in VS code and open the notebook file in editor
2. Start live share session and join the session in another VS code instance
3. On the guest, see the error "Co-editing is not supported for notebooks opened with non-shared views."
(If the notebook file does not automatically open on guest, select some text in the notebook file on the host)

The error shows up as the notebook serializer that Live Share registered as guest is not being selected and it breaks coediting in notebook. 
How can force Live Share serializer to be selected during a live share session?
Adding @lyup and @mattbierner .
Repository: flutter
Issue: use flatland's infinite hit region for input shield
Labels: engine,platform-fuchsia,c: proposal,P2,team-engine,triaged-engine

Flatland API has a new infinite hit region method call. Use that for Fuchsia view's input interceptor.