sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: net: TestTCPServer/tcp4_:0<-127.0.0.1 failures on Windows with `EOF` (and no other output)
Labels: help wanted,OS-Windows,NeedsInvestigation

```
--- FAIL: TestTCPServer (0.02s)
    --- FAIL: TestTCPServer/tcp4_:0<-127.0.0.1 (0.00s)
        server_test.go:113: #19: EOF
FAIL
FAIL	net	54.788s
```

`greplogs -l -e 'FAIL: TestTCPServer .*(?:\n[ ]+.*)* EOF'`
[2022-05-13T21:00:31-e755a56/windows-amd64-longtest](https://build.golang.org/log/2d2cf5a8ca64977282b9d1e66d0f5d3e9e5dcfa1)
[2019-11-07T02:33:31-198f045/windows-amd64-longtest](https://build.golang.org/log/bf58a3ebbcdfff30c37701a09b0309c105b7ebd8)

Probably a good first step would be to update this test to log more information about what's going on (per https://go.dev/wiki/CodeReviewComments#useful-test-failures), although given the low rate of occurrence it may be a while before we get another hit. 😅

(CC @ianlancetaylor @neild @golang/windows)
Repository: pytorch
Issue: lintrunner doesn't give good error message suggesting lintrunner init
Labels: module: lint,triaged

### 🐛 Describe the bug

```
  Error (CLANGTIDY) Linter failed
    Linter failed. This a bug, please file an issue against the linter
    maintainer.
    
    CONTEXT:
    Linter command failed with non-zero exit code.
    STDERR:
    Traceback (most recent call last):
      File "tools/linter/adapters/clangtidy_linter.py", line 138, in <module>
        ] + clang_search_dirs()
      File "tools/linter/adapters/clangtidy_linter.py", line 106, in
    clang_search_dirs
        result = subprocess.run(
      File "/scratch/ezyang/pytorch-scratch2-env/lib/python3.8/subprocess.py",
    line 512, in run
        raise CalledProcessError(retcode, process.args,
    subprocess.CalledProcessError: Command '['clang', '-E', '-x', 'c++', '-',
    '-v']' returned non-zero exit status 1.
    
    
    STDOUT:
    

```

cc @suo 

I have to say this is a very useless error message lol. I think the problem is I didn't run lintrunner init.

### Versions

master
Repository: rust
Issue: Should debuggers treat ZSTs initializers as code to step through?
Labels: A-debuginfo,I-needs-decision,T-compiler

Spawned off of https://github.com/rust-lang/rust/issues/33013#issuecomment-282736708

If you look at the beginning of the example there:

```rust
fn main () {
    let a = ();
    let b : [i32; 0] = [];
    let mut c = 27;
    let d = c = 99;
    [...]
}
```

the first two variables, `a` and `b`, are both ZSTs.

When you run this in a debugger and try to step though each statement, like so:

```
(gdb) break step::main
(gdb) run
Breakpoint 1, step::main () at step.rs:4
4       let mut c = 27;
(gdb) next
5       let d = c = 99;
```

you can see that the gdb `next` command has "skipped" the initialization of `a` and `b`.

This is understandable to a Rust expert, because `a` and `b` are both zero-sized types, and so no code is generated for initializing those local variables.

But for a Rust beginner, it is confusing.

If we wanted to, we could make `-g` mode deal with this. For example, we could generate `nop`'s for such initializers, and then  give the `nop`'s corresponding debug info. But that is also pessimizing the code generation to accommodate beginners.

This is something we need to make a decision on whether it is an actual bug we would like to fix or not.
Repository: PowerToys
Issue: System App Replacer
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Similarly to the option in Process Explorer to replace Task Manager, this feature will allow users to replace system applications, and the hotkeys or actions that trigger them, with applications they prefer.

![image](https://user-images.githubusercontent.com/716581/168623492-65b84c00-0bf9-4dee-9558-541280ff9734.png)

This feature can be implemented by using [Image File Execution Options](https://docs.microsoft.com/en-us/previous-versions/windows/desktop/xperf/image-file-execution-options) and will require the UseFilter DWORD to be set to 1 to prevent odd issues. 


### Scenario when this would be used?

- Keyboards with a dedicated application hotkeys can be set to open a preferred applications
- Task Manager can be replaced with Process Explorer or another preferred process manager
- Other non-easily replaced system applications can be swapped out to use the user's preferred application

### Supporting information

_No response_
Repository: transformers
Issue: GPT-neo generate is ignoring passed position ids
Labels: WIP,bug

### System Info

```shell
python version: 3.9
transformers version: 4.18
```


### Who can help?

@patil-suraj @patrickvonplaten 

### Information

- [ ] The official example scripts
- [X] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [X] My own task or dataset (give details below)

### Reproduction

``` 

from transformers import AutoTokenizer, AutoModelForCausalLM
import torch 

text = "hi there: "
modelname = "EleutherAI/gpt-neo-125M"
model = AutoModelForCausalLM.from_pretrained(modelname)
tokenizer = AutoTokenizer.from_pretrained(modelname)

inputs = tokenizer(text, return_tensors ="pt")
inputs["position_ids"] = inputs["attention_mask"].cumsum(-1)
print(inputs)
a = model.generate(**inputs)


inputs["position_ids"] = inputs["position_ids"] + 10
print(inputs)
b = model.generate(**inputs)

# a and b should be different because the position ids are different
print(a)
print(b)
```
the result
```
a = tensor([[5303,  612,   25,  220,  220,  220,  220,  220,  220,  220,  220,  220,
          220,  220,  220,  220,  220,  220,  220,  220]])
b = tensor([[5303,  612,   25,  220,  220,  220,  220,  220,  220,  220,  220,  220,
          220,  220,  220,  220,  220,  220,  220,  220]])
```

### Expected behavior

```shell
The outputs a and b should (almost always) be different because different position ids should be passed to the model's forward function, resulting in different activations. The issue seems to be here: https://github.com/huggingface/transformers/blob/ee393c009a243bbb86fa11d2efa771a1704d85cf/src/transformers/models/gpt_neo/modeling_gpt_neo.py#L699

Specifically, the else statement is such that if both an attention mask and position ids are passed, the position ids are erased. In such a scenario, the default position ids in the model's forward function (https://github.com/huggingface/transformers/blob/ee393c009a243bbb86fa11d2efa771a1704d85cf/src/transformers/models/gpt_neo/modeling_gpt_neo.py#L537) are used, rather than the passed-in position ids. 

Proposed fix: remove the `else` block on line 699 and unindent the `if past` block.
```
Repository: go
Issue: x/build/cmd/coordinator: decide what to do about the global VM/pod timeout
Labels: Builders,NeedsInvestigation

The comment of [`CleanUpOldVMs`](https://cs.opensource.google/go/x/build/+/master:internal/coordinator/pool/gce.go;l=648-661;drc=3ab5e7e87a80893ee88aba0e9de7e86cde9f5a0a) (and `CleanUpOldPodsLoop`) includes:

> This is the safety mechanism to delete VMs which stray from the
> normal deleting process. VMs are created to run a single build and
> should be shut down by a controlling process. Due to various types
> of failures, they might get stranded. To prevent them from getting
> stranded and wasting resources forever, we instead set the
> "delete-at" metadata attribute on them when created to some time
> that's well beyond their expected lifetime.

This mechanism requires maintaining a timeout for builds, one that's always "well beyond their expected lifetime". If that stops being true, also depending on the state of #42699, resources may be wasted due multiple retries (as happened in #49666 and #52591 in 2021-2022).

Since coordinator knows about all the builds it started, and already deletes builds that it doesn't know about (e.g., because they're left over from a previous instance of coordinator), I don't think a timer is actually needed for that. However, it might still be useful to handle stalls or other unexpected reasons why a build keeps going beyond a "reasonable" timeframe. So maybe we'll always need to maintain such a timeout.

One of the things we can do in either case is add better metrics/monitoring, so we find out when normal builds start to get dangerously close to the limit before it starts to cause problems.

[CL 406216](https://go.dev/cl/406216) increased the global timeout for builds from 45 mins to 2 hours to accommodate longtest builders, and this is the tracking issue to figure out what we want to do in this space long term. (Possibly simply bump it up from 2 hours if some builds need even longer in the future.)

CC @golang/release.
Repository: pytorch
Issue: Investigate sharded gradscaler OOM on CPU workloads
Labels: oncall: distributed,module: fsdp

### 🐛 Describe the bug

Sharded grad scaler for FSDP + mixed precision is landed: https://github.com/pytorch/pytorch/pull/76918, although we're seeing an OOM on workloads with CPU offload at the moment. We should investigate and fix this OOM. 

### Versions

main

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang
Repository: flutter
Issue: [plugins] Add engine retain cycle tests to all plugins
Labels: a: tests,team,platform-ios,package,P2,team-ios,triaged-ios

We've had bugs in a number of plugins where just setting them up creates a retain cycle that keeps the engine alive forever (e.g., due to engine foot-guns like https://github.com/flutter/flutter/issues/102990).

We should have a test in every plugin that calls `registerWithRegistrar` with a fake registrar that holds a strong reference to it when a channel handler is added, and also that returns itself as any of the called helper objects (binary messenger, texture registrar, etc.—using a strict mock to make sure we aren't missing any and accidentally returning nil). The test should drop its reference to the fake registrar, and then ensure that it nils out.

This would be more strict than the engine actually is (e.g., the binary messenger won't make a loop any more), but it should probably never actually be necessary to have a strong reference to something that's owned by the engine anyway, because if the engine is gone calling it is at best a no-op anyway (and in some cases an error).

This would ensure we aren't relying on add-to-app customers to find these one at a time, and also be a good backstop against accidentally introducing retain loop foot-guns with any new engine APIs.

/cc @jmagman @cyanglaz
Repository: pytorch
Issue: `stateless.functional_call` doesn't work with `nn.DataParallel`
Labels: module: nn,triaged,module: data parallel,actionable

### 🐛 Describe the bug

Encountered in https://github.com/pytorch/pytorch/pull/77137#issuecomment-1125694907 
```
import torch
import torch.nn as nn
import torch.nn.utils.stateless as stateless

class Foo(nn.Module):
    def __init__(self):
        super().__init__()
        self.weight = nn.Parameter(torch.ones(5))

    def forward(self, x):
        return self.weight + x

mod = Foo().cuda()
mod = nn.DataParallel(mod, [0, 1])
print(stateless.functional_call(mod, {'module.weight': torch.zeros(5, device='cuda')}, (torch.ones(2, 5, device='cuda'),)))
```
errors with
``
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cuda:1!
```

### Versions

Nightly

cc @ezyang @gchanan @zou3519 @albanD @mruberry @jbschlosser @walterddr @kshitij12345
Repository: flutter
Issue: Create linter that flags `Double.clamp` usage
Labels: framework,P2,team-framework,triaged-framework

`clampDouble` is 12x faster than `Double.clamp` and we should make sure that new usage of `Double.clamp` don't show up.

Context: https://github.com/flutter/flutter/pull/103559

I tried to implement it in `dev/bots/analyze.dart` but I got blocked with my AST's were not "resolved" so I didn't have the type information to know if we are calling clamp on doubles.

Here's how far I got:
```dart
class _DoubleClampVisitor extends RecursiveAstVisitor<CompilationUnit> {
  List<int> doubleClamps = <int>[];
  final ParseStringResult parseResult;
  _DoubleClampVisitor(this.parseResult);

  @override
  CompilationUnit? visitMethodInvocation(MethodInvocation node) {
    if (node.methodName.name == 'clamp') {
      print(node.argumentList.arguments.first);
    }

    node.visitChildren(this);
    return null;
  }
}

/// Verify that we use clampDouble instead of Double.clamp for performance reasons.
Future<void> verifyNoDoubleClamp(String workingDirectory) async {
  final String flutterLibPath = '$workingDirectory/packages/flutter/lib';
  final Stream<File> testFiles =
      _allFiles(flutterLibPath, 'dart', minimumMatches: 100);
  await for (final File file in testFiles) {
    try {
      final ParseStringResult parseResult = parseFile(
        featureSet: FeatureSet.fromEnableFlags2(
            sdkLanguageVersion: Version.parse('2.17.0-0'),
            flags: <String>['super-parameters']),
        path: file.absolute.path,
      );
      final _DoubleClampVisitor visitor = _DoubleClampVisitor(parseResult);
      visitor.visitCompilationUnit(parseResult.unit);
      for (final int doubleClamp in visitor.doubleClamps) {
        final int lineNumber =
            parseResult.lineInfo.getLocation(doubleClamp).lineNumber;
        print('${file.path} $lineNumber');
      }
    } catch (ex) {
      /// TODO(gaaclarke): There appears to be a bug with super parameter
      /// parsing on mac so we skip certain files until that is fixed.
      print('skipping ${file.path}: $ex');
    }
  }
}
```
Repository: pytorch
Issue: FSDP: test mixed precision with checkpoint
Labels: oncall: distributed,triaged,module: fsdp

### 🚀 The feature, motivation and pitch

When training with mixed precision, we should ensure we take checkpoint with parameters, buffers in full precision so that it can be loaded in for full precision retraining. We currently cast params and buffers to their full precision dtype before taking checkpoint, but this should be validated via unittests.

### Alternatives

_No response_

### Additional context

_No response_

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @kwen2501
Repository: PowerToys
Issue: Fanzy Zones and task view coordination suggestion
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

Custom Fancy zones can be named.  Using task view to create multiple desktops, can be individually named.

how about, if there is a match, the fancyzone gets active based on that name when the desktop is at the fore?

I could create my 'photoshop' desktop, my 'email' desktop and my 'writing' desktop-  
zones to match... and as I ctrl+win+left or right from desktop to desktop the fancy zone that is active will change....


### Scenario when this would be used?

to know that the fancyzone I want with process X is active when I approach each task?  
not have to keep rechoosing my zone when I change desktops? 

This one feels obvious.....

### Supporting information

_No response_
Repository: pytorch
Issue: How to handle __module__  attribute for Public API bindings
Labels: module: tests,triaged

While working on the NN onboarding lab (with corresponding closed PR: #77425 ), after registering the functional version of new module in `torch/nn/functional.py` The following test would fail ` pytest test/test_public_bindings.py` with:
```Bash
Full list:
# torch.nn.functional.bias:
  - Is public: it is an attribute that does not start with `_` on a module that does not have `__all__` defined
  - Does NOT look public: because its `__module__` attribute (`torch._C._nn`) is not within the torch library or does not start with the submodule where it is defined (`torch.nn.functional`)
  - You can do either of these two things to fix this problem:
    - To make it NOT public: either define a `__all__` for `torch.nn.functional` or add a `_` at the beginning of the name
    - To make it look public: make sure the `__module__` is properly set and points to a submodule of `torch.nn.functional`
```    
I defined the functional version analogously to the linear module:
```Python
bias = _add_docstr(
    torch._C._nn.bias,
    r"""
bias(input, bias) -> Tensor

Adds a bias vector the last dimension of input tensor

Shape:
    - Input: math:`(*, num\_features)` where `*` means any number of
      additional dimensions, including none
    - Bias: :math:`(num\_features)` or :math:`()`
    - Output: :math:`(*, num\_features)` where `*` means any number of
      additional dimensions, including none, same shape as Input
""")
```

I add this function 'bias' to the allowlist here: `test/allowlist_for_publicAPI.json` in the list for `"torch.nn.functional"`

When reading the test function though it says that no new functions should be added to this list. If I def bias above and then implement `bias.__module__ = 'torch.nn.functional'` This does indeed work. 

Is that the correct solution?
 Would it be a nicer API if there was a function analogous to `_add_docstr` which also defined the `__module__` attribute when setting the doc string.


cc @mruberry
Repository: electron
Issue: [Bug]: attached webContents.debugger interferes with renderer devtools dom element selection
Labels: component/devtools,bug :beetle:,platform/all,has-repro-gist,17-x-y,18-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

18.2.3, 17.1.2

### What operating system are you using?

Windows

### Operating System Version

win7 sp1

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

devtools DOM element selector should work

### Actual Behavior

1. run the testcase fiddle
2. in devtools console enter `location = 'https://www.verizon.com/'`
3. switch to the elements tab and use the element selector tool to select an element in the page
4. the selected element does not get highlighted in the elements tree, seemingly because the tree is not in sync with the page

### Testcase Gist URL

https://gist.github.com/8d64059054a91672a21a5aef1ca32dcf

### Additional Information

Reproducibility appears to depend on the complexity of the site. Some sites are intermittent, for me https://www.verizon.com is reliable.
Repository: flutter
Issue: Fuchsia input APIs don't report channel tombstone
Labels: engine,dependency: fuchsia,platform-fuchsia,P2,team-engine,triaged-engine

The Fuchsia input API hookups in pointer_delegate.cc don't report channel error messages, which helps with debugging. For TouchSource and MouseSource.
Repository: godot
Issue: Area3D - Connecting via code doesn't call target method
Labels: bug,topic:physics

### Godot version

v4.0.alpha.mono.custom_build [947a1fa09]

### System information

manjaro KDE

### Issue description

When you connect the Area3D via code, it doesnt work (doesnt call the target function)

```csharp
using Godot;
using System;

public partial class Area3D : Godot.Area3D
{
    public override void _Ready()
    {
        base._Ready();
        Connect("body_entered",new Callable(this, nameof(OnEntered)),new Godot.Collections.Array {"hello"});
    }

    public void OnEntered(Node3D body, string msg)
    {
        GD.Print("Player: ", body.Name, "entered -> ", msg);
    }
}

```

PS: Even this "bug" is an error of mine, godot should tell me the error, so probably related to: #59830


### Steps to reproduce

* Create a CHaracterBody
* Create an Area3D
* Attach script to Area3D
* connect via code (shown above)
* test in-game
* should see the error

### Minimal reproduction project

[AreaTest.zip](https://github.com/godotengine/godot/files/8703553/AreaTest.zip)
Repository: vscode
Issue: [scss] don't autocomplete in comments
Labels: bug,css-less-scss


Issue Type: <b>Bug</b>

I'm trying to type a scss comment. However, autocomplete is presenting useless suggestions for the content of the comment. For example, here I've typed a colon because I'm about to type a list. However, autocomplete has presented a list of junk, so when I press enter, it's going to prefill some junk instead of a newline like I wanted.

![Screen Shot 2022-05-16 at 5 41 50 PM](https://user-images.githubusercontent.com/10030156/168687546-49888297-3df3-4937-a4c0-7556f219243f.png)

VS Code version: Code 1.67.1 (da15b6fd3ef856477bf6f4fb29ba1b7af717770d, 2022-05-06T12:37:16.526Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 3, 4|
|Memory (System)|16.00GB (0.24GB free)|
|Process Argv|--crash-reporter-id 656c6348-b102-4b6b-8ade-e7f56a3faa5f|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (10)</summary>

Extension|Author (truncated)|Version
---|---|---
cform|aws|0.0.24
go|gol|0.33.0
vscode-scss|mrm|0.10.0
vscode-docker|ms-|1.22.0
vscode-kubernetes-tools|ms-|1.3.8
remote-containers|ms-|0.234.0
cpptools|ms-|1.9.8
vscode-commons|red|0.0.6
vscode-yaml|red|1.7.0
vscode-proto3|zxh|0.5.5


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebugcf:30475217
vscaac:30438847
vsclangdc:30486549

```

</details>

<!-- generated by issue reporter -->