-
Notifications
You must be signed in to change notification settings - Fork 8
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
Comment on this issue when beta is refreshed. #406
Comments
For anyone who refreshes beta in the future, keep in mind that the node apps are now being run from the top directory, not the server and web-client directories. The apps are called using server/app.js and web-client/app.js. This is a direct result of the |
Did you increment the version number? Shouldn't we be on 2.0.3 now? I will look at it and post comments on the relevant issues. |
The version number is now properly incremented. |
Beta has been refreshed from PR #448. |
Beta is refreshed from PR #459. |
Did Beta get refreshed from PR #460? It doesn't seem so. |
My bad -- it did not. I need to review how to refresh beta, I haven't actually done a refresh myself yet. |
Since you @anuvarsh, @NAnguiano, and @mihirsamdarshi seem to be working right now, will somebody refresh beta from PR #460 so it is up to date with the beta branch? Thanks. |
@kdahlquist @eileenchoe I updated it about 10 mins ago, so it should be up to date now! |
Got it! |
@eileenchoe I made a quick guide on the wiki to refresh the server right here. There's a more detailed guide on the wiki if you want to read it as well. :) |
beta has been refreshed |
While the main This version was branched from |
Beta points back to the |
Just noting that beta has been refreshed by @NAnguiano to 2.0.18. |
Beta is refreshed from PR #458 :) |
The server update has been completed and GRNsight execution (both production and beta) has been restored. The beta page now shows v5.0.0 with today’s date. I have also applied the new environment variables for connecting to the expression database on production, and in my testing that part now works. The version of node on this latest Ubuntu server is indeed newer than the prior one, but still not the newest version (Ubuntu Long-Term-Service releases tend to skew very conservative in their version updates). I will see whether this new version is sufficient for the planned security updates. Stay tuned. |
Following the merge of #985 the deployed beta is now at 6.0.2 A quick check seems to show a regression in database functionality though…genes that are appearing on prod do not seem to appear on beta now (for me). Maybe we can look at it at the meeting |
Epic PR #996 has been merged into I have verified and closed the 6.0.2 regression bug #995 but have not had a chance to look into the other bugs on @Onariaginosa I think you had some follow-up commits relating to database scripting and documentation—all clear to do this @Sarronnn you can now queue up your PR for #993 after merging |
Thanks to some quick-turnaround from @Onariaginosa, |
PR #1025 has been merged into |
PR #1026 have been merged into beta. The version and modified date has been changed to reflect the new changes. beta is currently at v6.0.7 |
|
|
It took a little more time due to some delays on my part and additional review iterations, but That’s quite a few PRs and issues addressed—it’s truly bug-bash time 🐜🔨 |
I'm opening this issue so that you can post a comment here when the GRNsight beta server is refreshed, so that @kdahlquist (and others) will get an e-mail notification.
The text was updated successfully, but these errors were encountered: