sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Proposal] Expose `padding` for multi-line `TextField`
Labels: a: text input,c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

## Use case

I have a Flutter desktop app with a full bleed `TextField` with infinite `maxLine` contraint. The text comes too close to the edges of the window, and I'd like to pad the content. 

I can pad the `TextField` on the left and right with a `Padding` widget, but I can't pad the top and bottom without creating an unsightly top and bottom gap during text scroll.

## Proposal

Please expose something akin to [`BoxScrollView`'s `padding`](https://api.flutter.dev/flutter/widgets/BoxScrollView/padding.html) property to multi-line `TextField`.
Repository: youtube-dl
Issue: Add TV Provider Cincinnati Bell Fioptics to adobepass.py 
Labels: clarification-needed

Can you add cincinnati bell fioptics to the adobepass.py please?

Thank you!
Repository: godot
Issue: Prevent infinite loop when a File can't be read
Labels: enhancement,topic:core

### Godot version

3.5 beta 3

### System information

Android Emulator, Android on OPPO CPH1941

### Issue description

Application works correctly on Mac OS when testing, but when Exporting to Android (either inside GODOT or via Android Studio) it doesn't get past the startup splash screen. 

Android Studio reports that the application is stuck inside some kind of infinite loop, but the error message does not display enough information to understand what might be the root cause of the problem or how to fix it. This error repeatedly appears in the logs until termination of the app.

058-4122/org.koineasy.test E/godot: ERROR: File must be opened before use.
2022-04-15 23:13:38.907 4058-4122/org.koineasy.test E/godot:    at: get_line (core/bind/core_bind.cpp:2104) - Condition "!f" is true. Returned: String()
2022-04-15 23:13:38.907 4058-4122/org.koineasy.test E/godot: ERROR: File must be opened before use.
2022-04-15 23:13:38.907 4058-4122/org.koineasy.test E/godot:    at: eof_reached (core/bind/core_bind.cpp:2017) - Condition "!f" is true. Returned: false
2022-04-15 23:13:38.907 4058-4122/org.koineasy.test E/godot: ERROR: File must be opened before use.
2022-04-15 23:13:38.909 4058-4122/org.koineasy.test E/godot:    at: get_line (core/bind/core_bind.cpp:2104) - Condition "!f" is true. Returned: String()
2022-04-15 23:13:38.909 4058-4122/org.koineasy.test E/godot: ERROR: File must be opened before use.
2022-04-15 23:13:38.909 4058-4122/org.koineasy.test E/godot:    at: eof_reached (core/bind/core_bind.cpp:2017) - Condition "!f" is true. Returned: false
2022-04-15 23:13:38.909 4058-4122/org.koineasy.test E/godot: ERROR: File must be opened before use.
2022-04-15 23:13:38.929 4058-4122/org.koineasy.test E/godot:    at: eof_reached (core/bind/core_bind.cpp:2017) - Condition "!f" is true. Returned: false
2022-04-15 23:13:38.929 4058-4122/org.koineasy.test E/godot: ERROR: File must be opened before use.
2022-04-15 23:13:38.929 40

### Steps to reproduce

If I create a blank project (Blank scene with a text label),  I am able to successfully export and run the blank project on android simulator and android devices. There is something specific to the project I have built that is preventing startup.

### Minimal reproduction project

The project is large and complicated, I don't have the skills to determine which small part of the project might be causing the startup freeze.

Perhaps if the error message can be improved I can understand what part of the project has a problem
Repository: TypeScript
Issue: Intersection causes incorrect type compatability
Labels: Needs Investigation,Has Repro

# Bug Report
### 🔎 Search Terms

intersection assignability omit compatability

### 🕗 Version & Regression Information

- This changed between versions 3.8.3 and 3.9.7

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/C4TwDgpgBAggCgSRmMAbAlgYwIbHQewDsBhfAWzO0IBMBlAVwCNNzKaBxAJ33rAHkweIlAC8UAN4AoKDKj5BBQgGcA-AC5YiZGiy5FpClTpMWhmgKGEA2gF0A3JIC+kyaEhQDbY81ZGuPfgVhMT4ydGAAHngkFAwcS08jBh8zan9eC0UAGigAcnlLJVyAPigAMgkoAHoqqAiAWnqoJXwodCUoYAALdrlCCGk5IOV1D18aZNMvTKJbJxc3aESJk3HqGcJRSvxuiE44bjAlDXpCAGtCfAB3Tcdyypq6xs6ejvRCYD2lCExLNo7sChsJwIB9UCAoJhOOFdKhBgVFKoTudLjc5s5JO9PpwAGbYTDQaLaOJ6IjLbxTIwbCSDGQIohIyo4-D4DRKYDQwgAcygjlsDlkcl2+0Oxygpwu10IDgxONOv0UnU4VCUzM4ZEma3SgUsAEYABT0wgacma1LajYASg0RNiugSazNXgtwxpMhBwHonE2Rrs1Vqlyge24nByjHowBee2gAH0lF0eKhqDGoIxoFQg5wQ-NJHLCArhByVWqNatzdwMsMAEyG4Ymx1l50VnWKa2aGI6eL6BspJsBalSd0QT3eyoAOgnRt5fsewfwnCcQA)




### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts repro
type APIApplicationCommandSubcommandGroupOption = {
    options?: APIApplicationCommandSubcommandOption[];
}

type CommandSubcommandGroupOption = Omit<APIApplicationCommandSubcommandGroupOption, 'options'> & { // <-- so is this one
  options?: CommandSubcommandOption[]
}

type CommandSubcommandOption = { otherProps: unknown } & { // <-- this intersection is apparently critical
  options?: unknown[]
}

interface APIApplicationCommandSubcommandOption {
    options?: { foo: string }[];
    otherProps: unknown;
}

function transformSubcommandGroupOption1(option: CommandSubcommandGroupOption): APIApplicationCommandSubcommandGroupOption {
  return option; // no error, but there _should_ be an error here.
}

function transformSubcommandGroupOption2(option: CommandSubcommandGroupOption): APIApplicationCommandSubcommandGroupOption {
  return { ...option }; // error in 3.9.7
}
```

### 🙁 Actual behavior

The `return option` does not produce an error and the `return { ...option }` does produce an error.

### 🙂 Expected behavior

Both `return`s should behave the same. Ideally, both should produce an error because `CommandSubcommandGroupOption` is incompatible with `APIApplicationCommandSubcommandGroupOption`.

From help thread on Discord: https://discord.com/channels/508357248330760243/964236133330460772
Repository: godot
Issue: (C#) [Export] Script Variables set in Inspector get reset when pulling from a Git repo
Labels: bug,topic:editor,confirmed,topic:dotnet

### Godot version

v3.4.4.stable.mono.official [419e713a2]

### System information

Windows 10 x64

### Issue description

**Because you need to build the project before the [Export] variables show up in the inspector, their values get reset when going in-between multiple computers.**

This is more noticeable if you save the node as a .tscn scene.  When you pull and build the project, the script variable will be set to null, but when you click the reset arrow, it sets it back to the correct value saved in the scene file.
![bit](https://user-images.githubusercontent.com/41555304/163597180-50cdf0a9-16a9-4372-9724-beabb9c0973b.PNG)



### Steps to reproduce

1. Open the reproduction project or create a C# script with a [Export] variable
2. Assign a value to the variable
3. Git push
4. Git pull (on another PC)
5. Build
6. Script variable is unassigned

### Minimal reproduction project

[ReproductionProject.zip](https://github.com/godotengine/godot/files/8497031/ReproductionProject.zip)
Repository: rust
Issue: rebinding values in an async function can double the memory usage
Labels: A-async-await,AsyncAwait-Polish,AsyncAwait-Triaged

Rebinding a value within an async function can cause the generated future to require twice the memory for the value. This seems to only happen if the value was borrowed earlier:

```rust
use std::mem;

async fn foo() {
    let x = [0u8; 100];
    async {}.await;
    println!("{}", x.len());
}

async fn a() {
    let fut = foo();
    let fut = fut;
    fut.await;
}

async fn b() {
    let fut = foo();
    println!("{}", mem::size_of_val(&fut));
    let fut = fut;
    fut.await;
}

