Skip to content
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

failed to read Quark directory listing #1585

Closed
telephon opened this issue Jul 1, 2015 · 13 comments
Closed

failed to read Quark directory listing #1585

telephon opened this issue Jul 1, 2015 · 13 comments
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. os: macOS quarks
Milestone

Comments

@telephon
Copy link
Member

telephon commented Jul 1, 2015

With a fresh install on OS X the latest binary – trying Quarks.gui and "Check for updates" we get consistently:

"failed to read Quark directory listing"

@telephon telephon added bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. os: macOS quarks labels Jul 1, 2015
@crucialfelix
Copy link
Member

Are you implying that there was no error posted ? How is that possible:

("Failed to read quarks directory listing: % %".format(if(fetch, directoryUrl, dirTxtPath), err)).error;

What is the full error message ?

@telephon
Copy link
Member Author

telephon commented Jul 1, 2015

ERROR: Failed to read quarks directory listing: https://github.com/supercollider-quarks/quarks.git a PrimitiveFailedError

@crucialfelix
Copy link
Member

Cannot reproduce.

You will have to investigate it and provide some more information.

what does "fresh install" mean exactly ? Did you remove Application Support ? do you have any sclang_conf ?

A primitive failed. What primitive ?

@telephon
Copy link
Member Author

telephon commented Jul 2, 2015

what does "fresh install" mean exactly ?

Three people in a workshop downloaded the latest alpha binary for OSX and had the same problem. This may be our network, but still, it were three cases in a row.

Did you remove Application Support ?

You mean Application Support > SuperCollider? No. But any existing quarks folders.

A primitive failed. What primitive ?

Unfortunately, I can't tell from the error message.

@crucialfelix
Copy link
Member

Stick some debugging in, locate the error please. What did you mean about
the network ? Is it possibly caused by not having network access ?

What does "no, but any existing quarks folder" mean?

It sounds like you have encountered a serious issue, but the bug report
needs more information.

On Thu, Jul 2, 2015 at 8:34 PM Julian Rohrhuber notifications@github.com
wrote:

what does "fresh install" mean exactly ?

Three people in a workshop downloaded the latest alpha binary for OSX and
had the same problem. This may be our network, but still, it were three
cases in a row.

Did you remove Application Support ?

You mean Application Support > SuperCollider? No. But any existing quarks
folders.

A primitive failed. What primitive ?

Unfortunately, I can't tell from the error message.


Reply to this email directly or view it on GitHub
#1585 (comment)
.

@telephon
Copy link
Member Author

telephon commented Jul 2, 2015

Stick some debugging in, locate the error please.

I cannot reproduce it myself. Also don't know how to stick debugging in.

What did you mean about the network ? Is it possibly caused by not having network access ?

It is possible. But we were able to use http as usual.

What does "no, but any existing quarks folder" mean?

Did you remove Application Support ?

You mean Application Support > SuperCollider? No. But any existing quarks folders.

I meant that I didn't remove Application Support/SuperCollider/, but only Application Support/SuperCollider/downloaded-quarks and Application Support/SuperCollider/quarks.

It sounds like you have encountered a serious issue, but the bug report needs more information.

I understand, but right now I have no access to the situation that caused it.

@crucialfelix
Copy link
Member

Do they have git installed ?

@telephon
Copy link
Member Author

telephon commented Jul 3, 2015

No, they haven't. Should they?

@crucialfelix
Copy link
Member

Of course. It uses git.

the readme here and in the help file are pretty clear I think:

https://github.com/supercollider-quarks/quarks

So this is perhaps the cause of the error.

@telephon
Copy link
Member Author

telephon commented Jul 4, 2015

Ah ok - if that is the case then the fix would simply be a warning. I'll try on Tuesday.

@crucialfelix
Copy link
Member

fix is there

@scztt scztt added this to the 3.7 milestone Jul 10, 2015
@crucialfelix crucialfelix modified the milestones: 3.7.0, 3.7.x Aug 17, 2015
@miguel-negrao
Copy link
Member

Doesn't the fix solve the issue, such that it can be closed ?

@crucialfelix
Copy link
Member

because it hasn't been merged yet. which is my fault. I said I would rename *exec to *call and then merge it.

I had a really big 3 month work project, but that's now complete. I'll try to merge this in the next day or two.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that relate to unexpected/unwanted behavior. Don't use for PRs. os: macOS quarks
Projects
None yet
Development

No branches or pull requests

4 participants