You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
issue 1: if some err occurs ,we MUST not invoke it (L60). If it noticeTrackerUserLogin just record a audit-log, we can ignore the err and invoke it.
issue 2: obd/service is just a database/data operation module, it MUST not call sendMsgToTracker to send async message; obd/lightclient module is async message center, now 95% async messages are recieved and sent here, all the client-websocket-conn p2p-conn are initialized here; obd/service/htlc_tx_forward.go PayerRequestFindPath invoke "sendMsgToTracker(enum.MsgType_Tracker_GetHtlcPath_351, pathRequest)" have the same probolem.
now i have fixed the two issue, and obd/service.sendMsgToTracker have disbled, and below messages submit by grpc-conn now,no need to sync userInfo/channelInfo/htlcInfo to tracker with complex async message Goroutines. the old msgList:
MsgType_Tracker_UpdateChannelInfo_350
MsgType_Tracker_UserLogin_304
MsgType_Tracker_UserLogout_305
MsgType_Tracker_UpdateHtlcTxState_352
(to to) may be we should design the obd-tracker info sync-mode and security first. Maybe new mechanism won't need the above work.
The text was updated successfully, but these errors were encountered:
This issue is the bug 12 and 13 in issue 53
obd/service/user.go
Lines 20 to 76 in 5829315
The text was updated successfully, but these errors were encountered: