GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — BF: remove a submodule with a remote without refs + misc fixes around by yarikoptic · Pull Request #521 · gitpython-developers/GitPython

Conversation

@yarikoptic

@yarikoptic yarikoptic commented Oct 2, 2016

Copy link
Copy Markdown
Contributor

now if there is a remote without any refs (this happens e.g. with git-annex repo with special remotes), it would refuse to remove the submodule
(with 2.0.8 it also didn't work but with a different msg "AssertionError: Remote datalad did not have any references")

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@yarikoptic
BF: Allow to remove a submodule with a remote without refs
f2b92c6
@yarikoptic yarikoptic mentioned this pull request Oct 2, 2016
uninstall would fail uninstall submodule with special remotes! datalad/datalad#970
Closed
@ankostis

ankostis commented Oct 2, 2016

Copy link
Copy Markdown
Contributor

@yarikoptic would it be possible to add a test-case into the PR with the annex command, replicating the situation you just described?

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

yarikoptic added 3 commits October 2, 2016 10:13
@yarikoptic
BF: @with_rw_directory must return decorated call
31fd955
As it was - many tests were simply not accounted/run at all
@yarikoptic
BF: log.info is a function, just pass msg, no .write!
2528d11
@yarikoptic
TST: finishing test for removing submodule with remotes without refs
f284a4e
originally draft committed by mistake in 31fd955
sorry
@yarikoptic

yarikoptic commented Oct 2, 2016

Copy link
Copy Markdown
Contributor Author

ok @ankostis -- but along the way had to fix 2 other bugs... apparently some tests (which used @with_rw_directory) were not run at all! so you can expect failures of those tests which were effected

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

yarikoptic
yarikoptic commented Oct 2, 2016
View reviewed changes
Comment thread git/test/test_submodule.py
assert sm.exists()

parent.index.commit("Added submodule")

@yarikoptic yarikoptic Oct 2, 2016

Copy link
Copy Markdown
Contributor Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

and I am not sure why that is the case -- I was expecting submodules repo to be the repo of the submodule ... but I guess it can make sense to refer to parent which contains the submodule, but then is there an attribute for submodules repo (if present)?

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@ankostis ankostis Oct 2, 2016

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

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

@Byron any comment? I'm not familiar with git-modules.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@yarikoptic

yarikoptic commented Oct 2, 2016

Copy link
Copy Markdown
Contributor Author

reincarnating @with_rw_directory lead to one failing test

======================================================================

FAIL: test_lock_reentry (git.test.test_config.TestBase)

----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/gitpython-developers/GitPython/git/test/lib/helper.py", line 95, in wrapper
    return func(self, path)
  File "/home/travis/build/gitpython-developers/GitPython/git/test/test_config.py", line 100, in test_lock_reentry
    self.failUnlessRaises(IOError, GitConfigParser, fpl, read_only=False)
AssertionError: IOError not raised
-------------------- >> begin captured logging << --------------------

git.util: INFO: Test TestBase.test_lock_reentry failed, output is at '/tmp/test_lock_reentryfSovNi'

I am not sure on state of locking/context manager expectations atm and see recent work touching locking... so I will need to leave this to you guys (@ankostis ?) to figure out

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@yarikoptic yarikoptic changed the title BF: Allow to remove a submodule with a remote without refs BF: remove a submodule with a remote without refs + misc fixes around Oct 2, 2016
yarikoptic added a commit to yarikoptic/GitPython that referenced this pull request Oct 2, 2016
@yarikoptic
RF: coveralls (not used/relied on really) -> codeco
18caa95
codecov in our (datalad, etc) experience provides a better service,
great support, and super-nice intergration with chromium and firefox
for reviewing coverage of pull requests.  In light of the
@with_rw_directory fiasco detected/fixed in gitpython-developers#521 I would strongly
recommend to (re-)enable and use coverage reports
@yarikoptic yarikoptic mentioned this pull request Oct 2, 2016
RF: coveralls (not used/relied on really) -> codecov #522
Merged
yarikoptic added a commit to yarikoptic/GitPython that referenced this pull request Oct 2, 2016
@yarikoptic
RF: coveralls (not used/relied on really) -> codecov
94ca83c
codecov in our (datalad, etc) experience provides a better service,
great support, and super-nice intergration with chromium and firefox
for reviewing coverage of pull requests.  In light of the
@with_rw_directory fiasco detected/fixed in gitpython-developers#521 I would strongly
recommend to (re-)enable and use coverage reports
@ankostis

ankostis commented Oct 2, 2016

Copy link
Copy Markdown
Contributor

@yarikoptic so you mean that git.test.test_config:TestBase.test_lock_reentry() that is failing is included in the CI for the first time?

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@yarikoptic

yarikoptic commented Oct 2, 2016

Copy link
Copy Markdown
Contributor Author

Yes, at least since some time in the past

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@yarikoptic

yarikoptic commented Oct 2, 2016

Copy link
Copy Markdown
Contributor Author

If your really want to know, I could check later since when

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@ankostis

ankostis commented Oct 2, 2016 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

Indeed @yarikoptic your 31fd955 fixed an important regression introduced by #519,
where I had practically disabled 19 TCs!
(so the ALL GREEN was an illusion :-/, check #519 for the actual list of TC errors on Windows)

So, I'm cherry picking your 2528d11 and 31fd955 but modified to include only your helper.py fixes and pushing them into my own repo, to try to fix the failing TC; for the test_submodles.py changes, they have to wait, and I will collect them and re-synthesize a new branch to merge.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@ankostis ankostis mentioned this pull request Oct 2, 2016
Test project on Windows with MINGW git (conda2.7&3.4/cpy-3.5) #519
Merged
@ankostis
ankostis merged commit f284a4e into gitpython-developers:master Oct 2, 2016
ankostis added a commit that referenced this pull request Oct 2, 2016
@ankostis
"Null" merge yarik/bf-rsubmodule-remove to close #521
3dc2f73
+ The actual commits have been re-written and rebased previously.
@ankostis

ankostis commented Oct 2, 2016

Copy link
Copy Markdown
Contributor

On Travis, PY3.3 failed due to file-handles; increased ulimit 96-->100 solved the problem.
On Appveyor, this is a drama...

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@ankostis

ankostis commented Oct 2, 2016 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

Forgot to thank you.
@yarikoptic If you may, add yourself on the Authors, on this branch, and I will cherry-pick it, just add a comment here to notify me.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@yarikoptic

yarikoptic commented Oct 3, 2016

Copy link
Copy Markdown
Contributor Author

That is OK, if you like to see me there - add, otherwise I am just fine. Cheers. Thanks for attending to my PRs quickly

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@yarikoptic
yarikoptic deleted the bf-rsubmodule-remove branch October 15, 2016 05:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer
@ankostis ankostis ankostis left review comments
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@yarikoptic @ankostis
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.