Upd/neo-go
subscriptions #73
No reviewers
Labels
No Label
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No Milestone
No Assignees
4 Participants
Notifications
Due Date
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#73
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "carpawell/upd/neo-go-subs"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Only adopts new API. More adds that removes; could look strange a little. But suggest separating updates and refactors.
Correct me if I am wrong, in this PR our main goal is to remove some of the
deprecated
messages??
??
If it is false, do can we take a mutex too?
It could look more readable without
if
.@fyrchik, yes, all the "deprecated" msgs about the notification processes are fixed (but that is not a refactor and that is not a PR that fixes all the linter messages)
no, we would have a dead-lock then:
background
flag isfalse
only if we have already lost connection and try to establish a new one, soswitchLock
has been already takencould not find unlocking line while was preparing that PR so decide to chose a better (IMO) spacing
a separate commit/keep as it was?
Can we embed
subsInfo
here? It allows us to get rid ofupdateSubs
and possibly prevents us from forgetting something to copy when we add it.I would keep if it then linter doesn't complain.
@fyrchik, fixed
1189ac6874
to7a7573bbe4
7a7573bbe4
to8c092eebba