-
Notifications
You must be signed in to change notification settings - Fork 408
feat(spanner): add spanner::Value support for TypeCode::UUID #15076
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
base: main
Are you sure you want to change the base?
Conversation
/gcbrun |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #15076 +/- ##
=======================================
Coverage 92.92% 92.92%
=======================================
Files 2389 2389
Lines 214832 214886 +54
=======================================
+ Hits 199631 199693 +62
+ Misses 15201 15193 -8 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @devbww)
Thanks again for the PR. While the protos defining the UUID field are public, service support for the type isn't live yet. We'll merge this PR and write some integration tests when UUID is available in production. |
Okie dokie. |
PiperOrigin-RevId: 745629297
* feat(devicestreaming): generate library * Run generators and format their outputs * Add API baseline * Manually update READMEs, quickstart, and top-level stuff * changelog
* fix: fix bug with customheadersoption * fix: fix bug with customheadersoption * fix: fix bug with customheadersoption * fix: fix bug with customheadersoption * fix: fix bug with customheadersoption * fix: fix bug with customheadersoption * fix: fix bug with customheadersoption --------- Co-authored-by: Denis DelGrosso <85250797+ddelgrosso1@users.noreply.github.com>
… in storage_object_samples (googleapis#15059) istream_iterator skips whitespace by default which results in data not being read as-is when it has whitespace symbols/bytes in it. Co-authored-by: Denis DelGrosso <85250797+ddelgrosso1@users.noreply.github.com>
* chore: update googleapis SHA circa 2025-04-16 PiperOrigin-RevId: 748054282
* feat(chronicle): generate library * Run generators and format their outputs * Manually update READMEs, quickstart, and top-level stuff * Add API baseline * add endpoint option for quickstart
/gcbrun |
I would proffer that this should be merged irrespective of the rollout of service support. It is the server support that actually matters, not the conversion between types within the client. Also, merging now would mean that there is no need to wait for a new client release when server support is enabled. And that means client-side development can start early, including writing the integration tests, which can also actually be run against the staging service. Finally, it avoids the possibility of future merge conflicts. |
This change is