dondi

Uptime of our server prior to reboot due to OS upgrade…

I’m not sure if this is visible without logging in to Zenodo, but this is what its log says: It can be reached via the My Account > GitHub menu...

Zenodo issue was resolved with a version number bump _just for Zenodo_; Maika's PR was also merged

I have started looking into porting to Lambda. Masao gave me access to the computer science AWS account and I have started looking around Meanwhile, the `node@14` workaround has worked...

Once we have established that this is a necessary update, we will revise and commit _package.json_ accordingly

Lambda update: I have been able to build and deploy GRNsight to a Lambda function on AWS. However, the function does not run correctly yet. It looks like a configuration...

After some experimentation, the Lambda deployments are now running…somewhat. Memory had to be increased for the Lambda environment plus additional configuration options needed to be set The latest issue is...

After a few fits and starts, we have… https://2dz4kdk52j37d7xhm6cwi4u4wq0ydwdv.lambda-url.us-east-1.on.aws/# The _grnsight.css_ and _print.css_ generation is still flaky for me, but when a load successfully retrieves those, I get a working...

Edited title of this issue to reflect what needs to be done more precisely. Comment above this one provides the details

@dondi and @eileenchoe walked @mihirsamdarshi and @yshin4 through the feature file JSON format located in https://github.com/dondi/GRNsight/tree/master/documents/developer_documents/testing_script_generator and they will start trying their hand at editing this file.