System.Exception opening an existing repository #6093

fabvit · 2019-01-11T15:17:44Z

Current behaviour

Open one of my local repositories
after the repository is opened I got a System exception:

Unable to parse git command output.

Target System: System.Collections.Generic.IReadOnlyList`1[GitCommands.Remote] <GetRemotes>g__ParseRemotes|154_0(System.Collections.Generic.IEnumerable`1[System.String]) @ GitCommands.GitModule

Application: GitExtensions.exe [3.00.00.4433]

NBug: 3.00.rc2

CLR: 4.0.30319.42000

Please note that thes exception happens only when the left panel (the one enumerating branches and remotes) is visible.
If I hide the the left panel, no exception arises.

Expected behaviour

No exceptions opening a repo.

Steps to reproduce

See Current behaviour section above

Screenshots

Did this work in previous version of GitExtensions

Yes it works fine in GitExtensions-2.51.05

Environment

GitExtensions version: GitExtensions-3.00.00.4433
GIT version: $ git --version
git version 2.20.1.windows.1
OS version: Windows 7 Pro 64 bit
.NET version: 4.0.30319.42000

Diagnostics

The text was updated successfully, but these errors were encountered:

vbjay · 2019-01-11T15:33:59Z

https://github.com/gitextensions/gitextensions/releases/latest

…

On Fri, Jan 11, 2019, 10:17 AM fabvit ***@***.***> wrote: Current behaviour 1. Open one specific local repositories after the repository is opened I got a System exception: Unable to parse git command output. System.Collections.Generic.IReadOnlyList1[GitCommands.Remote] <GetRemotes>g__ParseRemotes|154_0(System.Collections.Generic.IEnumerable1[System.String]) @ GitCommands.GitModule GitExtensions.exe [3.00.00.4433] 3.00.rc2 4.0.30319.42000 (Please note that this is specific to *this* repo, other repos are opening fine. Expected behaviour No exceptions opening a repo. Steps to reproduce Screenshots Did this work in previous version of GitExtensions Yes it works fine in GitExtensions-2.51.05 Environment - GitExtensions version: GitExtensions-3.00.00.4433 - GIT version: $ git --version git version 2.20.1.windows.1 - OS version: Windows 7 Pro 64 bit - .NET version: 4.0.30319.42000 Diagnostics — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6093>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADdhsaUDg3myWw_i3CqmpHLN3qRREF3Xks5vCKsegaJpZM4Z7pYM> .

gerhardol · 2019-01-11T16:31:07Z

Please include the complete stacktrace from NBug.
If you dismiss the dialog, can you continue?
Can you share the repo where this occurred if the stacktrace is not obvious?

I believe @vbjay reacted on that NBug said 3.00.rc2. That may be incorrectly set there if so, for someone to follow up.

vbjay · 2019-01-11T16:34:14Z

Oh right. That issue has been fixed.

fabvit · 2019-01-11T16:51:50Z

@gerhardol and @vbjay yes I am on the very last version (https://github.com/gitextensions/gitextensions/releases/latest), namely Version 3.00.00 released on Dec 7, 2018.

@vbjay at this point I confused: what issue was been fixed?

    1. the wrong NBug: 3.00.rc2 text

OR

    2. my issue of System.Exception when opening an existing repository

Yes I can continue after dismissing the dialog and hiding the left panel.

Unfortunately I cannot share the repo.

vbjay · 2019-01-11T17:00:36Z

Yes. the wrong NBug: 3.00.rc2 text

gerhardol · 2019-01-11T17:03:30Z

The complete stacktrace is needed

I am not aware that this is reported before (but there are related corrections fixed in the upcoming 3.0.1
The complete stacktrace is needed

How many remotes do you have?
What is seen in the command log? (F12)

vbjay · 2019-01-11T17:11:02Z

Part of it was you didn't use help about to get environment info so the rc2 jumped out at me.

amaiorano · 2019-01-11T18:16:08Z

Looks like it must be failing in GitModule.GetRemotes here:

                        if (!fetchMatch.Success || !pushMatch.Success || fetchMatch.Groups["direction"].Value != "fetch" || pushMatch.Groups["direction"].Value != "push")
                        {
                            throw new Exception("Unable to parse git command output.");
                        }

This code expects to match this regex on the result of 'git remote -v':

private static readonly Regex _remoteVerboseLineRegex = new Regex(@"^(?<name>[^	]+)\t(?<url>.+?) \((?<direction>fetch|push)\)$", RegexOptions.Compiled);

@fabvit could you also share the result of running git remote -v in bash (Ctrl+G from your remote)?

fabvit · 2019-01-13T09:51:03Z

@amaiorano , thank to your hint I found the cause of my issue.:

$ git remote -v
all     git@gitlab.com:tiger/my_project.git (fetch)
all     git@gitlab.com:tiger/my_project.git (push)
all     ssh://git@bitbucket.org/tiger/my_project.git (push)
gitlab  git@gitlab.com:tiger/my_project.git (fetch)
gitlab  git@gitlab.com:tiger/my_project.git (push)
origin  ssh://git@bitbucket.org/tiger/my_project.git (fetch)
origin  ssh://git@bitbucket.org/tiger/my_project.git (push)

I then removed the [remote "all"] section, and magically the exception disappeared. So I turned on left panel, done a refresh and the exception neve happened again.

P.S. The [remote "gitlab"] was put in the config as a way to perform a single command push instead of three separate pushes to:

git@gitlab.com
git@gitlab.com
git@bitbucket.org

fabvit · 2019-01-13T09:52:14Z

@gerhardol finnally I figured how to obtain the stack trace:

   at GitCommands.GitModule.<GetRemotes>g__ParseRemotes|154_0(IEnumerable`1 lines)
   at GitCommands.GitModule.GetRemotes()
   at GitUI.BranchTreePanel.RepoObjectsTree.RemoteBranchTree.<LoadNodesAsync>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at GitUI.BranchTreePanel.RepoObjectsTree.Tree.<ReloadAsync>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at GitUI.BranchTreePanel.RepoObjectsTree.<ReloadAsync>d__36.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at GitUI.BranchTreePanel.RepoObjectsTree.<ReloadAsync>d__36.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at GitUI.ThreadHelper.<>c__DisplayClass13_0.<<FileAndForget>b__0>d.MoveNext()

RussKie · 2019-01-13T10:18:41Z

Should we swallow the exception and ignore the error? Warn the the user of a problem?

…

On Sun, Jan 13, 2019, 8:52 PM fabvit ***@***.*** wrote: @gerhardol <https://github.com/gerhardol> finnally I figured how to obtain the stack trace: at GitCommands.GitModule.g__ParseRemotes|154_0(IEnumerable`1 lines) at GitCommands.GitModule.GetRemotes() at GitUI.BranchTreePanel.RepoObjectsTree.RemoteBranchTree.d__1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GitUI.BranchTreePanel.RepoObjectsTree.Tree.d__14.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GitUI.BranchTreePanel.RepoObjectsTree.d__36.MoveNext() --- End of stack trace from previous location where exception was thrown --- at GitUI.BranchTreePanel.RepoObjectsTree.d__36.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at GitUI.ThreadHelper.<>c__DisplayClass13_0.<b__0>d.MoveNext() — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6093 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEMyXp0tAKaxz1RhiA-Pyzih7Rr680LEks5vCwHRgaJpZM4Z7pYM> .

amaiorano · 2019-01-14T18:06:00Z

I'm not sure I understood the problem, exactly. Was it that there were two remotes pointing to the same thing?

gerhardol · 2019-01-14T21:16:14Z

Duplicate of #5943 - closed though

Suggest this is handled as a bug:

Use first remote if more than one
Report to user once per repo (need to be stored somehow). It is better to have a popup when using than a crash though...

Enhancement: Handle multiple (auto name, activate/deactivate must be handled)

RussKie · 2019-01-15T11:13:58Z

Reopening since this would be good to fix

SailorMax · 2019-02-23T14:56:37Z

Crash on startup.
GitExtensions.exe [3.1.0.5342]

System.Exception: Remote URLs should appear in pairs.
Target Site: System.Collections.Generic.IReadOnlyList`1[GitCommands.Remote] <GetRemotes>g__ParseRemotes|153_0(System.Collections.Generic.IEnumerable`1[System.String]) @ GitCommands.GitModule
CLR: 4.0.30319.42000
HResult: -2146233088

escherstair · 2019-03-08T08:08:53Z

I see this error with the following environment

Git Extensions 3.0.2.5232
Build 23b6f51
Git 2.21.0.windows.1
Microsoft Windows NT 6.1.7601 Service Pack 1
.NET Framework 4.7.3130.0
DPI 96dpi (no scaling)

This happens when my repo has submodules (which have remotes) but it doesn't have a remote itself.
After I add a remote for the main repo (through git command line) everything is ok.

vbjay · 2019-03-08T13:14:48Z

Show your git config showing the remotes.

…

On Fri, Mar 8, 2019, 3:08 AM escherstair ***@***.***> wrote: I see this error with the following environment - Git Extensions 3.0.2.5232 - Build 23b6f51 <23b6f51> - Git 2.21.0.windows.1 - Microsoft Windows NT 6.1.7601 Service Pack 1 - .NET Framework 4.7.3130.0 - DPI 96dpi (no scaling) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6093 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADdhsQZjR7SAkgg8-L9_8o4CcockuWyhks5vUhqYgaJpZM4Z7pYM> .

escherstair · 2019-03-08T13:33:28Z

Is this a question?
Which git config?
Either the one of the main repo (but it doesn't have remote when the issue happens), or those of submodules?

vbjay · 2019-03-08T13:39:22Z

Open a repo that exhibits this error. In console run git config --list

…

On Fri, Mar 8, 2019, 8:33 AM escherstair ***@***.***> wrote: Is this a question? Which git config? Either the one of the main repo (but it doesn't have remote when the issue happens), or those of submodules? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6093 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADdhsYGLQf7CevlIHdS2laXqOTjURbHKks5vUmargaJpZM4Z7pYM> .

escherstair · 2019-03-08T13:56:32Z

In the meanwhile I fixed the error (adding the remote).
I'll do what you suggest the next time I create a new repo with submodules

escherstair · 2019-03-19T08:46:04Z

git remote -v

origin

fsfod · 2019-03-21T03:28:40Z

I don't know how much helps but i bisected this issue for for my case at least to this commit c9e47e4 from pull request #5669. I have the same problem as closed as duplicate issue and i have "Open with last working directory" off.

Also this is the call stack that starting the task thats calling GitModule.GetRemotes

GitUI.dll!GitUI.BranchTreePanel.RepoObjectsTree.Tree.ReloadNodes({Method = {System.Reflection.RuntimeMethodInfo}}) Line 158	C#
GitUI.dll!GitUI.BranchTreePanel.RepoObjectsTree.BranchTree.RefreshTree() Line 203	C#
GitUI.dll!GitUI.BranchTreePanel.RepoObjectsTree.AddTree({GitUI.BranchTreePanel.RepoObjectsTree.BranchTree}) Line 254	C#
GitUI.dll!GitUI.BranchTreePanel.RepoObjectsTree.OnUICommandsSourceSet({GitUI.CommandsDialogs.FormBrowse}) Line 211	C#
GitUI.dll!GitUI.GitModuleControl.UICommandsSource.set({GitUI.CommandsDialogs.FormBrowse}) Line 83	C#
GitUI.dll!GitUI.GitModuleControl.UICommandsSource.get() Line 68	C#
GitUI.dll!GitUI.BranchTreePanel.RepoObjectsTree.Initialize({GitCommands.Git.AheadBehindDataProvider}, {GitUI.FilterBranchHelper}) Line 189	C#
GitUI.dll!GitUI.CommandsDialogs.FormBrowse.FormBrowse({GitUI.GitUICommands}, "", null) Line 185	C#
GitUI.dll!GitUI.GitUICommands.StartBrowseDialog(null, "", null) Line 1065	C#
GitExtensions.exe!GitExtensions.Program.RunApplication() Line 145	C#
GitExtensions.exe!GitExtensions.Program.Main() Line 68	C#

amaiorano · 2019-03-21T03:48:49Z

@fsfod Thank you for that, it's actually very helpful. I was able to reproduce this quite easily by just setting the working directory to a non-git directory, and launching our latest build in Debug.

The problem is that RepoObjectsTree.RemoteBranchTree.LoadNodesAsync is trying to read remotes from a GitModule that is effectively invalid -- it isn't initialized with an actual module. It fails when calling Module.GetRemotes(), which attempts to parse the output of "git remote -v", which in this case returns "fatal: not a git repository (or any of the parent directories): .git" as @mstv pointed out above.

There are a couple of possible fixes:

Make Module.GetRemotes robust against unexpected output, and have it simply return an empty list.
Have the left panel root tree nodes check if Module is "valid" before proceeding to try and populate themselves.

Personally, I would prefer the first option. I'll take a stab at that.

amaiorano · 2019-03-21T04:05:30Z

Please check out the fix in PR: #6390

fsfod · 2019-03-21T14:47:13Z

It fixed the issue but it looks like opening and closing the settings dialogue when no repo is open at the dashboard has the same issue of trying access non existent repository.

amaiorano · 2019-03-21T14:51:00Z

It fixed the issue but it looks like opening and closing the settings dialogue when no repo is open at the dashboard has the same issue of trying access non existent repository.

Hmm, I'll take a look. In fact, my change is making one of our tests fail, and I'm still considering the right way to approach this.

amaiorano · 2019-03-21T16:02:42Z

I pushed more fixes. It's working now even with open then close of Settings on a non-repo.

mstv · 2019-04-29T21:26:59Z

@RussKie, why did you reopen this issue a month ago?

RussKie · 2019-04-29T21:52:02Z

I can't recall.

RussKie · 2019-05-14T22:08:30Z

This is still not fixed

RussKie · 2019-05-14T22:35:46Z

#6562 #6563

ojchase · 2019-05-15T01:37:52Z

Yep, not fixed. I'm now hitting it just by launching Git Extensions after upgrading to the latest version. All was fine before upgrading. Now launch the application and identical to 6562/6563.

RussKie · 2019-05-15T03:05:45Z

Could you please share the results of `git remote -v`

…

On Wed, May 15, 2019, 11:37 AM ojchase ***@***.***> wrote: Yep, not fixed. I'm now hitting it just by launching Git Extensions after upgrading to the latest version. All was fine before upgrading. Now launch the application and identical to 6562/6563. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#6093?email_source=notifications&email_token=ABBTEXS5AEZ6WU6EL6NYBCLPVNSPLA5CNFSM4GPOSYGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVNIGRA#issuecomment-492471108>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABBTEXSQC7CMAOUKCW4PTODPVNSPLANCNFSM4GPOSYGA> .

ojchase · 2019-05-15T13:53:02Z

Not a lot of point as I'm not in a repository. The only difference between me and ideaalab on 3/18 is that I'm not on the portable version.

jacekprofisoft · 2019-05-20T08:41:12Z

I can confirm that bug exists in 3.1. Prior to that hiding left panel prevents from throwing exception, but in 3.1 this workaround don't work and exception is raised every time I open affected repository even if left panel is hidden.

Current behaviour

Exception is thrown when opening repository which has remote repository with more than one push url.

Expected behaviour

Exception should not be thrown.

Steps to reproduce

Create new (personal) repository and do initial commit. Let's call it 'Test'.
Clone 'Test' repo, assume it is 'TestA'
Once again clone 'Test', assume it is 'TestB'
Open 'TestA' in Git Extensions and go to Git Console
Make sure 'Test' is set as 'origin' remote repository by doing: git remote -v
Add another push 'origin' url to 'TestB' by executing: git remote set-url --add origin /path/to/TestB
Verify that you now have two 'origin' push urls by doing: git remote -v
Reload 'TestA' in Git Extensions - exception should be thrown
Dissmising exception dialog closes GE

Error Details

System.Exception: Remote URLs should appear in pairs.
   w GitCommands.GitModule.<GetRemotesAsync>g__ParseRemotes|155_0(IEnumerable`1 lines)
   w GitCommands.GitModule.<GetRemotesAsync>d__155.MoveNext()
--- Koniec śladu stosu z poprzedniej lokalizacji, w której wystąpił wyjątek ---
   w System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   w System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   w GitUI.BranchTreePanel.RepoObjectsTree.RemoteBranchTree.<LoadNodesAsync>d__4.MoveNext()
--- Koniec śladu stosu z poprzedniej lokalizacji, w której wystąpił wyjątek ---
   w System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   w System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   w GitUI.BranchTreePanel.RepoObjectsTree.Tree.<ReloadNodesAsync>d__27.MoveNext()
--- Koniec śladu stosu z poprzedniej lokalizacji, w której wystąpił wyjątek ---
   w System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   w System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   w GitUI.BranchTreePanel.RepoObjectsTree.Tree.<<UICommands_PostRepositoryChanged>b__6_0>d.MoveNext()
--- Koniec śladu stosu z poprzedniej lokalizacji, w której wystąpił wyjątek ---
   w System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   w System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   w GitUI.ThreadHelper.<>c__DisplayClass13_0.<<FileAndForget>b__0>d.MoveNext()

Environment

Git Extensions 3.1.0.5877
Build bb1687f
Git 2.20.1.windows.1
Microsoft Windows NT 10.0.17763.0
.NET Framework 4.7.3416.0
DPI 96dpi (no scaling)

RussKie · 2019-05-20T13:35:59Z

Fixed in #6580

gerhardol mentioned this issue Jan 12, 2019

NBug and other assemblies reports 3.00.rc2 #6096

Closed

fabvit closed this as completed Jan 13, 2019

RussKie reopened this Jan 15, 2019

RussKie added type: bug 🐛 up-for-grabs Easy tasks for those looking to get involved. Refer to https://up-for-grabs.net/ status: workaround available labels Jan 15, 2019

This was referenced Jan 15, 2019

Fix AE: Can not add a section that already exists: -remote #6111

Merged

Error and crash when using multiple remotes for a single branch #5943

Closed

RussKie mentioned this issue Feb 25, 2019

Don't load avatars, if network is not available #6287

Merged

RussKie mentioned this issue Mar 6, 2019

Performance degradation in 3.0+ #6267

Closed

amaiorano mentioned this issue Mar 21, 2019

Fix exception thrown GitModule.GetRemotes on an invalid git directory #6390

Merged

ghost assigned amaiorano Mar 21, 2019

ghost added the status: ready label Mar 21, 2019

amaiorano closed this as completed in #6390 Mar 24, 2019

ghost removed the status: ready label Mar 24, 2019

RussKie reopened this Mar 24, 2019

RussKie closed this as completed Apr 29, 2019

RussKie added this to the 3.1.0 milestone Apr 29, 2019

RussKie reopened this May 14, 2019

RussKie modified the milestones: 3.1.0, 3.1.1 May 14, 2019

RussKie closed this as completed May 20, 2019

gerhardol mentioned this issue Jul 14, 2019

[NBug] Remote URLs should appear in pairs. #6922

Closed

gerhardol mentioned this issue Sep 19, 2019

[NBug] Unable to parse git command output. #7176

Closed

System.Exception opening an existing repository #6093

System.Exception opening an existing repository #6093

Comments

fabvit commented Jan 11, 2019 • edited by RussKie Loading

Current behaviour

Expected behaviour

Steps to reproduce

Screenshots

Did this work in previous version of GitExtensions

Environment

Diagnostics

vbjay commented Jan 11, 2019 via email

gerhardol commented Jan 11, 2019 • edited Loading

vbjay commented Jan 11, 2019

fabvit commented Jan 11, 2019 • edited Loading

vbjay commented Jan 11, 2019

gerhardol commented Jan 11, 2019

vbjay commented Jan 11, 2019

amaiorano commented Jan 11, 2019

fabvit commented Jan 13, 2019 • edited by RussKie Loading

fabvit commented Jan 13, 2019 • edited by RussKie Loading

RussKie commented Jan 13, 2019 via email

amaiorano commented Jan 14, 2019

gerhardol commented Jan 14, 2019

RussKie commented Jan 15, 2019

SailorMax commented Feb 23, 2019 • edited by RussKie Loading

escherstair commented Mar 8, 2019 • edited Loading

vbjay commented Mar 8, 2019 via email

escherstair commented Mar 8, 2019

vbjay commented Mar 8, 2019 via email

escherstair commented Mar 8, 2019

escherstair commented Mar 19, 2019

fsfod commented Mar 21, 2019

amaiorano commented Mar 21, 2019

amaiorano commented Mar 21, 2019

fsfod commented Mar 21, 2019

amaiorano commented Mar 21, 2019

amaiorano commented Mar 21, 2019

mstv commented Apr 29, 2019

RussKie commented Apr 29, 2019

RussKie commented May 14, 2019

RussKie commented May 14, 2019

ojchase commented May 15, 2019

RussKie commented May 15, 2019 via email

ojchase commented May 15, 2019

jacekprofisoft commented May 20, 2019 • edited Loading

Current behaviour

Expected behaviour

Steps to reproduce

Error Details

Environment

RussKie commented May 20, 2019

fabvit commented Jan 11, 2019 •

edited by RussKie

Loading

gerhardol commented Jan 11, 2019 •

edited

Loading

fabvit commented Jan 11, 2019 •

edited

Loading

fabvit commented Jan 13, 2019 •

edited by RussKie

Loading

fabvit commented Jan 13, 2019 •

edited by RussKie

Loading

SailorMax commented Feb 23, 2019 •

edited by RussKie

Loading

escherstair commented Mar 8, 2019 •

edited

Loading

jacekprofisoft commented May 20, 2019 •

edited

Loading