sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Different breakpoint marker for unverified breakpoint before debug session start
Labels: debug,ux,under-discussion

<!-- ⚠️⚠️ 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. -->

If a user sets a breakpoint before the debug session starts, it will look like a successful breakpoint in red. Then once the debug session starts, it might get registered and stay red or it might fail to register and turn grey. Unless the program stops on entry, gets paused, etc, the user might never even notice that the breakpoint failed to register and wonder why it never got hit. 

Displaying the preliminary breakpoint as registered is misleading. Users do not always realize that the validation will happen later and that they need to check that it succeeded ([example](https://github.com/golang/vscode-go/issues/1818#issuecomment-942745182), [example](https://github.com/golang/vscode-go/issues/1840)). I propose that a different marker is used for such breakpoints with a hover message that it will be validated once the debug session is launched.
Repository: go
Issue: x/pkgsite: add e2e image snapshots for dark mode
Labels: NeedsInvestigation,pkgsite

We should consider adding snapshot tests for dark mode on a subset of pages from the e2e test suite. Full coverage is unlikely to be necessary because we have restricted color usage on pkg.go.dev to CSS variables for color intent.
Repository: flutter
Issue: When macOS apps crash on launch, no crash logs printed, fails with "Error waiting for a debug connection: The log reader stopped unexpectedly, or never started."
Labels: tool,platform-mac,a: triage improvements,P2,team-tool,triaged-tool

https://github.com/flutter/flutter/issues/85654#issuecomment-943608884 was very tricky to debug because the app crashed on launch with a codesigning error, but the `flutter` logging doesn't say what happened:
```
[hot_mode_dev_cycle_macos_target__benchmark] [STDOUT] stderr: [+1040 ms] Error waiting for a debug connection: The log reader stopped unexpectedly, or never started.
```

We should do something like https://github.com/flutter/flutter/pull/66092 for macOS to get crash logging from the debugger.
Repository: node
Issue: Investigate flaky test sequential/test-net-connect-econnrefused
Labels: net,flaky-test

### Version

amster

### Platform

s390x (but unlikely to be platform specific)

### Subsystem

net

### What steps will reproduce the bug?

run test sequential/test-net-econnect-econnrefused - https://ci.nodejs.org/job/node-test-commit-linuxone/nodes=rhel7-s390x/29181/testReport/junit/(root)/test/sequential_test_net_connect_econnrefused/

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

Intermittent, seen in 1 job and does not seem to be any open issue tracking failures

### What is the expected behavior?

Test passes

### What do you see instead?

Test fails

### Additional information

_No response_
Repository: flutter
Issue: [web] When line height is small, background could paint over text
Labels: a: typography,platform-web,P2,team-web,triaged-web

Code sample:
```dart
Container(
  width: 200,
  child: Text(
    'Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.',
    style: TextStyle(
      color: Colors.white,
      fontSize: 20.0,
      backgroundColor: Colors.black,
      height: 0.5,
    ),
  ),
)
```
Repository: excalidraw
Issue: Cant rotate to 90 degrees while in grid mode 
Labels: bug,good first issue


![image](https://user-images.githubusercontent.com/39966560/137378784-4ed9519c-2281-4e28-936e-9e1252b6da70.png)

The text shows up crooked when trying to rotate to 90% using the anchor
Repository: go
Issue: x/crypto: p256MulInternal and p256SqlInternal look like they could benefit from AVX-512
Labels: Performance,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
go version go1.16.7 linux/amd64

</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

recent Linux / amd64

### What did you do?

I ran performance profiles that involve the crypto library in Go.

I'm seeing unexpected bottlenecks in p256MulInternal and p256SqrInternal.  Looking at the code, it seems that these would benefit from AVX-512 instructions.
Repository: pytorch
Issue: [JIT] Profile optional tensor
Labels: oncall: jit

## 🚀 Feature

From Intel:

We found that when we use torch.jit.script on a conv2d module with bias=True, the specialization on the type of bias has different behaviors when the profiling graph executor is turned on or off. The issue we met is that, when we map conv2d to oneDNN graph backend, we need to know whether bias is existing or not. Optional bias is not supported in oneDNN graph. Now with profiling graph executor turned on, we fail to know this information.

When profiling graph executor is turned off:
Graph before PropagateInputShapes:
```
graph(%self : __torch__.torch.nn.modules.conv.Conv2d,
      %input.1 : Float(*, *, *, *, requires_grad=0, device=cpu)):
  %3 : int = prim::Constant[value=1]() 
  %4 : Tensor = prim::GetAttr[name="weight"](%self)
  %5 : Tensor? = prim::GetAttr[name="bias"](%self)
  %10 : int[] = prim::Constant[value=[1, 1]]()
  %11 : int[] = prim::Constant[value=[0, 0]]()
  %12 : int[] = prim::Constant[value=[1, 1]]()
  %9 : Tensor = aten::conv2d(%input.1, %4, %5, %10, %11, %12, %3) 
  return (%9)
```
Graph after PropagateInputShapes:
```
graph(%self : __torch__.torch.nn.modules.conv.Conv2d,
      %input.1 : Float(*, *, *, *, requires_grad=0, device=cpu)):
  %3 : int = prim::Constant[value=1]() 
  %4 : Float(*, *, *, *, requires_grad=0, device=cpu) = prim::GetAttr[name="weight"](%self)
  %5 : Float(*, requires_grad=0, device=cpu) = prim::GetAttr[name="bias"](%self)
  %10 : int[] = prim::Constant[value=[1, 1]]()
  %11 : int[] = prim::Constant[value=[0, 0]]()
  %12 : int[] = prim::Constant[value=[1, 1]]()
  %9 : Float(*, *, *, *, requires_grad=0, device=cpu) = aten::conv2d(%input.1, %4, %5, %10, %11, %12, %3) 
  return (%9)
```
Here %5 : Tensor? = prim::GetAttr[name="bias"](%self) has been specialized to %5 : Float(*, requires_grad=0, device=cpu) = prim::GetAttr[name="bias"](%self).
When profiling graph executor is turned off:
The bias will always be Tensor? type before and after PropagateInputShapes.
I have tried to understand the difference between these two executors and here are some findings:
When profiling graph executor is turned off, we will call specializeTypes on arg_spec_creator_, which will specialize optional tensor.
When it is on, we will directly enter the graph optimization passes without specialization on the argument spec. At the same time, in the profiling_record.cpp, we won't insertShapeProfile for optional type due to the check here. As a result, there's no chance to get the bias specialized.
We want to verify if the specialization on the argument spec is also needed for the profiling graph executor or should profiling nodes handle the optional type as well? Since currently it seems that the optional type is not handled when we turn it on.
Repository: godot
Issue: Vulkan: WorldEnvironment - Background Mode Custom Color makes metallic materials reflect pure black
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

v4.0.dev.custom_build [bf322bacd]

### System information

manjaro 21, AMD Radeon r7 200 series, Vulkan, 8GB Memory

### Issue description

When you set the background mode to custom color, all metallic materials gets black:

Reality:
![image](https://user-images.githubusercontent.com/58845030/137394023-1b960547-3d91-47ff-be00-04dbc46d1ab4.png)

Expected:
![image](https://user-images.githubusercontent.com/58845030/137394116-63fac236-4050-472e-9dd9-2fab21e7d92c.png)


### Steps to reproduce

* Create WorldEnviroment Node
* Set Background mode to custom color
* Place a model with material metallic at 1


### Minimal reproduction project

N/a
Repository: create-react-app
Issue: Allow disabling React DevTools using a new environment variable
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

Currently, CRA apps do not have any way to fully disable React DevTools via an existing, webpack configuration-based solution (https://github.com/facebook/react/pull/11448) and must resort to a more hacky solution such as the ones found here: https://github.com/facebook/react-devtools/issues/191.  

While it is possible to configure Webpack after ejecting, that seems too costly a solution for a simple change like this.

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

Add a new boolean environment variable `DISABLE_DEVTOOLS` or `DISABLE_REACT_DEVTOOLS` to [the advanced configuration list](https://create-react-app.dev/docs/advanced-configuration) so that the webpack configuration based solution can be available without ejecting. The default value for this new environment variable may be set to `false` to match the current behavior.

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

As mentioned above, one existing alternative is to eject and directly configure webpack setting. But this seems not desirable/too costly for a simple change like this. Another is to use the aforementioned hacky solution.

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

(Write your answer here.)
Repository: TypeScript
Issue: Circular reference error happens in jsdoc but not in typescript.
Labels: Bug,Help Wanted,Effort: Difficult,Domain: JSDoc

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->
circularly references itself jsdoc ts2456

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `circular`

### ⏯ Playground Link


[Playground link (js)](https://www.typescriptlang.org/play?ts=4.4.3&filetype=js#code/PQKhAIAEBcE8AcCmATRAzcBvA8gIwFaIDG0AdADwDO0ATgJYB2A5gDTgBiA9pwHwC+HbuBDAgA)
[Playground link (ts)](https://www.typescriptlang.org/play?ts=4.4.3&filetype=ts#code/C4TwDgpgBAYg9nKBeKBvAUASANoA8BcUAzsAE4CWAdgOYC6h8cA3OgL4tA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
#### Foo.js
```js
/** @typedef {Object.<string, Foo>} Foo */
```


#### Foo.ts
```ts
type Foo = {
    [x: string]: Foo;
};
```

### 🙁 Actual behavior

`Type alias 'Foo' circularly references itself. ts(2456)` happens in `Foo.js`. The TypeScript equivalent works fine.

### 🙂 Expected behavior

Both `Foo.ts` and `Foo.js` work without errors.

### Related issues
I found some related issues but they are either closed or use a different example.
#39372 - Closed (fixed)
#45641 - Seems very similar but uses `Array<>` and typescript rather than jsdoc. I'm not sure if the root cause is the same so this might be a duplicate.
Repository: storybook
Issue: Interactions: errors showing on hover event when stepping through manually
Labels: bug,addon: interactions

**Describe the bug**
When stepping through the Standard Fail Hover story, the last interaction will throw an error.

https://user-images.githubusercontent.com/1123119/137402605-1a8a86f9-6606-4885-b5eb-075c01dfdf70.mp4

**To Reproduce**


1. In the Official Storybook, navigate to Interactions > AccountForm > Standard Fail Hover.
1. Step backward and forward a few times.



┆Issue is synchronized with this [Asana task](https://app.asana.com/0/1200510412866230/1201230510952698) by [Unito](https://www.unito.io)
Repository: vscode
Issue: Links on extension pages don't work in safari or Firefox
Labels: bug,upstream,webview,firefox,safari

1. Using safari (tested with GitHub.dev)
2. Open an extension page
3. Try to click on a link to an external site on that page

**bug**
Nothing happens
Repository: godot
Issue: Full screen causes cursor offset in lower section of editor
Labels: bug,platform:macos,topic:editor

### Godot version

v3.3.4.stable.official [faf3f883d]

### System information

macOS Big Sur 11.6 MacBook Air (M1, 2020)

### Issue description

**What does not work:** When the Godot editor is in full screen mode, the mouse cursor selects/highlights a UI element that is 5-10mm below the pointer's position. In the image below shows the animation pane of the editor. The cursor highlights the zoom scroll bar even though the cursor is above the zoom UI element. 

<img width="327" alt="image" src="https://user-images.githubusercontent.com/1431772/137418216-4622e033-ac3d-422e-8090-74a40bc4d156.png">

**Expected:** The mouse cursor should select the UI element only when it the pointer is directly over the element.

### Steps to reproduce

Create a new project with a node 2D scene. Enter full screen mode.

<img width="293" alt="image" src="https://user-images.githubusercontent.com/1431772/137418504-7f44b809-5444-4e71-a476-c27a62735830.png">

Select the animation pane located at the bottom of the editor.

<img width="283" alt="image" src="https://user-images.githubusercontent.com/1431772/137418531-cfff2f03-accc-43de-b388-54276c054329.png">

Try to select the zoom scroll bar in the animation pane. Note that in order to click or select something, the cursor should be placed slightly above that particular UI element.

<img width="327" alt="image" src="https://user-images.githubusercontent.com/1431772/137418573-2a6c42bd-5dce-4e86-8c47-fb83273259f3.png">


### Minimal reproduction project

[TestProject.zip](https://github.com/godotengine/godot/files/7350265/TestProject.zip)
Repository: vscode
Issue: Cannot toggle Tab Trapping
Labels: bug,editor-contrib


Issue Type: <b>Bug</b>

When there are no files open in the workspace, <Ctrl+M> does not toggle "Tab Moves Focus". This only works when a file is open.

VS Code version: Code 1.61.1 (c13f1abb110fc756f9b3a6f16670df9cd9d4cf63, 2021-10-14T01:19:42.089Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No
Remote OS version: Linux x64 4.19.104-microsoft-standard


<!-- generated by issue reporter -->
Repository: TypeScript
Issue: Unexpected error message when using tagged union in an nested object.
Labels: Bug,Domain: Error Messages,Rescheduled

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

+ Tagged Union
+ Type Narrowing
+ Nested Object


### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This changed between versions ___3.9___ and ___4.5-beta___

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgDKgnKBxKcAmwE4A8gEYBWECYyA3gFDLPJgCeADhAFzIDkAGwxY+DJiwAevEAFcAtmWjjmbafMVRlyCQCY1CpS2Rs9yWQc0BfMaEixEKAEoFgcAbhfEw5KjXpb2Ll4+PEI3US0pM3VDFlVoiy0ofQ0GawZAlA9CLx9qWgBeNGEcUKJSSnzkAB9kZzD3MtzKmgBuMUzkAGV2ARQixiMEAHsBYeTkbPLvFtpagGcwKFAAczSxBgB6TeQAUSgocd4AFU4UPjpWM94AIiEQTCgb1uRLPmRgeeQ5T-nV1gAFigYKMxgB3f4cQ5cKBgIhfGCHORXLj8dAPLBTZq+MB8XgSAA0xiJuiJJgYIxAi2QIzGEyxFRxyAGAWu-Huj1ElnalOpizYfV4PQF-X8Q1GRzFRhY2z2B0lp1RfDuJRu70+ZmGtDg8z+KxAcDIfVYwxR5xuZTcaoAdAAKHQAZh0OgAlFojJlghyRFprNyxEA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
interface LinearGradientObject {
    type: 'linear'

    x: number
    y: number
    x2: number
    y2: number
}

interface RadialGradientObject {
    type: 'radial'

    x: number
    y: number
    r: number
}

type GradientObject = LinearGradientObject | RadialGradientObject;

type Style = {
    color: GradientObject | string
}


const style: Style = {
    color: {
        // Error: Type '"linear"' is not assignable to type '"radial"'.(2322)
        // It's not expected.
        type: 'linear'
    }
};

// Error: Type '{ type: "linear"; }' is missing the following properties from type 'LinearGradientObject': x, y, x2, y2
// It's expected
const color: GradientObject = {
    type: 'linear'
};

```

### 🙁 Actual behavior

The error when assigning the literal nested object to the `style` variable in the code above is confusing. 
```
Error: Type '"linear"' is not assignable to type '"radial"'.(2322)
```

### 🙂 Expected behavior

It will be much clearer if the error message is:
```
Error: Type '{ type: "linear"; }' is missing the following properties from type 'LinearGradientObject': x, y, x2, y2
```
Repository: flutter
Issue: [cross_file] [web] Implement `openRead` correctly.
Labels: c: new feature,package,team-ecosystem,P1,p: cross_file,triaged-ecosystem

The current implementation of `XFile.openRead` is not really streaming the contents of the enclosed Blob as a Stream. It just slices a cached blob and returning that slice, in one go.

People are chunking files by computing the chunks from the outside using the start/end variables, and then listening for the (only) event on the Stream. This is very inefficient, and even though it works, it is **not** what the Stream is supposed to do!

Users need to get a Stream from the slice they care about in the blob, and then read it until its completion. See an example of the [dart:io implementation: `_FileStream`](https://github.com/dart-lang/sdk/blob/main/sdk/lib/io/file_impl.dart#L8-L156)

`cross_file` needs a `_BlobStream` class for its web implementation.
Repository: flutter
Issue: [cross_file] Platform-aware factories.
Labels: c: new feature,package,team-ecosystem,P2,p: cross_file,triaged-ecosystem

The current implementation of `cross_file` relies on cross-platform constructors that "need to work" across all platforms. With time, and as features are added, these constructors end up growing, and now some parameters are being ignored by some platforms and used by others. This causes [confusion/problems](https://github.com/flutter/flutter/issues/87812).

It seems that cross-platform constructors are not the way to go for this particular package; instead XFile users should be able to choose what factory they need for the platform that they're implementing. So, in places where `dart:io` is available, they could do:

`XFileIO.fromFile(io.File file)` or `XFileIO.fromPath(String path)`

But if `dart:html` is available

`XFileWeb.fromHtmlFile(html.File file)` or  `XFileWeb.fromBlob(html.Blob blob, String name)` or `XFileWeb.fromBlobUrl(String blobUrl, String name, int length...)`...

or any other "specialty" constructors that would make sense per platform. 

The `XFile` class that most people use would end up being a read-only interface to retrieve data from the file, and the different backing implementations would extend it.

(This would also allow us to return `XFile` as the base-class name for all the objects, instead of being the top-most classname, which is weird from an OOP standpoint!)

Some questions:

* What to do when the user wants to modify the contents of a file programmatically?
* How to perform those operations so the modified file still uses an efficient backend?
* Should we keep an "inefficient" Uint8List-backed constructor so people can build raw files from memory?
Repository: godot
Issue: GLTF model causes godot importer to freeze (Blender can open it)
Labels: bug,topic:import,crash

### Godot version

3.3.4 stable

### System information

Windows 7 64 bit

### Issue description

I have a gltf that freezes the editor. Blender has no problems opening this file.

### Steps to reproduce

Create a new project and add the model uploaded below to the project. Upon importing, the editor freezes.

### Minimal reproduction project

Add this model to a project, when it auto imports the editor freezes.

[broken_model.zip](https://github.com/godotengine/godot/files/7350587/broken_model.zip)
Repository: pytorch
Issue: Adding modern linear transformer variants to `transformer` module
Labels: module: nn,triaged,enhancement

## 🚀 Feature
Adding more linear variants of the Transformer architectures to `transformer`.
- Use feature maps to get linearization.
- Two-level or Multilevel-based methods: patch.
- Low-rank approximation: Nystrom, fast multipole, etc.
- Various normalization schemes: Galerkin (a shameless plug-in...), etc.

## Motivation

It would be beneficial for users to define their own MHA.
- The current default `nn.Transformer` is extremely slow for long sequences using the default softmax MHA.
- Current implementation assumes the input is a sequence `(bsz, seq_len, emb_dim)`, the ideal one would be `(bsz, *, emb_dim)` for grid-based application (like ViT or AlphaFold).

## Pitch

Currently the `nn.MultiheadAttention` is just a wrapper for `nn.functional.multi_head_attention_forward`, so why not make it more completely detached and become a container of user defined Transformer architecture, with the default one being the current one:

```python
class MultiHeadAttention(Module):
    def __init__(self, norm, proj, attn):
        ...
        self.norm = norm
        self.proj = proj
        self.attn = attn

    def forward(self, q, k, v, mask):
        q, k, v = self.proj(q, k, v)
        q, k, v = self.norm[0](q, k, v)
        x = self.attn(q, k, v, mask)
        x = self.norm[1](x)
        ... 
        return x
```
However, this does not allow multilevel hierarchical interaction (`x` interacts with what is happening in `self.proj`). So there has to be a better way to unify everything.


cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @bhosmer @cpuhrsch