sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Date picker with incorrect date separator format
Labels: framework,f: material design,f: date/time picker,a: internationalization,team-design,triaged-design

Originally brought up in https://github.com/flutter/flutter/issues/55535 by @jans-y

Many other languages have the same problem with manual date entering `.`
e.g.: cs, sk, hu -> they all use . (dots) not / (slash)

Switching to 'de' (German) solves the issue.

@darrenaustin also did some research and found that the following might be incorrect as well:

```
af: sep = /, help = dd-mm-jjjj
fr_CA: sep = /, help = jj-mm-aaaa
hy: sep = /, help = օօ.աա.տտտտ
nl: sep = /, help = dd-mm-jjjj
```

I'll file these change requests to the internal translation console for the translation teams to update as appropriate for the locales mentioned above.
Repository: flutter
Issue: [Desktop] Provide Window APIs to show/hide a given window
Labels: c: new feature,framework,a: desktop,P3,team-framework,triaged-framework

Hi. Is it possible to programmatically hide or close a window (not minimize), but still keep the process alive in Flutter Desktop? This is similar to the `hide()`/`show()` methods in Qt and this is the standard approach in order to minimize the app to the tray.
Repository: rust
Issue: CI for deterministic / reproducible builds
Labels: A-testsuite,C-enhancement,T-infra,A-reproducibility

#34902 was finally closed as we got a [positive result on tests.r-b.org](https://tests.reproducible-builds.org/debian/history/rustc.html) for rustc 1.44.1 on Debian Unstable, where we test for build-path-independent reproducibility. However for rustc 1.45.0 the test turned negative again. (The codenamed suites e.g. "bullseye", "buster", only test for build-path-dependent reproducibility, i.e. are less strict / less ideal)

On the same bug report, @jgalenson had reported build-path-independent reproducibility for a configuration closer to rust's own builds, but this also occasionally regresses e.g. #69352.

The Debian builds and rust's own builds are slightly different; the probably-most-significant one being that Debian uses the system LLVM, so that part is excluded from reproducibility tests. Other than that, it is important to set `remap-debuginfo` in `config.toml` as well as `-ffile-prefix-map` and `-fdebug-prefix-map` for the C parts of the build, including in `CFLAGS` / `CXXFLAGS`.

Since many/most contributors are not aware of all of the details needed to retain build-path-independent reproducibility, it would be good to have some CI to ensure this property in the long run. Running a full build twice is costly, but perhaps some other solution would be just as effective, e.g. running a stage1 build twice, or running it for the beta channel, and/or running with a pre-built LLVM.
Repository: pytorch
Issue: build error redefinition of ‘struct c10::complex<T>’ with release v1.6.0
Labels: module: build,triaged


Try to install pytorch v1.6.0 in Ubuntu 16.04 cuda 10 by command 'python setup.py install'.
It returns long error log like:

