sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: doc: "Named result parameters" section in effective_go.html is less clear than Go specification
Labels: Documentation,NeedsInvestigation

### What version of Go are you using (`go version`)?
<pre>
$ go version
go version go1.15.3 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/boguslawwojcik/Library/Caches/go-build"
GOENV="/Users/boguslawwojcik/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/boguslawwojcik/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/boguslawwojcik/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.15.3/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.15.3/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/02/6gpzvgbx5pq4rl60g0spdbvw0000gn/T/go-build215540397=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

Run following code

```
package main

import (
	"fmt"
	"time"
)

func main() {
	val := foo()
	fmt.Printf("Main: %+v\n", val.Bar) // explicit
	time.Sleep(2 * time.Second)
}

type Foo struct {
	Bar string
}

func foo() (val *Foo) {
	val = &Foo{Bar: "named"}
	go func() {
		time.Sleep(time.Second)
		fmt.Printf("Goroutine: %+v\n", val.Bar) // explicit
	}()

	val2 := &Foo{Bar: "explicit"}

	return val2
}
```

### What did you expect to see?

`Main: explicit
Goroutine: named`

### What did you see instead?

`Main: explicit
Goroutine: explicit`

While I expect this is intended albeit slightly unintuitive behavior, the [documentation](https://golang.org/doc/effective_go.html#named-results) says _named results are initialized and tied to an unadorned return_ which presupposes that an explicit return *is not tied*. I humbly propose to alter the documentation to better reflect the actual behavior.
Repository: PowerToys
Issue: Calendar aware app startup
Labels: Idea-New PowerToy

I know I can use the Task Scheduler to make apps start on log-on/startup, but it would be great if that startup was aware of my Calendar to decide if the app should start or not...

A specific and concrete example is that I don't need Microsoft Teams to start on weekends or when I have holidays booked in my calendar!

I've been using some hacks with PowerShell to achieve this, but I think it would be great if we had something internal to deal with it!

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: godot
Issue: OpenGL window not clearing properly, leading to overdraw with the previously drawn pixels
Labels: bug,platform:windows,topic:rendering,needs testing

3.2.3


Windows 10 Home Build 1909
AMD Vega 8 graphics
GLES 3


overdraw with the previously drawn pixels


![Videogif](https://user-images.githubusercontent.com/63819697/96377159-742ed880-1138-11eb-8081-b43fcf544428.gif)


For me if I just use the Engine for an hour or so. it will occur.
Repository: godot
Issue: ScrollContainer doesn't respect _clips_input override
Labels: bug,topic:gui

**Godot version:**
3.2.2.stable.official


**OS/device including version:**
Debian 10


**Issue description:**
ScrollContainer clips input by default and ignores implementations of [`_clips_input`][1].


**Steps to reproduce:**
1. Create a ScrollContainer
2. Disable "Rect > Clip Content" and make it smaller than the full screen (to actually see the clipped content)
3. Fill it with enough buttons for a scroll bar to appear
4. Attach a script to it to disable input clipping:
```
extends ScrollContainer

func _clips_input():
	return false
```
5. Try clicking the buttons that are outside of the ScrollContainer's bounds. They're still not clickable.


**Minimal reproduction project:**
[scrollcontainer_clips_input.zip][2]

---

It's straight-forward to see that this is caused by an override of [`clips_input` in `scroll_container.cpp`][3] that always returns true without consulting the attached script. The [original implementation in `control.cpp`][4] does delegate to the attached script as documented.

My suggestion would be to add the same delegation to the implementation in `scroll_container.cpp`.
```diff
 bool ScrollContainer::clips_input() const {
+	if (get_script_instance()) {
+		return get_script_instance()->call(SceneStringNames::get_singleton()->_clips_input);
+	}
 	return true;
 }
```

[1]: https://docs.godotengine.org/en/stable/classes/class_control.html#class-control-method-clips-input
[2]: https://github.com/godotengine/godot/files/5397991/scrollcontainer_clips_input.zip
[3]: https://github.com/godotengine/godot/blob/3.2.3-stable/scene/gui/scroll_container.cpp#L35
[4]: https://github.com/godotengine/godot/blob/3.2.3-stable/scene/gui/control.cpp#L683
Repository: youtube-dl
Issue: Youtube-dl set sleep-interval as duration of current video on playlist before proceeding to next
Labels: request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2020.09.20. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2020.09.20**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

Would it be possible to have a feature work-around added where video downloads coming from a playlist/collection have a sleep time interval equal to the current video (plus optional randomized buffer)?  

This would allow video downloading to happen in approximately the same time increments as the underlaying videos take to stream a channel or video list, and make it less evident an automated process is performing a capture.  This may be slower but would be less detectable.
Repository: ant-design
Issue: Customizable Timeline.Item label span
Labels: Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
Currently the Timeline.Item label occupies 50% of Timeline right or left space. If I only set the date or time as a label, the space will be wasted much. It's better to have an API that can be used to adjust how much label width.

### What does the proposed API look like?
<Timeline.Item label='2020-01-20' labelSpan={4}>Here is very long text that should occupy more space. Bla bla bla</Timeline.Item>


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Link icon near system icon on taskbar
Labels: Help Wanted,Idea-New PowerToy

## 📝 Shortcuts for cleaners of windows

For years it has been my turn to wander the cleaning and maintenance system for windows. It would be wonderful to have a shortcut directly between the small white icons near audio, wifi and time...

![](https://user-images.githubusercontent.com/22998552/96416266-165dc780-11f0-11eb-9573-3663915c547a.jpg)

thanks

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: create-react-app
Issue: [v4.0.0-98]  url function in sass dont work as expected
Labels: stale,needs triage,issue: bug report

### Describe the bug

Im working on typescript 4.x in react 16.x without any issues.
I decide to install typescript eslint with the new projects `eslint-typescript` + `typescript-parser`
The actual 3.4.3 react-script has a known bug with theses 2 projects because the version is 2.0.1 which are also bug with the rules: `no-use-before-define` 🎉 
To solve this I update react to the nightly `99` which solved the issue with  `no-use-before-define` but I have now a new bug.
the behavior of sass-loader seems change on `background-image: url('/img/logo.jpg')`.  the Url function dont work anymore 🤔 

I dont expect any quick fix. Its eslint, I just remove it, rollback deps and now its working like before.


### Environment

```
  System:
    OS: Windows 10 10.0.19041
    CPU: (4) x64 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
  Binaries:
    Node: 12.18.2 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 44.19041.423.0
    Internet Explorer: 11.0.19041.1
  npmPackages:
    react: 16.13.1 => 16.13.1
    react-dom: 16.13.1 => 16.13.1
    react-scripts: 3.4.3 => 3.4.3
  npmGlobalPackages:
    create-react-app: Not Found
```


### Expected behavior

url function in sass should work as before.

### Actual behavior

url function in sass seems to use relative path from the actual dev scss file not from the run env
Repository: vscode
Issue: Add color customization for editor action icons
Labels: themes,under-discussion,icons-product

<!-- ⚠️⚠️ 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. -->

https://code.visualstudio.com/api/references/theme-color, does not indicate an option to change the color of the top right icons in the tabs row (e.g editor actions). 

see example:

![icons-1](https://user-images.githubusercontent.com/37540903/96443697-aeba7300-1215-11eb-8826-1da65e64f297.png)
![icons-2](https://user-images.githubusercontent.com/37540903/96443749-c4c83380-1215-11eb-8c5d-02f0839afade.png)
Repository: opencv
Issue: Confusion about opencv's distortion model w.r.t Brown–Conrady model
Labels: question (invalid tracker)

As described in https://docs.opencv.org/4.4.0/d4/d94/tutorial_camera_calibration.html:
x_{distorted} = x( 1 + k_1 r^2 + k_2 r^4 + k_3 r^6) 
y_{distorted} = y( 1 + k_1 r^2 + k_2 r^4 + k_3 r^6)
x_{distorted} = x + [ 2p_1xy + p_2(r^2+2x^2)] 
y_{distorted} = y + [ p_1(r^2+ 2y^2)+ 2p_2xy]

But in https://en.wikipedia.org/wiki/Distortion_(optics), Brown–Conrady model:
![image](https://user-images.githubusercontent.com/8348898/96449200-189f4080-1247-11eb-8d1a-a4366a6260b9.png)
![image](https://user-images.githubusercontent.com/8348898/96449247-25239900-1247-11eb-8488-55ae3c911354.png)

the above two models are in two different directions. I'm pretty confused when being told that OpenCV uses Brown–Conrady model for distortion.
Repository: electron
Issue: Parent window is minimized automatically when minimizing one of its child windows
Labels: platform/macOS,bug :beetle:,status/confirmed,10-x-y,has-repro-gist,11-x-y

### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:**
  * 10.1.3
* **Operating System:**
  * macOS 10.15.6

### Expected Behavior
When minimizing a child window, its parent window's state should remain unchanged.

### Actual Behavior
When minimizing a child window, its parent window is minimized automatically.

### To Reproduce

1. Open a terminal and execute the following commands:
```sh
git clone https://github.com/electron/electron-quick-start.git
cd electron-quick-start
npm install
```
2. Append the following code to the `createWindow` function in `main.js`:
```js
new BrowserWindow({
    parent: mainWindow,
    width: 400,
    height: 300
});
```
3. Go back to the terminal and execute `npm start`.
4. Click on the child window's minimize button.

### Additional Information
* When trying to restore both application windows by clicking on the app's task bar icon, nothing happens.
* Right-click the app's task bar icon to open this context menu:
![Context menu](https://i.imgur.com/MBWLuht.png)
When restoring the parent window (by clicking on "Hello world!"), the child window gets restored as well (which is expected), but it becomes inaccessible, i.e. you can no longer focus, close, maximize or minimize it. However, when you restore the child window (by clicking on "electron-quick-start") first, everything is working properly.
* Interestingly, the `minimize` event is not emitted for the parent window when it gets minimized. When restoring the parent window, the `restore` event is not emitted as well.
* The Windows equivalent of this issue seems to be ~#20059~ #38425.
Repository: go
Issue: net/http: TestTransportPersistConnLeak failure on plan9-386-0intro builder
Labels: OS-Plan9,NeedsInvestigation

```
#!watchflakes
post <- goos == "plan9" && pkg == "net/http" && test == "TestTransportPersistConnLeak"
```

[2019-11-05T19:06:28-7e71c9c/plan9-386-0intro](https://build.golang.org/log/587c22919d9f459aa2d64e069b00e7334a0eb417)

```
http.test 1338092: warning: process exceeds 100 file descriptors
--- FAIL: TestTransportPersistConnLeak (2.96s)
    transport_test.go:1619: goroutine growth: 170 -> 322 -> 220 (delta: 50)
    transport_test.go:1620: too many new goroutines
2019/11/05 14:48:14 http: TLS handshake error from 127.0.0.1:55194: EOF
2019/11/05 14:48:14 http: TLS handshake error from 127.0.0.1:57366: EOF
FAIL
FAIL	net/http	114.358s
```

See previously #14887, #14375, #4822, #7237.

CC @0intro @millerresearch @fhs
Repository: deno
Issue: Support vi keyboard shortcuts in the repl
Labels: repl,suggestion

Right now the keybinding layout of the repl is emacs, which is the default in upstream rustyline, but it's configurable.
Preferably we'd be able to parse .inputrc and to do the right thing and be a good unix citizen.
Repository: PowerToys
Issue: [Image Resizer] Option to change quality on the fly
Labels: Idea-Enhancement,Product-Image Resizer

## 📝 Provide a description of the new feature

In Image Resizer, while you can change JPeg quality in the PowerToys Settings, when you right-click a JPeg file and choose "Resize pictures", it does not allow you to change the quality.

It would be nice if I could change this value on the fly. I often want to change the quality depending on the use at that point.

It could be implemented so a change in the context menu would be sticky or not. Most sophisticated would be a check box saying something like "keep change in quality setting" of something.

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.

crutkas; edited description a tad
Repository: material-ui
Issue: [Autocomplete] Add equivalent to openOnFocus for `click` events
Labels: new feature,component: autocomplete

<!-- Provide a general summary of the feature in the Title above -->

<!--
  Thank you very much for contributing to Material-UI by creating an issue! ❤️
  To avoid duplicate issues we ask you to check off the following list.
-->

<!-- Checked checkbox should look like this: [x] -->

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

openOnFocus does not affect what happens when an out-of-focus input is clicked. In the comments of #20286, it was argued that this is by design. As such, I hereby request an equivalent (suggested: `disableOpenOnClick`) prop that disables opening the suggestions on click.

## Motivation 🔦

I had to add this to the embedded TextField
```
          [...]
          onMouseDownCapture={ (e) => e.stopPropagation()}
          [...]
```

<!--
  What are you trying to accomplish? How has the lack of this feature affected you?
  Providing context helps us come up with a solution that is most useful in the real world.
-->
Repository: storybook
Issue: Allow MDX theming
Labels: feature request,addon: docs,mdx

**Is your feature request related to a problem? Please describe**
Styles applied in `preview.js` are applied in the canvas which is perfect, but they're also applied to the MDX docs.
There is no way to style those separately. As a result, I'm losing all default styling of the docs.

**Describe the solution you'd like**
It would be nice to separate the styles applied to the canvas from the styles applied to the docs.
This would allow for fewer side effects from the global styles and normalizing styles.

Once this is done, it would also be nice to have a way to use MDX themes. This would ensure that styles are consistent and flexible.

**Describe alternatives you've considered**
An alternative could be to expose isolated classes to the Markdown generated tags, for example `<h2 class="sbdocs">`.
With these classes exposed, it would be possible to set custom styles that would only apply to the right tags.

**Are you able to assist to bring the feature to reality?**
no
Repository: TypeScript
Issue: Regex-validated string types (feedback reset)
Labels: Suggestion,Awaiting More Feedback

This is a pickup of #6579. With the addition of #40336, a large number of those use cases have been addressed, but possibly some still remain.

**Update 2023-04-11**: Reviewed use cases and [posted a write-up](https://github.com/microsoft/TypeScript/issues/41160#issuecomment-1503653578) of our current evaluation

## Search Terms

regex string types

## Suggestion

Open question: For people who had upvoted #6579, what use cases still need addressing?

Note: Please keep discussion on-topic; moderation will be a bit heavier to avoid off-topic tangents

## Examples

(please help)

## Checklist

My suggestion meets these guidelines:

* [?] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [?] This wouldn't change the runtime behavior of existing JavaScript code
* [?] This could be implemented without emitting different JS based on the types of the expressions
* [?] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [?] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: godot
Issue: Debugger stops working in the main thread when creating additional threads
Labels: bug,topic:gdscript,topic:editor

**Godot version:**
Godot Engine v3.2.3.stable.mono.official


**OS/device including version:**
windows 10 x64


**Issue description:**
The debuger/breakpoints are not working anymore in the main thread when i create and run an additional thread.
I run a scene and set two breakpoints. One before the thread is created and started and one after it.
The first breakpoint works as expected, the debuger holds on this breakpoint and show the current program state
![image](https://user-images.githubusercontent.com/347037/96470966-1d57fa80-122f-11eb-98e4-7b557580cb94.png)

Continue the debuger, the second breakpoint is not reached the old debug info is still shown.
![image](https://user-images.githubusercontent.com/347037/96471017-2e087080-122f-11eb-8edd-aca2f93a53f8.png)
The second print statement is also never executed (if removing the breakpoint it is shown)

The debuger panel shows like is holding on a breakpoint.
You can press step next or continue but nothing happens.
Removing the second breakpoint during the debug session also not helps.
The debuger is in an invalid state and unuseable.

**Steps to reproduce:**
Use the attached project and run the scene.

**Minimal reproduction project:**
[debug_main_thread.zip](https://github.com/godotengine/godot/files/5402943/debug_main_thread.zip)
Repository: rust
Issue: Support changing LLVM options between multiple rustc invocations within the same process
Labels: A-LLVM,C-enhancement,T-compiler

See https://rust-lang.zulipchat.com/#narrow/stream/187780-t-compiler.2Fwg-llvm/topic/Calling.20ParseCommandLineOptions.20twice/near/213808524

[`LLVMRustSetLLVMOptions`](https://github.com/rust-lang/rust/blob/c71248b70870960af9993de4f31d3cba9bbce7e8/compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp#L586) currently ignores all attempts to set the LLVM options after the first. It seems that calling [`cl::ResetCommandLineParser`](https://github.com/llvm/llvm-project/blob/225065b9a8e7ec0479b6ee8334f8fe4d4118f875/llvm/lib/Support/CommandLine.cpp#L2599) first is enough to support reconfiguring the LLVM options.

@rustbot modify labels: +A-llvm +C-enhancement
Repository: go
Issue: x/tools/gopls: improve the UX when the gopls daemon panics
Labels: gopls,Tools

Sometimes gopls panics. Hopefully this is becoming increasingly rare, but by definition panics are unexpected and disruptive to the user experience. vscode-go improves the UX with [special handling](https://github.com/golang/vscode-go/blob/8fc4183e7bb8963c3e7ebaf0696d9fe8f8be87fb/src/goLanguageServer.ts#L1158) to identify and capture panics, but for other editor plugins the disruption can be completly opaque: gopls just stops working.  Particularly when running gopls as a daemon, stderr is often /dev/null, and finding the panicking stack involves re-running the daemon and trying to reproduce the panic.

We can do better, by ensuring that stderr is always captured and doing our best to make it discoverable.  Here is one way to achieve this:

- If os.Stderr is /dev/null:
  - create a tempfile with 0600 permissions (conservative permissions since the caller didn't ask us to do this)
  - Redirect stderr to this temp file (using `syscall.Dup2` for POSIX systems, etc.)
  - defer a cleanup func that redirects back to /dev/null and then deletes the tempfile
- In the daemon, if `os.Stderr` is a normal file, tell the gopls forwarder about it during handshake.
- In the forwarder, track whether "shutdown" or "exit" have been called by the LSP client.  Detect abnormal daemon disconnection when "shutdown" or "exit" *haven't* been called.
- On abnormal exit from the daemon, before closing the client connection, inject a message to the effect of "The gopls daemon exited abnormally. Please check the output at `path/to/stderr` and consider filing an issue at golang.org/issues"

The net effect of this should be that when the gopls daemon panics the deferred cleanup will not run and the temporary stderr will be persisted. Then, the LSP client will get a `ShowMessage` notification explaining what went wrong, and suggesting next steps.

CC @myitcv @leitzler @bhcleek, who might have opinions on this UX as plugin maintainers.