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
{{ message }}
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.
Capturing comment #2328 (comment) about stage1/init/common/kvm_mount.go and generateMounts:
I know it was already like that before, but the mapification of the volume array into a map is done in both calls of generateMounts (both in the kvm stage1 and the non-kvm stage1). For factorisation, should generateMounts accept an array of volumes as parameter instead?
Both calls of generateMounts use the following pattern:
vols := make(map[types.ACName]types.Volume)
for _, v := range p.Manifest.Volumes {
vols[v.Name] = v
}
mounts := generateMounts(ra, vols)
for _, m := range mounts {
vol := vols[m.Volume]
...
}
Instead, it could be
mounts := generateMounts(ra, vols, func(m Mount, v Volume){
...
})
(Not necessarily for this PR though)
The text was updated successfully, but these errors were encountered:
Capturing comment #2328 (comment) about stage1/init/common/kvm_mount.go and generateMounts:
I know it was already like that before, but the mapification of the volume array into a map is done in both calls of
generateMounts
(both in the kvm stage1 and the non-kvm stage1). For factorisation, shouldgenerateMounts
accept an array of volumes as parameter instead?Both calls of
generateMounts
use the following pattern:Instead, it could be
(Not necessarily for this PR though)
The text was updated successfully, but these errors were encountered: