Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configKey is not well formed key #1570

Closed
sitaram-kalluri opened this issue Sep 20, 2023 · 1 comment · Fixed by #1622
Closed

configKey is not well formed key #1570

sitaram-kalluri opened this issue Sep 20, 2023 · 1 comment · Fixed by #1622
Assignees
Labels
bug Something isn't working

Comments

@sitaram-kalluri
Copy link
Member

sitaram-kalluri commented Sep 20, 2023

Describe the bug

With the changes in the PR: #1569, three functional tests are failing with below exception

  From verb response data:_60f74087-c688-4c1b-805f-bcb5fe10f12f@alice🛠:eb1042bf-89a1-48c9-8750-130f025c66d7
  
  pkam verb response data:success
  
  FormatException: Unexpected character (at character 1)
  error:null:Exception: configkey is not well-formed key

When adding an atSign to the block list, the list of atSigns are stored aganist the key "configKey" which is not a well formed key. "configKey" does not adhere to the key format specified for AtKeys.

Referring to the changes APKAM changes, and the process of retrieving the highest commitId within the enrolled namespaces, we achieve this by extracting the namespace from the key using AtKey.fromString(key).namespace. However, when the key "configKey" is encountered, this action triggers the mentioned error within AtKey.fromString because "configKey" does not conform to the valid AtKey format.

@sitaram-kalluri sitaram-kalluri added the bug Something isn't working label Sep 20, 2023
@gkc
Copy link
Contributor

gkc commented Sep 25, 2023

See also #1204

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants