ikedam
ikedam
I agree adding tests improves our development. I’ll take a look on test features of the serverless framework.
> the default should still be squashing the commits together. I agree. This should be provided with an option parameter. I’ll see I can use s3 meta data, like tags.
@j-rewerts Unfortunately, not yet. I’m a newbie to nodejs and serverless framework and needs much effort to develop this.
@recena Actually I can't get why you mentioned me as I haven't participate github-plugin nor JENKINS-43786. You might have mistaken me for someone else to invite.
Example pipeline to reproduce this issue: ``` node { // Code Build that does nothing at all. writeFile( file: 'buildspec.yaml', text: 'version: 0.2\nphases:\n build:\n commands:\n - true\n', ) // Create...
I believe this relates to https://stackoverflow.com/questions/63238344/amazon-s3-how-parallel-puts-to-the-same-key-are-resolved-in-versioned-buckets . The root cause is the limitation (not rate limit!) of S3, and clients must retry the upload if the request fail with 5xx.
It thows `ResetExcetion`: ``` com.amazonaws.ResetException: The request to the service failed with a retryable reason, but resetting the request input stream has failed. See exception.getExtraInfo or debug-level logging for the...
Called `zipFileInputStream.mark(1024);`, but that doesn't fix the issue.
Same issue in M5EPD (m5paper): m5stack/M5EPD#21
Available * v3.6.1 (15 Sep 2020) Not available * v3.7.0 (25 Mar 2021) * v3.7.1 (9 Apr 2021)