Topic Subscription exponential backoff not working properly (too many retries)

Description
What I am trying to do is set up a backend that subscribes to a Topic and in case of an error retries connecting indefinitely.
For testing I set the max attempts to a large number and I pointed the client to a non-existent local node (so that the connection fails each time)
const topicQuery = new TopicMessageQuery()
    .setTopicId(topicId).setMaxAttempts(Number.MAX_VALUE).setMaxBackoff(20000);

What I noticed is that the number of retries is rising unexpectedly fast. For debugging I added timestamp in the library TopicMessageQuery.js file in the MirrorChannel.makeServerStreamRequest function error handler:
console.warn(
                            `${(new Date()).toISOString()} - Error subscribing to topic ${
                                this._topicId != null
                                    ? this._topicId.toString()
                                    : "UNKNOWN"
                            } during attempt ${
                                this._attempt
                            }. Waiting ${delay} ms before next attempt: ${message}`,
                        );

As well as a console log in the timeout handler in the same function:
                        setTimeout(() => {
                            console.log(`${(new Date()).toISOString()} - Fire timeout for attempt ${attempt} (delay ${delay})`)
                            this._makeServerStreamRequest(client);
                        }, delay);

Please see the attached log.
After roughly 3 minutes there are about a 1000 retries with the max backoff time of 20s. I would expect it to be maximum of about 15-20 retries for these parameters.
What I noticed is that the error handler is executed twice for each error. Once with an Error class error and the second time with an object of the following form:
{
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}

I suppose this duplicated error handler execution leads to the unexpected exponential rise in the number of retries.
Could you please check this issue? It would also be great if you could add support for setting an indefinite number of max retries (perhaps a null or -1 value?)
Steps to reproduce

set up an empty node project (npm init)
install hashgraph sdk version v2.40.0
create the following file index.mjs

import {AccountId, Client, AccountBalanceQuery, TopicMessageQuery} from '@hashgraph/sdk';
import 'dotenv/config'

const localnodeaddress = "localhost";

const node = {};
node[`${localnodeaddress}:50211`] = new AccountId(3)
const client = Client.forNetwork(node).setMirrorNetwork(`${localnodeaddress}:5600`).setMaxExecutionTime(null);

const topicId = "0.0.1002"

// Subscribe to the topic
const topicQuery = new TopicMessageQuery()
    .setTopicId(topicId).setMaxAttempts(Number.MAX_VALUE).setMaxBackoff(20000);

topicQuery    .subscribe(client, null, (message) => {
        let messageAsString = Buffer.from(message.contents, "utf8").toString();
        console.log(
            `${message.consensusTimestamp.toDate()} Received: ${messageAsString}`
        );
    });

make sure that THERE IS NO localnode running at localhost:5600
run the code node index.mjs

