atomic.StoreInt32(&h.status, statusClosed)
	h.storeCtxCancel()

	// Wait for messages to be sent...
	h.wg.Wait()

	// Set logch to nil and close it.
	// This will block all Send operations,
	// and finish the existing ones.
	// All future ones will be discarded.
	h.logChMu.Lock()
	xioutil.SafeClose(h.logCh)
	h.logCh = nil
	h.logChMu.Unlock()

		g.Go(func() error {
			if formats[index] == nil {
				return errDiskNotFound
			}
			return saveFormatErasure(storageDisks[index], formats[index], "")
		}, index)
	}

	// Wait for the routines to finish.
	return reduceWriteQuorumErrs(ctx, g.Wait(), nil, len(storageDisks))
}

// relinquishes the underlying connection for all storage disks.
func closeStorageDisks(storageDisks ...StorageAPI) {
	var wg sync.WaitGroup

func listPathRaw(ctx context.Context, opts listPathRawOptions) (err error) {
	disks := opts.disks
	if len(disks) == 0 {
		return fmt.Errorf("listPathRaw: 0 drives provided")
	}

	// Cancel upstream if we finish before we expect.
	ctx, cancel := context.WithCancel(ctx)
	defer cancel()

	// Keep track of fallback disks
	var fdMu sync.Mutex
	fds := opts.fallbackDisks
	fallback := func(err error) StorageAPI {

  // until the previously pending operation (a StartExecute without a Join) has
  // finished, if any.
  //
  // `cancellation_manager` must live until after `Join` finishes and pending
  // `is_async` operations finish. In addition to allowing the caller to cancel
  // the operation, its `StartCancel` method will be called if op execution
  // fails on any device in order to cancel the others.

Worse, there is no guarantee that the write to <code>done</code> will ever
be observed by <code>main</code>, since there are no synchronization
events between the two threads.  The loop in <code>main</code> is not
guaranteed to finish.
</p>

<p>
There are subtler variants on this theme, such as this program.
</p>

<pre>
type T struct {
	msg string
}

var g *T

func setup() {
	t := new(T)

   * computes or retrieves it using the supplied {@code CacheLoader}. If another thread is currently
   * loading the value for this key, simply waits for that thread to finish and returns its loaded
   * value. Note that multiple threads can concurrently load values for distinct keys.
   *
   * <p>This method does not alter the state of this {@code CacheBuilder} instance, so it can be

labels.wizard_start_crawler_title=Crawler
labels.wizard_start_crawling_desc=To click "Start Crawling" button, you can start a crawling now.
labels.wizard_button_start_crawling=Start Crawling
labels.wizard_button_finish=Skip
labels.search_list_configuration=Search
labels.search_list_button_delete=Удалить
labels.search_list_delete_confirmation=Do you really want to delete?
labels.search_list_button_delete_all=Delete all with this query

labels.wizard_start_crawler_title=Crawler
labels.wizard_start_crawling_desc=To click "Start Crawling" button, you can start a crawling now.
labels.wizard_button_start_crawling=Start Crawling
labels.wizard_button_finish=Skip
labels.search_list_configuration=Search
labels.search_list_button_delete=Delete
labels.search_list_delete_confirmation=Do you really want to delete?
labels.search_list_button_delete_all=Delete all with this query

labels.wizard_start_crawler_title=Crawler
labels.wizard_start_crawling_desc=To click "Start Crawling" button, you can start a crawling now.
labels.wizard_button_start_crawling=Start Crawling
labels.wizard_button_finish=Skip
labels.search_list_configuration=Search
labels.search_list_button_delete=Delete
labels.search_list_delete_confirmation=Do you really want to delete?
labels.search_list_button_delete_all=Delete all with this query

labels.wizard_start_crawling_title = 크롤링 시작
labels.wizard_start_crawler_title = 크롤러
labels.wizard_start_crawling_desc = "탐색 시작"버튼을 클릭하여 이제 크롤링을 시작할 수 있습니다.
labels.wizard_button_start_crawling = 크롤링 시작
labels.wizard_button_finish = 건너 뛰기
labels.search_list_configuration = 검색
labels.search_list_button_delete = 삭제
labels.search_list_delete_confirmation = 삭제 하시겠습니까?
labels.search_list_button_delete_all =이 쿼리에서 모두 삭제