Re: [PR] Client configuration add namespace [rocketmq-clients]

2024-05-17 Thread via GitHub
RongtongJin merged PR #750: URL: https://github.com/apache/rocketmq-clients/pull/750 -- 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: commits-unsubscr...

(rocketmq-clients) branch master updated: Client configuration add namespace (#750)

2024-05-17 Thread jinrongtong
This is an automated email from the ASF dual-hosted git repository. jinrongtong pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/rocketmq-clients.git The following commit(s) were added to refs/heads/master by this push: new bc2a112b Client configuration add

[PR] chore(deps): bump com.google.guava:guava from 31.1-jre to 32.0.0-jre in /java [rocketmq-clients]

2024-05-17 Thread via GitHub
dependabot[bot] opened a new pull request, #756: URL: https://github.com/apache/rocketmq-clients/pull/756 Bumps [com.google.guava:guava](https://github.com/google/guava) from 31.1-jre to 32.0.0-jre. Release notes Sourced from https://github.com/google/guava/releases";>com.google.gu

[GH] (rocketmq-clients): Workflow run "Java Coverage" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Java Coverage" on rocketmq-clients.git has failed. Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]). Head commit for run: ff1c8e4ad6b80080966401acb58a0bd8db21f37e / dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> chore(deps):

[GH] (rocketmq-clients): Workflow run "Java Coverage" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Java Coverage" on rocketmq-clients.git has failed. Run started by GitHub user RongtongJin (triggered by RongtongJin). Head commit for run: bc2a112b092018061561966f8bbacefc9f111a5b / zhaohai <33314633+zhaohai...@users.noreply.github.com> Client configuration add namespace

[GH] (rocketmq-clients): Workflow run "Build" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Build" on rocketmq-clients.git has failed. Run started by GitHub user dependabot[bot] (triggered by dependabot[bot]). Head commit for run: ff1c8e4ad6b80080966401acb58a0bd8db21f37e / dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> chore(deps): bump com

(rocketmq-clients) branch dependabot/maven/java/com.google.guava-guava-32.0.0-jre created (now ff1c8e4a)

2024-05-17 Thread github-bot
This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/java/com.google.guava-guava-32.0.0-jre in repository https://gitbox.apache.org/repos/asf/rocketmq-clients.git at ff1c8e4a chore(deps): bump com.google.guava:guava in /

[GH] (rocketmq-clients): Workflow run "Golang Coverage" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Golang Coverage" on rocketmq-clients.git has failed. Run started by GitHub user RongtongJin (triggered by RongtongJin). Head commit for run: bc2a112b092018061561966f8bbacefc9f111a5b / zhaohai <33314633+zhaohai...@users.noreply.github.com> Client configuration add namespa

[GH] (rocketmq-clients): Workflow run "Rust Coverage" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Rust Coverage" on rocketmq-clients.git has failed. Run started by GitHub user RongtongJin (triggered by RongtongJin). Head commit for run: bc2a112b092018061561966f8bbacefc9f111a5b / zhaohai <33314633+zhaohai...@users.noreply.github.com> Client configuration add namespace

[GH] (rocketmq-clients): Workflow run "CPP Coverage" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "CPP Coverage" on rocketmq-clients.git has failed. Run started by GitHub user RongtongJin (triggered by RongtongJin). Head commit for run: bc2a112b092018061561966f8bbacefc9f111a5b / zhaohai <33314633+zhaohai...@users.noreply.github.com> Client configuration add namespace

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
drpmma commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2116988582 I could not reproducer your issue. The SimpleConsumer with fifo is basically using the pop orderly interface which is mostly server-side behavior. It seems that it is po

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117011809 > I could not reproduce your issue. > > The SimpleConsumer with fifo is basically using the pop orderly interface which is mostly server-side behavior. > > It seems tha

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117036502 > I could not reproduce your issue. > > The SimpleConsumer with fifo is basically using the pop orderly interface which is mostly server-side behavior. > > It seems tha

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
drpmma commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117046930 ```json "checkout-group":{ "attributes":{}, "brokerId":0, "consumeBroadcastEnable":true, "consumeEnable":true, "consumeFromMinEnable":true,

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
drpmma commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117053820 > When creating the consumer group, did you set it as a FIFO-ConsumerGroup? For reference, use the command `sh mqadmin updateSubGroup -n -g -c -o true.` You should set the

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117054651 > > When creating the consumer group, did you set it as a FIFO-ConsumerGroup? For reference, use the command `sh mqadmin updateSubGroup -n -g -c -o true.` > > You should s

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117055940 > > 创建消费者组时,是否将其设置为 FIFO-ConsumerGroup?作为参考,请使用命令`sh mqadmin updateSubGroup -n -g -c -o true.` > > 您应该设置选项 -o true 以在 updateSubGroup 时将 ConsumerMessageOrderly 设置为 true。

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117060945 > > When creating the consumer group, did you set it as a FIFO-ConsumerGroup? For reference, use the command `sh mqadmin updateSubGroup -n -g -c -o true.` > > You should s

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117069204 I copied this command exactly as it is, and it seems there are no errors. > > When creating the consumer group, did you set it as a FIFO-ConsumerGroup? For reference, use the

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork closed issue #8154: [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. URL: https://github.com/apache/rocketmq/issues/8154 -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117073495 Thank you again. I submitted a very foolish issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL a

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117081846 > > 创建消费者组时,是否将其设置为 FIFO-ConsumerGroup?作为参考,请使用命令`sh mqadmin updateSubGroup -n -g -c -o true.` > > 您应该设置选项 -o true 以在 updateSubGroup 时将 ConsumerMessageOrderly 设置为 true。

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117090261 my logs: ```sh ❯ ./bin/mqadmin updateTopic -c DefaultCluster -t checkout-topic-fifo -o true -n 127.0.0.1:9876 -a +message.type=FIFO create topic to 192.168.1.162:10911 succe

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
JanYork closed issue #8154: [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. URL: https://github.com/apache/rocketmq/issues/8154 -- This is an automated message from the Apache Git Service. To respond to the message,

[I] Update 5.0 updateSubGroup command in fifomessage doc [rocketmq-site]

2024-05-17 Thread via GitHub
drpmma opened a new issue, #640: URL: https://github.com/apache/rocketmq-site/issues/640 Update 5.0 updateSubGroup command version-5.0/04-featureBehavior/03fifomessage.md -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and us

Re: [I] [Bug] RocketMQ FIFO Topic still cannot guarantee message order for simple consumers even in sequential production scenarios. [rocketmq]

2024-05-17 Thread via GitHub
drpmma commented on issue #8154: URL: https://github.com/apache/rocketmq/issues/8154#issuecomment-2117113244 You should use `updateSubGroup` command to set ConsumerMessageOrderly field of group as `sh mqadmin updateSubGroup -n -g -c -o true.` And the document should be updated to

Re: [I] 请问如果topic不存在,会自动创建吗? [rocketmq-mqtt]

2024-05-17 Thread via GitHub
ChangingFond commented on issue #278: URL: https://github.com/apache/rocketmq-mqtt/issues/278#issuecomment-2117115510 No,you should create first topic in RocketMQ. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the UR

Re: [I] MQTT在jdk11环境无法启动 [rocketmq-mqtt]

2024-05-17 Thread via GitHub
ChangingFond commented on issue #273: URL: https://github.com/apache/rocketmq-mqtt/issues/273#issuecomment-2117120215 The error stack doesn't look like it's a JDK version related problem, you may check your server config instead. -- This is an automated message from the Apache Git Ser

[PR] Feature:支持CloudEvent事件写入OSS,OSS存储格式时间分区功能,按时间窗口和事件内容信息大小窗口攒批发送功能 [rocketmq-connect]

2024-05-17 Thread via GitHub
liiuzq-xiaobai opened a new pull request, #533: URL: https://github.com/apache/rocketmq-connect/pull/533 ## What is the purpose of the change 支持CloudEvent事件写入OSS,OSS存储格式时间分区功能,按时间窗口和事件内容信息大小窗口攒批发送功能 -- This is an automated message from the Apache Git Service. To respond to t

Re: [PR] Feature:支持CloudEvent事件写入OSS,OSS存储格式时间分区功能,按时间窗口和事件内容信息大小窗口攒批发送功能 [rocketmq-connect]

2024-05-17 Thread via GitHub
liiuzq-xiaobai closed pull request #533: Feature:支持CloudEvent事件写入OSS,OSS存储格式时间分区功能,按时间窗口和事件内容信息大小窗口攒批发送功能 URL: https://github.com/apache/rocketmq-connect/pull/533 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL ab

[PR] [ISSUE #640] Add Create subscriptionGroup in fifo message [rocketmq-site]

2024-05-17 Thread via GitHub
drpmma opened a new pull request, #641: URL: https://github.com/apache/rocketmq-site/pull/641 Please do not create a Pull Request without creating an issue first. ## What is the purpose of the change Add Create subscriptionGroup in fifo message ## Brief changelog Add

(rocketmq-site) branch new-official-website updated: [ISSUE #640] Add Create subscriptionGroup in fifo message (#641)

2024-05-17 Thread zhouxzhan
This is an automated email from the ASF dual-hosted git repository. zhouxzhan pushed a commit to branch new-official-website in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git The following commit(s) were added to refs/heads/new-official-website by this push: new b0e805f4d

Re: [PR] [ISSUE #640] Add Create subscriptionGroup in fifo message [rocketmq-site]

2024-05-17 Thread via GitHub
drpmma merged PR #641: URL: https://github.com/apache/rocketmq-site/pull/641 -- 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: commits-unsubscr...@rocketm

[I] [Bug] Transaction message data consistency violation problems: 1. transaction messages can be committed after check is triggered and returns COMMIT, causing committing the same message with identi

2024-05-17 Thread via GitHub
SeanJi213 opened a new issue, #8158: URL: https://github.com/apache/rocketmq/issues/8158 ### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I

[I] [Bug] Response should not be discarded even the channel is unwritable [rocketmq]

2024-05-17 Thread via GitHub
redlsz opened a new issue, #8159: URL: https://github.com/apache/rocketmq/issues/8159 ### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I hav

[PR] [ISSUE #8159] Fix proxy discarding response when channel is unwritable [rocketmq]

2024-05-17 Thread via GitHub
redlsz opened a new pull request, #8160: URL: https://github.com/apache/rocketmq/pull/8160 ### Which Issue(s) This PR Fixes Fixes #8159 ### Brief Description 1. do not check channel.isWritable when writeResponse 2. Reuse NettyRemotingAbstract.w

[GH] (rocketmq): Workflow run "Build and Run Tests by Bazel" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Build and Run Tests by Bazel" on rocketmq.git has failed. Run started by GitHub user redlsz (triggered by redlsz). Head commit for run: ad3b69f78321acff32360a463e4db1a27030d766 / redlsz Fix proxy AbstractRemotingActivity.writeResponse Report URL: https://github.com/apa

[GH] (rocketmq): Workflow run "E2E test for pull request" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "E2E test for pull request" on rocketmq.git has failed. Run started by GitHub user redlsz (triggered by redlsz). Head commit for run: 9bdc9db9c46873f948fad2bdac5cc14aa1918f57 / oopooa <41882826+oop...@users.noreply.github.com> [ISSUE #8155] Fix doc typo Report URL: https

[GH] (rocketmq): Workflow run "Coverage" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Coverage" on rocketmq.git has failed. Run started by GitHub user redlsz (triggered by redlsz). Head commit for run: ad3b69f78321acff32360a463e4db1a27030d766 / redlsz Fix proxy AbstractRemotingActivity.writeResponse Report URL: https://github.com/apache/rocketmq/actions/

[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has failed. Run started by GitHub user redlsz (triggered by redlsz). Head commit for run: ad3b69f78321acff32360a463e4db1a27030d766 / redlsz Fix proxy AbstractRemotingActivity.writeResponse Report URL: https://github.com/apa

Re: [I] build docker image [rocketmq]

2024-05-17 Thread via GitHub
github-actions[bot] closed issue #4704: build docker image URL: https://github.com/apache/rocketmq/issues/4704 -- 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

Re: [I] build docker image [rocketmq]

2024-05-17 Thread via GitHub
github-actions[bot] commented on issue #4704: URL: https://github.com/apache/rocketmq/issues/4704#issuecomment-2118511823 This issue was closed because it has been inactive for 3 days since being marked as stale. -- This is an automated message from the Apache Git Service. To respond to t

[GH] (rocketmq): Workflow run "Snapshot Daily Release Automation" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "Snapshot Daily Release Automation" on rocketmq.git has failed. Run started by GitHub user lizhanhui (triggered by lizhanhui). Head commit for run: 9bdc9db9c46873f948fad2bdac5cc14aa1918f57 / oopooa <41882826+oop...@users.noreply.github.com> [ISSUE #8155] Fix doc typo Re

[GH] (rocketmq): Workflow run "Build and Run Tests by Bazel" is working again!

2024-05-17 Thread GitBox
The GitHub Actions job "Build and Run Tests by Bazel" on rocketmq.git has succeeded. Run started by GitHub user yuz10 (triggered by yuz10). Head commit for run: 230fe546425afcb4750ae30a123b120ec503098d / yuzhou add to topic attributes Report URL: https://github.com/apache/rocketmq/actions/run

[GH] (rocketmq): Workflow run "E2E test for pull request" failed!

2024-05-17 Thread GitBox
The GitHub Actions job "E2E test for pull request" on rocketmq.git has failed. Run started by GitHub user yuz10 (triggered by yuz10). Head commit for run: 9bdc9db9c46873f948fad2bdac5cc14aa1918f57 / oopooa <41882826+oop...@users.noreply.github.com> [ISSUE #8155] Fix doc typo Report URL: https:/

[GH] (rocketmq): Workflow run "Coverage" is working again!

2024-05-17 Thread GitBox
The GitHub Actions job "Coverage" on rocketmq.git has succeeded. Run started by GitHub user yuz10 (triggered by yuz10). Head commit for run: 230fe546425afcb4750ae30a123b120ec503098d / yuzhou add to topic attributes Report URL: https://github.com/apache/rocketmq/actions/runs/9136451838 With re

[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" is working again!

2024-05-17 Thread GitBox
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has succeeded. Run started by GitHub user yuz10 (triggered by yuz10). Head commit for run: 230fe546425afcb4750ae30a123b120ec503098d / yuzhou add to topic attributes Report URL: https://github.com/apache/rocketmq/actions/run

Re: [I] [Bug] Using `rocketmq-client-java` appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED [rocketmq-clients]

2024-05-17 Thread via GitHub
xbhog commented on issue #742: URL: https://github.com/apache/rocketmq-clients/issues/742#issuecomment-2118662040 Has this issue been resolved? There is still a problem in 5.0.6 org.apache.rocketmq rocketmq-client-java 5.0.6 -- This is an automated message fro

Re: [I] [Bug] SimpleConsumer message is lost and not received. [rocketmq]

2024-05-17 Thread via GitHub
JanYork closed issue #8133: [Bug] SimpleConsumer message is lost and not received. URL: https://github.com/apache/rocketmq/issues/8133 -- 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 co

Re: [I] [Bug] Using `rocketmq-client-java` appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED [rocketmq-clients]

2024-05-17 Thread via GitHub
JanYork commented on issue #742: URL: https://github.com/apache/rocketmq-clients/issues/742#issuecomment-2118663770 > Has this issue been resolved? There is still a problem in 5.0.6 > > org.apache.rocketmq > rocketmq-client-java > 5.0.6 > There is no probl

Re: [I] [Bug] Using `rocketmq-client-java` appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED [rocketmq-clients]

2024-05-17 Thread via GitHub
xbhog commented on issue #742: URL: https://github.com/apache/rocketmq-clients/issues/742#issuecomment-2118666488 > > 这个问题解决了吗? 5.0.6 > > > > org.apache.rocketmq还是有问题 > > Rocketmq-client-java > > 5.0.6 > > 没问题,这不是未来的bug,而是我的疏忽,我没有启动rocketmq-proxy > > Has

Re: [I] [Bug] Using `rocketmq-client-java` appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED [rocketmq-clients]

2024-05-17 Thread via GitHub
xbhog commented on issue #742: URL: https://github.com/apache/rocketmq-clients/issues/742#issuecomment-2118666701 > > Has this issue been resolved? There is still a problem in 5.0.6 > > > > org.apache.rocketmq > > rocketmq-client-java > > 5.0.6 > > There is no problem, th

Re: [I] [Bug] Using `rocketmq-client-java` appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED [rocketmq-clients]

2024-05-17 Thread via GitHub
JanYork commented on issue #742: URL: https://github.com/apache/rocketmq-clients/issues/742#issuecomment-2118667158 > > > Has this issue been resolved? There is still a problem in 5.0.6 > > > > > > org.apache.rocketmq > > > rocketmq-client-java > > > 5.0.6 > > > > There i

Re: [I] [Bug] Using `rocketmq-client-java` appears: Expected the service ProducerImpl-0 [FAILED] to be RUNNING, but the service has FAILED [rocketmq-clients]

2024-05-17 Thread via GitHub
xbhog commented on issue #742: URL: https://github.com/apache/rocketmq-clients/issues/742#issuecomment-2118668124 > > > > Has this issue been resolved? There is still a problem in 5.0.6 > > > > org.apache.rocketmq > > > > rocketmq-client-java > > > > 5.0.6 > > > > > > > >