| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
This reverts commit 5874f8b.
Summary of ChangesHello @olavloite, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request serves to completely undo a previous change (PR #4236) that aimed to incorporate PostgreSQL error codes into SpannerException instances. The decision to revert was made due to the original feature causing benchmark tests to fail, which indicated a negative impact on performance or stability. By reverting these changes, the codebase is restored to a known stable state, ensuring the reliability and expected performance of the system. Highlights
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here. Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
Sorry, something went wrong.
|
(Do not merge yet, we can probably re-run the benchmarks based on the old commit) |
Sorry, something went wrong.
There was a problem hiding this comment.
This pull request reverts a feature that was causing benchmark test failures. The changes correctly remove the logic for including PostgreSQL error codes in exceptions and revert the related API changes in SpannerException. However, I've noticed a few inconsistencies in the revert where asSpannerException is not replaced by newSpannerException but is instead fully qualified. I've left comments on these specific locations. Otherwise, the revert looks correct.
Sorry, something went wrong.
| } catch (Throwable t) { | ||
| throw yieldError( | ||
| asSpannerException(t), | ||
| SpannerExceptionFactory.asSpannerException(t), |
There was a problem hiding this comment.
This change seems inconsistent with the rest of the revert. Other occurrences of asSpannerException are being changed to newSpannerException, but this one is kept and fully qualified. For consistency, shouldn't this also be changed to newSpannerException(t)? The static import for newSpannerException is available.
| SpannerExceptionFactory.asSpannerException(t), | |
| newSpannerException(t), |
Sorry, something went wrong.
| NanoClock.getDefaultClock()); | ||
| } catch (RetryHelperException e) { | ||
| throw asSpannerException(e.getCause()); | ||
| throw SpannerExceptionFactory.asSpannerException(e.getCause()); |
There was a problem hiding this comment.
This change to fully qualify asSpannerException seems inconsistent with the overall goal of the revert, which appears to be replacing asSpannerException with newSpannerException. Other parts of this file and the PR make that replacement. For consistency, this should probably be newSpannerException(e.getCause()).
| throw SpannerExceptionFactory.asSpannerException(e.getCause()); | |
| throw newSpannerException(e.getCause()); |
Sorry, something went wrong.
| } catch (ExecutionException e) { | ||
| Throwable t = e.getCause(); | ||
| SpannerException se = asSpannerException(t); | ||
| SpannerException se = SpannerExceptionFactory.asSpannerException(t); |
There was a problem hiding this comment.
Similar to other comments, this change to fully qualify asSpannerException is inconsistent with the revert. To maintain consistency with other changes in this PR, this should probably be newSpannerException(t).
| SpannerException se = SpannerExceptionFactory.asSpannerException(t); | |
| SpannerException se = newSpannerException(t); |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Benchmark tests are failing after submitting this change.
Reverts #4236