TEN-framework / TEN-framework/ten-framework
If the app is not fully started, how to determine which extension did not call on_init_done/on_start_done as expected?
Open
Nobody has claimed this yet.
enhancement
ten-framework
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1.4k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 22
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the extension lifecycle around the on_init_done and on_start_done callbacks mentioned in the title. The issue provides no files, tests, or reproduction steps, so first identify the startup entry points and determine how the framework tracks extensions that have not completed initialization. Done means the specific extension can be identified when startup does not complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100