sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: Filter and search components by tag
Labels: feature request,ui,ui: search

**Is your feature request related to a problem? Please describe.**
Right now, there isn't a way to filter or search through filtered items in the left navigation. While searching is available to find a specific component, it searches through all available components.

**Describe the solution you'd like**
I would like the ability to filter AND search filtered options based on tag. 

For example, the tag could be used to filter components by platform. I imagine by default, it would be set to show all components - but if I want to see just components that support Android, I could select that filter to only show me Android components. For a design system that supports different platforms, this means it's not possible to just see components that are Android, iOS, or web. 

When selecting an Android-only component, the viewport should show me a view corresponding to Android. When selecting a component that only supports a web component, I should not be able to toggle my view to a mobile view.

Basically, at a glance, I should be able to see what components are supported based on platform.

**Describe alternatives you've considered**
* A separate Storybook per tag (messy, duplicate documentation)
* Using the default SB hierarchy and duplicate components based on tag (makes left nav very long, hard to read)

**Are you able to assist bring the feature to reality?**
Yes

**Additional context**
I would love to be able to filter the left nav like this: https://backpack.github.io/components/accordion/?platform=web
Repository: pytorch
Issue: Error out during compilation if USE_FBGEMM=1 is ignored
Labels: module: build,module: cpu,module: ci,triaged,better-engineering

USE_FBGEMM=1 is ignored if your compiler does not support AVX512. It would be nice to change it so that it errors out so that developers are not confused about if it is enabled or not.

@jamesr66a says: "I think USE_FBGEMM=1 is the default in CI and if we did that, a bunch of builds would error". 

If we want to make this nicer for developers, we can just figure out which CI configurations we need to make USE_FBGEMM=0 to make this work.

cc @ZolotukhinM
Repository: puppeteer
Issue: Support to emulate @media (hover: *)
Labels: feature

<!--
STEP 1: Are you in the right place?

- For general technical questions or "how to" guidance, please search StackOverflow for questions tagged "puppeteer" or create a new post.

https://stackoverflow.com/questions/tagged/puppeteer