fn main() {
    assert_eq!(mem::size_of_val(&foo()), 102);

    // 1 + sizeof(foo)
    assert_eq!(mem::size_of_val(&a()), 103);

    // 1 + (sizeof(foo) * 2)
    assert_eq!(mem::size_of_val(&b()), 205);
}
```

[Playground link](https://play.rust-lang.org/?version=stable&mode=release&edition=2021&gist=d4f0c621befd754b4a52fe3cf8e1ce13).

I don't know if this counts as a bug but the behavior is a bit surprising.

The effect is present in both debug and release modes with rustc 1.60.0.
Repository: pytorch
Issue: add -D_GLIBCXX_ASSERTIONS in debug mode
Labels: module: build,triaged

### 🚀 The feature, motivation and pitch

Internally, dev builds are built with -D_GLIBCXX_ASSERTIONS, which enables checks like index out-of-bounds in vectors.

See https://github.com/pytorch/pytorch/pull/75766 - which was built with _GLIBCXX_ASSERTIONS and found one error.

cc @malfet @seemethere @janeyx99 

### Alternatives

_No response_

### Additional context

_No response_
Repository: electron
Issue: [Bug]:`showItemInFolder` does not open correct item location when run as Electron snap
Labels: platform/linux,bug :beetle:,16-x-y,17-x-y,18-x-y,19-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 bug report that matches the one I want to file, without success.

### Electron Version

16.*

### What operating system are you using?

Ubuntu

### Operating System Version

Ubuntu 20.04

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

`showItemInFolder` should do as advertised and open the folder location of an item. For example:

```
shell.openItemInFolder("/home/username/Downloads/file.txt");
```

This should open the file browser to the user's Download folder and select "file.txt".

### Actual Behavior

When using Electron Fiddle or running from an uncompressed .tar.gz distribution, this works as expected.

However, when running from a standard (vs. classic) snap, the file browser opens to the user's home directory and no deeper. This happens even when the snap is connected to the `:home` slot, and should have permissions to open user directories.

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: pytorch
Issue: Move _SKIP_PYTHON_BINDINGS to native_functions.yaml
Labels: triaged,module: codegen

### 🐛 Describe the bug

@swolchok ran into a case where he named a function with `_forward` suffix and that caused it to magically not show up in Python bindings, in a way that was not debuggable until I remembered that there are name based matches. We should move this into a field on `native_functions.yaml` to make it more obvious when python bindings are being suppressed.

### Versions

master

cc @ezyang @bhosmer @bdhirsh
Repository: go
Issue: cmd/compile: optimize struct reset logic
Labels: Performance,NeedsInvestigation,compiler/runtime

Consider the following:
```go
type S struct {
	Large [8]int
	Small int
}

var s = new(S)

func BenchmarkResetA(b *testing.B) {
	for i := 0; i < b.N; i++ {
		*s = S{Large: s.Large}
	}
}