> ../c10/util/complex.h:127:31: error: redefinition of ‘struct c10::complex<T>’
 struct alignas(sizeof(T) * 2) complex {
                               ^
In file included from ../c10/core/ScalarType.h:4:0,
                 from ../aten/src/ATen/native/DispatchStub.h:4,
                 from ../aten/src/ATen/native/CPUBlas.h:3,
                 from ../aten/src/ATen/native/CPUBlas.cpp:1:
../c10/util/complex_type.h:127:31: error: previous definition of ‘struct c10::complex<T>’
 struct alignas(sizeof(T) * 2) complex {
                               ^
In file included from ../aten/src/ATen/native/CPUBlas.h:4:0,
                 from ../aten/src/ATen/native/CPUBlas.cpp:1:
../c10/util/complex.h: In function ‘constexpr c10::complex<float> c10::complex_literals::operator""_if(long double)’:
../c10/util/complex.h:276:26: error: redefinition of ‘constexpr c10::complex<float> c10::complex_literals::operator""_if(long double)’
 constexpr complex<float> operator"" _if(long double imag) {
                          ^
In file included from ../c10/core/ScalarType.h:4:0,
                 from ../aten/src/ATen/native/DispatchStub.h:4,
                 from ../aten/src/ATen/native/CPUBlas.h:3,
                 from ../aten/src/ATen/native/CPUBlas.cpp:1:
../c10/util/complex_type.h:276:26: note: ‘constexpr c10::complex<float> c10::complex_literals::operator""_if(long double)’ previously defined here

How can build successfully? Thank you ! 

cc @malfet
Repository: PowerToys
Issue: [suggestion] Trimming empty alpha space in png
Labels: Idea-New PowerToy

There's various way to resize images.  
But there's no way to resize by empty alpha space on png.

![image](https://user-images.githubusercontent.com/13521406/89790732-52740c80-db5d-11ea-8dc9-94c102e46234.png)  
![image](https://user-images.githubusercontent.com/13521406/89792339-60c32800-db5f-11ea-807b-215442590404.png)

PowerToys is stands for productivity, so I think this feature would be great for content creators.
Repository: flutter
Issue: PageView : How to change scrolling speed and smoothness
Labels: framework,f: scrolling,d: api docs,P3,team-framework,triaged-framework

Is there any way to increase the speed scroll of a pageView? 
Can we have some documentation on how to do that? 

This is the same question available in StackOverflow for more than one year. 
https://stackoverflow.com/questions/55314932/pageview-how-to-change-scrolling-speed-and-smoothness/62983842#62983842
Repository: TypeScript
Issue: JSDoc property description containing "@" character seems to make everything below this as undefined
Labels: Bug

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

This is an issue with TS typings declarations generated from JSDoc and code analysis

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.8.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** jsdoc property at @ description link markdown

**Code**

```js
/**
 * @typedef SomeTypeDef
 * @property {string} property1
 *   I'm a comment with an [@s](link)
 * @property {boolean} propertyCantBeAccessed
 */

/**
 * @param {SomeTypeDef} s
 */
const f = (s) => {
    s.propertyCantBeAccessed
}

f({
    property1: 'only exists here',
    propertyCantBeAccessed: false
})
```

**Expected behavior:**
The property exists and can be accessed

**Actual behavior:**
Code fails with `Property 'propertyCantBeAccessed' does not exist on type 'SomeTypeDef'`
Repository: pytorch
Issue: Add a guide for what to do when you think there's a memory leak
Labels: high priority,module: docs,module: memory usage,triaged

## 📚 Documentation

Memory leaks are reported relatively frequently but it's often a different issue, e.g. that there's a caching allocator and/or you are doing worst-case allocation (increasing the size each time).  Here's a recent example: https://github.com/pytorch/pytorch/issues/42557.

We should have a guide on how to debug these issues.


cc @ezyang @gchanan @zou3519 @bdhirsh @jlin27 @mruberry
Repository: pytorch
Issue: Can't registered boxed kernel for operator that doesn't support boxing
Labels: triaged,module: dispatch

## 🐛 Bug

From https://github.com/pytorch/pytorch/pull/42617#discussion_r467124816, I wanted to register a kernel that would raise an error message for certain operators. The use case is to blocklist certain operators from running when a certain dispatch key is enabled.

One such example of a kernel that raises an error is the `CppFunction::makeNamedNotSupported()` kernel. However, when I tried to register `CppFunction::makeNamedNotSupported()` for an operator (e.g., `abs_`) that doesn't have `use_c10_dispatcher: full`, it raised a pretty cryptic [error message](https://gist.github.com/zou3519/da6426806e82c3cac3f78c7671c44200). Is it possible to support that or does one have to wait until all native operations have `use_c10_dispatcher: full`?

## To Reproduce

See minimum repro in https://github.com/pytorch/pytorch/pull/42817


## Environment
master

cc some composability folks: @bhosmer @ezyang @smessmer
Repository: flutter
Issue: Add option to disable splash screen transition on iOS
Labels: c: new feature,platform-ios,a: existing-apps,P2,team-ios,triaged-ios

iOS by default re-displays the splash screen while the engine draws its first frame. Add a flag on FlutterViewController to disable this mechanism. This is useful for add-to-app cases etc.
Repository: node
Issue: FileHandle don't allow close while writing/reading
Labels: fs

I think I've brought up something similar in the past. Regarding the data race issue with closing file descriptions while they are actively used.

I believe we could enforce this through `FileHandle` and possibly deprecating non `FileHandle` based fs ops?

i.e. move the `kIsPerformingIO` logic from fs streams up one level.
Repository: angular
Issue: Template type-checker: enable `strictInputAccessModifiers` by default
Labels: feature,area: compiler,compiler: template type-checking

# 🚀 feature request

### Relevant Package
@angular/compiler-cli

### Description
PR #38249 adds the compiler option `"strictInputAccessModifiers"` which causes the template type checker to honor `private`/`protected`/`readonly` modifiers and reports an error when assigning into it. This option is currently disabled by default.

This issue tracks the effort as enabling this option by default in a future major version of Angular.

Related: #30981
Repository: pytorch
Issue: torch/library.h doc rendering issue
Labels: module: docs,triaged

https://pytorch.org/cppdocs/api/file_torch_library.h.html code block renders wrong

cc @jlin27
Repository: pytorch
Issue: Undocumented parameters in the Variables section of the recurrent bidirectional layers regarding the backward pass
Labels: module: docs,triaged

## 📚 Documentation

In the [docs](https://pytorch.org/docs/stable/generated/torch.nn.RNN.html) (the same applies to LSTM and GRU) in case of the reccurent **bidirectional** layer, it is not mentioned that there is an additional set of parameters suffixed with `_reverse` that are used in the backward pass:
(k represents the layer)
* `weight_hh_l[k]_reverse` 
* `weight_ih_l[k]_reverse` 
* `bias_hh_l[k]_reverse`
* `bias_ih_l[k]_reverse`

In my opinion, it makes sense to have them documented so the user can easily access them and e.g. apply his own initialization procedure.

cc @jlin27
Repository: flutter
Issue: ThemeData default ColorSchemes primary/onPrimary contrast is insufficient
Labels: framework,f: material design,a: accessibility,a: quality,team-design,triaged-design

The [color schemes](https://api.flutter.dev/flutter/material/ColorScheme-class.html) for the current default themes, ThemeData.light() and ThemeData.light(), do not have sufficient primary/onPrimary or primary/surface contrast.

By default, TextButton and OutlineButton use the primary color for the foreground (text/icon) with a transparent background. The transparent background typically reveals a surface colored background.

By default, ElevatedButton uses the onPrimary color for its foreground (text/icon) and the onPrimary color for its filled background.

The table below shows the value of four ColorScheme colors for the default light and dark themes, and the dark and light themes created with `ThemeData.from(colorScheme: ColorScheme.light())`
and `ThemeData.from(colorScheme: ColorScheme.dark())`.

The last two columns link to the WCAG 2.0 a11y contrast ratio for TextButton (likewise for OutlineButton), and ElevatedButton, for all four color schemes. The contrast ratio in all cases is (for a font size of 14) must be greater than 4.5.  The default ThemeData.light() and ThemeData.dark() themes fail for all button types.


| Theme               | primary | onPrimary | surface | onSurface | TextButton | ElevatedButton |
| ------------------- | ------- | --------- | ------- | --------- | ---------- | -------------- |
| ThemeData.light()   | `2196f3` | `ffffff` | `ffffff` | `000000` | [3.12](https://contrast-ratio.com/#%232196f3-on-white)         | [3.12](https://contrast-ratio.com/#white-on-%232196f3) |
| ThemeData.dark()    | `2196f3` | `ffffff` | `424242` | `ffffff` | [3.21](https://contrast-ratio.com/#%232196f3-on-%23424242)     | [3.12](https://contrast-ratio.com/#%232196f3-on-white) |
| ColorScheme.light() | `6200ee` | `ffffff` | `ffffff` | `000000` | [7.62](https://contrast-ratio.com/#%236200ee-on-white)         | [7.62](https://contrast-ratio.com/#white-on-%236200ee) |
| ColorScheme.dark()  | `bb86fc` | `000000` | `121212` | `ffffff` | [7.07](https://contrast-ratio.com/#%23bb86fc-on-%23121212)     | [7.92](https://contrast-ratio.com/#%23bb86fc-on-black) |
Repository: go
Issue: cmd/go: allow 'go list' to accept '-u' without '-m'
Labels: NeedsInvestigation,FeatureRequest,GoCommand,modules

`go list` with the `-f` flag can print a lot of information about the module associated with a package.

Unfortunately, we don't populate the `Module.Update` field unless the `-u` flag is set, and the `-u` flag can only be set today if the `-m` flag is also set:

```
example.com$ go version
go version devel +ba9e1088 Thu Aug 6 19:17:13 2020 +0000 linux/amd64

example.com$ go list -u -f '{{with .Module}}{{with .Update}}{{.}}{{end}}{{end}}' ./... | sort -u
go list -u can only be used with -m
```

We should investigate whether it is feasible to allow the `-u` flag without `-m`. That would probably require a hook to instruct the package loader to compute upgrade information.

CC @jayconrod @matloob @komuw
Repository: go
Issue: runtime: lock held checking
Labels: NeedsFix,compiler/runtime

As an extension of @danscales' work on lock ordering, we can extend the runtime to check that functions hold their prerequisite locks when staticlockranking is enabled.
Repository: pytorch
Issue: RuntimeError: "triangular_solve_cuda" not implemented for 'Half'
Labels: module: cuda,triaged,module: half,module: amp (automated mixed precision)

## ❓ Questions and Help
I am running my code on a cluster and running into this issue in the torch.distributions library for MultivariateNormal. I do not encounter this issue while training locally on a single GPU but it happens on the cluster.

I would appreciate any help with this. Relevant part of the error is listed below.

`Mon Aug 10 23:38:36 2020[1]<stderr>:  File "/app/atg/perception_prediction/multinet/training/train.runfiles/__main__/atg/experimental/user/mayankg/rl_irl/models.py", line 133, in log_prob
Mon Aug 10 23:38:36 2020[1]<stderr>:    return self.dist.log_prob(actions)
Mon Aug 10 23:38:36 2020[1]<stderr>:  File "/app/atg/perception_prediction/multinet/training/train.runfiles/pythonhome_pypi/lib/python3.7/site-packages/torch/distributions/multivariate_normal.py", line 208, in log_prob
Mon Aug 10 23:38:36 2020[1]<stderr>:    M = _batch_mahalanobis(self._unbroadcasted_scale_tril, diff)
Mon Aug 10 23:38:36 2020[1]<stderr>:  File "/app/atg/perception_prediction/multinet/training/train.runfiles/pythonhome_pypi/lib/python3.7/site-packages/torch/distributions/multivariate_normal.py", line 57, in _batch_mahalanobis
Mon Aug 10 23:38:36 2020[1]<stderr>:    M_swap = torch.triangular_solve(flat_x_swap, flat_L, upper=False)[0].pow(2).sum(-2)  # shape = b x c
Mon Aug 10 23:38:36 2020[1]<stderr>:RuntimeError: "triangular_solve_cuda" not implemented for 'Half'`


cc @mcarilli @ppwwyyxx @ngimel
Repository: flutter
Issue: CanvasKit: allocate SkVertices data on the WASM heap
Labels: engine,c: performance,platform-web,perf: speed,e: web_canvaskit,P3,team-web,triaged-web

Filing so we don't forget. When converting Flutter vertex data for CanvasKit we convert it to objects that are still in the JS heap. This means when rendering vertices we still need to copy them to WASM. We can avoid having to do that by writing to WASM immediately. However, this needs to be done considering that Safari doesn't yet support `FinalizationRegistry`.
Repository: pytorch
Issue: Documentation mistake of Adam in v1.6.0?
Labels: module: docs,module: optimizer,triaged

## 📚 Documentation

The documentation of Adam since v1.6.0 suggests that it uses the weight decay fix proposed by paper "Decoupled Weight Decay Regularization":
https://github.com/pytorch/pytorch/blob/4b4273a04e566dcdf4cb96882f49c41127e8d3f1/torch/optim/adam.py#L10-L11

However I found this to not be the case. The actual weight decay in Adam is still the old one:
https://github.com/pytorch/pytorch/blob/4b4273a04e566dcdf4cb96882f49c41127e8d3f1/torch/optim/adam.py#L99-L100

In contrast, the new weight decay fix is implemented in AdamW, and explained by the AdamW doc:
https://github.com/pytorch/pytorch/blob/4b4273a04e566dcdf4cb96882f49c41127e8d3f1/torch/optim/adamw.py#L10

https://github.com/pytorch/pytorch/blob/4b4273a04e566dcdf4cb96882f49c41127e8d3f1/torch/optim/adamw.py#L73

It is possible that I misunderstood the current documentation of Adam, but I found it confusing and suggest that currently there is no difference between the Adam and AdamW implementations, while the difference still exists.

cc @jlin27 @vincentqb
Repository: pytorch
Issue: Get test_jit.py below 10k lines
Labels: oncall: jit,module: tests,enhancement,better-engineering

Update: the test_nn.py part of this is now tracked by https://github.com/pytorch/pytorch/issues/63085

Currently, many files, such as `test_jit.py` and `test_nn.py`, are larger than what GitHub can handle. For these files, you will not be able to use GitHub's review and browse source well:

In the review UI, some lines just magically disappear and we can not expand folded lines:
![image](https://user-images.githubusercontent.com/1032377/89848096-8c7fe700-db3a-11ea-8e94-67c79e1060b5.png)
 
If you browse the file, you will see a truncated file:
![image](https://user-images.githubusercontent.com/1032377/89848181-c18c3980-db3a-11ea-8b15-4c9be12595d7.png)


cc @mruberry @VitalyFedyunin @walterddr
Repository: pytorch
Issue: Add support for user defined types in serialization in libtorch
Labels: module: cpp,feature,module: serialization,triaged

## 🚀 Feature
It would be great for the serialization to be much broader than what it is now in libtorch. at least by providing a way for the users to be able to use existing functionality to serialize their objects. 

## Motivation

I was trying to serialize a `std::vector<std::tuple<std::string, torch::Tensor>>` in libtorch where I found out its simply impossible. there is no way to extend the `InputArchive ` so I can add the needed logic to load from it. 

## Pitch

Add support for `STL` containers at least when it comes to serialization. or allow the users to be able to extend existing functionality to support their own custom types.  

## Alternatives

I ultimately ended up using Protobuf for serialization 


cc @yf225 @glaringlee
Repository: node
Issue: domain: should variable domain in EventEmitter be private
Labels: domain

* **version: Node v10.5**:
* **platform: Darwin Kernel Version 19.3.0**:
* **core module name: domain**:

### What steps will reproduce the bug?

The domain module overwrites the EventEmitter and mounts the domain on the EventEmitter. This causes a problem. If a third-party library mounts a variable named domain on the EventEmitter and introduces the domain module at the same time, it will cause an error.
We use the request library, which mounts the request body on EventEmitter. There is a domain field in our request body, and there is an error of domain.enter is not a function (domain is overwritten as a string at this time)

### How often does it reproduce? Is there a required condition?

1. Import domain
2. Inherit the EventEmitter class
3. There is a variable named domain

### What is the expected behavior?

domain should be private

### What do you see instead?

![image](https://user-images.githubusercontent.com/22697021/89851149-61d77200-dbbe-11ea-876a-ba313bc890fe.png)


### Additional information

I see that the domain module no longer accepts PRs, can I submit a PR for this issue
Repository: flutter
Issue: Provide AppInfo.xcconfig to define ${PRODUCT_NAME}  ${EXECUTABLE_NAME} and ${TARGET_NAME}
Labels: platform-ios,tool,t: xcode,c: proposal,P3,team-ios,triaged-ios

XCode need so many names: ${PRODUCT_NAME} ${EXECUTABLE_NAME} and ${TARGET_NAME}.

I noticed `macos/Runner/Configs/AppInfo.xcconfig` already did this. Is it possible to provide file `AppInfo.xcconfig` in iOS project too?

```
Bundle Display Name - ${PRODUCT_NAME}
Executable File - ${EXECUTABLE_NAME}
Bundle Name - ${PRODUCT_NAME}
```
Repository: TypeScript
Issue: [feature request] Better error messages for decorators (they are completely not understandable)
Labels: Bug,Help Wanted,Effort: Moderate,Domain: Error Messages

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

"Unable to resolve signature of property decorator when called as an expression"

## Suggestion

The error message I received was `error TS1240: Unable to resolve signature of property decorator when called as an expression.`

This leaves absolutely no clue what is wrong.

## Examples


To fix the issue, I had to change the signature of one of my functions from

```ts
export function attribute(
	prototype: any
	propName: string,
	descriptor: PropertyDescriptor | undefined,
): any
```

to

```ts
export function attribute(
	prototype: any
	propName: string,
	descriptor?: PropertyDescriptor | undefined,
): any
```

The difference is subtle: the `descriptor` arg isn't always passed to a decorator (depends on whether it is used on a property or on an accessor or method).



It'd be better if the message said something like `The 'descriptor' argument to a property decorator should not be required.`

Similar for other cases that trigger the same unhelpful error message.

## Checklist

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, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).