Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`process_orchestration` raises ValidationError of pydantic

Open
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

Trace process_orchestration handling of the orchestration response, focusing on authenticationInfo and the Pydantic validation shown in the report. Reproduce the null-value case and compare it with the empty-string case; done means a null optional authenticationInfo no longer raises ValidationError.

Written by the indexing model from the issue text.

Description

Hi, when I try to do orchestration of a service, I get a ValidationError of pydantic. When I debug the code step by step, I realize that authenticationInfo couldn't get from core service Orchestration. It's actually null in the database and this doesn't cause an error in Java client. However when I debug and I even change the provider value orchestration response as authenticationInfo = null, error continue. Finally, I changed the provider value of orchestration response as authenticationInfo = "" and it was fixed. Even provider authenticationInfo is nonrequired, process_orchestration raises error. I'm sharing debugging screenshots.

authenticationInfo is returned from core service Orchestration and there is no exception in Java client
java
authenticationInfo couldn't get from service Orchestration
python
authenticationInfo couldn't get from service Orchestration and error raised from pydantic like below
exception
authenticationInfo couldn't get from service Orchestration and I added it as null but error raised from pydantic like below,
python2

Dominant language
Python
Stars
5
Forks
12
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from arrowhead-f/client-library-python

All issues in arrowhead-f/client-library-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.