A build problem after updating moose

[Always-kimi]

Check these boxes if you have followed the posting rules.

• Q&A Getting Started is the most appropriate category for my question (trouble installing, beginner user, ...)
• I have consulted the posting Guidelines on the Discussions front page
• I have searched the Discussions forum and my question has not been asked before
• I have searched the MOOSE website and the documentation does not answer my question
• I have formatted my post following the posting guidelines (avoid screenshots if possible, triple back quotes before/after pasted text, etc)

Issue or question about MOOSE

hello
developers,

I have a build problem after updating moose when I rebuild my applications. It seems to be a git problem that just happened yesterday and on both debian and wsl.

fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Traceback (most recent call last):
  File "/home/kimi/projects/moose/framework/../scripts/premake.py", line 183, in <module>
    PreMake().check()
  File "/home/kimi/projects/moose/framework/../scripts/premake.py", line 18, in __init__
    self.versioner_meta = Versioner().version_meta()
  File "/home/kimi/projects/moose/scripts/versioner.py", line 302, in version_meta
    app_name, _, app_hash = self.get_app()
  File "/home/kimi/projects/moose/scripts/versioner.py", line 352, in get_app
    git_hash = subprocess.check_output(hash_command, encoding='utf-8').rstrip()[0:7]
  File "/home/kimi/miniforge/envs/moose/lib/python3.10/subprocess.py", line 421, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/home/kimi/miniforge/envs/moose/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['git', 'rev-parse', 'HEAD']' returned non-zero exit status 128.
make: [/home/kimi/projects/moose/framework/moose.mk:388: prebuild] Error 1 (ignored)

Although it doesn't affect the build and test applications, I'd like to know how to deal with it.

Diagnostics for MOOSE installation issues

[Optional] Output of the diagnostics scripts. To run the script: cd ~/projects/moose/scripts; ./diagnostics.sh

[GiudGiud]

Hello

In which folder are you building? It seems to be outside of a git repository

Guillaume

[Always-kimi]

In the babbler folder created by using the command `./moose/scripts/stork.sh Babbler'.

I try to build a new application, it's still the same.

(moose) kimi@DESKTOP-7APSM1S:~/projects$ ./moose/scripts/stork.sh Abc
Initialized empty Git repository in /home/kimi/projects/abc/.git/

*** Please tell me who you are.

Run

  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: empty ident name (for <kimi@DESKTOP-7APSM1S.localdomain>) not allowed
MOOSE app created in '/home/kimi/projects/abc'

To store your changes on GitHub:
    1. Log in to your GitHub account
    2. Create a new repository named 'abc'
    3. In this terminal window, run the following commands:
         cd /home/kimi/projects/abc
         git remote add origin https://github.com/YourGitHubUserName/abc
         git commit -m "Initial code commit"
         git push -u origin main

To automatically enforce MOOSE C++ code style in your commits, run:

    cd /home/kimi/projects/abc
    ./scripts/install-format-hook.sh

To enable software quality assurance (SQA) documentation using MooseDocs, perform the
following steps after adding your git repository remote:

    1. Navigate to /home/kimi/projects/abc/doc
    2. Run './moosedocs.py init sqa --app 'Abc' --category abc'
    3. Commit the initial SQA changes using the following commands:
         git add /home/kimi/projects/abc/doc
         git commit -m "Initial SQA changes"
         git push origin main
    4. Add new SQA content to the forms in /home/kimi/projects/abc/doc/content/sqa

For general assistance in MOOSE-based application SQA, please contact the MOOSE
framework development team. For further info on the MooseDocs code documentation
system, please visit https://mooseframework.inl.gov.
(moose) kimi@DESKTOP-7APSM1S:~/projects$ cd abc/
(moose) kimi@DESKTOP-7APSM1S:~/projects/abc$ make -j6
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Traceback (most recent call last):
  File "/home/kimi/projects/moose/framework/../scripts/premake.py", line 183, in <module>
    PreMake().check()
  File "/home/kimi/projects/moose/framework/../scripts/premake.py", line 18, in __init__
    self.versioner_meta = Versioner().version_meta()
  File "/home/kimi/projects/moose/scripts/versioner.py", line 302, in version_meta
    app_name, _, app_hash = self.get_app()
  File "/home/kimi/projects/moose/scripts/versioner.py", line 352, in get_app
    git_hash = subprocess.check_output(hash_command, encoding='utf-8').rstrip()[0:7]
  File "/home/kimi/miniforge/envs/moose/lib/python3.10/subprocess.py", line 421, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/home/kimi/miniforge/envs/moose/lib/python3.10/subprocess.py", line 526, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['git', 'rev-parse', 'HEAD']' returned non-zero exit status 128.
make: [/home/kimi/projects/moose/framework/moose.mk:388: prebuild] Error 1 (ignored)

[GiudGiud]

the creation of the app is failing:
it is telling you to run this

  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

then Babbler, because this has not been done, is not an actual git repository

[Always-kimi]

Oh I got it, but this operation wasn't needed before when creating a moose application, did the moose framework update the procedure?

[GiudGiud]

I dont think we have. We ll make sure we catch this problem in the future though, I created an issue

[Always-kimi]

Thanks a lot!