func BenchmarkResetB(b *testing.B) {
	for i := 0; i < b.N; i++ {
		s.Small = 0
	}
}
```
Performance:
```
BenchmarkResetA
BenchmarkResetA-24    	131323767	         9.117 ns/op
BenchmarkResetB
BenchmarkResetB-24    	1000000000	         0.2167 ns/op
```


Both snippets are semantically equivalent, but `ResetB` is much faster. 
However, `ResetA` is common in reset logic where the intention is to reset all fields except a few select fields. This pattern is more maintainable since it properly resets the struct even if new fields are added to it later on.

The compiler should recognize the pattern exhibited in `ResetA` and avoid the unnecessary copy of `s.Large = s.Large`.
Repository: pytorch
Issue: Add batching rules for `{view}_copy` operators
Labels: triaged,module: batching

The plan for the `functionalize()` transform is that it will soon have two modes:
- `functionalize(remove='mutations')` will remove all inplace and out= ops from the function
- `functionalize(remove='mutations_and_views')` will *additionally* convert view operators into their view_copy variants.

You can't use that second version of `functionalize()` together with `vmap` today though, because none of the `view_copy` operators have batching rules.

Most of them can use the fallback batching rule, but some aren't able to because of their schemas, like `at::split_copy`. So maybe we should just ensure that the "problematic" view copy ops have batching rules first.
Repository: pytorch
Issue: [FSDP] Verify buffer checkpointing
Labels: high priority,triage review,oncall: distributed,module: fsdp

### 🚀 The feature, motivation and pitch

`test_fsdp_state_dict` currently does not contain any logic to test that buffers are checkpointed appropriately. We should add these tests and also verify that it works for rank0 and offload_to_cpu checkpoint which is being added in https://github.com/pytorch/pytorch/pull/75908

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @gchanan @zou3519 @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: vscode
Issue: [folding] Increase number of foldable regions
Labels: feature-request,editor-folding

<!-- ⚠️⚠️ 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. -->
Please increase the maximum number of foldable regions.

Pull request #140480 implements a configurable number of foldable regions which is great, but it's limited to 65000 which is too small - I regularly open large lua table dumps and huge log files and get the "_The number of foldable regions is limited to a maximum of 65000_" message several times a day.

I appreciate performance may be affected, but I want to turn the knob until it hurts... I am not noticing any issues at 65000 on even modestly specced PCs.
Repository: pytorch
Issue: 'python setup.py build' failed but succeed using  'pip install -v .' which calls 'python setup.py build'.
Labels: module: build,triaged

## Issue description

'python setup.py build' failed but succeed using  'pip install -v .' which calls 'python setup.py build'.

Error message:
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'install', '--config', 'Release', '--', '-j', '6']' returned non-zero exit status 2.


## Log
# TORCH_CUDA_ARCH_LIST="3.5 5.2 6.0 6.1 7.0+PTX 8.0" TORCH_NVCC_FLAGS="-Xfatbin -compress-all"     CMAKE_PREFIX_PATH="$(dirname $(which conda))/../"     python setup.py build
Building wheel torch-1.7.0a0
-- Building version 1.7.0a0
cmake --build . --target install --config Release -- -j 6
make: *** No rule to make target 'install'.  Stop.
Traceback (most recent call last):
  File "setup.py", line 717, in <module>
    build_deps()
  File "setup.py", line 308, in build_deps
    build_caffe2(version=version,
  File "/pytorch-builder/src/pytorch/tools/build_pytorch_libs.py", line 62, in build_caffe2
    cmake.build(my_env)
  File "/pytorch-builder/src/pytorch/tools/setup_helpers/cmake.py", line 345, in build
    self.run(build_args, my_env)
  File "/pytorch-builder/src/pytorch/tools/setup_helpers/cmake.py", line 141, in run
    check_call(command, cwd=self.build_dir, env=env)
  File "/opt/conda/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'install', '--config', 'Release', '--', '-j', '6']' returned non-zero exit status 2.


## System Info
# python ./torch/utils/collect_env.py 
Collecting environment information...
PyTorch version: 1.7.0a0+bd37e59
Is debug build: True
CUDA used to build PyTorch: Could not collect
ROCM used to build PyTorch: N/A

OS: Ubuntu 18.04.6 LTS (x86_64)
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Clang version: Could not collect
CMake version: version 3.10.2

Python version: 3.8 (64-bit runtime)
Is CUDA available: False
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 2070 SUPER
Nvidia driver version: 470.86
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.21.5
[pip3] torch==1.7.0a0
[conda] blas                      1.0                         mkl  
[conda] mkl                       2021.4.0           h06a4308_640  
[conda] mkl-service               2.4.0            py38h7f8727e_0  
[conda] mkl_fft                   1.3.1            py38hd3c417c_0  
[conda] mkl_random                1.2.2            py38h51133e4_0  
[conda] numpy                     1.21.5           py38he7a7128_1  
[conda] numpy-base                1.21.5           py38hf524024_1  
[conda] torch                     1.7.0a0                  pypi_0    pypi


cc @malfet @seemethere
Repository: flutter
Issue: Rewrite the NestedScrollView
Labels: c: new feature,framework,f: scrolling,a: quality,c: proposal,P3,team-framework,triaged-framework

I have a few ideas for this, although I will not be able to pursue them now.

Ideally, a re-vamped NestedScrollView would solve these issues (among others, theses are just a few of several that stand out):
- https://github.com/flutter/flutter/issues/102001
  - the new structure would not rely on the PrimaryScrollController, and perhaps introduce a public NestedScrollController that inherits the current existing concept of a NestedScrollCoodinator. This would be similar to widget specific controllers like TabController and PageController, and could grant long requested access to the inner workings.
- https://github.com/flutter/flutter/issues/62363
  - mentioned above, accessing the inner working of the NestedScrollView, or even just accurate metrics can be difficult for users. Any metrics or scroll notifications should be a composite of both scroll views
- https://github.com/flutter/flutter/issues/59189
  - similar: https://github.com/flutter/flutter/issues/54059
  - NestedScrollView should support all sliver features and functionality
- https://github.com/flutter/flutter/issues/45619
  - how it is configured should be clearer. right now it can be a mixed bag of configs, creating a host of issues.
- https://github.com/flutter/flutter/issues/40740
  - The PrimaryScrollController in the NestedScrollView here is applying the same scroll offset to every attached position, since the NestedScrollView applies scroll deltas to every attached position.


Lastly, it would be awesome if we could do this without breaking anyone. :)
Repository: flutter
Issue: disable notification center on mac due to high cpu usage
Labels: team-infra,P2,triaged-infra

 There are instances were it seems notification center widgets are taking a lot of CPU, see #95582 . Look at disabling notification center to reduce errant cpu use.

Note: 
`launchctl unload -w /System/Library/LaunchAgents/com.apple.notificationcenterui.plist`
 
seems to disable notification center, even across reboots.
Repository: create-react-app
Issue: React: 'create-react-app' is not recognized as an internal or external command
Labels: needs triage,issue: bug report

I am trying to set up react app using create-react-app command on windows pc. But I encounter error 'create-react-app' is not recognized as an internal or external command.

with the same command, it works for me on my MacOs. Below is the error detail:

 
C:\Users\ugur\Desktop\deneme>npm install -g create-react-app
C:\Users\ugur\AppData\Roaming\npm\create-react-app -> C:\Users\ugur\
AppData\Roaming\npm\node_modules\create-react-app\index.js
C:\Users\ugur\AppData\Roaming\npm
`-- create-react-app@0.2.0
  +-- chalk@1.1.3
  | +-- ansi-styles@2.2.1
  | +-- escape-string-regexp@1.0.5
  | +-- has-ansi@2.0.0
  | | `-- ansi-regex@2.0.0
  | +-- strip-ansi@3.0.1
  | `-- supports-color@2.0.0
  +-- cross-spawn@4.0.0
  | +-- lru-cache@4.0.1
  | | +-- pseudomap@1.0.2
  | | `-- yallist@2.0.0
  | `-- which@1.2.10
  |   `-- isexe@1.1.2
  +-- minimist@1.2.0
  `-- semver@5.3.0

C:\Users\ugur\Desktop\deneme>create-react-app new_app


How can I resolve this issue?


You need to re-install the latest version of node and try the latest version of React.

And then

npm install -g create-react-app
create-react-app my-app

I hope it useful for you!
Repository: create-react-app
Issue: 'create-react-app' is not recognized as an internal or external command
Labels: needs triage,issue: bug report

C:\Windows\system32>cd C:\Users\ugur\Desktop\deneme

C:\Users\ugur\Desktop\deneme>npm init


This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sensible defaults.

See 'npm help json' for definitive documentation on these fields
and exactly what they do.

Use 'npm install <pkg> --save' afterwards to install a package and
save it as a dependency in the package.json file.

Press ^C at any time to quit.
name: (deneme)
version: (1.0.0)
description:
entry point: (index.js)
test command:
git repository:
keywords:
license: (ISC)
About to write to C:\Users\ugur\Desktop\deneme\package.json:

{
   "name": "deneme",
   "version": "1.0.0",
   "description": "",
   "main": "index.js",
   "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
   },
   "author": "Ugur <ugur@abc.com.tr> (http://www.abc.com.tr)",
   "license": "ISC"
}


Is this ok? (yes)

C:\Users\ugur\Desktop\deneme>npm install -g create-react-app
C:\Users\ugur\AppData\Roaming\npm\create-react-app -> C:\Users\ugur\
AppData\Roaming\npm\node_modules\create-react-app\index.js
C:\Users\ugur\AppData\Roaming\npm
`-- create-react-app@0.2.0
  +-- chalk@1.1.3
  | +-- ansi-styles@2.2.1
  | +-- escape-string-regexp@1.0.5
  | +-- has-ansi@2.0.0
  | | `-- ansi-regex@2.0.0
  | +-- strip-ansi@3.0.1
  | `-- supports-color@2.0.0
  +-- cross-spawn@4.0.0
  | +-- lru-cache@4.0.1
  | | +-- pseudomap@1.0.2
  | | `-- yallist@2.0.0
  | `-- which@1.2.10
  |   `-- isexe@1.1.2
  +-- minimist@1.2.0
  `-- semver@5.3.0


C:\Users\ugur\Desktop\deneme>create-react-app new_app

'create-react-app' is not recognized as an internal or external command, operable program or batch file.

Also npm configuration path is like

C:\Users\ugur\AppData\Roaming\npm\node_modules\create-react-app\

Try with this

 npx create-react-app my-app
Repository: angular
Issue: Compiler incorrectly allows newlines in i18n placeholder names
Labels: state: has PR,area: compiler,P3

### Which @angular/* package(s) are the source of the bug?

compiler-cli, compiler

### Is this a regression?

No

### Description

The following is valid Angular code:

```html
<div i18n>
  Hello, {{ user // i18n(ph = "user
  name") }}
</div>
```

The newline in `user\n  name` should not be allowed. Newlines aren't allowed like that in real JS strings and it doesn't make sense to allow them here.

See http://cl/442095274 for one example of a developer doing this, which caused problems for https://github.com/angular/angular/pull/45606.

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
No exception, that's the exception.
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
Appeared in google3, which runs roughly at the repository HEAD.
```


### Anything else?

_No response_