sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: node spawn timeout not work
Labels: node compat,node API,triage required 👀

It seems like the `timeout` parameter of the `spawn` method in Node's `child_process` module did not take effect.

child.js：
```js
import { delay } from "https://deno.land/x/delay@v0.2.0/mod.ts";

console.log("Hello world!");
await delay(10_000);
console.log("Hello world end!");
```
mod.ts
```ts
import { spawn } from "node:child_process";

function test(
  command: string,
  options: string[],
  timeout: number,
) {
  return new Promise<string>((resolve, reject) => {
    console.info(command + " " + options.join(" "));
    const childProcess = spawn(command, options, {
      timeout,
    });
    const stdout: string[] = [];

    childProcess.stdout.on("data", (data: string) => {
      stdout.push(data);
      const info = data.toString().trim();
      console.info(info);
    });

    childProcess.stderr.on("data", (data: string) => {
      console.warn(`stderr: ${data}`);
    });

    childProcess.on("error", (error: Error) => {
      reject(error);
    });

    childProcess.on("close", (code: number) => {
      console.debug(`exit code: ${code}`);
      if (code == 0) {
        resolve(stdout.join(""));
      } else {
        reject(stdout.join(""));
      }
    });
  });
}

test("deno", ["run", "child.js"], 1000);
```

Deno will not generate error messages, but Node.js works:

```js
import { spawn } from "node:child_process";

function test(
  command,
  options,
  timeout,
) {
  return new Promise((resolve, reject) => {
    console.info(command + " " + options.join(" "));
    const childProcess = spawn(command, options, {
      timeout,
    });
    const stdout = [];

    childProcess.stdout.on("data", (data) => {
      stdout.push(data);
      const info = data.toString().trim();
      console.info(info);
    });

    childProcess.stderr.on("data", (data) => {
      console.warn(`stderr: ${data}`);
    });

    childProcess.on("error", (error) => {
      reject(error);
    });

    childProcess.on("close", (code) => {
      console.debug(`exit code: ${code}`);
      if (code == 0) {
        resolve(stdout.join(""));
      } else {
        reject(stdout.join(""));
      }
    });
  });
}

test("deno", ["run", "child.js"], 1000);
```
This is log:
```
deno run child.js
Hello world!
exit code: null
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "Hello world!
".] {
  code: 'ERR_UNHANDLED_REJECTION'
}
```
Test Deno version is 1.33.4 and 1.34.2.
Node.js version is  `v16.16.0`.
Repository: go
Issue: net/http: add test coverage for Fetch API-based Transport when viable
Labels: Suggested,Testing,NeedsInvestigation,arch-wasm,OS-JS

In https://github.com/golang/go/issues/57613#issuecomment-1408977731, I wrote:

> [...] the main reason the fake socket path was used is because that was the easiest path forward at the time. Back then, the NaCL port had the fake socket code implemented, and Node didn't support fetch. By now, with NaCL port being long gone and Node supporting fetch, it might be net simpler to start using fetch. But that is fine to investigate and consider doing if desired later.
>
> Just disabling fetch during tests with Node 18 as done in CL 463976 is good to resolve the immediate issue. Thanks.

Now that the immediate issue is resolved, this is the tracking issue for the "investigate and consider doing" part.

In addition to possibly being simpler, I think the main benefit here would be if it lets us have coverage for the Fetch API-based Transport on the builders, and help catch regressions like:

- #60808
- #60809

CC @golang/js, @golang/wasm.
Repository: next.js
Issue: Styling a Link with styled components and sending props to it causes react warning
Labels: bug,Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #22 SMP Tue Jan 10 18:39:00 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant packages:
      next: 13.4.6-canary.7
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/nextjs-with-styled-components-forked-k72zrg

### To Reproduce

- Use next 13 with the the new next/link behaviour, don't pass legacyBehavior.
- Style the link with additional props that is used for styling. Any prop that isn't a next/link prop.
- React will try to render all props as attributes to the link resulting in a warning

### Describe the Bug

Any prop that isn't a next/link prop but that is used for styled components will get rendered as attributed to the a tag and react will give a warning. 

```
Warning: Received `true` for a non-boolean attribute `green`.
If you want to write it to the DOM, pass a string instead: green="true" or green={value.toString()}.
```

### Expected Behavior

next/link should only render valid dom attributes

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: opencv
Issue: get error camera matrix   via cv2.fisheye.estimateNewCameraMatrixForUndistortRectify 
Labels: bug

### System Information

OpenCV python version:  4.7.0.72
Operating System / Platform: Windows10
Python version: 3.8.5

### Detailed description

get error camera matrix ,only use the following parameters:

%YAML:1.0
---
cameraMatrix: !!opencv-matrix
   rows: 3
   cols: 3
   dt: d
   data: [ 8.4987044312532169e+02, 0., 6.2728966391800384e+02, 0.,
       8.5362038761017914e+02, 4.3635413503683299e+02, 0., 0., 1. ]
distCoeffs: !!opencv-matrix
   rows: 4
   cols: 1
   dt: d
   data: [ -2.3462278813889084e-01, 9.2107063465541783e-01,
       -2.5047580340684577e+00, 1.0204472248251186e+00 ]


### Steps to reproduce

`newCameraMatrix = cv2.fisheye.estimateNewCameraMatrixForUndistortRectify(cameraMatrix,distortionMatrix , (1080,1080), None, balance=0.0)`

get a error camera matrix

[[1.08000024e-03 0.00000000e+00 1.07999998e+03]
 [0.00000000e+00 1.08476561e-03 1.08000024e+03]
 [0.00000000e+00 0.00000000e+00 1.00000000e+00]]

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] 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
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: excalidraw
Issue:  Rich Text Editor / Powerful WYSIWYG support
Labels: enhancement,richtext

As an extensive Excalidraw user I miss this feature specially when it comes creating presentations as I need to highlight specific parts of text or style them differently.
There is also an issue https://github.com/excalidraw/excalidraw/issues/1126 regarding adding the ability to colour different parts of text  

Here are some of the Rich Text Editors we can try out 

1. https://quilljs.com/ - 54.19KB (gzip) - probably this doesn''t have hightling with diff color support as well
2. https://lexical.dev/ - 29.79KB (gzip)
3. https://ckeditor.com/ - 277.17KB (gzip) 
4. https://github.com/basecamp/trix - too basic so probably not suitable for us as it doesn't have features like highlighting

There are couple of more, I will add here as I come across. Lexical seems to the best choice so far with features and bundle size as well.
Repository: excalidraw
Issue: Support more handwritten fonts in different languages
Labels: enhancement,font

There has been lot of requests to support handwritten font in different languages eg Chinese, Japanese, Arabic and more so creating this issue for linking all of theme at one place.


```[tasklist]
### Tasks
- [x] Chinese Handwritten font support #6394, #5665, #5259
- [x] Japanese Handwritten font support #1615
- [ ] Arabic Handwritten font support #6619
- [ ] Hebrew Handwritten font support #5633
```

`Chinese` is requested the most so we can start with supporting Chinese
Repository: vscode
Issue: Resolve all glob patterns for `files.associations` relative to workspace root
Labels: feature-request,languages-basic,keep

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:  1.79.1
- OS Version: Windows 11

Steps to Reproduce:

1. Create the following configuration:

```json
"files.associations": {
    "config/docker/*.cnf": "ini"
}
```
2. Create a file `config/docker/mariadb.cnf`
3. Files `mariadb.cnf` is not recognized as INI file

On the contrary, `**/config/docker/*.cnf` works as expected, but it would associate also `foo/config/docker/test.cnf`, which I don't wanto to.
Repository: excalidraw
Issue: Introduce a property Text Color for Text containers and labelled arrows
Labels: enhancement,Text containers,Labeled Arrows

Right now if we want to update colour of Text inside a Text container / Labelled arrow then we select the container and update its stroke color however if we want to colour if differently from the container stroke color then the only way is to double click and select the text and update the **Stroke colour.**


https://github.com/excalidraw/excalidraw/assets/11256141/21a4b9a1-9bba-4019-8f70-649155bc7847

1. However often might want to colour the text differently than stroke colour and double click is not ideal always and is currently sort of hack to achieve it and sometimes I do want the container stroke as transparent as mentioned in https://github.com/excalidraw/excalidraw/issues/5863 where I end up using double click hack

2. This also won't work when we want to update the text colour of **multiple text containers / labelled arrows** at once so having a field for it separately will be helpful. 

3. The Stroke colour and Text colour are two different properties and right now its used to serve two separate purpose.

Hence having a separate field **"Text Colour"** which is responsible for only updating text colour will be helpful
Repository: PowerToys
Issue: Mouse Without Borders - Share Clipboard , Transfer file not working
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.70.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

