sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/pkgsite: make package path visible after scroll down
Labels: NeedsInvestigation,pkgsite,UX

<!--
Please answer these questions before submitting your issue. Thanks!
-->
 
### What is the URL of the page with the issue?
 
 EG https://pkg.go.dev/github.com/go-air/pal@v0.0.5/memory
 
### What is your user agent?
 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1 Safari/605.1.15


 
 
 
### Screenshot
 
<!--
Please paste a screenshot of the page.
-->
 
 
 
### What did you do?
 
scroll down when there is enough documentation content to scroll.
 
 
### What did you expect to see?
 
 The path name of the current package at the top of the page (eg GitHub.com/go-air/pal/memory)
 
### What did you see instead?

the name "memory" and a button to copy the path above to the clipboard.

The reason I find this can be confused is that there are lots of packages with the same name and lots of documentation.

One kinda has to scroll up to the package path in order to navigate up.

It would be great if
1.  the package path were visible on the top bar after scrolling down.
2. keybindings were in place to scroll to the parent package or module
Repository: rust
Issue: cargo test 'test-threads' uses more threads than specified
Labels: A-libtest,C-bug,A-thread,T-testing-devex

## Summary

So I have noticed that `cargo test` actually uses more threads than is actually specified, and actually spawns a new thread for every test, as opposed to re-using threads in a pool. This is in many ways a bug because some tests the depend on thread local storage cannot be run in concurrent mode.

## Reproduction Steps

1. Create a fresh cargo project with a library.
2. Create a file called `tlocal.rs` , and list it in the `lib.rs` as a module.
3. Use the following code to create a very simple thread local storage:

```rust
use std::sync::atomic::{AtomicUsize, Ordering};
use std::thread;

static THREAD_CNTR:AtomicUsize = AtomicUsize::new(0);

thread_local!(static TH_ID:usize = THREAD_CNTR.fetch_add(1, Ordering::SeqCst));

pub fn tid() -> usize {
    TH_ID.with(|x| { *x })
}
```
4. Write a test module in the same file, such as 

```rust
#[cfg(test)]
mod tests {
    use super::*;

    #[test]
    fn tid_works() {
    	assert!(tid() < 2);
    }

    #[test]
    fn tid_works2() {
    	assert!(tid() < 2);
    }

    #[test]
    fn tid_works3() {
    	assert!(tid() < 2);
    }
}
```
5. Run `cargo test -- --test-threads=2`

I expected to see this happen: The tests pass.

Instead, this happened: The test fail with these errors:

```rust
---- tlocal::tests::tid_works stdout ----
thread 'tlocal::tests::tid_works' panicked at 'assertion failed: tid() < 2', src/tlocal.rs:62:9

---- tlocal::tests::tid_works2 stdout ----
thread 'tlocal::tests::tid_works2' panicked at 'assertion failed: tid() < 2', src/tlocal.rs:67:9

---- tlocal::tests::tid_works3 stdout ----
thread 'tlocal::tests::tid_works3' panicked at 'assertion failed: tid() < 2', src/tlocal.rs:72:9
```

### Meta

`rustc --version --verbose`:
```
% rustc --version --verbose      
rustc 1.52.1 (9bc8c42bb 2021-05-09)
binary: rustc
commit-hash: 9bc8c42bb2f19e745a63f3445f1ac248fb015e53
commit-date: 2021-05-09
host: x86_64-apple-darwin
release: 1.52.1
LLVM version: 12.0.0
```

## Problem

This is a bug because more than the stated number of threads are actually being used to run the tests. Ideally, this should either be clarified in the docs, or a way of running tests in a thread pool should be provided.
Repository: rust
Issue: Wrong suggestion for E0223 when using type alias
Labels: A-diagnostics,T-compiler

Given the following code:

```rust
type Length = f64;
const MyPI: Length = Length::consts::PI;
```

The current output is:

```
   Compiling playground v0.0.1 (/playground)
error[E0223]: ambiguous associated type
 --> src/lib.rs:2:22
  |
2 | const MyPI: Length = Length::consts::PI;
  |                      ^^^^^^^^^^^^^^ help: use fully-qualified syntax: `<f64 as Trait>::consts`

For more information about this error, try `rustc --explain E0223`.
```

rustc gets confused by the type alias for `f64` via `Length`, leading it to suggest the fully-qualified syntax. If we replace `Length` with `f64` (the primitive type), we get the correct suggestion:

```rust
type Length = f64;
const MyPI: Length = f64::consts::PI;
```

```
error[E0223]: ambiguous associated type
 --> src/lib.rs:2:22
  |
2 | const MyPI: Length = f64::consts::PI;
  |                      ^^^^^^^^^^^
  |
help: you are looking for the module in `std`, not the primitive type
  |
2 | const MyPI: Length = std::f64::consts::PI;
  |                      ~~~~~~~~~~~~~~~~

For more information about this error, try `rustc --explain E0223`.
```
Repository: transformers
Issue: "Resource exhausted" when loading Flax GPT-Neo 2.7B
Labels: WIP

## Environment info

- `transformers` version: 4.10.0.dev0
- Platform: Linux-5.4.0-1043-gcp-x86_64-with-glibc2.29
- Python version: 3.8.5
- PyTorch version (GPU?): 1.8.1+cu102 (False)
- Tensorflow version (GPU?): 2.6.0 (False)
- Flax version (CPU?/GPU?/TPU?): 0.3.4 (cpu)
- Jax version: 0.2.19
- JaxLib version: 0.1.70
- Using GPU in script?: <fill in>
- Using distributed or parallel set-up in script?: <fill in>

### Who can help
@patrickvonplaten @patil-suraj @LysandreJik

## Information

I am not able to load the Flax GPT-Neo 2.7B model in my TPU VM v3-8 instance. 
```python
tokenizer = AutoTokenizer.from_pretrained("EleutherAI/gpt-neo-2.7B", pad_token="
", padding_side="left")
model = FlaxAutoModelForCausalLM.from_pretrained("EleutherAI/gpt-neo-2.7B", pad_token_id=tokenizer.eos_token_id)
```
The model will download but will fail to load with
```
RuntimeError: Resource exhausted: Failed to allocate request for 100.00MiB (104857600B) on device ordinal 0
```
However, the pytorch version will load and run just fine.
Repository: flutter
Issue: Extremely slow layout with CupertinoPageRoute and Text
Labels: framework,c: performance,f: cupertino,f: routes,a: typography,perf: speed,has reproducible steps,P2,found in release: 3.7,found in release: 3.10,team-design,triaged-design

Hello,

I've been trying to optimize my app for a few days now and I've also encountered a strange problem.

As soon as you open a new page with a CupertinoPageRoute, there is a lag in the UI thread. According to the profiler this is due to the layout method which takes extremely long.

However, this only happens when the text widget is used in the page to be opened.

Reproducible example:
https://gist.github.com/b3nni97/fb68792baced3ce44201db8fcc404577

