#19. VATZ biweekly meeting at 2022-10-12 08:00:00 -06:00:00

[xellos00]

Retrospect

1. Overall

2. Statistic Rate

Sprint	Issue fulfillment	progress rate(%)
17	2/19	10
18	1/18	5

---

• Finished

  • Internal API service for VATZ #222

• Move to Sprint 19

  • Enhance Notification : Stop consecutive Notification within Configuration #246
  • Plugin Development : SystemUtil #242
  • Plugin Development : Flow  #238
  • Enhance Notification with Channels.  #226
  • Generate VATZ CLI List in file  #202
  • Check Test & Coverage automatically #197
  • Managements Plans for VATZ #187
  • Documentation to Updated CLI for 1.1 #175
  • Enhance Notification behaviors per status.  #174
  • Research for Prometheus to apply into notification for Protocol #146
  • Plugin Development: Matic #122
  • Plugin Development : Osmosis #121
  • Create How to create a unit test and implements with github action documents #119
  • vatz-proto buffer's Github action enhancement #87
  • Add unit test sample to Vatz #85

---

When you raise PR:

• Make a single test case at least if there's any update
• Go Test SC
• Go lint
• Go Build

---

Discussion

• Github action

  • Go Test
  • Go Lint - ok!!
  • Go Build - ok!!

• Test

  • Unit Test
    • for PR, make a single test case at least if there's any update.
      • attached SC (temporarily til repo to be public)
        • Build & Start
        • coverage
    • Separate milestone:
  • Integration test. (@xellos00 make another issue to discuss)

---

• Node Watcher : Plugin Development: vatz-plugin-node-watcher (temp title) #273

[xellos00]

동요

Developments

• CI/CD Managements in VATZ(VATZ, VATZ-PROTO) #248
  • vatz-proto buffer's Github action enhancement #87
  • Github Action to send a PR notification to discord if there's any update with PRs #228
• Enhancement on Dispatchers(Notifications. Prev) #240
  • Enhance Notification behaviors per status.  #174
  • Enhance Notification : Stop consecutive Notification within Configuration #246
  • Add new dispatcher type : PagerDuty #261

Bug fix

• open default.yaml: no such file or directory #259
• dispatcher CH: Telegram-Invalid telegram token. #262
• Plugin's parameters is not passing to plugins that declared in default.yaml #180

[rootwarp]

준교

• Read configs from the config file to start internal RPC. #256
  • Use config value to start RPC service #260

[xellos00]

@rootwarp
Please, Add md file for CLI and RPC with new issue later.

[kim201212]

형기

• Plugin Development : Cosmos (V1) #236
  • Cosmos - plugin - is_alived #243
  • Cosmos - Plugin - Refactoring is_alived plugin #266
  • Cosmos - Plugin - Test code for is_alived plugin #268
• Node Watcher plugin for Ethereum #271

[skonhwang]

승곤

• Cosmos - Plugin - Refactoring peer_count plugin #267
  • peer_count: refactoring for unified module vatz-plugin-cosmoshub#16

[gnongs]

진홍

Developments

• Plugin Development: Relayer V2 #272
• Plugin Development : Cosmos (V1) #236
  • Cosmos - Plugin - Test code for peer_count plugin #269

Bug fix

• dispatcher CH: Telegram-Invalid telegram token. #262

[meetrick]

황제

Developments

• Plugin Development: Relayer V2 #272
• Plugin Development : Cosmos (V1) #236
• Plugin Development : Aptos #183

[heejin-github]

희진

• Plugin Development : Cosmos (V1) #236
  • Cosmos - Plugin - Refactoring as a unified module #265
  • make a unified module for all plugins vatz-plugin-cosmoshub#13
  • Update Makefile for test vatz-plugin-cosmoshub#14
  • Fix test code for cosmos-sdk-blocksync/status vatz-plugin-cosmoshub#15

[xellos00]

@qkrybin
Create an issue to record items, if there's anything we need on VATZ as first open-source user.