Re: Issues with Gradle 8.0-rc-5 on NB 17rc3

[Scott Palmer]

This does seem to be a real issue, so I've filed
https://github.com/apache/netbeans/issues/5485


On Mon, Feb 13, 2023 at 12:04 PM László Kishalmi 
wrote:

> As far as I've checked the git diff between 8.0-rc-1 and 8.0-rc-5 there is
> no change in the tooling parts.
>
> On Mon, Feb 13, 2023 at 7:06 AM Scott Palmer  wrote:
>
> >
> > > On Feb 13, 2023, at 9:16 AM, Neil C Smith 
> wrote:
> > >
> > > On Sat, 11 Feb 2023 at 22:44, Scott Palmer 
> wrote:
> > >>
> > >> Trying to run multiple gradle projects from the IDE and second one
> > failed.
> > >>
> > >> A org.gradle.tooling.GradleConnectionException has occurred.
> > >>
> > >> If you are running the latest 
> > version
> > >> of NetBeans you can report this
> > >> , including a copy of
> your
> > >> messages.log file as an attachment.
> > >
> > > Following that instruction would be useful! :-)
> >
> >  That would be my next step.. but I was going to do more to investigate
> > first.
> >
> > >
> > > Anything here that might cause pause for thought in progressing to
> > > release of 17?
> >
> > Sorry, I already replied to my original message, but the reply was
> blocked
> > by mailing list filters. Strange.
> >
> > The issue seems to have been related to a threading issue in my code. It
> > may have crashed the JVM (which also shouldn’t have happened, but that
> bug
> > is for someone else).  I’m going to confirm that with a smaller test case
> > and I’ll file an issue if it still seems relevant.
> >
> > At this time I don’t think it is something that should block NB 17.
> >
> > Cheers,
> >
> > Scott
> >
> > >
> > > Best wishes,
> > >
> > > Neil
> >
>

Re: Issues with Gradle 8.0-rc-5 on NB 17rc3

[László Kishalmi]

As far as I've checked the git diff between 8.0-rc-1 and 8.0-rc-5 there is
no change in the tooling parts.

On Mon, Feb 13, 2023 at 7:06 AM Scott Palmer  wrote:

>
> > On Feb 13, 2023, at 9:16 AM, Neil C Smith  wrote:
> >
> > On Sat, 11 Feb 2023 at 22:44, Scott Palmer  wrote:
> >>
> >> Trying to run multiple gradle projects from the IDE and second one
> failed.
> >>
> >> A org.gradle.tooling.GradleConnectionException has occurred.
> >>
> >> If you are running the latest 
> version
> >> of NetBeans you can report this
> >> , including a copy of your
> >> messages.log file as an attachment.
> >
> > Following that instruction would be useful! :-)
>
>  That would be my next step.. but I was going to do more to investigate
> first.
>
> >
> > Anything here that might cause pause for thought in progressing to
> > release of 17?
>
> Sorry, I already replied to my original message, but the reply was blocked
> by mailing list filters. Strange.
>
> The issue seems to have been related to a threading issue in my code. It
> may have crashed the JVM (which also shouldn’t have happened, but that bug
> is for someone else).  I’m going to confirm that with a smaller test case
> and I’ll file an issue if it still seems relevant.
>
> At this time I don’t think it is something that should block NB 17.
>
> Cheers,
>
> Scott
>
> >
> > Best wishes,
> >
> > Neil
>

Re: Issues with Gradle 8.0-rc-5 on NB 17rc3

[Scott Palmer]

> On Feb 13, 2023, at 9:16 AM, Neil C Smith  wrote:
> 
> On Sat, 11 Feb 2023 at 22:44, Scott Palmer  wrote:
>> 
>> Trying to run multiple gradle projects from the IDE and second one failed.
>> 
>> A org.gradle.tooling.GradleConnectionException has occurred.
>> 
>> If you are running the latest  version
>> of NetBeans you can report this
>> , including a copy of your
>> messages.log file as an attachment.
> 
> Following that instruction would be useful! :-)

 That would be my next step.. but I was going to do more to investigate first.

> 
> Anything here that might cause pause for thought in progressing to
> release of 17?

Sorry, I already replied to my original message, but the reply was blocked by 
mailing list filters. Strange.

