Folks, That's extremely awesome! Now I see what stacktrace cause future creation and who will gain the result and how.
Are there any chances to keep variable's values at original stacktrace? Will this work correctly in case of concurrent calls? for example, when more that one stacktrace will cause same async op. Will this feature guarantee that I see exactly that what caused this async, not one of possible? Cons. Is there any chances now to see the whole stacktrace starting from worker got a message from the queue? On Fri, Dec 14, 2018 at 6:53 PM Dmitriy Pavlov <dpav...@apache.org> wrote: > Looks cool, I will try > > пт, 14 дек. 2018 г. в 16:46, Павлухин Иван <vololo...@gmail.com>: > > > Hi Igniters, > > > > I would like to share with you that now it is possible to use IDEA > > async debugger for debugging Ignite futures. And we should thank Ivan > > Bessonov for that awesome contribution [1]. > > > > Most of your might be already familiar with async debugger in IDEA. > > For the rest I prepared two screenshots [2], [3]. We can see regular > > stacktrace on breakpoint hit in future completion callback which is > > extended with an additional stacktrace showing a path where the > > callback was installed. > > > > Thank you Ivan! > > > > [1] https://issues.apache.org/jira/browse/IGNITE-10475 > > [2] > > > https://gist.githubusercontent.com/pavlukhin/c8c7c6266eeab56048c31f5cdfb31d20/raw/bfe32b8c11a67ccc3bcbbb8b398e39a8a818cad6/adebug1.png > > [3] > > > https://gist.githubusercontent.com/pavlukhin/c8c7c6266eeab56048c31f5cdfb31d20/raw/bfe32b8c11a67ccc3bcbbb8b398e39a8a818cad6/adebug2.png > > > > -- > > Best regards, > > Ivan Pavlukhin > > >