Additional context
2024-04-01T09:32:53.966Z - Error subscribing to topic 0.0.3378616 during attempt 0. Waiting 250 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:32:53.967Z - Error subscribing to topic 0.0.3378616 during attempt 1. Waiting 500 ms before next attempt: No connection established
2024-04-01T09:32:54.217Z - Fire timeout for attempt 1 (delay 250)
2024-04-01T09:32:54.221Z - Error subscribing to topic 0.0.3378616 during attempt 2. Waiting 1000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:32:54.221Z - Error subscribing to topic 0.0.3378616 during attempt 3. Waiting 2000 ms before next attempt: No connection established
2024-04-01T09:32:54.467Z - Fire timeout for attempt 2 (delay 500)
2024-04-01T09:32:54.469Z - Error subscribing to topic 0.0.3378616 during attempt 4. Waiting 4000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:32:54.469Z - Error subscribing to topic 0.0.3378616 during attempt 5. Waiting 8000 ms before next attempt: No connection established
2024-04-01T09:32:55.221Z - Fire timeout for attempt 3 (delay 1000)
2024-04-01T09:32:55.222Z - Error subscribing to topic 0.0.3378616 during attempt 6. Waiting 16000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:32:55.222Z - Error subscribing to topic 0.0.3378616 during attempt 7. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:32:56.220Z - Fire timeout for attempt 4 (delay 2000)
2024-04-01T09:32:56.223Z - Error subscribing to topic 0.0.3378616 during attempt 8. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:32:56.223Z - Error subscribing to topic 0.0.3378616 during attempt 9. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:32:58.470Z - Fire timeout for attempt 5 (delay 4000)
2024-04-01T09:32:58.474Z - Error subscribing to topic 0.0.3378616 during attempt 10. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:32:58.474Z - Error subscribing to topic 0.0.3378616 during attempt 11. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:02.469Z - Fire timeout for attempt 6 (delay 8000)
2024-04-01T09:33:02.471Z - Error subscribing to topic 0.0.3378616 during attempt 12. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:02.471Z - Error subscribing to topic 0.0.3378616 during attempt 13. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:11.222Z - Fire timeout for attempt 7 (delay 16000)
2024-04-01T09:33:11.226Z - Error subscribing to topic 0.0.3378616 during attempt 14. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:11.226Z - Error subscribing to topic 0.0.3378616 during attempt 15. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:15.223Z - Fire timeout for attempt 8 (delay 20000)
2024-04-01T09:33:15.224Z - Error subscribing to topic 0.0.3378616 during attempt 16. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:15.224Z - Error subscribing to topic 0.0.3378616 during attempt 17. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:16.223Z - Fire timeout for attempt 9 (delay 20000)
2024-04-01T09:33:16.223Z - Error subscribing to topic 0.0.3378616 during attempt 18. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:16.224Z - Error subscribing to topic 0.0.3378616 during attempt 19. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:16.224Z - Fire timeout for attempt 10 (delay 20000)
2024-04-01T09:33:16.224Z - Error subscribing to topic 0.0.3378616 during attempt 20. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:16.224Z - Error subscribing to topic 0.0.3378616 during attempt 21. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:18.474Z - Fire timeout for attempt 11 (delay 20000)
2024-04-01T09:33:18.476Z - Error subscribing to topic 0.0.3378616 during attempt 22. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:18.476Z - Error subscribing to topic 0.0.3378616 during attempt 23. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:18.476Z - Fire timeout for attempt 12 (delay 20000)
2024-04-01T09:33:18.477Z - Error subscribing to topic 0.0.3378616 during attempt 24. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:18.477Z - Error subscribing to topic 0.0.3378616 during attempt 25. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:22.470Z - Fire timeout for attempt 13 (delay 20000)
2024-04-01T09:33:22.471Z - Error subscribing to topic 0.0.3378616 during attempt 26. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:22.472Z - Error subscribing to topic 0.0.3378616 during attempt 27. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:22.472Z - Fire timeout for attempt 14 (delay 20000)
2024-04-01T09:33:22.472Z - Error subscribing to topic 0.0.3378616 during attempt 28. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:22.472Z - Error subscribing to topic 0.0.3378616 during attempt 29. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:31.225Z - Fire timeout for attempt 15 (delay 20000)
2024-04-01T09:33:31.226Z - Fire timeout for attempt 16 (delay 20000)
2024-04-01T09:33:34.551Z - Error subscribing to topic 0.0.3378616 during attempt 30. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:34.551Z - Error subscribing to topic 0.0.3378616 during attempt 31. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:34.551Z - Error subscribing to topic 0.0.3378616 during attempt 32. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:34.551Z - Error subscribing to topic 0.0.3378616 during attempt 33. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:35.224Z - Fire timeout for attempt 17 (delay 20000)
2024-04-01T09:33:35.226Z - Fire timeout for attempt 18 (delay 20000)
2024-04-01T09:33:35.227Z - Error subscribing to topic 0.0.3378616 during attempt 34. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:35.227Z - Error subscribing to topic 0.0.3378616 during attempt 35. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:35.227Z - Error subscribing to topic 0.0.3378616 during attempt 36. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:35.227Z - Error subscribing to topic 0.0.3378616 during attempt 37. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:36.223Z - Fire timeout for attempt 19 (delay 20000)
2024-04-01T09:33:36.225Z - Error subscribing to topic 0.0.3378616 during attempt 38. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:36.225Z - Error subscribing to topic 0.0.3378616 during attempt 39. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:36.225Z - Fire timeout for attempt 20 (delay 20000)
2024-04-01T09:33:36.226Z - Error subscribing to topic 0.0.3378616 during attempt 40. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:36.226Z - Error subscribing to topic 0.0.3378616 during attempt 41. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:36.227Z - Fire timeout for attempt 21 (delay 20000)
2024-04-01T09:33:36.227Z - Error subscribing to topic 0.0.3378616 during attempt 42. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:36.227Z - Error subscribing to topic 0.0.3378616 during attempt 43. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:36.227Z - Fire timeout for attempt 22 (delay 20000)
2024-04-01T09:33:36.228Z - Error subscribing to topic 0.0.3378616 during attempt 44. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:36.228Z - Error subscribing to topic 0.0.3378616 during attempt 45. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:38.475Z - Fire timeout for attempt 23 (delay 20000)
2024-04-01T09:33:38.476Z - Error subscribing to topic 0.0.3378616 during attempt 46. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:38.476Z - Error subscribing to topic 0.0.3378616 during attempt 47. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:38.476Z - Fire timeout for attempt 24 (delay 20000)
2024-04-01T09:33:38.477Z - Error subscribing to topic 0.0.3378616 during attempt 48. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:38.477Z - Error subscribing to topic 0.0.3378616 during attempt 49. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:38.477Z - Fire timeout for attempt 25 (delay 20000)
2024-04-01T09:33:38.477Z - Error subscribing to topic 0.0.3378616 during attempt 50. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:38.477Z - Error subscribing to topic 0.0.3378616 during attempt 51. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:38.479Z - Fire timeout for attempt 26 (delay 20000)
2024-04-01T09:33:38.480Z - Error subscribing to topic 0.0.3378616 during attempt 52. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:38.480Z - Error subscribing to topic 0.0.3378616 during attempt 53. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:42.472Z - Fire timeout for attempt 27 (delay 20000)
2024-04-01T09:33:42.473Z - Error subscribing to topic 0.0.3378616 during attempt 54. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:42.473Z - Error subscribing to topic 0.0.3378616 during attempt 55. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:42.473Z - Fire timeout for attempt 28 (delay 20000)
2024-04-01T09:33:42.474Z - Error subscribing to topic 0.0.3378616 during attempt 56. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:42.474Z - Error subscribing to topic 0.0.3378616 during attempt 57. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:42.474Z - Fire timeout for attempt 29 (delay 20000)
2024-04-01T09:33:42.474Z - Error subscribing to topic 0.0.3378616 during attempt 58. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:42.474Z - Error subscribing to topic 0.0.3378616 during attempt 59. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:42.475Z - Fire timeout for attempt 30 (delay 20000)
2024-04-01T09:33:42.475Z - Error subscribing to topic 0.0.3378616 during attempt 60. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:42.475Z - Error subscribing to topic 0.0.3378616 during attempt 61. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:54.551Z - Fire timeout for attempt 31 (delay 20000)
2024-04-01T09:33:54.552Z - Error subscribing to topic 0.0.3378616 during attempt 62. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:54.552Z - Error subscribing to topic 0.0.3378616 during attempt 63. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:54.552Z - Fire timeout for attempt 32 (delay 20000)
2024-04-01T09:33:54.553Z - Error subscribing to topic 0.0.3378616 during attempt 64. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:54.553Z - Error subscribing to topic 0.0.3378616 during attempt 65. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:54.553Z - Fire timeout for attempt 33 (delay 20000)
2024-04-01T09:33:54.554Z - Error subscribing to topic 0.0.3378616 during attempt 66. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:54.554Z - Error subscribing to topic 0.0.3378616 during attempt 67. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:54.554Z - Fire timeout for attempt 34 (delay 20000)
2024-04-01T09:33:54.555Z - Error subscribing to topic 0.0.3378616 during attempt 68. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:54.555Z - Error subscribing to topic 0.0.3378616 during attempt 69. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:55.227Z - Fire timeout for attempt 35 (delay 20000)
2024-04-01T09:33:55.228Z - Error subscribing to topic 0.0.3378616 during attempt 70. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:55.228Z - Error subscribing to topic 0.0.3378616 during attempt 71. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:55.228Z - Fire timeout for attempt 36 (delay 20000)
2024-04-01T09:33:55.228Z - Error subscribing to topic 0.0.3378616 during attempt 72. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:55.228Z - Error subscribing to topic 0.0.3378616 during attempt 73. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:55.229Z - Fire timeout for attempt 37 (delay 20000)
2024-04-01T09:33:55.229Z - Error subscribing to topic 0.0.3378616 during attempt 74. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:55.229Z - Error subscribing to topic 0.0.3378616 during attempt 75. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:55.229Z - Fire timeout for attempt 38 (delay 20000)
2024-04-01T09:33:55.229Z - Error subscribing to topic 0.0.3378616 during attempt 76. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:55.229Z - Error subscribing to topic 0.0.3378616 during attempt 77. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:56.225Z - Fire timeout for attempt 39 (delay 20000)
2024-04-01T09:33:56.226Z - Error subscribing to topic 0.0.3378616 during attempt 78. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:56.226Z - Error subscribing to topic 0.0.3378616 during attempt 79. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:56.226Z - Fire timeout for attempt 40 (delay 20000)
2024-04-01T09:33:56.228Z - Error subscribing to topic 0.0.3378616 during attempt 80. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:56.228Z - Error subscribing to topic 0.0.3378616 during attempt 81. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:56.228Z - Fire timeout for attempt 41 (delay 20000)
2024-04-01T09:33:56.229Z - Error subscribing to topic 0.0.3378616 during attempt 82. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:56.229Z - Error subscribing to topic 0.0.3378616 during attempt 83. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:56.229Z - Fire timeout for attempt 42 (delay 20000)
2024-04-01T09:33:56.229Z - Error subscribing to topic 0.0.3378616 during attempt 84. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:56.229Z - Error subscribing to topic 0.0.3378616 during attempt 85. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:56.231Z - Fire timeout for attempt 43 (delay 20000)
2024-04-01T09:33:56.231Z - Error subscribing to topic 0.0.3378616 during attempt 86. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:56.232Z - Error subscribing to topic 0.0.3378616 during attempt 87. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:56.232Z - Fire timeout for attempt 44 (delay 20000)
2024-04-01T09:33:56.232Z - Error subscribing to topic 0.0.3378616 during attempt 88. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:56.232Z - Error subscribing to topic 0.0.3378616 during attempt 89. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:56.232Z - Fire timeout for attempt 45 (delay 20000)
2024-04-01T09:33:56.232Z - Error subscribing to topic 0.0.3378616 during attempt 90. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:56.232Z - Error subscribing to topic 0.0.3378616 during attempt 91. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:56.233Z - Fire timeout for attempt 46 (delay 20000)
2024-04-01T09:33:56.233Z - Error subscribing to topic 0.0.3378616 during attempt 92. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:56.233Z - Error subscribing to topic 0.0.3378616 during attempt 93. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:58.476Z - Fire timeout for attempt 47 (delay 20000)
2024-04-01T09:33:58.477Z - Error subscribing to topic 0.0.3378616 during attempt 94. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:58.477Z - Error subscribing to topic 0.0.3378616 during attempt 95. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:58.477Z - Fire timeout for attempt 48 (delay 20000)
2024-04-01T09:33:58.478Z - Error subscribing to topic 0.0.3378616 during attempt 96. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:58.478Z - Error subscribing to topic 0.0.3378616 during attempt 97. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:58.478Z - Fire timeout for attempt 49 (delay 20000)
2024-04-01T09:33:58.479Z - Error subscribing to topic 0.0.3378616 during attempt 98. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:58.479Z - Error subscribing to topic 0.0.3378616 during attempt 99. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:58.479Z - Fire timeout for attempt 50 (delay 20000)
2024-04-01T09:33:58.479Z - Error subscribing to topic 0.0.3378616 during attempt 100. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:58.479Z - Error subscribing to topic 0.0.3378616 during attempt 101. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:58.480Z - Fire timeout for attempt 51 (delay 20000)
2024-04-01T09:33:58.480Z - Error subscribing to topic 0.0.3378616 during attempt 102. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:58.481Z - Error subscribing to topic 0.0.3378616 during attempt 103. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:58.481Z - Fire timeout for attempt 52 (delay 20000)
2024-04-01T09:33:58.481Z - Error subscribing to topic 0.0.3378616 during attempt 104. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:58.481Z - Error subscribing to topic 0.0.3378616 during attempt 105. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:58.483Z - Fire timeout for attempt 53 (delay 20000)
2024-04-01T09:33:58.483Z - Error subscribing to topic 0.0.3378616 during attempt 106. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:58.483Z - Error subscribing to topic 0.0.3378616 during attempt 107. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:33:58.483Z - Fire timeout for attempt 54 (delay 20000)
2024-04-01T09:33:58.484Z - Error subscribing to topic 0.0.3378616 during attempt 108. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:33:58.484Z - Error subscribing to topic 0.0.3378616 during attempt 109. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:02.472Z - Fire timeout for attempt 55 (delay 20000)
2024-04-01T09:34:02.472Z - Error subscribing to topic 0.0.3378616 during attempt 110. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:02.473Z - Error subscribing to topic 0.0.3378616 during attempt 111. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:02.473Z - Fire timeout for attempt 56 (delay 20000)
2024-04-01T09:34:02.473Z - Error subscribing to topic 0.0.3378616 during attempt 112. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:02.473Z - Error subscribing to topic 0.0.3378616 during attempt 113. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:02.474Z - Fire timeout for attempt 57 (delay 20000)
2024-04-01T09:34:02.475Z - Error subscribing to topic 0.0.3378616 during attempt 114. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:02.475Z - Error subscribing to topic 0.0.3378616 during attempt 115. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:02.475Z - Fire timeout for attempt 58 (delay 20000)
2024-04-01T09:34:02.476Z - Error subscribing to topic 0.0.3378616 during attempt 116. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:02.476Z - Error subscribing to topic 0.0.3378616 during attempt 117. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:02.476Z - Fire timeout for attempt 59 (delay 20000)
2024-04-01T09:34:02.476Z - Error subscribing to topic 0.0.3378616 during attempt 118. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:02.476Z - Error subscribing to topic 0.0.3378616 during attempt 119. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:02.476Z - Fire timeout for attempt 60 (delay 20000)
2024-04-01T09:34:02.477Z - Error subscribing to topic 0.0.3378616 during attempt 120. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:02.477Z - Error subscribing to topic 0.0.3378616 during attempt 121. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:02.477Z - Fire timeout for attempt 61 (delay 20000)
2024-04-01T09:34:02.478Z - Error subscribing to topic 0.0.3378616 during attempt 122. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:02.478Z - Error subscribing to topic 0.0.3378616 during attempt 123. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:02.478Z - Fire timeout for attempt 62 (delay 20000)
2024-04-01T09:34:02.478Z - Error subscribing to topic 0.0.3378616 during attempt 124. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:02.478Z - Error subscribing to topic 0.0.3378616 during attempt 125. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:14.552Z - Fire timeout for attempt 63 (delay 20000)
2024-04-01T09:34:14.553Z - Error subscribing to topic 0.0.3378616 during attempt 126. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:14.553Z - Error subscribing to topic 0.0.3378616 during attempt 127. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:14.554Z - Fire timeout for attempt 64 (delay 20000)
2024-04-01T09:34:14.554Z - Error subscribing to topic 0.0.3378616 during attempt 128. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:14.554Z - Error subscribing to topic 0.0.3378616 during attempt 129. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:14.554Z - Fire timeout for attempt 65 (delay 20000)
2024-04-01T09:34:14.555Z - Error subscribing to topic 0.0.3378616 during attempt 130. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:14.555Z - Error subscribing to topic 0.0.3378616 during attempt 131. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:14.555Z - Fire timeout for attempt 66 (delay 20000)
2024-04-01T09:34:14.556Z - Error subscribing to topic 0.0.3378616 during attempt 132. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:14.556Z - Error subscribing to topic 0.0.3378616 during attempt 133. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:14.557Z - Fire timeout for attempt 67 (delay 20000)
2024-04-01T09:34:14.558Z - Error subscribing to topic 0.0.3378616 during attempt 134. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:14.558Z - Error subscribing to topic 0.0.3378616 during attempt 135. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:14.558Z - Fire timeout for attempt 68 (delay 20000)
2024-04-01T09:34:14.559Z - Error subscribing to topic 0.0.3378616 during attempt 136. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:14.559Z - Error subscribing to topic 0.0.3378616 during attempt 137. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:14.559Z - Fire timeout for attempt 69 (delay 20000)
2024-04-01T09:34:14.559Z - Error subscribing to topic 0.0.3378616 during attempt 138. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:14.559Z - Error subscribing to topic 0.0.3378616 during attempt 139. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:14.559Z - Fire timeout for attempt 70 (delay 20000)
2024-04-01T09:34:14.560Z - Error subscribing to topic 0.0.3378616 during attempt 140. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:14.560Z - Error subscribing to topic 0.0.3378616 during attempt 141. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:15.228Z - Fire timeout for attempt 71 (delay 20000)
2024-04-01T09:34:15.229Z - Error subscribing to topic 0.0.3378616 during attempt 142. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:15.229Z - Error subscribing to topic 0.0.3378616 during attempt 143. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:15.229Z - Fire timeout for attempt 72 (delay 20000)
2024-04-01T09:34:15.229Z - Error subscribing to topic 0.0.3378616 during attempt 144. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:15.230Z - Error subscribing to topic 0.0.3378616 during attempt 145. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:15.230Z - Fire timeout for attempt 73 (delay 20000)
2024-04-01T09:34:15.230Z - Error subscribing to topic 0.0.3378616 during attempt 146. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:15.230Z - Error subscribing to topic 0.0.3378616 during attempt 147. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:15.230Z - Fire timeout for attempt 74 (delay 20000)
2024-04-01T09:34:15.231Z - Error subscribing to topic 0.0.3378616 during attempt 148. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:15.231Z - Error subscribing to topic 0.0.3378616 during attempt 149. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:15.231Z - Fire timeout for attempt 75 (delay 20000)
2024-04-01T09:34:15.232Z - Error subscribing to topic 0.0.3378616 during attempt 150. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:15.232Z - Error subscribing to topic 0.0.3378616 during attempt 151. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:15.232Z - Fire timeout for attempt 76 (delay 20000)
2024-04-01T09:34:15.232Z - Error subscribing to topic 0.0.3378616 during attempt 152. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:15.232Z - Error subscribing to topic 0.0.3378616 during attempt 153. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:15.232Z - Fire timeout for attempt 77 (delay 20000)
2024-04-01T09:34:15.232Z - Error subscribing to topic 0.0.3378616 during attempt 154. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:15.233Z - Error subscribing to topic 0.0.3378616 during attempt 155. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:15.233Z - Fire timeout for attempt 78 (delay 20000)
2024-04-01T09:34:15.233Z - Error subscribing to topic 0.0.3378616 during attempt 156. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:15.234Z - Error subscribing to topic 0.0.3378616 during attempt 157. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.226Z - Fire timeout for attempt 79 (delay 20000)
2024-04-01T09:34:16.227Z - Error subscribing to topic 0.0.3378616 during attempt 158. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.228Z - Error subscribing to topic 0.0.3378616 during attempt 159. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.228Z - Fire timeout for attempt 80 (delay 20000)
2024-04-01T09:34:16.228Z - Error subscribing to topic 0.0.3378616 during attempt 160. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.228Z - Error subscribing to topic 0.0.3378616 during attempt 161. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.228Z - Fire timeout for attempt 81 (delay 20000)
2024-04-01T09:34:16.228Z - Error subscribing to topic 0.0.3378616 during attempt 162. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.228Z - Error subscribing to topic 0.0.3378616 during attempt 163. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.228Z - Fire timeout for attempt 82 (delay 20000)
2024-04-01T09:34:16.229Z - Error subscribing to topic 0.0.3378616 during attempt 164. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.229Z - Error subscribing to topic 0.0.3378616 during attempt 165. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.229Z - Fire timeout for attempt 83 (delay 20000)
2024-04-01T09:34:16.229Z - Error subscribing to topic 0.0.3378616 during attempt 166. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.229Z - Error subscribing to topic 0.0.3378616 during attempt 167. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.229Z - Fire timeout for attempt 84 (delay 20000)
2024-04-01T09:34:16.229Z - Error subscribing to topic 0.0.3378616 during attempt 168. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.229Z - Error subscribing to topic 0.0.3378616 during attempt 169. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.229Z - Fire timeout for attempt 85 (delay 20000)
2024-04-01T09:34:16.230Z - Error subscribing to topic 0.0.3378616 during attempt 170. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.230Z - Error subscribing to topic 0.0.3378616 during attempt 171. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.230Z - Fire timeout for attempt 86 (delay 20000)
2024-04-01T09:34:16.230Z - Error subscribing to topic 0.0.3378616 during attempt 172. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.230Z - Error subscribing to topic 0.0.3378616 during attempt 173. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.231Z - Fire timeout for attempt 87 (delay 20000)
2024-04-01T09:34:16.232Z - Error subscribing to topic 0.0.3378616 during attempt 174. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.232Z - Error subscribing to topic 0.0.3378616 during attempt 175. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.232Z - Fire timeout for attempt 88 (delay 20000)
2024-04-01T09:34:16.233Z - Error subscribing to topic 0.0.3378616 during attempt 176. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.233Z - Error subscribing to topic 0.0.3378616 during attempt 177. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.233Z - Fire timeout for attempt 89 (delay 20000)
2024-04-01T09:34:16.233Z - Error subscribing to topic 0.0.3378616 during attempt 178. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.233Z - Error subscribing to topic 0.0.3378616 during attempt 179. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.234Z - Fire timeout for attempt 90 (delay 20000)
2024-04-01T09:34:16.236Z - Error subscribing to topic 0.0.3378616 during attempt 180. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.236Z - Error subscribing to topic 0.0.3378616 during attempt 181. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.236Z - Fire timeout for attempt 91 (delay 20000)
2024-04-01T09:34:16.237Z - Error subscribing to topic 0.0.3378616 during attempt 182. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.237Z - Error subscribing to topic 0.0.3378616 during attempt 183. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.238Z - Fire timeout for attempt 92 (delay 20000)
2024-04-01T09:34:16.239Z - Error subscribing to topic 0.0.3378616 during attempt 184. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.239Z - Error subscribing to topic 0.0.3378616 during attempt 185. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.239Z - Fire timeout for attempt 93 (delay 20000)
2024-04-01T09:34:16.240Z - Error subscribing to topic 0.0.3378616 during attempt 186. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.240Z - Error subscribing to topic 0.0.3378616 during attempt 187. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:16.240Z - Fire timeout for attempt 94 (delay 20000)
2024-04-01T09:34:16.240Z - Error subscribing to topic 0.0.3378616 during attempt 188. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:16.240Z - Error subscribing to topic 0.0.3378616 during attempt 189. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.478Z - Fire timeout for attempt 95 (delay 20000)
2024-04-01T09:34:18.478Z - Error subscribing to topic 0.0.3378616 during attempt 190. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.478Z - Error subscribing to topic 0.0.3378616 during attempt 191. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.478Z - Fire timeout for attempt 96 (delay 20000)
2024-04-01T09:34:18.479Z - Error subscribing to topic 0.0.3378616 during attempt 192. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.479Z - Error subscribing to topic 0.0.3378616 during attempt 193. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.479Z - Fire timeout for attempt 97 (delay 20000)
2024-04-01T09:34:18.479Z - Error subscribing to topic 0.0.3378616 during attempt 194. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.479Z - Error subscribing to topic 0.0.3378616 during attempt 195. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.479Z - Fire timeout for attempt 98 (delay 20000)
2024-04-01T09:34:18.480Z - Error subscribing to topic 0.0.3378616 during attempt 196. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.480Z - Error subscribing to topic 0.0.3378616 during attempt 197. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.480Z - Fire timeout for attempt 99 (delay 20000)
2024-04-01T09:34:18.481Z - Error subscribing to topic 0.0.3378616 during attempt 198. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.482Z - Error subscribing to topic 0.0.3378616 during attempt 199. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.482Z - Fire timeout for attempt 100 (delay 20000)
2024-04-01T09:34:18.482Z - Error subscribing to topic 0.0.3378616 during attempt 200. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.482Z - Error subscribing to topic 0.0.3378616 during attempt 201. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.482Z - Fire timeout for attempt 101 (delay 20000)
2024-04-01T09:34:18.483Z - Error subscribing to topic 0.0.3378616 during attempt 202. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.483Z - Error subscribing to topic 0.0.3378616 during attempt 203. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.483Z - Fire timeout for attempt 102 (delay 20000)
2024-04-01T09:34:18.484Z - Error subscribing to topic 0.0.3378616 during attempt 204. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.484Z - Error subscribing to topic 0.0.3378616 during attempt 205. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.484Z - Fire timeout for attempt 103 (delay 20000)
2024-04-01T09:34:18.484Z - Error subscribing to topic 0.0.3378616 during attempt 206. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.484Z - Error subscribing to topic 0.0.3378616 during attempt 207. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.485Z - Fire timeout for attempt 104 (delay 20000)
2024-04-01T09:34:18.485Z - Error subscribing to topic 0.0.3378616 during attempt 208. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.485Z - Error subscribing to topic 0.0.3378616 during attempt 209. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.486Z - Fire timeout for attempt 105 (delay 20000)
2024-04-01T09:34:18.487Z - Error subscribing to topic 0.0.3378616 during attempt 210. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.487Z - Error subscribing to topic 0.0.3378616 during attempt 211. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.487Z - Fire timeout for attempt 106 (delay 20000)
2024-04-01T09:34:18.488Z - Error subscribing to topic 0.0.3378616 during attempt 212. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.488Z - Error subscribing to topic 0.0.3378616 during attempt 213. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.488Z - Fire timeout for attempt 107 (delay 20000)
2024-04-01T09:34:18.488Z - Error subscribing to topic 0.0.3378616 during attempt 214. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.488Z - Error subscribing to topic 0.0.3378616 during attempt 215. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.488Z - Fire timeout for attempt 108 (delay 20000)
2024-04-01T09:34:18.489Z - Error subscribing to topic 0.0.3378616 during attempt 216. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.489Z - Error subscribing to topic 0.0.3378616 during attempt 217. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.489Z - Fire timeout for attempt 109 (delay 20000)
2024-04-01T09:34:18.490Z - Error subscribing to topic 0.0.3378616 during attempt 218. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.490Z - Error subscribing to topic 0.0.3378616 during attempt 219. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:18.490Z - Fire timeout for attempt 110 (delay 20000)
2024-04-01T09:34:18.490Z - Error subscribing to topic 0.0.3378616 during attempt 220. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:18.490Z - Error subscribing to topic 0.0.3378616 during attempt 221. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.473Z - Fire timeout for attempt 111 (delay 20000)
2024-04-01T09:34:22.474Z - Error subscribing to topic 0.0.3378616 during attempt 222. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.474Z - Error subscribing to topic 0.0.3378616 during attempt 223. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.474Z - Fire timeout for attempt 112 (delay 20000)
2024-04-01T09:34:22.474Z - Error subscribing to topic 0.0.3378616 during attempt 224. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.474Z - Error subscribing to topic 0.0.3378616 during attempt 225. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.475Z - Fire timeout for attempt 113 (delay 20000)
2024-04-01T09:34:22.475Z - Error subscribing to topic 0.0.3378616 during attempt 226. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.475Z - Error subscribing to topic 0.0.3378616 during attempt 227. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.475Z - Fire timeout for attempt 114 (delay 20000)
2024-04-01T09:34:22.475Z - Error subscribing to topic 0.0.3378616 during attempt 228. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.475Z - Error subscribing to topic 0.0.3378616 during attempt 229. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.475Z - Fire timeout for attempt 115 (delay 20000)
2024-04-01T09:34:22.476Z - Error subscribing to topic 0.0.3378616 during attempt 230. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.476Z - Error subscribing to topic 0.0.3378616 during attempt 231. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.476Z - Fire timeout for attempt 116 (delay 20000)
2024-04-01T09:34:22.476Z - Error subscribing to topic 0.0.3378616 during attempt 232. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.476Z - Error subscribing to topic 0.0.3378616 during attempt 233. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.476Z - Fire timeout for attempt 117 (delay 20000)
2024-04-01T09:34:22.477Z - Error subscribing to topic 0.0.3378616 during attempt 234. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.477Z - Error subscribing to topic 0.0.3378616 during attempt 235. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.477Z - Fire timeout for attempt 118 (delay 20000)
2024-04-01T09:34:22.477Z - Error subscribing to topic 0.0.3378616 during attempt 236. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.477Z - Error subscribing to topic 0.0.3378616 during attempt 237. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.477Z - Fire timeout for attempt 119 (delay 20000)
2024-04-01T09:34:22.479Z - Error subscribing to topic 0.0.3378616 during attempt 238. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.479Z - Error subscribing to topic 0.0.3378616 during attempt 239. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.479Z - Fire timeout for attempt 120 (delay 20000)
2024-04-01T09:34:22.479Z - Error subscribing to topic 0.0.3378616 during attempt 240. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.479Z - Error subscribing to topic 0.0.3378616 during attempt 241. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.479Z - Fire timeout for attempt 121 (delay 20000)
2024-04-01T09:34:22.479Z - Error subscribing to topic 0.0.3378616 during attempt 242. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.479Z - Error subscribing to topic 0.0.3378616 during attempt 243. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.479Z - Fire timeout for attempt 122 (delay 20000)
2024-04-01T09:34:22.480Z - Error subscribing to topic 0.0.3378616 during attempt 244. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.480Z - Error subscribing to topic 0.0.3378616 during attempt 245. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.481Z - Fire timeout for attempt 123 (delay 20000)
2024-04-01T09:34:22.481Z - Error subscribing to topic 0.0.3378616 during attempt 246. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.481Z - Error subscribing to topic 0.0.3378616 during attempt 247. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.481Z - Fire timeout for attempt 124 (delay 20000)
2024-04-01T09:34:22.482Z - Error subscribing to topic 0.0.3378616 during attempt 248. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.482Z - Error subscribing to topic 0.0.3378616 during attempt 249. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.482Z - Fire timeout for attempt 125 (delay 20000)
2024-04-01T09:34:22.482Z - Error subscribing to topic 0.0.3378616 during attempt 250. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.482Z - Error subscribing to topic 0.0.3378616 during attempt 251. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:22.482Z - Fire timeout for attempt 126 (delay 20000)
2024-04-01T09:34:22.482Z - Error subscribing to topic 0.0.3378616 during attempt 252. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:22.483Z - Error subscribing to topic 0.0.3378616 during attempt 253. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.554Z - Fire timeout for attempt 127 (delay 20000)
2024-04-01T09:34:34.555Z - Error subscribing to topic 0.0.3378616 during attempt 254. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.555Z - Error subscribing to topic 0.0.3378616 during attempt 255. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.555Z - Fire timeout for attempt 128 (delay 20000)
2024-04-01T09:34:34.555Z - Error subscribing to topic 0.0.3378616 during attempt 256. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.556Z - Error subscribing to topic 0.0.3378616 during attempt 257. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.556Z - Fire timeout for attempt 129 (delay 20000)
2024-04-01T09:34:34.556Z - Error subscribing to topic 0.0.3378616 during attempt 258. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.556Z - Error subscribing to topic 0.0.3378616 during attempt 259. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.556Z - Fire timeout for attempt 130 (delay 20000)
2024-04-01T09:34:34.557Z - Error subscribing to topic 0.0.3378616 during attempt 260. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.557Z - Error subscribing to topic 0.0.3378616 during attempt 261. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.557Z - Fire timeout for attempt 131 (delay 20000)
2024-04-01T09:34:34.558Z - Error subscribing to topic 0.0.3378616 during attempt 262. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.558Z - Error subscribing to topic 0.0.3378616 during attempt 263. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.558Z - Fire timeout for attempt 132 (delay 20000)
2024-04-01T09:34:34.558Z - Error subscribing to topic 0.0.3378616 during attempt 264. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.558Z - Error subscribing to topic 0.0.3378616 during attempt 265. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.558Z - Fire timeout for attempt 133 (delay 20000)
2024-04-01T09:34:34.558Z - Error subscribing to topic 0.0.3378616 during attempt 266. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.558Z - Error subscribing to topic 0.0.3378616 during attempt 267. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.559Z - Fire timeout for attempt 134 (delay 20000)
2024-04-01T09:34:34.559Z - Error subscribing to topic 0.0.3378616 during attempt 268. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.559Z - Error subscribing to topic 0.0.3378616 during attempt 269. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.559Z - Fire timeout for attempt 135 (delay 20000)
2024-04-01T09:34:34.559Z - Error subscribing to topic 0.0.3378616 during attempt 270. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.559Z - Error subscribing to topic 0.0.3378616 during attempt 271. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.559Z - Fire timeout for attempt 136 (delay 20000)
2024-04-01T09:34:34.560Z - Error subscribing to topic 0.0.3378616 during attempt 272. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.560Z - Error subscribing to topic 0.0.3378616 during attempt 273. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.560Z - Fire timeout for attempt 137 (delay 20000)
2024-04-01T09:34:34.560Z - Error subscribing to topic 0.0.3378616 during attempt 274. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.560Z - Error subscribing to topic 0.0.3378616 during attempt 275. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.562Z - Fire timeout for attempt 138 (delay 20000)
2024-04-01T09:34:34.562Z - Error subscribing to topic 0.0.3378616 during attempt 276. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.562Z - Error subscribing to topic 0.0.3378616 during attempt 277. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.562Z - Fire timeout for attempt 139 (delay 20000)
2024-04-01T09:34:34.564Z - Error subscribing to topic 0.0.3378616 during attempt 278. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.564Z - Error subscribing to topic 0.0.3378616 during attempt 279. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.564Z - Fire timeout for attempt 140 (delay 20000)
2024-04-01T09:34:34.564Z - Error subscribing to topic 0.0.3378616 during attempt 280. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.564Z - Error subscribing to topic 0.0.3378616 during attempt 281. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.564Z - Fire timeout for attempt 141 (delay 20000)
2024-04-01T09:34:34.565Z - Error subscribing to topic 0.0.3378616 during attempt 282. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.565Z - Error subscribing to topic 0.0.3378616 during attempt 283. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:34.565Z - Fire timeout for attempt 142 (delay 20000)
2024-04-01T09:34:34.565Z - Error subscribing to topic 0.0.3378616 during attempt 284. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:34.565Z - Error subscribing to topic 0.0.3378616 during attempt 285. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.228Z - Fire timeout for attempt 143 (delay 20000)
2024-04-01T09:34:35.229Z - Error subscribing to topic 0.0.3378616 during attempt 286. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.229Z - Error subscribing to topic 0.0.3378616 during attempt 287. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.229Z - Fire timeout for attempt 144 (delay 20000)
2024-04-01T09:34:35.230Z - Error subscribing to topic 0.0.3378616 during attempt 288. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.230Z - Error subscribing to topic 0.0.3378616 during attempt 289. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.230Z - Fire timeout for attempt 145 (delay 20000)
2024-04-01T09:34:35.230Z - Error subscribing to topic 0.0.3378616 during attempt 290. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.230Z - Error subscribing to topic 0.0.3378616 during attempt 291. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.230Z - Fire timeout for attempt 146 (delay 20000)
2024-04-01T09:34:35.230Z - Error subscribing to topic 0.0.3378616 during attempt 292. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.230Z - Error subscribing to topic 0.0.3378616 during attempt 293. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.232Z - Fire timeout for attempt 147 (delay 20000)
2024-04-01T09:34:35.232Z - Error subscribing to topic 0.0.3378616 during attempt 294. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.233Z - Error subscribing to topic 0.0.3378616 during attempt 295. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.233Z - Fire timeout for attempt 148 (delay 20000)
2024-04-01T09:34:35.233Z - Error subscribing to topic 0.0.3378616 during attempt 296. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.233Z - Error subscribing to topic 0.0.3378616 during attempt 297. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.233Z - Fire timeout for attempt 149 (delay 20000)
2024-04-01T09:34:35.233Z - Error subscribing to topic 0.0.3378616 during attempt 298. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.233Z - Error subscribing to topic 0.0.3378616 during attempt 299. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.234Z - Fire timeout for attempt 150 (delay 20000)
2024-04-01T09:34:35.234Z - Error subscribing to topic 0.0.3378616 during attempt 300. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.234Z - Error subscribing to topic 0.0.3378616 during attempt 301. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.234Z - Fire timeout for attempt 151 (delay 20000)
2024-04-01T09:34:35.234Z - Error subscribing to topic 0.0.3378616 during attempt 302. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.234Z - Error subscribing to topic 0.0.3378616 during attempt 303. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.234Z - Fire timeout for attempt 152 (delay 20000)
2024-04-01T09:34:35.235Z - Error subscribing to topic 0.0.3378616 during attempt 304. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.235Z - Error subscribing to topic 0.0.3378616 during attempt 305. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.235Z - Fire timeout for attempt 153 (delay 20000)
2024-04-01T09:34:35.235Z - Error subscribing to topic 0.0.3378616 during attempt 306. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.235Z - Error subscribing to topic 0.0.3378616 during attempt 307. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.235Z - Fire timeout for attempt 154 (delay 20000)
2024-04-01T09:34:35.236Z - Error subscribing to topic 0.0.3378616 during attempt 308. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.236Z - Error subscribing to topic 0.0.3378616 during attempt 309. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.236Z - Fire timeout for attempt 155 (delay 20000)
2024-04-01T09:34:35.236Z - Error subscribing to topic 0.0.3378616 during attempt 310. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.236Z - Error subscribing to topic 0.0.3378616 during attempt 311. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.236Z - Fire timeout for attempt 156 (delay 20000)
2024-04-01T09:34:35.236Z - Error subscribing to topic 0.0.3378616 during attempt 312. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.236Z - Error subscribing to topic 0.0.3378616 during attempt 313. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.238Z - Fire timeout for attempt 157 (delay 20000)
2024-04-01T09:34:35.238Z - Error subscribing to topic 0.0.3378616 during attempt 314. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established
2024-04-01T09:34:35.238Z - Error subscribing to topic 0.0.3378616 during attempt 315. Waiting 20000 ms before next attempt: No connection established
2024-04-01T09:34:35.238Z - Fire timeout for attempt 158 (delay 20000)
2024-04-01T09:34:35.238Z - Error subscribing to topic 0.0.3378616 during attempt 316. Waiting 20000 ms before next attempt: 14 UNAVAILABLE: No connection established

