witty-crayon-22786
05/23/2019, 5:40 PMwitty-crayon-22786
05/23/2019, 5:42 PM--compile-zinc-args
. you're likely seeing that warning because you changed the value of --compile-zinc-whitelisted-args="{'key1':val1,'key2':val2,...}" (default: { '-S.*':'False','-C.*':'False','-file-filter':'True','-msg-filter':'True' })
A dict of option regexes that make up pants' supported API for zinc. Options
not listed here are subject to change/removal. The value of the dict
indicates that an option accepts an argument.
perhaps?witty-crayon-22786
05/23/2019, 5:43 PMhappy-kitchen-89482
05/23/2019, 5:58 PMhappy-kitchen-89482
05/23/2019, 6:28 PMException in thread NailgunStreamWriter:
Traceback (most recent call last):
File "/Users/benjyw/.pyenv/versions/3.6.6/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
File "/Users/benjyw/.cache/pants/setup/bootstrap-Darwin-x86_64/1.17.0.dev1_py36/lib/python3.6/site-packages/pants/java/nailgun_io.py", line 271, in run
self._in_fds.remove(fileno)
ValueError: list.remove(x): x not in list
happy-kitchen-89482
05/23/2019, 6:29 PMhappy-kitchen-89482
05/23/2019, 6:30 PMerrored
is supposed to be a subset of self._in_fds
happy-kitchen-89482
05/23/2019, 6:31 PMerrored
?witty-crayon-22786
05/23/2019, 6:32 PMaloof-angle-91616
05/23/2019, 6:32 PMhappy-kitchen-89482
05/23/2019, 6:34 PMhappy-kitchen-89482
05/23/2019, 6:40 PMValueError
, but it would be nice to know why it's happening.happy-kitchen-89482
05/23/2019, 6:46 PMselect()
syscall modifies the argument lists in-place, is it possible Python does the same? The documentation implies not, but doesn't explicitly say so.red-balloon-89377
05/23/2019, 7:03 PMmock
help, if someone has a minute:
I have something like:
fake_environment = {"PANTSD_REQUEST_TIMEOUT_LIMIT": "-1"}
self.mock_handler_inst.parsed_request = lambda: (None, None, [], fake_environment)
,red-balloon-89377
05/23/2019, 7:03 PMred-balloon-89377
05/23/2019, 7:04 PMhandler.parsed_request()
from the threads, I get:
# The first thread
ENv is {'PANTSD_REQUEST_TIMEOUT_LIMIT': '-1'}
# The second thread
ENv is {}
red-balloon-89377
05/23/2019, 7:04 PMbrief-engineer-67497
05/27/2019, 5:11 PMbrief-engineer-67497
05/27/2019, 5:11 PMresolve.ivy
but it's kind of tedious right nowflaky-photographer-75744
05/29/2019, 2:25 PMTraceback (most recent call last):
File "/home/alexis/.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-16.4.3/virtualenv.py", line 22, in <module>
import distutils.spawn
ModuleNotFoundError: No module named 'distutils.spawn'
./pants: line 170: /home/alexis/.cache/pants/setup/bootstrap-Linux-x86_64/pants.fPKtJQ/install/bin/pip: No such file or directory
./pants: line 171: /home/alexis/.cache/pants/setup/bootstrap-Linux-x86_64/pants.fPKtJQ/install/bin/pip: No such file or directory
New virtual environment successfully created at /home/alexis/.cache/pants/setup/bootstrap-Linux-x86_64/1.15.0_py36.
./pants: line 193: /home/alexis/.cache/pants/setup/bootstrap-Linux-x86_64/1.15.0_py36/bin/python: No such file or directory
After some investigatiosn it appeared with 1.15.0.dev0
versionaloof-angle-91616
05/29/2019, 2:26 PMpip3 install setuptools==40.0.0
, which i didn't try to push a fix for because i thought it was isolated to the environment i was in, and it was running pants from source -- could you let me know if that does anything?dry-policeman-7927
05/30/2019, 2:26 PMbackground_root_workunit
to be a child of the main workunit?
Pictures show how the trace will look like in this case.
If this solution is not very good I would be grateful for better one 🙂dry-policeman-7927
05/30/2019, 2:27 PMaverage-vr-56795
05/30/2019, 3:19 PMaverage-vr-56795
05/30/2019, 4:05 PMaloof-angle-91616
05/30/2019, 4:06 PMaloof-angle-91616
06/03/2019, 12:44 PM./pants test --compile-zinc-cache-ignore
works -- i would have assumed that this would become --test-compile-zinc-cache-ignore
, which doesn't exist
(2) ./pants test --junit-cache-ignore
fails -- i would have assumed this would become --test-junit-cache-ignore
, analogous to ./pants test.junit --cache-ignore
, except additionally:
(3) ./pants --test-junit-cache-ignore
isn't recognized!! resulting in Exception message: Unrecognized command line flags on scope 'test.junit': --cache-ignore.
this is despite the fact that ./pants test.junit --cache-ignore
works!!
i think these feel like fixable bugs -- one approach is e.g. to "normalize" all command lines into options with scopes, e.g. convert test.junit --cache-ignore
into --test-junit-cache-ignore
, and then modify the code that looks for options to be able to recognize that (it currently doesn't -- that's #3 above). has anyone experienced any other surprises with options? does anyone have any thoughts on whether changing the options behavior to fix 1, 2, 3 above might break existing behavior (e.g. in scripts calling pants)?average-vr-56795
06/03/2019, 1:07 PMred-balloon-89377
06/05/2019, 11:05 AMthankful-barista-85113
06/05/2019, 1:37 PM