sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Please default "force-unwind-tables" to "yes" on Linux, so that unwind tables are present even if panic = "abort"
Labels: A-runtime,C-enhancement,A-codegen,T-compiler

On Linux, binaries need to contain unwind tables if one wants to get useful and accurate stack traces in profilers, debuggers and crash reports,. This requirement is mostly due to the fact that the Rust compiler, by default, does not use frame pointers on Linux.

When `panic` is set to `"unwind"` (the default), the Rust compiler emits unwind tables for all functions. This is good.

However, when building with `panic = "abort"`, the Rust compiler currently does not emit unwind tables for many functions. For example, a Linux x86_64 build of [dump_syms](https://github.com/mozilla/dump_syms/) with `panic = "abort"` has unwind tables for 5017 functions with the default settings, and for 9204 functions with `-C force-unwind-tables=yes`. The generated code for both builds is identical.

I think `force-unwind-tables=yes` would be a better default. It does not make the generated code any less efficient; it only generates extra information on the side. People who are concerned about binary size and who do not need useful stack traces can still make the trade-off and set `-C force-unwind-tables=no`.

This problem was also encountered in https://github.com/rust-lang/backtrace-rs/issues/397 and in https://github.com/rust-lang/rust/issues/81902.
Repository: go
Issue: runtime: test failure with `segmentation fault` (and no other output) on `linux-ppc64le-buildlet`
Labels: OS-Linux,NeedsInvestigation,arch-ppc64x,compiler/runtime

```
##### GOMAXPROCS=2 runtime -cpu=1,2,4 -quick
signal: segmentation fault (core dumped)
FAIL	runtime	20.337s
```

So far there is only one of these in the logs since [CL 369751](https://go.dev/cl/369751) — on `linux-ppc64le-buildlet` — but given the similarity to #49370 I wonder whether this may be a platform-independent bug in the test.
(CC @golang/runtime)

`greplogs --dashboard -md -l -e 'signal: segmentation fault .*\nFAIL\s+runtime\s+' --since=2021-12-07`

[2022-03-10T01:28:37-9faef5a/linux-ppc64le-buildlet](https://build.golang.org/log/f20264211638cb29693a87fbe631b4c10b947ab2)
Repository: PowerToys
Issue: [Feature/Enhancement] Enable GitHub Discussions
Labels: Idea-Enhancement,Area-GitHub workflow

### Description of the new feature / enhancement

Please enable GitHub Discussions feature.  Sometimes I just want to ask a question about a project and don't believe submitting an issue is the right avenue.

Is this possible?  

https://docs.github.com/en/discussions
https://www.youtube.com/watch?v=IpBw2SJkFyk&t=1s

### Scenario when this would be used?

To allow community discussions and Q&A for the project.

### Supporting information

_No response_
Repository: godot
Issue: VisualScriptFunctionCall can not choose any Function when use "Basic Type" as Call Mode
Labels: bug,topic:editor,topic:visualscript

### Godot version

3.4.3.stable (steam)

### System information

Windows 7

### Issue description

In Visual Script.

When use VisualScriptFunctionCall node in "Basic Type" mode,
there is not any thing can be chosen in Function bar.

And, if create this node by drag an out port,
that Function bar is filled automatically.
But, the node doesn't have any sequence port,
so it can not be executed by any func arrow.

I think this problem is related with commit 635d33dc6cb2226135fadeca3a2082a3c24c3757

### Steps to reproduce

In Visual Script editor.

1.1, Create a "call" node.
1.2, Change Call Mode to "Basic Type".
1.3, Choose any Basic Type.
1.4, Choose Function. <- Nothing can be chosen

Another.

2.1, Create a PoolIntArray variable
2.2, Drag it to editor, create a getter node of it.
2.3, Drag that getter node's out port, then choose "Pool Int Array Append" to create a "call" node of Basic Type.
2.4, That call node doesn't have any sequence port.

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: assertEqual gives confusing error when comparing tuple with Tensor with Tensor
Labels: module: tests,triaged

### 🐛 Describe the bug

```
        x = torch.randn([])
        self.assertEqual((x,), x)
```

This gives

```
AssertionError: The values for attribute 'shape' do not match: torch.Size([1]) != torch.Size([]).
```

Which is hella confusing.

### Versions

master

cc @mruberry
Repository: neovim
Issue: conceal: support composed character as cchar
Labels: enhancement,conceal

### Neovim version (nvim -v)

0.6.1

### Vim (not Nvim) behaves the same?

yes, vim 8.2.

### Operating system/version

ArchLinux

### Terminal name/version

xfce4-terminal

### $TERM environment variable

xterm-256

### Installation

AUR

### How to reproduce the issue

This
`:syntax match Entity "tildeP" conceal cchar=p̃`
does not work, probably because p̃ is composed from multiple bytes.
The character displayed is `p` instead of `p̃`.
Same with other characters.

Would be nice to use conceal all utf8 characters.

The setting is
`fileencoding=utf-8`

### Expected behavior

The concealed character should be: 
`p̃`

### Actual behavior

The output is:
`p`
Repository: storybook
Issue: addon-interactions 6.4.19 breaks Storybook...
Labels: bug,needs triage

Follow this guide: https://storybook.js.org/docs/react/writing-stories/play-function

Installed the package: `npm install @storybook/addon-interactions @storybook/testing-library --save-dev`

configured the package:
```

module.exports = {
  stories: ['../src/**/*.stories.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
  addons: [
    '@storybook/preset-create-react-app',
    {
      name: '@storybook/addon-storysource',
      options: {
        loaderOptions: {
          injectStoryParameters: false
        }
      }
    },
    '@storybook/addon-essentials',
    '@storybook/addon-toolbars',
    '@storybook/addon-links',
    'storybook-addon-designs',
    'storybook-react-i18next',
    //'@storybook/addon-interactions' // <= Will cause everything to fail
  ],
```

Greeted by error messages like these:
<img width="835" alt="image" src="https://user-images.githubusercontent.com/4440365/157752247-020c661f-7dc9-4beb-8d45-0d105a25591a.png">
<img width="757" alt="image" src="https://user-images.githubusercontent.com/4440365/157752321-62e91a94-32bc-4e9f-932e-64c4cdfcbfec.png">
<img width="964" alt="image" src="https://user-images.githubusercontent.com/4440365/157752410-9bc1f429-ceb2-49a8-a99c-544e8706f091.png">


Using pretty much everything latest... here is the versions in my package.json:

```
    "@storybook/addon-actions": "^6.4.19",
    "@storybook/addon-essentials": "^6.4.19",
    "@storybook/addon-interactions": "^6.4.19",
    "@storybook/addon-links": "^6.4.19",
    "@storybook/addon-storysource": "^6.4.19",
    "@storybook/preset-create-react-app": "^3.2.0",
    "@storybook/react": "6.4.19",
    "@storybook/testing-library": "0.0.9",


    "storybook": "^6.4.19",
    "storybook-addon-designs": "6.2.1",
    "storybook-react-i18next": "1.0.17",
```
Repository: pytorch
Issue: torch.fx.symbolic_trace is non-deterministic
Labels: triaged,module: fx

### 🐛 Describe the bug

If I run the following script:
```python
import torch
import torch.fx
from torch import nn

torch.manual_seed(0)
model = nn.Linear(1, 1)
for __ in range(2):
    traced = torch.fx.symbolic_trace(model)
    scripted = torch.jit.script(traced)
    print(len(scripted.save_to_buffer()))
```

on my laptop, I get:
```
2478
2514
```
indicating that I am getting two *different* torchscript files coming out of this, even though I am trying to save the same file!

From inspecting the buffers, it looks like the one difference are some extra `__torch_mangle_0` bytes inserted into the stream:
```
__torch__.torch.fx.graph_module\nLinear   # first call
__torch__.torch.fx.graph_module.___torch_mangle_0\nLinear  # second call
```

although there might be other differences in the buffers.

### Versions

```
Collecting environment information...
PyTorch version: 1.11.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Fedora release 34 (Thirty Four) (x86_64)
GCC version: (GCC) 11.2.1 20220127 (Red Hat 11.2.1-9)
Clang version: 12.0.1 (Fedora 12.0.1-1.fc34)
CMake version: Could not collect
Libc version: glibc-2.33

Python version: 3.8.12 | packaged by conda-forge | (default, Jan 30 2022, 23:53:36)  [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.15.18-100.fc34.x86_64-x86_64-with-glibc2.10
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.22.3
[pip3] torch==1.11.0
[conda] blas                      2.16                        mkl    conda-forge
[conda] cpuonly                   2.0                           0    pytorch
[conda] libblas                   3.8.0                    16_mkl    conda-forge
[conda] libcblas                  3.8.0                    16_mkl    conda-forge
[conda] liblapack                 3.8.0                    16_mkl    conda-forge
[conda] liblapacke                3.8.0                    16_mkl    conda-forge
[conda] mkl                       2020.2                      256  
[conda] numpy                     1.22.3           py38h05e7239_0    conda-forge
[conda] pytorch                   1.11.0              py3.8_cpu_0    pytorch
[conda] pytorch-mutex             1.0                         cpu    pytorch
```

cc @ezyang @SherlockNoMad
Repository: flutter
Issue: [web:html] off by one error in paragraph height measurement in Chrome 96+
Labels: engine,a: typography,platform-web,e: web_html,P2,team-web,triaged-web

In Chrome versions 96 or newer the HTML renderer measures text slightly differently from other renderers. This bug requires a special case in `cupertino/dialog_test.dart`.

## To reproduce

Make sure you have Chrome 96 or newer (this was reproducible in Chrome 96 in LUCI, and in Chrome 98 locally).

Sync to Flutter revision 8f58af8b8ce974061a1059ae7134211a8b8573b4.

Run the test below in these modes:

- `flutter test`
- `flutter test --platform=chrome --web-renderer=canvaskit`
- `flutter test --web-renderer=html`:

Test:

```dart
  testWidgets('Off by 1px', (WidgetTester tester) async {
    final ui.ParagraphBuilder b = ui.ParagraphBuilder(ui.ParagraphStyle(
      textDirection: ui.TextDirection.ltr,
    ));
    b.pushStyle(ui.TextStyle(
      fontWeight: FontWeight.w600,
      letterSpacing: -0.5,
      fontSize: 51,
      height: 1.3,
    ));
    b.addText('The Title');
    b.pop();

    final ui.Paragraph p = b.build();
    p.layout(const ui.ParagraphConstraints(width: double.infinity));
    print('Height: ${p.height}');
  });
```

## Expected behavior

In all cases the printed value of `p.height` should be exactly `66`.

## Actual behavior

The VM and CanvasKit modes print `66`. However, the HTML renderer prints `66.296875`.
Repository: rust
Issue: `IpAddr::from_str` is unnecessarily slow for IPv6 addresses
Labels: I-slow,C-enhancement,T-libs

`from_str` is implemented like so: https://github.com/rust-lang/rust/blob/5f4e0677190b82e61dc507e3e72caf89da8e5e28/library/std/src/net/parser.rs#L226-L229
This unnecessarily penalizes ipv6 addresses, because the parser will always do a full linear scan of the input before it even starts to parse the address. Instead, it could use the knowledge that IPv4 addresses are at most 15 bytes long to skip directly to `read_ipv6_addr` for longer strings.

@rustbot label: +I-slow +T-libs +C-enhancement

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"equt"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: puppeteer
Issue: Add forced-colors to emulateMediaFeature
Labels: feature

Now that forced-colors can be emulated in chromium we should add this ability to puppeteer. This will allow us to better test high contrast mode.
Repository: go
Issue: go/types, types2: add mechanism to report "last good" source file position in case of a panic
Labels: NeedsFix

We should track the source positions for the code we're in the process of type-checking so that we can report a position when panicking.

This won't simplify debugging (we can always turn on tracing), but it will make it easier for end-users to possibly find a work-around when presented with a compiler issue.
Repository: TypeScript
Issue: Module "..." cannot be named without a reference to "..." error when decl emitting references to nested modules
Labels: Bug,Domain: Declaration Emit,Rescheduled

# Bug Report

### 🔎 Search Terms

cannot be named without a reference to symlink

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

N/A

### 💻 Code

https://github.com/jcreamer898/monorepo-examples/tree/main/pnpm-example

TL;DR file layout:

```ts
// monorepo-examples\pnpm-example\packages\pkg-a\index.ts
import { FontSizes, FontWeights, ITheme, IStyle } from "@fluentui/react";

// This expression's inferred type depends on @fluentui/merge-styles
export const something = { ... 
```

`@fluentui/react` is nested in `/monorepo-examples/pnpm-example/node_modules/.pnpm/@fluentui+react`

Adding a blank import to `@fluentui/merge-styles` in `index.ts` makes the problem go away

### 🙁 Actual behavior

```
src/index.ts:28:14 - error TS2742: The inferred type of 'personScopeListItemOverrides' cannot be named without a reference to '.pnpm/@fluentui+merge-styles@8.3.0/node_modules/@fluentui/merge-styles'. This is likely not portable. A type annotation is necessary.
```

### 🙂 Expected behavior

No error
Repository: flutter
Issue: Add verbose reporting when debugging service stops in flutter_tools for web platform
Labels: c: new feature,tool,a: debugging,platform-web,c: proposal,P2,team-web,triaged-web

The following issue show verbose logs where debugging service stops with no explanation.

Adding following information on 'flutter run -d chrome --verbose' might help us understand the issue:
- Reason for exit
- If the exit is unexpected, an error and a stack trace.

Related: https://github.com/flutter/flutter/issues/99157
Repository: PowerToys
Issue: Advanced Renamer desktop app features to be added to PowerRename
Labels: Idea-New PowerToy,Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

I love PowerToys. 
Can you please take a look at Advanced Renamer desktop app features? [LINK](https://www.advancedrenamer.com/)  
to include in PowerRename!




![image](https://user-images.githubusercontent.com/27288406/157792609-7ab59a53-7a2e-445e-a011-859c58f510e9.png)


### Scenario when this would be used?

PowerRename

### Supporting information

_No response_
Repository: godot
Issue: Incorrect judgment of mouse position continues
Labels: documentation,topic:input

### Godot version

v4.0.alpha.custom_build

### System information

Windows10 Vulkan API 1.2.148 - Using Vulkan Device #0: Intel - Intel(R) UHD Graphics 630

### Issue description

I guess this is a continuation of the #22366 and #56016 questions:
The project in #56016 is still used here
The problem now is that the window size obtained by <code>get_viewport().size.y</code> and <code>get_viewport().size.x</code> when the window is minimized is consistent with the mouse position <code>event.position</code>, and it works fine. But when the window is maximized, moving the mouse to the button (or right?) side of the window will find that the mouse position exceeds the value of <code>get_viewport().size</code>.

![屏幕截图 2022-03-11 111932](https://user-images.githubusercontent.com/49355160/157796286-9ffd47b1-4d6d-430d-8d1a-62744e574ffb.png)

Please watch the video:

https://user-images.githubusercontent.com/49355160/157793363-76fc0bf5-4eca-4093-8bd8-3d475ec50906.mp4



### Steps to reproduce

The problem occurs when the window is maximized

### Minimal reproduction project

[Godot-object 4.0 test - copy.zip](https://github.com/godotengine/godot/files/8228751/Godot-object.4.0.test.-.copy.zip)
Repository: godot
Issue: Update Bitmask Region doesnt work on multiple atlases.
Labels: bug,topic:editor,topic:2d

### Godot version

3.4.2

### System information

Manjaro, Vega 8, Ryzen 3

### Issue description

Update bitmask region on the tilemap fails to update when there's more than a single Atlas picture for each autotile.

https://github.com/godotengine/godot/issues/43214

It is related to this another bug issue being reported.

### Steps to reproduce

Create multiple 3x3 minimal bitmask autotiles, one using a separate texture image.
Set up by code diferent autotiles values, by example, one autotile by grass, another for rocks, another to sand. (bug discovered on my proc gen roguelike dungeon generator).
Call update bitmask region.
Only a single autotile will be set up, the other autotiles will not be updated.

### Minimal reproduction project

_No response_
Repository: electron
Issue: [Feature Request]: is there a hook or event may like "will-enter-full-scrren"  to tell us that the window will enter fullscreen mode now ? 
Labels: enhancement :sparkles:

### Preflight Checklist

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

### Problem Description

i want to do something like recording window width before window enter full screen  
but there is no hook or event can do it

### Proposed Solution

give a hook or event before enter-full-screen. may like 'will-enter-full-screen'

### Alternatives Considered

nothing

### Additional Information

_No response_
Repository: pytorch
Issue: Two consecutive nn.LayerNorm are used in transformer model when norm_first is False
Labels: module: nn,triaged

### 🐛 Describe the bug

See the code from the master
https://github.com/pytorch/pytorch/blob/9a5c3ca23ff5f01c78c32ec710ba05942baeb019/torch/nn/modules/transformer.py#L62-L67

https://github.com/pytorch/pytorch/blob/9a5c3ca23ff5f01c78c32ec710ba05942baeb019/torch/nn/modules/transformer.py#L340-L345

When `norm_first` is False, the last layer of the encoder layer is `LayerNorm()`.

The problem is that it always puts a LayerNorm in the encoder, see
https://github.com/pytorch/pytorch/blob/9a5c3ca23ff5f01c78c32ec710ba05942baeb019/torch/nn/modules/transformer.py#L204-L205

The consequence is the output of the last encoder layer is fed into another layernorm, so two consectuive layer norm layers are used here.

Also, the output of the i-th encoder layer is used as the input for the next LayerNorm layer in (i+1)-th encoder layer.


---

**Expected behavior**: When norm_first is False, the Encoder should not contain a layer norm layer.

### Versions

The master

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @bhosmer @cpuhrsch
Repository: ant-design
Issue: 组件文档treeSelect第一个例子有错误
Labels: Inactive,🎱 Collaborate PR only

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/00nhvl)

### Steps to reproduce
初始state.value为undefined时.  组件虽然设置了value属性但并不受控
文档12行  setValue(value);  console打印value. 发现实际上设置的是 setValue(undefined).
导致组件value永远不受控.  

### What is expected?
修正文档12行的地方.  使用onChange的value参数赋值

### What is actually happening?
并没有实现

| Environment | Info |
|---|---|
| antd | 4.19.1 |
| React | 16.14.0 |
| System | windows 10 |
| Browser | chrome  79.0.3945.88 |

---
解决方案:  https://codesandbox.io/s/ji-ben-antd-4-19-1-forked-o62h13?file=/index.js


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Toggle all files in "refactor previews"
Labels: feature-request,ux,workspace-edit

<!-- ⚠️⚠️ 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. -->

I'm trying to rename a symbol from `decoder` to `is_decoder`. The "rename symbol" commonly prompts the "refactor preview" panel. 

**Problem**: I'm using vscode for running machine learning experiments and I use the popular weights&biases library. The library automatically creates codebase checkpoints for each new experiment.

I wanted to rename a symbol, and the "rename symbol" command searched through all these code checkpoints and suggested making changes in all of them. However, I want to make changes only in my main codebase.

**Suggestion**: In the "refactor preview" panel, add a button to "toggle all/uncheck all" files. Then I can select only the limited number of files was to make the code changes.

![CleanShot 2022-03-11 at 08 06 54](https://user-images.githubusercontent.com/18227298/157827839-906fa75b-a1b6-4175-8bcf-f0e6a753f8c0.png)
Repository: vscode
Issue: Some keys like "[" (left bracket) still not working in terminal (German keyboard layout)
Labels: bug,help wanted,terminal-input

I had raised this issue before in #140263 (which is now locked, preventing the natural communication channel) and it had been marked as a duplicate of https://github.com/microsoft/vscode/issues/133597, which is not quite accurate, because at least the way the issue manifests itself is different.

The issue had been closed with a note that it should be fixed in the first week of February. However the issue still isn't solved. Since this issue massively impacts the productivity in the terminal, I wish this issue can really be fixed. Either the fix had never been included in a release, or there is another regression leading to the broken behavior.

- VS Code Version: 1.65.2
- OS Version: Windows 10 Enterprise (build 19042.1526)

Detailed VSCode version:
```
Version: 1.65.2 (user setup)
Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1
Date: 2022-03-10T14:33:55.248Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19042
```

Steps to Reproduce:

1. Open the terminal in VSCode with a German Keyboard Layout
2. Try typing keys like "[" (which is `<AltGr>` + `8` on a German keyboard). It is not working at all.