Hedera network
other
Version
v2.40.0
Operating system
Linux

We've managed to reproduce the problem and we want to double check on the use case and on the impact of the issue

Is this a blocking problem? If yes how exactly?
Why you are testing against a stopped local-node? May be in case of network disconnection?
For example you are trying to subscribe to a Topic, your internet connection goes down (or was down at the first place) and then we would witness the unexpected exponential rise in the number of retries?
Is there any other use cases a stopped local-node is required?

@bpatrzyk

Thank you for addressing the issue.
I see that using a stopped (or non-existent) local node for testing caused some confusion, sorry.
Let me explain our usecase. We have a backend deployed to an on-prem server that subscribes to a topic. We noticed that from time to time (say, every 2-3 days) the backend disconnects from the topic and it does not reconnect automatically (it tries 10 times and fails) - so our backend requires a manual restart to re-subscribe to a topic. We suspect that the initial disconnect is caused by temporary problem with the Internet connection.
What I tried to do is increasing the max number of reconnect attempts but I experienced the aforementioned problems with exponential rise of retries.

Is this a blocking problem? If yes how exactly?
It is a blocking problem. We built a workaround to monitor the topic subscription and re-create it if necessary but it is not a good solution and we would prefer it if the reconnect could be handled by the library automatically.
Why you are testing against a stopped local-node? May be in case of network disconnection?
It was easy to test the reconnects in a repetitive and isolated environment (without dropping my network access) that way. It does not have anything to do with our production setup. In staging and prod environments we use testnet and mainnet.
For example you are trying to subscribe to a Topic, your internet connection goes down (or was down at the first place) and then we would witness the unexpected exponential rise in the number of retries?
When the max attempts is set to a large number and:

