| commit | 0cc8989a28833d473520233ae2ffff4e6561f4fa | [log] [tgz] |
|---|---|---|
| author | Vadim Shtayura <vadimsh@chromium.org> | Wed Dec 05 20:47:28 2018 |
| committer | Commit Bot <commit-bot@chromium.org> | Wed Dec 05 20:47:28 2018 |
| tree | a86db11e5890cca7e08ae311eb15c31fe52bde1e | |
| parent | 39238bd759e33b01f67631b26000842784722b14 [diff] |
[lucicfg] Slightly improve error messages by removing redundant info. Instead of reporting the full key (a list of (kind, id) pairs), we report only the last pair. The stack trace should provide enough context to understand what exactly the error refers to. This reduces how many internal implementation details (e.g. composite keys) we leak to the outside. R=nodir@chromium.org BUG=833946 Change-Id: I4227d5c015b037c498d63f4d4a3104d2aff5b91f Reviewed-on: https://chromium-review.googlesource.com/c/1362398 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Vadim Shtayura <vadimsh@chromium.org>
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
Contributing uses the same flow as Chromium contributions.