Google Git
Sign in
chromium / infra / luci / luci-go / 61327aa8734ad5f3d4adbe10ef1fea3193ad4c4f
commit61327aa8734ad5f3d4adbe10ef1fea3193ad4c4f[log] [tgz]
authorVadim Shtayura <vadimsh@chromium.org>Mon Mar 17 18:09:09 2025
committerLUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Mar 17 18:09:09 2025
tree1a34d890bd57d7b47e0664b3069933089ad97d03
parent60b23d9c43576bceb0dc18580fb55900174512f2 [diff]
[lucicfg] Improve rendering of errors with backtraces.

Also move relevant code into a dedicated package.

Previously, annotating such errors "swallowed" the backtrace,
resulting in e.g.

```
loading PACKAGE.star: in declare: bad package name "infra": must start with @
```

Now an annotated backtracable error is rendered as e.g.

```
Error: loading PACKAGE.star:
Traceback (most recent call last):
  //PACKAGE.star:1:12: in <toplevel>
  @stdlib//builtins.star:53:23: in _declare
Error in declare: bad package name "infra": must start with @
```

Depends on string hax, since errors aren't very examinable.

R=iannucci@chromium.org

Change-Id: If5c508de99833addbb1f3fcdc8bd22686987986d
Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/6354394
Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
Reviewed-by: Robbie Iannucci <iannucci@google.com>
10 files changed
tree: 1a34d890bd57d7b47e0664b3069933089ad97d03
  1. analysis/
  2. appengine/
  3. auth/
  4. auth_service/
  5. bisection/
  6. build/
  7. buildbucket/
  8. casviewer/
  9. cipd/
  10. cipkg/
  11. client/
  12. common/
  13. config/
  14. config_service/
  15. cv/
  16. deploy/
  17. examples/
  18. gae/
  19. gce/
  20. grpc/
  21. hardcoded/
  22. led/
  23. logdog/
  24. luci_notify/
  25. lucicfg/
  26. lucictx/
  27. luciexe/
  28. mailer/
  29. milo/
  30. mmutex/
  31. provenance/
  32. recipes_py/
  33. resultdb/
  34. scheduler/
  35. scripts/
  36. server/
  37. source_index/
  38. standalone/
  39. starlark/
  40. swarming/
  41. teams/
  42. third_party/
  43. tokenserver/
  44. tools/
  45. tree_status/
  46. vpython/
  47. web/
  48. .gitallowed
  49. .gitignore
  50. .go-lintable
  51. AUTHORS
  52. codereview.settings
  53. CONTRIBUTING.md
  54. CONTRIBUTORS
  55. go.mod
  56. go.sum
  57. LICENSE
  58. OWNERS
  59. PRESUBMIT.py
  60. README.md
  61. staticcheck.conf
  62. tools.go
  63. WATCHLISTS
README.md

luci-go: LUCI services and tools in Go

GoReference

Installing

LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:

fetch infra
cd infra/go
eval `./env.py`
cd src/go.chromium.org/luci

It is now possible to directly install tools with go install:

go install go.chromium.org/luci/auth/client/cmd/...@latest
go install go.chromium.org/luci/buildbucket/cmd/...@latest
go install go.chromium.org/luci/cipd/client/cmd/...@latest
go install go.chromium.org/luci/client/cmd/...@latest
go install go.chromium.org/luci/cv/cmd/...@latest
go install go.chromium.org/luci/gce/cmd/...@latest
go install go.chromium.org/luci/grpc/cmd/...@latest
go install go.chromium.org/luci/logdog/client/cmd/...@latest
go install go.chromium.org/luci/luci_notify/cmd/...@latest
go install go.chromium.org/luci/lucicfg/cmd/...@latest
go install go.chromium.org/luci/luciexe/legacy/cmd/...@latest
go install go.chromium.org/luci/mailer/cmd/...@latest
go install go.chromium.org/luci/mmutex/cmd/...@latest
go install go.chromium.org/luci/resultdb/cmd/...@latest
go install go.chromium.org/luci/server/cmd/...@latest
go install go.chromium.org/luci/swarming/cmd/...@latest
go install go.chromium.org/luci/tokenserver/cmd/...@latest
go install go.chromium.org/luci/tools/cmd/...@latest

Contributing

Contributing uses the same flow as Chromium contributions.