-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fix model download from marketplace (Trac #838) #7
Comments
Trac update at Path to models is wrong. It is http://marketplace.sasview.org/uploads/marketplace.sasview.org/uploads/uploaded_models/pringle_schmidt_helices.py and should be |
Trac update at
|
Trac update at The fix has been pushed but automatic deployment hasn't been triggered. Andrew will look into this. |
Trac update at
to:
|
Trac update at
This is really an admin task and not a 4.1 release blocker - though it would be REALLY nice to be able to release 4.1 with announcement of a working marketplace. Still, as we are closing down work on 4.1 release am moving this to 4.2 so as not to confuse things along with ticket #2
|
Trac update at And you can always highlight the code for a model, select, copy, and paste into an editor, so it's not like the models are unattainable. Agree, not a blocker. |
Trac update at
Fixed by @wojciech in commit [https://github.com/SasView/sasmodel-marketplace/commit/80731868511c584f33a39e716da2e15199a667ef 8073186]
|
From email to ajj:
After uploading the Pringle-Schmidt model for Ian to the !SasView marketplace online we discovered a small bug with the marketplace file downloader. Although if you click on the file link on the model description page (i.e. http://marketplace.sasview.org/uploads/8) it shows the file's contents, however, clicking the link at the bottom of the page returns a file that only contains the text:
I have tried this for models 2, 4, 6 & 8 all of which return the same file. Any ideas as to why this is occurring?
Regards,
Tim
Migrated from http://trac.sasview.org/ticket/838
The text was updated successfully, but these errors were encountered: