sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/link: "HEADR too small" error when linking against huge static library
Labels: NeedsInvestigation,compiler/runtime

<!--
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
1.17-rc1
</pre>

(though it also applies to at least 1.16.5, and probably goes back much further)

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/Users/bendik/Library/Caches/go-build"
GOENV="/Users/bendik/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/bendik/go/pkg/mod"
GONOPROXY="git.noisolation.com"
GONOSUMDB="git.noisolation.com"
GOOS="darwin"
GOPATH="/Users/bendik/go"
GOPRIVATE="git.noisolation.com"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.17rc1"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/rq/k2szrdln2t72syt8tzhzrds80000gn/T/go-build1228245628=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

I tried to link a Go program against a static WebRTC library (32MB without debug symbols). That, in combination with using the large `net/http` package, made Go print this error: `/usr/local/go/pkg/tool/darwin_amd64/link: HEADR too small: 4408 > 4096`

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?

I expected Go to link the binary correctly.

### What did you see instead?

The aforementioned `HEADR too small` error.
Repository: pytorch
Issue: Vulkan: error -5 when trying to use it with Nvidia card
Labels: module: android,oncall: mobile,module: vulkan

## 🐛 Bug

When attempting to use Vulkan backend, it failed with error -5 (VK_ERROR_MEMORY_MAP_FAILED)

## To Reproduce

$ python3 -c 'import torch; x = torch.randn(1,3,112,112); x = x.to("vulkan")'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
RuntimeError: VkResult:-5

It fails specifically with these messages with VK_DEBUG_ALL enabled:
DEBUG: Loading layer library libVkLayer_MESA_device_select.so
INFO: Failed to find vkGetDeviceProcAddr in layer libVkLayer_MESA_device_select.so
DEBUG: Unloading layer library libVkLayer_MESA_device_select.so

Also, my original image I had attempted failed with -2 (VK_ERROR_OUT_OF_DEVICE_MEMORY) even though the size did not seem unreasonable.

$ python3 -c 'import torch; x = torch.randn(8,3,1024,768); x = x.to("vulkan")'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
RuntimeError: VkResult:-2

## Expected behavior

It works, I suppose.

## Environment

 - PyTorch Version (e.g., 1.0): 1.10.0a0+gitdb11619
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): source
 - Build command you used (if compiling from source): USE_VULKAN=1 USE_VULKAN_SHADERC_RUNTIME=1 USE_VULKAN_WRAPPER=0  python3 setup.py install
 - Python version: 3.8
 - CUDA/cuDNN version: 10.2
 - GPU models and configuration: Titan V
 - Any other relevant information: Used nvidia vulkan

$ vulkaninfo | grep "GPU id"
```
Presentable Surfaces:
=====================
GPU id : 0 (TITAN V):
GPU id : 1 (llvmpipe (LLVM 11.0.0, 256 bits)):
```
Repository: flutter
Issue: CompositedTransformFollower callback when unlinked
Labels: framework,d: api docs,P2,team-framework,triaged-framework

Currently if you use `CompositedTransformFollower` and have `showWhenUnlinked` as `false`, the follower widget will be hidden. 

How is it hidden? Is it put in offstage, I tried to read the source but couldn't quite understand it. If it is put in offstage then it will be still running there but hidden, why not just remove the widget from tree? This way we could get notified using the widget `disposed` if the widget is removed from the tree.

If the above is not possible, then I would suggest adding a callback when the follower widget is unlinked.

If there is some better way to do this without making a PR, please suggest.

Thanks 👍
Repository: three.js
Issue: GLTFExporter does not export models with normal maps correctly
Labels: Bug

`GLTFExporter` does not export models with normal maps correctly. This is a known-issue. Perhaps this post can help sort it out.

//

three.js is highly flexible. It supports both OpenGL-style and DirectX-style normal maps.

three.js also supports geometries for which uv (0, 0) corresponds to the lower-left corner, or upper-left corner, of a texture.

To achieve this flexibility, three.js provides `texture.flipY`, and the bivariate material property `normalScale`.

Conversely, the glTF spec is much more restrictive: `material.normalScale` is univariate, and the spec supports only the OpenGL-style normal maps.

This means that when a model is exported by `GLTFExporter`, the more restrictive glTF convention must be honored.

Solution:

1. If `texture.flipY `is true, then the exporter must either flip the uv's of the geometry (likely not advisable), or reorder the rows of the texture. I believe this is currently implemented correctly in the exporter.

2. If either `material.normalScale.x` or `material.normalScale.y` is negative, then the exporter must modify the red or green channels of the normal map like so:

```js
color = 255 - color;
```

I think if these rules were followed, then any three.js model having a normal map can be exported in a glTF-compliant manner.

Here is a simple test case that should be helpful in validating the exporter. The test is based on the existing glTF exporter example.

https://raw.githack.com/westlangley/three.js/dev-gltf-normalMap/examples/misc_exporter_gltf_normalMap.html

/ping @donmccurdy 

 three.js r130
Repository: flutter
Issue: Ability to move app Theme below MaterialApp (Make MediaQuery be available while constructing app Theme)
Labels: framework,f: material design,c: proposal,a: layout,P3,team-design,triaged-design

There 2 issues with app Theme currently:

## 1. Be able to move app Theme below MaterialApp, out of MaterialApp widget
Ideally it could be: `MaterialApp > MediaQuery > AnimatedTheme`

It is needed to be able to change app Theme according user setting without recreating MaterialApp widget and all widgets between.
However before user login it could be many screens, SnackBar and etc that could use default Theme.
So it could be several widgets between MaterialApp and app Theme.

However MaterialApp have built in AnimatedTheme and in this case AnimatedTheme will be duplicated:

```dart
MaterialApp(
     home: AnimatedTheme(
          data: appTheme(context),
          child: child,
```
or
```dart
MaterialApp(
     home: MediaQuery(
          child: AnimatedTheme(
               data: appTheme(context),
               child: child,
```

</br>

## 2. Make MediaQuery be available while constructing app Theme

App themes depends on current screen width / system theme type and etc.
I found workarounds that have own issues:
### 1.
```dart
MaterialApp(
     home: child,
     builder: (context, child) => AnimatedTheme(
          data: appTheme(context),
          child: child!,
```
but it duplicate `AnimatedTheme(data: ThemeData.light()` creation in the MaterialApp 


### 2.
```dart
MediaQuery(
     data: MediaQueryData.fromWindow(window),
     child: MaterialApp(
          home: child,
          theme: appTheme(context),
```
but it duplicate MediaQuery creation (or alternative widget as sample above has no MediaQuery changes notifications for the theme) in the MaterialApp
Is there any simple way to disable duplicate AnimatedTheme creation for 1.? Could it be MaterialApp parameter or etc?
Repository: godot
Issue: Mouse click (input_event) is not processed for a CollisionShape inside another CollisionShape
Labels: documentation,topic:physics

### Godot version

3.4 Beta 1

### System information

Windows 10

### Issue description

If an input_event (a mouse click) is set up for a collision area that is inside a larger collision area, and both have "Ray Pickable" enabled, the larger collision area will swallow the input_event, even when its "input_event" signal is not connected to anything.

The input_event signal on the inner collision area will not trigger.

### Steps to reproduce

Create an area and attach a box collision shape to it. 
Connect the "input_event" signal on the area to some code to fire when a mouse click event is received :
`	
if event is InputEventMouseButton:
	if event.button_index == BUTTON_LEFT and event.pressed == true:
		print("Click")
`
Verify the code is working by running the project and confirming you get debug output when you click on the area

Create a second area and attach a box collision shape to it
Make the second collision box bigger than the first so that the first box is inside the second box
Run the project and click the original collision area. You will not get the debug output.

### Minimal reproduction project

[AreaClickTest.zip](https://github.com/godotengine/godot/files/6856165/AreaClickTest.zip)
Repository: bitcoin
Issue: 0.21.1 native descriptor wallet showing incorrect value for `spendable`
Labels: Bug,Wallet

<!-- Describe the issue -->
I created a native descriptor wallet using 0.21.1 setting `blank` to `true` and `private_keys_enabled` to `false`, which the `getwalletinfo` command confirms.

I import an xpub based descriptor using `importdescriptors` to add keys to the wallet.

However when I send funds to the wallet and issue the `listunspent` command the `spendable` field shows as `true`.

`spendable` should only show `true` if the wallet holds the private keys for that UTXO, this causes my wallet software to think the node is hot when it is not.
Repository: flutter
Issue: Add Flutter module to a Flutter app
Labels: c: new feature,engine,a: existing-apps,c: proposal,P3,team-engine,triaged-engine

Hi. Our client has a Flutter application and they would like to embed our Flutter module into their app. Is this possible?

I created a POC Flutter module and a Flutter app, added the module as a dependency to the app and everything is building OK (not errors), but I don't know how to launch a module Flutter Activity? Is there a way to specify a Dart entry point from the module?

I think this might be related, though my issue is slightly different:
https://github.com/flutter/flutter/issues/39707
Repository: flutter
Issue: Specify AppBar and TabBar heights separately
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

![Screenshot 2021-07-21 at 18 19 48](https://user-images.githubusercontent.com/17653648/126523787-9018ef43-b6e4-49a3-bf33-a8d36b727a0a.png)

It would be nice to have the possibility to specify `AppBar` height and `TabBar` height separately. Currently `Appbar` has the property `toolbarHeight` which sets the overall height for `AppBar` combined with `TabBar`.

The major problem is that I have not found any working workaround to have a custom TabBar height and custom AppBar height. I was trying also to use `PreferedSize` widget for `appBar` and `bottom` properties of the `Scaffold` but this not working. If I set `PreferedSize` widget for the `appBar` then it impacts the whole AppBar with TabBar.

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal
I.e. add `appBarHeight` property to `AppBar` and `tabBarHeight` to `TabBar`. Deprecate `toolbarHeight`.
<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: pytorch
Issue: Bootcamp Task: Add `prim::to_mkldnn` to convert from aten's nchw to mkldnn's nChw8c directly
Labels: oncall: jit,module: bootcamp,jit-backlog

## Feature

Currently, MKLDNNFuser always starts a fusion group with a `aten::conv2d` operation. It replaces `aten::conv2d` with `prim::mkldnn_convolution` and inserts a conversion op (`aten::to_mkldnn`) on convolutions' input. 
`aten::to_mkldnn()` copies the input tensor into a newly allocated mkldnn tensor preserving the original layout (usually, nchw)
when we run `prim::mkldnn_convolution` we have to convert the input from the `nchw` format into MKLDNN blocked format nChw8c (avx2) or nChw16c (avx512). The second conversion-copy makes the first one wastesful and redundant.

## Motivation

The redundant copy in rare cases could lead to a ~10% slowdown

## Pitch

This proposal is to introduce a new operation `prim::to_blocked_mkldnn` that will convert `aten` tensor (in nchw) into a MKLDNN tensor in (nchw8c or nchw16c) directly.

## Alternatives



## Additional context

Using `ideep` API `reorder_to` and contstructors we should be able to get rid of a copy.


cc @gmagogsfm
Repository: pytorch
Issue: FX incorrectly provides `int` instead of `float` for `value` kwarg of `nn.functional.pad`
Labels: triaged,module: fx

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->

## To Reproduce

```
import torch
import torch.fx
from torch import nn
import torch.nn.functional as F

class Foo(nn.Module):
    def forward(self, x):
        F.pad(x, [0, 1])

module = Foo()
graph_module = torch.fx.symbolic_trace(module)
print(graph_module.code)

jit_graph_module = torch.jit.script(graph_module)
```

Output is:

```
def forward(self, x):
    _pad = torch.nn.functional._pad(x, [0, 1], mode = 'constant', value = 0);  x = None
    return None
    
RuntimeError:

_pad(Tensor input, int[] pad, str mode="constant", float value=0.) -> (Tensor):
Expected a value of type 'float' for argument 'value' but instead found type 'int'.
:
def forward(self, x):
_pad = torch.nn.functional._pad(x, [0, 1], mode = 'constant', value = 0); x = None
~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
return **None**
```

## Expected behavior

Default for `value` should be `0.` to comply with the call signature [here](https://github.com/pytorch/pytorch/blob/403f59701c2f7f533c4448579643365b5e8f2fe7/torch/nn/functional.py#L4091). **(I can confirm that changing `0` to `0.` in the linked line of code fixes it)**

## Environment

```
Collecting environment information...
PyTorch version: 1.9.0+cu111
Is debug build: False
CUDA used to build PyTorch: 11.1
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.2 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: Could not collect
CMake version: version 3.16.3
Libc version: glibc-2.31

Python version: 3.8.10 (default, Jun  2 2021, 10:49:15)  [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.8.0-59-generic-x86_64-with-glibc2.29
Is CUDA available: True
CUDA runtime version: 11.2.152
GPU models and configuration: GPU 0: GeForce RTX 3090
Nvidia driver version: 460.84
cuDNN version: Probably one of the following:
/usr/local/cuda-11.2/targets/x86_64-linux/lib/libcudnn.so.8
/usr/local/cuda-11.2/targets/x86_64-linux/lib/libcudnn_adv_infer.so.8
/usr/local/cuda-11.2/targets/x86_64-linux/lib/libcudnn_adv_train.so.8
/usr/local/cuda-11.2/targets/x86_64-linux/lib/libcudnn_cnn_infer.so.8
/usr/local/cuda-11.2/targets/x86_64-linux/lib/libcudnn_cnn_train.so.8
/usr/local/cuda-11.2/targets/x86_64-linux/lib/libcudnn_ops_infer.so.8
/usr/local/cuda-11.2/targets/x86_64-linux/lib/libcudnn_ops_train.so.8
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.21.0
[pip3] torch==1.9.0+cu111
[pip3] torchvision==0.10.0+cu111
[conda] Could not collect
```


cc @ezyang @SherlockNoMad
Repository: terminal
Issue: `Pane::_FindFocusAndNeighbor` can probably be simpler
Labels: Help Wanted,Product-Terminal,Issue-Task,Area-CodeHealth

If we view this problem from the point of the focused pane, what this function (and the other) do is basically:
* move to the parent node
* check if the _other_ child node - the one the focused pane doesn't belong to - is in the direction we want to move the pane to
  * if yes: swap panes
  * if no: continue with the parent node

Is that correct?
If my understanding is correct, I believe we can simplify this code after it has been merged.

_Originally posted by @lhecker in https://github.com/microsoft/terminal/pull/10638#discussion_r674151375_
Repository: youtube-dl
Issue: pogu.live
Labels: site-support-request

Can I already download from there? It have weird format.
Repository: create-react-app
Issue: Update @babel/core dependency from 7.12.3 to ^7.13.0
Labels: stale,needs triage,issue: bug report

When using the eject option there is now a npm install error with babel core being less than 7.13.0 caused by @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining

Error log below.
Could not resolve dependency:
peer @babel/core@"^7.13.0" from @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.14.5
node_modules/@babel/preset-env/node_modules/@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining
  @babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@"^7.14.5" from @babel/preset-env@7.14.8
  node_modules/@babel/preset-env
    @babel/preset-env@"^7.12.1" from @svgr/webpack@5.5.0
    node_modules/@svgr/webpack
      @svgr/webpack@"5.5.0" from the root project
      @svgr/webpack@"5.5.0" from react-scripts@4.0.3
      node_modules/react-scripts
    @babel/preset-env@"^7.8.4" from workbox-build@5.1.4
    node_modules/workbox-build
      workbox-build@"^5.1.4" from workbox-webpack-plugin@5.1.4
      node_modules/workbox-webpack-plugin
        workbox-webpack-plugin@"5.1.4" from the root project
        workbox-webpack-plugin@"5.1.4" from react-scripts@4.0.3
        node_modules/react-scripts

Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.
Repository: flutter
Issue: Run plugin tests on older iOS versions
Labels: a: tests,platform-ios,package,P3,team-ios,triaged-ios

Currently we run the plugin tests on a simulator with a recent version of iOS. However, the [Flutter supported platforms](https://flutter.dev/docs/development/tools/sdk/release-notes/supported-platforms) document says that back to iOS 9.3.6 is a "supported Google-tested platform", so it would be good if we were running tests against that version as well.

This is something we could potentially look into adding as a post-submit-only test, so that it doesn't bloat our resource usage and/or presubmit test times.

/cc @jmagman
Repository: flutter
Issue: Add annotations to the DisplayLists to indicate which Flutter widget generated them
Labels: engine,c: performance,P2,team-engine,triaged-engine

The goal of this would be to aid in performance debugging, for example communicating to the Flutter users which widgets contribute to an expensive picutre.
Repository: flutter
Issue: Allow the framework to compare Pictures
Labels: engine,c: performance,P2,team-engine,triaged-engine

The new DisplayList can be extended to do more precise comparison of Picture objects. The ability of the framework to precisely compare Picture objects for equality opens up a number of possibilities. One example is allowing e.g. DevTools to suggest where to add `RepaintBoundary` widgets, which can reduce CPU utilization and improve raster cache performance.
Repository: flutter
Issue: Make `TextTheme` properties non-nullable
Labels: framework,f: material design,a: typography,c: proposal,a: null-safety,P2,team-design,triaged-design

Now that the deprecated TextTheme properties were removed, I don't see a reason for keeping them nullable. Also, previously they needed to be non-null (there were a few asserts), so we are in the window now where we can me it non-null without breaking changes.

`Theme.of(context).textTheme.headline6!.copyWith()` ->
`Theme.of(context).textTheme.headline6.copyWith()`

Related:
https://github.com/flutter/flutter/pull/67673 (was waiting for this removal).
Repository: go
Issue: x/build: collect key metrics from the build infrastructure
Labels: Builders,NeedsFix

This is a tracking issue for the collection of key operational metrics from the build infrastructure. These metrics are being collected for the following reasons:
 * Increasing speed of root cause analysis when an issue arrises.
 * Understanding how changes correlate to performance changes.
 * Facilitating key areas for possible optimizations.
 * Facilitating monitoring and alerting on metrics.

The task list below will be appended to once a detailed list of key metrics are identified.
- [ ] Collect Metrics
- [ ] Create Dashboards

- [ ] GCP Aggregate Service API metrics
- [ ] AWS Aggregate Service API
- [ ] GitHub Aggregate Service API
- [ ] Gerrit Aggregate Service API
- [ ] TLS certificate lifetime
- [ ] General OS/Application/Container specific metrics

Coordinator
- [ ] Amount of time waiting for VM quota
- [ ] Buildlet creation latency by stage and type
- [ ] Total buildlet creation latency
- [ ] VM instance creation failures
- [ ] Instance creation queue depth
- [ ] Instance creation queue latency
- [ ] Active Trybot count, latency, failures by type
- [ ] Buildlet count by pool
- [ ] Pending build count by type
- [ ] Pending build latency by type
- [ ] Uptime
- [ ] Build rate
- [ ] General API instrumentation (like ochttp)

Gomote
- [ ] Sessions created
- [ ] Sessions destroyed
- [ ] Session duration
- [ ] Command usage (SSH, put, etc.)

@golang/release
Repository: godot
Issue: When using NaN as a default for an export inspector always shows reset to default arrow
Labels: bug,topic:editor

### Godot version

Engine v4.0.dev.custom_build.3478690c0

### System information

Ubuntu 21.04

### Issue description

If an exported var is set with a default of NAN, the inspector in the editor will show the reset to default arrow, even when the value is set to NAN.



### Steps to reproduce

This simply requires a derived class that can be edited in the inspector to have a default value of NAN.
```GDScript
extends Node

@export var this_is_nan = NAN
```

It will be displayed in editor with the reset arrow, even when it's already NAN
![nan](https://user-images.githubusercontent.com/26716328/126557177-cbed16c6-2e2f-4632-9988-2a9c92bb7a34.gif)


### Minimal reproduction project

_No response_