sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: Pad line on `vim.api.nvim_buf_set_text` just like in virtualedit=all
Labels: enhancement,api

### Problem


https://github.com/neovim/neovim/assets/61395246/2bac3213-cf6c-4f1b-a71c-0c1b9f514cd2



### Expected behavior

I am looking at submitting a PR to make the behavior of `vim.api.nvim_buf_set_text` identical to the normal behavior expected when adding text in `set va=all`.
I see a lot of plugins constantly "padding"  their characters when inserting them in a column position that is not "allocated" to the line yet.
And i think its a shame since the behavior of the editor when setting text at that `col` is as expected, to add the text where its supposed to ,silently  padding it.

Before i start i would like some feedback, and more importantly if this PR would be welcomed by the maintainers, and if not why ?
Repository: go
Issue: proposal: log: support millisecond timestamp resolution
Labels: Proposal

I would suggest that alongside microsecond or second resolution Go log library would also have millisecond timestamp resolution.

Existing implementation has only microsecond or second resolution, but microsecond resolution could be seen as too precise (access to logs could be used for help with side channel attacks) while second resolution is not precise enough, at least for me, to grasp the evolution of events when many happen at the same time.

This would add the `Lmilliseconds` flag.

I have made draft of the implementation here https://go-review.googlesource.com/c/go/+/495298 and it seems pretty minimal (https://github.com/golang/go/pull/60246).
Repository: youtube-dl
Issue: Slow extraction speed for Youtube video urls
Labels: question

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

I'm using youtube-dl only to extract video urls from youtube, it's extremely slow (takes up to 30secs to extract the urls) for a while now. I've also checked the open issues, one was talking about that but the final conclusion was it won't be fixed and yt-dlp could be used. I agree yt-dlp is much faster (takes maybe 3sec to get a URL), any chance we can get such modifications used on yt-dlp also on youtube-dl?
yt-dlp is no alternative for me as I'm fixed to a system which still uses Python 2.7
Repository: material-ui
Issue: [RFC] Remove `variant` prop in NativeSelect
Labels: component: select,package: material-ui,v6.x,RFC

### What's the problem? 🤔

The `variant` prop in the Native Select does not apply any variant related styles like for the other components, such as Select or TextField. 

I see that the NativeSelect is build to have a smaller bundle size if you don't need many styles. See https://github.com/mui/material-ui/issues/20436#issuecomment-609995110.

Developers are getting confused as to why it is not working. See the multiple issues raised:

- https://github.com/mui/material-ui/issues/36787
- https://github.com/mui/material-ui/issues/20436
- https://github.com/mui/material-ui/issues/32197

I believe that providing an alternative solution like in https://github.com/mui/material-ui/issues/32197#issuecomment-1110834687 even though `variant` prop is listed in the [NativeSelect API docs](https://mui.com/material-ui/api/native-select/) does not look good. The question that arises is: what is the use of the variant prop?

### What are the requirements? ❓

_No response_

### What are our options? 💡

As an alternative, have proper styles based on the variant prop.

### Proposed solution 🟢

I propose simply removing the variant prop and adding the documentation on how to support the different variants by providing a custom component using the `input` prop. This is a breaking change, so it should be done in the next major release.

If I am not missing something, the styles applied as shown below based on the variant seem irrelevant for the variant values (standard, outlined, filled):
https://github.com/mui/material-ui/blob/0c58832b6e182f782e73b118ed9681055db3e249/packages/mui-material/src/NativeSelect/NativeSelectInput.js#L57-L70.

Why are there padding and border radius styles? I guess we can remove them.

### Resources and benchmarks 🔗

Also raised by @cherniavskii  in https://github.com/mui/material-ui/issues/20436#issuecomment-1040097605

Related issues:
- https://github.com/mui/material-ui/issues/36787
- https://github.com/mui/material-ui/issues/20436
- https://github.com/mui/material-ui/issues/32197
Repository: godot
Issue: Label3D sometimes becomes invisible in editor
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

4.0.2

### System information

Windows 11

### Issue description

I have a 3D scene with a PlaneMesh, with a Label3D slightly above the mesh. When moving the view around in the editor, the text of the label sometimes disappears. It seems to happen more when zooming close to the label, and when approaching it from an angle < 90 degrees. 


https://github.com/godotengine/godot/assets/220468/0af5a9fb-c270-402c-b3cf-a5664f9e414f



### Steps to reproduce

Make a project and add the included scene. Move the view around in the editor, similar to what is shown in the video.
 

### Minimal reproduction project

Here is a scene showing the bug.

[LabelBug.zip](https://github.com/godotengine/godot/files/11496629/LabelBug.zip)
Repository: next.js
Issue: _next/data/* URLs throwing 404, for multiple Next.js apps running on the same domain
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: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.12.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.4.2
      eslint-config-next: 13.4.2
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

-

### To Reproduce

We still use the Routes Router approach in our apps, and the apps are containerised and running on the same domain, like:

domain: example.com

- app1 routes: 
  - /about
  - /contact

- app2 routes:
  - /shop
  - /basket

Under the same domain we have these URLs:
- example.com/about
- example.com/contact
- example.com/shop
- example.com/basket

Some of these pages are using SSR.

We set the `assetPrefix` for the static content in the `next.config`, so those easily can be mapped in Cloudflare and handled in the config with rewrite rule, like:
- app1:
  - `assetPrefix: 'app1/'`
  - rewrite rule in the config:
      ```
      {
          source: '/app1/:path*`,
          destination: '/:path*'
      }
      ```

  - Cloudflare:
     - request: example.com/about
     - fetch from: example.com/app1/about

- app2:
  - `assetPrefix: 'app2/'`
  - rewrite rule in the config:
      ```
      {
          source: '/app2/:path*`,
          destination: '/:path*'
      }
      ```

  - Cloudflare:
     - request: example.com/shop
     - fetch from: example.com/app2/shop



### Describe the Bug

In the browser, we have 404 errors like this:
- `https://example.com/next/data/<build-id>/about.json`
- `https://example.com/next/data/<build-id>/shop.json`

The issue is that there is no data fetch request path URL prefix option in the `next.config`. As a result, we cannot prefix the next server requests. Therefore, we cannot differentiate and map those requests to the right app/container.

### Expected Behavior

The Next.js should have a prefix option as it has for assets. It could be like `nextServerPrefix` or something like that, and it should be an empty string by default. Then we could set our prefix similarly to the `assetPrefix`, and the calls would look like these then:

- `https://example.com/app1/next/data/<build-id>/about.json`
- `https://example.com/app2/next/data/<build-id>/shop.json`

I found an article from 2021, so it looks like it is not a new issue, unfortunately. We have the same problem now as I described above:
https://arihantverma.com/posts/2021/07/18/workaround-nextjs-data-urls-same-domain-multiple-apps/



### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: next.js
Issue: DraftMode __prerender_bypass cookie SameSite LAX instead of None
Labels: linear: next

### 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: x64
      Version: Darwin Kernel Version 22.3.0: Thu Jan  5 20:53:49 PST 2023; root:xnu-8792.81.2~2/RELEASE_X86_64
    Binaries:
      Node: 18.7.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.3-canary.1
      eslint-config-next: 13.1.6
      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/fromthemills/nextjs-draft-bug

### To Reproduce

Start the app `npm run dev`

Visit `https://localhost:3000/api/draft`

Check the set-cookie header in network tab.

### Describe the Bug

When activating draft mode the `__prerender_bypass` cookie is set to `SameSite=lax` which prevents a visuals CMS to set the cookie as part of an iFrame. The old preview mode set the cookie to `SameSite=None`

![Screenshot 2023-05-17 at 12 24 37](https://github.com/vercel/next.js/assets/7573464/66d88081-b834-4019-b710-0d4d69eeffe1)


New cookie: 
```
__prerender_bypass=...; Path=/; HttpOnly; SameSite=lax
```
Old cookie: 
```
__prerender_bypass=...; Path=/; HttpOnly; Secure; SameSite=None
```

### Expected Behavior

`SameSite=None` like the old cookie

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

_No response_

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

_No response_

<sub>[NEXT-1472](https://linear.app/vercel/issue/NEXT-1472/draftmode-prerender-bypass-cookie-samesite-lax-instead-of-none)</sub>
Repository: go
Issue: crypto: test that BoringCrypto is actually used
Labels: Testing,NeedsInvestigation

#58803 is about BoringCrypto not being used for generating 4096-bit keys. In general, we don't have tests that check that BoringCrypto is actually used (when enabled) instead of Go crypto for operations that are in scope.

This is somewhat tricky to test. @rolandshoemaker suggested using the BoringCrypto counters.
Repository: go
Issue: all: unrecognized failures on `plan9/386`
Labels: OS-Plan9,NeedsInvestigation

```
#!watchflakes
default <- goos == "plan9" && goarch == "386"
```

(attn @golang/plan9)
Repository: go
Issue: all: unrecognized failures on `plan9/amd64`
Labels: OS-Plan9,NeedsInvestigation

```
#!watchflakes
default <- goos == "plan9" && goarch == "amd64"
```

(attn @golang/plan9)
Repository: go
Issue: net: frequent `TestTCPListener` failures on `linux-amd64-wsl`
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net" && test == "TestTCPListener" && builder ~ `.*-wsl`
```

(attn @golang/wsl; CC @qmuntal @ianlancetaylor @neild)
Repository: go
Issue: net/http: frequent timeouts on `linux-amd64-wsl` with goroutines blocked in `checkConnErrorWriter.Write`
Labels: NeedsFix

```
#!watchflakes
post <- builder ~ `.*-wsl` && log ~ `test timed out` && log ~ `^net/http.checkConnErrorWriter.Write`
```

(attn @golang/wsl; CC @qmuntal @neild)
Repository: stable-diffusion-webui
Issue: [Bug]: txt2img API Requests regularly fail 
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

Since upgrading to the latest automatic release, we are experiencing an issue when running requests against the API.

### Steps to reproduce the problem

1. Install Automatic
2. Run many requests against the txt2img API

### What should have happened?

Previously we saw failures almost never.

### Commit where the problem happens

1.2.1 or earlier

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

Linux

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

Google Chrome

### Command Line Arguments

```Shell
python webui.py --xformers --ckpt /workspace/stable-diffusion-webui/v1-5-pruned-emaonly.ckpt --opt-split-attention --listen --enable-insecure-extension-access --api
```
```


### List of extensions

ControlNet

### Console logs

```Shell
88%|████████▊ | 44/50 [00:04<00:00,  9.30it/s]Exception in callback H11Protocol.timeout_keep_alive_handler()
handle: <TimerHandle when=5173939.370990578 H11Protocol.timeout_keep_alive_handler()>
Traceback (most recent call last):
  File "/workspace/stable-diffusion-webui/venv/lib/python3.10/site-packages/h11/_state.py", line 249, in _fire_event_triggered_transitions
    new_state = EVENT_TRIGGERED_TRANSITIONS[role][state][event_type]
KeyError: <class 'h11._events.ConnectionClosed'>
```
```


### Additional information

_No response_
Repository: go
Issue: cmd/compile/internal/test: TestIntendedInlining failures
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
post <- pkg == "cmd/compile/internal/test" && test == "TestIntendedInlining"
```

Issue created automatically to collect these failures.

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

    --- FAIL: TestIntendedInlining (63.02s)
        inl_test.go:340: sync.OnceFunc was not inlined: unhandled op DEFER


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: stable-diffusion-webui
Issue: [Bug]: Prompt parser incorrectly tokenizes punctuation, new lines and embedded weights
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

There are several parser bugs that were uncovered and fixed in the vladmandic fork of A1111. A discussion of the impact of the changes can be found here:

[https://github.com/vladmandic/automatic/discussions/1005](https://github.com/vladmandic/automatic/discussions/1005)



### Steps to reproduce the problem

Documented in the provided link.

### What should have happened?

Documented in the provided link.

### Commit where the problem happens

89f9faa

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

_No response_

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

_No response_

### Command Line Arguments

```Shell
No
```


### List of extensions

N/A

### Console logs

```Shell
N/A
```


### Additional information

_No response_
Repository: go
Issue: proposal: x/tools/cmd/stringer: add -trimsuffix
Labels: Proposal

**x/tools/cmd/stringer has -trimprefix option and should add a matching -trimsuffix option.**

stringer's help would then look like:

```diff
Usage of stringer:
	stringer [flags] -type T [directory]
	stringer [flags] -type T files... # Must be a single package
For more information, see:
	https://pkg.go.dev/golang.org/x/tools/cmd/stringer
Flags:
  -linecomment
    	use line comment text as printed text when present
  -output string
    	output file name; default srcdir/<type>_string.go
  -tags string
    	comma-separated list of build tags to apply
  -trimprefix prefix
    	trim the prefix from the generated constant names
+  -trimsuffix suffix
+    	trim the suffix from the generated constant names
  -type string
    	comma-separated list of type names; must be set
```

stringer should exit with an error if the -trimprefix and -trimsuffix flags appear simultaneously, so that we don't need to think about an ordering like -trimprefix=ab -trimsuffix=bc for an input "abc". Also, giving a constant identifier both a prefix and a suffix is not something you ever see.

### Rationale

From an unscientific code search, most Go "enum"-like constants take the form:

```
type Type int
const (
    Foo = Type(iota)
    Bar
    ...
)
```

or

```
type Type int
const (
    TypeFoo = Type(iota)
    TypeBar
    ...
)
```

However, less commonly but still not uncommonly, you see

```
type Type int
const (
    FooType = Type(iota)
    BarType
    ...
)
```

e.g. even in the stdlib (admittedly these don't have a String() method anyway):

* [sort uses the "Hint" suffix](https://github.com/golang/go/blob/54031132c87931d7a5844a1ce05e637b03703c38/src/sort/sort.go#L54)
* [Unicode uses the "Case" suffix](https://github.com/golang/go/blob/54031132c87931d7a5844a1ce05e637b03703c38/src/unicode/letter.go#L71)
* [http/cookie uses the "Mode" suffix](https://github.com/golang/go/blob/54031132c87931d7a5844a1ce05e637b03703c38/src/net/http/cookie.go#L52)
* [flag uses the "OnError" suffix](https://github.com/golang/go/blob/54031132c87931d7a5844a1ce05e637b03703c38/src/flag/flag.go#L379)

Sometimes it's clearly more natural e.g. "FragmentShader" vs "ShaderFragment", "UpperCase" vs "CaseUpper".

There are advantages to using a prefix everywhere, but this is not to argue which is better, merely that the suffix form exists.

While there's probably some mileage in extracting the stringer into a library that can build a custom stringer command that can arbitrarily rewrite names, this is not that proposal. The stringer command itself should probably not be made any more complicated than this.
Repository: PowerToys
Issue: FancyZones: Please allow to drag MAXIMIZED windows!
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Hello, I love FancyZones, except one extremely annoying thing:

It's not possible to drag a maximized window into a zone :-( 

You have to
- un-maximize it
- sometimes change size to allow dragging title bar
- drag it into a fanzy zone

Would be great if you could fix this issue!
Thx Florian

### Scenario when this would be used?

Whenever there's a maximized windows to be dragged into a fancy zone.

### Supporting information

_No response_
Repository: PowerToys
Issue: Fancy Zones not working for single app
Labels: Issue-Bug,FancyZones-Dragging&UI,Product-FancyZones,Needs-Triage,Area-App Compat

### Microsoft PowerToys version

0.69.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

I downloaded the ZIP version of https://github.com/qarmin/czkawka, v5.1.0, and ran it. The program runs fine, but if I hold down shift while dragging, nothing happens. When I do that with every other app, I get the expected behavior.

### ✔️ Expected Behavior

I'm expecting to see the zones and them to change color as I move and then for the window to resize when I release the mouse.

### ❌ Actual Behavior

Nothing. The window doesn't resize and the zones don't show.

### Other Software

I also have installed Dell Display Manager v2.1, but even when I close this I get the same behavior.

FWIW, DDM seems the have a strange behavior with this app when it is running. I have "Easy Arrange" disabled, but when I drag this window, and DDM is running, the Easy Arrange overlay shows up to try to get me to pick a layout in which to drop Czkawka, but even if I do, it doesn't resize the window. The disabling of "Easy Arrange" is obeyed for every other app on the system. So, there is clearly a problem with this app's response to windowing commands, but maybe Fancy Zones can work around it?
Repository: node
Issue: ibmi: test.parallel.test-http-pipeline fails
Labels: ibm i

I ran this test **BEFORE** applying this [patch](https://patch-diff.githubusercontent.com/raw/nodejs/node/pull/47038.patch) on IBM i, AIX, and Linux. The following were my results:

## IBM i

```sh
$ NODE_DEBUG=net,http,timers ./node test/parallel/test-http-pipeline-flood.js
...

HTTP 388536: write ret = true
HTTP 388536: outgoing message end.
HTTP 388536: SERVER socketOnParserExecute 65535
HTTP 388536: pause parser
NET 388536: _onTimeout
NET 388536: SERVER _emitCloseIfDrained
NET 388536: SERVER handle? false   connections? 1
NET 388536: _onTimeout
```

## AIX

```sh
$ NODE_DEBUG=net,http,timers ../node-v18.15.0-aix-ppc64/bin/node test/parallel/test-http-pipeline-flood.js

...

HTTP 12779906: write ret = true
HTTP 12779906: outgoing message end.
HTTP 12779906: SERVER socketOnParserExecute 32768
HTTP 12779906: pause parser
NET 12779906: _onTimeout
NET 12779906: destroy
NET 12779906: close
NET 12779906: close handle
NET 12779906: has server
NET 12779906: SERVER _emitCloseIfDrained
NET 12779906: SERVER handle? true   connections? 0
NET 12779906: emit close
HTTP 12779906: server socket close
NET 12779906: SERVER _emitCloseIfDrained
NET 12779906: SERVER: emit close

```


## Linux

```sh
$ NODE_DEBUG=net,http,timers node test/parallel/test-http-pipeline-flood.js
...

HTTP 35447: write ret = true
HTTP 35447: outgoing message end.
HTTP 35447: SERVER socketOnParserExecute 65464
HTTP 35447: pause parser
NET 35447: _onTimeout
NET 35447: destroy
NET 35447: close
NET 35447: close handle
NET 35447: has server
NET 35447: SERVER _emitCloseIfDrained
NET 35447: SERVER handle? true   connections? 0
NET 35447: emit close
HTTP 35447: server socket close
NET 35447: SERVER _emitCloseIfDrained
NET 35447: SERVER: emit close
```

The main difference is that on IBM i destroying and closing the client socket doen't happen after the timeout:

```
NET 35447: _onTimeout
NET 35447: destroy
NET 35447: close
NET 35447: close handle
```

Instead the timeout gets called a second time and the server just hangs until the test runner times out.

After Applying this patch the output on IBM i is:

```sh
HTTP 388626: write ret = true
HTTP 388626: outgoing message end.
HTTP 388626: SERVER socketOnParserExecute 65535
HTTP 388626: pause parser
NET 388626: _onTimeout
NET 388626: destroy
NET 388626: close
NET 388626: close handle
NET 388626: has server
NET 388626: SERVER _emitCloseIfDrained
NET 388626: SERVER handle? true   connections? 0
NET 388626: SERVER _emitCloseIfDrained
NET 388626: SERVER: emit close
NET 388626: emit close
HTTP 388626: server socket close
```

Any Ideas on how we can get this to work properly without having to call closeAllConnections?

_Originally posted by @abmusse in https://github.com/nodejs/node/issues/47038#issuecomment-1464444028_
Repository: material-ui
Issue: [TextField] Make fullWidth the default on form element?
Labels: discussion,breaking change,waiting for 👍,component: text field,package: material-ui,package: joy-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Coming from https://github.com/marmelab/react-admin/issues/8796, it seems it's common for UI libraries to set `fullWidth={true}` as the default behavior (see benchmark). Maybe we should do the same for MUI's open-source projects.

<img width="239" alt="Screenshot 2023-05-17 at 18 21 35" src="https://github.com/mui/material-ui/assets/3165635/4f0d2ba0-386b-4b48-ada7-aadd85a2f70e">

https://stackblitz.com/edit/react-ts-fbuqu9?file=App.tsx

An alternative option would be to set a consistent `min-width` CSS property on all the inputs. However, it would be surprising to override, so unlikely to fly.

### Examples 🌈

- https://getbootstrap.com/docs/5.3/forms/form-control/
- https://ant.design/components/input
- https://chakra-ui.com/docs/components/input/usage
- https://sancho-ui.com/components/form/#input
- https://baseweb.design/components/input/
- https://seek-oss.github.io/braid-design-system/components/TextField
- https://balance.reckon.com/package/text-input
- https://tailwindui.com/components/application-ui/forms/input-groups

### Motivation 🔦

In most of the time, as a developer, you need to set a width to an input element. Sometimes, it's `width: 100%`, sometimes, it's not, but it's almost never the default value. So maybe we should make this breaking change.