sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Option to enable key frame diamonds in Animation Editor
Labels: enhancement,topic:editor,usability,topic:animation

I love the new changes/updates in the Animation Editor. Except just one little quirk that makes it hard for me is the overlay images on keyframes

For example:

![image](https://user-images.githubusercontent.com/43447253/48674429-ea67d200-eb00-11e8-8680-d26105fb1fd2.png)


It makes it really hard/confusing to read the timeline when you go back to edit, because you don't really know where the keyframes are. Either you have to zoom in quite a bit, or click on the keyframe image overlay to see the edges. The left side of the rectangular image overlay is where the actual keyframe is at.

  It was much more easier (IMO) to see them with the little diamonds instead. My  suggestion is just if that could be an option. Maybe under Editor Settings -> Editors -> Animation
Repository: angular
Issue: fakeAsync does not fail with pending microtasks
Labels: type: bug/fix,area: testing,freq2: medium,P3,docsarea: testing,area: docs

<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅

Oh hi there! 😄

To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.

🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->

# 📚 Docs or angular.io bug report

### Description

The testing guide states that `flushMicrotasks` should be used when pending microtasks are expected at the end of a test to prevent an error from being thrown. What `fakeAsync` [actualy does](https://github.com/angular/angular/blob/4c2ce4e8ba4c5ac5ce8754d67bc6603eaad4564a/packages/core/testing/src/fake_async_fallback.ts#L78), is call `flushMicrotasks` after calling the test and only checks for pending timers.

## 🔬 Minimal Reproduction

### What's the affected URL?**

https://angular.io/guide/testing#testing-utility-apis

### Reproduction Steps**
<!-- If applicable please list the steps to take to reproduce the issue -->
<!-- ✍️edit:-->

### Expected vs Actual Behavior**
<!-- If applicable please describe the difference between the expected and actual behavior after following the repro steps. -->
<!-- ✍️edit:-->


## 📷Screenshot
<!-- Often a screenshot can help to capture the issue better than a long description. -->
<!-- ✍️upload a screenshot:-->


## 🔥 Exception or Error
<pre><code>
<!-- If the issue is accompanied by an exception or an error, please share it below: -->
<!-- ✍️-->

</code></pre>


## 🌍  Your Environment

### Browser info
<!-- ✍️Is this a browser specific issue? If so, please specify the device, browser, and version. -->

### Anything else relevant?
<!-- ✍️Please provide additional info if necessary. -->
Repository: go
Issue: cmd/go/internal/modfetch: TestCodeRepo failures due to external repo changes
Labels: Testing,NeedsFix,GoCommand

```
$ gotip version
go version devel +fe562cebf1 Sun Nov 18 16:13:13 2018 +0000 linux/amd64
```

To reproduce:

```
$ cd src/cmd/go/internal/modfetch

$ gotip test -run=TestCodeRepo
--- FAIL: TestCodeRepo (58.16s)
    --- FAIL: TestCodeRepo/gopkg.in_yaml.v2/v2 (3.32s)
        coderepo_test.go:368: info.Version = "v2.2.2-0.20181115110504-51d6538a90f8", want "v2.2.1"
        coderepo_test.go:371: info.Name = "51d6538a90f86fe93ac480b35f37b2be17fef232", want "5420a8b6744d3b0345ab293f6fcba19c978f1183"
        coderepo_test.go:374: info.Short = "51d6538a90f8", want "5420a8b6744d"
        coderepo_test.go:377: info.Time = 2018-11-15 11:05:04 +0000 UTC, want 2018-03-28 19:50:20 +0000 UTC
FAIL
exit status 1
FAIL	cmd/go/internal/modfetch	60.812s
```

[Spotted on the longtest builder](https://build.golang.org/log/27113d3c49cc2b99a1b440d14504d4831f30c999).
Repository: vscode
Issue: Indent/Outdent with tab key does not honor editor.autoIndent=false
Labels: typescript,javascript,editor-autoindent,under-discussion,on-unit-test

Issue Type: <b>Bug</b>

When I have:

        /*
         * Comment
         */

If I select it and hit tab, I get:

            /*
            * Comment
            */

If instead I had hit shift-tab, I get:

    /*
        * Comment
        */

Same happens with `Ctrl-]` and `Ctrl-[` *(if those are supposed to make a difference)*

I hoped turning off autoIndent would stop this, but no dice.  I also turned off C++ formatting in the JSON config:

    {
        "editor.autoIndent": false,
        "editor.detectIndentation": false,
        "C_Cpp.formatting": "Disabled"
    }

I have done due diligence by asking (and bountying, +100) a question on StackOverflow to get an answer on what to do about this, but no one seems to know:

https://stackoverflow.com/q/53326134/preserve-spacing-on-indent-or-outdent-with-tab-in-vscode

If someone can provide a resolution here, be sure to go there and get the bounty points.

VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.17134

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)|
|GPU Status|2d_canvas: enabled<br>checker_imaging: disabled_off<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: disabled_software<br>rasterization: enabled<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Memory (System)|15.86GB (1.40GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

</details><details><summary>Extensions (3)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-github|Kni|0.30.0
python|ms-|2018.10.1
cpptools|ms-|0.20.1


</details>
<!-- generated by issue reporter -->
Repository: flutter
Issue: Support running on ChromeOS emulator (Pixelbook_beta_API_25)
Labels: tool,platform-chromebook,P2,team-tool,triaged-tool

I am hoping  the team could consider supporting the new Chrome OS emulator ?

My app is on the Android and IOS play store and i want to get it tested for Chrome OS.
I can launch the ChromeOS emulator, but Flutter refuses to see that its running.

**My Log:**
````
flutter emulators --launch Pixelbook_beta_API_25
cd ./example && flutter run

flutter emulators --launch Pixelbook_beta_API_25
cd /Users/apple/workspace/go/src/github.com/zino-app/graphql-flutter/example && flutter run
No connected devices.

Run 'flutter emulators' to list and start any available device emulators.

If you expected your device to be detected, please run "flutter doctor" to diagnose
potential issues, or visit https://flutter.io/setup/ for troubleshooting tips.
make: *** [ex-chromeos-run] Error 1


````


**My Env:**
````
x-MacBook-Pro:~ apple$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v0.11.6, on Mac OS X 10.14.1 18B75, locale en-DE)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
[✓] Android Studio (version 3.2)
[✓] VS Code (version 1.29.1)
[!] Connected device


x-MacBook-Pro:~ apple$ flutter emulators
3 available emulators:

Pixel_2_API_28        • pixel_2          • Google • Pixel 2 API 28
Pixelbook_beta_API_25 • Pixelbook (beta) • Google • Pixelbook (beta) API 25
apple_ios_simulator   • iOS Simulator    • Apple

````

**To Reproduce:**

1. Install the emulator in Android Studio.
https://developer.android.com/topic/arc/emulator

2. Make a simple Flutter example

3. Fire it up as per my Log:
Repository: TypeScript
Issue: chained generic mixins fail
Labels: Suggestion,In Discussion

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.2.0-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** chained generic mixins

**Code**

```ts
type Constructor<T> = new(...args: any[]) => T;

interface XInterface {
    value: string;
 }

function make<T extends Constructor<any>>(Base: T) {
    return class extends Base implements XInterface {
        value = "Hello!"
    }
}

// Great. Works.
class _X1 extends make(Function) { hello() { this.value; }}

type _T1 = Constructor<HTMLElement>;

// Oops. But changing `make(Base)`, to `make(Base as _T1)` works perfectly, 
// which makes no sense.
function make2<T extends _T1>(Base: T) {
    return class extends make(Base) { }
}

```

**Expected behavior:** 
Compile.

**Actual behavior:**
Type '{ new (...args: any[]): make<T>.(Anonymous class); prototype: make<any>.(Anonymous class); } & T' is not a constructor function type.
Repository: rust
Issue: Enable strict HANDLE checking for all Windows Rust programs
Labels: A-runtime,O-windows,C-enhancement,A-security,T-libs-api

To help protect against bugs in unsafe or third-party code, the Rust compiler should emit code to enable strict `HANDLE` checking for all Windows Rust programs. The process will receive a fatal error if it manipulates a `HANDLE` that is not valid, such as using an uninitialized `HANDLE` or calling `CloseHandle` twice.

See MSDN for `SetProcessMitigationPolicy` and `PROCESS_MITIGATION_STRICT_HANDLE_CHECK_POLICY`:

https://docs.microsoft.com/en-us/windows/desktop/api/processthreadsapi/nf-processthreadsapi-setprocessmitigationpolicy

Strict `HANDLE` checking might cause compatibility problems for Rust programs that depends on third-party libraries that misuse `HANDLE`s. As a general rule, strict `HANDLE` checking cannot be turned off once it is turned on, so there would be no backdoor to allow sloppy third-party code to run without raising a `HANDLE` exception. If that compatibility constraint is too severe, strict `HANDLE` checking could be limited to debug builds or disabled with an opt-out compiler flag.

Here is how Firefox enables strict `HANDLE` checking for its sandbox processes:

https://searchfox.org/mozilla-central/rev/5117a4c4e29fcf80a627fecf899a62f117368abf/security/sandbox/chromium/sandbox/win/src/process_mitigations.cc#120-131
Repository: rust
Issue: Restrict Windows DLL search path as a precaution against DLL pre-loading attacks
Labels: O-windows,C-enhancement,A-security

Windows' standard DLL search path contains directories that can be vulnerable to DLL pre-loading attacks. An application can use the `SetDefaultDllDirectories` API to specify a default DLL search path for the process that eliminates the most vulnerable directories and limits the other directories that are searched.

For example, as a precaution, Firefox removes the current directory from the DLL search path and then restricts the DLL search path to the application's installation directory, the Windows system directory, and any paths explicitly added using the `AddDllDirectory` or `SetDllDirectory` APIs.

https://searchfox.org/mozilla-central/rev/5117a4c4e29fcf80a627fecf899a62f117368abf/toolkit/mozapps/update/updater/loaddlls.cpp#15-30

https://searchfox.org/mozilla-central/rev/5117a4c4e29fcf80a627fecf899a62f117368abf/security/sandbox/chromium/sandbox/win/src/process_mitigations.cc#46-58

To help protect against DLL pre-loading attacks, the Rust compiler could emit similar code to restrict its DLL search path for all Windows Rust programs. Changing the DLL search path could cause compatibility problems for Windows Rust programs that assume they can implicitly load DLLs in the current directory without explicitly configuring their DLL search path. The workaround is for those programs to configure their DLL search path using the the `AddDllDirectory` or `SetDllDirectory` APIs.

See MSDN for `SetDefaultDllDirectories`:

https://docs.microsoft.com/en-us/windows/desktop/api/libloaderapi/nf-libloaderapi-setdefaultdlldirectories
Repository: vscode
Issue: Git - Staging when ignoring whitespace, doesn't stage changed whitespace
Labels: bug,git

Issue Type: <b>Bug</b>

1. Indent several lines of code, and save. These should appear as changes in Git.
2. Click on "Open changes".
3. Ensure whitespace changes are hidden (which is the default).
4. Select the indented lines, and stage them with "Stage selected ranges".
5. Nothing is staged. Even though whitespace is hidden, shouldn't changes like indentation be staged, if they're within the selected range? Otherwise I end up with lines like `if (true)` staged, since it's a text change, but the block contained within its braces as not staged, since it's just an indentation change.

VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:06:21.742Z)
OS version: Darwin x64 18.0.0


<!-- generated by issue reporter -->
Repository: rust
Issue: Missing optimization with signed pointer offset
Labels: A-LLVM,I-slow,T-compiler

I am trying to elide the pointer offset of a slice indexing operation. 

I tried this code:

```rust
pub fn index(table: &[u128; 4], idx: i32) -> u128 {
    table[(idx as usize & 0b11_0000) >> 4]
}
```
with `RUST_BACKTRACE=full RUSTFLAGS='--emit=asm' cargo build --release`.

I expected to see this happen: 
```asm
example::index:
  and esi, 48
  mov rax, qword ptr [rsi + rdi]
  mov rdx, qword ptr [rsi + rdi + 8]
  ret
```
(selects two bits, already in the pointer offset position)

Instead, this happened: 
```asm
example::index:
  shr esi, 4
  and esi, 3
  shl rsi, 4
  mov rax, qword ptr [rdi + rsi]
  mov rdx, qword ptr [rdi + rsi + 8]
  ret
```

A godbolt link for comparison with an unsafe version which does apply the optimization: https://godbolt.org/z/0QsA3z

## Meta

```bash
rustc --version --verbose
rustc 1.32.0-nightly (6b9b97bd9 2018-11-15)
binary: rustc
commit-hash: 6b9b97bd9b704f85f0184f7a213cc4d62bd9654c
commit-date: 2018-11-15
host: x86_64-apple-darwin
release: 1.32.0-nightly
LLVM version: 8.0
```

Backtrace:
none
Repository: rust
Issue: Run proc macro invocations in separate threads.
Labels: C-enhancement,I-compiletime,A-macros,T-compiler

#49219 introduces `proc_macro::bridge::server::{ExecutionStrategy,SameThread,CrossThread}`.
`SameThread` had to be used because `CrossThread` was a significant performance regression.

Ideally, we'd use `CrossThread`, which spawns a thread for each invocation, to prevent (and discourage) proc macros from using TLS for state between invocations.

But we'd have to figure out how to make it not regress performance too much, if at all possible.
(it could be the use of channels, which are overkill since they never have more than one value)

cc @dtolnay @alexcrichton @petrochenkov 

<hr/>

(**TODO**: update with regressions, if any, after the cross-thread crater run finishes on #49219)
Repository: opencv
Issue: ‘memcpy’ was not declared in this scope (Ubuntu 16.04, opencv2.4.13)
Labels: bug,priority: low,category: build/install,affected: 2.4,category: gpu/cuda (contrib)

I'm trying to install opencv2.4.13 for Ubuntu 16.04 but get a bug like this when running `make` command

```
[  1%] Built target opencv_core_pch_dephelp
[  1%] Built target pch_Generate_opencv_core
[  2%] Building NVCC (Device) object modules/core/CMakeFiles/cuda_compile.dir/__/dynamicuda/src/cuda/cuda_compile_generated_matrix_operations.cu.o
/usr/include/string.h: In function ‘void* __mempcpy_inline(void*, const void*, size_t)’:
/usr/include/string.h:652:42: error: ‘memcpy’ was not declared in this scope
   return (char *) memcpy (__dest, __src, __n) + __n;
                                          ^
CMake Error at cuda_compile_generated_matrix_operations.cu.o.cmake:266 (message):
  Error generating file
  /home/savvycom/opencv-2.4.13.6/release/modules/core/CMakeFiles/cuda_compile.dir/__/dynamicuda/src/cuda/./cuda_compile_generated_matrix_operations.cu.o


modules/core/CMakeFiles/opencv_core.dir/build.make:198: recipe for target 'modules/core/CMakeFiles/cuda_compile.dir/__/dynamicuda/src/cuda/cuda_compile_generated_matrix_operations.cu.o' failed
make[2]: *** [modules/core/CMakeFiles/cuda_compile.dir/__/dynamicuda/src/cuda/cuda_compile_generated_matrix_operations.cu.o] Error 1
CMakeFiles/Makefile2:890: recipe for target 'modules/core/CMakeFiles/opencv_core.dir/all' failed
make[1]: *** [modules/core/CMakeFiles/opencv_core.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2

```

My cmake configuration is:

```
cmake \
-D CMAKE_BUILD_TYPE=Release \
-D CMAKE_INSTALL_PREFIX=/usr/local \
-D CUDA_GENERATION=Kepler \
-D BUILD_LIBPROTOBUF_FROM_SOURCES=ON \
-D INSTALL_PYTHON_EXAMPLES=ON \
-D INSTALL_C_EXAMPLES=OFF \
-D PYTHON2_EXECUTABLE=/usr/bin/python2.7 \
-D PYTHON_INCLUDE_DIR=/usr/include/python2.7 \
-D PYTHON_INCLUDE_DIR2=/usr/include/x86_64-linux-gnu/python2.7 \
-D PYTHON_LIBRARY=/usr/lib/x86_64-linux-gnu/libpython2.7.so \
-D PYTHON2_NUMPY_INCLUDE_DIRS=/usr/lib/python2.7/dist-packages/numpy/core/include/ \
-D BUILD_EXAMPLES=ON ..
```
I've tried the solution found here [https://github.com/opencv/opencv/issues/6500#issuecomment-221762139](url) but it doesn't work

Can anyone help me please ?
Repository: kubernetes
Issue: Ability to adjust number of inodes of filesystems
Labels: sig/storage,kind/feature,lifecycle/frozen

<!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:

I want to add a feature to adjust number of inodes (or customized mkfs options) for block PVs.

**Why is this needed**:

Sometimes, people need to store a large number of small files (typically, images for data mining), the default calculation of number of inodes in ext3/ext4 may be too small.

For ext3/ext4 filesystems, they allocate inodes at creation:

- `-i bytes-per-inode`: Specify the bytes/inode ratio.
- `-I inode-size`: Specify the size of each inode in bytes.
- `-N number-of-nodes`: Overrides the default  calculation  of  the number of inodes that should be reserved for the filesystem (which is based on the number of blocks and the bytes-per-inode ratio)

For other filesystems, e.g. `btrfs` has dynamic inode allocation and `xfs` has a space limit (percent of filesystem), this is filesystem-specific.

Workaround solution:

- Use other filesystems if possible, e.g. btrfs/xfs.

<!-- DO NOT EDIT BELOW THIS LINE -->
/kind feature
Repository: go
Issue: cmd/compile: fuse constant comparison with division by a constant
Labels: Performance,compiler/runtime

	func ssa(a uint32) uint32 {
		if a / 60 > 45 {
			return a
		} else {
			return a - 1
		}
	}

is compiled to

	       	00000 (4)	TEXT	"".ssa(SB)
	       	00001 (4)	FUNCDATA	$0, gclocals·33cdeccccebe80329f1fdbee7f5874cb(SB)
	       	00002 (4)	FUNCDATA	$1, gclocals·33cdeccccebe80329f1fdbee7f5874cb(SB)
	       	00003 (4)	FUNCDATA	$3, gclocals·33cdeccccebe80329f1fdbee7f5874cb(SB)
	 v7    	00004 (5)	PCDATA	$2, $0
	 v7    	00005 (5)	PCDATA	$0, $0
	 v7    	00006 (5)	MOVL	$2290649225, AX
	 v12   	00007 (5)	MOVL	"".a(SP), CX
	 v16   	00008 (5)	IMULQ	CX, AX
	 v13   	00009 (5)	SHRQ	$37, AX
	 v8    	00010 (5)	CMPL	AX, $45
	 b1    	00011 (5)	JLS	14
	 v15   	00012 (6)	MOVL	CX, "".~r1+8(SP)
	 b2    	00013 (6)	RET
	 v18   	00014 (8)	LEAL	-1(CX), AX
	 v21   	00015 (8)	MOVL	AX, "".~r1+8(SP)
	 b4    	00016 (8)	RET
	       	00017 (?)	END

maybe better should equal to something like

	func ssa(a uint32) uint32 {
		if a > 2700 {
			return a
		} else {
			return a - 1
		}
	}
Repository: pytorch
Issue: [Caffe2] Non-spatial batchnorm optimization
Labels: caffe2

## 🚀 Feature
To track the task
Repository: rust
Issue: Tracking issue for feature(repr128); enums with 128-bit discriminants
Labels: A-LLVM,B-RFC-approved,T-lang,C-tracking-issue,I-lang-nominated,S-tracking-unimplemented

This issue tracks `repr128`,  i.e. "enums with 128-bit discriminant" as per https://github.com/rust-lang/rfcs/pull/1504.
Originally this was tracked in https://github.com/rust-lang/rust/issues/35118.

-------------

> Nothing has changed re repr128… It is still the case that at least LLVM’s debuginfo API blocks us from implementing it at all. There’s very little incentive to work on it, though, and I’m not planning to do anything in that direction until a very convincing use-case for 128-bit enum discriminants comes up.

\- @nagisa
Repository: go
Issue: fmt: behavior of pointer-like format arguments is undocumented
Labels: Documentation,NeedsInvestigation

Funcs and channels have one thing in common - they're all pointers underneath. This means one can use `%p` to print them, much like actual pointers.

It's documented that `%b, %d, %o, %x and %X verbs also work with pointers`, so those can also be used for both funcs and channels too.

But nowhere is it documented that channels and functions are treated as pointers when formatting. The closest thing is this piece:

```
The default format for %v is:
[...]
chan:                    %p
```

I think we should extend the documentation to clarify a number of things:

* Funcs and channels are printed exactly like pointers
* The default format for `%v` of a function is also `%p`
* Maps are printed like pointers **only** with `%p`

That last point is especially tricky. For example, `fmt.Printf("%p", map[bool]bool{true: false}` will correctly print an address, but the same with `%b` or `%d` will fail as `fmt` recurses into the key and value elements, which aren't numbers.

I encountered this while fixing some bugs in vet, and I was surprised by how lightly `fmt` documents all this. A few of the behaviors surprised me too. I'll send a docs CL draft soon.

/cc @robpike @alandonovan @martisch
Repository: go
Issue: x/net/http/httproxy: Never uses proxy for localhost
Labels: NeedsInvestigation

`golang.org/x/net/http/httproxy` has a [hardcoded rule](https://github.com/golang/net/blob/adae6a3d119ae4890b46832a2e88a95adc62b8e7/http/httpproxy/proxy.go#L183) whereby requests to `localhost` never use a proxy.

This may be a sensible default, but there should be a way to override it. There is no intrinsic reason why a proxy cannot or should not be used for `localhost`. My use case is that I have mocks of remote HTTP services running on `localhost`, and I want to use [mitmproxy](https://mitmproxy.org/) to debug the Go program’s traffic to/from these services.

One solution might be to use the current default **unless** there’s a non-empty `NO_PROXY`/`NoProxy` environment variable: then I could use some dummy value like `NO_PROXY=foo.invalid`. But a 100% backwards-compatible solution would require some hack along the lines of `NO_PROXY=but_actually_localhost_ok` or `HTTP_PROXY_LOCALHOST=yes`.
Repository: rust
Issue: rustdoc "expand all docs" button does not expand "hidden undocumented items"
Labels: T-rustdoc

In nightly rustdoc, trait items that aren't overridden are collapsed as "hidden undocumented items." (This is slightly inaccurate, since they may have documentation from the trait declaration.) Clicking the `[+]` ("expand all docs") link at the top of the page expands all docs except for these.  This means there is no longer any way to actually expand *all* documentation.

My use case for this is using the browser's "find in page" feature to search for method names, or to answer questions like "does this type have any methods that take `&mut self`?"