there is no Internet connection when we first subscribe to a topic or
the internet connection goes down after we successfully subscribe to a topic
then we experience the unexpected exponential rise in the number of retires

Is there any other use cases a stopped local-node is required?
No, not at all. We only used it for reproducing this issue. We are typically using testnet and mainnet for development and production respectively.

Thank you for the detailed explanation, understanding the use case is a key part from understanding the issue in deep details. At this point we've only managed to reproduce it, but we will need additional time for debugging and fixing it.

Hey @agadzhalov @hendrikebbers, I would like to take this issue forward

After investigating the cause of this issue, I found that the NodeMirrorChannel class handles both the status and error events in a way that can trigger the error handler multiple times, leading to duplicate logging.
.on("status", (status) => {
    if (status.code == 0) {
        end();
    } else {
        error(status);  // Triggers error handler when status code is non-zero
    }
})

.on("error", (err) => {
    error(err);  // Also triggers error handler on the error event
})

Wouldn't it make sense to rely solely on the status event, as it provides more flexibility with error codes? This way, we could remove the error event listener entirely, preventing potential duplicate calls to the error handler.
Additionally, for clarity, are the infinite retry attempts still necessary? If so, should they be enabled by default, or would it be better to allow users to activate them when needed?
cc @hendrikebbers @agadzhalov


