search

mingo-app / mingo

Found a bug? have a FR ?
59 stars 3 forks source link

App is showing collections twice #552

Closed dimadev01 closed 1 year ago

dimadev01 commented 1 year ago

CleanShot 2023-04-05 at 15 19 41

Version 1.11.1

Nothing special, just connected and voilá

Vallefor commented 1 year ago

Sometimes I have the same bug but not always.

tothradoslav commented 1 year ago

Thanks. And what happens when you click to refresh db? Do the duplicates disappear? I'm looking into the issue now.

dimarixsus commented 1 year ago

Thanks. And what happens when you click to refresh db? Do the duplicates disappear? I'm looking into the issue now.

Nope, they are still there after the refresh

tothradoslav commented 1 year ago

Seems like we have found the cause for this behaviour. A simple description of the problem:

We recommend the following steps to be taken:

  1. remove the problematic connection from Mingo (I know this is a pain and we are really sorry this, but we can't do a roll-back on this)
  2. install the patch
  3. add the connection again.

Sorry, again, for the problem caused :(

Please let us know if this worked for you. Link to the new release:

https://github.com/mingo-app/mingo/releases/tag/v1.12.1-rc1

dimadev01 commented 1 year ago

Seems like we have found the cause for this behaviour. A simple description of the problem:

  • each collection has a UUID identifier that is given by mongodb
  • these ids should be unique even when you copy or restore a collection
  • Mingo relied on these, but it turned out that they don't have to be unique all the time
  • we have now changed the way Mingo identifies collections and released a patch for this issue

We recommend the following steps to be taken:

  1. remove the problematic connection from Mingo (I know this is a pain and we are really sorry this, but we can't do a roll-back on this)
  2. install the patch
  3. add the connection again.

Sorry, again, for the problem caused :(

Please let us know if this worked for you. Link to the new release:

https://github.com/mingo-app/mingo/releases/tag/v1.12.1-rc1

Heyy, so good you found the solution! No worries about reinstalling it from my side! I love Mingo, I'm glad you found the bug!

dimadev01 commented 1 year ago

Seems like we have found the cause for this behaviour. A simple description of the problem:

  • each collection has a UUID identifier that is given by mongodb
  • these ids should be unique even when you copy or restore a collection
  • Mingo relied on these, but it turned out that they don't have to be unique all the time
  • we have now changed the way Mingo identifies collections and released a patch for this issue

We recommend the following steps to be taken:

  1. remove the problematic connection from Mingo (I know this is a pain and we are really sorry this, but we can't do a roll-back on this)
  2. install the patch
  3. add the connection again.

Sorry, again, for the problem caused :( Please let us know if this worked for you. Link to the new release: https://github.com/mingo-app/mingo/releases/tag/v1.12.1-rc1

Heyy, so good you found the solution! No worries about reinstalling it from my side! I love Mingo, I'm glad you found the bug!

It worked, thanks!