sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/perf/storage: support postgres for db
Labels: NeedsInvestigation,FeatureRequest

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.1 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/ccasola/Library/Caches/go-build"
GOENV="/Users/ccasola/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/ccasola/dev/go/pkg/mod"
GONOPROXY=""
GONOSUMDB="*.factset.com"
GOOS="darwin"
GOPATH="/Users/ccasola/dev/go"
GOPRIVATE=""
GOPROXY="http://goproxy.factset.io,https://proxy.golang.org,direct"
GOROOT="/usr/local/opt/go/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/opt/go/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17.1"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/ccasola/dev/goperf/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 -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/7m/kwm3sc350q3c5w3cq0xkm2_hykbkhg/T/go-build265302748=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I'm trying to use the `x/perf/storage` app in an environment that requires postgresql instead of mysql.

### What did you expect to see?

I'd expect postgres to work properly.

### What did you see instead?

The create table statements and some of the queries are not compatible with postgres.

I'd be happy to contribute this change if you are open to supporting postgres in addition to the already supported mysql and sqlite.
Repository: pytorch
Issue: [doc] Can we update TorchScript union support?
Labels: oncall: jit,module: docs

## 📚 Documentation

The [doc](https://pytorch.org/docs/stable/jit_language_reference.html#supported-type) says `typing.Union: "Unlikely to be implemented"`. But as far as I understand this is supported on the main branch. (and released in 1.10. https://github.com/pytorch/pytorch/releases/tag/v1.10.0).

Can we update the documentation? Probably, it's worth noting that union types requires type refinement like optional does.

cc @brianjo @mruberry
Repository: godot
Issue: Per Pixel Transparency does not work from Godot 3.2.2 onward
Labels: bug,platform:windows,topic:rendering,topic:porting,needs testing,regression

### Godot version

3.2.2 and onward

### System information

Windows 10 Not so cool edition

### Issue description

in 3.2.1:
Settings -> Per Pixel Transparency Allowed = true
Settings -> Per Pixel Transparency Enabled = true

Ready func:
func _ready():
	get_viewport().transparent_bg = true;

works like a charm :)
![image](https://user-images.githubusercontent.com/57871912/138515863-1aa196b1-61a0-4dfa-90a9-3af66d7129e2.png)


---------------------------------------------------------------------------------------------------------------------------------------


in 3.2.2:
Settings -> Per Pixel Transparency Allowed = true
Settings -> Per Pixel Transparency Enabled = true

Ready func:
func _ready():
	get_viewport().transparent_bg = true;

works like poop :)
![image](https://user-images.githubusercontent.com/57871912/138516100-f106846b-f922-469f-bc55-67af9eac84f5.png)


I seriously don't know how to explain this better, but here are things that I tried and absolutely did nothing to fix it:

- Changed default environment color to be transparent.
- Changed renderers from 3.0 to 2.0.
- disabled batching since 2D batching was introduced in 3.2.2.
- Banged my head against the wall.

I searched some things, and it might have to do something with this, but I'm not that smart to know https://github.com/godotengine/godot/pull/38629

### Steps to reproduce

in 3.2.2:
Settings -> Display -> Window Per Pixel Transparency Allowed = true
Settings -> Display -> Window Per Pixel Transparency Enabled = true

set up a 2D scene with a godot icon in the middle and have a script with a Ready func like this:
func _ready():
	get_viewport().transparent_bg = true;


### Minimal reproduction project

Be sensitive with it, okay...
[Glass.zip](https://github.com/godotengine/godot/files/7401115/Glass.zip)
Repository: excalidraw
Issue: Stroke options should show keyboard shortcut
Labels: enhancement

One thing that's really nice with the UI is that most of the interactive elements have the keyboard shortcut listed, for example:

<img width="409" alt="image" src="https://user-images.githubusercontent.com/91254/138517722-b676d4ec-e4f7-4327-b3c6-d49a298d3c26.png">

This is really helpful as the number of options in the `(?)` popup makes it easy to miss something.

In my case, I could tell that the color picker was meant to be used with keyboard shortcuts:

<img width="205" alt="image" src="https://user-images.githubusercontent.com/91254/138516166-258c7449-da49-473f-a766-8afc7a8e3483.png">

But I couldn't figure out the keyboard shortcut to open the popup, and my eyes didn't settle on the option I was looking for:

<img width="382" alt="image" src="https://user-images.githubusercontent.com/91254/138516335-483ff136-c703-4a36-8265-781f696a7026.png">

(Funny story: after staring at the `(?)` popup for a while and giving up, I eventually went digging in the source code and Github Issues because I was so sure it was meant to be accessible, and noticed someone mention it in an unrelated issue.)

Some interactive elements have the keyboard shortcut next to it, like the 1-9 buttons at the top of the page, and some of them use a `title` attribute to show on mouse hover, such as the padlock icon which has `— Q` as part of the mouseover text:

```html
<label
  class="ToolIcon ToolIcon__lock ToolIcon_type_floating zen-mode-visibility ToolIcon_size_medium"
  title="Keep selected tool active after drawing — Q"
>
```

The color picker in particular is the one that stumped me, but, since I was in the deep dive mode (procrastinating real work 😅) I looked at a few others that don't show keyboard shortcuts:

- "Toggle dark mode" (the sun/moon button at top right) `cmd+shift+D`
- "Show stroke color picker" `S`
- "Show background color picker" `G`

I think ideally the letter would show next to those, but even a mouseover `title` would be really helpful.

Thanks so much!
Repository: godot
Issue: Camera background environment canvas setting doesn't do anything
Labels: bug,topic:rendering,topic:3d

### Godot version

3.3.3 stable

### System information

Windows 7 64-bit

### Issue description

Setting a camera's enviroment background setting to canvas to render a texture beneath a 3d scene does absolutely nothing and the texture will just render above the 3d camera:
![image](https://user-images.githubusercontent.com/16231628/138527670-a78ee3ed-0105-445d-98f4-2b95e505df27.png)

![image](https://user-images.githubusercontent.com/16231628/138527690-a14d4d2a-fc5b-483d-88e7-27ba5576eba0.png)

![image](https://user-images.githubusercontent.com/16231628/138527681-557b6e30-26a3-4e19-9275-20fd4743e2e3.png)

Instead, what must do is clear the camera environment setting:
![image](https://user-images.githubusercontent.com/16231628/138527764-1f07c5b0-543a-4ab5-b429-da5ee2dbf80f.png)

And add a WorldEnviroment node to the scene, with canvas set as background:
![image](https://user-images.githubusercontent.com/16231628/138527783-106f4d84-af06-4318-9865-fc9bd4c3db06.png)
![image](https://user-images.githubusercontent.com/16231628/138527805-94014c5d-318f-40a2-a942-546cd7fd1dd7.png)

Camera environment settings should do the exact same thing, I've encountered dozens of threads where other users have had the same problem, it took me an hour to figure out what was wrong with my set-up.

### Steps to reproduce

Spend a lot of time putting all of your canvas environment settings directly into the camera's environment settings, then redo it all in a WorldEnviroment node.

### Minimal reproduction project

_No response_
Repository: rust
Issue: Rework reservation impls into an `Ambiguous` trait
Labels: T-compiler,F-negative_impls

From [this comment in #90104](https://github.com/rust-lang/rust/pull/90104#r733958974):

> As a follow-up PR I would like to remove reservation impls and replace them with an (perma-unstable) Ambiguous trait. Then we could replace a reservation impl like 
>
> ```rust
> impl Foo for T
> where
>     T: Ambiguous,
> {
> }
> ```
> 
> We have to double check if this will work though!
Repository: neovim
Issue: Only one tutorial can be loaded at once
Labels: bug,runtime

### Neovim version (nvim -v)

0.5.0

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

N/A

### Operating system/version

CentOS 7.9

### Terminal name/version

xfce4-terminal 0.8.7.4

### $TERM environment variable

tmux-256color

### Installation

system package manager

### How to reproduce the issue

```
nvim -u NORC
:Tutor
:Tutor tutor
```

### Expected behavior

Opening another tutor works fine.

### Actual behavior

```
Error detected while processing function tutor#ApplyMarks[7]..tutor#CheckLine:
line    4:
E158: Invalid buffer name: .
E684: list index out of range: 0
E15: Invalid expression: sign_getplaced('.', {'lnum': a:line})[0].signs
line    5:
E121: Undefined variable: signs
E116: Invalid arguments for function empty
E15: Invalid expression: !empty(signs)
line    4:
E158: Invalid buffer name: .
E684: list index out of range: 0
E15: Invalid expression: sign_getplaced('.', {'lnum': a:line})[0].signs
line    5:
E121: Undefined variable: signs
E116: Invalid arguments for function empty
E15: Invalid expression: !empty(signs)
line    4:
E158: Invalid buffer name: .
E684: list index out of range: 0
E15: Invalid expression: sign_getplaced('.', {'lnum': a:line})[0].signs
line    5:
E121: Undefined variable: signs
E116: Invalid arguments for function empty
E15: Invalid expression: !empty(signs)
line    4:
E158: Invalid buffer name: .
E684: list index out of range: 0
E15: Invalid expression: sign_getplaced('.', {'lnum': a:line})[0].signs
line    5:
E121: Undefined variable: signs
E116: Invalid arguments for function empty
E15: Invalid expression: !empty(signs)
line    4:
E158: Invalid buffer name: .
E684: list index out of range: 0
E15: Invalid expression: sign_getplaced('.', {'lnum': a:line})[0].signs
-- More --
```
Repository: go
Issue: go/types, types2: consolidate error message formats
Labels: NeedsDecision

Error messages don't have a particular "style guide" at the moment:

- there are simple errors of the form: `func main must have no arguments and no return values`
- there are errors with clarifications using a `:`: `undefined: x`
- there are errors with clarifications using a `;`: `cannot make int; type must be slice, map, or channel`
- there are errors with clarifications using parentheses: `cannot slice s (variable of type chan int)`
- there are errors with clarifications on separate lines, indented, possible combined with any of the forms above

Maybe we can come up with a reasonably consistent set of rules for how to format errors (e.g., when to use ':', ';', or parentheses). If we can, that we should be able to encode this for consistent behavior.
Repository: flutter
Issue: backgroundColor for AppBarTheme in SearchDelegate uses hardcoded colors for dark theme.
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

## Use case

Custom app bar custom for dark modes.

## Proposal

Make the value configurable

<img width="832" alt="Screen Shot 2021-10-23 at 8 32 28 AM" src="https://user-images.githubusercontent.com/126065/138540267-e98f3a3e-3e98-4e4e-a8f8-efaa368a97b6.png">
Repository: pytorch
Issue: addition of loss function RMSE in the torch.nn 
Labels: feature,module: nn,module: loss,triaged,actionable

## 🚀 Feature
We  widely use torch.nn.MSEloss in our code ,but for RMSE ,we have to do torch.sqrt() . Rather why don't add torch.nn.RMSEloss 

## Motivation

MSE and RMSE have difference of only a square root but in application the results differ and it makes difference if we use 
MSEloss or RMSEloss 

## Pitch

RMSE is widely used than MSE to evaluate the performance of the regression model,  RMSE is sqrt(Σᵢ (ŷᵢ — yᵢ)² / n ) which works

## Alternatives

I have copied the the MSEloss class from loss.py in torch/nn/modules/loss and returned torch.sqrt(previous return)

```
class RMSELoss(_Loss):
    def __init__(self, size_average=None, reduce=None, reduction: str = 'mean') -> None:
        super(RMSELoss, self).__init__(size_average, reduce, reduction)

    def forward(self, input: Tensor, target: Tensor) -> Tensor:
        return torch.sqrt(F.mse_loss(input, target, reduction=self.reduction))

```



cc @albanD @mruberry @jbschlosser @walterddr
Repository: rust
Issue: LLVM ERROR: example-calendar.rs with dump-mir, -Zpolymorphize and debug assertions
Labels: A-LLVM,I-ICE,E-needs-test,T-compiler,C-bug,requires-nightly,-Zpolymorphize,requires-debug-assertions

<!--
Thank you for finding an Internal Compiler Error! 🧊  If possible, try to provide
a minimal verifiable example. You can read "Rust Bug Minimization Patterns" for
how to create smaller examples.

http://blog.pnkfx.org/blog/2019/11/18/rust-bug-minimization-patterns/

-->

### Code

Note that in order to reproduce this, you need a rustc build with debug assertions enabled!

Code:  https://github.com/rust-lang/rust/blob/master/src/test/ui/impl-trait/example-calendar.rs



### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.58.0-dev
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.58.0-dev
LLVM version: 13.0.0
```

rustc @ 01198792a608b05e624b0127e76dd0753057016c
### Error output

`rustc ./src/test/ui/impl-trait/example-calendar.rs  -Zdump-mir=all -Zpolymorphize=on`
```
Both operands to ICmp instruction are not of the same type!
  %18 = icmp ule %"core::iter::adapters::chain::Chain<core::option::IntoIter<alloc::string::String>, core::iter::adapters::map::Map<core::iter::adapters::map::Map<GroupBy<core::iter::adapters::peekable::Peekable<InGroup<core::iter::adapters::peekable::Peekable<InGroup<core::ops::range::RangeFrom<NaiveDate>, [closure@./src/test/ui/impl-trait/example-calendar.rs:321:12: 321:36], i32>>, [closure@./src/test/ui/impl-trait/example-calendar.rs:403:17: 403:30], u32>>, [closure@./src/test/ui/impl-trait/example-calendar.rs:419:17: 419:45]>, [closure@./src/test/ui/impl-trait/example-calendar.rs:567:18: 567:34]>, [closure@./src/test/ui/impl-trait/example-calendar.rs:488:12: 510:6]>>"* %15, %"core::iter::adapters::chain::Chain<core::option::IntoIter<alloc::string::String>, core::iter::adapters::map::Map<core::iter::adapters::map::Map<GroupBy<core::iter::adapters::peekable::Peekable<InGroup<core::iter::adapters::peekable::Peekable<InGroup<core::ops::range::RangeFrom<NaiveDate>, [closure@./src/test/ui/impl-trait/example-calendar.rs:321:12: 321:36], i32>>, [closure@./src/test/ui/impl-trait/example-calendar.rs:403:17: 403:30], u32>>, [closure@./src/test/ui/impl-trait/example-calendar.rs:419:17: 419:45]>, [closure@./src/test/ui/impl-trait/example-calendar.rs:567:18: 567:34]>, [closure@./src/test/ui/impl-trait/example-calendar.rs:488:12: 510:6]>>.3"* %17
in function _ZN5alloc3vec18source_iter_marker24write_in_place_with_drop28_$u7b$$u7b$closure$u7d$$u7d$17hafca98b87cb714a6E
LLVM ERROR: Broken function found, compilation aborted!
```
Repository: rust
Issue: References to local variables are considered to need dropping if a local variable does
Labels: C-bug,A-const-eval

For example, function `f` is rejected with an error that `a` needs dropping, while `g` succeeds even though it should use more conservative qualification because it uses an opaque function `id`:

```rust
pub const fn id<T>(t: T) -> T { t }

pub const fn f() -> String {
    let s = String::new();
    let mut a: (Option<String>, Option<&String>) = (None, None);
    a.1 = Some(&s);
    s
}

pub const fn g() -> String {
    let s = String::new();
    let mut a: (Option<String>, Option<&String>) = (None, None);
    a.1 = Some(id(&s));
    s
}
```
@rustbot label +A-const-eval +A-const-fn
Repository: TypeScript
Issue: Transforms on functions that have destructured arguments lose parameter names
Labels: Help Wanted,Effort: Moderate,Experience Enhancement

# Suggestion

<!--
  Please fill in each section completely. Thank you!
-->

## 🔍 Search Terms

<!--
  💡 Did you know? TypeScript has over 2,000 open suggestions!
  🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
  The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests

  Replace the text below:
-->

tuple, labels, parameters, destructure

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [x ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [ x] This wouldn't change the runtime behavior of existing JavaScript code
* [ x] This could be implemented without emitting different JS based on the types of the expressions
* [x ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [ x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

When using tuple types to capture function arguments the argument names are lost if any of the arguments are destructured, this leads to a less than ideal situation when trying to determine argument order of primitive types.

## 📃 Motivating Example

```typescript

// trivial exampled
const transform = <T, U extends unknown[]>(
   factory: (...args: U) => T
) : ((...args: U) => T) => factory

const transformed = transform(({ test } : { test: string }, b: string) : string => `${test}:`${b}`)

/* 
The intellisense for the transformed function shows args_0, args_1, the first 
argument clearly has no name, however the second does but is still not shown. If 
all arguments are named then everything works as expected.  I realize this 
is a fairly trivial example, however, it would significantly improve usage of 
transformed functions, particularly if those function have multiple primitive 
arguments whose order could be confused without names. 

Additionally I understand the potential for argument name collision, e.g. 
if argument two was for some reason called args_0, however, I believe this 
case is unlikely and also could be fixed with a numeric suffix which would 
still retain the intent.
*/
```


<!--
  If you were announcing this feature in a blog post, what's a short explanation that shows
  a developer why this feature improves the language?
-->

## 💻 Use Cases

<!--
  What do you want to use this for?
  What shortcomings exist with current approaches?
  What workarounds are you using in the meantime?
-->
Repository: pytorch
Issue: enumerate(..., start=idx) is not working correctly while scripting
Labels: oncall: jit

## 🐛 Bug

Originaly came from [discuss.pytorch.org](https://discuss.pytorch.org/t/slicing-using-tensor-doesnt-work-in-torchscript-as-expected/134875/2). 
It seems that `enumerate(..., start=idx)` is not working correctly while scripting and the start value is ignored:

## To Reproduce

```
def fun():
    for i, idx in enumerate(torch.arange(5), start=1):
        print(i, idx)
fun()

@torch.jit.script
def fun():
    for i, idx in enumerate(torch.arange(5), start=1):
        print(i, idx)
fun()
```

output:
```
1 tensor(0)
2 tensor(1)
3 tensor(2)
4 tensor(3)
5 tensor(4)

0 0
[ CPULongType{} ]
1 1
[ CPULongType{} ]
2 2
[ CPULongType{} ]
3 3
[ CPULongType{} ]
4 4
[ CPULongType{} ]
```

## Expected behavior

The result of torchscript func should be something like
```
1 0
[ CPULongType{} ]
2 1
[ CPULongType{} ]
3 2
[ CPULongType{} ]
4 3
[ CPULongType{} ]
5 4
[ CPULongType{} ]
```

## Environment

```
PyTorch version: 1.10.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 11.4 (x86_64)
GCC version: Could not collect
Clang version: 12.0.5 (clang-1205.0.22.9)
CMake version: Could not collect
Libc version: N/A

Python version: 3.8.12 (default, Oct 13 2021, 06:42:42)  [Clang 13.0.0 (clang-1300.0.29.3)] (64-bit runtime)
Python platform: macOS-11.4-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.21.3
[pip3] torch==1.10.0
[conda] Could not collect
```

## Additional context

<!-- Add any other context about the problem here. -->