[
https://issues.apache.org/jira/browse/NETBEANS-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035075#comment-17035075
]
Czukowski commented on NETBEANS-3796:
-------------------------------------
I can say that I've tried to close NetBeans and do {{composer install}} after
some dependency changes in upstream and it updated without any issue, so it
looks like NetBeans does somehow interfere with the process (guess by reading
files that are being changed, which results in them being locked for a short
while). The issue is kind of random, it happens almost each time, but I don't
think the initial {{composer install}} will cause any issues since there are no
files in {{vendor}} yet, some dependencies must be updated (the more the
better). I guess in order to reproduce, it should suffice to clone some fairly
large repo from Github that has a {{composer.lock}} in it, checkout its earlier
commit since which the dependencies have changed a lot, then do {{composer
update}} from the console and see what happens. I'll try to find one and see if
I can reproduce the issue this way.
I also notice a huge I/O activity and CPU usage by NetBeans taking an entire
core whenever there is anything substantial going on in the project folder,
like phing build (files are being generated) or Composer or NPM installs.
During that time the overall NetBeans performance seems to be a little
degraded, but my project is very large so maybe that's to be expected, even
though sometimes the CPU activity continues for a very long time. I think it
might be an indication of the same background process that causes the issue
with Composer. I tried clicking "Profile the IDE" when that happens, but I
didn't understand much in the results that have turned up.
> Prevents composer from working
> ------------------------------
>
> Key: NETBEANS-3796
> URL: https://issues.apache.org/jira/browse/NETBEANS-3796
> Project: NetBeans
> Issue Type: Bug
> Affects Versions: 11.2
> Reporter: R
> Priority: Major
>
> Now that I've upgraded from NetBeans 8.2 to 11.2, I'm no longer able to run
> `composer update` or `composer require` (if NetBeans 11.2 is running); I get
> random errors like "Update failed (Could not delete..."
> My guess is that NetBeans 11.2 must be interfering with files in my
> `/home/vagrant/Code/myproject/vendor/` folder more than 8.2 did (even when
> there is no message about background scanning).
> Once I close NetBeans 11.2, composer works again.
> My computer is Windows 10, and I'm also running VirtualBox 6.1.2r135662
> [Vagrant 2.2.7, laravel/homestead (virtualbox, 9.2.0), Ubuntu 18.04.3 LTS].
> I use Git Bash on my Windows machine to ssh into Ubuntu using `vagrant ssh`,
> and there I'm using Composer version 1.9.3.
> Everything had worked fine with NetBeans 8.2, but I needed to upgrade to 11.2
> for PHP 7.4 support.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
