The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/aliyun-topic-queue-counts has failed. Run started by GitHub user Frun1na (triggered by Frun1na).
Head commit for run: 41c11f2ec5573fda4298b3cdc8abec4b4cb1c078 / Apulupie <[email protected]> fix(topic): report queue counts a vendor cannot measure as unknown AliyunConverters.toTopicVO sets writeQueues and readQueues to 0 because the Aliyun ListTopics and GetTopic models carry no queue counts, so every Aliyun topic reports a topic without queues: the detail drawer shows 0, both CSV exports print 0, and the topic comparison reports queue drift against every other instance. The VO now carries queueCountsAvailable (default true, false for Aliyun) the way BrokerVO marks runtime statistics and TopicConsumerVO marks unreadable lag: the console renders the two counts as unknown when the vendor cannot measure them, the CSV exports leave the cells empty, the comparison skips the two fields unless both sides measured them, and the rebuild/sync actions no longer write the placeholder zeros back to the broker. The two AI tool contracts forward the flag too, with topic.yaml regenerated. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/38042959027 With regards, GitHub Actions via GitBox
