Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U06A03HV1>: <@U04S45AHA> we’re currently throwing away the work of individually resolving node_remote_module targets, so i changed the code to not do that… and i modified the repl code to just go into the target directory and run node, as you would normally in a project, rather than try to construct a NODE_PATH with all the built targets as it does now, which i think could cause a problem <https://github.com/pantsbuild/pants/pull/2402> / <https://rbcommons.com/s/twitter/r/2997/>

Whatever happened to the "make pants documentation nicer" project at twitter?

seems to have been delayed a bit - since it’s non-critical, we’re competing with their normal business-critical project workload for attention. also, the designer working on it went on paternity leave shortly after the sitemap thing went out for review so it’s been subsequently transferred to a new designer.

but theoretically we should expect a proposed wireframe any day now.

`jar_dependency` excludes don't make it into the hash

<@U053HNE90>: They are included explicity in the fingerprint in IvyTaskMixin

I see no reason not to consider the excludes to be a hashable component of the jar_dep itself

I’m just saying, that is why it isn’t a problem for the rest of us

<@U06A03HV1> I understand that killing the time math is good, but I can’t think of another way to ensure that the timeout actually stops the test (rather than just waiting and then failing) in the integration test.

<@U0ANNGE92>: i'm not saying don't have a log message. i'm saying don't use time math to compute it

```timeout = 10; start = x; end = y; print("total time was {}".format(end - start))```

is going to result in stuff like `total time was 10.345`

but if i log the configured timeout and the bug comes back