Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Update dependencies for Windows build and drop 32-bit support #567
Update dependencies for Windows build and drop 32-bit support #567
Changes from 7 commits
9226df1
2bff820
c96642a
645dd23
aacd7ed
c67e7c7
60c6674
8deb5b2
681301c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are these strings instead of actual true/false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same reason as with the input array: since
setup-mssql
is a composite action, it will coerce any value to be a string.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's on the receiver side though right? I'm thinking of it from our side, the user side, where normal values seem more ergonomic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, receiver's end.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be a yaml list instead of a comma delimited string?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are different types of custom GitHub Actions you can build: Composite, Docker and JavaScript. The last one is the only one that supports other types than strings, see discussion here.
Means the
setup-mssql
action will receive this comma-separated list as string. The action is a composite action and uses PowerShell behind the scenes. This comma-separated list format is easier to parse from PowerShell.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you would build tiny_tds using our "ports" mechanic, you will also get these versions. Our Linux CI build actually also uses these versions. For installations outside of our CI, the discovered freetds version is used, which could be anything.
There is a chance that something breaks. As mentioned on the PR, I wanted to make sure that
tiny_tds
generally works when using encrypted connections by adding this new scenario on CI. But I can imagine that there are some configurations that will no longer work with this new OpenSSL version.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, exactly. That's what most people will be using across all OS's since we go from CI artifact -> rubygems.org, right? So it seems more accurate to drop the "for Windows" part of the sentence is what I'm saying
Is there any other consideration to add to the changelog? Minimum OS version, minimum glibc version, etc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not exactly.
When you install
tiny_tds
on Linux or Mac OS, Rubygems will discover that we have some C code in the gem and will try to compile it. In order fortiny_tds
to compile, it tries to discover an installation offreetds
. This process does not invoke ourports
mechanic in casefreetds
is missing, but fails instead.So all people on non-Windows machines will compile
freetds
on their own first, likely according to our installation instructions.Mid-term I would like to explore if we could provide precompiled versions of
tiny_tds
for all platforms, similar as Nokogiri did a while back. It would simplify the installation for the end-user.Don't think so. I still would like to release the next version as v3 just to signal that there might be breaking changes.