IgnoCodeLib is missing from the Libraries page

[prisonerjohn]

The JSON entry is available on the processing-contributions repo, not sure why it's not listed on the website.
https://github.com/processing/processing-contributions/blob/master/sources/IgnoCodeLib.json

[Ignotus-mago]

I don't have access to the JSON entry. I get a 404 error. I hope this issue is still active, and that someday someone will have the time to check out the problem. Or maybe someone could just reinstate my library on the Contributed Libraries page?

If that's not a solution, should I just resubmit the library? I have a revision, with numerous small fixes. I am working on a new version, though that is likely to take time (other projects intervene).

// Paul

[REAS]

hi paul. this issue is active, but hasn't been followed up with yet. @prisonerjohn has just sent a note to the team to look into it. we're not sure why it's not showing up right now.

[runemadsen]

Sorry for the late response @Ignotus-mago. I have just run the migration script that takes the JSON files from the processing-contributions repo and moves them into the the processing-website repo and the library should be available on the website within a few minutes.

A brief explanation on what I think happened: We have to manually run the migration script (we're looking to automate this), and the last time it ran, your library was not present in the processing-contributions repo. This is probably because the script that pulls down the metadata for each library could not reach your metadata file on the specified server, so it removed the library. The next time it ran, your library was added again, but we didn't run the migration script right away.

Anyway, things should be good now. The only thing you can do on your end is to make sure that your server hosting this file is up and running smoothly.

[Ignotus-mago]

Thanks! I'm glad this issue was relatively simple to fix. It's good to see my work participating in the Processing community -- and good to know that despite the lags and interruptions we're all putting up with, sometimes small efforts and attentions can accomplish good results. I expect to be posting a minor update to the library soon, and a major revision in the Fall. cheers, Paul

…

On Wed, Jan 19, 2022 at 8:01 AM Rune Skjoldborg Madsen < ***@***.***> wrote: Sorry for the late response @Ignotus-mago <https://github.com/Ignotus-mago>. I have just run the migration script that takes the JSON files from the processing-contributions repo and moves them into the the processing-website repo and the library should be available on the website within a few minutes. A brief explanation on what I think happened: We have to manually run the migration script (we're looking to automate this), and the last time it ran, your library was not present in the processing-contributions repo. This is probably because the script that pulls down the metadata for each library could not reach your metadata file on the specified server, so it removed the library. The next time it ran, your library was added again, but we didn't run the migration script right away. Anyway, things should be good now. The only thing you can do on your end is to make sure that your server hosting this file <http://paulhertz.net/ignocodelib/download/IgnoCodeLib.txt> is up and running smoothly. — Reply to this email directly, view it on GitHub <#282 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAYWSFSTO6S42TZJFL7OXU3UW275FANCNFSM5H2UUQIQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- ----- |(*,+,#,=)(#,=,*,+)(=,#,+,*)(+,*,=,#)| --- http://paulhertz.net/