cmd/worker: Use db.LatestIndexTimestamp for internal poller rather than time horizon.

This is my mistake, sorry. In
https://go-review.googlesource.com/c/pkgsite/+/747880 I added the
internal poller with a horizon option, thinking that that was the
simplest way to do this. But, the problem with the horizon is that the
"cursor" doesn't advance properly. It advances with time, not with
whatever we indexed last.

If we last indexed T1, and the worker dies, we'd like to resume from T1.
Instead, with the horizon, we resume from whatever `Tx=now()-horizon`
might be. That's different than how /poll works: it uses
db.LatestIndexTimestamp. So, it'd have resumed from T1, since that was
where we last indexed. This change basically just makes the internal
poller do the same thing as the /poll endpoint in that regard.

Change-Id: I3232f1684d29ffc0c3bd5104fcdb8562899a2b93
Reviewed-on: https://go-review.googlesource.com/c/pkgsite/+/803720
Auto-Submit: Jonathan Amsterdam <jba@google.com>
Auto-Submit: Ethan Lee <ethanalee@google.com>
Reviewed-by: Jonathan Amsterdam <jba@google.com>
kokoro-CI: kokoro <noreply+kokoro@google.com>
Reviewed-by: Ethan Lee <ethanalee@google.com>
Commit-Queue: Jonathan Amsterdam <jba@google.com>
LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
1 file changed
tree: 82b84c6f412aaf8f415acae45e87c4fd772b7907
  1. cmd/
  2. deploy/
  3. devtools/
  4. doc/
  5. internal/
  6. migrations/
  7. static/
  8. tests/
  9. third_party/
  10. .dockerignore
  11. .gitignore
  12. .prettierignore
  13. .prettierrc.yaml
  14. .stylelintignore
  15. .stylelintrc.yaml
  16. all.bash
  17. codereview.cfg
  18. CONTRIBUTING.md
  19. db-schema.sql
  20. eslint.config.js
  21. go.mod
  22. go.sum
  23. jest.config.js
  24. LICENSE
  25. package-lock.json
  26. package.json
  27. PATENTS
  28. README.md
  29. tsconfig.json
README.md

golang.org/x/pkgsite

This repository hosts the source code of the pkg.go.dev website, and pkgsite, a documentation server program.

Go Reference

pkg.go.dev: a site for discovering Go packages

Pkg.go.dev is a website for discovering and evaluating Go packages and modules.

You can check it out at https://pkg.go.dev.

pkgsite: a documentation server

pkgsite program extracts and generates documentation for Go projects.

Example usage:

$ go install golang.org/x/pkgsite/cmd/pkgsite@latest
$ cd myproject
$ pkgsite -open .

For more information, see the pkgsite documentation.

API

pkgsite provides a REST API for retrieving package and module information. Currently the API is on v1beta, but after a periodic of community feedback we will transition to v1. The API endpoints include:

  • /v1beta/package/{path}: Information about the package at {path}.
  • /v1beta/module/{path}: Information about the module at {path}.
  • /v1beta/versions/{path}: Versions of the module at {path}.
  • /v1beta/packages/{path}: Information about packages of the module at {path}.
  • /v1beta/search: Search results.
  • /v1beta/symbols/{path}: List of symbols for the package at {path}.
  • /v1beta/imported-by/{path}: Paths of packages importing the package at {path}.
  • /v1beta/vulns/{path}: Vulnerabilities of the module at {path}.

For detailed documentation of parameters and response schemas, see the documentation page served at /api, or refer directly to the annotated source code in internal/api/api.go.

Issues

If you want to report a bug or have a feature suggestion, please first check the known issues to see if your issue is already being discussed. If an issue does not already exist, feel free to file an issue.

For answers to frequently asked questions, see pkg.go.dev/about.

You can also chat with us on the #pkgsite Slack channel on the Gophers Slack.

Contributing

We would love your help!

Our canonical Git repository is located at go.googlesource.com/pkgsite. There is a mirror of the repository at github.com/golang/pkgsite.

To contribute, please read our contributing guide.

License

Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file.

Links