eclipse-xtext / eclipse-xtext/xtext
Reading files in AA might lead to deadlock
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 831
- Forks
- 330
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 12
Description
I see deadlocks in the AA Processor for the template files when i do updates to fowler.ui on command line (or do a touch on all xtend and java files and restart eclipse + refresh)
i still dont complete understand the deadlock
Contributor guide
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 the attached jstack.txt and tracing the AA Processor while template files are updated from the command line. Reproduce the deadlock by touching the Xtend and Java files, restarting Eclipse, and refreshing; done means the deadlock is understood and the triggering file-reading path is corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100