sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: App crash when I create FFI template in objective-c.
Labels: c: crash,platform-ios,tool,dependency: dart,has reproducible steps,P2,found in release: 3.7,found in release: 3.8,a: plugins,team-ios,triaged-ios

https://flutter.dev/docs/development/platform-integration/c-interop
1: Create a plugin by flutter create
2: Add C/C++ sources
3: Load the code using the FFI library
4: Run on iPhone
----------
works well:
flutter create --platforms=android,ios --template=plugin native_add

crash happen:
flutter create -a java **-i objc** --platforms=android,ios --template=plugin native_add
Repository: storybook
Issue: Blocks: Clean up `useGlobals` for docs and export it
Labels: bug,help wanted,has workaround,core,addon: docs

**Describe the bug**
I need to access the globals set by toolbar addon in the custom DocPage I have set for the docs addon.
The toolbar addon documentation instructs to use the `useGlobals` hook to consume the globals within an addon.
However, when I try to use the `useGlobals` hook in the DocPage it throws an error:


```
Uncaught TypeError: Cannot read property 'updateGlobals' of undefined
    at useGlobals (index.js:550)
    at page (button.stories.tsx:67)
    at renderWithHooks (react-dom.development.js:16260)
    at mountIndeterminateComponent (react-dom.development.js:18794)
    at beginWork$1 (react-dom.development.js:20162)
    at HTMLUnknownElement.callCallback (react-dom.development.js:336)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:385)
    at invokeGuardedCallback (react-dom.development.js:440)
    at beginWork$$1 (react-dom.development.js:25780)
    at performUnitOfWork (react-dom.development.js:24698)
```

**To Reproduce**
Steps to reproduce the behavior:

1. Add a custom doc page globally or on component or story level
1. Use the `useGlobals` hook in the custom docs page
1. Go to storybook and the docs tab
1. Check the browser dev tools console for the error

**Expected behavior**
Expected to render the doc page without errors and have access to the globals.

**Code snippets**
Here's the code from my `DocsPage.tsx` file:


```ts
import * as React from "react";

import {
  ArgsTable,
  Description,
  PRIMARY_STORY,
  Primary,
  Stories,
  Subtitle,
  Title,
} from "@storybook/addon-docs/blocks";

import { useGlobals } from "@storybook/api";

export const DocsPage = () => {
  const [globals] = useGlobals();

  return (
      <Title />
      <Subtitle />
      <Description />
      <Primary />
      <ArgsTable story={PRIMARY_STORY} />
      <Stories />
  );
};
```

And here's how I set the doc page in `preview.ts` file with `addParameters` function:


```ts
addParameters({
  viewport,
  options: { storySort, theme },
  controls: { hideNoControlsWarning: true },
  docs: {
    page: DocsPage
  },
});
```

**System**
Environment Info:

  System:
    OS: macOS Mojave 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 12.18.2 - ~/.nvm/versions/node/v12.18.2/bin/node
    Yarn: 1.22.4 - ~/.yarn/bin/yarn
    npm: 6.14.5 - ~/.nvm/versions/node/v12.18.2/bin/npm
  Browsers:
    Chrome: 86.0.4240.111
    Firefox: 72.0.2
    Safari: 14.0

**Additional Info**
I'm using `@storybook/core@6.0.27` and `@storybook/addon-essentials@6.0.27`.
Repository: go
Issue: x/pkgsite: trim the non text elements from subdirectories synopsis
Labels: help wanted,NeedsInvestigation,pkgsite,pkgsite/dochtml

synopsis [here](https://beta.pkg.go.dev/sevki.org/x) (I believe this is the line https://github.com/golang/pkgsite/blob/master/content/static/html/pages/subdirectories.tmpl#L19) looks really awkward
![image](https://user-images.githubusercontent.com/429977/97860257-c146a900-1cf9-11eb-9b7a-f9e46928dbde.png)
as opposed to the 
![image](https://user-images.githubusercontent.com/429977/97860584-4af67680-1cfa-11eb-887a-67d424b0349d.png)

may I suggest rendering that synopsis to html and removing all non text html elements from that section? something like this might work
```go
depth := 0
summary := bytes.NewBuffer(nil)
for {
	tt := z.Next()
	switch tt {
	case html.ErrorToken:
		break
	case html.TextToken:
		summary.Write(z.Text())
}
return summary.String()
```
Repository: create-react-app
Issue: Port issues sarting projects simultaneously
Labels: stale,needs triage,issue: bug report

### Problem
I have three projects which I've made a script to start simultaneously, so the script creates the following procedure:

1. npm run start project-a
2. npm run start project-b
3. npm run start project-c
4. The console asks if i want to start project-b  on another port than 3000 since it is already in use by project-a.
5. I confirm to start the project on another port than 3000 and it tires 3001 and start correctly
6. Now the console asks if i want to start project-c on another port than 3000 since it is in use by project-a.
7. I confirm to start the project on another port and then it crashes 
8. I start the project c again and it asks if i want to start on another port where i confirm the start and it start fine on the port 3002.

I would expect the process/port to start a 3002 if 3001 is in use, as it does if i do the step by step setup.


### Environment

I use node 12.16.2
Repository: next.js
Issue: locale negotiation is incorrect for i18n routing
Labels: Internationalization (i18n)

# Bug report

## Describe the bug

If I send Accept-Language: "fr-XX,en" and I have available locales fr, en, it should give me fr instead of en (current behavior)

## To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

## Expected behavior

Should be routed to fr

## Screenshots

If applicable, add screenshots to help explain your problem.

## System information

- OS: [e.g. macOS, Windows]
- Browser (if applies) [e.g. chrome, safari]
- Version of Next.js: [e.g. 6.0.2]
- Version of Node.js: [e.g. 10.10.0]

## Additional context

Add any other context about the problem here.
Repository: flutter
Issue: Provide method and/or config to programmatically scroll to ListView index
Labels: c: new feature,framework,f: scrolling,would be a good package,c: proposal,P3,team-framework,triaged-framework

Hello,

I know there is already a (now closed) issue with the same name, #12319. The issue righty mentions how there are ways to accomplish the required functionality when developing native apps for iOS and Android. However, the issue was closed, since [scrollable_positioned_list](https://pub.dev/packages/scrollable_positioned_list) was released. I am sure it does for some, but there use cases it does not cover, such as:

- Animated insertion and removal
- CustomScrollView/Slivers in general

Flutter is great, but in my experience, any mobile development platform is as good as it's listview that supports large data sets ;) 

Would you please consider adding something like this?
Repository: godot
Issue: Vulkan: `RenderingServer.texture_set_shrink_all_x2_on_set_data()` not reimplemented yet
Labels: topic:core,topic:rendering,regression

**Godot version:** Git https://github.com/godotengine/godot/commit/be14d9d6448a9017c982fd7e30631525aed8f339

**OS/device including version:** Fedora 33

**Issue description:**

`RenderingServer.texture_set_shrink_all_x2_on_set_data()` is not reimplemented yet. For those wondering, this is a method that shrinks all loaded textures by a 2× factor. This can be used to [reduce aliasing on downsampling](https://docs.godotengine.org/en/latest/tutorials/viewports/multiple_resolutions.html#reducing-aliasing-on-downsampling) while lowering memory usage (unlike enabling mipmaps, which will *increase* memory usage).

For 3D, perhaps an upcoming [texture streaming](https://github.com/godotengine/godot-proposals/issues/3177) API will be a better replacement to this method, but we should probably have some kind of replacement in 4.0 anyway. The current method doesn't offer any control over *which* textures will be downscaled, which can be problematic for 3D games or games where you want to keep UI elements sharp at all times.
Repository: godot
Issue: Cannot use localized resx files in exported game
Labels: bug,topic:dotnet

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:** 3.2.3.stable.mono
<!-- Specify commit hash if using non-official build. -->


**OS/device including version:** Windows 10 2004 (also tested in Ubuntu VM)
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->


**Issue description:**
<!-- What happened, and what was expected. -->
When I use `.resx` file and its localized counterpart, I am getting the right string (`ResourceManager` respects `CultureInfo.CurrentCulture`) when running the game from Godot Editor, but string fallbacks to the default (unlocalized one) when running exported project.

Probably relevant: https://github.com/mono/mono/issues/19928
Mentioned workaround doesn't work in exported project since all assemblies seem to be packed into `.pck` file.

**Steps to reproduce:**
1. Create Mono project
2. Add `resx` file 
3. Add localized `resx` file
4. Export project with default Windows or Linux template

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[ResxLocalizationProblemMinimum.zip](https://github.com/godotengine/godot/files/5476777/ResxLocalizationProblemMinimum.zip)
Repository: electron
Issue: Add a method to open a fullscreen window next to the current fullscreen window (split view)
Labels: enhancement :sparkles:

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

### Problem Description

This is a feature request. I'm trying to replicate a behavior from macOS' Mail.app, where replying to an email while in fullscreen opens a second window next to the current one (see preview):

![Kapture 2020-11-02 at 18 22 38](https://user-images.githubusercontent.com/541628/97898640-6a13f900-1d38-11eb-8b22-f16ba3a31417.gif)

I haven't found any way to do this using Electron's API. It would be nice to have it available as an option (e.g. `splitView`) when creating or showing a window. Unfortunately, I don't have any experience with native macOS APIs, otherwise I would create a PR for this.
Repository: pytorch
Issue: torch.save has a maximum size regardless of RAM
Labels: module: docs,module: serialization,triaged,function request

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->

## To Reproduce

```
import torch

limit =      2147483647
over_limit = 2147483648

x = torch.zeros(limit)
torch.save(x, 'under_limit.pt')
x = torch.zeros(over_limit) 
torch.save(x, 'over_limit.pt')  # fails
```

Traceback: 
```
Traceback (most recent call last):
  File "I_dont_think_you_need_my_path/2020-11-02_max_torch_save/03_torch_save_failing.py", line 9, in <module>
    torch.save(x, 'over_limit.pt')
  File "C:\Users\mi_so\.conda\envs\conda_base\lib\site-packages\torch\serialization.py", line 363, in save
    _save(obj, opened_zipfile, pickle_module, pickle_protocol)
  File "C:\Users\mi_so\.conda\envs\conda_base\lib\site-packages\torch\serialization.py", line 475, in _save
    zip_file.write_record(name, storage.data_ptr(), num_bytes)
TypeError: write_record(): incompatible function arguments. The following argument types are supported:
    1. (self: torch._C.PyTorchFileWriter, arg0: str, arg1: str, arg2: int) -> None
    2. (self: torch._C.PyTorchFileWriter, arg0: str, arg1: int, arg2: int) -> None

Invoked with: <torch._C.PyTorchFileWriter object at 0x00000204636340F0>, 'data/2217904421808', 2218188488832, -8589934592
```
<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior
The tensor should be saved without error. I found the numbers by testing and https://stackoverflow.com/questions/17298129/python-pickle-size-limit. 

I understand that this is mainly a pickle-issue and my workaround for the moment will be to check if a given tensor is over that limit. If it is, change to save the x.numpy() array with numpy. But I do not like it very much - is there a better option?



## Environment



python collect_env.py
```
[pip3] numpy==1.19.2
[pip3] torch==1.7.0
[pip3] torchaudio==0.7.0
[pip3] torchvision==0.8.1
[conda] blas                      1.0                         mkl
[conda] cpuonly                   1.0                           0    pytorch
[conda] mkl                       2020.2                      256
[conda] mkl-service               2.3.0            py38hb782905_0
[conda] mkl_fft                   1.2.0            py38h45dec08_0
[conda] mkl_random                1.1.1            py38h47e9c7a_0
[conda] numpy                     1.19.2           py38hadc3359_0
[conda] numpy-base                1.19.2           py38ha3acd2a_0
[conda] pytorch                   1.7.0               py3.8_cpu_0  [cpuonly]  pytorch
[conda] torchaudio                0.7.0                      py38    pytorch
[conda] torchvision               0.8.1                  py38_cpu  [cpuonly]  pytorch
```
 - OS (e.g., Linux): Win10
 - How you installed PyTorch (`conda`, `pip`, source): conda
 - Python version: 3.8.5


cc @jlin27 @mruberry
Repository: create-react-app
Issue: Multiple html outputs, differing only in header tags (OpenGraph)
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

I don't care about server-side rendering of _content_, but I do care about **headers**. In particular, [OpenGraph Headers](https://ogp.me/). I know in advance what the different headers will contain, and how many there will be.

This has to be part of the html file for google and others to display preview image/title when sending a link to someone.

```html
<meta property='og:title' content='The title shown when I send this link to a friend' />
<meta property='og:description' content='This is the description of a particular sub-page' />
<meta property='og:image' content='https://link-to-some-image...' />
<meta property='og:type' content='website'/>
```

### Describe the solution you'd like

Static config file, `outputs.xml`, (inspired by sitemap.xml):
```xml
<outputs>
  <headers path='/about'>
    <meta property='og:title' content='Example | About' />
    <meta property='og:description' content='Read about our history' />
    <meta property='og:image' content='https://link-to-some-image...' />
    <meta property='og:type' content='website'/>
  </headers>
  <headers path='/faq'>
    <meta property='og:title' content='Example | FAQ' />
    <meta property='og:description' content='Frequently Asked Questions' />
    <meta property='og:image' content='https://link-to-some-image...' />
    <meta property='og:type' content='website'/>
  </headers>
  <headers path='/contact'>
    <meta property='og:title' content='Example | Contact' />
    <meta property='og:description' content='Get in touch with us' />
    <meta property='og:image' content='https://link-to-some-image...' />
    <meta property='og:type' content='website'/>
  </headers>
  <headers path='/'>
    <meta property='og:title' content='Website' />
    <meta property='og:description' content='Some generic description' />
    <meta property='og:image' content='https://link-to-some-image...' />
    <meta property='og:type' content='website'/>
  </headers>
</outputs>
```

The `outputs.xml`-file will be used to determine the output files. The respective headers will simply be appended to the bottom of the header section in the `public/index.html` input file.

Output files based on the above `outputs.xml`-file:
```
build/
  index.html
  about/index.html
  faq/index.html
  contact/index.html
```


### Describe alternatives you've considered

#### *react-snapshot*:
 - Didn't work for me at all
 - Tries to do too much
 - Unmaintained

#### *react-snap*:
 - Kind of worked after some hours of tweaking, but caused the page to look different whether it had been statically rendered or generated in the browser.
 - Tries to do too much
 - Also seems to be unmaintained at this point.
Repository: pytorch
Issue: [RFC] Add test execution time analysis CI workflow
Labels: module: ci,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->

I propose that we add a workflow on the `main` branch that does a comparison of current test execution time against previous runs so that we can catch large time regressions early on.

Regressions that could be caught include increases to:
* Overall test suite execution time
* Individual test execution time

## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

Currently we don't have many safeguards against things that increase test execution time and thus we have issues where (if left unchecked) test times could increase without constant oversight.

## Pitch

<!-- A clear and concise description of what you want to happen. -->

1. We should create a script to analyze the test reports that come out of our test suite (example: https://github.com/pytorch/pytorch/pull/46788).
2. Create a job that stores test reports on a per commit basis and ships them to S3 (or some storage backend)
3. Create a job that downloads the most recently available test reports (by going back in the `git history` until a commit has an available report) and compares them against the current reports using the script outlined in step 1

An alternative to step 3 is to create a rolling median of the `N` most recent test reports so that we can safeguard against outlier test times muddying results.

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @ezyang @seemethere @malfet @walterddr @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: [JIT] Alias Annotations for Native Schema List Ops Is Subtly Wrong
Labels: high priority,oncall: jit,days,weeks

## 🐛 Bug

Pytorch List Ops are schematized as `func: chunk(Tensor(a) self, int chunks, int dim=0) -> Tensor(a)[]`. Because we set all containers to store the wildcard element, the `Tensor(a)[]` annotation effectively is read as `Tensor(*)[]`. As a result, the input self is not read to be contained by the output list.

The correct annotation is: `func: chunk(Tensor(a -> *) self, int chunks, int dim=0) -> Tensor[]`. I tried updating the schemas and ran into some errors with internal codegen. I can get it to it if no one else wants to do it....
```
@torch.jit.script
def foo():
    x = torch.tensor([4, 4, 4, 4])
    for elem in x.chunk(4, dim=0):
        elem.add_(10)
    return x + 1
```
print(foo())
> tensor([5, 5, 5, 5])

cc: @suo 


cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @gmagogsfm
Repository: TypeScript
Issue: A trivial generic interface extending a generic type handles assignability differently than the base type
Labels: Needs Investigation

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:** 4.0.5, 4.1.0-beta, 4.1.0-dev.20201102

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** generic interface assignability

**Code**

```ts
type Assert<T, U extends T> = U;

type A = { value: 5, a: true };
type B = { value: 5, b: true };

interface Box<T> {
    value: T;
}

type _Rebox<T extends Box<any>> = Box<T["value"]>;

namespace Test0 {
    type Rebox<T extends Box<any>> = _Rebox<T>;

    export type Assertions = [
        Assert<Box<5>, Rebox<A>>, // Correctly passes
        Assert<Rebox<A>, Box<5>>, // Correctly passes

        Assert<Box<5>, Rebox<B>>, // Correctly passes
        Assert<Rebox<B>, Box<5>>, // Correctly passes

        Assert<Rebox<A>, Rebox<B>>, // Correctly passes
    ];
}

namespace Test1 {
    interface Rebox<T extends Box<any>> extends _Rebox<T> {};

    export type Assertions = [
        Assert<Box<5>, Rebox<A>>, // Correctly passes
        Assert<Rebox<A>, Box<5>>, // Correctly passes

        Assert<Box<5>, Rebox<B>>, // Correctly passes
        Assert<Rebox<B>, Box<5>>, // Correctly passes

        Assert<Rebox<A>, Rebox<B>>, // Incorrectly fails
    ];
}
```

**Expected behavior:** `Test0.Assertions` and `Test1.Assertions` should both resolve with no errors.

**Actual behavior:** When `Rebox` is an interface (in `Test1`), `Rebox<B>` is not assignable to `Rebox<A>`.

**[Playground Link](https://www.typescriptlang.org/play?ts=next#code/FAFwngDgpgBAggZwVATiAPAFQDQwKoxQAeIUAdgCYIyYB8MAvPgNzCiSxyMwDeMAbgEMANgFcoALhgBWXIKkgU4mAF9W4aDABC3PkLGSZuAEYKlsNWwCWZUigBmggMawtAeyJZ6PYDD8CRcSlMVhU2DVgAfQAlKGMPLEISciptBMEyMFp6JndPTABtACJ9cSKAXVpWYDJBAFsoBAhnWExGkAAGXl9-CJhY+Pyk0kpqPPQMrJyYGLiEumr-JIg3NBg+xGQ0KzcyaiYCnqW-TdQMcelaXAGEuGzcAHoHmABhVZQoJxBhMBhmpEaR2OpzQ6BunjuuAu9xgT1e70+31+-2QCDYx38IPOCUu1zmni0MLhbxQHy+Pz+ggBaIxJwBoPB6EJUJxROeJLJSMp1PRtKxYPx6Eh-UFhKusPZCPJyKpqKB5VCbFqDSaLRo7QAjN0ljY7I4XCLBoliCNUuNJtlhilqLMjXReJYgcQVmsNvSQDs9txDrT4O6may8Ua7uLiVKuSjAb7+YzhdDQ5LSYiKZG0UClvzoUGEmLHonOSnZVG+f7Gcy0p5Lgn4Unpdy5enMaXBcKy2yYABJMhOcMUxxWYQ0-wK4BhIA)**

**Related Issues:** N/A