sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ant-design
Issue: Form add defaultValidateMessages.i18n language
Labels: help wanted,Inactive,good first issue

- [x] 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?
For #6082
example: https://github.com/ant-design/ant-design/blob/acbbbfebc2c378b8fac6297ca2bb693228f3be13/components/locale/zh_CN.ts#L86-L135

Todo:

- [ ] fi_FI
- [ ] hu_HU
- [ ] hy_AM
- [ ] kmr_IQ
- [ ] ku_IQ
- [ ] lv_LV
- [ ] mk_MK
- [ ] sl_SI

<summary>Finished</summary>

- [x] en_GB #24404
- [x] en_US #23859
- [x] fa_IR #23926
- [x] ru_RU #24219
- [x] zh_CN #23165
- [x] zh_HK #25731 
- [x] zh_TW #24065
- [x] pt_BR #24518
- [x] he_IL #24716
- [x] ko_KR #24783
- [x] tr_TR #25100
- [x] ja_JP #25244
- [x] nb_NO #25374
- [x] es_ES #25460
- [x] ar_EG #25587
- [x] ca_ES #25583
- [x] de_DE #25823
- [x] th_TH #26906
- [x] hr_HR #28458
- [x] fr_FR #29839
- [x] sv_SE #29896 
- [x] nl_BE #30389
- [x] nl_NL #30389
- [x] sr_RS #30401
- [x] ro_RO #30419
- [x] hi_IN #30541
- [x] bn_BD #31257
- [x] ur_PK #31346
- [x] ml_IN #31521
- [x] ka_GE #32106
- [x] pl_PL #32896
- [x] et_EE #33005
- [x] sk_SK #34061
- [x] az_AZ #36967
- [x] cs_CZ #37388
- [x] by_BY #27028
- [x] ga_IE #24609
- [x] gl_ES #26015
- [x] kk_KZ #27589 
- [x] km_KH #32853
- [x] lt_LT #26312
- [x] si_LK #36149
- [x] tk_TK #35605 
- [x] uk_UA #35430
- [x] pt_PT #37857
- [x] it_IT #38108
- [x] uz_UZ #39353 #39556
- [x] fr_BE #39415
- [x] fr_CA #39416
- [x] ta_IN #39936 
- [x] vi_VN #40992
- [x] bg_BG #42203
- [x] da_DK #46493
- [x] is_IS #48104
- [x] id_ID #48287
- [x] ms_MY #49353
- [x] mn_MN #49373
- [x] ne_NP #49492
- [x] kn_IN #49860
- [x] el_GR #50825
### What does the proposed API look like?

None


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: terminal
Issue: Create separate UIA parent objects for standard and alt conhost buffers
Labels: Product-Conhost,Area-Accessibility,Issue-Task,Priority-2

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement
In https://github.com/microsoft/terminal/issues/5309#issuecomment-615040262:
> Ideally, in the long term, we would have different UIA parent objects for the different text buffers.

This would make things much better for UIA clients like NVDA.
<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->
Repository: go
Issue: x/pkgsite: provide multiple "copy to clipboard" options
Labels: NeedsInvestigation,FeatureRequest,pkgsite,UX

<!--
Please answer these questions before submitting your issue. Thanks!
For questions, please email go-discovery-feedback@google.com.
-->
 
