Cloud repository - SSL Error #54506
Labels
No Label
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Websites
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-cloud#54506
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
OS X 10.12.6, NVIDIA GeForce GTX 780M 4096 MB
Blender Version
Broken: 2.79.4
Worked: 2.79b
Short description of error
I can't login and open Blender Cloud Repository with daily builds.
Exact steps for others to reproduce the error
I can reproduce it with today build (31f2a6755db) too.
Factory setting.
Behaviour is like this:
2.79.4 (daily build 31f2a6755db) I can't login.
2.79b (official) I can and I can also access repository
than if I'm logged in with official 2.79b
2.79.4 I see I'm logged
2.79.4 I can't still access cloud repository
Thank you for help
I had already discussion with Sybren, he asked me to run this commands (see screen).
After that he direct me to post it here.
(Left side official 2.79b / Right side daily 2.79.3 in that time)
Added subscriber: @FilipMond
Added subscribers: @Sergey, @ArtoKitula
On my macOS local build, this is working. Might be that buildbot isn't working as it should. svn problem or something like that. @Sergey ? Or anyone who has access to mac buildbot.
@ArtoKitula, can you reproduce the issue with buildbot builds on your machine?
@Sergey Actually just now realized that this happens because of the application translocator, the very reason we give releases on signed DMG.
@FilipMond Could you try to start blender from Terminal ?
Added subscriber: @brecht
Buildbot should also be making signed dmg files I think, really the only difference with release builds should be the revision it's built from.
@ArtoKitula, do you think it will be smart idea and possible to sign buildbot binaries? Last time i've tried to sign in a headless mode, codesign gave me error code
0xffffffff
...@Sergey It is possible. I've got script that works, just needs some caring to do neat dmg. I'll push it when ready (next week latest).
Added subscriber: @lichtwerk
@ArtoKitula , assigning to you then?
[@Arto Kitula (akitula) ]] If you mentioned "translocation" issue - Do you mean [ https:*developer.blender.org/T49473 | "double docking" issue? Because I already moved blender out and in a directory, to "fix" that with mentioned build. But SSL error appeared before and after (double docking) anyway.
Running from Terminal - here is the output fromTerminal.txt if it helps in some way.
I also moved out all user files to run clear Blender and downloaded Blender Cloud addon to get all fresh :)
@lichtwerk yeah, that's ok.
@FilipMond Yeah so this is not because of application translocation. Wondering why ssl module is not found. When I downloaded latest build from buildbot, it works.
What does following code give you?
That's just as it should. If you go that folder, does it have ssl.py ?
No.
In folder "site-packages" is only "easy_install.py"
Filtering with blender's file browser displayed only this file containing SSL.
Here is what inside "site-packages" folder
EDIT:
But "ssl.py" is in level up in "python3.6" folder as you can see on screen too.
That's probably you asked for, right?
Oops, that one level up is correct. Could you start the build with all debugging options on. And then just hit import ssl to python console and post the whole debug output.
Marking this as incomplete for now.
Thanks for reliance :) but what the hell is "start the build with all debugging options on"? :) Sorry, simple designer on this side of cable.
I would like to help you, but be a bit more descriptive for me, thank you. I will try my best.
No pressure =)
Let's do also factory startup so your preferences and some addons aren't affecting this:
That is just for debugging python, --debug-all includes all debug messages. Let's start with --debug-python for now.
Here it is, just a note when I started now from terminal I was still logged in (by official 2.79b version) and I tried to open cloud from image editor, or should I log out first?
--debug-python.txt
--debug-all.txt
What if you move directory /Users/filip/Library/Application Support/Blender/2.79/ away and start blender again, and install the latest cloud addon?
That's exactly what I did yesterday.
Same error.
Should I do it again for you to get generated console output?
Added subscriber: @dr.sybren
We have a report (infrastructure/blender-open-data#56329) with the same issue in the Benchmark Client, so it's not just buildbot-builds.
Changed status from 'Open' to: 'Resolved'
This will be fixed now in the latest daily builds after blender/blender@cd5db90726.