|
Main /
SupportForImplementAndExtendInPtolemyIIDiscussionBelow are discussion and design notes about how we check out the accessors repo inside the ptII tree. See AlsoConfigure BehaviorBelow, we outline various behaviours of configure Anonymous PTII SVN, No CertificateIf the user checks out the ptII tree with anonymous svn and temporarily accepts the certificate: bash-3.2$ bash-3.2$ time svn co https://repo.eecs.berkeley.edu/svn-anon/projects/eal/ptII/trunk ptII-anon Error validating server certificate for 'https://repo.eecs.berkeley.edu:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: repo.eecs.berkeley.edu - Valid: from Fri, 11 Apr 2014 00:00:00 GMT until Mon, 10 Apr 2017 23:59:59 GMT - Issuer: InCommon, Internet2, US - Fingerprint: 7f:00:eb:6b:48:e3:77:0f:34:d8:f4:92:5f:57:39:6e:a6:12:34:e0 (R)eject, accept (t)emporarily or accept (p)ermanently? t A ptII-anon/copyright.htm A ptII-anon/vergil.jnlp.in ... Then, when Error validating server certificate for 'https://repo.eecs.berkeley.edu:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: repo.eecs.berkeley.edu - Valid: from Fri, 11 Apr 2014 00:00:00 GMT until Mon, 10 Apr 2017 23:59:59 GMT - Issuer: InCommon, Internet2, US - Fingerprint: 7f:00:eb:6b:48:e3:77:0f:34:d8:f4:92:5f:57:39:6e:a6:12:34:e0 (R)eject, accept (t)emporarily or accept (p)ermanently? svn: E175002: Unable to connect to a repository at URL 'https://repo.eecs.berkeley.edu/svn/projects\ /terraswarm/accessors/trunk/accessors' svn: E175002: OPTIONS of 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors': Server certificate verification failed: issuer\ is not trusted (https://repo.eecs.berkeley.edu) configure: WARNING: Could not check out the accessors svn repo. Accessors that extend the TerraSwarm accessors will not work. checking for ant... /usr/local/bin/ant The above is ok, but can be fixed by adding Anonymous PTII SVN, Certificate acceptedIf the user who has an anonymous tree but no access to the repo then does a bash-3.2$ svn update Updating '.': Error validating server certificate for 'https://repo.eecs.berkeley.edu:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: repo.eecs.berkeley.edu - Valid: from Fri, 11 Apr 2014 00:00:00 GMT until Mon, 10 Apr 2017 23:59:59 GMT - Issuer: InCommon, Internet2, US - Fingerprint: 7f:00:eb:6b:48:e3:77:0f:34:d8:f4:92:5f:57:39:6e:a6:12:34:e0 (R)eject, accept (t)emporarily or accept (p)ermanently? p At revision 73242. bash-3.2$ and then runs Authentication realm: <https://repo.eecs.berkeley.edu:443> UCB/EECS Subversion Repository Password for 'cxbrooks': Authentication realm: <https://repo.eecs.berkeley.edu:443> UCB/EECS Subversion Repository Username: svn: E170001: Unable to connect to a repository at URL 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors' svn: E170001: OPTIONS of 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors': authorization failed: Could not authenticate to server: rejected Basic challenge (https://repo.eecs.berkeley.edu) configure: WARNING: Could not check out the accessors svn repo. Accessors that extend the TerraSwarm accessors will not work. checking for ant... /usr/local/bin/ant Problems:
After adding About to check out the accessors repo. This will fail for people who do not have access. svn: E170001: Unable to connect to a repository at URL 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors' svn: E170001: OPTIONS of 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors': authorization failed: Could not authenticate to server: rejected Basic challenge (https://repo.eecs.berkeley.edu) configure: WARNING: Could not check out the accessors svn repo. Accessors that extend the TerraSwarm accessors will not work. Access to the repo is restricted. If you have an account on repo.eecs.berkeley.edu and your login on repo.eecs.berkeley.edu is different than your login, then try cd org/terraswarm/accessor svn co --username yourname@youremail.com https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors and rerun ./configure Now this is ok. Anonymous PTII SVN, No NetworkIf there is no network, then About to check out the accessors repo. This will fail for people who do not have access. svn: E175002: Unable to connect to a repository at URL 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors' svn: E175002: OPTIONS of 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors': Could not resolve hostname `repo.eecs.berkeley.edu': Host not found (https://repo.eecs.berkeley.edu) configure: WARNING: Could not check out the accessors svn repo. Accessors that extend the TerraSwarm accessors will not work. Access to the repo is restricted. If you have an account on repo.eecs.berkeley.edu and your login on repo.eecs.berkeley.edu is different than your login, then try cd org/terraswarm/accessor svn co --username yourname@youremail.com https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors and rerun ./configure checking for ant... /usr/local/bin/ant The above is ok. Runtime BehavioursAnonymous PTII SVN, No access to the repoIf the user does not have access to the accessors repo and then reload an accessor, vergil hangs! Edward wrote: "But then, in vergil, Import Accessor also asks on stdout/in for the password.
No matter what I enter, the exec process hangs and I have to quit vergil. Same thing happens in capecode if I try to expand the accessor library." bash-3.2$ $PTII/bin/vergil org/terraswarm/accessor/demo/Camera/Camera.xml 8297 ms. Memory: 333312K Free: 288149K (86%) Checking out the accessors repository. In "/Users/cxbrooks/ptII-anon/org/terraswarm/accessor", about to execute: svn co https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/accessors Password for 'cxbrooks': Authentication realm: <https://repo.eecs.berkeley.edu:443> UCB/EECS Subversion Repository Solution: Modify JSAccessor.java to invoke svn with Also, the checkout or update keeps happening even after it fails. Solution: Modify JSAccessor.java so that it sets a static boolean if the checkout or update fails. To reset the flag, restart the JVM. Below is a sample run, where we get a bunch of text the first time it fails and then nothing after each reload. [cxbrooks@terratest ptII-anon]$ $PTII/bin/vergil org/terraswarm/accessor/demo/StockTick/StockTick.xml Checking out the accessors repository. In "/home/cxbrooks/ptII-anon/org/terraswarm/accessor", about to execute: svn co --non-interactive --trust-server-cert https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/notreadable svn: OPTIONS of 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/notreadable': authorization failed: Could not authenticate to serve\ r: rejected Basic challenge (https://repo.eecs.berkeley.edu) All Done Failed to check out the accessors repository. Failed to check out the accessors repository. Failed to checkout or update the TerraSwarm accessor repo. This could happen if you don't have read access to the repo.The message was: java.io.IOException: Failed to check out the TerraSwarm accessors repository with: cd /home/cxbrooks/ptII-anon/org/terraswarm/accessor svn co --non-interactive --trust-server-cert https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/notreadable Perhaps you don't have read access?The TerraSwarm accessors repository is under development. The output was: In "/home/cxbrooks/ptII-anon/org/terraswarm/accessor", about to execute: svn co --non-interactive --trust-server-cert https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/notreada ble svn: OPTIONS of 'https://repo.eecs.berkeley.edu/svn/projects/terraswarm/accessors/trunk/notreadable': authorization failed: Could not authenticate to serve\ r: rejected Basic challenge (https://repo.eecs.berkeley.edu) All Done |