Missing certificate bundle in Docker image

When publishing a notification to my server running the 1.27.2 Docker image, I get an error in the log: Unable to publish poll request: Post "https://ntfy.sh/f9a14d6123f[…]": x509: certificate signed by unknown authority. I think the CA bundle is missing.

My apologies for the delay, but #387 :-D
I tried this and I cannot reproduce it:
ocker run \
  -p 2080:80 \
  -it \
  binwiederhier/ntfy \
    --debug \
    serve \
    --base-url http://<IP_ADDRESS> \
    --upstream-base-url https://ntfy.sh

2022/10/01 20:10:21 INFO Listening on :80[http], ntfy 1.28.0, log level is DEBUG
2022/10/01 20:10:23 DEBUG <IP_ADDRESS> HTTP POST /mytopic Dispatching request
2022/10/01 20:10:23 DEBUG <IP_ADDRESS>/mytopic/GVkLPnJ7eJoj Received message: event=poll_request, body=11 byte(s), delayed=false, firebase=true, cache=false, up=false, email=
2022/10/01 20:10:23 DEBUG <IP_ADDRESS>/mytopic/GVkLPnJ7eJoj Publishing poll request to https://ntfy.sh/2aa077f08d5bb00f192c983fcefeb56ce7feee97059c1b0f2ed26dd916913aa5
2022/10/01 20:11:21 DEBUG Manager: Starting
2022/10/01 20:11:21 DEBUG Manager: Deleted 0 stale visitor(s)
2022/10/01 20:11:21 DEBUG Manager: Pruning messages older than 2022-10-01 08:11:21
2022/10/01 20:11:21 INFO Stats: 1 messages published, 0 in cache, 0 topic(s) active, 0 subscriber(s), 1 visitor(s), 0 mails received (0 successful, 0 failed), 0 mails sent (0 successful, 0 failed)
2022/10/01 20:11:21 DEBUG Manager: Finished

