sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/tools/gopls: option to autocomplete function call without parentheses
Labels: NeedsDecision,FeatureRequest,gopls,Tools

(This is more of a question before it becomes a feature request. However, the original Slack invite link is no longer active.)

**Is your feature request related to a problem? Please describe.**
Is it possible to leave out the parentheses of a method when doing autocompletion? For example, when typing `time.No` and hit tab, instead of autocompleting with `time.Now()` is it possible to complete it as `time.Now`?

**Describe the solution you'd like**
Have an option for this, something like `gopls.includeParenthesesWhenAutocomplete` that can be set to `false`.

**Describe alternatives you've considered**
N/A

**Additional context**
I have been writing a mix of C++, Python, and JS/TS, and all these languages' autocompletion on VS Code are without the parentheses. It's muscle memory for me now to reach for `(` after completing the method and it's really counter-productive especially when I need to switch between languages.
Repository: pytorch
Issue: Add support for reading the whole file in from_file
Labels: module: serialization,triaged,enhancement,module: numpy

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Following [numpy implementation of fromfile](https://numpy.org/doc/stable/reference/generated/numpy.fromfile.html), I propose we add support for reading through the whole file via a `size=-1` argument.

## Motivation

`torch.from_file` almost provides a full-fleshed implementation allowing to read binary files into a tensor in a torchscript-compatible way. But it requires specifying the precise number of bytes that we need to read, making it hard to use it in a torchscript-compatible way.

Having support for such functionality means that we can implement many basic `io` functions natively in PyTorch with torchscript support.


## Pitch

Basic IO in PyTorch with torchscript support made easy!

## Additional context

In torchvision, in order to circumvent this limitation we had to wrap `from_file` in a C++ function just to query the file size, see https://github.com/pytorch/vision/pull/2728 , but it would have been preferable if this could be done with stock PyTorch


cc @mruberry @rgommers
Repository: PowerToys
Issue: FancyZones: maximize window when the zone matches the whole screen
Labels: Idea-Enhancement,Product-FancyZones

I have 3 monitors, and I like to keep one window in each for productivity. FancyZones help a lot in doing that, but it lacks an important feature:

When the zone matches the whole screen, the application should be maximized instead of windowed. Look this example:

Windowed by PowerToys:
![image](https://user-images.githubusercontent.com/29582865/95228121-cc1e2480-07b3-11eb-9a23-837fb5b5f25f.png)

Maximized:
![image](https://user-images.githubusercontent.com/29582865/95228201-e35d1200-07b3-11eb-9a92-c2849c17fb03.png)

Note that in the first example, the title bar of the application is not correctly dimensioned. Also, there is a blue border in the edges of the application.

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: godot
Issue: Pre-processing scripts with EditorExportPlugin
Labels: bug,topic:editor,topic:plugin

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
- 3.x
- master (ed333248f59da26fc0a3a1b30baf461ed332f0d9)

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Manjaro 20.1.1

**Issue description:**
<!-- What happened, and what was expected. -->
I was trying to do an experiment to learn more about the `EditorExportPlugin` but I had some issues with the API behaviours and/or documentation.
My experiment is quite simple, it's just a base to pre-process scripts on exports (to optimise, remove useless code etc).

*Godot 3.x behaviour:* If the script export mode is set to compiled or encrypted, the `_export_file()` function never receives a `GDScript` type. It only works in text mode.
Is this by design (documentation issue) or has it never been implemented?

*Godot master behaviour:* It looks like compiled mode is a no-op now (probably because of recent updates to the GDScript syntax), and encrypted mode is no longer applicable because of the encrypted pck. So, scripts are always being treated as text mode.

**Steps to reproduce:**
Try to detect a `GDScript` type in the `EditorExportPlugin:_export_file()` using compiled/encrypted export mode.
Export using <kbd>Export PCK/ZIP</kbd> button to facilitate testing.

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[ScriptExportPlugin.zip](https://github.com/godotengine/godot/files/5335298/ScriptExportPlugin.zip)
Repository: flutter
Issue: Make RouterInformationParser parameter in MaterialApp.router optional
Labels: framework,f: material design,f: routes,c: proposal,P3,team-design,triaged-design

Currently the MaterialApp.router has two required parameters RouterInfromationParser and RouterDelegate. For Application that does not care about route parsing but still want to leverage the router (for android back button), they do not care about RouterInfromationParser. We can make it optional so that user only need to provide the RouterDelegate in such case.
Repository: flutter
Issue: iOS 14 crash (Simulator) -- Fatal Exception: NSInternalInconsistencyException Modifications to the layout engine must not be performed from a background thread after it has been accessed from the main thread.
Labels: c: crash,e: device-specific,platform-ios,engine,a: existing-apps,p: image_picker,package,P3,c: fatal crash,team-ios,triaged-ios

The original issue was https://github.com/flutter/flutter/issues/66647. The crash was fixed on devices but not simulator. This issue is created to track the work on fixing it on the simulators.

Steps to reproduce: (Using image picker as an example, but this is more likely an engine issue, someone mentioned in https://github.com/flutter/flutter/issues/66647 that this happens to other plugins too, and it might happen in add to app as well)

1. Download the image picker plugin https://github.com/flutter/plugins/tree/master/packages/image_picker/image_picker

1.5 Make sure the image picker uses a full screen presentation style:

- Around https://github.com/flutter/plugins/blob/master/packages/image_picker/image_picker/ios/Classes/FLTImagePickerPlugin.m#L70
Set the presentationStyle of the `_imagePickerController` to `UIModalPresentationCurrentContext`: `_imagePickerController.modalPresentationStyle = UIModalPresentationCurrentContext;`

2. Launch the example app on iPhone SE (new) simulator with iOS 14

3. Click on the button to pick image from gallery.

4. When the image picker controller shows, tap on cancel. 

5. After image picker controller disappears, repeat step 3.

6. See crash.

After some debugging, we know the layout engine was somehow modified by setting the contents of a CALayer here: 
https://github.com/flutter/engine/blob/master/shell/platform/darwin/ios/ios_surface_software.mm#L120
Repository: pytorch
Issue: with torch.cuda.amp.autocast() get out of memory error when using with torch.no_grad() during validation
Labels: module: docs,module: autograd,triaged,module: amp (automated mixed precision)

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->

## To Reproduce

Steps to reproduce the behavior:

1.  using with torch.no_grad() and  autocast() at the same time
2. then get cuda out of memory error

## Environment

Google Colab


## code that work well
```python
with torch.nograd():
    for i,batch in enumerate(tqdm_dataloader):
        txt_ids, attention_mask, token_type_ids, context_mask, turn_mask,tags=batch['txt_ids'],batch['attention_mask'],batch['token_type_ids'],\
                                                                        batch['context_mask'],batch['turn_mask'],batch['tags']
        tag_idxs = model(txt_ids.to(device), attention_mask.to(device), token_type_ids.to(device))
        predict_spans = tag_decode(tag_idxs,context_mask)
        gold_spans = tag_decode(tags)
        predict.append((i,predict_spans))
        gold.append((i,gold_spans))
```
and
```python
with autocast():
    for i,batch in enumerate(tqdm_dataloader):
        txt_ids, attention_mask, token_type_ids, context_mask, turn_mask,tags=batch['txt_ids'],batch['attention_mask'],batch['token_type_ids'],\
                                                                        batch['context_mask'],batch['turn_mask'],batch['tags']
        tag_idxs = model(txt_ids.to(device), attention_mask.to(device), token_type_ids.to(device))
        predict_spans = tag_decode(tag_idxs,context_mask)
        gold_spans = tag_decode(tags)
        predict.append((i,predict_spans))
        gold.append((i,gold_spans))
```

## code that cause OOM error

```python
with autocast():
    with torch.no_grad():
        for i,batch in enumerate(tqdm_dataloader):
            txt_ids, attention_mask, token_type_ids, context_mask, turn_mask,tags=batch['txt_ids'],batch['attention_mask'],batch['token_type_ids'],\
                                                                            batch['context_mask'],batch['turn_mask'],batch['tags']
            tag_idxs = model(txt_ids.to(device), attention_mask.to(device), token_type_ids.to(device))
            predict_spans = tag_decode(tag_idxs,context_mask)
            gold_spans = tag_decode(tags)
            predict.append((i,predict_spans))
            gold.append((i,gold_spans))
```

no_grad and autocast dont't cause OOM when they work alone, but if I use them simultaneously  I get OOM error.

cc @mcarilli @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @jlin27 @mruberry
Repository: rust
Issue: bootstrap: Improve the UX when run from a git worktree
Labels: T-bootstrap,E-medium,C-feature-request,A-contributor-roadblock

it would be nice if bootstrap could auto-detect when it's being run from a git worktree and share
- the git submodule history, so it doesn't have to be refetched from the network https://github.com/rust-lang/rust/issues/77621#issuecomment-1596970050
- the config.toml from the original worktree https://github.com/rust-lang/rust/issues/77621#issuecomment-1596967245

<details><summary>original issue description</summary>

It should look something like this behind the scenes:

```
$ x.py setup --worktree ../rustc2
Setting up a new worktree at `/home/joshua/rustc2`  # runs `git worktree add ../rustc2`
# all the current prompts, but config.toml is written to rustc2 instead of the current directory
# does *not* suggest to set up a git hook
```

This would make https://rustc-dev-guide.rust-lang.org/building/suggested.html?highlight=worktree#working-on-multiple-branches-at-the-same-time a lot more discoverable.

It should also use the submodule suggestions from https://rust-lang.zulipchat.com/#narrow/stream/182449-t-compiler.2Fhelp/topic/script.20to.20quickly.20generate.20complete.20git.20worktree (cc @lzutao), which would prevent cloning llvm more than once.

This would help work around https://github.com/rust-lang/rust/issues/77620.

</details>
Repository: excalidraw
Issue: set up firebase CORS
Labels: collaboration

Right now we allow any origin so that anyone can read/write to our firebase databse. We should set up CORS to only allow excalidraw.com domain.

Downside is collab won't work in Vercel PR previews.

/cc @petehunt
Repository: rust
Issue: Type inference seems to pick up the wrong trait bound
Labels: A-trait-system,T-compiler,A-inference,C-bug,T-types

Hi.  I apologize if this is a dup (I tried to search, but is it not easy to distill this into words to search for).  If it's not a dup please update the title to something more meaningful.

When trying to compile (in [play](https://play.rust-lang.org/?mode=debug&edition=2018&gist=df374da147dde2481917344b1eafbfc8))

```rust
pub trait Distribution<T> {}

impl Distribution<u16> for () {}

fn gen<K>() -> K
where
    (): Distribution<K> {
    todo!()
}

fn foo<T>() -> u16
where
    (): Distribution<T>,
{
    gen()
}
```

I get the error:

```
error[E0308]: mismatched types
  --> src/lib.rs:15:5
   |
11 | fn foo<T>() -> u16
   |        -       --- expected `u16` because of return type
   |        |
   |        this type parameter
...
15 |     gen()
   |     ^^^^^ expected `u16`, found type parameter `T`
   |
   = note:        expected type `u16`
           found type parameter `T`
```

It it should be able to determine that the hole in `gen::<_>()` is `u16` because that's the return type of `foo()`.  Instead the compiler thinks the hole must be `T`, which is not true (in fact, if you change the call to `gen()` to `gen::<u16>()` the code compiles).

This happens in stable (1.46.0) as well as nightly 1.49.0-nightly (2020-10-05 a1dfd2490a6cb456b92e).
Repository: excalidraw
Issue: Do not use production firebase in development
Labels: discussion,collaboration

We're currently using production database even on localhost which is bad. Apart from cluttering the production database, we could inadvertently end up with stuff like infinite loops (for read/writes) when developing related features (raking huge bills), and who knows what else.

What we should do:

- [ ] set up CORS without localhost https://github.com/excalidraw/excalidraw/issues/2211
- [ ] set up Firestore emulator and write down development workflow

/cc @petehunt @vjeux
Repository: terminal
Issue: Convert Tab's context flyout into a XAML control
Labels: Area-UserInterface,Product-Terminal,Issue-Task

Tabs currently create their context flyout menu items in a big create function. It would be nice to convert that into a custom XAML control so that the more menu items we decide to add to the flyout, the easier it will be to manage. We should also design it in a way where different types of tabs (i.e. SettingsUI tab vs TerminalTab) can choose what menu items they would like to use.
Repository: ant-design
Issue: Implement a retry functionality to Ant Design's Upload Component if uploading a file fails
Labels: Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
In certain scenarios, upload fails and for those scenarios, we have to remove the picture and upload it again. This affects user experience greatly, so in order to avoid that retry functionality should be added in Upload component of Ant Design.

### What does the proposed API look like?
Add retry functionality on the picture that the user is attempting to upload which would attempt to upload the picture again without having to choose it again.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: node
Issue: CI setup for nodejs.org release notes
Labels: build

<!--
Thank you for suggesting an idea to make Node.js better.

Please fill in as much of the template below as you're able.
-->

**Is your feature request related to a problem? Please describe.**
Please describe the problem you are trying to solve.

Currently the blog post for new releases is a manual process as mentioned in https://github.com/nodejs/node/blob/b15ed6515323ec6cae2bde78feabf805c2fbb6b1/doc/guides/releases.md#17-create-a-blog-post

**Describe the solution you'd like**
Please describe the desired behavior.

When a new GitHub Release is created:
- Trigger the job based off of https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#release the `published` or `created` event
- Take content from the release. EX: https://github.com/nodejs/node/releases/tag/v12.19.0
- Create a PR to nodejs.org repo like https://github.com/nodejs/nodejs.org/pull/3436

Alternate flow would include the release `updated` event to either update the existing PR or create a new PR if information is added.

**Describe alternatives you've considered**
Please describe alternative solutions or features you have considered.

Keep it manual, as this is a small activity

/cc @nodejs/releasers
Repository: go
Issue: runtime: lack of checking of pointer returned by sysAlloc
Labels: NeedsInvestigation,compiler/runtime

Lack of checking of pointer returned by sysAlloc at [src/runtime/mpagealloc.go:395](https://github.com/golang/go/blob/930fa890c9b6a75700bda3dc4043de81350749ea/src/runtime/mpagealloc.go#L395).

Consider move nil checking into sysAlloc function itself. Currently almost all checks simply throw "runtime: cannot allocate memory".
Repository: flutter
Issue: Flutter Web border lines are discontinous on buttons
Labels: framework,f: material design,platform-web,P2,team-web,triaged-web

I'm experiencing some issues working with buttons in Flutter Web, when I apply a border radius of more than 16.
![imagen](https://user-images.githubusercontent.com/42511706/95268386-873bd180-0837-11eb-8eed-b70b859a5c09.png)
As you can appreciate in the image the border line is discontinous.

If I reduce the border radius it just doesn't happen.
![imagen](https://user-images.githubusercontent.com/42511706/95268503-c23e0500-0837-11eb-842a-2a2701df026b.png)

It happens only in some specific sizes of the screen, for example at 1920x1080.

Flutter doctor -v:
```

[√] Flutter (Channel beta, 1.22.0, on Microsoft Windows [VersiÃ³n 10.0.18363.1082], locale es-ES)
    • Flutter version 1.22.0 at C:\flutter
    • Framework revision d408d302e2 (7 days ago), 2020-09-29 11:49:17 -0700
    • Engine revision 5babba6c4d
    • Dart version 2.10.0


[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Users\F-Laptop\AppData\Local\Android\sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 43.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] IntelliJ IDEA Ultimate Edition (version 2019.3)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2019.3.3
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361

[√] VS Code, 64-bit edition (version 1.42.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.8.1

[√] Connected device (3 available)
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 85.0.4183.121
    • Edge (web)       • edge       • web-javascript • Microsoft Edge 85.0.564.68

• No issues found!
```
Repository: go
Issue: x/build/cmd/coordinator: warn if a slowbot is requested on a Go version that is known to be unsupported by the builder
Labels: Builders,NeedsInvestigation,FeatureRequest

If we can determine that the following two conditions are true:

- a builder requires at least Go 1.N or at most Go 1.M (e.g., via the [`MinimumGoVersion`](https://pkg.go.dev/golang.org/x/build/dashboard#BuildConfig.MinimumGoVersion) field or similar)
- the commit being asked for testing represents a Go version that is outside the builder's requirement (e.g., by using information in [`internal/goversion`](https://pkg.go.dev/internal/goversion) package or similar)

Then coordinator can print a warning about it when that builder is explicitly requested as a slowbot.

See #41829 for motivation.

/cc @ianlancetaylor ~@golang/release~ @cagedmantis @toothrot
Repository: pytorch
Issue: Improve distributed documentation for NCCL_BLOCKING_WAIT 
Labels: oncall: distributed,triaged,pt_distributed_rampup,module: ddp

## 📚 Documentation

We currently only document NCCL_BLOCKING_WAIT here: https://pytorch.org/docs/master/distributed.html?highlight=nccl_blocking_wait, where we say "For nccl, this is applicable only if the environment variable NCCL_BLOCKING_WAIT is set to 1.".

We should provide some more context into what NCCL_BLOCKING_WAIT is and how it can be used. For this, we can probably update the documentation to specify that it will wait for CUDA operations to complete when `synchronize()` is called, time out NCCL operations, and result in other processes also aborting those operations. 


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar @jiayisuse @agolynski
Repository: node
Issue: Background node process corrupts terminal state with tcsetattr() on exit
Labels: confirmed-bug,process

* **Version**: v14.9.0
* **Platform**: NixOS 21.03, Linux 5.8.11 x86_64
* **Subsystem**: `ResetStdio` in `src/node.cc`

In Bash, run the following:

```bash
node -e 'setTimeout(() => {}, 2000)' & sleep 1
```

This launches `node -e 'setTimeout(() => {}, 2000)'` in the background and `sleep 1` in the foreground. After 1 second, control returns to Bash. After 2 seconds, Node exits and corrupts Bash’s terminal state:

* the ↑, ↓, →, ← arrow keys start printing `^[[A`, `^[[B`, `^[[C`, `^[[D` instead of scrolling through the Bash history or moving the insert point,
* the Tab key starts moving the cursor 8 spaces forward instead of Tab-completing the command,
* Ctrl+A and Ctrl+E print `^A` and `^E` instead of jumping to the beginning and end of the command, etc.

This happens when the `ResetStdio` handler uses `tcsetattr` to “restore” the terminal to the state it was in when Node started (#24260). This interferes with Bash, which uses and expects a different terminal state than `sleep 1`.

(The bug is sometimes reproducible without the `sleep 1` depending on whether Node records the initial terminal state before Bash updates it, but the `sleep 1` makes it reliable.)

Normally, the terminal state would be protected from such undesired modifications by a background process: the kernel generates `SIGTTOU` to suspend the process until it’s brought to the foreground. But `ResetStdio` now deliberately overrides this protection by blocking `SIGTTOU` (#28535).

IMO, both #24260 and #28535 should be reverted. Node is a programming language; it should never make changes to the terminal state that programs did not request.
Repository: storybook
Issue: async configurations
Labels: feature request,configuration

**Is your feature request related to a problem? Please describe**
We have to dynamically generate some configurations based on the result of a JSON file on a server. In our case, we have a list of tenants in a JSON file, by which we want to configure addon-cssresources. But since we we just can `export parameters ...` in `preview.js` in a synchronous way, we do not have the possibility to achieve this asynchronous task.

**Describe the solution you'd like**
The config exports should also allow for asynchronous functions. E.g. in `preview.js` for parameters:
````javascript
export const parameters = async () => ({
    cssresources: await getCssResources()
});
````