We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
你好, 我们在 composer.json 内的版本指定是 ^7.2,所以在发布过程时 composer install,自动使用了 v.7.3.0版本,在调用 move方法时持续报错,后续排查发现 BucketManager.php move() 方法作了如下改动
list(, $error) = $this->rsPost($path); return $error;
=> return $this->rsPost($path);
return $this->rsPost($path);
同时 examples/rs_move.php 内容未同步,还是旧的demo
$err = $bucketManager->move($srcBucket, $srcKey, $destBucket, $destKey, true); if ($err) { print_r($err); }
有以下疑问, 为什么 v.7.2.10 => v7.3.0 旧函数的响应格式会做不兼容改动?成功响应 null 变成了一个 array(null, null)。同时不能明确其他可能造成的兼容影响,没法尝试直接升级,目前只能指定 "7.2.*"。
The text was updated successfully, but these errors were encountered:
No branches or pull requests
你好,
我们在 composer.json 内的版本指定是 ^7.2,所以在发布过程时 composer install,自动使用了 v.7.3.0版本,在调用 move方法时持续报错,后续排查发现 BucketManager.php move() 方法作了如下改动
=>
return $this->rsPost($path);
同时 examples/rs_move.php 内容未同步,还是旧的demo
有以下疑问,
为什么 v.7.2.10 => v7.3.0 旧函数的响应格式会做不兼容改动?成功响应 null 变成了一个 array(null, null)。同时不能明确其他可能造成的兼容影响,没法尝试直接升级,目前只能指定 "7.2.*"。
The text was updated successfully, but these errors were encountered: