Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yeast 8.5.0 #262

Merged
merged 72 commits into from
Jul 2, 2021
Merged

yeast 8.5.0 #262

merged 72 commits into from
Jul 2, 2021

Conversation

edkerk
Copy link
Member

@edkerk edkerk commented Jul 1, 2021

Main improvements in this PR:

Also rename your local branches to main and develop:

git branch -m master main
git branch -m devel develop
git fetch origin
git branch -u origin/main main
git branch -u origin/develop develop
git remote set-head origin -a

I hereby confirm that I have:

  • Tested my code with all requirements for running the model
  • Selected main as a target branch (top left drop-down menu)
  • If needed, asked first in the Gitter chat room about this PR

edkerk and others added 10 commits June 29, 2021 13:41
This partially reverts commit 919d396.
Restores the model.id so it will not have the dash (so yeastGEM instead of yeast-GEM)
mistakingly reverted in last commit
Benjamin's email no longer active, replace with Eduard's
- master --> main
- devel --> develop
@edkerk edkerk mentioned this pull request Jul 1, 2021
3 tasks
@edkerk edkerk marked this pull request as ready for review July 2, 2021 09:47
@edkerk
Copy link
Member Author

edkerk commented Jul 2, 2021

@mihai-sysbio Not sure why memote-history.yml contains the step Memote short run (line 42), but should its containing command not at least include --ignore-git? This was not problematic in recent commits/PRs as the model file hadn't changed (see for instance here).

@mihai-sysbio
Copy link
Member

Not sure why memote-history.yml contains the step Memote short run (line 42)

I see that the memote run action runs only on pull_request, whereas the memote history runs on push, which happens more often.

but should its containing command not at least include --ignore-git?

There is a hint in this line from memote:

"--ignore-git", is_flag=True, help="Avoid checking the git repository status."

This flag is needed only if the model has been modified without having the changes committed/stashed, e.g. by writing a BiGG compliant model, exactly how it is the case for the memote run action. Instead, memote history runs on the unchanged model.

@edkerk
Copy link
Member Author

edkerk commented Jul 2, 2021

@mihai-sysbio Aha, thanks for the explanation. But then I don't understand why memote history fails.

@mihai-sysbio
Copy link
Member

mihai-sysbio commented Jul 2, 2021

The error appears to be interspersed with the memote output, here are the relevant lines:

Committing result and changing back to working branch.
Storing result '03ee7535d608b89812b01f3fa1660b9ce355170b'.
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.9.5/x64/bin/memote", line 8, in <module>
    sys.exit(cli())
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/memote/suite/cli/runner.py", line 289, in run
    repo.git.commit(
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/git/cmd.py", line 545, in <lambda>
    return lambda *args, **kwargs: self._call_process(name, *args, **kwargs)
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/git/cmd.py", line 1011, in _call_process
    return self.execute(call, **exec_kwargs)
  File "/opt/hostedtoolcache/Python/3.9.5/x64/lib/python3.9/site-packages/git/cmd.py", line 828, in execute
    raise GitCommandError(command, status, stderr_value, stdout_value)
git.exc.GitCommandError: Cmd('git') failed due to: exit code(128)
  cmdline: git commit --message chore: add result for 03ee7535d608b89812b01f3fa1660b9ce355170b
  stderr: 'Author identity unknown
 
*** 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 <runner@fv-az212-186.zlodpucb4l4udavnfxg5s20dva.cx.internal.cloudapp.net>) not allowed

The line that looks weirdest to me is:

cmdline: git commit --message chore: add result for 03ee7535d608b89812b01f3fa1660b9ce355170b

@mihai-sysbio
Copy link
Member

mihai-sysbio commented Jul 2, 2021

It doesn't hurt to try out your idea @edkerk. Commit c897a25 adds the flag to instruct memote to not inspect the repository installation, so I'm hoping this does the trick (although I don't understand why it worked so far and now it doesn't).

Copy link
Collaborator

@feiranl feiranl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed all changes for the fix part

Copy link
Member

@mihai-sysbio mihai-sysbio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, although I am mostly trusting previous reviews here.

@edkerk
Copy link
Member Author

edkerk commented Jul 2, 2021

Seems like my suggestion didn't work though. The step Memote short run now does not submit the results to gh-pages (which it tried to do previously with cmdline: git commit --message chore: add result for 03ee7535d608b89812b01f3fa1660b9ce355170b, so when the history report is made it doesn't find the most recent changes:

In output from the step Compute Memote history on push, you can see it reads results from gh-pages but does not find the latest commit with changed model (03ee753):

Line 10: Obtaining history of results from the deployment branch gh-pages. (it reads results.db?)

Line 11534-11535: Loading result from '03ee7535d608b89812b01f3fa1660b9ce355170b'.
error: Could not load result '03ee7535d608b89812b01f3fa1660b9ce355170b'.

The problem seems to be that in the step Memote short run it does not have the proper credentials for pushing to gh-pages. In the step Auto-commit results the pushing of history_report.html to gh-pages is not handled directly by memote but rather by the action stefanzweifel/git-auto-commit-action@v4.4.0 (where the user name is set!). I'll try to see what happens when setting global user name to memote-bot, bare with me...

@edkerk
Copy link
Member Author

edkerk commented Jul 2, 2021

The history report is still not working exactly as intended (see comment), but will merge this PR now as it at least introduces the memote CI to the repo.

@edkerk edkerk merged commit 89e369f into main Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix: Wrong annotation for s_1218 fix: wrong annotation for gene YGR191W for rxn r_4590
4 participants