Skip to content

support for atomic writes for gcp#3523

Merged
jba merged 6 commits intogoogle:masterfrom
sandeepvinayak:spal-atomic-writes-gcp-memstore
Mar 12, 2025
Merged

support for atomic writes for gcp#3523
jba merged 6 commits intogoogle:masterfrom
sandeepvinayak:spal-atomic-writes-gcp-memstore

Conversation

@sandeepvinayak
Copy link
Contributor

Please use a title starting with the name of the affected package, or "all",
followed by a colon, followed by a short summary of the issue. Example:
blob/gcsblob: fix typo in documentation.

Please reference any Issue related to this Pull Request. Example: Fixes #1.

See
here
for tips on good Pull Request description.

@sandeepvinayak
Copy link
Contributor Author

@jba FYI

@sandeepvinayak sandeepvinayak force-pushed the spal-atomic-writes-gcp-memstore branch from 2a9a605 to 0ab460e Compare February 17, 2025 16:21
@sandeepvinayak
Copy link
Contributor Author

@jba just a friendly reminder if you can take a look at this PR. I have also added mongo implementation as well, enabled al the conformance tests.

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@jba
Copy link
Contributor

jba commented Mar 10, 2025

Please address failing checks.

@sandeepvinayak
Copy link
Contributor Author

@jba it should be good now. thanks!

@sandeepvinayak sandeepvinayak force-pushed the spal-atomic-writes-gcp-memstore branch from 3d7ba74 to 42f717d Compare March 10, 2025 22:06
@sandeepvinayak
Copy link
Contributor Author

@jba runchecks on local are good except some kafka failures due to connection issues which is unrelated to this PR. Can you please retrigger the workflow for me? Or maybe you can give me a permission to trigger the workflow ?

@codecov
Copy link

codecov bot commented Mar 10, 2025

Codecov Report

Attention: Patch coverage is 60.52632% with 45 lines in your changes missing coverage. Please review.

Project coverage is 73.29%. Comparing base (cbd7084) to head (42f717d).
Report is 2 commits behind head on master.

Files with missing lines Patch % Lines
docstore/mongodocstore/mongo.go 56.38% 33 Missing and 8 partials ⚠️
docstore/gcpfirestore/fs.go 80.00% 2 Missing and 2 partials ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3523      +/-   ##
==========================================
+ Coverage   73.26%   73.29%   +0.03%     
==========================================
  Files         113      113              
  Lines       15079    15190     +111     
==========================================
+ Hits        11048    11134      +86     
- Misses       3265     3277      +12     
- Partials      766      779      +13     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@sandeepvinayak
Copy link
Contributor Author

The CI seems to be good now, please help to merge when you get chance, thank you!

@sandeepvinayak
Copy link
Contributor Author

@jba just a reminder to merge if this is good to go, thanks!

@jba jba merged commit da0b8ec into google:master Mar 12, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants