-
-
Notifications
You must be signed in to change notification settings - Fork 846
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
Create temporary cache files in Dir.tmpdir #459
Create temporary cache files in Dir.tmpdir #459
Conversation
1ec990d
to
d264fec
Compare
(There were linting problems due to changed rules, rebased against new master.) |
I'll see if I can build it locally to test. |
Seems to still be failing in the same place:
Note that
Something seems to be up though, since if I manually put the proper temp path in there it still gives that same path, trying to trace down whether |
Okay, the options object coming into the My unreleased=true
future-release=v0.12.0
exclude_labels=duplicate,question,invalid,wontfix,Duplicate,Question,Invalid,Wontfix,External |
I literally just found that and looked over here to post that only to see your comment appear 😛! |
@Arcanemagus If you change those to the starting value
|
I hit the following then:
This does look related to the spec failure, want a new issue filed for that? |
@Arcanemagus No, this is not an issue with the program, my guess is it's that's a SSL certificates issue, related to your machine not having certificate authorities' certificate bundles available to it. Here's a long article about it: http://mislav.net/2013/07/ruby-openssl/ |
I understand that it's an SSL error, my point (as a user) is that v1.13.2 works, and v1.14.0 (and up) doesn't due to that. From what I've been finding around on the web the "solution" seems to all point to variants of http://stackoverflow.com/a/16134586/631338 which is a bit silly to expect all your users to have to go through. |
4b282bd
to
2012940
Compare
lostisland/faraday#392 (comment) is exactly my point, this is on I'm assuming that's why |
I'm not saying you're wrong. Commits like this: ...they put a lot of responsibility in the hands of the individual project: when a cert is un-trusted for some reason, the project's got to update their cert bundle. Example: I'll mull on this. |
@Arcanemagus In order to solve one thing at a time, can we open a new Windows-labeled issue for the |
@Arcanemagus In order for the Issue to be owned by you, can you open it, and make links and such? (I don't run Windows.) |
Already writing it 😉. |
This PR is a compatibility bugfix for an issue on Windows.
See #458
Question: Does it work for you, @Arcanemagus? (Update: no, but that's another issue.)
Additional note: A directory such as
C:\tmp
must exist on the Windows machine for this to work right.