sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Remove transitive includes
Labels: c: new feature,engine,P3,team-engine,triaged-engine

Frequently Skia will shift around their headers which breaks its compatibility with the flutter engine.  If flutter engine enforced "no transitive includes" like the Google C++ Style guide states, the codebase wouldn't be brittle and break with these kinds of changes.

Removing the transitive includes should be accompanied with tooling that enforces they aren't reintroduced.

## example failure

https://github.com/flutter/flutter/issues/126864
Repository: next.js
Issue: styled-components rendered by client in app directory
Labels: CSS

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:24 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T8101
    Binaries:
      Node: 17.2.0
      npm: 8.1.4
      Yarn: 1.22.17
      pnpm: N/A
    Relevant packages:
      next: 13.4.3-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.5
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://github.com/alexgoff/styled-components-repro

### To Reproduce

Clone the repo

```
yarn
yarn build && yarn start
```

Go to [http://localhost:3000](http://localhost:3000) and observe that there is a flash of unstyled content before the styled-components global CSS is rendered. This is less apparent with smaller chunks of CSS so I used a UI library's larger global styles to demonstrate the length of time that downloading and rendering the CSS takes on the client side.

Alternatively, disabled Javascript in the browser and load the server, styles will never be applied.

### Describe the Bug

styled-components global styles are rendered on the client side in app directory, even using the `registry.tsx` from the example in documentation. This causes a flash of unstyled content which makes styled-components non-viable in the app directory.

The issue is summed up well [here](https://github.com/styled-components/styled-components/issues/3856#issuecomment-1545104765)

### Expected Behavior

styled-components global styles and other styles are rendered by the server similar to how it functioned in `pages` using `ServerStyleSheets`

https://medium.com/swlh/server-side-rendering-styled-components-with-nextjs-1db1353e915e

### Which browser are you using? (if relevant)

Chrome 113.0.5672.92

### How are you deploying your application? (if relevant)

localhost
Repository: pytorch
Issue: [bazel] add inductor to bazel build
Labels: module: build,triaged,module: bazel

### 🚀 The feature, motivation and pitch

We should work towards allowing torch.compile() to be run from the bazel build.
After https://github.com/pytorch/pytorch/issues/101469
The next step would be enabling inductor backend in the bazel build.

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet @seemethere
Repository: flutter
Issue: Support `PixelFormat.rgbaFloat32` on Web
Labels: c: new feature,engine,platform-web,c: proposal,P2,team-web,triaged-web

The `PixelFormat` enum in the web engine is incomplete. According to https://api.flutter.dev/flutter/dart-ui/PixelFormat.html and the native engine, we are supposed to have a `rgbaFloat32` option as well. In https://github.com/flutter/engine/pull/42019 I added support for it in Skwasm, but it remains unsupported in the other renderers, as well as in the BMP creation code path.
Repository: neovim
Issue: Create a fully "modifiable" nvim terminal emulator (i.e., enable normal mode commands in terminal buffers)
Labels: enhancement,terminal

### Problem

The Neovim terminal ([nvim_terminal_emulator](https://neovim.io/doc/user/nvim_terminal_emulator.html)) is awesome. Combined with plugins such as [vim-slime](https://github.com/jpalardy/vim-slime), it enables powerful IDE-like functionality.

I think the Nvim terminal would be even better if it allowed for a fully "modifiable" mode whereby the normal mode commands work inside the terminal buffer, more akin to the [Emacs terminal](https://www.gnu.org/software/emacs/manual/html_node/emacs/Terminal-emulator.html). Perhaps this could be implemented by "separating" the shell process from the Neovim terminal buffer in which it displayed, such that the buffer becomes more like a regular vim buffer (including normal mode commands) with the added feature that it is capable of sending anything typed into the prompt back to the shell process (automatically updating the buffer with any output).

As far as I know, the current Nvim terminal does not allow for any normal mode edits to the command prompt. For example, pressing `dw` in a terminal buffer will not work (if one has `:set modifiable`, then `dw` will work on any text *prior to the command prompt*, but not on the command prompt itself, where it is most needed). Likewise, the normal mode and terminal mode cursors are distinct, meaning that if I exit from terminal mode to normal mode, move the cursor backwards by a couple of words, and enter terminal mode again, the cursor will return to the position from which I exited terminal mode, essentially "forgetting" any movement that happened in normal mode. 

I do realize that I can activate vi mode in the terminal itself, and this is indeed my current workflow. However, this is suboptimal since it requires navigating through 2 different normal modes, the Nvim normal mode and the terminal vi normal mode, which are not exactly the same and can throw off one's muscle memory.

### Expected behavior

It would be awesome if `:set modifiable` made the terminal behave more like any other Nvim buffer, with fully integrated normal and terminal modes. In other words, it should allow for arbitrary normal mode commands, including on the command prompt. So if I exit to normal mode, press `dw`, and return to terminal mode, a word should have been deleted. In addition, if I exit to normal mode, press `b`, and return to terminal mode, the cursor should now stand one word back from the original position (note this would allow effective navigation of the command prompt using plugins such as [easymotion](https://github.com/easymotion/vim-easymotion)). When in terminal mode, pressing Enter should still allow me to execute commands, and the buffer should automatically update with any new lines from the terminal output.
Repository: godot
Issue: RichTextLabel's built-in effects are not exposed as `push_()` functions
Labels: discussion,topic:gui

### Godot version

4.0.2.stable

### Issue description

I noticed something while working on https://github.com/godotengine/godot/pull/77117. These RichTextLabel methods exist in the C++ source code, but aren't exposed to GDScript unlike other built-in tags like `push_bgcolor()`:

- `push_fade()`
- `push_shake()`
- `push_wave()`
- `push_tornado()`
- `push_rainbow()`

Having these methods exposed would be useful for consistency with other tags, but also because large text is faster to format using `push_*()` methods compared to BBCode.

Note that `set_process_internal(true)` is called in the BBCode handler for those tags ([example](https://github.com/godotengine/godot/blob/8cfa19a078ecc7c5690740a8c669d1ecbd04bb0c/scene/gui/rich_text_label.cpp#L4490)), not in the `push_*()` methods (other than `push_customfx()` which is exposed). This call should be moved to the `push_*` methods so that it works even if you only use `push_*()` methods to format your RichTextLabel's text.

cc @Eoin-ONeill-Yokai – is there a reason these methods aren't exposed?

*Keywords for easier searching: RichTextEffect*
Repository: vscode
Issue: Workspace edit createFile with overwrite deletes file completely on undo
Labels: bug,workspace-edit


Type: <b>Bug</b>

1. Create an workspace edit that tries to overwrite an existing file in the workspace and also makes a text change in the active editor
2. After applying the edit, press undo in the active ditor

Example code:

```ts
import { TextEncoder } from 'util';
import * as vscode from 'vscode';

export function activate(context: vscode.ExtensionContext) {
	let i = 0;
	const encoder = new TextEncoder();

	const disposable = vscode.commands.registerCommand('extension.helloWorld', () => {
		const uri = vscode.Uri.joinPath(vscode.workspace.workspaceFolders![0].uri, 'created.test');

		const workspaceEdit = new vscode.WorkspaceEdit();

		workspaceEdit.insert(vscode.window.activeTextEditor!.document.uri, new vscode.Position(0, 0), `${i}`);

		workspaceEdit.createFile(uri, { contents: encoder.encode(String(i++)), overwrite: true });

		vscode.workspace.applyEdit(workspaceEdit);
	});

	context.subscriptions.push(disposable);
}
```

**bug**
On undo, the file from `createFile` is deleted completely

I'd expect this file to be reverted to the previous version instead 

VS Code version: Code - Insiders 1.79.0-insider (Universal) (9084e081d4e89ed8ab67fce340d573c4e1378939, 2023-05-15T05:24:47.185Z)
OS version: Darwin x64 22.4.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|11, 10, 7|
|Memory (System)|32.00GB (0.09GB free)|
|Process Argv|--crash-reporter-id 48781ca2-1705-4f64-9bab-325055aab55d|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: opencv
Issue: RotatedRect Points are not the same in IntelliJ and Android
Labels: bug

### System Information

OpenCV version 4.6.0
Operating System / Platform embedded Android system
compileSdkVersion 29, minSdkVersion 25, targetSdkVersion 28

OpenCV version 4.4
Windows 11, IntelliJ IDEA 2021.2.2

Here is the image used on both systems:
![D405_SLEEVE_02071639_18507_RRECT](https://github.com/opencv/opencv/assets/45668270/e771a147-02f9-4296-ab45-b275b600b7d8)
.0



### Detailed description

As you can see from the image, the slash (which is a RotatedRect) is angled towards the upper left. I got the correct results when I ran the image though an IntelliJ tester but when I tried the same code on Android, the Point coordinates were shifted so that Point 1 in IntelliJ (84, 40) is reported as Point 0 in Android.

Here are the logs from both systems (concatenated for comparison):
[Rotated rectangle coordinates - differences.txt](https://github.com/opencv/opencv/files/11483180/Rotated.rectangle.coordinates.-.differences.txt)


### Steps to reproduce


And here is the identical Java code used on Android and IntelliJ:
[Slash detection - AS.txt](https://github.com/opencv/opencv/files/11483177/Slash.detection.-.AS.txt) 

If you extract the code that determines the orientation of the RotatedRect from the complete code section you should get the same erroneous results for Android.

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: pytorch
Issue: Investigate random sequence number broadcast initially incorrect
Labels: oncall: distributed,triaged

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/pull/101422 removes an implementation of generating a random sequence number and communicating it via the store, instead opting to start off groups at a sequence number of 0. However, using a random initial sequence number is better for debugging UX as it allows users to easily tell the difference between different collectives corresponding to different subgroups. We should root cause and fix the store issue and re-enable.

### Versions

main

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: pytorch
Issue: Support pipeline parallelism with PyG
Labels: oncall: distributed,triaged,topic: new features

### 🚀 The feature, motivation and pitch

I would like to request support for pipeline parallelism for data constructed by PyG (PyTorch Geometric). Currently, PyG provides excellent capabilities for GNN modeling and processing, our teams use PyG to construct graph data for the drug field. However, there is a lack of native support for pipeline parallelism, which can significantly improve the performance and scalability of GNN training on large-scale graphs.

However, PyTorch does not support pipeline parallelism through the torch.distributed.pipeline.sync.Pipe modules, these modules are not directly compatible with PyG's graph-specific dataset. As a result, users currently need to implement custom solutions or workarounds to enable pipeline parallelism in PyG, which can be challenging and error-prone, our team has tried, but there have been no results.

Therefore, I kindly request that the PyTorch development team consider adding native support for pipeline parallelism. Such support would greatly benefit the PyG community, enabling faster and more efficient training of GNN models on large-scale graphs.

Thank you for considering this request. Please let me know if there are any questions or if I can provide further assistance in this matter.

### Alternatives

The main reason PyG data cannot be used with Pipeline is the inability to locate and correctly split the tensors within the data when dividing the minibatch into microbatches. PyG's tensors are wrapped within a dictionary-like data structure and are not directly exposed. Our team has attempted two approaches to address this issue.

The first approach involved manually splitting and recombining PyG data, but it was challenging to ensure the preservation of the graph topology within each data instance. The second approach attempted to load a certain number of minibatches (chunks) in dataloder first, combine them, and pass them into the Pipeline for internal microbatch splitting. However, this method encountered issues when invoking checkpoints during subsequent stages.

Regrettably, neither of these methods proved effective. It seems that microbatch requires specific handling of tensors.


### Additional context

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: TypeScript
Issue: `DataView.buffer` should be `ArrayBufferLike` instead of `ArrayBuffer`
Labels: Bug,Help Wanted,Domain: lib.d.ts

# Bug Report

### 🔎 Search Terms

dataview

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `ArrayBuffer` and `DataView`.

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/MYewdgzgLgBAbgSwKYHcYF4ZlTAIgQynwDVkUAKbNAZQAt8AnJAEwEEGH8BPAIQFcAZgKQNyABgCUEgNwAoAPTyYylarUA9APyzQkEABskAOn0gA5uUSojAI0HCGMhUrWuVW2UA)

### 💻 Code

```ts
const view = new DataView(new SharedArrayBuffer(0));
//               ^?  var DataView: DataViewConstructor␊new (buffer: ArrayBufferLike, byteOffset?: number | undefined, byteLength?: number | ...
console.log(view.buffer);
//               ^?  (property) DataView.buffer: ArrayBuffer
```

### 🙁 Actual behavior

The type of `view.buffer` is `ArrayBuffer`, while the `DataView` constructor accepts `ArrayBufferLike`.

### 🙂 Expected behavior

The type of `view.buffer` is `ArrayBufferLike`.
Repository: ant-design
Issue: Tooltip by mouseLeave Delay = 0 is not shown
Labels: help wanted,Inactive,4.x

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/bug-tooltip-mouseleavedelay-fu937d)

### Steps to reproduce

1. hover the mouse cursor over the Large tooltip

### What is expected?

the Large tooltip is displayed

### What is actually happening?

the Large tooltip is not open

| Environment | Info |
| --- | --- |
| antd | 4.24.9 |
| React | 18.2.0 |
| System | Win10 |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: deno
Issue: Cannot catch error from RequestEvent.respondWith
Labels: bug,ext/http

I'm writing a server with Server-Sent Events (SSE) endpoints where connections can be abruptly closed by a browser. I'm trying to silently handle such cases by detecting `connection closed before message completed`.

As per [HTTP Server API manual][http-doc], I try/catch RequestEvent.respondWith call. The error is caught but is thrown anyway (even though I do not re-throw it) causing process to be terminated.

Minimally reproducible below. Start the program, go to `localhost:8080` in a browser and refresh the page. Process will terminate.

```ts
const makeResponse = () => {
  const stream = new TransformStream()
  const writer = stream.writable.getWriter()

  setInterval(() => {
    writer.write(new TextEncoder().encode("ping\n"))
  }, 100)

  return new Response(stream.readable, {
    headers: {
      "Content-Type": "text/event-stream",
    },
  })
}

const server = Deno.listen({ port: 8080 })

// From:
// https://deno.com/manual@v1.33.2/runtime/http_server_apis#responding-with-a-response
async function handle(conn: Deno.Conn) {
  const httpConn = Deno.serveHttp(conn)

  for await (const requestEvent of httpConn) {
    try {
      await requestEvent.respondWith(makeResponse())
    } catch (error) {
      console.log("Cought error in respondWith")
      console.warn(error)

      break
    }
  }
}

for await (const conn of server) {
  handle(conn)
}
```

Output:
```
Cought error in respondWith
Http: connection closed before message completed
    at Object.respondWith (ext:deno_http/01_http.js:328:21)
    at eventLoopTick (ext:core/01_core.js:188:13)
    at async handle (file:///Users/soji/Projects/ownbot/server/scratch/shed_break.ts:27:7) {
  name: "Http"
}
error: Uncaught Http: connection closed before message completed
      await requestEvent.respondWith(makeResponse())
      ^
    at Object.respondWith (ext:deno_http/01_http.js:328:21)
    at eventLoopTick (ext:core/01_core.js:188:13)
    at async handle (file:///Users/soji/Projects/ownbot/server/scratch/shed_break.ts:27:7)
```

Deno version:
```js
{ deno: "1.33.2", v8: "11.4.183.1", typescript: "5.0.3" }
```

[http-doc]: https://deno.com/manual@v1.33.2/runtime/http_server_apis#http-requests-and-responses
Repository: opencv
Issue: Cannot disabled gapi when building OpenCV with python
Labels: category: python bindings,priority: low,category: build/install

### Expected behaviour

When set `-DBUILD_opencv_gapi=OFF` during building OpenCV with python, it should be well when I import cv2.

### Actual behaviour

```shell
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/wanli/Desktop/OpenCV_China/opencv/cmake-build-debug/python_loader/cv2/__init__.py", line 181, in <module>
    bootstrap()
  File "/Users/wanli/Desktop/OpenCV_China/opencv/cmake-build-debug/python_loader/cv2/__init__.py", line 175, in bootstrap
    if __load_extra_py_code_for_module("cv2", submodule, DEBUG):
  File "/Users/wanli/Desktop/OpenCV_China/opencv/cmake-build-debug/python_loader/cv2/__init__.py", line 28, in __load_extra_py_code_for_module
    py_module = importlib.import_module(module_name)
  File "/Users/wanli/miniconda3/envs/opencv-dev/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/Users/wanli/Desktop/OpenCV_China/opencv/cmake-build-debug/python_loader/cv2/gapi/__init__.py", line 301, in <module>
    cv.gapi.wip.GStreamerPipeline = cv.gapi_wip_gst_GStreamerPipeline
AttributeError: partially initialized module 'cv2' has no attribute 'gapi_wip_gst_GStreamerPipeline' (most likely due to a circular import)

```

### Steps to reproduce

- build  OpenCV with
  ```shell
  -DBUILD_opencv_python2=OFF
  -DBUILD_opencv_python3=ON
  -DBUILD_opencv_gapi=OFF
  -DPYTHON3_INCLUDE_DIR="path/to/python3.8"
  -DPYTHON3_EXECUTABLE="path/to/bin/python" 
  -DPYTHON3_NUMPY_INCLUDE_DIRS="path/to/site-packages/numpy/core/include/"
  -DCMAKE_OSX_ARCHITECTURES=arm64 
  -DCMAKE_SYSTEM_PROCESSOR=arm64
  ```
- MacOS
- architecture arm 64
- opencv 4.x
Repository: neovim
Issue: netrw, clipboard=unnamedplus and wl-copy cause high CPU load when netrw banner is turned off
Labels: bug-vim,clipboard,netrw

### Problem

I noticed that when i turn off the banner in netrw (via config or via `I`) my cursor starts to flicker and the CPU load goes up noticeably. While debugging I found out that when this happens, there's also a rapid deletion and creation of `/tmp/wl-copy-buffer-xxxx` directories happening at the same time. 

Curiously, this only happens when the netrw banner is turned **off**.

### Steps to reproduce

```
cd /tmp
nvim --clean

:set clipboard=unnamedplus
:Explore
<I>   # press 'I' to disable the banner in netrw
```

Observe how the curser starts to flicker and the CPU usage goes up considerably. When in `/tmp`,  you should see a directory called `wl-copy-buffer-xxxx` being rapidly created and deleted with a new suffix -- probably causing this issue.


### Expected behavior

CPU load should not increase when the banner is turned off, and the cursor should not flicker as well.

### Neovim version (nvim -v)

v0.7.2, confirmed also with latest nighly

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

yes, 9.0

### Operating system/version

Debian

### Terminal name/version

gnome-terminal

### $TERM environment variable

xterm-256color

### Installation

apt
Repository: pytorch
Issue: torch.nn.functional.scaled_dot_product_attention() : support both attn_mask and is_causal
Labels: triaged,module: sdpa

### 🚀 The feature, motivation and pitch

It would still be great if `torch.nn.functional.scaled_dot_product_attention()` supported setting both `attn_mask` and `is_causal=True`. In which case it ignores the upper triangular part of `attn_mask` and implicitly assumes it's either set to False or -inf. This would allow us to do some sort of relative positional encoding and causal masking at the same time while saving compute and memory.

### Alternatives

At the moment you set `is_causal=False` and make sure `attn_mask` is inherently causal. That's fine, but we're missing an optimization.

### Additional context

Mentioned in #100709