curl -d hi -H "X-Poll-ID: abc" localhost:2080/mytopic
{"id":"GVkLPnJ7eJoj","time":1664655023,"event":"poll_request","topic":"mytopic","message":"New message","poll_id":"abc"}

Maybe the newer Alpine image contains updated certs.

I'm going to close this for now, but I'm happy to re-open at any time.


Handle appname for removing odd characters

https://github.com/microsoft/azure-maven-plugins/issues/779

If there is anything wrong against schema in default value, config can also find this error:
eg:  "cpu": {
"description": "cpu cores",
"type": "integer",
"default": 1000,
"minimum": 1,
"maximum": 4
}
https://github.com/microsoft/azure-maven-plugins/issues/745

Codecov Report

Merging #810 into develop will decrease coverage by 0.13%.
The diff coverage is 26.47%.

@@              Coverage Diff              @@
##             develop     #810      +/-   ##
=============================================
- Coverage      40.17%   40.04%   -0.14%
+ Complexity       681      680       -1
=============================================
  Files            133      133
  Lines           5122     5144      +22
  Branches         727      731       +4
=============================================
+ Hits            2058     2060       +2
- Misses          2904     2922      +18
- Partials         160      162       +2

Impacted Files
Coverage Δ
Complexity Δ

...crosoft/azure/maven/spring/AbstractSpringMojo.java
1.09% <ø> (ø)
1 <0> (ø)
:arrow_down:

...a/com/microsoft/azure/maven/spring/ConfigMojo.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...osoft/azure/maven/spring/prompt/PromptWrapper.java
60.12% <56.25%> (-1.42%)
30 <0> (-1)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80534ec...65d6feb. Read the comment docs.


Move abbreviations to a different file

I think now the index file, which is the main one will lock more clear

@sheerun what do you think now? ^^

It looks really good :) Could you squash the commits and force push as the last step?

@sheerun done :dancer:

Great, thank you!

Getting a lot of activity recently, awsome!

@faceleg yeah!


Maintainer for AKS Sample

Deprecate the AKSSample as no active maintainer for this sample.

