Skip to content
New issue

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

deps: update module github.com/spf13/afero to v1.9.3 #654

Merged
merged 1 commit into from
Jan 20, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 18, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
github.com/spf13/afero require minor v1.6.0 -> v1.9.3

Release Notes

spf13/afero

v1.9.3

Compare Source

What's Changed

Full Changelog: spf13/afero@v1.9.2...v1.9.3

v1.9.2

Compare Source

What's Changed

Full Changelog: spf13/afero@v1.9.1...v1.9.2

v1.9.1

Compare Source

What's Changed

Full Changelog: spf13/afero@v1.9.0...v1.9.1

v1.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: spf13/afero@v1.8.2...v1.9.0

v1.8.2: : RemoveAll fixes in MemMapFs and GcsFs

Compare Source

v1.8.1: : memfs: add modTime on folder creation

Compare Source

v1.8.0: : Support sftpfs.Readdirnames, sftpfs.Readdir, CacheOnReadFs bugfix

Compare Source

  • sftpfs: Add support for Readdirnames and Readdir
  • CacheOnReadFs: Call OpenFile instead of Open in CacheOnReadFs.OpenFile

v1.7.1: : Move GCS into its own package

Compare Source

v1.7.0: : Add experimental GCS support

Compare Source

Add experimental GCS support in Afero. Experimental because the CI infra of afero does not test with real GCS buckets.

Limitations:

  • No Chmod support - The GCS ACL could probably be mapped to *nix style permissions but that would add another level of complexity and is ignored in this version.
  • No Chtimes support - Could be simulated with attributes (gcs a/m-times are set implicitly) but that's is left for another version.
  • NOTE: Not thread safe - Also assumes all file operations are done through the same instance of the GcsFs. File operations between different GcsFs instances are not guaranteed to be consistent.

Performance implications

  • Sequential reads are performant
  • Sequential writes are performant.
  • Seek + Read or ReadAt is performant after the initial seek. (produces a warning)
  • Alternating reads/writes to the same file handler are highly inefficient. To get consistent FS behavior using an API that separates readers and writers we close any open readers before an write as well close open writers before a read (ensure the data is committed).
  • Seek + Write such as WriteAt, Truncate, Seek+Write will work as expected but with significant overhead. Doing a seek + write will in effect download the old file/object, overlay it with the new writes and save it back. This is done in a streaming fashion so large files will not clog the memory but will trigger a full download and upload of the file/object.

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@codecov
Copy link

codecov bot commented Jan 18, 2023

Codecov Report

Merging #654 (cb30258) into main (da8fcee) will increase coverage by 0.05%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #654      +/-   ##
==========================================
+ Coverage   56.39%   56.45%   +0.05%     
==========================================
  Files          82       82              
  Lines        6683     6683              
==========================================
+ Hits         3769     3773       +4     
+ Misses       2755     2752       -3     
+ Partials      159      158       -1     
Impacted Files Coverage Δ
...lers/lifecycle/keptnworkloadinstance/controller.go 78.24% <0.00%> (+1.85%) ⬆️
Flag Coverage Δ
component-tests 53.37% <ø> (+0.52%) ⬆️
keptn-cert-manager 67.56% <ø> (ø)
keptn-lifecycle-operator 52.01% <ø> (ø)
scheduler 21.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@renovate renovate bot force-pushed the renovate/github.com-spf13-afero-1.x branch from 0a3d4ee to 45d9ed8 Compare January 19, 2023 10:53
Signed-off-by: Renovate Bot <bot@renovateapp.com>
@renovate renovate bot force-pushed the renovate/github.com-spf13-afero-1.x branch from 45d9ed8 to cb30258 Compare January 20, 2023 09:31
@sonarcloud
Copy link

sonarcloud bot commented Jan 20, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@odubajDT odubajDT merged commit 2831566 into main Jan 20, 2023
@odubajDT odubajDT deleted the renovate/github.com-spf13-afero-1.x branch January 20, 2023 10:23
@keptn-bot keptn-bot mentioned this pull request Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants