sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Pashto for Cupertino localization is missing 
Labels: framework,a: internationalization,f: cupertino,a: error message,P2,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

HI, I found that cupertino_ps.arb file is missing. 

It's needed for Pashto Cupertino  localisation. 

### Expected results

cupertino_ps.arb  file

### Actual results

ERROR: No CupertinoLocalizations found.

### Code sample

localizationsDelegates: context.localizationDelegates

### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

[✓] Flutter (Channel master, 3.6.0-5.0.pre.28, on macOS 13.3.1 22E772610a darwin-arm64, locale en-FI)
    • Flutter version 3.6.0-5.0.pre.28 on channel master at
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 69269602ea (6 months ago), 2022-11-18 01:52:25 -0500
    • Engine revision 4ca2c1d78f
    • Dart version 2.19.0 (build 2.19.0-406.0.dev)
    • DevTools version 2.19.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at
    • Platform android-33, build-tools 32.1.0-rc1
    • ANDROID_HOME = 
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7772763)

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile) • emulator-5554                        • android-arm64  • Android 12 (API 32) (emulator)
    • iPhone 14 Pro Max (mobile)  • AB32839D-107A-44BC-AC62-F6648C14325F • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-4 (simulator)
    • macOS (desktop)             • macos                                • darwin-arm64   • macOS 13.3.1 22E772610a darwin-arm64
    • Chrome (web)                • chrome                               • web-javascript • Google Chrome 113.0.5672.126

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!
Process finished with exit code 0
Repository: go
Issue: x/pkgsite/cmd/pkgsite: local pkgsite with -proxy doesn't use netrc auth to private GOPROXY
Labels: pkgsite

### What did you do?

Attempted to use a .netrc file to provide credentials to pkgsite for use when fetching via a private GOPROXY. 

The regular `go mod` commands are able to do this, so with a properly configured .netrc file the following succeeds:
```
GOPROXY="https://goproxy.company.com" go mod download -x github.company.com/org/repo@latest
```

