strong-caravan-64652
06/19/2019, 12:59 AMsrc/resources
sub-directory, and declared it as a dependency in my application, but it doesn't seem to be getting picked up by my application.happy-kitchen-89482
06/19/2019, 3:18 PMhappy-kitchen-89482
06/19/2019, 3:18 PMfierce-park-88503
06/19/2019, 3:26 PMaverage-vr-56795
06/19/2019, 7:28 PM/home/travis/.cache/pants/bin/binutils/linux/x86_64/2.30/binutils/bin/ld: cannot find -ltensorflow_framework
any ideas?red-balloon-89377
06/21/2019, 11:01 AMable-farmer-8537
06/24/2019, 3:34 PMImportError: No module named gunicorn.__main__; 'gunicorn' is a package and cannot be directly executed
Here's BUILD file. I assume that entry_point
do the same thing as -c
flag in pex?
python_binary(
name = "test_bin",
dependencies = [
":test_lib",
],
entry_point = "gunicorn",
)
wide-energy-11069
06/24/2019, 10:03 PM./pants goals
red-balloon-89377
06/25/2019, 1:50 PMfierce-park-88503
06/26/2019, 8:03 PM--pycheck-pycodestyle-ignore
that also suppresses the output?able-farmer-8537
06/27/2019, 12:23 PMException caught: (pex.resolver.Unsatisfiable) (backtrace omitted)
Exception message: Could not satisfy all requirements for Markdown==2.1.1:
Markdown==2.1.1(from: pantsbuild.pants==1.15.0), markdown>=2.6.8(from: tensorflow==1.12.0->tensorboard<1.13.0,>=1.12.0)
Is there any way to resolve such requirements clashes?enough-analyst-54434
06/27/2019, 1:31 PMstrong-caravan-64652
06/27/2019, 10:07 PMorg.apache.commons.commons-lang3
is actually a dependency of net.logstash.logback-logstash-logback-encoder
, but it's trying to include a resource that was in META-INF.
excludes = [
exclude(org="org.apache.commons" name="commons-lang3")
]
does nothing.
===== For target JvmBinary(BuildFileAddress(src/jvm/com/thesigma/server/restapi/bin/BUILD, bin)):
Duplicate classes and/or resources detected in artifacts: ('net.logstash.logback-logstash-logback-encoder-6.1.jar', 'org.apache.commons-commons-lang3-3.5.jar')
META-INF/maven/org.apache.commons/commons-lang3/pom.xml
META-INF/maven/org.apache.commons/commons-lang3/pom.properties
helpful-portugal-42688
07/01/2019, 9:58 PMaloof-angle-91616
07/01/2019, 9:59 PMaloof-angle-91616
07/01/2019, 10:00 PMaloof-angle-91616
07/01/2019, 10:00 PMhelpful-portugal-42688
07/01/2019, 10:09 PMapache_thrift_node_gen.py
when I override the execute_codegen, I essentially just create the default package.json and the yarn.lock and then just call the super().execute_codegen(target, target_workdir)
, am I missing something here, I was looking at similar py_gen and java_gen in the pants/backend/codegen and they both essentially call the super's exec_codegen and I feel that doing that should take care of the code generation however, I feel like that's too easy to be true.
3. How can I check whether a default package.json and yarn.lock was specified or not, is there a way to get it from the target?
Disclaimer: I'm kinda dim as you probably witnessed earlier.red-balloon-89377
07/08/2019, 10:54 AMgentle-wolf-58752
07/08/2019, 11:15 PMhundreds-breakfast-49010
07/09/2019, 8:44 PMwitty-crayon-22786
07/09/2019, 9:05 PMOptionsBootstrapper
and Options
gray-activity-4301
07/12/2019, 8:21 AMfresh-architect-74417
07/12/2019, 9:21 PMhappy-kitchen-89482
07/12/2019, 11:02 PMgray-activity-4301
07/13/2019, 5:29 PMhappy-kitchen-89482
07/15/2019, 5:13 AMpants.ini
for that repo?happy-kitchen-89482
07/15/2019, 5:14 AMpurple-oil-45048
07/15/2019, 2:13 PM./pants compile
command that was powering your 600 node build farm.
I vaguely remember you used some interesting zinc options to randomise the build order .. but sadly slack’s search only goes back a few months. Any chance you could share it once more?hundreds-breakfast-49010
07/15/2019, 9:03 PM