This is the result from the profiler when the text widget is used:
![ui-lag-no-cache](https://user-images.githubusercontent.com/18357332/130361412-1d89092b-5d22-4ecd-a755-fa1b50bdc640.png)

This is the result from the profiler when the text widget is **NOT** used:
![ui-lag-free-no-cache](https://user-images.githubusercontent.com/18357332/130361440-b33eef31-0fd5-46d8-abe3-598d1483d28f.png)

**Target Platform: iOS**
**Target OS version/browser: iOS 15**
**Devices: iPhone 12 Pro Max**

**I have been able to reproduce the problem on the Beta, Dev and the latest Master Channel.**
Repository: opencv
Issue: Unable to use static library
Labels: duplicate,category: build/install,incomplete

<!--
If you have a question rather than reporting a bug please go to https://forum.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

##### System information (version)
- OpenCV => 4.5.3
- Operating System / Platform => Windows 10 64 Bit
- Compiler => Visual Studio 2019

##### Detailed description

After building library with -DBUILD_SHARED_LIBS=FALSE, installing it, and trying to use it, cmake outputs:
```1> [CMake] CMake Error at pc/CMakeLists.txt:13 (find_package):
1> [CMake]   Found package configuration file:
1> [CMake] 
1> [CMake]     D:/OpenCV/OpenCVConfig.cmake
1> [CMake] 
1> [CMake]   but it set OpenCV_FOUND to FALSE so package "OpenCV" is considered to be
1> [CMake]   NOT FOUND.```
Repository: thefuck
Issue: sudo.py assumes && for shell 'and' 
Labels: bug,help wanted,fish

The sudo.py rule assumes that '&&' is every shells 'and' operator. This is not the case for fish shell v2.
Repository: excalidraw
Issue: zooming on a shape stops rendering it
Labels: bug

Probably a bug in visibility detection. 

Steps to repro:

1. https://excalidraw.com/#json=5236195592241152,nBFUdjjvd2rZyqpNHBMKUg
2. zoom on the ~center of the rectangle to 1000%
Repository: terminal
Issue: [Windows Terminal FR] Open alternate screen buffer in new tab
Labels: Issue-Feature,Area-UserInterface,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

When an application sets alternate screen buffer mode (e.g. `tput smcup`), Windows Terminal saves and clears everything in the viewport, but still allows you to scroll up and view the _rest_ of the scrollback buffer. This is a problem if you want to view something in recent history while using a full-screen application.

Some terminal emulators prevent you from accessing the scrollback buffer at all in the alternate screen mode, which is more intuitive but even less useful.

A better option might be to separate the two buffers: display the existing scrollback buffer and alternate screen buffer in different windows.

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->


# Proposed technical implementation details (optional)

When a terminal has the alternate screen buffer mode set, it would become split across two tabs: an inactive tab with the full, existing scrollback buffer, and an active tab with _only_ the alternate screen buffer.

When alternate screen buffer is disabled/reset, the first tab would become active again and the second tab would be closed.

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: go
Issue: net/http: clarify that TimeoutHandler buffers all writes into memory
Labels: Documentation,NeedsInvestigation

While reading `http.TimeoutHandler` implementation I noticed that in [current docs](https://github.com/golang/go/blob/29d7e5472be79b77f39d81b697d44038179ba1a1/src/net/http/server.go#L3275) there's no mention that all writes in the response are buffered in memory before being flushed to the client.

Digging a bit in the git history, this was a clarification that was present on the [original implementation](https://github.com/golang/go/commit/0478f7b9d6e9e0461e67716f003f4dbf26bf634d#diff-3fcb677d51a4d6e655f71eb642c7bb3fe8fa44e29ee3748111383c7d6ad3d47bR2106).

The [last change](https://github.com/golang/go/issues/35161) that touched the docs has a good summary of some back and forth in implementing `Flusher`, which docs changes made this original note be lost.

It feels to me that clarifying that all writes are buffered to memory is something worth adding again since that should be considered by users when wrapping handlers that might produce big writes.

The proposed new docs for that paragraph could be:
```
// TimeoutHandler buffers all Handler writes to memory. 
// It supports the Pusher interface but does not support the Hijacker 
// or Flusher interfaces.
```

If that sounds like a good idea, I can create a CL with this change.
Repository: flutter
Issue: FlutterInjector Javadocs
Labels: team,platform-android,engine,d: api docs,P2,team-android,triaged-android

FlutterInjector Javadocs

## Reference

- https://github.com/flutter/flutter/issues/21781
- https://github.com/flutter/flutter/issues/32377#issuecomment-903356803
Repository: vscode
Issue: The kernel selection UI should not appear if only one notebook controller is marked as preferred
Labels: under-discussion,notebook-execution

The following scenario:
1. I create a new Jupyter Notebook in Jupyter Lab and select the Julia 1.6.2 kernel, save the file.
2. I open the same file in VS Code. I only have the Julia extension installed, and the Julia extension registers two notebook controllers with VS Code: one for Julia 1.6.2 and one for Julia 1.5.4.
3. Currently VS Code now prompts me to select a kernel, but I think that UI prompt should not appear in this scenario, instead the Julia 1.6.2 kernel should just be used automatically.

The Julia extension will in the vast majority of cases only mark one of its controllers as preferred in https://github.com/julia-vscode/julia-vscode/blob/0eff0794e2433b4ce6289383d1afef8b43163c69/src/notebook/notebookFeature.ts#L76. I think in general, if only one controller is marked as preferred for a Jupyter notebook file that is opened for the first time in VS Code, then VS Code should just select that controller and not show any UI to the user to make a choice. There are a few situations where the Julia extension will not be able to select just one kernel (for example if a user has both a x64 and a x86 Julia 1.6.2 installed), and in those cases it would be good if the kernel selection UI pops up.

The current behavior is a) quite annoying if one works with a lot of Jupyter notebook files that originate from collaborators that use other clients and b) is also inconsistent with every other Jupyter notebook client that I know. Juptyer Lab, nteract and classical Jupyter notebook _all_ don't prompt users to make manual kernel selections if the kernel that is specified in the notebook file itself exists as a perfect match on the user system. I think VS Code should try to mimic that UI experience.

Another way to think about this: if I have Julia 1.6.2 installed, and I get a notebook file that specifies a Julia 1.6.2 kernel, there is really zero value in me having to then manually pick that kernel, it should just be automatic.
Repository: godot
Issue: [WIP] Multiple PlaneMesh  issues
Labels: enhancement,discussion,topic:core,topic:rendering,documentation

_[Note: This is a Work-In-Progress report covering multiple issues which will eventually hopefully be completed & split into separate issues like it should be.]_

### Godot version

3.3/3.4

### System information

N/A

### Issue description

[TODO: Add context.]

 - [ ] Document (in `PlaneMesh` docs) that `QuadMesh` should be used instead of `PlaneMesh` in 2D with a `MeshInstance2D`.
 - [ ] Document that the `QuadMesh` `material` property is ignored/not used in 2D with a `MeshInstance2D` and that e.g. the `MeshInstance2D`'s `CanvasItem` `Module` property (or `CanvasItem` `Material` property?) should used instead.
 - [ ] Prevent or warn when `PlaneMesh` is used in 2D with a `MeshInstance2D`.
 - [ ] Prevent or warn when `QuadMesh` `material` property is used in 2D with a `MeshInstance2D`.

### Steps to reproduce

[TODO]

### Minimal reproduction project

[TODO]
Repository: rust
Issue: Tracking Issue for Cell::as_array_of_cells
Labels: T-libs-api,C-tracking-issue,A-array

Feature gate: `#![feature(as_array_of_cells)]`

This is a tracking issue for `Cell::as_array_of_cells`, the const-generic counterpart to the existing `Cell::as_slice_of_cells`.

### Public API

```rust
impl<T, const N: usize> Cell<[T; N]> {
    pub const fn as_array_of_cells(&self) -> &[Cell<T>; N] { ... }
}

// Example

let mut array: [i32; 3] = [1, 2, 3];
let cell_array: &Cell<[i32; 3]> = Cell::from_mut(&mut array);
let array_cell: &[Cell<i32>; 3] = cell_array.as_array_of_cells();
```

### Steps / History

- [x] Implementation: https://github.com/rust-lang/rust/pull/87944
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

- None yet.
Repository: neovim
Issue: matchit does not use treesitter, depends on :syntax
Labels: enhancement,plugin,treesitter

### Neovim version (nvim -v)

NVIM v0.6.0-dev+142-g5a111c1b0

### Vim (not Nvim) behaves the same?

no, vim doesn't support nvim-treesitter

### Operating system/version

Microsoft Windows [Version 10.0.19043.1165]

### Terminal name/version

Windows Terminal/1.10.1933.0

### $TERM environment variable

(nothing is in $TERM env)

### Installation

choco install neovim --pre

### How to reproduce the issue

1. Install [nvim-treesitter](https://github.com/nvim-treesitter/nvim-treesitter)
2. Make a viml file: test-vim.vim
3. Type following
```viml
if
	" A comment containing a word if
else
	echo ELSE
endif
```
4. Press % while the cursor is on endif

### Expected behavior

Commented line is ignored for matching if-else-endif with % key.
![GIF 2021-08-22 오후 7-43-05](https://user-images.githubusercontent.com/19642705/130394191-feeb0654-fb68-4ea9-b8a1-bc13ce5272d6.gif)


### Actual behavior

The cursor jumps to the word if in the commented line
![GIF 2021-08-22 오후 7-42-23](https://user-images.githubusercontent.com/19642705/130394073-6c0a3dd8-83c8-4e02-89d0-5ff38ded2131.gif)

Happens with a controlling expression in the if statement as well.
![GIF 2021-08-23 오후 2-19-40](https://user-images.githubusercontent.com/19642705/130394534-d36c9dde-3c35-4ba2-b0d8-d007de0fbc5d.gif)
Repository: flutter
Issue: SkCanvas::Flush execution is too slow 
Labels: framework,engine,c: performance,dependency: skia,perf: speed,has reproducible steps,P2,found in release: 2.2,found in release: 2.6,team-engine,triaged-engine

```
Scaffold(
      body: TabBarView(

        controller: _tabController,
        children: getChildWidgets(),
      ),
      bottomNavigationBar: TabBar(
        controller: _tabController,
        tabs: tabs.map((item) {
          return Container(color: Colors.black,child: Text(item, style: TextStyle(color: Colors.white),),);
        }).toList(),
      ),
    )
```

A very simple test, click on the tab on the bottomNavigationBar to switch the page in TabBarView, but it cannot reach 60FPS from the devTools, and the time-consuming is mainly reflected in the SkCanvas::Flush operation on the Raster thread 。

Can you please tell me how to optimize the speed ？

The attached zip contains a simple test dart file and the json file generated by flutter run --profile --trace-skia.
 
**Target Platform: android**
**Target OS version/browser: android 9**
**Devices: Redmi Note 5**


```
D:\Users\yl4111>flutter doctor
Running "flutter pub get" in flutter_tools...                      17.1s
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.2.3, on Microsoft Windows [Version 10.0.18362.30], locale zh-CN)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Chrome - develop for the web
[√] Android Studio (version 4.1.0)
[√] Connected device (2 available)
```
[skCanva-flush.zip](https://github.com/flutter/flutter/files/7029453/skCanva-flush.zip)
Repository: godot
Issue: Android SDK: Failed to find package Cmake
Labels: platform:android,topic:buildsystem,topic:thirdparty

### Godot version

3.3.3

### System information

Windows 7 32-bit 2GB RAM Intel HD Graphics

### Issue description

I want to install Android SDK without Android Studio, because I can't. But it returns "Warning: Failed to find package "cmake;3.10.2.4988404""

### Steps to reproduce

I have cmdline-tools: C:\Users\adm\Android-SDK\cmdline-tools\latest\bin
I use documentation to download android sdk "sdkmanager --sdk_root=<android_sdk_path> "platform-tools" "build-tools;30.0.3" "platforms;android-29" "cmdline-tools;latest" "cmake;3.10.2.4988404" "ndk;21.4.7075529".

<android_sdk_path> = "C:\Users\adm\Android-SDK"

It returns error "Warning: Failed to find package "cmake;3.10.2.4988404""

### Minimal reproduction project

_No response_
Repository: flutter
Issue: [camera] Add missing unit tests for Android refactor
Labels: a: tests,platform-android,p: camera,package,P2,team-android,triaged-android

This issue is created to track the progress on adding the remaining missing unit tests for the camera plugin, after flutter/plugins#4059 has been merged.

While the test coverage of the camera plugin has been improved with this series of pull requests, a few methods, particularly in the Camera class itself still remain untested. (More information on why these are still missing can be found [here](https://github.com/flutter/plugins/pull/4059#issuecomment-902735609)).

As of right now, specifically the following methods of the `Camera` class are still lacking tests:

- `open`
- `takePicture` 
- `startVideoRecording`
- `stopVideoRecording`
- `setFocusMode`
- `startPreview`
- `startPreviewWithimageStream`
Repository: godot
Issue: `gdscript_tokenizer` error when opening `ScriptEditor` context menu using `Menu` key
Labels: bug,topic:gdscript,topic:editor

### Godot version

3.3, 3.2.3

### System information

Windows

### Issue description

I can see this error
`modules/gdscript/gdscript_tokenizer.cpp:1129 - Condition "tk_rb[ofs].type != TK_IDENTIFIER" is true. Returned: StringName()`
when I press Menu key (KEY_MENU) and if the caret is on certain places.

### Steps to reproduce

1. create a script (3 lines):
```gdscript
func _ready():
	pass
	print()
```
2. move the caret (using the mouse!) here:
```gdscript
func _ready():
	pass
|	print()
```
(that is at 3:1)

3. Press `menu` key on the keyboard.
The error should appear  in the `Output`.

it seems the error doesn't appear:
- if you write `pass` instead of `print()`
```gdscript
func _ready():
	pass
	pass
```
- if you move the caret at any other place.
- if you use arrow keys to move the caret (left/right keys on the keyboard) 

### Minimal reproduction project

_No response_