Originally posted by @samarthasthana in https://github.com/microsoftgraph/microsoft-graph-comms-samples/issues/637#issuecomment-1489210049
@zihzhan-msft
@ssulzer
What exactly does having a maintainer entail? It's not like the other samples are receiving great maintenance either.
There are numerous PRs open for the repo, which haven't been reviewed in 3 years. I think this repo in general could use a maintainer who takes this serious. Once contributions are welcomed and reviewed, the community would do most of the work I believe.
Is it possible to promote external community members to contributors with write-access, if they've shown good intent in the past?

To be clear. This is me applying for that position 😅


adds setupDone, unlisten(), camelCased feature flags

@imlucas can you please review?
The change includes an unlisten() function for each of the metrics, and a setupDone boolean. I'm not sure I "unlistened" everything correctly that is set up in listen().
The reason why we want this now is because we can install a listener to sync events on app.preferences that calls metrics.listen(app). This way, we can toggle any of the tracking on the fly with e.g.
app.preferences.save('bugsnag', false)

In the end, we can just attach UI toggles to these properties in a preferences pane.
I also camelCased the feature google-analytics to googleAnalytics for consistency (see ./src/models/preferences.js). Nicer to work with as these correspond to properties.

@rueckstiess, there is an exports.listen(app) in the top-level index.js. Should we add a corresponding unlisten()?

Minor nits found, otherwise LGTM.

published in v0.2.3


New version: foxglove.studio version 1.39.1

Result: Installation Successful

Manifest
Add/Remove Programs

Name
Foxglove Studio
Foxglove Studio 1.39.1

Version
1.39.1
1.39.1

Publisher
Foxglove Technologies
Foxglove Technologies

ProductCode

b1a22fb8-f6f3-5e1f-b388-958085c08782

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 5707
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

/azp run

[Policy] Reset Feedback


When I run the "video_demo.py" file, an error message appears

When I run the "video_demo.py" file, an error message appears: KeyError: 'target_response,  can you help me check it?

Hi, I have commented the parts in the script that were causing the error.  Can you re-try running the demo script with these changes?

Hi, I have commented the parts in the script that were causing the error. Can you re-try running the demo script with these changes?

Thank you very much. The issue has been resolved.


Plan to release training code and pre-trained model for direction prediction?

Hi!
I'm wondering if you have any plans in the future to release (i) the training code and (ii) the pre-trained model and inference code for walking direction prediction. I only see inference code for walkability, but I'm quite interested in the direction prediction results shown in your paper (Fig. 7).
Thanks for the great work and the released code again. :)

Hi Shanmy,
Thanks for your interest. Unfortunately, there is currently no plan to further release these parts as the project is no longer active.


Colorado Coin

