-
-
Notifications
You must be signed in to change notification settings - Fork 253
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
cargo pgx test
fails on new project after upgrading to 0.4.5
#610
Comments
I was unable to replicate this on my Linux machine. I'm just stepping out for the day but I can try to replicate this on my M1 tomorrow. Thanks for the report! |
Was able to get unblocked on this by uninstalling, deleting the cargo uninstall cargo-pgx
rm -rf ~/.pgx
cargo install cargo-pgx
cargo pgx init |
Running into this issue as well, with the same setup. Just started developing the extension, so started on 0.4.5 and testing was working initially. Now testing doesn't work even when using the sample project. Unfortunately for me, reinstalling did not solve it. I also tried the 0.5.0-beta.0 version. For the benefit of GH search (I was getting the same error at times, though it no longer is being shown): Sorry, I don't have anything to add, will report back if I do. |
The issue appeared for me again after 1 successful run of re-opening since ^ is experiencing it too |
I no longer have access to an M1 Mac so unfortunately I cannot help anymore. Perhaps someone with an M1 mac can help. |
Probably was not solved by #687 but that was a patch of UB so in reality: lol who knows, anything goes. |
Please try pgx = "0.5.6" in your Cargo.toml and confirm if this is fixed or still broken? |
After upgrading from from
0.4.0
to0.4.5
withcargo pgx test
now fails existing and brand-new projects created withcargo pgx new pg_sample
setup
results in:
But when installing with
cargo pgx run
orcargo pgx install
and test the extensions manually they work fine so I think its limited to testing.System:
The text was updated successfully, but these errors were encountered: