Google Git
Sign in
skia / buildbot / refs/heads/main
commit5efd24c25423e2b1a09a7db1c0905032f6a9293c[log] [tgz]
authorEduardo Yap <eduardoyap@google.com>Fri Feb 06 21:37:34 2026 +0000
committerSkCQ <skcq-be@skia-corp.google.com.iam.gserviceaccount.com>Fri Feb 06 14:40:47 2026 -0800
tree5a9feeb2f7d79c860b4e74d942673eb79d86aea0
parente1cac57ff296d47de28f996f50873a8b17a5d3eb [diff]
[perf] Implement hover debouncing in explore-simple-sk

- Added a 100ms debounce to the onChartOver event in ExploreSimpleSk to prevent excessive network requests and UI "cycling" during rapid mouse movements.
- Introduced HOVER_DEBOUNCE_MS constant for configurable delay duration.
- Modified onChartMouseDown and onChartMouseOut to clear pending hover timeouts, ensuring data fetching stops if the user clicks or leaves the graph.
- Added comprehensive unit tests for hover debouncing, including rapid hover, cancellation on exit/click, and skip-if-selected scenarios.

Bug: b/480022088
Change-Id: I71cd013be3664e360ff715aee298d935e7fa4716
Reviewed-on: https://skia-review.googlesource.com/c/buildbot/+/1159958
Reviewed-by: John Chen <zhanliang@google.com>
Commit-Queue: Eduardo Yap <eduardoyap@google.com>
2 files changed
tree: 5a9feeb2f7d79c860b4e74d942673eb79d86aea0
  1. am/
  2. android_ingest/
  3. android_stats/
  4. api/
  5. attest/
  6. autoroll/
  7. bash/
  8. bazel/
  9. blamer/
  10. bugs-central/
  11. cabe/
  12. cbb/
  13. cd/
  14. cdn/
  15. cherrypick-watcher/
  16. cmd/
  17. codereview-watcher/
  18. codesize/
  19. comments/
  20. cq_watcher/
  21. ct/
  22. datahopper/
  23. debugger-app/
  24. demos/
  25. docker/
  26. docs/
  27. docsyserver/
  28. ds/
  29. elements-sk/
  30. external/
  31. fiddlek/
  32. firestore/
  33. get_service_account/
  34. gitsync/
  35. go/
  36. gold-client/
  37. golden/
  38. helloworld/
  39. infra/
  40. infra-sk/
  41. jsdoc/
  42. jsfiddle/
  43. k8s-checker/
  44. k8s-deployer/
  45. kube/
  46. leasing/
  47. licenses/
  48. machine/
  49. make/
  50. mcp/
  51. modules/
  52. named-fiddles/
  53. new_element/
  54. npm-audit-mirror/
  55. perdiff/
  56. perf/
  57. periodic-trigger/
  58. pinpoint/
  59. proberk/
  60. promk/
  61. puppeteer-tests/
  62. rag/
  63. sa-keys-checker/
  64. scrap/
  65. scripts/
  66. shaders/
  67. sk/
  68. skbug/
  69. skcq/
  70. skfe/
  71. skolo/
  72. skottie/
  73. static_server/
  74. status/
  75. task_driver/
  76. task_scheduler/
  77. temporal/
  78. test-service/
  79. tool/
  80. tools/
  81. tree_status/
  82. trybot_updater/
  83. .bazelignore
  84. .bazelrc
  85. .bazelversion
  86. .eslintrc.js
  87. .gitattributes
  88. .gitignore
  89. .mockery.yaml
  90. .npmrc
  91. .prettierignore
  92. .prettierrc.json
  93. .puppeteerrc.js
  94. .pylintrc
  95. .vpython
  96. BAZEL_CHEATSHEET.md
  97. BUILD.bazel
  98. build_infra_prod.sh
  99. CDB.md
  100. cipd.ensure
  101. codereview.settings
  102. DATASTORE.md
  103. demopage.sh
  104. DEPS
  105. elements.d.ts
  106. go.mod
  107. go.sum
  108. karmatest.sh
  109. launch.md
  110. LICENSE
  111. LINT.md
  112. Makefile
  113. MODULE.bazel
  114. MODULE.bazel.lock
  115. OWNERS
  116. package-lock.json
  117. package.json
  118. pnpm-lock.yaml
  119. PRESUBMIT.py
  120. PRIVACY_POLICY.md
  121. puppeteerrc.bzl
  122. puppeteerrc.js.tpl
  123. README.md
  124. requirements.txt
  125. run_lint.sh
  126. STYLEGUIDE.md
  127. tools.go
  128. tsconfig.json
  129. whitespace.txt
README.md

Skia-Buildbot Repository

This repo contains infrastructure code for Skia.

Supported Infrastucture Platforms

The infrastructure code is generally built to run on x86 linux. Running on other platforms may be possible but is not officially supported and success will vary depending on the command.

Getting the Source Code

The main source code repository is a Git repository hosted at https://skia.googlesource.com/buildbot.git. It is possible to check out this repository directly with git clone or via go get.

Using git clone allows you to work in whatever directory you want. You will still need to set GOPATH in order to build some apps (recommended to put this in a cache dir). E.g.:

$ cd ${WORKDIR}
$ git clone https://skia.googlesource.com/buildbot.git
$ export GOPATH=${HOME}/.cache/gopath/$(basename ${WORKDIR})
$ mkdir $GOPATH
$ cd buildbot

Install dependencies

Almost all applications are built with Bazel, and bazelisk is the recommended tool to ensure you have the right version of bazel installed:

go install github.com/bazelbuild/bazelisk@latest
go install github.com/bazelbuild/buildtools/buildifier@latest
go install github.com/kisielk/errcheck@latest
go install golang.org/x/tools/cmd/goimports@latest
go install github.com/mikefarah/yq/v4@latest
go install go.chromium.org/luci/client/cmd/...@latest

Add bazelisk to path

export PATH=$PATH:$(go env GOPATH)/bin

Install Node.js and npm

You will need Node.js and npm installed to run web infrastructure tests and linters. We recommend using nvm to manage Node versions.

After installing Node.js, run the following command to install repository dependencies (including linter tools):

npm install

Install other dependencies:

sudo apt-get install jq

Build ~everything

bazelisk build --config=mayberemote //...

Test everything

Set up environ variables

This step might be an optional step, but some test requires these enviornment variables.

Runs

./scripts/run_emulators/run_emulators start

The following are example of environment variables.

Emulators started. Set environment variables as follows:
export DATASTORE_EMULATOR_HOST=localhost:8891
export BIGTABLE_EMULATOR_HOST=localhost:8892
export PUBSUB_EMULATOR_HOST=localhost:8893
export FIRESTORE_EMULATOR_HOST=localhost:8894
export COCKROACHDB_EMULATOR_HOST=localhost:8895

And stores these environment variables to ~/.bashrc file.

Execute tests

bazelisk test --config=mayberemote //...

Generated Code

To update generated code run the following in any directory:

go generate ./...

Running unit tests

Install Cloud SDK.

Use this command to run the presubmit tests:

./run_unittests --small