![image](https://github.com/microsoft/PowerToys/assets/14323465/f7b16c8e-4008-4040-b097-531a85e67408)
![image](https://github.com/microsoft/PowerToys/assets/14323465/ac1dccb6-c12b-4c8e-9836-76a410ba5ace)



### ✔️ Expected Behavior

Share Clipboard, Transfer file to another machine 

### ❌ Actual Behavior

**hit Ctrl + Alt + Del then Esc key，still unable to work**

### Other Software

_No response_
Repository: opencv
Issue: Warning C4127 for a missed constexpr opportunity
Labels: category: build/install,platform: win32

### System Information

Windows 7 64b, Visual Studio 2019
C++ (C++14 or C++17)
Debug build


### Detailed description

When compiling some code using OpenCV, with Debug+W4 warning level, "Warning C4127" is often raised and clutters the build console.
Warning C4127 is raised for an `if` statement that is always true/false at compile time and should be replaced with an `if constexpr`

It is totally harmless aside cluttering the output, and obviously could be explicitely silenced, but it might be an improvement to avoid it anyway.

In my case, I have observed the following source of Warning C4127

- in `_Tp Rect_<_Tp>::area() const`
- for a `_Tp=double` or `_Tp=float`
- because of the `CV_DbgAssert(...)` using `std::numeric_limits<_Tp>::is_integer`

`std::numeric_limits<_Tp>::is_integer` could be checked in an `if constexpr` outside of the `CV_DbgAssert()`


### Steps to reproduce

Use somewhere (Debug Build, W4 level)
```
cv::Rect2d r;
r.area();
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: vscode
Issue: Allow EnvironmentVariableCollection to unset variables
Labels: feature-request,api,terminal-process

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
[EnvironmentVariableCollection](https://code.visualstudio.com/api/references/vscode-api#EnvironmentVariableCollection) currently support modifying a variable, or deleting a *modification* in that collection, but not *unsetting* an environment variable.

Sometimes we want to unset variables in the [direnv extension](https://github.com/direnv/direnv-vscode) but there is no API for it (and if we force `null` or `undefined` through the current API they get automatically stringified to `"null"` and `"undefined"`).
The closest we can do is set them to the empty string (what POSIX calls null), but then some programs insist on distinguishing empty from undefined variables.
(N.B. Shells make this intentionally hard, for example the bash man page omits the expansion modifiers that distinguish null and unset variables.)

This could be done either by allowing `null` and/or `undefined` as the replacement value for `replace`, or with a new method on the API.

Related issue: direnv/direnv-vscode#527, and previously NixOS/nix#6409

Related commits: direnv/direnv-vscode@9905fe78d09a56264a0b229fba16326d181fe618, and previously direnv/direnv-vscode@79a4841ea6700cedcaa7849126c1acf0b5726e92
Repository: rust
Issue: Misleading `borrowed data escapes outside of function` error message due doesn't mention actual borrow that is affected
Labels: A-diagnostics,T-compiler

### Code

```Rust
struct Foo {
    s: Option<String>,
    i: i32,
}

fn foo(f: &Foo) {
    let s = match f.s.as_ref() {
        None => return,
        Some(s) => s,
    };
    
    let f = f.clone();
    std::thread::spawn(move || {
        println!("{:?} {:?}", s, f.i); 
    }).join();
}

fn main() {
    let f = Foo { s: Some(String::from("test")), i: 123 };
    foo(&f);
}
```


### Current output

```Shell
Compiling playground v0.0.1 (/playground)
error[E0521]: borrowed data escapes outside of function
  --> src/main.rs:13:5
   |
6  |   fn foo(f: &Foo) {
   |          -  - let's call the lifetime of this reference `'1`
   |          |
   |          `f` is a reference that is only valid in the function body
...
13 | /     std::thread::spawn(move || {
14 | |         println!("{:?} {:?}", s, f.i); 
15 | |     }).join();
   | |      ^
   | |      |
   | |______`f` escapes the function body here
   |        argument requires that `'1` must outlive `'static`

For more information about this error, try `rustc --explain E0521`.
error: could not compile `playground` (bin "playground") due to previous error
```
```


### Desired output

```Shell
I don't have a good suggestion how this could look like, but the error message should contain something in addition to what it currently contains that refers to 

  1. `s` being borrowed from `f`
  2. `s` being moved into the closure and thus requiring a `'static` lifetime
  3. `s` not having a `'static` lifetime because it's constrained by `f` in the way the original error message explains
```


### Rationale and extra context

Currently the error message does not contain any reference to `s` at all although that's the starting point where the borrowing rules are violated. If there's a lot of code between the `match` and the `thread::spawn()`, and the closure is also a lot of lines long, it can take a while to figure out that it's actually `s` that causes the problem here (and you'd have to re-borrow it from the `f` clone inside the closure).

### Other cases

```Rust
In this case it's only one level of indirection (`s` borrowing from `f`), but this could potentially be extended to more levels of indirection with multiple chained borrows.
```


### Anything else?

_No response_
Repository: kubernetes
Issue: 10 second timeout when killing or evicting pod
Labels: kind/bug,sig/node,triage/accepted

### What happened?

Killing or evicting a pod that is already terminated will result in a 10 second timeout in killPodNow.

A warning event is logged: 

Reason: ExceededGracePeriod, Message: Container runtime did not kill the pod within specified grace period.

The problem appears when using emptyDir volumes with limits. The volume scan might run after the pod has already finished.

### What did you expect to happen?

killPodNow should exit without timeout and no event should be generated.

### How can we reproduce it (as minimally and precisely as possible)?

Create a pod with emptyDir volume with size limit, write data beyond the size limit and quit immediately. When eviction is triggered if the pod is already finished it will generate an ExceededGracePeriod event.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: godot
Issue: Vulkan: External monitor occasionally freezes when using hybrid Intel + NVIDIA graphics on Linux
Labels: bug,platform:linuxbsd,topic:rendering,topic:editor,confirmed,topic:thirdparty

### Godot version

v4.0.2.stable.arch_linux

### System information

Manjaro, laptop with additional external monitor

*Bugsquad edit:* My laptop is Acer Nitro 5 with 32 GB RAM, 3 disks - 2 NVMe SSDs and 1 SATa HDD, I've got i5-9300H processor and Nvidia geForce GTX 1650 with 4 GB of VRAM.
Nvidia driver is NVIDIA 530.41.03, OpenGL API 3.3.0, and Vulkan API 1.3.236. Project using Forward+ redering.

### Issue description

I've got problem if I'm using Godot on my Manjaro with my second monitor, my second monitor freezing some times. I'm using nvidia gpu in laptop and intel igpu with hibrid prime drivers. The same issue is when I using dedicated GPU and iGPU, but on the second egnine can crash.

### Steps to reproduce

- Do something.
- Saving
- Writing script
- Imporrting

### Minimal reproduction project

N/A
Repository: excalidraw
Issue: Improve documentation :)
Labels: documentation

We launched new [docs](https://docs.excalidraw.com) recently but we need to make it better for user facing queries.

I am listing down the queries which we often get though we have mentioned it in docs but it needs to be improved so its more clear and helps in better communication. Feel free to add more.

- [ ] How to integrate Excalidraw in non React Projects ? Basically this is the way to do it https://docs.excalidraw.com/docs/@excalidraw/excalidraw/integration#browser and we need to improve the docs to communicate this better. There are couple of discussions also opened related to same https://github.com/excalidraw/excalidraw/discussions/4100, https://github.com/excalidraw/excalidraw/discussions/6537,https://github.com/excalidraw/excalidraw/discussions/3849
- [ ] How to support collaboration in Excalidraw npm package ? Its mention in [FAQ](https://docs.excalidraw.com/docs/@excalidraw/excalidraw/faq#does-this-package-support-collaboration-) but we get this query often and we need to improve the docs for the same. There are discussion opened related to this as well (apart from the one linked in FAQ) - https://github.com/excalidraw/excalidraw/discussions/6676, https://github.com/excalidraw/excalidraw/discussions/5902, https://github.com/excalidraw/excalidraw/discussions/3941, https://github.com/excalidraw/excalidraw/discussions/4924, https://github.com/excalidraw/excalidraw/discussions/4685
- [ ] Improve docs on how one can start collaboration locally by connecting to the collab server for development. There are couple of issues opened related to this as well
- [ ] Document JSON schema https://github.com/excalidraw/excalidraw/issues/6804

- [ ] Add code_of_conduct https://github.com/excalidraw/excalidraw/issues/6859
Repository: rust
Issue: change handling of subtyping to be less fragile after analysis
Labels: C-cleanup,A-MIR,E-medium,A-mir-opt,A-variance

*edit: no longer up-to date. the current plan is to add the explicitly add the source type to MIR casts instead*

We should add a MIR pass after analysis (and before any optimizations) which makes subtyping explicit in the MIR. This is a robust way to fix https://github.com/rust-lang/rust/issues/107205, preventing similar issues in the future. I don't quite know how to do that, probably by adding an explicit `ProjectionElem::Cast` (probably reusing `OpaqueCast` for that).

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"ouz-a"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: transformers
Issue: Add training support for EnCodec
Labels: Good Second Issue,Feature request

### Feature request

Would be cool to add training support for the EnCodec model. 
Not entirely sure if we can easily make it compatible with Trainer, so this can be a good second issue I think. 

### Motivation

…

### Your contribution

…
Repository: vscode
Issue: Reconsider the request to allow modals in Simple Browser and other WebViews
Labels: feature-request,webview

@mjbvz graciously accepted my recent PR https://github.com/microsoft/vscode/pull/185117 to make webview-hosted pages able to download files. This means Simple Browser can now do a better job of hosting a legacy web app that is important to users of several of my extensions. But that web app still chokes whenever the user takes a path leading to a `window.alert()` or `window.confirm()`. There is little prospect of the web app being changed to use `<dialog>` instead.

Back in 2019 @GordonSmith unsuccessfully [requested](https://github.com/microsoft/vscode/issues/67109) `allow-modals`. Please reconsider this.