sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Multiple Optional Catchall Routes with overlapping patterns fails to correctly fall-back in dev mode
Labels: good first issue,Navigation

# Bug report

## Describe the bug
While next is in dev mode, it fails to build appropriate catchall route when multiple catchalls exist with overlapping patterns. For example, a page at `pages/[[...foo]].js/` will not be built if `pages/[bar]/[[...bazz.js]]` exists, until first navigating to the homepage `/` to force a build of `[[...foo]]`

## To Reproduce
Created an example branch with this behavior 
https://github.com/brandondc741/next-catchall-route-bug

Repro steps are located in https://github.com/brandondc741/next-catchall-route-bug/blob/master/HOW_TO_REPLICATE_ISSUE.md

1. `npx next dev`
2. *First* visit /foo/root
3. Observe 404
4. visit /
5. Observe page renders, [[...slug]] builds
6. visit /foo/root
7. Observe page now renders

## Expected behavior
In dev mode, when next.js is given the path `/foo/root` it should
1. Attempt to render `pages/[firstSegment]/[[...nestedSlug]].js`
2. Fall-back to attempting to render `[[...slug]].js`

## System information

- OS: macOS
- Version of Next.js: 9.5.3
- Version of Node.js: 12.18.0
Repository: node
Issue: Test arm7 on Actions with qemu
Labels: build

No intention of dropping Jenkins ARM tests for now, but this should give us better coverage on Actions as well as serve as a testing ground for using qemu instead of bare metal hosts. Maybe after some time if we gather enough confidence in this method we can re-evaluate how we do those tests in Jenkins.

---

![image](https://user-images.githubusercontent.com/4048656/94316990-3f18d700-ff3a-11ea-9338-8f270bb5155a.png)

👀

(I might be derailing this issue, will open a tracking issue on nodejs/node)

_Originally posted by @mmarchini in https://github.com/nodejs/TSC/issues/931#issuecomment-699161021_
Repository: PowerToys
Issue: [KBM] Shortcut remaps can be optimized
Labels: Product-Keyboard Shortcut Manager,Area-Quality,Issue-Task

Currently the [ShortcutRemap](https://github.com/microsoft/PowerToys/blob/master/src/modules/keyboardmanager/dll/KeyboardEventHandlers.cpp#L179) code iterates through the list of shortcut remaps and checks if any of them match the current key selection or if it is a subset of it (for shortcut to key). Since these are stored in `std::map`, similar to what is done for single key remaps, it should be possible to directly find it by the map key rather than iterating. This could improve performance if the user has many remappings for a particular app or many global remappings.
Repository: flutter
Issue: Better rationale should be documented for using GlobalKeys
Labels: framework,f: material design,d: api docs,P2,team-design,triaged-design

Per @HansMuller in https://github.com/flutter/flutter/pull/66504 

> We should provide a better rationale for this approach than expediency. The cost of Scaffold.of(context) is constant (not proportional to context's depth). The example that follows does cover the case where the key is useful.

This is in regards to documentation comments like:

https://github.com/flutter/flutter/blob/2adb91895c5ef6aad5c27c72734962a2f1513a8d/packages/flutter/lib/src/material/scaffold.dart#L1460
Repository: terminal
Issue: Convert LocalTests_SettingsModel into UnitTests_SettingsModel
Labels: Product-Terminal,Issue-Task,Area-CodeHealth

# Description of the new feature/enhancement

#7667 introduces the TerminalSettingsModel by ripping out a large chunk of TerminalApp. All of the testing was thrown into LocalTests_SettingsModel. Moving them into a unit tests project like TermApp.UnitTests allows us to run these in CI.

About 20/33 tests are able to be moved into a UnitTests-like project with no modifications.
2/33 can be moved with minor modifications (see below).
The remaining 11/33 require a larger refactor (this issue tracks this).

# Proposed technical implementation details (optional)

`SettingsModelLocalTests::KeyBindingsTests`
- All of these tests fail because they need to construct a `KeyChord`. `KeyChord` is in the `TerminalControl` namespace.

`SettingsModelLocalTests::CommandTests`
- `TestResourceKeyName` and `TestLayerOnAutogeneratedName` fail because they need access to the resource loader.

`SettingsModelLocalTests::SerializationTests`
- The tests below fail because they need to import defaults.json. Which results in hitting the two cases above.
   - `TestReorderWithNullGuids`
   - `TestReorderingWithoutGuid`
   - `TestLayeringNameOnlyProfiles`
   - `TestExplodingNameOnlyProfiles`
   - `TestDontLayerGuidFromUserDefaults`
   - `ValidateKeybindingsWarnings`
- `TestCommandsAndKeybindings` doesn't import defaults.json, but fails again because it hits the two cases above.
- The two tests that can be fixed fairly easily are `ValidateLegacyGlobalsWarning` and `TestTrailingCommas`. They don't really need a dependency on importing defaults.json.
Repository: vscode
Issue: Selecting 2 color values and changing them both with color picker
Labels: help wanted,feature-request,editor-color-picker

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
As the title says, it would be a very nice feature if you could select 2 identical color values (HEX, RGB or HSL) and change them both at once with the color picker.

The value does not change for the 2nd selected option when changing colors

![j3XxbaQ4Ux](https://user-images.githubusercontent.com/18307183/94331305-45ca3d00-ff80-11ea-9cab-df7b8834b981.gif)
Repository: TypeScript
Issue: Compiler API: Please mark TransformationContext.addInitializationStatement as public API
Labels: Needs Investigation

<!-- 🚨 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

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Suggestion

<!-- A summary of what you'd like to see added or changed -->

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

## Examples

<!-- Show how this would be used and what the behavior would be -->

## Checklist

My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [ ] This wouldn't change the runtime behavior of existing JavaScript code
* [ ] This could be implemented without emitting different JS based on the types of the expressions
* [ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: flutter
Issue: [url_launcher] Support requiring non-browser for `launchUrl` on Android
Labels: platform-android,p: url_launcher,package,c: proposal,P3,has partial patch,team-android,triaged-android

## Use case

I am implementing OAuth2.0 (for Amazon Alexa, but this could apply for any OAuth provider with similar setup), the provider recommends that the deeplink/applink should be used to authorize, if the app is installed in the device and as a fallback use webview/in-app browser tab.

For iOS the use case is solved with `universalLinksOnly` option in `launch`. For Android `canLaunch` returns `true` since the applink is of scheme `https`. Alternative could be to use `PackageManager` to check if app is installed on device - this requires additional entries in `<queries>` in `AndroidManifest.xml` but this is [not recommended](https://developer.android.com/training/basics/intents/package-visibility-use-cases) by Android for just url launch use case.

## Proposal
- add optional `onlyNonBrowser` (defaults to `false`) argument to `canLaunch` method
- for android:  if `onlyNonBrowser` is `true`, add `FLAG_ACTIVITY_REQUIRE_NON_BROWSER `  flag to intent before `resolveActivity` is called [docs](https://developer.android.com/training/basics/intents/package-visibility-use-cases#let-non-browser-apps-handle-urls)

## Caveats
- As far as I know this can be only implemented for android platform.
Repository: node
Issue: doc: Options passed needlessly to https request object and agent prop
Labels: https,doc

# 📗 API Reference Docs Problem

<!--

Thank you for wanting to make nodejs.org better!

This template is for issues with the Node.js API
reference documentation.

For problems with nodejs.org beyond the API
reference documentation, please open an issue
using the issue tracker for our site repository.

  https://github.com/nodejs/nodejs.org

For more general support, please open an issue
using the issue tracker for our help repository.

  https://github.com/nodejs/help

---

For the issue title, please enter a one-line
summary after “doc: ” (preferably 50 characters
or less and no more than 72).

The “✍️” are placeholders signifying requests for
input. Replace them with your responses.

If you are unsure of something, do your best.

-->

<!-- The output of “node --version”. -->

- **Version**: v14.12.0

## Location
Affected URL(s):

- https://nodejs.org/api/https.html#https_https_request_options_callback

## Description
<!-- If applicable, include any screenshots that
may help solve the problem. -->

In the following example provided for the https.request method, the request config object is passed both to the top level https request object, and to the agent property of said object. 
This seems to either be a typo, or unclear. I would expect to see the following: 

- "key" and "cert" should be provided to the agent object only, and should not appear at the top level of the options object.
- The properties that comprise the URL object ("hostname",  "port", "path" and "method") should not be provided to the agent object. 

I think this would avoid confusion.

```
const options = {
  hostname: 'encrypted.google.com',
  port: 443,
  path: '/',
  method: 'GET',
  key: fs.readFileSync('test/fixtures/keys/agent2-key.pem'),
  cert: fs.readFileSync('test/fixtures/keys/agent2-cert.pem')
};
options.agent = new https.Agent(options);

const req = https.request(options, (res) => {
  // ...
});
```
Repository: create-react-app
Issue: Jest configuration support for "setupFiles"
Labels: issue: proposal,needs triage

### Is your proposal related to a problem? 

I'm trying to test localStorage with https://www.npmjs.com/package/jest-localstorage-mock which requires some minor configuration setup in the package.json however when I try to add the following to my package.json

```
  "jest": {
    "setupFiles": ["jest-localstorage-mock"]
  }
```

I get the following error message: 

```
Out of the box, Create React App only supports overriding these Jest options:

  • clearMocks
  • collectCoverageFrom
  • coveragePathIgnorePatterns
  • coverageReporters
  • coverageThreshold
  • displayName
  • extraGlobals
  • globalSetup
  • globalTeardown
  • moduleNameMapper
  • resetMocks
  • resetModules
  • restoreMocks
  • snapshotSerializers
  • transform
  • transformIgnorePatterns
  • watchPathIgnorePatterns.

These options in your package.json Jest configuration are not currently supported by Create React App:

  • setupFiles

If you wish to override other Jest options, you need to eject from the default setup. You can do so by running npm run eject but remember that this is a one-way operation. You may also file an issue with Create React App to discuss supporting more options out of the box.

error Command failed with exit code 1.
```
### Describe the solution you'd like

I'f possible, I'd like out of the box support for this as I don't want to run `npm run eject`

### Describe alternatives you've considered

(Write your answer here.)

### Additional context

https://www.npmjs.com/package/jest-localstorage-mock
https://jestjs.io/docs/en/configuration.html#content

(Write your answer here.)
Repository: rust
Issue: allow_internal_unstable silently ignores typos in feature names
Labels: A-attributes,C-bug

While working on #77088 I wasted a lot of time looking for a bug in my code, when the issue was that I made a typo in the feature name in my test case.

I think it would make sense to check that the feature to be allowed actually exists.
Repository: storybook
Issue: Docs slowing down reloading
Labels: performance issue,addon: docs,block: argstable

Reloading changes made to a component is super slow.
The build process hangs on `70% - sealing React Docgen Typescript Plugin` for 2-3 seconds. Then, tons of `react-syntax-highlighter` entries are output in the list of built files.

I'm using [react-boilerplate-cra-template](https://github.com/react-boilerplate/react-boilerplate-cra-template/issues) with storybook added via `npx sb init`.

I'm not using the docs addon at all.

I've changed `main.js` to:
```
const resolve = require('path').resolve;
module.exports = {
  stories: ['../src/**/*.stories.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
  addons: [
    '@storybook/addon-links',
    '@storybook/preset-create-react-app',
    {
      name: '@storybook/addon-essentials',
      options: {
        docs: false,
      },
    },
  ]
};

```
The `react-syntax-highlighter` files no longer pop up in the list of built files, but the process is still quite slow and it hangs 
on `70% - sealing React Docgen Typescript Plugin`
```
Environment Info:

  System:
    OS: Linux 5.4 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
  Binaries:
    Node: 12.18.3 - ~/.nvm/versions/node/v12.18.3/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.6 - ~/.nvm/versions/node/v12.18.3/bin/npm
  Browsers:
    Chrome: 85.0.4183.102
    Firefox: 80.0.1
  npmPackages:
    @storybook/addon-actions: ^6.0.21 => 6.0.21 
    @storybook/addon-essentials: ^6.0.21 => 6.0.21 
    @storybook/addon-links: ^6.0.21 => 6.0.21 
    @storybook/node-logger: ^6.0.21 => 6.0.21 
    @storybook/preset-create-react-app: ^3.1.4 => 3.1.4 
    @storybook/react: ^6.0.21 => 6.0.21 
```
Repository: godot
Issue: Puppet functions callable locally from non-network master
Labels: bug,topic:network,topic:multiplayer

**Godot version:** 3.2.3
**OS/device including version:** Windows 10
**Issue description:** The puppet and puppetsync annotated functions still receive calls from other puppet clients, not just the master.

According to this line: https://github.com/godotengine/godot/blob/00949f0c5fcc6a4f8382a4a97d5591fd9ec380f8/core/io/multiplayer_api.cpp#L92-L94 puppet functions should only be callable from the network master but this is not the case.

**Steps to reproduce:**
Create a puppet function, try call an rpc from the server - this will work.
Try call this same puppet function from a client which isn't the network master - it will still call the puppet function

**Example code:**

```
puppet func puppet_rpc():
	print('rpc_sender: %d' % get_tree().get_rpc_sender_id())
	print('network master: %d' % get_network_master())
```

If I call this from the master (server) and then a client this is what I see in the logs of the client:

```
rpc_sender: 1
network master: 1
rpc_sender: 510900438
network master: 1
```

I would not expect the second call to happen as the the sender id != master id
Repository: create-react-app
Issue: Get new jest and eslint
Labels: stale,needs triage,issue: bug report

Can we please upgrade inside react-scripts dependencies.

 eslint    6.8.0  →    7.9.0   
 jest    ^24.9.0  →  ^26.4.2   

Thanks.
Repository: youtube-dl
Issue: add extractor [www.believe.online]
Labels: site-support-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 2020.09.20. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support 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 new site support request
- [x] I've verified that I'm running youtube-dl version **2020.09.20**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://www.believe.online/player/2859

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Add this site, please. I'll send credentials by email when some dev answer this issue
Repository: kubernetes
Issue: Create E2E test for CVE-2020-8559 and similar
Labels: sig/api-machinery,sig/auth,help wanted,lifecycle/frozen,sig/security

@tabbysable Any interest in turning your POC into a Kubernetes E2E test? I was intending to use the overridden redirect feature added in https://github.com/kubernetes/kubernetes/pull/92850 as the basis for the E2E.

_Originally posted by @tallclair in https://github.com/kubernetes/kubernetes/issues/92914#issuecomment-663230309_
Repository: storybook
Issue: Allow viewport width/height fields to be editable + draggable viewport
Labels: feature request,addon: viewport

**Describe the solution you'd like**
When a viewport is selected, it shows the width and the height and allows them to be swapped, it would be nice if we could also edit those fields as number inputs. It would also be useful to make the right and bottom of the canvas draggable.

**Describe alternatives you've considered**
I realise there is an add-on called taffy which adds this behaviour, but I am not sure it is maintained and the viewport plugin looks more inline with storybook's design.

**Are you able to assist to bring the feature to reality?**
Yes I can take a shot at implementing this.
Repository: terminal
Issue: Minimize button glyph is one pixel too high
Labels: Help Wanted,Area-UserInterface,Product-Terminal,Issue-Task,Priority-3

![Windows Terminal Minimize Button](https://user-images.githubusercontent.com/71948533/94351343-0f5ff100-0058-11eb-92c7-77e425713b12.jpg)
# Description of the new feature/enhancement
The minimize button glyph is one pixel higher than all other window decorations and should be moved down by one pixel. The current design of the minimize button deviates from the rest of the Windows 10 UI by shifting the minimize button one pixel above the center-line of the other window control buttons instead of one pixel below. Ignoring all the other issues with Windows 10 and the design inconsistencies, it should at least be attempted to maintain consistency in the positioning of the window control elements.
Repository: flutter
Issue: Transparent Backgrounds for Linux
Labels: c: new feature,framework,engine,e: embedder,platform-linux,c: proposal,a: desktop,P3,team-linux,triaged-linux

<!-- 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 out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

My use case is definitely weird, but I think there could be some other uses for supporting this feature. I'm building a dock that renders above other apps, but not only do I want to hide the title bar (which I believe can be done with GTK stuff in the Linux files), I would also like to hide the background fully for custom window shapes. 
<!--
     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 the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

I'd like to have a system to allow transparent backgrounds on desktop platforms, iOS and Android already seemingly have this. Two limitations stand in the way of this, firstly GTK will render a black background behind Flutter, which is once again something that should be able to be fixed in GTK via the C++ files in the Linux folder. Secondly, when setting the background color to transparent on flutter, it errors.

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->