sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: bytes, strings: should have minimal dependency on unicode
Labels: Performance,NeedsInvestigation

Importing "unicode" immediately bloats a binary by ~100k. This is unfortunately unavoidable since the `unicode.Categories` map contains a reference to every Unicode category in existence (see #7600 or #2559).

We should make it such that only referencing `bytes` functions (e.g., `bytes.HasPrefix`) that do not depend on `unicode` should not result in `unicode` being linked into the binary.

Here's a list of functions that depend on `unicode`:
* `Fields` -> `unicode.IsSpace`
* `ToUpper` -> `unicode.ToUpper`
* `ToLower` -> `unicode.ToLower`
* `ToTitle` -> `unicode.ToTitle`
* `ToUpperSpecial` -> `unicode.SpecialCase`
* `ToLowerSpecial` -> `unicode.SpecialCase`
* `ToTitleSpecial` -> `unicode.SpecialCase`
* `Title` -> `unicode.{ToTitle,IsLetter,IsDigit,IsSpace}`
* `TrimSpace` -> `unicode.IsSpace`
* `EqualFold` -> `unicode.SimpleFold`

Of all of these, only `Fields` and `TrimSpace` are used to any significant degree. Even still, the implementation of `unicode.IsSpace` is fairly small and [references a relatively small table](https://github.com/golang/go/blob/462b78fe7027ef0d2e2b40c3cfd1f5a37d307310/src/unicode/tables.go#L6875-L6886).

Perhaps we should create a `internal/unicodetables` package that contains every table. The `unicode` package can depend on `unicodetables`, and other stdlib packages can depend on `unicodetables` directly.
Repository: flutter
Issue: Support PlatformViews on Windows using DirectComposition
Labels: c: new feature,engine,platform-windows,a: platform-views,a: desktop,P2,team-windows,triaged-windows

## High-level Overview

DirectComposition on Windows enables applications to interface with DWM to composite visuals from various sources (HWNDs, MediaFoundation sources, DXGI swapchains). By delegating this to DWM, it may utilize hardware overlay/underlay planes which eliminates the need to use the GPU to present video content or camera feeds. This is beneficial for power usage and performance on Windows laptops.

In a test application, using DirectComposition to present a USB Webcam's feed to the screen completely eliminated the need to convert the incoming NV12 video frames to RGB8 on the GPU, preventing a passively-cooled SurfaceBook 3 from thermal throttling.

## Use case

Flutter applications would like a way to present a platform-provided HWND, or more generally a [IDCompositionVisual](https://docs.microsoft.com/en-us/windows/win32/api/dcomp/nn-dcomp-idcompositionvisual) inside a Flutter widget tree.

## Proposal

### Presentation

Most Flutter applications & plugins may utilize an invisible child window (hidden via `DWMWA_CLOAK`, see [DwmSetWindowAttribute](https://docs.microsoft.com/en-us/windows/win32/api/dwmapi/nf-dwmapi-dwmsetwindowattribute)) with [IDCompositionDevice::CreateSurfaceFromHwnd](https://docs.microsoft.com/en-us/windows/win32/api/dcomp/nf-dcomp-idcompositiondevice-createsurfacefromhwnd) to embed a child window inside of Flutter. Since this is the most common case, Flutter should directly provide an API to wrap all the necessary surface and visual creation.

For some advanced usecases, one can instead pass an `IDCompositionVisual` directly. For example, video & webcam playback via MediaFoundation, or embedding a DirectX or Vulkan application using a DXGI swapchain.

### Input

Because `IDCompositionVisual` does not traditionally deal with input (with some exceptions for mouse drag & mouse wheel), Flutter needs a way to delegate mouse, touch, and keyboard input back to the application.

For an HWND passed directly to Flutter, Flutter can manage dispatching these messages to the specified window.

For a `IDCompositionVisual`, there needs to be some sort of delegate with callbacks.

### Accessibility

For an HWND passed directly to Flutter, Flutter can add the child window's IAccessible to the hierarchy using [AccessibleObjectFromWindow](https://docs.microsoft.com/en-us/windows/win32/api/oleacc/nf-oleacc-accessibleobjectfromwindow). It may already be included, depending on the relationship between the HWND passed into Flutter.

For a `IDCompositionVisual`, it should have a way of producing an `IAccessible` for inclusion in the parent.

### Windows 7 Support?

I'm unsure what version of Windows is the current minimally supported version by Flutter. DirectComposition is supported on Windows 8 and above. If Windows 7 is a supported target, using DirectComposition for PlatformViews may be an issue.
Repository: pytorch
Issue: masked_scatter_ is very lacking
Labels: module: docs,triaged,module: scatter & gather ops

### 📚 The doc issue

The documentation for `masked_scatter_` says

```
Tensor.masked_scatter_(mask, source):
Copies elements from source into self tensor at positions where the mask is True. 
```

Which suggests it might work similar to

```
tensor[mask] = source[mask]
```

however, the actual semantics are quite different, which leads to confusion as evidenced here: https://stackoverflow.com/questions/68675160/torch-masked-scatter-result-did-not-meet-expectations/73145411#73145411

### Suggest a potential alternative/fix

The docs should specify that the way scatter works is that the `i`th `True` in a row is given the `i`th value from the source. So not the value corresponding to the position of the `True`.
Maybe an example of the difference between the two methods described in the issue.


cc @svekars @holly1238 @mikaylagawarecki
Repository: rust
Issue: doctests show a full stack trace of the panic despite `RUST_BACKTRACE` not being set
Labels: T-rustdoc,A-doctests

at least since yesterday, when i get a panic in a doc test it shows a full backtrace of the panic. Over a page long, full of the old-style useless stack frames info, not the newer info that's usually nicer by cutting out the stuff burred inside the standard library.

however, *normal* tests using the `#[test]` attribute give the expected output of just saying "FAILED" and then printing the panic message (no stack trace) after all the test results.
```
rustc 1.64.0-nightly (4d6d601c8 2022-07-26)
```
Repository: go
Issue: crypto/tls: RFC 9266: Channel Bindings for TLS 1.3 support
Labels: NeedsInvestigation,FeatureRequest

Can you add the support of RFC 9266: Channel Bindings for TLS 1.3?
- https://datatracker.ietf.org/doc/html/rfc9266

Channel Bindings for TLS: https://datatracker.ietf.org/doc/html/rfc5929

- XEP-0388: Extensible SASL Profile: https://xmpp.org/extensions/xep-0388.html
- XEP-0440: SASL Channel-Binding Type Capability: https://xmpp.org/extensions/xep-0440.html
- XEP-0474: SASL SCRAM Downgrade Protection: https://xmpp.org/extensions/xep-0474.html
- XEP-0480: SASL Upgrade Tasks: https://xmpp.org/extensions/xep-0480.html

Little details, to know easily:
- tls-unique for TLS =< 1.2
- tls-server-end-point
- tls-exporter for TLS = 1.3

Thanks in advance.
Repository: flutter
Issue: ShellIOManager::CreateCompatibleResourceLoadingContext must be moved to shell/gpu
Labels: engine,P2,c: tech-debt,team-engine,triaged-engine

This only makes sense in the OpenGL backend. But, since it is in common code, the `SHELL_ENABLE_FOO` macros cannot be used.
Repository: flutter
Issue: [Proposal] InteractiveViewer should let apps override gestures by reporting pointer events
Labels: c: new feature,framework,customer: google,c: proposal,P3,team-framework,triaged-framework

`InteractiveViewer` scales its content up/down based on a user's pinch gesture.

I'm working on a drawing app where I'm using `InteractiveViewer` as the container for canvases. We have a lasso tool, which selects portions of a drawing. When the user pinches within the lasso bounds, we want to scale the selected content. When the user pinches outside the lasso bounds, we want to scale/zoom all content, like normal.

We can't implement the lasso resizing because we can't conditionally prevent `InteractiveViewer` scaling. 

One might suggest passing `false` for `scaleEnabled` to prevent `InteractiveViewer` from scaling its content. However, we don't know which scaling mode we need until the user starts to pinch. We need to check the location of the user's fingers before we decide whether we want `InteractiveViewer` to handle the scaling, or if we want to intercept the gesture and handle it ourselves.

On a similar note, `InteractiveViewer` should report the pointer locations for its gesture. Instead, all we get is a focal point: https://api.flutter.dev/flutter/gestures/ScaleStartDetails-class.html
Repository: node
Issue: Tracking issue: support of builtins and V8 issues in run-time user-land snapshots
Labels: snapshot

This issue is opened to track known bugs and limitations of the run-time user-land snapshot.

Currently known limitations/bugs in Node.js builtins:

- [ ] Support modules that generate system requests e.g. net, http (without supporting the snapshotting of those requests, which we can't resurrect. But user should be able to snapshot the application after all pending requests are completed).
- [ ] Certain global event listeners on the `process` object need to be removed during snapshot serialization, and re-installed during deserialization
- [ ] Support user-land modules
- [x] Integration with SEA (Single Executable Application): https://github.com/nodejs/node/pull/42334
- [ ] Support of more embedder objects and bindings: https://github.com/nodejs/node/issues/37476
- [x] Support diagnostics channels: https://github.com/nodejs/node/pull/44193
- [ ] Support vm contexts
- [ ] Support workers

Currently known limitations/bugs that are being fixed in the V8 upstream:

- [x] V8 hits a DCHECK when deserializing certain mutated globals, e.g. `Error.stackTraceLimit` (it should work fine in the release build, however): https://bugs.chromium.org/p/v8/issues/detail?id=12772 (fix in https://chromium-review.googlesource.com/c/v8/v8/+/3319481) (switch to https://github.com/nodejs/node/pull/44203)
- [x] Layout of V8's read-only heap can be inconsistent after deserialization, resulting in memory corruption: https://github.com/nodejs/node/issues/40832 & https://bugs.chromium.org/p/v8/issues/detail?id=12921 ([fixed](https://chromium-review.googlesource.com/c/v8/v8/+/3793525))
Repository: pytorch
Issue: Bilinear interpolation with antialiasing is slow in performance
Labels: module: performance,triaged

### 🐛 Describe the bug

Bilinear interpolation with antialiasing is significantly slower than without.
Is this intended behavior or am I missing something?

Code to reproduce
```python
import torch
import torch.nn.functional as F
from tqdm import tqdm

x = torch.randn((7, 3, 256, 256), device='cuda')
start = torch.cuda.Event(enable_timing=True)
end = torch.cuda.Event(enable_timing=True)

start.record()
for i in enumerate(tqdm(range(10000))):
  F.interpolate(x, (64, 64), mode='bilinear')
end.record()
torch.cuda.synchronize()
print(start.elapsed_time(end))
# 310.09381103515625

start.record()
for i in enumerate(tqdm(range(10000))):
  F.interpolate(x, (64, 64), mode='bilinear', antialias=True)
end.record()
torch.cuda.synchronize()
print(start.elapsed_time(end))
# 1558.083984375
```

### Versions

```
Collecting environment information...
PyTorch version: 1.12.0+cu113
Is debug build: False
CUDA used to build PyTorch: 11.3
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.5 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.5
Libc version: glibc-2.26

Python version: 3.7.13 (default, Apr 24 2022, 01:04:09)  [GCC 7.5.0] (64-bit runtime)
Python platform: Linux-5.4.188+-x86_64-with-Ubuntu-18.04-bionic
Is CUDA available: True
CUDA runtime version: 11.1.105
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.7.6.5
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.0.5
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.0.5
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.12.0+cu113
[pip3] torchaudio==0.12.0+cu113
[pip3] torchsummary==1.5.1
[pip3] torchtext==0.13.0
[pip3] torchvision==0.13.0+cu113
[conda] Could not collect

```

cc @VitalyFedyunin @ngimel
Repository: rust
Issue: Tracking Issue for `float_gamma`
Labels: T-libs-api,C-tracking-issue,A-floating-point

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(float_gamma)]`

This is a tracking issue for adding the [gamma](https://en.wikipedia.org/wiki/Gamma_function) and log-gamma functions to `f32` and `f64` (`tgammaf`, `tgamma`, `lgammaf_r`, and `lgamma_f` from C).

Refs:
- https://github.com/rust-lang/rfcs/issues/864
- https://github.com/rust-lang/rust/issues/18271

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
impl f32 {
    pub fn gamma(self) -> f32;
    pub fn ln_gamma(self) -> (f32, i32);
}

impl f64 {
    pub fn gamma(self) -> f64;
    pub fn ln_gamma(self) -> (f64, i32);
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [ ] Implementation: #99747 
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: godot
Issue: Network profiler doesn't work, nothing shows up
Labels: topic:editor,documentation,topic:network

### Godot version

3.4.2.stable.official

### System information

Windows 10

### Issue description

When using the network profiler nothing shows up, even though RPC calls are being made every second: https://imgur.com/a/7kt3f1s
May be because I'm using custom_multiplayer.

### Steps to reproduce

Create a server and a client using custom_multiplayer and start the network profiler before running the projects.

### Minimal reproduction project

[GithubClientAndServer.zip](https://github.com/godotengine/godot/files/9206576/GithubClientAndServer.zip)
Repository: vscode
Issue: Allow to resolve save conflicts using the merge editor
Labels: feature-request,file-io,workbench-editors

The built-in mechanism to handle FS conflicts nowadays still uses the diff editor:

<img width="351" alt="image" src="https://user-images.githubusercontent.com/22350/181455444-1cf86beb-bc8d-4004-b1ae-773d52c3de75.png">

It would be awesome if it could instead use the merge editor (with no base). Additionally, we could rename `Compare` to `Resolve Conflicts`.
Repository: next.js
Issue: New router behavior around middleware breaks redirects from getInitialProps on CSR
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information


    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.4.0: Fri Mar 18 00:47:26 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T8101
    Binaries:
      Node: 16.10.0
      npm: 7.24.0
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant packages:
      next: 12.2.0
      eslint-config-next: N/A
      react: 17.0.2
      react-dom: 17.0.2



### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

The redirect happens as a rewrite instead of a redirect. The correct redirected page displays, but the URL stays as the page we've initially navigated to. 
SSR still works fine as can be seen when going straight to `/content` in the codesandbox demo from the url bar.

### Expected Behavior

A normal redirect happens.

### Link to reproduction

https://codesandbox.io/s/hungry-glitter-isub6z?file=/pages/content.tsx

### To Reproduce

Redirect the user inside a `getInitialProps` call while also using middleware in your project.

A sample redirection logic can be seen in the codesandbox in `/routing.ts`
Repository: neovim
Issue: multigrid UI: missing msg_set_pos, win_pos events on reattach
Labels: bug,api,channels-rpc,ui-extensibility

### Neovim version (nvim -v)

0.7.2 and 0.7.0

### Vim (not Nvim) behaves the same?

NA

### Operating system/version

Linux NixOS

### Terminal name/version

alacritty

### $TERM environment variable

alacritty

### Installation

GitHub binary release and NixOS 22.05 package

### How to reproduce the issue

I use the following test.py script to emulate a super simple UI:
```python
#!/usr/bin/env python
from pynvim import attach
nvim = attach('socket', path='my_socket')
def notification_cb(name, args):
    if name == 'redraw':
        print(f"Redraw events ({len(args)}):")
        for x in args:
            print(f"    {x[0]}")
    else:
        print(f"Notification {name}", args)
nvim.run_loop(
    lambda name, args: print(f'Request {name}:', args),
    notification_cb,
    lambda: nvim.api.ui_attach(100, 100, {'rgb': True, 'ext_linegrid': True, 'ext_multigrid': True}),
)
```

Then I run in one terminal:
```
nvim --clean --headless --listen 'my_socket'
```

And in another:
```
./test.py
<Ctrl-C>
./test.py
<Ctrl-C>
```

### Expected behavior

I would expect to get functionally the same UI notifications upon first attach and later reattach of the UI. Specifically at least all the same message types should be sent for the first attach and later reattach.

### Actual behavior

However upon reattach (second run of `test.py`) I do not get any `win_pos` or `msg_set_pos` notifications. Output of first `./test.py`
```
Redraw events (17):
    option_set
    default_colors_set
    hl_attr_define
    hl_group_set
    option_set
    default_colors_set
    grid_resize
    grid_clear
    grid_resize
    msg_set_pos
    win_viewport
    grid_resize
    grid_line
    win_pos
    win_viewport
    grid_cursor_goto
    flush
Redraw events (4):
    mode_info_set
    mode_change
    mouse_off
    flush
```

Output of second:
```
edraw events (14):
    option_set
    default_colors_set
    hl_attr_define
    hl_group_set
    option_set
    default_colors_set
    grid_resize
    grid_clear
    win_viewport
    grid_resize
    grid_line
    win_viewport
    grid_cursor_goto
    flush
Redraw events (4):
    mode_info_set
    mode_change
    mouse_off
    flush
```
Repository: flutter
Issue: Canvas draw fill show a little gap.
Labels: engine,platform-windows,a: quality,c: rendering,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-engine,triaged-engine

**Use case : I am drawing a ratio ba**r 

**Here's how I thought of it**

1. draw left-end semi-circle
2. draw right-end semi-circle
3. draw each segment 's Rect shape in middle part depend on their percent.

But there is a very narrow gap showed between each end semi-circle and it's adjacent rect .

This happen in some specific screen size  ,or affected by alginment or other factors  , in other words it's inconsistent performance.
![image](https://user-images.githubusercontent.com/26296915/181481127-a3e99567-80f3-4d63-879e-727046fa7a50.png)

**To Reproduce :** 

You can run code link bellow in Dartpad
 
[Here is a the DartPad demo](https://dartpad.dev/?id=70f0e6dd98888ec09a848a9ca523f0c1)

I guess this's may because floating point arithmetic's precision issue

1. What I want know is does this performance is a Bug? Of just floating point arithmetic problem which couldn't avoid.
3. I know I can draw I a RRect combine the left-end semi-circle with first Rect segment and so on the right one, I want to know is there a  special method to avoid show gap use floating point arithmetic like I did in my code?

Thank you .
Repository: next.js
Issue: NextJs returns cached version of parent route if current route has "locale"-like name
Labels: bug,Internationalization (i18n),linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home Single Language
    Binaries:
      Node: 16.12.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.2.3
      eslint-config-next: 12.2.3
      react: 18.2.0
      react-dom: 18.2.0

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

An appplicaton should have i18n setup. If you try to access `/en/ru` it returns the cached version of `/en`, though cache should be generated at first. It seems to happen when a second route parameter matches to any locale that is setup in application.

If you manage to  `/en/ru` before `/en` it does work as expected.

At the same time urls like `/en/some-page` works as expected

It can be reproduced only with built version of application (`npm run build && npm run start`)

### Expected Behavior

`/en/ru` should always use its own response either from cache or just generated one.

### Link to reproduction

https://stackblitz.com/edit/vercel-next-js-shnr7j

### To Reproduce

- open link https://stackblitz.com/edit/vercel-next-js-shnr7j
- stop running process in terminal
- run `npm run build && npm run start` in terminal
- open `/en/ru` -> should get some text with 200 status
- open `/en` route -> should get Not Found
- open `/en/ru`  again -> returs Not Found
Repository: flutter
Issue: [Proposal] Allow modification of Steps padding in Stepper
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

Need:
It would be nice to be able to customize the Padding around Steps in Stepper. I see it is currently hard written which is kind of restrictive: `const EdgeInsets.all(24.0)`. (line 811 in stepper.dart)

Proposal:
Adding stepPadding attribute to Stepper Widget