sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/pkgsite: fails to update latest to reflect latest version
Labels: NeedsFix,pkgsite

<!--
Please answer these questions before submitting your issue. Thanks!
-->
 
### What is the URL of the page with the issue?

https://pkg.go.dev/gonum.org/v1/gonum@v0.9.3
 
 
### 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 (X11; Ubuntu; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0

 
### Screenshot
 
<!--
Please paste a screenshot of the page.
-->
![Screenshot from 2021-06-30 21-21-48](https://user-images.githubusercontent.com/275221/123956115-7a749480-d9e9-11eb-9a38-eb02c2abe0ac.png)

![Screenshot from 2021-06-30 21-22-02](https://user-images.githubusercontent.com/275221/123956141-7fd1df00-d9e9-11eb-9015-6fe9d9f80247.png)

![Screenshot from 2021-06-30 21-26-46](https://user-images.githubusercontent.com/275221/123956529-eeaf3800-d9e9-11eb-9281-cf4f5b6fc912.png)

 
### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
Navigate to the linked page. 
 
### What did you expect to see?
 
The LATEST text mark on the latest version.
 
### What did you see instead?

A "GO TO LATEST" link on the latest version pointing to the previous version and the previous version being marked as latest.
Repository: flutter
Issue: [in-app-purchase] Getting non-renewable subscription, instead of renewable one 
Labels: platform-android,p: in_app_purchase,package,P2,team-android,triaged-android

 - I am using version 1.0.6 of in_app_purchase.
 - Set up a subscription with id *base_mobile* in play console with monthly billing, 14-day free trial 
- The app is published to internal testing in play console

I am able to fetch the products using 

    final ProductDetailsResponse response =
    await iapConnection.queryProductDetails(_ids);

The main problem is not being able to test the free trial. On trying to buy a subscription as a non-consumable using the following code:

    await iapConnection.buyNonConsumable(purchaseParam: purchaseParam);
pops up the following dialog:

<img src="https://user-images.githubusercontent.com/31307345/123957018-f4485600-d9c8-11eb-9728-50b83fbcce66.jpeg" height="450" />	|


I am not able to opt-in for the free trial. No option is shown. Also, the subscription is not automatically renewable. According to my understanding, subscriptions should be renewable as per the interval of the billing period.

I even tried out installing the app from another play account which is not a licensed tester.
It's the same issue, the amount was deducted immediately without the possibility of a free trial.
The subscription also was not cancellable in the play store.


Do have any of my setup wrong?
Repository: transformers
Issue: Expand text-generation pipeline support for other causal models e.g., BigBirdForCausalLM
Labels: Feature request

# 🚀 Feature request

Tried using the text generation pipeline (TextGenerationPipeline) with BigBirdForCausalLM but seems like the pipeline currently only supports a limited number of models. Is there a reason for this? Is there a workaround short of implementing the pipeline myself? Thank you.
Repository: PowerToys
Issue: Choose / change systray icon
Labels: Idea-Enhancement,Area-Runner,Area-User Interface

### Description of the new feature / enhancement

You can change the icon next to the clock in settings, changing between some pre-defined options, or loading .ico files.
The idea is to make this icon less flashy and more similar to the identity of the original Windows icons.

Maybe even with the option of not having any icon there, and opening the options with just some command.

### Scenario when this would be used?

An option in General Settings.


### Supporting information

_No response_
Repository: PowerToys
Issue: Include "Restart as admin" button to file explorer add ins settings
Labels: Idea-Enhancement,Help Wanted,Product-Settings,Product-File Explorer

Open settings as a standard user, go to file explorer add ons. It displays that you should run the power toys settings as administrators.

### ✔️ Expected Behavior

Display a button to restart the settings as an administrator

### ❌ Actual Behavior

Have to close powertoys and run it again as administrator. It would be much nicer if powertoys offers a button for admin rights elevation. 

crutkas: tweaked this to be feature request versus bug
Repository: create-react-app
Issue: `env-cmd` example should mimic default `dotenv` behavior
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

By default `env-cmd` WILL override the globally defined env vars, which differs from the default `dotenv` behavior and adds confusion.

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

We should provide `--no-override` flag to `env-cmd` in the staging build example

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

An alternative would be a first-class support for environment-specific `.env` files by CRA, but that's a matter of future releases

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

- https://github.com/toddbluhm/env-cmd#--no-override-option
- https://github.com/motdotla/dotenv#what-happens-to-environment-variables-that-were-already-set
Repository: flutter
Issue: Add custom properties to ThemeData
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

This is related to https://github.com/flutter/flutter/issues/16487. Even though the issue is closed, the same problem is still present today. Since I can't find a "reopen issue" function, I am creating this proposal.

## Use case

I want to add custom properties (e.g. colors) to `ThemeData`.

Why? Sometimes the default meterial colors are just not good enough. Let's just say I want to have `myFancyColor` with a unique color value that can't be derived from any of the color values within the default `ThemeData` colors.

To this date, there is no simple and clean way to do this. All "solutions" proposed over the last 3 years are hacky workarounds that come with their own problems. Some examples of "solutions" that don't work are in the comments in the referenced issue.

## Proposal

There are two simple solutions to this problem.

### 1. Allow us to extend `ThemeData` (preferred)

_The constructor 'ThemeData ...' is a factory constructor, but must be a generative constructor to be a valid superinitializer.  Try calling a different constructor of the superclass, or making the called constructor not be a factory constructor._

Why is that? People thought of this solutions for 3 years now, see https://github.com/flutter/flutter/issues/16487.

If we could extend ThemeData we would have:
```dart
class CustomThemeData extends ThemeData {
  CustomThemeData(...): super(...);

  final Color myFancyColor;
}
```

And then use it everywhere without affecting any other built in functionality.

```dart
(Theme.of(context) as CustomThemeData).myFancyColor
```

### 2. Add a `custom` `Object` to `ThemeData`

We could do something like this:

```dart
@immutable
class ThemeData with Diagnosticable {
  ...

  /// An optional object with additional custom theme data.
  final Object? custom;
}
```

And then use it everywhere without affecting any other built in functionality.

```dart
(Theme.of(context).custom as CustomColors)?.myFancyColor
```

## Final thoughts
If none of the suggestions, or similar, is considered a valid solution, I want to know why the current `ThemeData` implementation is as it is. There has to be a reason why you want to restrict developers from customizing `ThemeData`. If so, what would be an _actual solution_ to the problem?
Repository: flutter
Issue: [Feature Request] add common spacing to theme (xs, s, m, l, xl)
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

## Use case

When writing a UI library it would be nice to have access to common values for spacing through the theme. 

Most applications need:

A color scheme with: [primary, secondary, warn, success, ...]
Spacings with [xs, s, m, l, xl]


The use case therefor would be that if one writes an UI library he can directly use those values as a default. EG:

```
// this is a container in a UI library that does not have to make assumptions to the spacing used throughout the
// application that will use the library
Container(
  padding: padding ?? EdgeInsets.all(Theme.of(ctx).spacing.xs)
  color: color ?? Theme.of(ctx).palette.warn
```

## Proposal

To have palette and spacing with the most common values on the theme.  Angular material does it somewhat.
Repository: PowerToys
Issue: Provide a replacement for Advanced Appearance Settings dialog that has gone missing
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Allow users to better fine tune the colors used in their environment by providing access to the settings which used to be available through the Advanced Settings panel of the Display Properties for versions of Windows prior to 10. It appears that all the registry settings are still there (Computer\HKEY_CURRENT_USER\Control Panel\Colors) and perform the same function. There just isn't a utility for users to use, other than Regedit, to make these changes. Regedit is a poor tool for this as colors need to be entered as numbers and there is no preview for the user of how the color appears in conjunction with other chosen colors.
This document shows the old interface and explains one instance where users would make use of this. [GrayBackgroundWindows.pdf](https://github.com/microsoft/PowerToys/files/6742382/GrayBackgroundWindows.pdf)


### Scenario when this would be used?

This would be useful for creating a display environment that prevents eye strain for those of us who have to spend way too long staring at screens. The Light / Dark themes are a step in the right direction but the new UI for Win10 doesn't allow enough control over the main fields of color that a user will be looking at (spreadsheet backgrounds, document backgrounds, etc).

### Supporting information

https://www.linkedin.com/pulse/dark-mode-2-dangerous-better-way-cristiano-galv%C3%A3o
https://answers.microsoft.com/en-us/windows/forum/windows_10-start-winpc/windows-10-advanced-appearance-settings/947ea4b8-bfa9-4689-a3bf-4925f763d269
Repository: pytorch
Issue: Audit use of __ARM_NEON__ define
Labels: oncall: quantization,low priority,triaged,enhancement

It looks like __ARM_NEON__ define sometimes used to distinguish between ARMv8 and ARMv7 builds, for example here:
https://github.com/pytorch/pytorch/blob/0b8a7daa2a7e765270b85234b868b5897a9822bb/aten/src/ATen/native/quantized/cpu/kernels/QuantizedOpKernels.cpp#L2482

But this is not the case, as __ARM_NEON__ is defined when compiling for aarch64 using clang compiler:
```
 % clang -dM -E - < /dev/null|grep -i ARM_NEON
#define __ARM_NEON 1
#define __ARM_NEON_FP 0xE
#define __ARM_NEON__ 1
```

Also see this issue, which claims that `__ARM_NEON__` is legacy define and `__ARM_NEON` should be used instead(which on the other hand will always be defined when compiling for 64-bit ARM):
https://github.com/openwall/john/issues/1998

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: vscode
Issue: Extension bisect does not consider "dependent" extensions when choosing what to disable
Labels: feature-request,bisect-ext

Suppose I have 4 extensions installed. Extension B has a dependency on A, and extension Y has a dependency on X. When running extension bisect, the bisect can select extensions A and X as the first two extensions to disable. However in this case, B and Y cannot be activated as the extensions they depend on are disabled, so the bisect runs with no extensions enabled. We should consider dependencies when bisecting, and only disable an extension if all other dependents of that extension have been disable by bisect.
Repository: transformers
Issue: [Wav2Vec2] Better names for internal classes
Labels: WIP

Wav2Vec2's classes have too many names, *e.g.*: FlaxWav2Vec2EncoderLayerStableLayerNormCollection. 

We should make those names easier (reminder for myself @patrickvonplaten to do this)
Repository: flutter
Issue: [flutter_plugin_tools] Validate test file locations
Labels: team,p: tooling,package,team-ecosystem,P2,triaged-ecosystem

As we've been auditing our test coverage, test harnesses, etc. in flutter/plugins there's been a recurring pattern of tests not running (or not running as expected) due to files being put in the wrong place. We've somewhat mitigated that by making more test commands fail, rather than do nothing, if a plugin that we haven't explicitly exempted doesn't run any tests, but it would still be fairly easy to fail to notice in a review that someone adding, say, a new Android test file had added it in the wrong place.

We should make a new tools command that looks for known filename patterns that indicate various kinds of tests and ensures that they are in the expected locations (as documented at https://github.com/flutter/flutter/wiki/Plugin-Tests).
Repository: TypeScript
Issue: Find All References does not work with module.exports in JavaScript
Labels: Bug,Rescheduled

Issue Type: <b>Bug</b>

1. Create two files:

`utils.js` containing:

```js
function getText() {
  return "Hello, World!";
}

module.exports = { getText };
```

and `index.js` containing:

```js
const { getText } = require("./utils");

console.log(getText());
```

2. Now go to `utils.js`, and try to find all references of `getText`, it will only show the references in the current file, `utils.js`, but not the reference in `index.js`.

Note that I've tried creating a `jsconfig.json` with the following contents in the root directory of the project, but it still didn't fix the problem:

```jsonc
{
    "compilerOptions": {
        "target": "es2020" // I also tried "ES6"
    },
    "exclude": [
        "node_modules",
        "**/node_modules/*"
    ]
}
```
---

VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:32.912Z)
OS version: Darwin x64 20.5.0
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|3, 3, 3|
|Memory (System)|32.00GB (9.81GB free)|
|Process Argv|--crash-reporter-id 3be7b697-7459-484d-8019-253c76c2ed36|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->

Node.js version: v14.16.0
Repository: youtube-dl
Issue: Validation of option keys provided to YoutubeDL constructor
Labels: request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

1. When passing options in the dict to the `YoutubeDL` class, the invalid ones are silently ignored. For example, it took me a bit of time to realize that one of the options that I was using is supposed to be spelled `restrictedfilenames` instead of `restricted_filenames`. It would save dev time if an error were raised in the below example

```
with youtube_dl.YoutubeDL({"restricted_filenames": True}) as ydl:
    ydl.download([url])

>>> Error: Invalid key "restricted_filenames"
```

2. This option specifically is inconsistently translated between CLI argument form to dict key form, eg `--max-filesize -> max_filesize` but `--restricted-filenames -> restrictedfilenames`.
Repository: PowerToys
Issue: Start PowerToys Run directly from the runner
Labels: Product-PowerToys Run,Issue-Task

### Description of the new feature / enhancement

Start PowerToys directly from the runner and remove the `ActionRunner.exe` process.

### Scenario when this would be used?

If PowerToys Run can be started directly from the runner we don't need to spawn useless processes.

### Supporting information

_No response_
Repository: vscode
Issue: Git - VSCode fails when working with git on paths containing non-english letters
Labels: bug,git,confirmed


Issue Type: <b>Bug</b>

Hi,
git in VS-Code fails when working with at least some non-english letters. I have an "ö" in the file path and while initializing a repository via the GUI works, nothing else does. Whenever I try to interact with git via VSCode, e.g. adding a file I get the error message
"Git: fatal: [path with ö]/file.xyz: '[path with ö]/file.xyz' is outside repository".
Colors for changed file (orange) or new file (green) also don't update in the GUI.

This problem does not occur when interacting with git directly and also disappears after renaming the path to contain only english letters and restarting VSCode.

Thanks.

VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:32.912Z)
OS version: Darwin x64 20.5.0
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz (4 x 1400)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|4, 4, 4|
|Memory (System)|8.00GB (0.25GB free)|
|Process Argv|. --crash-reporter-id 59d0e77b-83b1-47da-a039-7da20536f398|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (10)</summary>

Extension|Author (truncated)|Version
---|---|---
latex-workshop|Jam|8.19.2
vscode-docker|ms-|1.14.0
python|ms-|2021.6.944021595
vscode-pylance|ms-|2021.6.3
jupyter|ms-|2021.6.999662501
remote-containers|ms-|0.183.0
preview-vscode|sea|2.2.5
txt-syntax|xsh|0.1.5
ooxml-viewer|yue|1.1.1
markdown-pdf|yza|1.4.4


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspyt653:30270858
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
vspre833:30321513
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255cf:30323309
vscorehov:30309549
vscod805:30301674
binariesv615:30325510
aatestflight:30331711

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: Type checks don't work in statically typed functions when using yields 
Labels: bug,topic:gdscript

### Godot version

3.3.2 Standard stable

### System information

Windows 10

### Issue description

When using yields in statically typed functions the type checks don't work as expected.
This include but is not limited to:

- Being able to return different type
- Returning void in function that should return something
- Returning value in a void function.

### Steps to reproduce

See the attached minimal.zip. It contains the project with comments describing some cases.
Just run the test.tscn scene.

### Minimal reproduction project

[minimal.zip](https://github.com/godotengine/godot/files/6743512/minimal.zip)
Repository: vscode
Issue: Add cursor stops around inlay hints
Labels: feature-request,inlay-hints

This is some generic feedback on the editor inline hints implementation, not this TS-specific support, but I wasn’t sure where else to share it. I found the experience of splitting up a long function call with parameter name hints extremely disorienting, because I wanted to put my cursor before the hint to move it down a line with the argument. But the cursor position only exists _after_ the hint, so the impression you get as you make a refactor like this is that you’re actually inserting a newline between the label and the argument it’s labeling. And indeed, there is a moment of delay before the label disappears and reappears on the new line:


https://user-images.githubusercontent.com/3277153/122442211-f12e7e00-cf63-11eb-80c8-4863b1a7c710.mp4

I obviously understand what’s happening and how I need to adjust for it—I’m exaggerating my struggle in this screen cap to demonstrate the nature of why it feels unintuitive—but it really is kind of jarring. It seems to me that you’d either want to duplicate the cursor position on either side of these labels, so it appears as if there are two cursor positions, even though they’re actually the same position in the source text, _or_ you’d want an API that allows these labels to be “sticky” on either the start or end, which would control which side of the label you can place the cursor. Prefix labels like these would be sticky on their end side, such that you can’t separate the label from the argument that follows it. This would result not only in a more intuitive editing experience, but also fewer reflows of label position mid-edit like you see in every newline insertion here.

_Originally posted by @andrewbranch in https://github.com/microsoft/vscode/issues/113412#issuecomment-863413819_