https://pantsbuild.org/ logo
Join Slack
Powered by
Hi running pants from brew for the first time (use...
# general
m
Hi running pants from brew for the first time (used the old ./pants before) and I’m getting the following error:
Copy code
$ pants --version
Error: Isolates your Pants from the elements.

Please select from the following boot commands:

scie-pants
bootstrap-tools
pants
pants-debug
update

You can select a boot command by passing it as the 1st argument or else by setting the SCIE_BOOT environment variable.
I set SCIE_BOOT, based on the install instructions. so “update pants”
✅ 1
e
There should be more error text, you're just seeing (starting at "Isolates ...") a help screen you should never see.
What OS? And can you re-run as 
RUST_LOG=trace pants -V
? The output will be massive but it may help to see it.
Oh, right. OS is almost certainly Mac. I could still use the trace output though.
c
I set SCIE_BOOT, based on the install instructions. so “update pants”
what if you don’t set this at all?
oh, and if you want to update the 
pants
launcher, then you either use 
brew upgrade
or 
export SCIE_BOOT=update
then run 
pants
I separated them to make it clear that the value to provide to the env var there is just 
update
as it seems you set it to 
update pants
.
I don’t sugest actually using the export there, just wanted to highlight the setup. As you don’t want it set for normal operation.
e
Aha, yeah missed that last sentence in the OP. @mammoth-spring-77701 it would be interesting to know what portion of the install instructions seemed to suggest to you to 
export SCIE_BOOT="update pants"
, since that makes the error you got make sense.
m
Ah yeah all good by removing this, I was just reading the install instructions but now going back through it I just misinterpreted the update instructions. Thanks both for your help!
👍 1
e
OK. Well the scie help screen should probably have either an intro sentence or a trailing sentence that mentions the fact the scie was launched with env var SCIE_BOOT="x" and "x" is not amongst the supported boot commands which the rest of the message goes on to detail probably well enough with that additional context. I'll get that whipped out today.
This reveals another set of issues as well: 1. 
science
does not honor command 
descriptions
and they all show up blank in the scie help output: 2. The scie help output should probably hide scie boot commands with no description. 3. The scie-pants project should probably convert all its command descriptions to comments save for 
update
and 
bootstrap-tools
which are the only two intended for use by end users.
I'll leave it to Pants folks to fix 3 once I get out a release of scie-jump and science that fix these three issues.
👍 1
@curved-television-6568 sent you an invite to science in the off chance you want to get involved. Fix for the description propagation by 
science
is here: https://github.com/a-scie/lift/pull/44
😃 1
@curved-television-6568 one more invite is you're interested in the scie-jump: https://github.com/a-scie/jump/pull/145
c
thanks. I’ll peek around see if there’s some easy to tackle issues to get started on 😉
e
Great. #10 is of most relevance to Pants / SJs scie plugin work, but more generally Pants is relying on scie with little knowledge of how it works. Although Benjy and SJ have helped review; so probably have a grasp, no one besides me has hacked on the thing. Does not seem awesome.
👍 1
c
happy to get my feet wet, even if only polishing surfaces to begin with..
e
Ok, the 
science
issue (command description propagation) is fixed in the 0.2.1 release: + https://github.com/a-scie/lift/releases/tag/v0.2.1 The confusing help message when a bad SCIE_BOOT is supplied + the ability to hide internal-only commands from the help message is available in the 
scie-jump
0.13.0 release: + https://github.com/a-scie/jump/releases/tag/v0.13.0 The scie-pants maintainers can now upgrade to these if they wish + modify the scie-pants.toml lift manifest to have 2 less descriptions and get the following for the OP error case in this thread:
Copy code
$ export SCIE_BOOT="update pants"
$ pants --version
Error: `SCIE_BOOT=update pants` was found in the environment but "update pants" does not correspond to any scie-pants commands.

Isolates your Pants from the elements.

Please select from the following boot commands:

<default> (when SCIE_BOOT is not set in the environment)  Detects the current Pants installation and launches it.
bootstrap-tools                                           Introspection tools for the Pants bootstrap process.
update                                                    Update scie-pants.

You can select a boot command by setting the SCIE_BOOT environment variable.
b
I've done the upgrade in https://github.com/pantsbuild/scie-pants/pull/284 (thanks for the upstream work, John)
👍 1
Open in Slack
PreviousNext
Powered by