failed to resolve revision HEAD

[fsipa]

Bossman command are throwing the below error:

There are no problems with the git command because all the git command are working fine.

[ynohat]

Hi @fsipa ,

Thanks for this. Could you please share the output of git status?

It looks like you may be running into #9 , which typically occurs when a build system checks out a specific commit or tag as opposed to a branch. I would appreciate if you could help me confirm this.

[fsipa]

@ynohat here the output of git status

I assume that i am not running into detached HEAD. I have just clone the git repositery and try to run the "bossman status" from the master branch

[ynohat]

@fsipa is that still the output from bossman status, as opposed to git status? Thanks!

[fsipa]

@ynohat yes the output from bossman status give also the same error

[ynohat]

@fsipa sorry for the confusion. The error you are showing is the output of bossman commands. I am asking for the output of the git status command please.

[fsipa]

Ah ok. The confusion comes from me, sorry. Here the output of git status and bossman status

[ynohat]

Thanks a lot. Can you please share the output of

python3 -m pip show bossman

and

bossman --verbosity=DEBUG status

It would also be helpful if you could share details about how this occurred. Did you recently change workstations and are reinstalling? Was it an upgrade? Any change at all?

Thanks a lot for helping me troubleshoot this.

[ynohat]

Oh I just tried on my M1 and it works fine, so I don't think it's something related to the processor architecture directly. I've rephrased the issue title accordingly.

[fsipa]

@ynohat here the commands output:

I switch for 6 weeks from a Windows workingstation to Mac M1. So the setup went well.

[ynohat]

OK very clear, thank you.
Can you please try upgrading bossman to the latest version, which is 0.42.0?

python3 -m pip install --upgrade bossman

[fsipa]

@ynohat

i have actually the latest version(0.42.0) on my machine. Thanks

[fsipa]

@ynohat Hi there,

Somehow there was a version mismatch of the bossman installation. Now it is fine

[ynohat]

OK @fsipa, thanks for the update, do you still get the error though?

[ynohat]

I just released v0.42.1 which adds more detailed logs for when the error condition you are experiencing occurs.
If you are still facing this, please upgrade and share the logs again.

bossman --verbosity=DEBUG status

[fsipa]

@ynohat unfortunately the error is still there. I upgraded to the new version v0.42.1 and run the bossman status again

[ynohat]

@fsipa thanks for your patience with this; I'm surprised by the output, which does not contain the extra debug information I was expecting.

Could you please share the output of

which bossman

The intent is to check that the bossman you are executing is actually the one in /Users/fsi/Library/Python/3.9/bin/bossman which you just upgraded to 0.42.1.

If it is in a system wide location, then you should execute sudo python3 -m pip uninstall bossman.

Then

echo $PATH

To verify that you can /Users/fsi/Library/Python/3.9/bin/ is searched for executables, otherwise the command won't be found.

[fsipa]

@ynohat thank you for the help

The output of the "which bossman" command is empty. Very strange.
I executed also the other command "echo $PATH"

[ynohat]

OK, let's try this command:

PATH="/Users/fsi/Library/Python/3.9/bin/:$PATH" bossman status

[fsipa]

Here the output

[ynohat]

sorry, with --verbosity=DEBUG please

[fsipa]

@ynohat here it is

[ynohat]

I think I've got it.
I believe you have maybe retrieved your bashrc file from your WSL env on windows and it had an alias for executing bossman in docker, this may be why you have the Popen cwd=/work.
This would also explain why which bossman returns no output, because bossman is not actually resolving to the executable, but in fact to the bossman alias.
If this is the case, you should have an alias bossman="docker run ..." command in one of your init files (e.g; ~/.bashrc).
Could you please check?

[fsipa]

@ynohat
I already have an alias command in my bash file.

alias bossman='docker run -it --rm --platform linux/amd64 --name=akamai-bossman -e TERM=xterm-256color -v ~/.ssh/id_rsa:/home/bossman/.ssh/id_rsa:ro -v $PWD:/work -v ~/.edgerc:/home/bossman/.edgerc ynohat/bossman'

I have tried to remove this alias command and add it again, however the output of debug command still shows Popen cwd=/work

[ynohat]

Just in case: When you remove the alias you need to `source ~/.bashrc` Or re-open a new terminal, for the change to take effect. After that, you should get "command not found", because the executable is not on your PATH, to fix this you can simply add the following line to your `~/.bashrc`: `export PATH="/Users/fsi/Library/Python/3.9/bin/:$PATH"` Then `source ~/.bashrc` At this point I'm hoping bossman will work for you.

[fsipa]

Hi @ynohat

i have tried it. But unfortunately it still not working.

[ynohat]

Hi @fsipa you really need to remove the alias from your .zshrc, it is not working and is causing our troubles.
Once removed, you should

source ~/.zshrc

And try again

[fsipa]

Hello @ynohat. Thank you for the support.

I removed the alias from the .zshrc and it look now somehow different...

[ynohat]

OK, there is likely a .bossmancache.db file in your project folder, copied over from the windows install? Please delete that.

[fsipa]

Unfortunately i don't have this file .bossmancache.db on my project folder, I have this instead .bossmancache

[ynohat]

Right, that's the one; please delete it

[fsipa]

SOLVED !! Incredible ...Now it worked fine.

Thank you very much @ynohat, for the patience and the final solution. I learned a lot about bossman these last days

[ynohat]

I'm happy to know you folks are still happy users! Any time.

[ynohat]

@fsipa one last thing, that file should not be in source control, you should take steps to remove it from git and add it in .gitignore to avoid any pain at a later stage. The purpose of the file is just to keep some things in cache to avoid always going back to the APIs, it is by no means critical or important as a means of preserving bossman state.

With this, I'll close this and feel free to reopen if required.