Midburn / Midburn/midburn-devops
Investigate Spark issues
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
review problems in spark which might indicate infrastructure problem and or problem in other related components like profiles (which spark depends on)
https://github.com/Midburn/spark/issues/653
https://github.com/Midburn/spark/issues/651
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 reading Spark issues 653 and 651, then trace the related profiles dependency mentioned in this issue. Reproduce or document the reported problems and compare them with the infrastructure configuration. Done means identifying whether each problem belongs to infrastructure, Spark, or profiles, with supporting evidence and follow-up scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- spark
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100