- For issues or feature requests related to the DevTools Protocol (https://chromedevtools.github.io/devtools-protocol/), file an issue there:

https://github.com/ChromeDevTools/devtools-protocol/issues/new.

- Problem in Headless Chrome? File an issue against Chromium's issue tracker:

https://bugs.chromium.org/p/chromium/issues/entry?components=Internals%3EHeadless&blocking=705916

For issues, feature requests, or setup troubles with Puppeteer, file an issue right here!
-->

### Steps to reproduce

**Tell us about your environment:**

* Puppeteer version: 1.19
* Platform / OS version: macOS
* URLs (if applicable):
* Node.js version: 10.16

**What steps will reproduce the problem?**

I want to emulate `@media (hover: ...)` to test my CSS at different devices.
Example:
```
a {
  color: green;
}

@media (hover: hover) {
  a:hover {
    background: red;
  }
}
```

`@media (hover: hover)` works well when I run this code in puppeteer+macOS. But I want to emulate `@media (hover: none)` for mobile device to test it.

**What is the expected result?**

API to configure input mechanism.
Repository: go
Issue: cmd/go: populate debug.Module.Sum even if build in devel mode
Labels: help wanted,NeedsFix,FeatureRequest,modules

Related to #29814

When a binary is build from within a module's source tree, the output from runtime/debug.ReadBuildInfo currently reports the module as having version `(devel)`.
This is understandable.

However, I don't think there is technical reason why the `Sum` at least can't be computed.

This has usefulness when building commandline tools from the source tree, and you want to at least emit some versioning information that distinguishes one build from another build at a different commit.

\cc @bcmills
Repository: youtube-dl
Issue: YoutubeDL Embedded Buffer Download
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 2019.08.02. 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 **2019.08.02**
- [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.
-->

Downloading into a buffer should be possible, not simply into a file.
Repository: node
Issue: Non-heap memory leak in node:10.15.3-alpine, node:10.16.0-alpine
Labels: memory

Copied from https://github.com/nodejs/docker-node/issues/1082

We've witnessed a consistent memory leak in 2 versions of the node alpine Docker images: `node:10.15.3-alpine` and `node:10.16.0-alpine`. This leak may be present in other versions of the alpine images, but we know it is **NOT** present in `node:6.11.1-alpine`, `node:8.16.0-alpine`, `node:10.15.3-jessie`, and `node:10.15.3-stretch`.

This leak is a non-heap leak—the Node heap is not consistently growing, but the memory used by the docker container is.

Here is are some graphs demonstrating the leak across ~20 containers. The **blue lines** are the RSS of the docker containers and the **red lines** are the size of the Node heaps of the processes within each container.

## `node:10.15.3-alpine`

![node-10-15-3-alpine](https://user-images.githubusercontent.com/1128750/62477980-e77c4280-b75e-11e9-9b17-98964fa3dfd2.png)

## `node:10.16.0-alpine`

![node-10-16-0-alpine](https://user-images.githubusercontent.com/1128750/62477991-ee0aba00-b75e-11e9-89d1-b851355c29ce.png)

## `node:10.15.3-stretch` (no leak, for reference)

![node-10-15-3-stretch](https://user-images.githubusercontent.com/1128750/62478006-f2cf6e00-b75e-11e9-8ee4-1d9595d6965f.png)
Repository: godot
Issue: Godot Editor should only change date modified on files when contents change
Labels: bug,topic:editor,confirmed

# **Godot version:**
3.1.1.stable.mono.official

# **OS/device including version:**
Windows 10 Home 64-Bit

# **Issue description:**
## **What happens**
I open my project and see that Git is reporting that project.godot, default_env.tres and Game.tscn (my root node) have changed despite their contents being identical.

## **What should happen instead**
Last modified timestamps on files should only be changed when file contents change as is expected by Git and probably other version control systems.

# **Steps to reproduce:**

Create a new project.

Close Godot.

Initialize a Git repo and commit.

Open the project in Godot.

Look at Git reporting that files have changed.

# **Minimal reproduction project:**
Any project.

[Here's the project I'm working on](https://github.com/BenMcLean/Wolf3D-Godot)
Repository: flutter
Issue: Issue with refunds (IAP Plugin)
Labels: platform-android,customer: crowd,p: in_app_purchase,package,P2,team-android,triaged-android

Hello,
I've been using Flutter and the in_app_purchase pulgin to create an app with IAP.
Everything is working well, execpt if I refund(and revoke) a test purchace it still seems to be included in this list;

`final QueryPurchaseDetailsResponse responsePast = await InAppPurchaseConnection.instance.queryPastPurchases();`

Is there a way to verify if a purchase is still valid?

I think either this list shouldn't include revoked purchases,
Or it should be tagged as not current,
Or there should be a way to query the state of a purchase.

If this is already possible please point me in the right direction by way of documentation or examples.

Thank you.

Flutter version;
`Flutter 1.7.8+hotfix.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision b712a172f9 (4 weeks ago) • 2019-07-09 13:14:38 -0700
Engine • revision 54ad777fd2
Tools • Dart 2.4.0
`

In App Purchase version;
` in_app_purchase: 0.2.1`
Repository: youtube-dl
Issue: [ADN] How can I fix the subtitle support for the ADN extractor?
Labels: question

<!--

######################################################################
  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:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

Hello!
I want to fix the subtitle support in [`adn.py`](https://github.com/ytdl-org/youtube-dl/blob/master/youtube_dl/extractor/adn.py).
The current situation is explained in #12724. Right now, there is a key hardcoded [here](https://github.com/ytdl-org/youtube-dl/blob/master/youtube_dl/extractor/adn.py#L76) in the code:
```py
bytes_to_intlist(binascii.unhexlify(self._K + '4b8ef13ec1872730')),
```
This key changes every day, so poeple have been modifying the extractor code in their installation to get the subtitle extraction working -- and they have been changing the key every day. This is obviously not user friendly.

Youtubedl should automatically get the key as part of the subtitle retrieval process, and that is what I want to implement.
I know I need a JS Interpreter since the remote JS file that has the key changes every day and you can't easily get it with a regex or something similar because the key doesn't appear in the code; it is the result of an obfuscated js computation.

Should I use PhantomJS or another interpreter to do it?

I've found that you can get the key by executing 
```js
videojs.players["adn-video-js"].onChromecastCustomData().key
```
when an episode page is loaded. That's kinda hacky but it works :p

There are many more ways to do it (like proxying the `CryptoJS` object before the dom `load` event)
but I found no easier way than that, because the variable is deeply nested in obfuscated code.

More importantly; this code uses calls to [videojs](https://videojs.com/) (one of the dependencies ADN uses) so I think this code won't break for while.

Thank you!
Repository: flutter
Issue: flutter precache --force doesn't download artifacts for desktop
Labels: tool,a: first hour,a: desktop,P3,team-tool,triaged-tool

I synced and ran `flutter precache --force` with the macos desktop opt-in turned on, and it downloaded things, but didn't download "darwin-x64 tools", even though it said it did, because after I got on the bus, and tried to run my desktop app, it downloaded it again (or more parts of it, or something, that took 23 seconds to download).

Here's what it said it download when I did `fluttter precache --force`:

```
% flutter precache --force
Downloading Dart SDK from Flutter engine 739b2dd4b27151958ca5993665ba2e8f2a6e9032...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  265M  100  265M    0     0  24.0M      0  0:00:11  0:00:11 --:--:-- 29.0M
Building flutter tool...
Downloading android-arm-profile/darwin-x64 tools...                 0.8s
Downloading android-arm-release/darwin-x64 tools...                 0.5s
Downloading android-arm64-profile/darwin-x64 tools...               0.6s
Downloading android-arm64-release/darwin-x64 tools...               0.5s
Downloading android-x86 tools...                                    0.8s
Downloading android-x64 tools...                                    0.9s
Downloading android-arm tools...                                    0.5s
Downloading android-arm-profile tools...                            0.4s
Downloading android-arm-release tools...                            0.5s
Downloading android-arm64 tools...                                  0.7s
Downloading android-arm64-profile tools...                          0.5s
Downloading android-arm64-release tools...                          0.6s
Downloading ios tools...                                            2.0s
Downloading ios-profile tools...                                    1.5s
Downloading ios-release tools...                                    1.3s
Downloading package sky_engine...                                   0.2s
Downloading common tools...                                         0.7s
Downloading common tools...                                         0.6s
Downloading darwin-x64 tools...                                     1.8s
```

And when I ran my app:
```
Downloading darwin-x64 tools...                                    23.4s
```
Repository: kubernetes
Issue: TOB-K8S-034: HTTPS connections are not authenticated 
Labels: kind/bug,area/security,sig/api-machinery,sig/auth,priority/important-longterm,lifecycle/frozen,wg/security-audit

This issue was reported in the [Kubernetes Security Audit Report](https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Final%20Report.pdf)

**Description**
The Kubernetes system allows users to set up Public Key Infrastructure (PKI), but often fails to authenticate connections using Transport Layer Security (TLS) between components, negating any benefit to using PKI. The current status of authenticated HTTPS calls are outlined in the following diagram.

This failure to authenticate components within the system is extremely dangerous and should be changed to use authenticated HTTPS by default. Systems Kubernetes can depend on, such as Etcd, have also been impacted by the absence of authenticated TLS connections.

**Exploit Scenario**
Eve gains access to Alice’s Kubernetes cluster and registers a new malicious kubelet with the kube-apiserver. Since the kube-apiserver is not using authenticated HTTPS to authenticate the kubelet, the malicious kubelet receives Pod specifications as if it were an authorized kubelet. Eve subsequently introspects the malicious kubelet-managed Pods for sensitive information.

**Recommendation**
Short term, authenticate all HTTPS connections within the system by default, and ensure that all components use the same Certificate Authority controlled by the kube-apiserver.

Long term, disable the ability for components to communicate over HTTP, and ensure that all components only communicate over secure and authenticated channels. Additionally, use mutual, or two-way, TLS for all connections. This will allow the system to use TLS for authentication of client credentials whenever possible, and ensure that all components are communicating with their expected targets at the expected security level. 

**Anything else we need to know?**:

See #81146 for current status of all issues created from these findings.

The vendor gave this issue an ID of TOB-K8S-034 and it was finding 3 of the report.

The vendor considers this issue High Severity.

To view the original finding, begin on page 24 of the [Kubernetes Security Review Report](https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Final%20Report.pdf)

**Environment**:

- Kubernetes version: 1.13.4
Repository: kubernetes
Issue: TOB-K8S-012: Use of InsecureIgnoreHostKey in SSH connections
Labels: kind/bug,area/security,sig/api-machinery,lifecycle/frozen,wg/security-audit

This issue was reported in the [Kubernetes Security Audit Report](https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Final%20Report.pdf)

**Description**
Kubernetes uses Secure Shell (SSH) to connect from masters to nodes under certain, deprecated, configuration settings. As part of this connection, masters must open an SSH connection using NewSSHTunnel, which in turn uses makeSSHTunnel. However, makeSSHTunnel configures the connection to skip verification of host keys. An attacker could man-in-the-middle or otherwise tamper with the keys on the node, without alerting the master. The code for makeSSHTunnel begins with:
```
func makeSSHTunnel(user string, signer ssh.Signer, host string) (*SSHTunnel, error) {
	config := ssh.ClientConfig{
		User:            user,
		Auth:            []ssh.AuthMethod{ssh.PublicKeys(signer)},
		HostKeyCallback: ssh.InsecureIgnoreHostKey(),
	}
      // (...)
}
```

**Exploit Scenario**
Alice’s cluster is configured to use SSH tunnels from control plane nodes to worker nodes. Eve, a malicious privileged user, has a position sufficient to man-in-the-middle connections from control plane nodes to worker nodes. Due to the use of InsecureIgnoreHostKey, Alice is never alerted to this situation. Sensitive cluster information is leaked to Eve.

**Recommendation**
Short term, document that this restriction is in place, and provide administrators with guidance surrounding SSH host auditing. This should support something similar to the Mozilla SSH Best Practices guidance.

Long term, decide if SSH tunnels will be deprecated. If they will be deprecated, remove support completely. If tunnels will not be deprecated, include a mechanism for nodes to report the SSH keys to the cluster, and always insist that the keys remain static. This may require a process to preload the trust-on-first-use (TOFU) mechanisms for SSH. 

**Anything else we need to know?**:

See #81146 for current status of all issues created from these findings.

The vendor gave this issue an ID of TOB-K8S-012 and it was finding 10 of the report.

The vendor considers this issue Medium Severity.

To view the original finding, begin on page 37 of the [Kubernetes Security Review Report](https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Final%20Report.pdf)

**Environment**:

- Kubernetes version: 1.13.4
Repository: kubernetes
Issue: TOB-K8S-013: Use of InsecureSkipVerify and other TLS weaknesses
Labels: kind/bug,area/security,sig/auth,priority/important-longterm,lifecycle/frozen,wg/security-audit

This issue was reported in the [Kubernetes Security Audit Report](https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Final%20Report.pdf)

**Description**
Kubernetes uses Transport Layer Security (TLS) throughout the system to connect disparate components. These include kube-proxy, kubelets, and other core, fundamental components of a working cluster. However, Kubernetes does not verify TLS connections by default for certain connections, and portions of the codebase include the use of InsecureSkipVerify, which precludes verification of the presented certificate (Figure 11.1).

```
if dialer != nil {
	// We have a dialer; use it to open the connection, then
	// create a tls client using the connection.
	netConn, err := dialer(ctx, "tcp", dialAddr)
	if err != nil {
		return nil, err
	}
	if tlsConfig == nil {
		// tls.Client requires non-nil config
		klog.Warningf("using custom dialer with no TLSClientConfig. Defaulting to InsecureSkipVerify")
		// tls.Handshake() requires ServerName or InsecureSkipVerify
		tlsConfig = &tls.Config{
			InsecureSkipVerify: true,
		}
	// ...
}
```
Figure 11.1: An example of InsecureSkipVerify in kubernetes-1.13.4/staging/src/k8s.io/apimachinery/pkg/util/proxy/dial.go

**Exploit Scenario**
Alice configures a Kubernetes cluster for her organization. Eve, a malicious privileged attacker with sufficient position, launches a man-in-the-middle attack against the kube-apiserver, allowing her to view all of the secrets shared over the channel. 

**Recommendation**
Short term, audit all locations within the codebase that use InsecureSkipVerify, and move towards a model that always has the correct information present for all TLS connections in the cluster. 

Long term, default to verifying TLS certificates throughout the system, even in non-production configurations. There are few reasons to support insecure TLS configurations, even in development scenarios. It is better to default to secure configurations than to insecure ones that may be updated. 


**Anything else we need to know?**:

See #81146 for current status of all issues created from these findings.

The vendor gave this issue an ID of TOB-K8S-013 and it was finding 11 of the report.

The vendor considers this issue Medium Severity.

To view the original finding, begin on page 38 of the [Kubernetes Security Review Report](https://github.com/kubernetes/community/blob/master/wg-security-audit/findings/Kubernetes%20Final%20Report.pdf)

**Environment**:

- Kubernetes version: 1.13.4