discover_typeengine error handling
Open
- Dominant language
- Python
- Stars
- 1k
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Description
Per issue [#1615](https://github.com/blaze/blaze/issues/1615) on the main blaze repository, it appears that the error handling in discover_typeengine is causing some confusion issues. I'd be happy to look into fixing this and allow for some more robust error handling that could also resolve the issue on blaze.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading blaze issue #1615 and locating the discover_typeengine entry point in odo. Reproduce the confusing error-handling behavior described there, then define the expected robust behavior and verify it with focused coverage for the affected cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100