-
Notifications
You must be signed in to change notification settings - Fork 49
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
PG17 Support #820
PG17 Support #820
Conversation
Co-authored-by: Sebastian Webber <[email protected]> Signed-off-by: Vinh <[email protected]>
…lkit into pg17-support
WIP: Pg17
The latest pgrx requires 1.82; you need to bump the Rust toolchain version. |
#821 to bump toolchain to 1.82.0 |
pgrx's upstream is using 1.81.0... are we sure 1.82.0 is required? I'm going to push a commit on this branch to see if it helps, feel free to drop/modify it. Nope, too bad :\ |
Shame I can't make commits directly to the branch. Could you try with it bumped to 1.82? |
12ef55c
to
ec58425
Compare
Pushed again with 82, It's the same error for 81 and 82:
|
I'm curious now if we are even using the correct image for running the tests. |
I haven't actually tested it locally- if you have, and it works, it sounds like purely a CI issue unfortunately. |
ec58425
to
734dd00
Compare
Confirmed: CI is attempting to build with rustc: 1.74.0 (79e9716c9 2023-11-13) |
I think I see what's going on with the image build and tagging now. Seems the default tag (Example2) we are pushing to the CR for these runs are
Do we need to do a manual run of |
Btw I was building this branch locally and was able to get past the |
This container is built in CI with the current release, so use that one when testing.
@zilder how are things going? I've been fighting WSL2 in the free time I've had trying to help out with the compilation errors. |
Hey @Jo0, it took me some time to wrap my head around macros-based code generation in toolkit. With pgrx 0.12+ it seems most issues come from new requirements for |
Merged as part of #824 |
Imported through #819 /cc @Jo0