sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: gollvm: runtime/malloc.go, runtime/mgcscavenge.go: error: reference to undefined identifier 'sys.GoosIos' (GCC)
Labels: NeedsFix

Hi.
Automated build, using Github Actions, which uses
> gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

raised these errors:

> /home/runner/work/clang_test_cpu_features/clang_test_cpu_features/clang_test_cpu_features/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/malloc.go:220:51: error: reference to undefined identifier 'sys.GoosIos'
> /home/runner/work/clang_test_cpu_features/clang_test_cpu_features/clang_test_cpu_features/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/malloc.go:220:156: error: reference to undefined identifier 'sys.GoosIos'
> /home/runner/work/clang_test_cpu_features/clang_test_cpu_features/clang_test_cpu_features/llvm-project/llvm/tools/gollvm/gofrontend/libgo/go/runtime/mgcscavenge.go:93:50: error: reference to undefined identifier 'sys.GoosIos'
Repository: opencv
Issue: [Feature Request] - Drawing Shapes; Filled, with Border
Labels: feature,category: imgproc,priority: low

 Currently it is possible to draw shapes either as filled, or as an outline. E.g. Rectangle.  

Would like to request that all the drawing functions allow Filled together with an outline/border (with specified width).   

It is possible to achieve Filled with Outline using multiple calls to the drawing functions, but it would be better if the functions supported it. (The current workaround involved drawing the shape as Filled, then as Outline. This causes 2 function calls, and also caused drawn pixels from the Filled version to be overwritten by the Outline version. Dedicated function support would eliminate this and cause an increase in performance)
Repository: godot
Issue: Colors get converted to linear when using set_shader_param on a shader with render mode `spatial`
Labels: bug,topic:rendering,topic:shaders,topic:3d

Supersedes #44962.

**Godot version:**
3.2.4

**OS/device including version:**
Thinkpad T420, Intel CPU, Linux, GLES3

**Issue description:**
When using `set_shader_param` on a shader in render mode `spatial`, colors get converted to the linear color space. This is not the case when using `canvas_item` shaders.

**Steps to reproduce:**

Create two scenes, one with a MeshInstance and one with a ColorRect:.
Add this shader to the mesh instance:
```glsl
shader_type spatial;

uniform vec4 color;

void fragment() {
	ALBEDO = (color.r - 7.17537531) < 0.000000001 ? vec3(1) : vec3(0);
}
```
And this to the ColorRect:
```glsl
shader_type canvas_item;

uniform vec4 color;

void fragment() {
	COLOR.rgb = (color.r - 7.17537531) < 0.000000001 ? vec3(1) : vec3(0);
}
```
Set the `color` parameter to `Color(7.17537531, 0, 0)` by code. The ColorRect is white, while the MeshInstance is black.

**Minimal reproduction project:**

[shader_param_conversion.zip](https://github.com/godotengine/godot/files/5776460/shader_param_conversion.zip)
Repository: opencv
Issue: [Feature Request] - Drawing Shapes; Filled, with Gradients
Labels: feature,category: imgproc,priority: low

Currently it is possible to draw shapes either as filled, or as an outline. E.g. Rectangle. All colour is a solid single colour.

Would like to request that all the drawing functions allow colours to be a gradient of colours.

This is for _Fills_, and also for _Outlines_.

Multiple gradient types should be supported; e.g. Linear, Radial, Box, Diamond, etc.

Also there should be a _transparency_ value for the overall gradient, and a _blend mode_ the overall gradient.

Blend Modes (description) : [http://en.wikipedia.org/wiki/Blend_modes](http://en.wikipedia.org/wiki/Blend_modes)

Also when creating the actual gradient, each _major_ colour of the gradient should have its colour as well as a transparency value.  So to allow say a black to white gradient, where it also fades more and mode transparent when going to white (thus revealing what is underneath to what it it drawn over).

Also the gradient should allow more than just 2 colours (Start and End colours), i.e. multiple colours. E.g. _Black to White To Back_, or _Red to Green to Blue_.
Repository: go
Issue: x/website: Translate "ref/spec" to other languages
Labels: help wanted,NeedsFix

I propose that translate "ref/spec"  to other languages like a "Tour of Go".
I think it will help people who cannot read English.
Repository: pytorch
Issue: FX call_function does not work if target is a class member function
Labels: triaged,module: fx

## 🐛 Bug

Currently if one has a statement like `tracer.create_proxy('call_function', f, args, kwargs)` where `f` is a class member function, the generated code does not work correctly.

## To Reproduce

As explained in the description:

```
class A:
    def F(): return 1

tracer.create_proxy('call_function', A.F, tuple(), {})
```

## Expected behavior

The generated code should have `f = module_name.A.f()`. But instead it has `f.module_name.f()`


cc @ezyang @SherlockNoMad
Repository: go
Issue: testing: document that directories returned by TB.TempDir should not be accessed after cleanup
Labels: Documentation,help wanted,NeedsFix

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15.5 linux/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="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/howardjohn/.cache/go-build"
GOENV="/home/howardjohn/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/howardjohn/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/howardjohn/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.15"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.15/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/howardjohn/go/src/istio.io/istio/go.mod"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build890005715=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?
```
func TestTest(t *testing.T) {
	d := t.TempDir()
	go func() {
		c := 0
		for {
			ioutil.WriteFile(filepath.Join(d, fmt.Sprint(c)), nil, 0600)
			c++
		}
	}()
	t.TempDir()
}
```

### What did you expect to see?

Test passes. Alternatively, this caveat is sufficiently documented in t.TempDir and/or RemoveAll.

### What did you see instead?

Test fails with: `testing.go:915: TempDir RemoveAll cleanup: unlinkat /tmp/TestTest064788875/001: directory not empty`

This happens about 50% of the time in this case. In the real world scenario I am actually trying to test, it happens about 0.001% of the time, which makes it quite frustrating.

A manual version of t.TempDir which ignores this error passes, for what its worth.
```go
func TestManual(t *testing.T) {
	d, err := ioutil.TempDir("", "test")
	if err != nil {
		t.Fatal(err)
	}
	t.Cleanup(func() {
		if err := os.RemoveAll(d); err != nil {
			if err.(*os.PathError).Op != "unlinkat" {
				t.Errorf("TempDir RemoveAll cleanup: %v", err)
			}
		}
	})
	go func() {
		c := 0
		for {
			ioutil.WriteFile(filepath.Join(d, fmt.Sprint(c)), nil, 0600)
			c++
		}
	}()
}
```

I think I understand why it works this way, and unfortunately I don't see any great options here, so perhaps just some documentation around this is the best path forward.
Repository: PowerToys
Issue: [Run][Service Plugin] Improve UAC
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

## 📝 Provide a description of the new feature


With https://github.com/microsoft/PowerToys/pull/8076 merged there is now a plugin for managing Windows services in PowerToys Run.
As @htcfreek have remarked https://github.com/microsoft/PowerToys/pull/8076#issuecomment-730872281 the UAC "Command Processor" displayed on service start/stop can improved.

![UAC](https://user-images.githubusercontent.com/25966642/103800212-678d9280-504c-11eb-8cdd-c9d8e615db25.png)

Possible solution: use a CLI application as helper instead of calling the CMD https://github.com/microsoft/PowerToys/pull/8076#issuecomment-731352592

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: godot
Issue: in_app_store.mm is swallowing some responses.
Labels: bug,platform:ios,topic:porting

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
3.2.3


**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Any


**Issue description:**
<!-- What happened, and what was expected. -->
https://github.com/godotengine/godot/blob/2abe996414b8b551e69e29461de3ff1bcaf5a28f/modules/inappstore/in_app_store.mm#L230


`godot/modules/inappstore/in_app_store.mm` is ignoring some purchase "result" statuses.  Per [apple's documentation](https://developer.apple.com/documentation/storekit/in-app_purchase/offering_completing_and_restoring_in-app_purchases) there are two additional `SKPaymentTransactionState` that could occur (deferred and purchasing).  When these occur the `default` clause of the switch statement will print out a message but the event  won't be propagated out to the Singleton.

Seeing these events in Godot could be useful in determining how long to wait for a purchase to finish before giving up and assuming there was a timeout.  Also per the [services_for_ios page](https://docs.godotengine.org/en/stable/tutorials/platform/services_for_ios.html):
> Remember that when a call returns OK, the API will always produce an event through the pending_event interface, even if it's an error, or a network timeout, etc. You should be able to, for example, safely block the interface waiting for a reply from the server. If any of the APIs don't behave this way it should be treated as a bug.

Since it is swallowing some responses, I think this should "be treated as a bug".

Although it would be a breaking change, maybe the dictionary response should more closely resemble the [SKPaymentTransaction](https://developer.apple.com/documentation/storekit/skpaymenttransaction) that Apple sends instead of trying to simplify the structure in each case.  For example `type` should always be `purchase` for `SKPaymentTransaction` objects.  Also, instead of `result` it should have `transactionState`.


**Steps to reproduce:**
None really.  You'd have to kick off some tricky situations with XCode and the test StoreKit, which I'm not sure is possible (I've got limited experience with it).  These scenarios may be rare but they will appear in the wild eventually.


**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
None
Repository: PowerToys
Issue: [Run] Result outdated on relaunch
Labels: Issue-Bug,Product-PowerToys Run,Area-User Interface,Priority-3

If **clear the previous query on launch** option is **disabled** when you relaunch PT Run the previous result can be outdated.

Not really related to Service plugin but by the nature of this plugin the problem can be repro.
Originally posted by @enricogior in https://github.com/microsoft/PowerToys/pull/8076#issuecomment-755223340

- ALT + Space
- Search for a service
- Stop/Start the service
- ALT + Space again
- The service status displayed is outdated
Repository: go
Issue: cmd/gofmt: gofmt breaks examples with multline comments as output
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go1.15.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?



### 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="/home/agus/.cache/go-build"
GOENV="/home/agus/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/agus/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/agus/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build854558968=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?
As per the guide ["Testable examples in Go"](https://blog.golang.org/examples), I wrote a test file `example_test.go` inside an empty directory as the following:
```go
package test1_test

import "fmt"

func Example() {
	fmt.Println(1)
	fmt.Println("\t\tA")

	// Output:
/*1
		A*/
}
```
Run `go fmt` and then `go test`:

### What did you expect to see?

```console
$ go test
PASS
ok      _/home/agus/code/bugreproduce/gorunnableexample 0.002s
```
### What did you see instead?

After running `go fmt` ([see on playground](https://play.golang.org/p/cRzB3rntfk2)) , the program becomes: 

```go 
package test1_test

import "fmt"

func Example() {
	fmt.Println(1)
	fmt.Println("\t\tA")

	// Output:
	/* 1
	A*/
}

```
The change of indentation of the line `A*` seems to make the test fail:
```console
$ go test
--- FAIL: Example (0.00s)
got:
1
                A
want:
1
        A
FAIL
exit status 1
FAIL    _/home/agus/code/bugreproduce/gorunnableexample 0.002s
```
## Relevant issues & workarounds: 

https://github.com/golang/go/issues/41980
https://github.com/golang/go/issues/5128#issuecomment-708940093
https://github.com/golang/go/issues/6416

The problem can be worked around by using inline comments (`//`), which don't depend on formatting. This runs ok before and after gofmt:
```go
package test1_test

import "fmt"

func Example() {
	fmt.Println(1)
	fmt.Println("\t\tA")

	// Output:
	// 1
//		A
}
```
However, this isn't satisfactory because it would make very difficult to check output longer that a couple of lines.
Repository: flutter
Issue: Clarify/improve dependOnInheritedWidgetOfExactType documentation?
Labels: framework,d: api docs,P2,team-framework,triaged-framework

## Use case

In a few places in docs for `BuildContext` the following can be found (formatting/newlines mine) (e.g. https://api.flutter.dev/flutter/widgets/BuildContext/dependOnInheritedWidgetOfExactType.html):
```
This method should not be called from widget constructors or from State.initState methods, because those
methods would not get called again if the inherited value were to change. To ensure that the widget correctly
updates itself when the inherited value changes, only call this (directly or indirectly) from build methods,
layout and paint callbacks, or from State.didChangeDependencies.
```
Would it make sense to mention why exactly `initState` is excluded? Does this mean that such methods somehow save which method they were called from, and call them back when necessary? Why doesn't Flutter just call the `build` method of whatever Widget's context the method was called on, why would it try to call the method that the `dependOnInheritedWidgetOfExactType` (or others with the same caveat) method call was made from?
Repository: go
Issue: proposal: expvar: re-export runtime/metrics package statistics
Labels: Proposal

Currently the `expvar` package exports `MemStats` by default, so should it also include `runtime/metrics` keys and values? And if so, how?

As a starting point, I'm going to say that it should, and that it should do it the same way `MemStats` is re-exported: each individual variable isn't discoverable, but the whole `MemStats` struct is treated as one JSON object.

Some of the problems with doing this is that we would need to pick a name that's unlikely to collide with existing users' exported variable names. Another problem is that `runtime/metrics` exposes a lot of data through its histograms, making the default results potentially significantly heavier.

An alternative proposal is to export each individual `runtime/metrics` metric, therefore making them discoverable with `expvar`'s `Do` and `Get`. The names are unlikely to collide given that they contain a "/" and a ":", but simultaneously users of the package may not be prepared to deal with these characters, just based on what the package exports by default.

There's also some friction here where `expvar` seeks to look like and produce JSON, while `runtime/metrics` doesn't align itself with any particular representation. `runtime/metrics.Float64Histogram` is the elephant in the room here. Not a huge deal, but we would just need to pick an appropriate representation for it.

Although the title of this proposal takes a position, I'm personally not strongly invested in any particular change. Instead, I want to get feedback from actual users of `expvar` on what we should do here. It's not clear to me what the best way forward is, including just leaving `expvar` alone.

CC @bcmills @aclements @prattmic
Repository: create-react-app
Issue: create-react-app fails on "empty" vscode docker mounted container (.devcontainer folder)
Labels: needs triage,issue: bug report

### Describe the bug

create-react-app too aggressive when creating a new app about existance of tooling config folders, in this case, ".devcontainer" folder for using vscode to develop inside a docker container.

### Environment
```
  current version of create-react-app: 4.0.1
  running from /home/node/.npm/_npx/4431/lib/node_modules/create-react-app

  System:
    OS: Linux 4.19 Debian GNU/Linux 10 (buster) 10 (buster)
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 14.15.1 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.10 - /usr/local/share/npm-global/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    react: ^17.0.1 => 17.0.1 
    react-dom: ^17.0.1 => 17.0.1 
    react-scripts: 4.0.1 => 4.0.1 
  npmGlobalPackages:
    create-react-app: Not Found
```

NOTE: this is inside a docker image, running on Docker Desktop (windows 10), after launching and mounting the application folder using vscode's "Remote Development" extension.

### Steps to reproduce

1. launch vscode , with "Remote Development" extension installed: https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack
2. using extension:
  2A. launch "open folder in container..." option for extension
  2B. select an empty folder.
  2C. Select container image: "node.js & typescript"; select node version 14 (or later) if prompted.
3. once container has built, and vscode attached, open bash prompt from vscode, and execute create-react-app script to create a new app (in mount folder, E.G: /workspaces/new-app-folder):
  `npx create-react-app . --template typescript`

### Expected behavior

app template created with "create react app" initial code and logic.

### Actual behavior

error message:
```
The directory . contains files that could conflict:

  .devcontainer/
```

### Reproducible demo

Identical situation can be created by simply creating a folder ".devcontainer" having two empty files: Dockerfile and devcontainer.json -- while these files are not empty in the normal test, the contents are irrelevant to the issue.

VSCode uses these files to automatically relaunch the same docker container if it is opened in any subsequent sequence, or on another host with vscode + docker installed.

### Additional notes

In file: https://github.com/facebook/create-react-app/blob/8bf050aa7c16078fed5e51ac8388d6100c29e105/packages/create-react-app/createReactApp.js#L935

there is a list of exceptions to the list of files that are ignored relating to this error.  I was able to get this to succeed by hacking the name listed here, and renaming back after completion, E.G:

```
mv .devcontainer .hg
npx create-react-app . --template typescript
mv .hg .devcontainer
```
Repository: go
Issue: x/net/webdav: moving a locked file fails unless destination is locked
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.15 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Haven't tried, but it doesn't look like the code in question has changed.


### 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="/home/kyle/.cache/go-build"
GOENV="/home/kyle/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/kyle/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/kyle/"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/kyle/src/klarose/golang/net/go.mod"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build211380463=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

While running a webdav server using x/net/webdav, I found that any operations which tried to rename a locked file failed unless the client held a lock on the destination file. This seems wrong.

Reproduction steps:

Compile https://github.com/hacdias/webdav (this uses x/net/webdav as its server).

Run the following:
```
cd $(mktemp -d)
cat > config.yaml <<EOF 
# Server related settings
address: 127.0.0.1
port: 8080
auth: false
tls: false
prefix: /

scope: .
modify: true
rules: []
EOF

webdav -p 8080 --auth=false
```


Download/build/install/etc [cadaver](http://www.webdav.org/cadaver/) (a simple tool for running webdav commands)

Run `cadaver http://localhost:8080`

In its command prompt, run the following commands:

A
```
lock foo.yaml
mv foo.yaml foo.yaml.2
```

Then run:

B
```
lock foo.yaml.2
mv foo.yaml foo.yaml.2
```

### What did you expect to see?

A should have succeeded -- `foo.yaml` shoud be renamed to `foo.yaml.2`:

```
dav:/> lock foo.yaml
Locking `foo.yaml': succeeded.
dav:/> mv foo.yaml foo.yaml.2
Moving `/foo.yaml' to `/foo.yaml.2':  succeeded.

```

### What did you see instead?

A fails, but B succeeds:

```
dav:/> lock foo.yaml
Locking `foo.yaml': succeeded.
dav:/> mv foo.yaml foo.yaml.2
Moving `/foo.yaml' to `/foo.yaml.2':  failed:
412 Precondition Failed
dav:/> lock foo.yaml.2
Locking `foo.yaml.2': succeeded.
dav:/> mv foo.yaml foo.yaml.2
Moving `/foo.yaml' to `/foo.yaml.2':  succeeded.
dav:/> 
```
Repository: bitcoin
Issue: Option to ignore small inputs when internal wallet is building TXes?
Labels: Feature

This is mainly to aid in not sending TXes with a ton of fees due to using a lot of tiny inputs, an option in the config file to tell it to ignore inputs with a value less than X when doing coin selection would be useful.

Then you can do consolidation with manually built TXes or coin control whenever you want specifying lower fees, etc. for them.