Colorado Coin (COLO)  to be used in Boulder Startup week (http://boulderstartupweek.com/) as an interactive educational bounties game:

https://medium.com/@jon_59581/colorado-bounty-network-boulder-startup-week-blockchain-engagement-bd794fcb8dd9
https://colorado.bounties.network/

And further used to foster innovation in the Colorado blockchain community afterwards:

https://coloradocoin.us/

Actually - we have moved the event to Rinkeby at new address : 0xc069bfe8dc38940a15264564c51e362b2b849a29
Do you support testnet tokens?

Hi @NukeManDan, we do not suport testnet tokens. Let us know when you have it on mainnet!


Add system property to revert to old polling fs watcher

This adds a sbt.watch.polling system property that if set to true will use PollingWatchService instead of WatchServiceAdapter (nio).
This is a temporary workaround for users affected by #3527

To validate this pull request against other sbt modules, please visit this link.

To validate this pull request against other sbt modules, please visit this link.

A validation involving this pull request is in progress...

The validator has checked the following projects against Scala 2.12,
tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/3597/head
sbt/sbt@14cdd489597a41fcfb568a00db853b7dbc273638

zinc
1.x
sbt/zinc@8c4b9969d5d003f82c256106df850e7d450c41c6

io
1.x
sbt/io@62004b28dfcdc33273ebb07a563e78178f6eb21d

librarymanagement
1.x
sbt/librarymanagement@293666f653d2686e3049dce37fb80ccb58845b99

util
1.x
sbt/util@f4eadfc259f6f25b61eeb519fe29fb44220bec4a

website
1.x

:white_check_mark: The result is: SUCCESS
(restart)

@eed3si9n I've tweaked it so that the flag is now a mode option (nio or polling) and have expanded the notes. I'm not sure whether it's more of a 'bug fix' or an 'improvement' 🤔 .

OK, attempt 3. It will now default to polling on macOS and nio on all other platforms.

A validation involving this pull request is in progress...

The validator has checked the following projects, tested using dbuild, projects built on top of each other.

Project
Reference
Commit

sbt
pull/3597/head
sbt/sbt@a3c34c6c0a76948fe56ecf990e9defb18dfbf6d6

zinc
develop
sbt/zinc@6c0e9cbc84ecc08dede9fbe3c2df4ca34761de19

io
develop
sbt/io@c2668e77443e2a6fd7c33da706c299bf5a795e69

librarymanagement
develop
sbt/librarymanagement@f073dde812848ef443619578f55e290f3863bcaa

util
develop
sbt/util@473d42ac782f9449dbd7c7940a67208abbff1861

:x: The result is: FAILED
(restart)


fatal: could not read Username for 'https://github.com' error for PluginInstall of two plugins by scrooloose

I get the following error while updating or trying to install plugins nerdtree and syntastic. The rest of the plugins seem to install just fine.
 x syntastic:
 Cloning into '/home/jim/.vim/plugged/syntastic'...
 fatal: could not read Username for 'https://github.com': terminal prompts disabled
 x nerdtree:
 Cloning into '/home/jim/.vim/plugged/nerdtree'...                                                              |
 fatal: could not read Username for 'https://github.com': terminal prompts disabled

Type:

[ ] Bug
[ ] Enhancement
[ ] Feature Request
[x] Question

OS:

[ ] All/Other
[x] Linux
[ ] OS X
[ ] Windows

Vim:

[ ] Terminal Vim
[ ] GVim
[x] Neovim

What do your Plug commands look like for those plugins? This error usually indicates a typo, so double check the spelling for <username>/<pluginname>


RedisJSONSerializer - cast error

I'm applying your RedisSessionProvider to our project to improve it.
All was working fine until I realized that RedisJSONSerializer give us some problems.
The issue is when RedisJSONSerializer serialized a ComplexType (SerializeOne function).
It's storing fine, but when it's come time to deserialize is converting int type to long.

Joe,
I'm pretty sure, that this problem is not a problem of RedisJSONSerializer, but json.NET itself.
Here is a link to stackoverflow: http://stackoverflow.com/questions/8297541/how-do-i-change-the-default-type-for-numeric-deserialization
There is a description for this behavior...


Added blacklist logic and refactored some code

added back CORS
added blacklist for checking for website requests
added unit tests

Current coverage is 82.60%

Merging #147 into master will decrease coverage by -1.41% as of c965ef7

@@            master   #147   diff @@
=====================================
  Files           27     27
  Stmts          876    943    +67
  Branches         0      0
  Methods          0      0
=====================================
+ Hit            736    779    +43
  Partial          0      0
- Missed         140    164    +24

Review entire Coverage Diff as of c965ef7

Powered by Codecov. Updated on successful CI builds.

+1

r+


add services query permission

这个 PR 实现什么功能/修复什么问题:

新增域下services默认查询条件

是否需要 backport 到之前的 release 分支:

release/2.13
release/2.12

/area region
/cc @swordqiu

Codecov Report

Merging #4277 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #4277   +/-   ##
======================================
  Coverage    6.85%   6.85%
======================================
  Files         519     519
  Lines       87952   87952
======================================
  Hits         6026    6026
  Misses      81428   81428
  Partials      498     498

Flag
Coverage Δ

#aFlag
6.85% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/cloudcommon/db/lockman/fifo.go
80% <0%> (-10%)
:arrow_down:

pkg/appsrv/response.go
69.23% <0%> (+3.07%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 397fbd4...1c20200. Read the comment docs.

/lgtm

/approve

/approve


Custom Bean creation

I have a custom bean. I have a jar created out of custom bean. Whether we have options to load a custom bean to apache karavan?

you bean should be in mvn repository and then add it to your integration

I have added the custom code into the project and annotated it, but its saying "The bean name must be set must be specified". So after adding the code should I need to compile or run the code?
--> Other than the java file in karavan-demo where else should I need to add the bean?
--> How to use the bean in components and in which components we can use this custom bean?

...
            - to:
                uri: salesforce:updateSObject
                parameters:
                  sObjectName: Opportunity
                description: Update Opportunity Object
....
    - beans:
        - name: salesforce
          type: '#class:org.apache.camel.component.salesforce.SalesforceComponent'
          properties:
            loginUrl: https://login.salesforce.com
            clientSecret: SECRET
            userName: USERNAME
            clientId: CLIENT_ID
            password: PASSWORD


Fix: Removed repetition in content/tooling.mdf

Btw, I just want you to know that your portfolio / personal website is absolutely wonderful, i really like it 👍

@MrAnyx thanks so much for the fix! Can't believe I never noticed this aahahahhaha
And I'm so glad you liked it! 😄 If you haven't already, I recommend opening up the console for a lil' game 😉


Markdown table conflicts with some URLs

Links like this:

https://www.willhaben.at/iad/immobilien/d/mietwohnungen/wien/wien-1230-liesing/erstklassige-2-zimmerwohnung-in-der-khekgasse-|-ruhige-lage-|-erstbezug-998568375/

Are problematic as they mess with the markdown table format.
Task:

[x] Find valid solution to accommodate such URLs.

To fix this, I imported quote from urllib.parse and applied URL encoding to the Link column to safely encode special characters like |. This is done with the line:
recent_listings['Link'] = recent_listings['Link'].apply(lambda x: quote(x, safe='/:?=&%'))


Single app "Application Administrator"  Role not able to access Provisioning logs

Can you please calrify if the role "Application Administrator" need to be assigned on tenant level or enterprise level? Because if I assign an application administrator on one app, I cannot access Provisioing Logs (preview) with access denied error, but If I assign a user Application Administrator from All Roles under AAD then I can access the preview logs.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 684c1153-f8bc-0c5c-9004-4ae150c4dc37
Version Independent ID: 33863c64-ad39-dd57-06e5-a0fc7ac4993c
Content: Provisioning logs in the Azure Active Directory portal (preview)
Content Source: articles/active-directory/reports-monitoring/concept-provisioning-logs.md
Service: active-directory
Sub-service: report-monitor
GitHub Login: @MarkusVi
Microsoft Alias: markvi

@tajaber Thank You for your feedback . We will investigate and update the thread.

@tajaber If you have added a user to Application Administrator role of a specific application under App Registration, you cannot modify that application under Enterprise application as it provides  Application Administrator privileges to manage App Registration only and not the corresponding service principal under enterprise applications.

This feature will be available in new future. As of now to view provisioning logs, the required roles has to be assigned directory wide. The owner of the enterprise application can't access the provisioning logs.. They can only make configuration changes.
Who can access the data?

Users in the Security Administrator, Security Reader, Report Reader, Application Administrator, and Cloud Application Administrator roles
Global Administrators
Read More: https://docs.microsoft.com/en-us/azure/active-directory/reports-monitoring/concept-provisioning-logs


Vanha warps broken

In the blip that happened yesterday, I lost permission to all vanha town warps (except Agni), and even when I go back to them and run around it doesn't unlock them for me again. I'd really appreciate the help because this is making quests infinitely more inconvenient for me. Thanks!

Closing this since PrimalCyndaquil fixed it for you.


Neo cli to restart on static file changes

Is there anyway to just use neo cli to detect changes in all the files in the project? I love Neo and it's Express like architecture!

you can provide configuration file. Example here http://ivpusic.github.io/neo/tutorials/2015/01/22/configuration.html ("suffixes" is option you need). Under the hood neo is using https://github.com/ivpusic/rerun, so you can get more info about suffixes here


Billboard/label on terrain flickering

As described here and here.  @bagnell is right about the root cause.

@hpinkos is this OBE with #6621?

Should be


Added initial Bootstrap design

This includes starting designs for the overall grid, navbar, forms, and buttons.
Make sure you run bower install before testing.

:+1:

:100:

like the design :100:


SCD30 CO2 Sensor High Humidity Bug

Something odd is going on with one of my test CO2 sensors. About 2 days ago, it started reporting a relative humidity that was radically high and hasn't yet returned to normal. The blue line below is higher than real humidity:

I pulled the sensor out and let it dry out inside for a few hours, but that didn't change anything.
Then I tried to bake it at around 80 C for a few hours in the oven. That did seem to have improved the humidity sensing, but it seems like I fried something in the CO2 LaserElectric torchFireRightwards arrowFrowning face. 1.2K PPM is NOT correct.

SCD30 Serial Number: 2862279

I'm not too concerned about the sensor failing after the oven testing, I must have just exceeded some thermal limit, but the humidity sensor reading incorrectly seemingly randomly seems concerning.
I'm going to reach out to Sensirion to see if they have any insight on why that would happen.

@dahlwinters have you ever seen anything like this?

Email out to the Sensirion:

Haven't seen anything like this with the relative humidity. If it was with the CO2 readings only, it might have been an auto-calibration problem. Definitely something is wrong since a value of RH above 100% is not possible.

Thanks! I'll update this issue as I learn more!

More info from Sensirion, but no root cause.
"Thank you for the addition temperature plot. The graph shows a steady temperature drop of around 10°C and at the same time an unreal humidity increase over 100% RH. The temperature decrease is nearly linear and looks basically the same as if someone entered a temperature offset. The SHT31 on the SCD30 PCB is limited to an output of 100% RH. The only way to get values over 100% RH is setting a temperature offset as the compensation engine output is not limited to 100% RH. The average temperature offset due to self heating of the SCD30 PCB is 3°C. I’d suggest to set the offset to 3°C and see what happens.
There are a few other points to consider.

Power supply needs to be able to provide 75mA
There should be no pull up resister on the SDA and SCL
Bus voltage is 3V, maximum 3.3V
Supply voltage must be between 3.3V and 5.5V
For code verification please check our GitHub repository @ GitHub - Sensirion/info: Overview over the Sensirion Github repositories & available sensor drivers

Closing this issue out for now. I doubt I'll root cause the sensor issue without more help from the vendor, but I've documented what I know here for the future in case we see this issue again.


Fix type not set for isTransactionalCheck in TransactionDesugar

Purpose
Fixes #41975
Approach
The fix involves setting the type of BLangTransactionalExpr node, isTransactionalCheck to boolean type in accordance with the spec.
Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@heshanpadmasiri Can you confirm whether this solution fixes the problem you mentioned. If it does, We can merge this PR.

@heshanpadmasiri Can you confirm whether this solution fixes the problem you mentioned. If it does, We can merge this PR.

Yes this has fixed the issue and we can merge


Add function type: cloudevent

https://github.com/GoogleCloudPlatform/functions-framework#cloudevents-functions-signature-type-cloudevent

Parse these HTTP requests:
POST / HTTP/1.1
Content-Type: application/json; charset=utf-8
Content-Length: 33
ce-specversion: 1.0
ce-type: google.cloud.pubsub.topic.publish
ce-time: 2020-09-05T03:56:24Z
ce-id: 1234-1234-1234
{
 "subscription": "projects/my-project/subscriptions/my-subscription",
 "message": {
   "@type": "type.googleapis.com/google.pubsub.v1.PubsubMessage",
   "attributes": {
     "attr1":"attr1-value"
   },
   "data": "dGVzdCBtZXNzYWdlIDM="
 }
}

POST / HTTP/1.1
Content-Type: application/json; charset=utf-8
{
  specversion: 1.0
  type: google.cloud.pubsub.topic.publish
  time: 2020-09-05T03:56:24Z
  id: 1234-1234-1234
  data: {
    "subscription": "projects/my-project/subscriptions/my-subscription",
    "message": {
      "@type": "type.googleapis.com/google.pubsub.v1.PubsubMessage",
      "attributes": {
        "attr1":"attr1-value"
      },
      "data": "dGVzdCBtZXNzYWdlIDM="
    }
  }
}

HTTP return value doesn't matter. See FF GitHub repo readme: https://github.com/GoogleCloudPlatform/functions-framework

Here's example code for how to receive a CloudEvent in the FF:

Check if the HTTP requestisBinary: https://github.com/GoogleCloudPlatform/functions-framework-nodejs/blob/master/src/cloudevents.ts#L28

Get the correct CloudEvent (if binary or structured, see above for difference).

invoke a users function with a CloudEvent: https://github.com/GoogleCloudPlatform/functions-framework-nodejs/blob/master/src/invoker.ts#L145

Do note that the Pub/Sub emulator is not compatible with CloudEvents (and thus the Functions Framework), so don't use it. Use cURL and unit tests to test the functionality.