Skip to content

Conversation

@dodo920306
Copy link
Contributor

When serializers validate data, it compares them with the existing data in the DB for unique columns. Since agent lists are extracted from the DB, such validations will fail definitely. Thus, for getting data, the agent list in the response will skip for validation.

When serializers validate data, it compares them with the existing
data in the DB for unique columns. Since agent lists are extracted
from the DB, such validations will fail definitely. Thus, for getting
data, the agent list in the response will skip for validation.

Signed-off-by: dodo920306 <[email protected]>
YoungHypo
YoungHypo previously approved these changes Jul 15, 2025
@dodo920306 dodo920306 marked this pull request as draft July 15, 2025 13:37
@dodo920306
Copy link
Contributor Author

I want to figure out something first, so please don't merge this.

@dodo920306
Copy link
Contributor Author

@yeasy @YoungHypo Should agents actually be allowed to have the same name?
If there are 2 organizations naming their agents the same, they should be allowed to do it, right?

@yeasy
Copy link
Contributor

yeasy commented Jul 19, 2025

Agents will be in different namespaces based on the org. So one org cannot have two agents with the same name.

@dodo920306 dodo920306 marked this pull request as ready for review July 29, 2025 11:21
This reverts commit 849e071.

Signed-off-by: dodo920306 <[email protected]>
Agents don't have to be given different names.
They will work under their own organization respectively, so
it's unnecessary to restrict their name duplication.

Signed-off-by: dodo920306 <[email protected]>
@dodo920306 dodo920306 force-pushed the fix/unable-to-pass-validation-for-agent-list branch from f5753c9 to 6690d89 Compare July 29, 2025 11:26
@dodo920306
Copy link
Contributor Author

Agents will be in different namespaces based on the org. So one org cannot have two agents with the same name.

One organization can't have multiple agents, so in the end, there is no need to keep agent names unique.

@yeasy yeasy merged commit fb76cb9 into hyperledger-cello:main Jul 30, 2025
3 checks passed
@dodo920306 dodo920306 changed the title Stop validating agent lists Fix fail to access the agent list Jul 31, 2025
@dodo920306 dodo920306 deleted the fix/unable-to-pass-validation-for-agent-list branch July 31, 2025 04:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants