Sri Teja T
Sri Teja T
@VJag and I are brainstorming an approach for this. Moving to the next sprint for implementation
Had to put the implementation on hold due to some unplanned work. Carrying this over to the next sprint.
My intial approach: Introduce two methods to atClient: - isRemoteReset(): If the public key present in the LocalSecondary and the one on the RemoteSecondary are different the method throws an...
The implementation of solution for this is https://github.com/atsign-foundation/at_client_sdk/tree/reset_local_secondary. Currently testing this and discussing the validity of the approach with @VJag
I have an implementation ready in https://github.com/atsign-foundation/at_client_sdk/pull/1033. We need to discuss this in an arch call preferably. Will bring it up in the next arch call.
I was able to complete the fix and testing in PR68. The PR is being reviewed and this ticket will be closed once the PR has been merged.
Update from https://github.com/atsign-foundation/at_server/issues/964: We are currently enforcing toLowerCase in AtKey.fromString() and AtKey.toString(). Additionally, this will also be triggered from methods in AtClient where the conversion to lowercase will be logged...
Changes have been made in at_commons package concerning actively enforcing lowercase on AtKey. Once the at_commons package has been published and those changes have been consumed at_client, this ticket will...
The implementation is ready to be merged. Since this change affects a wide range of things, it is being thoroughly tested. Will be closed as soon as the changes are...
AtClient v3.0.55 has changes that actively enforce lower case on an AtKey. And this conversion is logged when the key or namespace of an AtKey contains uppercase characters so that...