Repeat crashing after "directory not empty" error about connect HOT 9 CLOSED

Hey @snarlysodboxer! We have just release v1.5.4 of Connect, which contains a fix for a similar issue. Could you let me know if that resolves your problem?

from connect.

Thank you for reporting this. I am pretty confident we have reproduced the problem and we are working on a fix. I'll let you know once it has been released.

from connect.

Hi @jpcoenen, looks like we'll also need to upgrade the connect-go-sdk version to be able to test against this new version. Hope to do that soon, I'll update.

from connect.

That should not have to be necessary. We generally try to keep Connect compatible with older versions of the SDK's. So if an older version of the SDK does not work with this version of Connect, we'd really like to know. Could you tell me what issue you are running into and with which version of the SDK that is?

from connect.

@jpcoenen it's version 1.4.0 of the sdk that had an error message, something about "need version 1.3.0 or higher, detected 1.2.0." - That's not verbatim, I don't have the error message in front of me at this time.

EDIT: updated the version of the SDK producing the error.

from connect.

@jpcoenen Here's the exact error: "need at least version 1.3.0 of Connect for this function, detected version 1.2.0 (or earlier). Please update your Connect server". This is happening even with the updated 1.4.0 version of the connect-sdk-go client, and with the 1password/connect-api:1.5.4 and 1password/connect-sync:1.5.4 docker images.

from connect.

@jpcoenen I believe I've nailed down the exact issue, and since it's not related to this issue, I submitted it as a new one: #40

from connect.

Still haven't been able to give this a good test, as there's now a third bug delineated here: #42. (First two fixed though!)

from connect.

This appears to be fixed with version 1.5.6. Thanks!

from connect.