is there a way to continuously stream logs from Do...
# general
e
is there a way to continuously stream logs from Docker builds? all I got so far is
Copy code
[docker]
build_verbose = true
but it prints the logs from Docker only after the command concludes. All we see for several minutes is e.g.:
Copy code
14:17:25.02 [INFO] Starting: Building docker image <image name>
from what I see, a relevant piece of code is here: https://github.com/pantsbuild/pants/blob/876075026628f875b410282e9be09969dd401d7f/src/python/pants/backend/docker/goals/package_image.py#L463 we'd have to spin up a separate process to pull the logs and print them perhaps
f
This is a particular instance of the more general problem of streaming any process outputs: https://github.com/pantsbuild/pants/issues/11056
👍 1
(given how Pants invokes docker is the same as how it invokes every other build process, the problem is really one of streaming any process's outputs)
@gorgeous-winter-99296 had a prototype according to the issue, but the work appears to have stalled. I did a little exploration of the issue, but haven't looked at it in a while.
e
got it, yeah - it would be cool to have it, for the sake of providing the same level of visibility as before wrapping Docker builds with Pants (the way we perceive it, for this particular instance). For local builds, we can get away by using Docker Desktop to see the current progress, but not on CI
ok, all I can do is +1 the issue and keep my fingers crossed 🙂
a general question: is there any system of picking up feature requests in a specific order, like based on reactions or another kind of voting? or, if there's a contributor willing to implement it, we're lucky? even more general: is there a roadmap? I see some threads from a few years ago: https://github.com/pantsbuild/pants/discussions?discussions_q=is%3Aopen+roadmap - was it discontinued?
c
a general question: is there any system of picking up feature requests in a specific order, like based on reactions or another kind of voting?
Pants is a volunteer driven community open source project. So people tend to work towards scratching their own itch, or doing things that solve their own problems at companies that have adopted Pants. Sometimes people show up out of the blue with patches. There are also several paid service providers <https://www.pantsbuild.org/spotlight/service-providers>. Among the things maintainers volunteer to do are ~yearly surveys. They are broadly informative, but don't come with any "funding" to do the top-N things or anything like that.
gratitude thank you 1