But attempting to view the documentation of github.company.com/org/repo via pkgsite:
```
GOPROXY="https://goproxy.company.com" pkgsite -proxy
```
Fails with 401 authentication errors as the [internal/proxy/client.go](https://github.com/golang/pkgsite/blob/master/internal/proxy/client.go) code doesn't attempt to insert authentication headers, unlike cmd/go which [does](https://github.com/golang/go/blob/d0c72c23dcb5afc80918686f18c14c870eacbd1c/src/cmd/go/internal/auth/auth.go#L10-L28)

### What did you expect to see?

pkgsite should be able to use authentication against a private GOPROXY

### What did you see instead?

pkgsite does not pass authentication headers to the http requests it makes to a private GOPROXY
Repository: bitcoin
Issue: Include torrent in binary download verification 
Labels: Brainstorming,Scripts and tools

The binary verification script currently covers bitcoin(core).org but not the torrents. We should add an option to download and verify those as well.
Repository: terminal
Issue: Add a "Tab Overview" view
Labels: Issue-Feature,Area-UserInterface,Product-Terminal

Found while perusing mastodon last night. 

We should shamelessly copy the "Tab Overview" from GNOME's "Console"[^1] 

![](https://149677182.v2.pressablecdn.com/wp-content/uploads/2023/02/gnome-console-tab-overview.gif)

It's like, Alt+tab, or tab un-zoom

Technical issues:
* We'd have to pre-render each tab & termcontrol
  * This would be harder with #997
* Is this a separate... `Page`? that we switch to temporarily, then switch back?
* What happens to the tab row during this?
* Animations are cool but also hard so skip those for a v1

[^1]: Which is different from gnome terminal
Repository: godot
Issue: Flickering on Android
Labels: bug,platform:android,topic:rendering,needs testing,topic:3d

### Godot version

v4.0.2.stable.official [7a0977ce2]

### System information

Samsung SM-A530F, Chipset: exynos5,OpenGl:3.0.2,CPU: arm64-v8a

### Issue description


https://github.com/godotengine/godot/assets/122531384/0b4cf7cc-d287-49b8-9a41-f5be0825a25e



### Steps to reproduce

Renderer: Mobile

### Minimal reproduction project

N/A
Repository: storybook
Issue: [Bug]: Enriched source displayed in storysource panel
Labels: bug,help wanted,has workaround,addon: storysource,addon: docs,sev:S3

### Describe the bug

When combining `@storybook/addon-storysource` with `@storybook/addon-docs` the code panel shows a re-formatted source code (eliminating blank lines) and the story parameters added by [enrichCsf](https://github.com/storybookjs/storybook/blob/7d2a090c2afacaaa0a06d82b50bb3764f507e7fc/code/lib/csf-tools/src/enrichCsf.ts).

To correctly display the sources in the Code panel I had to turn-off the `csfPluginOptions` in `addon-docs`.

Example source with `addon-docs` (default config, that includes the CSF plugin). Notice the removal of new lines and the addition of `Demo.parameters` at the end:

```ts
import { useState } from 'react';
import { Button } from './Button';
export default {
  title: 'Components/Button',
  component: Button,
};
export const Demo = () => <Button>Contained Primary</Button>
Demo.parameters = {
  ...Demo.parameters,
  docs: {
    ...Demo.parameters?.docs,
    source: {
      originalSource: "() => <Button>Contained Primary</Button>",
      ...Demo.parameters?.docs?.source
    }
  }
};
```

The source shown in the panel without `addon-docs`:

```ts
import { useState } from 'react';

import { Button } from './Button';

export default {
  title: 'Components/Button',
  component: Button,
};

export const Demo = () => <Button>Contained Primary</Button>
```

Expected behavior: I expect the `Code` panel to show the source without the parameters and preserving new lines spaces. It seems that the CSF plugin is processing the source that is consumed by other plugins.

### To Reproduce

1. Reproduction: https://stackblitz.com/edit/github-myey4b?file=src/stories/Button.stories.ts
2. Go to the Button story and look at the Code panel at the bottom
3. Scroll to the end. Notice the additional parameters added to the source.

The reproduction (using the alpha version) shows the new lines correctly. However, it still adds the additional parameters.

### System

```shell
My local machine env:

System:
    OS: macOS 13.3.1
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
  Binaries:
    Node: 18.14.0
    Yarn: 1.22.19
    npm: 9.6.2
  Browsers:
    Chrome: 113.0.5672.126
    Safari: 16.4
  npmPackages:
    @storybook/addon-coverage: ^0.0.8 => 0.0.8
    @storybook/addon-docs: ^7.0.12 => 7.0.12
    @storybook/addon-storysource: ^7.0.12 => 7.0.12
    @storybook/addon-toolbars: ^7.0.12 => 7.0.12
    @storybook/blocks: ^7.0.12 => 7.0.12
    @storybook/manager-api: ^7.0.12 => 7.0.12
    @storybook/react: ^7.0.12 => 7.0.12
    @storybook/react-webpack5: ^7.0.12 => 7.0.12
    @storybook/theming: ^7.0.12 => 7.0.12
```

However, the issue is also visible in the StackBlitz env using `7.1.0-alpha.19`.

### Additional context

This seems to be related to: https://github.com/storybookjs/storybook/pull/21159
Repository: pytorch
Issue: Can group convolution support other grouping methods?
Labels: module: convolution,triaged

### 🚀 The feature, motivation and pitch

I'm using group convolution, but I want to use a new grouping method. For example, I have a tensor called "a" with shape `[b, 256*3, h, w]`. I want to group `a[:, 0, :, :], a[:, 256, :, :], a[:, 256*2, :, :]` into one group, and `a[:, 1, :, :], a[:, 1+256, :, :], a[:, 1+256*2, :, :]` into another group, and so on, ultimately dividing it into 256 groups where each group is a tensor of shape `[b, 3, h, w]`. Then I want to perform group convolution with the number of groups set to 256. In other words, the grouping stride becomes 256. How can I achieve this? Can the nn.conv2D function handle this?
By the way, group convolution seems to be slower than regular convolution, which is contrary to theory. Is this due to optimization issues or is my torch version too low?

### Alternatives

_No response_

### Additional context

_No response_
Repository: next.js
Issue: Catch all routes does not work for edge runtime
Labels: Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Command 'next' not found, but can be installed with:
sudo apt install mailutils-mh  # version 1:3.14-1, or
sudo apt install mmh           # version 0.4-4
sudo apt install nmh           # version 1.7.1-11
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/dberhane/next13-testing

### To Reproduce

created a catchall route file at: src/app/route-testing/[[...slug]]

```
export const runtime = "edge"

const Page = () => (
    <div>
        <h1>Catch all route testing</h1>
    </div>
    );

export default Page;   
``` 

Catch all routing works only for the default nodejs runtime. When edge runtime is enabled as above it fails with the error "unhandledRejection: Error: Catch-all must be the last part of the URL"

### Describe the Bug

Catch all routing works only for the default nodejs runtime. When edge runtime is enabled it fails with the following error message:

```
- error unhandledRejection: Error: Catch-all must be the last part of the URL.
    at UrlNode._insert (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/shared/lib/router/utils/sorted-routes.js:54:19)
    at UrlNode._insert (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/shared/lib/router/utils/sorted-routes.js:136:40)
    at UrlNode._insert (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/shared/lib/router/utils/sorted-routes.js:136:40)
    at UrlNode.insert (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/shared/lib/router/utils/sorted-routes.js:7:14)
    at eval (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/shared/lib/router/utils/sorted-routes.js:159:46)
    at Array.forEach (<anonymous>)
    at getSortedRoutes (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/shared/lib/router/utils/sorted-routes.js:159:21)
    at DefaultRouteMatcherManager.reload (webpack-internal:///(sc_client)/./node_modules/next/dist/esm/server/future/route-matcher-managers/default-route-matcher-manager.js:109:101)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  digest: undefined
}
```


### Expected Behavior

When the catchall route page is accessed at "http://localhost:3000/route-testing" it should display the page without any error message:

![Screenshot from 2023-05-19 14-20-13](https://github.com/vercel/next.js/assets/645060/e543656a-b4e5-483c-a8c5-d24c8f5cc8e8)

It works fine when the edge runtime is disabled.


### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: angular
Issue: Document queries/query parameters better
Labels: P3,area: docs

### Describe the problem that you experienced

Today I started to work with queries respectively query parameters in Angular.
And I found that there seems not really any hands-on documentation (or even a tutorial) that describes the use of optional parameters in routes.

I was completely reliant on third party tutorials, have been searching for original explanations on angular.io but didn't find much.

My challenge was similar to [this one (stackoverflow)](https://stackoverflow.com/questions/58873567/passing-filter-options-to-route-in-angular).
And the [only answer](https://stackoverflow.com/a/58873771) also only refers to a third party tutorial by DigitalOcean (which from my point of view indicates that this is certainly a relevant topic, which is worth being covered in the original docs).

In fact this seems to be a *common routing task*.
Therefore it would be great to get at least some explanation about it Angular's [*Common Routing Tasks* Docs](https://angular.io/guide/router).

And from my point of view it would also be great to teach this hands-on in one of the tutorials (which isn't the case yet, as far as I know).

<!-- ### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

_No response_

### If the problem is browser-specific, please specify the device, OS, browser, and version

_No response_

### Provide any additional information here in as much as detail as you can

_No response_ -->
Repository: next.js
Issue: Empty headers in response of request proxied through `rewrites` get automatically removed. 
Labels: bug,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
I am running this on vercel.
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue or a replay of the bug

https://app.replay.io/recording/lusio-or-discover-new-games-or-track-your-gaming-portfolio-or-connect-with-other-gamers--4eed141a-022b-414e-82b5-77086de448b0

### To Reproduce

In the replay video below, please open the network terminal and look for 'signout' request.
Here, I have navigated through two environments, 
1. First one does not contain any reverse proxy from vercel and is directly hitting our API server.
2. Second one is being routed through a reverse proxy of vercel which I have configured in next.config.js.
Both these environments are actually deployed to vercel right now.

In the first `signout` request, please find that the headers 'st-access-token' and 'st-refresh-token' in the response are received by the browser as empty headers or with a value of ' '.

In the second instance where the 'signout' request goes through next's rewrite method's reverse proxy, these headers are not being received on the browser. 

### Describe the Bug

Bug here is that empty headers in response are being removed by the reverse proxy enabled through 'rewrite' method in next config. This is unexpected behaviour.

### Expected Behavior

The empty headers should be sent to browser as-is and should not be removed.

### Which browser are you using? (if relevant)

Version 113.0.5672.63 (Official Build) (arm64)

### How are you deploying your application? (if relevant)

Vercel
Repository: godot
Issue: Animation Library saves animations as binary .res instead of text .tres by default?
Labels: discussion,topic:editor,topic:animation

### Godot version

v4.0.2.stable.official [7a0977ce2]

### System information

Windows 11, Core i5-12400F, RX 6600

### Issue description

When click the disk icon and select "Save As" in Animation Library:
  - dialog has .res set as the extension and saves as binary
  - if change ext to .tres saves as text like 'normal'
  - i have never seen anything use that binary format by default in godot
  - so i thought it was an oversight? maybe not

### Steps to reproduce

n/a

### Minimal reproduction project

n/a
Repository: rust
Issue: Create Pull Request templates for common actions
Labels: T-infra,A-meta

Opening this issue so we can get central feedback from various teams on what categories of PRs we should support.

My initial list:

- [ ] New unstable library API
- [ ] Feature stabilization
- [ ] Updating subtree/submodule
- [ ] Experimental PR (`S-experimental`, `r? ghost`, opens as draft)
Repository: rust
Issue: building from source does not like if you `git init` the tree.
Labels: C-enhancement,T-bootstrap

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this shell interaction:

```
% curl -O https://static.rust-lang.org/dist/rustc-1.69.0-src.tar.gz
% tar xzf rustc-1.69.0-src.tar.gz
% cd rustc-1.69.0-src/
% git init
% ./x.py setup compiler
% ./x.py build
```

I expected to see this happen: A successful bootstrap.
Instead, this happened:  the last step there fails with:

```
Building bootstrap
    Finished dev [unoptimized] target(s) in 0.04s
thread 'main' panicked at 'command did not execute successfully: cd "/home/ubuntu/Dev/Rust/rustc-1.69.0-src" && "git" "config" "--file" "/home/ubuntu/Dev/Rust/rustc-1.69.0-src/.gitmodules" "--get-regexp" "path"
expected success, got: exit status: 1', lib.rs:631:22
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
```


This is because, I presume, our logic for inferring whether to automatically update submodules does so based on whether it sees a `.git` subdirectory (which `git init` above will create).

One can work around this specific problem by adding this to the `config.toml` generated by `x.py setup`:

```
[build]
submodules = false
```

but it would be nice to not have to workaround it at all...

and then I think we hit a different problem related to downloading LLVM... so we work around that by doing:

```
[llvm]
download-ci-llvm = false
```

(using `git init` as a cheap way to checkpoint bits of state locally before I edit them is a personal  development pattern of mine, and I wouldn't be surprised if others use it as well...)

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
<version>
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
<backtrace>
```

</p>
</details>
Repository: godot
Issue: PopupMenu ignores mouse hover to adjacent item after sub menu opened until jiggled
Labels: bug,topic:gui

### Godot version

4.1dev (6d7413b)

### System information

MacOS M1

### Issue description

Moving the mouse from a `PopupMenu` open sub menu item to another sub menu item is ignored until the mouse is jiggled. This is probably related to [#70361](https://github.com/godotengine/godot/issues/70361)

Inhibiting the `minimum_lifetime_timer` in popup_menu.cpp (effectively setting the timeout to zero) seems to mostly eliminate the issue. Keyboard navigation still works as expected, so I would propose getting rid of the lifetime timer completely.

I am wondering why there is a sub menu lifetime timer at all, because the sub menu should close instantly as soon as the mouse moves to another item. For example, this is how at least MacOS behaves. Is there a rational for the lifetime timer I'm not considering?


https://github.com/godotengine/godot/assets/33969780/4d1aa4d5-50d8-40e8-98fe-49e55f0cf170





### Steps to reproduce

See MRP below.

### Minimal reproduction project

[popup_issues.zip](https://github.com/godotengine/godot/files/11518515/popup_issues.zip)
Repository: create-react-app
Issue: require in production build
Labels: needs triage

**Description**
I have a "create react app" that imports a [third-party library](https://github.com/mzusin/toolcool-range-slider). In development all is working well, but after creating a production build, there is a console.log error in the browser. The error states: **"Uncaught ReferenceError: require is not defined".** After some investigation, I see the the generated bundle has the following code:

```js
var r = n.p + "static/media/logo.6ce24c58023cc2f8fd88fe9d219db6c6.svg",
a = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/classCallCheck.js").default,
l = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/createClass.js").default,
i = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/assertThisInitialized.js").default,
o = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/inherits.js").default,
u = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/createSuper.js").default,
s = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/wrapNativeSuper.js").default,
c = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/defineProperty.js").default,
d = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/slicedToArray.js").default,
f = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/toConsumableArray.js").default,
p = require("/Users/home/Documents/codelib/test/slider-test/node_modules/@babel/runtime/helpers/createForOfIteratorHelper.js").default;
```
It seems that after react includes the [library minified file](https://github.com/mzusin/toolcool-range-slider/blob/main/dist/toolcool-range-slider.min.js) and recompiles all the bundle, something went wrong.

**Did you try recovering your dependencies?**
I tried to remove node_modules and package-lock.json files and reinstall the dependencies, but it didn't help.

**Steps to reproduce**
Import the library:
```
import React from 'react';
import 'toolcool-range-slider';

export function App(props) {
  return (
    <div className='App'>
      <h1>require in production build</h1>
      <tc-range-slider></tc-range-slider>
    </div>
  );
}
```
Then create a production build using **npm run build**
Open the production build in a localhost server ---> you get errors in the console and the website doesn't work.

**Expected behavior**
The result bundle will not contains any "require" statements.

**Source code**
The source code example can be found [here](https://playcode.io/1478591) - https://playcode.io/1478591

I'm not sure if this is a react bug or a problem with the library (I'm the author). If the problem is in the library, could you give me some idea of what should be changed?

Thank you