sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: proposal: encoding/json.Encoder: add `ZeroizeNilSlice` option
Labels: Proposal

## What does it do

Use `(*json.Encoder).SetZeroizeNilSlice(true)` can let the encoder encode nil slice as an empty json array `[]` instead of `null`

## Why

If we have a nil slive `[]Type(nil)`, the encoder will encode it as `null`. Then the consumers will having trouble with it, they must to check if the field is null first.  
A way to solve this problem is always alloc a zero length slice before encoding. However, I want my code be simplify but not fill with `make([]Type, 0)` every where.

## Additional Information

1. This change should be completely backward compatible.
2. The options name is not good, maybe have to decide a better name later.
Repository: pytorch
Issue: DISABLED test_cross_entropy_large_tensor_reduction_mean_cuda (__main__.TestNNDeviceTypeCUDA)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on master ([recent examples](http://torch-ci.com/failure/test_nn.py%3A%3ATestNNDeviceTypeCUDA%3A%3Atest_cross_entropy_large_tensor_reduction_mean_cuda)).

cc @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: PowerToys
Issue: [Feature Request] Feedback for copy/cut/paste shortcuts
Labels: Needs-Triage

### Description of the new feature / enhancement

This feature would be showing a small popup on the mouse, or an audio clip when ctrl+c/x/v was successfully used to copy/cut/paste.

### Scenario when this would be used?

Windows clipboard shortcuts sometimes don't work, be it because the user didn't press the buttons hard enough, or due to some reason. 

Having used ctrl+c on a text, and then later finding out that it wasn't actually copied to the clipboard can be extremely frustrating. It happens to me quite often, and I'm 100% sure it's often not the user's fault. It sometimes flat out just doesn't copy to clipboard. 

A visual or audio indication that something was copied to the clipboard would completely eliminate this frustration.


### Supporting information

I've seen other user complain about it in various help requests, but Microsoft support is always blaming the user, which I think is a very bad way to go about this issue. Even if it was 100% the user's fault, adding a clipboard feedback would still fix the frustration completely.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Add a option to install only things AMD can use
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

adding a option for it to install NVidia or AMD's limited support so people dont mess with things that will mess it up

### Proposed workflow

1. Go to .... 
2. Press ....
3. ...


### Additional information

_No response_
Repository: next.js
Issue: usePathname() causes hydration errors when combined with rewrites
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: #1 SMP Fri Apr 2 22:23:49 UTC 2021
    Binaries:
      Node: 18.15.0
      npm: 9.6.7
      Yarn: 1.22.11
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10-canary.8
      eslint-config-next: 13.4.10
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/codeurs/next-rewrites-usepathname-hydration-error

### To Reproduce

```
git clone git@github.com:codeurs/next-rewrites-usepathname-hydration-error.git
cd next-rewrites-usepathname-hydration-error
yarn && yarn build && yarn start
```
Click on the /bug link. It will open a new tab where the hydration error will occur.

### Describe the Bug

Within next.config.js I added a rewrite to rewrite /bug to /error.

When we navigate to /bug, /bug is printed because usePathname() is giving the current pathname as a response.
But, while building the app, /error is prebuild. And because usePathname() is resulting in /error at that time, it's not matching with our /bug route which is rewrited to /error. So an hydration error occurs.

### Expected Behavior

usePathname() should return the destination path from the rewrite settings.
In this case usePathname() would result in /error while visiting /bug. By this no hydration errors would occur.

OR

/bug should also be prebuild with usePathname() returning /bug; in this case there would not be a hydration error as well.
But rewrite source routes are not prebuild.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: pytorch
Issue: [discussion] Integrate widely used utilities from fvcore into the core repo
Labels: oncall: distributed,feature,module: nn,triaged,needs research,module: LrScheduler

### 🚀 The feature, motivation and pitch

Some things like FLOP counter (https://dev-discuss.pytorch.org/t/the-ideal-pytorch-flop-counter-with-torch-dispatch/505/15 by @Chillee )  have already been reimplemented in core. But I propose to systematically study widely used things in fvcore (primarily uses in detectron2: https://github.com/search?q=repo%3Afacebookresearch%2Fdetectron2+fvcore+language%3APython&type=code&l=Python) and maybe move some of them into core (it would allow people to take fewer dependencies. that repo has existed now for a long time, so popularity/success of utils there can now be estimated more or less well):

- For instance, in vision/detectron2-related code weight inits from https://github.com/facebookresearch/fvcore/blob/main/fvcore/nn/weight_init.py are often used

- Another useful one is https://github.com/facebookresearch/fvcore/blob/main/fvcore/nn/print_model_statistics.py

- There are also some distributed utils

- It also has stateless schedulers used by detectron2: "A stateless, scale-invariant hyperparameter scheduler: see its [API doc](https://detectron2.readthedocs.io/en/latest/modules/fvcore.html#fvcore.common.param_scheduler.ParamScheduler)". It is also related to https://github.com/pytorch/pytorch/issues/68332, so maybe can be this design can be taken as base for schedulers enhancement / redesign in core (it has float iterations and uses `__call__` syntax; might be more generic to allow for int64 iterations and derive from nn.Module? Or even better: fully stateless free functions)

There are also a bunch of losses there that seem to have been already implemented in core. It would be useful then to deprecate / add warnings to the impls in fvcore or at least add a word in README there.

### Alternatives

_No response_

### Additional context

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: flutter
Issue: Support textures in software rendering for the embedded engine
Labels: c: new feature,engine,c: proposal,P3,team-engine,triaged-engine

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Custom embedder with software rendering fallback to draw wlroots surfaces onto the screen without handling compositing.

### Proposal

The embedded engine currently supports textures only with OpenGL or Metal. This feature proposal if implemented will add the ability to draw textures in software rendering without the need of overriding the compositing and using platform views. This would simplify the ability to render things not from Flutter itself in software rendering.

A mock up of the structure for the texture would look like this:
```c
typedef struct {
  void* buffer;
  uint32_t width;
  uint32_t height;
  FlutterSoftwarePixelFormat format;
  void* user_data;
  VoidCallback destruction_callback;
} FlutterSoftwareTexture;
```
Repository: godot
Issue: Android: onDestroy Causes segfault
Labels: bug,platform:android,topic:porting,crash

### Godot version

4.1-stable

### System information

Android API 33, Samsung S23

### Issue description

onDestroy causes segfault on basic games in Android. When you can reliably trigger onDestroy, bug reproduction is 100%.

Tested on Samsung galaxy s23 with Android API 33, and 2 emulated pixel 5's (API 33 and 32).

This bug seems to affect most apps. It may go unnoticed because normally you'd have to wait for the system to call onDestroy(), which could take hours. And then you may only notice that the first time you try to re-open your app it just closes right away but then works when you relaunch it. However, this issue could end up auto-sending a significant number of bug reports to the Play store leading to app removal.

### Steps to reproduce

Reproduction is trivial. Create an app with a single scene consisting of a sole CanvasLayer with "Follow Viewport" enabled (no scripts or other changes required). In the phone, enable "Don't Keep Activities" in developer settings (this will trigger onDestroy when the app is swiped away). Launch the app and then swipe it away. Observe "USER ERROR" messages and SIGSEGV with backtrace in logcat (see attached file).
If you reproduce the above steps without "Follow Viewport" (or with a Node2D instead) the segfault won't happen but the "USER ERROR" messages will appear. 

[godot-4.1-android.log](https://github.com/godotengine/godot/files/12061908/godot-4.1-android.log)


### Minimal reproduction project

N/A
Repository: neovim
Issue: libtermkey crashes when receiving CSI sequences with 17 or more arguments
Labels: tui,bug-crash

### Problem

When Nvim receives a CSI sequence with 17 or more arguments, it outputs the following error message and crashes:
```
*** stack smashing detected ***: terminated
                                           Aborted (core dumped)
```

The cause of this issue is in the `peekkey_csi` function at line 533 of `driver-csi.c` in libtermkey. The buffer that stores the arguments for the CSI sequence is declared with a size of 16, causing a buffer overflow when trying to store the 17th argument.
Applying the following patch to `driver-csi.c` can mitigate the problem:
```patch
532,533c532,533
<   size_t args = 16;
<   long arg[16];
---
>   size_t args = 32;
>   long arg[32];
```

According to the documentation, Nvim sends `CSI ? u CSI c` during startup. Some terminal emulators respond to this with `CSI ? 65;1;2;3;4;6;7;8;9;15;18;21;22;29;39;42;44 c`, which has more than 16 arguments. As a result, Nvim crashes during startup.

### Steps to reproduce

1. Run `nvim --clean`
1. Send `\x1b[?65;1;2;3;4;6;7;8;9;15;18;21;22;29;39;42;44c` to Nvim

### Expected behavior

No crash

### Neovim version (nvim -v)

NVIM v0.9.1, libtermkey 0.22

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

no, vim 9.0.1628

### Operating system/version

`Linux alarmpi 6.1.35-4-rpi-ARCH #1 SMP Sun Jun 25 13:05:28 MDT 2023 armv7l GNU/Linux`

### Terminal name/version

RLogin (x64) Version 2.28.3 (2023/07/03) https://github.com/kmiya-culti/RLogin

### $TERM environment variable

xterm-256color

### Installation

`sudo pacman -Syu neovim`
Repository: transformers
Issue: Pipeline feature request for min_new_tokens
Labels: WIP

### Feature request

Pipeline already supports the option max_new_tokens.

I’m requesting for the existing “min_new_tokens” to be able to be used with pipeline the same way as “max_new_tokens”.

Currently this will throw an error when trying to specify “min_new_tokens” as unrecognised.  

### Motivation

Maintaining consistency, as the previous way to specify tokens is deprecated.

### Your contribution

I can test, but I’m not a developer. So no, I couldn’t do a PR.
Repository: next.js
Issue: vercel error no such file or directory, open '/var/task/node_modules/shiki/themes/one-dark-pro.json'
Labels: bug

### 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 22.5.0: Thu Jun  8 22:22:19 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T8103
    Binaries:
      Node: 16.16.0
      npm: 9.8.0
      Yarn: 1.22.19
      pnpm: 7.16.0
    Relevant Packages:
      next: 13.4.10
      eslint-config-next: 13.4.10
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


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

App Router

### Link to the code that reproduces this issue or a replay of the bug

.

### To Reproduce

```jsx
import { serialize } from 'next-mdx-remote/serialize';
import readingTime from 'reading-time';
import remarkGfm from 'remark-gfm';
import rehypeSlug from 'rehype-slug';
import rehypeAutolinkHeadings from 'rehype-autolink-headings';
import rehypePrettyCode from 'rehype-pretty-code';

/** @type {import('rehype-pretty-code').Options} */
const options = {
    theme: 'one-dark-pro',
    onVisitLine(node: any) {
        if (node.children.length === 0) {
            node.children = [{ type: 'text', value: ' ' }];
        }
    },
    onVisitHighlightedLine(node: any) {
        node.properties.className.push('line--highlighted');
    },
    onVisitHighlightedWord(node: any) {
        node.properties.className = ['word--highlighted'];
    },
};

export async function mdxToHtml(source: any) {
    const mdxSource = await serialize(source, {
        mdxOptions: {
            remarkPlugins: [remarkGfm],
            rehypePlugins: [
                rehypeSlug,
                [rehypePrettyCode, options],
                [
                    rehypeAutolinkHeadings,
                    {
                        properties: {
                            className: ['anchor'],
                        },
                    },
                ],
            ],
            format: 'mdx',
        },
    });

    return {
        html: mdxSource,
        wordCount: source.split(/\s+/gu).length,
        readingTime: readingTime(source).text,
    };
}
```
got this error in vercel logs while building pages and i am using app router

```bash
ENOENT: no such file or directory, open '/var/task/node_modules/shiki/themes/one-dark-pro.json'
and i also install shiki package

```

### Describe the Bug

got this error in vercel logs while building pages and i am using app router


### Expected Behavior

mdx

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

brave

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

Vercel
Repository: opencv
Issue: can't use cuda detect onnx
Labels: bug,category: gpu/cuda (contrib),category: dnn

### System Information

OpenCV version: 4.8.0
Operating System / Platform: windows 11
CUDA version:12.1
CUDNN version:  v8.9.3 (July 11th, 2023), for CUDA 12.x

### Detailed description

```
net.forward(netOutImg, net.getUnconnectedOutLayersNames());
```
while detect，
error from ..\opencv-4.8.0\modules\dnn\src\cuda4dnn\csl\cudnn\convolution.hpp line 200
```CUDA4DNN_CHECK_CUDNN(cudnnCreateConvolutionDescriptor(&descriptor));```
Unhandled exception at 0x00007FF9AA4FDF51 (cudnn64_8.dll) (in 1.exe): a fatal program exit was requested.

### Steps to reproduce

```cpp
//cv::Mat netInput;
cv::dnn::Net net = cv::dnn::readNetFromONNX(ONNXpath);
if (1)
{
	net.setPreferableBackend(cv::dnn::DNN_BACKEND_CUDA);
	net.setPreferableTarget(cv::dnn::DNN_TARGET_CUDA); 
}
else
{// is success
	net.setPreferableBackend(cv::dnn::DNN_BACKEND_DEFAULT);
	net.setPreferableTarget(cv::dnn::DNN_TARGET_CPU);
}
cv::Mat blob;
cv::dnn::blobFromImage(netInput, blob, 1 / 255.0, cv::Size(640, 640), cv::Scalar(0, 0, 0), true, false);
net.setInput(blob);
std::vector<cv::Mat> netOutImg;
net.forward(netOutImg, net.getUnconnectedOutLayersNames());
```

### 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
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: excalidraw
Issue: Framing tool as links
Labels: More information needed / cannot reproduce

It would be incredible if the new framing tool could be used as a window into one drawing from other, allowing a chunk of the notes to be repeated but also synced in two different drawings.
Repository: next.js
Issue: [...catchAll] inside parallel route @slot not matched when route is already defined outside slot
Labels: bug

### 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.6.0: Sat Jun 18 17:07:22 PDT 2022; root:xnu-8020.140.41~1/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 8.6.0
    Relevant Packages:
      next: 13.4.10
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/lmatteis/nextgram/tree/e3c817dbd80521bde67e066c6a3f99a862b2f081

### To Reproduce

* Run project following README.
* Go to `/`
* Click on `Article Foo` which soft navigates to `/article/foo`


### Describe the Bug

Given this folder structure

```
├── @langSlot
│   ├── article
│   │   └── [...catchAll]
│   │       ├── loading.js
│   │       └── page.js
│   ├── default.js
│   └── page.js
├── article
│   └── [foo]
│       └── page.js
```

Note how `article/` is defined both on the root and inside the @langSlot:

* Soft navigating to `/article/foo` renders `app/@langSlot/page.js`
* Instead it should render `app/@langSlot/article/[...catchAll]/page.js`
* If however I remove the `article/*` folder defined outside @langSlot, `app/@langSlot/article/[...catchAll]/page.js` is rendered correctly. 

### Expected Behavior

Soft navigating to `/article/foo`  should render `app/@langSlot/article/[...catchAll]/page.js` even with `article/*` defined outside the @langSlot

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: svelte
Issue: Flag to wait for out transition to finish before 'in' start
Labels: transition/animation

### Describe the problem

Having an element inside a key tag plays both its in and out transition. I feel most of the time you want them to play after each other and not simultaneously. It can easily be done by setting the delay on the in transition for the duration of the out transition, however when the duration varies for example on the text's length a lot of extra steps are needed to overcome this challange and does not scale at all. 

Example: 
```
{#key random_text}
    <h3 out:typewriter in:typewriter> {random_text} </h3>
{/key}
```



### Describe the proposed solution

An easy solution would be to add a flag to the in transition to wait for the out transition.


### Alternatives considered

Another fix could be to have the old value of the key accessable in the block, then the same calculations could be performed and it would give more flexibility. 

### Importance

would make my life easier
Repository: neovim
Issue: set last search pattern/direction from a Vimscript function
Labels: enhancement,bug-vim

### Problem

It doesn't appear possible to set the `v:searchforward`  variable in a way that persists after a function return:
```vimhelp
v:searchforward			*v:searchforward* *searchforward-variable*
		Search direction:  1 after a forward search, 0 after a
		backward search.  It is reset to forward when directly setting
		the last search pattern, see |quote/|.
		Note that the value is restored when returning from a
		function. |function-search-undo|.
		Read-write.
```
But it is necessary to be able to set this variable in a persistent way in order to write plugins that override search-related actions, such as the `*` and `#` keys, and provide custom implementations for them.

Also, if there are any other such variables with this "automatic revert" behavior, consider giving those the same treatment.

### Expected behavior

Some (new?) API for setting the `v:searchforward` variable in a way that persists after the return of the function that sets it.

Note I am not suggesting that we change current behavior; I am merely suggesting that we add a new API method that does the new thing, preserving backward compatibility.
Repository: stable-diffusion-webui
Issue: [Feature Request]: saving prompts in localStorage to prevent losing it on accidental tab\window\browser closing
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

Saving prompts to localStorage

### Proposed workflow

Workflow 1: using debounce-like callbacks via setTimeout to save prompts input by handling onChange events

Workflow 2: saving latest, or 3-5 latests prompts into localStorage on "Generate" button press

### Additional information

I didn't found anything similar via searching issues on github, so if there is a solution for this already just link it, it would be very useful for me. Thanks in advance!
Repository: godot
Issue: When exporting for iOS, simulator options doesn't appear to run the app (II)
Labels: bug,platform:ios,topic:porting,topic:export

### Godot version

4.1.stable

### System information

MacOS - Ventura 13.1 - Godot 4.1.stable - XCode 14.3.1

### Issue description

Exactly what happened on this issue: https://github.com/godotengine/godot/issues/44681 but it is closed and I am not allowed to open it again, so I am forced to create a new one

As in the original issue: 
"If i export a project in Godot for iOS, the XCode doesn't let me test on Simulator, but when i make a new project in XCode it appears letting me thinking its a issue of Godot"

![Screenshot 2023-07-15 at 16 40 00](https://github.com/godotengine/godot/assets/23043/595b428a-c0a1-4466-b1b5-6117d808c45d)

I tried different Build Settings as in the original thread are suggested:

![Screenshot 2023-07-15 at 16 34 59](https://github.com/godotengine/godot/assets/23043/3a206f25-ca13-4a98-ab50-b7e15b41addb)
![Screenshot 2023-07-15 at 16 28 39](https://github.com/godotengine/godot/assets/23043/1d6d0041-1709-402b-9d3f-06d83d8c8010)

Neither work for me.

This is my export config:

![Screenshot 2023-07-15 at 16 34 03](https://github.com/godotengine/godot/assets/23043/b44a7b5d-1ab5-40b2-9193-91ca7ab29abd)




### Steps to reproduce

Create a simple project and export it to iOS. Open the .`xcodeproj` file.



### Minimal reproduction project

[godot_4_1_test.zip](https://github.com/godotengine/godot/files/12061898/godot_4_1_test.zip)