[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laszlo Kishalmi updated NETBEANS-168: - Labels: ca_survey (was: ca_survey pull-request-available) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 3.5h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated NETBEANS-168: Labels: ca_survey pull-request-available (was: ca_survey) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-168: Priority: Blocker (was: Critical) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John McDonnell updated NETBEANS-168: Component/s: projects - Gradle > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - > Execution, projects - Gradle >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h 20m > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John McDonnell updated NETBEANS-168: Component/s: (was: projects - Gradle) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Blocker > Labels: ca_survey, pull-request-available > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > Time Spent: 2h 20m > Remaining Estimate: 0h > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-168: Attachment: messages.log > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages.log > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-168: Attachment: ui.log > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages.log, ui.log > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-168: Attachment: uigestures 10.0 vc messages 10.0 vc2.log > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, Next > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiří Kovalský updated NETBEANS-168: --- Affects Version/s: (was: Next) 10.0 9.0 > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiří Kovalský updated NETBEANS-168: --- Labels: ca_survey (was: ) > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures > 10.0 vc > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-168: Attachment: wp-dms.7z puls.7z > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: messages 10.0 vc2.log, messages.log, puls.7z, ui.log, > uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-168: Attachment: messages - 10.0 vc3.log > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: messages - 10.0 vc3.log, messages 10.0 vc2.log, > messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[jira] [Updated] (NETBEANS-168) Background scanning process needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Lenz updated NETBEANS-168: Attachment: go-to-file.gif > Background scanning process needs a rethink > --- > > Key: NETBEANS-168 > URL: https://issues.apache.org/jira/browse/NETBEANS-168 > Project: NetBeans > Issue Type: Bug > Components: ide - Performance, java - Platform, platform - Execution >Affects Versions: 8.2, 9.0, 10.0 > Environment: NetBeans 8.2, Windows 10 x64 >Reporter: Christian Lenz >Priority: Critical > Labels: ca_survey > Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 > vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z > > > Often, while cloning, switching branch, merging, opening etc. etc. NetBeans > starts Background scanning for changes, but it is not real background, > because everything what you want to do then, like changing the branch, > commit, push, pull, open project, delete or whatever, is blocking by this > task and you can't cancel it, because it is essential. > Either we need to rethink about this process like to make everything or most > of the stuff doing things in parallel or the task should really be > cancelable. It is a pain in the ass for big projects when they start to scan > for changes. > It is a real world case because you acan see it when you work on NetBeans > modules. > Cheers > Chris -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
