You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "yuz10 (via GitHub)" <gi...@apache.org> on 2023/02/22 02:44:06 UTC

[GitHub] [rocketmq] yuz10 opened a new issue, #6157: Incompatibility between 4.x and 5.x in message trace

yuz10 opened a new issue, #6157:
URL: https://github.com/apache/rocketmq/issues/6157

   The issue tracker is used for bug reporting purposes **ONLY** whereas feature request needs to follow the [RIP process](https://github.com/apache/rocketmq/wiki/RocketMQ-Improvement-Proposal). To avoid unnecessary duplication, please check whether there is a previous issue before filing a new one.
   
   It is recommended to start a discussion thread in the [mailing lists](http://rocketmq.apache.org/about/contact/) in cases of discussing your deployment plan, API clarification, and other non-bug-reporting issues.
   We welcome any friendly suggestions, bug fixes, collaboration, and other improvements.
   
   Please ensure that your bug report is clear and self-contained. Otherwise, it would take additional rounds of communication, thus more time, to understand the problem itself.
   
   Generally, fixing an issue goes through the following steps:
   1. Understand the issue reported;
   1. Reproduce the unexpected behavior locally;
   1. Perform root cause analysis to identify the underlying problem;
   1. Create test cases to cover the identified problem;
   1. Work out a solution to rectify the behavior and make the newly created test cases pass;
   1. Make a pull request and go through peer review;
   
   As a result, it would be very helpful yet challenging if you could provide an isolated project reproducing your reported issue. Anyway, please ensure your issue report is informative enough for the community to pick up. At a minimum, include the following hints:
   
   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do (The steps to reproduce)?
     If the client that send message trace is 4.x and the client that query message trace is 5.x, then messageType of the trace is wrong.
   - What is expected to see?
   
   - What did you see instead?
   
   2. Please tell us about your environment:
   
   3. Other information (e.g. detailed explanation, logs, related issues, suggestions on how to fix, etc):
    
   MessageType have different ordinal in 4.x and 5.x.
   ![image](https://user-images.githubusercontent.com/14816818/220507726-e2029d32-51c0-469e-b555-4c29fa80d332.png)
   - 4.x
   ![image](https://user-images.githubusercontent.com/14816818/220507298-d4fec1fe-4741-452f-a378-d66b92926823.png)
   - 5.x
   ![image](https://user-images.githubusercontent.com/14816818/220507378-de35dbf0-79a7-4d2b-b6f3-086c69cb7523.png)
   


-- 
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-unsubscribe@rocketmq.apache.org.apache.org

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


[GitHub] [rocketmq] vongosling closed issue #6157: Incompatibility between 4.x and 5.x in message trace

Posted by "vongosling (via GitHub)" <gi...@apache.org>.
vongosling closed issue #6157: Incompatibility between 4.x and 5.x in message trace
URL: https://github.com/apache/rocketmq/issues/6157


-- 
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-unsubscribe@rocketmq.apache.org

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