Re: [PR] STORM-4054 -Add Worker CPU Metric (storm)

[via GitHub]

jnioche merged PR #3639:
URL: https://github.com/apache/storm/pull/3639


-- 
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: [PR] STORM-4054 -Add Worker CPU Metric (storm)

[via GitHub]

agresch commented on code in PR #3639:
URL: https://github.com/apache/storm/pull/3639#discussion_r1566440996


##
storm-client/src/jvm/org/apache/storm/metric/SystemBolt.java:
##
@@ -67,12 +68,56 @@ public Long getValue() {
 
 
 context.registerGauge("newWorkerEvent", new NewWorkerGauge());
+context.registerGauge("workerCpuUsage", new WorkerCpuMetric());
 
 int bucketSize = 
ObjectReader.getInt(topoConf.get(Config.TOPOLOGY_BUILTIN_METRICS_BUCKET_SIZE_SECS));
 registerMetrics(context, (Map) 
topoConf.get(Config.WORKER_METRICS), bucketSize, topoConf);
 registerMetrics(context, (Map) 
topoConf.get(Config.TOPOLOGY_WORKER_METRICS), bucketSize, topoConf);
 }
 
+private class WorkerCpuMetric implements Gauge {
+private long lastCalculationTimeNsec;
+private long previousCpuTotal;
+private double cpuUsage;
+
+WorkerCpuMetric() {
+lastCalculationTimeNsec = System.nanoTime();
+previousCpuTotal = getTotalCpuUsage();
+cpuUsage = 0.0d;
+}
+
+private long getTotalCpuUsage() {
+long totalCpuNsecs = 0L;
+ThreadMXBean threadMxBean = ManagementFactory.getThreadMXBean();
+for (Long threadId : threadMxBean.getAllThreadIds()) {
+long threadCpu = threadMxBean.getThreadCpuTime(threadId);
+if (threadCpu > 0L) {
+totalCpuNsecs += threadCpu;
+}
+}
+return totalCpuNsecs;
+}
+
+private void updateCalculation() {
+// we could have multiple reporters calling getValue() one right
+// after another, with inaccurate reporting due to the small time 
difference.
+long elapsed = System.nanoTime() - this.lastCalculationTimeNsec;
+if (elapsed >= 10L) {

Review Comment:
   updated



-- 
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: [PR] STORM-4054 -Add Worker CPU Metric (storm)

[via GitHub]

rzo1 commented on code in PR #3639:
URL: https://github.com/apache/storm/pull/3639#discussion_r1566353967


##
storm-client/src/jvm/org/apache/storm/metric/SystemBolt.java:
##
@@ -67,12 +68,56 @@ public Long getValue() {
 
 
 context.registerGauge("newWorkerEvent", new NewWorkerGauge());
+context.registerGauge("workerCpuUsage", new WorkerCpuMetric());
 
 int bucketSize = 
ObjectReader.getInt(topoConf.get(Config.TOPOLOGY_BUILTIN_METRICS_BUCKET_SIZE_SECS));
 registerMetrics(context, (Map) 
topoConf.get(Config.WORKER_METRICS), bucketSize, topoConf);
 registerMetrics(context, (Map) 
topoConf.get(Config.TOPOLOGY_WORKER_METRICS), bucketSize, topoConf);
 }
 
+private class WorkerCpuMetric implements Gauge {
+private long lastCalculationTimeNsec;
+private long previousCpuTotal;
+private double cpuUsage;
+
+WorkerCpuMetric() {
+lastCalculationTimeNsec = System.nanoTime();
+previousCpuTotal = getTotalCpuUsage();
+cpuUsage = 0.0d;
+}
+
+private long getTotalCpuUsage() {
+long totalCpuNsecs = 0L;
+ThreadMXBean threadMxBean = ManagementFactory.getThreadMXBean();
+for (Long threadId : threadMxBean.getAllThreadIds()) {
+long threadCpu = threadMxBean.getThreadCpuTime(threadId);
+if (threadCpu > 0L) {
+totalCpuNsecs += threadCpu;
+}
+}
+return totalCpuNsecs;
+}
+
+private void updateCalculation() {
+// we could have multiple reporters calling getValue() one right
+// after another, with inaccurate reporting due to the small time 
difference.
+long elapsed = System.nanoTime() - this.lastCalculationTimeNsec;
+if (elapsed >= 10L) {

Review Comment:
   Maybe introduce a constant here? I think, that a constant instead of this 
magic number  would be more readable here. Something like `private static final 
long THRESHOLD = TimeUnit.NANOSECONDS.convert(1, TimeUnit.SECONDS);` , wdyt?



-- 
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: [PR] STORM-4053 - Include Client API / Runtime for HDFS (storm)

[via GitHub]

jnioche merged PR #3638:
URL: https://github.com/apache/storm/pull/3638


-- 
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

[PR] STORM-4053 - Include Client API / Runtime for HDFS (storm)

[via GitHub]

rzo1 opened a new pull request, #3638:
URL: https://github.com/apache/storm/pull/3638

   Followed advice from Hadoop Devs: 
https://lists.apache.org/thread/f47s6bxrtslkxbc8s2gybwrxps8vk63x


-- 
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: [RESULT] Move Storm from JIRA to GitHub issues

[Richard Zowalla]

Thanks. I added a comment. Maybe they pick it up or we can do some steps 
ourselves.

Am 11. April 2024 17:52:05 MESZ schrieb Julien Nioche 
:
>No progress on https://issues.apache.org/jira/browse/INFRA-25574 from infra.
>Any suggestions on how to proceed?
>
>On Thu, 11 Apr 2024 at 13:26, Richard Zowalla  wrote:
>
>> did we get any updates on the related jira? Or does it hang @ infra?
>>
>> Gruß
>> Richard
>>
>> Am Samstag, dem 02.03.2024 um 10:20 + schrieb Julien Nioche:
>> > The vote passes with 4 +1
>> >
>> > Thanks for taking part. Let's get things in motion next week
>> >
>> > Julien
>> >
>> > On Thu, 29 Feb 2024 at 13:20, Kishor Patil
>> > 
>> > wrote:
>> >
>> > > +1
>> > >
>> > > Best regards,
>> > > Kishor Patil
>> > >
>> > > > On Feb 28, 2024, at 4:37 PM, Bipin Prasad
>> > > > 
>> > > wrote:
>> > > >
>> > > >  +1
>> > > >On Wednesday, February 28, 2024 at 02:42:21 PM CST, Richard
>> > > > Zowalla <
>> > > r...@apache.org> 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
>> > > >
>> > >
>> >
>> >
>>
>>
>
>-- 
>*Julien Nioche *
>
>
>digitalpebble.com 

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

[Julien Nioche]

No progress on https://issues.apache.org/jira/browse/INFRA-25574 from infra.
Any suggestions on how to proceed?

On Thu, 11 Apr 2024 at 13:26, Richard Zowalla  wrote:

> did we get any updates on the related jira? Or does it hang @ infra?
>
> Gruß
> Richard
>
> Am Samstag, dem 02.03.2024 um 10:20 + schrieb Julien Nioche:
> > The vote passes with 4 +1
> >
> > Thanks for taking part. Let's get things in motion next week
> >
> > Julien
> >
> > On Thu, 29 Feb 2024 at 13:20, Kishor Patil
> > 
> > wrote:
> >
> > > +1
> > >
> > > Best regards,
> > > Kishor Patil
> > >
> > > > On Feb 28, 2024, at 4:37 PM, Bipin Prasad
> > > > 
> > > wrote:
> > > >
> > > >  +1
> > > >On Wednesday, February 28, 2024 at 02:42:21 PM CST, Richard
> > > > Zowalla <
> > > r...@apache.org> 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
> > > >
> > >
> >
> >
>
>

-- 
*Julien Nioche *


digitalpebble.com 

Re: [PR] [STORM-4053] Add Hadoop client API dependency back to storm-hdfs (storm)

[via GitHub]

jnioche merged PR #3637:
URL: https://github.com/apache/storm/pull/3637


-- 
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: [PR] [STORM-4053] Add Hadoop client API dependency back to storm-hdfs (storm)

[via GitHub]

rzo1 closed pull request #3636: [STORM-4053] Add Hadoop client API dependency 
back to storm-hdfs
URL: https://github.com/apache/storm/pull/3636


-- 
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: [PR] [STORM-4053] Add Hadoop client API dependency back to storm-hdfs (storm)

[via GitHub]

rzo1 commented on PR #3636:
URL: https://github.com/apache/storm/pull/3636#issuecomment-2049694827

   superseeded by https://github.com/apache/storm/pull/3637


-- 
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

[PR] [STORM-4053] Add Hadoop client API dependency back to storm-hdfs (storm)

[via GitHub]

rzo1 opened a new pull request, #3637:
URL: https://github.com/apache/storm/pull/3637

   Superseeds https://github.com/apache/storm/pull/3636


-- 
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: [RESULT] Move Storm from JIRA to GitHub issues

[Richard Zowalla]

did we get any updates on the related jira? Or does it hang @ infra?

Gruß
Richard

Am Samstag, dem 02.03.2024 um 10:20 + schrieb Julien Nioche:
> The vote passes with 4 +1
> 
> Thanks for taking part. Let's get things in motion next week
> 
> Julien
> 
> On Thu, 29 Feb 2024 at 13:20, Kishor Patil
> 
> wrote:
> 
> > +1
> > 
> > Best regards,
> > Kishor Patil
> > 
> > > On Feb 28, 2024, at 4:37 PM, Bipin Prasad
> > > 
> > wrote:
> > > 
> > >  +1
> > >    On Wednesday, February 28, 2024 at 02:42:21 PM CST, Richard
> > > Zowalla <
> > r...@apache.org> 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
> > > 
> > 
> 
> 



signature.asc
Description: This is a digitally signed message part

[PR] [STORM-4053] Add Hadoop client API dependency back to storm-hdfs (storm)

[via GitHub]

jnioche opened a new pull request, #3636:
URL: https://github.com/apache/storm/pull/3636

   ## What is the purpose of the change
   
   Dependency was removed by mistake
   See https://github.com/apache/incubator-stormcrawler/pull/1189
   
   ## How was the change tested
   
   mvn clean test


-- 
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: [PR] STORM-4052 - Simplify/Remove double delete/lookup in heartbeat cleanup code. (storm)

[via GitHub]

rzo1 merged PR #3635:
URL: https://github.com/apache/storm/pull/3635


-- 
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: [PR] STORM-4052 - Simplify/Remove double delete/lookup in heartbeat cleanup code. (storm)

[via GitHub]

rzo1 commented on PR #3635:
URL: https://github.com/apache/storm/pull/3635#issuecomment-2040483708

   Thx for the contribution, @sammac 


-- 
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

[ANNOUNCE] Apache Storm 2.6.2 Released

[Richard Zowalla]

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

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/2024/04/05/storm262-released.html

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

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

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.6.2/RELEASE_NOTES.html
[2] https://issues.apache.org/jira/browse/STORM

[PR] Simplify/Remove double delete/lookup in heartbeat cleanup code. (storm)

[via GitHub]

sammac opened a new pull request, #3635:
URL: https://github.com/apache/storm/pull/3635

   ## What is the purpose of the change
   
   This changes slightly simplifies the heartbeat cleanup code so it no longer 
tries to delete the heartbeat files twice. It also removes an unneeded 
directory listing (and possible race) by truncating the versions list and using 
it for removal instead of for keeping.
   
   Removing the double delete attempt is important because it removes a lookup 
for now non-existent files. Looking up non existent files, especially highly 
unique (like timestamped) ones can adversely affect many operating systems as 
these lookups are cached as negative dentries.
   https://lwn.net/Articles/814535/
   
   When cleanup runs, it iterates over the heartbeat directory that contains a 
token and version file for each heartbeat. It calls deleteVersion for each file 
in the directory which attempts to delete both files associated with the 
heartbeat. As deleteVersion already deletes both when it first iterates over 
the token file, the iteration for the version file has nothing to do.
   
   Before removing, the deleteVersion code checks for the existence of these 
now non existent files. On linux (and other OSs) a lookup for a non-existent 
path will create a negative dentry in the operating system's cache. On some 
configurations this cache can grow effectively unbounded leading to performance 
issues. On newer systems this cache is better managed, but this will still 
dilute an otherwise useful OS cache with useless entries.
   
   ## How was the change tested
   
   Ran tests.


-- 
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: [PR] STORM-4051 - Scheduler needs to include acker memory for topology resources (storm)

[via GitHub]

rzo1 commented on PR #3633:
URL: https://github.com/apache/storm/pull/3633#issuecomment-2040326042

   Thanks @agresch 


-- 
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: [PR] STORM-4051 - Scheduler needs to include acker memory for topology resources (storm)

[via GitHub]

rzo1 merged PR #3633:
URL: https://github.com/apache/storm/pull/3633


-- 
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: [RESULT] [VOTE] Apache Storm 2.6.2 (rc1)

[Alexandre Vermeerbergen]

Thanks a lot Richard for this very smooth & efficient release !

Alexandre

Le ven. 5 avr. 2024 à 19:37, Richard Zowalla  a écrit :
>
> Hi,
>
> this vote passes with the following votes:
>
> +1 Julien Nioche (binding)
> +1 Alexandre Vermeerbergen (binding)
> +1 Richard Zowalla (binding)
>
> I'll proceed with the steps. Thx for your time!
>
> Gruß
> Richard

[RESULT] [VOTE] Apache Storm 2.6.2 (rc1)

[Richard Zowalla]

Hi,

this vote passes with the following votes:

+1 Julien Nioche (binding)
+1 Alexandre Vermeerbergen (binding)
+1 Richard Zowalla (binding)

I'll proceed with the steps. Thx for your time!

Gruß
Richard

Re: [PR] Release of Apache Storm 2.6.2 (storm)

[via GitHub]

rzo1 merged PR #3634:
URL: https://github.com/apache/storm/pull/3634


-- 
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

[PR] Release of Apache Storm 2.6.2 (storm)

[via GitHub]

rzo1 opened a new pull request, #3634:
URL: https://github.com/apache/storm/pull/3634

   (no comment)


-- 
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: [PR] Scheduler needs to include acker memory for topology resources (storm)

[via GitHub]

rzo1 commented on PR #3633:
URL: https://github.com/apache/storm/pull/3633#issuecomment-2040176179

   @agresch guess you need to reset your ASF credentials via 
https://id.apache.org/reset/enter
   
   No blocker for that PR though. I can also create a Jira.


-- 
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: [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: [PR] Scheduler needs to include acker memory for topology resources (storm)

[via GitHub]

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] Apache Storm 2.6.2 (rc1)

[Richard Zowalla]

Here is my own +1 (binding)

Am Dienstag, dem 02.04.2024 um 10:32 +0200 schrieb Richard Zowalla:
> Hi all,
> 
> I have posted a first release candidate for Apache Storm 2.6.2 and it
> is ready for testing.
> 
> We upgraded libraries and pruned some dependencies which came in as
> transient dependencies.
> 
> Full list of changes in this release:
>   
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.2-rc1/RELEASE_NOTES.html
> 
> 
> The Nexus staging repository is here:
> 
> https://repository.apache.org/content/repositories/orgapachestorm-/
> 
> Storm Source and Binary Release with sha512 signature files are here:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.2-rc1/
>    
> The release artifacts are signed with my key contained in this file:
> 
> https://dist.apache.org/repos/dist/release/storm/KEYS
> 
> The release was made from the Apache Storm v2.6.2 tag at:
> 
> https://github.com/apache/storm/releases/tag/v2.6.2
> 
> 
> To use it in a maven build set the version for Storm to 2.6.2 and add
> the following to your POM:
> 
> 
> 
> 
> storm-2.6.2-rc1
> Testing Storm 2.6.2 RC1 
> 
> https://repository.apache.org/content/repositories/orgapachestorm-
> /
> 
> 
> 
> 
> 
> 
> The release was made using the Storm release process, documented on
> the
> GitHub repository:
> https://github.com/apache/storm/blob/master/RELEASING.md
> 
> Please vote on releasing these packages as Apache Storm 2.6.2.
> 
> The vote is open for at least the next 72 hours or as long as needed.
> 
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> 
> When voting, please list the actions taken to verify the release.
> 
> Only votes from the Storm PMC are binding, but everyone is welcome to
> check the release candidate and vote.
> 
> The vote passes if at least three binding +1 votes are cast.
> 
> [ ] +1 Release this package as Apache Storm 2.6.2
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> Thanks!
> 
> Richard
> 
> 

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

[via GitHub]

rzo1 commented on code in PR #3633:
URL: https://github.com/apache/storm/pull/3633#discussion_r1552209393


##
storm-server/src/main/java/org/apache/storm/utils/ServerUtils.java:
##
@@ -708,9 +708,24 @@ public static double 
getEstimatedTotalHeapMemoryRequiredByTopo(Map topologyConf)
+throws InvalidTopologyException {
+topology = StormCommon.systemTopology(topologyConf, topology);
+Map boltResources = 
ResourceUtils.getBoltsResources(topology, topologyConf);
+NormalizedResourceRequest entry = 
boltResources.get(Acker.ACKER_COMPONENT_ID);
+Map componentParallelism = 
getComponentParallelism(topologyConf, topology);
+int parallelism = 
componentParallelism.getOrDefault(Acker.ACKER_COMPONENT_ID, 1);
+return entry.getTotalMemoryMb() * parallelism;

Review Comment:
   is `entry`guaranteed to be not `null` since it comes out of a map, so maybe 
`getOrDefault(...)` earlier?



-- 
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: [PR] Scheduler needs to include acker memory for topology resources (storm)

[via GitHub]

rzo1 commented on code in PR #3633:
URL: https://github.com/apache/storm/pull/3633#discussion_r1552208523


##
storm-server/src/test/java/org/apache/storm/scheduler/blacklist/TestBlacklistScheduler.java:
##
@@ -20,22 +20,25 @@
 import com.google.common.collect.ImmutableList;
 import com.google.common.collect.ImmutableMap;
 import com.google.common.collect.Sets;
+import org.apache.logging.log4j.Level;
+import org.apache.logging.log4j.LogManager;
+import org.apache.logging.log4j.core.config.Configurator;
 import org.apache.storm.Config;
 import org.apache.storm.DaemonConfig;
-import org.apache.storm.scheduler.Cluster;
-import org.apache.storm.scheduler.DefaultScheduler;
-import org.apache.storm.scheduler.INimbus;
-import org.apache.storm.scheduler.IScheduler;
-import org.apache.storm.scheduler.SchedulerAssignmentImpl;
-import org.apache.storm.scheduler.SupervisorDetails;
-import org.apache.storm.scheduler.Topologies;
-import org.apache.storm.scheduler.TopologyDetails;
+import org.apache.storm.daemon.StormCommon;
+import org.apache.storm.generated.Bolt;
+import org.apache.storm.generated.InvalidTopologyException;
+import org.apache.storm.generated.SpoutSpec;
+import org.apache.storm.generated.StormTopology;
+import org.apache.storm.scheduler.*;

Review Comment:
   Can we avoid *-imports here?



-- 
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: [PR] Scheduler needs to include acker memory for topology resources (storm)

[via GitHub]

rzo1 commented on PR #3633:
URL: https://github.com/apache/storm/pull/3633#issuecomment-2037714316

   Great so let's put it for 2.6.3. Will do a review later 


-- 
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: [PR] Scheduler needs to include acker memory for topology resources (storm)

[via GitHub]

agresch commented on PR #3633:
URL: https://github.com/apache/storm/pull/3633#issuecomment-2037699322

   The bug has existed for ages.  I don't think it is critical.  


-- 
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: [PR] Scheduler needs to include acker memory for topology resources (storm)

[via GitHub]

rzo1 commented on PR #3633:
URL: https://github.com/apache/storm/pull/3633#issuecomment-2037650197

   @agresch how critical is this? Would you like to re-roll the current 2.6.2 
vote and include it or okay to wait for 2.6.3?


-- 
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

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

[via GitHub]

agresch opened a new pull request, #3633:
URL: https://github.com/apache/storm/pull/3633

   ## What is the purpose of the change
   
   The scheduler has a bug where acker memory is not considered in the 
scheduling estimate.  The case I found was where a topology should fit on two 
supervisors, but the cluster has 1 available and 2 blacklisted.  The scheduler 
thinks the topology should fit on one supervisor and fails to schedule, but 
also fails to release a supervisor from the blacklist, resulting in the 
topology never getting scheduled.
   
   With this fix, the scheduler properly detects the topology will need to be 
scheduled on two supervisors and releases one from the blacklist and schedules 
successfully.
   
   Switched some scheduling logs from trace to debug to make debugging 
scheduling issues easier.
   
   ## How was the change tested
   
   Added a unit test to validate the topology will properly schedule after 
releasing a supervisor from the blacklist.  The fix was also validated on our 
internal cluster integration tests.


-- 
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

Community over Code EU 2024: Start planning your trip!

[Ryan Skraba]

[Note: You're receiving this email because you are subscribed to one
or more project dev@ mailing lists at the Apache Software Foundation.]

Dear community,

We hope you are doing great, are you ready for Community Over Code EU?
Check out the featured sessions, get your tickets with special
discounts and start planning your trip.

Save your spot! Take a look at our lineup of sessions, panelists and
featured speakers and make your final choice:

* EU policies and regulations affecting open source specialists working in OSPOs

The panel will discuss how EU legislation affects the daily work of
open source operations. Panelists will cover some recent policy
updates, the challenges of staying compliant when managing open source
contribution and usage within organizations, and their personal
experiences in adapting to the changing European regulatory
environment.

* Doing for sustainability, what open source did for software

In this keynote Asim Hussain will explain the history of Impact
Framework, a coalition of hundreds of software practitioners with
tangible solutions that directly foster meaningful change by measuring
the environmental impacts of a piece of software.

Don’t forget that we have special discounts for groups, students and
Apache committers. Visit the website to discover more about these
rates.[1]

It's time for you to start planning your trip. Remember that we have
prepared a “How to get there” guide that will be helpful to find out
the best transportation, either train, bus, flight or boat to
Bratislava from wherever you are coming from. Take a look at the
different options and please reach out to us if you have any
questions.

We have available rooms -with a special rate- at the Radisson Blu
Carlton Hotel, where the event will take place and at the Park Inn
Hotel which is only 5 minutes walking from the venue. [2] However, you
are free to choose any other accommodation options around the city.

See you in Bratislava,
Community Over Code EU Team

[1]: https://eu.communityovercode.org/tickets/ "Register"
[2]: https://eu.communityovercode.org/venue/ "Where to stay"

Participate in the ASF 25th Anniversary Campaign

[Brian Proffitt]

Hi everyone,

As part of The ASF’s 25th anniversary campaign[1], we will be celebrating
projects and communities in multiple ways.

We invite all projects and contributors to participate in the following
ways:

* Individuals - submit your first contribution:
https://news.apache.org/foundation/entry/the-asf-launches-firstasfcontribution-campaign
* Projects - share your public good story:
https://docs.google.com/forms/d/1vuN-tUnBwpTgOE5xj3Z5AG1hsOoDNLBmGIqQHwQT6k8/viewform?edit_requested=true
* Projects - submit a project spotlight for the blog:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=278466116
* Projects - contact the Voice of Apache podcast (formerly Feathercast) to
be featured: https://feathercast.apache.org/help/
*  Projects - use the 25th anniversary template and the #ASF25Years hashtag
on social media:
https://docs.google.com/presentation/d/1oDbMol3F_XQuCmttPYxBIOIjRuRBksUjDApjd8Ve3L8/edit#slide=id.g26b0919956e_0_13

If you have questions, email the Marketing & Publicity team at
mark...@apache.org.

Peace,
BKP

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

[NOTE: You are receiving this message because you are a contributor to an
Apache Software Foundation project. The ASF will very occasionally send out
messages relating to the Foundation to contributors and members, such as
this one.]

Brian Proffitt
VP, Marketing & Publicity
VP, Conferences

Re: [VOTE] Apache Storm 2.6.2 (rc1)

[Alexandre Vermeerbergen]

+1 (binding)

tested on my pre-production Storm cluster with 15 topologies on 6
supervisor nodes (and 3 zookeeper nodes), since all topologies relying
on Apache Kafka topics (with kafka-monitoring showing lags per
partitions & per topic in Storm UI, this time it's not broken ;) and
some topologies relying on old Storm HDFS stuff. All this powevered by
IBM Semeru 21 (aka OpenJ9 JVM, at Java runtime 21, but code is still
built with a JDK17) on Redhat Linux 8.

I have observed no functional regression, topologies global latency is
same as with Storm 2.6.1, same for Supervision CPU/Memory/IOPS usage.

Disclaimer : I haven't yet updated built-time dependencies of
topologies, whose "BigJars" are still relying on Storm 2.6.1
dependencies (but that's good to check that topologies built from
version N-1 still run with Storm version N, for those willing to do
"rolling upgrades".

Many thanks Richard for the great work at providing this release for votes!

Alexandre

Le mer. 3 avr. 2024 à 09:53, Julien Nioche
 a écrit :
>
> Thanks Richard
>
> +1 (binding) Release this package as Apache Storm 2.6.2
>
>
>- checked the signatures for the release candidate
>- successfully built Storm from the source
>- ran a local and distributed topology
>
>
> On Tue, 2 Apr 2024 at 09:32, Richard Zowalla  wrote:
>
> > Hi all,
> >
> > I have posted a first release candidate for Apache Storm 2.6.2 and it
> > is ready for testing.
> >
> > We upgraded libraries and pruned some dependencies which came in as
> > transient dependencies.
> >
> > Full list of changes in this release:
> >
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.2-rc1/RELEASE_NOTES.html
> >
> >
> > The Nexus staging repository is here:
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-/
> >
> > Storm Source and Binary Release with sha512 signature files are here:
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.2-rc1/
> >
> > The release artifacts are signed with my key contained in this file:
> >
> > https://dist.apache.org/repos/dist/release/storm/KEYS
> >
> > The release was made from the Apache Storm v2.6.2 tag at:
> >
> > https://github.com/apache/storm/releases/tag/v2.6.2
> >
> >
> > To use it in a maven build set the version for Storm to 2.6.2 and add
> > the following to your POM:
> >
> >
> > 
> > 
> > storm-2.6.2-rc1
> > Testing Storm 2.6.2 RC1 
> > 
> > https://repository.apache.org/content/repositories/orgapachestorm-/
> >
> > 
> > 
> > 
> >
> >
> > The release was made using the Storm release process, documented on the
> > GitHub repository:
> > https://github.com/apache/storm/blob/master/RELEASING.md
> >
> > Please vote on releasing these packages as Apache Storm 2.6.2.
> >
> > The vote is open for at least the next 72 hours or as long as needed.
> >
> > "How to vote" is described here:
> >
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >
> > When voting, please list the actions taken to verify the release.
> >
> > Only votes from the Storm PMC are binding, but everyone is welcome to
> > check the release candidate and vote.
> >
> > The vote passes if at least three binding +1 votes are cast.
> >
> > [ ] +1 Release this package as Apache Storm 2.6.2
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > Thanks!
> >
> > Richard
> >
> >
> >
>
> --
> *Julien Nioche *
>
>
> digitalpebble.com 

Re: [VOTE] Apache Storm 2.6.2 (rc1)

[Julien Nioche]

Thanks Richard

+1 (binding) Release this package as Apache Storm 2.6.2


   - checked the signatures for the release candidate
   - successfully built Storm from the source
   - ran a local and distributed topology


On Tue, 2 Apr 2024 at 09:32, Richard Zowalla  wrote:

> Hi all,
>
> I have posted a first release candidate for Apache Storm 2.6.2 and it
> is ready for testing.
>
> We upgraded libraries and pruned some dependencies which came in as
> transient dependencies.
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.2-rc1/RELEASE_NOTES.html
>
>
> The Nexus staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapachestorm-/
>
> Storm Source and Binary Release with sha512 signature files are here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.2-rc1/
>
> The release artifacts are signed with my key contained in this file:
>
> https://dist.apache.org/repos/dist/release/storm/KEYS
>
> The release was made from the Apache Storm v2.6.2 tag at:
>
> https://github.com/apache/storm/releases/tag/v2.6.2
>
>
> To use it in a maven build set the version for Storm to 2.6.2 and add
> the following to your POM:
>
>
> 
> 
> storm-2.6.2-rc1
> Testing Storm 2.6.2 RC1 
> 
> https://repository.apache.org/content/repositories/orgapachestorm-/
>
> 
> 
> 
>
>
> The release was made using the Storm release process, documented on the
> GitHub repository:
> https://github.com/apache/storm/blob/master/RELEASING.md
>
> Please vote on releasing these packages as Apache Storm 2.6.2.
>
> The vote is open for at least the next 72 hours or as long as needed.
>
> "How to vote" is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>
> When voting, please list the actions taken to verify the release.
>
> Only votes from the Storm PMC are binding, but everyone is welcome to
> check the release candidate and vote.
>
> The vote passes if at least three binding +1 votes are cast.
>
> [ ] +1 Release this package as Apache Storm 2.6.2
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> Thanks!
>
> Richard
>
>
>

-- 
*Julien Nioche *


digitalpebble.com 

[VOTE] Apache Storm 2.6.2 (rc1)

[Richard Zowalla]

Hi all,

I have posted a first release candidate for Apache Storm 2.6.2 and it
is ready for testing.

We upgraded libraries and pruned some dependencies which came in as
transient dependencies.

Full list of changes in this release:
  
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.2-rc1/RELEASE_NOTES.html


The Nexus staging repository is here:

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

Storm Source and Binary Release with sha512 signature files are here:

https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.2-rc1/
   
The release artifacts are signed with my key contained in this file:

https://dist.apache.org/repos/dist/release/storm/KEYS

The release was made from the Apache Storm v2.6.2 tag at:

https://github.com/apache/storm/releases/tag/v2.6.2


To use it in a maven build set the version for Storm to 2.6.2 and add
the following to your POM:




storm-2.6.2-rc1
Testing Storm 2.6.2 RC1 
https://repository.apache.org/content/repositories/orgapachestorm-/






The release was made using the Storm release process, documented on the
GitHub repository:
https://github.com/apache/storm/blob/master/RELEASING.md

Please vote on releasing these packages as Apache Storm 2.6.2.

The vote is open for at least the next 72 hours or as long as needed.

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

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

Only votes from the Storm PMC are binding, but everyone is welcome to
check the release candidate and vote.

The vote passes if at least three binding +1 votes are cast.

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

Thanks to everyone who contributed to this release.

Thanks!

Richard

Re: [DISCUSS] Release 2.6.2 ?

[Alexandre Vermeerbergen]

+1 and I commit that I will test 2.6.2RC with by large set of
topologies on my preproduction !

Alexandre

Le jeu. 28 mars 2024 à 15:45, Julien Nioche
 a écrit :
>
> +1 from me
>
>
> On Thu, 28 Mar 2024 at 13:58, Richard Zowalla  wrote:
>
> > Hi,
> >
> > any objections in doing a 2.6.2 after eastern?
> >
> > We have some CVE fixes, so might be worth making a small update?
> >
> > WDYT?
> >
> > Best
> > Richard
> >
>
>
> --
> *Julien Nioche *
>
>
> digitalpebble.com 

Re: [DISCUSS] Release 2.6.2 ?

[Julien Nioche]

+1 from me


On Thu, 28 Mar 2024 at 13:58, Richard Zowalla  wrote:

> Hi,
>
> any objections in doing a 2.6.2 after eastern?
>
> We have some CVE fixes, so might be worth making a small update?
>
> WDYT?
>
> Best
> Richard
>


-- 
*Julien Nioche *


digitalpebble.com 

Re: [PR] STORM-4042 - Bump org.clojure:clojure from 1.10.0 to 1.11.2 (storm)

[via GitHub]

rzo1 merged PR #3629:
URL: https://github.com/apache/storm/pull/3629


-- 
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: [PR] STORM-4041 - Bump org.apache.zookeeper:zookeeper from 3.9.1 to 3.9.2 (storm)

[via GitHub]

rzo1 merged PR #3630:
URL: https://github.com/apache/storm/pull/3630


-- 
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

[DISCUSS] Release 2.6.2 ?

[Richard Zowalla]

Hi,

any objections in doing a 2.6.2 after eastern?

We have some CVE fixes, so might be worth making a small update?

WDYT?

Best
Richard

Re: [PR] STORM-4040 Update Troubleshooting with workaround for Nimbus startup … (storm)

[via GitHub]

rzo1 merged PR #3632:
URL: https://github.com/apache/storm/pull/3632


-- 
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

[PR] STORM-4040 Update Troubleshooting with workaround for Nimbus startup … (storm)

[via GitHub]

Scomocouk opened a new pull request, #3632:
URL: https://github.com/apache/storm/pull/3632

   …issue on older CPUs
   
   ## What is the purpose of the change
   
   Addresses STORM-4040. This documentation update contains an explaination for 
Nimbus not startin up due to JVM illegal instruction exception on older CPUs. 
It also suggests two workarounds to get it working on the same CPU
   
   ## How was the change tested
   
   Documentation change only. (Verified workaround by swapping RocksdB from v8 
in Storm 2.5.0 to v6.x.x)


-- 
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

Community Over Code NA 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

[ You are receiving this email as a subscriber to one or more ASF project
dev or user
  mailing lists and is not being sent to you directly. It is important that
we reach all of our
  users and contributors/committers so that they may get a chance to
benefit from this.
  We apologise in advance if this doesn't interest you but it is on topic
for the mailing
  lists of the Apache Software Foundation; and it is important please that
you do not
  mark this as spam in your email client. Thank You! ]

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code NA 2024 are now
open!

We will be supporting Community over Code NA, Denver Colorado in
October 7th to the 10th 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Monday 6th May, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Denver, Colorado , October 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

Re: [PR] [STORM-4039] Bump org.apache.commons:commons-configuration2 from 2.9.0 to 2.10.1 (storm)

[via GitHub]

jnioche merged PR #3631:
URL: https://github.com/apache/storm/pull/3631


-- 
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: [PR] Bump org.apache.zookeeper:zookeeper from 3.9.1 to 3.9.2 (storm)

[via GitHub]

rzo1 commented on PR #3630:
URL: https://github.com/apache/storm/pull/3630#issuecomment-2000350198

@dependabot rebase.
   
   


-- 
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: [PR] Bump org.clojure:clojure from 1.10.0 to 1.11.2 (storm)

[via GitHub]

rzo1 commented on PR #3629:
URL: https://github.com/apache/storm/pull/3629#issuecomment-2000349989

@dependabot rebase.
   
   


-- 
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: [PR] STORM-4038 - Cleanup Hadoop/HDFS dependencies (storm)

[via GitHub]

rzo1 merged PR #3628:
URL: https://github.com/apache/storm/pull/3628


-- 
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

[PR] Bump org.apache.zookeeper:zookeeper from 3.9.1 to 3.9.2 (storm)

[via GitHub]

dependabot[bot] opened a new pull request, #3630:
URL: https://github.com/apache/storm/pull/3630

   Bumps org.apache.zookeeper:zookeeper from 3.9.1 to 3.9.2.
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.zookeeper:zookeeper=maven=3.9.1=3.9.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot show  ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/storm/network/alerts).
   
   


-- 
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

[PR] Bump org.clojure:clojure from 1.10.0 to 1.11.2 (storm)

[via GitHub]

dependabot[bot] opened a new pull request, #3629:
URL: https://github.com/apache/storm/pull/3629

   Bumps [org.clojure:clojure](https://github.com/clojure/clojure) from 1.10.0 
to 1.11.2.
   
   Changelog
   Sourced from https://github.com/clojure/clojure/blob/master/changes.md;>org.clojure:clojure's
 changelog.
   
   
   Changes to Clojure in Version 1.11.1
   
   https://clojure.atlassian.net/browse/CLJ-2701;>CLJ-2701
   Pin serialVersionUID for Keyword and ArraySeq back to 1.10.3 values to 
retain binary serialization
   
   Changes to Clojure in Version 1.11.0
   1 Compatibility
   1.1 Security
   Because XML external entity (XXE) attacks can be used to disclose local 
files using file schemes or relative paths in the system identifier, 
clojure.xml/parse now disables external entity processing by 
default.
   See: https://owasp.org/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing">https://owasp.org/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing
   This change disables the following SAX parser features:
   
   
http://apache.org/xml/features/nonvalidating/load-external-dtd
   http://xml.org/sax/features/external-general-entities
   http://xml.org/sax/features/external-parameter-entities
   
   If you rely on these features, modify your calls to 
clojure.xml/parse to explicitly
   supply startparse-sax function as the final argument:
   (clojure.xml/parse the-string clojure.xml/startparse-sax)
   This modification also works on prior Clojure versions.
   
   http://dev.clojure.org/jira/browse/CLJ-2611;>CLJ-2611 
clojure.xml now disables XXE processing by default
   
   1.2 Dependencies
   Updated dependencies:
   
   spec.alpha dependency to 0.3.218 - https://github.com/clojure/spec.alpha/blob/master/CHANGES.md;>changes
   core.specs.alpha dependency to 0.2.62 - https://github.com/clojure/core.specs.alpha/blob/master/CHANGES.md;>changes
   
   2 Features
   2.1 Keyword argument functions take a trailing map
   Keyword arguments are optional trailing variadic arguments of the form 
akey aval bkey bval...​.
   In Clojure 1.11, functions taking keyword arguments can now be passed a map 
instead of or in addition
   to and following the key/value pairs. When a lone map is passed, it is used 
for destructuring, else
   a trailing map is added to the key/value pair map by conj.
   Also see: https://clojure.org/news/2021/03/18/apis-serving-people-and-programs;>https://clojure.org/news/2021/03/18/apis-serving-people-and-programs
   
   https://clojure.atlassian.net/browse/CLJ-2603;>CLJ-2603 
Clojure keyword argument functions now also accept a map
   
   
   
   ... (truncated)
   
   
   Commits
   
   https://github.com/clojure/clojure/commit/218054f1f2ddfc69ef4f9d17f916de35e4a4effe;>218054f
 [maven-release-plugin] prepare release clojure-1.11.2
   https://github.com/clojure/clojure/commit/63474dbaf356cbbc38ed9bd9f3a01c5800b8a6c4;>63474db
 update pom to snapshot version
   https://github.com/clojure/clojure/commit/5366a0e9e6df8ade159772703da3ac32c352fcdc;>5366a0e
 add github actions to clojure-1.11-dev branch
   https://github.com/clojure/clojure/commit/777456f5f485ed42cee386344fbce891c559ec4e;>777456f
 CLJ-2839 Infinite seq class hashCode() is infinite loop
   https://github.com/clojure/clojure/commit/ce55092f2b2f5481d25cff6205470c1335760ef6;>ce55092
 [maven-release-plugin] prepare release clojure-1.11.1
   https://github.com/clojure/clojure/commit/cef38abac0d7139f4d38324290eaf2c40b8924a7;>cef38ab
 [maven-release-plugin] prepare for next development iteration
   https://github.com/clojure/clojure/commit/3f1c36d779a43b1951ddaa9cdf6250b1d739621b;>3f1c36d
 [maven-release-plugin] prepare release clojure-1.11.1-rc1
   https://github.com/clojure/clojure/commit/e917dcc003bdd56660d5057407ea7739d2736af2;>e917dcc
 Update changelog for 1.11.1
   https://github.com/clojure/clojure/commit/1da6b07722790e898faa261a816a7a070fd93ac5;>1da6b07
 CLJ-2701 Set serialVersionUIDs for Keyword and ArraySeq to retain 1.10.3 
values
   https://github.com/clojure/clojure/commit/48818bd96afc2c8ee8ee76075f7a186289c6517a;>48818bd
 [maven-release-plugin] prepare for next development iteration
   Additional commits viewable in https://github.com/clojure/clojure/compare/clojure-1.10.0...clojure-1.11.2;>compare
 view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.clojure:clojure=maven=1.10.0=1.11.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
 

[RESULT] Move Storm from JIRA to GitHub issues

[Julien Nioche]

The vote passes with 4 +1

Thanks for taking part. Let's get things in motion next week

Julien

On Thu, 29 Feb 2024 at 13:20, Kishor Patil 
wrote:

> +1
>
> Best regards,
> Kishor Patil
>
> > On Feb 28, 2024, at 4:37 PM, Bipin Prasad 
> wrote:
> >
> >  +1
> >On Wednesday, February 28, 2024 at 02:42:21 PM CST, Richard Zowalla <
> r...@apache.org> 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
> >
>


-- 
*Julien Nioche *


digitalpebble.com 

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

[Kishor Patil]

+1

Best regards,
Kishor Patil

> On Feb 28, 2024, at 4:37 PM, Bipin Prasad  
> wrote:
> 
>  +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: [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: [VOTE] Move Storm from JIRA to GitHub issues

[Richard Zowalla]

+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

[VOTE] Move Storm from JIRA to GitHub issues

[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: [PR] STORM-4035 - Remove ConfluentAvroSerializer (storm-hdfs) (storm)

[via GitHub]

jnioche merged PR #3627:
URL: https://github.com/apache/storm/pull/3627


-- 
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: [Discuss] Move Storm from JIRA to GitHub Issues

[Richard Zowalla]

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



signature.asc
Description: This is a digitally signed message part

Re: [PR] [STORM-4030] Dependency upgrades (storm)

[via GitHub]

jnioche merged PR #3626:
URL: https://github.com/apache/storm/pull/3626


-- 
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: [PR] [STORM-4030] Dependency upgrades (storm)

[via GitHub]

rzo1 commented on PR #3626:
URL: https://github.com/apache/storm/pull/3626#issuecomment-1959603586

   awesome


-- 
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: [PR] [STORM-4030] Dependency upgrades (storm)

[via GitHub]

jnioche commented on PR #3626:
URL: https://github.com/apache/storm/pull/3626#issuecomment-1959602138

   > Can we document the updated versions in the related Jira? Otherwise, it 
might be difficult for consumers to actually see the diff in the next release.
   
   done, see https://issues.apache.org/jira/browse/STORM-4030


-- 
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: [PR] [STORM-4030] Dependency upgrades (storm)

[via GitHub]

jnioche commented on code in PR #3626:
URL: https://github.com/apache/storm/pull/3626#discussion_r1499148766


##
pom.xml:
##
@@ -97,31 +97,31 @@
 9.4.53.v20231009
 0.2.3
 1.6.0
-2.0
+2.2
 4.5.14
 4.4.16
 2.0.1
 0.9.0
-32.1.3-jre
+33.0.0-jre
 1.0-rc4
-4.1.100.Final
+4.1.107.Final
 1.0.2
-2.21.1
-1.7.36
+2.23.0
+2.0.12
 3.2.6
 4.11.0
 3.9.1
 1.1.10.4
 0.9.94
 3.1.3
-3.3.6
+3.4.0

Review Comment:
   looks like it is still at the RC level
   https://github.com/apache/hadoop/tags



-- 
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: [PR] [STORM-4030] Dependency upgrades (storm)

[via GitHub]

jnioche commented on code in PR #3626:
URL: https://github.com/apache/storm/pull/3626#discussion_r1499147592


##
pom.xml:
##
@@ -97,31 +97,31 @@
 9.4.53.v20231009
 0.2.3
 1.6.0
-2.0
+2.2
 4.5.14
 4.4.16
 2.0.1
 0.9.0
-32.1.3-jre
+33.0.0-jre
 1.0-rc4
-4.1.100.Final
+4.1.107.Final
 1.0.2
-2.21.1
-1.7.36
+2.23.0
+2.0.12
 3.2.6
 4.11.0
 3.9.1
 1.1.10.4
 0.9.94
 3.1.3
-3.3.6
+3.4.0

Review Comment:
   The changes for 3.4.0 are not documented on 
https://hadoop.apache.org/docs/stable/ 
   Will revert for now, we can work out whether hadoop-auth is needed later



-- 
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: [PR] [STORM-4030] Dependency upgrades (storm)

[via GitHub]

rzo1 commented on code in PR #3626:
URL: https://github.com/apache/storm/pull/3626#discussion_r1499139290


##
pom.xml:
##
@@ -97,31 +97,31 @@
 9.4.53.v20231009
 0.2.3
 1.6.0
-2.0
+2.2
 4.5.14
 4.4.16
 2.0.1
 0.9.0
-32.1.3-jre
+33.0.0-jre
 1.0-rc4
-4.1.100.Final
+4.1.107.Final
 1.0.2
-2.21.1
-1.7.36
+2.23.0
+2.0.12

Review Comment:
   slf4j -> slf4j2 might require some changes in the log4j2 bindings used as 
the way the static logger bindings are loaded has changed in slf4j2. 



-- 
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: [PR] [STORM-4030] Dependency upgrades (storm)

[via GitHub]

rzo1 commented on code in PR #3626:
URL: https://github.com/apache/storm/pull/3626#discussion_r1499138646


##
pom.xml:
##
@@ -97,31 +97,31 @@
 9.4.53.v20231009
 0.2.3
 1.6.0
-2.0
+2.2
 4.5.14
 4.4.16
 2.0.1
 0.9.0
-32.1.3-jre
+33.0.0-jre
 1.0-rc4
-4.1.100.Final
+4.1.107.Final
 1.0.2
-2.21.1
-1.7.36
+2.23.0
+2.0.12
 3.2.6
 4.11.0
 3.9.1
 1.1.10.4
 0.9.94
 3.1.3
-3.3.6
+3.4.0

Review Comment:
   Looks like `3.4.0` purged `hadoop-auth` ? Isn't listed in 
https://mvnrepository.com/artifact/org.apache.hadoop/hadoop-auth anymore, so 
might be gone and needs migration?



-- 
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

[PR] [STORM-4030] Dependency upgrades (storm)

[via GitHub]

jnioche opened a new pull request, #3626:
URL: https://github.com/apache/storm/pull/3626

   ## What is the purpose of the change
   
   Update dependencies
   
   ## How was the change tested
   
   `mvn clean test` ran successfully


-- 
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: [Discuss] Move Storm from JIRA to GitHub Issues

[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: [Discuss] Move Storm from JIRA to GitHub Issues

[Julien Nioche]

I'd definitely be in favour of doing this.
Maybe if we were to migrate, the following tool would be useful ->
https://github.com/apache/infrastructure-jira-issues-importer

On Thu, 22 Feb 2024 at 11:18, Richard Zowalla  wrote:

> 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
>


-- 
*Julien Nioche *


digitalpebble.com 

[Discuss] Move Storm from JIRA to GitHub Issues

[Richard Zowalla]

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: [PR] STORM-4029 - Bump org.apache.commons:commons-compress from 1.21 to 1.26.0 (storm)

[via GitHub]

rzo1 merged PR #3625:
URL: https://github.com/apache/storm/pull/3625


-- 
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

[PR] Bump org.apache.commons:commons-compress from 1.21 to 1.26.0 (storm)

[via GitHub]

dependabot[bot] opened a new pull request, #3625:
URL: https://github.com/apache/storm/pull/3625

   Bumps org.apache.commons:commons-compress from 1.21 to 1.26.0.
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.commons:commons-compress=maven=1.21=1.26.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot show  ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/storm/network/alerts).
   
   


-- 
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

Community Over Code Asia 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code Asia 2024 are now
open!

We will be supporting Community over Code Asia, Hangzhou, China
July 26th - 28th, 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this year's applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Friday, May 10th, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you to
apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Hangzhou, China in July, 2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

Re: [PR] Bump nokogiri from 1.15.3 to 1.16.2 in /content [storm-site]

[via GitHub]

rzo1 merged PR #51:
URL: https://github.com/apache/storm-site/pull/51


-- 
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: [PR] Bump nokogiri from 1.15.3 to 1.16.2 [storm-site]

[via GitHub]

rzo1 merged PR #50:
URL: https://github.com/apache/storm-site/pull/50


-- 
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

[PR] Bump nokogiri from 1.15.3 to 1.16.2 [storm-site]

[via GitHub]

dependabot[bot] opened a new pull request, #50:
URL: https://github.com/apache/storm-site/pull/50

   Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.15.3 to 
1.16.2.
   
   Release notes
   Sourced from https://github.com/sparklemotion/nokogiri/releases;>nokogiri's 
releases.
   
   v1.16.2 / 2024-02-04
   Security
   
   [CRuby] Vendored libxml2 is updated to address CVE-2024-25062. See https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-xc9x-jj77-9p9j;>GHSA-xc9x-jj77-9p9j
 for more information.
   
   Dependencies
   
   [CRuby] Vendored libxml2 is updated to https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.5;>v2.12.5 
from v2.12.4. (https://github.com/flavorjones;>@​flavorjones)
   
   
   sha256 checksums:
   69ba15d2a2498324489ed63850997f0b8f684260114ea81116d3082f16551d2d  
nokogiri-1.16.2-aarch64-linux.gem
   6a05ce42e3587a40cf8936ece0beaa5d32922254215d2e8cf9ad40588bb42e57  
nokogiri-1.16.2-arm-linux.gem
   c957226c8e36b31be6a3afb8602e2128282bf8b40ea51016c4cd21aa2608d3f8  
nokogiri-1.16.2-arm64-darwin.gem
   122652bfc338cd8a54a692ac035e245e41fd3b8283299202ca26e7a7d50db310  
nokogiri-1.16.2-java.gem
   7344b5072ca69fc5bedb61cb01a3b765b93a27aae5a2a845c2ba7200e4345074  
nokogiri-1.16.2-x64-mingw-ucrt.gem
   a2a5e184a424111a0d5b77947986484920ad708009c667f061e8d02035c562dd  
nokogiri-1.16.2-x64-mingw32.gem
   833efddeb51a6c2c9f6356295623c2b2e0d50050d468695c59bd929162953323  
nokogiri-1.16.2-x86-linux.gem
   e67fc0418dffaff9dc8b1dc65f0605282c3fee9488832d0223b620b4319e0b53  
nokogiri-1.16.2-x86-mingw32.gem
   5def799e5f139f21a79d7cf71172313a7b6fb0e4b2a31ab9bd5d4ad305994539  
nokogiri-1.16.2-x86_64-darwin.gem
   5b146240ac6ec6c40fd4367623e74442bca45a542bd3282b1d4d18b07b8e5dfe  
nokogiri-1.16.2-x86_64-linux.gem
   68922ee5cde27497d995c46f2821957bae961947644eed2822d173daf7567f9c  
nokogiri-1.16.2.gem
   
   v1.16.1 / 2024-02-03
   Dependencies
   
   [CRuby] Vendored libxml2 is updated to https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.4;>v2.12.4 
from v2.12.3. (https://github.com/flavorjones;>@​flavorjones)
   
   Fixed
   
   [CRuby] XML::Reader defaults the encoding to UTF-8 if it's 
not specified in either the document or as a method parameter. Previously 
non-ASCII characters were serialized as NCRs in this case. https://redirect.github.com/sparklemotion/nokogiri/issues/2891;>#2891 
(https://github.com/flavorjones;>@​flavorjones)
   [CRuby] Restored support for compilation by GCC versions earlier than 
4.6, which was broken in v1.15.0 (540e9aee). https://redirect.github.com/sparklemotion/nokogiri/issues/3090;>#3090 
(https://github.com/adfoster-r7;>@​adfoster-r7)
   [CRuby] Patched upstream libxml2 to allow parsing HTML5 in the context 
of a namespaced node (e.g., foreign content like MathML). [#3112, https://redirect.github.com/sparklemotion/nokogiri/issues/3116;>#3116]
 (https://github.com/flavorjones;>@​flavorjones)
   [CRuby] Fixed a small memory leak in libgumbo (HTML5 parser) when the 
maximum tree depth limit is hit. [#3098, https://redirect.github.com/sparklemotion/nokogiri/issues/3100;>#3100]
 (https://github.com/stevecheckoway;>@​stevecheckoway)
   
   
   sha256 checksums:
   a541f35e5b9798a0c97300f9ee18f4217da2a2945a6d5499e4123b9018f9cafc  
nokogiri-1.16.1-aarch64-linux.gem
   6b82affd195000ab2f9c36cc08744ec2d2fcf6d8da88d59a2db67e83211f7c69  
nokogiri-1.16.1-arm-linux.gem
   /tr/table 
   
   
   ... (truncated)
   
   
   Changelog
   Sourced from https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md;>nokogiri's
 changelog.
   
   v1.16.2 / 2024-02-04
   Security
   
   [CRuby] Vendored libxml2 is updated to address CVE-2024-25062. See https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-xc9x-jj77-9p9j;>GHSA-xc9x-jj77-9p9j
 for more information.
   
   Dependencies
   
   [CRuby] Vendored libxml2 is updated to https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.5;>v2.12.5 
from v2.12.4. (https://github.com/flavorjones;>@​flavorjones)
   
   v1.16.1 / 2024-02-03
   Dependencies
   
   [CRuby] Vendored libxml2 is updated to https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.4;>v2.12.4 
from v2.12.3. (https://github.com/flavorjones;>@​flavorjones)
   
   Fixed
   
   [CRuby] XML::Reader defaults the encoding to UTF-8 if it's 
not specified in either the document or as a method parameter. Previously 
non-ASCII characters were serialized as NCRs in this case. https://redirect.github.com/sparklemotion/nokogiri/issues/2891;>#2891 
(https://github.com/flavorjones;>@​flavorjones)
   [CRuby] Restored support for compilation by GCC versions earlier than 
4.6, which was broken in v1.15.0 (540e9aee). https://redirect.github.com/sparklemotion/nokogiri/issues/3090;>#3090 
(https://github.com/adfoster-r7;>@​adfoster-r7)
   [CRuby] Patched upstream libxml2 to allow parsing HTML5 in the context 
of a namespaced node (e.g., foreign content like MathML). [#3112, 

[PR] Bump nokogiri from 1.15.3 to 1.16.2 in /content [storm-site]

[via GitHub]

dependabot[bot] opened a new pull request, #51:
URL: https://github.com/apache/storm-site/pull/51

   Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.15.3 to 
1.16.2.
   
   Release notes
   Sourced from https://github.com/sparklemotion/nokogiri/releases;>nokogiri's 
releases.
   
   v1.16.2 / 2024-02-04
   Security
   
   [CRuby] Vendored libxml2 is updated to address CVE-2024-25062. See https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-xc9x-jj77-9p9j;>GHSA-xc9x-jj77-9p9j
 for more information.
   
   Dependencies
   
   [CRuby] Vendored libxml2 is updated to https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.5;>v2.12.5 
from v2.12.4. (https://github.com/flavorjones;>@​flavorjones)
   
   
   sha256 checksums:
   69ba15d2a2498324489ed63850997f0b8f684260114ea81116d3082f16551d2d  
nokogiri-1.16.2-aarch64-linux.gem
   6a05ce42e3587a40cf8936ece0beaa5d32922254215d2e8cf9ad40588bb42e57  
nokogiri-1.16.2-arm-linux.gem
   c957226c8e36b31be6a3afb8602e2128282bf8b40ea51016c4cd21aa2608d3f8  
nokogiri-1.16.2-arm64-darwin.gem
   122652bfc338cd8a54a692ac035e245e41fd3b8283299202ca26e7a7d50db310  
nokogiri-1.16.2-java.gem
   7344b5072ca69fc5bedb61cb01a3b765b93a27aae5a2a845c2ba7200e4345074  
nokogiri-1.16.2-x64-mingw-ucrt.gem
   a2a5e184a424111a0d5b77947986484920ad708009c667f061e8d02035c562dd  
nokogiri-1.16.2-x64-mingw32.gem
   833efddeb51a6c2c9f6356295623c2b2e0d50050d468695c59bd929162953323  
nokogiri-1.16.2-x86-linux.gem
   e67fc0418dffaff9dc8b1dc65f0605282c3fee9488832d0223b620b4319e0b53  
nokogiri-1.16.2-x86-mingw32.gem
   5def799e5f139f21a79d7cf71172313a7b6fb0e4b2a31ab9bd5d4ad305994539  
nokogiri-1.16.2-x86_64-darwin.gem
   5b146240ac6ec6c40fd4367623e74442bca45a542bd3282b1d4d18b07b8e5dfe  
nokogiri-1.16.2-x86_64-linux.gem
   68922ee5cde27497d995c46f2821957bae961947644eed2822d173daf7567f9c  
nokogiri-1.16.2.gem
   
   v1.16.1 / 2024-02-03
   Dependencies
   
   [CRuby] Vendored libxml2 is updated to https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.4;>v2.12.4 
from v2.12.3. (https://github.com/flavorjones;>@​flavorjones)
   
   Fixed
   
   [CRuby] XML::Reader defaults the encoding to UTF-8 if it's 
not specified in either the document or as a method parameter. Previously 
non-ASCII characters were serialized as NCRs in this case. https://redirect.github.com/sparklemotion/nokogiri/issues/2891;>#2891 
(https://github.com/flavorjones;>@​flavorjones)
   [CRuby] Restored support for compilation by GCC versions earlier than 
4.6, which was broken in v1.15.0 (540e9aee). https://redirect.github.com/sparklemotion/nokogiri/issues/3090;>#3090 
(https://github.com/adfoster-r7;>@​adfoster-r7)
   [CRuby] Patched upstream libxml2 to allow parsing HTML5 in the context 
of a namespaced node (e.g., foreign content like MathML). [#3112, https://redirect.github.com/sparklemotion/nokogiri/issues/3116;>#3116]
 (https://github.com/flavorjones;>@​flavorjones)
   [CRuby] Fixed a small memory leak in libgumbo (HTML5 parser) when the 
maximum tree depth limit is hit. [#3098, https://redirect.github.com/sparklemotion/nokogiri/issues/3100;>#3100]
 (https://github.com/stevecheckoway;>@​stevecheckoway)
   
   
   sha256 checksums:
   a541f35e5b9798a0c97300f9ee18f4217da2a2945a6d5499e4123b9018f9cafc  
nokogiri-1.16.1-aarch64-linux.gem
   6b82affd195000ab2f9c36cc08744ec2d2fcf6d8da88d59a2db67e83211f7c69  
nokogiri-1.16.1-arm-linux.gem
   /tr/table 
   
   
   ... (truncated)
   
   
   Changelog
   Sourced from https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md;>nokogiri's
 changelog.
   
   v1.16.2 / 2024-02-04
   Security
   
   [CRuby] Vendored libxml2 is updated to address CVE-2024-25062. See https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-xc9x-jj77-9p9j;>GHSA-xc9x-jj77-9p9j
 for more information.
   
   Dependencies
   
   [CRuby] Vendored libxml2 is updated to https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.5;>v2.12.5 
from v2.12.4. (https://github.com/flavorjones;>@​flavorjones)
   
   v1.16.1 / 2024-02-03
   Dependencies
   
   [CRuby] Vendored libxml2 is updated to https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.12.4;>v2.12.4 
from v2.12.3. (https://github.com/flavorjones;>@​flavorjones)
   
   Fixed
   
   [CRuby] XML::Reader defaults the encoding to UTF-8 if it's 
not specified in either the document or as a method parameter. Previously 
non-ASCII characters were serialized as NCRs in this case. https://redirect.github.com/sparklemotion/nokogiri/issues/2891;>#2891 
(https://github.com/flavorjones;>@​flavorjones)
   [CRuby] Restored support for compilation by GCC versions earlier than 
4.6, which was broken in v1.15.0 (540e9aee). https://redirect.github.com/sparklemotion/nokogiri/issues/3090;>#3090 
(https://github.com/adfoster-r7;>@​adfoster-r7)
   [CRuby] Patched upstream libxml2 to allow parsing HTML5 in the context 
of a namespaced node (e.g., foreign content like MathML). [#3112, 

Community over Code EU 2024 Travel Assistance Applications now open!

[Gavin McDonald]

Hello to all users, contributors and Committers!

The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code EU 2024 are now
open!

We will be supporting Community over Code EU, Bratislava, Slovakia,
June 3th - 5th, 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Friday, March 1st, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

For those that will need a Visa to enter the Country - we advise you apply
now so that you have enough time in case of interview delays. So do not
wait until you know if you have been accepted or not.

We look forward to greeting many of you in Bratislava, Slovakia in June,
2024!

Kind Regards,

Gavin

(On behalf of the Travel Assistance Committee)

[ANNOUNCE] Apache Storm 2.6.1 Released

[Richard Zowalla]

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

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/2024/02/02/storm261-released.html

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

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

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.6.1/RELEASE_NOTES.html
[2] https://issues.apache.org/jira/browse/STORM


signature.asc
Description: This is a digitally signed message part

Re: [PR] Bump activesupport from 7.0.6 to 7.0.7.2 [storm-site]

[via GitHub]

rzo1 merged PR #47:
URL: https://github.com/apache/storm-site/pull/47


-- 
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: [PR] Bump activesupport from 7.0.6 to 7.0.7.2 in /content [storm-site]

[via GitHub]

rzo1 merged PR #48:
URL: https://github.com/apache/storm-site/pull/48


-- 
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

[RESULT] [VOTE] Release Apache Storm 2.6.1 (RC1)

[Richard Zowalla]

Hi all,

this vote passes with the following +1 being cast:

Julien Nioche (binding)
Alexandre Vermeerbergen (binding)
Richard Zowalla (binding)

Thanks to all voters. I'll proceed with the steps.

Gruß
Richard

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Richard Zowalla]

Here is my own +1 (binding)


Am Dienstag, dem 30.01.2024 um 09:42 +0100 schrieb Richard Zowalla:
> Hi ladies & lords,
> 
> I have posted a first release candidate for Apache Storm 2.6.1
> release
> and it is ready for testing.
> 
> We fixed a few bugs and upgraded libraries.
> 
> Full list of changes in this release: 
>    
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
> 
> 
> The Nexus staging repository is here:
> 
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1110/
> 
> Storm Source and Binary Release with sha512 signature files are here:
>     
> The release artifacts are signed with my key contained in this file:
> 
> https://dist.apache.org/repos/dist/release/storm/KEYS
> 
> The release was made from the Apache Storm v2.6.1 tag at:
> 
> https://github.com/apache/storm/releases/tag/v2.6.1
> 
> 
> To use it in a maven build set the version for Storm to 2.6.1 and add
> the following to your POM:
> 
> 
> 
> 
> storm-2.6.1-rc1
> Testing Storm 2.6.1 RC1 
> 
> https://repository.apache.org/content/repositories/orgapachestorm-
> 1110/
> 
> 
> 
> 
> 
> 
> The release was made using the Storm release process, documented on
> the
> GitHub repository:
> https://github.com/apache/storm/blob/master/RELEASING.md
> 
> Please vote on releasing these packages as Apache Storm 2.6.0. 
> 
> The vote is open for at least the next 72 hours or as long as needed.
> 
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> 
> When voting, please list the actions taken to verify the release.
> 
> Only votes from the Storm PMC are binding, but everyone is welcome to
> check the release candidate and vote.
> 
> The vote passes if at least three binding +1 votes are cast.
> 
> [ ] +1 Release this package as Apache Storm 2.6.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> Thanks!
> 
> Richard
> 

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Richard Zowalla]

Any more votes?

Am Dienstag, dem 30.01.2024 um 09:42 +0100 schrieb Richard Zowalla:
> Hi ladies & lords,
> 
> I have posted a first release candidate for Apache Storm 2.6.1
> release
> and it is ready for testing.
> 
> We fixed a few bugs and upgraded libraries.
> 
> Full list of changes in this release: 
>    
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
> 
> 
> The Nexus staging repository is here:
> 
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1110/
> 
> Storm Source and Binary Release with sha512 signature files are here:
>     
> The release artifacts are signed with my key contained in this file:
> 
> https://dist.apache.org/repos/dist/release/storm/KEYS
> 
> The release was made from the Apache Storm v2.6.1 tag at:
> 
> https://github.com/apache/storm/releases/tag/v2.6.1
> 
> 
> To use it in a maven build set the version for Storm to 2.6.1 and add
> the following to your POM:
> 
> 
> 
> 
> storm-2.6.1-rc1
> Testing Storm 2.6.1 RC1 
> 
> https://repository.apache.org/content/repositories/orgapachestorm-
> 1110/
> 
> 
> 
> 
> 
> 
> The release was made using the Storm release process, documented on
> the
> GitHub repository:
> https://github.com/apache/storm/blob/master/RELEASING.md
> 
> Please vote on releasing these packages as Apache Storm 2.6.0. 
> 
> The vote is open for at least the next 72 hours or as long as needed.
> 
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> 
> When voting, please list the actions taken to verify the release.
> 
> Only votes from the Storm PMC are binding, but everyone is welcome to
> check the release candidate and vote.
> 
> The vote passes if at least three binding +1 votes are cast.
> 
> [ ] +1 Release this package as Apache Storm 2.6.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 
> Thanks!
> 
> Richard
> 

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Alexandre Vermeerbergen]

[+1] binding

Tested this 2.6.1 RC1 using binary artifacts on my Storm preproduction
cluster (6 Supervisor VMs) after having rebuilt my 14 Storm topologies
with updated 2.6.1 RC1 dependencies (including storm-kafka-client and
storm-hdfs), on Redhat 8.7 Linux x64 and with IBM Semeru JDK  21.0.1
(aka OpenJ9 0.42.0)
=> everything runs fine compared to same setup with Storm 2.6.0, VM
resources (cpu, memory,iops) usage on Supervisors is quite the same as
usual
=> the very useful fix of [STORM-4025] - ClassCastException when
changing log level in Storm UI is fine with 2.6.1

Tthanks for this release !

Alexandre

Le mer. 31 janv. 2024 à 16:24, Julien Nioche
 a écrit :
>
> +1 to release this package as Apache Storm 2.6.1 (binding)
>
> Checked the *.asc and *.sha512
> Built from the source code and ran a StormCrawler topology successfully
>
> Thanks
>
> Julien
>
> On Tue, 30 Jan 2024 at 08:42, Richard Zowalla  wrote:
>
> > Hi ladies & lords,
> >
> > I have posted a first release candidate for Apache Storm 2.6.1 release
> > and it is ready for testing.
> >
> > We fixed a few bugs and upgraded libraries.
> >
> > Full list of changes in this release:
> >
> >
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
> >
> >
> > The Nexus staging repository is here:
> >
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-1110/
> >
> > Storm Source and Binary Release with sha512 signature files are here:
> >
> > The release artifacts are signed with my key contained in this file:
> >
> > https://dist.apache.org/repos/dist/release/storm/KEYS
> >
> > The release was made from the Apache Storm v2.6.1 tag at:
> >
> > https://github.com/apache/storm/releases/tag/v2.6.1
> >
> >
> > To use it in a maven build set the version for Storm to 2.6.1 and add
> > the following to your POM:
> >
> >
> > 
> > 
> > storm-2.6.1-rc1
> > Testing Storm 2.6.1 RC1 
> > 
> > https://repository.apache.org/content/repositories/orgapachestorm-1110/
> >
> > 
> > 
> > 
> >
> >
> > The release was made using the Storm release process, documented on the
> > GitHub repository:
> > https://github.com/apache/storm/blob/master/RELEASING.md
> >
> > Please vote on releasing these packages as Apache Storm 2.6.0.
> >
> > The vote is open for at least the next 72 hours or as long as needed.
> >
> > "How to vote" is described here:
> >
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >
> > When voting, please list the actions taken to verify the release.
> >
> > Only votes from the Storm PMC are binding, but everyone is welcome to
> > check the release candidate and vote.
> >
> > The vote passes if at least three binding +1 votes are cast.
> >
> > [ ] +1 Release this package as Apache Storm 2.6.1
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > Thanks!
> >
> > Richard
> >
> >
>
> --
> *Julien Nioche *
>
>
> digitalpebble.com 

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Julien Nioche]

+1 to release this package as Apache Storm 2.6.1 (binding)

Checked the *.asc and *.sha512
Built from the source code and ran a StormCrawler topology successfully

Thanks

Julien

On Tue, 30 Jan 2024 at 08:42, Richard Zowalla  wrote:

> Hi ladies & lords,
>
> I have posted a first release candidate for Apache Storm 2.6.1 release
> and it is ready for testing.
>
> We fixed a few bugs and upgraded libraries.
>
> Full list of changes in this release:
>
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
>
>
> The Nexus staging repository is here:
>
>
> https://repository.apache.org/content/repositories/orgapachestorm-1110/
>
> Storm Source and Binary Release with sha512 signature files are here:
>
> The release artifacts are signed with my key contained in this file:
>
> https://dist.apache.org/repos/dist/release/storm/KEYS
>
> The release was made from the Apache Storm v2.6.1 tag at:
>
> https://github.com/apache/storm/releases/tag/v2.6.1
>
>
> To use it in a maven build set the version for Storm to 2.6.1 and add
> the following to your POM:
>
>
> 
> 
> storm-2.6.1-rc1
> Testing Storm 2.6.1 RC1 
> 
> https://repository.apache.org/content/repositories/orgapachestorm-1110/
>
> 
> 
> 
>
>
> The release was made using the Storm release process, documented on the
> GitHub repository:
> https://github.com/apache/storm/blob/master/RELEASING.md
>
> Please vote on releasing these packages as Apache Storm 2.6.0.
>
> The vote is open for at least the next 72 hours or as long as needed.
>
> "How to vote" is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>
> When voting, please list the actions taken to verify the release.
>
> Only votes from the Storm PMC are binding, but everyone is welcome to
> check the release candidate and vote.
>
> The vote passes if at least three binding +1 votes are cast.
>
> [ ] +1 Release this package as Apache Storm 2.6.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> Thanks!
>
> Richard
>
>

-- 
*Julien Nioche *


digitalpebble.com 

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Alexandre Vermeerbergen]

Thanks for the clarification
=> I have upgraded my preproduction cluster with this 2.6.1
RC1,rebuilt all my topologies with 2.6.1 dependencies and deployed on
this preproduction cluster
=> so far sounds good, but I want to let it run at least for 24 hours
"at scale" (with a full day of processed data) & review the resulting
monitoring (on topologies métrics + supporting VMs cpu/memory/iops)
before casting my vote

Thanks,
Alexandre

Le mar. 30 janv. 2024 à 20:05, Richard Zowalla  a écrit :
>
> Hi,
>
> we do not ship "storm-kafka-client-*" since a few versions.
> It isn't contained in 2.3.0, 2.4.0, 2.5.0 and 2.6.0 (didn't check the
> others), so yes, it is intentional. (It is a collection of spouts /
> bolts, trident - so more or less something a user may want to use (or
> not)).
>
> The JAR itself is available via Maven:
>
> https://repository.apache.org/content/repositories/orgapachestorm-1110/org/apache/storm/storm-kafka-client/2.6.1/
>
> Hope it helps
> Richard
>
>
> Am Dienstag, dem 30.01.2024 um 16:02 +0100 schrieb Alexandre
> Vermeerbergen:
> > Other question: to test
> > https://issues.apache.org/jira/browse/STORM-4016 I would like to have
> > storm-kafka-client--2.6.1.jar, but it's not in
> > apache-storm-2.6.1.tar.gz archive (binary artifacts)
> > => is that intentional ?
> > => from where can I find torm-kafka-client--2.6.1.jar ?
> > (sorry if my questions sound trivial..)
> >
> > Alexandre
> >
> > Le mar. 30 janv. 2024 à 14:12, Richard Zowalla 
> > a écrit :
> > >
> > > Here is the missing link. It is located at the usual location:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/
> > >
> > > Thx for the hint!
> > >
> > >
> > > Am Dienstag, dem 30.01.2024 um 14:09 +0100 schrieb Alexandre
> > > Vermeerbergen:
> > > > Hi Richard,
> > > >
> > > > The link to "Storm Source and Binary Release with sha512
> > > > signature
> > > > files" is missing, can you please re-send the vote mail ?
> > > >
> > > > Thanks,
> > > > Alexandre
> > > >
> > > > Le mar. 30 janv. 2024 à 09:42, Richard Zowalla 
> > > > a
> > > > écrit :
> > > > >
> > > > > Hi ladies & lords,
> > > > >
> > > > > I have posted a first release candidate for Apache Storm 2.6.1
> > > > > release
> > > > > and it is ready for testing.
> > > > >
> > > > > We fixed a few bugs and upgraded libraries.
> > > > >
> > > > > Full list of changes in this release:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
> > > > >
> > > > >
> > > > > The Nexus staging repository is here:
> > > > >
> > > > >
> > > > > https://repository.apache.org/content/repositories/orgapachestorm-1110/
> > > > >
> > > > > Storm Source and Binary Release with sha512 signature files are
> > > > > here:
> > > > >
> > > > > The release artifacts are signed with my key contained in this
> > > > > file:
> > > > >
> > > > > https://dist.apache.org/repos/dist/release/storm/KEYS
> > > > >
> > > > > The release was made from the Apache Storm v2.6.1 tag at:
> > > > >
> > > > > https://github.com/apache/storm/releases/tag/v2.6.1
> > > > >
> > > > >
> > > > > To use it in a maven build set the version for Storm to 2.6.1
> > > > > and
> > > > > add
> > > > > the following to your POM:
> > > > >
> > > > >
> > > > > 
> > > > > 
> > > > > storm-2.6.1-rc1
> > > > > Testing Storm 2.6.1 RC1 
> > > > > 
> > > > > https://repository.apache.org/content/repositories/orgapachestorm
> > > > > -
> > > > > 1110/
> > > > >
> > > > > 
> > > > > 
> > > > > 
> > > > >
> > > > >
> > > > > The release was made using the Storm release process,
> > > > > documented on
> > > > > the
> > > > > GitHub repository:
> > > > > https://github.com/apache/storm/blob/master/RELEASING.md
> > > > >
> > > > > Please vote on releasing these packages as Apache Storm 2.6.0.
> > > > >
> > > > > The vote is open for at least the next 72 hours or as long as
> > > > > needed.
> > > > >
> > > > > "How to vote" is described here:
> > > > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > > > >
> > > > > When voting, please list the actions taken to verify the
> > > > > release.
> > > > >
> > > > > Only votes from the Storm PMC are binding, but everyone is
> > > > > welcome
> > > > > to
> > > > > check the release candidate and vote.
> > > > >
> > > > > The vote passes if at least three binding +1 votes are cast.
> > > > >
> > > > > [ ] +1 Release this package as Apache Storm 2.6.1
> > > > > [ ]  0 No opinion
> > > > > [ ] -1 Do not release this package because...
> > > > >
> > > > > Thanks to everyone who contributed to this release.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Richard
> > > > >
> > >
>

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Richard Zowalla]

Hi,

we do not ship "storm-kafka-client-*" since a few versions. 
It isn't contained in 2.3.0, 2.4.0, 2.5.0 and 2.6.0 (didn't check the
others), so yes, it is intentional. (It is a collection of spouts /
bolts, trident - so more or less something a user may want to use (or
not)).

The JAR itself is available via Maven:

https://repository.apache.org/content/repositories/orgapachestorm-1110/org/apache/storm/storm-kafka-client/2.6.1/

Hope it helps
Richard


Am Dienstag, dem 30.01.2024 um 16:02 +0100 schrieb Alexandre
Vermeerbergen:
> Other question: to test
> https://issues.apache.org/jira/browse/STORM-4016 I would like to have
> storm-kafka-client--2.6.1.jar, but it's not in
> apache-storm-2.6.1.tar.gz archive (binary artifacts)
> => is that intentional ?
> => from where can I find torm-kafka-client--2.6.1.jar ?
> (sorry if my questions sound trivial..)
> 
> Alexandre
> 
> Le mar. 30 janv. 2024 à 14:12, Richard Zowalla 
> a écrit :
> > 
> > Here is the missing link. It is located at the usual location:
> > 
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/
> > 
> > Thx for the hint!
> > 
> > 
> > Am Dienstag, dem 30.01.2024 um 14:09 +0100 schrieb Alexandre
> > Vermeerbergen:
> > > Hi Richard,
> > > 
> > > The link to "Storm Source and Binary Release with sha512
> > > signature
> > > files" is missing, can you please re-send the vote mail ?
> > > 
> > > Thanks,
> > > Alexandre
> > > 
> > > Le mar. 30 janv. 2024 à 09:42, Richard Zowalla 
> > > a
> > > écrit :
> > > > 
> > > > Hi ladies & lords,
> > > > 
> > > > I have posted a first release candidate for Apache Storm 2.6.1
> > > > release
> > > > and it is ready for testing.
> > > > 
> > > > We fixed a few bugs and upgraded libraries.
> > > > 
> > > > Full list of changes in this release:
> > > > 
> > > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
> > > > 
> > > > 
> > > > The Nexus staging repository is here:
> > > > 
> > > > 
> > > > https://repository.apache.org/content/repositories/orgapachestorm-1110/
> > > > 
> > > > Storm Source and Binary Release with sha512 signature files are
> > > > here:
> > > > 
> > > > The release artifacts are signed with my key contained in this
> > > > file:
> > > > 
> > > > https://dist.apache.org/repos/dist/release/storm/KEYS
> > > > 
> > > > The release was made from the Apache Storm v2.6.1 tag at:
> > > > 
> > > > https://github.com/apache/storm/releases/tag/v2.6.1
> > > > 
> > > > 
> > > > To use it in a maven build set the version for Storm to 2.6.1
> > > > and
> > > > add
> > > > the following to your POM:
> > > > 
> > > > 
> > > > 
> > > > 
> > > > storm-2.6.1-rc1
> > > > Testing Storm 2.6.1 RC1 
> > > > 
> > > > https://repository.apache.org/content/repositories/orgapachestorm
> > > > -
> > > > 1110/
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > The release was made using the Storm release process,
> > > > documented on
> > > > the
> > > > GitHub repository:
> > > > https://github.com/apache/storm/blob/master/RELEASING.md
> > > > 
> > > > Please vote on releasing these packages as Apache Storm 2.6.0.
> > > > 
> > > > The vote is open for at least the next 72 hours or as long as
> > > > needed.
> > > > 
> > > > "How to vote" is described here:
> > > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > > > 
> > > > When voting, please list the actions taken to verify the
> > > > release.
> > > > 
> > > > Only votes from the Storm PMC are binding, but everyone is
> > > > welcome
> > > > to
> > > > check the release candidate and vote.
> > > > 
> > > > The vote passes if at least three binding +1 votes are cast.
> > > > 
> > > > [ ] +1 Release this package as Apache Storm 2.6.1
> > > > [ ]  0 No opinion
> > > > [ ] -1 Do not release this package because...
> > > > 
> > > > Thanks to everyone who contributed to this release.
> > > > 
> > > > Thanks!
> > > > 
> > > > Richard
> > > > 
> > 

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Alexandre Vermeerbergen]

Other question: to test
https://issues.apache.org/jira/browse/STORM-4016 I would like to have
storm-kafka-client--2.6.1.jar, but it's not in
apache-storm-2.6.1.tar.gz archive (binary artifacts)
=> is that intentional ?
=> from where can I find torm-kafka-client--2.6.1.jar ?
(sorry if my questions sound trivial..)

Alexandre

Le mar. 30 janv. 2024 à 14:12, Richard Zowalla  a écrit :
>
> Here is the missing link. It is located at the usual location:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/
>
> Thx for the hint!
>
>
> Am Dienstag, dem 30.01.2024 um 14:09 +0100 schrieb Alexandre
> Vermeerbergen:
> > Hi Richard,
> >
> > The link to "Storm Source and Binary Release with sha512 signature
> > files" is missing, can you please re-send the vote mail ?
> >
> > Thanks,
> > Alexandre
> >
> > Le mar. 30 janv. 2024 à 09:42, Richard Zowalla  a
> > écrit :
> > >
> > > Hi ladies & lords,
> > >
> > > I have posted a first release candidate for Apache Storm 2.6.1
> > > release
> > > and it is ready for testing.
> > >
> > > We fixed a few bugs and upgraded libraries.
> > >
> > > Full list of changes in this release:
> > >
> > > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
> > >
> > >
> > > The Nexus staging repository is here:
> > >
> > >
> > > https://repository.apache.org/content/repositories/orgapachestorm-1110/
> > >
> > > Storm Source and Binary Release with sha512 signature files are
> > > here:
> > >
> > > The release artifacts are signed with my key contained in this
> > > file:
> > >
> > > https://dist.apache.org/repos/dist/release/storm/KEYS
> > >
> > > The release was made from the Apache Storm v2.6.1 tag at:
> > >
> > > https://github.com/apache/storm/releases/tag/v2.6.1
> > >
> > >
> > > To use it in a maven build set the version for Storm to 2.6.1 and
> > > add
> > > the following to your POM:
> > >
> > >
> > > 
> > > 
> > > storm-2.6.1-rc1
> > > Testing Storm 2.6.1 RC1 
> > > 
> > > https://repository.apache.org/content/repositories/orgapachestorm-
> > > 1110/
> > >
> > > 
> > > 
> > > 
> > >
> > >
> > > The release was made using the Storm release process, documented on
> > > the
> > > GitHub repository:
> > > https://github.com/apache/storm/blob/master/RELEASING.md
> > >
> > > Please vote on releasing these packages as Apache Storm 2.6.0.
> > >
> > > The vote is open for at least the next 72 hours or as long as
> > > needed.
> > >
> > > "How to vote" is described here:
> > > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > >
> > > When voting, please list the actions taken to verify the release.
> > >
> > > Only votes from the Storm PMC are binding, but everyone is welcome
> > > to
> > > check the release candidate and vote.
> > >
> > > The vote passes if at least three binding +1 votes are cast.
> > >
> > > [ ] +1 Release this package as Apache Storm 2.6.1
> > > [ ]  0 No opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks to everyone who contributed to this release.
> > >
> > > Thanks!
> > >
> > > Richard
> > >
>

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Richard Zowalla]

Here is the missing link. It is located at the usual location:

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

Thx for the hint!


Am Dienstag, dem 30.01.2024 um 14:09 +0100 schrieb Alexandre
Vermeerbergen:
> Hi Richard,
> 
> The link to "Storm Source and Binary Release with sha512 signature
> files" is missing, can you please re-send the vote mail ?
> 
> Thanks,
> Alexandre
> 
> Le mar. 30 janv. 2024 à 09:42, Richard Zowalla  a
> écrit :
> > 
> > Hi ladies & lords,
> > 
> > I have posted a first release candidate for Apache Storm 2.6.1
> > release
> > and it is ready for testing.
> > 
> > We fixed a few bugs and upgraded libraries.
> > 
> > Full list of changes in this release:
> > 
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
> > 
> > 
> > The Nexus staging repository is here:
> > 
> > 
> > https://repository.apache.org/content/repositories/orgapachestorm-1110/
> > 
> > Storm Source and Binary Release with sha512 signature files are
> > here:
> > 
> > The release artifacts are signed with my key contained in this
> > file:
> > 
> > https://dist.apache.org/repos/dist/release/storm/KEYS
> > 
> > The release was made from the Apache Storm v2.6.1 tag at:
> > 
> > https://github.com/apache/storm/releases/tag/v2.6.1
> > 
> > 
> > To use it in a maven build set the version for Storm to 2.6.1 and
> > add
> > the following to your POM:
> > 
> > 
> > 
> > 
> > storm-2.6.1-rc1
> > Testing Storm 2.6.1 RC1 
> > 
> > https://repository.apache.org/content/repositories/orgapachestorm-
> > 1110/
> > 
> > 
> > 
> > 
> > 
> > 
> > The release was made using the Storm release process, documented on
> > the
> > GitHub repository:
> > https://github.com/apache/storm/blob/master/RELEASING.md
> > 
> > Please vote on releasing these packages as Apache Storm 2.6.0.
> > 
> > The vote is open for at least the next 72 hours or as long as
> > needed.
> > 
> > "How to vote" is described here:
> > https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> > 
> > When voting, please list the actions taken to verify the release.
> > 
> > Only votes from the Storm PMC are binding, but everyone is welcome
> > to
> > check the release candidate and vote.
> > 
> > The vote passes if at least three binding +1 votes are cast.
> > 
> > [ ] +1 Release this package as Apache Storm 2.6.1
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> > 
> > Thanks to everyone who contributed to this release.
> > 
> > Thanks!
> > 
> > Richard
> > 

Re: [VOTE] Release Apache Storm 2.6.1 (RC1)

[Alexandre Vermeerbergen]

Hi Richard,

The link to "Storm Source and Binary Release with sha512 signature
files" is missing, can you please re-send the vote mail ?

Thanks,
Alexandre

Le mar. 30 janv. 2024 à 09:42, Richard Zowalla  a écrit :
>
> Hi ladies & lords,
>
> I have posted a first release candidate for Apache Storm 2.6.1 release
> and it is ready for testing.
>
> We fixed a few bugs and upgraded libraries.
>
> Full list of changes in this release:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html
>
>
> The Nexus staging repository is here:
>
>
> https://repository.apache.org/content/repositories/orgapachestorm-1110/
>
> Storm Source and Binary Release with sha512 signature files are here:
>
> The release artifacts are signed with my key contained in this file:
>
> https://dist.apache.org/repos/dist/release/storm/KEYS
>
> The release was made from the Apache Storm v2.6.1 tag at:
>
> https://github.com/apache/storm/releases/tag/v2.6.1
>
>
> To use it in a maven build set the version for Storm to 2.6.1 and add
> the following to your POM:
>
>
> 
> 
> storm-2.6.1-rc1
> Testing Storm 2.6.1 RC1 
> https://repository.apache.org/content/repositories/orgapachestorm-1110/
>
> 
> 
> 
>
>
> The release was made using the Storm release process, documented on the
> GitHub repository:
> https://github.com/apache/storm/blob/master/RELEASING.md
>
> Please vote on releasing these packages as Apache Storm 2.6.0.
>
> The vote is open for at least the next 72 hours or as long as needed.
>
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>
> When voting, please list the actions taken to verify the release.
>
> Only votes from the Storm PMC are binding, but everyone is welcome to
> check the release candidate and vote.
>
> The vote passes if at least three binding +1 votes are cast.
>
> [ ] +1 Release this package as Apache Storm 2.6.1
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> Thanks!
>
> Richard
>

[VOTE] Release Apache Storm 2.6.1 (RC1)

[Richard Zowalla]

Hi ladies & lords,

I have posted a first release candidate for Apache Storm 2.6.1 release
and it is ready for testing.

We fixed a few bugs and upgraded libraries.

Full list of changes in this release: 
   
https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.6.1-rc1/RELEASE_NOTES.html


The Nexus staging repository is here:


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

Storm Source and Binary Release with sha512 signature files are here:

The release artifacts are signed with my key contained in this file:

https://dist.apache.org/repos/dist/release/storm/KEYS

The release was made from the Apache Storm v2.6.1 tag at:

https://github.com/apache/storm/releases/tag/v2.6.1


To use it in a maven build set the version for Storm to 2.6.1 and add
the following to your POM:




storm-2.6.1-rc1
Testing Storm 2.6.1 RC1 
https://repository.apache.org/content/repositories/orgapachestorm-1110/






The release was made using the Storm release process, documented on the
GitHub repository:
https://github.com/apache/storm/blob/master/RELEASING.md

Please vote on releasing these packages as Apache Storm 2.6.0. 

The vote is open for at least the next 72 hours or as long as needed.

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

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

Only votes from the Storm PMC are binding, but everyone is welcome to
check the release candidate and vote.

The vote passes if at least three binding +1 votes are cast.

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

Thanks to everyone who contributed to this release.

Thanks!

Richard

Re: Storm 2.6.1 ?

[Alexandre Vermeerbergen]

I also updated my preproduction 10+ topologies with Storm snapshot
generated 20240128
=> everything runs fine and I confirm STORM-4025 is fixed !

Alex

Le lun. 29 janv. 2024 à 14:37, Julien Nioche
 a écrit :
>
> Hi,
>
> Ran a StormCrawler toplogy with a nightly - looking good, no issues found
> Can't see any outstanding PRs to merge in the short term so would +1 to
> releasing what we currently have as 2.6.1
>
> Thanks
>
> Julien
>
> On Fri, 26 Jan 2024 at 11:59, Julien Nioche 
> wrote:
>
> > +1 to a 2.6.1 release
> >
> > The nightlies are at https://nightlies.apache.org/storm/
> > A couple of changes were merged today, I'll try a nightly next week
> >
> > J
> >
> > On Fri, 26 Jan 2024 at 07:40, Richard Zowalla  wrote:
> >
> >> Hi all,
> >>
> >> we had some fixes and dependency updates in Storm since our last
> >> release.
> >>
> >> Any objections in going for a 2.6.1 soon? Any lib upgrades we need to
> >> include prior?
> >>
> >> Did someone test our nightlies already?
> >>
> >>
> >> Gruß
> >> Richard
> >>
> >
> >
> > --
> > *Julien Nioche *
> >
> >
> > digitalpebble.com 
> >
>
>
> --
> *Julien Nioche *
>
>
> digitalpebble.com 

Re: Storm 2.6.1 ?

[Julien Nioche]

Hi,

Ran a StormCrawler toplogy with a nightly - looking good, no issues found
Can't see any outstanding PRs to merge in the short term so would +1 to
releasing what we currently have as 2.6.1

Thanks

Julien

On Fri, 26 Jan 2024 at 11:59, Julien Nioche 
wrote:

> +1 to a 2.6.1 release
>
> The nightlies are at https://nightlies.apache.org/storm/
> A couple of changes were merged today, I'll try a nightly next week
>
> J
>
> On Fri, 26 Jan 2024 at 07:40, Richard Zowalla  wrote:
>
>> Hi all,
>>
>> we had some fixes and dependency updates in Storm since our last
>> release.
>>
>> Any objections in going for a 2.6.1 soon? Any lib upgrades we need to
>> include prior?
>>
>> Did someone test our nightlies already?
>>
>>
>> Gruß
>> Richard
>>
>
>
> --
> *Julien Nioche *
>
>
> digitalpebble.com 
>


-- 
*Julien Nioche *


digitalpebble.com 

Re: Community over Code EU 2024 Travel Assistance Applications now open!

[Alexandre Vermeerbergen]

Hi Julien,

It's very nice that your submitted a Sorm-related topic for this
conference, I wish your proposal to be accepted !

Unfortunately I won't be able to travel at that time, I hope to see
you in broadcasts or records of your future session (betting it'll be
accepted :)

Alex

Le sam. 27 janv. 2024 à 09:50, Julien Nioche
 a écrit :
>
> Dear Apache Storm community
>
> Below is a message from the Travel Assistance Committee (TAC) to announce
> that
> travel assistance applications for Community over Code EU 2024 are now open!
>
> I will be at the conference if my presentation on StormCrawler and Apache
> Storm is accepted.
> Anyone using or contributing to Apache Storm planning to attend?
>
> Cheers
>
> Julien
>
> ***
>
> We will be supporting Community over Code EU, Bratislava, Slovakia,
> June 3th - 5th, 2024.
>
> TAC exists to help those that would like to attend Community over Code
> events, but are unable to do so for financial reasons. For more info
> on this years applications and qualifying criteria, please visit the
> TAC website at < https://tac.apache.org/ >. Applications are already
> open on https://tac-apply.apache.org/, so don't delay!
>
> The Apache Travel Assistance Committee will only be accepting
> applications from those people that are able to attend the full event.
>
> Important: Applications close on Friday, March 1st, 2024.
>
> Applicants have until the the closing date above to submit their
> applications (which should contain as much supporting material as
> required to efficiently and accurately process their request), this
> will enable TAC to announce successful applications shortly
> afterwards.
>
> As usual, TAC expects to deal with a range of applications from a
> diverse range of backgrounds; therefore, we encourage (as always)
> anyone thinking about sending in an application to do so ASAP.
>
> We look forward to greeting many of you in Bratislava, Slovakia in June,
> 2024!
>
> Kind Regards,
>
> Chris
>
> (On behalf of the Travel Assistance Committee)
>
> When replying, please reply to travel-assista...@apache.org
>
> --
> *Julien Nioche *
> Director
>
>
> digitalpebble.com 

Community over Code EU 2024 Travel Assistance Applications now open!

[Julien Nioche]

Dear Apache Storm community

Below is a message from the Travel Assistance Committee (TAC) to announce
that
travel assistance applications for Community over Code EU 2024 are now open!

I will be at the conference if my presentation on StormCrawler and Apache
Storm is accepted.
Anyone using or contributing to Apache Storm planning to attend?

Cheers

Julien

***

We will be supporting Community over Code EU, Bratislava, Slovakia,
June 3th - 5th, 2024.

TAC exists to help those that would like to attend Community over Code
events, but are unable to do so for financial reasons. For more info
on this years applications and qualifying criteria, please visit the
TAC website at < https://tac.apache.org/ >. Applications are already
open on https://tac-apply.apache.org/, so don't delay!

The Apache Travel Assistance Committee will only be accepting
applications from those people that are able to attend the full event.

Important: Applications close on Friday, March 1st, 2024.

Applicants have until the the closing date above to submit their
applications (which should contain as much supporting material as
required to efficiently and accurately process their request), this
will enable TAC to announce successful applications shortly
afterwards.

As usual, TAC expects to deal with a range of applications from a
diverse range of backgrounds; therefore, we encourage (as always)
anyone thinking about sending in an application to do so ASAP.

We look forward to greeting many of you in Bratislava, Slovakia in June,
2024!

Kind Regards,

Chris

(On behalf of the Travel Assistance Committee)

When replying, please reply to travel-assista...@apache.org

-- 
*Julien Nioche *
Director


digitalpebble.com 

STORM-4021: Add worker hooks via storm.yaml configuration file

[Harish Madineni]

Why can't I add worker hooks via the storm.yaml configuration file?
Is it going to affect performance?
Any difference between adding a worker hook for a topology vs in configuration 
file? If any?

Re: Storm 2.6.1 ?

[Julien Nioche]

+1 to a 2.6.1 release

The nightlies are at https://nightlies.apache.org/storm/
A couple of changes were merged today, I'll try a nightly next week

J

On Fri, 26 Jan 2024 at 07:40, Richard Zowalla  wrote:

> Hi all,
>
> we had some fixes and dependency updates in Storm since our last
> release.
>
> Any objections in going for a 2.6.1 soon? Any lib upgrades we need to
> include prior?
>
> Did someone test our nightlies already?
>
>
> Gruß
> Richard
>


-- 
*Julien Nioche *


digitalpebble.com 

Re: [PR] STORM-4028 - Curator 5.6.0 (storm)

[via GitHub]

rzo1 merged PR #3624:
URL: https://github.com/apache/storm/pull/3624


-- 
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