The issue seems to have been related to a threading issue in my code. It may 
have crashed the JVM (which also shouldn’t have happened, but that bug is for 
someone else).  I’m going to confirm that with a smaller test case and I’ll 
file an issue if it still seems relevant.

At this time I don’t think it is something that should block NB 17.

Cheers,

Scott

> 
> Best wishes,
> 
> Neil

Re: Issues with Gradle 8.0-rc-5 on NB 17rc3

[Neil C Smith]

On Sat, 11 Feb 2023 at 22:44, Scott Palmer  wrote:
>
> Trying to run multiple gradle projects from the IDE and second one failed.
>
> A org.gradle.tooling.GradleConnectionException has occurred.
>
> If you are running the latest  version
> of NetBeans you can report this
> , including a copy of your
> messages.log file as an attachment.

Following that instruction would be useful! :-)

Anything here that might cause pause for thought in progressing to
release of 17?

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Issues with Gradle 8.0-rc-5 on NB 17rc3

[Scott Palmer]

Trying to run multiple gradle projects from the IDE and second one failed.

A org.gradle.tooling.GradleConnectionException has occurred.

If you are running the latest  version
of NetBeans you can report this
, including a copy of your
messages.log file as an attachment.

The messages.log file is located in this folder.

This exception was in messages.log:

SEVERE [global]
org.gradle.launcher.daemon.client.DaemonConnectionException: Timeout
waiting to connect to the Gradle daemon.
Daemon uid: a9f8350f-10e3-4d84-8ab4-19c2edcfb978 with diagnostics:
Daemon pid: 13657
  log file: /Users/scott/.gradle/daemon/8.0-rc-5/daemon-13657.out.log
- Last  20 lines from daemon log file - daemon-13657.out.log -
2023-02-11T17:26:16.409-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon
addresses registry.
2023-02-11T17:26:16.409-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon
addresses registry.
2023-02-11T17:26:26.400-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
shared lock on daemon addresses registry.
2023-02-11T17:26:26.400-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon
addresses registry.
2023-02-11T17:26:26.400-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon
addresses registry.
2023-02-11T17:26:26.401-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
shared lock on daemon addresses registry.
2023-02-11T17:26:26.401-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon
addresses registry.
2023-02-11T17:26:26.401-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon
addresses registry.
2023-02-11T17:26:26.401-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
shared lock on daemon addresses registry.
2023-02-11T17:26:26.402-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon
addresses registry.
2023-02-11T17:26:26.402-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon
addresses registry.
2023-02-11T17:26:36.403-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
shared lock on daemon addresses registry.
2023-02-11T17:26:36.403-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon
addresses registry.
2023-02-11T17:26:36.404-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon
addresses registry.
2023-02-11T17:26:36.404-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
shared lock on daemon addresses registry.
2023-02-11T17:26:36.404-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon
addresses registry.
2023-02-11T17:26:36.404-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon
addresses registry.
2023-02-11T17:26:36.404-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire
shared lock on daemon addresses registry.
2023-02-11T17:26:36.405-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon
addresses registry.
2023-02-11T17:26:36.405-0500 [DEBUG]
[org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon
addresses registry.
- End of the daemon log -

at
org.gradle.launcher.daemon.client.DefaultDaemonConnector.doStartDaemon(DefaultDaemonConnector.java:242)
at
org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(DefaultDaemonConnector.java:216)
at
org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:164)
at
org.gradle.launcher.daemon.client.DaemonClient.execute(DaemonClient.java:99)
at
org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:44)
at
org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(DaemonBuildActionExecuter.java:30)
at
org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:60)
at
org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(LoggingBridgingBuildActionExecuter.java:37)
at
org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:224)
at
org.gradle.tooling.internal.provider.ProviderConnection.run(ProviderConnection.java:150)
at
org.gradle.tooling.internal.provider.DefaultConnection.getModel(DefaultConnection.java:149)
at
org.gradle.tooling.internal.consumer.connection.CancellableModelBuilderBackedModelProducer.produceModel(CancellableModelBuilderBackedModelProducer.java:54)
at
org.gradle.tooling.internal.consumer.connection.PluginClasspathInjectionSupportedCheckModelProducer.produceModel(PluginClasspathInject