beyondstorage / go-service-cos Goto Github PK

• Rendered GSP
• Tracking Issue

This is the service tracking issue that generated by go-community, please close with comments if not applicable to this project.

Steps

If this service has native support for Link or Symlink:

• Implement CreateLink API
• Add support for List/Stat
• Setup linker tests

If this service doesn't have native support for Link or Symlink, it's optinal to implement the virtual_link features:

• Start a RFC to describe the way to implement the virtual_link feature (take this issue as the tracking issue)
• Implement the RFC
• Setup linker tests

• Rendered GSP
• Tracking Issue

This is the service tracking issue that generated by go-community, please close with comments if not applicable to this project.

Steps

• Update formatError to add new errors check

Migrate to go-storage v3.4.2.

Expected Behavior

According to COS API doc, when GetObject with Range header:

例如 bytes=0-9，表示下载对象的开头10个字节的数据；bytes=5-9，表示下载对象的第6到第10个字节。此时返回 HTTP 状态码206（Partial Content）及 Content-Range 响应头部。

And also, FormatRangeOptions() was provided to format Range value in cos-go-sdk:

func FormatRangeOptions(opt *RangeOptions) string {
	if opt == nil {
		return ""
	}
	if opt.HasStart && opt.HasEnd {
		return fmt.Sprintf("bytes=%v-%v", opt.Start, opt.End)
	}
	if opt.HasStart {
		return fmt.Sprintf("bytes=%v-", opt.Start)
	}
	if opt.HasEnd {
		return fmt.Sprintf("bytes=-%v", opt.End)
	}
	return ""
}

Based on the above, we envision that when Range: bytes=-9 we should be able to download data from 0 to 9([0-9]).

Current Behavior

• When setting RangeOptions.End as follows, we will get the read size check error.

  rangeOptions := &cos.RangeOptions{}
  if opt.HasSize {
    	rangeOptions.HasEnd = true
    	rangeOptions.End = rangeOptions.Start + opt.Size - 1
  }
  

• When setting RangeOptions.End as follows, we will get the read content check error.

  rangeOptions := &cos.RangeOptions{}
  if opt.HasSize {
    	rangeOptions.HasEnd = true
    	rangeOptions.End = opt.Size
  }
  

Steps to Reproduce

Run integration test after modifying the code as above.

Enviroment

github.com/tencentyun/cos-go-sdk-v5 v0.7.31

For CompleteMultipartUpload in cos:

• If the numbers of the uploaded parts are not continuous, 400 InvalidPart will be returned when this API is called.
• If the part information entries in the request body are not sorted by number in ascending order, 400 InvalidPartOrder will be returned when this API is called.

Random part number in CompletePart test case leads to the failure of multiparter integration test.