### What is the URL of the page with the issue?
Any package page (e.g. https://pkg.go.dev/github.com/sirupsen/logrus?tab=doc)
 
 
### What is your user agent?
 
<!-- 
You can find your user agent here:
https://www.whatismybrowser.com/detect/what-is-my-user-agent
-->
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.92 Safari/537.36
 
 
### Screenshot
 
<!--
Please paste a screenshot of the page.
-->
 
<img width="879" alt="Screen Shot 2020-04-18 at 3 24 01 AM" src="https://user-images.githubusercontent.com/115761/79631038-2bb04700-8124-11ea-9d8b-98a0850e8ec2.png">

### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
Click the "Copy path to clipboard" button
 
### What did you expect to see?
`github.com/sirupsen/logrus` on my clipboard
 
### What did you see instead?
`import "github.com/sirupsen/logrus"` on my clipboard

I almost never want an import statement; I want something I can copy into a `go get` command in my terminal. Plus all the UI indicates it's a path, not an import statement.
Repository: PowerToys
Issue: Please File Explorer support previewing the contents of zip without unarchived
Labels: Idea-Enhancement,Product-File Explorer

like BetterZip for QuickLook in macOS
Repository: ant-design
Issue: Toggle dark with @media (prefers-color-scheme: dark) such like ThemeProvider
Labels: 💡 Feature Request,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?
The theme color changes according to the system theme

主题色根据系统主题变换

### What does the proposed API look like?
```js
import 'antd/dist/antd.dark.css'
```
加载这个样式后，并不是直接应用到全局，而是可以通过一个类名，比如 `<body class="dark">`来切换主题。

再或者是把 less 颜色变量暴露到 css var
```css
:root {
    --red: #ff6347;
    --yellow: #ffc107;
    --blue: #6495ed;
}
@media screen and (prefers-color-scheme: dark) {
:root {
    color: #ddd;
    --red: #ad1a00;
    --blue: #1346a4;
  }
}
```


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: Allow `this` in constructor parameter
Labels: Suggestion,Awaiting More Feedback

## Search Terms

type, this, constructor, TS2526

## Suggestion

Currently, this code fails with `A 'this' type is available only in a non-static member of a class or interface.ts(2526)`:
```ts
class MyClass {
    private props: { baz: string };
    constructor(props: this["props"]) {
       this.props = props;
    }
}
```
It would be awesome if `this` could be supported in constructor arguments.

## Use Cases

This is very useful for react components, as demonstrated in the following example.
More general, sometimes a class extends a generic base class which requires generic data for initialization. If the super class also wants to do some initialization, it needs to pass this generic argument down to its base class. As constructor arguments must be typed, the type of this generic argument must be explicitly stated in the super class. 
In those cases, it is very practical to use `this` to refer to a field of that base class that has the right type.

## Examples

```ts
class MyComponent extends React.Component<{
    title: string;
}> {
    constructor(props: this["props"]) {
       super(props);
       // ...
    }
}
```

## Current Workarounds

```ts
class MyComponent extends React.Component<{
    title: string;
}> {
    constructor(props: MyComponent["props"]) {
       super(props);
       // ...
    }
}
```

This only works if the base class declares a static `props` member.
Also, it has the downside that you must write out the name of the current class. This obfuscates the fact that it refers itself.

## 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).
Repository: rust
Issue: Implement a function that creates a Cow<'_, CStr> from a slice of bytes
Labels: T-libs-api,C-feature-request

I've been working on FFI-bindings for a C library and I ran into an issue where `CString::new()` would fail if there's a 0-byte.

I was left with three options:
1) Let the users of my crate deal with `NulError`, which makes it less ergonomic, IMO;
2) Just unwrap the Result under the hood and document the possible panic;
3) When `CString::new()` fails, call `CStr::from_bytes_with_nul()` using `NulError::nul_position()`, wrap both `Ok` and `Err` branches in `Cow::from()`.

I found the third option to be the most ergonomic and that's what I went with. Of course you could argue that it's sort of a leaky abstraction because users are expected to understand that C-libraries usually read until the 0-byte. But an interior 0-byte in a Rust string is not really a common case, is it?

So, what do you guys think, is this something worthy of being a part of `std::ffi`?

I already made the changes locally and I'd be happy to make a PR. However, I can't come up with a good name, so far I called it `CString::from_slice()` but I don't think it's fitting.
Repository: vue
Issue: nextTick implementation breaks with core-js@3 Promise polyfill on Tizen 2016
Labels: need repro,browser quirks

### Version
2.6.11







### Steps to reproduce
Just cross-linking the issues here, it was opened in core-js repo:
https://github.com/zloirock/core-js/issues/814

The reproduction is not easily doable as it requires a Samsung Tizen 2016 device (which I have because I develop specifically for TVs).

### What is expected?
UI updates correctly after events

### What is actually happening?
UI will only update if another task is queue.

---
In the nextTick implementation there's a check for `isIOS` to trigger an extra `setTimeout` which, while hacky, works also for Tizen 2016.

Perhaps a PR could be made adding an exception for Samsung Tizen as well?

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: rust
Issue: const_err does not trigger on associated constants
Labels: T-lang,T-compiler,C-bug,A-const-eval

I tried this code:

```rust
pub struct Foo;

pub const FOO: Foo = Foo::new(1);

impl Foo {
    pub const FOO: Self = Self::new(1);

    pub const fn new(i: usize) -> Foo {
        [][i] = 5;
        Foo
    }
}
```

I expected to see this happen: Both `FOO` and `Foo::FOO` should trigger `const_err` errors.

Instead, this happened: Only `FOO` was marked with `const_err`

### Meta

Checked on current stable (1.42) and nightly (2020-04-17) on the playground
Repository: TypeScript
Issue: Intellisense should show internals of an interface declaration on hover
Labels: Suggestion,In Discussion,Domain: Quick Info,Experimentation Needed

## Search Terms

- intellisense interface
- intellisense interface expand

## Suggestion

I'm trying to re-open and start a discussion around #32616 and #12920, which were closed as "working as intended". It may well be the case, but it would be useful if Interfaces were expanded by default just as Type Aliases are.

Is there a hard reason impeding this I'm not seeing?

What are the metrics saying that "in general interfaces are longer"? Today Interfaces and Type Aliases offer almost the same features and they are for the most part interchangeable (especially for typing objects, see: https://stackoverflow.com/a/52682220/416714) 

I understand there is a discussion around expandable hints (#25784). Would that be the occasion to bring expanded-by-default Interfaces?

## Examples

When hovering over a Type:

<img width="340" alt="Screenshot 2020-04-18 at 15 44 41" src="https://user-images.githubusercontent.com/736316/79639547-cfcdd880-818c-11ea-8008-c2f22b2ef88f.png">

When hovering over an Interface:

<img width="340" alt="Screenshot 2020-04-18 at 15 45 01" src="https://user-images.githubusercontent.com/736316/79639557-de1bf480-818c-11ea-8ad7-ca9f5ab04012.png">

## 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).
Repository: flutter
Issue: Show Dart SDK version details in Flutter Doctor summary output
Labels: c: new feature,tool,c: proposal,P3,team-tool,triaged-tool

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
This information would be extremely useful to quickly check whether third-party packages are compatible with the project's current Dart SDK. It does show up on the detailed output (with the `-v` flag), but a mention of the Dart SDK version in the summary would be time-saving.
<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal
`flutter doctor` summary should also include the Dart SDK version info along with the Flutter version info.
Currently the Flutter section looks like:
```
[√] Flutter (Channel master, v1.18.0-6.0.pre.26, on Microsoft Windows [Version 10.0.18363.592], locale <locale>)
```
It could include the Dart SDK version in a manner similar to this:
```
[√] Flutter (Channel master, v1.18.0-6.0.pre.26, Dart SDK v2.8.0-dev.20.0, on Microsoft Windows [Version 10.0.18363.592], locale <locale>)
Repository: godot
Issue: Impossible to instantiate a scene file as node through drag-and-drop
Labels: bug,topic:editor

**Godot version:**

v3.2.1-stable-x11

**OS/device including version:**

Linux Fedora 31

**Issue description:**

After adding a GLB file (3D export in glTF binary format) to my project folder, I faced inconsistent behaviour from Godot when trying to instantiate it in my scene.

- the file was perfectly fine as Godot was able to open it in a standalone view through double-click in the file explorer panel
- the file had a red cross icon in the file explorer panel with no explanation regarding what was wrong
- I was unable to drag-and-drop the file to my scene's tree view

But:

- I was able to instantiate it by clicking the link-shaped button ("instance a scene file as a node") in the scene tree view's toolbar
- since then, the file has a movie clap icon and I can drag and drop it to the scene tree view

However:

- when pressing the play button, the game launches correctly and works fine but Godot shows an alert message box in the editor saying "requested file format unknown: glb"

**Steps to reproduce:**

(I'm currently taking part in a game jam so I will try to provide this later if and only if the bug is not deemed to be an error on my end or expected behaviour somehow, as I'm new to Godot.)

**Minimal reproduction project:**

(see note above)
Repository: pytorch
Issue: Stochasticity for DistributedDataParallel on CPU but not on GPU
Labels: high priority,needs reproduction,oncall: distributed,triaged,module: determinism,module: data parallel

## 🐛 Bug

When I run my DDP model on the GPU using a specific seed, I get identical results time after time.  But when I run the same DDP model on the CPU using the same seed, I get different results each time.  

I am setting the seed within the child process, near its beginning, using the following code:

    torch.manual_seed(args.seed)
    np.random.seed(args.seed)

I also tried setting the seed inside the model, before it goes into its training loop.  No luck.

## To Reproduce

Steps to reproduce the behavior:

1.Run the model via DDP on the GPU using a specific seed, three times, saving the output into different files each time.  Confirm the output is identical across all three files.
2.Run the same model via DDP on the CPU using a specific seed, three times, saving the output into different files each time.  Confirm the output is different across all three files.

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

The output should be the same each time for a given seed, on a given device.  I do not expect CPU and GPU output to match each other, but I do expect all GPU output to match itself, and the same for all CPU output.

<!-- A clear and concise description of what you expected to happen. -->

## Environment

PyTorch version: 1.4.0
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04.3 LTS
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
CMake version: version 3.10.2

Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: 10.0.130
GPU models and configuration: 
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti
GPU 2: GeForce RTX 2080 Ti
GPU 3: GeForce RTX 2080 Ti

Nvidia driver version: 418.74
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.2

Versions of relevant libraries:
[pip3] numpy==1.18.1
[pip3] torch==1.4.0
[conda] numpy                     1.17.2           py36h95a1406_0    conda-forge


## Additional context

<!-- Add any other context about the problem here. -->


cc @ezyang @gchanan @zou3519 @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar
Repository: pytorch
Issue: Memory leak upon exception for interactive consoles
Labels: module: memory usage,triaged

## 🐛 Bug

If I run PyTorch code in an interactive console such as the python interpreter or ipython, then PyTorch leaks memory when a function call on a `torch.nn.Module` raises an exception that propagates to the top level. Running `torch.cuda.clear_cache()` does not clear this memory, and I have observed cases where even catching the exception and running `del(model)` does not clear the memory.

## To Reproduce

In the Python interpreter, run:

```
import torch

class Blah(torch.nn.Module): 
    def __init__(self): 
        super().__init__() 
        self.params = torch.nn.Linear(30000, 30000) 
    def forward(self, vals): 
        val = self.params(vals) 
        raise RuntimeError("Oopsies")

b = Blah().to('cuda'); b.forward(torch.zeros(30000).to('cuda'))
torch.cuda.empty_cache()
b = Blah().to('cuda'); b.forward(torch.zeros(30000).to('cuda'))
torch.cuda.empty_cache()
```

Repeat the last line as needed until GPU memory is exhausted. Continuing further results in main memory being exhausted.

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

GPU (and regular) memory is cleared once `b` becomes out of scope after each exception, and I am allowed to run the last line arbitrarily many times.

<!-- A clear and concise description of what you expected to happen. -->

## Environment

```
Collecting environment information...
PyTorch version: 1.4.0
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04.4 LTS
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
CMake version: version 3.17.1

Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: 10.0.130
GPU models and configuration: GPU 0: GeForce GTX 1060 with Max-Q Design
Nvidia driver version: 440.64
cuDNN version: Could not collect

Versions of relevant libraries:
[pip] Could not collect
[conda] Could not collect
```

## Additional context

Fixing this bug is important for people who debug models interactively. Otherwise they'll have to repeatedly restart the console or kernel, or get an unexpected memory thrashing problem in the middle of their work.

<!-- Add any other context about the problem here. -->
Repository: three.js
Issue: FirstPersonControls doesn't support (0,0,1) as camera up.
Labels: Enhancement

Hey all,

Not sure if bug or feature so I'm starting with making the issue first.

Having `Object3D.defaultup` set to anything other than `new Vector3(0,1,0)` and by extension `camera.up`, results in jarring camera behaviour when controlled by the `FirstPersonController`.
Repository: go
Issue: cmd/go: override semantics break e.g. GOFLAGS=-ldflags
Labels: NeedsInvestigation

I was asked to post this as a separate issue in https://github.com/golang/go/issues/26849#issuecomment-615950020, so here goes:

Comment https://github.com/golang/go/issues/26849#issuecomment-454481195 already touches upon the override semantics issue (`-ldflags=-w -ldflags=-s` results in only `-s`), but since that example would likely be fixed by quoting changes, I’d like to stress another nuance not addressed by quoting: the current override behavior makes setting `-ldflags` in `GOFLAGS` impossible when the `go` tool command lines contain an explicit `-ldflags` flag.

For my use-case, I want to set the ELF interpreter in my build system, so I figured I’d set the `GOFLAGS` environment variable like so:

```
GOFLAGS="-ldflags=-extldflags=-Wl,--dynamic-linker=/ro/glibc-amd64-2.31-4/out/lib/ld-linux-x86-64.so.2"
```

This works in general, but breaks as soon as the software in question specifies its own ldflags on the command line, like e.g. [containerd does in its Makefile](https://github.com/containerd/containerd/blob/3282a1c14cd98c124970e448f6d1a9fe5ae0b9b8/Makefile#L100).

It’s easy to verify this:
```
GOFLAGS=-ldflags=-invalid go build # fails
GOFLAGS=-ldflags=-invalid go build -ldflags=-s # does not fail
```

Notably, from C build systems, I’m used to LDFLAGS generally being extended, never overridden.

For my use-case, I’m currently setting `-Wl,--dynamic-linker` in `CGO_LDFLAGS` instead. Not entirely sure how reliable that is longer-term, but it seems to work with the packages I currently care about.