Re: [PR] Scheduler needs to include acker memory for topology resources (storm)

[Bipin Prasad]

 Created Jira for Infrastructure group : 
https://issues.apache.org/jira/browse/INFRA-25692
On Friday, April 5, 2024 at 10:45:00 AM CDT, agresch (via GitHub) 
 wrote:  
 
 
agresch commented on PR #3633:
URL: https://github.com/apache/storm/pull/3633#issuecomment-2040131535

  @rzo1 - Storm JIRA is not taking my password for some reason.  I asked to 
reset it and received this email.  I am not sure how to get access to JIRA 
again based on this message.  Any thoughts?
  
    This user account is managed in an external User Directory and Jira is not 
able to update your password.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

  

Re: [VOTE] Move Storm from JIRA to GitHub issues

[Bipin Prasad]

 +1
On Wednesday, February 28, 2024 at 02:42:21 PM CST, Richard Zowalla 
 wrote:  
 
 +1

Am Mittwoch, dem 28.02.2024 um 09:08 + schrieb Julien Nioche:
> Hi,
> 
> Following the discussion initiated by Richard [1], please vote on
> moving
> Storm from JIRA to GitHub issues
> 
> The vote is open for at least the next 72 hours or as long as needed.
> 
> [ ] +1 Move Storm from JIRA to GitHub issues
> [ ]  0 No opinion
> [ ] -1 Keep the issues on JIRA
> 
> Here is my +1
> 
> Thanks
> 
> Julien
> 
> [1] https://lists.apache.org/thread/ty80h0kqfh2r7vh6wmzmhzh07njbq0jn

  

Re: [Discuss] Move Storm from JIRA to GitHub Issues

[Bipin Prasad]

 (1) Because of tighter integration with code, I think it will be better to 
move to github issues.If we run into any limitations we can ask github to 
implement.
(2) For storm, we will have to change some of the release tools/scripts that 
pull jiras and related PRs that will need to be changed to do the "right thing" 
in the github issues case.
--Bipin
On Monday, February 26, 2024 at 08:09:22 AM CST, Richard Zowalla 
 wrote:  
 
 Any additional thoughts?

Am Donnerstag, dem 22.02.2024 um 12:21 +0100 schrieb Alexandre
Vermeerbergen:
> +1 I agree that JIRA is overkill for the simple needs of incidents /
> enhancements tracking of Apache Storm
> 
> Alexandre
> 
> Le jeu. 22 févr. 2024 à 12:18, Richard Zowalla  a
> écrit :
> > 
> > Hi all,
> > 
> > The ASF JIRA instance no longer allows users to self-sign-up
> > (though it
> > DOES allow us to invite others). This is largely due to spam.
> > Most developers have a GitHub account (and that is where most folks
> > interact with Storm's code base), and this would meet folks where
> > they
> > are, as opposed to making them go somewhere else to dig through
> > issues.
> > 
> > Tentative suggestion:
> > 
> > * Go through existing Storm JIRA issues and close any issues that
> > are
> > no longer relevant.
> > * Migrate open issues to GitHub Issues in apache/storm (linking
> > back to
> > the
> > JIRA issue)
> > * All new issues will only be created in GitHub Issues
> > * When an existing JIRA issue is fixed, it will be updated in both
> > locations
> > * Make JIRA read-only for normal users
> > 
> > Potential process changes:
> > * Release notes/change logs are currently generated through JIRA.
> > We
> > would need to change that.
> > 
> > NOTE: This is not final; the above text is just to start the
> > discussion.
> > 
> > Feel free to pick holes in the above, suggest changes, or propose
> > something else!
> > 
> > Thoughts and feedback are welcome!
> > Richard

  

Re: get blob meta exception

[Bipin Prasad]

These are EC2 instances? Or is Storm running in AWS EKS? Socket timeout is 
generally 60 seconds, but can you verify from your log timestamps to infer what 
your socket timeout might be.


Sent from Yahoo Mail for iPhone


On Friday, January 19, 2024, 12:45 PM, Devendar Rao  
wrote:

The size of the jar is 270M. We've 19 topologies each with 270M jar size.
Yes, we use AWS EBS volumes for supervisors and Nimbus uses the local
Nvme(instance store).

Do you think increasing this topology.max.replication.wait.time.sec would
help?

On Fri, Jan 19, 2024 at 12:29 PM Bipin Prasad
 wrote:

> What is the size of the blob (the larger is probably the jar). The
> download time would depend on the network speed. Also noticed the name was
> f the mounted file system as ephemeral. These are not persistent storage?
> How about on the nimbus?
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Friday, January 19, 2024, 12:24 PM, Devendar Rao <
> devendar.gu...@gmail.com> wrote:
>
> We also see these warnings during the issue. Are there any settings which
> controls the availability of these files.
>
> Is there a setting which controls the wokrer to to keep in wait till the
> required files are available?
>
> Do we need to increase the value for this setting -
> topology.max.replication.wait.time.sec?
> It's set to 60 Sec now.
> 2024-01-18 11:37:08.328 o.a.s.l.AsyncLocalizer SLOT_6700 [WARN] Local base
> blobs are not available. java.io.FileNotFoundException: File
> '/mnt/ephermal0
> /data/storm/supervisor/stormdist/topology_A-15-1704896815/stormconf.ser'
> does not exist at org.apache.storm.shade.org.apache.commons.io.FileUtils.
> openInputStream(FileUtils.java:297) ~[storm-shaded-deps-2.3.0.jar:2.3.0] at
> org.apache.storm.shade.org
> .apache.commons.io.FileUtils.readFileToByteArray(
> FileUtils.java:1851) ~[storm-shaded-deps-2.3.0.jar:2.3.0] at org.apache.
> storm.utils.ConfigUtils.readSupervisorStormConfGivenPath(ConfigUtils.java:
> 311) ~[storm-client-2.3.0.jar:2.3.0] at org.apache.storm.utils.ConfigUtils.
> readSupervisorStormConfImpl(ConfigUtils.java:478)
> ~[storm-client-2.3.0.jar:2
> .3.0] at org.apache.storm.utils.ConfigUtils.readSupervisorStormConf(
> ConfigUtils.java:306) ~[storm-client-2.3.0.jar:2.3.0] at org.apache.storm.
> localizer.AsyncLocalizer.getLocalResources(AsyncLocalizer.java:368)
> ~[storm-
> server-2.3.0.jar:2.3.0] at org.apache.storm.localizer.AsyncLocalizer.
> releaseSlotFor(AsyncLocalizer.java:475) [storm-server-2.3.0.jar:2.3.0] at
> org.apache.storm.daemon.supervisor.Slot.handleWaitingForBlobLocalization(
> Slot.java:410) [storm-server-2.3.0.jar:2.3.0] at org.apache.storm.daemon.
> supervisor.Slot.stateMachineStep(Slot.java:192)
> [storm-server-2.3.0.jar:2.3.
> 0] at org.apache.storm.daemon.supervisor.Slot.run(Slot.java:941) [storm-
> server-2.3.0.jar:2.3.0]
>
>
> On Thu, Jan 18, 2024 at 1:28 PM Devendar Rao 
> wrote:
>
> > Hi Bipin,
> >
> > There are no disk space issues on the nimbus host. We also see this
> > exception. I think this is the effect not the cause. Not completely sure
> > though.
> >
> > 2024-01-18 11:47:16.018 o.a.s.t.ProcessFunction pool-29-thread-60 [ERROR]
> > Internal error processing beginBlobDownload
> > java.lang.RuntimeException: java.lang.RuntimeException:
> > java.lang.RuntimeException:
> > org.apache.storm.thrift.transport.TTransportException:
> > java.net.SocketTimeoutException: Read timed out
> > at
> > org.apache.storm.daemon.nimbus.Nimbus.beginBlobDownload(Nimbus.java:3860)
> > ~[storm-server-2.3.0.jar:2.3.0]
> > at
> >
> org.apache.storm.generated.Nimbus$Processor$beginBlobDownload.getResult(Nimbus.java:4340)
> > ~[storm-client-2.3.0.jar:2.3.0]
> > at
> >
> org.apache.storm.generated.Nimbus$Processor$beginBlobDownload.getResult(Nimbus.java:4319)
> > ~[storm-client-2.3.0.jar:2.3.0]
> > at
> > org.apache.storm.thrift.ProcessFunction.process(ProcessFunction.java:38)
> > [storm-shaded-deps-2.3.0.jar:2.3.0]
> > at org.apache.storm.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
> > [storm-shaded-deps-2.3.0.jar:2.3.0]
> > at
> >
> org.apache.storm.security.auth.SimpleTransportPlugin$SimpleWrapProcessor.process(SimpleTransportPlugin.java:172)
> > [storm-client-2.3.0.jar:2.3.0]
> > at
> >
> org.apache.storm.thrift.server.AbstractNonblockingServer$FrameBuffer.invoke(AbstractNonblockingServer.java:524)
> > [storm-shaded-deps-2.3.0.jar:2.3.0]
> > at org.apache.storm.thrift.server.Invocation.run(Invocation.java:18)
> > [storm-shaded-deps-2.3.0.jar:2.3.0]
> > at
> >
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> > [?

Re: get blob meta exception

[Bipin Prasad]

> at
> org.apache.storm.thrift.TServiceClient.receiveBase(TServiceClient.java:77)
> ~[storm-shaded-deps-2.3.0.jar:2.3.0]
> at
> org.apache.storm.generated.Nimbus$Client.recv_createStateInZookeeper(Nimbus.java:1036)
> ~[storm-client-2.3.0.jar:2.3.0]
> at
> org.apache.storm.generated.Nimbus$Client.createStateInZookeeper(Nimbus.java:1023)
> ~[storm-client-2.3.0.jar:2.3.0]
> at
> org.apache.storm.blobstore.NimbusBlobStore.createStateInZookeeper(NimbusBlobStore.java:136)
> ~[storm-client-2.3.0.jar:2.3.0]
> at
> org.apache.storm.blobstore.BlobStoreUtils.createStateInZookeeper(BlobStoreUtils.java:240)
> ~[storm-server-2.3.0.jar:2.3.0]
> at
> org.apache.storm.blobstore.BlobStoreUtils.updateKeyForBlobStore(BlobStoreUtils.java:277)
> ~[storm-server-2.3.0.jar:2.3.0]
> at
> org.apache.storm.blobstore.LocalFsBlobStore.checkForBlobUpdate(LocalFsBlobStore.java:469)
> ~[storm-server-2.3.0.jar:2.3.0]
> at
> org.apache.storm.blobstore.LocalFsBlobStore.getBlob(LocalFsBlobStore.java:389)
> ~[storm-server-2.3.0.jar:2.3.0]
> at
> org.apache.storm.daemon.nimbus.Nimbus.beginBlobDownload(Nimbus.java:3845)
> ~[storm-server-2.3.0.jar:2.3.0]
> ... 10 more
>
> On Thu, Jan 18, 2024 at 12:25 PM Bipin Prasad
>  wrote:
>
>> Hello Devender,  The zookeeper entry is expected to be removed when the
>> topology is killed. It appears that you are using local file store blob. So
>> the blobs are (expected to be) on the nimbus. Can you check the mailbox
>> directory and confirm whether or not the blob for this topology made it
>> that far? It is possible that there is some issue with disk space on the
>> nimbus host?
>> —Bipin
>>
>>
>> Sent from Yahoo Mail for iPhone
>>
>>
>> On Thursday, January 18, 2024, 11:39 AM, Devendar Rao <
>> devendar.gu...@gmail.com> wrote:
>>
>> Thanks Bipin for the response. To add more details:
>> Whenever a new topology is deployed nimbus doesn't respond and
>> supervisor(s) go down. We have to restart the services to bring the cluster
>> back to normal.
>> Another error we see: o.a.s.b.BlobStoreUtils BLOB-STORE-TIMER [ERROR]
>> Could not download the blob with key: topology_B-7-1704896101-stormjar.jar
>> There is a stale entry in the zk path:
>> /storm/blobstore/topology_B-7-1704896101-stormjar.jar. Not sure why it was
>> not getting cleared off. This is pretty consistent.
>> This error goes away after manually deleting stale entry from zk path:
>> rmr /storm/blobstore/topology_B-7-1704896101-stormjar.jar
>> Thanks,Devendar
>>
>>
>> On Thu, Jan 18, 2024 at 11:28 AM Devendar Rao 
>> wrote:
>>
>> Full stack trace:
>> 2024-01-18 18:27:12.889 o.a.s.d.n.Nimbus pool-29-thread-22 [WARN] get
>> blob meta exception.org.apache.storm.utils.WrappedKeyNotFoundException:
>> topology-A-7-1704896101-stormjar.jar at
>> org.apache.storm.blobstore.LocalFsBlobStore.getStoredBlobMeta(LocalFsBlobStore.java:258)
>> ~[storm-server-2.3.0.jar:2.3.0] at
>> org.apache.storm.blobstore.LocalFsBlobStore.getBlobMeta(LocalFsBlobStore.java:288)
>> ~[storm-server-2.3.0.jar:2.3.0] at
>> org.apache.storm.daemon.nimbus.Nimbus.getBlobMeta(Nimbus.java:3815)
>> [storm-server-2.3.0.jar:2.3.0] at
>> org.apache.storm.generated.Nimbus$Processor$getBlobMeta.getResult(Nimbus.java:4278)
>> [storm-client-2.3.0.jar:2.3.0] at
>> org.apache.storm.generated.Nimbus$Processor$getBlobMeta.getResult(Nimbus.java:4257)
>> [storm-client-2.3.0.jar:2.3.0] at
>> org.apache.storm.thrift.ProcessFunction.process(ProcessFunction.java:38)
>> [storm-shaded-deps-2.3.0.jar:2.3.0] at
>> org.apache.storm.thrift.TBaseProcessor.process(TBaseProcessor.java:38)
>> [storm-shaded-deps-2.3.0.jar:2.3.0] at
>> org.apache.storm.security.auth.SimpleTransportPlugin$SimpleWrapProcessor.process(SimpleTransportPlugin.java:172)
>> [storm-client-2.3.0.jar:2.3.0] at
>> org.apache.storm.thrift.server.AbstractNonblockingServer$FrameBuffer.invoke(AbstractNonblockingServer.java:524)
>> [storm-shaded-deps-2.3.0.jar:2.3.0] at
>> org.apache.storm.thrift.server.Invocation.run(Invocation.java:18)
>> [storm-shaded-deps-2.3.0.jar:2.3.0] at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>> [?:?] at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>> [?:?] at java.lang.Thread.run(Thread.java:834) [?:?]
>>
>> On Thu, Jan 18, 2024 at 11:26 AM Bipin Prasad 
>> 
>> wrote:
>>
>> Can you post the full stack trace? I want to confirm that this is logged
>> while trying to obtain the heartbeat.This message is a warning message and
>> is not expected to shutdown nimbus.
>>
>>
>> Sent from Yahoo Mail for iPhone
>>
>>
>> On Thursday, January 18, 2024, 11:19 AM, Devendar Rao <
>> devendar.gu...@gmail.com> wrote:
>>
>> Hi,
>> We're constantly seeing issues in storm 2.3.0 with blobs with each
>> topology deployment. Supervisor/nimbus dies after seeing the below
>> exceptions.
>> Is this a known issue? Are we hitting any blob cache size limits?
>> Exceptions:
>> "Could not download the blob with key:"
>> o.a.s.d.n.Nimbus pool-29-thread-22 [WARN]
>> .org.apache.storm.utils.WrappedKeyNotFoundException
>>
>>
>> Can someone please shed some light on this?
>> Thanks
>>
>>
>>
>>
>>
>>
>>
>>
>>

Re: get blob meta exception

[Bipin Prasad]

Hello Devender,   The zookeeper entry is expected to be removed when the 
topology is killed. It appears that you are using local file store blob. So the 
blobs are (expected to be) on the nimbus. Can you check the mailbox directory 
and confirm whether or not the blob for this topology made it that far? It is 
possible that there is some issue with disk space on the nimbus host?
—Bipin


Sent from Yahoo Mail for iPhone


On Thursday, January 18, 2024, 11:39 AM, Devendar Rao 
 wrote:

Thanks Bipin for the response. To add more details:
Whenever a new topology is deployed nimbus doesn't respond and supervisor(s) go 
down. We have to restart the services to bring the cluster back to normal.
Another error we see: o.a.s.b.BlobStoreUtils BLOB-STORE-TIMER [ERROR] Could not 
download the blob with key: topology_B-7-1704896101-stormjar.jar
There is a stale entry in the zk path: 
/storm/blobstore/topology_B-7-1704896101-stormjar.jar. Not sure why it was not 
getting cleared off. This is pretty consistent.
This error goes away after manually deleting stale entry from zk path: rmr 
/storm/blobstore/topology_B-7-1704896101-stormjar.jar
Thanks,Devendar


On Thu, Jan 18, 2024 at 11:28 AM Devendar Rao  wrote:

Full stack trace:
2024-01-18 18:27:12.889 o.a.s.d.n.Nimbus pool-29-thread-22 [WARN] get blob meta 
exception.org.apache.storm.utils.WrappedKeyNotFoundException: 
topology-A-7-1704896101-stormjar.jar at 
org.apache.storm.blobstore.LocalFsBlobStore.getStoredBlobMeta(LocalFsBlobStore.java:258)
 ~[storm-server-2.3.0.jar:2.3.0] at 
org.apache.storm.blobstore.LocalFsBlobStore.getBlobMeta(LocalFsBlobStore.java:288)
 ~[storm-server-2.3.0.jar:2.3.0] at 
org.apache.storm.daemon.nimbus.Nimbus.getBlobMeta(Nimbus.java:3815) 
[storm-server-2.3.0.jar:2.3.0] at 
org.apache.storm.generated.Nimbus$Processor$getBlobMeta.getResult(Nimbus.java:4278)
 [storm-client-2.3.0.jar:2.3.0] at 
org.apache.storm.generated.Nimbus$Processor$getBlobMeta.getResult(Nimbus.java:4257)
 [storm-client-2.3.0.jar:2.3.0] at 
org.apache.storm.thrift.ProcessFunction.process(ProcessFunction.java:38) 
[storm-shaded-deps-2.3.0.jar:2.3.0] at 
org.apache.storm.thrift.TBaseProcessor.process(TBaseProcessor.java:38) 
[storm-shaded-deps-2.3.0.jar:2.3.0] at 
org.apache.storm.security.auth.SimpleTransportPlugin$SimpleWrapProcessor.process(SimpleTransportPlugin.java:172)
 [storm-client-2.3.0.jar:2.3.0] at 
org.apache.storm.thrift.server.AbstractNonblockingServer$FrameBuffer.invoke(AbstractNonblockingServer.java:524)
 [storm-shaded-deps-2.3.0.jar:2.3.0] at 
org.apache.storm.thrift.server.Invocation.run(Invocation.java:18) 
[storm-shaded-deps-2.3.0.jar:2.3.0] at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 
[?:?] at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 
[?:?] at java.lang.Thread.run(Thread.java:834) [?:?]

On Thu, Jan 18, 2024 at 11:26 AM Bipin Prasad  
wrote:

Can you post the full stack trace? I want to confirm that this is logged while 
trying to obtain the heartbeat.This message is a warning message and is not 
expected to shutdown nimbus.


Sent from Yahoo Mail for iPhone


On Thursday, January 18, 2024, 11:19 AM, Devendar Rao 
 wrote:

Hi,
We're constantly seeing issues in storm 2.3.0 with blobs with each topology 
deployment. Supervisor/nimbus dies after seeing the below exceptions. 
Is this a known issue? Are we hitting any blob cache size limits?
Exceptions:
"Could not download the blob with key:"
o.a.s.d.n.Nimbus pool-29-thread-22 [WARN] 
.org.apache.storm.utils.WrappedKeyNotFoundException


Can someone please shed some light on this?
Thanks

Re: get blob meta exception

[Bipin Prasad]

Can you post the full stack trace? I want to confirm that this is logged while 
trying to obtain the heartbeat.This message is a warning message and is not 
expected to shutdown nimbus.


Sent from Yahoo Mail for iPhone


On Thursday, January 18, 2024, 11:19 AM, Devendar Rao 
 wrote:

Hi,
We're constantly seeing issues in storm 2.3.0 with blobs with each topology 
deployment. Supervisor/nimbus dies after seeing the below exceptions. 
Is this a known issue? Are we hitting any blob cache size limits?
Exceptions:
"Could not download the blob with key:"
o.a.s.d.n.Nimbus pool-29-thread-22 [WARN] 
.org.apache.storm.utils.WrappedKeyNotFoundException


Can someone please shed some light on this?
Thanks

Re: [VOTE] Docker images for Apache Storm

[Bipin Prasad]

[+1] for publishing Storm docker images as part of Storm project 


Sent from Yahoo Mail for iPhone


On Tuesday, December 12, 2023, 1:18 AM, Julien Nioche 
 wrote:

[0] is of course a valid option, just like in any vote in any ASF-related
project

Thanks


On Tue, 12 Dec 2023 at 09:01, Alexandre Vermeerbergen <
avermeerber...@gmail.com> wrote:

> Hello,
>
> I would have voted [0] if possible, but only [+1] or [-1] are proposed ;)
>
> Indeed, regarding Docker images, I tend to be reluctant to use
> community images appart from OS base ones and built mine based on my
> actual needs which are:
> 1. To use a specific JVM (I'm more found of OpenJ9 - aka IBM Semeru
> JRE than HotSpot - aka no matter which)
> 2. To package only what's needed in my Docker images. Given that the
> best practive in the word of containers in to have one process per
> container, I would build a image with only Storm process, another one
> with only Storm UI, etc (one tickly case is how to mix supervisor and
> logview ; and by the way worker processes should be spawned by Storm
> process acting as a k8s operator, to be really "cloud native" with k8s
> stack...)
>
> If the goal of the Docker image for which the vote is ran is to
> provide an all-in-one image embedding all Storm processes, then I'm
> neutral on it, it could help newbies in evaluating Storm...
>
> Given that I'm so undecided, I just confirm [0]
> (sorry for putting a mess in this vote)
>
> Alexandre
>
> Le mar. 12 déc. 2023 à 08:31, Richard Zowalla  a écrit :
> >
> > +1 (think it would be good to "officially" be responsible and
> > distribute those on our own instead of relying on 3rd party repos)
> >
> > Am Montag, dem 11.12.2023 um 14:57 + schrieb Julien Nioche:
> > > Dear Storm community,
> > >
> > > There was a recent discussion on the dev list [1] about a roadmap for
> > > the
> > > next release (major or minor). One of the items was to release Docker
> > > images for Apache Storm ourselves. There are Docker images but
> > > maintained
> > > by a third party [2]. By managing the images ourselves, we would have
> > > more
> > > control on when the images are available and also be able to fix
> > > issues
> > > quicker.
> > >
> > > The first step is to ask Infra to give our project seats on DockerHub
> > > [3].
> > >
> > > Could we have a quick vote to make sure everyone is happy to go ahead
> > > with this?
> > >
> > > *[+1] publish Docker images ourselves and ask infra for seats to do
> > > so on
> > > Dockerhub*
> > >
> > > *or *
> > >
> > > *[-1] do not publish Docker images ourselves?*
> > >
> > > The vote is open for the next 72 hours and will finish on Thursday,
> > > December 14 at  3PM UTC.
> > >
> > > Best regards,
> > >
> > > Julien Nioche
> > >
> > >
> > > [1] https://lists.apache.org/thread/g78xg0k1m86m3o9jtj4g6p4cvvz3dhgr
> > > [2] https://github.com/31z4/storm-docker
> > > [3] https://infra.apache.org/docker-hub-policy.html
> >
>


-- 
*Julien Nioche *


digitalpebble.com 

Re: Roadmap Apache Storm 3.x

[Bipin Prasad]

I agree on the need to fix logviewer functionality so that it works in a 
Kubernetes deployment (eg AWS EKS or GKE).


Sent from Yahoo Mail for iPhone


On Thursday, December 7, 2023, 4:26 AM, Richard Zowalla  
wrote:

It might be possible to build an abstraction layer + java 21-based
module, so ppl can decide (for ex by configuration) to switch to it or
not. If you do not activley decide to use it, it won't be a difference
to how it is currently working. Might need some carefully thinking and
some eyes on other projects. 

Am Donnerstag, dem 07.12.2023 um 13:24 +0100 schrieb Alexandre
Vermeerbergen:
> Agreed for leaving fiber projet aside from 3.x
> 
> Re-logviewer : how about my idea to use storm-ui's app server and
> write some kind of proxy servlet to make all traffic related to logs
> retrieval going to storm UI ?
> 
> Le jeu. 7 déc. 2023 à 13:06, Julien Nioche
>  a écrit :
> > 
> > Thanks Alexandre,
> > 
> > I haven't looked nor know anything about fibers but it sounds
> > promising.
> > Forcing Java 21 would be problematic I think.
> > Given that it is a fundamental change, maybe this could live in a
> > separate
> > branch until thoroughly tested and Java 21 is the norm. What do you
> > think?
> > 
> > Re-logviewer: it is something that has been bugging people for a
> > while and
> > that a lot of us would like to see fixed I think. Sadly, I don't
> > have a
> > clue on how to do it.
> > 
> > Julien
> > 
> > On Thu, 7 Dec 2023 at 11:01, Alexandre Vermeerbergen <
> > avermeerber...@gmail.com> wrote:
> > 
> > > Hello Julien,
> > > 
> > > Excellent initiative indeed !
> > > 
> > > I am very fond of "Find a way of having the Logviewer work in
> > > Docker"
> > > topic, because I think it's similar to a shorter time need which
> > > I
> > > have when deploying AWS EC2 with a VPN to avoid exposure of
> > > "internal
> > > VMs" : in this case, the public FQDN of Supervisor VMs is not
> > > usable
> > > for logviewer, so i'm trying to figure out a way to do some
> > > proxying
> > > through Nimbus/Nimbus UI process... it's only brainstorming at
> > > the
> > > moment.
> > > 
> > > I also have recently  launched the idea to use Java fibers and
> > > got a
> > > positive feedback from Bipin, but I have no idea on whether it
> > > could
> > > be affordable for 3.x. One problem being is that unless we un-
> > > support
> > > Storm on Java < 21, we can't just build everything using JDK21 to
> > > get
> > > access to fibers API...
> > > 
> > > That were my 2 cents...
> > > 
> > > Alexandre
> > > 
> > > 
> > > 
> > > Le jeu. 7 déc. 2023 à 10:43, Julien Nioche
> > >  a écrit :
> > > > 
> > > > Hi,
> > > > 
> > > > Now that Storm is active again and we are getting regular
> > > > releases,
> > > should
> > > > we try to come up with a roadmap for the Storm 3.x?
> > > > 
> > > > Here are a few things that come to mind
> > > > 
> > > >    - Finish the migration from Clojure to Java (it is still
> > > > used in the
> > > >    tests I think)
> > > >    - Find a way of having the Logviewer work in Docker
> > > >    
> > > >    - Publish the Docker images ourselves
> > > >    - UI Refresh (at least the libs) - suggested by R. Zowalla
> > > >    - Fix Maven build  - suggested by R. Zowalla
> > > > 
> > > > Anything else? Who would like to get involved? Where would be a
> > > > good
> > > place
> > > > to formalise a roadmap? JIRA? GitHub projects
> > > > ?
> > > > 
> > > > Best regards
> > > > 
> > > > --
> > > > *Julien Nioche *
> > > > 
> > > > 
> > > > digitalpebble.com 
> > > 
> > 
> > 
> > --
> > *Julien Nioche *
> > 
> > 
> > digitalpebble.com 

Re: Would Java Fibers (aka Loom Project) be of interest for improving Storm capacities?

[Bipin Prasad]

Hello Alexandre,
Fibers might be useful. Will need to code for that and do performance analysis. 
Currently each worker JVM (multiple for a supervisor) runs components in 
threads.For I/O bound processes/topology components, fibers “should” help. It 
could be a topology level option (ie whether ot uses threads or fibers). My two 
cents.

—Bipin

Sent from Yahoo Mail for iPhone


On Saturday, December 2, 2023, 12:48 AM, Alexandre Vermeerbergen 
 wrote:

Hello guys,

I have a weird idea bugging my mind, so let me share it and if that's
improductive/dead end, then I'll forget it :)

I have been reading a few sources about the notion of Fibers in Java
(aka Loom Project) which are generally available with Java 21.

There's an optional "virtual threads executor" in Apache Tomcat since
a while: 
https://tomcat.apache.org/tomcat-8.5-doc/config/executor.html#Virtual_Thread_Implementation
 ; would it be worth to have something similar in Apache Storm ?

Note: Storm is a scheduler, so normally the main pain of Java threads
which is that they are OS threads is part of Storm's mission to
schedule a potentially larger set of spouts & bolts than there are
physical threads on all supervisor nodes, right?  does it mean that
virtual threads would be useless for Storm ?

Sorry for pushing headaches to some of you with these questions, but
I'd like to challenge the idea :)

Alexandre

Re: [PR] [STORM-3970] Changes to storm-sql-core/pom.xml to avoid errors in Eclipse (storm)

[Bipin Prasad]

Yes, I have fixes for those. They will be up there shortly. But at least you 
are up and running and can use the power of UI.
One thing surprised me with the latest eclipse - it is very easy for the Editor 
to get confused about the content of a file (and loose the trailing end of a 
file). I had to go a couple times in “vi” just to make sure that the file did 
not end where eclipse screen showed.


Sent from Yahoo Mail for iPhone


On Friday, September 1, 2023, 8:53 AM, Alexandre Vermeerbergen 
 wrote:

And by the way, after copying the changes from STORM-3970 (and closing
storm-cassandra project, for which I'm anticipating low community
interest, so I'm skipping it), I only have 3 errors left in Eclipse
IDE for Storm:

On /storm-client/pom.xml:
 line 206 (which just contains  tag) error message is:
- Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack
(execution: unpack, phase: process-test-resources)
- Failed to execute mojo
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack
{execution: unpack}
(org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack:unpack:process-test-resources)

On /storm-core/pom.xml:
 line 367 (which just contains  tag) error message is:
 - Failed to execute mojo
org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies
{execution: copy-dependencies}
(org.apache.maven.plugins:maven-dependency-plugin:3.6.0:copy-dependencies:copy-dependencies:package)

On /storm-core/pom.xml:
 line 381 (which just contains  tag) error message is:
 - Failed to execute mojo
org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack
{execution: unpack}
(org.apache.maven.plugins:maven-dependency-plugin:3.6.0:unpack:unpack:process-test-resources)

What is strange is although there are these 3 last errors, there are
no more Java compilation errors...

Any idea how to get rid of these 3 last ones (I'm intentionally
forgetting storm-cassandra) ?

Kind regards,
Alexandre

Le ven. 1 sept. 2023 à 11:44, avermeer (via GitHub)  a écrit :
>
>
> avermeer commented on PR #3578:
> URL: https://github.com/apache/storm/pull/3578#issuecomment-1702951565
>
>    I verified that this change greatly improves the situation is Eclipse IDE 
>(by manually copying the changes to my local temporary branch for test 
>purposes).
>
>    May I merge it ?
>
>
> --
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
>
> To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org
>
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
>

Re: Any clue to import Storm's pom.xml in Eclipse for contributing purposes?

[Bipin Prasad]

Hello Alexandre,

I spent some time trying to tweak the storm-cassandra pom.xml. Although this 
will end up in a pull request, the actual error in eclipse about "The package 
java.util is accessible from more than one module: , java.base" will 
remain.

I might try one or two other things today, but it is not looking good.

The other issue with storm-client/storm-core should have been fixed with other 
PRs that were merged or will be merged.

Thanks
--Bipin




On Thursday, August 31, 2023 at 10:30:13 AM PDT, Bipin Prasad 
 wrote: 







I will look into this later today.
Your project (subproject) jvm shows jdk/jvm-11 (as visible in eclipse in 
Package Explorer window? 




On Thursday, August 31, 2023 at 06:15:55 AM PDT, Alexandre Vermeerbergen 
 wrote: 





Hello,

Thank you very much Bipin for your advice.
I did it, and good news, now the number of errors is much lower : from
several thousand errors to 73 errors.

First set of errors is very strange: in
/storm-cassandra/src/test/java/org/apache/storm/cassandra/trident/WeatherBatchSpout.java,
I have these imports:

import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.Random;
import java.util.UUID;

with all the same errror: "The package java.util is accessible from
more than one module: , java.base"
=> this look like an issue with the notion of Java modules

Another error is on /storm-client/pom.xml, at line 206 with this long
error message:
-
Multiple markers at this line - Plugin execution not covered by
lifecycle configuration: org.apache.maven.plugins:maven-
dependency-plugin:2.8:unpack (execution: unpack, phase:
process-test-resources) - Failed to execute mojo
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack
{execution: unpack} (org.apache.maven.plugins:maven-
dependency-plugin:2.8:unpack:unpack:process-test-resources)
org.eclipse.core.runtime.CoreException: Failed to execute
mojo org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack
{execution: unpack} at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeMojo(MavenExecutionContext.java:340)
at
... (more lines)
-

Any idea how to solve these 2 types of errors ? anything missing or to
fix in related pom.xml files?

Kind regards,
Alexandre

Le mer. 30 août 2023 à 23:41, Bipin Prasad
 a écrit :
>
> Looks like eclipse (Also IntelliJ) doesn’t know about the relocated (shaded) 
> class. Solution that I have used is to build Storm-shaded-deps directly in 
> maven (mvn install), and then closing the storm-shaded-deps subproject in 
> eclipse/IntelliJ. This forces the IDE to use the storm-shaded-jar from -/.m2 
> and errors go away.
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Wednesday, August 30, 2023, 8:19 PM, Alexandre Vermeerbergen 
>  wrote:
>
> Hello;
>
> I have created a branch in my own fork of storm Github projet, and
> merged Bipin's changes from these two branches on his own fork:
>
>  [STORM-3963] Add m2e plugin to storm-shaded-deps and few minor
> pom.xml fixes => remotes/origin/storm-3963 =>
> storm-shaded-deps/pom.xml
>  [STORM-3967] Specify generated sources directory
>        => remotes/origin/storm-3967 => pom.xml
>
> I cleaned everything that I previously had in Eclipse, then I tried to
> again create an blank Eclipse workspace, then, using Eclipse's import
> projects... / Maven / Existing Maven Projects and point to the root
> directory of my local Storm git directory.
>
> Maybe one interesting point at this step is that I leave everything
> selected by default "as is", including the "[x} Add project(s) to
> working set", with "storm" as the associated value.
>
> then I clic on "Finish".
>
> After certain time of processing/downloading dependencies, Eclipse
> shows me the "Discover m2e connectors" dialog with same list as in my
> initial post, with again, no matter what I select, there is no way to
> use "Finish" button
>
> => from here, clicking "on cancel", brings me to Eclipse IDE showing
> tons of errors in the various storm projects created by the import
> process.
>
> first one is the following line:
>
> /storm-server/src/main/java/org/apache/storm/zookeeper/AclEnforcement.java
>
>  The errors are because the following imports are not found:
>
>
> import org.apache.storm.shade.org.apache.curator.framework.CuratorFramework;
> import org.apache.storm.shade.org.apache.zookeeper.KeeperException;
> import org.apache.storm.shade.org.apache.zookeeper.ZooDefs;
> import org.apache.storm.shade.org.apache.zookeeper.data.ACL;
> import org.apache.storm.

Re: Any clue to import Storm's pom.xml in Eclipse for contributing purposes?

[Bipin Prasad]

 I will look into this later today.Your project (subproject) jvm shows 
jdk/jvm-11 (as visible in eclipse in Package Explorer window? 
On Thursday, August 31, 2023 at 06:15:55 AM PDT, Alexandre Vermeerbergen 
 wrote:  
 
 Hello,

Thank you very much Bipin for your advice.
I did it, and good news, now the number of errors is much lower : from
several thousand errors to 73 errors.

First set of errors is very strange: in
/storm-cassandra/src/test/java/org/apache/storm/cassandra/trident/WeatherBatchSpout.java,
I have these imports:

import java.util.ArrayList;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import java.util.Random;
import java.util.UUID;

with all the same errror: "The package java.util is accessible from
more than one module: , java.base"
=> this look like an issue with the notion of Java modules

Another error is on /storm-client/pom.xml, at line 206 with this long
error message:
-
Multiple markers at this line - Plugin execution not covered by
lifecycle configuration: org.apache.maven.plugins:maven-
dependency-plugin:2.8:unpack (execution: unpack, phase:
process-test-resources) - Failed to execute mojo
org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack
{execution: unpack} (org.apache.maven.plugins:maven-
dependency-plugin:2.8:unpack:unpack:process-test-resources)
org.eclipse.core.runtime.CoreException: Failed to execute
mojo org.apache.maven.plugins:maven-dependency-plugin:2.8:unpack
{execution: unpack} at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeMojo(MavenExecutionContext.java:340)
at
... (more lines)
-

Any idea how to solve these 2 types of errors ? anything missing or to
fix in related pom.xml files?

Kind regards,
Alexandre

Le mer. 30 août 2023 à 23:41, Bipin Prasad
 a écrit :
>
> Looks like eclipse (Also IntelliJ) doesn’t know about the relocated (shaded) 
> class. Solution that I have used is to build Storm-shaded-deps directly in 
> maven (mvn install), and then closing the storm-shaded-deps subproject in 
> eclipse/IntelliJ. This forces the IDE to use the storm-shaded-jar from -/.m2 
> and errors go away.
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Wednesday, August 30, 2023, 8:19 PM, Alexandre Vermeerbergen 
>  wrote:
>
> Hello;
>
> I have created a branch in my own fork of storm Github projet, and
> merged Bipin's changes from these two branches on his own fork:
>
>  [STORM-3963] Add m2e plugin to storm-shaded-deps and few minor
> pom.xml fixes => remotes/origin/storm-3963 =>
> storm-shaded-deps/pom.xml
>  [STORM-3967] Specify generated sources directory
>        => remotes/origin/storm-3967 => pom.xml
>
> I cleaned everything that I previously had in Eclipse, then I tried to
> again create an blank Eclipse workspace, then, using Eclipse's import
> projects... / Maven / Existing Maven Projects and point to the root
> directory of my local Storm git directory.
>
> Maybe one interesting point at this step is that I leave everything
> selected by default "as is", including the "[x} Add project(s) to
> working set", with "storm" as the associated value.
>
> then I clic on "Finish".
>
> After certain time of processing/downloading dependencies, Eclipse
> shows me the "Discover m2e connectors" dialog with same list as in my
> initial post, with again, no matter what I select, there is no way to
> use "Finish" button
>
> => from here, clicking "on cancel", brings me to Eclipse IDE showing
> tons of errors in the various storm projects created by the import
> process.
>
> first one is the following line:
>
> /storm-server/src/main/java/org/apache/storm/zookeeper/AclEnforcement.java
>
>  The errors are because the following imports are not found:
>
>
> import org.apache.storm.shade.org.apache.curator.framework.CuratorFramework;
> import org.apache.storm.shade.org.apache.zookeeper.KeeperException;
> import org.apache.storm.shade.org.apache.zookeeper.ZooDefs;
> import org.apache.storm.shade.org.apache.zookeeper.data.ACL;
> import org.apache.storm.shade.org.apache.zookeeper.data.Id;
> import 
> org.apache.storm.shade.org.apache.zookeeper.server.auth.DigestAuthenticationProvider;
>
> It is like storm-shaded-deps's pom.xml was not automatically
> generating the shared dependencies for storm-server module.
>
> Any idea what to do next ?
>
> Reminder, I'm using latest Eclipse IDE stable version:
>
> Eclipse IDE for Java Developers (includes Incubating components)
> Version: 2023-06 (4.28.0)
> Build id: 20230608-1333
>
>
> Kind regards,
> A

Re: Any clue to import Storm's pom.xml in Eclipse for contributing purposes?

[Bipin Prasad]

Looks like eclipse (Also IntelliJ) doesn’t know about the relocated (shaded) 
class. Solution that I have used is to build Storm-shaded-deps directly in 
maven (mvn install), and then closing the storm-shaded-deps subproject in 
eclipse/IntelliJ. This forces the IDE to use the storm-shaded-jar from -/.m2 
and errors go away.


Sent from Yahoo Mail for iPhone


On Wednesday, August 30, 2023, 8:19 PM, Alexandre Vermeerbergen 
 wrote:

Hello;

I have created a branch in my own fork of storm Github projet, and
merged Bipin's changes from these two branches on his own fork:

 [STORM-3963] Add m2e plugin to storm-shaded-deps and few minor
pom.xml fixes => remotes/origin/storm-3963 =>
storm-shaded-deps/pom.xml
 [STORM-3967] Specify generated sources directory
        => remotes/origin/storm-3967 => pom.xml

I cleaned everything that I previously had in Eclipse, then I tried to
again create an blank Eclipse workspace, then, using Eclipse's import
projects... / Maven / Existing Maven Projects and point to the root
directory of my local Storm git directory.

Maybe one interesting point at this step is that I leave everything
selected by default "as is", including the "[x} Add project(s) to
working set", with "storm" as the associated value.

then I clic on "Finish".

After certain time of processing/downloading dependencies, Eclipse
shows me the "Discover m2e connectors" dialog with same list as in my
initial post, with again, no matter what I select, there is no way to
use "Finish" button

=> from here, clicking "on cancel", brings me to Eclipse IDE showing
tons of errors in the various storm projects created by the import
process.

first one is the following line:

/storm-server/src/main/java/org/apache/storm/zookeeper/AclEnforcement.java

 The errors are because the following imports are not found:


import org.apache.storm.shade.org.apache.curator.framework.CuratorFramework;
import org.apache.storm.shade.org.apache.zookeeper.KeeperException;
import org.apache.storm.shade.org.apache.zookeeper.ZooDefs;
import org.apache.storm.shade.org.apache.zookeeper.data.ACL;
import org.apache.storm.shade.org.apache.zookeeper.data.Id;
import 
org.apache.storm.shade.org.apache.zookeeper.server.auth.DigestAuthenticationProvider;

It is like storm-shaded-deps's pom.xml was not automatically
generating the shared dependencies for storm-server module.

Any idea what to do next ?

Reminder, I'm using latest Eclipse IDE stable version:

Eclipse IDE for Java Developers (includes Incubating components)
Version: 2023-06 (4.28.0)
Build id: 20230608-1333


Kind regards,
Alexandre






Le mer. 30 août 2023 à 03:35, Richard Zowalla  a écrit :
>
> I think you can fork the project, merge Bipin's changes and test with
> Eclipse locally. If the changes solve the issues, it might be a good
> thing otherwise we need to ensure, Eclipse users have a chance to be
> onboarded :)
>
> Am Dienstag, dem 29.08.2023 um 23:14 -0400 schrieb Alexandre
> Vermeerbergen:
> > Hello Julien,
> >
> > Here's the precise version of Eclipse IDE which I am using:
> > ==
> > Eclipse IDE for Java Developers (includes Incubating components)
> >
> > Version: 2023-06 (4.28.0)
> > Build id: 20230608-1333
> > ===
> >
> > And here are the versions of my M2E - Maven Integration for Eclipse's
> > components:
> >  Eclipse.org - m2e    M2E Maven Integration for Eclipse Core
> > 2.1.2.20230523-2106    org.eclipse.m2e.logback.feature
> >  Eclipse.org - m2e    M2E Maven Integration for Eclipse Core
> > 2.3.0.20230523-2033    org.eclipse.m2e.feature
> >
> >
> > Unlike Binpin, I can wait forever, the tons of compile issues are
> > still there.
> >
> > I have seen that Binpin is currently doing a pull request to importe
> > stuff in Storm's pom.xml files, maybe should I wait until this is
> > merged to master and then re-try ?
> >
> > Kind regards,
> > Alexandre
> >
> > Le mar. 29 août 2023 à 05:39, Julien Nioche
> >  a écrit :
> > >
> > > Hi Alexandre
> > >
> > > I use Eclipse and have imported Storm with Import -> Existing Maven
> > > project
> > > etc.. but am not getting the error message you mentioned. Which
> > > version of
> > > Eclipse are you using?
> > > I then get tons of compilation errors, like you do.
> > >
> > > Julien
> > >
> > >
> > > On Mon, 28 Aug 2023 at 02:23, Alexandre Vermeerbergen <
> > > avermeerber...@gmail.com> wrote:
> > >
> > > > Hello,
> > > >
> > > > I am trying to use my Eclipse IDE to work on a contribution on
> > > > storm
> > > > project.
> > > >
> > > > I must be missing something, because I though I was just a matter
> > > > of
> > > > using Eclipse's import projects... / Maven / Existing Maven
> > > > Projects
> > > > and point to the root directory of my local Storm git directory.
> > > >
> > > > But this import project wizard shows me a 'Setup Maven plugin
> > > > connectors' dialog with the following table, having two columns:
> > > > "Maven Bui

Re: Any clue to import Storm's pom.xml in Eclipse for contributing purposes?

[Bipin Prasad]

 As a first time user of eclipse on Storm project, I did encounter a lot "red" 
compile error issues.Most of them go away when I built the storm-shaded-deps 
project separately, added eclipse m2e plugin for the lifecycle management 
setting, and then selected the sub-project and in the context menu (right-mouse 
click) and closed the project. There were a few minor other changes to pom's 
based on what eclipse detected. This reduced the compile errors down very low.
I will create a pull request shortly.
On Tuesday, August 29, 2023 at 02:39:36 AM PDT, Julien Nioche 
 wrote:  
 
 Hi Alexandre

I use Eclipse and have imported Storm with Import -> Existing Maven project
etc.. but am not getting the error message you mentioned. Which version of
Eclipse are you using?
I then get tons of compilation errors, like you do.

Julien


On Mon, 28 Aug 2023 at 02:23, Alexandre Vermeerbergen <
avermeerber...@gmail.com> wrote:

> Hello,
>
> I am trying to use my Eclipse IDE to work on a contribution on storm
> project.
>
> I must be missing something, because I though I was just a matter of
> using Eclipse's import projects... / Maven / Existing Maven Projects
> and point to the root directory of my local Storm git directory.
>
> But this import project wizard shows me a 'Setup Maven plugin
> connectors' dialog with the following table, having two columns:
> "Maven Build" and "Action" and 9 lines.
>
> Here are the 2 first lines in JSON:
>
> [{"Maven
> Build":"build-helper-maven-plugin:1.5:add-source","Action":"install
> buildhelper"},
> {"Maven Build":"clojure-maven-plugin:1.8.4:compile","Action":"Use
> Workspace Default"}]
>
> and from there I cannot click on Finish button, no matter what I try.
>
> If I close this dialog, Eclipse seem to have imported all sources, but
> I get tons of compilation errors, like the ones related to missing
> shaded packages, such as:
>
> import org.apache.storm.shade.org
> .apache.curator.framework.CuratorFramework;
> import org.apache.storm.shade.org.apache.zookeeper.KeeperException;
> import org.apache.storm.shade.org.apache.zookeeper.ZooDefs;
> import org.apache.storm.shade.org.apache.zookeeper.data.ACL;
> import org.apache.storm.shade.org.apache.zookeeper.data.Id;
> import org.apache.storm.shade.org
> .apache.zookeeper.server.auth.DigestAuthenticationProvider;
>
> Sorry if that sounds trivial to current Storm developers, but I'm
> confused what to do to get a "clean" Eclipse workspace to start
> contributing ; and I once I will have understood (which you help, you
> Storm developers who already solved that kind of issue) I will
> document this in Contributing page.
>
> Kind regards,
> Alexandre
>


-- 

*Open Source Solutions for Text Engineering*

http://www.digitalpebble.com
http://digitalpebble.blogspot.com/
#digitalpebble 
  

Re: Any clue to import Storm's pom.xml in Eclipse for contributing purposes?

[Bipin Prasad]

 I also use IntelliJ.To test this out, I downloaded eclipse and imported the 
maven project for Storm.It takes a long time for eclipse to complete the task 
for loading the project fully. You can right click on the pom.xml (for a 
sub-project) and see the progress "Progress Information" popup.I would 
recommend to let eclipse download all the sources and jars it 
needs.Interestingly, eclipse highlights some of the issues in pom files that 
should be changed.
--Bipin
On Monday, August 28, 2023 at 01:15:43 AM PDT, Richard Zowalla 
 wrote:  
 
 I am using IntelliJ, so no idea about Eclipse. Sorry.


Am Sonntag, dem 27.08.2023 um 21:21 -0400 schrieb Alexandre
Vermeerbergen:
> Hello,
> 
> I am trying to use my Eclipse IDE to work on a contribution on storm
> project.
> 
> I must be missing something, because I though I was just a matter of
> using Eclipse's import projects... / Maven / Existing Maven Projects
> and point to the root directory of my local Storm git directory.
> 
> But this import project wizard shows me a 'Setup Maven plugin
> connectors' dialog with the following table, having two columns:
> "Maven Build" and "Action" and 9 lines.
> 
> Here are the 2 first lines in JSON:
> 
> [{"Maven Build":"build-helper-maven-plugin:1.5:add-
> source","Action":"install
> buildhelper"},
> {"Maven Build":"clojure-maven-plugin:1.8.4:compile","Action":"Use
> Workspace Default"}]
> 
> and from there I cannot click on Finish button, no matter what I try.
> 
> If I close this dialog, Eclipse seem to have imported all sources,
> but
> I get tons of compilation errors, like the ones related to missing
> shaded packages, such as:
> 
> import
> org.apache.storm.shade.org.apache.curator.framework.CuratorFramework;
> import org.apache.storm.shade.org.apache.zookeeper.KeeperException;
> import org.apache.storm.shade.org.apache.zookeeper.ZooDefs;
> import org.apache.storm.shade.org.apache.zookeeper.data.ACL;
> import org.apache.storm.shade.org.apache.zookeeper.data.Id;
> import
> org.apache.storm.shade.org.apache.zookeeper.server.auth.DigestAuthent
> icationProvider;
> 
> Sorry if that sounds trivial to current Storm developers, but I'm
> confused what to do to get a "clean" Eclipse workspace to start
> contributing ; and I once I will have understood (which you help, you
> Storm developers who already solved that kind of issue) I will
> document this in Contributing page.
> 
> Kind regards,
> Alexandre

  

Re: [DISCUSS] Future of /external modules -> Ask for community input

[Bipin Prasad]

 Hello Richard,   I agree with this initiative. This is especially relevant to 
Cassandra module - since support for newer version in Apache Storm needs 
changes.
Thanks--Bipin
On Monday, August 28, 2023 at 07:34:16 AM PDT, Richard Zowalla 
 wrote:  
 
 Hi all,

we (Julien, Alexandre and myself) have been discussing about the future
of the /external modules in Storm over in Slack (#Storm). As Slack
isn't the place for any decisions at the ASF, we are now moving these
discussion to the list.

Many of these modules aren't maintained anymore and there created in
the spirit of "committer sponsorships": Many of those "sponsors" aren't
active anymore.

To get an idea of which of these modules are actually used, we were
thinking of asking the community for input before discussing
deprecating or removing modules from "/external" from Storm 2.

I created a draft mail for user@ and dev@ which can be found below.

WDYT? Any thoughts?

Gruß
Richard




Dear Apache Storm Users,

we would like to update you on recent discussions regarding the future
of the Apache Storm project and its modules. As you may be aware, there
was a discussion to move Apache Storm to the attic due to resource
limitations and waning community involvement. However, we are pleased
to share that Storm will continue under the Apache Umbrella as a top
level project.

To ensure the sustainability and vitality of Apache Storm, we are now
focusing our efforts on maintaining the Storm 2.x series. However, in
order to streamline our development process and allocate resources
efficiently, we must address some challenges posed by less active
previously community-maintained modules.

Within the /external directory of the Apache Storm repository, there
are various modules that were once actively maintained by community
members, but over time, their activity has diminished. These modules
have placed a strain on the overall development process, and we believe
it's important to assess their current relevance to the community.

You can find the list of these modules at the following link: 

https://github.com/apache/storm/tree/master/external

## Call for Your Input

To assess the actual usage and necessity of these modules, we have
created a GDPR-compliant survey. Your feedback is crucial in helping us
determine which modules are actively used and which ones may need to be
deprecated. Your input will greatly influence our decisions moving
forward.

## Access the Survey

We kindly ask you to participate in the survey by indicating whether
you are currently using any of the modules listed in the /external
directory. If you believe that a specific module is still essential, we
encourage you to consider contributing to its maintenance.

Here is the link to the survey:

 ;-)

## Get Involved

If you are passionate about any of the modules that are on the verge of
being deprecated, this is your opportunity to step up and contribute.
Your involvement will not only ensure the continued existence of these
modules but also contribute to the overall health of the Apache Storm
ecosystem.

Thanks in advance!


  

Storm 2.5.0 Docker Image is now available

[Bipin Prasad]

Please see update from Elisey Zanko:
Elisey Zanko 
To:Bipin PrasadWed, Aug 16 at 8:44 AMHi Bipin,
Thanks for notifying me about the update!
Seehttps://github.com/31z4/storm-docker/commit/8e162f994d36bfae7f13a32ceb4193d185b9a89e
 andhttps://github.com/docker-library/official-images/pull/15215

On 16 Aug 2023, at 18:42, Bipin Prasad  wrote:Hello 
Elisey,
   Will you be doing a Storm 2.5.0 docker image release soon?

Thanks
--Bipin Prasad

[VOTE][RESULT] Storm 2.5.0 Release Candidate 4

[Bipin Prasad]

Storm 2.5.0 RC-4 was approved for release with 3 binding +1 and two
non-binding +1.
This included one additional binding vote and one additional non-binding
vote that were received in the last two days.

Storm 2.5.0 release artifacts are available in Maven Central Repository.
 Release is available here
https://dist.apache.org/repos/dist/release/storm/apache-storm-2.5.0
 Release notes are here:
https://dist.apache.org/repos/dist/release/storm/apache-storm-2.5.0/RELEASE_NOTES.html
 Also see: https://storm.apache.org for updated information on this 2.5.0
and prior releases.

Thanks to everyone who contributed to this release.
Special thanks to everyone who tested/restested voted and reconfirmed to
this release.

--Bipin Prasad


On Sat, Aug 5, 2023 at 10:24 AM Bipin Prasad  wrote:

> Note: In order to be compliant with ASF procedures, we need an additional
> vote for Storm 2.5.0 RC4 (which was released yesterday) . Please test the
> following and vote:
>
> Storm Release candidate version 2.5.0 rc4 was earlier released yesterday
> to here:
> https://dist.apache.org/repos/dist/release/storm/apache-storm-2.5.0
> Please vote on this release.
>
>1. How to vote is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>2. Release notes are here:
>
> https://dist.apache.org/repos/dist/release/storm/apache-storm-2.5.0/RELEASE_NOTES.html
>.
>3. The tag/commit to be voted upon is v2.5.0:
>4. The source archive being votes upon is here:
>
> https://dist.apache.org/repos/dist/release/storm/apache-storm-2.5.0/apache-storm-2.5.0-src.tar.gz
>5. The release artifacts are signed with the following key:
>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> in this file https://www.apache.org/dist/storm/KEYS
>
>
> When voting, please list the actions taken to verify the release.
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.5.0
> [ ]   0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> --Bipin Prasad
>
> On Thu, Aug 3, 2023 at 2:41 PM Bipin Prasad 
> wrote:
>
>> Storm Release candidate version 2.5.0 rc4 is here:
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4
>> Please vote on this release.
>>
>>1. How to vote is described here:
>>
>> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>>2. Release notes are here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/RELEASE_NOTES.html
>>.
>>3. The tag/commit to be voted upon is v2.5.0:
>>4. The source archive being votes upon is here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/apache-storm-2.5.0-src.tar.gz
>>5. The release artifacts are signed with the following key:
>>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
>> in this file https://www.apache.org/dist/storm/KEYS
>>
>>
>> When voting, please list the actions taken to verify the release.
>> This vote will be open for at least 72 hours.
>>
>> [ ] +1 Release this package as Apache Storm 2.5.0
>> [ ]   0 No opinion
>> [ ] -1 Do not release this package because...
>>
>> Thanks to everyone who contributed to this release.
>>
>> --Bipin Prasad
>>
>> On Wed, Aug 2, 2023 at 4:07 PM Bipin Prasad 
>> wrote:
>>
>>> Storm Release candidate version 2.5.0 rc3 is here:
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
>>> Please vote on this release.
>>>
>>>1. How to vote is described here:
>>>
>>> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>>>2. Release notes are here:
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
>>>.
>>>3. The tag/commit to be voted upon is v2.5.0:
>>>4. The source archive being votes upon is here:
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
>>>5. The release artifacts are signed with the following key:
>>>    https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
>>> in this file https://www.apache.org/dist/storm/KEYS
>>>
>>>
>>> When voting, please list the actions taken to verify the release.
>>> This vote wil

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Note: In order to be compliant with ASF procedures, we need an additional
vote for Storm 2.5.0 RC4 (which was released yesterday) . Please test the
following and vote:

Storm Release candidate version 2.5.0 rc4 was earlier released yesterday to
here: https://dist.apache.org/repos/dist/release/storm/apache-storm-2.5.0
Please vote on this release.

   1. How to vote is described here:
   
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
   2. Release notes are here:
   
https://dist.apache.org/repos/dist/release/storm/apache-storm-2.5.0/RELEASE_NOTES.html
   .
   3. The tag/commit to be voted upon is v2.5.0:
   4. The source archive being votes upon is here:
   
https://dist.apache.org/repos/dist/release/storm/apache-storm-2.5.0/apache-storm-2.5.0-src.tar.gz
   5. The release artifacts are signed with the following key:
   https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e in
   this file https://www.apache.org/dist/storm/KEYS


When voting, please list the actions taken to verify the release.
This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.5.0
[ ]   0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

--Bipin Prasad

On Thu, Aug 3, 2023 at 2:41 PM Bipin Prasad  wrote:

> Storm Release candidate version 2.5.0 rc4 is here:
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4
> Please vote on this release.
>
>1. How to vote is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>2. Release notes are here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/RELEASE_NOTES.html
>.
>3. The tag/commit to be voted upon is v2.5.0:
>4. The source archive being votes upon is here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/apache-storm-2.5.0-src.tar.gz
>5. The release artifacts are signed with the following key:
>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> in this file https://www.apache.org/dist/storm/KEYS
>
>
> When voting, please list the actions taken to verify the release.
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.5.0
> [ ]   0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> --Bipin Prasad
>
> On Wed, Aug 2, 2023 at 4:07 PM Bipin Prasad 
> wrote:
>
>> Storm Release candidate version 2.5.0 rc3 is here:
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
>> Please vote on this release.
>>
>>1. How to vote is described here:
>>
>> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>>2. Release notes are here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
>>.
>>3. The tag/commit to be voted upon is v2.5.0:
>>4. The source archive being votes upon is here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
>>5. The release artifacts are signed with the following key:
>>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
>> in this file https://www.apache.org/dist/storm/KEYS
>>
>>
>> When voting, please list the actions taken to verify the release.
>> This vote will be open for at least 72 hours.
>>
>> [ ] +1 Release this package as Apache Storm 2.5.0
>> [ ]   0 No opinion
>> [ ] -1 Do not release this package because...
>>
>> Thanks to everyone who contributed to this release.
>>
>> --Bipin Prasad
>>
>> On Tue, Jul 25, 2023 at 8:28 AM Bipin Prasad 
>> wrote:
>>
>>> Storm Release candidate version 2.5.0 rc2 is here:
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
>>> Please vote on this release.
>>>
>>>1. How to vote is described here:
>>>
>>> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>>>2. Release notes are here:
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
>>>.
>>>3. The tag/commit to be voted upon is v2.5.0:
>>>4. The source archive being votes upon is here:
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
>&

Re: Addendum to Storm's release process

[Bipin Prasad]

Richard, 
Thanks for this note on the vote process. I will ask for further votes on 
the to ensure compliance - even though RC4 was moved to release area. Will send 
out an email with the new locations. Once an additional vote is registered, I 
will send out the vote result email.

--Bipin

On 2023/08/04 20:05:35 Richard Zowalla wrote:
> Hi all,
> 
> 
> During the last release vote, I noticed the following things that we
> should do better next time to adhere to the ASF release guidelines
> [1,2,3]:
> 
> - We need at least 3 (binding) votes for a release. A binding vote
> originates from PMC members only (although community is encouraged to
> also cast non-binding votes and test the binaries). For 2.5.0, we only
> had 2 (binding) votes for RC4 and an implicit one (at least I assume
> it) by our release manager, which would need to be cast next time, so
> we can formally do the release according to the foundation's policies.
> 
> - A successful vote should be followed by a [VOTE] [RESULT] mail to
> indicate, that the vote was successful and the release process
> continues.
> 
> - If multiple RC's are needed to do a release, we would need to sent a
> mail with [VOTE] [CANCELLED] to indicate the failed attempt and start a
> new mail thread with the next release candidate. This make the process
> more transparent to everyone. 
> 
> No blaming, just my observation. I think, that we can do better next
> time :)
> 
> Gruß
> Richard
> 
> [1] https://infra.apache.org/release-publishing.html
> [2] https://www.apache.org/legal/release-policy.html
> [3] https://www.apache.org/foundation/voting.html
> 

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Note added in RELEASE_NOTES.html, updated sha512 for RELEASE_NOTES.html.
Will go thru the rest of the release process.

On 2023/08/04 14:19:15 Bipin Prasad wrote:
> Thank you for checking on this RC4 and the vote. I will add note about 
> python3 in the README.
> 
> On 2023/08/04 08:58:12 Richard Zowalla wrote:
> > Hi,
> > 
> > 1. Checked SHA512 sums: OK
> > 2. Checked ASC signatures: OK
> > 3. Build from sources with the following setup
> > 
> > Apache Maven 3.8.7 (b89d5959fcde851dcb1c8946a785a163f14e1e29)
> > Maven home: /usr/share/maven
> > Java version: 11.0.20, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-
> > openjdk-amd64
> > Default locale: de_DE, platform encoding: UTF-8
> > OS name: "linux", version: "5.19.0-50-generic", arch: "amd64", family:
> > "unix"
> > 
> > similar to GH actions: SUCCESS
> > 
> > 4. Run all tests (similar to GH actions) locally: SUCCESS
> > 
> > 5. Run a dockerized Storm topology for a while
> > 
> > (A) First I saw "/usr/bin/env: ‘python3’: No such file or directory" or
> > "/apache-storm-2.5.0/bin/storm: line 42: 10 * ‘python3’: + ‘python3’::
> > syntax error: operand expected (error token is "‘python3’: +
> > ‘python3’:")" in the logs indicating that my docker containers did not
> > have python3 available. I fixed it locally but might be worth to
> > mention that in the announcement so people don't confused but isn't a
> > blocker for 2.5.0-rc4 IMHO.
> > 
> > (B) Storm UI is showing my cluster, topology viz looks good, no script
> > errors in browser console
> > 
> > (C) Started the topology using flux, don't see any issues (didn't test
> > log viewer).
> > 
> > Thanks for preparing RC4, Bipin!!
> > 
> > So here is my +1 (binding) for RC4.
> > 
> > Gruß
> > Richard
> > 
> > 
> > 
> > Am Donnerstag, dem 03.08.2023 um 14:41 -0700 schrieb Bipin Prasad:
> > > Storm Release candidate version 2.5.0 rc4 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4
> > > Please vote on this release.
> > > 
> > >    1. How to vote is described here:
> > >   
> > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >    2. Release notes are here:
> > >   
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/RELEASE_NOTES.html
> > >    .
> > >    3. The tag/commit to be voted upon is v2.5.0:
> > >    4. The source archive being votes upon is here:
> > >   
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/apache-storm-2.5.0-src.tar.gz
> > >    5. The release artifacts are signed with the following key:
> > >   
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > >  in
> > >    this file https://www.apache.org/dist/storm/KEYS
> > > 
> > > 
> > > When voting, please list the actions taken to verify the release.
> > > This vote will be open for at least 72 hours.
> > > 
> > >     [ ] +1 Release this package as Apache Storm 2.5.0
> > >     [ ]   0 No opinion
> > >     [ ] -1 Do not release this package because...
> > > 
> > > Thanks to everyone who contributed to this release.
> > > 
> > > --Bipin Prasad
> > > 
> > > On Wed, Aug 2, 2023 at 4:07 PM Bipin Prasad 
> > > wrote:
> > > 
> > > > Storm Release candidate version 2.5.0 rc3 is here:
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
> > > > Please vote on this release.
> > > > 
> > > >    1. How to vote is described here:
> > > >   
> > > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > > >    2. Release notes are here:
> > > >   
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
> > > >    .
> > > >    3. The tag/commit to be voted upon is v2.5.0:
> > > >    4. The source archive being votes upon is here:
> > > >   
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
> > > >    5. The release artifacts are signed with the following key:
> > > >   
> > > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af7

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Great. Thanks Julien for the prompt review and vote.

On 2023/08/04 09:12:20 Julien Nioche wrote:
> Hi
> 
> Compiled from source: OK
> Ran topology in local mode: OK
> Ran topology in deployed mode: OK
> 
> +1 to release
> 
> Thanks Bipin for all your work
> 
> Julien
> 
> 
> On Fri, 4 Aug 2023 at 09:58, Richard Zowalla  wrote:
> 
> > Hi,
> >
> > 1. Checked SHA512 sums: OK
> > 2. Checked ASC signatures: OK
> > 3. Build from sources with the following setup
> >
> > Apache Maven 3.8.7 (b89d5959fcde851dcb1c8946a785a163f14e1e29)
> > Maven home: /usr/share/maven
> > Java version: 11.0.20, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-
> > openjdk-amd64
> > Default locale: de_DE, platform encoding: UTF-8
> > OS name: "linux", version: "5.19.0-50-generic", arch: "amd64", family:
> > "unix"
> >
> > similar to GH actions: SUCCESS
> >
> > 4. Run all tests (similar to GH actions) locally: SUCCESS
> >
> > 5. Run a dockerized Storm topology for a while
> >
> > (A) First I saw "/usr/bin/env: ‘python3’: No such file or directory" or
> > "/apache-storm-2.5.0/bin/storm: line 42: 10 * ‘python3’: + ‘python3’::
> > syntax error: operand expected (error token is "‘python3’: +
> > ‘python3’:")" in the logs indicating that my docker containers did not
> > have python3 available. I fixed it locally but might be worth to
> > mention that in the announcement so people don't confused but isn't a
> > blocker for 2.5.0-rc4 IMHO.
> >
> > (B) Storm UI is showing my cluster, topology viz looks good, no script
> > errors in browser console
> >
> > (C) Started the topology using flux, don't see any issues (didn't test
> > log viewer).
> >
> > Thanks for preparing RC4, Bipin!!
> >
> > So here is my +1 (binding) for RC4.
> >
> > Gruß
> > Richard
> >
> >
> >
> > Am Donnerstag, dem 03.08.2023 um 14:41 -0700 schrieb Bipin Prasad:
> > > Storm Release candidate version 2.5.0 rc4 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4
> > > Please vote on this release.
> > >
> > >1. How to vote is described here:
> > >
> > >
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >2. Release notes are here:
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/RELEASE_NOTES.html
> > >.
> > >3. The tag/commit to be voted upon is v2.5.0:
> > >4. The source archive being votes upon is here:
> > >
> > >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/apache-storm-2.5.0-src.tar.gz
> > >5. The release artifacts are signed with the following key:
> > >
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > >  in
> > >this file https://www.apache.org/dist/storm/KEYS
> > >
> > >
> > > When voting, please list the actions taken to verify the release.
> > > This vote will be open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache Storm 2.5.0
> > > [ ]   0 No opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks to everyone who contributed to this release.
> > >
> > > --Bipin Prasad
> > >
> > > On Wed, Aug 2, 2023 at 4:07 PM Bipin Prasad 
> > > wrote:
> > >
> > > > Storm Release candidate version 2.5.0 rc3 is here:
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
> > > > Please vote on this release.
> > > >
> > > >1. How to vote is described here:
> > > >
> > > >
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > > >2. Release notes are here:
> > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
> > > >.
> > > >3. The tag/commit to be voted upon is v2.5.0:
> > > >4. The source archive being votes upon is here:
> > > >
> > > >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
> > > >5. The release artifacts are signed with the following key:
> > > >
> > > &g

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Thank you for checking on this RC4 and the vote. I will add note about python3 
in the README.

On 2023/08/04 08:58:12 Richard Zowalla wrote:
> Hi,
> 
> 1. Checked SHA512 sums: OK
> 2. Checked ASC signatures: OK
> 3. Build from sources with the following setup
> 
> Apache Maven 3.8.7 (b89d5959fcde851dcb1c8946a785a163f14e1e29)
> Maven home: /usr/share/maven
> Java version: 11.0.20, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-
> openjdk-amd64
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "linux", version: "5.19.0-50-generic", arch: "amd64", family:
> "unix"
> 
> similar to GH actions: SUCCESS
> 
> 4. Run all tests (similar to GH actions) locally: SUCCESS
> 
> 5. Run a dockerized Storm topology for a while
> 
> (A) First I saw "/usr/bin/env: ‘python3’: No such file or directory" or
> "/apache-storm-2.5.0/bin/storm: line 42: 10 * ‘python3’: + ‘python3’::
> syntax error: operand expected (error token is "‘python3’: +
> ‘python3’:")" in the logs indicating that my docker containers did not
> have python3 available. I fixed it locally but might be worth to
> mention that in the announcement so people don't confused but isn't a
> blocker for 2.5.0-rc4 IMHO.
> 
> (B) Storm UI is showing my cluster, topology viz looks good, no script
> errors in browser console
> 
> (C) Started the topology using flux, don't see any issues (didn't test
> log viewer).
> 
> Thanks for preparing RC4, Bipin!!
> 
> So here is my +1 (binding) for RC4.
> 
> Gruß
> Richard
> 
> 
> 
> Am Donnerstag, dem 03.08.2023 um 14:41 -0700 schrieb Bipin Prasad:
> > Storm Release candidate version 2.5.0 rc4 is here:
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4
> > Please vote on this release.
> > 
> >    1. How to vote is described here:
> >   
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >    2. Release notes are here:
> >   
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/RELEASE_NOTES.html
> >    .
> >    3. The tag/commit to be voted upon is v2.5.0:
> >    4. The source archive being votes upon is here:
> >   
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/apache-storm-2.5.0-src.tar.gz
> >    5. The release artifacts are signed with the following key:
> >   
> > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> >  in
> >    this file https://www.apache.org/dist/storm/KEYS
> > 
> > 
> > When voting, please list the actions taken to verify the release.
> > This vote will be open for at least 72 hours.
> > 
> >     [ ] +1 Release this package as Apache Storm 2.5.0
> >     [ ]   0 No opinion
> >     [ ] -1 Do not release this package because...
> > 
> > Thanks to everyone who contributed to this release.
> > 
> > --Bipin Prasad
> > 
> > On Wed, Aug 2, 2023 at 4:07 PM Bipin Prasad 
> > wrote:
> > 
> > > Storm Release candidate version 2.5.0 rc3 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
> > > Please vote on this release.
> > > 
> > >    1. How to vote is described here:
> > >   
> > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >    2. Release notes are here:
> > >   
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
> > >    .
> > >    3. The tag/commit to be voted upon is v2.5.0:
> > >    4. The source archive being votes upon is here:
> > >   
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
> > >    5. The release artifacts are signed with the following key:
> > >   
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > >     in this file https://www.apache.org/dist/storm/KEYS
> > > 
> > > 
> > > When voting, please list the actions taken to verify the release.
> > > This vote will be open for at least 72 hours.
> > > 
> > >     [ ] +1 Release this package as Apache Storm 2.5.0
> > >     [ ]   0 No opinion
> > >     [ ] -1 Do not release this package because...
> > > 
> > > Thanks to everyone who contributed to this release.
> > > 
> > > --Bipin Prasad
> > > 
> > > On Tue, Jul 25, 2023 at 8:28 AM Bipin Prasad
> > > 
> > &g

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Storm Release candidate version 2.5.0 rc4 is here:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4
Please vote on this release.

   1. How to vote is described here:
   
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
   2. Release notes are here:
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/RELEASE_NOTES.html
   .
   3. The tag/commit to be voted upon is v2.5.0:
   4. The source archive being votes upon is here:
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/apache-storm-2.5.0-src.tar.gz
   5. The release artifacts are signed with the following key:
   https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e in
   this file https://www.apache.org/dist/storm/KEYS


When voting, please list the actions taken to verify the release.
This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.5.0
[ ]   0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

--Bipin Prasad

On Wed, Aug 2, 2023 at 4:07 PM Bipin Prasad  wrote:

> Storm Release candidate version 2.5.0 rc3 is here:
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
> Please vote on this release.
>
>1. How to vote is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>2. Release notes are here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
>.
>3. The tag/commit to be voted upon is v2.5.0:
>4. The source archive being votes upon is here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
>5. The release artifacts are signed with the following key:
>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> in this file https://www.apache.org/dist/storm/KEYS
>
>
> When voting, please list the actions taken to verify the release.
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.5.0
> [ ]   0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> --Bipin Prasad
>
> On Tue, Jul 25, 2023 at 8:28 AM Bipin Prasad 
> wrote:
>
>> Storm Release candidate version 2.5.0 rc2 is here:
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
>> Please vote on this release.
>>
>>1. How to vote is described here:
>>
>> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>>2. Release notes are here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
>>.
>>3. The tag/commit to be voted upon is v2.5.0:
>>4. The source archive being votes upon is here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
>>5. The release artifacts are signed with the following key:
>>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
>> in this file https://www.apache.org/dist/storm/KEYS
>>
>>
>> When voting, please list the actions taken to verify the release.
>> This vote will be open for at least 72 hours.
>>
>> [ ] +1 Release this package as Apache Storm 2.5.0
>> [ ]   0 No opinion
>> [ ] -1 Do not release this package because...
>>
>> Thanks to everyone who contributed to this release.
>>
>> --Bipin Prasad
>>
>> On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad 
>> wrote:
>>
>>> Storm Release candidate version 2.5.0 rc1 is here:
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
>>> Please vote on this release.
>>>
>>>1. How to vote is described here:
>>>
>>> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>>>2. Release notes are here:
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
>>>.
>>>3. The tag/commit to be voted upon is v2.5.0:
>>>4. The source archive being votes upon is here:
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
>>>5. The release artifacts are signed with the following key:
>>>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
>>> in this file https://www.apache.org/dist/storm/KEYS
>>>
>>>
>>> When voting, please list the actions taken to verify the release.
>>> This vote will be open for at least 72 hours.
>>>
>>> [ ] +1 Release this package as Apache Storm 2.5.0
>>> [ ]   0 No opinion
>>> [ ] -1 Do not release this package because...
>>>
>>> Thanks to everyone who contributed to this release.
>>>
>>> --Bipin Prasad
>>>
>>

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Thanks for checking. If I cant figure out what went wrong in the release 
process, I will start from from beginning. In any case, there will be a RC4 
soon.

On 2023/08/03 14:25:10 Richard Zowalla wrote:
> I can confirm Julien's finding.
> 
> The /public folder is indeed missing from the tar.gz and zip file.
> 
> Gruß
> Richard
> 
> Am Donnerstag, dem 03.08.2023 um 15:04 +0100 schrieb Julien Nioche:
> > Thanks Bipin
> > 
> > The source code in RC3 can now be compiled
> > The signatures look OK
> > I was able to run a topology in local mode, In deployed mode nimbus
> > and the
> > supervisor services seem to work fine but not the UI:
> > 
> > Running: /home/julien/.sdkman/candidates/java/current/bin/java -
> > server
> > > -Ddaemon.name=ui -Dstorm.options=
> > > -Dstorm.home=/home/julien/Downloads/apache-storm-2.5.0
> > > -Dstorm.log.dir=/home/julien/Downloads/apache-storm-2.5.0/logs
> > > -
> > > Djava.library.path=/usr/local/lib:/opt/local/lib:/usr/lib:/usr/lib64
> > > -Dstorm.conf.file= -cp
> > > /home/julien/Downloads/apache-storm-
> > > 2.5.0/*:/home/julien/Downloads/apache-storm-
> > > 2.5.0/lib/*:/home/julien/Downloads/apache-storm-
> > > 2.5.0/extlib/*:/home/julien/Downloads/apache-storm-2.5.0/extlib-
> > > daemon/*:/home/julien/Downloads/apache-storm-2.5.0/lib-
> > > webapp/*:/home/julien/Downloads/apache-storm-2.5.0/conf
> > > -Xmx768m -Djava.deserialization.disabled=true -Dlogfile.name=ui.log
> > > -Dlog4j.configurationFile=/home/julien/Downloads/apache-storm-
> > > 2.5.0/log4j2/cluster.xml
> > > org.apache.storm.daemon.ui.UIServer
> > > Exception in thread "main" java.lang.RuntimeException: Cannot find
> > > static
> > > file directory in development location
> > > /home/julien/Downloads/apache-storm-2.5.0/lib-webapp/storm-webapp-
> > > 2.5.0.jarWEB-INF
> > > at org.apache.storm.daemon.ui.UIServer.main(UIServer.java:160)
> > 
> > 
> > The logs contain
> > 
> > 2023-08-03 14:49:23.728 o.a.s.d.u.UIServer main [WARN] Cannot find
> > static
> > > file directory in /home/julien/Downloads/apache-storm-2.5.0/public/
> > > -
> > > assuming that UIServer is being launchedin a development
> > > environment and
> > > not from a packaged release
> > 
> > 
> > Looking at the RC I see that the folder /public is missing. It was in
> > 2.4
> > and in the previous RC. When added manually, the storm ui command
> > runs fine.
> > 
> > Sorry to be the bearer of bad news
> > 
> > Julien
> > 
> > 
> > 
> > On Thu, 3 Aug 2023 at 00:08, Bipin Prasad 
> > wrote:
> > 
> > > Storm Release candidate version 2.5.0 rc3 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
> > > Please vote on this release.
> > > 
> > >    1. How to vote is described here:
> > > 
> > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >    2. Release notes are here:
> > > 
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
> > >    .
> > >    3. The tag/commit to be voted upon is v2.5.0:
> > >    4. The source archive being votes upon is here:
> > > 
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
> > >    5. The release artifacts are signed with the following key:
> > > 
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > > in
> > >    this file https://www.apache.org/dist/storm/KEYS
> > > 
> > > 
> > > When voting, please list the actions taken to verify the release.
> > > This vote will be open for at least 72 hours.
> > > 
> > >     [ ] +1 Release this package as Apache Storm 2.5.0
> > >     [ ]   0 No opinion
> > >     [ ] -1 Do not release this package because...
> > > 
> > > Thanks to everyone who contributed to this release.
> > > 
> > > --Bipin Prasad
> > > 
> > > On Tue, Jul 25, 2023 at 8:28 AM Bipin Prasad
> > > 
> > > wrote:
> > > 
> > > > Storm Release candidate version 2.5.0 rc2 is here:
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> > > > Please vote on this release.
> > > > 
> > > >    1. How to vote is described here:
> > > > 
&

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

repo closed

On 2023/08/03 13:58:34 Richard Zowalla wrote:
> 
> Hi,
> 
> can you close the staging repo on Nexus? Otherwise using the maven
> artifacts won't be possible.
> 
> @all: Here is the repo for conviniance:
> 
> 
> 
> storm-2.5.0-rc3-test
> Testing Storm 2.5.0 RC3
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1108
> 
> 
> 
> 
> I will test once the repository is closed.
> 
> Thanks for preparing the RC3, Bipin!
> 
> Gruß
> Richard
> 
> Am Mittwoch, dem 02.08.2023 um 16:07 -0700 schrieb Bipin Prasad:
> > Storm Release candidate version 2.5.0 rc3 is here:
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
> > Please vote on this release.
> > 
> >    1. How to vote is described here:
> >   
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >    2. Release notes are here:
> >   
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
> >    .
> >    3. The tag/commit to be voted upon is v2.5.0:
> >    4. The source archive being votes upon is here:
> >   
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
> >    5. The release artifacts are signed with the following key:
> >   
> > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> >  in
> >    this file https://www.apache.org/dist/storm/KEYS
> > 
> > 
> > When voting, please list the actions taken to verify the release.
> > This vote will be open for at least 72 hours.
> > 
> >     [ ] +1 Release this package as Apache Storm 2.5.0
> >     [ ]   0 No opinion
> >     [ ] -1 Do not release this package because...
> > 
> > Thanks to everyone who contributed to this release.
> > 
> > --Bipin Prasad
> > 
> > On Tue, Jul 25, 2023 at 8:28 AM Bipin Prasad 
> > wrote:
> > 
> > > Storm Release candidate version 2.5.0 rc2 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> > > Please vote on this release.
> > > 
> > >    1. How to vote is described here:
> > >   
> > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >    2. Release notes are here:
> > >   
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
> > >    .
> > >    3. The tag/commit to be voted upon is v2.5.0:
> > >    4. The source archive being votes upon is here:
> > >   
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> > >    5. The release artifacts are signed with the following key:
> > >   
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > >     in this file https://www.apache.org/dist/storm/KEYS
> > > 
> > > 
> > > When voting, please list the actions taken to verify the release.
> > > This vote will be open for at least 72 hours.
> > > 
> > >     [ ] +1 Release this package as Apache Storm 2.5.0
> > >     [ ]   0 No opinion
> > >     [ ] -1 Do not release this package because...
> > > 
> > > Thanks to everyone who contributed to this release.
> > > 
> > > --Bipin Prasad
> > > 
> > > On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad
> > > 
> > > wrote:
> > > 
> > > > Storm Release candidate version 2.5.0 rc1 is here:
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> > > > Please vote on this release.
> > > > 
> > > >    1. How to vote is described here:
> > > >   
> > > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > > >    2. Release notes are here:
> > > >   
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
> > > >    .
> > > >    3. The tag/commit to be voted upon is v2.5.0:
> > > >    4. The source archive being votes upon is here:
> > > >   
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
> > > >    5. The release artifacts are signed with the following key:
> > > >   
> > > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > > >     in this file https://www.apache.org/dist/storm/KEYS
> > > > 
> > > > 
> > > > When voting, please list the actions taken to verify the release.
> > > > This vote will be open for at least 72 hours.
> > > > 
> > > >     [ ] +1 Release this package as Apache Storm 2.5.0
> > > >     [ ]   0 No opinion
> > > >     [ ] -1 Do not release this package because...
> > > > 
> > > > Thanks to everyone who contributed to this release.
> > > > 
> > > > --Bipin Prasad
> > > > 
> > > 
> 
> 

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Storm Release candidate version 2.5.0 rc3 is here:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
Please vote on this release.

   1. How to vote is described here:
   
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
   2. Release notes are here:
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
   .
   3. The tag/commit to be voted upon is v2.5.0:
   4. The source archive being votes upon is here:
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
   5. The release artifacts are signed with the following key:
   https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e in
   this file https://www.apache.org/dist/storm/KEYS


When voting, please list the actions taken to verify the release.
This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.5.0
[ ]   0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

--Bipin Prasad

On Tue, Jul 25, 2023 at 8:28 AM Bipin Prasad  wrote:

> Storm Release candidate version 2.5.0 rc2 is here:
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> Please vote on this release.
>
>1. How to vote is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>2. Release notes are here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
>.
>3. The tag/commit to be voted upon is v2.5.0:
>4. The source archive being votes upon is here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
>5. The release artifacts are signed with the following key:
>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> in this file https://www.apache.org/dist/storm/KEYS
>
>
> When voting, please list the actions taken to verify the release.
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.5.0
> [ ]   0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> --Bipin Prasad
>
> On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad 
> wrote:
>
>> Storm Release candidate version 2.5.0 rc1 is here:
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
>> Please vote on this release.
>>
>>1. How to vote is described here:
>>
>> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>>2. Release notes are here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
>>.
>>3. The tag/commit to be voted upon is v2.5.0:
>>4. The source archive being votes upon is here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
>>5. The release artifacts are signed with the following key:
>>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
>> in this file https://www.apache.org/dist/storm/KEYS
>>
>>
>> When voting, please list the actions taken to verify the release.
>> This vote will be open for at least 72 hours.
>>
>> [ ] +1 Release this package as Apache Storm 2.5.0
>> [ ]   0 No opinion
>> [ ] -1 Do not release this package because...
>>
>> Thanks to everyone who contributed to this release.
>>
>> --Bipin Prasad
>>
>

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

I will create RC3.

On 2023/08/02 09:42:20 Julien Nioche wrote:
> Hi!
> 
> The fix for #3940 has been merged and it is now possible to build from
> source without hitting the issues mentioned previously.
> @Bipin any chance you could generate a new RC? Anything else that needs to
> go in there? Are the signatures now all good?
> 
> Thanks!
> 
> Julien
> 
> On Tue, 1 Aug 2023 at 17:10, Richard Zowalla  wrote:
> 
> > On a clean, vanilla system without a custom maven mirror in place, I am
> > hitting the same issue.
> >
> > The problem is, that Hive 2.3.9 declares the conjars.org repo:
> > https://github.com/apache/hive/blob/rel/release-2.3.9/pom.xml#L225
> >
> > This is the reason imho, why it gets pulled into our Maven build.
> >
> > Gruß
> > Richard
> >
> >
> > Am Dienstag, dem 01.08.2023 um 15:44 + schrieb Bipin Prasad:
> > > The failure in your build
> > >  >
> > >
> > http://conjars.org/repo/org/pentaho/pentaho-aggdesigner-algorithm/5.1.5-jhyde/pentaho-aggdesigner-algorithm-5.1.5-jhyde.pom
> > >  connection timeout
> > >
> > > conjars.org does not exist anymore. If this exists in your
> > > ~/.m2/settings.xml, please remove and retry.
> > >
> > > On 2023/07/28 04:52:21 Derek Dagit wrote:
> > > > I downloaded the release files:
> > > >
> > > > ∴ wget -r -np
> > > > 'https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc
> > > > 2/'
> > > >
> > > > I checked signatures:
> > > >
> > > > ∴ ls *.asc|xargs -n1 gpg --verify
> > > > gpg: assuming signed data in 'apache-storm-2.5.0.pom'
> > > > gpg: Signature made Tue 25 Jul 2023 09:33:30 AM CDT
> > > > gpg:using RSA key
> > > > 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> > > > gpg: Good signature from "Bipin Prasad (For Signing Apache Storm
> > > > release) " [full]
> > > > gpg: assuming signed data in 'apache-storm-2.5.0-src.tar.gz'
> > > > gpg: Signature made Tue 25 Jul 2023 09:34:52 AM CDT
> > > > gpg:using RSA key
> > > > 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> > > > gpg: Good signature from "Bipin Prasad (For Signing Apache Storm
> > > > release) " [full]
> > > > gpg: assuming signed data in 'apache-storm-2.5.0-src.zip'
> > > > gpg: Signature made Tue 25 Jul 2023 09:34:52 AM CDT
> > > > gpg:using RSA key
> > > > 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> > > > gpg: Good signature from "Bipin Prasad (For Signing Apache Storm
> > > > release) " [full]
> > > > gpg: assuming signed data in 'apache-storm-2.5.0.tar.gz'
> > > > gpg: Signature made Tue 25 Jul 2023 09:33:39 AM CDT
> > > > gpg:using RSA key
> > > > 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> > > > gpg: Good signature from "Bipin Prasad (For Signing Apache Storm
> > > > release) " [full]
> > > > gpg: assuming signed data in 'apache-storm-2.5.0.zip'
> > > > gpg: Signature made Tue 25 Jul 2023 09:33:39 AM CDT
> > > > gpg:using RSA key
> > > > 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> > > > gpg: Good signature from "Bipin Prasad (For Signing Apache Storm
> > > > release) " [full]
> > > > gpg: assuming signed data in 'RELEASE_NOTES.html'
> > > > gpg: Signature made Tue 25 Jul 2023 09:47:54 AM CDT
> > > > gpg:using RSA key
> > > > 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> > > > gpg: Good signature from "Bipin Prasad (For Signing Apache Storm
> > > > release) " [full]
> > > >
> > > >
> > > >
> > > > I checked checksums:
> > > >
> > > > ∴ ls *.sha512|while read f; do gpg --print-md SHA512
> > > > "${f%%.sha512}" | diff -s - "$f"; done
> > > >
> > > > Each one of these failed because the format does not match what
> > > > results from
> > > > following the instructions at
> > > >
> > https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vote
> > > > .
> > > >
> > > > I retried this way:
> > > >
> > > > ∴ ls *.sha512|while read f; do sha512sum "${f%%.sha512}" | diff -s
> > &

Re: [GitHub] [storm] rzo1 commented on pull request #3556: Missing dependency prevents Storm from being built, fixes #3940

[Bipin Prasad]

I think it may be safe to exclude this dependency. However, we know that 
currently storm builds with github actions.

On 2023/08/01 16:14:08 "rzo1 (via GitHub)" wrote:
> 
> rzo1 commented on PR #3556:
> URL: https://github.com/apache/storm/pull/3556#issuecomment-1660648311
> 
>> This artifact is available on maven central. Is there a need to exclude 
> it? 
> https://mvnrepository.com/artifact/org.pentaho/pentaho-aggdesigner-algorithm/5.1.5-jhyde
>
>I think, that the actual problem is, that hive 2.3.9 declares the (dead) 
> conjars repo in 
> https://github.com/apache/hive/blob/rel/release-2.3.9/pom.xml#L225 
>
>Thus, Maven tries to use this repository (because it is declared on a 
> transient dependency) to download the repo and fails. Given that it is 
> already excluded in `storm-sql-runtime`, `storm-hive` and in 
> `storm-autocreds`, the changes by @jnioche just apply the excludes 
> systematically. If we run the GH actions, we will see, if the dependency is 
> required at runtime.
> 
> 
> -- 
> This is an automated message from the Apache Git Service.
> To respond to the message, please log on to GitHub and use the
> URL above to go to the specific comment.
> 
> To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org
> 
> For queries about this service, please contact Infrastructure at:
> us...@infra.apache.org
> 
> 

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

The failure in your build
 > http://conjars.org/repo/org/pentaho/pentaho-aggdesigner-algorithm/5.1.5-jhyde/pentaho-aggdesigner-algorithm-5.1.5-jhyde.pom
 >  connection timeout

conjars.org does not exist anymore. If this exists in your ~/.m2/settings.xml, 
please remove and retry.

On 2023/07/28 04:52:21 Derek Dagit wrote:
> I downloaded the release files:
> 
> ∴ wget -r -np 
> 'https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/'
> 
> I checked signatures:
> 
> ∴ ls *.asc|xargs -n1 gpg --verify
> gpg: assuming signed data in 'apache-storm-2.5.0.pom'
> gpg: Signature made Tue 25 Jul 2023 09:33:30 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'apache-storm-2.5.0-src.tar.gz'
> gpg: Signature made Tue 25 Jul 2023 09:34:52 AM CDT
> gpg:    using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'apache-storm-2.5.0-src.zip'
> gpg: Signature made Tue 25 Jul 2023 09:34:52 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'apache-storm-2.5.0.tar.gz'
> gpg: Signature made Tue 25 Jul 2023 09:33:39 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'apache-storm-2.5.0.zip'
> gpg: Signature made Tue 25 Jul 2023 09:33:39 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'RELEASE_NOTES.html'
> gpg: Signature made Tue 25 Jul 2023 09:47:54 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> 
> 
> 
> I checked checksums:
> 
> ∴ ls *.sha512|while read f; do gpg --print-md SHA512 "${f%%.sha512}" | diff 
> -s - "$f"; done
> 
> Each one of these failed because the format does not match what results from
> following the instructions at
> https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vote.
> 
> I retried this way:
> 
> ∴ ls *.sha512|while read f; do sha512sum "${f%%.sha512}" | diff -s - "$f"; 
> done
> Files - and apache-storm-2.5.0.pom.asc.sha512 are identical
> Files - and apache-storm-2.5.0.pom.sha512 are identical
> Files - and apache-storm-2.5.0-src.tar.gz.asc.sha512 are identical
> Files - and apache-storm-2.5.0-src.tar.gz.sha512 are identical
> Files - and apache-storm-2.5.0-src.zip.asc.sha512 are identical
> Files - and apache-storm-2.5.0-src.zip.sha512 are identical
> Files - and apache-storm-2.5.0.tar.gz.asc.sha512 are identical
> Files - and apache-storm-2.5.0.tar.gz.sha512 are identical
> Files - and apache-storm-2.5.0.zip.asc.sha512 are identical
> Files - and apache-storm-2.5.0.zip.sha512 are identical
> Files - and RELEASE_NOTES.html.asc.sha512 are identical
> Files - and RELEASE_NOTES.html.sha512 are identical
> 
> Looks OK.
> 
> 
> 
> Unzipped the source, built and ran tests with `mvn clean && mvn install`
> 
> I needed to use the trick at https://stackoverflow.com/a/70673228 to avoid 
> the "Blocked mirror for repositories" error maven throws when trying to 
> download with plain HTTP.
> 
> Eventually, the project failed to build because conjars.org was down:
> 
> [ERROR] Failed to execute goal on project storm-autocreds: Could not resolve 
> dependencies for project org.apache.storm:storm-autocreds:jar:2.5.0: Failed 
> to collect dependencies at 
> org.apache.hive.hcatalog:hive-webhcat-java-client:jar:2.3.9 -> 
> org.apache.hive.hcatalog:hive-hcatalog-core:jar:2.3.9 -> 
> org.apache.hive:hive-cli:jar:2.3.9 -> org.apache.hive:hive-service:jar:2.3.9 
> -> org.apache.hive:hive-exec:jar:2.3.9 -> 
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde: Failed to read 
> artifact descriptor for 
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde: Could not transfer 
> artifact org.pentaho:pentaho-aggdesigner-algorithm:pom:5.1.5-jhyde from/to 
> conjars (http://conjars.org/repo): transfer failed for 
> http://conjars.org/repo/org/pent

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Hello Derek,
Looks like some shared libraries may be missing from the jdk11 install. 
Could be similar to this issue https://github.com/pytorch/serve/issues/1352

--Bipin

On 2023/07/28 04:52:21 Derek Dagit wrote:
> I downloaded the release files:
> 
> ∴ wget -r -np 
> 'https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/'
> 
> I checked signatures:
> 
> ∴ ls *.asc|xargs -n1 gpg --verify
> gpg: assuming signed data in 'apache-storm-2.5.0.pom'
> gpg: Signature made Tue 25 Jul 2023 09:33:30 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'apache-storm-2.5.0-src.tar.gz'
> gpg: Signature made Tue 25 Jul 2023 09:34:52 AM CDT
> gpg:    using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'apache-storm-2.5.0-src.zip'
> gpg: Signature made Tue 25 Jul 2023 09:34:52 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'apache-storm-2.5.0.tar.gz'
> gpg: Signature made Tue 25 Jul 2023 09:33:39 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'apache-storm-2.5.0.zip'
> gpg: Signature made Tue 25 Jul 2023 09:33:39 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> gpg: assuming signed data in 'RELEASE_NOTES.html'
> gpg: Signature made Tue 25 Jul 2023 09:47:54 AM CDT
> gpg:using RSA key 51379DA8A7AE5B02674EF15C134716AF768D9B6E
> gpg: Good signature from "Bipin Prasad (For Signing Apache Storm release) 
> " [full]
> 
> 
> 
> I checked checksums:
> 
> ∴ ls *.sha512|while read f; do gpg --print-md SHA512 "${f%%.sha512}" | diff 
> -s - "$f"; done
> 
> Each one of these failed because the format does not match what results from
> following the instructions at
> https://github.com/apache/storm/blob/master/RELEASING.md#setting-up-a-vote.
> 
> I retried this way:
> 
> ∴ ls *.sha512|while read f; do sha512sum "${f%%.sha512}" | diff -s - "$f"; 
> done
> Files - and apache-storm-2.5.0.pom.asc.sha512 are identical
> Files - and apache-storm-2.5.0.pom.sha512 are identical
> Files - and apache-storm-2.5.0-src.tar.gz.asc.sha512 are identical
> Files - and apache-storm-2.5.0-src.tar.gz.sha512 are identical
> Files - and apache-storm-2.5.0-src.zip.asc.sha512 are identical
> Files - and apache-storm-2.5.0-src.zip.sha512 are identical
> Files - and apache-storm-2.5.0.tar.gz.asc.sha512 are identical
> Files - and apache-storm-2.5.0.tar.gz.sha512 are identical
> Files - and apache-storm-2.5.0.zip.asc.sha512 are identical
> Files - and apache-storm-2.5.0.zip.sha512 are identical
> Files - and RELEASE_NOTES.html.asc.sha512 are identical
> Files - and RELEASE_NOTES.html.sha512 are identical
> 
> Looks OK.
> 
> 
> 
> Unzipped the source, built and ran tests with `mvn clean && mvn install`
> 
> I needed to use the trick at https://stackoverflow.com/a/70673228 to avoid 
> the "Blocked mirror for repositories" error maven throws when trying to 
> download with plain HTTP.
> 
> Eventually, the project failed to build because conjars.org was down:
> 
> [ERROR] Failed to execute goal on project storm-autocreds: Could not resolve 
> dependencies for project org.apache.storm:storm-autocreds:jar:2.5.0: Failed 
> to collect dependencies at 
> org.apache.hive.hcatalog:hive-webhcat-java-client:jar:2.3.9 -> 
> org.apache.hive.hcatalog:hive-hcatalog-core:jar:2.3.9 -> 
> org.apache.hive:hive-cli:jar:2.3.9 -> org.apache.hive:hive-service:jar:2.3.9 
> -> org.apache.hive:hive-exec:jar:2.3.9 -> 
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde: Failed to read 
> artifact descriptor for 
> org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde: Could not transfer 
> artifact org.pentaho:pentaho-aggdesigner-algorithm:pom:5.1.5-jhyde from/to 
> conjars (http://conjars.org/repo): transfer failed for 
> http://conjars.org/repo/org/pentaho/pentaho-aggdesigner-algorithm/5.1.5-jhyde/pentaho-aggdesigner-algorithm-5.1.5-jhyde.pom:
>  Connect to c

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

This appears to be the change in signature in snakeyaml 2.0 (which is used via 
transitive dependency in storm 2.5.0 release) vs the older smakeyaml 1.2.

The maven artifacts are in apache staging area, for the duration of the vote.
https://repository.apache.org/content/groups/staging/.  
(/org/apache/storm//2.5.0)


On 2023/07/27 08:21:45 Julien Nioche wrote:
> Thanks Bipin,
> 
> Are the Maven artefacts for the RC available somewhere?
> 
> I am trying to run a Flux topology in local mode with code compiled with a
> dependency on 2.4 and am getting
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> *09:07:27.820 [main] ERROR o.a.s.s.o.a.z.s.NIOServerCnxnFactory - Thread
> Thread[main,5,main] diedjava.lang.reflect.InvocationTargetException: null
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[?:?] at
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> ~[?:?] at
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:?] at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?] at
> org.apache.storm.LocalCluster.lambda$main$1(LocalCluster.java:401)
> ~[storm-server-2.5.0.jar:2.5.0] at
> org.apache.storm.LocalCluster.withLocalModeOverride(LocalCluster.java:349)
> ~[storm-server-2.5.0.jar:2.5.0] at
> org.apache.storm.LocalCluster.main(LocalCluster.java:394)
> ~[storm-server-2.5.0.jar:2.5.0]Caused by: java.lang.NoSuchMethodError:
> 'void org.yaml.snakeyaml.constructor.Constructor.(java.lang.Class)'
> at org.apache.storm.flux.parser.FluxParser.yaml(FluxParser.java:203)
> ~[opencrawl-1.0-SNAPSHOT.jar:?] at
> org.apache.storm.flux.parser.FluxParser.parseInputStream(FluxParser.java:107)
> ~[opencrawl-1.0-SNAPSHOT.jar:?] at
> org.apache.storm.flux.parser.FluxParser.parseFile(FluxParser.java:68)
> ~[opencrawl-1.0-SNAPSHOT.jar:?] at
> org.apache.storm.flux.Flux.runCli(Flux.java:167)
> ~[opencrawl-1.0-SNAPSHOT.jar:?] at
> org.apache.storm.flux.Flux.main(Flux.java:119)
> ~[opencrawl-1.0-SNAPSHOT.jar:?] ... 7 more09:07:29.138 [SessionTracker]
> INFO  o.a.s.s.o.a.z.s.SessionTrackerImpl - SessionTrackerImpl exited loop!*
> Being able to access the artefacts would help recompile and track
> incompatibility between versions.
> 
> Thanks
> 
> Julien
> 
> On Tue, 25 Jul 2023 at 16:29, Bipin Prasad  wrote:
> 
> > Storm Release candidate version 2.5.0 rc2 is here:
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> > Please vote on this release.
> >
> >1. How to vote is described here:
> >
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >2. Release notes are here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
> >.
> >3. The tag/commit to be voted upon is v2.5.0:
> >4. The source archive being votes upon is here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> >5. The release artifacts are signed with the following key:
> >
> > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > in
> >this file https://www.apache.org/dist/storm/KEYS
> >
> >
> > When voting, please list the actions taken to verify the release.
> > This vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Storm 2.5.0
> > [ ]   0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > --Bipin Prasad
> >
> > On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad 
> > wrote:
> >
> > > Storm Release candidate version 2.5.0 rc1 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> > > Please vote on this release.
> > >
> > >1. How to vote is described here:
> > >
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >2. Release notes are here:
> > >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
> > >.
> > >3. The tag/commit to be voted upon is v2.5.0:
> > >4. The source archive being votes upon is here:
> > >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
> > >5. The release artifacts are signed with the following key:
> > >
> > https://keyserver.ubuntu.com/pks/look

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Thanks for pointing this out. I have reverted to using individual sha512 files 
- generated via sha512sum command. These have been pushed to svn link.

On 2023/07/25 18:03:06 Alexandre Vermeerbergen wrote:
> Thanks... but that's not quite usable unless one download *all artefacts*, 
> see:
> 
> wget 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0.tar.gz
> wget 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/sha512sums.sha512
> /usr/bin/sha512sum -c sha512sums.sha512
> 
> /usr/bin/sha512sum: RELEASE_NOTES.html: No such file or directory
> RELEASE_NOTES.html: FAILED open or read
> /usr/bin/sha512sum: RELEASE_NOTES.html.asc: No such file or directory
> RELEASE_NOTES.html.asc: FAILED open or read
> /usr/bin/sha512sum: apache-storm-2.5.0-src.tar.gz: No such file or directory
> apache-storm-2.5.0-src.tar.gz: FAILED open or read
> /usr/bin/sha512sum: apache-storm-2.5.0-src.tar.gz.asc: No such file or 
> directory
> apache-storm-2.5.0-src.tar.gz.asc: FAILED open or read
> /usr/bin/sha512sum: apache-storm-2.5.0-src.zip: No such file or directory
> apache-storm-2.5.0-src.zip: FAILED open or read
> /usr/bin/sha512sum: apache-storm-2.5.0-src.zip.asc: No such file or directory
> apache-storm-2.5.0-src.zip.asc: FAILED open or read
> /usr/bin/sha512sum: apache-storm-2.5.0.pom: No such file or directory
> apache-storm-2.5.0.pom: FAILED open or read
> /usr/bin/sha512sum: apache-storm-2.5.0.pom.asc: No such file or directory
> apache-storm-2.5.0.pom.asc: FAILED open or read
> apache-storm-2.5.0.tar.gz: OK
> /usr/bin/sha512sum: apache-storm-2.5.0.tar.gz.asc: No such file or directory
> apache-storm-2.5.0.tar.gz.asc: FAILED open or read
> /usr/bin/sha512sum: apache-storm-2.5.0.zip: No such file or directory
> apache-storm-2.5.0.zip: FAILED open or read
> /usr/bin/sha512sum: apache-storm-2.5.0.zip.asc: No such file or directory
> apache-storm-2.5.0.zip.asc: FAILED open or read
> /usr/bin/sha512sum: WARNING: 11 listed files could not be read
> 
> I tried to "corrupt" apache-storm-2.5.0.tar.gz and run the same
> command, the corrupted file is detected, but that key information is a
> bit burried into the many lines of 'sha512sum -c sha512sums.sha512'
> output...
> 
> Couldn't we have one .sha512 per file but with some sed or awk command
> that post-processes gpg's output to turn the hexadecimal into a
> one-liner compatible with sha512sum ?
> 
> On a side note, the use of sha512sum is advertised on Apache
> Fundation's site to verify sha512's signatures:
> https://www.apache.org/info/verification.html
> 
> Even more puzzling is the fact that Apache Kafka's recent signature
> are also multi-line, see at: https://kafka.apache.org/downloads and I
> test:
> 
> wget https://downloads.apache.org/kafka/3.5.1/kafka-3.5.1-src.tgz
> wget https://downloads.apache.org/kafka/3.5.1/kafka-3.5.1-src.tgz.sha512
> sha512sum -c kafka-3.5.1-src.tgz.sha512
> sha512sum: kafka-3.5.1-src.tgz.sha512: no properly formatted SHA512
> checksum lines found
> 
> => So your .sha512 files initially published aren't worse than Apache
> Kafka's... but now I'm wondering why somebody seems to care??
> 
> Anyway, in parallel I'm running tests with this 2.5.0 RC2, I'll will
> provide feedbacks on that one too ASAP
> 
> Thanks,
> Alex
> 
> Le mar. 25 juil. 2023 à 19:40, Bipin Prasad  a écrit :
> >
> > I have removed the .sha512 files generated via gpg and created one single 
> > sha512 file with all the checksums. Please check again. Thanks
> >
> > On 2023/07/25 17:27:14 Bipin Prasad wrote:
> > > Looks like gpg does not generate checksum in the format expected by 
> > > sha512sum.
> > > sha512sum expects one line of the format:
> > > space 
> > >
> > > gpg generates:
> > >: 
> > >
> > > So when I take the checksum file:
> > > apache-storm-2.5.0-src.zip: 8ABE6595 4C51B310 BA226021 29253788 0201BF9D
> > > 92DC24D7 A00FEBAE 809D0F91 EC772FAC C433F16B
> > > B56F958E 2D2EDF21 0814A02B 58819949 E26B574B
> > > A75BF1B9
> > > and change it to:
> > > 8ABE65954C51B310BA226021292537880201BF9D92DC24D7A00FEBAE809D0F91EC772FACC433F16BB56F958E2D2EDF210814A02B58819949E26B574BA75BF1B9
> > >  apache-storm-2.5.0-src.zip
> > >
> > > and run sha512sum it works.
> > >
> > > On 2023/07/25 17:13:15 Bipin Prasad wrote:
> > > > The sha512 files were generated by "gpg --print-md SHA512" command. 
> > > > Will che

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

I have removed the .sha512 files generated via gpg and created one single 
sha512 file with all the checksums. Please check again. Thanks

On 2023/07/25 17:27:14 Bipin Prasad wrote:
> Looks like gpg does not generate checksum in the format expected by sha512sum.
> sha512sum expects one line of the format:
> space 
> 
> gpg generates:
>: 
> 
> So when I take the checksum file:
> apache-storm-2.5.0-src.zip: 8ABE6595 4C51B310 BA226021 29253788 0201BF9D
> 92DC24D7 A00FEBAE 809D0F91 EC772FAC C433F16B
> B56F958E 2D2EDF21 0814A02B 58819949 E26B574B
> A75BF1B9
> and change it to:
> 8ABE65954C51B310BA226021292537880201BF9D92DC24D7A00FEBAE809D0F91EC772FACC433F16BB56F958E2D2EDF210814A02B58819949E26B574BA75BF1B9
>  apache-storm-2.5.0-src.zip
> 
> and run sha512sum it works.
> 
> On 2023/07/25 17:13:15 Bipin Prasad wrote:
> > The sha512 files were generated by "gpg --print-md SHA512" command. Will 
> > check why sha512sum does not think it is valid file.
> > 
> > On 2023/07/25 16:50:50 Alexandre Vermeerbergen wrote:
> > > Hello,
> > > 
> > > Great !
> > > But I'm facing again an issue with SHA512 validation of the source 
> > > archive:
> > > 
> > > wget 
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> > > wget 
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz.sha512
> > > sha512sum -c apache-storm-2.5.0-src.tar.gz.sha512
> > > sha512sum: apache-storm-2.5.0-src.tar.gz.sha512: no properly formatted
> > > SHA512 checksum lines found
> > > 
> > > same issue with this binary artifact:
> > > 
> > > wget 
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0.tar.gz
> > > wget 
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0.tar.gz.sha512
> > >  sha512sum -c apache-storm-2.5.0.tar.gz.sha512
> > > sha512sum: apache-storm-2.5.0.tar.gz.sha512: no properly formatted
> > > SHA512 checksum lines found
> > > 
> > > So I guess that's not good for a final 2.5.0 release isn't it ?
> > > 
> > > Thanks,
> > > Alex
> > > 
> > > Le mar. 25 juil. 2023 à 17:29, Bipin Prasad  a 
> > > écrit :
> > > >
> > > > Storm Release candidate version 2.5.0 rc2 is here:
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> > > > Please vote on this release.
> > > >
> > > >1. How to vote is described here:
> > > >
> > > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > > >2. Release notes are here:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
> > > >.
> > > >3. The tag/commit to be voted upon is v2.5.0:
> > > >4. The source archive being votes upon is here:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> > > >5. The release artifacts are signed with the following key:
> > > >
> > > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > > >  in
> > > >this file https://www.apache.org/dist/storm/KEYS
> > > >
> > > >
> > > > When voting, please list the actions taken to verify the release.
> > > > This vote will be open for at least 72 hours.
> > > >
> > > > [ ] +1 Release this package as Apache Storm 2.5.0
> > > > [ ]   0 No opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks to everyone who contributed to this release.
> > > >
> > > > --Bipin Prasad
> > > >
> > > > On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad  
> > > > wrote:
> > > >
> > > > > Storm Release candidate version 2.5.0 rc1 is here:
> > > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> > > > > Please vote on this release.
> > > > >
> > > > >1. How to vote is described here:
> > > > >
> > > > > https://github.com/apache/storm/blob/master/RELE

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Looks like gpg does not generate checksum in the format expected by sha512sum.
sha512sum expects one line of the format:
space 

gpg generates:
   : 

So when I take the checksum file:
apache-storm-2.5.0-src.zip: 8ABE6595 4C51B310 BA226021 29253788 0201BF9D
92DC24D7 A00FEBAE 809D0F91 EC772FAC C433F16B
B56F958E 2D2EDF21 0814A02B 58819949 E26B574B
A75BF1B9
and change it to:
8ABE65954C51B310BA226021292537880201BF9D92DC24D7A00FEBAE809D0F91EC772FACC433F16BB56F958E2D2EDF210814A02B58819949E26B574BA75BF1B9
 apache-storm-2.5.0-src.zip

and run sha512sum it works.

On 2023/07/25 17:13:15 Bipin Prasad wrote:
> The sha512 files were generated by "gpg --print-md SHA512" command. Will 
> check why sha512sum does not think it is valid file.
> 
> On 2023/07/25 16:50:50 Alexandre Vermeerbergen wrote:
> > Hello,
> > 
> > Great !
> > But I'm facing again an issue with SHA512 validation of the source archive:
> > 
> > wget 
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> > wget 
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz.sha512
> > sha512sum -c apache-storm-2.5.0-src.tar.gz.sha512
> > sha512sum: apache-storm-2.5.0-src.tar.gz.sha512: no properly formatted
> > SHA512 checksum lines found
> > 
> > same issue with this binary artifact:
> > 
> > wget 
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0.tar.gz
> > wget 
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0.tar.gz.sha512
> >  sha512sum -c apache-storm-2.5.0.tar.gz.sha512
> > sha512sum: apache-storm-2.5.0.tar.gz.sha512: no properly formatted
> > SHA512 checksum lines found
> > 
> > So I guess that's not good for a final 2.5.0 release isn't it ?
> > 
> > Thanks,
> > Alex
> > 
> > Le mar. 25 juil. 2023 à 17:29, Bipin Prasad  a 
> > écrit :
> > >
> > > Storm Release candidate version 2.5.0 rc2 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> > > Please vote on this release.
> > >
> > >1. How to vote is described here:
> > >
> > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >2. Release notes are here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
> > >.
> > >3. The tag/commit to be voted upon is v2.5.0:
> > >4. The source archive being votes upon is here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> > >5. The release artifacts are signed with the following key:
> > >
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e 
> > > in
> > >this file https://www.apache.org/dist/storm/KEYS
> > >
> > >
> > > When voting, please list the actions taken to verify the release.
> > > This vote will be open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache Storm 2.5.0
> > > [ ]   0 No opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks to everyone who contributed to this release.
> > >
> > > --Bipin Prasad
> > >
> > > On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad  
> > > wrote:
> > >
> > > > Storm Release candidate version 2.5.0 rc1 is here:
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> > > > Please vote on this release.
> > > >
> > > >1. How to vote is described here:
> > > >
> > > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > > >2. Release notes are here:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
> > > >.
> > > >3. The tag/commit to be voted upon is v2.5.0:
> > > >4. The source archive being votes upon is here:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
> > > >5. The release artifacts are signed with the following key:
> > > >
> > > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > > > in this file https://www.apache.org/dist/storm/KEYS
> > > >
> > > >
> > > > When voting, please list the actions taken to verify the release.
> > > > This vote will be open for at least 72 hours.
> > > >
> > > > [ ] +1 Release this package as Apache Storm 2.5.0
> > > > [ ]   0 No opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks to everyone who contributed to this release.
> > > >
> > > > --Bipin Prasad
> > > >
> > 
> 

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

The sha512 files were generated by "gpg --print-md SHA512" command. Will check 
why sha512sum does not think it is valid file.

On 2023/07/25 16:50:50 Alexandre Vermeerbergen wrote:
> Hello,
> 
> Great !
> But I'm facing again an issue with SHA512 validation of the source archive:
> 
> wget 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> wget 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz.sha512
> sha512sum -c apache-storm-2.5.0-src.tar.gz.sha512
> sha512sum: apache-storm-2.5.0-src.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> 
> same issue with this binary artifact:
> 
> wget 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0.tar.gz
> wget 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0.tar.gz.sha512
>  sha512sum -c apache-storm-2.5.0.tar.gz.sha512
> sha512sum: apache-storm-2.5.0.tar.gz.sha512: no properly formatted
> SHA512 checksum lines found
> 
> So I guess that's not good for a final 2.5.0 release isn't it ?
> 
> Thanks,
> Alex
> 
> Le mar. 25 juil. 2023 à 17:29, Bipin Prasad  a écrit :
> >
> > Storm Release candidate version 2.5.0 rc2 is here:
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> > Please vote on this release.
> >
> >1. How to vote is described here:
> >
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >2. Release notes are here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
> >.
> >3. The tag/commit to be voted upon is v2.5.0:
> >4. The source archive being votes upon is here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> >5. The release artifacts are signed with the following key:
> >https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e 
> > in
> >this file https://www.apache.org/dist/storm/KEYS
> >
> >
> > When voting, please list the actions taken to verify the release.
> > This vote will be open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Storm 2.5.0
> > [ ]   0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > --Bipin Prasad
> >
> > On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad  wrote:
> >
> > > Storm Release candidate version 2.5.0 rc1 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> > > Please vote on this release.
> > >
> > >1. How to vote is described here:
> > >
> > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >2. Release notes are here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
> > >.
> > >3. The tag/commit to be voted upon is v2.5.0:
> > >4. The source archive being votes upon is here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
> > >5. The release artifacts are signed with the following key:
> > >
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > > in this file https://www.apache.org/dist/storm/KEYS
> > >
> > >
> > > When voting, please list the actions taken to verify the release.
> > > This vote will be open for at least 72 hours.
> > >
> > > [ ] +1 Release this package as Apache Storm 2.5.0
> > > [ ]   0 No opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks to everyone who contributed to this release.
> > >
> > > --Bipin Prasad
> > >
> 

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Storm Release candidate version 2.5.0 rc2 is here:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
Please vote on this release.

   1. How to vote is described here:
   
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
   2. Release notes are here:
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
   .
   3. The tag/commit to be voted upon is v2.5.0:
   4. The source archive being votes upon is here:
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
   5. The release artifacts are signed with the following key:
   https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e in
   this file https://www.apache.org/dist/storm/KEYS


When voting, please list the actions taken to verify the release.
This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.5.0
[ ]   0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

--Bipin Prasad

On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad  wrote:

> Storm Release candidate version 2.5.0 rc1 is here:
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> Please vote on this release.
>
>1. How to vote is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>2. Release notes are here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
>.
>3. The tag/commit to be voted upon is v2.5.0:
>4. The source archive being votes upon is here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
>5. The release artifacts are signed with the following key:
>https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> in this file https://www.apache.org/dist/storm/KEYS
>
>
> When voting, please list the actions taken to verify the release.
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.5.0
> [ ]   0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> --Bipin Prasad
>

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

About jdk11,jdk17 this is coming shortly. Because of some downstream 
dependencies, there were some issues with tests. After this release, we need to 
add jdk11 and 17 to GitHub actions (and then at some point drop jdk8).


Sent from Yahoo Mail for iPhone


On Saturday, July 8, 2023, 11:44 AM, Alexandre Vermeerbergen 
 wrote:

More tests on Storm 2.5.0-RC1:
* Using the binary distribution, I upgrade my Storm cluster with 6
workers/supervisor dedicated machines (without changing the big JARs
which are still compiled with Storm 2.4.0 dependencies)
  => everything work fine so far
* I tried to compile from sources on a RedHat 8.6 machine with JDK8
(OpenJ9's) and Maven 3.9.2, got errors but that looks like what you
guys are trying to fix to Python.
  => I have attached GZIPed version of mvn clean install

Question: can we use JDK11 or JDK17 to compile Storm ?

Thanks,
Alex

Le sam. 8 juil. 2023 à 13:55, Bipin Prasad
 a écrit :
>
> I am working on release candidate 2, but will also look at this issue this 
> weekend and get back to you.Thanks for checking.
>
>
> Sent from Yahoo Mail for iPhone
>
>
> On Saturday, July 8, 2023, 1:15 AM, Alexandre Vermeerbergen 
>  wrote:
>
> Hello,
>
> I tried to check apache-storm-2.5.0.tar.gz.sha512(from
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/),
> but I get this error:
>
> $ /usr/bin/sha512sum -c apache-storm-2.5.0.tar.gz.sha512
> /usr/bin/sha512sum: apache-storm-2.5.0.tar.gz.sha512: no properly
> formatted SHA512 checksum lines found
> $ cat apache-storm-2.5.0.tar.gz.sha512
> apache-storm-2.5.0.tar.gz: 93066657 9585BF11 9F71444D 355A2FBB B1B2FAF5
>                          EA2B8FDA B783C375 391D6926 C27D9BA3 2269
>                          32D22B77 AEB00E79 EBDC5563 910740DC 35E77DD9
>                          625C0DDD
>
> Am I doing it wrong? (to create the contents of
> apache-storm-2.5.0.tar.gz.sha512, I copy-pasted the output of
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0.tar.gz.sha512)
>
> thanks,
> Alex
>
> Le jeu. 29 juin 2023 à 21:18, Aaron Gresch  a écrit :
> >
> > I found some issues with python vs python3 with the release candidate that
> > Bipin is addressing.
> >
> > On Mon, Jun 26, 2023 at 6:15 PM Bipin Prasad  wrote:
> >
> > > Storm Release candidate version 2.5.0 rc1 is here:
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> > > Please vote on this release.
> > >
> > >    1. How to vote is described here:
> > >
> > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >    2. Release notes are here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
> > >    .
> > >    3. The tag/commit to be voted upon is v2.5.0:
> > >    4. The source archive being votes upon is here:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
> > >    5. The release artifacts are signed with the following key:
> > >
> > > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > > in
> > >    this file https://www.apache.org/dist/storm/KEYS
> > >
> > >
> > > When voting, please list the actions taken to verify the release.
> > > This vote will be open for at least 72 hours.
> > >
> > >    [ ] +1 Release this package as Apache Storm 2.5.0
> > >    [ ]  0 No opinion
> > >    [ ] -1 Do not release this package because...
> > >
> > > Thanks to everyone who contributed to this release.
> > >
> > > --Bipin Prasad
> > >
>
>
>

Re: Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

I am working on release candidate 2, but will also look at this issue this 
weekend and get back to you.Thanks for checking.


Sent from Yahoo Mail for iPhone


On Saturday, July 8, 2023, 1:15 AM, Alexandre Vermeerbergen 
 wrote:

Hello,

I tried to check apache-storm-2.5.0.tar.gz.sha512(from
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/),
but I get this error:

$ /usr/bin/sha512sum -c apache-storm-2.5.0.tar.gz.sha512
/usr/bin/sha512sum: apache-storm-2.5.0.tar.gz.sha512: no properly
formatted SHA512 checksum lines found
$ cat apache-storm-2.5.0.tar.gz.sha512
apache-storm-2.5.0.tar.gz: 93066657 9585BF11 9F71444D 355A2FBB B1B2FAF5
                          EA2B8FDA B783C375 391D6926 C27D9BA3 2269
                          32D22B77 AEB00E79 EBDC5563 910740DC 35E77DD9
                          625C0DDD

Am I doing it wrong? (to create the contents of
apache-storm-2.5.0.tar.gz.sha512, I copy-pasted the output of
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0.tar.gz.sha512)

thanks,
Alex

Le jeu. 29 juin 2023 à 21:18, Aaron Gresch  a écrit :
>
> I found some issues with python vs python3 with the release candidate that
> Bipin is addressing.
>
> On Mon, Jun 26, 2023 at 6:15 PM Bipin Prasad  wrote:
>
> > Storm Release candidate version 2.5.0 rc1 is here:
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> > Please vote on this release.
> >
> >    1. How to vote is described here:
> >
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >    2. Release notes are here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
> >    .
> >    3. The tag/commit to be voted upon is v2.5.0:
> >    4. The source archive being votes upon is here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
> >    5. The release artifacts are signed with the following key:
> >
> > https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e
> > in
> >    this file https://www.apache.org/dist/storm/KEYS
> >
> >
> > When voting, please list the actions taken to verify the release.
> > This vote will be open for at least 72 hours.
> >
> >    [ ] +1 Release this package as Apache Storm 2.5.0
> >    [ ]  0 No opinion
> >    [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > --Bipin Prasad
> >

Re: Onboarding new Database Connectors to storm-external

[Bipin Prasad]

Stephen,    That will be great. Hope you get this message since the return 
email has INVALID at the end.
Thanks—Bipin


Sent from Yahoo Mail for iPhone


On Tuesday, June 27, 2023, 8:21 AM, Stephen Powis 
 wrote:

I'm happy to take up the redis spout.  I think I have an outstanding PR
(might be 3 or 4 years old at this point tho...) to improve the existing
one, and also have this implementation I'd be willing to give to the
project after bringing it up to date:
https://github.com/SourceLabOrg/RedisStreams-StormSpout

Let me know what you think,
Stephen

On Sun, Jun 25, 2023 at 8:39 PM 6harat 
wrote:

> Hey,
>
> I have been accumulating a list of popular/trending db for which storm
> connectors are still missing and preparing a case for getting them
> prioritized and added to the repo based on user interest.
>
> For now, we have the below list of potential candidates (based solely on
> my own experience in the industry)
>
> A. Listed in Top 100 at https://db-engines.com/en/ranking
>
>    1. ScyllaDB
>    2. Aeropsike
>    3. CockroachDB
>    4. Ignite
>    5. Hazelcast
>
> B. Popular Graph DBs:
>
>    1. Neo4j
>    2. ArangoDB
>    3. OrientDB
>
> C. Trending Vector DBs:
>
>    1. Milvus
>    2. Weaviate
>
> D. Already present Improvement JIRAs pertaining to existing connectors:
>
>    1. Mongo Spout: https://issues.apache.org/jira/browse/STORM-3336
>    2. Redis Sentinel: https://issues.apache.org/jira/browse/STORM-3410
>    3. Cassandra Spout: https://issues.apache.org/jira/browse/STORM-3298
>
>
> Would love to hear thoughts from the community on the same. Feel free to
> add other missing databases to the above list which you feel are also worth
> considering and/or volunteer to contribute to any of the aforementioned
> connectors.
>
> --
> Regards
> 6harat
>

Storm 2.5.0 Release Candidate Vote

[Bipin Prasad]

Storm Release candidate version 2.5.0 rc1 is here:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
Please vote on this release.

   1. How to vote is described here:
   
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
   2. Release notes are here:
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
   .
   3. The tag/commit to be voted upon is v2.5.0:
   4. The source archive being votes upon is here:
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
   5. The release artifacts are signed with the following key:
   https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x134716af768d9b6e in
   this file https://www.apache.org/dist/storm/KEYS


When voting, please list the actions taken to verify the release.
This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.5.0
[ ]   0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

--Bipin Prasad

Re: [DISCUSS] Call for PMC Members and Contributors

[Bipin Prasad]

I would urge PMC Chair to give us some guidance on this.


Sent from Yahoo Mail for iPhone


On Tuesday, June 20, 2023, 8:32 AM, 6harat  
wrote:

Hey,

Just wanted to follow-up on the thread initiated by Richard, if there were
any updates from the PMC circle that can be shared with the wider audience.
Also, curious about if we have any previous roadmap available for the
further evolution of the project. (I checked on JIRA but wasn't able to
find one)

I would be interested to help contribute to the project in any way possible
out of my personal capacity. (Have used Storm in the enterprise environment
for many years)
I would suggest if the PMC circle can syncup over google meet / zoom along
with interested new folks and help decide the way forward. Please let us
know your thoughts on the same.

Regards
6harat

On Mon, Jun 19, 2023 at 12:37 PM Richard Zowalla  wrote:

> Don't want to come across as an annoying user, but have we made any
> progress in this area yet? Everyone who has expressed interest
> (usually) doesn't have read access to private@, so no one knows what
> the current status is regarding the continuation of the project by
> expanding the committer / pmc circle. CC'ing private@, so we can
> hopefully get an update.
>
> I am asking because I read about the intention to cut a storm 2.5.0
> release and I am wondering, if we get the necessary votes in a timely
> manner.
>
> Gruß
> Richard
>
> Am Montag, dem 12.06.2023 um 12:06 +0200 schrieb Alexandre
> Vermeerbergen:
> > +1
> >
> > Le lun. 12 juin 2023 à 11:57, Richard Zowalla  a
> > écrit :
> > >
> > > Some weeks passed, any updates?
> > >
> > > Gruß
> > > Richard
> > >
> > > Am Donnerstag, dem 11.05.2023 um 19:16 -0400 schrieb P. Taylor
> > > Goetz:
> > > > Thanks for the reminder Richard,
> > > >
> > > > In response, I’ve bumped the PMC-private discussion around adding
> > > > new
> > > > members interested in contributing.
> > > >
> > > > - Taylor
> > > >
> > > > > On May 11, 2023, at 8:39 AM, Richard Zowalla 
> > > > > wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > I know we are all busy with our day jobs, but is there any
> > > > > news?
> > > > >
> > > > > We had some activity after a move to the attic was proposed. In
> > > > > the
> > > > > process, a few people volunteered to help with the project.
> > > > >
> > > > > A few weeks later, IMHO we are back to where we were before the
> > > > > proposal. Mails are going nowhere and I've heard of a few
> > > > > people
> > > > > planning to just fork Storm to get an updated version into
> > > > > production.
> > > > >
> > > > > If we want to prevent that and Storm should really be put into
> > > > > maintenance mode, then we should urgently take care of
> > > > > expanding
> > > > > the PMC/Committers circle, so that we are able to put out
> > > > > timely
> > > > > releases again and the work regarding maintenance is
> > > > > distributed on
> > > > > more than just 2 shoulders.
> > > > >
> > > > > Don't take it as a rant, it's just my opinion as someone who
> > > > > runs a
> > > > > Storm Cluster in production and would love to help the project
> > > > > to
> > > > > sustain.
> > > > >
> > > > > Gruß
> > > > > Richard
> > > > >
> > > > > On 2023/05/02 12:58:00 Richard Zowalla wrote:
> > > > > > Any updates? :-)
> > > > > >
> > > > > > Think Storm would benefit from a new release soon...
> > > > > >
> > > > > > Am Mittwoch, dem 22.02.2023 um 18:02 -0500 schrieb P. Taylor
> > > > > > Goetz:
> > > > > > > Quick update:
> > > > > > >
> > > > > > > The ASF Board voted to accept both our report and the
> > > > > > > resolution to
> > > > > > > change PMC Chair. Board feedback on our report was
> > > > > > > positive.
> > > > > > >
> > > > > > > The next step is to expand the the PMC/Committers group.
> > > > > > > Official
> > > > > > > votes will necessarily be private, but I see no reason
> > > > > > > nominations
> > > > > > > can’t be public.
> > > > > > >
> > > > > > > So lets open a thread to talk about adding new contributors
> > > > > > > to
> > > > > > > the
> > > > > > > PMC. Feel free to:
> > > > > > >
> > > > > > > 1. Volunteer to support the project as a PMC
> > > > > > > Member/Committer..
> > > > > > > 2. Nominate someone become PMC/Committer
> > > > > > >
> > > > > > > I have a few candidates in mind, and will follow up
> > > > > > > accordingly.
> > > > > > > Votes for new members will be private, but successful votes
> > > > > > > for
> > > > > > > new
> > > > > > > members will be announced on the public lists.
> > > > > > >
> > > > > > > One important way to contribute is to volunteer as a
> > > > > > > release
> > > > > > > manager
> > > > > > > for any given release, even if we release infrequently
> > > > > > > (e.g.
> > > > > > > only in
> > > > > > > response to a serious bug or security issue. I don’t have
> > > > > > > the
> > > > > > > bandwidth to act in that role, though I will commit to
> > > > > > > support
> > > > > > > voting
> > > > > > > on releases, et

Re: Storm Cassandra

[Bipin Prasad]

 Created Jira [STORM-3923] Cassandra module fails tests probably OOM - ASF JIRA 
. I think mvn test is using 3gb (inherited from main pom.xml), but will add 
directly in its pom under Cassandra. Also MAVEN_OPTS in git actions is set to 
1.5gb. I wonder if that is limiting the memory.

| 
| 
|  | 
[STORM-3923] Cassandra module fails tests probably OOM - ASF JIRA


 |

 |

 |




On Friday, June 16, 2023 at 09:58:32 AM PDT, Richard Zowalla 
 wrote:  
 
 Hi,

looks like it only falls occasionally in Java 8 with an OOM issue / JVM crash. 
Might be possible to just increase the JVM memory for that module. 

I remember from the Travis migration, that we had some heap adjustments in the 
scripts. Wdyt?

Gruß
Richard 

Am 16. Juni 2023 17:57:21 MESZ schrieb Bipin Prasad :
>All,
>  I am working on creating a new release for Storm 2.5.0. Unfortunately,
>storm-cassandra has been failing tests since we moved to Git Actions. Can
>someone take a look at it and possibly get it to work - with a newer
>version of Cassandra if possible and/or upgraded tests?
>
>  If no one is using Storm Cassandra (under xternal/storm-cassandra), I
>can exclude this from the build and release). Open to other suggestions.
>
>Thanks
>--Bipin
  

Storm Cassandra

[Bipin Prasad]

All,
   I am working on creating a new release for Storm 2.5.0. Unfortunately,
storm-cassandra has been failing tests since we moved to Git Actions. Can
someone take a look at it and possibly get it to work - with a newer
version of Cassandra if possible and/or upgraded tests?

   If no one is using Storm Cassandra (under xternal/storm-cassandra), I
can exclude this from the build and release). Open to other suggestions.

Thanks
--Bipin

Re: Does storm 2.4.0 supports IPv6 address

[Bipin Prasad]

 Hello Aishwarya,    Are you using a helm chart for this deploy and/or k8s 
deployment/service files that you can share? I don't believe Storm has been 
extensively tested in IPv6.
Thanks--Bipin
On Thursday, June 1, 2023 at 12:20:45 PM PDT, Aishwarya Soni 
 wrote:  
 
 Hi,
I have a storm 2.4.0 cluster with all the storm components such as Nimbus, UI, 
supervisors, and drpc. Recently we moved to a new GCP Kubernetes cluster where 
both traffic was coming from both IPv4 and IPv6 addresses. Previously, we were 
on a hashicorp nomad cluster where only IPv4 was supported.
Since the move to GCP Kubernetes (v1.23.x), I started to see supervisor is 
unable to communicate with drpc on port 3773. This is the error snippet from 
one of the topology logs inside a supervisor.
2023-06-01 19:02:10.136 o.a.s.d.DRPCSpout Thread-28-spout-executor[194, 194] 
[ERROR] Failed to fetch DRPC request from DRPC server 
[search-storm-drpc-4.search-storm-drpc:3773]

org.apache.storm.thrift.transport.TTransportException: Socket is closed by peer.

        at 
org.apache.storm.thrift.transport.TIOStreamTransport.read(TIOStreamTransport.java:130)
 ~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.thrift.transport.TTransport.readAll(TTransport.java:86) 
~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.thrift.transport.TFramedTransport.readFrame(TFramedTransport.java:141)
 ~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.thrift.transport.TFramedTransport.read(TFramedTransport.java:109)
 ~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.thrift.transport.TTransport.readAll(TTransport.java:86) 
~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.thrift.protocol.TBinaryProtocol.readAll(TBinaryProtocol.java:455)
 ~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.thrift.protocol.TBinaryProtocol.readI32(TBinaryProtocol.java:354)
 ~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:243)
 ~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.thrift.TServiceClient.receiveBase(TServiceClient.java:77) 
~[storm-shaded-deps-2.4.0.jar:2.4.0]

        at 
org.apache.storm.generated.DistributedRPCInvocations$Client.recv_fetchRequest(DistributedRPCInvocations.java:114)
 ~[storm-client-2.4.0.jar:2.4.0]

        at 
org.apache.storm.generated.DistributedRPCInvocations$Client.fetchRequest(DistributedRPCInvocations.java:101)
 ~[storm-client-2.4.0.jar:2.4.0]

        at 
org.apache.storm.drpc.DRPCInvocationsClient.fetchRequest(DRPCInvocationsClient.java:84)
 ~[storm-client-2.4.0.jar:2.4.0]

        at org.apache.storm.drpc.DRPCSpout.nextTuple(DRPCSpout.java:175) 
[storm-client-2.4.0.jar:2.4.0]

        at 
org.apache.storm.executor.spout.SpoutExecutor$2.call(SpoutExecutor.java:187) 
[storm-client-2.4.0.jar:2.4.0]

        at 
org.apache.storm.executor.spout.SpoutExecutor$2.call(SpoutExecutor.java:153) 
[storm-client-2.4.0.jar:2.4.0]

        at org.apache.storm.utils.Utils$1.run(Utils.java:396) 
[storm-client-2.4.0.jar:2.4.0]

        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_211]











On further debugging, I see all storm-drpc ports (3772, 3773, 3774) are 
listening to IPv6 addresses.







I tried adding the JVM flag -Djava.net.preferIPv4Stack=true mentioned here 
https://storm.apache.org/releases/2.4.0/Troubleshooting.html but that also did 
not help.




The weird thing is, telnet to the DRPC DNS names and ports work from all pods, 
but still, I see socket errors in supervisor pods while talking to DRPC.




Any inputs on any difficulties or workaround to run Storm 2.4.0 in IPv6 
addresses or make it successfully run by making ports listen to IPv4 addresses?




Regards,

Ash
  

Re: [DISCUSSION] Apache Storm and moving to the Attic

[Bipin Prasad]

I am volunteering to take on the role of PMC chairFor Storm. Not quite sure 
about the process.
Thanks—Bipin Prasad


Sent from Yahoo Mail for iPhone


On Wednesday, January 25, 2023, 4:50 PM, Aaron Niskode-Dossett 
 wrote:

Hello Storm developer community,

In the past year or so this project has slowed down and the Project
Management Committee [PMC] has almost no active members.  The PMC chair
resigned in 2022 with due notice and noone has since volunteered to assume
those duties.  I myself am an inactive PMC member.

This suggests to me that it's time to consider moving this project to the
Attic [1].  I would view this as the natural culmination of a very
successful Apache project and not as a mark of failure.  There are many,
many successful and influential projects in the attic.

The alternative to moving to the attic would be to reconstitute the PMC
with *new members* of the development community willing to take on the
responsibilities of the project and reporting to the Apache Software
Foundation board.

So, please respond to this thread if you are interested in that role.
Please also respond if you believe moving to the attic is appropriate.  A
vote on moving to the attic may be held on this list in the future.

Thanks you for your time,
Aaron

[1] https://attic.apache.org/

Re: [VOTE] Release Apache Storm 2.4.0 (rc2)

[Bipin Prasad]

+1

This vote is a little delayed. But confirming that I did checkout the
release code and went thru the following steps:
 (1) Verify files *.asc, *.sha512
 (2) Build Apache Storm source code and run unit tests, create an Apache
Storm distribution
 (i) encountered python2 and maven http blocker issues that have
workaround
 (3) Set up a standalone cluster using apache-storm-xxx.zip,
apache-storm-xxx.tar.gz, the Apache Storm distribution created from step 2,
separately;
 (i) Launch WordCountTopology and ThroughputVsLatency topology and
checked logs, UI metrics
 (4)  Test basic UI functionalities deactivate, activate, rebalance, change
log level, log search, kill topology
 (5) Test basic CLI such as kill, list, deactivate, deactivate, rebalance

--Bipin Prasad (PMC)

On Thu, Mar 10, 2022 at 9:24 AM Bipin Prasad  wrote:

> Corrected email
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>
> *This is a call to vote on releasing Apache Storm 2.4.0 (rc2)*
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v2.4.0:
>
>
> https://github.com/apache/storm/commit/a432e99bca526886655cc1d5b2453a09b302b5ca
>
>
> The source archive being voted upon can be found here:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/apache-storm-2.4.0-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/
>
> The release artifacts are signed with the following key:
>
>
> https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
>   in this file
> https://www.apache.org/dist/storm/KEYS
>
> The Nexus staging repository for this release is:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1103/
>
> Please vote on releasing this package as Apache Storm 2.4.0.
>
> When voting, please list the actions taken to verify the release.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.4.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>

[ANNOUNCE] Apache Storm 2.4.0 Released

[Bipin Prasad]

The Apache Storm community is pleased to announce the release of Apache
Storm version 2.4.0.

Apache Storm is a distributed, fault-tolerant, and high-performance
realtime computation system that provides strong guarantees on the
processing of data. You can read more about Apache Storm on the project
website:

https://storm.apache.org/

Downloads of source and binary distributions are listed in our download
section:

https://storm.apache.org/downloads.html

You can read more about this release in the following blog post:

https://storm.apache.org/2022/03/25/storm240-released.html

Distribution artifacts are available in Maven Central at the following
coordinates:

groupId: org.apache.storm
artifactId: storm-{component}
version: 2.4.0

The full list of changes is available here[1]. Please let us know [2] if
you encounter any problems.

Regards,
The Apache Storm Team

[1] https://downloads.apache.org/storm/apache-storm-2.4.0/RELEASE_NOTES.html
[2] https://issues.apache.org/jira/browse/STORM

   -
   -
   -
   -

Re: [VOTE] Release Apache Storm 2.4.0 (rc2)

[Bipin Prasad]

Gentle reminder to vote on this release for Storm 2.4.0 (rc2):

"How to vote" is described here:
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate

*This is a call to vote on releasing Apache Storm 2.4.0 (rc2)*

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.4.0:

https://github.com/apache/storm/commit/a432e99bca526886655cc1d5b2453a09b302b5ca


The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/apache-storm-2.4.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/

The release artifacts are signed with the following key:

https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
  in this file
https://www.apache.org/dist/storm/KEYS

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1103/

Please vote on releasing this package as Apache Storm 2.4.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.4.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

On Thu, Mar 10, 2022 at 6:24 AM Bipin Prasad  wrote:

> Corrected email
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>
> *This is a call to vote on releasing Apache Storm 2.4.0 (rc2)*
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v2.4.0:
>
>
> https://github.com/apache/storm/commit/a432e99bca526886655cc1d5b2453a09b302b5ca
>
>
> The source archive being voted upon can be found here:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/apache-storm-2.4.0-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/
>
> The release artifacts are signed with the following key:
>
>
> https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
>   in this file
> https://www.apache.org/dist/storm/KEYS
>
> The Nexus staging repository for this release is:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1103/
>
> Please vote on releasing this package as Apache Storm 2.4.0.
>
> When voting, please list the actions taken to verify the release.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.4.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>

[VOTE] Release Apache Storm 2.4.0 (rc2)

[Bipin Prasad]

Corrected email
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/
"How to vote" is described here:
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate

*This is a call to vote on releasing Apache Storm 2.4.0 (rc2)*

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.4.0:

https://github.com/apache/storm/commit/a432e99bca526886655cc1d5b2453a09b302b5ca


The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/apache-storm-2.4.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/

The release artifacts are signed with the following key:

https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
  in this file
https://www.apache.org/dist/storm/KEYS

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1103/

Please vote on releasing this package as Apache Storm 2.4.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.4.0
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

Re: [VOTE] Release Apache Storm 2.4.0 (rc1)

[Bipin Prasad]

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/
"How to vote" is described here:
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate

This is a call to vote on releasing Apache Storm 2.4.0 (rc2)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.4.0:

https://github.com/apache/storm/commit/a432e99bca526886655cc1d5b2453a09b302b5ca


The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/apache-storm-2.4.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc2/

The release artifacts are signed with the following key:

https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
  in this file
https://www.apache.org/dist/storm/KEYS

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1103/

Please vote on releasing this package as Apache Storm 2.4.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.1.1
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

On Thu, Mar 3, 2022 at 12:27 PM Bipin Prasad  wrote:

> This release candidate Storm Release candidate 2.4.0 rc1
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/ has
> been canceled.
> New vote request will be sent out on RC2 with further updates.
>
> On Thu, Mar 3, 2022 at 7:09 AM Bipin Prasad 
> wrote:
>
>> Gentle reminder: please vote on the Storm Release candidate 2.4.0 rc1
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
>> "How to vote" is described here:
>> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>>
>> Thank you.
>>
>>
>> On Tue, Mar 1, 2022 at 8:55 AM Bipin Prasad 
>> wrote:
>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
>>>
>>> This is a call to vote on releasing Apache Storm 2.4.0 (rc1)
>>>
>>> Full list of changes in this release:
>>>
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/RELEASE_NOTES.html
>>>
>>> The tag/commit to be voted upon is v2.4.0:
>>>
>>>
>>> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=e41710a506b401970487b5e8ca96072f7b65c9bc
>>>
>>> The source archive being voted upon can be found here:
>>>
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/apache-storm-2.4.0-src.tar.gz
>>>
>>> Other release files, signatures and digests can be found here:
>>>
>>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
>>>
>>> The release artifacts are signed with the following key:
>>>
>>>
>>> https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
>>>   in this file
>>> https://www.apache.org/dist/storm/KEYS
>>>
>>> The Nexus staging repository for this release is:
>>>
>>> https://repository.apache.org/content/repositories/orgapachestorm-1102/
>>>
>>> Please vote on releasing this package as Apache Storm 2.4.0.
>>>
>>> When voting, please list the actions taken to verify the release.
>>>
>>> This vote will be open for at least 72 hours.
>>>
>>> [ ] +1 Release this package as Apache Storm 2.1.1
>>> [ ]  0 No opinion
>>> [ ] -1 Do not release this package because...
>>>
>>> Thanks to everyone who contributed to this release.
>>>
>>

Re: [VOTE] Release Apache Storm 2.4.0 (rc1)

[Bipin Prasad]

This release candidate Storm Release candidate 2.4.0 rc1
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/ has
been canceled.
New vote request will be sent out on RC2 with further updates.

On Thu, Mar 3, 2022 at 7:09 AM Bipin Prasad  wrote:

> Gentle reminder: please vote on the Storm Release candidate 2.4.0 rc1
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>
> Thank you.
>
>
> On Tue, Mar 1, 2022 at 8:55 AM Bipin Prasad 
> wrote:
>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
>>
>> This is a call to vote on releasing Apache Storm 2.4.0 (rc1)
>>
>> Full list of changes in this release:
>>
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/RELEASE_NOTES.html
>>
>> The tag/commit to be voted upon is v2.4.0:
>>
>>
>> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=e41710a506b401970487b5e8ca96072f7b65c9bc
>>
>> The source archive being voted upon can be found here:
>>
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/apache-storm-2.4.0-src.tar.gz
>>
>> Other release files, signatures and digests can be found here:
>>
>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
>>
>> The release artifacts are signed with the following key:
>>
>>
>> https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
>>   in this file
>> https://www.apache.org/dist/storm/KEYS
>>
>> The Nexus staging repository for this release is:
>>
>> https://repository.apache.org/content/repositories/orgapachestorm-1102/
>>
>> Please vote on releasing this package as Apache Storm 2.4.0.
>>
>> When voting, please list the actions taken to verify the release.
>>
>> This vote will be open for at least 72 hours.
>>
>> [ ] +1 Release this package as Apache Storm 2.1.1
>> [ ]  0 No opinion
>> [ ] -1 Do not release this package because...
>>
>> Thanks to everyone who contributed to this release.
>>
>

Re: [VOTE] Release Apache Storm 2.4.0 (rc1)

[Bipin Prasad]

Gentle reminder: please vote on the Storm Release candidate 2.4.0 rc1
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
"How to vote" is described here:
https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate

Thank you.


On Tue, Mar 1, 2022 at 8:55 AM Bipin Prasad  wrote:

> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
>
> This is a call to vote on releasing Apache Storm 2.4.0 (rc1)
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/RELEASE_NOTES.html
>
> The tag/commit to be voted upon is v2.4.0:
>
>
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=e41710a506b401970487b5e8ca96072f7b65c9bc
>
> The source archive being voted upon can be found here:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/apache-storm-2.4.0-src.tar.gz
>
> Other release files, signatures and digests can be found here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/
>
> The release artifacts are signed with the following key:
>
>
> https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
>   in this file
> https://www.apache.org/dist/storm/KEYS
>
> The Nexus staging repository for this release is:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1102/
>
> Please vote on releasing this package as Apache Storm 2.4.0.
>
> When voting, please list the actions taken to verify the release.
>
> This vote will be open for at least 72 hours.
>
> [ ] +1 Release this package as Apache Storm 2.1.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>

[VOTE] Release Apache Storm 2.4.0 (rc1)

[Bipin Prasad]

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/

This is a call to vote on releasing Apache Storm 2.4.0 (rc1)

Full list of changes in this release:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/RELEASE_NOTES.html

The tag/commit to be voted upon is v2.4.0:

https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=e41710a506b401970487b5e8ca96072f7b65c9bc

The source archive being voted upon can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/apache-storm-2.4.0-src.tar.gz

Other release files, signatures and digests can be found here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.4.0-rc1/

The release artifacts are signed with the following key:

https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=0x51379DA8A7AE5B02674EF15C134716AF768D9B6E
  in this file
https://www.apache.org/dist/storm/KEYS

The Nexus staging repository for this release is:

https://repository.apache.org/content/repositories/orgapachestorm-1102/

Please vote on releasing this package as Apache Storm 2.4.0.

When voting, please list the actions taken to verify the release.

This vote will be open for at least 72 hours.

[ ] +1 Release this package as Apache Storm 2.1.1
[ ]  0 No opinion
[ ] -1 Do not release this package because...

Thanks to everyone who contributed to this release.

Re: [VOTE] Release Apache Storm 2.1.1 (rc1)

[Bipin Prasad]

+1

One test failure (due to difficulty in setting up "python-2.7" with "mock" 
because of its End-Of-Life)
can be ignored. 


On 2021/09/29 17:33:23, Ethan Li  wrote: 
> This is a call to vote on releasing Apache Storm 2.1.1 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.1-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.1.1:
> 
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=c5009d993ee049cd0b7c3fe0dad2fc8f700ddb5f
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.1-rc1/apache-storm-2.1.1-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.1.1-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://www.apache.org/dist/storm/KEYS
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1098
> 
> Please vote on releasing this package as Apache Storm 2.1.1.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.1.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 

Re: [VOTE] Release Apache Storm 2.2.1 (rc1)

[Bipin Prasad]

+1

One test failure (due to difficulty in setting up "python-2.7" with "mock" 
because of its End-Of-Life)
can be ignored.

++
Compile/Test Environment: "mvn -version"
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 
2019-04-04T14:00:29-05:00)
Maven home: /usr/local/Cellar/maven/3.6.1/libexec
Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_221.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
++

Checked out the release "svn co 
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.1-rc1";
 - extract storm source "tar zxvf 
apache-storm-2.2.1-rc1/apache-storm-2.2.1-src.tar.gz"
 - built "mvn install -DskipTests"
 - run unit tests "mvn test"
   - first run failed in unit "storm-client"

- second run: skip storm-client: "mvn test -rf storm-server" success

- rerun just storm-client test: "cd storm-client; mvn test" failed

---
[INFO] --- exec-maven-plugin:1.6.0:exec (python2.7-test) @ 
storm-client ---
Traceback (most recent call last):
File "test_storm_cli.py", line 20, in 
import mock
ImportError: No module named mock
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an 
error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal 
(DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute 
(DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine 
(ExecMojo.java:804)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine 
(ExecMojo.java:751)
at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:313)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:148)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute 
(DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute 
(DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:225)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:347)

---
 - because of End-of-life of python 2.7.6 and associated supported version and 
installation issues with "pip" and "mock",
python 2 support will be removed in later version. This test failure 
can be ignored.


On 2021/09/29 16:04:09, Ethan Li  wrote: 
> This is a call to vote on releasing Apache Storm 2.2.1 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.1-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.2.1:
> 
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=1d86ffd1ad

Re: [VOTE] Release Apache Storm 1.2.4 (rc1)

[Bipin Prasad]

+1

===
Compile/Test Environment: "mvn -version"
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 
2019-04-04T15:00:29-04:00)
Maven home: /usr/local/Cellar/maven/3.6.1/libexec
Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk1.8.0_221.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
===

Checked out the release "svn co 
https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1";
 - extract storm source "tar zxvf 
apache-storm-1.2.4-rc1/apache-storm-1.2.4-src.tar.gz"
 - built "mvn install -DskipTests"
 - run unit tests "mvn test"
   - first run failed in unit "flux-core"

org.apache.storm.flux.multilang.MultilangEnvironmentTest-output.txt
1566 [main] DEBUG MultilangEnvironmentTest - Invoking command: 
python
1658 [main] DEBUG MultilangEnvironmentTest - Command result: 
Python 2.7.16
1660 [main] DEBUG MultilangEnvironmentTest - Invoking command: 
node
2599 [main] DEBUG MultilangEnvironmentTest - Command result: 
dyld: Library not loaded:
  /usr/local/opt/icu4c/lib/libicui18n.64.dylib
  Referenced from: /usr/local/bin/node
  Reason: image not found
   
---
Test set: 
org.apache.storm.flux.multilang.MultilangEnvironmentTest

---
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
1.051 sec <<< FAILURE! - in 
org.apache.storm.flux.multilang.MultilangEnvironmentTest

testInvokeNode(org.apache.storm.flux.multilang.MultilangEnvironmentTest)  Time 
elapsed: 0.946 sec  <<< FAILURE!
java.lang.AssertionError: Exit value for node is 0. 
expected:<0> but was:<134>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at 
org.apache.storm.flux.multilang.MultilangEnvironmentTest.testInvokeNode(MultilangEnvironmentTest.java:48)


- second run: "mvn clean; mvn install -DskipTests": Success
"mvn test" - failed in flux-core at the same location as the 
first time: MultilangEnvironmentTest.java:48
Failure is due to execution of ccommand "node --version"
Running this command on command line: bprasad@C02XG0WLJGH8 
surefire-reports % "node --version"
dyld: Library not loaded: 
/usr/local/opt/icu4c/lib/libicui18n.64.dylib
Referenced from: /usr/local/bin/node
Reason: image not found
zsh: abort  node
- run "brew install node"
"node --version" : v16.10.0
"mvn test -rf :flux-core" - test success



On 2021/10/01 19:19:05, Ethan Li  wrote: 
> This is a call to vote on releasing Apache Storm 1.2.4 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v1.2.4:
> 
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=1bc944091b727e9a892bb36349231fcc57d9ea30
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/apache-storm-1.2.4-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://www.apache.org/dist/storm/KEYS
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1099
> 
> Please vote on releasing this package as Apache Storm 1.2.4.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 1.2.4
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 

Re: [VOTE] Release Apache Storm 2.3.0 (rc1)

[Bipin Prasad]

+1

On 2021/09/24 00:36:43, Ethan Li  wrote: 
> This is a call to vote on releasing Apache Storm 2.3.0 (rc1)
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.3.0-rc1/RELEASE_NOTES.html
> 
> The tag/commit to be voted upon is v2.3.0:
> 
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=b5252eda18e76c4f42af58d7481ea66cf3ec8471
> 
> The source archive being voted upon can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.3.0-rc1/apache-storm-2.3.0-src.tar.gz
> 
> Other release files, signatures and digests can be found here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.3.0-rc1/
> 
> The release artifacts are signed with the following key:
> 
> https://www.apache.org/dist/storm/KEYS
> 
> The Nexus staging repository for this release is:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1096
> 
> Please vote on releasing this package as Apache Storm 2.3.0.
> 
> When voting, please list the actions taken to verify the release.
> 
> This vote will be open for at least 72 hours.
> 
> [ ] +1 Release this package as Apache Storm 2.3.0
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
>