Skip to content

Conversation

@zeroshade
Copy link
Member

expanding the solution from #2889 We can make sure that we inject the proper version string into the internal/driverbase handling. This should populate the GetInfo correctly with the driver version via vcs information.

@zeroshade zeroshade requested a review from lidavidm as a code owner June 2, 2025 21:10
@github-actions github-actions bot added this to the ADBC Libraries 19 milestone Jun 2, 2025
Copy link
Member Author

@zeroshade zeroshade left a comment

Choose a reason for hiding this comment

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

@davidhcoe Can you check this out and test it with your workflows to ensure it works outside of my testing?

Copy link
Member

@lidavidm lidavidm left a comment

Choose a reason for hiding this comment

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

What happens if you build outside of CMake and outside of Git/the Makefile? (I don't think we ever do this...)

@davidhcoe
Copy link
Contributor

@davidhcoe Can you check this out and test it with your workflows to ensure it works outside of my testing?

yes, I will try it out tomorrow.

@davidhcoe
Copy link
Contributor

The version comes back as apache-arrow-adbc-17-dev for me. Does that mean 1.7? It's a little confusing because we are on Adbc 19 (and C# reports as v19), but I recognize Go and C# are on different paths.

Is the dev an indicator of something in particular?

@zeroshade
Copy link
Member Author

Oy, looks like this is gonna be more difficult than I thought because of the tag aliases.

Quick question: did you build with cmake? Or the makefile in the pkg directory?

@davidhcoe
Copy link
Contributor

davidhcoe commented Jun 3, 2025 via email

@zeroshade
Copy link
Member Author

@davidhcoe Can you try the updated version I just pushed?

Is the dev an indicator of something in particular?

Yea, it indicates that when it was built Go's build info had vcs.modified=true indicating that the source tree wasn't clean

@davidhcoe
Copy link
Contributor

@davidhcoe Can you try the updated version I just pushed?

Is the dev an indicator of something in particular?

Yea, it indicates that when it was built Go's build info had vcs.modified=true indicating that the source tree wasn't clean

It shows me the version is -dev now.

@zeroshade
Copy link
Member Author

@davidhcoe are you working on a fork or on a clone of the main repo? Can you make sure you pull all the tags down locally?

@davidhcoe
Copy link
Contributor

Maybe I am missing something here. I deleted then re-cloned the repo. I ran git fetch --tags. I pulled your PR. Then I ran make libadbc_driver_snowflake.dll from arrow-adbc\go\adbc\pkg. Now, the driver version is back to saying (unknown or development build).

@zeroshade
Copy link
Member Author

That's REALLY weird.

For the heck of it, can you try building with cmake and let me know if it picks up the version correctly?

@zeroshade zeroshade force-pushed the static-version-handling branch from c5bb683 to 6b25f11 Compare June 18, 2025 15:24
@davidhcoe
Copy link
Contributor

I get v1.6.0-dev with your latest push.

@zeroshade
Copy link
Member Author

from building with the Makefile in pkg? That makes sense given that it's pulling the version from the git tags. Is that sufficient for you? Does it need to be different?

@davidhcoe
Copy link
Contributor

davidhcoe commented Jun 18, 2025 via email

@lidavidm
Copy link
Member

I gave it a test and the drivers built by CI report version v1.7.0-SNAPSHOT. That's actually somewhat surprising, if it's supposed to be pulling things from Git, but it is right...

The C++ drivers need to have the same thing done ideally but that can be done separately

@lidavidm
Copy link
Member

Ah, it's because the CMake version is getting injected in. I'm guessing David Coe is building off of a fork of v1.6.0 or has local changes - then it would combine the v1.6.0 in CMakeLists.txt with -dev since the worktree is apparently dirty.

@lidavidm
Copy link
Member

Pushed a small fix to the one failing test. Then I'll merge.

@lidavidm lidavidm merged commit c84cc91 into apache:main Jun 19, 2025
68 checks passed
@lidavidm
Copy link
Member

I filed #3000 for PostgreSQL/SQLite to also have this fix

@davidhcoe
Copy link
Contributor

davidhcoe commented Jun 19, 2025 via email

@lidavidm
Copy link
Member

Ah ok. But 1.6.0 can come from the tags. I was just slightly confused at first why 1.7.0 (which isn't yet tagged) came in and had to review the CMakeLists config

@zeroshade zeroshade deleted the static-version-handling branch June 19, 2025 14:50
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.

3 participants