sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: release react-dev-utils 11.0.5
Labels: stale,needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

There was a security bug in immer 8.0.1 and react-dev-utils is now using [9.0.6](https://github.com/facebook/create-react-app/commit/960b21e89d368acc0cbbb672d6755269b65b57f8#diff-5fa747ee59928aa870b421193b0ad74be1701fe65cfddd1691284dbeac6caa8b) but react-dev-utils' version hasn't been bumped ever since, so consumers are still getting the impacted version of immer. 

Can we please publish a new version?
Repository: flutter
Issue: Newline in Textformfield does not work on desktop
Labels: a: text input,framework,f: material design,platform-mac,platform-linux,a: desktop,has reproducible steps,P2,found in release: 2.5,found in release: 2.6,fyi-text-input,team-macos,triaged-macos

## Steps to Reproduce

1. Have a Textformfield
2. Build web app
3. Attempt to insert a newline in any web browser

**Expected results:** 

A new line

**Actual results:**

Not a new line

```dart
TextFormField(
    maxLines: 4,
    minLines: 3,
    controller: editingControllers['addr'],
    onChanged: (String val) => _changed(),
    textInputAction: TextInputAction.newline,
    keyboardType: TextInputType.streetAddress,
    decoration: InputDecoration(
        alignLabelWithHint: true,
        labelText: 'Address',
        hintMaxLines: 3,
        hintText:
            '124. Conch street\n00802 Bikini Bottom\nU.S. Virgin Islands'),
),
```
I have found similar issues on github, all of which were left unanswered and automatically closed by bots.
Repository: pytorch
Issue: zeta(1/2) returns nan
Labels: triaged,module: special

## Bug

The [Riemann zeta function](https://pytorch.org/docs/stable/special.html?highlight=zeta#torch.special.zeta) at 1/2 should be `zeta(1/2) = -1.46...` (See [WolframAlpha](https://www.wolframalpha.com/input/?i=zeta%281%2F2%29)) but [`torch.special.zeta`](https://pytorch.org/docs/stable/special.html?highlight=zeta#torch.special.zeta) returns `nan`.

This may be expected behavior but if so it would be nice to have documentation for this behavior.

## To Reproduce

```py
import torch

output = torch.special.zeta(torch.tensor(1 / 2), 1.0)

print(output)
```

```txt
tensor(nan)
```

## Expected behavior

```txt
tensor(-1.46...)
```

## Environment

```txt
Collecting environment information...
PyTorch version: 1.10.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 11.6 (x86_64)
GCC version: Could not collect
Clang version: 12.0.5 (clang-1205.0.22.11)
CMake version: Could not collect
Libc version: N/A

Python version: 3.9.7 (default, Oct 13 2021, 06:45:31)  [Clang 13.0.0 (clang-1300.0.29.3)] (64-bit runtime)
Python platform: macOS-11.6-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] mypy==0.910
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.21.2
[pip3] torch==1.10.0
[conda] Could not collect
```

## Additional context

The scipy 1.7.1 counterpart, [scipy.special.zeta](https://docs.scipy.org/doc/scipy/reference/generated/scipy.special.zeta.html), returns the correct value.

```py
from scipy.special import zeta

output = zeta(1 / 2)

print(output)
```

```txt
-1.4603545088095866
```

update: Additional context

cc @mruberry
Repository: ant-design
Issue: [Bug] Steps progressDot 无法放置在小容器中
Labels: Inactive,improvement

### 重现链接

https://codesandbox.io/s/antd-reproduction-template-forked-clfri?file=/index.js:533-544

### antd 版本

4.16.3

### 重现步骤

```
<div style={{ width: 200, border: "1px solid blue", margin: 20 }}>
      <Steps progressDot size="small">
        <Steps.Step>1</Steps.Step>
        <Steps.Step>2</Steps.Step>
        <Steps.Step>3</Steps.Step>
        <Steps.Step>4</Steps.Step>
      </Steps>
    </div>
```


### 期望的结果是什么？

能正确容纳在小容器中

### 实际的结果是什么？

![image](https://user-images.githubusercontent.com/566097/141069285-5dc934b0-1f88-4e88-8e86-69cb82e4ff6a.png)


### 浏览器

_No response_

### 浏览器版本

_No response_

### 操作系统

_No response_

### 其他

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: electron
Issue: [Bug]: In will-navigate e.preventDefault() does not prevent navigation to about: urls
Labels: bug :beetle:,13-x-y,15-x-y,16-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Electron Version

13.6.1, 15.3.1, 16.0.0.b8

### What operating system are you using?

Other Linux

### Operating System Version

5.14.12

### What arch are you using?

x64

### Last Known Working Electron version

unknown

### Expected Behavior

Calling `e.preventDefault` in `will-navigate` event handler should prevent any navigation within webContents frame.

### Actual Behavior

This does not work if the url being navigated to is an about: url, such as `about:blank`, `about:` Even random about urls like `about:vh99fh2` will cause navigating away.

### Testcase Gist URL

https://gist.github.com/mckravchyk/5673785c24dfcda54b648aa418b4cc40

### Additional Information

_No response_
Repository: svelte
Issue: Cursor jumps to end in search box in Safari
Labels: bug,compiler

### Describe the bug

The cursor in a search box (`input[type="search"]`) with a two-way value binding jumps to the end when typing in Safari.  I don't know my way around the Svelte code base, but looking at previous cursor issues, I think `'search`' would have to be added to the `if` condition [here](https://github.com/sveltejs/svelte/blob/fc4797c6f84cf299117243e7193bf77d96914e85/src/compiler/compile/render_dom/wrappers/Element/Attribute.ts#L207).

### Reproduction

```svelte
<script>
  let foo: string = '';
</script>

<input type="search" bind:value={foo}>
```

https://svelte.dev/repl/ede78dee46f74e088fcc07241a389363?version=3.44.1

### Logs

_No response_

### System Info

```shell
n/a
```


### Severity

annoyance
Repository: flutter
Issue: [cross_file] Document that `mimeType` is not expected to be set for io implementation
Labels: platform-android,package,good first issue,has reproducible steps,P3,found in release: 2.5,found in release: 2.6,team-android,triaged-android

<!-- 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
-->

## Steps to Reproduce

1. Run the image picker example on a physical android device
2. Add a line in `_onImageButtonPressed` to `print(pickedFile?.mimeType)`
3. Pick an image

**Expected results:**
'image/jpeg' or something like that

**Actual results:**
null :'(

<details>
<summary>Code sample</summary>
Reproducible with the official example, testing on a Poco X3.

</details>

<details>
  <summary>Logs</summary>

```
alex@Alexs-MacBook-Air ~ % flutter doctor -v
[✓] Flutter (Channel stable, 2.5.3, on macOS 12.0.1 21A559 darwin-arm, locale en-GB)
    • Flutter version 2.5.3 at /Users/alex/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (4 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/alex/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 13.1, Build version 13A1030d
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2020.3)
    • 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.10+0-b96-7281165)

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (2 available)
    • M2007J20CG (mobile) • d35bf0f1 • android-arm64  • Android 11 (API 30)
    • Chrome (web)        • chrome   • web-javascript • Google Chrome 95.0.4638.69
```

</details>
Repository: flutter
Issue: [WebView] App Crashes after adopting Hybrid Composition on Android SDK 19 
Labels: c: crash,platform-android,a: platform-views,p: webview,package,e: OS-version specific,has reproducible steps,P2,found in release: 2.5,found in release: 2.6,team-android,triaged-android

Refer to this issue https://github.com/flutter/flutter/issues/63897, it still happened on Android version 4.4.
Repository: node
Issue: Environment with NODE_OPTIONS=--max-old-space-size=x installation breaks with illegal value for flag
Labels: cli

### Version

v12.22.7

### Platform

Linux 0031d2238124 4.14.248-189.473.amzn2.x86_64 #1 SMP Mon Sep 27 05:52:26 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

### Subsystem

_No response_

### What steps will reproduce the bug?

```bash
export NODE_OPTIONS=--max-old-space-size=8192
nvm install v12
```

provided latest v12 release is v12.22.7, otherwise do

```bash
export NODE_OPTIONS=--max-old-space-size=8192
nvm install v12.22.7
```

### How often does it reproduce? Is there a required condition?

Not specific. Consistent with this release version. Other version works fine.
Following passes without any failures
```bash
export NODE_OPTIONS=--max-old-space-size=8192
nvm install v12.22.6
```


### What is the expected behavior?

Expect installation to pass

### What do you see instead?

```
Error: illegal value for flag --max-old-space-size=8192	 of type size_t
Try --help for options
node: bad option: --max-old-space-size=8192
```

### Additional information

Little unclear if node or nvm specific, but broken with release of v12.22.7
Repository: flutter
Issue: feat(android): support am instrument arguments
Labels: a: tests,c: new feature,platform-android,tool,c: proposal,P3,team-android,triaged-android

Hi!

I'm a developer of a custom test runner and I have a pre-execution phase where I need to collect a list of tests expected to execute. On Android I use the `am instrument -e log true` [flag](https://developer.android.com/studio/test/command-line) [supported natively](https://cs.android.com/androidx/android-test/+/master:runner/android_junit_runner/java/androidx/test/internal/runner/RunnerArgs.java;l=58?q=RunnerArgs) by any implementation of Junit4 Runner that extends [AndroidJunitRunner](https://developer.android.com/reference/androidx/test/runner/AndroidJUnitRunner).

Unfortunately, current implementation used by [flutter extends ](https://github.com/flutter/flutter/blob/e7b7ebc066c1b2a5aa5c19f8961307427e0142a6/packages/integration_test/android/src/main/java/dev/flutter/plugins/integration_test/FlutterTestRunner.java#L19) `org.junit.runner.Runner`. This makes it impossible to utilize flags that are expected to works out-of-the-box.

There are two ways to fix this as far as I can see:
1. Continue to extend `org.junit.runner.Runner` and properly return descriptions for tests in `getDescription()` [here](https://github.com/flutter/flutter/blob/e7b7ebc066c1b2a5aa5c19f8961307427e0142a6/packages/integration_test/android/src/main/java/dev/flutter/plugins/integration_test/FlutterTestRunner.java#L51)
2. Rework the runner to extend `androidx.test.runner.AndroidJUnitRunner`. This is the case for example in [cucumber-android](https://github.com/cucumber/cucumber-android/blob/main/cucumber-android/src/main/java/io/cucumber/android/runner/CucumberAndroidJUnitRunner.java#L14) where tests are also generated at runtime

Currently if I execute the tests with `-e log true` I receive the following:
```
generic_x86:/ $ am instrument -w -r --no-window-animation -e log true -e class com.example.integration_test_example.MainActivityTest#Flutter\ Tests com.example.integration_test_example.test/androidx.test.runner.AndroidJUnitRunner      
INSTRUMENTATION_STATUS: class=com.example.integration_test_example.MainActivityTest
INSTRUMENTATION_STATUS: current=1
INSTRUMENTATION_STATUS: id=AndroidJUnitRunner
INSTRUMENTATION_STATUS: numtests=1
INSTRUMENTATION_STATUS: stream=
com.example.integration_test_example.MainActivityTest:
INSTRUMENTATION_STATUS: test=Flutter Tests
INSTRUMENTATION_STATUS_CODE: 1
INSTRUMENTATION_STATUS: class=com.example.integration_test_example.MainActivityTest
INSTRUMENTATION_STATUS: current=1
INSTRUMENTATION_STATUS: id=AndroidJUnitRunner
INSTRUMENTATION_STATUS: numtests=1
INSTRUMENTATION_STATUS: stream=.
INSTRUMENTATION_STATUS: test=Flutter Tests
INSTRUMENTATION_STATUS_CODE: 0
INSTRUMENTATION_RESULT: stream=

Time: 0.002

OK (1 test)


INSTRUMENTATION_CODE: -1
```

The test will always be `Flutter Tests` because it's hardcoded in the runner and I want to receive a list of tests expected to run without actually running them.

Please let me know if I can provide more information.
Repository: material-ui
Issue: [core] API docs generator including props of unstyled components
Labels: core

I've encountered an issue while working on the Popper component (https://github.com/mui-org/material-ui/pull/29488#discussion_r743640362).

Popper uses PopperUnstyled internally but has a different set of props. Specifically, `type PopperProps = Omit<PopperUnstyledProps, 'direction'>`.
However, when building API documentation for Popper, the `direction` prop appears on the generated page. The docs generator should take into consideration the real shape of PopperProps.
Repository: pytorch
Issue: CPU Memory Deallocation 
Labels: module: memory usage,triaged

Hello! :D First of all, thank you all for this wonderful project!

Well, I'm using a package that uses pytorch models to do their job (easyocr/JaiddedAI). The problem is that, when a new model is loaded, its resources are kept in my memory even though I deallocated manually (del model) not sure why that is a thing since I'm currently using a CPU, and the cache tensor way is a GPU thing. Anyone know why that is happening and what I can do to prevent this to happen?

I'm working in a API Project, so shut down the process is not allowed. Even though works on scripts!
Repository: vscode
Issue: ICodeEditor.setHiddenAreas optimizes away valid update
Labels: bug,editor-folding,editor-core

From #132784

- create a python file
```
a
  b
c
```
- fold the first range. -> `ICodeEditor.setHiddenAreas` called with (line 2)
- set the cursor on line 3 (c) and invoke `Insert line above`
- the editor internally expands the hidden range at line 2: line 2 and the new line 3 are now hidden
- the folding provider recompute the hidden lines and because it is Python (offside mode) the new line is not part of the folded range.
- the folding provider calls `ICodeEditor.setHiddenAreas` with [line 2] as hidden. 

Nothing happens. The empty line is still hidden :bug: 

https://github.com/microsoft/vscode/blob/main/src/vs/editor/common/viewModel/viewModelLines.ts#L175
assumes that only line 2 is folded and skips the update.
Repository: godot
Issue: Extended C# custom types aren't detected by the editor
Labels: bug,topic:dotnet

### Godot version

3.3.3

### System information

Ubuntu 20.04

### Issue description

I added a custom type with a plugin using [AddCustomType](https://docs.godotengine.org/en/stable/tutorials/plugins/editor/making_plugins.html#a-custom-node). The custom type appears in the node selector as expected and shows the icon.

However when I extend the node with a new script, the editor looses the type/icon information in the extended node. `BT_Task` is the custom type added by the plugin, and `BT_Task2` is using a script that extends the type. It looses the icon, and when i hover it it says its of type `Node` instead of `BT_Task`.

![Screenshot_20211110_094520](https://user-images.githubusercontent.com/3958783/141134604-7f1d0328-aece-4d42-982e-9ba4eaa4687b.png)

I'm not sure if this is actually a bug or not but I can't find anything in the docs about it. I expected that I could just extend custom types the same way that i can base types. Also I'm not sure why the custom type still shows a script icon beside it.


### Steps to reproduce

[Create a C# custom type via plugin](https://docs.godotengine.org/en/stable/tutorials/plugins/editor/making_plugins.html) and then try to extend a node of that type.

### Minimal reproduction project

_No response_
Repository: react
Issue: Consolidate component stack and (DEV only) element __source
Labels: Type: Discussion,Component: Developer Tools

There are currently two types of component "location" displayed and used in DevTools:
* "Native" component stacks: These are detected by intentionally causing the component to throw an error (e.g. `null` props object, a hooks dispatcher that throws) so DevTools can figure out **where the function is defined**.
* DEV source metadata that comes from plugins like [@babel/plugin-transform-react-jsx-source](https://github.com/babel/babel/blob/main/packages/babel-plugin-transform-react-jsx-source/src/index.js) and describes **where the JSX element is defined** (e.g. where its props are passed).

In other words, for the `Greeting` component:
```jsx
function Example() {
  return <Greeting name="brian" />; // <- DEV source metadata
}

function Greeting({name}) { // <- component stack
  return <div>Hi, {name}</div>;
}
```
The two locations have different use cases. Which one do you want when you click the "open in editor" button?

I'm not sure. I can imagine cases for both of these. My gut is that the component stack location is actually slightly better for "open in editor" _but_ it would be a change in behavior.

That being said, it would be nice to pick one and stick with it, and the component stack location has the added benefit of working in production.
Repository: opencv
Issue: cv::rectangle with very large cv::Rect triggers undefined behavior sanitizer
Labels: RFC

##### System information (version)
- OpenCV => 4.5.4
- Operating System / Platform => Linux
- Compiler => clang 12

##### Detailed description

cv::rectangle with a cv::Rect where x and width are std::numeric_limits<int>::max() creates a problem because it calls Rect::br() which overflows (x+width does not fit in an int and overflows).
The external call to cv::rectangle is still valid, the internal call to cv::Rect::br() not. What should be the proper solution ?

- not allow the creation of a cv::Rect with such big values because br() (and area() ) will overflow ?
- only warn of overflows when calling br() ?
- have br() return std::numeric_limits<int>::max() ? (probably not desirable because inaccurate, then again what is returned now is wrong)
- create a safe_br() function that caps and not overflows ?
- only fix cv::rectangle for now. Then again, other functions will probably fail.

##### Issue submission checklist

 - [x] I report the issue, it's not a question
 - [x] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found solution
 - [x] I updated to latest OpenCV version and the issue is still there
Repository: flutter
Issue: Consider adding a build-file-generating command to `flutter`
Labels: tool,c: proposal,P3,team-tool,triaged-tool

Currently on many platforms there are critical files for the native build system that are generated by building, such that you must `flutter build` or `flutter run` before using those systems directly. Some cases that I've run into:
- Android: `gradlew` isn't generated until building.
- Linux: `ninja` files for each configuration (debug, release) aren't created until building for that configuration.
- Windows: the generated Visual Studio solution isn't created until building.
- [ETA:] iOS/macOS: the Podfile isn't created until building.

As an example of things this affects, the flutter/plugin repository tooling must build examples before being able to run unit tests on most platforms, which is not ideal (especially on Linux, where since we're only building release mode, we can only run unit tests in release mode unless we make CI much slower).

In at least the Linux and Windows case, the step for generating the native build files is easily separable from the actual build, so with minor refactoring we could have a new command that would run just that (fast) step, without the expensive build.
Repository: rust
Issue: Tracking Issue for `proc_macro_expand`
Labels: T-libs-api,C-tracking-issue,A-proc-macros,WG-macros

Feature gate: `#![feature(proc_macro_expand)]`

This is a tracking issue for the `TokenStream::expand_expr` function for use in proc-macros. This function allows eagerly expanding TokenStreams containing expressions from within a proc-macro, such that they can be modified, giving proc-macros similar functionality to built-in macros like `format_args!`, `concat!` and `include!`.

### Public API

```rust
impl TokenStream {
    pub fn expand_expr(&self) -> Result<TokenStream, ExpandError>;
}

#[non_exhaustive]
pub struct ExpandError;

impl Debug for ExpandError { ... }
impl Display for ExpandError { ... }
impl Error for ExpandError {}
impl !Send for ExpandError {}
impl !Sync for ExpandError {}
```

### Steps / History

- [x] Implementation for literal expressions: #87264
- [ ] Generalization for other expression types: TODO
- [ ] (optional) Generalization to other AST types: TODO
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

- What types of expressions beyond literals should be supported?
- Should expanding non-expression macros (e.g. types, items, etc.) be supported?
- Should certain macros (e.g. those with `#[allow_internal_unstable]`) be expandable or left unexpanded?
- How can we evolve which macros are expanded or not within the rustc stability model? Can downstream crates opt-in to additional macro expansion on nightly channels? Should an additional argument be provided to customize what should be expanded?
- Should compilation be allowed to proceed after an expand method errors?
- Are there concerns about stabilizing the span information generated by internal macros like `include!`?
- How can we properly preserve span information when expanding expression macros?