Upd/neo-go
subscriptions #73
No reviewers
Labels
No labels
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 project
No assignees
4 participants
Notifications
Due date
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#73
Loading…
Reference in a new issue
No description provided.
Delete branch "carpawell/upd/neo-go-subs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. 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.
nns-name
andnns-zone
forcontainer create
88e3868f47strings.Cut
instead ofstrings.Split*
where possible e9f3c24229nnsResolveKey
7486c02bbcgroup.frostfs
key from output of thedump-hashes
9929dcf50bgroup.frostfs
at init step b4582239bfIsLocked
public f006f3b342@fyrchik, fixed
1189ac6874
to7a7573bbe4
7a7573bbe4
to8c092eebba