中国移动云盘存储驱动上传大小为0的markdown文件失败

[xuchuang199636]

Please make sure of the following things

• I have read the documentation.
• I'm sure there are no duplicate issues or discussions.
• I'm sure it's due to alist and not something else(such as Dependencies or Operational).
• I'm sure I'm using the latest version

Alist Version / Alist 版本

v3.20.1

Driver used / 使用的存储驱动

中国移动云盘

Describe the bug / 问题描述

上传文件大小为0的markdown文件失败。

Reproduction / 复现链接

复现步骤：①在本地新建一个大小为0的markdown文件。②在AList网页客户端创建一个中国移动云盘的存储。③使用AList网页客户端的上传文件功能，将步骤①的文件上传到步骤②创建的存储。

复现预计的效果：检查中国移动云盘官网对应的目录，将会发现上述步骤③并没有成功，即对应的大小为0的markdown文件并没有上传成功。

Logs / 日志

No response

[welcome]

Thanks for opening your first issue here! Be sure to follow the issue template!

[anwen-anyi]

好像0b文件不止和彩云 我试了天翼 魔盘 联通 Teambition， 123倒是可以上传（正好在一个文件挂载着）其他没试了

天翼

code: IncompleteUpload ,msg: sessionKey=814f9a94-1f4a-4059-a83d-5899d62bd3c1, uploaded part number less than total slice part number, please continue uploaded! requestId=a20cc6b5-9abb-4577-9597-db5bf6cebaf2

魔盘

parsing time "Jul 6, 2023 8:31:21 PM +08" as "Jan 02, 2006 15:04:05 PM -07": cannot parse "6, 2023 8:31:21 PM +08" as "02"

联通

partIndex: 1, failed to upload2C with http status: 400, body: Bad Request

Teambition

�[31mERRO�[0m[2023-07-06 20:34:19] failed put /其他/TB团队/: 参数有误
github.com/alist-org/alist/v3/internal/op.Put
	api.nn.ci/alist/internal/op/fs.go:569
github.com/alist-org/alist/v3/internal/fs.putDirectly
	api.nn.ci/alist/internal/fs/put.go:54
github.com/alist-org/alist/v3/internal/fs.PutDirectly
	api.nn.ci/alist/internal/fs/fs.go:97
github.com/alist-org/alist/v3/server/handles.FsStream
	api.nn.ci/alist/server/handles/fsup.go:49
github.com/gin-gonic/gin.(*Context).Next
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/alist-org/alist/v3/server/middlewares.FsUp
	api.nn.ci/alist/server/middlewares/fsup.go:43
github.com/gin-gonic/gin.(*Context).Next
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/alist-org/alist/v3/server/middlewares.Auth
	api.nn.ci/alist/server/middlewares/auth.go:67
github.com/gin-gonic/gin.(*Context).Next
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/alist-org/alist/v3/server/middlewares.StoragesLoaded
	api.nn.ci/alist/server/middlewares/check.go:14
github.com/gin-gonic/gin.(*Context).Next
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/gin-gonic/gin.CustomRecoveryWithWriter.func1
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/recovery.go:102
github.com/gin-gonic/gin.(*Context).Next
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/gin-gonic/gin.LoggerWithConfig.func1
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/logger.go:240
github.com/gin-gonic/gin.(*Context).Next
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/context.go:174
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/gin.go:620
github.com/gin-gonic/gin.(*Engine).ServeHTTP
	C:go/pkg/mod/github.com/gin-gonic/gin@v1.9.1/gin.go:576
net/http.serverHandler.ServeHTTP
	C:/Program Files/Go/src/net/http/server.go:2936
net/http.(*conn).serve
	C:/Program Files/Go/src/net/http/server.go:1995
runtime.goexit
	C:/Program Files/Go/src/runtime/asm_amd64.s:1598 

结论

上面的运营商的是在前端复制的，实际上日志和Teambition团队协作的错误一样

github.com/alist-org/alist/v3/internal/op.Put

[luneew]

上传那里分段数有问题，没有空文件这种场景