Skip to content
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

ci: fix warnings and notices when compiling with latest V 0.4.0 320057d #159

Closed

Conversation

spytheman
Copy link
Contributor

@spytheman spytheman commented Aug 7, 2023

After the deprecation of the .microsecond field of time.Time, and the addition of a notice about uninitialised fn callback fields, vsql can not be compiled cleanly with just make bin/vsql .

This PR fixes it.

…7d, after the deprecation of the .microsecond field of time.Time, and the notice about uninitialised fn callback fields
@spytheman spytheman changed the title ci: fix warnings and notices when compiling with latest V 0.4.0 320057d, after the deprecation of the .microsecond field of time.Time, and the notice about uninitialised fn callback fields ci: fix warnings and notices when compiling with latest V 0.4.0 320057d Aug 7, 2023
@@ -23,67 +23,6 @@ fn catalog_name_from_path



fn new_varchar_value
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the build is failing because there are coming are not being written in a deterministic order. I think you need to add a sort here: https://github.com/elliotchance/vsql/blob/main/scripts/generate-v-client-library-docs.vsh#L32

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All right, they are now sorted with dcs_contents.sort_by_kind() .

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me, running make clean-docs docs does not change the order.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like there are some legitimate build failures now.

Copy link
Contributor Author

@spytheman spytheman Aug 8, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like there are some legitimate build failures now.

Indeed. Given that vsql has not changed since May, I think there is a codegen regression in V. I'll bisect later today to see when it happened and what caused it.

It could also be related to the .microsecond -> .nanosecond change in the time module, but that seems less likely to me.

@elliotchance
Copy link
Owner

Thanks for the effort, but I've cleaned this up with #160

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