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

CSV, JSON and Java links seem to be broken #2

Open
bromagosa opened this issue Aug 16, 2019 · 7 comments
Open

CSV, JSON and Java links seem to be broken #2

bromagosa opened this issue Aug 16, 2019 · 7 comments

Comments

@bromagosa
Copy link

These aren't working anymore since (I think) today:

https://think.cs.vt.edu/corgis/csv
https://think.cs.vt.edu/corgis/json
https://think.cs.vt.edu/corgis/java

@acbart
Copy link
Contributor

acbart commented Aug 16, 2019

Actually, more like a week I think. We are doing a large refactoring of the CORGIS project this summer, and we're moving to the new infrastructure now since the semester is about to start. I've (mostly) restored the Python, BlockPy, and Visualizer datasets. The CSV and JSON are next on my CORGIS todo list. The Java datasets will be a little further behind because I don't have any direct demand on them, they'll be slightly trickier than the others, and it's the easiest to find another solution to (besides perhaps Python). However, I have to make a little more progress on our other upgrades relating to BlockPy, or several of our courses will very much be on fire. I'm hoping to have the CSV and JSON datasets back in action by sometime next week, but it might be a little longer.

The major advantage of the CORGIS related upgrades is that we're no longer hosting the datasets ourselves, but instead doing so directly through GitHub Pages. This will eventually also allow a nice CI situation where uploading new datasets/versions will automatically rebuild them without a command line being involved. But best of all, we're switching from a complex JSON format to CSVs for all the source datasets, which makes it much easier to make datasets and fix existing ones.

In the meantime, all the old datasets are still available via the old GitHub: https://github.com/RealTimeWeb/datasets/tree/master/datasets

@bromagosa
Copy link
Author

Great, thank you for the thorough explanation. And for the alternative URL, too!

I just mentioned Java because I noticed the link was down too, but if these were to be gone for good you wouldn't see me complaining 😅

@acbart
Copy link
Contributor

acbart commented Sep 5, 2019

CSV files are now working again: https://think.cs.vt.edu/corgis/csv/

JSON files shouldn't take too long, so they'll be next when I get some free time. The Java ones probably won't take much time either, but the semester is definitely keeping me busy...

@bromagosa
Copy link
Author

bromagosa commented Sep 5, 2019 via email

@acbart
Copy link
Contributor

acbart commented Nov 10, 2019

More than two months later, and someone reminded me that JSON still wasn't working. Took less than an hour to get together, fortunately, but the JSON files are now working again: https://think.cs.vt.edu/corgis/json/

@jkhuggins
Copy link

Any word on getting the Java links working?

@acbart
Copy link
Contributor

acbart commented Jan 23, 2020

No updates for now, I'm afraid. I might not have time until the summer to fix those up, depending on how busy this semester starts being. I haven't had a whole lot of demand for the Java ones, since there you can usually access the data some other way. I'll point out that all the datasets are still available in the dist/ folders of the old repo: https://github.com/RealTimeWeb/datasets/tree/master/datasets/java

If someone's teaching a class and is relying on the web interface, it'd be helpful to let me know so I can redecide priority. But right now I have a lot to prep for the summer and SIGCSE, and I don't have the sense that this is causing a huge issue for many folks. Sorry for the delays!

lukesg08 pushed a commit that referenced this issue Oct 1, 2022
updates based on filename changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants