Skip to content

cargo: use neon branch of rust-postgres #9757

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

Merged
merged 1 commit into from
Nov 14, 2024

Conversation

VladLazar
Copy link
Contributor

@VladLazar VladLazar commented Nov 14, 2024

Problem

We are pining our fork of rust-postgres to a commit hash and that prevents us from making
further changes to it. The latest commit in rust-postgres requires #8747,
but that seems to have gone stale. I reverted rust-postgres neon branch to the pinned commit in neondatabase/rust-postgres#31.

Summary of changes

Switch back to using the neon branch of the rust-postgres fork.

cc: @conradludgate

@VladLazar VladLazar requested a review from hlinnaka November 14, 2024 11:02
Copy link

5400 tests run: 5173 passed, 0 failed, 227 skipped (full report)


Code coverage* (full report)

  • functions: 31.8% (7891 of 24837 functions)
  • lines: 49.4% (62451 of 126324 lines)

* collected from Rust tests only


The comment gets automatically updated with the latest test results
043b8f5 at 2024-11-14T12:26:50.916Z :recycle:

@VladLazar VladLazar merged commit 21282aa into main Nov 14, 2024
82 checks passed
@VladLazar VladLazar deleted the vlad/use-rust-postgres-neon-branch branch November 14, 2024 15:16
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