Error when (only) Refreshing my local repository. Known bug?

Started by Yost67, February 04, 2024, 17:07:04 PM

Previous topic - Next topic


It seems like Refreshing a local repository generates an error if nothing changed locally...

Today I tried to refresh my repository after not working in Archi for 3 weeks. My Change History shows my last Commit/Publish at January 14th. After selecting Refresh Model from the Collaboration menu, I have to type in my password, after that Archi tries to login to the gitlab server and responds with an error.

I checked if my password was correct, if VPN was running and if I could access the gitlab server using its web interface. Everything works fine. I try to Refresh again, and get the connection error again. I do a Commit and Archi responds with "Nothing to Commit". I try to Refresh, and get the connection error.

Now I create a new view with one element. I Commit this change and it Commits. I Publish the change and Archi publishes the change to the central repository. But it also refreshes my local repository with the changes my colleagues made the last 3 weeks; my Change History now shows changes at January 25 and 26, before showing my change of today.

Is this a know bug? Or is something wrong in our server or local setup? Thanks for any insights.

Jean-Baptiste Sarrodie


Quote from: Yost67 on February 04, 2024, 17:07:04 PMIs this a know bug? Or is something wrong in our server or local setup?

I've never had this issue (nor any of my colleagues), so I assume the issue is on your overall setup.


If you value and use Archi, please consider making a donation!
Ask your ArchiMate related questions to the ArchiMate Community's Discussion Board.