Terraform Version

Terraform v1.2.2
on linux_amd64
+ provider registry.terraform.io/hashicorp/aws v4.18.0
+ provider registry.terraform.io/hashicorp/random v3.3.1
+ provider registry.terraform.io/mongey/kafka v0.5.1
+ provider registry.terraform.io/scottwinkler/shell v1.7.10

Git version

git version 2.25.4

Terraform Configuration Files

1. This works, b

What happened?

I click next button after maximizing the image, it switches to the first image instead of next right image.

Reproduce the Bug

1. Insert multiple images
2. View the second image in maximize mode
3. Press next or previous button to switch image

Expected Behavior

No response

Screenshots

![Jun-28-2022 22-32-27](https://user-images.githubusercontent.com

Description

The y-axis ticks supports the rotated option, but the doc is missing.

I haven't checked whether other options are missing.

缘由 Cause

G6 现在已经正式迈入了4.0+时代，我们很欣慰的看到有越来越多的人使用G6，承蒙各位厚爱，G6目前也在越来越多的场景被使用。与此同时，G6原来的图表案例就相形见绌了，还停留在一个比较基本的案例阶段，他只是展示了一些基本的原子功能案例。所以在这里，我们向社区的各位发出请求，为了让对G6的使用方案有更好的沉淀，希望大家提供自己实际的使用案例，我们将会修改为G6官网的案例，并且附上你的署名，让你的案例在G6官网可以帮助更多的人。

G6 has now officially entered the 4.0+ era and we are pleased to see that more and more people are using G6, and thanks to your love, G6 is now being used in more and

context: https://discuss.nebula-graph.com.cn/t/topic/6991

it's becoming more time-consuming and error-prone to manually re-test all the demos following internal refactorings and API adjustments.

now that the API is fleshed out a bit, it's possible to test a large amount of code (non-granularly) without having to simulate all interactions via Puppeteer or similar.

a lot of code can already be regression-tested by simply running all the demos and val

.rickshaw_graph .detail .item.active from detail.css would benefit by adding 'width: auto; height:auto;' to auto-size the detail tooltip on graph mouse hover. In it's current form, the tooltip doesn't get auto-sized when using a relative/percentage based layout.

See:
gonum/gonum#845 (comment)

steps to reproduce

Write a loop, from 1 to 80000, each time add a random int to the max heap.

In theory it takes very little time(NlogN, N=80000, <1sec ), but the program does take a long time.

I'v also tested the BinaryHeap in https://github.com/SolutionsDesign/Algorithmia, it performs well, so it is probably due to the bad algorithm.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce

1. Work computer works fine loading .gml
2. Home PC gets angry
3. Java is updated

Context